From: Miao Xie <miaox@cn.fujitsu.com>
To: Adi <adalbert.b@gmx.de>
Cc: liubo2009@cn.fujitsu.com, linux-btrfs@vger.kernel.org
Subject: Re: wanted X found X-1 but you got X-2
Date: Mon, 02 Aug 2010 09:04:27 +0800 [thread overview]
Message-ID: <4C56199B.8090400@cn.fujitsu.com> (raw)
In-Reply-To: <20100731163424.105410@gmx.net>
Hi, Adi
On Sat, 31 Jul 2010 18:34:24 +0200, Adi wrote:
> ok, i have tried the 2.6.35-rc6 kernel, as TiCPU on #btrfs suggested, but i also got an error. i don't think it has something to do with kcrypt, as i can mount another partition without any problems.
[snip]
> ------------[ cut here ]------------
> kernel BUG at fs/btrfs/async-thread.c:603!
> invalid opcode: 0000 [#1] PREEMPT
[snip]
> Call Trace:
> [<c13fc670>] ? kcryptd_crypt+0x0/0x360
> [<c10d99e1>] ? bio_endio+0x11/0x30
> [<c10d99e1>] ? bio_endio+0x11/0x30
> [<c10d99e1>] ? bio_endio+0x11/0x30
> [<c1041032>] ? worker_thread+0xf2/0x230
> [<c1040f40>] ? worker_thread+0x0/0x230
> [<c156d3ab>] ? schedule+0x1ab/0x4c0
> [<c10448d0>] ? autoremove_wake_function+0x0/0x40
> [<c1040f40>] ? worker_thread+0x0/0x230
> [<c10444f4>] ? kthread+0x74/0x80
> [<c1044480>] ? kthread+0x0/0x80
> [<c1002fb6>] ? kernel_thread_helper+0x6/0x10
It seems this problem is the same as the one I have fixed.
Could you try to applied the following patches and test again?
http://lkml.org/lkml/2010/7/29/86
http://lkml.org/lkml/2010/7/29/84
http://lkml.org/lkml/2010/7/29/82
Thanks
Miao
next prev parent reply other threads:[~2010-08-02 1:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 13:11 wanted X found X-1 but you got X-2 Adi
2010-07-30 5:37 ` liubo
2010-07-30 7:13 ` Adi
2010-07-31 16:34 ` Adi
2010-08-02 1:04 ` Miao Xie [this message]
2010-08-02 19:37 ` Adi
2010-08-03 13:07 ` Miao Xie
2010-08-05 16:04 ` adi
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=4C56199B.8090400@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=adalbert.b@gmx.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.com \
/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.