public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Soeren Sandmann <sandmann@daimi.au.dk>,
	linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de,
	acme@redhat.com, rosted@goodmis.org, paulus@samba.org
Subject: Re: Hard lockup with timer events
Date: Wed, 11 Nov 2009 14:23:01 +0100	[thread overview]
Message-ID: <1257945781.4372.34.camel@twins> (raw)
In-Reply-To: <20091111045004.GA5421@nowhere>

On Wed, 2009-11-11 at 05:50 +0100, Frederic Weisbecker wrote:
> On Thu, Oct 29, 2009 at 08:15:03PM +0100, Soeren Sandmann wrote:
> > Hi,
> > 
> > This program
> > 
> >         http://www.daimi.au.dk/~sandmann/lockup.c
> > 
> > locks up hard for me on a Pentium 4 in 32 bit mode, with the hrtimer
> > patches applied (-tip for example).
> > 
> > What the program does is spawn a thread that just spins, and then 400
> > threads that each create a performance counter of type
> > PERF_COUNT_SW_CPU_CLOCK and a sample period of 1000000 and a
> > sample_type of
> > 
> >         PERF_SAMPLE_IP | PERF_SAMPLE_TID | PERF_SAMPLE_CALLCHAIN
> > 
> > These threads then map the event buffer and read it continuously.
> > 
> > It does not apparently lock up if SAMPLE_CALLCHAIN is removed; also I
> > cannot get it to lock up on Core 2 Duo in either 32 or 64 bit mode.
> > 
> > 
> > Soren
> 
> 
> 
> It locks up hard for me too, no more blinking cursor, nothing.
> I've attached my config, it's against tip:master from yesterday.

What kind of cpu does your laptop have? The .config seems to suggest a
Core2. Which would make Soeren's report of not being able to trash a
64bit core2 'interesting' ;-)

  reply	other threads:[~2009-11-11 13:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 19:15 Hard lockup with timer events Soeren Sandmann
2009-11-11  4:50 ` Frederic Weisbecker
2009-11-11 13:23   ` Peter Zijlstra [this message]
2009-11-11 16:34     ` Frederic Weisbecker
2009-11-11 13:48 ` Peter Zijlstra

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=1257945781.4372.34.camel@twins \
    --to=peterz@infradead.org \
    --cc=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=rosted@goodmis.org \
    --cc=sandmann@daimi.au.dk \
    --cc=tglx@linutronix.de \
    /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