All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Reinbrech <andi.reinbrech@darwinistic.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Kernel 3.0 crashes 4.2 unstable on some hardware
Date: Sat, 30 Jul 2011 22:30:34 +0200	[thread overview]
Message-ID: <4E3469EA.8070309@darwinistic.com> (raw)

Hi,

I have successfully set up a xen-unstable machine with kernel 3.0, on an 
old core2duo - running win2008 in hvm works 100%.  When trying on a new 
i5 machine though, the same kernel reboots the machine immediately after 
xen starts up dom0.

It appears to be during the stage of graphics/framebuffer initialisation 
but the serial console does not show any details.  I have tried 
nomodeset with no changes.

What would the xen-gurus need from me to debug this in more detail?  The 
machine (same xen 4.2) boots fine with the 2.6.32.xendom0 kernel.  I was 
expecting at least an exception, core dump or freeze, but this reboot is 
quite strange and very hard to debug.

Thanks!
Andi

             reply	other threads:[~2011-07-30 20:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30 20:30 Andi Reinbrech [this message]
2011-08-03 15:34 ` Kernel 3.0 crashes 4.2 unstable on some hardware Konrad Rzeszutek Wilk

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=4E3469EA.8070309@darwinistic.com \
    --to=andi.reinbrech@darwinistic.com \
    --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.