Current problem reports assigned to freebsd-usb@FreeBSD.org
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/177013 usb[patch] Adding support for LOGITEC LAN-W300N/U2S on if o usb/176913 usbHigh interrupt load with ehci o usb/176841 usb[umass] Sony DSC-H2 USB connection fails o usb/176417 usb[xhci][cam][umass] kernelpanic while removing plugged o usb/175731 usbdetaching USB keyboard freezes other USB keyboards o usb/175639 usbnot detect usb netcard D-LINK DUB-E100 rev C1 o usb/175599 usb[usbdevs][patch]Liebert UPS PSI1000 being assigned uhi o usb/175551 usbSeagate 2TB USB extern hard disk have errors with Free o usb/175454 usbupdate usbdevs and usb_quirk.c for SanDisk SDDR-289 o usb/175379 usbusb card-reader problem o usb/175302 usbdon't mount virtual driver CD for my phone o usb/174963 usbbuffalo wli-uc-gn wireless card sometimes unusable and o usb/174835 usbuaudio fails to create pcm/dsp device file o usb/174814 usb[PATCH] support for MiFi 2200 o usb/174695 usbusb keeps disconnecting mouse or keyboard o usb/174575 usbInterrupt storm error on startup o usb/174464 usbclone MAC address(es) on usb networks cdce(4) ue[0- o usb/174254 usbMIDI keyboard not recognised o usb/173722 usb[xhci] xhci driver bug after suspend to RAM (ACPI S3 m o usb/173616 usbLG USB DVD-RW USB STALL o usb/173182 usbusbus appears as a network device o usb/172937 usbFreeBSD 9.1-RC2 usb3 port disconnects o usb/172633 usbSony Cybershot not recognized as USB mem stick o usb/172199 usb[xhci] high interrupts load xhci o usb/171354 usb[umass] Medium not present error on flash drive [regre o usb/171262 usbplug in sdhc via usb reader reboots machine o usb/171197 usbADATA Classic CH11 USB HDD doesn't work in FreeBSD 9.1 o usb/170699 usbFreeBSD 9.0 Doesn't list HDD or its partitions in part o usb/170688 usbpatch][usbdevs][wlan] Patch for ASUS Black Diamond USB o usb/170606 usbr239222 kernel panic at boot - usb locking issue o usb/170358 usb[ums] Wrong (duplicate) button numbers o usb/170123 usb[umass] HP v210w USB stick not supported o usb/169935 usb[keyboard] Unable use USB keyboard while panic o usb/169789 usb[u3g] [patch] add support for huawei e3131 o usb/169461 usb[ugen] USB2 high-speed device detected as full speed o usb/169428 usb[ugen] ugen not detecting all endpoints on device [reg o usb/168551 usb[umass] Issues with embedded card reader (Laptop ASUS o usb/168132 usb[umass] MATSHITA memory card size reported wrong, moun o usb/167847 usb[ural] dlink dwl-122g e crashes(?) when trying wap2 cr o usb/167001 usb[USB] [PATCH] add support for Smart G2 64MB memory key o usb/165815 usb[usbdevs] [patch] add k3772z 3g modem support o usb/165163 usb[keyboard] The USB RF keyboard and mouse become non-re o usb/164058 usb[umass] Lexar 8GB USB flash drive doesn't work by defa f usb/163328 usb[usb] Support for Atheros USB abgn devices o kern/163091 usb[panic] Fatal trap 12: page fault while in kernel mode f usb/162306 usbusb devices cant get address asignation, no memories, o usb/162054 usbusbdump just hangs on 9.0-RC1 f usb/161793 usbpoor EHCI usb2 i/o performance o usb/160436 usbucom wedges machine on parity error ? o usb/160299 usbMicroSDHC-to-USB adapters do not work in FreeBSD 8.x o usb/160192 usb[install] Installation from USB-Stick doesn't find the o usb/159274 usbUSB 3.0 Etron EJ168A does not work. f usb/159191 usb[fusefs-ntfs] write on fusefs-ntfs mounted partition r o usb/157376 usbLaCie USB disk not recognized o usb/157074 usb[boot] [usb8] vfs_mountroot_ask is called when no usb o usb/156898 usb[keyboard] usb keyboard does not work while boot (ps2 f usb/156735 usbNeed Quirk for Goflex USB Disk Drives o usb/156726 usb[snd_uaudio]: snd_uaudio(4) fails to detach when mixer o usb/156725 usbUSB stack stall cause complete system input loss o usb/156596 usb[ehci] Extremely high interrupt rate on ehci/uhci IRQ1 o usb/156000 usbrum(4) Fatal trap 18: integer divide fault while in ke f usb/155996 usbNanoBSD not booted as Disk o usb/155784 usbProblem with Transcend StoreJet 25M3 (2AJ1) on Asus M2 o usb/155663 usb[usbdevs]
Re: usb/177013: commit references a PR
The following reply was made to PR usb/177013; it has been noted by GNATS. From: dfil...@freebsd.org (dfilter service) To: bug-follo...@freebsd.org Cc: Subject: Re: usb/177013: commit references a PR Date: Mon, 18 Mar 2013 11:12:15 + (UTC) Author: hselasky Date: Mon Mar 18 07:02:58 2013 New Revision: 248458 URL: http://svnweb.freebsd.org/changeset/base/248458 Log: Add new USB ID. PR: usb/177013 MFC after: 1 week Modified: head/sys/dev/usb/usbdevs head/sys/dev/usb/wlan/if_run.c Modified: head/sys/dev/usb/usbdevs == --- head/sys/dev/usb/usbdevs Mon Mar 18 05:30:18 2013(r248457) +++ head/sys/dev/usb/usbdevs Mon Mar 18 07:02:58 2013(r248458) @@ -2499,6 +2499,7 @@ product LOGITEC RT2870_2 0x0163 RT2870 product LOGITEC RT2870_3 0x0164 RT2870 product LOGITEC LANW300NU20x0166 LAN-W300N/U2 product LOGITEC LANW150NU20x0168 LAN-W150N/U2 +product LOGITEC LANW300NU2S 0x0169 LAN-W300N/U2S /* Longcheer Holdings, Ltd. products */ product LONGCHEER WM660x6061 Longcheer WM66 HSDPA Modified: head/sys/dev/usb/wlan/if_run.c == --- head/sys/dev/usb/wlan/if_run.c Mon Mar 18 05:30:18 2013 (r248457) +++ head/sys/dev/usb/wlan/if_run.c Mon Mar 18 07:02:58 2013 (r248458) @@ -211,6 +211,7 @@ static const STRUCT_USB_HOST_ID run_devs RUN_DEV(LOGITEC, RT2870_3), RUN_DEV(LOGITEC, LANW300NU2), RUN_DEV(LOGITEC, LANW150NU2), +RUN_DEV(LOGITEC, LANW300NU2S), RUN_DEV(MELCO,RT2870_1), RUN_DEV(MELCO,RT2870_2), RUN_DEV(MELCO,WLIUCAG300N), ___ svn-src-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to svn-src-all-unsubscr...@freebsd.org ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Help please... More problems with USB 3.0 (kernel freezes)
Back on March 11, I wrote here about the problems I was having with a new Anker[tm] 2-port USB 3.0 PCIe card. After Hans Petter Selasky kindly responded, I believed that I had isolated the problem to just one specific pairing of a specific device and my specific card. Well, it seems now that I was utterly wrong. (I have only just now realized this because since the 11th, I have been working on other things and haven't even touched any of the USB 3.0 stuff... at least not in conjunction with FreeBSD.) Anyway, the problem is back now, and with a vengence. In fact now, it is causing kernel freezes. (This is exceptionally serious in my book.) The problem is what it was before... the Anker[tm] card, together with the 9.1-RELEASE xhci driver, is refusing to properly connect a USB mass storage type device that has been plugged into the card. I have now reproduced this problem multiple times, both with external (non-powered) USB 3.0 drive enclosures (2 x Patriot Gauntlet2) and also even with a USB 3.0 flash thumb drive I have here (ADATA S102 16GB). It appears that once the drive+card gets into a mode (mood?) where it no longer wants to properly recognize any newly inserted USB mass storage type device it will, after that point in time, refuse to properly recognize _any_ USB mass storage device (3.0 or 2.0) that is plugged into the Anker card after that time. So far, this problem only seems to occur when I plug something in to the Anker card _after_ boot time. But since the problem appears to be somewhat random... sometimes failing, sometimes not... I cannot tell for sure if pre-boot-time versus post-boot-time device insertion is making any real difference to the problem. After boot time, about 50% of the time when I plug a device... apparently _any_ device... into the Anker card, I will get messages like the following in my /var/log/messages file: ... Mar 18 13:36:44 segfault kernel: xhci_do_command: Command timeout! Mar 18 13:36:44 segfault kernel: usb_alloc_device: set address 3 failed (USB_ERR_TIMEOUT, ignored) Mar 18 13:36:44 segfault kernel: xhci_do_command: Command timeout! Mar 18 13:36:58 segfault last message repeated 47 times Mar 18 13:36:58 segfault kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) Mar 18 13:36:59 segfault kernel: xhci_do_command: Command timeout! Mar 18 13:37:12 segfault last message repeated 41 times Mar 18 13:37:12 segfault kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) Mar 18 13:37:14 segfault kernel: xhci_do_command: Command timeout! Mar 18 13:37:25 segfault last message repeated 39 times Mar 18 13:37:25 segfault kernel: ugen0.3: Unknown at usbus0 (disconnected) Mar 18 13:37:25 segfault kernel: xhci_do_command: Command timeout! Mar 18 13:37:25 segfault kernel: uhub_reattach_port: could not allocate new device Mar 18 13:37:26 segfault kernel: xhci_do_command: Command timeout! ... In all cases where the set of /var/log/messages messages is exactly like what is shown above, after the final messages of the sequence (see above) the little blue power light on my Gauntlet2 box goes out and at that point the kernel absolutely freezes... there is no longer any response from key- board or mouse input, and the system in question then and henceforth refuses to respond even to pings from elsewhere on the same networtk. I have now seen these kernel freezes several times. They can and do happen regardless of whether or not X is running at the time. These kernel freezes are unambiguously linked to the physical act of me plugging in a device to the Anker card... they always happen very shortly thereafter, and only and immediately after the exact sequence of messages shown above are written to /var/log/messages. For the record, the card+driver is/are malfunctioning... specifically not completing the attach of a newly inserted mass storage device... regardless of whether the device just inserted is an external hard drive or an external flash drive, however I have only seen the kernel freezes occur when the device just inserted was an external (self-powered) hard drive. In due course, I will of course file appropriate formal PRs for these USB problems, however for now I am more focused on just getting these bloody things working. (I have already invested a fair amount of time and effort into this little project and I have nothing to show for it, other than some personal aggravation.) So anyway, for right now I just want to debug these problems, if possible, and get this equipment working properly. Along those lines, I have a few questions: 1) What is the best way to debug this? I have seen HPS suggest to others with USB problems that they either (a) use the usbdump(8) command to get more info about the problems or else (b) compile and install a new kernel in which the option USB_DEBUG has been defined. Which should I do, and how may I interpret the results in either case? 2) What are the
