From: Valdis.Kletnieks@vt.edu
To: Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.36-rc5-mmotm0928 BUG while trying to ptrace a process
Date: Wed, 06 Oct 2010 05:32:57 -0400 [thread overview]
Message-ID: <108598.1286357577@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]
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
Here's the stack traceback:
[20669.480761] Process gdb (pid: 60320, threadinfo ffff8800a0e4c000, task ffff8800c62acc80)
[20669.480763] Stack:
[20669.480765] ffff8801188c2eac ffffffff81a40750 0000000100000000 ffffffff81a406b0
[20669.480771] <0> ffffffff8100b469 ffff8800a0d6c400 0000000000000000 ffffffff81a406b0
[20669.480777] <0> ffffffff8100b469 0000000000000000 ffff8800a0e4dcf8 ffffffff810b83e5
[20669.480784] Call Trace:
[20669.480789] [<ffffffff8100b469>] ? ptrace_triggered+0x0/0x39
[20669.480793] [<ffffffff8100b469>] ? ptrace_triggered+0x0/0x39
[20669.480797] [<ffffffff810b83e5>] reserve_bp_slot+0x22/0x3b
[20669.480800] [<ffffffff810b6805>] ? perf_init_event+0x0/0xc9
[20669.480804] [<ffffffff810b8487>] register_perf_hw_breakpoint+0x11/0x36
[20669.480808] [<ffffffff810b84cb>] hw_breakpoint_event_init+0x1f/0x34
[20669.480811] [<ffffffff8100b469>] ? ptrace_triggered+0x0/0x39
[20669.480815] [<ffffffff810b685a>] perf_init_event+0x55/0xc9
[20669.480818] [<ffffffff810b6805>] ? perf_init_event+0x0/0xc9
[20669.480822] [<ffffffff810b6a74>] perf_event_alloc+0x1a6/0x3ef
[20669.480826] [<ffffffff810b6f92>] perf_event_create_kernel_counter+0x22/0x185
[20669.480830] [<ffffffff810b7d9b>] register_user_hw_breakpoint+0xf/0x11
[20669.480834] [<ffffffff8100c7d3>] ptrace_set_debugreg+0xaa/0x257
[20669.480838] [<ffffffff8156bfab>] ? sub_preempt_count+0x35/0x48
[20669.480844] [<ffffffff81568957>] ? _raw_spin_unlock_irqrestore+0x72/0x80
[20669.480848] [<ffffffff8100cd48>] arch_ptrace+0x126/0x214
[20669.480852] [<ffffffff81045609>] sys_ptrace+0x7e/0x99
[20669.480857] [<ffffffff810027eb>] system_call_fastpath+0x16/0x1b
Any thoughts? I haven't gotten any further than "the big honking commits
against perf in linux-next". Probably bisectable with some effort - I've got
a fairly replicable Firefox hang that seems to trigger the gdb indigestion.,
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2010-10-06 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 9:32 Valdis.Kletnieks [this message]
2010-10-06 13:45 ` 2.6.36-rc5-mmotm0928 BUG while trying to ptrace a process Peter Zijlstra
2010-10-18 1:28 ` KOSAKI Motohiro
2010-10-18 1:36 ` Frederic Weisbecker
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=108598.1286357577@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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 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.