On 23/12/2018 13:43, Michael Biebl wrote:
Am 23.12.18 um 01:38 schrieb Ben Caradoc-Davies:
On 23/12/2018 13:11, Michael Biebl wrote:
Am 23.12.18 um 00:58 schrieb Ben Caradoc-Davies:
Failure was seen with linux-image-4.19.0-1-amd64 4.19.9-1. (Needed to
boot an 4.18.0-3-amd64 initramfs to get a working system.)
So 4.18 works and 4.19 fails?
No, 239-15 works with either kernel, and 240-1 fails, only tested with
the 4.19 kernel. Downgrading to 239-15 makes 4.19 bootable.
Then I don't understand your reply above, where you said you downgraded
to a 4.18.0-3-amd64 initramfs to get a working system.
Can you please elaborate what you meant with the above.
I have three installed kernels:
linux-image-4.18.0-2-amd64 -> 4.18.10-2+b1
linux-image-4.18.0-3-amd64 -> 4.18.20-2
linux-image-4.19.0-1-amd64 -> 4.19.9-1
I upgraded systemd to 240-1, which caused the initramfs for
linux-image-4.19.0-1-amd64 to be rebuilt to include systemd 240-1 and be
unbootable, so I booted linux-image-4.18.0-3-amd64 and made the bug
report. The system information gathered by reportbug is misleading
because it implies that problem was observed with 4.18.20-2, the running
kernel at the time of the report, which is not the kernel running when
the failure was observed. My remark was only to correct this misinformation.
Kind regards,
--
Ben Caradoc-Davies <b...@transient.nz>
Director
Transient Software Limited <https://transient.nz/>
New Zealand
