From: Gleb Natapov <gleb@redhat.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [Bisected][-next-20130204+] [x86/kvm] udevd:[97]: segfault at ffffffffff5fd020 ip 00007fff069e277f sp 00007fff068c9ef8 error d
Date: Tue, 19 Feb 2013 10:26:56 +0200 [thread overview]
Message-ID: <20130219082656.GE3600@redhat.com> (raw)
In-Reply-To: <1361236341.3263.11.camel@thor.lan>
On Mon, Feb 18, 2013 at 08:12:21PM -0500, Peter Hurley wrote:
> On Mon, 2013-02-18 at 19:59 -0300, Marcelo Tosatti wrote:
> > On Wed, Feb 13, 2013 at 06:57:09AM -0500, Peter Hurley wrote:
> > > On Wed, 2013-02-13 at 12:51 +0200, Gleb Natapov wrote:
> > > > On Tue, Feb 12, 2013 at 04:39:03PM -0800, H. Peter Anvin wrote:
> > > > > On 02/12/2013 04:26 PM, Peter Hurley wrote:
> > > > > > With -next-20130204+ in ubuntu 12.10 VM (so the 80x25 VGA
> > > > > > device/console):
> > > > > >
> > > > > > [ 0.666410] udevd[97]: starting version 175
> > > > > > [ 0.674043] udevd[97]: udevd:[97]: segfault at ffffffffff5fd020 ip 00007fff069e277f sp 00007fff068c9ef8 error d
> > > > > >
> > > > > > and boots to an initramfs prompt.
> > > > > >
> > > > > > git bisect (log attached) blames:
> > > > > >
> > > > > > commit 7b5c4a65cc27f017c170b025f8d6d75dabb11c6f
> > > > > > Merge: 3596f5b 949db15
> > > > > > Author: H. Peter Anvin <hpa@linux.intel.com>
> > > > > > Date: Fri Jan 25 16:31:21 2013 -0800
> > > > > >
> > > > > > Merge tag 'v3.8-rc5' into x86/mm
> > > > > >
> > > > > > The __pa() fixup series that follows touches KVM code that is not
> > > > > > present in the existing branch based on v3.7-rc5, so merge in the
> > > > > > current upstream from Linus.
> > > > > >
> > > > > > Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
> > > > > >
> > > > > >
> > > > > > This only happens with the VGA device/console but that is the default
> > > > > > configuration for Ubuntu/KVM because it blacklists pretty much every fb
> > > > > > driver.
> > > > > >
> > > > >
> > > > > I am guessing this is another bad use of __pa()... need to look into that.
> >
> > Can't find this commit on kvm.git or linux-2.6.git. Is it reproducible
> > there?
>
> This is in the linux-next repo (any git tag after 'next-20130204' will
> reproduce this). It's a pretty large merge commit.
>
> This doesn't happen on 3.8-rc7.
>
> I'll try to repro this on kvm.git sometime this week. Otherwise, we can
> wait for it to show up in 3.9.
>
Can you also drop 5dfd486c4750c9278c63fa96e6e85bdd2fb58e9d from linux-next and reproduce?
--
Gleb.
next prev parent reply other threads:[~2013-02-19 8:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 0:26 [Bisected][-next-20130204+] [x86/kvm] udevd:[97]: segfault at ffffffffff5fd020 ip 00007fff069e277f sp 00007fff068c9ef8 error d Peter Hurley
2013-02-13 0:39 ` H. Peter Anvin
2013-02-13 10:51 ` Gleb Natapov
2013-02-13 11:57 ` Peter Hurley
2013-02-18 22:59 ` Marcelo Tosatti
2013-02-19 1:12 ` Peter Hurley
2013-02-19 8:26 ` Gleb Natapov [this message]
2013-02-20 17:20 ` Peter Hurley
2013-02-24 21:23 ` Peter Hurley
2013-02-27 19:43 ` Marcelo Tosatti
2013-02-27 20:28 ` [PATCH] x86/kvm: Fix pvclock vsyscall fixmap Peter Hurley
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=20130219082656.GE3600@redhat.com \
--to=gleb@redhat.com \
--cc=hpa@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peter@hurleysoftware.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