From: Dennis Grevenstein <dennis@pcde.inka.de>
To: linux-mips@linux-mips.org
Subject: Re: unable to handle kernel paging request
Date: Sun, 31 Oct 2004 20:55:50 +0100 [thread overview]
Message-ID: <20041031195550.GA12397@aton.pcde.inka.de> (raw)
In-Reply-To: <20041031192653.GG2094@lug-owl.de>
On Sun, Oct 31, 2004 at 08:26:53PM +0100, Jan-Benedict Glaw wrote:
> System.map is a list of function start addresses. Typically, functions
> don't crash at their very first instructions, this is why you don't see
> "exact" matches.
okay.
> From my fading MIPS knowledge, ip22zilog_interrupt called
> ip22zilog_receive_chars and the later one crashed. Now, use objdump and
> create a disassembly dump of the object file that contains the IP22
> Zilog stuff. There, find the part that's 0x20 bytes away from the start
> of ip22zilog_receive_chars. Now you know the cause of this oops.
That's what I found:
8810da14: 8c82001c lw v0,28(a0)
8810da18: 00809021 move s2,a0
8810da1c: 8c510000 lw s1,0(v0)
8810da20: 00a09821 move s3,a1
8810da24: 8e220118 lw v0,280(s1)
and:
8810e224: 0e04367f jal 8810d9fc <ip22zilog_receive_chars>
8810e228: 02803021 move a2,s4
8810e22c: 0a04386e j 8810e1b8 <ip22zilog_interrupt+0xd8>
8810e230: 32020001 andi v0,s0,0x1
8810e234: 0e0437bc jal 8810def0 <ip22zilog_transmit_chars>
> From
> here, try to figure out the reason for it...
Well, I'm sure "MIPS assembly for Dummies" must be available
somewhere. While I keep looking please help me ;-)
mfg
Dennis
--
There is certainly no purpose in remaining in the dark
except long enough to clear from the mind
the illusion of ever having been in the light.
T.S. Eliot
next prev parent reply other threads:[~2004-10-31 19:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 18:42 unable to handle kernel paging request Dennis Grevenstein
2004-10-31 19:15 ` Jan-Benedict Glaw
[not found] ` <Pine.GSO.4.10.10410311947570.9753-100000@helios.et.put.poznan.pl>
2004-10-31 19:16 ` Dennis Grevenstein
2004-10-31 19:26 ` Jan-Benedict Glaw
2004-10-31 19:26 ` Jan-Benedict Glaw
2004-10-31 19:55 ` Dennis Grevenstein [this message]
2004-10-31 20:13 ` Jan-Benedict Glaw
2004-10-31 22:36 ` Dennis Grevenstein
2004-10-31 23:59 ` Maciej W. Rozycki
2004-11-01 21:50 ` Florian Lohoff
2004-10-31 22:51 ` Dennis Grevenstein
2004-10-31 23:13 ` Dennis Grevenstein
-- strict thread matches above, loose matches on Subject: below --
2019-11-15 15:26 Lange Norbert
2019-11-15 15:41 ` Jan Kiszka
2016-09-15 14:08 Mark Gavalda
2016-09-15 16:05 ` Chris Mason
2016-09-15 20:12 ` Mark Gavalda
2016-09-16 2:45 ` Duncan
2007-09-27 16:30 Unable " Laurent Vivier
[not found] ` <46FBDA8A.8030109-6ktuUTfB/bM@public.gmane.org>
2007-09-27 16:54 ` Laurent Vivier
[not found] ` <46FBE055.2040904-6ktuUTfB/bM@public.gmane.org>
2007-09-30 9:07 ` Avi Kivity
[not found] ` <46FF6764.5090502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-01 6:58 ` Laurent Vivier
2006-08-12 18:48 Ian Pratt
2006-08-13 0:08 ` Keir Fraser
2006-08-14 5:44 ` Steve Traugott
2006-08-05 7:38 blocking Xen 3.X production use: soft lockup bugs Ian Pratt
2006-08-12 1:50 ` Unable to handle kernel paging request Steve Traugott
2006-08-12 4:34 ` Steve Traugott
2006-08-12 5:50 ` Steve Traugott
2006-08-12 9:50 ` Keir Fraser
2005-01-12 18:43 Praedor Atrebates
2004-03-03 16:33 Paulo Marques
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=20041031195550.GA12397@aton.pcde.inka.de \
--to=dennis@pcde.inka.de \
--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.