From: Alexander Holler <holler@ahsoftware.de>
To: Jan Kara <jack@suse.cz>
Cc: Dan Carpenter <dan.carpenter@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at fs/buffer.c:3205 (stable 3.5.3)
Date: Tue, 02 Oct 2012 11:30:14 +0200 [thread overview]
Message-ID: <506AB426.4000407@ahsoftware.de> (raw)
In-Reply-To: <506960AE.2000402@ahsoftware.de>
Am 01.10.2012 11:21, schrieb Alexander Holler:
> Hello,
>
> Am 01.10.2012 11:10, schrieb Jan Kara:
>
>>> sha1sum Tainted: P O 3.5.4-00009-gfa43f23-dirty #228
>> BTW, fglrx moodule taints the kernel because it is a proprietary
>> driver.
>
> I know.
>
>> Can you reproduce the issue without this module loaded?
>
> I will try it with a clean 3.6. Most of the 9 additional patches here
> are for ARM boxes, but anyway. I will need a few days.
Just tried my "tar cp . | mbuffer | bzip2smp >/usb3/ext4/foo.tar.bz2
using a kernel 3.6 without using fglrx and without any additional
patches. The first try already ended up in a broken archive (tar djf =>
bzip2: Data integrity error when decompressing), but (again) without the
BUG() in fs/buffer.c getting hit. Will do some more tests, trying hit
that BUG().
Regards,
Alexander
next prev parent reply other threads:[~2012-10-02 9:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 11:34 kernel BUG at fs/buffer.c:3205 (stable 3.5.3) Alexander Holler
2012-09-25 11:02 ` Dan Carpenter
2012-09-27 11:45 ` Alexander Holler
2012-09-27 15:12 ` Jan Kara
2012-09-27 15:46 ` Alexander Holler
2012-09-27 16:20 ` Alexander Holler
2012-09-27 18:01 ` Alexander Holler
2012-09-27 18:12 ` Alexander Holler
2012-09-27 20:05 ` Jan Kara
2012-09-28 8:09 ` Alexander Holler
2012-09-27 20:03 ` Jan Kara
2012-09-29 19:07 ` Alexander Holler
2012-10-01 9:10 ` Jan Kara
2012-10-01 9:21 ` Alexander Holler
2012-10-02 9:30 ` Alexander Holler [this message]
2012-10-14 9:10 ` Alexander Holler
2012-10-14 12:27 ` Alan Cox
2012-10-15 8:46 ` Alexander Holler
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=506AB426.4000407@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=dan.carpenter@oracle.com \
--cc=jack@suse.cz \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).