Public bug reported:
The system hangs when I ask it to print, and I can't get it to panic and
dump. Keyboard sysrq doesn't seem to do anything, nor does waiting 15
minutes. Using the text console makes no difference either. Memtest
shows no errors. When I boot 4.4.0-112 kernel there's no probl
The hang is gone in mainline 4.4.126, thanks.
** Tags added: kernel-fixed-upstream
--
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/1760508
Title:
system hang
Status in linux package in
** Changed in: linux (Ubuntu Xenial)
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/1760508
Title:
system hang
Status in linux package in Ubuntu:
Information only: The hang is still present in linux-
image-4.4.0-119-generic, but takes a few seconds longer (maybe 30
instead of instantly) to manifest.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
I tested mainline 4.4.119, and the hang is not present.
--
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/1760508
Title:
system hang
Status in linux package in Ubuntu:
Incomplete
Status
I went back and tested mainline 4.4.113, 4.4.114, 4.4.115 and 4.4.116,
none shows the hang.
--
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/1760508
Title:
system hang
Status in linux pac
Latest kernel, 4.4.0-121-generic, from xenial main repository works now,
thanks all for the fixes.
--
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/1760508
Title:
system hang
Status in li
I see a lot of chatter that is likely confusion related to the leak
manifestations, and the false belief that eliminating X or Y memory
consumer "fixed" the problem. The proper test is probably to leave a
computer running, idle for 24-48 hours; if you begin swapping and
running out of RAM while tak
X1 Carbon 2014, Ubuntu 14.04, Intel 7260 wireless module, was definitely
severely affected by this bug.
Have been "relatively" stable with:
1. In the /usr/lib/pm-utils/power.d directory in the file wireless I changed in
the end of the file with two off so that there is no wireless powersave:
cas
9 matches
Mail list logo
