All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi <opencode@gmx.net>
To: linux-mips@linux-mips.org
Subject: Problems booting Linux kernel on Sigma SMP8634 #2
Date: Wed, 05 Mar 2008 13:35:20 +0100	[thread overview]
Message-ID: <47CE9388.9050808@gmx.net> (raw)

Hey folks,

first of all, sorry for _waisting_ the list with that topic again and again!

this question is related to that one here, posted sooner on this list:
http://www.linux-mips.org/archives/linux-mips/2008-02/msg00032.html

I spent a bit more time on this topic and found out that there is
seriously something going wrong with memory initialization and/or
handling during Linux startup.

I simply add "mem=32m" to the kernel command line, and the kernel runs
longer, at least a bit. However, it than stops with nearly the same
issue: Unable to handle kernel paging request at virtual address, but
different addresses. Tried "16m, 64m" and other values, all behave in
different way. Resulting to a crash at the position w/o any parameter or
 a bit later on.

Since I am not so familiar MIPS and especially the fact that our hard-
and software is more than closed, I am asking you guys to point me where
to spend more time on in order to get this issue fixed and fire up a
kernel on this box.

I am sure there some more guys around using the smp8634. Is it necessary
to load the microcode in order to get the kernel starting up?
Maybe we don't need the audio/video-ucode but irq-handler-ucode looks
very usefull ;-) Do we just have to copy this code at a certain memory
address?


Thank you in advance ...

Regards,
	Andi

             reply	other threads:[~2008-03-05 12:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 12:35 Andi [this message]
2008-03-05 17:03 ` Problems booting Linux kernel on Sigma SMP8634 #2 David Daney
2008-03-05 18:25   ` Andi
2008-03-13 10:11     ` Andi

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=47CE9388.9050808@gmx.net \
    --to=opencode@gmx.net \
    --cc=linux-mips@linux-mips.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.