From: David Miller <davem@davemloft.net>
To: fweisbec@gmail.com
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: Sun, 04 Apr 2010 18:00:57 -0700 (PDT) [thread overview]
Message-ID: <20100404.180057.109331958.davem@davemloft.net> (raw)
In-Reply-To: <20100404122113.GD5177@nowhere>
From: Frederic Weisbecker <fweisbec@gmail.com>
Date: Sun, 4 Apr 2010 14:21:19 +0200
> Forgot the config, it's in attachment.
I get them too when even trying to use the function tracer in some
simple way. They occur in random places and eventually the entire
machine wedges and is unusuable.
I suspect there is some bug that ends up corrupting memory, so I
started trying to debug this last night when I first saw it.
I'll let you know if I make any progress.
next prev parent reply other threads:[~2010-04-05 1:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 12:18 Frederic Weisbecker
2010-04-04 12:21 ` Frederic Weisbecker
2010-04-05 1:00 ` David Miller [this message]
2010-04-05 6:57 ` Frederic Weisbecker
2010-04-05 19:22 ` David Miller
2010-04-05 19:40 ` Frederic Weisbecker
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=20100404.180057.109331958.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--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
all inboxes | Powered by JetHome®