Date: Wed, 11 Jun 2014 15:19:16 +0200
From: Igor Mammedov <imammedo@redhat.com>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: Toshi Kani <toshi.kani@hp.com>, Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [BISECTED][REGRESSION] Kernel does not boot on EeePC
Message-ID: <20140611151916.00723f74@nial.usersys.redhat.com>
In-Reply-To: <20140611130558.GA7173@sucs.org>
References: <20140608090223.GA8703@sucs.org>
	<20140609122616.124ebe43@thinkpad>
	<20140611061624.GA12132@sucs.org>
	<20140611144846.4a55410a@nial.usersys.redhat.com>
	<20140611130558.GA7173@sucs.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

On Wed, 11 Jun 2014 14:05:58 +0100
Sitsofe Wheeler <sitsofe@gmail.com> wrote:

> On Wed, Jun 11, 2014 at 02:48:46PM +0200, Igor Mammedov wrote:
> > On Wed, 11 Jun 2014 07:16:24 +0100
> > Sitsofe Wheeler <sitsofe@gmail.com> wrote:
> > 
> > > It basically gives up just before Initializing CPU#0. The following is
> > > an approximation of the boot messages that I see on the screen (the
> > > early ones are gone before I can eyeball them so this is a blend of a
> > > previous dmesg and what I see on the screen during a failure):
> > Thanks for answer,
> > 
> > I've overlooked nonsmp case when testing where no one sets
> > cpu_callout_mask for boot CPU and as result kernel hangs in cpu_init()
> 
> What gave you the tip off?
Just that you were booting on 1 core CPU with custom config,
then the only place where it could hang would be cpu_init().

--
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/