mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Doug Ledford <dledford@redhat.com>
Cc: Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	linux-scsi@vger.kernel.org
Subject: Re: 2.5.43 IO-APIC bug and spinlock deadlock
Date: Thu, 17 Oct 2002 10:29:28 +0200	[thread overview]
Message-ID: <15790.29928.793212.310557@kim.it.uu.se> (raw)
In-Reply-To: <20021017051308.GA10276@redhat.com>

Doug Ledford writes:
 > On Wed, Oct 16, 2002 at 09:40:24PM -0700, Andrew Morton wrote:
 > > Doug Ledford wrote:
 > > > 
 > > > On Wed, Oct 16, 2002 at 11:33:02PM -0400, Doug Ledford wrote:
 > > > > IO-APIC bug: regular kernel, UP, no IO-APIC or APIC on UP enabled, compile
 > > > > fails (does *everyone* run SMP or at least UP + APIC now?)
 > > > 
 > > > OK, this is real.
 > > > 
 > > 
 > > Linus has merged a patch for this.  Does it work for you?  I don't
 > > think you've sent us any error output.
 > > 
 > > 
 > >  include/asm-i386/apic.h |    4 ++--
 > >  include/asm-i386/smp.h  |    2 +-
 > >  2 files changed, 3 insertions(+), 3 deletions(-)
 > 
 > No, tried that, didn't work.  Turn off SMP in your config and also turn 
 > off APIC support entirely, that's when it breaks the compile.

Ah, that rings a bell. Does 'grep MPPARSE' find a match in your .config
even though SMP and *APIC are disabled? That's a scripts/Configure bug:
it enables MPPARSE because CONFIG_X86_LOCAL_APIC was enabled at the start
of this Configure run, even though CONFIG_X86_LOCAL_APIC was disabled later.
Another 'make oldconfig' fixes it.

  reply	other threads:[~2002-10-17  8:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17  3:33 Doug Ledford
2002-10-17  4:28 ` Doug Ledford
2002-10-17  4:40   ` Andrew Morton
2002-10-17  5:13     ` Doug Ledford
2002-10-17  8:29       ` Mikael Pettersson [this message]
2002-10-17  4:49 ` Zwane Mwaikambo
2002-10-18 19:39 ` Bill Davidsen

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=15790.29928.793212.310557@kim.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=akpm@digeo.com \
    --cc=dledford@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mingo@redhat.com \
    /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®