From: Christian Kujau <lists@nerdbynature.de>
To: linux-btrfs@vger.kernel.org
Cc: davem@davemloft.net
Subject: Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60
Date: Fri, 5 Feb 2010 10:36:52 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.01.1002051020020.3483@bogon.housecafe.de> (raw)
When writing to a newly created btrfs (vanilla 2.6.33-rc6, sparc64) the
following messages are printed:
[28617.650231] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
[28617.745783] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
[28654.589492] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
[28654.685036] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
[28689.595394] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
...and so on. I've seen these "unaligned access at TPC" on sparc64
before[0], but they were not btrfs related. Btw, *reading* does not cause
these messages.
At one point and when lots of I/O was going on, the following appeared once, inbetween
the other messages:
[31419.847052] Kernel unaligned access at TPC[102a3f18] btrfs_csum_final+0x38/0x60 [btrfs]
[31447.243224] Kernel unaligned access at TPC[102a3f18] btrfs_csum_final+0x38/0x60 [btrfs]
[31447.338727] Kernel unaligned access at TPC[102a3f18] btrfs_csum_final+0x38/0x60 [btrfs]
[33888.613296] btrfs: loop0 checksum verify failed on 39084032 wanted EAFC29EA found BBFFFFFF level 0
[34421.508271] Kernel unaligned access at TPC[102a3f18] btrfs_csum_final+0x38/0x60 [btrfs]
[34421.603872] Kernel unaligned access at TPC[102a3f18] btrfs_csum_final+0x38/0x60 [btrfs]
[34452.965546] Kernel unaligned access at TPC[102a3f18] btrfs_csum_final+0x38/0x60 [btrfs]
No messages from the backing device have been reported though, but I'm
not so sure about the system's RAM, so it might be a hardware issue after
all. I was not able to reproduce the "checksum verify failed" yet.
Full dmesg and .config: http://nerdbynature.de/bits/2.6.33-rc6/btrfs/
Christian.
[0] http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-02/msg01327.html
--
BOFH excuse #369:
Virus transmitted from computer to sysadmins.
next reply other threads:[~2010-02-05 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 18:36 Christian Kujau [this message]
2010-02-05 20:01 ` Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 David Miller
2010-02-06 5:13 ` Christian Kujau
2010-02-06 5:32 ` David Miller
2010-02-06 6:28 ` Christian Kujau
2010-02-06 6:43 ` David Miller
2010-02-08 21:46 ` Chris Mason
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=alpine.DEB.2.01.1002051020020.3483@bogon.housecafe.de \
--to=lists@nerdbynature.de \
--cc=davem@davemloft.net \
--cc=linux-btrfs@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.