LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Schichan <nschichan@freebox.fr>
To: linuxppc-embedded@ozlabs.org
Subject: random panic and freezes on mpc8349 itx
Date: Fri, 7 Sep 2007 14:05:06 +0200	[thread overview]
Message-ID: <200709071405.06500.nschichan@freebox.fr> (raw)


Hi,

I am currently working with an MPC8349ITX board and I have some trouble with 
the kernel as soon as it reaches userland.

If I boot the kernel with all the memory (256MB) available (no mem=... on the 
command line), I get random freezes or random kernel panics. Some times it 
won't even run init. Some times it will panic badly if I try to put some 
pressure to the system (stress --cpu 256). Some times it will hang 
immediately after logging in, ...

If I boot the kernel with mem=64M, these freeze and random panic disapear and 
I am able to run the stress program without any problems.

I have had this strange behaviour on both kernel 2.6.20 and 2.6.22 with 
mpc834x_itx_defconfig (both from kernel.org) (ARCH=powerpc).

I am inclined to say that it is not a broken RAM chip problem because if I use 
a 2.6.17 from kernel.org with all the RAM available (ARCH=ppc) configured 
with mpc834x_sys_defconfig (there was no defconfig for the itx board on this 
version) everything runs fine and I am able to run the stress program without 
any problems.

The panic does not happen very often, 90% of the time, the board hangs and 
stops responding to ping. When a panic do happen it is almost always in a 
different place.

Does any of you have met this problem before ? If you have any clues about 
what is hapenning I'd be glad to hear about it :)

Thank you for your attention,

Regards,

-- 
Nicolas Schichan

             reply	other threads:[~2007-09-07 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07 12:05 Nicolas Schichan [this message]
2007-09-07 12:24 ` random panic and freezes on mpc8349 itx Clemens Koller
2007-09-07 21:16 ` Benedict, Michael
2007-09-10 13:48   ` Nicolas Schichan

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=200709071405.06500.nschichan@freebox.fr \
    --to=nschichan@freebox.fr \
    --cc=linuxppc-embedded@ozlabs.org \
    /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