Kernel panic when resize2fs called (LVM and RAID)

Linux 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC
2007 i686 GNU/Linux

Gnu C 4.1.2
Gnu make 3.81
binutils 2.17.50
util-linux 2.12r
mount 2.12r
module-init-tools 3.3-pre2
e2fsprogs 1.40-WIP
jfsutils 1.1.11
reiserfsprogs 3.6.19
reiser4progs 1.0.5
xfsprogs 2.8.18
PPP 2.4.4
Linux C Library > libc.2.5
Dynamic linker (ldd) 2.5
Procps 3.2.7
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.97
udev 108
wireless-tools 28
Modules Loaded xt_multiport iptable_filter ip_tables x_tables
binfmt_misc af_packet rfcomm l2cap bluetooth ppdev speedstep_lib
cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_ondemand
freq_table cpufreq_conservative tc1100_wmi pcc_acpi dev_acpi sony_acpi
video sbs i2c_ec dock button battery container ac asus_acpi backlight
eeprom lm85 hwmon_vid i2c_i801 psmouse lp snd_intel8x0 snd_ac97_codec
ac97_bus snd_pcm_oss snd_pcm snd_mixer_oss snd_seq_dummy snd_seq_oss
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer
snd_seq_device snd soundcore i2c_core parport_pc parport snd_page_alloc
intel_agp agpgart i82875p_edac edac_mc pcspkr shpchp pci_hotplug iTCO_wdt
iTCO_vendor_support evdev tsdev ipv6 ext3 jbd mbcache sr_mod cdrom ata_piix
sg sd_mod ata_generic sata_sil pata_sil680 libata scsi_mod ehci_hcd
ohci1394 ieee1394 uhci_hcd usbcore floppy e1000 generic raid456 xor raid1
md_mod thermal processor fan dm_mod fbcon tileblit font bitblit softcursor
vesafb capability commoncap

By definition a kernel panic is a linux kernel problem and not a userspace bug. There should be nothing that a user program can do that should be able to trigger a kernel panic, without a kernel bug. In this case, the bug isn't even in any ext3 filesystem code, but rather a kernel soft lockup while doing some block device I/O. 2.6.20 is a rather old kernel, so it would be interesting to see if the problem can be reproduced on a more modern kernel.

Tried again today after Theodore's comment.

Worked fine on 2.6.24-21-generic.

Thanks for looking into this.

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.