On Mon, Oct 08, 2001, J�rg Ziuber <[EMAIL PROTECTED]> wrote: > On Sat, Sep 15, 2001, AA ZZ <<EMAIL: PROTECTED>> wrote: > > ==== USB broken on Sony VAIO PCG-FX250 running RedHat-7.1 Linux ==== > > > > ... > > > > The list of used IRQs reproted in /proc/interrupts shows conflicts at IRQ=9 > > but I think it is not a problem for 2.4.x kernels: > > CPU0 > > 0: 99768 XT-PIC timer > > 1: 2171 XT-PIC keyboard > > 2: 0 XT-PIC cascade > > 8: 1 XT-PIC rtc > > 9: 25169 XT-PIC usb-uhci, usb-uhci, e100, i810@PCI:0:2:0, > > Intel ICH2 > > 12: 696 XT-PIC PS/2 Mouse > > 14: 10177 XT-PIC ide0 > > 15: 27782 XT-PIC ide1 > > NMI: 0 > > ERR: 0 > > > > ... > > JE replied: > > > This looks very much like an IRQ routing problem. Sharing IRQ's is fine, > > but it looks like the IRQ's are never being delivered. > > > Does Windows say what IRQ it is using? > > I have the same problem on the Sony Vaio FX (205/209/301/302 - all > identical). Let me tell > you: > This is not an IRQ conflict between different devices !!! I tried this, > when only usb-uhci was running on IRQ#9.
I don't think anyone is saying it's an IRQ conflict. > This happens if you plug _any_ USB device (powered or not does not mind) > to this notebook under > Linux, even if there are no other devices (eth, sound) running on that > IRQ#9. In that case you have only two usb-uhci devices running on IRQ 9. > > I describe this problem extensively in my new posting "USB support for > i815E/823820 820 (Camino > 2) ?", where I ask if there is a support for this chip which is build in > in my notebook. > > Any advice ? > > I don't know if this would be a solution, but has anyone an idea, if it > is possible to assign > different interrupts to the two usb-uhci modules running on IRQ#9 ? The > module usb-uhci.o has no > parameters, so I dont'now. > > I'm running SuSE 7.2 - so it is distribution independent. I checked it > to be hardware independent, BIOS option (PnP) independent, and > IRQ-conflict-between-DIFFERENT-devices independent. So, I ask for the > correctness of the driver for this chipset (see above) ! Like I said, it sounds like an IRQ routing problem. We've seen many instances of this in the past. Does USB work for you in Windows? If so, I'd still like to hear what IRQ Windows thinks the device is on. JE _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
