linux-kernel - Re: EeePC 900 reboots/hangs when using using perf -a -f -g

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 12 Sep 2010 17:17:31 +0100
From:	Sitsofe Wheeler <sitsofe@...oo.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Corentin Chary <corentincj@...aif.net>
Subject: Re: EeePC 900 reboots/hangs when using using perf -a -f -g

On Sun, Sep 12, 2010 at 03:06:39PM +0200, Frederic Weisbecker wrote:
> 
> Testing with a software event like page faults will test if it's related
> to hardware events only or some of them.
> For example if it doesn't happen in fault events, then let's try with some
> others, just to see if we can narrow down to some particular events.

OK.

> If it happens on faults it will be easier to debug because software events
> don't happen in NMI (at least not the faults), so enabling RCU stalls checks
> there will probably success to trigger a backtrace. Perhaps you can profile
> only one CPU for that (-C 1, eeepc 900 are SMT, right?), so that there is
> a free CPU to notice the stall and trigger the backtrace through remote NMIs.

An EeePC has only one CPU (so it's strictly UP only). 

-- 
Sitsofe | http://sucs.org/~sits/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/