Bug 3096
Summary: | irq 11: nobody cared! on Toshiba laptop | ||
---|---|---|---|
Product: | ACPI | Reporter: | Ville Herva (v) |
Component: | Config-Interrupts | Assignee: | Len Brown (lenb) |
Status: | REJECTED UNREPRODUCIBLE | ||
Severity: | normal | CC: | mishu |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.7-mm7, fedora kernel-2.6.6-1.435.2.3 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: | acpidmp output |
Description
Ville Herva
2004-07-18 10:25:07 UTC
The problem remains the same with 2.6.7-mm7. full acpi, nor "noacpi" work. With "noacpi acpi=off", it works. The full acpi dmesg is in attachment #3341 [details]: http://bugme.osdl.org/attachment.cgi?id=3341&action=view Later I realized that I seem to have confused the (non-existent) "noacpi" argument with the (correct) "pci=noacpi". Using "pci=noacpi acpi=noirq" it seems to work. 2.6.8-rc2-mm1 still has the same problem. Created attachment 3452 [details]
acpidmp output
> With 2.4.x this machine has no problems
Is that an ACPI-enabled 2.4.x kernel?
If yes, can you attach the dmesg and /proc/interrupts?
I expect that acpi=noirq will work(around) just as well as pci=noapic
Please attach the output from lspci -vv
same with 2.6.9? Sorry to be a slow responder with this. The problem is, I only get to use the laptop once in a while my coworkers typically use W2k on it. Once I get to use it again (it has been long since I used it), I'll compile a new version and send you lspci -vv. Is 2.6.9, 2.6.10-rc? or 2.6.10-rc?-mm? preferable once I get to try new kernels? they're all interesting, depending on if they work or not, probably in this order: 2.6.9 2.6.10-rc? 2.6.10-rc?-mm? Sorry, I was hasty and went with 2.6.10-rc2-mm1 straight off. With this kernel, ACPI turned on, I get no "Nobody cared" messages at all. Not from the sound card driver, not from e100. I can even software suspend and resume without those messages (sound doesn't work after that, but I guess I could work around that by unloading sound modules first.) thanks for verifying that 2.6.10-rc2-mm1 works. yes, sound suspend/resume is a different issue, and I noticed a fix for it in 2.6.10 today, so you might try that again soon. closing. |