public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Khalfallah Karim <aurelyen.tomp@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Linux-2.6.6 crash on Leon2-MMU (while init loads ELF busybox)
Date: Wed, 6 Jul 2005 19:23:16 +0200	[thread overview]
Message-ID: <100bdf0005070610231ce9067@mail.gmail.com> (raw)

In brief:
=========
	While booting Snapgear-Linux-2.6.6 on Leon2-MMU,
	crash of IU due to an unresolved virtual address
	of the 1st ELF binary launched by init process
	(it is actually in kernel mode, not in user mode yet)
In detail:
==========
	The situation:
		When the init process is getting ready to load the
		Busybox (which is in ELF format), probably to do a
		mount, the system wants to clear its bss section.
		So there's a call made to padzero() (coded in file
		<fs/binfmt_elf.c>) with an argument 'elf_bss' which
		equals the virtual base address of .bss.
		Currently I am using ROMfs, for I still can't handle
		non-versatile memory on my board (I mean at a hardware
		level).
	The trouble:
		When padzero() attempts to clear the first word of the
		.bss section, the virtual address does not seem to have
		been previously "MMU-resolved" by the system. Therefore,
		it crashes the IU.
	My questions:
		Q1: Has anyone any idea why the MMU has not been settled
		yet at the time the system attempts to clear the .bss
		section ?
		Q2: I should get an exception trap for accessing a 'bad'
		virtual address (I'm on Sparc) - why do the machine gets
		straight in IU error mode ?	

I have not registered yet to <lkml.org>, so please CC'me if you intend
to answer.

Thank you a lot,
Aurelyen.

                 reply	other threads:[~2005-07-07  0:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=100bdf0005070610231ce9067@mail.gmail.com \
    --to=aurelyen.tomp@gmail.com \
    --cc=linux-kernel@vger.kernel.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