From: Stephan von Krawczynski <skraw-DcQCyzbjH0jQT0dZR+AlfA@public.gmane.org>
To: Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
Cc: adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org,
rl-7uj+XXdSDtwfv37vnLkPlQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [ACPI] Where do I send APIC victims?
Date: Wed, 3 Sep 2003 14:53:56 +0200 [thread overview]
Message-ID: <20030903145356.35b9a192.skraw@ithnet.com> (raw)
In-Reply-To: <1062589205.19059.6.camel-Z+iYsftfazAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>
On Wed, 03 Sep 2003 12:40:06 +0100
Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org> 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)
Regards,
Stephan
next prev parent reply other threads:[~2003-09-03 12:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 8:08 Where do I send APIC victims? Roger Luethi
[not found] ` <20030903080852.GA27649-NW/W/tFpkLjPJA67Yv3YjA@public.gmane.org>
2003-09-03 10:23 ` [ACPI] " Andrew de Quincey
2003-09-03 10:23 ` Andrew de Quincey
[not found] ` <200309031123.58713.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-03 9:38 ` Roger Luethi
[not found] ` <20030903093808.GA28594-NW/W/tFpkLjPJA67Yv3YjA@public.gmane.org>
2003-09-03 10:48 ` Andrew de Quincey
[not found] ` <200309031148.03941.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-03 11:40 ` Alan Cox
[not found] ` <1062589205.19059.6.camel-Z+iYsftfazAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>
2003-09-03 12:53 ` Stephan von Krawczynski [this message]
[not found] ` <20030903145356.35b9a192.skraw-DcQCyzbjH0jQT0dZR+AlfA@public.gmane.org>
2003-09-03 13:04 ` Vladimir Lazarenko
[not found] ` <200309031504.03596.vlad-Qw1rWqDNyQwB085IDyDbTA@public.gmane.org>
2003-09-03 14:14 ` Stefan Smietanowski
[not found] ` <3F55F739.4010600-uPWUOVYScjfQT0dZR+AlfA@public.gmane.org>
2003-09-03 16:10 ` Andrew de Quincey
[not found] ` <200309031710.49411.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-03 18:21 ` Marcelo Tosatti
2003-09-03 16:09 ` [ACPI] " Andrew de Quincey
[not found] ` <200309031709.08286.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-04 0:28 ` Mike Fedyk
2003-09-03 18:13 ` Marcelo Tosatti
[not found] ` <Pine.LNX.4.44.0309031511420.6102-100000-IP5UegVbiV6sTnJN9+BGXg@public.gmane.org>
2003-09-03 18:15 ` Marcelo Tosatti
2003-09-03 22:44 ` [ACPI] " Sérgio Monteiro Basto
2003-09-03 13:19 ` Greg Meyer
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=20030903145356.35b9a192.skraw@ithnet.com \
--to=skraw-dcqcyzbjh0jqt0dzr+alfa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org \
--cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rl-7uj+XXdSDtwfv37vnLkPlQ@public.gmane.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