Bug 6517
Summary: | VIA K8T890: irq 10: nobody cared - acpi_irq - AMD64 X2 | ||
---|---|---|---|
Product: | ACPI | Reporter: | Miroslaw Mieszczak (gentoo) |
Component: | Config-Interrupts | Assignee: | Len Brown (lenb) |
Status: | REJECTED UNREPRODUCIBLE | ||
Severity: | normal | CC: | acpi-bugzilla, sergio |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.16 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
Dmesg
lspci kernel config file cpuinfo contents of /proc/interrupts |
Description
Miroslaw Mieszczak
2006-05-08 09:08:35 UTC
Created attachment 8053 [details]
Dmesg
Created attachment 8054 [details]
lspci
Created attachment 8055 [details]
kernel config file
Created attachment 8056 [details]
cpuinfo
Created attachment 8057 [details]
contents of /proc/interrupts
I found that there are 2 independent things. The one is with ACPI interrupt. Right now it happen 1 time. The other one is with USB interrupts, I will make separate bug report for it. As it works for hours before the failure, I expect that the SCI on IRQ10 is working properly and that the problem at hand is some sort of run-time error. If you kill acpid and cat /proc/acpi/event and then press the power button a bunch of times, do you see an event for each press? Does the failure occur also if you boot with "maxcpus=1"? When I killed acpid, and press power button, then after each time the button was released there was generated an event: button/power PWRB 00000080 000000xx where xx is autoincremented event No also I got several: processor CPU0 00000080 00000000 I will try later for maxcpus=1 Now I cannot repeat the Ooops again. Probably the condition was somehow associated with problem on Via EHCI. I propose to make the error invalid now. If I get it again, and have more details, I will reopen it. I try duplicate this bug with mine (http://bugme.osdl.org/show_bug.cgi?id=6419) , Please try lastest kernel 2.6.18-rc7 with http://lkml.org/lkml/diff/2006/9/7/235/1 patch. and use nvidia opensource code drive please re-open if this is reproducible with 2.6.21-rc5 or later. |