From: Tony Lindgren <tony@atomide.com>
To: linux-kernel@vger.kernel.org
Cc: acpi-devel-request@lists.sourceforge.net, patches@x86-64.org,
ak@suse.de, len.brown@intel.com, pavel@ucw.cz,
ccheney@debian.org
Subject: [PATCH] x86_64 VIA chipset IOAPIC fix
Date: Wed, 24 Mar 2004 19:34:34 -0800 [thread overview]
Message-ID: <20040325033434.GB8139@atomide.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]
Hi Andi & Len,
Sorry for cross posting all over the place, I tried to CC some people who have
been bugged by this bug.
I finally got the IOAPIC working on my eMachines m6805 amd64 laptop with the
following patch. I have not tried it on any other machines, so can you guys
please check the sanity and make the necessary changes if needed?
This fixes at least ACPI bug 2090:
http://bugme.osdl.org/show_bug.cgi?id=2090
Might fix some other x86 VIA bugs too?
To turn it on, apic still needs to be specified in the kernel cmdline:
root=/dev/hda3 ro psmouse.proto=imps apic console=tty0
Now cat /proc/interrupts shows:
0: 70843 IO-APIC-edge timer
1: 9 IO-APIC-edge i8042
2: 0 XT-PIC cascade
8: 0 IO-APIC-edge rtc
10: 0 IO-APIC-level acpi
12: 44 IO-APIC-edge i8042
14: 2734 IO-APIC-edge ide0
15: 19 IO-APIC-edge ide1
17: 0 IO-APIC-level yenta
18: 0 IO-APIC-level eth0
21: 565 IO-APIC-level ehci_hcd, uhci_hcd, uhci_hcd, uhci_hcd
22: 0 IO-APIC-level VIA8233
23: 6 IO-APIC-level eth1
NMI: 12
LOC: 70752
ERR: 0
MIS: 0
And things are just working :)
Regards,
Tony
And here's the patch, it's against 2.6.5-rc2:
[-- Attachment #2: patch-amd64-via-ioapic --]
[-- Type: text/plain, Size: 1170 bytes --]
diff -Nru a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c
--- a/drivers/acpi/pci_link.c Wed Feb 25 21:11:46 2004
+++ b/drivers/acpi/pci_link.c Wed Mar 24 18:47:48 2004
@@ -402,10 +402,8 @@
ACPI_DEBUG_PRINT((ACPI_DB_ERROR, "Unable to read status\n"));
return_VALUE(result);
}
- if (!link->device->status.enabled) {
- ACPI_DEBUG_PRINT((ACPI_DB_ERROR, "Link disabled\n"));
- return_VALUE(-ENODEV);
- }
+ if (!link->device->status.enabled)
+ ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Link disabled: VIA chipset? Trying to continue\n"));
/* Make sure the active IRQ is the one we requested. */
result = acpi_pci_link_try_get_current(link, irq);
@@ -415,11 +413,9 @@
if (link->irq.active != irq) {
ACPI_DEBUG_PRINT((ACPI_DB_ERROR,
- "Attempt to enable at IRQ %d resulted in IRQ %d\n",
- irq, link->irq.active));
- link->irq.active = 0;
- acpi_ut_evaluate_object (link->handle, "_DIS", 0, NULL);
- return_VALUE(-ENODEV);
+ "Attempt to enable at IRQ %d resulted in IRQ %d: VIA chipset? Using irq %d\n",
+ irq, link->irq.active, irq));
+ link->irq.active = irq;
}
ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Set IRQ %d\n", link->irq.active));
next reply other threads:[~2004-03-25 3:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 3:34 Tony Lindgren [this message]
2004-03-26 0:15 ` [PATCH] x86_64 VIA chipset IOAPIC fix Len Brown
2004-03-26 0:47 ` Tony Lindgren
2004-03-26 3:04 ` Chris Cheney
2004-03-26 3:11 ` Tony Lindgren
2004-03-26 3:13 ` Len Brown
2004-03-26 3:20 ` Chris Cheney
2004-03-26 3:35 ` Tony Lindgren
2004-03-26 4:21 ` Len Brown
2004-03-26 4:34 ` Chris Cheney
2004-03-26 5:10 ` Tony Lindgren
2004-03-30 3:17 ` Randy.Dunlap
2004-03-26 5:02 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2004-04-16 10:53 HurryLin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040325033434.GB8139@atomide.com \
--to=tony@atomide.com \
--cc=acpi-devel-request@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=ccheney@debian.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox