linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Where do I send APIC victims?
@ 2003-09-03  8:08 Roger Luethi
  2003-09-03 10:23 ` [ACPI] " Andrew de Quincey
  2003-09-03 10:23 ` Andrew de Quincey
  0 siblings, 2 replies; 18+ messages in thread
From: Roger Luethi @ 2003-09-03  8:08 UTC (permalink / raw)
  To: linux-kernel; +Cc: acpi-devel

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?

Roger

^ permalink raw reply	[flat|nested] 18+ messages in thread
* Re: [ACPI] Where do I send APIC victims?
@ 2003-09-03 11:18 Nicolas Mailhot
  0 siblings, 0 replies; 18+ messages in thread
From: Nicolas Mailhot @ 2003-09-03 11:18 UTC (permalink / raw)
  To: linux-kernel; +Cc: Roger Luethi, Andrew de Quincey, Danny ter Haar, Len Brown

[-- 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 --]

^ permalink raw reply	[flat|nested] 18+ messages in thread

end of thread, other threads:[~2003-09-04  7:27 UTC | newest]

Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
2003-09-03 11:18 Nicolas Mailhot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).