From: Valentin R Sitsikov <valentin.sitdikov@siemens.com>
To: linux-sh@vger.kernel.org
Subject: Possibly icahe/dcache synchronization problem on sh7785lcr
Date: Fri, 09 Oct 2009 12:55:30 +0000 [thread overview]
Message-ID: <4ACF32C2.9010501@siemens.com> (raw)
Hello.
During execution of user space application form time to time
invalid instruction or bus error occured or even init dies during sturtup.
The situation became more stable if i use the following code:
static void sh4_flush_icache_page(void *arg)
{
flush_dcache_all();
flush_icache_all();
}
...
local_flush_icache_page = sh4_flush_icache_page;
This is done because previous experience with 2.6.20 on sdk7785.
There was the similar problems (at least it looks like).
So my question is if it really might be icache/dcache synchronization
problem or something different.
May be somebody has had the same problems and know how to solve it right?
I have the following configuration:
sh7785lcr
2.6.32-rc2. pagesize = 8K (avoid cache alias problem)
uclibc-9.28 with pagesize = 8k
Example of illegal instruction execution:
...
[ 7.408000] VFS: Mounted root (nfs filesystem) on device 0:12.
[ 7.416000] Freeing unused kernel memory: 136k freed
init started: BusyBox v1.01 (Slind 1:1.01-2.slind3) multi-call binary
init: Bummer, can't write to log on /dev/vc/5!
Starting pid 881, console /dev/ttySC1: '/etc/init.d/rcS'
Loading kernel modules
cat: /etc/modules: No such file or directory
Done loading modules
.: 15: Can't open /lib/lsb/init-functions
Activating swap.
Cleaning up ifupdown...done.
Starting OpenBSD Secure Shell server: sshdIllegal instruction
...
Example of unfixed unaligned access:
[ 7.416000] Freeing unused kernel memory: 136k freed
init started: BusyBox v1.01 (Slind 1:1.01-2.slind3) multi-call binary
init: Bummer, can't write to log on /dev/vc/5!
Starting pid 881, console /dev/ttySC1: '/etc/init.d/rcS'
Loading kernel modules
cat: /etc/modules: No such file or directory
Done loading modules
.: 15: Can't open /lib/lsb/init-functions
Activating swap.
Cleaning up ifupdown...done.
[ 9.764000] Unaligned userspace access in "sshd" pid\x1020
pc=0x29684740 ins=0x2f86
[ 9.776000] Fixing up unaligned userspace access in "sshd" pid\x1020
pc=0x29684740 ins=0x2f86
Starting OpenBSD Secure Shell server: sshd[ 9.916000] Unaligned
userspace access in "sshd" pid\x1027 pc=0x296731e4 ins=0x2f96
[ 9.924000] Fixing up unaligned userspace access in "sshd" pid\x1027
pc=0x296731e4 ins=0x2f96
[ 9.932000] Unaligned userspace access in "sshd" pid\x1027
pc=0x296731f2 ins=0x0103
[ 9.940000] Fixing up unaligned userspace access in "sshd" pid\x1027
pc=0x296731f2 ins=0x0103
[ 9.948000] Sending SIGBUS to "sshd" due to unaligned access (PC
b3325bf8 PR 296731f6)
Bus error
Best regards,
Valentin.
next reply other threads:[~2009-10-09 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 12:55 Valentin R Sitsikov [this message]
2009-10-13 2:16 ` Possibly icahe/dcache synchronization problem on sh7785lcr Paul Mundt
2009-10-13 8:13 ` Valentin R Sitsikov
2009-10-13 10:25 ` Paul Mundt
2009-10-13 12:44 ` Valentin R Sitsikov
2009-10-13 13:08 ` Paul Mundt
2009-10-13 13:58 ` Paul Mundt
2009-10-13 14:05 ` Valentin R Sitsikov
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=4ACF32C2.9010501@siemens.com \
--to=valentin.sitdikov@siemens.com \
--cc=linux-sh@vger.kernel.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.