Comment 4 for bug 925309

 today i caused this bug to come out when i tried moving one of the big image files into my home directory. same 100% cpu, same unkillable.

i downloaded and installed the latest mainline kernel ( 3.3.0-030300rc2-generic-pae), booted up into it with only one issue, my wireless network driver is not loaded, so i have no network connectivity.

after booting into the newly installed mainline kernel, i tried all of the failing tasks to try to reproduce the unkillable process that uses 100% of the CPU.

i started with the mv command, moving the 5Gb disk image file to my home directory. watching my mv command in top, the cpu percent in not 100%, but a more reasonable 30-60%, and data continues to be added to the destination directory. after a minute or so, the file finished copying, all 5Gb of it.

creating a disk image using qemu-img also works as expected. creating a 5Gb raw disk image file works. i am also able to stop the qemu-img process at any time in the terminal where i ran it from using Ctl-C.

creating a disk image using VirtualBox also works as expected. the VBoxSVC process spends a lot of time using 100% cpu, but the image file continues to have bytes allocated to it. the process creating an 8Gb disk image file completes. pressing the cancel icon on the progress dialog changes status message to "Canceling...", just like when the VBoxSVC process was unkillable; however, this time the process continues to allocate disk pace to the image file and, once all eight gigabytes is allocated, exits as expected.

i think that this bug does not exist in the latest mainline kernel