From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1 Description of problem: Three times now I've had system freezes while (or just after) accessing an external firewire drive which is using dm_crypt and aes encryption (my backup disk). No log messages, can't ping machine, needs hard reset. It looks very similar to the problem reported on this thread: http://www.ussg.iu.edu/hypermail/linux/kernel/0503.0/1361.html One freeze happened when I suspended a dd operation to the encrypted partition, the other two happened when I exited the root shell where I had been running backup operations (with rsync). Interestingly the last time I was long finished with the backup, I had already unmounted the partition, removed the mapper entry and unplugged the disk maybe 30 minutes before but had left the root shell open in a Konsole. I'm not sure how helpful this is, but seems like between 2.6.10 and 2.6.11 there was a bug introduced in one of the dm_crypt, aes, and/or loop modules. Disclaimer: I am using the nvidia 1.0-7174 driver, so my kernel is tainted. But since other people are reporting similar problems with vanilla kernels, I don't think that is the issue. Version-Release number of selected component (if applicable): kernel-2.6.11-1.14_FC3 How reproducible: Sometimes Steps to Reproduce: Access an encrypted partition (dd/rsync) for some amount of time (both read and writes). Suspend the process or exit the shell. The kernel will sometimes hang. Additional info: loop 16713 2 aes_i586 37825 1 dm_crypt 11977 1 kernel-2.6.11-1.14_FC3
unless you can reproduce this without the binary module, this isn't worth investigating. Please reopen if you can repeat this without having loaded that module.
OK, I reproduced the problem (or at least a problem). I rebooted with generic nv driver, mounted my external drive, wrote about 60GB of data while trying to reproduce the hang by suspending/resuming the process, etc. with no luck. I had just given up, and was rebooting the machine when I get a kernel panic during shutdown: Kernel panic - not syncing: drivers/block/cfq-iosched.c:1065 spin_is_locked on uninitialized spinlock f763001c. (Not tainted) (That's all the information it printed on the screen). After that I had to power cycle.
Created attachment 113627 [details] List of loaded modules before kernel panic
that should be fixed in the work-in-progress kernel at http://people.redhat.com/davej/kernels/Fedora/FC3/
I really pounded it tonight using 2.6.11-1.19_FC3 and I could not reproduce the problem (even while running with the nvidia drivers :-). So looks like it was fixed. Thanks!
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you.
I've done a full system backup with two different external firewire disks with no problems running 2.6.12-1.1372_FC3 (still running fc3). So from my point of view this looks fixed. Thanks.