Hi all, I suddenly found myself unable to access one of my file systems on a 7.2 machine with all of the updates except wa running the 2.4.9-21 kernel. Looking in the logs the only thing I could see was the following: Mar 6 05:12:31 kanga syslogd 1.4.1: restart. Mar 6 05:12:30 kanga kernel: [ext3:__insmod_ext3_S.bss_L1024+163840/116200300] __insmod_wd_S.bss_L1376 [wd] 0x20 Mar 6 05:12:30 kanga kernel: [<c8842020>] __insmod_wd_S.bss_L1376 [wd] 0x20 Mar 6 05:12:30 kanga kernel: [net_tx_action+142/160] net_tx_action [kernel] 0x8e Mar 6 05:12:30 kanga kernel: [<c01c0e0e>] net_tx_action [kernel] 0x8e Mar 6 05:12:30 kanga kernel: [ext3:__insmod_ext3_S.bss_L1024+163840/116200300] __insmod_wd_S.bss_L1376 [wd] 0x20 Mar 6 05:12:31 kanga kernel: [<c8842020>] __insmod_wd_S.bss_L1376 [wd] 0x20 Mar 6 05:12:31 kanga kernel: [do_softirq+83/160] do_softirq [kernel] 0x53 Mar 6 05:12:31 kanga kernel: [<c0119763>] do_softirq [kernel] 0x53 Mar 6 05:12:31 kanga kernel: [do_IRQ+156/176] do_IRQ [kernel] 0x9c Mar 6 05:12:31 kanga kernel: [<c01084cc>] do_IRQ [kernel] 0x9c Mar 6 05:12:31 kanga kernel: [call_do_IRQ+5/17] call_do_IRQ [kernel] 0x5 Mar 6 05:12:31 kanga kernel: [<c0211c54>] call_do_IRQ [kernel] 0x5 Mar 6 05:12:31 kanga kernel: [schedule+622/960] schedule [kernel] 0x26e Mar 6 05:12:31 kanga kernel: [<c011319e>] schedule [kernel] 0x26e Mar 6 05:12:31 kanga kernel: [wd:__insmod_wd_O/lib/modules/2.4.9-21/kernel/drivers/net/wd.o_+-246213/96] journal_revoke_R088e3507 [jbd] 0x5eb Mar 6 05:12:31 kanga kernel: [<c8804e3b>] journal_revoke_R088e3507 [jbd] 0x5eb Mar 6 05:12:31 kanga kernel: [wd:__insmod_wd_O/lib/modules/2.4.9-21/kernel/drivers/net/wd.o_+-246512/96] journal_revoke_R088e3507 [jbd] 0x4c0 Mar 6 05:12:32 kanga kernel: [<c8804d10>] journal_revoke_R088e3507 [jbd] 0x4c0 Mar 6 05:12:32 kanga kernel: [kernel_thread+38/48] kernel_thread [kernel] 0x26 Mar 6 05:12:32 kanga kernel: [<c0105726>] kernel_thread [kernel] 0x26 Mar 6 05:12:32 kanga kernel: [wd:__insmod_wd_O/lib/modules/2.4.9-21/kernel/drivers/net/wd.o_+-246480/96] journal_revoke_R088e3507 [jbd] 0x4e0 Mar 6 05:12:32 kanga kernel: [<c8804d30>] journal_revoke_R088e3507 [jbd] 0x4e0 Mar 6 05:12:32 kanga kernel: Mar 6 05:12:32 kanga kernel: Mar 6 05:12:32 kanga kernel: Code: 0f 0b 59 58 eb 04 89 f6 89 c3 89 d8 5b c3 8d 76 00 8d bc 27 I did not notice the problem until late afternoon but nothing was in the logs. The machine was still running but I was unable to shut it down cleanly. It hung trying to kill nfs. After rebooting and an fsck all seems ok. The machine was up about 10 days and it is now running 2.4.9-31. Can someone tell me what this means? -- ......Tom CLUELESSNESS: There Are No Stupid Questions, But tdiehl@rogueind.com There Are LOTS of Inquisitive Idiots. :-)
