Breezy sometimes does not manage to reboot

Bug #25548 reported by Jörg Höhle
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
Medium
Ben Collins

Bug Description

Hi,

Sometimes, esp. when using "reboot" from the login screen, the last messages on
the console are
* Shutting down LVM Volume Groups
* Rebooting
[4294825.547000] Restarting system
After which the system does not react anymore. I need to power off and on.

The last line ([429...] which looks like Breezy's new style syslog format) seems
suspicious to me, since it does *not* appear when the system manages to reboot
by itself.
I'm surprised to see a syslog-style message. I would have expected syslog etc.
to be long stopped when that state is reached.

The machine is a Fujitsu/Siemens laptop Lifebook C1110.
I can't remember having experience this with Hoary or Warty.

Actually, I wonder whether sometimes kernel logging gets confused: I see
incomplete snippets of lines like in:
Nov 9 13:43:31 localhost kernel: No module symbols loaded - kernel modules not
enabled.
Nov 9 13:43:31 localhost kernel: .617000] Checking if this processor honours
the WP bit even in supervisor mode... Ok.
                                  ^^^^^^^^
Nov 9 17:08:51 localhost kernel: No module symbols loaded - kernel modules not
enabled.
Nov 9 17:08:51 localhost kernel: 000] Mount-cache hash table entries: 512

Nov 9 17:56:25 localhost kernel: No module symbols loaded - kernel modules not
enabled.
Nov 9 17:56:25 localhost kernel: nitialized
(the latter may be a typo in kernel sources?)

Actually, there's a repeatable pattern here. Every time after "No module symbols
loaded", the next line is partially garbled.
Nov 9 15:21:18 localhost kernel: No module symbols loaded - kernel modules not
enabled.
Nov 9 15:21:18 localhost kernel:

Regards,
 Jörg Höhle

Revision history for this message
Jörg Höhle (joerg-cyril-hoehle) wrote :

>* Rebooting
>[4294825.547000] Restarting system
>The last line ([429...] which looks like Breezy's new style syslog format) seems
>suspicious to me, since it does *not* appear when the system manages to reboot
>by itself.
This is just a short note that the last line with [4294825.5...] is independent
on whether the system manages to reboot or not. Sometimes such a line appears,
sometimes not.

Revision history for this message
Ben Collins (ben-collins) wrote :

If possible, please upgrade to Dapper's 2.6.15-7 kernel. If you do not want to
upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
are due out within the next few days.

Let me know if this bug still exists with this kernel.

Revision history for this message
Carthik Sharma (carthik) wrote :

Thank you for reporting this bug and following up on it.

I am marking this bug Closed since there has been no response from you for over three months. We would like to fix all existing issues, but need feedback to help with debugging.

Should you still have a problem with the latest up to date Dapper kernel and packages, please reopen this bug. In this case, please answer the questions that have already been asked of you before and provide the log files and information required for debugging.

Changed in linux-source-2.6.15:
status: Needs Info → Rejected
Revision history for this message
Jörg Höhle (joerg-cyril-hoehle) wrote :

I'm Sorry,
I should have closed this bug myself since I've not seen it repeated for some time. (And I'm still running Breezy, not Dapper).
Regards,
 Jörg Höhle

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.