Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: durai <durai@isofttech.com>
Cc: mips <linux-mips@linux-mips.org>
Subject: Re: Network problem in mips
Date: Fri, 12 Dec 2003 12:42:41 -0500	[thread overview]
Message-ID: <3FD9FE11.3060501@realitydiluted.com> (raw)
In-Reply-To: <001d01c3c083$be226600$0a05a8c0@DURAI>

durai wrote:
>
> Sorry for the incomplete information.
> My OS is uCLinux (linux kernel 2.4.10) . Whenever I start a high transfer
> through the wireless interface the system crashes, sometimes it hangs
> without any messages in the console. Here is the oops message.
>
No problem. You have a thick skin :). Let's take a look at things.

[SNIP]
> epc  : 80f930c1
> Status: 3000fc00
> Cause : 00000010
>
What is the function at '0x80f930c1'? If the function is less than 20 lines,
go ahead a paste it in. If not, compile with debugging symbols, use GDB on
the kernel and do a 'dissassem 0x80f930c1' and show us the lines that way.

[SNIP]
> Code:Unaligned memory access at 8020b780, address 80f930b5, PID -2142680720
> ( )
> 
Well, you have an unaligned access, so hopefully we can see from the code
what you were trying to do. Looking forward to your reply.

-Steve

  reply	other threads:[~2003-12-12 17:42 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 [this message]
2003-12-13  2:48     ` 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=3FD9FE11.3060501@realitydiluted.com \
    --to=sjhill@realitydiluted.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox