That was unexpected. This would further indicate an Ubuntu specific SAUCE patch that is causing this, since Saucy has been rebased to upstream 3.11.1. Let me build one more Saucy test kernel from the Saucy master-next tree and see if the bug is fixed by only reverting b1a1442. If the bug still does exist, I'll have to pull off some of the SAUCE patches to see which one is causing this.
That was unexpected. This would further indicate an Ubuntu specific SAUCE patch that is causing this, since Saucy has been rebased to upstream 3.11.1. Let me build one more Saucy test kernel from the Saucy master-next tree and see if the bug is fixed by only reverting b1a1442. If the bug still does exist, I'll have to pull off some of the SAUCE patches to see which one is causing this.