From owner-freebsd-usb@FreeBSD.ORG Wed Dec 23 15:30:04 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D05A106568B for ; Wed, 23 Dec 2009 15:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 73DB38FC1A for ; Wed, 23 Dec 2009 15:30:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBNFU48J061239 for ; Wed, 23 Dec 2009 15:30:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBNFU4j8061233; Wed, 23 Dec 2009 15:30:04 GMT (envelope-from gnats) Date: Wed, 23 Dec 2009 15:30:04 GMT Message-Id: <200912231530.nBNFU4j8061233@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Hans Petter Selasky Cc: Subject: Re: usb/141918: ehci_interrupt: unrecoverable error, controller halted (sparc64) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hans Petter Selasky List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2009 15:30:04 -0000 The following reply was made to PR usb/141918; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org, Andrew Belashov Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: usb/141918: ehci_interrupt: unrecoverable error, controller halted (sparc64) Date: Wed, 23 Dec 2009 16:25:53 +0100 On Wednesday 23 December 2009 12:15:42 Andrew Belashov wrote: > >Number: 141918 > >Category: usb > >Synopsis: ehci_interrupt: unrecoverable error, controller halted > > (sparc64) Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Dec 23 11:40:01 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Andrew Belashov > >Release: FreeBSD 8.0-RELEASE sparc64 > >Organization: > > CT > > >Environment: > > System: FreeBSD bel.localdomain 8.0-RELEASE FreeBSD 8.0-RELEASE #3: Wed Dec > 2 00:54:28 MSK 2009 bel@bel.localdomain:/usr/obj/usr/src/sys/SUNC3D sparc64 > > Hardware: Sun Microsystems ULTRA 60 > > >Description: > > After upgrading from FreeBSD 7.2-RELEASE to 8.0-RELEASE there were > problems with USB. Attempt to mount flash drive leads to an error in USB > EHCI driver. Here are the kernel messages: > > ehci_interrupt: unrecoverable error, controller halted > cmd=0x00010020 > EHCI_CMD_ITC_1 > EHCI_CMD_ASE > sts=0x0000b000 > EHCI_STS_ASS > EHCI_STS_REC > EHCI_STS_HCH > ien=0x00000037 > frindex=0x0000169e ctrdsegm=0x00000000 periodic=0xfee30000 async=0xfee35600 > port 1 status=0x00001000 > port 2 status=0x00001000 > port 3 status=0x00001005 > port 4 status=0x00003400 > ehci_dump_isoc: isochronous dump from frame 0x053: > ITD(0xfffff800813a3900) at 0xff185900 > next=0xff384204 > status[0]=0x00000000; <> > status[1]=0x00000000; <> > status[2]=0x00000000; <> > status[3]=0x00000000; <> > status[4]=0x00000000; <> > status[5]=0x00000000; <> > status[6]=0x00000000; <> > status[7]=0x00000000; <> > bp[0]=0x00000000 > addr=0x00; endpt=0x0 > bp[1]=0x00000000 > dir=out; mpl=0x00 > bp[2..6]=0x00000000,0x00000000,0x00000000,0x00000000,0x00000000 > bp_hi=0x00000000,0x00000000,0x00000000,0x00000000, > 0x00000000,0x00000000,0x00000000 > SITD(0xfffff800813b4200) at 0xff384200 > next=0xfef85502 > portaddr=0x00000000 dir=out addr=0 endpt=0x0 port=0x0 huba=0x0 > mask=0x00000000 > status=0x00000000 <> len=0x0 > back=0x00000001, bp=0x00000000,0x00000000,0x00000000,0x00000000 > ehci_interrupt: blocking interrupts 0x10 > > Full dmesg: > http://orel.ru/~bel/usb/dmesg.txt > > Kernel config: > http://orel.ru/~bel/usb/SUNC3D.txt > > >How-To-Repeat: > > Insert USB Flash drive and try to mount it for read-write. > Hi, My guess for this issue is that the cache invalidate and cache flush instructions are not properly implemented by busdma on your platform. Please check that first. --HPS