OK. So, I've bisected all of the mainline kernels between 2.6.32-02063211-generic (last known working release) and 2.6.32-0206322612-generic (first known broken release) and wouldn't you know it, the release in which this was broken was 2.6.32-02063212-generic, a.k.a. v2.6.32.12-lucid, a.k.a. linux-image-2.6.32-02063212-generic_2.6.32-02063212_i386.deb.
So, now that I've spent an afternoon going to all of this effort, is there any chance that somebody with knowledge of what changed between .11 and .12 can spend a few minutes to identify what went into .12 that would have caused this breakage?
OK. So, I've bisected all of the mainline kernels between 2.6.32- 02063211- generic (last known working release) and 2.6.32- 0206322612- generic (first known broken release) and wouldn't you know it, the release in which this was broken was 2.6.32- 02063212- generic, a.k.a. v2.6.32.12-lucid, a.k.a. linux-image- 2.6.32- 02063212- generic_ 2.6.32- 02063212_ i386.deb.
So, now that I've spent an afternoon going to all of this effort, is there any chance that somebody with knowledge of what changed between .11 and .12 can spend a few minutes to identify what went into .12 that would have caused this breakage?