From: Ian Campbell <ijc@hellion.org.uk>
To: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
Cc: "638172@bugs.debian.org" <638172@bugs.debian.org>,
Ben Hutchings <ben@decadent.org.uk>,
xen-devel <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Re: Bug#638172: BUG: soft lockup - CPU#0 stuck for 61s! [qemu-dm:3205]
Date: Thu, 25 Aug 2011 07:56:40 +0100 [thread overview]
Message-ID: <1314255400.17978.724.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <1314255147.4943.5.camel@scarafaggio>
[-- Attachment #1.1: Type: text/plain, Size: 1200 bytes --]
On Thu, 2011-08-25 at 08:52 +0200, Giuseppe Sacco wrote:
> Il giorno mer, 24/08/2011 alle 22.24 +0100, Ian Campbell ha scritto:
> [...]
> > Giuseppe, are you able to reproduce the issue you are seeing at will? If
> > I build a test kernel would you be able to try it? You are using a -686
> > kernel right (as opposed to amd64). OOI which hypervisor flavour do you
> > use?
>
> Unfortunately not. This server crashes often, but I do not have any
> method to let it crashes. The worst case is when it crashes just after
> reboot, the opposite was after a month from reboot.
>
> But, I may use a different kernel and let the server goes until crashes:
> no problem in rebooting it for kernel update.
Thanks that would be useful, I'll put something together and let you
know.
> And yes, it is a 32bit debian squeeze system on a 64 bit Athlon cpu.
But are you running the amd64 or 686 flavour of the hypervisor? Both are
available in 32bit Debian. FWIW I would always recommend running the 64
bit hypervisor (even with 32 bit dom0) if you are able to.
Ian.
--
Ian Campbell
Once the toothpaste is out of the tube, it's hard to get it back in.
-- H. R. Haldeman
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-08-25 6:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1313577856.13030.17.camel@scarafaggio>
2011-08-22 9:00 ` Bug#638172: BUG: soft lockup - CPU#0 stuck for 61s! [qemu-dm:3205] Ian Campbell
2011-08-22 9:49 ` Giuseppe Sacco
2011-08-24 20:24 ` Konrad Rzeszutek Wilk
2011-08-24 21:24 ` Ian Campbell
2011-08-25 6:52 ` Bug#638172: [Xen-devel] " Giuseppe Sacco
2011-08-25 6:56 ` Ian Campbell [this message]
2011-08-25 7:23 ` Giuseppe Sacco
2011-08-26 7:25 ` Bug#638172: " Ian Campbell
2011-08-26 8:28 ` Giuseppe Sacco
2011-08-26 8:31 ` Ian Campbell
2011-10-18 10:54 ` Ian Campbell
2011-10-18 11:00 ` Giuseppe Sacco
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=1314255400.17978.724.camel@dagon.hellion.org.uk \
--to=ijc@hellion.org.uk \
--cc=638172@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=giuseppe@eppesuigoccas.homedns.org \
--cc=konrad.wilk@oracle.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.