Thomas Renninger wrote: > On Friday 29 August 2008 12:20:14 Tejun Heo wrote: >> Thomas Renninger wrote: >>> Also the system is really old. Why don't you stick to pci=noacpi or >>> even acpi=off? >>> What advantage do you want to get with ACPI (SATA works?)? >> I think this is the second time I see ACPI IRQ routing doesn't work on >> old ACPI. > Hey, that's great. I expected you have seen much more (you inflicted me > on more than two? :) ). Yeah, I tend to redirect all IRQ routing related problems to you. :-P ... > where pci=noacpi helped. IMO not worth an automated detection. > Especially for those old machines..., people know which param to use, you will > produce more grief than any good. > > There were several acpipnp problems recently, but this is another topic and > that needs fixing anyway, Bjorn is doing a real good job here. Hmm... Maybe what's necessary it to detect IRQ misrouting and turn on irqpoll on the specific IRQ (or IRQ handler), which would help 'nobody cared' cases too. Misrouted or killed IRQs cause a lot of griefs and sporadic ones are kinda wide spread. For example, I got hit by one during resume for an IRQ shared by USB, 1394 and sound controller after probably hundreds of successful suspend/resume cycles (not in one go) on the same machine and that somehow caused the sound driver to get stuck leaving no way out than rebooting. Thanks. -- tejun -- 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
