LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Rossi <srossi@labs.mot.com>
To: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: strange crashes
Date: Mon, 15 Apr 2002 07:34:36 -0500	[thread overview]
Message-ID: <3CBAC8DC.680E0E63@labs.mot.com> (raw)


Hi All,
Wondering if anyone has seen this ... I've been periodically fighting
some pseudo-random crashes. These occur always during kernel boot, and
occur consistenly (i.e. at the same address) for a given kernel build.
The crash usually occurs right after kswapd starts or somewhere in the
following inittasks where I get a kernel oops with access to bad area.
I say these are pseudo random, because they depend on how the kernel is
built. A given build will either work always or work never. Some of the
things that I've observed that causes it to not work are things like
adding config options that make the kernel bigger, compiling with
debugging symbols - and (don't laugh) changing the path to the kernel.
Thats right, an identical kernel placed at two different paths, compiled
clean from both locations - one will boot and run fine, the other will
crash during boot.
I'm using the MontaVista tools from the 2.0 Journeyman and the 2.4.16
kernel with some modifications on custom hardware. I'm certain its not a
hardware problem, because once I get a kernel that boots, it runs
solidly. In my latest encounter with this problem, it happened when
I added one file to my initial ramdisk - thereby increasing its size by
a few K - absolutely nothing else changed. Before that the same exact
kernel booted and ran solidly, now it does not. I'm fairly certain that
the problem is not just size related, though that seems to play some
role. I suspect some kind of a compiler or linker problem but I wanted
to ask around before spending too much time digging into it. Any similar
experiences or ideas of what might be going on?

Thanks,
Steve

--
-------------------------------------------------------
Steven K. Rossi                     srossi@labs.mot.com
Senior Staff Engineer
Multimedia Communications Research Laboratory
Motorola Labs
-------------------------------------------------------


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

             reply	other threads:[~2002-04-15 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15 12:34 Steve Rossi [this message]
2002-04-15 12:40 ` strange crashes Christian Pellegrin
  -- strict thread matches above, loose matches on Subject: below --
2002-04-15 12:49 Goddeeris Frederic

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=3CBAC8DC.680E0E63@labs.mot.com \
    --to=srossi@labs.mot.com \
    --cc=linuxppc-embedded@lists.linuxppc.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