From: Nicolas Mailhot <Nicolas.Mailhot@laposte.net>
To: linux-kernel@vger.kernel.org
Cc: Roger Luethi <rl@hellgate.ch>,
Andrew de Quincey <adq@lidskialf.net>,
Danny ter Haar <dth@ncc1701.cistron.net>,
Len Brown <len.brown@intel.com>
Subject: Re: [ACPI] Where do I send APIC victims?
Date: Wed, 03 Sep 2003 13:18:51 +0200 [thread overview]
Message-ID: <1062587931.3679.5.camel@ulysse.olympe.o2t> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Roger Luethi wrote :
> As the maintainer of via-rhine, I get bug reports that almost in their
> entirety are "fixed" by turning off APIC and/or ACPI. This has been going
> on for several months now. Every now and then, something promising gets
> posted on LKML, but so far if anything I've seen an _increase_ in those bug
> reports. Maybe a fix is floating around and this will be a non-issue RSN. I
> simply can't tell, since I don't have any IO-APIC hardware to play with.
> Instead of just telling everybody to turn off APIC, I'd like to point bug
> reporters to the proper place and tell them what information they should
> provide so it can get fixed for real. According to MAINTAINERS, Ingo Molnar
> does Intel APIC, but the problems are with VIA chip sets. So where do I
> send my users? Any takers?
As far as I can say (as a lowly 2.6 Via user) for 2.5/2.6 the relevant
bug is :
http://bugzilla.kernel.org/show_bug.cgi?id=845
Just tell your users to open a new bug (with system info, dmesg,
interrupts, dmidecode, acpidmp, etc) and make it block bug #845
resolution.
(btw the first registered via acpi bug is november 2002 bug #10, it just
got an initial fix that also worked for another #845 child bug. So
crossing fingers all this will be resolved soonish)
Cheers,
--
Nicolas Mailhot
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-09-03 11:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 11:18 Nicolas Mailhot [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=1062587931.3679.5.camel@ulysse.olympe.o2t \
--to=nicolas.mailhot@laposte.net \
--cc=adq@lidskialf.net \
--cc=dth@ncc1701.cistron.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rl@hellgate.ch \
/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®