[Bug 20282] Full system crash after normal shutdown (no problems after hard reset)

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=20282
Ubuntu | UNKNOWN





------- Additional Comments From nkoren at gmail.com  2005-12-01 17:36 UTC -------
Hi, and thanks for following up on this.  I can always log in; the
freezing/crashing behavior doesn't start until after that.  Once it has frozen,
control-alt-f1 doesn't do anything.

Here's the output of "df":

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hdc1             12516412   4583032   7297684  39% /
tmpfs                   258244         0    258244   0% /dev/shm
tmpfs                   258244     12588    245656   5%
/lib/modules/2.6.12-10-386/volatile

And here's the output of "ifconfig lo":

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2774 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2774 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:252074 (246.1 KiB)  TX bytes:252074 (246.1 KiB)

Of course I'm in a stable session right now, having just booted up from a hard
reset.  I could try to get this info after a soft shutdown, but probably won't
have enough time to open a terminal capture the info, and save it, before the
machine crashes.

Also, I was looking more carefully at the shutdown sequence, and although
nothing is actually marked as "fail", there *is* some kind of message about
resetting the filesystem to read-only.  However it scrolls by too quickly for me
to read.  Is there anywhere in the logs that captures the output of the shutdown
process?  I haven't been able to find it, but if there is, I bet that would give
you the clue that you need.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.