public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Hopper <ku4nf@austin.rr.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-rc2-mm4
Date: Sun, 28 Mar 2004 17:59:28 -0600	[thread overview]
Message-ID: <20040328235928.GA32243@obiwan.dummynet> (raw)
In-Reply-To: <1E741-Sh-5@gated-at.bofh.it>

Andrew Morton <akpm@osdl.org> remarked:
> 
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.5-rc2/2.6.5-rc2-mm4/

Hi Andrew,

On a Thinkpad T40p, 2.6.5-rc2-mm4 does not boot successfully,
whereas 2.6.5-rc2 does.  All the typical things (ACPI, CPUFREQ, APIC
& IOAPIC, etc.) are built in.  The -mm4 kernel config was derived
from the working config for 2.6.5-rc2.  

I have to pass the nolapic kernel option to disable the local APIC
in order to successfully boot 2.6.x kernels.  It appears that with
2.6.5-rc2-mm4, this option is ignored, or perhaps there's a ordering
issue with when it is checked.  With -mm4, a message saying that it
is enabling the local APIC appears _before_ the "Kernel command
line: ... nolapic" line appears.

Without the -mm4 patch, the nolapic command line option is parsed
before it would have tried to reenable the local APIC.  With -mm4,
it is parsed after it tries to renable it.  Boom, and then it locks
on "Calibrating delay loop...".

Any relevant config options I should try with/without to help narrow
it down?

Thanks,
Dan

       reply	other threads:[~2004-03-28 23:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1E741-Sh-5@gated-at.bofh.it>
2004-03-28 23:59 ` Dan Hopper [this message]
2004-03-29  0:46   ` 2.6.5-rc2-mm4 Andrew Morton
2004-03-29 14:17     ` 2.6.5-rc2-mm4 Dan Hopper
2004-03-28  2:28 2.6.5-rc2-mm4 Sid Boyce
  -- strict thread matches above, loose matches on Subject: below --
2004-03-26 23:28 2.6.5-rc2-mm4 Sid Boyce
     [not found] <4062E015.2000608@blueyonder.co.uk>
2004-03-25 19:26 ` 2.6.5-rc2-mm3 Sid Boyce
2004-03-26 23:11   ` 2.6.5-rc2-mm4 Sid Boyce
2004-03-26 23:49     ` 2.6.5-rc2-mm4 Andrew Morton
2004-03-26 21:18 2.6.5-rc2-mm4 Andrew Morton
2004-03-26 21:22 ` 2.6.5-rc2-mm4 Andrew Morton
2004-03-26 21:40   ` 2.6.5-rc2-mm4 Christoph Hellwig
2004-03-26 22:00     ` 2.6.5-rc2-mm4 Andrew Morton
2004-03-27 17:54       ` 2.6.5-rc2-mm4 Jens Axboe
2004-03-28 18:54         ` 2.6.5-rc2-mm4 Olaf Hering
2004-03-28 11:31 ` 2.6.5-rc2-mm4 Paul Mackerras
2004-03-29 15:23   ` 2.6.5-rc2-mm4 Tom Rini

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=20040328235928.GA32243@obiwan.dummynet \
    --to=ku4nf@austin.rr.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /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