From: Jonathan Nieder <jrnieder@gmail.com>
To: Sergio Gelato <Sergio.Gelato@astro.su.se>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
xen-devel@lists.xensource.com, 676360@bugs.debian.org
Subject: Re: xen: oops at atomic64_read_cx8+0x4
Date: Thu, 7 Jun 2012 02:33:33 -0500 [thread overview]
Message-ID: <20120607073333.GF3210@burratino> (raw)
In-Reply-To: <20120607064017.GA2112@hanuman.astro.su.se>
Sergio Gelato wrote[1]:
> That 3.4.1-1~experimental.1 build
> (3.4-trunk-686-pae #1 SMP Wed Jun 6 15:11:31 UTC 2012 i686 GNU/Linux)
> is even less well-behaved under Xen: I'm getting a kernel OOPS at
> EIP: [<c1168e54>] atomic64_read_cx8+0x4/0xc SS:ESP e021:ca853c6c
> The top of the trace message unfortunately scrolled off the console before I
> could see it, and the message doesn't have time to make it to syslog (either
> local or remote).
[...]
> Non-Xen boots proceed normally.
Yeah, apparently[2] that's caused by
commit 26c191788f18
Author: Andrea Arcangeli <aarcange@redhat.com>
Date: Tue May 29 15:06:49 2012 -0700
mm: pmd_read_atomic: fix 32bit PAE pmd walk vs pmd_populate SMP race condition
which was also included in Debian kernel 3.2.19-1.
[1] http://bugs.debian.org/676360
[2] https://bugzilla.redhat.com/show_bug.cgi?id=829016#c4
next parent reply other threads:[~2012-06-07 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120606132012.GB24320@hanuman.astro.su.se>
[not found] ` <20120606163000.GD9354@burratino>
[not found] ` <20120607064017.GA2112@hanuman.astro.su.se>
2012-06-07 7:33 ` Jonathan Nieder [this message]
2012-06-07 10:33 ` xen: oops at atomic64_read_cx8+0x4 Andrea Arcangeli
2012-06-07 12:30 ` Bug#676360: " Sergio Gelato
2012-06-07 15:56 ` Bug#676360: [Xen-devel] " Konrad Rzeszutek Wilk
2012-06-07 16:17 ` Andrea Arcangeli
2012-06-07 19:50 ` Jan Beulich
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=20120607073333.GF3210@burratino \
--to=jrnieder@gmail.com \
--cc=676360@bugs.debian.org \
--cc=Sergio.Gelato@astro.su.se \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.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 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.