From: Andreas Kinzler <ml-xen-devel@hfp.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: jeremy.fitzhardinge@citrix.com, xen-devel@lists.xensource.com
Subject: Re: pvops0 kernel 2.6.32.21 does not boot
Date: Thu, 16 Sep 2010 12:09:01 +0200 [thread overview]
Message-ID: <4C91ECBD.6030105@hfp.de> (raw)
In-Reply-To: <4C912D31.5020209@goop.org>
On 15.09.2010 22:31, Jeremy Fitzhardinge wrote:
> On 09/15/2010 11:39 AM, Andreas Kinzler wrote:
>> On 15.09.2010 19:34, Jeremy Fitzhardinge wrote:
>>>>>> current git stable 2.6.32.x (2968b25) crashes on boot with the
>>>>>> attached debug output. The same config file works perfectly on
>>>>>> 2.6.32.18 (e6b9b2c).
>>>>> Thanks for the report. I've pushed an update to xen/stable-2.6.32.x
>>>>> which should fix this.
>>>> Sorry, still does not boot. I attached the serial console log and
>>>> manually created a traceback from the stack hex dump.
>>> Does adding "mem=1g" to the kernel command line help?
>>
>> No (log attached). But the stacktrace changed back to the first
>> "version":
>>
>> get_phys_to_machine
>> pte_pfn_to_mfn
>> xen_make_pgd
>> __raw_callee_save_xen_make_pgd
>> vmemmap_pgd_populate
>> vmemmap_populate
>> sparse_mem_map_populate
>> sparse_init
> What's your kernel config?
Still the one from the original post
(http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00758.html).
Regards Andreas
next prev parent reply other threads:[~2010-09-16 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 13:44 pvops0 kernel 2.6.32.21 does not boot Andreas Kinzler
2010-09-13 22:05 ` Jeremy Fitzhardinge
2010-09-15 10:41 ` Andreas Kinzler
2010-09-15 17:34 ` Jeremy Fitzhardinge
2010-09-15 18:39 ` Andreas Kinzler
2010-09-15 20:31 ` Jeremy Fitzhardinge
2010-09-16 10:09 ` Andreas Kinzler [this message]
2010-09-22 16:17 ` Andreas Kinzler
2010-09-22 17:23 ` Jeremy Fitzhardinge
2010-10-01 10:53 ` Andreas Kinzler
2010-10-01 16:50 ` Jeremy Fitzhardinge
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=4C91ECBD.6030105@hfp.de \
--to=ml-xen-devel@hfp.de \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=jeremy@goop.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;
as well as URLs for NNTP newsgroup(s).