2.2.0 lockup

A. Wik (aw@mail1.bet1.puv.fi)
Sun, 7 Feb 1999 16:09:45 +0200 (EET)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Andrea Arcangeli: "Re: [patch] inode leakage again"
Previous message: Nigel Rowe: "NON blocking writes to a FIFO can block (un-interuptable)"

After getting the following messages from the kernel (version 2.2.0)
it locked up - couldn't log in from the network or the console, but
I was able to do an emergency remount read-only using SysRq+U.
Device 08:03 is a swap partition.

Feb 5 11:26:49 mail1 kernel: ll_rw_block: device 08:03: only 512-char blocks implemented (4096)
Feb 5 11:26:49 mail1 last message repeated 31 times
Feb 5 11:28:08 mail1 last message repeated 22 times
Feb 5 11:29:17 mail1 last message repeated 32 times
Feb 5 11:29:29 mail1 last message repeated 6 times
Feb 5 11:31:16 mail1 last message repeated 16 times
Feb 5 11:33:29 mail1 kernel: ll_rw_block: device 08:03: only 512-char blocks implemented (4096)
Feb 5 11:33:32 mail1 last message repeated 21 times
Feb 5 11:50:00 mail1 kernel: 96)
Feb 5 11:50:00 mail1 kernel: ll_rw_block: device 08:03: only 512-char blocks implemented (4096)
Feb 5 11:50:01 mail1 last message repeated 233 times

-
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/

Next message: Andrea Arcangeli: "Re: [patch] inode leakage again"
Previous message: Nigel Rowe: "NON blocking writes to a FIFO can block (un-interuptable)"