From: David Miller <davem@davemloft.net>
To: lists@nerdbynature.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60
Date: Fri, 05 Feb 2010 21:32:20 -0800 (PST) [thread overview]
Message-ID: <20100205.213220.147487541.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.01.1002052106400.3483@bogon.housecafe.de>
From: Christian Kujau <lists@nerdbynature.de>
Date: Fri, 5 Feb 2010 21:13:00 -0800 (PST)
> On Fri, 5 Feb 2010 at 12:01, David Miller wrote:
>> Can you rerun your test with the following patch applied?
>> It will obtain more information for the btrfs developers.
>
> Thanks, David! Here it is:
>
> [ 1861.965178] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
> [ 1862.060546] Caller [100a6044:crc32c+0x44/0x80 [libcrc32c]]
> [ 1862.126652] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
> [ 1862.221928] Caller [100a6044:crc32c+0x44/0x80 [libcrc32c]]
>
> It's always libcrc32c and the numbers stay the same too. Full dmesg here:
> http://nerdbynature.de/bits/2.6.33-rc6/btrfs/
My debugging patch didn't work correctly.
Can you try using this one instead?
Thanks!
diff --git a/arch/sparc/kernel/unaligned_64.c b/arch/sparc/kernel/unaligned_64.c
index 378ca82..cbde2ea 100644
--- a/arch/sparc/kernel/unaligned_64.c
+++ b/arch/sparc/kernel/unaligned_64.c
@@ -283,6 +283,9 @@ static void log_unaligned(struct pt_regs *regs)
count++;
printk("Kernel unaligned access at TPC[%lx] %pS\n",
regs->tpc, (void *) regs->tpc);
+ printk("Caller [%lx:%pS]\n",
+ regs->tnpc,
+ (void *) regs->tnpc);
}
}
next prev parent reply other threads:[~2010-02-06 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 18:36 Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 Christian Kujau
2010-02-05 20:01 ` David Miller
2010-02-06 5:13 ` Christian Kujau
2010-02-06 5:32 ` David Miller [this message]
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=20100205.213220.147487541.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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