[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <453DE80E.8090607@aitel.hist.no>
Date: Tue, 24 Oct 2006 12:16:46 +0200
From: Helge Hafting <helge.hafting@...el.hist.no>
To: "Christopher \"Monty\" Montgomery" <xiphmont@...il.com>
CC: Alan Stern <stern@...land.harvard.edu>,
Paolo Ornati <ornati@...twebnet.it>,
Kernel development list <linux-kernel@...r.kernel.org>,
USB development list <linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] 2.6.19-rc1-mm1 - locks when using "dd bs=1M"
from card reader
Christopher "Monty" Montgomery wrote:
> On 10/20/06, Alan Stern <stern@...land.harvard.edu> wrote:
>> At this point it's beyond me. Monty will have to take it from here.
>
> I will look more closely at what might have changed there. Despite
> the code refactoring (and a hand-resolved patch collision at that
> point) the async disable handling *should* have been functionally
> unchanged from 2.6.18. I will revisit that closely.
>
> Has it actually been demonstrated that this does not crash 2.6.18
> (pre-my-patches) kernels?
I just tested this. 2.6.18 does not crash. I still get tons of errors,
and no data. Copying using 1MB chunks or 4kB chunks
don't matter, it doesn't work. So card, reader or driver must be faulty.
The card works in a windows machine though.
2.6.19-rc1 gets data with 4kB chunks, and BUGs with 1M chunks.
> If it crashes earlier, that doesn't mean
> I'm uninterested in fixing it, I just want to know. I don't think
> that had been explicitly answered earlier in the thread.
2.6.18 wasn't tried before, the reason being I did not have this
card reader when 2.6.18 was current.
dmesg output for 2.6.18 (after the dd attempts) is attached. I have
edited out stuff that isn't usb or scsi.
Helge Hafting
Download attachment "dmesg3.gz" of type "application/gzip" (3387 bytes)
Powered by blists - more mailing lists