Control: reassign -1 linux-signed-amd64 Control: found -1 4.17.0-3 Just a note, bugs.debian.org is the package for reporting issues with the bug tracking system itself, not general issues in packages (or the kernel.)
I've reassigned this bug for you. On Sat, 29 Dec 2018, Patrick Boettcher wrote: > I did an apt upgrade this morning, I'm running testing/unstable. This updated > my kernels to 4.17.0-3-amd64 and 4.19.0-1-amd64. I think the first since a few > months (6 or more, but less then one year). > * What exactly did you do (or not do) that was effective (or > ineffective)? > > sudo apt update; sudo apt dist-upgrade > > * What was the outcome of this action? > > After rebooting to the new kernel booting stuck with some messages about mdadm > looking for a RAID I don't have. > > Ultimately the initramfs-shell came up and I found out that there are no > block- > devices loaded. /dev/sda* and /dev/nvme* did not exists. > > I manually modprobe'd nvme. Followed by CTRL-D and the boot continued. > > > > -- System Information: > Debian Release: buster/sid > APT prefers unstable > APT policy: (602, 'unstable'), (601, 'testing'), (600, 'stable'), (598, > 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.17.0-3-amd64 (SMP w/12 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_ALL > to default locale: No such file or directory > UTF-8), LANGUAGE=en_US:en (charmap=locale: Cannot set LC_ALL to default > locale: No such file or directory > UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > -- Don Armstrong https://www.donarmstrong.com When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. -- Edmund Burke "Thoughts on the Cause of Present Discontents"
