From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Friedrich Berendsen <afberendsen@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: kernel BUG at fs/ext4/extents.c:2738!
Date: Fri, 20 Feb 2009 09:42:20 -0600 [thread overview]
Message-ID: <499ECF5C.7020509@redhat.com> (raw)
In-Reply-To: <1235115642.22702.2.camel@localhost.localdomain>
Andreas Friedrich Berendsen wrote:
> I have no idea what information you guys will need. Let me know and I'll
> to gather it.
>
> Feb 20 19:26:11 storage kernel: ------------[ cut here ]------------
> Feb 20 19:26:11 storage kernel: kernel BUG at fs/ext4/extents.c:2738!
> Feb 20 19:26:11 storage kernel: invalid opcode: 0000 [#1] SMP
> Feb 20 19:26:11 storage kernel: last sysfs
> file: /sys/devices/pci0000:00/0000:00:04.0/host0/target0:0:0/0:0:0:0/block/sda/sda2/dev
> Feb 20 19:26:11 storage kernel: Dumping ftrace buffer:
> Feb 20 19:26:11 storage kernel: (ftrace buffer empty)
> Feb 20 19:26:11 storage kernel: CPU 0
> Feb 20 19:26:11 storage kernel: Modules linked in: vboxnetflt vboxdrv
> ext2 ext4 jbd2 crc16 fuse ipt_MASQUERADE iptable_nat nf_nat bridge stp
> nfsd lockd nfs_acl auth_rpcgss exportfs sunrpc bonding ipv6 dm_multipath
> raid456 async_xor async_memcpy async_tx xor kvm_amd kvm uinput usblp
> snd_hda_intel snd_seq_dummy cfi_cmdset_0002 jedec_probe snd_seq_oss
> snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss forcedeth
> snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_hwdep joydev sata_nv
> usb_storage cfi_probe gen_probe cfi_util serio_raw nvidia(P) snd
> firewire_ohci pcspkr k8temp hwmon ck804xrom soundcore firewire_core
> crc_itu_t mtd chipreg map_funcs i2c_nforce2 i2c_core ata_generic
> pata_acpi pata_amd [last unloaded: vboxdrv]
> Feb 20 19:26:11 storage kernel: Pid: 24313, comm: mv Tainted: P W
> 2.6.28.5.afb.fc10.3.x86_amd64 #1
since this isn't a stock fc10 kernel (?) i'm nto exactly sure what the
BUG was, I assume it was:
BUG_ON(path[depth].p_ext == NULL && depth != 0);
?
Can you reproduce this? Perhaps we can reproduce it from an e2image as
well if so, then it could be investigated ....
(Or, if you can reproduce it, perhaps try a .29 kernel first)
- Eric
next prev parent reply other threads:[~2009-02-20 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 7:40 kernel BUG at fs/ext4/extents.c:2738! Andreas Friedrich Berendsen
2009-02-20 15:42 ` Eric Sandeen [this message]
2009-02-20 18:48 ` Andreas Friedrich Berendsen
2009-02-20 19:30 ` Theodore Tso
2009-02-22 4:21 ` Andreas Friedrich Berendsen
2009-02-22 4:31 ` Theodore Tso
2009-02-22 5:22 ` Andreas Friedrich Berendsen
2009-02-22 20:00 ` Theodore Tso
2009-02-20 20:40 ` Eric Sandeen
2009-02-20 21:56 ` Andreas Friedrich Berendsen
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=499ECF5C.7020509@redhat.com \
--to=sandeen@redhat.com \
--cc=afberendsen@gmail.com \
--cc=linux-ext4@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).