Your message dated Mon, 20 May 2024 12:14:45 +0200 with message-id <[email protected]> and subject line Re: Bug#1071467: linux-image-6.6.13+bpo-amd64: installation botched, tiny and corrupt deb file has caused the Debian Bug report #1071467, regarding linux-image-6.6.13+bpo-amd64: installation botched, tiny and corrupt deb file to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1071467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071467 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: src:linux Version: 6.6.13-1~bpo12+1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: [email protected] To install linux-image-6.6.13+bpo-amd64, this command was executed: $ apt -t bookworm-backports install linux-image-amd64 I have a transcript of the session but it’s probably not worth posting. It’s in the binary format produced by the “script” command. The deb file is only 1,480 bytes, which is obviously a non-starter. The final output was this: Download is performed unsandboxed as root as file '/root/linux-image-amd64_6.6.13-1~bpo12+1_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-21-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.6.13+bpo-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod 30+20221128-1 ii linux-base 4.9 Versions of packages linux-image-6.6.13+bpo-amd64 recommends: ii apparmor 3.0.8-3 ii firmware-linux-free 20200122-1 Versions of packages linux-image-6.6.13+bpo-amd64 suggests: pn debian-kernel-handbook <none> ii grub-pc 2.06-13+deb12u1 pn linux-doc-6.6 <none> Versions of packages linux-image-6.6.13+bpo-amd64 is related to: pn firmware-amd-graphics <none> pn firmware-atheros <none> pn firmware-bnx2 <none> pn firmware-bnx2x <none> pn firmware-brcm80211 <none> pn firmware-cavium <none> pn firmware-intel-sound <none> pn firmware-intelwimax <none> pn firmware-ipw2x00 <none> pn firmware-ivtv <none> ii firmware-iwlwifi 20230210-5 pn firmware-libertas <none> pn firmware-linux-nonfree <none> pn firmware-misc-nonfree <none> pn firmware-myricom <none> pn firmware-netxen <none> pn firmware-qlogic <none> pn firmware-realtek <none> pn firmware-samsung <none> pn firmware-siano <none> pn firmware-ti-connectivity <none> pn xen-hypervisor <none> -- no debconf information
--- End Message ---
--- Begin Message ---On Mon, May 20, 2024 at 11:01:06AM +0200, Manny wrote: > make -j2 KERNELRELEASE=6.6.13+bpo-amd64 -C > /lib/modules/6.6.13+bpo-amd64/build M=/var/lib/dkms/tp_smapi/0.43/build > HDAPS=1...(bad exit status: 2) > Error! Bad return status for module build on kernel: 6.6.13+bpo-amd64 (x86_64) > Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information. Here is your error. > Apparently the Thinkpad battery modules break in the latest backports > kernel. You might recall from this bug: Yes, you need to talk to the authors of this module. The kernel module API is not stable, so no guarantees are given that something builds on other versions. > that the Thinkpad modules are suspect of causing freezes in kernel > versions 6.1.x. I am currently running one of those versions with the > two modules removed, as an experiment per your suggestion (so far, no > freezing with the modules removed but it’s a bit early to conclude > anything from that). The above attempt to install the latest backports > kernel (performed last week) was another effort to diagnose the same > problem.. to test whether the newest kernel also freezes. So we are back at tp_smapi being the culprit, not the kernel. I'm closing this bug here, as all points to tp_smapi as the culprit, both for the freeze and the installation problems. Bastian -- There are some things worth dying for. -- Kirk, "Errand of Mercy", stardate 3201.7
--- End Message ---
