From owner-freebsd-usb@FreeBSD.ORG Thu Jun 30 12:07:26 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 EC32A16A41C for ; Thu, 30 Jun 2005 12:07:26 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8246743D4C for ; Thu, 30 Jun 2005 12:07:26 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== Received: from mp-217-209-38.daxnet.no ([193.217.209.38] verified) by mailfe03.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 213002183; Thu, 30 Jun 2005 14:07:24 +0200 From: Hans Petter Selasky To: Stefan Walter Date: Thu, 30 Jun 2005 14:08:18 +0200 User-Agent: KMail/1.7 References: <20050626091628.775DD3A1D@kyuzo.dunkelkammer.void> <200506291225.36375.hselasky@c2i.net> <20050629135802.GA976@kyuzo.dunkelkammer.void> In-Reply-To: <20050629135802.GA976@kyuzo.dunkelkammer.void> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506301408.20619.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: Thu, 30 Jun 2005 12:07:27 -0000 On Wednesday 29 June 2005 15:58, Stefan Walter wrote: > [Cc'd usb@, maybe someone else wants to comment on this, too.] > > Hans Petter Selasky, 29.06.05, 12:25h CEST: > > On Tuesday 28 June 2005 19:23, you wrote: > > > Hi, > > > > > > Hans Petter Selasky, 26.06.05, 14:15h CEST: > > > > I know there is bug related to the alignments of hardware structures > > > > in the existing EHCI driver. The EHCI driver works with generic intel > > > > chips, but not others. > > > > > > > > Could you have tried my USB driver and see if the problem is the > > > > same? > > > > > > I tried your driver today, but unfortunately the same thing happened: > > > I/O got stuck after reading a few KBytes. > > > > OK, then your problem is most likely inside /sys/dev/usb/umass.c. > > > > Try "sysctl hw.usb.umass.debug=15" while you have the my driver in the > > kernel, hence it has got debugging flags enabled by default. Else you > > need to add something like "option USB_DEBUG" to your kernel config file. > > I'm not sure if you can compile the modules with debugging support unless > > you use my USB driver. > > > > See if any errors show up. > > > > Then try "sysctl hw.usb.debug=15". See if any errors appear. > > I tried that with the official FreeBSD driver for now (USB_DEBUG and ehci > in the kernel). > > hw.usb.umass.debug=15 didn't show me any messages during the transfer, > only when (dis)connecting the device. hw.usb.debug=15 dumped a lot of > output. It's available here: Try "sysctl hw.usb.umass.debug=-1" while "hw.usb.debug=0". You should get some error messages, hence your logs show that transfers are failing: Jun 29 15:26:58 kyuzo kernel: usb_transfer_complete: pipe=0xc2068d00 xfer=0xc215a300 status=17 actlen=0 (STALL) This can indicate that EHCI got the data toggle wrong. Jun 29 15:28:43 kyuzo kernel: usb_transfer_complete: pipe=0xc2068d00 xfer=0xc215a300 status=15 actlen=0 (TIMEOUT) If you are loading umass as a module, you need to add #ifndef USB_DEBUG #define USB_DEBUG #endif before #ifdef USB_DEBUG in the file /sys/dev/usb/umass.c, and then recompile and install the module: make -C/sys/modules/umass depend all install clean You might also want to add: #undef DIF #define DIF(args...) after the ifdef/endif USB_DEBUG, to limit the debugging output, if there is too much dmsg. > > I haven't tried the same with your driver, yet - would that bring more > info? You will get something similar. --HPS