Date: Fri, 13 Jun 2003 20:46:46 -0500
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-kernel@vger.kernel.org
Subject: Microstar MS-6163 blacklist
Message-ID: <20030614014646.GD1010@dbz.icequake.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1462
Lines: 39


In other news, I noticed recently that the IO-APIC on my MS-6163
BX-Master was being disabled at boot by the kernel, due to a recently
introduced blacklist:

{ apm_kills_local_apic, "Microstar 6163",
	{ MATCH(DMI_BOARD_VENDOR, "MICRO-STAR INTERNATIONAL CO., LTD"),
	  MATCH(DMI_BOARD_NAME, "MS-6163"),
	  NO_MATCH, NO_MATCH } },

Consulting mailing list archives indicated that there is some sort of
problem with the IO-APIC on the MS-6163 Pro and APM events.  However,
this seems a rather clumsy fix to the problem, since it disabled the
IO-APIC on _all_ MS-6163 boards rather than just the Pro, and also
regardless of whether APM support is even enabled (I don't enable it and
don't use it at all).

The DMI string for my board is:
Board Information Block
	Vendor: MICRO-STAR INTERNATIONAL CO., LTD
	Product: MS-6163 (i440BX)
	Version: 3.X
	Serial Number:

It would seem that if a closer match were performed, using the version
number of the board (3.X in my case, likely 2.X in the case of the
broken Pro), it would be a better idea.  Perhaps another alternative
solution would be to only disable the IO-APIC if CONFIG_APM is defined.
(?)

Thoughts?
	  
-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/