“Taed Wynnell” wrote in message news:xxxxx@ntdev…
> So, something is whacked out somewhere causing my PCI interrupt A that
> should be routed to IRQ 11 to actually be routed to IRQ 10.
I verified that when it’s in the “bad state” (which is what we were
debugging on the phone), the South Bridge’s interrupt routing control
register 0x60 has 0x0A (IRQ 10), but my device’s and the other devices that
are on physical PCI INTA# have InterruptLine 0x3C registers that contain
0x0B (IRQ 11).
HOWEVER, I did an initial breakpoint with WinDbg, and the values were all
0x0B at that point, but then about 30 seconds later, the South Bridge
interrupt routing control register was changed to 0x0A. So, this seems to
either be a Windows problem, or maybe an error in the BIOS’ PCI Interrupt
Routing Table that causes it to make a bad decision.
After 2 weeks, I’m glad that I’m making some progress…