archive mirror
 help / color / mirror / Atom feed
From: John Wong <>
To: Greg KH <>
Subject: Re: USB stops working with any of 2.4.22-pre's after 2.4.21
Date: Thu, 10 Jul 2003 11:58:13 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Sorry if this is a duplicate...I received an error bounce

ACPI isn't absolutely needed, but it comes in handy for issuing a
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.


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

  parent reply	other threads:[~2003-07-10 18:43 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
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 [this message]
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:

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

  git send-email \ \ \ \ \

* 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 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).