From: Drasko DRASKOVIC <drasko.draskovic@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Unaligned kernel access for __udivsi3_i4i
Date: Fri, 19 Feb 2010 23:51:38 +0000 [thread overview]
Message-ID: <5ec3d7931002191551g21c0cda9le17729529b1afd78@mail.gmail.com> (raw)
Hi all,
I am getting Unaligned kernel access on 0x809b7662
(gdb) disassemble 0x809b7662 0x809b7762
Dump of assembler code from 0x809b7662 to 0x809b7762:
0x809b7662 <__udivsi3_i4i+54>: mov.l @(r0,r1),r1
0x809b7664 <__udivsi3_i4i+56>: mov r5,r0
0x809b7666 <__udivsi3_i4i+58>: tst #-2,r0
0x809b7668 <__udivsi3_i4i+60>: mova 0x809b784c <__sdivsi3_i4i+336>,r0
...
Can it be related to __udivsi3_i4i and toolchain problem, mentioned
here http://209.85.229.132/search?qÊche:7eePA2ixT4gJ:www.sfr-fresh.com/linux/misc/v2.6/ChangeLog-2.6.21+__udivsi3_i4i+unaligned+access+st+linux&cd\x10&hl=en&ct=clnk
Can this be the reason that my app is crashing (after some time) with
SIGBUS errors?
How can I further investigate problem of unaligned access in the
kernel, to check if it comes from kernel modules?
Best regards,
Drasko
next reply other threads:[~2010-02-19 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 23:51 Drasko DRASKOVIC [this message]
2010-02-20 0:08 ` Unaligned kernel access for __udivsi3_i4i Matt Fleming
2010-02-20 0:24 ` Drasko DRASKOVIC
2010-02-20 11:47 ` Matt Fleming
2010-02-20 12:17 ` Paul Mundt
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=5ec3d7931002191551g21c0cda9le17729529b1afd78@mail.gmail.com \
--to=drasko.draskovic@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).