Tyler, the attached diff helps me read/write files over 4GB. I think
some of the changes may be redundant, so I'm checking to see what is the
minimal set of changes required.
** Patch added: "32-bit-fixes.diff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243636/+attachment/3889738/+
Tyler, reduced it down to a one line fix. Tested with a 0.5GB, 2GB, 4GB,
8GB, 32GB test file with a sanity check on each byte. Patch attached
below. Not yet tested with ecryptfs tests, but it looks like the root
issue.
** Patch added: "potential fix"
https://bugs.launchpad.net/ubuntu/+source/
the 4 GB.
[Impact]
32 bit users experience corruption of large files.
[Fix]
A cast is needed when shifting the page's index. Colin and I independently
identified the problem. It is a simple fix that is currently located in the
eCryptfs next branch:
http://git.kernel.org
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491467/+attachment/4486870/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1
** Project changed: launchpad => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1504308
Title:
wifi light indicator doesn't stop flashing after update kernel linux
to 4.
Public bug reported:
On resume the screens (laptop + external) showed windows as before
suspend but the machine was completely unresponsive.
ProblemType: KernelOops
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-14-generic 4.2.0-14.16
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.
** Description changed:
On resume the screens (laptop + external) showed windows as before
suspend but the machine was completely unresponsive.
+
+ This happens around 1 in 10 times I suspend. I am suspending using pm-
+ suspend or via the cog > Suspend.
ProblemType: KernelOops
Distr
Tested with mainline kernel 4.3.0 rc5 and got the same failure, though
it seemed to take longer before it failed. Likely just the statistics
working themselves out though.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.3.0-rc5
** Changed in: linux (Ubuntu)
Status:
Done some time back:
revno: 556
committer: Colin Watson
branch nick: sync-blacklist
timestamp: Tue 2015-01-27 15:48:18 +
message:
unblacklist makedumpfile; newer version syncable from experimental
... and we got a suitable version in vivid by way of a sync from
experimental.
** Changed
A full rebuild is in progress at the moment, and nova-compute segfaulted
yesterday, so it doesn't look as though disabling KSM was enough.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/150
*** This bug is a duplicate of bug 1459571 ***
https://bugs.launchpad.net/bugs/1459571
** This bug has been marked a duplicate of bug 1459571
Keyboard shortcuts stop working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
On Fujitsu A544 laptop (and likely others) fitted with SSD, kworker
takes 100% of one core of CPU due to GPE13 interrupt storm
See upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=53071
The bug can be identified by repeatedly running
cat /sys/firmware/acpi/interrupt
By bisecting the kernel I have determined that the problem is not seen
on the last Ubuntu 3.19 kernel 3.19.8-vivid but is seen on the first
4.0 kernel that will build using fakeroot debian/rules binary-headers
binary-generic, which is
commit 636cdd7b2930ca2cdaf90eedd04fdb9fc7a8d5ec
Author: Stefan
I can confirm that
v3.19 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/ does
not show the problem
4.0-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/
and
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/
both do show the problem
--
You received
02f1f2170d2831b3233e91091c60a66622f29e82
http://kernel.ubuntu.com/~jsalisbury/lp1491467
linux-image-3.19.0-031900-generic_3.19.0-031900.201509021605_amd64.deb
is BAD
that is it shows the bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
c5ce28df0e7c01a1de23c36ebdefcd803f2b6cbb
linux-image-3.19.0-031900-generic_3.19.0-031900.201509022146_amd64.deb
is GOOD :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
718749d56214aa97015fe01b76b6d6dd0c171796
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031253_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwo
b3d6524ff7956c5a898d51a18eaecb62a60a2b84
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031452_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwo
8cc748aa76c921d8834ef00f762f31acd2c93aa8
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031637_amd64.deb
is BAD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwor
d3f180ea1a44aecba1b0dab2a253428e77f906bf
linux-image-3.19.0-031900-generic_3.19.0-031900.201509032049_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwo
ba4877b9ca51f80b5d30f304a46762f0509e1635
linux-image-3.19.0-031900-generic_3.19.0-031900.201509041408_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwo
7b1ee96f074cc931a2c226b33607fe7a74d5cba3
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509050242_amd64.deb
is BAD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
As a matter of interest, which repository have you cloned from?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kworker consuming cpu due to GPE13 interrupt storm on Fujits
875edad528cf29b382e82837e652e997aec16c49
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081446_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
Can you confirm the repo please, I get
$ git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/
Cloning into 'linux'...
fatal: remote error: Repository '~ubuntu-kernel/ubuntu/+source/linux' not found.
Alternatively is it fundamentally the same (as far as this exercise is
concerned
afb5abc262e962089ef2d7c2bbf71bb6f53a2a78
/home/colinl/Downloads/linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081446_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
30fc8d138e9123f374a3c3867e7c7c5cd4004941
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081948_amd64.deb
is Bad
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
I don't think you have actually, there's nowt there :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544
S
71ed848fd791bc0b53a1b7a04f29eb9e994c7cbb
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509091541_amd64.deb
is BAD
Only one, or two, to go :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
It may be of interest that another A544 running kernel 3.13 exhibits the
problem. It went away some time between then and 3.19 and came back in
4.0. The other machine does not have an SSD so that may not be a
factor, though comments in the upstream bug suggested that it was a
factor. Of course t
0dc553652102c55a43eb1ab52e2049e478469f53
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509092055_amd64.deb
is BAD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
Have I missed something or has it not arrived yet?
I have gone back and confirmed that afb5abc262e962089e was good and
0dc553652102c55a4 is bad, just in case I had made a mistake.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
OK. In case it is of interest I have determined that the problem was
originally fixed between mainline kernels 3.13.11.11-trusty and
3.14-rc1-trusty, before being reintroduced in 4.0.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I think 4.3-rc1 kernel build has failed, at least there are no images
there. I will test it when they appear.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kworker consu
4.3-rc1 kernel (linux-
image-4.3.0-040300rc1-generic_4.3.0-040300rc1.201509160642_amd64.deb)
also exhibits the problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwor
** Bug watch added: Red Hat Bugzilla #1290311
https://bugzilla.redhat.com/show_bug.cgi?id=1290311
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=1290311
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
Is anything happening on this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544
Status in Linux:
Unknow
** Attachment added: "/proc/acpi/wakeup from current kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504420/+attachment/4525281/+files/wakeup.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
After several weeks running with the suspend command
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
with both the latest mainline kernel I was unable to make it fail. I reverted
to the current kernel and it still refused to fail. I then resorted to just
using pm_suspend (with c
** Attachment added: "dmesg on re-boot after failure with current kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504420/+attachment/4525280/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
Public bug reported:
We're working on bringing up new arm64 builder infrastructure in
Launchpad scalingstack to replace the current bare-metal builders, and
the current plan is that they should be able to cover armhf as well.
Ideally, we would be able to do this using the same guest images:
scalin
This is a specific actionable feature request with no relevant log
files.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
** Project changed: launchpad => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2014037
Title:
ACPI bios error on dell laptop.
Status in linux package in Ubuntu:
New
B
Experiencing the same problem after upgrade to Impish. I have determined
that the desktop does actually start after a resume from suspend, but
the screen remains blank, with the backlight on. (To determine this, I
used a keyboard shortcut to launch a terminal window and typed a reboot
command succe
Same problem on 6.5.0-17-generic #17~22.04.1-Ubuntu.
System Information
Manufacturer: LENOVO
Product Name: 20SUS2LM0D
Version: ThinkPad P15 Gen 1
Serial Number: PF2J52X3
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_20SU_BU_Think_FM_ThinkPad P15 G
I'm seeing the same thing with 20.04 when running any of the 5.13
kernels. Last tested with 5.13.0-41.
My setup is an ASUS Hero XIII motherboard. Monitor plugged in, with a
second monitor plugged in via a USB / HDMI adapter (not sure if that is
relevant)
I had to remove iwlwifi-ty-a0-gf-a0.pnvm a
Confirmed, my system boots fine when that second monitor isn't plugged
in. I removed the bluetooth driver as well, but that didn't fix it.
This is the adapter I'm using (I believe):
https://us.amazon.com/NiaoChao-Adapter-Charging-Compatible-MacBook/dp/B08CRXD22M
I have a bunch of USBC / HDMI ada
** Changed in: ubuntu-release-notes
Assignee: Colin Watson (cjwatson) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/283316
Title:
CD-ROM tray closes automatica
I can confirm getting same errors on an LG gram laptop, running Intel
AX201 wifi hardware. I get frequent disconnect and reconnects until
finally, it failed to reconnect, despite reboots. I also see the message
concerning a microcode software error.
Removing ucode newer than v55, as suggested by O
Problem occurs on my LG gram laptop with Intel AX2-1, running Kubuntu
21.10. Disconnects/reconnects occurred sporadically for a week or two
recently but now it fails to reconnect, even on reboot. Log shows the
same error messages reported above.
--
You received this bug notification because you a
Public bug reported:
https://packages.ubuntu.com/bionic/kernel/linux-modules-4.15.0-196-generic
file kernel/drivers/media/usb/gspca/gspca_sonixj.ko
in this driver, the illuminator est considered driven by the sensor chip.
i buyed recently an hercules (guillemot) webcam with illuminator .. 06f8:30
i a not able to have a log file when a light remain switched off
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997102
details of modification (4 program lines were modified)
modification in initialisation
static const struct usb_device_id device_table[]
...
/* {USB_DEVICE(0x06f8, 0x3008), BS(SN9C105, OV7660)}, la webcam a des LED
d'éclairage*/
{USB_DEVICE(0x06f8, 0x3008), BSF(SN9C105, OV7660, F_I
And what means "upstream" for you ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1997102
Title:
illuminator control in driver sonixj
Status in linux package in Ubuntu:
Confirmed
Bu
Too complicated for me ... there is only 4 lines to change ... and il
will not spend one full day to understand your labyrinthic method.
Regards
Jean COLIN
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Public bug reported:
I tried to do a routine upgrade and reflash of the Launchpad riscv64
builders, which pulled in linux-image-5.11.0-1017-generic
5.11.0-1017.18~20.04.1. The resulting image failed to boot with the
following (complete) console output:
Device 0: QEMU VirtIO Block Device
Hm, I actually get similar results when I revert to 5.8.0-29:
Device 0: QEMU VirtIO Block Device
Type: Hard Disk
Capacity: 71680.0 MB = 70.0 GB (146800640 x 512)
... is now current device
Scanning virtio 0:1...
Found /boot/extlinux/extlinux.conf
OK, this is actually due to the changes between u-boot-menu
4.0.1ubuntu0.1 and 4.0.2ubuntu5~20.04.1. The relevant difference is
that the menu entry now has `fdtdir
/lib/firmware/5.8.0-29-generic/device-tree/` (or similar) when it
previously didn't load a device tree at all.
I successfully worked
I had the same problem with that driver and fixed it in the driver.
Feel free to use my patch for that:
https://github.com/enlyze/xr-usb-serial/commit/6515173a8b2681fd52cc2747d7282f4e47bdd254
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
** Project changed: launchpad => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912646
Title:
Ubuntu 20.10 freeze after update
Status in linux package in Ubuntu:
Incom
This still seems to be happening on 5.8. Different board yet again, but
same situation. Crashes every 1/X times when resetting the board. I
don't have logs of the actual crash (ZFS root maybe?), but it locks up
right after the "failed to set dtr/rts" like the others reported here,
with similar logs
For the other folks that see this, it does seem to help to use the reset
button slower, for what its worth. Possibly offers a better
disconnect/reconnect timing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
** Project changed: launchpad => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Assignee: edsnowden2021 (edsnowden2021) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/19
*** This bug is a duplicate of bug 1917274 ***
https://bugs.launchpad.net/bugs/1917274
** This bug has been marked a duplicate of bug 1917274
MSI MS-7817 desktop linux kernel 5.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
** Project changed: canonical-identity-provider => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904339
Title:
kernel 5.4.0-53 (amd64) won't shut down
Status in linux p
(End User: https://askubuntu.com/questions/1455925/dell-
xps-13-plus-9320-horizontal-lines-static-after-installing-latest-
release)
Test kernel did not correct the issue on my machine.
https://people.canonical.com/~khfeng/lp2007516/jammy-5.19/
OPERATING SYSTEM: Ubuntu 22.04
Kernel:
eDP dump file
** Attachment added: "eDP_PSR_status_dump.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007516/+attachment/5650604/+files/eDP_PSR_status_dump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1
lspci dump file
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007516/+attachment/5650605/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.l
So far the artifact has _not_ returned running:
6.2.0-060200rc2drmintelnext20230228-generic
I'm seeing overall good behavior with this kernel.
I will need more information/assistance on how to apply the quirk. Do I
download the patch files and execute them, or do I edit the grub file as
descri
The problem remains with the test kernel:
https://people.canonical.com/~khfeng/jammy-5.19-fast-wake/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2007516
Title:
XPS 9320 screen
Kernel 5.19.0-3035-generic x86_64 has good behavior.
I have not seen the artifacts with this version while performing the
typical workflow that normally caused it to manifest.
https://people.canonical.com/~khfeng/lp2002986-2/
--
You received this bug notification because you are a member of Ke
We plan to switch the buildd host system from Ubuntu 20.04 to 22.04
fairly soon, which would result in using a 5.15 kernel instead of 5.4.
Would that be enough to fix this problem?
** Project changed: launchpad => launchpad-buildd
--
You received this bug notification because you are a member of
** Project changed: launchpad => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2018420
Title:
linux kerkel 6.2.0.20-generic failed to install
Status in linux package in
Public bug reported:
Under ubuntu plucky (upgrade from 24.10) the nvidia driver package doesn't seem
to work.
- No graphic acceleration (llvmpipe is used)
- No resolution change
The driver installs successfully, I haven't seen any specific log.
A RTX 3080 is used.
ProblemType: Bug
DistroRele
BTW, I verified this on bionic, all fixed.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1833410
Title
verified zfsutils-linux 0.7.5-1ubuntu16.6 with 4.15.0-55.60, tested
against the Ubuntu zfs regression tests, no failures. Looks good to me.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
verified OK on xenial, 4.4.0-156
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1833410
Title:
idle-p
** Description changed:
+ == SRU Justification, BIONIC ==
+
+ Running the autotest regression test ubuntu_nbd_smoke occasionally trips
+ I/O errors such as:
+
+ [ 700.668758] print_req_error: I/O error, dev nbd0, sector 0
+ [ 700.668840] Buffer I/O error on dev nbd0, logical block 0, async pag
I've been running this for 3+ days now and cannot reproduce this
specific issue. From the look of the error it appears to be a hardware
related NMI issue, so perhaps we have some faulty H/W in this specific
case.
When running these tests for several days now with and without the
kernel parameters
I can't repro this specific issue, I believe it may be a H/W issue as
reported in this bug. Other reasons for the reboot tests failing are
marked in comment #3. Marking this as won't fix.
** Changed in: linux-aws (Ubuntu)
Status: In Progress => Won't Fix
--
You received this bug notifica
Fix sent to mailing list: https://lists.ubuntu.com/archives/kernel-
team/2019-April/099806.html
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1840161
Title:
Very severe regression in ZFS 0.7.12 in 18.04.3
Stat
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** Changed in: thermald (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Tags removed: veri
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** Tags removed: verification-needed verification-needed-bionic
** Changed in: thermald (Ubuntu Bionic)
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** Changed in: thermald (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Tags removed: veri
I wonder if the msr module is not loaded. Try
sudo modprobe msr
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1840454
Title:
kernel 5.2 disallows thermald's direct MSR writes
Statu
Good point.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1840454
Title:
kernel 5.2 disallows thermald's direct MSR writes
Status in linux package in Ubuntu:
Incomplete
Status in the
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1840867
The issue was that we had a lockup on a futex on a pthread_cond_wait().
I've added a time out to this and a re-spin with a yield to break the
lockup.
Fix committed:
https://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=e7ef382acc7d49aa21a7e060872717c782db41aa
Please re-test and let me kn
And also this fix is helpful:
https://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=9fdaf8b716038f12a188ba82fa25a8638bdd09bf
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1840867
@Dimitri, so you set the defaults w/o any benchmarking stats?
I'll see if I can get some time to check what the sane options are per-
arch.
Colin
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Title:
Change kernel compression method to improve boot speed
Status in linux package in Ubuntu:
Fix Committed
Bug description:
Colin King has done some analysis of kernel boot speed using different
kernel compression methods. Results for x86 are at:
https://kernel.ubuntu.com/~cking
Seems to occur when exercising /dev/hpet
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1841747
Title:
dev test in ubuntu_stress_smoke_test crashes AWS c5.large with Disco
Status in
301 - 400 of 2653 matches
Mail list logo
