> +++ > > 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 <ST330620A> [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?> >
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? >
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 <ST330620A> [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 wheel 169 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.
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: <UHCI (generic) USB controller> port 0xe800-0xe81f irq 5 at device 29.0 o n 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 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: <UHCI (generic) USB controller> port 0xec00-0xec1f irq 9 at device 29.1 o n 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 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: <unknown card> (vendor=0x8086, dev=0x25ab) at 29.4 pci0: <unknown card> (vendor=0x8086, dev=0x25ac) at 29.5 ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfe7ffc00-0xfe7fffff irq 7 at de vice 29.7 on pci0 usb2: EHCI version 1.0 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 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: <PS/2 Mouse> irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: <System console> 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 <ST3120026A> [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