mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Jackson <mpfj-list@newflow.co.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	tglx@linutronix.de, lkml <linux-kernel@vger.kernel.org>
Subject: Re: v3.9.0-rc8 : oops in tick_do_update_jiffies64+0xbc/0x110
Date: Mon, 29 Apr 2013 16:46:18 +0100	[thread overview]
Message-ID: <517E95CA.4000708@newflow.co.uk> (raw)
In-Reply-To: <20130429154146.GB28721@atomide.com>

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.

      reply	other threads:[~2013-04-29 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29  8:32 Mark Jackson
2013-04-29 15:41 ` Tony Lindgren
2013-04-29 15:46   ` Mark Jackson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=517E95CA.4000708@newflow.co.uk \
    --to=mpfj-list@newflow.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®