Some additional info:
1) It happened in 2.2.0-pre7-ac5 once, too :((
2) Although the system cannot be reached by telnet, active connections are
not broken (e.g. masquerading worked even when the system was totally locked
up).
3) All of these lock ups happened under X here with a rather heavy cpu or
disk load (kernel compilation or copying of large directories).
4) After exiting X (alt-ctrl-backspace works) no console can be reached
(alt-sysrq-r doesn't help) -- black screen :((
5) Nothing strange can be seen in any logs and, what is curious, top doesn't
show anything suspicious (distributed.net client gets the highest cpu time
and other processes have less than 10% of cpu time).
6) My configuration:
* pentium 166mmx, 64mb ram, only ide disks used during lock-ups
* kernel compiled using egcs 1.1.1 (debian packaged) with -mpentium
but no other optimizations options changed
> All I can do is push the reset button and wait till my raid devices have
> been checked =(
I advise using sysrq commands (they work even then) -- alt-sysrq-s syncs disks
and alt-sysrq-u umounts them. It doesn't prevent all fs errors, though.
Qman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/