Bug 1115
| Summary: | IO-APIC errors on VIA-KT400 | ||
|---|---|---|---|
| Product: | ACPI | Reporter: | Samuele Kaplun (kaplun) |
| Component: | Config-Interrupts | Assignee: | Len Brown (lenb) |
| Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
| Severity: | high | CC: | acpi-bugzilla |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.5.xx-2.6.0-test3 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Bug Depends on: | 1351 | ||
| Bug Blocks: | 845 | ||
| Attachments: |
Dmesg with IO-APIC
Dmesg without IO-APIC My interrupts on kernel 2.4.22-ck2 with IO-APIC, without ACPI My dmesg on kernel 2.4.22-ck2 with IO-APIC, without ACPI Dmesg of kernel 2.6.0-test11 with #1351 patches And these are the interrupts |
||
|
Description
Samuele Kaplun
2003-08-16 01:28:48 UTC
Created attachment 655 [details]
Dmesg with IO-APIC
Created attachment 656 [details]
Dmesg without IO-APIC
Yes it seems to make all my devices run very well! Wow! That's great! I can use again IO-APIC! I have the same problems with kernel 2.4.x. Is there a way to fix there too? Can you attach the dmesg and /proc/interrupts for the current 2.4 or 2.6 kernel? Does it work for you, or is the unpatched baseline still have problems? thanks, -Len Created attachment 1430 [details]
My interrupts on kernel 2.4.22-ck2 with IO-APIC, without ACPI
These are my interrupts with kernel 2.4.22-ck2. I disabled ACPI because if I
enable both ACPI and IO-APIC I encounter all the problems I said before.
Do you need also with ACPI enabled?
Created attachment 1431 [details]
My dmesg on kernel 2.4.22-ck2 with IO-APIC, without ACPI
This is the Dmesg log with kernel 2.4.22-ck2. no ACPI with IO-APIC, as I
already said in the previous attchment I encounter many problems if I activate
both IO-APIC and ACPI
There are two issues with this system: ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 0 ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 0 ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 0 ACPI: PCI Interrupt Link [ALKD] enabled at IRQ 0 This was the _CRS issue fixed for bug #10, included in 2.4.23 and 2.6.0 ACPI: INT_SRC_OVR (bus[0] irq[0x9] global_irq[0x9] polarity[0x0] trigger[0x0]) This is the SCI low/level issue from bug #1351 Is it possible to re-test this system with 2.6.0 in ACPI+APIC mode with the two patches from bug #1351? I'd like to see the resulting dmesg and /proc/interrupts. thanks, -Len Created attachment 1583 [details] Dmesg of kernel 2.6.0-test11 with #1351 patches Sure! here it is the Dmesg of kernel 2.6.0-test11 with bug #1351 patches. I compiled it with -march=athlon-xp... Previously, I used to compile everything, including the kernel, with "-march=athlon-xp -mcpu=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse". Could it cause shifty problems with the system? Is it always better to compile with -march=athlon-xp only? Created attachment 1584 [details]
And these are the interrupts
These are the interrupts of my machine with kernel 2.6.0-test11 with the two
patches...
Comment on attachment 1583 [details] Dmesg of kernel 2.6.0-test11 with #1351 patches Sure! here it is the Dmesg of kernel 2.6.0-test11 with bug #1351 patches. I compiled it with -march=athlon-xp... Previously, I used to compile everything, including the kernel, with "-march=athlon-xp -mcpu=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse". Could it cause shifty problems with the system? Is it always better to compile with -march=athlon-xp only? Thanks for the logs -- they look good. Do the interrupts work? Be sure to press your power button to see if the acpi interrupts is detected. I'm clue challenged on athlon build options. I generally stick with defaults for stuff like that. thanks, -Len Yes! The USB system seems to work perfectly, now! And when I press the power button of my pc, I find in the system log the signal from the acpi saying that button was pressed! Everything seems to work! Great Work!!! |