From owner-freebsd-usb@FreeBSD.ORG Sun Dec 19 02:52:01 2004 Return-Path: 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 9BB3F16A4CE for ; Sun, 19 Dec 2004 02:52:01 +0000 (GMT) Received: from wattres.watt.com (wattres.watt.com [66.93.133.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6524743D1D for ; Sun, 19 Dec 2004 02:52:01 +0000 (GMT) (envelope-from steve@Watt.COM) Received: from wattres.watt.com (localhost.watt.com [127.0.0.1]) by wattres.watt.com (8.13.1/8.13.1) with ESMTP id iBJ2q1Ob002381 for ; Sat, 18 Dec 2004 18:52:01 -0800 (PST) (envelope-from steve@wattres.watt.com) Received: (from steve@localhost) by wattres.watt.com (8.13.1/8.13.1/Submit) id iBJ2q1eW002380 for freebsd-usb@freebsd.org; Sat, 18 Dec 2004 18:52:01 -0800 (PST) (envelope-from steve) Message-Id: <200412190252.iBJ2q1eW002380@wattres.watt.com> From: steve@Watt.COM (Steve Watt) Date: Sat, 18 Dec 2004 18:52:01 -0800 X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: freebsd-usb@freebsd.org X-Archived: 1103424721.307452951@wattres.Watt.COM Subject: panic w/ USB<->serial adapter and modem X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 02:52:01 -0000 I've got a 5.3-STABLE (updated 19 Nov around 2000PST) machine that has serious difficulty when I attempt to use the modems that are attached via the Prolofic Technology PL2303 serial adapters. It seems that the kernel panics when carrier drops, during the general TTY cleanup. Here's a hand-transcribed trace from the one I saw this afternoon. Note that I didn't bother writing down all of the addresses in all of the functions, those are listed as "...". I include the line number and source line from GDB (ex-post-facto) as well. Some of the latter is guessing, since it wasn't a debug kernel. - - - 8< - - - hand-entered off my scribbled notes - - - panic: uhci_abort_xfer: not in process context KDB: enter: panic [ thread 100027 ] kdb> trace kdb_enter(...) panic(...) at panic + 0xce uhci_abort_xfer(c19f8b00,6,caca1b80,c05f328f,c19f8b00) at uhci_abort_xfer + 0x8b 1954 if (xfer->device->bus->intr_context || !curproc) 1955 panic("uhci_abort_xfer: not in process context"); uhci_device_bulk_abort(...) at uhci_device_bulk_abort + 0x19 1919 uhci_abort_xfer(xfer, USBD_CANCELLED); usbd_ar_pipe(...) at usbd_ar_pipe + 0x22 747 /* Make the HC abort it (and invoke the callback). */ 748 pipe->methods->abort(xfer); usbd_abort_pipe(..) at usbd_abort_pipe + 0x11 547 s = splusb(); 548 err = usbd_ar_pipe(pipe); ucomstopread(c156ad00,1,c1559e00,3,caca1bc8) at ucomstopread+0x28 1156 err = usbd_abort_pipe(sc->sc_bulkin_pipe); ucomstop(...) at ucomstop+0x44 933 DPRINTF(("ucomstop: read\n")); 934 ucomstopread(sc); ttyflush(c1559e00,3,0,1,5) at ttyflush+0x43 1420 (*tp->t_stop)(tp, rw); ttymodem(...) at ttymodem+0x194 1614 ttyflush(tp, FREAD | FWRITE); ucom_status_change(c156ad00,caca1c4c,...) at ucom_status_change+0x73 759 ttyld_modem(tp, onoff); uplcom_intr(c19f9900,c156ad00,0,0,1) at uplcom_intr+0x69 805 ucom_status_change(&sc->sc_ucom); usb_transfer_complete(c19f9900,0,caca1cbc,a,c26cc00) at usb_transfer_complete+0x135 845 pipe->methods->done(xfer); uhci_idone(c19f996c,0) at uhci_idone+0x11d 1497 end: 1498 usb_transfer_complete(xfer); uhci_check_intr(c1595000,...) at uhci_check_intr+0x93 1372 usb_uncallout(ii->xfer->timeout_handle, uhci_timeout, ii); 1373 uhci_idone(ii); uhci_softintr(c1595000,...) at uhci_softintr+0x2b 1303 LIST_FOREACH_SAFE(ii, &sc->sc_intrhead, list, nextii) 1304 uhci_check_intr(sc, ii); usb_schedsoftintr(c1595000,7058c,c15a0040,4,c146b380) at usb_schedsoftintr+0x12 859 bus->methods->soft_intr(bus); uhci_intr1(c1595000,...) at uhci_intr1+0x18c 1274 usb_schedsoftintr(&sc->sc_bus); uhci_intr(c1595000,0,0,0,0) at uhci_intr+0x2e 1189 return (uhci_intr1(sc)); ithread_loop(...)... fork_exit(...)... fork_trampoline(...)... - - - >8 - - - hand-entered off my scribbled notes - - - So it's pretty clear, reading that over, that uhci_abort_xfer *IS* being called from interrupt context, namely when carrier drops. There's some kind of think-o happening in there, but I'm not sure quite what to do about it. It also looks like there's some risk of ugly recursion, because usb_transfer_complete is called from uhci_abort_xfer, but I really haven't analyzed the code path well enough to be certain that it's OK. My kernel config is pretty much GENERIC, and usbdevs -v looks like: Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 port 1 addr 2: full speed, self powered, config 1, Generic USB Hub(0x9254), ALCOR(0x058f), rev 3.12 port 1 addr 3: full speed, power 500 mA, config 1, PL2303 Serial adapter (ATEN/IOGEAR UC232A)(0x2303), Prolific Technology(0x067b), rev 2.02 port 2 addr 4: full speed, power 500 mA, config 1, PL2303 Serial adapter (ATEN/IOGEAR UC232A)(0x2303), Prolific Technology(0x067b), rev 2.02 port 3 addr 5: full speed, power 500 mA, config 1, PL2303 Serial adapter (ATEN/IOGEAR UC232A)(0x2303), Prolific Technology(0x067b), rev 2.02 port 4 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 port 1 powered port 2 powered -- Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.8" / 37N 20' 14.9" Internet: steve @ Watt.COM Whois: SW32 Free time? There's no such thing. It just comes in varying prices... From owner-freebsd-usb@FreeBSD.ORG Sun Dec 19 21:46:21 2004 Return-Path: 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 292F616A4CE for ; Sun, 19 Dec 2004 21:46:21 +0000 (GMT) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4DC943D2F for ; Sun, 19 Dec 2004 21:46:20 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-216-100-134-143.dsl.snfc21.pacbell.net [216.100.134.143])iBJLkENb329926; Sun, 19 Dec 2004 16:46:19 -0500 Message-ID: <41C5F6A5.5000906@elischer.org> Date: Sun, 19 Dec 2004 13:46:13 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: Steve Watt References: <200412190252.iBJ2q1eW002380@wattres.watt.com> In-Reply-To: <200412190252.iBJ2q1eW002380@wattres.watt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: panic w/ USB<->serial adapter and modem X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 21:46:21 -0000 Steve Watt wrote: > I've got a 5.3-STABLE (updated 19 Nov around 2000PST) machine that > has serious difficulty when I attempt to use the modems that are > attached via the Prolofic Technology PL2303 serial adapters. It > seems that the kernel panics when carrier drops, during the general > TTY cleanup. > > Here's a hand-transcribed trace from the one I saw this afternoon. > Note that I didn't bother writing down all of the addresses in > all of the functions, those are listed as "...". I include the > line number and source line from GDB (ex-post-facto) as well. > Some of the latter is guessing, since it wasn't a debug kernel. > > - - - 8< - - - hand-entered off my scribbled notes - - - This may be fixed in the ongoing 5 branch after 5.3 (and teh 6 branch (-current)) and in the newest 4.x too i think. There were problems in the abort code that have been fixed.. this may relate to your problem. > > panic: uhci_abort_xfer: not in process context > KDB: enter: panic > [ thread 100027 ] > kdb> trace > kdb_enter(...) > panic(...) at panic + 0xce > uhci_abort_xfer(c19f8b00,6,caca1b80,c05f328f,c19f8b00) at uhci_abort_xfer + 0x8b > 1954 if (xfer->device->bus->intr_context || !curproc) > 1955 panic("uhci_abort_xfer: not in process context"); > uhci_device_bulk_abort(...) at uhci_device_bulk_abort + 0x19 > 1919 uhci_abort_xfer(xfer, USBD_CANCELLED); > usbd_ar_pipe(...) at usbd_ar_pipe + 0x22 > 747 /* Make the HC abort it (and invoke the callback). */ > 748 pipe->methods->abort(xfer); > usbd_abort_pipe(..) at usbd_abort_pipe + 0x11 > 547 s = splusb(); > 548 err = usbd_ar_pipe(pipe); > ucomstopread(c156ad00,1,c1559e00,3,caca1bc8) at ucomstopread+0x28 > 1156 err = usbd_abort_pipe(sc->sc_bulkin_pipe); > ucomstop(...) at ucomstop+0x44 > 933 DPRINTF(("ucomstop: read\n")); > 934 ucomstopread(sc); > ttyflush(c1559e00,3,0,1,5) at ttyflush+0x43 > 1420 (*tp->t_stop)(tp, rw); > ttymodem(...) at ttymodem+0x194 > 1614 ttyflush(tp, FREAD | FWRITE); > ucom_status_change(c156ad00,caca1c4c,...) at ucom_status_change+0x73 > 759 ttyld_modem(tp, onoff); > uplcom_intr(c19f9900,c156ad00,0,0,1) at uplcom_intr+0x69 > 805 ucom_status_change(&sc->sc_ucom); > usb_transfer_complete(c19f9900,0,caca1cbc,a,c26cc00) at usb_transfer_complete+0x135 > 845 pipe->methods->done(xfer); > uhci_idone(c19f996c,0) at uhci_idone+0x11d > 1497 end: > 1498 usb_transfer_complete(xfer); > uhci_check_intr(c1595000,...) at uhci_check_intr+0x93 > 1372 usb_uncallout(ii->xfer->timeout_handle, uhci_timeout, ii); > 1373 uhci_idone(ii); > uhci_softintr(c1595000,...) at uhci_softintr+0x2b > 1303 LIST_FOREACH_SAFE(ii, &sc->sc_intrhead, list, nextii) > 1304 uhci_check_intr(sc, ii); > usb_schedsoftintr(c1595000,7058c,c15a0040,4,c146b380) at usb_schedsoftintr+0x12 > 859 bus->methods->soft_intr(bus); > uhci_intr1(c1595000,...) at uhci_intr1+0x18c > 1274 usb_schedsoftintr(&sc->sc_bus); > uhci_intr(c1595000,0,0,0,0) at uhci_intr+0x2e > 1189 return (uhci_intr1(sc)); > ithread_loop(...)... > fork_exit(...)... > fork_trampoline(...)... > > - - - >8 - - - hand-entered off my scribbled notes - - - > > So it's pretty clear, reading that over, that uhci_abort_xfer > *IS* being called from interrupt context, namely when carrier > drops. There's some kind of think-o happening in there, but > I'm not sure quite what to do about it. > > It also looks like there's some risk of ugly recursion, because > usb_transfer_complete is called from uhci_abort_xfer, but I really > haven't analyzed the code path well enough to be certain that > it's OK. > > My kernel config is pretty much GENERIC, and usbdevs -v looks > like: > > Controller /dev/usb0: > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 > port 1 powered > port 2 powered > Controller /dev/usb1: > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 > port 1 addr 2: full speed, self powered, config 1, Generic USB Hub(0x9254), ALCOR(0x058f), rev 3.12 > port 1 addr 3: full speed, power 500 mA, config 1, PL2303 Serial adapter (ATEN/IOGEAR UC232A)(0x2303), Prolific Technology(0x067b), rev 2.02 > port 2 addr 4: full speed, power 500 mA, config 1, PL2303 Serial adapter (ATEN/IOGEAR UC232A)(0x2303), Prolific Technology(0x067b), rev 2.02 > port 3 addr 5: full speed, power 500 mA, config 1, PL2303 Serial adapter (ATEN/IOGEAR UC232A)(0x2303), Prolific Technology(0x067b), rev 2.02 > port 4 powered > port 2 powered > Controller /dev/usb2: > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 > port 1 powered > port 2 powered > > > From owner-freebsd-usb@FreeBSD.ORG Sun Dec 19 22:23:53 2004 Return-Path: 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 A8A7916A4CE for ; Sun, 19 Dec 2004 22:23:53 +0000 (GMT) Received: from wattres.watt.com (wattres.watt.com [66.93.133.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BA0343D39 for ; Sun, 19 Dec 2004 22:23:53 +0000 (GMT) (envelope-from steve@Watt.COM) Received: from wattres.watt.com (localhost.watt.com [127.0.0.1]) by wattres.watt.com (8.13.1/8.13.1) with ESMTP id iBJMNllh026094; Sun, 19 Dec 2004 14:23:47 -0800 (PST) (envelope-from steve@wattres.watt.com) Received: (from steve@localhost) by wattres.watt.com (8.13.1/8.13.1/Submit) id iBJMNlK3026093; Sun, 19 Dec 2004 14:23:47 -0800 (PST) (envelope-from steve) Message-Id: <200412192223.iBJMNlK3026093@wattres.watt.com> From: steve@Watt.COM (Steve Watt) Date: Sun, 19 Dec 2004 14:23:46 -0800 In-Reply-To: Julian Elischer "Re: panic w/ USB<->serial adapter and modem" (Dec 19, 13:46) X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Julian Elischer , Steve Watt X-Archived: 1103495027.183112813@wattres.Watt.COM cc: freebsd-usb@freebsd.org Subject: Re: panic w/ USB<->serial adapter and modem X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 22:23:53 -0000 On Dec 19, 13:46, Julian Elischer wrote: } Subject: Re: panic w/ USB<->serial adapter and modem } Steve Watt wrote: } > I've got a 5.3-STABLE (updated 19 Nov around 2000PST) machine that } > has serious difficulty when I attempt to use the modems that are } > attached via the Prolofic Technology PL2303 serial adapters. It } > seems that the kernel panics when carrier drops, during the general } > TTY cleanup. } > } > Here's a hand-transcribed trace from the one I saw this afternoon. } > Note that I didn't bother writing down all of the addresses in } > all of the functions, those are listed as "...". I include the } > line number and source line from GDB (ex-post-facto) as well. } > Some of the latter is guessing, since it wasn't a debug kernel. } > } > - - - 8< - - - hand-entered off my scribbled notes - - - } } This may be fixed in the ongoing 5 branch after 5.3 (and teh } 6 branch (-current)) and in the newest 4.x too i think. } There were problems in the abort code that have been fixed.. } this may relate to your problem. Do you know roughly when the fix went in? It's reproducable enough that I can just try it, though. Thanks, [ snip the trace ] -- Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.8" / 37N 20' 14.9" Internet: steve @ Watt.COM Whois: SW32 Free time? There's no such thing. It just comes in varying prices... From owner-freebsd-usb@FreeBSD.ORG Mon Dec 20 11:02:19 2004 Return-Path: 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 EBF3316A4DF for ; Mon, 20 Dec 2004 11:02:18 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B10E743D1F for ; Mon, 20 Dec 2004 11:02:18 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBKB2Ifc047199 for ; Mon, 20 Dec 2004 11:02:18 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBKB2Hdl047189 for freebsd-usb@freebsd.org; Mon, 20 Dec 2004 11:02:17 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 20 Dec 2004 11:02:17 GMT Message-Id: <200412201102.iBKB2Hdl047189@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-usb@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 11:02:19 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/05/04] kern/66248 usb [panic] bootloader is confused by booting 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2001/09/11] kern/30502 usb panics if logitech joystick usb attached a [2001/10/31] kern/31659 usb USB controller driver will die after some f [2001/12/12] kern/32713 usb [usb] mouse detaches from hub and doesnt f [2002/01/13] kern/33839 usb usb0: host controller halted (involving A f [2002/02/17] kern/35061 usb After printing to HP Deskjet 656c USB pri f [2002/04/07] i386/36850 usb Page Fault using ppp with USB Modem [4.9] f [2002/05/30] kern/38736 usb kernel panic during memory stick removal f [2002/06/15] kern/39341 usb ppp + USB modem problem f [2002/06/24] kern/39805 usb 4.6R install panics with umass0 device co o [2002/07/19] kern/40792 usb signals lead to data loss on device ugen o [2002/09/13] kern/42748 usb USB does not work (Fujitsu Lifebook) f [2002/09/25] i386/43366 usb Cannot format media in USB floppy devices o [2002/09/29] kern/43462 usb copying files from olympus C-4040 digital o [2002/10/13] bin/43993 usb /usr/sbin/usbd does not handle an usb eve f [2002/11/22] kern/45579 usb Panic from USB stack after device detach o [2002/12/10] kern/46176 usb umass causes kernel panic if device remov o [2002/12/19] i386/46371 usb USB controller cannot be initialized on I f [2002/12/24] i386/46506 usb [usb] [hang] Crash Before Initialization o [2002/12/29] kern/46618 usb USB (UHCI/ICH3) PALM connect/disconnect/c f [2003/01/12] kern/47005 usb OHCI USB not noticing device detachments o [2003/02/17] kern/48359 usb SiS 5597/8 USB + uscanner breakage a [2003/03/02] kern/48849 usb Maxtor XT5000 causes panic in boot o [2003/03/05] kern/48952 usb uscanner0 hangs a [2003/03/20] kern/50149 usb Using Alcatel SpeedTouch results in "usb0 a [2003/08/14] kern/55587 usb null dereference in usbdi.c: usb_transfer o [2003/09/26] bin/57255 usb usbd and multi-function devices f [2003/12/11] kern/60131 usb [usb] Page fault on disconnect of USB dev f [2003/12/13] kern/60217 usb EHCI controller halts when USB 2.0 device o [2003/12/15] kern/60276 usb [usb] Kernel panic when plugging in USB ( o [2004/01/11] kern/61191 usb [usb] panic: USB vs. Serial problems o [2004/01/15] kern/61377 usb [kbd] usb keyboard not functional after b o [2004/01/20] kern/61627 usb [usb] [patch] New USB printer not support f [2004/01/23] kern/61804 usb [panic] panic with hitachi travelstar USB o [2004/01/24] kern/61841 usb [boot] 5.2 Boot freeze if memorybird (USB f [2004/01/30] kern/62088 usb [usb] Logitech Cordless/Optical Mouse not o [2004/01/30] kern/62123 usb [usb] LaCie 160GB USB drive umass: BBB re o [2004/02/23] i386/63251 usb [usb] USB stops working after 2nd APM sus o [2004/02/26] kern/63375 usb [patch] panic: unplugging USB devices pan o [2004/02/29] i386/63521 usb 5.2.1 doesn't detect drives on SATA contr o [2004/03/01] kern/63621 usb [usb] USB MemoryStick Reader stalls/crash o [2004/04/07] kern/65292 usb [panic] random page faults (usb-related?) o [2004/04/19] i386/65783 usb [panic] Panic when attaching card reader o [2004/05/06] kern/66324 usb [usb] usb driver memory leak grows wired o [2004/07/13] kern/69006 usb [patch] Apple Cinema Display hangs USB po o [2004/08/30] kern/71155 usb [usb] misbehaving usb-printer hangs proce o [2004/09/18] kern/71887 usb [kbd] Losing keyboard after plugging a bl o [2004/09/27] kern/72119 usb Detaching USB Memory Stick w/o umount cau f [2004/10/11] i386/72497 usb WD USB Disk Panics -stable and 5.2.1 o [2004/10/29] kern/73295 usb Lock order reversal in USB code. o [2004/10/30] kern/73307 usb Kernel panics on USB disconnect o [2004/11/18] kern/74088 usb ohci ehci uhub: port disabled on connecti 51 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/09/30] conf/30929 usb [patch] use usbd to initialize USB ADSL m o [2001/12/09] kern/32652 usb [patch] A new ioctl to uscanner s [2001/12/09] ports/32653 usb Added patches to improve USB scanner supp f [2002/04/23] kern/37374 usb [PATCH] closing ums0 blocks with wmesg uh f [2002/05/04] conf/37732 usb usbd start in wrong place in /etc/rc in 4 o [2002/05/23] kern/38452 usb [usb] Logitech USB iFeel: device_probe_an o [2002/07/16] kern/40657 usb [usb] Logitech iFeel usb mouse will not a o [2002/07/24] kern/40948 usb [usb] USB HP CDW8200 does not work o [2002/08/07] kern/41415 usb [usb] [patch] Some USB scanners cannot ta f [2002/10/25] kern/44450 usb USB support FAILURE for device that was s o [2003/01/18] kern/47200 usb USB port is disabled when Kodak DX4900 is o [2003/02/06] kern/48014 usb [usb] moused fails to correctly identify o [2003/02/16] bin/48342 usb [PATCH] usbd dynamic device list. o [2003/03/19] kern/50110 usb [usb] Astra 2100U scanner being detected o [2003/05/08] kern/51958 usb [usb] [patch] update for urio driver o [2003/05/10] kern/52026 usb [usb] feature request: umass driver suppo o [2003/06/08] kern/53025 usb [PATCH] ugen does not allow O_NONBLOCK fo f [2003/09/19] kern/56999 usb FreeCom USB CD/RW problem on FreeBSD 5.1 o [2003/11/10] i386/59147 usb [usb] USB active extension cable not reco o [2003/11/11] kern/59169 usb [patch] ulpt is missing read operation o [2003/12/15] kern/60248 usb [patch] Problem with USB printer HP Laser o [2004/01/12] bin/61234 usb [usb] [patch] usbhidaction doesn't suppor o [2004/01/14] kern/61365 usb FreeBSD resets when I turn off monitor w/ o [2004/02/13] kern/62788 usb need quirks for Super Talent Flash USB 2. o [2004/03/04] kern/63779 usb [usb] USB-mass storage (USB to IDE Conver o [2004/03/06] kern/63837 usb [patch] USB: hid_is_collection() only loo o [2004/04/11] kern/65436 usb QUIRK: [patch] to add support for PNY Att o [2004/04/19] kern/65769 usb [usb] Call to tcflush(x, TCIFLUSH) stops o [2004/05/11] kern/66547 usb [usb] Palm Tungsten T USB does not initia o [2004/06/27] kern/68412 usb [usb] [patch] QUIRK: Philips KEY013 USB M o [2004/07/06] i386/68719 usb [usb] USB 2.0 mobil rack+ fat32 performan o [2004/08/16] kern/70523 usb [usb] [patch] umct sending/receiving wron o [2004/08/25] kern/70942 usb [usb] Genius Wireless USB mouse: moused d o [2004/09/06] kern/71416 usb [usb] Cryptoflex e-gate USB token (ugen0) o [2004/09/06] kern/71417 usb [usb] Cryptoflex e-gate USB token (ugen0) o [2004/09/07] kern/71455 usb [usb] Slow USB umass performance of 5.3 o [2004/09/11] kern/71605 usb [usb] [patch] umass doesn't recognize mul o [2004/10/05] kern/72344 usb [usb] [patch] QUIRK: Dane-Elec zMate 512 f [2004/10/06] i386/72380 usb [usb] USB does not work [dual Celeron Abi o [2004/10/23] i386/73056 usb [usb] Sun Microsystems Type 6 USB mouse n o [2004/11/02] i386/73421 usb [usb] USB not recgnized/working on Toshib o [2004/11/16] kern/73999 usb [usb] USB Freezes when a device is plugge 42 problems total. From owner-freebsd-usb@FreeBSD.ORG Mon Dec 20 19:45:36 2004 Return-Path: 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 6FFE516A4D0 for ; Mon, 20 Dec 2004 19:45:36 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FC9843D41 for ; Mon, 20 Dec 2004 19:45:36 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 3BE467A425; Mon, 20 Dec 2004 11:45:36 -0800 (PST) Message-ID: <41C72BE0.2030807@elischer.org> Date: Mon, 20 Dec 2004 11:45:36 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Steve Watt References: <200412192223.iBJMNlK3026093@wattres.watt.com> In-Reply-To: <200412192223.iBJMNlK3026093@wattres.watt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: panic w/ USB<->serial adapter and modem X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 19:45:36 -0000 Steve Watt wrote: >On Dec 19, 13:46, Julian Elischer wrote: > >} >} This may be fixed in the ongoing 5 branch after 5.3 (and teh >} 6 branch (-current)) and in the newest 4.x too i think. >} There were problems in the abort code that have been fixed.. >} this may relate to your problem. > >Do you know roughly when the fix went in? It's reproducable >enough that I can just try it, though. > -------------------------- in -current: revision 1.159 date: 2004/11/16 00:48:27; author: iedowse; state: Exp; lines: +2 -1 Fix just the worst of the timeout race conditions that the previous backed out commits were trying to address: when cancelling the timeout callout, also cancel the abort_task event, since it is possible that the timeout has already fired and set up an abort_task. ----------------------------------- In releng_4: revision 1.40.2.15 date: 2004/11/24 19:04:30; author: julian; state: Exp; lines: +2 -0 MFC: Fix just the worst of the known timeout race conditions. ehci.c 1.20 uhci.c 1.159 ohci.c 1.147 -------------------------------------- In releng_5: revision 1.154.2.2 date: 2004/12/01 03:02:52; author: iedowse; state: Exp; lines: +2 -1 MFC: fix the worst of the timeout race conditions: usb_port.h 1.72 uhci.c 1.159 ehci.c 1.20 ohci.c 1.147 > >Thanks, > >[ snip the trace ] > > > From owner-freebsd-usb@FreeBSD.ORG Mon Dec 20 21:51:24 2004 Return-Path: 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 CE76A16A4CE for ; Mon, 20 Dec 2004 21:51:24 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 650F543D46 for ; Mon, 20 Dec 2004 21:51:24 +0000 (GMT) (envelope-from e.schuele@computer.org) Received: from [208.206.151.59] (host59.gtisd.com[208.206.151.59]) by comcast.net (sccrmhc12) with ESMTP id <2004122021505901200754g1e>; Mon, 20 Dec 2004 21:50:59 +0000 Message-ID: <41C748B7.5050707@computer.org> Date: Mon, 20 Dec 2004 15:48:39 -0600 From: Eric Schuele User-Agent: Mozilla Thunderbird 1.0 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freeBSD-USB@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Trouble with TEAC usb floppy (FD-05PUB)... X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 21:51:24 -0000 Hello, I'm having trouble with my TEAC (FD-05PUB) USB Floppy in 5.3-STABLE i386 on a Dell Inspiron 5100. My problem appears to be that which is described in the following post(s): http://news.gw.com/freebsd.ia64/348 http://news.gw.com/freebsd.ia64/347 I was wondering if a fix had ever been developed. I have cvsup'd RELENG_5 on Dec 19 2004, and the problem still persists. To summarize.. I see things like this in dmesg umass0: TEAC TEAC FD-05PUB, rev 2.00/0.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 1MB (2880 512 byte sectors: 64H 32S/T 1C) umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 ... and ... > > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not present > (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (da0:umass-sim0:0:0:0): SCSI Status: Check Condition > (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 > (da0:umass-sim0:0:0:0): Medium not present > (da0:umass-sim0:0:0:0): Unretryable error > Opened disk da0 -> 6 Can mount the disk, ls the contents, but otherwise its useless. Page fault when umounting and/or if I remove device before umounting. I have a kernel configuration including usb, da, ohci, uhci as per a post I found. It was working in 5.2.1-RELEASE... maybe in 5.3-BETA7 (I think). But appears broken now. I've googled, read the manual, searched the PRs, read UPDATING, etc, etc... can't find the fix. If I've missed it could someone please point me in the right direction. -- Regards, Eric From owner-freebsd-usb@FreeBSD.ORG Mon Dec 20 21:58:08 2004 Return-Path: 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 01BED16A4CE for ; Mon, 20 Dec 2004 21:58:08 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7624A43D5D for ; Mon, 20 Dec 2004 21:58:07 +0000 (GMT) (envelope-from e.schuele@computer.org) Received: from [208.206.151.59] (host59.gtisd.com[208.206.151.59]) by comcast.net (rwcrmhc12) with ESMTP id <20041220215801014002g3tie>; Mon, 20 Dec 2004 21:58:02 +0000 Message-ID: <41C74A63.8050303@computer.org> Date: Mon, 20 Dec 2004 15:55:47 -0600 From: Eric Schuele User-Agent: Mozilla Thunderbird 1.0 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 References: <41C748B7.5050707@computer.org> In-Reply-To: <41C748B7.5050707@computer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freeBSD-USB@freebsd.org Subject: Re: Trouble with TEAC usb floppy (FD-05PUB)... X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 21:58:08 -0000 Forgot to mention: It behaves the same with ACPI enabled or disabled. Eric Schuele wrote: > Hello, > > I'm having trouble with my TEAC (FD-05PUB) USB Floppy in 5.3-STABLE i386 > on a Dell Inspiron 5100. > > My problem appears to be that which is described in the following post(s): > http://news.gw.com/freebsd.ia64/348 > http://news.gw.com/freebsd.ia64/347 > > I was wondering if a fix had ever been developed. I have cvsup'd > RELENG_5 on Dec 19 2004, and the problem still persists. > > To summarize.. I see things like this in dmesg > umass0: TEAC TEAC FD-05PUB, rev 2.00/0.00, addr 2 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: 1MB (2880 512 byte sectors: 64H 32S/T 1C) > umass0: Unsupported UFI command 0x35 > (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi > status == 0x0 > umass0: Unsupported UFI command 0x35 > (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi > status == 0x0 > umass0: Unsupported UFI command 0x35 > (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi > status == 0x0 > > ... and ... > > > > > da0 at umass-sim0 bus 0 target 0 lun 0 > > da0: Removable Direct Access SCSI-0 device > > da0: 1.000MB/s transfers > > da0: Attempt to query device size failed: NOT READY, Medium not present > > (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > > (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error > > (da0:umass-sim0:0:0:0): SCSI Status: Check Condition > > (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 > > (da0:umass-sim0:0:0:0): Medium not present > > (da0:umass-sim0:0:0:0): Unretryable error > > Opened disk da0 -> 6 > > Can mount the disk, ls the contents, but otherwise its useless. Page > fault when umounting and/or if I remove device before umounting. > > I have a kernel configuration including > usb, da, ohci, uhci > as per a post I found. > > It was working in 5.2.1-RELEASE... maybe in 5.3-BETA7 (I think). But > appears broken now. > > I've googled, read the manual, searched the PRs, read UPDATING, etc, > etc... can't find the fix. If I've missed it could someone please point > me in the right direction. > -- Regards, Eric From owner-freebsd-usb@FreeBSD.ORG Tue Dec 21 01:45:41 2004 Return-Path: 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 529B316A4CE for ; Tue, 21 Dec 2004 01:45:41 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09BA343D1F for ; Tue, 21 Dec 2004 01:45:41 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id B12967A450; Mon, 20 Dec 2004 17:45:40 -0800 (PST) Message-ID: <41C78044.2050005@elischer.org> Date: Mon, 20 Dec 2004 17:45:40 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: usb@freebsd.org, Lennart Augustsson Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: getting vendor IDs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 01:45:41 -0000 For those interested, here's a littel script that pruduces a list of vendor names vs USB IDs. taken from the USB website in a backdoor manner. #!/bin/sh fetch -o- http://www.usb.org/app/db/search/contacts/ |\ awk -F'[<=>"]' '/