we have been trying to install 3.19 /4.2 kernels on our DELL machines after successful installation on boot the system simply doesn't boot to run level (see attachment where its stuck).Some machines of 4.2 kernel suceed to boot and subsequent reboots fail and drops with the same error (See attachment)
Isolated the issue to be out of grub since grub is able to be detected and boot from the mentioned identified device
Isolated the issue to be out of initramfs since if the modules are missing it will not pass to the next stage of boot process
Issue is seen in a boot stage before the kernel loads completely
Same issue is not seen in virtual environment (KVM) since the device drivers that is needed to boot is completely different compared to the baremetals (DELL/HP) suspect something really messy with the ata,ide drivers that goes missing but too early to comment
While booting to recovery mode it just drops to initramfs shell
Could be possibly related to #1308264 but i see none assigned to the BUG. Too many work arounds suggested in #1308264 as well in internet nothing helped
we have been trying to install 3.19 /4.2 kernels on our DELL machines after successful installation on boot the system simply doesn't boot to run level (see attachment where its stuck).Some machines of 4.2 kernel suceed to boot and subsequent reboots fail and drops with the same error (See attachment)
Isolated the issue to be out of grub since grub is able to be detected and boot from the mentioned identified device
Isolated the issue to be out of initramfs since if the modules are missing it will not pass to the next stage of boot process
Issue is seen in a boot stage before the kernel loads completely
Same issue is not seen in virtual environment (KVM) since the device drivers that is needed to boot is completely different compared to the baremetals (DELL/HP) suspect something really messy with the ata,ide drivers that goes missing but too early to comment
While booting to recovery mode it just drops to initramfs shell
Could be possibly related to #1308264 but i see none assigned to the BUG. Too many work arounds suggested in #1308264 as well in internet nothing helped