From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log
Date: Tue, 3 Aug 2010 11:45:41 -0400 [thread overview]
Message-ID: <20100803154541.GA16122@phenom.dumpdata.com> (raw)
In-Reply-To: <698099271.20100803173057@eikelenboom.it>
On Tue, Aug 03, 2010 at 05:30:57PM +0200, Sander Eikelenboom wrote:
> Hi All,
>
> I'm experiencing for what it seems a random freeze with current xen-4.0-testing, pvops dom0 2.6.32.16 kernel, most of the time within 2 days after rebooting.
>
You did not experience the freeze with 2.6.32.15?
> Symptoms:
> - Complete freeze, only power cycle does work.
> - No bug output/stacktrace in serial log / on screen.
> - Not able to get into hypervisor with ctrl-a (doesn't react to keyboard)
> - No info in syslog.
>
> Are there any more boot options I could give a try in the hope it will give some debug output ?
The Linux kernel has some of those 'DETECT_SPINLOCK_HANG' or
'DETECT_WORK..something' flags. It might be a good idea to compile those
and see when your machine freezes if after 2 minutes the kernel starts
spitting out what is hung. That could give some idea.
next prev parent reply other threads:[~2010-08-03 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:30 [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log Sander Eikelenboom
2010-08-03 15:45 ` Konrad Rzeszutek Wilk [this message]
2010-08-03 15:51 ` Jeremy Fitzhardinge
2010-08-03 16:18 ` Sander Eikelenboom
2010-08-03 17:18 ` Sander Eikelenboom
2010-08-05 9:48 ` Sander Eikelenboom
2010-08-05 14:52 ` Konrad Rzeszutek Wilk
2010-08-05 15:12 ` Sander Eikelenboom
2010-08-05 16:21 ` Jeremy Fitzhardinge
2010-08-06 9:21 ` Sander Eikelenboom
2010-08-06 15:17 ` Konrad Rzeszutek Wilk
2010-08-06 20:44 ` Jeremy Fitzhardinge
2010-08-08 13:54 ` Sander Eikelenboom
2010-08-08 16:57 ` Sander Eikelenboom
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=20100803154541.GA16122@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--cc=linux@eikelenboom.it \
--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).