[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <453C877E.6090002@aitel.hist.no>
Date: Mon, 23 Oct 2006 11:12:30 +0200
From: Helge Hafting <helge.hafting@...el.hist.no>
To: Alan Stern <stern@...land.harvard.edu>
CC: Christopher Monty Montgomery <xiphmont@...il.com>,
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
Alan Stern wrote:
>>> You could try putting a printk() just before the BUG() to display the
>>> values of ehci->reclaim and qh->qh_state. Maybe also change the BUG() to
>>>
>>>
>> ehci->reclaim=0
>> qh->qh_state=5
>>
>
> 5 is QH_STATE_COMPLETING. That explains why the BUG() fires.
>
> At this point it's beyond me. Monty will have to take it from here.
>
>
>> During boot I get lots of those "Hardware error, end-of-data detected"
>> messages, but I've never seen it crash during bootup.
>>
>
> Those messages are from the card reader. It doesn't seem to be working
> right. It returns the "end-of-data" error in response to a PREVENT MEDIUM
> REMOVAL command
Unlike a cdrom, it doesn't have the means to prevent media removal. :-)
> and it returns a phase error in response to a READ
> command. In spite of the fact that it claims to have a 256 MB card
> present.
>
It has slots for several different cards, all the other
slots are empty.
Perhaps it is broken, but interesting as a "stress-test".
Linux should not crash because of a bad usb thing, just complain.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists