public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
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 22:43:10 -0800 (PST)	[thread overview]
Message-ID: <20100205.224310.06173989.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.01.1002052226480.3483@bogon.housecafe.de>

From: Christian Kujau <lists@nerdbynature.de>
Date: Fri, 5 Feb 2010 22:28:47 -0800 (PST)

> Hm, now it looks like this, but I don't know how it'd reveal more 
> information:
> 
> [  210.707051] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
> [  210.802236] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]]
> [  210.874620] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
> [  210.969899] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]]
> [  228.724982] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
> [  228.820220] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]]
> [  228.892286] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs]
> [  228.987851] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]]
> 
> I'm open for more patches :-)

Confusing for me too.  I'll try to think about this some more.

  reply	other threads:[~2010-02-06  6:43 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
2010-02-06  6:28       ` Christian Kujau
2010-02-06  6:43         ` David Miller [this message]
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.224310.06173989.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