From: Frederic Weisbecker <fweisbec@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, acme@redhat.com, a.p.zijlstra@chello.nl,
paulus@samba.org
Subject: Re: Random scheduler/unaligned accesses crashes with perf lock events on sparc 64
Date: Mon, 5 Apr 2010 21:40:58 +0200 [thread overview]
Message-ID: <20100405194055.GA5265@nowhere> (raw)
In-Reply-To: <20100405.122233.188421941.davem@davemloft.net>
On Mon, Apr 05, 2010 at 12:22:33PM -0700, David Miller wrote:
> From: Frederic Weisbecker <fweisbec@gmail.com>
> Date: Mon, 5 Apr 2010 08:57:04 +0200
>
> > It seems to happen after an unaligned access fixup.
>
> You shouldn't be getting the unaligned fixup in the first place,
> especially in the locations where you see them. I suspect that
> once you see first fixup, all of the registers in the cpu have
> been corrupted in one way or another.
>
> I suspect something fundamental gets corrupted, for example the
> current register window (%cwp) is corrupted and that screws up all of
> the registers so every single function starts accessing garbage.
>
> My suspicions lie in three places, the ftrace mcount()
> stubs, stack_trace_flush(), or the new perf_arch_save_caller_regs()
> since those are the three places offhand that could make
> us potentially make us return to function in the wrong
> register window.
It happens without CONFIG_FUNCTION_TRACER as well (but it happens
when the function tracer runs). And I hadn't your perf_arch_save_caller_regs()
when I triggered this.
next prev parent reply other threads:[~2010-04-05 19:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 12:18 Random scheduler/unaligned accesses crashes with perf lock events on sparc 64 Frederic Weisbecker
2010-04-04 12:21 ` Frederic Weisbecker
2010-04-05 1:00 ` David Miller
2010-04-05 6:57 ` Frederic Weisbecker
2010-04-05 19:22 ` David Miller
2010-04-05 19:40 ` Frederic Weisbecker [this message]
2010-04-05 20:46 ` David Miller
2010-04-06 2:15 ` David Miller
2010-04-06 13:41 ` Steven Rostedt
2010-04-06 17:46 ` David Miller
2010-04-06 18:15 ` Steven Rostedt
2010-04-06 21:17 ` David Miller
2010-04-06 9:50 ` David Miller
2010-04-06 10:19 ` Frederic Weisbecker
2010-04-06 10:28 ` David Miller
2010-04-06 11:12 ` [RFC][PATCH] lockdep: WARN about local_irq_{en,dis}able in NMI context Peter Zijlstra
2010-04-06 11:13 ` David Miller
2010-04-06 11:20 ` Peter Zijlstra
2010-04-06 11:22 ` David Miller
2010-04-06 11:38 ` Random scheduler/unaligned accesses crashes with perf lock events on sparc 64 Frederic Weisbecker
2010-04-06 11:51 ` Peter Zijlstra
2010-04-06 12:54 ` Mike Galbraith
2010-04-06 12:57 ` Peter Zijlstra
2010-04-06 18:04 ` Paul E. McKenney
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=20100405194055.GA5265@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=sparclinux@vger.kernel.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