All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Igor Mammedov <imammedo@redhat.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
Date: Wed, 11 Jun 2014 14:05:58 +0100	[thread overview]
Message-ID: <20140611130558.GA7173@sucs.org> (raw)
In-Reply-To: <20140611144846.4a55410a@nial.usersys.redhat.com>

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?

Additionally, does that also mean Ingo's test stand doesn't run nonsmp
kernels?

-- 
Sitsofe | http://sucs.org/~sits/

  reply	other threads:[~2014-06-11 13:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-08  9:02 [BISECTED][REGRESSION] Kernel does not boot on EeePC Sitsofe Wheeler
2014-06-08  9:45 ` Ingo Molnar
2014-06-08 17:50   ` H. Peter Anvin
2014-06-09 14:02     ` Ingo Molnar
2014-06-10 19:19       ` Sitsofe Wheeler
2014-06-09 10:26 ` Igor Mammedov
2014-06-11  6:16   ` Sitsofe Wheeler
2014-06-11 12:48     ` Igor Mammedov
2014-06-11 13:05       ` Sitsofe Wheeler [this message]
2014-06-11 13:19         ` Igor Mammedov

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=20140611130558.GA7173@sucs.org \
    --to=sitsofe@gmail.com \
    --cc=imammedo@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=toshi.kani@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.