From: Sven Joachim <svenjoac@gmx.de>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: 631255@bugs.debian.org, LKML <linux-kernel@vger.kernel.org>,
Johannes Wiedersich <debian@aktendiener.de>
Subject: Re: Bug#631255: 3.0-rc3: kernel BUG at fs/inode.c:1368!
Date: Wed, 22 Jun 2011 16:30:34 +0200 [thread overview]
Message-ID: <878vsu3pmd.fsf@turtle.gmx.de> (raw)
In-Reply-To: <1308750980.3093.470.camel__9654.87580183453$1308751219$gmane$org@localhost> (Ben Hutchings's message of "Wed, 22 Jun 2011 14:56:20 +0100")
On 2011-06-22 15:56 +0200, Ben Hutchings wrote:
> On Wed, 2011-06-22 at 08:36 +0200, Johannes Wiedersich wrote:
>> Package: linux-2.6
>> Version: 3.0.0~rc3-1~experimental.1
>> Severity: important
>>
>>
>> aptitude installing a package triggers a kernel oops. I have no idea,
>> what part of the installation process is to blame, but could try to
>> reproduce, if I would get further instructions.
> [...]
>
> I assume you haven't seen a similar crash in earlier versions?
This bug is specific to 3.0.0-rc3 and has been fixed in -rc4.
> Also, what type of filesystem where you installing on
> (ext3/ext4/btrfs/xfs...)?
I have seen it on ext4, but it's not really filesystem specific AFAIK.
>> /media/data/mattems/src/linux-2.6-3.0.0~rc3/debian/build/source_amd64_none/fs/inode.c:1368!
Fixed by commit 50338b889dc.
Cheers,
Sven
prev parent reply other threads:[~2011-06-22 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110622063624.7374.9343.reportbug@johannes4.fritz.box>
2011-06-22 13:56 ` 3.0-rc3: kernel BUG at fs/inode.c:1368! Ben Hutchings
2011-06-22 14:21 ` Johannes Wiedersich
[not found] ` <1308750980.3093.470.camel__9654.87580183453$1308751219$gmane$org@localhost>
2011-06-22 14:30 ` Sven Joachim [this message]
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=878vsu3pmd.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=631255@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=debian@aktendiener.de \
--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 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.