From: Ralf Baechle <ralf@linux-mips.org>
To: durai <durai@isofttech.com>
Cc: mips <linux-mips@linux-mips.org>
Subject: Re: Network problem in mips
Date: Sat, 13 Dec 2003 03:48:59 +0100 [thread overview]
Message-ID: <20031213024859.GA22208@linux-mips.org> (raw)
In-Reply-To: <001d01c3c083$be226600$0a05a8c0@DURAI>
On Fri, Dec 12, 2003 at 01:14:14PM +0530, durai wrote:
> Kernel unaligned instruction access in unaligned.c:do_ade, line 428:
> $0 : 00000000 a0000000 00097fff ffffffff 80fa228c ba000000 a0f40000 00000000
> $8 : 00000045 00000001 00ff0000 00ff0000 80fa228c 80f90738 00003b00 80fdd812
> $16: 80fa2000 80fe8221 80fe6010 00008da9 ff000000 00ff0000 80fa2000 a0f40000
> $24: 00000001 80494970 8043a000 8043a118 80fa228c 80f930c1
^^^^^^^^^^^^^^^^^
$28 is the current pointer, $29 the stack pointer.
> epc : 80f930c1
> Status: 3000fc00
> Cause : 00000010
> Process (pid: -2142680720, stackpage=8043a000)
You've overflowed the stack to the point where the process structure got
overwritten. which also explains the nonsense pid value. -2142680720 is
0x80494970 which is probably some valid kernel address.
Find what's consuming so much stack - you should only use a split fraction
of that. The epc value also looks quite strange because it's lowest bit is
set - does your CPU support MIPS16?
Ralf
prev parent reply other threads:[~2003-12-13 2:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 14:57 Network problem in mips durai
2003-12-11 15:25 ` Steven J. Hill
2003-12-11 23:07 ` Alan Cox
2003-12-11 23:30 ` Ralf Baechle
2003-12-11 23:46 ` Maciej W. Rozycki
2003-12-13 1:10 ` Ralf Baechle
2003-12-12 15:19 ` [uClinux-dev] " Paul Mundt
2003-12-12 19:25 ` Alan Cox
2003-12-12 7:44 ` durai
2003-12-12 17:42 ` Steven J. Hill
2003-12-13 2:48 ` Ralf Baechle [this message]
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=20031213024859.GA22208@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=durai@isofttech.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 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.