(Illustration by Gaich Muramatsu)
On Wed, Jan 16, 2002 at 03:16:57PM +1000, Vaughan Clarkson wrote: > Jan 16 14:20:53 point kernel: Call Trace: > [usbcore:__insmod_usbcore_S.bss_L96+37993966/173825234] [sys_write+150/208] > [sys_open+125/176] [system_call+51/56] > Jan 16 14:20:53 point kernel: Call Trace: [<d2ca878e>] [<c01355e6>] > [<c013504d>] [<c0106f0b>] > Jan 16 14:20:53 point kernel: > Jan 16 14:20:53 point kernel: Code: 0f 0b 5e 58 8b 43 08 8b 70 08 8d 5e 60 > 89 d9 ff 4e 60 0f 88 > > Why this manifests itself in usbcore is beyond my feeble skills in Linux > kernel oops divination. Has anyone else noticed this problem? Should > it be registered properly as a bug? Is there yet a solution? (I don't > seem to be able to take Sujal's option of uninstalling a patch --- > unless I uninstall RH 7.2!) That's because the oops decoder in klogd isn't that great and has problems with modules. If you'd run the oops through ksymoops it should show that the bug is coming from Coda. To fix this, you simply need to apply the RedHat 7.2 security patches, amongst which is a more recent kernel (2.4.9 I believe) that has a fix that makes Coda work nicely on top of pretty much any filesystem including ext3. JanReceived on 2002-01-16 11:05:55