From: Stefan Smietanowski <stesmi@stesmi.com>
To: Vladimir Lazarenko <vlad@lazarenko.net>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
adq_dvb@lidskialf.net, rl@hellgate.ch,
linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Where do I send APIC victims?
Date: Wed, 03 Sep 2003 16:14:17 +0200 [thread overview]
Message-ID: <3F55F739.4010600@stesmi.com> (raw)
In-Reply-To: <200309031504.03596.vlad@lazarenko.net>
Vladimir Lazarenko wrote:
> On my board, A7V8X, ACPI/APIC works just perfectly with 2.4.22 and KT400
> chipset, 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.
>
> --
> Regards,
> Vladimir
>
> On Wednesday 03 September 2003 14:53, Stephan von Krawczynski wrote:
>
>>On Wed, 03 Sep 2003 12:40:06 +0100
>>
>>Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>>
>>>On Mer, 2003-09-03 at 11:48, Andrew de Quincey wrote:
>>>
>>>>2.4.22 has the ACPI from 2.6 backported into it, (which includes my
>>>>patch for nforce2 boards) so it will start having the same issue with
>>>>the BIOS bug in KT333/KT400 boards.
>>>
>>>It does - 2.4.22pre7 is great on my boxes, 2.4.22 final ACPI is
>>>basically unusable on anything I own thats not intel.
>>
>>I can't back that. At least on all my Serverworks boxes there are no
>>problems with ACPI. I got reports from VIA-bases SMP boards that they are
>>doing well, too. (all for 2.4.22)
And I can say that my Soyo SY-KT600 Ultra (VIA KT600+8237) has ACPI
problems as well. pci=noacpi doesn't help but acpi=off does. It gives
lots of errors that the ACPI tables are buggy when booting claiming
my 8237 SATA controller has gotten IRQ -19 for instance.
Using acpi=off solves the problem. This is with or without the libata
VIA 8237 SATA driver. Without anything it recognizes the chip but
doesn't like using IRQ -19 and doesn't see any disks. With pci=noacpi
it sees the disks but bombs out when trying to get the partition table.
It gets IRQ -19 still there. acpi=off makes it all work.
// Stefan
next prev parent reply other threads:[~2003-09-03 14:14 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 [this message]
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
-- 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=3F55F739.4010600@stesmi.com \
--to=stesmi@stesmi.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