Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Dennis Grevenstein <dennis@pcde.inka.de>
Cc: linux-mips@linux-mips.org
Subject: Re: unable to handle kernel paging request
Date: Sun, 31 Oct 2004 21:13:35 +0100	[thread overview]
Message-ID: <20041031201335.GH2094@lug-owl.de> (raw)
In-Reply-To: <20041031195550.GA12397@aton.pcde.inka.de>

[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]

On Sun, 2004-10-31 20:55:50 +0100, Dennis Grevenstein <dennis@pcde.inka.de>
wrote in message <20041031195550.GA12397@aton.pcde.inka.de>:
> On Sun, Oct 31, 2004 at 08:26:53PM +0100, Jan-Benedict Glaw wrote:
> > 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)

It's accessing (most probably) a structure's first field, where the
structure is supplied by pointer in v0.

> 8810da20:       00a09821        move    s3,a1   
> 8810da24:       8e220118        lw      v0,280(s1) 

So now, find out what v0 belongs to. Maybe compiling the kernel with
debug infos (-g) and using objdump -S (for intermixing sources) will
help you.

Most probably, something wasn't correctly registered, so the pointer to
a struct is just a NULL pointer.

> 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>

So this all fits properly :-)

> > 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 ;-)

"objdump -S" for starters, but it seems quite straight forward. Maybe
paste the code of ip22zilog_receive_chars, I don't  have that at hands
right now...

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-10-31 20:13 UTC|newest]

Thread overview: 12+ 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
2004-10-31 20:13         ` Jan-Benedict Glaw [this message]
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

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=20041031201335.GH2094@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox