From: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Arnd Hannemann <Arnd.Hannemann@nets.rwth-aachen.de>,
Pekka Enberg <penberg@cs.helsinki.fi>,
LKML <linux-kernel@vger.kernel.org>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.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:38:14 +0200 [thread overview]
Message-ID: <4A942F96.7000900@nets.rwth-aachen.de> (raw)
In-Reply-To: <4A942DB9.3020209@goop.org>
Jeremy Fitzhardinge wrote:
> On 08/25/09 11:25, Ingo Molnar wrote:
>> * 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?
>>
>
> It's a Xen domain, so it should be earlyprintk=xen
>
> J
>
Here is the output with earlyprintk=xen and the second patch from pekka
applied:
(early) [ 0.000000] Initializing CPU#0
(early) [ 0.000000] Checking if this processor honours the WP bit
even in supervisor mode...(early)
(early) [ 0.000000] BUG: unable to handle kernel (early) NULL pointer
dereference(early) at (null)
(early) [ 0.000000] IP:(early) [<c1192993>]
xen_evtchn_do_upcall+0xd3/0x160
(early) [ 0.000000] *pdpt = 0000000008386001 (early)
(early) [ 0.000000] Thread overran stack, or stack corrupted
(early) [ 0.000000] Oops: 0000 [#1] (early) SMP (early)
(early) [ 0.000000] last sysfs file:
(early) [ 0.000000] Modules linked in:(early)
(early) [ 0.000000]
(early) [ 0.000000] Pid: 0, comm: swapper Not tainted
(2.6.31-rc7-pae-um #10)
(early) [ 0.000000] EIP: 0061:[<c1192993>] EFLAGS: 00010046 CPU: 0
(early) [ 0.000000] EIP is at xen_evtchn_do_upcall+0xd3/0x160
(early) [ 0.000000] EAX: 00000004 EBX: 00000000 ECX: 00000004 EDX:
ffffffff
(early) [ 0.000000] ESI: fffffffe EDI: 00000000 EBP: 00000000 ESP:
c1413e64
(early) [ 0.000000] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: e021
(early) [ 0.000000] Process swapper (pid: 0, ti=c1412000
task=c13d11a0 task.ti=c1412000)
(early) [ 0.000000] Stack:
(early) [ 0.000000] f5793000(early) c146d9f0(early)
c146d9f0(early) 00000000(early) c1413e9c(early) 00000000(early)
00000000(early) c3a01020(early)
(early) [ 0.000000] <0>(early) 00000000(early) eec06067(early)
c000cff8(early) 00000000(early) 00000000(early) c10086d7(early)
eec06067(early) c000cff8(early)
(early) [ 0.000000] <0>(early) f55ff000(early) c000cff8(early)
00000000(early) 00000000(early) c13d7d60(early) c101e021(early)
c141e021(early) c10100d8(early)
(early) [ 0.000000] Call Trace:
(early) [ 0.000000] [<c10086d7>] ? xen_do_upcall+0x7/0xc
(early) [ 0.000000] [<c101e021>] ? ptep_set_access_flags+0x1/0x80
(early) [ 0.000000] [<c141e021>] ? find_e820_area_size+0x51/0x330
(early)
Best regards,
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
Ingo Molnar <mingo@elte.hu>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
Arnd Hannemann <Arnd.Hannemann@nets.rwth-aachen.de>
Subject: Re: [bisected] 2.6.31 regression: fails to boot as xen guest
Date: Tue, 25 Aug 2009 20:38:14 +0200 [thread overview]
Message-ID: <4A942F96.7000900@nets.rwth-aachen.de> (raw)
In-Reply-To: <4A942DB9.3020209@goop.org>
Jeremy Fitzhardinge wrote:
> On 08/25/09 11:25, Ingo Molnar wrote:
>> * 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?
>>
>
> It's a Xen domain, so it should be earlyprintk=xen
>
> J
>
Here is the output with earlyprintk=xen and the second patch from pekka
applied:
(early) [ 0.000000] Initializing CPU#0
(early) [ 0.000000] Checking if this processor honours the WP bit
even in supervisor mode...(early)
(early) [ 0.000000] BUG: unable to handle kernel (early) NULL pointer
dereference(early) at (null)
(early) [ 0.000000] IP:(early) [<c1192993>]
xen_evtchn_do_upcall+0xd3/0x160
(early) [ 0.000000] *pdpt = 0000000008386001 (early)
(early) [ 0.000000] Thread overran stack, or stack corrupted
(early) [ 0.000000] Oops: 0000 [#1] (early) SMP (early)
(early) [ 0.000000] last sysfs file:
(early) [ 0.000000] Modules linked in:(early)
(early) [ 0.000000]
(early) [ 0.000000] Pid: 0, comm: swapper Not tainted
(2.6.31-rc7-pae-um #10)
(early) [ 0.000000] EIP: 0061:[<c1192993>] EFLAGS: 00010046 CPU: 0
(early) [ 0.000000] EIP is at xen_evtchn_do_upcall+0xd3/0x160
(early) [ 0.000000] EAX: 00000004 EBX: 00000000 ECX: 00000004 EDX:
ffffffff
(early) [ 0.000000] ESI: fffffffe EDI: 00000000 EBP: 00000000 ESP:
c1413e64
(early) [ 0.000000] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: e021
(early) [ 0.000000] Process swapper (pid: 0, ti=c1412000
task=c13d11a0 task.ti=c1412000)
(early) [ 0.000000] Stack:
(early) [ 0.000000] f5793000(early) c146d9f0(early)
c146d9f0(early) 00000000(early) c1413e9c(early) 00000000(early)
00000000(early) c3a01020(early)
(early) [ 0.000000] <0>(early) 00000000(early) eec06067(early)
c000cff8(early) 00000000(early) 00000000(early) c10086d7(early)
eec06067(early) c000cff8(early)
(early) [ 0.000000] <0>(early) f55ff000(early) c000cff8(early)
00000000(early) 00000000(early) c13d7d60(early) c101e021(early)
c141e021(early) c10100d8(early)
(early) [ 0.000000] Call Trace:
(early) [ 0.000000] [<c10086d7>] ? xen_do_upcall+0x7/0xc
(early) [ 0.000000] [<c101e021>] ? ptep_set_access_flags+0x1/0x80
(early) [ 0.000000] [<c141e021>] ? find_e820_area_size+0x51/0x330
(early)
Best regards,
Arnd
next prev parent reply other threads:[~2009-08-25 18:38 UTC|newest]
Thread overview: 38+ 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:29 ` Pekka Enberg
2009-08-25 16:49 ` Arnd Hannemann
2009-08-25 16:49 ` Arnd Hannemann
2009-08-25 16:52 ` Pekka Enberg
2009-08-25 16:52 ` Pekka Enberg
2009-08-25 17:49 ` Arnd Hannemann
2009-08-25 17:49 ` Arnd Hannemann
2009-08-25 18:03 ` Pekka Enberg
2009-08-25 18:03 ` Pekka Enberg
2009-08-25 18:08 ` Jeremy Fitzhardinge
2009-08-25 18:08 ` Jeremy Fitzhardinge
2009-08-25 18:22 ` Arnd Hannemann
2009-08-25 18:22 ` Arnd Hannemann
2009-08-25 18:25 ` Ingo Molnar
2009-08-25 18:25 ` Ingo Molnar
2009-08-25 18:30 ` Jeremy Fitzhardinge
2009-08-25 18:38 ` Arnd Hannemann [this message]
2009-08-25 18:38 ` Arnd Hannemann
2009-08-25 18:43 ` Pekka Enberg
2009-08-25 18:43 ` Pekka Enberg
2009-08-25 19:31 ` Jeremy Fitzhardinge
2009-08-25 19:31 ` Jeremy Fitzhardinge
2009-08-25 19:30 ` 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:07 ` Pekka Enberg
2009-08-25 19:13 ` Arnd Hannemann
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:06 ` Jeremy Fitzhardinge
2009-08-25 18:14 ` Pekka Enberg
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=4A942F96.7000900@nets.rwth-aachen.de \
--to=hannemann@nets.rwth-aachen.de \
--cc=Arnd.Hannemann@nets.rwth-aachen.de \
--cc=benh@kernel.crashing.org \
--cc=hannes@cmpxchg.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.