From owner-freebsd-usb@FreeBSD.ORG Sun Oct 17 17:47:11 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3127C1065674 for ; Sun, 17 Oct 2010 17:47:11 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.freebsd.org (Postfix) with ESMTP id B307F8FC16 for ; Sun, 17 Oct 2010 17:47:10 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=gl0LPzB4YDQuuzpDoHYit7deEV0cOo++Sg28kyvF6vg= c=1 sm=1 a=P4Ckh2d6ZMEA:10 a=N659UExz7-8A:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=8kQB0OdkAAAA:8 a=vtkzoV46cqmySDWx2ZUA:9 a=GDGN_VBwe-rjXIxpc3fxRfl5CSkA:4 a=pILNOxqGKmIA:10 a=9aOQ2cSd83gA:10 a=pn506jkUYPczYuoS:21 a=TkqEEsdrorsb4TU8:21 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 36299227; Sun, 17 Oct 2010 19:47:08 +0200 From: Hans Petter Selasky To: "Wilkinson, Alex" Date: Sun, 17 Oct 2010 19:48:25 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <201010140851.51159.hselasky@freebsd.org> <4CB7525C.3030702@freebsdfoundation.org> In-Reply-To: <4CB7525C.3030702@freebsdfoundation.org> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'( =?windows-1252?q?=3B=5FIjlA=3A=0A=09hGE=2E=2EEw?=, =?windows-1252?q?XAQ*o=23=5C/M=7ESC=3DS1-f9=7BEzRfT=27=7CHhll5Q=5Dha5Bt-s=7Co?= =?windows-1252?q?TlKMusi=3A1e=5BwJl=7Dkd=7DGR=0A=09Z0adGx-x=5F0zGbZj=27e?=(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <201010171948.25610.hselasky@c2i.net> Cc: freebsd-emulation@freebsd.org, freebsd-usb@freebsd.org Subject: Re: Hope for USB support? [SEC=UNCLASSIFIED] X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2010 17:47:11 -0000 On Thursday 14 October 2010 20:56:28 Deb Goodkin wrote: > Dear Hans, > > Add USB support to VirtualBox under FreeBSD. Hi, My paypal account is: hselasky@c2i.net The plan is to release VirtualBox USB support for FreeBSD 8+ before November or December 2010. Currently two people have requested interest paying for this support. If everyone that is interested in this can send me an e-mail, I will divide $1000 by the number of people interested and send out a pay-request. --HPS From owner-freebsd-usb@FreeBSD.ORG Sun Oct 17 18:11:39 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBCD410656AA; Sun, 17 Oct 2010 18:11:39 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id 3216F8FC08; Sun, 17 Oct 2010 18:11:38 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=omSrwDgyMf70S47Fr5SNr0rQzcmIOo0IafWlB/wSLLo= c=1 sm=1 a=P4Ckh2d6ZMEA:10 a=N659UExz7-8A:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=8kQB0OdkAAAA:8 a=PzXqmPsee8DjNEux5dUA:9 a=9zNUp9uqbp5MxMgwZAMx1aDDMJkA:4 a=pILNOxqGKmIA:10 a=9aOQ2cSd83gA:10 a=M47vDuLcLiWnuYt1:21 a=3ilpgUxB4e2ycMDK:21 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 37053153; Sun, 17 Oct 2010 20:11:37 +0200 From: Hans Petter Selasky To: "Wilkinson, Alex" Date: Sun, 17 Oct 2010 20:12:54 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <201010140851.51159.hselasky@freebsd.org> <4CB7525C.3030702@freebsdfoundation.org> <201010171948.25610.hselasky@c2i.net> In-Reply-To: <201010171948.25610.hselasky@c2i.net> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <201010172012.54484.hselasky@c2i.net> Cc: freebsd-emulation@freebsd.org, freebsd-usb@freebsd.org Subject: Re: Hope for USB support? [SEC=UNCLASSIFIED] X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2010 18:11:40 -0000 On Sunday 17 October 2010 19:48:25 Hans Petter Selasky wrote: > On Thursday 14 October 2010 20:56:28 Deb Goodkin wrote: > > Dear Hans, > > > > > Add USB support to VirtualBox under FreeBSD. > > Hi, > > My paypal account is: hselasky@c2i.net > > The plan is to release VirtualBox USB support for FreeBSD 8+ before > November or December 2010. Currently two people have requested interest > paying for this support. If everyone that is interested in this can send > me an e-mail, I will divide $1000 by the number of people interested and > send out a pay-request. > > --HPS Checking the VirtualBox SVN sources, it appears someone has already done the work :-) I'm checking out the stuff right now! /* $Id: USBProxyDevice-freebsd.cpp 31890 2010-08-24 07:50:47Z vboxsync $ */ --HPS From owner-freebsd-usb@FreeBSD.ORG Sun Oct 17 18:40:43 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD941106566C for ; Sun, 17 Oct 2010 18:40:43 +0000 (UTC) (envelope-from fb-usb@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id 7F2578FC1B for ; Sun, 17 Oct 2010 18:40:43 +0000 (UTC) Received: from mx1.psconsult.nl (psc11.adsl.iaf.nl [80.89.238.138]) by mx1.psconsult.nl (8.14.4/8.14.4) with ESMTP id o9HIeb5W038413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 17 Oct 2010 20:40:42 +0200 (CEST) (envelope-from fb-usb@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.4/8.14.4/Submit) id o9HIeblT038412 for freebsd-usb@freebsd.org; Sun, 17 Oct 2010 20:40:37 +0200 (CEST) (envelope-from fb-usb@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to fb-usb@psconsult.nl using -f Date: Sun, 17 Oct 2010 20:40:37 +0200 From: Paul Schenkeveld To: freebsd-usb@freebsd.org Message-ID: <20101017184037.GA38323@psconsult.nl> References: <20101016140502.GA12905@psconsult.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Subject: Re: How to use the buttons on my USB scanner X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2010 18:40:43 -0000 On Sat, Oct 16, 2010 at 08:24:52AM -0600, Warren Block wrote: > On Sat, 16 Oct 2010, Paul Schenkeveld wrote: > > > My HP 7400c scanner has several buttons and a LCD display. Would it > > be possible to read the buttons > > sysutils/scanbuttond works, at least with my Epson scanner's one button. Hadn't seen that port yet but unfortunately the pkg-descr file says: The supported scanner backends currently are: epson, niash, plustek, snapscan (my backend is avision) and scanbuttond obviously doesn't respond to buttons pressed. Anywey, thanks for your answer. Regards, Paul Schenkeveld From owner-freebsd-usb@FreeBSD.ORG Mon Oct 18 11:07:09 2010 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BBB910656A4 for ; Mon, 18 Oct 2010 11:07:09 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 786808FC27 for ; Mon, 18 Oct 2010 11:07:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o9IB79RV029483 for ; Mon, 18 Oct 2010 11:07:09 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o9IB78Le029481 for freebsd-usb@FreeBSD.org; Mon, 18 Oct 2010 11:07:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Oct 2010 11:07:08 GMT Message-Id: <201010181107.o9IB78Le029481@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-usb@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2010 11:07:09 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o usb/151043 usb Please add USB device MELCO WLR-UC-G o usb/150989 usb [patch] Add Netgear WG111V2_2 support to upgt(4) o usb/150892 usb [zyd] Whenever network contacted in any shape, way or p usb/150546 usb libusb(3) libusb_control_transfer() prototype is incor o usb/150401 usb [umass] [usb8] Errors from USB drives mixed between UF o usb/150189 usb [run] [usb8] [patch] if_run appears to corrupt IP traf o usb/149934 usb [patch] [usb8] Transcend JetFlash V85 poor performance o usb/149900 usb [uftdi] [patch] FreeBSD 8.1 uftdi patch to support usb o usb/149764 usb [u3g] [patch] usbdevs update: Huawei K3765 3G modem o usb/149675 usb [uftdi] [usb_serial] doesn't react to break properly o usb/149528 usb [zyd] Wireless USB stick not detected - vendor id 0x08 o usb/149283 usb [uftdi] avrdude unable to talk to Arduino board (via u o usb/149162 usb [ural] ASUS WL-167g doesn't work in 8.1 (continue of 1 o usb/149039 usb [uhso] [patch] Binding problem with uhso s usb/148702 usb [usb8] [request] IO DATA USB-RSAQ5 support on FreeBSD- o usb/148080 usb usbconfig(8) sometimes does not turn off the device o usb/147516 usb [umass] [usb67] kernel unable to deal with Olympus USB o usb/146871 usb [usbdevs] [usb8] [patch] provide descriprive string fo o usb/146840 usb [hang] FreeBSD 7.2 / 7.3 / 8.0 hang at startup after e o usb/146153 usb [axe] [usb8] Hosts in network doesn't receive any pack o usb/146054 usb [urtw] [usb8] urtw driver potentially out of date f usb/145513 usb [usb8] New USB stack: no new devices after forced usb o usb/145455 usb [usb8] [patch] USB debug support cannot be disabled o usb/145415 usb [umass] [usb8] USB card reader does not create slices a usb/145184 usb GENERIC can't mount root from USB on Asus EEE o usb/145165 usb [keyboard] [usb8] ukbd_set_leds_callback: error=USB_ER f kern/144938 usb [keyboard] [boot] Boot Failure with Apple (MB869LL/A) o usb/144387 usb [run] [panic] if_run panic o usb/144043 usb [umass] [usb8] USB DLT tape drive throws random errors o usb/143790 usb [boot] can not boot from usb hdd f usb/143620 usb [cdce] [usb8] the module if_cdce doesn't support my Op f usb/143294 usb [usb8] copying process stops at some time (10 - 50 sec o usb/143286 usb [ukbd] [usb8] [boot] boot failures on RELENG_8 system f usb/143186 usb [usbdevs] [usb8] [patch] add USB device IDs for Google a usb/143139 usb [umass] [usb8] [patch] Quirk for Century EX35SW4_SB4 J o usb/143045 usb [umass] [usb8] [patch] mounting Fujitsu 2600Z camera d o usb/142991 usb [uftdi] [usb67] [patch] Patch to add Crystalfontz 533 f usb/142989 usb [usb8] canon eos 50D attaches but detaches after few s f usb/142957 usb [umass] [usb8] [patch] patch for USB disk SYNCHRONIZE o usb/142719 usb [urtw] [usb8] AirLive WL-1600USB (RTL8187L chipset) fa o usb/142713 usb [usb67] [panic] Kernel Panik when connecting an IPhone f usb/142276 usb [umass] [usb8] Cache Synchronization Error with Olympu o usb/142229 usb [ums] [usb8] [hang] connecting a USB mouse to a Dell P o usb/141680 usb [uath] [usb8] Netgear WG111T not working with uath dri o usb/141664 usb [pcm] [usb8] Logitech USB microphone failure [regressi o usb/141474 usb [boot] [usb8] FreeBSD 8.0 can not install from USB CDR o usb/141327 usb [ukbd] [usb67] USB kbd not working with 7.1+PAE on IBM o usb/141212 usb [ukbd] [usb8] ukbd_set_leds_callback:700: error=USB_ER o kern/141011 usb [usb] Encrypted root, geli password at boot; enter key o usb/140920 usb [install] [usb8] USB based install fails on 8.0-RELEAS o usb/140893 usb [urtw] [usb8] WPA2 not working on rtl8187b f usb/140883 usb [axe] [usb8] USB gigabit ethernet hangs after short pe o kern/140849 usb [ums] [usb8] USB mouse doesn't work under FreeBSD 8.0- a usb/140810 usb [uftdi] [usb8] 8.X copy and paste problem / tty overfl o usb/140477 usb [umass] [usb8] [patch] allow boot-time attachment of d o usb/140236 usb [msdosfs] [usb8] Labels wiped on external Journaled US o usb/140160 usb [usb8] [acpi] USB ports are no longer "active" after A s usb/139990 usb [panic] [patch] [usb67] Kernel frequently panics after a usb/139598 usb [umass] [usb8] CAM reports "xptioctl: put "device pass o usb/139243 usb [uhci] [usb67] unplug prolific USB serial -> uhci_abor a usb/138904 usb [rum] [panic] [usb67] unpluging USB wifi card panics s f usb/138882 usb [ohci] [panic] [usb67] Can't install FreeBSD 7.2 due t o usb/138798 usb [boot] [usb8] 8.0-BETA4 can't boot from USB flash driv o usb/138659 usb [usb8][uftdi] driver broken in RELENG_8/CURRENT o usb/138570 usb [usb] [panic] USB mass device panics current 7.2-STABL o usb/138548 usb [usb67] [usb8] usb devices periodically have unknown a o usb/138175 usb [usb67] [boot] System cannot boot, when USB reader wit o usb/138124 usb [snd_uaudio] [usb8] Axed uaudio functionality in the u o usb/138119 usb [usb67] [usb8] MultiBay CDROM (probably on USB bus) is o usb/137872 usb [usb67] [boot] slow booting on usb flash drive o usb/137806 usb [ukbd] [usb67] USB keyboard doesn't work until it's un o usb/137763 usb [usb67][ukbd] Logitech wireless keyboard media keys no o usb/137377 usb [usb8] request support for Huawei E180 o usb/137341 usb [usb8][rum] driver if_rum doesn't work at all and thro f usb/137190 usb [usb8][patch] inhibit spurious button releases for som o usb/137189 usb [usb8][patch] create and use sysctl nodes for HID repo p usb/137188 usb [usb8][patch] correctly handle USB report descriptors o usb/137129 usb [ums] [usb8] SteelSeries Ikari USB laser mouse not att p usb/136761 usb [usbdevs][usb67][patch] Teach usbdevs / u3g(4) about H o usb/135938 usb [aue] [usb67] aue driver only passes traffic in promis o usb/135542 usb [keyboard] boot loader does not work with a usb keyboa o usb/135348 usb [umass] [patch] USB Drive Hangs with ZFS (JMicron USB2 o usb/135206 usb machine reboots when inserted USB device o usb/135200 usb SAMSUNG i740 usb mass: Synchronize cache failed, statu o usb/135182 usb UMASS quirk - Olympus FE20 camera o usb/134950 usb Lowering DTR for USB-modem via ubsa is not possible o usb/134299 usb Kernel Panic plugging in MF626 USB UMTS Stick u3g o usb/134193 usb System freeze on usb MP3 player insertion o usb/134085 usb [umass] Adding usb quirk for Sony USB flash drive o usb/133989 usb [usb8] [ukbd] USB keyboard dead at mountroot> prompt o usb/133712 usb [ural] [patch] RE: Fixed an issue with ural(4) that wa o usb/133390 usb umass crashes system in 7.1 when Olympus D-540 attache o usb/133296 usb [rum] driver not working properly in hostap mode o usb/132594 usb USB subsystem causes page fault and crashes o usb/132312 usb [hang] Xorg 7.4 halts USB controller o usb/132080 usb [patch] [usb] [rum] [panic] Kernel panic after NOMEM c o usb/132066 usb [ukbd] Keyboard failure USB keyboard DELL 760 o usb/132036 usb [panic] page fault when connecting Olympus C740 camera o usb/131583 usb [umass] Failure when detaching umass Device o usb/131576 usb [aue] ADMtek USB To LAN Converter can't send data o usb/131521 usb Registering Belkin UPS to usb_quirks.c p usb/131123 usb [patch] [usb67] re-add UQ_ASSUME_CM_OVER_DATA USB quir o usb/131074 usb no run-time detection of usb devices plugged into exte o usb/130736 usb Page fault unplugging USB stick o usb/130230 usb Samsung Electronics YP-U3 does not attach in 7.1-RELEA o usb/130208 usb Boot process severely hampered by umass0 error o usb/130122 usb [usb8] DVD drive detects as 'da' device o usb/129766 usb [usb] [panic] plugging in usb modem HUAWEI E226 panics o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb67] [patch] uaudio is not full duplex p usb/128803 usb [usbdevs] [patch] Quirk for I-Tuner Networks USBLCD4X2 o usb/128485 usb [umodem] [patch] Nokia N80 modem support o usb/128425 usb [umass] Cannot Connect Maxtor Onetouch 4 USB drive o usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/127926 usb [boot] USB Timeout during bootup s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should p docs/127406 usb [patch] update umodem man page: Sony Ericsson W810i o usb/127342 usb [boot] [panic] enabling usb keyboard and mouse support o usb/127248 usb [ucom] panic while uplcom devices attach and detach o usb/127222 usb [ohci] Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c o usb/126848 usb [usb]: USB Keyboard hangs during Installation o usb/126740 usb [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be o usb/126519 usb [usb] [panic] panic when plugging in an iphone o kern/126396 usb [panic] kernel panic after unplug USB Bluetooth device o usb/125631 usb [ums] [panic] kernel panic during bootup while 'Logite o usb/125510 usb [panic] repeated plug and unplug of USB mass storage d o usb/125450 usb [panic] Removing USB flash card while being accessed c o usb/125238 usb [ums] Habu Mouse turns off in X o usb/125088 usb [keyboard] Touchpad not detected on Adesso AKB-430UG U o usb/124980 usb [panic] kernel panic on detaching unmounted umass devi o kern/124777 usb [ucom] USB cua devices don't revert to tty devices whe o usb/124758 usb [rum] [panic] rum panics SMP kernel o usb/124708 usb [panic] Kernel panic on USB KVM reattach f usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work o kern/124130 usb [usb] gmirror fails to start usb devices that were pre o usb/123969 usb [usb] Supermicro H8SMi-2 usb problem: port reset faile o usb/123714 usb [usb] [panic] Panic when hald-storage-probe runs with o usb/123691 usb usbd(8): usbd hangs o usb/123690 usb [usb] [panic] Panic on USB device insertion when usb l o usb/123611 usb [usb] BBB reset failed, STALLED from Imation/Mitsumi U o usb/123509 usb [umass] continuous reset Samsung SGH-G600 phone o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122936 usb [ucom] [ubsa] Device does not receive interrupt o usb/122905 usb [ubsa] [patch] add Huawei E220 to ubsa o usb/122819 usb [usb] [patch] Patch to provide dynamic additions to th o usb/122813 usb [udbp] [request] udbp driver should be removed in favo o usb/122547 usb [ehci] USB Printer not being recognized after reboot o usb/122539 usb [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci o usb/122483 usb [panic] [ulpt] Repeatable panic in 7.0-STABLE o usb/122119 usb [umass] umass device causes creation of daX but not da o usb/121755 usb [ohci] [patch] Fix panic after ohci/uhub cardbus devic o usb/121734 usb [ugen] ugen HP1022 printer device not working since up o usb/121708 usb [keyboard] nforce 650i mobo w/ usb keyboard infinite k o usb/121474 usb [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard o usb/121275 usb [boot] [panic] FreeBSD fails to boot with usb legacy s o usb/121232 usb [usb] [panic] USB CardBus card removal causes reboot s p usb/121184 usb [uipaq] [patch] add ids from linux ipaq driver (plus a o usb/121169 usb [umass] Issues with usb mp3 player o usb/121045 usb [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS o usb/120786 usb [usb] [panic] Kernel panic when forced umount of a det o usb/120729 usb [panic] fault while in kernel mode with connecting USB o usb/120572 usb [usb67] [umass] [patch] quirk to support ASUS P535 as o usb/120321 usb [hang] System hangs when transferring data to WD MyBoo o usb/120283 usb [panic] Automation reboot with wireless keyboard & mou o usb/120034 usb [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 o usb/119977 usb [ums] Mouse does not work in a Cherry-USB keyboard/mou o usb/119653 usb [cam] [patch] iriver s7 player sync cache error patch o usb/119633 usb [umass] umass0: BBB reset failed, IOERROR [regression] o usb/119513 usb [irq] inserting dlink dwl-g630 wireless card results i o usb/119509 usb [usb] USB flaky on Dell Optiplex 755 o usb/119481 usb [hang] FreeBSD not responding after connecting USB-Mas o usb/119389 usb [umass] Sony DSC-W1 CBI reset failed, STALLED [regress o usb/119227 usb [ubsa] [patch] ubsa buffer is too small; should be tun o usb/119201 usb [cam] [patch] Quirks for Olympus FE-210 camera, LG and o usb/118480 usb [umass] Timeout in USB mass storage freezes vfs layer o usb/118353 usb [panic] [ppp] repeatable kernel panic during ppp(4) se o usb/118141 usb [ucom] usb serial and nokia phones ucomreadcb ucomread o usb/118140 usb [ucom] [patch] quick hack for ucom to get it behave wi o usb/118098 usb [umass] 6th gen iPod causes problems when disconnectin o usb/117955 usb [umass] [panic] inserting minolta dimage a2 crashes OS o usb/117946 usb [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE o usb/117938 usb [ums] [patch] Adding support for MS WL Natural and MS o usb/117911 usb [ums] [request] Mouse Gembird MUSWC not work o usb/117893 usb [umass] Lacie USB DVD writing failing o usb/117613 usb [uhci] [irq] uhci interrupt storm & USB leaked memory o usb/117598 usb [snd_uaudio] [patch] Not possible to record with Plant o usb/117313 usb [umass] [panic] panic on usb camera insertion o usb/117200 usb [ugen] ugen0 prints strange string on attach if detach o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a p usb/116947 usb [ukbd] [patch] [regression] enable boot protocol on th o usb/116699 usb [usbhid] USB HID devices do not initialize at system b o usb/116561 usb [umodem] [panic] RELENG_6 umodem panic "trying to slee o usb/116282 usb [ulpt] Cannot print on USB HP LJ1018 or LJ1300 o usb/115935 usb [usbdevs] [patch] kernel counterproductively attaches o usb/115933 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/115400 usb [ehci] Problem with EHCI on ASUS M2N4-SLI o usb/115298 usb [ulpt] [panic] Turning off USB printer panics kernel o usb/114916 usb [umass] [patch] USB Maxtor drive (L300RO) requires qui o kern/114780 usb [uplcom] [panic] Panics while stress testing the uplco o usb/114682 usb [umass] generic USB media-card reader unusable o usb/114310 usb [libusb] [patch] [panic] USB hub attachment panics ker o usb/114068 usb [usb67] [usb8] [umass] [patch] Problem with connection o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113060 usb [usb67] [ulpt] [patch] Samsung printer not working in o usb/110856 usb [usb67] [ugen] [patch] interrupt in msgs are truncated s usb/108344 usb [usb67] [atausb] [panic] kernel with atausb panics whe o usb/107827 usb [usb67] [ohci] [panic] ohci_add_done addr not found o usb/107388 usb [usb67] [usb8] [new driver] [patch] add utoppy device o usb/106041 usb [usb67] [usb8] [request] FreeBSD does not recognise Mu o usb/105361 usb [usb67] [panic] Kernel panic during unmounting mass st s usb/103917 usb [usb67] [uhub] USB driver reports "Addr 0 should never o usb/103418 usb [usb67] [usb8] [patch] [request] usbhidctl(8) add abil o usb/103046 usb [usb67] [ulpt] [patch] ulpt event driven I/O with sele o usb/101775 usb [usb67] [usb8] [libusbhid] [patch] possible error in r o usb/101761 usb [usb67] [patch] [request] usb.h: increase maximal size o usb/100746 usb [usb67] [ukbd] system does not boot due to USB keyboar o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar o kern/99200 usb [bluetooth] SMP-Kernel crashes reliably when Bluetooth o usb/98343 usb [boot] BBB reset failed errors with Creative Muvo MP3 o usb/97472 usb [cam] [patch] add support for Olympus C150,D390 s usb/97286 usb [mouse] [request] MS Wireless Intellimouse Explorer 2. o usb/97175 usb [umass] [hang] USB cardreader hangs system o usb/96457 usb [umass] [panic] fatback on umass = reboot o usb/96381 usb [cam] [patch] add a quirk table entry for a flash ram o usb/96224 usb [usb] [msdosfs] mount_msdosfs cause page fault in sync s usb/96120 usb [ums] [request] USB mouse not always detected s usb/95636 usb [umass] [boot] 5 minute delay at boot when using VT620 o usb/95562 usb [umass] Write Stress in USB Mass drive causes "vinvalb s usb/95348 usb [keyboard] USB keyboard unplug causes noise on screen o usb/95037 usb [umass] USB disk not recognized on hot-plug. o usb/94897 usb [panic] Kernel Panic when cleanly unmounting USB disk o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94384 usb [panic] kernel panic with usb2 hardware o usb/93872 usb [cam] [patch] SCSI quirk required for ELTA 8061 OL USB o usb/93828 usb [ohci] [panic] ohci causes panic on boot (HP Pavillion o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/92852 usb [ums] [patch] Vertical scroll not working properly on o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/92142 usb [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb o usb/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92052 usb [ulpt] usbd causes defunct process with busy file-hand o usb/91906 usb [ehci] [hang] FreeBSD hangs while booting with USB leg f usb/91896 usb camcontrol(8): Serial Number of USB Memory Sticks is n o usb/91811 usb [umass] Compact Flash in HP Photosmart 2610 return " o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91538 usb [ulpt] [patch] Unable to print to EPSON CX3500 o usb/91283 usb [boot] [regression] booting very slow with usb devices o usb/91238 usb [umass] USB tape unit fails to write a second tape fil o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas o usb/89954 usb [umass] [panic] USB Disk driver race condition? s usb/89003 usb [request] LaCie Firewire drive not properly supported o usb/88743 usb [hang] [regression] USB makes kernel hang at boot (reg o usb/88408 usb [axe] axe0 read PHY failed o usb/87648 usb [mouse] Logitech USB-optical mouse problem. o usb/87224 usb [usb] Cannot mount USB Zip750 o usb/86767 usb [umass] [patch] bogus "slice starts beyond end of the o usb/86298 usb [mouse] Known good USB mouse won't work with correct s s usb/85067 usb [uscanner] Cannot attach ScanJet 4300C to usb device s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/83863 usb [ugen] Communication problem between opensc/openct via o usb/83756 usb [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe o usb/83563 usb [umass] [panic] Page Fault while detaching Mpman Usb d o usb/83504 usb [kernel] [patch] SpeedTouch USB stop working on recent o usb/82660 usb [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic s usb/82569 usb [umass] [panic] USB mass storage plug/unplug causes sy o usb/82520 usb [udbp] [reboot] Reboot when USL101 connected o usb/82350 usb [ucom] [panic] null pointer dereference in USB stack o usb/81621 usb [ehci] [hang] external hd hangs under load on ehci o usb/80935 usb [uvisor] [patch] uvisor.c is not work with CLIE TH55. o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me s usb/80777 usb [request] usb_rem_task() should wait for callback to c s usb/80776 usb [udav] [request] UDAV device driver shouldn't use usb_ o usb/80774 usb [patch] have "usbd_find_desc" in line with the other " f usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails f usb/80040 usb [sound] [hang] Use of sound mixer causes system freeze o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/78984 usb [umass] [patch] Creative MUVO umass failure f usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/76732 usb [ums] Mouse problems with USB KVM Switch o usb/76653 usb [umass] [patch] Problem with Asahi Optical usb device o usb/76461 usb [umass] disklabel of umass(4)-CAM(4)-da(4) not used by f usb/76395 usb [uhci] USB printer does not work, usbdevs says "addr 0 s usb/75928 usb [umass] [request] Cytronix SmartMedia card (SMC) reade o usb/75800 usb [ucom] ucom1: init failed STALLED error in time of syn f usb/75797 usb [sound] [regression] 5.3-STABLE(2005 1/4) detect USB h o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for f usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) f usb/74771 usb [umass] [hang] mounting write-protected umass device a s usb/74453 usb [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL o usb/74211 usb [umass] USB flash drive causes CAM status 0x4 on 4.10R o usb/73307 usb [panic] Kernel panics on USB disconnect s usb/72733 usb [ucom] [request] Kyocera 7135 Palm OS connection probl o usb/71455 usb [umass] Slow USB umass performance of 5.3 o usb/71417 usb [ugen] Cryptoflex e-gate USB token (ugen0) communicati o usb/71416 usb [ugen] Cryptoflex e-gate USB token (ugen0) detach is n o usb/71280 usb [aue] aue0 device (linksys usb100tx) doesn't work in 1 o usb/71155 usb [ulpt] misbehaving usb-printer hangs processes, causes o usb/70523 usb [umct] [patch] umct sending/receiving wrong characters o usb/69006 usb [usbdevs] [patch] Apple Cinema Display hangs USB ports o usb/68232 usb [ugen] [patch] ugen(4) isochronous handling correction o usb/67301 usb [uftdi] [panic] RTS and system panic o usb/66547 usb [ucom] Palm Tungsten T USB does not initialize correct o usb/63621 usb [umass] [panic] USB MemoryStick Reader stalls/crashes s usb/62257 usb [umass] [request] card reader UCR-61S2B is only half-s o usb/59698 usb [keyboard] [patch] Rework of ukbd HID to AT code trans s bin/57255 usb [patch] usbd(8) and multi-function devices s usb/52026 usb [usb] [request] umass driver support for InSystem ISD2 s usb/51958 usb [urio] [patch] update for urio driver o usb/40948 usb [umass] [request] USB HP CDW8200 does not work o usb/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem 315 problems total. From owner-freebsd-usb@FreeBSD.ORG Mon Oct 18 15:40:20 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 17FEF10656BA; Mon, 18 Oct 2010 15:40:20 +0000 (UTC) Date: Mon, 18 Oct 2010 15:40:20 +0000 From: Alexander Best To: Hans Petter Selasky Message-ID: <20101018154020.GA10306@freebsd.org> References: <20100914002017.GA97489@freebsd.org> <201009141400.00427.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201009141400.00427.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: USB_VERBOSE and vendor-/productnames X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2010 15:40:20 -0000 On Tue Sep 14 10, Hans Petter Selasky wrote: > On Tuesday 14 September 2010 02:20:17 Alexander Best wrote: > > hi there, > > > > a lot of people report issues where usbconfig doesn't show a vendor or > > device name, although an usbdevs entry exists. i found a few replies to > > those reports by hps@ stating that USB_VERBOSE needs to be enabled. > > > > could anybody explain why? if that option needs to be enabled in order to > > see vendor and device names in usbconfig how come that even without it i > > see most of the vendor and device names with usbconfig: > > Hi, > > The reason the option is not default, is that the verbose database consume a > couple of hundred kilobytes. does "usbdevs" actually get compiled into the kernel if USB_VERBOSE has been defined? that would explain the extra size. why not do it like the pci database? simply add usbdevs to /usr/share/misc and look for entries in that file for each request. cheers. alex > > > > > ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) > > pwr=SAVE ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL > > (12Mbps) pwr=SAVE ugen2.1: at usbus2, cfg=0 md=HOST > > spd=FULL (12Mbps) pwr=SAVE ugen3.1: at usbus3, cfg=0 > > md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen4.1: at > > usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen5.1: > Intel> at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen6.1: > root HUB Intel> at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE > > ugen7.1: at usbus7, cfg=0 md=HOST spd=HIGH (480Mbps) > > pwr=SAVE ugen3.2: at usbus3, cfg=0 md=HOST > > spd=HIGH (480Mbps) pwr=SAVE ugen1.2: at usbus1, > > cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen1.3: > Razer> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > > > > my guess would be that these devices are missing the iManufacturer and/or > > iProduct string, but that's just a wild guess. > > > > if that is the case wouldn't it be possible to check for a usbdevs entry in > > case one of those strings don't exist and if there's an entry in usbdevs > > use it? > > > > i think the option USB_VERBOSE is not really accurate in this particular > > case. people who want usbconfig to output the vendor and product name > > actually want less verbosity (i.e. no product/vendor hex ids). > > I'm not sure if compiling this information into usbdevs will be any better. > > --HPS -- a13x From owner-freebsd-usb@FreeBSD.ORG Mon Oct 18 15:40:59 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 3A7EB1065696; Mon, 18 Oct 2010 15:40:59 +0000 (UTC) Date: Mon, 18 Oct 2010 15:40:59 +0000 From: Alexander Best To: Nick Hibma Message-ID: <20101018154059.GB10306@freebsd.org> References: <20100914002017.GA97489@freebsd.org> <201009141400.00427.hselasky@c2i.net> <20100914202546.GA80216@freebsd.org> <201009142231.41221.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: ?FreeBSD USB Mailing List? Subject: Re: USB_VERBOSE and vendor-/productnames X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2010 15:40:59 -0000 On Thu Sep 16 10, Nick Hibma wrote: > From: > > http://www.linux-usb.org/usb-ids.html > > "The contents of the database and the generated files can be distributed under the terms of either the GNU General Public License (version 2 or later) or of the 3-clause BSD License." > > Do you want me make this list available in our source tree? any progress on this task? ;) cheers. alex > > Steps: > 1) Write a script to download it and convert it to our usbdevs*.h files. > 2) Match the entries with our own and add usbdevs*_legacy.h for FBSD8 systems, so recompilation of existing drivers is straightforward. > 3) Test. Review. Bikeshed. Rinse. Repeat. > 4) Commit. > > Nick > > > On 14 Sep 2010, at 22:31, Hans Petter Selasky wrote: > > > On Tuesday 14 September 2010 22:25:46 Alexander Best wrote: > >> also i've been wondering why freebsd keeps its own set of a usb device db? > >> the databse at http://www.linux-usb.org/usb-ids.html seems very active. > >> can't we just use a script to create usbdevs from that db? that's how pci > >> ids are mapped to vendors/products on freebsd (see > >> http://www.mail-archive.com/freebsd-current@freebsd.org/msg124948.html). > > > > If we don't have to GPL the resulting .h and .c files. > > > > --HPS > > _______________________________________________ > > freebsd-usb@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > -- a13x From owner-freebsd-usb@FreeBSD.ORG Tue Oct 19 14:43:14 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1B62106566C; Tue, 19 Oct 2010 14:43:14 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id 2DAE18FC0A; Tue, 19 Oct 2010 14:43:13 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=yevn+QCjI6xy199BDvBOOiO14qYvyLq62he9tTtU3M8= c=1 sm=1 a=xqJwjQdkl30A:10 a=N659UExz7-8A:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=4VszKAkPqfOYw1deoAAA:9 a=lJYFm_T3xtMOA7D5Tn_9nvo7QEUA:4 a=pILNOxqGKmIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 37116554; Tue, 19 Oct 2010 16:43:12 +0200 To: "Wilkinson, Alex" From: Hans Petter Selasky X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'( =?windows-1252?q?=3B=5FIjlA=3A=0A=09hGE=2E=2EEw?=, =?windows-1252?q?XAQ*o=23=5C/M=7ESC=3DS1-f9=7BEzRfT=27=7CHhll5Q=5Dha5Bt-s=7Co?= =?windows-1252?q?TlKMusi=3A1e=5BwJl=7Dkd=7DGR=0A=09Z0adGx-x=5F0zGbZj=27e?=(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' Date: Tue, 19 Oct 2010 16:44:28 +0200 MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <201010191644.28140.hselasky@c2i.net> Cc: freebsd-emulation@freebsd.org, freebsd-usb@freebsd.org Subject: Re: Hope for USB support? X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 14:43:14 -0000 Hi, After some closer investigation, it turns out that the VirtualBox USB support in SVN is only working for control endpoints. To get an ordinary USB device working, the software still needs some work? My offer is still valid. Send me an e-mail if you want to pay for fixing the USB support in VirtualBox under FreeBSD. --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Oct 20 00:24:15 2010 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 1BFAA1065670; Wed, 20 Oct 2010 00:24:15 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E57FF8FC08; Wed, 20 Oct 2010 00:24:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o9K0OEGZ084681; Wed, 20 Oct 2010 00:24:14 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o9K0OE50084677; Wed, 20 Oct 2010 00:24:14 GMT (envelope-from arundel) Date: Wed, 20 Oct 2010 00:24:14 GMT Message-Id: <201010200024.o9K0OE50084677@freefall.freebsd.org> To: spawk@acm.poly.edu, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/130230: [usb67] [usb] [cam] Samsung Electronics YP-U3 does not attach in 7.1-RELEASE X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 00:24:15 -0000 Old Synopsis: Samsung Electronics YP-U3 does not attach in 7.1-RELEASE New Synopsis: [usb67] [usb] [cam] Samsung Electronics YP-U3 does not attach in 7.1-RELEASE State-Changed-From-To: open->feedback State-Changed-By: arundel State-Changed-When: Wed Oct 20 00:20:46 UTC 2010 State-Changed-Why: Does this issue still exist? Do you still need to apply the quirks you posted below or does your device work out of the box? http://www.freebsd.org/cgi/query-pr.cgi?pr=130230 From owner-freebsd-usb@FreeBSD.ORG Wed Oct 20 00:27:48 2010 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 130671065670; Wed, 20 Oct 2010 00:27:48 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DCD298FC19; Wed, 20 Oct 2010 00:27:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o9K0RleN084779; Wed, 20 Oct 2010 00:27:47 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o9K0Rl39084775; Wed, 20 Oct 2010 00:27:47 GMT (envelope-from arundel) Date: Wed, 20 Oct 2010 00:27:47 GMT Message-Id: <201010200027.o9K0Rl39084775@freefall.freebsd.org> To: tim@pcbsd.org, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/123509: [umass] [cam] [usb67] continuous reset Samsung SGH-G600 phone X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 00:27:48 -0000 Old Synopsis: [umass] continuous reset Samsung SGH-G600 phone New Synopsis: [umass] [cam] [usb67] continuous reset Samsung SGH-G600 phone State-Changed-From-To: open->closed State-Changed-By: arundel State-Changed-When: Wed Oct 20 00:25:42 UTC 2010 State-Changed-Why: Closed per submitters request. http://www.freebsd.org/cgi/query-pr.cgi?pr=123509 From owner-freebsd-usb@FreeBSD.ORG Wed Oct 20 00:52:48 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id C4571106566B; Wed, 20 Oct 2010 00:52:48 +0000 (UTC) Date: Wed, 20 Oct 2010 00:52:48 +0000 From: Alexander Best To: freebsd-usb@freebsd.org Message-ID: <20101020005248.GA94374@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline Subject: fixing PR 130230 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 00:52:48 -0000 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline hi there, this patch should fix PR 130230. cheers. alex -- a13x --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_da.c.diff" diff --git a/sys/cam/scsi/scsi_da.c b/sys/cam/scsi/scsi_da.c index 7729ecc..7125c2a 100644 --- a/sys/cam/scsi/scsi_da.c +++ b/sys/cam/scsi/scsi_da.c @@ -547,9 +547,9 @@ static struct da_quirk_entry da_quirk_table[] = { /* * Samsung YP-U3 mp3-player - * PR: 125398 + * PR: 125398, 130230 */ - {T_DIRECT, SIP_MEDIA_REMOVABLE, "Samsung", "YP-U3", + {T_DIRECT, SIP_MEDIA_REMOVABLE, "Samsung*", "YP-U3*", "*"}, /*quirks*/ DA_Q_NO_SYNC_CACHE }, { --0F1p//8PRICkK4MW-- From owner-freebsd-usb@FreeBSD.ORG Wed Oct 20 01:22:00 2010 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 A6CE91065672; Wed, 20 Oct 2010 01:22:00 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7B67E8FC1A; Wed, 20 Oct 2010 01:22:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o9K1M0dH046364; Wed, 20 Oct 2010 01:22:00 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o9K1LxM9046360; Wed, 20 Oct 2010 01:21:59 GMT (envelope-from arundel) Date: Wed, 20 Oct 2010 01:21:59 GMT Message-Id: <201010200121.o9K1LxM9046360@freefall.freebsd.org> To: crazyalexnt@inbox.ru, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/143790: [boot] [cam] can not boot from usb hdd X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 01:22:00 -0000 Old Synopsis: [boot] can not boot from usb hdd New Synopsis: [boot] [cam] can not boot from usb hdd State-Changed-From-To: open->analyzed State-Changed-By: arundel State-Changed-When: Wed Oct 20 01:11:21 UTC 2010 State-Changed-Why: As mav@ pointed out it is possible to fix this issue by setting kern.cam.boot_delay so devices/controllers on slow systems have time to initialize. However what needs to be done is to add a default entry to conf/GENERIC on platforms like mips or arm. Right now however kern.cam.boot_delay is only a sysctl tunable and no kern option. http://www.freebsd.org/cgi/query-pr.cgi?pr=143790 From owner-freebsd-usb@FreeBSD.ORG Wed Oct 20 12:47:25 2010 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 BDD3C1065672; Wed, 20 Oct 2010 12:47:25 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 92A2B8FC16; Wed, 20 Oct 2010 12:47:25 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o9KClP8O093642; Wed, 20 Oct 2010 12:47:25 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o9KClP0W093638; Wed, 20 Oct 2010 12:47:25 GMT (envelope-from arundel) Date: Wed, 20 Oct 2010 12:47:25 GMT Message-Id: <201010201247.o9KClP0W093638@freefall.freebsd.org> To: spawk@acm.poly.edu, arundel@FreeBSD.org, freebsd-usb@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: usb/130230: [quirk] [usb67] [usb] [cam] [umass] Samsung Electronics YP-U3 does not attach in 7.1-RELEASE X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 12:47:25 -0000 Old Synopsis: [usb67] [usb] [cam] Samsung Electronics YP-U3 does not attach in 7.1-RELEASE New Synopsis: [quirk] [usb67] [usb] [cam] [umass] Samsung Electronics YP-U3 does not attach in 7.1-RELEASE State-Changed-From-To: feedback->suspended State-Changed-By: arundel State-Changed-When: Wed Oct 20 12:39:17 UTC 2010 State-Changed-Why: In order to add a quirk for this device it's necessary to have the output of 'usbconfig dump_device_desc'. The current patch may collide with a previous revision of the device. See PR 125398. http://www.freebsd.org/cgi/query-pr.cgi?pr=130230 From owner-freebsd-usb@FreeBSD.ORG Wed Oct 20 15:30:40 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 2B6F51065670; Wed, 20 Oct 2010 15:30:40 +0000 (UTC) Date: Wed, 20 Oct 2010 15:30:40 +0000 From: Alexander Best To: freebsd-usb@freebsd.org, freebsd-current@freebsd.org Message-ID: <20101020153040.GA3184@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Cc: Subject: serious issue caused by usb device, stalling almost all operations X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 15:30:40 -0000 hi there, i'm running HEAD (r213495; amd64). i stumbled upon this severe problem: after attaching my mobile phone, it simply resets without doing mount or anything. however after letting the device come up again it won't show up in the console. after detaching it the usb subsystem seemed to have completely crashed. but that's not all. the following programs now simply hang without producing any output C-C won't do anything: - dmesg - top - ps - killall - camcontrol devlist - usbconfig i cannot even kill the apps, since top and ps aren't working so there's no way to find out the PIDs. using 'killall dmesg' e.g. won't work either, since killall will also stall. this is the console output which i could grab with 'vidcontrol -H -P < /dev/ttyv0' (since dmesg doesn't work anymore): ugen3.3: at usbus3 umass0: on usbus3 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI status: Check Condition (probe0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to rea dy change, medium may have changed) da0 at umass-sim0 bus 0 scbus9 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 3777MB (7736320 512 byte sectors: 255H 63S/T 481C) (da0:umass-sim0:0:0:0): AutoSense failed ugen3.3: at usbus3 (disconnected) umass0: at uhub8, port 3, addr 3 (disconnected) (da0:umass-sim0:0:0:0): AutoSense failed (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): Invalidating pack (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scsi status == 0x0 (da0:umass-sim0:0:0:0): removing device entry lock order reversal: 1st 0xffffffff80a37d50 GEOM topology (GEOM topology) @ /usr/src/sys/geom/label/ g_label.c:320 2nd 0xffffffff808387a0 sysctl lock (sysctl lock) @ /usr/src/sys/kern/kern_sysct l.c:257 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x35 kdb_backtrace() at kdb_backtrace+0x4e _witness_debugger() at _witness_debugger+0x29 witness_checkorder() at witness_checkorder+0xad2 _sx_xlock() at _sx_xlock+0xae sysctl_ctx_free() at sysctl_ctx_free+0x2e dacleanup() at dacleanup+0x65 camperiphfree() at camperiphfree+0x152 cam_periph_release_locked() at cam_periph_release_locked+0x84 cam_periph_release() at cam_periph_release+0x6d daclose() at daclose+0x223 g_disk_access() at g_disk_access+0x21c g_access() at g_access+0x3b7 g_label_taste() at g_label_taste+0x3be g_new_provider_event() at g_new_provider_event+0x145 one_event() at one_event+0x2d5 g_run_events() at g_run_events+0xe g_event_procbody() at g_event_procbody+0x8b fork_exit() at fork_exit+0xfd fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff800003ecf0, rbp = 0 --- cheers. alex -- a13x From owner-freebsd-usb@FreeBSD.ORG Wed Oct 20 16:10:13 2010 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 26DA7106564A for ; Wed, 20 Oct 2010 16:10:13 +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 EF6948FC19 for ; Wed, 20 Oct 2010 16:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o9KGAC4r000312 for ; Wed, 20 Oct 2010 16:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o9KGACFi000311; Wed, 20 Oct 2010 16:10:12 GMT (envelope-from gnats) Date: Wed, 20 Oct 2010 16:10:12 GMT Message-Id: <201010201610.o9KGACFi000311@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: AlexNT Cc: Subject: Re: usb/143790: [boot] [cam] can not boot from usb hdd X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: AlexNT List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 16:10:13 -0000 The following reply was made to PR usb/143790; it has been noted by GNATS. From: AlexNT To: bug-followup@FreeBSD.org, crazyalexnt@inbox.ru Cc: Subject: Re: usb/143790: [boot] [cam] can not boot from usb hdd Date: Wed, 20 Oct 2010 13:58:35 +0600 I checked the option "kern.cam.boot_delay = 10000", pointed it in / boot / loader.conf in FreeBSD 8.1 - works fine in the patch is not necessary. From owner-freebsd-usb@FreeBSD.ORG Wed Oct 20 17:36:32 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29509106564A; Wed, 20 Oct 2010 17:36:32 +0000 (UTC) (envelope-from justin.victoria@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id BE7818FC17; Wed, 20 Oct 2010 17:36:31 +0000 (UTC) Received: by ywh2 with SMTP id 2so2202392ywh.13 for ; Wed, 20 Oct 2010 10:36:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :in-reply-to:message-id:references:user-agent:mime-version :content-type; bh=A/bWBBIW5xxHlXqe8+baguXSiFmYBDSHV4mDeYcfvTQ=; b=RzkjpcEWcrmgiZNgnNrZ6Hk4Y6h3uacVWoFxJMQMEAA5XfYpvjOv3kNtXfnm32UwAp fgBNIzq3EwGWKAfwe4lDMzlRTecRDD9ua9lkjGWznFybY5/9q70wXbu2xl96DmCvZjnq o9GPw2scZUFQ0Vxzl8lM8suBmUdfJi5oYe/ms= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version:content-type; b=DAyN2Okp/V9/bZvHXDoZp0WQSJnCtocgzv1bXrXvP7D7clqF99L2yFAKRzEwGJG3kc D8cYGQWMjVFn4B8S+LYfo2fYLw3XfAEezicSMjnTCMm8pJuxoRJyR5AR+zk4/DfT2VII 7UlqVSkjdIA4FJZ9EJ161/zEh2Of9dw9yb5nA= Received: by 10.100.136.7 with SMTP id j7mr5505041and.64.1287594671159; Wed, 20 Oct 2010 10:11:11 -0700 (PDT) Received: from [192.168.1.169] (cpe-67-49-120-184.socal.res.rr.com [67.49.120.184]) by mx.google.com with ESMTPS id w3sm469051anw.25.2010.10.20.10.11.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 10:11:10 -0700 (PDT) Date: Wed, 20 Oct 2010 10:11:04 -0700 (PDT) From: jcv To: Alexander Best In-Reply-To: <20101020153040.GA3184@freebsd.org> Message-ID: References: <20101020153040.GA3184@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org Subject: Re: serious issue caused by usb device, stalling almost all operations X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 17:36:32 -0000 Sorry, I replied to another message regarding this matter by mistake.. Here is my intended response to the USB issue: Wow, i mounted my phone last nite and nothing that bad happened to my FreeBSD server. The only negative issue that I had was my Phone reset. This definately makes me nervous plugging my phone in now. Is there any other messages in /var/log/messages?? hbca# dmesg | grep da rum0: need multicast update callback da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 scbus0 target 0 lun 1 da1: Removable Direct Access SCSI-2 device da1: 1.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry (da1:umass-sim0:0:0:1): lost device (da1:umass-sim0:0:0:1): removing device entry da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 scbus0 target 0 lun 1 da1: Removable Direct Access SCSI-2 device da1: 1.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry (da1:umass-sim0:0:0:1): lost device (da1:umass-sim0:0:0:1): removing device entry hbca# On Wed, 20 Oct 2010, Alexander Best wrote: > hi there, > > i'm running HEAD (r213495; amd64). i stumbled upon this severe problem: > > after attaching my mobile phone, it simply resets without doing mount or > anything. however after letting the device come up again it won't show up in > the console. after detaching it the usb subsystem seemed to have completely > crashed. but that's not all. the following programs now simply hang without > producing any output C-C won't do anything: > > - dmesg > - top > - ps > - killall > - camcontrol devlist > - usbconfig > > i cannot even kill the apps, since top and ps aren't working so there's no way > to find out the PIDs. using 'killall dmesg' e.g. won't work either, since > killall will also stall. > > this is the console output which i could grab with > 'vidcontrol -H -P < /dev/ttyv0' (since dmesg doesn't work anymore): > > ugen3.3: at usbus3 > umass0: on usbus3 > (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error > (probe0:umass-sim0:0:0:0): SCSI status: Check Condition > (probe0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to rea > dy change, medium may have changed) > da0 at umass-sim0 bus 0 scbus9 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 3777MB (7736320 512 byte sectors: 255H 63S/T 481C) > (da0:umass-sim0:0:0:0): AutoSense failed > ugen3.3: at usbus3 (disconnected) > umass0: at uhub8, port 3, addr 3 (disconnected) > (da0:umass-sim0:0:0:0): AutoSense failed > (da0:umass-sim0:0:0:0): lost device > (da0:umass-sim0:0:0:0): Invalidating pack > (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scsi status == > 0x0 > (da0:umass-sim0:0:0:0): removing device entry > lock order reversal: > 1st 0xffffffff80a37d50 GEOM topology (GEOM topology) @ /usr/src/sys/geom/label/ > g_label.c:320 > 2nd 0xffffffff808387a0 sysctl lock (sysctl lock) @ /usr/src/sys/kern/kern_sysct > l.c:257 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x35 > kdb_backtrace() at kdb_backtrace+0x4e > _witness_debugger() at _witness_debugger+0x29 > witness_checkorder() at witness_checkorder+0xad2 > _sx_xlock() at _sx_xlock+0xae > sysctl_ctx_free() at sysctl_ctx_free+0x2e > dacleanup() at dacleanup+0x65 > camperiphfree() at camperiphfree+0x152 > cam_periph_release_locked() at cam_periph_release_locked+0x84 > cam_periph_release() at cam_periph_release+0x6d > daclose() at daclose+0x223 > g_disk_access() at g_disk_access+0x21c > g_access() at g_access+0x3b7 > g_label_taste() at g_label_taste+0x3be > g_new_provider_event() at g_new_provider_event+0x145 > one_event() at one_event+0x2d5 > g_run_events() at g_run_events+0xe > g_event_procbody() at g_event_procbody+0x8b > fork_exit() at fork_exit+0xfd > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff800003ecf0, rbp = 0 --- > > cheers. > alex > > -- > a13x > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-usb@FreeBSD.ORG Wed Oct 20 17:54:46 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F0AB10656A4; Wed, 20 Oct 2010 17:54:46 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id 253908FC0C; Wed, 20 Oct 2010 17:54:44 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=iBCGAMPDYtSF9sDXX85uHY3wcnYctfVT8vFpe3qPflY= c=1 sm=1 a=88e7-T71Oz4A:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=zk-QPIRbcTxHS1SbQ3EA:9 a=Moe5nSEDNAsiRCxPdgNk8Or1ydcA:4 a=wPNLvfGTeEIA:10 a=iTBbjxRKQiG1Xzjl:21 a=YgJZt3ZVx1deoEbO:21 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 38038615; Wed, 20 Oct 2010 19:54:43 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Wed, 20 Oct 2010 19:55:56 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <20101020153040.GA3184@freebsd.org> In-Reply-To: <20101020153040.GA3184@freebsd.org> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201010201955.56816.hselasky@c2i.net> Cc: Alexander Best , mav@freebsd.org, freebsd-current@freebsd.org Subject: Re: serious issue caused by usb device, stalling almost all operations X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 17:54:46 -0000 On Wednesday 20 October 2010 17:30:40 Alexander Best wrote: > hi there, > > i'm running HEAD (r213495; amd64). i stumbled upon this severe problem: > > after attaching my mobile phone, it simply resets without doing mount or > anything. however after letting the device come up again it won't show up > in the console. after detaching it the usb subsystem seemed to have > completely crashed. but that's not all. the following programs now simply > hang without producing any output C-C won't do anything: > > - dmesg > - top > - ps > - killall > - camcontrol devlist > - usbconfig That's most likely because USB's umass driver is waiting for cam to drain. Possibly some refcounting is not correct. I suspect this is not a USB problem. Try to enter into the debugger, and look for backtrace for function stuck in umass_detach. --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Oct 21 15:02:41 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58B861065672 for ; Thu, 21 Oct 2010 15:02:41 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2-6.sentex.ca [IPv6:2607:f3e0:80:80::2]) by mx1.freebsd.org (Postfix) with ESMTP id 162468FC14 for ; Thu, 21 Oct 2010 15:02:40 +0000 (UTC) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.14.4/8.14.4) with ESMTP id o9LF2WpQ008904 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 21 Oct 2010 11:02:32 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.14.4/8.14.4) with ESMTP id o9LF2WYf086752 for ; Thu, 21 Oct 2010 11:02:32 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <201010211502.o9LF2WYf086752@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Thu, 21 Oct 2010 11:02:30 -0400 To: freebsd-usb@freebsd.org From: Mike Tancsa Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.67 on 205.211.164.50 Subject: USB_ERR_TIMEOUT and USB_ERR_STALLED X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 15:02:41 -0000 I am trying to use RELENG_8 to monitor a number of APC upses and it seems when there are more than one, I start to see a lot of USB errors with the devices "coming and going" In the logs, I see a lot of # grep USB /var/log/all.log | tail Oct 21 10:24:05 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:25:47 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:27:45 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:29:44 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:30:35 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 Oct 21 10:32:35 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:37:04 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:38:38 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:44:14 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 Oct 21 10:45:09 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 # usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.3: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.4: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.5: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.6: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.7: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.8: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen3.9: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.10: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.11: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON This is with a kernel from Oct 4th, i386. Any idea what might be up or how to debug this ?? Setting hw.usb.debug to anything > 0 causes the system to almost hang under the load unfortunately. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike From owner-freebsd-usb@FreeBSD.ORG Thu Oct 21 17:46:17 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5AD41065693 for ; Thu, 21 Oct 2010 17:46:17 +0000 (UTC) (envelope-from mgmartin@comcast.net) Received: from mx.appliedtechnicalknowledge.com (portfolioframework.com [173.14.31.49]) by mx1.freebsd.org (Postfix) with ESMTP id A1D6E8FC1F for ; Thu, 21 Oct 2010 17:46:17 +0000 (UTC) Received: from [10.0.0.92] (gandalf.martins.home [10.0.0.92]) by gimle.appliedtechnicalknowledge.com (Postfix) with ESMTPSA id 661D29590E for ; Thu, 21 Oct 2010 01:29:58 -0600 (MDT) Message-ID: <4CBFEBF5.30203@comcast.net> Date: Thu, 21 Oct 2010 01:29:57 -0600 From: Michael Martin User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20101012 Thunderbird/3.1.4 MIME-Version: 1.0 To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: USB 3.0 Fails To Attach Western Digital My Book 3.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 17:46:17 -0000 Thanks for the new USB 3.0 effort! I'm testing it out on 9.0-CURRENT amd64. The controller seems to find a 2.0 usb stick fine. However, when I plug in a Western Digital 3.0 drive, the device fails to attach. The WD drive attaches fine when plugging into a 2.0 port on the motherboard. Controller info: xhci0@pci0:5:0:0: class=0x0c0330 card=0xffffffff chip=0x01941033 rev=0x03 hdr=0x00 vendor = 'NEC Electronics Hong Kong' class = serial bus subclass = USB bar [10] = type Memory, range 64, base 0xfbbfe000, size 8192, enabled cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 05[70] = MSI supports 8 messages, 64 bit cap 11[90] = MSI-X supports 8 messages in map 0x10 cap 10[a0] = PCI-Express 2 endpoint max data 128(128) link x1(x1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected ecap 0003[140] = Serial 1 ffffffffffffffff ecap 0018[150] = unknown 1 WD 3.0 Drive Info ( while plugged into the 2.0 port ): ugen3.4: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0210 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x1058 idProduct = 0x1123 bcdDevice = 0x1010 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 Output when plugging in the Western Digital 3.0 into the 3.0 port: Oct 21 01:03:54 gandalf root: Unknown USB device: vendor 0x1058 product 0x1123 bus uhub4 Oct 21 01:03:54 gandalf kernel: ugen4.2: at usbus4 Oct 21 01:03:54 gandalf kernel: umass0: on usbus4 Oct 21 01:03:54 gandalf kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000 Oct 21 01:03:55 gandalf kernel: umass0:9:0:-1: Attached to scbus9 Oct 21 01:03:57 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 error=28 Oct 21 01:03:57 gandalf last message repeated 2 times Oct 21 01:03:57 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= offset= size= error= Oct 21 01:04:03 gandalf kernel: ugen4.2: at usbus4 (disconnected) Oct 21 01:04:03 gandalf kernel: umass0: at uhub4, port 2, addr 1 (disconnected) Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): lost device Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): got CAM status 0xa Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): fatal error, failed to attach to device Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0: Oct 21 01:04:03 gandalf kernel: 0:0): removing device entry Oct 21 01:04:14 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 error=28 Oct 21 01:04:14 gandalf last message repeated 2 times Oct 21 01:04:14 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= offset= size= error= Output when plugging in the WD 3.0 into the 2.0 port: Oct 21 01:15:20 gandalf root: Unknown USB device: vendor 0x1058 product 0x1123 bus uhub3 Oct 21 01:15:20 gandalf kernel: ugen3.4: at usbus3 Oct 21 01:15:20 gandalf kernel: umass0: on usbus3 Oct 21 01:15:20 gandalf kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000 Oct 21 01:15:21 gandalf kernel: umass0:9:0:-1: Attached to scbus9 Oct 21 01:15:28 gandalf kernel: da0 at umass-sim0 bus 0 scbus9 target 0 lun 0 Oct 21 01:15:28 gandalf kernel: da0: Fixed Direct Access SCSI-4 device Oct 21 01:15:28 gandalf kernel: da0: 40.000MB/s transfers Oct 21 01:15:28 gandalf kernel: da0: 953867MB (1953519616 512 byte sectors: 255H 63S/T 121600C) Output when plugging in 2.0 device into the 3.0 port: Oct 21 01:09:54 gandalf root: Unknown USB device: vendor 0x090c product 0x1000 bus uhub4 Oct 21 01:09:54 gandalf kernel: ugen4.2: at usbus4 Oct 21 01:09:54 gandalf kernel: umass1: on usbus4 Oct 21 01:09:54 gandalf kernel: umass1: SCSI over Bulk-Only; quirks = 0x0000 Oct 21 01:09:55 gandalf kernel: umass1:10:1:-1: Attached to scbus10 Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) Oct 21 01:09:56 gandalf kernel: da1 at umass-sim1 bus 1 scbus10 target 0 lun 0 Oct 21 01:09:56 gandalf kernel: da1: Fixed Direct Access SCSI-0 device Oct 21 01:09:56 gandalf kernel: da1: 40.000MB/s transfers Oct 21 01:09:56 gandalf kernel: da1: 956MB (1957888 512 byte sectors: 64H 32S/T 956C) --Michael From owner-freebsd-usb@FreeBSD.ORG Thu Oct 21 20:52:48 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50221106566C; Thu, 21 Oct 2010 20:52:48 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id 7747E8FC0C; Thu, 21 Oct 2010 20:52:46 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=5OBHFxb9I47YZ7HELXzI6cL6pwPTRnd5uxbD1DPQ4WY= c=1 sm=1 a=teY7EFdY6K0A:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=pM0583-Z2yWqtI276ScA:9 a=vAPkElypu_rBTkBhasYA:7 a=EOBJt3ralku4Iihl8aLsg3o9MLQA:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe05.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 38138037; Thu, 21 Oct 2010 22:52:45 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Thu, 21 Oct 2010 22:53:57 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <4CBFEBF5.30203@comcast.net> In-Reply-To: <4CBFEBF5.30203@comcast.net> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201010212253.57555.hselasky@c2i.net> Cc: mav@freebsd.org Subject: Re: USB 3.0 Fails To Attach Western Digital My Book 3.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 20:52:48 -0000 On Thursday 21 October 2010 09:29:57 Michael Martin wrote: > Thanks for the new USB 3.0 effort! > > I'm testing it out on 9.0-CURRENT amd64. The controller seems to find a > 2.0 usb stick fine. However, when I plug in a Western Digital 3.0 > drive, the device fails to attach. The WD drive attaches fine when > plugging into a 2.0 port on the motherboard. > > Controller info: > > xhci0@pci0:5:0:0: class=0x0c0330 card=0xffffffff chip=0x01941033 > rev=0x03 hdr=0x00 > vendor = 'NEC Electronics Hong Kong' > class = serial bus > subclass = USB > bar [10] = type Memory, range 64, base 0xfbbfe000, size 8192, > enabled cap 01[50] = powerspec 3 supports D0 D3 current D0 > cap 05[70] = MSI supports 8 messages, 64 bit > cap 11[90] = MSI-X supports 8 messages in map 0x10 > cap 10[a0] = PCI-Express 2 endpoint max data 128(128) link x1(x1) > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0003[140] = Serial 1 ffffffffffffffff > ecap 0018[150] = unknown 1 > > WD 3.0 Drive Info ( while plugged into the 2.0 port ): > > ugen3.4: at usbus3, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0210 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x1058 > idProduct = 0x1123 > bcdDevice = 0x1010 > iManufacturer = 0x0001 > iProduct = 0x0002 > iSerialNumber = 0x0003 > bNumConfigurations = 0x0001 > > Output when plugging in the Western Digital 3.0 into the 3.0 port: > > Oct 21 01:03:54 gandalf root: Unknown USB device: vendor 0x1058 product > 0x1123 bus uhub4 > Oct 21 01:03:54 gandalf kernel: ugen4.2: at usbus4 > Oct 21 01:03:54 gandalf kernel: umass0: class 0/0, rev 3.00/10.10, addr 1> on usbus4 > Oct 21 01:03:54 gandalf kernel: umass0: SCSI over Bulk-Only; quirks = > 0x0000 > Oct 21 01:03:55 gandalf kernel: umass0:9:0:-1: Attached to scbus9 > Oct 21 01:03:57 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 error=28 > Oct 21 01:03:57 gandalf last message repeated 2 times > Oct 21 01:03:57 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= > offset= size= error= > Oct 21 01:04:03 gandalf kernel: ugen4.2: at usbus4 > (disconnected) > Oct 21 01:04:03 gandalf kernel: umass0: at uhub4, port 2, addr 1 > (disconnected) > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): lost device > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): got CAM status 0xa > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): fatal error, > failed to attach to device > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0: > Oct 21 01:04:03 gandalf kernel: 0:0): removing device entry > Oct 21 01:04:14 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 error=28 > Oct 21 01:04:14 gandalf last message repeated 2 times > Oct 21 01:04:14 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= > offset= size= error= > Hi, 1) Try to enable UMASS debugging (you maybe need to rebuild kernel with options USB_DEBUG): sysctl hw.usb.umass.debug=-1 2) Also try to boot without umass in the kernel. What is the output from usbconfig, like descriptors, etc ... in USB 3.0 mode. --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Oct 21 20:55:02 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F95E1065670; Thu, 21 Oct 2010 20:55:02 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id 854CC8FC0A; Thu, 21 Oct 2010 20:55:01 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=omSrwDgyMf70S47Fr5SNr0rQzcmIOo0IafWlB/wSLLo= c=1 sm=1 a=BJjCyyNTvkcA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=yc1GMiH63V9npsZAuQQA:9 a=1ELZ4b7q8BO3dwzp14bNOOOOlpAA:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 39169967; Thu, 21 Oct 2010 22:54:59 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Thu, 21 Oct 2010 22:56:12 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <201010211502.o9LF2WYf086752@lava.sentex.ca> In-Reply-To: <201010211502.o9LF2WYf086752@lava.sentex.ca> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201010212256.12800.hselasky@c2i.net> Cc: Weongyo Jeong Subject: Re: USB_ERR_TIMEOUT and USB_ERR_STALLED X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 20:55:02 -0000 On Thursday 21 October 2010 17:02:30 Mike Tancsa wrote: > I am trying to use RELENG_8 to monitor a number of APC upses and it > seems when there are more than one, I start to see a lot of USB > errors with the devices "coming and going" > > In the logs, I see a lot of > > > # grep USB /var/log/all.log | tail > Oct 21 10:24:05 upsmon1 root: Unknown USB device: vendor 0x051d > product 0x0002 bus uhub4 > Oct 21 10:25:47 upsmon1 root: Unknown USB device: vendor 0x051d > product 0x0002 bus uhub4 > Oct 21 10:27:45 upsmon1 root: Unknown USB device: vendor 0x051d > product 0x0002 bus uhub4 > Oct 21 10:29:44 upsmon1 root: Unknown USB device: vendor 0x051d > product 0x0002 bus uhub4 > Oct 21 10:30:35 upsmon1 root: Unknown USB device: vendor 0x051d > product 0x0002 bus uhub5 > Oct 21 10:32:35 upsmon1 root: Unknown USB device: vendor 0x051d > product 0x0002 bus uhub4 > Oct 21 10:37:04 upsmon1 root: Unknown USB device: vendor 0x051d > product 0x0002 bus uhub4 > Oct 21 10:38:38 upsmon1 root: Unknown USB device: vendor 0x051d > product 0x0002 bus uhub4 > Oct 21 10:44:14 upsmon1 root: Unknown USB device: vendor 0x051d > product 0x0002 bus uhub5 > Oct 21 10:45:09 upsmon1 root: Unknown USB device: vendor 0x051d > product 0x0002 bus uhub5 > > > > # usbconfig > ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON > ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON > ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON > ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=ON > ugen3.2: at usbus3, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=SAVE > ugen0.2: Conversion> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > ugen3.3: Conversion> at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > ugen3.4: Conversion> at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > ugen3.5: Conversion> at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > ugen3.6: Conversion> at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > ugen3.7: Conversion> at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > ugen3.8: at usbus3, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=SAVE > ugen3.9: Conversion> at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > ugen3.10: Conversion> at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > ugen3.11: Conversion> at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > > > This is with a kernel from Oct 4th, i386. Any idea what might be up > or how to debug this ?? Setting > hw.usb.debug to anything > 0 causes the system to almost hang under > the load unfortunately. > > ---Mike Weongyo is working on a usbdump utility to monitor ongoing USB traffic. --HPS From owner-freebsd-usb@FreeBSD.ORG Sat Oct 23 00:08:01 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 151271065672 for ; Sat, 23 Oct 2010 00:08:01 +0000 (UTC) (envelope-from mgmartin@comcast.net) Received: from mx.appliedtechnicalknowledge.com (appliedtechnicalknowledge.com [173.14.31.49]) by mx1.freebsd.org (Postfix) with ESMTP id D2E708FC12 for ; Sat, 23 Oct 2010 00:08:00 +0000 (UTC) Received: from [10.0.0.92] (gandalf.martins.home [10.0.0.92]) by mx.appliedtechnicalknowledge.com (Postfix) with ESMTPSA id 12732108BE0 for ; Fri, 22 Oct 2010 18:08:00 -0600 (MDT) Message-ID: <4CC2275F.1010201@comcast.net> Date: Fri, 22 Oct 2010 18:07:59 -0600 From: Michael Martin User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20101012 Thunderbird/3.1.4 MIME-Version: 1.0 To: freebsd-usb@freebsd.org References: <4CBFEBF5.30203@comcast.net> In-Reply-To: <4CBFEBF5.30203@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: USB 3.0 Fails To Attach Western Digital My Book 3.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Oct 2010 00:08:01 -0000 On 10/21/2010 01:29, Michael Martin wrote: > Thanks for the new USB 3.0 effort! > > I'm testing it out on 9.0-CURRENT amd64. The controller seems to find > a 2.0 usb stick fine. However, when I plug in a Western Digital 3.0 > drive, the device fails to attach. The WD drive attaches fine when > plugging into a 2.0 port on the motherboard. > > Controller info: > > xhci0@pci0:5:0:0: class=0x0c0330 card=0xffffffff chip=0x01941033 > rev=0x03 hdr=0x00 > vendor = 'NEC Electronics Hong Kong' > class = serial bus > subclass = USB > bar [10] = type Memory, range 64, base 0xfbbfe000, size 8192, > enabled > cap 01[50] = powerspec 3 supports D0 D3 current D0 > cap 05[70] = MSI supports 8 messages, 64 bit > cap 11[90] = MSI-X supports 8 messages in map 0x10 > cap 10[a0] = PCI-Express 2 endpoint max data 128(128) link x1(x1) > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0003[140] = Serial 1 ffffffffffffffff > ecap 0018[150] = unknown 1 > > WD 3.0 Drive Info ( while plugged into the 2.0 port ): > > ugen3.4: at usbus3, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0210 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x1058 > idProduct = 0x1123 > bcdDevice = 0x1010 > iManufacturer = 0x0001 > iProduct = 0x0002 > iSerialNumber = 0x0003 > bNumConfigurations = 0x0001 > > Output when plugging in the Western Digital 3.0 into the 3.0 port: > > Oct 21 01:03:54 gandalf root: Unknown USB device: vendor 0x1058 > product 0x1123 bus uhub4 > Oct 21 01:03:54 gandalf kernel: ugen4.2: at usbus4 > Oct 21 01:03:54 gandalf kernel: umass0: class 0/0, rev 3.00/10.10, addr 1> on usbus4 > Oct 21 01:03:54 gandalf kernel: umass0: SCSI over Bulk-Only; quirks = > 0x0000 > Oct 21 01:03:55 gandalf kernel: umass0:9:0:-1: Attached to scbus9 > Oct 21 01:03:57 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 > error=28 > Oct 21 01:03:57 gandalf last message repeated 2 times > Oct 21 01:03:57 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= > offset= size= error= > Oct 21 01:04:03 gandalf kernel: ugen4.2: at usbus4 > (disconnected) > Oct 21 01:04:03 gandalf kernel: umass0: at uhub4, port 2, addr 1 > (disconnected) > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): lost device > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): got CAM status > 0xa > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): fatal error, > failed to attach to device > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0: > Oct 21 01:04:03 gandalf kernel: 0:0): removing device entry > Oct 21 01:04:14 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 > error=28 > Oct 21 01:04:14 gandalf last message repeated 2 times > Oct 21 01:04:14 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= > offset= size= error= > > Output when plugging in the WD 3.0 into the 2.0 port: > > Oct 21 01:15:20 gandalf root: Unknown USB device: vendor 0x1058 > product 0x1123 bus uhub3 > Oct 21 01:15:20 gandalf kernel: ugen3.4: at usbus3 > Oct 21 01:15:20 gandalf kernel: umass0: class 0/0, rev 2.10/10.10, addr 4> on usbus3 > Oct 21 01:15:20 gandalf kernel: umass0: SCSI over Bulk-Only; quirks = > 0x0000 > Oct 21 01:15:21 gandalf kernel: umass0:9:0:-1: Attached to scbus9 > Oct 21 01:15:28 gandalf kernel: da0 at umass-sim0 bus 0 scbus9 target > 0 lun 0 > Oct 21 01:15:28 gandalf kernel: da0: Fixed > Direct Access SCSI-4 device > Oct 21 01:15:28 gandalf kernel: da0: 40.000MB/s transfers > Oct 21 01:15:28 gandalf kernel: da0: 953867MB (1953519616 512 byte > sectors: 255H 63S/T 121600C) > > Output when plugging in 2.0 device into the 3.0 port: > > Oct 21 01:09:54 gandalf root: Unknown USB device: vendor 0x090c > product 0x1000 bus uhub4 > Oct 21 01:09:54 gandalf kernel: ugen4.2: at usbus4 > Oct 21 01:09:54 gandalf kernel: umass1: rev 2.00/11.00, addr 1> on usbus4 > Oct 21 01:09:54 gandalf kernel: umass1: SCSI over Bulk-Only; quirks = > 0x0000 > Oct 21 01:09:55 gandalf kernel: umass1:10:1:-1: Attached to scbus10 > Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): TEST UNIT > READY. CDB: 0 0 0 0 0 0 > Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): CAM status: > SCSI Status Error > Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): SCSI > status: Check Condition > Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): SCSI sense: > UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have > changed) > Oct 21 01:09:56 gandalf kernel: da1 at umass-sim1 bus 1 scbus10 target > 0 lun 0 > Oct 21 01:09:56 gandalf kernel: da1: Fixed > Direct Access SCSI-0 device > Oct 21 01:09:56 gandalf kernel: da1: 40.000MB/s transfers > Oct 21 01:09:56 gandalf kernel: da1: 956MB (1957888 512 byte sectors: > 64H 32S/T 956C) > > --Michael ( I never got the last list email to this thread, so replying to my own.) Hans, I added your suggestions and here's what I've found: There seems to be two issues. (1) The first is initial recognition of the device. If I have umass compiled in the kernel or as a module loaded by loader.conf, initial load of xhci almost never finds the attached drive as the modules are loaded. If I kldunload xhci then load it back in, umass finds the drive. Re-loading or delaying the the load of xhci ( manual kldload or in rc.local ) almost always finds the drive. Seems like order matters here too. umass likes to be loaded first followed by xhci which then triggers umass to see the drive. If both umass and xhci are compiled in the kernel, the drive is never initialized. The good news is I can get the drive to be recognized by a kldunload/kldload of xhci. (2) One the drive is recognized I can see it and partition it using gpart. However, when I start dumping data to the drive, the drive gets disconnected. I was doing a dd if=/dev/zero of=/dev/da0 bs=1M count=500. The initial dd would sometimes succeed. Running dd imediately after the initial success would cause an error. Here's the tail output of umass debugging while the dd was running and the device stopped: Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer index = 4 Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=512 Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=0 Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer index = 8 Oct 22 17:44:19 gandalf kernel: umass0:umass_bbb_dump_csw: CSW 4049: sig = 0x53425355 (valid), tag = 0x00000fd1, res = 0, status = 0x00 (good) Oct 22 17:44:19 gandalf kernel: umass0:umass_cam_action: 7:0:0:XPT_SCSI_IO: cmd: 0x28, flags: 0x40, 10b cmd/512b data/32b sense Oct 22 17:44:19 gandalf kernel: umass0:umass_bbb_dump_cbw: CBW 4050: cmd = 10b (0x280000000000...), data = 512b, lun = 0, dir = in Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer index = 4 Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=512 Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=0 Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer index = 8 Oct 22 17:44:19 gandalf kernel: umass0:umass_bbb_dump_csw: CSW 4050: sig = 0x53425355 (valid), tag = 0x00000fd2, res = 0, status = 0x00 (good) Oct 22 17:44:19 gandalf kernel: umass0:umass_cam_action: 7:0:0:XPT_SCSI_IO: cmd: 0x35, flags: 0xc0, 10b cmd/0b data/32b sense Oct 22 17:44:23 gandalf kernel: umass0:umass_cam_action: 7:0:0:XPT_SCSI_IO: cmd: 0x25, flags: 0x40, 10b cmd/8b data/32b sense Oct 22 17:44:23 gandalf kernel: umass0:umass_bbb_dump_cbw: CBW 4051: cmd = 10b (0x250000000000...), data = 8b, lun = 0, dir = in Oct 22 17:44:23 gandalf kernel: ugen4.2: at usbus4 (disconnected) Oct 22 17:44:23 gandalf kernel: umass0: at uhub4, port 2, addr 1 (disconnected) Oct 22 17:44:23 gandalf kernel: umass0:umass_detach: Oct 22 17:44:23 gandalf kernel: (da0:umass-sim0:0:0:0): AutoSense failed Oct 22 17:44:23 gandalf kernel: (da0:umass-sim0:0:0:0): lost device Oct 22 17:44:23 gandalf kernel: (da0:umass-sim0:0:0:0): removing device entry I've saw there are quirks for the WESTERN MYBOOK . A added a specific device into usbdevs and an entry into usb_quirk.c to mimic the same quirks: USB_QUIRK(WESTERN, MYBOOK3, 0x0000, 0xffff, UQ_MSC_FORCE_WIRE_BBB, UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_INQUIRY_EVPD, UQ_MSC_NO_SYNC_CACHE), This didn't help, and I got the disconnect as shown above. --Michael From owner-freebsd-usb@FreeBSD.ORG Sat Oct 23 06:22:27 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AE8D1065672 for ; Sat, 23 Oct 2010 06:22:27 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id F180D8FC08 for ; Sat, 23 Oct 2010 06:22:26 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=yevn+QCjI6xy199BDvBOOiO14qYvyLq62he9tTtU3M8= c=1 sm=1 a=teY7EFdY6K0A:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=3AF_jjmrgWurMXyvWl0A:9 a=pdnFhMQuCWgvfkgPqhcA:7 a=quQ7vxgo3ktsR0reuIRJGSUhwd0A:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 38854183; Sat, 23 Oct 2010 08:22:24 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Sat, 23 Oct 2010 08:23:36 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <4CBFEBF5.30203@comcast.net> <4CC2275F.1010201@comcast.net> In-Reply-To: <4CC2275F.1010201@comcast.net> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201010230823.36449.hselasky@c2i.net> Cc: Subject: Re: USB 3.0 Fails To Attach Western Digital My Book 3.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Oct 2010 06:22:27 -0000 On Saturday 23 October 2010 02:07:59 Michael Martin wrote: > On 10/21/2010 01:29, Michael Martin wrote: > > Thanks for the new USB 3.0 effort! > > > > I'm testing it out on 9.0-CURRENT amd64. The controller seems to find > > a 2.0 usb stick fine. However, when I plug in a Western Digital 3.0 > > drive, the device fails to attach. The WD drive attaches fine when > > plugging into a 2.0 port on the motherboard. > > > > Controller info: > > > > xhci0@pci0:5:0:0: class=0x0c0330 card=0xffffffff chip=0x01941033 > > rev=0x03 hdr=0x00 > > > > vendor = 'NEC Electronics Hong Kong' > > class = serial bus > > subclass = USB > > bar [10] = type Memory, range 64, base 0xfbbfe000, size 8192, > > > > enabled > > > > cap 01[50] = powerspec 3 supports D0 D3 current D0 > > cap 05[70] = MSI supports 8 messages, 64 bit > > cap 11[90] = MSI-X supports 8 messages in map 0x10 > > cap 10[a0] = PCI-Express 2 endpoint max data 128(128) link x1(x1) > > > > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > > ecap 0003[140] = Serial 1 ffffffffffffffff > > ecap 0018[150] = unknown 1 > > > > WD 3.0 Drive Info ( while plugged into the 2.0 port ): > > > > ugen3.4: at usbus3, cfg=0 md=HOST > > spd=HIGH (480Mbps) pwr=ON > > > > bLength = 0x0012 > > bDescriptorType = 0x0001 > > bcdUSB = 0x0210 > > bDeviceClass = 0x0000 > > bDeviceSubClass = 0x0000 > > bDeviceProtocol = 0x0000 > > bMaxPacketSize0 = 0x0040 > > idVendor = 0x1058 > > idProduct = 0x1123 > > bcdDevice = 0x1010 > > iManufacturer = 0x0001 > > iProduct = 0x0002 > > iSerialNumber = 0x0003 > > bNumConfigurations = 0x0001 > > > > Output when plugging in the Western Digital 3.0 into the 3.0 port: > > > > Oct 21 01:03:54 gandalf root: Unknown USB device: vendor 0x1058 > > product 0x1123 bus uhub4 > > Oct 21 01:03:54 gandalf kernel: ugen4.2: at usbus4 > > Oct 21 01:03:54 gandalf kernel: umass0: > class 0/0, rev 3.00/10.10, addr 1> on usbus4 > > Oct 21 01:03:54 gandalf kernel: umass0: SCSI over Bulk-Only; quirks = > > 0x0000 > > Oct 21 01:03:55 gandalf kernel: umass0:9:0:-1: Attached to scbus9 > > Oct 21 01:03:57 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 > > error=28 > > Oct 21 01:03:57 gandalf last message repeated 2 times > > Oct 21 01:03:57 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= > > offset= size= error= > > Oct 21 01:04:03 gandalf kernel: ugen4.2: at usbus4 > > (disconnected) > > Oct 21 01:04:03 gandalf kernel: umass0: at uhub4, port 2, addr 1 > > (disconnected) > > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): lost device > > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): got CAM status > > 0xa > > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): fatal error, > > failed to attach to device > > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0: > > Oct 21 01:04:03 gandalf kernel: 0:0): removing device entry > > Oct 21 01:04:14 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 > > error=28 > > Oct 21 01:04:14 gandalf last message repeated 2 times > > Oct 21 01:04:14 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= > > offset= size= error= > > > > Output when plugging in the WD 3.0 into the 2.0 port: > > > > Oct 21 01:15:20 gandalf root: Unknown USB device: vendor 0x1058 > > product 0x1123 bus uhub3 > > Oct 21 01:15:20 gandalf kernel: ugen3.4: at usbus3 > > Oct 21 01:15:20 gandalf kernel: umass0: > class 0/0, rev 2.10/10.10, addr 4> on usbus3 > > Oct 21 01:15:20 gandalf kernel: umass0: SCSI over Bulk-Only; quirks = > > 0x0000 > > Oct 21 01:15:21 gandalf kernel: umass0:9:0:-1: Attached to scbus9 > > Oct 21 01:15:28 gandalf kernel: da0 at umass-sim0 bus 0 scbus9 target > > 0 lun 0 > > Oct 21 01:15:28 gandalf kernel: da0: Fixed > > Direct Access SCSI-4 device > > Oct 21 01:15:28 gandalf kernel: da0: 40.000MB/s transfers > > Oct 21 01:15:28 gandalf kernel: da0: 953867MB (1953519616 512 byte > > sectors: 255H 63S/T 121600C) > > > > Output when plugging in 2.0 device into the 3.0 port: > > > > Oct 21 01:09:54 gandalf root: Unknown USB device: vendor 0x090c > > product 0x1000 bus uhub4 > > Oct 21 01:09:54 gandalf kernel: ugen4.2: at usbus4 > > Oct 21 01:09:54 gandalf kernel: umass1: > rev 2.00/11.00, addr 1> on usbus4 > > Oct 21 01:09:54 gandalf kernel: umass1: SCSI over Bulk-Only; quirks = > > 0x0000 > > Oct 21 01:09:55 gandalf kernel: umass1:10:1:-1: Attached to scbus10 > > Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): TEST UNIT > > READY. CDB: 0 0 0 0 0 0 > > Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): CAM status: > > SCSI Status Error > > Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): SCSI > > status: Check Condition > > Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): SCSI sense: > > UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have > > changed) > > Oct 21 01:09:56 gandalf kernel: da1 at umass-sim1 bus 1 scbus10 target > > 0 lun 0 > > Oct 21 01:09:56 gandalf kernel: da1: Fixed > > Direct Access SCSI-0 device > > Oct 21 01:09:56 gandalf kernel: da1: 40.000MB/s transfers > > Oct 21 01:09:56 gandalf kernel: da1: 956MB (1957888 512 byte sectors: > > 64H 32S/T 956C) > > > > --Michael > > ( I never got the last list email to this thread, so replying to my own.) > > Hans, I added your suggestions and here's what I've found: > > There seems to be two issues. > > (1) > The first is initial recognition of the device. If I have umass > compiled in the kernel or as a module loaded by loader.conf, initial > load of xhci almost never finds the attached drive as the modules are > loaded. If I kldunload xhci then load it back in, umass finds the > drive. Re-loading or delaying the the load of xhci ( manual kldload or > in rc.local ) almost always finds the drive. Seems like order matters > here too. umass likes to be loaded first followed by xhci which then > triggers umass to see the drive. > > If both umass and xhci are compiled in the kernel, the drive is never > initialized. > > The good news is I can get the drive to be recognized by a > kldunload/kldload of xhci. > > (2) > One the drive is recognized I can see it and partition it using gpart. > However, when I start dumping data to the drive, the drive gets > disconnected. I was doing a dd if=/dev/zero of=/dev/da0 bs=1M > count=500. The initial dd would sometimes succeed. Running dd > imediately after the initial success would cause an error. > > Here's the tail output of umass debugging while the dd was running and > the device stopped: > > Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer > index = 4 > Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: > max_bulk=131072, data_rem=512 > Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: > max_bulk=131072, data_rem=0 > Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer > index = 8 > Oct 22 17:44:19 gandalf kernel: umass0:umass_bbb_dump_csw: CSW 4049: sig > = 0x53425355 (valid), tag = 0x00000fd1, res = 0, status = 0x00 (good) > Oct 22 17:44:19 gandalf kernel: umass0:umass_cam_action: > 7:0:0:XPT_SCSI_IO: cmd: 0x28, flags: 0x40, 10b cmd/512b data/32b sense > Oct 22 17:44:19 gandalf kernel: umass0:umass_bbb_dump_cbw: CBW 4050: cmd > = 10b (0x280000000000...), data = 512b, lun = 0, dir = in > Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer > index = 4 > Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: > max_bulk=131072, data_rem=512 > Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: > max_bulk=131072, data_rem=0 > Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer > index = 8 > Oct 22 17:44:19 gandalf kernel: umass0:umass_bbb_dump_csw: CSW 4050: sig > = 0x53425355 (valid), tag = 0x00000fd2, res = 0, status = 0x00 (good) > Oct 22 17:44:19 gandalf kernel: umass0:umass_cam_action: > 7:0:0:XPT_SCSI_IO: cmd: 0x35, flags: 0xc0, 10b cmd/0b data/32b sense > Oct 22 17:44:23 gandalf kernel: umass0:umass_cam_action: > 7:0:0:XPT_SCSI_IO: cmd: 0x25, flags: 0x40, 10b cmd/8b data/32b sense > Oct 22 17:44:23 gandalf kernel: umass0:umass_bbb_dump_cbw: CBW 4051: cmd > = 10b (0x250000000000...), data = 8b, lun = 0, dir = in > Oct 22 17:44:23 gandalf kernel: ugen4.2: at usbus4 > (disconnected) > Oct 22 17:44:23 gandalf kernel: umass0: at uhub4, port 2, addr 1 > (disconnected) > Oct 22 17:44:23 gandalf kernel: umass0:umass_detach: > Oct 22 17:44:23 gandalf kernel: (da0:umass-sim0:0:0:0): AutoSense failed > Oct 22 17:44:23 gandalf kernel: (da0:umass-sim0:0:0:0): lost device > Oct 22 17:44:23 gandalf kernel: (da0:umass-sim0:0:0:0): removing device > entry > > I've saw there are quirks for the WESTERN MYBOOK . A added a specific > device into usbdevs and an entry into usb_quirk.c to mimic the same quirks: > > USB_QUIRK(WESTERN, MYBOOK3, 0x0000, 0xffff, UQ_MSC_FORCE_WIRE_BBB, > UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_INQUIRY_EVPD, > UQ_MSC_NO_SYNC_CACHE), > > This didn't help, and I got the disconnect as shown above. > > --Michael Hi, Could you compile kernel with "options USB_DEBUG". Then run: sysctl hw.usb.uhub.debug=16 Then attach your drive. Maybe the USB stack is mistreating some event from the XHCI. Send the resulting dmesg. --HPS From owner-freebsd-usb@FreeBSD.ORG Sat Oct 23 08:52:25 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA510106566B; Sat, 23 Oct 2010 08:52:25 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id A39BD8FC08; Sat, 23 Oct 2010 08:52:25 +0000 (UTC) Received: from [109.84.147.79] (helo=tiny.Sisis.de.) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1P9Zpu-0000YH-Q7; Sat, 23 Oct 2010 10:52:23 +0200 Received: from tiny.Sisis.de. (localhost [127.0.0.1]) by tiny.Sisis.de. (8.14.3/8.14.3) with ESMTP id o9N8rhYd001446; Sat, 23 Oct 2010 10:53:44 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by tiny.Sisis.de. (8.14.3/8.14.3/Submit) id o9N8rh4I001445; Sat, 23 Oct 2010 10:53:43 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: tiny.Sisis.de.: guru set sender to guru@unixarea.de using -f Resent-From: guru@tiny.Sisis.de Resent-Date: Sat, 23 Oct 2010 10:53:42 +0200 Resent-Message-ID: <20101023085342.GA1439@tiny.Sisis.de> Resent-To: freebsd-hackers@freebsd.org, freebsd-usb@freebsd.org Date: Sat, 23 Oct 2010 10:49:56 +0200 From: Matthias Apitz To: freebsd-hackers@freebsd.org Message-ID: <20101023084956.GA1362@tiny.Sisis.de> References: <20100905081917.GA2212@current.Sisis.de> <20100909063514.GA2333@current.Sisis.de> <20100910061629.GA2461@current.Sisis.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100910061629.GA2461@current.Sisis.de> X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 109.84.147.79 Cc: freebsd-usb@freebsd.org Subject: USB key && can't mount /root during boot X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Oct 2010 08:52:26 -0000 Hello, I have now again the same problem (see Subject) again with a new laptop Acer Aspire One D250 and neither of the two values in loader.conf: kern.cam.boot_delay="10000" kern.cam.scsi_delay="10000" seems to help. The 10 sec delay is not even visible during the boot, the message to enter manually the root device just pops up without any delay. What does this mean? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ From owner-freebsd-usb@FreeBSD.ORG Sat Oct 23 14:33:23 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18DEF106564A for ; Sat, 23 Oct 2010 14:33:23 +0000 (UTC) (envelope-from mgmartin@comcast.net) Received: from mx.appliedtechnicalknowledge.com (portfolioframework.com [173.14.31.49]) by mx1.freebsd.org (Postfix) with ESMTP id E75A28FC0A for ; Sat, 23 Oct 2010 14:33:22 +0000 (UTC) Received: from [10.0.0.92] (gandalf.martins.home [10.0.0.92]) by mx.appliedtechnicalknowledge.com (Postfix) with ESMTPSA id 2674710A428 for ; Sat, 23 Oct 2010 08:33:22 -0600 (MDT) Message-ID: <4CC2F231.7020507@comcast.net> Date: Sat, 23 Oct 2010 08:33:21 -0600 From: Michael Martin User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20101012 Thunderbird/3.1.4 MIME-Version: 1.0 To: freebsd-usb@freebsd.org References: <4CBFEBF5.30203@comcast.net> <4CC2275F.1010201@comcast.net> <201010230823.36449.hselasky@c2i.net> In-Reply-To: <201010230823.36449.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: USB 3.0 Fails To Attach Western Digital My Book 3.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Oct 2010 14:33:23 -0000 On 10/23/2010 00:23, Hans Petter Selasky wrote: > On Saturday 23 October 2010 02:07:59 Michael Martin wrote: >> On 10/21/2010 01:29, Michael Martin wrote: >>> Thanks for the new USB 3.0 effort! >>> >>> I'm testing it out on 9.0-CURRENT amd64. The controller seems to find >>> a 2.0 usb stick fine. However, when I plug in a Western Digital 3.0 >>> drive, the device fails to attach. The WD drive attaches fine when >>> plugging into a 2.0 port on the motherboard. >>> >>> Controller info: >>> >>> xhci0@pci0:5:0:0: class=0x0c0330 card=0xffffffff chip=0x01941033 >>> rev=0x03 hdr=0x00 >>> >>> vendor = 'NEC Electronics Hong Kong' >>> class = serial bus >>> subclass = USB >>> bar [10] = type Memory, range 64, base 0xfbbfe000, size 8192, >>> >>> enabled >>> >>> cap 01[50] = powerspec 3 supports D0 D3 current D0 >>> cap 05[70] = MSI supports 8 messages, 64 bit >>> cap 11[90] = MSI-X supports 8 messages in map 0x10 >>> cap 10[a0] = PCI-Express 2 endpoint max data 128(128) link x1(x1) >>> >>> ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected >>> ecap 0003[140] = Serial 1 ffffffffffffffff >>> ecap 0018[150] = unknown 1 >>> >>> WD 3.0 Drive Info ( while plugged into the 2.0 port ): >>> >>> ugen3.4: at usbus3, cfg=0 md=HOST >>> spd=HIGH (480Mbps) pwr=ON >>> >>> bLength = 0x0012 >>> bDescriptorType = 0x0001 >>> bcdUSB = 0x0210 >>> bDeviceClass = 0x0000 >>> bDeviceSubClass = 0x0000 >>> bDeviceProtocol = 0x0000 >>> bMaxPacketSize0 = 0x0040 >>> idVendor = 0x1058 >>> idProduct = 0x1123 >>> bcdDevice = 0x1010 >>> iManufacturer = 0x0001 >>> iProduct = 0x0002 >>> iSerialNumber = 0x0003 >>> bNumConfigurations = 0x0001 >>> >>> Output when plugging in the Western Digital 3.0 into the 3.0 port: >>> >>> Oct 21 01:03:54 gandalf root: Unknown USB device: vendor 0x1058 >>> product 0x1123 bus uhub4 >>> Oct 21 01:03:54 gandalf kernel: ugen4.2: at usbus4 >>> Oct 21 01:03:54 gandalf kernel: umass0:>> class 0/0, rev 3.00/10.10, addr 1> on usbus4 >>> Oct 21 01:03:54 gandalf kernel: umass0: SCSI over Bulk-Only; quirks = >>> 0x0000 >>> Oct 21 01:03:55 gandalf kernel: umass0:9:0:-1: Attached to scbus9 >>> Oct 21 01:03:57 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 >>> error=28 >>> Oct 21 01:03:57 gandalf last message repeated 2 times >>> Oct 21 01:03:57 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= >>> offset= size= error= >>> Oct 21 01:04:03 gandalf kernel: ugen4.2: at usbus4 >>> (disconnected) >>> Oct 21 01:04:03 gandalf kernel: umass0: at uhub4, port 2, addr 1 >>> (disconnected) >>> Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): lost device >>> Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): got CAM status >>> 0xa >>> Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): fatal error, >>> failed to attach to device >>> Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0: >>> Oct 21 01:04:03 gandalf kernel: 0:0): removing device entry >>> Oct 21 01:04:14 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 >>> error=28 >>> Oct 21 01:04:14 gandalf last message repeated 2 times >>> Oct 21 01:04:14 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= >>> offset= size= error= >>> >>> Output when plugging in the WD 3.0 into the 2.0 port: >>> >>> Oct 21 01:15:20 gandalf root: Unknown USB device: vendor 0x1058 >>> product 0x1123 bus uhub3 >>> Oct 21 01:15:20 gandalf kernel: ugen3.4: at usbus3 >>> Oct 21 01:15:20 gandalf kernel: umass0:>> class 0/0, rev 2.10/10.10, addr 4> on usbus3 >>> Oct 21 01:15:20 gandalf kernel: umass0: SCSI over Bulk-Only; quirks = >>> 0x0000 >>> Oct 21 01:15:21 gandalf kernel: umass0:9:0:-1: Attached to scbus9 >>> Oct 21 01:15:28 gandalf kernel: da0 at umass-sim0 bus 0 scbus9 target >>> 0 lun 0 >>> Oct 21 01:15:28 gandalf kernel: da0: Fixed >>> Direct Access SCSI-4 device >>> Oct 21 01:15:28 gandalf kernel: da0: 40.000MB/s transfers >>> Oct 21 01:15:28 gandalf kernel: da0: 953867MB (1953519616 512 byte >>> sectors: 255H 63S/T 121600C) >>> >>> Output when plugging in 2.0 device into the 3.0 port: >>> >>> Oct 21 01:09:54 gandalf root: Unknown USB device: vendor 0x090c >>> product 0x1000 bus uhub4 >>> Oct 21 01:09:54 gandalf kernel: ugen4.2: at usbus4 >>> Oct 21 01:09:54 gandalf kernel: umass1:>> rev 2.00/11.00, addr 1> on usbus4 >>> Oct 21 01:09:54 gandalf kernel: umass1: SCSI over Bulk-Only; quirks = >>> 0x0000 >>> Oct 21 01:09:55 gandalf kernel: umass1:10:1:-1: Attached to scbus10 >>> Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): TEST UNIT >>> READY. CDB: 0 0 0 0 0 0 >>> Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): CAM status: >>> SCSI Status Error >>> Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): SCSI >>> status: Check Condition >>> Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): SCSI sense: >>> UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have >>> changed) >>> Oct 21 01:09:56 gandalf kernel: da1 at umass-sim1 bus 1 scbus10 target >>> 0 lun 0 >>> Oct 21 01:09:56 gandalf kernel: da1: Fixed >>> Direct Access SCSI-0 device >>> Oct 21 01:09:56 gandalf kernel: da1: 40.000MB/s transfers >>> Oct 21 01:09:56 gandalf kernel: da1: 956MB (1957888 512 byte sectors: >>> 64H 32S/T 956C) >>> >>> --Michael >> ( I never got the last list email to this thread, so replying to my own.) >> >> Hans, I added your suggestions and here's what I've found: >> >> There seems to be two issues. >> >> (1) >> The first is initial recognition of the device. If I have umass >> compiled in the kernel or as a module loaded by loader.conf, initial >> load of xhci almost never finds the attached drive as the modules are >> loaded. If I kldunload xhci then load it back in, umass finds the >> drive. Re-loading or delaying the the load of xhci ( manual kldload or >> in rc.local ) almost always finds the drive. Seems like order matters >> here too. umass likes to be loaded first followed by xhci which then >> triggers umass to see the drive. >> >> If both umass and xhci are compiled in the kernel, the drive is never >> initialized. >> >> The good news is I can get the drive to be recognized by a >> kldunload/kldload of xhci. >> >> (2) >> One the drive is recognized I can see it and partition it using gpart. >> However, when I start dumping data to the drive, the drive gets >> disconnected. I was doing a dd if=/dev/zero of=/dev/da0 bs=1M >> count=500. The initial dd would sometimes succeed. Running dd >> imediately after the initial success would cause an error. >> >> Here's the tail output of umass debugging while the dd was running and >> the device stopped: >> >> Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer >> index = 4 >> Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: >> max_bulk=131072, data_rem=512 >> Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: >> max_bulk=131072, data_rem=0 >> Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer >> index = 8 >> Oct 22 17:44:19 gandalf kernel: umass0:umass_bbb_dump_csw: CSW 4049: sig >> = 0x53425355 (valid), tag = 0x00000fd1, res = 0, status = 0x00 (good) >> Oct 22 17:44:19 gandalf kernel: umass0:umass_cam_action: >> 7:0:0:XPT_SCSI_IO: cmd: 0x28, flags: 0x40, 10b cmd/512b data/32b sense >> Oct 22 17:44:19 gandalf kernel: umass0:umass_bbb_dump_cbw: CBW 4050: cmd >> = 10b (0x280000000000...), data = 512b, lun = 0, dir = in >> Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer >> index = 4 >> Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: >> max_bulk=131072, data_rem=512 >> Oct 22 17:44:19 gandalf kernel: umass0:umass_t_bbb_data_read_callback: >> max_bulk=131072, data_rem=0 >> Oct 22 17:44:19 gandalf kernel: umass0:umass_transfer_start: transfer >> index = 8 >> Oct 22 17:44:19 gandalf kernel: umass0:umass_bbb_dump_csw: CSW 4050: sig >> = 0x53425355 (valid), tag = 0x00000fd2, res = 0, status = 0x00 (good) >> Oct 22 17:44:19 gandalf kernel: umass0:umass_cam_action: >> 7:0:0:XPT_SCSI_IO: cmd: 0x35, flags: 0xc0, 10b cmd/0b data/32b sense >> Oct 22 17:44:23 gandalf kernel: umass0:umass_cam_action: >> 7:0:0:XPT_SCSI_IO: cmd: 0x25, flags: 0x40, 10b cmd/8b data/32b sense >> Oct 22 17:44:23 gandalf kernel: umass0:umass_bbb_dump_cbw: CBW 4051: cmd >> = 10b (0x250000000000...), data = 8b, lun = 0, dir = in >> Oct 22 17:44:23 gandalf kernel: ugen4.2: at usbus4 >> (disconnected) >> Oct 22 17:44:23 gandalf kernel: umass0: at uhub4, port 2, addr 1 >> (disconnected) >> Oct 22 17:44:23 gandalf kernel: umass0:umass_detach: >> Oct 22 17:44:23 gandalf kernel: (da0:umass-sim0:0:0:0): AutoSense failed >> Oct 22 17:44:23 gandalf kernel: (da0:umass-sim0:0:0:0): lost device >> Oct 22 17:44:23 gandalf kernel: (da0:umass-sim0:0:0:0): removing device >> entry >> >> I've saw there are quirks for the WESTERN MYBOOK . A added a specific >> device into usbdevs and an entry into usb_quirk.c to mimic the same quirks: >> >> USB_QUIRK(WESTERN, MYBOOK3, 0x0000, 0xffff, UQ_MSC_FORCE_WIRE_BBB, >> UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_INQUIRY_EVPD, >> UQ_MSC_NO_SYNC_CACHE), >> >> This didn't help, and I got the disconnect as shown above. >> >> --Michael > Hi, > > Could you compile kernel with "options USB_DEBUG". > > Then run: > > sysctl hw.usb.uhub.debug=16 > > Then attach your drive. > > Maybe the USB stack is mistreating some event from the XHCI. Send the > resulting dmesg. > > --HPS I set debug and plugged in the drive. Here's the output. --Michael From owner-freebsd-usb@FreeBSD.ORG Sat Oct 23 22:26:29 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3ED45106566C for ; Sat, 23 Oct 2010 22:26:29 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id C48FF8FC08 for ; Sat, 23 Oct 2010 22:26:28 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=5OBHFxb9I47YZ7HELXzI6cL6pwPTRnd5uxbD1DPQ4WY= c=1 sm=1 a=teY7EFdY6K0A:10 a=Q9fys5e9bTEA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=SUX610Jcqg_oVEOPwU4A:9 a=k7NkdFDkVFvzdvg4j_hZSkSbCkEA:4 a=PUjeQqilurYA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe05.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 38939578; Sun, 24 Oct 2010 00:26:26 +0200 From: Hans Petter Selasky To: Michael Martin Date: Sun, 24 Oct 2010 00:27:38 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <4CBFEBF5.30203@comcast.net> <201010230823.36449.hselasky@c2i.net> <4CC2E533.3010604@comcast.net> In-Reply-To: <4CC2E533.3010604@comcast.net> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Message-Id: <201010240027.38385.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: USB 3.0 Fails To Attach Western Digital My Book 3.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Oct 2010 22:26:29 -0000 On Saturday 23 October 2010 15:37:55 Michael Martin wrote: > On 10/23/2010 00:23, Hans Petter Selasky wrote: > > On Saturday 23 October 2010 02:07:59 Michael Martin wrote: > >> On 10/21/2010 01:29, Michael Martin wrote: > >>> Thanks for the new USB 3.0 effort! > >>>=20 > >>> I'm testing it out on 9.0-CURRENT amd64. The controller seems to find > >>> a 2.0 usb stick fine. However, when I plug in a Western Digital 3.0 > >>> drive, the device fails to attach. The WD drive attaches fine when > >>> plugging into a 2.0 port on the motherboard. > >>>=20 > >>> Controller info: > >>>=20 Hi, =46rom the logs you sent me I see that the super-speed inactive state is=20 reached. There is currently no recovery from this state. I will send you a= =20 patch which you can try. =2D-HPS