Seems to be an upstream bug introduced somewhere between v3.6 and v3.7-rc3:
linux-image-3.5.0-18-generic_3.5.0-18.29_amd64.deb works
linux-image-3.5.7-030507-generic_3.5.7-030507.201210130556_amd64.deb works
linux-image-3.6.0-030600-generic_3.6.0-030600.201209302035_amd64.deb works
linux-image-3.7.0-2-generic_3.7.0-2.8_amd64.deb FAILS
linux-image-3.7.0-030700rc3-generic_3.7.0-030700rc3.201210310756_amd64.deb FAILS
linux-image-3.7.0-030700rc5-generic_3.7.0-030700rc5.201211110835_amd64.deb FAILS
Seems to be an upstream bug introduced somewhere between v3.6 and v3.7-rc3:
linux-image- 3.5.0-18- generic_ 3.5.0-18. 29_amd64. deb works 3.5.7-030507- generic_ 3.5.7-030507. 201210130556_ amd64.deb works 3.6.0-030600- generic_ 3.6.0-030600. 201209302035_ amd64.deb works 3.7.0-2- generic_ 3.7.0-2. 8_amd64. deb FAILS 3.7.0-030700rc3 -generic_ 3.7.0-030700rc3 .201210310756_ amd64.deb FAILS 3.7.0-030700rc5 -generic_ 3.7.0-030700rc5 .201211110835_ amd64.deb FAILS
linux-image-
linux-image-
linux-image-
linux-image-
linux-image-