linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Microstar MS-6163 blacklist
@ 2003-06-14  1:46 Ryan Underwood
  2003-06-14  8:19 ` Alan Cox
  0 siblings, 1 reply; 3+ messages in thread
From: Ryan Underwood @ 2003-06-14  1:46 UTC (permalink / raw)
  To: linux-kernel


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

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

* Re: Microstar MS-6163 blacklist
  2003-06-14  1:46 Microstar MS-6163 blacklist Ryan Underwood
@ 2003-06-14  8:19 ` Alan Cox
  2003-06-14  8:42   ` Microstar MS-6163 blacklist [IO-APIC] Ryan Underwood
  0 siblings, 1 reply; 3+ messages in thread
From: Alan Cox @ 2003-06-14  8:19 UTC (permalink / raw)
  To: Ryan Underwood; +Cc: Linux Kernel Mailing List

On Sad, 2003-06-14 at 02:46, Ryan Underwood wrote:
> 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.
> (?)

Its more likely to be about BIOS version than about the board itself


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

* Re: Microstar MS-6163 blacklist [IO-APIC]
  2003-06-14  8:19 ` Alan Cox
@ 2003-06-14  8:42   ` Ryan Underwood
  0 siblings, 0 replies; 3+ messages in thread
From: Ryan Underwood @ 2003-06-14  8:42 UTC (permalink / raw)
  To: linux-kernel

On Sat, Jun 14, 2003 at 09:19:14AM +0100, Alan Cox wrote:
> On Sad, 2003-06-14 at 02:46, Ryan Underwood wrote:
> > 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.
> > (?)
> 
> Its more likely to be about BIOS version than about the board itself

It would have been nice if the original submitter of the patch would
have specified what bios they were using.  IO-APIC support on my board
seemed to be working nicely until eventually it got disabled. :)

I am using the 5.6 bios from their site for the BX Master -- the 6163
Pro (v2) has a totally different BIOS versions and I'm not sure if a
blanket black-list for this board would be the best idea.

Thanks,
-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

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

end of thread, other threads:[~2003-06-14  8:28 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-06-14  1:46 Microstar MS-6163 blacklist Ryan Underwood
2003-06-14  8:19 ` Alan Cox
2003-06-14  8:42   ` Microstar MS-6163 blacklist [IO-APIC] Ryan Underwood

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).