From: Tim Wu <chtimwu@libra.seed.net.tw>
To: linux-mips <linux-mips@oss.sgi.com>
Subject: LEXRA MIPS
Date: Fri, 12 Apr 2002 15:29:12 +0800 [thread overview]
Message-ID: <3CB68CC8.1050207@libra.seed.net.tw> (raw)
Hi, everybody:
I'm working on porting Linux to a MIPS based processor whose IP is from
Lexra's LX4189 processor.
I started my work from the linux MIPS port of oss.sgi.com. Right now
the kernel can boot and run some user applications well.
But I met a problem that once a process raises any kind of signal,
kernel will send a SIGILL signal to the process which let the process stop.
I traced the kernel source and found SIGILL is sent by the exception
handler, do_ri().
The problem is very weird because when I change to another crosscompiler
or insert some asserting code to functions in signal.c. The kernel
become unbootable. I hope someone can give me directions to solve this
bug or tell me who already done Linux on Lexra?
kernel version:2.4.17.
toolchain: GCC 3.1 from ftp.cotw.com.
use new IRQ and new timer interface.
next reply other threads:[~2002-04-12 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 7:29 Tim Wu [this message]
2002-04-12 11:41 ` LEXRA MIPS Bradley D. LaRonde
2002-04-12 11:41 ` Bradley D. LaRonde
2002-04-13 8:02 ` Tim Wu
2002-04-13 14:44 ` Bradley D. LaRonde
2002-04-13 14:44 ` Bradley D. LaRonde
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=3CB68CC8.1050207@libra.seed.net.tw \
--to=chtimwu@libra.seed.net.tw \
--cc=linux-mips@oss.sgi.com \
/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