Hi,
I'm having problems with an Intel D865PERL motherboard and Serial ATA support. Everytime I boot my RHL9 box using 2.6.0-test1, I get an "irq18 nobody cared!" error and then "Disabling IRQ #18". Any attempt to access any of the SATA controllers makes the system hang and spitting out problems with timings on the "hde" interface.
I have tried compiling without ACPI, APIC and SMP, but the result is nearly the same. Attached to this message are the output of "lspci -vvv", a "dmesg" and the "config" used to compile the kernel.
Any ideas? Should I report this to IDE mantainers?
Thanks!
--
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr
Powered by Outblaze
On Mon, 2003-07-14 at 16:12, Felipe Alfaro Solana wrote:
> I'm having problems with an Intel D865PERL motherboard and Serial ATA
> support. Everytime I boot my RHL9 box using 2.6.0-test1, I get an
> "irq18 nobody cared!" error and then "Disabling IRQ #18". Any attempt
> to access any of the SATA controllers makes the system hang and
> spitting out problems with timings on the "hde" interface.
I have the same problem with Abit IS7-E, which also has the i865PE
chipset.
Add "noirqdebug" to the kernel command line and you should be able to
boot, although the irq will be firing continously until the device
driver gets initialized and catches it.
MikaL
On Saturday 26 July 2003 22:52, Mika Liljeberg wrote:
> On Mon, 2003-07-14 at 16:12, Felipe Alfaro Solana wrote:
> > I'm having problems with an Intel D865PERL motherboard and Serial ATA
> > support. Everytime I boot my RHL9 box using 2.6.0-test1, I get an
> > "irq18 nobody cared!" error and then "Disabling IRQ #18". Any attempt
> > to access any of the SATA controllers makes the system hang and
> > spitting out problems with timings on the "hde" interface.
>
> I have the same problem with Abit IS7-E, which also has the i865PE
> chipset.
>
> Add "noirqdebug" to the kernel command line and you should be able to
> boot, although the irq will be firing continously until the device
> driver gets initialized and catches it.
Out of interest, do these boxes have an IO-APIC and are you using ACPI? If so,
can you tell me if the attached patch helps?
These are exactly the symptoms I got without the attached patch (it fixes an
IO-APIC setup bug with ACPI).
On Sun, 2003-07-27 at 01:13, Andrew de Quincey wrote:
> Out of interest, do these boxes have an IO-APIC and are you using ACPI? If so,
> can you tell me if the attached patch helps?
Yes, yes, nope. I tried your patch but the SATA driver now hangs during
boot waiting for an irq that never arrives.
MikaL
On Sunday 27 July 2003 00:01, Mika Liljeberg wrote:
> On Sun, 2003-07-27 at 01:13, Andrew de Quincey wrote:
> > Out of interest, do these boxes have an IO-APIC and are you using ACPI?
> > If so, can you tell me if the attached patch helps?
>
> Yes, yes, nope. I tried your patch but the SATA driver now hangs during
> boot waiting for an irq that never arrives.
This sounds very familiar. As I said, the patch fixes the IO-APIC so IRQ
polarities and mode is it is now setup as per ACPI... its obviously doing
_something_ for you.
However, there is a second problem which I do not yet have a resolution for.
On my board, it manifests itself with PCI addon cards.. I never see any IRQs
from them because the IO-APIC is configured (as per ACPI) for active high
IRQs, yet the PCI standard is active low IRQs.
I am fairly certain that the IO-APIC is now configured correctly, and that the
PCI routing is correct, because Windows XP sets everything up in exactly the
same way, and everything works fine under it.
There is something else that is not being done by linux. I'd assumed this was
an nforce2-specific issue, but your results hint that it may be larger than
this.
> There is something else that is not being done by linux. I'd assumed this
> was an nforce2-specific issue, but your results hint that it may be larger
> than this.
Yay! I've found it. What seems to be happening is the PIC is left connected to
the PCI IRQ lines, and is causing problems.. I assume pulling the lines
up/down incorrectly.
My BIOS lets me define which PIC IRQs are allocated to PCI and which are
"reserved". I set them all to reserved, effectively disabling any IRQs < 15
being allocated to PCI. Now everything works perfectly.
I've downloaded the manual for your motherboard, but I can't see anything like
that for your board.. all you can do is the standard choose IRQ, or auto.
Anyway, now I know what is causing this, expect a patch soon.
On Sun, 2003-07-27 at 00:13, Andrew de Quincey wrote:
> > I have the same problem with Abit IS7-E, which also has the i865PE
> > chipset.
> >
> > Add "noirqdebug" to the kernel command line and you should be able to
> > boot, although the irq will be firing continously until the device
> > driver gets initialized and catches it.
>
> Out of interest, do these boxes have an IO-APIC and are you using ACPI? If so,
> can you tell me if the attached patch helps?
>
> These are exactly the symptoms I got without the attached patch (it fixes an
> IO-APIC setup bug with ACPI).
I won't have access to those machines until August, 3th. I will give
your patch a try then :-)
Thanks!