Re: USB changes
It did go somewhere; Julian altered two files in the relevant source and after I updated the issue was resolved. > 13. Re: USB changes. (Joel) > > Message: 13 > Date: Mon, 02 May 2005 12:20:30 +0900 > From: Joel <[EMAIL PROTECTED]> > Subject: Re: USB changes. > To: freebsd-stable@freebsd.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="ISO-2022-JP" > > > If I were Joe, I'd be wondering if that meant re-compiling the kernel. > > Did this go anywhere? (I also have UHB hardware that fusses on boot.) > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > End of freebsd-stable Digest, Vol 108, Issue 1 > ** -- I don't care what you think. This is not a stylishly insouciant stroll out of the jungle, here. It's more like we've fallen out of our trees and rolled, butt-naked before the entire galaxy, downhill. That, and we seem to have a teensy problem lifting ourselves off the ground. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
On Thu, 28 Apr 2005 13:51:37 -0700 (BJulian Elischer <[EMAIL PROTECTED]> wrote (B (B> (B> (B> Joe Altman wrote: (B> (B> >On Thu, Apr 28, 2005 at 01:40:50PM -0700, Julian Elischer wrote: (B> > (B> > (B> >>Since I can't make this happen here, I'm going to need help.. (B> >> (B> >> (B> > (B> >What do you need? Relatively speaking, I'm sort of a newbie at the (B> >more complex aspects of bugs, and this strikes me as somewhat complex. (B> > (B> >But if you are willing to tell me what you need, and how to proceed or (B> >what to read to help you, I'll do what I can. (B> > (B> > (B> (B> I asked you to add 2 lines to that file and try again. (B (BIf I were Joe, I'd be wondering if that meant re-compiling the kernel. (B (BDid this go anywhere? (I also have UHB hardware that fusses on boot.) (B (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc. $B3t<02qhttp://www.ddcom.co.jp> ** (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes
> -- > > Message: 9 > Date: Thu, 28 Apr 2005 11:23:14 -0700 > From: Julian Elischer <[EMAIL PROTECTED]> > Subject: Re: USB changes. > To: freebsd-stable@freebsd.org, Joe Altman <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii; format=flowed > > > > +++ > > > > Currently, I find my P4 hanging just after discovering the parallel > > port and mounting disk; in other words, just here: Julian has patched various aspects for the usb source; this has remedied the issue. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
Joe Altman wrote: On Thu, Apr 28, 2005 at 01:40:50PM -0700, Julian Elischer wrote: Since I can't make this happen here, I'm going to need help.. What do you need? Relatively speaking, I'm sort of a newbie at the more complex aspects of bugs, and this strikes me as somewhat complex. But if you are willing to tell me what you need, and how to proceed or what to read to help you, I'll do what I can. I asked you to add 2 lines to that file and try again. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
On Thu, Apr 28, 2005 at 01:40:50PM -0700, Julian Elischer wrote: > > Since I can't make this happen here, I'm going to need help.. What do you need? Relatively speaking, I'm sort of a newbie at the more complex aspects of bugs, and this strikes me as somewhat complex. But if you are willing to tell me what you need, and how to proceed or what to read to help you, I'll do what I can. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
Since I can't make this happen here, I'm going to need help..
Joe Altman wrote:
Apr 27 00:07 /usr/src/sys/dev/usb/usb.c
/* Explore USB busses at the end of device configuration. */
Static void
usb_cold_explore(void *arg)
{
struct usb_softc *sc;
can you add this line here:
printf("HEY WE GOT HERE!\n");
KASSERT(cold || TAILQ_EMPTY(&usb_coldexplist),
("usb_cold_explore: busses to explore when !cold"));
while (!TAILQ_EMPTY(&usb_coldexplist)) {
sc = TAILQ_FIRST(&usb_coldexplist);
TAILQ_REMOVE(&usb_coldexplist, sc, sc_coldexplist);
and:
printf("probing a USB 1.1 bus.\n");
sc->sc_bus->use_polling++;
sc->sc_port.device->hub->explore(sc->sc_bus->root_hub);
sc->sc_bus->use_polling--;
}
}
DRIVER_MODULE(usb, ohci, usb_driver, usb_devclass, 0, 0);
DRIVER_MODULE(usb, uhci, usb_driver, usb_devclass, 0, 0);
DRIVER_MODULE(usb, ehci, usb_driver, usb_devclass, 0, 0);
SYSINIT(usb_cold_explore, SI_SUB_INT_CONFIG_HOOKS, SI_ORDER_FIRST,
usb_cold_explore, NULL);
#endif
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
On Thu, Apr 28, 2005 at 01:23:25PM -0700, Julian Elischer wrote:
>
>
> Joe Altman wrote:
>
> >On Thu, Apr 28, 2005 at 12:55:31PM -0700, Julian Elischer wrote:
> >
> >
> Can you confirm that usb.c ends with:
> SYSINIT(usb_cold_explore, SI_SUB_INT_CONFIG_HOOKS, SI_ORDER_FIRST,
> usb_cold_explore, NULL);
>
>
> >>/usr/src/sys/dev/usb/usb.c
> >>
> >>
>
> ^^^
Oh; sorry...I must have gone cross-eyed.
Here is the tail of the file, with timestamp:
Apr 27 00:07 /usr/src/sys/dev/usb/usb.c
/* Explore USB busses at the end of device configuration. */
Static void
usb_cold_explore(void *arg)
{
struct usb_softc *sc;
KASSERT(cold || TAILQ_EMPTY(&usb_coldexplist),
("usb_cold_explore: busses to explore when !cold"));
while (!TAILQ_EMPTY(&usb_coldexplist)) {
sc = TAILQ_FIRST(&usb_coldexplist);
TAILQ_REMOVE(&usb_coldexplist, sc, sc_coldexplist);
sc->sc_bus->use_polling++;
sc->sc_port.device->hub->explore(sc->sc_bus->root_hub);
sc->sc_bus->use_polling--;
}
}
DRIVER_MODULE(usb, ohci, usb_driver, usb_devclass, 0, 0);
DRIVER_MODULE(usb, uhci, usb_driver, usb_devclass, 0, 0);
DRIVER_MODULE(usb, ehci, usb_driver, usb_devclass, 0, 0);
SYSINIT(usb_cold_explore, SI_SUB_INT_CONFIG_HOOKS, SI_ORDER_FIRST,
usb_cold_explore, NULL);
#endif
--
I don't care what you think. This is not a stylishly insouciant stroll
out of the jungle, here. It's more like we've fallen out of our trees
and rolled, butt-naked before the entire galaxy, downhill. That, and
we seem to have a teensy problem lifting ourselves off the ground.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
Joe Altman wrote: On Thu, Apr 28, 2005 at 12:55:31PM -0700, Julian Elischer wrote: Can you confirm that usb.c ends with: SYSINIT(usb_cold_explore, SI_SUB_INT_CONFIG_HOOKS, SI_ORDER_FIRST, usb_cold_explore, NULL); /usr/src/sys/dev/usb/usb.c ^^^ Where does the file that you need live? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
On Thu, Apr 28, 2005 at 12:55:31PM -0700, Julian Elischer wrote: > >> > >>Can you confirm that usb.c ends with: > >>SYSINIT(usb_cold_explore, SI_SUB_INT_CONFIG_HOOKS, SI_ORDER_FIRST, > >> usb_cold_explore, NULL); > > /usr/sr/sys/dev/usb/usb.c > > >Aha...maybe this is it: > > > >/usr/src/usr.sbin/usbd/ > > > > > > nope > > >ll /usr/src/usr.sbin/usbd/ > > > >2734320 -rw-r--r--1 root wheel169 Apr 25 2001 Makefile > >2738254 -rw-r--r--1 root wheel 4460 Jun 22 2003 usbd.8 > >2736938 -rw-r--r--1 root wheel 30079 Nov 29 2003 usbd.c > >2737339 -rw-r--r--1 root wheel 5046 Aug 27 2004 usbd.conf.5 > > > >Is that the one? Where does the file that you need live? > theoretically it may be that the usb code doesn't like being run at that > time.. > > I'll try duplicate your setup more closely. > > is it a uhci or ohci controller? >From dmesg: uhci0: port 0xbc00-0xbc1f irq 5 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb000-0xb01f irq 10 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xb400-0xb41f irq 11 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xb800-0xb81f irq 5 at device 29.3 on pci0 usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xfc00-0xfc0003ff irq 3 at device 29.7 on pci0 usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: single transaction translator uhub4: 8 ports with 8 removable, self powered So it's uhci and ehci. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
Joe Altman wrote: On Thu, Apr 28, 2005 at 11:23:14AM -0700, Julian Elischer wrote: [...] I assume it works right if you remove the mouse before booting and reinsert it after the kernel has booted? Yes; once I have a console, the mouse is detected: ums0: Logitech USB Receiver, rev 1.10/23.02, addr 2, iclass 3/1 ums0: 7 buttons and Z dir. Then, it works in X just fine; I forgot to test it on the console. seems to work for me with uhci too.. can you see if changing the BIOS usb optiosn makes a difference? [...] uhci0: port 0xe800-0xe81f irq 5 at device 29.0 o n pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xec00-0xec1f irq 9 at device 29.1 o n pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: (vendor=0x8086, dev=0x25ab) at 29.4 pci0: (vendor=0x8086, dev=0x25ac) at 29.5 ehci0: mem 0xfe7ffc00-0xfe7f irq 7 at de vice 29.7 on pci0 usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: single transaction translator uhub2: 4 ports with 4 removable, self powered [...] psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port not found. DUMMYNET initialized (011031) IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled IPsec: Initialized Security Association Processing. ad0: 114473MB [232581/16/63] at ata0-master UDMA100 ums0: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM), rev 1.10/3.00, add r 2, iclass 3/1 ums0: 3 buttons and Z dir. Mounting root from ufs:/dev/ad0s1a ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
Joe Altman wrote:
On Thu, Apr 28, 2005 at 11:23:14AM -0700, Julian Elischer wrote:
+++
Currently, I find my P4 hanging just after discovering the parallel
port and mounting disk; in other words, just here:
ppc0: parallel port not found.
ad0: 28629MB [58168/16/63] at ata0-master UDMA100
but ->only<- when my Logitech USB mouse is plugged in. Now, if I
unplug it and hit reset (not Ctrl-Alt-Del; the keyboard is frozen) the
system boots, and I can obtain X w/ a functional mouse. Yesterday, of
course, prior to the USB change the system did not hang.
I saw this problem in testing ad THOUGHT I had checked in the fix..
Can you confirm that usb.c ends with:
SYSINIT(usb_cold_explore, SI_SUB_INT_CONFIG_HOOKS, SI_ORDER_FIRST,
usb_cold_explore, NULL);
Hmmm...
/usr/src/lib/libusbhid/
Nope..
/usr/sr/sys/dev/usb/usb.c
Aha...maybe this is it:
/usr/src/usr.sbin/usbd/
nope
ll /usr/src/usr.sbin/usbd/
2734320 -rw-r--r--1 root wheel169 Apr 25 2001 Makefile
2738254 -rw-r--r--1 root wheel 4460 Jun 22 2003 usbd.8
2736938 -rw-r--r--1 root wheel 30079 Nov 29 2003 usbd.c
2737339 -rw-r--r--1 root wheel 5046 Aug 27 2004 usbd.conf.5
Is that the one?
Here is a part of 'tail -25' on the file, showing the bottom:
/* check the event queue */
if (handle_events && (FD_ISSET(fd, &r) || error == 0))
{
if (verbose >= 2)
printf("%s: processing event queue
%son %s\n",
__progname,
(error? "":"due to timeout "),
USBDEV);
process_event_queue(fd);
}
}
}
So no, this file doesn't end in what you ask; I can't see anywhere
else it might live; is there some other usbd.c you need?
I noticed that some code was changed in between my discovery of the
hanging and my attempt to fix it:
Apr 27 21:15 subr_bus.c
but this change, and the subsequent world update, did not solve the
issue of the hanging mouse.
the changes that you are refering to include some to defer probing of the
USB 1.1 busses untill after the USB2.0 busses have been configured.
Ah...okay; well, I was in the dark anyway, may as well whistle.
theoretically it may be that the usb code doesn't like being run at that
time..
I'll try duplicate your setup more closely.
is it a uhci or ohci controller?
I just realised I did most of my testing with ohci..
will hunt down a uhci machine to test with.
I'll see if I can duplicate yuor problem.. I tested with several USB 1.1
devices but a mounse was not amongst them.
Okay; it may be a one off, relative to me only, as I've seen no other
indications of issues. I am behind on my list reading, though.
I assume it works right if you remove the mouse before booting and reinsert
it after the kernel has booted?
Yes; once I have a console, the mouse is detected:
ums0: Logitech USB Receiver, rev 1.10/23.02, addr 2, iclass 3/1
ums0: 7 buttons and Z dir.
Then, it works in X just fine; I forgot to test it on the console.
shouldn't matter..
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
On Thu, Apr 28, 2005 at 11:23:14AM -0700, Julian Elischer wrote:
>
> >+++
> >
> >Currently, I find my P4 hanging just after discovering the parallel
> >port and mounting disk; in other words, just here:
> >
> >ppc0: parallel port not found.
> >ad0: 28629MB [58168/16/63] at ata0-master UDMA100
> >
> >but ->only<- when my Logitech USB mouse is plugged in. Now, if I
> >unplug it and hit reset (not Ctrl-Alt-Del; the keyboard is frozen) the
> >system boots, and I can obtain X w/ a functional mouse. Yesterday, of
> >course, prior to the USB change the system did not hang.
> >
>
> I saw this problem in testing ad THOUGHT I had checked in the fix..
>
> Can you confirm that usb.c ends with:
> SYSINIT(usb_cold_explore, SI_SUB_INT_CONFIG_HOOKS, SI_ORDER_FIRST,
>usb_cold_explore, NULL);
Hmmm...
/usr/src/lib/libusbhid/
Nope..
Aha...maybe this is it:
/usr/src/usr.sbin/usbd/
ll /usr/src/usr.sbin/usbd/
2734320 -rw-r--r--1 root wheel169 Apr 25 2001 Makefile
2738254 -rw-r--r--1 root wheel 4460 Jun 22 2003 usbd.8
2736938 -rw-r--r--1 root wheel 30079 Nov 29 2003 usbd.c
2737339 -rw-r--r--1 root wheel 5046 Aug 27 2004 usbd.conf.5
Is that the one?
Here is a part of 'tail -25' on the file, showing the bottom:
/* check the event queue */
if (handle_events && (FD_ISSET(fd, &r) || error == 0))
{
if (verbose >= 2)
printf("%s: processing event queue
%son %s\n",
__progname,
(error? "":"due to timeout "),
USBDEV);
process_event_queue(fd);
}
}
}
So no, this file doesn't end in what you ask; I can't see anywhere
else it might live; is there some other usbd.c you need?
> >I noticed that some code was changed in between my discovery of the
> >hanging and my attempt to fix it:
> >
> >Apr 27 21:15 subr_bus.c
> >
> >but this change, and the subsequent world update, did not solve the
> >issue of the hanging mouse.
>
> the changes that you are refering to include some to defer probing of the
> USB 1.1 busses untill after the USB2.0 busses have been configured.
Ah...okay; well, I was in the dark anyway, may as well whistle.
> I'll see if I can duplicate yuor problem.. I tested with several USB 1.1
> devices but a mounse was not amongst them.
Okay; it may be a one off, relative to me only, as I've seen no other
indications of issues. I am behind on my list reading, though.
> I assume it works right if you remove the mouse before booting and reinsert
> it after the kernel has booted?
Yes; once I have a console, the mouse is detected:
ums0: Logitech USB Receiver, rev 1.10/23.02, addr 2, iclass 3/1
ums0: 7 buttons and Z dir.
Then, it works in X just fine; I forgot to test it on the console.
--
I don't care what you think. This is not a stylishly insouciant stroll
out of the jungle, here. It's more like we've fallen out of our trees
and rolled, butt-naked before the entire galaxy, downhill. That, and
we seem to have a teensy problem lifting ourselves off the ground.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
Julian Elischer wrote: +++ Currently, I find my P4 hanging just after discovering the parallel port and mounting disk; in other words, just here: but ->only<- when my Logitech USB mouse is plugged in. Now, if I unplug it and hit reset (not Ctrl-Alt-Del; the keyboard is frozen) the system boots, and I can obtain X w/ a functional mouse. Yesterday, of course, prior to the USB change the system did not hang. try plugging the mouse in again before X starts. I saw this problem in testing ad THOUGHT I had checked in the fix.. Can you confirm that usb.c ends with: SYSINIT(usb_cold_explore, SI_SUB_INT_CONFIG_HOOKS, SI_ORDER_FIRST, usb_cold_explore, NULL); I noticed that some code was changed in between my discovery of the hanging and my attempt to fix it: Apr 27 21:15 subr_bus.c but this change, and the subsequent world update, did not solve the issue of the hanging mouse. the changes that you are refering to include some to defer probing of the USB 1.1 busses untill after the USB2.0 busses have been configured. They should probe for the devices at around the same time that the scsi devices probe. I'll see if I can duplicate yuor problem.. I tested with several USB 1.1 devices but a mounse was not amongst them. I tried to duplicate this but failed.. my mose was found just fine.. can you boot with the -v option? i.e. "boot -v" fromt eh loader prompt. See, I know I've only myself to blame for missing the announcement and/or starting an upgrade in an interstice between stability and apparent instability. But still...test first, deploy later, perhaps? Kernel bits, had them for a couple of years now: device uhci device ohci device ehci device usb device ugen device ums device uscanner With my luck, it's probably not the mouse after all. what about if you don't have the ums driver loaded? I assume it works right if you remove the mouse before booting and reinsert it after the kernel has booted? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
+++ Currently, I find my P4 hanging just after discovering the parallel port and mounting disk; in other words, just here: ppc0: parallel port not found. ad0: 28629MB [58168/16/63] at ata0-master UDMA100 but ->only<- when my Logitech USB mouse is plugged in. Now, if I unplug it and hit reset (not Ctrl-Alt-Del; the keyboard is frozen) the system boots, and I can obtain X w/ a functional mouse. Yesterday, of course, prior to the USB change the system did not hang. I saw this problem in testing ad THOUGHT I had checked in the fix.. Can you confirm that usb.c ends with: SYSINIT(usb_cold_explore, SI_SUB_INT_CONFIG_HOOKS, SI_ORDER_FIRST, usb_cold_explore, NULL); I noticed that some code was changed in between my discovery of the hanging and my attempt to fix it: Apr 27 21:15 subr_bus.c but this change, and the subsequent world update, did not solve the issue of the hanging mouse. the changes that you are refering to include some to defer probing of the USB 1.1 busses untill after the USB2.0 busses have been configured. They should probe for the devices at around the same time that the scsi devices probe. I'll see if I can duplicate yuor problem.. I tested with several USB 1.1 devices but a mounse was not amongst them. See, I know I've only myself to blame for missing the announcement and/or starting an upgrade in an interstice between stability and apparent instability. But still...test first, deploy later, perhaps? Kernel bits, had them for a couple of years now: device uhci device ohci device ehci device usb device ugen device ums device uscanner With my luck, it's probably not the mouse after all. I assume it works right if you remove the mouse before booting and reinsert it after the kernel has booted? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
