On Mon, Jul 08, 2013 at 06:50:23PM +0200, Peter Zijlstra wrote:
>
> [ 324.983534] [ cut here ]
> [ 324.984420] WARNING: at /usr/src/linux-2.6/kernel/events/core.c:1953
> __perf_event_enable+0x187/0x190()
> [ 324.984420] Modules linked in:
> [ 324.984420] CPU: 19 PID: 2
On Mon, Jul 08, 2013 at 03:50:48PM +0200, Jiri Olsa wrote:
> need to check if that does not break anything else ;-)
Vince's test-case triggered the below; so there might still be a few loose
ends.
[ 324.983534] [ cut here ]
[ 324.984420] WARNING: at /usr/src/linux-2.6/
On Mon, Jul 08, 2013 at 03:50:48PM +0200, Jiri Olsa wrote:
> patch below gets rid of the warning, and probably the
> crash as well
>
> the reason seems to be when HW context is cloned based
> on SW event that happened to get there because of the
> HW leader, which got closed just before (fd[15] ev
On Mon, 8 Jul 2013, Jiri Olsa wrote:
> On Wed, Jul 03, 2013 at 09:49:29AM +0200, Peter Zijlstra wrote:
> > On Tue, Jul 02, 2013 at 11:15:59PM -0400, Vince Weaver wrote:
> need to check if that does not break anything else ;-)
I've applied your patch to stock 3.10 and am now unable to hang my Core
On Wed, Jul 03, 2013 at 09:49:29AM +0200, Peter Zijlstra wrote:
> On Tue, Jul 02, 2013 at 11:15:59PM -0400, Vince Weaver wrote:
> >
> > OK, I have bisected this problem to the following change:
> >
> > commit 8dc85d547285668e509f86c177bcd4ea055bcaaf
> > Author: Peter Zijlstra
> > Date: Thu Sep
On Tue, Jul 02, 2013 at 11:15:59PM -0400, Vince Weaver wrote:
>
> OK, I have bisected this problem to the following change:
>
> commit 8dc85d547285668e509f86c177bcd4ea055bcaaf
> Author: Peter Zijlstra
> Date: Thu Sep 2 16:50:03 2010 +0200
>
> perf: Multiple task contexts
>
> Prov
OK, I have bisected this problem to the following change:
commit 8dc85d547285668e509f86c177bcd4ea055bcaaf
Author: Peter Zijlstra
Date: Thu Sep 2 16:50:03 2010 +0200
perf: Multiple task contexts
Provide the infrastructure for multiple task contexts.
--
To unsubscribe from this li
On Mon, 1 Jul 2013, Vince Weaver wrote:
> I'm in the process of kernel bisecting this, though all I can tell you so
> far is 2.6.32 is unaffected by the bug but 3.2 and later are.
well, I spent 2 days bisecting between 3.1 and 3.2 (after
wasting time bisecting between 3.0 and 3.1 by mistake)
(
On Mon, 1 Jul 2013, Peter Zijlstra wrote:
> OK, so on my westmere it triggers that WARN in task_ctx_sched_out() a
> _lot_ (I removed the ONCE for easier debugging earlier -- still kinda
> stumped there).
>
> Then this thing causes an RCU stall and starts triggering NMI watchdog
> msgs.. so YAY!
On Fri, Jun 28, 2013 at 05:07:38PM -0400, Vince Weaver wrote:
> On Fri, 28 Jun 2013, Vince Weaver wrote:
>
> > On Fri, 14 Jun 2013, Vince Weaver wrote:
> >
> > > OK, I haven't managed to get a small reproducible test case for the
> > > system
> > > crash yet
> >
> > I wasted the last 2 days b
On Fri, 28 Jun 2013, Vince Weaver wrote:
> On Fri, 14 Jun 2013, Vince Weaver wrote:
>
> > OK, I haven't managed to get a small reproducible test case for the system
> > crash yet
>
> I wasted the last 2 days bisecting a 1 syscall trace, but below is a
> 20-syscall testcase that rapidly ma
On Fri, 14 Jun 2013, Vince Weaver wrote:
> OK, I haven't managed to get a small reproducible test case for the system
> crash yet
I wasted the last 2 days bisecting a 1 syscall trace, but below is a
20-syscall testcase that rapidly makes a core2 machine running 3.10-rc7
unusable.
You may
OK, I haven't managed to get a small reproducible test case for the system
crash yet, but I do have one for the initial WARN_ONCE that happens.
This is on 3.10-rc5
As a refresher, it looks like this:
[ 44.688044] [ cut here ]
[ 44.692023] WARNING: at kernel/events/co
Current git of my perf_fuzzer tool (recently enhanced to fork and prctl)
https://github.com/deater/perf_event_tests/tree/master/fuzzer
rapidly crashes my machine with a
Warning followed by NMI errors then an rcu_stall then stuck cpus.
This is on a core2 machine.
I don't think these traces look
14 matches
Mail list logo
