All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Wong <kernel@implode.net>
To: linux-kernel@vger.kernel.org
Subject: Re: USB stops working with any of 2.4.22-pre's after 2.4.21
Date: Thu, 10 Jul 2003 00:06:34 -0700	[thread overview]
Message-ID: <20030710070634.GA400@gambit.implode.net> (raw)
In-Reply-To: <20030710065801.GA351@gambit.implode.net>

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

  reply	other threads:[~2003-07-10  6:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030710070634.GA400@gambit.implode.net \
    --to=kernel@implode.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.