On Wednesday 12 March 2008, Bjorn Helgaas wrote: > On Tuesday 11 March 2008 09:40:04 pm Len Brown wrote: > > Is it true that simply enabling pci=routeirq on these boxes > > is an insufficient workaround? > > I'm told that pci=routeirq is a sufficient workaround for the > first two issues, but I verified that it is not sufficient on > the t5710. > > On the t5710, even with pci=routeirq, as soon as we turn on the > radeon interrupt, it starts generating interrupts on LNK3. Since > the radeon driver isn't listening there, we eventually turn off > that IRQ, killing other other devices sharing it as a side-effect. > > I don't know why pci=routeirq works on the other two boxes. Maybe > because of your guess below. okay, then lets go with the precise workaround you proposed. thanks, -Len > > I suspect the answer is yes, because when pci=routeirq works > > we may just be lucky -- eg. we happen to assign the real > > and the fake link to the same IRQ and thus the driver > > actually registers for the correct IRQ, but by accident. > > -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
