linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Ming Lei <mlei@Brocade.COM>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: watchdog exception on 8548CDS during cpu_idle
Date: Thu, 19 Nov 2009 11:37:25 -0600	[thread overview]
Message-ID: <20091119173725.GA6845@b07421-ec1.am.freescale.net> (raw)
In-Reply-To: <7301F255FCB62048851F165FFAAF9BD106E9B3F0E5@HQ-EXCH-7.corp.brocade.com>

On Wed, Nov 18, 2009 at 03:53:27PM -0800, Ming Lei wrote:
> 
> I used the vanilla linux 2.6.30 and compiled with mpc85xx_defconfig(enable CONFIG_BOOK_WDT) and then ran on 8548CDS and soon after I saw the prompt I hit this watchdog.
>  
> bash-2.04# PowerPC Book-E Watchdog Exception
> NIP: c000b740 LR: c00088dc CTR: c000b6b0
> REGS: cfffbf10 TRAP: 3202   Not tainted  (2.6.30)
> MSR: 00029000 <EE,ME,CE>  CR: 28028048  XER: 20000000
> TASK = c04f4458[0] 'swapper' THREAD: c052c000
> GPR00: c000b6b0 c052df90 c04f4458 00800000 80804080 0000001d c053af48 00069000 
> GPR08: ffffffff 00000000 08954400 00000000 002167ee 7f652f31 0ffad800 0fff0000 
> GPR16: 00000000 00000000 00000000 00000000 00000000 f30a620b 0ff50450 00000000 
> GPR24: 00000000 00000000 c053506c c0534fa0 c0534fa0 c052c034 00000008 c052c000 
> NIP [c000b740] e500_idle+0x90/0x94
> LR [c00088dc] cpu_idle+0x98/0xec
> Call Trace:
> [c052df90] [c000889c] cpu_idle+0x58/0xec (unreliable)
> [c052dfb0] [c00023ec] rest_init+0x5c/0x70
> [c052dfc0] [c04c16f4] start_kernel+0x22c/0x290
> [c052dff0] [c0000398] skpinv+0x2b0/0x2ec
> Instruction dump:
> 7c90faa6 548402ce 7c841b78 4c00012c 7c90fba6 4c00012c 7ce000a6 64e70004 
> 60e78000 7c0004ac 7ce00124 4c00012c <48000000> 812b00a0 912b0090 39600000 
> 
> Have anyone seen this before? Why the EE bit is on in the stack trace?
> I put show_regs in watchdog exception handler in traps.c. I verified
> that EE is off when entering the watchdog exception handler. Can I
> trust this stack trace?

EE is there because it was set in the context that got interrupted, just
as all the other state is for the interrupted context.

-Scott

      reply	other threads:[~2009-11-19 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 23:53 watchdog exception on 8548CDS during cpu_idle Ming Lei
2009-11-19 17:37 ` Scott Wood [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=20091119173725.GA6845@b07421-ec1.am.freescale.net \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mlei@Brocade.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;
as well as URLs for NNTP newsgroup(s).