From: David Brownell <david-b@pacbell.net>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: linux-usb-devel@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] usb.c: USB device not accepting new address=4 (error=-110)
Date: Sat, 09 Jun 2001 06:14:24 -0700 [thread overview]
Message-ID: <0ae201c0f0e6$1b59fb00$cc07aace@brownell.org> (raw)
In-Reply-To: <20010609064123.V11815@nightmaster.csn.tu-chemnitz.de> <0ab501c0f0ac$10532720$cc07aace@brownell.org> <20010609091919.W11815@nightmaster.csn.tu-chemnitz.de>
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...
>
> Thanks and Regards
>
> Ingo Oeser
next prev parent reply other threads:[~2001-06-09 13:18 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 ` David Brownell [this message]
2001-06-09 18:15 ` [linux-usb-devel] " thunder7
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='0ae201c0f0e6$1b59fb00$cc07aace@brownell.org' \
--to=david-b@pacbell.net \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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