From owner-freebsd-usb@FreeBSD.ORG Sat Jul 2 13:53:01 2005 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48BDB16A41C for ; Sat, 2 Jul 2005 13:53:01 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.swip.net [212.247.155.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D780D43D1F for ; Sat, 2 Jul 2005 13:53:00 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== Received: from 217-231-18.511210.adsl.tele2.no ([193.217.231.18] verified) by mailfe09.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 193107979; Sat, 02 Jul 2005 15:52:58 +0200 From: Hans Petter Selasky To: Stefan Walter Date: Sat, 2 Jul 2005 15:53:47 +0200 User-Agent: KMail/1.7 References: <20050626091628.775DD3A1D@kyuzo.dunkelkammer.void> <200507011210.25250.hselasky@c2i.net> <20050701114207.GA826@kyuzo.dunkelkammer.void> In-Reply-To: <20050701114207.GA826@kyuzo.dunkelkammer.void> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507021553.49043.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: usb/82660: EHCI: I/O stuck in state 'physrd'/panic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2005 13:53:01 -0000 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