All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Ben Hutchings <ben@decadent.org.uk>,
	xen-devel <xen-devel@lists.xensource.com>,
	638172@bugs.debian.org
Subject: Re: Bug#638172: Re: Bug#638172: BUG: soft lockup - CPU#0 stuck for 61s! [qemu-dm:3205]
Date: Fri, 26 Aug 2011 09:31:29 +0100	[thread overview]
Message-ID: <1314347489.10283.64.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <1314347333.4595.27.camel@scarafaggio>

On Fri, 2011-08-26 at 10:28 +0200, Giuseppe Sacco wrote:
> Hi,
> I just installed the new kernel and switched to 64bit hypervisor. I'll
> let you know about any news.
> 
> Il giorno ven, 26/08/2011 alle 08.25 +0100, Ian Campbell ha scritto:
> [...]
> > I'm in the process of uploading a kernel to
> > http://xenbits.xen.org/people/ianc/2.6.32-36~xen0/ which has a bunch of
> > patches to the event channel (aka IRQ) subsystem backported. I think the
> > kernel flavour you want is there already please could you give it a go
> > when you get the chance.
> 
> During boot I got this message. Is this related to this bug or to new
> kernel?

It's a benign (but annoying) warning. I'm angling to get it dropped:
http://marc.info/?l=xen-devel&m=131400621622691

> 
> [    0.004000] ------------[ cut here ]------------
> [    0.004000] WARNING: at /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_xen/arch/x86/xen/enlighten.c:726 perf_events_lapic_init+0x28/0x29()
> [    0.004000] Hardware name: MS-7368
> [    0.004000] Modules linked in:
> [    0.004000] Pid: 0, comm: swapper Not tainted 2.6.32-5-xen-686 #1
> [    0.004000] Call Trace:
> [    0.004000]  [<c1037839>] ? warn_slowpath_common+0x5e/0x8a
> [    0.004000]  [<c103786f>] ? warn_slowpath_null+0xa/0xc
> [    0.004000]  [<c1011db0>] ? perf_events_lapic_init+0x28/0x29
> [    0.004000]  [<c14033dd>] ? init_hw_perf_events+0x2dd/0x376
> [    0.004000]  [<c1403030>] ? check_bugs+0x8/0xd8
> [    0.004000]  [<c13fb808>] ? start_kernel+0x309/0x31d
> [    0.004000]  [<c13fd410>] ? xen_start_kernel+0x564/0x56b
> [    0.004000]  [<c1409045>] ? check_nmi_watchdog+0xcd/0x1f2
> [    0.004000] ---[ end trace a7919e7f17c0a725 ]---
> 
> Thanks,
> Giuseppe
> 
> 

-- 
Ian Campbell

May your Tongue stick to the Roof of your Mouth with the Force of a
Thousand Caramels.

  reply	other threads:[~2011-08-26  8:31 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
2011-08-25  7:23           ` Bug#638172: [Xen-devel] " 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 [this message]
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=1314347489.10283.64.camel@zakaz.uk.xensource.com \
    --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.