From: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext2 fs corruption and usb devices
Date: Mon, 28 Jan 2002 18:34:56 +0100 [thread overview]
Message-ID: <3C558BC0.5050700@wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.44.0201281631110.20095-100000@netfinity.realnet.co.sz>
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>
------------------------------------------------
next prev parent reply other threads:[~2002-01-28 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 14:34 ext2 fs corruption and usb devices Zwane Mwaikambo
2002-01-28 17:34 ` Pierre Rousselet [this message]
2002-01-29 6:37 ` Zwane Mwaikambo
2002-01-29 12:13 ` Pierre Rousselet
2002-01-29 14:20 ` Zwane Mwaikambo
2002-01-29 14:34 ` Duncan Sands
-- strict thread matches above, loose matches on Subject: below --
2002-01-27 15:48 Pierre Rousselet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C558BC0.5050700@wanadoo.fr \
--to=pierre.rousselet@wanadoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox