From: Mike Fedyk <mfedyk@matchmail.com>
To: Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: Vladimir Lazarenko <vlad@lazarenko.net>,
Stephan von Krawczynski <skraw@ithnet.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
rl@hellgate.ch, linux-kernel@vger.kernel.org,
acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Where do I send APIC victims?
Date: Wed, 3 Sep 2003 17:28:12 -0700 [thread overview]
Message-ID: <20030904002812.GI16361@matchmail.com> (raw)
In-Reply-To: <200309031709.08286.adq_dvb@lidskialf.net>
[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]
On Wed, Sep 03, 2003 at 05:09:08PM +0100, Andrew de Quincey wrote:
> On Wednesday 03 Sep 2003 2:04 pm, Vladimir Lazarenko wrote:
> > On my board, A7V8X, ACPI/APIC works just perfectly with 2.4.22 and KT400
> > chipset,
>
> Does it indeed? Sounds like that BIOS doesn't have the bug! Can you send me
> your /proc/acpi/dsdt so I can see what is different? Be really good if I can
> nick the code out of that for the other boards!
>
I have a board like this too. It works fine with 2.4 & 2.6. The only
trouble I've had has been a hard drive. (hardware)
> > alas on A7N8X Deluxe board with nForce2 chipsets it causes nasty
> > hangups.
> > Machine just simply freezes, no oops, nothing whatsoever.
> >
> > Disabling APIC solved the problem.
>
> Does it work with ACPI disabled, but APIC enabled?
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge
00:0a.0 VGA compatible controller: Trident Microsystems TGUI 9660/938x/968x
(rev d3)
00:0e.0 RAID bus controller: CMD Technology Inc PCI0680 (rev 02)
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus
Master IDE (rev 06)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
[-- Attachment #2: dsdt --]
[-- Type: application/octet-stream, Size: 10622 bytes --]
next prev parent reply other threads:[~2003-09-04 0:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 8:08 Where do I send APIC victims? 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20030904002812.GI16361@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=adq_dvb@lidskialf.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rl@hellgate.ch \
--cc=skraw@ithnet.com \
--cc=vlad@lazarenko.net \
/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