Comment 17 for bug 1489622

I'd be happy to, but first I want to reproduce it in a kernel I built myself instead of one that I got from Ubuntu. I am not able to do that.

The issue does not reproduce for me when I use linux 3.18-rc1 built myself, using the same kernel configuration as v3.18-rc1-utopic.

I installed linux-image-3.18.0-031800rc1-generic_3.18.0-031800rc1.201410192135_amd64.deb and copied its configuration from /boot and then used it to build my own kernel, and the resulting kernel that I built does not have this issue. What I did to build my kernel:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
cd linux-stable
git remote add ubuntu-trusty git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git
git checkout ubuntu-trusty/master

cp -a /usr/share/kernel-package ../ubuntu-package
cp debian/control-scripts/{postinst,postrm,preinst,prerm} ../ubuntu-package/pkg/image/
cp debian/control-scripts/headers-postinst ../ubuntu-package/pkg/headers/

git checkout v3.18-rc1

sudo make-kpkg clean
sudo make-kpkg --initrd --overlay-dir=../ubuntu-package kernel_image kernel_headers

sudo dpkg -i ../*deb

I rebooted, verified it was my kernel with 'uname -a' and attempted to reproduce the issue, but it did not reproduce.

What would be differnet between the way I built the kernel and the way Ubuntu built linux-image-3.18.0-031800rc1-generic_3.18.0-031800rc1.201410192135_amd64.deb ?