Control: clone -1 -2 Control: notfound -2 linux/5.17.3-1 Control: retitle -2 linux-image-5.10.0-14-amd64: boot failure in VM after upgrading from -13 Control: tag -2 moreinfo On Friday, 3 June 2022 05:35:15 CEST Vicente Olivert Riera wrote: > Package: src:linux > Followup-For: Bug #1012210 This seems to be completely unrelated to that bug, so I've cloned it into a new bug. When responding please only respond to that new bug report/number. > I'm running Debian stable on a VM from an Apple MacBook Pro M1 14" 2021. > The software I'm using is UTM, which uses QEMU under the hood. > > Yesterday I did a system upgrade: > aptitude -y update && aptitude -y full-upgrade && apt -y autoremove General tip: don't do that! With 'update' it seems pointless With 'full-upgrade' you REALLY should review what is about to happen before agreeing to that as it could remove packages (important for you) I'd recommend reviewing the 'autoremove' result too before committing it > I noticed the kernel was upgraded to 5.10.0-14 so I rebooted the VM. After > that Debian was unable to boot. Choosing the previous kernel image > available from Grub (5.10.0-13) allowed Debian to boot normally. Bug 1012210 is about a boot failure on a (wide) variety of kernels, likely related to igpu. Your issue is a regression from -13 to -14. I assumed that you're running Debian Stable *in* a VM (on what host OS?). Please clarify whether that is correct or not. Also provide more info about YOUR boot failure and sent that to the NEW bug number that you should receive.
Attachment:
signature.asc
Description: This is a digitally signed message part.