Bug#914967: linux-image-4.18.0-3-amd64: errors "Failed to get unique processor _UID"
Hi Vincent, On Fri, Nov 15, 2019 at 01:43:07PM +0100, Vincent Lefevre wrote: > Control: found -1 4.19.67-2+deb10u2 > > On 2018-11-29 09:21:31 +0100, Vincent Lefevre wrote: > > I get the following errors at boot time: > > > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:06: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:07: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:08: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:09: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0a: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0b: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0c: Failed to get unique > > processor _UID (0xff) > > [...] > > Nov 29 09:04:21 cventin kernel: acpi LNXCPU:8f: Failed to get unique > > processor _UID (0xff) > > > > There were no such errors before linux-image-4.18.0-3-amd64. > > Still occurs in the Debian/stable kernel. Looking through some of opened bugs for src:linux noticed yours for #914967. This might actually not be a kernel issue, from [1]. [1] https://bugzilla.kernel.org/show_bug.cgi?id=203925 Regards, Salvatore
Bug#944350: [External] Bug#944350: systemd: screen remains off after waking up from suspend
Hi, I don't know if this is helpful but I recently debugged a similar issue on the Lenovo P1Gen2. There the problem is only with the integrated graphics and an OLED screen - we tracked it down to an issue in the i915 driver where it wasn't giving enough time for eDP link training. It turned out this was due to the driver using the wrong clocks after a suspend and resume . Intel recently up-streamed a fix (commit 2f216a85 - it went into 5.4-rc8) I'm working on doing a patch that I'm hoping to get into Debian to backport - just not done yet :) The patch is pretty small (I've attached it) so you might want to give it a go and see if it helps. Note - we did also test X1 extreme with OLED panel and didn't see a problem therebut it's a really subtle timing issue so some units might be more susceptible than others. Maybe worth a go? If it does make a difference let me know. Mark > -Original Message- > From: Jiri Kanicky > Sent: Sunday, November 24, 2019 9:13 PM > To: 944...@bugs.debian.org > Subject: [External] Bug#944350: systemd: screen remains off after waking up > from suspend > > Further to the issue, when I set BIOS to discrete graphics only, I am > experiencing the same issue when booting the system from shutdown state. > The screen stays off, but the OS is booted and working. 0001-drm-i915-update-rawclk-also-on-resume.patch Description: 0001-drm-i915-update-rawclk-also-on-resume.patch
Bug#900821: Reproduced on Apache container images for Docker/Kubernetes
Hi all, I experienced this problem while working with Apache container images deployed on a Kubernetes cluster on Azure (the containers are based on Debian). root@apache-nodeport-test-6595bf6579-5vsl6:/usr/local/apache2# hostname apache-nodeport-test-6595bf6579-5vsl6 root@apache-nodeport-test-6595bf6579-5vsl6:/usr/local/apache2# uname -a Linux apache-nodeport-test-6595bf6579-5vsl6 4.15.0-1060-azure #65-Ubuntu SMP Wed Sep 18 08:55:51 UTC 2019 x86_64 GNU/Linux root@apache-nodeport-test-6595bf6579-5vsl6:/usr/local/apache2# cat /etc/debian_version 10.2 root@apache-nodeport-test-6595bf6579-5vsl6:/usr/local/apache2# cat /etc/apt/sources.list # deb http://snapshot.debian.org/archive/debian/20191118T00Z buster main deb http://deb.debian.org/debian buster main # deb http://snapshot.debian.org/archive/debian-security/20191118T00Z buster/updates main deb http://security.debian.org/debian-security buster/updates main # deb http://snapshot.debian.org/archive/debian/20191118T00Z buster-updates main deb http://deb.debian.org/debian buster-updates main root@apache-nodeport-test-6595bf6579-5vsl6:/usr/local/apache2# apachectl -v Server version: Apache/2.4.41 (Unix) Server built: Nov 23 2019 00:34:14 I have tested 2 Apache 2.4.X containers, one from Azure, and one from Bitnami, with the same behaviour. Greetings, David.
Processed: Re: Bug#927026: Please enable CONFIG_MD_CLUSTER for linux packages in Buster
Processing control commands: > tags -1 + pending Bug #927026 [src:linux] Please enable CONFIG_MD_CLUSTER for linux packages in Buster Added tag(s) pending. -- 927026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927026: Please enable CONFIG_MD_CLUSTER for linux packages in Buster
Control: tags -1 + pending Hi, On Sun, Oct 20, 2019 at 02:35:00PM +0200, Valentin Vidić wrote: > Hi, > > Please enable for kernels in unstable so we can test cluster functionality > for bullseye release. Enabled now in master branch[1]. Regards, Salvatore [1] https://salsa.debian.org/kernel-team/linux/commit/5eed86cb5b5d331499f9971724f7030c5a3f4d8a
Processed: Re: Bug#927026: Please enable CONFIG_MD_CLUSTER for linux packages in Buster
Processing control commands: > tags -1 + pending Bug #927026 [src:linux] Please enable CONFIG_MD_CLUSTER for linux packages in Buster Ignoring request to alter tags of bug #927026 to the same tags previously set -- 927026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945497: initramfs-tools: Resume function does not check for swap file
Package: initramfs-tools
Version: 0.133ubuntu10
Severity: normal
Dear Maintainer,
The resume hook script (/usr/share/initramfs-tools/hooks/resume) does not check
for a swap file. It checks for a swap device referenced by the RESUME variable.
The RESUME_OFFSET variable is additionally used to point to a file in the
RESUME device that acts as the swap device. In this case, since RESUME points
to a standard file system, a warning is generated:
W: initramfs-tools configuration sets RESUME=$RESUME
W: but no matching swap device is available.
The following contains a possible solution to check for a swap file. It relies
on a set RESUME_OFFSET variable indicating a swap file. At least two files
should be modified: 1) the resume hook script and 2) the mkinitramfs script.
The resume script contains the following line numbered items. The unnumbered
lines contain a possible fix to check for the use of a swap file.
20 # First check if a location is set and is a valid swap partition.
21 # If so, the config file will be copied in and there is nothing to do.
22 if [ -n "$RESUME" ] && [ "$RESUME" != auto ]; then
23 if [ "$RESUME" = none ]; then
24 exit 0
25 fi
if resume_dev_node="$(resolve_device "$RESUME")"; then
if [ -z "$RESUME_OFFSET" ] && \
blkid -p -n swap "$resume_dev_node" >/dev/null 2>&1;
then
exit 0
fi
# Assume RESUME_OFFSET is a proper offset pointing to
# the first data block of an inode in RESUME.
# Then, the swap filename should be in /proc/swaps.
# Get largest filename that is NOT a /dev/...
for resume_filename in $( grep -v ^/dev/ /proc/swaps |
grep ^/ | sort -rnk3 | cut -d " " -f 1 ); do
if [ -n "$resume_filename" ] && \
blkid -p -n swap "$resume_filename"
>/dev/null 2>&1; then
exit 0
fi
break
done
echo >&2 "W: initramfs-tools configuration sets
RESUME=$RESUME and
echo >&2 "W:
RESUME_OFFSET=$RESUME_OFFSET"
echo >&2 "W: but no matching swap file is available."
29 fi
30
31 echo >&2 "W: initramfs-tools configuration sets RESUME=$RESUME"
32 echo >&2 "W: but no matching swap device is available."
33 fi
Getting a file name from an inode from a block offset might be done, but is
problematic as tools related to this are dependent on the file system. For
ext*, this could be:
resume_inode=$( debugfs -R "icheck $RESUME_OFFSET" $resume_dev_node
2>/dev/null | tail -1 | cut -f2 )
resume_fn=$( debugfs -R "ncheck ${RESUME_INODE}" ${RESUME_DEV} 2>/dev/null |
tail -1 | cut -f2 )
However, this process is not generic and may not be available for every file
system.
Additionally, the mkinitramfs script (/usr/sbin/mkinitramfs) does not export
the RESUME_OFFSET variable. It should be exported for use by the hook scripts.
242 # Export environment for hook scripts.
243 #
244 export MODULESDIR
245 export version
246 export CONFDIR
247 export DESTDIR
248 export DPKG_ARCH
249 export verbose
250 export MODULES
251 export BUSYBOX
252 export COMPCACHE_SIZE
253 export RESUME
export RESUME_OFFSET
254
-- System Information:
Debian Release: buster/sid
APT prefers eoan-updates
APT policy: (500, 'eoan-updates'), (500, 'eoan-security'), (500, 'eoan'),
(100, 'eoan-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-23-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages initramfs-tools depends on:
ii initramfs-tools-core 0.133ubuntu10
ii linux-base4.5ubuntu2
initramfs-tools recommends no packages.
Versions of packages initramfs-tools suggests:
ii bash-completion 1:2.9-1ubuntu1
-- no debconf information
Processed: severity of 945497 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 945497 wishlist Bug #945497 [initramfs-tools] initramfs-tools: Resume function does not check for swap file Severity set to 'wishlist' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 945497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
