public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	Arnd Hannemann <Arnd.Hannemann@nets.rwth-aachen.de>,
	LKML <linux-kernel@vger.kernel.org>,
	"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [bisected] 2.6.31 regression: fails to boot as xen guest
Date: Tue, 25 Aug 2009 20:25:10 +0200	[thread overview]
Message-ID: <20090825182510.GA6903@elte.hu> (raw)
In-Reply-To: <4A942BDD.70303@nets.rwth-aachen.de>


* Arnd Hannemann <hannemann@nets.rwth-aachen.de> wrote:

> Pekka Enberg wrote:
> > On Tue, 2009-08-25 at 19:49 +0200, Arnd Hannemann wrote:
> >> Hi Pekka,
> >>
> >> Pekka Enberg wrote:
> >>> On Tue, 2009-08-25 at 18:49 +0200, Arnd Hannemann wrote:
> >>>>> Thanks for doing the bisect! Can we also see your .config
> >>>>> also?
> >>>> Config for -rc7 is attached. My bisect configs were based on
> >>>> that
> >>> Thanks! While we wait for the Xen people, you can try the
> >>> following patch to see if we can narrow the bug down to
> >>> trap_init().
> >> Yes seems to be trap_init(). -rc7 with this patch applied boots up
> >> to the prompt.
> >
> > Thanks for testing! Ingo, what do you think of the following patch?
> > AFAICT, x86-32 is the only architecture playing with traps in
> > mem_init() so this should be the safest fix for 2.6.31.
> 
> Hmm, -rc7 + this fix does not work for me :-/
> Still hangs before any output...

does earlyprintk=vga tell you anything about precisely where it 
hangs?

	Ingo

  reply	other threads:[~2009-08-25 18:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 15:48 [bisected] 2.6.31 regression: fails to boot as xen guest Arnd Hannemann
2009-08-25 16:29 ` Pekka Enberg
2009-08-25 16:49   ` Arnd Hannemann
2009-08-25 16:52     ` Pekka Enberg
2009-08-25 17:49       ` Arnd Hannemann
2009-08-25 18:03         ` Pekka Enberg
2009-08-25 18:08           ` Jeremy Fitzhardinge
2009-08-25 18:22           ` Arnd Hannemann
2009-08-25 18:25             ` Ingo Molnar [this message]
2009-08-25 18:30               ` Jeremy Fitzhardinge
2009-08-25 18:38                 ` Arnd Hannemann
2009-08-25 18:43                   ` Pekka Enberg
2009-08-25 19:31                     ` Jeremy Fitzhardinge
2009-08-25 19:30                   ` Jeremy Fitzhardinge
2009-08-25 18:58             ` Pekka Enberg
2009-08-25 19:07               ` Pekka Enberg
2009-08-25 19:13                 ` Arnd Hannemann
2009-08-26  9:59           ` Benjamin Herrenschmidt
2009-08-25 18:06       ` Jeremy Fitzhardinge
2009-08-25 18:14         ` Pekka Enberg
2009-08-26 11:54 ` Pasi Kärkkäinen
2009-08-26 12:00   ` Pekka Enberg

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=20090825182510.GA6903@elte.hu \
    --to=mingo@elte.hu \
    --cc=Arnd.Hannemann@nets.rwth-aachen.de \
    --cc=benh@kernel.crashing.org \
    --cc=hannemann@nets.rwth-aachen.de \
    --cc=hannes@cmpxchg.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=torvalds@linux-foundation.org \
    --cc=xen-devel@lists.xensource.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