Can you reproduce this? I know the initial occurrence was not caused by
a suspend/resume, but it wouldn't hurt to try to reproduce it by doing
such. If you can reproduce the issue, can you try booting with the
command line paramenter notsc to see if it fixes your issue?
Thanks
--
Kernel
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: New = Triaged
--
Kernel 2.6.32-16 PAE hangs - WARNING: at
/build/buildd/linux-2.6.32/kernel/trace/ring_buffer.c:1984
rb_add_time_stamp+0x79/0x230()
I looked through your WifiSyslog.txt and I saw multiple WARNING
statements. It seems to me that when your machine froze it was due to a
different WARNING statement than what is logged in the bug report. The
reason the bug report logged the WARNING it did is because it was the
last WARNING in the
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/40554059/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/40554060/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/40554061/ArecordDevices.txt
When it happened, I got a black screen with an immobile mouse pointer.
--
Kernel 2.6.32-16 PAE hangs - WARNING: at
/build/buildd/linux-2.6.32/kernel/trace/ring_buffer.c:1984
rb_add_time_stamp+0x79/0x230()
https://bugs.launchpad.net/bugs/534847
You received this bug notification because you are
It did not happen after resuming from suspend-to-ram (as in bug
#533498).
--
Kernel 2.6.32-16 PAE hangs - WARNING: at
/build/buildd/linux-2.6.32/kernel/trace/ring_buffer.c:1984
rb_add_time_stamp+0x79/0x230()
https://bugs.launchpad.net/bugs/534847
You received this bug notification because you
Or as in bug #527541.
--
Kernel 2.6.32-16 PAE hangs - WARNING: at
/build/buildd/linux-2.6.32/kernel/trace/ring_buffer.c:1984
rb_add_time_stamp+0x79/0x230()
https://bugs.launchpad.net/bugs/534847
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
