I need to look at the commit history of the debian kernel source tree to
see which patches from the linux mainline kernel are applied to the debian
tree. Where can i get that?
Thanks.
Package: src:linux
Version: 5.3.2-1~exp1
Severity: important
I can't figure out how to sign my kernel modules once I installed my MOK,
the doc in https://wiki.debian.org/SecureBoot#MOK_-_Machine_Owner_Key didn't
really help me out.
└[cochabamba] mokutil --test-key mok/MOK.cer
Processing commands for cont...@bugs.debian.org:
> reassign 941239 src:linux 4.19.67-2
Bug #941239 [linux-image-4.19.0-6-686] systemd 241-7, poweroff+reboot
stalls/freezes after "Reached target shutdown"
Bug reassigned from package 'linux-image-4.19.0-6-686' to 'src:linux'.
Ignoring request to al
+1
QUIRK: In order to reliably disable NFS 4.2 on *server* side; in
/etc/systemd/system/nfs-server.service.d/nfs-version.conf
# Disable NFS 4.2
# FIX: umask ignored (files created world-writable) when using NFS 4.2 (on top
of ZFS)
# BUG: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934160
I have also observed this, and it is rather critical because I depend heavily
on VirtualBox which now won't work because it can't build the necessary kernel
modules ... and try as I might, I cannot get my system to downgrade to the
previous 4.19.0 kernel.
I have managed to downgrade all the way
Control: reassign -1 linux-image-4.19.0-6-686
Am 05.10.19 um 12:26 schrieb Rado Q:
> =- Michael Biebl wrote on Fri 4.Oct'19 at 14:53:45 +0200 -=
>
>> Could you also provide a log file from a failed/hanging shutdown?
>
> I've attached a log per:
> - failed 'poweroff' (happens everytime)
> - succ
Processing control commands:
> reassign -1 linux-image-4.19.0-6-686
Bug #941239 [systemd] systemd 241-7, poweroff+reboot stalls/freezes after
"Reached target shutdown"
Bug reassigned from package 'systemd' to 'linux-image-4.19.0-6-686'.
No longer marked as found in versions systemd/241-7~deb10u1.
7 matches
Mail list logo