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: Fri, 01 Oct 2010 12:53:29 +0200 [thread overview]
Message-ID: <4CA5BDA9.60603@hfp.de> (raw)
In-Reply-To: <4C9A3B76.9030705@goop.org>
On 22.09.2010 19:23, 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":
>> Are you still checking this? Any news?
> Haven't forgotten about it, but I was waiting for some inspiration to
> strike. Could you try some earlier versions and try to isolate when the
> problem appeared?
Actually I found something very strange. Even the vanilla kernels from
kernel.org stopped working as a domU with the transition of 2.6.32.21 to
2.6.32.22. No output, no log, no nothing, just eating CPU time. Are
there any debug options how to debug domUs that don't output anything?
I am actually starting to wonder if the problems are related to kernels
at all. I tried Xen 3.4.4 with the same result. Perhaps the whole
problem is a binutils/gcc problem. What is your version of binutils /
gcc / glibc?
Regards Andreas
next prev parent reply other threads:[~2010-10-01 10:53 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
2010-09-22 16:17 ` Andreas Kinzler
2010-09-22 17:23 ` Jeremy Fitzhardinge
2010-10-01 10:53 ` Andreas Kinzler [this message]
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=4CA5BDA9.60603@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).