Asus P5W DH Deluxe APIC/SMP IRQ problem

[John Baldwin]

On Friday 13 July 2007 10:07:56 am Михаил Кучин wrote:
> Hi!
> 
> I am still searching help with Asus P5W DH Deluxe IRQ's
> 
> > > > atapci0: <JMicron JMB363 SATA300 controller> port
> > > > 0xac00-0xac07,0xa880-0xa883,0xa800-0xa807,0xa480-0xa483,0xa400-0xa40f 
mem
> > > > 0xfe8fe000-0xfe8fffff irq 17 at device 0.0 on pci2
> > > > atapci0: AHCI Version 01.00 controller with 2 ports detected
> > > > ata2: <ATA channel 0> on atapci0
> > > > ata3: <ATA channel 1> on atapci0
> > > > ata4: <ATA channel 2> on atapci0
> > >
> > > So my guess is that one or more of these ATA issues is the cause.
> 
> > Probably not.  His issue is that some device that _isn't_ on IRQ 23 in the
> > _PRT tables, actually _is_ on IRQ 23.  The key is to find out what device
> > (not atapci2) is generating those interrupts.  Turning each device off
> > individually to test can figure this out.
> 
> Thank You for ideas. Today I've tried to use some other VGA cards,
> lots of old different PCI and some new PCI experss card - no effect.
> Not to load myk0 intertface - also unsuccessful.
> 
> How can I turn off other devices like bus or conroller? I have
> succeeded in turning off only myk0 and changing VGA. What cat I do
> next while searching this "bad" device?
> 
> By the way, I've got verbose boot log and mptable output:
>    http://mixey.spb.ru/boot-verbose.txt
>    http://mixey.spb.ru/mptable.txt
>    
> Can it help me?

For now you would just have to hack drivers to not attach, etc.  Your mptable 
agrees with the ACPI tables.  It could also be a bug in the ata(4) driver if 
it's not acknowledging some interrupt condition.  You could test for that by 
trying to print out the interrupt status register in the ata interrupt 
handler for the device on irq 23 and seeing if there are conditions that are 
set on each interrupt and not getting cleared.

-- 
John Baldwin