Bug#951543: Please enable SECO HDMI CEC driver
Package: src:linux Severity: wis hlist Tags: patch Dear Maintainer, Could you please enable CONFIG_VIDEO_SECO_CEC ? That device is found on x86 board from UDOO, it would be very cool to not have to rebuild the kernel by hand :-) Thanks. Sébastien --- a/config-5.4.13 +++ b/config-5.4.13 @@ -4797,6 +4797,7 @@ # CONFIG_REGULATOR_TPS65132 is not set # CONFIG_REGULATOR_TPS6524X is not set CONFIG_CEC_CORE=y +CONFIG_CEC_NOTIFIER=y CONFIG_RC_CORE=m CONFIG_RC_MAP=m CONFIG_LIRC=y @@ -5122,7 +5123,9 @@ # CONFIG_VIDEO_VIM2M is not set # CONFIG_VIDEO_VICODEC is not set # CONFIG_DVB_PLATFORM_DRIVERS is not set -# CONFIG_CEC_PLATFORM_DRIVERS is not set +CONFIG_CEC_PLATFORM_DRIVERS=y +CONFIG_VIDEO_SECO_CEC=m +CONFIG_VIDEO_SECO_RC=y # CONFIG_SDR_PLATFORM_DRIVERS is not set #
Bug#951517: installing this kernel does not cause the ndivida/bumblebee driver to be compiled
Package: src:linux Version: 5.4.8-1~bpo10+1 Severity: normal Hi, usually, installing a kernel results in any DKMS modules being recompiled for this kernel, but for the nvidia driver, this does not seem to happen. As a result, bumblebeed does not start, effectively disabling the nvidia card. Cheers, Toni -- Package-specific info: ** Version: Linux version 5.4.0-0.bpo.2-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 5.4.8-1~bpo10+1 (2020-01-07) ** Command line: BOOT_IMAGE=/vmlinuz-5.4.0-0.bpo.2-amd64 root=/dev/mapper/ev0-root ro crashkernel=384M-:128M ** Not tainted ** Kernel log: [ 2758.632378] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.632378] mce: CPU8: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.632379] mce: CPU11: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.632380] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.632381] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.632382] mce: CPU9: Package temperature above threshold, cpu clock throttled (total events = 3554) [ 2758.633344] mce: CPU0: Package temperature/speed normal [ 2758.633345] mce: CPU4: Core temperature/speed normal [ 2758.633346] mce: CPU11: Package temperature/speed normal [ 2758.633347] mce: CPU5: Package temperature/speed normal [ 2758.633347] mce: CPU4: Package temperature/speed normal [ 2758.633348] mce: CPU3: Package temperature/speed normal [ 2758.633348] mce: CPU9: Package temperature/speed normal [ 2758.633349] mce: CPU6: Package temperature/speed normal [ 2758.633349] mce: CPU10: Core temperature/speed normal [ 2758.633350] mce: CPU10: Package temperature/speed normal [ 2758.633382] mce: CPU7: Package temperature/speed normal [ 2758.633383] mce: CPU8: Package temperature/speed normal [ 2758.633383] mce: CPU1: Package temperature/speed normal [ 2758.633384] mce: CPU2: Package temperature/speed normal [ 3120.602728] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602728] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 3615) [ 3120.602768] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602769] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602770] mce: CPU8: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602771] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602772] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602773] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602774] mce: CPU9: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602775] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602776] mce: CPU11: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.602778] mce: CPU10: Package temperature above threshold, cpu clock throttled (total events = 3621) [ 3120.603737] mce: CPU6: Package temperature/speed normal [ 3120.603737] mce: CPU0: Package temperature/speed normal [ 3120.603782] mce: CPU3: Package temperature/speed normal [ 3120.603783] mce: CPU1: Package temperature/speed normal [ 3120.603784] mce: CPU9: Package temperature/speed normal [ 3120.603785] mce: CPU2: Package temperature/speed normal [ 3120.603785] mce: CPU7: Package temperature/speed normal [ 3120.603786] mce: CPU8: Package temperature/speed normal [ 3120.603787] mce: CPU10: Package temperature/speed normal [ 3120.603787] mce: CPU4: Package temperature/speed normal [ 3120.603788] mce: CPU5: Package temperature/speed normal [ 3120.603789] mce: CPU11: Package temperature/speed normal [ 4810.196840] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 2594) [ 4810.196841] mce: CPU8: Core temperature above threshold, cpu clock throttled (total events = 2594) [ 4810.196841] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196842] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196843] mce: CPU8: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196844] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196844] mce: CPU9: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196845] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 3622) [ 4810.196881] mce: CPU6: Package temperature above threshold, cpu
Processed: reassign 951482 to src:linux, severity of 951482 is wishlist
Processing commands for cont...@bugs.debian.org: > reassign 951482 src:linux 5.4.19-1 Bug #951482 [linux-image-amd64] CX2072X SoC audio modules Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/5.4.19+1. Ignoring request to alter fixed versions of bug #951482 to the same values previously set Bug #951482 [src:linux] CX2072X SoC audio modules Marked as found in versions linux/5.4.19-1. > severity 951482 wishlist Bug #951482 [src:linux] CX2072X SoC audio modules Severity set to 'wishlist' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 951482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951495: linux-image-4.19.0-8-armmp: unable to boot an odroid xu4, cannot load rootfs from sdcard by UUID
Package: src:linux Version: 4.19.98-1 Severity: normal Dear Maintainer, I encountered a problem when upgrading linux-image from 4.0.19-6 to 4.0.19-8 on two odroid xu4 servers. They do not boot anymore when using the vmlinuz-4.19.0-8-armmp image installed on /boot (but they still boot if I use the older vmlinuz-4.19.0-6-armmp). Using a serial console to check the boot process, I get these upon failure: Starting version 241 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. [ 10.468381] dma-pl330 388.adma: Loaded driver for PL330 DMAC-241330 [ 10.473603] dma-pl330 388.adma: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6 [ 10.503820] dma-pl330 388.adma: PM domain MAU will not be powered off Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. ... lots of similar lines removed ... Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=e139ce78-9841-40fe-8823-96a304a09859 does not exist. Dropping to a shell! BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) So I ran the sugested commands: - cat /proc/modules returned absolutely nothing - ls /dev liste reported the following list, where there are no "disk" directory, hence no /dev/disk/by-uuid: apm_biosnetwork_throughput tty40 charnulltty41 console porttty42 cpu_dma_latency psaux tty43 fd ptmxtty44 fullpts tty45 gpiochip0 random tty46 gpiochip1 snapshottty47 gpiochip10 stderr tty48 gpiochip11 stdin tty49 gpiochip12 stdout tty5 gpiochip13 tty tty50 gpiochip14 tty0tty51 gpiochip15 tty1tty52 gpiochip16 tty10 tty53 gpiochip17 tty11 tty54 gpiochip18 tty12 tty55 gpiochip19 tty13 tty56 gpiochip2 tty14 tty57 gpiochip20 tty15 tty58 gpiochip21 tty16 tty59 gpiochip22 tty17 tty6 gpiochip23 tty18 tty60 gpiochip24 tty19 tty61 gpiochip25 tty2tty62 gpiochip26 tty20 tty63 gpiochip27 tty21 tty7 gpiochip28 tty22 tty8 gpiochip29 tty23 tty9 gpiochip3 tty24 ttyS0 gpiochip30 tty25 ttyS1 gpiochip31 tty26 ttyS2 gpiochip32 tty27 ttyS3 gpiochip33 tty28 ttySAC0 gpiochip34 tty29 ttySAC1 gpiochip35 tty3ttySAC2 gpiochip4 tty30 ttySAC3 gpiochip5 tty31 urandom gpiochip6 tty32 vcs gpiochip7 tty33 vcs1 gpiochip8 tty34 vcsa gpiochip9 tty35 vcsa1 input tty36 vcsu kmsgtty37 vcsu1 mem tty38 vga_arbiter memory_bandwidthtty39 zero network_latency tty4 - cat /proc/cmdline output was: console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes net.ifnames=0 smsc95xx.macaddr=00:1e:06:61:7a:39 This commandline comes from the uboot and is the one I epxected, and the one that works with previous kernel image. This command line looks for the rootfs using its UUID. The previous kernel image found the rootfs directly, but the new kernel image does not find it anymore. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information Hardware: SAMSUNG EXYNOS (Flattened Device Tree) Revision: Device Tree model: Hardkernel Odroid XU4 ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.19.0-6-armmp
Processed: Re: linux-source-5.4: Failed to build linux-source-5.4 in efi_set_secure_boot
Processing control commands: > tags -1 patch Bug #945604 [linux-source-5.4] linux-source-5.4: Failed to build linux-source-5.4 in efi_set_secure_boot Added tag(s) patch. -- 945604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945604: linux-source-5.4: Failed to build linux-source-5.4 in efi_set_secure_boot
Control: tags -1 patch
The root cause is that lock_kernel_down() is unconditionally called
in efi_set_secure_boot, even if the kernel is compiled without
lockdown support (i.e. SECURITY_LOCKDOWN_LSM=n).
This build failure shouldn't affect the Debian official kernel
packages because the Kconfig default value is overridden
to enable lockdown support. However, if you use the Kconfig
defaults (e.g. when building via the linux-source package)
then you may encounter this error.
There is a flag LOCK_DOWN_IN_EFI_SECURE_BOOT (depending
on SECURITY_LOCKDOWN_LSM) that is currently ignored. It seems
like it was originally supposed to gate the lock_kernel_down call().
I've attached a patch to honor this flag again, which should fix this issue.
From de06de54508caf6bb1d3f25d4ef652d1360a43e0 Mon Sep 17 00:00:00 2001
From: Christian Barcenas
Date: Mon, 17 Feb 2020 02:50:58 -0800
Subject: [PATCH] lockdown: honor LOCK_DOWN_IN_EFI_SECURE_BOOT
Previously LOCK_DOWN_IN_EFI_SECURE_BOOT was ignored;
lock_kernel_down() was always called during EFI Secure Boot.
Additionally this resolves a link-time error that occurs when
the kernel is built with EFI=y and SECURITY_LOCKDOWN_LSM=n.
Closes: #945604
---
...efi-lock-down-the-kernel-if-booted-in-secure-boot-mo.patch | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/debian/patches/features/all/lockdown/efi-lock-down-the-kernel-if-booted-in-secure-boot-mo.patch b/debian/patches/features/all/lockdown/efi-lock-down-the-kernel-if-booted-in-secure-boot-mo.patch
index e20fd562963c..7d7eada166d0 100644
--- a/debian/patches/features/all/lockdown/efi-lock-down-the-kernel-if-booted-in-secure-boot-mo.patch
+++ b/debian/patches/features/all/lockdown/efi-lock-down-the-kernel-if-booted-in-secure-boot-mo.patch
@@ -50,12 +50,14 @@ Signed-off-by: Ben Hutchings
/*
* Decide what to do when UEFI secure boot mode is enabled.
-@@ -28,6 +29,8 @@ void __init efi_set_secure_boot(enum efi
+@@ -28,6 +29,10 @@ void __init efi_set_secure_boot(enum efi
break;
case efi_secureboot_mode_enabled:
set_bit(EFI_SECURE_BOOT, );
++#ifdef CONFIG_LOCK_DOWN_IN_EFI_SECURE_BOOT
+ lock_kernel_down("EFI Secure Boot",
+ LOCKDOWN_CONFIDENTIALITY_MAX);
++#endif
pr_info("Secure boot enabled\n");
break;
default:
--
2.25.0
Bug#951482: CX2072X SoC audio modules
Package: linux-image-amd64 Version: 5.4.19-1 Please enable modules for CX2072X audio [1] (included in mainline from 5.3 [2] ) CONFIG_SND_SOC_INTEL_BYT_CHT_CX2072X_MACH CONFIG_SND_SOC_CX2072X [1] https://bugzilla.kernel.org/show_bug.cgi?id=115531 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a497a4363706b3eb208c64e66e5b485bb3b186ac Thanks Peter
