public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Dave Jones <davej@redhat.com>
Cc: Michael Ellerman <michael@ellerman.id.au>,
	linux-kernel@vger.kernel.org, Chris McDermott <lcm@us.ibm.com>
Subject: Re: [PATCH] leave APIC code inactive by default on i386
Date: Wed, 01 Mar 2006 15:29:31 -0800	[thread overview]
Message-ID: <1141255771.30185.64.camel@localhost.localdomain> (raw)
In-Reply-To: <20060301225103.GE1440@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

On Wed, 2006-03-01 at 17:51 -0500, Dave Jones wrote:
> On Wed, Mar 01, 2006 at 02:47:38PM -0800, Darrick J. Wong wrote:
>  > On Wed, 2006-03-01 at 17:14 -0500, Dave Jones wrote:
>  > 
>  > > In light of Matthew's comments in this thread though, I'm also wondering
>  > > if we can now get by without this diff, and just enable it by default now
>  > > that the kernel respects that the BIOS and leaves it alone if it's been
>  > > disabled.
>  > 
>  > Actually, it seems that there are Lenovo ThinkCenter P4 machines with
>  > buggy BIOSes that tell us that we can enable the APIC ... but doing so
>  > eventually causes the system to hang.  Granted, the Google-recommended
>  > fixes are "noapic" or "Update the BIOS", but perhaps it would be best to
>  > leave it off _except_ for the few cases where we know that we need it.
>  > 
>  > (Then again, the correct solution in this case is to fix the BIOS...)
> 
> Indeed. And also blacklist the bad ones with DMI entries.

Yeah.  Since the kernel honors the BIOS's APIC settings, we might as
well enable the APIC code by default.

--D

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

  reply	other threads:[~2006-03-01 23:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20  1:20 [PATCH] leave APIC code inactive by default on i386 Darrick J. Wong
2006-01-20 14:42 ` Jan Engelhardt
2006-03-01  3:57 ` Michael Ellerman
2006-03-01  4:33   ` Dave Jones
2006-03-01  5:10     ` Michael Ellerman
2006-03-01 13:38       ` Dave Jones
2006-03-01 13:52         ` Matthew Garrett
2006-03-01  6:36     ` Zwane Mwaikambo
2006-03-01 13:39       ` Dave Jones
2006-03-01 21:29     ` Darrick J. Wong
2006-03-01 22:14       ` Dave Jones
2006-03-01 22:47         ` Darrick J. Wong
2006-03-01 22:51           ` Dave Jones
2006-03-01 23:29             ` Darrick J. Wong [this message]
2006-03-06 12:50     ` Pavel Machek
2006-03-06 17:17       ` Dave Jones
2006-03-06 17:41         ` Pavel Machek
2006-03-06 17:52           ` Dave Jones
2006-03-06 17:58             ` Pavel Machek
2006-03-06 18:17               ` Dave Jones
2006-03-06 19:05                 ` Darrick J. Wong

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=1141255771.30185.64.camel@localhost.localdomain \
    --to=djwong@us.ibm.com \
    --cc=davej@redhat.com \
    --cc=lcm@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    /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