The 4 v3.6-rc1-quantal packages have been installed using:
sudo dpkg -i Downloads/*.deb
(with a capital "D" - not lowercase "d")
instead of:
sudo dpkg -i *.deb
"The BUG: soft lockup - CPU#0 stuck for 22s!" error occurred once in 52
suspend/resumes performed since the install.
There are, however, a large frequency of other brand new suspend/resume
failures happening now.
About 30% of the time the cursor will blink in the upper left of a blank
screen for a few seconds and then resume proceeds normally.
The rest of the time there is a mixture of events:
Intermittently the:
dpm_run_callback():
acpi_button_resume+0x0/0x21 returns -19
PM: Device PNP0C0D:00 failed to resume:
error -19
message is displayed one or more times for 5 or 6 seconds and then resume
proceeds normally.
When suspend is performed from the drop down menu instead of closing the lid
these messages occur before and after suspend.
Intermittently there is a blank screen with a blinking, non-blinking, or
sometimes no cursor at all in the upper left and a mouse cursur which
moves and sometimes changes to the text insertion cursor in the middle
of the screen and sometimes doesn't and sometimes isn't there either.
Reboot is the only solution.
Intermittently the log on screen appears but the mouse cursor is frozen
near the lower right of the password insertion box and the text
insertion cursor is frozen in the password field. The password cannot be
inserted. Reboot is the only solution.
Intermittently the log on screen appears and the mouse cursor moves but
the password field will not accept any text. Reboot is the only
solution.
Once the log on screen appeared without the password insertion box and
with no cursor. Reboot was the only solution.
Intermittently there is a bright flicker of the screen immediately after
the log on screen appears - then everything proceeds normally.
The biggest, newest event was a system crash upon suspend/resume. A
screen full of text appeared containing:
watchdog detected HARD lockup on CPU#2
and ending with:
fixing recursive fault but reboot is needed
A log containing the full text hasn't been located.
The two CPU lockup events did not occur until immediately after the
Onboard application was used. The Onboard application displays the on
screen keyboard at the bottom of the log on screen by default after it
is first opened. That seemed to have a big impact. The Onboard
application was never used with the 3.2 kernel however. It was only used
with the v3.6. The system seemed to recover after several more
suspend/resumes.
There are seemingly unrelated bugs in the LibreOffice Writer help and
Gnote.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036456
Title:
BUG: soft lockup - CPU#0 stuck for 22s!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1036456/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
