linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Linux 2.4.4 on 860 custom board
@ 2001-08-24 20:46 Elan Feingold
  2001-08-24 20:59 ` Wolfgang Denk
  0 siblings, 1 reply; 2+ messages in thread
From: Elan Feingold @ 2001-08-24 20:46 UTC (permalink / raw)
  To: Linuxppc-Embedded@Lists. Linuxppc. Org


Hi,

I'm still trying to get Wolfgang's Linux 2.4.4 to come up on my custom 860
board.  I started with a bootrom that normally boots VxWorks, so I thought
I'd have no problem.  The IMMR is at the right place (0xff000000), and in
general the kernel boots up fine, but it dies with a "kernel access of bad
area" where the actual address is question is usually strange (e.g.
0x40000004, or 0x00000004).  It seems like it dies when it's trying to
access data, either kmalloc()ed or static, and it's never consistent where
it dies.  Sometimes it's inside a printk() where the print is trying to
print out some member of some structure.  And sometimes it does until it
mounts my root file system via NFS and then does the same oops down in the
NFS code.  Generally just very flaky!

I'd usually think it was a memory timing setup problem, right?  But VxWorks
runs fine, and has for years on the board.

Any ideas?  Is it possible that VxWorks just has less strict timing
requirements to run?

Best regards,

-elan


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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Linux 2.4.4 on 860 custom board
  2001-08-24 20:46 Linux 2.4.4 on 860 custom board Elan Feingold
@ 2001-08-24 20:59 ` Wolfgang Denk
  0 siblings, 0 replies; 2+ messages in thread
From: Wolfgang Denk @ 2001-08-24 20:59 UTC (permalink / raw)
  To: Elan Feingold; +Cc: Linuxppc-Embedded@Lists. Linuxppc. Org


In message <NDBBLJKOJGKDOFBHNPGEMEIICEAA.elan@nxnetworks.com> you wrote:
>
> I'd have no problem.  The IMMR is at the right place (0xff000000), and in
> general the kernel boots up fine, but it dies with a "kernel access of bad
> area" where the actual address is question is usually strange (e.g.
...

Ummm...

> I'd usually think it was a memory timing setup problem, right?  But VxWorks

Maybe, but I don't think so here.

> runs fine, and has for years on the board.

For years? Which mask revision is your CPU, then? Did you enable  the
CPU6  bug  workaround  in  the kernel configuration for a try, and/or
disabled the data cache?

> Any ideas?  Is it possible that VxWorks just has less strict timing
> requirements to run?

Probably it does not use the MMU as much.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"Life, loathe it or ignore it, you can't like it."
- Marvin the paranoid android

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-08-24 20:59 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-08-24 20:46 Linux 2.4.4 on 860 custom board Elan Feingold
2001-08-24 20:59 ` Wolfgang Denk

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).