On i386 images, the bug is not occurring since 3.9.0-5. i.e. the issue does not occur with kernel version 3.9.0-5 and 3.9.0-6 kernels on i386 images.
On amd64 images, although with 3.9.0-5 there were a couple of instances when the issue did not occur during smoke tests, the consecutive runs show that the bug is in fact still present even with 3.9.0-5 and 3.9.0-6. Sorry for my hasty claim on comment #15.
So basically on i386 images the bug is not present from 3.9.0-5 onwards but on amd64 images it continues to exist even with kernels 3.9.0-5 and 3.9.0-6
With mainline v3.10.0-031000rc6-generic the bug is still present on amd64 images. (but displays different message in dmesg as given below)
unregister_netdevice: waiting for h1-eth0 to become free. Usage count = 1
unregister_netdevice: waiting for h2-eth0 to become free. Usage count = 1
On i386 images, the bug is not occurring since 3.9.0-5. i.e. the issue does not occur with kernel version 3.9.0-5 and 3.9.0-6 kernels on i386 images.
On amd64 images, although with 3.9.0-5 there were a couple of instances when the issue did not occur during smoke tests, the consecutive runs show that the bug is in fact still present even with 3.9.0-5 and 3.9.0-6. Sorry for my hasty claim on comment #15.
So basically on i386 images the bug is not present from 3.9.0-5 onwards but on amd64 images it continues to exist even with kernels 3.9.0-5 and 3.9.0-6
With mainline v3.10.0- 031000rc6- generic the bug is still present on amd64 images. (but displays different message in dmesg as given below)
unregister_ netdevice: waiting for h1-eth0 to become free. Usage count = 1 netdevice: waiting for h2-eth0 to become free. Usage count = 1
unregister_