Package: initramfs-tools-core
Version: 0.142
Severity: normal
Tags: patch
With a root filesystem on ZFS then mkinitramfs builds an initrd that
lacks fsck.zfs:
testaroli# mkinitramfs -o /boot/initrd.img-$(uname -r)
W: Couldn't identify type of root file system for fsck hook
Hi All,
Bernhard informed me that you might no longer want me to
do the kernel building, due to messages on the bug's mailing
list that didn't get sent to me.
Please advise; ideally "please test deb at " :-)
Regards,
Alexis
> I will try to do this, but owing to my schedule, it will
> be only Tuesday before I can try.
everything slipped. Building ten kernel packages today. Further
feedback some time over the weekend.
Alexis
Hi All,
> Would you be able to start own kenel builds, confirming it does not
> happen with 5.10.140 upstream but with 5.10.149, and isolate the
> breaking change?
>
> (Are you able to boot the kernel from bullseye-backports?)
I will try to do this, but owing to my schedule, it will
be only
the kernel command line is:
sugo$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.10.0-18-amd64 root=/dev/mapper/vg0-root ro ipv6.disable=1
amdgpu.dc=0 swapaccount=1
sugo$
where obviously 18 is 19 when booting the bad kernel.
Package: src:linux
Version: 5.10.149-2
Severity: serious
Justification: 1022025, 1022051, 1022062, 1022070, 1022097, 1022147 marked
serious so this marked serious too
Dear Maintainer,
Following other reports of post-grub kernel hangs on systems with
amdgpu, I waited for new release of
Package: linux-doc-2.6.24
Version: 2.6.24-6
Severity: normal
When I install the packages:
linux-image-2.6-686
linux-headers-2.6-686
then the right thing happens; these depend on the latest 2.6 kernels and
headers.
But when I install:
linux-doc-2.6
the corresponding
7 matches
Mail list logo
