Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 Jul 2005 15:53:47 +0200
From:      Hans Petter Selasky <hselasky@c2i.net>
To:        Stefan Walter <sw@gegenunendlich.de>
Cc:        freebsd-usb@freebsd.org
Subject:   Re: usb/82660: EHCI: I/O stuck in state 'physrd'/panic
Message-ID:  <200507021553.49043.hselasky@c2i.net>
In-Reply-To: <20050701114207.GA826@kyuzo.dunkelkammer.void>
References:  <20050626091628.775DD3A1D@kyuzo.dunkelkammer.void> <200507011210.25250.hselasky@c2i.net> <20050701114207.GA826@kyuzo.dunkelkammer.void>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 01 July 2005 13:42, Stefan Walter wrote:
> Hans Petter Selasky, 01.07.05, 12:10h CEST:
> > Could you try to reproduce the error while logging?
>
> OK, seems like it did behave differently this time - after I pulled out, I
> didn't get the "umass0: CAM poll" messages. This time's output is here
> (again, the mtools process got stuck in state 'physrd'):
>
> http://www.gegenunendlich.de/stuff/messages-umass-until-pullout.bz2
> http://www.gegenunendlich.de/stuff/messages-umass-after-pullout.diff

The end of the log is just before you pulled out your device, when the error 
happened, right?

I'm not sure what is wrong. From what I can see the problem is in an upper 
layer, hence UMASS's USB transfers should timeout at least, if they get 
stuck. While having [umass] debugging enabled, could you have tried playing 
around with "camcontrol" and see if it changes anything:

man camcontrol
camcontrol devlist
camcontrol reset scbus0:0:0 

# replace "0:0" with "target" and "lun" for the device you are reading from

Could you have tried another brand of USB 2.0 flash disks and see if the 
problem is the same?

--HPS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507021553.49043.hselasky>