The 15.10 kernel has been rebased to v4.0. Can you get the system to boot, then apply the latest updates and see if this bug still exists?
The 15.10 kernel has been rebased to v4.0. Can you get the system to boot, then apply the latest updates and see if this bug still exists?