Re: ext2 fs corruption and usb devices

Pierre Rousselet (pierre.rousselet@wanadoo.fr)
Mon, 28 Jan 2002 18:34:56 +0100


Zwane Mwaikambo wrote:
>> Warning (Oops_read): Code line not seen, dumping what data is
>> available
>>
>
> You need to get the whole oops output...

Where have you seen it's an oops. have you read my message ?

>
>>>> EIP; c0140754 <inode_change_ok+24/128> <=====
>>>>
>> Trace; d08b959c <[speedtch]udsl_usb_driver+1c/40> Trace; d089ea1c
>> <[usbcore]free_inode+7c/84> Trace; d089f870
>> <[usbcore]usbdevfs_remove_device+30/d8>
>>
>
> Isn't that a proprietory driver you have there? Who knows what lurks
> in the inner depths of that cruft, i'd ask you to reproduce it
> without loading that driver, but then that would be pointless for
> your situation. I suggest you take it up with Alcatel...

Why? The problem is solved by the diff in ext2 code in 2.4.18-pre7
(have you read my message ?)

What i would like to know is why the corruption of the ext2 root fs with
2.4.18-pre6 in only visible by the usb drivers. is it pure chance ?

Pierre

-- 
------------------------------------------------
  Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/