From man at email.com.ua Sun Mar 1 10:07:33 2009 From: man at email.com.ua (Artyom Mirgorodsky) Date: Sun Mar 1 10:07:40 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903010205.37192.man@email.com.ua> References: <200903010045.44904.man@email.com.ua> <200903010038.29534.hselasky@c2i.net> <200903010205.37192.man@email.com.ua> Message-ID: <200903012011.03358.man@email.com.ua> 7.1 livefs test result: dd if=/dev/da0 of=/dev/null bs=65536 19534+0 records in 19534+0 records out 1280180224 bytes transferred in 64.897932 secs (197263329 bytes/sec) systat -vm Disks da0 KB/t 64.00 tps 301 MB/s 18.84 %busy 99 From hselasky at c2i.net Sun Mar 1 10:58:55 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Mar 1 10:59:01 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903012011.03358.man@email.com.ua> References: <200903010045.44904.man@email.com.ua> <200903010205.37192.man@email.com.ua> <200903012011.03358.man@email.com.ua> Message-ID: <200903012001.21543.hselasky@c2i.net> On Sunday 01 March 2009, Artyom Mirgorodsky wrote: > 7.1 livefs test result: > > dd if=/dev/da0 of=/dev/null bs=65536 > 19534+0 records in > 19534+0 records out > 1280180224 bytes transferred in 64.897932 secs (197263329 bytes/sec) > Hi, It might be a bug with your memory stick. Are your findings consistent accross other brands of memory sticks aswell, between 7.1 and 8.x ? --HPS From thompsa at FreeBSD.org Sun Mar 1 11:01:03 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Mar 1 11:01:10 2009 Subject: USB2+umass: root mount fails In-Reply-To: References: Message-ID: <20090301190057.GD90301@citylink.fud.org.nz> On Mon, Feb 16, 2009 at 01:53:36PM -0800, Marcel Moolenaar wrote: > It appears that the root mount isn't serialized with USB discovery > in the same way it was under USB1. It seems that this is not completly resolved with the root mount hold in r188907 as geom may not have tasted the partition tables when vfs_rootmount is woken. USB still needs to finish its bus probe earlier on the boot process. Andrew From imp at bsdimp.com Sun Mar 1 11:19:17 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 1 11:19:24 2009 Subject: USB2+umass: root mount fails In-Reply-To: <20090301190057.GD90301@citylink.fud.org.nz> References: <20090301190057.GD90301@citylink.fud.org.nz> Message-ID: <20090301.121620.-2073256982.imp@bsdimp.com> In message: <20090301190057.GD90301@citylink.fud.org.nz> Andrew Thompson writes: : On Mon, Feb 16, 2009 at 01:53:36PM -0800, Marcel Moolenaar wrote: : > It appears that the root mount isn't serialized with USB discovery : > in the same way it was under USB1. : : It seems that this is not completly resolved with the root mount hold in : r188907 as geom may not have tasted the partition tables when : vfs_rootmount is woken. USB still needs to finish its bus probe earlier : on the boot process. This sounds like a more fundamental ordering problem. It sounds like we need two gates here. (1) All the underlying devices are there and (2) All tasting is done. Warner From thompsa at FreeBSD.org Sun Mar 1 11:25:57 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Mar 1 11:26:04 2009 Subject: USB2+umass: root mount fails In-Reply-To: <20090301.121620.-2073256982.imp@bsdimp.com> References: <20090301190057.GD90301@citylink.fud.org.nz> <20090301.121620.-2073256982.imp@bsdimp.com> Message-ID: <20090301192551.GA57940@citylink.fud.org.nz> On Sun, Mar 01, 2009 at 12:16:20PM -0700, M. Warner Losh wrote: > In message: <20090301190057.GD90301@citylink.fud.org.nz> > Andrew Thompson writes: > : On Mon, Feb 16, 2009 at 01:53:36PM -0800, Marcel Moolenaar wrote: > : > It appears that the root mount isn't serialized with USB discovery > : > in the same way it was under USB1. > : > : It seems that this is not completly resolved with the root mount hold in > : r188907 as geom may not have tasted the partition tables when > : vfs_rootmount is woken. USB still needs to finish its bus probe earlier > : on the boot process. > > This sounds like a more fundamental ordering problem. It sounds like > we need two gates here. (1) All the underlying devices are there and > (2) All tasting is done. So should another root hold token be grabbed in disk_create() and released on taste? Andrew From agniaus at gmail.com Sun Mar 1 12:36:23 2009 From: agniaus at gmail.com (Agnius) Date: Sun Mar 1 12:37:05 2009 Subject: axe usb network adapter problems Message-ID: <22277434.post@talk.nabble.com> I have http://www.a-link.com/uk/NA1GU.html?id=dr7bZGZG OS FreeBSD 7.1 When I use axe.88178.patch4 adapter begin work axe0: on uhub3 axe0: AX88178, bufsz 1536, boundary 64 axe0: PHYADDR 0xe0:0x18 miibus0: on axe0 ciphy0: PHY 24 on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto axe0: WARNING: using obsoleted if_watchdog interface axe0: WARNING: using obsoleted IFF_NEEDSGIANT flag axe0: Ethernet address: 00:1a:9f:0b:02:ea But I found problems: 1. I can not use TX and RX 2. Many errors: netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll axe0 1500 00:1a:9f:0b:02:ea 996093 15890 701185 0 0 3. Max speed ~4000 kbytes/s -- View this message in context: http://www.nabble.com/axe-usb-network-adapter-problems-tp22277434p22277434.html Sent from the freebsd-usb mailing list archive at Nabble.com. From agniaus at gmail.com Sun Mar 1 12:36:23 2009 From: agniaus at gmail.com (Agnius) Date: Sun Mar 1 12:37:05 2009 Subject: axe usb networ adapter problems Message-ID: <22277434.post@talk.nabble.com> I have http://www.a-link.com/uk/NA1GU.html?id=dr7bZGZG OS FreeBSD 7.1 When I use axe.88178.patch4 adapter begin work axe0: on uhub3 axe0: AX88178, bufsz 1536, boundary 64 axe0: PHYADDR 0xe0:0x18 miibus0: on axe0 ciphy0: PHY 24 on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto axe0: WARNING: using obsoleted if_watchdog interface axe0: WARNING: using obsoleted IFF_NEEDSGIANT flag axe0: Ethernet address: 00:1a:9f:0b:02:ea But I found problems: 1. I can not use TX and RX 2. Many errors: netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll axe0 1500 00:1a:9f:0b:02:ea 996093 15890 701185 0 0 3. Max speed ~4000 kbytes/s -- View this message in context: http://www.nabble.com/axe-usb-networ-adapter-problems-tp22277434p22277434.html Sent from the freebsd-usb mailing list archive at Nabble.com. From agniaus at gmail.com Sun Mar 1 12:36:24 2009 From: agniaus at gmail.com (Agnius) Date: Sun Mar 1 12:37:06 2009 Subject: axe usb networ adapter problems Message-ID: <22277434.post@talk.nabble.com> I have http://www.a-link.com/uk/NA1GU.html?id=dr7bZGZG OS FreeBSD 7.1 When I use axe.88178.patch4 adapter begin work axe0: on uhub3 axe0: AX88178, bufsz 1536, boundary 64 axe0: PHYADDR 0xe0:0x18 miibus0: on axe0 ciphy0: PHY 24 on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto axe0: WARNING: using obsoleted if_watchdog interface axe0: WARNING: using obsoleted IFF_NEEDSGIANT flag axe0: Ethernet address: 00:1a:9f:0b:02:ea But I found problems: 1. I can not use TX and RX 2. Many errors: netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll axe0 1500 00:1a:9f:0b:02:ea 996093 15890 701185 0 0 3. Max speed ~4000 kbytes/s -- View this message in context: http://www.nabble.com/axe-usb-networ-adapter-problems-tp22277434p22277434.html Sent from the freebsd-usb mailing list archive at Nabble.com. From yanefbsd at gmail.com Sun Mar 1 18:25:23 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Mar 1 18:25:29 2009 Subject: ums no longer loads on CURRENT Message-ID: Recently built kernel as of today around 4pm. The mouse is available on the console and moused isn't running; this issue prevents me from using X11. I'm looking for all libraries linked against libusb-0.1.so. 8 right now... More details: [root@orangebox /usr/home/gcooper]# kldload ums module_register: module ushub/ums already exists! Module ushub/ums failed to register: 17 kldload: can't load ums: File exists [root@orangebox /usr/home/gcooper]# cat /root/ORANGEBOX-common /root/ ORANGEBOX # START COMMON INCLUDE FILE cpu I686_CPU ident ORANGEBOX # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking #options INET6 # IPv6 communications protocols options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD # Network Lock Manager options NFS_ROOT # NFS usable as /, requires NFSCLIENT options NTFS # NT File System options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_BSD options GEOM_MBR options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options STOP_NMI # Stop CPUS using NMI instead of IPI options AUDIT # Security event auditing options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) # Debugging for use in -current options KDB # Enable kernel debugger support. options KDB_UNATTENDED # I don't want to be here when shit crashes.. options DDB # Support DDB. options GDB # Support remote GDB. options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS #options WITNESS # Enable checks to detect deadlocks and cycles #options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed options COMPAT_LINUX # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel device apic # CPU frequency control device cpufreq # Bus support. device acpi device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicam # Required for [C|DV]D burning #device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives #device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Serial (COM) ports device uart # Generic UART driver # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to sio, uart and/or ppc drivers): #device sio # PCI Ethernet NICs. device em # Intel PRO/1000 Gigabit Ethernet Family # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device msk # Marvell/SysKonnect Yukon II Gigabit Ethernet # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" #device gif # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) device firmware # firmware assist module # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # FireWire support device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device dcons device sound device snd_emu10kx # END COMMON INCLUDE FILE include "ORANGEBOX-common" # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse #device uscanner # Scanners # USB <-> RS232 adapter. device uplcom device ucom [root@orangebox /usr/home/gcooper]# uname -a FreeBSD orangebox.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT #2: Sun Mar 1 16:42:18 PST 2009 root@orangebox.gateway.2wire.net:/ usr/obj/usr/src/sys/ORANGEBOX i386 From imp at bsdimp.com Sun Mar 1 18:46:35 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 1 18:46:48 2009 Subject: ums no longer loads on CURRENT In-Reply-To: References: Message-ID: <20090301.194410.1927934231.imp@bsdimp.com> In message: Garrett Cooper writes: : Recently built kernel as of today around 4pm. The mouse is available : on the console and moused isn't running; this issue prevents me from : using X11. I'm looking for all libraries linked against libusb-0.1.so. : 8 right now... Did you read updating? Warner : More details: : : [root@orangebox /usr/home/gcooper]# kldload ums : module_register: module ushub/ums already exists! : Module ushub/ums failed to register: 17 : kldload: can't load ums: File exists : : [root@orangebox /usr/home/gcooper]# cat /root/ORANGEBOX-common /root/ : ORANGEBOX : # START COMMON INCLUDE FILE : : cpu I686_CPU : ident ORANGEBOX : : # To statically compile in device wiring instead of /boot/device.hints : #hints "GENERIC.hints" # Default places to look for devices. : : makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols : : options SCHED_ULE # ULE scheduler : options PREEMPTION # Enable kernel thread preemption : options INET # InterNETworking : #options INET6 # IPv6 communications protocols : options SCTP # Stream Control Transmission Protocol : options FFS # Berkeley Fast Filesystem : options SOFTUPDATES # Enable FFS soft updates support : options UFS_ACL # Support for access control lists : options UFS_DIRHASH # Improve performance on big directories : options UFS_GJOURNAL # Enable gjournal-based UFS journaling : options MD_ROOT # MD is a potential root device : options NFSCLIENT # Network Filesystem Client : options NFSSERVER # Network Filesystem Server : options NFSLOCKD # Network Lock Manager : options NFS_ROOT # NFS usable as /, requires NFSCLIENT : options NTFS # NT File System : options MSDOSFS # MSDOS Filesystem : options CD9660 # ISO 9660 Filesystem : options PROCFS # Process filesystem (requires PSEUDOFS) : options PSEUDOFS # Pseudo-filesystem framework : options GEOM_BSD : options GEOM_MBR : options GEOM_PART_GPT # GUID Partition Tables. : options GEOM_LABEL # Provides labelization : options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!] : options COMPAT_FREEBSD4 # Compatible with FreeBSD4 : options COMPAT_FREEBSD5 # Compatible with FreeBSD5 : options COMPAT_FREEBSD6 # Compatible with FreeBSD6 : options COMPAT_FREEBSD7 # Compatible with FreeBSD7 : options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI : options KTRACE # ktrace(1) support : options STACK # stack(9) support : options SYSVSHM # SYSV-style shared memory : options SYSVMSG # SYSV-style message queues : options SYSVSEM # SYSV-style semaphores : options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time : extensions : options KBD_INSTALL_CDEV # install a CDEV entry in /dev : options STOP_NMI # Stop CPUS using NMI instead of IPI : options AUDIT # Security event auditing : options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) : : # Debugging for use in -current : options KDB # Enable kernel debugger support. : options KDB_UNATTENDED # I don't want to be here when shit crashes.. : options DDB # Support DDB. : options GDB # Support remote GDB. : options INVARIANTS # Enable calls of extra sanity checking : options INVARIANT_SUPPORT # Extra sanity checks of internal : structures, required by INVARIANTS : #options WITNESS # Enable checks to detect deadlocks and cycles : #options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed : options COMPAT_LINUX : : # Make an SMP-capable kernel by default : options SMP # Symmetric MultiProcessor Kernel : : device apic : : # CPU frequency control : device cpufreq : : # Bus support. : device acpi : device pci : : # ATA and ATAPI devices : device ata : device atadisk # ATA disk drives : device atapicam # Required for [C|DV]D burning : #device ataraid # ATA RAID drives : device atapicd # ATAPI CDROM drives : #device atapist # ATAPI tape drives : options ATA_STATIC_ID # Static device numbering : : # SCSI peripherals : device scbus # SCSI bus (required for SCSI) : device ch # SCSI media changers : device da # Direct Access (disks) : device cd # CD : device pass # Passthrough device (direct SCSI access) : : # atkbdc0 controls both the keyboard and the PS/2 mouse : device atkbdc # AT keyboard controller : device atkbd # AT keyboard : device psm # PS/2 mouse : : device kbdmux # keyboard multiplexer : : device vga # VGA video card driver : : device splash # Splash screen and screen saver support : : # syscons is the default console driver, resembling an SCO console : device sc : : device agp # support several AGP chipsets : : # Serial (COM) ports : device uart # Generic UART driver : : # If you've got a "dumb" serial or parallel PCI card that is : # supported by the puc(4) glue driver, uncomment the following : # line to enable it (connects to sio, uart and/or ppc drivers): : #device sio : : # PCI Ethernet NICs. : device em # Intel PRO/1000 Gigabit Ethernet Family : : # PCI Ethernet NICs that use the common MII bus controller code. : # NOTE: Be sure to keep the 'device miibus' line in order to use these : NICs! : device miibus # MII bus support : device msk # Marvell/SysKonnect Yukon II Gigabit Ethernet : : # Pseudo devices. : device loop # Network loopback : device random # Entropy device : device ether # Ethernet support : device tun # Packet tunnel. : device pty # Pseudo-ttys (telnet etc) : device md # Memory "disks" : #device gif # IPv6 and IPv4 tunneling : #device faith # IPv6-to-IPv4 relaying (translation) : device firmware # firmware assist module : : # The `bpf' device enables the Berkeley Packet Filter. : # Be aware of the administrative consequences of enabling this! : # Note that 'bpf' is required for DHCP. : device bpf # Berkeley packet filter : : # FireWire support : device firewire # FireWire bus code : device sbp # SCSI over FireWire (Requires scbus and da) : device dcons : : device sound : device snd_emu10kx : : # END COMMON INCLUDE FILE : include "ORANGEBOX-common" : : # USB support : device uhci # UHCI PCI->USB interface : device ohci # OHCI PCI->USB interface : device ehci # EHCI PCI->USB interface (USB 2.0) : device usb # USB Bus (required) : #device udbp # USB Double Bulk Pipe devices : device uhid # "Human Interface Devices" : device ukbd # Keyboard : device ulpt # Printer : device umass # Disks/Mass storage - Requires scbus and da : device ums # Mouse : #device uscanner # Scanners : : # USB <-> RS232 adapter. : device uplcom : device ucom : : [root@orangebox /usr/home/gcooper]# uname -a : FreeBSD orangebox.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT : #2: Sun Mar 1 16:42:18 PST 2009 root@orangebox.gateway.2wire.net:/ : usr/obj/usr/src/sys/ORANGEBOX i386 : _______________________________________________ : 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" : : From yanefbsd at gmail.com Sun Mar 1 19:14:35 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Mar 1 19:14:42 2009 Subject: ums no longer loads on CURRENT In-Reply-To: <49AB4649.40906@freebsd.org> References: <49AB4649.40906@freebsd.org> Message-ID: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: > Garrett Cooper wrote: >> device ums # Mouse > > This is why you cannot kldload. Not sure about any functional > regression. > > Sam Yeah, well that message was printed out by another process altogether while loading up the kernel after the ata subsystem was brought up, so something's getting confused and trying to kldload by accident... I was just reproducing the message. I'll provide more data to prove this claim when I can. Thanks, -Garrett From yanefbsd at gmail.com Sun Mar 1 19:30:57 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Mar 1 19:31:09 2009 Subject: ums no longer loads on CURRENT In-Reply-To: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> References: <49AB4649.40906@freebsd.org> <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> Message-ID: <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> On Mar 1, 2009, at 7:20 PM, Garrett Cooper wrote: > On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: > >> Garrett Cooper wrote: >>> device ums # Mouse >> >> This is why you cannot kldload. Not sure about any functional >> regression. >> >> Sam > > Yeah, well that message was printed out by another process > altogether while loading up the kernel after the ata subsystem was > brought up, so something's getting confused and trying to kldload by > accident... I was just reproducing the message. > I'll provide more data to prove this claim when I can. > Thanks, > -Garrett Here's the picture from my iPhone: . I OBVIOUSLY didn't do the kldload... and because my /boot/ loader.conf doesn't contain ums_load="YES", I'm really curious who the actual culprit is in rc.d land... I used to do WITHOUT_MODULES=* to not build modules, but I'm trying to move away from that mentality for some things like snd_emu10kx, but obviously there's a conflict somewhere for ums; hopefully it's merely cosmetic... Thanks, -Garrett From yanefbsd at gmail.com Sun Mar 1 19:41:27 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Mar 1 19:41:38 2009 Subject: The rc.d mess strikes back (was Re: ums no longer loads on CURRENT) In-Reply-To: <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> References: <49AB4649.40906@freebsd.org> <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> Message-ID: On Mar 1, 2009, at 7:36 PM, Garrett Cooper wrote: > On Mar 1, 2009, at 7:20 PM, Garrett Cooper wrote: > >> On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: >> >>> Garrett Cooper wrote: >>>> device ums # Mouse >>> >>> This is why you cannot kldload. Not sure about any functional >>> regression. >>> >>> Sam >> >> Yeah, well that message was printed out by another process >> altogether while loading up the kernel after the ata subsystem was >> brought up, so something's getting confused and trying to kldload >> by accident... I was just reproducing the message. >> I'll provide more data to prove this claim when I can. >> Thanks, >> -Garrett > > Here's the picture from my iPhone: >. I OBVIOUSLY didn't do the kldload... and because my /boot/ > loader.conf doesn't contain ums_load="YES", I'm really curious who > the actual culprit is in rc.d land... > I used to do WITHOUT_MODULES=* to not build modules, but I'm trying > to move away from that mentality for some things like snd_emu10kx, > but obviously there's a conflict somewhere for ums; hopefully it's > merely cosmetic... > Thanks, > -Garrett Ok, found the culprit. It turns out moused is being called from devd... this is all probably related to the startup mess I reported 2 weeks ago with my NIC. I'm seeing a lot of additional problems in terms of keeping track of daemons; for instance syslogd is getting started up twice, but the first instance isn't recording a PID and the second one is dying because the first one is bound to the address. Agh... Could we just unwind this rc.d mess? It seems to be causing issues and wasn't very thoroughly tested before commit. Thanks, -Garrett From imp at bsdimp.com Sun Mar 1 19:51:47 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 1 19:51:59 2009 Subject: The rc.d mess strikes back In-Reply-To: References: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> Message-ID: <20090301.205017.1025328203.imp@bsdimp.com> In message: Garrett Cooper writes: : On Mar 1, 2009, at 7:36 PM, Garrett Cooper wrote: : : > On Mar 1, 2009, at 7:20 PM, Garrett Cooper wrote: : > : >> On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: : >> : >>> Garrett Cooper wrote: : >>>> device ums # Mouse : >>> : >>> This is why you cannot kldload. Not sure about any functional : >>> regression. : >>> : >>> Sam : >> : >> Yeah, well that message was printed out by another process : >> altogether while loading up the kernel after the ata subsystem was : >> brought up, so something's getting confused and trying to kldload : >> by accident... I was just reproducing the message. : >> I'll provide more data to prove this claim when I can. : >> Thanks, : >> -Garrett : > : > Here's the picture from my iPhone: >. I OBVIOUSLY didn't do the kldload... and because my /boot/ : > loader.conf doesn't contain ums_load="YES", I'm really curious who : > the actual culprit is in rc.d land... : > I used to do WITHOUT_MODULES=* to not build modules, but I'm trying : > to move away from that mentality for some things like snd_emu10kx, : > but obviously there's a conflict somewhere for ums; hopefully it's : > merely cosmetic... : > Thanks, : > -Garrett : : Ok, found the culprit. It turns out moused is being called from : devd... this is all probably related to the startup mess I reported 2 : weeks ago with my NIC. I'm seeing a lot of additional problems in : terms of keeping track of daemons; for instance syslogd is getting : started up twice, but the first instance isn't recording a PID and the : second one is dying because the first one is bound to the address. : Agh... I didn't think that moused loaded anything. And what do extra nics have to do with this? I think you are confusing multiple problems... : Could we just unwind this rc.d mess? It seems to be causing issues : and wasn't very thoroughly tested before commit. This is a little to vague to be actionable. Do you have specific instances? Do you have rcorder output? Etc... Warner From yanefbsd at gmail.com Sun Mar 1 19:53:25 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Mar 1 19:53:37 2009 Subject: ums no longer loads on CURRENT In-Reply-To: <20090301.194410.1927934231.imp@bsdimp.com> References: <20090301.194410.1927934231.imp@bsdimp.com> Message-ID: On Mar 1, 2009, at 6:44 PM, M. Warner Losh wrote: > In message: > Garrett Cooper writes: > : Recently built kernel as of today around 4pm. The mouse is available > : on the console and moused isn't running; this issue prevents me from > : using X11. I'm looking for all libraries linked against > libusb-0.1.so. > : 8 right now... > > Did you read updating? Yes, I did. The only problem is that I can't find anything linked against that library; then again my one-liner was probably screwed up so I'll check again later. I'll applied the libmap.conf suggestion and that solved that issue. Yet I've unhappily uncovered something else that needs to be solved with rc.d :(... Since I started up this thread, I'll be more than happy to note what apps I encounter that need to be rebuilt so it can be further documented in UPDATING. Thanks, -Garrett From yanefbsd at gmail.com Sun Mar 1 20:02:15 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Mar 1 20:02:27 2009 Subject: The rc.d mess strikes back In-Reply-To: <20090301.205017.1025328203.imp@bsdimp.com> References: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> <20090301.205017.1025328203.imp@bsdimp.com> Message-ID: <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com> On Mar 1, 2009, at 7:50 PM, M. Warner Losh wrote: > In message: > Garrett Cooper writes: > : On Mar 1, 2009, at 7:36 PM, Garrett Cooper wrote: > : > : > On Mar 1, 2009, at 7:20 PM, Garrett Cooper wrote: > : > > : >> On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: > : >> > : >>> Garrett Cooper wrote: > : >>>> device ums # Mouse > : >>> > : >>> This is why you cannot kldload. Not sure about any functional > : >>> regression. > : >>> > : >>> Sam > : >> > : >> Yeah, well that message was printed out by another process > : >> altogether while loading up the kernel after the ata subsystem > was > : >> brought up, so something's getting confused and trying to kldload > : >> by accident... I was just reproducing the message. > : >> I'll provide more data to prove this claim when I can. > : >> Thanks, > : >> -Garrett > : > > : > Here's the picture from my iPhone: : > >. I OBVIOUSLY didn't do the kldload... and because my /boot/ > : > loader.conf doesn't contain ums_load="YES", I'm really curious who > : > the actual culprit is in rc.d land... > : > I used to do WITHOUT_MODULES=* to not build modules, but I'm > trying > : > to move away from that mentality for some things like snd_emu10kx, > : > but obviously there's a conflict somewhere for ums; hopefully it's > : > merely cosmetic... > : > Thanks, > : > -Garrett > : > : Ok, found the culprit. It turns out moused is being called from > : devd... this is all probably related to the startup mess I > reported 2 > : weeks ago with my NIC. I'm seeing a lot of additional problems in > : terms of keeping track of daemons; for instance syslogd is getting > : started up twice, but the first instance isn't recording a PID and > the > : second one is dying because the first one is bound to the address. > : Agh... > > I didn't think that moused loaded anything. > > And what do extra nics have to do with this? I think you are > confusing multiple problems... > > : Could we just unwind this rc.d mess? It seems to be causing issues > : and wasn't very thoroughly tested before commit. > > This is a little to vague to be actionable. Do you have specific > instances? Do you have rcorder output? Etc... > > Warner For whatever reason the NFS filemounts not coming up forces rc.d to restart from a square one (because it enters maintenance mode), which nukes PID files in /var/run (I'm assuming) via the cleanvar service, and causes devd and syslogd to be started twice, which in turn causes that message to be printed out on the console. devd's rc script is just smart enough to recognize that there's a PID already running on the system, and thus it doesn't try to start more than once, but syslogd's is braindead (is there really a point to running multiple instances of syslogd?) and thus it tries to start up the service twice. I'm understand why devd attempts to probe and install ums in the kernel's namespace if it already exists... but I'm unhappy with the fact that even though I set moused_enable=NO in rc.conf, moused still doesn't honor that option ;(... -Garrett From sam at freebsd.org Sun Mar 1 20:08:04 2009 From: sam at freebsd.org (Sam Leffler) Date: Sun Mar 1 20:08:21 2009 Subject: The rc.d mess strikes back In-Reply-To: <20090301.205017.1025328203.imp@bsdimp.com> References: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> <20090301.205017.1025328203.imp@bsdimp.com> Message-ID: <49AB5BA0.9070406@freebsd.org> M. Warner Losh wrote: > In message: > Garrett Cooper writes: > : On Mar 1, 2009, at 7:36 PM, Garrett Cooper wrote: > : > : > On Mar 1, 2009, at 7:20 PM, Garrett Cooper wrote: > : > > : >> On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: > : >> > : >>> Garrett Cooper wrote: > : >>>> device ums # Mouse > : >>> > : >>> This is why you cannot kldload. Not sure about any functional > : >>> regression. > : >>> > : >>> Sam > : >> > : >> Yeah, well that message was printed out by another process > : >> altogether while loading up the kernel after the ata subsystem was > : >> brought up, so something's getting confused and trying to kldload > : >> by accident... I was just reproducing the message. > : >> I'll provide more data to prove this claim when I can. > : >> Thanks, > : >> -Garrett > : > > : > Here's the picture from my iPhone: : > >. I OBVIOUSLY didn't do the kldload... and because my /boot/ > : > loader.conf doesn't contain ums_load="YES", I'm really curious who > : > the actual culprit is in rc.d land... > : > I used to do WITHOUT_MODULES=* to not build modules, but I'm trying > : > to move away from that mentality for some things like snd_emu10kx, > : > but obviously there's a conflict somewhere for ums; hopefully it's > : > merely cosmetic... > : > Thanks, > : > -Garrett > : > : Ok, found the culprit. It turns out moused is being called from > : devd... this is all probably related to the startup mess I reported 2 > : weeks ago with my NIC. I'm seeing a lot of additional problems in > : terms of keeping track of daemons; for instance syslogd is getting > : started up twice, but the first instance isn't recording a PID and the > : second one is dying because the first one is bound to the address. > : Agh... > > I didn't think that moused loaded anything. > > And what do extra nics have to do with this? I think you are > confusing multiple problems... > > : Could we just unwind this rc.d mess? It seems to be causing issues > : and wasn't very thoroughly tested before commit. > > This is a little to vague to be actionable. Do you have specific > instances? Do you have rcorder output? Etc... > I saw a similar problem today; if I have a wireless nic setup with ifconfig_ath0="wlan0" ifconfig_wlan0="WPA DHCP" then two instances of wpa_supplicant are launched when I do /etc/rc.d/netif start ath0 (you get log msgs from wpa_supplicant about not being able to setup the /var/run/wpa_supplicant/wlan0 unix domain socket). Wasn't able to pin it down but it's likely the same issue. Sam From yanefbsd at gmail.com Sun Mar 1 20:24:58 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Mar 1 20:25:10 2009 Subject: ums no longer loads on CURRENT In-Reply-To: References: <20090301.194410.1927934231.imp@bsdimp.com> Message-ID: <7d6fde3d0903012024t3eafacdbx4edf5c2a8645d53e@mail.gmail.com> On Sun, Mar 1, 2009 at 7:58 PM, Garrett Cooper wrote: > On Mar 1, 2009, at 6:44 PM, M. Warner Losh wrote: > >> In message: >> ? ? ? ? ? Garrett Cooper writes: >> : Recently built kernel as of today around 4pm. The mouse is available >> : on the console and moused isn't running; this issue prevents me from >> : using X11. I'm looking for all libraries linked against libusb-0.1.so. >> : 8 right now... >> >> Did you read updating? > > Yes, I did. The only problem is that I can't find anything linked against > that library; then again my one-liner was probably screwed up so I'll check > again later. > > I'll applied the libmap.conf suggestion and that solved that issue. Yet I've > unhappily uncovered something else that needs to be solved with rc.d :(... > > Since I started up this thread, I'll be more than happy to note what apps I > encounter that need to be rebuilt so it can be further documented in > UPDATING. > > Thanks, > -Garrett I think I've tied down the issue in part with hal, etc. I have perforce installed on the system, along with nvidia-kernel, which means that I need misc/compat-5x. Unfortunately compat-5x installs libusbhid.so.1, which no doubt conflicts with the installed copy we have in /usr/lib, but through the glorious thing known as autoconf with ports, I believe it's picking up the copy in /usr/local/lib/compat/... I could be wrong though. Thoughts? Thanks, -Garrett From thompsa at FreeBSD.org Sun Mar 1 20:30:20 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Mar 1 20:30:31 2009 Subject: ums no longer loads on CURRENT In-Reply-To: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> References: <49AB4649.40906@freebsd.org> <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> Message-ID: <20090302043013.GA66136@citylink.fud.org.nz> On Sun, Mar 01, 2009 at 07:20:03PM -0800, Garrett Cooper wrote: > On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: > >> Garrett Cooper wrote: >>> device ums # Mouse >> >> This is why you cannot kldload. Not sure about any functional regression. >> >> Sam > > Yeah, well that message was printed out by another process altogether > while loading up the kernel after the ata subsystem was brought up, so > something's getting confused and trying to kldload by accident... I was > just reproducing the message. > I'll provide more data to prove this claim when I can. I have traced this already but not looked into why, the process trying to (re)load ums is moused. Andrew From yanefbsd at gmail.com Sun Mar 1 20:41:36 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Mar 1 20:41:48 2009 Subject: ums no longer loads on CURRENT In-Reply-To: <20090302043013.GA66136@citylink.fud.org.nz> References: <49AB4649.40906@freebsd.org> <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <20090302043013.GA66136@citylink.fud.org.nz> Message-ID: <7d6fde3d0903012041l76436344o6db7660a3fa8cf37@mail.gmail.com> On Sun, Mar 1, 2009 at 8:30 PM, Andrew Thompson wrote: > On Sun, Mar 01, 2009 at 07:20:03PM -0800, Garrett Cooper wrote: >> On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: >> >>> Garrett Cooper wrote: >>>> device ? ? ? ?ums ? ? ? ?# Mouse >>> >>> This is why you cannot kldload. ?Not sure about any functional regression. >>> >>> ? Sam >> >> ? ? ? Yeah, well that message was printed out by another process altogether >> while loading up the kernel after the ata subsystem was brought up, so >> something's getting confused and trying to kldload by accident... I was >> just reproducing the message. >> ? ? ? I'll provide more data to prove this claim when I can. > > I have traced this already but not looked into why, the process trying > to (re)load ums is moused. > > > Andrew It's being done from devd's end, but I'd really like it if the terse messaging would go away because it confused the heck out of me... the issue was ABI/libmap.conf related like Warner put down in UPDATING, but I instead opened up another can of worms ;(... Thanks, -Garrett From thompsa at FreeBSD.org Sun Mar 1 20:44:56 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Mar 1 20:45:03 2009 Subject: ums no longer loads on CURRENT In-Reply-To: <7d6fde3d0903012041l76436344o6db7660a3fa8cf37@mail.gmail.com> References: <49AB4649.40906@freebsd.org> <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <20090302043013.GA66136@citylink.fud.org.nz> <7d6fde3d0903012041l76436344o6db7660a3fa8cf37@mail.gmail.com> Message-ID: <20090302044446.GC66136@citylink.fud.org.nz> On Sun, Mar 01, 2009 at 08:41:35PM -0800, Garrett Cooper wrote: > On Sun, Mar 1, 2009 at 8:30 PM, Andrew Thompson wrote: > > On Sun, Mar 01, 2009 at 07:20:03PM -0800, Garrett Cooper wrote: > >> On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: > >> > >>> Garrett Cooper wrote: > >>>> device ? ? ? ?ums ? ? ? ?# Mouse > >>> > >>> This is why you cannot kldload. ?Not sure about any functional regression. > >>> > >>> ? Sam > >> > >> ? ? ? Yeah, well that message was printed out by another process altogether > >> while loading up the kernel after the ata subsystem was brought up, so > >> something's getting confused and trying to kldload by accident... I was > >> just reproducing the message. > >> ? ? ? I'll provide more data to prove this claim when I can. > > > > I have traced this already but not looked into why, the process trying > > to (re)load ums is moused. > > > > > > Andrew > > It's being done from devd's end, but I'd really like it if the > terse messaging would go away because it confused the heck out of > me... the issue was ABI/libmap.conf related like Warner put down in > UPDATING, but I instead opened up another can of worms ;(... > Thanks, A quick look found it, static int usbmodule(void) { return (kld_isloaded("uhub/ums") || kld_load("ums") != -1); } its now called ushub/ums. It can probably be renamed back to uhub now. Andrew From yanefbsd at gmail.com Sun Mar 1 21:39:02 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Mar 1 21:39:09 2009 Subject: The rc.d mess strikes back In-Reply-To: <49AB6C1E.1030808@acm.poly.edu> References: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> <20090301.205017.1025328203.imp@bsdimp.com> <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com> <49AB6C1E.1030808@acm.poly.edu> Message-ID: <775D7BE8-DF85-4119-9A7D-6ED349E96EC5@gmail.com> On Mar 1, 2009, at 9:18 PM, Boris Kochergin wrote: > Garrett Cooper wrote: >> On Mar 1, 2009, at 7:50 PM, M. Warner Losh wrote: >> >>> In message: >>> Garrett Cooper writes: >>> : On Mar 1, 2009, at 7:36 PM, Garrett Cooper wrote: >>> : >>> : > On Mar 1, 2009, at 7:20 PM, Garrett Cooper wrote: >>> : > >>> : >> On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: >>> : >> >>> : >>> Garrett Cooper wrote: >>> : >>>> device ums # Mouse >>> : >>> >>> : >>> This is why you cannot kldload. Not sure about any functional >>> : >>> regression. >>> : >>> >>> : >>> Sam >>> : >> >>> : >> Yeah, well that message was printed out by another process >>> : >> altogether while loading up the kernel after the ata >>> subsystem was >>> : >> brought up, so something's getting confused and trying to >>> kldload >>> : >> by accident... I was just reproducing the message. >>> : >> I'll provide more data to prove this claim when I can. >>> : >> Thanks, >>> : >> -Garrett >>> : > >>> : > Here's the picture from my iPhone: >> : > >. I OBVIOUSLY didn't do the kldload... and because my /boot/ >>> : > loader.conf doesn't contain ums_load="YES", I'm really curious >>> who >>> : > the actual culprit is in rc.d land... >>> : > I used to do WITHOUT_MODULES=* to not build modules, but >>> I'm trying >>> : > to move away from that mentality for some things like >>> snd_emu10kx, >>> : > but obviously there's a conflict somewhere for ums; hopefully >>> it's >>> : > merely cosmetic... >>> : > Thanks, >>> : > -Garrett >>> : >>> : Ok, found the culprit. It turns out moused is being called >>> from >>> : devd... this is all probably related to the startup mess I >>> reported 2 >>> : weeks ago with my NIC. I'm seeing a lot of additional problems in >>> : terms of keeping track of daemons; for instance syslogd is getting >>> : started up twice, but the first instance isn't recording a PID >>> and the >>> : second one is dying because the first one is bound to the address. >>> : Agh... >>> >>> I didn't think that moused loaded anything. >>> >>> And what do extra nics have to do with this? I think you are >>> confusing multiple problems... >>> >>> : Could we just unwind this rc.d mess? It seems to be causing >>> issues >>> : and wasn't very thoroughly tested before commit. >>> >>> This is a little to vague to be actionable. Do you have specific >>> instances? Do you have rcorder output? Etc... >>> >>> Warner >> >> For whatever reason the NFS filemounts not coming up forces rc.d >> to restart from a square one (because it enters maintenance mode), >> which nukes PID files in /var/run (I'm assuming) via the cleanvar >> service, and causes devd and syslogd to be started twice, which in >> turn causes that message to be printed out on the console. devd's >> rc script is just smart enough to recognize that there's a PID >> already running on the system, and thus it doesn't try to start >> more than once, but syslogd's is braindead (is there really a point >> to running multiple instances of syslogd?) and thus it tries to >> start up the service twice. >> I'm understand why devd attempts to probe and install ums in the >> kernel's namespace if it already exists... but I'm unhappy with the >> fact that even though I set moused_enable=NO in rc.conf, moused >> still doesn't honor that option ;(... >> -Garrett >> >> With regard to NFS breaking your boot process, I have run into the >> same thing recently, but it was my fault. Your screenshot omits the >> potentially-interesting information, if the problem is the same. In >> my case, /etc/rc.d/* was out of sync with /etc/network.subr. /etc/ >> rc.d/netif, which handles the ifconfig_* lines in rc.conf, has >> references to an ifn_start() function in /etc/network.subr, so >> interfaces configured in rc.conf never came up. > > -Boris Thanks for the reminder to upload the other images.... here they are in their verbose glory: http://s303.photobucket.com/albums/nn159/yaneurabeya/?action=view¤t=IMG_0033.jpg http://s303.photobucket.com/albums/nn159/yaneurabeya/?action=view¤t=IMG_0034.jpg And the interesting sections of my rc.conf: ifconfig_msk0="DHCP" defaultrouter="192.168.10.1" hostname="orangebox.gateway.2wire.net" nfs_client_enable="YES" ntpdate_enable="YES" ntpdate_flags="ntp.ucsd.edu" rpcbind_enable="YES" synchronous_dhclient="YES" So the issue is again not with my interface, but the fact that registering dhcp sucks with my router (it's a lame 2wire hunk of AT&T junk), and it takes a while to register properly (5~10 seconds), and by the time the NFS mount line is reached, it's only been 2~3 seconds... I realize the motivation for not having runlevels like Linux, but there should something such that mounting NFS filesystems doesn't cause rc to start from scratch because it's entirely unnecessary and it breaks a lot of assumptions with rc... HTH, -Garrett From thompsa at FreeBSD.org Sun Mar 1 21:39:22 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Mar 1 21:39:34 2009 Subject: ums no longer loads on CURRENT In-Reply-To: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> References: <49AB4649.40906@freebsd.org> <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> Message-ID: <20090302053916.GF66136@citylink.fud.org.nz> On Sun, Mar 01, 2009 at 07:20:03PM -0800, Garrett Cooper wrote: > On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: > >> Garrett Cooper wrote: >>> device ums # Mouse >> >> This is why you cannot kldload. Not sure about any functional regression. >> >> Sam > > Yeah, well that message was printed out by another process altogether > while loading up the kernel after the ata subsystem was brought up, so > something's getting confused and trying to kldload by accident... I was > just reproducing the message. > I'll provide more data to prove this claim when I can. The warning should be gone in r189275 (tested locally). Andrew From spawk at acm.poly.edu Sun Mar 1 21:46:38 2009 From: spawk at acm.poly.edu (Boris Kochergin) Date: Sun Mar 1 21:46:51 2009 Subject: The rc.d mess strikes back In-Reply-To: <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com> References: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> <20090301.205017.1025328203.imp@bsdimp.com> <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com> Message-ID: <49AB6C1E.1030808@acm.poly.edu> Garrett Cooper wrote: > On Mar 1, 2009, at 7:50 PM, M. Warner Losh wrote: > >> In message: >> Garrett Cooper writes: >> : On Mar 1, 2009, at 7:36 PM, Garrett Cooper wrote: >> : >> : > On Mar 1, 2009, at 7:20 PM, Garrett Cooper wrote: >> : > >> : >> On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: >> : >> >> : >>> Garrett Cooper wrote: >> : >>>> device ums # Mouse >> : >>> >> : >>> This is why you cannot kldload. Not sure about any functional >> : >>> regression. >> : >>> >> : >>> Sam >> : >> >> : >> Yeah, well that message was printed out by another process >> : >> altogether while loading up the kernel after the ata subsystem was >> : >> brought up, so something's getting confused and trying to kldload >> : >> by accident... I was just reproducing the message. >> : >> I'll provide more data to prove this claim when I can. >> : >> Thanks, >> : >> -Garrett >> : > >> : > Here's the picture from my iPhone: >> > >> : > >. I OBVIOUSLY didn't do the kldload... and because my /boot/ >> : > loader.conf doesn't contain ums_load="YES", I'm really curious who >> : > the actual culprit is in rc.d land... >> : > I used to do WITHOUT_MODULES=* to not build modules, but I'm >> trying >> : > to move away from that mentality for some things like snd_emu10kx, >> : > but obviously there's a conflict somewhere for ums; hopefully it's >> : > merely cosmetic... >> : > Thanks, >> : > -Garrett >> : >> : Ok, found the culprit. It turns out moused is being called from >> : devd... this is all probably related to the startup mess I reported 2 >> : weeks ago with my NIC. I'm seeing a lot of additional problems in >> : terms of keeping track of daemons; for instance syslogd is getting >> : started up twice, but the first instance isn't recording a PID and the >> : second one is dying because the first one is bound to the address. >> : Agh... >> >> I didn't think that moused loaded anything. >> >> And what do extra nics have to do with this? I think you are >> confusing multiple problems... >> >> : Could we just unwind this rc.d mess? It seems to be causing issues >> : and wasn't very thoroughly tested before commit. >> >> This is a little to vague to be actionable. Do you have specific >> instances? Do you have rcorder output? Etc... >> >> Warner > > For whatever reason the NFS filemounts not coming up forces rc.d > to restart from a square one (because it enters maintenance mode), > which nukes PID files in /var/run (I'm assuming) via the cleanvar > service, and causes devd and syslogd to be started twice, which in > turn causes that message to be printed out on the console. devd's rc > script is just smart enough to recognize that there's a PID already > running on the system, and thus it doesn't try to start more than > once, but syslogd's is braindead (is there really a point to running > multiple instances of syslogd?) and thus it tries to start up the > service twice. > I'm understand why devd attempts to probe and install ums in the > kernel's namespace if it already exists... but I'm unhappy with the > fact that even though I set moused_enable=NO in rc.conf, moused still > doesn't honor that option ;(... > -Garrett > _______________________________________________ > 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" With regard to NFS breaking your boot process, I have run into the same thing recently, but it was my fault. Your screenshot omits the potentially-interesting information, if the problem is the same. In my case, /etc/rc.d/* was out of sync with /etc/network.subr. /etc/rc.d/netif, which handles the ifconfig_* lines in rc.conf, has references to an ifn_start() function in /etc/network.subr, so interfaces configured in rc.conf never came up. -Boris From man at email.com.ua Mon Mar 2 00:42:40 2009 From: man at email.com.ua (Artyom Mirgorodsky) Date: Mon Mar 2 00:42:46 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903012001.21543.hselasky@c2i.net> References: <200903010045.44904.man@email.com.ua> <200903012011.03358.man@email.com.ua> <200903012001.21543.hselasky@c2i.net> Message-ID: <200903021042.36967.man@email.com.ua> This flash drive works fine on another system (Intel 6300ESB USB 2.0 controller) with FreeBSD-8-current. May be problem in controller? From bugmaster at FreeBSD.org Mon Mar 2 03:07:45 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Mar 2 03:12:45 2009 Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org Message-ID: <200903021107.n22B71OD057480@freefall.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/132080 usb [patch] [usb] Kernel panic after NOMEM caused by rum 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/131912 usb [uslcom] [patch] New devices using Silicon Labs chips o usb/131900 usb Additional product identification code for Logitech Qu 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 f usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk 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/130325 usb [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh 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 [newusb] DVD drive detects as 'da' device o usb/129964 usb [newusb] disconnection of ugen devices isn't logged o bin/129963 usb [newusb] usbconfig(8) fails with misleading error when o docs/129962 usb [newusb] usbconfig(8) refers to non-existant usb2_core o usb/129945 usb [usbdevs] [patch] add u3g support for Longcheer WM66 U o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [patch] add support for ZTE AC8700 modem o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [patch] Liebert UPS being assigned uhid and o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb] [patch] uaudio is not full duplex o 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 f usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup o usb/127549 usb [umass] [patch] Meizu MiniPlayer M6 (SL) requires some s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127423 usb [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr o usb/127342 usb [boot] cannot enable usb keyboard and mouse support in o kern/127222 usb [ohci]: Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c f 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/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if 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/125264 usb [patch] sysctl for set usb mouse rate (very useful for 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/125072 usb [uplcom] [patch] add Mobile Action MA-620 Infrared Ada 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 o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work 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/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 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/122621 usb [patch] [request] New driver for Sierra Wireless 3G US 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/122025 usb [uscanner] [patch] uscanner does not attach to Epson R 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/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] FreeBSD fails to boot with usb legacy support e 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 [umass] [patch] quirk to support ASUS P535 as umass (a 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/120017 usb [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk o usb/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab 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/118686 usb [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround 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 [uaudio] [patch] Not possible to record with Plantroni 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/117185 usb [umodem] [patch] Add support for UNION interface descr o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a o 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 [umass] [patch] Problems with connection of the umass o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113977 usb [request] Need a way to set mode of USB disk's write c o usb/113672 usb [ehci] [panic] Kernel panic with AEWIN CB6971 s usb/113629 usb [ukbd] Dropped USB keyboard events on Dell Latitude D6 o usb/113432 usb [ucom] WARNING: attempt to net_add_domain(netgraph) af a usb/113060 usb [usbdevs] [patch] Samsung printer not working in bidir o usb/112944 usb [ulpt] [patch] Bi-directional access to HP LaserJet 10 o usb/112640 usb [usb] [hang] Kernel freezes when writing a file to an o usb/112631 usb [panic] Problem with SONY DSC-S80 camera on umount s usb/112568 usb [umass] [request] USB mode may wrong when mounting Pla o usb/112463 usb [umass] problem with Samsung USB DVD writer, libscg an o usb/112461 usb [ehci] [request] ehci USB 2.0 doesn't work on nforce4 o usb/111753 usb [uhid] [panic] Replicable system panic involving UHID s usb/110991 usb [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends o usb/110988 usb [umass] [patch] Handling of quirk IGNORE_RESIDUE is um o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC o usb/109397 usb [panic] on boot from USB flash o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr s usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/108056 usb [ohci] Mouse gets powered off during device probe when o usb/107935 usb [uplcom] [panic] panic while accessing /dev/cuaU0 o usb/107924 usb [patch] usbd(8) does not call detach o usb/107848 usb [umass] [request] cannot access Samsung flash disk o usb/107827 usb [ohci] [panic] ohci_add_done addr not found o usb/107496 usb [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [ o usb/107388 usb [patch] [request] new driver: add utoppy device from N o usb/107248 usb [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP o usb/107243 usb [cam] [patch] Apacer USB Flash Drive quirk o usb/106861 usb [usbdevs] [patch]: usbdevs update: Add product ACER Ze s usb/106832 usb [usb] USB HP printer is not detected by kernel when AC o usb/106648 usb [umass] [hang] USB Floppy on D1950 10 min Hang on Inse o usb/106621 usb [axe] [patch] DLINK DUB-E100 support broken o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106041 usb [usb] [request] FreeBSD does not recognise Mustek Bear o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/105186 usb [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c o usb/105065 usb [ata] [usb] SATA - USB Bridge o usb/104830 usb [umass] system crashes when copying data to umass devi o usb/104645 usb [umass] [request] Rave C-201 MP3 player does not commu o usb/104352 usb [ural] [patch] ural driver doesnt work o usb/104292 usb [umass] [hang] system lockup on forced umount of usb-s o usb/104290 usb [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto o usb/103917 usb [uhub] USB driver reports "Addr 0 should never happen" o usb/103418 usb usbhidctl(1): [patch] [request] usbhidctl: add ability o usb/103289 usb [request] USB 2.0 problems on AMD LX-800 CPU and CS-55 o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103025 usb [uhub] [panic] wrong detection of USB device for FreeB o usb/102976 usb [panic] Casio Exilim Digital Camera causes panic on in o usb/102678 usb [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/101761 usb [usb] [patch] [request] usb.h: increase maximal size o o usb/101752 usb [umass] [panic] 6.1-RELEASE kernel panic on usb device o usb/101448 usb [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O o usb/101096 usb [ural] [panic] USB WLAN occasionally causes kernel-pan o usb/100746 usb [keyboard] system does not boot due to USB keyboard pr o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar 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/93408 usb [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w 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 o 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/91629 usb [usb] usbd_abort_pipe() may result in infinite loop 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 f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US 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 f usb/83677 usb [usb] [request] usb controller often not detected (Sun 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/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu 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 " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, 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 o 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 o usb/75797 usb [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o 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 i386/46371 usb USB controller cannot be initialized on IBM Netfinity 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 305 problems total. From mmakonnen at gmail.com Mon Mar 2 04:41:48 2009 From: mmakonnen at gmail.com (Mike Makonnen) Date: Mon Mar 2 04:41:57 2009 Subject: The rc.d mess strikes back In-Reply-To: <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com> References: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> <20090301.205017.1025328203.imp@bsdimp.com> <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com> Message-ID: <49ABCECE.1040102@gmail.com> Garrett Cooper wrote: >> : Could we just unwind this rc.d mess? It seems to be causing issues >> : and wasn't very thoroughly tested before commit. >> This is not an option because the previous behavior caused an unconditional 30 sec. delay if the system wasn't plugged in (or if it is plugged in but not on a DHCP network). I think making synchronous_dhclient default to YES is the best option. Cheers. -- Mike Makonnen | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc mtm @ FreeBSD.Org | AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 FreeBSD | http://www.freebsd.org From astrodog at gmail.com Mon Mar 2 05:44:10 2009 From: astrodog at gmail.com (Astrodog) Date: Mon Mar 2 05:44:17 2009 Subject: The rc.d mess strikes back In-Reply-To: <49ABCECE.1040102@gmail.com> References: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> <20090301.205017.1025328203.imp@bsdimp.com> <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com> <49ABCECE.1040102@gmail.com> Message-ID: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> As unfortunate (and annoying) as that delay was, your system was in a "defined" state, at the end of rc.d. As things stand now, that doesn't appear to be the case anymore, and I think that may be a more significant issue than the delay. --- Harrison On Mon, Mar 2, 2009 at 6:19 AM, Mike Makonnen wrote: > Garrett Cooper wrote: >>> >>> : ? ? Could we just unwind this rc.d mess? It seems to be causing issues >>> : and wasn't very thoroughly tested before commit. >>> > > This is not an option because the previous behavior caused an unconditional > 30 sec. delay if the system wasn't plugged in (or if it is plugged in but > not on a DHCP network). ?I think making synchronous_dhclient default to YES > is the best option. > > Cheers. > -- > Mike Makonnen ? ? ? | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc > mtm @ FreeBSD.Org ? | AC7B 5672 2D11 F4D0 EBF8 ?5279 5359 2B82 7CD4 1F55 > FreeBSD ? ? ? ? ? ? | http://www.freebsd.org > _______________________________________________ > 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" > -- "A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects." --- Robert A. Heinlein From imp at bsdimp.com Mon Mar 2 12:28:09 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Mar 2 12:28:16 2009 Subject: The rc.d mess strikes back In-Reply-To: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> References: <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com> <49ABCECE.1040102@gmail.com> <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> Message-ID: <20090302.132522.-432836388.imp@bsdimp.com> In message: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> Astrodog writes: : As unfortunate (and annoying) as that delay was, your system was in a : "defined" state, at the end of rc.d. As things stand now, that doesn't : appear to be the case anymore, and I think that may be a more : significant issue than the delay. I'd be happy with synchronous dhcp. Warner : --- Harrison : : On Mon, Mar 2, 2009 at 6:19 AM, Mike Makonnen wrote: : > Garrett Cooper wrote: : >>> : >>> : ? ? Could we just unwind this rc.d mess? It seems to be causing issues : >>> : and wasn't very thoroughly tested before commit. : >>> : > : > This is not an option because the previous behavior caused an unconditional : > 30 sec. delay if the system wasn't plugged in (or if it is plugged in but : > not on a DHCP network). ?I think making synchronous_dhclient default to YES : > is the best option. : > : > Cheers. : > -- : > Mike Makonnen ? ? ? | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc : > mtm @ FreeBSD.Org ? | AC7B 5672 2D11 F4D0 EBF8 ?5279 5359 2B82 7CD4 1F55 : > FreeBSD ? ? ? ? ? ? | http://www.freebsd.org : > _______________________________________________ : > 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" : > : : : : -- : "A human being should be able to change a diaper, plan an invasion, : butcher a hog, conn a ship, design a building, write a sonnet, balance : accounts, build a wall, set a bone, comfort the dying, take orders, : give orders, cooperate, act alone, solve equations, analyze a new : problem, pitch manure, program a computer, cook a tasty meal, fight : efficiently, die gallantly. Specialization is for insects." : --- Robert A. Heinlein : : From rene at freebsd.org Mon Mar 2 13:09:47 2009 From: rene at freebsd.org (Rene Ladan) Date: Mon Mar 2 13:10:17 2009 Subject: ports/132246: [PATCH] Make devel/libusb play nice with new usb2 Message-ID: This patch fixes USB access on FreeBSD >= 800063 by including legacy/dev/usb/usb.h instead of dev/usb/usb.h on those systems; however, is the legacy directory going to stay in 8.0-RELEASE and onwards? If not, this patch is invalid and another solution must be sought. From man at email.com.ua Mon Mar 2 13:17:10 2009 From: man at email.com.ua (Artyom Mirgorodsky) Date: Mon Mar 2 13:17:16 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903012001.21543.hselasky@c2i.net> References: <200903010045.44904.man@email.com.ua> <200903012011.03358.man@email.com.ua> <200903012001.21543.hselasky@c2i.net> Message-ID: <200903022320.31592.man@email.com.ua> > It might be a bug with your memory stick. Are your findings consistent accross > other brands of memory sticks aswell, between 7.1 and 8.x ? Today, I tested another flash drive ugen1.2: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:3:0:-1: Attached to scbus3 sg1 at umass-sim0 bus 0 target 0 lun 0 sg1: Removable Direct Access SCSI-2 device sg1: 40.000MB/s transfers pass1 at umass-sim0 bus 0 target 0 lun 0 pass1: Removable Direct Access SCSI-2 device pass1: 40.000MB/s transfers GEOM: new disk da0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 3872MB (7929856 512 byte sectors: 255H 63S/T 493C) FreeBSD-8-Current dd if=/dev/da0 of=/dev/null bs=64k count=10000 10000+0 records in 10000+0 records out 655360000 bytes transferred in 60.320972 secs (10864546 bytes/sec) systat -vm Disks ad4 ad6 da0 cd0 pass0 sg0 sg1 68560 wire KB/t 0.00 0.00 64.00 0.00 0.00 0.00 0.00 117684 act tps 0 0 166 0 0 0 0 75468 inact MB/s 0.00 0.00 10.40 0.00 0.00 0.00 0.00 1860 cache %busy 0 0 99 0 0 0 0 1136340 free FreeBSD-7.1 dd if=/dev/da0 of=/dev/null bs=64k count=10000 10000+0 records in 10000+0 records out 655360000 bytes transferred in 44.021160 secs (14887386 bytes/sec) systat -vm Disks ad4 ad6 da0 KB/t 0.00 0.00 64.00 tps 0 0 228 MB/s 0.00 0.00 14.22 %busy 0 0 99 From imp at bsdimp.com Mon Mar 2 17:16:07 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Mar 2 17:16:13 2009 Subject: The rc.d mess strikes back In-Reply-To: <20090302233215.GA53763@duncan.reilly.home> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> Message-ID: <20090302.181513.1973603215.imp@bsdimp.com> In message: <20090302233215.GA53763@duncan.reilly.home> Andrew Reilly writes: : On Mon, Mar 02, 2009 at 01:25:22PM -0700, M. Warner Losh wrote: : > In message: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> : > Astrodog writes: : > : As unfortunate (and annoying) as that delay was, your system was in a : > : "defined" state, at the end of rc.d. As things stand now, that doesn't : > : appear to be the case anymore, and I think that may be a more : > : significant issue than the delay. : > : > I'd be happy with synchronous dhcp. : : The more general problem is the (large) number of network : applications that assume that network addresses and routes never : change (because that's how things were when they were written.) : My personal pet peeve is ntpd, but there are many others. Any : daemon that caches host IP address information at startup is : (IMO) broken, and needs to be fixed. There are many reasons why : network addresses may change *after* startup, and it is not : reasonable to go around and manually HUP everything when that : happens. True. : Needing synchronous DHCP as a work-around here is just the : signifier of the problem: it isn't the over-all solution. It is a short-term work-around at best. Warner From andrew-freebsd at areilly.bpc-users.org Mon Mar 2 17:42:37 2009 From: andrew-freebsd at areilly.bpc-users.org (Andrew Reilly) Date: Mon Mar 2 17:42:48 2009 Subject: The rc.d mess strikes back In-Reply-To: <20090302.132522.-432836388.imp@bsdimp.com> References: <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com> <49ABCECE.1040102@gmail.com> <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> Message-ID: <20090302233215.GA53763@duncan.reilly.home> On Mon, Mar 02, 2009 at 01:25:22PM -0700, M. Warner Losh wrote: > In message: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> > Astrodog writes: > : As unfortunate (and annoying) as that delay was, your system was in a > : "defined" state, at the end of rc.d. As things stand now, that doesn't > : appear to be the case anymore, and I think that may be a more > : significant issue than the delay. > > I'd be happy with synchronous dhcp. The more general problem is the (large) number of network applications that assume that network addresses and routes never change (because that's how things were when they were written.) My personal pet peeve is ntpd, but there are many others. Any daemon that caches host IP address information at startup is (IMO) broken, and needs to be fixed. There are many reasons why network addresses may change *after* startup, and it is not reasonable to go around and manually HUP everything when that happens. Needing synchronous DHCP as a work-around here is just the signifier of the problem: it isn't the over-all solution. Cheers, -- Andrew From hselasky at c2i.net Mon Mar 2 23:47:34 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Mar 2 23:47:40 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903022320.31592.man@email.com.ua> References: <200903010045.44904.man@email.com.ua> <200903012001.21543.hselasky@c2i.net> <200903022320.31592.man@email.com.ua> Message-ID: <200903030850.01866.hselasky@c2i.net> On Monday 02 March 2009, Artyom Mirgorodsky wrote: > > It might be a bug with your memory stick. Are your findings consistent > > accross other brands of memory sticks aswell, between 7.1 and 8.x ? > > Today, I tested another flash drive > > ugen1.2: at usbus1 > umass0: on usbus1 > umass0: SCSI over Bulk-Only; quirks = 0x0000 > umass0:3:0:-1: Attached to scbus3 > sg1 at umass-sim0 bus 0 target 0 lun 0 > sg1: Removable Direct Access SCSI-2 device > sg1: 40.000MB/s transfers > pass1 at umass-sim0 bus 0 target 0 lun 0 > pass1: Removable Direct Access SCSI-2 device > pass1: 40.000MB/s transfers > GEOM: new disk da0 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-2 device > da0: 40.000MB/s transfers > da0: 3872MB (7929856 512 byte sectors: 255H 63S/T 493C) > > > > FreeBSD-8-Current > > dd if=/dev/da0 of=/dev/null bs=64k count=10000 > 10000+0 records in > 10000+0 records out > 655360000 bytes transferred in 60.320972 secs (10864546 bytes/sec) > > systat -vm > > Disks ad4 ad6 da0 cd0 pass0 sg0 sg1 68560 wire > KB/t 0.00 0.00 64.00 0.00 0.00 0.00 0.00 117684 act > tps 0 0 166 0 0 0 0 75468 inact > MB/s 0.00 0.00 10.40 0.00 0.00 0.00 0.00 1860 cache > %busy 0 0 99 0 0 0 0 1136340 free > > > > FreeBSD-7.1 > > dd if=/dev/da0 of=/dev/null bs=64k count=10000 > 10000+0 records in > 10000+0 records out > 655360000 bytes transferred in 44.021160 secs (14887386 bytes/sec) Hi, What brand is your CPU. I know that certain AMD USB controllers perform less with the new USB stack, but I've not been able to track down the issue. Can you try another PC having another CPU brand? There might be some minor things that needs tuning like the NAK retry counter. I suspect you have run into a timing issue with the hardware. --HPS From man at email.com.ua Tue Mar 3 01:30:38 2009 From: man at email.com.ua (Artyom Mirgorodsky) Date: Tue Mar 3 01:30:45 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903030850.01866.hselasky@c2i.net> References: <200903010045.44904.man@email.com.ua> <200903022320.31592.man@email.com.ua> <200903030850.01866.hselasky@c2i.net> Message-ID: <200903031130.35613.man@email.com.ua> >I know that certain AMD USB controllers perform less with the new USB stack, >but I've not been able to track down the issue. Yes, I have AMD platform (motherboard ASUS A8N-VM-CSM) >Can you try another PC having another CPU brand? Yes, I have already posted the result - 22 Mb/sec, much better than on my computer. >There might be some minor things that needs tuning like the NAK retry counter. >I suspect you have run into a timing issue with the hardware. Can I do anything to solve this problem or at least help you to track it down? From hselasky at c2i.net Tue Mar 3 06:13:33 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Mar 3 06:13:40 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903031130.35613.man@email.com.ua> References: <200903010045.44904.man@email.com.ua> <200903030850.01866.hselasky@c2i.net> <200903031130.35613.man@email.com.ua> Message-ID: <200903031516.02744.hselasky@c2i.net> On Tuesday 03 March 2009, Artyom Mirgorodsky wrote: > >I know that certain AMD USB controllers perform less with the new USB > > stack, but I've not been able to track down the issue. > > Yes, I have AMD platform (motherboard ASUS A8N-VM-CSM) > > >Can you try another PC having another CPU brand? > > Yes, I have already posted the result - 22 Mb/sec, much better than on my > computer. > > >There might be some minor things that needs tuning like the NAK retry > > counter. I suspect you have run into a timing issue with the hardware. > > Can I do anything to solve this problem or at least help you to track it > down? Edit: src/sys/dev/usb/controller/ehci.c if (usb2_get_speed(xfer->xroot->udev) == USB_SPEED_HIGH) { qh_endp |= (EHCI_QH_SET_EPS(EHCI_QH_SPEED_HIGH) | EHCI_QH_DTC); if (methods != &ehci_device_intr_methods) qh_endp |= EHCI_QH_SET_NRL(8); } else { And tune to NRL value to 15. Recompile kernel and modules. --HPS From mmakonnen at gmail.com Tue Mar 3 08:33:42 2009 From: mmakonnen at gmail.com (Mike Telahun Makonnen) Date: Tue Mar 3 08:33:54 2009 Subject: The rc.d mess strikes back In-Reply-To: <20090302.181513.1973603215.imp@bsdimp.com> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> <20090302.181513.1973603215.imp@bsdimp.com> Message-ID: <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> On Tue, Mar 3, 2009 at 4:15 AM, M. Warner Losh wrote: > In message: <20090302233215.GA53763@duncan.reilly.home> > ? ? ? ? ? ?Andrew Reilly writes: > : On Mon, Mar 02, 2009 at 01:25:22PM -0700, M. Warner Losh wrote: > : > In message: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> > : > ? ? ? ? ? ? Astrodog writes: > : > : As unfortunate (and annoying) as that delay was, your system was in a > : > : "defined" state, at the end of rc.d. As things stand now, that doesn't > : > : appear to be the case anymore, and I think that may be a more > : > : significant issue than the delay. > : > > : > I'd be happy with synchronous dhcp. Ok. I've been waiting to see if brooks@ was going to weigh in on this, but I'll go ahead and make the change now and see if there is any more fall-out. Once that's done, network behaviour should be more or less the same as before my change, with the exception that any DHCP interfaces that aren't plugged in may delay the boot by more than 30sec. [snip] > > : Needing synchronous DHCP as a work-around here is just the > : signifier of the problem: it isn't the over-all solution. > > It is a short-term work-around at best. >From the problems that have been reported so far it seems to me the problem is with some drivers that repeatedly bring the network link up and down. The *ideal* solution seems (to me) to be to fix these drivers. Am I wrong? Cheers. Mike. From man at email.com.ua Tue Mar 3 10:18:19 2009 From: man at email.com.ua (Artyom Mirgorodsky) Date: Tue Mar 3 10:18:27 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903031516.02744.hselasky@c2i.net> References: <200903010045.44904.man@email.com.ua> <200903031130.35613.man@email.com.ua> <200903031516.02744.hselasky@c2i.net> Message-ID: <200903032006.54451.man@email.com.ua> On Tuesday 03 March 2009 16:16:02 Hans Petter Selasky wrote: > if (usb2_get_speed(xfer->xroot->udev) == USB_SPEED_HIGH) { > qh_endp |= (EHCI_QH_SET_EPS(EHCI_QH_SPEED_HIGH) | > EHCI_QH_DTC); > if (methods != &ehci_device_intr_methods) > qh_endp |= EHCI_QH_SET_NRL(8); > } else { > > And tune to NRL value to 15. Recompile kernel and modules. Nothing changed dd if=/dev/da0 of=/dev/null bs=64k 5433+0 records in 5433+0 records out 356057088 bytes transferred in 27.286939 secs (13048627 bytes/sec) From brooks at freebsd.org Tue Mar 3 10:25:23 2009 From: brooks at freebsd.org (Brooks Davis) Date: Tue Mar 3 10:25:29 2009 Subject: The rc.d mess strikes back In-Reply-To: <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> <20090302.181513.1973603215.imp@bsdimp.com> <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> Message-ID: <20090303180307.GA11134@lor.one-eyed-alien.net> On Tue, Mar 03, 2009 at 07:33:39PM +0300, Mike Telahun Makonnen wrote: > On Tue, Mar 3, 2009 at 4:15 AM, M. Warner Losh wrote: > > In message: <20090302233215.GA53763@duncan.reilly.home> > > ? ? ? ? ? ?Andrew Reilly writes: > > : On Mon, Mar 02, 2009 at 01:25:22PM -0700, M. Warner Losh wrote: > > : > In message: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> > > : > ? ? ? ? ? ? Astrodog writes: > > : > : As unfortunate (and annoying) as that delay was, your system was in a > > : > : "defined" state, at the end of rc.d. As things stand now, that doesn't > > : > : appear to be the case anymore, and I think that may be a more > > : > : significant issue than the delay. > > : > > > : > I'd be happy with synchronous dhcp. > > Ok. I've been waiting to see if brooks@ was going to weigh in on this, > but I'll go ahead and make the change now and see if there is any more > fall-out. Once that's done, network behaviour should be more or less > the same as before my change, with the exception that any DHCP > interfaces that aren't plugged in may delay the boot by more than > 30sec. I don't have much time to debug this, but I've not had problems with services starting too early on the systems I've been running with async dhcp. If there is a problem with the wait process we need to actually debug it. If the wait for a route/running interface isn't sufficent we should try to figure out what is. Synchronous dhcp sucks and yeilds justifed user complaints so it would be nice to kill it off. I switched the default because it worked for me and I hoped that people would help find and fix edge cases. BTW, the change to background by default still doesn't make sense to me. At best it shouldn't do anything useful in the async case and it entierly defeats the sync case. > [snip] > > > > : Needing synchronous DHCP as a work-around here is just the > > : signifier of the problem: it isn't the over-all solution. > > > > It is a short-term work-around at best. > > >From the problems that have been reported so far it seems to me the > problem is with some drivers that repeatedly bring the network link up > and down. The *ideal* solution seems (to me) to be to fix these > drivers. Am I wrong? This needs to be the solution in the end. -- Brooks -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090303/fa159bb9/attachment.pgp From hselasky at c2i.net Tue Mar 3 13:41:08 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Mar 3 13:41:14 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903032006.54451.man@email.com.ua> References: <200903010045.44904.man@email.com.ua> <200903031516.02744.hselasky@c2i.net> <200903032006.54451.man@email.com.ua> Message-ID: <200903032243.31914.hselasky@c2i.net> On Tuesday 03 March 2009, Artyom Mirgorodsky wrote: > On Tuesday 03 March 2009 16:16:02 Hans Petter Selasky wrote: > > if (usb2_get_speed(xfer->xroot->udev) == USB_SPEED_HIGH) { > > qh_endp |= (EHCI_QH_SET_EPS(EHCI_QH_SPEED_HIGH) | > > EHCI_QH_DTC); > > if (methods != &ehci_device_intr_methods) > > qh_endp |= EHCI_QH_SET_NRL(8); > > } else { > > > > And tune to NRL value to 15. Recompile kernel and modules. > Hi, Here is some more testing you can do: dd if=/dev/da0 of=/dev/null bs=1024 & And then: vmstat -i ; sleep 1 ; vmstat -i Now compute the number of interrupts that appear on the EHCI. Repeat the same test using FreeBSD -current. a) On the machine where it is slow. b) On the machine where it is fast. I think the reduced performance can be explained by a clamp on the interrupt rate around 1000 interrupts per second instead of 8000. Maybe someone has an explanation for this? The EHCI is being programmed to interrupt at 125us intervals, but there seems to be limits other places. It is possible to workaround this in the umass driver by doing the cmd + read in one operation. --HPS From stevecalfee at gmail.com Tue Mar 3 14:15:44 2009 From: stevecalfee at gmail.com (Steve Calfee) Date: Tue Mar 3 14:15:51 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903032243.31914.hselasky@c2i.net> References: <200903010045.44904.man@email.com.ua> <200903031516.02744.hselasky@c2i.net> <200903032006.54451.man@email.com.ua> <200903032243.31914.hselasky@c2i.net> Message-ID: <4a5ff6bc0903031415s16158407m386b8321a5082996@mail.gmail.com> > I think the reduced performance can be explained by a clamp on the interrupt > rate around 1000 interrupts per second instead of 8000. Maybe someone has an > explanation for this? > > The EHCI is being programmed to interrupt at 125us intervals, but there seems > to be limits other places. > > It is possible to workaround this in the umass driver by doing the cmd + read > in one operation. Hi Hans, I am looking at using FreeBSD in an embedded product. I have not examined your ehci software, but I am aware of how Linux and other OSes run the controller. Why are you taking an interrupt every uFrame SOF? What can you possibly do then? You are not in a RTOS, you are not guaranteed to even get that fast an interrupt. The whole point of the magic ehci DMA engine is that many transactions can be programmed and then they can interrupt when they are done. The Periodic list is set up with (hopefully) enough transactions that the OS can keep up, and async doesn't care at all - the only impact is possible xfer speed. Taking really fast periodic (uFrame) interrupts guarantees no faster transfers than just having the end of transfer interrupt. Just wondering. Regards, Steve From dfilter at FreeBSD.ORG Tue Mar 3 19:50:03 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Tue Mar 3 19:50:09 2009 Subject: usb/125072: commit references a PR Message-ID: <200903040350.n243o2ob031105@freefall.freebsd.org> The following reply was made to PR usb/125072; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/125072: commit references a PR Date: Wed, 4 Mar 2009 03:48:11 +0000 (UTC) Author: thompsa Date: Wed Mar 4 03:47:57 2009 New Revision: 189360 URL: http://svn.freebsd.org/changeset/base/189360 Log: Add Mobile Action MA-620 Infrared Adapter. PR: usb/125072 Submitted by: Alexander Logvinov MFC after: 1 week Modified: head/share/man/man4/uplcom.4 head/sys/dev/usb/serial/uplcom.c head/sys/dev/usb/usbdevs Modified: head/share/man/man4/uplcom.4 ============================================================================== --- head/share/man/man4/uplcom.4 Wed Mar 4 03:45:34 2009 (r189359) +++ head/share/man/man4/uplcom.4 Wed Mar 4 03:47:57 2009 (r189360) @@ -98,6 +98,8 @@ I/O DATA USB-RSAQ2 .It I/O DATA USB-RSAQ3 .It +Mobile Action MA-620 Infrared Adapter +.It PLANEX USB-RS232 URS-03 .It RATOC REX-USB60 Modified: head/sys/dev/usb/serial/uplcom.c ============================================================================== --- head/sys/dev/usb/serial/uplcom.c Wed Mar 4 03:45:34 2009 (r189359) +++ head/sys/dev/usb/serial/uplcom.c Wed Mar 4 03:47:57 2009 (r189360) @@ -274,6 +274,9 @@ static const struct usb2_device_id uplco {USB_UPL(USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PHAROS, 0, 0xFFFF, TYPE_PL2303)}, /* Willcom W-SIM */ {USB_UPL(USB_VENDOR_PROLIFIC2, USB_PRODUCT_PROLIFIC2_WSIM, 0, 0xFFFF, TYPE_PL2303X)}, + /* Mobile Action MA-620 Infrared Adapter */ + {USB_UPL(USB_VENDOR_MOBILEACTION, USB_PRODUCT_MOBILEACTION_MA620, 0, 0xFFFF, TYPE_PL2303X)}, + }; static device_method_t uplcom_methods[] = { Modified: head/sys/dev/usb/usbdevs ============================================================================== --- head/sys/dev/usb/usbdevs Wed Mar 4 03:45:34 2009 (r189359) +++ head/sys/dev/usb/usbdevs Wed Mar 4 03:47:57 2009 (r189360) @@ -1767,6 +1767,9 @@ product MITSUMI CDRRW 0x0000 CD-R/RW Dr product MITSUMI BT_DONGLE 0x641f Bluetooth USB dongle product MITSUMI FDD 0x6901 USB FDD +/* Mobile Action products */ +product MOBILEACTION MA620 0x0620 MA-620 Infrared Adapter + /* Mobility products */ product MOBILITY EA 0x0204 Ethernet product MOBILITY EASIDOCK 0x0304 EasiDock Ethernet _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From mmakonnen at gmail.com Tue Mar 3 22:12:51 2009 From: mmakonnen at gmail.com (Mike Telahun Makonnen) Date: Tue Mar 3 22:13:04 2009 Subject: The rc.d mess strikes back In-Reply-To: <20090303180307.GA11134@lor.one-eyed-alien.net> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> <20090302.181513.1973603215.imp@bsdimp.com> <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> <20090303180307.GA11134@lor.one-eyed-alien.net> Message-ID: <584bfc3f0903032212x25831c5bi35d9b637c1896e1d@mail.gmail.com> On Tue, Mar 3, 2009 at 9:03 PM, Brooks Davis wrote: > > I don't have much time to debug this, but I've not had problems with > services starting too early on the systems I've been running with async > dhcp. ?If there is a problem with the wait process we need to actually > debug it. ?If the wait for a route/running interface isn't sufficent we > should try to figure out what is. ?Synchronous dhcp sucks and yeilds > justifed user complaints so it would be nice to kill it off. ?I switched > the default because it worked for me and I hoped that people would help > find and fix edge cases. Can you elaborate why synchronous DHCP sucks ? > > BTW, the change to background by default still doesn't make sense to > me. ?At best it shouldn't do anything useful in the async case and it > entierly defeats the sync case. > Yeah, I realized this as soon as people started complaining about the changes and reverting that commit didn't fix their problem. I'll back it out. Cheers, Mike. From yanefbsd at gmail.com Wed Mar 4 00:04:08 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Wed Mar 4 00:04:20 2009 Subject: The rc.d mess strikes back In-Reply-To: <584bfc3f0903032212x25831c5bi35d9b637c1896e1d@mail.gmail.com> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> <20090302.181513.1973603215.imp@bsdimp.com> <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> <20090303180307.GA11134@lor.one-eyed-alien.net> <584bfc3f0903032212x25831c5bi35d9b637c1896e1d@mail.gmail.com> Message-ID: <7d6fde3d0903040004y1fcbb086i355cd0113717620b@mail.gmail.com> On Tue, Mar 3, 2009 at 10:12 PM, Mike Telahun Makonnen wrote: > On Tue, Mar 3, 2009 at 9:03 PM, Brooks Davis wrote: >> >> I don't have much time to debug this, but I've not had problems with >> services starting too early on the systems I've been running with async >> dhcp. ?If there is a problem with the wait process we need to actually >> debug it. ?If the wait for a route/running interface isn't sufficent we >> should try to figure out what is. ?Synchronous dhcp sucks and yeilds >> justifed user complaints so it would be nice to kill it off. ?I switched >> the default because it worked for me and I hoped that people would help >> find and fix edge cases. > > Can you elaborate why synchronous DHCP sucks ? The only reason I could see is bringup time. Am I correct in this assumption? >> >> BTW, the change to background by default still doesn't make sense to >> me. ?At best it shouldn't do anything useful in the async case and it >> entierly defeats the sync case. >> > > Yeah, I realized this as soon as people started complaining about the > changes and reverting that commit didn't fix their problem. I'll back > it out. Thanks :), -Garrett From yanefbsd at gmail.com Wed Mar 4 00:09:32 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Wed Mar 4 00:09:43 2009 Subject: The rc.d mess strikes back In-Reply-To: <20090302233215.GA53763@duncan.reilly.home> References: <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com> <49ABCECE.1040102@gmail.com> <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> Message-ID: <7d6fde3d0903040009y1b9d009chbacab05180630572@mail.gmail.com> On Mon, Mar 2, 2009 at 3:32 PM, Andrew Reilly wrote: > On Mon, Mar 02, 2009 at 01:25:22PM -0700, M. Warner Losh wrote: >> In message: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> >> ? ? ? ? ? ? Astrodog writes: >> : As unfortunate (and annoying) as that delay was, your system was in a >> : "defined" state, at the end of rc.d. As things stand now, that doesn't >> : appear to be the case anymore, and I think that may be a more >> : significant issue than the delay. >> >> I'd be happy with synchronous dhcp. > > The more general problem is the (large) number of network > applications that assume that network addresses and routes never > change (because that's how things were when they were written.) > My personal pet peeve is ntpd, but there are many others. ?Any > daemon that caches host IP address information at startup is > (IMO) broken, and needs to be fixed. ?There are many reasons why > network addresses may change *after* startup, and it is not > reasonable to go around and manually HUP everything when that > happens. > > Needing synchronous DHCP as a work-around here is just the > signifier of the problem: it isn't the over-all solution. I completely and wholeheartedly agree with you. This could be more difficult with contributed software, but it can be done! Thanks =], -Garrett From hselasky at c2i.net Wed Mar 4 00:20:19 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 4 00:20:26 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <4a5ff6bc0903031415s16158407m386b8321a5082996@mail.gmail.com> References: <200903010045.44904.man@email.com.ua> <200903032243.31914.hselasky@c2i.net> <4a5ff6bc0903031415s16158407m386b8321a5082996@mail.gmail.com> Message-ID: <200903040922.48163.hselasky@c2i.net> Hi Steve, On Tuesday 03 March 2009, Steve Calfee wrote: > > I think the reduced performance can be explained by a clamp on the > > interrupt rate around 1000 interrupts per second instead of 8000. Maybe > > someone has an explanation for this? > > > > The EHCI is being programmed to interrupt at 125us intervals, but there > > seems to be limits other places. > > > > It is possible to workaround this in the umass driver by doing the cmd + > > read in one operation. > > Hi Hans, > > I am looking at using FreeBSD in an embedded product. I have not > examined your ehci software, but I am aware of how Linux and other > OSes run the controller. > > Why are you taking an interrupt every uFrame SOF? If the transaction completes before 125us we take the interrupt before 125us. The problem is that the interrupt delay becomes critical to performance when the interrupt rate is close to the interrupt limitation. For example: Transferring 13Mbyte/sec at blocksize equal to 65536 bytes generates 600 interrupts. Hence the Mass Storage state machine has three steps the throughput is computed like (600/3)*65536 bytes. If we on the average have to wait 0.5ms for an interrupt we loose throughput. > async > doesn't care at all If you have to wait for a transaction before you can do the next one it matters. > - the only impact is possible xfer speed. Taking > really fast periodic (uFrame) interrupts guarantees no faster > transfers than just having the end of transfer interrupt. > --HPS From man at email.com.ua Wed Mar 4 00:28:40 2009 From: man at email.com.ua (Artyom Mirgorodsky) Date: Wed Mar 4 00:28:51 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903032243.31914.hselasky@c2i.net> References: <200903010045.44904.man@email.com.ua> <200903032006.54451.man@email.com.ua> <200903032243.31914.hselasky@c2i.net> Message-ID: <200903041028.37027.man@email.com.ua> >Repeat the same test using FreeBSD -current. >a) On the machine where it is slow. vmstat -i ; sleep 1 ; vmstat -i interrupt total rate irq1: atkbd0 233 2 irq14: ata0 85 0 irq16: vgapci0 5377 52 irq21: hdac0 ohci0 742 7 irq22: nfe0 ehci0 23610 229 irq23: atapci1 5405 52 cpu0: timer 203959 1980 cpu1: timer 200914 1950 Total 440325 4275 interrupt total rate irq1: atkbd0 234 2 irq14: ata0 85 0 irq16: vgapci0 5439 52 irq21: hdac0 ohci0 742 7 irq22: nfe0 ehci0 24621 236 irq23: atapci1 5405 51 cpu0: timer 205981 1980 cpu1: timer 202937 1951 Total 445444 4283 >I think the reduced performance can be explained by a clamp on the interrupt >rate around 1000 interrupts per second instead of 8000. Maybe someone has an >explanation for this? You right, the interrupt rate around 1000 (1011) on this machine, but on FreeBSD 7.1 more 3000. If it is some kind of interrupt aggregation, may be I can try to turn it off? >b) On the machine where it is fast. vmstat -i ; sleep 1 ; vmstat -i interrupt total rate irq4: uart0 4154 0 irq14: ata0 472922 0 irq15: ata1 26 0 irq18: em0 752711 0 irq21: ahc0 53 0 irq23: ehci0 103456 0 irq24: em1 147 0 cpu0: timer 1551216517 2000 cpu1: timer 1551195251 2000 Total 3103745237 4001 interrupt total rate irq4: uart0 4154 0 irq14: ata0 472923 0 irq15: ata1 26 0 irq18: em0 752713 0 irq21: ahc0 53 0 irq23: ehci0 110949 0 irq24: em1 147 0 cpu0: timer 1551218551 2000 cpu1: timer 1551197285 2000 Total 3103756801 4001 From hselasky at c2i.net Wed Mar 4 00:40:12 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 4 00:40:19 2009 Subject: Knobs to reduce PCI interrupt latency [was: Low perfomance when read from usb flash drive] In-Reply-To: <200903041028.37027.man@email.com.ua> References: <200903010045.44904.man@email.com.ua> <200903032243.31914.hselasky@c2i.net> <200903041028.37027.man@email.com.ua> Message-ID: <200903040942.39191.hselasky@c2i.net> Hi, Do we have any knobs in FreeBSD to reduce the interrupt latency? I am currently seeing performance differences between 8.x and 7.x. Anyone have any ideas? --HPS On Wednesday 04 March 2009, Artyom Mirgorodsky wrote: > >Repeat the same test using FreeBSD -current. > > > >a) On the machine where it is slow. > > vmstat -i ; sleep 1 ; vmstat -i > interrupt total rate > irq1: atkbd0 233 2 > irq14: ata0 85 0 > irq16: vgapci0 5377 52 > irq21: hdac0 ohci0 742 7 > irq22: nfe0 ehci0 23610 229 > irq23: atapci1 5405 52 > cpu0: timer 203959 1980 > cpu1: timer 200914 1950 > Total 440325 4275 > interrupt total rate > irq1: atkbd0 234 2 > irq14: ata0 85 0 > irq16: vgapci0 5439 52 > irq21: hdac0 ohci0 742 7 > irq22: nfe0 ehci0 24621 236 > irq23: atapci1 5405 51 > cpu0: timer 205981 1980 > cpu1: timer 202937 1951 > Total 445444 4283 > > >I think the reduced performance can be explained by a clamp on the > > interrupt rate around 1000 interrupts per second instead of 8000. Maybe > > someone has an explanation for this? > > You right, the interrupt rate around 1000 (1011) on this machine, but on > FreeBSD 7.1 more 3000. If it is some kind of interrupt aggregation, may be > I can try to turn it off? > > >b) On the machine where it is fast. > > vmstat -i ; sleep 1 ; vmstat -i > interrupt total rate > irq4: uart0 4154 0 > irq14: ata0 472922 0 > irq15: ata1 26 0 > irq18: em0 752711 0 > irq21: ahc0 53 0 > irq23: ehci0 103456 0 > irq24: em1 147 0 > cpu0: timer 1551216517 2000 > cpu1: timer 1551195251 2000 > Total 3103745237 4001 > interrupt total rate > irq4: uart0 4154 0 > irq14: ata0 472923 0 > irq15: ata1 26 0 > irq18: em0 752713 0 > irq21: ahc0 53 0 > irq23: ehci0 110949 0 > irq24: em1 147 0 > cpu0: timer 1551218551 2000 > cpu1: timer 1551197285 2000 > Total 3103756801 4001 From man at email.com.ua Wed Mar 4 00:48:00 2009 From: man at email.com.ua (Artyom Mirgorodsky) Date: Wed Mar 4 00:48:06 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903030850.01866.hselasky@c2i.net> References: <200903010045.44904.man@email.com.ua> <200903022320.31592.man@email.com.ua> <200903030850.01866.hselasky@c2i.net> Message-ID: <200903041047.57385.man@email.com.ua> I forgot to write, that a similar problem was observed in FreeBSD 7 with usb4bsd patches. From imp at bsdimp.com Wed Mar 4 00:49:01 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Mar 4 00:49:07 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903040922.48163.hselasky@c2i.net> References: <200903032243.31914.hselasky@c2i.net> <4a5ff6bc0903031415s16158407m386b8321a5082996@mail.gmail.com> <200903040922.48163.hselasky@c2i.net> Message-ID: <20090304.014655.1820405796.imp@bsdimp.com> In message: <200903040922.48163.hselasky@c2i.net> Hans Petter Selasky writes: : Hi Steve, : : On Tuesday 03 March 2009, Steve Calfee wrote: : > > I think the reduced performance can be explained by a clamp on the : > > interrupt rate around 1000 interrupts per second instead of 8000. Maybe : > > someone has an explanation for this? : > > : > > The EHCI is being programmed to interrupt at 125us intervals, but there : > > seems to be limits other places. : > > : > > It is possible to workaround this in the umass driver by doing the cmd + : > > read in one operation. : > : > Hi Hans, : > : > I am looking at using FreeBSD in an embedded product. I have not : > examined your ehci software, but I am aware of how Linux and other : > OSes run the controller. : > : > Why are you taking an interrupt every uFrame SOF? : : If the transaction completes before 125us we take the interrupt before 125us. : The problem is that the interrupt delay becomes critical to performance when : the interrupt rate is close to the interrupt limitation. : : For example: : : Transferring 13Mbyte/sec at blocksize equal to 65536 bytes generates 600 : interrupts. Hence the Mass Storage state machine has three steps the : throughput is computed like (600/3)*65536 bytes. If we on the average have to : wait 0.5ms for an interrupt we loose throughput. Shouldn't you be using filters and such to make this less relevant? A filter runs on the order of 5us after the interrupt on fast machines, and 20us on slower (400MHz) ones. You can feed the pipeline better, and handle higher interrupt rates... Warner From imp at bsdimp.com Wed Mar 4 00:52:35 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Mar 4 00:52:46 2009 Subject: Knobs to reduce PCI interrupt latency In-Reply-To: <200903040942.39191.hselasky@c2i.net> References: <200903032243.31914.hselasky@c2i.net> <200903041028.37027.man@email.com.ua> <200903040942.39191.hselasky@c2i.net> Message-ID: <20090304.015013.-862235060.imp@bsdimp.com> In message: <200903040942.39191.hselasky@c2i.net> Hans Petter Selasky writes: : Do we have any knobs in FreeBSD to reduce the interrupt latency? I am : currently seeing performance differences between 8.x and 7.x. Anyone have any : ideas? If we did, don't you think they would be enabled by default :) Seriously, I measured interrupt latency on a 7.0-current system at around 20us for a fast interrupt/filter (300MHz or 400MHz low-power CPU). For fast machines, this can approach 1us, which is hard to measure with the setup I had for the 300MHz case. Deferring work to the scheduled interrupt can be useful, especailly if you can keep the pipeline full such that the filter can kick off the next set of transactions quickly, and then call the completion routines on the last set in parallel in the ithread. This works well for most random-access things, but less well for single threaded, sequential benchmarks. Warner : --HPS : : On Wednesday 04 March 2009, Artyom Mirgorodsky wrote: : > >Repeat the same test using FreeBSD -current. : > > : > >a) On the machine where it is slow. : > : > vmstat -i ; sleep 1 ; vmstat -i : > interrupt total rate : > irq1: atkbd0 233 2 : > irq14: ata0 85 0 : > irq16: vgapci0 5377 52 : > irq21: hdac0 ohci0 742 7 : > irq22: nfe0 ehci0 23610 229 : > irq23: atapci1 5405 52 : > cpu0: timer 203959 1980 : > cpu1: timer 200914 1950 : > Total 440325 4275 : > interrupt total rate : > irq1: atkbd0 234 2 : > irq14: ata0 85 0 : > irq16: vgapci0 5439 52 : > irq21: hdac0 ohci0 742 7 : > irq22: nfe0 ehci0 24621 236 : > irq23: atapci1 5405 51 : > cpu0: timer 205981 1980 : > cpu1: timer 202937 1951 : > Total 445444 4283 : > : > >I think the reduced performance can be explained by a clamp on the : > > interrupt rate around 1000 interrupts per second instead of 8000. Maybe : > > someone has an explanation for this? : > : > You right, the interrupt rate around 1000 (1011) on this machine, but on : > FreeBSD 7.1 more 3000. If it is some kind of interrupt aggregation, may be : > I can try to turn it off? : > : > >b) On the machine where it is fast. : > : > vmstat -i ; sleep 1 ; vmstat -i : > interrupt total rate : > irq4: uart0 4154 0 : > irq14: ata0 472922 0 : > irq15: ata1 26 0 : > irq18: em0 752711 0 : > irq21: ahc0 53 0 : > irq23: ehci0 103456 0 : > irq24: em1 147 0 : > cpu0: timer 1551216517 2000 : > cpu1: timer 1551195251 2000 : > Total 3103745237 4001 : > interrupt total rate : > irq4: uart0 4154 0 : > irq14: ata0 472923 0 : > irq15: ata1 26 0 : > irq18: em0 752713 0 : > irq21: ahc0 53 0 : > irq23: ehci0 110949 0 : > irq24: em1 147 0 : > cpu0: timer 1551218551 2000 : > cpu1: timer 1551197285 2000 : > Total 3103756801 4001 : : : _______________________________________________ : 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" : : From hselasky at c2i.net Wed Mar 4 00:59:18 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 4 00:59:25 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <20090304.014655.1820405796.imp@bsdimp.com> References: <200903032243.31914.hselasky@c2i.net> <200903040922.48163.hselasky@c2i.net> <20090304.014655.1820405796.imp@bsdimp.com> Message-ID: <200903041001.37376.hselasky@c2i.net> On Wednesday 04 March 2009, M. Warner Losh wrote: > In message: <200903040922.48163.hselasky@c2i.net> > > Hans Petter Selasky writes: > : Hi Steve, > : > : On Tuesday 03 March 2009, Steve Calfee wrote: > : > > I think the reduced performance can be explained by a clamp on the > : > > interrupt rate around 1000 interrupts per second instead of 8000. > : > > Maybe someone has an explanation for this? > : > > > : > > The EHCI is being programmed to interrupt at 125us intervals, but > : > > there seems to be limits other places. > : > > > : > > It is possible to workaround this in the umass driver by doing the > : > > cmd + read in one operation. > : > > : > Hi Hans, > : > > : > I am looking at using FreeBSD in an embedded product. I have not > : > examined your ehci software, but I am aware of how Linux and other > : > OSes run the controller. > : > > : > Why are you taking an interrupt every uFrame SOF? > : > : If the transaction completes before 125us we take the interrupt before > : 125us. The problem is that the interrupt delay becomes critical to > : performance when the interrupt rate is close to the interrupt limitation. > : > : For example: > : > : Transferring 13Mbyte/sec at blocksize equal to 65536 bytes generates 600 > : interrupts. Hence the Mass Storage state machine has three steps the > : throughput is computed like (600/3)*65536 bytes. If we on the average > : have to wait 0.5ms for an interrupt we loose throughput. > > Shouldn't you be using filters and such to make this less relevant? A > filter runs on the order of 5us after the interrupt on fast machines, > and 20us on slower (400MHz) ones. You can feed the pipeline better, > and handle higher interrupt rates... > Yes, that's one possibility. It looks like there is some timing slightly out of sync. I have an AMD box with the same symptoms. I will try to figure out what is causing it. --HPS From imp at bsdimp.com Wed Mar 4 01:16:02 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Mar 4 01:16:18 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903041001.37376.hselasky@c2i.net> References: <200903040922.48163.hselasky@c2i.net> <20090304.014655.1820405796.imp@bsdimp.com> <200903041001.37376.hselasky@c2i.net> Message-ID: <20090304.021311.-705197428.imp@bsdimp.com> In message: <200903041001.37376.hselasky@c2i.net> Hans Petter Selasky writes: : On Wednesday 04 March 2009, M. Warner Losh wrote: : > In message: <200903040922.48163.hselasky@c2i.net> : > : > Hans Petter Selasky writes: : > : Hi Steve, : > : : > : On Tuesday 03 March 2009, Steve Calfee wrote: : > : > > I think the reduced performance can be explained by a clamp on the : > : > > interrupt rate around 1000 interrupts per second instead of 8000. : > : > > Maybe someone has an explanation for this? : > : > > : > : > > The EHCI is being programmed to interrupt at 125us intervals, but : > : > > there seems to be limits other places. : > : > > : > : > > It is possible to workaround this in the umass driver by doing the : > : > > cmd + read in one operation. : > : > : > : > Hi Hans, : > : > : > : > I am looking at using FreeBSD in an embedded product. I have not : > : > examined your ehci software, but I am aware of how Linux and other : > : > OSes run the controller. : > : > : > : > Why are you taking an interrupt every uFrame SOF? : > : : > : If the transaction completes before 125us we take the interrupt before : > : 125us. The problem is that the interrupt delay becomes critical to : > : performance when the interrupt rate is close to the interrupt limitation. : > : : > : For example: : > : : > : Transferring 13Mbyte/sec at blocksize equal to 65536 bytes generates 600 : > : interrupts. Hence the Mass Storage state machine has three steps the : > : throughput is computed like (600/3)*65536 bytes. If we on the average : > : have to wait 0.5ms for an interrupt we loose throughput. : > : > Shouldn't you be using filters and such to make this less relevant? A : > filter runs on the order of 5us after the interrupt on fast machines, : > and 20us on slower (400MHz) ones. You can feed the pipeline better, : > and handle higher interrupt rates... : > : : Yes, that's one possibility. It looks like there is some timing slightly out : of sync. I have an AMD box with the same symptoms. I will try to figure out : what is causing it. Maybe there's just good, old-fashioned lock contention going on? 7.x has more Giant use than 8.0 will, and in the past this has been a source of problems. Something else to check into. Maybe enabling lock profiling might yield some good data? Warner From thompsa at FreeBSD.org Wed Mar 4 08:33:49 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Wed Mar 4 08:33:55 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903041001.37376.hselasky@c2i.net> References: <200903032243.31914.hselasky@c2i.net> <200903040922.48163.hselasky@c2i.net> <20090304.014655.1820405796.imp@bsdimp.com> <200903041001.37376.hselasky@c2i.net> Message-ID: <20090304163343.GD17847@citylink.fud.org.nz> On Wed, Mar 04, 2009 at 10:01:36AM +0100, Hans Petter Selasky wrote: > On Wednesday 04 March 2009, M. Warner Losh wrote: > > In message: <200903040922.48163.hselasky@c2i.net> > > > > : > I am looking at using FreeBSD in an embedded product. I have not > > : > examined your ehci software, but I am aware of how Linux and other > > : > OSes run the controller. > > : > > > : > Why are you taking an interrupt every uFrame SOF? > > : > > : If the transaction completes before 125us we take the interrupt before > > : 125us. The problem is that the interrupt delay becomes critical to > > : performance when the interrupt rate is close to the interrupt limitation. > > : > > : For example: > > : > > : Transferring 13Mbyte/sec at blocksize equal to 65536 bytes generates 600 > > : interrupts. Hence the Mass Storage state machine has three steps the > > : throughput is computed like (600/3)*65536 bytes. If we on the average > > : have to wait 0.5ms for an interrupt we loose throughput. > > > > Shouldn't you be using filters and such to make this less relevant? A > > filter runs on the order of 5us after the interrupt on fast machines, > > and 20us on slower (400MHz) ones. You can feed the pipeline better, > > and handle higher interrupt rates... > > > > Yes, that's one possibility. It looks like there is some timing slightly out > of sync. I have an AMD box with the same symptoms. I will try to figure out > what is causing it. If you do change to filters then this is much easier with taskqueues as it has a fast variant, otherwise you would need an intermediate step in order to signal the existing usb threading scheme. The taskqueue changeover will be happening soonish anyway. Andrew From brooks at freebsd.org Wed Mar 4 08:51:10 2009 From: brooks at freebsd.org (Brooks Davis) Date: Wed Mar 4 08:51:17 2009 Subject: The rc.d mess strikes back In-Reply-To: <7d6fde3d0903040004y1fcbb086i355cd0113717620b@mail.gmail.com> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> <20090302.181513.1973603215.imp@bsdimp.com> <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> <20090303180307.GA11134@lor.one-eyed-alien.net> <584bfc3f0903032212x25831c5bi35d9b637c1896e1d@mail.gmail.com> <7d6fde3d0903040004y1fcbb086i355cd0113717620b@mail.gmail.com> Message-ID: <20090304164953.GB1209@lor.one-eyed-alien.net> On Wed, Mar 04, 2009 at 12:04:06AM -0800, Garrett Cooper wrote: > On Tue, Mar 3, 2009 at 10:12 PM, Mike Telahun Makonnen > wrote: > > On Tue, Mar 3, 2009 at 9:03 PM, Brooks Davis wrote: > >> > >> I don't have much time to debug this, but I've not had problems with > >> services starting too early on the systems I've been running with async > >> dhcp. ?If there is a problem with the wait process we need to actually > >> debug it. ?If the wait for a route/running interface isn't sufficent we > >> should try to figure out what is. ?Synchronous dhcp sucks and yeilds > >> justifed user complaints so it would be nice to kill it off. ?I switched > >> the default because it worked for me and I hoped that people would help > >> find and fix edge cases. > > > > Can you elaborate why synchronous DHCP sucks ? > > The only reason I could see is bringup time. Am I correct in this assumption? If you use synchronous DHCP then every interface that wants to try to get a DHCP address if it has link needs to run through the full link timeout at boot. On a laptop this is annoying and generally pointless. The changes to defaultroute to wait for a default route to be set mean that you consolidate the wait in one location and you don't waste time starting dhclient on interfaces until a link exists (or an association is made for wlan devices). There may well be something better to wait or a need for a longer timeout in some environments. It's also quite possible that we have an ordering problem and need to move some more things after defaultroute or move the checks to a different location. -- Brooks -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090304/787e7758/attachment.pgp From opensource2005 at yandex.ru Wed Mar 4 09:10:04 2009 From: opensource2005 at yandex.ru (Alexey Viziryakin) Date: Wed Mar 4 09:10:16 2009 Subject: usb/132312: Xorg 7.4 halts USB controller Message-ID: <200903041705.n24H5kd3042373@www.freebsd.org> >Number: 132312 >Category: usb >Synopsis: Xorg 7.4 halts USB controller >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Mar 04 17:10:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Alexey Viziryakin >Release: 7.1 Stable >Organization: none >Environment: FreeBSD freebsd.localhost 7.1-STABLE FreeBSD 7.1-STABLE #0: Sun Feb 15 14:27:11 MSK 2009 root@freebsd.localhost:/usr/obj/usr/src/sys/I686VESA7R i386 >Description: After perfoming upgrade to Xorg 7.4, it halts my internal USB controller completely. I have this in /var/log/messages: Mar 4 19:42:51 freebsd kernel: usb3: unrecoverable error, controller halted Mar 4 19:42:51 freebsd kernel: usb3: blocking intrs 0x10 Part of my dmesg: Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #0: Sun Feb 15 14:27:11 MSK 2009 root@freebsd.localhost:/usr/obj/usr/src/sys/I686VESA7R Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 2.20GHz (2200.17-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Features2=0x4400 real memory = 1006612480 (959 MB) avail memory = 975761408 (930 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 kqemu version 0x00010300 kqemu: KQEMU installed, max_locked_mem=487144kB. acpi0: on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 3bf00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_acad0: on acpi0 battery0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xd800-0xd87f mem 0xe8000000-0xefffffff,0 xcf800000-0xcf81ffff irq 16 at device 0.0 on pci1 isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0 xa400-0xa40f irq 16 at device 2.5 on pci0 ata0: on atapci0 ata1: [ITHREAD] pcm0: port 0x9400-0x94ff,0x9000-0x907f irq 18 at device 2.7 on pci0 pcm0: [ITHREAD] pcm0: ohci0: mem 0xce800000-0xce800fff irq 20 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xce000000-0xce000fff irq 21 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ohci2: mem 0xcd800000-0xcd800fff irq 22 at device 3.2 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: on ohci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xcd000000-0xcd000fff irq 23 at d evice 3.3 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self poweredA channel 0> on atapci0 umass0: on uhub3 uhub4: on uhub3 uhub4: single transaction translator uhub4: 4 ports with 4 removable, self powered uhub5: on uhub4 uhub5: single transaction translator uhub5: 4 ports with 4 removable, self powered Xorg has compiled without HAL and AIGLX options. >How-To-Repeat: start Xorg 7.4 on same hardware. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From boris.kotzev at gmail.com Wed Mar 4 10:06:46 2009 From: boris.kotzev at gmail.com (Boris Kotzev) Date: Wed Mar 4 10:06:53 2009 Subject: usb touchpad not working properly on CURRENT with usb2 Message-ID: <200903041946.15105.boris.kotzev@gmail.com> Hi, The touchpad of my laptop is not responding properly to input anymore. It used to work fine with the old usb stack. The laptop is running CURRENT from yesterday: FreeBSD zembla.universe 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Wed Mar 4 17:30:05 EET 2009 user@zembla.universe:/usr/obj/usr/src/sys/CUSTOM amd64 When I move my finger horizontally on the touchpad of the laptop, the cursor moves up and down. Moving the finger vertically moves the cursor a little and then it stops. Pressing the touchpad button moves the cursor to the right. The touchpad is detected as: ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Resetting the touchpad produces the following dmesg output: ukbd0: at uhub0, port 2, addr 2 (disconnected) ums1: at uhub0, port 2, addr 2 (disconnected) ums_detach:608: sc=0xffffff000188c400 uhid1: at uhub0, port 2, addr 2 (disconnected) ukbd0: on usbus0 kbd1 at ukbd0 ums1: on usbus0 ums_attach:530: WARNING: report size, 67 bytes, is larger than interrupt size, 64 bytes! ums1: 3 buttons and [XY] coordinates ums_attach:546: sc=0xffffff000184e800 ums_attach:547: X 8/8 ums_attach:548: Y 16/8 ums_attach:549: Z 0/0 ums_attach:550: T 0/0 ums_attach:551: W 0/0 ums_attach:555: B1 0/1 ums_attach:555: B2 1/1 ums_attach:555: B3 2/1 ums_attach:557: size=67, id=0 uhid1: on usbus0 What other information should I provide to help solving this problem? Sincerely, Boris Kotzev From hselasky at c2i.net Wed Mar 4 10:08:32 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 4 10:08:39 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <20090304163343.GD17847@citylink.fud.org.nz> References: <200903032243.31914.hselasky@c2i.net> <200903041001.37376.hselasky@c2i.net> <20090304163343.GD17847@citylink.fud.org.nz> Message-ID: <200903041910.58446.hselasky@c2i.net> On Wednesday 04 March 2009, Andrew Thompson wrote: > On Wed, Mar 04, 2009 at 10:01:36AM +0100, Hans Petter Selasky wrote: > > On Wednesday 04 March 2009, M. Warner Losh wrote: > > > In message: <200903040922.48163.hselasky@c2i.net> > > > > > > : > I am looking at using FreeBSD in an embedded product. I have not > > > : > examined your ehci software, but I am aware of how Linux and other > > > : > OSes run the controller. > > > : > > > > : > Why are you taking an interrupt every uFrame SOF? > > > : > > > : If the transaction completes before 125us we take the interrupt > > > : before 125us. The problem is that the interrupt delay becomes > > > : critical to performance when the interrupt rate is close to the > > > : interrupt limitation. > > > : > > > : For example: > > > : > > > : Transferring 13Mbyte/sec at blocksize equal to 65536 bytes generates > > > : 600 interrupts. Hence the Mass Storage state machine has three steps > > > : the throughput is computed like (600/3)*65536 bytes. If we on the > > > : average have to wait 0.5ms for an interrupt we loose throughput. > > > > > > Shouldn't you be using filters and such to make this less relevant? A > > > filter runs on the order of 5us after the interrupt on fast machines, > > > and 20us on slower (400MHz) ones. You can feed the pipeline better, > > > and handle higher interrupt rates... > > > > Yes, that's one possibility. It looks like there is some timing slightly > > out of sync. I have an AMD box with the same symptoms. I will try to > > figure out what is causing it. > > If you do change to filters then this is much easier with taskqueues as > it has a fast variant, otherwise you would need an intermediate step in > order to signal the existing usb threading scheme. The taskqueue > changeover will be happening soonish anyway. I am not going to do anything with filters. I'm going to try some other things. --HPS From imp at bsdimp.com Wed Mar 4 10:43:24 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Mar 4 10:43:31 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903041910.58446.hselasky@c2i.net> References: <200903041001.37376.hselasky@c2i.net> <20090304163343.GD17847@citylink.fud.org.nz> <200903041910.58446.hselasky@c2i.net> Message-ID: <20090304.114244.106970172.imp@bsdimp.com> In message: <200903041910.58446.hselasky@c2i.net> Hans Petter Selasky writes: : On Wednesday 04 March 2009, Andrew Thompson wrote: : > On Wed, Mar 04, 2009 at 10:01:36AM +0100, Hans Petter Selasky wrote: : > > On Wednesday 04 March 2009, M. Warner Losh wrote: : > > > In message: <200903040922.48163.hselasky@c2i.net> : > > > : > > > : > I am looking at using FreeBSD in an embedded product. I have not : > > > : > examined your ehci software, but I am aware of how Linux and other : > > > : > OSes run the controller. : > > > : > : > > > : > Why are you taking an interrupt every uFrame SOF? : > > > : : > > > : If the transaction completes before 125us we take the interrupt : > > > : before 125us. The problem is that the interrupt delay becomes : > > > : critical to performance when the interrupt rate is close to the : > > > : interrupt limitation. : > > > : : > > > : For example: : > > > : : > > > : Transferring 13Mbyte/sec at blocksize equal to 65536 bytes generates : > > > : 600 interrupts. Hence the Mass Storage state machine has three steps : > > > : the throughput is computed like (600/3)*65536 bytes. If we on the : > > > : average have to wait 0.5ms for an interrupt we loose throughput. : > > > : > > > Shouldn't you be using filters and such to make this less relevant? A : > > > filter runs on the order of 5us after the interrupt on fast machines, : > > > and 20us on slower (400MHz) ones. You can feed the pipeline better, : > > > and handle higher interrupt rates... : > > : > > Yes, that's one possibility. It looks like there is some timing slightly : > > out of sync. I have an AMD box with the same symptoms. I will try to : > > figure out what is causing it. : > : > If you do change to filters then this is much easier with taskqueues as : > it has a fast variant, otherwise you would need an intermediate step in : > order to signal the existing usb threading scheme. The taskqueue : > changeover will be happening soonish anyway. : : I am not going to do anything with filters. I'm going to try some other : things. Then you will always have the scheduling delay... Warner From hselasky at c2i.net Wed Mar 4 11:29:14 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 4 11:29:20 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <20090304.114244.106970172.imp@bsdimp.com> References: <200903041001.37376.hselasky@c2i.net> <200903041910.58446.hselasky@c2i.net> <20090304.114244.106970172.imp@bsdimp.com> Message-ID: <200903042031.37578.hselasky@c2i.net> On Wednesday 04 March 2009, M. Warner Losh wrote: > : > > : > If you do change to filters then this is much easier with taskqueues as > : > it has a fast variant, otherwise you would need an intermediate step in > : > order to signal the existing usb threading scheme. The taskqueue > : > changeover will be happening soonish anyway. > : > : I am not going to do anything with filters. I'm going to try some other > : things. > > Then you will always have the scheduling delay... But the scheduling delay is not in the millisecond range on a 2.4GHz ?? --HPS From hselasky at c2i.net Wed Mar 4 11:36:30 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 4 11:36:37 2009 Subject: usb/132312: Xorg 7.4 halts USB controller In-Reply-To: <200903041705.n24H5kd3042373@www.freebsd.org> References: <200903041705.n24H5kd3042373@www.freebsd.org> Message-ID: <200903042038.57592.hselasky@c2i.net> On Wednesday 04 March 2009, Alexey Viziryakin wrote: > >Number: 132312 > >Category: usb > >Synopsis: Xorg 7.4 halts USB controller > >Confidential: no > >Severity: critical > >Priority: high > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Mar 04 17:10:02 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Alexey Viziryakin > >Release: 7.1 Stable > >Organization: > > none > > >Environment: > > FreeBSD freebsd.localhost 7.1-STABLE FreeBSD 7.1-STABLE #0: Sun Feb 15 > 14:27:11 MSK 2009 root@freebsd.localhost:/usr/obj/usr/src/sys/I686VESA7R > i386 > > >Description: > > After perfoming upgrade to Xorg 7.4, it halts my internal USB controller > completely. I have this in /var/log/messages: > > Mar 4 19:42:51 freebsd kernel: usb3: unrecoverable error, controller > halted Mar 4 19:42:51 freebsd kernel: usb3: blocking intrs 0x10 > > Part of my dmesg: > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.1-STABLE #0: Sun Feb 15 14:27:11 MSK 2009 > root@freebsd.localhost:/usr/obj/usr/src/sys/I686VESA7R > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Celeron(R) CPU 2.20GHz (2200.17-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > Features=0xbfebfbffA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=0x4400 > real memory = 1006612480 (959 MB) > avail memory = 975761408 (930 MB) > ACPI APIC Table: > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > kqemu version 0x00010300 > kqemu: KQEMU installed, max_locked_mem=487144kB. > acpi0: on motherboard > acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, 3bf00000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 > acpi_acad0: on acpi0 > battery0: on acpi0 > acpi_lid0: on acpi0 > acpi_button0: on acpi0 > acpi_button1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: on hostb0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xd800-0xd87f mem > 0xe8000000-0xefffffff,0 xcf800000-0xcf81ffff irq 16 at device 0.0 on pci1 > isab0: at device 2.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0 xa400-0xa40f irq 16 at device 2.5 on > pci0 > ata0: ata1: on atapci0 > ata1: [ITHREAD] > pcm0: port 0x9400-0x94ff,0x9000-0x907f irq 18 at device 2.7 on > pci0 pcm0: [ITHREAD] > pcm0: > ohci0: mem 0xce800000-0xce800fff irq 20 at device > 3.0 on pci0 > ohci0: [GIANT-LOCKED] > ohci0: [ITHREAD] > usb0: OHCI version 1.0, legacy support > usb0: SMM does not respond, resetting > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > ohci1: mem 0xce000000-0xce000fff irq 21 at device > 3.1 on pci0 > ohci1: [GIANT-LOCKED] > ohci1: [ITHREAD] > usb1: OHCI version 1.0, legacy support > usb1: SMM does not respond, resetting > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > ohci2: mem 0xcd800000-0xcd800fff irq 22 at device > 3.2 on pci0 > ohci2: [GIANT-LOCKED] > ohci2: [ITHREAD] > usb2: OHCI version 1.0, legacy support > usb2: SMM does not respond, resetting > usb2: on ohci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem 0xcd000000-0xcd000fff irq 23 > at d evice 3.3 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: on usb3 > uhub3: 6 ports with 6 removable, self poweredA channel 0> on atapci0 > umass0: 2.00 /0.01, addr 2> on uhub3 > uhub4: on > uhub3 uhub4: single transaction translator > uhub4: 4 ports with 4 removable, self powered > uhub5: on > uhub4 uhub5: single transaction translator > uhub5: 4 ports with 4 removable, self powered > > Xorg has compiled without HAL and AIGLX options. > > >How-To-Repeat: > > start Xorg 7.4 on same hardware. > > >Fix: > > > > > >Release-Note: > >Audit-Trail: > >Unformatted: This is probably an IRQ problem. --HPS From hselasky at c2i.net Wed Mar 4 11:39:19 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 4 11:39:26 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903041946.15105.boris.kotzev@gmail.com> References: <200903041946.15105.boris.kotzev@gmail.com> Message-ID: <200903042041.47709.hselasky@c2i.net> On Wednesday 04 March 2009, Boris Kotzev wrote: > Hi, > > The touchpad of my laptop is not responding properly to input anymore. It > used to work fine with the old usb stack. > > The laptop is running CURRENT from yesterday: > > FreeBSD zembla.universe 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Wed Mar 4 > 17:30:05 EET 2009 user@zembla.universe:/usr/obj/usr/src/sys/CUSTOM amd64 > > When I move my finger horizontally on the touchpad of the laptop, the > cursor moves up and down. Moving the finger vertically moves the cursor a > little and then it stops. Pressing the touchpad button moves the cursor to > the right. > > The touchpad is detected as: > > ugen0.2: at usbus0, > cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > > Resetting the touchpad produces the following dmesg output: > > ukbd0: at uhub0, port 2, addr 2 (disconnected) > ums1: at uhub0, port 2, addr 2 (disconnected) > ums_detach:608: sc=0xffffff000188c400 > uhid1: at uhub0, port 2, addr 2 (disconnected) > ukbd0: on usbus0 > kbd1 at ukbd0 > ums1: on usbus0 > ums_attach:530: WARNING: report size, 67 bytes, is larger than interrupt > size, 64 bytes! ums1: 3 buttons and [XY] coordinates > ums_attach:546: sc=0xffffff000184e800 > ums_attach:547: X 8/8 > ums_attach:548: Y 16/8 > ums_attach:549: Z 0/0 > ums_attach:550: T 0/0 > ums_attach:551: W 0/0 > ums_attach:555: B1 0/1 > ums_attach:555: B2 1/1 > ums_attach:555: B3 2/1 > ums_attach:557: size=67, id=0 > uhid1: on usbus0 > > What other information should I provide to help solving this problem? > > Sincerely, > > Boris Kotzev Could you get the USB HID descriptors dumped using: usbhidctl --HPS From imp at bsdimp.com Wed Mar 4 12:10:34 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Mar 4 12:10:40 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903042031.37578.hselasky@c2i.net> References: <200903041910.58446.hselasky@c2i.net> <20090304.114244.106970172.imp@bsdimp.com> <200903042031.37578.hselasky@c2i.net> Message-ID: <20090304.130800.-1943978022.imp@bsdimp.com> In message: <200903042031.37578.hselasky@c2i.net> Hans Petter Selasky writes: : On Wednesday 04 March 2009, M. Warner Losh wrote: : > : > : > : > If you do change to filters then this is much easier with taskqueues as : > : > it has a fast variant, otherwise you would need an intermediate step in : > : > order to signal the existing usb threading scheme. The taskqueue : > : > changeover will be happening soonish anyway. : > : : > : I am not going to do anything with filters. I'm going to try some other : > : things. : > : > Then you will always have the scheduling delay... : : But the scheduling delay is not in the millisecond range on a 2.4GHz ?? Not typically. Warner From hselasky at c2i.net Wed Mar 4 12:40:07 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 4 12:40:14 2009 Subject: usb/132312: Xorg 7.4 halts USB controller Message-ID: <200903042040.n24Ke6nW030203@freefall.freebsd.org> The following reply was made to PR usb/132312; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org Cc: Alexey Viziryakin , freebsd-gnats-submit@freebsd.org Subject: Re: usb/132312: Xorg 7.4 halts USB controller Date: Wed, 4 Mar 2009 20:38:56 +0100 On Wednesday 04 March 2009, Alexey Viziryakin wrote: > >Number: 132312 > >Category: usb > >Synopsis: Xorg 7.4 halts USB controller > >Confidential: no > >Severity: critical > >Priority: high > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Mar 04 17:10:02 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Alexey Viziryakin > >Release: 7.1 Stable > >Organization: > > none > > >Environment: > > FreeBSD freebsd.localhost 7.1-STABLE FreeBSD 7.1-STABLE #0: Sun Feb 15 > 14:27:11 MSK 2009 root@freebsd.localhost:/usr/obj/usr/src/sys/I686VESA7R > i386 > > >Description: > > After perfoming upgrade to Xorg 7.4, it halts my internal USB controller > completely. I have this in /var/log/messages: > > Mar 4 19:42:51 freebsd kernel: usb3: unrecoverable error, controller > halted Mar 4 19:42:51 freebsd kernel: usb3: blocking intrs 0x10 > > Part of my dmesg: > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.1-STABLE #0: Sun Feb 15 14:27:11 MSK 2009 > root@freebsd.localhost:/usr/obj/usr/src/sys/I686VESA7R > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Celeron(R) CPU 2.20GHz (2200.17-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > Features=0xbfebfbffA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=0x4400 > real memory = 1006612480 (959 MB) > avail memory = 975761408 (930 MB) > ACPI APIC Table: > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > kqemu version 0x00010300 > kqemu: KQEMU installed, max_locked_mem=487144kB. > acpi0: on motherboard > acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, 3bf00000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 > acpi_acad0: on acpi0 > battery0: on acpi0 > acpi_lid0: on acpi0 > acpi_button0: on acpi0 > acpi_button1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: on hostb0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xd800-0xd87f mem > 0xe8000000-0xefffffff,0 xcf800000-0xcf81ffff irq 16 at device 0.0 on pci1 > isab0: at device 2.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0 xa400-0xa40f irq 16 at device 2.5 on > pci0 > ata0: ata1: on atapci0 > ata1: [ITHREAD] > pcm0: port 0x9400-0x94ff,0x9000-0x907f irq 18 at device 2.7 on > pci0 pcm0: [ITHREAD] > pcm0: > ohci0: mem 0xce800000-0xce800fff irq 20 at device > 3.0 on pci0 > ohci0: [GIANT-LOCKED] > ohci0: [ITHREAD] > usb0: OHCI version 1.0, legacy support > usb0: SMM does not respond, resetting > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > ohci1: mem 0xce000000-0xce000fff irq 21 at device > 3.1 on pci0 > ohci1: [GIANT-LOCKED] > ohci1: [ITHREAD] > usb1: OHCI version 1.0, legacy support > usb1: SMM does not respond, resetting > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > ohci2: mem 0xcd800000-0xcd800fff irq 22 at device > 3.2 on pci0 > ohci2: [GIANT-LOCKED] > ohci2: [ITHREAD] > usb2: OHCI version 1.0, legacy support > usb2: SMM does not respond, resetting > usb2: on ohci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem 0xcd000000-0xcd000fff irq 23 > at d evice 3.3 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: on usb3 > uhub3: 6 ports with 6 removable, self poweredA channel 0> on atapci0 > umass0: 2.00 /0.01, addr 2> on uhub3 > uhub4: on > uhub3 uhub4: single transaction translator > uhub4: 4 ports with 4 removable, self powered > uhub5: on > uhub4 uhub5: single transaction translator > uhub5: 4 ports with 4 removable, self powered > > Xorg has compiled without HAL and AIGLX options. > > >How-To-Repeat: > > start Xorg 7.4 on same hardware. > > >Fix: > > > > > >Release-Note: > >Audit-Trail: > >Unformatted: This is probably an IRQ problem. --HPS From boris.kotzev at gmail.com Wed Mar 4 13:46:09 2009 From: boris.kotzev at gmail.com (Boris Kotzev) Date: Wed Mar 4 13:46:16 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903042041.47709.hselasky@c2i.net> References: <200903041946.15105.boris.kotzev@gmail.com> <200903042041.47709.hselasky@c2i.net> Message-ID: <200903042346.00840.boris.kotzev@gmail.com> > On Wednesday 04 March 2009, Boris Kotzev wrote: > > Hi, > > > > The touchpad of my laptop is not responding properly to input anymore. It > > used to work fine with the old usb stack. > > > > The laptop is running CURRENT from yesterday: > > > > FreeBSD zembla.universe 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Wed Mar 4 > > 17:30:05 EET 2009 user@zembla.universe:/usr/obj/usr/src/sys/CUSTOM amd64 > > > > When I move my finger horizontally on the touchpad of the laptop, the > > cursor moves up and down. Moving the finger vertically moves the cursor a > > little and then it stops. Pressing the touchpad button moves the cursor > > to the right. > > > > The touchpad is detected as: > > > > ugen0.2: at usbus0, > > cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > > > > Resetting the touchpad produces the following dmesg output: > > > > ukbd0: at uhub0, port 2, addr 2 (disconnected) > > ums1: at uhub0, port 2, addr 2 (disconnected) > > ums_detach:608: sc=0xffffff000188c400 > > uhid1: at uhub0, port 2, addr 2 (disconnected) > > ukbd0: on usbus0 > > kbd1 at ukbd0 > > ums1: on usbus0 > > ums_attach:530: WARNING: report size, 67 bytes, is larger than interrupt > > size, 64 bytes! ums1: 3 buttons and [XY] coordinates > > ums_attach:546: sc=0xffffff000184e800 > > ums_attach:547: X 8/8 > > ums_attach:548: Y 16/8 > > ums_attach:549: Z 0/0 > > ums_attach:550: T 0/0 > > ums_attach:551: W 0/0 > > ums_attach:555: B1 0/1 > > ums_attach:555: B2 1/1 > > ums_attach:555: B3 2/1 > > ums_attach:557: size=67, id=0 > > uhid1: on usbus0 > > > > What other information should I provide to help solving this problem? > > > > Sincerely, > > > > Boris Kotzev > > Could you get the USB HID descriptors dumped using: > > usbhidctl > > --HPS All information I managed to extract by using usbhidctl is below: # usbhidctl -f /dev/uhid1 -ra Report descriptor: Collection page=Consumer usage=Consumer_Control Input size=8 count=1 page=Consumer usage=Eject, logical range 0..255 End collection Total input size 1 bytes Total output size 0 bytes Total feature size 0 bytes usbhidctl: USB_SET_IMMED: Device not configured If it is not enough, will you explain to me how to use this utility? Thanks! Boris Kotzev From hselasky at c2i.net Wed Mar 4 14:08:33 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 4 14:08:39 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903041047.57385.man@email.com.ua> References: <200903010045.44904.man@email.com.ua> <200903030850.01866.hselasky@c2i.net> <200903041047.57385.man@email.com.ua> Message-ID: <200903042311.00403.hselasky@c2i.net> On Wednesday 04 March 2009, Artyom Mirgorodsky wrote: > I forgot to write, that a similar problem was observed in FreeBSD 7 with > usb4bsd patches. Here is a patch which I think will address your problem. It is EHCI hardware related. Different models behave differently. Try this: http://perforce.freebsd.org/chv.cgi?CH=158692 --HPS From stevecalfee at gmail.com Wed Mar 4 14:18:52 2009 From: stevecalfee at gmail.com (Steve Calfee) Date: Wed Mar 4 14:18:59 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903040922.48163.hselasky@c2i.net> References: <200903010045.44904.man@email.com.ua> <200903032243.31914.hselasky@c2i.net> <4a5ff6bc0903031415s16158407m386b8321a5082996@mail.gmail.com> <200903040922.48163.hselasky@c2i.net> Message-ID: <4a5ff6bc0903041418g1a26c046sbc7ae2459ba48044@mail.gmail.com> On Wed, Mar 4, 2009 at 12:22 AM, Hans Petter Selasky wrote: > Hi Steve, > > On Tuesday 03 March 2009, Steve Calfee wrote: >> > I think the reduced performance can be explained by a clamp on the >> > interrupt rate around 1000 interrupts per second instead of 8000. Maybe >> > someone has an explanation for this? >> > >> > The EHCI is being programmed to interrupt at 125us intervals, but there >> > seems to be limits other places. >> > >> > It is possible to workaround this in the umass driver by doing the cmd + >> > read in one operation. >> >> Hi Hans, >> >> I am looking at using FreeBSD in an embedded product. I have not >> examined your ehci software, but I am aware of how Linux and other >> OSes run the controller. >> >> Why are you taking an interrupt every uFrame SOF? > > If the transaction completes before 125us we take the interrupt before 125us. > The problem is that the interrupt delay becomes critical to performance when > the interrupt rate is close to the interrupt limitation. > Hi Hans, Ok I have looked a little at your ehci.c code and the ehci spec. I see that you are talking about the "interrupt threshold control" field which Intel added to the ehci to keep the high speed controller from flooding the cpu with interrupts. It has nothing to do with SOF interrupts. > For example: > > Transferring 13Mbyte/sec at blocksize equal to 65536 bytes generates 600 > interrupts. Hence the Mass Storage state machine has three steps the > throughput is computed like (600/3)*65536 bytes. If we on the average have to > wait 0.5ms for an interrupt we loose throughput. > I think here you are referring to the awkward synchronous scsi protocol embedded in usb mass storage devices. In this protocol the host does a IN and gets a USBS... status data block, does an OUT with a USBC... data block and then the data transfer (either IN or OUT). I don't think I have seen Linux or Windows transfer (in one scsi xfer) more than about 40K, but ok lets say 65K is possible. This means 128 -- 512 byte packet transfers. The max number of transfers I have seen in a microframe is about 11, but lets say it is 16 with some super ehci/dma controller. That says you can transfer 65K in 128/16 == 8 uFrames (this is higher than the 60Mbyte/sec bus speed of light, but it is easy to calculate). In this same super computer/ehci hardware the 3 packets (USBS, USBC, data) will most likely all be in different microframes. So in this scenario there will be 3 interrupts in 10 microframes = 1.250 milliseconds. In practice the USB mass storage device is the limiting factor and will be much slower than this. So what I am getting at is it is hard to believe the interrupt rate which will limit your xfer speed. Now the interesting question (for me a FreeBSD novice) is how does the OS limit the number of interrupts? Usually they would be limited by the available CPU power, and unlikely be limited to some arbitrary number per second (1000 or 8000). Does FreeBSD run all interrupts out of what Linux would call a bottom-half or tasklet? In that case latency for sequential I/O in the 3 step scsi protocol could add up to hurt you. Regards, Steve From stevecalfee at gmail.com Wed Mar 4 14:37:59 2009 From: stevecalfee at gmail.com (Steve Calfee) Date: Wed Mar 4 14:38:06 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903042311.00403.hselasky@c2i.net> References: <200903010045.44904.man@email.com.ua> <200903030850.01866.hselasky@c2i.net> <200903041047.57385.man@email.com.ua> <200903042311.00403.hselasky@c2i.net> Message-ID: <4a5ff6bc0903041437l52a58387v1735e34ebc383847@mail.gmail.com> On Wed, Mar 4, 2009 at 2:10 PM, Hans Petter Selasky wrote: > On Wednesday 04 March 2009, Artyom Mirgorodsky wrote: >> I forgot to write, that a similar problem was observed in FreeBSD 7 with >> usb4bsd patches. > > Here is a patch which I think will address your problem. It is EHCI hardware > related. Different models behave differently. Try this: > > http://perforce.freebsd.org/chv.cgi?CH=158692 > Wow, that is bizarre. The "doorbell" is usually used so the software knows that the cpu vs dma race is complete when moving qtds off the qh - ie dequeueing requests. What you have done is asked the guy doing the photo finish at the end of a horse race to press the shutter a little before the horse crosses the line - so the shutter latency will allow a picture right as the horse crosses the line. Unfortunately, this (like all races) is affected by the object doing the racing - horse speed and camera speed are variable! I believe something else must be wrong. Regards, Steve From man at email.com.ua Wed Mar 4 14:48:26 2009 From: man at email.com.ua (Artyom Mirgorodsky) Date: Wed Mar 4 14:48:33 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903042311.00403.hselasky@c2i.net> References: <200903010045.44904.man@email.com.ua> <200903041047.57385.man@email.com.ua> <200903042311.00403.hselasky@c2i.net> Message-ID: <200903050052.01911.man@email.com.ua> > Here is a patch which I think will address your problem. It is EHCI hardware > related. Different models behave differently. Try this: > > http://perforce.freebsd.org/chv.cgi?CH=158692 Much better: dd if=/dev/da0 of=/dev/null bs=64k count=5000 5000+0 records in 5000+0 records out 327680000 bytes transferred in 17.282871 secs (18959813 bytes/sec) From hselasky at c2i.net Wed Mar 4 15:07:20 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 4 15:07:27 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <4a5ff6bc0903041437l52a58387v1735e34ebc383847@mail.gmail.com> References: <200903010045.44904.man@email.com.ua> <200903042311.00403.hselasky@c2i.net> <4a5ff6bc0903041437l52a58387v1735e34ebc383847@mail.gmail.com> Message-ID: <200903050009.48188.hselasky@c2i.net> On Wednesday 04 March 2009, Steve Calfee wrote: > On Wed, Mar 4, 2009 at 2:10 PM, Hans Petter Selasky wrote: > > On Wednesday 04 March 2009, Artyom Mirgorodsky wrote: > >> I forgot to write, that a similar problem was observed in FreeBSD 7 with > >> usb4bsd patches. > > > > Here is a patch which I think will address your problem. It is EHCI > > hardware related. Different models behave differently. Try this: > > > > http://perforce.freebsd.org/chv.cgi?CH=158692 > > Wow, that is bizarre. The "doorbell" is usually used so the software > knows that the cpu vs dma race is complete when moving qtds off the qh > - ie dequeueing requests. What you have done is asked the guy doing > the photo finish at the end of a horse race to press the shutter a > little before the horse crosses the line - so the shutter latency will > allow a picture right as the horse crosses the line. Unfortunately, > this (like all races) is affected by the object doing the racing - > horse speed and camera speed are variable! > > I believe something else must be wrong. The new USB stack _is_ doing things faster than the old one. I have gone through a large range of tests before I landed on the doorbell trick. Actually the new USB stack doesn't use the doorbell, we use software timers instead. The hardware certainly behaves different from vendor to vendor. Probably somone making the chips have to explain what is wrong. In my (Nvidia+AMD64+EHCI) test case I tried: No doorbell: 12 Mbyte/sec Doorbell after transfer (after QH removal): 14 Mbyte/sec Doorbell after next transfer (after QH insertion): 21 Mbyte/sec On my other reference Intel chip I did not get any noticable performance increase by doing this trick ... I think this trick is the best I can do. I've seen peculiarities before regarding the doorbell not behaving like it should .... --HPS From thompsa at FreeBSD.org Wed Mar 4 17:29:17 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Wed Mar 4 17:29:29 2009 Subject: TODO Message-ID: <20090305012911.GB26859@citylink.fud.org.nz> Hi, I have started a page to track USB tasks, please update with any items and feel free to work on any. Any discussion about the items should happen on the usb@ mailing list. http://wiki.freebsd.org/USBTODO cheers, Andrew From alex.wilkinson at dsto.defence.gov.au Wed Mar 4 18:02:57 2009 From: alex.wilkinson at dsto.defence.gov.au (Wilkinson, Alex) Date: Wed Mar 4 18:03:04 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <200903050009.48188.hselasky@c2i.net> References: <200903010045.44904.man@email.com.ua> <200903042311.00403.hselasky@c2i.net> <4a5ff6bc0903041437l52a58387v1735e34ebc383847@mail.gmail.com> <200903050009.48188.hselasky@c2i.net> Message-ID: <20090305004839.GH92789@stlux503.dsto.defence.gov.au> Excuse my ignorance, but what is meant by "doorbell" ? -aW 0n Thu, Mar 05, 2009 at 12:09:47AM +0100, Hans Petter Selasky wrote: >The new USB stack _is_ doing things faster than the old one. I have gone >through a large range of tests before I landed on the doorbell trick. >Actually the new USB stack doesn't use the doorbell, we use software timers >instead. The hardware certainly behaves different from vendor to vendor. >Probably somone making the chips have to explain what is wrong. > >In my (Nvidia+AMD64+EHCI) test case I tried: > >No doorbell: 12 Mbyte/sec >Doorbell after transfer (after QH removal): 14 Mbyte/sec >Doorbell after next transfer (after QH insertion): 21 Mbyte/sec IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From pluknet at gmail.com Wed Mar 4 22:47:06 2009 From: pluknet at gmail.com (pluknet) Date: Wed Mar 4 22:47:12 2009 Subject: TODO In-Reply-To: <20090305012911.GB26859@citylink.fud.org.nz> References: <20090305012911.GB26859@citylink.fud.org.nz> Message-ID: 2009/3/5 Andrew Thompson : > Hi, > > > I have started a page to track USB tasks, please update with any items > and feel free to work on any. > > Any discussion about the items should happen on the usb@ mailing list. > > http://wiki.freebsd.org/USBTODO > Please, add the DDB support. This is now impossible due to threaded nature of USB. -- wbr, pluknet From hselasky at c2i.net Thu Mar 5 00:38:16 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Mar 5 00:38:23 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <20090305004839.GH92789@stlux503.dsto.defence.gov.au> References: <200903010045.44904.man@email.com.ua> <200903050009.48188.hselasky@c2i.net> <20090305004839.GH92789@stlux503.dsto.defence.gov.au> Message-ID: <200903050940.44754.hselasky@c2i.net> On Thursday 05 March 2009, Wilkinson, Alex wrote: > Excuse my ignorance, but what is meant by "doorbell" ? > Doorbell is an EHCI callback interrupt when the Async queue has been checked for removed QH's. --HPS From keramida at freebsd.org Thu Mar 5 00:53:28 2009 From: keramida at freebsd.org (Giorgos Keramidas) Date: Thu Mar 5 00:53:35 2009 Subject: recent usb2 regression Message-ID: <87k5742wwv.fsf@kobe.laptop> After my last update to March 1 sources, uhci started going into interrupt storm mode: $ vmstat -i interrupt total rate irq1: atkbd0 8676 1 irq9: acpi0 12412 2 irq12: psm0 5979 1 irq14: ata0 601562 136 irq15: ata1 69 0 irq16: uhci0 745625990 169191 irq19: uhci3 5906 1 irq23: uhci2 ehci1 1 0 cpu0: timer 8813127 1999 irq256: hdac0 116677 26 irq258: re0 2438 0 cpu1: timer 8804089 1997 irq259: vgapci0 20525 4 Total 764017451 173364 Setting hw.usb2.uhci.debug=1 I see many repeated messages like: Mar 5 10:06:39 foo kernel: uhci_interrupt:1453: uhci_interrupt: host controller halted Mar 5 10:06:39 foo kernel: uhci_dumpregs:691: usbus0 regs: cmd=0080, sts=0020, intr=000f, frnum=0072, flbase=010be1c8, sof=0040, portsc1=0080, portsc2=0080 Mar 5 10:06:39 foo kernel: uhci_dump_qh:764: QH(0xc6251e00) at 0x01a51e02: h_next=0x01a79e82 e_next=0x00000001 Mar 5 10:06:39 foo kernel: uhci_dump_qh:764: QH(0xc6279e80) at 0x01a79e82: h_next=0x01a76702 e_next=0x00000001 Mar 5 10:06:39 foo kernel: uhci_dump_qh:764: QH(0xc6276700) at 0x01a76702: h_next=0x01a8b002 e_next=0x00000001 Mar 5 10:06:39 foo kernel: uhci_dump_qh:764: QH(0xc628b000) at 0x01a8b002: h_next=0x00000001 e_next=0x01a77080 There are local changes in this src/ tree, but none of them seems related to usb2 going crazy. I am running an i386 kernel build from the `KOBE' config file shown in the patch uploaded at: http://people.freebsd.org/~keramida/diff/gker.head.r189392.diff usbconfig shows only my USB mouse attached at the time: # usbconfig ugen5.1: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen6.1: at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON 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=HIGH (480Mbps) pwr=ON ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.2: at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON Is this a known problem with kernels from March 1, or a new one? From hselasky at c2i.net Thu Mar 5 01:11:25 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Mar 5 01:11:32 2009 Subject: recent usb2 regression In-Reply-To: <87k5742wwv.fsf@kobe.laptop> References: <87k5742wwv.fsf@kobe.laptop> Message-ID: <200903051013.19417.hselasky@c2i.net> On Thursday 05 March 2009, Giorgos Keramidas wrote: > After my last update to March 1 sources, uhci started going into > interrupt storm mode: > > $ vmstat -i > interrupt total rate > irq1: atkbd0 8676 1 > irq9: acpi0 12412 2 > irq12: psm0 5979 1 > irq14: ata0 601562 136 > irq15: ata1 69 0 > irq16: uhci0 745625990 169191 > irq19: uhci3 5906 1 > irq23: uhci2 ehci1 1 0 > cpu0: timer 8813127 1999 > irq256: hdac0 116677 26 > irq258: re0 2438 0 > cpu1: timer 8804089 1997 > irq259: vgapci0 20525 4 > Total 764017451 173364 > > Setting hw.usb2.uhci.debug=1 I see many repeated messages like: > > Mar 5 10:06:39 foo kernel: uhci_interrupt:1453: uhci_interrupt: host > controller halted Mar 5 10:06:39 foo kernel: uhci_dumpregs:691: usbus0 > regs: cmd=0080, sts=0020, intr=000f, frnum=0072, flbase=010be1c8, sof=0040, > portsc1=0080, portsc2=0080 Mar 5 10:06:39 foo kernel: uhci_dump_qh:764: > QH(0xc6251e00) at 0x01a51e02: h_next=0x01a79e82 e_next=0x00000001 Mar 5 > 10:06:39 foo kernel: uhci_dump_qh:764: QH(0xc6279e80) at 0x01a79e82: > h_next=0x01a76702 e_next=0x00000001 Mar 5 10:06:39 foo kernel: > uhci_dump_qh:764: QH(0xc6276700) at 0x01a76702: h_next=0x01a8b002 > e_next=0x00000001 Mar 5 10:06:39 foo kernel: uhci_dump_qh:764: > QH(0xc628b000) at 0x01a8b002: h_next=0x00000001 e_next=0x01a77080 > > There are local changes in this src/ tree, but none of them seems > related to usb2 going crazy. I am running an i386 kernel build from the > `KOBE' config file shown in the patch uploaded at: > > http://people.freebsd.org/~keramida/diff/gker.head.r189392.diff > > usbconfig shows only my USB mouse attached at the time: > > # usbconfig > ugen5.1: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) > pwr=ON ugen6.1: at usbus6, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=ON 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=HIGH (480Mbps) pwr=ON ugen3.1: at > usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: Intel> at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.2: 0x0003 Creative Labs> at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > > Is this a known problem with kernels from March 1, or a new one? Hi, The only active interrupt is the HCH status bit. You can try editing /sys/dev/usb/controller/uhci.c and apply the following patch: /* get acknowledge bits */ status &= (UHCI_STS_USBINT | UHCI_STS_USBEI | UHCI_STS_RD | + UHCI_STS_HCH | UHCI_STS_HSE | UHCI_STS_HCPE); --HPS From hselasky at c2i.net Thu Mar 5 01:16:46 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Mar 5 01:16:52 2009 Subject: Low perfomance when read from usb flash drive In-Reply-To: <4a5ff6bc0903041418g1a26c046sbc7ae2459ba48044@mail.gmail.com> References: <200903010045.44904.man@email.com.ua> <200903040922.48163.hselasky@c2i.net> <4a5ff6bc0903041418g1a26c046sbc7ae2459ba48044@mail.gmail.com> Message-ID: <200903051019.14577.hselasky@c2i.net> On Wednesday 04 March 2009, Steve Calfee wrote: > On Wed, Mar 4, 2009 at 12:22 AM, Hans Petter Selasky wrote: > > Hi Steve, > > > > On Tuesday 03 March 2009, Steve Calfee wrote: > >> > I think the reduced performance can be explained by a clamp on the > >> > interrupt rate around 1000 interrupts per second instead of 8000. > >> > Maybe someone has an explanation for this? > >> > > >> > The EHCI is being programmed to interrupt at 125us intervals, but > >> > there seems to be limits other places. > >> > > >> > It is possible to workaround this in the umass driver by doing the cmd > >> > + read in one operation. > >> > >> Hi Hans, > >> > >> I am looking at using FreeBSD in an embedded product. I have not > >> examined your ehci software, but I am aware of how Linux and other > >> OSes run the controller. > >> > >> Why are you taking an interrupt every uFrame SOF? > > > > If the transaction completes before 125us we take the interrupt before > > 125us. The problem is that the interrupt delay becomes critical to > > performance when the interrupt rate is close to the interrupt limitation. > Hi Steve, > Now the interesting question (for me a FreeBSD novice) is how does the > OS limit the number of interrupts? Usually they would be limited by > the available CPU power, and unlikely be limited to some arbitrary > number per second (1000 or 8000). Does FreeBSD run all interrupts out > of what Linux would call a bottom-half or tasklet? In that case > latency for sequential I/O in the 3 step scsi protocol could add up to > hurt you. I think there is no limit. It is the EHCI hardware that is responsible for limiting the IRQ rate. Usually it is limited by some bits in the command register like 1,2,4,8.. x 125us. I'm currently using 1x125us yielding max 8000 IRQs/second. The operating system is probably not the bottleneck in this case. It's something in the hardware hanging or waiting. --HPS From hselasky at c2i.net Thu Mar 5 05:28:56 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Mar 5 05:29:03 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903042346.00840.boris.kotzev@gmail.com> References: <200903041946.15105.boris.kotzev@gmail.com> <200903042041.47709.hselasky@c2i.net> <200903042346.00840.boris.kotzev@gmail.com> Message-ID: <200903051431.22066.hselasky@c2i.net> On Wednesday 04 March 2009, Boris Kotzev wrote: > > On Wednesday 04 March 2009, Boris Kotzev wrote: > > > Hi, > > > > > > The touchpad of my laptop is not responding properly to input anymore. > > > It used to work fine with the old usb stack. > > > > > > The laptop is running CURRENT from yesterday: > > > > > > FreeBSD zembla.universe 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Wed Mar 4 > > > 17:30:05 EET 2009 user@zembla.universe:/usr/obj/usr/src/sys/CUSTOM > > > amd64 > > > > > > When I move my finger horizontally on the touchpad of the laptop, the > > > cursor moves up and down. Moving the finger vertically moves the cursor > > > a little and then it stops. Pressing the touchpad button moves the > > > cursor to the right. > > > > > > The touchpad is detected as: > > > > > > ugen0.2: at usbus0, > > > cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > > > > > > Resetting the touchpad produces the following dmesg output: > > > > > > ukbd0: at uhub0, port 2, addr 2 (disconnected) > > > ums1: at uhub0, port 2, addr 2 (disconnected) > > > ums_detach:608: sc=0xffffff000188c400 > > > uhid1: at uhub0, port 2, addr 2 (disconnected) > > > ukbd0: on usbus0 > > > kbd1 at ukbd0 > > > ums1: on usbus0 > > > ums_attach:530: WARNING: report size, 67 bytes, is larger than > > > interrupt size, 64 bytes! ums1: 3 buttons and [XY] coordinates > > > ums_attach:546: sc=0xffffff000184e800 > > > ums_attach:547: X 8/8 > > > ums_attach:548: Y 16/8 > > > ums_attach:549: Z 0/0 > > > ums_attach:550: T 0/0 > > > ums_attach:551: W 0/0 > > > ums_attach:555: B1 0/1 > > > ums_attach:555: B2 1/1 > > > ums_attach:555: B3 2/1 > > > ums_attach:557: size=67, id=0 > > > uhid1: on usbus0 > > > > > > What other information should I provide to help solving this problem? > > > > > > Sincerely, > > > > > > Boris Kotzev > > > > Could you get the USB HID descriptors dumped using: > > > > usbhidctl > > > > --HPS > > All information I managed to extract by using usbhidctl is below: > > # usbhidctl -f /dev/uhid1 -ra > Report descriptor: > Collection page=Consumer usage=Consumer_Control > Input size=8 count=1 page=Consumer usage=Eject, logical range 0..255 > End collection > Total input size 1 bytes > Total output size 0 bytes > Total feature size 0 bytes > usbhidctl: USB_SET_IMMED: Device not configured > > If it is not enough, will you explain to me how to use this utility? > Hi, I think you have to unload ums module. Then replug the device and search for the new uhid device. Can you also do: usbconfig -u 0 -a 2 dump_device_desc dump_curr_config_desc --HPS From dfilter at FreeBSD.ORG Thu Mar 5 08:20:04 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Thu Mar 5 08:20:10 2009 Subject: usb/117185: commit references a PR Message-ID: <200903051620.n25GK33C062929@freefall.freebsd.org> The following reply was made to PR usb/117185; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/117185: commit references a PR Date: Thu, 5 Mar 2009 16:15:23 +0000 (UTC) Author: thompsa Date: Thu Mar 5 16:15:07 2009 New Revision: 189405 URL: http://svn.freebsd.org/changeset/base/189405 Log: Add support for the UNION interface descriptor, used by Nokia phones. PR: usb/117185 Modified: head/sys/dev/usb/serial/umodem.c Modified: head/sys/dev/usb/serial/umodem.c ============================================================================== --- head/sys/dev/usb/serial/umodem.c Thu Mar 5 16:03:44 2009 (r189404) +++ head/sys/dev/usb/serial/umodem.c Thu Mar 5 16:15:07 2009 (r189405) @@ -69,6 +69,7 @@ __FBSDID("$FreeBSD$"); /* * Comm Class spec: http://www.usb.org/developers/devclass_docs/usbccs10.pdf * http://www.usb.org/developers/devclass_docs/usbcdc11.pdf + * http://www.usb.org/developers/devclass_docs/cdc_wmc10.zip */ /* @@ -253,8 +254,6 @@ static int umodem_probe(device_t dev) { struct usb2_attach_arg *uaa = device_get_ivars(dev); - uint8_t cm; - uint8_t acm; int error; DPRINTFN(11, "\n"); @@ -263,19 +262,6 @@ umodem_probe(device_t dev) return (ENXIO); } error = usb2_lookup_id_by_uaa(umodem_devs, sizeof(umodem_devs), uaa); - if (error) { - return (error); - } - if (uaa->driver_info == NULL) { - /* some modems do not have any capabilities */ - return (error); - } - umodem_get_caps(uaa, &cm, &acm); - if (!(cm & USB_CDC_CM_DOES_CM) || - !(cm & USB_CDC_CM_OVER_DATA) || - !(acm & USB_CDC_ACM_HAS_LINE)) { - error = ENXIO; - } return (error); } @@ -285,6 +271,7 @@ umodem_attach(device_t dev) struct usb2_attach_arg *uaa = device_get_ivars(dev); struct umodem_softc *sc = device_get_softc(dev); struct usb2_cdc_cm_descriptor *cmd; + struct usb2_cdc_union_descriptor *cud; uint8_t i; int error; @@ -302,10 +289,20 @@ umodem_attach(device_t dev) cmd = umodem_get_desc(uaa, UDESC_CS_INTERFACE, UDESCSUB_CDC_CM); if ((cmd == NULL) || (cmd->bLength < sizeof(*cmd))) { - device_printf(dev, "no CM descriptor!\n"); - goto detach; + + cud = usb2_find_descriptor(uaa->device, NULL, + uaa->info.bIfaceIndex, UDESC_CS_INTERFACE, + 0 - 1, UDESCSUB_CDC_UNION, 0 - 1); + + if ((cud == NULL) || (cud->bLength < sizeof(*cud))) { + device_printf(dev, "no CM or union descriptor!\n"); + goto detach; + } + + sc->sc_data_iface_no = cud->bSlaveInterface[0]; + } else { + sc->sc_data_iface_no = cmd->bDataInterface; } - sc->sc_data_iface_no = cmd->bDataInterface; device_printf(dev, "data interface %d, has %sCM over " "data, has %sbreak\n", @@ -419,21 +416,19 @@ umodem_get_caps(struct usb2_attach_arg * struct usb2_cdc_cm_descriptor *cmd; struct usb2_cdc_acm_descriptor *cad; - *cm = *acm = 0; - cmd = umodem_get_desc(uaa, UDESC_CS_INTERFACE, UDESCSUB_CDC_CM); if ((cmd == NULL) || (cmd->bLength < sizeof(*cmd))) { - DPRINTF("no CM desc\n"); - return; - } - *cm = cmd->bmCapabilities; + DPRINTF("no CM desc (faking one)\n"); + *cm = USB_CDC_CM_DOES_CM | USB_CDC_CM_OVER_DATA; + } else + *cm = cmd->bmCapabilities; cad = umodem_get_desc(uaa, UDESC_CS_INTERFACE, UDESCSUB_CDC_ACM); if ((cad == NULL) || (cad->bLength < sizeof(*cad))) { DPRINTF("no ACM desc\n"); - return; - } - *acm = cad->bmCapabilities; + *acm = 0; + } else + *acm = cad->bmCapabilities; } static void _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From hselasky at c2i.net Thu Mar 5 08:50:06 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Mar 5 08:50:16 2009 Subject: usb/117185: [umodem] [patch] Add support for UNION interface descriptor Message-ID: <200903051650.n25Go4lO086710@freefall.freebsd.org> The following reply was made to PR usb/117185; it has been noted by GNATS. From: Hans Petter Selasky To: bug-followup@freebsd.org, eugen@grosbein.pp.ru, Andrew Thompson Cc: Subject: Re: usb/117185: [umodem] [patch] Add support for UNION interface descriptor Date: Thu, 5 Mar 2009 16:50:49 +0100 Hi, Committed to USB P4 with some modifications. http://perforce.freebsd.org/chv.cgi?CH=158721 Andrew: Another patch to commit. --HPS From boris.kotzev at gmail.com Thu Mar 5 11:09:06 2009 From: boris.kotzev at gmail.com (Boris Kotzev) Date: Thu Mar 5 11:09:13 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903051431.22066.hselasky@c2i.net> References: <200903041946.15105.boris.kotzev@gmail.com> <200903042346.00840.boris.kotzev@gmail.com> <200903051431.22066.hselasky@c2i.net> Message-ID: <200903052109.00282.boris.kotzev@gmail.com> > On Wednesday 04 March 2009, Boris Kotzev wrote: > > > On Wednesday 04 March 2009, Boris Kotzev wrote: > > > > Hi, > > > > > > > > The touchpad of my laptop is not responding properly to input > > > > anymore. It used to work fine with the old usb stack. > > > > > > > > The laptop is running CURRENT from yesterday: > > > > > > > > FreeBSD zembla.universe 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Wed Mar > > > > 4 17:30:05 EET 2009 user@zembla.universe:/usr/obj/usr/src/sys/CUSTOM > > > > amd64 > > > > > > > > When I move my finger horizontally on the touchpad of the laptop, the > > > > cursor moves up and down. Moving the finger vertically moves the > > > > cursor a little and then it stops. Pressing the touchpad button moves > > > > the cursor to the right. > > > > > > > > The touchpad is detected as: > > > > > > > > ugen0.2: at > > > > usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > > > > > > > > Resetting the touchpad produces the following dmesg output: > > > > > > > > ukbd0: at uhub0, port 2, addr 2 (disconnected) > > > > ums1: at uhub0, port 2, addr 2 (disconnected) > > > > ums_detach:608: sc=0xffffff000188c400 > > > > uhid1: at uhub0, port 2, addr 2 (disconnected) > > > > ukbd0: on usbus0 > > > > kbd1 at ukbd0 > > > > ums1: on usbus0 > > > > ums_attach:530: WARNING: report size, 67 bytes, is larger than > > > > interrupt size, 64 bytes! ums1: 3 buttons and [XY] coordinates > > > > ums_attach:546: sc=0xffffff000184e800 > > > > ums_attach:547: X 8/8 > > > > ums_attach:548: Y 16/8 > > > > ums_attach:549: Z 0/0 > > > > ums_attach:550: T 0/0 > > > > ums_attach:551: W 0/0 > > > > ums_attach:555: B1 0/1 > > > > ums_attach:555: B2 1/1 > > > > ums_attach:555: B3 2/1 > > > > ums_attach:557: size=67, id=0 > > > > uhid1: on usbus0 > > > > > > > > What other information should I provide to help solving this problem? > > > > > > > > Sincerely, > > > > > > > > Boris Kotzev > > > > > > Could you get the USB HID descriptors dumped using: > > > > > > usbhidctl > > > > > > --HPS > > > > All information I managed to extract by using usbhidctl is below: > > > > # usbhidctl -f /dev/uhid1 -ra > > Report descriptor: > > Collection page=Consumer usage=Consumer_Control > > Input size=8 count=1 page=Consumer usage=Eject, logical range 0..255 > > End collection > > Total input size 1 bytes > > Total output size 0 bytes > > Total feature size 0 bytes > > usbhidctl: USB_SET_IMMED: Device not configured > > > > If it is not enough, will you explain to me how to use this utility? > > Hi, > > I think you have to unload ums module. Then replug the device and search > for the new uhid device. > > Can you also do: > > usbconfig -u 0 -a 2 dump_device_desc dump_curr_config_desc > > --HPS Hi, After the removal of the ums and ukbd devices from the kernel, a lot more uhid devices showed up in /dev: # dmesg | grep uhid uhid0: on usbus4 uhid1: on usbus4 uhid2: on usbus0 uhid3: on usbus0 uhid4: on usbus0 uhid5: on usbus2 uhid6: on usbus3 uhid7: on usbus3 The dump for uhid2, uhid3 and uhid4 is shown below. # usbhidctl -f /dev/uhid2 -r Report descriptor: Collection page=Generic_Desktop usage=Keyboard Input size=1 count=1 page=Keyboard usage=Keyboard_LeftControl, logical range 0..1 Input size=1 count=1 page=Keyboard usage=Keyboard_LeftShift, logical range 0..1 Input size=1 count=1 page=Keyboard usage=Keyboard_LeftAlt, logical range 0..1 Input size=1 count=1 page=Keyboard usage=Keyboard_Left_GUI, logical range 0..1 Input size=1 count=1 page=Keyboard usage=Keyboard_RightControl, logical range 0..1 Input size=1 count=1 page=Keyboard usage=Keyboard_RightShift, logical range 0..1 Input size=1 count=1 page=Keyboard usage=Keyboard_RightAlt, logical range 0..1 Input size=1 count=1 page=Keyboard usage=Keyboard_Right_GUI, logical range 0..1 Output size=1 count=1 page=LEDs usage=Num_Lock, logical range 0..1 Output size=1 count=1 page=LEDs usage=Caps_Lock, logical range 0..1 Output size=1 count=1 page=LEDs usage=Scroll_Lock, logical range 0..1 Output size=1 count=1 page=LEDs usage=Compose, logical range 0..1 Output size=1 count=1 page=LEDs usage=Kana, logical range 0..1 Input size=8 count=5 page=Keyboard usage=Reserved_(no_event_indicated), logical range 0..101 Input size=8 count=1 page=0x00ff usage=0x0003, logical range 0..101 End collection Total input size 8 bytes Total output size 1 bytes Total feature size 0 bytes # usbhidctl -f /dev/uhid3 -r Report descriptor: Collection page=Generic_Desktop usage=Mouse Total input size 0 bytes Total output size 0 bytes Total feature size 0 bytes # usbhidctl -f /dev/uhid4 -r Report descriptor: Collection page=Consumer usage=Consumer_Control Input size=8 count=1 page=Consumer usage=Eject, logical range 0..255 End collection Total input size 1 bytes Total output size 0 bytes Total feature size 0 bytes The output of usbconfig is as follows: # usbconfig -u 0 -a 2 dump_device_desc dump_curr_config_desc ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x05ac idProduct = 0x0218 bcdDevice = 0x0064 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0054 bNumInterfaces = 0x0003 bConfigurationValue = 0x0001 iConfiguration = 0x0000 bmAttributes = 0x00a0 bMaxPower = 0x0014 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x0003 Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x0d, 0x01, 0x22, 0x49, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0003 wMaxPacketSize = 0x0008 bInterval = 0x0008 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x0004 Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x59, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0040 bInterval = 0x0008 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 2 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0002 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0003 Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x14, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0084 bmAttributes = 0x0003 wMaxPacketSize = 0x0001 bInterval = 0x0008 bRefresh = 0x0000 bSynchAddress = 0x0000 Thanks! Boris Kotzev From linimon at FreeBSD.org Thu Mar 5 11:11:08 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu Mar 5 11:11:46 2009 Subject: usb/117185: [umodem] [patch] Add support for UNION interface descriptor Message-ID: <200903051911.n25JB7Fu096993@freefall.freebsd.org> Synopsis: [umodem] [patch] Add support for UNION interface descriptor Responsible-Changed-From-To: freebsd-usb->thompsa Responsible-Changed-By: linimon Responsible-Changed-When: Thu Mar 5 19:10:09 UTC 2009 Responsible-Changed-Why: Committed to p4, so let thompsa track this one for merge to current. http://www.freebsd.org/cgi/query-pr.cgi?pr=117185 From keramida at freebsd.org Thu Mar 5 13:49:09 2009 From: keramida at freebsd.org (Giorgos Keramidas) Date: Thu Mar 5 13:49:16 2009 Subject: recent usb2 regression In-Reply-To: <200903051013.19417.hselasky@c2i.net> (Hans Petter Selasky's message of "Thu, 5 Mar 2009 10:13:19 +0100") References: <87k5742wwv.fsf@kobe.laptop> <200903051013.19417.hselasky@c2i.net> Message-ID: <87eixby71r.fsf@kobe.laptop> On Thu, 5 Mar 2009 10:13:19 +0100, Hans Petter Selasky wrote: > On Thursday 05 March 2009, Giorgos Keramidas wrote: >> After my last update to March 1 sources, uhci started going into >> interrupt storm mode: >> >> $ vmstat -i >> interrupt total rate >> irq16: uhci0 745625990 169191 >> Total 764017451 173364 > Hi, > The only active interrupt is the HCH status bit. > > You can try editing /sys/dev/usb/controller/uhci.c and apply the > following patch: > > /* get acknowledge bits */ > status &= (UHCI_STS_USBINT | > UHCI_STS_USBEI | > UHCI_STS_RD | > + UHCI_STS_HCH | > UHCI_STS_HSE | > UHCI_STS_HCPE); Hi Hans, Thanks for the patch. I'll try it later today and report back :) From hselasky at c2i.net Fri Mar 6 08:18:48 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Mar 6 08:18:55 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903052109.00282.boris.kotzev@gmail.com> References: <200903041946.15105.boris.kotzev@gmail.com> <200903051431.22066.hselasky@c2i.net> <200903052109.00282.boris.kotzev@gmail.com> Message-ID: <200903061721.15975.hselasky@c2i.net> On Thursday 05 March 2009, Boris Kotzev wrote: > > On Wednesday 04 March 2009, Boris Kotzev wrote: > > > > On Wednesday 04 March 2009, Boris Kotzev wrote: > > > Thanks! > > Boris Kotzev Try editing /sys/dev/usb/input/ums.c . Change "bufsize": static const struct usb2_config ums_config[UMS_N_TRANSFER] = { [UMS_INTR_DT] = { .type = UE_INTERRUPT, .endpoint = UE_ADDR_ANY, .direction = UE_DIR_IN, .mh.flags = {.pipe_bof = 1,.short_xfer_ok = 1,}, .mh.bufsize = 0, /* use wMaxPacketSize */ .mh.callback = &ums_intr_callback, }, }; into: static const struct usb2_config ums_config[UMS_N_TRANSFER] = { [UMS_INTR_DT] = { .type = UE_INTERRUPT, .endpoint = UE_ADDR_ANY, .direction = UE_DIR_IN, .mh.flags = {.pipe_bof = 1,.short_xfer_ok = 1,}, .mh.bufsize = 128, /* use wMaxPacketSize XXX */ .mh.callback = &ums_intr_callback, }, }; This patch might make other USB mouse devices not work. It's just supposed to make the Touchpad work. Let me know the result and I will make the final patch. --HPS From boris.kotzev at gmail.com Fri Mar 6 10:21:59 2009 From: boris.kotzev at gmail.com (Boris Kotzev) Date: Fri Mar 6 10:22:06 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903061721.15975.hselasky@c2i.net> References: <200903041946.15105.boris.kotzev@gmail.com> <200903052109.00282.boris.kotzev@gmail.com> <200903061721.15975.hselasky@c2i.net> Message-ID: <200903062021.52408.boris.kotzev@gmail.com> On ????? 06 ???? 2009 18:21:15 you wrote: > On Thursday 05 March 2009, Boris Kotzev wrote: > > > On Wednesday 04 March 2009, Boris Kotzev wrote: > > > > > On Wednesday 04 March 2009, Boris Kotzev wrote: > > > > Thanks! > > > > Boris Kotzev > > Try editing /sys/dev/usb/input/ums.c . Change "bufsize": > > static const struct usb2_config ums_config[UMS_N_TRANSFER] = { > > [UMS_INTR_DT] = { > .type = UE_INTERRUPT, > .endpoint = UE_ADDR_ANY, > .direction = UE_DIR_IN, > .mh.flags = {.pipe_bof = 1,.short_xfer_ok = 1,}, > .mh.bufsize = 0, /* use wMaxPacketSize */ > .mh.callback = &ums_intr_callback, > }, > }; > > > into: > > > static const struct usb2_config ums_config[UMS_N_TRANSFER] = { > > [UMS_INTR_DT] = { > .type = UE_INTERRUPT, > .endpoint = UE_ADDR_ANY, > .direction = UE_DIR_IN, > .mh.flags = {.pipe_bof = 1,.short_xfer_ok = 1,}, > .mh.bufsize = 128, /* use wMaxPacketSize XXX */ > .mh.callback = &ums_intr_callback, > }, > }; > > This patch might make other USB mouse devices not work. It's just supposed > to make the Touchpad work. Let me know the result and I will make the final > patch. > > --HPS Hi Hans, Changing the bfsz from 0 to 128 in ums.c did not solve the problem. The touchpad continues to respond to input in the same weird way. Best regards, Boris Kotzev From hselasky at c2i.net Fri Mar 6 10:57:55 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Mar 6 10:58:01 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903062021.52408.boris.kotzev@gmail.com> References: <200903041946.15105.boris.kotzev@gmail.com> <200903061721.15975.hselasky@c2i.net> <200903062021.52408.boris.kotzev@gmail.com> Message-ID: <200903062000.22447.hselasky@c2i.net> On Friday 06 March 2009, Boris Kotzev wrote: > > Hi Hans, > > Changing the bfsz from 0 to 128 in ums.c did not solve the problem. The > touchpad continues to respond to input in the same weird way. > Hi Boris, Please dump the HID descriptor of your interface 1 of the apple keyboard like this: usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 1 0x100 Parameters after u and a must be correct. You can also dump interface #0: usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 0 0x100 And the other interfaces if you want. --HPS From boris.kotzev at gmail.com Fri Mar 6 12:05:09 2009 From: boris.kotzev at gmail.com (Boris Kotzev) Date: Fri Mar 6 12:05:15 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903062000.22447.hselasky@c2i.net> References: <200903041946.15105.boris.kotzev@gmail.com> <200903062021.52408.boris.kotzev@gmail.com> <200903062000.22447.hselasky@c2i.net> Message-ID: <200903062205.04687.boris.kotzev@gmail.com> On ????? 06 ???? 2009 21:00:22 you wrote: > On Friday 06 March 2009, Boris Kotzev wrote: > > Hi Hans, > > > > Changing the bfsz from 0 to 128 in ums.c did not solve the problem. The > > touchpad continues to respond to input in the same weird way. > > Hi Boris, > > Please dump the HID descriptor of your interface 1 of the apple keyboard > like this: > > usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 1 0x100 > > Parameters after u and a must be correct. You can also dump interface #0: > > usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 0 0x100 > > And the other interfaces if you want. > > --HPS Hi Hans, I guess that the parameters after u and a should be 0 and 2 correspondingly: # usbconfig -u 0 -a 2 list ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Dump of Interface 1: usbconfig -u 0 -a 2 do_request 0x81 0x06 0x2200 1 0x100 REQUEST = <0x05 0x01 0x09 0x02 0xa1 0x01 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x03 0x15 0x00 0x25 0x01 0x85 0x02 0x95 0x03 0x75 0x01 0x81 0x02 0x95 0x01 0x75 0x05 0x81 0x01 0x05 0x01 0x09 0x30 0x09 0x31 0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x02 0x81 0x06 0xc0 0xc0 0x05 0xff 0x09 0x01 0xa1 0x00 0x09 0x02 0x15 0x01 0x25 0x41 0x35 0x00 0x45 0xff 0x85 0x05 0x75 0x08 0x95 0x3f 0x81 0x00 0x09 0x04 0x15 0x80 0x25 0x7f 0x75 0x08 0x95 0x10 0xb1 0x02 0xc0><)%uu01%u%A5Eu?%u> Dump of Interface 0: # usbconfig -u 0 -a 2 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x01 0x09 0x06 0xa1 0x01 0x05 0x07 0x19 0xe0 0x29 0xe7 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x08 0x81 0x02 0x95 0x01 0x75 0x08 0x81 0x01 0x95 0x05 0x75 0x01 0x05 0x08 0x19 0x01 0x29 0x05 0x91 0x02 0x95 0x01 0x75 0x03 0x91 0x01 0x95 0x05 0x75 0x08 0x15 0x00 0x25 0x65 0x05 0x07 0x19 0x00 0x29 0x65 0x81 0x00 0x05 0xff 0x09 0x03 0x75 0x08 0x95 0x01 0x81 0x02 0xc0><)%uuu)uu%e)eu> Dump of Interface 2: usbconfig -u 0 -a 2 do_request 0x81 0x06 0x2200 2 0x100 REQUEST = <0x05 0x0c 0x09 0x01 0xa1 0x01 0x75 0x08 0x95 0x01 0x09 0xb8 0x15 0x00 0x26 0xff 0x00 0x81 0x02 0xc0> Best regards, Boris Kotzev From admin.dragos at gmail.com Sun Mar 8 01:28:51 2009 From: admin.dragos at gmail.com (Dragos) Date: Sun Mar 8 01:28:57 2009 Subject: Can't work out which disk we are booting from Message-ID: <49B38863.2090507@gmail.com> Hi, I have installed freebsd 7.1 on a 8GB usb flash drive. Now, it seems that the freebsd loader is unable to identify the usb disk where is booting from(da0s1a). The loader runs fine from the stick but gets confused on the drive it runs from, and the kernel it's not loaded. Here is what the loader prints out: [...] Bios drive A: is disk0 [...] Can't work out which disk we are booting from. Guessed BIOS device 0x80 not found by probes, defaulting to disk0: can't load 'kernel' I installed grub too and grub is loading the freebsd loader just fine, but the freebsd loader still get confused. Unfortunately I wasn't able to load the kernel (/boot/kernel/kernel) directly from grub. From mmakonnen at gmail.com Sun Mar 8 03:02:28 2009 From: mmakonnen at gmail.com (Mike Makonnen) Date: Sun Mar 8 03:02:35 2009 Subject: The rc.d mess strikes back In-Reply-To: <20090304164953.GB1209@lor.one-eyed-alien.net> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> <20090302.181513.1973603215.imp@bsdimp.com> <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> <20090303180307.GA11134@lor.one-eyed-alien.net> <584bfc3f0903032212x25831c5bi35d9b637c1896e1d@mail.gmail.com> <7d6fde3d0903040004y1fcbb086i355cd0113717620b@mail.gmail.com> <20090304164953.GB1209@lor.one-eyed-alien.net> Message-ID: <49B397A4.8090508@gmail.com> Brooks Davis wrote: > On Wed, Mar 04, 2009 at 12:04:06AM -0800, Garrett Cooper wrote: >> On Tue, Mar 3, 2009 at 10:12 PM, Mike Telahun Makonnen >> wrote: >>> On Tue, Mar 3, 2009 at 9:03 PM, Brooks Davis wrote: >>>> I don't have much time to debug this, but I've not had problems with >>>> services starting too early on the systems I've been running with async >>>> dhcp. ?If there is a problem with the wait process we need to actually >>>> debug it. ?If the wait for a route/running interface isn't sufficent we >>>> should try to figure out what is. ?Synchronous dhcp sucks and yeilds >>>> justifed user complaints so it would be nice to kill it off. ?I switched >>>> the default because it worked for me and I hoped that people would help >>>> find and fix edge cases. >>> Can you elaborate why synchronous DHCP sucks ? >> The only reason I could see is bringup time. Am I correct in this assumption? > > If you use synchronous DHCP then every interface that wants to try to > get a DHCP address if it has link needs to run through the full link > timeout at boot. On a laptop this is annoying and generally pointless. Ok, I just turned synchronous dhclient on locally and I see what you mean. > The changes to defaultroute to wait for a default route to be set mean > that you consolidate the wait in one location and you don't waste time > starting dhclient on interfaces until a link exists (or an association > is made for wlan devices). OK, so that means that it's not just waiting for the default route, but it's also waiting for the link on any DHCP interfaces to come up as well. That's what confused me. When it's plugged in my NIC's link is always up by the time rc.d gets to the default route, so I didn't see the point in waiting the extra 30sec when it wasn't plugged in. The comments also seemed to imply that we should be checking whether the link is up. Anyways, given that synchronous dhclient re-introduces the same problem I was trying to fix in the first place I'll just back the whole thing out until we can come up with a better fix. Do you mind if I change the timeout to 15sec. (instead of 30s)? > There may well be something better to wait > or a need for a longer timeout in some environments. It's also quite > possible that we have an ordering problem and need to move some more > things after defaultroute or move the checks to a different location. > > -- Brooks Cheers. -- Mike Makonnen | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc mtm @ FreeBSD.Org | AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 FreeBSD | http://www.freebsd.org From kutizs at t-online.hu Sun Mar 8 03:26:05 2009 From: kutizs at t-online.hu (Zsolt =?ISO-8859-2?Q?K=FAti?=) Date: Sun Mar 8 03:26:11 2009 Subject: pendrive recognizing problem Message-ID: <20090308110808.3c97edfa@brain> Hello, First of all, please bear with me were this not the appropriate list for my question. I searched high and low for a clue to no avail. One of my pendrives (Kingston Datatraveler 2G) is recognized if no X is run before. If, however, an X session is already started all I see on the console after some time: uhub5: device problem (TIMEOUT), disabling port 5. (After this an old LEXAR pendrive works like charm on the same USB port.) I tried to run X without hald. Does not help. While this is certainly X related, I cant see why should this has an effect on a low level, device detection part of the OS. I appreciate any suggestion where to look for a solution. Thanks! Zsolt ps.: Please CC, as I am not on the list. From david.guedj at gmail.com Sun Mar 8 05:10:05 2009 From: david.guedj at gmail.com (David Guedj) Date: Sun Mar 8 05:10:13 2009 Subject: usb/126848: [usb]: USB Keyboard hangs during Installation Message-ID: <200903081210.n28CA4Xt037780@freefall.freebsd.org> The following reply was made to PR usb/126848; it has been noted by GNATS. From: David Guedj To: bug-followup@FreeBSD.org, f0ng@hotmail.com Cc: Subject: Re: usb/126848: [usb]: USB Keyboard hangs during Installation Date: Sun, 08 Mar 2009 12:44:32 +0100 I'm facing the exact same problem with 7.1 installation CD. USB Keyboard stop working as soon as the kernel loads. The mainboard is a Gigabyte GA-EP35C-DS3R. The problem is known to happen frequently on Gigabyte motherboards. I've tried myriad Linux distribution and none had this kind of problem. I've no other fix than unplug/plug the keyboard to make it working again. From brooks at freebsd.org Sun Mar 8 11:10:54 2009 From: brooks at freebsd.org (Brooks Davis) Date: Sun Mar 8 11:11:06 2009 Subject: The rc.d mess strikes back In-Reply-To: <49B397A4.8090508@gmail.com> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> <20090302.181513.1973603215.imp@bsdimp.com> <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> <20090303180307.GA11134@lor.one-eyed-alien.net> <584bfc3f0903032212x25831c5bi35d9b637c1896e1d@mail.gmail.com> <7d6fde3d0903040004y1fcbb086i355cd0113717620b@mail.gmail.com> <20090304164953.GB1209@lor.one-eyed-alien.net> <49B397A4.8090508@gmail.com> Message-ID: <20090308180934.GA9147@lor.one-eyed-alien.net> On Sun, Mar 08, 2009 at 01:02:12PM +0300, Mike Makonnen wrote: > Brooks Davis wrote: >> On Wed, Mar 04, 2009 at 12:04:06AM -0800, Garrett Cooper wrote: >>> On Tue, Mar 3, 2009 at 10:12 PM, Mike Telahun Makonnen >>> wrote: >>>> On Tue, Mar 3, 2009 at 9:03 PM, Brooks Davis wrote: >>>>> I don't have much time to debug this, but I've not had problems with >>>>> services starting too early on the systems I've been running with async >>>>> dhcp. ?If there is a problem with the wait process we need to actually >>>>> debug it. ?If the wait for a route/running interface isn't sufficent we >>>>> should try to figure out what is. ?Synchronous dhcp sucks and yeilds >>>>> justifed user complaints so it would be nice to kill it off. ?I switched >>>>> the default because it worked for me and I hoped that people would help >>>>> find and fix edge cases. >>>> Can you elaborate why synchronous DHCP sucks ? >>> The only reason I could see is bringup time. Am I correct in this assumption? >> >> If you use synchronous DHCP then every interface that wants to try to >> get a DHCP address if it has link needs to run through the full link >> timeout at boot. On a laptop this is annoying and generally pointless. > > Ok, I just turned synchronous dhclient on locally and I see what you > mean. > >> The changes to defaultroute to wait for a default route to be set mean >> that you consolidate the wait in one location and you don't waste time >> starting dhclient on interfaces until a link exists (or an association >> is made for wlan devices). > > OK, so that means that it's not just waiting for the default route, but > it's also waiting for the link on any DHCP interfaces to come up as > well. That's what confused me. When it's plugged in my NIC's link is > always up by the time rc.d gets to the default route, so I didn't see > the point in waiting the extra 30sec when it wasn't plugged in. The > comments also seemed to imply that we should be checking whether the > link is up. > > Anyways, given that synchronous dhclient re-introduces the same problem > I was trying to fix in the first place I'll just back the whole thing out > until we can come up with a better fix. Do you mind if I change the timeout > to 15sec. (instead of 30s)? 15 is probably a bit short in practice for wpa networks. Someone a while back suggested that there's some reason (perhaps spanning tree, but I can't remember) why it it should be closer to 50sec for maximum reliability. One thing I've thought of adding is changing the sleeps to "read -t1", checking for a non-timeout result and adding "Press return to skip". Another option would be for each interface to set a minimum timeout based on it's type such as having WPA interfaces set it to 30 and others set it to 15. -- Brooks -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090308/ccccd429/attachment.pgp From sam at freebsd.org Sun Mar 8 11:39:34 2009 From: sam at freebsd.org (Sam Leffler) Date: Sun Mar 8 11:39:41 2009 Subject: The rc.d mess strikes back In-Reply-To: <20090308180934.GA9147@lor.one-eyed-alien.net> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> <20090302.181513.1973603215.imp@bsdimp.com> <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> <20090303180307.GA11134@lor.one-eyed-alien.net> <584bfc3f0903032212x25831c5bi35d9b637c1896e1d@mail.gmail.com> <7d6fde3d0903040004y1fcbb086i355cd0113717620b@mail.gmail.com> <20090304164953.GB1209@lor.one-eyed-alien.net> <49B397A4.8090508@gmail.com> <20090308180934.GA9147@lor.one-eyed-alien.net> Message-ID: <49B410E0.4030803@freebsd.org> Brooks Davis wrote: > On Sun, Mar 08, 2009 at 01:02:12PM +0300, Mike Makonnen wrote: > >> Brooks Davis wrote: >> >>> On Wed, Mar 04, 2009 at 12:04:06AM -0800, Garrett Cooper wrote: >>> >>>> On Tue, Mar 3, 2009 at 10:12 PM, Mike Telahun Makonnen >>>> wrote: >>>> >>>>> On Tue, Mar 3, 2009 at 9:03 PM, Brooks Davis wrote: >>>>> >>>>>> I don't have much time to debug this, but I've not had problems with >>>>>> services starting too early on the systems I've been running with async >>>>>> dhcp. ?If there is a problem with the wait process we need to actually >>>>>> debug it. ?If the wait for a route/running interface isn't sufficent we >>>>>> should try to figure out what is. ?Synchronous dhcp sucks and yeilds >>>>>> justifed user complaints so it would be nice to kill it off. ?I switched >>>>>> the default because it worked for me and I hoped that people would help >>>>>> find and fix edge cases. >>>>>> >>>>> Can you elaborate why synchronous DHCP sucks ? >>>>> >>>> The only reason I could see is bringup time. Am I correct in this assumption? >>>> >>> If you use synchronous DHCP then every interface that wants to try to >>> get a DHCP address if it has link needs to run through the full link >>> timeout at boot. On a laptop this is annoying and generally pointless. >>> >> Ok, I just turned synchronous dhclient on locally and I see what you >> mean. >> >> >>> The changes to defaultroute to wait for a default route to be set mean >>> that you consolidate the wait in one location and you don't waste time >>> starting dhclient on interfaces until a link exists (or an association >>> is made for wlan devices). >>> >> OK, so that means that it's not just waiting for the default route, but >> it's also waiting for the link on any DHCP interfaces to come up as >> well. That's what confused me. When it's plugged in my NIC's link is >> always up by the time rc.d gets to the default route, so I didn't see >> the point in waiting the extra 30sec when it wasn't plugged in. The >> comments also seemed to imply that we should be checking whether the >> link is up. >> >> Anyways, given that synchronous dhclient re-introduces the same problem >> I was trying to fix in the first place I'll just back the whole thing out >> until we can come up with a better fix. Do you mind if I change the timeout >> to 15sec. (instead of 30s)? >> > > 15 is probably a bit short in practice for wpa networks. Someone a > while back suggested that there's some reason (perhaps spanning tree, > but I can't remember) why it it should be closer to 50sec for maximum > reliability. One thing I've thought of adding is changing the sleeps to > "read -t1", checking for a non-timeout result and adding "Press return > to skip". Another option would be for each interface to set a minimum > timeout based on it's type such as having WPA interfaces set it to 30 > and others set it to 15. > wpa is typically not the issue unless wpa-eapol is involved (in which case you need to negotiate with a backend authentication server). wpa typically takes <100ms to handshake and plumb keys once you have an association. The more time consuming aspects of setting up a wireless connection are scanning (if dual-band and not done intelligently) and how fast the dhcp server is (I have observed 15-30 sec lag on some large corporate nets). One thing I don't understand is why we poll at all given that we can listen to the routing socket and figure out exactly what we need. This would require a new app but that's easy (just mod something like wlanwatch or route). We'd still need to decide how to handle the timeout and/or how to deal with interrupting the process. Sam From imp at bsdimp.com Sun Mar 8 12:06:49 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 8 12:06:56 2009 Subject: Latest kernel breaks scanner Message-ID: <20090308.130659.-1303465250.imp@bsdimp.com> Sigh. Had a working system from Mar 4th. Upgraded now it doesn't work. Scanner not found by xsane. Warner From thompsa at FreeBSD.org Sun Mar 8 13:32:03 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Mar 8 13:32:08 2009 Subject: Latest kernel breaks scanner In-Reply-To: <20090308.130659.-1303465250.imp@bsdimp.com> References: <20090308.130659.-1303465250.imp@bsdimp.com> Message-ID: <20090308203157.GC30672@citylink.fud.org.nz> On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: > Sigh. Had a working system from Mar 4th. Upgraded now it doesn't > work. Scanner not found by xsane. Are you sure its not this? 20090227: The /dev handling for the new USB stack has changed, a buildworld/installworld is required for libusb20. Does usbconfig list your devices? Andrew From hselasky at c2i.net Sun Mar 8 13:46:53 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Mar 8 13:46:59 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903062205.04687.boris.kotzev@gmail.com> References: <200903041946.15105.boris.kotzev@gmail.com> <200903062000.22447.hselasky@c2i.net> <200903062205.04687.boris.kotzev@gmail.com> Message-ID: <200903082149.21753.hselasky@c2i.net> Hi Boris, Based on the HID descriptor dump you sent I've found and corrected a couple of bugs in the FreeBSD kernel HID parser. 1) cvsup to latest current. 2) replace the two patched files with the version from USB P4 3) compile new kernel and modules If it doesn't work, then turn on ums debugging before plugging the devices and send me the result! Patch: http://perforce.freebsd.org/chv.cgi?CH=158868 --HPS From imp at bsdimp.com Sun Mar 8 14:43:03 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 8 14:43:09 2009 Subject: Latest kernel breaks scanner In-Reply-To: <20090308.130659.-1303465250.imp@bsdimp.com> References: <20090308.130659.-1303465250.imp@bsdimp.com> Message-ID: <20090308.154037.1649769695.imp@bsdimp.com> In message: <20090308.130659.-1303465250.imp@bsdimp.com> "M. Warner Losh" writes: : Sigh. Had a working system from Mar 4th. Upgraded now it doesn't : work. Scanner not found by xsane. Most likely userland, since the kernel that it worked on last week doesn't work now. Warner : Warner : _______________________________________________ : 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" : : From imp at bsdimp.com Sun Mar 8 14:46:35 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 8 14:46:40 2009 Subject: Latest kernel breaks scanner In-Reply-To: <20090308203157.GC30672@citylink.fud.org.nz> References: <20090308.130659.-1303465250.imp@bsdimp.com> <20090308203157.GC30672@citylink.fud.org.nz> Message-ID: <20090308.154353.-1350498283.imp@bsdimp.com> In message: <20090308203157.GC30672@citylink.fud.org.nz> Andrew Thompson writes: : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: : > Sigh. Had a working system from Mar 4th. Upgraded now it doesn't : > work. Scanner not found by xsane. : : Are you sure its not this? : : 20090227: : The /dev handling for the new USB stack has changed, a : buildworld/installworld is required for libusb20. Yes. Been there, done that. Also have the libmap.conf changes in place for old binaries that had worked for months before that. xsane used to just work in this setup, but now fails. Looks like some kind of mismatch in the ABI: found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0 it used to print a real product/vendor there... : Does usbconfig list your devices? Yes. Warner From thompsa at FreeBSD.org Sun Mar 8 14:56:11 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Mar 8 14:56:17 2009 Subject: Latest kernel breaks scanner In-Reply-To: <20090308.154353.-1350498283.imp@bsdimp.com> References: <20090308.130659.-1303465250.imp@bsdimp.com> <20090308203157.GC30672@citylink.fud.org.nz> <20090308.154353.-1350498283.imp@bsdimp.com> Message-ID: <20090308215604.GD30672@citylink.fud.org.nz> On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: > In message: <20090308203157.GC30672@citylink.fud.org.nz> > Andrew Thompson writes: > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: > : > Sigh. Had a working system from Mar 4th. Upgraded now it doesn't > : > work. Scanner not found by xsane. > : > : Are you sure its not this? > : > : 20090227: > : The /dev handling for the new USB stack has changed, a > : buildworld/installworld is required for libusb20. > > Yes. Been there, done that. Also have the libmap.conf changes in > place for old binaries that had worked for months before that. xsane > used to just work in this setup, but now fails. Looks like some kind > of mismatch in the ABI: > > found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0 Not sure what would have caused that. Before you spend too much time on this you may want to note that the integration patches for libusb into the ports build will likely be committed tomorrow. This will bump the port numbers so the affected ports rebuild, hopefully sane with DTRT after that. Andrew From conall at gmail.com Sun Mar 8 15:37:55 2009 From: conall at gmail.com (Conall O'Brien) Date: Sun Mar 8 15:38:02 2009 Subject: 1wire sensor with ugen... Message-ID: <6721d4100903081516v19e46090if41d373b82b476c3@mail.gmail.com> Hello, I've a 1wire USB device with a temperature sensor which I'm trying to set up. My FreeBSD 7.x (RELENG_7) system detects it on boot and IDs it correctly: ugen1: on uhub0 which results in /dev/ugen1 , /dev/ugen1.1 and /dev/ugen1.2 devices all being created. The sensor should be accessible as a straight serial device (9600 baud, etc), but my attempts using pyserial aren't working: >>> s = serial.Serial('/dev/ugen1', 9600, timeout=1) >>> s.read(10) Traceback (most recent call last): File "", line 1, in File "build/bdist.freebsd-7.1-STABLE-amd64/egg/serial/serialposix.py", line 344, in read serial.serialutil.SerialException: Port not open >>> s.isOpen() False I don't have much experience working directly with ugen devices, so any advice to get this working would be appreciated. Thanks! -- Conall O'Brien From boris.kotzev at gmail.com Sun Mar 8 17:05:06 2009 From: boris.kotzev at gmail.com (Boris Kotzev) Date: Sun Mar 8 17:05:12 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903082149.21753.hselasky@c2i.net> References: <200903041946.15105.boris.kotzev@gmail.com> <200903062205.04687.boris.kotzev@gmail.com> <200903082149.21753.hselasky@c2i.net> Message-ID: <200903090205.01119.boris.kotzev@gmail.com> > Hi Boris, > > Based on the HID descriptor dump you sent I've found and corrected a couple > of bugs in the FreeBSD kernel HID parser. > > 1) cvsup to latest current. > 2) replace the two patched files with the version from USB P4 > 3) compile new kernel and modules > > If it doesn't work, then turn on ums debugging before plugging the devices > and send me the result! > > Patch: > > http://perforce.freebsd.org/chv.cgi?CH=158868 > > --HPS Hi Hans, I performed steps 1, 2 and 3 (in step 2 downloaded and then replaced the files usb_hid.c and usb_hid.h.) - there is no change in the behavior of the touchpad. It still does not function properly. Resetting the device with "hw.usb2.ums.debug" set to "1" produces the following output in dmesg : usbconfig -u 0 -a 2 reset ukbd0: at uhub0, port 2, addr 2 (disconnected) ums1: at uhub0, port 2, addr 2 (disconnected) ums_detach:608: sc=0xffffff00017c3400 uhid1: at uhub0, port 2, addr 2 (disconnected) ukbd0: on usbus0 kbd1 at ukbd0 ums1: on usbus0 ums1: 3 buttons and [XY] coordinates ums_attach:546: sc=0xffffff000d06a400 ums_attach:547: X 8/8 ums_attach:548: Y 16/8 ums_attach:549: Z 0/0 ums_attach:550: T 0/0 ums_attach:551: W 0/0 ums_attach:555: B1 0/1 ums_attach:555: B2 1/1 ums_attach:555: B3 2/1 ums_attach:557: size=64, id=0 uhid1: on usbus0 Best regards, Boris Kotzev From hselasky at c2i.net Mon Mar 9 00:49:26 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Mar 9 00:49:36 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903090205.01119.boris.kotzev@gmail.com> References: <200903041946.15105.boris.kotzev@gmail.com> <200903082149.21753.hselasky@c2i.net> <200903090205.01119.boris.kotzev@gmail.com> Message-ID: <200903090851.53432.hselasky@c2i.net> On Monday 09 March 2009, Boris Kotzev wrote: > > Hi Boris, > > > > Based on the HID descriptor dump you sent I've found and corrected a > > couple of bugs in the FreeBSD kernel HID parser. > > > > 1) cvsup to latest current. > > 2) replace the two patched files with the version from USB P4 > > 3) compile new kernel and modules > > > > If it doesn't work, then turn on ums debugging before plugging the > > devices and send me the result! > > > > Patch: > > > > http://perforce.freebsd.org/chv.cgi?CH=158868 > > > > --HPS > > Hi Hans, > > I performed steps 1, 2 and 3 (in step 2 downloaded and then replaced the > files usb_hid.c and usb_hid.h.) - there is no change in the behavior of the > touchpad. It still does not function properly. > > Resetting the device with "hw.usb2.ums.debug" set to "1" produces the > following output in dmesg : > > usbconfig -u 0 -a 2 reset > > ukbd0: at uhub0, port 2, addr 2 (disconnected) > ums1: at uhub0, port 2, addr 2 (disconnected) > ums_detach:608: sc=0xffffff00017c3400 > uhid1: at uhub0, port 2, addr 2 (disconnected) > ukbd0: on usbus0 > kbd1 at ukbd0 > ums1: on usbus0 > ums1: 3 buttons and [XY] coordinates > ums_attach:546: sc=0xffffff000d06a400 > ums_attach:547: X 8/8 > ums_attach:548: Y 16/8 > ums_attach:549: Z 0/0 > ums_attach:550: T 0/0 > ums_attach:551: W 0/0 > ums_attach:555: B1 0/1 > ums_attach:555: B2 1/1 > ums_attach:555: B3 2/1 > ums_attach:557: size=64, id=0 > uhid1: on usbus0 > Can you get me dmesg with ums debugging enabled when you move the cursor? What does: ps auxw |grep moused output ? --HPS From hselasky at c2i.net Mon Mar 9 04:31:28 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Mar 9 04:31:37 2009 Subject: Latest kernel breaks scanner In-Reply-To: <20090308215604.GD30672@citylink.fud.org.nz> References: <20090308.130659.-1303465250.imp@bsdimp.com> <20090308.154353.-1350498283.imp@bsdimp.com> <20090308215604.GD30672@citylink.fud.org.nz> Message-ID: <200903091233.55089.hselasky@c2i.net> On Sunday 08 March 2009, Andrew Thompson wrote: > On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: > > In message: <20090308203157.GC30672@citylink.fud.org.nz> > > > > Andrew Thompson writes: > > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: > > : > Sigh. Had a working system from Mar 4th. Upgraded now it doesn't > > : > work. Scanner not found by xsane. > > : > > : Are you sure its not this? > > : > > : 20090227: > > : The /dev handling for the new USB stack has changed, a > > : buildworld/installworld is required for libusb20. > > > > Yes. Been there, done that. Also have the libmap.conf changes in > > place for old binaries that had worked for months before that. xsane > > used to just work in this setup, but now fails. Looks like some kind > > of mismatch in the ABI: > > > > found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0 > > Not sure what would have caused that. Before you spend too much time on > this you may want to note that the integration patches for libusb into > the ports build will likely be committed tomorrow. This will bump the > port numbers so the affected ports rebuild, hopefully sane with DTRT > after that. > Maybe you need to chown or rm /dev/uscanner0 to enforce use of libusb backend? --HPS From hselasky at c2i.net Mon Mar 9 04:32:50 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Mar 9 04:32:56 2009 Subject: 1wire sensor with ugen... In-Reply-To: <6721d4100903081516v19e46090if41d373b82b476c3@mail.gmail.com> References: <6721d4100903081516v19e46090if41d373b82b476c3@mail.gmail.com> Message-ID: <200903091235.19268.hselasky@c2i.net> On Sunday 08 March 2009, Conall O'Brien wrote: > Hello, > > I've a 1wire USB device with a temperature sensor which I'm trying to set > up. My FreeBSD 7.x (RELENG_7) system detects it on boot and IDs it > correctly: > > ugen1: on uhub0 > > which results in /dev/ugen1 , /dev/ugen1.1 and /dev/ugen1.2 devices all > being created. > > > The sensor should be accessible as a straight serial device (9600 baud, > > etc), but my attempts using pyserial aren't working: > >>> s = serial.Serial('/dev/ugen1', 9600, timeout=1) > >>> s.read(10) > > Traceback (most recent call last): > File "", line 1, in > File "build/bdist.freebsd-7.1-STABLE-amd64/egg/serial/serialposix.py", > line 344, in read > serial.serialutil.SerialException: Port not open > > >>> s.isOpen() > > False > > > I don't have much experience working directly with ugen devices, so any > advice to get this working would be appreciated. > > > Thanks! Hi, Ugen devices do not support setting the baud rate ... You need to add your device to the "ugensa" driver or make it look like a generic "umodem" device. --HPS From boris.kotzev at gmail.com Mon Mar 9 04:45:06 2009 From: boris.kotzev at gmail.com (Boris Kotzev) Date: Mon Mar 9 04:45:13 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903090851.53432.hselasky@c2i.net> References: <200903041946.15105.boris.kotzev@gmail.com> <200903090205.01119.boris.kotzev@gmail.com> <200903090851.53432.hselasky@c2i.net> Message-ID: <200903091345.00743.boris.kotzev@gmail.com> > > Can you get me dmesg with ums debugging enabled when you move the cursor? > > What does: > > ps auxw |grep moused > > output ? > > --HPS Hi Hans, With "hw.usb2.ums.debug" set to "5" the touchpad attaches as follows: ukbd0: on usbus0 kbd1 at ukbd0 ums1: on usbus0 ums1: 3 buttons and [XY] coordinates ums_attach:546: sc=0xffffff000e020c00 ums_attach:547: X 8/8 ums_attach:548: Y 16/8 ums_attach:549: Z 0/0 ums_attach:550: T 0/0 ums_attach:551: W 0/0 ums_attach:555: B1 0/1 ums_attach:555: B2 1/1 ums_attach:555: B3 2/1 ums_attach:557: size=64, id=0 uhid1: on usbus0 ums_open:701: ums_open:701: ums_ioctl:738: ums_ioctl:738: ums_ioctl:738: ums_ioctl:738: ums_ioctl:738: After raising the debug level to "6" the following messages begin scrolling on the console on end (without any input to the touchpad): ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff000e020c00 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 In contrast, the external usb mouse does not produce any dmesg output at the same debug level until moved. Moving the cursor results in the following dmesg output (hw.usb2.ums.debug=6): ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f9 00 00 00 00 00 ums_intr_callback:264: x:0 y:7 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 fa ff 00 00 00 00 ums_intr_callback:264: x:0 y:6 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f9 00 00 00 00 00 ums_intr_callback:264: x:0 y:7 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f8 00 00 00 00 00 ums_intr_callback:264: x:0 y:8 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f8 00 00 00 00 00 ums_intr_callback:264: x:0 y:8 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f8 00 00 00 00 00 ums_intr_callback:264: x:0 y:8 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f7 00 00 00 00 00 ums_intr_callback:264: x:0 y:9 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f6 00 00 00 00 00 ums_intr_callback:264: x:0 y:10 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f7 00 00 00 00 00 ums_intr_callback:264: x:0 y:9 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f6 00 00 00 00 00 ums_intr_callback:264: x:0 y:10 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f6 00 00 00 00 00 ums_intr_callback:264: x:0 y:10 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f6 00 00 00 00 00 ums_intr_callback:264: x:0 y:10 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f6 ff 00 00 00 00 ums_intr_callback:264: x:0 y:10 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f5 00 00 00 00 00 ums_intr_callback:264: x:0 y:11 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f5 00 00 00 00 00 ums_intr_callback:264: x:0 y:11 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f6 ff 00 00 00 00 ums_intr_callback:264: x:0 y:10 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f7 ff 00 00 00 00 ums_intr_callback:264: x:0 y:9 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f5 00 00 00 00 00 ums_intr_callback:264: x:0 y:11 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f6 ff 00 00 00 00 ums_intr_callback:264: x:0 y:10 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f6 ff 00 00 00 00 ums_intr_callback:264: x:0 y:10 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f7 ff 00 00 00 00 ums_intr_callback:264: x:0 y:9 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f8 fe 00 00 00 00 ums_intr_callback:264: x:0 y:8 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f8 ff 00 00 00 00 ums_intr_callback:264: x:0 y:8 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f8 fe 00 00 00 00 ums_intr_callback:264: x:0 y:8 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 f9 ff 00 00 00 00 ums_intr_callback:264: x:0 y:7 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 fa ff 00 00 00 00 ums_intr_callback:264: x:0 y:6 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 fb ff 00 00 00 00 ums_intr_callback:264: x:0 y:5 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 fb ff 00 00 00 00 ums_intr_callback:264: x:0 y:5 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 fc ff 00 00 00 00 ums_intr_callback:264: x:0 y:4 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 fd ff 00 00 00 00 ums_intr_callback:264: x:0 y:3 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 fd ff 00 00 00 00 ums_intr_callback:264: x:0 y:3 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 fe 00 00 00 00 00 ums_intr_callback:264: x:0 y:2 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 00 ff 00 00 00 00 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 02 00 00 00 00 00 ums_intr_callback:264: x:0 y:-2 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 03 01 00 00 00 00 ums_intr_callback:264: x:0 y:-3 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 04 00 00 00 00 00 ums_intr_callback:264: x:0 y:-4 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 05 01 00 00 00 00 ums_intr_callback:264: x:0 y:-5 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 06 01 00 00 00 00 ums_intr_callback:264: x:0 y:-6 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 07 01 00 00 00 00 ums_intr_callback:264: x:0 y:-7 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 08 01 00 00 00 00 ums_intr_callback:264: x:0 y:-8 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 09 01 00 00 00 00 ums_intr_callback:264: x:0 y:-9 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 09 02 00 00 00 00 ums_intr_callback:264: x:0 y:-9 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0a 01 00 00 00 00 ums_intr_callback:264: x:0 y:-10 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0b 02 00 00 00 00 ums_intr_callback:264: x:0 y:-11 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0b 02 00 00 00 00 ums_intr_callback:264: x:0 y:-11 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0b 02 00 00 00 00 ums_intr_callback:264: x:0 y:-11 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0c 03 00 00 00 00 ums_intr_callback:264: x:0 y:-12 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0c 04 00 00 00 00 ums_intr_callback:264: x:0 y:-12 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0d 03 00 00 00 00 ums_intr_callback:264: x:0 y:-13 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0d 03 00 00 00 00 ums_intr_callback:264: x:0 y:-13 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0c 03 00 00 00 00 ums_intr_callback:264: x:0 y:-12 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0c 03 00 00 00 00 ums_intr_callback:264: x:0 y:-12 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0b 03 00 00 00 00 ums_intr_callback:264: x:0 y:-11 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0b 02 00 00 00 00 ums_intr_callback:264: x:0 y:-11 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 0a 02 00 00 00 00 ums_intr_callback:264: x:0 y:-10 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 09 01 00 00 00 00 ums_intr_callback:264: x:0 y:-9 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 08 02 00 00 00 00 ums_intr_callback:264: x:0 y:-8 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 07 01 00 00 00 00 ums_intr_callback:264: x:0 y:-7 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 06 02 00 00 00 00 ums_intr_callback:264: x:0 y:-6 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 05 01 00 00 00 00 ums_intr_callback:264: x:0 y:-5 z:0 t:0 w:0 buttons:0x00000001 ums_intr_callback:174: sc=0xffffff00060c9000 actlen=4 ums_intr_callback:191: data = 02 00 00 00 00 00 00 00 All the time moused was running on the ums1 port only: ps auxw |grep moused root 1537 0,0 0,1 6968 1100 ?? Is 1:06pm 0:00,00 /usr/sbin/moused -p /dev/ums1 -t auto -I /var/run/moused.ums1.pi root 1560 0,0 0,1 8016 1232 1 S+ 1:07pm 0:00,00 grep moused I also killed all instances of moused and then started X with Option "Device" "/dev/ums1" in xorg.conf. The behavior of the touchpad was the same as when running under the moused. Best regards, Boris Kotzev From hselasky at c2i.net Mon Mar 9 05:31:28 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Mar 9 05:31:39 2009 Subject: Latest kernel breaks scanner In-Reply-To: <20090308215604.GD30672@citylink.fud.org.nz> References: <20090308.130659.-1303465250.imp@bsdimp.com> <20090308.154353.-1350498283.imp@bsdimp.com> <20090308215604.GD30672@citylink.fud.org.nz> Message-ID: <200903091233.55089.hselasky@c2i.net> On Sunday 08 March 2009, Andrew Thompson wrote: > On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: > > In message: <20090308203157.GC30672@citylink.fud.org.nz> > > > > Andrew Thompson writes: > > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: > > : > Sigh. Had a working system from Mar 4th. Upgraded now it doesn't > > : > work. Scanner not found by xsane. > > : > > : Are you sure its not this? > > : > > : 20090227: > > : The /dev handling for the new USB stack has changed, a > > : buildworld/installworld is required for libusb20. > > > > Yes. Been there, done that. Also have the libmap.conf changes in > > place for old binaries that had worked for months before that. xsane > > used to just work in this setup, but now fails. Looks like some kind > > of mismatch in the ABI: > > > > found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0 > > Not sure what would have caused that. Before you spend too much time on > this you may want to note that the integration patches for libusb into > the ports build will likely be committed tomorrow. This will bump the > port numbers so the affected ports rebuild, hopefully sane with DTRT > after that. > Maybe you need to chown or rm /dev/uscanner0 to enforce use of libusb backend? --HPS From hselasky at c2i.net Mon Mar 9 05:54:18 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Mar 9 05:54:36 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903091345.00743.boris.kotzev@gmail.com> References: <200903041946.15105.boris.kotzev@gmail.com> <200903090851.53432.hselasky@c2i.net> <200903091345.00743.boris.kotzev@gmail.com> Message-ID: <200903091356.47621.hselasky@c2i.net> On Monday 09 March 2009, Boris Kotzev wrote: > Boris Kotzev Try the following patch: http://perforce.freebsd.org/chv.cgi?CH=158916 Repeat with ums debugging turned on. I think I see what is wrong now. --HPS From imp at bsdimp.com Mon Mar 9 05:58:15 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Mar 9 05:58:27 2009 Subject: Latest kernel breaks scanner In-Reply-To: <200903091233.55089.hselasky@c2i.net> References: <20090308.154353.-1350498283.imp@bsdimp.com> <20090308215604.GD30672@citylink.fud.org.nz> <200903091233.55089.hselasky@c2i.net> Message-ID: <20090309.065558.-432839106.imp@bsdimp.com> In message: <200903091233.55089.hselasky@c2i.net> Hans Petter Selasky writes: : On Sunday 08 March 2009, Andrew Thompson wrote: : > On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: : > > In message: <20090308203157.GC30672@citylink.fud.org.nz> : > > : > > Andrew Thompson writes: : > > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: : > > : > Sigh. Had a working system from Mar 4th. Upgraded now it doesn't : > > : > work. Scanner not found by xsane. : > > : : > > : Are you sure its not this? : > > : : > > : 20090227: : > > : The /dev handling for the new USB stack has changed, a : > > : buildworld/installworld is required for libusb20. : > > : > > Yes. Been there, done that. Also have the libmap.conf changes in : > > place for old binaries that had worked for months before that. xsane : > > used to just work in this setup, but now fails. Looks like some kind : > > of mismatch in the ABI: : > > : > > found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0 : > : > Not sure what would have caused that. Before you spend too much time on : > this you may want to note that the integration patches for libusb into : > the ports build will likely be committed tomorrow. This will bump the : > port numbers so the affected ports rebuild, hopefully sane with DTRT : > after that. : > : : Maybe you need to chown or rm /dev/uscanner0 to enforce use of libusb backend? never had to do that before... Warner From imp at bsdimp.com Mon Mar 9 05:58:15 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Mar 9 05:58:28 2009 Subject: Latest kernel breaks scanner In-Reply-To: <200903091233.55089.hselasky@c2i.net> References: <20090308.154353.-1350498283.imp@bsdimp.com> <20090308215604.GD30672@citylink.fud.org.nz> <200903091233.55089.hselasky@c2i.net> Message-ID: <20090309.065558.-432839106.imp@bsdimp.com> In message: <200903091233.55089.hselasky@c2i.net> Hans Petter Selasky writes: : On Sunday 08 March 2009, Andrew Thompson wrote: : > On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: : > > In message: <20090308203157.GC30672@citylink.fud.org.nz> : > > : > > Andrew Thompson writes: : > > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: : > > : > Sigh. Had a working system from Mar 4th. Upgraded now it doesn't : > > : > work. Scanner not found by xsane. : > > : : > > : Are you sure its not this? : > > : : > > : 20090227: : > > : The /dev handling for the new USB stack has changed, a : > > : buildworld/installworld is required for libusb20. : > > : > > Yes. Been there, done that. Also have the libmap.conf changes in : > > place for old binaries that had worked for months before that. xsane : > > used to just work in this setup, but now fails. Looks like some kind : > > of mismatch in the ABI: : > > : > > found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0 : > : > Not sure what would have caused that. Before you spend too much time on : > this you may want to note that the integration patches for libusb into : > the ports build will likely be committed tomorrow. This will bump the : > port numbers so the affected ports rebuild, hopefully sane with DTRT : > after that. : > : : Maybe you need to chown or rm /dev/uscanner0 to enforce use of libusb backend? never had to do that before... Warner From hselasky at c2i.net Mon Mar 9 06:02:11 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Mar 9 06:02:23 2009 Subject: Latest kernel breaks scanner In-Reply-To: <20090309.065558.-432839106.imp@bsdimp.com> References: <20090308.154353.-1350498283.imp@bsdimp.com> <200903091233.55089.hselasky@c2i.net> <20090309.065558.-432839106.imp@bsdimp.com> Message-ID: <200903091404.34912.hselasky@c2i.net> On Monday 09 March 2009, M. Warner Losh wrote: > In message: <200903091233.55089.hselasky@c2i.net> > > Hans Petter Selasky writes: > : On Sunday 08 March 2009, Andrew Thompson wrote: > : > On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: > : > > In message: <20090308203157.GC30672@citylink.fud.org.nz> > : > > > : > > Andrew Thompson writes: > : > > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: > : > > : > Sigh. Had a working system from Mar 4th. Upgraded now it > : > > : > doesn't work. Scanner not found by xsane. > : > > : > : > > : Are you sure its not this? > : > > : > : > > : 20090227: > : > > : The /dev handling for the new USB stack has changed, a > : > > : buildworld/installworld is required for libusb20. > : > > > : > > Yes. Been there, done that. Also have the libmap.conf changes in > : > > place for old binaries that had worked for months before that. xsane > : > > used to just work in this setup, but now fails. Looks like some kind > : > > of mismatch in the ABI: > : > > > : > > found USB scanner (UNKNOWN vendor and product) at device > : > > /dev/uscanner0 > : > > : > Not sure what would have caused that. Before you spend too much time on > : > this you may want to note that the integration patches for libusb into > : > the ports build will likely be committed tomorrow. This will bump the > : > port numbers so the affected ports rebuild, hopefully sane with DTRT > : > after that. > : > : Maybe you need to chown or rm /dev/uscanner0 to enforce use of libusb > : backend? > > never had to do that before... Or recompile all of the sane backends. Probably an IOCTL on the uscanner0 is broken, and the fallback to libusb backend will maybe solve your problem temporarily if you rm /dev/uscanner0 . Actually that is another question: Should we remove ID's from uscanner.c which will work fine attaching through the libusb backend ? --HPS From hselasky at c2i.net Mon Mar 9 06:02:11 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Mar 9 06:02:24 2009 Subject: Latest kernel breaks scanner In-Reply-To: <20090309.065558.-432839106.imp@bsdimp.com> References: <20090308.154353.-1350498283.imp@bsdimp.com> <200903091233.55089.hselasky@c2i.net> <20090309.065558.-432839106.imp@bsdimp.com> Message-ID: <200903091404.34912.hselasky@c2i.net> On Monday 09 March 2009, M. Warner Losh wrote: > In message: <200903091233.55089.hselasky@c2i.net> > > Hans Petter Selasky writes: > : On Sunday 08 March 2009, Andrew Thompson wrote: > : > On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: > : > > In message: <20090308203157.GC30672@citylink.fud.org.nz> > : > > > : > > Andrew Thompson writes: > : > > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: > : > > : > Sigh. Had a working system from Mar 4th. Upgraded now it > : > > : > doesn't work. Scanner not found by xsane. > : > > : > : > > : Are you sure its not this? > : > > : > : > > : 20090227: > : > > : The /dev handling for the new USB stack has changed, a > : > > : buildworld/installworld is required for libusb20. > : > > > : > > Yes. Been there, done that. Also have the libmap.conf changes in > : > > place for old binaries that had worked for months before that. xsane > : > > used to just work in this setup, but now fails. Looks like some kind > : > > of mismatch in the ABI: > : > > > : > > found USB scanner (UNKNOWN vendor and product) at device > : > > /dev/uscanner0 > : > > : > Not sure what would have caused that. Before you spend too much time on > : > this you may want to note that the integration patches for libusb into > : > the ports build will likely be committed tomorrow. This will bump the > : > port numbers so the affected ports rebuild, hopefully sane with DTRT > : > after that. > : > : Maybe you need to chown or rm /dev/uscanner0 to enforce use of libusb > : backend? > > never had to do that before... Or recompile all of the sane backends. Probably an IOCTL on the uscanner0 is broken, and the fallback to libusb backend will maybe solve your problem temporarily if you rm /dev/uscanner0 . Actually that is another question: Should we remove ID's from uscanner.c which will work fine attaching through the libusb backend ? --HPS From imp at bsdimp.com Mon Mar 9 06:49:49 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Mar 9 06:50:00 2009 Subject: Latest kernel breaks scanner In-Reply-To: <200903091404.34912.hselasky@c2i.net> References: <200903091233.55089.hselasky@c2i.net> <20090309.065558.-432839106.imp@bsdimp.com> <200903091404.34912.hselasky@c2i.net> Message-ID: <20090309.073931.635732127.imp@bsdimp.com> In message: <200903091404.34912.hselasky@c2i.net> Hans Petter Selasky writes: : On Monday 09 March 2009, M. Warner Losh wrote: : > In message: <200903091233.55089.hselasky@c2i.net> : > : > Hans Petter Selasky writes: : > : On Sunday 08 March 2009, Andrew Thompson wrote: : > : > On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: : > : > > In message: <20090308203157.GC30672@citylink.fud.org.nz> : > : > > : > : > > Andrew Thompson writes: : > : > > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: : > : > > : > Sigh. Had a working system from Mar 4th. Upgraded now it : > : > > : > doesn't work. Scanner not found by xsane. : > : > > : : > : > > : Are you sure its not this? : > : > > : : > : > > : 20090227: : > : > > : The /dev handling for the new USB stack has changed, a : > : > > : buildworld/installworld is required for libusb20. : > : > > : > : > > Yes. Been there, done that. Also have the libmap.conf changes in : > : > > place for old binaries that had worked for months before that. xsane : > : > > used to just work in this setup, but now fails. Looks like some kind : > : > > of mismatch in the ABI: : > : > > : > : > > found USB scanner (UNKNOWN vendor and product) at device : > : > > /dev/uscanner0 : > : > : > : > Not sure what would have caused that. Before you spend too much time on : > : > this you may want to note that the integration patches for libusb into : > : > the ports build will likely be committed tomorrow. This will bump the : > : > port numbers so the affected ports rebuild, hopefully sane with DTRT : > : > after that. : > : : > : Maybe you need to chown or rm /dev/uscanner0 to enforce use of libusb : > : backend? : > : > never had to do that before... : : Or recompile all of the sane backends. Probably an IOCTL on the uscanner0 is : broken, and the fallback to libusb backend will maybe solve your problem : temporarily if you rm /dev/uscanner0 . Can't do it. devel/libusb is broken. Been there tried that: Didn't work. I do know that it has *NEVER* found the device when I don't have uscanner loaded, even when ugen was loaded... : Actually that is another question: : : Should we remove ID's from uscanner.c which will work fine attaching through : the libusb backend ? Unlikely, given my experience that it appears to be required... Anyway, it is going to be at least a week before I can do anything on this again because the scanner is at home right now, and I'm in the airport waiting for my flight to AsiaBSDCon 2009... Warner From imp at bsdimp.com Mon Mar 9 06:49:49 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Mar 9 06:50:01 2009 Subject: Latest kernel breaks scanner In-Reply-To: <200903091404.34912.hselasky@c2i.net> References: <200903091233.55089.hselasky@c2i.net> <20090309.065558.-432839106.imp@bsdimp.com> <200903091404.34912.hselasky@c2i.net> Message-ID: <20090309.073931.635732127.imp@bsdimp.com> In message: <200903091404.34912.hselasky@c2i.net> Hans Petter Selasky writes: : On Monday 09 March 2009, M. Warner Losh wrote: : > In message: <200903091233.55089.hselasky@c2i.net> : > : > Hans Petter Selasky writes: : > : On Sunday 08 March 2009, Andrew Thompson wrote: : > : > On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: : > : > > In message: <20090308203157.GC30672@citylink.fud.org.nz> : > : > > : > : > > Andrew Thompson writes: : > : > > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: : > : > > : > Sigh. Had a working system from Mar 4th. Upgraded now it : > : > > : > doesn't work. Scanner not found by xsane. : > : > > : : > : > > : Are you sure its not this? : > : > > : : > : > > : 20090227: : > : > > : The /dev handling for the new USB stack has changed, a : > : > > : buildworld/installworld is required for libusb20. : > : > > : > : > > Yes. Been there, done that. Also have the libmap.conf changes in : > : > > place for old binaries that had worked for months before that. xsane : > : > > used to just work in this setup, but now fails. Looks like some kind : > : > > of mismatch in the ABI: : > : > > : > : > > found USB scanner (UNKNOWN vendor and product) at device : > : > > /dev/uscanner0 : > : > : > : > Not sure what would have caused that. Before you spend too much time on : > : > this you may want to note that the integration patches for libusb into : > : > the ports build will likely be committed tomorrow. This will bump the : > : > port numbers so the affected ports rebuild, hopefully sane with DTRT : > : > after that. : > : : > : Maybe you need to chown or rm /dev/uscanner0 to enforce use of libusb : > : backend? : > : > never had to do that before... : : Or recompile all of the sane backends. Probably an IOCTL on the uscanner0 is : broken, and the fallback to libusb backend will maybe solve your problem : temporarily if you rm /dev/uscanner0 . Can't do it. devel/libusb is broken. Been there tried that: Didn't work. I do know that it has *NEVER* found the device when I don't have uscanner loaded, even when ugen was loaded... : Actually that is another question: : : Should we remove ID's from uscanner.c which will work fine attaching through : the libusb backend ? Unlikely, given my experience that it appears to be required... Anyway, it is going to be at least a week before I can do anything on this again because the scanner is at home right now, and I'm in the airport waiting for my flight to AsiaBSDCon 2009... Warner From boris.kotzev at gmail.com Mon Mar 9 07:19:56 2009 From: boris.kotzev at gmail.com (Boris Kotzev) Date: Mon Mar 9 07:20:03 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903091356.47621.hselasky@c2i.net> References: <200903041946.15105.boris.kotzev@gmail.com> <200903091345.00743.boris.kotzev@gmail.com> <200903091356.47621.hselasky@c2i.net> Message-ID: <200903091619.51682.boris.kotzev@gmail.com> > Try the following patch: > > http://perforce.freebsd.org/chv.cgi?CH=158916 > > Repeat with ums debugging turned on. I think I see what is wrong now. > > --HPS The touchpad is functioning properly now! dmesg output with "sysctl hw.usb2.ums.debug=5": ums1: on usbus0 ums1: 3 buttons and [XY] coordinates ums_attach:543: sc=0xffffff000e0ad800 ums_attach:545: X 8/8 id=2 ums_attach:547: Y 16/8 id=2 ums_attach:549: Z 0/0 id=0 ums_attach:551: T 0/0 id=0 ums_attach:553: W 0/0 id=0 ums_attach:558: B1 0/1 id=2 ums_attach:558: B2 1/1 id=2 ums_attach:558: B3 2/1 id=2 ums_attach:560: size=64, id=2 uhid1: on usbus0 ums_open:704: ums_open:704: ums_ioctl:741: ums_ioctl:741: ums_ioctl:741: ums_ioctl:741: ums_ioctl:741: Thank you very much for your work! Let me know if you need more information. Best regards, Boris Kotzev From thompsa at FreeBSD.org Mon Mar 9 08:18:19 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Mar 9 08:18:31 2009 Subject: Latest kernel breaks scanner In-Reply-To: <20090309.073931.635732127.imp@bsdimp.com> References: <200903091233.55089.hselasky@c2i.net> <20090309.065558.-432839106.imp@bsdimp.com> <200903091404.34912.hselasky@c2i.net> <20090309.073931.635732127.imp@bsdimp.com> Message-ID: <20090309151811.GA40452@citylink.fud.org.nz> On Mon, Mar 09, 2009 at 07:39:31AM -0600, M. Warner Losh wrote: > In message: <200903091404.34912.hselasky@c2i.net> > Hans Petter Selasky writes: > : On Monday 09 March 2009, M. Warner Losh wrote: > : > In message: <200903091233.55089.hselasky@c2i.net> > : > > : > Hans Petter Selasky writes: > : > : On Sunday 08 March 2009, Andrew Thompson wrote: > : > : > On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: > : > : > > In message: <20090308203157.GC30672@citylink.fud.org.nz> > : > : > > > : > : > > Andrew Thompson writes: > : > : > > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: > : > : > > : > Sigh. Had a working system from Mar 4th. Upgraded now it > : > : > > : > doesn't work. Scanner not found by xsane. > : > : > > : > : > : > > : Are you sure its not this? > : > : > > : > : > : > > : 20090227: > : > : > > : The /dev handling for the new USB stack has changed, a > : > : > > : buildworld/installworld is required for libusb20. > : > : > > > : > : > > Yes. Been there, done that. Also have the libmap.conf changes in > : > : > > place for old binaries that had worked for months before that. xsane > : > : > > used to just work in this setup, but now fails. Looks like some kind > : > : > > of mismatch in the ABI: > : > : > > > : > : > > found USB scanner (UNKNOWN vendor and product) at device > : > : > > /dev/uscanner0 > : > : > > : > : > Not sure what would have caused that. Before you spend too much time on > : > : > this you may want to note that the integration patches for libusb into > : > : > the ports build will likely be committed tomorrow. This will bump the ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > : > : > port numbers so the affected ports rebuild, hopefully sane with DTRT > : > : > after that. > : > : > : > : Maybe you need to chown or rm /dev/uscanner0 to enforce use of libusb > : > : backend? > : > > : > never had to do that before... > : > : Or recompile all of the sane backends. Probably an IOCTL on the uscanner0 is > : broken, and the fallback to libusb backend will maybe solve your problem > : temporarily if you rm /dev/uscanner0 . > > Can't do it. devel/libusb is broken. Been there tried that: Didn't > work. > > I do know that it has *NEVER* found the device when I don't have > uscanner loaded, even when ugen was loaded... > > : Actually that is another question: > : > : Should we remove ID's from uscanner.c which will work fine attaching through > : the libusb backend ? > > Unlikely, given my experience that it appears to be required... > > Anyway, it is going to be at least a week before I can do anything on > this again because the scanner is at home right now, and I'm in the > airport waiting for my flight to AsiaBSDCon 2009... This is about to be fixed, see above. Hopefully everything is good on your return :) Andrew From thompsa at FreeBSD.org Mon Mar 9 08:18:19 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Mar 9 08:18:32 2009 Subject: Latest kernel breaks scanner In-Reply-To: <20090309.073931.635732127.imp@bsdimp.com> References: <200903091233.55089.hselasky@c2i.net> <20090309.065558.-432839106.imp@bsdimp.com> <200903091404.34912.hselasky@c2i.net> <20090309.073931.635732127.imp@bsdimp.com> Message-ID: <20090309151811.GA40452@citylink.fud.org.nz> On Mon, Mar 09, 2009 at 07:39:31AM -0600, M. Warner Losh wrote: > In message: <200903091404.34912.hselasky@c2i.net> > Hans Petter Selasky writes: > : On Monday 09 March 2009, M. Warner Losh wrote: > : > In message: <200903091233.55089.hselasky@c2i.net> > : > > : > Hans Petter Selasky writes: > : > : On Sunday 08 March 2009, Andrew Thompson wrote: > : > : > On Sun, Mar 08, 2009 at 03:43:53PM -0600, M. Warner Losh wrote: > : > : > > In message: <20090308203157.GC30672@citylink.fud.org.nz> > : > : > > > : > : > > Andrew Thompson writes: > : > : > > : On Sun, Mar 08, 2009 at 01:06:59PM -0600, M. Warner Losh wrote: > : > : > > : > Sigh. Had a working system from Mar 4th. Upgraded now it > : > : > > : > doesn't work. Scanner not found by xsane. > : > : > > : > : > : > > : Are you sure its not this? > : > : > > : > : > : > > : 20090227: > : > : > > : The /dev handling for the new USB stack has changed, a > : > : > > : buildworld/installworld is required for libusb20. > : > : > > > : > : > > Yes. Been there, done that. Also have the libmap.conf changes in > : > : > > place for old binaries that had worked for months before that. xsane > : > : > > used to just work in this setup, but now fails. Looks like some kind > : > : > > of mismatch in the ABI: > : > : > > > : > : > > found USB scanner (UNKNOWN vendor and product) at device > : > : > > /dev/uscanner0 > : > : > > : > : > Not sure what would have caused that. Before you spend too much time on > : > : > this you may want to note that the integration patches for libusb into > : > : > the ports build will likely be committed tomorrow. This will bump the ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > : > : > port numbers so the affected ports rebuild, hopefully sane with DTRT > : > : > after that. > : > : > : > : Maybe you need to chown or rm /dev/uscanner0 to enforce use of libusb > : > : backend? > : > > : > never had to do that before... > : > : Or recompile all of the sane backends. Probably an IOCTL on the uscanner0 is > : broken, and the fallback to libusb backend will maybe solve your problem > : temporarily if you rm /dev/uscanner0 . > > Can't do it. devel/libusb is broken. Been there tried that: Didn't > work. > > I do know that it has *NEVER* found the device when I don't have > uscanner loaded, even when ugen was loaded... > > : Actually that is another question: > : > : Should we remove ID's from uscanner.c which will work fine attaching through > : the libusb backend ? > > Unlikely, given my experience that it appears to be required... > > Anyway, it is going to be at least a week before I can do anything on > this again because the scanner is at home right now, and I'm in the > airport waiting for my flight to AsiaBSDCon 2009... This is about to be fixed, see above. Hopefully everything is good on your return :) Andrew From thompsa at FreeBSD.org Mon Mar 9 08:26:33 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Mar 9 08:26:39 2009 Subject: usb touchpad not working properly on CURRENT with usb2 In-Reply-To: <200903091619.51682.boris.kotzev@gmail.com> References: <200903041946.15105.boris.kotzev@gmail.com> <200903091345.00743.boris.kotzev@gmail.com> <200903091356.47621.hselasky@c2i.net> <200903091619.51682.boris.kotzev@gmail.com> Message-ID: <20090309152628.GB40452@citylink.fud.org.nz> On Mon, Mar 09, 2009 at 04:19:51PM +0200, Boris Kotzev wrote: > > Try the following patch: > > > > http://perforce.freebsd.org/chv.cgi?CH=158916 > > > > Repeat with ums debugging turned on. I think I see what is wrong now. > > > > --HPS > > The touchpad is functioning properly now! > Committed in r189583. Andrew From bugmaster at FreeBSD.org Mon Mar 9 10:15:20 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Mar 9 10:17:45 2009 Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org Message-ID: <200903091715.n29HFELF045425@freefall.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/132312 usb Xorg 7.4 halts USB controller o usb/132080 usb [patch] [usb] Kernel panic after NOMEM caused by rum 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/131912 usb [uslcom] [patch] New devices using Silicon Labs chips o usb/131900 usb [usbdevs] [patch] Additional product identification co 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 f usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk 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/130325 usb [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh 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 [newusb] DVD drive detects as 'da' device o usb/129964 usb [newusb] disconnection of ugen devices isn't logged o bin/129963 usb [newusb] usbconfig(8) fails with misleading error when o docs/129962 usb [newusb] usbconfig(8) refers to non-existant usb2_core o usb/129945 usb [usbdevs] [patch] add u3g support for Longcheer WM66 U o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [patch] add support for ZTE AC8700 modem o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [patch] Liebert UPS being assigned uhid and o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb] [patch] uaudio is not full duplex o 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 f usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup o usb/127549 usb [umass] [patch] Meizu MiniPlayer M6 (SL) requires some s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127423 usb [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr o usb/127342 usb [boot] cannot enable usb keyboard and mouse support in o kern/127222 usb [ohci]: Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c f 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/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if 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/125264 usb [patch] sysctl for set usb mouse rate (very useful for 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/125072 usb [uplcom] [patch] add Mobile Action MA-620 Infrared Ada 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 o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work 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/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 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/122621 usb [patch] [request] New driver for Sierra Wireless 3G US 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/122025 usb [uscanner] [patch] uscanner does not attach to Epson R 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/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] FreeBSD fails to boot with usb legacy support e 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 [umass] [patch] quirk to support ASUS P535 as umass (a 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/120017 usb [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk o usb/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab 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/118686 usb [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround 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 [uaudio] [patch] Not possible to record with Plantroni 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 o 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 [umass] [patch] Problems with connection of the umass o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113977 usb [request] Need a way to set mode of USB disk's write c o usb/113672 usb [ehci] [panic] Kernel panic with AEWIN CB6971 s usb/113629 usb [ukbd] Dropped USB keyboard events on Dell Latitude D6 o usb/113432 usb [ucom] WARNING: attempt to net_add_domain(netgraph) af a usb/113060 usb [usbdevs] [patch] Samsung printer not working in bidir o usb/112944 usb [ulpt] [patch] Bi-directional access to HP LaserJet 10 o usb/112640 usb [usb] [hang] Kernel freezes when writing a file to an o usb/112631 usb [panic] Problem with SONY DSC-S80 camera on umount s usb/112568 usb [umass] [request] USB mode may wrong when mounting Pla o usb/112463 usb [umass] problem with Samsung USB DVD writer, libscg an o usb/112461 usb [ehci] [request] ehci USB 2.0 doesn't work on nforce4 o usb/111753 usb [uhid] [panic] Replicable system panic involving UHID s usb/110991 usb [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends o usb/110988 usb [umass] [patch] Handling of quirk IGNORE_RESIDUE is um o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC o usb/109397 usb [panic] on boot from USB flash o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr s usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/108056 usb [ohci] Mouse gets powered off during device probe when o usb/107935 usb [uplcom] [panic] panic while accessing /dev/cuaU0 o usb/107924 usb [patch] usbd(8) does not call detach o usb/107848 usb [umass] [request] cannot access Samsung flash disk o usb/107827 usb [ohci] [panic] ohci_add_done addr not found o usb/107496 usb [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [ o usb/107388 usb [patch] [request] new driver: add utoppy device from N o usb/107248 usb [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP o usb/107243 usb [cam] [patch] Apacer USB Flash Drive quirk o usb/106861 usb [usbdevs] [patch]: usbdevs update: Add product ACER Ze s usb/106832 usb [usb] USB HP printer is not detected by kernel when AC o usb/106648 usb [umass] [hang] USB Floppy on D1950 10 min Hang on Inse o usb/106621 usb [axe] [patch] DLINK DUB-E100 support broken o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106041 usb [usb] [request] FreeBSD does not recognise Mustek Bear o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/105186 usb [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c o usb/105065 usb [ata] [usb] SATA - USB Bridge o usb/104830 usb [umass] system crashes when copying data to umass devi o usb/104645 usb [umass] [request] Rave C-201 MP3 player does not commu o usb/104352 usb [ural] [patch] ural driver doesnt work o usb/104292 usb [umass] [hang] system lockup on forced umount of usb-s o usb/104290 usb [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto o usb/103917 usb [uhub] USB driver reports "Addr 0 should never happen" o usb/103418 usb usbhidctl(1): [patch] [request] usbhidctl: add ability o usb/103289 usb [request] USB 2.0 problems on AMD LX-800 CPU and CS-55 o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103025 usb [uhub] [panic] wrong detection of USB device for FreeB o usb/102976 usb [panic] Casio Exilim Digital Camera causes panic on in o usb/102678 usb [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/101761 usb [usb] [patch] [request] usb.h: increase maximal size o o usb/101752 usb [umass] [panic] 6.1-RELEASE kernel panic on usb device o usb/101448 usb [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O o usb/101096 usb [ural] [panic] USB WLAN occasionally causes kernel-pan o usb/100746 usb [keyboard] system does not boot due to USB keyboard pr o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar 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/93408 usb [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w 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 o 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/91629 usb [usb] usbd_abort_pipe() may result in infinite loop 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 f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US 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 f usb/83677 usb [usb] [request] usb controller often not detected (Sun 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/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu 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 " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, 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 o 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 o usb/75797 usb [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o 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 i386/46371 usb USB controller cannot be initialized on IBM Netfinity 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 305 problems total. From thompsa at FreeBSD.org Mon Mar 9 13:14:54 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Mon Mar 9 13:15:01 2009 Subject: HEADSUP: usb ports should be fixed Message-ID: <20090309201448.GB55506@citylink.fud.org.nz> Hi, Stanislav has updated the usb ports that depend on libusb to use the library from the base system, this should fix the majority of usb apps. Please see /usr/ports/UPDATING for instructions about this. Andrew From ache at nagual.pp.ru Mon Mar 9 22:06:25 2009 From: ache at nagual.pp.ru (Andrey Chernov) Date: Mon Mar 9 22:06:38 2009 Subject: USB2 makes moused insane Message-ID: <20090310045605.GA38857@nagual.pp.ru> Every pure mouse movement now acts like pressing several buttons at the same time which cause parts of console text under cursor copied/pasted randomly. This is "Logitech G3" mouse, corresponding dmesg entries are: ugen2.2: at usbus2 ums0: on usbus2 ums0: 16 buttons and [XYZ] coordinates uhid0: on usbus2 moused -d -i all -p /dev/ums0 moused: proto params: f8 80 00 00 8 00 ff /dev/ums0 usb sysmouse generic Please fix, it works with old usb just nice. -- http://ache.pp.ru/ From dougb at FreeBSD.org Mon Mar 9 22:46:50 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Mon Mar 9 22:46:56 2009 Subject: USB2 makes moused insane In-Reply-To: <20090310045605.GA38857@nagual.pp.ru> References: <20090310045605.GA38857@nagual.pp.ru> Message-ID: <49B5F885.1050508@FreeBSD.org> Andrey Chernov wrote: > Every pure mouse movement now acts like pressing several buttons at the > same time which cause parts of console text under cursor copied/pasted > randomly. > > This is "Logitech G3" mouse, corresponding dmesg entries are: > > ugen2.2: at usbus2 > ums0: on usbus2 > ums0: 16 buttons and [XYZ] coordinates > uhid0: on usbus2 > > moused -d -i all -p /dev/ums0 > moused: proto params: f8 80 00 00 8 00 ff > /dev/ums0 usb sysmouse generic > > Please fix, it works with old usb just nice. Try reverting back to r189546. I had a similar problem with the mouse which I narrowed down to http://svn.freebsd.org/changeset/base/189547 If that works, it's not the USBII changes generally, it's this specific change related to HID devices. hth, Doug -- This .signature sanitized for your protection From ache at nagual.pp.ru Mon Mar 9 23:04:44 2009 From: ache at nagual.pp.ru (Andrey Chernov) Date: Mon Mar 9 23:04:56 2009 Subject: USB2 makes moused insane In-Reply-To: <49B5F885.1050508@FreeBSD.org> References: <20090310045605.GA38857@nagual.pp.ru> <49B5F885.1050508@FreeBSD.org> Message-ID: <20090310060441.GA40479@nagual.pp.ru> On Mon, Mar 09, 2009 at 10:20:05PM -0700, Doug Barton wrote: > Andrey Chernov wrote: > > Every pure mouse movement now acts like pressing several buttons at the > > same time which cause parts of console text under cursor copied/pasted > > randomly. > > > > This is "Logitech G3" mouse, corresponding dmesg entries are: > > > > ugen2.2: at usbus2 > > ums0: on usbus2 > > ums0: 16 buttons and [XYZ] coordinates > > uhid0: on usbus2 > > > > moused -d -i all -p /dev/ums0 > > moused: proto params: f8 80 00 00 8 00 ff > > /dev/ums0 usb sysmouse generic > > > > Please fix, it works with old usb just nice. > > Try reverting back to r189546. I had a similar problem with the mouse > which I narrowed down to http://svn.freebsd.org/changeset/base/189547 > > If that works, it's not the USBII changes generally, it's this > specific change related to HID devices. Yes, reverting back to r189546 fix the problem. Something wrong done to HID in r189547 -- http://ache.pp.ru/ From beech at freebsd.org Mon Mar 9 23:25:13 2009 From: beech at freebsd.org (Beech Rintoul) Date: Mon Mar 9 23:25:24 2009 Subject: USB2 makes moused insane In-Reply-To: <20090310045605.GA38857@nagual.pp.ru> References: <20090310045605.GA38857@nagual.pp.ru> Message-ID: <200903092206.29775.beech@freebsd.org> On Monday 09 March 2009 20:56:06 Andrey Chernov wrote: > Every pure mouse movement now acts like pressing several buttons at the > same time which cause parts of console text under cursor copied/pasted > randomly. > > This is "Logitech G3" mouse, corresponding dmesg entries are: > > ugen2.2: at usbus2 > ums0: on > usbus2 ums0: 16 buttons and [XYZ] coordinates > uhid0: on > usbus2 > > moused -d -i all -p /dev/ums0 > moused: proto params: f8 80 00 00 8 00 ff > /dev/ums0 usb sysmouse generic > > Please fix, it works with old usb just nice. I see the exact same thing with my logitech USB mouse. Reverting to a kernel from about a week ago fixes the problem. Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.1R/announce.html --------------------------------------------------------------------------------------- From hselasky at c2i.net Tue Mar 10 00:38:31 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Mar 10 00:38:43 2009 Subject: USB2 makes moused insane In-Reply-To: <200903092206.29775.beech@freebsd.org> References: <20090310045605.GA38857@nagual.pp.ru> <200903092206.29775.beech@freebsd.org> Message-ID: <200903100840.57018.hselasky@c2i.net> On Tuesday 10 March 2009, Beech Rintoul wrote: > On Monday 09 March 2009 20:56:06 Andrey Chernov wrote: > > Every pure mouse movement now acts like pressing several buttons at the > > same time which cause parts of console text under cursor copied/pasted > > randomly. > > > > This is "Logitech G3" mouse, corresponding dmesg entries are: > > > > ugen2.2: at usbus2 > > ums0: on > > usbus2 ums0: 16 buttons and [XYZ] coordinates > > uhid0: on > > usbus2 > > > > moused -d -i all -p /dev/ums0 > > moused: proto params: f8 80 00 00 8 00 ff > > /dev/ums0 usb sysmouse generic > > > > Please fix, it works with old usb just nice. > > I see the exact same thing with my logitech USB mouse. Reverting to a > kernel from about a week ago fixes the problem. > > Beech Hi, Please dump the HID descriptors of mouse devices using USB config and send me the result and I will fix the issue. Replace 1 and 3 with the ugenX.Y for your device: usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 1 0x100 Parameters after u and a must be correct. You can also dump interface #0: usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 0 0x100 And the other interfaces if you want. --HPS From hselasky at c2i.net Tue Mar 10 06:28:08 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Mar 10 06:28:15 2009 Subject: USB2 makes moused insane In-Reply-To: <200903101300.24502.paul@fletchermoorland.co.uk> References: <20090310045605.GA38857@nagual.pp.ru> <200903100840.57018.hselasky@c2i.net> <200903101300.24502.paul@fletchermoorland.co.uk> Message-ID: <200903101430.35346.hselasky@c2i.net> Have you tried the following patch: http://perforce.freebsd.org/chv.cgi?CH=158916 --HPS From ache at nagual.pp.ru Tue Mar 10 07:18:59 2009 From: ache at nagual.pp.ru (Andrey Chernov) Date: Tue Mar 10 07:19:06 2009 Subject: USB2 makes moused insane In-Reply-To: <200903101430.35346.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903100840.57018.hselasky@c2i.net> <200903101300.24502.paul@fletchermoorland.co.uk> <200903101430.35346.hselasky@c2i.net> Message-ID: <20090310141848.GA50012@nagual.pp.ru> On Tue, Mar 10, 2009 at 02:30:34PM +0100, Hans Petter Selasky wrote: > Have you tried the following patch: > > http://perforce.freebsd.org/chv.cgi?CH=158916 It seems that this version already is in the head (so doesn't help) or I mess something in perforce interface :) -- http://ache.pp.ru/ From rbgarga at gmail.com Tue Mar 10 07:34:33 2009 From: rbgarga at gmail.com (Renato Botelho) Date: Tue Mar 10 07:34:50 2009 Subject: USB2 makes moused insane In-Reply-To: <200903100840.57018.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903092206.29775.beech@freebsd.org> <200903100840.57018.hselasky@c2i.net> Message-ID: <747dc8f30903100708w1e08c47akd445314cf19a8442@mail.gmail.com> On Tue, Mar 10, 2009 at 4:40 AM, Hans Petter Selasky wrote: > On Tuesday 10 March 2009, Beech Rintoul wrote: >> On Monday 09 March 2009 20:56:06 Andrey Chernov wrote: >> > Every pure mouse movement now acts like pressing several buttons at the >> > same time which cause parts of console text under cursor copied/pasted >> > randomly. >> > >> > This is "Logitech G3" mouse, corresponding dmesg entries are: >> > >> > ugen2.2: at usbus2 >> > ums0: on >> > usbus2 ums0: 16 buttons and [XYZ] coordinates >> > uhid0: on >> > usbus2 >> > >> > moused -d -i all -p /dev/ums0 >> > moused: proto params: f8 80 00 00 8 00 ff >> > /dev/ums0 usb sysmouse generic >> > >> > Please fix, it works with old usb just nice. >> >> I see the exact same thing with my logitech USB mouse. Reverting to a >> kernel from about a week ago fixes the problem. >> >> Beech > > Hi, > > Please dump the HID descriptors of mouse devices using USB config and send me > the result and I will fix the issue. > > Replace 1 and 3 with the ugenX.Y for your device: > > usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 1 0x100 I'm having same problem here, output of usbconfig you ask is available here: http://freebsd.pastebin.com/f2831347 Thanks -- Renato Botelho From hselasky at c2i.net Tue Mar 10 08:20:01 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Mar 10 08:20:08 2009 Subject: USB2 makes moused insane In-Reply-To: <200903101300.24502.paul@fletchermoorland.co.uk> References: <20090310045605.GA38857@nagual.pp.ru> <200903100840.57018.hselasky@c2i.net> <200903101300.24502.paul@fletchermoorland.co.uk> Message-ID: <200903101622.28277.hselasky@c2i.net> On Tuesday 10 March 2009, Paul Wootton wrote: > Paul Wootton Hi Paul, After looking at the HID descriptor, the following patch should fix your mouse: http://perforce.freebsd.org/chv.cgi?CH=159001 Sorry for the inconvenience, but it was neccessary to clean up the HID parsing. --HPS From hselasky at c2i.net Tue Mar 10 08:23:29 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Mar 10 08:23:41 2009 Subject: USB2 makes moused insane In-Reply-To: <747dc8f30903100708w1e08c47akd445314cf19a8442@mail.gmail.com> References: <20090310045605.GA38857@nagual.pp.ru> <200903100840.57018.hselasky@c2i.net> <747dc8f30903100708w1e08c47akd445314cf19a8442@mail.gmail.com> Message-ID: <200903101625.57647.hselasky@c2i.net> On Tuesday 10 March 2009, Renato Botelho wrote: > http://freebsd.pastebin.com/f2831347 Try this patch: http://perforce.freebsd.org/chv.cgi?CH=159001 --HPS From thompsa at FreeBSD.org Tue Mar 10 08:28:28 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Tue Mar 10 08:28:34 2009 Subject: USB2 makes moused insane In-Reply-To: <200903101625.57647.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903100840.57018.hselasky@c2i.net> <747dc8f30903100708w1e08c47akd445314cf19a8442@mail.gmail.com> <200903101625.57647.hselasky@c2i.net> Message-ID: <20090310152819.GB63136@citylink.fud.org.nz> On Tue, Mar 10, 2009 at 04:25:55PM +0100, Hans Petter Selasky wrote: > On Tuesday 10 March 2009, Renato Botelho wrote: > > http://freebsd.pastebin.com/f2831347 > > Try this patch: > > http://perforce.freebsd.org/chv.cgi?CH=159001 A regular diff for those not familiar with the p4web interface. http://people.freebsd.org/~thompsa/usb_hid.diff Andrew From rbgarga at gmail.com Tue Mar 10 08:51:12 2009 From: rbgarga at gmail.com (Renato Botelho) Date: Tue Mar 10 08:51:25 2009 Subject: USB2 makes moused insane In-Reply-To: <200903101625.57647.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903100840.57018.hselasky@c2i.net> <747dc8f30903100708w1e08c47akd445314cf19a8442@mail.gmail.com> <200903101625.57647.hselasky@c2i.net> Message-ID: <747dc8f30903100851o7e8ba37dl71bcd59056571232@mail.gmail.com> On Tue, Mar 10, 2009 at 12:25 PM, Hans Petter Selasky wrote: > On Tuesday 10 March 2009, Renato Botelho wrote: >> http://freebsd.pastebin.com/f2831347 > > Try this patch: > > http://perforce.freebsd.org/chv.cgi?CH=159001 Worked fine. Thanks!!! -- Renato Botelho From beech at freebsd.org Tue Mar 10 11:23:14 2009 From: beech at freebsd.org (Beech Rintoul) Date: Tue Mar 10 11:23:26 2009 Subject: USB2 makes moused insane In-Reply-To: <200903092206.29775.beech@freebsd.org> References: <20090310045605.GA38857@nagual.pp.ru> <200903092206.29775.beech@freebsd.org> Message-ID: <200903101023.10146.beech@freebsd.org> On Monday 09 March 2009 22:06:29 Beech Rintoul wrote: > On Monday 09 March 2009 20:56:06 Andrey Chernov wrote: > > Every pure mouse movement now acts like pressing several buttons at the > > same time which cause parts of console text under cursor copied/pasted > > randomly. > > > > This is "Logitech G3" mouse, corresponding dmesg entries are: > > > > ugen2.2: at usbus2 > > ums0: on > > usbus2 ums0: 16 buttons and [XYZ] coordinates > > uhid0: on > > usbus2 > > > > moused -d -i all -p /dev/ums0 > > moused: proto params: f8 80 00 00 8 00 ff > > /dev/ums0 usb sysmouse generic > > > > Please fix, it works with old usb just nice. > > I see the exact same thing with my logitech USB mouse. Reverting to a > kernel from about a week ago fixes the problem. > > Beech That patch fixes my issues as well, thanks :-) Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.1R/announce.html --------------------------------------------------------------------------------------- From dougb at FreeBSD.org Tue Mar 10 15:06:04 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Tue Mar 10 15:06:16 2009 Subject: USB2 makes moused insane In-Reply-To: <200903100840.57018.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903092206.29775.beech@freebsd.org> <200903100840.57018.hselasky@c2i.net> Message-ID: <49B6E445.3000302@FreeBSD.org> Hans Petter Selasky wrote: > Please dump the HID descriptors of mouse devices using USB config and send me > the result and I will fix the issue. > > Replace 1 and 3 with the ugenX.Y for your device: > > usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 1 0x100 > > Parameters after u and a must be correct. You can also dump interface #0: > > usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 0 0x100 I'm up to r189646 now (Andrew's latest this morning) and the mouse pointer works, but I've lost the wheel. I also tried the version in http://perforce.freebsd.org/chv.cgi?CH=159001, same result. You mentioned http://perforce.freebsd.org/chv.cgi?CH=158916 in another post, but those changes seem to be in the tree as of r189646. Here is the information you requested: ugen4.7: at usbus4 ums0: on usbus4 usbconfig -u 4 -a 7 do_request 0x81 0x06 0x2200 1 0x100 REQUEST = <0x05 0x01 0x09 0x02 0xa1 0x01 0x05 0x09 0x19 0x01 0x29 0x03 0x15 0x00 0x25 0x01 0x95 0x03 0x75 0x01 0x81 0x02 0x95 0x01 0x75 0x05 0x81 0x03 0x05 0x01 0x09 0x01 0xa1 0x00 0x09 0x30 0x09 0x31 0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x02 0x81 0x06 0xc0 0x09 0x38 0x95 0x01 0x81 0x06 0x09 0x3c 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x01 0xb1 0x22 0x95 0x07 0xb1 0x01 0x05 0x08 0x09 0x4b 0x15 0x00 0x25 0x03 0x95 0x01 0x75 0x02 0x09 0x3c 0xa1 0x02 0x09 0x41 0x09 0x3d 0x09 0x3f 0x09 0x40 0x91 0x00 0xc0 0x75 0x06 0x91 0x01 0xc0><)%uu01%u8%u"K%uA=?@u> usbconfig -u 4 -a 7 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = Can I get my wheel back please? :) Doug -- This .signature sanitized for your protection From thompsa at FreeBSD.org Tue Mar 10 18:04:19 2009 From: thompsa at FreeBSD.org (thompsa@FreeBSD.org) Date: Tue Mar 10 18:04:26 2009 Subject: usb/125072: [uplcom] [patch] add Mobile Action MA-620 Infrared Adapter Message-ID: <200903110104.n2B14JIq055616@freefall.freebsd.org> Synopsis: [uplcom] [patch] add Mobile Action MA-620 Infrared Adapter State-Changed-From-To: open->closed State-Changed-By: thompsa State-Changed-When: Wed Mar 11 01:04:03 UTC 2009 State-Changed-Why: MFC complete, thanks for the patch. http://www.freebsd.org/cgi/query-pr.cgi?pr=125072 From ache at nagual.pp.ru Tue Mar 10 18:15:45 2009 From: ache at nagual.pp.ru (Andrey Chernov) Date: Tue Mar 10 18:15:51 2009 Subject: USB2 makes moused insane In-Reply-To: <200903101625.57647.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903100840.57018.hselasky@c2i.net> <747dc8f30903100708w1e08c47akd445314cf19a8442@mail.gmail.com> <200903101625.57647.hselasky@c2i.net> Message-ID: <20090311011536.GB65734@nagual.pp.ru> On Tue, Mar 10, 2009 at 04:25:55PM +0100, Hans Petter Selasky wrote: > On Tuesday 10 March 2009, Renato Botelho wrote: > > http://freebsd.pastebin.com/f2831347 > > Try this patch: > > http://perforce.freebsd.org/chv.cgi?CH=159001 Mine one still not fixed by that. Here is debugging info as asked: usbconfig ... 1 ... REQUEST = <0x06 0x00 0xff 0x09 0x01 0xa1 0x01 0x85 0x10 0x75 0x08 0x95 0x06 0x15 0x00 0x26 0xff 0x00 0x09 0x01 0x81 0x00 0x09 0x01 0x91 0x00 0xc0 0x06 0x00 0xff 0x09 0x02 0xa1 0x01 0x85 0x11 0x75 0x08 0x95 0x13 0x15 0x00 0x26 0xff 0x00 0x09 0x02 0x81 0x00 0x09 0x02 0x91 0x00 0xc0> usbconfig ... 0 ... REQUEST = <0x05 0x01 0x09 0x02 0xa1 0x01 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x08 0x15 0x00 0x25 0x01 0x95 0x08 0x75 0x01 0x81 0x02 0x06 0x00 0xff 0x09 0x40 0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x02 0x81 0x02 0x05 0x01 0x09 0x38 0x95 0x01 0x81 0x06 0x05 0x0c 0x0a 0x38 0x02 0x95 0x01 0x81 0x06 0x05 0x01 0x16 0x01 0x80 0x26 0xff 0x7f 0x75 0x10 0x95 0x02 0x09 0x30 0x09 0x31 0x81 0x06 0x05 0x09 0x19 0x09 0x29 0x10 0x15 0x00 0x25 0x01 0x95 0x08 0x75 0x01 0x81 0x02 0xc0 0xc0><)%u@%u88&u01)%u> -- http://ache.pp.ru/ From hselasky at c2i.net Wed Mar 11 01:26:23 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 11 01:26:35 2009 Subject: USB2 makes moused insane In-Reply-To: <49B6E445.3000302@FreeBSD.org> References: <20090310045605.GA38857@nagual.pp.ru> <200903100840.57018.hselasky@c2i.net> <49B6E445.3000302@FreeBSD.org> Message-ID: <200903110928.51384.hselasky@c2i.net> On Tuesday 10 March 2009, Doug Barton wrote: > Hans Petter Selasky wrote: > > Please dump the HID descriptors of mouse devices using USB config and > > send me the result and I will fix the issue. > > > > Replace 1 and 3 with the ugenX.Y for your device: > > > > usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 1 0x100 > > > > Parameters after u and a must be correct. You can also dump interface #0: > > > > usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 0 0x100 > > > Can I get my wheel back please? :) > After looking at the HID descriptors I have made the following patch: http://perforce.freebsd.org/chv.cgi?CH=159053 USB wheel should work again! --HPS From hselasky at c2i.net Wed Mar 11 01:32:25 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 11 01:32:38 2009 Subject: USB2 makes moused insane In-Reply-To: <20090311011536.GB65734@nagual.pp.ru> References: <20090310045605.GA38857@nagual.pp.ru> <200903101625.57647.hselasky@c2i.net> <20090311011536.GB65734@nagual.pp.ru> Message-ID: <200903110934.53005.hselasky@c2i.net> On Wednesday 11 March 2009, Andrey Chernov wrote: > 0x05 0x01 0x09 0x02 0xa1 0x01 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 > 0x08 0x15 0x00 0x25 0x01 0x95 0x08 0x75 0x01 0x81 0x02 0x06 0x00 0xff 0x09 > 0x40 0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x02 0x81 0x02 0x05 0x01 0x09 0x38 > 0x95 0x01 0x81 0x06 0x05 0x0c 0x0a 0x38 0x02 0x95 0x01 0x81 0x06 0x05 0x01 > 0x16 0x01 0x80 0x26 0xff 0x7f 0x75 0x10 0x95 0x02 0x09 0x30 0x09 0x31 0x81 > 0x06 0x05 0x09 0x19 0x09 0x29 0x10 0x15 0x00 0x25 0x01 0x95 0x08 0x75 0x01 > 0x81 0x02 0xc0 0xc0 Hi, This patch should also fix your mouse. Please try and report back! http://perforce.freebsd.org/chv.cgi?CH=159053 Thanks for reporting. Now we have some nice reference HID descriptors on the e-mail lists to run tests against for the future! --HPS From dougb at FreeBSD.org Wed Mar 11 11:33:55 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Wed Mar 11 11:34:02 2009 Subject: USB2 makes moused insane In-Reply-To: <200903110928.51384.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903100840.57018.hselasky@c2i.net> <49B6E445.3000302@FreeBSD.org> <200903110928.51384.hselasky@c2i.net> Message-ID: <49B8040E.9090604@FreeBSD.org> Hans Petter Selasky wrote: > After looking at the HID descriptors I have made the following patch: > > http://perforce.freebsd.org/chv.cgi?CH=159053 > > USB wheel should work again! Thanks for the quick response. One question, how do I generate a diff I can apply to my sources from the perforce web thingy? Thanks, Doug From hselasky at c2i.net Wed Mar 11 12:44:19 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 11 12:44:31 2009 Subject: USB2 makes moused insane In-Reply-To: <49B8040E.9090604@FreeBSD.org> References: <20090310045605.GA38857@nagual.pp.ru> <200903110928.51384.hselasky@c2i.net> <49B8040E.9090604@FreeBSD.org> Message-ID: <200903112046.45540.hselasky@c2i.net> On Wednesday 11 March 2009, Doug Barton wrote: > Hans Petter Selasky wrote: > > After looking at the HID descriptors I have made the following patch: > > > > http://perforce.freebsd.org/chv.cgi?CH=159053 > > > > USB wheel should work again! > > Thanks for the quick response. One question, how do I generate a diff > I can apply to my sources from the perforce web thingy? > Hi, There is a link where you can download the complete file. Then you have to diff on your box. --HPS From dougb at FreeBSD.org Wed Mar 11 13:04:00 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Wed Mar 11 13:04:07 2009 Subject: USB2 makes moused insane In-Reply-To: <200903112046.45540.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903110928.51384.hselasky@c2i.net> <49B8040E.9090604@FreeBSD.org> <200903112046.45540.hselasky@c2i.net> Message-ID: <49B81923.1050204@FreeBSD.org> Hans Petter Selasky wrote: > On Wednesday 11 March 2009, Doug Barton wrote: >> Hans Petter Selasky wrote: >>> After looking at the HID descriptors I have made the following patch: >>> >>> http://perforce.freebsd.org/chv.cgi?CH=159053 >>> >>> USB wheel should work again! >> Thanks for the quick response. One question, how do I generate a diff >> I can apply to my sources from the perforce web thingy? >> > > Hi, > > There is a link where you can download the complete file. > > Then you have to diff on your box. D'oh, I should have thought of that. Thanks. :) From ache at nagual.pp.ru Wed Mar 11 13:59:01 2009 From: ache at nagual.pp.ru (Andrey Chernov) Date: Wed Mar 11 13:59:15 2009 Subject: USB2 makes moused insane In-Reply-To: <200903110934.53005.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903101625.57647.hselasky@c2i.net> <20090311011536.GB65734@nagual.pp.ru> <200903110934.53005.hselasky@c2i.net> Message-ID: <20090311205843.GA6101@nagual.pp.ru> On Wed, Mar 11, 2009 at 09:34:51AM +0100, Hans Petter Selasky wrote: > Hi, > > This patch should also fix your mouse. Please try and report back! > > http://perforce.freebsd.org/chv.cgi?CH=159053 Just tried. It seems nothing is changed for my mice. -- http://ache.pp.ru/ From hselasky at c2i.net Wed Mar 11 14:04:21 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 11 14:04:33 2009 Subject: USB2 makes moused insane In-Reply-To: <20090311205843.GA6101@nagual.pp.ru> References: <20090310045605.GA38857@nagual.pp.ru> <200903110934.53005.hselasky@c2i.net> <20090311205843.GA6101@nagual.pp.ru> Message-ID: <200903112206.47108.hselasky@c2i.net> On Wednesday 11 March 2009, Andrey Chernov wrote: > On Wed, Mar 11, 2009 at 09:34:51AM +0100, Hans Petter Selasky wrote: > > Hi, > > > > This patch should also fix your mouse. Please try and report back! > > > > http://perforce.freebsd.org/chv.cgi?CH=159053 > > Just tried. It seems nothing is changed for my mice. Are you sure that you re-loaded the USB module? Send debugging when hw.usb2.ums.debug=15 and you plug and move mouse. --HPS From hselasky at c2i.net Wed Mar 11 14:06:23 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 11 14:06:36 2009 Subject: USB2 makes moused insane In-Reply-To: <20090311205843.GA6101@nagual.pp.ru> References: <20090310045605.GA38857@nagual.pp.ru> <200903110934.53005.hselasky@c2i.net> <20090311205843.GA6101@nagual.pp.ru> Message-ID: <200903112208.49142.hselasky@c2i.net> On Wednesday 11 March 2009, Andrey Chernov wrote: > On Wed, Mar 11, 2009 at 09:34:51AM +0100, Hans Petter Selasky wrote: > > Hi, > > > > This patch should also fix your mouse. Please try and report back! > > > > http://perforce.freebsd.org/chv.cgi?CH=159053 > > Just tried. It seems nothing is changed for my mice. This patch also depends on some previous patches, which have not been committed yet, so maybe the best is to just grab the latest usb_hid.c file from P4 and compile that. --HPS From ache at nagual.pp.ru Wed Mar 11 14:30:51 2009 From: ache at nagual.pp.ru (Andrey Chernov) Date: Wed Mar 11 14:31:03 2009 Subject: USB2 makes moused insane In-Reply-To: <200903112206.47108.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903110934.53005.hselasky@c2i.net> <20090311205843.GA6101@nagual.pp.ru> <200903112206.47108.hselasky@c2i.net> Message-ID: <20090311213045.GB47787@nagual.pp.ru> On Wed, Mar 11, 2009 at 10:06:44PM +0100, Hans Petter Selasky wrote: > > Are you sure that you re-loaded the USB module? It is in the kernel. I use whole file from p4. > Send debugging when hw.usb2.ums.debug=15 and you plug and move mouse. As you can see, some lines have ff in the buttons while no buttons are pressed. The mice itself have 5 buttons (including wheel click). ums_intr_callback:181: sc=0xc517ec00 actlen=10 ums_intr_callback:198: data = 00 00 ff 00 00 00 00 ff ums_intr_callback:255: x:0 y:256 z:1 t:0 w:0 buttons:0x0000ff00 ums_intr_callback:181: sc=0xc517ec00 actlen=10 ums_intr_callback:198: data = 00 ff 00 00 00 ff ff 00 ums_intr_callback:255: x:-256 y:-255 z:0 t:0 w:0 buttons:0x00000000 ums_intr_callback:181: sc=0xc517ec00 actlen=10 ums_intr_callback:198: data = 00 ff 00 00 00 ff ff 00 ums_intr_callback:255: x:-256 y:-255 z:0 t:0 w:0 buttons:0x00000000 ums_intr_callback:181: sc=0xc517ec00 actlen=10 ums_intr_callback:198: data = 00 e9 f9 00 00 e9 ff f9 ums_intr_callback:255: x:-5888 y:1537 z:7 t:0 w:0 buttons:0x0000ff00 ums_intr_callback:181: sc=0xc517ec00 actlen=10 ums_intr_callback:198: data = 00 f0 fe 00 00 f0 ff fe ums_intr_callback:255: x:-4096 y:257 z:2 t:0 w:0 buttons:0x0000ff00 ums_intr_callback:181: sc=0xc517ec00 actlen=10 ums_intr_callback:198: data = 00 fb 00 00 00 fb ff 00 ums_intr_callback:255: x:-1280 y:-255 z:0 t:0 w:0 buttons:0x00000000 ums_intr_callback:181: sc=0xc517ec00 actlen=10 ums_intr_callback:198: data = 00 ff 00 00 00 ff ff 00 ums_intr_callback:255: x:-256 y:-255 z:0 t:0 w:0 buttons:0x00000000 ums_intr_callback:181: sc=0xc517ec00 actlen=10 ums_intr_callback:198: data = 00 01 00 00 00 01 00 00 ums_intr_callback:255: x:256 y:0 z:0 t:0 w:0 buttons:0x00000000 ums_intr_callback:181: sc=0xc517ec00 actlen=10 ums_intr_callback:198: data = 00 01 00 00 00 01 00 00 ums_intr_callback:255: x:256 y:0 z:0 t:0 w:0 buttons:0x00000000 ums_intr_callback:181: sc=0xc517ec00 actlen=10 ums_intr_callback:198: data = 00 0e fc 00 00 0e 00 fc ums_intr_callback:255: x:3584 y:1024 z:4 t:0 w:0 buttons:0x0000ff00 ums_intr_callback:181: sc=0xc517ec00 actlen=10 ums_intr_callback:198: data = 00 01 00 00 00 01 00 00 ums_intr_callback:255: x:256 y:0 z:0 t:0 w:0 buttons:0x00000000 -- http://ache.pp.ru/ From hselasky at c2i.net Wed Mar 11 14:45:16 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 11 14:45:26 2009 Subject: USB2 makes moused insane In-Reply-To: <20090311213045.GB47787@nagual.pp.ru> References: <20090310045605.GA38857@nagual.pp.ru> <200903112206.47108.hselasky@c2i.net> <20090311213045.GB47787@nagual.pp.ru> Message-ID: <200903112247.42768.hselasky@c2i.net> On Wednesday 11 March 2009, Andrey Chernov wrote: > On Wed, Mar 11, 2009 at 10:06:44PM +0100, Hans Petter Selasky wrote: > > Are you sure that you re-loaded the USB module? > > It is in the kernel. I use whole file from p4. > > > Send debugging when hw.usb2.ums.debug=15 and you plug and move mouse. > Can you show me the dmesg right after you plug the device, that prints where the X,Y,Z and buttons are located. I think we are seeing a different problem where we have a zero-valued report ID. And also. Re-dump the HID descriptor if this a different mouse than before. --HPS > As you can see, some lines have ff in the buttons while no buttons are > pressed. The mice itself have 5 buttons (including wheel click). > > ums_intr_callback:181: sc=0xc517ec00 actlen=10 > ums_intr_callback:198: data = 00 00 ff 00 00 00 00 ff > ums_intr_callback:255: x:0 y:256 z:1 t:0 w:0 buttons:0x0000ff00 > ums_intr_callback:181: sc=0xc517ec00 actlen=10 > ums_intr_callback:198: data = 00 ff 00 00 00 ff ff 00 > ums_intr_callback:255: x:-256 y:-255 z:0 t:0 w:0 buttons:0x00000000 > ums_intr_callback:181: sc=0xc517ec00 actlen=10 > ums_intr_callback:198: data = 00 ff 00 00 00 ff ff 00 > ums_intr_callback:255: x:-256 y:-255 z:0 t:0 w:0 buttons:0x00000000 > ums_intr_callback:181: sc=0xc517ec00 actlen=10 > ums_intr_callback:198: data = 00 e9 f9 00 00 e9 ff f9 > ums_intr_callback:255: x:-5888 y:1537 z:7 t:0 w:0 buttons:0x0000ff00 > ums_intr_callback:181: sc=0xc517ec00 actlen=10 > ums_intr_callback:198: data = 00 f0 fe 00 00 f0 ff fe > ums_intr_callback:255: x:-4096 y:257 z:2 t:0 w:0 buttons:0x0000ff00 > ums_intr_callback:181: sc=0xc517ec00 actlen=10 > ums_intr_callback:198: data = 00 fb 00 00 00 fb ff 00 > ums_intr_callback:255: x:-1280 y:-255 z:0 t:0 w:0 buttons:0x00000000 > ums_intr_callback:181: sc=0xc517ec00 actlen=10 > ums_intr_callback:198: data = 00 ff 00 00 00 ff ff 00 > ums_intr_callback:255: x:-256 y:-255 z:0 t:0 w:0 buttons:0x00000000 > ums_intr_callback:181: sc=0xc517ec00 actlen=10 > ums_intr_callback:198: data = 00 01 00 00 00 01 00 00 > ums_intr_callback:255: x:256 y:0 z:0 t:0 w:0 buttons:0x00000000 > ums_intr_callback:181: sc=0xc517ec00 actlen=10 > ums_intr_callback:198: data = 00 01 00 00 00 01 00 00 > ums_intr_callback:255: x:256 y:0 z:0 t:0 w:0 buttons:0x00000000 > ums_intr_callback:181: sc=0xc517ec00 actlen=10 > ums_intr_callback:198: data = 00 0e fc 00 00 0e 00 fc > ums_intr_callback:255: x:3584 y:1024 z:4 t:0 w:0 buttons:0x0000ff00 > ums_intr_callback:181: sc=0xc517ec00 actlen=10 > ums_intr_callback:198: data = 00 01 00 00 00 01 00 00 > ums_intr_callback:255: x:256 y:0 z:0 t:0 w:0 buttons:0x00000000 From ache at nagual.pp.ru Wed Mar 11 14:54:30 2009 From: ache at nagual.pp.ru (Andrey Chernov) Date: Wed Mar 11 14:54:41 2009 Subject: USB2 makes moused insane In-Reply-To: <200903112247.42768.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903112206.47108.hselasky@c2i.net> <20090311213045.GB47787@nagual.pp.ru> <200903112247.42768.hselasky@c2i.net> Message-ID: <20090311215423.GA51085@nagual.pp.ru> On Wed, Mar 11, 2009 at 10:47:41PM +0100, Hans Petter Selasky wrote: > Can you show me the dmesg right after you plug the device, that prints where > the X,Y,Z and buttons are located. I think we are seeing a different problem > where we have a zero-valued report ID. Mouse is always plugged in, here is dmesg from my earlier message: ugen2.2: at usbus2 ums0: on usbus2 ums0: 16 buttons and [XYZ] coordinates uhid0: on usbus2 Or you need dmesg with mouse debug enabled? > And also. Re-dump the HID descriptor if this a different mouse than before. This is the same mouse. HID descriptors dumped are the same too. -- http://ache.pp.ru/ From hselasky at c2i.net Wed Mar 11 14:57:22 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 11 14:57:27 2009 Subject: USB2 makes moused insane In-Reply-To: <20090311215423.GA51085@nagual.pp.ru> References: <20090310045605.GA38857@nagual.pp.ru> <200903112247.42768.hselasky@c2i.net> <20090311215423.GA51085@nagual.pp.ru> Message-ID: <200903112259.48298.hselasky@c2i.net> On Wednesday 11 March 2009, Andrey Chernov wrote: > On Wed, Mar 11, 2009 at 10:47:41PM +0100, Hans Petter Selasky wrote: > > Can you show me the dmesg right after you plug the device, that prints > > where the X,Y,Z and buttons are located. I think we are seeing a > > different problem where we have a zero-valued report ID. > > Mouse is always plugged in, here is dmesg from my earlier message: > > ugen2.2: at usbus2 > ums0: on > usbus2 > ums0: 16 buttons and [XYZ] coordinates > uhid0: on > usbus2 > > Or you need dmesg with mouse debug enabled? Yes. > > > And also. Re-dump the HID descriptor if this a different mouse than > > before. > > This is the same mouse. HID descriptors dumped are the same too. From hselasky at c2i.net Wed Mar 11 15:23:17 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 11 15:23:24 2009 Subject: USB2 makes moused insane In-Reply-To: <20090311011536.GB65734@nagual.pp.ru> References: <20090310045605.GA38857@nagual.pp.ru> <200903101625.57647.hselasky@c2i.net> <20090311011536.GB65734@nagual.pp.ru> Message-ID: <200903112325.44983.hselasky@c2i.net> On Wednesday 11 March 2009, Andrey Chernov wrote: > Andrey Chernov Re-fetch the usb_hid.c file from USB P4 after the patch below. Problem should be solved now! http://perforce.freebsd.org/chv.cgi?CH=159091 --HPS From ache at nagual.pp.ru Wed Mar 11 15:36:13 2009 From: ache at nagual.pp.ru (Andrey Chernov) Date: Wed Mar 11 15:36:19 2009 Subject: USB2 makes moused insane In-Reply-To: <200903112325.44983.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903101625.57647.hselasky@c2i.net> <20090311011536.GB65734@nagual.pp.ru> <200903112325.44983.hselasky@c2i.net> Message-ID: <20090311223607.GA51845@nagual.pp.ru> On Wed, Mar 11, 2009 at 11:25:42PM +0100, Hans Petter Selasky wrote: > On Wednesday 11 March 2009, Andrey Chernov wrote: > > Andrey Chernov > > Re-fetch the usb_hid.c file from USB P4 after the patch below. Problem should > be solved now! > > http://perforce.freebsd.org/chv.cgi?CH=159091 Thanx, fixed now! -- http://ache.pp.ru/ From dougb at FreeBSD.org Wed Mar 11 23:00:02 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Wed Mar 11 23:01:31 2009 Subject: USB2 makes moused insane In-Reply-To: <200903112325.44983.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903101625.57647.hselasky@c2i.net> <20090311011536.GB65734@nagual.pp.ru> <200903112325.44983.hselasky@c2i.net> Message-ID: On Wed, 11 Mar 2009, Hans Petter Selasky wrote: > On Wednesday 11 March 2009, Andrey Chernov wrote: >> Andrey Chernov > > Re-fetch the usb_hid.c file from USB P4 after the patch below. Problem should > be solved now! > > http://perforce.freebsd.org/chv.cgi?CH=159091 woo hoo! Well done, it's all fine now. Doug -- This .signature sanitized for your protection From mlistsw at corp.iskratelecom.ru Thu Mar 12 06:05:24 2009 From: mlistsw at corp.iskratelecom.ru (Andrey Urtaykin) Date: Thu Mar 12 06:05:37 2009 Subject: USB KVM Raritan DKX2-232 In-Reply-To: <20090311155243.57fdcb25.freebsd@edvax.de> References: <7280394.541236782303889.JavaMail.HALO$@halo> <10423240.561236782522127.JavaMail.HALO$@halo> <20090311155243.57fdcb25.freebsd@edvax.de> Message-ID: <49B8FECF.60305@corp.iskratelecom.ru> Hi all This KVM (Raritan DKX2-232) uses only one USB connector for both mouse and keyboard. I have several servers with different hardware and FreeBSD from 6.2 to 7.1, and no one works properly the problem is: input doesn`t work at all OR/AND mouse moves interpretend as keyboard pressings OR/AND input with like CTRL pressed, (for example if you hit "T" KVM sending SIGUSR to terminal). Tryed all possible bios options(Legacy USB, Fast USB, etc) . BUT! IF i connect PS/2 keyboard to RUNNING server, and pressing several key on it - miracle happens and KVM works properly for sometime... Server info(this server interpretend mouse moves as text and keyboard pressings as signals): dmesg: uhci0: port 0x4040-0x405f irq 16 at device 29.0 on pci0 ukbd0: on uhub1 kbd2 at ukbd0 usbdevs -v: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: full speed, power 100 mA, config 1, RU-CIM(0x1005), RU(0x14dd), rev 0.00 <<-- this is KVM uname -a: FreeBSD xx 7.1-RELEASE FreeBSD 7.1-RELEASE #3: Fri Jan 2 13:30:10 MSK 2009 fxp@xx:/usr/obj/usr/src/sys/GENERIC i386 kbdcontrol -k /dev/ukbd0 < /dev/console kbdcontrol: cannot open /dev/ukbd0: Device busy kldload kbdmux kldload: can't load kbdmux: File exists From hselasky at c2i.net Thu Mar 12 07:37:06 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Mar 12 07:37:14 2009 Subject: USB2 makes moused insane In-Reply-To: <49B91BC3.2010205@zedat.fu-berlin.de> References: <20090310045605.GA38857@nagual.pp.ru> <200903112325.44983.hselasky@c2i.net> <49B91BC3.2010205@zedat.fu-berlin.de> Message-ID: <200903121539.35133.hselasky@c2i.net> On Thursday 12 March 2009, O. Hartmann wrote: > Hans Petter Selasky wrote: > > On Wednesday 11 March 2009, Andrey Chernov wrote: > >> Andrey Chernov > > > > Re-fetch the usb_hid.c file from USB P4 after the patch below. Problem > > should be solved now! > > > > http://perforce.freebsd.org/chv.cgi?CH=159091 > > > > --HPS > > _______________________________________________ > > 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" > > When will the patches be merged into the source tree? I have several > boxes rendered useless at this very moment due to jumping mice cursors on > X. The patches are in -current as of today. --HPS From ohartman at zedat.fu-berlin.de Thu Mar 12 07:51:50 2009 From: ohartman at zedat.fu-berlin.de (O. Hartmann) Date: Thu Mar 12 07:51:55 2009 Subject: USB2 makes moused insane In-Reply-To: <200903112325.44983.hselasky@c2i.net> References: <20090310045605.GA38857@nagual.pp.ru> <200903101625.57647.hselasky@c2i.net> <20090311011536.GB65734@nagual.pp.ru> <200903112325.44983.hselasky@c2i.net> Message-ID: <49B91BC3.2010205@zedat.fu-berlin.de> Hans Petter Selasky wrote: > On Wednesday 11 March 2009, Andrey Chernov wrote: >> Andrey Chernov > > Re-fetch the usb_hid.c file from USB P4 after the patch below. Problem should > be solved now! > > http://perforce.freebsd.org/chv.cgi?CH=159091 > > --HPS > _______________________________________________ > 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" When will the patches be merged into the source tree? I have several boxes rendered useless at this very moment due to jumping mice cursors on X. Regards, Oliver From lintzuyau at gmail.com Thu Mar 12 10:11:32 2009 From: lintzuyau at gmail.com (tzu-yau Lin) Date: Thu Mar 12 10:11:39 2009 Subject: How to add a USB vender in sys/dev/usb/usbdevs Message-ID: Dear all: I bought a usb network device. according to its spec, it claims it is Davicom 9601 usb nic. but when I plug it in my freebsd 7.1-Release box, it shows as following: ugen0: on uhub4 I did the instruction from http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2008-04/msg00532.html Here are the modifications /usr/src/sys/dev/usb/if_udav.c, line 263 /* DAVICOM DM9601 Generic */ {{ USB_VENDOR_DAVICOM, USB_PRODUCT_DAVICOM_DM9601 }, 0}, As for /usr/src/sys/dev/usb/usbdevs add line 1080 /* Davicom Semiconductor products */ product DAVICOM DM9601 0x9601 DM9601 USB NIC I disable original DAVICOM data at line 158 /*vendor DAVICOM 0x04a6 Davicom*/ And add new definition at line 537 vendor DAVICOM 0x0fe6 Davicom I re-bulid my kernel and reload if_udav, but nothing happened. Most confusing me is why dmesg messages still shows "0x0fe6" not Davicom. Did I miss something? Thanks for your help!! From jhein at timing.com Thu Mar 12 10:50:04 2009 From: jhein at timing.com (John Hein) Date: Thu Mar 12 10:50:11 2009 Subject: usb/122539: kernel panic: ohci_abort_xfer: not in process context Message-ID: <200903121750.n2CHo3a1083301@freefall.freebsd.org> The following reply was made to PR usb/122539; it has been noted by GNATS. From: John Hein To: bug-followup@FreeBSD.org, artur.zabronski@gmail.com Cc: usb@FreeBSD.org Subject: Re: usb/122539: kernel panic: ohci_abort_xfer: not in process context Date: Thu, 12 Mar 2009 11:44:21 -0600 Note: this is not specific to ohci or the device originally used in this PR. The problem is more generic. This happens for us when hardware flow control is turned on when using a usb serial device (specifically an ftdi based one). Eventually if hardware flow has to kick in and RTS is to be set, uftdi_set() is called in uftdi.c (old usb stack). In uftdi_set() there is this... (void)usbd_do_request(ucom->sc_udev, &req, NULL); Since we're calling this from the interrupt context, the response to the request times out (because the reply is not processed), the ohci_abort_xfer which performas the panic because we're not in the process context. Here is a patch that uses the usbd_do_request_async() call (instead of the synchronous version) to assert flow control when the input buffer reaches the highwater mark (which is detected from within interupt context). (patch against today's version of uftdi.c in the old usb stack) Index: sys/legacy/dev/usb/uftdi.c =================================================================== RCS file: /base/FreeBSD-CVS/src/sys/legacy/dev/usb/uftdi.c,v retrieving revision 1.1 diff -u -p -r1.1 uftdi.c --- uftdi.c 23 Feb 2009 18:16:17 -0000 1.1 +++ uftdi.c 12 Mar 2009 17:34:27 -0000 @@ -557,7 +557,7 @@ uftdi_set(void *vsc, int portno, int reg DPRINTFN(2,("uftdi_set: reqtype=0x%02x req=0x%02x value=0x%04x " "index=0x%04x len=%d\n", req.bmRequestType, req.bRequest, UGETW(req.wValue), UGETW(req.wIndex), UGETW(req.wLength))); - (void)usbd_do_request(ucom->sc_udev, &req, NULL); + (void)usbd_do_request_async(ucom->sc_udev, &req, NULL); } static int This is not specific to FTDI devices. It would probably be better to handle this in the usb serial layer. Whatever better fix someone comes up with should be merged to 7.x if possible (and 6). I have not yet looked to see if the new usb stack has the same problem. Please let me know if someone does this analysis. From hselasky at c2i.net Thu Mar 12 10:55:04 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Mar 12 10:55:10 2009 Subject: How to add a USB vender in sys/dev/usb/usbdevs In-Reply-To: References: Message-ID: <200903121857.32241.hselasky@c2i.net> On Thursday 12 March 2009, tzu-yau Lin wrote: > vendor DAVICOM 0x0fe6 Davicom > > I re-bulid my kernel and reload if_udav, In FreeBSD-7 you need to load if_udav before the kernel is loaded, else ugen will grab the device. Try this: echo "if_udav_load=YES" >> /boot/loader.conf cat /boot/loader.conf --HPS From jhein at timing.com Thu Mar 12 11:20:06 2009 From: jhein at timing.com (John Hein) Date: Thu Mar 12 11:20:14 2009 Subject: usb/122539: kernel panic: ohci_abort_xfer: not in process context Message-ID: <200903121820.n2CIK5qL021535@freefall.freebsd.org> The following reply was made to PR usb/122539; it has been noted by GNATS. From: John Hein To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/122539: kernel panic: ohci_abort_xfer: not in process context Date: Thu, 12 Mar 2009 12:14:42 -0600 The code to pull the patch out of the text of the last submission for the web page was too agressive and pulled some text into the patch blurb. So it's not missed, here is that last bit of text separately... ====================== This is not specific to FTDI devices. It would probably be better to handle this in the usb serial layer. Whatever better fix someone comes up with should be merged to 7.x if possible (and 6). I have not yet looked to see if the new usb stack has the same problem. Please let me know if someone does this analysis. ====================== From jhein at timing.com Thu Mar 12 11:55:07 2009 From: jhein at timing.com (John Hein) Date: Thu Mar 12 11:55:16 2009 Subject: usb/122539: kernel panic: ohci_abort_xfer: not in process context Message-ID: <18873.18933.723897.835863@gromit.timing.com> Note: this is not specific to ohci or the device originally used in this PR. The problem is more generic. This happens for us when hardware flow control is turned on when using a usb serial device (specifically an ftdi based one). Eventually if hardware flow has to kick in and RTS is to be set, uftdi_set() is called in uftdi.c (old usb stack). In uftdi_set() there is this... (void)usbd_do_request(ucom->sc_udev, &req, NULL); Since we're calling this from the interrupt context, the response to the request times out (because the reply is not processed), the ohci_abort_xfer which performas the panic because we're not in the process context. Here is a patch that uses the usbd_do_request_async() call (instead of the synchronous version) to assert flow control when the input buffer reaches the highwater mark (which is detected from within interupt context). (patch against today's version of uftdi.c in the old usb stack) Index: sys/legacy/dev/usb/uftdi.c =================================================================== RCS file: /base/FreeBSD-CVS/src/sys/legacy/dev/usb/uftdi.c,v retrieving revision 1.1 diff -u -p -r1.1 uftdi.c --- uftdi.c 23 Feb 2009 18:16:17 -0000 1.1 +++ uftdi.c 12 Mar 2009 17:34:27 -0000 @@ -557,7 +557,7 @@ uftdi_set(void *vsc, int portno, int reg DPRINTFN(2,("uftdi_set: reqtype=0x%02x req=0x%02x value=0x%04x " "index=0x%04x len=%d\n", req.bmRequestType, req.bRequest, UGETW(req.wValue), UGETW(req.wIndex), UGETW(req.wLength))); - (void)usbd_do_request(ucom->sc_udev, &req, NULL); + (void)usbd_do_request_async(ucom->sc_udev, &req, NULL); } static int This is not specific to FTDI devices. It would probably be better to handle this in the usb serial layer. Whatever better fix someone comes up with should be merged to 7.x if possible (and 6). I have not yet looked to see if the new usb stack has the same problem. Please let me know if someone does this analysis. From ml-freebsd at bettercom.de Thu Mar 12 23:00:08 2009 From: ml-freebsd at bettercom.de (Martin Lesser) Date: Thu Mar 12 23:00:14 2009 Subject: usb/132594: USB subsystem causes page fault and crashes Message-ID: <200903130558.n2D5wpeQ058261@www.freebsd.org> >Number: 132594 >Category: usb >Synopsis: USB subsystem causes page fault and crashes >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Mar 13 06:00:07 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Martin Lesser >Release: 7.1-RELEASE >Organization: >Environment: FreeBSD fs.bettercom.de 7.1-RELEASE FreeBSD 7.1-RELEASE #4: Thu Jan 15 10:42:38 CET 2009 root@fs.bettercom.de:/usr/obj/usr/src/sys/FSKERNEL i386 >Description: Infrequently the system crashes when - printing to an USB-printer - inserting or removing USB-sticks I have two savecores from such crashes (lines #7 and #8 are probably the problematic ones?): (kgdb) backtrace #0 doadump () at pcpu.h:196 #1 0xc054e2b3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc054e4be in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc078e38c in trap_fatal (frame=0xe5aeac0c, eva=0) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc078e610 in trap_pfault (frame=0xe5aeac0c, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc078efa9 in trap (frame=0xe5aeac0c) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc0777d4b in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc04d7419 in usbd_setup_xfer (xfer=0x0, pipe=0x0, priv=0xc56ed600, buffer=0xc805c000, length=4096, flags=5, timeout=10, callback=0xc09d6480 ) at /usr/src/sys/dev/usb/usbdi.c:547 #8 0xc09d646d in ulpt_tick (xsc=0xc56ed600) at /usr/src/sys/modules/ulpt/../../dev/usb/ulpt.c:773 #9 0xc055fe07 in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:274 #10 0xc052e19b in ithread_loop (arg=0xc549f830) at /usr/src/sys/kern/kern_intr.c:1088 #11 0xc052adc6 in fork_exit (callout=0xc052dff0 , arg=0xc549f830, frame=0xe5aead38) at /usr/src/sys/kern/kern_fork.c:804 #12 0xc0777dc0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 What else information can I submit to help to solve this problem? >How-To-Repeat: >Fix: Not using USB-devices on my system ;-) >Release-Note: >Audit-Trail: >Unformatted: From rwatson at FreeBSD.org Fri Mar 13 04:37:58 2009 From: rwatson at FreeBSD.org (Robert Watson) Date: Fri Mar 13 04:38:05 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: <20090217052121.GB86244@weongyo.cdnetworks.kr> References: <20090217052121.GB86244@weongyo.cdnetworks.kr> Message-ID: On Tue, 17 Feb 2009, Weongyo Jeong wrote: >> As you know, I've been gradually working to eliminate all non-MPSAFE >> network device driver infrastructure for 8.0, having removed non-MPSAFE >> network protocol infrastructure in 7.0. In reviewing remaining drivers >> using IFF_NEEDSGIANT, I spotted this in the NDIS code: ... >> Having taken a glance, it looks like this was added specifically to support >> USB devices attached via NDIS. > > AFAIK all of usb wireless drivers had it so I couldn't avoid it when I had > implemented. > >> With the new USB code, are NDIS drivers still supported? > > I think that it would be supported at 8.0 > >> And in the new world order, is this IFF_NEEDSGIANT still required? > > Probably we can remove the IFF_NEEDSGIANT flags at the new USB code. > >> Can I simply remove it once the old USB code is on the way out the door? > > IMHO yes I think. Dear all: A few weeks have passed, so I wanted to check in and see how this project was going -- are we at a point yet where removing IFF_NEEDSGIANT won't cause significant loss of functionality? Thanks, Robert N M Watson Computer Laboratory University of Cambridge From hselasky at freebsd.org Fri Mar 13 07:37:56 2009 From: hselasky at freebsd.org (Hans Petter Selasky) Date: Fri Mar 13 07:38:33 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: References: <20090217052121.GB86244@weongyo.cdnetworks.kr> Message-ID: <200903131440.22224.hselasky@freebsd.org> On Friday 13 March 2009, Robert Watson wrote: > On Tue, 17 Feb 2009, Weongyo Jeong wrote: > >> As you know, I've been gradually working to eliminate all non-MPSAFE > >> network device driver infrastructure for 8.0, having removed non-MPSAFE > >> network protocol infrastructure in 7.0. In reviewing remaining drivers > >> using IFF_NEEDSGIANT, I spotted this in the NDIS code: > > ... > > >> Having taken a glance, it looks like this was added specifically to > >> support USB devices attached via NDIS. > > > > AFAIK all of usb wireless drivers had it so I couldn't avoid it when I > > had implemented. > > > >> With the new USB code, are NDIS drivers still supported? > > > > I think that it would be supported at 8.0 > > > >> And in the new world order, is this IFF_NEEDSGIANT still required? > > > > Probably we can remove the IFF_NEEDSGIANT flags at the new USB code. > > > >> Can I simply remove it once the old USB code is on the way out the door? > > > > IMHO yes I think. > > Dear all: > > A few weeks have passed, so I wanted to check in and see how this project > was going -- are we at a point yet where removing IFF_NEEDSGIANT won't > cause significant loss of functionality? I think both NDIS USB and USB Ethernet/WLAN drivers have been made Giant-free. --HPS From hselasky at freebsd.org Fri Mar 13 07:37:56 2009 From: hselasky at freebsd.org (Hans Petter Selasky) Date: Fri Mar 13 07:38:34 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: References: <20090217052121.GB86244@weongyo.cdnetworks.kr> Message-ID: <200903131440.22224.hselasky@freebsd.org> On Friday 13 March 2009, Robert Watson wrote: > On Tue, 17 Feb 2009, Weongyo Jeong wrote: > >> As you know, I've been gradually working to eliminate all non-MPSAFE > >> network device driver infrastructure for 8.0, having removed non-MPSAFE > >> network protocol infrastructure in 7.0. In reviewing remaining drivers > >> using IFF_NEEDSGIANT, I spotted this in the NDIS code: > > ... > > >> Having taken a glance, it looks like this was added specifically to > >> support USB devices attached via NDIS. > > > > AFAIK all of usb wireless drivers had it so I couldn't avoid it when I > > had implemented. > > > >> With the new USB code, are NDIS drivers still supported? > > > > I think that it would be supported at 8.0 > > > >> And in the new world order, is this IFF_NEEDSGIANT still required? > > > > Probably we can remove the IFF_NEEDSGIANT flags at the new USB code. > > > >> Can I simply remove it once the old USB code is on the way out the door? > > > > IMHO yes I think. > > Dear all: > > A few weeks have passed, so I wanted to check in and see how this project > was going -- are we at a point yet where removing IFF_NEEDSGIANT won't > cause significant loss of functionality? I think both NDIS USB and USB Ethernet/WLAN drivers have been made Giant-free. --HPS From jlevine at boulder.nist.gov Fri Mar 13 09:15:06 2009 From: jlevine at boulder.nist.gov (Judah Levine) Date: Fri Mar 13 09:15:13 2009 Subject: usb/132066: [ukbd] Keyboard failure USB keyboard DELL 760 In-Reply-To: <200902251049.n1PAnWXo002536@freefall.freebsd.org> References: <200902251049.n1PAnWXo002536@freefall.freebsd.org> Message-ID: <7.0.0.16.2.20090313100539.023d8488@boulder.nist.gov> Hello, I have fixed this problem, but I don't understand why it works. I made the following changes to the config file and re-built the kernel: 1. remove device atkb 2. add device puc 3. add: options UKBD_DFLT_KEYMAP options UKBD_DFLT_KEYMAP=us.unix I have installed the same software with USB keyboards on many different systems, and this is the first time that I had to do this. The system now works correctly both using the command-line and X-windows. Is it possible that the keyboard is not being recognized correctly during the bootstrap process? Judah Levine Time and Frequency Division NIST Boulder From lintzuyau at gmail.com Fri Mar 13 10:28:22 2009 From: lintzuyau at gmail.com (tzu-yau Lin) Date: Fri Mar 13 10:28:28 2009 Subject: How to add a USB vender in sys/dev/usb/usbdevs In-Reply-To: <200903121857.32241.hselasky@c2i.net> References: <200903121857.32241.hselasky@c2i.net> Message-ID: On Fri, Mar 13, 2009 at 1:57 AM, Hans Petter Selasky wrote: > > > In FreeBSD-7 you need to load if_udav before the kernel is loaded, else > ugen > will grab the device. > > Try this: > > echo "if_udav_load=YES" >> /boot/loader.conf > > cat /boot/loader.conf > > > --HPS > Dear HPS and all: I've found the solution. The problem is due to the vendor ID and product ID incorrect. I wrote a patch and now it works. 2 files need to be changed. It seems working now. ========================= if_udav.c.patch ========================= --- if_udav.c 2009-03-14 00:56:17.000000000 +0800 +++ if_udav.c.new 2009-03-14 00:56:17.000000000 +0800 @@ -260,11 +260,9 @@ static const struct udav_type { {{ USB_VENDOR_COREGA, USB_PRODUCT_COREGA_FETHER_USB_TXC }, 0}, /* ShanTou ST268 USB NIC */ {{ USB_VENDOR_SHANTOU, USB_PRODUCT_SHANTOU_ST268 }, 0}, -#if 0 - /* DAVICOM DM9601 Generic? */ - /* XXX: The following ids was obtained from the data sheet. */ - {{ 0x0a46, 0x9601 }, 0}, -#endif + /* DAVICOM DM9601 Generic */ + {{ USB_VENDOR_DAVICOM, USB_PRODUCT_DAVICOM_DM9601 }, 0}, + }; #define udav_lookup(v, p) ((const struct udav_type *)usb_lookup(udav_devs, v, p)) ========================= usbdevs.patch ========================= --- usbdevs 2009-03-14 00:56:25.000000000 +0800 +++ usbdevs.new 2009-03-14 00:56:25.000000000 +0800 @@ -155,7 +155,7 @@ vendor YAMAHA 0x0499 YAMAHA vendor COMPAQ 0x049f Compaq vendor HITACHI 0x04a4 Hitachi vendor ACERP 0x04a5 Acer Peripherals -vendor DAVICOM 0x04a6 Davicom +/*vendor DAVICOM 0x04a6 Davicom*/ vendor VISIONEER 0x04a7 Visioneer vendor CANON 0x04a9 Canon vendor NIKON 0x04b0 Nikon @@ -534,6 +534,7 @@ vendor VTECH 0x0f88 VTech vendor FALCOM 0x0f94 Falcom Wireless Communications GmbH vendor RIM 0x0fca Research In Motion vendor DYNASTREAM 0x0fcf Dynastream Innovations +vendor DAVICOM 0x0fe6 Davicom vendor QUALCOMM 0x1004 Qualcomm vendor DESKNOTE 0x1019 Desknote vendor GIGABYTE 0x1044 GIGABYTE @@ -1076,6 +1077,10 @@ product CYPRESS FMRADIO 0x1002 FM Radio product CYPRESS USBRS232 0x5500 USB-RS232 Interface product CYPRESS SLIM_HUB 0x6560 Slim Hub +/* Davicom Semiconductor products */ +/*product DAVICOM DM9601 0x9601 DM9601 USB NIC*/ +product DAVICOM DM9601 0x8101 DM9601 USB NIC + /* Daisy Technology products */ product DAISY DMC 0x6901 USB MultiMedia Reader From man at email.com.ua Fri Mar 13 16:11:13 2009 From: man at email.com.ua (man@email.com.ua) Date: Fri Mar 13 16:11:20 2009 Subject: support for logitech mx610 mouse Message-ID: <200903140114.22511.man@email.com.ua> Hi. I have logitech mx610. This mouse have a lot of buttons, but not all of this buttons work (volume control, mail, im and tilt wheel). ums0: on usbus0 ums0: 16 buttons and [XYZ] coordinates kldunload ums kldunload uhid kldload uhid uhid0: on usbus0 uhid1: on usbus0 usbhidctl -f /dev/uhid0 -ar Report descriptor: Collection page=Generic_Desktop usage=Mouse Collection page=Generic_Desktop usage=Pointer Input size=1 count=1 page=Button usage=Button_1, logical range 0..1 Input size=1 count=1 page=Button usage=Button_2, logical range 0..1 Input size=1 count=1 page=Button usage=Button_3, logical range 0..1 Input size=1 count=1 page=Button usage=Button_4, logical range 0..1 Input size=1 count=1 page=Button usage=Button_5, logical range 0..1 Input size=1 count=1 page=Button usage=Button_6, logical range 0..1 Input size=1 count=1 page=Button usage=Button_7, logical range 0..1 Input size=1 count=1 page=Button usage=Button_8, logical range 0..1 Input size=1 count=1 page=Button usage=Button_9, logical range 0..1 Input size=1 count=1 page=Button usage=Button_10, logical range 0..1 Input size=1 count=1 page=Button usage=Button_11, logical range 0..1 Input size=1 count=1 page=Button usage=Button_12, logical range 0..1 Input size=1 count=1 page=Button usage=Button_13, logical range 0..1 Input size=1 count=1 page=Button usage=Button_14, logical range 0..1 Input size=1 count=1 page=Button usage=Button_15, logical range 0..1 Input size=1 count=1 page=Button usage=Button_16, logical range 0..1 Input size=12 count=1 page=Generic_Desktop usage=X, logical range -2047..2047 Input size=12 count=1 page=Generic_Desktop usage=Y, logical range -2047..2047 Input size=8 count=1 page=Generic_Desktop usage=Wheel, logical range -127..127 Input size=8 count=1 page=Consumer usage=AC_Pan, logical range -127..127 End collection End collection Total input size 7 bytes Total output size 0 bytes Total feature size 0 bytes usbhidctl: USB_SET_IMMED: Device not configured usbhidctl -f /dev/uhid1 -ar Report descriptor: Total input size 0 bytes Total output size 0 bytes Total feature size 0 bytes usbhidctl: USB_SET_IMMED: Device not configured usbconfig -u 0 -a 2 do_request 0x81 0x06 0x2200 1 0x100 REQUEST = <0x05 0x0c 0x09 0x01 0xa1 0x01 0x85 0x03 0x75 0x10 0x95 0x02 0x15 0x01 0x26 0x8c 0x02 0x19 0x01 0x2a 0x8c 0x02 0x81 0x60 0xc0 0x06 0x00 0xff 0x09 0x01 0xa1 0x01 0x85 0x10 0x75 0x08 0x95 0x06 0x15 0x00 0x26 0xff 0x00 0x09 0x01 0x81 0x00 0x09 0x01 0x91 0x00 0xc0 0x06 0x00 0xff 0x09 0x02 0xa1 0x01 0x85 0x11 0x75 0x08 0x95 0x13 0x15 0x00 0x26 0xff 0x00 0x09 0x02 0x81 0x00 0x09 0x02 0x91 0x00 0xc0> I see from this report, what tilt wheel is defined as AC_Pan (expected button) - this is not supported by Xorg. Can I remap this? All of the additional buttons would have to determine at uhid1, but not decided. This can be done? Thanks in advance. You gave hope that the usb subsystem will be released at a high level of implementation. IMHO your job - is a big step forward for support FreeBSD at desktop. From hselasky at c2i.net Sat Mar 14 01:30:56 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Mar 14 01:31:04 2009 Subject: support for logitech mx610 mouse In-Reply-To: <200903140114.22511.man@email.com.ua> References: <200903140114.22511.man@email.com.ua> Message-ID: <200903140933.24547.hselasky@c2i.net> On Saturday 14 March 2009, man@email.com.ua wrote: > Hi. > I have logitech mx610. This mouse have a lot of buttons, but not all of > this buttons work (volume control, mail, im and tilt wheel). > > ums0: on usbus0 > ums0: 16 buttons and [XYZ] coordinates > > kldunload ums > kldunload uhid > kldload uhid > > uhid0: on usbus0 > uhid1: on usbus0 > > usbhidctl -f /dev/uhid0 -ar > Report descriptor: > Collection page=Generic_Desktop usage=Mouse > Collection page=Generic_Desktop usage=Pointer > Input size=1 count=1 page=Button usage=Button_1, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_2, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_3, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_4, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_5, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_6, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_7, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_8, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_9, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_10, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_11, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_12, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_13, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_14, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_15, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_16, logical range 0..1 > Input size=12 count=1 page=Generic_Desktop usage=X, logical range > -2047..2047 Input size=12 count=1 page=Generic_Desktop usage=Y, logical > range -2047..2047 Input size=8 count=1 page=Generic_Desktop usage=Wheel, > logical range -127..127 Input size=8 count=1 page=Consumer usage=AC_Pan, > logical range -127..127 End collection > End collection > Total input size 7 bytes > Total output size 0 bytes > Total feature size 0 bytes > usbhidctl: USB_SET_IMMED: Device not configured > > usbhidctl -f /dev/uhid1 -ar > Report descriptor: > Total input size 0 bytes > Total output size 0 bytes > Total feature size 0 bytes > usbhidctl: USB_SET_IMMED: Device not configured > > usbconfig -u 0 -a 2 do_request 0x81 0x06 0x2200 1 0x100 > REQUEST = <0x05 0x0c 0x09 0x01 0xa1 0x01 0x85 0x03 0x75 0x10 0x95 0x02 0x15 > 0x01 0x26 0x8c 0x02 0x19 0x01 0x2a 0x8c 0x02 0x81 0x60 0xc0 0x06 0x00 0xff > 0x09 0x01 0xa1 0x01 0x85 0x10 0x75 0x08 0x95 0x06 0x15 0x00 0x26 0xff 0x00 > 0x09 0x01 0x81 0x00 0x09 0x01 0x91 0x00 0xc0 0x06 0x00 0xff 0x09 0x02 0xa1 > 0x01 0x85 0x11 0x75 0x08 0x95 0x13 0x15 0x00 0x26 0xff 0x00 0x09 0x02 0x81 > 0x00 0x09 0x02 0x91 0x00 0xc0> > > > I see from this report, what tilt wheel is defined as AC_Pan (expected > button) - this is not supported by Xorg. Can I remap this? You can re-map in /sys/dev/usb/input/ums.c > All of the > additional buttons would have to determine at uhid1, but not decided. This > can be done? I need some samples of the data format, when you a) move mouse b) press buttons. Can you write a small C-program? f = open("/dev/uhid0", O_RDONLY); if (f < 0) return; uint8_t buf[256]; int len; while (1) { len = read(f, buf, sizeof(buf)); if (len < 0) break; } dump buf in HEX. --HPS > > Thanks in advance. > > You gave hope that the usb subsystem will be released at a high level of > implementation. IMHO your job - is a big step forward for support FreeBSD > at desktop. From man at email.com.ua Sat Mar 14 03:59:20 2009 From: man at email.com.ua (man@email.com.ua) Date: Sat Mar 14 03:59:27 2009 Subject: support for logitech mx610 mouse In-Reply-To: <200903140933.24547.hselasky@c2i.net> References: <200903140114.22511.man@email.com.ua> <200903140933.24547.hselasky@c2i.net> Message-ID: <200903141303.11883.man@email.com.ua> > I need some samples of the data format, when you a) move mouse b) press > buttons. Can you write a small C-program? Of course, but to my surprise, the program does not read any data from uhid0. I tried an even more simple test cat /dev/uhid0 ^C Nothing But on FreeBSD 7.1 - nice read (see attached file, result of cat) >a) move mouse b) press buttons. Only press additional buttons expected. This mouse create 2 uhid devices - first report about moving and press standard button (hidden when loaded ums), second - about additional buttons. -------------- next part -------------- A non-text attachment was scrubbed... Name: uhid0 Type: application/octet-stream Size: 150 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090314/17ad596c/uhid0.obj From hselasky at c2i.net Sat Mar 14 04:02:52 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Mar 14 04:02:58 2009 Subject: support for logitech mx610 mouse In-Reply-To: <200903141303.11883.man@email.com.ua> References: <200903140114.22511.man@email.com.ua> <200903140933.24547.hselasky@c2i.net> <200903141303.11883.man@email.com.ua> Message-ID: <200903141205.20848.hselasky@c2i.net> Try open up the endpoint(s) instead: see /dev/usb/xxx --HPS On Saturday 14 March 2009, man@email.com.ua wrote: > > I need some samples of the data format, when you a) move mouse b) press > > buttons. Can you write a small C-program? > > Of course, but to my surprise, the program does not read any data from > uhid0. I tried an even more simple test > cat /dev/uhid0 > ^C > Nothing > > But on FreeBSD 7.1 - nice read (see attached file, result of cat) > > >a) move mouse b) press buttons. > > Only press additional buttons expected. This mouse create 2 uhid devices - > first report about moving and press standard button (hidden when loaded > ums), second - about additional buttons. From man at email.com.ua Sat Mar 14 04:10:02 2009 From: man at email.com.ua (man@email.com.ua) Date: Sat Mar 14 04:10:07 2009 Subject: support for logitech mx610 mouse In-Reply-To: <200903141205.20848.hselasky@c2i.net> References: <200903140114.22511.man@email.com.ua> <200903141303.11883.man@email.com.ua> <200903141205.20848.hselasky@c2i.net> Message-ID: <200903141313.53345.man@email.com.ua> > Try open up the endpoint(s) instead: > > see /dev/usb/xxx Inconclusive :( From hselasky at c2i.net Sat Mar 14 04:14:23 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Mar 14 04:14:30 2009 Subject: support for logitech mx610 mouse In-Reply-To: <200903141313.53345.man@email.com.ua> References: <200903140114.22511.man@email.com.ua> <200903141205.20848.hselasky@c2i.net> <200903141313.53345.man@email.com.ua> Message-ID: <200903141216.44932.hselasky@c2i.net> On Saturday 14 March 2009, man@email.com.ua wrote: > > Try open up the endpoint(s) instead: > > > > see /dev/usb/xxx > > Inconclusive :( The format is: /dev/usb/X.Y.Z X is USB BUS Y is device index Z is endpoint & 0xF The the usbconfig's dump_curr_config_desc which endpoint belongs to your driver. Also see the show_ifdrv command to see which driver is connected to which interface. --HPS From man at alkar.net Sat Mar 14 05:11:46 2009 From: man at alkar.net (Artyom Mirgorodsky) Date: Sat Mar 14 05:23:22 2009 Subject: support for logitech mx610 mouse In-Reply-To: <200903141216.44932.hselasky@c2i.net> References: <200903140114.22511.man@email.com.ua> <200903141313.53345.man@email.com.ua> <200903141216.44932.hselasky@c2i.net> Message-ID: <200903141345.36631.man@alkar.net> > The format is: > > /dev/usb/X.Y.Z > > X is USB BUS > Y is device index > Z is endpoint & 0xF > > The the usbconfig's dump_curr_config_desc which endpoint belongs to your > driver. Also see the show_ifdrv command to see which driver is connected to > which interface. I understand that. But I can't read from this devices does. usbconfig show_ifdrv ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.1.0: uhub0: ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.1.0: uhub1: ugen0.2: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen0.2.0: ums0: usbconfig dump_curr_config_desc ugen0.2: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr= ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x003b bNumInterfaces = 0x0002 bConfigurationValue = 0x0001 iConfiguration = 0x0004 bmAttributes = 0x00a0 bMaxPower = 0x0031 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x0000 Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x43, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0008 bInterval = 0x000a bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0000 Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x4f, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 bmAttributes = 0x0003 wMaxPacketSize = 0x0008 bInterval = 0x000a bRefresh = 0x0000 bSynchAddress = 0x0000 I'm unload ums and reload uhid then try read again: uhid0: on usbus0 uhid1: on usbus0 cat /dev/usb/0.2.1 ^C cat /dev/usb/0.2.2 ^C cat /dev/uhid0 0O??_?o?o??o?o?@?O?_?_?O?O???/???????P??????????? ??? P ``p?`P@ ??????????? P ?/?????O??O???/????????????????????????????????? cat /dev/uhid1 ^C Only mouse moving produce any data from uhid. From hselasky at c2i.net Sat Mar 14 05:34:24 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Mar 14 05:34:31 2009 Subject: support for logitech mx610 mouse In-Reply-To: <200903141345.36631.man@alkar.net> References: <200903140114.22511.man@email.com.ua> <200903141216.44932.hselasky@c2i.net> <200903141345.36631.man@alkar.net> Message-ID: <200903141336.51769.hselasky@c2i.net> On Saturday 14 March 2009, Artyom Mirgorodsky wrote: > > The format is: > > > > /dev/usb/X.Y.Z > > > > X is USB BUS > > Y is device index > > Z is endpoint & 0xF > > > > The the usbconfig's dump_curr_config_desc which endpoint belongs to your > > driver. Also see the show_ifdrv command to see which driver is connected > > to which interface. > > I understand that. But I can't read from this devices does. > > usbconfig show_ifdrv > ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) > pwr=ON ugen0.1.0: uhub0: addr 1> ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=ON ugen1.1.0: uhub1: 2.00/1.00, addr 1> ugen0.2: at usbus0, cfg=0 > md=HOST spd=LOW (1.5Mbps) pwr=ON ugen0.2.0: ums0: class 0/0, rev 2.00/42.00, addr 2> > > > usbconfig dump_curr_config_desc > ugen0.2: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) > pwr= ON > > > Configuration index 0 > > bLength = 0x0009 > bDescriptorType = 0x0002 > wTotalLength = 0x003b > bNumInterfaces = 0x0002 > bConfigurationValue = 0x0001 > iConfiguration = 0x0004 > bmAttributes = 0x00a0 > bMaxPower = 0x0031 > > Interface 0 > bLength = 0x0009 > bDescriptorType = 0x0004 > bInterfaceNumber = 0x0000 > bAlternateSetting = 0x0000 > bNumEndpoints = 0x0001 > bInterfaceClass = 0x0003 > bInterfaceSubClass = 0x0001 > bInterfaceProtocol = 0x0002 > iInterface = 0x0000 > > Additional Descriptor > > bLength = 0x09 > bDescriptorType = 0x21 > bDescriptorSubType = 0x11 > RAW dump: > 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x43, > 0x08 | 0x00 > > Endpoint 0 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0081 > bmAttributes = 0x0003 > wMaxPacketSize = 0x0008 > bInterval = 0x000a > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > > Interface 1 > bLength = 0x0009 > bDescriptorType = 0x0004 > bInterfaceNumber = 0x0001 > bAlternateSetting = 0x0000 > bNumEndpoints = 0x0001 > bInterfaceClass = 0x0003 > bInterfaceSubClass = 0x0000 > bInterfaceProtocol = 0x0000 > iInterface = 0x0000 > > Additional Descriptor > > bLength = 0x09 > bDescriptorType = 0x21 > bDescriptorSubType = 0x11 > RAW dump: > 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x4f, > 0x08 | 0x00 > > Endpoint 0 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0082 > bmAttributes = 0x0003 > wMaxPacketSize = 0x0008 > bInterval = 0x000a > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > I'm unload ums and reload uhid then try read again: > uhid0: on usbus0 > uhid1: on usbus0 > > cat /dev/usb/0.2.1 > ^C > cat /dev/usb/0.2.2 > ^C > > cat /dev/uhid0 > 0O??_?o?o??o?o?@?O?_?_?O?O???/???????P??????????? ??? > P ``p?`P@ ??????????? P > ?/?????O??O???/????????????????????????????????? cat /dev/uhid1 > ^C > > Only mouse moving produce any data from uhid. Can you get this data dumped into HEX ? --HPS From man at email.com.ua Sat Mar 14 05:56:57 2009 From: man at email.com.ua (Artyom Mirgorodsky) Date: Sat Mar 14 05:57:04 2009 Subject: support for logitech mx610 mouse In-Reply-To: <200903141336.51769.hselasky@c2i.net> References: <200903140114.22511.man@email.com.ua> <200903141345.36631.man@alkar.net> <200903141336.51769.hselasky@c2i.net> Message-ID: <200903141500.48042.man@email.com.ua> > Can you get this data dumped into HEX ? See attached file -------------- next part -------------- 1 0 0 F0 FF 0 0 0 0 46 A0 FF 0 0 0 0 2 0 0 0 0 0 0 3 0 0 0 0 0 0 4 0 0 0 0 0 0 4 10 0 0 0 0 0 5 20 0 0 0 0 0 7 20 0 0 0 0 0 10 60 0 0 0 0 0 A 50 0 0 0 0 0 B 40 0 0 0 0 0 9 60 0 0 0 0 0 D 40 0 0 0 0 0 9 40 0 0 0 0 0 7 40 0 0 0 0 0 8 50 0 0 0 0 0 E 40 0 0 0 0 0 16 C0 0 0 0 0 0 A 70 0 0 0 0 0 7 70 0 0 0 0 0 7 80 0 0 0 0 0 6 90 0 0 0 0 0 4 80 0 0 0 0 0 4 A0 0 0 0 0 0 1 A0 0 0 0 0 0 3 20 1 0 0 0 0 0 90 0 0 0 0 0 FF 8F 0 0 0 0 0 FE 7F 0 0 0 0 0 FC 7F 0 0 0 0 0 FB 6F 0 0 0 0 0 F9 5F 0 0 0 0 0 F8 4F 0 0 0 0 0 F6 3F 0 0 0 0 0 EB 5F 0 0 0 0 0 F4 1F 0 0 0 0 0 F4 F 0 0 0 0 0 F3 FF FF 0 0 0 0 F3 DF FF 0 0 0 0 F3 CF FF 0 0 0 0 F5 BF FF 0 0 0 0 F4 AF FF 0 0 0 0 F5 8F FF 0 0 0 0 EE DF FE 0 0 0 0 F9 5F FF 0 0 0 0 F9 3F FF 0 0 0 0 FB 2F FF 0 0 0 0 FC 1F FF 0 0 0 0 FD 2F FF 0 0 0 0 FE 2F FF 0 0 0 0 0 30 FF 0 0 0 0 0 40 FF 0 0 0 0 1 A0 FE 0 0 0 0 2 60 FF 0 0 0 0 3 70 FF 0 0 0 0 3 70 FF 0 0 0 0 4 90 FF 0 0 0 0 5 90 FF 0 0 0 0 5 A0 FF 0 0 0 0 7 C0 FF 0 0 0 0 9 C0 FF 0 0 0 0 16 A0 FF 0 0 0 0 C F0 FF 0 0 0 0 F 0 0 0 0 0 0 F 0 0 0 0 0 0 11 20 0 0 0 0 0 C 0 0 0 0 0 0 9 E0 FF 0 0 0 0 8 90 FF 0 0 0 0 A 70 FF 0 0 0 0 0 30 FF 0 0 0 0 1 70 FF 0 0 0 0 0 C0 FF 0 0 0 0 0 E0 FF 0 0 0 0 FE F 0 0 0 0 0 FE 1F 0 0 0 0 0 FE 2F 0 0 0 0 0 FD 3F 0 0 0 0 0 F7 5F 0 0 0 0 0 FB 2F 0 0 0 0 0 FB 3F 0 0 0 0 0 FC 1F 0 0 0 0 0 FD 2F 0 0 0 0 0 FD 1F 0 0 0 0 0 FE F 0 0 0 0 0 FE EF FF 0 0 0 0 FF FF FF 0 0 0 0 0 F0 FF 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 FF 1F 0 0 0 0 0 FC 4F 0 0 0 0 0 FC 2F 0 0 0 0 0 FD 2F 0 0 0 0 0 FD 2F 0 0 0 0 0 FE F 0 0 0 0 0 FF 1F 0 0 0 0 0 FF F 0 0 0 0 0 FF F 0 0 0 0 0 FE F 0 0 0 0 0 FB EF FF 0 0 0 0 FB EF FF 0 0 0 0 FB FF FF 0 0 0 0 FB DF FF 0 0 0 0 FB EF FF 0 0 0 0 FB FF FF 0 0 0 0 FC EF FF 0 0 0 0 FF F 0 0 0 0 0 FD FF FF 0 0 2 0 FE FF FF 0 0 2 0 FF F 0 0 0 1 0 0 0 0 0 0 1 0 0 10 0 0 0 1 0 0 10 0 0 0 3 0 0 10 0 0 0 3 0 1 30 0 0 0 3 0 0 30 0 0 0 2 0 2 50 0 0 0 2 0 1 50 0 0 0 2 0 3 50 0 0 0 2 0 2 30 0 0 0 2 0 1 30 0 0 0 2 0 1 20 0 0 0 2 0 3 40 0 0 0 2 0 1 20 0 0 0 2 0 1 20 0 0 0 2 0 1 10 0 0 0 2 0 1 10 0 0 0 2 0 0 10 0 0 0 2 0 1 10 0 0 0 3 0 2 20 0 0 0 1 0 0 10 0 0 0 1 0 0 10 0 0 0 1 0 FE FF FF 0 0 1 0 FC FF FF 0 0 1 0 FC DF FF 0 0 1 0 FC DF FF 0 0 1 0 FD CF FF 0 0 0 0 FC BF FF 0 0 0 0 FD EF FF 0 0 0 0 FE EF FF 0 0 0 0 FF DF FF 0 0 0 0 FF EF FF 0 0 0 0 FD 8F FF 0 0 0 0 FF CF FF 0 0 0 0 FE CF FF 0 0 0 0 FF CF FF 0 0 0 0 FF DF FF 0 0 0 0 FF EF FF 0 0 0 0 FF EF FF 0 0 0 0 0 E0 FF 0 0 0 0 0 F0 FF 0 0 0 0 0 F0 FF 0 0 0 0 2 F0 FF 0 0 0 0 2 E0 FF 0 0 0 0 4 E0 FF 0 0 0 0 3 F0 FF 0 0 0 0 3 F0 FF 0 0 0 0 3 F0 FF 0 0 0 0 C F0 FF 0 0 0 0 5 0 0 0 0 1 0 7 0 0 0 0 1 0 8 20 0 0 0 1 0 A 20 0 0 0 1 0 A 40 0 0 0 1 0 B 60 0 0 0 1 0 B 60 0 0 0 1 0 C 80 0 0 0 1 0 B 70 0 0 0 1 0 12 C0 0 0 0 1 0 5 40 0 0 0 0 0 0 0 0 0 0 0 0 FE 1F 0 0 0 0 0 FF 1F 0 0 0 0 0 FD 2F 0 0 0 0 0 FD 2F 0 0 0 0 0 F6 3F 0 0 0 0 0 FC 2F 0 0 0 0 0 FB 2F 0 0 0 0 0 FA 2F 0 0 0 1 0 F9 2F 0 0 0 1 0 F7 2F 0 0 0 1 0 F6 2F 0 0 0 1 0 F6 3F 0 0 0 1 0 F6 1F 0 0 0 1 0 F6 2F 0 0 0 1 0 F6 2F 0 0 0 1 0 F0 1F 0 0 0 1 0 FB 1F 0 0 0 1 0 FC F 0 0 0 1 0 FF F 0 0 0 1 0 FF F 0 0 0 1 0 0 E0 FF 0 0 1 0 1 E0 FF 0 0 1 0 2 D0 FF 0 0 1 0 4 E0 FF 0 0 1 0 3 E0 FF 0 0 1 0 4 F0 FF 0 0 1 0 6 F0 FF 0 0 1 0 7 E0 FF 0 0 1 0 9 F0 FF 0 0 1 0 9 F0 FF 0 0 1 0 14 0 0 0 0 1 0 B 0 0 0 0 1 0 C 20 0 0 0 1 0 7 0 0 0 0 1 0 0 50 FF 0 0 1 0 FF AF FF 0 0 1 0 2 0 0 0 0 0 0 3 0 0 0 0 0 0 2 0 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 FD F 0 0 0 1 0 0 0 0 0 0 1 0 FF 1F 0 0 0 1 0 FF 1F 0 0 0 1 0 FF 1F 0 0 0 1 0 FD F 0 0 0 1 0 FC 2F 0 0 0 1 0 FB 3F 0 0 0 1 0 F9 3F 0 0 0 1 0 F1 4F 0 0 0 1 0 F8 2F 0 0 0 1 0 F8 1F 0 0 0 1 0 F9 F 0 0 0 1 0 F9 F 0 0 0 1 0 FA FF FF 0 0 1 0 FB FF FF 0 0 0 0 FB CF FF 0 0 0 0 0 E0 FF 0 0 0 0 FF FF FF 0 0 1 0 0 0 0 0 0 3 0 0 0 0 0 0 3 0 FF EF FF 0 0 3 0 FF DF FF 0 0 3 0 FF DF FF 0 0 3 0 FF AF FF 0 0 3 0 FF EF FF 0 0 3 0 0 D0 FF 0 0 1 0 FF DF FF 0 0 1 0 0 D0 FF 0 0 1 0 0 D0 FF 0 0 1 0 0 E0 FF 0 0 1 0 0 F0 FF 0 0 3 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 F0 FF 0 0 0 0 2 E0 FF 0 0 0 0 1 F0 FF 0 0 0 0 1 F0 FF 0 0 0 0 1 F0 FF 0 0 0 0 3 E0 FF 0 0 0 0 9 A0 FF 0 0 0 0 4 F0 FF 0 0 0 0 3 E0 FF 0 0 0 0 2 0 0 0 0 0 0 0 0 0 FF 0 0 0 0 0 0 FF 0 0 0 0 0 0 FF 0 0 0 0 0 0 FF 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 FF 0 0 0 0 0 0 FF 0 0 0 1 0 0 0 0 0 0 0 0 0 FF 0 0 0 1 0 0 0 0 0 0 0 0 0 FF 0 0 0 0 0 0 FF 0 0 0 1 10 0 0 0 0 0 1 30 0 0 0 0 0 1 20 0 FF 0 0 0 1 20 0 0 0 0 0 1 40 0 0 0 0 0 1 60 0 0 0 0 0 1 60 0 0 0 0 0 0 60 0 0 0 0 0 1 70 0 0 0 0 0 0 20 0 0 0 0 0 FF 1F 0 0 0 0 0 FE F 0 0 0 0 0 FD 1F 0 0 0 0 0 FB 1F 0 0 0 0 0 F2 F 0 0 0 0 0 FA F 0 1 0 0 0 F9 F 0 0 0 0 0 F9 F 0 1 0 0 0 F7 F 0 0 0 0 0 F6 EF FF 1 0 0 0 F6 FF FF 0 0 0 0 F6 EF FF 1 0 0 0 F6 EF FF 0 0 0 0 F6 EF FF 0 0 0 0 F6 CF FF 0 0 0 0 EF 9F FF 0 0 0 0 F9 CF FF 1 0 0 0 F8 DF FF 0 0 0 0 FA DF FF 0 0 0 0 FC FF FF 0 0 0 0 0 C0 FF 0 0 0 0 0 C0 FF 0 0 0 0 0 A0 FF 0 0 0 0 3 60 FF 0 0 0 0 4 B0 FF 0 0 0 0 4 B0 FF 0 0 0 0 5 C0 FF 0 0 0 0 8 B0 FF 0 0 0 0 9 C0 FF 0 0 0 0 B C0 FF 0 0 0 0 C D0 FF 0 0 0 0 E D0 FF 0 0 0 0 1D B0 FF 0 0 0 0 E F0 FF 0 0 0 0 D 0 0 0 0 0 0 B 0 0 FF 0 0 0 A 0 0 0 0 0 0 8 0 0 FF 0 0 0 7 0 0 0 0 0 0 4 10 0 0 0 0 0 1 10 0 FF 0 0 0 0 10 0 FF 0 0 0 0 20 0 0 0 0 0 FF 2F 0 0 0 0 0 FF 3F 0 0 0 0 0 FF 2F 0 0 0 0 0 FF 2F 0 0 0 0 0 FD 3F 0 0 0 0 0 FD 2F 0 0 0 0 0 FE 1F 0 0 0 0 0 FD 1F 0 0 0 0 0 FE 1F 0 0 0 0 0 FD F 0 0 0 0 0 FE F 0 0 0 0 0 FD F 0 1 0 0 0 FD F 0 0 0 0 0 FA EF FF 0 0 0 0 FD FF FF 1 0 0 0 FD F 0 0 0 0 0 FD FF FF 0 0 0 0 FE FF FF 0 0 0 0 FE FF FF 1 0 0 0 FF FF FF 0 0 0 0 FF F 0 0 0 0 0 FF FF FF 0 0 0 0 FD DF FF 0 0 0 0 FE FF FF 0 0 0 0 FF F 0 0 0 0 0 0 F0 FF 0 0 0 0 2 0 0 0 0 0 0 5 F0 FF 0 0 0 0 3 0 0 0 0 0 0 2 10 0 0 0 0 0 2 10 0 0 0 0 0 1 20 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 1 10 0 0 0 0 0 0 20 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 2 30 0 0 0 0 0 3 80 0 0 0 0 0 3 70 0 0 0 0 0 1 50 0 0 0 0 0 2 40 0 0 0 0 0 1 50 0 0 0 0 0 2 50 0 0 0 0 0 2 B0 0 0 0 0 0 1 60 0 0 0 0 0 0 50 0 0 0 0 0 1 90 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 0 30 0 0 0 0 0 0 30 0 0 0 0 0 0 30 0 0 0 0 0 0 20 0 0 0 0 0 0 30 0 0 0 0 0 0 F0 FF 0 0 0 0 0 F0 FF 0 0 0 0 0 E0 FF 0 0 0 0 0 D0 FF 0 0 0 0 0 C0 FF 0 0 0 0 0 F0 FF 0 0 0 0 0 F0 FF 0 0 0 0 FF EF FF 0 0 0 0 FF DF FF 0 0 0 0 0 E0 FF 0 0 0 0 FF CF FF 0 0 0 0 0 D0 FF 0 0 0 0 0 E0 FF 0 0 0 0 0 E0 FF 0 0 0 0 1 E0 FF 0 0 0 0 0 F0 FF 0 0 0 0 0 F0 FF 0 0 0 0 0 D0 FF 0 0 0 0 1 D0 FF 0 0 0 0 1 A0 FF 0 0 0 0 0 D0 FF 0 0 0 0 1 F0 FF 0 0 0 0 0 10 0 0 0 0 0 FF 1F 0 0 0 0 0 0 10 0 0 0 0 0 FE 2F 0 0 0 0 0 FE 2F 0 0 0 0 0 FF 2F 0 0 0 0 0 FE 3F 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 1 10 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 FE 6F 0 0 0 0 0 FF 2F 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 0 30 0 0 0 0 0 0 30 0 0 0 0 0 0 10 0 0 0 0 0 1 20 0 0 0 0 0 4 20 0 0 0 0 0 D 80 0 0 0 0 0 B 50 0 0 0 0 0 E 70 0 0 0 0 0 E 50 0 0 0 0 0 1A 90 0 0 0 0 0 9 30 0 0 0 0 0 8 20 0 0 0 0 0 5 20 0 0 0 0 0 0 10 0 0 0 0 0 FF 1F 0 0 0 0 0 FE 2F 0 0 0 0 0 FD 2F 0 0 0 0 0 FD 2F 0 0 0 0 0 FE 1F 0 0 0 0 0 FF F 0 0 0 0 0 FF FF FF 0 0 0 0 FF F 0 0 0 0 0 FE EF FF 0 0 0 0 FC EF FF 0 0 0 0 FA CF FF 0 0 0 0 FB EF FF 0 0 0 0 E4 5F FF 0 0 0 0 F5 BF FF 0 0 0 0 F7 BF FF 0 0 0 0 F8 CF FF 0 0 0 0 F9 BF FF 0 0 0 0 FC BF FF 0 0 0 0 FC AF FF 0 0 0 0 FE 9F FF 0 0 0 0 2 D0 FE 0 0 0 0 7 40 FF 0 0 0 0 9 30 FF 0 0 0 0 D 20 FF 0 0 0 0 E 30 FF 0 0 0 0 B 10 FF 0 0 0 0 D 40 FF 0 0 0 0 1A E0 FE 0 0 0 0 13 50 FF 0 0 0 0 6 D0 FF 0 0 0 0 1 0 0 0 0 0 0 0 20 0 0 0 0 0 0 30 0 0 0 0 0 FF 3F 0 0 0 0 0 FE 6F 0 0 0 0 0 FF 3F 0 0 0 0 0 0 20 0 0 0 0 0 FE 3F 0 0 0 0 0 FE 5F 0 0 0 0 0 F8 8F 0 0 0 0 0 FA 6F 0 0 0 0 0 F6 8F 0 0 0 0 0 FC 3F 0 0 0 0 0 FD 3F 0 0 0 0 0 FE 4F 0 0 0 0 0 FE 2F 0 0 0 0 0 FF 2F 0 0 0 0 0 FF F 0 0 0 0 0 0 10 0 0 0 0 0 FF F 0 0 0 0 0 2 E0 FF 0 0 0 0 2 F0 FF 0 0 0 0 2 D0 FF 0 0 0 0 1 E0 FF 0 0 0 0 0 F0 FF 0 0 0 0 FA F 0 0 0 0 0 FB F 0 0 0 0 0 FA F 0 0 0 0 0 FA F 0 0 0 0 0 FA F 0 0 0 0 0 FB FF FF 0 0 0 0 FC F 0 0 0 0 0 FD F 0 0 0 0 0 0 F0 FF 0 0 0 0 1 E0 FF 0 0 0 0 4 E0 FF 0 0 0 0 5 F0 FF 0 0 0 0 7 E0 FF 0 0 0 0 6 F0 FF 0 0 0 0 E F0 FF 0 0 0 0 8 F0 FF 0 0 0 0 9 F0 FF 0 0 0 0 A 0 0 0 0 0 0 9 F0 FF 0 0 0 0 7 30 0 0 0 0 0 5 20 0 0 0 0 0 6 30 0 0 0 0 0 9 20 0 0 0 0 0 1A 80 0 0 0 0 0 5 30 0 0 0 0 0 4 20 0 0 0 0 0 FF F 0 0 0 0 0 FD F 0 0 0 0 0 F4 1F 0 0 0 0 0 F9 1F 0 0 0 0 0 F9 1F 0 0 0 0 0 FA 1F 0 0 0 0 0 F6 F 0 0 0 0 0 FD 1F 0 0 0 0 0 FD F 0 0 0 0 0 FF F 0 0 0 0 0 FF F 0 0 0 0 0 FE F 0 0 0 0 0 FF F 0 0 0 0 0 FE F 0 0 0 0 0 FD 1F 0 0 0 0 0 FC 1F 0 0 0 0 0 F0 4F 0 0 0 0 0 EB 2F 0 0 0 0 0 F6 2F 0 0 0 0 0 F5 F 0 0 0 0 0 F6 1F 0 0 0 0 0 F8 1F 0 0 0 0 0 F8 F 0 0 0 0 0 FA F 0 0 0 0 0 FC F 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 30 0 0 0 0 0 1 30 0 0 0 0 0 1 40 0 0 0 0 0 1 40 0 0 0 0 0 2 40 0 0 0 0 0 6 60 0 0 0 0 0 8 70 0 0 0 0 0 D 70 0 0 0 0 0 D 60 0 0 0 0 0 1C B0 0 0 0 0 0 C 40 0 0 0 0 0 10 40 0 0 0 0 0 2 0 0 0 0 0 0 0 10 0 0 0 0 0 FF F 0 0 0 0 0 FF FF FF 0 0 0 0 FD FF FF 0 0 0 0 FD FF FF 0 0 0 0 FD F 0 0 0 0 0 FD FF FF 0 0 0 0 FB FF FF 0 0 0 0 FB FF FF 0 0 0 0 F9 FF FF 0 0 0 0 F8 EF FF 0 0 0 0 E3 BF FF 0 0 0 0 F6 EF FF 0 0 0 0 F9 FF FF 0 0 0 0 FA DF FF 0 0 0 0 FC CF FF 0 0 0 0 F9 BF FF 0 0 0 0 FB BF FF 0 0 0 0 F9 8F FF 0 0 0 0 0 F0 FF 0 0 0 0 FE FF FF 0 0 0 0 0 F0 FF 0 0 0 0 0 F0 FF 0 0 0 0 0 F0 FF 0 0 0 0 0 C0 FF 0 0 0 0 1 A0 FF 0 0 0 0 0 C0 FF 0 0 0 0 0 B0 FF 0 0 0 0 0 B0 FF 0 0 0 0 0 B0 FF 0 0 0 0 0 B0 FF 0 0 0 0 0 60 FF 0 0 0 0 0 C0 FF 0 0 0 0 0 B0 FF 0 0 0 0 3 60 FF 0 0 0 0 1 B0 FF 0 0 0 0 2 C0 FF 0 0 0 0 2 C0 FF 0 0 0 0 1 E0 FF 0 0 0 0 1 F0 FF 0 0 0 0 0 F0 FF 0 0 0 0 2 0 0 0 0 0 0 8 F0 FF 0 0 0 0 7 0 0 0 0 0 0 6 0 0 0 0 0 0 7 F0 FF 0 0 0 0 6 0 0 0 0 0 0 6 F0 FF 0 0 0 0 4 F0 FF 0 0 0 0 4 0 0 0 0 0 0 4 F0 FF 0 0 0 0 5 0 0 0 0 0 0 2 0 0 0 0 0 0 2 0 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 1 10 0 0 0 0 0 1 50 0 0 0 0 0 0 30 0 0 0 0 0 1 30 0 0 0 0 0 2 40 0 0 0 0 0 2 60 0 0 0 0 0 2 50 0 0 0 0 0 3 60 0 0 0 0 0 2 50 0 0 0 0 0 4 80 0 0 0 0 0 2 50 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 0 20 0 0 0 0 0 0 20 0 0 0 0 0 FF 4F 0 0 0 0 0 0 30 0 0 0 0 0 FF 4F 0 0 0 0 0 FF 6F 0 0 0 0 0 FF F 1 0 0 0 0 FF 8F 0 0 0 0 0 FF 8F 0 0 0 0 0 FF 8F 0 0 0 0 0 0 70 0 0 0 0 0 FF 6F 0 0 0 0 0 0 40 0 0 0 0 0 0 30 0 0 0 0 0 0 10 0 0 0 0 0 0 40 0 0 0 0 0 1 40 0 0 0 0 0 1 50 0 0 0 0 0 3 70 0 0 0 0 0 3 90 0 0 0 0 0 3 90 0 0 0 0 0 3 B0 0 0 0 0 0 3 B0 0 0 0 0 0 3 B0 0 0 0 0 0 3 A0 0 0 0 0 0 4 D0 0 0 0 0 0 0 20 0 0 0 0 0 1 30 0 0 0 0 0 0 30 0 0 0 0 0 1 50 0 0 0 0 0 1 50 0 0 0 0 0 2 C0 0 0 0 0 0 0 70 0 0 0 0 0 0 50 0 0 0 0 0 0 50 0 0 0 0 0 0 40 0 0 0 0 0 0 20 0 0 0 0 0 FF F 0 0 0 0 0 FE F 0 0 0 0 0 FE 1F 0 0 0 0 0 FF F 0 0 0 0 0 FF F 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 0 20 0 0 0 0 0 0 30 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 FF 1F 0 0 0 0 0 FF 2F 0 0 0 0 0 FF F 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 40 0 0 0 0 0 0 70 0 0 0 0 0 0 50 0 0 0 0 0 0 40 0 0 0 0 0 0 40 0 0 0 0 0 0 30 0 0 0 0 0 0 30 0 0 0 0 0 FE 1F 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 40 0 0 0 0 0 1 50 0 0 0 0 0 1 50 0 0 0 0 0 1 40 0 0 0 0 0 1 30 0 0 0 0 0 1 40 0 0 0 0 0 1 40 0 0 0 0 0 1 50 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 0 30 0 0 0 0 0 0 20 0 0 0 0 0 FF 2F 0 0 0 0 0 FF 4F 0 0 0 0 0 0 40 0 0 0 0 0 FE 9F 0 0 0 0 0 FE 7F 0 0 0 0 0 0 70 0 0 0 0 0 FE 8F 0 0 0 0 0 FF 9F 0 0 0 0 0 FE AF 0 0 0 0 0 0 A0 0 0 0 0 0 FF 8F 0 0 0 0 0 0 60 0 0 0 0 0 0 70 0 0 0 0 0 1 C0 0 0 0 0 0 1 50 0 0 0 0 0 0 50 0 0 0 0 0 1 50 0 0 0 0 0 2 50 0 0 0 0 0 1 50 0 0 0 0 0 1 50 0 0 0 0 0 0 30 0 0 0 0 0 1 40 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 FF F 0 0 0 0 0 FF F 0 0 0 0 0 FF F 0 0 0 0 0 0 F0 FF 0 0 0 0 FC EF FF 0 0 0 0 FB AF FF 0 0 0 0 FF EF FF 0 0 0 0 FF F 0 0 0 0 0 0 E0 FF 0 0 0 0 0 F0 FF 0 0 0 0 FF FF FF 0 0 0 0 0 F0 FF 0 0 0 0 FF FF FF 0 0 0 0 FF DF FF 0 0 0 0 0 D0 FF 0 0 0 0 FF DF FF 0 0 0 0 FF DF FF 0 0 0 0 FF DF FF 0 0 0 0 FF DF FF 0 0 0 0 FF CF FF 0 0 0 0 FF DF FF 0 0 0 0 FD 8F FF 0 0 0 0 FF BF FF 0 0 0 0 FE BF FF 0 0 0 0 FE CF FF 0 0 0 0 FE CF FF 0 0 0 0 FF DF FF 0 0 0 0 FF DF FF 0 0 0 0 FF EF FF 0 0 0 0 0 E0 FF 0 0 0 0 FF EF FF 0 0 0 0 0 20 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 0 20 0 0 0 0 0 0 20 0 0 0 0 0 FF 5F 0 0 0 0 0 0 20 0 0 0 0 0 0 20 0 0 0 0 0 0 20 0 0 0 0 0 1 20 0 0 0 0 0 0 20 0 0 0 0 0 1 30 0 0 0 0 0 1 20 0 0 0 0 0 1 20 0 0 0 0 0 0 50 0 0 0 0 0 1 20 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 1 0 0 0 0 0 0 0 10 0 0 0 0 0 1 0 0 0 0 0 0 2 30 0 0 0 0 0 4 30 0 0 0 0 0 6 40 0 0 0 0 0 7 50 0 0 0 0 0 8 60 0 0 0 0 0 8 50 0 0 0 0 0 8 60 0 0 0 0 0 7 60 0 0 0 10 0 C B0 0 0 0 10 0 5 60 0 0 0 10 0 4 60 0 0 0 10 0 4 70 0 0 0 10 0 5 70 0 0 0 10 0 4 60 0 0 0 10 0 3 60 0 0 0 10 0 4 60 0 0 0 10 0 4 70 0 0 0 10 0 A E0 0 0 0 10 0 4 60 0 0 0 10 0 4 50 0 0 0 10 0 3 30 0 0 0 10 0 2 30 0 0 0 10 0 0 10 0 0 0 10 0 0 10 0 0 0 10 0 0 F0 FF 0 0 10 0 FD CF FF 0 0 10 0 FF EF FF 0 0 10 0 FD EF FF 0 0 10 0 FD FF FF 0 0 10 0 FC FF FF 0 0 10 0 FC FF FF 0 0 10 0 FD F 0 0 0 10 0 FB EF FF 0 0 10 0 FC CF FF 0 0 0 0 FB CF FF 0 0 0 0 F9 CF FF 0 0 0 0 FB AF FF 0 0 0 0 F9 BF FF 0 0 0 0 F9 AF FF 0 0 0 0 FA AF FF 0 0 0 0 F9 9F FF 0 0 0 0 F4 2F FF 0 0 0 0 FC 9F FF 0 0 0 0 FC 9F FF 0 0 0 0 FC AF FF 0 0 0 0 FD 9F FF 0 0 0 0 FD 9F FF 0 0 0 0 FD AF FF 0 0 0 0 FD 9F FF 0 0 0 0 FD 5F FF 0 0 0 0 FE CF FF 0 0 0 0 0 E0 FF 0 0 0 0 FF FF FF 0 0 0 0 FF F 0 0 0 0 0 FF F 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 0 30 0 0 0 0 0 1 60 0 0 0 0 0 0 20 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 20 0 0 0 0 0 1 20 0 0 0 0 0 1 20 0 0 0 0 0 1 30 0 0 0 0 0 1 20 0 0 0 0 0 2 40 0 0 0 0 0 1 20 0 0 0 0 0 2 40 0 0 0 0 0 3 A0 0 0 0 0 0 2 60 0 0 0 0 0 2 70 0 0 0 0 0 2 70 0 0 0 0 0 2 70 0 0 0 0 0 1 80 0 0 0 0 0 2 80 0 0 0 0 0 2 90 0 0 0 0 0 2 A0 0 0 0 0 0 2 80 0 0 0 0 0 3 90 0 0 0 0 0 5 F0 0 0 0 0 0 2 70 0 0 0 0 0 4 B0 0 0 0 0 0 1 40 0 0 0 0 0 1 20 0 0 0 0 0 1 30 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 1 10 0 0 0 0 0 1 20 0 0 0 0 0 1 10 0 0 0 0 0 1 10 0 0 0 0 0 2 0 0 0 0 0 0 1 10 0 0 0 0 0 2 20 0 0 0 0 0 2 20 0 0 0 0 0 1 20 0 0 0 0 0 1 10 0 0 0 0 0 1 10 0 0 0 0 0 1 40 0 0 0 0 0 FF F 0 0 0 0 0 FD F 0 0 0 0 0 FA FF FF 0 0 0 0 F8 EF FF 0 0 0 0 F8 EF FF 0 0 0 0 F9 EF FF 0 0 0 0 FB FF FF 0 0 0 0 FC FF FF 0 0 0 0 FF FF FF 0 0 0 0 FE EF FF 0 0 0 0 FD DF FF 0 0 0 0 FA 8F FF 0 0 0 0 FD CF FF 0 0 0 0 FD BF FF 0 0 0 0 FD CF FF 0 0 0 0 FD CF FF 0 0 0 0 FE BF FF 0 0 0 0 FE DF FF 0 0 0 0 FF DF FF 0 0 0 0 FE DF FF 0 0 0 0 FE CF FF 0 0 0 0 FE CF FF 0 0 0 0 FE BF FF 0 0 0 0 FE CF FF 0 0 0 0 FE BF FF 0 0 0 0 FE BF FF 0 0 0 0 FD CF FF 0 0 0 0 FE BF FF 0 0 0 0 FB 5F FF 0 0 0 0 FF CF FF 0 0 0 0 FF CF FF 0 0 0 0 0 C0 FF 0 0 0 0 0 C0 FF 0 0 0 0 0 A0 FF 0 0 0 0 0 A0 FF 0 0 0 0 FF 2F FF 0 0 0 0 FF 7F FF 0 0 0 0 0 60 FF 0 0 0 0 0 70 FF 0 0 0 0 0 70 FF 0 0 0 0 0 90 FF 0 0 0 0 0 B0 FF 0 0 0 0 0 F0 FF 0 0 0 0 0 D0 FF 0 0 0 0 2 0 0 0 0 0 0 1 0 0 0 0 0 0 0 10 0 0 0 0 0 0 10 0 0 0 0 0 3 0 0 0 0 0 0 7 0 0 0 0 0 0 5 0 0 0 0 0 0 5 F0 FF 0 0 0 0 5 F0 FF 0 0 0 0 3 0 0 0 0 0 0 3 F0 FF 0 0 0 0 0 0 0 FF 0 0 0 1 0 0 0 0 0 0 2 0 0 0 0 0 0 2 0 0 0 0 0 0 3 F0 FF 0 0 0 0 2 0 0 0 0 0 0 2 0 0 0 0 0 0 2 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 FF 0 0 FF F 0 0 0 0 0 FF F 0 0 0 0 0 FE F 0 0 0 0 0 FD F 0 0 0 0 0 F4 EF FF 0 0 0 0 F9 EF FF 0 0 0 0 F7 EF FF 0 0 0 0 F9 EF FF 0 0 0 0 FA FF FF 0 0 0 0 FC FF FF 0 0 0 0 FE F 0 0 0 0 0 0 F0 FF 0 0 0 0 5 0 0 0 0 0 0 3 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 2 0 0 0 0 0 0 1 0 0 0 0 0 0 5 0 0 0 0 0 0 5 0 0 0 0 0 0 5 0 0 0 0 From man at email.com.ua Sat Mar 14 06:51:32 2009 From: man at email.com.ua (Artyom Mirgorodsky) Date: Sat Mar 14 06:51:39 2009 Subject: support for logitech mx610 mouse In-Reply-To: <200903141500.48042.man@email.com.ua> References: <200903140114.22511.man@email.com.ua> <200903141336.51769.hselasky@c2i.net> <200903141500.48042.man@email.com.ua> Message-ID: <200903141555.21815.man@email.com.ua> > See attached file Sorry. I don't post data when only move mouse. In attach -------------- next part -------------- 0 0 B 70 0 0 0 0 0 C 80 0 0 0 0 0 3 10 1 0 0 0 0 3 F0 0 0 0 0 0 2 90 0 0 0 0 0 2 70 0 0 0 0 0 1 50 0 0 0 0 0 0 C0 1 0 0 0 0 0 A0 1 0 0 0 0 2 10 1 0 0 0 0 0 40 1 0 0 0 0 FB 4F 1 0 0 0 0 F6 6F 1 0 0 0 0 DB 8F 2 0 0 0 0 E5 4F 1 0 0 0 0 DE 3F 1 0 0 0 0 DC 3F 1 0 0 0 0 DA 2F 1 0 0 0 0 D8 2F 1 0 0 0 0 D8 EF 0 0 0 0 0 DA BF 0 0 0 0 0 DA 8F 0 0 0 0 0 DC 3F 0 0 0 0 0 C0 FF FF 0 0 0 0 E9 6F FF 0 0 0 0 E9 6F FF 0 0 0 0 EF 2F FF 0 0 0 0 F3 1F FF 0 0 0 0 F5 EF FE 0 0 0 0 F7 AF FE 0 0 0 0 FB 8F FE 0 0 0 0 FC 7F FE 0 0 0 0 0 40 FE 0 0 0 0 9 50 FC 0 0 0 0 8 10 FE 0 0 0 0 9 20 FE 0 0 0 0 C 30 FE 0 0 0 0 D 50 FE 0 0 0 0 E 60 FE 0 0 0 0 11 90 FE 0 0 0 0 13 B0 FE 0 0 0 0 14 C0 FE 0 0 0 0 16 D0 FE 0 0 0 0 18 0 FF 0 0 0 0 31 80 FE 0 0 0 0 1B 90 FF 0 0 0 0 1A B0 FF 0 0 0 0 1B F0 FF 0 0 0 0 1C 20 0 0 0 0 0 1B 60 0 0 0 0 0 1A 90 0 0 0 0 0 18 B0 0 0 0 0 0 16 E0 0 0 0 0 0 12 50 1 0 0 0 0 15 A0 1 0 0 0 0 4 D0 0 0 0 0 0 2 80 0 0 0 0 0 2 C0 0 0 0 0 0 1 C0 0 0 0 0 0 0 D0 0 0 0 0 0 FF 1F 1 0 0 0 0 FC F 1 0 0 0 0 FC 3F 1 0 0 0 0 FA 4F 1 0 0 0 0 EC 3F 2 0 0 0 0 F4 F 1 0 0 0 0 F2 BF 0 0 0 0 0 F2 CF 0 0 0 0 0 EE AF 0 0 0 0 0 EB 7F 0 0 0 0 0 E9 5F 0 0 0 0 0 EA 4F 0 0 0 0 0 EA 1F 0 0 0 0 0 D0 DF FF 0 0 0 0 E8 AF FF 0 0 0 0 EB 6F FF 0 0 0 0 F1 9F FF 0 0 0 0 F0 6F FF 0 0 0 0 F0 1F FF 0 0 0 0 F0 EF FE 0 0 0 0 F1 CF FE 0 0 0 0 F5 9F FE 0 0 0 0 F5 7F FE 0 0 0 0 F0 EF FC 0 0 0 0 FB 7F FE 0 0 0 0 FE 8F FE 0 0 0 0 0 90 FE 0 0 0 0 3 C0 FE 0 0 0 0 6 D0 FE 0 0 0 0 A F0 FE 0 0 0 0 F 10 FF 0 0 0 0 11 20 FF 0 0 0 0 13 50 FF 0 0 0 0 2F F0 FE 0 0 0 0 1B C0 FF 0 0 0 0 1C F0 FF 0 0 0 0 1E 0 0 0 0 0 0 1D 0 0 0 0 0 0 1D 30 0 0 0 0 0 1D 70 0 0 0 0 0 1C 90 0 0 0 0 0 1D E0 0 0 0 0 0 1B E0 0 0 0 0 0 19 0 1 0 0 0 0 23 0 2 0 0 0 0 D 60 1 0 0 0 0 A 70 1 0 0 0 0 9 20 1 0 0 0 0 6 D0 0 0 0 0 0 4 E0 0 0 0 0 0 3 E0 0 0 0 0 0 1 F0 0 0 0 0 0 1 F0 0 0 0 0 0 FF 1F 1 0 0 0 0 FB AF 1 0 0 0 0 FD EF 0 0 0 0 0 F9 DF 0 0 0 0 0 F9 FF 0 0 0 0 0 F3 EF 0 0 0 0 0 EF AF 0 0 0 0 0 F3 7F 0 0 0 0 0 F1 6F 0 0 0 0 0 EC 4F 0 0 0 0 0 D5 3F 0 0 0 0 0 E9 FF FF 0 0 0 0 E6 DF FF 0 0 0 0 E8 AF FF 0 0 0 0 E8 7F FF 0 0 0 0 E9 4F FF 0 0 0 0 EC 2F FF 0 0 0 0 ED 1F FF 0 0 0 0 F0 FF FE 0 0 0 0 F1 FF FE 0 0 0 0 F3 DF FE 0 0 0 0 EC 9F FD 0 0 0 0 FA DF FE 0 0 0 0 FD DF FE 0 0 0 0 FF DF FE 0 0 0 0 2 D0 FE 0 0 0 0 5 E0 FE 0 0 0 0 8 E0 FE 0 0 0 0 A 0 FF 0 0 0 0 E 10 FF 0 0 0 0 22 60 FE 0 0 0 0 15 50 FF 0 0 0 0 16 50 FF 0 0 0 0 18 70 FF 0 0 0 0 1A 80 FF 0 0 0 0 19 B0 FF 0 0 0 0 1B E0 FF 0 0 0 0 1B 0 0 0 0 0 0 1B 30 0 0 0 0 0 1B 60 0 0 0 0 0 32 20 1 0 0 0 0 16 C0 0 0 0 0 0 15 F0 0 0 0 0 0 10 F0 0 0 0 0 0 D 10 1 0 0 0 0 A 20 1 0 0 0 0 8 30 1 0 0 0 0 6 50 1 0 0 0 0 4 10 1 0 0 0 0 2 10 1 0 0 0 0 2 60 2 0 0 0 0 0 30 1 0 0 0 0 FF 6F 1 0 0 0 0 FA 6F 1 0 0 0 0 FC 1F 1 0 0 0 0 FC 2F 1 0 0 0 0 FA 1F 1 0 0 0 0 FB 7F 0 0 0 0 0 F6 8F 0 0 0 0 0 F2 7F 0 0 0 0 0 DB 8F 0 0 0 0 0 ED 2F 0 0 0 0 0 EB F 0 0 0 0 0 EA EF FF 0 0 0 0 E9 CF FF 0 0 0 0 EA 8F FF 0 0 0 0 EB 6F FF 0 0 0 0 EE 3F FF 0 0 0 0 ED F FF 0 0 0 0 F0 EF FE 0 0 0 0 F1 CF FE 0 0 0 0 E6 7F FD 0 0 0 0 F7 CF FE 0 0 0 0 F9 CF FE 0 0 0 0 FB BF FE 0 0 0 0 FE CF FE 0 0 0 0 0 D0 FE 0 0 0 0 1 D0 FE 0 0 0 0 4 F0 FE 0 0 0 0 7 F0 FE 0 0 0 0 A 10 FF 0 0 0 0 B 10 FF 0 0 0 0 1E 50 FE 0 0 0 0 13 50 FF 0 0 0 0 14 60 FF 0 0 0 0 15 70 FF 0 0 0 0 18 80 FF 0 0 0 0 18 B0 FF 0 0 0 0 19 B0 FF 0 0 0 0 18 C0 FF 0 0 0 0 17 0 0 0 0 0 0 18 30 0 0 0 0 0 2F 10 1 0 0 0 0 17 E0 0 0 0 0 0 17 F0 0 0 0 0 0 14 0 1 0 0 0 0 13 20 1 0 0 0 0 11 20 1 0 0 0 0 D 30 1 0 0 0 0 9 10 1 0 0 0 0 6 20 1 0 0 0 0 5 20 1 0 0 0 0 5 50 2 0 0 0 0 2 D0 0 0 0 0 0 0 E0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 1 0 0 0 0 FB 1F 1 0 0 0 0 F6 1F 1 0 0 0 0 F3 F 1 0 0 0 0 F0 F 1 0 0 0 0 EF EF 0 0 0 0 0 DD 8F 1 0 0 0 0 EF 9F 0 0 0 0 0 EC 5F 0 0 0 0 0 EB 5F 0 0 0 0 0 EB 4F 0 0 0 0 0 EA 2F 0 0 0 0 0 F0 2F 0 0 0 0 0 F3 1F 0 0 0 0 0 FA DF FF 0 0 0 0 FC EF FF 0 0 0 0 F6 BF FF 0 0 0 0 F3 8F FF 0 0 0 0 F3 5F FF 0 0 0 0 F2 4F FF 0 0 0 0 F2 3F FF 0 0 0 0 F6 3F FF 0 0 0 0 F7 1F FF 0 0 0 0 F8 1F FF 0 0 0 0 FB F FF 0 0 0 0 FD F FF 0 0 0 0 FF DF FD 0 0 0 0 3 E0 FE 0 0 0 0 6 E0 FE 0 0 0 0 9 E0 FE 0 0 0 0 C E0 FE 0 0 0 0 10 E0 FE 0 0 0 0 13 D0 FE 0 0 0 0 16 F0 FE 0 0 0 0 19 0 FF 0 0 0 0 37 40 FE 0 0 0 0 1E 40 FF 0 0 0 0 1F 60 FF 0 0 0 0 20 80 FF 0 0 0 0 20 B0 FF 0 0 0 0 22 E0 FF 0 0 0 0 23 20 0 0 0 0 0 25 70 0 0 0 0 0 25 B0 0 0 0 0 0 23 C0 0 0 0 0 0 22 F0 0 0 0 0 0 30 B0 2 0 0 0 0 12 50 1 0 0 0 0 10 50 1 0 0 0 0 C 0 1 0 0 0 0 B 20 1 0 0 0 0 9 30 1 0 0 0 0 6 40 1 0 0 0 0 4 60 1 0 0 0 0 2 40 1 0 0 0 0 FD BF 2 0 0 0 0 FA 4F 1 0 0 0 0 F7 4F 1 0 0 0 0 F5 1F 1 0 0 0 0 F1 1F 1 0 0 0 0 EF F 1 0 0 0 0 EA FF 0 0 0 0 0 E9 DF 0 0 0 0 0 E7 AF 0 0 0 0 0 E4 AF 0 0 0 0 0 C4 F 1 0 0 0 0 E0 5F 0 0 0 0 0 DF 4F 0 0 0 0 0 E0 2F 0 0 0 0 0 E1 F 0 0 0 0 0 E2 FF FF 0 0 0 0 E3 CF FF 0 0 0 0 E6 7F FF 0 0 0 0 E8 4F FF 0 0 0 0 EA FF FE 0 0 0 0 DB 6F FD 0 0 0 0 F2 AF FE 0 0 0 0 F5 9F FE 0 0 0 0 F8 7F FE 0 0 0 0 F9 7F FE 0 0 0 0 FB 8F FE 0 0 0 0 FE 9F FE 0 0 0 0 0 B0 FE 0 0 0 0 4 B0 FE 0 0 0 0 7 C0 FE 0 0 0 0 A E0 FE 0 0 0 0 21 0 FE 0 0 0 0 15 30 FF 0 0 0 0 18 40 FF 0 0 0 0 1C 60 FF 0 0 0 0 1F A0 FF 0 0 0 0 23 C0 FF 0 0 0 0 27 F0 FF 0 0 0 0 28 20 0 0 0 0 0 28 50 0 0 0 0 0 1D 10 0 0 0 0 0 41 B0 0 0 0 0 0 18 B0 0 0 0 0 0 1B C0 0 0 0 0 0 19 E0 0 0 0 0 0 1A F0 0 0 0 0 0 1A E0 0 0 0 0 0 1A E0 0 0 0 0 0 1C C0 0 0 0 0 0 1B A0 0 0 0 0 0 1A 40 0 0 0 0 0 31 0 0 0 0 0 0 18 B0 FF 0 0 0 0 16 80 FF 0 0 0 0 14 50 FF 0 0 0 0 11 20 FF 0 0 0 0 F 10 FF 0 0 0 0 D 10 FF 0 0 0 0 B 0 FF 0 0 0 0 8 0 FF 0 0 0 0 5 F0 FE 0 0 0 0 3 F0 FE 0 0 0 0 FD DF FD 0 0 0 0 FA EF FE 0 0 0 0 F7 FF FE 0 0 0 0 F9 2F FF 0 0 0 0 F4 1F FF 0 0 0 0 F1 F FF 0 0 0 0 EE EF FE 0 0 0 0 EF FF FE 0 0 0 0 EB FF FE 0 0 0 0 D2 2F FE 0 0 0 0 E6 3F FF 0 0 0 0 E5 5F FF 0 0 0 0 E4 8F FF 0 0 0 0 E3 BF FF 0 0 0 0 E2 EF FF 0 0 0 0 E1 F 0 0 0 0 0 E0 3F 0 0 0 0 0 E2 4F 0 0 0 0 0 E2 7F 0 0 0 0 0 E3 8F 0 0 0 0 0 C7 2F 1 0 0 0 0 E7 AF 0 0 0 0 0 E8 BF 0 0 0 0 0 E9 BF 0 0 0 0 0 EA CF 0 0 0 0 0 EC DF 0 0 0 0 0 EE DF 0 0 0 0 0 EF DF 0 0 0 0 0 F1 DF 0 0 0 0 0 F2 FF 0 0 0 0 0 E8 EF 1 0 0 0 0 F6 FF 0 0 0 0 0 F7 FF 0 0 0 0 0 F9 FF 0 0 0 0 0 FA F 1 0 0 0 0 FD 1F 1 0 0 0 0 FF 1F 1 0 0 0 0 1 20 1 0 0 0 0 4 30 1 0 0 0 0 7 20 1 0 0 0 0 15 30 2 0 0 0 0 C 20 1 0 0 0 0 E 0 1 0 0 0 0 10 0 1 0 0 0 0 13 E0 0 0 0 0 0 14 E0 0 0 0 0 0 17 D0 0 0 0 0 0 18 B0 0 0 0 0 0 1A A0 0 0 0 0 0 36 D0 0 0 0 0 0 1D 40 0 0 0 0 0 1F 20 0 0 0 0 0 20 0 0 0 0 0 0 21 0 0 0 0 0 0 22 D0 FF 0 0 0 0 22 B0 FF 0 0 0 0 22 80 FF 0 0 0 0 21 50 FF 0 0 0 0 20 30 FF 0 0 0 0 39 10 FE 0 0 0 0 1B D0 FE 0 0 0 0 16 C0 FE 0 0 0 0 14 A0 FE 0 0 0 0 11 90 FE 0 0 0 0 E 70 FE 0 0 0 0 A A0 FE 0 0 0 0 6 A0 FE 0 0 0 0 3 B0 FE 0 0 0 0 0 E0 FE 0 0 0 0 FD 1F FF 0 0 0 0 F9 2F FF 0 0 0 0 E9 9F FE 0 0 0 0 F1 5F FF 0 0 0 0 F0 8F FF 0 0 0 0 F2 5F FF 0 0 0 0 EF 3F FF 0 0 0 0 F0 DF FF 0 0 0 0 F4 EF FF 0 0 0 0 F4 1F 0 0 0 0 0 F7 6F 0 0 0 0 0 F0 FF 0 0 0 0 0 F5 8F 0 0 0 0 0 F1 BF 0 0 0 0 0 EF FF 0 0 0 0 0 EF 2F 1 0 0 0 0 EE 4F 1 0 0 0 0 EF 8F 1 0 0 0 0 EF AF 1 0 0 0 0 F0 AF 1 0 0 0 0 F0 CF 1 0 0 0 0 F1 AF 1 0 0 0 0 E2 F 3 0 0 0 0 F2 4F 1 0 0 0 0 F1 1F 1 0 0 0 0 F0 F 1 0 0 0 0 F1 EF 0 0 0 0 0 F1 CF 0 0 0 0 0 F0 BF 0 0 0 0 0 F0 9F 0 0 0 0 0 F1 7F 0 0 0 0 0 F1 6F 0 0 0 0 0 E2 8F 0 0 0 0 0 F1 2F 0 0 0 0 0 F1 F 0 0 0 0 0 F2 F 0 0 0 0 0 F0 F 0 0 0 0 0 F0 FF FF 0 0 0 0 EF DF FF 0 0 0 0 EE CF FF 0 0 0 0 ED CF FF 0 0 0 0 EE CF FF 0 0 0 0 DF 3F FF 0 0 0 0 F2 8F FF 0 0 0 0 F2 5F FF 0 0 0 0 F1 3F FF 0 0 0 0 F1 FF FE 0 0 0 0 F1 EF FE 0 0 0 0 F1 DF FE 0 0 0 0 F2 BF FE 0 0 0 0 F3 AF FE 0 0 0 0 E7 8F FD 0 0 0 0 F8 BF FE 0 0 0 0 FB BF FE 0 0 0 0 FC BF FE 0 0 0 0 FE CF FE 0 0 0 0 0 C0 FE 0 0 0 0 2 B0 FE 0 0 0 0 5 A0 FE 0 0 0 0 9 B0 FE 0 0 0 0 B B0 FE 0 0 0 0 1F 90 FD 0 0 0 0 14 E0 FE 0 0 0 0 17 10 FF 0 0 0 0 19 30 FF 0 0 0 0 1B 30 FF 0 0 0 0 1E 60 FF 0 0 0 0 20 50 FF 0 0 0 0 21 60 FF 0 0 0 0 25 70 FF 0 0 0 0 50 30 FF 0 0 0 0 29 B0 FF 0 0 0 0 29 E0 FF 0 0 0 0 28 0 0 0 0 0 0 26 10 0 0 0 0 0 23 D0 FF 0 0 0 0 0 80 1 0 0 0 0 0 80 1 0 0 0 0 0 70 1 0 0 0 0 3 30 1 0 0 0 0 5 40 1 0 0 0 0 3 F0 0 0 0 0 0 6 60 2 0 0 0 0 7 70 1 0 0 0 0 5 60 1 0 0 0 0 2 70 1 0 0 0 0 0 70 1 0 0 0 0 FD 6F 1 0 0 0 0 F9 6F 1 0 0 0 0 F8 7F 1 0 0 0 0 EE 9F 2 0 0 0 0 F0 3F 1 0 0 0 0 ED 1F 1 0 0 0 0 EC EF 0 0 0 0 0 EA FF 0 0 0 0 0 E8 CF 0 0 0 0 0 E5 BF 0 0 0 0 0 E5 CF 0 0 0 0 0 E3 AF 0 0 0 0 0 E3 8F 0 0 0 0 0 C2 FF 0 0 0 0 0 E1 7F 0 0 0 0 0 E1 5F 0 0 0 0 0 E3 5F 0 0 0 0 0 E6 1F 0 0 0 0 0 E6 F 0 0 0 0 0 E8 F 0 0 0 0 0 EA CF FF 0 0 0 0 EB 8F FF 0 0 0 0 ED 5F FF 0 0 0 0 DF 1F FE 0 0 0 0 F1 CF FE 0 0 0 0 F3 AF FE 0 0 0 0 F6 8F FE 0 0 0 0 F8 4F FE 0 0 0 0 FB 6F FE 0 0 0 0 FC 6F FE 0 0 0 0 0 50 FE 0 0 0 0 1 50 FE 0 0 0 0 5 60 FE 0 0 0 0 6 60 FE 0 0 0 0 14 E0 FC 0 0 0 0 D A0 FE 0 0 0 0 F B0 FE 0 0 0 0 11 D0 FE 0 0 0 0 13 F0 FE 0 0 0 0 16 10 FF 0 0 0 0 18 30 FF 0 0 0 0 1B 50 FF 0 0 0 0 1E 70 FF 0 0 0 0 41 40 FF 0 0 0 0 22 E0 FF 0 0 0 0 25 0 0 0 0 0 0 25 40 0 0 0 0 0 26 60 0 0 0 0 0 25 80 0 0 0 0 0 1B 80 0 0 0 0 0 19 90 0 0 0 0 0 19 B0 0 0 0 0 0 18 50 0 0 0 0 0 14 80 0 0 0 0 0 20 B0 1 0 0 0 0 A 20 1 0 0 0 0 8 30 1 0 0 0 0 5 30 1 0 0 0 0 1 30 1 0 0 0 0 FE 4F 1 0 0 0 0 FA 3F 1 0 0 0 0 F5 3F 1 0 0 0 0 F3 2F 1 0 0 0 0 DB FF 1 0 0 0 0 EB FF 0 0 0 0 0 E9 EF 0 0 0 0 0 E7 CF 0 0 0 0 0 E4 BF 0 0 0 0 0 E4 AF 0 0 0 0 0 E3 9F 0 0 0 0 0 E2 8F 0 0 0 0 0 E2 8F 0 0 0 0 0 E2 7F 0 0 0 0 0 C5 7F 0 0 0 0 0 E3 F 0 0 0 0 0 E3 FF FF 0 0 0 0 E6 DF FF 0 0 0 0 E8 CF FF 0 0 0 0 EB BF FF 0 0 0 0 EE 8F FF 0 0 0 0 F3 4F FF 0 0 0 0 F6 3F FF 0 0 0 0 F9 FF FE 0 0 0 0 FA 4F FD 0 0 0 0 1 50 FE 0 0 0 0 3 50 FE 0 0 0 0 5 50 FE 0 0 0 0 7 50 FE 0 0 0 0 8 40 FE 0 0 0 0 A 50 FE 0 0 0 0 D 60 FE 0 0 0 0 E 70 FE 0 0 0 0 11 90 FE 0 0 0 0 29 70 FD 0 0 0 0 18 F0 FE 0 0 0 0 1B 0 FF 0 0 0 0 1C 20 FF 0 0 0 0 1D 40 FF 0 0 0 0 1E 70 FF 0 0 0 0 1E 90 FF 0 0 0 0 1E B0 FF 0 0 0 0 1F C0 FF 0 0 0 0 1E F0 FF 0 0 0 0 3A 20 0 0 0 0 0 17 10 0 0 0 0 0 21 50 0 0 0 0 0 1A E0 0 0 0 0 0 18 F0 0 0 0 0 0 19 10 1 0 0 0 0 18 30 1 0 0 0 0 17 20 1 0 0 0 0 16 20 1 0 0 0 0 14 E0 0 0 0 0 0 12 B0 0 0 0 0 0 1A 80 0 0 0 0 0 9 10 0 0 0 0 0 7 20 0 0 0 0 0 5 0 0 0 0 0 0 1 0 0 0 0 0 0 0 F0 FF 0 0 0 0 0 E0 FF 0 0 0 0 0 D0 FF 0 0 0 0 0 A0 FF 0 0 0 0 0 80 FF 0 0 0 0 FE CF FE 0 0 0 0 FE 4F FF 0 0 0 0 0 30 FF 0 0 0 0 FC 2F FF 0 0 0 0 FC F FF 0 0 0 0 FE F FF 0 0 0 0 FC EF FE 0 0 0 0 FC CF FE 0 0 0 0 FE 5F FE 0 0 0 0 EC 2F FD 0 0 0 0 F3 AF FE 0 0 0 0 F1 BF FE 0 0 0 0 EF EF FE 0 0 0 0 EE FF FE 0 0 0 0 ED F FF 0 0 0 0 EC 3F FF 0 0 0 0 E9 4F FF 0 0 0 0 E8 8F FF 0 0 0 0 E6 9F FF 0 0 0 0 CB CF FF 0 0 0 0 E5 F 0 0 0 0 0 E4 5F 0 0 0 0 0 E3 4F 0 0 0 0 0 E3 5F 0 0 0 0 0 E5 6F 0 0 0 0 0 E5 6F 0 0 0 0 0 E4 8F 0 0 0 0 0 E6 7F 0 0 0 0 0 E6 9F 0 0 0 0 0 E7 9F 0 0 0 0 0 CD 4F 1 0 0 0 0 E6 AF 0 0 0 0 0 E7 BF 0 0 0 0 0 E6 DF 0 0 0 0 0 E7 CF 0 0 0 0 0 E6 DF 0 0 0 0 0 E8 CF 0 0 0 0 0 E8 DF 0 0 0 0 0 EA EF 0 0 0 0 0 EA FF 0 0 0 0 0 D7 FF 1 0 0 0 0 EE F 1 0 0 0 0 EE 2F 1 0 0 0 0 F0 2F 1 0 0 0 0 F2 2F 1 0 0 0 0 F3 3F 1 0 0 0 0 F7 F 1 0 0 0 0 F9 BF 0 0 0 0 0 FA FF 0 0 0 0 0 FB EF 1 0 0 0 0 0 F0 0 0 0 0 0 FF 1F 1 0 0 0 0 0 10 1 0 0 0 0 0 20 1 0 0 0 0 0 20 1 0 0 0 0 1 20 1 0 0 0 0 2 40 1 0 0 0 0 4 40 1 0 0 0 0 5 40 1 0 0 0 0 7 30 1 0 0 0 0 13 50 2 0 0 0 0 B 10 1 0 0 0 0 C 10 1 0 0 0 0 E F0 0 0 0 0 0 E D0 0 0 0 0 0 10 D0 0 0 0 0 0 11 C0 0 0 0 0 0 14 C0 0 0 0 0 0 14 B0 0 0 0 0 0 2F 60 1 0 0 0 0 19 B0 0 0 0 0 0 1B A0 0 0 0 0 0 1D 80 0 0 0 0 0 1D 90 0 0 0 0 0 1F 60 0 0 0 0 0 20 50 0 0 0 0 0 20 40 0 0 0 0 0 21 20 0 0 0 0 0 22 20 0 0 0 0 0 4A E0 FF 0 0 0 0 25 C0 FF 0 0 0 0 25 B0 FF 0 0 0 0 25 90 FF 0 0 0 0 20 A0 FF 0 0 0 0 21 70 FF 0 0 0 0 20 70 FF 0 0 0 0 1F 60 FF 0 0 0 0 1D 60 FF 0 0 0 0 1D B0 FF 0 0 0 0 2B 40 0 0 0 0 0 10 A0 FF 0 0 0 0 F 50 FF 0 0 0 0 C 20 FF 0 0 0 0 9 10 FF 0 0 0 0 7 F0 FE 0 0 0 0 6 D0 FE 0 0 0 0 2 C0 FE 0 0 0 0 0 B0 FE 0 0 0 0 FD CF FE 0 0 0 0 FB DF FE 0 0 0 0 F0 FF FD 0 0 0 0 F5 F FF 0 0 0 0 F3 2F FF 0 0 0 0 F1 2F FF 0 0 0 0 EE 4F FF 0 0 0 0 EC 3F FF 0 0 0 0 EA 5F FF 0 0 0 0 EA AF FF 0 0 0 0 D0 5F FF 0 0 0 0 E4 DF FF 0 0 0 0 E4 EF FF 0 0 0 0 E1 FF FF 0 0 0 0 E2 F 0 0 0 0 0 E0 5F 0 0 0 0 0 E1 9F 0 0 0 0 0 EA 1F 1 0 0 0 0 E8 1F 1 0 0 0 0 E7 DF 0 0 0 0 0 E5 DF 0 0 0 0 0 C6 DF 1 0 0 0 0 E2 1F 1 0 0 0 0 E2 1F 1 0 0 0 0 E3 1F 1 0 0 0 0 E2 2F 1 0 0 0 0 E5 2F 1 0 0 0 0 E6 3F 1 0 0 0 0 E8 3F 1 0 0 0 0 EA 1F 1 0 0 0 0 EE 2F 1 0 0 0 0 F0 2F 1 0 0 0 0 ED 2F 2 0 0 0 0 FD FF 0 0 0 0 0 0 F0 0 0 0 0 0 5 D0 0 0 0 0 0 8 D0 0 0 0 0 0 C B0 0 0 0 0 0 F B0 0 0 0 0 0 13 90 0 0 0 0 0 17 70 0 0 0 0 0 38 80 0 0 0 0 0 20 20 0 0 0 0 0 25 E0 FF 0 0 0 0 28 D0 FF 0 0 0 0 29 90 FF 0 0 0 0 2B 80 FF 0 0 0 0 2B 50 FF 0 0 0 0 2C 40 FF 0 0 0 0 2C 30 FF 0 0 0 0 2A 0 FF 0 0 0 0 51 C0 FD 0 0 0 0 26 C0 FE 0 0 0 0 25 A0 FE 0 0 0 0 22 80 FE 0 0 0 0 21 60 FE 0 0 0 0 1E 50 FE 0 0 0 0 1C 40 FE 0 0 0 0 1A 40 FE 0 0 0 0 19 30 FE 0 0 0 0 1A F0 FE 0 0 0 0 2B 90 FD 0 0 0 0 D D0 FE 0 0 0 0 B D0 FE 0 0 0 0 7 F0 FE 0 0 0 0 4 E0 FE 0 0 0 0 1 D0 FE 0 0 0 0 FF EF FE 0 0 0 0 0 E0 FE 0 0 0 0 FA 9F FE 0 0 0 0 F6 CF FE 0 0 0 0 F4 EF FE 0 0 0 0 DC 4F FE 0 0 0 0 E6 5F FF 0 0 0 0 E1 7F FF 0 0 0 0 E2 7F FF 0 0 0 0 D3 4F FF 0 0 0 0 DE 7F FF 0 0 0 0 E7 9F 0 0 0 0 0 ED 4F 0 0 0 0 0 F1 1F 0 0 0 0 0 C4 6F 0 0 0 0 0 D9 3F 0 0 0 0 0 D5 6F 0 0 0 0 0 D2 7F 0 0 0 0 0 CF 8F 0 0 0 0 0 CE 8F 0 0 0 0 0 CE 9F 0 0 0 0 0 CD AF 0 0 0 0 0 CE BF 0 0 0 0 0 D0 CF 0 0 0 0 0 A3 BF 1 0 0 0 0 D5 FF 0 0 0 0 0 D5 1F 1 0 0 0 0 DC DF 0 0 0 0 0 DE DF 0 0 0 0 0 DE EF 0 0 0 0 0 E0 CF 0 0 0 0 0 E3 AF 0 0 0 0 0 E5 CF 0 0 0 0 0 E4 AF 0 0 0 0 0 E6 AF 0 0 0 0 0 D2 EF 0 0 0 0 0 EA AF 0 0 0 0 0 EC 9F 0 0 0 0 0 EC 9F 0 0 0 0 0 EB 8F 0 0 0 0 0 ED 8F 0 0 0 0 0 EC 9F 0 0 0 0 0 ED 7F 0 0 0 0 0 EE 7F 0 0 0 0 0 ED 4F 0 0 0 0 0 DA 6F 0 0 0 0 0 EC 1F 0 0 0 0 0 EC F 0 0 0 0 0 EB FF FF 0 0 0 0 E9 EF FF 0 0 0 0 E8 EF FF 0 0 0 0 ED 9F FF 0 0 0 0 EB 9F FF 0 0 0 0 E7 9F FF 0 0 0 0 DB DF FE 0 0 0 0 F3 F FF 0 0 0 0 EE 1F FF 0 0 0 0 F2 EF FD 0 0 0 0 F0 F FE 0 0 0 0 F4 5F FE 0 0 0 0 F7 1F FF 0 0 0 0 FA 8F FF 0 0 0 0 F8 3F FF 0 0 0 0 F9 3F FF 0 0 0 0 FA 2F FF 0 0 0 0 FB F FE 0 0 0 0 0 E0 FE 0 0 0 0 4 E0 FE 0 0 0 0 6 B0 FE 0 0 0 0 9 B0 FE 0 0 0 0 A B0 FE 0 0 0 0 E B0 FE 0 0 0 0 F B0 FE 0 0 0 0 11 B0 FE 0 0 0 0 12 E0 FE 0 0 0 0 25 D0 FD 0 0 0 0 13 20 FF 0 0 0 0 14 30 FF 0 0 0 0 14 40 FF 0 0 0 0 16 40 FF 0 0 0 0 17 50 FF 0 0 0 0 18 60 FF 0 0 0 0 1C 60 FF 0 0 0 0 1C 80 FF 0 0 0 0 3E 0 FF 0 0 0 0 22 90 FF 0 0 0 0 28 80 FF 0 0 0 0 2C 80 FF 0 0 0 0 2E 90 FF 0 0 0 0 2F 90 FF 0 0 0 0 33 90 FF 0 0 0 0 35 B0 FF 0 0 0 0 35 90 FF 0 0 0 0 38 80 FF 0 0 0 0 74 0 FF 0 0 0 0 3C 90 FF 0 0 0 0 3B 80 FF 0 0 0 0 3E 90 FF 0 0 0 0 3D 80 FF 0 0 0 0 3D 80 FF 0 0 0 0 3C 90 FF 0 0 0 0 3C 90 FF 0 0 0 0 3C 80 FF 0 0 0 0 3A B0 FF 0 0 0 0 6D 80 FF 0 0 0 0 31 E0 FF 0 0 0 0 30 0 0 0 0 0 0 2C 10 0 0 0 0 0 2B 20 0 0 0 0 0 20 E0 FF 0 0 0 0 18 0 0 0 0 0 0 18 40 0 0 0 0 0 13 70 0 0 0 0 0 17 A0 0 0 0 0 0 17 C0 0 0 0 0 0 34 F0 1 0 0 0 0 1C 40 1 0 0 0 0 19 40 1 0 0 0 0 17 70 1 0 0 0 0 18 70 1 0 0 0 0 1A A0 1 0 0 0 0 1B D0 1 0 0 0 0 1C E0 1 0 0 0 0 16 B0 1 0 0 0 0 10 B0 1 0 0 0 0 1C E0 3 0 0 0 0 9 80 1 0 0 0 0 B 10 2 0 0 0 0 B 60 2 0 0 0 0 D C0 2 0 0 0 0 E 10 3 0 0 0 0 10 60 3 0 0 0 0 F 90 3 0 0 0 0 11 C0 3 0 0 0 0 21 C0 7 0 0 0 0 10 10 4 0 0 0 0 A 10 4 0 0 0 0 A 20 4 0 0 0 0 7 30 4 0 0 0 0 7 D0 3 0 0 0 0 3 E0 3 0 0 0 0 1 E0 3 0 0 0 0 FF EF 3 0 0 0 0 FC DF 3 0 0 0 0 F9 EF 3 0 0 0 0 EC 4F 7 0 0 0 0 F3 8F 3 0 0 0 0 F1 6F 3 0 0 0 0 F0 7F 3 0 0 0 0 EE 4F 3 0 0 0 0 EB 4F 3 0 0 0 0 EA 2F 3 0 0 0 0 E8 1F 3 0 0 0 0 E7 F 3 0 0 0 0 E6 DF 2 0 0 0 0 C4 4F 5 0 0 0 0 DF 7F 2 0 0 0 0 DE 5F 2 0 0 0 0 DD 3F 2 0 0 0 0 DC 2F 2 0 0 0 0 DB FF 1 0 0 0 0 DA EF 1 0 0 0 0 DA BF 1 0 0 0 0 D9 8F 1 0 0 0 0 D8 4F 1 0 0 0 0 AF 2F 2 0 0 0 0 D8 CF 0 0 0 0 0 D7 AF 0 0 0 0 0 D7 7F 0 0 0 0 0 D9 5F 0 0 0 0 0 D8 2F 0 0 0 0 0 D8 FF FF 0 0 0 0 D6 CF FF 0 0 0 0 D6 8F FF 0 0 0 0 D6 6F FF 0 0 0 0 AD 7F FE 0 0 0 0 D9 F FF 0 0 0 0 DA DF FE 0 0 0 0 DB 8F FE 0 0 0 0 E2 7F FE 0 0 0 0 EA 2F FE 0 0 0 0 F1 4F FE 0 0 0 0 F5 3F FE 0 0 0 0 F4 4F FE 0 0 0 0 F5 FF FD 0 0 0 0 ED 8F FB 0 0 0 0 F9 6F FD 0 0 0 0 FC 5F FD 0 0 0 0 0 20 FD 0 0 0 0 4 0 FD 0 0 0 0 3 0 FD 0 0 0 0 9 C0 FC 0 0 0 0 D C0 FC 0 0 0 0 11 C0 FC 0 0 0 0 14 A0 FC 0 0 0 0 33 10 F9 0 0 0 0 1D 60 FC 0 0 0 0 21 50 FC 0 0 0 0 25 70 FC 0 0 0 0 27 50 FC 0 0 0 0 29 40 FC 0 0 0 0 2D 60 FC 0 0 0 0 2F 70 FC 0 0 0 0 37 E1 EE 0 0 0 0 39 B0 FD 0 0 0 0 3B E0 FD 0 0 0 0 3B 0 FE 0 0 0 0 3C 30 FE 0 0 0 0 3C 50 FE 0 0 0 0 77 10 FD 0 0 0 0 2B 80 FE 0 0 0 0 2B D0 FE 0 0 0 0 20 10 FF 0 0 0 0 18 50 FF 0 0 0 0 0 10 0 0 0 0 0 0 30 0 0 0 0 0 2C 20 0 0 0 0 0 28 50 0 0 0 0 0 28 0 0 0 0 From alexbestms at math.uni-muenster.de Sat Mar 14 09:56:08 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Sat Mar 14 09:56:15 2009 Subject: problem with usb printer Message-ID: hi there. i'm having a problem with my usb printer. it's being recognised as ulpt0, but i cannot print. i'm using the cups port for printing. i've set hw.usb2.ulpt.debug=15 and this is the output: uhub_reattach_port:348: port 2 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port:434: device problem (USB_ERR_TIMEOUT), disabling port 2 ugen0.3: at usbus0 ulpt_probe:472: ulpt_attach:498: sc=0xc6f6be80 ulpt0: on usbus0 ulpt_attach:538: setting alternate config number: 0 ulpt0: using bi-directional mode ulpt_reset:164: ulpt_write_callback:203: state=0x0 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x2 after turning off the device i constantly get this output: ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED ulpt_status_callback:328: error=USB_ERR_STALLED the cups daemon cannot be stopped (even with kill -9) and none of the lp* apps work anymore. also i'm not able to attach any new usb devices. so a reboot is the only solution that worked in order to get my computer fully operational again. i'm running: FreeBSD moshnroll 8.0-CURRENT FreeBSD 8.0-CURRENT #6 r189789M: Sat Mar 14 13:37:49 UTC 2009 root@moshnroll:/usr/obj/usr/src/sys/ARUNDEL i386 cheers. From hselasky at c2i.net Sat Mar 14 10:38:06 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Mar 14 10:38:12 2009 Subject: problem with usb printer In-Reply-To: References: Message-ID: <200903141840.33955.hselasky@c2i.net> On Saturday 14 March 2009, Alexander Best wrote: > hi there. > > i'm having a problem with my usb printer. it's being recognised as ulpt0, > but i cannot print. i'm using the cups port for printing. i've set > hw.usb2.ulpt.debug=15 and this is the output: > > uhub_reattach_port:348: port 2 reset failed, error=USB_ERR_TIMEOUT > uhub_reattach_port:434: device problem (USB_ERR_TIMEOUT), disabling port 2 > ugen0.3: at usbus0 > ulpt_probe:472: > ulpt_attach:498: sc=0xc6f6be80 > ulpt0: 1.10/1.00, addr 3> on usbus0 > ulpt_attach:538: setting alternate config number: 0 > ulpt0: using bi-directional mode > ulpt_reset:164: > ulpt_write_callback:203: state=0x0 > ulpt_write_callback:203: state=0x1 > ulpt_write_callback:203: state=0x1 > ulpt_write_callback:203: state=0x2 > > after turning off the device i constantly get this output: > > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > ulpt_status_callback:328: error=USB_ERR_STALLED > > the cups daemon cannot be stopped (even with kill -9) and none of the lp* > apps work anymore. also i'm not able to attach any new usb devices. so a > reboot is the only solution that worked in order to get my computer fully > operational again. What happens if you try to reset the usb device? Maybe you could press CTRL + ALT + ESC and dump all the threads or at least threads having the word "ulpt" in the function names in the backtrace? --HPS From alexbestms at math.uni-muenster.de Sat Mar 14 11:54:58 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Sat Mar 14 11:55:04 2009 Subject: problem with usb printer In-Reply-To: <200903141840.33955.hselasky@c2i.net> Message-ID: what do you mean by reset the device? turning it off and on again? nothing! there's no detach notice or attach notice being printed to the console. what actually happens is this: when i try to print a testpage from the cups web interface it says "Processing page 1...". however the print job doesn't get printed. what happens is that a red light on my printer starts flashing telling me that there's an error. if i try to print the testpage another time the whole web interface stops responding. if i run commands like lp or lpq the apps just hang. also running usbconfig lust let's the application hang. if i turn off the printer the console get's flooded with the ulpt_status_callback:328: error=USB_ERR_STALLED message. before flooding the console with those warnings this one get's printed out: ulpt_write_callback:203: state=0x2 if i reboot the system using reboot the flooding stops and the detach info that wasn't output when i unplugged the device get's printed then. i'm not sure at which pint exactly the following warnings are being produced: ulpt_write_callback:203: state=0x0 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x2 i'll reboot my machine and check it out. i tried hitting ctrl+alt+esc. unfortunately i'm not able to use my keyboard anymore after entering the debugger. :( cheers. Hans Petter Selasky schrieb am 2009-03-14: > On Saturday 14 March 2009, Alexander Best wrote: > > hi there. > > i'm having a problem with my usb printer. it's being recognised as > > ulpt0, > > but i cannot print. i'm using the cups port for printing. i've set > > hw.usb2.ulpt.debug=15 and this is the output: > > uhub_reattach_port:348: port 2 reset failed, error=USB_ERR_TIMEOUT > > uhub_reattach_port:434: device problem (USB_ERR_TIMEOUT), disabling > > port 2 > > ugen0.3: at usbus0 > > ulpt_probe:472: > > ulpt_attach:498: sc=0xc6f6be80 > > ulpt0: > 0/0, rev > > 1.10/1.00, addr 3> on usbus0 > > ulpt_attach:538: setting alternate config number: 0 > > ulpt0: using bi-directional mode > > ulpt_reset:164: > > ulpt_write_callback:203: state=0x0 > > ulpt_write_callback:203: state=0x1 > > ulpt_write_callback:203: state=0x1 > > ulpt_write_callback:203: state=0x2 > > after turning off the device i constantly get this output: > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > the cups daemon cannot be stopped (even with kill -9) and none of > > the lp* > > apps work anymore. also i'm not able to attach any new usb devices. > > so a > > reboot is the only solution that worked in order to get my computer > > fully > > operational again. > What happens if you try to reset the usb device? > Maybe you could press CTRL + ALT + ESC and dump all the threads or at > least > threads having the word "ulpt" in the function names in the > backtrace? > --HPS From alexbestms at math.uni-muenster.de Sat Mar 14 12:17:01 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Sat Mar 14 12:17:17 2009 Subject: problem with usb printer In-Reply-To: <200903141840.33955.hselasky@c2i.net> Message-ID: alright. here's some more information. when i attach the printer i get the following output: uhub_reattach_port:348: port 2 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port:434: device problem (USB_ERR_TIMEOUT), disabling port 2 ugen0.3: at usbus0 ulpt_probe:472: ulpt_attach:498: sc=0xc5f81200 ulpt0: on usbus0 ulpt_attach:538: setting alternate config number: 0 ulpt0: using bi-directional mode when i simply issue a print command using `lp file` i get the following output: ulpt_reset:164: ulpt_write_callback:203: state=0x0 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x1 at this point the printers light flashes a few times indicating that it's about to print. but nothing get's printed. `lpq` tells me that the job has been finished succesfully. the problem where the console get's flooded with warnings and the printer's led reports an error appears randomly. i'm trying to figure out how to exactly to reproduce it. alex Hans Petter Selasky schrieb am 2009-03-14: > On Saturday 14 March 2009, Alexander Best wrote: > > hi there. > > i'm having a problem with my usb printer. it's being recognised as > > ulpt0, > > but i cannot print. i'm using the cups port for printing. i've set > > hw.usb2.ulpt.debug=15 and this is the output: > > uhub_reattach_port:348: port 2 reset failed, error=USB_ERR_TIMEOUT > > uhub_reattach_port:434: device problem (USB_ERR_TIMEOUT), disabling > > port 2 > > ugen0.3: at usbus0 > > ulpt_probe:472: > > ulpt_attach:498: sc=0xc6f6be80 > > ulpt0: > 0/0, rev > > 1.10/1.00, addr 3> on usbus0 > > ulpt_attach:538: setting alternate config number: 0 > > ulpt0: using bi-directional mode > > ulpt_reset:164: > > ulpt_write_callback:203: state=0x0 > > ulpt_write_callback:203: state=0x1 > > ulpt_write_callback:203: state=0x1 > > ulpt_write_callback:203: state=0x2 > > after turning off the device i constantly get this output: > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > the cups daemon cannot be stopped (even with kill -9) and none of > > the lp* > > apps work anymore. also i'm not able to attach any new usb devices. > > so a > > reboot is the only solution that worked in order to get my computer > > fully > > operational again. > What happens if you try to reset the usb device? > Maybe you could press CTRL + ALT + ESC and dump all the threads or at > least > threads having the word "ulpt" in the function names in the > backtrace? > --HPS From alexbestms at math.uni-muenster.de Sat Mar 14 12:47:36 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Sat Mar 14 12:47:43 2009 Subject: problem with usb printer In-Reply-To: <200903141840.33955.hselasky@c2i.net> Message-ID: i've been able to reproduce the error. it only occurs when i print a testpage from the cups web interface. if i simply print a page using `lp` the problem doesn't occur. also the printer needs to have the following device line configured: DeviceURI file:/dev/ulpt0 if DeviceURI is set to usb:/dev/ulpt0 the error doesn't occur when i print a testpage. i'm not sure which exact command is being issued when a testpage is being printed. obviously the error i described only appears in rare situations. so it might not be worth fixing it. however apart from this error i'm not able to print at all. even though there's no crash, nothing get's printed. cheers. Hans Petter Selasky schrieb am 2009-03-14: > On Saturday 14 March 2009, Alexander Best wrote: > > hi there. > > i'm having a problem with my usb printer. it's being recognised as > > ulpt0, > > but i cannot print. i'm using the cups port for printing. i've set > > hw.usb2.ulpt.debug=15 and this is the output: > > uhub_reattach_port:348: port 2 reset failed, error=USB_ERR_TIMEOUT > > uhub_reattach_port:434: device problem (USB_ERR_TIMEOUT), disabling > > port 2 > > ugen0.3: at usbus0 > > ulpt_probe:472: > > ulpt_attach:498: sc=0xc6f6be80 > > ulpt0: > 0/0, rev > > 1.10/1.00, addr 3> on usbus0 > > ulpt_attach:538: setting alternate config number: 0 > > ulpt0: using bi-directional mode > > ulpt_reset:164: > > ulpt_write_callback:203: state=0x0 > > ulpt_write_callback:203: state=0x1 > > ulpt_write_callback:203: state=0x1 > > ulpt_write_callback:203: state=0x2 > > after turning off the device i constantly get this output: > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > ulpt_status_callback:328: error=USB_ERR_STALLED > > the cups daemon cannot be stopped (even with kill -9) and none of > > the lp* > > apps work anymore. also i'm not able to attach any new usb devices. > > so a > > reboot is the only solution that worked in order to get my computer > > fully > > operational again. > What happens if you try to reset the usb device? > Maybe you could press CTRL + ALT + ESC and dump all the threads or at > least > threads having the word "ulpt" in the function names in the > backtrace? > --HPS From hselasky at c2i.net Sat Mar 14 18:08:29 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Mar 14 18:08:34 2009 Subject: problem with usb printer In-Reply-To: References: Message-ID: <200903150210.58509.hselasky@c2i.net> On Saturday 14 March 2009, Alexander Best wrote: > Alexander Best I think there has been a regression. Can you try the following patch: http://perforce.freebsd.org/chv.cgi?CH=159225 --HPS From alexbestms at math.uni-muenster.de Sat Mar 14 18:55:07 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Sat Mar 14 18:55:15 2009 Subject: problem with usb printer In-Reply-To: <200903150210.58509.hselasky@c2i.net> Message-ID: i recompiled my kernel with the p4-files, but still nothing get's printed. this is what i get when attaching the device: ugen0.3: at usbus0 ulpt_probe:472: ulpt_attach:498: sc=0xc5a4c900 ulpt0: on usbus0 ulpt_attach:538: setting alternate config number: 0 ulpt0: using bi-directional mode and this when i try to print something: ulpt_reset:164: ulpt_write_callback:203: state=0x0 ulpt_write_callback:203: state=0x1 ulpt_write_callback:203: state=0x1 i also enabled debugging output in the cups config file, but that didn't reveal any errors. right now i'm trying to build a kernel with the old usb stack to see if the problem get's solved. if the problem then still exists cups must be causing the problems. unfortunately building the kernel with the old usb stack fails: /usr/src/sys/legacy/dev/usb/ehci.c:84:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci.c:85:30: error: dev/usb/usbdivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci.c:86:29: error: dev/usb/usb_mem.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci.c:87:32: error: dev/usb/usb_quirks.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci.c:89:29: error: dev/usb/ehcireg.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci.c:90:29: error: dev/usb/ehcivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci_ddb.c:19:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci_ddb.c:20:30: error: dev/usb/usbdivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci_ddb.c:22:29: error: dev/usb/ehcireg.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci_ddb.c:23:29: error: dev/usb/ehcivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci_pci.c:74:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci_pci.c:75:30: error: dev/usb/usbdivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci_pci.c:76:29: error: dev/usb/usb_mem.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci_pci.c:78:29: error: dev/usb/ehcireg.h: No such file or directory /usr/src/sys/legacy/dev/usb/ehci_pci.c:79:29: error: dev/usb/ehcivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/hid.c:50:25: error: dev/usb/hid.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhci.c:82:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhci.c:83:30: error: dev/usb/usbdivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhci.c:84:29: error: dev/usb/usb_mem.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhci.c:85:32: error: dev/usb/usb_quirks.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhci.c:87:29: error: dev/usb/uhcireg.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhci.c:88:29: error: dev/usb/uhcivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhci_pci.c:69:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhci_pci.c:70:30: error: dev/usb/usbdivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhci_pci.c:71:29: error: dev/usb/usb_mem.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhci_pci.c:73:29: error: dev/usb/uhcireg.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhci_pci.c:74:29: error: dev/usb/uhcivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhub.c:60:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhub.c:61:32: error: dev/usb/usbdi_util.h: No such file or directory /usr/src/sys/legacy/dev/usb/uhub.c:62:30: error: dev/usb/usbdivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/ukbd.c:64:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/ukbd.c:65:32: error: dev/usb/usbdi_util.h: No such file or directory /usr/src/sys/legacy/dev/usb/ukbd.c:67:32: error: dev/usb/usb_quirks.h: No such file or directory /usr/src/sys/legacy/dev/usb/ukbd.c:68:25: error: dev/usb/hid.h: No such file or directory /usr/src/sys/legacy/dev/usb/ulpt.c:63:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/ulpt.c:64:32: error: dev/usb/usbdi_util.h: No such file or directory /usr/src/sys/legacy/dev/usb/ulpt.c:66:32: error: dev/usb/usb_quirks.h: No such file or directory /usr/src/sys/legacy/dev/usb/umass.c:119:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/umass.c:120:32: error: dev/usb/usbdi_util.h: No such file or directory /usr/src/sys/legacy/dev/usb/ums.c:64:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/ums.c:65:32: error: dev/usb/usbdi_util.h: No such file or directory /usr/src/sys/legacy/dev/usb/ums.c:67:32: error: dev/usb/usb_quirks.h: No such file or directory /usr/src/sys/legacy/dev/usb/ums.c:68:25: error: dev/usb/hid.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb.c:78:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb.c:79:32: error: dev/usb/usbdi_util.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb.c:92:30: error: dev/usb/usbdivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb.c:93:32: error: dev/usb/usb_quirks.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb_ethersubr.c:70:35: error: dev/usb/usb_ethersubr.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb_mem.c:68:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb_mem.c:69:55: error: dev/usb/usbdivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb_mem.c:70:29: error: dev/usb/usb_mem.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb_quirks.c:49:32: error: dev/usb/usb_quirks.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb_subr.c:68:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb_subr.c:69:32: error: dev/usb/usbdi_util.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb_subr.c:70:30: error: dev/usb/usbdivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/usb_subr.c:72:32: error: dev/usb/usb_quirks.h: No such file or directory /usr/src/sys/legacy/dev/usb/usbdi.c:57:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/usbdi.c:58:32: error: dev/usb/usbdi_util.h: No such file or directory /usr/src/sys/legacy/dev/usb/usbdi.c:59:30: error: dev/usb/usbdivar.h: No such file or directory /usr/src/sys/legacy/dev/usb/usbdi.c:60:29: error: dev/usb/usb_mem.h: No such file or directory /usr/src/sys/legacy/dev/usb/usbdi.c:61:32: error: dev/usb/usb_quirks.h: No such file or directory /usr/src/sys/legacy/dev/usb/usbdi_util.c:53:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/legacy/dev/usb/usbdi_util.c:54:32: error: dev/usb/usbdi_util.h: No such file or directory /usr/src/sys/netgraph/bluetooth/drivers/ubt/ng_ubt.c:50:27: error: dev/usb/usbdi.h: No such file or directory /usr/src/sys/netgraph/bluetooth/drivers/ubt/ng_ubt.c:51:32: error: dev/usb/usbdi_util.h: No such file or directory /usr/src/sys/netgraph/bluetooth/drivers/ubt/ng_ubt.c:52:30: error: dev/usb/usbdivar.h: No such file or directory mkdep: compile failed *** Error code 1 alex Hans Petter Selasky schrieb am 2009-03-15: > On Saturday 14 March 2009, Alexander Best wrote: > > Alexander Best > I think there has been a regression. Can you try the following patch: > http://perforce.freebsd.org/chv.cgi?CH=159225 > --HPS From thompsa at FreeBSD.org Sat Mar 14 20:36:47 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sat Mar 14 20:36:52 2009 Subject: problem with usb printer In-Reply-To: References: <200903150210.58509.hselasky@c2i.net> Message-ID: <20090315033641.GD24680@citylink.fud.org.nz> On Sun, Mar 15, 2009 at 02:55:04AM +0100, Alexander Best wrote: > i recompiled my kernel with the p4-files, but still nothing get's printed. > > this is what i get when attaching the device: > > ugen0.3: at usbus0 > ulpt_probe:472: > ulpt_attach:498: sc=0xc5a4c900 > ulpt0: 1.10/1.00, addr 3> on usbus0 > ulpt_attach:538: setting alternate config number: 0 > ulpt0: using bi-directional mode > > and this when i try to print something: > > ulpt_reset:164: > ulpt_write_callback:203: state=0x0 > ulpt_write_callback:203: state=0x1 > ulpt_write_callback:203: state=0x1 > > i also enabled debugging output in the cups config file, but that didn't > reveal any errors. > > right now i'm trying to build a kernel with the old usb stack to see if the > problem get's solved. if the problem then still exists cups must be causing > the problems. unfortunately building the kernel with the old usb stack fails: > > /usr/src/sys/legacy/dev/usb/ehci.c:84:27: error: dev/usb/usbdi.h: No such file > or directory You need to add makeoptions WITH_LEGACY to your kernel config so it can find the old usb headers. Andrew From hselasky at c2i.net Sun Mar 15 01:36:21 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Mar 15 01:36:27 2009 Subject: problem with usb printer In-Reply-To: References: Message-ID: <200903150938.49921.hselasky@c2i.net> On Sunday 15 March 2009, Alexander Best wrote: > i recompiled my kernel with the p4-files, but still nothing get's printed. > > this is what i get when attaching the device: > > ugen0.3: at usbus0 > ulpt_probe:472: > ulpt_attach:498: sc=0xc5a4c900 > ulpt0: 1.10/1.00, addr 3> on usbus0 > ulpt_attach:538: setting alternate config number: 0 > ulpt0: using bi-directional mode > > and this when i try to print something: > > ulpt_reset:164: > ulpt_write_callback:203: state=0x0 > ulpt_write_callback:203: state=0x1 > ulpt_write_callback:203: state=0x1 Looks good. Try also: sysctl hw.usb2.dev.debug=15 While printing and see if there is a drain in the end! > > i also enabled debugging output in the cups config file, but that didn't > reveal any errors. > > right now i'm trying to build a kernel with the old usb stack to see if the > problem get's solved. if the problem then still exists cups must be causing > the problems. unfortunately building the kernel with the old usb stack > fails: Did it work before? The only thing I can imagine is that the flushing/drain mechanism is not working, after that the last byte has been written. --HPS From hselasky at c2i.net Sun Mar 15 03:37:12 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Mar 15 03:37:19 2009 Subject: problem with usb printer In-Reply-To: References: Message-ID: <200903151139.42508.hselasky@c2i.net> Hi, I have been able to reproduce the issue over here on an USB printer. Try this patch in addition to the previous ones: http://perforce.freebsd.org/chv.cgi?CH=159241 --HPS From alexbestms at math.uni-muenster.de Sun Mar 15 11:26:46 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Sun Mar 15 11:26:53 2009 Subject: problem with usb printer In-Reply-To: <200903151139.42508.hselasky@c2i.net> Message-ID: i applied the patches. now every time i try to print something the printer indicates an error (red light blinking). i can however turn off the printer and then turn it on again with the printer getting detached and attached properly. if i try to print something after the first attempt to print the issue i described beforehand occurs. cupsd cannot be killed and usb devices cannot be attached/detached. running lp* and usbconfig doesn't work anymore. i need to reboot. cheers. Hans Petter Selasky schrieb am 2009-03-15: > Hi, > I have been able to reproduce the issue over here on an USB printer. > Try this > patch in addition to the previous ones: > http://perforce.freebsd.org/chv.cgi?CH=159241 > --HPS From alexbestms at math.uni-muenster.de Sun Mar 15 12:35:18 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Sun Mar 15 12:35:25 2009 Subject: problem with usb printer In-Reply-To: <200903150938.49921.hselasky@c2i.net> Message-ID: i recompiled my kernel using the usb1 stack and was able to print a perfect testpage. i was able to print using the gdi driver (ulpt and unlpt) and printing with the splix2 driver also works. the splix version from the ports dir doesn't work for some reason. i now installed 4 printers in cups: splix2 (ulpt and unlpt) and gdi (ulpt and unlpt). i'll try to recompile my kernel (usb2) with and without the patches and see if one of those combinations works. cheers. Hans Petter Selasky schrieb am 2009-03-15: > On Sunday 15 March 2009, Alexander Best wrote: > > i recompiled my kernel with the p4-files, but still nothing get's > > printed. > > this is what i get when attaching the device: > > ugen0.3: at usbus0 > > ulpt_probe:472: > > ulpt_attach:498: sc=0xc5a4c900 > > ulpt0: > 0/0, rev > > 1.10/1.00, addr 3> on usbus0 > > ulpt_attach:538: setting alternate config number: 0 > > ulpt0: using bi-directional mode > > and this when i try to print something: > > ulpt_reset:164: > > ulpt_write_callback:203: state=0x0 > > ulpt_write_callback:203: state=0x1 > > ulpt_write_callback:203: state=0x1 > Looks good. > Try also: > sysctl hw.usb2.dev.debug=15 > While printing and see if there is a drain in the end! > > i also enabled debugging output in the cups config file, but that > > didn't > > reveal any errors. > > right now i'm trying to build a kernel with the old usb stack to > > see if the > > problem get's solved. if the problem then still exists cups must be > > causing > > the problems. unfortunately building the kernel with the old usb > > stack > > fails: > Did it work before? > The only thing I can imagine is that the flushing/drain mechanism is > not > working, after that the last byte has been written. > --HPS From alexbestms at math.uni-muenster.de Sun Mar 15 14:15:58 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Sun Mar 15 14:16:05 2009 Subject: problem with usb printer In-Reply-To: <200903151139.42508.hselasky@c2i.net> Message-ID: alright. i've tried various patches and cups drivers. the only combination that slightly works is a kernel with both patchsets in combination with the splix2 driver. alls other combinations of patches and drivers fail without a page being printed and causing the printer to signal an error. with the two patchsets and the splix2 driver i'm able to print about 5% of the testpage. the paper is almost completely empty. only a a little bit of the testpage is being printed onto the top of the page. after ejecting the page the printer signals an error. with the usb1-stack the whole testpage get's printed and the printer stays operational afterwards. also the gdi driver works just like the splix2 driver without any problems. using the usb2-stack the gdi driver causes the printer to signal an error without anything being printed. alex Hans Petter Selasky schrieb am 2009-03-15: > Hi, > I have been able to reproduce the issue over here on an USB printer. > Try this > patch in addition to the previous ones: > http://perforce.freebsd.org/chv.cgi?CH=159241 > --HPS From weongyo.jeong at gmail.com Sun Mar 15 23:21:55 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Sun Mar 15 23:22:02 2009 Subject: USB support in NDIS -- IFF_NEEDSGIANT? In-Reply-To: References: <20090217052121.GB86244@weongyo.cdnetworks.kr> Message-ID: <20090316062150.GC1851@weongyo.cdnetworks.kr> On Fri, Mar 13, 2009 at 11:37:57AM +0000, Robert Watson wrote: > > On Tue, 17 Feb 2009, Weongyo Jeong wrote: > > >>As you know, I've been gradually working to eliminate all non-MPSAFE > >>network device driver infrastructure for 8.0, having removed non-MPSAFE > >>network protocol infrastructure in 7.0. In reviewing remaining drivers > >>using IFF_NEEDSGIANT, I spotted this in the NDIS code: > ... > >>Having taken a glance, it looks like this was added specifically to > >>support > >>USB devices attached via NDIS. > > > >AFAIK all of usb wireless drivers had it so I couldn't avoid it when I had > >implemented. > > > >>With the new USB code, are NDIS drivers still supported? > > > >I think that it would be supported at 8.0 > > > >>And in the new world order, is this IFF_NEEDSGIANT still required? > > > >Probably we can remove the IFF_NEEDSGIANT flags at the new USB code. > > > >>Can I simply remove it once the old USB code is on the way out the door? > > > >IMHO yes I think. > > Dear all: > > A few weeks have passed, so I wanted to check in and see how this project > was going -- are we at a point yet where removing IFF_NEEDSGIANT won't > cause significant loss of functionality? In the current, NDIS USB porting almost have completed and it doesn't use IFF_NEEDSGIANT anymore. With some tests it looks it works well so I think it wouldn't cause any loss of functionality. regards, Weongyo Jeong From hselasky at c2i.net Mon Mar 16 01:22:47 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Mar 16 01:22:54 2009 Subject: problem with usb printer In-Reply-To: References: Message-ID: <200903160925.15806.hselasky@c2i.net> Hi Alexander, There are now multiple outstanding patches. Are you sure you applied all of them? I've attached a diff between -current and USB P4. Some patches might fail regarding the RCS-ID changes. --HPS From bugmaster at FreeBSD.org Mon Mar 16 04:07:06 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Mar 16 04:09:39 2009 Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org Message-ID: <200903161107.n2GB740o043427@freefall.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/132594 usb USB subsystem causes page fault and crashes o usb/132312 usb Xorg 7.4 halts USB controller o usb/132080 usb [patch] [usb] Kernel panic after NOMEM caused by rum 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/131912 usb [uslcom] [patch] New devices using Silicon Labs chips o usb/131900 usb [usbdevs] [patch] Additional product identification co 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 f usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk 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/130325 usb [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh 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 [newusb] DVD drive detects as 'da' device o usb/129964 usb [newusb] disconnection of ugen devices isn't logged o bin/129963 usb [newusb] usbconfig(8) fails with misleading error when o docs/129962 usb [newusb] usbconfig(8) refers to non-existant usb2_core o usb/129945 usb [usbdevs] [patch] add u3g support for Longcheer WM66 U o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [patch] add support for ZTE AC8700 modem o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [patch] Liebert UPS being assigned uhid and o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb] [patch] uaudio is not full duplex o 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 f usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup o usb/127549 usb [umass] [patch] Meizu MiniPlayer M6 (SL) requires some s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127423 usb [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr o usb/127342 usb [boot] cannot enable usb keyboard and mouse support in o kern/127222 usb [ohci]: Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c f 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/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if 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/125264 usb [patch] sysctl for set usb mouse rate (very useful for 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 o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work 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/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 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/122621 usb [patch] [request] New driver for Sierra Wireless 3G US 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/122025 usb [uscanner] [patch] uscanner does not attach to Epson R 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/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] FreeBSD fails to boot with usb legacy support e 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 [umass] [patch] quirk to support ASUS P535 as umass (a 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/120017 usb [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk o usb/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab 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/118686 usb [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround 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 [uaudio] [patch] Not possible to record with Plantroni 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 o 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 [umass] [patch] Problems with connection of the umass o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113977 usb [request] Need a way to set mode of USB disk's write c o usb/113672 usb [ehci] [panic] Kernel panic with AEWIN CB6971 s usb/113629 usb [ukbd] Dropped USB keyboard events on Dell Latitude D6 o usb/113432 usb [ucom] WARNING: attempt to net_add_domain(netgraph) af a usb/113060 usb [usbdevs] [patch] Samsung printer not working in bidir o usb/112944 usb [ulpt] [patch] Bi-directional access to HP LaserJet 10 o usb/112640 usb [usb] [hang] Kernel freezes when writing a file to an o usb/112631 usb [panic] Problem with SONY DSC-S80 camera on umount s usb/112568 usb [umass] [request] USB mode may wrong when mounting Pla o usb/112463 usb [umass] problem with Samsung USB DVD writer, libscg an o usb/112461 usb [ehci] [request] ehci USB 2.0 doesn't work on nforce4 o usb/111753 usb [uhid] [panic] Replicable system panic involving UHID s usb/110991 usb [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends o usb/110988 usb [umass] [patch] Handling of quirk IGNORE_RESIDUE is um o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC o usb/109397 usb [panic] on boot from USB flash o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr s usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/108056 usb [ohci] Mouse gets powered off during device probe when o usb/107935 usb [uplcom] [panic] panic while accessing /dev/cuaU0 o usb/107924 usb [patch] usbd(8) does not call detach o usb/107848 usb [umass] [request] cannot access Samsung flash disk o usb/107827 usb [ohci] [panic] ohci_add_done addr not found o usb/107496 usb [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [ o usb/107388 usb [patch] [request] new driver: add utoppy device from N o usb/107248 usb [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP o usb/107243 usb [cam] [patch] Apacer USB Flash Drive quirk o usb/106861 usb [usbdevs] [patch]: usbdevs update: Add product ACER Ze s usb/106832 usb [usb] USB HP printer is not detected by kernel when AC o usb/106648 usb [umass] [hang] USB Floppy on D1950 10 min Hang on Inse o usb/106621 usb [axe] [patch] DLINK DUB-E100 support broken o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106041 usb [usb] [request] FreeBSD does not recognise Mustek Bear o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/105186 usb [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c o usb/105065 usb [ata] [usb] SATA - USB Bridge o usb/104830 usb [umass] system crashes when copying data to umass devi o usb/104645 usb [umass] [request] Rave C-201 MP3 player does not commu o usb/104352 usb [ural] [patch] ural driver doesnt work o usb/104292 usb [umass] [hang] system lockup on forced umount of usb-s o usb/104290 usb [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto o usb/103917 usb [uhub] USB driver reports "Addr 0 should never happen" o usb/103418 usb usbhidctl(1): [patch] [request] usbhidctl: add ability o usb/103289 usb [request] USB 2.0 problems on AMD LX-800 CPU and CS-55 o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103025 usb [uhub] [panic] wrong detection of USB device for FreeB o usb/102976 usb [panic] Casio Exilim Digital Camera causes panic on in o usb/102678 usb [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/101761 usb [usb] [patch] [request] usb.h: increase maximal size o o usb/101752 usb [umass] [panic] 6.1-RELEASE kernel panic on usb device o usb/101448 usb [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O o usb/101096 usb [ural] [panic] USB WLAN occasionally causes kernel-pan o usb/100746 usb [keyboard] system does not boot due to USB keyboard pr o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar 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/93408 usb [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w 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 o 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/91629 usb [usb] usbd_abort_pipe() may result in infinite loop 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 f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US 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 f usb/83677 usb [usb] [request] usb controller often not detected (Sun 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/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu 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 " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, 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 o 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 o usb/75797 usb [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o 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 i386/46371 usb USB controller cannot be initialized on IBM Netfinity 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 305 problems total. From alexbestms at math.uni-muenster.de Mon Mar 16 04:48:37 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Mon Mar 16 04:48:44 2009 Subject: problem with usb printer In-Reply-To: <200903160925.15806.hselasky@c2i.net> Message-ID: to be sure i updated my sources using `svn up /usr/src` then reverted back to the repository files in order to get rid of any previously patched files using `svn -R revert /usr/src` and the applied the patch you send me. the result is the same: only the top of the page get's printed. that's it. the printer signals an error. at this point i need to turn off the printer and turn it on again in order to use it again. if i try to print another page without restarting the printer usb becomes unusable. i've attached my kernel config and my make.conf. maybe there's a problem there. cheers. Hans Petter Selasky schrieb am 2009-03-16: > Hi Alexander, > There are now multiple outstanding patches. Are you sure you applied > all of > them? I've attached a diff between -current and USB P4. Some patches > might > fail regarding the RCS-ID changes. > --HPS -------------- next part -------------- A non-text attachment was scrubbed... Name: arundel Type: application/octet-stream Size: 2830 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090316/046d62ef/arundel.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: make.conf Type: application/octet-stream Size: 536 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090316/046d62ef/make.obj From hselasky at c2i.net Mon Mar 16 07:53:24 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon Mar 16 07:53:34 2009 Subject: problem with usb printer In-Reply-To: References: Message-ID: <200903161555.49172.hselasky@c2i.net> Hi, It seems like I have introduced a regression in ULPT and USCANNER. Code has been reverted to be similar to USB1 behaviour. http://perforce.freebsd.org/chv.cgi?CH=159292 Thanks for reporting and testing! --HPS From torfinn.ingolfsen at broadpark.no Mon Mar 16 12:56:31 2009 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Mon Mar 16 12:56:38 2009 Subject: Xorg 7.4 and umass devices - a bad combination? Message-ID: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> Hi, Have anyone seen bad performance when using umass devices (external hard drives) in combination with Xorg 7.4? The reason I ask is that I have this machine[1] which is both a test workstation, and cheap-ass fileserver. I am using external usb drives for storage (it was the cheapest option when I set this up). root@kg-quiet# dmesg | grep da[01234] da4 at sbp0 bus 0 target 0 lun 0 da4: Fixed Direct Access SCSI-4 device da4: 50.000MB/s transfers da4: 286188MB (586114704 512 byte sectors: 255H 63S/T 36483C) da3 at umass-sim3 bus 3 target 0 lun 0 da3: Fixed Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) da2 at umass-sim2 bus 2 target 0 lun 0 da2: Fixed Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) da1 at umass-sim1 bus 1 target 0 lun 0 da1: Fixed Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) Yes, there is a firewire drive in there too. The machine currently runs FreeBSD 6.4-stable / amd64, and have run through most releases sine 6.1-prerelease. I use Samba for file serving. root@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 6.4-STABLE FreeBSD 6.4-STABLE #27: Sun Mar 15 19:42:19 CET 2009 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 The machine have always been in X when it is up (I use XFce) and this hasn't created any problems that I have noticed. However, after I upgraded Xorg to 7.4, I get lots of these messages in /var/log/messages if I try to do a simple 'ls' on any filesystem on a usb drive: Mar 16 17:09:02 kg-quiet kernel: umass2: BBB bulk-out clear stall failed, TIMEOUT Mar 16 17:09:31 kg-quiet kernel: umass1: BBB bulk-out clear stall failed, TIMEOUT Mar 16 17:10:00 kg-quiet kernel: umass3: BBB bulk-out clear stall failed, TIMEOUT Mar 16 17:10:43 kg-quiet kernel: umass0: BBB reset failed, TIMEOUT Mar 16 17:11:12 kg-quiet kernel: umass2: BBB reset failed, TIMEOUT Mar 16 17:11:41 kg-quiet kernel: umass1: BBB reset failed, TIMEOUT Mar 16 17:11:48 kg-quiet kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Mar 16 17:12:10 kg-quiet kernel: umass3: BBB reset failed, TIMEOUT Followed by these: Mar 16 17:12:53 kg-quiet kernel: g_vfs_done():da0s1d[WRITE(offset=196864589824, length=16384)]error = 5 Mar 16 17:12:53 kg-quiet kernel: g_vfs_done():da0s1d[WRITE(offset=114688, length=16384)]error = 5 Mar 16 17:13:15 kg-quiet kernel: umass3: BBB bulk-in clear stall failed, TIMEOUT Mar 16 17:13:22 kg-quiet kernel: umass2: BBB bulk-out clear stall failed, TIMEOUT Mar 16 17:13:22 kg-quiet kernel: g_vfs_done():da2s1d[WRITE(offset=357707874304, length=16384)]error = 5 Mar 16 17:13:22 kg-quiet kernel: g_vfs_done():da2s1d[WRITE(offset=114688, length=16384)]error = 5 and the 'ls' takes several minutes to complete. Notice that the messages mention all umass drives (umass0 - umass3), even if I only do an ls on one of them. Also notice that the firewire drive is absent fom any messages. Note: hal is NOT running on this machine. What is my workaround? Reboot the machine (needing a forced reset, as the machine hangs on shutdown after the umass errors), let fsck do its thing and then don't start Xorg. But this is no solution. The funny thing is that It worked find before I upgraded Xorg from 7.3.2 to 7.4... Any hints on how I can debug this? More info: FreeBSD work log[2], dmesg output normal[3] and verbose[4]. References: 1) http://tingox.googlepages.com/rs480m2 2) http://tingox.googlepages.com/rs480m2_freebsd 3) http://tingox.googlepages.com/quiet-dmesg-6.4-stable-20090315.txt 4) http://tingox.googlepages.com/quiet-dmesg-6.4-stable-20090315_verb.txt -- Regards, Torfinn Ingolfsen, Norway From imp at bsdimp.com Mon Mar 16 13:01:46 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Mar 16 13:01:52 2009 Subject: Xorg 7.4 and umass devices - a bad combination? In-Reply-To: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> References: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> Message-ID: <20090317.050116.76561605.imp@bsdimp.com> In message: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> Torfinn Ingolfsen writes: : Have anyone seen bad performance when using umass devices (external : hard drives) in combination with Xorg 7.4? I don't see it. But I'm not using a usb mouse/keyboard... Are you? Warner : The reason I ask is that I have this machine[1] which is both a test : workstation, and cheap-ass fileserver. I am using external usb drives : for storage (it was the cheapest option when I set this up). : root@kg-quiet# dmesg | grep da[01234] : da4 at sbp0 bus 0 target 0 lun 0 : da4: Fixed Direct Access SCSI-4 device : da4: 50.000MB/s transfers : da4: 286188MB (586114704 512 byte sectors: 255H 63S/T 36483C) : da3 at umass-sim3 bus 3 target 0 lun 0 : da3: Fixed Direct Access SCSI-0 device : da3: 40.000MB/s transfers : da3: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) : da2 at umass-sim2 bus 2 target 0 lun 0 : da2: Fixed Direct Access SCSI-0 device : da2: 40.000MB/s transfers : da2: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) : da1 at umass-sim1 bus 1 target 0 lun 0 : da1: Fixed Direct Access SCSI-0 device : da1: 40.000MB/s transfers : da1: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) : da0 at umass-sim0 bus 0 target 0 lun 0 : da0: Fixed Direct Access SCSI-0 device : da0: 40.000MB/s transfers : da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) : : Yes, there is a firewire drive in there too. : : The machine currently runs FreeBSD 6.4-stable / amd64, and have run : through most releases sine 6.1-prerelease. I use Samba for file serving. : root@kg-quiet# uname -a : FreeBSD kg-quiet.kg4.no 6.4-STABLE FreeBSD 6.4-STABLE #27: Sun Mar 15 : 19:42:19 CET 2009 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET : amd64 : : The machine have always been in X when it is up (I use XFce) and this hasn't created any problems that I have noticed. : However, after I upgraded Xorg to 7.4, I get lots of these messages in /var/log/messages if I try to : do a simple 'ls' on any filesystem on a usb drive: : Mar 16 17:09:02 kg-quiet kernel: umass2: BBB bulk-out clear stall failed, TIMEOUT : Mar 16 17:09:31 kg-quiet kernel: umass1: BBB bulk-out clear stall failed, TIMEOUT : Mar 16 17:10:00 kg-quiet kernel: umass3: BBB bulk-out clear stall failed, TIMEOUT : Mar 16 17:10:43 kg-quiet kernel: umass0: BBB reset failed, TIMEOUT : Mar 16 17:11:12 kg-quiet kernel: umass2: BBB reset failed, TIMEOUT : Mar 16 17:11:41 kg-quiet kernel: umass1: BBB reset failed, TIMEOUT : Mar 16 17:11:48 kg-quiet kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT : Mar 16 17:12:10 kg-quiet kernel: umass3: BBB reset failed, TIMEOUT : : Followed by these: : Mar 16 17:12:53 kg-quiet kernel: g_vfs_done():da0s1d[WRITE(offset=196864589824, length=16384)]error = 5 : Mar 16 17:12:53 kg-quiet kernel: g_vfs_done():da0s1d[WRITE(offset=114688, length=16384)]error = 5 : Mar 16 17:13:15 kg-quiet kernel: umass3: BBB bulk-in clear stall failed, TIMEOUT : Mar 16 17:13:22 kg-quiet kernel: umass2: BBB bulk-out clear stall failed, TIMEOUT : Mar 16 17:13:22 kg-quiet kernel: g_vfs_done():da2s1d[WRITE(offset=357707874304, length=16384)]error = 5 : Mar 16 17:13:22 kg-quiet kernel: g_vfs_done():da2s1d[WRITE(offset=114688, length=16384)]error = 5 : : and the 'ls' takes several minutes to complete. : : Notice that the messages mention all umass drives (umass0 - umass3), even if I only do an ls on one of them. : Also notice that the firewire drive is absent fom any messages. : Note: hal is NOT running on this machine. : : What is my workaround? Reboot the machine (needing a forced reset, as the machine hangs on shutdown : after the umass errors), let fsck do its thing and then don't start Xorg. But this is no solution. : : The funny thing is that It worked find before I upgraded Xorg from 7.3.2 to 7.4... : : Any hints on how I can debug this? : : More info: FreeBSD work log[2], dmesg output normal[3] and verbose[4]. : : References: : 1) http://tingox.googlepages.com/rs480m2 : 2) http://tingox.googlepages.com/rs480m2_freebsd : 3) http://tingox.googlepages.com/quiet-dmesg-6.4-stable-20090315.txt : 4) http://tingox.googlepages.com/quiet-dmesg-6.4-stable-20090315_verb.txt : -- : Regards, : Torfinn Ingolfsen, : Norway : : _______________________________________________ : 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" : : From torfinn.ingolfsen at broadpark.no Mon Mar 16 15:15:16 2009 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Mon Mar 16 15:15:23 2009 Subject: Xorg 7.4 and umass devices - a bad combination? In-Reply-To: <20090317.050116.76561605.imp@bsdimp.com> References: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> <20090317.050116.76561605.imp@bsdimp.com> Message-ID: <20090316231513.208750bf.torfinn.ingolfsen@broadpark.no> On Tue, 17 Mar 2009 05:01:16 +0900 (JST) "M. Warner Losh" wrote: > In message: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> > Torfinn Ingolfsen writes: > : Have anyone seen bad performance when using umass devices (external > : hard drives) in combination with Xorg 7.4? > > I don't see it. > > But I'm not using a usb mouse/keyboard... Are you? No, I am not. PS/" mouse and keyboard here. This is very strange, very puzzling. -- Regards, Torfinn Ingolfsen From hselasky at c2i.net Tue Mar 17 00:54:38 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Tue Mar 17 00:54:44 2009 Subject: Xorg 7.4 and umass devices - a bad combination? In-Reply-To: <20090316231513.208750bf.torfinn.ingolfsen@broadpark.no> References: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> <20090317.050116.76561605.imp@bsdimp.com> <20090316231513.208750bf.torfinn.ingolfsen@broadpark.no> Message-ID: <200903170857.07049.hselasky@c2i.net> On Monday 16 March 2009, Torfinn Ingolfsen wrote: > On Tue, 17 Mar 2009 05:01:16 +0900 (JST) > > "M. Warner Losh" wrote: > > In message: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> > > > > Torfinn Ingolfsen writes: > > : Have anyone seen bad performance when using umass devices (external > > : hard drives) in combination with Xorg 7.4? > > > > I don't see it. > > > > But I'm not using a usb mouse/keyboard... Are you? > > No, I am not. PS/" mouse and keyboard here. > > This is very strange, very puzzling. It's maybe an interrupt problem. Can you do some vmstat'ing before and after ? Also try to upgrade the kernel to the lastest sources. There has been an EHCI performance quirk added recently. --HPS From xcllnt at mac.com Tue Mar 17 13:23:41 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Tue Mar 17 13:23:48 2009 Subject: USB2: usb_device_info not declared (redux) Message-ID: I got the following error building KDE4 on FreeBSD/powerpc (-current): In file included from /usr/obj/nfs/freebsd/ports/x11/kdebase4/work/ kdebase-4.2.1/apps/kinfocenter/usbview/kcmusb.cpp:27: /usr/obj/nfs/freebsd/ports/x11/kdebase4/work/kdebase-4.2.1/apps/ kinfocenter/usbview/usbdevices.h:80: error: 'usb_device_info' has not been declared *** Error code 1 Do we have closure on where it's going to be fixed? Do we know if GNOME is affected as well? Andrew: you were think about adding the ioctl. Did you reach a conclusion? -- Marcel Moolenaar xcllnt@mac.com From torfinn.ingolfsen at broadpark.no Tue Mar 17 14:44:15 2009 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Tue Mar 17 14:44:21 2009 Subject: Xorg 7.4 and umass devices - a bad combination? In-Reply-To: <20090316231513.208750bf.torfinn.ingolfsen@broadpark.no> References: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> <20090317.050116.76561605.imp@bsdimp.com> <20090316231513.208750bf.torfinn.ingolfsen@broadpark.no> Message-ID: <20090317224409.e0d71dc4.torfinn.ingolfsen@broadpark.no> On Mon, 16 Mar 2009 23:15:13 +0100 Torfinn Ingolfsen wrote: > No, I am not. PS/" mouse and keyboard here. should read: PS/2 mouse and keyboard. -- Torfinn From torfinn.ingolfsen at broadpark.no Tue Mar 17 14:55:03 2009 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Tue Mar 17 14:55:11 2009 Subject: Xorg 7.4 and umass devices - a bad combination? In-Reply-To: <200903170857.07049.hselasky@c2i.net> References: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> <20090317.050116.76561605.imp@bsdimp.com> <20090316231513.208750bf.torfinn.ingolfsen@broadpark.no> <200903170857.07049.hselasky@c2i.net> Message-ID: <20090317225459.d709b94a.torfinn.ingolfsen@broadpark.no> On Tue, 17 Mar 2009 08:57:06 +0100 Hans Petter Selasky wrote: > It's maybe an interrupt problem. Can you do some vmstat'ing before > and after ? After starting Xorg (with startx this time), but before doing an 'ls' on one of the usb drives: root@kg-quiet# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in sy cs us sy id 1 0 0 136M 2736M 512 4 11 0 438 0 0 0 198 1604 570 1 1 98 After issuing the 'ls' command (and still waiting for it to complete): root@kg-quiet# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in sy cs us sy id 1 1 0 136M 2736M 474 4 10 0 405 0 0 0 205 1484 573 1 1 98 root@kg-quiet# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in sy cs us sy id 1 1 0 136M 2736M 470 4 10 0 402 0 0 0 206 1473 574 1 1 98 root@kg-quiet# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in sy cs us sy id 1 1 0 136M 2736M 469 4 10 0 401 0 0 0 206 1469 574 1 1 98 root@kg-quiet# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in sy cs us sy id 1 1 0 136M 2736M 468 4 10 0 400 0 0 0 206 1464 574 1 1 98 root@kg-quiet# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in sy cs us sy id 1 1 0 136M 2736M 466 4 10 0 399 0 0 0 206 1459 574 1 1 98 root@kg-quiet# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in sy cs us sy id 1 1 0 136M 2736M 467 4 10 0 399 0 0 0 207 1460 576 1 1 98 root@kg-quiet# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in sy cs us sy id 1 1 0 136M 2736M 466 4 10 0 398 0 0 0 207 1456 576 1 1 98 root@kg-quiet# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in sy cs us sy id 1 1 0 136M 2736M 464 4 10 0 397 0 0 0 208 1451 576 1 1 98 root@kg-quiet# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in sy cs us sy id 1 1 0 136M 2736M 463 4 9 0 396 0 0 0 208 1447 576 1 1 98 I can't see anything odd from these. Can you? Now it is several minutes later,. the 'ls' command still hasn't completed, and I try vmstat once more: root@kg-quiet# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in sy cs us sy id 0 1 0 136M 2736M 214 2 4 0 183 0 0 0 252 676 606 0 1 99 I now have several timeout messages in /var/log/messages: Mar 17 22:48:56 kg-quiet kernel: umass1: BBB reset failed, TIMEOUT Mar 17 22:48:56 kg-quiet kernel: umass3: BBB reset failed, TIMEOUT Mar 17 22:48:56 kg-quiet kernel: umass2: BBB reset failed, TIMEOUT Mar 17 22:48:56 kg-quiet kernel: umass0: BBB reset failed, TIMEOUT Mar 17 22:50:01 kg-quiet kernel: umass1: BBB bulk-in clear stall failed, TIMEOUT Mar 17 22:50:01 kg-quiet kernel: umass3: BBB bulk-in clear stall failed, TIMEOUT Mar 17 22:50:01 kg-quiet kernel: umass2: BBB bulk-in clear stall failed, TIMEOUT Mar 17 22:50:01 kg-quiet kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Mar 17 22:51:06 kg-quiet kernel: umass1: BBB bulk-out clear stall failed, TIMEOUT Mar 17 22:51:06 kg-quiet kernel: umass3: BBB bulk-out clear stall failed, TIMEOUT Mar 17 22:51:06 kg-quiet kernel: umass2: BBB bulk-out clear stall failed, TIMEOUT Mar 17 22:51:06 kg-quiet kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Mar 17 22:53:16 kg-quiet kernel: umass1: BBB reset failed, TIMEOUT Mar 17 22:53:16 kg-quiet kernel: umass3: BBB reset failed, TIMEOUT Mar 17 22:53:16 kg-quiet kernel: umass2: BBB reset failed, TIMEOUT Mar 17 22:53:16 kg-quiet kernel: umass0: BBB reset failed, TIMEOUT Mar 17 22:54:21 kg-quiet kernel: umass1: BBB bulk-in clear stall failed, TIMEOUT Mar 17 22:54:21 kg-quiet kernel: umass3: BBB bulk-in clear stall failed, TIMEOUT Mar 17 22:54:21 kg-quiet kernel: umass2: BBB bulk-in clear stall failed, TIMEOUT Mar 17 22:54:21 kg-quiet kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT > Also try to upgrade the kernel to the lastest sources. There has been > an EHCI performance quirk added recently. Is this update in RELENG_6 as well? I am running: root@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 6.4-STABLE FreeBSD 6.4-STABLE #27: Sun Mar 15 19:42:19 CET 2009 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 which is quite recent (but RELENG_6). HTH -- Regards, Torfinn Ingolfsen From marcus at marcuscom.com Tue Mar 17 14:55:57 2009 From: marcus at marcuscom.com (Joe Marcus Clarke) Date: Tue Mar 17 14:56:04 2009 Subject: USB2: usb_device_info not declared (redux) In-Reply-To: References: Message-ID: <1237326957.5465.100.camel@shumai.marcuscom.com> On Tue, 2009-03-17 at 13:23 -0700, Marcel Moolenaar wrote: > I got the following error building KDE4 on FreeBSD/powerpc (-current): > > In file included from /usr/obj/nfs/freebsd/ports/x11/kdebase4/work/ > kdebase-4.2.1/apps/kinfocenter/usbview/kcmusb.cpp:27: > /usr/obj/nfs/freebsd/ports/x11/kdebase4/work/kdebase-4.2.1/apps/ > kinfocenter/usbview/usbdevices.h:80: error: 'usb_device_info' has not > been declared > *** Error code 1 > > Do we have closure on where it's going to be fixed? > Do we know if GNOME is affected as well? All GNOME Desktop components should now be building on the latest -CURRENT. Joe > > Andrew: you were think about adding the ioctl. > Did you reach a conclusion? > -- PGP Key : http://www.marcuscom.com/pgp.asc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090317/1d70fb50/attachment.pgp From xcllnt at mac.com Tue Mar 17 15:27:19 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Tue Mar 17 15:27:31 2009 Subject: USB2: usb_device_info not declared (redux) In-Reply-To: <1237326957.5465.100.camel@shumai.marcuscom.com> References: <1237326957.5465.100.camel@shumai.marcuscom.com> Message-ID: <94E025C2-8AC4-4AAF-B7D2-43B836D1CC36@mac.com> On Mar 17, 2009, at 2:55 PM, Joe Marcus Clarke wrote: > On Tue, 2009-03-17 at 13:23 -0700, Marcel Moolenaar wrote: >> I got the following error building KDE4 on FreeBSD/powerpc (- >> current): >> >> In file included from /usr/obj/nfs/freebsd/ports/x11/kdebase4/work/ >> kdebase-4.2.1/apps/kinfocenter/usbview/kcmusb.cpp:27: >> /usr/obj/nfs/freebsd/ports/x11/kdebase4/work/kdebase-4.2.1/apps/ >> kinfocenter/usbview/usbdevices.h:80: error: 'usb_device_info' has not >> been declared >> *** Error code 1 >> >> Do we have closure on where it's going to be fixed? >> Do we know if GNOME is affected as well? > > All GNOME Desktop components should now be building on the latest > -CURRENT. Ok. I guess we change consumers. I switch to GNOME again (I keep ping-ponging :-) Thanks for tracking -current so closely. It's very much appreciated! -- Marcel Moolenaar xcllnt@mac.com From marcus at marcuscom.com Tue Mar 17 15:37:06 2009 From: marcus at marcuscom.com (Joe Marcus Clarke) Date: Tue Mar 17 15:37:23 2009 Subject: USB2: usb_device_info not declared (redux) In-Reply-To: <94E025C2-8AC4-4AAF-B7D2-43B836D1CC36@mac.com> References: <1237326957.5465.100.camel@shumai.marcuscom.com> <94E025C2-8AC4-4AAF-B7D2-43B836D1CC36@mac.com> Message-ID: <1237329427.5465.136.camel@shumai.marcuscom.com> On Tue, 2009-03-17 at 15:27 -0700, Marcel Moolenaar wrote: > On Mar 17, 2009, at 2:55 PM, Joe Marcus Clarke wrote: > > > On Tue, 2009-03-17 at 13:23 -0700, Marcel Moolenaar wrote: > >> I got the following error building KDE4 on FreeBSD/powerpc (- > >> current): > >> > >> In file included from /usr/obj/nfs/freebsd/ports/x11/kdebase4/work/ > >> kdebase-4.2.1/apps/kinfocenter/usbview/kcmusb.cpp:27: > >> /usr/obj/nfs/freebsd/ports/x11/kdebase4/work/kdebase-4.2.1/apps/ > >> kinfocenter/usbview/usbdevices.h:80: error: 'usb_device_info' has not > >> been declared > >> *** Error code 1 > >> > >> Do we have closure on where it's going to be fixed? > >> Do we know if GNOME is affected as well? > > > > All GNOME Desktop components should now be building on the latest > > -CURRENT. > > Ok. I guess we change consumers. > > I switch to GNOME again (I keep ping-ponging :-) > > Thanks for tracking -current so closely. It's very much appreciated! Tracking -CURRENT is the key. This means running delete-old and delete-old-libs, and removing stale packages. In this case, you should NOT have devel/libusb installed on -CURRENT anymore. If you do that, you shouldn't have any issues with GNOME. I'm running GNOME 2.25 on -CURRENT i386 and amd64 quite well. I assume 2.24 should be okay, but any issues found will be fixed. Joe > -- PGP Key : http://www.marcuscom.com/pgp.asc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20090317/eb2d98ec/attachment.pgp From jrh29 at alumni.cwru.edu Tue Mar 17 18:10:58 2009 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Tue Mar 17 18:11:05 2009 Subject: USB2: usb_device_info not declared (redux) In-Reply-To: <94E025C2-8AC4-4AAF-B7D2-43B836D1CC36@mac.com> References: <1237326957.5465.100.camel@shumai.marcuscom.com> <94E025C2-8AC4-4AAF-B7D2-43B836D1CC36@mac.com> Message-ID: <20090317225553.GA20340@narn.knownspace> On Tue, Mar 17, 2009 at 03:27:17PM -0700, Marcel Moolenaar wrote: > > On Mar 17, 2009, at 2:55 PM, Joe Marcus Clarke wrote: > > > On Tue, 2009-03-17 at 13:23 -0700, Marcel Moolenaar wrote: > >> I got the following error building KDE4 on FreeBSD/powerpc (- > >> current): > >> > >> In file included from /usr/obj/nfs/freebsd/ports/x11/kdebase4/work/ > >> kdebase-4.2.1/apps/kinfocenter/usbview/kcmusb.cpp:27: > >> /usr/obj/nfs/freebsd/ports/x11/kdebase4/work/kdebase-4.2.1/apps/ > >> kinfocenter/usbview/usbdevices.h:80: error: 'usb_device_info' has not > >> been declared > >> *** Error code 1 > >> > >> Do we have closure on where it's going to be fixed? > >> Do we know if GNOME is affected as well? > > > > All GNOME Desktop components should now be building on the latest > > -CURRENT. > > Ok. I guess we change consumers. > > I switch to GNOME again (I keep ping-ponging :-) > > Thanks for tracking -current so closely. It's very much appreciated! > > -- > Marcel Moolenaar > xcllnt@mac.com A patch to kdebase4 was applied recently as well (last couple days). Updating your ports tree to today's should fix that. - Justin From hselasky at c2i.net Wed Mar 18 00:50:19 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 18 00:50:27 2009 Subject: q: USB_SET_TIMEOUT in ugen. In-Reply-To: <20090318073032.GA12632@weongyo.cdnetworks.kr> References: <20090318073032.GA12632@weongyo.cdnetworks.kr> Message-ID: <200903180852.48034.hselasky@c2i.net> Hi, On Wednesday 18 March 2009, Weongyo Jeong wrote: > Hello, > > During porting uath(4) to usb2 I found the following code failed to run: > > data = open("/dev/usb/0.2.2", O_WRONLY, 0); > timeout = UATH_DATA_TIMEOUT; > if (ioctl(data, USB_SET_TIMEOUT, &timeout) < 0) > err(-1, "%s: USB_SET_TIMEOUT(%u)", datadev, > UATH_DATA_TIMEOUT); > > and the error was: > > uathload: /dev/usb/0.2.2: USB_SET_TIMEOUT(1000): Invalid > argument Use the following macro instead: #define USB_SET_TX_TIMEOUT _IOW ('U', 137, int) There also is a match for USB_SET_RX_TIMEOUT . USB_SET_TIMEOUT has been removed. Also don't forget to include "usb_ioctl.h" . Another idea: Port the program to libusb .... > > It looks it's ok with calling ioctl(msg, USB_SET_TIMEOUT, ..) to > /dev/usb/0.2.1 > > And the behaviour of program isn't likely with usb1 that it worked well > in usb1. After writing some data into msg and data pipe there was no > any response using read(2). The problem source can be found at:. > > http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo >/wireless/src/usr.sbin/uathload&HIDEDEL=NO > > Are there something I missed in here? > See hints above. --HPS From weongyo.jeong at gmail.com Wed Mar 18 01:00:20 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Wed Mar 18 01:00:31 2009 Subject: q: USB_SET_TIMEOUT in ugen. Message-ID: <20090318073032.GA12632@weongyo.cdnetworks.kr> Hello, During porting uath(4) to usb2 I found the following code failed to run: data = open("/dev/usb/0.2.2", O_WRONLY, 0); timeout = UATH_DATA_TIMEOUT; if (ioctl(data, USB_SET_TIMEOUT, &timeout) < 0) err(-1, "%s: USB_SET_TIMEOUT(%u)", datadev, UATH_DATA_TIMEOUT); and the error was: uathload: /dev/usb/0.2.2: USB_SET_TIMEOUT(1000): Invalid argument It looks it's ok with calling ioctl(msg, USB_SET_TIMEOUT, ..) to /dev/usb/0.2.1 And the behaviour of program isn't likely with usb1 that it worked well in usb1. After writing some data into msg and data pipe there was no any response using read(2). The problem source can be found at:. http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/usr.sbin/uathload&HIDEDEL=NO Are there something I missed in here? regards, Weongyo Jeong From weongyo.jeong at gmail.com Wed Mar 18 04:46:51 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Wed Mar 18 04:47:08 2009 Subject: q: USB_SET_TIMEOUT in ugen. In-Reply-To: <200903180852.48034.hselasky@c2i.net> References: <20090318073032.GA12632@weongyo.cdnetworks.kr> <200903180852.48034.hselasky@c2i.net> Message-ID: <20090318114642.GB12632@weongyo.cdnetworks.kr> On Wed, Mar 18, 2009 at 08:52:47AM +0100, Hans Petter Selasky wrote: > Hi, > > On Wednesday 18 March 2009, Weongyo Jeong wrote: > > Hello, > > > > During porting uath(4) to usb2 I found the following code failed to run: > > > > data = open("/dev/usb/0.2.2", O_WRONLY, 0); > > timeout = UATH_DATA_TIMEOUT; > > if (ioctl(data, USB_SET_TIMEOUT, &timeout) < 0) > > err(-1, "%s: USB_SET_TIMEOUT(%u)", datadev, > > UATH_DATA_TIMEOUT); > > > > and the error was: > > > > uathload: /dev/usb/0.2.2: USB_SET_TIMEOUT(1000): Invalid > > argument > > Use the following macro instead: > > #define USB_SET_TX_TIMEOUT _IOW ('U', 137, int) > > There also is a match for USB_SET_RX_TIMEOUT . > > USB_SET_TIMEOUT has been removed. > > Also don't forget to include "usb_ioctl.h" . > > Another idea: > > Port the program to libusb .... > > > > > It looks it's ok with calling ioctl(msg, USB_SET_TIMEOUT, ..) to > > /dev/usb/0.2.1 > > > > And the behaviour of program isn't likely with usb1 that it worked well > > in usb1. After writing some data into msg and data pipe there was no > > any response using read(2). The problem source can be found at:. > > > > http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo > >/wireless/src/usr.sbin/uathload&HIDEDEL=NO > > > > Are there something I missed in here? > > > > See hints above. Thank you for advise. :-) I've solve `Invalid argument' error. However the program looks it still doesn't work. All functions the problem used are open(2), ioctl(2), read(2) and write(2). I think I can try to use libusb but it'd be better if it works again using the above 4 system calls. Is it supported in CURRENT or is it a one of regression? regards, Weongyo Jeong From hselasky at c2i.net Wed Mar 18 06:51:51 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 18 06:51:59 2009 Subject: q: USB_SET_TIMEOUT in ugen. In-Reply-To: <20090318114642.GB12632@weongyo.cdnetworks.kr> References: <20090318073032.GA12632@weongyo.cdnetworks.kr> <200903180852.48034.hselasky@c2i.net> <20090318114642.GB12632@weongyo.cdnetworks.kr> Message-ID: <200903181454.18859.hselasky@c2i.net> On Wednesday 18 March 2009, Weongyo Jeong wrote: > On Wed, Mar 18, 2009 at 08:52:47AM +0100, Hans Petter Selasky wrote: > > Hi, > > > > On Wednesday 18 March 2009, Weongyo Jeong wrote: > > > Hello, > > > > > > During porting uath(4) to usb2 I found the following code failed to > > > run: > > > > > > data = open("/dev/usb/0.2.2", O_WRONLY, 0); > > > timeout = UATH_DATA_TIMEOUT; > > > if (ioctl(data, USB_SET_TIMEOUT, &timeout) < 0) > > > err(-1, "%s: USB_SET_TIMEOUT(%u)", datadev, > > > UATH_DATA_TIMEOUT); > > > > > > and the error was: > > > > > > uathload: /dev/usb/0.2.2: USB_SET_TIMEOUT(1000): Invalid > > > argument > > > > Use the following macro instead: > > > > #define USB_SET_TX_TIMEOUT _IOW ('U', 137, int) > > > > There also is a match for USB_SET_RX_TIMEOUT . > > > > USB_SET_TIMEOUT has been removed. > > > > Also don't forget to include "usb_ioctl.h" . > > > > Another idea: > > > > Port the program to libusb .... > > > > > It looks it's ok with calling ioctl(msg, USB_SET_TIMEOUT, ..) to > > > /dev/usb/0.2.1 > > > > > > And the behaviour of program isn't likely with usb1 that it worked well > > > in usb1. After writing some data into msg and data pipe there was no > > > any response using read(2). The problem source can be found at:. > > > > > > http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/weo > > >ngyo /wireless/src/usr.sbin/uathload&HIDEDEL=NO > > > > > > Are there something I missed in here? > > > > See hints above. > > Thank you for advise. :-) I've solve `Invalid argument' error. However > the program looks it still doesn't work. All functions the problem used > are open(2), ioctl(2), read(2) and write(2). I think I can try to use > libusb but it'd be better if it works again using the above 4 system > calls. > > Is it supported in CURRENT or is it a one of regression? > > regards, > Weongyo Jeong What other IOCTL's are used? Can you make a debug trace: sysctl hw.usb2.ugen.debug=15 sysctl hw.usb2.dev.debug=15 ? --HPS From avg at icyb.net.ua Wed Mar 18 09:08:29 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Wed Mar 18 09:08:36 2009 Subject: usb keyboard dying at loader prompt In-Reply-To: <493D37DB.6030902@icyb.net.ua> References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> <492FF127.807@icyb.net.ua> <20081128134802.GA75900@onelab2.iet.unipi.it> <493D37DB.6030902@icyb.net.ua> Message-ID: <49C116EB.7020409@icyb.net.ua> I would like to report that I am no longer seeing the issue in the subject line. The problem was fixed by the recent commits of jhb ( I tested stable/7). -- Andriy Gapon From jhs at berklix.org Wed Mar 18 12:31:41 2009 From: jhs at berklix.org (Julian Stacey) Date: Wed Mar 18 12:31:49 2009 Subject: Belkin Cardbus USB2 adaptors too hot. Message-ID: <200903181907.n2IJ7k1D042835@fire.js.berklix.net> Hi, Anyone else noticed Belkin Cardbus USB2 adaptors run extremely hot ? I've been having weird things happen umass errs, g_vfs_done()da0a[WRITE(offset=...., length=131072)]error = 5 first errors after a 66G write, subsequent errors after just 1G more, (in retrospect when truly hot) I've built a break out box to check Voltages & Current delivered into external USB2 to IDE enclosures, just bought another new 250G IDE for another enclosure, lots of enclosures & usb2 hub power blocks tried, then I remembered this card used to run hot on FreeBSD-6, in this Toshiba Satellite S5100-603, & I think BSD + this laptop cooked my brothers identical Belkin card too last year. The laptop BTW: http://www.berklix.com/~jhs/hardware/toshiba/satellite.s5100-603/ So 2 things: FreeBSD-7.1-RELEASE is still cooking by default. I recall cardbus can run at 2 different voltages ? Well we need to change something to detect that. Anyone want to throw me an RTFM URL start point for reading ? (Sorry to ask here & not read first, trying to catch a boat ASAP). Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org From imp at bsdimp.com Wed Mar 18 12:58:15 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Mar 18 12:58:22 2009 Subject: Belkin Cardbus USB2 adaptors too hot. In-Reply-To: <200903181907.n2IJ7k1D042835@fire.js.berklix.net> References: <200903181907.n2IJ7k1D042835@fire.js.berklix.net> Message-ID: <20090318.135729.1159138617.imp@bsdimp.com> In message: <200903181907.n2IJ7k1D042835@fire.js.berklix.net> "Julian Stacey" writes: : Hi, : Anyone else noticed Belkin Cardbus USB2 adaptors run extremely hot ? : I've been having weird things happen : umass errs, g_vfs_done()da0a[WRITE(offset=...., : length=131072)]error = 5 first errors after a 66G write, : subsequent errors after just 1G more, (in retrospect when : truly hot) : I've built a break out box to check Voltages & Current : delivered into external USB2 to IDE enclosures, : just bought another new 250G IDE for another enclosure, : lots of enclosures & usb2 hub power blocks tried, then I : remembered this card used to run hot on FreeBSD-6, in this : Toshiba Satellite S5100-603, & I think BSD + this laptop : cooked my brothers identical Belkin card too last year. : The laptop BTW: : http://www.berklix.com/~jhs/hardware/toshiba/satellite.s5100-603/ : So 2 things: : FreeBSD-7.1-RELEASE is still cooking by default. : I recall cardbus can run at 2 different voltages ? : Well we need to change something to detect that. : Anyone want to throw me an RTFM URL start point for reading ? : (Sorry to ask here & not read first, trying to catch a boat ASAP). Cardbus runs at 3.3V only. There's X.X and Y.Y low-voltage specs, but nobody seems to implement them. PC Card (the 16-bit version) runs at 3.3V or 5.0V. The usual reason for cards running really hot is too much current draw over the bus for supplied devices. Many of the cards have an external power supply that can be used to provide more power over a path that is made for it rather than exceeding the CardBus specs to pull the power in over that power bus. Don't know if this card has that or not... Warner From torfinn.ingolfsen at broadpark.no Wed Mar 18 12:59:11 2009 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Wed Mar 18 12:59:43 2009 Subject: Xorg 7.4 and umass devices - a bad combination? In-Reply-To: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> References: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> Message-ID: <20090318205909.07625cdb.torfinn.ingolfsen@broadpark.no> Hello, More testing. - I verified that listing the firewire drive while Xorg is running doesn't seeem to cause any errors. So I thought: what happens if I start Xorg (using startx), then exit it and _then_ do an 'ls' on the usb drives? First try: 'startx', do a couple of commands (like 'date', 'pwd'), the exit Xorg again. Then do 'ls' on the usb drives. Result: it works without errors. Second try: 'startx', do a couple of commands (like 'date', 'pwd'), the exit Xorg again. Then do 'ls' on the usb drives. Result: the erors are back. -- Regards, Torfinn Ingolfsen From torfinn.ingolfsen at broadpark.no Wed Mar 18 13:01:55 2009 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Wed Mar 18 13:02:01 2009 Subject: Xorg 7.4 and umass devices - a bad combination? In-Reply-To: <20090318205909.07625cdb.torfinn.ingolfsen@broadpark.no> References: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> <20090318205909.07625cdb.torfinn.ingolfsen@broadpark.no> Message-ID: <20090318210153.188e35db.torfinn.ingolfsen@broadpark.no> On Wed, 18 Mar 2009 20:59:09 +0100 Torfinn Ingolfsen wrote: > More testing. Also, drm uses irq 18. AFAICT, this doesn't conflict with anything else: Mar 18 20:49:45 kg-quiet kernel: drm0: port 0xef00-0xefff mem 0xd8000000-0xdfffffff,0xfdef0000-0xfdefffff irq 18 at device 0.0 on pci1 Mar 18 20:49:45 kg-quiet kernel: info: [drm] Initialized radeon 1.25.0 20060524 Mar 18 20:49:46 kg-quiet kernel: info: [drm] Setting GART location based on new memory map Mar 18 20:49:46 kg-quiet kernel: info: [drm] Loading R300 Microcode Mar 18 20:49:46 kg-quiet kernel: info: [drm] writeback test succeeded in 1 usecs -- Torfinn From mike at sentex.net Wed Mar 18 13:15:54 2009 From: mike at sentex.net (Mike Tancsa) Date: Wed Mar 18 13:16:01 2009 Subject: openct port and USB2 Message-ID: <200903182015.n2IKFWIb011457@lava.sentex.ca> Hi, I was trying to see if OpenCT and OpenSC work under the new USB regime, but openCT doesnt compile now. Are there any tricks to get it to compile and or work ? . . . mv -f .deps/libifd_la-sys-sunray.Tpo .deps/libifd_la-sys-sunray.Plo /bin/sh ../../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -MT libifd_la-sys-solaris.lo -MD -MP -MF .deps/libifd_la-sys-solaris.Tpo -c -o libifd_la-sys-solaris.lo `test -f 'sys-solaris.c' || echo './'`sys-solaris.c cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -MT libifd_la-sys-solaris.lo -MD -MP -MF .deps/libifd_la-sys-solaris.Tpo -c sys-solaris.c -fPIC -DPIC -o .libs/libifd_la-sys-solaris.o cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -MT libifd_la-sys-solaris.lo -MD -MP -MF .deps/libifd_la-sys-solaris.Tpo -c sys-solaris.c -o libifd_la-sys-solaris.o >/dev/null 2>&1 mv -f .deps/libifd_la-sys-solaris.Tpo .deps/libifd_la-sys-solaris.Plo /bin/sh ../../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -MT libifd_la-sys-bsd.lo -MD -MP -MF .deps/libifd_la-sys-bsd.Tpo -c -o libifd_la-sys-bsd.lo `test -f 'sys-bsd.c' || echo './'`sys-bsd.c cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -MT libifd_la-sys-bsd.lo -MD -MP -MF .deps/libifd_la-sys-bsd.Tpo -c sys-bsd.c -fPIC -DPIC -o .libs/libifd_la-sys-bsd.o sys-bsd.c: In function 'ifd_sysdep_usb_bulk': sys-bsd.c:113: error: 'USB_SET_SHORT_XFER' undeclared (first use in this function) sys-bsd.c:113: error: (Each undeclared identifier is reported only once sys-bsd.c:113: error: for each function it appears in.) sys-bsd.c: In function 'ifd_sysdep_usb_control': sys-bsd.c:243: error: storage size of 'ctrl' isn't known sys-bsd.c:256: error: 'USBD_SHORT_XFER_OK' undeclared (first use in this function) sys-bsd.c:265: error: 'USB_SET_TIMEOUT' undeclared (first use in this function) sys-bsd.c:272: error: 'USB_DO_REQUEST' undeclared (first use in this function) sys-bsd.c: In function 'ifd_sysdep_usb_set_configuration': sys-bsd.c:291: error: 'USB_SET_CONFIG' undeclared (first use in this function) sys-bsd.c: In function 'ifd_sysdep_usb_set_interface': sys-bsd.c:312: error: 'USB_SET_ALTINTERFACE' undeclared (first use in this function) sys-bsd.c: In function 'ifd_scan_usb': sys-bsd.c:378: error: 'USB_MAX_DEVICES' undeclared (first use in this function) sys-bsd.c:379: error: storage size of 'device_info' isn't known sys-bsd.c:386: error: 'USB_DEVICEINFO' undeclared (first use in this function) gmake[3]: *** [libifd_la-sys-bsd.lo] Error 1 gmake[3]: Leaving directory `/usr/ports/security/openct/work/openct-0.6.15/src/ifd' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/security/openct/work/openct-0.6.15/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/security/openct/work/openct-0.6.15' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/security/openct. *** Error code 1 Stop in /usr/ports/security/openct. 1[i7]# ---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 hselasky at c2i.net Wed Mar 18 14:09:04 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 18 14:09:11 2009 Subject: openct port and USB2 In-Reply-To: <200903182015.n2IKFWIb011457@lava.sentex.ca> References: <200903182015.n2IKFWIb011457@lava.sentex.ca> Message-ID: <200903182211.30046.hselasky@c2i.net> On Wednesday 18 March 2009, Mike Tancsa wrote: > Hi, > I was trying to see if OpenCT and OpenSC work under the new > USB regime, but openCT doesnt compile now. Are there any tricks to > get it to compile and or work ? > > . > . > . > mv -f .deps/libifd_la-sys-sunray.Tpo .deps/libifd_la-sys-sunray.Plo > /bin/sh ../../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H > -I. -I../.. -I../../src/include > -I../../src/include -I/usr/local/include -O2 -pipe > -fno-strict-aliasing -MT libifd_la-sys-solaris.lo -MD -MP -MF > .deps/libifd_la-sys-solaris.Tpo -c -o libifd_la-sys-solaris.lo `test > -f 'sys-solaris.c' || echo './'`sys-solaris.c > cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include > -I../../src/include -I/usr/local/include -O2 -pipe > -fno-strict-aliasing -MT libifd_la-sys-solaris.lo -MD -MP -MF > .deps/libifd_la-sys-solaris.Tpo -c sys-solaris.c -fPIC -DPIC -o > .libs/libifd_la-sys-solaris.o > cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include > -I../../src/include -I/usr/local/include -O2 -pipe > -fno-strict-aliasing -MT libifd_la-sys-solaris.lo -MD -MP -MF > .deps/libifd_la-sys-solaris.Tpo -c sys-solaris.c -o > libifd_la-sys-solaris.o >/dev/null 2>&1 > mv -f .deps/libifd_la-sys-solaris.Tpo .deps/libifd_la-sys-solaris.Plo > /bin/sh ../../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H > -I. -I../.. -I../../src/include > -I../../src/include -I/usr/local/include -O2 -pipe > -fno-strict-aliasing -MT libifd_la-sys-bsd.lo -MD -MP -MF > .deps/libifd_la-sys-bsd.Tpo -c -o libifd_la-sys-bsd.lo `test -f > 'sys-bsd.c' || echo './'`sys-bsd.c > cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include > -I../../src/include -I/usr/local/include -O2 -pipe > -fno-strict-aliasing -MT libifd_la-sys-bsd.lo -MD -MP -MF > .deps/libifd_la-sys-bsd.Tpo -c sys-bsd.c -fPIC -DPIC -o > .libs/libifd_la-sys-bsd.o > sys-bsd.c: In function 'ifd_sysdep_usb_bulk': > sys-bsd.c:113: error: 'USB_SET_SHORT_XFER' undeclared (first use in > this function) > sys-bsd.c:113: error: (Each undeclared identifier is reported only once > sys-bsd.c:113: error: for each function it appears in.) > sys-bsd.c: In function 'ifd_sysdep_usb_control': > sys-bsd.c:243: error: storage size of 'ctrl' isn't known > sys-bsd.c:256: error: 'USBD_SHORT_XFER_OK' undeclared (first use in > this function) > sys-bsd.c:265: error: 'USB_SET_TIMEOUT' undeclared (first use in this > function) sys-bsd.c:272: error: 'USB_DO_REQUEST' undeclared (first use in > this function) sys-bsd.c: In function 'ifd_sysdep_usb_set_configuration': > sys-bsd.c:291: error: 'USB_SET_CONFIG' undeclared (first use in this > function) sys-bsd.c: In function 'ifd_sysdep_usb_set_interface': > sys-bsd.c:312: error: 'USB_SET_ALTINTERFACE' undeclared (first use in > this function) > sys-bsd.c: In function 'ifd_scan_usb': > sys-bsd.c:378: error: 'USB_MAX_DEVICES' undeclared (first use in this > function) sys-bsd.c:379: error: storage size of 'device_info' isn't known > sys-bsd.c:386: error: 'USB_DEVICEINFO' undeclared (first use in this > function) gmake[3]: *** [libifd_la-sys-bsd.lo] Error 1 > gmake[3]: Leaving directory > `/usr/ports/security/openct/work/openct-0.6.15/src/ifd' > gmake[2]: *** [all-recursive] Error 1 > gmake[2]: Leaving directory > `/usr/ports/security/openct/work/openct-0.6.15/src' gmake[1]: *** > [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/security/openct/work/openct-0.6.15' > gmake: *** [all] Error 2 > *** Error code 2 > > Stop in /usr/ports/security/openct. > *** Error code 1 > > Stop in /usr/ports/security/openct. > 1[i7]# > > ---Mike > You need to check in the sources if there is a libusb-based backend which you can use! Else the old way is still supported, but ioctl numbers have changed. See /usr/include/dev/usb/usb_ioctl.h --HPS From thompsa at FreeBSD.org Wed Mar 18 14:40:33 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Wed Mar 18 14:40:39 2009 Subject: openct port and USB2 In-Reply-To: <200903182015.n2IKFWIb011457@lava.sentex.ca> References: <200903182015.n2IKFWIb011457@lava.sentex.ca> Message-ID: <20090318214025.GB79077@citylink.fud.org.nz> On Wed, Mar 18, 2009 at 04:15:46PM -0400, Mike Tancsa wrote: > Hi, > I was trying to see if OpenCT and OpenSC work under the new USB > regime, but openCT doesnt compile now. Are there any tricks to get it to > compile and or work ? > Can you try this patch. http://people.freebsd.org/~thompsa/openct.diff Andrew From thompsa at FreeBSD.org Wed Mar 18 16:48:24 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Wed Mar 18 16:48:30 2009 Subject: uscanner & sane Message-ID: <20090318234818.GD79077@citylink.fud.org.nz> Hi, I am looking into fixing sane-backends and see that the uscanner driver is not needed at all. I wonder if we should follow Linux on this and remove it in favour of libusb? uscanner is just a simple wrapper around a fifo anyway, it has no logic. Andrew From mike at sentex.net Wed Mar 18 17:04:55 2009 From: mike at sentex.net (Mike Tancsa) Date: Wed Mar 18 17:05:02 2009 Subject: openct port and USB2 In-Reply-To: <20090318214025.GB79077@citylink.fud.org.nz> References: <200903182015.n2IKFWIb011457@lava.sentex.ca> <20090318214025.GB79077@citylink.fud.org.nz> Message-ID: <200903190004.n2J04YjP012665@lava.sentex.ca> At 05:40 PM 3/18/2009, Andrew Thompson wrote: >On Wed, Mar 18, 2009 at 04:15:46PM -0400, Mike Tancsa wrote: > > Hi, > > I was trying to see if OpenCT and OpenSC work under the new USB > > regime, but openCT doesnt compile now. Are there any tricks to get it to > > compile and or work ? > > > >Can you try this patch. > >http://people.freebsd.org/~thompsa/openct.diff > Thanks! It does build now. However, not all of the bits seem to be working just yet 1[i7]# opensc-tool -l [opensc-tool] reader-pcsc.c:996:pcsc_detect_readers: returning with: No readers found No smart card readers found. 0[i7]# ps -auxww | grep if root 64638 0.0 0.1 3328 1640 ?? Ss 7:57PM 0:00.00 /usr/local/sbin/ifdhandler -H etoken64 usb (null)/usb//dev/usb//dev/ugen1.2 root 64653 0.0 0.1 3440 1616 2 R+ 7:59PM 0:00.00 grep if 0[i7]# 0[i7]# 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 ugen4.1: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen5.1: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen6.1: at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen7.1: at usbus7, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen6.2: at usbus6, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen1.2: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.2: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON 0[i7]# ---Mike From thompsa at FreeBSD.org Wed Mar 18 17:30:06 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Wed Mar 18 17:30:13 2009 Subject: openct port and USB2 In-Reply-To: <200903190004.n2J04YjP012665@lava.sentex.ca> References: <200903182015.n2IKFWIb011457@lava.sentex.ca> <20090318214025.GB79077@citylink.fud.org.nz> <200903190004.n2J04YjP012665@lava.sentex.ca> Message-ID: <20090319003001.GE79077@citylink.fud.org.nz> On Wed, Mar 18, 2009 at 08:04:48PM -0400, Mike Tancsa wrote: > At 05:40 PM 3/18/2009, Andrew Thompson wrote: >> On Wed, Mar 18, 2009 at 04:15:46PM -0400, Mike Tancsa wrote: >> > Hi, >> > I was trying to see if OpenCT and OpenSC work under the new USB >> > regime, but openCT doesnt compile now. Are there any tricks to get it to >> > compile and or work ? >> > >> >> Can you try this patch. >> >> http://people.freebsd.org/~thompsa/openct.diff >> > > Thanks! It does build now. However, not all of the bits seem to be > working just yet Thats odd, its working for me. > 1[i7]# opensc-tool -l > [opensc-tool] reader-pcsc.c:996:pcsc_detect_readers: returning with: No > readers found > No smart card readers found. % opensc-tool -l Readers known about: Nr. Driver Name 0 openct Aladdin eToken PRO 1 openct Aladdin eToken PRO 64k > 0[i7]# ps -auxww | grep if > root 64638 0.0 0.1 3328 1640 ?? Ss 7:57PM 0:00.00 > /usr/local/sbin/ifdhandler -H etoken64 usb (null)/usb//dev/usb//dev/ugen1.2 root 4433 0.0 0.1 3352 1548 ?? Ss 5:22PM 0:00.01 /usr/local/sbin/ifdhandler -H etoken usb (null)/usb//dev/usb//dev/ugen1.3 root 4435 0.0 0.1 3352 1548 ?? Ss 5:22PM 0:00.01 /usr/local/sbin/ifdhandler -H etoken64 usb (null)/usb//dev/usb//dev/ugen1.2 Does 'ldd /usr/local/sbin/ifdhandler' show it linked to /usr/lib/libusb.so.1 ? Andrew From mike at sentex.net Wed Mar 18 17:47:07 2009 From: mike at sentex.net (Mike Tancsa) Date: Wed Mar 18 17:47:14 2009 Subject: openct port and USB2 In-Reply-To: <20090319003001.GE79077@citylink.fud.org.nz> References: <200903182015.n2IKFWIb011457@lava.sentex.ca> <20090318214025.GB79077@citylink.fud.org.nz> <200903190004.n2J04YjP012665@lava.sentex.ca> <20090319003001.GE79077@citylink.fud.org.nz> Message-ID: <200903190046.n2J0kk0x012885@lava.sentex.ca> At 08:30 PM 3/18/2009, Andrew Thompson wrote: >On Wed, Mar 18, 2009 at 08:04:48PM -0400, Mike Tancsa wrote: > > At 05:40 PM 3/18/2009, Andrew Thompson wrote: > >> On Wed, Mar 18, 2009 at 04:15:46PM -0400, Mike Tancsa wrote: > >> > Hi, > >> > I was trying to see if OpenCT and OpenSC work under the new USB > >> > regime, but openCT doesnt compile now. Are there any tricks > to get it to > >> > compile and or work ? > >> > > >> > >> Can you try this patch. > >> > >> http://people.freebsd.org/~thompsa/openct.diff > >> > > > > Thanks! It does build now. However, not all of the bits seem to be > > working just yet > >Thats odd, its working for me. > > > 1[i7]# opensc-tool -l > > [opensc-tool] reader-pcsc.c:996:pcsc_detect_readers: returning with: No > > readers found > > No smart card readers found. > >% opensc-tool -l >Readers known about: >Nr. Driver Name >0 openct Aladdin eToken PRO >1 openct Aladdin eToken PRO 64k > > > 0[i7]# ps -auxww | grep if > > root 64638 0.0 0.1 3328 1640 ?? Ss 7:57PM 0:00.00 > > /usr/local/sbin/ifdhandler -H etoken64 usb (null)/usb//dev/usb//dev/ugen1.2 > >root 4433 0.0 0.1 3352 1548 ?? Ss 5:22PM 0:00.01 >/usr/local/sbin/ifdhandler -H etoken usb >(null)/usb//dev/usb//dev/ugen1.3 >root 4435 0.0 0.1 3352 1548 ?? Ss 5:22PM 0:00.01 >/usr/local/sbin/ifdhandler -H etoken64 usb >(null)/usb//dev/usb//dev/ugen1.2 > >Does 'ldd /usr/local/sbin/ifdhandler' show it linked to >/usr/lib/libusb.so.1 ? Hi, 0[i7]# ldd /usr/local/sbin/ifdhandler /usr/local/sbin/ifdhandler: libopenct.so.1 => /usr/local/lib/libopenct.so.1 (0x280b0000) libltdl.so.4 => /usr/local/lib/libltdl.so.4 (0x280b7000) libusb.so.1 => /usr/lib/libusb.so.1 (0x280be000) libc.so.7 => /lib/libc.so.7 (0x280c7000) 0[i7]# Actually, I just did a full make deinstall and full re-install of opensc, and it seems to periodically work 0[i7]# opensc-tool -l [opensc-tool] reader-pcsc.c:996:pcsc_detect_readers: returning with: No readers found Readers known about: Nr. Driver Name 0 openct Aladdin eToken PRO 64k 1 openct OpenCT reader (detached) 0[i7]# opensc-tool -l [opensc-tool] reader-pcsc.c:996:pcsc_detect_readers: returning with: No readers found Readers known about: Nr. Driver Name 0 openct Aladdin eToken PRO 64k 1 openct OpenCT reader (detached) 0[i7]# cardos-info Running cardos-tool --info [cardos-tool] reader-pcsc.c:996:pcsc_detect_readers: returning with: No readers found Using reader with a card: Aladdin eToken PRO 64k 3b:f2:18:00:02:c1:0a:31:fe:58:c8:09:75 Info : CardOS V4.2B (C) Siemens AG 1994-2005 Chip type: 124 Serial number: 28 59 e2 19 37 20 Full prom dump: 33 66 00 22 9A 9A 9A 9A 7C FF 28 59 E2 19 37 20 3f."....|.(Y..7 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 ................ OS Version: 200.9 (that's CardOS M4.2B) Current life cycle: 32 (administration) Security Status of current DF: Free memory : 1024 ATR Status: 0x0 ROM-ATR [cardos-tool] reader-openct.c:324:openct_reader_transmit: unable to transmit [cardos-tool] apdu.c:394:do_single_transmit: unable to transmit APDU APDU transmit failed: Generic reader error 1[i7]# cardos-info Running cardos-tool --info [cardos-tool] reader-pcsc.c:996:pcsc_detect_readers: returning with: No readers found Using reader with a card: Aladdin eToken PRO 64k 3b:f2:18:00:02:c1:0a:31:fe:58:c8:09:75 [cardos-tool] reader-openct.c:324:openct_reader_transmit: unable to transmit [cardos-tool] apdu.c:394:do_single_transmit: unable to transmit APDU APDU transmit failed: Generic reader error 1[i7]# ---Mike ---Mike From wblock at wonkity.com Wed Mar 18 18:24:05 2009 From: wblock at wonkity.com (Warren Block) Date: Wed Mar 18 18:24:15 2009 Subject: uscanner & sane In-Reply-To: <20090318234818.GD79077@citylink.fud.org.nz> References: <20090318234818.GD79077@citylink.fud.org.nz> Message-ID: On Wed, 18 Mar 2009, Andrew Thompson wrote: > I am looking into fixing sane-backends and see that the uscanner driver > is not needed at all. I wonder if we should follow Linux on this and > remove it in favour of libusb? uscanner is just a simple wrapper around > a fifo anyway, it has no logic. libusb also allows the detection of scanner button presses which don't make it through uscanner. Having said that, for some reason I can't recall I switched back to uscanner. -Warren Block * Rapid City, South Dakota USA From weongyo.jeong at gmail.com Wed Mar 18 19:11:37 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Wed Mar 18 19:11:49 2009 Subject: q: USB_SET_TIMEOUT in ugen. In-Reply-To: <200903181454.18859.hselasky@c2i.net> References: <20090318073032.GA12632@weongyo.cdnetworks.kr> <200903180852.48034.hselasky@c2i.net> <20090318114642.GB12632@weongyo.cdnetworks.kr> <200903181454.18859.hselasky@c2i.net> Message-ID: <20090319021128.GC12632@weongyo.cdnetworks.kr> On Wed, Mar 18, 2009 at 02:54:17PM +0100, Hans Petter Selasky wrote: > On Wednesday 18 March 2009, Weongyo Jeong wrote: > > On Wed, Mar 18, 2009 at 08:52:47AM +0100, Hans Petter Selasky wrote: > > > Hi, > > > > > > On Wednesday 18 March 2009, Weongyo Jeong wrote: > > > > Hello, > > > > > > > > During porting uath(4) to usb2 I found the following code failed to > > > > run: > > > > > > > > data = open("/dev/usb/0.2.2", O_WRONLY, 0); > > > > timeout = UATH_DATA_TIMEOUT; > > > > if (ioctl(data, USB_SET_TIMEOUT, &timeout) < 0) > > > > err(-1, "%s: USB_SET_TIMEOUT(%u)", datadev, > > > > UATH_DATA_TIMEOUT); > > > > > > > > and the error was: > > > > > > > > uathload: /dev/usb/0.2.2: USB_SET_TIMEOUT(1000): Invalid > > > > argument > > > > > > Use the following macro instead: > > > > > > #define USB_SET_TX_TIMEOUT _IOW ('U', 137, int) > > > > > > There also is a match for USB_SET_RX_TIMEOUT . > > > > > > USB_SET_TIMEOUT has been removed. > > > > > > Also don't forget to include "usb_ioctl.h" . > > > > > > Another idea: > > > > > > Port the program to libusb .... > > > > > > > It looks it's ok with calling ioctl(msg, USB_SET_TIMEOUT, ..) to > > > > /dev/usb/0.2.1 > > > > > > > > And the behaviour of program isn't likely with usb1 that it worked well > > > > in usb1. After writing some data into msg and data pipe there was no > > > > any response using read(2). The problem source can be found at:. > > > > > > > > http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/weo > > > >ngyo /wireless/src/usr.sbin/uathload&HIDEDEL=NO > > > > > > > > Are there something I missed in here? > > > > > > See hints above. > > > > Thank you for advise. :-) I've solve `Invalid argument' error. However > > the program looks it still doesn't work. All functions the problem used > > are open(2), ioctl(2), read(2) and write(2). I think I can try to use > > libusb but it'd be better if it works again using the above 4 system > > calls. > > > > Is it supported in CURRENT or is it a one of regression? > > > > regards, > > Weongyo Jeong > > What other IOCTL's are used? > > Can you make a debug trace: > > sysctl hw.usb2.ugen.debug=15 > sysctl hw.usb2.dev.debug=15 > > ? It's a simple program so only USB_SET_RX_TIMEOUT and USB_SET_TX_TIMEOUT are set via ioctl(2). And the result is as follows: [root@kkk /usr/p4/w/usr.sbin/uathload]# ./uathload -d /dev/ugen0.2 -v usb2_open:823: fflags=0x00000003 usb2_ref_device:165: usb2_ref_device, cpd=0xc8374bc0 need uref=1 usb2_ref_device:243: ref udev - needed usb2_fifo_create:409: Endpoint device, searching for 0x01 usb2_fifo_create:480: dev_get_pipe(1, 0x0) usb2_fifo_create:507: dev_get_pipe(1, 0x1) usb2_fifo_create:536: fifo index = 0 ugen_open:158: flag=0x1 ugen_open:158: flag=0x2 usb2_ref_device:165: usb2_ref_device, cpd=0xc8374bc0 need uref=0 usb2_ref_device:235: ref write usb2_ref_device:239: ref read usb2_ioctl:1021: fflags=3, cmd=0x80045572 ugen_ioctl:1388: cmd=0x80045572 ugen_ioctl:1566: error=-3 usb2_uref_location:297: ref udev ugen_ioctl_post:1963: cmd=0x80045572 ugen_ioctl_post:2164: error=0 usb2_open:823: fflags=0x00000002 usb2_ref_device:165: usb2_ref_device, cpd=0xc8374740 need uref=1 usb2_ref_device:243: ref udev - needed usb2_fifo_create:409: Endpoint device, searching for 0x02 usb2_fifo_create:480: dev_get_pipe(2, 0x0) usb2_fifo_create:536: fifo index = 2 ugen_open:158: flag=0x2 usb2_ref_device:165: usb2_ref_device, cpd=0xc8374740 need uref=0 usb2_ref_device:235: ref write usb2_ioctl:1021: fflags=2, cmd=0x80045589 ugen_ioctl:1388: cmd=0x80045589 ugen_ioctl:1566: error=-3 usb2_uref_location:297: ref udev ugen_ioctl_post:1963: cmd=0x80045589 ugen_ioctl_post:2164: error=0 Load firmware aru5523.bin (builtisn) to /dev/ugen0b.2 send block 20: 147368 bytes _remainingwrite:1291: usb2_ref_device:165: usb2_ref_device, cpd=0xc8374bc0 need uref=0 usb2_ref_device:235: ref write usb2_ref_device:239: ref read usb2_write:1362: transfer 512 bytes to 0xc8382038 ugen_default_write_callback:434: actlen=0, aframes=0 ugen_default_write_callback:434: actlen=0, aframes=0 ugen_default_write_callback:434: actlen=512, aframes=1 u : dsata...b2_write:1291: usb2_ref_device:165: usb2_ref_device, cpd=0xc8374740 need uref=0 usb2_ref_device:235: ref write usb2_write:1362: transfer 2048 bytes to 0xc839c038 ugen_default_write_callback:434: actlen=0, aframes=0 ugen_default_write_callback:434: actlen=0, aframes=0 ugen_default_write_callback:434: actlen=2048, aframes=1 u : wsait for ack...b2_ref_device:165: usb2_ref_device, cpd=0xc8374bc0 need uref=0 usb2_ref_device:235: ref write usb2_ref_device:239: ref read usb2_read:1222: sleeping ugen_default_read_callback:384: actlen=0, aframes=0 ugen_default_read_callback:384: actlen=0, aframes=0 ugen_read_clear_stall_callback:477: f=0xc4d5b000: stall cleared [...again...] ugen_default_read_callback:384: actlen=0, aframes=0 ugen_default_read_callback:384: actlen=0, aframes=0 ugen_read_clear_stall_callback:477: f=0xc4d5b000: stall cleared [...again...] ugen_default_read_callback:384: actlen=0, aframes=0 ugen_default_read_callback:384: actlen=0, aframes=0 ugen_read_clear_stall_callback:477: f=0xc4d5b000: stall cleared [...again...] [...again...] [...again...] [...after CTRL-C...] ^Cusb2_close:889: cpd=0xc8374bc0 usb2_ref_device:165: usb2_ref_device, cpd=0xc8374bc0 need uref=1 usb2_ref_device:235: ref write usb2_ref_device:239: ref read usb2_ref_device:243: ref udev - needed usb2_fifo_close:803: Sleeping at close! ugen_closugen_default_read_callback:384: actlen=0, aframes=0 e:188: flag=0x1 ugen_close:202: no FIFOs usb2_fifo_close:810: closed ugen_default_write_callback:434: actlen=512, aframes=1 ugen_close:188: flag=0x2 ugen_close:202: no FIFOs usb2_fifo_close:810: closed usb2_close:889: cpd=0xc8374740 usb2_ref_device:165: usb2_ref_device, cpd=0xc8374740 need uref=1 usb2_ref_device:235: ref write usb2_ref_device:243: ref udev - needed ugen_default_write_callback:434: actlen=2048, aframes=1 ugen_close:188: flag=0x2 ugen_close:202: no FIFOs usb2_fifo_close:810: closed regards, Weongyo Jeong From linimon at FreeBSD.org Wed Mar 18 19:11:42 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Mar 18 19:11:49 2009 Subject: usb/132785: [usb] [patch] Gemtech remote powersocket is classed as a HID device rather than ugen Message-ID: <200903190211.n2J2BftT036668@freefall.freebsd.org> Old Synopsis: Gemtech remote powersocket is classed as a HID device rather than ugen New Synopsis: [usb] [patch] Gemtech remote powersocket is classed as a HID device rather than ugen Responsible-Changed-From-To: freebsd-bugs->freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Thu Mar 19 02:11:24 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=132785 From ota at j.email.ne.jp Wed Mar 18 22:30:02 2009 From: ota at j.email.ne.jp (Yoshihiro Ota) Date: Wed Mar 18 22:30:08 2009 Subject: usb/132799: [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CACHE in its QUIRK Message-ID: <200903190528.n2J5SEG9010937@www.freebsd.org> >Number: 132799 >Category: usb >Synopsis: [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CACHE in its QUIRK >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Thu Mar 19 05:30:00 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Yoshihiro Ota >Release: 7.1-RELEASE 8-CURRENT >Organization: >Environment: %uname -a FreeBSD xxx 7.1-RELEASE-p3 FreeBSD 7.1-RELEASE-p3 #463 r188634M: Thu Mar 12 12:27:06 EDT 2009 xxx:/usr/obj/usr/src/sys/GENERIC i386 >Description: >How-To-Repeat: >Fix: The patch is verified on both 7.1-RELEASE and 8-CURRENT. Patch attached with submission follows: Index: umass.c =================================================================== RCS file: /home/ncvs/src/sys/dev/usb/Attic/umass.c,v retrieving revision 1.160.2.4.2.1 diff -u -r1.160.2.4.2.1 umass.c --- umass.c 25 Nov 2008 02:59:29 -0000 1.160.2.4.2.1 +++ umass.c 19 Mar 2009 05:18:51 -0000 @@ -415,6 +415,7 @@ { USB_VENDOR_GENESYS, USB_PRODUCT_GENESYS_GL641USB2IDE, RID_WILDCARD, UMASS_PROTO_SCSI | UMASS_PROTO_BBB, FORCE_SHORT_INQUIRY | NO_START_STOP | IGNORE_RESIDUE + | NO_SYNCHRONIZE_CACHE }, { USB_VENDOR_GENESYS, USB_PRODUCT_GENESYS_GL641USB2IDE_2, RID_WILDCARD, UMASS_PROTO_ATAPI | UMASS_PROTO_BBB, >Release-Note: >Audit-Trail: >Unformatted: From hselasky at c2i.net Thu Mar 19 00:58:55 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Mar 19 00:59:04 2009 Subject: q: USB_SET_TIMEOUT in ugen. In-Reply-To: <20090319021128.GC12632@weongyo.cdnetworks.kr> References: <20090318073032.GA12632@weongyo.cdnetworks.kr> <200903181454.18859.hselasky@c2i.net> <20090319021128.GC12632@weongyo.cdnetworks.kr> Message-ID: <200903190901.23844.hselasky@c2i.net> On Thursday 19 March 2009, Weongyo Jeong wrote: > ugen_default_read_callback:384: actlen=0, aframes=0 > ugen_default_read_callback:384: actlen=0, aframes=0 > ugen_read_clear_stall_callback:477: f=0xc4d5b000: stall cleared One difference from the old ugen implementation is that a stall error does not cause any error to be returned to userland! You could try to return a ZLP on errors. Try this patch: http://perforce.freebsd.org/chv.cgi?CH=159423 If you need to distinguish a ZLP from a STALL, then you have to use the new libusb! Ugen is not meant to be a replacement for libusb! --HPS From hselasky at c2i.net Thu Mar 19 01:08:29 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Mar 19 01:08:36 2009 Subject: usb/132785: [usb] [patch] Gemtech remote powersocket is classed as a HID device rather than ugen In-Reply-To: <200903190211.n2J2BftT036668@freefall.freebsd.org> References: <200903190211.n2J2BftT036668@freefall.freebsd.org> Message-ID: <200903190910.58461.hselasky@c2i.net> On Thursday 19 March 2009, linimon@freebsd.org wrote: > http://www.freebsd.org/cgi/query-pr.cgi?pr=132785 Does this patch also apply for FreeBSD 8-current? Hence on current both UGEN and UHID will appear. Does the device have HID descriptors? --HPS From jhs at berklix.org Thu Mar 19 03:13:28 2009 From: jhs at berklix.org (Julian Stacey) Date: Thu Mar 19 03:13:36 2009 Subject: Belkin Cardbus USB2 adaptors too hot. In-Reply-To: Your message "Wed, 18 Mar 2009 13:57:29 CST." <20090318.135729.1159138617.imp@bsdimp.com> Message-ID: <200903191013.n2JADT9T054996@fire.js.berklix.net> Hi Warner, cc usb@ Thanks for your reply :-) "M. Warner Losh" wrote: > "Julian Stacey" writes: > : Hi, > : Anyone else noticed Belkin Cardbus USB2 adaptors run extremely hot ? > : I've been having weird things happen > : umass errs, g_vfs_done()da0a[WRITE(offset=...., > : length=131072)]error = 5 first errors after a 66G write, > : subsequent errors after just 1G more, (in retrospect when > : truly hot) > : I've built a break out box to check Voltages & Current > : delivered into external USB2 to IDE enclosures, > : just bought another new 250G IDE for another enclosure, > : lots of enclosures & usb2 hub power blocks tried, then I > : remembered this card used to run hot on FreeBSD-6, in this > : Toshiba Satellite S5100-603, & I think BSD + this laptop > : cooked my brothers identical Belkin card too last year. > : The laptop BTW: > : http://www.berklix.com/~jhs/hardware/toshiba/satellite.s5100-603/ > : So 2 things: > : FreeBSD-7.1-RELEASE is still cooking by default. > : I recall cardbus can run at 2 different voltages ? > : Well we need to change something to detect that. > : Anyone want to throw me an RTFM URL start point for reading ? > : (Sorry to ask here & not read first, trying to catch a boat ASAP). > > Cardbus runs at 3.3V only. There's X.X and Y.Y low-voltage specs, but > nobody seems to implement them. PC Card (the 16-bit version) runs at > 3.3V or 5.0V. The usual reason for cards running really hot is too > much current draw over the bus for supplied devices. Many of the > cards have an external power supply that can be used to provide more > power over a path that is made for it rather than exceeding the > CardBus specs to pull the power in over that power bus. Don't know if > this card has that or not... I guess my Belkin Hi-Speed USB 2.0 Notebook Card is an earlier version of http://catalog.belkin.com/IWCatProductPage.process?Product_Id=123940 I've not found tech detail there though. It gets too warm when just plugged into laptop's cardbus, nothing external connected, (but not painfully hot as when pulled out after heavy use with no external power, connected to a powered hub driving an unpowered 2.5" disc. (But yes of course lots of stuff in a laptop to keep it hot. Belkin doesnt seem to get hot, sitting idle under XP But I dont know how to load Belkin to do disc intensive IO under XP. (more accurately I have not looked for eg GCC under XP to compile my http://berklix.com/~jhs/src/bsd/jhs/bin/public/testblock/ ) I wonder if XP turns off the card when not needed, & if that might be viable in BSD ?. Powerd: I was not running powerd until last few days. PC fan went on & off OK before & still does. Yes, this Belkin has a power socket, I hardly ever used it till now: Only ever used the Belkin via 1 or 2 powered hubs, which I assumed would buffer it + laptop from excess load. I had assumed laptop supplies the Belkin at a well regulated 5V, & I measured a few 5V supplies for hubs as { 5.36, 5.41 & 5.22 V }, (So unless disc pulled down hub voltage below 5.0, hub would not load down the Belkin, pulling extra current, but I suppose an over voltage is also potential unwanted heat (& at square law V^2 / R for heat), if hubs were to feeds back to Belkin at full V (but hubs would not, as discs pull hub V. down from eg 5.36 to 5.2. Both Belkin sockets deliver no voltage, unless Belkin is externaly powered. (& a memory stick requiring little current produces no /dev/da* so power supply from Belkin is not some OS related turn- on- if- something detected thing), but more simple: power must be supplied from { external socket or a device (in my case a powered hub). Current into 2 unpowered hubs, with no devs on hub: Powered Belkin alone, not in laptop PC: Hub=Slim: 0.01 A Hub=Zediworks: 0.19 A Belkin in PC: Unpowered Belkin: 0A Powered Belkin: Hub=Slim 0.16 A Hub=Zediworks: 0.29 A 7.1-RELEASE /var/log/messages : Belkin after insertion: cardbus0: Warning: CIS pointer 0 (no CIS present) cardbus0: Warning: Bogus CIS ignored cardbus0: at device 0.0 (no driver attached ) cardbus0: Warning: CIS pointer 0 (no CIS present) cardbus0: Warning: Bogus CIS ignored cardbus0: at device 0.1 (no driver attached ) cardbus0: Warning: CIS pointer 0 (no CIS present) cardbus0: Warning: Bogus CIS ignored ehci0: mem 0xfce05000-0xfce050ff irq 11 at device 0.2 on cardbus0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: wrong number of companions (2 != 0) usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 5 ports with 5 removable, self powered Hub=Slim uhub4: on uhub3 uhub4: single transaction translator uhub4: 4 ports with 4 removable, self powered Hub=Zediworks uhub4: on uhub3 uhub4: single transaction translator uhub4: 4 ports with 0 removable, self powered PS Ive tried a few runs since, with powered Belkin + powered hub, running my testblock.c to fill a UFS FS on various discs. It still runs too hot. Curiously at that point, I can still open more remote xterms on to the laptop, & run eg man etc, but the laptop just lets commands such as halt & reboot hang, presumably as kernel is waiting to talk to an overheated hanging USB system. Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org From weongyo.jeong at gmail.com Thu Mar 19 03:52:05 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Thu Mar 19 03:52:12 2009 Subject: q: USB_SET_TIMEOUT in ugen. In-Reply-To: <200903190901.23844.hselasky@c2i.net> References: <20090318073032.GA12632@weongyo.cdnetworks.kr> <200903181454.18859.hselasky@c2i.net> <20090319021128.GC12632@weongyo.cdnetworks.kr> <200903190901.23844.hselasky@c2i.net> Message-ID: <20090319105200.GA17221@weongyo.cdnetworks.kr> On Thu, Mar 19, 2009 at 09:01:23AM +0100, Hans Petter Selasky wrote: > On Thursday 19 March 2009, Weongyo Jeong wrote: > > ugen_default_read_callback:384: actlen=0, aframes=0 > > ugen_default_read_callback:384: actlen=0, aframes=0 > > ugen_read_clear_stall_callback:477: f=0xc4d5b000: stall cleared > > One difference from the old ugen implementation is that a stall error does not > cause any error to be returned to userland! > > You could try to return a ZLP on errors. Try this patch: > > http://perforce.freebsd.org/chv.cgi?CH=159423 > > If you need to distinguish a ZLP from a STALL, then you have to use the new > libusb! Ugen is not meant to be a replacement for libusb! Thanks you for a patch but it's not a answer what I want because my symptom is that recv(2) waits forever before or returns 0 after applying your patch. It shouldn't return 0 or nothing that the size of the recv(2) return value should be 512. I tried to dump USB transactions using USB analyzer and the dump file is available at: http://people.freebsd.org/~weongyo/uathload_20090319_export.txt Interesting packets could be found after 241 transactions and the steps of program are as follows: write(endpoint 0x1, buf, 512); write(endpoint 0x2, buf, 512); write(endpoint 0x2, buf, 512); write(endpoint 0x2, buf, 512); write(endpoint 0x2, buf, 512); read(endpoint 0x81, buf, 512); <-- here error. As you can see with looking the dump file, ugen couldn't catch the read event even though the USB stick responses data at Transaction 264, 265 and 266. It looks the problem is in ugen(4). As looking usb_generic.c it looks the read/write pipe are opened on the fly when read(2) or write(2) systemcalls are called though in the previous ugen(4) in usb1 all pipes are opened at open(2). Could this difference affect this symptom? I'd try to test another cases. regards, Weongyo Jeong From hselasky at c2i.net Thu Mar 19 06:29:57 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Mar 19 06:30:04 2009 Subject: q: USB_SET_TIMEOUT in ugen. In-Reply-To: <20090319105200.GA17221@weongyo.cdnetworks.kr> References: <20090318073032.GA12632@weongyo.cdnetworks.kr> <200903190901.23844.hselasky@c2i.net> <20090319105200.GA17221@weongyo.cdnetworks.kr> Message-ID: <200903191432.24364.hselasky@c2i.net> Hi, On Thursday 19 March 2009, Weongyo Jeong wrote: > On Thu, Mar 19, 2009 at 09:01:23AM +0100, Hans Petter Selasky wrote: > > On Thursday 19 March 2009, Weongyo Jeong wrote: > > > ugen_default_read_callback:384: actlen=0, aframes=0 > > > ugen_default_read_callback:384: actlen=0, aframes=0 > > > ugen_read_clear_stall_callback:477: f=0xc4d5b000: stall cleared > > > > One difference from the old ugen implementation is that a stall error > > does not cause any error to be returned to userland! > > > > You could try to return a ZLP on errors. Try this patch: > > > > http://perforce.freebsd.org/chv.cgi?CH=159423 > > > > If you need to distinguish a ZLP from a STALL, then you have to use the > > new libusb! Ugen is not meant to be a replacement for libusb! > > Thanks you for a patch but it's not a answer what I want because my > symptom is that recv(2) waits forever before or returns 0 after applying > your patch. It shouldn't return 0 or nothing that the size of the recv(2) > return value should be 512. The ugen interface is now double buffered, so it will read data in the background! The old was not double buffered. There are currently only two buffers. If you see the packet in the analyzer it has most likely also ended up in a UGEN buffer. > I tried to dump USB transactions using USB > analyzer and the dump file is available at: > > http://people.freebsd.org/~weongyo/uathload_20090319_export.txt What happens if you change: | if (read(msg, &rxmsg, sizeof(rxmsg)) != sizeof(rxmsg)) { 215: | VERBOSE("%s", "\n"); | err(-1, "error reading msg (%s)", msgdev); | break; | } Into while loop for sake of testing? So that if the length is 0 you loop one more time and if you have more than X zero lengths returned, you break? > > Interesting packets could be found after 241 transactions and the steps > of program are as follows: > > write(endpoint 0x1, buf, 512); > write(endpoint 0x2, buf, 512); > write(endpoint 0x2, buf, 512); > write(endpoint 0x2, buf, 512); > write(endpoint 0x2, buf, 512); > read(endpoint 0x81, buf, 512); <-- here error. > > As you can see with looking the dump file, ugen couldn't catch the read > event even though the USB stick responses data at Transaction 264, 265 > and 266. It looks the problem is in ugen(4). As looking usb_generic.c > it looks the read/write pipe are opened on the fly when read(2) or > write(2) systemcalls are called though in the previous ugen(4) in usb1 > all pipes are opened at open(2). Could this difference affect this > symptom? I'd try to test another cases. The old ugen would also do a clear-stall which the new one does not do, unless you do an IOCTL before the first read! That is also something you can try. --HPS From garga at FreeBSD.org Thu Mar 19 07:00:05 2009 From: garga at FreeBSD.org (Renato Botelho) Date: Thu Mar 19 07:00:16 2009 Subject: usb/132811: Patch: [newusb] Add Sun Type 7 keyboard id Message-ID: <20090319135753.8019.qmail@botelhor.bluepex.com> >Number: 132811 >Category: usb >Synopsis: Patch: [newusb] Add Sun Type 7 keyboard id >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Mar 19 14:00:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Renato Botelho >Release: FreeBSD 8.0-CURRENT i386 >Organization: BluePex Security Solutions >Environment: System: FreeBSD botelhor.bplab.local 8.0-CURRENT FreeBSD 8.0-CURRENT #58 r189892M: Thu Mar 19 10:26:41 BRT 2009 root@botelhor.bplab.local:/usr/obj/usr/src/sys/GARGA i386 >Description: Add Sun Type 7 keyboard id to usbdevs, working fine here: 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=FULL (12Mbps) pwr=ON ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen3.2: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen3.3: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.4: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.2 is the USB hub provvided by the keyboard, I didn't know how to describe this and where it's supposed to be added, but would be nice to have it added too >How-To-Repeat: >Fix: --- usbdevs.diff begins here --- Index: sys/dev/usb/usbdevs =================================================================== --- sys/dev/usb/usbdevs (revision 189892) +++ sys/dev/usb/usbdevs (working copy) @@ -2308,7 +2308,8 @@ product SUNTAC AS144L4 0x0011 SUNTAC U-Cable type A4 /* Sun Microsystems products */ -product SUN KEYBOARD 0x0005 Type 6 USB keyboard +product SUN KEYBOARD_TYPE_6 0x0005 Type 6 USB keyboard +product SUN KEYBOARD_TYPE_7 0x00a2 Type 7 USB keyboard /* XXX The above is a North American PC style keyboard possibly */ product SUN MOUSE 0x0100 Type 6 USB mouse --- usbdevs.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From garga at FreeBSD.org Thu Mar 19 10:18:02 2009 From: garga at FreeBSD.org (garga@FreeBSD.org) Date: Thu Mar 19 10:18:10 2009 Subject: usb/132811: Patch: [newusb] Add Sun Type 7 keyboard id Message-ID: <200903191718.n2JHI1vE050550@freefall.freebsd.org> Synopsis: Patch: [newusb] Add Sun Type 7 keyboard id State-Changed-From-To: open->closed State-Changed-By: garga State-Changed-When: Thu Mar 19 17:18:01 UTC 2009 State-Changed-Why: Committed. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=132811 From dfilter at FreeBSD.ORG Thu Mar 19 10:20:05 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Thu Mar 19 10:20:26 2009 Subject: usb/132811: commit references a PR Message-ID: <200903191720.n2JHK48C050671@freefall.freebsd.org> The following reply was made to PR usb/132811; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/132811: commit references a PR Date: Thu, 19 Mar 2009 17:16:48 +0000 (UTC) Author: garga (ports committer) Date: Thu Mar 19 17:16:33 2009 New Revision: 190089 URL: http://svn.freebsd.org/changeset/base/190089 Log: - Add Sun Type 7 keyboard - Rename Type 6 entry (following NetBSD) - Add Sun Type 7 Keyboard USB Hub PR: usb/132811 Reviewed by: thompsa Approved by: thompsa Modified: head/sys/dev/usb/usbdevs Modified: head/sys/dev/usb/usbdevs ============================================================================== --- head/sys/dev/usb/usbdevs Thu Mar 19 17:14:00 2009 (r190088) +++ head/sys/dev/usb/usbdevs Thu Mar 19 17:16:33 2009 (r190089) @@ -2310,9 +2310,11 @@ product SUNTAC AS64LX 0x000b SUNTAC U-C product SUNTAC AS144L4 0x0011 SUNTAC U-Cable type A4 /* Sun Microsystems products */ -product SUN KEYBOARD 0x0005 Type 6 USB keyboard +product SUN KEYBOARD_TYPE_6 0x0005 Type 6 USB keyboard +product SUN KEYBOARD_TYPE_7 0x00a2 Type 7 USB keyboard /* XXX The above is a North American PC style keyboard possibly */ product SUN MOUSE 0x0100 Type 6 USB mouse +product SUN KBD_HUB 0x100e Kbd Hub /* Super Top products */ product SUPERTOP IDE 0x6600 USB-IDE _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From c.r.n.a at wanadoo.fr Thu Mar 19 11:10:30 2009 From: c.r.n.a at wanadoo.fr (Nicolas) Date: Thu Mar 19 11:10:36 2009 Subject: "Big Problem" with removable media Message-ID: <49C27B93.5000309@wanadoo.fr> Hi, I'm using FreeBSD 8-Current (as of today) and when i plug my samsung omnia, i have this message: ugen7.7: at usbus7 umass1: on usbus7 umass1: SCSI over Bulk-Only; quirks = 0x0000 umass1:3:1:-1: Attached to scbus3 da1 at umass-sim1 bus 1 target 0 lun 0 da1: < > Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: 7680MB (15728640 512 byte sectors: 255H 63S/T 979C) GEOM: da1: partition 1 does not start on a track boundary. GEOM: da1: partition 1 does not end on a track boundary. (da1:umass-sim1:1:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 My computer frezees until i unplug the device. What's wrong ? Thanks in advance, Niko. From jhs at berklix.org Thu Mar 19 12:31:24 2009 From: jhs at berklix.org (Julian Stacey) Date: Thu Mar 19 12:31:32 2009 Subject: Belkin Cardbus USB2 adaptors too hot. In-Reply-To: Your message "Thu, 19 Mar 2009 11:13:29 +0100." <200903191013.n2JADT9T054996@fire.js.berklix.net> Message-ID: <200903191931.n2JJVamf061503@fire.js.berklix.net> Problem solved :-) All hangs I mentioned till now were coming from 2 identical enclosures I have, they report as: vendor=0x058f product=0x6390 devclass=0x00 devsubclass=0x00 release=0x0100 sernum="" intclass=0x08 intsubclass=0x06 2 other enclosures of different ID I have are OK. Should we extend devd or BSD USB code to issue a brief warning when devices match any in a lookup list of suspect rogues ? (Not the first flakey USB device I've encountered, Some Sony 2G sticks were bad, all 4, ( "vendor" "0x10d6"; "product" "0x1100"; "devclass" "0x00"; "devsubclass" "0x00"; "release" "0x0100"; ) PS Thanks for you power etc advice Warner :-) Further backround before conclusion above: { I moved same new 250G disc in same enclosure to another 7.1-RELEASE tower PC with & without USB hub, & with a current doubler cable (ie to suck up to a 2nd 0.5A from 2nd socket if disk wants) testblock -v /mnt/tmp/bla1 stopped writing at 5G. /var/log/messages & console: umass0: BBB reset failed, TIMEOUT umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, TIMEOUT umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, TIMEOUT g_vfs_done():da0a[WRITE(offset=65536, length=2048)]error = 5 g_vfs_done():da0a[WRITE(offset=6144000, length=16384)]error = 5 g_vfs_done():da0a[WRITE(offset=6160384, length=6144)]error = 5 g_vfs_done():da0a[WRITE(offset=198229819392, length=16384)]error = 5 .... I swapped the disc to a different USB to IDE converter, omitted case, disc does not get hot, but USB to IDE chip painfully hot (on good converter) + another power doubler cable, straight into PC, no hub, it wrote then read all remaining FS free space of 217 G succesfully. I swapped my other previously failing 120 G disc out of bad enclosure, into a known good enclosure, NO problems now on that either, have written 106 with no hang, & read verified 60 G as I type. } Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org From thompsa at FreeBSD.org Thu Mar 19 16:09:28 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Thu Mar 19 16:09:40 2009 Subject: USBTODO Message-ID: <20090319223756.GF2118@citylink.fud.org.nz> Hi, Remember there is a page tracking the new USB stack to the 8.0 release. Please add any items/regressions or even better would be to pick up a task and work on it. http://wiki.freebsd.org/USBTODO Andrew From imp at bsdimp.com Thu Mar 19 18:37:07 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Mar 19 18:37:13 2009 Subject: USBTODO In-Reply-To: <20090319223756.GF2118@citylink.fud.org.nz> References: <20090319223756.GF2118@citylink.fud.org.nz> Message-ID: <20090319.193447.-399283086.imp@bsdimp.com> In message: <20090319223756.GF2118@citylink.fud.org.nz> Andrew Thompson writes: : Remember there is a page tracking the new USB stack to the 8.0 release. : Please add any items/regressions or even better would be to pick up a : task and work on it. : : http://wiki.freebsd.org/USBTODO I have a flash drive that dies under heavy load (the LED on it goes out) and then any further disk I/O fails. Would something like that go on the page? Warner From weongyo.jeong at gmail.com Thu Mar 19 20:58:55 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Thu Mar 19 20:59:02 2009 Subject: q: USB_SET_TIMEOUT in ugen. In-Reply-To: <200903191432.24364.hselasky@c2i.net> References: <20090318073032.GA12632@weongyo.cdnetworks.kr> <200903190901.23844.hselasky@c2i.net> <20090319105200.GA17221@weongyo.cdnetworks.kr> <200903191432.24364.hselasky@c2i.net> Message-ID: <20090320035850.GB17221@weongyo.cdnetworks.kr> On Thu, Mar 19, 2009 at 02:32:23PM +0100, Hans Petter Selasky wrote: > Hi, > > On Thursday 19 March 2009, Weongyo Jeong wrote: > > On Thu, Mar 19, 2009 at 09:01:23AM +0100, Hans Petter Selasky wrote: > > > On Thursday 19 March 2009, Weongyo Jeong wrote: > > > > ugen_default_read_callback:384: actlen=0, aframes=0 > > > > ugen_default_read_callback:384: actlen=0, aframes=0 > > > > ugen_read_clear_stall_callback:477: f=0xc4d5b000: stall cleared > > > > > > One difference from the old ugen implementation is that a stall error > > > does not cause any error to be returned to userland! > > > > > > You could try to return a ZLP on errors. Try this patch: > > > > > > http://perforce.freebsd.org/chv.cgi?CH=159423 > > > > > > If you need to distinguish a ZLP from a STALL, then you have to use the > > > new libusb! Ugen is not meant to be a replacement for libusb! > > > > Thanks you for a patch but it's not a answer what I want because my > > symptom is that recv(2) waits forever before or returns 0 after applying > > your patch. It shouldn't return 0 or nothing that the size of the recv(2) > > return value should be 512. > > The ugen interface is now double buffered, so it will read data in the > background! The old was not double buffered. There are currently only two > buffers. If you see the packet in the analyzer it has most likely also ended > up in a UGEN buffer. > > > I tried to dump USB transactions using USB > > analyzer and the dump file is available at: > > > > http://people.freebsd.org/~weongyo/uathload_20090319_export.txt > > What happens if you change: > > | if (read(msg, &rxmsg, sizeof(rxmsg)) != > sizeof(rxmsg)) { > 215: | VERBOSE("%s", "\n"); > | err(-1, "error reading msg (%s)", > msgdev); > | break; > | } > > Into while loop for sake of testing? So that if the length is 0 you loop one > more time and if you have more than X zero lengths returned, you break? I tried to do your suggestion but no changes. read(2) returned always 0 (after applying http://perforce.freebsd.org/chv.cgi?CH=159423) that it looks ugen missed a transaction the device sent to the host. > > > > Interesting packets could be found after 241 transactions and the steps > > of program are as follows: > > > > write(endpoint 0x1, buf, 512); > > write(endpoint 0x2, buf, 512); > > write(endpoint 0x2, buf, 512); > > write(endpoint 0x2, buf, 512); > > write(endpoint 0x2, buf, 512); > > read(endpoint 0x81, buf, 512); <-- here error. > > > > As you can see with looking the dump file, ugen couldn't catch the read > > event even though the USB stick responses data at Transaction 264, 265 > > and 266. It looks the problem is in ugen(4). As looking usb_generic.c > > it looks the read/write pipe are opened on the fly when read(2) or > > write(2) systemcalls are called though in the previous ugen(4) in usb1 > > all pipes are opened at open(2). Could this difference affect this > > symptom? I'd try to test another cases. > > The old ugen would also do a clear-stall which the new one does not do, unless > you do an IOCTL before the first read! That is also something you can try. Also I tried this with commenting out all of ioctl(2) calls. But after it it looks recv(2) never returns. regards, Weongyo Jeong From vova at fbsd.ru Fri Mar 20 00:26:49 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Fri Mar 20 00:27:01 2009 Subject: print/hplip does not build with new USB stack (8-CURRENT) Message-ID: <1237531830.1728.24.camel@localhost> Hi # portupgrade -f hplip ---> Reinstalling 'hplip-2.8.2_3' (print/hplip) ---> Building '/usr/ports/print/hplip' ===> Cleaning for net-snmp-5.4.2.1_3 ===> Cleaning for hplip-2.8.2_3 ===> Found saved configuration for hplip-2.7.12 ===> Extracting for hplip-2.8.2_3 => MD5 Checksum OK for hplip-2.8.2.tar.gz. => SHA256 Checksum OK for hplip-2.8.2.tar.gz. ===> Patching for hplip-2.8.2_3 ===> Applying FreeBSD patches for hplip-2.8.2_3 ===> hplip-2.8.2_3 depends on file: /usr/local/bin/python2.5 - found ===> hplip-2.8.2_3 depends on shared library: jpeg.9 - found ===> hplip-2.8.2_3 depends on shared library: sane.1 - found ===> hplip-2.8.2_3 depends on shared library: cups.2 - found ===> hplip-2.8.2_3 depends on shared library: netsnmp.16 - found ===> Configuring for hplip-2.8.2_3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for gawk... gawk ... checking for cups/cups.h... yes checking for usb_init in -lusb... yes checking usb.h usability... yes checking usb.h presence... yes checking for usb.h... yes checking whether /usr/local/bin/python2.5 version >= 2.2... yes ... ===> Building for hplip-2.8.2_3 /bin/sh ./libtool --tag=CC --mode=compile cc -DPACKAGE_NAME=\"HP\ Linux\ Imaging\ and\ Printing\" -DPACKAGE_TARNAME=\"hplip\" -DPACKAGE_VERSION=\"2.8.2\" -DPACKAGE_STRING=\"HP\ Linux\ Imaging\ and\ Printing\ 2.8.2\" -DPACKAGE_BUGREPORT=\"2.8.2.10\" -DPACKAGE=\"hplip\" -DVERSION=\"2.8.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBPTHREAD=1 -DHAVE_LIBM=1 -DHAVE_LIBJPEG=1 -DHAVE_LIBDL=1 -DSTDC_HEADERS=1 -DHAVE_PTHREAD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_SYSLOG_H=1 -DHAVE_UNISTD_H=1 -DHAVE_JPEGLIB_H=1 -DHAVE_UINT32_T=1 -DHAVE_LIBHPIP=1 -DHAVE_LIBCRYPTO=1 -DHAVE_LIBNETSNMP=1 -DHAVE_NET_SNMP_NET_SNMP_CONFIG_H=1 -DHAVE_LIBCUPS=1 -DHAVE_CUPS_CUPS_H=1 -DHAVE_LIBUSB=1 -DHAVE_USB_H=1 -DHAVE_PYTHON2_5_PYTHON_H=1 -DHAVE_LIBSANE=1 -I. -I. -Iip -Iio/hpmud -Iscan/sane -I/usr/local/include -I/usr/local/include/python2.5 -O2 -pipe! -fno-strict-aliasing -c -o cupsext_la-cupsext.lo `test -f 'prnt/cupsext/cupsext.c' || echo './'`prnt/cupsext/cupsext.c mkdir .libs cc "-DPACKAGE_NAME=\"HP Linux Imaging and Printing\"" -DPACKAGE_TARNAME=\"hplip\" -DPACKAGE_VERSION=\"2.8.2\" "-DPACKAGE_STRING=\"HP Linux Imaging and Printing 2.8.2\"" -DPACKAGE_BUGREPORT=\"2.8.2.10\" -DPACKAGE=\"hplip\" -DVERSION=\"2.8.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBPTHREAD=1 -DHAVE_LIBM=1 -DHAVE_LIBJPEG=1 -DHAVE_LIBDL=1 -DSTDC_HEADERS=1 -DHAVE_PTHREAD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_SYSLOG_H=1 -DHAVE_UNISTD_H=1 -DHAVE_JPEGLIB_H=1 -DHAVE_UINT32_T=1 -DHAVE_LIBHPIP=1 -DHAVE_LIBCRYPTO=1 -DHAVE_LIBNETSNMP=1 -DHAVE_NET_SNMP_NET_SNMP_CONFIG_H=1 -DHAVE_LIBCUPS=1 -DHAVE_CUPS_CUPS_H=1 -DHAVE_LIBUSB=1 -DHAVE_USB_H=1 -DHAVE_PYTHON2_5_PYTHON_H=1 -DHAVE_LIBSANE=1 -I. -I. -Iip -Iio/hpmud -Iscan/sane -I/usr/local/include -I/usr/local/include/python2.5 -O2 -pipe -fno-strict-aliasing -c prnt/cupsext/cupsext.c! -fPIC -DPIC -o .libs/cupsext_la-cupsext.o /bin/sh ./libtool --tag=CC --mode=link cc -O2 -pipe -fno-strict-aliasing -L/usr/local/lib -o cupsext.la -rpath /usr/local/lib/python2.5/site-packages -module -avoid-version cupsext_la-cupsext.lo -lsane -lusb -lcups -lnetsnmp -lcrypto -ljpeg -lm -pthread grep: /usr/local/lib/libusb.la: No such file or directory /usr/local/bin/gsed: can't read /usr/local/lib/libusb.la: No such file or directory ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20090320-2598-exqhin-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=hplip-2.8.2_3 UPGRADE_PORT_VER=2.8.2_3 make no libusb port installed, all old usb libraries and headers are cleaned (make delete-old). # pkg_info -I '*usb*' pkg_info: can't find package '*usb*' installed or in a file! # ldconfig -r | fgrep usb 94:-lusbhid.3 => /usr/lib/libusbhid.so.3 101:-lusb.1 => /usr/lib/libusb.so.1 1165:-lsane-mustek_usb.1 => /usr/local/lib/compat/pkg/libsane-mustek_usb.so.1 1166:-lsane-mustek_usb2.1 => /usr/local/lib/compat/pkg/libsane-mustek_usb2.so.1 1501:-lusb.0 => /usr/local/lib/compat/libusb.so.0 1502:-lusbhid.0 => /usr/local/lib/compat/libusbhid.so.0 1503:-lusbhid.1 => /usr/local/lib/compat/libusbhid.so.1 1504:-lusbhid.2 => /usr/local/lib/compat/libusbhid.so.2 # ls -ldtr /usr/include/*usb* -r--r--r-- 1 root wheel 1451 Nov 26 01:10 /usr/include/libusb20_compat10.h -r--r--r-- 1 root wheel 3601 Feb 2 17:20 /usr/include/usbhid.h -r--r--r-- 1 root wheel 9496 Mar 11 02:51 /usr/include/usb.h -r--r--r-- 1 root wheel 15969 Mar 11 02:51 /usr/include/libusb20_desc.h -r--r--r-- 1 root wheel 11822 Mar 18 17:31 /usr/include/libusb20.h # -- Vladimir B. Grebenschikov vova@fbsd.ru From vova at fbsd.ru Fri Mar 20 00:26:51 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Fri Mar 20 00:27:02 2009 Subject: USBTODO In-Reply-To: <20090319223756.GF2118@citylink.fud.org.nz> References: <20090319223756.GF2118@citylink.fud.org.nz> Message-ID: <1237531950.1728.25.camel@localhost> On Thu, 2009-03-19 at 15:37 -0700, Andrew Thompson wrote: > Hi, > > > Remember there is a page tracking the new USB stack to the 8.0 release. > Please add any items/regressions or even better would be to pick up a > task and work on it. > > http://wiki.freebsd.org/USBTODO Please add here http://wiki.freebsd.org/PortsBrokenOnCurrent to USB part print/hplip > Andrew -- Vladimir B. Grebenschikov vova@fbsd.ru From ota at j.email.ne.jp Fri Mar 20 00:51:23 2009 From: ota at j.email.ne.jp (Yoshihiro Ota) Date: Fri Mar 20 00:51:30 2009 Subject: USBTODO In-Reply-To: <20090319223756.GF2118@citylink.fud.org.nz> References: <20090319223756.GF2118@citylink.fud.org.nz> Message-ID: <20090320043115.3b46177e.ota@j.email.ne.jp> On Thu, 19 Mar 2009 15:37:56 -0700 Andrew Thompson wrote: > Hi, > > > Remember there is a page tracking the new USB stack to the 8.0 release. > Please add any items/regressions or even better would be to pick up a > task and work on it. > > http://wiki.freebsd.org/USBTODO Can I create an account and update the page freely or do I need someone's permission to do so? I have USB FDD that does not work and USB keyboard that needs a workaround in the source. Hans has helped me to get keyboard functional. However, FDD needs more investigation but I haven't got enough time for that, yet. Should these be mentioned in the wiki? There are quirks filed in PRs as I searched patches before I had to create/update one for my device. If I get your or some other committer's help, I can find our quirk updates and report. I am currentlly looking for simple quirk updates that updates the table or add some defines for unlist venders in this effort. Are you, Andrew, able to help to commit them? Thanks, Hiro From hselasky at c2i.net Fri Mar 20 02:20:21 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Mar 20 02:20:28 2009 Subject: "Big Problem" with removable media In-Reply-To: <49C27B93.5000309@wanadoo.fr> References: <49C27B93.5000309@wanadoo.fr> Message-ID: <200903201022.49413.hselasky@c2i.net> On Thursday 19 March 2009, Nicolas wrote: > Hi, > > I'm using FreeBSD 8-Current (as of today) and when i plug my samsung > omnia, i have this message: > > ugen7.7: at usbus7 > umass1: on usbus7 > umass1: SCSI over Bulk-Only; quirks = 0x0000 > umass1:3:1:-1: Attached to scbus3 > da1 at umass-sim1 bus 1 target 0 lun 0 > da1: < > Removable Direct Access SCSI-0 device > da1: 40.000MB/s transfers > da1: 7680MB (15728640 512 byte sectors: 255H 63S/T 979C) > GEOM: da1: partition 1 does not start on a track boundary. > GEOM: da1: partition 1 does not end on a track boundary. > (da1:umass-sim1:1:0:0): Synchronize cache failed, status == 0x4, scsi ^^^^ looks like your mass storage device needs a quirk. You can try sysutils/kdpatch to patch the quirks table for umass. As far as I can tell the table has the same format in usb2 and usb1 so the following should work: kldpatch umass.ko - @0 0x10d6 0x0000xxxx 0xffffffff 0x0201 0x4200 (replace xxxx with the usb product id for your device). 0x201 means use ATAPI commands over BBB protocol which is what your messages say. Perhaps 0x101 also works here. 0x4000 means the following: /* Device cannot handle a SCSI synchronize cache command. Normally * this quirk would be handled in the cam layer, but for IDE bridges * we need to associate the quirk with the bridge and not the * underlying disk device. This is handled by faking a success result. */ # define NO_SYNCHRONIZE_CACHE 0x4000 you may have to play with different flags and quirks to make the thing work. cheers luigi --HPS From lev at serebryakov.spb.ru Fri Mar 20 05:01:53 2009 From: lev at serebryakov.spb.ru (Lev Serebryakov) Date: Fri Mar 20 05:02:00 2009 Subject: libusb-1.x -- is it availiable on FreeBSD? Message-ID: <83352858.20090320144304@serebryakov.spb.ru> Hello, Freebsd-usb. Some software (with Linux origins, of course), which I want to port, uses libusb1 (libusb-1.0). Is it availiable on FreeBSD? It seems, that `ports/devel/libusb' is something very different... -- // Black Lion AKA Lev Serebryakov From thompsa at FreeBSD.org Fri Mar 20 06:43:28 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Fri Mar 20 06:43:34 2009 Subject: libusb-1.x -- is it availiable on FreeBSD? In-Reply-To: <83352858.20090320144304@serebryakov.spb.ru> References: <83352858.20090320144304@serebryakov.spb.ru> Message-ID: <20090320134322.GB5298@citylink.fud.org.nz> On Fri, Mar 20, 2009 at 02:43:04PM +0300, Lev Serebryakov wrote: > Hello, Freebsd-usb. > > Some software (with Linux origins, of course), which I want to port, > uses libusb1 (libusb-1.0). Is it availiable on FreeBSD? It seems, that > `ports/devel/libusb' is something very different... Libusb 1.0 is not yet supported. ports/devel/libusb gives you libusb 0.1 (will be part of the base OS in 8.0). Andrew From lev at serebryakov.spb.ru Fri Mar 20 06:45:02 2009 From: lev at serebryakov.spb.ru (Lev Serebryakov) Date: Fri Mar 20 06:45:08 2009 Subject: libusb-1.x -- is it availiable on FreeBSD? In-Reply-To: <20090320134322.GB5298@citylink.fud.org.nz> References: <83352858.20090320144304@serebryakov.spb.ru> <20090320134322.GB5298@citylink.fud.org.nz> Message-ID: <973521329.20090320164458@serebryakov.spb.ru> Hello, Andrew. You wrote 20 ????? 2009 ?., 16:43:22: >> Some software (with Linux origins, of course), which I want to port, >> uses libusb1 (libusb-1.0). Is it availiable on FreeBSD? It seems, that >> `ports/devel/libusb' is something very different... > Libusb 1.0 is not yet supported. ports/devel/libusb gives you libusb 0.1 Any ongoing project of porting? > (will be part of the base OS in 8.0). According to USBTODO wikipage, here is plan to add 1.0 support to 8.0? -- // Black Lion AKA Lev Serebryakov From hselasky at c2i.net Fri Mar 20 06:45:24 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Mar 20 06:45:31 2009 Subject: libusb-1.x -- is it availiable on FreeBSD? In-Reply-To: <83352858.20090320144304@serebryakov.spb.ru> References: <83352858.20090320144304@serebryakov.spb.ru> Message-ID: <200903201447.49983.hselasky@c2i.net> On Friday 20 March 2009, Lev Serebryakov wrote: > Hello, Freebsd-usb. > > Some software (with Linux origins, of course), which I want to port, > uses libusb1 (libusb-1.0). Is it availiable on FreeBSD? It seems, that > `ports/devel/libusb' is something very different... I will be available on 8-current eventually. --HPS From hselasky at c2i.net Fri Mar 20 07:03:39 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Mar 20 07:03:46 2009 Subject: libusb-1.x -- is it availiable on FreeBSD? In-Reply-To: <200903201447.49983.hselasky@c2i.net> References: <83352858.20090320144304@serebryakov.spb.ru> <200903201447.49983.hselasky@c2i.net> Message-ID: <200903201506.08582.hselasky@c2i.net> On Friday 20 March 2009, Hans Petter Selasky wrote: > On Friday 20 March 2009, Lev Serebryakov wrote: > > Hello, Freebsd-usb. > > > > Some software (with Linux origins, of course), which I want to port, > > uses libusb1 (libusb-1.0). Is it availiable on FreeBSD? It seems, that > > `ports/devel/libusb' is something very different... > > I will be available on 8-current eventually. s/I/it s/on/in My USB keyboard is obviously not of the best brand :-) --HPS From gavin at FreeBSD.org Fri Mar 20 07:40:05 2009 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Fri Mar 20 07:40:11 2009 Subject: usb/132066: [ukbd] Keyboard failure USB keyboard DELL 760 Message-ID: <200903201440.n2KEe46r077977@freefall.freebsd.org> The following reply was made to PR usb/132066; it has been noted by GNATS. From: Gavin Atkinson To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/132066: [ukbd] Keyboard failure USB keyboard DELL 760 Date: Fri, 20 Mar 2009 14:33:36 +0000 -------- Forwarded Message -------- From: Judah Levine To: gavin@FreeBSD.org, freebsd-usb@FreeBSD.org Cc: fein@nist.gov Subject: Re: usb/132066: [ukbd] Keyboard failure USB keyboard DELL 760 Date: Fri, 13 Mar 2009 10:14:33 -0600 Hello, I have fixed this problem, but I don't understand why it works. I made the following changes to the config file and re-built the kernel: 1. remove device atkb 2. add device puc 3. add: options UKBD_DFLT_KEYMAP options UKBD_DFLT_KEYMAP=us.unix I have installed the same software with USB keyboards on many different systems, and this is the first time that I had to do this. The system now works correctly both using the command-line and X-windows. Is it possible that the keyboard is not being recognized correctly during the bootstrap process? Judah Levine Time and Frequency Division NIST Boulder From thompsa at FreeBSD.org Fri Mar 20 10:14:20 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Fri Mar 20 10:14:31 2009 Subject: USBTODO In-Reply-To: <20090319.193447.-399283086.imp@bsdimp.com> References: <20090319223756.GF2118@citylink.fud.org.nz> <20090319.193447.-399283086.imp@bsdimp.com> Message-ID: <20090320171413.GA33041@citylink.fud.org.nz> On Thu, Mar 19, 2009 at 07:34:47PM -0600, M. Warner Losh wrote: > In message: <20090319223756.GF2118@citylink.fud.org.nz> > Andrew Thompson writes: > : Remember there is a page tracking the new USB stack to the 8.0 release. > : Please add any items/regressions or even better would be to pick up a > : task and work on it. > : > : http://wiki.freebsd.org/USBTODO > > I have a flash drive that dies under heavy load (the LED on it goes > out) and then any further disk I/O fails. Would something like that > go on the page? I think so, under the regressions section. Its better to be more verbose than forget to fix something. Andrew From dfilter at FreeBSD.ORG Fri Mar 20 15:20:03 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Fri Mar 20 15:20:10 2009 Subject: usb/132799: commit references a PR Message-ID: <200903202220.n2KMK3xB001987@freefall.freebsd.org> The following reply was made to PR usb/132799; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: usb/132799: commit references a PR Date: Fri, 20 Mar 2009 22:17:37 +0000 (UTC) Author: thompsa Date: Fri Mar 20 22:17:27 2009 New Revision: 190189 URL: http://svn.freebsd.org/changeset/base/190189 Log: Add umass quirk. PR: usb/132799 Reported by: Yoshihiro Ota Submitted by: Hans Petter Selasky Modified: head/sys/dev/usb/storage/umass.c Modified: head/sys/dev/usb/storage/umass.c ============================================================================== --- head/sys/dev/usb/storage/umass.c Fri Mar 20 22:15:22 2009 (r190188) +++ head/sys/dev/usb/storage/umass.c Fri Mar 20 22:17:27 2009 (r190189) @@ -458,6 +458,7 @@ static const struct umass_devdescr umass {USB_VENDOR_GENESYS, USB_PRODUCT_GENESYS_GL641USB2IDE, RID_WILDCARD, UMASS_PROTO_SCSI | UMASS_PROTO_BBB, FORCE_SHORT_INQUIRY | NO_START_STOP | IGNORE_RESIDUE + | NO_SYNCHRONIZE_CACHE }, {USB_VENDOR_GENESYS, USB_PRODUCT_GENESYS_GL641USB2IDE_2, RID_WILDCARD, UMASS_PROTO_ATAPI | UMASS_PROTO_BBB, _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From thompsa at FreeBSD.org Fri Mar 20 15:24:07 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Fri Mar 20 15:24:13 2009 Subject: openct port and USB2 In-Reply-To: <200903190004.n2J04YjP012665@lava.sentex.ca> References: <200903182015.n2IKFWIb011457@lava.sentex.ca> <20090318214025.GB79077@citylink.fud.org.nz> <200903190004.n2J04YjP012665@lava.sentex.ca> Message-ID: <20090320222401.GA39648@citylink.fud.org.nz> On Wed, Mar 18, 2009 at 08:04:48PM -0400, Mike Tancsa wrote: > At 05:40 PM 3/18/2009, Andrew Thompson wrote: >> On Wed, Mar 18, 2009 at 04:15:46PM -0400, Mike Tancsa wrote: >> > Hi, >> > I was trying to see if OpenCT and OpenSC work under the new USB >> > regime, but openCT doesnt compile now. Are there any tricks to get it to >> > compile and or work ? >> > >> >> Can you try this patch. >> >> http://people.freebsd.org/~thompsa/openct.diff >> > > Thanks! It does build now. However, not all of the bits seem to be > working just yet It should be working as of r190185, please try again. Andrew From mike at sentex.net Fri Mar 20 19:03:10 2009 From: mike at sentex.net (Mike Tancsa) Date: Fri Mar 20 19:03:16 2009 Subject: openct port and USB2 In-Reply-To: <20090320222401.GA39648@citylink.fud.org.nz> References: <200903182015.n2IKFWIb011457@lava.sentex.ca> <20090318214025.GB79077@citylink.fud.org.nz> <200903190004.n2J04YjP012665@lava.sentex.ca> <20090320222401.GA39648@citylink.fud.org.nz> Message-ID: <200903210202.n2L22ltf030180@lava.sentex.ca> At 06:24 PM 3/20/2009, Andrew Thompson wrote: >On Wed, Mar 18, 2009 at 08:04:48PM -0400, Mike Tancsa wrote: > > At 05:40 PM 3/18/2009, Andrew Thompson wrote: > >> On Wed, Mar 18, 2009 at 04:15:46PM -0400, Mike Tancsa wrote: > >> > Hi, > >> > I was trying to see if OpenCT and OpenSC work under the new USB > >> > regime, but openCT doesnt compile now. Are there any tricks > to get it to > >> > compile and or work ? > >> > > >> > >> Can you try this patch. > >> > >> http://people.freebsd.org/~thompsa/openct.diff > >> > > > > Thanks! It does build now. However, not all of the bits seem to be > > working just yet > >It should be working as of r190185, please try again. It sure does!!! Thanks for fixing! ---Mike >Andrew From nox at jelal.kn-bremen.de Sat Mar 21 14:06:17 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sat Mar 21 14:06:23 2009 Subject: Xorg 7.4 and umass devices - a bad combination? In-Reply-To: <20090318205909.07625cdb.torfinn.ingolfsen@broadpark.no> References: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> Message-ID: <200903212044.n2LKiYWR071943@saturn.kn-bremen.de> In article <20090318205909.07625cdb.torfinn.ingolfsen@broadpark.no> you write: >Hello, > >More testing. >- I verified that listing the firewire drive while Xorg is running >doesn't seeem to cause any errors. >So I thought: what happens if I start Xorg (using startx), then exit it >and _then_ do an 'ls' on the usb drives? > >First try: 'startx', do a couple of commands (like 'date', 'pwd'), the >exit Xorg again. Then do 'ls' on the usb drives. Result: it works >without errors. > >Second try: 'startx', do a couple of commands (like 'date', 'pwd'), the >exit Xorg again. Then do 'ls' on the usb drives. Result: the erors are >back. Just in case you haven't seen it yet... Apparently there have been issues on some hardware with the way xorg (used to) probe the pci bus, see the `Unhappy Xorg upgrade' thread on -stable, particularly: http://docs.freebsd.org/cgi/mid.cgi?1234292252.1524.38.camel and http://docs.freebsd.org/cgi/mid.cgi?49A81556.2040801 (which details the fix.) HTH, Juergen From torfinn.ingolfsen at broadpark.no Sat Mar 21 14:42:54 2009 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Sat Mar 21 14:43:01 2009 Subject: Xorg 7.4 and umass devices - a bad combination? In-Reply-To: <200903212044.n2LKiYWR071943@saturn.kn-bremen.de> References: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> <200903212044.n2LKiYWR071943@saturn.kn-bremen.de> Message-ID: <20090321224252.7a92180e.torfinn.ingolfsen@broadpark.no> On Sat, 21 Mar 2009 21:44:34 +0100 (CET) Juergen Lock wrote: > Just in case you haven't seen it yet... > > Apparently there have been issues on some hardware with the way xorg > (used to) probe the pci bus, see the `Unhappy Xorg upgrade' thread on > -stable, particularly: > http://docs.freebsd.org/cgi/mid.cgi?1234292252.1524.38.camel > and > http://docs.freebsd.org/cgi/mid.cgi?49A81556.2040801 > (which details the fix.) Interesting. As mentioned in my earlier posts, I am running RELENG_6, not RELENG_7. Is this problem also relevant for releng_6? -- Torfinn From torfinn.ingolfsen at broadpark.no Sat Mar 21 14:47:26 2009 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Sat Mar 21 14:47:39 2009 Subject: Xorg 7.4 and umass devices - a bad combination? In-Reply-To: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> References: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> Message-ID: <20090321224724.1e2e2c72.torfinn.ingolfsen@broadpark.no> I did some more tests, this time with RELENG_7 / amd64: root@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #2: Tue Mar 17 22:09:21 CET 2009 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 I updated the ports tree, and installed Xorg 7.4 (and Xfce 4.6.0) directly - no upgrades needed. And now everything runs smooth - I can not reproduce the problem at all. I am using the ati driver (xf86-video-ati-6.12.1) for Xorg in case that matters. -- Regards, Torfinn Ingolfsen From arved at FreeBSD.org Sun Mar 22 05:26:30 2009 From: arved at FreeBSD.org (Tilman Linneweh) Date: Sun Mar 22 05:26:37 2009 Subject: USBTODO In-Reply-To: <20090320043115.3b46177e.ota@j.email.ne.jp> References: <20090319223756.GF2118@citylink.fud.org.nz> <20090320043115.3b46177e.ota@j.email.ne.jp> Message-ID: <8C4A9CBD-486C-40E5-AE91-C2B281625C1B@FreeBSD.org> * Yoshihiro Ota [ Mar 20, 2009 (09:31 )]: >> >> Remember there is a page tracking the new USB stack to the 8.0 >> release. >> Please add any items/regressions or even better would be to pick up a >> task and work on it. >> >> http://wiki.freebsd.org/USBTODO > > Can I create an account and update the page freely or do I need > someone's > permission to do so? You can create an account and then ask a FreeBSD Developer to give editing permissions to this account. From imp at bsdimp.com Sun Mar 22 06:13:19 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 22 06:13:25 2009 Subject: Still wrong Message-ID: <20090322.071220.1447367564.imp@bsdimp.com> ugen2.2: at usbus2 umass0: on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x4480 umass0:2:0:-1: Attached to scbus2 (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): NOT READY csi:0,0,bb,0 asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error da0 at umass-sim0 bus 0 target 0 lun 0 da0: < > Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present This is a cd player. Warner From imp at bsdimp.com Sun Mar 22 06:16:11 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 22 06:16:18 2009 Subject: usbdevs -v Message-ID: <20090322.071504.-726381019.imp@bsdimp.com> So what's the new way to say usbdevs -v? usbconfig list doesn't list device IDs. And devinfo doesn't show a device unless it is attached to a driver. Warner From imp at bsdimp.com Sun Mar 22 06:22:11 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 22 06:22:17 2009 Subject: Still wrong In-Reply-To: <20090322.071220.1447367564.imp@bsdimp.com> References: <20090322.071220.1447367564.imp@bsdimp.com> Message-ID: <20090322.072131.-450937795.imp@bsdimp.com> In message: <20090322.071220.1447367564.imp@bsdimp.com> "M. Warner Losh" writes: : ugen2.2: at usbus2 : umass0: on usbus2 : umass0: SCSI over Bulk-Only; quirks = 0x4480 : umass0:2:0:-1: Attached to scbus2 : (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): NOT READY csi:0,0,bb,0 asc:3a,0 : (probe0:umass-sim0:0:0:0): Medium not present : (probe0:umass-sim0:0:0:0): Unretryable error : da0 at umass-sim0 bus 0 target 0 lun 0 : da0: < > Removable Direct Access SCSI-2 device : da0: 40.000MB/s transfers : da0: Attempt to query device size failed: NOT READY, Medium not present : : This is a cd player. The MYSON HEDEN entry most likely can just be removed entirely. I don't think it is needed, and certainly isn't necessary for my device. Warner From hselasky at c2i.net Sun Mar 22 06:51:43 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Mar 22 06:51:55 2009 Subject: usbdevs -v In-Reply-To: <20090322.071504.-726381019.imp@bsdimp.com> References: <20090322.071504.-726381019.imp@bsdimp.com> Message-ID: <200903221454.10594.hselasky@c2i.net> On Sunday 22 March 2009, M. Warner Losh wrote: > So what's the new way to say usbdevs -v? usbconfig list doesn't list > device IDs. And devinfo doesn't show a device unless it is attached > to a driver. usbconfig dump_device_desc | grep id --HPS From hselasky at c2i.net Sun Mar 22 06:51:43 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Mar 22 06:51:55 2009 Subject: usbdevs -v In-Reply-To: <20090322.071504.-726381019.imp@bsdimp.com> References: <20090322.071504.-726381019.imp@bsdimp.com> Message-ID: <200903221454.10594.hselasky@c2i.net> On Sunday 22 March 2009, M. Warner Losh wrote: > So what's the new way to say usbdevs -v? usbconfig list doesn't list > device IDs. And devinfo doesn't show a device unless it is attached > to a driver. usbconfig dump_device_desc | grep id --HPS From hselasky at c2i.net Sun Mar 22 06:52:44 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sun Mar 22 06:52:50 2009 Subject: Still wrong In-Reply-To: <20090322.072131.-450937795.imp@bsdimp.com> References: <20090322.071220.1447367564.imp@bsdimp.com> <20090322.072131.-450937795.imp@bsdimp.com> Message-ID: <200903221455.13414.hselasky@c2i.net> On Sunday 22 March 2009, M. Warner Losh wrote: > In message: <20090322.071220.1447367564.imp@bsdimp.com> > > "M. Warner Losh" writes: > : ugen2.2: at usbus2 > : umass0: on usbus2 > : umass0: SCSI over Bulk-Only; quirks = 0x4480 > : umass0:2:0:-1: Attached to scbus2 > : (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): NOT READY csi:0,0,bb,0 asc:3a,0 > : (probe0:umass-sim0:0:0:0): Medium not present > : (probe0:umass-sim0:0:0:0): Unretryable error > : da0 at umass-sim0 bus 0 target 0 lun 0 > : da0: < > Removable Direct Access SCSI-2 device > : da0: 40.000MB/s transfers > : da0: Attempt to query device size failed: NOT READY, Medium not present > : > : This is a cd player. > > The MYSON HEDEN entry most likely can just be removed entirely. I > don't think it is needed, and certainly isn't necessary for my > device. Maybe you can limit the entry by the revision ID ? It seems like multiple products are using the same vendor + product ID's. --HPS From thompsa at FreeBSD.org Sun Mar 22 08:38:03 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Mar 22 08:38:10 2009 Subject: usbdevs -v In-Reply-To: <20090322.071504.-726381019.imp@bsdimp.com> References: <20090322.071504.-726381019.imp@bsdimp.com> Message-ID: <20090322153757.GC50126@citylink.fud.org.nz> On Sun, Mar 22, 2009 at 07:15:04AM -0600, M. Warner Losh wrote: > So what's the new way to say usbdevs -v? usbconfig list doesn't list > device IDs. And devinfo doesn't show a device unless it is attached > to a driver. There is an open task on the todo to add usbdevs compat to usbconfig. Andrew From imp at bsdimp.com Sun Mar 22 11:40:41 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 22 11:40:48 2009 Subject: Still wrong In-Reply-To: <200903221455.13414.hselasky@c2i.net> References: <20090322.071220.1447367564.imp@bsdimp.com> <20090322.072131.-450937795.imp@bsdimp.com> <200903221455.13414.hselasky@c2i.net> Message-ID: <20090322.124024.1062686055.imp@bsdimp.com> In message: <200903221455.13414.hselasky@c2i.net> Hans Petter Selasky writes: : On Sunday 22 March 2009, M. Warner Losh wrote: : > In message: <20090322.071220.1447367564.imp@bsdimp.com> : > : > "M. Warner Losh" writes: : > : ugen2.2: at usbus2 : > : umass0: on usbus2 : > : umass0: SCSI over Bulk-Only; quirks = 0x4480 : > : umass0:2:0:-1: Attached to scbus2 : > : (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): NOT READY csi:0,0,bb,0 asc:3a,0 : > : (probe0:umass-sim0:0:0:0): Medium not present : > : (probe0:umass-sim0:0:0:0): Unretryable error : > : da0 at umass-sim0 bus 0 target 0 lun 0 : > : da0: < > Removable Direct Access SCSI-2 device : > : da0: 40.000MB/s transfers : > : da0: Attempt to query device size failed: NOT READY, Medium not present : > : : > : This is a cd player. : > : > The MYSON HEDEN entry most likely can just be removed entirely. I : > don't think it is needed, and certainly isn't necessary for my : > device. : : Maybe you can limit the entry by the revision ID ? : : It seems like multiple products are using the same vendor + product ID's. Do we have the history about why the quirk was needed to start with? Warner From imp at bsdimp.com Sun Mar 22 12:16:23 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 22 12:16:30 2009 Subject: usbdevs -v In-Reply-To: <200903221454.10594.hselasky@c2i.net> References: <20090322.071504.-726381019.imp@bsdimp.com> <200903221454.10594.hselasky@c2i.net> Message-ID: <20090322.131558.114727889.imp@bsdimp.com> In message: <200903221454.10594.hselasky@c2i.net> Hans Petter Selasky writes: : On Sunday 22 March 2009, M. Warner Losh wrote: : > So what's the new way to say usbdevs -v? usbconfig list doesn't list : > device IDs. And devinfo doesn't show a device unless it is attached : > to a driver. : : usbconfig dump_device_desc | grep id So the answer would basically be "no, there isn't a simple one": sudo usbconfig dump_device_desc | grep id idVendor = 0x0000 idProduct = 0x0000 idVendor = 0x0000 idProduct = 0x0000 idVendor = 0x0000 idProduct = 0x0000 idVendor = 0x04cf idProduct = 0x8818 idVendor = 0x0d49 idProduct = 0x7310 It is possible to find the info, but it is burried in a very verbose output. It is some cool very verbose output, granted, but still, it can take a while to find... Guess that's what they made emacs for... Warner From chuckr at telenix.org Sun Mar 22 12:44:02 2009 From: chuckr at telenix.org (Chuck Robey) Date: Sun Mar 22 12:44:15 2009 Subject: usbdevs -v In-Reply-To: <200903221454.10594.hselasky@c2i.net> References: <20090322.071504.-726381019.imp@bsdimp.com> <200903221454.10594.hselasky@c2i.net> Message-ID: <49C68EBB.8090306@telenix.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hans Petter Selasky wrote: > On Sunday 22 March 2009, M. Warner Losh wrote: >> So what's the new way to say usbdevs -v? usbconfig list doesn't list >> device IDs. And devinfo doesn't show a device unless it is attached >> to a driver. > > usbconfig dump_device_desc | grep id Is this usbconfig interface planned to be the only remaining tool? Having only those difficult to remember long form commands makes this tool quite user unfriendly. In my own system, I'm going to have to implement a shell shim, to help me out. Doesn't this seem hard to remember, to anyone else? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknGjrsACgkQz62J6PPcoOms6QCeJn6H3//84neYYT4blOpgHkfr Eo8Ani1aawuhT9VLRqIdes9v8TrX33hl =VRRs -----END PGP SIGNATURE----- From chuckr at telenix.org Sun Mar 22 12:44:02 2009 From: chuckr at telenix.org (Chuck Robey) Date: Sun Mar 22 12:44:15 2009 Subject: usbdevs -v In-Reply-To: <200903221454.10594.hselasky@c2i.net> References: <20090322.071504.-726381019.imp@bsdimp.com> <200903221454.10594.hselasky@c2i.net> Message-ID: <49C68EBB.8090306@telenix.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hans Petter Selasky wrote: > On Sunday 22 March 2009, M. Warner Losh wrote: >> So what's the new way to say usbdevs -v? usbconfig list doesn't list >> device IDs. And devinfo doesn't show a device unless it is attached >> to a driver. > > usbconfig dump_device_desc | grep id Is this usbconfig interface planned to be the only remaining tool? Having only those difficult to remember long form commands makes this tool quite user unfriendly. In my own system, I'm going to have to implement a shell shim, to help me out. Doesn't this seem hard to remember, to anyone else? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknGjrsACgkQz62J6PPcoOms6QCeJn6H3//84neYYT4blOpgHkfr Eo8Ani1aawuhT9VLRqIdes9v8TrX33hl =VRRs -----END PGP SIGNATURE----- From thompsa at FreeBSD.org Sun Mar 22 13:08:20 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Mar 22 13:08:32 2009 Subject: usbdevs -v In-Reply-To: <49C68EBB.8090306@telenix.org> References: <20090322.071504.-726381019.imp@bsdimp.com> <200903221454.10594.hselasky@c2i.net> <49C68EBB.8090306@telenix.org> Message-ID: <20090322200814.GA54381@citylink.fud.org.nz> On Sun, Mar 22, 2009 at 03:17:15PM -0400, Chuck Robey wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hans Petter Selasky wrote: > > On Sunday 22 March 2009, M. Warner Losh wrote: > >> So what's the new way to say usbdevs -v? usbconfig list doesn't list > >> device IDs. And devinfo doesn't show a device unless it is attached > >> to a driver. > > > > usbconfig dump_device_desc | grep id > > Is this usbconfig interface planned to be the only remaining tool? Having only > those difficult to remember long form commands makes this tool quite user > unfriendly. In my own system, I'm going to have to implement a shell shim, to > help me out. Doesn't this seem hard to remember, to anyone else? As I have already said on this thread there is an open task to implement usbdevs compat to usbconfig. Once this is done the problem is moot :) Andrew From thompsa at FreeBSD.org Sun Mar 22 13:08:20 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sun Mar 22 13:08:32 2009 Subject: usbdevs -v In-Reply-To: <49C68EBB.8090306@telenix.org> References: <20090322.071504.-726381019.imp@bsdimp.com> <200903221454.10594.hselasky@c2i.net> <49C68EBB.8090306@telenix.org> Message-ID: <20090322200814.GA54381@citylink.fud.org.nz> On Sun, Mar 22, 2009 at 03:17:15PM -0400, Chuck Robey wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hans Petter Selasky wrote: > > On Sunday 22 March 2009, M. Warner Losh wrote: > >> So what's the new way to say usbdevs -v? usbconfig list doesn't list > >> device IDs. And devinfo doesn't show a device unless it is attached > >> to a driver. > > > > usbconfig dump_device_desc | grep id > > Is this usbconfig interface planned to be the only remaining tool? Having only > those difficult to remember long form commands makes this tool quite user > unfriendly. In my own system, I'm going to have to implement a shell shim, to > help me out. Doesn't this seem hard to remember, to anyone else? As I have already said on this thread there is an open task to implement usbdevs compat to usbconfig. Once this is done the problem is moot :) Andrew From imp at bsdimp.com Sun Mar 22 13:16:56 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 22 13:17:08 2009 Subject: usbdevs -v In-Reply-To: <49C68EBB.8090306@telenix.org> References: <20090322.071504.-726381019.imp@bsdimp.com> <200903221454.10594.hselasky@c2i.net> <49C68EBB.8090306@telenix.org> Message-ID: <20090322.141641.1942082123.imp@bsdimp.com> In message: <49C68EBB.8090306@telenix.org> Chuck Robey writes: : -----BEGIN PGP SIGNED MESSAGE----- : Hash: SHA1 : : Hans Petter Selasky wrote: : > On Sunday 22 March 2009, M. Warner Losh wrote: : >> So what's the new way to say usbdevs -v? usbconfig list doesn't list : >> device IDs. And devinfo doesn't show a device unless it is attached : >> to a driver. : > : > usbconfig dump_device_desc | grep id : : Is this usbconfig interface planned to be the only remaining tool? Having only : those difficult to remember long form commands makes this tool quite user : unfriendly. In my own system, I'm going to have to implement a shell shim, to : help me out. Doesn't this seem hard to remember, to anyone else? I'd be happy with a 'usbconfig list -v' for this request. usbdevs does little more than that. That would make the usbdevs "program" #!/bin/sh exec usbconfig list $* (or is that list bit "$*", I forget). Warner From imp at bsdimp.com Sun Mar 22 13:16:56 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 22 13:17:09 2009 Subject: usbdevs -v In-Reply-To: <49C68EBB.8090306@telenix.org> References: <20090322.071504.-726381019.imp@bsdimp.com> <200903221454.10594.hselasky@c2i.net> <49C68EBB.8090306@telenix.org> Message-ID: <20090322.141641.1942082123.imp@bsdimp.com> In message: <49C68EBB.8090306@telenix.org> Chuck Robey writes: : -----BEGIN PGP SIGNED MESSAGE----- : Hash: SHA1 : : Hans Petter Selasky wrote: : > On Sunday 22 March 2009, M. Warner Losh wrote: : >> So what's the new way to say usbdevs -v? usbconfig list doesn't list : >> device IDs. And devinfo doesn't show a device unless it is attached : >> to a driver. : > : > usbconfig dump_device_desc | grep id : : Is this usbconfig interface planned to be the only remaining tool? Having only : those difficult to remember long form commands makes this tool quite user : unfriendly. In my own system, I'm going to have to implement a shell shim, to : help me out. Doesn't this seem hard to remember, to anyone else? I'd be happy with a 'usbconfig list -v' for this request. usbdevs does little more than that. That would make the usbdevs "program" #!/bin/sh exec usbconfig list $* (or is that list bit "$*", I forget). Warner From imp at bsdimp.com Sun Mar 22 13:28:20 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 22 13:28:32 2009 Subject: usbdevs -v In-Reply-To: <20090322.141641.1942082123.imp@bsdimp.com> References: <200903221454.10594.hselasky@c2i.net> <49C68EBB.8090306@telenix.org> <20090322.141641.1942082123.imp@bsdimp.com> Message-ID: <20090322.142746.-364329192.imp@bsdimp.com> In message: <20090322.141641.1942082123.imp@bsdimp.com> "M. Warner Losh" writes: : In message: <49C68EBB.8090306@telenix.org> : Chuck Robey writes: : : -----BEGIN PGP SIGNED MESSAGE----- : : Hash: SHA1 : : : : Hans Petter Selasky wrote: : : > On Sunday 22 March 2009, M. Warner Losh wrote: : : >> So what's the new way to say usbdevs -v? usbconfig list doesn't list : : >> device IDs. And devinfo doesn't show a device unless it is attached : : >> to a driver. : : > : : > usbconfig dump_device_desc | grep id : : : : Is this usbconfig interface planned to be the only remaining tool? Having only : : those difficult to remember long form commands makes this tool quite user : : unfriendly. In my own system, I'm going to have to implement a shell shim, to : : help me out. Doesn't this seem hard to remember, to anyone else? : : I'd be happy with a 'usbconfig list -v' for this request. usbdevs : does little more than that. That would make the usbdevs "program" : : #!/bin/sh : exec usbconfig list $* : : (or is that list bit "$*", I forget). Oh, just ran the man page, and it is a little more than that... -f is the only hard one to implement... Warner From imp at bsdimp.com Sun Mar 22 13:28:20 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Mar 22 13:28:32 2009 Subject: usbdevs -v In-Reply-To: <20090322.141641.1942082123.imp@bsdimp.com> References: <200903221454.10594.hselasky@c2i.net> <49C68EBB.8090306@telenix.org> <20090322.141641.1942082123.imp@bsdimp.com> Message-ID: <20090322.142746.-364329192.imp@bsdimp.com> In message: <20090322.141641.1942082123.imp@bsdimp.com> "M. Warner Losh" writes: : In message: <49C68EBB.8090306@telenix.org> : Chuck Robey writes: : : -----BEGIN PGP SIGNED MESSAGE----- : : Hash: SHA1 : : : : Hans Petter Selasky wrote: : : > On Sunday 22 March 2009, M. Warner Losh wrote: : : >> So what's the new way to say usbdevs -v? usbconfig list doesn't list : : >> device IDs. And devinfo doesn't show a device unless it is attached : : >> to a driver. : : > : : > usbconfig dump_device_desc | grep id : : : : Is this usbconfig interface planned to be the only remaining tool? Having only : : those difficult to remember long form commands makes this tool quite user : : unfriendly. In my own system, I'm going to have to implement a shell shim, to : : help me out. Doesn't this seem hard to remember, to anyone else? : : I'd be happy with a 'usbconfig list -v' for this request. usbdevs : does little more than that. That would make the usbdevs "program" : : #!/bin/sh : exec usbconfig list $* : : (or is that list bit "$*", I forget). Oh, just ran the man page, and it is a little more than that... -f is the only hard one to implement... Warner From bugmaster at FreeBSD.org Mon Mar 23 04:07:06 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Mar 23 04:09:37 2009 Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org Message-ID: <200903231107.n2NB751B004181@freefall.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/132799 usb [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CA o usb/132785 usb [usb] [patch] Gemtech remote powersocket is classed as o usb/132594 usb USB subsystem causes page fault and crashes o usb/132312 usb Xorg 7.4 halts USB controller o usb/132080 usb [patch] [usb] Kernel panic after NOMEM caused by rum 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/131912 usb [uslcom] [patch] New devices using Silicon Labs chips o usb/131900 usb [usbdevs] [patch] Additional product identification co 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 f usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk 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/130325 usb [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh 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 [newusb] DVD drive detects as 'da' device o usb/129964 usb [newusb] disconnection of ugen devices isn't logged o bin/129963 usb [newusb] usbconfig(8) fails with misleading error when o docs/129962 usb [newusb] usbconfig(8) refers to non-existant usb2_core o usb/129945 usb [usbdevs] [patch] add u3g support for Longcheer WM66 U o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [patch] add support for ZTE AC8700 modem o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [patch] Liebert UPS being assigned uhid and o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb] [patch] uaudio is not full duplex o 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 f usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup o usb/127549 usb [umass] [patch] Meizu MiniPlayer M6 (SL) requires some s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127423 usb [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr o usb/127342 usb [boot] cannot enable usb keyboard and mouse support in o kern/127222 usb [ohci]: Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c f 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/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if 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/125264 usb [patch] sysctl for set usb mouse rate (very useful for 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 o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work 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/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 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/122621 usb [patch] [request] New driver for Sierra Wireless 3G US 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/122025 usb [uscanner] [patch] uscanner does not attach to Epson R 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/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] FreeBSD fails to boot with usb legacy support e 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 [umass] [patch] quirk to support ASUS P535 as umass (a 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/120017 usb [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk o usb/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab 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/118686 usb [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround 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 [uaudio] [patch] Not possible to record with Plantroni 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 o 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 [umass] [patch] Problems with connection of the umass o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113977 usb [request] Need a way to set mode of USB disk's write c o usb/113672 usb [ehci] [panic] Kernel panic with AEWIN CB6971 s usb/113629 usb [ukbd] Dropped USB keyboard events on Dell Latitude D6 o usb/113432 usb [ucom] WARNING: attempt to net_add_domain(netgraph) af a usb/113060 usb [usbdevs] [patch] Samsung printer not working in bidir o usb/112944 usb [ulpt] [patch] Bi-directional access to HP LaserJet 10 o usb/112640 usb [usb] [hang] Kernel freezes when writing a file to an o usb/112631 usb [panic] Problem with SONY DSC-S80 camera on umount s usb/112568 usb [umass] [request] USB mode may wrong when mounting Pla o usb/112463 usb [umass] problem with Samsung USB DVD writer, libscg an o usb/112461 usb [ehci] [request] ehci USB 2.0 doesn't work on nforce4 o usb/111753 usb [uhid] [panic] Replicable system panic involving UHID s usb/110991 usb [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends o usb/110988 usb [umass] [patch] Handling of quirk IGNORE_RESIDUE is um o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC o usb/109397 usb [panic] on boot from USB flash o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr s usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/108056 usb [ohci] Mouse gets powered off during device probe when o usb/107935 usb [uplcom] [panic] panic while accessing /dev/cuaU0 o usb/107924 usb [patch] usbd(8) does not call detach o usb/107848 usb [umass] [request] cannot access Samsung flash disk o usb/107827 usb [ohci] [panic] ohci_add_done addr not found o usb/107496 usb [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [ o usb/107388 usb [patch] [request] new driver: add utoppy device from N o usb/107248 usb [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP o usb/107243 usb [cam] [patch] Apacer USB Flash Drive quirk o usb/106861 usb [usbdevs] [patch]: usbdevs update: Add product ACER Ze s usb/106832 usb [usb] USB HP printer is not detected by kernel when AC o usb/106648 usb [umass] [hang] USB Floppy on D1950 10 min Hang on Inse o usb/106621 usb [axe] [patch] DLINK DUB-E100 support broken o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106041 usb [usb] [request] FreeBSD does not recognise Mustek Bear o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/105186 usb [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c o usb/105065 usb [ata] [usb] SATA - USB Bridge o usb/104830 usb [umass] system crashes when copying data to umass devi o usb/104645 usb [umass] [request] Rave C-201 MP3 player does not commu o usb/104352 usb [ural] [patch] ural driver doesnt work o usb/104292 usb [umass] [hang] system lockup on forced umount of usb-s o usb/104290 usb [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto o usb/103917 usb [uhub] USB driver reports "Addr 0 should never happen" o usb/103418 usb usbhidctl(1): [patch] [request] usbhidctl: add ability o usb/103289 usb [request] USB 2.0 problems on AMD LX-800 CPU and CS-55 o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103025 usb [uhub] [panic] wrong detection of USB device for FreeB o usb/102976 usb [panic] Casio Exilim Digital Camera causes panic on in o usb/102678 usb [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/101761 usb [usb] [patch] [request] usb.h: increase maximal size o o usb/101752 usb [umass] [panic] 6.1-RELEASE kernel panic on usb device o usb/101448 usb [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O o usb/101096 usb [ural] [panic] USB WLAN occasionally causes kernel-pan o usb/100746 usb [keyboard] system does not boot due to USB keyboard pr o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar 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/93408 usb [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w 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 o 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/91629 usb [usb] usbd_abort_pipe() may result in infinite loop 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 f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US 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 f usb/83677 usb [usb] [request] usb controller often not detected (Sun 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/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu 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 " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, 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 o 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 o usb/75797 usb [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o 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 i386/46371 usb USB controller cannot be initialized on IBM Netfinity 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 307 problems total. From gavin at FreeBSD.org Mon Mar 23 06:13:31 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Mon Mar 23 06:13:37 2009 Subject: usb/132799: [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CACHE in its QUIRK Message-ID: <200903231313.n2NDDTGh091712@freefall.freebsd.org> Synopsis: [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CACHE in its QUIRK State-Changed-From-To: open->patched State-Changed-By: gavin State-Changed-When: Mon Mar 23 13:13:07 UTC 2009 State-Changed-Why: Patched in HEAD http://www.freebsd.org/cgi/query-pr.cgi?pr=132799 From meslists at yahoo.fr Mon Mar 23 09:04:24 2009 From: meslists at yahoo.fr (dan) Date: Mon Mar 23 09:04:30 2009 Subject: external DVD Rewriter Message-ID: <49C7AFFE.4060001@yahoo.fr> Hi ! I recently added an external LG dvd rewriter to a clean FreeBSD 7.1 installation. ------- umass0: on uhub3 cd0 at umass-sim0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device ------- As soon as I installed the xorg + gnome 2 ports these `odd` messages started to continuously appear in ttyv0 : ------- umass0: Unsupported ATAPI command 0x4a - trying anyway umass0: Unsupported ATAPI command 0x4a - trying anyway umass0: Unsupported ATAPI command 0x46 - trying anyway umass0: Unsupported ATAPI command 0x4a - trying anyway [....] umass0: Unsupported ATAPI command 0x4a - trying anyway [....] ------- After investigating a bit, I suppose these messages are a kind of an answer from the umass driver to HAL inquiries ( ... disabling HAL the messages disappear). the doubts and questions are: ...is the command really an unsupported command or is it a bug ? In case it is a bug, to whom should I fill in a PR ? Thank you ! dan From imp at bsdimp.com Mon Mar 23 09:47:07 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Mar 23 09:47:18 2009 Subject: external DVD Rewriter In-Reply-To: <49C7AFFE.4060001@yahoo.fr> References: <49C7AFFE.4060001@yahoo.fr> Message-ID: <20090323.104641.-75255559.imp@bsdimp.com> In message: <49C7AFFE.4060001@yahoo.fr> dan writes: : Hi ! : : I recently added an external LG dvd rewriter to a clean FreeBSD 7.1 : installation. : : ------- : umass0: on uhub3 : cd0 at umass-sim0 bus 0 target 0 lun 0 : cd0: Removable CD-ROM SCSI-0 device : ------- : : As soon as I installed the xorg + gnome 2 ports these `odd` messages : started to continuously appear in ttyv0 : : : ------- : umass0: Unsupported ATAPI command 0x4a - trying anyway : umass0: Unsupported ATAPI command 0x4a - trying anyway : umass0: Unsupported ATAPI command 0x46 - trying anyway : umass0: Unsupported ATAPI command 0x4a - trying anyway : [....] : umass0: Unsupported ATAPI command 0x4a - trying anyway : [....] : ------- : : After investigating a bit, I suppose these messages are a kind of an : answer from the umass driver to HAL inquiries ( ... disabling HAL the : messages disappear). : : the doubts and questions are: ...is the command really an unsupported : command or is it a bug ? : : In case it is a bug, to whom should I fill in a PR ? Old usb printed this warning because of history. Originally it was an error because the thumb drives were stupid POS at the time and any command that they didn't understand would take an error path that hung the device. Bad kharma. In time, I got tired of adding each new command so that my dvd burner would work, so I just said "screw it, this is a warning now, and if somebody's drive fraks up, then so be it: they will know what's going on at least. Besides, people that try to burn a CD/DVD on their 256MB flash drive don't need that much protection: bad things happening to them isn't necessarily bad." Usb in 8.0 I think eliminated the warning. Warner From marius at FreeBSD.org Mon Mar 23 14:15:52 2009 From: marius at FreeBSD.org (marius@FreeBSD.org) Date: Mon Mar 23 14:15:58 2009 Subject: usb/110988: [umass] [patch] Handling of quirk IGNORE_RESIDUE is umass.c is broken Message-ID: <200903232115.n2NLFpMA044057@freefall.freebsd.org> Synopsis: [umass] [patch] Handling of quirk IGNORE_RESIDUE is umass.c is broken State-Changed-From-To: open->closed State-Changed-By: marius State-Changed-When: Mon Mar 23 21:12:42 UTC 2009 State-Changed-Why: Close; IGNORE_RESIDUE was fixed as part of r189905 in head and in r190327 for stable/7. http://www.freebsd.org/cgi/query-pr.cgi?pr=110988 From marius at FreeBSD.org Mon Mar 23 14:19:58 2009 From: marius at FreeBSD.org (marius@FreeBSD.org) Date: Mon Mar 23 14:20:04 2009 Subject: usb/110991: [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends on usb/110988) Message-ID: <200903232119.n2NLJtWl044186@freefall.freebsd.org> Synopsis: [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends on usb/110988) State-Changed-From-To: suspended->closed State-Changed-By: marius State-Changed-When: Mon Mar 23 21:16:55 UTC 2009 State-Changed-Why: Close; a quirk for the Supertop IDE adapter was added in r189904, which was MFC'ed to stable/7 in r190311. http://www.freebsd.org/cgi/query-pr.cgi?pr=110991 From kamikaze at bsdforen.de Mon Mar 23 23:00:17 2009 From: kamikaze at bsdforen.de (Dominic Fandrey) Date: Mon Mar 23 23:00:24 2009 Subject: usb/122936: [ucom] [ubsa] Device does not receive interrupt Message-ID: <200903240600.n2O60Fwp051701@freefall.freebsd.org> The following reply was made to PR usb/122936; it has been noted by GNATS. From: Dominic Fandrey To: bug-followup@FreeBSD.org, kamikaze@bsdforen.de Cc: Subject: Re: usb/122936: [ucom] [ubsa] Device does not receive interrupt Date: Tue, 24 Mar 2009 06:59:40 +0100 U3G has made this not worth bothering. I suggest this be closed. Maybe strip support for the device from ubsa. It's just a lot more pleasant experience with u3g. From meslists at yahoo.fr Tue Mar 24 09:02:32 2009 From: meslists at yahoo.fr (dan) Date: Tue Mar 24 09:02:38 2009 Subject: external DVD Rewriter In-Reply-To: <20090323.104641.-75255559.imp@bsdimp.com> References: <49C7AFFE.4060001@yahoo.fr> <20090323.104641.-75255559.imp@bsdimp.com> Message-ID: <49C90409.8020308@yahoo.fr> Hi, thank you for the answer ! So, If I am not wrong, you are suggesting to forget about this warning and go on using the writer, right ? Hmmm ... I would be at least interested in understanding the nature of the problem, to be honest. And avoid that hundreds of these messages fill in the screen sometimes hiding important error messages :-) Any suggestion ? Thank you, dan M. Warner Losh wrote: > In message: <49C7AFFE.4060001@yahoo.fr> > dan writes: > : Hi ! > : > : I recently added an external LG dvd rewriter to a clean FreeBSD 7.1 > : installation. > : > : ------- > : umass0: on uhub3 > : cd0 at umass-sim0 bus 0 target 0 lun 0 > : cd0: Removable CD-ROM SCSI-0 device > : ------- > : > : As soon as I installed the xorg + gnome 2 ports these `odd` messages > : started to continuously appear in ttyv0 : > : > : ------- > : umass0: Unsupported ATAPI command 0x4a - trying anyway > : umass0: Unsupported ATAPI command 0x4a - trying anyway > : umass0: Unsupported ATAPI command 0x46 - trying anyway > : umass0: Unsupported ATAPI command 0x4a - trying anyway > : [....] > : umass0: Unsupported ATAPI command 0x4a - trying anyway > : [....] > : ------- > : > : After investigating a bit, I suppose these messages are a kind of an > : answer from the umass driver to HAL inquiries ( ... disabling HAL the > : messages disappear). > : > : the doubts and questions are: ...is the command really an unsupported > : command or is it a bug ? > : > : In case it is a bug, to whom should I fill in a PR ? > > Old usb printed this warning because of history. Originally it was an > error because the thumb drives were stupid POS at the time and any > command that they didn't understand would take an error path that hung > the device. Bad kharma. In time, I got tired of adding each new > command so that my dvd burner would work, so I just said "screw it, > this is a warning now, and if somebody's drive fraks up, then so be > it: they will know what's going on at least. Besides, people that try > to burn a CD/DVD on their 256MB flash drive don't need that much > protection: bad things happening to them isn't necessarily bad." > > Usb in 8.0 I think eliminated the warning. > > Warner > > From imp at bsdimp.com Tue Mar 24 09:32:33 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Tue Mar 24 09:32:43 2009 Subject: external DVD Rewriter In-Reply-To: <49C90409.8020308@yahoo.fr> References: <49C7AFFE.4060001@yahoo.fr> <20090323.104641.-75255559.imp@bsdimp.com> <49C90409.8020308@yahoo.fr> Message-ID: <20090324.103138.1359520009.imp@bsdimp.com> In message: <49C90409.8020308@yahoo.fr> dan writes: : Hi, thank you for the answer ! : : So, If I am not wrong, you are suggesting to forget about this warning : and go on using the writer, right ? If it works, yes. Don't worry. Be happy! : Hmmm ... I would be at least interested in understanding the nature of : the problem, to be honest. And avoid that hundreds of these messages : fill in the screen sometimes hiding important error messages :-) The problem is with old Flash memory sticks. They wedge hard when certain commands are sent to them. The original filter was put in place to ensure a strict compliance to one of the scsi subsets that was used for the flash sticks. However, it caught more than just memory sticks in its net. so when the burning software sends the commands to query the state of the disk, set the burn speed, etc, you'll see these commands appear in the logs. : Any suggestion ? Did that help? Warner : Thank you, : : dan : : : M. Warner Losh wrote: : > In message: <49C7AFFE.4060001@yahoo.fr> : > dan writes: : > : Hi ! : > : : > : I recently added an external LG dvd rewriter to a clean FreeBSD 7.1 : > : installation. : > : : > : ------- : > : umass0: on uhub3 : > : cd0 at umass-sim0 bus 0 target 0 lun 0 : > : cd0: Removable CD-ROM SCSI-0 device : > : ------- : > : : > : As soon as I installed the xorg + gnome 2 ports these `odd` messages : > : started to continuously appear in ttyv0 : : > : : > : ------- : > : umass0: Unsupported ATAPI command 0x4a - trying anyway : > : umass0: Unsupported ATAPI command 0x4a - trying anyway : > : umass0: Unsupported ATAPI command 0x46 - trying anyway : > : umass0: Unsupported ATAPI command 0x4a - trying anyway : > : [....] : > : umass0: Unsupported ATAPI command 0x4a - trying anyway : > : [....] : > : ------- : > : : > : After investigating a bit, I suppose these messages are a kind of an : > : answer from the umass driver to HAL inquiries ( ... disabling HAL the : > : messages disappear). : > : : > : the doubts and questions are: ...is the command really an unsupported : > : command or is it a bug ? : > : : > : In case it is a bug, to whom should I fill in a PR ? : > : > Old usb printed this warning because of history. Originally it was an : > error because the thumb drives were stupid POS at the time and any : > command that they didn't understand would take an error path that hung : > the device. Bad kharma. In time, I got tired of adding each new : > command so that my dvd burner would work, so I just said "screw it, : > this is a warning now, and if somebody's drive fraks up, then so be : > it: they will know what's going on at least. Besides, people that try : > to burn a CD/DVD on their 256MB flash drive don't need that much : > protection: bad things happening to them isn't necessarily bad." : > : > Usb in 8.0 I think eliminated the warning. : > : > Warner : > : > : : : From weongyo.jeong at gmail.com Wed Mar 25 02:18:02 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Wed Mar 25 02:18:13 2009 Subject: q: Memory modified after free in usb2 Message-ID: <20090325091756.GA14916@weongyo.cdnetworks.kr> Hello Hans :), I think porting uath(4) to usb almost have done that it works well to associate with AP and for WPA but I'm suffered from a strange panic after detach as follows: Memory modified after free 0xc4da3600(508) val=24000000 @ 0xc4da3600 panic: Most recently used by USBdev cpuid = 0 KDB: enter: panic [thread pid 17 tid 100036 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why The detach step is like as follows: usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); ... uath_free_rx_data_list(sc); uath_free_tx_data_list(sc); uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); that I've checked all memory leaks or calls after freeing memory but it looks it's not a driver problem. To solve this problem I modified codes slightly like below: usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); usb2_pause_mtx(NULL, 5 * hz); ... uath_free_rx_data_list(sc); uath_free_tx_data_list(sc); uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); After adding it I couldn't see `Memory modified after free' messages anymore. My question is that I can't understand why adding usb2_pause_mtx() helps this symptom? regards, Weongyo Jeong From hselasky at c2i.net Wed Mar 25 02:44:27 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Mar 25 02:44:34 2009 Subject: q: Memory modified after free in usb2 In-Reply-To: <20090325091756.GA14916@weongyo.cdnetworks.kr> References: <20090325091756.GA14916@weongyo.cdnetworks.kr> Message-ID: <200903251046.55586.hselasky@c2i.net> On Wednesday 25 March 2009, Weongyo Jeong wrote: > Hello Hans :), > > I think porting uath(4) to usb almost have done that it works well to > associate with AP and for WPA but I'm suffered from a strange panic after > detach as follows: > > Memory modified after free 0xc4da3600(508) val=24000000 @ 0xc4da3600 > panic: Most recently used by USBdev > > cpuid = 0 > KDB: enter: panic > [thread pid 17 tid 100036 ] > Stopped at kdb_enter+0x3a: movl $0,kdb_why > > The detach step is like as follows: > > usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); > ... > uath_free_rx_data_list(sc); > uath_free_tx_data_list(sc); > uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); > > that I've checked all memory leaks or calls after freeing memory but it > looks it's not a driver problem. > > To solve this problem I modified codes slightly like below: > > usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); > usb2_pause_mtx(NULL, 5 * hz); > ... > uath_free_rx_data_list(sc); > uath_free_tx_data_list(sc); > uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); > > After adding it I couldn't see `Memory modified after free' messages > anymore. My question is that I can't understand why adding > usb2_pause_mtx() helps this symptom? Did you drain all the taskqueues before unsetup ? --HPS From brucec at FreeBSD.org Wed Mar 25 10:47:39 2009 From: brucec at FreeBSD.org (brucec@FreeBSD.org) Date: Wed Mar 25 10:47:50 2009 Subject: kern/99200: [bluetooth] SMP-Kernel crashes reliably when Bluetooth connection speeds up Message-ID: <200903251747.n2PHlXn0046095@freefall.freebsd.org> Synopsis: [bluetooth] SMP-Kernel crashes reliably when Bluetooth connection speeds up Responsible-Changed-From-To: freebsd-bugs->freebsd-usb Responsible-Changed-By: brucec Responsible-Changed-When: Wed Mar 25 17:46:56 UTC 2009 Responsible-Changed-Why: Looks like a usb bug. http://www.freebsd.org/cgi/query-pr.cgi?pr=99200 From weongyo.jeong at gmail.com Wed Mar 25 18:49:43 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Wed Mar 25 18:49:49 2009 Subject: q: Memory modified after free in usb2 In-Reply-To: <200903251046.55586.hselasky@c2i.net> References: <20090325091756.GA14916@weongyo.cdnetworks.kr> <200903251046.55586.hselasky@c2i.net> Message-ID: <20090326014938.GB14916@weongyo.cdnetworks.kr> On Wed, Mar 25, 2009 at 10:46:54AM +0100, Hans Petter Selasky wrote: > On Wednesday 25 March 2009, Weongyo Jeong wrote: > > Hello Hans :), > > > > I think porting uath(4) to usb almost have done that it works well to > > associate with AP and for WPA but I'm suffered from a strange panic after > > detach as follows: > > > > Memory modified after free 0xc4da3600(508) val=24000000 @ 0xc4da3600 > > panic: Most recently used by USBdev > > > > cpuid = 0 > > KDB: enter: panic > > [thread pid 17 tid 100036 ] > > Stopped at kdb_enter+0x3a: movl $0,kdb_why > > > > The detach step is like as follows: > > > > usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); > > ... > > uath_free_rx_data_list(sc); > > uath_free_tx_data_list(sc); > > uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); > > > > that I've checked all memory leaks or calls after freeing memory but it > > looks it's not a driver problem. > > > > To solve this problem I modified codes slightly like below: > > > > usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); > > usb2_pause_mtx(NULL, 5 * hz); > > ... > > uath_free_rx_data_list(sc); > > uath_free_tx_data_list(sc); > > uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); > > > > After adding it I couldn't see `Memory modified after free' messages > > anymore. My question is that I can't understand why adding > > usb2_pause_mtx() helps this symptom? > > Did you drain all the taskqueues before unsetup ? Yes. All I used was two callouts that the driver currently doesn't use usb2_proc_create() and tried to drain its before calling usb2_transfer_unsetup() but it still encounters `Memory modified after free'. regards, Weongyo Jeong From weongyo.jeong at gmail.com Thu Mar 26 00:36:23 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Thu Mar 26 00:36:30 2009 Subject: q: Memory modified after free in usb2 In-Reply-To: <200903251046.55586.hselasky@c2i.net> References: <20090325091756.GA14916@weongyo.cdnetworks.kr> <200903251046.55586.hselasky@c2i.net> Message-ID: <20090326073616.GA20088@weongyo.cdnetworks.kr> On Wed, Mar 25, 2009 at 10:46:54AM +0100, Hans Petter Selasky wrote: > On Wednesday 25 March 2009, Weongyo Jeong wrote: > > Hello Hans :), > > > > I think porting uath(4) to usb almost have done that it works well to > > associate with AP and for WPA but I'm suffered from a strange panic after > > detach as follows: > > > > Memory modified after free 0xc4da3600(508) val=24000000 @ 0xc4da3600 > > panic: Most recently used by USBdev > > > > cpuid = 0 > > KDB: enter: panic > > [thread pid 17 tid 100036 ] > > Stopped at kdb_enter+0x3a: movl $0,kdb_why > > > > The detach step is like as follows: > > > > usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); > > ... > > uath_free_rx_data_list(sc); > > uath_free_tx_data_list(sc); > > uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); > > > > that I've checked all memory leaks or calls after freeing memory but it > > looks it's not a driver problem. > > > > To solve this problem I modified codes slightly like below: > > > > usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); > > usb2_pause_mtx(NULL, 5 * hz); > > ... > > uath_free_rx_data_list(sc); > > uath_free_tx_data_list(sc); > > uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); > > > > After adding it I couldn't see `Memory modified after free' messages > > anymore. My question is that I can't understand why adding > > usb2_pause_mtx() helps this symptom? > > Did you drain all the taskqueues before unsetup ? It looks I found a problem that some tasks running by net80211 causes this problem. It looks calling usb2_transfer_unsetup() after ieee80211_ifdetach(ic) solves the problem. Thanks! regards, Weongyo Jeong From hselasky at c2i.net Thu Mar 26 00:59:36 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Mar 26 00:59:44 2009 Subject: q: Memory modified after free in usb2 In-Reply-To: <20090326014938.GB14916@weongyo.cdnetworks.kr> References: <20090325091756.GA14916@weongyo.cdnetworks.kr> <200903251046.55586.hselasky@c2i.net> <20090326014938.GB14916@weongyo.cdnetworks.kr> Message-ID: <200903260902.04274.hselasky@c2i.net> On Thursday 26 March 2009, Weongyo Jeong wrote: > On Wed, Mar 25, 2009 at 10:46:54AM +0100, Hans Petter Selasky wrote: > > > To solve this problem I modified codes slightly like below: > > > > > > usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); > > > usb2_pause_mtx(NULL, 5 * hz); > > > ... > > > uath_free_rx_data_list(sc); > > > uath_free_tx_data_list(sc); > > > uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); > > > > > > After adding it I couldn't see `Memory modified after free' messages > > > anymore. My question is that I can't understand why adding > > > usb2_pause_mtx() helps this symptom? > > > > Did you drain all the taskqueues before unsetup ? > > Yes. All I used was two callouts that the driver currently doesn't use > usb2_proc_create() and tried to drain its before calling > usb2_transfer_unsetup() but it still encounters `Memory modified after > free'. Hi, Is this the link to the complete code? http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/usb/wlan/if_uath.c&REV=24 1) The manpage states: "This function MUST NOT be called while holding any locks ..." | UATH_LOCK(sc); | callout_drain(&sc->stat_ch); | callout_drain(&sc->watchdog_ch); 505: 159831 21 | UATH_UNLOCK(sc); callout_stop() is not callout_drain() ! Same sematics with USB2. transfer_stop()/transfer_drain() 2) Instead of copying the data twice, use the .ext_buffer=1 flag to instruct USB to not allocate its own buffer in "struct usb2_config", see "umass.c" for example, and the and usb2_set_frame_data(xfer, urb->transfer_buffer, 0); Before you start the hardware! Actually you can save alot of copying if you can exploit the multi-frame feature of the USB-stack for BULK transfers! Then you have to set "frames > 1" in usb2_config structure. For example you would then copy in the header to wMaxPacketSize bytes, and use the data pointer for the rest, given that the IP-packet is not that defragged. 3) There is a chicken egg problem at detach. I suspect that "uath_bulk_tx_callback()" is called with the USB_ERR_CANCELLED error. And here you seem to access freed memory. I think you need to re-think how you get that last node freed. Maybe it should be done by the if_stop() and not at cancelled, because according to detach, you will do if_stop() first and then cancel USB and unless you drain, you are not certain that the callback is complete! | default: | data = STAILQ_FIRST(&sc->sc_datatx_active); | if (data == NULL) | goto setup; 2605: 159735 3 | if (data->ni != NULL) { | ieee80211_free_node(data->ni); | data->ni = NULL; | ifp->if_oerrors++; | } 2610: 159733 1 | if (xfer->error != USB_ERR_CANCELLED) { | xfer->flags.stall_pipe = 1; | goto setup; | } I recommend that you do the usb2_transfer_unsetup() first at detach like in if_rum.c and the other WLAN drivers. That will solve your problem, and maybe you have to fix the datatx_active queue, so that the last "data" is not stuck there for ever ??? --HPS From gavin at FreeBSD.org Thu Mar 26 06:41:29 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Thu Mar 26 06:41:35 2009 Subject: usb/120017: [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk Message-ID: <200903261341.n2QDfTeP076917@freefall.freebsd.org> Synopsis: [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk State-Changed-From-To: open->closed State-Changed-By: gavin State-Changed-When: Thu Mar 26 13:40:14 UTC 2009 State-Changed-Why: Fixed in HEAD and MFC'd http://www.freebsd.org/cgi/query-pr.cgi?pr=120017 From sam at freebsd.org Thu Mar 26 09:46:08 2009 From: sam at freebsd.org (Sam Leffler) Date: Thu Mar 26 09:46:14 2009 Subject: q: Memory modified after free in usb2 In-Reply-To: <20090326073616.GA20088@weongyo.cdnetworks.kr> References: <20090325091756.GA14916@weongyo.cdnetworks.kr> <200903251046.55586.hselasky@c2i.net> <20090326073616.GA20088@weongyo.cdnetworks.kr> Message-ID: <49CBAEB1.6080304@freebsd.org> Weongyo Jeong wrote: > On Wed, Mar 25, 2009 at 10:46:54AM +0100, Hans Petter Selasky wrote: > >> On Wednesday 25 March 2009, Weongyo Jeong wrote: >> >>> Hello Hans :), >>> >>> I think porting uath(4) to usb almost have done that it works well to >>> associate with AP and for WPA but I'm suffered from a strange panic after >>> detach as follows: >>> >>> Memory modified after free 0xc4da3600(508) val=24000000 @ 0xc4da3600 >>> panic: Most recently used by USBdev >>> >>> cpuid = 0 >>> KDB: enter: panic >>> [thread pid 17 tid 100036 ] >>> Stopped at kdb_enter+0x3a: movl $0,kdb_why >>> >>> The detach step is like as follows: >>> >>> usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); >>> ... >>> uath_free_rx_data_list(sc); >>> uath_free_tx_data_list(sc); >>> uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); >>> >>> that I've checked all memory leaks or calls after freeing memory but it >>> looks it's not a driver problem. >>> >>> To solve this problem I modified codes slightly like below: >>> >>> usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); >>> usb2_pause_mtx(NULL, 5 * hz); >>> ... >>> uath_free_rx_data_list(sc); >>> uath_free_tx_data_list(sc); >>> uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); >>> >>> After adding it I couldn't see `Memory modified after free' messages >>> anymore. My question is that I can't understand why adding >>> usb2_pause_mtx() helps this symptom? >>> >> Did you drain all the taskqueues before unsetup ? >> > > It looks I found a problem that some tasks running by net80211 causes > this problem. It looks calling usb2_transfer_unsetup() after > ieee80211_ifdetach(ic) solves the problem. Thanks! > ieee80211_ifdetach may call back into the driver (e.g. if you're associated in sta mode and the state machine wants to notify the ap to disassociate). Reordering the calls is the right thing to do. Sam From weongyo.jeong at gmail.com Thu Mar 26 18:59:52 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Thu Mar 26 18:59:59 2009 Subject: q: Memory modified after free in usb2 In-Reply-To: <200903260902.04274.hselasky@c2i.net> References: <20090325091756.GA14916@weongyo.cdnetworks.kr> <200903251046.55586.hselasky@c2i.net> <20090326014938.GB14916@weongyo.cdnetworks.kr> <200903260902.04274.hselasky@c2i.net> Message-ID: <20090327015945.GB19512@weongyo.cdnetworks.kr> On Thu, Mar 26, 2009 at 09:02:02AM +0100, Hans Petter Selasky wrote: > On Thursday 26 March 2009, Weongyo Jeong wrote: > > On Wed, Mar 25, 2009 at 10:46:54AM +0100, Hans Petter Selasky wrote: > > > > > To solve this problem I modified codes slightly like below: > > > > > > > > usb2_transfer_unsetup(sc->sc_xfer, UATH_N_XFERS); > > > > usb2_pause_mtx(NULL, 5 * hz); > > > > ... > > > > uath_free_rx_data_list(sc); > > > > uath_free_tx_data_list(sc); > > > > uath_free_cmd_list(sc, sc->sc_cmd, UATH_CMD_LIST_COUNT); > > > > > > > > After adding it I couldn't see `Memory modified after free' messages > > > > anymore. My question is that I can't understand why adding > > > > usb2_pause_mtx() helps this symptom? > > > > > > Did you drain all the taskqueues before unsetup ? > > > > Yes. All I used was two callouts that the driver currently doesn't use > > usb2_proc_create() and tried to drain its before calling > > usb2_transfer_unsetup() but it still encounters `Memory modified after > > free'. > > Hi, > > Is this the link to the complete code? > > http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/usb/wlan/if_uath.c&REV=24 Yes. > 1) The manpage states: "This function MUST NOT be called while holding any > locks ..." > | UATH_LOCK(sc); > | callout_drain(&sc->stat_ch); > | callout_drain(&sc->watchdog_ch); > 505: 159831 21 | UATH_UNLOCK(sc); > > > callout_stop() is not callout_drain() ! > > Same sematics with USB2. transfer_stop()/transfer_drain() It looks it's my mistake to lock before going into callout_drain(9). > 2) Instead of copying the data twice, use the .ext_buffer=1 flag to instruct > USB to not allocate its own buffer in "struct usb2_config", see "umass.c" for > example, and the and > usb2_set_frame_data(xfer, > urb->transfer_buffer, 0); > > Before you start the hardware! > > Actually you can save alot of copying if you can exploit the multi-frame > feature of the USB-stack for BULK transfers! Then you have to set "frames > > 1" in usb2_config structure. For example you would then copy in the header to > wMaxPacketSize bytes, and use the data pointer for the rest, given that the > IP-packet is not that defragged. This is what I want! I'll apply it immediately. Thanks! :-) > 3) There is a chicken egg problem at detach. > > I suspect that "uath_bulk_tx_callback()" is called with the USB_ERR_CANCELLED > error. And here you seem to access freed memory. I think you need to re-think > how you get that last node freed. Maybe it should be done by the if_stop() > and not at cancelled, because according to detach, you will do if_stop() > first and then cancel USB and unless you drain, you are not certain that the > callback is complete! > > | default: > | data = STAILQ_FIRST(&sc->sc_datatx_active); > | if (data == NULL) > | goto setup; > 2605: 159735 3 | if (data->ni != NULL) { > | ieee80211_free_node(data->ni); > | data->ni = NULL; > | ifp->if_oerrors++; > | } > 2610: 159733 1 | if (xfer->error != USB_ERR_CANCELLED) { > | xfer->flags.stall_pipe = 1; > | goto setup; > | } > > I recommend that you do the usb2_transfer_unsetup() first at detach like in > if_rum.c and the other WLAN drivers. That will solve your problem, and maybe > you have to fix the datatx_active queue, so that the last "data" is not stuck > there for ever ??? Thank you for advice again. I'll try to do some more tests. It looks ordering is important when detaching and with looking other WLAN drivers it seems calling ieee80211_ifdetach(ic) should be moved before usb2_transfer_unsetup(9) including if_zyd.c, if_ural.c and if_ral.c regards, Weongyo Jeong From weongyo.jeong at gmail.com Thu Mar 26 19:29:08 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Thu Mar 26 19:29:14 2009 Subject: q: a trivial question of usb2_transfer_unsetup() Message-ID: <20090327022902.GC19512@weongyo.cdnetworks.kr> Hello Hans, I have a simple question that is there a possibility for .mh.callback of usb2_config to be called after usb2_transfer_unsetup()? regards, Weongyo Jeong From hselasky at c2i.net Fri Mar 27 00:34:26 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Mar 27 00:34:34 2009 Subject: q: a trivial question of usb2_transfer_unsetup() In-Reply-To: <20090327022902.GC19512@weongyo.cdnetworks.kr> References: <20090327022902.GC19512@weongyo.cdnetworks.kr> Message-ID: <200903270836.55005.hselasky@c2i.net> On Friday 27 March 2009, Weongyo Jeong wrote: > Hello Hans, > > I have a simple question that is there a possibility for .mh.callback of > usb2_config to be called after usb2_transfer_unsetup()? Hi, usb2_transfer_unsetup() calls usb2_transfer_drain() which ensures that the callback has exited before returning. Even if you drop the private transfer lock in the callback and pick it up before returning. --HPS From thompsa at FreeBSD.org Fri Mar 27 11:27:47 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Fri Mar 27 11:28:59 2009 Subject: Proposed USB data buffer changes Message-ID: <20090327182740.GB26662@citylink.fud.org.nz> Hi, I want the USB peripheral driver API to be solid before 8.0 so things dont bite us down the line. I have discussed this privately with Hans already and want to put it out for public consumption. With the new USB code the buffer management has been merged into the xfer structure and this dictates the layout of the usb drivers and how locking is performed. This uses a state machine (my attempt to show below) |-< |-< XFER <-| <-| | | | | --------- callback_fn --------- | | | | | -> SETUP (copyin) >-| | | | -> COMPLETE (copyout) >-| It can take an external buffer instead of the copyin/out but it doesnt really simplify things at all. The problems I see with this approach are 1. It is in contrast to other major operating systems, making porting drivers harder. Windows, Linux and oldUSB all use a URB style of data handling. 2. It greatly complicates locking as the xfer lock can not be dropped until the xfer is resubmitted. This requirement to hold the lock creates a big problem for get/put of data to another layer (eg TTY), to avoid lock order reversals the drivers are generally written to share the lock with the lower/upper layer (eg TTY). 3. In the general case data can not be directly queued on the xfer (must be "picked" up by the state machine callback). This limits the options for designing a driver and may require the driver to implement a queue. I think its vital that we separate out the data buffers from the xfer (its actually a pipe in usb speak). It should draw from the Linux API which is simple and I believe works quite well. The data buffer is represented as a usb URB which is allocated either at attach or on the fly and then queued on the xfer (pipe) for processing. An arbitrary number of URB buffers can be on the queue. As the buffer would only have a single reference it would not need explicit locking, the callback would not need the xfer lock to be held at all and this would make it _much_ easier to handoff the data without LOR. This reduction in locking means that the driver and the xfer do not need to share a lock either, something that is mandatory now. The xfer can have a private lock for enqueue/start/stop. Example functions could be, usb_alloc_urb - Creates a URB representing data and housekeeping, the data section can be allocated or passed in from say a mbuf. This can also perform the DMA foo. usb_submit_urb - Queues the URB on the usb pipe. I dont think this would take much work. The xfer callbacks would be changed to take a URB and a few changes to queuing. It was mentioned the reason for this approach was to preallocate and do DMA setup on attach but this can still easily be done with the above. Comments? cheers, Andrew From mike at sentex.net Fri Mar 27 14:27:23 2009 From: mike at sentex.net (Mike Tancsa) Date: Fri Mar 27 14:27:29 2009 Subject: u3g panic Message-ID: <200903272126.n2RLQjIe052544@lava.sentex.ca> Hi, I was trying the u3g driver in FreeBSD on RELENG_7. The previous version from the webpage seemed to work ok, but the one MFC'd causes a panic if I load the driver and attach the stick Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xc fault code = supervisor read, page not present instruction pointer = 0x20:0xc357d71f stack pointer = 0x28:0xc2fccbc0 frame pointer = 0x28:0xc2fccbf4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 26 (irq19: uhci1) trap number = 12 panic: page fault cpuid = 0 Uptime: 2m39s Physical memory: 498 MB Dumping 42 MB: 27 11 (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc07198b7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc0719b89 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc09e495c in trap_fatal (frame=0xc2fccb80, eva=12) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc09e4be0 in trap_pfault (frame=0xc2fccb80, usermode=0, eva=12) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc09e558c in trap (frame=0xc2fccb80) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc09c9c6b in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc357d71f in u3gstub_BBB_cb (xfer=0xc3578600, priv=0x0, err=USBD_NORMAL_COMPLETION) at /usr/src/sys/modules/u3g/../../dev/usb/u3g.c:475 #8 0xc06950d5 in usb_transfer_complete (xfer=0xc3578600) at /usr/src/sys/dev/usb/usbdi.c:979 #9 0xc06879bb in uhci_transfer_complete (xfer=0xc3578600) at /usr/src/sys/dev/usb/uhci.c:2109 #10 0xc0687b07 in uhci_idone (ii=Variable "ii" is not available. ) at /usr/src/sys/dev/usb/uhci.c:1449 #11 0xc068800d in uhci_softintr (v=0xc319a000) at /usr/src/sys/dev/usb/uhci.c:1324 #12 0xc0690c72 in usb_schedsoftintr (bus=0xc319a000) at /usr/src/sys/dev/usb/usb.c:844 #13 0xc0688ce3 in uhci_intr1 (sc=0xc319a000) at /usr/src/sys/dev/usb/uhci.c:1224 #14 0xc0688fad in uhci_intr (arg=0xc319a000) at /usr/src/sys/dev/usb/uhci.c:1139 #15 0xc06f781b in ithread_loop (arg=0xc31a4000) at /usr/src/sys/kern/kern_intr.c:1088 #16 0xc06f4369 in fork_exit (callout=0xc06f7660 , arg=0xc31a4000, frame=0xc2fccd38) at /usr/src/sys/kern/kern_fork.c:810 #17 0xc09c9ce0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 (kgdb) On CURRENT, it shows and seems to work fine. Root mount waiting for: usbus1 ugen0.2: at usbus0 u3g0: on usbus0 u3g0: Found 2 ports. 0[freebsd-current2]# usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON 0[freebsd-current2]# cu -l /dev/cuaU0.0 Connected ati Manufacturer: Novatel Wireless Incorporated Model: Ovation MC950D Card Revision: 3.15.02.0-00 [2008-03-04 09:19:50] IMEI: 356846015465400 +GCAP: +CGSM,+DS,+ES OK -------------------------------------------------------------------- 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 c.r.n.a at wanadoo.fr Sat Mar 28 00:49:08 2009 From: c.r.n.a at wanadoo.fr (Nicolas) Date: Sat Mar 28 00:49:14 2009 Subject: "Big Problem" with removable media Message-ID: <49C2627A.9070806@wanadoo.fr> Hi, I'm using FreeBSD 8-Current (as of today) and when i plug my samsung omnia, i have this message: ugen7.7: at usbus7 umass1: on usbus7 umass1: SCSI over Bulk-Only; quirks = 0x0000 umass1:3:1:-1: Attached to scbus3 da1 at umass-sim1 bus 1 target 0 lun 0 da1: < > Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: 7680MB (15728640 512 byte sectors: 255H 63S/T 979C) GEOM: da1: partition 1 does not start on a track boundary. GEOM: da1: partition 1 does not end on a track boundary. (da1:umass-sim1:1:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 My computer frezees until i unplug the device. What's wrong ? Thanks in advance, Niko. From hselasky at c2i.net Sat Mar 28 01:06:02 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Sat Mar 28 01:06:09 2009 Subject: "Big Problem" with removable media In-Reply-To: <49C2627A.9070806@wanadoo.fr> References: <49C2627A.9070806@wanadoo.fr> Message-ID: <200903280908.30647.hselasky@c2i.net> On Thursday 19 March 2009, Nicolas wrote: > Hi, > > I'm using FreeBSD 8-Current (as of today) and when i plug my samsung > omnia, i have this message: > > ugen7.7: at usbus7 > umass1: on usbus7 > umass1: SCSI over Bulk-Only; quirks = 0x0000 > umass1:3:1:-1: Attached to scbus3 > da1 at umass-sim1 bus 1 target 0 lun 0 > da1: < > Removable Direct Access SCSI-0 device > da1: 40.000MB/s transfers > da1: 7680MB (15728640 512 byte sectors: 255H 63S/T 979C) > GEOM: da1: partition 1 does not start on a track boundary. > GEOM: da1: partition 1 does not end on a track boundary. > (da1:umass-sim1:1:0:0): Synchronize cache failed, status == 0x4, scsi > status == 0x0 You need a quirk for your mass storage device. See previous postings by Luigi Rizzo. > > My computer frezees until i unplug the device. > What's wrong ? Ask PHK, probably a GEOM issue. --HPS > > Thanks in advance, > Niko. > > _______________________________________________ > 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" From phk at phk.freebsd.dk Sat Mar 28 13:44:28 2009 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Sat Mar 28 13:44:35 2009 Subject: "Big Problem" with removable media In-Reply-To: Your message of "Sat, 28 Mar 2009 09:08:29 +0100." <200903280908.30647.hselasky@c2i.net> Message-ID: <11408.1238272005@critter.freebsd.dk> In message <200903280908.30647.hselasky@c2i.net>, Hans Petter Selasky writes: >> My computer frezees until i unplug the device. >> What's wrong ? > >Ask PHK, probably a GEOM issue. The device driver fails to return an I/O request. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From brucec at FreeBSD.org Sat Mar 28 17:24:09 2009 From: brucec at FreeBSD.org (brucec@FreeBSD.org) Date: Sat Mar 28 17:24:15 2009 Subject: usb/129964: [newusb] disconnection of ugen devices isn't logged Message-ID: <200903290024.n2T0O9SO065802@freefall.freebsd.org> Synopsis: [newusb] disconnection of ugen devices isn't logged State-Changed-From-To: open->closed State-Changed-By: brucec State-Changed-When: Sun Mar 29 00:23:44 UTC 2009 State-Changed-Why: Fixed in -current. http://www.freebsd.org/cgi/query-pr.cgi?pr=129964 From brucec at FreeBSD.org Sat Mar 28 17:24:52 2009 From: brucec at FreeBSD.org (brucec@FreeBSD.org) Date: Sat Mar 28 17:24:58 2009 Subject: bin/129963: [newusb] usbconfig(8) fails with misleading error when run as a normal user Message-ID: <200903290024.n2T0Oq9b065851@freefall.freebsd.org> Synopsis: [newusb] usbconfig(8) fails with misleading error when run as a normal user State-Changed-From-To: open->closed State-Changed-By: brucec State-Changed-When: Sun Mar 29 00:24:34 UTC 2009 State-Changed-Why: Fixed in -current. http://www.freebsd.org/cgi/query-pr.cgi?pr=129963 From c.r.n.a at wanadoo.fr Sun Mar 29 03:10:57 2009 From: c.r.n.a at wanadoo.fr (Nicolas) Date: Sun Mar 29 03:11:04 2009 Subject: USB Video Class support Message-ID: <49CF48C3.7050904@wanadoo.fr> Hi, Someone knows if a person works on usb video class driver ? Thanks in advance, Nicolas. From henry.hu.sh at gmail.com Sun Mar 29 09:06:16 2009 From: henry.hu.sh at gmail.com (Henry Hu) Date: Sun Mar 29 09:06:26 2009 Subject: USB Video Class support In-Reply-To: <49CF48C3.7050904@wanadoo.fr> References: <49CF48C3.7050904@wanadoo.fr> Message-ID: <53a1e0710903290840n456c0281g5dcaf536581837da@mail.gmail.com> I tried to port netbsd driver, and I found that the version in cvs depends on the high speed ehci transfer, which someone submitted a patch for FreeBSD to one maillist but not committed. I applied the patch and got a kernel panic when the usb transfer starts. Maybe it would be good to do this after USB2 is merged from current?.... Cheers, Henry On Sun, Mar 29, 2009 at 6:09 PM, Nicolas wrote: > Hi, > > Someone knows if a person works on usb video class driver ? > > Thanks in advance, > Nicolas. > > _______________________________________________ > freebsd-multimedia@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia > To unsubscribe, send any mail to > "freebsd-multimedia-unsubscribe@freebsd.org" > From mrechberger at gmail.com Sun Mar 29 09:09:51 2009 From: mrechberger at gmail.com (Markus Rechberger) Date: Sun Mar 29 09:09:58 2009 Subject: USB Video Class support In-Reply-To: <53a1e0710903290840n456c0281g5dcaf536581837da@mail.gmail.com> References: <49CF48C3.7050904@wanadoo.fr> <53a1e0710903290840n456c0281g5dcaf536581837da@mail.gmail.com> Message-ID: Hi, On Sun, Mar 29, 2009 at 5:40 PM, Henry Hu wrote: > I tried to port netbsd driver, and I found that the version in cvs > depends on the high speed ehci transfer, which someone submitted a > patch for FreeBSD to one maillist but not committed. I applied the > patch and got a kernel panic when the usb transfer starts. > Maybe it would be good to do this after USB2 is merged from current?.... > I'm about to kick off a portable framework for those media drivers, the code is currently disclosed to interested people only. http://mcentral.de/wiki/index.php5/DVBConfigFramework so if anyone is interested to join it just let me know.. Markus From c.r.n.a at wanadoo.fr Sun Mar 29 11:42:09 2009 From: c.r.n.a at wanadoo.fr (Nicolas) Date: Sun Mar 29 11:42:22 2009 Subject: USB Video Class support References: 49CF48C3.7050904@wanadoo.fr Message-ID: <49CFB60A.3000809@wanadoo.fr> Hi Henry, Thanks for your response ! Could you send me your patch ? I'm using FreeBSD 8 Current and i want to test it if it's possible. Thanks in advance. Nicolas. From bugmaster at FreeBSD.org Mon Mar 30 04:07:03 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Mar 30 04:09:33 2009 Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org Message-ID: <200903301107.n2UB71mg054937@freefall.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 -------------------------------------------------------------------------------- p usb/132799 usb [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CA o usb/132785 usb [usb] [patch] Gemtech remote powersocket is classed as o usb/132594 usb USB subsystem causes page fault and crashes o usb/132312 usb Xorg 7.4 halts USB controller o usb/132080 usb [patch] [usb] Kernel panic after NOMEM caused by rum 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/131912 usb [uslcom] [patch] New devices using Silicon Labs chips o usb/131900 usb [usbdevs] [patch] Additional product identification co 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 f usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk 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/130325 usb [usb] [patch] fix tools/tools/usb/print-usb-if-vids.sh 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 [newusb] DVD drive detects as 'da' device o docs/129962 usb [newusb] usbconfig(8) refers to non-existant usb2_core o usb/129945 usb [usbdevs] [patch] add u3g support for Longcheer WM66 U o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [patch] add support for ZTE AC8700 modem o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [patch] Liebert UPS being assigned uhid and o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb] [patch] uaudio is not full duplex o 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 f usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup o usb/127549 usb [umass] [patch] Meizu MiniPlayer M6 (SL) requires some s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127423 usb [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr o usb/127342 usb [boot] cannot enable usb keyboard and mouse support in o kern/127222 usb [ohci]: Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c f 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/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if 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/125264 usb [patch] sysctl for set usb mouse rate (very useful for 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 o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work 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/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 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/122621 usb [patch] [request] New driver for Sierra Wireless 3G US 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/122025 usb [uscanner] [patch] uscanner does not attach to Epson R 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/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] FreeBSD fails to boot with usb legacy support e 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 [umass] [patch] quirk to support ASUS P535 as umass (a 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/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab 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/118686 usb [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround 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 [uaudio] [patch] Not possible to record with Plantroni 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 o 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 [umass] [patch] Problems with connection of the umass o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113977 usb [request] Need a way to set mode of USB disk's write c o usb/113672 usb [ehci] [panic] Kernel panic with AEWIN CB6971 s usb/113629 usb [ukbd] Dropped USB keyboard events on Dell Latitude D6 o usb/113432 usb [ucom] WARNING: attempt to net_add_domain(netgraph) af a usb/113060 usb [usbdevs] [patch] Samsung printer not working in bidir o usb/112944 usb [ulpt] [patch] Bi-directional access to HP LaserJet 10 o usb/112640 usb [usb] [hang] Kernel freezes when writing a file to an o usb/112631 usb [panic] Problem with SONY DSC-S80 camera on umount s usb/112568 usb [umass] [request] USB mode may wrong when mounting Pla o usb/112463 usb [umass] problem with Samsung USB DVD writer, libscg an o usb/112461 usb [ehci] [request] ehci USB 2.0 doesn't work on nforce4 o usb/111753 usb [uhid] [panic] Replicable system panic involving UHID o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC o usb/109397 usb [panic] on boot from USB flash o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr s usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/108056 usb [ohci] Mouse gets powered off during device probe when o usb/107935 usb [uplcom] [panic] panic while accessing /dev/cuaU0 o usb/107924 usb [patch] usbd(8) does not call detach o usb/107848 usb [umass] [request] cannot access Samsung flash disk o usb/107827 usb [ohci] [panic] ohci_add_done addr not found o usb/107496 usb [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [ o usb/107388 usb [patch] [request] new driver: add utoppy device from N o usb/107248 usb [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP o usb/107243 usb [cam] [patch] Apacer USB Flash Drive quirk o usb/106861 usb [usbdevs] [patch]: usbdevs update: Add product ACER Ze s usb/106832 usb [usb] USB HP printer is not detected by kernel when AC o usb/106648 usb [umass] [hang] USB Floppy on D1950 10 min Hang on Inse o usb/106621 usb [axe] [patch] DLINK DUB-E100 support broken o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106041 usb [usb] [request] FreeBSD does not recognise Mustek Bear o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/105186 usb [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c o usb/105065 usb [ata] [usb] SATA - USB Bridge o usb/104830 usb [umass] system crashes when copying data to umass devi o usb/104645 usb [umass] [request] Rave C-201 MP3 player does not commu o usb/104352 usb [ural] [patch] ural driver doesnt work o usb/104292 usb [umass] [hang] system lockup on forced umount of usb-s o usb/104290 usb [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto o usb/103917 usb [uhub] USB driver reports "Addr 0 should never happen" o usb/103418 usb usbhidctl(1): [patch] [request] usbhidctl: add ability o usb/103289 usb [request] USB 2.0 problems on AMD LX-800 CPU and CS-55 o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103025 usb [uhub] [panic] wrong detection of USB device for FreeB o usb/102976 usb [panic] Casio Exilim Digital Camera causes panic on in o usb/102678 usb [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/101761 usb [usb] [patch] [request] usb.h: increase maximal size o o usb/101752 usb [umass] [panic] 6.1-RELEASE kernel panic on usb device o usb/101448 usb [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O o usb/101096 usb [ural] [panic] USB WLAN occasionally causes kernel-pan o usb/100746 usb [keyboard] system does not boot due to USB keyboard pr o usb/99538 usb [keyboard] while using USB keyboard default params of 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/93408 usb [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w 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 o 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/91629 usb [usb] usbd_abort_pipe() may result in infinite loop 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 f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US 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 f usb/83677 usb [usb] [request] usb controller often not detected (Sun 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/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu 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 " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, 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 o 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 o usb/75797 usb [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o 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 i386/46371 usb USB controller cannot be initialized on IBM Netfinity 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 303 problems total.