All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conn Clark <clark@esteem.com>
To: Patrick Mahoney <pmahoney@8d.com>
Cc: May Ling List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mpc8xx - power save modes - PIT
Date: Fri, 11 Oct 2002 10:05:43 -0700	[thread overview]
Message-ID: <3DA704E7.DF667121@esteem.com> (raw)
In-Reply-To: 20021011155904.GA9579@segfault.usine.8d.com


First I must appologize, I sent you the stable C code version instead of the
stable inlined asm version. It appears I deleted the wrong file a month or
so ago  :-( . Oh well it appears you like C anyway.




Patrick Mahoney wrote:
>
> Hi Conn,
>
> > I forgot to mention my kernel source tree was directly from kernel.org
>
> Fell free to correct me, but I believe the ppc patched kernel is
> identical to the one at source.mvista.com. Still, I'll try with the
> latest patch (2.4.18) available on kernel.org.
>
> > When using my idle loop, does it crash right away or only when you try to
> > use the PIT?

Strange....... Hmmmm.....


>
> It crashes before I get a chance to load my module. I dont get to the
> shell. It's got nothing to do with the PIT. Here's what my console
> gives me:
>
>         i2c-algo-8xx.o: i2c mpc8xx algorithm module version 2.6.5 (20020915)
>         i2c-rpx.o: i2c MPC8xx module version 2.6.5 (20020915)
>         i2c-algo-8xx.o: scanning bus m8xx...
>         Machine check in kernel mode.
>         Caused by (from SRR1=1000): Transfer error ack signal
>         Oops: machine check, sig: 7
>         NIP: 00004038 XER: 20000000 LR: 0002B91C SP: C0143F30 REGS: c0143e80 TRAP: 0200    Not tainted
>         MSR: 00001000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00
>         TASK = c0141fa0[0] 'swapper' Last syscall: 120
>         last math 00000000 last altivec 00000000
>         GPR00: 00000000 C0143F30 C0141FA0 00000000 00048000 00000000 00000001 FFFFFC18
>         GPR08: 00000100 C015F00C C014DBFF C014DCEE 0000000D FA202210 00000000 00000000
>         GPR16: 00000000 00000000 00000000 00000000 42004022 00EA5F40 00000000 C0004654
>         GPR24: 00000000 00000000 FA200000 743D2F62 00000000 C0160000 C014DC01 55CCAA32
>         Call backtrace:
>         C0005C94 C0005CA8 C0002268 C0152544 C0002138
>         Kernel panic: Attempted to kill the idle task!
>         In idle task - not syncing
>         <0>Rebooting in 180 seconds..
>
> ... and it normally fives me...
>
>         i2c-core.o: i2c core module version 2.6.5 (20020915)
>         i2c-dev.o: i2c /dev entries driver module version 2.6.5 (20020915)
>         i2c-algo-8xx.o: i2c mpc8xx algorithm module version 2.6.5 (20020915)
>         i2c-rpx.o: i2c MPC8xx module version 2.6.5 (20020915)
>          i2c-algo-8xx.o: scanning bus m8xx...
>         (90)(a8)(aa)
>         i2c-proc.o version 2.6.5 (20020915)
>         CPM UART driver version 0.03
>         ttyS00 at 0x0280 is a SMC
>         eth0: CPM ENET Version 0.2 on SCC2, 00:10:ec:00:33:ce
>
> Hmmm... It seems to oops in the i2c initialisation...
>
> <recompiling...>
>
> Ok. I took out the i2c stuff. It doesn't oops anymore... In fact, in
> enters the power saving mode (doze?) you put in the idle.c file before
> reaching the console! :))

PHEW... Good.


>
> Could be stuck waiting for a never-coming-interrupt? I gave the
> parameter "init=/bin/sash" to the kernel... Any logical explanation to this?
>

Strange you should be getting some intermitant interupts from things such as
the real time clock and other misc things and timers. Hmmm... Must be a RPX
hardware thing or something.


> >       Well if you put the power saving code in the idle loop, when there
> > isn't anything to do the processor sleeps. When an interrupt happens it
> > wakes up to service the interrupt then checks to see if it is needed for
> > other things and if not it goes back to bed (much like me ;-)). If you need
> > to do something 5 seconds later a sleep call should do the trick unless
> > you need more precision.
>
> It's not a precision thing. It's not so important. It would be neat,
> thats all.  :)
>
> Thanks again for your help.
> Best regards,
>
> Pat Mahoney

Well I have no idea whats going on. You should be getting some interrupts.
Unless your RPX board is entering the idle loop before these things get
initalized (which I don't think is possible). This has me stumped...

Good Luck,

	Conn

--

*****************************************************************
  If you live at home long enough, your parents will move out.
 (Warning they may try to sell their house out from under you.)
*****************************************************************

Conn Clark
Engineering Stooge				clark@esteem.com
Electronic Systems Technology Inc.		www.esteem.com


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-10-11 17:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 18:35 mpc8xx - power save modes - PIT Patrick Mahoney
2002-10-10 21:49 ` Conn Clark
2002-10-10 23:00   ` Patrick Mahoney
2002-10-11  1:42     ` Conn Clark
2002-10-11 15:59       ` Patrick Mahoney
2002-10-11 17:05         ` Conn Clark [this message]
2002-10-11 17:17           ` Patrick Mahoney
     [not found]       ` <20021021133451.GA16540@segfault.usine.8d.com>
2002-10-21 15:52         ` Conn Clark
     [not found]   ` <20021015225625.GA8153@segfault.usine.8d.com>
2002-10-16  1:08     ` Conn Clark
2002-10-16 15:42       ` Patrick Mahoney
     [not found]       ` <20021016130153.GA16430@segfault.usine.8d.com>
2002-10-16 18:14         ` Conn Clark
  -- strict thread matches above, loose matches on Subject: below --
2002-10-11 13:15 Steven Blakeslee
2002-10-11 16:08 ` Patrick Mahoney
2002-10-16  6:00 Cameron Rich
2002-10-16 13:22 ` Patrick Mahoney
2002-10-16 20:00   ` Conn Clark
2002-10-17 19:58     ` Patrick Mahoney
2002-10-17 21:50       ` Conn Clark
2002-10-16 17:29 ` Conn Clark

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=3DA704E7.DF667121@esteem.com \
    --to=clark@esteem.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=pmahoney@8d.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.