All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Greg KH <greg@kroah.com>
Cc: Johannes Resch <jr@xor.at>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.25: USB problems ("device not accepting new address")
Date: 20 Mar 2004 22:53:58 -0500	[thread overview]
Message-ID: <1079841238.7277.880.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615F5EC0@hdsmsx402.hd.intel.com>

On Sat, 2004-03-20 at 14:53, Greg KH wrote:
> On Sat, Mar 20, 2004 at 12:05:33PM +0100, Johannes Resch wrote:
> > Hello,
> > 
> > I've got the problem that the USB mouse device will cease responding
> after
> > some time. "dmesg" then shows:
> > 
> > usb-uhci.c: interrupt, status 2, frame# 699
> > usb.c: USB device not accepting new address=2 (error=-110)
> > hub.c: new USB device 00:1d.1-2, assigned address 3
> > usb.c: USB device not accepting new address=3 (error=-110)
> 
> This is a PCI interrupt routing issue, not a USB issue.  I suggest
> disabing acpi if you do not need it.  If you require acpi, then please
> take this to the acpi mailing list, the people there will work with
> you
> to solve it.

I didn't notice any configuration-time ACPI issues that would cause
USB to start failing after a few hours of use.

If the system runs properly with acpi=off or pci=noacpi,
but fails without it, please set me know
cc: acpi-devel@lists.sourceforge.net

thanks,
-Len




       reply	other threads:[~2004-03-21  3:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A6974D8E5F98D511BB910002A50A6647615F5EC0@hdsmsx402.hd.intel.com>
2004-03-21  3:53 ` Len Brown [this message]
2004-03-21  7:39   ` Linux 2.4.25: USB problems ("device not accepting new address") Stian Jordet
2004-03-20 11:05 Johannes Resch
2004-03-20 19:53 ` Greg KH

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=1079841238.7277.880.camel@dhcppc4 \
    --to=len.brown@intel.com \
    --cc=greg@kroah.com \
    --cc=jr@xor.at \
    --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.