Just a failed drive. Was: Sysreq during system hang where ssh/screenstill accessible.
From: Mike Mestnik
Date: Mon Feb 13 2012 - 20:38:47 EST
It's kind of odd that these are the symptoms of a failing disc. I think
perhaps syslog and others should be made to not swap??
This may also have something to do with my zram hack that re-mounts the
zram swaps every 5min to flush them to disk.
On 02/13/2012 12:30 PM, Mike Mestnik wrote:
Hello,
I have an unusual hang:
The box is responding to monitor wakeup key presses and putting the
display to sleep after idle, however the screen is always blank.
From the network side a previously started root ssh screen session can
create more views,but the shell never starts, neither does ls from an
existing shell.
I've configured remote logging and there is noting in any of the logs
to indicate a problem, smart-tools is installed.
The remote log(over SCTP) is still connected and the IRC client is
still connected.
Kernel messages are being logged, last msg from apparmor about empathy.
Key presses wake up monitor, but sysreq-s is not logging anything.
No further ssh shells able to check, but I don't think that dmesg
would even start.
However ssh/screen is still responsive to create new views and switch
views, but the shell never starts.
Feb 12 17:33:33: The only error is smatd: Prefailure: Spin_Up_Time (3)
changed to: 197
Feb 13 12:54 AM an email http://pastebin.com/A8srcY7v
However nothing in the _remote_ log around 1AM/12:54.
Any thoughts?
linux-image-3.2.0-15-generic-pae
System specs.
http://pastebin.com/35NwE0G1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/