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/168743 usbpanic: double fault caused by umass o usb/168551 usbIssues with embedded card reader (Laptop ASUS K43SJ) 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/166848 usb[umass] [patch] Buffalo RUF2 requires quirk 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/159611 usb[PATCH] USB stick extrememory Snippy needs quirks 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/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] [patch] Add support for Supertop Nano 1GB US o usb/154753 usb[usbdevs] [patch] Support for Qualcomm USB modem/stora o usb/154506 usb[umass] Copying dir with large files makes FreeBSD loa o usb/154192 usb[umass] In Garmin Oregon GPS, only the first umass dev o i386/153851 usb[keyboard] keyboard issues on new Intel Mother boards. o usb/153703 usb[keyboard] My USB keyboard can not be used in 8-STABLE o usb/153609 usb[zyd] [panic] kernel: Fatal trap 12: page fault while o usb/153599 usb[usbdevs] [patch] Feiya Elango USB MicroSD reader sync o usb/153149 usb[umass] USB stick quirk regression [regression] o usb/152075 usb[usb8] [ehci] [request] Add quirk for CS5536 USB o usb/150892 usb[zyd] Whenever network contacted in any shape, way or o usb/150189 usb[run] [usb8] [patch] if_run appears to corrupt IP traf p usb/149764 usb[u3g] [patch] usbdevs update: Huawei K3765 3G modem 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 s usb/148702 usb[usb8] [request] IO DATA USB-RSAQ5 support on FreeBSD- o usb/148080 usbusbconfig(8) sometimes does not turn off the device o usb/147516 usb[umass] [usb67] kernel unable to deal with Olympus USB o i386/147475 usb[install] FreeBSD 8.x does not install on ASUS K8N4-E 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 f 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 p 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 usbGENERIC 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 a usb/143790 usb[boot] [cam] can not boot from usb hdd f usb/143620 usb[cdce]
the usb port is not providing enough juice
Hi, I can't charge iPad using my FreeBD desctop, iPhone/iPod is ok. under Linux there is a patch that does some 'magic', so I was wondering if we have something similar for FreeBSD. cheers, danny ___ 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
Re: the usb port is not providing enough juice
On 11/06/2012, at 22:52, Daniel Braniss wrote: I can't charge iPad using my FreeBD desctop, iPhone/iPod is ok. under Linux there is a patch that does some 'magic', so I was wondering if we have something similar for FreeBSD. Some googling shows.. /usr/ports/sysutils/ipad_charge (which looks like it tells the ipad to draw more current, not to enable magic bits in the port to supply it so YMMV with various USB hardware) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ 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
usb/168743: panic: double fault caused by umass
Hi, This sounds like a missing MODULE_DEPEND() issue or your pendrive is returning an error code to some of the SCSI commands which is not handled properly. Could you add these options to the kernel config file: options KDB # Kernel debugger related code options KDB_TRACE # Print a stack trace for a panic Then get full backtrace. Is this issue reproducable. I cannot reproduce over here using a 9-stable GENERIC kernel without device umass. --HPS ___ 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
usb/168743: panic: double fault caused by umass
The following reply was made to PR usb/168743; it has been noted by GNATS. From: Hans Petter Selasky hsela...@c2i.net To: free...@nagilum.org Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@freebsd.org Subject: usb/168743: panic: double fault caused by umass Date: Mon, 11 Jun 2012 18:57:12 +0200 Hi, This sounds like a missing MODULE_DEPEND() issue or your pendrive is returning an error code to some of the SCSI commands which is not handled properly. Could you add these options to the kernel config file: options KDB # Kernel debugger related code options KDB_TRACE # Print a stack trace for a panic Then get full backtrace. Is this issue reproducable. I cannot reproduce over here using a 9-stable GENERIC kernel without device umass. --HPS ___ 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
Re: usb/168743: panic: double fault caused by umass
I'm compiling a new kernel with those options as I type. Yes, this is very much reproduceable. If you look at the dmesg you will also see the previous reboot for the same reason but with a different device - a WLAN stick that also includes some mass storage for the windows driver and probably another for the mini-sd or whatever card fits in there.. The Pendrive I then used is a 64MB (yes, megabytes) so from that you can probably guess how ancient that thing is so it should not have any new and fancy options aka quirks ;). What I haven't tried yet is simply loading the module while no device is attached. I'll try that when I have the new kernel booted. It will take some time though since this is a 500MHz Geode.. I think I also saw a few other bugreports related to this issue maybe someone else already included a backtrace. Thanks for looking into this, Alex. Zitat von Hans Petter Selasky hsela...@c2i.net: Hi, This sounds like a missing MODULE_DEPEND() issue or your pendrive is returning an error code to some of the SCSI commands which is not handled properly. Could you add these options to the kernel config file: options KDB # Kernel debugger related code options KDB_TRACE # Print a stack trace for a panic Then get full backtrace. Is this issue reproducable. I cannot reproduce over here using a 9-stable GENERIC kernel without device umass. --HPS ___ 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
Re: usb/168743: panic: double fault caused by umass
The following reply was made to PR usb/168743; it has been noted by GNATS. From: free...@nagilum.org To: Hans Petter Selasky hsela...@c2i.net Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@freebsd.org Subject: Re: usb/168743: panic: double fault caused by umass Date: Mon, 11 Jun 2012 19:53:51 +0200 I'm compiling a new kernel with those options as I type. Yes, this is very much reproduceable. If you look at the dmesg you will also see the previous reboot for the same reason but with a different device - a WLAN stick that also includes some mass storage for the windows driver and probably another for the mini-sd or whatever card fits in there.. The Pendrive I then used is a 64MB (yes, megabytes) so from that you can probably guess how ancient that thing is so it should not have any new and fancy options aka quirks ;). What I haven't tried yet is simply loading the module while no device is attached. I'll try that when I have the new kernel booted. It will take some time though since this is a 500MHz Geode.. I think I also saw a few other bugreports related to this issue maybe someone else already included a backtrace. Thanks for looking into this, Alex. Zitat von Hans Petter Selasky hsela...@c2i.net: Hi, This sounds like a missing MODULE_DEPEND() issue or your pendrive is returning an error code to some of the SCSI commands which is not handled properly. Could you add these options to the kernel config file: options KDB # Kernel debugger related code options KDB_TRACE # Print a stack trace for a panic Then get full backtrace. Is this issue reproducable. I cannot reproduce over here using a 9-stable GENERIC kernel without device umass. --HPS ___ 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
