On Friday 03 June 2005 10:41 am, Parag Warudkar wrote:
>
> Also interesting is this line -
> [ 40.586298] ohci_hcd 0000:00:02.0: Unlink after no-IRQ? Controller is
> probably using the wrong IRQ.
So did you investigate these IRQ setup problem, or just ignore
that pointed diagnostic?
Controllers are not expected to behave if their drivers aren't given
the correct IRQ. In particular, when software needs to wait until
the hardware reports it's finished with something, and the hardware
never reports that (== never issues the IRQ) then things may hang.
Also this earlier line already identified a potential root cause:
> [ 38.927690] ACPI: PCI Interrupt 0000:00:02.0[P]: no GSI - using IRQ 11
This could be a problem in either the tables BIOS provided, or in the
way ACPI is interpreting them, or something else ... I'm not an ACPI guru.
You should be experimenting with ways to get the right IRQ assigned to this
controller; such problems are common enough that there are probably half a
dozen boot options affecting what happens. Or maybe look at BIOS options that
affect that controller; you might need to update your board's BIOS firmware.
- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
