[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-omap
Subject:    Re: v3.9.0-rc8 : oops in tick_do_update_jiffies64+0xbc/0x110
From:       Mark Jackson <mpfj-list () newflow ! co ! uk>
Date:       2013-04-29 15:46:18
Message-ID: 517E95CA.4000708 () newflow ! co ! uk
[Download RAW message or body]

On 29/04/13 16:41, Tony Lindgren wrote:
> * Mark Jackson <mpfj-list@newflow.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-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[prev in list] [next in list] [prev in thread] [next in thread]