Messages in this thread |  | | Date | Sun, 10 Jun 2001 18:03:42 -0400 | | From | Pete Zaitcev <> | | Subject | Re: [linux-usb-devel] usb.c: USB device not accepting new address=4 (error=-110) |
| |
I had difficulties making it all work on ServerWorks III LE based machines, most notably 2450 & 6450.
Dell fixed 2450 eventually, BIOS needs upgrade to level A11.
> > 30: 0 0 IO-APIC-level usb-ohci
The line above says that MP table contained the device. This is the situarion with 6450 - they have the MP entry, but there is no way to make it work. I am working with their BIOS and hw engineers on a fix.
For the moment the workaround is to run the whole thing with "noapic". Try it, perhaps it helps the machine in question.
-- Pete
> 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> > Reply-To: linux-usb-devel@lists.sourceforge.net > Date: Sat, 09 Jun 2001 06:14:24 -0700
> 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |