From: "wei liu" <wei.liu@esstech.com>
To: <linux-mips@linux-mips.org>
Subject: is there any cache problem with 4kc core?
Date: Wed, 21 Jan 2004 10:13:51 -0800 [thread overview]
Message-ID: <000e01c3e04a$52f38a80$6a0d12ac@ess> (raw)
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
I met a crash problem when trying linux2.4.18 on 4kc board. When the kernel starts thread to run function init, it will crash, showing Unhandled kernel unaligned access in unaligned.c:emulate_load_store_insn, line 3
51:
while it is ok for me to run linux2.4.3
Following is chip detail.
CPU revision is: 00018004
Primary instruction cache 8kb, linesize 16 bytes (2 ways)
Primary data cache 8kb, linesize 16 bytes (2 ways)
Linux version 2.4.18-MIPS-01.01 (gcc version 3.0)
[-- Attachment #2: Type: text/html, Size: 929 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "wei liu" <wei.liu@esstech.com>
To: linux-mips@linux-mips.org
Subject: is there any cache problem with 4kc core?
Date: Wed, 21 Jan 2004 10:13:51 -0800 [thread overview]
Message-ID: <000e01c3e04a$52f38a80$6a0d12ac@ess> (raw)
Message-ID: <20040121181351.ptmVIoaB4O-LeGOIvpYG6EDV7JJnc_IKJrepk6NICqA@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
I met a crash problem when trying linux2.4.18 on 4kc board. When the kernel starts thread to run function init, it will crash, showing Unhandled kernel unaligned access in unaligned.c:emulate_load_store_insn, line 3
51:
while it is ok for me to run linux2.4.3
Following is chip detail.
CPU revision is: 00018004
Primary instruction cache 8kb, linesize 16 bytes (2 ways)
Primary data cache 8kb, linesize 16 bytes (2 ways)
Linux version 2.4.18-MIPS-01.01 (gcc version 3.0)
[-- Attachment #2: Type: text/html, Size: 929 bytes --]
next reply other threads:[~2004-01-21 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 18:13 wei liu [this message]
2004-01-21 18:13 ` is there any cache problem with 4kc core? wei liu
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='000e01c3e04a$52f38a80$6a0d12ac@ess' \
--to=wei.liu@esstech.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