From: Matthias Andree <matthias.andree@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [ACPI] Where do I send APIC victims?
Date: Wed, 3 Sep 2003 13:05:52 +0200 [thread overview]
Message-ID: <20030903110552.GF27875@merlin.emma.line.org> (raw)
In-Reply-To: <200309031123.58713.adq_dvb@lidskialf.net>
On Wed, 03 Sep 2003, Andrew de Quincey wrote:
> Hi, I'm trying to develop patches for ACPI IRQ issues.
>
> Are these VIA KT333/KT400 chipsets? If so, there's a known bug in many BIOSes
> with these chipsets. I'm waiting on some docs from VIA to fix this issue.
I'm looking after a box with EPoX 8K9A2+ board (IIRC), with KT400 chip
set. Booting with ACPI enabled (i. e. no acpi=off in kernel command
line) makes most interrupts (network, disk) invisible. acpi=off fixes
this. I haven't bothered to report this because it's running some
SuSE-patched 2.4.20 kernel (they did patch newer ACPI, "Subsystem
revision 20030228").
Is testing a newer kernel or ACPI stuff worthwhile or should I wait?
It's a production machine, so "see if this works" is out of the game,
"it should work" can be tested in times of low load but not necessarily
on short notice.
Is this any help?
<6>ACPI: Subsystem revision 20030228
<6>ACPI: Disabled via command line (acpi=off)
<6>PCI: PCI BIOS revision 2.10 entry at 0xfb380, last bus=1
<6>PCI: Using configuration type 1
<6>PCI: Probing PCI hardware
<4>PCI: ACPI tables contain no PCI IRQ routing entries
<4>PCI: Probing PCI hardware (bus 00)
<6>PCI: Using IRQ router VIA [1106/3177] at 00:11.0
That 00:11.0 is:
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
next prev parent reply other threads:[~2003-09-04 7:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 8:08 Roger Luethi
2003-09-03 10:23 ` [ACPI] " Andrew de Quincey
2003-09-03 10:23 ` Andrew de Quincey
2003-09-03 9:38 ` Roger Luethi
2003-09-03 10:30 ` Danny ter Haar
2003-09-03 10:48 ` Andrew de Quincey
2003-09-03 11:40 ` Alan Cox
2003-09-03 12:53 ` Stephan von Krawczynski
2003-09-03 13:04 ` Vladimir Lazarenko
2003-09-03 14:14 ` Stefan Smietanowski
2003-09-03 16:10 ` Andrew de Quincey
2003-09-03 16:09 ` Andrew de Quincey
2003-09-04 0:28 ` Mike Fedyk
2003-09-03 18:13 ` Marcelo Tosatti
2003-09-03 18:15 ` Marcelo Tosatti
2003-09-03 22:44 ` Sérgio Monteiro Basto
2003-09-03 11:05 ` Matthias Andree [this message]
2003-09-03 11:18 Nicolas Mailhot
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=20030903110552.GF27875@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®