Comment 10 for bug 986654

In my original posting, I did not mention that I had also tested a bunnch of mainline kernels, and always had this issue.
I tested 3.4RC4 this morning, and it has the issue of the bug posting. The edited kern.log file is attached.

Even if the issue did not appear with kernel 3.4RC4, I would be reluctant to call this issue solved. Why? Two reasons: First, the execution of what I am using as a test for this, "sudo update-apt-xapian-index --force", is very different for kernel 3.3.2 and 3.4RC4 taking only an average of 23 minutes instead of an average of 45 minutes to an hour previously; Second, since this seems to be some race condition how do we know that some subtle change is merely hiding it, with the underlying root issue still there? (It could be argued that the root underlying issue was always there, and it was a subtle change that revealed it to begin with. O.K. but I doubt it, because I have been running Ubuntu server edition on this computer for several years, and have never seen this before). It is for these reasons that I was trying to narrow down and find the actual code change that introduced the issue. Then the plan would be to test with and without the change to verify (i.e. a single variable test).

For reference:
doug@test-smy:~/temp-kernel$ uname -a
Linux test-smy 3.4.0-030400rc4-generic-pae #201204230908 SMP Mon Apr 23 13:23:25 UTC 2012 i686 i686 i386 GNU/Linux
doug@test-smy:~/temp-kernel$ cat /proc/version
Linux version 3.4.0-030400rc4-generic-pae (apw@gomeisa) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1) ) #201204230908 SMP Mon Apr 23 13:23:25 UTC 2012