From: Ingo Molnar <mingo@elte.hu>
To: Chris Malley <mail@chrismalley.co.uk>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: perf sched record hangs machine
Date: Wed, 23 Sep 2009 11:20:24 +0200 [thread overview]
Message-ID: <20090923092024.GA29323@elte.hu> (raw)
In-Reply-To: <7863dc4c0909230215u2fed3edciec84f93f24d3ae1@mail.gmail.com>
* Chris Malley <mail@chrismalley.co.uk> wrote:
> 2009/9/23 Cyrill Gorcunov <gorcunov@gmail.com>:
> >
> > Btw, meanwhile Chris may try to pass lapic boot-option in attempt to
> > reenable apic via msr registers. Also (iirc) i feel we may be hiding
> > errors if complete noop apic would be used since i belive we need to
> > check out under which condition a particular operation is called and
> > when apic is disabled it's mean we're switched to UP mode and
> > inter-cpu interrupts are under suspicion too. Will take a look during
> > ~6 hours ;)
> >
>
> Hi Cyrill
>
> Heh, yes that just occurred to me as well. With the lapic boot option
> I can't reproduce the problem, and get a good recording every time.
> Don't know why the BIOS had disabled it (can't see any specific
> option).
Would still be important to fix the crash - there are boxes where lapics
are disabled permanently and cannot be re-enabled. (plus most people
dont touch their defaults and dont add funky boot options - so crashing
is not an option)
I have such a test-box:
[ 0.000000] Using APIC driver default
[ 0.000000] ACPI: PM-Timer IO Port: 0x8008
[ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] Local APIC disabled by BIOS -- reenabling.
[ 0.000000] Could not enable APIC!
[ 0.000000] APIC: disable apic facility
Btw., perf events can work even without a lapic (albeit without NMI
driven sampling):
[ 0.052051] Performance Events:
[ 0.055138] no APIC, boot with the "lapic" boot parameter to force-enable it.
[ 0.056014] no hardware sampling interrupt available.
[ 0.060014] p6 PMU driver.
[ 0.062955] ... version: 0
[ 0.064014] ... bit width: 32
[ 0.068014] ... generic registers: 2
[ 0.072015] ... value mask: 00000000ffffffff
[ 0.076014] ... max period: 000000007fffffff
[ 0.080014] ... fixed-purpose events: 0
[ 0.084014] ... event mask: 0000000000000003
That's what it did on your box too:
[ 0.013679] Performance Events:
[ 0.013705] no APIC, boot with the "lapic" boot parameter to force-enable it.
[ 0.013783] no hardware sampling interrupt available.
[ 0.013826] p6 PMU driver.
[ 0.013882] ... version: 0
[ 0.013922] ... bit width: 32
[ 0.013962] ... generic registers: 2
[ 0.014002] ... value mask: 00000000ffffffff
[ 0.014045] ... max period: 000000007fffffff
[ 0.014088] ... fixed-purpose events: 0
[ 0.014128] ... event mask: 0000000000000003
Unfortunately i cannot reproduce the crash you've been seeing. (but i'm
quite sure it's due to self-IPI not working fine with dummy lapic.)
Ingo
next prev parent reply other threads:[~2009-09-23 9:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 21:09 perf sched record hangs machine Chris Malley
2009-09-22 21:24 ` Frederic Weisbecker
2009-09-22 21:44 ` Frederic Weisbecker
2009-09-23 6:16 ` Peter Zijlstra
2009-09-23 7:32 ` Ingo Molnar
2009-09-23 7:40 ` Ingo Molnar
2009-09-23 7:44 ` Cyrill Gorcunov
2009-09-23 8:48 ` Cyrill Gorcunov
2009-09-23 8:52 ` Peter Zijlstra
2009-09-23 9:15 ` Chris Malley
2009-09-23 9:20 ` Ingo Molnar [this message]
2009-09-23 9:48 ` Cyrill Gorcunov
2009-09-23 10:06 ` Chris Malley
2009-09-23 10:12 ` Cyrill Gorcunov
2009-09-23 10:42 ` Ingo Molnar
2009-09-23 11:41 ` Chris Malley
2009-09-23 11:42 ` Ingo Molnar
2009-09-23 12:20 ` Chris Malley
2009-09-23 12:27 ` Ingo Molnar
2009-09-23 10:41 ` Ingo Molnar
2009-09-23 9:03 ` Peter Zijlstra
2009-09-23 11:49 ` [tip:perf/urgent] perf_event, x86: Fix 'perf sched record' crashing the machine tip-bot for Peter Zijlstra
2009-09-23 12:15 ` Chris Malley
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=20090923092024.GA29323@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@chrismalley.co.uk \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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