Re: 2.2.18pre16 and USB_UHCI_ALT
On Thu, Oct 19, 2000 at 09:44:48AM -0700, David Rees wrote: > > These messages don't happen with the uhci.c ALT driver and USB works > great. Well, then I'd suggest just sticking with the uhci.c driver :) Seriously, I have no idea of what's wrong. greg k-h -- greg@(kroah|wirex).com http://immunix.org/~greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Wed, Oct 18, 2000 at 11:02:27PM -0700, Greg KH wrote: > > > I'll give the usb-uhci driver in 2.2.18pre17 another shot tonight. > > Let me know how it goes. Same thing. Now I only have my Intellimouse plugged into the USB port. The messages seem to start appearing when gpm starts up... Oct 19 09:07:54 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 19 09:07:54 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 901 Oct 19 09:07:54 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 19 09:07:54 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:2.0 Oct 19 09:07:54 spoke kernel: hub.c: already running port 1 disabled by hub (EMI?), re-enabling... Oct 19 09:07:54 spoke kernel: usb.c: USB disconnect on device 2 Oct 19 09:07:54 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 19 09:07:54 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1244 Oct 19 09:07:54 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 19 09:07:54 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:2.0 Oct 19 09:07:54 spoke kernel: hub.c: already running port 1 disabled by hub (EMI?), re-enabling... Oct 19 09:07:54 spoke kernel: usb.c: USB disconnect on device 2 Oct 19 09:07:54 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 19 09:07:54 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1757 Oct 19 09:07:54 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 19 09:07:54 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:2.0 Oct 19 09:07:54 spoke kernel: usb.c: USB new device connect, assigned device number 3 Oct 19 09:07:54 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 49 Oct 19 09:07:54 spoke kernel: mouse1: PS/2 mouse device for input1 Oct 19 09:07:54 spoke kernel: input1: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:3.0 Oct 19 09:07:58 spoke gpm: gpm startup succeeded Oct 19 09:07:58 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 860 Oct 19 09:07:58 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 884 Oct 19 09:07:58 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 908 Oct 19 09:07:58 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 932 Oct 19 09:07:59 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 956 Oct 19 09:07:59 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 980 These messages don't happen with the uhci.c ALT driver and USB works great. -Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Wed, Oct 18, 2000 at 11:02:27PM -0700, Greg KH wrote: I'll give the usb-uhci driver in 2.2.18pre17 another shot tonight. Let me know how it goes. Same thing. Now I only have my Intellimouse plugged into the USB port. The messages seem to start appearing when gpm starts up... Oct 19 09:07:54 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 19 09:07:54 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 901 Oct 19 09:07:54 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 19 09:07:54 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:2.0 Oct 19 09:07:54 spoke kernel: hub.c: already running port 1 disabled by hub (EMI?), re-enabling... Oct 19 09:07:54 spoke kernel: usb.c: USB disconnect on device 2 Oct 19 09:07:54 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 19 09:07:54 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1244 Oct 19 09:07:54 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 19 09:07:54 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:2.0 Oct 19 09:07:54 spoke kernel: hub.c: already running port 1 disabled by hub (EMI?), re-enabling... Oct 19 09:07:54 spoke kernel: usb.c: USB disconnect on device 2 Oct 19 09:07:54 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 19 09:07:54 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1757 Oct 19 09:07:54 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 19 09:07:54 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:2.0 Oct 19 09:07:54 spoke kernel: usb.c: USB new device connect, assigned device number 3 Oct 19 09:07:54 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 49 Oct 19 09:07:54 spoke kernel: mouse1: PS/2 mouse device for input1 Oct 19 09:07:54 spoke kernel: input1: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:3.0 snip Oct 19 09:07:58 spoke gpm: gpm startup succeeded Oct 19 09:07:58 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 860 Oct 19 09:07:58 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 884 Oct 19 09:07:58 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 908 Oct 19 09:07:58 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 932 Oct 19 09:07:59 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 956 Oct 19 09:07:59 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 980 These messages don't happen with the uhci.c ALT driver and USB works great. -Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Thu, Oct 19, 2000 at 09:44:48AM -0700, David Rees wrote: These messages don't happen with the uhci.c ALT driver and USB works great. Well, then I'd suggest just sticking with the uhci.c driver :) Seriously, I have no idea of what's wrong. greg k-h -- greg@(kroah|wirex).com http://immunix.org/~greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Wed, Oct 18, 2000 at 11:02:27PM -0700, Greg KH wrote: > On Wed, Oct 18, 2000 at 10:47:16PM -0700, David Rees wrote: > > > > This is on a Tyan Trinity 1598 Socket 7 motherboard. No hubs of any sort. > > No external hubs? Then why is the hub driver seeing both a 2 port root > hub, and a 4 port "normal" hub? Does this motherboard have more than 2 > external USB connectors on it? > > Odd. Well, according to /proc/pci there's two USB controllers: Bus 0, device 7, function 2: USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 6). Medium devsel. IRQ 10. Master Capable. Latency=32. I/O at 0xd400 [0xd401]. Bus 0, device 7, function 3: USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 6). Medium devsel. IRQ 10. Master Capable. Latency=32. I/O at 0xd800 [0xd801]. -Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Wed, Oct 18, 2000 at 10:47:16PM -0700, David Rees wrote: > > This is on a Tyan Trinity 1598 Socket 7 motherboard. No hubs of any sort. No external hubs? Then why is the hub driver seeing both a 2 port root hub, and a 4 port "normal" hub? Does this motherboard have more than 2 external USB connectors on it? Odd. > I'll give the usb-uhci driver in 2.2.18pre17 another shot tonight. Let me know how it goes. greg k-h -- greg@(kroah|wirex).com http://immunix.org/~greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Wed, Oct 18, 2000 at 10:51:05PM -0700, Greg KH wrote: > On Wed, Oct 18, 2000 at 08:21:53AM -0700, David Rees wrote: > > > > Nothing else odd changed. Here's the boot sequence and messages which > > repeated endlessly after booting 2.2.18pre16 with the usb-uhci driver: > > This kinda looks like you have a flaky hub. It is a self powered hub? > If so, try making it a external powered hub if you can. > Or is this the root hub on a laptop? This is on a Tyan Trinity 1598 Socket 7 motherboard. No hubs of any sort. I'll give the usb-uhci driver in 2.2.18pre17 another shot tonight. -Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Wed, Oct 18, 2000 at 08:21:53AM -0700, David Rees wrote: > > Nothing else odd changed. Here's the boot sequence and messages which > repeated endlessly after booting 2.2.18pre16 with the usb-uhci driver: This kinda looks like you have a flaky hub. It is a self powered hub? If so, try making it a external powered hub if you can. Or is this the root hub on a laptop? thanks, greg k-h -- greg@(kroah|wirex).com http://immunix.org/~greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Tue, Oct 17, 2000 at 01:46:46PM -0700, Greg KH wrote: > On Mon, Oct 16, 2000 at 10:49:56PM -0700, David Rees wrote: > > > > Well, the real interesting part is that I was using the usb-uhci.c driver > > in 2.2.18pre15, and now in 2.2.18pre16 it stopped working for my mouse > > with no apparent change to either of the uhci drivers. > > Kernel debug messages? > Anything else odd change? Nothing else odd changed. Here's the boot sequence and messages which repeated endlessly after booting 2.2.18pre16 with the usb-uhci driver: Oct 15 23:35:12 spoke kernel: usb.c: registered new driver hid Oct 15 23:35:12 spoke kernel: mice: PS/2 mouse device common for all mice Oct 15 23:35:12 spoke kernel: usb.c: registered new driver hub Oct 15 23:35:12 spoke kernel: usb-uhci.c: $Revision: 1.237 $ time 23:19:11 Oct 15 2000 Oct 15 23:35:12 spoke kernel: usb-uhci.c: High bandwidth mode enabled Oct 15 23:35:12 spoke kernel: usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10 Oct 15 23:35:12 spoke kernel: usb-uhci.c: Detected 2 ports Oct 15 23:35:12 spoke kernel: usb.c: new USB bus registered, assigned bus number 1 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 1 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 2 ports detected Oct 15 23:35:12 spoke kernel: usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 10 Oct 15 23:35:12 spoke kernel: usb-uhci.c: Detected 2 ports Oct 15 23:35:12 spoke kernel: usb.c: new USB bus registered, assigned bus number 2 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 1 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 2 ports detected Oct 15 23:35:12 spoke kernel: VFS: Mounted root (ext2 filesystem) readonly. Oct 15 23:35:12 spoke kernel: Freeing unused kernel memory: 48k freed Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 4 ports detected Oct 15 23:35:12 spoke kernel: hub.c: already running port 1 disabled by hub (EMI?), re-enabling... Oct 15 23:35:12 spoke kernel: usb.c: USB disconnect on device 2 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 4 ports detected Oct 15 23:35:12 spoke kernel: hub.c: already running port 1 disabled by hub (EMI?), re-enabling... Oct 15 23:35:12 spoke kernel: usb.c: USB disconnect on device 2 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 4 ports detected Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 3 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 4 ports detected Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1984 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 320 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 4 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 479 Oct 15 23:35:12 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 15 23:35:12 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:4.0 Oct 15 23:35:12 spoke kernel: hub.c: already running port 2 disabled by hub (EMI?), re-enabling... Oct 15 23:35:12 spoke kernel: usb.c: USB disconnect on device 4 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 704 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 4 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1029 Oct 15 23:35:12 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 15 23:35:12 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:4.0 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1088 Oct 15 23:35:12 spoke kernel: usb.c: USB disconnect on device 4 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 4 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1359 Oct 15 23:35:12 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 15 23:35:12 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:4.0 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1472 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1856 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 5 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1948 Oct 15 23:35:12 spoke kernel: mouse1: PS/2 mouse device for input1 Oct 15 23:35:12 spoke kernel: input1: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:5.0 Oct 15
Re: 2.2.18pre16 and USB_UHCI_ALT
On Tue, Oct 17, 2000 at 01:46:46PM -0700, Greg KH wrote: On Mon, Oct 16, 2000 at 10:49:56PM -0700, David Rees wrote: Well, the real interesting part is that I was using the usb-uhci.c driver in 2.2.18pre15, and now in 2.2.18pre16 it stopped working for my mouse with no apparent change to either of the uhci drivers. Kernel debug messages? Anything else odd change? Nothing else odd changed. Here's the boot sequence and messages which repeated endlessly after booting 2.2.18pre16 with the usb-uhci driver: Oct 15 23:35:12 spoke kernel: usb.c: registered new driver hid Oct 15 23:35:12 spoke kernel: mice: PS/2 mouse device common for all mice Oct 15 23:35:12 spoke kernel: usb.c: registered new driver hub Oct 15 23:35:12 spoke kernel: usb-uhci.c: $Revision: 1.237 $ time 23:19:11 Oct 15 2000 Oct 15 23:35:12 spoke kernel: usb-uhci.c: High bandwidth mode enabled Oct 15 23:35:12 spoke kernel: usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10 Oct 15 23:35:12 spoke kernel: usb-uhci.c: Detected 2 ports Oct 15 23:35:12 spoke kernel: usb.c: new USB bus registered, assigned bus number 1 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 1 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 2 ports detected Oct 15 23:35:12 spoke kernel: usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 10 Oct 15 23:35:12 spoke kernel: usb-uhci.c: Detected 2 ports Oct 15 23:35:12 spoke kernel: usb.c: new USB bus registered, assigned bus number 2 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 1 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 2 ports detected Oct 15 23:35:12 spoke kernel: VFS: Mounted root (ext2 filesystem) readonly. Oct 15 23:35:12 spoke kernel: Freeing unused kernel memory: 48k freed Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 4 ports detected Oct 15 23:35:12 spoke kernel: hub.c: already running port 1 disabled by hub (EMI?), re-enabling... Oct 15 23:35:12 spoke kernel: usb.c: USB disconnect on device 2 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 4 ports detected Oct 15 23:35:12 spoke kernel: hub.c: already running port 1 disabled by hub (EMI?), re-enabling... Oct 15 23:35:12 spoke kernel: usb.c: USB disconnect on device 2 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 2 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 4 ports detected Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 3 Oct 15 23:35:12 spoke kernel: hub.c: USB hub found Oct 15 23:35:12 spoke kernel: hub.c: 4 ports detected Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1984 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 320 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 4 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 479 Oct 15 23:35:12 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 15 23:35:12 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:4.0 Oct 15 23:35:12 spoke kernel: hub.c: already running port 2 disabled by hub (EMI?), re-enabling... Oct 15 23:35:12 spoke kernel: usb.c: USB disconnect on device 4 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 704 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 4 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1029 Oct 15 23:35:12 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 15 23:35:12 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:4.0 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1088 Oct 15 23:35:12 spoke kernel: usb.c: USB disconnect on device 4 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 4 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1359 Oct 15 23:35:12 spoke kernel: mouse0: PS/2 mouse device for input0 Oct 15 23:35:12 spoke kernel: input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:4.0 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1472 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1856 Oct 15 23:35:12 spoke kernel: usb.c: USB new device connect, assigned device number 5 Oct 15 23:35:12 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 1948 Oct 15 23:35:12 spoke kernel: mouse1: PS/2 mouse device for input1 Oct 15 23:35:12 spoke kernel: input1: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:5.0 Oct 15 23:35:12 spoke
Re: 2.2.18pre16 and USB_UHCI_ALT
On Wed, Oct 18, 2000 at 08:21:53AM -0700, David Rees wrote: Nothing else odd changed. Here's the boot sequence and messages which repeated endlessly after booting 2.2.18pre16 with the usb-uhci driver: This kinda looks like you have a flaky hub. It is a self powered hub? If so, try making it a external powered hub if you can. Or is this the root hub on a laptop? thanks, greg k-h -- greg@(kroah|wirex).com http://immunix.org/~greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Wed, Oct 18, 2000 at 10:51:05PM -0700, Greg KH wrote: On Wed, Oct 18, 2000 at 08:21:53AM -0700, David Rees wrote: Nothing else odd changed. Here's the boot sequence and messages which repeated endlessly after booting 2.2.18pre16 with the usb-uhci driver: This kinda looks like you have a flaky hub. It is a self powered hub? If so, try making it a external powered hub if you can. Or is this the root hub on a laptop? This is on a Tyan Trinity 1598 Socket 7 motherboard. No hubs of any sort. I'll give the usb-uhci driver in 2.2.18pre17 another shot tonight. -Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Wed, Oct 18, 2000 at 10:47:16PM -0700, David Rees wrote: This is on a Tyan Trinity 1598 Socket 7 motherboard. No hubs of any sort. No external hubs? Then why is the hub driver seeing both a 2 port root hub, and a 4 port "normal" hub? Does this motherboard have more than 2 external USB connectors on it? Odd. I'll give the usb-uhci driver in 2.2.18pre17 another shot tonight. Let me know how it goes. greg k-h -- greg@(kroah|wirex).com http://immunix.org/~greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Mon, Oct 16, 2000 at 10:49:56PM -0700, David Rees wrote: > > Well, the real interesting part is that I was using the usb-uhci.c driver > in 2.2.18pre15, and now in 2.2.18pre16 it stopped working for my mouse > with no apparent change to either of the uhci drivers. Kernel debug messages? Anything else odd change? thanks, greg k-h -- greg@(kroah|wirex).com http://immunix.org/~greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Mon, Oct 16, 2000 at 10:49:56PM -0700, David Rees wrote: Well, the real interesting part is that I was using the usb-uhci.c driver in 2.2.18pre15, and now in 2.2.18pre16 it stopped working for my mouse with no apparent change to either of the uhci drivers. Kernel debug messages? Anything else odd change? thanks, greg k-h -- greg@(kroah|wirex).com http://immunix.org/~greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Mon, Oct 16, 2000 at 01:32:01PM -0400, Johannes Erdfelt wrote: > On Mon, Oct 16, 2000, David Rees <[EMAIL PROTECTED]> wrote: > > In 2.2.18pre16 an alternative USB_UHCI driver under the option > > CONFIG_USB_UHCI_ALT was added. Only this one works for me, and > > CONFIG_USB_UHCI throws up 50 messages a second like this one: > > > > Oct 16 00:12:22 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 188 > > > > and leaves my mouse in an unusable state. > > > > This is on a VIA Technologies VT 82C586 Apollo USB (rev 6). I have two > > USB devices connected to it: > > Microsoft Microsoft IntelliMouse® Optical > > Microsoft Natural Keyboard Pro > > > > What is supposed to be the difference between the two drivers, anyway? It > > is not clear from the docs what is different besides the fact that they > > are different. > > Just that. It's an alternative implementation. It's a long story why > there's 2 drivers for the same device, and you can check the USB > archives to learn the whole story. > > The short of it is that I didn't like the usb-uhci.c driver so I wrote a > different one. It looks like it was worth the effort since it works for > you whereas usb-uhci.c doesn't. > > I'm sure the usb-uhci.c guys will be interested to follow up with you > about the problems you are seeing. Well, the real interesting part is that I was using the usb-uhci.c driver in 2.2.18pre15, and now in 2.2.18pre16 it stopped working for my mouse with no apparent change to either of the uhci drivers. -Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Mon, Oct 16, 2000, David Rees <[EMAIL PROTECTED]> wrote: > In 2.2.18pre16 an alternative USB_UHCI driver under the option > CONFIG_USB_UHCI_ALT was added. Only this one works for me, and > CONFIG_USB_UHCI throws up 50 messages a second like this one: > > Oct 16 00:12:22 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 188 > > and leaves my mouse in an unusable state. > > This is on a VIA Technologies VT 82C586 Apollo USB (rev 6). I have two > USB devices connected to it: > Microsoft Microsoft IntelliMouse® Optical > Microsoft Natural Keyboard Pro > > What is supposed to be the difference between the two drivers, anyway? It > is not clear from the docs what is different besides the fact that they > are different. Just that. It's an alternative implementation. It's a long story why there's 2 drivers for the same device, and you can check the USB archives to learn the whole story. The short of it is that I didn't like the usb-uhci.c driver so I wrote a different one. It looks like it was worth the effort since it works for you whereas usb-uhci.c doesn't. I'm sure the usb-uhci.c guys will be interested to follow up with you about the problems you are seeing. JE - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
2.2.18pre16 and USB_UHCI_ALT
In 2.2.18pre16 an alternative USB_UHCI driver under the option CONFIG_USB_UHCI_ALT was added. Only this one works for me, and CONFIG_USB_UHCI throws up 50 messages a second like this one: Oct 16 00:12:22 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 188 and leaves my mouse in an unusable state. This is on a VIA Technologies VT 82C586 Apollo USB (rev 6). I have two USB devices connected to it: Microsoft Microsoft IntelliMouse® Optical Microsoft Natural Keyboard Pro What is supposed to be the difference between the two drivers, anyway? It is not clear from the docs what is different besides the fact that they are different. -Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
2.2.18pre16 and USB_UHCI_ALT
In 2.2.18pre16 an alternative USB_UHCI driver under the option CONFIG_USB_UHCI_ALT was added. Only this one works for me, and CONFIG_USB_UHCI throws up 50 messages a second like this one: Oct 16 00:12:22 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 188 and leaves my mouse in an unusable state. This is on a VIA Technologies VT 82C586 Apollo USB (rev 6). I have two USB devices connected to it: Microsoft Microsoft IntelliMouse® Optical Microsoft Natural Keyboard Pro What is supposed to be the difference between the two drivers, anyway? It is not clear from the docs what is different besides the fact that they are different. -Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.18pre16 and USB_UHCI_ALT
On Mon, Oct 16, 2000, David Rees [EMAIL PROTECTED] wrote: In 2.2.18pre16 an alternative USB_UHCI driver under the option CONFIG_USB_UHCI_ALT was added. Only this one works for me, and CONFIG_USB_UHCI throws up 50 messages a second like this one: Oct 16 00:12:22 spoke kernel: usb-uhci.c: interrupt, status 3, frame# 188 and leaves my mouse in an unusable state. This is on a VIA Technologies VT 82C586 Apollo USB (rev 6). I have two USB devices connected to it: Microsoft Microsoft IntelliMouse® Optical Microsoft Natural Keyboard Pro What is supposed to be the difference between the two drivers, anyway? It is not clear from the docs what is different besides the fact that they are different. Just that. It's an alternative implementation. It's a long story why there's 2 drivers for the same device, and you can check the USB archives to learn the whole story. The short of it is that I didn't like the usb-uhci.c driver so I wrote a different one. It looks like it was worth the effort since it works for you whereas usb-uhci.c doesn't. I'm sure the usb-uhci.c guys will be interested to follow up with you about the problems you are seeing. JE - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
