linux-kernel - Re: v3.9.0-rc8 : oops in tick_do_update

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] [day] [month] [year] [list]

Message-ID: <517E95CA.4000708@newflow.co.uk>
Date:	Mon, 29 Apr 2013 16:46:18 +0100
From:	Mark Jackson <mpfj-list@...flow.co.uk>
To:	Tony Lindgren <tony@...mide.com>
CC:	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	tglx@...utronix.de, lkml <linux-kernel@...r.kernel.org>
Subject: Re: v3.9.0-rc8 : oops in tick_do_update_jiffies64+0xbc/0x110

On 29/04/13 16:41, Tony Lindgren wrote:
> * Mark Jackson <mpfj-list@...flow.co.uk> [130429 01:38]:
>> I've been experiencing several crashes all pointing exactly the same place in the same tick routine (see below).
>>
>> The "exception stack" trace at the end changes depending on when the oops occurs.
>>
>> I've had the oops occur maybe 6 times in the last 50 reboots.
>>
>> Any ideas ?
> 
> Sounds like it might be an issue with the physical memory or
> the timings. It could also be related to the idle loop not
> restoring something right for deeper idle states that corrupts
> the memory. And that's why it would seem to appear while waking
> to a timer.

I am suspecting a borderline CPU.  We only have "X" AM3359 parts which
are all pre-production.

> Maybe disable PM and run memtester to see if that runs reliably?

I'll see if I can get it running on our platform.

Thanks
Mark J.
--
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/