Bug 9795
Summary: | Confusion caused by pci=routeirq console messages | ||
---|---|---|---|
Product: | ACPI | Reporter: | Artem Goncharov (artem.goncharov) |
Component: | Config-Interrupts | Assignee: | ykzhao (yakui.zhao) |
Status: | REJECTED INVALID | ||
Severity: | low | CC: | bjorn.helgaas |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.24-rc8 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: | dmesg |
Description
Artem Goncharov
2008-01-22 10:24:37 UTC
Hi, Artem There is no boot parameter about pci=routeacpi. Will you please confirm whether the boot option of "pci=routeirq" is added ? If the boot option of "pci=routeirq" is added, the above message should be reported. The option is to enable the interrupt of all PCI devices. It will be great if you can attach the output of dmesg. Thanks. Created attachment 14547 [details]
dmesg
dmesg
Sorry, pci=routeirq option was added (mistyping ;-) Hi, Artem Thanks for the confirm. From the dmesg in comment #2 it seems that there is no error about the laptop. The only confusing is that OSPM reports ACPI PCI interrupt message when boot option of pci=routeirq is added. The boot option of "pci=routeirq" is used to enable the interrupt of all PCI devices before loading PCI driver for PCI device and OSPM will report the above message. So the bug will be rejected. If there's confusion here, I'm afraid I'm responsible for it, since I added the "pci=routeirq" option. Without "pci=routeirq", PCI interrupts are enabled only when a driver enables a device. When you specify "pci=routeirq", the only thing that changes is that we enable the interrupts for all devices right away at boot, before any drivers claim devices. What would make this less confusing to you? Would you just rather not see the messages about how the interrupts are routed? That's useful debugging information, so I'd like to keep that in some form. |