* USB stops working with any of 2.4.22-pre's after 2.4.21
@ 2003-07-10 6:58 John Wong
2003-07-10 7:06 ` John Wong
2003-07-10 17:02 ` Greg KH
0 siblings, 2 replies; 10+ messages in thread
From: John Wong @ 2003-07-10 6:58 UTC (permalink / raw)
To: linux-kernel
On any of the 2.4.22-pre's, after a bit of time, my USB mouse stops
responding. It is using the usb-ohci driver. 2.4.22-pre1 included the
new ACPI base. Even before this ACPI was merged into mainstream, I had
tried patching the system with the newer ACPI on 2.4.21-pre, and rc's
and I also ran into the same problem that I am now getting with
2.4.22-pre's. I'm suspecting the new ACPI is behind this. Stopping gpm
and removing usb-ohci and then reloading it doesn't seem to get it
working again. A reboot does the trick. Strange though is that the one
USB 2.0 device I have plugged in still continues to work (at least for a
while as I normally reboot when the problem arises) when I start having
the problems with USB mouse. But then, it uses the ehci-hcd driver.
Some hardware info. I'm using a nForce2 board with an ATI Radeon video
card.
Jul 9 23:39:29 gambit kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 9 23:39:29 gambit kernel: eth0: transmit timed out, tx_status 00
status e601.
Jul 9 23:39:29 gambit kernel: diagnostics: net 0cc0 media 8080 dma
0000003a.
Jul 9 23:39:29 gambit kernel: eth0: Interrupt posted but not delivered
-- IRQ blocked by another device?
Jul 9 23:39:29 gambit kernel: Flags; bus-master 1, dirty 5538(2)
current 5538(2)
Jul 9 23:39:29 gambit kernel: Transmit list 00000000 vs. f7c40280.
Jul 9 23:39:29 gambit kernel: 0: @f7c40200 length 80000036 status
80010036
Jul 9 23:39:29 gambit kernel: 1: @f7c40240 length 80000036 status
80010036
Jul 9 23:39:29 gambit kernel: 2: @f7c40280 length 80000042 status
00010042
Jul 9 23:39:29 gambit kernel: 3: @f7c402c0 length 8000004a status
0001004a
Jul 9 23:39:29 gambit kernel: 4: @f7c40300 length 800005ea status
000105ea
Jul 9 23:39:29 gambit kernel: 5: @f7c40340 length 800001be status
000101be
Jul 9 23:39:29 gambit kernel: 6: @f7c40380 length 800005ea status
000105ea
Jul 9 23:39:29 gambit kernel: 7: @f7c403c0 length 800001be status
000101be
Jul 9 23:39:29 gambit kernel: 8: @f7c40400 length 800001be status
000101be
Jul 9 23:39:29 gambit kernel: 9: @f7c40440 length 800005ea status
000105ea
Jul 9 23:39:29 gambit kernel: 10: @f7c40480 length 8000004a status
0001004a
Jul 9 23:39:29 gambit kernel: 11: @f7c404c0 length 80000187 status
00010187
Jul 9 23:39:29 gambit kernel: 12: @f7c40500 length 8000004a status
0001004a
Jul 9 23:39:29 gambit kernel: 13: @f7c40540 length 80000042 status
00010042
Jul 9 23:39:29 gambit kernel: 14: @f7c40580 length 8000004a status
0001004a
Jul 9 23:39:29 gambit kernel: 15: @f7c405c0 length 8000004a status
0001004a
Jul 9 23:39:29 gambit kernel: eth0: Resetting the Tx ring pointer.
Jul 9 23:39:44 gambit kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 9 23:39:44 gambit kernel: eth0: transmit timed out, tx_status 00
status e601.
Jul 9 23:39:44 gambit kernel: diagnostics: net 0cc0 media 8080 dma
0000003a.
Jul 9 23:39:44 gambit kernel: eth0: Interrupt posted but not delivered
-- IRQ blocked by another device?
Jul 9 23:39:44 gambit kernel: Flags; bus-master 1, dirty 5554(2)
current 5554(2)
Jul 9 23:39:44 gambit kernel: Transmit list 00000000 vs. f7c40280.
Jul 9 23:39:44 gambit kernel: 0: @f7c40200 length 80000036 status
80010036
Jul 9 23:39:44 gambit kernel: 1: @f7c40240 length 80000036 status
80010036
Jul 9 23:39:44 gambit kernel: 2: @f7c40280 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 3: @f7c402c0 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 4: @f7c40300 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 5: @f7c40340 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 6: @f7c40380 length 80000042 status
00010042
Jul 9 23:39:44 gambit kernel: 7: @f7c403c0 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 8: @f7c40400 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 9: @f7c40440 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 10: @f7c40480 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 11: @f7c404c0 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 12: @f7c40500 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 13: @f7c40540 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 14: @f7c40580 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: 15: @f7c405c0 length 80000036 status
00010036
Jul 9 23:39:44 gambit kernel: eth0: Resetting the Tx ring pointer.
Jul 9 23:39:51 gambit kernel: usb-ohci.c: unlink URB timeout
Jul 9 23:39:54 gambit kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 9 23:39:54 gambit kernel: eth0: transmit timed out, tx_status 00
status e601.
Jul 9 23:39:54 gambit kernel: diagnostics: net 0cc0 media 8080 dma
0000003a.
Jul 9 23:39:54 gambit kernel: eth0: Interrupt posted but not delivered
-- IRQ blocked by another device?
Jul 9 23:39:54 gambit kernel: Flags; bus-master 1, dirty 5570(2)
current 5570(2)
Jul 9 23:39:54 gambit kernel: Transmit list 00000000 vs. f7c40280.
Jul 9 23:39:54 gambit kernel: 0: @f7c40200 length 80000078 status
80010078
Jul 9 23:39:54 gambit kernel: 1: @f7c40240 length 80000036 status
80010036
Jul 9 23:39:54 gambit kernel: 2: @f7c40280 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: 3: @f7c402c0 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: 4: @f7c40300 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: 5: @f7c40340 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: 6: @f7c40380 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: 7: @f7c403c0 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: 8: @f7c40400 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: 9: @f7c40440 length 80000078 status
00010078
Jul 9 23:39:54 gambit kernel: 10: @f7c40480 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: 11: @f7c404c0 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: 12: @f7c40500 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: 13: @f7c40540 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: 15: @f7c405c0 length 80000036 status
00010036
Jul 9 23:39:54 gambit kernel: eth0: Resetting the Tx ring pointer.
Jul 9 23:40:04 gambit kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 9 23:40:04 gambit kernel: eth0: transmit timed out, tx_status 00
status e601.
Jul 9 23:40:04 gambit kernel: diagnostics: net 0cc0 media 8080 dma
0000003a.
Jul 9 23:40:04 gambit kernel: eth0: Interrupt posted but not delivered
-- IRQ blocked by another device?
Jul 9 23:40:04 gambit kernel: Flags; bus-master 1, dirty 5586(2)
current 5586(2)
Jul 9 23:40:04 gambit kernel: Transmit list 00000000 vs. f7c40280.
Jul 9 23:40:04 gambit kernel: 0: @f7c40200 length 80000036 status
80010036
Jul 9 23:40:04 gambit kernel: 1: @f7c40240 length 80000036 status
80010036
Jul 9 23:40:04 gambit kernel: 2: @f7c40280 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 3: @f7c402c0 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 4: @f7c40300 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 5: @f7c40340 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 6: @f7c40380 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 7: @f7c403c0 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 8: @f7c40400 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 9: @f7c40440 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 10: @f7c40480 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 11: @f7c404c0 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 12: @f7c40500 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 13: @f7c40540 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 14: @f7c40580 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: 15: @f7c405c0 length 80000036 status
00010036
Jul 9 23:40:04 gambit kernel: eth0: Resetting the Tx ring pointer.
I am not subscribed to LKML, but I do check the archives regularly.
John
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: USB stops working with any of 2.4.22-pre's after 2.4.21
2003-07-10 6:58 USB stops working with any of 2.4.22-pre's after 2.4.21 John Wong
@ 2003-07-10 7:06 ` John Wong
2003-07-10 17:02 ` Greg KH
1 sibling, 0 replies; 10+ messages in thread
From: John Wong @ 2003-07-10 7:06 UTC (permalink / raw)
To: linux-kernel
Hmm, forgot to mention that I've tried 2.4.22-pre1, pre2, pre3, and
pre4. All incur this problem.
On Wed, Jul 09, 2003 at 11:58:01PM -0700, John Wong wrote:
> On any of the 2.4.22-pre's, after a bit of time, my USB mouse stops
> responding. It is using the usb-ohci driver. 2.4.22-pre1 included the
> new ACPI base. Even before this ACPI was merged into mainstream, I had
> tried patching the system with the newer ACPI on 2.4.21-pre, and rc's
> and I also ran into the same problem that I am now getting with
> 2.4.22-pre's. I'm suspecting the new ACPI is behind this. Stopping gpm
> and removing usb-ohci and then reloading it doesn't seem to get it
> working again. A reboot does the trick. Strange though is that the one
> USB 2.0 device I have plugged in still continues to work (at least for a
> while as I normally reboot when the problem arises) when I start having
> the problems with USB mouse. But then, it uses the ehci-hcd driver.
>
> Some hardware info. I'm using a nForce2 board with an ATI Radeon video
> card.
>
> Jul 9 23:39:29 gambit kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Jul 9 23:39:29 gambit kernel: eth0: transmit timed out, tx_status 00
> status e601.
> Jul 9 23:39:29 gambit kernel: diagnostics: net 0cc0 media 8080 dma
> 0000003a.
> Jul 9 23:39:29 gambit kernel: eth0: Interrupt posted but not delivered
> -- IRQ blocked by another device?
> Jul 9 23:39:29 gambit kernel: Flags; bus-master 1, dirty 5538(2)
> current 5538(2)
> Jul 9 23:39:29 gambit kernel: Transmit list 00000000 vs. f7c40280.
> Jul 9 23:39:29 gambit kernel: 0: @f7c40200 length 80000036 status
> 80010036
> Jul 9 23:39:29 gambit kernel: 1: @f7c40240 length 80000036 status
> 80010036
> Jul 9 23:39:29 gambit kernel: 2: @f7c40280 length 80000042 status
> 00010042
> Jul 9 23:39:29 gambit kernel: 3: @f7c402c0 length 8000004a status
> 0001004a
> Jul 9 23:39:29 gambit kernel: 4: @f7c40300 length 800005ea status
> 000105ea
> Jul 9 23:39:29 gambit kernel: 5: @f7c40340 length 800001be status
> 000101be
> Jul 9 23:39:29 gambit kernel: 6: @f7c40380 length 800005ea status
> 000105ea
> Jul 9 23:39:29 gambit kernel: 7: @f7c403c0 length 800001be status
> 000101be
> Jul 9 23:39:29 gambit kernel: 8: @f7c40400 length 800001be status
> 000101be
> Jul 9 23:39:29 gambit kernel: 9: @f7c40440 length 800005ea status
> 000105ea
> Jul 9 23:39:29 gambit kernel: 10: @f7c40480 length 8000004a status
> 0001004a
> Jul 9 23:39:29 gambit kernel: 11: @f7c404c0 length 80000187 status
> 00010187
> Jul 9 23:39:29 gambit kernel: 12: @f7c40500 length 8000004a status
> 0001004a
> Jul 9 23:39:29 gambit kernel: 13: @f7c40540 length 80000042 status
> 00010042
> Jul 9 23:39:29 gambit kernel: 14: @f7c40580 length 8000004a status
> 0001004a
> Jul 9 23:39:29 gambit kernel: 15: @f7c405c0 length 8000004a status
> 0001004a
> Jul 9 23:39:29 gambit kernel: eth0: Resetting the Tx ring pointer.
> Jul 9 23:39:44 gambit kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Jul 9 23:39:44 gambit kernel: eth0: transmit timed out, tx_status 00
> status e601.
> Jul 9 23:39:44 gambit kernel: diagnostics: net 0cc0 media 8080 dma
> 0000003a.
> Jul 9 23:39:44 gambit kernel: eth0: Interrupt posted but not delivered
> -- IRQ blocked by another device?
> Jul 9 23:39:44 gambit kernel: Flags; bus-master 1, dirty 5554(2)
> current 5554(2)
> Jul 9 23:39:44 gambit kernel: Transmit list 00000000 vs. f7c40280.
> Jul 9 23:39:44 gambit kernel: 0: @f7c40200 length 80000036 status
> 80010036
> Jul 9 23:39:44 gambit kernel: 1: @f7c40240 length 80000036 status
> 80010036
> Jul 9 23:39:44 gambit kernel: 2: @f7c40280 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 3: @f7c402c0 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 4: @f7c40300 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 5: @f7c40340 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 6: @f7c40380 length 80000042 status
> 00010042
> Jul 9 23:39:44 gambit kernel: 7: @f7c403c0 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 8: @f7c40400 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 9: @f7c40440 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 10: @f7c40480 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 11: @f7c404c0 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 12: @f7c40500 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 13: @f7c40540 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 14: @f7c40580 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: 15: @f7c405c0 length 80000036 status
> 00010036
> Jul 9 23:39:44 gambit kernel: eth0: Resetting the Tx ring pointer.
> Jul 9 23:39:51 gambit kernel: usb-ohci.c: unlink URB timeout
> Jul 9 23:39:54 gambit kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Jul 9 23:39:54 gambit kernel: eth0: transmit timed out, tx_status 00
> status e601.
> Jul 9 23:39:54 gambit kernel: diagnostics: net 0cc0 media 8080 dma
> 0000003a.
> Jul 9 23:39:54 gambit kernel: eth0: Interrupt posted but not delivered
> -- IRQ blocked by another device?
> Jul 9 23:39:54 gambit kernel: Flags; bus-master 1, dirty 5570(2)
> current 5570(2)
> Jul 9 23:39:54 gambit kernel: Transmit list 00000000 vs. f7c40280.
> Jul 9 23:39:54 gambit kernel: 0: @f7c40200 length 80000078 status
> 80010078
> Jul 9 23:39:54 gambit kernel: 1: @f7c40240 length 80000036 status
> 80010036
> Jul 9 23:39:54 gambit kernel: 2: @f7c40280 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: 3: @f7c402c0 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: 4: @f7c40300 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: 5: @f7c40340 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: 6: @f7c40380 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: 7: @f7c403c0 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: 8: @f7c40400 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: 9: @f7c40440 length 80000078 status
> 00010078
> Jul 9 23:39:54 gambit kernel: 10: @f7c40480 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: 11: @f7c404c0 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: 12: @f7c40500 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: 13: @f7c40540 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: 15: @f7c405c0 length 80000036 status
> 00010036
> Jul 9 23:39:54 gambit kernel: eth0: Resetting the Tx ring pointer.
> Jul 9 23:40:04 gambit kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Jul 9 23:40:04 gambit kernel: eth0: transmit timed out, tx_status 00
> status e601.
> Jul 9 23:40:04 gambit kernel: diagnostics: net 0cc0 media 8080 dma
> 0000003a.
> Jul 9 23:40:04 gambit kernel: eth0: Interrupt posted but not delivered
> -- IRQ blocked by another device?
> Jul 9 23:40:04 gambit kernel: Flags; bus-master 1, dirty 5586(2)
> current 5586(2)
> Jul 9 23:40:04 gambit kernel: Transmit list 00000000 vs. f7c40280.
> Jul 9 23:40:04 gambit kernel: 0: @f7c40200 length 80000036 status
> 80010036
> Jul 9 23:40:04 gambit kernel: 1: @f7c40240 length 80000036 status
> 80010036
> Jul 9 23:40:04 gambit kernel: 2: @f7c40280 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 3: @f7c402c0 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 4: @f7c40300 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 5: @f7c40340 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 6: @f7c40380 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 7: @f7c403c0 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 8: @f7c40400 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 9: @f7c40440 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 10: @f7c40480 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 11: @f7c404c0 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 12: @f7c40500 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 13: @f7c40540 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 14: @f7c40580 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: 15: @f7c405c0 length 80000036 status
> 00010036
> Jul 9 23:40:04 gambit kernel: eth0: Resetting the Tx ring pointer.
>
> I am not subscribed to LKML, but I do check the archives regularly.
>
> John
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: USB stops working with any of 2.4.22-pre's after 2.4.21
2003-07-10 6:58 USB stops working with any of 2.4.22-pre's after 2.4.21 John Wong
2003-07-10 7:06 ` John Wong
@ 2003-07-10 17:02 ` Greg KH
2003-07-10 17:35 ` Gene Heskett
2003-07-10 18:58 ` John Wong
1 sibling, 2 replies; 10+ messages in thread
From: Greg KH @ 2003-07-10 17:02 UTC (permalink / raw)
To: John Wong; +Cc: linux-kernel
On Wed, Jul 09, 2003 at 11:58:01PM -0700, John Wong wrote:
> Jul 9 23:39:44 gambit kernel: eth0: Resetting the Tx ring pointer.
> Jul 9 23:39:51 gambit kernel: usb-ohci.c: unlink URB timeout
> Jul 9 23:39:54 gambit kernel: NETDEV WATCHDOG: eth0: transmit timed out
Hm, looks like bad things are happening with your interrupts.
Do you need acpi to run this box? What happens if you disable it?
As it looks like networking is also in trouble, I don't think this is a
USB specific problem for you.
Good luck,
greg k-h
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: USB stops working with any of 2.4.22-pre's after 2.4.21
2003-07-10 17:02 ` Greg KH
@ 2003-07-10 17:35 ` Gene Heskett
2003-07-10 17:50 ` Greg KH
2003-07-10 18:58 ` John Wong
1 sibling, 1 reply; 10+ messages in thread
From: Gene Heskett @ 2003-07-10 17:35 UTC (permalink / raw)
To: Greg KH, John Wong; +Cc: linux-kernel
On Thursday 10 July 2003 13:02, Greg KH wrote:
>On Wed, Jul 09, 2003 at 11:58:01PM -0700, John Wong wrote:
>> Jul 9 23:39:44 gambit kernel: eth0: Resetting the Tx ring
>> pointer. Jul 9 23:39:51 gambit kernel: usb-ohci.c: unlink URB
>> timeout Jul 9 23:39:54 gambit kernel: NETDEV WATCHDOG: eth0:
>> transmit timed out
>
>Hm, looks like bad things are happening with your interrupts.
>
>Do you need acpi to run this box? What happens if you disable it?
>
>As it looks like networking is also in trouble, I don't think this
> is a USB specific problem for you.
>
>Good luck,
>
>greg k-h
>-
I have a couple of nits with usb here too.
kernel is 2.4.22-pre3
dmesg shows this for a radio shack/Prolific 2303 usb-seriel convertor:
---
usbserial.c: USB Serial support registered for Generic
usbserial.c: USB Serial Driver core v1.4
usbserial.c: USB Serial support registered for PL-2303
pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.9
----
But the output of an lsusb command shows this only:
---
Bus 002 Device 006: ID 1453:4026
Language IDs: none (invalid length string descriptor 63; len=7)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 Interface
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x1453
idProduct 0x4026
bcdDevice 0.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 10
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Language IDs: none (invalid length string descriptor 63; len=7)
---
And my ability to use it, while never great due to config problems on
the other end of the cable, seems now to have gone away. There has
also been some pretty heavy lightning activity in the area, during
which time it may have been hooked up, and something blown from the
EMP of a nearby strike. I usually leave it unplugged on the seriel
side because of that.
Does this look normal? ISTR it used to ID itself all the time, not
just in dmesg.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: USB stops working with any of 2.4.22-pre's after 2.4.21
2003-07-10 17:35 ` Gene Heskett
@ 2003-07-10 17:50 ` Greg KH
2003-07-10 22:51 ` Gene Heskett
0 siblings, 1 reply; 10+ messages in thread
From: Greg KH @ 2003-07-10 17:50 UTC (permalink / raw)
To: Gene Heskett; +Cc: John Wong, linux-kernel
On Thu, Jul 10, 2003 at 01:35:34PM -0400, Gene Heskett wrote:
> And my ability to use it, while never great due to config problems on
> the other end of the cable, seems now to have gone away. There has
> also been some pretty heavy lightning activity in the area, during
> which time it may have been hooked up, and something blown from the
> EMP of a nearby strike. I usually leave it unplugged on the seriel
> side because of that.
>
> Does this look normal? ISTR it used to ID itself all the time, not
> just in dmesg.
What does /proc/bus/usb/devices show for this device?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: USB stops working with any of 2.4.22-pre's after 2.4.21
2003-07-10 17:02 ` Greg KH
2003-07-10 17:35 ` Gene Heskett
@ 2003-07-10 18:58 ` John Wong
2003-07-11 5:20 ` John Wong
1 sibling, 1 reply; 10+ messages in thread
From: John Wong @ 2003-07-10 18:58 UTC (permalink / raw)
To: Greg KH; +Cc: linux-kernel
Sorry if this is a duplicate...I received an error bounce
----
ACPI isn't absolutely needed, but it comes in handy for issuing a
shutdown.
Though I suppose I can use apm to do this as well.
On a uni-processor system, isn't the ACPI tables used to setup the
IO-APIC bits to have PCI IRQ routing so that I have more than 16
interrupts? This was another reason I had enabled ACPI.
When I do get those interrupt problems, my network still continues to
function while the USB mouse fails. I do agree it's not USB specific.
It's more tied in to ACPI/(IO-)APIC.
When I get back home, I'll try booting it with acpi=off on pre4 and see
how it goes.
John
On Thu, Jul 10, 2003 at 10:02:17AM -0700, Greg KH wrote:
> On Wed, Jul 09, 2003 at 11:58:01PM -0700, John Wong wrote:
> > Jul 9 23:39:44 gambit kernel: eth0: Resetting the Tx ring pointer.
> > Jul 9 23:39:51 gambit kernel: usb-ohci.c: unlink URB timeout
> > Jul 9 23:39:54 gambit kernel: NETDEV WATCHDOG: eth0: transmit timed out
>
> Hm, looks like bad things are happening with your interrupts.
>
> Do you need acpi to run this box? What happens if you disable it?
>
> As it looks like networking is also in trouble, I don't think this is a
> USB specific problem for you.
>
> Good luck,
>
> greg k-h
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: USB stops working with any of 2.4.22-pre's after 2.4.21
2003-07-10 17:50 ` Greg KH
@ 2003-07-10 22:51 ` Gene Heskett
2003-07-11 0:12 ` Greg KH
0 siblings, 1 reply; 10+ messages in thread
From: Gene Heskett @ 2003-07-10 22:51 UTC (permalink / raw)
To: Greg KH; +Cc: John Wong, linux-kernel
On Thursday 10 July 2003 13:50, Greg KH wrote:
>On Thu, Jul 10, 2003 at 01:35:34PM -0400, Gene Heskett wrote:
>> And my ability to use it, while never great due to config problems
>> on the other end of the cable, seems now to have gone away. There
>> has also been some pretty heavy lightning activity in the area,
>> during which time it may have been hooked up, and something blown
>> from the EMP of a nearby strike. I usually leave it unplugged on
>> the seriel side because of that.
>>
>> Does this look normal? ISTR it used to ID itself all the time,
>> not just in dmesg.
>
>What does /proc/bus/usb/devices show for this device?
>
>thanks,
>
>greg k-h
A cat of that looks like this:
[root@coyote root]# cat /proc/bus/usb/devices
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=e400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 22/900 us ( 2%), #Int= 2, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=e000
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 4
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=03eb ProdID=3301 Rev= 3.00
S: Product=Standard USB Hub
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 64mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 6 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=1453 ProdID=4026 Rev= 0.00
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=serial
E: Ad=81(I) Atr=03(Int.) MxPS= 10 Ivl=1ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=02 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 8 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=04b8 ProdID=0005 Rev= 1.00
S: Manufacturer=EPSON
S: Product=USB Printer
S: SerialNumber=W02L20201172205420
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=02 Lev=02 Prnt=02 Port=02 Cnt=03 Dev#= 7 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=0900 Rev= 0.90
C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00
Driver=Connectix QuickCam VC
E: Ad=81(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 0 Alt= 1 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00
Driver=Connectix QuickCam VC
E: Ad=81(I) Atr=01(Isoc) MxPS= 128 Ivl=1ms
I: If#= 0 Alt= 2 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00
Driver=Connectix QuickCam VC
E: Ad=81(I) Atr=01(Isoc) MxPS= 384 Ivl=1ms
I: If#= 0 Alt= 3 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00
Driver=Connectix QuickCam VC
E: Ad=81(I) Atr=01(Isoc) MxPS= 512 Ivl=1ms
I: If#= 0 Alt= 4 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00
Driver=Connectix QuickCam VC
E: Ad=81(I) Atr=01(Isoc) MxPS= 640 Ivl=1ms
I: If#= 0 Alt= 5 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00
Driver=Connectix QuickCam VC
E: Ad=81(I) Atr=01(Isoc) MxPS= 768 Ivl=1ms
I: If#= 0 Alt= 6 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00
Driver=Connectix QuickCam VC
E: Ad=81(I) Atr=01(Isoc) MxPS= 896 Ivl=1ms
I: If#= 0 Alt= 7 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00
Driver=Connectix QuickCam VC
E: Ad=81(I) Atr=01(Isoc) MxPS=1023 Ivl=1ms
I: If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00
Driver=Connectix QuickCam VC
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=84(I) Atr=03(Int.) MxPS= 1 Ivl=8ms
The above doesn't work yet
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=04b8 ProdID=010f Rev= 1.00
S: Manufacturer=EPSON
S: Product=EPSON Scanner 010F
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff
Driver=usbscanner
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=16ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 93/900 us (10%), #Int= 1, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=dc00
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=c00e Rev=11.00
S: Manufacturer=Logitech
S: Product=USB-PS/2 Optical Mouse
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 98mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=hid
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=10ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=04b8 ProdID=0005 Rev= 1.00
S: Manufacturer=EPSON
S: Product=USB Printer
S: SerialNumber=RL0200301161041200
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0msPS= 64 Ivl=0ms
r=02(Bulk) MxPS= 64 Ivl=0ms
And yes, there are two printers attached. The 820 is for sale.
And, sort of as an afterthought, lemme toss in that the Belkin Bulldog
UPS monitor soft, runs on a real serial port, /dev/ttyS1, hasn't
worked since about 2.4.18 or so. Somewhere about that time anyway.
I've yelled at Belkin since it was compiled on a RH5.2 system and
they've refused to update their proprietary drivers. Or to release
the API even if I'd have signed an NDA. NDI why.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: USB stops working with any of 2.4.22-pre's after 2.4.21
2003-07-10 22:51 ` Gene Heskett
@ 2003-07-11 0:12 ` Greg KH
2003-07-11 0:59 ` Gene Heskett
0 siblings, 1 reply; 10+ messages in thread
From: Greg KH @ 2003-07-11 0:12 UTC (permalink / raw)
To: Gene Heskett; +Cc: John Wong, linux-kernel
On Thu, Jul 10, 2003 at 06:51:14PM -0400, Gene Heskett wrote:
>
> T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 6 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=1453 ProdID=4026 Rev= 0.00
> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
> I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=serial
> E: Ad=81(I) Atr=03(Int.) MxPS= 10 Ivl=1ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
Looks ok, the device probably just doesn't have any string descriptors
(or any valid ones at least.)
It should not affect the operation of the device, right?
greg k-h
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: USB stops working with any of 2.4.22-pre's after 2.4.21
2003-07-11 0:12 ` Greg KH
@ 2003-07-11 0:59 ` Gene Heskett
0 siblings, 0 replies; 10+ messages in thread
From: Gene Heskett @ 2003-07-11 0:59 UTC (permalink / raw)
To: Greg KH; +Cc: John Wong, linux-kernel
On Thursday 10 July 2003 20:12, Greg KH wrote:
>On Thu, Jul 10, 2003 at 06:51:14PM -0400, Gene Heskett wrote:
>> T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 6 Spd=12 MxCh= 0
>> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
>> P: Vendor=1453 ProdID=4026 Rev= 0.00
>> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
>> I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00
>> Driver=serial E: Ad=81(I) Atr=03(Int.) MxPS= 10 Ivl=1ms
>> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>> E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>
>Looks ok, the device probably just doesn't have any string
> descriptors (or any valid ones at least.)
>
>It should not affect the operation of the device, right?
>
>greg k-h
It must be time for me to see if I can find enough 9 to 25 pin
adaptors and stick an led sniffer in the line then, because I cannot
talk to the trs80 Color Computer on the other end of the cable.
I'll be back on this if I find anything interesting. Of more interest
is the fact that the belkin bulldog kits upsd cannot talk to
/dev/ttyS1 although it is picking up data from the port. It outputs
on localhost:2710 but its only the keep-alive chatter from the ups.
Apparently no commands can be sent to the ups.
This however, is a seriel port problem, not usb. I was sort of hoping
there might be a common thread to the failures. :)
--
Cheers Greg, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: USB stops working with any of 2.4.22-pre's after 2.4.21
2003-07-10 18:58 ` John Wong
@ 2003-07-11 5:20 ` John Wong
0 siblings, 0 replies; 10+ messages in thread
From: John Wong @ 2003-07-11 5:20 UTC (permalink / raw)
To: Greg KH; +Cc: linux-kernel
acpi=off on 2.4.22-pre4 for the last 4 hours and haven't run into the
interrupt/usb problems. Normally the problems arise not too soon into
the boot up, forcing me to boot up 2.4.21 if I ever wanted to log on
remotely. Looks like all my problems are being caused by the newer ACPI
code base merged since pre1.
John
On Thu, Jul 10, 2003 at 11:58:13AM -0700, John Wong wrote:
> Sorry if this is a duplicate...I received an error bounce
>
> ----
> ACPI isn't absolutely needed, but it comes in handy for issuing a
> shutdown.
> Though I suppose I can use apm to do this as well.
>
> On a uni-processor system, isn't the ACPI tables used to setup the
> IO-APIC bits to have PCI IRQ routing so that I have more than 16
> interrupts? This was another reason I had enabled ACPI.
>
> When I do get those interrupt problems, my network still continues to
> function while the USB mouse fails. I do agree it's not USB specific.
> It's more tied in to ACPI/(IO-)APIC.
>
> When I get back home, I'll try booting it with acpi=off on pre4 and see
> how it goes.
>
> John
>
> On Thu, Jul 10, 2003 at 10:02:17AM -0700, Greg KH wrote:
> > On Wed, Jul 09, 2003 at 11:58:01PM -0700, John Wong wrote:
> > > Jul 9 23:39:44 gambit kernel: eth0: Resetting the Tx ring pointer.
> > > Jul 9 23:39:51 gambit kernel: usb-ohci.c: unlink URB timeout
> > > Jul 9 23:39:54 gambit kernel: NETDEV WATCHDOG: eth0: transmit timed out
> >
> > Hm, looks like bad things are happening with your interrupts.
> >
> > Do you need acpi to run this box? What happens if you disable it?
> >
> > As it looks like networking is also in trouble, I don't think this is a
> > USB specific problem for you.
> >
> > Good luck,
> >
> > greg k-h
> >
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2003-07-11 5:06 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-10 6:58 USB stops working with any of 2.4.22-pre's after 2.4.21 John Wong
2003-07-10 7:06 ` John Wong
2003-07-10 17:02 ` Greg KH
2003-07-10 17:35 ` Gene Heskett
2003-07-10 17:50 ` Greg KH
2003-07-10 22:51 ` Gene Heskett
2003-07-11 0:12 ` Greg KH
2003-07-11 0:59 ` Gene Heskett
2003-07-10 18:58 ` John Wong
2003-07-11 5:20 ` John Wong
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).