From: Eric Sandeen <sandeen@redhat.com>
To: Dave Jones <davej@redhat.com>,
Norbert Preining <preining@logic.at>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: another ext3 kernel BUG
Date: Mon, 13 Jun 2011 22:32:20 -0500 [thread overview]
Message-ID: <4DF6D644.3010109@redhat.com> (raw)
In-Reply-To: <20110614032111.GA5392@redhat.com>
On 6/13/11 10:21 PM, Dave Jones wrote:
> On Tue, Jun 14, 2011 at 11:43:07AM +0900, Norbert Preining wrote:
>
> > > You seem uniquely able to hit it, and you do have a truckload of interesting modules loaded. :)
> >
> > Interesting modules?
> > alsa stuff, bluetooth, fuse/fat/vfat for ntfs/external drives, wlan
> > the only thing that stand out is the vbox* I guess, all the others are
> > pretty standard, aren't they?
>
> we've been getting a lot of bug reports in Fedora that have the vbox module
> loaded that manifest in various ways that look like it's corrupting kernel data
> structures. (Usually it scribbles over some linked list, and the CONFIG_LIST_DEBUG
> stuff catches it).
>
> I'd definitly try and reproduce it without that having been loaded if you can.
>
> Dave
Yep, that's what I thought was "interesting" :)
-Eric
next prev parent reply other threads:[~2011-06-14 3:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 2:17 ext3 and btrfs various Oops and kernel BUGs Norbert Preining
2011-06-14 1:19 ` another ext3 kernel BUG Norbert Preining
2011-06-14 2:19 ` Eric Sandeen
2011-06-14 2:43 ` Norbert Preining
2011-06-14 3:21 ` Dave Jones
2011-06-14 3:32 ` Eric Sandeen [this message]
2011-06-14 4:03 ` Norbert Preining
2011-06-15 1:23 ` Norbert Preining
2011-06-15 8:09 ` Török Edwin
2011-06-15 21:06 ` [PATCH] fix wrong iput on d_inode introduced by e6bc45d65d Török Edwin
2011-06-16 5:51 ` another ext3 kernel BUG Norbert Preining
2011-06-16 7:02 ` Török Edwin
2011-06-16 8:28 ` Norbert Preining
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=4DF6D644.3010109@redhat.com \
--to=sandeen@redhat.com \
--cc=davej@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/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;
as well as URLs for NNTP newsgroup(s).