Could not boot after Debian 10 upgrade

[schnappi]

See attached image. Got system to boot by editing kernel options but in doing so disabled keyboard access and can only access via SSH. Issue appears to be the kernel.

[sunrat]

So what happened when you booted with the "noapic" kernel option as suggested in the messages on screen?

[schnappi]

Forget the exact option used (noapic did not work), but the machine will boot. The keyboard is non-responsive though, making SSH the only login option.

Booting to an old kernel allows use of keyboard.

[Head_on_a_Stick]

Did you follow the upgrade guide in the official release notes?

Does this also happen if you try to load a live version of Debian 10?

Did you boot with apic=debug and submit a bug report?

[schnappi]

System will not boot with a liveboot version of gparted based on Debian. It is absolutely a kernel issue. Who should the bug report go to?

[Head_on_a_Stick]

System will not boot with a liveboot version of gparted based on Debian.

Please try the Debian ISO image as well, although DistroWatch says that gparted live uses the same kernel version they may not be correct.

Who should the bug report go to?

https://www.debian.org/Bugs/Reporting

[schnappi]

Is booting with apic=debug going to create a bug report somewhere, if so where will it be to submit? If it is just going to create a bug report I want to do it and submit the bug. However, this is a remote system. If the kernel cannot boot again due to changing a kernel option it will be a huge headache to get booting again just because added apic=debug to create a bug report.

Will rebooting with apic=debug have any other effect than creating a text file report?