From: thunder7@xs4all.nl
To: linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] usb.c: USB device not accepting new address=4 (error=-110)
Date: Sat, 9 Jun 2001 20:15:22 +0200 [thread overview]
Message-ID: <20010609201522.A5319@middle.of.nowhere> (raw)
In-Reply-To: <20010609064123.V11815@nightmaster.csn.tu-chemnitz.de> <0ab501c0f0ac$10532720$cc07aace@brownell.org> <20010609091919.W11815@nightmaster.csn.tu-chemnitz.de> <0ae201c0f0e6$1b59fb00$cc07aace@brownell.org>
In-Reply-To: <0ae201c0f0e6$1b59fb00$cc07aace@brownell.org>
On Sat, Jun 09, 2001 at 06:14:24AM -0700, David Brownell wrote:
> Then whatever sets up your ServerWorks ServerSet III LE chipset
> needs its PCI IRQ setup fixed ... I'm not sure how to do this.
>
> Perhaps someone who's familiar with arch/i386/kernel/pci-*.c
> irq setup can suggest the right patch for this problem. I think
> the "dmesg" output in your original post probably had the info
> needed to figure that out.
>
> - Dave
>
>
> > From: "Ingo Oeser" <ingo.oeser@informatik.tu-chemnitz.de>
> > Sent: Saturday, June 09, 2001 12:19 AM
> >
> > > David Brownell wrote:
> > > Can you verify, using /proc/interrupts, that you're actually
> > > getting interrupts on irq #30 when these timeouts happen?
> >
> > I get none:
> > 30: 0 0 IO-APIC-level usb-ohci
> >
> > > One possibility: the timeout happens because the HCD
> > > is not getting the interrupts it expects. That would imply
> > > that the PCI IRQ setup for this device isn't quite right.
> > > Such problems have been seen before.
> >
> > This seems to be my problem. How can I solve this?
> >
> > My BIOS cannot set a specific IRQ for USB like other BIOSes do.
> >
> > And now that you say^W it, I remember sth. like this on
> > linux-kernel... I just didn't know the messages...
> >
A similar problem with USB on a VIA smp board was solved by Jeff Garzik,
so you might want to send him some info, like
dmesg
lspci -vvvxxx
Good luck,
Jurriaan
--
You have nothing to be afraid of. Well, that might not be true in the
larger scheme of things, but this ordeal is over, so off you go. Toodle-oo.
Fraser, Due South
GNU/Linux 2.4.5-ac12 SMP/ReiserFS 2x1402 bogomips load av: 0.49 0.12 0.04
next prev parent reply other threads:[~2001-06-09 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-09 4:41 usb.c: USB device not accepting new address=4 (error=-110) Ingo Oeser
[not found] ` <0ab501c0f0ac$10532720$cc07aace@brownell.org>
[not found] ` <20010609091919.W11815@nightmaster.csn.tu-chemnitz.de>
2001-06-09 13:14 ` [linux-usb-devel] " David Brownell
2001-06-09 18:15 ` thunder7 [this message]
2001-06-09 18:44 ` Ingo Oeser
2001-06-10 22:03 ` Pete Zaitcev
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=20010609201522.A5319@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox