From: Frederic Weisbecker <fweisbec@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Valdis.Kletnieks@vt.edu,
Andrew Morton <akpm@linux-foundation.org>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: 2.6.36-rc5-mmotm0928 BUG while trying to ptrace a process
Date: Mon, 18 Oct 2010 03:36:24 +0200 [thread overview]
Message-ID: <20101018013622.GA21722@nowhere> (raw)
In-Reply-To: <20101018102609.3ADF.A69D9226@jp.fujitsu.com>
On Mon, Oct 18, 2010 at 10:28:43AM +0900, KOSAKI Motohiro wrote:
> > On Wed, 2010-10-06 at 05:32 -0400, Valdis.Kletnieks@vt.edu wrote:
> > > Dell Latitude E6500, Intel Core2 Duo P8700 CPU.
> > >
> > > Have seen this three times now while trying to attach gdb to a hung Firefox
> > > process.
> > >
> > > [20669.480674] BUG: unable to handle kernel NULL pointer dereference at 0000000000000100
> > > [20669.480682] IP: [<ffffffff810b8275>] __reserve_bp_slot+0x56/0x17d
> >
> > Known issue I think, Frederic was looking into curing this.
> >
> > Frederic, what's the current status of that?
>
> mmotm1014 seems still have this issue. Frederic, can you please tell us
> current status if you are tracking this issue?
Peter has a pending queue for .37 which includes:
[RFC][PATCH 3/7] perf, hw_breakpoint: Fix crash in hw_breakpoint creation
This patch should fix the issue (it depends on others in the queue).
What is mmotm1014 BTW? Because you should see this bug only in a tree
that has tip:/perf/core merged inside, like linux-next.
Thanks.
next prev parent reply other threads:[~2010-10-18 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 9:32 2.6.36-rc5-mmotm0928 BUG while trying to ptrace a process Valdis.Kletnieks
2010-10-06 13:45 ` Peter Zijlstra
2010-10-18 1:28 ` KOSAKI Motohiro
2010-10-18 1:36 ` Frederic Weisbecker [this message]
2010-10-18 2:01 ` KOSAKI Motohiro
2010-10-18 2:04 ` Frederic Weisbecker
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=20101018013622.GA21722@nowhere \
--to=fweisbec@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
/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