From: Andi <opencode@gmx.net>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-mips@linux-mips.org
Subject: Re: Problems booting Linux kernel on Sigma SMP8634
Date: Fri, 08 Feb 2008 10:24:05 +0100 [thread overview]
Message-ID: <47AC1FB5.4060208@gmx.net> (raw)
In-Reply-To: <47AB5614.5010804@avtrex.com>
Hey David,
> You need symbols so that you can interpret the stack trace. It is
> impossible to tell anything without that.
Unfortunately, we don't have much more than just the binary kernel
image. No sources. No memory map.
How can I find out which functions do correspondent to these addresses?
I thought about that this might be a common problem, if one doesn't load
a certain ucode, maybe the interrupt-handler or so ..
>> Determined physical RAM map:
>> memory: 05ee0000 @ 10020000 (usable)
>
> This seems like an odd value. I would expect either 03fe0000 or 07fe0000
This was also my first guess. But this seems to be ok, as you can see on
the "reference" output here:
http://www.networkedmediatank.com/viewtopic.php?t=457
This box has a total of 128MB of memory ..
>
> David Daney
>
Regards,
Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi <opencode@gmx.net>
Cc: linux-mips@linux-mips.org
Subject: Re: Problems booting Linux kernel on Sigma SMP8634
Date: Fri, 08 Feb 2008 10:24:05 +0100 [thread overview]
Message-ID: <47AC1FB5.4060208@gmx.net> (raw)
Message-ID: <20080208092405.sP4qQOg4Y6aRMcAxCdTh8lt2ptGhSJatRScGDmX7ftE@z> (raw)
In-Reply-To: <47AB5614.5010804@avtrex.com>
Hey David,
> You need symbols so that you can interpret the stack trace. It is
> impossible to tell anything without that.
Unfortunately, we don't have much more than just the binary kernel
image. No sources. No memory map.
How can I find out which functions do correspondent to these addresses?
I thought about that this might be a common problem, if one doesn't load
a certain ucode, maybe the interrupt-handler or so ..
>> Determined physical RAM map:
>> memory: 05ee0000 @ 10020000 (usable)
>
> This seems like an odd value. I would expect either 03fe0000 or 07fe0000
This was also my first guess. But this seems to be ok, as you can see on
the "reference" output here:
http://www.networkedmediatank.com/viewtopic.php?t=457
This box has a total of 128MB of memory ..
>
> David Daney
>
Regards,
Andi
next prev parent reply other threads:[~2008-02-08 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 18:41 Problems booting Linux kernel on Sigma SMP8634 Andi
2008-02-07 19:03 ` David Daney
2008-02-08 9:24 ` Andi [this message]
2008-02-08 9:24 ` 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=47AC1FB5.4060208@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox