From: Thomas Backlund <tmb@mandriva.org>
To: linux-kernel@vger.kernel.org
Cc: ataraid-list@redhat.com, linux-raid@vger.kernel.org
Subject: kernel BUG at fs/scache.c:670
Date: Thu, 28 Jan 2010 01:01:25 +0200 [thread overview]
Message-ID: <4B60C5C5.3040604@mandriva.org> (raw)
Hi, (please cc me on response)
I'm hitting a kernel BUG at fs/scache.c:670 bug using dmraid on 2.6.32
and 2.6.33-rc5-git2 kernels:
Distro: Mandriva Linux Cooker
Arch: x86_64
Hardware: Intel ICH10R with 4 x 500GB disks in biosraid10,
System has 8GB ram
OOPS: http://tmb.mine.nu/Mandriva/Cooker/bugs/fs-dcache-bug/dsc00918.jpg
config: http://tmb.mine.nu/Mandriva/Cooker/bugs/fs-dcache-bug/x86_64.config
This happends on 2.6.33-rc5-git2, 2.6.32, and seems to be as old as
2.6.32-rc1.
2.6.31 is the latest kernel that actually boots on this system.
I tried to bisect between 2.6.31 and 2.6.32-rc1, but it failed...
Now before I start a second bisect, I decided to post here in case some
one has some suggestions / pointers...
--
Thomas
next reply other threads:[~2010-01-27 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 23:01 Thomas Backlund [this message]
2010-01-28 9:37 ` kernel BUG at fs/dcache.c:670 using dmraid Thomas Backlund
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=4B60C5C5.3040604@mandriva.org \
--to=tmb@mandriva.org \
--cc=ataraid-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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