Kernel Panic on 'Safety Remove' of WD My Passport Essentials 500GB HDD

[Kieran Grant]

*** UPDATE *** - Confirmed not my netbook.

When I 'Safety Remove' my Western Digital My Passport Essentials 500GB Hard drive I get a kernel panic (60% first time, if I reinsert and repeat i get about 95% second and always panicked by the third retry)

Whilst it occurs on safety remove, from what I can make out from kernel panic text (it won't make a crash dump, even with kdump, need help with getting this to work), it has something to do with a kernel thread failing to flush, and I see something about changing the vsync and hsync (which also appears in dmesg but succeeds).

I can unmount the device and use the 'eject' command in terminal and take it out no worries, but If i 'safety remove' it panics.

I have tested this on a Kogan Agora Pro 12" Running Ubuntu 11.10 x86_64 and I Intel Core 2 Duo Machine running Ubuntu 11.10 on Live USB. Test on a Ubuntu 10.04 machine shows no sign of bug, it doesn't not panic.

It is not my netbook as the bug occurs identically on other computers with Ubuntu 11.10. So far I have not been able to reproduce on Ubuntu 10.04, have not tested on Ubuntu 11.04 (yet), nor on 32-bit only versions.

[Kieran Grant (kieran-grant)]

I wasn't sure what log files were included with "ubuntu-bug linux" so I added some in my compressed archive that are repeats :P sorry about that. If you want me to do some tests that's fine, I can reproduce it easily, Disk Utilities says my external drive is fine (Smart Status all crystal clear).

[Kieran Grant (kieran-grant)]

I have completed a quick batch test on different machines with different versions of Ubuntu:

Ubuntu 11.10 - Always panics by third attempt (Most of the time on the first)
Ubuntu 11.04 - Never panics, system normal
Ubuntu 10.04 - Never panics, system normal

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.