All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Christopher Monty Montgomery <xiphmont@gmail.com>,
	Paolo Ornati <ornati@fastwebnet.it>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] 2.6.19-rc1-mm1 - locks when using "dd bs=1M" from card reader
Date: Mon, 23 Oct 2006 11:12:30 +0200	[thread overview]
Message-ID: <453C877E.6090002@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0610201133110.7060-100000@iolanthe.rowland.org>

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


  reply	other threads:[~2006-10-23  9:16 UTC|newest]

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10  7:09 2.6.19-rc1-mm1 Andrew Morton
2006-10-10  7:20 ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-10  7:45   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10  7:45     ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10  8:03     ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-10  8:03       ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-10 13:14       ` RSS accounting (was: Re: 2.6.19-rc1-mm1) Peter Zijlstra
2006-10-10 13:14         ` Peter Zijlstra
2006-10-10 16:13         ` Arjan van de Ven
2006-10-10 16:13           ` Arjan van de Ven
2006-10-10 23:54           ` Eric W. Biederman
2006-10-10 23:54             ` Eric W. Biederman
2006-10-11  8:47             ` Arjan van de Ven
2006-10-11  8:47               ` Arjan van de Ven
2006-10-11 12:07               ` Eric W. Biederman
2006-10-11 12:07                 ` Eric W. Biederman
2006-10-11 13:55                 ` Arjan van de Ven
2006-10-11 13:55                   ` Arjan van de Ven
2006-10-11 17:15                   ` Chen, Kenneth W
2006-10-11 17:15                     ` Chen, Kenneth W
2006-10-11 22:36                     ` Benjamin LaHaise
2006-10-11 22:36                       ` Benjamin LaHaise
2006-10-10  7:31 ` 2.6.19-rc1-mm1 Miguel Ojeda
2006-10-10  8:10   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10  9:57     ` 2.6.19-rc1-mm1 Miguel Ojeda
2006-10-10 18:25       ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 12:19 ` 2.6.19-rc1-mm1 Theodore Tso
2006-10-10 12:26   ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-10 16:21   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 13:10 ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-10 14:04   ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-11  5:35     ` 2.6.19-rc1-mm1 Neil Brown
2006-10-11 10:48       ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-11 11:23         ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-11 13:08           ` _cpu_down deadlock [was Re: 2.6.19-rc1-mm1] Neil Brown
2006-10-11 13:32             ` Rusty Russell
2006-10-11 16:39             ` Andrew Morton
2006-10-11 23:46               ` Neil Brown
2006-10-12  6:51                 ` Arjan van de Ven
2006-10-12  7:53                   ` SPAM: " Neil Brown
2006-10-12  8:04                     ` Andrew Morton
2006-10-13  4:49                       ` Neil Brown
2006-10-10 15:47 ` BUG in filp_close() (was: Re: 2.6.19-rc1-mm1) Dave Kleikamp
2006-10-10 22:07   ` Dave Kleikamp
2006-10-10 22:14     ` Vadim Lobanov
2006-10-10 22:38     ` Vadim Lobanov
2006-10-10 16:09 ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-10 19:04   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 21:44     ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-10 21:52       ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-20 20:44         ` 2.6.19-rc1-mm1 Thomas Gleixner
2006-10-10 17:15 ` BUG() in copy_fdtable() with 64K pages (2.6.19-rc1-mm1) Olof Johansson
2006-10-10 17:15   ` Olof Johansson
2006-10-10 19:34   ` Andrew Morton
2006-10-10 19:34     ` Andrew Morton
2006-10-10 20:20   ` Linas Vepstas
2006-10-10 20:31     ` Vadim Lobanov
2006-10-10 20:31       ` Vadim Lobanov
2006-10-10 23:05       ` Linas Vepstas
2006-10-10 23:05         ` Linas Vepstas
2006-10-10 18:09 ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 19:25   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 19:41     ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 23:10     ` 2.6.19-rc1-mm1 Paul Mackerras
2006-10-10 23:16       ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 23:37       ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 22:17 ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-11  6:56   ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-11  3:13 ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-11  4:01   ` 2.6.19-rc1-mm1 Andrew Morton
     [not found]     ` <1160578934.1447.1.camel@dyn9047017100.beaverton.ibm.com>
2006-10-11 16:56       ` 2.6.19-rc1-mm1 (ext4 problem ?) Andrew Morton
2006-10-11 17:08         ` Badari Pulavarty
2006-10-11 12:51   ` 2.6.19-rc1-mm1 Theodore Tso
2006-10-11 19:54 ` 2.6.19-rc1-mm1 Martin J. Bligh
2006-10-11 21:58   ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-16 15:56     ` 2.6.19-rc1-mm1 Andy Whitcroft
2006-10-11 19:59 ` 2.6.19-rc1-mm1 Martin J. Bligh
2006-10-11 20:10   ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-11 21:47   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-12 10:22     ` 2.6.19-rc1-mm1 Andy Whitcroft
2006-10-12 18:09     ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-12 18:52       ` 2.6.19-rc1-mm1 Vadim Lobanov
2006-10-12 19:01         ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-11 21:19 ` 2.6.19-rc1-mm1 Michael Lothian
2006-10-12 12:18 ` 2.6.19-rc1-mm1 - locks when using "dd bs=1M" from card reader Helge Hafting
2006-10-12 18:29   ` Andrew Morton
2006-10-13 13:11     ` Helge Hafting
2006-10-13 16:29       ` Andrew Morton
2006-10-13 18:10         ` [linux-usb-devel] " Alan Stern
2006-10-18  9:31           ` Helge Hafting
2006-10-18 16:26             ` Alan Stern
2006-10-19 12:25               ` Helge Hafting
2006-10-19 18:40                 ` Alan Stern
2006-10-19 18:57                   ` Christopher "Monty" Montgomery
2006-10-20 11:44                   ` Helge Hafting
2006-10-20 15:55                     ` Alan Stern
2006-10-23  9:12                       ` Helge Hafting [this message]
2006-10-23 14:13                         ` Alan Stern
2006-10-23 20:36                       ` Christopher "Monty" Montgomery
2006-10-24 10:16                         ` Helge Hafting
2006-10-24 14:09                           ` Alan Stern
2006-10-12 18:37 ` 2.6.19-rc1-mm1 Valdis.Kletnieks

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=453C877E.6090002@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=ornati@fastwebnet.it \
    --cc=stern@rowland.harvard.edu \
    --cc=xiphmont@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.