Hide Forgot
Created attachment 527043 [details] The backtrace as collected by ABRT Description of problem: I got this kernel crash and ABRT picked it up. I'm reporting it manually because on F14 the ABRT tries to send to "kerneloops" which apparently is dead. Version-Release number of selected component (if applicable): Fedora 14 Steps to Reproduce: 1. My external SATA enclosure gets accidentally powered off 2. I powered the enclosure back on 3. I remount the ext3 partition (umount /mnt/mountpoint && mount -a) 4. Partition becomes available, all is well 5. 10-15 seconds later ABRT pops up with kernel crash info How reproducible: Not sure, I don't want to break my file system by power cycling it unnecessarily Additional info: The accidental power off is obviously not the kernel's fault. However it should not crash; it should handle the disappearance of a device gracefully.
Also here is the kernel version I was running when it happened: $ uname -a Linux magrathea 2.6.35.14-96.fc14.x86_64 #1 SMP Thu Sep 1 11:59:56 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
There has been an enormous amount of change to the block layer, and upper layers that handle device removal since 2.6.35. It's not feasible to really backport it all, and f14 isn't going to get rebased at this point in its lifecycle, so all I can really suggest is to try and reproduce this on f15 (which will continue to see rebases) or f16-beta.
are you still seeing this on f15/f16 ?
I have not experienced this problem since installing F16. It probably makes sense to close this. Will reopen if I can reproduce it in F16 or higher. Cheers, Michael
Thanks for letting us know.