linux-kernel - Re: 3.10.0 i386 uniprocessor panic

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:	Fri, 19 Jul 2013 15:21:07 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Borislav Petkov <bp@...en8.de>
cc:	George Spelvin <linux@...izon.com>, linux-kernel@...r.kernel.org
Subject: Re: 3.10.0 i386 uniprocessor panic

On Thu, 18 Jul 2013, Borislav Petkov wrote:
> On Thu, Jul 18, 2013 at 02:13:47AM -0400, George Spelvin wrote:
> > I ressurected an old Athlon XP box for fun, and was stress-testing it
> > with mprime.  (It had been stable before retirement.)  After 34 hours
> > of successful torture test (suggesting a stable memory syatem), I found
> > this on the screen (hand-transcribed, top scrolled off):
> > Call Trace:
> >  [<c102437d>] ? call_timer_fn.isra.37+0x16/0x6d
> >  [<c1024524>] ? run_timer_softirq+0x150/0x165
> >  [<c1020e8b>] ? __do_softirq+0x8b/0x135

Can you please enable debugobjects. That should catch the offender.

Thanks,

	tglx
--
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/