I've been using "Linux rhino 2.4.0-test8 #5 Thu Sep 28 20:48:16 EDT 2000 i686 unknown" successfully until starting yesterday. I've had two complete lockups while executing a user-space program as root (dselect if it matters, which is a little more "bursty" network wise). The first failure resulted in a total lock immediately, with no log info once fsck recovered. This time I was able to collect the syslog, but of interest was that "sync" wouldn't work, nor would saving a large file (my email from within xemacs). The syslog entry was: Oct 25 09:40:04 rhino kernel: kernel BUG at ll_rw_blk.c:711! Oct 25 09:40:05 rhino kernel: invalid operand: 0000 Oct 25 09:40:05 rhino kernel: CPU: 0 Oct 25 09:40:05 rhino kernel: EIP: 0010:[__make_request+161/1444] Oct 25 09:40:05 rhino kernel: EFLAGS: 00010282 Oct 25 09:40:05 rhino kernel: eax: 0000001f ebx: c6f250e0 ecx: 00000000 edx: ffffffff Oct 25 09:40:05 rhino kernel: esi: c6f250e0 edi: c02815a0 ebp: 00000001 esp: c7fb7f3c Oct 25 09:40:05 rhino kernel: ds: 0018 es: 0018 ss: 0018 Oct 25 09:40:05 rhino kernel: Process kflushd (pid: 4, stackpage=c7fb7000) Oct 25 09:40:05 rhino kernel: Stack: c01ec485 c01ec722 000002c7 c6f250e0 00000001 0000000c 00000000 001e8480 Oct 25 09:40:05 rhino kernel: c02815b8 c02815b0 00000000 00000008 00000000 00000000 c01633e2 000000fe Oct 25 09:40:05 rhino kernel: c0163fa1 c02815a0 00000001 c6f250e0 c6f250e0 00000000 00000001 c7fb7fd8 Oct 25 09:40:05 rhino kernel: Call Trace: [tvecs+56989/63896] [tvecs+57658/63896] [blk_get_queue+50/64] [generic_make_request+257/272] [ll_rw_block+337/448] [flush_dirty_buffers+130/180] [bdflush+111/168] Oct 25 09:40:05 rhino kernel: [kernel_thread+40/56] Oct 25 09:40:05 rhino kernel: Code: 0f 0b 83 c4 0c 0f b6 46 15 0f b7 4e 14 8b 14 85 20 5c 27 c0 Billy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
