Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks.

On Friday 26 December 2008 11:14:15 Renato Botelho wrote:
> On Wed, Dec 24, 2008 at 4:58 PM, Renato Botelho <rbgarga_at_gmail.com> wrote:
> > On Wed, Dec 24, 2008 at 9:12 AM, Hans Petter Selasky <hselasky_at_c2i.net> 
wrote:
> >> On Wednesday 24 December 2008, Renato Botelho wrote:
> >>> On Mon, Dec 22, 2008 at 7:40 PM, Alfred Perlstein <alfred_at_freebsd.org>
> >>
> >> wrote:
> >>> > We're going to usher in the New Year with a new usb stack.
> >>> >
> >>> > Now is the time to test, test, test.
> >>> >
> >>> > It is also the time to point out anything missing from usb2 that
> >>> > is in usb1.
> >>> >
> >>> > In two weeks, on Jan 3rd I will switch the GENERIC kernel to use
> >>> > usb2.
> >>> >
> >>> > The old usb code will remain in case there is any fallout.
> >>> >
> >>> > Depending on how this trial goes we will hopefully move to the new
> >>> > stack entirely within a few weeks after bug reports start dying
> >>> > down.
> >>>
> >>> Alfred,
> >>>
> >>> I tried a build yesterday with a fresh -current (Revision: 186431),
> >>> after boot I couldn't have my usb keyboard (Sun Type 7 Unix) working.
> >>>
> >>> I've collected these lines from messages, and i would like to know
> >>> what i can do to give you necessary information to fix this.
> >>>
> >>> Dec 23 14:48:35 botelhor kernel: Trying to mount root from
> >>> ufs:/dev/ad4s1a Dec 23 14:48:35 botelhor kernel:
> >>> usb2_alloc_device:1417: set address 2 failed (ignored)
> >>> Dec 23 14:48:35 botelhor kernel: usb2_alloc_device:1452: getting
> >>> device descriptor at addr 2 failed!
> >>> Dec 23 14:48:35 botelhor kernel: uhub_reattach_port:401: could not
> >>> allocate new device!
> >>> Dec 23 14:48:39 botelhor lpd[1090]: lpd startup: logging=0
> >>> Dec 23 14:48:40 botelhor kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI
> >>> 7.8 Dec 23 14:48:40 botelhor kernel: fuse4bsd: compiled against kernel
> >>> config /usr/obj/usr/src/sys/GARGA
> >>> Dec 23 14:49:05 botelhor kernel: usb2_alloc_device:1417: set address 2
> >>> failed (ignored)
> >>> Dec 23 14:49:05 botelhor kernel: usb2_alloc_device:1452: getting
> >>> device descriptor at addr 2 failed!
> >>> Dec 23 14:49:05 botelhor kernel: uhub_reattach_port:401: could not
> >>> allocate new device!
> >>>
> >>> Here is the same lines with current usb stack:
> >>>
> >>> Dec 23 14:52:23 botelhor kernel: uhub5: <vendor 0x0430 product 0x100e,
> >>> class 9/0, rev 2.00/1.04, addr 2> on uhub3
> >>> Dec 23 14:52:23 botelhor kernel: uhub5: 4 ports with 3 removable, bus
> >>> powered Dec 23 14:52:23 botelhor kernel: ums0: <vendor 0x0566 USB
> >>> Mouse, class 0/0, rev 1.10/51.27, addr 3> on uhub5
> >>> Dec 23 14:52:23 botelhor kernel: ums0: 3 buttons and Z dir.
> >>> Dec 23 14:52:23 botelhor kernel: ukbd0: <vendor 0x0430 Sun USB
> >>> Keyboard, class 0/0, rev 2.00/1.04, addr 4> on uhub5
> >>> Dec 23 14:52:23 botelhor kernel: kbd2 at ukbd0
> >>>
> >>> Thanks
> >>
> >> Hi,
> >>
> >> I have made some patches for this kind of issues which are not yet
> >> in -current.
> >>
> >> You can try to fetch the latest from:
> >>
> >> svn --username anonsvn --password anonsvn \
> >>      checkout svn://svn.turbocat.net/i4b
> >>
> >> cd i4b/trunk/i4b/src/sys/dev
> >> cp -r usb2 /sys/dev/
> >> make -C /sys/modules/usb2 clean all install
> >
> > I still had problems, I'll collect more details on Friday and
> > send you.
>
> Here are my /var/log/messages:
>
> http://pastebin.com/f6c28d7ca
>
> I still have problems with my keyboard.

I dont know if this will be of any help to you, but I have had similar 
problems on my machine (I use a Sun Type 6 keyboard). 

Its a once in a blue moon fault where the keyboard comes up unresponsive after 
reboot, and reboots and power-cycles to the machine dont help. What I found on 
mine is that I have to physically unplug the keyboard after a power down, and 
replug it back in. I think something gets stuck in the keyboard and even with 
the power off to the machine, the 5V stand-by is being applied, so the 
keyboard never gets reset. 

When this fault occurs, the keyboard is even unresponsive during POST and will 
not recognize the delete key to get into bios, etc. 

It has only happened maybe 5 or 6 times out of the many reboots on my machine, 
but what normally seems to kick it off is if I do a shutdown -r from within a 
xterm. 

Just my $0.02, 
Peg