From: Ingo Molnar <mingo@elte•hu>
To: Eric Paris <eparis@redhat•com>
Cc: rostedt@goodmis•org, linux-kernel@vger•kernel.org,
linux-next@vger•kernel.org, zhaolei@cn•fujitsu.com,
lizf@cn•fujitsu.com, Peter Zijlstra <a.p.zijlstra@chello•nl>
Subject: Re: [-next regression] lockdep? tracing? BUG: unable to handle kernel paging request at
Date: Tue, 3 Nov 2009 18:08:31 +0100 [thread overview]
Message-ID: <20091103170831.GB3074@elte.hu> (raw)
In-Reply-To: <1257267617.2891.107.camel@dhcp231-106.rdu.redhat.com>
* Eric Paris <eparis@redhat•com> wrote:
> On Tue, 2009-11-03 at 11:02 -0500, Steven Rostedt wrote:
> > [ Added Peter Zijlstra ]
> >
> > On Tue, 2009-11-03 at 10:48 -0500, Eric Paris wrote:
> > > Linux-next from Oct 30 did not have this problem. Linux next from
> > > yesterday (and today) I always hit this on boot.
> >
> > Could you also give the SHA1 of Linux-next, as well as the config you
> > used.
>
> False alarm, apparently this is due to a patch that I added. Odd part
> is, I don't touch anything even remotely close to this section of
> code. I'm at a bit of a lose, but apply my patch, boom, revert, works.
>
> I'll figure it out eventually I guess.
When i saw your crash earlier today my first guess was memory
corruption: lockdep is one of the first things to blow up on kernel data
structure memory corruption. It tracks all locks and affects everything
so gets hit first.
( Nevertheless we do have fresh changes in the tracing tree so some
genuine lockdep/tracing crash was not implausible either. )
Ingo
prev parent reply other threads:[~2009-11-03 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 15:48 [-next regression] lockdep? tracing? BUG: unable to handle kernel paging request at Eric Paris
2009-11-03 16:02 ` Steven Rostedt
2009-11-03 16:22 ` Eric Paris
2009-11-03 17:00 ` Eric Paris
2009-11-03 17:08 ` Ingo Molnar [this message]
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=20091103170831.GB3074@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=a.p.zijlstra@chello$(echo .)nl \
--cc=eparis@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lizf@cn$(echo .)fujitsu.com \
--cc=rostedt@goodmis$(echo .)org \
--cc=zhaolei@cn$(echo .)fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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