I think I see what may have happened. Commit 288fa3e0 was applied to v3.10-rc1 before commit ec5f0615 :
git describe --contains 288fa3e022eb85fa151e0f9bcd15caeb81679af6 <jsalisbury> v3.10-rc1~194^2~38 git describe --contains ec5f061564238892005257c83565a0b58ec79295 <jsalisbury> v3.10-rc1~66^2~545
Commit 288fa3e fixed the Hyper-V bug, but then commit ec5f061 introduced a new, but similar bug. They were both introduced in v3.10-rc1, so we never saw the Hyper-V fix before this new bug came along.
@Milan Dadok, I built a Saucy test kernel with commit ec5f061 reverted. The kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1200243/ec5f061-reverted/
Can you test this kernel and post back if it resolves this bug? You may have to install both the linux-image and linux-image-extra .deb packages.
I think I see what may have happened. Commit 288fa3e0 was applied to v3.10-rc1 before commit ec5f0615 :
git describe --contains 288fa3e022eb85f a151e0f9bcd15ca eb81679af6 2005257c83565a0 b58ec79295
<jsalisbury> v3.10-rc1~194^2~38
git describe --contains ec5f06156423889
<jsalisbury> v3.10-rc1~66^2~545
Commit 288fa3e fixed the Hyper-V bug, but then commit ec5f061 introduced a new, but similar bug. They were both introduced in v3.10-rc1, so we never saw the Hyper-V fix before this new bug came along.
@Milan Dadok, I built a Saucy test kernel with commit ec5f061 reverted. The kernel can be downloaded from: kernel. ubuntu. com/~jsalisbury /lp1200243/ ec5f061- reverted/
http://
Can you test this kernel and post back if it resolves this bug? You may have to install both the linux-image and linux-image-extra .deb packages.