linux-kernel - Re: WARNING: CPU: 2 PID: 1857 at arch/x86/kernel/smp.c:124

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:	Wed, 16 Apr 2014 11:58:37 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Richard Weinberger <richard@....at>
Cc:	the arch/x86 maintainers <x86@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Seiji Aguchi <seiji.aguchi@....com>, ak@...ux.intel.com,
	Steven Rostedt <rostedt@...dmis.org>,
	Borislav Petkov <bp@...en8.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: WARNING: CPU: 2 PID: 1857 at arch/x86/kernel/smp.c:124

On Wed, Apr 16, 2014 at 11:28:40AM +0200, Richard Weinberger wrote:
> Am 16.04.2014 11:21, schrieb Peter Zijlstra:
> > On Wed, Apr 16, 2014 at 11:13:44AM +0200, Richard Weinberger wrote:
> >> Hi!
> >>
> >> On a new 8 core server I'm facing the following issue.
> >> After an oops a warning triggers.
> > 
> > I think its fair to ignore everything _after_ an OOPS ;-)
> 
> The problem here is that I'm using pstore with the erst backend (ACPI APEI).
> But it can only store a few KiB. So upon every oops it captures only the bogus
> warning and the original one is lost.

Then teach it to stop recording after the first WARN/OOPS.

You can generates megabytes of crap after an oops, that's a feature
afaik, think of dump_ftrace_on_oops and the like.
--
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/