From jamesbrandongooch at gmail.com  Sun Nov  1 05:50:01 2009
From: jamesbrandongooch at gmail.com (Brandon Gooch)
Date: Sun Nov  1 05:50:09 2009
Subject: usb/140160: USB ports are no longer "active" after ACPI
	suspend/resume cycle.
Message-ID: <200911010545.nA15jtFR012076@www.freebsd.org>


>Number:         140160
>Category:       usb
>Synopsis:       USB ports are no longer "active" after ACPI suspend/resume cycle.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 01 05:50:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Brandon Gooch
>Release:        8.0
>Organization:
>Environment:
FreeBSD x300 8.0-RC2 FreeBSD 8.0-RC2 #0 r198667: Fri Oct 30 02:21:46 UTC 2009     root@x300:/usr/obj/usr/src/sys/X300  amd64
>Description:
USB ports are unavailable after a suspend/resume cycle. From /var/log/messages:

Oct 31 13:41:22 x300 acpi: suspend at 20091031 13:41:22
Oct 31 13:41:26 x300 kernel: ugen0.2: <STMicroelectronics> at usbus0 (disconnected)
Oct 31 13:41:35 x300 kernel: ugen6.2: <vendor 0x17ef> at usbus6 (disconnected)
Oct 31 13:41:35 x300 kernel: usb_alloc_device:1597: set address 2 failed (USB_ERR_TIMEOUT, ignored)
Oct 31 13:41:47 x300 kernel: usb_alloc_device:1635: getting device descriptor at addr 2 failed, USB_ERR_STALLED!
Oct 31 13:41:47 x300 kernel: usbus2: port reset timeout
Oct 31 13:41:47 x300 kernel: uhub_reattach_port:371: port 2 reset failed, error=USB_ERR_TIMEOUT
Oct 31 13:41:47 x300 kernel: uhub_reattach_port:458: device problem (USB_ERR_TIMEOUT), disabling port 2
Oct 31 13:41:47 x300 kernel: usbus6: port reset timeout
Oct 31 13:41:47 x300 kernel: uhub_reattach_port:371: port 5 reset failed, error=USB_ERR_TIMEOUT
Oct 31 13:41:47 x300 kernel: uhub_reattach_port:458: device problem (USB_ERR_TIMEOUT), disabling port 5
Oct 31 13:41:47 x300 kernel: usbd_req_re_enumerate:1539: addr=2, set address failed! (USB_ERR_STALLED, ignored)
Oct 31 13:41:47 x300 kernel: usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed, USB_ERR_STALLED!
Oct 31 13:41:47 x300 kernel: usbd_req_re_enumerate:1539: addr=2, set address failed! (USB_ERR_STALLED, ignored)
Oct 31 13:41:47 x300 kernel: usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed, USB_ERR_STALLED!
Oct 31 13:41:47 x300 kernel: ugen0.2: <(null)> at usbus0 (disconnected)
Oct 31 13:41:47 x300 kernel: uhub_reattach_port:436: could not allocate new device!
Oct 31 13:41:47 x300 acpi: resumed at 20091031 13:41:47
Oct 31 13:41:48 x300 root: Unknown USB device: vendor 0x17ef product 0x4807 bus uhub6
Oct 31 13:41:48 x300 kernel: ugen6.2: <vendor 0x17ef> at usbus6

>How-To-Repeat:
Suspend computer, then resume computer. Plug a device into any of the USB ports and realize that the ports are no longer "active".
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From hselasky at c2i.net  Sun Nov  1 09:11:30 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Nov  1 09:11:37 2009
Subject: usb/140160: USB ports are no longer "active" after ACPI
	suspend/resume cycle.
In-Reply-To: <200911010545.nA15jtFR012076@www.freebsd.org>
References: <200911010545.nA15jtFR012076@www.freebsd.org>
Message-ID: <200911011012.43262.hselasky@c2i.net>

On Sunday 01 November 2009 06:45:55 Brandon Gooch wrote:
> >Number:         140160
> >Category:       usb
> >Synopsis:       USB ports are no longer "active" after ACPI suspend/resume
> > cycle. Confidential:   no
> >Severity:       non-critical
> >Priority:       medium
> >Responsible:    freebsd-usb
> >State:          open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Sun Nov 01 05:50:00 UTC 2009
> >Closed-Date:
> >Last-Modified:
> >Originator:     Brandon Gooch
> >Release:        8.0
> >Organization:
> >Environment:
>
> FreeBSD x300 8.0-RC2 FreeBSD 8.0-RC2 #0 r198667: Fri Oct 30 02:21:46 UTC
> 2009     root@x300:/usr/obj/usr/src/sys/X300  amd64
>
> >Description:
>
> USB ports are unavailable after a suspend/resume cycle. From
> /var/log/messages:
>
> Oct 31 13:41:22 x300 acpi: suspend at 20091031 13:41:22
> Oct 31 13:41:26 x300 kernel: ugen0.2: <STMicroelectronics> at usbus0
> (disconnected) Oct 31 13:41:35 x300 kernel: ugen6.2: <vendor 0x17ef> at
> usbus6 (disconnected) Oct 31 13:41:35 x300 kernel: usb_alloc_device:1597:
> set address 2 failed (USB_ERR_TIMEOUT, ignored) Oct 31 13:41:47 x300
> kernel: usb_alloc_device:1635: getting device descriptor at addr 2 failed,
> USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: usbus2: port reset timeout
> Oct 31 13:41:47 x300 kernel: uhub_reattach_port:371: port 2 reset failed,
> error=USB_ERR_TIMEOUT Oct 31 13:41:47 x300 kernel: uhub_reattach_port:458:
> device problem (USB_ERR_TIMEOUT), disabling port 2 Oct 31 13:41:47 x300
> kernel: usbus6: port reset timeout
> Oct 31 13:41:47 x300 kernel: uhub_reattach_port:371: port 5 reset failed,
> error=USB_ERR_TIMEOUT Oct 31 13:41:47 x300 kernel: uhub_reattach_port:458:
> device problem (USB_ERR_TIMEOUT), disabling port 5 Oct 31 13:41:47 x300
> kernel: usbd_req_re_enumerate:1539: addr=2, set address failed!
> (USB_ERR_STALLED, ignored) Oct 31 13:41:47 x300 kernel:
> usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed,
> USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: usbd_req_re_enumerate:1539:
> addr=2, set address failed! (USB_ERR_STALLED, ignored) Oct 31 13:41:47 x300
> kernel: usbd_req_re_enumerate:1553: getting device descriptor at addr 2
> failed, USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: ugen0.2: <(null)> at
> usbus0 (disconnected) Oct 31 13:41:47 x300 kernel: uhub_reattach_port:436:
> could not allocate new device! Oct 31 13:41:47 x300 acpi: resumed at
> 20091031 13:41:47
> Oct 31 13:41:48 x300 root: Unknown USB device: vendor 0x17ef product 0x4807
> bus uhub6 Oct 31 13:41:48 x300 kernel: ugen6.2: <vendor 0x17ef> at usbus6
>
> >How-To-Repeat:
>
> Suspend computer, then resume computer. Plug a device into any of the USB
> ports and realize that the ports are no longer "active".
>
> >Fix:

Can you try to disable USB legacy support in the BIOS. Probably there is a 
BIOS handover issue at resume.

--HPS

From hselasky at c2i.net  Sun Nov  1 09:20:03 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Nov  1 09:20:09 2009
Subject: usb/140160: USB ports are no longer "active" after ACPI
	suspend/resume cycle.
Message-ID: <200911010920.nA19K3h6055784@freefall.freebsd.org>

The following reply was made to PR usb/140160; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Brandon Gooch <jamesbrandongooch@gmail.com>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/140160: USB ports are no longer "active" after ACPI suspend/resume cycle.
Date: Sun, 1 Nov 2009 10:12:41 +0100

 On Sunday 01 November 2009 06:45:55 Brandon Gooch wrote:
 > >Number:         140160
 > >Category:       usb
 > >Synopsis:       USB ports are no longer "active" after ACPI suspend/resume
 > > cycle. Confidential:   no
 > >Severity:       non-critical
 > >Priority:       medium
 > >Responsible:    freebsd-usb
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Sun Nov 01 05:50:00 UTC 2009
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Brandon Gooch
 > >Release:        8.0
 > >Organization:
 > >Environment:
 >
 > FreeBSD x300 8.0-RC2 FreeBSD 8.0-RC2 #0 r198667: Fri Oct 30 02:21:46 UTC
 > 2009     root@x300:/usr/obj/usr/src/sys/X300  amd64
 >
 > >Description:
 >
 > USB ports are unavailable after a suspend/resume cycle. From
 > /var/log/messages:
 >
 > Oct 31 13:41:22 x300 acpi: suspend at 20091031 13:41:22
 > Oct 31 13:41:26 x300 kernel: ugen0.2: <STMicroelectronics> at usbus0
 > (disconnected) Oct 31 13:41:35 x300 kernel: ugen6.2: <vendor 0x17ef> at
 > usbus6 (disconnected) Oct 31 13:41:35 x300 kernel: usb_alloc_device:1597:
 > set address 2 failed (USB_ERR_TIMEOUT, ignored) Oct 31 13:41:47 x300
 > kernel: usb_alloc_device:1635: getting device descriptor at addr 2 failed,
 > USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: usbus2: port reset timeout
 > Oct 31 13:41:47 x300 kernel: uhub_reattach_port:371: port 2 reset failed,
 > error=USB_ERR_TIMEOUT Oct 31 13:41:47 x300 kernel: uhub_reattach_port:458:
 > device problem (USB_ERR_TIMEOUT), disabling port 2 Oct 31 13:41:47 x300
 > kernel: usbus6: port reset timeout
 > Oct 31 13:41:47 x300 kernel: uhub_reattach_port:371: port 5 reset failed,
 > error=USB_ERR_TIMEOUT Oct 31 13:41:47 x300 kernel: uhub_reattach_port:458:
 > device problem (USB_ERR_TIMEOUT), disabling port 5 Oct 31 13:41:47 x300
 > kernel: usbd_req_re_enumerate:1539: addr=2, set address failed!
 > (USB_ERR_STALLED, ignored) Oct 31 13:41:47 x300 kernel:
 > usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed,
 > USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: usbd_req_re_enumerate:1539:
 > addr=2, set address failed! (USB_ERR_STALLED, ignored) Oct 31 13:41:47 x300
 > kernel: usbd_req_re_enumerate:1553: getting device descriptor at addr 2
 > failed, USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: ugen0.2: <(null)> at
 > usbus0 (disconnected) Oct 31 13:41:47 x300 kernel: uhub_reattach_port:436:
 > could not allocate new device! Oct 31 13:41:47 x300 acpi: resumed at
 > 20091031 13:41:47
 > Oct 31 13:41:48 x300 root: Unknown USB device: vendor 0x17ef product 0x4807
 > bus uhub6 Oct 31 13:41:48 x300 kernel: ugen6.2: <vendor 0x17ef> at usbus6
 >
 > >How-To-Repeat:
 >
 > Suspend computer, then resume computer. Plug a device into any of the USB
 > ports and realize that the ports are no longer "active".
 >
 > >Fix:
 
 Can you try to disable USB legacy support in the BIOS. Probably there is a 
 BIOS handover issue at resume.
 
 --HPS
 
From oxyd.oxyd at gmail.com  Sun Nov  1 15:28:21 2009
From: oxyd.oxyd at gmail.com (=?UTF-8?Q?Ond=C5=99ej_Majerech?=)
Date: Sun Nov  1 15:28:27 2009
Subject: HP LaserJet P1005 USB Printer under FreeBSD 8.0-RC2
Message-ID: <f60d361f0911010658y75e85a43m8a43c1074dc022e5@mail.gmail.com>

Hello list,

I had my HP P1005 printer working just fine under 7.2-RELEASE, but I
just updated to 8.0-RC2 and the driver doesn't seem to like the new
USB stack.

I was using the foo2xqx driver [ http://foo2xqx.rkkda.com/ ] -- with
this driver, the firmware needs to be sent to the printer each time it
is turned on, like this: cat sihpP1005.dl > /dev/ugen0.0.

Now, according to dmesg, the printer is now known as device
/dev/ugen2.2, but I can't send the firmware to it (and I can't send
the firmware to any other ugen* device either):

cat sihpP1005.dl > /dev/ugen2.2
cat: stdout: Input/output error

(Trying the same as root or with sudo doesn't make any difference.)

My /etc/devfs.rules:

add path 'da*' mode 0660 group operator
add path 'usb' mode 0777
add path 'usb/*' mode 0666
add path 'usbctl' mode 0666
add path 'ugen*' mode 0777

ls -lh /dev/ugen* with the printer connected and turned on:

lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen0.1 -> usb/0.1.0
lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen1.1 -> usb/1.1.0
lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen2.1 -> usb/2.1.0
lrwxrwxrwx  1 root  wheel     9B Oct 31 20:31 /dev/ugen2.2 -> usb/2.2.0
lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen3.1 -> usb/3.1.0
lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen4.1 -> usb/4.1.0
lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen5.1 -> usb/5.1.0
lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen6.1 -> usb/6.1.0

Googling around for possible solutions didn't turn up anything
successful for me.  I asked on the FreeBSD Forums and was told to turn
on debug informations on ugen by sysctl hw.usb.ugen.debug=1 -- I did,
but I don't see anything new in dmesg or /var/log/messages -- maybe I
don't know where to look?

Anyway, any suggestions?

~ Ondra
From hselasky at c2i.net  Sun Nov  1 16:11:57 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Nov  1 16:12:03 2009
Subject: HP LaserJet P1005 USB Printer under FreeBSD 8.0-RC2
In-Reply-To: <f60d361f0911010658y75e85a43m8a43c1074dc022e5@mail.gmail.com>
References: <f60d361f0911010658y75e85a43m8a43c1074dc022e5@mail.gmail.com>
Message-ID: <200911011713.07994.hselasky@c2i.net>

On Sunday 01 November 2009 15:58:50 Ond?ej Majerech wrote:
> Hello list,
>
> I had my HP P1005 printer working just fine under 7.2-RELEASE, but I
> just updated to 8.0-RC2 and the driver doesn't seem to like the new
> USB stack.

How did you update?

Did you recompile foo2xqx ?

>
> I was using the foo2xqx driver [ http://foo2xqx.rkkda.com/ ] -- with
> this driver, the firmware needs to be sent to the printer each time it
> is turned on, like this: cat sihpP1005.dl > /dev/ugen0.0.

You need to specify the endpoint. ugenX.0 is the control endpoint.

> Now, according to dmesg, the printer is now known as device
> /dev/ugen2.2, but I can't send the firmware to it (and I can't send
> the firmware to any other ugen* device either):
>
> cat sihpP1005.dl > /dev/ugen2.2
> cat: stdout: Input/output error
>
> (Trying the same as root or with sudo doesn't make any difference.)
>
> My /etc/devfs.rules:
>
> add path 'da*' mode 0660 group operator
> add path 'usb' mode 0777
> add path 'usb/*' mode 0666
> add path 'usbctl' mode 0666
> add path 'ugen*' mode 0777
>
> ls -lh /dev/ugen* with the printer connected and turned on:
>
> lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen0.1 -> usb/0.1.0
> lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen1.1 -> usb/1.1.0
> lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen2.1 -> usb/2.1.0
> lrwxrwxrwx  1 root  wheel     9B Oct 31 20:31 /dev/ugen2.2 -> usb/2.2.0
> lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen3.1 -> usb/3.1.0
> lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen4.1 -> usb/4.1.0
> lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen5.1 -> usb/5.1.0
> lrwxrwxrwx  1 root  wheel     9B Oct 31 17:18 /dev/ugen6.1 -> usb/6.1.0
>
> Googling around for possible solutions didn't turn up anything
> successful for me.  I asked on the FreeBSD Forums and was told to turn
> on debug informations on ugen by sysctl hw.usb.ugen.debug=1 -- I did,
> but I don't see anything new in dmesg or /var/log/messages -- maybe I
> don't know where to look?
>
> Anyway, any suggestions?

--HPS

From jamesbrandongooch at gmail.com  Sun Nov  1 17:15:35 2009
From: jamesbrandongooch at gmail.com (Brandon Gooch)
Date: Sun Nov  1 17:15:42 2009
Subject: usb/140160: USB ports are no longer "active" after ACPI 
	suspend/resume cycle.
In-Reply-To: <200911011012.43262.hselasky@c2i.net>
References: <200911010545.nA15jtFR012076@www.freebsd.org>
	<200911011012.43262.hselasky@c2i.net>
Message-ID: <179b97fb0911010850h4acb2bfen3c236bcc7abda49f@mail.gmail.com>

On Sun, Nov 1, 2009 at 9:12 AM, Hans Petter Selasky <hselasky@c2i.net> wrote:
> On Sunday 01 November 2009 06:45:55 Brandon Gooch wrote:
>> >Number: ? ? ? ? 140160
>> >Category: ? ? ? usb
>> >Synopsis: ? ? ? USB ports are no longer "active" after ACPI suspend/resume
>> > cycle. Confidential: ? no
>> >Severity: ? ? ? non-critical
>> >Priority: ? ? ? medium
>> >Responsible: ? ?freebsd-usb
>> >State: ? ? ? ? ?open
>> >Quarter:
>> >Keywords:
>> >Date-Required:
>> >Class: ? ? ? ? ?sw-bug
>> >Submitter-Id: ? current-users
>> >Arrival-Date: ? Sun Nov 01 05:50:00 UTC 2009
>> >Closed-Date:
>> >Last-Modified:
>> >Originator: ? ? Brandon Gooch
>> >Release: ? ? ? ?8.0
>> >Organization:
>> >Environment:
>>
>> FreeBSD x300 8.0-RC2 FreeBSD 8.0-RC2 #0 r198667: Fri Oct 30 02:21:46 UTC
>> 2009 ? ? root@x300:/usr/obj/usr/src/sys/X300 ?amd64
>>
>> >Description:
>>
>> USB ports are unavailable after a suspend/resume cycle. From
>> /var/log/messages:
>>
>> Oct 31 13:41:22 x300 acpi: suspend at 20091031 13:41:22
>> Oct 31 13:41:26 x300 kernel: ugen0.2: <STMicroelectronics> at usbus0
>> (disconnected) Oct 31 13:41:35 x300 kernel: ugen6.2: <vendor 0x17ef> at
>> usbus6 (disconnected) Oct 31 13:41:35 x300 kernel: usb_alloc_device:1597:
>> set address 2 failed (USB_ERR_TIMEOUT, ignored) Oct 31 13:41:47 x300
>> kernel: usb_alloc_device:1635: getting device descriptor at addr 2 failed,
>> USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: usbus2: port reset timeout
>> Oct 31 13:41:47 x300 kernel: uhub_reattach_port:371: port 2 reset failed,
>> error=USB_ERR_TIMEOUT Oct 31 13:41:47 x300 kernel: uhub_reattach_port:458:
>> device problem (USB_ERR_TIMEOUT), disabling port 2 Oct 31 13:41:47 x300
>> kernel: usbus6: port reset timeout
>> Oct 31 13:41:47 x300 kernel: uhub_reattach_port:371: port 5 reset failed,
>> error=USB_ERR_TIMEOUT Oct 31 13:41:47 x300 kernel: uhub_reattach_port:458:
>> device problem (USB_ERR_TIMEOUT), disabling port 5 Oct 31 13:41:47 x300
>> kernel: usbd_req_re_enumerate:1539: addr=2, set address failed!
>> (USB_ERR_STALLED, ignored) Oct 31 13:41:47 x300 kernel:
>> usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed,
>> USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: usbd_req_re_enumerate:1539:
>> addr=2, set address failed! (USB_ERR_STALLED, ignored) Oct 31 13:41:47 x300
>> kernel: usbd_req_re_enumerate:1553: getting device descriptor at addr 2
>> failed, USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: ugen0.2: <(null)> at
>> usbus0 (disconnected) Oct 31 13:41:47 x300 kernel: uhub_reattach_port:436:
>> could not allocate new device! Oct 31 13:41:47 x300 acpi: resumed at
>> 20091031 13:41:47
>> Oct 31 13:41:48 x300 root: Unknown USB device: vendor 0x17ef product 0x4807
>> bus uhub6 Oct 31 13:41:48 x300 kernel: ugen6.2: <vendor 0x17ef> at usbus6
>>
>> >How-To-Repeat:
>>
>> Suspend computer, then resume computer. Plug a device into any of the USB
>> ports and realize that the ports are no longer "active".
>>
>> >Fix:
>
> Can you try to disable USB legacy support in the BIOS. Probably there is a
> BIOS handover issue at resume.
>
> --HPS
>
>

I've tried each combination of bios settings, and the problem
persists. It's strange -- the first suspend/resume cycle works great,
everything comes back on, USB ports still active, etc...

It's the subsequent suspend/resume cycles where I see the problem.
I've attached my dmesg output, in case it matters.
-------------- next part --------------
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 8.0-RC2 #0 r198667: Fri Oct 30 02:21:46 UTC 2009
    root@x300:/usr/obj/usr/src/sys/X300
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Duo CPU     L7100  @ 1.20GHz (1197.01-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x6fb  Stepping = 11
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0xe3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant
real memory  = 2147483648 (2048 MB)
avail memory = 2031456256 (1937 MB)
ACPI APIC Table: <LENOVO TP-7T   >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32 20090521 tbfadt-625
ACPI Warning: Optional field Gpe1Block has zero address or length:        0    102C/0 20090521 tbfadt-655
ioapic0: Changing APIC ID to 1
ioapic0 <Version 2.0> irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: <LENOVO TP-7T> on motherboard
acpi0: [ITHREAD]
acpi_ec0: <Embedded Controller: GPE 0x12, ECDT> port 0x62,0x66 on acpi0
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 7ef00000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_button0: <Sleep Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
vgapci0: <VGA-compatible display> port 0x1800-0x1807 mem 0xfa000000-0xfa0fffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
agp0: <Intel GM965 SVGA controller> on vgapci0
agp0: detected 7676k stolen memory
agp0: aperture size is 256M
drm0: <Intel i965GM> on vgapci0
info: [drm] MSI enabled 1 message(s)
vgapci0: child drm0 requested pci_enable_busmaster
info: [drm] AGP at 0xe0000000 256MB
info: [drm] Initialized i915 1.6.0 20080730
vgapci1: <VGA-compatible display> mem 0xfa100000-0xfa1fffff at device 2.1 on pci0
em0: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0x1840-0x185f mem 0xfa200000-0xfa21ffff,0xfa225000-0xfa225fff irq 20 at device 25.0 on pci0
em0: Using MSI interrupt
em0: [FILTER]
em0: Ethernet address: 00:1c:25:7c:1d:59
uhci0: <Intel 82801H (ICH8) USB controller USB-D> port 0x1860-0x187f irq 20 at device 26.0 on pci0
uhci0: [ITHREAD]
usbus0: <Intel 82801H (ICH8) USB controller USB-D> on uhci0
uhci1: <Intel 82801H (ICH8) USB controller USB-E> port 0x1880-0x189f irq 21 at device 26.1 on pci0
uhci1: [ITHREAD]
usbus1: <Intel 82801H (ICH8) USB controller USB-E> on uhci1
ehci0: <Intel 82801H (ICH8) USB 2.0 controller USB2-B> mem 0xfa426c00-0xfa426fff irq 22 at device 26.7 on pci0
ehci0: [ITHREAD]
usbus2: EHCI version 1.0
usbus2: <Intel 82801H (ICH8) USB 2.0 controller USB2-B> on ehci0
hdac0: <Intel 82801H High Definition Audio Controller> mem 0xfa220000-0xfa223fff irq 17 at device 27.0 on pci0
hdac0: HDA Driver Revision: 20090624_0136
hdac0: [ITHREAD]
pcib1: <ACPI PCI-PCI bridge> irq 20 at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 21 at device 28.1 on pci0
pci3: <ACPI PCI bus> on pcib2
iwn0: <Intel(R) PRO/Wireless 4965BGN> mem 0xf9f00000-0xf9f01fff irq 17 at device 0.0 on pci3
===band 0===
chan lo=1, chan hi=13
chan1 num=2
chain 0, sample 0: temp=30 gain=40 power=18 pa_det=-27
chain 0, sample 1: temp=28 gain=32 power=26 pa_det=3
chain 0, sample 2: temp=29 gain=24 power=34 pa_det=38
chain 1, sample 0: temp=29 gain=41 power=18 pa_det=-22
chain 1, sample 1: temp=29 gain=33 power=26 pa_det=9
chain 1, sample 2: temp=29 gain=26 power=32 pa_det=39
chan2 num=12
chain 0, sample 0: temp=29 gain=41 power=18 pa_det=-30
chain 0, sample 1: temp=29 gain=34 power=26 pa_det=-5
chain 0, sample 2: temp=29 gain=27 power=32 pa_det=26
chain 1, sample 0: temp=29 gain=42 power=18 pa_det=-25
chain 1, sample 1: temp=29 gain=35 power=25 pa_det=0
chain 1, sample 2: temp=29 gain=28 power=32 pa_det=33
===band 1===
chan lo=34, chan hi=64
chan1 num=36
chain 0, sample 0: temp=29 gain=38 power=19 pa_det=-23
chain 0, sample 1: temp=29 gain=28 power=28 pa_det=12
chain 0, sample 2: temp=29 gain=23 power=33 pa_det=35
chain 1, sample 0: temp=29 gain=35 power=18 pa_det=-20
chain 1, sample 1: temp=29 gain=25 power=26 pa_det=14
chain 1, sample 2: temp=29 gain=20 power=31 pa_det=37
chan2 num=60
chain 0, sample 0: temp=29 gain=41 power=19 pa_det=-26
chain 0, sample 1: temp=29 gain=33 power=27 pa_det=6
chain 0, sample 2: temp=29 gain=27 power=32 pa_det=26
chain 1, sample 0: temp=29 gain=34 power=19 pa_det=-21
chain 1, sample 1: temp=29 gain=26 power=26 pa_det=4
chain 1, sample 2: temp=29 gain=20 power=32 pa_det=31
===band 2===
chan lo=100, chan hi=132
chan1 num=104
chain 0, sample 0: temp=29 gain=44 power=17 pa_det=-40
chain 0, sample 1: temp=29 gain=36 power=25 pa_det=-17
chain 0, sample 2: temp=29 gain=28 power=32 pa_det=15
chain 1, sample 0: temp=29 gain=36 power=17 pa_det=-33
chain 1, sample 1: temp=29 gain=27 power=25 pa_det=-7
chain 1, sample 2: temp=30 gain=20 power=32 pa_det=24
chan2 num=128
chain 0, sample 0: temp=29 gain=40 power=17 pa_det=-39
chain 0, sample 1: temp=29 gain=33 power=24 pa_det=-18
chain 0, sample 2: temp=29 gain=25 power=32 pa_det=13
chain 1, sample 0: temp=29 gain=37 power=17 pa_det=-34
chain 1, sample 1: temp=29 gain=27 power=26 pa_det=-4
chain 1, sample 2: temp=30 gain=21 power=32 pa_det=22
===band 3===
chan lo=134, chan hi=165
chan1 num=140
chain 0, sample 0: temp=30 gain=39 power=17 pa_det=-39
chain 0, sample 1: temp=30 gain=31 power=24 pa_det=-17
chain 0, sample 2: temp=29 gain=24 power=31 pa_det=13
chain 1, sample 0: temp=29 gain=37 power=16 pa_det=-36
chain 1, sample 1: temp=30 gain=26 power=27 pa_det=-2
chain 1, sample 2: temp=30 gain=21 power=31 pa_det=18
chan2 num=161
chain 0, sample 0: temp=30 gain=37 power=16 pa_det=-38
chain 0, sample 1: temp=30 gain=28 power=25 pa_det=-9
chain 0, sample 2: temp=30 gain=22 power=31 pa_det=17
chain 1, sample 0: temp=30 gain=32 power=16 pa_det=-34
chain 1, sample 1: temp=30 gain=22 power=26 pa_det=-2
chain 1, sample 2: temp=31 gain=16 power=31 pa_det=24
===band 4===
chan lo=0, chan hi=0
chan1 num=0
chain 0, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 2: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 2: temp=0 gain=0 power=0 pa_det=0
chan2 num=0
chain 0, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 2: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 2: temp=0 gain=0 power=0 pa_det=0
===band 5===
chan lo=0, chan hi=0
chan1 num=0
chain 0, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 2: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 2: temp=0 gain=0 power=0 pa_det=0
chan2 num=0
chain 0, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 2: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 2: temp=0 gain=0 power=0 pa_det=0
===band 6===
chan lo=0, chan hi=0
chan1 num=0
chain 0, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 2: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 2: temp=0 gain=0 power=0 pa_det=0
chan2 num=0
chain 0, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 2: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 2: temp=0 gain=0 power=0 pa_det=0
===band 7===
chan lo=0, chan hi=0
chan1 num=0
chain 0, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 2: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 2: temp=0 gain=0 power=0 pa_det=0
chan2 num=0
chain 0, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 0, sample 2: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 0: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 1: temp=0 gain=0 power=0 pa_det=0
chain 1, sample 2: temp=0 gain=0 power=0 pa_det=0
iwn0: MIMO 2T3R, MoW1, address 00:1f:3b:28:30:c5
iwn0: [ITHREAD]
iwn0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
iwn0: 11na MCS: 15Mbps 30Mbps 45Mbps 60Mbps 90Mbps 120Mbps 135Mbps 150Mbps 30Mbps 60Mbps 90Mbps 120Mbps 180Mbps 240Mbps 270Mbps 300Mbps
iwn0: 11ng MCS: 15Mbps 30Mbps 45Mbps 60Mbps 90Mbps 120Mbps 135Mbps 150Mbps 30Mbps 60Mbps 90Mbps 120Mbps 180Mbps 240Mbps 270Mbps 300Mbps
pcib3: <ACPI PCI-PCI bridge> irq 22 at device 28.2 on pci0
pci4: <ACPI PCI bus> on pcib3
uhci2: <Intel 82801H (ICH8) USB controller USB-A> port 0x18a0-0x18bf irq 16 at device 29.0 on pci0
uhci2: [ITHREAD]
usbus3: <Intel 82801H (ICH8) USB controller USB-A> on uhci2
uhci3: <Intel 82801H (ICH8) USB controller USB-B> port 0x18c0-0x18df irq 17 at device 29.1 on pci0
uhci3: [ITHREAD]
usbus4: <Intel 82801H (ICH8) USB controller USB-B> on uhci3
uhci4: <Intel 82801H (ICH8) USB controller USB-C> port 0x18e0-0x18ff irq 18 at device 29.2 on pci0
uhci4: [ITHREAD]
usbus5: <Intel 82801H (ICH8) USB controller USB-C> on uhci4
ehci1: <Intel 82801H (ICH8) USB 2.0 controller USB2-A> mem 0xfa427000-0xfa4273ff irq 19 at device 29.7 on pci0
ehci1: [ITHREAD]
usbus6: EHCI version 1.0
usbus6: <Intel 82801H (ICH8) USB 2.0 controller USB2-A> on ehci1
pcib4: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci13: <ACPI PCI bus> on pcib4
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH8M UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1c00-0x1c0f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
atapci1: <Intel ICH8M SATA300 controller> port 0x1c50-0x1c57,0x1c44-0x1c47,0x1c48-0x1c4f,0x1c40-0x1c43,0x1c20-0x1c3f mem 0xfa426000-0xfa4267ff irq 16 at device 31.2 on pci0
atapci1: [ITHREAD]
atapci1: AHCI called from vendor specific driver
atapci1: AHCI v1.10 controller with 3 1.5Gbps ports, PM not supported
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 2> on atapci1
ata3: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
acpi_tz0: <Thermal Zone> on acpi0
acpi_tz1: <Thermal Zone> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model Generic PS/2 mouse, device ID 0
battery0: <ACPI Control Method Battery> on acpi0
acpi_acad0: <AC Adapter> on acpi0
acpi_ibm0: <IBM ThinkPad ACPI Extras> on acpi0
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcffff,0xd0000-0xd0fff,0xd1000-0xd1fff,0xe0000-0xeffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
            to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS filesystem version 13
ZFS storage pool version 13
Timecounters tick every 1.000 msec
module_register_init: MOD_LOAD (ng_vboxnetflt, 0xffffffff80b95580, 0xffffffff80d782e0) error 22
vboxdrv: fAsync=0 offMin=0xf6 offMax=0x22e
vboxnet0: Ethernet address: 0a:00:27:00:00:00
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 480Mbps High Speed USB v2.0
usbus3: 12Mbps Full Speed USB v1.0
usbus4: 12Mbps Full Speed USB v1.0
usbus5: 12Mbps Full Speed USB v1.0
usbus6: 480Mbps High Speed USB v2.0
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen2.1: <Intel> at usbus2
uhub2: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
ugen3.1: <Intel> at usbus3
uhub3: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
ugen4.1: <Intel> at usbus4
uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
ugen5.1: <Intel> at usbus5
uhub5: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
ugen6.1: <Intel> at usbus6
uhub6: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus6
acd0: DVDR <MATSHITADVD-RAM UJ-844/RC02> at ata0-master UDMA33
ad4: 61057MB <SAMSUNG MCCOE64G8MPP-0VA PS105L15> at ata2-master SATA150
hdac0: HDA Codec #0: Analog Devices AD1984A
pcm0: <HDA Analog Devices AD1984A PCM #0 Analog> at cad 0 nid 1 on hdac0
SMP: AP CPU #1 Launched!
Root mount waiting for: usbus6 usbus5 usbus4 usbus3 usbus2 usbus1 usbus0
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
uhub4: 2 ports with 2 removable, self powered
uhub5: 2 ports with 2 removable, self powered
Root mount waiting for: usbus6 usbus2
uhub2: 4 ports with 4 removable, self powered
Root mount waiting for: usbus6 usbus2
uhub6: 6 ports with 6 removable, self powered
ugen6.2: <vendor 0x17ef> at usbus6
Trying to mount root from zfs:zroot
ugen1.2: <vendor 0x0461> at usbus1
ums0: <vendor 0x0461 USB Optical Mouse, class 0/0, rev 2.00/2.00, addr 2> on usbus1
ugen0.2: <STMicroelectronics> at usbus0
ums0: 3 buttons and [XYZ] coordinates ID=0
wlan0: Ethernet address: 00:1f:3b:28:30:c5
ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding disabled, default to deny, logging disabled
wlan0: link state changed to UP
iwn0: need multicast update callback
iwn0: need multicast update callback
iwn0: need multicast update callback
drm0: [ITHREAD]
iwn0: need multicast update callback
wlan0: link state changed to DOWN
stray irq0
ugen0.2: <STMicroelectronics> at usbus0 (disconnected)ugen1.2: <vendor 0x0461> at usbus1 (disconnected)

ums0: at uhub1, port 1, addr 2 (disconnected)
ugen1.2: <vendor 0x0461> at usbus1
ums0: <vendor 0x0461 USB Optical Mouse, class 0/0, rev 2.00/2.00, addr 2> on usbus1
ums0: 3 buttons and [XYZ] coordinates ID=0
ugen0.2: <STMicroelectronics> at usbus0
drm0: [ITHREAD]
wlan0: link state changed to UP
iwn0: need multicast update callback
iwn0: need multicast update callback
iwn0: need multicast update callback
iwn0: need multicast update callback
wlan0: link state changed to DOWN
stray irq0
acpi_ec0: warning: EC done before starting event wait
ugen0.2: <STMicroelectronics> at usbus0 (disconnected)
ugen1.2: <vendor 0x0461> at usbus1 (disconnected)
ums0: at uhub1, port 1, addr 2 (disconnected)
ugen6.2: <vendor 0x17ef> at usbus6 (disconnected)
ugen6.2: <vendor 0x17ef> at usbus6
ugen0.2: <STMicroelectronics> at usbus0
drm0: [ITHREAD]
wlan0: link state changed to UP
iwn0: need multicast update callback
iwn0: need multicast update callback
iwn0: need multicast update callback
iwn0: need multicast update callback
wlan0: link state changed to DOWN
stray irq0
ugen0.2: <STMicroelectronics> at usbus0 (disconnected)
ugen0.2: <STMicroelectronics> at usbus0
drm0: [ITHREAD]
wlan0: link state changed to UP
iwn0: need multicast update callback
iwn0: need multicast update callback
iwn0: need multicast update callback
iwn0: need multicast update callback
wlan0: link state changed to DOWN
stray irq0
ugen0.2: <STMicroelectronics> at usbus0 (disconnected)
usbus2: port reset timeout
uhub_reattach_port:371: port 2 reset failed, error=USB_ERR_TIMEOUT
uhub_reattach_port:458: device problem (USB_ERR_TIMEOUT), disabling port 2
ugen6.2: <vendor 0x17ef> at usbus6 (disconnected)
usbus6: port reset timeout
uhub_reattach_port:371: port 5 reset failed, error=USB_ERR_TIMEOUT
uhub_reattach_port:458: device problem (USB_ERR_TIMEOUT), disabling port 5
drm0: [ITHREAD]
ugen6.2: <vendor 0x17ef> at usbus6
wlan0: link state changed to UP
iwn0: need multicast update callback
iwn0: need multicast update callback
iwn0: need multicast update callback
From jamesbrandongooch at gmail.com  Sun Nov  1 17:20:04 2009
From: jamesbrandongooch at gmail.com (Brandon Gooch)
Date: Sun Nov  1 17:20:11 2009
Subject: usb/140160: USB ports are no longer "active" after ACPI 
	suspend/resume cycle.
Message-ID: <200911011720.nA1HK3vd070719@freefall.freebsd.org>

The following reply was made to PR usb/140160; it has been noted by GNATS.

From: Brandon Gooch <jamesbrandongooch@gmail.com>
To: Hans Petter Selasky <hselasky@c2i.net>
Cc: freebsd-usb@freebsd.org, freebsd-gnats-submit@freebsd.org
Subject: Re: usb/140160: USB ports are no longer "active" after ACPI 
	suspend/resume cycle.
Date: Sun, 1 Nov 2009 16:50:05 +0000

 --000325559e2695b4640477520d3a
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 On Sun, Nov 1, 2009 at 9:12 AM, Hans Petter Selasky <hselasky@c2i.net> wrot=
 e:
 > On Sunday 01 November 2009 06:45:55 Brandon Gooch wrote:
 >> >Number: =A0 =A0 =A0 =A0 140160
 >> >Category: =A0 =A0 =A0 usb
 >> >Synopsis: =A0 =A0 =A0 USB ports are no longer "active" after ACPI suspe=
 nd/resume
 >> > cycle. Confidential: =A0 no
 >> >Severity: =A0 =A0 =A0 non-critical
 >> >Priority: =A0 =A0 =A0 medium
 >> >Responsible: =A0 =A0freebsd-usb
 >> >State: =A0 =A0 =A0 =A0 =A0open
 >> >Quarter:
 >> >Keywords:
 >> >Date-Required:
 >> >Class: =A0 =A0 =A0 =A0 =A0sw-bug
 >> >Submitter-Id: =A0 current-users
 >> >Arrival-Date: =A0 Sun Nov 01 05:50:00 UTC 2009
 >> >Closed-Date:
 >> >Last-Modified:
 >> >Originator: =A0 =A0 Brandon Gooch
 >> >Release: =A0 =A0 =A0 =A08.0
 >> >Organization:
 >> >Environment:
 >>
 >> FreeBSD x300 8.0-RC2 FreeBSD 8.0-RC2 #0 r198667: Fri Oct 30 02:21:46 UTC
 >> 2009 =A0 =A0 root@x300:/usr/obj/usr/src/sys/X300 =A0amd64
 >>
 >> >Description:
 >>
 >> USB ports are unavailable after a suspend/resume cycle. From
 >> /var/log/messages:
 >>
 >> Oct 31 13:41:22 x300 acpi: suspend at 20091031 13:41:22
 >> Oct 31 13:41:26 x300 kernel: ugen0.2: <STMicroelectronics> at usbus0
 >> (disconnected) Oct 31 13:41:35 x300 kernel: ugen6.2: <vendor 0x17ef> at
 >> usbus6 (disconnected) Oct 31 13:41:35 x300 kernel: usb_alloc_device:1597=
 :
 >> set address 2 failed (USB_ERR_TIMEOUT, ignored) Oct 31 13:41:47 x300
 >> kernel: usb_alloc_device:1635: getting device descriptor at addr 2 faile=
 d,
 >> USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: usbus2: port reset timeout
 >> Oct 31 13:41:47 x300 kernel: uhub_reattach_port:371: port 2 reset failed=
 ,
 >> error=3DUSB_ERR_TIMEOUT Oct 31 13:41:47 x300 kernel: uhub_reattach_port:=
 458:
 >> device problem (USB_ERR_TIMEOUT), disabling port 2 Oct 31 13:41:47 x300
 >> kernel: usbus6: port reset timeout
 >> Oct 31 13:41:47 x300 kernel: uhub_reattach_port:371: port 5 reset failed=
 ,
 >> error=3DUSB_ERR_TIMEOUT Oct 31 13:41:47 x300 kernel: uhub_reattach_port:=
 458:
 >> device problem (USB_ERR_TIMEOUT), disabling port 5 Oct 31 13:41:47 x300
 >> kernel: usbd_req_re_enumerate:1539: addr=3D2, set address failed!
 >> (USB_ERR_STALLED, ignored) Oct 31 13:41:47 x300 kernel:
 >> usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed,
 >> USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: usbd_req_re_enumerate:1539=
 :
 >> addr=3D2, set address failed! (USB_ERR_STALLED, ignored) Oct 31 13:41:47=
  x300
 >> kernel: usbd_req_re_enumerate:1553: getting device descriptor at addr 2
 >> failed, USB_ERR_STALLED! Oct 31 13:41:47 x300 kernel: ugen0.2: <(null)> =
 at
 >> usbus0 (disconnected) Oct 31 13:41:47 x300 kernel: uhub_reattach_port:43=
 6:
 >> could not allocate new device! Oct 31 13:41:47 x300 acpi: resumed at
 >> 20091031 13:41:47
 >> Oct 31 13:41:48 x300 root: Unknown USB device: vendor 0x17ef product 0x4=
 807
 >> bus uhub6 Oct 31 13:41:48 x300 kernel: ugen6.2: <vendor 0x17ef> at usbus=
 6
 >>
 >> >How-To-Repeat:
 >>
 >> Suspend computer, then resume computer. Plug a device into any of the US=
 B
 >> ports and realize that the ports are no longer "active".
 >>
 >> >Fix:
 >
 > Can you try to disable USB legacy support in the BIOS. Probably there is =
 a
 > BIOS handover issue at resume.
 >
 > --HPS
 >
 >
 
 I've tried each combination of bios settings, and the problem
 persists. It's strange -- the first suspend/resume cycle works great,
 everything comes back on, USB ports still active, etc...
 
 It's the subsequent suspend/resume cycles where I see the problem.
 I've attached my dmesg output, in case it matters.
 
 --000325559e2695b4640477520d3a
 Content-Type: text/plain; charset=US-ASCII; name="dmesg_lenovo_x300.txt"
 Content-Disposition: attachment; filename="dmesg_lenovo_x300.txt"
 Content-Transfer-Encoding: base64
 X-Attachment-Id: f_g1hqfx5t0
 
 Q29weXJpZ2h0IChjKSAxOTkyLTIwMDkgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChj
 KSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAx
 OTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln
 aHRzIHJlc2VydmVkLgpGcmVlQlNEIGlzIGEgcmVnaXN0ZXJlZCB0cmFkZW1hcmsgb2YgVGhlIEZy
 ZWVCU0QgRm91bmRhdGlvbi4KRnJlZUJTRCA4LjAtUkMyICMwIHIxOTg2Njc6IEZyaSBPY3QgMzAg
 MDI6MjE6NDYgVVRDIDIwMDkKICAgIHJvb3RAeDMwMDovdXNyL29iai91c3Ivc3JjL3N5cy9YMzAw
 ClRpbWVjb3VudGVyICJpODI1NCIgZnJlcXVlbmN5IDExOTMxODIgSHogcXVhbGl0eSAwCkNQVTog
 SW50ZWwoUikgQ29yZShUTSkyIER1byBDUFUgICAgIEw3MTAwICBAIDEuMjBHSHogKDExOTcuMDEt
 TUh6IEs4LWNsYXNzIENQVSkKICBPcmlnaW4gPSAiR2VudWluZUludGVsIiAgSWQgPSAweDZmYiAg
 U3RlcHBpbmcgPSAxMQogIEZlYXR1cmVzPTB4YmZlYmZiZmY8RlBVLFZNRSxERSxQU0UsVFNDLE1T
 UixQQUUsTUNFLENYOCxBUElDLFNFUCxNVFJSLFBHRSxNQ0EsQ01PVixQQVQsUFNFMzYsQ0xGTFVT
 SCxEVFMsQUNQSSxNTVgsRlhTUixTU0UsU1NFMixTUyxIVFQsVE0sUEJFPgogIEZlYXR1cmVzMj0w
 eGUzYmQ8U1NFMyxEVEVTNjQsTU9OLERTX0NQTCxWTVgsRVNULFRNMixTU1NFMyxDWDE2LHhUUFIs
 UERDTT4KICBBTUQgRmVhdHVyZXM9MHgyMDEwMDgwMDxTWVNDQUxMLE5YLExNPgogIEFNRCBGZWF0
 dXJlczI9MHgxPExBSEY+CiAgVFNDOiBQLXN0YXRlIGludmFyaWFudApyZWFsIG1lbW9yeSAgPSAy
 MTQ3NDgzNjQ4ICgyMDQ4IE1CKQphdmFpbCBtZW1vcnkgPSAyMDMxNDU2MjU2ICgxOTM3IE1CKQpB
 Q1BJIEFQSUMgVGFibGU6IDxMRU5PVk8gVFAtN1QgICA+CkZyZWVCU0QvU01QOiBNdWx0aXByb2Nl
 c3NvciBTeXN0ZW0gRGV0ZWN0ZWQ6IDIgQ1BVcwpGcmVlQlNEL1NNUDogMSBwYWNrYWdlKHMpIHgg
 MiBjb3JlKHMpCiBjcHUwIChCU1ApOiBBUElDIElEOiAgMAogY3B1MSAoQVApOiBBUElDIElEOiAg
 MQpBQ1BJIFdhcm5pbmc6IDMyLzY0WCBsZW5ndGggbWlzbWF0Y2ggaW4gR3BlMUJsb2NrOiAwLzMy
 IDIwMDkwNTIxIHRiZmFkdC02MjUKQUNQSSBXYXJuaW5nOiBPcHRpb25hbCBmaWVsZCBHcGUxQmxv
 Y2sgaGFzIHplcm8gYWRkcmVzcyBvciBsZW5ndGg6ICAgICAgICAwICAgIDEwMkMvMCAyMDA5MDUy
 MSB0YmZhZHQtNjU1CmlvYXBpYzA6IENoYW5naW5nIEFQSUMgSUQgdG8gMQppb2FwaWMwIDxWZXJz
 aW9uIDIuMD4gaXJxcyAwLTIzIG9uIG1vdGhlcmJvYXJkCmtiZDEgYXQga2JkbXV4MAphY3BpMDog
 PExFTk9WTyBUUC03VD4gb24gbW90aGVyYm9hcmQKYWNwaTA6IFtJVEhSRUFEXQphY3BpX2VjMDog
 PEVtYmVkZGVkIENvbnRyb2xsZXI6IEdQRSAweDEyLCBFQ0RUPiBwb3J0IDB4NjIsMHg2NiBvbiBh
 Y3BpMAphY3BpMDogUG93ZXIgQnV0dG9uIChmaXhlZCkKYWNwaTA6IHJlc2VydmF0aW9uIG9mIDAs
 IGEwMDAwICgzKSBmYWlsZWQKYWNwaTA6IHJlc2VydmF0aW9uIG9mIDEwMDAwMCwgN2VmMDAwMDAg
 KDMpIGZhaWxlZApUaW1lY291bnRlciAiQUNQSS1mYXN0IiBmcmVxdWVuY3kgMzU3OTU0NSBIeiBx
 dWFsaXR5IDEwMDAKYWNwaV90aW1lcjA6IDwyNC1iaXQgdGltZXIgYXQgMy41Nzk1NDVNSHo+IHBv
 cnQgMHgxMDA4LTB4MTAwYiBvbiBhY3BpMAphY3BpX2hwZXQwOiA8SGlnaCBQcmVjaXNpb24gRXZl
 bnQgVGltZXI+IGlvbWVtIDB4ZmVkMDAwMDAtMHhmZWQwMDNmZiBvbiBhY3BpMApUaW1lY291bnRl
 ciAiSFBFVCIgZnJlcXVlbmN5IDE0MzE4MTgwIEh6IHF1YWxpdHkgOTAwCmFjcGlfbGlkMDogPENv
 bnRyb2wgTWV0aG9kIExpZCBTd2l0Y2g+IG9uIGFjcGkwCmFjcGlfYnV0dG9uMDogPFNsZWVwIEJ1
 dHRvbj4gb24gYWNwaTAKcGNpYjA6IDxBQ1BJIEhvc3QtUENJIGJyaWRnZT4gcG9ydCAweGNmOC0w
 eGNmZiBvbiBhY3BpMApwY2kwOiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liMAp2Z2FwY2kwOiA8VkdB
 LWNvbXBhdGlibGUgZGlzcGxheT4gcG9ydCAweDE4MDAtMHgxODA3IG1lbSAweGZhMDAwMDAwLTB4
 ZmEwZmZmZmYsMHhlMDAwMDAwMC0weGVmZmZmZmZmIGlycSAxNiBhdCBkZXZpY2UgMi4wIG9uIHBj
 aTAKYWdwMDogPEludGVsIEdNOTY1IFNWR0EgY29udHJvbGxlcj4gb24gdmdhcGNpMAphZ3AwOiBk
 ZXRlY3RlZCA3Njc2ayBzdG9sZW4gbWVtb3J5CmFncDA6IGFwZXJ0dXJlIHNpemUgaXMgMjU2TQpk
 cm0wOiA8SW50ZWwgaTk2NUdNPiBvbiB2Z2FwY2kwCmluZm86IFtkcm1dIE1TSSBlbmFibGVkIDEg
 bWVzc2FnZShzKQp2Z2FwY2kwOiBjaGlsZCBkcm0wIHJlcXVlc3RlZCBwY2lfZW5hYmxlX2J1c21h
 c3RlcgppbmZvOiBbZHJtXSBBR1AgYXQgMHhlMDAwMDAwMCAyNTZNQgppbmZvOiBbZHJtXSBJbml0
 aWFsaXplZCBpOTE1IDEuNi4wIDIwMDgwNzMwCnZnYXBjaTE6IDxWR0EtY29tcGF0aWJsZSBkaXNw
 bGF5PiBtZW0gMHhmYTEwMDAwMC0weGZhMWZmZmZmIGF0IGRldmljZSAyLjEgb24gcGNpMAplbTA6
 IDxJbnRlbChSKSBQUk8vMTAwMCBOZXR3b3JrIENvbm5lY3Rpb24gNi45LjE0PiBwb3J0IDB4MTg0
 MC0weDE4NWYgbWVtIDB4ZmEyMDAwMDAtMHhmYTIxZmZmZiwweGZhMjI1MDAwLTB4ZmEyMjVmZmYg
 aXJxIDIwIGF0IGRldmljZSAyNS4wIG9uIHBjaTAKZW0wOiBVc2luZyBNU0kgaW50ZXJydXB0CmVt
 MDogW0ZJTFRFUl0KZW0wOiBFdGhlcm5ldCBhZGRyZXNzOiAwMDoxYzoyNTo3YzoxZDo1OQp1aGNp
 MDogPEludGVsIDgyODAxSCAoSUNIOCkgVVNCIGNvbnRyb2xsZXIgVVNCLUQ+IHBvcnQgMHgxODYw
 LTB4MTg3ZiBpcnEgMjAgYXQgZGV2aWNlIDI2LjAgb24gcGNpMAp1aGNpMDogW0lUSFJFQURdCnVz
 YnVzMDogPEludGVsIDgyODAxSCAoSUNIOCkgVVNCIGNvbnRyb2xsZXIgVVNCLUQ+IG9uIHVoY2kw
 CnVoY2kxOiA8SW50ZWwgODI4MDFIIChJQ0g4KSBVU0IgY29udHJvbGxlciBVU0ItRT4gcG9ydCAw
 eDE4ODAtMHgxODlmIGlycSAyMSBhdCBkZXZpY2UgMjYuMSBvbiBwY2kwCnVoY2kxOiBbSVRIUkVB
 RF0KdXNidXMxOiA8SW50ZWwgODI4MDFIIChJQ0g4KSBVU0IgY29udHJvbGxlciBVU0ItRT4gb24g
 dWhjaTEKZWhjaTA6IDxJbnRlbCA4MjgwMUggKElDSDgpIFVTQiAyLjAgY29udHJvbGxlciBVU0Iy
 LUI+IG1lbSAweGZhNDI2YzAwLTB4ZmE0MjZmZmYgaXJxIDIyIGF0IGRldmljZSAyNi43IG9uIHBj
 aTAKZWhjaTA6IFtJVEhSRUFEXQp1c2J1czI6IEVIQ0kgdmVyc2lvbiAxLjAKdXNidXMyOiA8SW50
 ZWwgODI4MDFIIChJQ0g4KSBVU0IgMi4wIGNvbnRyb2xsZXIgVVNCMi1CPiBvbiBlaGNpMApoZGFj
 MDogPEludGVsIDgyODAxSCBIaWdoIERlZmluaXRpb24gQXVkaW8gQ29udHJvbGxlcj4gbWVtIDB4
 ZmEyMjAwMDAtMHhmYTIyM2ZmZiBpcnEgMTcgYXQgZGV2aWNlIDI3LjAgb24gcGNpMApoZGFjMDog
 SERBIERyaXZlciBSZXZpc2lvbjogMjAwOTA2MjRfMDEzNgpoZGFjMDogW0lUSFJFQURdCnBjaWIx
 OiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gaXJxIDIwIGF0IGRldmljZSAyOC4wIG9uIHBjaTAKcGNp
 MjogPEFDUEkgUENJIGJ1cz4gb24gcGNpYjEKcGNpYjI6IDxBQ1BJIFBDSS1QQ0kgYnJpZGdlPiBp
 cnEgMjEgYXQgZGV2aWNlIDI4LjEgb24gcGNpMApwY2kzOiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2li
 Mgppd24wOiA8SW50ZWwoUikgUFJPL1dpcmVsZXNzIDQ5NjVCR04+IG1lbSAweGY5ZjAwMDAwLTB4
 ZjlmMDFmZmYgaXJxIDE3IGF0IGRldmljZSAwLjAgb24gcGNpMwo9PT1iYW5kIDA9PT0KY2hhbiBs
 bz0xLCBjaGFuIGhpPTEzCmNoYW4xIG51bT0yCmNoYWluIDAsIHNhbXBsZSAwOiB0ZW1wPTMwIGdh
 aW49NDAgcG93ZXI9MTggcGFfZGV0PS0yNwpjaGFpbiAwLCBzYW1wbGUgMTogdGVtcD0yOCBnYWlu
 PTMyIHBvd2VyPTI2IHBhX2RldD0zCmNoYWluIDAsIHNhbXBsZSAyOiB0ZW1wPTI5IGdhaW49MjQg
 cG93ZXI9MzQgcGFfZGV0PTM4CmNoYWluIDEsIHNhbXBsZSAwOiB0ZW1wPTI5IGdhaW49NDEgcG93
 ZXI9MTggcGFfZGV0PS0yMgpjaGFpbiAxLCBzYW1wbGUgMTogdGVtcD0yOSBnYWluPTMzIHBvd2Vy
 PTI2IHBhX2RldD05CmNoYWluIDEsIHNhbXBsZSAyOiB0ZW1wPTI5IGdhaW49MjYgcG93ZXI9MzIg
 cGFfZGV0PTM5CmNoYW4yIG51bT0xMgpjaGFpbiAwLCBzYW1wbGUgMDogdGVtcD0yOSBnYWluPTQx
 IHBvd2VyPTE4IHBhX2RldD0tMzAKY2hhaW4gMCwgc2FtcGxlIDE6IHRlbXA9MjkgZ2Fpbj0zNCBw
 b3dlcj0yNiBwYV9kZXQ9LTUKY2hhaW4gMCwgc2FtcGxlIDI6IHRlbXA9MjkgZ2Fpbj0yNyBwb3dl
 cj0zMiBwYV9kZXQ9MjYKY2hhaW4gMSwgc2FtcGxlIDA6IHRlbXA9MjkgZ2Fpbj00MiBwb3dlcj0x
 OCBwYV9kZXQ9LTI1CmNoYWluIDEsIHNhbXBsZSAxOiB0ZW1wPTI5IGdhaW49MzUgcG93ZXI9MjUg
 cGFfZGV0PTAKY2hhaW4gMSwgc2FtcGxlIDI6IHRlbXA9MjkgZ2Fpbj0yOCBwb3dlcj0zMiBwYV9k
 ZXQ9MzMKPT09YmFuZCAxPT09CmNoYW4gbG89MzQsIGNoYW4gaGk9NjQKY2hhbjEgbnVtPTM2CmNo
 YWluIDAsIHNhbXBsZSAwOiB0ZW1wPTI5IGdhaW49MzggcG93ZXI9MTkgcGFfZGV0PS0yMwpjaGFp
 biAwLCBzYW1wbGUgMTogdGVtcD0yOSBnYWluPTI4IHBvd2VyPTI4IHBhX2RldD0xMgpjaGFpbiAw
 LCBzYW1wbGUgMjogdGVtcD0yOSBnYWluPTIzIHBvd2VyPTMzIHBhX2RldD0zNQpjaGFpbiAxLCBz
 YW1wbGUgMDogdGVtcD0yOSBnYWluPTM1IHBvd2VyPTE4IHBhX2RldD0tMjAKY2hhaW4gMSwgc2Ft
 cGxlIDE6IHRlbXA9MjkgZ2Fpbj0yNSBwb3dlcj0yNiBwYV9kZXQ9MTQKY2hhaW4gMSwgc2FtcGxl
 IDI6IHRlbXA9MjkgZ2Fpbj0yMCBwb3dlcj0zMSBwYV9kZXQ9MzcKY2hhbjIgbnVtPTYwCmNoYWlu
 IDAsIHNhbXBsZSAwOiB0ZW1wPTI5IGdhaW49NDEgcG93ZXI9MTkgcGFfZGV0PS0yNgpjaGFpbiAw
 LCBzYW1wbGUgMTogdGVtcD0yOSBnYWluPTMzIHBvd2VyPTI3IHBhX2RldD02CmNoYWluIDAsIHNh
 bXBsZSAyOiB0ZW1wPTI5IGdhaW49MjcgcG93ZXI9MzIgcGFfZGV0PTI2CmNoYWluIDEsIHNhbXBs
 ZSAwOiB0ZW1wPTI5IGdhaW49MzQgcG93ZXI9MTkgcGFfZGV0PS0yMQpjaGFpbiAxLCBzYW1wbGUg
 MTogdGVtcD0yOSBnYWluPTI2IHBvd2VyPTI2IHBhX2RldD00CmNoYWluIDEsIHNhbXBsZSAyOiB0
 ZW1wPTI5IGdhaW49MjAgcG93ZXI9MzIgcGFfZGV0PTMxCj09PWJhbmQgMj09PQpjaGFuIGxvPTEw
 MCwgY2hhbiBoaT0xMzIKY2hhbjEgbnVtPTEwNApjaGFpbiAwLCBzYW1wbGUgMDogdGVtcD0yOSBn
 YWluPTQ0IHBvd2VyPTE3IHBhX2RldD0tNDAKY2hhaW4gMCwgc2FtcGxlIDE6IHRlbXA9MjkgZ2Fp
 bj0zNiBwb3dlcj0yNSBwYV9kZXQ9LTE3CmNoYWluIDAsIHNhbXBsZSAyOiB0ZW1wPTI5IGdhaW49
 MjggcG93ZXI9MzIgcGFfZGV0PTE1CmNoYWluIDEsIHNhbXBsZSAwOiB0ZW1wPTI5IGdhaW49MzYg
 cG93ZXI9MTcgcGFfZGV0PS0zMwpjaGFpbiAxLCBzYW1wbGUgMTogdGVtcD0yOSBnYWluPTI3IHBv
 d2VyPTI1IHBhX2RldD0tNwpjaGFpbiAxLCBzYW1wbGUgMjogdGVtcD0zMCBnYWluPTIwIHBvd2Vy
 PTMyIHBhX2RldD0yNApjaGFuMiBudW09MTI4CmNoYWluIDAsIHNhbXBsZSAwOiB0ZW1wPTI5IGdh
 aW49NDAgcG93ZXI9MTcgcGFfZGV0PS0zOQpjaGFpbiAwLCBzYW1wbGUgMTogdGVtcD0yOSBnYWlu
 PTMzIHBvd2VyPTI0IHBhX2RldD0tMTgKY2hhaW4gMCwgc2FtcGxlIDI6IHRlbXA9MjkgZ2Fpbj0y
 NSBwb3dlcj0zMiBwYV9kZXQ9MTMKY2hhaW4gMSwgc2FtcGxlIDA6IHRlbXA9MjkgZ2Fpbj0zNyBw
 b3dlcj0xNyBwYV9kZXQ9LTM0CmNoYWluIDEsIHNhbXBsZSAxOiB0ZW1wPTI5IGdhaW49MjcgcG93
 ZXI9MjYgcGFfZGV0PS00CmNoYWluIDEsIHNhbXBsZSAyOiB0ZW1wPTMwIGdhaW49MjEgcG93ZXI9
 MzIgcGFfZGV0PTIyCj09PWJhbmQgMz09PQpjaGFuIGxvPTEzNCwgY2hhbiBoaT0xNjUKY2hhbjEg
 bnVtPTE0MApjaGFpbiAwLCBzYW1wbGUgMDogdGVtcD0zMCBnYWluPTM5IHBvd2VyPTE3IHBhX2Rl
 dD0tMzkKY2hhaW4gMCwgc2FtcGxlIDE6IHRlbXA9MzAgZ2Fpbj0zMSBwb3dlcj0yNCBwYV9kZXQ9
 LTE3CmNoYWluIDAsIHNhbXBsZSAyOiB0ZW1wPTI5IGdhaW49MjQgcG93ZXI9MzEgcGFfZGV0PTEz
 CmNoYWluIDEsIHNhbXBsZSAwOiB0ZW1wPTI5IGdhaW49MzcgcG93ZXI9MTYgcGFfZGV0PS0zNgpj
 aGFpbiAxLCBzYW1wbGUgMTogdGVtcD0zMCBnYWluPTI2IHBvd2VyPTI3IHBhX2RldD0tMgpjaGFp
 biAxLCBzYW1wbGUgMjogdGVtcD0zMCBnYWluPTIxIHBvd2VyPTMxIHBhX2RldD0xOApjaGFuMiBu
 dW09MTYxCmNoYWluIDAsIHNhbXBsZSAwOiB0ZW1wPTMwIGdhaW49MzcgcG93ZXI9MTYgcGFfZGV0
 PS0zOApjaGFpbiAwLCBzYW1wbGUgMTogdGVtcD0zMCBnYWluPTI4IHBvd2VyPTI1IHBhX2RldD0t
 OQpjaGFpbiAwLCBzYW1wbGUgMjogdGVtcD0zMCBnYWluPTIyIHBvd2VyPTMxIHBhX2RldD0xNwpj
 aGFpbiAxLCBzYW1wbGUgMDogdGVtcD0zMCBnYWluPTMyIHBvd2VyPTE2IHBhX2RldD0tMzQKY2hh
 aW4gMSwgc2FtcGxlIDE6IHRlbXA9MzAgZ2Fpbj0yMiBwb3dlcj0yNiBwYV9kZXQ9LTIKY2hhaW4g
 MSwgc2FtcGxlIDI6IHRlbXA9MzEgZ2Fpbj0xNiBwb3dlcj0zMSBwYV9kZXQ9MjQKPT09YmFuZCA0
 PT09CmNoYW4gbG89MCwgY2hhbiBoaT0wCmNoYW4xIG51bT0wCmNoYWluIDAsIHNhbXBsZSAwOiB0
 ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAgcGFfZGV0PTAKY2hhaW4gMCwgc2FtcGxlIDE6IHRlbXA9MCBn
 YWluPTAgcG93ZXI9MCBwYV9kZXQ9MApjaGFpbiAwLCBzYW1wbGUgMjogdGVtcD0wIGdhaW49MCBw
 b3dlcj0wIHBhX2RldD0wCmNoYWluIDEsIHNhbXBsZSAwOiB0ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAg
 cGFfZGV0PTAKY2hhaW4gMSwgc2FtcGxlIDE6IHRlbXA9MCBnYWluPTAgcG93ZXI9MCBwYV9kZXQ9
 MApjaGFpbiAxLCBzYW1wbGUgMjogdGVtcD0wIGdhaW49MCBwb3dlcj0wIHBhX2RldD0wCmNoYW4y
 IG51bT0wCmNoYWluIDAsIHNhbXBsZSAwOiB0ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAgcGFfZGV0PTAK
 Y2hhaW4gMCwgc2FtcGxlIDE6IHRlbXA9MCBnYWluPTAgcG93ZXI9MCBwYV9kZXQ9MApjaGFpbiAw
 LCBzYW1wbGUgMjogdGVtcD0wIGdhaW49MCBwb3dlcj0wIHBhX2RldD0wCmNoYWluIDEsIHNhbXBs
 ZSAwOiB0ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAgcGFfZGV0PTAKY2hhaW4gMSwgc2FtcGxlIDE6IHRl
 bXA9MCBnYWluPTAgcG93ZXI9MCBwYV9kZXQ9MApjaGFpbiAxLCBzYW1wbGUgMjogdGVtcD0wIGdh
 aW49MCBwb3dlcj0wIHBhX2RldD0wCj09PWJhbmQgNT09PQpjaGFuIGxvPTAsIGNoYW4gaGk9MApj
 aGFuMSBudW09MApjaGFpbiAwLCBzYW1wbGUgMDogdGVtcD0wIGdhaW49MCBwb3dlcj0wIHBhX2Rl
 dD0wCmNoYWluIDAsIHNhbXBsZSAxOiB0ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAgcGFfZGV0PTAKY2hh
 aW4gMCwgc2FtcGxlIDI6IHRlbXA9MCBnYWluPTAgcG93ZXI9MCBwYV9kZXQ9MApjaGFpbiAxLCBz
 YW1wbGUgMDogdGVtcD0wIGdhaW49MCBwb3dlcj0wIHBhX2RldD0wCmNoYWluIDEsIHNhbXBsZSAx
 OiB0ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAgcGFfZGV0PTAKY2hhaW4gMSwgc2FtcGxlIDI6IHRlbXA9
 MCBnYWluPTAgcG93ZXI9MCBwYV9kZXQ9MApjaGFuMiBudW09MApjaGFpbiAwLCBzYW1wbGUgMDog
 dGVtcD0wIGdhaW49MCBwb3dlcj0wIHBhX2RldD0wCmNoYWluIDAsIHNhbXBsZSAxOiB0ZW1wPTAg
 Z2Fpbj0wIHBvd2VyPTAgcGFfZGV0PTAKY2hhaW4gMCwgc2FtcGxlIDI6IHRlbXA9MCBnYWluPTAg
 cG93ZXI9MCBwYV9kZXQ9MApjaGFpbiAxLCBzYW1wbGUgMDogdGVtcD0wIGdhaW49MCBwb3dlcj0w
 IHBhX2RldD0wCmNoYWluIDEsIHNhbXBsZSAxOiB0ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAgcGFfZGV0
 PTAKY2hhaW4gMSwgc2FtcGxlIDI6IHRlbXA9MCBnYWluPTAgcG93ZXI9MCBwYV9kZXQ9MAo9PT1i
 YW5kIDY9PT0KY2hhbiBsbz0wLCBjaGFuIGhpPTAKY2hhbjEgbnVtPTAKY2hhaW4gMCwgc2FtcGxl
 IDA6IHRlbXA9MCBnYWluPTAgcG93ZXI9MCBwYV9kZXQ9MApjaGFpbiAwLCBzYW1wbGUgMTogdGVt
 cD0wIGdhaW49MCBwb3dlcj0wIHBhX2RldD0wCmNoYWluIDAsIHNhbXBsZSAyOiB0ZW1wPTAgZ2Fp
 bj0wIHBvd2VyPTAgcGFfZGV0PTAKY2hhaW4gMSwgc2FtcGxlIDA6IHRlbXA9MCBnYWluPTAgcG93
 ZXI9MCBwYV9kZXQ9MApjaGFpbiAxLCBzYW1wbGUgMTogdGVtcD0wIGdhaW49MCBwb3dlcj0wIHBh
 X2RldD0wCmNoYWluIDEsIHNhbXBsZSAyOiB0ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAgcGFfZGV0PTAK
 Y2hhbjIgbnVtPTAKY2hhaW4gMCwgc2FtcGxlIDA6IHRlbXA9MCBnYWluPTAgcG93ZXI9MCBwYV9k
 ZXQ9MApjaGFpbiAwLCBzYW1wbGUgMTogdGVtcD0wIGdhaW49MCBwb3dlcj0wIHBhX2RldD0wCmNo
 YWluIDAsIHNhbXBsZSAyOiB0ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAgcGFfZGV0PTAKY2hhaW4gMSwg
 c2FtcGxlIDA6IHRlbXA9MCBnYWluPTAgcG93ZXI9MCBwYV9kZXQ9MApjaGFpbiAxLCBzYW1wbGUg
 MTogdGVtcD0wIGdhaW49MCBwb3dlcj0wIHBhX2RldD0wCmNoYWluIDEsIHNhbXBsZSAyOiB0ZW1w
 PTAgZ2Fpbj0wIHBvd2VyPTAgcGFfZGV0PTAKPT09YmFuZCA3PT09CmNoYW4gbG89MCwgY2hhbiBo
 aT0wCmNoYW4xIG51bT0wCmNoYWluIDAsIHNhbXBsZSAwOiB0ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAg
 cGFfZGV0PTAKY2hhaW4gMCwgc2FtcGxlIDE6IHRlbXA9MCBnYWluPTAgcG93ZXI9MCBwYV9kZXQ9
 MApjaGFpbiAwLCBzYW1wbGUgMjogdGVtcD0wIGdhaW49MCBwb3dlcj0wIHBhX2RldD0wCmNoYWlu
 IDEsIHNhbXBsZSAwOiB0ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAgcGFfZGV0PTAKY2hhaW4gMSwgc2Ft
 cGxlIDE6IHRlbXA9MCBnYWluPTAgcG93ZXI9MCBwYV9kZXQ9MApjaGFpbiAxLCBzYW1wbGUgMjog
 dGVtcD0wIGdhaW49MCBwb3dlcj0wIHBhX2RldD0wCmNoYW4yIG51bT0wCmNoYWluIDAsIHNhbXBs
 ZSAwOiB0ZW1wPTAgZ2Fpbj0wIHBvd2VyPTAgcGFfZGV0PTAKY2hhaW4gMCwgc2FtcGxlIDE6IHRl
 bXA9MCBnYWluPTAgcG93ZXI9MCBwYV9kZXQ9MApjaGFpbiAwLCBzYW1wbGUgMjogdGVtcD0wIGdh
 aW49MCBwb3dlcj0wIHBhX2RldD0wCmNoYWluIDEsIHNhbXBsZSAwOiB0ZW1wPTAgZ2Fpbj0wIHBv
 d2VyPTAgcGFfZGV0PTAKY2hhaW4gMSwgc2FtcGxlIDE6IHRlbXA9MCBnYWluPTAgcG93ZXI9MCBw
 YV9kZXQ9MApjaGFpbiAxLCBzYW1wbGUgMjogdGVtcD0wIGdhaW49MCBwb3dlcj0wIHBhX2RldD0w
 Cml3bjA6IE1JTU8gMlQzUiwgTW9XMSwgYWRkcmVzcyAwMDoxZjozYjoyODozMDpjNQppd24wOiBb
 SVRIUkVBRF0KaXduMDogMTFhIHJhdGVzOiA2TWJwcyA5TWJwcyAxMk1icHMgMThNYnBzIDI0TWJw
 cyAzNk1icHMgNDhNYnBzIDU0TWJwcwppd24wOiAxMWIgcmF0ZXM6IDFNYnBzIDJNYnBzIDUuNU1i
 cHMgMTFNYnBzCml3bjA6IDExZyByYXRlczogMU1icHMgMk1icHMgNS41TWJwcyAxMU1icHMgNk1i
 cHMgOU1icHMgMTJNYnBzIDE4TWJwcyAyNE1icHMgMzZNYnBzIDQ4TWJwcyA1NE1icHMKaXduMDog
 MTFuYSBNQ1M6IDE1TWJwcyAzME1icHMgNDVNYnBzIDYwTWJwcyA5ME1icHMgMTIwTWJwcyAxMzVN
 YnBzIDE1ME1icHMgMzBNYnBzIDYwTWJwcyA5ME1icHMgMTIwTWJwcyAxODBNYnBzIDI0ME1icHMg
 MjcwTWJwcyAzMDBNYnBzCml3bjA6IDExbmcgTUNTOiAxNU1icHMgMzBNYnBzIDQ1TWJwcyA2ME1i
 cHMgOTBNYnBzIDEyME1icHMgMTM1TWJwcyAxNTBNYnBzIDMwTWJwcyA2ME1icHMgOTBNYnBzIDEy
 ME1icHMgMTgwTWJwcyAyNDBNYnBzIDI3ME1icHMgMzAwTWJwcwpwY2liMzogPEFDUEkgUENJLVBD
 SSBicmlkZ2U+IGlycSAyMiBhdCBkZXZpY2UgMjguMiBvbiBwY2kwCnBjaTQ6IDxBQ1BJIFBDSSBi
 dXM+IG9uIHBjaWIzCnVoY2kyOiA8SW50ZWwgODI4MDFIIChJQ0g4KSBVU0IgY29udHJvbGxlciBV
 U0ItQT4gcG9ydCAweDE4YTAtMHgxOGJmIGlycSAxNiBhdCBkZXZpY2UgMjkuMCBvbiBwY2kwCnVo
 Y2kyOiBbSVRIUkVBRF0KdXNidXMzOiA8SW50ZWwgODI4MDFIIChJQ0g4KSBVU0IgY29udHJvbGxl
 ciBVU0ItQT4gb24gdWhjaTIKdWhjaTM6IDxJbnRlbCA4MjgwMUggKElDSDgpIFVTQiBjb250cm9s
 bGVyIFVTQi1CPiBwb3J0IDB4MThjMC0weDE4ZGYgaXJxIDE3IGF0IGRldmljZSAyOS4xIG9uIHBj
 aTAKdWhjaTM6IFtJVEhSRUFEXQp1c2J1czQ6IDxJbnRlbCA4MjgwMUggKElDSDgpIFVTQiBjb250
 cm9sbGVyIFVTQi1CPiBvbiB1aGNpMwp1aGNpNDogPEludGVsIDgyODAxSCAoSUNIOCkgVVNCIGNv
 bnRyb2xsZXIgVVNCLUM+IHBvcnQgMHgxOGUwLTB4MThmZiBpcnEgMTggYXQgZGV2aWNlIDI5LjIg
 b24gcGNpMAp1aGNpNDogW0lUSFJFQURdCnVzYnVzNTogPEludGVsIDgyODAxSCAoSUNIOCkgVVNC
 IGNvbnRyb2xsZXIgVVNCLUM+IG9uIHVoY2k0CmVoY2kxOiA8SW50ZWwgODI4MDFIIChJQ0g4KSBV
 U0IgMi4wIGNvbnRyb2xsZXIgVVNCMi1BPiBtZW0gMHhmYTQyNzAwMC0weGZhNDI3M2ZmIGlycSAx
 OSBhdCBkZXZpY2UgMjkuNyBvbiBwY2kwCmVoY2kxOiBbSVRIUkVBRF0KdXNidXM2OiBFSENJIHZl
 cnNpb24gMS4wCnVzYnVzNjogPEludGVsIDgyODAxSCAoSUNIOCkgVVNCIDIuMCBjb250cm9sbGVy
 IFVTQjItQT4gb24gZWhjaTEKcGNpYjQ6IDxBQ1BJIFBDSS1QQ0kgYnJpZGdlPiBhdCBkZXZpY2Ug
 MzAuMCBvbiBwY2kwCnBjaTEzOiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liNAppc2FiMDogPFBDSS1J
 U0EgYnJpZGdlPiBhdCBkZXZpY2UgMzEuMCBvbiBwY2kwCmlzYTA6IDxJU0EgYnVzPiBvbiBpc2Fi
 MAphdGFwY2kwOiA8SW50ZWwgSUNIOE0gVURNQTEwMCBjb250cm9sbGVyPiBwb3J0IDB4MWYwLTB4
 MWY3LDB4M2Y2LDB4MTcwLTB4MTc3LDB4Mzc2LDB4MWMwMC0weDFjMGYgYXQgZGV2aWNlIDMxLjEg
 b24gcGNpMAphdGEwOiA8QVRBIGNoYW5uZWwgMD4gb24gYXRhcGNpMAphdGEwOiBbSVRIUkVBRF0K
 YXRhcGNpMTogPEludGVsIElDSDhNIFNBVEEzMDAgY29udHJvbGxlcj4gcG9ydCAweDFjNTAtMHgx
 YzU3LDB4MWM0NC0weDFjNDcsMHgxYzQ4LTB4MWM0ZiwweDFjNDAtMHgxYzQzLDB4MWMyMC0weDFj
 M2YgbWVtIDB4ZmE0MjYwMDAtMHhmYTQyNjdmZiBpcnEgMTYgYXQgZGV2aWNlIDMxLjIgb24gcGNp
 MAphdGFwY2kxOiBbSVRIUkVBRF0KYXRhcGNpMTogQUhDSSBjYWxsZWQgZnJvbSB2ZW5kb3Igc3Bl
 Y2lmaWMgZHJpdmVyCmF0YXBjaTE6IEFIQ0kgdjEuMTAgY29udHJvbGxlciB3aXRoIDMgMS41R2Jw
 cyBwb3J0cywgUE0gbm90IHN1cHBvcnRlZAphdGEyOiA8QVRBIGNoYW5uZWwgMD4gb24gYXRhcGNp
 MQphdGEyOiBbSVRIUkVBRF0KYXRhMzogPEFUQSBjaGFubmVsIDI+IG9uIGF0YXBjaTEKYXRhMzog
 W0lUSFJFQURdCnBjaTA6IDxzZXJpYWwgYnVzLCBTTUJ1cz4gYXQgZGV2aWNlIDMxLjMgKG5vIGRy
 aXZlciBhdHRhY2hlZCkKYWNwaV90ejA6IDxUaGVybWFsIFpvbmU+IG9uIGFjcGkwCmFjcGlfdHox
 OiA8VGhlcm1hbCBab25lPiBvbiBhY3BpMAphdHJ0YzA6IDxBVCByZWFsdGltZSBjbG9jaz4gcG9y
 dCAweDcwLTB4NzEgaXJxIDggb24gYWNwaTAKYXRrYmRjMDogPEtleWJvYXJkIGNvbnRyb2xsZXIg
 KGk4MDQyKT4gcG9ydCAweDYwLDB4NjQgaXJxIDEgb24gYWNwaTAKYXRrYmQwOiA8QVQgS2V5Ym9h
 cmQ+IGlycSAxIG9uIGF0a2JkYzAKa2JkMCBhdCBhdGtiZDAKYXRrYmQwOiBbR0lBTlQtTE9DS0VE
 XQphdGtiZDA6IFtJVEhSRUFEXQpwc20wOiA8UFMvMiBNb3VzZT4gaXJxIDEyIG9uIGF0a2JkYzAK
 cHNtMDogW0dJQU5ULUxPQ0tFRF0KcHNtMDogW0lUSFJFQURdCnBzbTA6IG1vZGVsIEdlbmVyaWMg
 UFMvMiBtb3VzZSwgZGV2aWNlIElEIDAKYmF0dGVyeTA6IDxBQ1BJIENvbnRyb2wgTWV0aG9kIEJh
 dHRlcnk+IG9uIGFjcGkwCmFjcGlfYWNhZDA6IDxBQyBBZGFwdGVyPiBvbiBhY3BpMAphY3BpX2li
 bTA6IDxJQk0gVGhpbmtQYWQgQUNQSSBFeHRyYXM+IG9uIGFjcGkwCmNwdTA6IDxBQ1BJIENQVT4g
 b24gYWNwaTAKZXN0MDogPEVuaGFuY2VkIFNwZWVkU3RlcCBGcmVxdWVuY3kgQ29udHJvbD4gb24g
 Y3B1MApwNHRjYzA6IDxDUFUgRnJlcXVlbmN5IFRoZXJtYWwgQ29udHJvbD4gb24gY3B1MApjcHUx
 OiA8QUNQSSBDUFU+IG9uIGFjcGkwCmVzdDE6IDxFbmhhbmNlZCBTcGVlZFN0ZXAgRnJlcXVlbmN5
 IENvbnRyb2w+IG9uIGNwdTEKcDR0Y2MxOiA8Q1BVIEZyZXF1ZW5jeSBUaGVybWFsIENvbnRyb2w+
 IG9uIGNwdTEKb3JtMDogPElTQSBPcHRpb24gUk9Ncz4gYXQgaW9tZW0gMHhjMDAwMC0weGNmZmZm
 LDB4ZDAwMDAtMHhkMGZmZiwweGQxMDAwLTB4ZDFmZmYsMHhlMDAwMC0weGVmZmZmIG9uIGlzYTAK
 c2MwOiA8U3lzdGVtIGNvbnNvbGU+IGF0IGZsYWdzIDB4MTAwIG9uIGlzYTAKc2MwOiBWR0EgPDE2
 IHZpcnR1YWwgY29uc29sZXMsIGZsYWdzPTB4MzAwPgp2Z2EwOiA8R2VuZXJpYyBJU0EgVkdBPiBh
 dCBwb3J0IDB4M2MwLTB4M2RmIGlvbWVtIDB4YTAwMDAtMHhiZmZmZiBvbiBpc2EwClpGUyBOT1RJ
 Q0U6IFByZWZldGNoIGlzIGRpc2FibGVkIGJ5IGRlZmF1bHQgaWYgbGVzcyB0aGFuIDRHQiBvZiBS
 QU0gaXMgcHJlc2VudDsKICAgICAgICAgICAgdG8gZW5hYmxlLCBhZGQgInZmcy56ZnMucHJlZmV0
 Y2hfZGlzYWJsZT0wIiB0byAvYm9vdC9sb2FkZXIuY29uZi4KWkZTIGZpbGVzeXN0ZW0gdmVyc2lv
 biAxMwpaRlMgc3RvcmFnZSBwb29sIHZlcnNpb24gMTMKVGltZWNvdW50ZXJzIHRpY2sgZXZlcnkg
 MS4wMDAgbXNlYwptb2R1bGVfcmVnaXN0ZXJfaW5pdDogTU9EX0xPQUQgKG5nX3Zib3huZXRmbHQs
 IDB4ZmZmZmZmZmY4MGI5NTU4MCwgMHhmZmZmZmZmZjgwZDc4MmUwKSBlcnJvciAyMgp2Ym94ZHJ2
 OiBmQXN5bmM9MCBvZmZNaW49MHhmNiBvZmZNYXg9MHgyMmUKdmJveG5ldDA6IEV0aGVybmV0IGFk
 ZHJlc3M6IDBhOjAwOjI3OjAwOjAwOjAwCnVzYnVzMDogMTJNYnBzIEZ1bGwgU3BlZWQgVVNCIHYx
 LjAKdXNidXMxOiAxMk1icHMgRnVsbCBTcGVlZCBVU0IgdjEuMAp1c2J1czI6IDQ4ME1icHMgSGln
 aCBTcGVlZCBVU0IgdjIuMAp1c2J1czM6IDEyTWJwcyBGdWxsIFNwZWVkIFVTQiB2MS4wCnVzYnVz
 NDogMTJNYnBzIEZ1bGwgU3BlZWQgVVNCIHYxLjAKdXNidXM1OiAxMk1icHMgRnVsbCBTcGVlZCBV
 U0IgdjEuMAp1c2J1czY6IDQ4ME1icHMgSGlnaCBTcGVlZCBVU0IgdjIuMAp1Z2VuMC4xOiA8SW50
 ZWw+IGF0IHVzYnVzMAp1aHViMDogPEludGVsIFVIQ0kgcm9vdCBIVUIsIGNsYXNzIDkvMCwgcmV2
 IDEuMDAvMS4wMCwgYWRkciAxPiBvbiB1c2J1czAKdWdlbjEuMTogPEludGVsPiBhdCB1c2J1czEK
 dWh1YjE6IDxJbnRlbCBVSENJIHJvb3QgSFVCLCBjbGFzcyA5LzAsIHJldiAxLjAwLzEuMDAsIGFk
 ZHIgMT4gb24gdXNidXMxCnVnZW4yLjE6IDxJbnRlbD4gYXQgdXNidXMyCnVodWIyOiA8SW50ZWwg
 RUhDSSByb290IEhVQiwgY2xhc3MgOS8wLCByZXYgMi4wMC8xLjAwLCBhZGRyIDE+IG9uIHVzYnVz
 Mgp1Z2VuMy4xOiA8SW50ZWw+IGF0IHVzYnVzMwp1aHViMzogPEludGVsIFVIQ0kgcm9vdCBIVUIs
 IGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAxPiBvbiB1c2J1czMKdWdlbjQuMTogPElu
 dGVsPiBhdCB1c2J1czQKdWh1YjQ6IDxJbnRlbCBVSENJIHJvb3QgSFVCLCBjbGFzcyA5LzAsIHJl
 diAxLjAwLzEuMDAsIGFkZHIgMT4gb24gdXNidXM0CnVnZW41LjE6IDxJbnRlbD4gYXQgdXNidXM1
 CnVodWI1OiA8SW50ZWwgVUhDSSByb290IEhVQiwgY2xhc3MgOS8wLCByZXYgMS4wMC8xLjAwLCBh
 ZGRyIDE+IG9uIHVzYnVzNQp1Z2VuNi4xOiA8SW50ZWw+IGF0IHVzYnVzNgp1aHViNjogPEludGVs
 IEVIQ0kgcm9vdCBIVUIsIGNsYXNzIDkvMCwgcmV2IDIuMDAvMS4wMCwgYWRkciAxPiBvbiB1c2J1
 czYKYWNkMDogRFZEUiA8TUFUU0hJVEFEVkQtUkFNIFVKLTg0NC9SQzAyPiBhdCBhdGEwLW1hc3Rl
 ciBVRE1BMzMKYWQ0OiA2MTA1N01CIDxTQU1TVU5HIE1DQ09FNjRHOE1QUC0wVkEgUFMxMDVMMTU+
 IGF0IGF0YTItbWFzdGVyIFNBVEExNTAKaGRhYzA6IEhEQSBDb2RlYyAjMDogQW5hbG9nIERldmlj
 ZXMgQUQxOTg0QQpwY20wOiA8SERBIEFuYWxvZyBEZXZpY2VzIEFEMTk4NEEgUENNICMwIEFuYWxv
 Zz4gYXQgY2FkIDAgbmlkIDEgb24gaGRhYzAKU01QOiBBUCBDUFUgIzEgTGF1bmNoZWQhClJvb3Qg
 bW91bnQgd2FpdGluZyBmb3I6IHVzYnVzNiB1c2J1czUgdXNidXM0IHVzYnVzMyB1c2J1czIgdXNi
 dXMxIHVzYnVzMAp1aHViMDogMiBwb3J0cyB3aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQK
 dWh1YjE6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJsZSwgc2VsZiBwb3dlcmVkCnVodWIzOiAyIHBv
 cnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZAp1aHViNDogMiBwb3J0cyB3aXRoIDIg
 cmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQKdWh1YjU6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJsZSwg
 c2VsZiBwb3dlcmVkClJvb3QgbW91bnQgd2FpdGluZyBmb3I6IHVzYnVzNiB1c2J1czIKdWh1YjI6
 IDQgcG9ydHMgd2l0aCA0IHJlbW92YWJsZSwgc2VsZiBwb3dlcmVkClJvb3QgbW91bnQgd2FpdGlu
 ZyBmb3I6IHVzYnVzNiB1c2J1czIKdWh1YjY6IDYgcG9ydHMgd2l0aCA2IHJlbW92YWJsZSwgc2Vs
 ZiBwb3dlcmVkCnVnZW42LjI6IDx2ZW5kb3IgMHgxN2VmPiBhdCB1c2J1czYKVHJ5aW5nIHRvIG1v
 dW50IHJvb3QgZnJvbSB6ZnM6enJvb3QKdWdlbjEuMjogPHZlbmRvciAweDA0NjE+IGF0IHVzYnVz
 MQp1bXMwOiA8dmVuZG9yIDB4MDQ2MSBVU0IgT3B0aWNhbCBNb3VzZSwgY2xhc3MgMC8wLCByZXYg
 Mi4wMC8yLjAwLCBhZGRyIDI+IG9uIHVzYnVzMQp1Z2VuMC4yOiA8U1RNaWNyb2VsZWN0cm9uaWNz
 PiBhdCB1c2J1czAKdW1zMDogMyBidXR0b25zIGFuZCBbWFlaXSBjb29yZGluYXRlcyBJRD0wCnds
 YW4wOiBFdGhlcm5ldCBhZGRyZXNzOiAwMDoxZjozYjoyODozMDpjNQppcGZ3MiAoK2lwdjYpIGlu
 aXRpYWxpemVkLCBkaXZlcnQgbG9hZGFibGUsIG5hdCBsb2FkYWJsZSwgcnVsZS1iYXNlZCBmb3J3
 YXJkaW5nIGRpc2FibGVkLCBkZWZhdWx0IHRvIGRlbnksIGxvZ2dpbmcgZGlzYWJsZWQKd2xhbjA6
 IGxpbmsgc3RhdGUgY2hhbmdlZCB0byBVUAppd24wOiBuZWVkIG11bHRpY2FzdCB1cGRhdGUgY2Fs
 bGJhY2sKaXduMDogbmVlZCBtdWx0aWNhc3QgdXBkYXRlIGNhbGxiYWNrCml3bjA6IG5lZWQgbXVs
 dGljYXN0IHVwZGF0ZSBjYWxsYmFjawpkcm0wOiBbSVRIUkVBRF0KaXduMDogbmVlZCBtdWx0aWNh
 c3QgdXBkYXRlIGNhbGxiYWNrCndsYW4wOiBsaW5rIHN0YXRlIGNoYW5nZWQgdG8gRE9XTgpzdHJh
 eSBpcnEwCnVnZW4wLjI6IDxTVE1pY3JvZWxlY3Ryb25pY3M+IGF0IHVzYnVzMCAoZGlzY29ubmVj
 dGVkKXVnZW4xLjI6IDx2ZW5kb3IgMHgwNDYxPiBhdCB1c2J1czEgKGRpc2Nvbm5lY3RlZCkKCnVt
 czA6IGF0IHVodWIxLCBwb3J0IDEsIGFkZHIgMiAoZGlzY29ubmVjdGVkKQp1Z2VuMS4yOiA8dmVu
 ZG9yIDB4MDQ2MT4gYXQgdXNidXMxCnVtczA6IDx2ZW5kb3IgMHgwNDYxIFVTQiBPcHRpY2FsIE1v
 dXNlLCBjbGFzcyAwLzAsIHJldiAyLjAwLzIuMDAsIGFkZHIgMj4gb24gdXNidXMxCnVtczA6IDMg
 YnV0dG9ucyBhbmQgW1hZWl0gY29vcmRpbmF0ZXMgSUQ9MAp1Z2VuMC4yOiA8U1RNaWNyb2VsZWN0
 cm9uaWNzPiBhdCB1c2J1czAKZHJtMDogW0lUSFJFQURdCndsYW4wOiBsaW5rIHN0YXRlIGNoYW5n
 ZWQgdG8gVVAKaXduMDogbmVlZCBtdWx0aWNhc3QgdXBkYXRlIGNhbGxiYWNrCml3bjA6IG5lZWQg
 bXVsdGljYXN0IHVwZGF0ZSBjYWxsYmFjawppd24wOiBuZWVkIG11bHRpY2FzdCB1cGRhdGUgY2Fs
 bGJhY2sKaXduMDogbmVlZCBtdWx0aWNhc3QgdXBkYXRlIGNhbGxiYWNrCndsYW4wOiBsaW5rIHN0
 YXRlIGNoYW5nZWQgdG8gRE9XTgpzdHJheSBpcnEwCmFjcGlfZWMwOiB3YXJuaW5nOiBFQyBkb25l
 IGJlZm9yZSBzdGFydGluZyBldmVudCB3YWl0CnVnZW4wLjI6IDxTVE1pY3JvZWxlY3Ryb25pY3M+
 IGF0IHVzYnVzMCAoZGlzY29ubmVjdGVkKQp1Z2VuMS4yOiA8dmVuZG9yIDB4MDQ2MT4gYXQgdXNi
 dXMxIChkaXNjb25uZWN0ZWQpCnVtczA6IGF0IHVodWIxLCBwb3J0IDEsIGFkZHIgMiAoZGlzY29u
 bmVjdGVkKQp1Z2VuNi4yOiA8dmVuZG9yIDB4MTdlZj4gYXQgdXNidXM2IChkaXNjb25uZWN0ZWQp
 CnVnZW42LjI6IDx2ZW5kb3IgMHgxN2VmPiBhdCB1c2J1czYKdWdlbjAuMjogPFNUTWljcm9lbGVj
 dHJvbmljcz4gYXQgdXNidXMwCmRybTA6IFtJVEhSRUFEXQp3bGFuMDogbGluayBzdGF0ZSBjaGFu
 Z2VkIHRvIFVQCml3bjA6IG5lZWQgbXVsdGljYXN0IHVwZGF0ZSBjYWxsYmFjawppd24wOiBuZWVk
 IG11bHRpY2FzdCB1cGRhdGUgY2FsbGJhY2sKaXduMDogbmVlZCBtdWx0aWNhc3QgdXBkYXRlIGNh
 bGxiYWNrCml3bjA6IG5lZWQgbXVsdGljYXN0IHVwZGF0ZSBjYWxsYmFjawp3bGFuMDogbGluayBz
 dGF0ZSBjaGFuZ2VkIHRvIERPV04Kc3RyYXkgaXJxMAp1Z2VuMC4yOiA8U1RNaWNyb2VsZWN0cm9u
 aWNzPiBhdCB1c2J1czAgKGRpc2Nvbm5lY3RlZCkKdWdlbjAuMjogPFNUTWljcm9lbGVjdHJvbmlj
 cz4gYXQgdXNidXMwCmRybTA6IFtJVEhSRUFEXQp3bGFuMDogbGluayBzdGF0ZSBjaGFuZ2VkIHRv
 IFVQCml3bjA6IG5lZWQgbXVsdGljYXN0IHVwZGF0ZSBjYWxsYmFjawppd24wOiBuZWVkIG11bHRp
 Y2FzdCB1cGRhdGUgY2FsbGJhY2sKaXduMDogbmVlZCBtdWx0aWNhc3QgdXBkYXRlIGNhbGxiYWNr
 Cml3bjA6IG5lZWQgbXVsdGljYXN0IHVwZGF0ZSBjYWxsYmFjawp3bGFuMDogbGluayBzdGF0ZSBj
 aGFuZ2VkIHRvIERPV04Kc3RyYXkgaXJxMAp1Z2VuMC4yOiA8U1RNaWNyb2VsZWN0cm9uaWNzPiBh
 dCB1c2J1czAgKGRpc2Nvbm5lY3RlZCkKdXNidXMyOiBwb3J0IHJlc2V0IHRpbWVvdXQKdWh1Yl9y
 ZWF0dGFjaF9wb3J0OjM3MTogcG9ydCAyIHJlc2V0IGZhaWxlZCwgZXJyb3I9VVNCX0VSUl9USU1F
 T1VUCnVodWJfcmVhdHRhY2hfcG9ydDo0NTg6IGRldmljZSBwcm9ibGVtIChVU0JfRVJSX1RJTUVP
 VVQpLCBkaXNhYmxpbmcgcG9ydCAyCnVnZW42LjI6IDx2ZW5kb3IgMHgxN2VmPiBhdCB1c2J1czYg
 KGRpc2Nvbm5lY3RlZCkKdXNidXM2OiBwb3J0IHJlc2V0IHRpbWVvdXQKdWh1Yl9yZWF0dGFjaF9w
 b3J0OjM3MTogcG9ydCA1IHJlc2V0IGZhaWxlZCwgZXJyb3I9VVNCX0VSUl9USU1FT1VUCnVodWJf
 cmVhdHRhY2hfcG9ydDo0NTg6IGRldmljZSBwcm9ibGVtIChVU0JfRVJSX1RJTUVPVVQpLCBkaXNh
 YmxpbmcgcG9ydCA1CmRybTA6IFtJVEhSRUFEXQp1Z2VuNi4yOiA8dmVuZG9yIDB4MTdlZj4gYXQg
 dXNidXM2CndsYW4wOiBsaW5rIHN0YXRlIGNoYW5nZWQgdG8gVVAKaXduMDogbmVlZCBtdWx0aWNh
 c3QgdXBkYXRlIGNhbGxiYWNrCml3bjA6IG5lZWQgbXVsdGljYXN0IHVwZGF0ZSBjYWxsYmFjawpp
 d24wOiBuZWVkIG11bHRpY2FzdCB1cGRhdGUgY2FsbGJhY2sK
 --000325559e2695b4640477520d3a--
From oxyd.oxyd at gmail.com  Sun Nov  1 17:32:41 2009
From: oxyd.oxyd at gmail.com (=?UTF-8?Q?Ond=C5=99ej_Majerech?=)
Date: Sun Nov  1 17:32:50 2009
Subject: HP LaserJet P1005 USB Printer under FreeBSD 8.0-RC2
In-Reply-To: <200911011713.07994.hselasky@c2i.net>
References: <f60d361f0911010658y75e85a43m8a43c1074dc022e5@mail.gmail.com>
	<200911011713.07994.hselasky@c2i.net>
Message-ID: <f60d361f0911010932y9715d8ft9e7112e1ca07d29e@mail.gmail.com>

2009/11/1 Hans Petter Selasky <hselasky@c2i.net>:
> On Sunday 01 November 2009 15:58:50 Ond?ej Majerech wrote:
>> Hello list,
>>
>> I had my HP P1005 printer working just fine under 7.2-RELEASE, but I
>> just updated to 8.0-RC2 and the driver doesn't seem to like the new
>> USB stack.
>
> How did you update?

Source update -- csup'd to RELENG_8, then followed the instructions in Handbook.

>
> Did you recompile foo2xqx ?

Yes.  Actually, I did pkg_delete -a and then rebuilt everything from scratch.

~ Ondra
From hselasky at c2i.net  Sun Nov  1 17:34:51 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Nov  1 17:34:57 2009
Subject: HP LaserJet P1005 USB Printer under FreeBSD 8.0-RC2
In-Reply-To: <f60d361f0911010932y9715d8ft9e7112e1ca07d29e@mail.gmail.com>
References: <f60d361f0911010658y75e85a43m8a43c1074dc022e5@mail.gmail.com>
	<200911011713.07994.hselasky@c2i.net>
	<f60d361f0911010932y9715d8ft9e7112e1ca07d29e@mail.gmail.com>
Message-ID: <200911011836.03573.hselasky@c2i.net>

On Sunday 01 November 2009 18:32:39 Ond?ej Majerech wrote:
> 2009/11/1 Hans Petter Selasky <hselasky@c2i.net>:
> > On Sunday 01 November 2009 15:58:50 Ond?ej Majerech wrote:
> >> Hello list,
> >>
> >> I had my HP P1005 printer working just fine under 7.2-RELEASE, but I
> >> just updated to 8.0-RC2 and the driver doesn't seem to like the new
> >> USB stack.
> >
> > How did you update?
>
> Source update -- csup'd to RELENG_8, then followed the instructions in
> Handbook.
>
> > Did you recompile foo2xqx ?
>
> Yes.  Actually, I did pkg_delete -a and then rebuilt everything from
> scratch.
>
> ~ Ondra

If you need to cat some firmware somwhere first, then check:

/dev/usb/X.Y.Z, where Z is the endpoint.

--HPS
From oxyd.oxyd at gmail.com  Sun Nov  1 18:09:41 2009
From: oxyd.oxyd at gmail.com (=?UTF-8?Q?Ond=C5=99ej_Majerech?=)
Date: Sun Nov  1 18:09:47 2009
Subject: HP LaserJet P1005 USB Printer under FreeBSD 8.0-RC2
In-Reply-To: <200911011836.03573.hselasky@c2i.net>
References: <f60d361f0911010658y75e85a43m8a43c1074dc022e5@mail.gmail.com>
	<200911011713.07994.hselasky@c2i.net>
	<f60d361f0911010932y9715d8ft9e7112e1ca07d29e@mail.gmail.com>
	<200911011836.03573.hselasky@c2i.net>
Message-ID: <f60d361f0911011009g1b93fc81yad400ab57572649f@mail.gmail.com>

2009/11/1 Hans Petter Selasky <hselasky@c2i.net>:
> On Sunday 01 November 2009 18:32:39 Ond?ej Majerech wrote:
>> 2009/11/1 Hans Petter Selasky <hselasky@c2i.net>:
>> > On Sunday 01 November 2009 15:58:50 Ond?ej Majerech wrote:
>> >> Hello list,
>> >>
>> >> I had my HP P1005 printer working just fine under 7.2-RELEASE, but I
>> >> just updated to 8.0-RC2 and the driver doesn't seem to like the new
>> >> USB stack.
>> >
>> > How did you update?
>>
>> Source update -- csup'd to RELENG_8, then followed the instructions in
>> Handbook.
>>
>> > Did you recompile foo2xqx ?
>>
>> Yes. ?Actually, I did pkg_delete -a and then rebuilt everything from
>> scratch.
>>
>> ~ Ondra
>
> If you need to cat some firmware somwhere first, then check:
>
> /dev/usb/X.Y.Z, where Z is the endpoint.
>

Wow, this was much easier than I'd thought.  cat'ing the firmware to
/dev/usb/2.2.1 indeed did the trick.

Thanks for the help.

~ Ondra
From torfinn.ingolfsen at broadpark.no  Sun Nov  1 20:32:04 2009
From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen)
Date: Sun Nov  1 20:32:10 2009
Subject: usb thermometer - TEMPer - FreeBSD
In-Reply-To: <20090414235727.38d16ee1.torfinn.ingolfsen@broadpark.no>
References: <20090414235727.38d16ee1.torfinn.ingolfsen@broadpark.no>
Message-ID: <20091101213154.cf76de69.torfinn.ingolfsen@broadpark.no>

On Tue, 14 Apr 2009 23:57:27 +0200
Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no> wrote:

> I got a new usb gadget, a TEMPer[1]. According to info on the net,

A small update. I tried this gadget with FreeBSD 8.0-rc2.
Without uchcom loaded it prints this in /var/log/messages:
Nov  1 21:25:33 kg-t2 root: Unknown USB device: vendor 0x4348 product 0x5523 bus uhub0
Nov  1 21:25:33 kg-t2 kernel: ugen0.2: <vendor 0x4348> at usbus0

If I insert the gadget after loading the uchcom driver, the machine panics. The same happens if I load the driver with the gadget inserted. No core dump.

I've trie this on two different machines, one running the i386 and the other the amd64 version of FreeBSD 8.0-RC2.
Both panics with the uchcom driver and this gadget.

References:
1) http://www.dealextreme.com/details.dx/sku.7003
-- 
Regards,
Torfinn Ingolfsen

From hselasky at c2i.net  Sun Nov  1 21:08:24 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Nov  1 21:08:32 2009
Subject: usb thermometer - TEMPer - FreeBSD
In-Reply-To: <20091101213154.cf76de69.torfinn.ingolfsen@broadpark.no>
References: <20090414235727.38d16ee1.torfinn.ingolfsen@broadpark.no>
	<20091101213154.cf76de69.torfinn.ingolfsen@broadpark.no>
Message-ID: <200911012209.37403.hselasky@c2i.net>

On Sunday 01 November 2009 21:31:54 Torfinn Ingolfsen wrote:
> On Tue, 14 Apr 2009 23:57:27 +0200
>
> Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no> wrote:
> > I got a new usb gadget, a TEMPer[1]. According to info on the net,
>
> A small update. I tried this gadget with FreeBSD 8.0-rc2.
> Without uchcom loaded it prints this in /var/log/messages:
> Nov  1 21:25:33 kg-t2 root: Unknown USB device: vendor 0x4348 product
> 0x5523 bus uhub0 Nov  1 21:25:33 kg-t2 kernel: ugen0.2: <vendor 0x4348> at
> usbus0
>
> If I insert the gadget after loading the uchcom driver, the machine panics.
> The same happens if I load the driver with the gadget inserted. No core
> dump.
>
> I've trie this on two different machines, one running the i386 and the
> other the amd64 version of FreeBSD 8.0-RC2. Both panics with the uchcom
> driver and this gadget.
>
> References:
> 1) http://www.dealextreme.com/details.dx/sku.7003

Hi,

Try to fetch: 

/sys/dev/usb/serial/uchcom.c 

From FreeBSD 9-current and rebuild the uchcom module or kernel.

Known issue I think.

--HPS

From bugmaster at FreeBSD.org  Mon Nov  2 11:07:05 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov  2 11:09:54 2009
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200911021107.nA2B75mB033755@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/140160   usb        USB ports are no longer "active" after ACPI suspend/re
o usb/139990   usb        [panic] Kernel frequently panics after printing
o usb/139598   usb        [umass] CAM reports "xptioctl: put "device pass" in yo
o usb/139243   usb        [uhci] unplug prolific USB serial -> uhci_abort_xfer: 
o usb/139142   usb        [regression] ehci drivers (NVIDIA nForce4 USB 2.0 cont
o usb/138915   usb        [patch][usb8][usb67] add support for SheevaPlug serial
o usb/138904   usb        [rum] unpluging USB wifi card panics system
f usb/138882   usb        [ohci] [panic] Can't install FreeBSD 7.2 due to ohci p
o usb/138879   usb        [uftdi] [patch] Patch to add support for CTI USB-Mini 
o usb/138798   usb        8.0-BETA4 can't boot from USB flash drive [regression]
o usb/138675   usb        [usb8] [panic] page fault, perhaps in USB
o usb/138659   usb        [usb8][uftdi] driver broken in RELENG_8/CURRENT
o usb/138563   usb        [usb8] [patch] Increase buffer sizes to accomodate lon
o usb/138389   usb        [usb8] [patch] NULL pointer dereference in usb_endpoin
o usb/138175   usb        [usb67] [boot] System cannot boot, when USB reader wit
o usb/138172   usb        Additional dev id for u3g (Option mini PCIe)
o usb/138138   usb        Novatel U760 for u3g (Verizon and Bell Canada)
o usb/138124   usb        [usb8] Axed uaudio functionality in the usbng (alterna
o usb/138119   usb        MultiBay CDROM (propably on USB bus) is not recognized
o usb/137872   usb        slow booting on usb flash drive
f usb/137848   usb        Page fault when using an USB bluetooth adapter
o usb/137806   usb        [ukbd] USB keyboard doesn't work until it's unplugged
o usb/137763   usb        [usb67][ukbd] Logitech wireless keyboard media keys no
o usb/137616   usb        [usb67][usb8][usbdevs] [patch]: usbdevs update: Please
o usb/137377   usb        [usb8] Support for Huawei E180
o usb/137341   usb        [usb8][rum] driver if_rum doesn't work at all and thro
p usb/137226   usb        [usb67][patch] quirk for Philips extern USB disk
o usb/137190   usb        [usb8][patch] inhibit spurious button releases for som
o usb/137189   usb        [usb8][patch] create and use sysctl nodes for HID repo
p usb/137188   usb        [usb8][patch] correctly handle USB report descriptors 
o usb/137129   usb        SteelSeries Ikari USB laser mouse not attaching
p usb/136761   usb        [usbdevs][usb67][patch] Teach usbdevs / u3g(4) about H
o usb/135938   usb        [aue] aue driver only passes traffic in promisc mode
f usb/135857   usb        RTL8187 Wireless Adapter
o usb/135575   usb        [usbdevs] [patch] Add HTC Wizard phone vid/pid informa
o usb/135542   usb        [keyboard] boot loader does not work with a usb keyboa
p usb/135372   usb        [usb67][umass] Quirk report for Teclast TL-C300 usb me
o usb/135348   usb        [umass] USB Drive Hangs with ZFS (JMicron USB2/eSata)
o usb/135206   usb        machine reboots when inserted USB device
o usb/135200   usb        SAMSUNG i740 usb mass: Synchronize cache failed, statu
o usb/135182   usb        UMASS quirk - Olympus FE20 camera
o usb/134950   usb        Lowering DTR for USB-modem via ubsa is not possible
o usb/134633   usb        Add support for WILLCOM03(SHARP smart phone)
o usb/134631   usb        [usbdevs] [patch] WiSPY DBx support requires usb tweak
o usb/134299   usb        Kernel Panic plugging in MF626 USB UMTS Stick u3g
o usb/134193   usb        System freeze on usb MP3 player insertion
o usb/134117   usb        [Patch] Add support for 'Option GlobeTrotter HSDPA Mod
o usb/134085   usb        [umass] Adding usb quirk for Sony USB flash drive
o usb/133989   usb        [newusb] [ukbd] USB keyboard dead at mountroot> prompt
o usb/133712   usb        [ural] [patch] RE: Fixed an issue with ural(4) that wa
o usb/133390   usb        umass crashes system in 7.1 when Olympus D-540 attache
o usb/133296   usb        [rum] driver not working properly in hostap mode
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] [rum] Kernel panic after NOMEM caused by
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
o 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/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/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
o 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
s 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] [panic] enabling usb keyboard and mouse support
o usb/127248   usb        [ucom] panic while uplcom devices attaach and detach
o usb/127222   usb        [ohci] Regression in 7.0 usb storage generic driver
o usb/126884   usb        [ugen] [patch] Bug in buffer handling in ugen.c
o usb/126848   usb        [usb]: USB Keyboard hangs during Installation
o usb/126740   usb        [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be
o usb/126519   usb        [usb] [panic] panic when plugging in an iphone
o kern/126396  usb        [panic] kernel panic after unplug USB Bluetooth device
o usb/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
p 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 kern/124130  usb        [usb] gmirror fails to start usb devices that were pre
o usb/123969   usb        [usb] Supermicro H8SMi-2 usb problem: port reset faile
o usb/123714   usb        [usb] [panic] Panic when hald-storage-probe runs with 
o usb/123691   usb        usbd(8): usbd hangs
o usb/123690   usb        [usb] [panic] Panic on USB device insertion when usb l
o usb/123611   usb        [usb] BBB reset failed, STALLED from Imation/Mitsumi U
o usb/123509   usb        [umass] continuous reset Samsung SGH-G600 phone
o usb/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        [new driver] [patch] New driver for Sierra Wireless 3G
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] [panic] FreeBSD fails to boot with usb legacy s
o usb/121232   usb        [usb] [panic] USB CardBus card removal causes reboot s
p usb/121184   usb        [uipaq] [patch] add ids from linux ipaq driver (plus a
o usb/121169   usb        [umass] Issues with usb mp3 player
o usb/121045   usb        [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS
o usb/120786   usb        [usb] [panic] Kernel panic when forced umount of a det
o usb/120729   usb        [panic] fault while in kernel mode with connecting USB
o usb/120572   usb        [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/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        [usb67] [usb8] [umass] [patch] Problem with connection
o conf/114013  usb        [patch] WITHOUT_USB allow to compil a lot of USB stuff
o usb/113060   usb        [usb67] [ulpt] [patch] Samsung printer not working in 
o usb/110856   usb        [usb67] [ugen] [patch] interrupt in msgs are truncated
s usb/108344   usb        [usb67] [atausb] [panic] kernel with atausb panics whe
o usb/107924   usb        [usb67] usbd(8) does not call detach
o usb/107827   usb        [usb67] [ohci] [panic] ohci_add_done addr not found
o usb/107388   usb        [usb67] [usb8] [new driver] [patch] add utoppy device 
o usb/107243   usb        [usb67] [cam] [quirk] [patch] Apacer USB Flash Drive q
o usb/106041   usb        [usb67] [usb8] [request] FreeBSD does not recognise Mu
o usb/105361   usb        [usb67] [panic] Kernel panic during unmounting mass st
s usb/103917   usb        [usb67] [uhub] USB driver reports "Addr 0 should never
o usb/103418   usb        [usb67] [usb8] [patch] [request] usbhidctl(8) add abil
o usb/103046   usb        [usb67] [ulpt] [patch] ulpt event driven I/O with sele
o usb/101775   usb        [usb67] [usb8] [libusbhid] [patch] possible error in r
o usb/101761   usb        [usb67] [patch] [request] usb.h: increase maximal size
o usb/100746   usb        [usb67] [ukbd] system does not boot due to USB keyboar
o usb/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/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/83977    usb        [ucom] [panic] ucom1: open bulk out error (addr 2): IN
o usb/83863    usb        [ugen] Communication problem between opensc/openct via
o usb/83756    usb        [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe
o usb/83563    usb        [umass] [panic] Page Fault while detaching Mpman Usb d
o usb/83504    usb        [kernel] [patch] SpeedTouch USB stop working on recent
o usb/82660    usb        [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic
s usb/82569    usb        [umass] [panic] USB mass storage plug/unplug causes sy
o usb/82520    usb        [udbp] [reboot] Reboot when USL101 connected
o usb/82350    usb        [ucom] [panic] null pointer dereference in USB stack
o usb/81621    usb        [ehci] [hang] external hd hangs under load on ehci
o usb/80935    usb        [uvisor] [patch] uvisor.c is not work with CLIE TH55.
o usb/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        [sound] [hang] Use of sound mixer causes system freeze
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] [regression] 5.3-STABLE(2005 1/4) detect USB h
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

311 problems total.

From dlangille at myyearbook.com  Mon Nov  2 13:21:21 2009
From: dlangille at myyearbook.com (Dan Langille)
Date: Mon Nov  2 13:21:27 2009
Subject: MS USB mouse does not work
In-Reply-To: <3a142e750910211210k7c99ec54q605e4c3ef3de9c4c@mail.gmail.com>
References: <6dd019370906101118k6c26ccat5596dbe1ba03ebe5@mail.gmail.com>
	<6dd019370910210726x49ce12f5uf06a17a039d2c9d0@mail.gmail.com>
	<3a142e750910211210k7c99ec54q605e4c3ef3de9c4c@mail.gmail.com>
Message-ID: <6dd019370911020521g9eff193jd9f26589dc5afcd7@mail.gmail.com>

On Wed, Oct 21, 2009 at 2:10 PM, Paul B Mahol <onemda@gmail.com> wrote:

> On 10/21/09, Dan Langille <dlangille@myyearbook.com> wrote:
> > bump
> >
> > On Wed, Jun 10, 2009 at 2:18 PM, Dan Langille
> > <dlangille@myyearbook.com>wrote:
> >
> >> I'm running FreeBSD 7.2-STABLE from Tue May 26.
> >>
> >> I have an MS keyboard and mouse, both of which are wireless and
> >> operate through the same USB transceiver.  The keyboard works.  The
> >> mouse does not.
> >>
> >> From /var/run/dmesg.boot:
> >>
> >> ukbd0: <Microsoft Microsoft\M-. 2.4GHz Transceiver V1.0, class 0/0,
> >> rev 2.00/2.50, addr 3> on uhub7
> >> kbd2 at ukbd0
> >> uhid0: <Microsoft Microsoft\M-. 2.4GHz Transceiver V1.0, class 0/0,
> >> rev 2.00/2.50, addr 3> on uhub7
> >>
> >> I see nothing related to the mouse.  Any ideas.  It's a really nice
> >> mouse, otherwise.  ;)
>
> Try with 8.0, maybe something improved ...
> If not, than the only option is to write mouse driver, if this particular
> mouse
> doesnt need some kind of quirk ....
>

FYI, I upgraded to FreeBSD 8.0-RC2.

Mouse and keyboard both work.  :)

-- 
Dan Langille
myYearbook.com
From achilov-rn at askd.ru  Tue Nov  3 03:36:24 2009
From: achilov-rn at askd.ru (Rashid N. Achilov)
Date: Tue Nov  3 03:36:35 2009
Subject: MS USB mouse does not work
In-Reply-To: <6dd019370911020521g9eff193jd9f26589dc5afcd7@mail.gmail.com>
References: <6dd019370906101118k6c26ccat5596dbe1ba03ebe5@mail.gmail.com>
	<3a142e750910211210k7c99ec54q605e4c3ef3de9c4c@mail.gmail.com>
	<6dd019370911020521g9eff193jd9f26589dc5afcd7@mail.gmail.com>
Message-ID: <200911030936.19878.achilov-rn@askd.ru>

On Monday 02 November 2009, Dan Langille wrote:

> > Try with 8.0, maybe something improved ...
> > If not, than the only option is to write mouse driver, if this particular
> > mouse
> > doesnt need some kind of quirk ....
> >
> 
> FYI, I upgraded to FreeBSD 8.0-RC2.
> 
> Mouse and keyboard both work.  :)

Awaiting at least 8.0-RELEASE (but preferrable 8.1-RELEASE - "dot zero" still 
will buggy). But this is good news. Probably, my Genius Optical Value and 
Microsoft 5000 twins will work :-)
-- 
   With Best Regards.
   Rashid N. Achilov (RNA1-RIPE), JID: citycat4@jabber.org
   OOO "ACK" telecommunications administrator, e-mail: achilov-rn [at] askd.ru
   PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A
From sprague at msu.edu  Tue Nov  3 04:00:17 2009
From: sprague at msu.edu (Rick Sprague)
Date: Tue Nov  3 04:00:26 2009
Subject: usb/140236: Labels wiped on external Journaled USB HDD on 8.0-RC2
Message-ID: <200911030357.nA33v91O094425@www.freebsd.org>


>Number:         140236
>Category:       usb
>Synopsis:       Labels wiped on external Journaled USB HDD on 8.0-RC2
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 03 04:00:09 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Rick Sprague
>Release:        8.0-RC2
>Organization:
>Environment:
FreeBSD XXXXXX 8.0-RC2 FreeBSD 8.0-RC2 #0: Sun Oct 25 08:55:51 UTC 2009     root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
This happens after reboot. All the labels on the external USB 450GB HDD, which is gjournaled, are erased.  This drive I know works fine and am pretty sure it's a software issue.  I thought this was a fluke, but I'm reporting this bug after it happened for the 2nd time.  I've been able to recover the data by relabeling the disk w/ the same sizes.
>How-To-Repeat:
Reboot
>Fix:
If you know the exact label sizes, just renter and untoggle newfs.

>Release-Note:
>Audit-Trail:
>Unformatted:
From sebastian.huber at embedded-brains.de  Tue Nov  3 10:00:15 2009
From: sebastian.huber at embedded-brains.de (Sebastian Huber)
Date: Tue Nov  3 10:00:22 2009
Subject: usb/140242: dev/usb/controller/ehci_ix4xx.c shortcomings
Message-ID: <200911030952.nA39qqlq082386@www.freebsd.org>


>Number:         140242
>Category:       usb
>Synopsis:       dev/usb/controller/ehci_ix4xx.c shortcomings
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 03 10:00:12 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Sebastian Huber
>Release:        9-current
>Organization:
embedded brains GmbH
>Environment:
>Description:
In ehci_ixp_attach() setting of sc->sc_bus.usbrev is superfluous since this is also set in ehci_init().

Calling ehci_reset() without a valid sc->sc_offs value makes no sense.
>How-To-Repeat:

>Fix:
Index: ehci_ixp4xx.c                                               
===================================================================
--- ehci_ixp4xx.c       (revision 198848)                          
+++ ehci_ixp4xx.c       (working copy)                             
@@ -157,8 +157,6 @@                                                
                return (ENOMEM);                                   
        }                                                          
                                                                   
-       sc->sc_bus.usbrev = USB_REV_2_0;                           
-                                                                  
        /* NB: hints fix the memory location and irq */            
                                                                   
        rid = 0;                                                   
@@ -230,7 +228,6 @@                                                
                     | EHCI_SCFLG_BIGEMMIO                         
                     | EHCI_SCFLG_NORESTERM                        
                     ;                                             
-       (void) ehci_reset(sc);                                     
                                                                   
        err = ehci_init(sc);                                       
        if (!err) {

>Release-Note:
>Audit-Trail:
>Unformatted:
From hselasky at c2i.net  Tue Nov  3 10:09:29 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Nov  3 10:09:35 2009
Subject: usb/140242: dev/usb/controller/ehci_ix4xx.c shortcomings
In-Reply-To: <200911030952.nA39qqlq082386@www.freebsd.org>
References: <200911030952.nA39qqlq082386@www.freebsd.org>
Message-ID: <200911031108.33332.hselasky@c2i.net>

On Tuesday 03 November 2009 10:52:52 Sebastian Huber wrote:
> >Number:         140242
> >Category:       usb
> >Synopsis:       dev/usb/controller/ehci_ix4xx.c shortcomings
> >Confidential:   no
> >Severity:       non-critical
> >Priority:       low
> >Responsible:    freebsd-usb
> >State:          open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Tue Nov 03 10:00:12 UTC 2009
> >Closed-Date:
> >Last-Modified:
> >Originator:     Sebastian Huber
> >Release:        9-current
> >Organization:
>
> embedded brains GmbH
>
> >Environment:
> >Description:
>
> In ehci_ixp_attach() setting of sc->sc_bus.usbrev is superfluous since this
> is also set in ehci_init().
>
> Calling ehci_reset() without a valid sc->sc_offs value makes no sense.
>
> >How-To-Repeat:
> >
> >Fix:
>
> Index: ehci_ixp4xx.c
> ===================================================================
> --- ehci_ixp4xx.c       (revision 198848)
> +++ ehci_ixp4xx.c       (working copy)
> @@ -157,8 +157,6 @@
>                 return (ENOMEM);
>         }
>
> -       sc->sc_bus.usbrev = USB_REV_2_0;
> -
>         /* NB: hints fix the memory location and irq */
>
>         rid = 0;
> @@ -230,7 +228,6 @@
>
>                      | EHCI_SCFLG_BIGEMMIO
>                      | EHCI_SCFLG_NORESTERM
>
>                      ;
> -       (void) ehci_reset(sc);
>
>         err = ehci_init(sc);
>         if (!err) {
>
> >Release-Note:
> >Audit-Trail:
> >Unformatted:

Hi,

Thanks for your patch.

What is the correct "sc->sc_offs" value? The sc_offs field is used by more 
than reset, and should be set correctly. I.E. The right solution is not to 
remove the ehci_reset() call.

--HPS

From hselasky at c2i.net  Tue Nov  3 10:10:02 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Nov  3 10:10:09 2009
Subject: usb/140242: dev/usb/controller/ehci_ix4xx.c shortcomings
Message-ID: <200911031010.nA3AA2Tx067711@freefall.freebsd.org>

The following reply was made to PR usb/140242; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Sebastian Huber <sebastian.huber@embedded-brains.de>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/140242: dev/usb/controller/ehci_ix4xx.c shortcomings
Date: Tue, 3 Nov 2009 11:08:32 +0100

 On Tuesday 03 November 2009 10:52:52 Sebastian Huber wrote:
 > >Number:         140242
 > >Category:       usb
 > >Synopsis:       dev/usb/controller/ehci_ix4xx.c shortcomings
 > >Confidential:   no
 > >Severity:       non-critical
 > >Priority:       low
 > >Responsible:    freebsd-usb
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Tue Nov 03 10:00:12 UTC 2009
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Sebastian Huber
 > >Release:        9-current
 > >Organization:
 >
 > embedded brains GmbH
 >
 > >Environment:
 > >Description:
 >
 > In ehci_ixp_attach() setting of sc->sc_bus.usbrev is superfluous since this
 > is also set in ehci_init().
 >
 > Calling ehci_reset() without a valid sc->sc_offs value makes no sense.
 >
 > >How-To-Repeat:
 > >
 > >Fix:
 >
 > Index: ehci_ixp4xx.c
 > ===================================================================
 > --- ehci_ixp4xx.c       (revision 198848)
 > +++ ehci_ixp4xx.c       (working copy)
 > @@ -157,8 +157,6 @@
 >                 return (ENOMEM);
 >         }
 >
 > -       sc->sc_bus.usbrev = USB_REV_2_0;
 > -
 >         /* NB: hints fix the memory location and irq */
 >
 >         rid = 0;
 > @@ -230,7 +228,6 @@
 >
 >                      | EHCI_SCFLG_BIGEMMIO
 >                      | EHCI_SCFLG_NORESTERM
 >
 >                      ;
 > -       (void) ehci_reset(sc);
 >
 >         err = ehci_init(sc);
 >         if (!err) {
 >
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 
 Hi,
 
 Thanks for your patch.
 
 What is the correct "sc->sc_offs" value? The sc_offs field is used by more 
 than reset, and should be set correctly. I.E. The right solution is not to 
 remove the ehci_reset() call.
 
 --HPS
 
From sebastian.huber at embedded-brains.de  Tue Nov  3 10:28:22 2009
From: sebastian.huber at embedded-brains.de (Sebastian Huber)
Date: Tue Nov  3 10:28:29 2009
Subject: usb/140242: dev/usb/controller/ehci_ix4xx.c shortcomings
In-Reply-To: <200911031010.nA3AA2Tx067711@freefall.freebsd.org>
References: <200911031010.nA3AA2Tx067711@freefall.freebsd.org>
Message-ID: <4AF005C1.7090007@embedded-brains.de>

Hans Petter Selasky wrote:
[...]
>  What is the correct "sc->sc_offs" value? The sc_offs field is used by more 
>  than reset, and should be set correctly. I.E. The right solution is not to 
>  remove the ehci_reset() call.
[...]

The sc->sc_offs value is initialized early during ehci_init().  Afterwards a
ehci_reset() is ok, but before it is not good.

-- 
Sebastian Huber, embedded brains GmbH

Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone   : +49 89 18 90 80 79-6
Fax     : +49 89 18 90 80 79-9
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine gesch?ftliche Mitteilung im Sinne des EHUG.
From gavin at FreeBSD.org  Tue Nov  3 10:43:06 2009
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Tue Nov  3 10:43:14 2009
Subject: aue0 detected as ue0 on 8.0-RC2
In-Reply-To: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com>
References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com>
Message-ID: <1257243047.98619.8.camel@buffy.york.ac.uk>

[freebsd-current cc'd, as that was where the thread started, but this
probably belongs on -usb, replies should go there]

On Sat, 2009-10-31 at 21:59 +0100, Rick van der Zwet wrote:
> The first net interface of a aue(4) define used to be called aue0
> afaik. But is now called ue0 (declared in usb/net/usb_ethernet.c). (no
> sign of ue(4) btw).
> 
> I was looking in the UPDATING, man, mailinglists freebsd-usb@ and
> freebsd-current@. But I could not find the reason why the naming
> convention on this aue differs from the regular stuff, anybody?
> 
> /Rick
> 
> quick# dmesg | tail -8
> ugen1.3: <ADMtek> at usbus1
> aue0: <ADMtek USB To LAN Converter, rev 2.00/1.01, addr 3> on usbus1
> miibus1: <MII bus> on aue0
> ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus1
> ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> ue0: <USB Ethernet> on aue0
> ue0: Ethernet address: 00:00:e8:00:11:36
> ue0: link state changed to DOWN
> 
> quick# ifconfig -l
> bfe0 lo0 ue0

Hmm, this looks like a serious bug, possibly in the new USB subsystem
(HPS CC'd).

I've got an axe(4) device, which also does the same:

ugen7.3: <vendor 0x0b95> at usbus7
axe0: <vendor 0x0b95 product 0x7720, rev 2.00/0.01, addr 3> on usbus7
axe0: PHYADDR 0xe0:0x10
miibus1: <MII bus> on axe0
ukphy0: <Generic IEEE 802.3u media interface> PHY 16 on miibus1
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ue0: <USB Ethernet> on axe0
ue0: Ethernet address: 00:50:b6:05:57:a7
ue0: link state changed to DOWN

Gavin
From hselasky at freebsd.org  Tue Nov  3 11:04:17 2009
From: hselasky at freebsd.org (Hans Petter Selasky)
Date: Tue Nov  3 11:04:24 2009
Subject: aue0 detected as ue0 on 8.0-RC2
In-Reply-To: <1257243047.98619.8.camel@buffy.york.ac.uk>
References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com>
	<1257243047.98619.8.camel@buffy.york.ac.uk>
Message-ID: <200911031203.22103.hselasky@freebsd.org>

On Tuesday 03 November 2009 11:10:47 Gavin Atkinson wrote:
> [freebsd-current cc'd, as that was where the thread started, but this
> probably belongs on -usb, replies should go there]
>
> On Sat, 2009-10-31 at 21:59 +0100, Rick van der Zwet wrote:
> > The first net interface of a aue(4) define used to be called aue0
> > afaik. But is now called ue0 (declared in usb/net/usb_ethernet.c). (no
> > sign of ue(4) btw).
> >
> > I was looking in the UPDATING, man, mailinglists freebsd-usb@ and
> > freebsd-current@. But I could not find the reason why the naming
> > convention on this aue differs from the regular stuff, anybody?
> >
> > /Rick
> >
> > quick# dmesg | tail -8
> > ugen1.3: <ADMtek> at usbus1
> > aue0: <ADMtek USB To LAN Converter, rev 2.00/1.01, addr 3> on usbus1
> > miibus1: <MII bus> on aue0
> > ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus1
> > ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > ue0: <USB Ethernet> on aue0
> > ue0: Ethernet address: 00:00:e8:00:11:36
> > ue0: link state changed to DOWN
> >
> > quick# ifconfig -l
> > bfe0 lo0 ue0
>
> Hmm, this looks like a serious bug, possibly in the new USB subsystem
> (HPS CC'd).
>
> I've got an axe(4) device, which also does the same:
>
> ugen7.3: <vendor 0x0b95> at usbus7
> axe0: <vendor 0x0b95 product 0x7720, rev 2.00/0.01, addr 3> on usbus7
> axe0: PHYADDR 0xe0:0x10
> miibus1: <MII bus> on axe0
> ukphy0: <Generic IEEE 802.3u media interface> PHY 16 on miibus1
> ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> ue0: <USB Ethernet> on axe0
> ue0: Ethernet address: 00:50:b6:05:57:a7
> ue0: link state changed to DOWN

Hi,

All USB ethernet adapters are now named ue0. You will get one axe0 event and 
one ue0 event. So there should be no problems regarding devd.conf  .

--HPS

From hselasky at c2i.net  Tue Nov  3 11:07:14 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Nov  3 11:07:26 2009
Subject: aue0 detected as ue0 on 8.0-RC2
In-Reply-To: <200911031203.22103.hselasky@freebsd.org>
References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com>
	<1257243047.98619.8.camel@buffy.york.ac.uk>
	<200911031203.22103.hselasky@freebsd.org>
Message-ID: <200911031206.19512.hselasky@c2i.net>

On Tuesday 03 November 2009 12:03:21 Hans Petter Selasky wrote:

> Hi,
>
> All USB ethernet adapters are now named ue0. You will get one axe0 event
> and one ue0 event. So there should be no problems regarding devd.conf  .
>
> --HPS

s/ue0/ueN/

--HPS

From hselasky at c2i.net  Tue Nov  3 11:15:28 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Nov  3 11:15:41 2009
Subject: usb/140242: dev/usb/controller/ehci_ix4xx.c shortcomings
In-Reply-To: <200911030952.nA39qqlq082386@www.freebsd.org>
References: <200911030952.nA39qqlq082386@www.freebsd.org>
Message-ID: <200911031159.33427.hselasky@c2i.net>

On Tuesday 03 November 2009 10:52:52 Sebastian Huber wrote:
> >Number:         140242
> >Category:       usb
> >Synopsis:       dev/usb/controller/ehci_ix4xx.c shortcomings
> >Confidential:   no
> >Severity:       non-critical
> >Priority:       low
> >Responsible:    freebsd-usb
> >State:          open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Tue Nov 03 10:00:12 UTC 2009
> >Closed-Date:
> >Last-Modified:
> >Originator:     Sebastian Huber
> >Release:        9-current
> >Organization:
>
> embedded brains GmbH
>
> >Environment:
> >Description:
>
> In ehci_ixp_attach() setting of sc->sc_bus.usbrev is superfluous since this
> is also set in ehci_init().
>
> Calling ehci_reset() without a valid sc->sc_offs value makes no sense.
>
> >How-To-Repeat:
> >
> >Fix:
>
> Index: ehci_ixp4xx.c
> ===================================================================
> --- ehci_ixp4xx.c       (revision 198848)
> +++ ehci_ixp4xx.c       (working copy)
> @@ -157,8 +157,6 @@
>                 return (ENOMEM);
>         }
>
> -       sc->sc_bus.usbrev = USB_REV_2_0;
> -
>         /* NB: hints fix the memory location and irq */
>
>         rid = 0;
> @@ -230,7 +228,6 @@
>
>                      | EHCI_SCFLG_BIGEMMIO
>                      | EHCI_SCFLG_NORESTERM
>
>                      ;
> -       (void) ehci_reset(sc);
>
>         err = ehci_init(sc);
>         if (!err) {
>
> >Release-Note:
> >Audit-Trail:
> >Unformatted:
>

Committed to USB P4:

http://p4web.freebsd.org/chv.cgi?CH=170109

--HPS

From hselasky at c2i.net  Tue Nov  3 11:20:04 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Nov  3 11:20:51 2009
Subject: usb/140242: dev/usb/controller/ehci_ix4xx.c shortcomings
Message-ID: <200911031120.nA3BK472030689@freefall.freebsd.org>

The following reply was made to PR usb/140242; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Sebastian Huber <sebastian.huber@embedded-brains.de>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/140242: dev/usb/controller/ehci_ix4xx.c shortcomings
Date: Tue, 3 Nov 2009 11:59:33 +0100

 On Tuesday 03 November 2009 10:52:52 Sebastian Huber wrote:
 > >Number:         140242
 > >Category:       usb
 > >Synopsis:       dev/usb/controller/ehci_ix4xx.c shortcomings
 > >Confidential:   no
 > >Severity:       non-critical
 > >Priority:       low
 > >Responsible:    freebsd-usb
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Tue Nov 03 10:00:12 UTC 2009
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Sebastian Huber
 > >Release:        9-current
 > >Organization:
 >
 > embedded brains GmbH
 >
 > >Environment:
 > >Description:
 >
 > In ehci_ixp_attach() setting of sc->sc_bus.usbrev is superfluous since this
 > is also set in ehci_init().
 >
 > Calling ehci_reset() without a valid sc->sc_offs value makes no sense.
 >
 > >How-To-Repeat:
 > >
 > >Fix:
 >
 > Index: ehci_ixp4xx.c
 > ===================================================================
 > --- ehci_ixp4xx.c       (revision 198848)
 > +++ ehci_ixp4xx.c       (working copy)
 > @@ -157,8 +157,6 @@
 >                 return (ENOMEM);
 >         }
 >
 > -       sc->sc_bus.usbrev = USB_REV_2_0;
 > -
 >         /* NB: hints fix the memory location and irq */
 >
 >         rid = 0;
 > @@ -230,7 +228,6 @@
 >
 >                      | EHCI_SCFLG_BIGEMMIO
 >                      | EHCI_SCFLG_NORESTERM
 >
 >                      ;
 > -       (void) ehci_reset(sc);
 >
 >         err = ehci_init(sc);
 >         if (!err) {
 >
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 >
 
 Committed to USB P4:
 
 http://p4web.freebsd.org/chv.cgi?CH=170109
 
 --HPS
 
From sebastian.huber at embedded-brains.de  Tue Nov  3 11:33:32 2009
From: sebastian.huber at embedded-brains.de (Sebastian Huber)
Date: Tue Nov  3 11:33:43 2009
Subject: umass.c question
Message-ID: <4AF01509.7060701@embedded-brains.de>

Hi!

In umass_attach() the sc->sc_mtx will be initialized.  This mutex will be
passed to cam_sim_alloc().  Who destroys this mutex?  I guess it should be
destroyed in umass_detach() right after the last unlock.

CU

-- 
Sebastian Huber, embedded brains GmbH

Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone   : +49 89 18 90 80 79-6
Fax     : +49 89 18 90 80 79-9
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine gesch?ftliche Mitteilung im Sinne des EHUG.
From hselasky at c2i.net  Tue Nov  3 12:32:31 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Nov  3 12:32:38 2009
Subject: umass.c question
In-Reply-To: <4AF01509.7060701@embedded-brains.de>
References: <4AF01509.7060701@embedded-brains.de>
Message-ID: <200911031331.37162.hselasky@c2i.net>

On Tuesday 03 November 2009 12:33:29 Sebastian Huber wrote:
> Sebastian Huber

Thanks for your patch.

Committed to USB P4:

http://p4web.freebsd.org/chv.cgi?CH=170113

--HPS
From rpaulo at freebsd.org  Tue Nov  3 12:42:11 2009
From: rpaulo at freebsd.org (Rui Paulo)
Date: Tue Nov  3 12:42:18 2009
Subject: aue0 detected as ue0 on 8.0-RC2
In-Reply-To: <200911031203.22103.hselasky@freebsd.org>
References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com>
	<1257243047.98619.8.camel@buffy.york.ac.uk>
	<200911031203.22103.hselasky@freebsd.org>
Message-ID: <ADB61C07-6690-4DD3-BF2F-EA5B2C23C718@freebsd.org>

On 3 Nov 2009, at 11:03, Hans Petter Selasky wrote:

> On Tuesday 03 November 2009 11:10:47 Gavin Atkinson wrote:
>> [freebsd-current cc'd, as that was where the thread started, but this
>> probably belongs on -usb, replies should go there]
>>
>> On Sat, 2009-10-31 at 21:59 +0100, Rick van der Zwet wrote:
>>> The first net interface of a aue(4) define used to be called aue0
>>> afaik. But is now called ue0 (declared in usb/net/usb_ethernet.c).  
>>> (no
>>> sign of ue(4) btw).
>>>
>>> I was looking in the UPDATING, man, mailinglists freebsd-usb@ and
>>> freebsd-current@. But I could not find the reason why the naming
>>> convention on this aue differs from the regular stuff, anybody?
>>>
>>> /Rick
>>>
>>> quick# dmesg | tail -8
>>> ugen1.3: <ADMtek> at usbus1
>>> aue0: <ADMtek USB To LAN Converter, rev 2.00/1.01, addr 3> on usbus1
>>> miibus1: <MII bus> on aue0
>>> ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus1
>>> ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>>> ue0: <USB Ethernet> on aue0
>>> ue0: Ethernet address: 00:00:e8:00:11:36
>>> ue0: link state changed to DOWN
>>>
>>> quick# ifconfig -l
>>> bfe0 lo0 ue0
>>
>> Hmm, this looks like a serious bug, possibly in the new USB subsystem
>> (HPS CC'd).
>>
>> I've got an axe(4) device, which also does the same:
>>
>> ugen7.3: <vendor 0x0b95> at usbus7
>> axe0: <vendor 0x0b95 product 0x7720, rev 2.00/0.01, addr 3> on usbus7
>> axe0: PHYADDR 0xe0:0x10
>> miibus1: <MII bus> on axe0
>> ukphy0: <Generic IEEE 802.3u media interface> PHY 16 on miibus1
>> ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>> ue0: <USB Ethernet> on axe0
>> ue0: Ethernet address: 00:50:b6:05:57:a7
>> ue0: link state changed to DOWN
>
> Hi,
>
> All USB ethernet adapters are now named ue0. You will get one axe0  
> event and
> one ue0 event. So there should be no problems regarding devd.conf  .

Fair enough, but this must be mentioned in src/UPDATING.

--
Rui Paulo

From pyunyh at gmail.com  Tue Nov  3 17:55:40 2009
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Tue Nov  3 17:55:46 2009
Subject: aue0 detected as ue0 on 8.0-RC2
In-Reply-To: <1257243047.98619.8.camel@buffy.york.ac.uk>
References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com>
	<1257243047.98619.8.camel@buffy.york.ac.uk>
Message-ID: <20091103175501.GD1256@michelle.cdnetworks.com>

On Tue, Nov 03, 2009 at 10:10:47AM +0000, Gavin Atkinson wrote:
> [freebsd-current cc'd, as that was where the thread started, but this
> probably belongs on -usb, replies should go there]
> 
> On Sat, 2009-10-31 at 21:59 +0100, Rick van der Zwet wrote:
> > The first net interface of a aue(4) define used to be called aue0
> > afaik. But is now called ue0 (declared in usb/net/usb_ethernet.c). (no
> > sign of ue(4) btw).
> > 
> > I was looking in the UPDATING, man, mailinglists freebsd-usb@ and
> > freebsd-current@. But I could not find the reason why the naming
> > convention on this aue differs from the regular stuff, anybody?
> > 
> > /Rick
> > 
> > quick# dmesg | tail -8
> > ugen1.3: <ADMtek> at usbus1
> > aue0: <ADMtek USB To LAN Converter, rev 2.00/1.01, addr 3> on usbus1
> > miibus1: <MII bus> on aue0
> > ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus1
> > ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > ue0: <USB Ethernet> on aue0
> > ue0: Ethernet address: 00:00:e8:00:11:36
> > ue0: link state changed to DOWN
> > 
> > quick# ifconfig -l
> > bfe0 lo0 ue0
> 
> Hmm, this looks like a serious bug, possibly in the new USB subsystem
> (HPS CC'd).
> 
> I've got an axe(4) device, which also does the same:
> 
> ugen7.3: <vendor 0x0b95> at usbus7
> axe0: <vendor 0x0b95 product 0x7720, rev 2.00/0.01, addr 3> on usbus7
> axe0: PHYADDR 0xe0:0x10
> miibus1: <MII bus> on axe0
> ukphy0: <Generic IEEE 802.3u media interface> PHY 16 on miibus1
> ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> ue0: <USB Ethernet> on axe0
> ue0: Ethernet address: 00:50:b6:05:57:a7
> ue0: link state changed to DOWN
> 

I'm not sure this is feature of new USB or bug. I don't have strong
objections on current behavior but looks like I'm seeing Linux
behavior. Traditionally all network interfaces used their own
driver name. I think this change should be documented in UPDATING.

> Gavin
From kungfu_disciple at sbcglobal.net  Tue Nov  3 18:50:03 2009
From: kungfu_disciple at sbcglobal.net (Monty Hall)
Date: Tue Nov  3 18:50:08 2009
Subject: usb/140236: Labels wiped on external Journaled USB HDD on
	8.0-RC2
Message-ID: <200911031850.nA3Io2sS020749@freefall.freebsd.org>

The following reply was made to PR usb/140236; it has been noted by GNATS.

From: Monty Hall <kungfu_disciple@sbcglobal.net>
To: bug-followup@FreeBSD.org, sprague@msu.edu
Cc:  
Subject: Re: usb/140236: Labels wiped on external Journaled USB HDD on 8.0-RC2
Date: Tue, 03 Nov 2009 13:43:54 -0500

 OMG, I didn't mean LABEL, I meant PARTITION.
From kungfu_disciple at sbcglobal.net  Tue Nov  3 19:50:03 2009
From: kungfu_disciple at sbcglobal.net (Monty Hall)
Date: Tue Nov  3 19:50:09 2009
Subject: usb/140236: Labels wiped on external Journaled USB HDD on
	8.0-RC2
Message-ID: <200911031950.nA3Jo3YH071982@freefall.freebsd.org>

The following reply was made to PR usb/140236; it has been noted by GNATS.

From: Monty Hall <kungfu_disciple@sbcglobal.net>
To: bug-followup@FreeBSD.org, sprague@msu.edu
Cc:  
Subject: Re: usb/140236: Labels wiped on external Journaled USB HDD on 8.0-RC2
Date: Tue, 03 Nov 2009 14:41:29 -0500

 FYI: please use my sbcglobal account
From tlb at tlb.org  Tue Nov  3 20:49:34 2009
From: tlb at tlb.org (Trevor Blackwell)
Date: Tue Nov  3 20:49:40 2009
Subject: usb/140236: Labels wiped on external Journaled USB HDD on
	8.0-RC2
In-Reply-To: <200911031850.nA3Io2sS020749@freefall.freebsd.org>
References: <200911031850.nA3Io2sS020749@freefall.freebsd.org>
Message-ID: <8098FB54-3C93-42EA-9FA0-B34ED779E83C@tlb.org>


I recently had a partition table wiped out on a non-boot disk, an 8 GB  
flash drive on a SATA port. I don't know that I can reproduce it, but  
if there are more similar reports it might be worth looking in the  
disk subsystem rather than USB.

--
Trevor Blackwell      tlb@tlb.org     650 776 7870



On Nov 3, 2009, at 10:50 , Monty Hall wrote:

> The following reply was made to PR usb/140236; it has been noted by  
> GNATS.
>
> From: Monty Hall <kungfu_disciple@sbcglobal.net>
> To: bug-followup@FreeBSD.org, sprague@msu.edu
> Cc:
> Subject: Re: usb/140236: Labels wiped on external Journaled USB HDD  
> on 8.0-RC2
> Date: Tue, 03 Nov 2009 13:43:54 -0500
>
> OMG, I didn't mean LABEL, I meant PARTITION.
> _______________________________________________
> 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 thompsa at FreeBSD.org  Tue Nov  3 21:23:40 2009
From: thompsa at FreeBSD.org (Andrew Thompson)
Date: Tue Nov  3 21:23:46 2009
Subject: aue0 detected as ue0 on 8.0-RC2
In-Reply-To: <20091103175501.GD1256@michelle.cdnetworks.com>
References: <5aaae08a0910311359v45cc9dc9h2826d8a29bfb5575@mail.gmail.com>
	<1257243047.98619.8.camel@buffy.york.ac.uk>
	<20091103175501.GD1256@michelle.cdnetworks.com>
Message-ID: <20091103210725.GA33086@citylink.fud.org.nz>

On Tue, Nov 03, 2009 at 09:55:01AM -0800, Pyun YongHyeon wrote:
> On Tue, Nov 03, 2009 at 10:10:47AM +0000, Gavin Atkinson wrote:
> > [freebsd-current cc'd, as that was where the thread started, but this
> > Hmm, this looks like a serious bug, possibly in the new USB subsystem
> > (HPS CC'd).
> > 
> > I've got an axe(4) device, which also does the same:
> > 
> > ugen7.3: <vendor 0x0b95> at usbus7
> > axe0: <vendor 0x0b95 product 0x7720, rev 2.00/0.01, addr 3> on usbus7
> > axe0: PHYADDR 0xe0:0x10
> > miibus1: <MII bus> on axe0
> > ukphy0: <Generic IEEE 802.3u media interface> PHY 16 on miibus1
> > ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > ue0: <USB Ethernet> on axe0
> > ue0: Ethernet address: 00:50:b6:05:57:a7
> > ue0: link state changed to DOWN
> > 
> 
> I'm not sure this is feature of new USB or bug. I don't have strong
> objections on current behavior but looks like I'm seeing Linux
> behavior. Traditionally all network interfaces used their own
> driver name. I think this change should be documented in UPDATING.

I have added an UPDATING entry in 198859.


Andrew
From torfinn.ingolfsen at broadpark.no  Tue Nov  3 21:27:05 2009
From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen)
Date: Tue Nov  3 21:27:11 2009
Subject: usb thermometer - TEMPer - FreeBSD
In-Reply-To: <200911012209.37403.hselasky@c2i.net>
References: <20090414235727.38d16ee1.torfinn.ingolfsen@broadpark.no>
	<20091101213154.cf76de69.torfinn.ingolfsen@broadpark.no>
	<200911012209.37403.hselasky@c2i.net>
Message-ID: <20091103222703.0e8ea0eb.torfinn.ingolfsen@broadpark.no>

On Sun, 01 Nov 2009 22:09:34 +0100
Hans Petter Selasky <hselasky@c2i.net> wrote:

> Try to fetch: 
> 
> /sys/dev/usb/serial/uchcom.c 
> 
> From FreeBSD 9-current and rebuild the uchcom module or kernel.

I noticed that the latest uchcom.c had been MFC'ed to RELENG_8, so I
fetched and built that instead.
root@kg-t2# uname -a
FreeBSD kg-t2.kg4.no 8.0-RC2 FreeBSD 8.0-RC2 #0: Tue Nov  3 20:13:10 CET 2009     root@kg-t2.kg4.no:/usr/obj/usr/src/sys/GENERIC  i386

And in /var/log/messages I see:
Nov  3 22:17:43 kg-t2 kernel: ugen0.2: <vendor 0x4348> at usbus0
Nov  3 22:17:43 kg-t2 kernel: ucom0: <vendor 0x4348 USB-SER!, rev 1.10/2.50, addr 2> on usbus0
Nov  3 22:17:43 kg-t2 kernel: ucom0: CH340 detected
and usbconfig shows:
root@kg-t2# usbconfig list
ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2: <USB-SER! vendor 0x4348> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

But where is ucom0?
root@kg-t2# ls -l /dev/uc*
ls: /dev/uc*: No such file or directory
root@kg-t2# ls -l /dev/ucom0
ls: /dev/ucom0: No such file or directory
root@kg-t2# ls -l /dev/ucom0

-- 
Regards,
Torfinn Ingolfsen

From hselasky at c2i.net  Tue Nov  3 21:55:43 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Nov  3 21:55:50 2009
Subject: usb thermometer - TEMPer - FreeBSD
In-Reply-To: <20091103222703.0e8ea0eb.torfinn.ingolfsen@broadpark.no>
References: <20090414235727.38d16ee1.torfinn.ingolfsen@broadpark.no>
	<200911012209.37403.hselasky@c2i.net>
	<20091103222703.0e8ea0eb.torfinn.ingolfsen@broadpark.no>
Message-ID: <200911032256.58552.hselasky@c2i.net>

On Tuesday 03 November 2009 22:27:03 Torfinn Ingolfsen wrote:
> On Sun, 01 Nov 2009 22:09:34 +0100
>
> Hans Petter Selasky <hselasky@c2i.net> wrote:
> > Try to fetch:
> >
> > /sys/dev/usb/serial/uchcom.c
> >
> > From FreeBSD 9-current and rebuild the uchcom module or kernel.
>
> I noticed that the latest uchcom.c had been MFC'ed to RELENG_8, so I
> fetched and built that instead.
> root@kg-t2# uname -a
> FreeBSD kg-t2.kg4.no 8.0-RC2 FreeBSD 8.0-RC2 #0: Tue Nov  3 20:13:10 CET
> 2009     root@kg-t2.kg4.no:/usr/obj/usr/src/sys/GENERIC  i386
>
> And in /var/log/messages I see:
> Nov  3 22:17:43 kg-t2 kernel: ugen0.2: <vendor 0x4348> at usbus0
> Nov  3 22:17:43 kg-t2 kernel: ucom0: <vendor 0x4348 USB-SER!, rev
> 1.10/2.50, addr 2> on usbus0 Nov  3 22:17:43 kg-t2 kernel: ucom0: CH340
> detected
> and usbconfig shows:
> root@kg-t2# usbconfig list
> ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON ugen0.2: <USB-SER! vendor 0x4348> at usbus0, cfg=0 md=HOST spd=FULL
> (12Mbps) pwr=ON
>
> But where is ucom0?
> root@kg-t2# ls -l /dev/uc*
> ls: /dev/uc*: No such file or directory
> root@kg-t2# ls -l /dev/ucom0
> ls: /dev/ucom0: No such file or directory
> root@kg-t2# ls -l /dev/ucom0

/dev/cuaU0

--HPS

From robertjenssen at hotmail.com  Wed Nov  4 01:20:02 2009
From: robertjenssen at hotmail.com (Robert Jenssen)
Date: Wed Nov  4 01:20:08 2009
Subject: usb/140259: libusb-1.0 portability/compatibility nits
Message-ID: <200911040111.nA41Bw30098496@www.freebsd.org>


>Number:         140259
>Category:       usb
>Synopsis:       libusb-1.0 portability/compatibility nits
>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:   Wed Nov 04 01:20:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Robert Jenssen
>Release:        8.0RC2
>Organization:
>Environment:
FreeBSD kraken 8.0-RC2 FreeBSD 8.0-RC2 #0: Sat Oct 31 05:40:55 EST 2009     robj@kraken:/usr/obj/usr/src/sys/KRAKEN  i386
>Description:
Thankyou for porting libusb-1.0 to the FreeBSD kernel. Being new to usb programming, I tried to compile the non-trivial example program, dpfp.c,  provided with the libusb-1.0.3.tar.bz2 tarball available from "http://sourceforge.net/projects/libusb/files/libusb-1.0/libusb-1.0.3/libusb-1.0.3.tar.bz2/download" . I found two problems

1. FreeBSD libusb10 is not quite portable. Here is a diff required to get dpfp.c to compile:
[robj examples]diff dpfp.c dpfp.c.orig 
30,32c30
< #include <libusb.h>
< 
< #define LIBUSB_CONTROL_SETUP_SIZE (sizeof(struct libusb_control_setup))
---
> #include <libusb/libusb.h>
62c60
< static libusb_device_handle *devh = NULL;
---
> static struct libusb_device_handle *devh = NULL;


2. Some libusb-1.0 functions are not implemented. Here is an attempt to link dpfp.c:
[robj examples]gcc -O0 -g -o dpfp -lusb dpfp.c 
/var/tmp//ccPc8n2t.o(.text+0x4dc): In function `set_mode_async':
/home/robj/TMP/libusb-1.0.3/examples/dpfp.c:182: undefined reference to `libusb_fill_control_setup'
/var/tmp//ccPc8n2t.o(.text+0x51c):/home/robj/TMP/libusb-1.0.3/examples/dpfp.c:184: undefined reference to `libusb_fill_control_transfer'
/var/tmp//ccPc8n2t.o(.text+0xbe5): In function `alloc_transfers':
/home/robj/TMP/libusb-1.0.3/examples/dpfp.c:406: undefined reference to `libusb_fill_bulk_transfer'
/var/tmp//ccPc8n2t.o(.text+0xc2c):/home/robj/TMP/libusb-1.0.3/examples/dpfp.c:408: undefined reference to `libusb_fill_interrupt_transfer'


>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From torfinn.ingolfsen at broadpark.no  Wed Nov  4 18:42:43 2009
From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen)
Date: Wed Nov  4 18:42:49 2009
Subject: usb thermometer - TEMPer - FreeBSD
In-Reply-To: <200911032256.58552.hselasky@c2i.net>
References: <20090414235727.38d16ee1.torfinn.ingolfsen@broadpark.no>
	<200911012209.37403.hselasky@c2i.net>
	<20091103222703.0e8ea0eb.torfinn.ingolfsen@broadpark.no>
	<200911032256.58552.hselasky@c2i.net>
Message-ID: <20091104194221.c325fb37.torfinn.ingolfsen@broadpark.no>

On Tue, 03 Nov 2009 22:56:57 +0100
Hans Petter Selasky <hselasky@c2i.net> wrote:

> > But where is ucom0?
> > root@kg-t2# ls -l /dev/uc*
> > ls: /dev/uc*: No such file or directory
> > root@kg-t2# ls -l /dev/ucom0
> > ls: /dev/ucom0: No such file or directory
> > root@kg-t2# ls -l /dev/ucom0
> 
> /dev/cuaU0

Ah! I did know that, but had forgotten and that "ucom0:" in the output
confused me. Thanks!

Here is an idea: could we have the class of devices (usb devices that
create / use ttys) report which tty they are using when they attach?
Ie, instead of
ucom0: CH340 detected

We could have:
ucom0: CH340  detected, using /dev/cuaU0
or something like that?
I don't care if it is the driver, ther kenel or another part of FreeBSd
that outpus this information, I just want it t be presented to the user.

Just my 0.02 eurocents.
-- 
Regards,
Torfinn Ingolfsen

From a.markov at complitex.ru  Thu Nov  5 09:01:13 2009
From: a.markov at complitex.ru (Alexey Markov)
Date: Thu Nov  5 12:40:02 2009
Subject: AnyDATA ADU-500A USB-modem and a lot of "ubsa_cfg_request" errors
Message-ID: <E419495488F746A7ABD4D8D558B4942F@complitex.local>

Hello!

First of all, excuse my English.

Well, i have an AnyDATA ADU-500A Rev.A USB-modem, and i'm going to use
it for my handmade "VIA EPIA-based mobile router". I have installed
latest 8.0-RC2 and configured ppp, and now everything works just fine,
except that I got a lot of such messages on console when I run ppp:

ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED (ignored)

I really want to work it out, and I have some spare time for experiments,
but haven't any experience of debuging kernel drivers. Can anybody give me
a clue to solve this little problem?

-- 
WBR, Alexey Markov. 

From hselasky at c2i.net  Thu Nov  5 13:00:48 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Nov  5 13:00:54 2009
Subject: AnyDATA ADU-500A USB-modem and a lot of "ubsa_cfg_request"
	errors
In-Reply-To: <E419495488F746A7ABD4D8D558B4942F@complitex.local>
References: <E419495488F746A7ABD4D8D558B4942F@complitex.local>
Message-ID: <200911051359.49517.hselasky@c2i.net>

On Thursday 05 November 2009 09:01:05 Alexey Markov wrote:
> Hello!
>
> First of all, excuse my English.
>
> Well, i have an AnyDATA ADU-500A Rev.A USB-modem, and i'm going to use
> it for my handmade "VIA EPIA-based mobile router". I have installed
> latest 8.0-RC2 and configured ppp, and now everything works just fine,
> except that I got a lot of such messages on console when I run ppp:
>
> ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED
> (ignored)
>
> I really want to work it out, and I have some spare time for experiments,
> but haven't any experience of debuging kernel drivers. Can anybody give me
> a clue to solve this little problem?

Did you look in the source code:

/sys/dev/usb/serial/ubsa.c

--HPS
From lioux at FreeBSD.org  Thu Nov  5 13:13:05 2009
From: lioux at FreeBSD.org (Mario Sergio Fujikawa Ferreira)
Date: Thu Nov  5 13:13:39 2009
Subject: usb/106861: [usb67] [usb8] [usbdevs] [patch] Add ACER Zeevo
 BT-500 Bluetooth USB Adapter
In-Reply-To: <200908251137.n7PBbVA7086443@freefall.freebsd.org>
	(sfid-20090825_09001_6359084E) (sfid-20090825_09001_6359084E)
References: <200908251137.n7PBbVA7086443@freefall.freebsd.org>
	(sfid-20090825_09001_6359084E) (sfid-20090825_09001_6359084E)
Message-ID: <20091105111228.42154lq771l53zeo@exxodus.dyndns.org>

Quoting gavin@FreeBSD.org:

> Old Synopsis: [usbdevs] [patch]: usbdevs update: Add product ACER  
> Zeevo BT-500 Bluetooth USB Adapter
> New Synopsis: [usb67] [usb8] [usbdevs] [patch] Add ACER Zeevo BT-500
> Bluetooth USB Adapter
>
> Do you know if this USB bluetooth adapter works with more recent
> versions of FreeBSD?

   Unfortunately, I do not have access to this adapter anymore. Unless  
there are other people with a similar need, this PR could be marked  
for expiration (say 2 months without a follow up).

   Regards,

-- 
Mario S F Ferreira - DF - Brazil - "I guess this is a signature."
feature, n: a documented bug | bug, n: an undocumented feature
From robertjenssen at hotmail.com  Fri Nov  6 00:30:08 2009
From: robertjenssen at hotmail.com (Robert Jenssen)
Date: Fri Nov  6 00:30:17 2009
Subject: usb/140325: Missing/incorrect initialisation and memory leak in
	libusb10/libusb20
Message-ID: <200911060026.nA60QEoB073159@www.freebsd.org>


>Number:         140325
>Category:       usb
>Synopsis:       Missing/incorrect initialisation and memory leak in libusb10/libusb20
>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 Nov 06 00:30:07 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Robert Jenssen
>Release:        8.0RC2
>Organization:
>Environment:
FreeBSD kraken 8.0-RC2 FreeBSD 8.0-RC2 #0: Fri Nov  6 02:43:24 EST 2009     root@kraken:/usr/obj/usr/src/sys/KRAKEN  i386
>Description:
I was getting some weird values for usb configuration descriptor extra length. Valgrind is a wonderful tool recently ported to FreeBSD by stas@FreeBSD.org. Using valgrind I found the following problems (fixed in the attached patch):

1. In libusb10_desc.c, libusb_get_config_descriptor(), at line 162:
	pconfd->interface = (libusb_interface *) (pconfd +
	    sizeof(libusb_config_descriptor));
should be:
	pconfd->interface = (libusb_interface *) (pconfd + 1);
This problem causes illegal writes past the end of pconfd.

2. In libusb20_ugen20.c , ugen20_get_config_desc_full(), cdesc and ptr are not initialised. This problem causes branches on uninitialised values.

3. In libusb20.c, libusb20_be_free(), pbe is not free'd. This problem causes a minor memory leak.


>How-To-Repeat:
Compile the following test, link with a debug version of libusb.a and run valgrind.

#include <libusb.h>
int main(void) {
  libusb_context *context;
  struct libusb_device **devs;
  struct libusb_config_descriptor *config;

  libusb_init(&context);
  libusb_get_device_list(context, &devs);
  libusb_get_active_config_descriptor(devs[0], &config);
  libusb_free_config_descriptor(config);
  libusb_free_device_list(devs, 1);
  libusb_exit(context);
  return 0;
}

>Fix:
Apply the attached patch in /usr/src/lib/libusb


Patch attached with submission follows:

*** libusb10_desc.c	2009-11-06 10:35:00.000000000 +1100
--- libusb10_desc.c.orig	2009-08-03 18:13:06.000000000 +1000
***************
*** 116,133 ****
  	nep = 0;
  	nextra = pconf->extra.len;
  
- #define NEXTRA_ALIGN_TO(n) (nextra=((nextra+n)/n)*n)
  	for (i = 0; i < nif; i++) {
  
  		pinf = pconf->interface + i;
  		nextra += pinf->extra.len;
-     NEXTRA_ALIGN_TO(16);
  		nep += pinf->num_endpoints;
  		k = pinf->num_endpoints;
  		pend = pinf->endpoints;
  		while (k--) {
  			nextra += pend->extra.len;
-       NEXTRA_ALIGN_TO(16);
  			pend++;
  		}
  
--- 116,130 ----
***************
*** 136,148 ****
  		pinf = pinf->altsetting;
  		while (j--) {
  			nextra += pinf->extra.len;
-       NEXTRA_ALIGN_TO(16);
  			nep += pinf->num_endpoints;
  			k = pinf->num_endpoints;
  			pend = pinf->endpoints;
  			while (k--) {
  				nextra += pend->extra.len;
-         NEXTRA_ALIGN_TO(16);
  				pend++;
  			}
  			pinf++;
--- 133,143 ----
***************
*** 155,163 ****
  	    (nalt * sizeof(libusb_interface_descriptor)) +
  	    (nep * sizeof(libusb_endpoint_descriptor));
  
-   /* Align nextra */
-   NEXTRA_ALIGN_TO(16);
- 
  	pconfd = malloc(nextra);
  
  	if (pconfd == NULL) {
--- 150,155 ----
***************
*** 167,173 ****
  	/* make sure memory is clean */
  	memset(pconfd, 0, nextra);
  
! 	pconfd->interface = (libusb_interface *) (pconfd + 1);
  
  	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
  	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
--- 159,166 ----
  	/* make sure memory is clean */
  	memset(pconfd, 0, nextra);
  
! 	pconfd->interface = (libusb_interface *) (pconfd +
! 	    sizeof(libusb_config_descriptor));
  
  	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
  	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
***************
*** 194,200 ****
  
  	for (i = 0; i < nif; i++) {
  
- 		pconfd->interface[i].altsetting = 0;
  		pconfd->interface[i].altsetting = ifd;
  		ifd->endpoint = endd;
  		endd += pconf->interface[i].num_endpoints;
--- 187,192 ----
*** libusb20.c	2009-11-06 10:35:00.000000000 +1100
--- libusb20.c.orig	2009-08-03 18:13:06.000000000 +1000
***************
*** 1093,1100 ****
  	if (pbe->methods->exit_backend) {
  		pbe->methods->exit_backend(pbe);
  	}
-   /* free backend */
-   free(pbe);
  	return;
  }
  
--- 1093,1098 ----
*** libusb20_desc.c	2009-11-06 10:35:00.000000000 +1100
--- libusb20_desc.c.orig	2009-08-03 18:13:06.000000000 +1000
***************
*** 118,124 ****
  	if (lub_config == NULL) {
  		return (NULL);		/* out of memory */
  	}
-   memset(lub_config, 0, size);
  	lub_interface = (void *)(lub_config + 1);
  	lub_alt_interface = (void *)(lub_interface + niface_no_alt);
  	lub_endpoint = (void *)(lub_interface + niface);
--- 118,123 ----
*** libusb20_ugen20.c	2009-11-06 10:35:00.000000000 +1100
--- libusb20_ugen20.c.orig	2009-10-23 23:02:01.000000000 +1100
***************
*** 449,455 ****
  	uint16_t len;
  	int error;
  
- 	memset(&cdesc, 0, sizeof(cdesc));
  	memset(&gen_desc, 0, sizeof(gen_desc));
  
  	gen_desc.ugd_data = &cdesc;
--- 449,454 ----
***************
*** 469,475 ****
  	if (!ptr) {
  		return (LIBUSB20_ERROR_NO_MEM);
  	}
-   memset(ptr, 0, len);
  	gen_desc.ugd_data = ptr;
  	gen_desc.ugd_maxlen = len;
  
--- 468,473 ----


>Release-Note:
>Audit-Trail:
>Unformatted:
From robertjenssen at ozemail.com.au  Fri Nov  6 04:00:14 2009
From: robertjenssen at ozemail.com.au (Robert Jenssen)
Date: Fri Nov  6 04:00:21 2009
Subject: usb/140325: Missing/incorrect initialisation and memory leak in
 libusb10/libusb20
Message-ID: <200911060400.nA640E7C058546@freefall.freebsd.org>

The following reply was made to PR usb/140325; it has been noted by GNATS.

From: Robert Jenssen <robertjenssen@ozemail.com.au>
To: bug-followup@FreeBSD.org, robertjenssen@hotmail.com
Cc:  
Subject: Re: usb/140325: Missing/incorrect initialisation and memory leak in
 libusb10/libusb20
Date: Fri, 6 Nov 2009 14:42:13 +1100

 Hi,
 
 Regarding my bug report usb/140325: Missing/incorrect initialisation and memory leak in libusb10/libusb20. I revised my simple test to:
 
 #include <stdio.h>
 #include <libusb.h>
 
 int
 main(void)
 {
   libusb_context *context;
   struct libusb_device **devs;
   libusb_device_handle *handle;
   struct libusb_config_descriptor *config;
   struct libusb_device_descriptor device_desc;
   int bytes;
 #define STRLEN 128
   unsigned char str[STRLEN];
   int transferred;
   
   libusb_init(&context);
   libusb_get_device_list(context, &devs);
   libusb_get_active_config_descriptor(devs[0], &config);
   libusb_free_config_descriptor(config);
   libusb_get_device_descriptor(devs[0], &device_desc);
   libusb_open(devs[0], &handle);
   libusb_get_string_descriptor_ascii(handle,device_desc.iProduct,str,STRLEN);
   libusb_claim_interface(handle, 1);
   libusb_bulk_transfer(handle, 1, str, STRLEN, &transferred, 0);
   libusb_release_interface(handle, 1);
   libusb_close(handle);
   libusb_free_device_list(devs, 1);
   libusb_exit(context);
 
   return 0;
 }
 
 and found two additional problems:
 
 4. A jump on uninitialised occurs at libusb20.c:658 in libusb20_dev_req_string_sync():
   req.wLength = *(uint8_t *)ptr;	/* bytes */
   if (req.wLength > len) {
 To fix, zero the upper byte with:
   memset(ptr, 0, len);
 
 5. A memory leak occurs for devs[0] in the above test. devs[0]->refcnt is incremented to 3 during libusb_bulk_transfer() but not decremented on exit from that function. Consequently, devs[0] is not freed in libusb_free_device_list(). I couldn't see a quick fix for this and it's a minor memory leak (44 bytes) so I will leave it for an expert.
 
 Regards,
 
 Rob
 -- 
 Robert Jenssen <robertjenssen@ozemail.com.au>
From robertjenssen at hotmail.com  Fri Nov  6 04:10:05 2009
From: robertjenssen at hotmail.com (Robert Jenssen)
Date: Fri Nov  6 04:10:10 2009
Subject: usb/140325: Missing/incorrect initialisation and memory leak in
 libusb10/libusb20
Message-ID: <200911060410.nA64A4LQ066868@freefall.freebsd.org>

The following reply was made to PR usb/140325; it has been noted by GNATS.

From: Robert Jenssen <robertjenssen@hotmail.com>
To: <bug-followup@freebsd.org>
Cc:  
Subject: Re: usb/140325: Missing/incorrect initialisation and memory leak in
 libusb10/libusb20
Date: Fri, 6 Nov 2009 14:57:00 +1100

 --_813ea73d-cf99-4614-b03d-4bb9d22d7898_
 Content-Type: text/plain; charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 
 Hi=2C
 
 Sorry for the noise. In my last email I missed out a memory leak:
 
 6. In libusb10.c=2C libusb_close()=2C pdev isn't freed. Here is a diff:
 *** libusb10.c    2009-11-06 13:30:51.000000000 +1100
 --- libusb10.c.orig    2009-08-03 18:13:06.000000000 +1000
 ***************
 *** 416=2C422 ****
       libusb10_remove_pollfd(ctx=2C &dev->dev_poll)=3B
  =20
       libusb20_dev_close(pdev)=3B
 -   free(pdev)=3B
       libusb_unref_device(dev)=3B
  =20
       /* make sure our event loop detects the closed device */
 --- 416=2C421 ----
 
 --=20
 Robert Jenssen <robertjenssen@hotmail.com>
 
  		 	   		 =20
 _________________________________________________________________
 Looking to move this spring? With all the lastest places=2C searching has n=
 ever been easier. Look now!
 http://clk.atdmt.com/NMN/go/157631292/direct/01/=
 
 --_813ea73d-cf99-4614-b03d-4bb9d22d7898_
 Content-Type: text/html; charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 <html>
 <head>
 <style><!--
 .hmmessage P
 {
 margin:0px=3B
 padding:0px
 }
 body.hmmessage
 {
 font-size: 10pt=3B
 font-family:Verdana
 }
 --></style>
 </head>
 <body class=3D'hmmessage'>
 Hi=2C<br><br>Sorry for the noise. In my last email I missed out a memory le=
 ak:<br><br>6. In libusb10.c=2C libusb_close()=2C pdev isn't freed. Here is =
 a diff:<br>*** libusb10.c&nbsp=3B&nbsp=3B &nbsp=3B2009-11-06 13:30:51.00000=
 0000 +1100<br>--- libusb10.c.orig&nbsp=3B&nbsp=3B &nbsp=3B2009-08-03 18:13:=
 06.000000000 +1000<br>***************<br>*** 416=2C422 ****<br>&nbsp=3B &nb=
 sp=3B&nbsp=3B &nbsp=3Blibusb10_remove_pollfd(ctx=2C &amp=3Bdev-&gt=3Bdev_po=
 ll)=3B<br>&nbsp=3B <br>&nbsp=3B &nbsp=3B&nbsp=3B &nbsp=3Blibusb20_dev_close=
 (pdev)=3B<br>-&nbsp=3B&nbsp=3B free(pdev)=3B<br>&nbsp=3B &nbsp=3B&nbsp=3B &=
 nbsp=3Blibusb_unref_device(dev)=3B<br>&nbsp=3B <br>&nbsp=3B &nbsp=3B&nbsp=
 =3B &nbsp=3B/* make sure our event loop detects the closed device */<br>---=
  416=2C421 ----<br><br>-- <br>Robert Jenssen &lt=3Brobertjenssen@hotmail.co=
 m&gt=3B<br><br> 		 	   		  <br /><hr />With all the lastest places=2C searc=
 hing has never been easier. Look now! <a href=3D'http://clk.atdmt.com/NMN/g=
 o/157631292/direct/01/' target=3D'_new'>Looking to move this spring?</a></b=
 ody>
 </html>=
 
 --_813ea73d-cf99-4614-b03d-4bb9d22d7898_--
From hselasky at c2i.net  Fri Nov  6 08:30:38 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Fri Nov  6 08:30:45 2009
Subject: AnyDATA ADU-500A USB-modem and a lot of "ubsa_cfg_request"
	errors
In-Reply-To: <8E4D6619143F4948997186D3DF828D66@complitex.local>
References: <E419495488F746A7ABD4D8D558B4942F@complitex.local>
	<200911051359.49517.hselasky@c2i.net>
	<8E4D6619143F4948997186D3DF828D66@complitex.local>
Message-ID: <200911060929.40525.hselasky@c2i.net>

On Friday 06 November 2009 08:31:05 Alexey Markov wrote:
> Hello, Hans!
> On November, 05 2009 at 15:59 you wrote to freebsd-usb@freebsd.org:
>
>  ??>> except that I got a lot of such messages on console when I run ppp:
>  ??>>
>  ??>> ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED
>  ??>>
>  ??>> I really want to work it out, and I have some spare time for
>  ??>> experiments, but haven't any experience of debuging kernel drivers.
>  ??>> Can anybody give me a clue to solve this little problem?
>
>  HPS> Did you look in the source code:
>  HPS> /sys/dev/usb/serial/ubsa.c
>
> Yes, of course! Line #317 belongs to ubsa_cfg_request(), which just calls
> another function, ucom_cfg_do_request(), with some parameters. But this
> function is called several times in the code, so I've changed code of
> ubsa_cfg_request() function to see, which config requests are failed:
>
> DPRINTFN(0, "device request failed, err=%s, index=%d, value=%d "...
>
> I have got a lot of messages like this one:
>
> ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED,
> index=10, value=1 (ignored)
>
> where index/value pairs sequence is:
>
> 10/1, 11/1, 12/0, 0/24, 3/0, 2/3, 1/0, 16/384, 0/2, 3/0 and so forth.
>
> It seems, that driver tried to set some config parameters like DTR, RTS,
> BAUDRATE etc, and failed. But after all, modem is working (maybe, with
> non-optimal settings or default settings).
>
> So, I need an advice: what can I do to find the cause of failed config
> requests?

Hi,

Maybe you device belongs in the ugensa.c driver and not ubsa.c if it does not 
support all those DTR/RTS ... settings? Do you have a datasheet for the modem 
in question?

--HPS
From hselasky at c2i.net  Fri Nov  6 08:52:32 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Fri Nov  6 08:52:40 2009
Subject: usb/140325: Missing/incorrect initialisation and memory leak in
	libusb10/libusb20
In-Reply-To: <200911060026.nA60QEoB073159@www.freebsd.org>
References: <200911060026.nA60QEoB073159@www.freebsd.org>
Message-ID: <200911060951.34794.hselasky@c2i.net>

On Friday 06 November 2009 01:26:14 Robert Jenssen wrote:
> >Number:         140325
> >Category:       usb
> >Synopsis:       Missing/incorrect initialisation and memory leak in
> > libusb10/libusb20 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 Nov 06 00:30:07 UTC 2009
> >Closed-Date:
> >Last-Modified:
> >Originator:     Robert Jenssen
> >Release:        8.0RC2
> >Organization:
> >Environment:
>
> FreeBSD kraken 8.0-RC2 FreeBSD 8.0-RC2 #0: Fri Nov  6 02:43:24 EST 2009    
> root@kraken:/usr/obj/usr/src/sys/KRAKEN  i386
>
> >Description:
>
> I was getting some weird values for usb configuration descriptor extra
> length. Valgrind is a wonderful tool recently ported to FreeBSD by
> stas@FreeBSD.org. Using valgrind I found the following problems (fixed in
> the attached patch):
>
> 1. In libusb10_desc.c, libusb_get_config_descriptor(), at line 162:
> 	pconfd->interface = (libusb_interface *) (pconfd +
> 	    sizeof(libusb_config_descriptor));
> should be:
> 	pconfd->interface = (libusb_interface *) (pconfd + 1);
> This problem causes illegal writes past the end of pconfd.
>
> 2. In libusb20_ugen20.c , ugen20_get_config_desc_full(), cdesc and ptr are
> not initialised. This problem causes branches on uninitialised values.
>
> 3. In libusb20.c, libusb20_be_free(), pbe is not free'd. This problem
> causes a minor memory leak.
>
> >How-To-Repeat:
>
> Compile the following test, link with a debug version of libusb.a and run
> valgrind.
>
> #include <libusb.h>
> int main(void) {
>   libusb_context *context;
>   struct libusb_device **devs;
>   struct libusb_config_descriptor *config;
>
>   libusb_init(&context);
>   libusb_get_device_list(context, &devs);
>   libusb_get_active_config_descriptor(devs[0], &config);
>   libusb_free_config_descriptor(config);
>   libusb_free_device_list(devs, 1);
>   libusb_exit(context);
>   return 0;
> }
>
> >Fix:
>
> Apply the attached patch in /usr/src/lib/libusb
>
>
> Patch attached with submission follows:
>
> *** libusb10_desc.c	2009-11-06 10:35:00.000000000 +1100
> --- libusb10_desc.c.orig	2009-08-03 18:13:06.000000000 +1000
> ***************
> *** 116,133 ****
>   	nep = 0;
>   	nextra = pconf->extra.len;
>
> - #define NEXTRA_ALIGN_TO(n) (nextra=((nextra+n)/n)*n)
>   	for (i = 0; i < nif; i++) {
>
>   		pinf = pconf->interface + i;
>   		nextra += pinf->extra.len;
> -     NEXTRA_ALIGN_TO(16);
>   		nep += pinf->num_endpoints;
>   		k = pinf->num_endpoints;
>   		pend = pinf->endpoints;
>   		while (k--) {
>   			nextra += pend->extra.len;
> -       NEXTRA_ALIGN_TO(16);
>   			pend++;
>   		}
>
> --- 116,130 ----
> ***************
> *** 136,148 ****
>   		pinf = pinf->altsetting;
>   		while (j--) {
>   			nextra += pinf->extra.len;
> -       NEXTRA_ALIGN_TO(16);
>   			nep += pinf->num_endpoints;
>   			k = pinf->num_endpoints;
>   			pend = pinf->endpoints;
>   			while (k--) {
>   				nextra += pend->extra.len;
> -         NEXTRA_ALIGN_TO(16);
>   				pend++;
>   			}
>   			pinf++;
> --- 133,143 ----
> ***************
> *** 155,163 ****
>   	    (nalt * sizeof(libusb_interface_descriptor)) +
>   	    (nep * sizeof(libusb_endpoint_descriptor));
>
> -   /* Align nextra */
> -   NEXTRA_ALIGN_TO(16);
> -
>   	pconfd = malloc(nextra);
>
>   	if (pconfd == NULL) {
> --- 150,155 ----
> ***************
> *** 167,173 ****
>   	/* make sure memory is clean */
>   	memset(pconfd, 0, nextra);
>
> ! 	pconfd->interface = (libusb_interface *) (pconfd + 1);
>
>   	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
>   	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
> --- 159,166 ----
>   	/* make sure memory is clean */
>   	memset(pconfd, 0, nextra);
>
> ! 	pconfd->interface = (libusb_interface *) (pconfd +
> ! 	    sizeof(libusb_config_descriptor));
>
>   	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
>   	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
> ***************
> *** 194,200 ****
>
>   	for (i = 0; i < nif; i++) {
>
> - 		pconfd->interface[i].altsetting = 0;
>   		pconfd->interface[i].altsetting = ifd;
>   		ifd->endpoint = endd;
>   		endd += pconf->interface[i].num_endpoints;
> --- 187,192 ----
> *** libusb20.c	2009-11-06 10:35:00.000000000 +1100
> --- libusb20.c.orig	2009-08-03 18:13:06.000000000 +1000
> ***************
> *** 1093,1100 ****
>   	if (pbe->methods->exit_backend) {
>   		pbe->methods->exit_backend(pbe);
>   	}
> -   /* free backend */
> -   free(pbe);
>   	return;
>   }
>
> --- 1093,1098 ----
> *** libusb20_desc.c	2009-11-06 10:35:00.000000000 +1100
> --- libusb20_desc.c.orig	2009-08-03 18:13:06.000000000 +1000
> ***************
> *** 118,124 ****
>   	if (lub_config == NULL) {
>   		return (NULL);		/* out of memory */
>   	}
> -   memset(lub_config, 0, size);
>   	lub_interface = (void *)(lub_config + 1);
>   	lub_alt_interface = (void *)(lub_interface + niface_no_alt);
>   	lub_endpoint = (void *)(lub_interface + niface);
> --- 118,123 ----
> *** libusb20_ugen20.c	2009-11-06 10:35:00.000000000 +1100
> --- libusb20_ugen20.c.orig	2009-10-23 23:02:01.000000000 +1100
> ***************
> *** 449,455 ****
>   	uint16_t len;
>   	int error;
>
> - 	memset(&cdesc, 0, sizeof(cdesc));
>   	memset(&gen_desc, 0, sizeof(gen_desc));
>
>   	gen_desc.ugd_data = &cdesc;
> --- 449,454 ----
> ***************
> *** 469,475 ****
>   	if (!ptr) {
>   		return (LIBUSB20_ERROR_NO_MEM);
>   	}
> -   memset(ptr, 0, len);
>   	gen_desc.ugd_data = ptr;
>   	gen_desc.ugd_maxlen = len;
>
> --- 468,473 ----
>
> >Release-Note:
> >Audit-Trail:
> >Unformatted:
>

I'm working on these issues.

--HPS

From hselasky at c2i.net  Fri Nov  6 09:00:10 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Fri Nov  6 09:00:15 2009
Subject: usb/140325: Missing/incorrect initialisation and memory leak in
	libusb10/libusb20
Message-ID: <200911060900.nA6908Z0052242@freefall.freebsd.org>

The following reply was made to PR usb/140325; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Robert Jenssen <robertjenssen@hotmail.com>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/140325: Missing/incorrect initialisation and memory leak in libusb10/libusb20
Date: Fri, 6 Nov 2009 09:51:34 +0100

 On Friday 06 November 2009 01:26:14 Robert Jenssen wrote:
 > >Number:         140325
 > >Category:       usb
 > >Synopsis:       Missing/incorrect initialisation and memory leak in
 > > libusb10/libusb20 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 Nov 06 00:30:07 UTC 2009
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Robert Jenssen
 > >Release:        8.0RC2
 > >Organization:
 > >Environment:
 >
 > FreeBSD kraken 8.0-RC2 FreeBSD 8.0-RC2 #0: Fri Nov  6 02:43:24 EST 2009    
 > root@kraken:/usr/obj/usr/src/sys/KRAKEN  i386
 >
 > >Description:
 >
 > I was getting some weird values for usb configuration descriptor extra
 > length. Valgrind is a wonderful tool recently ported to FreeBSD by
 > stas@FreeBSD.org. Using valgrind I found the following problems (fixed in
 > the attached patch):
 >
 > 1. In libusb10_desc.c, libusb_get_config_descriptor(), at line 162:
 > 	pconfd->interface = (libusb_interface *) (pconfd +
 > 	    sizeof(libusb_config_descriptor));
 > should be:
 > 	pconfd->interface = (libusb_interface *) (pconfd + 1);
 > This problem causes illegal writes past the end of pconfd.
 >
 > 2. In libusb20_ugen20.c , ugen20_get_config_desc_full(), cdesc and ptr are
 > not initialised. This problem causes branches on uninitialised values.
 >
 > 3. In libusb20.c, libusb20_be_free(), pbe is not free'd. This problem
 > causes a minor memory leak.
 >
 > >How-To-Repeat:
 >
 > Compile the following test, link with a debug version of libusb.a and run
 > valgrind.
 >
 > #include <libusb.h>
 > int main(void) {
 >   libusb_context *context;
 >   struct libusb_device **devs;
 >   struct libusb_config_descriptor *config;
 >
 >   libusb_init(&context);
 >   libusb_get_device_list(context, &devs);
 >   libusb_get_active_config_descriptor(devs[0], &config);
 >   libusb_free_config_descriptor(config);
 >   libusb_free_device_list(devs, 1);
 >   libusb_exit(context);
 >   return 0;
 > }
 >
 > >Fix:
 >
 > Apply the attached patch in /usr/src/lib/libusb
 >
 >
 > Patch attached with submission follows:
 >
 > *** libusb10_desc.c	2009-11-06 10:35:00.000000000 +1100
 > --- libusb10_desc.c.orig	2009-08-03 18:13:06.000000000 +1000
 > ***************
 > *** 116,133 ****
 >   	nep = 0;
 >   	nextra = pconf->extra.len;
 >
 > - #define NEXTRA_ALIGN_TO(n) (nextra=((nextra+n)/n)*n)
 >   	for (i = 0; i < nif; i++) {
 >
 >   		pinf = pconf->interface + i;
 >   		nextra += pinf->extra.len;
 > -     NEXTRA_ALIGN_TO(16);
 >   		nep += pinf->num_endpoints;
 >   		k = pinf->num_endpoints;
 >   		pend = pinf->endpoints;
 >   		while (k--) {
 >   			nextra += pend->extra.len;
 > -       NEXTRA_ALIGN_TO(16);
 >   			pend++;
 >   		}
 >
 > --- 116,130 ----
 > ***************
 > *** 136,148 ****
 >   		pinf = pinf->altsetting;
 >   		while (j--) {
 >   			nextra += pinf->extra.len;
 > -       NEXTRA_ALIGN_TO(16);
 >   			nep += pinf->num_endpoints;
 >   			k = pinf->num_endpoints;
 >   			pend = pinf->endpoints;
 >   			while (k--) {
 >   				nextra += pend->extra.len;
 > -         NEXTRA_ALIGN_TO(16);
 >   				pend++;
 >   			}
 >   			pinf++;
 > --- 133,143 ----
 > ***************
 > *** 155,163 ****
 >   	    (nalt * sizeof(libusb_interface_descriptor)) +
 >   	    (nep * sizeof(libusb_endpoint_descriptor));
 >
 > -   /* Align nextra */
 > -   NEXTRA_ALIGN_TO(16);
 > -
 >   	pconfd = malloc(nextra);
 >
 >   	if (pconfd == NULL) {
 > --- 150,155 ----
 > ***************
 > *** 167,173 ****
 >   	/* make sure memory is clean */
 >   	memset(pconfd, 0, nextra);
 >
 > ! 	pconfd->interface = (libusb_interface *) (pconfd + 1);
 >
 >   	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
 >   	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
 > --- 159,166 ----
 >   	/* make sure memory is clean */
 >   	memset(pconfd, 0, nextra);
 >
 > ! 	pconfd->interface = (libusb_interface *) (pconfd +
 > ! 	    sizeof(libusb_config_descriptor));
 >
 >   	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
 >   	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
 > ***************
 > *** 194,200 ****
 >
 >   	for (i = 0; i < nif; i++) {
 >
 > - 		pconfd->interface[i].altsetting = 0;
 >   		pconfd->interface[i].altsetting = ifd;
 >   		ifd->endpoint = endd;
 >   		endd += pconf->interface[i].num_endpoints;
 > --- 187,192 ----
 > *** libusb20.c	2009-11-06 10:35:00.000000000 +1100
 > --- libusb20.c.orig	2009-08-03 18:13:06.000000000 +1000
 > ***************
 > *** 1093,1100 ****
 >   	if (pbe->methods->exit_backend) {
 >   		pbe->methods->exit_backend(pbe);
 >   	}
 > -   /* free backend */
 > -   free(pbe);
 >   	return;
 >   }
 >
 > --- 1093,1098 ----
 > *** libusb20_desc.c	2009-11-06 10:35:00.000000000 +1100
 > --- libusb20_desc.c.orig	2009-08-03 18:13:06.000000000 +1000
 > ***************
 > *** 118,124 ****
 >   	if (lub_config == NULL) {
 >   		return (NULL);		/* out of memory */
 >   	}
 > -   memset(lub_config, 0, size);
 >   	lub_interface = (void *)(lub_config + 1);
 >   	lub_alt_interface = (void *)(lub_interface + niface_no_alt);
 >   	lub_endpoint = (void *)(lub_interface + niface);
 > --- 118,123 ----
 > *** libusb20_ugen20.c	2009-11-06 10:35:00.000000000 +1100
 > --- libusb20_ugen20.c.orig	2009-10-23 23:02:01.000000000 +1100
 > ***************
 > *** 449,455 ****
 >   	uint16_t len;
 >   	int error;
 >
 > - 	memset(&cdesc, 0, sizeof(cdesc));
 >   	memset(&gen_desc, 0, sizeof(gen_desc));
 >
 >   	gen_desc.ugd_data = &cdesc;
 > --- 449,454 ----
 > ***************
 > *** 469,475 ****
 >   	if (!ptr) {
 >   		return (LIBUSB20_ERROR_NO_MEM);
 >   	}
 > -   memset(ptr, 0, len);
 >   	gen_desc.ugd_data = ptr;
 >   	gen_desc.ugd_maxlen = len;
 >
 > --- 468,473 ----
 >
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 >
 
 I'm working on these issues.
 
 --HPS
 
From a.markov at complitex.ru  Fri Nov  6 07:31:12 2009
From: a.markov at complitex.ru (Alexey Markov)
Date: Fri Nov  6 12:22:59 2009
Subject: AnyDATA ADU-500A USB-modem and a lot of "ubsa_cfg_request"
	errors
References: <E419495488F746A7ABD4D8D558B4942F@complitex.local>
	<200911051359.49517.hselasky@c2i.net>
Message-ID: <8E4D6619143F4948997186D3DF828D66@complitex.local>

Hello, Hans!
On November, 05 2009 at 15:59 you wrote to freebsd-usb@freebsd.org:

 ??>> except that I got a lot of such messages on console when I run ppp:
 ??>> 
 ??>> ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED
 ??>> 
 ??>> I really want to work it out, and I have some spare time for
 ??>> experiments, but haven't any experience of debuging kernel drivers.
 ??>> Can anybody give me a clue to solve this little problem?

 HPS> Did you look in the source code:
 HPS> /sys/dev/usb/serial/ubsa.c

Yes, of course! Line #317 belongs to ubsa_cfg_request(), which just calls
another function, ucom_cfg_do_request(), with some parameters. But this
function is called several times in the code, so I've changed code of
ubsa_cfg_request() function to see, which config requests are failed:

DPRINTFN(0, "device request failed, err=%s, index=%d, value=%d "...

I have got a lot of messages like this one:

ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED,
index=10, value=1 (ignored)

where index/value pairs sequence is:

10/1, 11/1, 12/0, 0/24, 3/0, 2/3, 1/0, 16/384, 0/2, 3/0 and so forth.

It seems, that driver tried to set some config parameters like DTR, RTS,
BAUDRATE etc, and failed. But after all, modem is working (maybe, with
non-optimal settings or default settings).

So, I need an advice: what can I do to find the cause of failed config
requests?

-- 
WBR, Alexey Markov.
From a.markov at complitex.ru  Fri Nov  6 09:27:49 2009
From: a.markov at complitex.ru (Alexey Markov)
Date: Fri Nov  6 12:23:11 2009
Subject: AnyDATA ADU-500A USB-modem and a lot of "ubsa_cfg_request"
	errors
References: <E419495488F746A7ABD4D8D558B4942F@complitex.local>
	<200911051359.49517.hselasky@c2i.net>
	<8E4D6619143F4948997186D3DF828D66@complitex.local>
	<200911060929.40525.hselasky@c2i.net>
Message-ID: <3334975634114673BD39836F55BDAFD6@complitex.local>

Hello, Hans!
On November, 06 2009 at 11:29 you wrote to Alexey Markov:

 HPS> Maybe you device belongs in the ugensa.c driver and not ubsa.c

No, AnyDATA ADU-500A definitely belongs to the ubsa driver, it even
stated in the man page of ubsa. Just in case i had tried the ugensa
driver, but it doesn't work at all.

 HPS> if it does not support all those DTR/RTS ... settings?

I think, it may be connected with this PR: usb/134950

 HPS>  Do you have a datasheet for the modem in question?

Alas! There is no any datasheets neither in Google nor on manufacturer
site. :-(

-- 
WBR, Alexey Markov.
From hselasky at c2i.net  Sat Nov  7 01:04:24 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Nov  7 01:04:31 2009
Subject: usb/140325: Missing/incorrect initialisation and memory leak in
	libusb10/libusb20
In-Reply-To: <200911060951.34794.hselasky@c2i.net>
References: <200911060026.nA60QEoB073159@www.freebsd.org>
	<200911060951.34794.hselasky@c2i.net>
Message-ID: <200911070205.44380.hselasky@c2i.net>

On Friday 06 November 2009 09:51:34 Hans Petter Selasky wrote:
> On Friday 06 November 2009 01:26:14 Robert Jenssen wrote:
> > >Number:         140325
> > >Category:       usb
> > >Synopsis:       Missing/incorrect initialisation and memory leak in
> > > libusb10/libusb20 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 Nov 06 00:30:07 UTC 2009
> > >Closed-Date:
> > >Last-Modified:
> > >Originator:     Robert Jenssen
> > >Release:        8.0RC2
> > >Organization:
> > >Environment:
> >
> > FreeBSD kraken 8.0-RC2 FreeBSD 8.0-RC2 #0: Fri Nov  6 02:43:24 EST 2009
> > root@kraken:/usr/obj/usr/src/sys/KRAKEN  i386
> >
> > >Description:
> >
> > I was getting some weird values for usb configuration descriptor extra
> > length. Valgrind is a wonderful tool recently ported to FreeBSD by
> > stas@FreeBSD.org. Using valgrind I found the following problems (fixed in
> > the attached patch):
> >
> > 1. In libusb10_desc.c, libusb_get_config_descriptor(), at line 162:
> > 	pconfd->interface = (libusb_interface *) (pconfd +
> > 	    sizeof(libusb_config_descriptor));
> > should be:
> > 	pconfd->interface = (libusb_interface *) (pconfd + 1);
> > This problem causes illegal writes past the end of pconfd.
> >
> > 2. In libusb20_ugen20.c , ugen20_get_config_desc_full(), cdesc and ptr
> > are not initialised. This problem causes branches on uninitialised
> > values.
> >
> > 3. In libusb20.c, libusb20_be_free(), pbe is not free'd. This problem
> > causes a minor memory leak.
> >
> > >How-To-Repeat:
> >
> > Compile the following test, link with a debug version of libusb.a and run
> > valgrind.
> >
> > #include <libusb.h>
> > int main(void) {
> >   libusb_context *context;
> >   struct libusb_device **devs;
> >   struct libusb_config_descriptor *config;
> >
> >   libusb_init(&context);
> >   libusb_get_device_list(context, &devs);
> >   libusb_get_active_config_descriptor(devs[0], &config);
> >   libusb_free_config_descriptor(config);
> >   libusb_free_device_list(devs, 1);
> >   libusb_exit(context);
> >   return 0;
> > }
> >
> > >Fix:
> >
> > Apply the attached patch in /usr/src/lib/libusb
> >
> >
> > Patch attached with submission follows:
> >
> > *** libusb10_desc.c	2009-11-06 10:35:00.000000000 +1100
> > --- libusb10_desc.c.orig	2009-08-03 18:13:06.000000000 +1000
> > ***************
> > *** 116,133 ****
> >   	nep = 0;
> >   	nextra = pconf->extra.len;
> >
> > - #define NEXTRA_ALIGN_TO(n) (nextra=((nextra+n)/n)*n)
> >   	for (i = 0; i < nif; i++) {
> >
> >   		pinf = pconf->interface + i;
> >   		nextra += pinf->extra.len;
> > -     NEXTRA_ALIGN_TO(16);
> >   		nep += pinf->num_endpoints;
> >   		k = pinf->num_endpoints;
> >   		pend = pinf->endpoints;
> >   		while (k--) {
> >   			nextra += pend->extra.len;
> > -       NEXTRA_ALIGN_TO(16);
> >   			pend++;
> >   		}
> >
> > --- 116,130 ----
> > ***************
> > *** 136,148 ****
> >   		pinf = pinf->altsetting;
> >   		while (j--) {
> >   			nextra += pinf->extra.len;
> > -       NEXTRA_ALIGN_TO(16);
> >   			nep += pinf->num_endpoints;
> >   			k = pinf->num_endpoints;
> >   			pend = pinf->endpoints;
> >   			while (k--) {
> >   				nextra += pend->extra.len;
> > -         NEXTRA_ALIGN_TO(16);
> >   				pend++;
> >   			}
> >   			pinf++;
> > --- 133,143 ----
> > ***************
> > *** 155,163 ****
> >   	    (nalt * sizeof(libusb_interface_descriptor)) +
> >   	    (nep * sizeof(libusb_endpoint_descriptor));
> >
> > -   /* Align nextra */
> > -   NEXTRA_ALIGN_TO(16);
> > -
> >   	pconfd = malloc(nextra);
> >
> >   	if (pconfd == NULL) {
> > --- 150,155 ----
> > ***************
> > *** 167,173 ****
> >   	/* make sure memory is clean */
> >   	memset(pconfd, 0, nextra);
> >
> > ! 	pconfd->interface = (libusb_interface *) (pconfd + 1);
> >
> >   	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
> >   	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
> > --- 159,166 ----
> >   	/* make sure memory is clean */
> >   	memset(pconfd, 0, nextra);
> >
> > ! 	pconfd->interface = (libusb_interface *) (pconfd +
> > ! 	    sizeof(libusb_config_descriptor));
> >
> >   	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
> >   	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
> > ***************
> > *** 194,200 ****
> >
> >   	for (i = 0; i < nif; i++) {
> >
> > - 		pconfd->interface[i].altsetting = 0;
> >   		pconfd->interface[i].altsetting = ifd;
> >   		ifd->endpoint = endd;
> >   		endd += pconf->interface[i].num_endpoints;
> > --- 187,192 ----
> > *** libusb20.c	2009-11-06 10:35:00.000000000 +1100
> > --- libusb20.c.orig	2009-08-03 18:13:06.000000000 +1000
> > ***************
> > *** 1093,1100 ****
> >   	if (pbe->methods->exit_backend) {
> >   		pbe->methods->exit_backend(pbe);
> >   	}
> > -   /* free backend */
> > -   free(pbe);
> >   	return;
> >   }
> >
> > --- 1093,1098 ----
> > *** libusb20_desc.c	2009-11-06 10:35:00.000000000 +1100
> > --- libusb20_desc.c.orig	2009-08-03 18:13:06.000000000 +1000
> > ***************
> > *** 118,124 ****
> >   	if (lub_config == NULL) {
> >   		return (NULL);		/* out of memory */
> >   	}
> > -   memset(lub_config, 0, size);
> >   	lub_interface = (void *)(lub_config + 1);
> >   	lub_alt_interface = (void *)(lub_interface + niface_no_alt);
> >   	lub_endpoint = (void *)(lub_interface + niface);
> > --- 118,123 ----
> > *** libusb20_ugen20.c	2009-11-06 10:35:00.000000000 +1100
> > --- libusb20_ugen20.c.orig	2009-10-23 23:02:01.000000000 +1100
> > ***************
> > *** 449,455 ****
> >   	uint16_t len;
> >   	int error;
> >
> > - 	memset(&cdesc, 0, sizeof(cdesc));
> >   	memset(&gen_desc, 0, sizeof(gen_desc));
> >
> >   	gen_desc.ugd_data = &cdesc;
> > --- 449,454 ----
> > ***************
> > *** 469,475 ****
> >   	if (!ptr) {
> >   		return (LIBUSB20_ERROR_NO_MEM);
> >   	}
> > -   memset(ptr, 0, len);
> >   	gen_desc.ugd_data = ptr;
> >   	gen_desc.ugd_maxlen = len;
> >
> > --- 468,473 ----
> >
> > >Release-Note:
> > >Audit-Trail:
> > >Unformatted:
>
> I'm working on these issues.
>
> --HPS

First set of patches has been commited to USB P4 with some modifications. 
Please verify:

http://p4web.freebsd.org/chv.cgi?CH=170304

--HPS
From hselasky at c2i.net  Sat Nov  7 01:10:04 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Nov  7 01:10:10 2009
Subject: usb/140325: Missing/incorrect initialisation and memory leak in
	libusb10/libusb20
Message-ID: <200911070110.nA71A3cG064305@freefall.freebsd.org>

The following reply was made to PR usb/140325; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Robert Jenssen <robertjenssen@hotmail.com>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/140325: Missing/incorrect initialisation and memory leak in libusb10/libusb20
Date: Sat, 7 Nov 2009 02:05:43 +0100

 On Friday 06 November 2009 09:51:34 Hans Petter Selasky wrote:
 > On Friday 06 November 2009 01:26:14 Robert Jenssen wrote:
 > > >Number:         140325
 > > >Category:       usb
 > > >Synopsis:       Missing/incorrect initialisation and memory leak in
 > > > libusb10/libusb20 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 Nov 06 00:30:07 UTC 2009
 > > >Closed-Date:
 > > >Last-Modified:
 > > >Originator:     Robert Jenssen
 > > >Release:        8.0RC2
 > > >Organization:
 > > >Environment:
 > >
 > > FreeBSD kraken 8.0-RC2 FreeBSD 8.0-RC2 #0: Fri Nov  6 02:43:24 EST 2009
 > > root@kraken:/usr/obj/usr/src/sys/KRAKEN  i386
 > >
 > > >Description:
 > >
 > > I was getting some weird values for usb configuration descriptor extra
 > > length. Valgrind is a wonderful tool recently ported to FreeBSD by
 > > stas@FreeBSD.org. Using valgrind I found the following problems (fixed in
 > > the attached patch):
 > >
 > > 1. In libusb10_desc.c, libusb_get_config_descriptor(), at line 162:
 > > 	pconfd->interface = (libusb_interface *) (pconfd +
 > > 	    sizeof(libusb_config_descriptor));
 > > should be:
 > > 	pconfd->interface = (libusb_interface *) (pconfd + 1);
 > > This problem causes illegal writes past the end of pconfd.
 > >
 > > 2. In libusb20_ugen20.c , ugen20_get_config_desc_full(), cdesc and ptr
 > > are not initialised. This problem causes branches on uninitialised
 > > values.
 > >
 > > 3. In libusb20.c, libusb20_be_free(), pbe is not free'd. This problem
 > > causes a minor memory leak.
 > >
 > > >How-To-Repeat:
 > >
 > > Compile the following test, link with a debug version of libusb.a and run
 > > valgrind.
 > >
 > > #include <libusb.h>
 > > int main(void) {
 > >   libusb_context *context;
 > >   struct libusb_device **devs;
 > >   struct libusb_config_descriptor *config;
 > >
 > >   libusb_init(&context);
 > >   libusb_get_device_list(context, &devs);
 > >   libusb_get_active_config_descriptor(devs[0], &config);
 > >   libusb_free_config_descriptor(config);
 > >   libusb_free_device_list(devs, 1);
 > >   libusb_exit(context);
 > >   return 0;
 > > }
 > >
 > > >Fix:
 > >
 > > Apply the attached patch in /usr/src/lib/libusb
 > >
 > >
 > > Patch attached with submission follows:
 > >
 > > *** libusb10_desc.c	2009-11-06 10:35:00.000000000 +1100
 > > --- libusb10_desc.c.orig	2009-08-03 18:13:06.000000000 +1000
 > > ***************
 > > *** 116,133 ****
 > >   	nep = 0;
 > >   	nextra = pconf->extra.len;
 > >
 > > - #define NEXTRA_ALIGN_TO(n) (nextra=((nextra+n)/n)*n)
 > >   	for (i = 0; i < nif; i++) {
 > >
 > >   		pinf = pconf->interface + i;
 > >   		nextra += pinf->extra.len;
 > > -     NEXTRA_ALIGN_TO(16);
 > >   		nep += pinf->num_endpoints;
 > >   		k = pinf->num_endpoints;
 > >   		pend = pinf->endpoints;
 > >   		while (k--) {
 > >   			nextra += pend->extra.len;
 > > -       NEXTRA_ALIGN_TO(16);
 > >   			pend++;
 > >   		}
 > >
 > > --- 116,130 ----
 > > ***************
 > > *** 136,148 ****
 > >   		pinf = pinf->altsetting;
 > >   		while (j--) {
 > >   			nextra += pinf->extra.len;
 > > -       NEXTRA_ALIGN_TO(16);
 > >   			nep += pinf->num_endpoints;
 > >   			k = pinf->num_endpoints;
 > >   			pend = pinf->endpoints;
 > >   			while (k--) {
 > >   				nextra += pend->extra.len;
 > > -         NEXTRA_ALIGN_TO(16);
 > >   				pend++;
 > >   			}
 > >   			pinf++;
 > > --- 133,143 ----
 > > ***************
 > > *** 155,163 ****
 > >   	    (nalt * sizeof(libusb_interface_descriptor)) +
 > >   	    (nep * sizeof(libusb_endpoint_descriptor));
 > >
 > > -   /* Align nextra */
 > > -   NEXTRA_ALIGN_TO(16);
 > > -
 > >   	pconfd = malloc(nextra);
 > >
 > >   	if (pconfd == NULL) {
 > > --- 150,155 ----
 > > ***************
 > > *** 167,173 ****
 > >   	/* make sure memory is clean */
 > >   	memset(pconfd, 0, nextra);
 > >
 > > ! 	pconfd->interface = (libusb_interface *) (pconfd + 1);
 > >
 > >   	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
 > >   	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
 > > --- 159,166 ----
 > >   	/* make sure memory is clean */
 > >   	memset(pconfd, 0, nextra);
 > >
 > > ! 	pconfd->interface = (libusb_interface *) (pconfd +
 > > ! 	    sizeof(libusb_config_descriptor));
 > >
 > >   	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
 > >   	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
 > > ***************
 > > *** 194,200 ****
 > >
 > >   	for (i = 0; i < nif; i++) {
 > >
 > > - 		pconfd->interface[i].altsetting = 0;
 > >   		pconfd->interface[i].altsetting = ifd;
 > >   		ifd->endpoint = endd;
 > >   		endd += pconf->interface[i].num_endpoints;
 > > --- 187,192 ----
 > > *** libusb20.c	2009-11-06 10:35:00.000000000 +1100
 > > --- libusb20.c.orig	2009-08-03 18:13:06.000000000 +1000
 > > ***************
 > > *** 1093,1100 ****
 > >   	if (pbe->methods->exit_backend) {
 > >   		pbe->methods->exit_backend(pbe);
 > >   	}
 > > -   /* free backend */
 > > -   free(pbe);
 > >   	return;
 > >   }
 > >
 > > --- 1093,1098 ----
 > > *** libusb20_desc.c	2009-11-06 10:35:00.000000000 +1100
 > > --- libusb20_desc.c.orig	2009-08-03 18:13:06.000000000 +1000
 > > ***************
 > > *** 118,124 ****
 > >   	if (lub_config == NULL) {
 > >   		return (NULL);		/* out of memory */
 > >   	}
 > > -   memset(lub_config, 0, size);
 > >   	lub_interface = (void *)(lub_config + 1);
 > >   	lub_alt_interface = (void *)(lub_interface + niface_no_alt);
 > >   	lub_endpoint = (void *)(lub_interface + niface);
 > > --- 118,123 ----
 > > *** libusb20_ugen20.c	2009-11-06 10:35:00.000000000 +1100
 > > --- libusb20_ugen20.c.orig	2009-10-23 23:02:01.000000000 +1100
 > > ***************
 > > *** 449,455 ****
 > >   	uint16_t len;
 > >   	int error;
 > >
 > > - 	memset(&cdesc, 0, sizeof(cdesc));
 > >   	memset(&gen_desc, 0, sizeof(gen_desc));
 > >
 > >   	gen_desc.ugd_data = &cdesc;
 > > --- 449,454 ----
 > > ***************
 > > *** 469,475 ****
 > >   	if (!ptr) {
 > >   		return (LIBUSB20_ERROR_NO_MEM);
 > >   	}
 > > -   memset(ptr, 0, len);
 > >   	gen_desc.ugd_data = ptr;
 > >   	gen_desc.ugd_maxlen = len;
 > >
 > > --- 468,473 ----
 > >
 > > >Release-Note:
 > > >Audit-Trail:
 > > >Unformatted:
 >
 > I'm working on these issues.
 >
 > --HPS
 
 First set of patches has been commited to USB P4 with some modifications. 
 Please verify:
 
 http://p4web.freebsd.org/chv.cgi?CH=170304
 
 --HPS
From brucec at FreeBSD.org  Sat Nov  7 11:07:07 2009
From: brucec at FreeBSD.org (brucec@FreeBSD.org)
Date: Sat Nov  7 11:07:13 2009
Subject: usb/138563: [usb8] [patch] Increase buffer sizes to accomodate
	longer USB strings
Message-ID: <200911071107.nA7B77m1017016@freefall.freebsd.org>

Synopsis: [usb8] [patch] Increase buffer sizes to accomodate longer USB strings

State-Changed-From-To: open->closed 
State-Changed-By: brucec
State-Changed-When: Sat Nov 7 11:05:11 UTC 2009
State-Changed-Why: 
Fixed in CURRENT and 8.x

http://www.freebsd.org/cgi/query-pr.cgi?pr=138563
From alexbestms at math.uni-muenster.de  Sat Nov  7 20:10:03 2009
From: alexbestms at math.uni-muenster.de (Alexander Best)
Date: Sat Nov  7 20:10:10 2009
Subject: usb/125264: [patch] sysctl for set usb mouse rate (very useful
 for gamers - FPS games)
Message-ID: <200911072010.nA7KA2JZ090400@freefall.freebsd.org>

The following reply was made to PR usb/125264; it has been noted by GNATS.

From: Alexander Best <alexbestms@math.uni-muenster.de>
To: <bug-followup@FreeBSD.org>
Cc:  
Subject: Re: usb/125264: [patch] sysctl for set usb mouse rate (very useful
 for gamers - FPS games)
Date: Sat, 07 Nov 2009 21:08:18 +0100 (CET)

 since 8 has now become a stable branch the pr can be closed.
 
 this feature is dependant upon the usb2 stack an will not be backported to
 branches 7 and 6 which use the old usb1 stack.
 
 alex
From alexbestms at math.uni-muenster.de  Sun Nov  8 15:00:07 2009
From: alexbestms at math.uni-muenster.de (Alexander Best)
Date: Sun Nov  8 15:00:13 2009
Subject: usb/127549: [umass] [patch] Meizu MiniPlayer M6 (SL) requires
 some quirks
Message-ID: <200911081500.nA8F060W002015@freefall.freebsd.org>

The following reply was made to PR usb/127549; it has been noted by GNATS.

From: Alexander Best <alexbestms@math.uni-muenster.de>
To: <bug-followup@FreeBSD.org>
Cc:  
Subject: Re: usb/127549: [umass] [patch] Meizu MiniPlayer M6 (SL) requires
 some quirks
Date: Sun, 08 Nov 2009 15:58:25 +0100 (CET)

 i'm the originator of the pr.
 
 using this device under HEAD works without any problems. commit r187163 fixed
 the issues described in this problem report.
 
 apparently the changes to sys/cam/scsi/scsi_da.c in the initial patch weren't
 necessary and thus weren't committed by thompsa@.
 
 the changes are also in 8-stable (which was HEAD at the time the fixes got
 committed). also with r190311/r190310 umass.c and usbdevs in 7-stable got
 synced with the HEAD versions of those files meaning the fixes are in this
 branch too.
 
 6-stable is still missing these changes.
 
 please mark this pr as patched.
 
 thanks.
 alex
From gavin at FreeBSD.org  Sun Nov  8 16:14:14 2009
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Sun Nov  8 16:14:26 2009
Subject: docs/107924: [usb67] usbd(8) does not call detach
Message-ID: <200911081614.nA8GEE44072007@freefall.freebsd.org>

Synopsis: [usb67] usbd(8) does not call detach

Responsible-Changed-From-To: freebsd-usb->freebsd-docs
Responsible-Changed-By: gavin
Responsible-Changed-When: Sun Nov 8 16:11:48 UTC 2009
Responsible-Changed-Why: 
This PR is actually only relevent for 6.x, as usbd was replaced in 7.x.
Because of that, I can't see this problem being fixed in 6.x alone -
so pass over to doc team to document as a bug instead.

http://www.freebsd.org/cgi/query-pr.cgi?pr=107924
From dfilter at FreeBSD.ORG  Sun Nov  8 20:10:05 2009
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Sun Nov  8 20:10:16 2009
Subject: usb/140325: commit references a PR
Message-ID: <200911082010.nA8KA4jj069130@freefall.freebsd.org>

The following reply was made to PR usb/140325; it has been noted by GNATS.

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: usb/140325: commit references a PR
Date: Sun,  8 Nov 2009 20:04:02 +0000 (UTC)

 Author: thompsa
 Date: Sun Nov  8 20:03:52 2009
 New Revision: 199055
 URL: http://svn.freebsd.org/changeset/base/199055
 
 Log:
   - fix refcounting error during data transfer
   - fix a memory leak on the USB backend
   - fix invalid pointer computations (in one case memory outside the allocated
     area was written in LibUSB v1.0)
   - make sure memory is always initialised, also in failing cases
   - add missing functions from v1.0.4
   
   PR:		usb/140325
   Reported by:	Robert Jenssen
   Submitted by:	Hans Petter Selasky
   MFC After:	3 days
 
 Modified:
   head/lib/libusb/libusb.h
   head/lib/libusb/libusb10.c
   head/lib/libusb/libusb10_desc.c
   head/lib/libusb/libusb10_io.c
   head/lib/libusb/libusb20.c
   head/lib/libusb/libusb20_desc.c
   head/lib/libusb/libusb20_ugen20.c
 
 Modified: head/lib/libusb/libusb.h
 ==============================================================================
 --- head/lib/libusb/libusb.h	Sun Nov  8 19:59:54 2009	(r199054)
 +++ head/lib/libusb/libusb.h	Sun Nov  8 20:03:52 2009	(r199055)
 @@ -271,9 +271,11 @@ typedef struct libusb_control_setup {
  	uint16_t wLength;
  }	libusb_control_setup;
  
 +#define	LIBUSB_CONTROL_SETUP_SIZE	8	/* bytes */
 +
  typedef struct libusb_iso_packet_descriptor {
 -	unsigned int length;
 -	unsigned int actual_length;
 +	uint32_t length;
 +	uint32_t actual_length;
  	enum libusb_transfer_status status;
  }	libusb_iso_packet_descriptor __aligned(sizeof(void *));
  
 @@ -282,9 +284,9 @@ typedef void (*libusb_transfer_cb_fn) (s
  typedef struct libusb_transfer {
  	libusb_device_handle *dev_handle;
  	uint8_t	flags;
 -	unsigned int endpoint;
 +	uint32_t endpoint;
  	uint8_t type;
 -	unsigned int timeout;
 +	uint32_t timeout;
  	enum libusb_transfer_status status;
  	int	length;
  	int	actual_length;
 @@ -320,7 +322,7 @@ int	libusb_get_configuration(libusb_devi
  int	libusb_set_configuration(libusb_device_handle * devh, int configuration);
  int	libusb_claim_interface(libusb_device_handle * devh, int interface_number);
  int	libusb_release_interface(libusb_device_handle * devh, int interface_number);
 -int	libusb_reset_device(libusb_device_handle * dev);
 +int	libusb_reset_device(libusb_device_handle * devh);
  int 	libusb_kernel_driver_active(libusb_device_handle * devh, int interface);
  int 	libusb_detach_kernel_driver(libusb_device_handle * devh, int interface);
  int 	libusb_attach_kernel_driver(libusb_device_handle * devh, int interface);
 @@ -333,7 +335,8 @@ int	libusb_get_active_config_descriptor(
  int	libusb_get_config_descriptor(libusb_device * dev, uint8_t config_index, struct libusb_config_descriptor **config);
  int	libusb_get_config_descriptor_by_value(libusb_device * dev, uint8_t bConfigurationValue, struct libusb_config_descriptor **config);
  void	libusb_free_config_descriptor(struct libusb_config_descriptor *config);
 -int	libusb_get_string_descriptor_ascii(libusb_device_handle * dev, uint8_t desc_index, uint8_t *data, int length);
 +int	libusb_get_string_descriptor_ascii(libusb_device_handle * devh, uint8_t desc_index, uint8_t *data, int length);
 +int	libusb_get_descriptor(libusb_device_handle * devh, uint8_t desc_type, uint8_t desc_index, uint8_t *data, int length);
  
  /* Asynchronous device I/O */
  
 @@ -341,7 +344,16 @@ struct libusb_transfer *libusb_alloc_tra
  void	libusb_free_transfer(struct libusb_transfer *transfer);
  int	libusb_submit_transfer(struct libusb_transfer *transfer);
  int	libusb_cancel_transfer(struct libusb_transfer *transfer);
 -uint8_t *libusb_get_iso_packet_buffer_simple(struct libusb_transfer *transfer, unsigned int packet);
 +uint8_t *libusb_get_iso_packet_buffer(struct libusb_transfer *transfer, uint32_t index);
 +uint8_t *libusb_get_iso_packet_buffer_simple(struct libusb_transfer *transfer, uint32_t index);
 +void	libusb_set_iso_packet_lengths(struct libusb_transfer *transfer, uint32_t length);
 +uint8_t *libusb_control_transfer_get_data(struct libusb_transfer *transfer);
 +struct libusb_control_setup *libusb_control_transfer_get_setup(struct libusb_transfer *transfer);
 +void	libusb_fill_control_setup(uint8_t *buf, uint8_t bmRequestType, uint8_t bRequest, uint16_t wValue, uint16_t wIndex, uint16_t wLength);
 +void	libusb_fill_control_transfer(struct libusb_transfer *transfer, libusb_device_handle *devh, uint8_t *buf, libusb_transfer_cb_fn callback, void *user_data, uint32_t timeout);
 +void	libusb_fill_bulk_transfer(struct libusb_transfer *transfer, libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf, int length, libusb_transfer_cb_fn callback, void *user_data, uint32_t timeout);
 +void	libusb_fill_interrupt_transfer(struct libusb_transfer *transfer, libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf, int length, libusb_transfer_cb_fn callback, void *user_data, uint32_t timeout);
 +void	libusb_fill_iso_transfer(struct libusb_transfer *transfer, libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf, int length, int npacket, libusb_transfer_cb_fn callback, void *user_data, uint32_t timeout);
  
  /* Polling and timing */
  
 @@ -362,9 +374,14 @@ struct libusb_pollfd **libusb_get_pollfd
  
  /* Synchronous device I/O */
  
 -int	libusb_control_transfer(libusb_device_handle * devh, uint8_t bmRequestType, uint8_t bRequest, uint16_t wValue, uint16_t wIndex, uint8_t *data, uint16_t wLength, unsigned int timeout);
 -int	libusb_bulk_transfer(libusb_device_handle *devh, uint8_t endpoint, uint8_t *data, int length, int *transferred, unsigned int timeout);
 -int	libusb_interrupt_transfer(libusb_device_handle *devh, uint8_t endpoint, uint8_t *data, int length, int *transferred, unsigned int timeout);
 +int	libusb_control_transfer(libusb_device_handle * devh, uint8_t bmRequestType, uint8_t bRequest, uint16_t wValue, uint16_t wIndex, uint8_t *data, uint16_t wLength, uint32_t timeout);
 +int	libusb_bulk_transfer(libusb_device_handle * devh, uint8_t endpoint, uint8_t *data, int length, int *transferred, uint32_t timeout);
 +int	libusb_interrupt_transfer(libusb_device_handle * devh, uint8_t endpoint, uint8_t *data, int length, int *transferred, uint32_t timeout);
 +
 +/* Byte-order */
 +
 +uint16_t libusb_cpu_to_le16(uint16_t x);
 +uint16_t libusb_le16_to_cpu(uint16_t x);
  
  #if 0
  {					/* indent fix */
 
 Modified: head/lib/libusb/libusb10.c
 ==============================================================================
 --- head/lib/libusb/libusb10.c	Sun Nov  8 19:59:54 2009	(r199054)
 +++ head/lib/libusb/libusb10.c	Sun Nov  8 20:03:52 2009	(r199055)
 @@ -35,6 +35,7 @@
  #include <sys/ioctl.h>
  #include <sys/filio.h>
  #include <sys/queue.h>
 +#include <sys/endian.h>
  
  #include "libusb20.h"
  #include "libusb20_desc.h"
 @@ -185,8 +186,6 @@ libusb_get_device_list(libusb_context *c
  	/* create libusb v1.0 compliant devices */
  	i = 0;
  	while ((pdev = libusb20_be_device_foreach(usb_backend, NULL))) {
 -		/* get device into libUSB v1.0 list */
 -		libusb20_be_dequeue_device(usb_backend, pdev);
  
  		dev = malloc(sizeof(*dev));
  		if (dev == NULL) {
 @@ -199,6 +198,10 @@ libusb_get_device_list(libusb_context *c
  			libusb20_be_free(usb_backend);
  			return (LIBUSB_ERROR_NO_MEM);
  		}
 +
 +		/* get device into libUSB v1.0 list */
 +		libusb20_be_dequeue_device(usb_backend, pdev);
 +
  		memset(dev, 0, sizeof(*dev));
  
  		/* init transfer queues */
 @@ -416,6 +419,8 @@ libusb_close(struct libusb20_device *pde
  	libusb10_remove_pollfd(ctx, &dev->dev_poll);
  
  	libusb20_dev_close(pdev);
 +
 +	/* unref will free the "pdev" when the refcount reaches zero */
  	libusb_unref_device(dev);
  
  	/* make sure our event loop detects the closed device */
 @@ -1195,7 +1200,7 @@ libusb_submit_transfer(struct libusb_tra
  	struct libusb20_transfer *pxfer1;
  	struct libusb_super_transfer *sxfer;
  	struct libusb_device *dev;
 -	unsigned int endpoint;
 +	uint32_t endpoint;
  	int err;
  
  	if (uxfer == NULL)
 @@ -1252,7 +1257,7 @@ libusb_cancel_transfer(struct libusb_tra
  	struct libusb20_transfer *pxfer1;
  	struct libusb_super_transfer *sxfer;
  	struct libusb_device *dev;
 -	unsigned int endpoint;
 +	uint32_t endpoint;
  
  	if (uxfer == NULL)
  		return (LIBUSB_ERROR_INVALID_PARAM);
 @@ -1312,3 +1317,16 @@ libusb10_cancel_all_transfer(libusb_devi
  {
  	/* TODO */
  }
 +
 +uint16_t
 +libusb_cpu_to_le16(uint16_t x)
 +{
 +	return (htole16(x));
 +}
 +
 +uint16_t
 +libusb_le16_to_cpu(uint16_t x)
 +{
 +	return (le16toh(x));
 +}
 +
 
 Modified: head/lib/libusb/libusb10_desc.c
 ==============================================================================
 --- head/lib/libusb/libusb10_desc.c	Sun Nov  8 19:59:54 2009	(r199054)
 +++ head/lib/libusb/libusb10_desc.c	Sun Nov  8 20:03:52 2009	(r199055)
 @@ -35,6 +35,8 @@
  #include "libusb.h"
  #include "libusb10.h"
  
 +#define	N_ALIGN(n) (-((-(n)) & (-8UL)))
 +
  /* USB descriptors */
  
  int
 @@ -114,17 +116,17 @@ libusb_get_config_descriptor(libusb_devi
  
  	nalt = nif = pconf->num_interface;
  	nep = 0;
 -	nextra = pconf->extra.len;
 +	nextra = N_ALIGN(pconf->extra.len);
  
  	for (i = 0; i < nif; i++) {
  
  		pinf = pconf->interface + i;
 -		nextra += pinf->extra.len;
 +		nextra += N_ALIGN(pinf->extra.len);
  		nep += pinf->num_endpoints;
  		k = pinf->num_endpoints;
  		pend = pinf->endpoints;
  		while (k--) {
 -			nextra += pend->extra.len;
 +			nextra += N_ALIGN(pend->extra.len);
  			pend++;
  		}
  
 @@ -132,12 +134,12 @@ libusb_get_config_descriptor(libusb_devi
  		nalt += pinf->num_altsetting;
  		pinf = pinf->altsetting;
  		while (j--) {
 -			nextra += pinf->extra.len;
 +			nextra += N_ALIGN(pinf->extra.len);
  			nep += pinf->num_endpoints;
  			k = pinf->num_endpoints;
  			pend = pinf->endpoints;
  			while (k--) {
 -				nextra += pend->extra.len;
 +				nextra += N_ALIGN(pend->extra.len);
  				pend++;
  			}
  			pinf++;
 @@ -150,17 +152,18 @@ libusb_get_config_descriptor(libusb_devi
  	    (nalt * sizeof(libusb_interface_descriptor)) +
  	    (nep * sizeof(libusb_endpoint_descriptor));
  
 +	nextra = N_ALIGN(nextra);
 +
  	pconfd = malloc(nextra);
  
  	if (pconfd == NULL) {
  		free(pconf);
  		return (LIBUSB_ERROR_NO_MEM);
  	}
 -	/* make sure memory is clean */
 +	/* make sure memory is initialised */
  	memset(pconfd, 0, nextra);
  
 -	pconfd->interface = (libusb_interface *) (pconfd +
 -	    sizeof(libusb_config_descriptor));
 +	pconfd->interface = (libusb_interface *) (pconfd + 1);
  
  	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
  	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
 @@ -181,7 +184,7 @@ libusb_get_config_descriptor(libusb_devi
  		pconfd->extra_length = pconf->extra.len;
  		pconfd->extra = pextra;
  		memcpy(pextra, pconf->extra.ptr, pconfd->extra_length);
 -		pextra += pconfd->extra_length;
 +		pextra += N_ALIGN(pconfd->extra_length);
  	}
  	/* setup all interface and endpoint pointers */
  
 @@ -221,7 +224,7 @@ libusb_get_config_descriptor(libusb_devi
  				ifd->extra_length = pinf->extra.len;
  				ifd->extra = pextra;
  				memcpy(pextra, pinf->extra.ptr, pinf->extra.len);
 -				pextra += pinf->extra.len;
 +				pextra += N_ALIGN(pinf->extra.len);
  			}
  			for (k = 0; k < pinf->num_endpoints; k++) {
  				pend = &pinf->endpoints[k];
 @@ -238,7 +241,7 @@ libusb_get_config_descriptor(libusb_devi
  					endd->extra_length = pend->extra.len;
  					endd->extra = pextra;
  					memcpy(pextra, pend->extra.ptr, pend->extra.len);
 -					pextra += pend->extra.len;
 +					pextra += N_ALIGN(pend->extra.len);
  				}
  			}
  		}
 @@ -304,3 +307,12 @@ libusb_get_string_descriptor_ascii(libus
  
  	return (LIBUSB_ERROR_OTHER);
  }
 +
 +int
 +libusb_get_descriptor(libusb_device_handle * devh, uint8_t desc_type, 
 +    uint8_t desc_index, uint8_t *data, int length)
 +{
 +	return (libusb_control_transfer(devh, LIBUSB_ENDPOINT_IN,
 +	    LIBUSB_REQUEST_GET_DESCRIPTOR, (desc_type << 8) | desc_index, 0, data,
 +	    length, 1000));
 +}
 
 Modified: head/lib/libusb/libusb10_io.c
 ==============================================================================
 --- head/lib/libusb/libusb10_io.c	Sun Nov  8 19:59:54 2009	(r199054)
 +++ head/lib/libusb/libusb10_io.c	Sun Nov  8 20:03:52 2009	(r199055)
 @@ -32,6 +32,7 @@
  #include <time.h>
  #include <errno.h>
  #include <sys/queue.h>
 +#include <sys/endian.h>
  
  #include "libusb20.h"
  #include "libusb20_desc.h"
 @@ -148,19 +149,19 @@ libusb10_handle_events_sub(struct libusb
  		goto do_done;
  	}
  	for (i = 0; i != nfds; i++) {
 -		if (fds[i].revents == 0)
 -			continue;
  		if (ppdev[i] != NULL) {
  			dev = libusb_get_device(ppdev[i]);
  
 -			err = libusb20_dev_process(ppdev[i]);
 +			if (fds[i].revents == 0)
 +				err = 0;	/* nothing to do */
 +			else
 +				err = libusb20_dev_process(ppdev[i]);
 +
  			if (err) {
  				/* cancel all transfers - device is gone */
  				libusb10_cancel_all_transfer(dev);
 -				/*
 -				 * make sure we don't go into an infinite
 -				 * loop
 -				 */
 +
 +				/* remove USB device from polling loop */
  				libusb10_remove_pollfd(dev->ctx, &dev->dev_poll);
  			}
  			CTX_UNLOCK(ctx);
 @@ -573,3 +574,160 @@ libusb_interrupt_transfer(libusb_device_
  	DPRINTF(ctx, LIBUSB_DEBUG_FUNCTION, "libusb_interrupt_transfer leave");
  	return (ret);
  }
 +
 +uint8_t *
 +libusb_get_iso_packet_buffer(struct libusb_transfer *transfer, uint32_t index)
 +{
 +	uint8_t *ptr;
 +	uint32_t n;
 +
 +	if (transfer->num_iso_packets < 0)
 +		return (NULL);
 +
 +	if (index >= (uint32_t)transfer->num_iso_packets)
 +		return (NULL);
 +
 +	ptr = transfer->buffer;
 +	if (ptr == NULL)
 +		return (NULL);
 +
 +	for (n = 0; n != index; n++) {
 +		ptr += transfer->iso_packet_desc[n].length;
 +	}
 +	return (ptr);
 +}
 +
 +uint8_t *
 +libusb_get_iso_packet_buffer_simple(struct libusb_transfer *transfer, uint32_t index)
 +{
 +	uint8_t *ptr;
 +
 +	if (transfer->num_iso_packets < 0)
 +		return (NULL);
 +
 +	if (index >= (uint32_t)transfer->num_iso_packets)
 +		return (NULL);
 +
 +	ptr = transfer->buffer;
 +	if (ptr == NULL)
 +		return (NULL);
 +
 +	ptr += transfer->iso_packet_desc[0].length * index;
 +
 +	return (ptr);
 +}
 +
 +void
 +libusb_set_iso_packet_lengths(struct libusb_transfer *transfer, uint32_t length)
 +{
 +	int n;
 +
 +	if (transfer->num_iso_packets < 0)
 +		return;
 +
 +	for (n = 0; n != transfer->num_iso_packets; n++)
 +		transfer->iso_packet_desc[n].length = length;
 +}
 +
 +uint8_t *
 +libusb_control_transfer_get_data(struct libusb_transfer *transfer)
 +{
 +	if (transfer->buffer == NULL)
 +		return (NULL);
 +
 +	return (transfer->buffer + LIBUSB_CONTROL_SETUP_SIZE);
 +}
 +
 +struct libusb_control_setup *
 +libusb_control_transfer_get_setup(struct libusb_transfer *transfer)
 +{
 +	return ((struct libusb_control_setup *)transfer->buffer);
 +}
 +
 +void
 +libusb_fill_control_setup(uint8_t *buf, uint8_t bmRequestType,
 +    uint8_t bRequest, uint16_t wValue,
 +    uint16_t wIndex, uint16_t wLength)
 +{
 +	struct libusb_control_setup *req = (struct libusb_control_setup *)buf;
 +
 +	/* The alignment is OK for all fields below. */
 +	req->bmRequestType = bmRequestType;
 +	req->bRequest = bRequest;
 +	req->wValue = htole16(wValue);
 +	req->wIndex = htole16(wIndex);
 +	req->wLength = htole16(wLength);
 +}
 +
 +void
 +libusb_fill_control_transfer(struct libusb_transfer *transfer, 
 +    libusb_device_handle *devh, uint8_t *buf,
 +    libusb_transfer_cb_fn callback, void *user_data,
 +    uint32_t timeout)
 +{
 +	struct libusb_control_setup *setup = (struct libusb_control_setup *)buf;
 +
 +	transfer->dev_handle = devh;
 +	transfer->endpoint = 0;
 +	transfer->type = LIBUSB_TRANSFER_TYPE_CONTROL;
 +	transfer->timeout = timeout;
 +	transfer->buffer = buf;
 +	if (setup != NULL)
 +		transfer->length = LIBUSB_CONTROL_SETUP_SIZE
 +			+ le16toh(setup->wLength);
 +	else
 +		transfer->length = 0;
 +	transfer->user_data = user_data;
 +	transfer->callback = callback;
 +
 +}
 +
 +void
 +libusb_fill_bulk_transfer(struct libusb_transfer *transfer, 
 +    libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf, 
 +    int length, libusb_transfer_cb_fn callback, void *user_data,
 +    uint32_t timeout)
 +{
 +	transfer->dev_handle = devh;
 +	transfer->endpoint = endpoint;
 +	transfer->type = LIBUSB_TRANSFER_TYPE_BULK;
 +	transfer->timeout = timeout;
 +	transfer->buffer = buf;
 +	transfer->length = length;
 +	transfer->user_data = user_data;
 +	transfer->callback = callback;
 +}
 +
 +void
 +libusb_fill_interrupt_transfer(struct libusb_transfer *transfer,
 +    libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf,
 +    int length, libusb_transfer_cb_fn callback, void *user_data,
 +    uint32_t timeout)
 +{
 +	transfer->dev_handle = devh;
 +	transfer->endpoint = endpoint;
 +	transfer->type = LIBUSB_TRANSFER_TYPE_INTERRUPT;
 +	transfer->timeout = timeout;
 +	transfer->buffer = buf;
 +	transfer->length = length;
 +	transfer->user_data = user_data;
 +	transfer->callback = callback;
 +}
 +
 +void
 +libusb_fill_iso_transfer(struct libusb_transfer *transfer, 
 +    libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf,
 +    int length, int npacket, libusb_transfer_cb_fn callback,
 +    void *user_data, uint32_t timeout)
 +{
 +	transfer->dev_handle = devh;
 +	transfer->endpoint = endpoint;
 +	transfer->type = LIBUSB_TRANSFER_TYPE_ISOCHRONOUS;
 +	transfer->timeout = timeout;
 +	transfer->buffer = buf;
 +	transfer->length = length;
 +	transfer->num_iso_packets = npacket;
 +	transfer->user_data = user_data;
 +	transfer->callback = callback;
 +}
 +
 
 Modified: head/lib/libusb/libusb20.c
 ==============================================================================
 --- head/lib/libusb/libusb20.c	Sun Nov  8 19:59:54 2009	(r199054)
 +++ head/lib/libusb/libusb20.c	Sun Nov  8 20:03:52 2009	(r199055)
 @@ -630,6 +630,9 @@ libusb20_dev_req_string_sync(struct libu
  	struct LIBUSB20_CONTROL_SETUP_DECODED req;
  	int error;
  
 +	/* make sure memory is initialised */
 +	memset(ptr, 0, len);
 +
  	if (len < 4) {
  		/* invalid length */
  		return (LIBUSB20_ERROR_INVALID_PARAM);
 @@ -1093,7 +1096,8 @@ libusb20_be_free(struct libusb20_backend
  	if (pbe->methods->exit_backend) {
  		pbe->methods->exit_backend(pbe);
  	}
 -	return;
 +	/* free backend */
 +	free(pbe);
  }
  
  void
 @@ -1101,7 +1105,6 @@ libusb20_be_enqueue_device(struct libusb
  {
  	pdev->beMethods = pbe->methods;	/* copy backend methods */
  	TAILQ_INSERT_TAIL(&(pbe->usb_devs), pdev, dev_entry);
 -	return;
  }
  
  void
 @@ -1109,5 +1112,4 @@ libusb20_be_dequeue_device(struct libusb
      struct libusb20_device *pdev)
  {
  	TAILQ_REMOVE(&(pbe->usb_devs), pdev, dev_entry);
 -	return;
  }
 
 Modified: head/lib/libusb/libusb20_desc.c
 ==============================================================================
 --- head/lib/libusb/libusb20_desc.c	Sun Nov  8 19:59:54 2009	(r199054)
 +++ head/lib/libusb/libusb20_desc.c	Sun Nov  8 20:03:52 2009	(r199055)
 @@ -118,6 +118,9 @@ libusb20_parse_config_desc(const void *c
  	if (lub_config == NULL) {
  		return (NULL);		/* out of memory */
  	}
 +	/* make sure memory is initialised */
 +	memset(lub_config, 0, size);
 +
  	lub_interface = (void *)(lub_config + 1);
  	lub_alt_interface = (void *)(lub_interface + niface_no_alt);
  	lub_endpoint = (void *)(lub_interface + niface);
 
 Modified: head/lib/libusb/libusb20_ugen20.c
 ==============================================================================
 --- head/lib/libusb/libusb20_ugen20.c	Sun Nov  8 19:59:54 2009	(r199054)
 +++ head/lib/libusb/libusb20_ugen20.c	Sun Nov  8 20:03:52 2009	(r199055)
 @@ -449,6 +449,8 @@ ugen20_get_config_desc_full(struct libus
  	uint16_t len;
  	int error;
  
 +	/* make sure memory is initialised */
 +	memset(&cdesc, 0, sizeof(cdesc));
  	memset(&gen_desc, 0, sizeof(gen_desc));
  
  	gen_desc.ugd_data = &cdesc;
 @@ -468,6 +470,10 @@ ugen20_get_config_desc_full(struct libus
  	if (!ptr) {
  		return (LIBUSB20_ERROR_NO_MEM);
  	}
 +
 +	/* make sure memory is initialised */
 +	memset(ptr, 0, len);
 +
  	gen_desc.ugd_data = ptr;
  	gen_desc.ugd_maxlen = len;
  
 _______________________________________________
 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 dfilter at FreeBSD.ORG  Sun Nov  8 20:50:02 2009
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Sun Nov  8 20:50:09 2009
Subject: usb/140242: commit references a PR
Message-ID: <200911082050.nA8Ko2oC005116@freefall.freebsd.org>

The following reply was made to PR usb/140242; it has been noted by GNATS.

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: usb/140242: commit references a PR
Date: Sun,  8 Nov 2009 20:45:09 +0000 (UTC)

 Author: thompsa
 Date: Sun Nov  8 20:44:55 2009
 New Revision: 199057
 URL: http://svn.freebsd.org/changeset/base/199057
 
 Log:
   ehci_init() will do reset and set the usbrev flag.  Fix problem where
   ehci_reset() was called before ehci_init().
   
   PR:		usb/140242
   Submitted by:	Sebastian Huber
 
 Modified:
   head/sys/dev/usb/controller/ehci_ixp4xx.c
   head/sys/dev/usb/controller/ehci_mbus.c
   head/sys/dev/usb/controller/ehci_pci.c
 
 Modified: head/sys/dev/usb/controller/ehci_ixp4xx.c
 ==============================================================================
 --- head/sys/dev/usb/controller/ehci_ixp4xx.c	Sun Nov  8 20:17:15 2009	(r199056)
 +++ head/sys/dev/usb/controller/ehci_ixp4xx.c	Sun Nov  8 20:44:55 2009	(r199057)
 @@ -157,8 +157,6 @@ ehci_ixp_attach(device_t self)
  		return (ENOMEM);
  	}
  
 -	sc->sc_bus.usbrev = USB_REV_2_0;
 -
  	/* NB: hints fix the memory location and irq */
  
  	rid = 0;
 @@ -230,7 +228,6 @@ ehci_ixp_attach(device_t self)
  		     | EHCI_SCFLG_BIGEMMIO
  		     | EHCI_SCFLG_NORESTERM
  		     ;
 -	(void) ehci_reset(sc);
  
  	err = ehci_init(sc);
  	if (!err) {
 
 Modified: head/sys/dev/usb/controller/ehci_mbus.c
 ==============================================================================
 --- head/sys/dev/usb/controller/ehci_mbus.c	Sun Nov  8 20:17:15 2009	(r199056)
 +++ head/sys/dev/usb/controller/ehci_mbus.c	Sun Nov  8 20:44:55 2009	(r199057)
 @@ -166,8 +166,6 @@ ehci_mbus_attach(device_t self)
  		return (ENOMEM);
  	}
  
 -	sc->sc_bus.usbrev = USB_REV_2_0;
 -
  	rid = 0;
  	sc->sc_io_res = bus_alloc_resource_any(self, SYS_RES_MEMORY, &rid, RF_ACTIVE);
  	if (!sc->sc_io_res) {
 
 Modified: head/sys/dev/usb/controller/ehci_pci.c
 ==============================================================================
 --- head/sys/dev/usb/controller/ehci_pci.c	Sun Nov  8 20:17:15 2009	(r199056)
 +++ head/sys/dev/usb/controller/ehci_pci.c	Sun Nov  8 20:44:55 2009	(r199057)
 @@ -318,13 +318,11 @@ ehci_pci_attach(device_t self)
  		device_printf(self, "pre-2.0 USB revision (ignored)\n");
  		/* fallthrough */
  	case PCI_USB_REV_2_0:
 -		sc->sc_bus.usbrev = USB_REV_2_0;
  		break;
  	default:
  		/* Quirk for Parallels Desktop 4.0 */
  		device_printf(self, "USB revision is unknown. Assuming v2.0.\n");
 -		sc->sc_bus.usbrev = USB_REV_2_0;
 -                break;
 +		break;
  	}
  
  	rid = PCI_CBMEM;
 _______________________________________________
 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 bugmaster at FreeBSD.org  Mon Nov  9 11:07:05 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov  9 11:09:41 2009
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200911091107.nA9B74O7079147@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/140325   usb        Missing/incorrect initialisation and memory leak in li
o usb/140259   usb        libusb-1.0 portability/compatibility nits
o usb/140242   usb        dev/usb/controller/ehci_ix4xx.c shortcomings
o usb/140236   usb        [msdosfs] Labels wiped on external Journaled USB HDD o
o usb/140160   usb        USB ports are no longer "active" after ACPI suspend/re
o usb/139990   usb        [panic] Kernel frequently panics after printing
o usb/139598   usb        [umass] CAM reports "xptioctl: put "device pass" in yo
o usb/139243   usb        [uhci] unplug prolific USB serial -> uhci_abort_xfer: 
o usb/139142   usb        [regression] ehci drivers (NVIDIA nForce4 USB 2.0 cont
o usb/138915   usb        [patch][usb8][usb67] add support for SheevaPlug serial
o usb/138904   usb        [rum] unpluging USB wifi card panics system
f usb/138882   usb        [ohci] [panic] Can't install FreeBSD 7.2 due to ohci p
o usb/138879   usb        [uftdi] [patch] Patch to add support for CTI USB-Mini 
o usb/138798   usb        8.0-BETA4 can't boot from USB flash drive [regression]
o usb/138675   usb        [usb8] [panic] page fault, perhaps in USB
o usb/138659   usb        [usb8][uftdi] driver broken in RELENG_8/CURRENT
o usb/138389   usb        [usb8] [patch] NULL pointer dereference in usb_endpoin
o usb/138175   usb        [usb67] [boot] System cannot boot, when USB reader wit
o usb/138172   usb        Additional dev id for u3g (Option mini PCIe)
o usb/138138   usb        Novatel U760 for u3g (Verizon and Bell Canada)
o usb/138124   usb        [usb8] Axed uaudio functionality in the usbng (alterna
o usb/138119   usb        MultiBay CDROM (propably on USB bus) is not recognized
o usb/137872   usb        slow booting on usb flash drive
f usb/137848   usb        Page fault when using an USB bluetooth adapter
o usb/137806   usb        [ukbd] USB keyboard doesn't work until it's unplugged
o usb/137763   usb        [usb67][ukbd] Logitech wireless keyboard media keys no
o usb/137616   usb        [usb67][usb8][usbdevs] [patch]: usbdevs update: Please
o usb/137377   usb        [usb8] Support for Huawei E180
o usb/137341   usb        [usb8][rum] driver if_rum doesn't work at all and thro
p usb/137226   usb        [usb67][patch] quirk for Philips extern USB disk
o usb/137190   usb        [usb8][patch] inhibit spurious button releases for som
o usb/137189   usb        [usb8][patch] create and use sysctl nodes for HID repo
p usb/137188   usb        [usb8][patch] correctly handle USB report descriptors 
o usb/137129   usb        SteelSeries Ikari USB laser mouse not attaching
p usb/136761   usb        [usbdevs][usb67][patch] Teach usbdevs / u3g(4) about H
o usb/135938   usb        [aue] aue driver only passes traffic in promisc mode
f usb/135857   usb        RTL8187 Wireless Adapter
o usb/135575   usb        [usbdevs] [patch] Add HTC Wizard phone vid/pid informa
o usb/135542   usb        [keyboard] boot loader does not work with a usb keyboa
p usb/135372   usb        [usb67][umass] Quirk report for Teclast TL-C300 usb me
o usb/135348   usb        [umass] USB Drive Hangs with ZFS (JMicron USB2/eSata)
o usb/135206   usb        machine reboots when inserted USB device
o usb/135200   usb        SAMSUNG i740 usb mass: Synchronize cache failed, statu
o usb/135182   usb        UMASS quirk - Olympus FE20 camera
o usb/134950   usb        Lowering DTR for USB-modem via ubsa is not possible
o usb/134633   usb        Add support for WILLCOM03(SHARP smart phone)
o usb/134631   usb        [usbdevs] [patch] WiSPY DBx support requires usb tweak
o usb/134299   usb        Kernel Panic plugging in MF626 USB UMTS Stick u3g
o usb/134193   usb        System freeze on usb MP3 player insertion
o usb/134117   usb        [Patch] Add support for 'Option GlobeTrotter HSDPA Mod
o usb/134085   usb        [umass] Adding usb quirk for Sony USB flash drive
o usb/133989   usb        [newusb] [ukbd] USB keyboard dead at mountroot> prompt
o usb/133712   usb        [ural] [patch] RE: Fixed an issue with ural(4) that wa
o usb/133390   usb        umass crashes system in 7.1 when Olympus D-540 attache
o usb/133296   usb        [rum] driver not working properly in hostap mode
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] [rum] Kernel panic after NOMEM caused by
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
o 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/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/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
o 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
s 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] [panic] enabling usb keyboard and mouse support
o usb/127248   usb        [ucom] panic while uplcom devices attaach and detach
o usb/127222   usb        [ohci] Regression in 7.0 usb storage generic driver
o usb/126884   usb        [ugen] [patch] Bug in buffer handling in ugen.c
o usb/126848   usb        [usb]: USB Keyboard hangs during Installation
o usb/126740   usb        [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be
o usb/126519   usb        [usb] [panic] panic when plugging in an iphone
o kern/126396  usb        [panic] kernel panic after unplug USB Bluetooth device
o usb/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
p 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 kern/124130  usb        [usb] gmirror fails to start usb devices that were pre
o usb/123969   usb        [usb] Supermicro H8SMi-2 usb problem: port reset faile
o usb/123714   usb        [usb] [panic] Panic when hald-storage-probe runs with 
o usb/123691   usb        usbd(8): usbd hangs
o usb/123690   usb        [usb] [panic] Panic on USB device insertion when usb l
o usb/123611   usb        [usb] BBB reset failed, STALLED from Imation/Mitsumi U
o usb/123509   usb        [umass] continuous reset Samsung SGH-G600 phone
o usb/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        [new driver] [patch] New driver for Sierra Wireless 3G
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] [panic] FreeBSD fails to boot with usb legacy s
o usb/121232   usb        [usb] [panic] USB CardBus card removal causes reboot s
p usb/121184   usb        [uipaq] [patch] add ids from linux ipaq driver (plus a
o usb/121169   usb        [umass] Issues with usb mp3 player
o usb/121045   usb        [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS
o usb/120786   usb        [usb] [panic] Kernel panic when forced umount of a det
o usb/120729   usb        [panic] fault while in kernel mode with connecting USB
o usb/120572   usb        [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/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        [usb67] [usb8] [umass] [patch] Problem with connection
o conf/114013  usb        [patch] WITHOUT_USB allow to compil a lot of USB stuff
o usb/113060   usb        [usb67] [ulpt] [patch] Samsung printer not working in 
o usb/110856   usb        [usb67] [ugen] [patch] interrupt in msgs are truncated
s usb/108344   usb        [usb67] [atausb] [panic] kernel with atausb panics whe
o usb/107827   usb        [usb67] [ohci] [panic] ohci_add_done addr not found
o usb/107388   usb        [usb67] [usb8] [new driver] [patch] add utoppy device 
o usb/107243   usb        [usb67] [cam] [quirk] [patch] Apacer USB Flash Drive q
o usb/106041   usb        [usb67] [usb8] [request] FreeBSD does not recognise Mu
o usb/105361   usb        [usb67] [panic] Kernel panic during unmounting mass st
s usb/103917   usb        [usb67] [uhub] USB driver reports "Addr 0 should never
o usb/103418   usb        [usb67] [usb8] [patch] [request] usbhidctl(8) add abil
o usb/103046   usb        [usb67] [ulpt] [patch] ulpt event driven I/O with sele
o usb/101775   usb        [usb67] [usb8] [libusbhid] [patch] possible error in r
o usb/101761   usb        [usb67] [patch] [request] usb.h: increase maximal size
o usb/100746   usb        [usb67] [ukbd] system does not boot due to USB keyboar
o usb/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/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/83977    usb        [ucom] [panic] ucom1: open bulk out error (addr 2): IN
o usb/83863    usb        [ugen] Communication problem between opensc/openct via
o usb/83756    usb        [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe
o usb/83563    usb        [umass] [panic] Page Fault while detaching Mpman Usb d
o usb/83504    usb        [kernel] [patch] SpeedTouch USB stop working on recent
o usb/82660    usb        [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic
s usb/82569    usb        [umass] [panic] USB mass storage plug/unplug causes sy
o usb/82520    usb        [udbp] [reboot] Reboot when USL101 connected
o usb/82350    usb        [ucom] [panic] null pointer dereference in USB stack
o usb/81621    usb        [ehci] [hang] external hd hangs under load on ehci
o usb/80935    usb        [uvisor] [patch] uvisor.c is not work with CLIE TH55.
o usb/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        [sound] [hang] Use of sound mixer causes system freeze
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] [regression] 5.3-STABLE(2005 1/4) detect USB h
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

313 problems total.

From hsn at sendmail.cz  Mon Nov  9 11:30:05 2009
From: hsn at sendmail.cz (Radim Kolar)
Date: Mon Nov  9 11:30:12 2009
Subject: usb/71455: [umass] Slow USB umass performance of 5.3
Message-ID: <200911091130.nA9BU58k099301@freefall.freebsd.org>

The following reply was made to PR usb/71455; it has been noted by GNATS.

From: Radim Kolar <hsn@sendmail.cz>
To: bug-followup@FreeBSD.org, hsn@netmag.cz
Cc:  
Subject: Re: usb/71455: [umass] Slow USB umass performance of 5.3
Date: Mon, 09 Nov 2009 12:26:03 +0100

 close this pr, its for outdated freebsd version.
From linimon at FreeBSD.org  Tue Nov 10 08:20:08 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Tue Nov 10 08:20:15 2009
Subject: usb/125264: [patch] sysctl for set usb mouse rate (very useful
	for gamers - FPS games)
Message-ID: <200911100820.nAA8K71N014320@freefall.freebsd.org>

Synopsis: [patch] sysctl for set usb mouse rate (very useful for gamers - FPS games)

State-Changed-From-To: patched->closed
State-Changed-By: linimon
State-Changed-When: Tue Nov 10 08:19:13 UTC 2009
State-Changed-Why: 
A fix has been committed to -8, but the usb stack changed so much from
7 to 8 that it is not possible to back-port the fix to 6 or 7.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125264
From dfilter at FreeBSD.ORG  Wed Nov 11 01:30:08 2009
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Wed Nov 11 01:30:15 2009
Subject: usb/140325: commit references a PR
Message-ID: <200911110130.nAB1U7O7003160@freefall.freebsd.org>

The following reply was made to PR usb/140325; it has been noted by GNATS.

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: usb/140325: commit references a PR
Date: Wed, 11 Nov 2009 01:28:09 +0000 (UTC)

 Author: thompsa
 Date: Wed Nov 11 01:27:58 2009
 New Revision: 199165
 URL: http://svn.freebsd.org/changeset/base/199165
 
 Log:
   MFC r199055
   
    - fix refcounting error during data transfer
    - fix a memory leak on the USB backend
    - fix invalid pointer computations (in one case memory outside the allocated
      area was written in LibUSB v1.0)
    - make sure memory is always initialised, also in failing cases
    - add missing functions from v1.0.4
   
   PR:		usb/140325
 
 Modified:
   stable/8/lib/libusb/libusb.h
   stable/8/lib/libusb/libusb10.c
   stable/8/lib/libusb/libusb10_desc.c
   stable/8/lib/libusb/libusb10_io.c
   stable/8/lib/libusb/libusb20.c
   stable/8/lib/libusb/libusb20_desc.c
   stable/8/lib/libusb/libusb20_ugen20.c
 Directory Properties:
   stable/8/lib/libusb/   (props changed)
   stable/8/lib/libusb/usb.h   (props changed)
 
 Modified: stable/8/lib/libusb/libusb.h
 ==============================================================================
 --- stable/8/lib/libusb/libusb.h	Wed Nov 11 01:11:08 2009	(r199164)
 +++ stable/8/lib/libusb/libusb.h	Wed Nov 11 01:27:58 2009	(r199165)
 @@ -271,9 +271,11 @@ typedef struct libusb_control_setup {
  	uint16_t wLength;
  }	libusb_control_setup;
  
 +#define	LIBUSB_CONTROL_SETUP_SIZE	8	/* bytes */
 +
  typedef struct libusb_iso_packet_descriptor {
 -	unsigned int length;
 -	unsigned int actual_length;
 +	uint32_t length;
 +	uint32_t actual_length;
  	enum libusb_transfer_status status;
  }	libusb_iso_packet_descriptor __aligned(sizeof(void *));
  
 @@ -282,9 +284,9 @@ typedef void (*libusb_transfer_cb_fn) (s
  typedef struct libusb_transfer {
  	libusb_device_handle *dev_handle;
  	uint8_t	flags;
 -	unsigned int endpoint;
 +	uint32_t endpoint;
  	uint8_t type;
 -	unsigned int timeout;
 +	uint32_t timeout;
  	enum libusb_transfer_status status;
  	int	length;
  	int	actual_length;
 @@ -320,7 +322,7 @@ int	libusb_get_configuration(libusb_devi
  int	libusb_set_configuration(libusb_device_handle * devh, int configuration);
  int	libusb_claim_interface(libusb_device_handle * devh, int interface_number);
  int	libusb_release_interface(libusb_device_handle * devh, int interface_number);
 -int	libusb_reset_device(libusb_device_handle * dev);
 +int	libusb_reset_device(libusb_device_handle * devh);
  int 	libusb_kernel_driver_active(libusb_device_handle * devh, int interface);
  int 	libusb_detach_kernel_driver(libusb_device_handle * devh, int interface);
  int 	libusb_attach_kernel_driver(libusb_device_handle * devh, int interface);
 @@ -333,7 +335,8 @@ int	libusb_get_active_config_descriptor(
  int	libusb_get_config_descriptor(libusb_device * dev, uint8_t config_index, struct libusb_config_descriptor **config);
  int	libusb_get_config_descriptor_by_value(libusb_device * dev, uint8_t bConfigurationValue, struct libusb_config_descriptor **config);
  void	libusb_free_config_descriptor(struct libusb_config_descriptor *config);
 -int	libusb_get_string_descriptor_ascii(libusb_device_handle * dev, uint8_t desc_index, uint8_t *data, int length);
 +int	libusb_get_string_descriptor_ascii(libusb_device_handle * devh, uint8_t desc_index, uint8_t *data, int length);
 +int	libusb_get_descriptor(libusb_device_handle * devh, uint8_t desc_type, uint8_t desc_index, uint8_t *data, int length);
  
  /* Asynchronous device I/O */
  
 @@ -341,7 +344,16 @@ struct libusb_transfer *libusb_alloc_tra
  void	libusb_free_transfer(struct libusb_transfer *transfer);
  int	libusb_submit_transfer(struct libusb_transfer *transfer);
  int	libusb_cancel_transfer(struct libusb_transfer *transfer);
 -uint8_t *libusb_get_iso_packet_buffer_simple(struct libusb_transfer *transfer, unsigned int packet);
 +uint8_t *libusb_get_iso_packet_buffer(struct libusb_transfer *transfer, uint32_t index);
 +uint8_t *libusb_get_iso_packet_buffer_simple(struct libusb_transfer *transfer, uint32_t index);
 +void	libusb_set_iso_packet_lengths(struct libusb_transfer *transfer, uint32_t length);
 +uint8_t *libusb_control_transfer_get_data(struct libusb_transfer *transfer);
 +struct libusb_control_setup *libusb_control_transfer_get_setup(struct libusb_transfer *transfer);
 +void	libusb_fill_control_setup(uint8_t *buf, uint8_t bmRequestType, uint8_t bRequest, uint16_t wValue, uint16_t wIndex, uint16_t wLength);
 +void	libusb_fill_control_transfer(struct libusb_transfer *transfer, libusb_device_handle *devh, uint8_t *buf, libusb_transfer_cb_fn callback, void *user_data, uint32_t timeout);
 +void	libusb_fill_bulk_transfer(struct libusb_transfer *transfer, libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf, int length, libusb_transfer_cb_fn callback, void *user_data, uint32_t timeout);
 +void	libusb_fill_interrupt_transfer(struct libusb_transfer *transfer, libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf, int length, libusb_transfer_cb_fn callback, void *user_data, uint32_t timeout);
 +void	libusb_fill_iso_transfer(struct libusb_transfer *transfer, libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf, int length, int npacket, libusb_transfer_cb_fn callback, void *user_data, uint32_t timeout);
  
  /* Polling and timing */
  
 @@ -362,9 +374,14 @@ struct libusb_pollfd **libusb_get_pollfd
  
  /* Synchronous device I/O */
  
 -int	libusb_control_transfer(libusb_device_handle * devh, uint8_t bmRequestType, uint8_t bRequest, uint16_t wValue, uint16_t wIndex, uint8_t *data, uint16_t wLength, unsigned int timeout);
 -int	libusb_bulk_transfer(libusb_device_handle *devh, uint8_t endpoint, uint8_t *data, int length, int *transferred, unsigned int timeout);
 -int	libusb_interrupt_transfer(libusb_device_handle *devh, uint8_t endpoint, uint8_t *data, int length, int *transferred, unsigned int timeout);
 +int	libusb_control_transfer(libusb_device_handle * devh, uint8_t bmRequestType, uint8_t bRequest, uint16_t wValue, uint16_t wIndex, uint8_t *data, uint16_t wLength, uint32_t timeout);
 +int	libusb_bulk_transfer(libusb_device_handle * devh, uint8_t endpoint, uint8_t *data, int length, int *transferred, uint32_t timeout);
 +int	libusb_interrupt_transfer(libusb_device_handle * devh, uint8_t endpoint, uint8_t *data, int length, int *transferred, uint32_t timeout);
 +
 +/* Byte-order */
 +
 +uint16_t libusb_cpu_to_le16(uint16_t x);
 +uint16_t libusb_le16_to_cpu(uint16_t x);
  
  #if 0
  {					/* indent fix */
 
 Modified: stable/8/lib/libusb/libusb10.c
 ==============================================================================
 --- stable/8/lib/libusb/libusb10.c	Wed Nov 11 01:11:08 2009	(r199164)
 +++ stable/8/lib/libusb/libusb10.c	Wed Nov 11 01:27:58 2009	(r199165)
 @@ -35,6 +35,7 @@
  #include <sys/ioctl.h>
  #include <sys/filio.h>
  #include <sys/queue.h>
 +#include <sys/endian.h>
  
  #include "libusb20.h"
  #include "libusb20_desc.h"
 @@ -185,8 +186,6 @@ libusb_get_device_list(libusb_context *c
  	/* create libusb v1.0 compliant devices */
  	i = 0;
  	while ((pdev = libusb20_be_device_foreach(usb_backend, NULL))) {
 -		/* get device into libUSB v1.0 list */
 -		libusb20_be_dequeue_device(usb_backend, pdev);
  
  		dev = malloc(sizeof(*dev));
  		if (dev == NULL) {
 @@ -199,6 +198,10 @@ libusb_get_device_list(libusb_context *c
  			libusb20_be_free(usb_backend);
  			return (LIBUSB_ERROR_NO_MEM);
  		}
 +
 +		/* get device into libUSB v1.0 list */
 +		libusb20_be_dequeue_device(usb_backend, pdev);
 +
  		memset(dev, 0, sizeof(*dev));
  
  		/* init transfer queues */
 @@ -416,6 +419,8 @@ libusb_close(struct libusb20_device *pde
  	libusb10_remove_pollfd(ctx, &dev->dev_poll);
  
  	libusb20_dev_close(pdev);
 +
 +	/* unref will free the "pdev" when the refcount reaches zero */
  	libusb_unref_device(dev);
  
  	/* make sure our event loop detects the closed device */
 @@ -1195,7 +1200,7 @@ libusb_submit_transfer(struct libusb_tra
  	struct libusb20_transfer *pxfer1;
  	struct libusb_super_transfer *sxfer;
  	struct libusb_device *dev;
 -	unsigned int endpoint;
 +	uint32_t endpoint;
  	int err;
  
  	if (uxfer == NULL)
 @@ -1252,7 +1257,7 @@ libusb_cancel_transfer(struct libusb_tra
  	struct libusb20_transfer *pxfer1;
  	struct libusb_super_transfer *sxfer;
  	struct libusb_device *dev;
 -	unsigned int endpoint;
 +	uint32_t endpoint;
  
  	if (uxfer == NULL)
  		return (LIBUSB_ERROR_INVALID_PARAM);
 @@ -1312,3 +1317,16 @@ libusb10_cancel_all_transfer(libusb_devi
  {
  	/* TODO */
  }
 +
 +uint16_t
 +libusb_cpu_to_le16(uint16_t x)
 +{
 +	return (htole16(x));
 +}
 +
 +uint16_t
 +libusb_le16_to_cpu(uint16_t x)
 +{
 +	return (le16toh(x));
 +}
 +
 
 Modified: stable/8/lib/libusb/libusb10_desc.c
 ==============================================================================
 --- stable/8/lib/libusb/libusb10_desc.c	Wed Nov 11 01:11:08 2009	(r199164)
 +++ stable/8/lib/libusb/libusb10_desc.c	Wed Nov 11 01:27:58 2009	(r199165)
 @@ -35,6 +35,8 @@
  #include "libusb.h"
  #include "libusb10.h"
  
 +#define	N_ALIGN(n) (-((-(n)) & (-8UL)))
 +
  /* USB descriptors */
  
  int
 @@ -114,17 +116,17 @@ libusb_get_config_descriptor(libusb_devi
  
  	nalt = nif = pconf->num_interface;
  	nep = 0;
 -	nextra = pconf->extra.len;
 +	nextra = N_ALIGN(pconf->extra.len);
  
  	for (i = 0; i < nif; i++) {
  
  		pinf = pconf->interface + i;
 -		nextra += pinf->extra.len;
 +		nextra += N_ALIGN(pinf->extra.len);
  		nep += pinf->num_endpoints;
  		k = pinf->num_endpoints;
  		pend = pinf->endpoints;
  		while (k--) {
 -			nextra += pend->extra.len;
 +			nextra += N_ALIGN(pend->extra.len);
  			pend++;
  		}
  
 @@ -132,12 +134,12 @@ libusb_get_config_descriptor(libusb_devi
  		nalt += pinf->num_altsetting;
  		pinf = pinf->altsetting;
  		while (j--) {
 -			nextra += pinf->extra.len;
 +			nextra += N_ALIGN(pinf->extra.len);
  			nep += pinf->num_endpoints;
  			k = pinf->num_endpoints;
  			pend = pinf->endpoints;
  			while (k--) {
 -				nextra += pend->extra.len;
 +				nextra += N_ALIGN(pend->extra.len);
  				pend++;
  			}
  			pinf++;
 @@ -150,17 +152,18 @@ libusb_get_config_descriptor(libusb_devi
  	    (nalt * sizeof(libusb_interface_descriptor)) +
  	    (nep * sizeof(libusb_endpoint_descriptor));
  
 +	nextra = N_ALIGN(nextra);
 +
  	pconfd = malloc(nextra);
  
  	if (pconfd == NULL) {
  		free(pconf);
  		return (LIBUSB_ERROR_NO_MEM);
  	}
 -	/* make sure memory is clean */
 +	/* make sure memory is initialised */
  	memset(pconfd, 0, nextra);
  
 -	pconfd->interface = (libusb_interface *) (pconfd +
 -	    sizeof(libusb_config_descriptor));
 +	pconfd->interface = (libusb_interface *) (pconfd + 1);
  
  	ifd = (libusb_interface_descriptor *) (pconfd->interface + nif);
  	endd = (libusb_endpoint_descriptor *) (ifd + nalt);
 @@ -181,7 +184,7 @@ libusb_get_config_descriptor(libusb_devi
  		pconfd->extra_length = pconf->extra.len;
  		pconfd->extra = pextra;
  		memcpy(pextra, pconf->extra.ptr, pconfd->extra_length);
 -		pextra += pconfd->extra_length;
 +		pextra += N_ALIGN(pconfd->extra_length);
  	}
  	/* setup all interface and endpoint pointers */
  
 @@ -221,7 +224,7 @@ libusb_get_config_descriptor(libusb_devi
  				ifd->extra_length = pinf->extra.len;
  				ifd->extra = pextra;
  				memcpy(pextra, pinf->extra.ptr, pinf->extra.len);
 -				pextra += pinf->extra.len;
 +				pextra += N_ALIGN(pinf->extra.len);
  			}
  			for (k = 0; k < pinf->num_endpoints; k++) {
  				pend = &pinf->endpoints[k];
 @@ -238,7 +241,7 @@ libusb_get_config_descriptor(libusb_devi
  					endd->extra_length = pend->extra.len;
  					endd->extra = pextra;
  					memcpy(pextra, pend->extra.ptr, pend->extra.len);
 -					pextra += pend->extra.len;
 +					pextra += N_ALIGN(pend->extra.len);
  				}
  			}
  		}
 @@ -304,3 +307,12 @@ libusb_get_string_descriptor_ascii(libus
  
  	return (LIBUSB_ERROR_OTHER);
  }
 +
 +int
 +libusb_get_descriptor(libusb_device_handle * devh, uint8_t desc_type, 
 +    uint8_t desc_index, uint8_t *data, int length)
 +{
 +	return (libusb_control_transfer(devh, LIBUSB_ENDPOINT_IN,
 +	    LIBUSB_REQUEST_GET_DESCRIPTOR, (desc_type << 8) | desc_index, 0, data,
 +	    length, 1000));
 +}
 
 Modified: stable/8/lib/libusb/libusb10_io.c
 ==============================================================================
 --- stable/8/lib/libusb/libusb10_io.c	Wed Nov 11 01:11:08 2009	(r199164)
 +++ stable/8/lib/libusb/libusb10_io.c	Wed Nov 11 01:27:58 2009	(r199165)
 @@ -32,6 +32,7 @@
  #include <time.h>
  #include <errno.h>
  #include <sys/queue.h>
 +#include <sys/endian.h>
  
  #include "libusb20.h"
  #include "libusb20_desc.h"
 @@ -148,19 +149,19 @@ libusb10_handle_events_sub(struct libusb
  		goto do_done;
  	}
  	for (i = 0; i != nfds; i++) {
 -		if (fds[i].revents == 0)
 -			continue;
  		if (ppdev[i] != NULL) {
  			dev = libusb_get_device(ppdev[i]);
  
 -			err = libusb20_dev_process(ppdev[i]);
 +			if (fds[i].revents == 0)
 +				err = 0;	/* nothing to do */
 +			else
 +				err = libusb20_dev_process(ppdev[i]);
 +
  			if (err) {
  				/* cancel all transfers - device is gone */
  				libusb10_cancel_all_transfer(dev);
 -				/*
 -				 * make sure we don't go into an infinite
 -				 * loop
 -				 */
 +
 +				/* remove USB device from polling loop */
  				libusb10_remove_pollfd(dev->ctx, &dev->dev_poll);
  			}
  			CTX_UNLOCK(ctx);
 @@ -573,3 +574,160 @@ libusb_interrupt_transfer(libusb_device_
  	DPRINTF(ctx, LIBUSB_DEBUG_FUNCTION, "libusb_interrupt_transfer leave");
  	return (ret);
  }
 +
 +uint8_t *
 +libusb_get_iso_packet_buffer(struct libusb_transfer *transfer, uint32_t index)
 +{
 +	uint8_t *ptr;
 +	uint32_t n;
 +
 +	if (transfer->num_iso_packets < 0)
 +		return (NULL);
 +
 +	if (index >= (uint32_t)transfer->num_iso_packets)
 +		return (NULL);
 +
 +	ptr = transfer->buffer;
 +	if (ptr == NULL)
 +		return (NULL);
 +
 +	for (n = 0; n != index; n++) {
 +		ptr += transfer->iso_packet_desc[n].length;
 +	}
 +	return (ptr);
 +}
 +
 +uint8_t *
 +libusb_get_iso_packet_buffer_simple(struct libusb_transfer *transfer, uint32_t index)
 +{
 +	uint8_t *ptr;
 +
 +	if (transfer->num_iso_packets < 0)
 +		return (NULL);
 +
 +	if (index >= (uint32_t)transfer->num_iso_packets)
 +		return (NULL);
 +
 +	ptr = transfer->buffer;
 +	if (ptr == NULL)
 +		return (NULL);
 +
 +	ptr += transfer->iso_packet_desc[0].length * index;
 +
 +	return (ptr);
 +}
 +
 +void
 +libusb_set_iso_packet_lengths(struct libusb_transfer *transfer, uint32_t length)
 +{
 +	int n;
 +
 +	if (transfer->num_iso_packets < 0)
 +		return;
 +
 +	for (n = 0; n != transfer->num_iso_packets; n++)
 +		transfer->iso_packet_desc[n].length = length;
 +}
 +
 +uint8_t *
 +libusb_control_transfer_get_data(struct libusb_transfer *transfer)
 +{
 +	if (transfer->buffer == NULL)
 +		return (NULL);
 +
 +	return (transfer->buffer + LIBUSB_CONTROL_SETUP_SIZE);
 +}
 +
 +struct libusb_control_setup *
 +libusb_control_transfer_get_setup(struct libusb_transfer *transfer)
 +{
 +	return ((struct libusb_control_setup *)transfer->buffer);
 +}
 +
 +void
 +libusb_fill_control_setup(uint8_t *buf, uint8_t bmRequestType,
 +    uint8_t bRequest, uint16_t wValue,
 +    uint16_t wIndex, uint16_t wLength)
 +{
 +	struct libusb_control_setup *req = (struct libusb_control_setup *)buf;
 +
 +	/* The alignment is OK for all fields below. */
 +	req->bmRequestType = bmRequestType;
 +	req->bRequest = bRequest;
 +	req->wValue = htole16(wValue);
 +	req->wIndex = htole16(wIndex);
 +	req->wLength = htole16(wLength);
 +}
 +
 +void
 +libusb_fill_control_transfer(struct libusb_transfer *transfer, 
 +    libusb_device_handle *devh, uint8_t *buf,
 +    libusb_transfer_cb_fn callback, void *user_data,
 +    uint32_t timeout)
 +{
 +	struct libusb_control_setup *setup = (struct libusb_control_setup *)buf;
 +
 +	transfer->dev_handle = devh;
 +	transfer->endpoint = 0;
 +	transfer->type = LIBUSB_TRANSFER_TYPE_CONTROL;
 +	transfer->timeout = timeout;
 +	transfer->buffer = buf;
 +	if (setup != NULL)
 +		transfer->length = LIBUSB_CONTROL_SETUP_SIZE
 +			+ le16toh(setup->wLength);
 +	else
 +		transfer->length = 0;
 +	transfer->user_data = user_data;
 +	transfer->callback = callback;
 +
 +}
 +
 +void
 +libusb_fill_bulk_transfer(struct libusb_transfer *transfer, 
 +    libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf, 
 +    int length, libusb_transfer_cb_fn callback, void *user_data,
 +    uint32_t timeout)
 +{
 +	transfer->dev_handle = devh;
 +	transfer->endpoint = endpoint;
 +	transfer->type = LIBUSB_TRANSFER_TYPE_BULK;
 +	transfer->timeout = timeout;
 +	transfer->buffer = buf;
 +	transfer->length = length;
 +	transfer->user_data = user_data;
 +	transfer->callback = callback;
 +}
 +
 +void
 +libusb_fill_interrupt_transfer(struct libusb_transfer *transfer,
 +    libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf,
 +    int length, libusb_transfer_cb_fn callback, void *user_data,
 +    uint32_t timeout)
 +{
 +	transfer->dev_handle = devh;
 +	transfer->endpoint = endpoint;
 +	transfer->type = LIBUSB_TRANSFER_TYPE_INTERRUPT;
 +	transfer->timeout = timeout;
 +	transfer->buffer = buf;
 +	transfer->length = length;
 +	transfer->user_data = user_data;
 +	transfer->callback = callback;
 +}
 +
 +void
 +libusb_fill_iso_transfer(struct libusb_transfer *transfer, 
 +    libusb_device_handle *devh, uint8_t endpoint, uint8_t *buf,
 +    int length, int npacket, libusb_transfer_cb_fn callback,
 +    void *user_data, uint32_t timeout)
 +{
 +	transfer->dev_handle = devh;
 +	transfer->endpoint = endpoint;
 +	transfer->type = LIBUSB_TRANSFER_TYPE_ISOCHRONOUS;
 +	transfer->timeout = timeout;
 +	transfer->buffer = buf;
 +	transfer->length = length;
 +	transfer->num_iso_packets = npacket;
 +	transfer->user_data = user_data;
 +	transfer->callback = callback;
 +}
 +
 
 Modified: stable/8/lib/libusb/libusb20.c
 ==============================================================================
 --- stable/8/lib/libusb/libusb20.c	Wed Nov 11 01:11:08 2009	(r199164)
 +++ stable/8/lib/libusb/libusb20.c	Wed Nov 11 01:27:58 2009	(r199165)
 @@ -630,6 +630,9 @@ libusb20_dev_req_string_sync(struct libu
  	struct LIBUSB20_CONTROL_SETUP_DECODED req;
  	int error;
  
 +	/* make sure memory is initialised */
 +	memset(ptr, 0, len);
 +
  	if (len < 4) {
  		/* invalid length */
  		return (LIBUSB20_ERROR_INVALID_PARAM);
 @@ -1093,7 +1096,8 @@ libusb20_be_free(struct libusb20_backend
  	if (pbe->methods->exit_backend) {
  		pbe->methods->exit_backend(pbe);
  	}
 -	return;
 +	/* free backend */
 +	free(pbe);
  }
  
  void
 @@ -1101,7 +1105,6 @@ libusb20_be_enqueue_device(struct libusb
  {
  	pdev->beMethods = pbe->methods;	/* copy backend methods */
  	TAILQ_INSERT_TAIL(&(pbe->usb_devs), pdev, dev_entry);
 -	return;
  }
  
  void
 @@ -1109,5 +1112,4 @@ libusb20_be_dequeue_device(struct libusb
      struct libusb20_device *pdev)
  {
  	TAILQ_REMOVE(&(pbe->usb_devs), pdev, dev_entry);
 -	return;
  }
 
 Modified: stable/8/lib/libusb/libusb20_desc.c
 ==============================================================================
 --- stable/8/lib/libusb/libusb20_desc.c	Wed Nov 11 01:11:08 2009	(r199164)
 +++ stable/8/lib/libusb/libusb20_desc.c	Wed Nov 11 01:27:58 2009	(r199165)
 @@ -118,6 +118,9 @@ libusb20_parse_config_desc(const void *c
  	if (lub_config == NULL) {
  		return (NULL);		/* out of memory */
  	}
 +	/* make sure memory is initialised */
 +	memset(lub_config, 0, size);
 +
  	lub_interface = (void *)(lub_config + 1);
  	lub_alt_interface = (void *)(lub_interface + niface_no_alt);
  	lub_endpoint = (void *)(lub_interface + niface);
 
 Modified: stable/8/lib/libusb/libusb20_ugen20.c
 ==============================================================================
 --- stable/8/lib/libusb/libusb20_ugen20.c	Wed Nov 11 01:11:08 2009	(r199164)
 +++ stable/8/lib/libusb/libusb20_ugen20.c	Wed Nov 11 01:27:58 2009	(r199165)
 @@ -449,6 +449,8 @@ ugen20_get_config_desc_full(struct libus
  	uint16_t len;
  	int error;
  
 +	/* make sure memory is initialised */
 +	memset(&cdesc, 0, sizeof(cdesc));
  	memset(&gen_desc, 0, sizeof(gen_desc));
  
  	gen_desc.ugd_data = &cdesc;
 @@ -468,6 +470,10 @@ ugen20_get_config_desc_full(struct libus
  	if (!ptr) {
  		return (LIBUSB20_ERROR_NO_MEM);
  	}
 +
 +	/* make sure memory is initialised */
 +	memset(ptr, 0, len);
 +
  	gen_desc.ugd_data = ptr;
  	gen_desc.ugd_maxlen = len;
  
 _______________________________________________
 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 linimon at FreeBSD.org  Wed Nov 11 18:01:30 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Wed Nov 11 18:01:36 2009
Subject: usb/140477: [umass] [patch] allow boot-time attachment of daX
	devices to GEOM_ELI
Message-ID: <200911111801.nABI1U1O001790@freefall.freebsd.org>

Old Synopsis: [patch] allow boot-time attachment of daX devices to GEOM_ELI
New Synopsis: [umass] [patch] allow boot-time attachment of daX devices to GEOM_ELI

Responsible-Changed-From-To: freebsd-bugs->freebsd-usb
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Nov 11 17:59:57 UTC 2009
Responsible-Changed-Why: 
The patch affects both usb and scsi, so it will need to be reviewed by
multiple people, but just pick usb to start with.

http://www.freebsd.org/cgi/query-pr.cgi?pr=140477
From scottl at samsco.org  Wed Nov 11 21:30:05 2009
From: scottl at samsco.org (Scott Long)
Date: Wed Nov 11 21:30:11 2009
Subject: usb/140477: [patch] allow boot-time attachment of daX devices
	to GEOM_ELI
Message-ID: <200911112130.nABLU4oo074267@freefall.freebsd.org>

The following reply was made to PR usb/140477; it has been noted by GNATS.

From: Scott Long <scottl@samsco.org>
To: FreeBSD-gnats-submit@freebsd.org
Cc:  
Subject: Re: usb/140477: [patch] allow boot-time attachment of daX devices to GEOM_ELI
Date: Wed, 11 Nov 2009 11:37:55 -0700

 I understand your concern about G_ELI.  I'm not a fan of  
 root_mount_hold, and I'd really like it to go away in favor of the  
 SYSINIT and INTRHOOK mechanisms that already existed before  
 root_mount_hold was introduced.  It's really a hack, and a messy one  
 that requires extensive modification to the system to work; i.e.  
 root_mount_hold calls need to be added to just about every storage  
 driver, not just 'ad' and 'da', while the existing SYSINIT based  
 ordering does not.
 
 I'll look into this and see if I can come up with an alternate solution.
 
 Scott
 
From eculp at encontacto.net  Thu Nov 12 00:09:42 2009
From: eculp at encontacto.net (eculp)
Date: Thu Nov 12 00:09:49 2009
Subject: Epson MFP CX5600  was  Re: usb2 + scanner HP ScanJet 4300C
Message-ID: <20091111175935.19402q31p6gbp1q8@econet.encontacto.net>

Based on the Luigi's link included in an almost year old email to  
these lists, I purchased an Epson CX5600 with all intentions of using  
the scanner but never seemed to get around to configuring it.  Many  
things have happened since then including new USB, etc. etc. The  
printer still works fine using cups.  I have just tried to configure  
the scanner without luck.  A device isn't created in /dev and only the  
printer is recognized on boot:

Nov 11 17:24:51 ed kernel: uhub0: 5 ports with 5 removable, self powered
Nov 11 17:24:51 ed kernel: uhub2: 5 ports with 5 removable, self powered
Nov 11 17:24:51 ed kernel: GEOM: ad4s2: geometry does not match label  
(255h,63s != 16h,63s).
Nov 11 17:24:51 ed kernel: GEOM: ad4s3: geometry does not match label  
(255h,63s != 16h,63s).
Nov 11 17:24:51 ed kernel: uhub1: 5 ports with 5 removable, self powered
Nov 11 17:24:51 ed kernel: uhub3: 5 ports with 5 removable, self powered
Nov 11 17:24:51 ed kernel: ugen1.2: <SuYin> at usbus1
Nov 11 17:24:51 ed kernel: ugen2.2: <EPSON> at usbus2
Nov 11 17:24:51 ed kernel: ulpt0: <USB2.0 Printer> on usbus2
Nov 11 17:24:51 ed kernel: ulpt0: using bi-directional mode

I installed:

drwxr-xr-x  2 root  wheel       512 Nov 11 16:27 sane-backends-1.0.20_4
drwxr-xr-x  2 root  wheel       512 Nov 11 16:41 sane-frontends-1.0.14_5
drwxr-xr-x  2 root  wheel       512 Nov 11 16:47 xsane-0.996_1


added entries in usbdevs and devd.conf.

I don't really know where to go from here.  I haven't configured a  
scanner for freebsd in years and am totally lost.  It isn't really  
that important but it would certainly be handy.

I am running up to date Current:

FreeBSD ed.local.net.mx 9.0-CURRENT FreeBSD 9.0-CURRENT #360: Wed Nov  
11 06:55:25 CST 2009      
root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO  i386

That could be part of the problem.

Thanks,

ed

P.S. Luigi thanks for the great tutoral.  I'm pretty sure the problems
      are from the changes made in current this year.


----- Forwarded message from rizzo@iet.unipi.it -----
     Date: Fri, 12 Dec 2008 23:04:28 +0100
     From: Luigi Rizzo <rizzo@iet.unipi.it>
  Subject: Re: usb2 + scanner HP ScanJet 4300C
       To: Oliver Fromme <olli@lurza.secnetix.de>
       Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org

On Fri, Dec 12, 2008 at 09:27:27PM +0100, Oliver Fromme wrote:
> Hi,
>
> I've got a HP ScanJet 4300C that seems to be a little bit
> stubborn.
>
...
> Is there anything I can do, except for forgetting about
> this scanner alltogether?

one option is to put the device IDs in uscanner.c and see if
it is recognised. But other than that, i wouldn't waste much time:
for 50..80 euro you can get one of the
Epson multifunction printer scanners (i have personally
tried DX4400 to DX7050) which are well supported and
extremely reliable.

see http://info.iet.unipi.it/~luigi/FreeBSD/dx5050.html

	cheers
	luigi
_______________________________________________
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"


----- End forwarded message -----
From wblock at wonkity.com  Thu Nov 12 04:33:51 2009
From: wblock at wonkity.com (Warren Block)
Date: Thu Nov 12 04:33:57 2009
Subject: Epson MFP CX5600  was  Re: usb2 + scanner HP ScanJet 4300C
In-Reply-To: <20091111175935.19402q31p6gbp1q8@econet.encontacto.net>
References: <20091111175935.19402q31p6gbp1q8@econet.encontacto.net>
Message-ID: <alpine.BSF.2.00.0911112040440.70214@wonkity.com>

On Wed, 11 Nov 2009, eculp wrote:

> Based on the Luigi's link included in an almost year old email to these 
> lists, I purchased an Epson CX5600 with all intentions of using the scanner 
> but never seemed to get around to configuring it.  Many things have happened 
> since then including new USB, etc. etc. The printer still works fine using 
> cups.  I have just tried to configure the scanner without luck.  A device 
> isn't created in /dev and only the printer is recognized on boot:
>
> Nov 11 17:24:51 ed kernel: uhub0: 5 ports with 5 removable, self powered
> Nov 11 17:24:51 ed kernel: uhub2: 5 ports with 5 removable, self powered
> Nov 11 17:24:51 ed kernel: GEOM: ad4s2: geometry does not match label 
> (255h,63s != 16h,63s).
> Nov 11 17:24:51 ed kernel: GEOM: ad4s3: geometry does not match label 
> (255h,63s != 16h,63s).
> Nov 11 17:24:51 ed kernel: uhub1: 5 ports with 5 removable, self powered
> Nov 11 17:24:51 ed kernel: uhub3: 5 ports with 5 removable, self powered
> Nov 11 17:24:51 ed kernel: ugen1.2: <SuYin> at usbus1
> Nov 11 17:24:51 ed kernel: ugen2.2: <EPSON> at usbus2
> Nov 11 17:24:51 ed kernel: ulpt0: <USB2.0 Printer> on usbus2
> Nov 11 17:24:51 ed kernel: ulpt0: using bi-directional mode
>
> I installed:
>
> drwxr-xr-x  2 root  wheel       512 Nov 11 16:27 sane-backends-1.0.20_4
> drwxr-xr-x  2 root  wheel       512 Nov 11 16:41 sane-frontends-1.0.14_5
> drwxr-xr-x  2 root  wheel       512 Nov 11 16:47 xsane-0.996_1
>
> added entries in usbdevs

Not needed for scanners any more, I think.

> and devd.conf.

Things are different than they used to be since uscanner(4) is gone. 
Now, you can just refer to the USB device, probably ugen2.2 from above. 
The Handbook scanning section does have notes for FreeBSD 8.

However, I wanted to create a static device for the scanner at 
uscanner0.


First, devd is used to recognize the scanner on attach.  devd.conf:

attach 20 {
         device-name "ugen[0-9]+";
         match "vendor" "0x04b8";
         match "product" "0x010a";
         action "/bin/ln -sf /dev/$device-name /dev/uscanner0; \
                 /sbin/devfs rule applyset"

detach 20 {
         device-name "ugen[0-9]+";
         match "vendor" "0x04b8";
         match "product" "0x010a";
         action "/bin/rm /dev/uscanner0"

Note that this doesn't care which ugen device is created, it looks for 
the vendor and product ID of the scanner.  When that device attaches, a 
link is created to /dev/uscanner0 and devfs rules are reapplied so the 
owner and permissions are set on that link.


Speaking of which, devfs.rules:

add path 'ugen*' mode 0660 group operator
add path 'usb*' mode 0770 group operator
add path 'uscanner*' mode 0660 group operator

About that middle rule: I found that was needed to let non-root members 
of the operator group scan.  It may be a mistake.


And finally, /usr/local/etc/sane.d/epson.conf has just:

usb /dev/uscanner0

-Warren Block * Rapid City, South Dakota USA
From bzeeb-lists at lists.zabbadoz.net  Thu Nov 12 07:40:04 2009
From: bzeeb-lists at lists.zabbadoz.net (Bjoern A. Zeeb)
Date: Thu Nov 12 07:40:10 2009
Subject: usb/140477: [umass] [patch] allow boot-time attachment of daX
 devices to GEOM_ELI
Message-ID: <200911120740.nAC7e31B032671@freefall.freebsd.org>

The following reply was made to PR usb/140477; it has been noted by GNATS.

From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To: bug-followup@FreeBSD.org, rea-fbsd@codelabs.ru
Cc:  
Subject: Re: usb/140477: [umass] [patch] allow boot-time attachment of daX
 devices to GEOM_ELI
Date: Thu, 12 Nov 2009 07:28:03 +0000 (UTC)

 Hi,
 
 has this changed recently, that it no longer works?  I seem to
 remember that it had perfectly worked before this year.
 
 /bz
 
 -- 
 Bjoern A. Zeeb         It will not break if you know what you are doing.
From hselasky at c2i.net  Thu Nov 12 07:59:25 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Nov 12 07:59:40 2009
Subject: Epson MFP CX5600  was  Re: usb2 + scanner HP ScanJet 4300C
In-Reply-To: <20091111175935.19402q31p6gbp1q8@econet.encontacto.net>
References: <20091111175935.19402q31p6gbp1q8@econet.encontacto.net>
Message-ID: <200911120858.25508.hselasky@c2i.net>

On Thursday 12 November 2009 00:59:35 eculp wrote:
> Based on the Luigi's link included in an almost year old email to
> these lists, I purchased an Epson CX5600 with all intentions of using
> the scanner but never seemed to get around to configuring it.  Many
> things have happened since then including new USB, etc. etc. The
> printer still works fine using cups.  I have just tried to configure
> the scanner without luck.  A device isn't created in /dev and only the
> printer is recognized on boot:
>
> Nov 11 17:24:51 ed kernel: uhub0: 5 ports with 5 removable, self powered
> Nov 11 17:24:51 ed kernel: uhub2: 5 ports with 5 removable, self powered
> Nov 11 17:24:51 ed kernel: GEOM: ad4s2: geometry does not match label
> (255h,63s != 16h,63s).
> Nov 11 17:24:51 ed kernel: GEOM: ad4s3: geometry does not match label
> (255h,63s != 16h,63s).
> Nov 11 17:24:51 ed kernel: uhub1: 5 ports with 5 removable, self powered
> Nov 11 17:24:51 ed kernel: uhub3: 5 ports with 5 removable, self powered
> Nov 11 17:24:51 ed kernel: ugen1.2: <SuYin> at usbus1
> Nov 11 17:24:51 ed kernel: ugen2.2: <EPSON> at usbus2
> Nov 11 17:24:51 ed kernel: ulpt0: <USB2.0 Printer> on usbus2
> Nov 11 17:24:51 ed kernel: ulpt0: using bi-directional mode
>
> I installed:
>
> drwxr-xr-x  2 root  wheel       512 Nov 11 16:27 sane-backends-1.0.20_4
> drwxr-xr-x  2 root  wheel       512 Nov 11 16:41 sane-frontends-1.0.14_5
> drwxr-xr-x  2 root  wheel       512 Nov 11 16:47 xsane-0.996_1
>
>
> added entries in usbdevs and devd.conf.
>
> I don't really know where to go from here.  I haven't configured a
> scanner for freebsd in years and am totally lost.  It isn't really
> that important but it would certainly be handy.

Hi,

Your scanner should be available under /dev/usb/1.2.xxx according to ugen1.2

What do you mean by configure? Upload firmware?

--HPS

>
> I am running up to date Current:
>
> FreeBSD ed.local.net.mx 9.0-CURRENT FreeBSD 9.0-CURRENT #360: Wed Nov
> 11 06:55:25 CST 2009
> root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO  i386
>
> That could be part of the problem.
>
> Thanks,
>
> ed
>
> P.S. Luigi thanks for the great tutoral.  I'm pretty sure the problems
>       are from the changes made in current this year.
>
>
> ----- Forwarded message from rizzo@iet.unipi.it -----
>      Date: Fri, 12 Dec 2008 23:04:28 +0100
>      From: Luigi Rizzo <rizzo@iet.unipi.it>
>   Subject: Re: usb2 + scanner HP ScanJet 4300C
>        To: Oliver Fromme <olli@lurza.secnetix.de>
>        Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org
>
> On Fri, Dec 12, 2008 at 09:27:27PM +0100, Oliver Fromme wrote:
> > Hi,
> >
> > I've got a HP ScanJet 4300C that seems to be a little bit
> > stubborn.
>
> ...
>
> > Is there anything I can do, except for forgetting about
> > this scanner alltogether?
>
> one option is to put the device IDs in uscanner.c and see if
> it is recognised. But other than that, i wouldn't waste much time:
> for 50..80 euro you can get one of the
> Epson multifunction printer scanners (i have personally
> tried DX4400 to DX7050) which are well supported and
> extremely reliable.
>
> see http://info.iet.unipi.it/~luigi/FreeBSD/dx5050.html
>
> 	cheers
> 	luigi
> _______________________________________________
> 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"
>
>
> ----- End forwarded message -----
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

From rea-fbsd at codelabs.ru  Thu Nov 12 09:20:03 2009
From: rea-fbsd at codelabs.ru (Eygene Ryabinkin)
Date: Thu Nov 12 09:20:09 2009
Subject: usb/140477: [umass] [patch] allow boot-time attachment of daX
 devices to GEOM_ELI
Message-ID: <200911120920.nAC9K3g1022490@freefall.freebsd.org>

The following reply was made to PR usb/140477; it has been noted by GNATS.

From: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Cc: bug-followup@FreeBSD.org
Subject: Re: usb/140477: [umass] [patch] allow boot-time attachment of daX
 devices to GEOM_ELI
Date: Thu, 12 Nov 2009 12:11:17 +0300

 Bjoern, good day.
 
 Thu, Nov 12, 2009 at 07:28:03AM +0000, Bjoern A. Zeeb wrote:
 > has this changed recently, that it no longer works?  I seem to
 > remember that it had perfectly worked before this year.
 
 Yes, it used to work with up to 7.<anything>.  But it seems that with
 the new USB stack we have asynchronous discovery and attachment, so
 other subsystems are started when this process isn't yet fully
 completed, so root mount is getting "closer" and, for my case, root
 mount typically waits only for the completion of USB tasks.
 
 My gut feeling is that the device discovery prior to the USBv2 was
 done synchronously, but with USBv2 kernel use async callbacks.  Though,
 I may be wrong in this judgement.
 
 You can try it yourself -- plugged USB stick with geli volume that is
 marked as attach-on-boot should show the current behaviour.
 -- 
 Eygene
  _                ___       _.--.   #
  \`.|\..----...-'`   `-._.-'_.-'`   #  Remember that it is hard
  /  ' `         ,       __.--'      #  to read the on-line manual
  )/' _/     \   `-_,   /            #  while single-stepping the kernel.
  `-'" `"\_  ,_.-;_.-\_ ',  fsc/as   #
      _.-'_./   {_.'   ; /           #    -- FreeBSD Developers handbook
     {_.-``-'         {_/            #
From bzeeb-lists at lists.zabbadoz.net  Thu Nov 12 10:50:04 2009
From: bzeeb-lists at lists.zabbadoz.net (Bjoern A. Zeeb)
Date: Thu Nov 12 10:50:10 2009
Subject: usb/140477: [umass] [patch] allow boot-time attachment of daX
 devices to GEOM_ELI
Message-ID: <200911121050.nACAo3nK001667@freefall.freebsd.org>

The following reply was made to PR usb/140477; it has been noted by GNATS.

From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
Cc: bug-followup@FreeBSD.org
Subject: Re: usb/140477: [umass] [patch] allow boot-time attachment of daX
 devices to GEOM_ELI
Date: Thu, 12 Nov 2009 10:43:56 +0000 (UTC)

 On Thu, 12 Nov 2009, Eygene Ryabinkin wrote:
 
 Hi,
 
 > Bjoern, good day.
 >
 > Thu, Nov 12, 2009 at 07:28:03AM +0000, Bjoern A. Zeeb wrote:
 >> has this changed recently, that it no longer works?  I seem to
 >> remember that it had perfectly worked before this year.
 >
 > Yes, it used to work with up to 7.<anything>.  But it seems that with
 > the new USB stack we have asynchronous discovery and attachment, so
 > other subsystems are started when this process isn't yet fully
 > completed, so root mount is getting "closer" and, for my case, root
 > mount typically waits only for the completion of USB tasks.
 >
 > My gut feeling is that the device discovery prior to the USBv2 was
 > done synchronously, but with USBv2 kernel use async callbacks.  Though,
 > I may be wrong in this judgement.
 >
 > You can try it yourself -- plugged USB stick with geli volume that is
 > marked as attach-on-boot should show the current behaviour.
 
 I am doing that regularly, on HEAD (last updated in October). But I
 see I lacked coffee this morning, wanted to say "earlier this year".
 
 -- 
 Bjoern A. Zeeb         It will not break if you know what you are doing.
From rea-fbsd at codelabs.ru  Thu Nov 12 13:40:04 2009
From: rea-fbsd at codelabs.ru (Eygene Ryabinkin)
Date: Thu Nov 12 13:40:11 2009
Subject: usb/140477: [umass] [patch] allow boot-time attachment of daX
 devices to GEOM_ELI
Message-ID: <200911121340.nACDe3Dc051859@freefall.freebsd.org>

The following reply was made to PR usb/140477; it has been noted by GNATS.

From: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Cc: bug-followup@FreeBSD.org
Subject: Re: usb/140477: [umass] [patch] allow boot-time attachment of daX
 devices to GEOM_ELI
Date: Thu, 12 Nov 2009 16:29:54 +0300

 Thu, Nov 12, 2009 at 10:43:56AM +0000, Bjoern A. Zeeb wrote:
 > I am doing that regularly, on HEAD (last updated in October). But I
 > see I lacked coffee this morning, wanted to say "earlier this year".
 
 Then it will be interesting to see on which point your kernel is
 attaching the daX devices.  Could you, please, show your dmesg?
 -- 
 Eygene
  _                ___       _.--.   #
  \`.|\..----...-'`   `-._.-'_.-'`   #  Remember that it is hard
  /  ' `         ,       __.--'      #  to read the on-line manual
  )/' _/     \   `-_,   /            #  while single-stepping the kernel.
  `-'" `"\_  ,_.-;_.-\_ ',  fsc/as   #
      _.-'_./   {_.'   ; /           #    -- FreeBSD Developers handbook
     {_.-``-'         {_/            #
From sasha.devel at gmail.com  Thu Nov 12 20:08:04 2009
From: sasha.devel at gmail.com (Alexander Samarin)
Date: Thu Nov 12 20:08:12 2009
Subject: [madwimax] madwimax-0.1.1 patch for FreeBSD 8 (very buggy)
Message-ID: <1258055618.4944.22.camel@eien>

HOWTO:

yume$ fetch "ftp://ftp.enikasoft.ru/pub/madwimax-freebsd8.patch"
yume$ fetch "http://madwimax.googlecode.com/files/madwimax-0.1.1.tar.gz"
yume$ tar xf madwimax-0.1.1.tar.gz

yume$ cd madwimax-0.1.1
yume$ export libusb1_CFLAGS="-I/usr/include"
yume$ export libusb1_LIBS="-L/usr/lib -lusb"
yume$ ./configure --without-man-pages
yume$ echo '#define MADWIMAX_VERSION_MACRO "madwimax-0.1.1-freebsd"' > \
        include/madwimax_version.h
yume$ cd src
yume$ patch < ../../madwimax-freebsd8.patch
yume$ make

yume$ su
yume# kldload if_tap
yume# ./madwimax
...
Allocated tap interface: tap0
...

On other console:

yume$ su
yume# dhclient tap0
yume# cat /var/db/dhclient.leases.tap
...
  option routers XXX.XXX.XXX.XXX;
  option domain-name-servers YYY.YYY.YYY.YYY;
...
yume# route delete default
yume# route add default XXX.XXX.XXX.XXX
yume# echo "nameserver YYY.YYY.YYY.YYY" > /etc/resolv.conf



Tested on FreeBSD 8.0-RC2 i386; modem Samsung SWC-U200.
Usually works fine (ping normal - less than 1% packet loss; http ok)
Sometimes crashes in libusb:

yume# ./madwimax
...
Allocated tap interface: tap0
zsh: segmentation fault (core dumped)  ./madwimax
yume# gdb ./madwimax madwimax.core
GNU gdb 6.1.1 [FreeBSD]
...
Core was generated by `madwimax'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libthr.so.3...done.
Loaded symbols for /lib/libthr.so.3
Reading symbols from /usr/lib/libusb.so.2...done.
Loaded symbols for /usr/lib/libusb.so.2
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  libusb10_submit_transfer_sub (pdev=0x28209480, endpoint=4 '\004') at
libusb10.c:1116
1116 if (sxfer->rem_len)
[New Thread 28201140 (LWP 100077)]
(gdb) bt
#0  libusb10_submit_transfer_sub (pdev=0x28209480, endpoint=4 '\004') at
libusb10.c:1116
#1  0x280acf23 in libusb_cancel_transfer (uxfer=0x282250c8) at
libusb10.c:1297
#2  0x280ac615 in libusb10_do_transfer (devh=0x28209480,
endpoint=Variable "endpoint" is not available.
) at libusb10_io.c:509
#3  0x280ac757 in libusb_bulk_transfer (devh=0x28209480,
endpoint=Variable "endpoint" is not available.
) at libusb10_io.c:552
#4  0x08049874 in set_data (data=0xbfbfab80 "WC\024", size=26) at
wimax.c:224
#5  0x0804a914 in main (argc=1, argv=0x280ad160) at wimax.c:652
(gdb) print *pxfer0 
$1 = {pdev = 0x28209480, callback = 0x280ad160
<libusb10_bulk_intr_proxy>, priv_sc0 = 0x28209480,
  priv_sc1 = 0x0, ppBuffer = 0x28226094, pLength = 0x28226090,
maxTotalLength = 16384,
  maxFrames = 1, nFrames = 1, aFrames = 1, timeout = 0, timeComplete =
0, trIndex = 16,
  maxPacketLen = 512, flags = 0 '\0', status = 1 '\001', is_opened = 1
'\001',
  is_pending = 1 '\001', is_cancel = 1 '\001', is_draining = 0 '\0',
is_restart = 0 '\0'}
(gdb) print *pxfer1
$2 = {pdev = 0x28209480, callback = 0x280b0380 <dummy_callback>,
priv_sc0 = 0x0,
  priv_sc1 = 0x0, ppBuffer = 0x0, pLength = 0x0, maxTotalLength = 0,
  maxFrames = 0, nFrames = 0, aFrames = 0, timeout = 0, timeComplete =
0, trIndex = 17,
  maxPacketLen = 0, flags = 0 '\0', status = 0 '\0', is_opened = 0 '\0',
  is_pending = 0 '\0', is_cancel = 0 '\0', is_draining = 0 '\0',
is_restart = 0 '\0'}
(gdb) print *sxfer 
Variable "sxfer" is not available.

Near libusb10.c:1116:
1115 sxfer = libusb20_tr_get_priv_sc1(pxfer0);
1116 if (sxfer->rem_len)

Near libusb20.c:258:
257 void   *
258 libusb20_tr_get_priv_sc1(struct libusb20_transfer *xfer)
259 {
260 return (xfer->priv_sc1);
261 }

Because of pxfer0->priv_sc1 is NULL from core dump, I think that it is
a libusb implementation bug.



PS:
Also I've commented this call at wimax.c:847:

847 //libusb_cancel_transfer(req_transfer);

because of segmentation fault when program going to terminate.
(this is inside exit_release_resources() function)


--
Best regards,  Alexander Samarin
    mailto:sasha@enikasoft.ru
    https://www.fsora.ru (waits for FreeBSD 8.0-RELEASE)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: madwimax-freebsd8.patch
Type: text/x-patch
Size: 4657 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20091112/8b537071/madwimax-freebsd8.bin
From ivoras at freebsd.org  Fri Nov 13 14:20:01 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Fri Nov 13 14:20:07 2009
Subject: HP iLO virtual console / virtual CDROM device not recognized in 8?
Message-ID: <hdjptm$2mc$1@ger.gmane.org>

Hi,

HP's virtual console allows remote (network) mounting of ISO images & CD 
devices on servers. In 7.x this worked fine but apparently with the new 
USB stack the device (which is emulated as a USB-attached CD/DVD reader. 
umass device) is not activated, though reported as recognized and being 
just booted from it.

The last few lines from the kernel about the device (transcribed by 
hand) are:

Root mount waiting for: usbus5
umass0: <Virtual CDROM> on usbus5
umass0: 8070i (ATAPI) over Bulk-Only; quirks=0
umass0:2:0:-1: attached to scbus2

That is all - there is no cd0 device or similar and sysinstall of course 
cannot install from the CD. Unfortunately, I'm also having trouble 
bringing up the network so I can't install over network either.

Has anyone else seen something like this before? Any suggestions?

This is a BL460 G1 blade server in c7000 chasis.

From everos at gmail.com  Fri Nov 13 19:11:03 2009
From: everos at gmail.com (Ever Last)
Date: Fri Nov 13 19:11:09 2009
Subject: Problem with usb external storage
Message-ID: <ae82a2f30911131043g5b0243c4l88f45d093508055b@mail.gmail.com>

Hi,
firstly: hello everyone, its my first mail here:) I hope my english would be
understoodable enough.
secondly: i have problem with my external storage (hdd) connected
by usb.

The Problem:
I plugged the hdd (in 3'5 chasis with usb connector) into the
usb slot in my server.
As you can see in dmesg (you can find it below) - freebsd has recognized it
properly.
Disk has linux partition but no file system.
I tried to format it and this is what i got:
-bash-2.05b# newfs /dev/da0s1
newfs: wtfs: 512 bytes at sector 390716801: Inappropriate ioctl for device

disklabel:
-bash-2.05b# disklabel /dev/da0s1
disklabel: /dev/da0s1 read: Unknown error: 0

I tried to do fdisk i label this disk by sysinstall tool,
but it wasnt able to write it:
ERROR: Unable to write data to disk da0!

Disk is 100% healthy - i plugged it into my notebook's usb
port (with rescue cd) and i was able to format it, read, write, etc. Then I
reformated it with ntfs and plugged into freebsd again. This time i could
mount it as ntfs but nothing else - writing nor erasing was possible.
Even dd was unable to write enything on it.
So i'm completly run out of ideas. I suspect usb drivers but i dont know how
to check it and repair.
Could you help me?

Software:
FBSD 6.2
kernel options:
# SCSI peripherals
device          scbus
device          da
device          pass
device          ses

# USB support
device          uhci
device          ohci
device          ehci
device          usb
device          ugen
device          uhid
device          umass

Hardware:
uhci0: <Intel 82801EB (ICH5) USB controller USB-A> port 0xdc00-0xdc1f irq 11
at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <Intel 82801EB (ICH5) USB controller USB-A> on uhci0
usb0: USB revision 1.0
[...]

umass0: Super Top USB 2.0  IDE DEVICE, rev 2.00/2.01, addr 2
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <WDC WD20 00JB-00KFA0 \\0000\\0000> Fixed Direct Access SCSI-0 device
da0: 1.000MB/s transfers
da0: 190782MB (390721968 512 byte sectors: 255H 63S/T 24321C)
From meslists at yahoo.fr  Sat Nov 14 18:58:36 2009
From: meslists at yahoo.fr (Dan)
Date: Sat Nov 14 18:58:42 2009
Subject: usb samsung yp-r1 device issue
Message-ID: <638006.72144.qm@web28102.mail.ukl.yahoo.com>

Hi !

In short, this is the issue. Plugging in a Samsung Portable Player, the system _always_ reports ( I marked some lines with '[*]'):
"umass0: <SAMSUNG Electronics.Co.Ltd YP-R1, class 0/0, rev 2.00/2.00, addr 2> on uhub3
[*](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): UNIT ATTENTION asc:29,0
[*](probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred
[*](probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)

da0 at umass-sim0 bus 0 target 0 lun 0
da0: <Samsung YP-R1 0322> Removable Direct Access SCSI-2 device 
da0: 40.000MB/s transfers"

Do the lines marked with [*] represent an usual/accepted/normal/safe behaviour ? Any action must be taken ? The same thing _sometimes_ happens for an external usb cd. Both the devices seem to work fine. 
Here's uname output :

7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May  1 08:49:13 UTC 2009     root@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

Thanks for advices,
dan



      
From alexbestms at wwu.de  Mon Nov 16 02:10:02 2009
From: alexbestms at wwu.de (Alexander Best)
Date: Mon Nov 16 02:10:08 2009
Subject: usb/140590: [bluetooth] [usb] ng_ubt(4) ng_l2cap_process_cmd_rej
	warnings
Message-ID: <200911160202.nAG22oQM035220@www.freebsd.org>


>Number:         140590
>Category:       usb
>Synopsis:       [bluetooth] [usb] ng_ubt(4) ng_l2cap_process_cmd_rej warnings
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 16 02:10:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Alexander Best
>Release:        9.0-CURRENT
>Organization:
>Environment:
FreeBSD otaku 9.0-CURRENT FreeBSD 9.0-CURRENT #7 r199258M: Sat Nov 14 00:05:10 CET 2009     root@otaku:/usr/obj/usr/src/sys/ARUNDEL  i386
>Description:
when receiving data with my usb bluetooth dongle device i'm getting these warnings:

ng_l2cap_process_cmd_rej: ubt0l2cap - unexpected L2CAP_CommandRej command. Requested ident does not exist, ident=2
ng_l2cap_process_cmd_rej: ubt0l2cap - unexpected L2CAP_CommandRej command. Requested ident does not exist, ident=2

when sending data these are the warnings appear:

ng_l2cap_process_cmd_rej: ubt0l2cap - unexpected L2CAP_CommandRej command. Requested ident does not exist, ident=1
ng_l2cap_process_cmd_rej: ubt0l2cap - unexpected L2CAP_CommandRej command. Requested ident does not exist, ident=1
ng_btsocket_rfcomm_receive_dm: Got DM for non-existing dlci=18

this is my device:

ugen3.3: <product 0x0001 vendor 0x0a12> at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x00e0
  bDeviceSubClass = 0x0001
  bDeviceProtocol = 0x0001
  bMaxPacketSize0 = 0x0040
  idVendor = 0x0a12
  idProduct = 0x0001
  bcdDevice = 0x1593
  iManufacturer = 0x0000  <no string>
  iProduct = 0x0000  <no string>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001

i have the following devd.conf entries installed to start bluetooth services upon attach:

attach 100 {
        device-name "ubt[0-9]+";
        action "/etc/rc.d/hcsecd onestart";
        action "/etc/rc.d/sdpd onestart";
        action "/etc/rc.d/bluetooth quietstart $device-name";
        action "/usr/local/bin/obexapp -u arundel -r /var/spool/obex -s -C1";
};

this is the detach entry:

detach 100 {
        device-name "ubt[0-9]+";
        action "/usr/bin/killall obexapp";
        action "/etc/rc.d/bluetooth quietstop $device-name";
        action "/etc/rc.d/sdpd onestop";
        action "/etc/rc.d/hcsecd onestop";
};

cheers.
alex
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From bugmaster at FreeBSD.org  Mon Nov 16 11:07:03 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov 16 11:09:43 2009
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200911161107.nAGB73VH011321@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/140590   usb        [bluetooth] [usb] ng_ubt(4) ng_l2cap_process_cmd_rej w
o usb/140477   usb        [umass] [patch] allow boot-time attachment of daX devi
o usb/140325   usb        Missing/incorrect initialisation and memory leak in li
o usb/140259   usb        libusb-1.0 portability/compatibility nits
o usb/140242   usb        dev/usb/controller/ehci_ix4xx.c shortcomings
o usb/140236   usb        [msdosfs] Labels wiped on external Journaled USB HDD o
o usb/140160   usb        USB ports are no longer "active" after ACPI suspend/re
o usb/139990   usb        [panic] Kernel frequently panics after printing
o usb/139598   usb        [umass] CAM reports "xptioctl: put "device pass" in yo
o usb/139243   usb        [uhci] unplug prolific USB serial -> uhci_abort_xfer: 
o usb/139142   usb        [regression] ehci drivers (NVIDIA nForce4 USB 2.0 cont
o usb/138915   usb        [patch][usb8][usb67] add support for SheevaPlug serial
o usb/138904   usb        [rum] unpluging USB wifi card panics system
f usb/138882   usb        [ohci] [panic] Can't install FreeBSD 7.2 due to ohci p
o usb/138879   usb        [uftdi] [patch] Patch to add support for CTI USB-Mini 
o usb/138798   usb        8.0-BETA4 can't boot from USB flash drive [regression]
o usb/138675   usb        [usb8] [panic] page fault, perhaps in USB
o usb/138659   usb        [usb8][uftdi] driver broken in RELENG_8/CURRENT
o usb/138389   usb        [usb8] [patch] NULL pointer dereference in usb_endpoin
o usb/138175   usb        [usb67] [boot] System cannot boot, when USB reader wit
o usb/138172   usb        Additional dev id for u3g (Option mini PCIe)
o usb/138138   usb        Novatel U760 for u3g (Verizon and Bell Canada)
o usb/138124   usb        [usb8] Axed uaudio functionality in the usbng (alterna
o usb/138119   usb        MultiBay CDROM (propably on USB bus) is not recognized
o usb/137872   usb        slow booting on usb flash drive
f usb/137848   usb        Page fault when using an USB bluetooth adapter
o usb/137806   usb        [ukbd] USB keyboard doesn't work until it's unplugged
o usb/137763   usb        [usb67][ukbd] Logitech wireless keyboard media keys no
o usb/137616   usb        [usb67][usb8][usbdevs] [patch]: usbdevs update: Please
o usb/137377   usb        [usb8] Support for Huawei E180
o usb/137341   usb        [usb8][rum] driver if_rum doesn't work at all and thro
p usb/137226   usb        [usb67][patch] quirk for Philips extern USB disk
o usb/137190   usb        [usb8][patch] inhibit spurious button releases for som
o usb/137189   usb        [usb8][patch] create and use sysctl nodes for HID repo
p usb/137188   usb        [usb8][patch] correctly handle USB report descriptors 
o usb/137129   usb        SteelSeries Ikari USB laser mouse not attaching
p usb/136761   usb        [usbdevs][usb67][patch] Teach usbdevs / u3g(4) about H
o usb/135938   usb        [aue] aue driver only passes traffic in promisc mode
f usb/135857   usb        RTL8187 Wireless Adapter
o usb/135575   usb        [usbdevs] [patch] Add HTC Wizard phone vid/pid informa
o usb/135542   usb        [keyboard] boot loader does not work with a usb keyboa
p usb/135372   usb        [usb67][umass] Quirk report for Teclast TL-C300 usb me
o usb/135348   usb        [umass] USB Drive Hangs with ZFS (JMicron USB2/eSata)
o usb/135206   usb        machine reboots when inserted USB device
o usb/135200   usb        SAMSUNG i740 usb mass: Synchronize cache failed, statu
o usb/135182   usb        UMASS quirk - Olympus FE20 camera
o usb/134950   usb        Lowering DTR for USB-modem via ubsa is not possible
o usb/134633   usb        Add support for WILLCOM03(SHARP smart phone)
o usb/134631   usb        [usbdevs] [patch] WiSPY DBx support requires usb tweak
o usb/134299   usb        Kernel Panic plugging in MF626 USB UMTS Stick u3g
o usb/134193   usb        System freeze on usb MP3 player insertion
o usb/134117   usb        [Patch] Add support for 'Option GlobeTrotter HSDPA Mod
o usb/134085   usb        [umass] Adding usb quirk for Sony USB flash drive
o usb/133989   usb        [newusb] [ukbd] USB keyboard dead at mountroot> prompt
o usb/133712   usb        [ural] [patch] RE: Fixed an issue with ural(4) that wa
o usb/133390   usb        umass crashes system in 7.1 when Olympus D-540 attache
o usb/133296   usb        [rum] driver not working properly in hostap mode
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] [rum] Kernel panic after NOMEM caused by
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
o 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/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/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
o 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
s 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] [panic] enabling usb keyboard and mouse support
o usb/127248   usb        [ucom] panic while uplcom devices attaach and detach
o usb/127222   usb        [ohci] Regression in 7.0 usb storage generic driver
o usb/126884   usb        [ugen] [patch] Bug in buffer handling in ugen.c
o usb/126848   usb        [usb]: USB Keyboard hangs during Installation
o usb/126740   usb        [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be
o usb/126519   usb        [usb] [panic] panic when plugging in an iphone
o kern/126396  usb        [panic] kernel panic after unplug USB Bluetooth device
o usb/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/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 kern/124130  usb        [usb] gmirror fails to start usb devices that were pre
o usb/123969   usb        [usb] Supermicro H8SMi-2 usb problem: port reset faile
o usb/123714   usb        [usb] [panic] Panic when hald-storage-probe runs with 
o usb/123691   usb        usbd(8): usbd hangs
o usb/123690   usb        [usb] [panic] Panic on USB device insertion when usb l
o usb/123611   usb        [usb] BBB reset failed, STALLED from Imation/Mitsumi U
o usb/123509   usb        [umass] continuous reset Samsung SGH-G600 phone
o usb/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        [new driver] [patch] New driver for Sierra Wireless 3G
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] [panic] FreeBSD fails to boot with usb legacy s
o usb/121232   usb        [usb] [panic] USB CardBus card removal causes reboot s
p usb/121184   usb        [uipaq] [patch] add ids from linux ipaq driver (plus a
o usb/121169   usb        [umass] Issues with usb mp3 player
o usb/121045   usb        [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS
o usb/120786   usb        [usb] [panic] Kernel panic when forced umount of a det
o usb/120729   usb        [panic] fault while in kernel mode with connecting USB
o usb/120572   usb        [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/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        [usb67] [usb8] [umass] [patch] Problem with connection
o conf/114013  usb        [patch] WITHOUT_USB allow to compil a lot of USB stuff
o usb/113060   usb        [usb67] [ulpt] [patch] Samsung printer not working in 
o usb/110856   usb        [usb67] [ugen] [patch] interrupt in msgs are truncated
s usb/108344   usb        [usb67] [atausb] [panic] kernel with atausb panics whe
o usb/107827   usb        [usb67] [ohci] [panic] ohci_add_done addr not found
o usb/107388   usb        [usb67] [usb8] [new driver] [patch] add utoppy device 
o usb/107243   usb        [usb67] [cam] [quirk] [patch] Apacer USB Flash Drive q
o usb/106041   usb        [usb67] [usb8] [request] FreeBSD does not recognise Mu
o usb/105361   usb        [usb67] [panic] Kernel panic during unmounting mass st
s usb/103917   usb        [usb67] [uhub] USB driver reports "Addr 0 should never
o usb/103418   usb        [usb67] [usb8] [patch] [request] usbhidctl(8) add abil
o usb/103046   usb        [usb67] [ulpt] [patch] ulpt event driven I/O with sele
o usb/101775   usb        [usb67] [usb8] [libusbhid] [patch] possible error in r
o usb/101761   usb        [usb67] [patch] [request] usb.h: increase maximal size
o usb/100746   usb        [usb67] [ukbd] system does not boot due to USB keyboar
o usb/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/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/83977    usb        [ucom] [panic] ucom1: open bulk out error (addr 2): IN
o usb/83863    usb        [ugen] Communication problem between opensc/openct via
o usb/83756    usb        [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe
o usb/83563    usb        [umass] [panic] Page Fault while detaching Mpman Usb d
o usb/83504    usb        [kernel] [patch] SpeedTouch USB stop working on recent
o usb/82660    usb        [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic
s usb/82569    usb        [umass] [panic] USB mass storage plug/unplug causes sy
o usb/82520    usb        [udbp] [reboot] Reboot when USL101 connected
o usb/82350    usb        [ucom] [panic] null pointer dereference in USB stack
o usb/81621    usb        [ehci] [hang] external hd hangs under load on ehci
o usb/80935    usb        [uvisor] [patch] uvisor.c is not work with CLIE TH55.
o usb/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        [sound] [hang] Use of sound mixer causes system freeze
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] [regression] 5.3-STABLE(2005 1/4) detect USB h
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

314 problems total.

From gavin at FreeBSD.org  Mon Nov 16 22:56:10 2009
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Mon Nov 16 22:57:10 2009
Subject: usb/127549: [umass] [usb67] [patch] Meizu MiniPlayer M6 (SL)
	requires some quirks
Message-ID: <200911162256.nAGMu9jJ026292@freefall.freebsd.org>

Old Synopsis: [umass] [patch] Meizu MiniPlayer M6 (SL) requires some quirks
New Synopsis: [umass] [usb67] [patch] Meizu MiniPlayer M6 (SL) requires some quirks

State-Changed-From-To: suspended->patched
State-Changed-By: gavin
State-Changed-When: Mon Nov 16 22:53:28 UTC 2009
State-Changed-Why: 
This is fixed in 8 and 7, but not merged to 6.  Mark patched in
case somebody wants to do that.

http://www.freebsd.org/cgi/query-pr.cgi?pr=127549
From linimon at FreeBSD.org  Mon Nov 16 23:19:51 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Mon Nov 16 23:20:48 2009
Subject: kern/140614: [uplcom] [patch] adding support for Radio Shack
	Gigware USB to Serial cable (26-949) to uplcom
Message-ID: <200911162319.nAGNJonq043732@freefall.freebsd.org>

Old Synopsis: adding support for Radio Shack Gigware USB to Serial cable (26-949) to uplcom
New Synopsis: [uplcom] [patch] adding support for Radio Shack Gigware USB to Serial cable (26-949) to uplcom

Responsible-Changed-From-To: freebsd-bugs->freebsd-usb
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Nov 16 23:19:21 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=140614
From erleya at gmail.com  Mon Nov 16 23:24:44 2009
From: erleya at gmail.com (Alex Troussov)
Date: Mon Nov 16 23:25:57 2009
Subject: usb printer rejects incoming data
Message-ID: <20091116230741.GA46228@erley.homeip.net>

Hello all,

Recently I upgraded to the latest RELENG_8 and rebuilt world.
Now I'm having strange problems with my USB printer (Samsung CLP 315).
Digging into it these last days, I found that it seems to refuse
incoming data via USB port.
I'm using foo2qpdl filter and it generates a standard QPDL stream for that
printer, the problem occurs when I try to feed that data to the printer.
Here is some details about my environment:

>uname -a
FreeBSD xxxx.yyyy.net 8.0-PRERELEASE FreeBSD 8.0-PRERELEASE #26: Sun
Nov 15 15:44:11 CET 2009 root@xxxx.yyyy.net:/usr/obj/usr/src/sys/ERLEY  i386

>sudo usbconfig
ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen1.1: <UHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen2.1: <UHCI root HUB Intel> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen3.1: <UHCI root HUB Intel> at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen4.1: <EHCI root HUB Intel> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
ugen4.2: <802.11 bg WLAN Ralink> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
ugen0.2: <CanoScan Canon> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen4.3: <CLP-310 Series Samsung Electronics Co., Ltd.> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
ugen1.2: <Protection Station EATON> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON

>sudo ls -l /dev/u* | grep 4.3
lrw-rw-rw-  1 daemon  daemon           9 16 ??? 14:07 /dev/ugen4.3@ -> usb/4.3.0
crw-rw-rw-  1 daemon  daemon      0, 140 16 ??? 14:07 4.3.0
crw-rw-rw-  1 daemon  daemon      0, 142 16 ??? 14:07 4.3.1
crw-rw-rw-  1 daemon  daemon      0, 143 16 ??? 14:07 4.3.2

>sudo cat tiger.qpdl > /dev/usb/4.3.0
cat: stdout: Input/output error

I'm sure this file tiger.qpdl contains the data needed, I created it
from /usr/local/share/ghostscript/8.64/examples/tiger.eps using gs + foo2qpdl
and tested on another PC.

Any ideas?

WBR, Alex

From daichi at ongs.co.jp  Tue Nov 17 02:08:34 2009
From: daichi at ongs.co.jp (Daichi GOTO)
Date: Tue Nov 17 02:08:41 2009
Subject: some quirk issue around uhid operations
Message-ID: <20091117105025.55e8d003.daichi@ongs.co.jp>

Hi USB developers :)

Our company's developer Ozawa-san has found some quirk issue
around uhid device operations.

For example, using uhid0 from processA and using uhid1 from 
processB at the same time, sometimes read(2) operation leads 
handup. In case useing those not at same time, there is no 
hangup. In this week he has been doing test and above issue 
happens all the time.

At last he didn't find does which read(2) or write(2) 
operations have a bug.  If you have some ideas or can resolve
this issue, please help us!

-- 
Daichi GOTO
CEO | ONGS Inc.
81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp
LinkedIn: http://linkedin.com/in/daichigoto
From hselasky at c2i.net  Tue Nov 17 08:14:36 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Nov 17 08:14:43 2009
Subject: usb printer rejects incoming data
In-Reply-To: <20091116230741.GA46228@erley.homeip.net>
References: <20091116230741.GA46228@erley.homeip.net>
Message-ID: <200911170916.04429.hselasky@c2i.net>

On Tuesday 17 November 2009 00:07:41 Alex Troussov wrote:
> Hello all,
>
> Recently I upgraded to the latest RELENG_8 and rebuilt world.
> Now I'm having strange problems with my USB printer (Samsung CLP 315).
> Digging into it these last days, I found that it seems to refuse
> incoming data via USB port.
> I'm using foo2qpdl filter and it generates a standard QPDL stream for that
> printer, the problem occurs when I try to feed that data to the printer.
>
> Here is some details about my environment:
> >uname -a
>
> FreeBSD xxxx.yyyy.net 8.0-PRERELEASE FreeBSD 8.0-PRERELEASE #26: Sun
> Nov 15 15:44:11 CET 2009 root@xxxx.yyyy.net:/usr/obj/usr/src/sys/ERLEY 
> i386
>
> >sudo usbconfig
>
> ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON ugen1.1: <UHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=FULL
> (12Mbps) pwr=ON ugen2.1: <UHCI root HUB Intel> at usbus2, cfg=0 md=HOST
> spd=FULL (12Mbps) pwr=ON ugen3.1: <UHCI root HUB Intel> at usbus3, cfg=0
> md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: <EHCI root HUB Intel> at usbus4,
> cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen4.2: <802.11 bg WLAN Ralink> at
> usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: <CanoScan Canon>
> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.3: <CLP-310 Series
> Samsung Electronics Co., Ltd.> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps)
> pwr=ON ugen1.2: <Protection Station EATON> at usbus1, cfg=0 md=HOST spd=LOW
> (1.5Mbps) pwr=ON
>
> >sudo ls -l /dev/u* | grep 4.3
>
> lrw-rw-rw-  1 daemon  daemon           9 16 ??? 14:07 /dev/ugen4.3@ ->
> usb/4.3.0 crw-rw-rw-  1 daemon  daemon      0, 140 16 ??? 14:07 4.3.0
> crw-rw-rw-  1 daemon  daemon      0, 142 16 ??? 14:07 4.3.1
> crw-rw-rw-  1 daemon  daemon      0, 143 16 ??? 14:07 4.3.2
>
> >sudo cat tiger.qpdl > /dev/usb/4.3.0
>
> cat: stdout: Input/output error
>
> I'm sure this file tiger.qpdl contains the data needed, I created it
> from /usr/local/share/ghostscript/8.64/examples/tiger.eps using gs +
> foo2qpdl and tested on another PC.

Hi,

.0 is the control endpoint. You won't get any data through there :-)

See:

usbconfig -u 4 -a 3 dump_curr_config_desc

for the correct OUT endpoint.

--HPS
From erleya at gmail.com  Tue Nov 17 17:23:13 2009
From: erleya at gmail.com (Alex Troussov)
Date: Tue Nov 17 17:23:20 2009
Subject: usb printer rejects incoming data [SOLVED]
In-Reply-To: <200911170916.04429.hselasky@c2i.net>
References: <20091116230741.GA46228@erley.homeip.net>
	<200911170916.04429.hselasky@c2i.net>
Message-ID: <20091117172310.GA54813@erley.homeip.net>

On Tue, Nov 17, 2009 at 09:16:03AM +0100, Hans Petter Selasky wrote:
> > Recently I upgraded to the latest RELENG_8 and rebuilt world.
> > Now I'm having strange problems with my USB printer (Samsung CLP 315).
> > Digging into it these last days, I found that it seems to refuse
> > incoming data via USB port.
> >
> > >sudo cat tiger.qpdl > /dev/usb/4.3.0
> >
> > cat: stdout: Input/output error
> >
> > I'm sure this file tiger.qpdl contains the data needed, I created it
> > from /usr/local/share/ghostscript/8.64/examples/tiger.eps using gs +
> > foo2qpdl and tested on another PC.
> 
> .0 is the control endpoint. You won't get any data through there :-)
> 
> See:
> 
> usbconfig -u 4 -a 3 dump_curr_config_desc
> 
> for the correct OUT endpoint.

OK, here is what it gives:

>sudo usbconfig -u 4 -a 3 dump_curr_config_desc
ugen4.3: <CLP-310 Series Samsung Electronics Co., Ltd.> at usbus4, cfg=0
md=HOST spd=HIGH (480Mbps) pwr=ON

 Configuration index 0

    bLength = 0x0009 
    bDescriptorType = 0x0002 
    wTotalLength = 0x0020 
    bNumInterfaces = 0x0001 
    bConfigurationValue = 0x0001 
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x00c0 
    bMaxPower = 0x0001 

    Interface 0
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0000 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0002 
      bInterfaceClass = 0x0007 
      bInterfaceSubClass = 0x0001 
      bInterfaceProtocol = 0x0002 
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0002 
        bmAttributes = 0x0002 
        wMaxPacketSize = 0x0200 
        bInterval = 0x000a 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000 

     Endpoint 1
        bLength = 0x0007 
        bDescriptorType = 0x0005 
        bEndpointAddress = 0x0081 
        bmAttributes = 0x0002 
        wMaxPacketSize = 0x0200 
        bInterval = 0x000a 
        bRefresh = 0x0000 
        bSynchAddress = 0x0000

I don't know where to look for the right endpoint here...

But I tried every endpoint - /dev/usb/4.3.0, /dev/usb/4.3.1 and
/dev/usb/4.3.2 - and the last one worked.
So, the problem is solved for me.

Just for my curiosity, where can I read more about USB endpoints?

WBR, Alex
From gjin at ubicom.com  Wed Nov 18 07:46:29 2009
From: gjin at ubicom.com (Guojun Jin)
Date: Wed Nov 18 07:46:48 2009
Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB
	drive
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
Message-ID: <CB2DD11991B27C4F99935E6229450D3203950A1D@STORK.scenix.com>

Did newfs on those partition and made things worsen -- restore completely fails:
(I had experienced another similar problem on an IDE, which works well for 6.4 and 7.2, but 8.0.)
This dirve works fine under FreeBSD 6.4.

Is something new in 8.0 making disk partition schema changed?

g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6
g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6
fopen: Device not configured
cannot create save file ./restoresymtable for symbol table
abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scs
i status == 0x0
(da0:umass-sim0:0:0:0): removing device entry
ugen1.2: <DMI> at usbus1
umass0: <DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2> on usbus1
umass0:  SCSI over Bulk-Only; quirks = 0x0000
umass0:0:0:-1: Attached to scbus0
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <DMI Ultra HDD 1.19> Fixed Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C)
Device da0s3d went missing before all of the data could be written to it; expect
 data loss.

    99  23:19   sysinstall
   100  23:20   newfs /dev/da0s3d
   101  23:20   newfs /dev/da0s3e
   102  23:21   mount /dev/da0s3d /mnt
   103  23:21   cd /mnt
   104  23:21   dump -0f - /home | restore -rf -
   105  23:27   history 15



-----Original Message-----
From: Guojun Jin
Sent: Tue 11/17/2009 11:05 PM
To: freebsd-stable@freebsd.org
Cc: questions@freebsd.org; freebsd-usb@freebsd.org
Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
 
When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time.
Details:

Terminal 1 --
term1# mount /dev/da0s3d  /mnt
term1# cd /mnt ; rm -fr *

when rm starts, go to terminal 2 and do:

term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off.
After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on.

term2# ls /dist   ### this will cause dUSB dirve hanging again -- no avtivity.
Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive
activity will stop again.

Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one
partition, then doing "rm -rf *" without involve the second partition, rm will finish quickly.

Has anyone obseved this behave on 8.0-RC?

-Jin














From gjin at ubicom.com  Wed Nov 18 08:23:25 2009
From: gjin at ubicom.com (Guojun Jin)
Date: Wed Nov 18 08:23:37 2009
Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
Message-ID: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>

When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time.
Details:

Terminal 1 --
term1# mount /dev/da0s3d  /mnt
term1# cd /mnt ; rm -fr *

when rm starts, go to terminal 2 and do:

term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off.
After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on.

term2# ls /dist   ### this will cause dUSB dirve hanging again -- no avtivity.
Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive
activity will stop again.

Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one
partition, then doing "rm -rf *" without involve the second partition, rm will finish quickly.

Has anyone obseved this behave on 8.0-RC?

-Jin













From hselasky at c2i.net  Wed Nov 18 08:40:14 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Nov 18 08:40:22 2009
Subject: usb printer rejects incoming data [SOLVED]
In-Reply-To: <20091117172310.GA54813@erley.homeip.net>
References: <20091116230741.GA46228@erley.homeip.net>
	<200911170916.04429.hselasky@c2i.net>
	<20091117172310.GA54813@erley.homeip.net>
Message-ID: <200911180941.43970.hselasky@c2i.net>

On Tuesday 17 November 2009 18:23:10 Alex Troussov wrote:
> On Tue, Nov 17, 2009 at 09:16:03AM +0100, Hans Petter Selasky wrote:
> > > Recently I upgraded to the latest RELENG_8 and rebuilt world.
> > > Now I'm having strange problems with my USB printer (Samsung CLP 315).
> > > Digging into it these last days, I found that it seems to refuse
> > > incoming data via USB port.
> > >
> > > >sudo cat tiger.qpdl > /dev/usb/4.3.0
> > >
> > > cat: stdout: Input/output error
> > >
> > > I'm sure this file tiger.qpdl contains the data needed, I created it
> > > from /usr/local/share/ghostscript/8.64/examples/tiger.eps using gs +
> > > foo2qpdl and tested on another PC.
> >
> > .0 is the control endpoint. You won't get any data through there :-)
> >
> > See:
> >
> > usbconfig -u 4 -a 3 dump_curr_config_desc
> >
> > for the correct OUT endpoint.
>
> OK, here is what it gives:
> >sudo usbconfig -u 4 -a 3 dump_curr_config_desc
>
> ugen4.3: <CLP-310 Series Samsung Electronics Co., Ltd.> at usbus4, cfg=0
> md=HOST spd=HIGH (480Mbps) pwr=ON
>
>  Configuration index 0
>
>     bLength = 0x0009
>     bDescriptorType = 0x0002
>     wTotalLength = 0x0020
>     bNumInterfaces = 0x0001
>     bConfigurationValue = 0x0001
>     iConfiguration = 0x0000  <no string>
>     bmAttributes = 0x00c0
>     bMaxPower = 0x0001
>
>     Interface 0
>       bLength = 0x0009
>       bDescriptorType = 0x0004
>       bInterfaceNumber = 0x0000
>       bAlternateSetting = 0x0000
>       bNumEndpoints = 0x0002
>       bInterfaceClass = 0x0007
>       bInterfaceSubClass = 0x0001
>       bInterfaceProtocol = 0x0002
>       iInterface = 0x0000  <no string>
>
>      Endpoint 0
>         bLength = 0x0007
>         bDescriptorType = 0x0005
>         bEndpointAddress = 0x0002
>         bmAttributes = 0x0002
>         wMaxPacketSize = 0x0200
>         bInterval = 0x000a
>         bRefresh = 0x0000
>         bSynchAddress = 0x0000
>
>      Endpoint 1
>         bLength = 0x0007
>         bDescriptorType = 0x0005
>         bEndpointAddress = 0x0081
>         bmAttributes = 0x0002
>         wMaxPacketSize = 0x0200
>         bInterval = 0x000a
>         bRefresh = 0x0000
>         bSynchAddress = 0x0000
>
> I don't know where to look for the right endpoint here...
>
> But I tried every endpoint - /dev/usb/4.3.0, /dev/usb/4.3.1 and
> /dev/usb/4.3.2 - and the last one worked.
> So, the problem is solved for me.
>
> Just for my curiosity, where can I read more about USB endpoints?

Try google. I don't have any links at hand.

--HPS

From hselasky at c2i.net  Wed Nov 18 11:12:04 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Nov 18 11:12:16 2009
Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB
	drive
In-Reply-To: <CB2DD11991B27C4F99935E6229450D3203950A1D@STORK.scenix.com>
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A1D@STORK.scenix.com>
Message-ID: <200911181213.34112.hselasky@c2i.net>

Hi,

I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and 
the drive simply dies then it might be the case. Else it is a system issue.

There are quirks for mass storage which you can add to 
sys/dev/usb/storage/umass.c .

--HPS

On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote:
> Did newfs on those partition and made things worsen -- restore completely
> fails: (I had experienced another similar problem on an IDE, which works
> well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4.
>
> Is something new in 8.0 making disk partition schema changed?
>
> g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6
> g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6
> fopen: Device not configured
> cannot create save file ./restoresymtable for symbol table
> abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status ==
> 0xa, scs i status == 0x0
> (da0:umass-sim0:0:0:0): removing device entry
> ugen1.2: <DMI> at usbus1
> umass0: <DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2> on usbus1
> umass0:  SCSI over Bulk-Only; quirks = 0x0000
> umass0:0:0:-1: Attached to scbus0
> da0 at umass-sim0 bus 0 target 0 lun 0
> da0: <DMI Ultra HDD 1.19> Fixed Direct Access SCSI-0 device
> da0: 40.000MB/s transfers
> da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C)
> Device da0s3d went missing before all of the data could be written to it;
> expect data loss.
>
>     99  23:19   sysinstall
>    100  23:20   newfs /dev/da0s3d
>    101  23:20   newfs /dev/da0s3e
>    102  23:21   mount /dev/da0s3d /mnt
>    103  23:21   cd /mnt
>    104  23:21   dump -0f - /home | restore -rf -
>    105  23:27   history 15
>
>
>
> -----Original Message-----
> From: Guojun Jin
> Sent: Tue 11/17/2009 11:05 PM
> To: freebsd-stable@freebsd.org
> Cc: questions@freebsd.org; freebsd-usb@freebsd.org
> Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
>
> When mounting two partitions from a USB dirve, it can cause the drive
> access lock up for a long time. Details:
>
> Terminal 1 --
> term1# mount /dev/da0s3d  /mnt
> term1# cd /mnt ; rm -fr *
>
> when rm starts, go to terminal 2 and do:
>
> term2# mount /dev/da0s3e /dist ### this will hanging for a long time and
> USB hard drive activity light is off. After more than 1-2 minutes, mount
> returns, and the drive activity light is blinking, thus removing is going
> on.
>
> term2# ls /dist   ### this will cause dUSB dirve hanging again -- no
> avtivity. Similarly, ls will finish in a couple of miniutes or longer, the
> rm command continues; but for a while, the drive activity will stop again.
>
> Reboot machine, repeat the above steps, and result will be the same. Reboot
> machine again, and just mount one partition, then doing "rm -rf *" without
> involve the second partition, rm will finish quickly.
>
> Has anyone obseved this behave on 8.0-RC?
>
> -Jin

From 166162 at gmail.com  Wed Nov 18 12:51:11 2009
From: 166162 at gmail.com (Travelling Particle)
Date: Wed Nov 18 12:51:17 2009
Subject: [keyboard] ukbd stops working after filesystems mount at boot time
Message-ID: <da6b214d0911180425r2b720333r87fe2fb79e3e13e1@mail.gmail.com>

Hello,

I am not sure if the problem is with USB, because the same hardware works
fine with LiveCD. I will seek help here first, please feel free to redirect
me to a better place for advice.

The system is 8.0-RC3.

I am booting off USB stick because I have to attach root partition on HDD
with GELI. It all works fine, I am able to enter passphrase on the keyboard
(there's only ukbd keyboard in the kernel at this moment, but I had tried
with atkbd as well; I have also experimented with or without TEKEN with no
difference). After root partition is mounted, system mounts other geli
partitions on the same hard disk. It is right after the filesystems were
mounted that the problem starts. The output on console at that moment starts
to be interleaved with new lines symbols. After late boot stage completes, I
see login prompt on console, but system acts *as if* I had just pressed
Enter and presents login prompt again and again. The keyboard itself appears
to be dead. If I choose to boot single-mode, behavior is the same -- I see
multiple shell prompts as if I were hitting Enter repeatedly. I had been
trying various configurations in the kernel for over 5 days now, and still
couldn't make the console work on the system (I can login via network
though).

The hardware is Nvidea ION-based Acer nettop. It does not come with PS/2
keyboard connector and I cannot test it with any keyboard but USB. The
keyboard itself I am using is Acer's standard one, and it works fine with
LiveCD. I wonder if GELI might mess the things up, but the geli attachment
process goes well, and all filesystems are attached just fine.

Thanks a lot for help,
Vassiliy
From avg at icyb.net.ua  Wed Nov 18 13:49:24 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Wed Nov 18 13:49:32 2009
Subject: [keyboard] ukbd stops working after filesystems mount at boot
 time
In-Reply-To: <da6b214d0911180425r2b720333r87fe2fb79e3e13e1@mail.gmail.com>
References: <da6b214d0911180425r2b720333r87fe2fb79e3e13e1@mail.gmail.com>
Message-ID: <4B03FB5E.5070308@icyb.net.ua>

on 18/11/2009 14:25 Travelling Particle said the following:
> Hello,
> 
> I am not sure if the problem is with USB, because the same hardware works
> fine with LiveCD. I will seek help here first, please feel free to redirect
> me to a better place for advice.
> 
> The system is 8.0-RC3.
> 
> I am booting off USB stick because I have to attach root partition on HDD
> with GELI. It all works fine, I am able to enter passphrase on the keyboard
> (there's only ukbd keyboard in the kernel at this moment, but I had tried
> with atkbd as well; I have also experimented with or without TEKEN with no
> difference). After root partition is mounted, system mounts other geli
> partitions on the same hard disk. It is right after the filesystems were
> mounted that the problem starts. The output on console at that moment starts
> to be interleaved with new lines symbols. After late boot stage completes, I
> see login prompt on console, but system acts *as if* I had just pressed
> Enter and presents login prompt again and again. The keyboard itself appears
> to be dead. If I choose to boot single-mode, behavior is the same -- I see
> multiple shell prompts as if I were hitting Enter repeatedly. I had been
> trying various configurations in the kernel for over 5 days now, and still
> couldn't make the console work on the system (I can login via network
> though).
> 
> The hardware is Nvidea ION-based Acer nettop. It does not come with PS/2
> keyboard connector and I cannot test it with any keyboard but USB. The
> keyboard itself I am using is Acer's standard one, and it works fine with
> LiveCD. I wonder if GELI might mess the things up, but the geli attachment
> process goes well, and all filesystems are attached just fine.

LiveCD is also 8.0-RC3?


-- 
Andriy Gapon
From gjin at ubicom.com  Wed Nov 18 20:11:32 2009
From: gjin at ubicom.com (Guojun Jin)
Date: Wed Nov 18 20:11:50 2009
Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB
	drive
In-Reply-To: <200911181213.34112.hselasky@c2i.net>
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A1D@STORK.scenix.com>
	<200911181213.34112.hselasky@c2i.net>
Message-ID: <CB2DD11991B27C4F99935E6229450D3204D531C9@STORK.scenix.com>

It looks like a system issue since it also happens to the SATA drive. 
The USB drive seems having more difficulty. I will back up rest
partitions,
Then redo the slice and partition to see if problem goes away.
If so, then 8.0-R has a backward compatibility issue on the partition
table or format to older FreeBSD release.

-----Original Message-----
From: Hans Petter Selasky [mailto:hselasky@c2i.net] 
Sent: Wednesday, November 18, 2009 3:14 AM
To: freebsd-usb@freebsd.org
Cc: Guojun Jin; freebsd-stable@freebsd.org; questions@freebsd.org
Subject: Re: 8.0-RC3 USB lock up on mounting two partitions from one USB
drive

Hi,

I'm not sure if this is an USB issue or not. If you get READ/WRITE
errors and 
the drive simply dies then it might be the case. Else it is a system
issue.

There are quirks for mass storage which you can add to 
sys/dev/usb/storage/umass.c .

--HPS

On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote:
> Did newfs on those partition and made things worsen -- restore
completely
> fails: (I had experienced another similar problem on an IDE, which
works
> well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD
6.4.
>
> Is something new in 8.0 making disk partition schema changed?
>
> g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6
> g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6
> fopen: Device not configured
> cannot create save file ./restoresymtable for symbol table
> abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status
==
> 0xa, scs i status == 0x0
> (da0:umass-sim0:0:0:0): removing device entry
> ugen1.2: <DMI> at usbus1
> umass0: <DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2> on usbus1
> umass0:  SCSI over Bulk-Only; quirks = 0x0000
> umass0:0:0:-1: Attached to scbus0
> da0 at umass-sim0 bus 0 target 0 lun 0
> da0: <DMI Ultra HDD 1.19> Fixed Direct Access SCSI-0 device
> da0: 40.000MB/s transfers
> da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C)
> Device da0s3d went missing before all of the data could be written to
it;
> expect data loss.
>
>     99  23:19   sysinstall
>    100  23:20   newfs /dev/da0s3d
>    101  23:20   newfs /dev/da0s3e
>    102  23:21   mount /dev/da0s3d /mnt
>    103  23:21   cd /mnt
>    104  23:21   dump -0f - /home | restore -rf -
>    105  23:27   history 15
>
>
>
> -----Original Message-----
> From: Guojun Jin
> Sent: Tue 11/17/2009 11:05 PM
> To: freebsd-stable@freebsd.org
> Cc: questions@freebsd.org; freebsd-usb@freebsd.org
> Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB
drive
>
> When mounting two partitions from a USB dirve, it can cause the drive
> access lock up for a long time. Details:
>
> Terminal 1 --
> term1# mount /dev/da0s3d  /mnt
> term1# cd /mnt ; rm -fr *
>
> when rm starts, go to terminal 2 and do:
>
> term2# mount /dev/da0s3e /dist ### this will hanging for a long time
and
> USB hard drive activity light is off. After more than 1-2 minutes,
mount
> returns, and the drive activity light is blinking, thus removing is
going
> on.
>
> term2# ls /dist   ### this will cause dUSB dirve hanging again -- no
> avtivity. Similarly, ls will finish in a couple of miniutes or longer,
the
> rm command continues; but for a while, the drive activity will stop
again.
>
> Reboot machine, repeat the above steps, and result will be the same.
Reboot
> machine again, and just mount one partition, then doing "rm -rf *"
without
> involve the second partition, rm will finish quickly.
>
> Has anyone obseved this behave on 8.0-RC?
>
> -Jin

From torfinn.ingolfsen at broadpark.no  Wed Nov 18 21:32:50 2009
From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen)
Date: Wed Nov 18 21:32:58 2009
Subject: FreeBSD - support for DisplayLink devices?
Message-ID: <20091118223223.8223a2c6.torfinn.ingolfsen@broadpark.no>

Hi,
Do we have support for DisplayLink devices in FreeBSD?
Like libdlo[2,3] or udl[4]?

Today I got a UM-70[5] monitor made by Lilliput, this is what /var/log/messages
says when I connectd it to my 7.2-stable machine:
Nov 18 22:18:13 kg-v2 root: Unknown USB device: vendor 0x17e9 product 0x02a9 bus uhub1
Nov 18 22:18:13 kg-v2 kernel: ugen2: <DisplayLink LILLIPUT USB Monitor, class 0/0, rev 2.00/1.23, addr 4> on uhub1

Output from 'usbdevs -v':
 port 5 addr 4: high speed, power 500 mA, config 1, LILLIPUT USB Monitor(0x02a9), DisplayLink(0x17e9), rev 1.23

(No, I can't stop buying gadgets)

Refernces:
1) http://en.wikipedia.org/wiki/Displaylink
2) http://displaylink.org/
3) http://libdlo.freedesktop.org/
4) http://libdlo.freedesktop.org/wiki/udl
5) http://www.lilliputlcd.com/lilliput-um70-7-usb-monitor-only-one-cable-does-all_p592.html
-- 
Regards,
Torfinn Ingolfsen

From torfinn.ingolfsen at broadpark.no  Wed Nov 18 21:44:06 2009
From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen)
Date: Wed Nov 18 21:44:11 2009
Subject: FreeBSD - support for DisplayLink devices?
In-Reply-To: <20091118223223.8223a2c6.torfinn.ingolfsen@broadpark.no>
References: <20091118223223.8223a2c6.torfinn.ingolfsen@broadpark.no>
Message-ID: <20091118224404.da498629.torfinn.ingolfsen@broadpark.no>

On Wed, 18 Nov 2009 22:32:23 +0100
Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no> wrote:

> Today I got a UM-70[5] monitor made by Lilliput, this is
> what /var/log/messages says when I connectd it to my 7.2-stable
> machine: 

Oh, I forgot to tell the age of this -stable:
tingo@kg-v2$ uname -a
FreeBSD kg-v2.kg4.no 7.2-STABLE FreeBSD 7.2-STABLE #1: Fri Oct 30
19:46:58 CET 2009     root@kg-v2.kg4.no:/usr/obj/usr/src/sys/V2  amd64
-- 
Regards,
Torfinn Ingolfsen

From hselasky at c2i.net  Wed Nov 18 21:45:51 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Nov 18 21:45:57 2009
Subject: FreeBSD - support for DisplayLink devices?
In-Reply-To: <20091118224404.da498629.torfinn.ingolfsen@broadpark.no>
References: <20091118223223.8223a2c6.torfinn.ingolfsen@broadpark.no>
	<20091118224404.da498629.torfinn.ingolfsen@broadpark.no>
Message-ID: <200911182247.21035.hselasky@c2i.net>

On Wednesday 18 November 2009 22:44:04 Torfinn Ingolfsen wrote:
> On Wed, 18 Nov 2009 22:32:23 +0100
>
> Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no> wrote:
> > Today I got a UM-70[5] monitor made by Lilliput, this is
> > what /var/log/messages says when I connectd it to my 7.2-stable
> > machine:
>
> Oh, I forgot to tell the age of this -stable:
> tingo@kg-v2$ uname -a
> FreeBSD kg-v2.kg4.no 7.2-STABLE FreeBSD 7.2-STABLE #1: Fri Oct 30
> 19:46:58 CET 2009     root@kg-v2.kg4.no:/usr/obj/usr/src/sys/V2  amd64

Is there are userland driver using libusb for your device?

--HPS
From torfinn.ingolfsen at broadpark.no  Wed Nov 18 22:04:39 2009
From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen)
Date: Wed Nov 18 22:04:47 2009
Subject: FreeBSD - support for DisplayLink devices?
In-Reply-To: <200911182247.21035.hselasky@c2i.net>
References: <20091118223223.8223a2c6.torfinn.ingolfsen@broadpark.no>
	<20091118224404.da498629.torfinn.ingolfsen@broadpark.no>
	<200911182247.21035.hselasky@c2i.net>
Message-ID: <20091118230431.4191fb1c.torfinn.ingolfsen@broadpark.no>

On Wed, 18 Nov 2009 22:47:19 +0100
Hans Petter Selasky <hselasky@c2i.net> wrote:

> Is there are userland driver using libusb for your device?

I don't know, really. I haven't finished googling yet. :-)

So far I've got this:
http://libdlo.freedesktop.org/wiki/
http://mulchman.org/blog/?tag=displaylink
-- 
Rgds,
Torfinn Ingolfsen

From thompsa at FreeBSD.org  Wed Nov 18 22:09:02 2009
From: thompsa at FreeBSD.org (Andrew Thompson)
Date: Wed Nov 18 22:09:08 2009
Subject: FreeBSD - support for DisplayLink devices?
In-Reply-To: <200911182247.21035.hselasky@c2i.net>
References: <20091118223223.8223a2c6.torfinn.ingolfsen@broadpark.no>
	<20091118224404.da498629.torfinn.ingolfsen@broadpark.no>
	<200911182247.21035.hselasky@c2i.net>
Message-ID: <20091118220855.GA91753@citylink.fud.org.nz>

On Wed, Nov 18, 2009 at 10:47:19PM +0100, Hans Petter Selasky wrote:
> On Wednesday 18 November 2009 22:44:04 Torfinn Ingolfsen wrote:
> > On Wed, 18 Nov 2009 22:32:23 +0100
> >
> > Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no> wrote:
> > > Today I got a UM-70[5] monitor made by Lilliput, this is
> > > what /var/log/messages says when I connectd it to my 7.2-stable
> > > machine:
> >
> > Oh, I forgot to tell the age of this -stable:
> > tingo@kg-v2$ uname -a
> > FreeBSD kg-v2.kg4.no 7.2-STABLE FreeBSD 7.2-STABLE #1: Fri Oct 30
> > 19:46:58 CET 2009     root@kg-v2.kg4.no:/usr/obj/usr/src/sys/V2  amd64
> 
> Is there are userland driver using libusb for your device?


libdlo mentioned in the original email is a  userland driver using
libusb. It should just work.

Note for FreeBSD 7 and below you will need to install the devel/libusb
port.


Andrew
From 166162 at gmail.com  Thu Nov 19 14:22:08 2009
From: 166162 at gmail.com (Travelling Particle)
Date: Thu Nov 19 14:22:15 2009
Subject: [keyboard] ukbd stops working after filesystems mount at boot time
In-Reply-To: <da6b214d0911180815u63532a8iea91e785df2accf9@mail.gmail.com>
References: <da6b214d0911180425r2b720333r87fe2fb79e3e13e1@mail.gmail.com>
	<4B03FB5E.5070308@icyb.net.ua>
	<da6b214d0911180815u63532a8iea91e785df2accf9@mail.gmail.com>
Message-ID: <da6b214d0911190622r67542c69w10ba1432556f069a@mail.gmail.com>

Thanks for your interest!

LiveCD is also 8.0-RC3?
>

Yes, and the kernel is freshly built from the very same sources (and no, it
did not work when i booted GENERIC off the USB card + mounted geli
partitions, symptoms were the same).

Vassiliy
From sarumont at sigil.org  Fri Nov 20 05:20:29 2009
From: sarumont at sigil.org (Richard Kolkovich)
Date: Fri Nov 20 05:20:35 2009
Subject: uaudio recording problem
Message-ID: <20091120052059.GE36142@magus.portal.sigil.org>

I'm trying to get my Logitech Quickcam microphone working.  When I try to record, I get nothing but
the following in dmesg:

pcm5: chn_read(): pcm5:virtual:dsp5.vr0: record interrupt timeout, channel dead

Here's dmesg after adding/kldloading:

ugen3.9: <vendor 0x046d> at usbus3
uaudio0: <vendor 0x046d product 0x0990, class 239/2, rev 2.00/0.08, addr 9> on usbus3
uaudio0: No playback!
uaudio0: Record: 16000 Hz, 1 ch, 16-bit S-LE PCM format
uaudio0: No midi sequencer
pcm5: <USB audio> on uaudio0

Running 8.0-RC1 on amd64.  This also occurs on my laptop running 8.0-BETA3 on i386.  Any clues?

Thanks,

-- 

Richard Kolkovich
sarumont@sigil.org
PGP Key: 0x9E54EF59 (http://pgp.mit.edu)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20091120/cd416d86/attachment.pgp
From remko at FreeBSD.org  Fri Nov 20 06:56:40 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Fri Nov 20 06:56:46 2009
Subject: kern/140714: system freeze when disconect my flash usb
Message-ID: <200911200656.nAK6ueDJ088676@freefall.freebsd.org>

Synopsis: system freeze when disconect my flash usb

Responsible-Changed-From-To: freebsd-bugs->freebsd-usb
Responsible-Changed-By: remko
Responsible-Changed-When: Fri Nov 20 06:55:49 UTC 2009
Responsible-Changed-Why: 
Reassign to USB.

Submitter: please provide more information on your system, like
a verbose boot, pciconf -vl and any possible information that
HPS might need to get this going. Your information is -very-
limited


http://www.freebsd.org/cgi/query-pr.cgi?pr=140714
From remko at FreeBSD.org  Fri Nov 20 06:56:48 2009
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Fri Nov 20 06:56:56 2009
Subject: kern/140714: system freeze when disconect my flash usb
Message-ID: <200911200656.nAK6umAX088722@freefall.freebsd.org>

Synopsis: system freeze when disconect my flash usb

State-Changed-From-To: open->feedback
State-Changed-By: remko
State-Changed-When: Fri Nov 20 06:56:42 UTC 2009
State-Changed-Why: 
Submitter: please provide more information on your system, like
a verbose boot, pciconf -vl and any possible information that
HPS might need to get this going. Your information is -very-
limited.


http://www.freebsd.org/cgi/query-pr.cgi?pr=140714
From hselasky at c2i.net  Fri Nov 20 07:57:35 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Fri Nov 20 07:57:42 2009
Subject: uaudio recording problem
In-Reply-To: <20091120052059.GE36142@magus.portal.sigil.org>
References: <20091120052059.GE36142@magus.portal.sigil.org>
Message-ID: <200911200859.05532.hselasky@c2i.net>

On Friday 20 November 2009 06:21:01 Richard Kolkovich wrote:
> I'm trying to get my Logitech Quickcam microphone working.  When I try to
> record, I get nothing but the following in dmesg:
>
> pcm5: chn_read(): pcm5:virtual:dsp5.vr0: record interrupt timeout, channel
> dead
>
> Here's dmesg after adding/kldloading:
>
> ugen3.9: <vendor 0x046d> at usbus3
> uaudio0: <vendor 0x046d product 0x0990, class 239/2, rev 2.00/0.08, addr 9>
> on usbus3 uaudio0: No playback!
> uaudio0: Record: 16000 Hz, 1 ch, 16-bit S-LE PCM format
> uaudio0: No midi sequencer
> pcm5: <USB audio> on uaudio0
>
> Running 8.0-RC1 on amd64.  This also occurs on my laptop running 8.0-BETA3
> on i386.  Any clues?

Hi,

This issue has been fixed in USB P4, but the changes have not been committed 
to FreeBSD yet.

--HPS

From gem at parallels.com  Fri Nov 20 08:37:01 2009
From: gem at parallels.com (Maxim Giryaev)
Date: Fri Nov 20 08:37:12 2009
Subject: [madwimax] madwimax-0.1.1 patch for FreeBSD 8 (very buggy)
Message-ID: <4B064F48.50506@parallels.com>

I create similar patch, you can see it here: 
http://code.google.com/p/madwimax/issues/detail?id=39
Periodical crashes in libusb triggered by sigchild handler in madwimax.
I check to way to fix it:
1. remove sigchild handler and call wait3() in scan_loop()
2. check for NULL result of  libusb20_tr_get_priv_sc1() inside  lubusb.

Second way fixes crashes but periodically  libusb_submit_trasfer() 
returns error 99.

There are no disconnects from Internet on my router during last week.

-- 

Maxim Giryaev

From 166162 at gmail.com  Fri Nov 20 09:06:59 2009
From: 166162 at gmail.com (Travelling Particle)
Date: Fri Nov 20 09:07:05 2009
Subject: [keyboard] ukbd stops working after filesystems mount at boot 
	time
In-Reply-To: <4B03FB5E.5070308@icyb.net.ua>
References: <da6b214d0911180425r2b720333r87fe2fb79e3e13e1@mail.gmail.com>
	<4B03FB5E.5070308@icyb.net.ua>
Message-ID: <da6b214d0911200106h128ffdb4waf2d6732087ebef4@mail.gmail.com>

New symptom, as Greg House would say. It appears that keyboard is not as
dead as it looks. If I do shutdown -h, the keyboard suddenly becomes usable:
I can hit any key to reboot. However, between the start of the late boot
stage and the end of halt the system behaves exactly as if somebody pressed
Enter and stick some gum to it to stay that way.

> I am booting off USB stick because I have to attach root partition on HDD
> > with GELI. It all works fine, I am able to enter passphrase on the
> keyboard
> > (there's only ukbd keyboard in the kernel at this moment, but I had tried
> > with atkbd as well; I have also experimented with or without TEKEN with
> no
> > difference). After root partition is mounted, system mounts other geli
> > partitions on the same hard disk. It is right after the filesystems were
> > mounted that the problem starts. The output on console at that moment
> starts
> > to be interleaved with new lines symbols. After late boot stage
> completes, I
> > see login prompt on console, but system acts *as if* I had just pressed
> > Enter and presents login prompt again and again. The keyboard itself
> appears
> > to be dead. If I choose to boot single-mode, behavior is the same -- I
> see
> > multiple shell prompts as if I were hitting Enter repeatedly. I had been
> > trying various configurations in the kernel for over 5 days now, and
> still
> > couldn't make the console work on the system (I can login via network
> > though).
>
From hselasky at c2i.net  Fri Nov 20 11:22:36 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Fri Nov 20 11:23:09 2009
Subject: [keyboard] ukbd stops working after filesystems mount at boot
	time
In-Reply-To: <da6b214d0911200106h128ffdb4waf2d6732087ebef4@mail.gmail.com>
References: <da6b214d0911180425r2b720333r87fe2fb79e3e13e1@mail.gmail.com>
	<4B03FB5E.5070308@icyb.net.ua>
	<da6b214d0911200106h128ffdb4waf2d6732087ebef4@mail.gmail.com>
Message-ID: <200911201224.08313.hselasky@c2i.net>

On Friday 20 November 2009 10:06:56 Travelling Particle wrote:
> New symptom, as Greg House would say. It appears that keyboard is not as
> dead as it looks. If I do shutdown -h, the keyboard suddenly becomes
> usable: I can hit any key to reboot. However, between the start of the late
> boot stage and the end of halt the system behaves exactly as if somebody
> pressed Enter and stick some gum to it to stay that way.
>
> > I am booting off USB stick because I have to attach root partition on HDD
> >
> > > with GELI. It all works fine, I am able to enter passphrase on the
> >
> > keyboard
> >
> > > (there's only ukbd keyboard in the kernel at this moment, but I had
> > > tried with atkbd as well; I have also experimented with or without
> > > TEKEN with
> >
> > no
> >
> > > difference). After root partition is mounted, system mounts other geli
> > > partitions on the same hard disk. It is right after the filesystems
> > > were mounted that the problem starts. The output on console at that
> > > moment
> >
> > starts
> >
> > > to be interleaved with new lines symbols. After late boot stage
> >
> > completes, I
> >
> > > see login prompt on console, but system acts *as if* I had just pressed
> > > Enter and presents login prompt again and again. The keyboard itself
> >
> > appears
> >
> > > to be dead. If I choose to boot single-mode, behavior is the same -- I
> >
> > see
> >
> > > multiple shell prompts as if I were hitting Enter repeatedly. I had
> > > been trying various configurations in the kernel for over 5 days now,
> > > and
> >
> > still
> >
> > > couldn't make the console work on the system (I can login via network
> > > though).

There was a recent EHCI interrupt patch. I'm not sure if it is committed to 9-
current yet.

--HPS

From sasha.devel at gmail.com  Fri Nov 20 15:41:14 2009
From: sasha.devel at gmail.com (Alexander Samarin)
Date: Fri Nov 20 15:41:21 2009
Subject: [madwimax] madwimax-0.1.1 patch for FreeBSD 8 (very buggy)
In-Reply-To: <4B064F48.50506@parallels.com>
References: <4B064F48.50506@parallels.com>
Message-ID: <7dcca81d0911200741q2eb22c20ge2718be32dff0045@mail.gmail.com>

Maxim Giryaev ?????:
> I create similar patch, you can see it here: http://code.google.com/p/madwimax/issues/detail?id=39
> Periodical crashes in libusb triggered by sigchild handler in madwimax.
> I check to way to fix it:
> 1. remove sigchild handler and call wait3() in scan_loop()
> 2. check for NULL result of  libusb20_tr_get_priv_sc1() inside  lubusb.
>
> Second way fixes crashes but periodically  libusb_submit_trasfer() returns error 99.
>
> There are no disconnects from Internet on my router during last week.
>

sighandler_wait_child does not work with any of libusb functions and
structures, so I can't understand how it can crash.. And libusb
protected inside by mutex.



PS: To destroy interface on exit:

-int tap_close(int fd, char *dev) { return close(fd); }
+int tap_close(int fd, char *dev) {
+    int res = close(fd);
+
+#if defined(__FreeBSD__)
+    // We need to destroy tun/tap interface like `ifconfig tunN destroy`
+    struct ifreq ifr;
+
+    memset(&ifr, 0, sizeof(ifr));
+    strncpy(ifr.ifr_name, dev, IFNAMSIZ);
+
+    if ((fd = socket(PF_INET, SOCK_DGRAM, 0)) < 0) {
+        res = fd;
+        perror("socket");
+    } else {
+        if ((res = ioctl(fd, SIOCIFDESTROY, &ifr)) < 0) {
+            perror("ioctl(SIOCIFDESTROY)");
+        }
+        close(fd);
+    }
+#endif
+    return res;
+}

-- 
Best regards,  Alexander Samarin
    mailto:sasha at enikasoft.ru
    https://www.fsora.ru (waits for FreeBSD 8.0-RELEASE)
From sarumont at sigil.org  Fri Nov 20 18:36:56 2009
From: sarumont at sigil.org (Richard Kolkovich)
Date: Fri Nov 20 18:37:03 2009
Subject: uaudio recording problem
In-Reply-To: <200911200859.05532.hselasky@c2i.net>
References: <20091120052059.GE36142@magus.portal.sigil.org>
	<200911200859.05532.hselasky@c2i.net>
Message-ID: <20091120183738.GF36142@magus.portal.sigil.org>

On Fri, Nov 20, 2009 at 08:59:04AM +0100, Hans Petter Selasky wrote:
> Hi,
> 
> This issue has been fixed in USB P4, but the changes have not been committed 
> to FreeBSD yet.
> 
> --HPS

Thanks!

In case anyone else runs into this before the fix is MFC'd, I csup'd src-sys from HEAD and copied
everything from sys/dev/usb/* and sys/dev/sound/usb/* into my source tree, rebuild my kernel and
rebooted to resolve.

-- 

Richard Kolkovich
sarumont@sigil.org
PGP Key: 0x9E54EF59 (http://pgp.mit.edu)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20091120/4965967a/attachment.pgp
From torfinn.ingolfsen at broadpark.no  Fri Nov 20 23:03:30 2009
From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen)
Date: Fri Nov 20 23:03:36 2009
Subject: FreeBSD - support for DisplayLink devices?
In-Reply-To: <20091118220855.GA91753@citylink.fud.org.nz>
References: <20091118223223.8223a2c6.torfinn.ingolfsen@broadpark.no>
	<20091118224404.da498629.torfinn.ingolfsen@broadpark.no>
	<200911182247.21035.hselasky@c2i.net>
	<20091118220855.GA91753@citylink.fud.org.nz>
Message-ID: <20091121000308.89b83d5e.torfinn.ingolfsen@broadpark.no>

On Thu, 19 Nov 2009 11:08:55 +1300
Andrew Thompson <thompsa@FreeBSD.org> wrote:

> libdlo mentioned in the original email is a  userland driver using
> libusb. It should just work.

I've tried with just './configure' and
./configure --includedir=/usr/local/include
./configure --includedir=/usr/local/include --libdir=/usr/local/lib

but all bombs out with this:
checking for usb_open in -lusb... no
checking for usb_get_driver_np... no
configure: error: Can't find libusb. On ubuntu, try sudo apt-get install libusb-dev

> Note for FreeBSD 7 and below you will need to install the devel/libusb
> port.

libusb in ports is currently at version 0.1.12_4, I don't know if that
affects anything, but the libdlo page says  "libusb (0.13)".
-- 
Regards,
Torfinn Ingolfsen

From 166162 at gmail.com  Sat Nov 21 18:12:47 2009
From: 166162 at gmail.com (Travelling Particle)
Date: Sat Nov 21 18:12:53 2009
Subject: [keyboard] ukbd stops working after filesystems mount at boot 
	time
In-Reply-To: <200911201224.08313.hselasky@c2i.net>
References: <da6b214d0911180425r2b720333r87fe2fb79e3e13e1@mail.gmail.com>
	<4B03FB5E.5070308@icyb.net.ua>
	<da6b214d0911200106h128ffdb4waf2d6732087ebef4@mail.gmail.com>
	<200911201224.08313.hselasky@c2i.net>
Message-ID: <da6b214d0911211012he5b2bb7v701596976d2bd0ea@mail.gmail.com>

On Fri, Nov 20, 2009 at 2:24 PM, Hans Petter Selasky <hselasky@c2i.net>wrote:


There was a recent EHCI interrupt patch. I'm not sure if it is committed to
> 9-
> current yet.
>

Do you mean there was a patch that might have caused this problem, or the
patch fixing this problem? Also, I'm on 8-RC3, not 9-CURRENT

Vassiliy
From hselasky at c2i.net  Sat Nov 21 21:58:48 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Nov 21 21:58:55 2009
Subject: [keyboard] ukbd stops working after filesystems mount at boot
	time
In-Reply-To: <da6b214d0911211012he5b2bb7v701596976d2bd0ea@mail.gmail.com>
References: <da6b214d0911180425r2b720333r87fe2fb79e3e13e1@mail.gmail.com>
	<200911201224.08313.hselasky@c2i.net>
	<da6b214d0911211012he5b2bb7v701596976d2bd0ea@mail.gmail.com>
Message-ID: <200911212300.20154.hselasky@c2i.net>

On Saturday 21 November 2009 19:12:45 Travelling Particle wrote:
> On Fri, Nov 20, 2009 at 2:24 PM, Hans Petter Selasky
> <hselasky@c2i.net>wrote:
>
>
> There was a recent EHCI interrupt patch. I'm not sure if it is committed to
>
> > 9-
> > current yet.
>
> Do you mean there was a patch that might have caused this problem, or the
> patch fixing this problem? Also, I'm on 8-RC3, not 9-CURRENT
>

I mean fixing.

--HPS
From gjin at ubicom.com  Sun Nov 22 03:46:25 2009
From: gjin at ubicom.com (Guojun Jin)
Date: Sun Nov 22 03:46:45 2009
Subject: 8.0-RC USB problem -- how to recover a damaged USB stick
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A1D@STORK.scenix.com>
	<200911181213.34112.hselasky@c2i.net>
Message-ID: <CB2DD11991B27C4F99935E6229450D3203950A23@STORK.scenix.com>

It seems this is more serious problem in 8.0, and I hope it could be resolved before a formal release. I can help to diagnose this if people need more information (this is destructive).

I have picked a USB stick (DataTraveler 2GB), that has two partitions s0 for DOS and s1 for FreeBSD.
Both USB hard drive and the USB stick have worked under FreeBSD 6.2, 6.3, 6.4 and 7.2 for a few years without any problem.

Plugged USB stick in 8.0-RC and mounted it on /mnt; then
untar a file, tarred one day ago from FreeBSD 6.3 machine onto stick,to a IDE drive then tar it
back to the USB stick.
During tar writting from IDE to USB stick, did "ls /mnt", and "tar" paused and "ls" hangs.
A couple of minutes later, ls comes back, but tar still pauses.

Hit ^C on tar process around 14:30, it took another minutes to stop the process. Tried tar again,
and system disallowed to write on  the USB stick. "ls" shows all file still there (probably cached inods).

Went out for a few hours, and came back found /var/log/message are flooded with following message:
-rw-r--r--  1 root  wheel  167181 Nov 21 19:02 messages
-rw-r--r--  1 root  wheel    7390 Nov 21 18:00 messages.0.bz2
-rw-r--r--  1 root  wheel    7509 Nov 21 17:00 messages.1.bz2
-rw-r--r--  1 root  wheel    9365 Nov 21 16:00 messages.2.bz2
-rw-r--r--  1 root  wheel   20598 Nov 21 15:00 messages.3.bz2

Nov 21 18:00:00 wolf newsyslog[2635]: logfile turned over due to size>384K
Nov 21 18:00:27 wolf kernel: g_vfs_done():da0s2[WRITE(offset=625688576, length=1
31072)]error = 5
Nov 21 18:00:27 wolf kernel: g_vfs_done():da0s2[WRITE(offset=625819648, length=1
31072)]error = 5
.....
Nov 21 18:19:03 wolf kernel: g_vfs_done():da0s2[WRITE(offset=524451840, length=1
6384)]error = 5
Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=5586944, length=204
8)]error = 5
Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=65536, length=2048)
]error = 5
Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=114688, length=1638
4)]error = 5
Nov 21 18:20:05 wolf kernel: g_vfs_done():da0s2[WRITE(offset=349700096, length=1

and has to reboot the system, and reboot was not able to umount everything (boot up message):

Nov 21 18:24:03 wolf kernel: da0: <Kingston DataTraveler 2.0 1.00> Removable Dir
ect Access SCSI-2 device
Nov 21 18:24:03 wolf kernel: da0: 40.000MB/s transfers
Nov 21 18:24:03 wolf kernel: da0: 1947MB (3987456 512 byte sectors: 255H 63S/T 2
48C)
Nov 21 18:24:03 wolf kernel: WARNING: / was not properly dismounted
Nov 21 18:24:03 wolf kernel: WARNING: /data was not properly dismounted
Nov 21 18:24:03 wolf kernel: WARNING: /home was not properly dismounted
Nov 21 18:24:03 wolf kernel: WARNING: /tmp was not properly dismounted
Nov 21 18:24:03 wolf kernel: WARNING: /usr was not properly dismounted
...

# mount /dev/da0s2 /mnt
mount: /dev/da0s2 : Operation not permitted

The USB stick cannot be mount under any FreeBSD OS now, and everything on the drive has lost.

Does anyone know if it is possible to revocer such damaged USB stick?

-----Original Message-----
From: Hans Petter Selasky [mailto:hselasky@c2i.net]
Sent: Wed 11/18/2009 3:13 AM
To: freebsd-usb@freebsd.org
Cc: Guojun Jin; freebsd-stable@freebsd.org; questions@freebsd.org
Subject: Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
 
Hi,

I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and 
the drive simply dies then it might be the case. Else it is a system issue.

There are quirks for mass storage which you can add to 
sys/dev/usb/storage/umass.c .

--HPS

On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote:
> Did newfs on those partition and made things worsen -- restore completely
> fails: (I had experienced another similar problem on an IDE, which works
> well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4.
>
> Is something new in 8.0 making disk partition schema changed?
>
> g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6
> g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6
> fopen: Device not configured
> cannot create save file ./restoresymtable for symbol table
> abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status ==
> 0xa, scs i status == 0x0
> (da0:umass-sim0:0:0:0): removing device entry
> ugen1.2: <DMI> at usbus1
> umass0: <DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2> on usbus1
> umass0:  SCSI over Bulk-Only; quirks = 0x0000
> umass0:0:0:-1: Attached to scbus0
> da0 at umass-sim0 bus 0 target 0 lun 0
> da0: <DMI Ultra HDD 1.19> Fixed Direct Access SCSI-0 device
> da0: 40.000MB/s transfers
> da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C)
> Device da0s3d went missing before all of the data could be written to it;
> expect data loss.
>
>     99  23:19   sysinstall
>    100  23:20   newfs /dev/da0s3d
>    101  23:20   newfs /dev/da0s3e
>    102  23:21   mount /dev/da0s3d /mnt
>    103  23:21   cd /mnt
>    104  23:21   dump -0f - /home | restore -rf -
>    105  23:27   history 15
>
>
>
> -----Original Message-----
> From: Guojun Jin
> Sent: Tue 11/17/2009 11:05 PM
> To: freebsd-stable@freebsd.org
> Cc: questions@freebsd.org; freebsd-usb@freebsd.org
> Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
>
> When mounting two partitions from a USB dirve, it can cause the drive
> access lock up for a long time. Details:
>
> Terminal 1 --
> term1# mount /dev/da0s3d  /mnt
> term1# cd /mnt ; rm -fr *
>
> when rm starts, go to terminal 2 and do:
>
> term2# mount /dev/da0s3e /dist ### this will hanging for a long time and
> USB hard drive activity light is off. After more than 1-2 minutes, mount
> returns, and the drive activity light is blinking, thus removing is going
> on.
>
> term2# ls /dist   ### this will cause dUSB dirve hanging again -- no
> avtivity. Similarly, ls will finish in a couple of miniutes or longer, the
> rm command continues; but for a while, the drive activity will stop again.
>
> Reboot machine, repeat the above steps, and result will be the same. Reboot
> machine again, and just mount one partition, then doing "rm -rf *" without
> involve the second partition, rm will finish quickly.
>
> Has anyone obseved this behave on 8.0-RC?
>
> -Jin


From gjin at ubicom.com  Sun Nov 22 04:45:34 2009
From: gjin at ubicom.com (Guojun Jin)
Date: Sun Nov 22 04:45:41 2009
Subject: 8.0-RC USB/FS problem
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A1D@STORK.scenix.com>
	<200911181213.34112.hselasky@c2i.net>
	<CB2DD11991B27C4F99935E6229450D3203950A23@STORK.scenix.com>
Message-ID: <CB2DD11991B27C4F99935E6229450D3203950A26@STORK.scenix.com>

Tried on the USB hard drive:

Deleted slice 3 and recreated slice 3 with two partitions s3d and s3e.
Was happy because successfully did dump/restore on s3d, and thought it just partition format issue;
but system crashed during dump/restore on s3e, and partition lost the file system type.

wolf# mount /dev/da0s3e /mnt
WARNING: /mnt was not properly dismounted
/mnt: mount pending error: blocks 35968 files 0
wolf# fsck da0s3e
fsck: Could not determine filesystem type
wolf# bsdlabel da0s3
# /dev/da0s3:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  c: 175735035        0    unused        0     0         # "raw" part, don't edi
t
  d: 18874368        0    4.2BSD        0     0     0
  e: 156860667 18874368    4.2BSD        0     0     0

Therefore, tried directly use fsck_ufs on both USB hard drive and USB stick to get file system
clean up. All data got back now.

The machine has run with FreeBSD 6.1 all the way to 7.2 without such problem.
How can we determine what could go wrong in 8.0? FS or USB.

By the way, IDE to IDE dump/restore seems not having such problem at this point, although
one of IDE drive experienced partition recognizing problem, which went away after deleting
slices and recreating slices.


-----Original Message-----
From: Guojun Jin
Sent: Sat 11/21/2009 7:40 PM
To: Hans Petter Selasky; freebsd-usb@freebsd.org
Cc: freebsd-stable@freebsd.org; questions@freebsd.org
Subject: 8.0-RC USB problem -- how to recover a damaged USB stick
 
It seems this is more serious problem in 8.0, and I hope it could be resolved before a formal release. I can help to diagnose this if people need more information (this is destructive).

I have picked a USB stick (DataTraveler 2GB), that has two partitions s0 for DOS and s1 for FreeBSD.
Both USB hard drive and the USB stick have worked under FreeBSD 6.2, 6.3, 6.4 and 7.2 for a few years without any problem.

Plugged USB stick in 8.0-RC and mounted it on /mnt; then
untar a file, tarred one day ago from FreeBSD 6.3 machine onto stick,to a IDE drive then tar it
back to the USB stick.
During tar writting from IDE to USB stick, did "ls /mnt", and "tar" paused and "ls" hangs.
A couple of minutes later, ls comes back, but tar still pauses.

Hit ^C on tar process around 14:30, it took another minutes to stop the process. Tried tar again,
and system disallowed to write on  the USB stick. "ls" shows all file still there (probably cached inods).

Went out for a few hours, and came back found /var/log/message are flooded with following message:
-rw-r--r--  1 root  wheel  167181 Nov 21 19:02 messages
-rw-r--r--  1 root  wheel    7390 Nov 21 18:00 messages.0.bz2
-rw-r--r--  1 root  wheel    7509 Nov 21 17:00 messages.1.bz2
-rw-r--r--  1 root  wheel    9365 Nov 21 16:00 messages.2.bz2
-rw-r--r--  1 root  wheel   20598 Nov 21 15:00 messages.3.bz2

Nov 21 18:00:00 wolf newsyslog[2635]: logfile turned over due to size>384K
Nov 21 18:00:27 wolf kernel: g_vfs_done():da0s2[WRITE(offset=625688576, length=1
31072)]error = 5
Nov 21 18:00:27 wolf kernel: g_vfs_done():da0s2[WRITE(offset=625819648, length=1
31072)]error = 5
.....
Nov 21 18:19:03 wolf kernel: g_vfs_done():da0s2[WRITE(offset=524451840, length=1
6384)]error = 5
Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=5586944, length=204
8)]error = 5
Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=65536, length=2048)
]error = 5
Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=114688, length=1638
4)]error = 5
Nov 21 18:20:05 wolf kernel: g_vfs_done():da0s2[WRITE(offset=349700096, length=1

and has to reboot the system, and reboot was not able to umount everything (boot up message):

Nov 21 18:24:03 wolf kernel: da0: <Kingston DataTraveler 2.0 1.00> Removable Dir
ect Access SCSI-2 device
Nov 21 18:24:03 wolf kernel: da0: 40.000MB/s transfers
Nov 21 18:24:03 wolf kernel: da0: 1947MB (3987456 512 byte sectors: 255H 63S/T 2
48C)
Nov 21 18:24:03 wolf kernel: WARNING: / was not properly dismounted
Nov 21 18:24:03 wolf kernel: WARNING: /data was not properly dismounted
Nov 21 18:24:03 wolf kernel: WARNING: /home was not properly dismounted
Nov 21 18:24:03 wolf kernel: WARNING: /tmp was not properly dismounted
Nov 21 18:24:03 wolf kernel: WARNING: /usr was not properly dismounted
...

# mount /dev/da0s2 /mnt
mount: /dev/da0s2 : Operation not permitted

The USB stick cannot be mount under any FreeBSD OS now, and everything on the drive has lost.

Does anyone know if it is possible to revocer such damaged USB stick?

-----Original Message-----
From: Hans Petter Selasky [mailto:hselasky@c2i.net]
Sent: Wed 11/18/2009 3:13 AM
To: freebsd-usb@freebsd.org
Cc: Guojun Jin; freebsd-stable@freebsd.org; questions@freebsd.org
Subject: Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
 
Hi,

I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and 
the drive simply dies then it might be the case. Else it is a system issue.

There are quirks for mass storage which you can add to 
sys/dev/usb/storage/umass.c .

--HPS

On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote:
> Did newfs on those partition and made things worsen -- restore completely
> fails: (I had experienced another similar problem on an IDE, which works
> well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4.
>
> Is something new in 8.0 making disk partition schema changed?
>
> g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6
> g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6
> fopen: Device not configured
> cannot create save file ./restoresymtable for symbol table
> abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status ==
> 0xa, scs i status == 0x0
> (da0:umass-sim0:0:0:0): removing device entry
> ugen1.2: <DMI> at usbus1
> umass0: <DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2> on usbus1
> umass0:  SCSI over Bulk-Only; quirks = 0x0000
> umass0:0:0:-1: Attached to scbus0
> da0 at umass-sim0 bus 0 target 0 lun 0
> da0: <DMI Ultra HDD 1.19> Fixed Direct Access SCSI-0 device
> da0: 40.000MB/s transfers
> da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C)
> Device da0s3d went missing before all of the data could be written to it;
> expect data loss.
>
>     99  23:19   sysinstall
>    100  23:20   newfs /dev/da0s3d
>    101  23:20   newfs /dev/da0s3e
>    102  23:21   mount /dev/da0s3d /mnt
>    103  23:21   cd /mnt
>    104  23:21   dump -0f - /home | restore -rf -
>    105  23:27   history 15
>
>
>
> -----Original Message-----
> From: Guojun Jin
> Sent: Tue 11/17/2009 11:05 PM
> To: freebsd-stable@freebsd.org
> Cc: questions@freebsd.org; freebsd-usb@freebsd.org
> Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
>
> When mounting two partitions from a USB dirve, it can cause the drive
> access lock up for a long time. Details:
>
> Terminal 1 --
> term1# mount /dev/da0s3d  /mnt
> term1# cd /mnt ; rm -fr *
>
> when rm starts, go to terminal 2 and do:
>
> term2# mount /dev/da0s3e /dist ### this will hanging for a long time and
> USB hard drive activity light is off. After more than 1-2 minutes, mount
> returns, and the drive activity light is blinking, thus removing is going
> on.
>
> term2# ls /dist   ### this will cause dUSB dirve hanging again -- no
> avtivity. Similarly, ls will finish in a couple of miniutes or longer, the
> rm command continues; but for a while, the drive activity will stop again.
>
> Reboot machine, repeat the above steps, and result will be the same. Reboot
> machine again, and just mount one partition, then doing "rm -rf *" without
> involve the second partition, rm will finish quickly.
>
> Has anyone obseved this behave on 8.0-RC?
>
> -Jin



From hselasky at c2i.net  Sun Nov 22 09:31:44 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Nov 22 09:31:51 2009
Subject: 8.0-RC USB problem -- how to recover a damaged USB stick
In-Reply-To: <CB2DD11991B27C4F99935E6229450D3203950A23@STORK.scenix.com>
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<200911181213.34112.hselasky@c2i.net>
	<CB2DD11991B27C4F99935E6229450D3203950A23@STORK.scenix.com>
Message-ID: <200911221033.17251.hselasky@c2i.net>

On Sunday 22 November 2009 04:40:27 Guojun Jin wrote:
> Does anyone know if it is possible to revocer such damaged USB stick?

Hi,

There are several recovery tools in /usr/ports for this kind of task.

For example photorec .

--HPS

From hselasky at c2i.net  Sun Nov 22 09:45:47 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Nov 22 09:46:08 2009
Subject: 8.0-RC USB/FS problem
In-Reply-To: <CB2DD11991B27C4F99935E6229450D3203950A26@STORK.scenix.com>
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A23@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A26@STORK.scenix.com>
Message-ID: <200911221047.20362.hselasky@c2i.net>

On Sunday 22 November 2009 05:38:13 Guojun Jin wrote:
> Tried on the USB hard drive:
>
> Deleted slice 3 and recreated slice 3 with two partitions s3d and s3e.
> Was happy because successfully did dump/restore on s3d, and thought it just
> partition format issue; but system crashed during dump/restore on s3e, and
> partition lost the file system type.
>
> wolf# mount /dev/da0s3e /mnt
> WARNING: /mnt was not properly dismounted
> /mnt: mount pending error: blocks 35968 files 0
> wolf# fsck da0s3e
> fsck: Could not determine filesystem type
> wolf# bsdlabel da0s3
> # /dev/da0s3:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>   c: 175735035        0    unused        0     0         # "raw" part,
> don't edi t
>   d: 18874368        0    4.2BSD        0     0     0
>   e: 156860667 18874368    4.2BSD        0     0     0
>
> Therefore, tried directly use fsck_ufs on both USB hard drive and USB stick
> to get file system clean up. All data got back now.
>
> The machine has run with FreeBSD 6.1 all the way to 7.2 without such
> problem. How can we determine what could go wrong in 8.0? FS or USB.

Hi,

Error 5 means IO error, so probably the transport layer, USB or lower, is to 
blame.

Some things to check:

1) Make sure the connection for your memory stick is Ok.
2) Make sure there is enough power for your memory stick.

Regarding memory sticks:

Other operating systems do a port bus reset when the device has a problem. On 
FreeBSD we just try a software reset via the control endpoint. I guess that it 
is a device problem you are seeing. The USB stack in FreeBSD is faster than 
the old one, and maybe the faster queueing of mass storage requests trigger 
some hidden bugs in your device.

When the problem happens try:

sysctl hw.usb.umass.debug=-1

--HPS
From sasha.devel at gmail.com  Sun Nov 22 20:09:05 2009
From: sasha.devel at gmail.com (Alexander Samarin)
Date: Sun Nov 22 20:09:12 2009
Subject: usb ethernet driver question
Message-ID: <4B099A50.9000006@gmail.com>

Hello, all!

I'm trying to write a kernel module driver for WiMAX modem.
I have Samsung SWC-U100 USB modem.

Driver is based on if_cue module (it's source file is smallest in the tree).
I've get module successfully attaching to device and registering new network 
interface, but some questions appeared:

1. madwimax project have a description of protocol of the modem, but it says
    simply "This data should be sent over OUT endpoint in bulk mode."
    In other drivers I found only calls to functionu ether_do_request() e.g:

       struct usb_device_request req;

       req.bmRequestType = UT_READ_VENDOR_DEVICE;
       req.bRequest = CUE_CMD_GET_MACADDR;
       USETW(req.wValue, 0);
       USETW(req.wIndex, 0);
       USETW(req.wLength, ETHER_ADDR_LEN);

       uether_do_request(&sc->sc_ue, &req, buf, 1000);

    Here I can't understand:
    Buffer can be sent or received via buf argument of ether_do_request(), but
    what value should be used for req.bRequest, req.wValue and req.wIndex fields?

    In dev/usb/net/if_* files drivers read and write to registers or memory of
    chip; libusb just writes to file descriptor.

    Can anyone take me a link where I can read more about programming usb
    drivers for kernel?

2. Is it possible to detach CAM subsystem from virtual DVD-ROM on other
    interface? This DVD-ROM contains WinXP drivers and access program, which
    will never be used (I think) on UNIX systems.

PS: I know that if_cue is an ethernet driver, but WiMAX is a wireless so basing
    driver on if_cue code is not a good idea, but wireless drivers are big and
    my modem can connect only to one provider (Yota) so I decided to use if_cue
    as base code.

PS2: sorry for my English.

-- 
Best regards,  Alexander Samarin
     mailto:sasha at enikasoft.ru
     https://www.fsora.ru (waits for FreeBSD 8.0-RELEASE)
From gjin at ubicom.com  Mon Nov 23 04:12:00 2009
From: gjin at ubicom.com (Guojun Jin)
Date: Mon Nov 23 04:12:13 2009
Subject: 8.0-RC USB/FS problem
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A23@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A26@STORK.scenix.com>
	<200911221047.20362.hselasky@c2i.net>
Message-ID: <CB2DD11991B27C4F99935E6229450D3203950A27@STORK.scenix.com>

>From more intensive diagnose, it looks like more related USB layer.

repeated a few time on following process and ithe crash happened at different USB access phase at each time.

dd if=/dev/zero of=/dev/da0 count=1000 bs=4k
sysinstall
        partition 
             slice 1 (da0s1) 18GB ID=12
             slice 2 (da0s2) 10-15GB Id=165
             slice 3 (da0s3) rest ID=165
         W ---> OK
        label
             da0s3d 9GB         /mnt
             da0s3e rest        /dist
         W ---> da0s3e ---- device is not configured.

w# ll /dev/da0*      # after sysinstall did partition + W at 1st time
crw-r-----  1 root  operator    0,  97 Nov 22 11:23 /dev/da0
crw-r-----  1 root  operator    0,  98 Nov 22 11:23 /dev/da0s1
crw-r-----  1 root  operator    0,  99 Nov 22 11:23 /dev/da0s2
crw-r-----  1 root  operator    0, 100 Nov 22 11:23 /dev/da0s3

# ll /dev/da0*      # after sysinstall start at 2nd time
crw-r-----  1 root  operator    0,  97 Nov 22 11:27 /dev/da0
System crashed

The crash log is available at http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2
(All logs are based on hw.usb.umass.debug=-1)

After system reboot, and repeated above processes, the da0s3e was mounted on /dist, but da0s3d cannot.
It tunred out that newfs fail inside labeling process in sysinstall. Manually did newfs on da0s3d, and
it cannot be mounted on /mnt, but access to it caused crash.
The crash log is available at http:/www.daemonfun.com/archives/pub/USB/newfs

Tried entire process again, this time, both partitons are formatted (newfs) inside labaling process (sysinstall)
but crahsed system during dump/restore on da0s3e (/dist).
The crash log is available at http:/www.daemonfun.com/archives/pub/USB/usb-log.crash2.bz2, which is huge one.
It contains two parts, one dump/restore IDE to da0s3d (passed), and the rest is dump/restore to da0s3e (crashed).

I am going to reinstall the system with the new ISO from Nov 21 8.0-RELEASE to see if anything will improve.

-----Original Message-----
From: Hans Petter Selasky [mailto:hselasky@c2i.net]
Sent: Sun 11/22/2009 1:47 AM
To: freebsd-usb@freebsd.org
Cc: Guojun Jin; bugs@freebsd.org; freebsd-stable@freebsd.org
Subject: Re: 8.0-RC USB/FS problem
 
On Sunday 22 November 2009 05:38:13 Guojun Jin wrote:
> Tried on the USB hard drive:
>
> Deleted slice 3 and recreated slice 3 with two partitions s3d and s3e.
> Was happy because successfully did dump/restore on s3d, and thought it just
> partition format issue; but system crashed during dump/restore on s3e, and
> partition lost the file system type.
>
> wolf# mount /dev/da0s3e /mnt
> WARNING: /mnt was not properly dismounted
> /mnt: mount pending error: blocks 35968 files 0
> wolf# fsck da0s3e
> fsck: Could not determine filesystem type
> wolf# bsdlabel da0s3
> # /dev/da0s3:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>   c: 175735035        0    unused        0     0         # "raw" part,
> don't edi t
>   d: 18874368        0    4.2BSD        0     0     0
>   e: 156860667 18874368    4.2BSD        0     0     0
>
> Therefore, tried directly use fsck_ufs on both USB hard drive and USB stick
> to get file system clean up. All data got back now.
>
> The machine has run with FreeBSD 6.1 all the way to 7.2 without such
> problem. How can we determine what could go wrong in 8.0? FS or USB.

Hi,

Error 5 means IO error, so probably the transport layer, USB or lower, is to 
blame.

Some things to check:

1) Make sure the connection for your memory stick is Ok.
2) Make sure there is enough power for your memory stick.

Regarding memory sticks:

Other operating systems do a port bus reset when the device has a problem. On 
FreeBSD we just try a software reset via the control endpoint. I guess that it 
is a device problem you are seeing. The USB stack in FreeBSD is faster than 
the old one, and maybe the faster queueing of mass storage requests trigger 
some hidden bugs in your device.

When the problem happens try:

sysctl hw.usb.umass.debug=-1

--HPS

From bugmaster at FreeBSD.org  Mon Nov 23 11:07:06 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Nov 23 11:09:43 2009
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200911231107.nANB75PS070280@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
--------------------------------------------------------------------------------
f usb/140714   usb        [hang] system freeze when disconect my flash usb
o kern/140614  usb        [uplcom] [patch] adding support for Radio Shack Gigwar
o usb/140590   usb        [bluetooth] [usb] ng_ubt(4) ng_l2cap_process_cmd_rej w
o usb/140477   usb        [umass] [patch] allow boot-time attachment of daX devi
o usb/140325   usb        Missing/incorrect initialisation and memory leak in li
o usb/140259   usb        libusb-1.0 portability/compatibility nits
o usb/140242   usb        dev/usb/controller/ehci_ix4xx.c shortcomings
o usb/140236   usb        [msdosfs] Labels wiped on external Journaled USB HDD o
o usb/140160   usb        USB ports are no longer "active" after ACPI suspend/re
o usb/139990   usb        [panic] Kernel frequently panics after printing
o usb/139598   usb        [umass] CAM reports "xptioctl: put "device pass" in yo
o usb/139243   usb        [uhci] unplug prolific USB serial -> uhci_abort_xfer: 
o usb/139142   usb        [regression] ehci drivers (NVIDIA nForce4 USB 2.0 cont
o usb/138915   usb        [patch][usb8][usb67] add support for SheevaPlug serial
o usb/138904   usb        [rum] unpluging USB wifi card panics system
f usb/138882   usb        [ohci] [panic] Can't install FreeBSD 7.2 due to ohci p
o usb/138879   usb        [uftdi] [patch] Patch to add support for CTI USB-Mini 
o usb/138798   usb        8.0-BETA4 can't boot from USB flash drive [regression]
o usb/138675   usb        [usb8] [panic] page fault, perhaps in USB
o usb/138659   usb        [usb8][uftdi] driver broken in RELENG_8/CURRENT
o usb/138389   usb        [usb8] [patch] NULL pointer dereference in usb_endpoin
o usb/138175   usb        [usb67] [boot] System cannot boot, when USB reader wit
o usb/138172   usb        Additional dev id for u3g (Option mini PCIe)
o usb/138138   usb        Novatel U760 for u3g (Verizon and Bell Canada)
o usb/138124   usb        [usb8] Axed uaudio functionality in the usbng (alterna
o usb/138119   usb        MultiBay CDROM (propably on USB bus) is not recognized
o usb/137872   usb        slow booting on usb flash drive
f usb/137848   usb        Page fault when using an USB bluetooth adapter
o usb/137806   usb        [ukbd] USB keyboard doesn't work until it's unplugged
o usb/137763   usb        [usb67][ukbd] Logitech wireless keyboard media keys no
o usb/137616   usb        [usb67][usb8][usbdevs] [patch]: usbdevs update: Please
o usb/137377   usb        [usb8] Support for Huawei E180
o usb/137341   usb        [usb8][rum] driver if_rum doesn't work at all and thro
p usb/137226   usb        [usb67][patch] quirk for Philips extern USB disk
o usb/137190   usb        [usb8][patch] inhibit spurious button releases for som
o usb/137189   usb        [usb8][patch] create and use sysctl nodes for HID repo
p usb/137188   usb        [usb8][patch] correctly handle USB report descriptors 
o usb/137129   usb        SteelSeries Ikari USB laser mouse not attaching
p usb/136761   usb        [usbdevs][usb67][patch] Teach usbdevs / u3g(4) about H
o usb/135938   usb        [aue] aue driver only passes traffic in promisc mode
f usb/135857   usb        RTL8187 Wireless Adapter
o usb/135575   usb        [usbdevs] [patch] Add HTC Wizard phone vid/pid informa
o usb/135542   usb        [keyboard] boot loader does not work with a usb keyboa
p usb/135372   usb        [usb67][umass] Quirk report for Teclast TL-C300 usb me
o usb/135348   usb        [umass] USB Drive Hangs with ZFS (JMicron USB2/eSata)
o usb/135206   usb        machine reboots when inserted USB device
o usb/135200   usb        SAMSUNG i740 usb mass: Synchronize cache failed, statu
o usb/135182   usb        UMASS quirk - Olympus FE20 camera
o usb/134950   usb        Lowering DTR for USB-modem via ubsa is not possible
o usb/134633   usb        Add support for WILLCOM03(SHARP smart phone)
o usb/134631   usb        [usbdevs] [patch] WiSPY DBx support requires usb tweak
o usb/134299   usb        Kernel Panic plugging in MF626 USB UMTS Stick u3g
o usb/134193   usb        System freeze on usb MP3 player insertion
o usb/134117   usb        [Patch] Add support for 'Option GlobeTrotter HSDPA Mod
o usb/134085   usb        [umass] Adding usb quirk for Sony USB flash drive
o usb/133989   usb        [newusb] [ukbd] USB keyboard dead at mountroot> prompt
o usb/133712   usb        [ural] [patch] RE: Fixed an issue with ural(4) that wa
o usb/133390   usb        umass crashes system in 7.1 when Olympus D-540 attache
o usb/133296   usb        [rum] driver not working properly in hostap mode
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] [rum] Kernel panic after NOMEM caused by
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
o 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/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/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
o 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
p usb/127549   usb        [umass] [usb67] [patch] Meizu MiniPlayer M6 (SL) requi
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] [panic] enabling usb keyboard and mouse support
o usb/127248   usb        [ucom] panic while uplcom devices attaach and detach
o usb/127222   usb        [ohci] Regression in 7.0 usb storage generic driver
o usb/126884   usb        [ugen] [patch] Bug in buffer handling in ugen.c
o usb/126848   usb        [usb]: USB Keyboard hangs during Installation
o usb/126740   usb        [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be
o usb/126519   usb        [usb] [panic] panic when plugging in an iphone
o kern/126396  usb        [panic] kernel panic after unplug USB Bluetooth device
o usb/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/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 kern/124130  usb        [usb] gmirror fails to start usb devices that were pre
o usb/123969   usb        [usb] Supermicro H8SMi-2 usb problem: port reset faile
o usb/123714   usb        [usb] [panic] Panic when hald-storage-probe runs with 
o usb/123691   usb        usbd(8): usbd hangs
o usb/123690   usb        [usb] [panic] Panic on USB device insertion when usb l
o usb/123611   usb        [usb] BBB reset failed, STALLED from Imation/Mitsumi U
o usb/123509   usb        [umass] continuous reset Samsung SGH-G600 phone
o usb/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        [new driver] [patch] New driver for Sierra Wireless 3G
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] [panic] FreeBSD fails to boot with usb legacy s
o usb/121232   usb        [usb] [panic] USB CardBus card removal causes reboot s
p usb/121184   usb        [uipaq] [patch] add ids from linux ipaq driver (plus a
o usb/121169   usb        [umass] Issues with usb mp3 player
o usb/121045   usb        [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS
o usb/120786   usb        [usb] [panic] Kernel panic when forced umount of a det
o usb/120729   usb        [panic] fault while in kernel mode with connecting USB
o usb/120572   usb        [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/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        [usb67] [usb8] [umass] [patch] Problem with connection
o conf/114013  usb        [patch] WITHOUT_USB allow to compil a lot of USB stuff
o usb/113060   usb        [usb67] [ulpt] [patch] Samsung printer not working in 
o usb/110856   usb        [usb67] [ugen] [patch] interrupt in msgs are truncated
s usb/108344   usb        [usb67] [atausb] [panic] kernel with atausb panics whe
o usb/107827   usb        [usb67] [ohci] [panic] ohci_add_done addr not found
o usb/107388   usb        [usb67] [usb8] [new driver] [patch] add utoppy device 
o usb/107243   usb        [usb67] [cam] [quirk] [patch] Apacer USB Flash Drive q
o usb/106041   usb        [usb67] [usb8] [request] FreeBSD does not recognise Mu
o usb/105361   usb        [usb67] [panic] Kernel panic during unmounting mass st
s usb/103917   usb        [usb67] [uhub] USB driver reports "Addr 0 should never
o usb/103418   usb        [usb67] [usb8] [patch] [request] usbhidctl(8) add abil
o usb/103046   usb        [usb67] [ulpt] [patch] ulpt event driven I/O with sele
o usb/101775   usb        [usb67] [usb8] [libusbhid] [patch] possible error in r
o usb/101761   usb        [usb67] [patch] [request] usb.h: increase maximal size
o usb/100746   usb        [usb67] [ukbd] system does not boot due to USB keyboar
o usb/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/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/83977    usb        [ucom] [panic] ucom1: open bulk out error (addr 2): IN
o usb/83863    usb        [ugen] Communication problem between opensc/openct via
o usb/83756    usb        [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe
o usb/83563    usb        [umass] [panic] Page Fault while detaching Mpman Usb d
o usb/83504    usb        [kernel] [patch] SpeedTouch USB stop working on recent
o usb/82660    usb        [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic
s usb/82569    usb        [umass] [panic] USB mass storage plug/unplug causes sy
o usb/82520    usb        [udbp] [reboot] Reboot when USL101 connected
o usb/82350    usb        [ucom] [panic] null pointer dereference in USB stack
o usb/81621    usb        [ehci] [hang] external hd hangs under load on ehci
o usb/80935    usb        [uvisor] [patch] uvisor.c is not work with CLIE TH55.
o usb/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        [sound] [hang] Use of sound mixer causes system freeze
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] [regression] 5.3-STABLE(2005 1/4) detect USB h
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

316 problems total.

From csmith at bonddesk.com  Mon Nov 23 15:50:02 2009
From: csmith at bonddesk.com (Corey Smith)
Date: Mon Nov 23 15:50:09 2009
Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
Message-ID: <200911231545.nANFjs2W091289@www.freebsd.org>


>Number:         140810
>Category:       usb
>Synopsis:       8.X+ uftdi copy and paste problem / tty overflow
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 23 15:50:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Corey Smith
>Release:        8.0-RC3
>Organization:
BondDesk Group
>Environment:
FreeBSD  8.0-RC3 FreeBSD 8.0-RC3 #2: Fri Nov 20 18:28:57 EST 2009     root@:/usr/src/sys/amd64/compile/GENERIC  amd64

>Description:
We are using a VSCOM USB-16COM-RM which is a UFTDI based 16 port serial terminal.

It is detected as 8 FT2232C dual port serial connections:

product FTDI SERIAL_2232C       0x6010  FT2232C Dual port Serial

ugen3.3: <USB FAST SERIAL ADAPTER FTDI> at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x0000 
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0008 
  idVendor = 0x0403 
  idProduct = 0x6010 
  bcdDevice = 0x0500 
  iManufacturer = 0x0001  <FTDI>
  iProduct = 0x0002  <USB FAST SERIAL ADAPTER>
  iSerialNumber = 0x0003  <FT58L91Z>
  bNumConfigurations = 0x0001 

If you 'tip ucom1' and paste a long sequence of text into the terminal then the terminal will start to constantly spew what appears to be random memory contents to the host connected on ucom1.  This same configuration is known good in 7.1-RELEASE.

The problem definitely occurs on 8.0-BETA3 and 8.0-RC3.  The serial ports work fine if you never copy and paste but as soon as you start to copy and paste more than 60 odd characters at a time you see this random garbage on the tty.  AFAIK the garbage will continuously send to the attached host until you reboot the box.

I don't know if this problem is reproducible using other uftdi based devices as I don't have any other hardware to test with.

>How-To-Repeat:
Paste long sequences of text into a tip session connected through a uftdi device under 8.0-RC3.  Notice constant garbage being transmitted to the host until you reboot the console server.
>Fix:
No fix but a workaround is to not copy and paste into terminals connected through uftdi devices.

>Release-Note:
>Audit-Trail:
>Unformatted:
From hselasky at c2i.net  Mon Nov 23 16:23:49 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Nov 23 16:23:55 2009
Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
In-Reply-To: <200911231545.nANFjs2W091289@www.freebsd.org>
References: <200911231545.nANFjs2W091289@www.freebsd.org>
Message-ID: <200911231725.20787.hselasky@c2i.net>

On Monday 23 November 2009 16:45:54 Corey Smith wrote:
> >Number:         140810
> >Category:       usb
> >Synopsis:       8.X+ uftdi copy and paste problem / tty overflow
> >Confidential:   no
> >Severity:       serious
> >Priority:       medium
> >Responsible:    freebsd-usb
> >State:          open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Mon Nov 23 15:50:01 UTC 2009
> >Closed-Date:
> >Last-Modified:
> >Originator:     Corey Smith
> >Release:        8.0-RC3
> >Organization:
>
> BondDesk Group
>
> >Environment:
>
> FreeBSD  8.0-RC3 FreeBSD 8.0-RC3 #2: Fri Nov 20 18:28:57 EST 2009    
> root@:/usr/src/sys/amd64/compile/GENERIC  amd64
>
> >Description:
>
> We are using a VSCOM USB-16COM-RM which is a UFTDI based 16 port serial
> terminal.
>
> It is detected as 8 FT2232C dual port serial connections:
>
> product FTDI SERIAL_2232C       0x6010  FT2232C Dual port Serial
>
> ugen3.3: <USB FAST SERIAL ADAPTER FTDI> at usbus3, cfg=0 md=HOST spd=FULL
> (12Mbps) pwr=ON
>
>   bLength = 0x0012
>   bDescriptorType = 0x0001
>   bcdUSB = 0x0200
>   bDeviceClass = 0x0000
>   bDeviceSubClass = 0x0000
>   bDeviceProtocol = 0x0000
>   bMaxPacketSize0 = 0x0008
>   idVendor = 0x0403
>   idProduct = 0x6010
>   bcdDevice = 0x0500
>   iManufacturer = 0x0001  <FTDI>
>   iProduct = 0x0002  <USB FAST SERIAL ADAPTER>
>   iSerialNumber = 0x0003  <FT58L91Z>
>   bNumConfigurations = 0x0001
>
> If you 'tip ucom1' and paste a long sequence of text into the terminal then
> the terminal will start to constantly spew what appears to be random memory
> contents to the host connected on ucom1.  This same configuration is known
> good in 7.1-RELEASE.
>
> The problem definitely occurs on 8.0-BETA3 and 8.0-RC3.  The serial ports
> work fine if you never copy and paste but as soon as you start to copy and
> paste more than 60 odd characters at a time you see this random garbage on
> the tty.  AFAIK the garbage will continuously send to the attached host
> until you reboot the box.
>
> I don't know if this problem is reproducible using other uftdi based
> devices as I don't have any other hardware to test with.
>
> >How-To-Repeat:
>
> Paste long sequences of text into a tip session connected through a uftdi
> device under 8.0-RC3.  Notice constant garbage being transmitted to the
> host until you reboot the console server.
>
> >Fix:
>
> No fix but a workaround is to not copy and paste into terminals connected
> through uftdi devices.
>

Hi,

I can you enable ucom debugging while doing the test?

sysctl hw.usb.ucom.debug=15

--HPS
From hselasky at c2i.net  Mon Nov 23 16:30:11 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Nov 23 16:30:23 2009
Subject: usb ethernet driver question
In-Reply-To: <4B099A50.9000006@gmail.com>
References: <4B099A50.9000006@gmail.com>
Message-ID: <200911231731.45953.hselasky@c2i.net>

On Sunday 22 November 2009 21:08:48 Alexander Samarin wrote:
> Hello, all!
>
> I'm trying to write a kernel module driver for WiMAX modem.
> I have Samsung SWC-U100 USB modem.
>
> Driver is based on if_cue module (it's source file is smallest in the
> tree). I've get module successfully attaching to device and registering new
> network interface, but some questions appeared:
>
> 1. madwimax project have a description of protocol of the modem, but it
> says simply "This data should be sent over OUT endpoint in bulk mode." In
> other drivers I found only calls to functionu ether_do_request() e.g:
>
>        struct usb_device_request req;
>
>        req.bmRequestType = UT_READ_VENDOR_DEVICE;
>        req.bRequest = CUE_CMD_GET_MACADDR;
>        USETW(req.wValue, 0);
>        USETW(req.wIndex, 0);
>        USETW(req.wLength, ETHER_ADDR_LEN);
>
>        uether_do_request(&sc->sc_ue, &req, buf, 1000);
>
>     Here I can't understand:
>     Buffer can be sent or received via buf argument of ether_do_request(),
> but what value should be used for req.bRequest, req.wValue and req.wIndex
> fields?

Hi,

The example you have given is for a CONTROL endpoint. CONTROL endpoint 
messages typically consist of 3 stages: <SETUP> <DATA> <STATUS>

BULK endpoints only transfer <DATA>

If the configuration data is sent accross a BULK endpoint, you need to 
allocate a separate BULK endpoint for that and consequently cannot use 
ether_do_request(). 

>
>     In dev/usb/net/if_* files drivers read and write to registers or memory
> of chip; libusb just writes to file descriptor.
>
>     Can anyone take me a link where I can read more about programming usb
>     drivers for kernel?

man 4 usb

>
> 2. Is it possible to detach CAM subsystem from virtual DVD-ROM on other
>     interface? This DVD-ROM contains WinXP drivers and access program,
> which will never be used (I think) on UNIX systems.

Yes:

1) parent the CAM interface to your driver. Then umass won't attach to it
2) look in sys/dev/usb/usb_msctest.c

>
> PS: I know that if_cue is an ethernet driver, but WiMAX is a wireless so
> basing driver on if_cue code is not a good idea, but wireless drivers are
> big and my modem can connect only to one provider (Yota) so I decided to
> use if_cue as base code.
>
> PS2: sorry for my English.

Your English is good!

--HPS


From hselasky at c2i.net  Mon Nov 23 16:30:13 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Nov 23 16:30:24 2009
Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
Message-ID: <200911231630.nANGUC9l091372@freefall.freebsd.org>

The following reply was made to PR usb/140810; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Corey Smith <csmith@bonddesk.com>,
 freebsd-gnats-submit@freebsd.org
Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
Date: Mon, 23 Nov 2009 17:25:19 +0100

 On Monday 23 November 2009 16:45:54 Corey Smith wrote:
 > >Number:         140810
 > >Category:       usb
 > >Synopsis:       8.X+ uftdi copy and paste problem / tty overflow
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    freebsd-usb
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Mon Nov 23 15:50:01 UTC 2009
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Corey Smith
 > >Release:        8.0-RC3
 > >Organization:
 >
 > BondDesk Group
 >
 > >Environment:
 >
 > FreeBSD  8.0-RC3 FreeBSD 8.0-RC3 #2: Fri Nov 20 18:28:57 EST 2009    
 > root@:/usr/src/sys/amd64/compile/GENERIC  amd64
 >
 > >Description:
 >
 > We are using a VSCOM USB-16COM-RM which is a UFTDI based 16 port serial
 > terminal.
 >
 > It is detected as 8 FT2232C dual port serial connections:
 >
 > product FTDI SERIAL_2232C       0x6010  FT2232C Dual port Serial
 >
 > ugen3.3: <USB FAST SERIAL ADAPTER FTDI> at usbus3, cfg=0 md=HOST spd=FULL
 > (12Mbps) pwr=ON
 >
 >   bLength = 0x0012
 >   bDescriptorType = 0x0001
 >   bcdUSB = 0x0200
 >   bDeviceClass = 0x0000
 >   bDeviceSubClass = 0x0000
 >   bDeviceProtocol = 0x0000
 >   bMaxPacketSize0 = 0x0008
 >   idVendor = 0x0403
 >   idProduct = 0x6010
 >   bcdDevice = 0x0500
 >   iManufacturer = 0x0001  <FTDI>
 >   iProduct = 0x0002  <USB FAST SERIAL ADAPTER>
 >   iSerialNumber = 0x0003  <FT58L91Z>
 >   bNumConfigurations = 0x0001
 >
 > If you 'tip ucom1' and paste a long sequence of text into the terminal then
 > the terminal will start to constantly spew what appears to be random memory
 > contents to the host connected on ucom1.  This same configuration is known
 > good in 7.1-RELEASE.
 >
 > The problem definitely occurs on 8.0-BETA3 and 8.0-RC3.  The serial ports
 > work fine if you never copy and paste but as soon as you start to copy and
 > paste more than 60 odd characters at a time you see this random garbage on
 > the tty.  AFAIK the garbage will continuously send to the attached host
 > until you reboot the box.
 >
 > I don't know if this problem is reproducible using other uftdi based
 > devices as I don't have any other hardware to test with.
 >
 > >How-To-Repeat:
 >
 > Paste long sequences of text into a tip session connected through a uftdi
 > device under 8.0-RC3.  Notice constant garbage being transmitted to the
 > host until you reboot the console server.
 >
 > >Fix:
 >
 > No fix but a workaround is to not copy and paste into terminals connected
 > through uftdi devices.
 >
 
 Hi,
 
 I can you enable ucom debugging while doing the test?
 
 sysctl hw.usb.ucom.debug=15
 
 --HPS
From oxyd.oxyd at gmail.com  Mon Nov 23 18:04:24 2009
From: oxyd.oxyd at gmail.com (=?UTF-8?Q?Ond=C5=99ej_Majerech?=)
Date: Mon Nov 23 18:04:30 2009
Subject: USB mouse not working on 8.0-RELEASE
Message-ID: <f60d361f0911231004i4a8aa4c1ma9aa9d164ef327e2@mail.gmail.com>

Hello,

I've just upgraded my box to 8.0-RELEASE (FreeBSD starlight
8.0-RELEASE FreeBSD 8.0-RELEASE #9: Mon Nov 23 17:52:12 CET 2009
root@starlight:/usr/obj/usr/src/sys/STARLIGHT  i386) via csup'ing to
RELENG_8_0 and the usual suite of buildworld, buildkernel,
installkernel, mergemaster -p, installworld, mergemaster.

My USB mouse doesn't work now.  While booting, I can see error
messages from the USB part of the kernel; the same messages also
reappear when I disconnect and reconnect the thing.  They read the
following: (Grabbed from /var/log/messages after having dis- and
re-connected the mouse.)

Nov 23 18:54:19 starlight kernel: usb_alloc_device:1586: set address 2
failed (USB_ERR_TIMEOUT, ignored)
Nov 23 18:54:20 starlight kernel: usb_alloc_device:1624: getting
device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
Nov 23 18:54:21 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
set address failed! (USB_ERR_TIMEOUT, ignored)
Nov 23 18:54:22 starlight kernel: usbd_req_re_enumerate:1553: getting
device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
Nov 23 18:54:24 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
set address failed! (USB_ERR_TIMEOUT, ignored)
Nov 23 18:54:25 starlight kernel: usbd_req_re_enumerate:1553: getting
device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
Nov 23 18:54:25 starlight kernel: ugen0.2: <(null)> at usbus0 (disconnected)
Nov 23 18:54:25 starlight kernel: uhub_reattach_port:435: could not
allocate new device!

The mouse was working without any problems whatsoever on 8.0-RC3 and
all older FBSD versions that I used.

Other USB devices work as they should, without producing anything
unusual in dmesg.

So, what's up?  Any clues?

~ Ondra
From csmith at bonddesk.com  Mon Nov 23 19:16:18 2009
From: csmith at bonddesk.com (Corey Smith)
Date: Mon Nov 23 19:16:25 2009
Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
In-Reply-To: <200911231725.20787.hselasky@c2i.net>
References: <200911231545.nANFjs2W091289@www.freebsd.org>
	<200911231725.20787.hselasky@c2i.net>
Message-ID: <1259002796.16068.110.camel@csmith-desktop.bdg.local>

On Mon, 2009-11-23 at 11:25 -0500, Hans Petter Selasky wrote:
> sysctl hw.usb.ucom.debug=15

Thanks for the quick reply.  I decided to do a fresh install of
8.0-RELEASE amd64 before I re-ran the test.  Here are the details:

# uname -a
FreeBSD lab1 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009     root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
# sysctl hw.usb.ucom.debug=15
# tip ucom1
connected
# paste 160 "a"s followed by a newline (may take several attempts when debugging is enabled)
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Nov 23 14:54:13 lab1 su: csmith to root on /dev/pts/0
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 last message repeated 2 times
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=3
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 last message repeated 4 times
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 last message repeated 8 times
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=9
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 last message repeated 4 times
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 last message repeated 13 times
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=13
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 last message repeated 26 times
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=27
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 last message repeated 14 times
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=15
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 last message repeated 37 times
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=37
Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:14 lab1 last message repeated 34 times
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=33
Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=0
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 2 times
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=3
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 4 times
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 8 times
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=9
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 4 times
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 3 times
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 3 times
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=14
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 14 times
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 9 times
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=26
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 14 times
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=15
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 11 times
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 5 times
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 12 times
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 5 times
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=41
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 17 times
Nov 23 14:57:15 lab1 kernel: 
Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:15 lab1 last message repeated 12 times
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=29
Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=0
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 last message repeated 2 times
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=3
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 last message repeated 7 times
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=8
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 last message repeated 5 times
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 last message repeated 4 times
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=5
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 last message repeated 23 times
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=23
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 last message repeated 16 times
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=17
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 last message repeated 14 times
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=15
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 last message repeated 68 times
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64
Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:16 lab1 last message repeated 4 times
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=0
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 kernel: ucom_get_data:1064: cnt=1
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 last message repeated 135 times
Nov 23 14:57:18 lab1 kernel: 
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 kernel: 
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 last message repeated 9 times
Nov 23 14:57:18 lab1 kernel: 
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 kernel: 
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 kernel: 
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 last message repeated 3 times
Nov 23 14:57:18 lab1 kernel: 
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 kernel: 
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 kernel: 
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:18 lab1 kernel: 
Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:39 lab1 last message repeated 1307 times
Nov 23 14:57:39 lab1 kernel: 
Nov 23 14:57:39 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:42 lab1 last message repeated 212 times
Nov 23 14:57:43 lab1 kernel: 
Nov 23 14:57:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:45 lab1 last message repeated 187 times
Nov 23 14:57:46 lab1 kernel: 
Nov 23 14:57:46 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:57:58 lab1 last message repeated 801 times
Nov 23 14:57:58 lab1 kernel: 
Nov 23 14:57:58 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:58:29 lab1 last message repeated 1891 times
Nov 23 14:58:29 lab1 last message repeated 50 times
Nov 23 14:58:29 lab1 kernel: 
Nov 23 14:58:29 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:58:55 lab1 last message repeated 1640 times
Nov 23 14:58:56 lab1 kernel: 
Nov 23 14:58:56 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:59:27 lab1 last message repeated 1940 times
Nov 23 14:59:43 lab1 last message repeated 1051 times
Nov 23 14:59:43 lab1 kernel: 
Nov 23 14:59:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 14:59:57 lab1 last message repeated 825 times
Nov 23 14:59:57 lab1 kernel: 
Nov 23 14:59:57 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
Nov 23 15:00:00 lab1 newsyslog[926]: logfile turned over due to size>100K
Nov 23 15:00:00 lab1 last message repeated 208 times

I believe the problem occurs whenever you see a message like this:
Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64

>From a look at the code it looks like the largest uftdi frame is 64 characters (UFTDI_[IO]BUFSIZE in uftdi.c).  Perhaps it is an off by one bug?

-Corey Smith


From csmith at bonddesk.com  Mon Nov 23 19:20:07 2009
From: csmith at bonddesk.com (Corey Smith)
Date: Mon Nov 23 19:20:14 2009
Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
Message-ID: <200911231920.nANJK7rA038529@freefall.freebsd.org>

The following reply was made to PR usb/140810; it has been noted by GNATS.

From: Corey Smith <csmith@bonddesk.com>
To: Hans Petter Selasky <hselasky@c2i.net>
Cc: "freebsd-usb@freebsd.org" <freebsd-usb@freebsd.org>,
	"freebsd-gnats-submit@freebsd.org" <freebsd-gnats-submit@freebsd.org>
Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
Date: Mon, 23 Nov 2009 13:59:56 -0500

 On Mon, 2009-11-23 at 11:25 -0500, Hans Petter Selasky wrote:
 > sysctl hw.usb.ucom.debug=15
 
 Thanks for the quick reply.  I decided to do a fresh install of
 8.0-RELEASE amd64 before I re-ran the test.  Here are the details:
 
 # uname -a
 FreeBSD lab1 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009     root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
 # sysctl hw.usb.ucom.debug=15
 # tip ucom1
 connected
 # paste 160 "a"s followed by a newline (may take several attempts when debugging is enabled)
 aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
 
 Nov 23 14:54:13 lab1 su: csmith to root on /dev/pts/0
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 last message repeated 2 times
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=3
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 last message repeated 4 times
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 last message repeated 8 times
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=9
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 last message repeated 4 times
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 last message repeated 13 times
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=13
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 last message repeated 26 times
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=27
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 last message repeated 14 times
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=15
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 last message repeated 37 times
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=37
 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:14 lab1 last message repeated 34 times
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=33
 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=0
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 2 times
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=3
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 4 times
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 8 times
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=9
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 4 times
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 3 times
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 3 times
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=14
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 14 times
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 9 times
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=26
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 14 times
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=15
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 11 times
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 5 times
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 12 times
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 5 times
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=41
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 17 times
 Nov 23 14:57:15 lab1 kernel: 
 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:15 lab1 last message repeated 12 times
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=29
 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=0
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 last message repeated 2 times
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=3
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 last message repeated 7 times
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=8
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 last message repeated 5 times
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 last message repeated 4 times
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=5
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 last message repeated 23 times
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=23
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 last message repeated 16 times
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=17
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 last message repeated 14 times
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=15
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 last message repeated 68 times
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64
 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:16 lab1 last message repeated 4 times
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=0
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 kernel: ucom_get_data:1064: cnt=1
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 last message repeated 135 times
 Nov 23 14:57:18 lab1 kernel: 
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 kernel: 
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 last message repeated 9 times
 Nov 23 14:57:18 lab1 kernel: 
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 kernel: 
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 kernel: 
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 last message repeated 3 times
 Nov 23 14:57:18 lab1 kernel: 
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 kernel: 
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 kernel: 
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:18 lab1 kernel: 
 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:39 lab1 last message repeated 1307 times
 Nov 23 14:57:39 lab1 kernel: 
 Nov 23 14:57:39 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:42 lab1 last message repeated 212 times
 Nov 23 14:57:43 lab1 kernel: 
 Nov 23 14:57:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:45 lab1 last message repeated 187 times
 Nov 23 14:57:46 lab1 kernel: 
 Nov 23 14:57:46 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:57:58 lab1 last message repeated 801 times
 Nov 23 14:57:58 lab1 kernel: 
 Nov 23 14:57:58 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:58:29 lab1 last message repeated 1891 times
 Nov 23 14:58:29 lab1 last message repeated 50 times
 Nov 23 14:58:29 lab1 kernel: 
 Nov 23 14:58:29 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:58:55 lab1 last message repeated 1640 times
 Nov 23 14:58:56 lab1 kernel: 
 Nov 23 14:58:56 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:59:27 lab1 last message repeated 1940 times
 Nov 23 14:59:43 lab1 last message repeated 1051 times
 Nov 23 14:59:43 lab1 kernel: 
 Nov 23 14:59:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 14:59:57 lab1 last message repeated 825 times
 Nov 23 14:59:57 lab1 kernel: 
 Nov 23 14:59:57 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 Nov 23 15:00:00 lab1 newsyslog[926]: logfile turned over due to size>100K
 Nov 23 15:00:00 lab1 last message repeated 208 times
 
 I believe the problem occurs whenever you see a message like this:
 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64
 
 >From a look at the code it looks like the largest uftdi frame is 64 characters (UFTDI_[IO]BUFSIZE in uftdi.c).  Perhaps it is an off by one bug?
 
 -Corey Smith
 
 
From hselasky at c2i.net  Mon Nov 23 20:59:46 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Nov 23 20:59:53 2009
Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
In-Reply-To: <1259002796.16068.110.camel@csmith-desktop.bdg.local>
References: <200911231545.nANFjs2W091289@www.freebsd.org>
	<200911231725.20787.hselasky@c2i.net>
	<1259002796.16068.110.camel@csmith-desktop.bdg.local>
Message-ID: <200911232201.15414.hselasky@c2i.net>

On Monday 23 November 2009 19:59:56 Corey Smith wrote:
> On Mon, 2009-11-23 at 11:25 -0500, Hans Petter Selasky wrote:
> > sysctl hw.usb.ucom.debug=15
>
> Thanks for the quick reply.  I decided to do a fresh install of
> 8.0-RELEASE amd64 before I re-ran the test.  Here are the details:
>
> # uname -a
> FreeBSD lab1 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC
> 2009     root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64 #
> sysctl hw.usb.ucom.debug=15
> # tip ucom1
> connected
> # paste 160 "a"s followed by a newline (may take several attempts when
> debugging is enabled)
> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>aaaaaaaa
>
> Nov 23 14:54:13 lab1 su: csmith to root on /dev/pts/0
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 last message repeated 2 times
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=3
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 last message repeated 4 times
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 last message repeated 8 times
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=9
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 last message repeated 4 times
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 last message repeated 13 times
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=13
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 last message repeated 26 times
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=27
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 last message repeated 14 times
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=15
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 last message repeated 37 times
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=37
> Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:14 lab1 last message repeated 34 times
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=33
> Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=0
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 2 times
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=3
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 4 times
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 8 times
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=9
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 4 times
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 3 times
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 3 times
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=14
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 14 times
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 9 times
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=26
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 14 times
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=15
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 11 times
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 5 times
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 12 times
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 5 times
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=41
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 17 times
> Nov 23 14:57:15 lab1 kernel:
> Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:15 lab1 last message repeated 12 times
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=29
> Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=0
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 last message repeated 2 times
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=3
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 last message repeated 7 times
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=8
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 last message repeated 5 times
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 last message repeated 4 times
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=5
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 last message repeated 23 times
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=23
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 last message repeated 16 times
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=17
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 last message repeated 14 times
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=15
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 last message repeated 68 times
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64
> Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:16 lab1 last message repeated 4 times
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=0
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 kernel: ucom_get_data:1064: cnt=1
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 last message repeated 135 times
> Nov 23 14:57:18 lab1 kernel:
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 kernel:
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 last message repeated 9 times
> Nov 23 14:57:18 lab1 kernel:
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 kernel:
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 kernel:
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 last message repeated 3 times
> Nov 23 14:57:18 lab1 kernel:
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 kernel:
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 kernel:
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:18 lab1 kernel:
> Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:39 lab1 last message repeated 1307 times
> Nov 23 14:57:39 lab1 kernel:
> Nov 23 14:57:39 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:42 lab1 last message repeated 212 times
> Nov 23 14:57:43 lab1 kernel:
> Nov 23 14:57:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:45 lab1 last message repeated 187 times
> Nov 23 14:57:46 lab1 kernel:
> Nov 23 14:57:46 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:57:58 lab1 last message repeated 801 times
> Nov 23 14:57:58 lab1 kernel:
> Nov 23 14:57:58 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:58:29 lab1 last message repeated 1891 times
> Nov 23 14:58:29 lab1 last message repeated 50 times
> Nov 23 14:58:29 lab1 kernel:
> Nov 23 14:58:29 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:58:55 lab1 last message repeated 1640 times
> Nov 23 14:58:56 lab1 kernel:
> Nov 23 14:58:56 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:59:27 lab1 last message repeated 1940 times
> Nov 23 14:59:43 lab1 last message repeated 1051 times
> Nov 23 14:59:43 lab1 kernel:
> Nov 23 14:59:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 14:59:57 lab1 last message repeated 825 times
> Nov 23 14:59:57 lab1 kernel:
> Nov 23 14:59:57 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
> Nov 23 15:00:00 lab1 newsyslog[926]: logfile turned over due to size>100K
> Nov 23 15:00:00 lab1 last message repeated 208 times
>
> I believe the problem occurs whenever you see a message like this:
> Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64
>
> >From a look at the code it looks like the largest uftdi frame is 64
> > characters (UFTDI_[IO]BUFSIZE in uftdi.c).  Perhaps it is an off by one
> > bug?
>
> -Corey Smith

Hi,

Your issue looks like a hardware issue. Does the following patch help?

==== //depot/projects/usb/src/sys/dev/usb/serial/uftdi.c#16 - 
src/sys/dev/usb/serial/uftdi.c ====
@@ -165,7 +165,7 @@
                .endpoint = UE_ADDR_ANY,
                .direction = UE_DIR_OUT,
                .bufsize = UFTDI_OBUFSIZE,
-               .flags = {.pipe_bof = 1,.force_short_xfer = 1,},
+               .flags = {.pipe_bof = 1,},
                .callback = &uftdi_write_callback,
        },

From hselasky at c2i.net  Mon Nov 23 21:00:22 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Nov 23 21:00:29 2009
Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
Message-ID: <200911232100.nANL0L8t023101@freefall.freebsd.org>

The following reply was made to PR usb/140810; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: Corey Smith <csmith@bonddesk.com>
Cc: "freebsd-usb@freebsd.org" <freebsd-usb@freebsd.org>,
 "freebsd-gnats-submit@freebsd.org" <freebsd-gnats-submit@freebsd.org>
Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
Date: Mon, 23 Nov 2009 22:01:12 +0100

 On Monday 23 November 2009 19:59:56 Corey Smith wrote:
 > On Mon, 2009-11-23 at 11:25 -0500, Hans Petter Selasky wrote:
 > > sysctl hw.usb.ucom.debug=15
 >
 > Thanks for the quick reply.  I decided to do a fresh install of
 > 8.0-RELEASE amd64 before I re-ran the test.  Here are the details:
 >
 > # uname -a
 > FreeBSD lab1 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC
 > 2009     root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64 #
 > sysctl hw.usb.ucom.debug=15
 > # tip ucom1
 > connected
 > # paste 160 "a"s followed by a newline (may take several attempts when
 > debugging is enabled)
 > aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
 >aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
 >aaaaaaaa
 >
 > Nov 23 14:54:13 lab1 su: csmith to root on /dev/pts/0
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 last message repeated 2 times
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=3
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 last message repeated 4 times
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 last message repeated 8 times
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=9
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 last message repeated 4 times
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 last message repeated 13 times
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=13
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 last message repeated 26 times
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=27
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 last message repeated 14 times
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=15
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 last message repeated 37 times
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=37
 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:14 lab1 last message repeated 34 times
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=33
 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=0
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 2 times
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=3
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 4 times
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 8 times
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=9
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 4 times
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 3 times
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 3 times
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=14
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 14 times
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 9 times
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=26
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 14 times
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=15
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 11 times
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 5 times
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 12 times
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 5 times
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=41
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 17 times
 > Nov 23 14:57:15 lab1 kernel:
 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:15 lab1 last message repeated 12 times
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=29
 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=0
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 last message repeated 2 times
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=3
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 last message repeated 7 times
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=8
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 last message repeated 5 times
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 last message repeated 4 times
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=5
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 last message repeated 23 times
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=23
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 last message repeated 16 times
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=17
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 last message repeated 14 times
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=15
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 last message repeated 68 times
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64
 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:16 lab1 last message repeated 4 times
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=0
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 kernel: ucom_get_data:1064: cnt=1
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 last message repeated 135 times
 > Nov 23 14:57:18 lab1 kernel:
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 kernel:
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 last message repeated 9 times
 > Nov 23 14:57:18 lab1 kernel:
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 kernel:
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 kernel:
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 last message repeated 3 times
 > Nov 23 14:57:18 lab1 kernel:
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 kernel:
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 kernel:
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:18 lab1 kernel:
 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:39 lab1 last message repeated 1307 times
 > Nov 23 14:57:39 lab1 kernel:
 > Nov 23 14:57:39 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:42 lab1 last message repeated 212 times
 > Nov 23 14:57:43 lab1 kernel:
 > Nov 23 14:57:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:45 lab1 last message repeated 187 times
 > Nov 23 14:57:46 lab1 kernel:
 > Nov 23 14:57:46 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:57:58 lab1 last message repeated 801 times
 > Nov 23 14:57:58 lab1 kernel:
 > Nov 23 14:57:58 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:58:29 lab1 last message repeated 1891 times
 > Nov 23 14:58:29 lab1 last message repeated 50 times
 > Nov 23 14:58:29 lab1 kernel:
 > Nov 23 14:58:29 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:58:55 lab1 last message repeated 1640 times
 > Nov 23 14:58:56 lab1 kernel:
 > Nov 23 14:58:56 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:59:27 lab1 last message repeated 1940 times
 > Nov 23 14:59:43 lab1 last message repeated 1051 times
 > Nov 23 14:59:43 lab1 kernel:
 > Nov 23 14:59:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 14:59:57 lab1 last message repeated 825 times
 > Nov 23 14:59:57 lab1 kernel:
 > Nov 23 14:59:57 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858
 > Nov 23 15:00:00 lab1 newsyslog[926]: logfile turned over due to size>100K
 > Nov 23 15:00:00 lab1 last message repeated 208 times
 >
 > I believe the problem occurs whenever you see a message like this:
 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64
 >
 > >From a look at the code it looks like the largest uftdi frame is 64
 > > characters (UFTDI_[IO]BUFSIZE in uftdi.c).  Perhaps it is an off by one
 > > bug?
 >
 > -Corey Smith
 
 Hi,
 
 Your issue looks like a hardware issue. Does the following patch help?
 
 ==== //depot/projects/usb/src/sys/dev/usb/serial/uftdi.c#16 - 
 src/sys/dev/usb/serial/uftdi.c ====
 @@ -165,7 +165,7 @@
                 .endpoint = UE_ADDR_ANY,
                 .direction = UE_DIR_OUT,
                 .bufsize = UFTDI_OBUFSIZE,
 -               .flags = {.pipe_bof = 1,.force_short_xfer = 1,},
 +               .flags = {.pipe_bof = 1,},
                 .callback = &uftdi_write_callback,
         },
 
From hselasky at c2i.net  Mon Nov 23 21:36:46 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Nov 23 21:36:53 2009
Subject: USB mouse not working on 8.0-RELEASE
In-Reply-To: <f60d361f0911231004i4a8aa4c1ma9aa9d164ef327e2@mail.gmail.com>
References: <f60d361f0911231004i4a8aa4c1ma9aa9d164ef327e2@mail.gmail.com>
Message-ID: <200911232238.19592.hselasky@c2i.net>

On Monday 23 November 2009 19:04:22 Ond?ej Majerech wrote:
> Hello,
>
> I've just upgraded my box to 8.0-RELEASE (FreeBSD starlight
> 8.0-RELEASE FreeBSD 8.0-RELEASE #9: Mon Nov 23 17:52:12 CET 2009
> root@starlight:/usr/obj/usr/src/sys/STARLIGHT  i386) via csup'ing to
> RELENG_8_0 and the usual suite of buildworld, buildkernel,
> installkernel, mergemaster -p, installworld, mergemaster.
>
> My USB mouse doesn't work now.  While booting, I can see error
> messages from the USB part of the kernel; the same messages also
> reappear when I disconnect and reconnect the thing.  They read the
> following: (Grabbed from /var/log/messages after having dis- and
> re-connected the mouse.)
>
> Nov 23 18:54:19 starlight kernel: usb_alloc_device:1586: set address 2
> failed (USB_ERR_TIMEOUT, ignored)
> Nov 23 18:54:20 starlight kernel: usb_alloc_device:1624: getting
> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
> Nov 23 18:54:21 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
> set address failed! (USB_ERR_TIMEOUT, ignored)
> Nov 23 18:54:22 starlight kernel: usbd_req_re_enumerate:1553: getting
> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
> Nov 23 18:54:24 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
> set address failed! (USB_ERR_TIMEOUT, ignored)
> Nov 23 18:54:25 starlight kernel: usbd_req_re_enumerate:1553: getting
> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
> Nov 23 18:54:25 starlight kernel: ugen0.2: <(null)> at usbus0
> (disconnected) Nov 23 18:54:25 starlight kernel: uhub_reattach_port:435:
> could not allocate new device!
>
> The mouse was working without any problems whatsoever on 8.0-RC3 and
> all older FBSD versions that I used.
>
> Other USB devices work as they should, without producing anything
> unusual in dmesg.
>
> So, what's up?  Any clues?

Hi,

This looks like a regression issue. There has been some changes with regard to 
USB legacy support handling. Try disabling USB legacy support in the BIOS or 
try to see if the problem is present in a 9-current kernel.

Thanks for reporting your issue!

--HPS

From csmith at bonddesk.com  Mon Nov 23 22:05:47 2009
From: csmith at bonddesk.com (Corey Smith)
Date: Mon Nov 23 22:05:53 2009
Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
In-Reply-To: <200911232201.15414.hselasky@c2i.net>
References: <200911231545.nANFjs2W091289@www.freebsd.org>
	<200911231725.20787.hselasky@c2i.net>
	<1259002796.16068.110.camel@csmith-desktop.bdg.local>
	<200911232201.15414.hselasky@c2i.net>
Message-ID: <1259013867.16068.116.camel@csmith-desktop.bdg.local>

On Mon, 2009-11-23 at 16:01 -0500, Hans Petter Selasky wrote:
> Your issue looks like a hardware issue. Does the following patch help?
> 
> ==== //depot/projects/usb/src/sys/dev/usb/serial/uftdi.c#16 -
> src/sys/dev/usb/serial/uftdi.c ====
> @@ -165,7 +165,7 @@
>                 .endpoint = UE_ADDR_ANY,
>                 .direction = UE_DIR_OUT,
>                 .bufsize = UFTDI_OBUFSIZE,
> -               .flags = {.pipe_bof = 1,.force_short_xfer = 1,},
> +               .flags = {.pipe_bof = 1,},
>                 .callback = &uftdi_write_callback,
>         },
> 

Your patch worked.

FWIW: This patch also works:

# diff -u sys/dev/usb/serial/uftdi.c.orig sys/dev/usb/serial/uftdi.c
--- sys/dev/usb/serial/uftdi.c.orig	2009-11-23 16:48:01.000000000 -0500
+++ sys/dev/usb/serial/uftdi.c	2009-11-23 17:54:23.000000000 -0500
@@ -93,7 +93,7 @@
 
 #define	UFTDI_IBUFSIZE 64		/* bytes, maximum number of bytes per
 					 * frame */
-#define	UFTDI_OBUFSIZE 64		/* bytes, cannot be increased due to
+#define	UFTDI_OBUFSIZE 63		/* bytes, cannot be increased due to
 					 * do size encoding */
 
 enum {

Is there a way to fix this so USB-16COM-RM will work properly in a -RELEASE again?

-Corey Smith

From csmith at bonddesk.com  Mon Nov 23 22:10:09 2009
From: csmith at bonddesk.com (Corey Smith)
Date: Mon Nov 23 22:10:34 2009
Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
Message-ID: <200911232210.nANMA8cc063848@freefall.freebsd.org>

The following reply was made to PR usb/140810; it has been noted by GNATS.

From: Corey Smith <csmith@bonddesk.com>
To: Hans Petter Selasky <hselasky@c2i.net>
Cc: "freebsd-usb@freebsd.org" <freebsd-usb@freebsd.org>,
	"freebsd-gnats-submit@freebsd.org" <freebsd-gnats-submit@freebsd.org>
Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
Date: Mon, 23 Nov 2009 17:04:27 -0500

 On Mon, 2009-11-23 at 16:01 -0500, Hans Petter Selasky wrote:
 > Your issue looks like a hardware issue. Does the following patch help?
 > 
 > ==== //depot/projects/usb/src/sys/dev/usb/serial/uftdi.c#16 -
 > src/sys/dev/usb/serial/uftdi.c ====
 > @@ -165,7 +165,7 @@
 >                 .endpoint = UE_ADDR_ANY,
 >                 .direction = UE_DIR_OUT,
 >                 .bufsize = UFTDI_OBUFSIZE,
 > -               .flags = {.pipe_bof = 1,.force_short_xfer = 1,},
 > +               .flags = {.pipe_bof = 1,},
 >                 .callback = &uftdi_write_callback,
 >         },
 > 
 
 Your patch worked.
 
 FWIW: This patch also works:
 
 # diff -u sys/dev/usb/serial/uftdi.c.orig sys/dev/usb/serial/uftdi.c
 --- sys/dev/usb/serial/uftdi.c.orig	2009-11-23 16:48:01.000000000 -0500
 +++ sys/dev/usb/serial/uftdi.c	2009-11-23 17:54:23.000000000 -0500
 @@ -93,7 +93,7 @@
  
  #define	UFTDI_IBUFSIZE 64		/* bytes, maximum number of bytes per
  					 * frame */
 -#define	UFTDI_OBUFSIZE 64		/* bytes, cannot be increased due to
 +#define	UFTDI_OBUFSIZE 63		/* bytes, cannot be increased due to
  					 * do size encoding */
  
  enum {
 
 Is there a way to fix this so USB-16COM-RM will work properly in a -RELEASE again?
 
 -Corey Smith
 
From oxyd.oxyd at gmail.com  Mon Nov 23 22:18:08 2009
From: oxyd.oxyd at gmail.com (=?UTF-8?Q?Ond=C5=99ej_Majerech?=)
Date: Mon Nov 23 22:18:15 2009
Subject: USB mouse not working on 8.0-RELEASE
In-Reply-To: <200911232238.19592.hselasky@c2i.net>
References: <f60d361f0911231004i4a8aa4c1ma9aa9d164ef327e2@mail.gmail.com>
	<200911232238.19592.hselasky@c2i.net>
Message-ID: <f60d361f0911231418p1503194duaae4cad98aeb754b@mail.gmail.com>

2009/11/23 Hans Petter Selasky <hselasky@c2i.net>:
> On Monday 23 November 2009 19:04:22 Ond?ej Majerech wrote:
>> Hello,
>>
>> I've just upgraded my box to 8.0-RELEASE (FreeBSD starlight
>> 8.0-RELEASE FreeBSD 8.0-RELEASE #9: Mon Nov 23 17:52:12 CET 2009
>> root@starlight:/usr/obj/usr/src/sys/STARLIGHT ?i386) via csup'ing to
>> RELENG_8_0 and the usual suite of buildworld, buildkernel,
>> installkernel, mergemaster -p, installworld, mergemaster.
>>
>> My USB mouse doesn't work now. ?While booting, I can see error
>> messages from the USB part of the kernel; the same messages also
>> reappear when I disconnect and reconnect the thing. ?They read the
>> following: (Grabbed from /var/log/messages after having dis- and
>> re-connected the mouse.)
>>
>> Nov 23 18:54:19 starlight kernel: usb_alloc_device:1586: set address 2
>> failed (USB_ERR_TIMEOUT, ignored)
>> Nov 23 18:54:20 starlight kernel: usb_alloc_device:1624: getting
>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
>> Nov 23 18:54:21 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
>> set address failed! (USB_ERR_TIMEOUT, ignored)
>> Nov 23 18:54:22 starlight kernel: usbd_req_re_enumerate:1553: getting
>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
>> Nov 23 18:54:24 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
>> set address failed! (USB_ERR_TIMEOUT, ignored)
>> Nov 23 18:54:25 starlight kernel: usbd_req_re_enumerate:1553: getting
>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
>> Nov 23 18:54:25 starlight kernel: ugen0.2: <(null)> at usbus0
>> (disconnected) Nov 23 18:54:25 starlight kernel: uhub_reattach_port:435:
>> could not allocate new device!
>>
>> The mouse was working without any problems whatsoever on 8.0-RC3 and
>> all older FBSD versions that I used.
>>
>> Other USB devices work as they should, without producing anything
>> unusual in dmesg.
>>
>> So, what's up? ?Any clues?
>
> Hi,
>
> This looks like a regression issue. There has been some changes with regard to
> USB legacy support handling. Try disabling USB legacy support in the BIOS or
> try to see if the problem is present in a 9-current kernel.
>
> Thanks for reporting your issue!
>
> --HPS
>
>

The only option in my BIOS regarding legacy USB is "Legacy USB storage
detect" -- I set this one to Disabled and booted with the mouse
disabled -- when I connected it to the running system, it got detected
properly, but it simply wouldn't work in X.

When I rebooted with the mouse plugged in, the same thing as before
happened -- error messages during boot, and un- and re-plugging
produced the same errors.

I'll try 9-CURRENT sometime tomorrow and report back how that turned out.

~ Ondra
From hselasky at c2i.net  Mon Nov 23 22:22:03 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Nov 23 22:22:09 2009
Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
In-Reply-To: <1259013867.16068.116.camel@csmith-desktop.bdg.local>
References: <200911231545.nANFjs2W091289@www.freebsd.org>
	<200911232201.15414.hselasky@c2i.net>
	<1259013867.16068.116.camel@csmith-desktop.bdg.local>
Message-ID: <200911232323.37784.hselasky@c2i.net>

On Monday 23 November 2009 23:04:27 Corey Smith wrote:
> Corey Smith

Hi,

I've committed your patch to USB P4. Should end up in 8+9-current soon.

http://p4web.freebsd.org/chv.cgi?CH=170963

--HPS
From hselasky at c2i.net  Mon Nov 23 22:30:08 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Mon Nov 23 22:30:14 2009
Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
Message-ID: <200911232230.nANMU7sD092637@freefall.freebsd.org>

The following reply was made to PR usb/140810; it has been noted by GNATS.

From: Hans Petter Selasky <hselasky@c2i.net>
To: Corey Smith <csmith@bonddesk.com>,
 Andrew Thompson <thompsa@freebsd.org>
Cc: "freebsd-usb@freebsd.org" <freebsd-usb@freebsd.org>,
 "freebsd-gnats-submit@freebsd.org" <freebsd-gnats-submit@freebsd.org>
Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow
Date: Mon, 23 Nov 2009 23:23:36 +0100

 On Monday 23 November 2009 23:04:27 Corey Smith wrote:
 > Corey Smith
 
 Hi,
 
 I've committed your patch to USB P4. Should end up in 8+9-current soon.
 
 http://p4web.freebsd.org/chv.cgi?CH=170963
 
 --HPS
From 166162 at gmail.com  Tue Nov 24 00:08:15 2009
From: 166162 at gmail.com (Travelling Particle)
Date: Tue Nov 24 00:08:22 2009
Subject: [keyboard] ukbd stops working after filesystems mount at boot 
	time
In-Reply-To: <200911212300.20154.hselasky@c2i.net>
References: <da6b214d0911180425r2b720333r87fe2fb79e3e13e1@mail.gmail.com>
	<200911201224.08313.hselasky@c2i.net>
	<da6b214d0911211012he5b2bb7v701596976d2bd0ea@mail.gmail.com>
	<200911212300.20154.hselasky@c2i.net>
Message-ID: <da6b214d0911231608l18fb2ae0h5cab9420a5631923@mail.gmail.com>

> > > There was a recent EHCI interrupt patch. I'm not sure if it is committed to
> > > 9-current yet.

> > Do you mean there was a patch that might have caused this problem, or the
> > patch fixing this problem? Also, I'm on 8-RC3, not 9-CURRENT
> >
>
> I mean fixing.

Well, indeed there're changes, but they're not good for me. I've tried
to boot 8.0-RELEASE and keyboard appears to be dead when I need to
type the geli password at root mount. Sometimes it's possible to send
the passphrase by hitting Enter, but not every hit does so, and the
passphrase entered appears to be wrong. I suppose certain keypresses
are just dropped. Can't say much about empty lines interleaving the
output of the late stage, as that would be happening later, after root
fs is mounted.

Is there anything I can do to debug the problem or help? I'm back to
using RC3 now, since I can at least enter the passphrase and boot the
system.
From gjin at ubicom.com  Tue Nov 24 08:16:17 2009
From: gjin at ubicom.com (Guojun Jin)
Date: Tue Nov 24 08:16:31 2009
Subject: 8.0-RC USB/FS problem
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A23@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A26@STORK.scenix.com>
	<200911221047.20362.hselasky@c2i.net>
	<CB2DD11991B27C4F99935E6229450D3203950A27@STORK.scenix.com>
Message-ID: <CB2DD11991B27C4F99935E6229450D3203950A29@STORK.scenix.com>

Freshly installed 8.0-RELEASE on two differnt machines, and USB stick work well so far, but the USB hard drive
still has crash on this SMP (4-core AMD phenom 9600) during the dump/restore. I will try it on the single CPU
machine tomorrow.

Re-tested dump/restore with FreeBSD 6.3/6.4 on this SMP machine and they are working well.

Also the another strange thing ocurred during the mount a partition on /tmp, which ended with two /tmp,
and the last one mounted is on the top (the first should be hidden):

: df
Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
/dev/ad0s1a    756750   165484   530726    24%    /
devfs               1        1        0   100%    /dev
/dev/ad0s2e  43194318 27833648 11905126    70%    /data
/dev/ad0s2d   9135182  5870390  2533978    70%    /home
/dev/ad0s1e    507630    34882   432138     7%    /tmp
/dev/ad0s1f  13246730  1424522 10762470    12%    /usr
/dev/ad0s1d   5077038    12700  4658176     0%    /var
/dev/da0s2     661176   487660   120622    80%    /mnt
/dev/da1s3d   9135182        4  8404364     0%    /dist
/dev/da1s3e  74938948        4 68943830     0%    /tmp

: df /tmp
Filesystem  1K-blocks Used    Avail Capacity  Mounted on
/dev/da1s3e  74938948    4 68943830     0%    /tmp

-----Original Message-----
From: Guojun Jin
Sent: Sun 11/22/2009 7:59 PM
To: Hans Petter Selasky; freebsd-usb@freebsd.org
Cc: bugs@freebsd.org; freebsd-stable@freebsd.org
Subject: RE: 8.0-RC USB/FS problem
 
>From more intensive diagnose, it looks like more related USB layer.

repeated a few time on following process and ithe crash happened at different USB access phase at each time.

dd if=/dev/zero of=/dev/da0 count=1000 bs=4k
sysinstall
        partition 
             slice 1 (da0s1) 18GB ID=12
             slice 2 (da0s2) 10-15GB Id=165
             slice 3 (da0s3) rest ID=165
         W ---> OK
        label
             da0s3d 9GB         /mnt
             da0s3e rest        /dist
         W ---> da0s3e ---- device is not configured.

w# ll /dev/da0*      # after sysinstall did partition + W at 1st time
crw-r-----  1 root  operator    0,  97 Nov 22 11:23 /dev/da0
crw-r-----  1 root  operator    0,  98 Nov 22 11:23 /dev/da0s1
crw-r-----  1 root  operator    0,  99 Nov 22 11:23 /dev/da0s2
crw-r-----  1 root  operator    0, 100 Nov 22 11:23 /dev/da0s3

# ll /dev/da0*      # after sysinstall start at 2nd time
crw-r-----  1 root  operator    0,  97 Nov 22 11:27 /dev/da0
System crashed

The crash log is available at http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2
(All logs are based on hw.usb.umass.debug=-1)

After system reboot, and repeated above processes, the da0s3e was mounted on /dist, but da0s3d cannot.
It tunred out that newfs fail inside labeling process in sysinstall. Manually did newfs on da0s3d, and
it cannot be mounted on /mnt, but access to it caused crash.
The crash log is available at http:/www.daemonfun.com/archives/pub/USB/newfs

Tried entire process again, this time, both partitons are formatted (newfs) inside labaling process (sysinstall)
but crahsed system during dump/restore on da0s3e (/dist).
The crash log is available at http:/www.daemonfun.com/archives/pub/USB/usb-log.crash2.bz2, which is huge one.
It contains two parts, one dump/restore IDE to da0s3d (passed), and the rest is dump/restore to da0s3e (crashed).

I am going to reinstall the system with the new ISO from Nov 21 8.0-RELEASE to see if anything will improve.

-----Original Message-----
From: Hans Petter Selasky [mailto:hselasky@c2i.net]
Sent: Sun 11/22/2009 1:47 AM
To: freebsd-usb@freebsd.org
Cc: Guojun Jin; bugs@freebsd.org; freebsd-stable@freebsd.org
Subject: Re: 8.0-RC USB/FS problem
 
On Sunday 22 November 2009 05:38:13 Guojun Jin wrote:
> Tried on the USB hard drive:
>
> Deleted slice 3 and recreated slice 3 with two partitions s3d and s3e.
> Was happy because successfully did dump/restore on s3d, and thought it just
> partition format issue; but system crashed during dump/restore on s3e, and
> partition lost the file system type.
>
> wolf# mount /dev/da0s3e /mnt
> WARNING: /mnt was not properly dismounted
> /mnt: mount pending error: blocks 35968 files 0
> wolf# fsck da0s3e
> fsck: Could not determine filesystem type
> wolf# bsdlabel da0s3
> # /dev/da0s3:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>   c: 175735035        0    unused        0     0         # "raw" part,
> don't edi t
>   d: 18874368        0    4.2BSD        0     0     0
>   e: 156860667 18874368    4.2BSD        0     0     0
>
> Therefore, tried directly use fsck_ufs on both USB hard drive and USB stick
> to get file system clean up. All data got back now.
>
> The machine has run with FreeBSD 6.1 all the way to 7.2 without such
> problem. How can we determine what could go wrong in 8.0? FS or USB.

Hi,

Error 5 means IO error, so probably the transport layer, USB or lower, is to 
blame.

Some things to check:

1) Make sure the connection for your memory stick is Ok.
2) Make sure there is enough power for your memory stick.

Regarding memory sticks:

Other operating systems do a port bus reset when the device has a problem. On 
FreeBSD we just try a software reset via the control endpoint. I guess that it 
is a device problem you are seeing. The USB stack in FreeBSD is faster than 
the old one, and maybe the faster queueing of mass storage requests trigger 
some hidden bugs in your device.

When the problem happens try:

sysctl hw.usb.umass.debug=-1

--HPS


From hselasky at c2i.net  Tue Nov 24 08:31:44 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Nov 24 08:32:01 2009
Subject: 8.0-RC USB/FS problem
In-Reply-To: <CB2DD11991B27C4F99935E6229450D3203950A29@STORK.scenix.com>
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A27@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A29@STORK.scenix.com>
Message-ID: <200911240933.19329.hselasky@c2i.net>

On Tuesday 24 November 2009 09:12:45 Guojun Jin wrote:
> http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2

I'm not able to fetch this file. Could you extract the panic backtrace?

--HPS
From gjin at ubicom.com  Tue Nov 24 17:09:03 2009
From: gjin at ubicom.com (Guojun Jin)
Date: Tue Nov 24 17:09:16 2009
Subject: 8.0-RC USB/FS problem
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A27@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A29@STORK.scenix.com>
	<200911240933.19329.hselasky@c2i.net>
Message-ID: <CB2DD11991B27C4F99935E6229450D3203950A2A@STORK.scenix.com>

Sorry for the typo -- it is public not pub in the middle. The others should be all public.

http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2

-----Original Message-----
From: Hans Petter Selasky [mailto:hselasky@c2i.net]
Sent: Tue 11/24/2009 12:33 AM
To: Guojun Jin
Cc: freebsd-usb@freebsd.org; bugs@freebsd.org; freebsd-stable@freebsd.org
Subject: Re: 8.0-RC USB/FS problem
 
On Tuesday 24 November 2009 09:12:45 Guojun Jin wrote:
> http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2

I'm not able to fetch this file. Could you extract the panic backtrace?

--HPS

From hselasky at c2i.net  Tue Nov 24 17:11:54 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Nov 24 17:12:01 2009
Subject: 8.0-RC USB/FS problem
In-Reply-To: <CB2DD11991B27C4F99935E6229450D3203950A2A@STORK.scenix.com>
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<200911240933.19329.hselasky@c2i.net>
	<CB2DD11991B27C4F99935E6229450D3203950A2A@STORK.scenix.com>
Message-ID: <200911241813.23616.hselasky@c2i.net>

On Tuesday 24 November 2009 17:58:47 Guojun Jin wrote:
> Sorry for the typo -- it is public not pub in the middle. The others should
> be all public.
>
> http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2
>

%fetch http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2
fetch: http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2: No 
address record

--HPS

> -----Original Message-----
> From: Hans Petter Selasky [mailto:hselasky@c2i.net]
> Sent: Tue 11/24/2009 12:33 AM
> To: Guojun Jin
> Cc: freebsd-usb@freebsd.org; bugs@freebsd.org; freebsd-stable@freebsd.org
> Subject: Re: 8.0-RC USB/FS problem
>
> On Tuesday 24 November 2009 09:12:45 Guojun Jin wrote:
> > http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2
>
> I'm not able to fetch this file. Could you extract the panic backtrace?
>
> --HPS

From tevans.uk at googlemail.com  Tue Nov 24 17:53:26 2009
From: tevans.uk at googlemail.com (Tom Evans)
Date: Tue Nov 24 17:53:35 2009
Subject: 8.0-RC USB/FS problem
In-Reply-To: <200911241813.23616.hselasky@c2i.net>
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<200911240933.19329.hselasky@c2i.net>
	<CB2DD11991B27C4F99935E6229450D3203950A2A@STORK.scenix.com>
	<200911241813.23616.hselasky@c2i.net>
Message-ID: <2e027be00911240923q7b8e192dk1ad67346d2f7e4d4@mail.gmail.com>

On Tue, Nov 24, 2009 at 5:13 PM, Hans Petter Selasky <hselasky@c2i.net>wrote:

> On Tuesday 24 November 2009 17:58:47 Guojun Jin wrote:
> > Sorry for the typo -- it is public not pub in the middle. The others
> should
> > be all public.
> >
> > http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2
> >
>
> %fetch http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2
> fetch: http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2: No
> address record
>
>
You need two '/' for a URL :)

Try:

http://www.daemonfun.com/archives/public/USB/crash1-reset.bz2

Cheers

Tom
From oxyd.oxyd at gmail.com  Tue Nov 24 20:59:55 2009
From: oxyd.oxyd at gmail.com (=?UTF-8?Q?Ond=C5=99ej_Majerech?=)
Date: Tue Nov 24 21:00:02 2009
Subject: USB mouse not working on 8.0-RELEASE
In-Reply-To: <f60d361f0911231418p1503194duaae4cad98aeb754b@mail.gmail.com>
References: <f60d361f0911231004i4a8aa4c1ma9aa9d164ef327e2@mail.gmail.com>
	<200911232238.19592.hselasky@c2i.net>
	<f60d361f0911231418p1503194duaae4cad98aeb754b@mail.gmail.com>
Message-ID: <f60d361f0911241259pe43896dwa0912f323e3fee0f@mail.gmail.com>

2009/11/23 Ond?ej Majerech <oxyd.oxyd@gmail.com>:
> 2009/11/23 Hans Petter Selasky <hselasky@c2i.net>:
>> On Monday 23 November 2009 19:04:22 Ond?ej Majerech wrote:
>>> Hello,
>>>
>>> I've just upgraded my box to 8.0-RELEASE (FreeBSD starlight
>>> 8.0-RELEASE FreeBSD 8.0-RELEASE #9: Mon Nov 23 17:52:12 CET 2009
>>> root@starlight:/usr/obj/usr/src/sys/STARLIGHT ?i386) via csup'ing to
>>> RELENG_8_0 and the usual suite of buildworld, buildkernel,
>>> installkernel, mergemaster -p, installworld, mergemaster.
>>>
>>> My USB mouse doesn't work now. ?While booting, I can see error
>>> messages from the USB part of the kernel; the same messages also
>>> reappear when I disconnect and reconnect the thing. ?They read the
>>> following: (Grabbed from /var/log/messages after having dis- and
>>> re-connected the mouse.)
>>>
>>> Nov 23 18:54:19 starlight kernel: usb_alloc_device:1586: set address 2
>>> failed (USB_ERR_TIMEOUT, ignored)
>>> Nov 23 18:54:20 starlight kernel: usb_alloc_device:1624: getting
>>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
>>> Nov 23 18:54:21 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
>>> set address failed! (USB_ERR_TIMEOUT, ignored)
>>> Nov 23 18:54:22 starlight kernel: usbd_req_re_enumerate:1553: getting
>>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
>>> Nov 23 18:54:24 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
>>> set address failed! (USB_ERR_TIMEOUT, ignored)
>>> Nov 23 18:54:25 starlight kernel: usbd_req_re_enumerate:1553: getting
>>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
>>> Nov 23 18:54:25 starlight kernel: ugen0.2: <(null)> at usbus0
>>> (disconnected) Nov 23 18:54:25 starlight kernel: uhub_reattach_port:435:
>>> could not allocate new device!
>>>
>>> The mouse was working without any problems whatsoever on 8.0-RC3 and
>>> all older FBSD versions that I used.
>>>
>>> Other USB devices work as they should, without producing anything
>>> unusual in dmesg.
>>>
>>> So, what's up? ?Any clues?
>>
>> Hi,
>>
>> This looks like a regression issue. There has been some changes with regard to
>> USB legacy support handling. Try disabling USB legacy support in the BIOS or
>> try to see if the problem is present in a 9-current kernel.
>>
>> Thanks for reporting your issue!
>>
>> --HPS
>>
>>
>
> The only option in my BIOS regarding legacy USB is "Legacy USB storage
> detect" -- I set this one to Disabled and booted with the mouse
> disabled -- when I connected it to the running system, it got detected
> properly, but it simply wouldn't work in X.
>
> When I rebooted with the mouse plugged in, the same thing as before
> happened -- error messages during boot, and un- and re-plugging
> produced the same errors.
>
> I'll try 9-CURRENT sometime tomorrow and report back how that turned out.
>
> ~ Ondra
>

Alright, I tried with 9-CURRENT and indeed, it works without problems.

So, shall I file a bug?  I'd prefer to continue using -RELEASE, but
I'd also like to have my mouse working. x)

~ Ondra
From hselasky at c2i.net  Tue Nov 24 21:28:31 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Nov 24 21:28:38 2009
Subject: USB mouse not working on 8.0-RELEASE
In-Reply-To: <f60d361f0911241259pe43896dwa0912f323e3fee0f@mail.gmail.com>
References: <f60d361f0911231004i4a8aa4c1ma9aa9d164ef327e2@mail.gmail.com>
	<f60d361f0911231418p1503194duaae4cad98aeb754b@mail.gmail.com>
	<f60d361f0911241259pe43896dwa0912f323e3fee0f@mail.gmail.com>
Message-ID: <200911242230.05637.hselasky@c2i.net>

On Tuesday 24 November 2009 21:59:53 Ond?ej Majerech wrote:
> 2009/11/23 Ond?ej Majerech <oxyd.oxyd@gmail.com>:
> > 2009/11/23 Hans Petter Selasky <hselasky@c2i.net>:
> >> On Monday 23 November 2009 19:04:22 Ond?ej Majerech wrote:
> >>> Hello,
> >>>
> >>> I've just upgraded my box to 8.0-RELEASE (FreeBSD starlight
> >>> 8.0-RELEASE FreeBSD 8.0-RELEASE #9: Mon Nov 23 17:52:12 CET 2009
> >>> root@starlight:/usr/obj/usr/src/sys/STARLIGHT  i386) via csup'ing to
> >>> RELENG_8_0 and the usual suite of buildworld, buildkernel,
> >>> installkernel, mergemaster -p, installworld, mergemaster.
> >>>
> >>> My USB mouse doesn't work now.  While booting, I can see error
> >>> messages from the USB part of the kernel; the same messages also
> >>> reappear when I disconnect and reconnect the thing.  They read the
> >>> following: (Grabbed from /var/log/messages after having dis- and
> >>> re-connected the mouse.)
> >>>
> >>> Nov 23 18:54:19 starlight kernel: usb_alloc_device:1586: set address 2
> >>> failed (USB_ERR_TIMEOUT, ignored)
> >>> Nov 23 18:54:20 starlight kernel: usb_alloc_device:1624: getting
> >>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
> >>> Nov 23 18:54:21 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
> >>> set address failed! (USB_ERR_TIMEOUT, ignored)
> >>> Nov 23 18:54:22 starlight kernel: usbd_req_re_enumerate:1553: getting
> >>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
> >>> Nov 23 18:54:24 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
> >>> set address failed! (USB_ERR_TIMEOUT, ignored)
> >>> Nov 23 18:54:25 starlight kernel: usbd_req_re_enumerate:1553: getting
> >>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
> >>> Nov 23 18:54:25 starlight kernel: ugen0.2: <(null)> at usbus0
> >>> (disconnected) Nov 23 18:54:25 starlight kernel:
> >>> uhub_reattach_port:435: could not allocate new device!
> >>>
> >>> The mouse was working without any problems whatsoever on 8.0-RC3 and
> >>> all older FBSD versions that I used.
> >>>
> >>> Other USB devices work as they should, without producing anything
> >>> unusual in dmesg.
> >>>
> >>> So, what's up?  Any clues?
> >>
> >> Hi,
> >>
> >> This looks like a regression issue. There has been some changes with
> >> regard to USB legacy support handling. Try disabling USB legacy support
> >> in the BIOS or try to see if the problem is present in a 9-current
> >> kernel.
> >>
> >> Thanks for reporting your issue!
> >>
> >> --HPS
> >
> > The only option in my BIOS regarding legacy USB is "Legacy USB storage
> > detect" -- I set this one to Disabled and booted with the mouse
> > disabled -- when I connected it to the running system, it got detected
> > properly, but it simply wouldn't work in X.
> >
> > When I rebooted with the mouse plugged in, the same thing as before
> > happened -- error messages during boot, and un- and re-plugging
> > produced the same errors.
> >
> > I'll try 9-CURRENT sometime tomorrow and report back how that turned out.
> >
> > ~ Ondra
>
> Alright, I tried with 9-CURRENT and indeed, it works without problems.
>
> So, shall I file a bug?  I'd prefer to continue using -RELEASE, but
> I'd also like to have my mouse working. x)

Yes, file a bug report.

--HPS

From gjin at ubicom.com  Tue Nov 24 23:09:41 2009
From: gjin at ubicom.com (Guojun Jin)
Date: Tue Nov 24 23:09:54 2009
Subject: 8.0-RC USB/FS problem
In-Reply-To: <CB2DD11991B27C4F99935E6229450D3203950A29@STORK.scenix.com>
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A23@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A26@STORK.scenix.com>
	<200911221047.20362.hselasky@c2i.net>
	<CB2DD11991B27C4F99935E6229450D3203950A27@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A29@STORK.scenix.com>
Message-ID: <CB2DD11991B27C4F99935E6229450D3204E5C6A4@STORK.scenix.com>

Interesting now by some incident :-)

The single CPU machine (Intel P4) with 8.0 works fine on the USB drives
and the USB stick.

So, installed 8.0 on another AMD Turion64 HP Pavilion dv5210us Laptop,
it
comes the same problem -- accessing the USB hard drive causes system
panic
and reboot:

Took the previously dump/restored USB drive and mount it on this Laptop,
tried to remove the data before dump/restore, it crashed the system
after 
hit ^C and unplugged USB hard drive when the LED on USB hard drive
becomes
solid red and spiting out numbers of lines Operation not permitted 
(the user is root, so this means accessing hard drive is not possible):

rm: bin/... : Operation not permitted
......

A second try causes the system locks up After ^C.

So, try to re-partitioning the USB hard drive on AMD laptop and
dump/restore, partitioning passed, but dump/restore crashed.

Since hw.usb.umass.debug=-1 does not tell a USB problem beside the
RESET,
What other debug shall we turn on to analyze this problem.


-----Original Message-----
From: Guojun Jin 
Sent: Tuesday, November 24, 2009 12:13 AM
To: Guojun Jin; Hans Petter Selasky; freebsd-usb@freebsd.org
Cc: bugs@freebsd.org; freebsd-stable@freebsd.org
Subject: RE: 8.0-RC USB/FS problem

Freshly installed 8.0-RELEASE on two differnt machines, and USB stick
work well so far, but the USB hard drive
still has crash on this SMP (4-core AMD phenom 9600) during the
dump/restore. I will try it on the single CPU
machine tomorrow.

Re-tested dump/restore with FreeBSD 6.3/6.4 on this SMP machine and they
are working well.

Also the another strange thing ocurred during the mount a partition on
/tmp, which ended with two /tmp,
and the last one mounted is on the top (the first should be hidden):

: df
Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
/dev/ad0s1a    756750   165484   530726    24%    /
devfs               1        1        0   100%    /dev
/dev/ad0s2e  43194318 27833648 11905126    70%    /data
/dev/ad0s2d   9135182  5870390  2533978    70%    /home
/dev/ad0s1e    507630    34882   432138     7%    /tmp
/dev/ad0s1f  13246730  1424522 10762470    12%    /usr
/dev/ad0s1d   5077038    12700  4658176     0%    /var
/dev/da0s2     661176   487660   120622    80%    /mnt
/dev/da1s3d   9135182        4  8404364     0%    /dist
/dev/da1s3e  74938948        4 68943830     0%    /tmp

: df /tmp
Filesystem  1K-blocks Used    Avail Capacity  Mounted on
/dev/da1s3e  74938948    4 68943830     0%    /tmp

-----Original Message-----
From: Guojun Jin
Sent: Sun 11/22/2009 7:59 PM
To: Hans Petter Selasky; freebsd-usb@freebsd.org
Cc: bugs@freebsd.org; freebsd-stable@freebsd.org
Subject: RE: 8.0-RC USB/FS problem
 
>From more intensive diagnose, it looks like more related USB layer.

repeated a few time on following process and ithe crash happened at
different USB access phase at each time.

dd if=/dev/zero of=/dev/da0 count=1000 bs=4k
sysinstall
        partition 
             slice 1 (da0s1) 18GB ID=12
             slice 2 (da0s2) 10-15GB Id=165
             slice 3 (da0s3) rest ID=165
         W ---> OK
        label
             da0s3d 9GB         /mnt
             da0s3e rest        /dist
         W ---> da0s3e ---- device is not configured.

w# ll /dev/da0*      # after sysinstall did partition + W at 1st time
crw-r-----  1 root  operator    0,  97 Nov 22 11:23 /dev/da0
crw-r-----  1 root  operator    0,  98 Nov 22 11:23 /dev/da0s1
crw-r-----  1 root  operator    0,  99 Nov 22 11:23 /dev/da0s2
crw-r-----  1 root  operator    0, 100 Nov 22 11:23 /dev/da0s3

# ll /dev/da0*      # after sysinstall start at 2nd time
crw-r-----  1 root  operator    0,  97 Nov 22 11:27 /dev/da0
System crashed

The crash log is available at
http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2
(All logs are based on hw.usb.umass.debug=-1)

After system reboot, and repeated above processes, the da0s3e was
mounted on /dist, but da0s3d cannot.
It tunred out that newfs fail inside labeling process in sysinstall.
Manually did newfs on da0s3d, and
it cannot be mounted on /mnt, but access to it caused crash.
The crash log is available at
http:/www.daemonfun.com/archives/pub/USB/newfs

Tried entire process again, this time, both partitons are formatted
(newfs) inside labaling process (sysinstall)
but crahsed system during dump/restore on da0s3e (/dist).
The crash log is available at
http:/www.daemonfun.com/archives/pub/USB/usb-log.crash2.bz2, which is
huge one.
It contains two parts, one dump/restore IDE to da0s3d (passed), and the
rest is dump/restore to da0s3e (crashed).

I am going to reinstall the system with the new ISO from Nov 21
8.0-RELEASE to see if anything will improve.

-----Original Message-----
From: Hans Petter Selasky [mailto:hselasky@c2i.net]
Sent: Sun 11/22/2009 1:47 AM
To: freebsd-usb@freebsd.org
Cc: Guojun Jin; bugs@freebsd.org; freebsd-stable@freebsd.org
Subject: Re: 8.0-RC USB/FS problem
 
On Sunday 22 November 2009 05:38:13 Guojun Jin wrote:
> Tried on the USB hard drive:
>
> Deleted slice 3 and recreated slice 3 with two partitions s3d and s3e.
> Was happy because successfully did dump/restore on s3d, and thought it
just
> partition format issue; but system crashed during dump/restore on s3e,
and
> partition lost the file system type.
>
> wolf# mount /dev/da0s3e /mnt
> WARNING: /mnt was not properly dismounted
> /mnt: mount pending error: blocks 35968 files 0
> wolf# fsck da0s3e
> fsck: Could not determine filesystem type
> wolf# bsdlabel da0s3
> # /dev/da0s3:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>   c: 175735035        0    unused        0     0         # "raw" part,
> don't edi t
>   d: 18874368        0    4.2BSD        0     0     0
>   e: 156860667 18874368    4.2BSD        0     0     0
>
> Therefore, tried directly use fsck_ufs on both USB hard drive and USB
stick
> to get file system clean up. All data got back now.
>
> The machine has run with FreeBSD 6.1 all the way to 7.2 without such
> problem. How can we determine what could go wrong in 8.0? FS or USB.

Hi,

Error 5 means IO error, so probably the transport layer, USB or lower,
is to 
blame.

Some things to check:

1) Make sure the connection for your memory stick is Ok.
2) Make sure there is enough power for your memory stick.

Regarding memory sticks:

Other operating systems do a port bus reset when the device has a
problem. On 
FreeBSD we just try a software reset via the control endpoint. I guess
that it 
is a device problem you are seeing. The USB stack in FreeBSD is faster
than 
the old one, and maybe the faster queueing of mass storage requests
trigger 
some hidden bugs in your device.

When the problem happens try:

sysctl hw.usb.umass.debug=-1

--HPS


From tlb at anybots.com  Wed Nov 25 01:56:11 2009
From: tlb at anybots.com (Trevor Blackwell)
Date: Wed Nov 25 01:56:17 2009
Subject: Identifying serial ports
Message-ID: <C4DA98C1-7AF6-4F22-BF4F-5565A45AD0E5@anybots.com>


I have two USB devices that work as serial ports:

ugen2.2.0: umodem0: <Hokuyo Data Flex for USB URG-Series USB Driver,  
class 2/0, rev 2.00/1.00, addr 2>
ugen2.3.0: uplcom0: <Prolific Technology Inc. USB-Serial Controller,  
class 0/0, rev 1.10/3.00, addr 3>

and they appear as serial devices /dev/cuaU0 and /dev/cuaU1. But I  
can't find a general-purpose way to figure out which is which. It  
depends on which gets enumerated first. In FreeBSD 7, the USB device  
minor # seemed to correspond to the cuaU device number, but here they  
are both zero. Any ideas?

--
Trevor Blackwell        tlb@anybots.com        650 776 7870




From hselasky at c2i.net  Wed Nov 25 08:35:34 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Nov 25 08:35:46 2009
Subject: 8.0-RC USB/FS problem
In-Reply-To: <CB2DD11991B27C4F99935E6229450D3204E5C6A4@STORK.scenix.com>
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A29@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3204E5C6A4@STORK.scenix.com>
Message-ID: <200911250937.08267.hselasky@c2i.net>

On Wednesday 25 November 2009 00:08:59 Guojun Jin wrote:
> What other debug shall we turn on to analyze this problem.

Are you able to extract the panic message? Try enabling dump on the swap 
partition.

--HPS
From 166162 at gmail.com  Wed Nov 25 12:14:02 2009
From: 166162 at gmail.com (Travelling Particle)
Date: Wed Nov 25 12:14:09 2009
Subject: [keyboard] ukbd stops working after filesystems mount at boot 
	time
In-Reply-To: <sa6r5ropx06.wl%tamaru@myn.rcast.u-tokyo.ac.jp>
References: <da6b214d0911180425r2b720333r87fe2fb79e3e13e1@mail.gmail.com>
	<200911201224.08313.hselasky@c2i.net>
	<da6b214d0911211012he5b2bb7v701596976d2bd0ea@mail.gmail.com>
	<200911212300.20154.hselasky@c2i.net>
	<da6b214d0911231608l18fb2ae0h5cab9420a5631923@mail.gmail.com>
	<sa6r5ropx06.wl%tamaru@myn.rcast.u-tokyo.ac.jp>
Message-ID: <da6b214d0911250414x738ae0e8t2b8d733441872faf@mail.gmail.com>

> Does this let you work around your problem too?
>
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+0+/usr/local/www/db/text/2008/freebsd-mobile/20080309.freebsd-mobile

Haven't tried the patch, but I see what you mean. I had tested with
atkbd and kbdmux both disabled and having geli passphrase visible.
It appears that in 8.0-PRERELEASE (cvsuped Nov 23 2009, I think) the
original problem I had reported is gone: if I can get thru the
passphrase, the late stage continues fine and keyboard works at login
prompt without any problem. However, the keyboard works unreliably(*)
just before the late boot stage, at the moment when the geli
passphrase is expected. 8.0-RC3 behaved the opposite way: no problem
at the passphrase, but unusable console right after that.

(*) By working unreliably I mean that key presses are randomly
skipped. Sometimes you see keys pressed right after the first press,
sometimes it takes 3-4 times to repeat the press before the symbol
gets entered.

I have googled up that skipping key presses at the passphrase prompt
was reported since a long time ago. I see that it was somewhat fixed
in 8.0-RC3 with undesired side-effects. This leaves me wonder if the
keyboard can be fixed without breaking the console. I am willing to
help: if anyone needs debugging output or anything, just tell me what
I should do. USB keyboard is the only input device this computer has
(no PS/2 or serial port), so I' somewhat desperate.

> Chances are that unreliable key inputs at boot stage is not that
> usb specific, but I couldn't dig any deeper then...

I think it's usb-specific. What else would be responsible for dropping
input from the usb device?

Thanks.
From tamaru at myn.rcast.u-tokyo.ac.jp  Wed Nov 25 16:13:07 2009
From: tamaru at myn.rcast.u-tokyo.ac.jp (Hiroharu Tamaru)
Date: Wed Nov 25 16:13:13 2009
Subject: [keyboard] ukbd stops working after filesystems mount at boot
	time
In-Reply-To: <da6b214d0911250414x738ae0e8t2b8d733441872faf@mail.gmail.com>
References: <da6b214d0911180425r2b720333r87fe2fb79e3e13e1@mail.gmail.com>
	<200911201224.08313.hselasky@c2i.net>
	<da6b214d0911211012he5b2bb7v701596976d2bd0ea@mail.gmail.com>
	<200911212300.20154.hselasky@c2i.net>
	<da6b214d0911231608l18fb2ae0h5cab9420a5631923@mail.gmail.com>
	<sa6r5ropx06.wl%tamaru@myn.rcast.u-tokyo.ac.jp>
	<da6b214d0911250414x738ae0e8t2b8d733441872faf@mail.gmail.com>
Message-ID: <sa6pr76poqb.wl%tamaru@myn.rcast.u-tokyo.ac.jp>

Hi

At Wed, 25 Nov 2009 15:14:01 +0300, Travelling Particle wrote:
> > Does this let you work around your problem too?
> >
> > http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+0+/usr/local/www/db/text/2008/freebsd-mobile/20080309.freebsd-mobile
> 
> Haven't tried the patch, but I see what you mean. I had tested with
> atkbd and kbdmux both disabled and having geli passphrase visible.
> It appears that in 8.0-PRERELEASE (cvsuped Nov 23 2009, I think) the
> original problem I had reported is gone: if I can get thru the
> passphrase, the late stage continues fine and keyboard works at login
> prompt without any problem. However, the keyboard works unreliably(*)
> just before the late boot stage, at the moment when the geli
> passphrase is expected. 8.0-RC3 behaved the opposite way: no problem
> at the passphrase, but unusable console right after that.
> 
> (*) By working unreliably I mean that key presses are randomly
> skipped. Sometimes you see keys pressed right after the first press,
> sometimes it takes 3-4 times to repeat the press before the symbol
> gets entered.
> 
> I have googled up that skipping key presses at the passphrase prompt
> was reported since a long time ago. I see that it was somewhat fixed
> in 8.0-RC3 with undesired side-effects. This leaves me wonder if the
> keyboard can be fixed without breaking the console. I am willing to
> help: if anyone needs debugging output or anything, just tell me what
> I should do. USB keyboard is the only input device this computer has
> (no PS/2 or serial port), so I' somewhat desperate.
> 
> > Chances are that unreliable key inputs at boot stage is not that
> > usb specific, but I couldn't dig any deeper then...
> 
> I think it's usb-specific. What else would be responsible for dropping
> input from the usb device?

BIOS or something alike, or some non-interrupt driven
method, or some interrupt mechanism itself?

Back then, I wondered if the kernel used BIOS or any of the
above, that probably is different from how the device is
driven after the boot stage is finalized, but I never
reached the actual code to know it myself.  I'd appreciate
if someone can confirm it either way.

Anyway, in my case, I was using atkbd, and not ukbd, and it
was just that I thought if it were really the BIOS, the same
work around may help.

Anyway, reading your description above, more than one thing
is probably involved, so just take what I wrote as my wild
guess at best.  I wish I knew the kernel better not to guess
a lot like this, of course...

So, the ball is back on the side of the experts here ;-p

> Thanks.
From br at rambler-co.ru  Wed Nov 25 17:25:38 2009
From: br at rambler-co.ru (Bukin Ruslan)
Date: Wed Nov 25 17:25:45 2009
Subject: uhci_interrupt: host controller halted
Message-ID: <20091125170832.GA78035@rambler-co.ru>

hello,

i have about 1000 UHCI_STS_HCH intrr per second:

Nov 25 19:55:27 br kernel: uhci_interrupt:1506: uhci_interrupt: host controller halted
Nov 25 19:55:27 br kernel: uhci_dumpregs:741: usbus2 regs: cmd=0080, sts=0020, intr=000f, frnum=01c9, flbase=01a23724, sof=0040, portsc1=0080, portsc2=0080
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073005000) at 0x01a24002: h_next=0x01a25002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073006000) at 0x01a25002: h_next=0x01a26002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073007000) at 0x01a26002: h_next=0x01a27002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073008000) at 0x01a27002: h_next=0x00000001 e_next=0x01a28000
Nov 25 19:55:27 br kernel: uhci_interrupt:1506: uhci_interrupt: host controller halted
Nov 25 19:55:27 br kernel: uhci_dumpregs:741: usbus2 regs: cmd=0080, sts=0020, intr=000f, frnum=01c9, flbase=01a23724, sof=0040, portsc1=0080, portsc2=0080
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073005000) at 0x01a24002: h_next=0x01a25002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073006000) at 0x01a25002: h_next=0x01a26002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073007000) at 0x01a26002: h_next=0x01a27002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073008000) at 0x01a27002: h_next=0x00000001 e_next=0x01a28000
Nov 25 19:55:27 br kernel: uhci_interrupt:1506: uhci_interrupt: host controller halted
Nov 25 19:55:27 br kernel: uhci_dumpregs:741: usbus2 regs: cmd=0080, sts=0020, intr=000f, frnum=01c9, flbase=01a23724, sof=0040, portsc1=0080, portsc2=0080
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073005000) at 0x01a24002: h_next=0x01a25002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073006000) at 0x01a25002: h_next=0x01a26002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073007000) at 0x01a26002: h_next=0x01a27002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073008000) at 0x01a27002: h_next=0x00000001 e_next=0x01a28000
Nov 25 19:55:27 br kernel: uhci_interrupt:1506: uhci_interrupt: host controller halted
Nov 25 19:55:27 br kernel: uhci_dumpregs:741: usbus2 regs: cmd=0080, sts=0020, intr=000f, frnum=01c9, flbase=01a23724, sof=0040, portsc1=0080, portsc2=0080
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073005000) at 0x01a24002: h_next=0x01a25002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073006000) at 0x01a25002: h_next=0x01a26002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073007000) at 0x01a26002: h_next=0x01a27002 e_next=0x00000001
Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073008000) at 0x01a27002: h_next=0x00000001 e_next=0x01a28000
Nov 25 19:55:27 br kernel: uhci_interrupt:1506: uhci_interrupt: host controller halted

is this normal?

kern.version: FreeBSD 9.0-CURRENT #6: Wed Nov 25 06:48:28 UTC 2009

From gjin at ubicom.com  Wed Nov 25 17:42:35 2009
From: gjin at ubicom.com (Guojun Jin)
Date: Wed Nov 25 17:42:46 2009
Subject: 8.0-RC USB/FS problem
References: <CB2DD11991B27C4F99935E6229450D3203950A1C@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3203950A29@STORK.scenix.com>
	<CB2DD11991B27C4F99935E6229450D3204E5C6A4@STORK.scenix.com>
	<200911250937.08267.hselasky@c2i.net>
Message-ID: <CB2DD11991B27C4F99935E6229450D3203950A33@STORK.scenix.com>

I will do,

I also borrowed two other machiens -- one AMD two core laptop, and one P4 desktop -- for further testing.
I will enable kernel coredump for all of them and will make cores available by end of today.

-Jin

-----Original Message-----
From: Hans Petter Selasky [mailto:hselasky@c2i.net]
Sent: Wed 11/25/2009 12:37 AM
To: Guojun Jin
Cc: freebsd-usb@freebsd.org; bugs@freebsd.org; freebsd-stable@freebsd.org
Subject: Re: 8.0-RC USB/FS problem
 
On Wednesday 25 November 2009 00:08:59 Guojun Jin wrote:
> What other debug shall we turn on to analyze this problem.

Are you able to extract the panic message? Try enabling dump on the swap 
partition.

--HPS

From hselasky at c2i.net  Wed Nov 25 17:54:26 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Nov 25 17:54:33 2009
Subject: uhci_interrupt: host controller halted
In-Reply-To: <20091125170832.GA78035@rambler-co.ru>
References: <20091125170832.GA78035@rambler-co.ru>
Message-ID: <200911251855.59108.hselasky@c2i.net>

On Wednesday 25 November 2009 18:08:32 Bukin Ruslan wrote:
> hello,
>
> i have about 1000 UHCI_STS_HCH intrr per second:
>

>
> is this normal?

No, it is not normal. Maybe this happens because the interrupt line is shared. 
What does vmstat -i say?

--HPS

From br at rambler-co.ru  Wed Nov 25 18:21:45 2009
From: br at rambler-co.ru (Bukin Ruslan)
Date: Wed Nov 25 18:21:51 2009
Subject: uhci_interrupt: host controller halted
In-Reply-To: <200911251855.59108.hselasky@c2i.net>
References: <20091125170832.GA78035@rambler-co.ru>
	<200911251855.59108.hselasky@c2i.net>
Message-ID: <20091125182143.GA78322@rambler-co.ru>

On Wed, Nov 25, 2009 at 06:55:57PM +0100, Hans Petter Selasky wrote:
> On Wednesday 25 November 2009 18:08:32 Bukin Ruslan wrote:
> > hello,
> >
> > i have about 1000 UHCI_STS_HCH intrr per second:
> >
> 
> >
> > is this normal?
> 
> No, it is not normal. Maybe this happens because the interrupt line is shared. 
> What does vmstat -i say?
> 
> --HPS

#vmstat -i
interrupt                          total       rate
irq1: atkbd0                        3527          6
irq9: acpi0                          741          1
irq16: uhci2+                      82402        150
irq20: uhci0                          13          0
irq21: uhci1                        3303          6
irq22: ehci0                           3          0
cpu0: timer                      1090324       1996
irq256: em0                         3514          6
irq257: hdac0                      72093        132
cpu1: timer                      1090197       1996
irq258: vgapci0                     4535          8
Total                            2350652       4305

From hselasky at c2i.net  Wed Nov 25 18:23:36 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Nov 25 18:23:42 2009
Subject: uhci_interrupt: host controller halted
In-Reply-To: <20091125182143.GA78322@rambler-co.ru>
References: <20091125170832.GA78035@rambler-co.ru>
	<200911251855.59108.hselasky@c2i.net>
	<20091125182143.GA78322@rambler-co.ru>
Message-ID: <200911251925.11024.hselasky@c2i.net>

On Wednesday 25 November 2009 19:21:43 Bukin Ruslan wrote:
> On Wed, Nov 25, 2009 at 06:55:57PM +0100, Hans Petter Selasky wrote:
> > On Wednesday 25 November 2009 18:08:32 Bukin Ruslan wrote:
> > > hello,
> > >
> > > i have about 1000 UHCI_STS_HCH intrr per second:
> > >
> > >
> > >
> > > is this normal?
> >
> > No, it is not normal. Maybe this happens because the interrupt line is
> > shared. What does vmstat -i say?
> >
> > --HPS
>
> #vmstat -i
> interrupt                          total       rate
> irq1: atkbd0                        3527          6
> irq9: acpi0                          741          1
> irq16: uhci2+                      82402        150
> irq20: uhci0                          13          0
> irq21: uhci1                        3303          6
> irq22: ehci0                           3          0
> cpu0: timer                      1090324       1996
> irq256: em0                         3514          6
> irq257: hdac0                      72093        132
> cpu1: timer                      1090197       1996
> irq258: vgapci0                     4535          8
> Total                            2350652       4305

Hi,

There should be some code so that the UHCI only prints this message once. 
Thought it looks like the IRQ is shared so the message is printed multiple 
times.

--HPS

From sub.mesa at gmail.com  Thu Nov 26 03:00:12 2009
From: sub.mesa at gmail.com (sub mesa)
Date: Thu Nov 26 03:00:19 2009
Subject: usb/140883: axe(4) USB gigabit ethernet hangs after short period of
	traffic
Message-ID: <200911260259.nAQ2xtXf000958@www.freebsd.org>


>Number:         140883
>Category:       usb
>Synopsis:       axe(4) USB gigabit ethernet hangs after short period of traffic
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Nov 26 03:00:11 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     sub mesa
>Release:        FreeBSD 8.0-RELEASE i386
>Organization:
>Environment:
FreeBSD gut 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Wed Nov 25 14:30:17 CET 2009     xor@xor:/usr/obj/usr/src/sys/XOR  i386
>Description:
I own a USB gigabit ethernet adapter with ASIX Electronics AX88178 chip supported by the axe(4) driver in FreeBSD 8.0. It works, but it 'freezes' or 'hangs' after some traffic, like downloading at ~50Mbps for 5-10 minutes will cause the device to freeze. This has been happening since a long time on 8.0, ever since i bought the device and was running one of the early beta's. Upgrading to the final release of 8.0 did not resolve the issue.

Googling on the problem i found this mailinglist thread:
http://lists.freebsd.org/pipermail/freebsd-current/2009-April/005738.html

However, there doesn't seem to be a single conclusion. Even though my product ("Belkin F5D5055") seems to be supported according to the axe(4) manpage, it doesn't get detected as such, rather with a vendor id. Quoting dmesg output:

axe0: <vendor 0x050d product 0x5055, rev 2.00/0.01, addr 2> on usbus4
axe0: PHYADDR 0xe0:0x01
miibus1: <MII bus> on axe0
ue0: <USB Ethernet> on axe0

May i suggest removing the Belkin F5D5055 from the supported devices list in the axe(4) manpage, until a fix has been committed? I specifically bought the device believing it would work since it was explicitly listed in the manpage. As of 8.0, it doesn't even get detected by name. It is of course possible my device is of a different revision.

I would be happy to try any patches.

Also see:
http://forums.freebsd.org/showthread.php?t=8661
>How-To-Repeat:
Connect axe(4) gigabit ethernet device
Send/receive packets using the ueX ethernet device
Device will stop receiving/transmitting packets after a short while
>Fix:
Workaround: re-plug device or use usbreset command. No fix known.

>Release-Note:
>Audit-Trail:
>Unformatted: