Christopher, since bug report 153241 documents the bisecting the kernels
to isolate this problem, is there any reason for Raymond and I to do
likewise?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Joseph, yes, we will be testing the 4.4.19 kernel to see if the
DID_ERRORs manifest themselves.
--
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/1618678
Title:
Disk Device Driver Reported
I am still having to kill the X server (kill -QUIT) ever other day or so
because the GUI hangs, while awaiting instructions on how to move this
bug report to the Xorg X server or the Radeon video device driver. Thank
you.
--
You received this bug notification because you are a member of Kernel
I am still having to kill the X server (kill -QUIT) ever other day or so
because the GUI hangs, while awaiting instructions on how to move this
bug report to the Xorg X server or the Radeon video device driver. Thank
you.
--
You received this bug notification because you are a member of Kernel
I am still having to kill the X server (kill -QUIT) ever other day or so
because the GUI hangs, while awaiting instructions on how to move this
bug report to the Xorg X server or the Radeon video device driver. Thank
you.
--
You received this bug notification because you are a member of Kernel
I am still having to kill the X server (kill -QUIT) ever other day or so
because the GUI hangs, while awaiting instructions on how to move this
bug report to the Xorg X server or the Radeon video device driver. Thank
you.
--
You received this bug notification because you are a member of Kernel
I am still having to kill the X server (kill -QUIT) ever other day or so
because the GUI hangs, while awaiting instructions on how to move this
bug report to the Xorg X server or the Radeon video device driver. Thank
you.
--
You received this bug notification because you are a member of Kernel
I am still having to kill the X server (kill -QUIT) ever other day or so
because the GUI hangs, while awaiting instructions on how to move this
bug report to the Xorg X server or the Radeon video device driver. Thank
you.
--
You received this bug notification because you are a member of Kernel
I am still having to kill the X server (kill -QUIT) ever other day or so
because the GUI hangs, while awaiting instructions on how to move this
bug report to the Xorg X server or the Radeon video device driver. Thank
you.
--
You received this bug notification because you are a member of Kernel
I am still having to kill the X server (kill -QUIT) ever other day or so
because the GUI hangs, while awaiting instructions on how to move this
bug report to the Xorg X server or the Radeon video device driver. Thank
you.
--
You received this bug notification because you are a member of Kernel
I am still having to kill the X server (kill -QUIT) ever other day or so
because the GUI hangs, while awaiting instructions on how to move this
bug report to the Xorg X server or the Radeon video device driver. Thank
you.
--
You received this bug notification because you are a member of Kernel
I am still having to kill the X server (kill -QUIT) ever other day or so
because the GUI hangs, while awaiting instructions on how to move this
bug report to the Xorg X server or the Radeon video device driver. Thank
you.
--
You received this bug notification because you are a member of Kernel
I am still having to kill the X server (kill -QUIT) ever other day or so
because the GUI hangs, while awaiting instructions on how to move this
bug report to the Xorg X server or the Radeon video device driver. Thank
you.
--
You received this bug notification because you are a member of Kernel
This bug report ought to be transferred from Linux Package to either
the X server or the Radeon video driver. The X server still hangs in a
livelock-like fashion every three or four days, requiring a kill -QUIT
to kill the server.
--
You received this bug notification because you are a member of
When the system hung this afternoon, I was able to recover control by
killing the X server with a QUIT signal (3). However, when I logged back
in from the display manager (LightDM), the color palette was messed up.
Logging out and back did not resolve the problem. I finally power cycled
the
I recovered from a system hang this morning with a kill -SIGQUIT X
process ID. The color palette is still fine.
How may I move this bug report to either Xorg or to the Radeon video
driver?
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is
When the system hung this afternoon, I was able to recover control by
killing the X server with a QUIT signal (3). However, when I logged back
in from the display manager (LightDM), the color palette was messed up.
Logging out and back did not resolve the problem. I finally power cycled
the
System hung again today but I was able to kill the X server (Xorg) with
signal 3 (QUIT) by ssh-ing in from another machine on the LAN, running
top(1) as root, and using the k command.
To recap the current status: running kernels 3.0.0 though the current
Ubuntu 12.10 kernel, 3.2.0-56-generic, an
Booted the current Ubuntu 12.10 kernel, 3.2.0-56-generic.
--
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/1223055
Title:
System Hangs With Kernel Migration Processes Consuming 100% CPU
Running 3.2.0-55-generic, my system again hung this morning but the
evidence is increasingly pointing to either the X server (Xorg) or the
video device driver as the culprit.
As earlier, the keyboard became non-responsive (except the kernel magic
keys) and the mouse nearly non-responsive, the
Running kernel 3.0.0-0300-generic this morning, the system hung like
before: kworker/0 and kworker/1 processes each consuming about 15%, Xorg
35%. The Xorg process would not respond to signals 1, 15 or 9. I
resorted to the magic key sequence R-E-I-S-U-B to reboot, running the
current stock kernel,
Whoops! I just realized that you wanted me to also test the 3.0 final
kernel so I will boot that shortly.
Thanks.
--
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/1223055
Title:
System
The system hung running the 3.1 final kernel so I reverted back to
running the current stock Ubuntu kernel, 3.2.0-55-generic.
--
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/1223055
Title:
Booted and running 3.0 final kernel. Will report success or failure
during the next two weeks.
--
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/1223055
Title:
System Hangs With Kernel
I have not received a reply from Benjamin Herrenschmidt so I opened
kernel upstream bug report 63801
(https://bugzilla.kernel.org/show_bug.cgi?id=63801).
** Bug watch added: Linux Kernel Bug Tracker #63801
http://bugzilla.kernel.org/show_bug.cgi?id=63801
--
You received this bug notification
The 3.12 kernel hung this morning, as in earlier instances. These are a
few observations from a remote login (ssh) from another system on the
LAN:
* No process was consuming an inordinate amount of CPU, unlike previous
migration/0 and migration/1 processes
* No process or thread was doing any
Joseph, I mailed Benjamin Herrenschmidt b...@kernel.crashing.org an
upstream bug report.
Regarding bisecting, I will run the 3.1 kernel for two weeks or until I
observe the same failure. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Will do!
--
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/1223055
Title:
System Hangs With Kernel Migration Processes Consuming 100% CPU
Status in “linux” package in Ubuntu:
Incomplete
I had to reboot my system this morning for the same reason as described
in the bug description: System became non-responsive as though the CPU
was running at 100% or it was fielding thousands of interrupts. I am
currently running the 3.2.0-54 kernel.
--
You received this bug notification because
Will do. I will report results within two weeks, by October 14, 2013.
--
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/1223055
Title:
System Hangs With Kernel Migration Processes
Joseph, I am now running the 3.2.0-54 kernel that was pushed out today:
$ uname -a
Linux elijah 3.2.0-54-generic #82-Ubuntu SMP Tue Sep 10 20:09:12 UTC 2013 i686
i686 i386 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I booted the 3.12rc kernel but discovered that All Settings - Sound no
longer recognizes my two attached USB headsets. It only reports the
motherboard sound card (Thinkpad T60). These are the /var/log/syslog
messages from attaching one of the headsets:
==
Sep 26 15:41:32
I am following up on my 9/18/13 and 9/22/13 question. It is safe to run
the 3.12rc kernel even though the installation reported many missing
firmware warnings? The first few warnings from the installation log I
posted above are:
W: Possible missing firmware /lib/firmware/radeon/CYPRESS_smc.bin
Joseph, I'd like to test the 3.12 kernel but need an answer to my
question about the missing Radeon firmware messages (see 9/18/13 note
above). Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
What about the Radeon module missing firmware messages?
--
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/1223055
Title:
System Hangs With Kernel Migration Processes Consuming 100% CPU
Joseph, I installed the three 3.12-rc1 kernel packages:
linux-headers-3.12.0-031200rc1_3.12.0-031200rc1.201309161735_all.deb
linux-image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_i386.deb
linux-headers-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_i386.deb
but the
** Attachment added: Linux kernel 3.12 rc1 installation log.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223055/+attachment/3827945/+files/Linux%20Kernel%203.12%20Install%20Log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Joseph, I am a bit leery of running an RC kernel. Any chance of
filesytsem corruption?
Thanks.
--
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/1223055
Title:
System Hangs With Kernel
Today (September 15 ,2013, 1830 CDT) this Ubuntu 12.10 system running
the 3.11 kernel hung as described above. Adding tag kernel-bug-exists-
upstream.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
Once or twice a week, the system becomes non-responsive, with the mouse
cursor tracking mouse movement but no keyboard response. Until today I
would resort to using the kernel magic keys to reboot the system
(R-E-I-S-U-B). Today I remotely logged in from another machine on
Joseph, to answer your question regarding when the issue appeared, it
has been something I have tolerated for a long time ( 6 mo) so it
probably appeared after an Ubuntu update, but I cannot pinpoint which
one.
Regarding testing the latest upstream kernel, yes, I believe I can test
v3.11 but
Okay, I am running v3.11 so I'll report any subsequent hangs between now
and September 23, 2013.
$ uname -a
Linux elijah 3.11.0-031100-generic #201309021735 SMP Mon Sep 2 21:44:40
UTC 2013 i686 i686 i386 GNU/Linux
$
Thanks.
--
You received this bug notification because
42 matches
Mail list logo
