From: Scott Wood <scottwood@freescale.com>
To: Geoffrey Bugniot <g.bugniot@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Memory management problems on a custom PPC 8270 board
Date: Mon, 23 Jul 2012 11:48:39 -0500 [thread overview]
Message-ID: <500D8067.6070805@freescale.com> (raw)
In-Reply-To: <loom.20120723T170223-328@post.gmane.org>
On 07/23/2012 10:34 AM, Geoffrey Bugniot wrote:
> Hi,
>
> I've ported on a custom board U-Boot and Linux 2.6.39.4. It seems to work
> well until the kernel is begin to manipulate "data/file" with a size larger
> than about 5 Mo. I suppose that's a VM management problem, but I'm not
> sure.
>
> In fact, when I use "cp file1 file2" with file1 >= 5/6 Mo, the kernel panics.
> Same behaviour with a command like "tar cvf file.tar.gz file1 file2...".
>
> I got something like that :
>
> [ 148.891584] Kernel panic - not syncing: Attempted to kill init!
Was there anything before this?
> [ 148.897503] Call Trace:
> [ 148.899934] [c7829d10] [c0008fbc] show_stack+0x4c/0x138 (unreliable)
> [ 148.906470] [c7829d50] [c03be7d8] panic+0xa4/0x1e8
> [ 148.911401] [c7829db0] [c0025580] do_exit+0x94/0x630
> [ 148.916501] [c7829e00] [c0025bdc] do_group_exit+0x80/0xac
> [ 148.922071] [c7829e10] [c00340d8] get_signal_to_deliver+0x474/0x490
> [ 148.928515] [c7829e70] [c0009aa4] do_signal_pending.constprop.9+0x40/0x22c
> [ 148.935586] [c7829f30] [c0009d88] do_signal+0x24/0x50
> [ 148.940793] [c7829f40] [c000f76c] do_user_signal+0x74/0xc4
> [ 148.946419] --- Exception: 700 at 0xfec5394
> [ 148.946433] LR = 0x1000410c
> [ 148.954009] Rebooting in 3 seconds..
This looks like your init process crashed. You could try enabling
show_unhandled_signals in arch/powerpc/signal.c.
What are you running as your init process? Do you have a normal
init/login scheme, or are you running a shell (esp. busybox, which would
have cp built in) directly as init?
> When I use netsniff-ng, with default parameters, kernel hangs too. But If I
> specify a small ring buffer size with option "netsniff-ng -S 3MB" all is
> running fine. Here, is the dump when netsniff-ng causes a crash:
>
> root@pLinesE_VMEb:~# netsniff-ng
> netsniff-ng 0.5.5.0 -- pid (245)
> [ 36.065574] device eth0 entered promiscuous mode
> nice (0), scheduler (0 prio 0)
> 1 of 1 CPUs online, affinity bitstring (1)
> No device specified, using `eth0`.
> No filter applied. Switching to `all traffic`.
>
> [ 36.159714] BUG: Bad page state in process netsniff-ng pfn:05401
> [ 36.165759] page:c0401020 count:0 mapcount:1 mapping: (null) index:0x0
> [ 36.172548] page flags: 0x0()
Could you have bad memory timings (or bad memory)? Usually when I see
things like this, it's because memory is getting corrupted.
-Scott
next prev parent reply other threads:[~2012-07-23 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 15:34 Memory management problems on a custom PPC 8270 board Geoffrey Bugniot
2012-07-23 16:48 ` Scott Wood [this message]
2012-07-24 9:16 ` Geoffrey Bugniot
2012-07-27 15:14 ` Geoffrey Bugniot
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=500D8067.6070805@freescale.com \
--to=scottwood@freescale.com \
--cc=g.bugniot@gmail.com \
--cc=linuxppc-dev@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 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.