From: Gregor Waltz <gregor.waltz@raritan.com>
To: linux-mips@linux-mips.org
Subject: Re: Toshiba JMR 3927 working setup?
Date: Fri, 04 Jan 2008 14:23:27 -0500 [thread overview]
Message-ID: <477E87AF.6010404@raritan.com> (raw)
In-Reply-To: <20080104185130.GB6532@paradigm.rfc822.org>
Florian Lohoff wrote:
> On Fri, Jan 04, 2008 at 01:40:46PM -0500, Gregor Waltz wrote:
>
>> CRC Check passed
>> Image Started At Address 0x80020000.
>> Image Length = 3424394 (0x34408a).
>> Exception! EPC=80056eb4 CAUSE=30000008(TLBL)
>> 80056eb4 8ce4000c lw a0,12(a3) # 0xc
>>
>
> The exception comes from PMON too - Did you look up the EPC in your
> System.map file ?
>
>
>> Further, the exception gets printed immediately after "Image Length =
>> 3424394 (0x34408a)." The exception happens so soon that I doubt that the
>> kernel does very much beforehand.
>>
>
> The kernel seems to be initializing and steps upon an virtual address
> and triggers an TLB exception which as the kernel is not yet ready
> to handle it itself, thus PMONs exception handler gets triggered.
>
> My first guess is that you are catching a NULL Pointer exception
> somewhere.
>
> FLo
>
Linux 2.6.23.9:
80056eb4 T kernel_execve
My coworker built Linux 2.6.23.12 and got:
EPC=80056ee0 which does not correspond to anything in his System.map.
With a different set of tools, I also built 2.6.21.7 and got:
EPC=80056eb8 which also does not correspond to anything in the
corresponding System.map.
If this does not ring any bells, do you have any suggestions for how I
could debug this issue?
Thanks
next prev parent reply other threads:[~2008-01-04 19:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 16:45 Toshiba JMR 3927 working setup? Gregor Waltz
2008-01-04 17:21 ` Thiemo Seufer
2008-01-04 18:40 ` Gregor Waltz
2008-01-04 18:51 ` Florian Lohoff
2008-01-04 19:23 ` Gregor Waltz [this message]
2008-01-04 19:23 ` Thiemo Seufer
2008-01-04 22:27 ` Gregor Waltz
2008-01-05 14:42 ` Atsushi Nemoto
2008-01-07 12:21 ` Ralf Baechle
2008-01-07 15:34 ` Atsushi Nemoto
2008-01-05 15:07 ` Atsushi Nemoto
2008-01-11 17:49 ` Gregor Waltz
2008-01-12 12:17 ` Atsushi Nemoto
2008-01-15 15:50 ` Gregor Waltz
2008-01-15 15:50 ` Gregor Waltz
2008-01-15 16:14 ` Thiemo Seufer
2008-01-15 20:05 ` Gregor Waltz
2008-01-15 23:14 ` Thiemo Seufer
2008-01-16 15:28 ` Gregor Waltz
2008-01-16 16:04 ` Atsushi Nemoto
2008-01-17 16:50 ` Gregor Waltz
2008-01-18 1:05 ` Atsushi Nemoto
2008-01-05 14:45 ` Ralf Baechle
2008-01-08 23:54 ` Gregor Waltz
2008-01-09 0:17 ` Thiemo Seufer
2008-02-04 1:14 ` M. Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2008-01-25 16:50 Max Okumoto
2008-01-26 5:08 ` Atsushi Nemoto
2008-01-28 16:36 ` Gregor Waltz
2008-01-29 13:50 ` Atsushi Nemoto
2008-03-06 15:49 ` Ralf Baechle
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=477E87AF.6010404@raritan.com \
--to=gregor.waltz@raritan.com \
--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