From: Edward Hong <edward.qin.hong@gmail•com>
To: Randy Vinson <rvinson@mvista•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: kernel ported from ELDK 3.0 hangs (loops in idled()) on my custom MPC870 Board
Date: Fri, 10 Jun 2005 15:43:56 -0600 [thread overview]
Message-ID: <21fb73bc0506101443414d99a2@mail.gmail.com> (raw)
In-Reply-To: <21fb73bc0506061300126b1c43@mail.gmail.com>
It looks like the BDI2000 debugger caused the problem. The kernel
boots fine after removing the debugger.
Thank you very much for all your replies!
Edward
On 6/6/05, Edward Hong <edward.qin.hong@gmail•com> wrote:
> On 6/6/05, Randy Vinson <rvinson@mvista•com> wrote:
> >
> > Hi Edward,
> > I've seen these symptoms before. The problem was traced to external
> > interrupts being disabled (MSR[EE] not set). Without external
> > interrupts, there is no decrementer interrupt (at least on 7xx
> > processors). Without the decrementer, there in no system clock tick and
> > without the clock tick, the scheduler won't run which means that the
> > init task won't start. To verify that this is the problem, use mfmsr()
> > to get the MSR and print it. I'd suggest that you add something like:
> >
> > printk("MSR =3D %x\n", mfmsr());
> >
> I got MSR =3D 9032 just before cpu_idle which means EE (the most
> significant bit) was enabled.
>=20
> Thank you!
>=20
> Edward
>
prev parent reply other threads:[~2005-06-10 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 23:10 kernel ported from ELDK 3.0 hangs (loops in idled()) on my custom MPC870 Board Edward Hong
2005-06-04 1:17 ` Wolfgang Denk
2005-06-04 23:40 ` Edward Hong
2005-06-05 0:28 ` Wolfgang Denk
2005-06-06 5:33 ` Edward Hong
2005-06-06 8:03 ` Wolfgang Denk
2005-06-06 18:48 ` Randy Vinson
2005-06-06 20:00 ` Edward Hong
2005-06-10 21:43 ` Edward Hong [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=21fb73bc0506101443414d99a2@mail.gmail.com \
--to=edward.qin.hong@gmail$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=rvinson@mvista$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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