From g.veniamin at googlemail.com  Wed Jul  2 11:30:05 2008
From: g.veniamin at googlemail.com (admin)
Date: Wed Jul  2 11:30:11 2008
Subject: usb/124980: [panic] kernel panic
Message-ID: <200807021130.m62BU44x036097@freefall.freebsd.org>

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

From: admin <g.veniamin@googlemail.com>
To: bug-followup@FreeBSD.org, g.veniamin@googlemail.com
Cc:  
Subject: Re: usb/124980: [panic] kernel panic
Date: Wed, 02 Jul 2008 19:04:09 +0000

 ss# kldstat
 Id Refs Address Size Name
  1 35 0xc0400000 64c944 kernel (/boot/kernel/kernel)
  2 1 0xc0a4d000 7040 snd_ich.ko (/boot/kernel/snd_ich.ko)
  3 2 0xc0a55000 4a744 sound.ko (/boot/kernel/sound.ko)
  4 1 0xc0aa0000 3500 umodem.ko (/boot/kernel/umodem.ko)
  5 1 0xc0aa4000 7200 i915.ko (/boot/kernel/i915.ko)
  6 1 0xc0aac000 6b6a0 acpi.ko (/boot/kernel/acpi.ko)
 
 device insert
 
 umass0: <vendor 0x05e3 USB TO IDE, class 0/0, rev 2.00/0.33, addr 2> on 
 uhub3
 
 device removal kernel panic
 
 (kgdb) core-file vmcore.0
 
 Unread portion of the kernel message buffer:
 umass0: BBB reset failed, IOERROR
 umass0: BBB bulk-in clear stall failed, IOERROR
 umass0: BBB bulk-out clear stall failed, IOERROR
 umass0: at uhub3 port 1 (addr 2) disconnected
 
 
 Fatal trap 12: page fault while in kernel mode
 fault virtual address = 0x0
 fault code = supervisor write, page not present
 instruction pointer = 0x20:0xc044e89b
 stack pointer = 0x28:0xc4afa9b4
 frame pointer = 0x28:0xc4afa9d0
 code segment = base 0x0, limit 0xfffff, type 0x1b
   = DPL 0, pres 1, def32 1, gran 1
 processor eflags = interrupt enabled, resume, IOPL = 0
 current process = 19 (usb3)
 trap number = 12
 panic: page fault
 Uptime: 2m41s
 Physical memory: 2006 MB
 Dumping 76 MB: 61 45 29 13
 
 (kgdb) bt 0xc044e89b
 #0 doadump () at pcpu.h:196
 #1 0xc05d57f3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
 #2 0xc05d59ef in panic (fmt=Variable "fmt" is not available.
 ) at /usr/src/sys/kern/kern_shutdown.c:572
 #3 0xc086e49c in trap_fatal (frame=0xc4afa974, eva=0)
   at /usr/src/sys/i386/i386/trap.c:934
 #4 0xc086e700 in trap_pfault (frame=0xc4afa974, usermode=0, eva=0)
   at /usr/src/sys/i386/i386/trap.c:847
 #5 0xc086f049 in trap (frame=0xc4afa974) at 
 /usr/src/sys/i386/i386/trap.c:525
 #6 0xc085beeb in calltrap () at /usr/src/sys/i386/i386/exception.s:165
 #7 0xc044e89b in xpt_done (done_ccb=0xc4dbcc00)
   at /usr/src/sys/cam/cam_xpt.c:4835
 #8 0xc0454f6e in probedone (periph=0xc531e000, done_ccb=Variable 
 "done_ccb" is not available.
 )
   at /usr/src/sys/cam/cam_xpt.c:6392
 #9 0xc0450a21 in camisr_runqueue (V_queue=Variable "V_queue" is not 
 available.
 ) at /usr/src/sys/cam/cam_xpt.c:7316
 #10 0xc045435f in xpt_bus_deregister (pathid=1)
   at /usr/src/sys/cam/cam_xpt.c:4421
 #11 0xc0551a70 in umass_cam_detach_sim (sc=0xc5211800)
   at /usr/src/sys/dev/usb/umass.c:2712
 #12 0xc0551b1d in umass_detach (self=0xc531cc80)
   at /usr/src/sys/dev/usb/umass.c:1560
 #13 0xc05f7b78 in device_detach (dev=0xc531cc80) at device_if.h:212
 #14 0xc0558d32 in usb_disconnect_port (up=0xc4d2e730, parent=0xc4d3ee00)
   at /usr/src/sys/dev/usb/usb_subr.c:1380
 ---Type <return> to continue, or q <return> to quit---
 #15 0xc054eaee in uhub_explore (dev=0xc4d5d100)
   at /usr/src/sys/dev/usb/uhub.c:462
 #16 0xc0556e75 in usb_discover (v=Variable "v" is not available.
 ) at /usr/src/sys/dev/usb/usb.c:728
 #17 0xc0557d4a in usb_event_thread (arg=0xc4d5c600)
   at /usr/src/sys/dev/usb/usb.c:440
 #18 0xc05b5e20 in fork_exit (callout=0xc0557ca0 <usb_event_thread>,
   arg=0xc4d5c600, frame=0xc4afad38) at /usr/src/sys/kern/kern_fork.c:812
 #19 0xc085bf60 in fork_trampoline () at 
 /usr/src/sys/i386/i386/exception.s:270
From gavin at FreeBSD.org  Wed Jul  2 13:16:22 2008
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Wed Jul  2 13:16:26 2008
Subject: usb/124980: [panic] kernel panic
Message-ID: <200807021316.m62DGLue045417@freefall.freebsd.org>

Synopsis: [panic] kernel panic

State-Changed-From-To: feedback->open
State-Changed-By: gavin
State-Changed-When: Wed Jul 2 13:15:25 UTC 2008
State-Changed-Why: 
Feedback received:

ss# kldstat
Id Refs Address Size Name
 1 35 0xc0400000 64c944 kernel (/boot/kernel/kernel)
 2 1 0xc0a4d000 7040 snd_ich.ko (/boot/kernel/snd_ich.ko)
 3 2 0xc0a55000 4a744 sound.ko (/boot/kernel/sound.ko)
 4 1 0xc0aa0000 3500 umodem.ko (/boot/kernel/umodem.ko)
 5 1 0xc0aa4000 7200 i915.ko (/boot/kernel/i915.ko)
 6 1 0xc0aac000 6b6a0 acpi.ko (/boot/kernel/acpi.ko)

device insert

umass0: <vendor 0x05e3 USB TO IDE, class 0/0, rev 2.00/0.33, addr 2> on
uhub3

device removal kernel panic

(kgdb) core-file vmcore.0

Unread portion of the kernel message buffer:
umass0: BBB reset failed, IOERROR
umass0: BBB bulk-in clear stall failed, IOERROR
umass0: BBB bulk-out clear stall failed, IOERROR
umass0: at uhub3 port 1 (addr 2) disconnected


Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor write, page not present
instruction pointer = 0x20:0xc044e89b
stack pointer = 0x28:0xc4afa9b4
frame pointer = 0x28:0xc4afa9d0
code segment = base 0x0, limit 0xfffff, type 0x1b
  = DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 19 (usb3)
trap number = 12
panic: page fault
Uptime: 2m41s
Physical memory: 2006 MB
Dumping 76 MB: 61 45 29 13

(kgdb) bt 0xc044e89b
#0 doadump () at pcpu.h:196
#1 0xc05d57f3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2 0xc05d59ef in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:572
#3 0xc086e49c in trap_fatal (frame=0xc4afa974, eva=0)
  at /usr/src/sys/i386/i386/trap.c:934
#4 0xc086e700 in trap_pfault (frame=0xc4afa974, usermode=0, eva=0)
  at /usr/src/sys/i386/i386/trap.c:847
#5 0xc086f049 in trap (frame=0xc4afa974) at
/usr/src/sys/i386/i386/trap.c:525
#6 0xc085beeb in calltrap () at /usr/src/sys/i386/i386/exception.s:165
#7 0xc044e89b in xpt_done (done_ccb=0xc4dbcc00)
  at /usr/src/sys/cam/cam_xpt.c:4835
#8 0xc0454f6e in probedone (periph=0xc531e000, done_ccb=Variable "done_ccb"
is not available.
)
  at /usr/src/sys/cam/cam_xpt.c:6392
#9 0xc0450a21 in camisr_runqueue (V_queue=Variable "V_queue" is not
available.
) at /usr/src/sys/cam/cam_xpt.c:7316
#10 0xc045435f in xpt_bus_deregister (pathid=1)
  at /usr/src/sys/cam/cam_xpt.c:4421
#11 0xc0551a70 in umass_cam_detach_sim (sc=0xc5211800)
  at /usr/src/sys/dev/usb/umass.c:2712
#12 0xc0551b1d in umass_detach (self=0xc531cc80)
  at /usr/src/sys/dev/usb/umass.c:1560
#13 0xc05f7b78 in device_detach (dev=0xc531cc80) at device_if.h:212
#14 0xc0558d32 in usb_disconnect_port (up=0xc4d2e730, parent=0xc4d3ee00)
  at /usr/src/sys/dev/usb/usb_subr.c:1380
---Type <return> to continue, or q <return> to quit---
#15 0xc054eaee in uhub_explore (dev=0xc4d5d100)
  at /usr/src/sys/dev/usb/uhub.c:462
#16 0xc0556e75 in usb_discover (v=Variable "v" is not available.
) at /usr/src/sys/dev/usb/usb.c:728
#17 0xc0557d4a in usb_event_thread (arg=0xc4d5c600)
  at /usr/src/sys/dev/usb/usb.c:440
#18 0xc05b5e20 in fork_exit (callout=0xc0557ca0 <usb_event_thread>,
  arg=0xc4d5c600, frame=0xc4afad38) at /usr/src/sys/kern/kern_fork.c:812
#19 0xc085bf60 in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:270

http://www.freebsd.org/cgi/query-pr.cgi?pr=124980
From rizzo at icir.org  Thu Jul  3 14:30:38 2008
From: rizzo at icir.org (Luigi Rizzo)
Date: Thu Jul  3 14:30:42 2008
Subject: may I commit this small umodem patch ?
Message-ID: <20080703140719.GA72315@onelab2.iet.unipi.it>

There was a discussion back in september about adding
support for basic CDC tty devices in umodem.c.
This lets you talk to a number of usb devices built around
microcontrollers (e.g. Atmel), and puts us on par with
Linux and Windows in terms of supporting these devices.

Because this simply requires the small patch below to the
probe/attach routine, so if there are no objections I plan to add
this to the system (CURRENT then RELENG_7 and RELENG_6) in the next
few days.

> Index: umodem.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/dev/usb/umodem.c,v
> retrieving revision 1.57
> diff -u -r1.57 umodem.c
> --- umodem.c	31 Jan 2005 13:58:10 -0000	1.57
> +++ umodem.c	20 Aug 2006 17:05:34 -0000
> @@ -256,6 +260,15 @@
>  	    id->bInterfaceProtocol == UIPROTO_CDC_AT)
>  		ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO;
>  
> +#if 1
> +	if (ret == UMATCH_NONE &&
> +	    id->bInterfaceClass == UICLASS_CDC_DATA &&
> +	    id->bInterfaceSubClass == UISUBCLASS_DATA &&
> +	    id->bInterfaceProtocol == 0x00)
> +		ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO;
> +		return ret;
> +#endif
> +
>  	if (ret == UMATCH_NONE)
>  		return (ret);

cheers
luigi
From gary.jennejohn at freenet.de  Thu Jul  3 15:07:04 2008
From: gary.jennejohn at freenet.de (Gary Jennejohn)
Date: Thu Jul  3 15:07:06 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <20080703140719.GA72315@onelab2.iet.unipi.it>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
Message-ID: <20080703170700.3b91b8c6@peedub.jennejohn.org>

On Thu, 3 Jul 2008 16:07:19 +0200
Luigi Rizzo <rizzo@icir.org> wrote:

> There was a discussion back in september about adding
> support for basic CDC tty devices in umodem.c.
> This lets you talk to a number of usb devices built around
> microcontrollers (e.g. Atmel), and puts us on par with
> Linux and Windows in terms of supporting these devices.
> 
> Because this simply requires the small patch below to the
> probe/attach routine, so if there are no objections I plan to add
> this to the system (CURRENT then RELENG_7 and RELENG_6) in the next
> few days.
> 
> > Index: umodem.c
> > ===================================================================
> > RCS file: /home/ncvs/src/sys/dev/usb/umodem.c,v
> > retrieving revision 1.57
> > diff -u -r1.57 umodem.c
> > --- umodem.c	31 Jan 2005 13:58:10 -0000	1.57
> > +++ umodem.c	20 Aug 2006 17:05:34 -0000
> > @@ -256,6 +260,15 @@
> >  	    id->bInterfaceProtocol == UIPROTO_CDC_AT)
> >  		ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO;
> >  
> > +#if 1
> > +	if (ret == UMATCH_NONE &&
> > +	    id->bInterfaceClass == UICLASS_CDC_DATA &&
> > +	    id->bInterfaceSubClass == UISUBCLASS_DATA &&
> > +	    id->bInterfaceProtocol == 0x00)
> > +		ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO;
> > +		return ret;
> > +#endif
> > +
> >  	if (ret == UMATCH_NONE)
> >  		return (ret);
> 

Is there any reason to keep the #if 1 ... #endif?  And why not just
directly return UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO rather than
assigning it to ret first?

---
Gary Jennejohn (gj@freebsd.org)
From rizzo at icir.org  Thu Jul  3 15:24:08 2008
From: rizzo at icir.org (Luigi Rizzo)
Date: Thu Jul  3 15:24:12 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <20080703170700.3b91b8c6@peedub.jennejohn.org>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<20080703170700.3b91b8c6@peedub.jennejohn.org>
Message-ID: <20080703152551.GA73103@onelab2.iet.unipi.it>

On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote:
> On Thu, 3 Jul 2008 16:07:19 +0200
> Luigi Rizzo <rizzo@icir.org> wrote:
> 
> > There was a discussion back in september about adding
> > support for basic CDC tty devices in umodem.c.
> > This lets you talk to a number of usb devices built around
> > microcontrollers (e.g. Atmel), and puts us on par with
> > Linux and Windows in terms of supporting these devices.
> > 
> > Because this simply requires the small patch below to the
> > probe/attach routine, so if there are no objections I plan to add
> > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next
> > few days.
> > 
> > > Index: umodem.c
> > > ===================================================================
> > > RCS file: /home/ncvs/src/sys/dev/usb/umodem.c,v
> > > retrieving revision 1.57
> > > diff -u -r1.57 umodem.c
> > > --- umodem.c	31 Jan 2005 13:58:10 -0000	1.57
> > > +++ umodem.c	20 Aug 2006 17:05:34 -0000
> > > @@ -256,6 +260,15 @@
> > >  	    id->bInterfaceProtocol == UIPROTO_CDC_AT)
> > >  		ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO;
> > >  
> > > +#if 1
> > > +	if (ret == UMATCH_NONE &&
> > > +	    id->bInterfaceClass == UICLASS_CDC_DATA &&
> > > +	    id->bInterfaceSubClass == UISUBCLASS_DATA &&
> > > +	    id->bInterfaceProtocol == 0x00)
> > > +		ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO;
> > > +		return ret;
> > > +#endif
> > > +
> > >  	if (ret == UMATCH_NONE)
> > >  		return (ret);
> > 
> 
> Is there any reason to keep the #if 1 ... #endif?  And why not just
> directly return UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO rather than
> assigning it to ret first?

in fact there are also missing braces that need to be
added -- as is, the code after the #endif is completely disabled.

thanks for the comment, but don't worry, the commit will be done
the right way.

cheers
luigi
From chrispetso at gmail.com  Thu Jul  3 16:10:05 2008
From: chrispetso at gmail.com (Chris Pet)
Date: Thu Jul  3 16:10:38 2008
Subject: usb/125238: Habu Mouse turns off in X
Message-ID: <200807031601.m63G1c9o064894@www.freebsd.org>


>Number:         125238
>Category:       usb
>Synopsis:       Habu Mouse turns off in X
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jul 03 16:10:05 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Chris Pet
>Release:        FreeBSD 7-STABLE 64Bit
>Organization:
None
>Environment:
FreeBSD slappy.domain 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jun 25 04:25:57 CDT 2008 root@.gateway.2wire.net:/usr/obj/usr/src/sys/chris amd64
>Description:
Habu mouse does get detected as a mouse in 7.0-rel but it does in stable. The issue I have is with the mouse when it's used in X. I am using Gnome when ever I use the mouse a lot the mouse tends to stop working or turn off and the only way to make it work again is by changing virtual consoles and then going back to x but this doesn't fix it permanently. This is getting very frustrating as I don't wish to purchase a cheaper PS/2 mouse to please FreeBSD even though it's very tempting due to the reliability and stability FreeBSD offers over other OS's such as Linux and Windows. 
>How-To-Repeat:
Have a Microsoft Habu mouse plugged in and use X, eventually the mouse will stop working.
>Fix:
No working fix after doing some personal experiments.

>Release-Note:
>Audit-Trail:
>Unformatted:
From chrispetso at gmail.com  Thu Jul  3 16:13:32 2008
From: chrispetso at gmail.com (Chris Pet.)
Date: Thu Jul  3 16:13:35 2008
Subject: Microsoft Habu Mouse
Message-ID: <51027c750807030844r35db93e7h159b56020372111e@mail.gmail.com>

Hello,
I have an issue with this mouse, as I believe it's a known issue I
didn't bother making a PR. The problem is this mouse is not support in
7.0-release as it's detected as a keyboard only, I had to upgrade to
Stable which isn't a issue. The issue lies when using the mouse with X
the mouse tends to turn off, mouse stops moving/working the only way
to fix it is to change virtual terms and then back to X, this works to
an extent but after doing it 2-3 times well it gets frustrating. Does
anyone have any patches to fix this issue, or is this a issue that
involved X and not just FreeBSD's USB stack? I have tried changing the
Protocol to Auto, changing the device from sysmouse to /dev/ums0 but
this is worst as it requires a total X shutdown in order to get the
mouse back. I have thought about purchasing a cheaper PS/2 mouse but I
like the speed of the Habu. You normally don't get this speed in PS/2
but rather USB. I have gotten weird reply's like my USB ports are mal
functioning, my motherboard is going bad normally I just ignore these
issues and the Mouse works in Linux/Windows without this issue.

Any input would be appreciated.
From screwdriver at lxnt.info  Thu Jul  3 16:18:22 2008
From: screwdriver at lxnt.info (Alexander Sabourenkov)
Date: Thu Jul  3 16:18:25 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <20080703170700.3b91b8c6@peedub.jennejohn.org>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<20080703170700.3b91b8c6@peedub.jennejohn.org>
Message-ID: <486CF22F.3080901@lxnt.info>

Gary Jennejohn wrote:
> On Thu, 3 Jul 2008 16:07:19 +0200
> Luigi Rizzo <rizzo@icir.org> wrote:
> 
[...]
>>> +#if 1
>>> +	if (ret == UMATCH_NONE &&
>>> +	    id->bInterfaceClass == UICLASS_CDC_DATA &&
>>> +	    id->bInterfaceSubClass == UISUBCLASS_DATA &&
>>> +	    id->bInterfaceProtocol == 0x00)
>>> +		ret = UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO;
>>> +		return ret;
>>> +#endif
>>> +
>>>  	if (ret == UMATCH_NONE)
>>>  		return (ret);
> 
> Is there any reason to keep the #if 1 ... #endif?  And why not just
> directly return UMATCH_IFACECLASS_IFACESUBCLASS_IFACEPROTO rather than
> assigning it to ret first?

This patch also makes all statements below ''return ret;'' unreachable.
I think it should be rewritten.


-- 

./lxnt

From vvd at quakeworld.ru  Fri Jul  4 15:00:12 2008
From: vvd at quakeworld.ru (vvd@quakeworld.ru)
Date: Fri Jul  4 15:00:18 2008
Subject: usb/125264: [patch] sysctl for set usb mouse rate (very useful for
	gamers - FPS games)
Message-ID: <200807041353.m64DrFdM030252@gw.unislabs.com>


>Number:         125264
>Category:       usb
>Synopsis:       [patch] sysctl for set usb mouse rate (very useful for gamers - FPS games)
>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:   Fri Jul 04 15:00:09 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     VVD <vvd@quakeworld.ru>
>Release:        FreeBSD 7.0-STABLE i386
>Organization:
no
>Environment:
System: FreeBSD vvd.home 7.0-STABLE FreeBSD 7.0-STABLE #0: Tue Jul 1 04:39:52 MSD 2008 root@vvd.home:/usr/obj/usr/src/sys/VVD2 i386
Platform independent patch.
Tested on: i386, motherboard ASUS P4P8X, mice Logitech MX300 and Logitech G5, game ezQuake 1.9.

>Description:
Add "options UMS_HZ=<INT_VALUE>" in kernel config.
USB mouse rate: value from 1 to 1000, other values set default rate - mouse specific.
Most mice suport till 250Hz and 500Hz. Greater value - smoother movements.
Some of "professional gaming" mice support 1000Hz and have default rate 500Hz.
User can to change this value using sysctl hw.usb.ums.hz.
For applying it user must take out mouse and insert it back.

>How-To-Repeat:
Use usb mouse. :-D

>Fix:

--- ums_hz.diff begins here ---
--- sys/conf/options.orig	2008-07-01 04:22:39.000000000 +0400
+++ sys/conf/options	2008-07-01 04:22:45.000000000 +0400
@@ -621,6 +621,7 @@
 UPLCOM_INTR_INTERVAL	opt_uplcom.h
 UVSCOM_DEFAULT_OPKTSIZE	opt_uvscom.h
 UVSCOM_INTR_INTERVAL	opt_uvscom.h
+UMS_HZ			opt_ums.h
 
 # Embedded system options
 INIT_PATH
--- sys/dev/usb/ums.c.orig	2008-06-16 19:51:35.000000000 +0400
+++ sys/dev/usb/ums.c	2008-07-01 04:23:41.000000000 +0400
@@ -69,6 +69,13 @@
 
 #include <sys/mouse.h>
 
+#include "opt_ums.h"
+#ifdef UMS_HZ
+static int ums_hz = UMS_HZ;
+SYSCTL_NODE(_hw_usb, OID_AUTO, ums, CTLFLAG_RW, 0, "USB ums");
+SYSCTL_INT(_hw_usb_ums, OID_AUTO, hz, CTLFLAG_RW, &ums_hz, 0, "");
+#endif
+
 #ifdef USB_DEBUG
 #define DPRINTF(x)	if (umsdebug) printf x
 #define DPRINTFN(n,x)	if (umsdebug>(n)) printf x
@@ -700,7 +707,12 @@
 	err = usbd_open_pipe_intr(sc->sc_iface, sc->sc_ep_addr,
 				USBD_SHORT_XFER_OK, &sc->sc_intrpipe, sc,
 				sc->sc_ibuf, sc->sc_isize, ums_intr,
-				USBD_DEFAULT_INTERVAL);
+#ifdef UMS_HZ
+				(ums_hz > 0 && ums_hz <= 1000) ? 1000 / ums_hz : USBD_DEFAULT_INTERVAL
+#else
+				USBD_DEFAULT_INTERVAL
+#endif
+				);
 	if (err) {
 		DPRINTF(("ums_enable: usbd_open_pipe_intr failed, error=%d\n",
 			 err));
--- sys/conf/NOTES.orig	2008-07-02 01:00:01.000000000 +0400
+++ sys/conf/NOTES	2008-07-02 01:06:12.000000000 +0400
@@ -2431,6 +2431,12 @@
 device		umodem
 # USB mouse
 device		ums
+# USB mouse rate (1 to 1000, other values set default rate - mouse specific).
+# Most mice suport till 250Hz and 500Hz. Greater value - smoother movements.
+# Some of "professional gaming" mice support 1000Hz and have default rate 500Hz.
+# You can to change this value using sysctl hw.usb.ums.hz.
+# For applying it you must take out mouse and insert it back.
+options		UMS_HZ=-1
 # Diamond Rio 500 MP3 player
 device		urio
 # USB scanners
>Release-Note:
>Audit-Trail:
>Unformatted:
From hselasky at c2i.net  Fri Jul  4 15:29:46 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Fri Jul  4 15:29:52 2008
Subject: usb/125264: [patch] sysctl for set usb mouse rate (very useful
	for gamers - FPS games)
In-Reply-To: <200807041353.m64DrFdM030252@gw.unislabs.com>
References: <200807041353.m64DrFdM030252@gw.unislabs.com>
Message-ID: <200807041731.12088.hselasky@c2i.net>

On Friday 04 July 2008, vvd@quakeworld.ru wrote:
> >Number:         125264
> >Category:       usb
> >Synopsis:       [patch] sysctl for set usb mouse rate (very useful for
> > gamers - FPS games) 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:   Fri Jul 04 15:00:09 UTC 2008
> >Closed-Date:
> >Last-Modified:
> >Originator:     VVD <vvd@quakeworld.ru>
> >Release:        FreeBSD 7.0-STABLE i386
> >Organization:
>
> no
>
> >Environment:
>
> System: FreeBSD vvd.home 7.0-STABLE FreeBSD 7.0-STABLE #0: Tue Jul 1
> 04:39:52 MSD 2008 root@vvd.home:/usr/obj/usr/src/sys/VVD2 i386 Platform
> independent patch.
> Tested on: i386, motherboard ASUS P4P8X, mice Logitech MX300 and Logitech
> G5, game ezQuake 1.9.
>
> >Description:
>
> Add "options UMS_HZ=<INT_VALUE>" in kernel config.
> USB mouse rate: value from 1 to 1000, other values set default rate - mouse
> specific. Most mice suport till 250Hz and 500Hz. Greater value - smoother
> movements. Some of "professional gaming" mice support 1000Hz and have
> default rate 500Hz. User can to change this value using sysctl
> hw.usb.ums.hz.
> For applying it user must take out mouse and insert it back.
>
> >How-To-Repeat:
>
> Use usb mouse. :-D
>
> >Fix:
>
> --- ums_hz.diff begins here ---
> --- sys/conf/options.orig	2008-07-01 04:22:39.000000000 +0400
> +++ sys/conf/options	2008-07-01 04:22:45.000000000 +0400
> @@ -621,6 +621,7 @@
>  UPLCOM_INTR_INTERVAL	opt_uplcom.h
>  UVSCOM_DEFAULT_OPKTSIZE	opt_uvscom.h
>  UVSCOM_INTR_INTERVAL	opt_uvscom.h
> +UMS_HZ			opt_ums.h
>
>  # Embedded system options
>  INIT_PATH
> --- sys/dev/usb/ums.c.orig	2008-06-16 19:51:35.000000000 +0400
> +++ sys/dev/usb/ums.c	2008-07-01 04:23:41.000000000 +0400
> @@ -69,6 +69,13 @@
>
>  #include <sys/mouse.h>
>
> +#include "opt_ums.h"
> +#ifdef UMS_HZ
> +static int ums_hz = UMS_HZ;
> +SYSCTL_NODE(_hw_usb, OID_AUTO, ums, CTLFLAG_RW, 0, "USB ums");
> +SYSCTL_INT(_hw_usb_ums, OID_AUTO, hz, CTLFLAG_RW, &ums_hz, 0, "");
> +#endif
> +
>  #ifdef USB_DEBUG
>  #define DPRINTF(x)	if (umsdebug) printf x
>  #define DPRINTFN(n,x)	if (umsdebug>(n)) printf x
> @@ -700,7 +707,12 @@
>  	err = usbd_open_pipe_intr(sc->sc_iface, sc->sc_ep_addr,
>  				USBD_SHORT_XFER_OK, &sc->sc_intrpipe, sc,
>  				sc->sc_ibuf, sc->sc_isize, ums_intr,
> -				USBD_DEFAULT_INTERVAL);
> +#ifdef UMS_HZ
> +				(ums_hz > 0 && ums_hz <= 1000) ? 1000 / ums_hz : USBD_DEFAULT_INTERVAL
> +#else
> +				USBD_DEFAULT_INTERVAL
> +#endif
> +				);
>  	if (err) {
>  		DPRINTF(("ums_enable: usbd_open_pipe_intr failed, error=%d\n",
>  			 err));
> --- sys/conf/NOTES.orig	2008-07-02 01:00:01.000000000 +0400
> +++ sys/conf/NOTES	2008-07-02 01:06:12.000000000 +0400
> @@ -2431,6 +2431,12 @@
>  device		umodem
>  # USB mouse
>  device		ums
> +# USB mouse rate (1 to 1000, other values set default rate - mouse
> specific). +# Most mice suport till 250Hz and 500Hz. Greater value -
> smoother movements. +# Some of "professional gaming" mice support 1000Hz
> and have default rate 500Hz. +# You can to change this value using sysctl
> hw.usb.ums.hz.
> +# For applying it you must take out mouse and insert it back.
> +options		UMS_HZ=-1
>  # Diamond Rio 500 MP3 player
>  device		urio
>  # USB scanners
>

Hi,

If the mouse is LOW speed you should not poll that often. Maybe you need to 
add a USB speed check (See usbd_get_speed() or something similar.)

--HPS
From hselasky at c2i.net  Fri Jul  4 16:30:04 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Fri Jul  4 16:30:11 2008
Subject: usb/125264: [patch] sysctl for set usb mouse rate (very useful
	for gamers - FPS games)
Message-ID: <200807041630.m64GU3pf087643@freefall.freebsd.org>

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

From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org,
 vvd@quakeworld.ru
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: usb/125264: [patch] sysctl for set usb mouse rate (very useful for gamers - FPS games)
Date: Fri, 4 Jul 2008 17:31:10 +0200

 On Friday 04 July 2008, vvd@quakeworld.ru wrote:
 > >Number:         125264
 > >Category:       usb
 > >Synopsis:       [patch] sysctl for set usb mouse rate (very useful for
 > > gamers - FPS games) 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:   Fri Jul 04 15:00:09 UTC 2008
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     VVD <vvd@quakeworld.ru>
 > >Release:        FreeBSD 7.0-STABLE i386
 > >Organization:
 >
 > no
 >
 > >Environment:
 >
 > System: FreeBSD vvd.home 7.0-STABLE FreeBSD 7.0-STABLE #0: Tue Jul 1
 > 04:39:52 MSD 2008 root@vvd.home:/usr/obj/usr/src/sys/VVD2 i386 Platform
 > independent patch.
 > Tested on: i386, motherboard ASUS P4P8X, mice Logitech MX300 and Logitech
 > G5, game ezQuake 1.9.
 >
 > >Description:
 >
 > Add "options UMS_HZ=<INT_VALUE>" in kernel config.
 > USB mouse rate: value from 1 to 1000, other values set default rate - mouse
 > specific. Most mice suport till 250Hz and 500Hz. Greater value - smoother
 > movements. Some of "professional gaming" mice support 1000Hz and have
 > default rate 500Hz. User can to change this value using sysctl
 > hw.usb.ums.hz.
 > For applying it user must take out mouse and insert it back.
 >
 > >How-To-Repeat:
 >
 > Use usb mouse. :-D
 >
 > >Fix:
 >
 > --- ums_hz.diff begins here ---
 > --- sys/conf/options.orig	2008-07-01 04:22:39.000000000 +0400
 > +++ sys/conf/options	2008-07-01 04:22:45.000000000 +0400
 > @@ -621,6 +621,7 @@
 >  UPLCOM_INTR_INTERVAL	opt_uplcom.h
 >  UVSCOM_DEFAULT_OPKTSIZE	opt_uvscom.h
 >  UVSCOM_INTR_INTERVAL	opt_uvscom.h
 > +UMS_HZ			opt_ums.h
 >
 >  # Embedded system options
 >  INIT_PATH
 > --- sys/dev/usb/ums.c.orig	2008-06-16 19:51:35.000000000 +0400
 > +++ sys/dev/usb/ums.c	2008-07-01 04:23:41.000000000 +0400
 > @@ -69,6 +69,13 @@
 >
 >  #include <sys/mouse.h>
 >
 > +#include "opt_ums.h"
 > +#ifdef UMS_HZ
 > +static int ums_hz = UMS_HZ;
 > +SYSCTL_NODE(_hw_usb, OID_AUTO, ums, CTLFLAG_RW, 0, "USB ums");
 > +SYSCTL_INT(_hw_usb_ums, OID_AUTO, hz, CTLFLAG_RW, &ums_hz, 0, "");
 > +#endif
 > +
 >  #ifdef USB_DEBUG
 >  #define DPRINTF(x)	if (umsdebug) printf x
 >  #define DPRINTFN(n,x)	if (umsdebug>(n)) printf x
 > @@ -700,7 +707,12 @@
 >  	err = usbd_open_pipe_intr(sc->sc_iface, sc->sc_ep_addr,
 >  				USBD_SHORT_XFER_OK, &sc->sc_intrpipe, sc,
 >  				sc->sc_ibuf, sc->sc_isize, ums_intr,
 > -				USBD_DEFAULT_INTERVAL);
 > +#ifdef UMS_HZ
 > +				(ums_hz > 0 && ums_hz <= 1000) ? 1000 / ums_hz : USBD_DEFAULT_INTERVAL
 > +#else
 > +				USBD_DEFAULT_INTERVAL
 > +#endif
 > +				);
 >  	if (err) {
 >  		DPRINTF(("ums_enable: usbd_open_pipe_intr failed, error=%d\n",
 >  			 err));
 > --- sys/conf/NOTES.orig	2008-07-02 01:00:01.000000000 +0400
 > +++ sys/conf/NOTES	2008-07-02 01:06:12.000000000 +0400
 > @@ -2431,6 +2431,12 @@
 >  device		umodem
 >  # USB mouse
 >  device		ums
 > +# USB mouse rate (1 to 1000, other values set default rate - mouse
 > specific). +# Most mice suport till 250Hz and 500Hz. Greater value -
 > smoother movements. +# Some of "professional gaming" mice support 1000Hz
 > and have default rate 500Hz. +# You can to change this value using sysctl
 > hw.usb.ums.hz.
 > +# For applying it you must take out mouse and insert it back.
 > +options		UMS_HZ=-1
 >  # Diamond Rio 500 MP3 player
 >  device		urio
 >  # USB scanners
 >
 
 Hi,
 
 If the mouse is LOW speed you should not poll that often. Maybe you need to 
 add a USB speed check (See usbd_get_speed() or something similar.)
 
 --HPS
From rizzo at icir.org  Fri Jul  4 21:38:16 2008
From: rizzo at icir.org (Luigi Rizzo)
Date: Fri Jul  4 21:38:34 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <200807042333.17859.hselasky@c2i.net>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<20080703170700.3b91b8c6@peedub.jennejohn.org>
	<20080703152551.GA73103@onelab2.iet.unipi.it>
	<200807042333.17859.hselasky@c2i.net>
Message-ID: <20080704213959.GA1706@onelab2.iet.unipi.it>

On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote:
> On Thursday 03 July 2008, Luigi Rizzo wrote:
> > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote:
> > > On Thu, 3 Jul 2008 16:07:19 +0200
> > >
> > > Luigi Rizzo <rizzo@icir.org> wrote:
> > > > There was a discussion back in september about adding
> > > > support for basic CDC tty devices in umodem.c.
> > > > This lets you talk to a number of usb devices built around
> > > > microcontrollers (e.g. Atmel), and puts us on par with
> > > > Linux and Windows in terms of supporting these devices.
> > > >
> > > > Because this simply requires the small patch below to the
> > > > probe/attach routine, so if there are no objections I plan to add
> > > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next
> > > > few days.
> 
> What about flow control? Is flow control required for these devices?

the ones I am talking about don't implement any form of flow control.
I suppose they would otherwise match the previous check.

luigi
From hselasky at c2i.net  Fri Jul  4 22:27:15 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Fri Jul  4 22:27:32 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <20080704213959.GA1706@onelab2.iet.unipi.it>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<200807042333.17859.hselasky@c2i.net>
	<20080704213959.GA1706@onelab2.iet.unipi.it>
Message-ID: <200807050028.48942.hselasky@c2i.net>

On Friday 04 July 2008, Luigi Rizzo wrote:
> On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote:
> > On Thursday 03 July 2008, Luigi Rizzo wrote:
> > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote:
> > > > On Thu, 3 Jul 2008 16:07:19 +0200
> > > >
> > > > Luigi Rizzo <rizzo@icir.org> wrote:
> > > > > There was a discussion back in september about adding
> > > > > support for basic CDC tty devices in umodem.c.
> > > > > This lets you talk to a number of usb devices built around
> > > > > microcontrollers (e.g. Atmel), and puts us on par with
> > > > > Linux and Windows in terms of supporting these devices.
> > > > >
> > > > > Because this simply requires the small patch below to the
> > > > > probe/attach routine, so if there are no objections I plan to add
> > > > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next
> > > > > few days.
> >
> > What about flow control? Is flow control required for these devices?
>
> the ones I am talking about don't implement any form of flow control.
> I suppose they would otherwise match the previous check.
>
> luigi

I mean, are you going to upload firmware through these interfaces?

--HPS
From hselasky at c2i.net  Fri Jul  4 22:31:47 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Fri Jul  4 22:32:00 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <20080703152551.GA73103@onelab2.iet.unipi.it>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<20080703170700.3b91b8c6@peedub.jennejohn.org>
	<20080703152551.GA73103@onelab2.iet.unipi.it>
Message-ID: <200807042333.17859.hselasky@c2i.net>

On Thursday 03 July 2008, Luigi Rizzo wrote:
> On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote:
> > On Thu, 3 Jul 2008 16:07:19 +0200
> >
> > Luigi Rizzo <rizzo@icir.org> wrote:
> > > There was a discussion back in september about adding
> > > support for basic CDC tty devices in umodem.c.
> > > This lets you talk to a number of usb devices built around
> > > microcontrollers (e.g. Atmel), and puts us on par with
> > > Linux and Windows in terms of supporting these devices.
> > >
> > > Because this simply requires the small patch below to the
> > > probe/attach routine, so if there are no objections I plan to add
> > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next
> > > few days.

What about flow control? Is flow control required for these devices?

--HPS
From rizzo at icir.org  Fri Jul  4 22:47:33 2008
From: rizzo at icir.org (Luigi Rizzo)
Date: Fri Jul  4 22:47:46 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <200807050028.48942.hselasky@c2i.net>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<200807042333.17859.hselasky@c2i.net>
	<20080704213959.GA1706@onelab2.iet.unipi.it>
	<200807050028.48942.hselasky@c2i.net>
Message-ID: <20080704224918.GA2145@onelab2.iet.unipi.it>

On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote:
> On Friday 04 July 2008, Luigi Rizzo wrote:
> > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote:
> > > On Thursday 03 July 2008, Luigi Rizzo wrote:
> > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote:
> > > > > On Thu, 3 Jul 2008 16:07:19 +0200
> > > > >
> > > > > Luigi Rizzo <rizzo@icir.org> wrote:
> > > > > > There was a discussion back in september about adding
> > > > > > support for basic CDC tty devices in umodem.c.
> > > > > > This lets you talk to a number of usb devices built around
> > > > > > microcontrollers (e.g. Atmel), and puts us on par with
> > > > > > Linux and Windows in terms of supporting these devices.
> > > > > >
> > > > > > Because this simply requires the small patch below to the
> > > > > > probe/attach routine, so if there are no objections I plan to add
> > > > > > this to the system (CURRENT then RELENG_7 and RELENG_6) in the next
> > > > > > few days.
> > >
> > > What about flow control? Is flow control required for these devices?
> >
> > the ones I am talking about don't implement any form of flow control.
> > I suppose they would otherwise match the previous check.
> >
> > luigi
> 
> I mean, are you going to upload firmware through these interfaces?

the OS only know about bytes.

are firmware, software, data or random noise.
if you want to know whether the sam7 uploader works, yes it does.
From chuckr at telenix.org  Sat Jul  5 00:49:14 2008
From: chuckr at telenix.org (Chuck Robey)
Date: Sat Jul  5 00:49:21 2008
Subject: recognizing a usb device
Message-ID: <486EC29D.20108@telenix.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Is there any way to be able to recognizing a filename that the user has given
me as a sub device?  I figure I can try a udbhid ioctl to see if it's a USB HID
device, but is there any other way to recognize a usb device?

Using an ioctl, it just sort of seems like a messy way to do it.  I was sort of
hoping that there might've been some sort of sysctl giving ghe names, but if
there is, I couldn't find it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhuwp0ACgkQz62J6PPcoOkkUwCghk9/RWuzJmvzv3P7FHNli4ns
qMoAn0Y0WSoDS7XyxxDhpDimboPyL587
=rHrm
-----END PGP SIGNATURE-----
From xiaofanc at gmail.com  Sat Jul  5 01:18:02 2008
From: xiaofanc at gmail.com (Xiaofan Chen)
Date: Sat Jul  5 01:18:07 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <20080704213959.GA1706@onelab2.iet.unipi.it>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<20080703170700.3b91b8c6@peedub.jennejohn.org>
	<20080703152551.GA73103@onelab2.iet.unipi.it>
	<200807042333.17859.hselasky@c2i.net>
	<20080704213959.GA1706@onelab2.iet.unipi.it>
Message-ID: <a276da400807041750q7aa04d7va5844d7197230b1a@mail.gmail.com>

On Sat, Jul 5, 2008 at 5:39 AM, Luigi Rizzo <rizzo@icir.org> wrote:
>> What about flow control? Is flow control required for these devices?
>
> the ones I am talking about don't implement any form of flow control.
> I suppose they would otherwise match the previous check.
>

They are many of this device and they do not have flow control.
I got two of them right here. One is for NXP LPC-P2148 and the other
is using Microchip PIC18F USB PICs.

Last time it was discussed here.
http://lists.freebsd.org/pipermail/freebsd-usb/2008-April/004907.html

I've tried the lpcusb based generic CDC-ACM device under
Linux/Windows/NetBSD successfully but not FreeBSD.

Xiaofan
From vvd at quakeworld.ru  Sat Jul  5 02:20:04 2008
From: vvd at quakeworld.ru (VVD)
Date: Sat Jul  5 02:20:11 2008
Subject: usb/125264: [patch] sysctl for set usb mouse rate (very useful
	for gamers - FPS games)
Message-ID: <200807050220.m652K3P6043115@freefall.freebsd.org>

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

From: "VVD" <vvd@quakeworld.ru>
To: <bug-followup@FreeBSD.org>,
	<hselasky@c2i.net>
Cc:  
Subject: Re: usb/125264: [patch] sysctl for set usb mouse rate (very useful for gamers - FPS games)
Date: Sat, 5 Jul 2008 06:10:01 +0400

 Hi,
 
 AFAIK, all mice are LOW speed usb devices. Didn't understand how to use
 usbd_get_speed() for ums - have no field like speed. High rate need only for
 more smooth mouse moving.
 Linux have custom mouse rate patch from ~2.6.1x. Logitech have Setpoint
 drivers for Win with possibility to set mouse rate from 125 to 1000. Time
 for FreeBSD to have this feature. :-]
 
 With best regards.
 
 
From mi at bonkers.video-collage.com  Sat Jul  5 04:02:58 2008
From: mi at bonkers.video-collage.com (Mikhail Teterin)
Date: Sat Jul  5 04:03:04 2008
Subject: USB mouse not seen at boot
Message-ID: <200807050347.m653lOXZ005998@bonkers.video-collage.com>

Hello!

I'm trying to switch a computer from psm- to ums-connected mouse and am
seeing a strange problem.

Although ums_load is enabled in loader.conf, the mouse is not seen at
boot. Its light (it is a laser-based device) remains off, until I unplug
it from the USB-port and then plug back in.

After that everything is dandy, it lights up, and is detected as:

ums0: <ARROW STRONG USB 3D Mouse, class 0/0, rev 1.00/0.10, addr 2> on uhub0
ums0: 5 buttons and Z dir.

Xorg sees it and life is good.

But why does it have to be reconnected every time at boot?

The only "unusual" thing I did with it was setting
moused_nondefault_enable="NO" to prevent moused from ever starting --
this PC starts xdm on boot and does not use text consoles.

Any ideas? Thanks!

	-mi
From hselasky at c2i.net  Sat Jul  5 07:55:33 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Jul  5 07:55:41 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <20080704224918.GA2145@onelab2.iet.unipi.it>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<200807050028.48942.hselasky@c2i.net>
	<20080704224918.GA2145@onelab2.iet.unipi.it>
Message-ID: <200807050957.07900.hselasky@c2i.net>

On Saturday 05 July 2008, Luigi Rizzo wrote:
> On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote:
> > On Friday 04 July 2008, Luigi Rizzo wrote:
> > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote:
> > > > On Thursday 03 July 2008, Luigi Rizzo wrote:
> > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote:
> > > > > > On Thu, 3 Jul 2008 16:07:19 +0200
> > > > > >
> > > > > > Luigi Rizzo <rizzo@icir.org> wrote:
> > > > > > > There was a discussion back in september about adding
> > > > > > > support for basic CDC tty devices in umodem.c.
> > > > > > > This lets you talk to a number of usb devices built around
> > > > > > > microcontrollers (e.g. Atmel), and puts us on par with
> > > > > > > Linux and Windows in terms of supporting these devices.
> > > > > > >
> > > > > > > Because this simply requires the small patch below to the
> > > > > > > probe/attach routine, so if there are no objections I plan to
> > > > > > > add this to the system (CURRENT then RELENG_7 and RELENG_6) in
> > > > > > > the next few days.
> > > >
> > > > What about flow control? Is flow control required for these devices?
> > >
> > > the ones I am talking about don't implement any form of flow control.
> > > I suppose they would otherwise match the previous check.
> > >
> > > luigi
> >
> > I mean, are you going to upload firmware through these interfaces?
>
> the OS only know about bytes.
>
> are firmware, software, data or random noise.
> if you want to know whether the sam7 uploader works, yes it does.
> _______________________________________________
> 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"

Yes, but you know that umodem can drop data, if the buffers overflow ?

--HPS
From rizzo at icir.org  Sat Jul  5 08:05:05 2008
From: rizzo at icir.org (Luigi Rizzo)
Date: Sat Jul  5 08:05:18 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <200807050957.07900.hselasky@c2i.net>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<200807050028.48942.hselasky@c2i.net>
	<20080704224918.GA2145@onelab2.iet.unipi.it>
	<200807050957.07900.hselasky@c2i.net>
Message-ID: <20080705080649.GA7043@onelab2.iet.unipi.it>

On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote:
> On Saturday 05 July 2008, Luigi Rizzo wrote:
> > On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote:
> > > On Friday 04 July 2008, Luigi Rizzo wrote:
> > > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote:
> > > > > On Thursday 03 July 2008, Luigi Rizzo wrote:
> > > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote:
> > > > > > > On Thu, 3 Jul 2008 16:07:19 +0200
> > > > > > >
> > > > > > > Luigi Rizzo <rizzo@icir.org> wrote:
> > > > > > > > There was a discussion back in september about adding
> > > > > > > > support for basic CDC tty devices in umodem.c.
> > > > > > > > This lets you talk to a number of usb devices built around
> > > > > > > > microcontrollers (e.g. Atmel), and puts us on par with
> > > > > > > > Linux and Windows in terms of supporting these devices.
> > > > > > > >
> > > > > > > > Because this simply requires the small patch below to the
> > > > > > > > probe/attach routine, so if there are no objections I plan to
> > > > > > > > add this to the system (CURRENT then RELENG_7 and RELENG_6) in
> > > > > > > > the next few days.
> > > > >
> > > > > What about flow control? Is flow control required for these devices?
> > > >
> > > > the ones I am talking about don't implement any form of flow control.
> > > > I suppose they would otherwise match the previous check.
> > > >
> > > > luigi
> > >
> > > I mean, are you going to upload firmware through these interfaces?
> >
> > the OS only know about bytes.
> >
> > are firmware, software, data or random noise.
> > if you want to know whether the sam7 uploader works, yes it does.
> > _______________________________________________
> > 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"
> 
> Yes, but you know that umodem can drop data, if the buffers overflow ?

yes i know. and there is another million things that can go wrong.

bye
luigi
From citycat4 at ngs.ru  Sat Jul  5 11:33:17 2008
From: citycat4 at ngs.ru (Rashid N. Achilov)
Date: Sat Jul  5 11:33:25 2008
Subject: USB mouse not seen at boot
Message-ID: <web-20748642@mx6.intranet.ru>

>Although ums_load is enabled in loader.conf, the mouse is not seen at
>boot. Its light (it is a laser-based device) remains off, until I unplug
>it from the USB-port and then plug back in.

It's so "good" working USB subsystem in FreeBSD. Are you 
using 6.x or 7.x? I had have discussed this issue recently 
- for my 6,3-STABLE I _must_ _each_ _boot_ re-plug 
keyboard to detect it. ROFL. And, of course, USB mouse do 
not work. Last time I see, how to increase filling of 
mails with similar questions - "my mouse does not 
detected", "why I should replug device" and so on. And 
each time I have receive answers, that it's free OS, like 
to do good - do it yourself and similar, that's USB 
subsystem works good and mouse isn't required for server, 
etc.

What a pity.
From ticso at cicely7.cicely.de  Sat Jul  5 17:01:01 2008
From: ticso at cicely7.cicely.de (Bernd Walter)
Date: Sat Jul  5 17:01:14 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <200807050957.07900.hselasky@c2i.net>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<200807050028.48942.hselasky@c2i.net>
	<20080704224918.GA2145@onelab2.iet.unipi.it>
	<200807050957.07900.hselasky@c2i.net>
Message-ID: <20080705162426.GD41487@cicely7.cicely.de>

On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote:
> On Saturday 05 July 2008, Luigi Rizzo wrote:
> > On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote:
> > > On Friday 04 July 2008, Luigi Rizzo wrote:
> > > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote:
> > > > > On Thursday 03 July 2008, Luigi Rizzo wrote:
> > > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote:
> > > > > > > On Thu, 3 Jul 2008 16:07:19 +0200
> > > > > > >
> > > > > > > Luigi Rizzo <rizzo@icir.org> wrote:
> > > > > > > > There was a discussion back in september about adding
> > > > > > > > support for basic CDC tty devices in umodem.c.
> > > > > > > > This lets you talk to a number of usb devices built around
> > > > > > > > microcontrollers (e.g. Atmel), and puts us on par with
> > > > > > > > Linux and Windows in terms of supporting these devices.
> > > > > > > >
> > > > > > > > Because this simply requires the small patch below to the
> > > > > > > > probe/attach routine, so if there are no objections I plan to
> > > > > > > > add this to the system (CURRENT then RELENG_7 and RELENG_6) in
> > > > > > > > the next few days.
> > > > >
> > > > > What about flow control? Is flow control required for these devices?
> > > >
> > > > the ones I am talking about don't implement any form of flow control.
> > > > I suppose they would otherwise match the previous check.
> > > >
> > > > luigi
> > >
> > > I mean, are you going to upload firmware through these interfaces?
> >
> > the OS only know about bytes.
> >
> > are firmware, software, data or random noise.
> > if you want to know whether the sam7 uploader works, yes it does.
> > _______________________________________________
> > 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"
> 
> Yes, but you know that umodem can drop data, if the buffers overflow ?

Do you mean the driver can loose data?
It would be good if this is avoidable somehow.
In fact those beasts have some kind of pseudo flow control in that they
don't ack further packets.
Basicly this is nothing more than using a pair of bulk pipes for raw
data, but under the hood of CDC identification.
I personally only use them for uploading firmware to AT91SAM7*
controllers, as luigi does, but since Windows and Linux have generic
drivers this is quite popular.

-- 
B.Walter <bernd@bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
From onemda at gmail.com  Sat Jul  5 17:19:02 2008
From: onemda at gmail.com (Paul B. Mahol)
Date: Sat Jul  5 17:19:08 2008
Subject: usb/125264: [patch] sysctl for set usb mouse rate (very useful
	for gamers - FPS games)
In-Reply-To: <200807050220.m652K3P6043115@freefall.freebsd.org>
References: <200807050220.m652K3P6043115@freefall.freebsd.org>
Message-ID: <3a142e750807051019w3d3568c0g32605625d27fb470@mail.gmail.com>

On 7/5/08, VVD <vvd@quakeworld.ru> wrote:
> The following reply was made to PR usb/125264; it has been noted by GNATS.
>
> From: "VVD" <vvd@quakeworld.ru>
> To: <bug-followup@FreeBSD.org>,
> 	<hselasky@c2i.net>
> Cc:  
> Subject: Re: usb/125264: [patch] sysctl for set usb mouse rate (very useful
> for gamers - FPS games)
> Date: Sat, 5 Jul 2008 06:10:01 +0400
>
>  Hi,
>  
>  AFAIK, all mice are LOW speed usb devices. Didn't understand how to use
>  usbd_get_speed() for ums - have no field like speed. High rate need only
> for
>  more smooth mouse moving.
>  Linux have custom mouse rate patch from ~2.6.1x. Logitech have Setpoint
>  drivers for Win with possibility to set mouse rate from 125 to 1000. Time
>  for FreeBSD to have this feature. :-]
>  

But what about moused -F option? Is it supported at all by ums driver?


>  With best regards.
>  
>  
> _______________________________________________
> 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 ticso at cicely7.cicely.de  Sat Jul  5 21:50:57 2008
From: ticso at cicely7.cicely.de (Bernd Walter)
Date: Sat Jul  5 21:51:10 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <200807052256.15792.hselasky@c2i.net>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<200807050957.07900.hselasky@c2i.net>
	<20080705162426.GD41487@cicely7.cicely.de>
	<200807052256.15792.hselasky@c2i.net>
Message-ID: <20080705215032.GG41487@cicely7.cicely.de>

On Sat, Jul 05, 2008 at 10:56:14PM +0200, Hans Petter Selasky wrote:
> On Saturday 05 July 2008, Bernd Walter wrote:
> > On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote:
> > >
> > > Yes, but you know that umodem can drop data, if the buffers overflow ?
> >
> > Do you mean the driver can loose data?
> > It would be good if this is avoidable somehow.
> > In fact those beasts have some kind of pseudo flow control in that they
> > don't ack further packets.
> > Basicly this is nothing more than using a pair of bulk pipes for raw
> > data, but under the hood of CDC identification.
> > I personally only use them for uploading firmware to AT91SAM7*
> > controllers, as luigi does, but since Windows and Linux have generic
> > drivers this is quite popular.
> 
> From what I know the TTY layer which umodem uses will dump data when the 
> buffers are full. But it there is some kind of framing in the protocol used, 
> then this is no problem.

Well - the problem is that there is not special protocol.
This technology is used as a general purpose interface for almost every
kind of application that.
Most protocols are using smal transactions, but this is general purpos
after all.
This is quite similar as devices using embedded uart or something like
the FT245 pseudo uart chips from FTDI.
I asume even most modern cell phones don't use real uarts.

I wonder what happens with real USB RS232 with activated RTS/CTS.
The handshake is handled in the USB device and not under FreeBSD,
because the USB devices have too large buffers for the OS to react fast
enough.
Can we loose data as well?
If yes we have a problem there as well.
If not, then there must be some kind of mechanism to sync TTY layer
with the USB transport speed and we can use the same for pseudo uart.

I don't think we should drop data ourself, since we have USB handshake
for speed syncronisation.

-- 
B.Walter <bernd@bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
From hselasky at c2i.net  Sat Jul  5 21:54:46 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sat Jul  5 21:54:52 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <20080705162426.GD41487@cicely7.cicely.de>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<200807050957.07900.hselasky@c2i.net>
	<20080705162426.GD41487@cicely7.cicely.de>
Message-ID: <200807052256.15792.hselasky@c2i.net>

On Saturday 05 July 2008, Bernd Walter wrote:
> On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote:
> > On Saturday 05 July 2008, Luigi Rizzo wrote:
> > > On Sat, Jul 05, 2008 at 12:28:47AM +0200, Hans Petter Selasky wrote:
> > > > On Friday 04 July 2008, Luigi Rizzo wrote:
> > > > > On Fri, Jul 04, 2008 at 11:33:15PM +0200, Hans Petter Selasky wrote:
> > > > > > On Thursday 03 July 2008, Luigi Rizzo wrote:
> > > > > > > On Thu, Jul 03, 2008 at 05:07:00PM +0200, Gary Jennejohn wrote:
> > > > > > > > On Thu, 3 Jul 2008 16:07:19 +0200
> > > > > > > >
> > > > > > > > Luigi Rizzo <rizzo@icir.org> wrote:
> > > > > > > > > There was a discussion back in september about adding
> > > > > > > > > support for basic CDC tty devices in umodem.c.
> > > > > > > > > This lets you talk to a number of usb devices built around
> > > > > > > > > microcontrollers (e.g. Atmel), and puts us on par with
> > > > > > > > > Linux and Windows in terms of supporting these devices.
> > > > > > > > >
> > > > > > > > > Because this simply requires the small patch below to the
> > > > > > > > > probe/attach routine, so if there are no objections I plan
> > > > > > > > > to add this to the system (CURRENT then RELENG_7 and
> > > > > > > > > RELENG_6) in the next few days.
> > > > > >
> > > > > > What about flow control? Is flow control required for these
> > > > > > devices?
> > > > >
> > > > > the ones I am talking about don't implement any form of flow
> > > > > control. I suppose they would otherwise match the previous check.
> > > > >
> > > > > luigi
> > > >
> > > > I mean, are you going to upload firmware through these interfaces?
> > >
> > > the OS only know about bytes.
> > >
> > > are firmware, software, data or random noise.
> > > if you want to know whether the sam7 uploader works, yes it does.
> > > _______________________________________________
> > > 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"
> >
> > Yes, but you know that umodem can drop data, if the buffers overflow ?
>
> Do you mean the driver can loose data?
> It would be good if this is avoidable somehow.
> In fact those beasts have some kind of pseudo flow control in that they
> don't ack further packets.
> Basicly this is nothing more than using a pair of bulk pipes for raw
> data, but under the hood of CDC identification.
> I personally only use them for uploading firmware to AT91SAM7*
> controllers, as luigi does, but since Windows and Linux have generic
> drivers this is quite popular.

From what I know the TTY layer which umodem uses will dump data when the 
buffers are full. But it there is some kind of framing in the protocol used, 
then this is no problem.

--HPS
From ticso at cicely7.cicely.de  Sat Jul  5 22:13:20 2008
From: ticso at cicely7.cicely.de (Bernd Walter)
Date: Sat Jul  5 22:13:27 2008
Subject: may I commit this small umodem patch ?
In-Reply-To: <20080705215032.GG41487@cicely7.cicely.de>
References: <20080703140719.GA72315@onelab2.iet.unipi.it>
	<200807050957.07900.hselasky@c2i.net>
	<20080705162426.GD41487@cicely7.cicely.de>
	<200807052256.15792.hselasky@c2i.net>
	<20080705215032.GG41487@cicely7.cicely.de>
Message-ID: <20080705221247.GH41487@cicely7.cicely.de>

On Sat, Jul 05, 2008 at 11:50:32PM +0200, Bernd Walter wrote:
> On Sat, Jul 05, 2008 at 10:56:14PM +0200, Hans Petter Selasky wrote:
> > On Saturday 05 July 2008, Bernd Walter wrote:
> > > On Sat, Jul 05, 2008 at 09:57:06AM +0200, Hans Petter Selasky wrote:
> > > >
> > > > Yes, but you know that umodem can drop data, if the buffers overflow ?
> > >
> > > Do you mean the driver can loose data?
> > > It would be good if this is avoidable somehow.
> > > In fact those beasts have some kind of pseudo flow control in that they
> > > don't ack further packets.
> > > Basicly this is nothing more than using a pair of bulk pipes for raw
> > > data, but under the hood of CDC identification.
> > > I personally only use them for uploading firmware to AT91SAM7*
> > > controllers, as luigi does, but since Windows and Linux have generic
> > > drivers this is quite popular.
> > 
> > From what I know the TTY layer which umodem uses will dump data when the 
> > buffers are full. But it there is some kind of framing in the protocol used, 
> > then this is no problem.
> 
> Well - the problem is that there is not special protocol.
> This technology is used as a general purpose interface for almost every
> kind of application that.
> Most protocols are using smal transactions, but this is general purpos
> after all.
> This is quite similar as devices using embedded uart or something like
> the FT245 pseudo uart chips from FTDI.
> I asume even most modern cell phones don't use real uarts.
> 
> I wonder what happens with real USB RS232 with activated RTS/CTS.
> The handshake is handled in the USB device and not under FreeBSD,
> because the USB devices have too large buffers for the OS to react fast
> enough.
> Can we loose data as well?
> If yes we have a problem there as well.
> If not, then there must be some kind of mechanism to sync TTY layer
> with the USB transport speed and we can use the same for pseudo uart.
> 
> I don't think we should drop data ourself, since we have USB handshake
> for speed syncronisation.

After rethinking: I only remember having seen TTY layer dropped data
in the receive path and I can't think that it was every reasonable to
do for sending, since the local application can be throttled.
However - we should not receive from USB if our tty buffer can't hold
further data.
It is up to the USB device to drop data if unavoidable, since only the
device itsel can judge.

-- 
B.Walter <bernd@bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
From bugmaster at FreeBSD.org  Mon Jul  7 11:07:08 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Jul  7 11:09:38 2008
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200807071107.m67B78na062211@freefall.freebsd.org>

Current FreeBSD problem reports
Critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
f usb/84750    usb        [hang] 6-BETA2 reboot/shutdown with root_fs on externa
o usb/91629    usb        usbd_abort_pipe() may result in infinite loop

2 problems total.

Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o i386/46371   usb        USB controller cannot be initialized on IBM Netfinity 
o bin/57255    usb        usbd(8) and multi-function devices
o usb/63621    usb        [umass] [panic] USB MemoryStick Reader stalls/crashes 
o usb/67301    usb        [uftdi] [panic] RTS and system panic
o usb/69006    usb        [usbdevs] [patch] Apple Cinema Display hangs USB ports
o usb/71155    usb        [ulpt] misbehaving usb-printer hangs processes, causes
o usb/73307    usb        [panic] Kernel panics on USB disconnect
o usb/74771    usb        [umass] [hang] mounting write-protected umass device a
o usb/75705    usb        [umass] [panic] da0 attach / Optio S4 (with backtrace)
o usb/75797    usb        [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c
o usb/76395    usb        [uhci] USB printer does not work, usbdevs says "addr 0
o usb/77184    usb        [umass] [panic] kernel panic on USB device disconnect,
o usb/77294    usb        [ucom] [panic] ucom + ulpcom panic
o usb/79269    usb        [ohci] USB ohci da0 plug/unplug causes crashes and loc
o usb/79287    usb        [uhci] [hang] UHCI hang after interrupt transfer
o usb/79524    usb        [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa
a usb/79656    usb        [ehci] RHSC interrupts lost
o usb/79722    usb        [ehci] wrong alignments in ehci.h
o usb/80040    usb        [hang] Use of sound mixer causes system freeze with ua
o usb/80361    usb        [umass] [patch] mounting of Dell usb-stick fails
o usb/80829    usb        [modules] [panic] possible panic when loading USB-modu
o usb/80862    usb        [patch] USB locking issues: missing some Giant calls
o usb/82350    usb        [ucom] [panic] null pointer dereference in USB stack
o usb/82520    usb        [udbp] [reboot] Reboot when USL101 connected
s usb/82569    usb        [umass] [panic] USB mass storage plug/unplug causes sy
o usb/82660    usb        [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic
o usb/83504    usb        [kernel] [patch] SpeedTouch USB stop working on recent
o usb/83563    usb        [umass] [panic] Page Fault while detaching Mpman Usb d
f usb/83677    usb        [usb] [request] usb controller often not detected (Sun
o usb/83756    usb        [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe
o usb/83977    usb        [ucom] [panic] ucom1: open bulk out error (addr 2): IN
o usb/84326    usb        [umass] Panic trying to connect SCSI tape drive via US
s usb/84336    usb        [usb] [reboot] instant system reboot when unmounting a
o usb/86767    usb        [umass] [patch] bogus "slice starts beyond end of the 
o usb/88743    usb        [hang] [regression] USB makes kernel hang at boot (reg
s usb/89003    usb        [request] LaCie Firewire drive not properly supported 
o usb/89954    usb        [umass] [panic] USB Disk driver race condition?
o usb/90700    usb        [umass] [panic] Kernel panic on connect/mount/use umas
o usb/91238    usb        [umass] USB tape unit fails to write a second tape fil
o usb/91283    usb        [boot] [regression] booting very slow with usb devices
o usb/91538    usb        [ulpt] [patch] Unable to print to EPSON CX3500
o usb/91906    usb        [ehci] [hang] FreeBSD hangs while booting with USB leg
o usb/92052    usb        [ulpt] usbd causes defunct process with busy file-hand
o usb/92083    usb        [ural] [panic] panic using WPA on ural NIC in 6.0-RELE
o usb/92142    usb        [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb 
o usb/92171    usb        [panic] panic unplugging Vodafone Mobile Connect (UMTS
o usb/93155    usb        [ulpt] /dev/ulpt0: device busy, USB printer does not w
o usb/93408    usb        [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes 
o usb/93828    usb        [ohci] [panic] ohci causes panic on boot (HP Pavillion
o usb/94384    usb        [panic] kernel panic with usb2 hardware
o usb/94717    usb        [ulpt] Reading from /dev/ulpt can break work of a UHCI
o usb/94897    usb        [panic] Kernel Panic when cleanly unmounting USB disk
s usb/95348    usb        [keyboard] USB keyboard unplug causes noise on screen
o usb/95562    usb        [umass] Write Stress in USB Mass drive causes "vinvalb
s usb/95636    usb        [umass] [boot] 5 minute delay at boot when using VT620
s usb/96120    usb        [ums] [request] USB mouse not always detected
o usb/96224    usb        [usb] [msdosfs] mount_msdosfs cause page fault in sync
o usb/96457    usb        [umass] [panic] fatback on umass = reboot
s usb/97286    usb        [mouse] [request] MS Wireless Intellimouse Explorer 2.
o usb/99431    usb        [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar
o usb/101096   usb        [ural] [panic] USB WLAN occasionally causes kernel-pan
o usb/101448   usb        [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O
o usb/101752   usb        [umass] [panic] 6.1-RELEASE kernel panic on usb device
o usb/102066   usb        [ukbd] usb keyboard and multimedia keys don't work
f usb/102096   usb        [patch] usbd(8) does not handle multiple devices in on
o usb/103025   usb        [uhub] [panic] wrong detection of USB device for FreeB
o usb/104292   usb        [umass] [hang] system lockup on forced umount of usb-s
o usb/104830   usb        [umass] system crashes when copying data to umass devi
o usb/105186   usb        [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c
o usb/106615   usb        [uftdi] uftdi module does not automatically load with 
o usb/106648   usb        [umass] [hang] USB Floppy on D1950 10 min Hang on Inse
s usb/106832   usb        USB HP printer is not detected by kernel when ACPI ena
o usb/107248   usb        [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP
o usb/107446   usb        [umass] umass problems (usb and fw disks)
o usb/107827   usb        [ohci] [panic] ohci_add_done addr not found
o usb/107848   usb        [umass] [request] cannot access Samsung flash disk
o usb/107924   usb        [patch] usbd(8) does not call detach
o usb/108513   usb        [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr
o usb/109274   usb        [usb] MCP55 USB Controller fails to attach in AMD64 Cu
o usb/109397   usb        [panic] on boot from USB flash
o usb/110856   usb        [ugen] [patch] interrupt in msgs are truncated when bu
o usb/110988   usb        [umass] [patch] Handling of quirk IGNORE_RESIDUE is um
o usb/111753   usb        [uhid] [panic] Replicable system panic involving UHID 
s usb/112568   usb        [umass] [request] USB mode may wrong when mounting Pla
o usb/112631   usb        [panic] Problem with SONY DSC-S80 camera on umount
o usb/112640   usb        [usb] [hang] Kernel freezes when writing a file to an 
s usb/113629   usb        [ukbd] Dropped USB keyboard events on Dell Latitude D6
o usb/113672   usb        [ehci] [panic] Kernel panic with AEWIN CB6971
s usb/113977   usb        [request] Need a way to set mode of USB disk's write c
o usb/114310   usb        [libusb] [patch] [panic] USB hub attachment panics ker
o usb/114682   usb        [umass] generic USB media-card reader unusable
o kern/114780  usb        [uplcom] [panic] Panics while stress testing the uplco
o usb/115298   usb        [ulpt] [panic] Turning off USB printer panics kernel
o usb/116561   usb        [umodem] [panic] RELENG_6 umodem panic "trying to slee
o usb/116699   usb        [usbhid] USB HID devices do not initialize at system b
o usb/116947   usb        [ukbd] [patch] [regression] enable boot protocol on th
o usb/117200   usb        [ugen] ugen0 prints strange string on attach if detach
o usb/117313   usb        [umass] [panic] panic on usb camera insertion
o usb/117613   usb        [uhci] [irq] uhci interrupt storm & USB leaked memory 
o usb/117946   usb        [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE
o usb/117955   usb        [umass] [panic] inserting minolta dimage a2 crashes OS
o usb/118140   usb        [ucom] [patch] quick hack for ucom to get it behave wi
o usb/118141   usb        [ucom] usb serial and nokia phones ucomreadcb ucomread
o usb/118353   usb        [panic] [ppp] repeatable kernel panic during ppp(4) se
o usb/118480   usb        [umass] Timeout in USB mass storage freezes vfs layer 
o usb/119201   usb        [cam] [patch] Quirks for Olympus FE-210 camera, LG and
o usb/119481   usb        [hang] FreeBSD not responding after connecting USB-Mas
o usb/119509   usb        USB flaky on Dell Optiplex 755
o usb/119513   usb        [irq] inserting dlink dwl-g630 wireless card results i
o usb/119977   usb        [ums] Mouse does not work in a Cherry-USB keyboard/mou
o usb/120017   usb        [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk
o usb/120034   usb        [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 
o usb/120283   usb        [panic] Automation reboot with wireless keyboard & mou
o usb/120321   usb        [hang] System hangs when transferring data to WD MyBoo
o usb/120729   usb        [panic] fault while in kernel mode with connecting USB
o usb/120786   usb        Kernel panic when forced umount of a dettached USB Har
o usb/121232   usb        remove PCCARD rebooted system
o usb/121275   usb        [boot] FreeBSD fails to boot with usb legacy support e
o usb/121474   usb        [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard
o usb/121708   usb        [keyboard] nforce 650i mobo w/ usb keyboard infinite k
o usb/121734   usb        [ugen] ugen HP1022 printer device not working since up
o usb/121755   usb        [ohci] [patch] Fix panic after ohci/uhub cardbus devic
o usb/122483   usb        [panic] [ulpt] Repeatable panic in 7.0-STABLE
o usb/122539   usb        [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci
o usb/122905   usb        [ubsa] [patch] add Huawei E220 to ubsa
o kern/123510  usb        [ums] Mouse Wheel Fails to Work [regression]
o usb/123690   usb        Panic on USB device insertion when usb loaded as a mod
o usb/123714   usb        Panic when hald-storage-probe runs with umass device i
o usb/124708   usb        [panic] Kernel panic on USB KVM reattach
o usb/124758   usb        rum panics SMP kernel
o kern/124777  usb        [ucom] USB cua devices don't revert to tty devices whe
o usb/124980   usb        [panic] kernel panic on detaching unmounted umass devi
o usb/125088   usb        Touchpad not detected on Adesso AKB-430UG USB kbd/pad 

133 problems total.

Non-critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o conf/30929   usb        [usb] [patch] use usbd to initialize USB ADSL modem
o usb/40948    usb        [umass] [request] USB HP CDW8200 does not work
s usb/51958    usb        [urio] [patch] update for urio driver
s usb/52026    usb        [usb] [request] umass driver support for InSystem ISD2
o usb/59698    usb        [keyboard] [patch] Rework of ukbd HID to AT code trans
s usb/62257    usb        [umass] [request] card reader UCR-61S2B is only half-s
o usb/66547    usb        [ucom] Palm Tungsten T USB does not initialize correct
o usb/68232    usb        [ugen] [patch] ugen(4) isochronous handling correction
o usb/70523    usb        [umct] [patch] umct sending/receiving wrong characters
o usb/71280    usb        [aue] aue0 device (linksys usb100tx) doesn't work in 1
o usb/71416    usb        [ugen] Cryptoflex e-gate USB token (ugen0) detach is n
o usb/71417    usb        [ugen] Cryptoflex e-gate USB token (ugen0) communicati
o usb/71455    usb        [umass] Slow USB umass performance of 5.3
s usb/72733    usb        [ucom] [request] Kyocera 7135 Palm OS connection probl
o usb/74211    usb        [umass] USB flash drive causes CAM status 0x4 on 4.10R
a usb/74453    usb        [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL
o usb/75764    usb        [umass] [patch] "umass0: Phase Error" - no device for 
o usb/75800    usb        [ucom] ucom1: init failed STALLED error in time of syn
s usb/75928    usb        [umass] [request] Cytronix SmartMedia card (SMC) reade
o usb/76461    usb        [umass] disklabel of umass(4)-CAM(4)-da(4) not used by
o usb/76653    usb        [umass] [patch] Problem with Asahi Optical usb device 
o usb/76732    usb        Mouse problems with USB KVM Switch
o usb/78984    usb        [umass] [patch] Creative MUVO umass failure
o usb/79723    usb        [usb] [request] prepare for high speed isochronous tra
o usb/80774    usb        [patch] have "usbd_find_desc" in line with the other "
s usb/80776    usb        [udav] [request] UDAV device driver shouldn't use usb_
s usb/80777    usb        [request] usb_rem_task() should wait for callback to c
o usb/80854    usb        [patch] [request] suggestion for new iface-no-probe me
o usb/80935    usb        [uvisor] [patch] uvisor.c is not work with CLIE TH55.
o usb/81621    usb        [ehci] [hang] external hd hangs under load on ehci
o usb/83863    usb        [ugen] Communication problem between opensc/openct via
s usb/85067    usb        [uscanner] Cannot attach ScanJet 4300C to usb device
o usb/86298    usb        [mouse] Known good USB mouse won't work with correct s
o usb/87224    usb        Cannot mount USB Zip750
o usb/87648    usb        [mouse] Logitech USB-optical mouse problem.
o usb/88408    usb        [axe] axe0 read PHY failed
o usb/91546    usb        [umodem] [patch] Nokia 6630 mobile phone does not work
o usb/91811    usb        [umass] Compact Flash in HP Photosmart 2610 return  " 
o usb/91896    usb        camcontrol(8): Serial Number of USB Memory Sticks is n
o usb/92852    usb        [ums] [patch] Vertical scroll not working properly on 
o usb/93389    usb        [umass] [patch] Digital Camera Pentax S60 don't work
o usb/93872    usb        [cam] [patch] SCSI quirk required for ELTA 8061 OL USB
o usb/95037    usb        [umass] USB disk not recognized on hot-plug.
o usb/96381    usb        [cam] [patch] add a quirk table entry for a flash ram 
o usb/97175    usb        [umass] [hang] USB cardreader hangs system
o usb/97472    usb        [cam] [patch] add support for Olympus C150,D390
o usb/98343    usb        [boot] BBB reset failed errors with Creative Muvo MP3 
o usb/99538    usb        [keyboard] while using USB keyboard default params of 
o usb/100746   usb        [keyboard] system does not boot due to USB keyboard pr
o usb/101761   usb        [usb] [patch] [request] usb.h: increase maximal size o
o usb/101775   usb        [libusbhid] [patch] possible error in report descripto
o usb/102678   usb        [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not 
o usb/102976   usb        [panic] Casio Exilim Digital Camera causes panic on in
o usb/103046   usb        [ulpt] [patch] ulpt event driven I/O with select(2) an
o usb/103289   usb        [request] USB 2.0 problems on AMD LX-800 CPU and CS-55
o usb/103418   usb        [usbhidctl] [patch] [request] usbhidctl: add ability t
o usb/103917   usb        [uhub] USB driver reports "Addr 0 should never happen"
o usb/104290   usb        [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto
o usb/104352   usb        [ural] [patch] ural driver doesnt work
o usb/104645   usb        [umass] [request] Rave C-201 MP3 player does not commu
o usb/105065   usb        [ata] SATA - USB Bridge
o usb/105361   usb        [panic] Kernel panic during unmounting mass storage (C
o usb/106041   usb        [usb] [request] FreeBSD does not recognise Mustek Bear
o usb/106621   usb        [axe] [patch] DLINK DUB-E100 support broken
o usb/106861   usb        [usbdevs] [patch]: usbdevs update: Add product ACER Ze
o usb/107243   usb        [cam] [patch] Apacer USB Flash Drive quirk
o usb/107388   usb        [patch] [request] new driver: add utoppy device from N
o usb/107496   usb        [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [
o usb/107935   usb        [uplcom] [panic] panic while accessing /dev/cuaU0
o usb/108056   usb        [ohci] Mouse gets powered off during device probe when
s usb/108344   usb        [panic] kernel with atausb panics when unplugging USB 
o usb/110197   usb        [umass] Sony PSP umass device does not detach from EHC
s usb/110991   usb        [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends
o usb/112461   usb        [ehci] [request] ehci USB 2.0 doesn't work on nforce4
o usb/112463   usb        [umass] problem with Samsung USB DVD writer, libscg an
o usb/112944   usb        [ulpt] [patch] Bi-directional access to HP LaserJet 10
o usb/113060   usb        [usbdevs] [patch] Samsung printer not working in bidir
o usb/113432   usb        [ucom] WARNING: attempt to net_add_domain(netgraph) af
o conf/114013  usb        [patch] WITHOUT_USB allow to compil a lot of USB stuff
o usb/114068   usb        [umass] [patch] Problems with connection of the umass 
o usb/114916   usb        [umass] [patch] USB Maxtor drive (L300RO) requires qui
o usb/115400   usb        [ehci] Problem with EHCI on ASUS M2N4-SLI
o usb/115933   usb        [uftdi] [patch] RATOC REX-USB60F (usb serial converter
o usb/115935   usb        [usbdevs] [patch] kernel counterproductively attaches 
o usb/116282   usb        [ulpt] Cannot print on USB HP LJ1018 or LJ1300
o usb/117075   usb        [scsi_da] [patch] quirk: USB Samsung YP-U3 MP3
o usb/117183   usb        [panic] USB/fusefs -- panic while transferring large a
o usb/117185   usb        [umodem] [patch] Add support for UNION interface descr
o usb/117205   usb        [uscanner] [patch] uscanner support for HP ScanJet 447
o usb/117546   usb        [uftdi] [patch] Add MaxStream ZigBee product ID to uft
o usb/117598   usb        [uaudio] [patch] Not possible to record with Plantroni
o usb/117893   usb        [umass] Lacie USB DVD writing failing
o usb/117911   usb        [ums] [request] Mouse Gembird MUSWC not work
o usb/117938   usb        [ums] [patch] Adding support for MS WL Natural and MS 
o usb/118098   usb        [umass] 6th gen iPod causes problems when disconnectin
o usb/118485   usb        [usbdevs] [patch] Logitech Headset Workaround
o usb/118686   usb        [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei
o usb/119150   usb        [usbdevs] [patch] new usbdevs for CDMA 1xEVDO devices
o usb/119227   usb        [ubsa] [patch] ubsa buffer is too small; should be tun
o usb/119389   usb        [umass] Sony DSC-W1 CBI reset failed, STALLED [regress
o usb/119633   usb        [umass] umass0: BBB reset failed, IOERROR [regression]
o usb/119653   usb        [cam] [patch] iriver s7 player sync cache error patch
o usb/119981   usb        [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab
o usb/120572   usb        [umass] [patch] quirk to support ASUS P535 as umass (a
o usb/121045   usb        [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS
o usb/121169   usb        [umass] Issues with usb mp3 player
o usb/121184   usb        [uipaq] [patch] add ids from linux ipaq driver (plus a
o usb/121426   usb        [patch] [uscanner] add HP ScanJet 3570C
o usb/122025   usb        [patch] uscanner does not attach to Epson RX620 printe
o usb/122119   usb        [umass] umass device causes creation of daX but not da
o usb/122547   usb        [ehci] USB Printer not being recognized after reboot
p usb/122610   usb        Add Verizon v740 support to ubsa(4)
o usb/122621   usb        [patch] [request] New driver for Sierra Wireless 3G US
o usb/122712   usb        [usbdevs] [patch] Sony Vaio RF keyboard/mouse receiver
o usb/122813   usb        [udbp] [request] udbp driver should be removed in favo
o usb/122819   usb        Patch to provide dynamic additions to the usb quirks t
o usb/122936   usb        [ucom][ubsa] Device does not receive interrupt
o usb/122956   usb        Support for Novatel Wireless XU870 3G Card
o usb/122992   usb        MotoROKR Z6 Phone not recognised by umass as USB disk.
p usb/123148   usb        [uscanner] [patch] Epson DX8400/50 needs uscanner to s
p usb/123211   usb        [udav] if_udav driver doesn't support Davicom 9601 USB
o kern/123224  usb        [ums] Scroll wheel breakage w/ USB MS Wireless Intelli
o usb/123351   usb        Add Reiner SCT cyberJack, Omnikey [26]020, Fujitsu Sie
o usb/123352   usb        Add Option GTMAX3.6/7.2 and Quallcomm MMC module devic
o usb/123509   usb        [umass] continuous reset Samsung SGH-G600 phone
o usb/123611   usb        [usb] BBB reset failed, STALLED from Imation/Mitsumi U
o usb/123691   usb        usbd(8): usbd hangs
o usb/123959   usb        [ums] add support for Razer Lachesis 4000dpi usb mouse
o usb/123969   usb        Supermicro H8SMi-2 usb problem
o usb/124604   usb        Wireless Mouse doesn't work
o usb/125072   usb        [uplcom] [patch] add Mobile Action MA-620 Infrared Ada
o usb/125238   usb        Habu Mouse turns off in X
o usb/125264   usb        [patch] sysctl for set usb mouse rate (very useful for

133 problems total.

From vvd at quakeworld.ru  Mon Jul  7 19:26:34 2008
From: vvd at quakeworld.ru (VVD)
Date: Mon Jul  7 19:26:41 2008
Subject: usb/125264: [patch] sysctl for set usb mouse rate (very useful
	for gamers - FPS games)
In-Reply-To: <3a142e750807051019w3d3568c0g32605625d27fb470@mail.gmail.com>
Message-ID: <006601c8e05e$f7753360$1b00000a@unislabs.local>


Can't use sc->mode.rate instead sysctl hw.usb.ums.
ums always get 0 value in sc->mode.rate.
Better way is -F, of course, instead sysctl hw.usb.ums, but I don't know why
ums always get sc->mode.rate with value 0... :-(


-----Original Message-----
From: Paul B. Mahol [mailto:onemda@gmail.com] 
Sent: Saturday, July 05, 2008 9:19 PM
To: VVD
Cc: freebsd-usb@freebsd.org
Subject: Re: usb/125264: [patch] sysctl for set usb mouse rate (very useful
for gamers - FPS games)


On 7/5/08, VVD <vvd@quakeworld.ru> wrote:
> The following reply was made to PR usb/125264; it has been noted by GNATS.
>
> From: "VVD" <vvd@quakeworld.ru>
> To: <bug-followup@FreeBSD.org>,
> 	<hselasky@c2i.net>
> Cc:  
> Subject: Re: usb/125264: [patch] sysctl for set usb mouse rate (very 
> useful for gamers - FPS games)
> Date: Sat, 5 Jul 2008 06:10:01 +0400
>
>  Hi,
>  
>  AFAIK, all mice are LOW speed usb devices. Didn't understand how to 
> use
>  usbd_get_speed() for ums - have no field like speed. High rate need 
> only for  more smooth mouse moving.
>  Linux have custom mouse rate patch from ~2.6.1x. Logitech have 
> Setpoint  drivers for Win with possibility to set mouse rate from 125 
> to 1000. Time  for FreeBSD to have this feature. :-]
>  

But what about moused -F option? Is it supported at all by ums driver?


>  With best regards.


From pschmehl_lists at tx.rr.com  Tue Jul  8 18:56:30 2008
From: pschmehl_lists at tx.rr.com (Paul Schmehl)
Date: Tue Jul  8 19:19:25 2008
Subject: UMASS problem on 7.0 STABLE
Message-ID: <91D5108989A3D7EC5803650C@utd65257.utdallas.edu>

IMPORTANT! This message has been blind-carbon-copied to you.
Do not reply-to-all or forward it without the author's permission.

Ever since I upgraded this workstation to 7.0 STABLE, I have been unable to 
reboot with my USB hard drive attached.  During the boot sequence, the device 
is properly detected and identified, but then I get an error message, a crash 
dump and a reboot.  I enabled /var/log/console.log in the hope that I would 
catch the error message, but it doesn't appear in the log.  I also don't have 
any kernel dumps, so I can't trace those to see what the problem might be.

An additional problem that I have is that, during boot, the system says there 
is no dump device available.  This is despite the fact that swap is twice the 
real memory size and /etc/defaults/rc.conf defines dumpdev as auto.  I even 
tried defining dumpdev as the swap partition (in /etc/rc.conf), but nothing 
changed.

I have to be doing something wrong, but I'm at a loss to know what it is.  I've 
rebuilt world and kernel nine times now, in the desparate hope that something 
might have changed in the usb code that would solve this problem.  (Every time 
"#find /usr/src -newer /boot/kernel" returns changes in the usb code, I rebuild 
kernel and world.)

Is there something I can enable that will capture the boot sequence during a 
failed boot while devices are still being detected?

# grep -i umass /var/log/console.log


Any helpful hints would be gratefully appreciated.

# uname -a
FreeBSD utd65257.utdallas.edu 7.0-STABLE FreeBSD 7.0-STABLE #8: Mon Jul  7 
10:41:03 CDT 2008     root@utd65257.utdallas.edu:/usr/obj/usr/src/sys/GENERIC 
i386

# sysctl -a | grep hw.physmem
hw.physmem: 3474407424

# dmesg | grep -i umass
umass0: <Maxtor Corporation Maxtor 3200, class 0/0, rev 2.00/0.01, addr 2> on 
uhub5
da0 at umass-sim0 bus 0 target 0 lun 0

# grep swap /etc/fstab
/dev/ad8s1b             none            swap    sw              0       0

# swapctl -l
Device:       1024-blocks     Used:
/dev/ad8s1b     8388608         0

# grep -i usb /var/run/dmesg.boot
uhci0: <UHCI (generic) USB controller> port 0xff20-0xff3f irq 16 at device 26.0 
on pci0
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhci1: <UHCI (generic) USB controller> port 0xff00-0xff1f irq 17 at device 26.1 
on pci0
usb1: <UHCI (generic) USB controller> on uhci1
usb1: USB revision 1.0
uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfebd9c00-0xfebd9fff irq 22 at 
device 26.7 on pci0
usb2: waiting for BIOS to give up control
usb2: EHCI version 1.0
usb2: wrong number of companions (3 != 2)
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <EHCI (generic) USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2
ums0: <Logitech Optical USB Mouse, class 0/0, rev 2.00/3.40, addr 4> on uhub3
uhci2: <UHCI (generic) USB controller> port 0xff80-0xff9f irq 23 at device 29.0 
on pci0
usb3: <UHCI (generic) USB controller> on uhci2
usb3: USB revision 1.0
uhub4: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhci3: <UHCI (generic) USB controller> port 0xff60-0xff7f irq 17 at device 29.1 
on pci0
usb4: <UHCI (generic) USB controller> on uhci3
usb4: USB revision 1.0
uhub5: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhci4: <UHCI (generic) USB controller> port 0xff40-0xff5f irq 18 at device 29.2 
on pci0
usb5: <UHCI (generic) USB controller> on uhci4
usb5: USB revision 1.0
uhub6: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb5
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xff980800-0xff980bff irq 23 at 
device 29.7 on pci0
usb6: waiting for BIOS to give up control
usb6: timed out waiting for BIOS
usb6: EHCI version 1.0
usb6: companion controllers, 2 ports each: usb3 usb4 usb5
usb6: <EHCI (generic) USB 2.0 controller> on ehci1
usb6: USB revision 2.0
uhub7: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb6

-- 
Paul Schmehl
As if it wasn't already obvious,
my opinions are my own and not
those of my employer.

From goaengel at gmx.net  Wed Jul  9 21:01:08 2008
From: goaengel at gmx.net (Tino Engel)
Date: Wed Jul  9 21:01:14 2008
Subject: Quirks
Message-ID: <20080709223926.142cbe5b@gmx.net>

Dear all,

I had the chance to write my first Quirk-PR and therefore took some
time looking at the FreeBSD usb system.
I am thinking that the solution there is is not the ideal
one. Through mailing list discussions I read, I also have the
impression, that the usb part of the cam subsystem is kind of a problem
child.
I read through parts of the usb code and am kind of understanding it.
So I am trying to make an attempt to help improving it. That means,
that I would like to discuss some ideas and in case this is wanted,
volunteer to do some coding.

What I was thinking so far is:

Since Windows and Linux can handle most of the the devices FreeBSD needs
a quirk for out of the box, and at least in the case of linux, I believe
they do not hold all quirks in a db, there must be a way of doing it.

My idea so far is to do something like this:
- When a usb device is connected, try to use it without quirks.
- If it stalls, cache device id data
- Then emulate a disconnect/connect
- Then try all permutations of possible quirks (most common to less
common?) for the device
- As soon as one permutation causes device not to stall -> done

Anyhow my knowledge concerning the topic is not too in-deep, but I would
be happy to gather some feedback concerning my idea and maybe about
other approaches in this area.

Best regards, Tino Engel
From hselasky at c2i.net  Wed Jul  9 21:42:37 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Jul  9 21:42:43 2008
Subject: Quirks
In-Reply-To: <20080709223926.142cbe5b@gmx.net>
References: <20080709223926.142cbe5b@gmx.net>
Message-ID: <200807092344.09985.hselasky@c2i.net>

Hi Tino,

On Wednesday 09 July 2008, Tino Engel wrote:
> Dear all,
>
> I had the chance to write my first Quirk-PR and therefore took some
> time looking at the FreeBSD usb system.
> I am thinking that the solution there is is not the ideal
> one. Through mailing list discussions I read, I also have the
> impression, that the usb part of the cam subsystem is kind of a problem
> child.
> I read through parts of the usb code and am kind of understanding it.
> So I am trying to make an attempt to help improving it. That means,
> that I would like to discuss some ideas and in case this is wanted,
> volunteer to do some coding.
>
> What I was thinking so far is:
>
> Since Windows and Linux can handle most of the the devices FreeBSD needs
> a quirk for out of the box, and at least in the case of linux, I believe
> they do not hold all quirks in a db, there must be a way of doing it.
>
> My idea so far is to do something like this:
> - When a usb device is connected, try to use it without quirks.
> - If it stalls, cache device id data
> - Then emulate a disconnect/connect

Yes, this is possible. But unfortunately some devices are very crappy and even 
if you do a USB BUS reset, they will malfunction after the invalid command, 
simply because the USB software on the dongle has crashed :-) Or the endpoint 
state is not correct.

> - Then try all permutations of possible quirks (most common to less
> common?) for the device
> - As soon as one permutation causes device not to stall -> done

I assume that you are thinking about Mass Storage devices. You might be 
interested in looking at:

http://www.selasky.org/hans_petter/isdn4bsd/sources/src/sys/dev/usb2/core/usb2_msctest.c

>
> Anyhow my knowledge concerning the topic is not too in-deep, but I would
> be happy to gather some feedback concerning my idea and maybe about
> other approaches in this area.

How much time are you willing to spend on this ?

--HPS
From linimon at FreeBSD.org  Thu Jul 10 09:31:03 2008
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Thu Jul 10 09:31:09 2008
Subject: usb/125450: Removing USB flash card while being accessed causes
	kernel panic
Message-ID: <200807100931.m6A9V2AA074065@freefall.freebsd.org>

Old Synopsis: kernel panic
New Synopsis: Removing USB flash card while being accessed causes kernel  panic

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Thu Jul 10 09:28:03 UTC 2008
State-Changed-Why: 
See http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/46176 and subsequent
(e.g. http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html).


Responsible-Changed-From-To: gnats-admin->freebsd-usb
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Jul 10 09:28:03 UTC 2008
Responsible-Changed-Why: 

http://www.freebsd.org/cgi/query-pr.cgi?pr=125450
From goaengel at gmx.net  Thu Jul 10 11:45:32 2008
From: goaengel at gmx.net (Tino Engel)
Date: Thu Jul 10 11:45:38 2008
Subject: Quirks
In-Reply-To: <200807092344.09985.hselasky@c2i.net>
References: <20080709223926.142cbe5b@gmx.net>
	<200807092344.09985.hselasky@c2i.net>
Message-ID: <20080710135033.71c1bf21@gmx.net>

Hi Petter,

On Wed, 9 Jul 2008 23:44:08 +0200
Hans Petter Selasky <hselasky@c2i.net> wrote:


> Hi Tino,
> 
> On Wednesday 09 July 2008, Tino Engel wrote:
> > Dear all,
> >
> > I had the chance to write my first Quirk-PR and therefore took some
> > time looking at the FreeBSD usb system.
> > I am thinking that the solution there is is not the ideal
> > one. Through mailing list discussions I read, I also have the
> > impression, that the usb part of the cam subsystem is kind of a
> > problem child.
> > I read through parts of the usb code and am kind of understanding
> > it. So I am trying to make an attempt to help improving it. That
> > means, that I would like to discuss some ideas and in case this is
> > wanted, volunteer to do some coding.
> >
> > What I was thinking so far is:
> >
> > Since Windows and Linux can handle most of the the devices FreeBSD
> > needs a quirk for out of the box, and at least in the case of
> > linux, I believe they do not hold all quirks in a db, there must be
> > a way of doing it.
> >
> > My idea so far is to do something like this:
> > - When a usb device is connected, try to use it without quirks.
> > - If it stalls, cache device id data
> > - Then emulate a disconnect/connect
> 
> Yes, this is possible. But unfortunately some devices are very crappy
> and even if you do a USB BUS reset, they will malfunction after the
> invalid command, simply because the USB software on the dongle has
> crashed :-) Or the endpoint state is not correct.
> 
> > - Then try all permutations of possible quirks (most common to less
> > common?) for the device
> > - As soon as one permutation causes device not to stall -> done
> 
> I assume that you are thinking about Mass Storage devices. You might
> be interested in looking at:
> 
> http://www.selasky.org/hans_petter/isdn4bsd/sources/src/sys/dev/usb2/core/usb2_msctest.c
> 

Yes, your Assumption is right. I am about mass storage.

I have looked your at the code. 
As far as I can see the whole package it is meant as a replacement for
the existing usb-driver in freebsd. (Correct me if I am wrong)
But it seems to be installed just as an addon... How does that
interfere with what is existing in freebsd?

Can you please tell me a little more about the plans of merging this
into freebsd?

> >
> > Anyhow my knowledge concerning the topic is not too in-deep, but I
> > would be happy to gather some feedback concerning my idea and maybe
> > about other approaches in this area.
> 
> How much time are you willing to spend on this ?
> 
> --HPS

I am willing to spend about 5h a week, from time to time more. (depends
on things like job-workload, weather, etc...) 
Anyhow I am more into doing than into planning, so i would be happy to
help, when some surroundings have been clarified to me.
(i.e. develop on top of what, what to do exactly, etc...)

Greez, Tino
From hselasky at c2i.net  Thu Jul 10 17:08:26 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Jul 10 17:08:34 2008
Subject: Quirks
In-Reply-To: <20080710135033.71c1bf21@gmx.net>
References: <20080709223926.142cbe5b@gmx.net>
	<200807092344.09985.hselasky@c2i.net>
	<20080710135033.71c1bf21@gmx.net>
Message-ID: <200807101809.59532.hselasky@c2i.net>

Hi Tino,

On Thursday 10 July 2008, Tino Engel wrote:
> Hi Petter,
>

>
> Can you please tell me a little more about the plans of merging this
> into freebsd?

Let's focus on getting the USB mass storage problems fixed first. There are 
plenty of USB Mass Storage IR's in the database.

What kind of quirk strategy would you like to apply?

If the device fails the Mass Storage test, then switch on all possible 
quirks ? Which means that the user might have to replug the USB device ?

--HPS
From simsong at acm.org  Thu Jul 10 18:09:55 2008
From: simsong at acm.org (Simson Garfinkel)
Date: Thu Jul 10 18:10:24 2008
Subject: usb/125450: Removing USB flash card while being accessed causes
	kernel panic
In-Reply-To: <200807100931.m6A9V2AA074065@freefall.freebsd.org>
References: <200807100931.m6A9V2AA074065@freefall.freebsd.org>
Message-ID: <502A1816-12E2-4FA1-B955-B049D38DA399@acm.org>

Hi. You did not read my bug report.

This is not a case of a mounted file system causing a panic. I am  
accessing the raw device with DD; the disk is not mounted.


On Jul 10, 2008, at 2:31 AM, linimon@FreeBSD.org wrote:

> Old Synopsis: kernel panic
> New Synopsis: Removing USB flash card while being accessed causes  
> kernel  panic
>
> State-Changed-From-To: open->closed
> State-Changed-By: linimon
> State-Changed-When: Thu Jul 10 09:28:03 UTC 2008
> State-Changed-Why:
> See http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/46176 and  
> subsequent
> (e.g. http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html) 
> .
>
>
> Responsible-Changed-From-To: gnats-admin->freebsd-usb
> Responsible-Changed-By: linimon
> Responsible-Changed-When: Thu Jul 10 09:28:03 UTC 2008
> Responsible-Changed-Why:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=125450
>

From linimon at FreeBSD.org  Thu Jul 10 18:28:34 2008
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Thu Jul 10 18:28:40 2008
Subject: usb/125450: [panic] Removing USB flash card while being
	accessed causes kernel panic, even without device mounted
Message-ID: <200807101828.m6AISXqH021119@freefall.freebsd.org>

Old Synopsis: Removing USB flash card while being accessed causes kernel  panic
New Synopsis: [panic] Removing USB flash card while being accessed causes kernel panic, even without device mounted

State-Changed-From-To: closed->open
State-Changed-By: linimon
State-Changed-When: Thu Jul 10 18:28:01 UTC 2008
State-Changed-Why: 
re-open.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125450
From linimon at lonesome.com  Thu Jul 10 18:30:06 2008
From: linimon at lonesome.com (Mark Linimon)
Date: Thu Jul 10 18:30:11 2008
Subject: usb/125450: Removing USB flash card while being accessed causes
	kernel panic
Message-ID: <200807101830.m6AIU5As021420@freefall.freebsd.org>

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

From: linimon@lonesome.com (Mark Linimon)
To: Simson Garfinkel <simsong@acm.org>
Cc: bug-followup@FreeBSD.org
Subject: Re: usb/125450: Removing USB flash card while being accessed causes kernel panic
Date: Thu, 10 Jul 2008 13:29:02 -0500

 we're going to need a stack trace, as well.
 
 mcl
From simsong at acm.org  Thu Jul 10 19:40:09 2008
From: simsong at acm.org (Simson Garfinkel)
Date: Thu Jul 10 19:40:15 2008
Subject: usb/125450: Removing USB flash card while being accessed causes
	kernel panic
Message-ID: <200807101940.m6AJe9b0028179@freefall.freebsd.org>

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

From: Simson Garfinkel <simsong@acm.org>
To: linimon@lonesome.com (Mark Linimon)
Cc: bug-followup@FreeBSD.org
Subject: Re: usb/125450: Removing USB flash card while being accessed causes kernel panic
Date: Thu, 10 Jul 2008 12:19:00 -0700

 I'm happy to get you a stack trace; it's easy to make this happen. How  
 do I get a stack trace from a kernel panic?
 
 On Jul 10, 2008, at 11:29 AM, Mark Linimon wrote:
 
 > we're going to need a stack trace, as well.
 >
 > mcl
 >
 
From simsong at acm.org  Thu Jul 10 20:14:45 2008
From: simsong at acm.org (Simson Garfinkel)
Date: Thu Jul 10 20:14:52 2008
Subject: usb/125450: Removing USB flash card while being accessed causes
	kernel panic
In-Reply-To: <200807102203.35245.hselasky@c2i.net>
References: <200807101940.m6AJe9b0028179@freefall.freebsd.org>
	<200807102203.35245.hselasky@c2i.net>
Message-ID: <25D09836-2EAC-48D9-88F7-B0279EC5B6A0@acm.org>

Sorry, I've never done this before.

So you want me to build a kernel with options USB_DEBUG and run those  
sysctls after I boot. After the panic, how do I get that stack trace  
from the computer to a disk file? What command should I type?

Regards,


Simson Garfinkel

On Jul 10, 2008, at 1:03 PM, Hans Petter Selasky wrote:

> On Thursday 10 July 2008, Simson Garfinkel wrote:
>> The following reply was made to PR usb/125450; it has been noted by  
>> GNATS.
>>
>> From: Simson Garfinkel <simsong@acm.org>
>> To: linimon@lonesome.com (Mark Linimon)
>> Cc: bug-followup@FreeBSD.org
>> Subject: Re: usb/125450: Removing USB flash card while being accessed
>> causes kernel panic Date: Thu, 10 Jul 2008 12:19:00 -0700
>>
>> I'm happy to get you a stack trace; it's easy to make this happen.  
>> How
>> do I get a stack trace from a kernel panic?
>>
>> On Jul 10, 2008, at 11:29 AM, Mark Linimon wrote:
>>> we're going to need a stack trace, as well.
>>>
>>> mcl
>>
>> _______________________________________________
>> 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"
>
> options USB_DEBUG
>
> and
>
> sysctl hw.usb.umass.debug=-1
> sysctl hw.usb.debug=15
>
> --HPS
>

From hselasky at c2i.net  Thu Jul 10 21:02:10 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Jul 10 21:02:16 2008
Subject: usb/125450: Removing USB flash card while being accessed causes
	kernel panic
In-Reply-To: <200807101940.m6AJe9b0028179@freefall.freebsd.org>
References: <200807101940.m6AJe9b0028179@freefall.freebsd.org>
Message-ID: <200807102203.35245.hselasky@c2i.net>

On Thursday 10 July 2008, Simson Garfinkel wrote:
> The following reply was made to PR usb/125450; it has been noted by GNATS.
>
> From: Simson Garfinkel <simsong@acm.org>
> To: linimon@lonesome.com (Mark Linimon)
> Cc: bug-followup@FreeBSD.org
> Subject: Re: usb/125450: Removing USB flash card while being accessed
> causes kernel panic Date: Thu, 10 Jul 2008 12:19:00 -0700
>
>  I'm happy to get you a stack trace; it's easy to make this happen. How
>  do I get a stack trace from a kernel panic?
>
>  On Jul 10, 2008, at 11:29 AM, Mark Linimon wrote:
>  > we're going to need a stack trace, as well.
>  >
>  > mcl
>
> _______________________________________________
> 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"

options USB_DEBUG

and

sysctl hw.usb.umass.debug=-1
sysctl hw.usb.debug=15

--HPS
From goaengel at gmx.net  Thu Jul 10 22:37:23 2008
From: goaengel at gmx.net (Tino Engel)
Date: Thu Jul 10 22:37:30 2008
Subject: Quirks
In-Reply-To: <200807101809.59532.hselasky@c2i.net>
References: <20080709223926.142cbe5b@gmx.net>
	<200807092344.09985.hselasky@c2i.net>
	<20080710135033.71c1bf21@gmx.net>
	<200807101809.59532.hselasky@c2i.net>
Message-ID: <20080711004223.76d17a7e@gmx.net>

Hi --HPS,

> Hi Tino,
> 
> Let's focus on getting the USB mass storage problems fixed first.
> There are plenty of USB Mass Storage IR's in the database.
> 
> What kind of quirk strategy would you like to apply?
> 
> If the device fails the Mass Storage test, then switch on all
> possible quirks ? Which means that the user might have to replug the
> USB device ?
> 
> --HPS

Here is a map of what I think would be reasonable:


At first there is a file (let's say /etc/ums.conf) which holds the
configuration of how to approach new devices. The file is delivered
with reasonable defaults.


GLOBAL OPTIONS:
===============
If the option ALL_QUIRKS="YES" is set, a new UMS is approached with
all quirks. If something fails here, there is pretty much nothing left
to do.

Also all other quirks can be set on by default:
Example: Q_NO_SYNC_CACHE="YES" would disable cache syncing for all msc
devices.

So, now there more sophisticated part:
In case the all quirks option is not set, 2 cases remain in this model:

CASE 1:
=======

Case 1 describes the case of a MSC device that hangs up
after receiving a command it could not be able to handle. It ends in a
unfixable state, even a bus reset cannot help.

That leads us to the conclusion, the device has to be unplugged in
order to proceed. The only question is, how to proceed then. Also in
this case, the was is determined by configuration.

The easiest case would be given by using the option:
STALLED_ALL_QUIRKS="YES"

Then dmesg would tell to replug the device (and other events would be
triggered, for whatsoever), and all quirks would be applied for this
device from there on. The information would be held in /var/db/ums or
whatever appropriate place.

Additionally one could think about enabling a chained quirk set:
For example I could set STALLED_Q_NO_SYNC_CACHE="1" and
STALLED_ALL_QUIRKS="2" which would have the effect, that for this
specific device, cache syncing would be disabled (quirked) on first
reconnect, and, if failed, all quirks would be activated on next
connect. dmesg would properly inform me to replug.

Nice would also be an option STALLED_INTELLIGENCE="YES" which would try
same order as in case 2.

The successful quirk combination is also stored in /var/db/ums.

In addition, it would be nice to have a vendor/device specific config
format. (e.g. STALLED_Q_NO_SYNC_CACHE="SAMSUNG,1")

This way would have the advantage that my device runs anyhow without
kernel recompilation (although i might have to replug a couple of times
in worst case :-( )

CASE 2:
=======
In case 2, the device can recover by a usb reset. There it is a runtime
issue, if just all quirk permutations can be tested or if a
configuration similar to case 1 is appropriate. (I assume, we can live
with the runtime there, since plugging an usb device is not a
real-time-thing ^^)
Than we can have a nice logic (from most common to less common quirk
permutations order)

Here we should definitely have a config file, containing device
specific quirk information, which can be updated.


Anyhow, feedback events (e.g. for graphical connection tools)
interaction with things like HAL and whatever comes up should be
considered, so it can be implemented sooner or later...


What do you think?

Best regards, Tino

P.S.: Maybe /etc and /var/db is not the right place for things like
this, you probably know better...

P.P.S.: What is an IR (from your last mail)?
From ivoras at freebsd.org  Fri Jul 11 11:06:16 2008
From: ivoras at freebsd.org (Ivan Voras)
Date: Fri Jul 11 11:06:22 2008
Subject: PR 120017
Message-ID: <g57eqt$t26$1@ger.gmane.org>

Hi,

Any objections if I commit a slightly improved version of the patch at
http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/120017 ?

I know a similar functionality has been included in the new "hps" USB
stack but it's kind-of prolonged...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20080711/b6803b79/signature.pgp
From ivoras at freebsd.org  Fri Jul 11 11:10:03 2008
From: ivoras at freebsd.org (Ivan Voras)
Date: Fri Jul 11 11:10:31 2008
Subject: best block size for file systems on USB media ?
In-Reply-To: <200806182026.m5IKQLw5016490@fire.js.berklix.net>
References: <200806180148.46908.hselasky@c2i.net>
	<200806182026.m5IKQLw5016490@fire.js.berklix.net>
Message-ID: <g57eta$t26$2@ger.gmane.org>

Julian Stacey wrote:

> But what if the internal stick hardware works on say 10K chunks ?
> is there anyone on this list who knows how USB sticks work internaly ?
> ( I remember at least one chap some time back, on some freebsd list,
> being quite authoritative on max read write patterns before failure,
> maybe he knows about blocking & if there's cache too ? )

I think PHK knows what you need - he was the one usually delivering
low-level details on flash memory in previous discussions. (If you're
going to ask him, it would be nice if you asked on a list, I'm
interested in the same subject).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20080711/f9a7f8b0/signature.pgp
From synthetic.youth at gmail.com  Fri Jul 11 14:20:02 2008
From: synthetic.youth at gmail.com (Alexander Kozlov)
Date: Fri Jul 11 14:20:09 2008
Subject: AnyDATA ADU-500A speed/stalled/panic
Message-ID: <7ca5745b0807110653q240ea42cx9151df8305f4b218@mail.gmail.com>

   Hi.

I have some problems with USB CDMA modem AnyDATA ADU-500A.
I'm running FreeBSD 7.0 RELEASE rebuilt with GENERIC conf and patch to
recognize this modem. I took patch from
http://www.freebsd.org/cgi/query-pr.cgi?pr=118479

Device is recognized as
ucom0: <AnyDATA Corporation AnyDATA CDMA Products, class 0/0, rev
1.10/0.00, addr 2> on uhub1

1. The first issue is 'ucom0: ubsa_request: STALLED' messages.

I have these messaged when dailing with ppp
ucom0: ubsa_request: STALLED
ucom0: ubsa_request: STALLED
ucom0: ubsa_request: STALLED
ucom0: ubsa_request: STALLED
ucom0: ubsa_request: STALLED
ucom0: ubsa_request: STALLED
ucom0: ubsa_request: STALLED

But I have device connected to internet. A lot of such messages I got
when notebook is idle for some time.

2. Second is speed issue. I never get more than 29 KByte/sec. But at
Windows XP SP3 and Ubuntu 8.04 I have up to 100 KByte/sec. As far as I
know this is the limit for my location.
I managed to have 100 KByte by patching ubsa.c: tuning ibuzsize and
obufsize. I partially applied patch from
http://lists.freebsd.org/pipermail/freebsd-usb/2008-January/004298.html

Is this correct way to resolve speed issue?

3. Third and most painfull is system crash. It happens when device is
used by several apps or when downloading at high speed. I got

kernel: panic: uhci_abort_xfer: not in process context

Panic happens and without speed issue patch. Crashes never happen when
device is idle and there's no internet traffic.

I' sure this device has no hardware issues because it works well at
Windows and Ubuntu. I can provide any information you need. I'm newbie
to FreeBSD and unix world but have some skill at C/C++ programming. I
want to have this device working under FreeBSD and ready to spend as
much time as needed.

Thank you in advance, and sorry for mangled english.
From seth.hutchins at baesystems.com  Fri Jul 11 15:10:04 2008
From: seth.hutchins at baesystems.com (S. Hutchins)
Date: Fri Jul 11 15:10:20 2008
Subject: usb/125510: repeated plug and unplug of USB mass storage devices
	leads to stall, panics
Message-ID: <200807111504.m6BF4ZG3001112@www.freebsd.org>


>Number:         125510
>Category:       usb
>Synopsis:       repeated plug and unplug of USB mass storage devices leads to stall, panics
>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:   Fri Jul 11 15:10:03 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     S. Hutchins
>Release:        7.0-RELEASE
>Organization:
>Environment:
FreeBSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>Description:
Tested on at least two separate machines, a Shuttle with ICH6 and an Intel Server with an ICH8.

Repeatedly plug and unplug a mass storage device. It doesn't seem to matter what kind. The kernel will panic. There are multiple locations for the panic, but I expect the system state that triggers the panic is related: it's always a NULL dereference, and it's always the result of plugging or unplugging the device, and the EIPs are relatively close.

I have two panics logged on the stock FreeBSD 7 kernel:

The first is a dereference off of NULL faulting address == 0:
EIP = 20:0xc04675b6
Supervisor write, page not present; trap 12 in proc 2 (g_event)

The second is a dereference 0x10 off of NULL, faulting address == 0x10:
EIP = 20:0xc04801e5
Supervisor write, page not present; trap 12 in proc 35 (usb2)

Likewise, if a mass storage device(s) is already plugged in and doing I/O, and another device is plugged and unplugged repeatedly, the I/O on the other device(s) will eventually stall, even if that original device is connected through nested hubs. This can impact multiple devices at once. The message is shown:

<dev>: BBB reset failed, IOERROR
<dev>: BBB bulk-in clear stall failed (TIMEOUT)
<dev>: BBB bulk-out clear stall failed (TIMEOUT)

The device is unresponsive until it is removed and reconnected.
>How-To-Repeat:
To yield a panic, choose a mass storage device at random. Repeatedly plug and unplug the device, especially prior to the system indicating that the device has been detected.

To yield a stall, attach a mass storage device and start non-stop I/O to it. You can also choose to select multiple mass storage devices and have them all do I/O. Plug this device or hub into one port into the EHCI host controller. Repeatedly plug and unplug another mass storage device into an adjacent port. Other ports may work but I believe they must be associated with the same host controller. Eventually I/O on one or more of the connected devices will stall.

>Fix:
Make sure NULL isn't dereferenced, to fix the first set of problems. This may not    be trivial. Apparently the USB driver is subtle and quick to panic.

>Release-Note:
>Audit-Trail:
>Unformatted:
From merao at udm.ru  Fri Jul 11 17:35:53 2008
From: merao at udm.ru (Andrey Merkulov)
Date: Fri Jul 11 17:36:00 2008
Subject: AnyDATA ADU-500A speed/stalled/panic
In-Reply-To: <7ca5745b0807110653q240ea42cx9151df8305f4b218@mail.gmail.com>
References: <7ca5745b0807110653q240ea42cx9151df8305f4b218@mail.gmail.com>
Message-ID: <20080711211637.12504966.merao@udm.ru>

+ 1
I have absolutely same problem ? 3,  when use EV-DO mode (high speed).
My device is USB CDMA Ubiquam U-300

kernel modules:
ucom
umodem
uplcom


On Fri, 11 Jul 2008 16:53:06 +0300
"Alexander Kozlov" <synthetic.youth@gmail.com> wrote:

>    Hi.
> 
> I have some problems with USB CDMA modem AnyDATA ADU-500A.
> I'm running FreeBSD 7.0 RELEASE rebuilt with GENERIC conf and patch to
> recognize this modem. I took patch from
> http://www.freebsd.org/cgi/query-pr.cgi?pr=118479
> 
> Device is recognized as
> ucom0: <AnyDATA Corporation AnyDATA CDMA Products, class 0/0, rev
> 1.10/0.00, addr 2> on uhub1
> 
> 1. The first issue is 'ucom0: ubsa_request: STALLED' messages.
> 
> I have these messaged when dailing with ppp
> ucom0: ubsa_request: STALLED
> ucom0: ubsa_request: STALLED
> ucom0: ubsa_request: STALLED
> ucom0: ubsa_request: STALLED
> ucom0: ubsa_request: STALLED
> ucom0: ubsa_request: STALLED
> ucom0: ubsa_request: STALLED
> 
> But I have device connected to internet. A lot of such messages I got
> when notebook is idle for some time.
> 
> 2. Second is speed issue. I never get more than 29 KByte/sec. But at
> Windows XP SP3 and Ubuntu 8.04 I have up to 100 KByte/sec. As far as I
> know this is the limit for my location.
> I managed to have 100 KByte by patching ubsa.c: tuning ibuzsize and
> obufsize. I partially applied patch from
> http://lists.freebsd.org/pipermail/freebsd-usb/2008-January/004298.html
> 
> Is this correct way to resolve speed issue?
> 
> 3. Third and most painfull is system crash. It happens when device is
> used by several apps or when downloading at high speed. I got
> 
> kernel: panic: uhci_abort_xfer: not in process context
> 
> Panic happens and without speed issue patch. Crashes never happen when
> device is idle and there's no internet traffic.
> 
> I' sure this device has no hardware issues because it works well at
> Windows and Ubuntu. I can provide any information you need. I'm newbie
> to FreeBSD and unix world but have some skill at C/C++ programming. I
> want to have this device working under FreeBSD and ready to spend as
> much time as needed.
> 
> Thank you in advance, and sorry for mangled english.
> _______________________________________________
> 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"


-- 
????? ???? ????
??? ???????? ? ??????????? ?????
?????? ???????? mailto:merao@udm.ru
From vvd at quakeworld.ru  Sun Jul 13 04:13:08 2008
From: vvd at quakeworld.ru (VVD)
Date: Sun Jul 13 04:13:14 2008
Subject: usb/125264: [patch] sysctl for set usb mouse rate (very useful
	for gamers - FPS games)
In-Reply-To: <3a142e750807051019w3d3568c0g32605625d27fb470@mail.gmail.com>
Message-ID: <002d01c8e49e$bc4c1e90$1b00000a@unislabs.local>


I find speed - always LOW (tested on 6 Logitech mice: G5, MX300, RX250 and 3
different 5$-cost mice).
But I wrote another patch:
--- ums.c.orig	2008-06-16 19:51:35.000000000 +0400
+++ ums.c	2008-07-13 07:48:58.000000000 +0400
@@ -673,6 +673,7 @@
 	void *v;
 {
 	struct ums_softc *sc = v;
+	int usb_interval;
 
 	usbd_status err;
 
@@ -696,11 +697,21 @@
 	 */
 	usbd_set_protocol(sc->sc_iface, 1);
 
+	/* 
+	 * Calculate USB interval in ms from rate in Hz (moused command line
option -F).
+	 * Possible values are from 1 to 1000, else use
USBD_DEFAULT_INTERVAL.
+	 * Modern gaming mice have 500Hz by default, other 100Hz or 125Hz.
+	 */
+	usb_interval = (sc->mode.rate > 0 && sc->mode.rate <= 1000) ?
+			1000 / sc->mode.rate : USBD_DEFAULT_INTERVAL;
+	DPRINTF(("ums_enable: mouse rate is %d, usb interval is %d\n",
+		sc->mode.rate, usb_interval));
+
 	/* Set up interrupt pipe. */
 	err = usbd_open_pipe_intr(sc->sc_iface, sc->sc_ep_addr,
 				USBD_SHORT_XFER_OK, &sc->sc_intrpipe, sc,
 				sc->sc_ibuf, sc->sc_isize, ums_intr,
-				USBD_DEFAULT_INTERVAL);
+				usb_interval);
 	if (err) {
 		DPRINTF(("ums_enable: usbd_open_pipe_intr failed,
error=%d\n",
 			 err));
@@ -900,6 +911,29 @@
 			sc->mode.syncmask[1] = MOUSE_SYS_SYNC;
 		}
 
+		/*
+		 * Most modern gaming mice support customized resolution,
but I don't know
+		 * how to set it. For support this feature in
ums_ioctl(MOUSE_SETMODE)
+		 * need to uncomment next line:
+		 * sc->mode.resolution = mode.resolution > 0 ?
+		 *			 mode.resolution :
MOUSE_RES_UNKNOWN;
+		 * and may be call ums_disable() and ums_enable() if
resolution was changed.
+		 */
+
+		/*
+		 * Call ums_disable() and ums_enable() because of what rate
was set in
+		 * ums_enable() and can't to change it on the fly (if can -
how?).
+		 * For example: during moused startup (with options "-F rate
-r resolution")
+		 * 1st call ums_enable() and then ums_ioctl(MOUSE_SETMODE)
and, as result,
+		 * mouse initialized with default values of the rate and
resolution,
+		 * but not with custom from command line.
+		 */
+		if (sc->mode.rate != mode.rate) {
+			sc->mode.rate = mode.rate;
+			ums_disable(sc);
+			ums_enable(sc);
+		}
+
 		bzero(sc->qbuf, sizeof(sc->qbuf));
 		sc->qhead = sc->qtail = sc->qcount = 0;
 		splx(s);


I want to ask about to make another PR with patch:
--- usbdi.c.orig	2008-07-12 20:43:42.000000000 +0400
+++ usbdi.c	2008-07-12 20:43:47.000000000 +0400
@@ -231,23 +231,19 @@
 	xfer = usbd_alloc_xfer(iface->device);
 	if (xfer == NULL) {
 		err = USBD_NOMEM;
-		goto bad1;
-	}
+	} else {
 	usbd_setup_xfer(xfer, ipipe, priv, buffer, len, flags,
 	    USBD_NO_TIMEOUT, cb);
 	ipipe->intrxfer = xfer;
 	ipipe->repeat = 1;
 	err = usbd_transfer(xfer);
 	*pipe = ipipe;
-	if (err != USBD_IN_PROGRESS && err)
-		goto bad2;
+		if (err == USBD_IN_PROGRESS || !err)
 	return (USBD_NORMAL_COMPLETION);
-
- bad2:
 	ipipe->intrxfer = NULL;
 	ipipe->repeat = 0;
 	usbd_free_xfer(xfer);
- bad1:
+	}
 	usbd_close_pipe(ipipe);
 	return (err);
 }

IMHO/AFAIK, using of "goto" is not a good practice. But who know... :-)


P.S. Sorry for my English.


-----Original Message-----
From: Paul B. Mahol [mailto:onemda@gmail.com] 
Sent: Saturday, July 05, 2008 9:19 PM
To: VVD
Cc: freebsd-usb@freebsd.org
Subject: Re: usb/125264: [patch] sysctl for set usb mouse rate (very useful
for gamers - FPS games)


On 7/5/08, VVD <vvd@quakeworld.ru> wrote:
> The following reply was made to PR usb/125264; it has been noted by GNATS.
>
> From: "VVD" <vvd@quakeworld.ru>
> To: <bug-followup@FreeBSD.org>,
> 	<hselasky@c2i.net>
> Cc:  
> Subject: Re: usb/125264: [patch] sysctl for set usb mouse rate (very 
> useful for gamers - FPS games)
> Date: Sat, 5 Jul 2008 06:10:01 +0400
>
>  Hi,
>  
>  AFAIK, all mice are LOW speed usb devices. Didn't understand how to 
> use
>  usbd_get_speed() for ums - have no field like speed. High rate need 
> only for  more smooth mouse moving.
>  Linux have custom mouse rate patch from ~2.6.1x. Logitech have 
> Setpoint  drivers for Win with possibility to set mouse rate from 125 
> to 1000. Time  for FreeBSD to have this feature. :-]
>  

But what about moused -F option? Is it supported at all by ums driver?


>  With best regards.
>  
>  
> _______________________________________________
> 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 vvd at quakeworld.ru  Sun Jul 13 04:20:04 2008
From: vvd at quakeworld.ru (VVD)
Date: Sun Jul 13 04:20:11 2008
Subject: usb/125264: [patch] sysctl for set usb mouse rate (very useful
	for gamers - FPS games)
Message-ID: <200807130420.m6D4K3aA079594@freefall.freebsd.org>

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

From: "VVD" <vvd@quakeworld.ru>
To: <bug-followup@FreeBSD.org>
Cc: <freebsd-usb@freebsd.org>,
	"'Paul B. Mahol'" <onemda@gmail.com>
Subject: RE: usb/125264: [patch] sysctl for set usb mouse rate (very useful for gamers - FPS games)
Date: Sun, 13 Jul 2008 08:12:59 +0400

 I find speed - always LOW (tested on 6 Logitech mice: G5, MX300, RX250 and 3
 different 5$-cost mice).
 But I wrote another patch:
 --- ums.c.orig	2008-06-16 19:51:35.000000000 +0400
 +++ ums.c	2008-07-13 07:48:58.000000000 +0400
 @@ -673,6 +673,7 @@
  	void *v;
  {
  	struct ums_softc *sc = v;
 +	int usb_interval;
  
  	usbd_status err;
  
 @@ -696,11 +697,21 @@
  	 */
  	usbd_set_protocol(sc->sc_iface, 1);
  
 +	/* 
 +	 * Calculate USB interval in ms from rate in Hz (moused command line
 option -F).
 +	 * Possible values are from 1 to 1000, else use
 USBD_DEFAULT_INTERVAL.
 +	 * Modern gaming mice have 500Hz by default, other 100Hz or 125Hz.
 +	 */
 +	usb_interval = (sc->mode.rate > 0 && sc->mode.rate <= 1000) ?
 +			1000 / sc->mode.rate : USBD_DEFAULT_INTERVAL;
 +	DPRINTF(("ums_enable: mouse rate is %d, usb interval is %d\n",
 +		sc->mode.rate, usb_interval));
 +
  	/* Set up interrupt pipe. */
  	err = usbd_open_pipe_intr(sc->sc_iface, sc->sc_ep_addr,
  				USBD_SHORT_XFER_OK, &sc->sc_intrpipe, sc,
  				sc->sc_ibuf, sc->sc_isize, ums_intr,
 -				USBD_DEFAULT_INTERVAL);
 +				usb_interval);
  	if (err) {
  		DPRINTF(("ums_enable: usbd_open_pipe_intr failed,
 error=%d\n",
  			 err));
 @@ -900,6 +911,29 @@
  			sc->mode.syncmask[1] = MOUSE_SYS_SYNC;
  		}
  
 +		/*
 +		 * Most modern gaming mice support customized resolution,
 but I don't know
 +		 * how to set it. For support this feature in
 ums_ioctl(MOUSE_SETMODE)
 +		 * need to uncomment next line:
 +		 * sc->mode.resolution = mode.resolution > 0 ?
 +		 *			 mode.resolution :
 MOUSE_RES_UNKNOWN;
 +		 * and may be call ums_disable() and ums_enable() if
 resolution was changed.
 +		 */
 +
 +		/*
 +		 * Call ums_disable() and ums_enable() because of what rate
 was set in
 +		 * ums_enable() and can't to change it on the fly (if can -
 how?).
 +		 * For example: during moused startup (with options "-F rate
 -r resolution")
 +		 * 1st call ums_enable() and then ums_ioctl(MOUSE_SETMODE)
 and, as result,
 +		 * mouse initialized with default values of the rate and
 resolution,
 +		 * but not with custom from command line.
 +		 */
 +		if (sc->mode.rate != mode.rate) {
 +			sc->mode.rate = mode.rate;
 +			ums_disable(sc);
 +			ums_enable(sc);
 +		}
 +
  		bzero(sc->qbuf, sizeof(sc->qbuf));
  		sc->qhead = sc->qtail = sc->qcount = 0;
  		splx(s);
 
 
 I want to ask about to make another PR with patch:
 --- usbdi.c.orig	2008-07-12 20:43:42.000000000 +0400
 +++ usbdi.c	2008-07-12 20:43:47.000000000 +0400
 @@ -231,23 +231,19 @@
  	xfer = usbd_alloc_xfer(iface->device);
  	if (xfer == NULL) {
  		err = USBD_NOMEM;
 -		goto bad1;
 -	}
 +	} else {
  	usbd_setup_xfer(xfer, ipipe, priv, buffer, len, flags,
  	    USBD_NO_TIMEOUT, cb);
  	ipipe->intrxfer = xfer;
  	ipipe->repeat = 1;
  	err = usbd_transfer(xfer);
  	*pipe = ipipe;
 -	if (err != USBD_IN_PROGRESS && err)
 -		goto bad2;
 +		if (err == USBD_IN_PROGRESS || !err)
  	return (USBD_NORMAL_COMPLETION);
 -
 - bad2:
  	ipipe->intrxfer = NULL;
  	ipipe->repeat = 0;
  	usbd_free_xfer(xfer);
 - bad1:
 +	}
  	usbd_close_pipe(ipipe);
  	return (err);
  }
 
 IMHO/AFAIK, using of "goto" is not a good practice. But who know... :-)
 
 
 P.S. Sorry for my English.
 
 
 -----Original Message-----
 From: Paul B. Mahol [mailto:onemda@gmail.com] 
 Sent: Saturday, July 05, 2008 9:19 PM
 To: VVD
 Cc: freebsd-usb@freebsd.org
 Subject: Re: usb/125264: [patch] sysctl for set usb mouse rate (very useful
 for gamers - FPS games)
 
 
 On 7/5/08, VVD <vvd@quakeworld.ru> wrote:
 > The following reply was made to PR usb/125264; it has been noted by GNATS.
 >
 > From: "VVD" <vvd@quakeworld.ru>
 > To: <bug-followup@FreeBSD.org>,
 > 	<hselasky@c2i.net>
 > Cc:  
 > Subject: Re: usb/125264: [patch] sysctl for set usb mouse rate (very 
 > useful for gamers - FPS games)
 > Date: Sat, 5 Jul 2008 06:10:01 +0400
 >
 >  Hi,
 >  
 >  AFAIK, all mice are LOW speed usb devices. Didn't understand how to 
 > use
 >  usbd_get_speed() for ums - have no field like speed. High rate need 
 > only for  more smooth mouse moving.
 >  Linux have custom mouse rate patch from ~2.6.1x. Logitech have 
 > Setpoint  drivers for Win with possibility to set mouse rate from 125 
 > to 1000. Time  for FreeBSD to have this feature. :-]
 >  
 
 But what about moused -F option? Is it supported at all by ums driver?
 
 
 >  With best regards.
 >  
 >  
 > _______________________________________________
 > 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 bugmaster at FreeBSD.org  Mon Jul 14 11:07:07 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Jul 14 11:09:14 2008
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200807141107.m6EB77TX014589@freefall.freebsd.org>

Current FreeBSD problem reports
Critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
f usb/84750    usb        [hang] 6-BETA2 reboot/shutdown with root_fs on externa
o usb/91629    usb        usbd_abort_pipe() may result in infinite loop

2 problems total.

Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o i386/46371   usb        USB controller cannot be initialized on IBM Netfinity 
o bin/57255    usb        usbd(8) and multi-function devices
o usb/63621    usb        [umass] [panic] USB MemoryStick Reader stalls/crashes 
o usb/67301    usb        [uftdi] [panic] RTS and system panic
o usb/69006    usb        [usbdevs] [patch] Apple Cinema Display hangs USB ports
o usb/71155    usb        [ulpt] misbehaving usb-printer hangs processes, causes
o usb/73307    usb        [panic] Kernel panics on USB disconnect
o usb/74771    usb        [umass] [hang] mounting write-protected umass device a
o usb/75705    usb        [umass] [panic] da0 attach / Optio S4 (with backtrace)
o usb/75797    usb        [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c
o usb/76395    usb        [uhci] USB printer does not work, usbdevs says "addr 0
o usb/77184    usb        [umass] [panic] kernel panic on USB device disconnect,
o usb/77294    usb        [ucom] [panic] ucom + ulpcom panic
o usb/79269    usb        [ohci] USB ohci da0 plug/unplug causes crashes and loc
o usb/79287    usb        [uhci] [hang] UHCI hang after interrupt transfer
o usb/79524    usb        [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa
a usb/79656    usb        [ehci] RHSC interrupts lost
o usb/79722    usb        [ehci] wrong alignments in ehci.h
o usb/80040    usb        [hang] Use of sound mixer causes system freeze with ua
o usb/80361    usb        [umass] [patch] mounting of Dell usb-stick fails
o usb/80829    usb        [modules] [panic] possible panic when loading USB-modu
o usb/80862    usb        [patch] USB locking issues: missing some Giant calls
o usb/82350    usb        [ucom] [panic] null pointer dereference in USB stack
o usb/82520    usb        [udbp] [reboot] Reboot when USL101 connected
s usb/82569    usb        [umass] [panic] USB mass storage plug/unplug causes sy
o usb/82660    usb        [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic
o usb/83504    usb        [kernel] [patch] SpeedTouch USB stop working on recent
o usb/83563    usb        [umass] [panic] Page Fault while detaching Mpman Usb d
f usb/83677    usb        [usb] [request] usb controller often not detected (Sun
o usb/83756    usb        [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe
o usb/83977    usb        [ucom] [panic] ucom1: open bulk out error (addr 2): IN
o usb/84326    usb        [umass] Panic trying to connect SCSI tape drive via US
s usb/84336    usb        [usb] [reboot] instant system reboot when unmounting a
o usb/86767    usb        [umass] [patch] bogus "slice starts beyond end of the 
o usb/88743    usb        [hang] [regression] USB makes kernel hang at boot (reg
s usb/89003    usb        [request] LaCie Firewire drive not properly supported 
o usb/89954    usb        [umass] [panic] USB Disk driver race condition?
o usb/90700    usb        [umass] [panic] Kernel panic on connect/mount/use umas
o usb/91238    usb        [umass] USB tape unit fails to write a second tape fil
o usb/91283    usb        [boot] [regression] booting very slow with usb devices
o usb/91538    usb        [ulpt] [patch] Unable to print to EPSON CX3500
o usb/91906    usb        [ehci] [hang] FreeBSD hangs while booting with USB leg
o usb/92052    usb        [ulpt] usbd causes defunct process with busy file-hand
o usb/92083    usb        [ural] [panic] panic using WPA on ural NIC in 6.0-RELE
o usb/92142    usb        [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb 
o usb/92171    usb        [panic] panic unplugging Vodafone Mobile Connect (UMTS
o usb/93155    usb        [ulpt] /dev/ulpt0: device busy, USB printer does not w
o usb/93408    usb        [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes 
o usb/93828    usb        [ohci] [panic] ohci causes panic on boot (HP Pavillion
o usb/94384    usb        [panic] kernel panic with usb2 hardware
o usb/94717    usb        [ulpt] Reading from /dev/ulpt can break work of a UHCI
o usb/94897    usb        [panic] Kernel Panic when cleanly unmounting USB disk
s usb/95348    usb        [keyboard] USB keyboard unplug causes noise on screen
o usb/95562    usb        [umass] Write Stress in USB Mass drive causes "vinvalb
s usb/95636    usb        [umass] [boot] 5 minute delay at boot when using VT620
s usb/96120    usb        [ums] [request] USB mouse not always detected
o usb/96224    usb        [usb] [msdosfs] mount_msdosfs cause page fault in sync
o usb/96457    usb        [umass] [panic] fatback on umass = reboot
s usb/97286    usb        [mouse] [request] MS Wireless Intellimouse Explorer 2.
o usb/99431    usb        [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar
o usb/101096   usb        [ural] [panic] USB WLAN occasionally causes kernel-pan
o usb/101448   usb        [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O
o usb/101752   usb        [umass] [panic] 6.1-RELEASE kernel panic on usb device
o usb/102066   usb        [ukbd] usb keyboard and multimedia keys don't work
f usb/102096   usb        [patch] usbd(8) does not handle multiple devices in on
o usb/103025   usb        [uhub] [panic] wrong detection of USB device for FreeB
o usb/104292   usb        [umass] [hang] system lockup on forced umount of usb-s
o usb/104830   usb        [umass] system crashes when copying data to umass devi
o usb/105186   usb        [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c
o usb/106615   usb        [uftdi] uftdi module does not automatically load with 
o usb/106648   usb        [umass] [hang] USB Floppy on D1950 10 min Hang on Inse
s usb/106832   usb        USB HP printer is not detected by kernel when ACPI ena
o usb/107248   usb        [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP
o usb/107446   usb        [umass] umass problems (usb and fw disks)
o usb/107827   usb        [ohci] [panic] ohci_add_done addr not found
o usb/107848   usb        [umass] [request] cannot access Samsung flash disk
o usb/107924   usb        [patch] usbd(8) does not call detach
o usb/108513   usb        [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr
o usb/109274   usb        [usb] MCP55 USB Controller fails to attach in AMD64 Cu
o usb/109397   usb        [panic] on boot from USB flash
o usb/110856   usb        [ugen] [patch] interrupt in msgs are truncated when bu
o usb/110988   usb        [umass] [patch] Handling of quirk IGNORE_RESIDUE is um
o usb/111753   usb        [uhid] [panic] Replicable system panic involving UHID 
s usb/112568   usb        [umass] [request] USB mode may wrong when mounting Pla
o usb/112631   usb        [panic] Problem with SONY DSC-S80 camera on umount
o usb/112640   usb        [usb] [hang] Kernel freezes when writing a file to an 
s usb/113629   usb        [ukbd] Dropped USB keyboard events on Dell Latitude D6
o usb/113672   usb        [ehci] [panic] Kernel panic with AEWIN CB6971
s usb/113977   usb        [request] Need a way to set mode of USB disk's write c
o usb/114310   usb        [libusb] [patch] [panic] USB hub attachment panics ker
o usb/114682   usb        [umass] generic USB media-card reader unusable
o kern/114780  usb        [uplcom] [panic] Panics while stress testing the uplco
o usb/115298   usb        [ulpt] [panic] Turning off USB printer panics kernel
o usb/116561   usb        [umodem] [panic] RELENG_6 umodem panic "trying to slee
o usb/116699   usb        [usbhid] USB HID devices do not initialize at system b
o usb/116947   usb        [ukbd] [patch] [regression] enable boot protocol on th
o usb/117200   usb        [ugen] ugen0 prints strange string on attach if detach
o usb/117313   usb        [umass] [panic] panic on usb camera insertion
o usb/117613   usb        [uhci] [irq] uhci interrupt storm & USB leaked memory 
o usb/117946   usb        [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE
o usb/117955   usb        [umass] [panic] inserting minolta dimage a2 crashes OS
o usb/118140   usb        [ucom] [patch] quick hack for ucom to get it behave wi
o usb/118141   usb        [ucom] usb serial and nokia phones ucomreadcb ucomread
o usb/118353   usb        [panic] [ppp] repeatable kernel panic during ppp(4) se
o usb/118480   usb        [umass] Timeout in USB mass storage freezes vfs layer 
o usb/119201   usb        [cam] [patch] Quirks for Olympus FE-210 camera, LG and
o usb/119481   usb        [hang] FreeBSD not responding after connecting USB-Mas
o usb/119509   usb        USB flaky on Dell Optiplex 755
o usb/119513   usb        [irq] inserting dlink dwl-g630 wireless card results i
o usb/119977   usb        [ums] Mouse does not work in a Cherry-USB keyboard/mou
o usb/120017   usb        [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk
o usb/120034   usb        [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 
o usb/120283   usb        [panic] Automation reboot with wireless keyboard & mou
o usb/120321   usb        [hang] System hangs when transferring data to WD MyBoo
o usb/120729   usb        [panic] fault while in kernel mode with connecting USB
o usb/120786   usb        Kernel panic when forced umount of a dettached USB Har
o usb/121232   usb        remove PCCARD rebooted system
o usb/121275   usb        [boot] FreeBSD fails to boot with usb legacy support e
o usb/121474   usb        [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard
o usb/121708   usb        [keyboard] nforce 650i mobo w/ usb keyboard infinite k
o usb/121734   usb        [ugen] ugen HP1022 printer device not working since up
o usb/121755   usb        [ohci] [patch] Fix panic after ohci/uhub cardbus devic
o usb/122483   usb        [panic] [ulpt] Repeatable panic in 7.0-STABLE
o usb/122539   usb        [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci
o usb/122905   usb        [ubsa] [patch] add Huawei E220 to ubsa
o kern/123510  usb        [ums] Mouse Wheel Fails to Work [regression]
o usb/123690   usb        Panic on USB device insertion when usb loaded as a mod
o usb/123714   usb        Panic when hald-storage-probe runs with umass device i
o usb/124708   usb        [panic] Kernel panic on USB KVM reattach
o usb/124758   usb        rum panics SMP kernel
o kern/124777  usb        [ucom] USB cua devices don't revert to tty devices whe
o usb/124980   usb        [panic] kernel panic on detaching unmounted umass devi
o usb/125088   usb        Touchpad not detected on Adesso AKB-430UG USB kbd/pad 
o usb/125450   usb        [panic] Removing USB flash card while being accessed c

134 problems total.

Non-critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o conf/30929   usb        [usb] [patch] use usbd to initialize USB ADSL modem
o usb/40948    usb        [umass] [request] USB HP CDW8200 does not work
s usb/51958    usb        [urio] [patch] update for urio driver
s usb/52026    usb        [usb] [request] umass driver support for InSystem ISD2
o usb/59698    usb        [keyboard] [patch] Rework of ukbd HID to AT code trans
s usb/62257    usb        [umass] [request] card reader UCR-61S2B is only half-s
o usb/66547    usb        [ucom] Palm Tungsten T USB does not initialize correct
o usb/68232    usb        [ugen] [patch] ugen(4) isochronous handling correction
o usb/70523    usb        [umct] [patch] umct sending/receiving wrong characters
o usb/71280    usb        [aue] aue0 device (linksys usb100tx) doesn't work in 1
o usb/71416    usb        [ugen] Cryptoflex e-gate USB token (ugen0) detach is n
o usb/71417    usb        [ugen] Cryptoflex e-gate USB token (ugen0) communicati
o usb/71455    usb        [umass] Slow USB umass performance of 5.3
s usb/72733    usb        [ucom] [request] Kyocera 7135 Palm OS connection probl
o usb/74211    usb        [umass] USB flash drive causes CAM status 0x4 on 4.10R
a usb/74453    usb        [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL
o usb/75764    usb        [umass] [patch] "umass0: Phase Error" - no device for 
o usb/75800    usb        [ucom] ucom1: init failed STALLED error in time of syn
s usb/75928    usb        [umass] [request] Cytronix SmartMedia card (SMC) reade
o usb/76461    usb        [umass] disklabel of umass(4)-CAM(4)-da(4) not used by
o usb/76653    usb        [umass] [patch] Problem with Asahi Optical usb device 
o usb/76732    usb        Mouse problems with USB KVM Switch
o usb/78984    usb        [umass] [patch] Creative MUVO umass failure
o usb/79723    usb        [usb] [request] prepare for high speed isochronous tra
o usb/80774    usb        [patch] have "usbd_find_desc" in line with the other "
s usb/80776    usb        [udav] [request] UDAV device driver shouldn't use usb_
s usb/80777    usb        [request] usb_rem_task() should wait for callback to c
o usb/80854    usb        [patch] [request] suggestion for new iface-no-probe me
o usb/80935    usb        [uvisor] [patch] uvisor.c is not work with CLIE TH55.
o usb/81621    usb        [ehci] [hang] external hd hangs under load on ehci
o usb/83863    usb        [ugen] Communication problem between opensc/openct via
s usb/85067    usb        [uscanner] Cannot attach ScanJet 4300C to usb device
o usb/86298    usb        [mouse] Known good USB mouse won't work with correct s
o usb/87224    usb        Cannot mount USB Zip750
o usb/87648    usb        [mouse] Logitech USB-optical mouse problem.
o usb/88408    usb        [axe] axe0 read PHY failed
o usb/91546    usb        [umodem] [patch] Nokia 6630 mobile phone does not work
o usb/91811    usb        [umass] Compact Flash in HP Photosmart 2610 return  " 
o usb/91896    usb        camcontrol(8): Serial Number of USB Memory Sticks is n
o usb/92852    usb        [ums] [patch] Vertical scroll not working properly on 
o usb/93389    usb        [umass] [patch] Digital Camera Pentax S60 don't work
o usb/93872    usb        [cam] [patch] SCSI quirk required for ELTA 8061 OL USB
o usb/95037    usb        [umass] USB disk not recognized on hot-plug.
o usb/96381    usb        [cam] [patch] add a quirk table entry for a flash ram 
o usb/97175    usb        [umass] [hang] USB cardreader hangs system
o usb/97472    usb        [cam] [patch] add support for Olympus C150,D390
o usb/98343    usb        [boot] BBB reset failed errors with Creative Muvo MP3 
o usb/99538    usb        [keyboard] while using USB keyboard default params of 
o usb/100746   usb        [keyboard] system does not boot due to USB keyboard pr
o usb/101761   usb        [usb] [patch] [request] usb.h: increase maximal size o
o usb/101775   usb        [libusbhid] [patch] possible error in report descripto
o usb/102678   usb        [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not 
o usb/102976   usb        [panic] Casio Exilim Digital Camera causes panic on in
o usb/103046   usb        [ulpt] [patch] ulpt event driven I/O with select(2) an
o usb/103289   usb        [request] USB 2.0 problems on AMD LX-800 CPU and CS-55
o usb/103418   usb        [usbhidctl] [patch] [request] usbhidctl: add ability t
o usb/103917   usb        [uhub] USB driver reports "Addr 0 should never happen"
o usb/104290   usb        [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto
o usb/104352   usb        [ural] [patch] ural driver doesnt work
o usb/104645   usb        [umass] [request] Rave C-201 MP3 player does not commu
o usb/105065   usb        [ata] SATA - USB Bridge
o usb/105361   usb        [panic] Kernel panic during unmounting mass storage (C
o usb/106041   usb        [usb] [request] FreeBSD does not recognise Mustek Bear
o usb/106621   usb        [axe] [patch] DLINK DUB-E100 support broken
o usb/106861   usb        [usbdevs] [patch]: usbdevs update: Add product ACER Ze
o usb/107243   usb        [cam] [patch] Apacer USB Flash Drive quirk
o usb/107388   usb        [patch] [request] new driver: add utoppy device from N
o usb/107496   usb        [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [
o usb/107935   usb        [uplcom] [panic] panic while accessing /dev/cuaU0
o usb/108056   usb        [ohci] Mouse gets powered off during device probe when
s usb/108344   usb        [panic] kernel with atausb panics when unplugging USB 
o usb/110197   usb        [umass] Sony PSP umass device does not detach from EHC
s usb/110991   usb        [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends
o usb/112461   usb        [ehci] [request] ehci USB 2.0 doesn't work on nforce4
o usb/112463   usb        [umass] problem with Samsung USB DVD writer, libscg an
o usb/112944   usb        [ulpt] [patch] Bi-directional access to HP LaserJet 10
o usb/113060   usb        [usbdevs] [patch] Samsung printer not working in bidir
o usb/113432   usb        [ucom] WARNING: attempt to net_add_domain(netgraph) af
o conf/114013  usb        [patch] WITHOUT_USB allow to compil a lot of USB stuff
o usb/114068   usb        [umass] [patch] Problems with connection of the umass 
o usb/114916   usb        [umass] [patch] USB Maxtor drive (L300RO) requires qui
o usb/115400   usb        [ehci] Problem with EHCI on ASUS M2N4-SLI
o usb/115933   usb        [uftdi] [patch] RATOC REX-USB60F (usb serial converter
o usb/115935   usb        [usbdevs] [patch] kernel counterproductively attaches 
o usb/116282   usb        [ulpt] Cannot print on USB HP LJ1018 or LJ1300
o usb/117075   usb        [scsi_da] [patch] quirk: USB Samsung YP-U3 MP3
o usb/117183   usb        [panic] USB/fusefs -- panic while transferring large a
o usb/117185   usb        [umodem] [patch] Add support for UNION interface descr
o usb/117205   usb        [uscanner] [patch] uscanner support for HP ScanJet 447
o usb/117546   usb        [uftdi] [patch] Add MaxStream ZigBee product ID to uft
o usb/117598   usb        [uaudio] [patch] Not possible to record with Plantroni
o usb/117893   usb        [umass] Lacie USB DVD writing failing
o usb/117911   usb        [ums] [request] Mouse Gembird MUSWC not work
o usb/117938   usb        [ums] [patch] Adding support for MS WL Natural and MS 
o usb/118098   usb        [umass] 6th gen iPod causes problems when disconnectin
o usb/118485   usb        [usbdevs] [patch] Logitech Headset Workaround
o usb/118686   usb        [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei
o usb/119150   usb        [usbdevs] [patch] new usbdevs for CDMA 1xEVDO devices
o usb/119227   usb        [ubsa] [patch] ubsa buffer is too small; should be tun
o usb/119389   usb        [umass] Sony DSC-W1 CBI reset failed, STALLED [regress
o usb/119633   usb        [umass] umass0: BBB reset failed, IOERROR [regression]
o usb/119653   usb        [cam] [patch] iriver s7 player sync cache error patch
o usb/119981   usb        [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab
o usb/120572   usb        [umass] [patch] quirk to support ASUS P535 as umass (a
o usb/121045   usb        [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS
o usb/121169   usb        [umass] Issues with usb mp3 player
o usb/121184   usb        [uipaq] [patch] add ids from linux ipaq driver (plus a
o usb/121426   usb        [patch] [uscanner] add HP ScanJet 3570C
o usb/122025   usb        [patch] uscanner does not attach to Epson RX620 printe
o usb/122119   usb        [umass] umass device causes creation of daX but not da
o usb/122547   usb        [ehci] USB Printer not being recognized after reboot
p usb/122610   usb        Add Verizon v740 support to ubsa(4)
o usb/122621   usb        [patch] [request] New driver for Sierra Wireless 3G US
o usb/122712   usb        [usbdevs] [patch] Sony Vaio RF keyboard/mouse receiver
o usb/122813   usb        [udbp] [request] udbp driver should be removed in favo
o usb/122819   usb        Patch to provide dynamic additions to the usb quirks t
o usb/122936   usb        [ucom][ubsa] Device does not receive interrupt
o usb/122956   usb        Support for Novatel Wireless XU870 3G Card
o usb/122992   usb        MotoROKR Z6 Phone not recognised by umass as USB disk.
p usb/123148   usb        [uscanner] [patch] Epson DX8400/50 needs uscanner to s
p usb/123211   usb        [udav] if_udav driver doesn't support Davicom 9601 USB
o kern/123224  usb        [ums] Scroll wheel breakage w/ USB MS Wireless Intelli
o usb/123351   usb        Add Reiner SCT cyberJack, Omnikey [26]020, Fujitsu Sie
o usb/123352   usb        Add Option GTMAX3.6/7.2 and Quallcomm MMC module devic
o usb/123509   usb        [umass] continuous reset Samsung SGH-G600 phone
o usb/123611   usb        [usb] BBB reset failed, STALLED from Imation/Mitsumi U
o usb/123691   usb        usbd(8): usbd hangs
o usb/123959   usb        [ums] add support for Razer Lachesis 4000dpi usb mouse
o usb/123969   usb        Supermicro H8SMi-2 usb problem
o usb/124604   usb        Wireless Mouse doesn't work
o usb/125072   usb        [uplcom] [patch] add Mobile Action MA-620 Infrared Ada
o usb/125238   usb        Habu Mouse turns off in X
o usb/125264   usb        [patch] sysctl for set usb mouse rate (very useful for
o usb/125510   usb        repeated plug and unplug of USB mass storage devices l

134 problems total.

From ddkprog at yahoo.com  Mon Jul 14 16:00:15 2008
From: ddkprog at yahoo.com (ddk ddk)
Date: Mon Jul 14 16:00:23 2008
Subject: usb/117911: [ums] [request] Mouse Gembird MUSWC not work
Message-ID: <200807141600.m6EG0FvI044107@freefall.freebsd.org>

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

From: ddk ddk <ddkprog@yahoo.com>
To: bug-followup@FreeBSD.org, admin@lissyara.su
Cc:  
Subject: Re: usb/117911: [ums] [request] Mouse Gembird MUSWC not work
Date: Mon, 14 Jul 2008 05:52:03 -0700 (PDT)

 --0-923209554-1216039923=:43904
 Content-Type: text/plain; charset=us-ascii
 
 
 hi! this problem an HID parser on FreeBSD and other *BSD system
 
 i'am use a krepdump http://people.freebsd.org/~kaiw/tools/krepdump.tgz
 to show full HID protocol dump from this USB Mouse
 
 -----------------------------------------------
 [report desc size=79]
 USAGE PAGE Consumer(0xc)
 USAGE Consumer Control(0x1)[Consumer(0xc)]
 COLLECTION Application(1)
   REPORT ID 1
   USAGE MINIMUM Unassigned(0)
   USAGE MAXIMUM AC Underline(576)
   LOGICAL MINIMUM 0
   LOGICAL MAXIMUM 576
   REPORT SIZE 16
   REPORT COUNT 1
   INPUT ( Data Array Absolute ) (0)
 END COLLECTION
 USAGE PAGE Generic Desktop(0x1)
 USAGE Mouse(0x2)[Generic Desktop(0x1)]
 COLLECTION Application(1)
   REPORT ID 2
   USAGE Pointer(0x1)[Generic Desktop(0x1)]
   COLLECTION Physical(0)
     USAGE PAGE Button(0x9)
     USAGE MINIMUM Button1(1)
     USAGE MAXIMUM Button3(3)
     LOGICAL MINIMUM 0
     LOGICAL MAXIMUM 1
     REPORT SIZE 1
     REPORT COUNT 3
     INPUT ( Data Variable Absolute ) (2)
     REPORT SIZE 5
     REPORT COUNT 1
     INPUT ( Const Array Absolute ) (1)
     USAGE PAGE Generic Desktop(0x1)
     USAGE X(0x30)[Generic Desktop(0x1)]
     USAGE Y(0x31)[Generic Desktop(0x1)]
     USAGE Wheel(0x38)[Generic Desktop(0x1)]
     LOGICAL MINIMUM -127
     LOGICAL MAXIMUM 127
     REPORT SIZE 8
     REPORT COUNT 3
     INPUT ( Data Variable Relative ) (6)
   END COLLECTION
 END COLLECTION
 [hexdump]
 0000 05 0C 09 01 A1 01 85 01 19 00 2A 40 02 15 00 26
 0010 40 02 75 10 95 01 81 00 C0 05 01 09 02 A1 01 85
 0020 02 09 01 A1 00 05 09 19 01 29 03 15 00 25 01 75
 0030 01 95 03 81 02 75 05 95 01 81 01 05 01 09 30 09
 0040 31 09 38 15 81 25 7F 75 08 95 03 81 06 C0 C0
 
 --------------------------------------------------
 as you can see
 this Mouse generate 2 HID protocol collection
 
 the first collection is
 USAGE PAGE Consumer(0xc)
 USAGE Consumer Control(0x1)[Consumer(0xc)]
 COLLECTION Application(1)
   REPORT ID 1
   ...
 
 the second collection is
 USAGE PAGE Generic Desktop(0x1)
 USAGE Mouse(0x2)[Generic Desktop(0x1)]
 COLLECTION Application(1)
   REPORT ID 2
   ...
 
 two collection describe a two protocol 
 first protocol - AC line (Wireless Mouse from AC battarey)
 second protocol - Mouse movement
  
 
 an exists FreeBSD HID parser don't work with such collection
 to parse it used first collection, allways
 is't correct!!
 
 as example with this Mouse
 
 #kldload ums.ko
 #dmesg -a | grep ums
 
 ----------------------
 ums_attach: 3 buttons
 ums_attach: X   24/8
 ums_attach: Y   32/8
 ums_attach: Z   40/8
 ums_attach: B1  16/1
 ums_attach: B2  17/1
 ums_attach: B3  18/1
 ums_attach: size=3, id=1
 ----------------------
 
 the HID parser use first HID collection to parse Mouse movenent
 Mouse not work!!
 
 
 
 i'am fixx the HID parser
 to correct use HID collection
 after patch http://paradox.org.ua/work/fixx.tar.bz2
 ----------------------
 ums_attach: 3 buttons
 ums_attach: X   8/8
 ums_attach: Y   16/8
 ums_attach: Z   24/8
 ums_attach: B1  0/1
 ums_attach: B2  1/1
 ums_attach: B3  2/1
 ums_attach: size=5, id=2
 ----------------------
 and Mouse works fine!
 
 i think this patch fixx
 fixed all USB Mouse problem an *BSD system
 
 
 
       
 --0-923209554-1216039923=:43904
 Content-Type: text/plain; name="usb.fixx"
 Content-Transfer-Encoding: base64
 Content-Disposition: attachment; filename="usb.fixx"
 
 ZGlmZiAtdXJOIHVzYi5vcmlnL2hpZC5jIHVzYi5uZXcvaGlkLmMKLS0tIHVz
 Yi5vcmlnL2hpZC5jCTIwMDgtMDMtMDMgMDM6MTQ6NDcuMDAwMDAwMDAwICsw
 MjAwCisrKyB1c2IubmV3L2hpZC5jCTIwMDgtMDctMTQgMDI6MDM6MTMuMDAw
 MDAwMDAwICswMzAwCkBAIC03Miw2ICs3Miw3IEBACiAJaW50IG11bHRpOwog
 CWludCBtdWx0aW1heDsKIAlpbnQga2luZHNldDsKKwlpbnQgdXNhZ2U7CiB9
 OwogCiBzdGF0aWMgdm9pZApAQCAtMTE1LDcgKzExNiw3IEBACiB9CiAKIGlu
 dAotaGlkX2dldF9pdGVtKHN0cnVjdCBoaWRfZGF0YSAqcywgc3RydWN0IGhp
 ZF9pdGVtICpoKQoraGlkX2dldF9pdGVtKHN0cnVjdCBoaWRfZGF0YSAqcywg
 dV9pbnQzMl90IHUsIHN0cnVjdCBoaWRfaXRlbSAqaCkKIHsKIAlzdHJ1Y3Qg
 aGlkX2l0ZW0gKmMgPSAmcy0+Y3VyOwogCXVuc2lnbmVkIGludCBiVGFnLCBi
 VHlwZSwgYlNpemU7CkBAIC0xOTMsNiArMTk0LDkgQEAKIAkJY2FzZSAwOgkJ
 CS8qIE1haW4gKi8KIAkJCXN3aXRjaCAoYlRhZykgewogCQkJY2FzZSA4OgkJ
 LyogSW5wdXQgKi8KKwkJCQlpZiAocy0+dXNhZ2UgIT0gdSA+PjE2ICYmIHUg
 IT0gMCkKKwkJCQkJYnJlYWs7CisKIAkJCQlpZiAoIShzLT5raW5kc2V0ICYg
 KDEgPDwgaGlkX2lucHV0KSkpCiAJCQkJCWNvbnRpbnVlOwogCQkJCWMtPmtp
 bmQgPSBoaWRfaW5wdXQ7CkBAIC0yMjMsNiArMjI3LDkgQEAKIAkJCQkJcmV0
 dXJuICgxKTsKIAkJCQl9CiAJCQljYXNlIDk6CQkvKiBPdXRwdXQgKi8KKwkJ
 CQlpZiAocy0+dXNhZ2UgIT0gdSA+PjE2ICYmIHUgIT0gMCkKKwkJCQkJYnJl
 YWs7CisKIAkJCQlpZiAoIShzLT5raW5kc2V0ICYgKDEgPDwgaGlkX291dHB1
 dCkpKQogCQkJCQljb250aW51ZTsKIAkJCQljLT5raW5kID0gaGlkX291dHB1
 dDsKQEAgLTIzMiwxMSArMjM5LDE2IEBACiAJCQkJYy0+a2luZCA9IGhpZF9j
 b2xsZWN0aW9uOwogCQkJCWMtPmNvbGxlY3Rpb24gPSBkdmFsOwogCQkJCWMt
 PmNvbGxldmVsKys7CisJCQkJaWYgKGMtPmNvbGxldmVsID4gMCAmJiB1ICE9
 IDApCisJCQkJCXMtPnVzYWdlID0gYy0+X3VzYWdlX3BhZ2UgPj4gMTY7CiAJ
 CQkJKmggPSAqYzsKIAkJCQloaWRfY2xlYXJfbG9jYWwoYyk7CiAJCQkJcy0+
 bnUgPSAwOwogCQkJCXJldHVybiAoMSk7CiAJCQljYXNlIDExOgkvKiBGZWF0
 dXJlICovCisJCQkJaWYgKHMtPnVzYWdlICE9IHUgPj4xNiAmJiB1ICE9IDAp
 CisJCQkJCWJyZWFrOworCiAJCQkJaWYgKCEocy0+a2luZHNldCAmICgxIDw8
 IGhpZF9mZWF0dXJlKSkpCiAJCQkJCWNvbnRpbnVlOwogCQkJCWMtPmtpbmQg
 PSBoaWRfZmVhdHVyZTsKQEAgLTI1OCw2ICsyNzAsOSBAQAogCQkJc3dpdGNo
 IChiVGFnKSB7CiAJCQljYXNlIDA6CiAJCQkJYy0+X3VzYWdlX3BhZ2UgPSBk
 dmFsIDw8IDE2OworCisJCQkJaWYgKHUgIT0gMCAmJiB1Pj4xNiA9PSBkdmFs
 KQorCQkJCQlzLT51c2FnZSA9IGR2YWw7CiAJCQkJYnJlYWs7CiAJCQljYXNl
 IDE6CiAJCQkJYy0+bG9naWNhbF9taW5pbXVtID0gZHZhbDsKQEAgLTM2NCw3
 ICszNzksNyBAQAogfQogCiBpbnQKLWhpZF9yZXBvcnRfc2l6ZSh2b2lkICpi
 dWYsIGludCBsZW4sIGVudW0gaGlkX2tpbmQgaywgdV9pbnQ4X3QgKmlkcCkK
 K2hpZF9yZXBvcnRfc2l6ZSh2b2lkICpidWYsIGludCBsZW4sIHVfaW50MzJf
 dCB1LCBlbnVtIGhpZF9raW5kIGssIHVfaW50OF90ICppZHApCiB7CiAJc3Ry
 dWN0IGhpZF9kYXRhICpkOwogCXN0cnVjdCBoaWRfaXRlbSBoOwpAQCAtMzcy
 LDcgKzM4Nyw3IEBACiAKIAlpZCA9IDA7CiAJaGkgPSBsbyA9IC0xOwotCWZv
 ciAoZCA9IGhpZF9zdGFydF9wYXJzZShidWYsIGxlbiwgMTw8ayk7IGhpZF9n
 ZXRfaXRlbShkLCAmaCk7ICkKKwlmb3IgKGQgPSBoaWRfc3RhcnRfcGFyc2Uo
 YnVmLCBsZW4sIDE8PGspOyBoaWRfZ2V0X2l0ZW0oZCwgdSwgJmgpOyApCiAJ
 CWlmIChoLmtpbmQgPT0gaykgewogCQkJaWYgKGgucmVwb3J0X0lEICE9IDAg
 JiYgIWlkKQogCQkJCWlkID0gaC5yZXBvcnRfSUQ7CkBAIC0zOTksNyArNDE0
 LDcgQEAKIAlzdHJ1Y3QgaGlkX2RhdGEgKmQ7CiAJc3RydWN0IGhpZF9pdGVt
 IGg7CiAKLQlmb3IgKGQgPSBoaWRfc3RhcnRfcGFyc2UoZGVzYywgc2l6ZSwg
 MTw8ayk7IGhpZF9nZXRfaXRlbShkLCAmaCk7ICkgeworCWZvciAoZCA9IGhp
 ZF9zdGFydF9wYXJzZShkZXNjLCBzaXplLCAxPDxrKTsgaGlkX2dldF9pdGVt
 KGQsIHUsICZoKTsgKSB7CiAJCWlmIChoLmtpbmQgPT0gayAmJiAhKGguZmxh
 Z3MgJiBISU9fQ09OU1QpICYmIGgudXNhZ2UgPT0gdSkgewogCQkJaWYgKGxv
 YyAhPSBOVUxMKQogCQkJCSpsb2MgPSBoLmxvYzsKQEAgLTQ1Miw3ICs0Njcs
 NyBAQAogCWlmIChoZCA9PSBOVUxMKQogCQlyZXR1cm4gKDApOwogCi0JZXJy
 ID0gaGlkX2dldF9pdGVtKGhkLCAmaGkpICYmCisJZXJyID0gaGlkX2dldF9p
 dGVtKGhkLCB1c2FnZSwgJmhpKSAmJgogCSAgICBoaS5raW5kID09IGhpZF9j
 b2xsZWN0aW9uICYmCiAJICAgIGhpLnVzYWdlID09IHVzYWdlOwogCWhpZF9l
 bmRfcGFyc2UoaGQpOwpkaWZmIC11ck4gdXNiLm9yaWcvaGlkLmggdXNiLm5l
 dy9oaWQuaAotLS0gdXNiLm9yaWcvaGlkLmgJMjAwNS0wMS0xOSAxNzo1MTow
 My4wMDAwMDAwMDAgKzAyMDAKKysrIHVzYi5uZXcvaGlkLmgJMjAwOC0wNy0x
 MSAxOTozNTowOS4wMDAwMDAwMDAgKzAzMDAKQEAgLTgyLDggKzgyLDggQEAK
 IAogc3RydWN0IGhpZF9kYXRhICpoaWRfc3RhcnRfcGFyc2Uodm9pZCAqZCwg
 aW50IGxlbiwgaW50IGtpbmRzZXQpOwogdm9pZCBoaWRfZW5kX3BhcnNlKHN0
 cnVjdCBoaWRfZGF0YSAqcyk7Ci1pbnQgaGlkX2dldF9pdGVtKHN0cnVjdCBo
 aWRfZGF0YSAqcywgc3RydWN0IGhpZF9pdGVtICpoKTsKLWludCBoaWRfcmVw
 b3J0X3NpemUodm9pZCAqYnVmLCBpbnQgbGVuLCBlbnVtIGhpZF9raW5kIGss
 IHVfaW50OF90ICppZCk7CitpbnQgaGlkX2dldF9pdGVtKHN0cnVjdCBoaWRf
 ZGF0YSAqcywgdV9pbnQzMl90IHUsIHN0cnVjdCBoaWRfaXRlbSAqaCk7Citp
 bnQgaGlkX3JlcG9ydF9zaXplKHZvaWQgKmJ1ZiwgaW50IGxlbiwgdV9pbnQz
 Ml90IHUsIGVudW0gaGlkX2tpbmQgaywgdV9pbnQ4X3QgKmlkKTsKIGludCBo
 aWRfbG9jYXRlKHZvaWQgKmRlc2MsIGludCBzaXplLCB1X2ludDMyX3QgdXNh
 Z2UsCiAJCSAgICBlbnVtIGhpZF9raW5kIGtpbmQsIHN0cnVjdCBoaWRfbG9j
 YXRpb24gKmxvYywKIAkJICAgIHVfaW50MzJfdCAqZmxhZ3MpOwpkaWZmIC11
 ck4gdXNiLm9yaWcvdWN5Y29tLmMgdXNiLm5ldy91Y3ljb20uYwotLS0gdXNi
 Lm9yaWcvdWN5Y29tLmMJMjAwOC0wMy0wMyAwMzoxODoxMi4wMDAwMDAwMDAg
 KzAyMDAKKysrIHVzYi5uZXcvdWN5Y29tLmMJMjAwOC0wNy0xMiAwMzo0Njox
 MS4wMDAwMDAwMDAgKzAzMDAKQEAgLTIyMSw5ICsyMjEsOSBAQAogCX0KIAog
 CS8qIGdldCByZXBvcnQgc2l6ZXMgKi8KLQlzYy0+c2NfZmxlbiA9IGhpZF9y
 ZXBvcnRfc2l6ZSh1cmQsIHVyZGxlbiwgaGlkX2ZlYXR1cmUsICZzYy0+c2Nf
 ZmlkKTsKLQlzYy0+c2NfaWxlbiA9IGhpZF9yZXBvcnRfc2l6ZSh1cmQsIHVy
 ZGxlbiwgaGlkX2lucHV0LCAmc2MtPnNjX2lpZCk7Ci0Jc2MtPnNjX29sZW4g
 PSBoaWRfcmVwb3J0X3NpemUodXJkLCB1cmRsZW4sIGhpZF9vdXRwdXQsICZz
 Yy0+c2Nfb2lkKTsKKwlzYy0+c2NfZmxlbiA9IGhpZF9yZXBvcnRfc2l6ZSh1
 cmQsIHVyZGxlbiwgMCwgaGlkX2ZlYXR1cmUsICZzYy0+c2NfZmlkKTsgLyog
 TkVFRCBUTyBCRSBGSVhYID8/Pz8/ICovCisJc2MtPnNjX2lsZW4gPSBoaWRf
 cmVwb3J0X3NpemUodXJkLCB1cmRsZW4sIDAsIGhpZF9pbnB1dCwgJnNjLT5z
 Y19paWQpOwkvKiBORUVEIFRPIEJFIEZJWFggPz8/Pz8gKi8KKwlzYy0+c2Nf
 b2xlbiA9IGhpZF9yZXBvcnRfc2l6ZSh1cmQsIHVyZGxlbiwgMCwgaGlkX291
 dHB1dCwgJnNjLT5zY19vaWQpOwkvKiBORUVEIFRPIEJFIEZJWFggPz8/Pz8g
 Ki8KIAogCWlmIChzYy0+c2NfaWxlbiA+IFVDWUNPTV9NQVhfSU9MRU4gfHwg
 c2MtPnNjX29sZW4gPiBVQ1lDT01fTUFYX0lPTEVOKSB7CiAJCWRldmljZV9w
 cmludGYoZGV2LCAiSS9PIHJlcG9ydCBzaXplIHRvbyBiaWcgKCV6dSwgJXp1
 LCAldSlcbiIsCmRpZmYgLXVyTiB1c2Iub3JpZy91aGlkLmMgdXNiLm5ldy91
 aGlkLmMKLS0tIHVzYi5vcmlnL3VoaWQuYwkyMDA3LTA2LTIxIDE3OjQyOjMz
 LjAwMDAwMDAwMCArMDMwMAorKysgdXNiLm5ldy91aGlkLmMJMjAwOC0wNy0x
 MiAwMjoxNzoyNi4wMDAwMDAwMDAgKzAzMDAKQEAgLTMyMCw5ICszMjAsOSBA
 QAogCiAJKHZvaWQpdXNiZF9zZXRfaWRsZShpZmFjZSwgMCwgMCk7CiAKLQlz
 Yy0+c2NfaXNpemUgPSBoaWRfcmVwb3J0X3NpemUoZGVzYywgc2l6ZSwgaGlk
 X2lucHV0LCAgICZzYy0+c2NfaWlkKTsKLQlzYy0+c2Nfb3NpemUgPSBoaWRf
 cmVwb3J0X3NpemUoZGVzYywgc2l6ZSwgaGlkX291dHB1dCwgICZzYy0+c2Nf
 b2lkKTsKLQlzYy0+c2NfZnNpemUgPSBoaWRfcmVwb3J0X3NpemUoZGVzYywg
 c2l6ZSwgaGlkX2ZlYXR1cmUsICZzYy0+c2NfZmlkKTsKKwlzYy0+c2NfaXNp
 emUgPSBoaWRfcmVwb3J0X3NpemUoZGVzYywgc2l6ZSwgMCwgaGlkX2lucHV0
 LCAgICZzYy0+c2NfaWlkKTsKKwlzYy0+c2Nfb3NpemUgPSBoaWRfcmVwb3J0
 X3NpemUoZGVzYywgc2l6ZSwgMCwgaGlkX291dHB1dCwgICZzYy0+c2Nfb2lk
 KTsKKwlzYy0+c2NfZnNpemUgPSBoaWRfcmVwb3J0X3NpemUoZGVzYywgc2l6
 ZSwgMCwgaGlkX2ZlYXR1cmUsICZzYy0+c2NfZmlkKTsKIAogCXNjLT5zY19y
 ZXBkZXNjID0gZGVzYzsKIAlzYy0+c2NfcmVwZGVzY19zaXplID0gc2l6ZTsK
 ZGlmZiAtdXJOIHVzYi5vcmlnL3Vtcy5jIHVzYi5uZXcvdW1zLmMKLS0tIHVz
 Yi5vcmlnL3Vtcy5jCTIwMDgtMDQtMzAgMjI6Mzc6NTQuMDAwMDAwMDAwICsw
 MzAwCisrKyB1c2IubmV3L3Vtcy5jCTIwMDgtMDctMTEgMTk6NTY6MjAuMDAw
 MDAwMDAwICswMzAwCkBAIC0zNTgsNyArMzU4LDggQEAKIAkJaGlkX2xvY2F0
 ZShkZXNjLCBzaXplLCBISURfVVNBR0UyKEhVUF9CVVRUT04sIGkpLAogCQkJ
 CWhpZF9pbnB1dCwgJnNjLT5zY19sb2NfYnRuW2ktMV0sIDApOwogCi0Jc2Mt
 PnNjX2lzaXplID0gaGlkX3JlcG9ydF9zaXplKGRlc2MsIHNpemUsIGhpZF9p
 bnB1dCwgJnNjLT5zY19paWQpOworCXNjLT5zY19pc2l6ZSA9IGhpZF9yZXBv
 cnRfc2l6ZShkZXNjLCBzaXplLCBISURfVVNBR0UyKEhVUF9HRU5FUklDX0RF
 U0tUT1AsIEhVR19NT1VTRSksCisJCQkJCWhpZF9pbnB1dCwgJnNjLT5zY19p
 aWQpOwogCXNjLT5zY19pYnVmID0gbWFsbG9jKHNjLT5zY19pc2l6ZSwgTV9V
 U0IsIE1fTk9XQUlUKTsKIAlpZiAoIXNjLT5zY19pYnVmKSB7CiAJCXByaW50
 ZigiJXM6IG5vIG1lbW9yeVxuIiwgZGV2aWNlX2dldF9uYW1ldW5pdChzYy0+
 c2NfZGV2KSk7CkBAIC0zOTMsNiArMzk0LDcgQEAKIAkgKiBkZXNjcmlwdG9y
 KSwgaXQgc2VlbXMgdGhhdCByZXBvcnQgaWQgMTcgY29udGFpbnMgdGhlIG5l
 Y2Vzc2FyeQogCSAqIG1vdXNlIGluZm9ybWF0aW9uKDMtYnV0dG9ucyxYLFks
 d2hlZWwpIHNvIHdlIHNwZWNpZnkgaXQgbWFudWFsbHkuCiAJICovCisJLyog
 SVMgSVQgTkVTU0VTQVJZID8/PyBORUVEIFRPIEJFIFJFQ0hFQ0sgISEhISEh
 ISBBTkQgRVhDTFVERSAqLwogCWlmICh1YWEtPnZlbmRvciA9PSBVU0JfVkVO
 RE9SX01JQ1JPU09GVCAmJgogCSAgICB1YWEtPnByb2R1Y3QgPT0gVVNCX1BS
 T0RVQ1RfTUlDUk9TT0ZUX1dMTk9URUJPT0szKSB7CiAJCXNjLT5mbGFncyA9
 IFVNU19aOwo=
From simsong at acm.org  Mon Jul 14 16:20:07 2008
From: simsong at acm.org (Simson Garfinkel)
Date: Mon Jul 14 16:20:14 2008
Subject: usb/125450: Removing USB flash card while being accessed causes
	kernel panic
In-Reply-To: <200807102203.35245.hselasky@c2i.net>
References: <200807101940.m6AJe9b0028179@freefall.freebsd.org>
	<200807102203.35245.hselasky@c2i.net>
Message-ID: <06B613DC-AC88-4DCC-B94D-A2D3BDA06F96@acm.org>

> options USB_DEBUG
>
> and
>
> sysctl hw.usb.umass.debug=-1
> sysctl hw.usb.debug=15

Strangely, it was considerably harder to make the machine panic once  
USB_DEBUG was enabled and the usb debug messages were printing to the  
kernel. It took me 6 tries of running the "dd" command on the raw USB  
device and pulling the device before the machine actually panicked.

The panic is happened after the "dd" command finishes printing it's  
statistics. but before the return to the command line.

page fault while in kernel mode.  Fault virtual addr = 0

Is that a dereference through a null pointer?

The IP is 0x20:0xc0460c3b

Is there an easy way to get a link map of the kernel?

Unfortunately, I can't get the stack trace because the system is not  
performing the crash dump. I've never done a FreeBSD crash dump. I  
tried following the directions, but no luck.

I have also tried configuring a dumpdev in the /etc/rc.conf file:

03:27 PM copy:/home/simsong# cat /etc/rc.conf
hostname="copy"
ifconfig_em0="DHCP"
keymap="us.pc-ctrl"
keyrate="fast"
linux_enable="YES"
moused_enable="YES"
sshd_enable="YES"
dumpdev=/dev/ad0s1a

03:28 PM copy:/home/simsong# cat /etc/fstab
# Device		Mountpoint	FStype	Options		Dump	Pass#
/dev/ad0s1b		none		swap	sw		0	0
/dev/ad0s1a		/		ufs	rw		1	1
/dev/ad0s1e		/tmp		ufs	rw		2	2
/dev/ad0s1f		/usr		ufs	rw		2	2
/dev/ad0s1d		/var		ufs	rw		2	2
/dev/acd0		/cdrom		cd9660	ro,noauto	0	0
/dev/acd1		/cdrom1		cd9660	ro,noauto	0	0
/dev/ad8s1d		/big		ufs	rw		3	3
03:29 PM copy:/home/simsong#


I can't figure out why it won't dump.



>
>
> --HPS
>

From toomas.aas at raad.tartu.ee  Mon Jul 14 16:35:33 2008
From: toomas.aas at raad.tartu.ee (Toomas Aas)
Date: Mon Jul 14 16:35:39 2008
Subject: usb/125450: Removing USB flash card while being accessed causes
	kernel panic
In-Reply-To: <06B613DC-AC88-4DCC-B94D-A2D3BDA06F96@acm.org>
References: <200807101940.m6AJe9b0028179@freefall.freebsd.org>
	<200807102203.35245.hselasky@c2i.net>
	<06B613DC-AC88-4DCC-B94D-A2D3BDA06F96@acm.org>
Message-ID: <200807141935.25292.toomas.aas@raad.tartu.ee>

Monday 14 July 2008 19:18:51 kirjutas Simson Garfinkel:

> Unfortunately, I can't get the stack trace because the system is not
> performing the crash dump. I've never done a FreeBSD crash dump. I
> tried following the directions, but no luck.
>
> I have also tried configuring a dumpdev in the /etc/rc.conf file:
>
> 03:27 PM copy:/home/simsong# cat /etc/rc.conf
> hostname="copy"
> ifconfig_em0="DHCP"
> keymap="us.pc-ctrl"
> keyrate="fast"
> linux_enable="YES"
> moused_enable="YES"
> sshd_enable="YES"
> dumpdev=/dev/ad0s1a

dumpdev should be set to swap device - "/dev/ad0s1b" in your case. But 
actually you *should* be able to leave it undefined, in which case "AUTO" is 
used. 

I am also trying to create a pr regarding panic when connecting and 
disconnecting an umass device, and I also can't get a crash dump. Don't know 
why...

> 03:28 PM copy:/home/simsong# cat /etc/fstab
> # Device		Mountpoint	FStype	Options		Dump	Pass#
> /dev/ad0s1b		none		swap	sw		0	0
> /dev/ad0s1a		/		ufs	rw		1	1
> /dev/ad0s1e		/tmp		ufs	rw		2	2
> /dev/ad0s1f		/usr		ufs	rw		2	2
> /dev/ad0s1d		/var		ufs	rw		2	2
> /dev/acd0		/cdrom		cd9660	ro,noauto	0	0
> /dev/acd1		/cdrom1		cd9660	ro,noauto	0	0
> /dev/ad8s1d		/big		ufs	rw		3	3
> 03:29 PM copy:/home/simsong#

--
Toomas Aas
From simsong at acm.org  Mon Jul 14 16:48:11 2008
From: simsong at acm.org (Simson Garfinkel)
Date: Mon Jul 14 16:48:17 2008
Subject: usb/125450: Removing USB flash card while being accessed causes
	kernel panic
In-Reply-To: <200807141935.25292.toomas.aas@raad.tartu.ee>
References: <200807101940.m6AJe9b0028179@freefall.freebsd.org>
	<200807102203.35245.hselasky@c2i.net>
	<06B613DC-AC88-4DCC-B94D-A2D3BDA06F96@acm.org>
	<200807141935.25292.toomas.aas@raad.tartu.ee>
Message-ID: <E6598FAF-1036-45D2-85AC-E4C202CA8EEE@acm.org>


On Jul 14, 2008, at 9:35 AM, Toomas Aas wrote:

> Monday 14 July 2008 19:18:51 kirjutas Simson Garfinkel:
>
>> Unfortunately, I can't get the stack trace because the system is not
>> performing the crash dump. I've never done a FreeBSD crash dump. I
>> tried following the directions, but no luck.
>>
>> I have also tried configuring a dumpdev in the /etc/rc.conf file:
>>
>> 03:27 PM copy:/home/simsong# cat /etc/rc.conf
>> hostname="copy"
>> ifconfig_em0="DHCP"
>> keymap="us.pc-ctrl"
>> keyrate="fast"
>> linux_enable="YES"
>> moused_enable="YES"
>> sshd_enable="YES"
>> dumpdev=/dev/ad0s1a
>
> dumpdev should be set to swap device - "/dev/ad0s1b" in your case. But
> actually you *should* be able to leave it undefined, in which case  
> "AUTO" is
> used.

Huh. How about that. Dyslexia strikes again. Let me leave it undefined  
and see what happens.

>
>
> I am also trying to create a pr regarding panic when connecting and
> disconnecting an umass device, and I also can't get a crash dump.  
> Don't know
> why...

Hm... I guess I'm lucky that it didn't wipe out /.

From admin at lissyara.su  Mon Jul 14 16:50:05 2008
From: admin at lissyara.su (Alex Keda)
Date: Mon Jul 14 16:50:12 2008
Subject: usb/117911: [ums] [request] Mouse Gembird MUSWC not work
Message-ID: <200807141650.m6EGo4cM048650@freefall.freebsd.org>

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

From: Alex Keda <admin@lissyara.su>
To: bug-followup@FreeBSD.org, admin@lissyara.su
Cc:  
Subject: Re: usb/117911: [ums] [request] Mouse Gembird MUSWC not work
Date: Mon, 14 Jul 2008 20:42:08 +0400

 This is a multi-part message in MIME format.
 --------------050502020101000706000208
 Content-Type: text/plain; charset=UTF-8; format=flowed
 Content-Transfer-Encoding: 7bit
 
 resend mail.
 ============
 hi! this problem an HID parser on FreeBSD and other *BSD system
 
 i'am use a krepdump http://people.freebsd.org/~kaiw/tools/krepdump.tgz
 to show full HID protocol dump from this USB Mouse
 
 -----------------------------------------------
 [report desc size=79]
 USAGE PAGE Consumer(0xc)
 USAGE Consumer Control(0x1)[Consumer(0xc)]
 COLLECTION Application(1)
    REPORT ID 1
    USAGE MINIMUM Unassigned(0)
    USAGE MAXIMUM AC Underline(576)
    LOGICAL MINIMUM 0
    LOGICAL MAXIMUM 576
    REPORT SIZE 16
    REPORT COUNT 1
    INPUT ( Data Array Absolute ) (0)
 END COLLECTION
 USAGE PAGE Generic Desktop(0x1)
 USAGE Mouse(0x2)[Generic Desktop(0x1)]
 COLLECTION Application(1)
    REPORT ID 2
    USAGE Pointer(0x1)[Generic Desktop(0x1)]
    COLLECTION Physical(0)
      USAGE PAGE Button(0x9)
      USAGE MINIMUM Button1(1)
      USAGE MAXIMUM Button3(3)
      LOGICAL MINIMUM 0
      LOGICAL MAXIMUM 1
      REPORT SIZE 1
      REPORT COUNT 3
      INPUT ( Data Variable Absolute ) (2)
      REPORT SIZE 5
      REPORT COUNT 1
      INPUT ( Const Array Absolute ) (1)
      USAGE PAGE Generic Desktop(0x1)
      USAGE X(0x30)[Generic Desktop(0x1)]
      USAGE Y(0x31)[Generic Desktop(0x1)]
      USAGE Wheel(0x38)[Generic Desktop(0x1)]
      LOGICAL MINIMUM -127
      LOGICAL MAXIMUM 127
      REPORT SIZE 8
      REPORT COUNT 3
      INPUT ( Data Variable Relative ) (6)
    END COLLECTION
 END COLLECTION
 [hexdump]
 0000 05 0C 09 01 A1 01 85 01 19 00 2A 40 02 15 00 26
 0010 40 02 75 10 95 01 81 00 C0 05 01 09 02 A1 01 85
 0020 02 09 01 A1 00 05 09 19 01 29 03 15 00 25 01 75
 0030 01 95 03 81 02 75 05 95 01 81 01 05 01 09 30 09
 0040 31 09 38 15 81 25 7F 75 08 95 03 81 06 C0 C0
 
 --------------------------------------------------
 as you can see
 this Mouse generate 2 HID protocol collection
 
 the first collection is
 USAGE PAGE Consumer(0xc)
 USAGE Consumer Control(0x1)[Consumer(0xc)]
 COLLECTION Application(1)
    REPORT ID 1
    ...
 
 the second collection is
 USAGE PAGE Generic Desktop(0x1)
 USAGE Mouse(0x2)[Generic Desktop(0x1)]
 COLLECTION Application(1)
    REPORT ID 2
    ...
 
 two collection describe a two protocol
 first protocol - AC line (Wireless Mouse from AC battarey)
 second protocol - Mouse movement
 
 
 an exists FreeBSD HID parser don't work with such collection
 to parse it used first collection, allways
 is't correct!!
 
 as example with this Mouse
 
 #kldload ums.ko
 #dmesg -a | grep ums
 
 ----------------------
 ums_attach: 3 buttons
 ums_attach: X   24/8
 ums_attach: Y   32/8
 ums_attach: Z   40/8
 ums_attach: B1  16/1
 ums_attach: B2  17/1
 ums_attach: B3  18/1
 ums_attach: size=3, id=1
 ----------------------
 
 the HID parser use first HID collection to parse Mouse movenent
 Mouse not work!!
 
 
 
 i'am fixx the HID parser
 to correct use HID collection
 after patch http://paradox.org.ua/work/fixx.tar.bz2
 ----------------------
 ums_attach: 3 buttons
 ums_attach: X   8/8
 ums_attach: Y   16/8
 ums_attach: Z   24/8
 ums_attach: B1  0/1
 ums_attach: B2  1/1
 ums_attach: B3  2/1
 ums_attach: size=5, id=2
 ----------------------
 and Mouse works fine!
 
 i think this patch fixx
 fixed all USB Mouse problem an *BSD system
 
 --------------050502020101000706000208
 Content-Type: text/plain;
  name="usb.diff"
 Content-Transfer-Encoding: base64
 Content-Disposition: inline;
  filename="usb.diff"
 
 ZGlmZiAtTnJ1IHN5cy9kZXYvdXNiLm9yaWcvaGlkLmMgc3lzL2Rldi91c2IvaGlkLmMKLS0t
 IHN5cy9kZXYvdXNiLm9yaWcvaGlkLmMJMjAwNy0wNi0yMCAwOToxMDo1Mi4wMDAwMDAwMDAg
 KzA0MDAKKysrIHN5cy9kZXYvdXNiL2hpZC5jCTIwMDgtMDctMTQgMTY6MDE6MzkuMDAwMDAw
 MDAwICswNDAwCkBAIC03Miw2ICs3Miw3IEBACiAJaW50IG11bHRpOwogCWludCBtdWx0aW1h
 eDsKIAlpbnQga2luZHNldDsKKwlpbnQgdXNhZ2U7CiB9OwogCiBzdGF0aWMgdm9pZApAQCAt
 MTE1LDcgKzExNiw3IEBACiB9CiAKIGludAotaGlkX2dldF9pdGVtKHN0cnVjdCBoaWRfZGF0
 YSAqcywgc3RydWN0IGhpZF9pdGVtICpoKQoraGlkX2dldF9pdGVtKHN0cnVjdCBoaWRfZGF0
 YSAqcywgdV9pbnQzMl90IHUsIHN0cnVjdCBoaWRfaXRlbSAqaCkKIHsKIAlzdHJ1Y3QgaGlk
 X2l0ZW0gKmMgPSAmcy0+Y3VyOwogCXVuc2lnbmVkIGludCBiVGFnLCBiVHlwZSwgYlNpemU7
 CkBAIC0xOTMsNiArMTk0LDkgQEAKIAkJY2FzZSAwOgkJCS8qIE1haW4gKi8KIAkJCXN3aXRj
 aCAoYlRhZykgewogCQkJY2FzZSA4OgkJLyogSW5wdXQgKi8KKwkJCQlpZiAocy0+dXNhZ2Ug
 IT0gdSA+PjE2ICYmIHUgIT0gMCkKKwkJCQkJYnJlYWs7CisKIAkJCQlpZiAoIShzLT5raW5k
 c2V0ICYgKDEgPDwgaGlkX2lucHV0KSkpCiAJCQkJCWNvbnRpbnVlOwogCQkJCWMtPmtpbmQg
 PSBoaWRfaW5wdXQ7CkBAIC0yMjMsNiArMjI3LDkgQEAKIAkJCQkJcmV0dXJuICgxKTsKIAkJ
 CQl9CiAJCQljYXNlIDk6CQkvKiBPdXRwdXQgKi8KKwkJCQlpZiAocy0+dXNhZ2UgIT0gdSA+
 PjE2ICYmIHUgIT0gMCkKKwkJCQkJYnJlYWs7CisKIAkJCQlpZiAoIShzLT5raW5kc2V0ICYg
 KDEgPDwgaGlkX291dHB1dCkpKQogCQkJCQljb250aW51ZTsKIAkJCQljLT5raW5kID0gaGlk
 X291dHB1dDsKQEAgLTIzMiwxMSArMjM5LDE2IEBACiAJCQkJYy0+a2luZCA9IGhpZF9jb2xs
 ZWN0aW9uOwogCQkJCWMtPmNvbGxlY3Rpb24gPSBkdmFsOwogCQkJCWMtPmNvbGxldmVsKys7
 CisJCQkJaWYgKGMtPmNvbGxldmVsID4gMCAmJiB1ICE9IDApCisJCQkJCXMtPnVzYWdlID0g
 Yy0+X3VzYWdlX3BhZ2UgPj4gMTY7CiAJCQkJKmggPSAqYzsKIAkJCQloaWRfY2xlYXJfbG9j
 YWwoYyk7CiAJCQkJcy0+bnUgPSAwOwogCQkJCXJldHVybiAoMSk7CiAJCQljYXNlIDExOgkv
 KiBGZWF0dXJlICovCisJCQkJaWYgKHMtPnVzYWdlICE9IHUgPj4xNiAmJiB1ICE9IDApCisJ
 CQkJCWJyZWFrOworCiAJCQkJaWYgKCEocy0+a2luZHNldCAmICgxIDw8IGhpZF9mZWF0dXJl
 KSkpCiAJCQkJCWNvbnRpbnVlOwogCQkJCWMtPmtpbmQgPSBoaWRfZmVhdHVyZTsKQEAgLTI1
 OCw2ICsyNzAsOSBAQAogCQkJc3dpdGNoIChiVGFnKSB7CiAJCQljYXNlIDA6CiAJCQkJYy0+
 X3VzYWdlX3BhZ2UgPSBkdmFsIDw8IDE2OworCisJCQkJaWYgKHUgIT0gMCAmJiB1Pj4xNiA9
 PSBkdmFsKQorCQkJCQlzLT51c2FnZSA9IGR2YWw7CiAJCQkJYnJlYWs7CiAJCQljYXNlIDE6
 CiAJCQkJYy0+bG9naWNhbF9taW5pbXVtID0gZHZhbDsKQEAgLTM2NCw3ICszNzksNyBAQAog
 fQogCiBpbnQKLWhpZF9yZXBvcnRfc2l6ZSh2b2lkICpidWYsIGludCBsZW4sIGVudW0gaGlk
 X2tpbmQgaywgdV9pbnQ4X3QgKmlkcCkKK2hpZF9yZXBvcnRfc2l6ZSh2b2lkICpidWYsIGlu
 dCBsZW4sIHVfaW50MzJfdCB1LCBlbnVtIGhpZF9raW5kIGssIHVfaW50OF90ICppZHApCiB7
 CiAJc3RydWN0IGhpZF9kYXRhICpkOwogCXN0cnVjdCBoaWRfaXRlbSBoOwpAQCAtMzcyLDcg
 KzM4Nyw3IEBACiAKIAlpZCA9IDA7CiAJaGkgPSBsbyA9IC0xOwotCWZvciAoZCA9IGhpZF9z
 dGFydF9wYXJzZShidWYsIGxlbiwgMTw8ayk7IGhpZF9nZXRfaXRlbShkLCAmaCk7ICkKKwlm
 b3IgKGQgPSBoaWRfc3RhcnRfcGFyc2UoYnVmLCBsZW4sIDE8PGspOyBoaWRfZ2V0X2l0ZW0o
 ZCwgdSwgJmgpOyApCiAJCWlmIChoLmtpbmQgPT0gaykgewogCQkJaWYgKGgucmVwb3J0X0lE
 ICE9IDAgJiYgIWlkKQogCQkJCWlkID0gaC5yZXBvcnRfSUQ7CkBAIC0zOTksNyArNDE0LDcg
 QEAKIAlzdHJ1Y3QgaGlkX2RhdGEgKmQ7CiAJc3RydWN0IGhpZF9pdGVtIGg7CiAKLQlmb3Ig
 KGQgPSBoaWRfc3RhcnRfcGFyc2UoZGVzYywgc2l6ZSwgMTw8ayk7IGhpZF9nZXRfaXRlbShk
 LCAmaCk7ICkgeworCWZvciAoZCA9IGhpZF9zdGFydF9wYXJzZShkZXNjLCBzaXplLCAxPDxr
 KTsgaGlkX2dldF9pdGVtKGQsIHUsICZoKTsgKSB7CiAJCWlmIChoLmtpbmQgPT0gayAmJiAh
 KGguZmxhZ3MgJiBISU9fQ09OU1QpICYmIGgudXNhZ2UgPT0gdSkgewogCQkJaWYgKGxvYyAh
 PSBOVUxMKQogCQkJCSpsb2MgPSBoLmxvYzsKQEAgLTQ1Miw3ICs0NjcsNyBAQAogCWlmICho
 ZCA9PSBOVUxMKQogCQlyZXR1cm4gKDApOwogCi0JZXJyID0gaGlkX2dldF9pdGVtKGhkLCAm
 aGkpICYmCisJZXJyID0gaGlkX2dldF9pdGVtKGhkLCB1c2FnZSwgJmhpKSAmJgogCSAgICBo
 aS5raW5kID09IGhpZF9jb2xsZWN0aW9uICYmCiAJICAgIGhpLnVzYWdlID09IHVzYWdlOwog
 CWhpZF9lbmRfcGFyc2UoaGQpOwpkaWZmIC1OcnUgc3lzL2Rldi91c2Iub3JpZy9oaWQuaCBz
 eXMvZGV2L3VzYi9oaWQuaAotLS0gc3lzL2Rldi91c2Iub3JpZy9oaWQuaAkyMDA1LTAxLTA2
 IDA0OjQzOjI3LjAwMDAwMDAwMCArMDMwMAorKysgc3lzL2Rldi91c2IvaGlkLmgJMjAwOC0w
 Ny0xNCAxNjowMTozOS4wMDAwMDAwMDAgKzA0MDAKQEAgLTgyLDggKzgyLDggQEAKIAogc3Ry
 dWN0IGhpZF9kYXRhICpoaWRfc3RhcnRfcGFyc2Uodm9pZCAqZCwgaW50IGxlbiwgaW50IGtp
 bmRzZXQpOwogdm9pZCBoaWRfZW5kX3BhcnNlKHN0cnVjdCBoaWRfZGF0YSAqcyk7Ci1pbnQg
 aGlkX2dldF9pdGVtKHN0cnVjdCBoaWRfZGF0YSAqcywgc3RydWN0IGhpZF9pdGVtICpoKTsK
 LWludCBoaWRfcmVwb3J0X3NpemUodm9pZCAqYnVmLCBpbnQgbGVuLCBlbnVtIGhpZF9raW5k
 IGssIHVfaW50OF90ICppZCk7CitpbnQgaGlkX2dldF9pdGVtKHN0cnVjdCBoaWRfZGF0YSAq
 cywgdV9pbnQzMl90IHUsIHN0cnVjdCBoaWRfaXRlbSAqaCk7CitpbnQgaGlkX3JlcG9ydF9z
 aXplKHZvaWQgKmJ1ZiwgaW50IGxlbiwgdV9pbnQzMl90IHUsIGVudW0gaGlkX2tpbmQgaywg
 dV9pbnQ4X3QgKmlkKTsKIGludCBoaWRfbG9jYXRlKHZvaWQgKmRlc2MsIGludCBzaXplLCB1
 X2ludDMyX3QgdXNhZ2UsCiAJCSAgICBlbnVtIGhpZF9raW5kIGtpbmQsIHN0cnVjdCBoaWRf
 bG9jYXRpb24gKmxvYywKIAkJICAgIHVfaW50MzJfdCAqZmxhZ3MpOwpkaWZmIC1OcnUgc3lz
 L2Rldi91c2Iub3JpZy91Y3ljb20uYyBzeXMvZGV2L3VzYi91Y3ljb20uYwotLS0gc3lzL2Rl
 di91c2Iub3JpZy91Y3ljb20uYwkyMDA3LTA2LTIxIDE4OjQyOjMzLjAwMDAwMDAwMCArMDQw
 MAorKysgc3lzL2Rldi91c2IvdWN5Y29tLmMJMjAwOC0wNy0xNCAxNjowMTozOS4wMDAwMDAw
 MDAgKzA0MDAKQEAgLTIyMSw5ICsyMjEsOSBAQAogCX0KIAogCS8qIGdldCByZXBvcnQgc2l6
 ZXMgKi8KLQlzYy0+c2NfZmxlbiA9IGhpZF9yZXBvcnRfc2l6ZSh1cmQsIHVyZGxlbiwgaGlk
 X2ZlYXR1cmUsICZzYy0+c2NfZmlkKTsKLQlzYy0+c2NfaWxlbiA9IGhpZF9yZXBvcnRfc2l6
 ZSh1cmQsIHVyZGxlbiwgaGlkX2lucHV0LCAmc2MtPnNjX2lpZCk7Ci0Jc2MtPnNjX29sZW4g
 PSBoaWRfcmVwb3J0X3NpemUodXJkLCB1cmRsZW4sIGhpZF9vdXRwdXQsICZzYy0+c2Nfb2lk
 KTsKKwlzYy0+c2NfZmxlbiA9IGhpZF9yZXBvcnRfc2l6ZSh1cmQsIHVyZGxlbiwgMCwgaGlk
 X2ZlYXR1cmUsICZzYy0+c2NfZmlkKTsgLyogTkVFRCBUTyBCRSBGSVhYID8/Pz8/ICovCisJ
 c2MtPnNjX2lsZW4gPSBoaWRfcmVwb3J0X3NpemUodXJkLCB1cmRsZW4sIDAsIGhpZF9pbnB1
 dCwgJnNjLT5zY19paWQpOwkvKiBORUVEIFRPIEJFIEZJWFggPz8/Pz8gKi8KKwlzYy0+c2Nf
 b2xlbiA9IGhpZF9yZXBvcnRfc2l6ZSh1cmQsIHVyZGxlbiwgMCwgaGlkX291dHB1dCwgJnNj
 LT5zY19vaWQpOwkvKiBORUVEIFRPIEJFIEZJWFggPz8/Pz8gKi8KIAogCWlmIChzYy0+c2Nf
 aWxlbiA+IFVDWUNPTV9NQVhfSU9MRU4gfHwgc2MtPnNjX29sZW4gPiBVQ1lDT01fTUFYX0lP
 TEVOKSB7CiAJCWRldmljZV9wcmludGYoZGV2LCAiSS9PIHJlcG9ydCBzaXplIHRvbyBiaWcg
 KCV6dSwgJXp1LCAldSlcbiIsCmRpZmYgLU5ydSBzeXMvZGV2L3VzYi5vcmlnL3VoaWQuYyBz
 eXMvZGV2L3VzYi91aGlkLmMKLS0tIHN5cy9kZXYvdXNiLm9yaWcvdWhpZC5jCTIwMDctMDYt
 MjEgMTg6NDI6MzMuMDAwMDAwMDAwICswNDAwCisrKyBzeXMvZGV2L3VzYi91aGlkLmMJMjAw
 OC0wNy0xNCAxNjowMTozOS4wMDAwMDAwMDAgKzA0MDAKQEAgLTMyMCw5ICszMjAsOSBAQAog
 CiAJKHZvaWQpdXNiZF9zZXRfaWRsZShpZmFjZSwgMCwgMCk7CiAKLQlzYy0+c2NfaXNpemUg
 PSBoaWRfcmVwb3J0X3NpemUoZGVzYywgc2l6ZSwgaGlkX2lucHV0LCAgICZzYy0+c2NfaWlk
 KTsKLQlzYy0+c2Nfb3NpemUgPSBoaWRfcmVwb3J0X3NpemUoZGVzYywgc2l6ZSwgaGlkX291
 dHB1dCwgICZzYy0+c2Nfb2lkKTsKLQlzYy0+c2NfZnNpemUgPSBoaWRfcmVwb3J0X3NpemUo
 ZGVzYywgc2l6ZSwgaGlkX2ZlYXR1cmUsICZzYy0+c2NfZmlkKTsKKwlzYy0+c2NfaXNpemUg
 PSBoaWRfcmVwb3J0X3NpemUoZGVzYywgc2l6ZSwgMCwgaGlkX2lucHV0LCAgICZzYy0+c2Nf
 aWlkKTsKKwlzYy0+c2Nfb3NpemUgPSBoaWRfcmVwb3J0X3NpemUoZGVzYywgc2l6ZSwgMCwg
 aGlkX291dHB1dCwgICZzYy0+c2Nfb2lkKTsKKwlzYy0+c2NfZnNpemUgPSBoaWRfcmVwb3J0
 X3NpemUoZGVzYywgc2l6ZSwgMCwgaGlkX2ZlYXR1cmUsICZzYy0+c2NfZmlkKTsKIAogCXNj
 LT5zY19yZXBkZXNjID0gZGVzYzsKIAlzYy0+c2NfcmVwZGVzY19zaXplID0gc2l6ZTsKZGlm
 ZiAtTnJ1IHN5cy9kZXYvdXNiLm9yaWcvdW1zLmMgc3lzL2Rldi91c2IvdW1zLmMKLS0tIHN5
 cy9kZXYvdXNiLm9yaWcvdW1zLmMJMjAwOC0wNC0zMCAyMzozNzo1NC4wMDAwMDAwMDAgKzA0
 MDAKKysrIHN5cy9kZXYvdXNiL3Vtcy5jCTIwMDgtMDctMTQgMTY6MDE6MzkuMDAwMDAwMDAw
 ICswNDAwCkBAIC0zNTgsNyArMzU4LDggQEAKIAkJaGlkX2xvY2F0ZShkZXNjLCBzaXplLCBI
 SURfVVNBR0UyKEhVUF9CVVRUT04sIGkpLAogCQkJCWhpZF9pbnB1dCwgJnNjLT5zY19sb2Nf
 YnRuW2ktMV0sIDApOwogCi0Jc2MtPnNjX2lzaXplID0gaGlkX3JlcG9ydF9zaXplKGRlc2Ms
 IHNpemUsIGhpZF9pbnB1dCwgJnNjLT5zY19paWQpOworCXNjLT5zY19pc2l6ZSA9IGhpZF9y
 ZXBvcnRfc2l6ZShkZXNjLCBzaXplLCBISURfVVNBR0UyKEhVUF9HRU5FUklDX0RFU0tUT1As
 IEhVR19NT1VTRSksCisJCQkJCWhpZF9pbnB1dCwgJnNjLT5zY19paWQpOwogCXNjLT5zY19p
 YnVmID0gbWFsbG9jKHNjLT5zY19pc2l6ZSwgTV9VU0IsIE1fTk9XQUlUKTsKIAlpZiAoIXNj
 LT5zY19pYnVmKSB7CiAJCXByaW50ZigiJXM6IG5vIG1lbW9yeVxuIiwgZGV2aWNlX2dldF9u
 YW1ldW5pdChzYy0+c2NfZGV2KSk7CkBAIC0zOTMsNiArMzk0LDcgQEAKIAkgKiBkZXNjcmlw
 dG9yKSwgaXQgc2VlbXMgdGhhdCByZXBvcnQgaWQgMTcgY29udGFpbnMgdGhlIG5lY2Vzc2Fy
 eQogCSAqIG1vdXNlIGluZm9ybWF0aW9uKDMtYnV0dG9ucyxYLFksd2hlZWwpIHNvIHdlIHNw
 ZWNpZnkgaXQgbWFudWFsbHkuCiAJICovCisJLyogSVMgSVQgTkVTU0VTQVJZID8/PyBORUVE
 IFRPIEJFIFJFQ0hFQ0sgISEhISEhISBBTkQgRVhDTFVERSAqLwogCWlmICh1YWEtPnZlbmRv
 ciA9PSBVU0JfVkVORE9SX01JQ1JPU09GVCAmJgogCSAgICB1YWEtPnByb2R1Y3QgPT0gVVNC
 X1BST0RVQ1RfTUlDUk9TT0ZUX1dMTk9URUJPT0szKSB7CiAJCXNjLT5mbGFncyA9IFVNU19a
 Owo=
 --------------050502020101000706000208--
From pschmehl_lists at tx.rr.com  Mon Jul 14 17:05:13 2008
From: pschmehl_lists at tx.rr.com (Paul Schmehl)
Date: Mon Jul 14 17:05:24 2008
Subject: Crash when booting with umass device connected
Message-ID: <3632806C83D31F1A23DE0F0A@utd65257.utdallas.edu>

I'd like to work with someone to provide useful information about this problem. 
Ever since upgrading my workstation to 7.0 STABLE, I cannot boot with my umass 
device connected.  Once the system is up and running, I can mount the device 
with no problems.

During the boot process, the device is detected, but then it causes a kernel 
panic.  I'm logging the console to console.log, but there is no useful 
information there.  I've enabled USB_DEBUG and rebuilt the kernel, but I have 
no idea how to capture the information printed to the console when this failure 
occurs.  (I'm seriously considering taking a photograph of the screen since I 
can't do a screenshot and I can't find the information in any logs.)

I'd post a bug, but without some trace information, it's kind of worthless.  If 
I can get help from someone knowledgeable, I'll provide whatever information is 
needed to track this problem down.

-- 
Paul Schmehl
As if it wasn't already obvious,
my opinions are my own and not
those of my employer.

From admin at lissyara.su  Mon Jul 14 17:50:04 2008
From: admin at lissyara.su (Alex Keda)
Date: Mon Jul 14 17:50:10 2008
Subject: usb/117911: [ums] [request] Mouse Gembird MUSWC not work
Message-ID: <200807141750.m6EHo33e053967@freefall.freebsd.org>

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

From: Alex Keda <admin@lissyara.su>
To: bug-followup@FreeBSD.org, admin@lissyara.su
Cc:  
Subject: Re: usb/117911: [ums] [request] Mouse Gembird MUSWC not work
Date: Mon, 14 Jul 2008 21:43:01 +0400

 this patch work correct for my mouse (CURRENT, i386)
From onemda at gmail.com  Tue Jul 15 09:23:15 2008
From: onemda at gmail.com (Paul B. Mahol)
Date: Tue Jul 15 09:23:22 2008
Subject: Crash when booting with umass device connected
In-Reply-To: <3a142e750807150219j5a619135x19edba16e6590c21@mail.gmail.com>
References: <3632806C83D31F1A23DE0F0A@utd65257.utdallas.edu>
	<3a142e750807150219j5a619135x19edba16e6590c21@mail.gmail.com>
Message-ID: <3a142e750807150223w6f264048wd9e13ae8846b593c@mail.gmail.com>

On 7/14/08, Paul Schmehl <pschmehl_lists@tx.rr.com> wrote:
> I'd like to work with someone to provide useful information about this
> problem.
> Ever since upgrading my workstation to 7.0 STABLE, I cannot boot with my
> umass
> device connected.  Once the system is up and running, I can mount the
> device
> with no problems.
>
> During the boot process, the device is detected, but then it causes a
> kernel
> panic.  I'm logging the console to console.log, but there is no useful
> information there.  I've enabled USB_DEBUG and rebuilt the kernel, but I
> have
> no idea how to capture the information printed to the console when this
> failure
> occurs.  (I'm seriously considering taking a photograph of the screen
> since
> I
> can't do a screenshot and I can't find the information in any logs.)
>
> I'd post a bug, but without some trace information, it's kind of
> worthless.
> If
> I can get help from someone knowledgeable, I'll provide whatever
> information
> is
> needed to track this problem down.

Look in Developers handbook for more info
/usr/share/doc/en/books/developers-handbook/index.html

I think that textdumps are MFCed to STABLE.
Textdumps provide easy way for gathering backtraces.
From hselasky at c2i.net  Tue Jul 15 09:31:16 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Tue Jul 15 09:31:24 2008
Subject: Quirks
In-Reply-To: <20080711004223.76d17a7e@gmx.net>
References: <20080709223926.142cbe5b@gmx.net>
	<200807101809.59532.hselasky@c2i.net>
	<20080711004223.76d17a7e@gmx.net>
Message-ID: <200807151132.53525.hselasky@c2i.net>

On Friday 11 July 2008, Tino Engel wrote:
> Hi --HPS,
>
> > Hi Tino,
> >
> > Let's focus on getting the USB mass storage problems fixed first.
> > There are plenty of USB Mass Storage IR's in the database.
> >
> > What kind of quirk strategy would you like to apply?
> >
> > If the device fails the Mass Storage test, then switch on all
> > possible quirks ? Which means that the user might have to replug the
> > USB device ?
> >
> > --HPS
>
> Here is a map of what I think would be reasonable:
>
>
> At first there is a file (let's say /etc/ums.conf) which holds the
> configuration of how to approach new devices. The file is delivered
> with reasonable defaults.
>
>
> GLOBAL OPTIONS:
> ===============
> If the option ALL_QUIRKS="YES" is set, a new UMS is approached with
> all quirks. If something fails here, there is pretty much nothing left
> to do.
>
> Also all other quirks can be set on by default:
> Example: Q_NO_SYNC_CACHE="YES" would disable cache syncing for all msc
> devices.
>
> So, now there more sophisticated part:
> In case the all quirks option is not set, 2 cases remain in this model:
>
> CASE 1:
> =======
>
> Case 1 describes the case of a MSC device that hangs up
> after receiving a command it could not be able to handle. It ends in a
> unfixable state, even a bus reset cannot help.
>
> That leads us to the conclusion, the device has to be unplugged in
> order to proceed. The only question is, how to proceed then. Also in
> this case, the was is determined by configuration.
>
> The easiest case would be given by using the option:
> STALLED_ALL_QUIRKS="YES"
>
> Then dmesg would tell to replug the device (and other events would be
> triggered, for whatsoever), and all quirks would be applied for this
> device from there on. The information would be held in /var/db/ums or
> whatever appropriate place.
>
> Additionally one could think about enabling a chained quirk set:
> For example I could set STALLED_Q_NO_SYNC_CACHE="1" and
> STALLED_ALL_QUIRKS="2" which would have the effect, that for this
> specific device, cache syncing would be disabled (quirked) on first
> reconnect, and, if failed, all quirks would be activated on next
> connect. dmesg would properly inform me to replug.
>
> Nice would also be an option STALLED_INTELLIGENCE="YES" which would try
> same order as in case 2.
>
> The successful quirk combination is also stored in /var/db/ums.
>
> In addition, it would be nice to have a vendor/device specific config
> format. (e.g. STALLED_Q_NO_SYNC_CACHE="SAMSUNG,1")
>
> This way would have the advantage that my device runs anyhow without
> kernel recompilation (although i might have to replug a couple of times
> in worst case :-( )
>
> CASE 2:
> =======
> In case 2, the device can recover by a usb reset. There it is a runtime
> issue, if just all quirk permutations can be tested or if a
> configuration similar to case 1 is appropriate. (I assume, we can live
> with the runtime there, since plugging an usb device is not a
> real-time-thing ^^)
> Than we can have a nice logic (from most common to less common quirk
> permutations order)
>
> Here we should definitely have a config file, containing device
> specific quirk information, which can be updated.
>
>
> Anyhow, feedback events (e.g. for graphical connection tools)
> interaction with things like HAL and whatever comes up should be
> considered, so it can be implemented sooner or later...
>
>
> What do you think?

Hi Tino,

I think this should be all automatic. Most users will have no clue what to put 
in those configuration files.

Any others have any opinion about this on the list?

--HPS
From bst2006 at dva.dyndns.org  Tue Jul 15 10:30:01 2008
From: bst2006 at dva.dyndns.org (Boris S.)
Date: Tue Jul 15 10:30:31 2008
Subject: usb/125631: [usb][ums] kernel panic during bootup while 'Logitech
	USB receiver' (Logitech RX650 wireless mouse) is connected
Message-ID: <20080715100547.462A7823F3@dva.homeunix.org>


>Number:         125631
>Category:       usb
>Synopsis:       [usb][ums] kernel panic during bootup while 'Logitech USB receiver' (Logitech RX650 wireless mouse) is connected
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jul 15 10:30:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Boris S.
>Release:        FreeBSD 7.0-STABLE amd64
>Organization:
private
>Environment:
System: FreeBSD xxx.intranet.local 7.0-STABLE FreeBSD 7.0-STABLE #0: Sun Jun 22 13:58:13 CEST 2008 root@xxx.intranet.local:/usr/obj/usr/src/sys/XXX amd64

Mainboard: Gigabyte GA-MA78G-DS3H
Chipset: AMD760G
Southbridge: AMD SB700
CPU: AMD X2 4850e

>Description:
The system will panic during bootup while a 'Logitech USB receiver' is connected.
It happens right after the vga probe:


vga0: <GENERIC ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 1.000 msec
panic: ohci_add_done: addr 0xcfef1cd0 not found
cpuid = 0
Uptime: 1s


If the USB receiver is connected AFTER the boot up, it will be detected correctly and works very reliable.
It is detected as:

ums0: <Logitech USB Receiver, class 0/0, rev 1.10/46.00, addr 2> on uhub4
ums0: 8 buttons and Z dir.
uhid0: <Logitech USB Receiver, class 0/0, rev 1.10/46.00, addr 2> on uhub4

>How-To-Repeat:
plug in the USB receiver and start the system.
>Fix:
Workaround: plug in the USB receiver after the boot up. Then it will be detected without panic.


--- dmesg.boot begins here ---
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-STABLE #0: Sun Jun 22 13:58:13 CEST 2008
    root@xxx.intranet.local:/usr/obj/usr/src/sys/XXX
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) Dual Core Processor 4850e (2505.35-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x60fb2  Stepping = 2
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x2001<SSE3,CX16>
  AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
  AMD Features2=0x11f<LAHF,CMP,SVM,ExtAPIC,CR8,Prefetch>
  Cores per package: 2
usable memory = 4149764096 (3957 MB)
avail memory  = 3990966272 (3806 MB)
ACPI APIC Table: <GBT    GBTUACPI>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0: Changing APIC ID to 2
ioapic0 <Version 2.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: <GBT GBTUACPI> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, cfde0000 (3) failed
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
cpu0: <ACPI CPU> on acpi0
powernow0: <PowerNow! K8> on cpu0
cpu1: <ACPI CPU> on acpi0
powernow1: <PowerNow! K8> on cpu1
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xee00-0xeeff mem 0xd8000000-0xdfffffff,0xfdee0000-0xfdeeffff,0xfdd00000-0xfddfffff irq 18 at device 5.0 on pci1
pci1: <multimedia> at device 5.1 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> irq 18 at device 6.0 on pci0
pci2: <ACPI PCI bus> on pcib2
em0: <Intel(R) PRO/1000 Network Connection 6.9.5> port 0xdf00-0xdf1f mem 0xfdce0000-0xfdcfffff,0xfdcc0000-0xfdcdffff irq 18 at device 0.0 on pci2
em0: Using MSI interrupt
em0: [FILTER]
em0: Ethernet address: 00:1b:21:1c:0d:18
pcib3: <ACPI PCI-PCI bridge> irq 18 at device 10.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pci3: <network, ethernet> at device 0.0 (no driver attached)
atapci0: <ATI IXP700 SATA300 controller> port 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 0xfe02f000-0xfe02f3ff irq 22 at device 17.0 on pci0
atapci0: [ITHREAD]
atapci0: AHCI Version 01.10 controller with 4 ports detected
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci0
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci0
ata5: [ITHREAD]
ohci0: <OHCI (generic) USB controller> mem 0xfe02e000-0xfe02efff irq 16 at device 18.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 3 ports with 3 removable, self powered
ohci1: <OHCI (generic) USB controller> mem 0xfe02d000-0xfe02dfff irq 16 at device 18.1 on pci0
ohci1: [GIANT-LOCKED]
ohci1: [ITHREAD]
usb1: OHCI version 1.0, legacy support
usb1: SMM does not respond, resetting
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 3 ports with 3 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfe02c000-0xfe02c0ff irq 17 at device 18.2 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb2: EHCI version 1.0
usb2: companion controllers, 3 ports each: usb0 usb1
usb2: <EHCI (generic) USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: <ATI EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2
uhub2: 6 ports with 6 removable, self powered
ohci2: <OHCI (generic) USB controller> mem 0xfe02b000-0xfe02bfff irq 18 at device 19.0 on pci0
ohci2: [GIANT-LOCKED]
ohci2: [ITHREAD]
usb3: OHCI version 1.0, legacy support
usb3: SMM does not respond, resetting
usb3: <OHCI (generic) USB controller> on ohci2
usb3: USB revision 1.0
uhub3: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 3 ports with 3 removable, self powered
ohci3: <OHCI (generic) USB controller> mem 0xfe02a000-0xfe02afff irq 18 at device 19.1 on pci0
ohci3: [GIANT-LOCKED]
ohci3: [ITHREAD]
usb4: OHCI version 1.0, legacy support
usb4: SMM does not respond, resetting
usb4: <OHCI (generic) USB controller> on ohci3
usb4: USB revision 1.0
uhub4: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhub4: 3 ports with 3 removable, self powered
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xfe029000-0xfe0290ff irq 19 at device 19.2 on pci0
ehci1: [GIANT-LOCKED]
ehci1: [ITHREAD]
usb5: EHCI version 1.0
usb5: companion controllers, 3 ports each: usb3 usb4
usb5: <EHCI (generic) USB 2.0 controller> on ehci1
usb5: USB revision 2.0
uhub5: <ATI EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb5
uhub5: 6 ports with 6 removable, self powered
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)
atapci1: <ATI IXP700 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f at device 20.1 on pci0
ata0: <ATA channel 0> on atapci1
ata0: [ITHREAD]
pci0: <multimedia> at device 20.2 (no driver attached)
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib4: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pci4: <ACPI PCI bus> on pcib4
em1: <Intel(R) PRO/1000 Network Connection 6.9.5> port 0xbf00-0xbf3f mem 0xfdac0000-0xfdadffff,0xfdaa0000-0xfdabffff irq 21 at device 7.0 on pci4
em1: [FILTER]
em1: Ethernet address: 00:0e:0c:34:17:46
pci4: <serial bus, FireWire> at device 14.0 (no driver attached)
ohci4: <OHCI (generic) USB controller> mem 0xfe028000-0xfe028fff irq 18 at device 20.5 on pci0
ohci4: [GIANT-LOCKED]
ohci4: [ITHREAD]
usb6: OHCI version 1.0, legacy support
usb6: SMM does not respond, resetting
usb6: <OHCI (generic) USB controller> on ohci4
usb6: USB revision 1.0
uhub6: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb6
uhub6: 2 ports with 2 removable, self powered
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FILTER]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio0: [FILTER]
ppc0: <Parallel port> port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: <Parallel port bus> on ppc0
ppbus0: [ITHREAD]
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ppc0: [GIANT-LOCKED]
ppc0: [ITHREAD]
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]
orm0: <ISA Option ROMs> at iomem 0xd0000-0xd0fff,0xd1000-0xd1fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 1.000 msec
ad0: 190781MB <SAMSUNG SP2014N VC100-30> at ata0-master UDMA133
ad4: 305245MB <Seagate ST3320620NS 3.AEK> at ata2-master SATA300
ad8: 305245MB <Seagate ST3320620NS 3.AEG> at ata4-master SATA300
acd0: DVDROM <HL-DT-STDVD-ROM GDRH20N/0L02> at ata5-master SATA150
SMP: AP CPU #1 Launched!
GEOM_MIRROR: Device mirror/gmir0s1 launched (2/2).
WARNING: Expected rawoffset 0, found 63
Trying to mount root from ufs:/dev/mirror/gmir0s1a
WARNING: ZFS is considered to be an experimental feature in FreeBSD.
ZFS filesystem version 6
ZFS storage pool version 6
--- dmesg.boot ends here ---

--- kernel config ---

cpu		HAMMER
ident		XXX

# To statically compile in device wiring instead of /boot/device.hints
#hints		"GENERIC.hints"		# Default places to look for devices.

#makeoptions	DEBUG=-g		# Build kernel with gdb(1) debug symbols

options 	SCHED_ULE		# ULE scheduler
options 	PREEMPTION		# Enable kernel thread preemption
options 	INET			# InterNETworking
options 	INET6			# IPv6 communications protocols
options 	SCTP			# Stream Control Transmission Protocol
options 	FFS			# Berkeley Fast Filesystem
options 	SOFTUPDATES		# Enable FFS soft updates support
options 	UFS_ACL			# Support for access control lists
options 	UFS_DIRHASH		# Improve performance on big directories
options 	UFS_GJOURNAL		# Enable gjournal-based UFS journaling
options 	CD9660			# ISO 9660 Filesystem
options 	PROCFS			# Process filesystem (requires PSEUDOFS)
options 	PSEUDOFS		# Pseudo-filesystem framework
options 	GEOM_PART_GPT		# GUID Partition Tables.
options 	GEOM_LABEL		# Provides labelization
options 	COMPAT_43TTY		# BSD 4.3 TTY compat [KEEP THIS!]
options 	COMPAT_IA32		# Compatible with i386 binaries
options 	COMPAT_FREEBSD4		# Compatible with FreeBSD4
options 	COMPAT_FREEBSD5		# Compatible with FreeBSD5
options 	COMPAT_FREEBSD6		# Compatible with FreeBSD6
options 	COMPAT_FREEBSD7		# Compatible with FreeBSD7
options 	SCSI_DELAY=5000		# Delay (in ms) before probing SCSI
options 	KTRACE			# ktrace(1) support
options 	STACK			# stack(9) support
options 	SYSVSHM			# SYSV-style shared memory
options 	SYSVMSG			# SYSV-style message queues
options 	SYSVSEM			# SYSV-style semaphores
options 	_KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
options 	KBD_INSTALL_CDEV	# install a CDEV entry in /dev
options 	STOP_NMI		# Stop CPUS using NMI instead of IPI
options 	AUDIT			# Security event auditing
options 	HWPMC_HOOKS		# Necessary kernel hooks for hwpmc(4)

## Debugging for use in -current
#options 	KDB			# Enable kernel debugger support.
#options 	DDB			# Support DDB.
#options 	GDB			# Support remote GDB.
#options 	INVARIANTS		# Enable calls of extra sanity checking
#options 	INVARIANT_SUPPORT	# Extra sanity checks of internal structures, required by INVARIANTS
#options 	WITNESS			# Enable checks to detect deadlocks and cycles
#options 	WITNESS_SKIPSPIN	# Don't run witness on spinlocks for speed

options     DEVICE_POLLING
options     NETGRAPH
options     NETGRAPH_ETHER
options     NETGRAPH_SOCKET
options     NETGRAPH_PPP
options     NETGRAPH_PPPOE
options     NETGRAPH_IFACE
options     NETGRAPH_BPF
options     NETGRAPH_TCPMSS
options     NETGRAPH_VJC

device      pf
device      pflog
device      pfsync

options     ALTQ
options     ALTQ_CBQ
options     ALTQ_RED
options     ALTQ_RIO
options     ALTQ_HFSC
options     ALTQ_CDNR
options     ALTQ_PRIQ
#options    ALTQ_NOPCC
##options    ALTQ_DEBUG
#
#device      drm

options         MSGBUF_SIZE=40960
options         SC_HISTORY_SIZE=1000     # number of history buffer lines
options         PANIC_REBOOT_WAIT_TIME=10000
options         GEOM_MIRROR

# Make an SMP-capable kernel by default
options 	SMP			# Symmetric MultiProcessor Kernel

# CPU frequency control
device		cpufreq

# Bus support.
device		acpi
device		pci

# Floppy drives
device		fdc

# ATA and ATAPI devices
device		ata
device		atadisk		# ATA disk drives
device		ataraid		# ATA RAID drives
device		atapicd		# ATAPI CDROM drives
device		atapifd		# ATAPI floppy drives
device		atapist		# ATAPI tape drives
options 	ATA_STATIC_ID	# Static device numbering

# SCSI peripherals
device		scbus		# SCSI bus (required for SCSI)
device		ch		# SCSI media changers
device		da		# Direct Access (disks)
device		sa		# Sequential Access (tape etc)
device		cd		# CD
device		pass		# Passthrough device (direct SCSI access)
device		ses		# SCSI Environmental Services (and SAF-TE)


# atkbdc0 controls both the keyboard and the PS/2 mouse
device		atkbdc		# AT keyboard controller
device		atkbd		# AT keyboard
device		psm		# PS/2 mouse

device		kbdmux		# keyboard multiplexer

device		vga		# VGA video card driver

device		splash		# Splash screen and screen saver support

# syscons is the default console driver, resembling an SCO console
device		sc

device		agp		# support several AGP chipsets

# Serial (COM) ports
device		sio		# 8250, 16[45]50 based serial ports
revice		uart		# Generic UART driver

# Parallel port
device		ppc
device		ppbus		# Parallel port bus (required)
device		lpt		# Printer
#device		plip		# TCP/IP over parallel
device		ppi		# Parallel port interface device
#device		vpo		# Requires scbus and da

# If you've got a "dumb" serial or parallel PCI card that is
# supported by the puc(4) glue driver, uncomment the following
# line to enable it (connects to sio, uart and/or ppc drivers):
#device		puc

# PCI Ethernet NICs.
device		em		# Intel PRO/1000 adapter Gigabit Ethernet Card

# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device		miibus		# MII bus support
device		re		# RealTek 8139C+/8169/8169S/8110S
device		rl		# RealTek 8129/8139

# Pseudo devices.
device		loop		# Network loopback
device		random		# Entropy device
device		ether		# Ethernet support
device		sl		# Kernel SLIP
device		ppp		# Kernel PPP
device		tun		# Packet tunnel.
device		pty		# Pseudo-ttys (telnet etc)
device		md		# Memory "disks"
device		gif		# IPv6 and IPv4 tunneling
device		faith		# IPv6-to-IPv4 relaying (translation)
device		firmware	# firmware assist module

# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
# Note that 'bpf' is required for DHCP.
device		bpf		# Berkeley packet filter

# USB support
device		uhci		# UHCI PCI->USB interface
device		ohci		# OHCI PCI->USB interface
device		ehci		# EHCI PCI->USB interface (USB 2.0)
device		usb		# USB Bus (required)
#device		udbp		# USB Double Bulk Pipe devices
device		ugen		# Generic
device		uhid		# "Human Interface Devices"
device		ukbd		# Keyboard
device		ulpt		# Printer
device		umass		# Disks/Mass storage - Requires scbus and da
device		ums		# Mouse
#device		uscanner	# Scanners

--- kernel config ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From pschmehl_lists at tx.rr.com  Tue Jul 15 16:27:03 2008
From: pschmehl_lists at tx.rr.com (Paul Schmehl)
Date: Tue Jul 15 16:27:14 2008
Subject: Crash when booting with umass device connected
In-Reply-To: <3a142e750807150223w6f264048wd9e13ae8846b593c@mail.gmail.com>
References: <3632806C83D31F1A23DE0F0A@utd65257.utdallas.edu>
	<3a142e750807150219j5a619135x19edba16e6590c21@mail.gmail.com>
	<3a142e750807150223w6f264048wd9e13ae8846b593c@mail.gmail.com>
Message-ID: <91DD32EA4C3672A46D423E44@utd65257.utdallas.edu>

--On Tuesday, July 15, 2008 11:23:09 +0200 "Paul B. Mahol" <onemda@gmail.com> 
wrote:
>
> Look in Developers handbook for more info
> /usr/share/doc/en/books/developers-handbook/index.html
>
> I think that textdumps are MFCed to STABLE.
> Textdumps provide easy way for gathering backtraces.

The problem is, I'm not getting dump files.  (And dumpdev is set to AUTO - the 
default.)  Savecore runs, but there's nothing to put in /var/crash.

-- 
Paul Schmehl
As if it wasn't already obvious,
my opinions are my own and not
those of my employer.

From onemda at gmail.com  Wed Jul 16 08:58:54 2008
From: onemda at gmail.com (Paul B. Mahol)
Date: Wed Jul 16 08:59:00 2008
Subject: Crash when booting with umass device connected
In-Reply-To: <91DD32EA4C3672A46D423E44@utd65257.utdallas.edu>
References: <3632806C83D31F1A23DE0F0A@utd65257.utdallas.edu>
	<3a142e750807150219j5a619135x19edba16e6590c21@mail.gmail.com>
	<3a142e750807150223w6f264048wd9e13ae8846b593c@mail.gmail.com>
	<91DD32EA4C3672A46D423E44@utd65257.utdallas.edu>
Message-ID: <3a142e750807160158x150f521fv696845d77d6e3c58@mail.gmail.com>

On 7/15/08, Paul Schmehl <pschmehl_lists@tx.rr.com> wrote:
> --On Tuesday, July 15, 2008 11:23:09 +0200 "Paul B. Mahol"
> <onemda@gmail.com>
> wrote:
>>
>> Look in Developers handbook for more info
>> /usr/share/doc/en/books/developers-handbook/index.html
>>
>> I think that textdumps are MFCed to STABLE.
>> Textdumps provide easy way for gathering backtraces.
>
> The problem is, I'm not getting dump files.  (And dumpdev is set to AUTO -
> the
> default.)  Savecore runs, but there's nothing to put in /var/crash.
>

First, do you see kdb prompt when system panics?
If not then you will need to recompile kernel with various debug stuff:
KDB, DDB, GDB, DEBUG=-g ...
Second do you have line with sw in /etc/fstab. If not,
it is possible to set dump device manually.
You should have following lines in /etc/rc.conf:

ddb_enable="YES"
ddb_config="/etc/ddb.conf"

But this one is required only if you want that textdumps are
taken automaticaly after system crash.
Exploring ddb(4) is also usefull.
From danfe at nsu.ru  Wed Jul 16 13:00:12 2008
From: danfe at nsu.ru (Alexey Dokuchaev)
Date: Wed Jul 16 13:00:28 2008
Subject: usb/117185: [umodem] [patch] Add support for UNION interface
	descriptor
Message-ID: <200807161300.m6GD0A8a042062@freefall.freebsd.org>

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

From: Alexey Dokuchaev <danfe@nsu.ru>
To: bug-followup@FreeBSD.org, eugen@grosbein.pp.ru
Cc: imp@bsdimp.com
Subject: Re: usb/117185: [umodem] [patch] Add support for UNION interface descriptor
Date: Wed, 16 Jul 2008 19:00:17 +0700

 --YiEDa0DAkWCtVeE4
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 Just confirmed to fix my Nokia E60 on 6-STABLE (had to change the patch
 slightly to fit 6.x codebase).
 
 P.S.  Warner, you mentioned that you were going to take a look at NetBSD
 (which this patch originates from) changes and merge the fix (usb/91546,
 obsolete now).  Could you possibly take a look now?  People say this
 code had been pretty stable for them for several months by now.
 Provided 6.x is also covered, I look forward for a merge.  Thanks.
 
 --YiEDa0DAkWCtVeE4
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename="umodem-nokia-releng6.patch"
 
 --- umodem.c.orig	2008-07-16 12:01:22.000000000 +0700
 +++ umodem.c	2008-07-16 12:43:32.000000000 +0700
 @@ -172,13 +172,14 @@
  	struct task		sc_task;
  };
  
 -Static void	*umodem_get_desc(usbd_device_handle dev, int type, int subtype);
 +Static void	*umodem_get_desc(usbd_device_handle dev, usb_descriptor_t *, int type, int subtype);
 +Static usbd_interface_handle umodem_get_interface(struct usb_attach_arg *uaa, int ifcno);
  Static usbd_status umodem_set_comm_feature(struct umodem_softc *sc,
  					   int feature, int state);
  Static usbd_status umodem_set_line_coding(struct umodem_softc *sc,
  					  usb_cdc_line_state_t *state);
  
 -Static void	umodem_get_caps(usbd_device_handle, int *, int *);
 +Static int	umodem_get_caps(struct usb_attach_arg *, int, int *, int *);
  
  Static void	umodem_get_status(void *, int portno, u_char *lsr, u_char *msr);
  Static void	umodem_set(void *, int, int, int);
 @@ -261,10 +262,7 @@
  	if (ret == UMATCH_NONE)
  		return (ret);
  
 -	umodem_get_caps(uaa->device, &cm, &acm);
 -	if (!(cm & USB_CDC_CM_DOES_CM) ||
 -	    !(cm & USB_CDC_CM_OVER_DATA) ||
 -	    !(acm & USB_CDC_ACM_HAS_LINE))
 +	if (umodem_get_caps(uaa, -1, &cm, &acm) == -1)
  		return (UMATCH_NONE);
  
  	return ret;
 @@ -276,7 +274,6 @@
  	usbd_device_handle dev = uaa->device;
  	usb_interface_descriptor_t *id;
  	usb_endpoint_descriptor_t *ed;
 -	usb_cdc_cm_descriptor_t *cmd;
  	char *devinfo = NULL;
  	const char *devname;
  	usbd_status err;
 @@ -304,15 +301,14 @@
  	  id->bInterfaceClass, id->bInterfaceSubClass);
  	sc->sc_ctl_iface_no = id->bInterfaceNumber;
  
 -	umodem_get_caps(dev, &sc->sc_cm_cap, &sc->sc_acm_cap);
 -
  	/* Get the data interface no. */
 -	cmd = umodem_get_desc(dev, UDESC_CS_INTERFACE, UDESCSUB_CDC_CM);
 -	if (cmd == NULL) {
 -		printf("%s: no CM descriptor\n", devname);
 + 	sc->sc_data_iface_no = data_ifcno =
 + 	    umodem_get_caps(uaa, sc->sc_ctl_iface_no, &sc->sc_cm_cap, &sc->sc_acm_cap);
 + 
 + 	if (data_ifcno == -1) {
 +		printf("%s: no pointer to data interface\n", devname);
  		goto bad;
  	}
 -	sc->sc_data_iface_no = data_ifcno = cmd->bDataInterface;
  
  	printf("%s: data interface %d, has %sCM over data, has %sbreak\n",
  	       devname, data_ifcno,
 @@ -550,27 +546,50 @@
  	ucom_status_change(&sc->sc_ucom);
  }
  
 -void
 -umodem_get_caps(usbd_device_handle dev, int *cm, int *acm)
 +Static int
 +umodem_get_caps(struct usb_attach_arg *uaa, int ctl_iface_no, int *cm, int *acm)
  {
  	usb_cdc_cm_descriptor_t *cmd;
  	usb_cdc_acm_descriptor_t *cad;
 +	usb_cdc_union_descriptor_t *cud;
 +	usbd_device_handle dev = uaa->device;
 +	usbd_interface_handle iface;
 +	int iface_no = 0;
  
  	*cm = *acm = 0;
  
 -	cmd = umodem_get_desc(dev, UDESC_CS_INTERFACE, UDESCSUB_CDC_CM);
 +	cmd = umodem_get_desc(dev, NULL, UDESC_CS_INTERFACE, UDESCSUB_CDC_CM);
  	if (cmd == NULL) {
  		DPRINTF(("umodem_get_desc: no CM desc\n"));
 -		return;
 +	} else {
 +		*cm = cmd->bmCapabilities;
  	}
 -	*cm = cmd->bmCapabilities;
  
 -	cad = umodem_get_desc(dev, UDESC_CS_INTERFACE, UDESCSUB_CDC_ACM);
 +	cad = umodem_get_desc(dev, NULL, UDESC_CS_INTERFACE, UDESCSUB_CDC_ACM);
  	if (cad == NULL) {
  		DPRINTF(("umodem_get_desc: no ACM desc\n"));
 -		return;
 +	} else {
 +		*acm = cad->bmCapabilities;
 +	}
 +	
 +	cud = NULL;
 +	while ((cud = umodem_get_desc(dev, (usb_descriptor_t *)cud,
 +			UDESC_CS_INTERFACE, UDESCSUB_CDC_UNION)))
 +	{
 +		iface_no = cud->bSlaveInterface[0];
 +		if (ctl_iface_no == -1)
 +			break;
 +
 +		iface = umodem_get_interface(uaa,iface_no);
 +		if (ctl_iface_no == cud->bMasterInterface &&
 +		    usbd_get_interface_descriptor(iface)->bNumEndpoints >= 2)
 +			break;
  	}
 -	*acm = cad->bmCapabilities;
 +	if (cud == NULL) {
 +		DPRINTF(("umodem_get_caps: no UNION desc\n"));
 +	}
 +	
 +	return cmd ? cmd->bDataInterface : cud ? iface_no : -1;
  }
  
  void
 @@ -586,6 +605,23 @@
  		*msr = sc->sc_msr;
  }
  
 +Static usbd_interface_handle
 +umodem_get_interface(struct usb_attach_arg *uaa, int ifcno)
 +{
 +	int i;
 +	usb_interface_descriptor_t *id;
 +
 +	for (i = 0; i < uaa->nifaces; i++) {
 +		if (uaa->ifaces[i] != NULL) {
 +			id = usbd_get_interface_descriptor(uaa->ifaces[i]);
 +			if (id != NULL && id->bInterfaceNumber == ifcno) {
 +				return uaa->ifaces[i];
 +			}
 +		}
 +	}
 +	return NULL;
 +}
 +
  int
  umodem_param(void *addr, int portno, struct termios *t)
  {
 @@ -776,14 +812,17 @@
  	return (USBD_NORMAL_COMPLETION);
  }
  
 -void *
 -umodem_get_desc(usbd_device_handle dev, int type, int subtype)
 +static void *
 +umodem_get_desc(usbd_device_handle dev, usb_descriptor_t *restart, int type, int subtype)
  {
  	usb_descriptor_t *desc;
  	usb_config_descriptor_t *cd = usbd_get_config_descriptor(dev);
          uByte *p = (uByte *)cd;
          uByte *end = p + UGETW(cd->wTotalLength);
  
 +	if (restart)
 +		p = (uByte *)(restart) + restart->bLength;
 +
  	while (p < end) {
  		desc = (usb_descriptor_t *)p;
  		if (desc->bDescriptorType == type &&
 
 --YiEDa0DAkWCtVeE4--
From hselasky at c2i.net  Wed Jul 16 14:12:50 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Jul 16 14:12:57 2008
Subject: usb/117185: [umodem] [patch] Add support for UNION interface
	descriptor
In-Reply-To: <200807161300.m6GD0A8a042062@freefall.freebsd.org>
References: <200807161300.m6GD0A8a042062@freefall.freebsd.org>
Message-ID: <200807161614.26974.hselasky@c2i.net>

On Wednesday 16 July 2008, Alexey Dokuchaev wrote:
> ?+??????if (restart)
> ?+??????????????p = (uByte *)(restart) + restart->bLength;

Maybe you can add some extra range checks here. Remember the descriptors come 
from the device itself, and might be corrupt.

--HPS
From pschmehl_lists at tx.rr.com  Wed Jul 16 20:49:47 2008
From: pschmehl_lists at tx.rr.com (Paul Schmehl)
Date: Wed Jul 16 20:49:54 2008
Subject: Crash when booting with umass device connected
In-Reply-To: <3a142e750807160158x150f521fv696845d77d6e3c58@mail.gmail.com>
References: <3632806C83D31F1A23DE0F0A@utd65257.utdallas.edu>
	<3a142e750807150219j5a619135x19edba16e6590c21@mail.gmail.com>
	<3a142e750807150223w6f264048wd9e13ae8846b593c@mail.gmail.com>
	<91DD32EA4C3672A46D423E44@utd65257.utdallas.edu>
	<3a142e750807160158x150f521fv696845d77d6e3c58@mail.gmail.com>
Message-ID: <32370E1FFF045EDCAB01F90D@utd65257.utdallas.edu>

--On Wednesday, July 16, 2008 10:58:53 +0200 "Paul B. Mahol" <onemda@gmail.com> 
wrote:

> On 7/15/08, Paul Schmehl <pschmehl_lists@tx.rr.com> wrote:
>> --On Tuesday, July 15, 2008 11:23:09 +0200 "Paul B. Mahol"
>> <onemda@gmail.com>
>> wrote:
>>>
>>> Look in Developers handbook for more info
>>> /usr/share/doc/en/books/developers-handbook/index.html
>>>
>>> I think that textdumps are MFCed to STABLE.
>>> Textdumps provide easy way for gathering backtraces.
>>
>> The problem is, I'm not getting dump files.  (And dumpdev is set to AUTO -
>> the
>> default.)  Savecore runs, but there's nothing to put in /var/crash.
>>
>
> First, do you see kdb prompt when system panics?

I'm sorry.  I don't know what that means.

> If not then you will need to recompile kernel with various debug stuff:
> KDB, DDB, GDB, DEBUG=-g ...

Well, there's a problem with that.  I added option USB_DEBUG and recompiled the 
kernel, and now it doesn't crash.  ???  I left the umass device plugged in and 
rebooted, so that I could show a peer the crash, and it zipped right on through 
without a hiccup.

> Second do you have line with sw in /etc/fstab.

Yes.

pauls@utd65257# grep sw /etc/fstab
/dev/ad8s1b             none            swap    sw              0       0

> If not,
> it is possible to set dump device manually.
> You should have following lines in /etc/rc.conf:
>
> ddb_enable="YES"
> ddb_config="/etc/ddb.conf"
>
> But this one is required only if you want that textdumps are
> taken automaticaly after system crash.
> Exploring ddb(4) is also usefull.

Thanks for the tips.  I'll read up on those.

-- 
Paul Schmehl
As if it wasn't already obvious,
my opinions are my own and not
those of my employer.

From danfe at nsu.ru  Thu Jul 17 06:10:05 2008
From: danfe at nsu.ru (Alexey Dokuchaev)
Date: Thu Jul 17 06:10:12 2008
Subject: usb/117185: [umodem] [patch] Add support for UNION interface
	descriptor
Message-ID: <200807170610.m6H6A3s5035951@freefall.freebsd.org>

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

From: Alexey Dokuchaev <danfe@nsu.ru>
To: bug-followup@FreeBSD.org, eugen@grosbein.pp.ru
Cc: imp@bsdimp.com
Subject: Re: usb/117185: [umodem] [patch] Add support for UNION interface descriptor
Date: Thu, 17 Jul 2008 13:04:27 +0700

 Apparently, GNATS does not handle attached files correctly (or maybe I
 have to name them differently), anyways.  Here're direct links for both
 latest patch by Jeremie and RELENG_6 backport:
 
 	http://freebsd.nsu.ru/patches/umodem-nokia.diff
 	http://freebsd.nsu.ru/patches/umodem-nokia-releng6.diff
 
 Hans Petter Selasky <hselasky(at)c2i.net> raised a point about this part
 of the patch:
 
 >  +      if (restart)
 >  +              p = (uByte *)(restart) + restart->bLength;
 
 that maybe we "can add some extra range checks here.  Remember the
 descriptors come from the device itself, and might be corrupt."
From Luoqi.Chen at brion.com  Thu Jul 17 10:51:49 2008
From: Luoqi.Chen at brion.com (Luoqi Chen)
Date: Thu Jul 17 10:52:18 2008
Subject: Maintainer of usb code
Message-ID: <0707E37B6D2E244C85660487B602C92217ABC04434@ex02.briontech.com>

Hello,

Do we have an official maintainer of the usb code? I came across some quite trivial
errors while debugging another problem (which turned out not to be usb related),
please see the diff below. I'm not terribly familiar with the usb code, so I'd like
to seek someone to review this change,

Index: ohci.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/usb/ohci.c,v
retrieving revision 1.170
diff -u -r1.170 ohci.c
--- ohci.c      20 Jun 2007 05:10:52 -0000      1.170
+++ ohci.c      17 Jul 2008 10:07:07 -0000
@@ -815,20 +815,19 @@
 ohci_controller_init(ohci_softc_t *sc)
 {
        int i;
-       u_int32_t s, ctl, ival, hcr, fm, per, desca;
+       u_int32_t ctl, ival, hcr, fm, per, desca;

        /* Determine in what context we are running. */
        ctl = OREAD4(sc, OHCI_CONTROL);
        if (ctl & OHCI_IR) {
                /* SMM active, request change */
                DPRINTF(("ohci_init: SMM active, request owner change\n"));
-               s = OREAD4(sc, OHCI_COMMAND_STATUS);
-               OWRITE4(sc, OHCI_COMMAND_STATUS, s | OHCI_OCR);
+               OWRITE4(sc, OHCI_COMMAND_STATUS, OHCI_OCR);
                for (i = 0; i < 100 && (ctl & OHCI_IR); i++) {
                        usb_delay_ms(&sc->sc_bus, 1);
                        ctl = OREAD4(sc, OHCI_CONTROL);
                }
-               if ((ctl & OHCI_IR) == 0) {
+               if (ctl & OHCI_IR) {
                        printf("%s: SMM does not respond, resetting\n",
                               device_get_nameunit(sc->sc_bus.bdev));
                        OWRITE4(sc, OHCI_CONTROL, OHCI_HCFS_RESET);

Thanks
-lq
From hselasky at c2i.net  Thu Jul 17 12:19:17 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Jul 17 12:19:24 2008
Subject: Maintainer of usb code
In-Reply-To: <0707E37B6D2E244C85660487B602C92217ABC04434@ex02.briontech.com>
References: <0707E37B6D2E244C85660487B602C92217ABC04434@ex02.briontech.com>
Message-ID: <200807171420.52900.hselasky@c2i.net>

Hi Luoqi,

From what version of FreeBSD did you fetch your ohci.c ?

--HPS

On Thursday 17 July 2008, Luoqi Chen wrote:
> Hello,
>
> Do we have an official maintainer of the usb code? I came across some quite
> trivial errors while debugging another problem (which turned out not to be
> usb related), please see the diff below. I'm not terribly familiar with the
> usb code, so I'd like to seek someone to review this change,
>
> Index: ohci.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/dev/usb/ohci.c,v
> retrieving revision 1.170
> diff -u -r1.170 ohci.c
> --- ohci.c      20 Jun 2007 05:10:52 -0000      1.170
> +++ ohci.c      17 Jul 2008 10:07:07 -0000
> @@ -815,20 +815,19 @@
>  ohci_controller_init(ohci_softc_t *sc)
>  {
>         int i;
> -       u_int32_t s, ctl, ival, hcr, fm, per, desca;
> +       u_int32_t ctl, ival, hcr, fm, per, desca;
>
>         /* Determine in what context we are running. */
>         ctl = OREAD4(sc, OHCI_CONTROL);
>         if (ctl & OHCI_IR) {
>                 /* SMM active, request change */
>                 DPRINTF(("ohci_init: SMM active, request owner change\n"));
> -               s = OREAD4(sc, OHCI_COMMAND_STATUS);
> -               OWRITE4(sc, OHCI_COMMAND_STATUS, s | OHCI_OCR);
> +               OWRITE4(sc, OHCI_COMMAND_STATUS, OHCI_OCR);
>                 for (i = 0; i < 100 && (ctl & OHCI_IR); i++) {
>                         usb_delay_ms(&sc->sc_bus, 1);
>                         ctl = OREAD4(sc, OHCI_CONTROL);
>                 }
> -               if ((ctl & OHCI_IR) == 0) {
> +               if (ctl & OHCI_IR) {
>                         printf("%s: SMM does not respond, resetting\n",
>                                device_get_nameunit(sc->sc_bus.bdev));
>                         OWRITE4(sc, OHCI_CONTROL, OHCI_HCFS_RESET);
>
> Thanks
> -lq
From hselasky at c2i.net  Thu Jul 17 17:13:55 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Thu Jul 17 17:14:02 2008
Subject: Maintainer of usb code
In-Reply-To: <0707E37B6D2E244C85660487B602C92217ABC04449@ex02.briontech.com>
References: <0707E37B6D2E244C85660487B602C92217ABC04434@ex02.briontech.com>
	<200807171420.52900.hselasky@c2i.net>
	<0707E37B6D2E244C85660487B602C92217ABC04449@ex02.briontech.com>
Message-ID: <200807171915.31598.hselasky@c2i.net>

I think your patch is Ok. It should look similar to this:

        /* Determine in what context we are running. */
        ctl = OREAD4(sc, OHCI_CONTROL);
        if (ctl & OHCI_IR) {
                /* SMM active, request change */
                DPRINTF(0, "SMM active, request owner change\n");
                s = OREAD4(sc, OHCI_COMMAND_STATUS);
                OWRITE4(sc, OHCI_COMMAND_STATUS, s | OHCI_OCR);
                for (i = 0; (i < 100) && (ctl & OHCI_IR); i++) {
                        DELAY(1000 * 1);
                        ctl = OREAD4(sc, OHCI_CONTROL);
                }
                if ((ctl & OHCI_IR) == 0) {
                        device_printf(sc->sc_bus.bdev, "SMM does not respond, 
resetting\n");
                        OWRITE4(sc, OHCI_CONTROL, OHCI_HCFS_RESET);
                        goto reset;
                }

--HPS

On Thursday 17 July 2008, Luoqi Chen wrote:
> Hans,
>
> It probably doesn't matter, this part of code hasn't been touched
> for years. I did a quick check on the latest svn version, it looked
> the same.
>
> -lq
>
> > -----Original Message-----
> > From: Hans Petter Selasky [mailto:hselasky@c2i.net]
> > Sent: Thursday, July 17, 2008 5:21 AM
> > To: freebsd-usb@freebsd.org
> > Cc: Luoqi Chen
> > Subject: Re: Maintainer of usb code
> >
> > Hi Luoqi,
> >
> > From what version of FreeBSD did you fetch your ohci.c ?
> >
> > --HPS
> >
> > On Thursday 17 July 2008, Luoqi Chen wrote:
> > > Hello,
> > >
> > > Do we have an official maintainer of the usb code? I came
> >
> > across some quite
> >
> > > trivial errors while debugging another problem (which
> >
> > turned out not to be
> >
> > > usb related), please see the diff below. I'm not terribly
> >
> > familiar with the
> >
> > > usb code, so I'd like to seek someone to review this change,
> > >
> > > Index: ohci.c
> > > ===================================================================
> > > RCS file: /home/ncvs/src/sys/dev/usb/ohci.c,v
> > > retrieving revision 1.170
> > > diff -u -r1.170 ohci.c
> > > --- ohci.c      20 Jun 2007 05:10:52 -0000      1.170
> > > +++ ohci.c      17 Jul 2008 10:07:07 -0000
> > > @@ -815,20 +815,19 @@
> > >  ohci_controller_init(ohci_softc_t *sc)
> > >  {
> > >         int i;
> > > -       u_int32_t s, ctl, ival, hcr, fm, per, desca;
> > > +       u_int32_t ctl, ival, hcr, fm, per, desca;
> > >
> > >         /* Determine in what context we are running. */
> > >         ctl = OREAD4(sc, OHCI_CONTROL);
> > >         if (ctl & OHCI_IR) {
> > >                 /* SMM active, request change */
> > >                 DPRINTF(("ohci_init: SMM active, request
> >
> > owner change\n"));
> >
> > > -               s = OREAD4(sc, OHCI_COMMAND_STATUS);
> > > -               OWRITE4(sc, OHCI_COMMAND_STATUS, s | OHCI_OCR);
> > > +               OWRITE4(sc, OHCI_COMMAND_STATUS, OHCI_OCR);
> > >                 for (i = 0; i < 100 && (ctl & OHCI_IR); i++) {
> > >                         usb_delay_ms(&sc->sc_bus, 1);
> > >                         ctl = OREAD4(sc, OHCI_CONTROL);
> > >                 }
> > > -               if ((ctl & OHCI_IR) == 0) {
> > > +               if (ctl & OHCI_IR) {
> > >                         printf("%s: SMM does not respond,
> >
> > resetting\n",
> >
> > device_get_nameunit(sc->sc_bus.bdev));
> >
> > >                         OWRITE4(sc, OHCI_CONTROL, OHCI_HCFS_RESET);
> > >
> > > Thanks
> > > -lq


From Luoqi.Chen at brion.com  Thu Jul 17 17:31:49 2008
From: Luoqi.Chen at brion.com (Luoqi Chen)
Date: Thu Jul 17 17:31:58 2008
Subject: Maintainer of usb code
In-Reply-To: <200807171420.52900.hselasky@c2i.net>
References: <0707E37B6D2E244C85660487B602C92217ABC04434@ex02.briontech.com>
	<200807171420.52900.hselasky@c2i.net>
Message-ID: <0707E37B6D2E244C85660487B602C92217ABC04449@ex02.briontech.com>

Hans,

It probably doesn't matter, this part of code hasn't been touched
for years. I did a quick check on the latest svn version, it looked
the same.

-lq

> -----Original Message-----
> From: Hans Petter Selasky [mailto:hselasky@c2i.net]
> Sent: Thursday, July 17, 2008 5:21 AM
> To: freebsd-usb@freebsd.org
> Cc: Luoqi Chen
> Subject: Re: Maintainer of usb code
>
> Hi Luoqi,
>
> From what version of FreeBSD did you fetch your ohci.c ?
>
> --HPS
>
> On Thursday 17 July 2008, Luoqi Chen wrote:
> > Hello,
> >
> > Do we have an official maintainer of the usb code? I came
> across some quite
> > trivial errors while debugging another problem (which
> turned out not to be
> > usb related), please see the diff below. I'm not terribly
> familiar with the
> > usb code, so I'd like to seek someone to review this change,
> >
> > Index: ohci.c
> > ===================================================================
> > RCS file: /home/ncvs/src/sys/dev/usb/ohci.c,v
> > retrieving revision 1.170
> > diff -u -r1.170 ohci.c
> > --- ohci.c      20 Jun 2007 05:10:52 -0000      1.170
> > +++ ohci.c      17 Jul 2008 10:07:07 -0000
> > @@ -815,20 +815,19 @@
> >  ohci_controller_init(ohci_softc_t *sc)
> >  {
> >         int i;
> > -       u_int32_t s, ctl, ival, hcr, fm, per, desca;
> > +       u_int32_t ctl, ival, hcr, fm, per, desca;
> >
> >         /* Determine in what context we are running. */
> >         ctl = OREAD4(sc, OHCI_CONTROL);
> >         if (ctl & OHCI_IR) {
> >                 /* SMM active, request change */
> >                 DPRINTF(("ohci_init: SMM active, request
> owner change\n"));
> > -               s = OREAD4(sc, OHCI_COMMAND_STATUS);
> > -               OWRITE4(sc, OHCI_COMMAND_STATUS, s | OHCI_OCR);
> > +               OWRITE4(sc, OHCI_COMMAND_STATUS, OHCI_OCR);
> >                 for (i = 0; i < 100 && (ctl & OHCI_IR); i++) {
> >                         usb_delay_ms(&sc->sc_bus, 1);
> >                         ctl = OREAD4(sc, OHCI_CONTROL);
> >                 }
> > -               if ((ctl & OHCI_IR) == 0) {
> > +               if (ctl & OHCI_IR) {
> >                         printf("%s: SMM does not respond,
> resetting\n",
> >
> device_get_nameunit(sc->sc_bus.bdev));
> >                         OWRITE4(sc, OHCI_CONTROL, OHCI_HCFS_RESET);
> >
> > Thanks
> > -lq
>
From markir at paradise.net.nz  Fri Jul 18 05:44:42 2008
From: markir at paradise.net.nz (Mark Kirkwood)
Date: Fri Jul 18 05:44:49 2008
Subject: usb/78984: [umass] [patch] Creative MUVO umass failure
In-Reply-To: <20080421.060554.1621851987.imp@bsdimp.com>
References: <200804211030.m3LAU3Uo091913@freefall.freebsd.org>
	<20080421.060554.1621851987.imp@bsdimp.com>
Message-ID: <488029EA.1010106@paradise.net.nz>

M. Warner Losh wrote:
> In message: <200804211030.m3LAU3Uo091913@freefall.freebsd.org>
>             Mark Kirkwood <markir@paradise.net.nz> writes:
> : The following reply was made to PR usb/78984; it has been noted by GNATS.
> : 
> : From: Mark Kirkwood <markir@paradise.net.nz>
> : To: bug-followup@FreeBSD.org, bofh@m-wesemeyer.de
> : Cc:  
> : Subject: Re: usb/78984: [umass] [patch] Creative MUVO umass failure
> : Date: Mon, 21 Apr 2008 22:11:17 +1200
> : 
> :  I ran into this with 7-STABLE and a 128MB creatiev muvo. This slightly 
> :  updated patch seems to fix.
> :  ================================================================================
> :  *** sys/dev/usb/umass.c.orig    Mon Apr 21 18:17:08 2008
> :  --- sys/dev/usb/umass.c Mon Apr 21 18:20:31 2008
> :  ***************
> :  *** 374,379 ****
> :  --- 374,383 ----
> :        UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
> :        FORCE_SHORT_INQUIRY | NO_START_STOP | IGNORE_RESIDUE
> :      },
> :  +   { USB_VENDOR_CREATIVE, USB_PRODUCT_CREATIVE_NOMAD, RID_WILDCARD,
> :  +     UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
> :  +     READ_CAPACITY_OFFBY1
> :  +   },
> :      { USB_VENDOR_DESKNOTE, USB_PRODUCT_DESKNOTE_UCR_61S2B, RID_WILDCARD,
> :        UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
> :        NO_QUIRKS
> :  ================================================================================
>
> Are all Creative nomad's off by one?  In linux, this quirk is used
> extremely rarely, and i don't think I see the nomad on the lists...
>
>
>   


Good point, the wildcard for all creative nomads is wrong (I've 
corrected the patch in the pr) - Interestingly I had the opportunity to 
try this device out in Linux the other day (Ubuntu 8.0.4) I got the 
error stack below...seems Linux needs the quirk for this guy as well!

-------------------------------------Ubuntu 
dmesg-------------------------------------------

[   11.975774] usb 2-1: new full speed USB device using uhci_hcd and 
address 2
[   11.996611] usb 2-1: configuration #1 chosen from 1 choice
[   12.199422] usbcore: registered new interface driver libusual
[   12.235825] Initializing USB Mass Storage driver...
[   12.237512] scsi2 : SCSI emulation for USB Mass Storage devices
[   12.239161] usbcore: registered new interface driver usb-storage
[   12.239171] USB Mass Storage support registered.
[   12.239333] usb-storage: device found at 2
[   12.239339] usb-storage: waiting for device to settle before scanning
[   14.930721] usb-storage: device scan complete
[   14.933726] scsi 2:0:0:0: Direct-Access     CREATIVE NOMAD_MUVO       
0001 PQ: 0 ANSI: 4
[   14.957715] sd 2:0:0:0: [sdb] 256001 512-byte hardware sectors (131 MB)
[   14.960641] sd 2:0:0:0: [sdb] Write Protect is off
[   14.960650] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 04
[   14.960656] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[   14.978623] sd 2:0:0:0: [sdb] 256001 512-byte hardware sectors (131 MB)
[   14.981610] sd 2:0:0:0: [sdb] Write Protect is off
[   14.981619] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 04
[   14.981625] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[   14.981635]  sdb: sdb1
[   14.988768] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[   14.988857] sd 2:0:0:0: Attached scsi generic sg2 type 0
[   15.401063] end_request: I/O error, dev sdb, sector 256000
[   15.401076] Buffer I/O error on device sdb, logical block 256000



From bugmaster at FreeBSD.org  Mon Jul 21 11:07:05 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Jul 21 11:09:06 2008
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200807211107.m6LB74jW032044@freefall.freebsd.org>

Current FreeBSD problem reports
Critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
f usb/84750    usb        [hang] 6-BETA2 reboot/shutdown with root_fs on externa
o usb/91629    usb        usbd_abort_pipe() may result in infinite loop

2 problems total.

Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o i386/46371   usb        USB controller cannot be initialized on IBM Netfinity 
o bin/57255    usb        usbd(8) and multi-function devices
o usb/63621    usb        [umass] [panic] USB MemoryStick Reader stalls/crashes 
o usb/67301    usb        [uftdi] [panic] RTS and system panic
o usb/69006    usb        [usbdevs] [patch] Apple Cinema Display hangs USB ports
o usb/71155    usb        [ulpt] misbehaving usb-printer hangs processes, causes
o usb/73307    usb        [panic] Kernel panics on USB disconnect
o usb/74771    usb        [umass] [hang] mounting write-protected umass device a
o usb/75705    usb        [umass] [panic] da0 attach / Optio S4 (with backtrace)
o usb/75797    usb        [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c
o usb/76395    usb        [uhci] USB printer does not work, usbdevs says "addr 0
o usb/77184    usb        [umass] [panic] kernel panic on USB device disconnect,
o usb/77294    usb        [ucom] [panic] ucom + ulpcom panic
o usb/79269    usb        [ohci] USB ohci da0 plug/unplug causes crashes and loc
o usb/79287    usb        [uhci] [hang] UHCI hang after interrupt transfer
o usb/79524    usb        [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa
a usb/79656    usb        [ehci] RHSC interrupts lost
o usb/79722    usb        [ehci] wrong alignments in ehci.h
o usb/80040    usb        [hang] Use of sound mixer causes system freeze with ua
o usb/80361    usb        [umass] [patch] mounting of Dell usb-stick fails
o usb/80829    usb        [modules] [panic] possible panic when loading USB-modu
o usb/80862    usb        [patch] USB locking issues: missing some Giant calls
o usb/82350    usb        [ucom] [panic] null pointer dereference in USB stack
o usb/82520    usb        [udbp] [reboot] Reboot when USL101 connected
s usb/82569    usb        [umass] [panic] USB mass storage plug/unplug causes sy
o usb/82660    usb        [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic
o usb/83504    usb        [kernel] [patch] SpeedTouch USB stop working on recent
o usb/83563    usb        [umass] [panic] Page Fault while detaching Mpman Usb d
f usb/83677    usb        [usb] [request] usb controller often not detected (Sun
o usb/83756    usb        [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe
o usb/83977    usb        [ucom] [panic] ucom1: open bulk out error (addr 2): IN
o usb/84326    usb        [umass] Panic trying to connect SCSI tape drive via US
s usb/84336    usb        [usb] [reboot] instant system reboot when unmounting a
o usb/86767    usb        [umass] [patch] bogus "slice starts beyond end of the 
o usb/88743    usb        [hang] [regression] USB makes kernel hang at boot (reg
s usb/89003    usb        [request] LaCie Firewire drive not properly supported 
o usb/89954    usb        [umass] [panic] USB Disk driver race condition?
o usb/90700    usb        [umass] [panic] Kernel panic on connect/mount/use umas
o usb/91238    usb        [umass] USB tape unit fails to write a second tape fil
o usb/91283    usb        [boot] [regression] booting very slow with usb devices
o usb/91538    usb        [ulpt] [patch] Unable to print to EPSON CX3500
o usb/91906    usb        [ehci] [hang] FreeBSD hangs while booting with USB leg
o usb/92052    usb        [ulpt] usbd causes defunct process with busy file-hand
o usb/92083    usb        [ural] [panic] panic using WPA on ural NIC in 6.0-RELE
o usb/92142    usb        [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb 
o usb/92171    usb        [panic] panic unplugging Vodafone Mobile Connect (UMTS
o usb/93155    usb        [ulpt] /dev/ulpt0: device busy, USB printer does not w
o usb/93408    usb        [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes 
o usb/93828    usb        [ohci] [panic] ohci causes panic on boot (HP Pavillion
o usb/94384    usb        [panic] kernel panic with usb2 hardware
o usb/94717    usb        [ulpt] Reading from /dev/ulpt can break work of a UHCI
o usb/94897    usb        [panic] Kernel Panic when cleanly unmounting USB disk
s usb/95348    usb        [keyboard] USB keyboard unplug causes noise on screen
o usb/95562    usb        [umass] Write Stress in USB Mass drive causes "vinvalb
s usb/95636    usb        [umass] [boot] 5 minute delay at boot when using VT620
s usb/96120    usb        [ums] [request] USB mouse not always detected
o usb/96224    usb        [usb] [msdosfs] mount_msdosfs cause page fault in sync
o usb/96457    usb        [umass] [panic] fatback on umass = reboot
s usb/97286    usb        [mouse] [request] MS Wireless Intellimouse Explorer 2.
o usb/99431    usb        [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar
o usb/101096   usb        [ural] [panic] USB WLAN occasionally causes kernel-pan
o usb/101448   usb        [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O
o usb/101752   usb        [umass] [panic] 6.1-RELEASE kernel panic on usb device
o usb/102066   usb        [ukbd] usb keyboard and multimedia keys don't work
f usb/102096   usb        [patch] usbd(8) does not handle multiple devices in on
o usb/103025   usb        [uhub] [panic] wrong detection of USB device for FreeB
o usb/104292   usb        [umass] [hang] system lockup on forced umount of usb-s
o usb/104830   usb        [umass] system crashes when copying data to umass devi
o usb/105186   usb        [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c
o usb/106615   usb        [uftdi] uftdi module does not automatically load with 
o usb/106648   usb        [umass] [hang] USB Floppy on D1950 10 min Hang on Inse
s usb/106832   usb        USB HP printer is not detected by kernel when ACPI ena
o usb/107248   usb        [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP
o usb/107446   usb        [umass] umass problems (usb and fw disks)
o usb/107827   usb        [ohci] [panic] ohci_add_done addr not found
o usb/107848   usb        [umass] [request] cannot access Samsung flash disk
o usb/107924   usb        [patch] usbd(8) does not call detach
o usb/108513   usb        [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr
o usb/109274   usb        [usb] MCP55 USB Controller fails to attach in AMD64 Cu
o usb/109397   usb        [panic] on boot from USB flash
o usb/110856   usb        [ugen] [patch] interrupt in msgs are truncated when bu
o usb/110988   usb        [umass] [patch] Handling of quirk IGNORE_RESIDUE is um
o usb/111753   usb        [uhid] [panic] Replicable system panic involving UHID 
s usb/112568   usb        [umass] [request] USB mode may wrong when mounting Pla
o usb/112631   usb        [panic] Problem with SONY DSC-S80 camera on umount
o usb/112640   usb        [usb] [hang] Kernel freezes when writing a file to an 
s usb/113629   usb        [ukbd] Dropped USB keyboard events on Dell Latitude D6
o usb/113672   usb        [ehci] [panic] Kernel panic with AEWIN CB6971
s usb/113977   usb        [request] Need a way to set mode of USB disk's write c
o usb/114310   usb        [libusb] [patch] [panic] USB hub attachment panics ker
o usb/114682   usb        [umass] generic USB media-card reader unusable
o kern/114780  usb        [uplcom] [panic] Panics while stress testing the uplco
o usb/115298   usb        [ulpt] [panic] Turning off USB printer panics kernel
o usb/116561   usb        [umodem] [panic] RELENG_6 umodem panic "trying to slee
o usb/116699   usb        [usbhid] USB HID devices do not initialize at system b
o usb/116947   usb        [ukbd] [patch] [regression] enable boot protocol on th
o usb/117200   usb        [ugen] ugen0 prints strange string on attach if detach
o usb/117313   usb        [umass] [panic] panic on usb camera insertion
o usb/117613   usb        [uhci] [irq] uhci interrupt storm & USB leaked memory 
o usb/117946   usb        [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE
o usb/117955   usb        [umass] [panic] inserting minolta dimage a2 crashes OS
o usb/118140   usb        [ucom] [patch] quick hack for ucom to get it behave wi
o usb/118141   usb        [ucom] usb serial and nokia phones ucomreadcb ucomread
o usb/118353   usb        [panic] [ppp] repeatable kernel panic during ppp(4) se
o usb/118480   usb        [umass] Timeout in USB mass storage freezes vfs layer 
o usb/119201   usb        [cam] [patch] Quirks for Olympus FE-210 camera, LG and
o usb/119481   usb        [hang] FreeBSD not responding after connecting USB-Mas
o usb/119509   usb        USB flaky on Dell Optiplex 755
o usb/119513   usb        [irq] inserting dlink dwl-g630 wireless card results i
o usb/119977   usb        [ums] Mouse does not work in a Cherry-USB keyboard/mou
o usb/120017   usb        [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk
o usb/120034   usb        [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 
o usb/120283   usb        [panic] Automation reboot with wireless keyboard & mou
o usb/120321   usb        [hang] System hangs when transferring data to WD MyBoo
o usb/120729   usb        [panic] fault while in kernel mode with connecting USB
o usb/120786   usb        Kernel panic when forced umount of a dettached USB Har
o usb/121232   usb        remove PCCARD rebooted system
o usb/121275   usb        [boot] FreeBSD fails to boot with usb legacy support e
o usb/121474   usb        [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard
o usb/121708   usb        [keyboard] nforce 650i mobo w/ usb keyboard infinite k
o usb/121734   usb        [ugen] ugen HP1022 printer device not working since up
o usb/121755   usb        [ohci] [patch] Fix panic after ohci/uhub cardbus devic
o usb/122483   usb        [panic] [ulpt] Repeatable panic in 7.0-STABLE
o usb/122539   usb        [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci
o usb/122905   usb        [ubsa] [patch] add Huawei E220 to ubsa
o kern/123510  usb        [ums] Mouse Wheel Fails to Work [regression]
o usb/123690   usb        Panic on USB device insertion when usb loaded as a mod
o usb/123714   usb        Panic when hald-storage-probe runs with umass device i
o usb/124708   usb        [panic] Kernel panic on USB KVM reattach
o usb/124758   usb        rum panics SMP kernel
o kern/124777  usb        [ucom] USB cua devices don't revert to tty devices whe
o usb/124980   usb        [panic] kernel panic on detaching unmounted umass devi
o usb/125088   usb        Touchpad not detected on Adesso AKB-430UG USB kbd/pad 
o usb/125450   usb        [panic] Removing USB flash card while being accessed c
o usb/125631   usb        [usb][ums] kernel panic during bootup while 'Logitech 

135 problems total.

Non-critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o conf/30929   usb        [usb] [patch] use usbd to initialize USB ADSL modem
o usb/40948    usb        [umass] [request] USB HP CDW8200 does not work
s usb/51958    usb        [urio] [patch] update for urio driver
s usb/52026    usb        [usb] [request] umass driver support for InSystem ISD2
o usb/59698    usb        [keyboard] [patch] Rework of ukbd HID to AT code trans
s usb/62257    usb        [umass] [request] card reader UCR-61S2B is only half-s
o usb/66547    usb        [ucom] Palm Tungsten T USB does not initialize correct
o usb/68232    usb        [ugen] [patch] ugen(4) isochronous handling correction
o usb/70523    usb        [umct] [patch] umct sending/receiving wrong characters
o usb/71280    usb        [aue] aue0 device (linksys usb100tx) doesn't work in 1
o usb/71416    usb        [ugen] Cryptoflex e-gate USB token (ugen0) detach is n
o usb/71417    usb        [ugen] Cryptoflex e-gate USB token (ugen0) communicati
o usb/71455    usb        [umass] Slow USB umass performance of 5.3
s usb/72733    usb        [ucom] [request] Kyocera 7135 Palm OS connection probl
o usb/74211    usb        [umass] USB flash drive causes CAM status 0x4 on 4.10R
a usb/74453    usb        [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL
o usb/75764    usb        [umass] [patch] "umass0: Phase Error" - no device for 
o usb/75800    usb        [ucom] ucom1: init failed STALLED error in time of syn
s usb/75928    usb        [umass] [request] Cytronix SmartMedia card (SMC) reade
o usb/76461    usb        [umass] disklabel of umass(4)-CAM(4)-da(4) not used by
o usb/76653    usb        [umass] [patch] Problem with Asahi Optical usb device 
o usb/76732    usb        Mouse problems with USB KVM Switch
o usb/78984    usb        [umass] [patch] Creative MUVO umass failure
o usb/79723    usb        [usb] [request] prepare for high speed isochronous tra
o usb/80774    usb        [patch] have "usbd_find_desc" in line with the other "
s usb/80776    usb        [udav] [request] UDAV device driver shouldn't use usb_
s usb/80777    usb        [request] usb_rem_task() should wait for callback to c
o usb/80854    usb        [patch] [request] suggestion for new iface-no-probe me
o usb/80935    usb        [uvisor] [patch] uvisor.c is not work with CLIE TH55.
o usb/81621    usb        [ehci] [hang] external hd hangs under load on ehci
o usb/83863    usb        [ugen] Communication problem between opensc/openct via
s usb/85067    usb        [uscanner] Cannot attach ScanJet 4300C to usb device
o usb/86298    usb        [mouse] Known good USB mouse won't work with correct s
o usb/87224    usb        Cannot mount USB Zip750
o usb/87648    usb        [mouse] Logitech USB-optical mouse problem.
o usb/88408    usb        [axe] axe0 read PHY failed
o usb/91546    usb        [umodem] [patch] Nokia 6630 mobile phone does not work
o usb/91811    usb        [umass] Compact Flash in HP Photosmart 2610 return  " 
o usb/91896    usb        camcontrol(8): Serial Number of USB Memory Sticks is n
o usb/92852    usb        [ums] [patch] Vertical scroll not working properly on 
o usb/93389    usb        [umass] [patch] Digital Camera Pentax S60 don't work
o usb/93872    usb        [cam] [patch] SCSI quirk required for ELTA 8061 OL USB
o usb/95037    usb        [umass] USB disk not recognized on hot-plug.
o usb/96381    usb        [cam] [patch] add a quirk table entry for a flash ram 
o usb/97175    usb        [umass] [hang] USB cardreader hangs system
o usb/97472    usb        [cam] [patch] add support for Olympus C150,D390
o usb/98343    usb        [boot] BBB reset failed errors with Creative Muvo MP3 
o usb/99538    usb        [keyboard] while using USB keyboard default params of 
o usb/100746   usb        [keyboard] system does not boot due to USB keyboard pr
o usb/101761   usb        [usb] [patch] [request] usb.h: increase maximal size o
o usb/101775   usb        [libusbhid] [patch] possible error in report descripto
o usb/102678   usb        [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not 
o usb/102976   usb        [panic] Casio Exilim Digital Camera causes panic on in
o usb/103046   usb        [ulpt] [patch] ulpt event driven I/O with select(2) an
o usb/103289   usb        [request] USB 2.0 problems on AMD LX-800 CPU and CS-55
o usb/103418   usb        [usbhidctl] [patch] [request] usbhidctl: add ability t
o usb/103917   usb        [uhub] USB driver reports "Addr 0 should never happen"
o usb/104290   usb        [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto
o usb/104352   usb        [ural] [patch] ural driver doesnt work
o usb/104645   usb        [umass] [request] Rave C-201 MP3 player does not commu
o usb/105065   usb        [ata] SATA - USB Bridge
o usb/105361   usb        [panic] Kernel panic during unmounting mass storage (C
o usb/106041   usb        [usb] [request] FreeBSD does not recognise Mustek Bear
o usb/106621   usb        [axe] [patch] DLINK DUB-E100 support broken
o usb/106861   usb        [usbdevs] [patch]: usbdevs update: Add product ACER Ze
o usb/107243   usb        [cam] [patch] Apacer USB Flash Drive quirk
o usb/107388   usb        [patch] [request] new driver: add utoppy device from N
o usb/107496   usb        [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [
o usb/107935   usb        [uplcom] [panic] panic while accessing /dev/cuaU0
o usb/108056   usb        [ohci] Mouse gets powered off during device probe when
s usb/108344   usb        [panic] kernel with atausb panics when unplugging USB 
o usb/110197   usb        [umass] Sony PSP umass device does not detach from EHC
s usb/110991   usb        [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends
o usb/112461   usb        [ehci] [request] ehci USB 2.0 doesn't work on nforce4
o usb/112463   usb        [umass] problem with Samsung USB DVD writer, libscg an
o usb/112944   usb        [ulpt] [patch] Bi-directional access to HP LaserJet 10
o usb/113060   usb        [usbdevs] [patch] Samsung printer not working in bidir
o usb/113432   usb        [ucom] WARNING: attempt to net_add_domain(netgraph) af
o conf/114013  usb        [patch] WITHOUT_USB allow to compil a lot of USB stuff
o usb/114068   usb        [umass] [patch] Problems with connection of the umass 
o usb/114916   usb        [umass] [patch] USB Maxtor drive (L300RO) requires qui
o usb/115400   usb        [ehci] Problem with EHCI on ASUS M2N4-SLI
o usb/115933   usb        [uftdi] [patch] RATOC REX-USB60F (usb serial converter
o usb/115935   usb        [usbdevs] [patch] kernel counterproductively attaches 
o usb/116282   usb        [ulpt] Cannot print on USB HP LJ1018 or LJ1300
o usb/117075   usb        [scsi_da] [patch] quirk: USB Samsung YP-U3 MP3
o usb/117183   usb        [panic] USB/fusefs -- panic while transferring large a
o usb/117185   usb        [umodem] [patch] Add support for UNION interface descr
o usb/117205   usb        [uscanner] [patch] uscanner support for HP ScanJet 447
o usb/117546   usb        [uftdi] [patch] Add MaxStream ZigBee product ID to uft
o usb/117598   usb        [uaudio] [patch] Not possible to record with Plantroni
o usb/117893   usb        [umass] Lacie USB DVD writing failing
o usb/117911   usb        [ums] [request] Mouse Gembird MUSWC not work
o usb/117938   usb        [ums] [patch] Adding support for MS WL Natural and MS 
o usb/118098   usb        [umass] 6th gen iPod causes problems when disconnectin
o usb/118485   usb        [usbdevs] [patch] Logitech Headset Workaround
o usb/118686   usb        [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei
o usb/119150   usb        [usbdevs] [patch] new usbdevs for CDMA 1xEVDO devices
o usb/119227   usb        [ubsa] [patch] ubsa buffer is too small; should be tun
o usb/119389   usb        [umass] Sony DSC-W1 CBI reset failed, STALLED [regress
o usb/119633   usb        [umass] umass0: BBB reset failed, IOERROR [regression]
o usb/119653   usb        [cam] [patch] iriver s7 player sync cache error patch
o usb/119981   usb        [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab
o usb/120572   usb        [umass] [patch] quirk to support ASUS P535 as umass (a
o usb/121045   usb        [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS
o usb/121169   usb        [umass] Issues with usb mp3 player
o usb/121184   usb        [uipaq] [patch] add ids from linux ipaq driver (plus a
o usb/121426   usb        [patch] [uscanner] add HP ScanJet 3570C
o usb/122025   usb        [patch] uscanner does not attach to Epson RX620 printe
o usb/122119   usb        [umass] umass device causes creation of daX but not da
o usb/122547   usb        [ehci] USB Printer not being recognized after reboot
p usb/122610   usb        Add Verizon v740 support to ubsa(4)
o usb/122621   usb        [patch] [request] New driver for Sierra Wireless 3G US
o usb/122712   usb        [usbdevs] [patch] Sony Vaio RF keyboard/mouse receiver
o usb/122813   usb        [udbp] [request] udbp driver should be removed in favo
o usb/122819   usb        Patch to provide dynamic additions to the usb quirks t
o usb/122936   usb        [ucom][ubsa] Device does not receive interrupt
o usb/122956   usb        Support for Novatel Wireless XU870 3G Card
o usb/122992   usb        MotoROKR Z6 Phone not recognised by umass as USB disk.
p usb/123148   usb        [uscanner] [patch] Epson DX8400/50 needs uscanner to s
p usb/123211   usb        [udav] if_udav driver doesn't support Davicom 9601 USB
o kern/123224  usb        [ums] Scroll wheel breakage w/ USB MS Wireless Intelli
o usb/123351   usb        Add Reiner SCT cyberJack, Omnikey [26]020, Fujitsu Sie
o usb/123352   usb        Add Option GTMAX3.6/7.2 and Quallcomm MMC module devic
o usb/123509   usb        [umass] continuous reset Samsung SGH-G600 phone
o usb/123611   usb        [usb] BBB reset failed, STALLED from Imation/Mitsumi U
o usb/123691   usb        usbd(8): usbd hangs
o usb/123959   usb        [ums] add support for Razer Lachesis 4000dpi usb mouse
o usb/123969   usb        Supermicro H8SMi-2 usb problem
o usb/124604   usb        Wireless Mouse doesn't work
o usb/125072   usb        [uplcom] [patch] add Mobile Action MA-620 Infrared Ada
o usb/125238   usb        Habu Mouse turns off in X
o usb/125264   usb        [patch] sysctl for set usb mouse rate (very useful for
o usb/125510   usb        repeated plug and unplug of USB mass storage devices l

134 problems total.

From freebsd at heesakkers.info  Tue Jul 22 22:10:35 2008
From: freebsd at heesakkers.info (Oliver Heesakkers)
Date: Tue Jul 22 22:10:46 2008
Subject: usb_reset
Message-ID: <200807222344.17713.freebsd@heesakkers.info>

I have a problem with the lack of usb_reset on FreeBSD (flashing an image to 
an Openmoko powered device with dfu-util).

> Resetting USB...
> error resetting after detach: usb_reset called, unimplemented on BSD
> not at least 2 device changes found ?!?
> Lost device after RESET?

Can anyone tell me if there is any work being done on this, and where I could 
follow that work?
From bruce at cran.org.uk  Tue Jul 22 22:45:09 2008
From: bruce at cran.org.uk (Bruce Cran)
Date: Tue Jul 22 22:45:15 2008
Subject: Microsoft Natural keyboard vendor/product strings aren't displayed
Message-ID: <20080722234426.04478e64@tau>

I've come across a strange issue with the detection of a Microsoft
Natural Elite keyboard I recently bought and am using with FreeBSD 7.0
with the PS/2-USB adapter that came with it. I've had a look through
some of the usb code and found the usbdevs file which I guess generates
a database of vendor/product strings that get used if the identification
data can't be read from the device itself. However, although my
keyboard is listed in usbdevs that information doesn't seem to get used
when it's attached:

ukbd0: <vendor 0x045e product 0x000b, class 0/0, rev 1.00/0.82, addr 3>
on uhub3

I've had a look through usbd_devinfo_vp in usb_subr.c but can't see
anything that would prevent the strings from usbdevs_data.h being used
when reading from the device fails. Is the usbdevs file still used to
obtain vendor/product strings when attaching usb devices or have I
just stumbled across a bug?

-- 
Bruce Cran
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20080722/85a052dc/signature.pgp
From pschmehl_lists at tx.rr.com  Tue Jul 22 23:35:15 2008
From: pschmehl_lists at tx.rr.com (Paul Schmehl)
Date: Tue Jul 22 23:35:21 2008
Subject: Microsoft Natural keyboard vendor/product strings aren't
	displayed
In-Reply-To: <20080722234426.04478e64@tau>
References: <20080722234426.04478e64@tau>
Message-ID: <51D000AAFDCDD4FD3DE78300@utd65257.utdallas.edu>

--On Tuesday, July 22, 2008 23:44:26 +0100 Bruce Cran <bruce@cran.org.uk> wrote:

> I've come across a strange issue with the detection of a Microsoft
> Natural Elite keyboard I recently bought and am using with FreeBSD 7.0
> with the PS/2-USB adapter that came with it. I've had a look through
> some of the usb code and found the usbdevs file which I guess generates
> a database of vendor/product strings that get used if the identification
> data can't be read from the device itself. However, although my
> keyboard is listed in usbdevs that information doesn't seem to get used
> when it's attached:
>
> ukbd0: <vendor 0x045e product 0x000b, class 0/0, rev 1.00/0.82, addr 3>
> on uhub3
>

Something is wrong with your system.  Here's the line in dmesg.boot on my 
workstation:

ukbd0: <vendor 0x045e Microsoft Natural Keyboard Elite, class 0/0, rev 
2.00/2.07, addr 3> on uhub3
kbd2 at ukbd0

I believe this is the same keyboard you are using:

# grep "Keyboard Elite" /usr/src/sys/dev/usb/*
/usr/src/sys/dev/usb/usbdevs:product MICROSOFT NATURALKBD       0x000b  Natural 
Keyboard Elite

# devinfo -v | grep 0x045e
                ukbd0 pnpinfo vendor=0x045e product=0x000b devclass=0x00 
devsubclass=0x00 release=0x0207 sernum="" intclass=0x03 intsubclass=0x01 at 
port=0 interface=0

-- 
Paul Schmehl
As if it wasn't already obvious,
my opinions are my own and not
those of my employer.

From gavin at FreeBSD.org  Wed Jul 23 11:35:29 2008
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Wed Jul 23 11:35:39 2008
Subject: usb/125736: [ukbd] [hang] system hangs after AT keyboard detect
	if ukbd loaded as a module
Message-ID: <200807231135.m6NBZTxN067063@freefall.freebsd.org>

Old Synopsis: [hang] system hangs after keyboard detect
New Synopsis: [ukbd] [hang] system hangs after AT keyboard detect if ukbd loaded as a module

State-Changed-From-To: feedback->open
State-Changed-By: gavin
State-Changed-When: Wed Jul 23 10:52:33 UTC 2008
State-Changed-Why: 
Feedback received: This is a problem seen by two different users, where
loading ukbd as a module will cause the boot process to hang while
detecting an AT keyboard iff ukbd is also built into the kernel


Responsible-Changed-From-To: gavin->freebsd-usb
Responsible-Changed-By: gavin
Responsible-Changed-When: Wed Jul 23 10:52:33 UTC 2008
Responsible-Changed-Why: 
Over to maintainer(s)

http://www.freebsd.org/cgi/query-pr.cgi?pr=125736
From hselasky at c2i.net  Wed Jul 23 17:53:44 2008
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Wed Jul 23 17:53:51 2008
Subject: usb_reset
In-Reply-To: <200807222344.17713.freebsd@heesakkers.info>
References: <200807222344.17713.freebsd@heesakkers.info>
Message-ID: <200807231855.21643.hselasky@c2i.net>

On Tuesday 22 July 2008, Oliver Heesakkers wrote:
> I have a problem with the lack of usb_reset on FreeBSD (flashing an image
> to an Openmoko powered device with dfu-util).
>
> > Resetting USB...
> > error resetting after detach: usb_reset called, unimplemented on BSD
> > not at least 2 device changes found ?!?
> > Lost device after RESET?
>
> Can anyone tell me if there is any work being done on this, and where I
> could follow that work?
> _______________________________________________
> 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"

Hi,

The official USB stack has no IOCTL for this. What you can do is to turn off 
the port power on the HUB manually, using an USB control request.

--HPS

From bruce at cran.org.uk  Wed Jul 23 19:13:32 2008
From: bruce at cran.org.uk (Bruce Cran)
Date: Wed Jul 23 19:13:39 2008
Subject: Microsoft Natural keyboard vendor/product strings aren't
 displayed
In-Reply-To: <51D000AAFDCDD4FD3DE78300@utd65257.utdallas.edu>
References: <20080722234426.04478e64@tau>
	<51D000AAFDCDD4FD3DE78300@utd65257.utdallas.edu>
Message-ID: <20080723201322.1a9f69c6@tau>

On Tue, 22 Jul 2008 18:06:39 -0500
Paul Schmehl <pschmehl_lists@tx.rr.com> wrote:

> --On Tuesday, July 22, 2008 23:44:26 +0100 Bruce Cran
> <bruce@cran.org.uk> wrote:
> 
> > I've come across a strange issue with the detection of a Microsoft
> > Natural Elite keyboard I recently bought and am using with FreeBSD
> > 7.0 with the PS/2-USB adapter that came with it. I've had a look
> > through some of the usb code and found the usbdevs file which I
> > guess generates a database of vendor/product strings that get used
> > if the identification data can't be read from the device itself.
> > However, although my keyboard is listed in usbdevs that information
> > doesn't seem to get used when it's attached:
> >
> > ukbd0: <vendor 0x045e product 0x000b, class 0/0, rev 1.00/0.82,
> > addr 3> on uhub3
> >
> 
> Something is wrong with your system.  Here's the line in dmesg.boot
> on my workstation:
> 
> ukbd0: <vendor 0x045e Microsoft Natural Keyboard Elite, class 0/0,
> rev 2.00/2.07, addr 3> on uhub3
> kbd2 at ukbd0
> 
> I believe this is the same keyboard you are using:
> 
> # grep "Keyboard Elite" /usr/src/sys/dev/usb/*
> /usr/src/sys/dev/usb/usbdevs:product MICROSOFT NATURALKBD
> 0x000b  Natural Keyboard Elite
> 
> # devinfo -v | grep 0x045e
>                 ukbd0 pnpinfo vendor=0x045e product=0x000b
> devclass=0x00 devsubclass=0x00 release=0x0207 sernum="" intclass=0x03
> intsubclass=0x01 at port=0 interface=0
> 

It is the same keyboard, but it's being identified as rev 1.00/0.82 as
opposed to 2.00/2.07 - I don't know if that makes any difference.   I'd
have thought it was something wrong with my system too but I've tried
it on my powerpc ibook running 8-CURRENT and it has the same problem.

-- 
Bruce
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20080723/8e096fd7/signature.pgp
From dfilter at FreeBSD.ORG  Thu Jul 24 23:30:04 2008
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Thu Jul 24 23:30:16 2008
Subject: usb/120017: commit references a PR
Message-ID: <200807242330.m6ONU4s5091691@freefall.freebsd.org>

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

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: usb/120017: commit references a PR
Date: Thu, 24 Jul 2008 23:22:46 +0000 (UTC)

 ivoras      2008-07-24 23:22:19 UTC
 
   FreeBSD src repository
 
   Modified files:
     sys/dev/usb          ehci_pci.c 
   Log:
   SVN rev 180791 on 2008-07-24 23:22:19Z by ivoras
   
   Add tweak for AMD Geode "companion" chip, AMD CS5536, which is apparently
   USB 2.0 capable but is shy and doesn't adwertise it much.
   
   PR:             120017
   Reviewed by:    imp
   Approved by:    gnn (mentor)
   MFC after:      2 weeks
   
   Revision  Changes    Path
   1.33      +10 -1     src/sys/dev/usb/ehci_pci.c
 _______________________________________________
 cvs-all@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/cvs-all
 To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
 
From Magik at back-up.pl  Thu Jul 24 23:30:08 2008
From: Magik at back-up.pl (Grzegorz Blach)
Date: Thu Jul 24 23:30:16 2008
Subject: usb/125941: not working wheel on my microsoft notebook optical
	mouse 3000
Message-ID: <200807242328.m6ONSOnO053385@www.freebsd.org>


>Number:         125941
>Category:       usb
>Synopsis:       not working wheel on my microsoft notebook optical mouse 3000
>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:   Thu Jul 24 23:30:07 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Grzegorz Blach
>Release:        RELENG_7
>Organization:
None
>Environment:
FreeBSD silver.doors 7.0-STABLE FreeBSD 7.0-STABLE #0: Thu Jul 24 20:25:56 CEST 2008    root@silver.doors:/usr/obj/usr/src/sys/SILVER  i386
>Description:
I have microsoft notebook optical (usb) mouse 3000,
When I installed FreeBSD 7.0 i386,
my mouse dont work, it start to work after I recompile kernel with patch from
http://lists.freebsd.org/pipermail/freebsd-usb/2008-February/004618.html.

When I update source with csup -g -L 2 /usr/share/examples/cvsup/stable-subfile,
this patch is integrated in source. After recompilation and reboot wheel on my mouse don't work. When I unplug and plug mouse again I see:

ums0: <Microsoft Microsoft Notebook Optical Mouse with Tilt Wheel, class
0/0, rev 2.00/1.20, addr 3> on uhub0
ums0: 3 buttons and a TILT dir.

there is no information about Z dir, but this info was in before upgrade.

With this report I attach my kernel config.

>How-To-Repeat:
Upgrade system with RELENG_7 release.
>Fix:


Patch attached with submission follows:

#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#    http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.10 2008/07/16 02:05:40 yongari Exp $

#cpu		I486_CPU
#cpu		I586_CPU
cpu		I686_CPU
ident		SILVER

# To statically compile in device wiring instead of /boot/device.hints
#hints		"GENERIC.hints"		# Default places to look for devices.

#makeoptions	DEBUG=-g		# Build kernel with gdb(1) debug symbols

options 	SCHED_ULE		# ULE scheduler
options 	PREEMPTION		# Enable kernel thread preemption
options 	INET			# InterNETworking
options 	INET6			# IPv6 communications protocols
options 	SCTP			# Stream Control Transmission Protocol
options 	FFS			# Berkeley Fast Filesystem
options 	SOFTUPDATES		# Enable FFS soft updates support
options 	UFS_ACL			# Support for access control lists
options 	UFS_DIRHASH		# Improve performance on big directories
options 	UFS_GJOURNAL		# Enable gjournal-based UFS journaling
#options 	MD_ROOT			# MD is a potential root device
options 	NFSCLIENT		# Network Filesystem Client
options 	NFSSERVER		# Network Filesystem Server
options 	NFSLOCKD		# Network Lock Manager
#options 	NFS_ROOT		# NFS usable as /, requires NFSCLIENT
options 	MSDOSFS			# MSDOS Filesystem
options 	CD9660			# ISO 9660 Filesystem
options 	PROCFS			# Process filesystem (requires PSEUDOFS)
options 	PSEUDOFS		# Pseudo-filesystem framework
options 	GEOM_PART_GPT		# GUID Partition Tables.
options 	GEOM_LABEL		# Provides labelization
options 	COMPAT_43TTY		# BSD 4.3 TTY compat [KEEP THIS!]
#options 	COMPAT_FREEBSD4		# Compatible with FreeBSD4
options 	COMPAT_FREEBSD5		# Compatible with FreeBSD5
options 	COMPAT_FREEBSD6		# Compatible with FreeBSD6
options 	SCSI_DELAY=5000		# Delay (in ms) before probing SCSI
options 	KTRACE			# ktrace(1) support
options 	STACK			# stack(9) support
options 	SYSVSHM			# SYSV-style shared memory
options 	SYSVMSG			# SYSV-style message queues
options 	SYSVSEM			# SYSV-style semaphores
options 	_KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
options 	KBD_INSTALL_CDEV	# install a CDEV entry in /dev
options 	ADAPTIVE_GIANT		# Giant mutex is adaptive.
options 	STOP_NMI		# Stop CPUS using NMI instead of IPI
options 	AUDIT			# Security event auditing

# To make an SMP kernel, the next two lines are needed
options 	SMP			# Symmetric MultiProcessor Kernel
device		apic			# I/O APIC

# CPU frequency control
device		cpufreq

# Bus support.
#device		eisa
device		pci

# Floppy drives
#device		fdc

# ATA and ATAPI devices
device		ata
device		atadisk		# ATA disk drives
device		ataraid		# ATA RAID drives
device		atapicd		# ATAPI CDROM drives
#device		atapifd		# ATAPI floppy drives
#device		atapist		# ATAPI tape drives
options 	ATA_STATIC_ID	# Static device numbering

# SCSI Controllers
#device		ahb		# EISA AHA1742 family
device		ahc		# AHA2940 and onboard AIC7xxx devices
#options 	AHC_REG_PRETTY_PRINT	# Print register bitfields in debug
					# output.  Adds ~128k to driver.
#device		ahd		# AHA39320/29320 and onboard AIC79xx devices
#options 	AHD_REG_PRETTY_PRINT	# Print register bitfields in debug
					# output.  Adds ~215k to driver.
#device		amd		# AMD 53C974 (Tekram DC-390(T))
#device		hptiop		# Highpoint RocketRaid 3xxx series
#device		isp		# Qlogic family
#device 	ispfw		# Firmware for QLogic HBAs- normally a module
#device		mpt		# LSI-Logic MPT-Fusion
#device		ncr		# NCR/Symbios Logic
#device		sym		# NCR/Symbios Logic (newer chipsets + those of `ncr')
#device		trm		# Tekram DC395U/UW/F DC315U adapters

#device		adv		# Advansys SCSI adapters
#device		adw		# Advansys wide SCSI adapters
#device		aha		# Adaptec 154x SCSI adapters
#device		aic		# Adaptec 15[012]x SCSI adapters, AIC-6[23]60.
#device		bt		# Buslogic/Mylex MultiMaster SCSI adapters

#device		ncv		# NCR 53C500
#device		nsp		# Workbit Ninja SCSI-3
#device		stg		# TMC 18C30/18C50

# SCSI peripherals
device		scbus		# SCSI bus (required for SCSI)
device		ch		# SCSI media changers
device		da		# Direct Access (disks)
device		sa		# Sequential Access (tape etc)
device		cd		# CD
device		pass		# Passthrough device (direct SCSI access)
device		ses		# SCSI Environmental Services (and SAF-TE)

# RAID controllers interfaced to the SCSI subsystem
#device		amr		# AMI MegaRAID
#device		arcmsr		# Areca SATA II RAID
#device		asr		# DPT SmartRAID V, VI and Adaptec SCSI RAID
#device		ciss		# Compaq Smart RAID 5*
#device		dpt		# DPT Smartcache III, IV - See NOTES for options
#device		hptmv		# Highpoint RocketRAID 182x
#device		hptrr		# Highpoint RocketRAID 17xx, 22xx, 23xx, 25xx
#device		iir		# Intel Integrated RAID
#device		ips		# IBM (Adaptec) ServeRAID
#device		mly		# Mylex AcceleRAID/eXtremeRAID
#device		twa		# 3ware 9000 series PATA/SATA RAID

# RAID controllers
#device		aac		# Adaptec FSA RAID
#device		aacp		# SCSI passthrough for aac (requires CAM)
#device		ida		# Compaq Smart RAID
#device		mfi		# LSI MegaRAID SAS
#device		mlx		# Mylex DAC960 family
#device		pst		# Promise Supertrak SX6000
#device		twe		# 3ware ATA RAID

# atkbdc0 controls both the keyboard and the PS/2 mouse
#device		atkbdc		# AT keyboard controller
#device		atkbd		# AT keyboard
#device		psm		# PS/2 mouse

device		kbdmux		# keyboard multiplexer

device		vga		# VGA video card driver

device		splash		# Splash screen and screen saver support

# syscons is the default console driver, resembling an SCO console
device		sc

#device		agp		# support several AGP chipsets

# Power management support (see NOTES for more options)
#device		apm
# Add suspend/resume support for the i8254.
device		pmtimer

# PCCARD (PCMCIA) support
# PCMCIA and cardbus bridge support
#device		cbb		# cardbus (yenta) bridge
#device		pccard		# PC Card (16-bit) bus
#device		cardbus		# CardBus (32-bit) bus

# Serial (COM) ports
#device		sio		# 8250, 16[45]50 based serial ports
#device		uart		# Generic UART driver

# Parallel port
#device		ppc
#device		ppbus		# Parallel port bus (required)
#device		lpt		# Printer
#device		plip		# TCP/IP over parallel
#device		ppi		# Parallel port interface device
#device		vpo		# Requires scbus and da

# If you've got a "dumb" serial or parallel PCI card that is
# supported by the puc(4) glue driver, uncomment the following
# line to enable it (connects to sio, uart and/or ppc drivers):
#device		puc

# PCI Ethernet NICs.
#device		de		# DEC/Intel DC21x4x (``Tulip'')
#device		em		# Intel PRO/1000 adapter Gigabit Ethernet Card
#device		ixgb		# Intel PRO/10GbE Ethernet Card
#device		le		# AMD Am7900 LANCE and Am79C9xx PCnet
#device		txp		# 3Com 3cR990 (``Typhoon'')
#device		vx		# 3Com 3c590, 3c595 (``Vortex'')

# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device		miibus		# MII bus support
#device		age		# Attansic/Atheros L1 Gigabit Ethernet
#device		bce		# Broadcom BCM5706/BCM5708 Gigabit Ethernet
#device		bfe		# Broadcom BCM440x 10/100 Ethernet
#device		bge		# Broadcom BCM570xx Gigabit Ethernet
#device		dc		# DEC/Intel 21143 and various workalikes
#device		et		# Agere ET1310 10/100/Gigabit Ethernet
device		fxp		# Intel EtherExpress PRO/100B (82557, 82558)
#device		jme		# JMicron JMC250 Gigabit/JMC260 Fast Ethernet
#device		lge		# Level 1 LXT1001 gigabit Ethernet
#device		msk		# Marvell/SysKonnect Yukon II Gigabit Ethernet
device		nfe		# nVidia nForce MCP on-board Ethernet
#device		nge		# NatSemi DP83820 gigabit Ethernet
#device		nve		# nVidia nForce MCP on-board Ethernet Networking
#device		pcn		# AMD Am79C97x PCI 10/100 (precedence over 'le')
#device		re		# RealTek 8139C+/8169/8169S/8110S
#device		rl		# RealTek 8129/8139
#device		sf		# Adaptec AIC-6915 (``Starfire'')
#device		sis		# Silicon Integrated Systems SiS 900/SiS 7016
#device		sk		# SysKonnect SK-984x & SK-982x gigabit Ethernet
#device		ste		# Sundance ST201 (D-Link DFE-550TX)
#device		stge		# Sundance/Tamarack TC9021 gigabit Ethernet
#device		ti		# Alteon Networks Tigon I/II gigabit Ethernet
#device		tl		# Texas Instruments ThunderLAN
#device		tx		# SMC EtherPower II (83c170 ``EPIC'')
#device		vge		# VIA VT612x gigabit Ethernet
#device		vr		# VIA Rhine, Rhine II
#device		wb		# Winbond W89C840F
#device		xl		# 3Com 3c90x (``Boomerang'', ``Cyclone'')

# ISA Ethernet NICs.  pccard NICs included.
#device		cs		# Crystal Semiconductor CS89x0 NIC
# 'device ed' requires 'device miibus'
#device		ed		# NE[12]000, SMC Ultra, 3c503, DS8390 cards
#device		ex		# Intel EtherExpress Pro/10 and Pro/10+
#device		ep		# Etherlink III based cards
#device		fe		# Fujitsu MB8696x based cards
#device		ie		# EtherExpress 8/16, 3C507, StarLAN 10 etc.
#device		sn		# SMC's 9000 series of Ethernet chips
#device		xe		# Xircom pccard Ethernet

# Wireless NIC cards
#device		wlan		# 802.11 support
#device		wlan_wep	# 802.11 WEP support
#device		wlan_ccmp	# 802.11 CCMP support
#device		wlan_tkip	# 802.11 TKIP support
#device		wlan_amrr	# AMRR transmit rate control algorithm
#device		wlan_scan_ap	# 802.11 AP mode scanning
#device		wlan_scan_sta	# 802.11 STA mode scanning
#device		an		# Aironet 4500/4800 802.11 wireless NICs.
#device		ath		# Atheros pci/cardbus NIC's
#device		ath_hal		# Atheros HAL (Hardware Access Layer)
#device		ath_rate_sample	# SampleRate tx rate control for ath
#device		awi		# BayStack 660 and others
#device		ral		# Ralink Technology RT2500 wireless NICs.
#device		wi		# WaveLAN/Intersil/Symbol 802.11 wireless NICs.
#device		wl		# Older non 802.11 Wavelan wireless NIC.

# Pseudo devices.
device		loop		# Network loopback
device		random		# Entropy device
device		ether		# Ethernet support
#device		sl		# Kernel SLIP
#device		ppp		# Kernel PPP
device		tun		# Packet tunnel.
device		pty		# Pseudo-ttys (telnet etc)
device		md		# Memory "disks"
device		gif		# IPv6 and IPv4 tunneling
device		faith		# IPv6-to-IPv4 relaying (translation)
device		firmware	# firmware assist module

# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
# Note that 'bpf' is required for DHCP.
device		bpf		# Berkeley packet filter

# USB support
device		uhci		# UHCI PCI->USB interface
device		ohci		# OHCI PCI->USB interface
device		ehci		# EHCI PCI->USB interface (USB 2.0)
device		usb		# USB Bus (required)
#device		udbp		# USB Double Bulk Pipe devices
device		ugen		# Generic
device		uhid		# "Human Interface Devices"
device		ukbd		# Keyboard
#device		ulpt		# Printer
device		umass		# Disks/Mass storage - Requires scbus and da
device		ums		# Mouse
#device		ural		# Ralink Technology RT2500USB wireless NICs
#device		rum		# Ralink Technology RT2501USB wireless NICs
#device		urio		# Diamond Rio 500 MP3 player
#device		uscanner	# Scanners
# USB Serial devices
device		ucom		# Generic com ttys
device		uark		# Technologies ARK3116 based serial adapters
device		ubsa		# Belkin F5U103 and compatible serial adapters
device		ubser		# BWCT console serial adapters
device		uftdi		# For FTDI usb serial adapters
device		uipaq		# Some WinCE based devices
device		uplcom		# Prolific PL-2303 serial adapters
device		uslcom		# SI Labs CP2101/CP2102 serial adapters
device		uvisor		# Visor and Palm devices
device		uvscom		# USB serial support for DDI pocket's PHS
# USB Ethernet, requires miibus
#device		aue		# ADMtek USB Ethernet
#device		axe		# ASIX Electronics USB Ethernet
#device		cdce		# Generic USB over Ethernet
#device		cue		# CATC USB Ethernet
#device		kue		# Kawasaki LSI USB Ethernet
#device		rue		# RealTek RTL8150 USB Ethernet

# FireWire support
#device		firewire	# FireWire bus code
#device		sbp		# SCSI over FireWire (Requires scbus and da)
#device		fwe		# Ethernet over FireWire (non-standard!)
#device		fwip		# IP over FireWire (RFC 2734,3146)
#device		dcons		# Dumb console driver
#device		dcons_crom	# Configuration ROM for dcons


>Release-Note:
>Audit-Trail:
>Unformatted:
From admin at lissyara.su  Sun Jul 27 17:40:03 2008
From: admin at lissyara.su (Alex Keda)
Date: Sun Jul 27 17:40:10 2008
Subject: usb/125941: [ums] not working wheel on my microsoft notebook
 optical mouse 3000
Message-ID: <200807271740.m6RHe3e7054058@freefall.freebsd.org>

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

From: Alex Keda <admin@lissyara.su>
To: bug-followup@FreeBSD.org, Magik@back-up.pl
Cc:  
Subject: Re: usb/125941: [ums] not working wheel on my microsoft notebook
 optical mouse 3000
Date: Sun, 27 Jul 2008 21:38:46 +0400

 please, test this patch. this may fix you problems
 http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/117911
From bugmaster at FreeBSD.org  Mon Jul 28 11:07:06 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Jul 28 11:09:06 2008
Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org
Message-ID: <200807281107.m6SB754d079081@freefall.freebsd.org>

Current FreeBSD problem reports
Critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
f usb/84750    usb        [hang] 6-BETA2 reboot/shutdown with root_fs on externa
o usb/91629    usb        usbd_abort_pipe() may result in infinite loop

2 problems total.

Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o i386/46371   usb        USB controller cannot be initialized on IBM Netfinity 
o bin/57255    usb        usbd(8) and multi-function devices
o usb/63621    usb        [umass] [panic] USB MemoryStick Reader stalls/crashes 
o usb/67301    usb        [uftdi] [panic] RTS and system panic
o usb/69006    usb        [usbdevs] [patch] Apple Cinema Display hangs USB ports
o usb/71155    usb        [ulpt] misbehaving usb-printer hangs processes, causes
o usb/73307    usb        [panic] Kernel panics on USB disconnect
o usb/74771    usb        [umass] [hang] mounting write-protected umass device a
o usb/75705    usb        [umass] [panic] da0 attach / Optio S4 (with backtrace)
o usb/75797    usb        [sound] 5.3-STABLE(2005 1/4) detect USB headset, But c
o usb/76395    usb        [uhci] USB printer does not work, usbdevs says "addr 0
o usb/77184    usb        [umass] [panic] kernel panic on USB device disconnect,
o usb/77294    usb        [ucom] [panic] ucom + ulpcom panic
o usb/79269    usb        [ohci] USB ohci da0 plug/unplug causes crashes and loc
o usb/79287    usb        [uhci] [hang] UHCI hang after interrupt transfer
o usb/79524    usb        [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa
a usb/79656    usb        [ehci] RHSC interrupts lost
o usb/79722    usb        [ehci] wrong alignments in ehci.h
o usb/80040    usb        [hang] Use of sound mixer causes system freeze with ua
o usb/80361    usb        [umass] [patch] mounting of Dell usb-stick fails
o usb/80829    usb        [modules] [panic] possible panic when loading USB-modu
o usb/80862    usb        [patch] USB locking issues: missing some Giant calls
o usb/82350    usb        [ucom] [panic] null pointer dereference in USB stack
o usb/82520    usb        [udbp] [reboot] Reboot when USL101 connected
s usb/82569    usb        [umass] [panic] USB mass storage plug/unplug causes sy
o usb/82660    usb        [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic
o usb/83504    usb        [kernel] [patch] SpeedTouch USB stop working on recent
o usb/83563    usb        [umass] [panic] Page Fault while detaching Mpman Usb d
f usb/83677    usb        [usb] [request] usb controller often not detected (Sun
o usb/83756    usb        [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe
o usb/83977    usb        [ucom] [panic] ucom1: open bulk out error (addr 2): IN
o usb/84326    usb        [umass] Panic trying to connect SCSI tape drive via US
s usb/84336    usb        [usb] [reboot] instant system reboot when unmounting a
o usb/86767    usb        [umass] [patch] bogus "slice starts beyond end of the 
o usb/88743    usb        [hang] [regression] USB makes kernel hang at boot (reg
s usb/89003    usb        [request] LaCie Firewire drive not properly supported 
o usb/89954    usb        [umass] [panic] USB Disk driver race condition?
o usb/90700    usb        [umass] [panic] Kernel panic on connect/mount/use umas
o usb/91238    usb        [umass] USB tape unit fails to write a second tape fil
o usb/91283    usb        [boot] [regression] booting very slow with usb devices
o usb/91538    usb        [ulpt] [patch] Unable to print to EPSON CX3500
o usb/91906    usb        [ehci] [hang] FreeBSD hangs while booting with USB leg
o usb/92052    usb        [ulpt] usbd causes defunct process with busy file-hand
o usb/92083    usb        [ural] [panic] panic using WPA on ural NIC in 6.0-RELE
o usb/92142    usb        [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb 
o usb/92171    usb        [panic] panic unplugging Vodafone Mobile Connect (UMTS
o usb/93155    usb        [ulpt] /dev/ulpt0: device busy, USB printer does not w
o usb/93408    usb        [mouse] hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes 
o usb/93828    usb        [ohci] [panic] ohci causes panic on boot (HP Pavillion
o usb/94384    usb        [panic] kernel panic with usb2 hardware
o usb/94717    usb        [ulpt] Reading from /dev/ulpt can break work of a UHCI
o usb/94897    usb        [panic] Kernel Panic when cleanly unmounting USB disk
s usb/95348    usb        [keyboard] USB keyboard unplug causes noise on screen
o usb/95562    usb        [umass] Write Stress in USB Mass drive causes "vinvalb
s usb/95636    usb        [umass] [boot] 5 minute delay at boot when using VT620
s usb/96120    usb        [ums] [request] USB mouse not always detected
o usb/96224    usb        [usb] [msdosfs] mount_msdosfs cause page fault in sync
o usb/96457    usb        [umass] [panic] fatback on umass = reboot
s usb/97286    usb        [mouse] [request] MS Wireless Intellimouse Explorer 2.
o usb/99431    usb        [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar
o usb/101096   usb        [ural] [panic] USB WLAN occasionally causes kernel-pan
o usb/101448   usb        [ohci] FBSD 6.1-STABLE/AMD64 crashes under heavy USB/O
o usb/101752   usb        [umass] [panic] 6.1-RELEASE kernel panic on usb device
o usb/102066   usb        [ukbd] usb keyboard and multimedia keys don't work
f usb/102096   usb        [patch] usbd(8) does not handle multiple devices in on
o usb/103025   usb        [uhub] [panic] wrong detection of USB device for FreeB
o usb/104292   usb        [umass] [hang] system lockup on forced umount of usb-s
o usb/104830   usb        [umass] system crashes when copying data to umass devi
o usb/105186   usb        [ehci] [panic] USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 c
o usb/106615   usb        [uftdi] uftdi module does not automatically load with 
o usb/106648   usb        [umass] [hang] USB Floppy on D1950 10 min Hang on Inse
s usb/106832   usb        USB HP printer is not detected by kernel when ACPI ena
o usb/107248   usb        [umass] [patch] scsi_da.c quirk for Cowon iAUDIO X5 MP
o usb/107446   usb        [umass] umass problems (usb and fw disks)
o usb/107827   usb        [ohci] [panic] ohci_add_done addr not found
o usb/107848   usb        [umass] [request] cannot access Samsung flash disk
o usb/107924   usb        [patch] usbd(8) does not call detach
o usb/108513   usb        [umass] Creative MuVo TX FM fails in 6.2-RELEASE [regr
o usb/109274   usb        [usb] MCP55 USB Controller fails to attach in AMD64 Cu
o usb/109397   usb        [panic] on boot from USB flash
o usb/110856   usb        [ugen] [patch] interrupt in msgs are truncated when bu
o usb/110988   usb        [umass] [patch] Handling of quirk IGNORE_RESIDUE is um
o usb/111753   usb        [uhid] [panic] Replicable system panic involving UHID 
s usb/112568   usb        [umass] [request] USB mode may wrong when mounting Pla
o usb/112631   usb        [panic] Problem with SONY DSC-S80 camera on umount
o usb/112640   usb        [usb] [hang] Kernel freezes when writing a file to an 
s usb/113629   usb        [ukbd] Dropped USB keyboard events on Dell Latitude D6
o usb/113672   usb        [ehci] [panic] Kernel panic with AEWIN CB6971
s usb/113977   usb        [request] Need a way to set mode of USB disk's write c
o usb/114310   usb        [libusb] [patch] [panic] USB hub attachment panics ker
o usb/114682   usb        [umass] generic USB media-card reader unusable
o kern/114780  usb        [uplcom] [panic] Panics while stress testing the uplco
o usb/115298   usb        [ulpt] [panic] Turning off USB printer panics kernel
o usb/116561   usb        [umodem] [panic] RELENG_6 umodem panic "trying to slee
o usb/116699   usb        [usbhid] USB HID devices do not initialize at system b
o usb/116947   usb        [ukbd] [patch] [regression] enable boot protocol on th
o usb/117200   usb        [ugen] ugen0 prints strange string on attach if detach
o usb/117313   usb        [umass] [panic] panic on usb camera insertion
o usb/117613   usb        [uhci] [irq] uhci interrupt storm & USB leaked memory 
o usb/117946   usb        [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE
o usb/117955   usb        [umass] [panic] inserting minolta dimage a2 crashes OS
o usb/118140   usb        [ucom] [patch] quick hack for ucom to get it behave wi
o usb/118141   usb        [ucom] usb serial and nokia phones ucomreadcb ucomread
o usb/118353   usb        [panic] [ppp] repeatable kernel panic during ppp(4) se
o usb/118480   usb        [umass] Timeout in USB mass storage freezes vfs layer 
o usb/119201   usb        [cam] [patch] Quirks for Olympus FE-210 camera, LG and
o usb/119481   usb        [hang] FreeBSD not responding after connecting USB-Mas
o usb/119509   usb        USB flaky on Dell Optiplex 755
o usb/119513   usb        [irq] inserting dlink dwl-g630 wireless card results i
o usb/119977   usb        [ums] Mouse does not work in a Cherry-USB keyboard/mou
o usb/120017   usb        [ehci] [patch] CS5536 (AMD Geode) USB 2.0 quirk
o usb/120034   usb        [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 
o usb/120283   usb        [panic] Automation reboot with wireless keyboard & mou
o usb/120321   usb        [hang] System hangs when transferring data to WD MyBoo
o usb/120729   usb        [panic] fault while in kernel mode with connecting USB
o usb/120786   usb        Kernel panic when forced umount of a dettached USB Har
o usb/121232   usb        remove PCCARD rebooted system
o usb/121275   usb        [boot] FreeBSD fails to boot with usb legacy support e
o usb/121474   usb        [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard
o usb/121708   usb        [keyboard] nforce 650i mobo w/ usb keyboard infinite k
o usb/121734   usb        [ugen] ugen HP1022 printer device not working since up
o usb/121755   usb        [ohci] [patch] Fix panic after ohci/uhub cardbus devic
o usb/122483   usb        [panic] [ulpt] Repeatable panic in 7.0-STABLE
o usb/122539   usb        [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci
o usb/122905   usb        [ubsa] [patch] add Huawei E220 to ubsa
o kern/123510  usb        [ums] Mouse Wheel Fails to Work [regression]
o usb/123690   usb        Panic on USB device insertion when usb loaded as a mod
o usb/123714   usb        Panic when hald-storage-probe runs with umass device i
o usb/124708   usb        [panic] Kernel panic on USB KVM reattach
o usb/124758   usb        rum panics SMP kernel
o kern/124777  usb        [ucom] USB cua devices don't revert to tty devices whe
o usb/124980   usb        [panic] kernel panic on detaching unmounted umass devi
o usb/125088   usb        Touchpad not detected on Adesso AKB-430UG USB kbd/pad 
o usb/125450   usb        [panic] Removing USB flash card while being accessed c
o usb/125631   usb        [usb][ums] kernel panic during bootup while 'Logitech 

135 problems total.

Non-critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o conf/30929   usb        [usb] [patch] use usbd to initialize USB ADSL modem
o usb/40948    usb        [umass] [request] USB HP CDW8200 does not work
s usb/51958    usb        [urio] [patch] update for urio driver
s usb/52026    usb        [usb] [request] umass driver support for InSystem ISD2
o usb/59698    usb        [keyboard] [patch] Rework of ukbd HID to AT code trans
s usb/62257    usb        [umass] [request] card reader UCR-61S2B is only half-s
o usb/66547    usb        [ucom] Palm Tungsten T USB does not initialize correct
o usb/68232    usb        [ugen] [patch] ugen(4) isochronous handling correction
o usb/70523    usb        [umct] [patch] umct sending/receiving wrong characters
o usb/71280    usb        [aue] aue0 device (linksys usb100tx) doesn't work in 1
o usb/71416    usb        [ugen] Cryptoflex e-gate USB token (ugen0) detach is n
o usb/71417    usb        [ugen] Cryptoflex e-gate USB token (ugen0) communicati
o usb/71455    usb        [umass] Slow USB umass performance of 5.3
s usb/72733    usb        [ucom] [request] Kyocera 7135 Palm OS connection probl
o usb/74211    usb        [umass] USB flash drive causes CAM status 0x4 on 4.10R
a usb/74453    usb        [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL
o usb/75764    usb        [umass] [patch] "umass0: Phase Error" - no device for 
o usb/75800    usb        [ucom] ucom1: init failed STALLED error in time of syn
s usb/75928    usb        [umass] [request] Cytronix SmartMedia card (SMC) reade
o usb/76461    usb        [umass] disklabel of umass(4)-CAM(4)-da(4) not used by
o usb/76653    usb        [umass] [patch] Problem with Asahi Optical usb device 
o usb/76732    usb        Mouse problems with USB KVM Switch
o usb/78984    usb        [umass] [patch] Creative MUVO umass failure
o usb/79723    usb        [usb] [request] prepare for high speed isochronous tra
o usb/80774    usb        [patch] have "usbd_find_desc" in line with the other "
s usb/80776    usb        [udav] [request] UDAV device driver shouldn't use usb_
s usb/80777    usb        [request] usb_rem_task() should wait for callback to c
o usb/80854    usb        [patch] [request] suggestion for new iface-no-probe me
o usb/80935    usb        [uvisor] [patch] uvisor.c is not work with CLIE TH55.
o usb/81621    usb        [ehci] [hang] external hd hangs under load on ehci
o usb/83863    usb        [ugen] Communication problem between opensc/openct via
s usb/85067    usb        [uscanner] Cannot attach ScanJet 4300C to usb device
o usb/86298    usb        [mouse] Known good USB mouse won't work with correct s
o usb/87224    usb        Cannot mount USB Zip750
o usb/87648    usb        [mouse] Logitech USB-optical mouse problem.
o usb/88408    usb        [axe] axe0 read PHY failed
o usb/91546    usb        [umodem] [patch] Nokia 6630 mobile phone does not work
o usb/91811    usb        [umass] Compact Flash in HP Photosmart 2610 return  " 
o usb/91896    usb        camcontrol(8): Serial Number of USB Memory Sticks is n
o usb/92852    usb        [ums] [patch] Vertical scroll not working properly on 
o usb/93389    usb        [umass] [patch] Digital Camera Pentax S60 don't work
o usb/93872    usb        [cam] [patch] SCSI quirk required for ELTA 8061 OL USB
o usb/95037    usb        [umass] USB disk not recognized on hot-plug.
o usb/96381    usb        [cam] [patch] add a quirk table entry for a flash ram 
o usb/97175    usb        [umass] [hang] USB cardreader hangs system
o usb/97472    usb        [cam] [patch] add support for Olympus C150,D390
o usb/98343    usb        [boot] BBB reset failed errors with Creative Muvo MP3 
o usb/99538    usb        [keyboard] while using USB keyboard default params of 
o usb/100746   usb        [keyboard] system does not boot due to USB keyboard pr
o usb/101761   usb        [usb] [patch] [request] usb.h: increase maximal size o
o usb/101775   usb        [libusbhid] [patch] possible error in report descripto
o usb/102678   usb        [keyboard] Dell PowerEdge DRAC5 USB Keyboard does not 
o usb/102976   usb        [panic] Casio Exilim Digital Camera causes panic on in
o usb/103046   usb        [ulpt] [patch] ulpt event driven I/O with select(2) an
o usb/103289   usb        [request] USB 2.0 problems on AMD LX-800 CPU and CS-55
o usb/103418   usb        [usbhidctl] [patch] [request] usbhidctl: add ability t
o usb/103917   usb        [uhub] USB driver reports "Addr 0 should never happen"
o usb/104290   usb        [umass] [patch] quirk: TOSHIBA DVD-RAM drive (libretto
o usb/104352   usb        [ural] [patch] ural driver doesnt work
o usb/104645   usb        [umass] [request] Rave C-201 MP3 player does not commu
o usb/105065   usb        [ata] SATA - USB Bridge
o usb/105361   usb        [panic] Kernel panic during unmounting mass storage (C
o usb/106041   usb        [usb] [request] FreeBSD does not recognise Mustek Bear
o usb/106621   usb        [axe] [patch] DLINK DUB-E100 support broken
o usb/106861   usb        [usbdevs] [patch]: usbdevs update: Add product ACER Ze
o usb/107243   usb        [cam] [patch] Apacer USB Flash Drive quirk
o usb/107388   usb        [patch] [request] new driver: add utoppy device from N
o usb/107496   usb        [uhub] USB device problem on RELENG_6_2 (SHORT_XFER) [
o usb/107935   usb        [uplcom] [panic] panic while accessing /dev/cuaU0
o usb/108056   usb        [ohci] Mouse gets powered off during device probe when
s usb/108344   usb        [panic] kernel with atausb panics when unplugging USB 
o usb/110197   usb        [umass] Sony PSP umass device does not detach from EHC
s usb/110991   usb        [usbdevs] [patch] QUIRK: Super Top IDE DEVICE (depends
o usb/112461   usb        [ehci] [request] ehci USB 2.0 doesn't work on nforce4
o usb/112463   usb        [umass] problem with Samsung USB DVD writer, libscg an
o usb/112944   usb        [ulpt] [patch] Bi-directional access to HP LaserJet 10
o usb/113060   usb        [usbdevs] [patch] Samsung printer not working in bidir
o usb/113432   usb        [ucom] WARNING: attempt to net_add_domain(netgraph) af
o conf/114013  usb        [patch] WITHOUT_USB allow to compil a lot of USB stuff
o usb/114068   usb        [umass] [patch] Problems with connection of the umass 
o usb/114916   usb        [umass] [patch] USB Maxtor drive (L300RO) requires qui
o usb/115400   usb        [ehci] Problem with EHCI on ASUS M2N4-SLI
o usb/115933   usb        [uftdi] [patch] RATOC REX-USB60F (usb serial converter
o usb/115935   usb        [usbdevs] [patch] kernel counterproductively attaches 
o usb/116282   usb        [ulpt] Cannot print on USB HP LJ1018 or LJ1300
o usb/117075   usb        [scsi_da] [patch] quirk: USB Samsung YP-U3 MP3
o usb/117183   usb        [panic] USB/fusefs -- panic while transferring large a
o usb/117185   usb        [umodem] [patch] Add support for UNION interface descr
o usb/117205   usb        [uscanner] [patch] uscanner support for HP ScanJet 447
o usb/117546   usb        [uftdi] [patch] Add MaxStream ZigBee product ID to uft
o usb/117598   usb        [uaudio] [patch] Not possible to record with Plantroni
o usb/117893   usb        [umass] Lacie USB DVD writing failing
o usb/117911   usb        [ums] [request] Mouse Gembird MUSWC not work
o usb/117938   usb        [ums] [patch] Adding support for MS WL Natural and MS 
o usb/118098   usb        [umass] 6th gen iPod causes problems when disconnectin
o usb/118485   usb        [usbdevs] [patch] Logitech Headset Workaround
o usb/118686   usb        [usbdevs] [patch] teach usbdevs / ubsa(4) about Huawei
o usb/119150   usb        [usbdevs] [patch] new usbdevs for CDMA 1xEVDO devices
o usb/119227   usb        [ubsa] [patch] ubsa buffer is too small; should be tun
o usb/119389   usb        [umass] Sony DSC-W1 CBI reset failed, STALLED [regress
o usb/119633   usb        [umass] umass0: BBB reset failed, IOERROR [regression]
o usb/119653   usb        [cam] [patch] iriver s7 player sync cache error patch
o usb/119981   usb        [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab
o usb/120572   usb        [umass] [patch] quirk to support ASUS P535 as umass (a
o usb/121045   usb        [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS
o usb/121169   usb        [umass] Issues with usb mp3 player
o usb/121184   usb        [uipaq] [patch] add ids from linux ipaq driver (plus a
o usb/121426   usb        [patch] [uscanner] add HP ScanJet 3570C
o usb/122025   usb        [patch] uscanner does not attach to Epson RX620 printe
o usb/122119   usb        [umass] umass device causes creation of daX but not da
o usb/122547   usb        [ehci] USB Printer not being recognized after reboot
p usb/122610   usb        Add Verizon v740 support to ubsa(4)
o usb/122621   usb        [patch] [request] New driver for Sierra Wireless 3G US
o usb/122712   usb        [usbdevs] [patch] Sony Vaio RF keyboard/mouse receiver
o usb/122813   usb        [udbp] [request] udbp driver should be removed in favo
o usb/122819   usb        Patch to provide dynamic additions to the usb quirks t
o usb/122936   usb        [ucom][ubsa] Device does not receive interrupt
o usb/122956   usb        Support for Novatel Wireless XU870 3G Card
o usb/122992   usb        MotoROKR Z6 Phone not recognised by umass as USB disk.
p usb/123148   usb        [uscanner] [patch] Epson DX8400/50 needs uscanner to s
p usb/123211   usb        [udav] if_udav driver doesn't support Davicom 9601 USB
o kern/123224  usb        [ums] Scroll wheel breakage w/ USB MS Wireless Intelli
o usb/123351   usb        Add Reiner SCT cyberJack, Omnikey [26]020, Fujitsu Sie
o usb/123352   usb        Add Option GTMAX3.6/7.2 and Quallcomm MMC module devic
o usb/123509   usb        [umass] continuous reset Samsung SGH-G600 phone
o usb/123611   usb        [usb] BBB reset failed, STALLED from Imation/Mitsumi U
o usb/123691   usb        usbd(8): usbd hangs
o usb/123959   usb        [ums] add support for Razer Lachesis 4000dpi usb mouse
o usb/123969   usb        Supermicro H8SMi-2 usb problem
o usb/124604   usb        Wireless Mouse doesn't work
o usb/125072   usb        [uplcom] [patch] add Mobile Action MA-620 Infrared Ada
o usb/125238   usb        Habu Mouse turns off in X
o usb/125264   usb        [patch] sysctl for set usb mouse rate (very useful for
o usb/125510   usb        repeated plug and unplug of USB mass storage devices l
o usb/125736   usb        [ukbd] [hang] system hangs after AT keyboard detect if
o usb/125941   usb        [ums] not working wheel on my microsoft notebook optic

136 problems total.

From okrg at ukr.net  Wed Jul 30 09:10:04 2008
From: okrg at ukr.net (Oleksii Krykun)
Date: Wed Jul 30 09:10:11 2008
Subject: usb/122992: MotoROKR Z6 Phone not recognised by umass as USB
	disk
Message-ID: <200807300910.m6U9A3B3042444@freefall.freebsd.org>

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

From: "Oleksii Krykun" <okrg@ukr.net>
To: bug-followup@FreeBSD.org,gemellus@sdf.lonestar.org
Cc:  
Subject: Re: usb/122992: MotoROKR Z6 Phone not recognised by umass as USB disk
Date: Wed, 30 Jul 2008 11:45:37 +0300

 I got the same problem under 7.0-RELEASE.
 
 From dmesg:
 
 Jul 30 08:53:26 kws kernel: usb0: <UHCI (generic) USB controller> on uhci0
 Jul 30 08:53:26 kws kernel: usb0: USB revision 1.0
 Jul 30 08:53:26 kws kernel: uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
 Jul 30 08:53:26 kws kernel: usb1: <UHCI (generic) USB controller> on uhci1
 Jul 30 08:53:26 kws kernel: usb1: USB revision 1.0
 Jul 30 08:53:26 kws kernel: uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
 Jul 30 08:53:26 kws kernel: usb2: <UHCI (generic) USB controller> on uhci2
 Jul 30 08:53:26 kws kernel: usb2: USB revision 1.0
 Jul 30 08:53:26 kws kernel: uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
 Jul 30 08:53:26 kws kernel: usb3: <UHCI (generic) USB controller> on uhci3
 Jul 30 08:53:26 kws kernel: usb3: USB revision 1.0
 Jul 30 08:53:26 kws kernel: uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
 Jul 30 08:53:26 kws kernel: usb4: EHCI version 1.0
 Jul 30 08:53:26 kws kernel: usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
 Jul 30 08:53:26 kws kernel: usb4: <Intel 82801GB/R (ICH7) USB 2.0 controller> on ehci0
 Jul 30 08:53:26 kws kernel: usb4: USB revision 2.0
 Jul 30 08:53:26 kws kernel: uhub4: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4
 
 After Z6 connecting I see following:
 
 ul 30 09:24:09 kws kernel: umass0: <Motorola Inc. MS, class 0/0, rev 2.00/1.01, addr 2> on uhub4
 Jul 30 09:24:09 kws kernel: umass0:0:0:-1: Attached to scbus0
 Jul 30 09:24:09 kws root: Unknown USB device: vendor 0x22b8 product 0x6426 bus uhub4
 
 kws# usbdevs -vd
 Controller /dev/usb0:
 addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
   uhub0
  port 1 powered
  port 2 powered
 Controller /dev/usb1:
 addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
   uhub1
  port 1 powered
  port 2 powered
 Controller /dev/usb2:
 addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
   uhub2
  port 1 powered
  port 2 powered
 Controller /dev/usb3:
 addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
   uhub3
  port 1 powered
  port 2 powered
 Controller /dev/usb4:
 addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00
   uhub4
  port 1 powered
  port 2 powered
  port 3 addr 2: high speed, power 500 mA, config 1, MS(0x6426), Motorola Inc.(0x22b8), rev 1.01
    umass0
  port 4 powered
  port 5 powered
  port 6 powered
  port 7 powered
  port 8 powered
 
 kws# camcontrol devlist -v
 scbus0 on umass-sim0 bus 0:
 
 So, umass0 line and scbus0 are attached but no daX devices.
 
 
From gavin at FreeBSD.org  Wed Jul 30 15:10:46 2008
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Wed Jul 30 15:10:57 2008
Subject: kern/126097: [uipaq] [patch] add support for ASUS P535 PDA
Message-ID: <200807301510.m6UFAjfw074859@freefall.freebsd.org>

Old Synopsis: uipaq support for ASUS P535 PDA
New Synopsis: [uipaq] [patch] add support for ASUS P535 PDA

Responsible-Changed-From-To: freebsd-i386->freebsd-usb
Responsible-Changed-By: gavin
Responsible-Changed-When: Wed Jul 30 15:08:39 UTC 2008
Responsible-Changed-Why: 
Over to maintainers

http://www.freebsd.org/cgi/query-pr.cgi?pr=126097
From remko at FreeBSD.org  Thu Jul 31 09:42:54 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Thu Jul 31 09:43:00 2008
Subject: kern/126097: [uipaq] [patch] add support for ASUS P535 PDA
Message-ID: <200807310942.m6V9gsTV017066@freefall.freebsd.org>

Synopsis: [uipaq] [patch] add support for ASUS P535 PDA

Responsible-Changed-From-To: freebsd-usb->remko
Responsible-Changed-By: remko
Responsible-Changed-When: Thu Jul 31 09:42:53 UTC 2008
Responsible-Changed-Why: 
I'll take it.

http://www.freebsd.org/cgi/query-pr.cgi?pr=126097