Bug#1029356: marked as done (Thinkpad AMD: amd_pmc module is required for correct s0ix (Windows mode) suspend)
Your message dated Tue, 24 Jan 2023 08:03:23 +0100 with message-id <5642177.DvuYhMxLoT@turnagra> and subject line Re: Bug#1029356: Thinkpad AMD: amd_pmc module is required for correct s0ix (Windows mode) suspend has caused the Debian Bug report #1029356, regarding Thinkpad AMD: amd_pmc module is required for correct s0ix (Windows mode) suspend 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 ow...@bugs.debian.org immediately.) -- 1029356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-6.1.0-1-amd64 Version: 6.1.4-1 Severity: important Hello there, this is a regression from 6.0.0 too; after post-suspend wakeup, my plasma wayland session stays frozen; the two DisplayPort screens light up, backgrounds are shown, but the mouse doesn't move, nothing works. I'm reportbug'ging this from a SysRQ-R, Ctrl-Alt-F2 text tty. >From cursory dmesg reading, it seems amdgpu has an "IB test failed" _before_ kernel suspend. This is on 6.1.4-1a~test, patched against the "2nd DisplayPort doesn't light up", so feel free to close the bug; I'll test if I get the same symptoms on an unpatched kernel anyway :-) Best, OdyX -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CH:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.1.0-1-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod30+20221128-1 ii linux-base 4.9 Versions of packages linux-image-6.1.0-1-amd64 recommends: ii apparmor 3.0.8-1 ii firmware-linux-free 20200122-1 Versions of packages linux-image-6.1.0-1-amd64 suggests: pn debian-kernel-handbook ii extlinux3:6.04~git20190206.bf6db5b4+dfsg1-3+b1 ii grub-efi-amd64 2.06-7 pn linux-doc-6.1 --- End Message --- --- Begin Message --- Version: 6.1.7-2 Hello there, Le lundi, 23 janvier 2023, 22.09:22 h CET Salvatore Bonaccorso a écrit : > (Adding Mario to CC, I guess he is fine with it, given as well > involved in Debian). > > On Sat, Jan 21, 2023 at 05:54:26PM +0100, Didier 'OdyX' Raboud wrote: > > Control: tags -1 +patch -help > > Control: clone -1 -2 > > Control: retitle -2 Thinkpad AMD: amd_pmc module is required for correct > > s0ix (Windows mode) suspend Control: severity -2 important > > > > Hello there, > > > > My understanding is that there are two distinct bugs here; hereby > > splitting to make this clearer. > > The answer here is probably "maybe". > > > * Original bug, as retitled by Salvatore; S3 suspend is broken on some AMD > > > > Ryzens. This is fixed by this patch queue, also attached. > > > > https://gitlab.freedesktop.org/superm1/linux/-/commits/mlimonci/rhbz-21620 > > 13-gitlab-2357-v4/> > > In the BIOS, "S3" is "Linux mode" for suspend. > > This is one clear bug, which has now patches submitted upstream for > review, hopefully for inclusion and then tickle in in 6.1.y. > > > * While investigating this; it turns out modern kernels can also suspend > > on s0ix "Windows mode", but this _requires_ the `amd_pmc` module, which > > is not loaded automatically, but it really should. This doesn't look > > like an upstream bug, but rather a Debian one. > > > > As this only shows on Laptops with a "Windows mode" BIOS configuration > > (in a box that also shows "Linux mode"), I think it's reasonable to see > > this as a bug of only "important" level (even though not resuming from > > suspend is _bad_). > > > > I don't think we have seen a patch to fix this one yet though. > > I asked explicitly again here upstream, but I think there might be a > missunderstanding of each other's side. I asked upstream what can help > identify why the module is not autoloading, in the thread > https://lore.kernel.org/lkml/y81ja5y%2ftgpxk...@eldamar.lan/#t . > Unfortunately the replies from Mario are not archived. But his final > > reply was: > > Salvatore, > > > > I don't think we have a bug here. The reporters said it's working > > for s0ix. > > > > It will only load by default when the system is set to Modern > > Standby/s2idle
Processed: bug 971068 is forwarded to https://lore.kernel.org/lkml/y89xbxittrfpj...@eldamar.lan/T/#u
Processing commands for cont...@bugs.debian.org: > forwarded 971068 > https://lore.kernel.org/lkml/y89xbxittrfpj...@eldamar.lan/T/#u Bug #971068 [src:linux] linux-image-5.9.0-1-686-pae: Assertion failure in i915 intel_display.c#assert_plane() after resume from hibernation Set Bug forwarded-to-address to 'https://lore.kernel.org/lkml/y89xbxittrfpj...@eldamar.lan/T/#u'. > thanks Stopping processing here. Please contact me if you need assistance. -- 971068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1029384: ro option fails when used to mount a previously umounted partition
Processing control commands: > reassign -1 src:linux Bug #1029384 [mount] ro option fails when used to mount a previously umounted partition Bug reassigned from package 'mount' to 'src:linux'. No longer marked as found in versions util-linux/2.38.1-4. Ignoring request to alter fixed versions of bug #1029384 to the same values previously set -- 1029384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
linux-signed-i386_5.10.162+1_source.changes is NEW
Mapping stable-security to proposed-updates. binary:acpi-modules-5.10.0-21-686-di is NEW. binary:acpi-modules-5.10.0-21-686-pae-di is NEW. binary:ata-modules-5.10.0-21-686-di is NEW. binary:ata-modules-5.10.0-21-686-pae-di is NEW. binary:btrfs-modules-5.10.0-21-686-di is NEW. binary:btrfs-modules-5.10.0-21-686-pae-di is NEW. binary:cdrom-core-modules-5.10.0-21-686-di is NEW. binary:cdrom-core-modules-5.10.0-21-686-pae-di is NEW. binary:crc-modules-5.10.0-21-686-di is NEW. binary:crc-modules-5.10.0-21-686-pae-di is NEW. binary:crypto-dm-modules-5.10.0-21-686-di is NEW. binary:crypto-dm-modules-5.10.0-21-686-pae-di is NEW. binary:crypto-modules-5.10.0-21-686-di is NEW. binary:crypto-modules-5.10.0-21-686-pae-di is NEW. binary:efi-modules-5.10.0-21-686-di is NEW. binary:efi-modules-5.10.0-21-686-pae-di is NEW. binary:event-modules-5.10.0-21-686-di is NEW. binary:event-modules-5.10.0-21-686-pae-di is NEW. binary:ext4-modules-5.10.0-21-686-di is NEW. binary:ext4-modules-5.10.0-21-686-pae-di is NEW. binary:f2fs-modules-5.10.0-21-686-di is NEW. binary:f2fs-modules-5.10.0-21-686-pae-di is NEW. binary:fat-modules-5.10.0-21-686-di is NEW. binary:fat-modules-5.10.0-21-686-pae-di is NEW. binary:fb-modules-5.10.0-21-686-di is NEW. binary:fb-modules-5.10.0-21-686-pae-di is NEW. binary:firewire-core-modules-5.10.0-21-686-di is NEW. binary:firewire-core-modules-5.10.0-21-686-pae-di is NEW. binary:fuse-modules-5.10.0-21-686-di is NEW. binary:fuse-modules-5.10.0-21-686-pae-di is NEW. binary:i2c-modules-5.10.0-21-686-di is NEW. binary:i2c-modules-5.10.0-21-686-pae-di is NEW. binary:input-modules-5.10.0-21-686-di is NEW. binary:input-modules-5.10.0-21-686-pae-di is NEW. binary:isofs-modules-5.10.0-21-686-di is NEW. binary:isofs-modules-5.10.0-21-686-pae-di is NEW. binary:jfs-modules-5.10.0-21-686-di is NEW. binary:jfs-modules-5.10.0-21-686-pae-di is NEW. binary:kernel-image-5.10.0-21-686-di is NEW. binary:kernel-image-5.10.0-21-686-pae-di is NEW. binary:linux-image-5.10.0-21-686 is NEW. binary:linux-image-5.10.0-21-686-pae is NEW. binary:linux-image-5.10.0-21-rt-686-pae is NEW. binary:loop-modules-5.10.0-21-686-di is NEW. binary:loop-modules-5.10.0-21-686-pae-di is NEW. binary:md-modules-5.10.0-21-686-di is NEW. binary:md-modules-5.10.0-21-686-pae-di is NEW. binary:mmc-core-modules-5.10.0-21-686-di is NEW. binary:mmc-core-modules-5.10.0-21-686-pae-di is NEW. binary:mmc-modules-5.10.0-21-686-di is NEW. binary:mmc-modules-5.10.0-21-686-pae-di is NEW. binary:mouse-modules-5.10.0-21-686-di is NEW. binary:mouse-modules-5.10.0-21-686-pae-di is NEW. binary:mtd-core-modules-5.10.0-21-686-di is NEW. binary:mtd-core-modules-5.10.0-21-686-pae-di is NEW. binary:multipath-modules-5.10.0-21-686-di is NEW. binary:multipath-modules-5.10.0-21-686-pae-di is NEW. binary:nbd-modules-5.10.0-21-686-di is NEW. binary:nbd-modules-5.10.0-21-686-pae-di is NEW. binary:nic-modules-5.10.0-21-686-di is NEW. binary:nic-modules-5.10.0-21-686-pae-di is NEW. binary:nic-pcmcia-modules-5.10.0-21-686-di is NEW. binary:nic-pcmcia-modules-5.10.0-21-686-pae-di is NEW. binary:nic-shared-modules-5.10.0-21-686-di is NEW. binary:nic-shared-modules-5.10.0-21-686-pae-di is NEW. binary:nic-usb-modules-5.10.0-21-686-di is NEW. binary:nic-usb-modules-5.10.0-21-686-pae-di is NEW. binary:nic-wireless-modules-5.10.0-21-686-di is NEW. binary:nic-wireless-modules-5.10.0-21-686-pae-di is NEW. binary:pata-modules-5.10.0-21-686-di is NEW. binary:pata-modules-5.10.0-21-686-pae-di is NEW. binary:pcmcia-modules-5.10.0-21-686-di is NEW. binary:pcmcia-modules-5.10.0-21-686-pae-di is NEW. binary:pcmcia-storage-modules-5.10.0-21-686-di is NEW. binary:pcmcia-storage-modules-5.10.0-21-686-pae-di is NEW. binary:ppp-modules-5.10.0-21-686-di is NEW. binary:ppp-modules-5.10.0-21-686-pae-di is NEW. binary:rfkill-modules-5.10.0-21-686-di is NEW. binary:rfkill-modules-5.10.0-21-686-pae-di is NEW. binary:sata-modules-5.10.0-21-686-di is NEW. binary:sata-modules-5.10.0-21-686-pae-di is NEW. binary:scsi-core-modules-5.10.0-21-686-di is NEW. binary:scsi-core-modules-5.10.0-21-686-pae-di is NEW. binary:scsi-modules-5.10.0-21-686-di is NEW. binary:scsi-modules-5.10.0-21-686-pae-di is NEW. binary:scsi-nic-modules-5.10.0-21-686-di is NEW. binary:scsi-nic-modules-5.10.0-21-686-pae-di is NEW. binary:serial-modules-5.10.0-21-686-di is NEW. binary:serial-modules-5.10.0-21-686-pae-di is NEW. binary:sound-modules-5.10.0-21-686-di is NEW. binary:sound-modules-5.10.0-21-686-pae-di is NEW. binary:speakup-modules-5.10.0-21-686-di is NEW. binary:speakup-modules-5.10.0-21-686-pae-di is NEW. binary:squashfs-modules-5.10.0-21-686-di is NEW. binary:squashfs-modules-5.10.0-21-686-pae-di is NEW. binary:udf-modules-5.10.0-21-686-di is NEW. binary:udf-modules-5.10.0-21-686-pae-di is NEW. binary:uinput-modules-5.10.0-21-686-di is NEW. binary:uinput-modules-5.10.0-21-686-pae-di is NEW. binary:usb-modules-5.10.0-21-686-di is NEW. binary:usb-modules-5.10.0-21-686-pae-di is NEW. binary:usb-serial-modules-5.10.0-21-686-di is
linux-signed-arm64_5.10.162+1_source.changes is NEW
Mapping stable-security to proposed-updates. binary:ata-modules-5.10.0-21-arm64-di is NEW. binary:btrfs-modules-5.10.0-21-arm64-di is NEW. binary:cdrom-core-modules-5.10.0-21-arm64-di is NEW. binary:crc-modules-5.10.0-21-arm64-di is NEW. binary:crypto-dm-modules-5.10.0-21-arm64-di is NEW. binary:crypto-modules-5.10.0-21-arm64-di is NEW. binary:efi-modules-5.10.0-21-arm64-di is NEW. binary:event-modules-5.10.0-21-arm64-di is NEW. binary:ext4-modules-5.10.0-21-arm64-di is NEW. binary:f2fs-modules-5.10.0-21-arm64-di is NEW. binary:fat-modules-5.10.0-21-arm64-di is NEW. binary:fb-modules-5.10.0-21-arm64-di is NEW. binary:fuse-modules-5.10.0-21-arm64-di is NEW. binary:i2c-modules-5.10.0-21-arm64-di is NEW. binary:input-modules-5.10.0-21-arm64-di is NEW. binary:isofs-modules-5.10.0-21-arm64-di is NEW. binary:jfs-modules-5.10.0-21-arm64-di is NEW. binary:kernel-image-5.10.0-21-arm64-di is NEW. binary:leds-modules-5.10.0-21-arm64-di is NEW. binary:linux-image-5.10.0-21-arm64 is NEW. binary:linux-image-5.10.0-21-cloud-arm64 is NEW. binary:linux-image-5.10.0-21-rt-arm64 is NEW. binary:loop-modules-5.10.0-21-arm64-di is NEW. binary:md-modules-5.10.0-21-arm64-di is NEW. binary:mmc-modules-5.10.0-21-arm64-di is NEW. binary:mtd-core-modules-5.10.0-21-arm64-di is NEW. binary:multipath-modules-5.10.0-21-arm64-di is NEW. binary:nbd-modules-5.10.0-21-arm64-di is NEW. binary:nic-modules-5.10.0-21-arm64-di is NEW. binary:nic-shared-modules-5.10.0-21-arm64-di is NEW. binary:nic-usb-modules-5.10.0-21-arm64-di is NEW. binary:nic-wireless-modules-5.10.0-21-arm64-di is NEW. binary:ppp-modules-5.10.0-21-arm64-di is NEW. binary:sata-modules-5.10.0-21-arm64-di is NEW. binary:scsi-core-modules-5.10.0-21-arm64-di is NEW. binary:scsi-modules-5.10.0-21-arm64-di is NEW. binary:scsi-nic-modules-5.10.0-21-arm64-di is NEW. binary:squashfs-modules-5.10.0-21-arm64-di is NEW. binary:udf-modules-5.10.0-21-arm64-di is NEW. binary:uinput-modules-5.10.0-21-arm64-di is NEW. binary:usb-modules-5.10.0-21-arm64-di is NEW. binary:usb-serial-modules-5.10.0-21-arm64-di is NEW. binary:usb-storage-modules-5.10.0-21-arm64-di is NEW. binary:xfs-modules-5.10.0-21-arm64-di is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Bug#1027915: systemd requires /run to be mounted with a minimum size of 20MB
The attached patch ensures that the /run mount point
is always mounted with at least 20MB.
This is important since systemd requires at least 16MB
in /run, otherwise it will give errors and warnings and
will refuse to boot further after an emergency shell.
This patch has been tested on x86 (with VirtualBox VMs)
in configurations with 160MB RAM and 900MB RAM, as well
on a debian parisc installation with 160MB RAM.
This patch will adapt the size of /run, even if the
default value of 10% (of physical memory) is given
in the /etc/initramfs-tools/update-initramfs.conf file
(e.g. on x86).
Please apply to the next initramfs-tools update.
Signed-off-by: Helge Deller diff -up ./init.org ./init
--- ./init.org 2023-01-23 21:40:33.079738389 +
+++ ./init 2023-01-23 21:40:45.983861851 +
@@ -205,6 +205,15 @@ else
resume=${RESUME:-}
fi
+if [ -z "${RUNSIZE}" ] || [[ "${RUNSIZE}" \< "20" ]]; then
+ read MemTotal mem_kb rest < /proc/meminfo
+ # systemd requires at minumum 16MB for /run, so reserve
+ # 20MB for machines which have less than 200MB RAM
+ if [ "$mem_kb" -lt "20" ]; then
+ RUNSIZE=20M # for machines <= 200MB RAM
+ fi
+fi
+
mount -t tmpfs -o "nodev,noexec,nosuid,size=${RUNSIZE:-10%},mode=0755" tmpfs /run
mkdir -m 0700 /run/initramfs
linux-signed-amd64_5.10.162+1_source.changes is NEW
Mapping stable-security to proposed-updates. binary:acpi-modules-5.10.0-21-amd64-di is NEW. binary:ata-modules-5.10.0-21-amd64-di is NEW. binary:btrfs-modules-5.10.0-21-amd64-di is NEW. binary:cdrom-core-modules-5.10.0-21-amd64-di is NEW. binary:crc-modules-5.10.0-21-amd64-di is NEW. binary:crypto-dm-modules-5.10.0-21-amd64-di is NEW. binary:crypto-modules-5.10.0-21-amd64-di is NEW. binary:efi-modules-5.10.0-21-amd64-di is NEW. binary:event-modules-5.10.0-21-amd64-di is NEW. binary:ext4-modules-5.10.0-21-amd64-di is NEW. binary:f2fs-modules-5.10.0-21-amd64-di is NEW. binary:fat-modules-5.10.0-21-amd64-di is NEW. binary:fb-modules-5.10.0-21-amd64-di is NEW. binary:firewire-core-modules-5.10.0-21-amd64-di is NEW. binary:fuse-modules-5.10.0-21-amd64-di is NEW. binary:i2c-modules-5.10.0-21-amd64-di is NEW. binary:input-modules-5.10.0-21-amd64-di is NEW. binary:isofs-modules-5.10.0-21-amd64-di is NEW. binary:jfs-modules-5.10.0-21-amd64-di is NEW. binary:kernel-image-5.10.0-21-amd64-di is NEW. binary:linux-image-5.10.0-21-amd64 is NEW. binary:linux-image-5.10.0-21-cloud-amd64 is NEW. binary:linux-image-5.10.0-21-rt-amd64 is NEW. binary:loop-modules-5.10.0-21-amd64-di is NEW. binary:md-modules-5.10.0-21-amd64-di is NEW. binary:mmc-core-modules-5.10.0-21-amd64-di is NEW. binary:mmc-modules-5.10.0-21-amd64-di is NEW. binary:mouse-modules-5.10.0-21-amd64-di is NEW. binary:mtd-core-modules-5.10.0-21-amd64-di is NEW. binary:multipath-modules-5.10.0-21-amd64-di is NEW. binary:nbd-modules-5.10.0-21-amd64-di is NEW. binary:nic-modules-5.10.0-21-amd64-di is NEW. binary:nic-pcmcia-modules-5.10.0-21-amd64-di is NEW. binary:nic-shared-modules-5.10.0-21-amd64-di is NEW. binary:nic-usb-modules-5.10.0-21-amd64-di is NEW. binary:nic-wireless-modules-5.10.0-21-amd64-di is NEW. binary:pata-modules-5.10.0-21-amd64-di is NEW. binary:pcmcia-modules-5.10.0-21-amd64-di is NEW. binary:pcmcia-storage-modules-5.10.0-21-amd64-di is NEW. binary:ppp-modules-5.10.0-21-amd64-di is NEW. binary:rfkill-modules-5.10.0-21-amd64-di is NEW. binary:sata-modules-5.10.0-21-amd64-di is NEW. binary:scsi-core-modules-5.10.0-21-amd64-di is NEW. binary:scsi-modules-5.10.0-21-amd64-di is NEW. binary:scsi-nic-modules-5.10.0-21-amd64-di is NEW. binary:serial-modules-5.10.0-21-amd64-di is NEW. binary:sound-modules-5.10.0-21-amd64-di is NEW. binary:speakup-modules-5.10.0-21-amd64-di is NEW. binary:squashfs-modules-5.10.0-21-amd64-di is NEW. binary:udf-modules-5.10.0-21-amd64-di is NEW. binary:uinput-modules-5.10.0-21-amd64-di is NEW. binary:usb-modules-5.10.0-21-amd64-di is NEW. binary:usb-serial-modules-5.10.0-21-amd64-di is NEW. binary:usb-storage-modules-5.10.0-21-amd64-di is NEW. binary:xfs-modules-5.10.0-21-amd64-di is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Bug#999915: (no subject)
I think the patch I sent in #1027915 should fix this issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027915#24
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 1027915 patch Bug #1027915 [initramfs-tools-core] systemd requires /run to be mounted with a minimum size of 20MB Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 1027915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028309: linux-image-6.0.0-6-amd64: Regression in Kernel 6.0: System partially freezes with "nvme controller is down"
On Thu, 12 Jan 2023 18:31:37 + =?UTF-8?Q?Julian_Gro=c3=9f?= wrote: My computer just froze on Kernel version 5.19.11-1. Though nothing got logged. Now I don't know if this is the same issue and newer kernels just behave better in terms of logging, or if this is a different issue.. I guess I will add a second screen to my computer, open journalctl on there, and point a camera at it to capture the issue. Hello Julian, Capturing with a camera might be possible. But if you have a serial port at the target machine, another capturing system available, and a cable connecting them, it might be more convenient to capture the output from the serial port, to have it in text form. Below links show the kernel parameters at the target machine: https://wiki.archlinux.org/title/working_with_the_serial_console#Kernel And at the capturing machine you could start "script", that would record all that happens to a file "typescript" in the current directory, and inside start "screen" to the other machine like here: https://wiki.archlinux.org/title/working_with_the_serial_console#Screen If the machine is still kind of responsive then it might also be possible to capture through a network connection via "netconsole", more details in following link: https://wiki.ubuntu.com/Kernel/Netconsole Kind regards, Bernhard
linux_5.10.162-1_source.changes is NEW
Mapping stable-security to proposed-updates. binary:affs-modules-5.10.0-21-4kc-malta-di is NEW. binary:affs-modules-5.10.0-21-5kc-malta-di is NEW. binary:affs-modules-5.10.0-21-loongson-3-di is NEW. binary:affs-modules-5.10.0-21-octeon-di is NEW. binary:ata-modules-5.10.0-21-4kc-malta-di is NEW. binary:ata-modules-5.10.0-21-5kc-malta-di is NEW. binary:ata-modules-5.10.0-21-armmp-di is NEW. binary:ata-modules-5.10.0-21-loongson-3-di is NEW. binary:ata-modules-5.10.0-21-powerpc64le-di is NEW. binary:btrfs-modules-5.10.0-21-4kc-malta-di is NEW. binary:btrfs-modules-5.10.0-21-5kc-malta-di is NEW. binary:btrfs-modules-5.10.0-21-armmp-di is NEW. binary:btrfs-modules-5.10.0-21-loongson-3-di is NEW. binary:btrfs-modules-5.10.0-21-marvell-di is NEW. binary:btrfs-modules-5.10.0-21-octeon-di is NEW. binary:btrfs-modules-5.10.0-21-powerpc64le-di is NEW. binary:btrfs-modules-5.10.0-21-s390x-di is NEW. binary:cdrom-core-modules-5.10.0-21-4kc-malta-di is NEW. binary:cdrom-core-modules-5.10.0-21-5kc-malta-di is NEW. binary:cdrom-core-modules-5.10.0-21-armmp-di is NEW. binary:cdrom-core-modules-5.10.0-21-loongson-3-di is NEW. binary:cdrom-core-modules-5.10.0-21-marvell-di is NEW. binary:cdrom-core-modules-5.10.0-21-octeon-di is NEW. binary:cdrom-core-modules-5.10.0-21-powerpc64le-di is NEW. binary:cdrom-core-modules-5.10.0-21-s390x-di is NEW. binary:crc-modules-5.10.0-21-4kc-malta-di is NEW. binary:crc-modules-5.10.0-21-5kc-malta-di is NEW. binary:crc-modules-5.10.0-21-armmp-di is NEW. binary:crc-modules-5.10.0-21-loongson-3-di is NEW. binary:crc-modules-5.10.0-21-marvell-di is NEW. binary:crc-modules-5.10.0-21-octeon-di is NEW. binary:crc-modules-5.10.0-21-powerpc64le-di is NEW. binary:crc-modules-5.10.0-21-s390x-di is NEW. binary:crypto-dm-modules-5.10.0-21-4kc-malta-di is NEW. binary:crypto-dm-modules-5.10.0-21-5kc-malta-di is NEW. binary:crypto-dm-modules-5.10.0-21-armmp-di is NEW. binary:crypto-dm-modules-5.10.0-21-loongson-3-di is NEW. binary:crypto-dm-modules-5.10.0-21-marvell-di is NEW. binary:crypto-dm-modules-5.10.0-21-octeon-di is NEW. binary:crypto-dm-modules-5.10.0-21-powerpc64le-di is NEW. binary:crypto-dm-modules-5.10.0-21-s390x-di is NEW. binary:crypto-modules-5.10.0-21-4kc-malta-di is NEW. binary:crypto-modules-5.10.0-21-5kc-malta-di is NEW. binary:crypto-modules-5.10.0-21-armmp-di is NEW. binary:crypto-modules-5.10.0-21-loongson-3-di is NEW. binary:crypto-modules-5.10.0-21-marvell-di is NEW. binary:crypto-modules-5.10.0-21-octeon-di is NEW. binary:crypto-modules-5.10.0-21-powerpc64le-di is NEW. binary:crypto-modules-5.10.0-21-s390x-di is NEW. binary:dasd-extra-modules-5.10.0-21-s390x-di is NEW. binary:dasd-modules-5.10.0-21-s390x-di is NEW. binary:efi-modules-5.10.0-21-armmp-di is NEW. binary:event-modules-5.10.0-21-4kc-malta-di is NEW. binary:event-modules-5.10.0-21-5kc-malta-di is NEW. binary:event-modules-5.10.0-21-armmp-di is NEW. binary:event-modules-5.10.0-21-loongson-3-di is NEW. binary:event-modules-5.10.0-21-marvell-di is NEW. binary:event-modules-5.10.0-21-octeon-di is NEW. binary:event-modules-5.10.0-21-powerpc64le-di is NEW. binary:ext4-modules-5.10.0-21-4kc-malta-di is NEW. binary:ext4-modules-5.10.0-21-5kc-malta-di is NEW. binary:ext4-modules-5.10.0-21-armmp-di is NEW. binary:ext4-modules-5.10.0-21-loongson-3-di is NEW. binary:ext4-modules-5.10.0-21-marvell-di is NEW. binary:ext4-modules-5.10.0-21-octeon-di is NEW. binary:ext4-modules-5.10.0-21-powerpc64le-di is NEW. binary:ext4-modules-5.10.0-21-s390x-di is NEW. binary:f2fs-modules-5.10.0-21-4kc-malta-di is NEW. binary:f2fs-modules-5.10.0-21-5kc-malta-di is NEW. binary:f2fs-modules-5.10.0-21-armmp-di is NEW. binary:f2fs-modules-5.10.0-21-loongson-3-di is NEW. binary:f2fs-modules-5.10.0-21-marvell-di is NEW. binary:f2fs-modules-5.10.0-21-octeon-di is NEW. binary:f2fs-modules-5.10.0-21-powerpc64le-di is NEW. binary:f2fs-modules-5.10.0-21-s390x-di is NEW. binary:fancontrol-modules-5.10.0-21-powerpc64le-di is NEW. binary:fat-modules-5.10.0-21-4kc-malta-di is NEW. binary:fat-modules-5.10.0-21-5kc-malta-di is NEW. binary:fat-modules-5.10.0-21-armmp-di is NEW. binary:fat-modules-5.10.0-21-loongson-3-di is NEW. binary:fat-modules-5.10.0-21-marvell-di is NEW. binary:fat-modules-5.10.0-21-octeon-di is NEW. binary:fat-modules-5.10.0-21-powerpc64le-di is NEW. binary:fat-modules-5.10.0-21-s390x-di is NEW. binary:fb-modules-5.10.0-21-4kc-malta-di is NEW. binary:fb-modules-5.10.0-21-5kc-malta-di is NEW. binary:fb-modules-5.10.0-21-armmp-di is NEW. binary:fb-modules-5.10.0-21-loongson-3-di is NEW. binary:fb-modules-5.10.0-21-marvell-di is NEW. binary:fb-modules-5.10.0-21-powerpc64le-di is NEW. binary:firewire-core-modules-5.10.0-21-loongson-3-di is NEW. binary:firewire-core-modules-5.10.0-21-powerpc64le-di is NEW. binary:fuse-modules-5.10.0-21-4kc-malta-di is NEW. binary:fuse-modules-5.10.0-21-5kc-malta-di is NEW. binary:fuse-modules-5.10.0-21-armmp-di is NEW. binary:fuse-modules-5.10.0-21-loongson-3-di is NEW. binary:fuse-modules-5.10.0-21-marvell-di is
Bug#1029356: Thinkpad AMD: amd_pmc module is required for correct s0ix (Windows mode) suspend
Control: tags -1 + moreinfo Hi Didier, (Adding Mario to CC, I guess he is fine with it, given as well involved in Debian). On Sat, Jan 21, 2023 at 05:54:26PM +0100, Didier 'OdyX' Raboud wrote: > Control: tags -1 +patch -help > Control: clone -1 -2 > Control: retitle -2 Thinkpad AMD: amd_pmc module is required for correct s0ix > (Windows mode) suspend > Control: severity -2 important > > Hello there, > > My understanding is that there are two distinct bugs here; hereby splitting > to make this clearer. The answer here is probably "maybe". > * Original bug, as retitled by Salvatore; S3 suspend is broken on some AMD > Ryzens. This is fixed by this patch queue, also attached. > https://gitlab.freedesktop.org/superm1/linux/-/commits/mlimonci/rhbz-2162013-gitlab-2357-v4/ > > In the BIOS, "S3" is "Linux mode" for suspend. This is one clear bug, which has now patches submitted upstream for review, hopefully for inclusion and then tickle in in 6.1.y. > * While investigating this; it turns out modern kernels can also suspend > on s0ix "Windows mode", but this _requires_ the `amd_pmc` module, which > is not loaded automatically, but it really should. This doesn't look > like an upstream bug, but rather a Debian one. > > As this only shows on Laptops with a "Windows mode" BIOS configuration > (in a box that also shows "Linux mode"), I think it's reasonable to see > this as a bug of only "important" level (even though not resuming from > suspend is _bad_). > > I don't think we have seen a patch to fix this one yet though. I asked explicitly again here upstream, but I think there might be a missunderstanding of each other's side. I asked upstream what can help identify why the module is not autoloading, in the thread https://lore.kernel.org/lkml/y81ja5y%2ftgpxk...@eldamar.lan/#t . Unfortunately the replies from Mario are not archived. But his final reply was: > Salvatore, > > I don't think we have a bug here. The reporters said it's working > for s0ix. > > It will only load by default when the system is set to Modern > Standby/s2idle mode in BIOS. On Lenovo systems they call this > "Windows" sleep mode for some systems. Didier, in my undestanding of your comments on upstream issue, you did that actually, correct? I.e. setting to Modern Standby/s2idle mode in BIOS, but amd_pmc was still *not* autoloading? Regards, Salvatore
Processed: Re: Bug#1029356: Thinkpad AMD: amd_pmc module is required for correct s0ix (Windows mode) suspend
Processing control commands: > tags -1 + moreinfo Bug #1029356 [src:linux] Thinkpad AMD: amd_pmc module is required for correct s0ix (Windows mode) suspend Added tag(s) moreinfo. -- 1029356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: [6.1] regression in net/mac80211/rx.c causing mt76x2u to freeze the system
On Monday, 23 January 2023 19:05:43 CET Florian Rehnisch wrote: > I researched a bit and found a discussion in the Arch forum, and also an > issue in the upstream bugzilla, mentioning a patch. > > I applied that patch against linux-source/6.1.7-1, built it, and it > fixed the freeze. That patch is also mainlined (for 6.2rc5 I guess). > > What should I do now? Sorry for the noise. It's already in the queue so should be released with 6.1.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/ queue-6.1/wifi-mac80211-fix-initialization-of-rx-link-and-rx-link_sta.patch signature.asc Description: This is a digitally signed message part.
[6.1] regression in net/mac80211/rx.c causing mt76x2u to freeze the system
Hi folks, I have an issue with both linux-image-6.1.0-1-amd64/6.1.4-1 and linux-image-6.1.0-2-amd64/6.1.7-1. I have a | Bus 002 Device 007: ID 057c:8503 AVM GmbH FRITZ!WLAN AC 860 stick, and a soon as this gets traffic, the system silently freezes (i.e. no Kernel Panic at tty1). I researched a bit and found a discussion in the Arch forum, and also an issue in the upstream bugzilla, mentioning a patch. I applied that patch against linux-source/6.1.7-1, built it, and it fixed the freeze. That patch is also mainlined (for 6.2rc5 I guess). What should I do now? Sorry for the noise. Greetings, Florian [Arch] https://bbs.archlinux.org/viewtopic.php?id=282306 [bugzilla] https://bugzilla.kernel.org/show_bug.cgi?id=216839 [patch] https://patchwork.kernel.org/project/linux-wireless/patch/20221217085624.52077-1-...@nbd.name/
Processed: Re: Bug#1029507: linux-image-6.1.0-1-amd64 isn't installable
Processing control commands: > reassign -1 dkms Bug #1029507 [src:linux] linux-image-6.1.0-1-amd64 isn't installable Bug reassigned from package 'src:linux' to 'dkms'. No longer marked as found in versions linux/6.1.4-1. Ignoring request to alter fixed versions of bug #1029507 to the same values previously set > forcemerge 1029063 -1 Bug #1029063 [dkms] dkms: linux-image-* remains unconfigured after dkms module build failure Bug #1029388 [dkms] linux-image-6.1.0-2-amd64: system does not boot up when swap partion is a file Bug #1029507 [dkms] linux-image-6.1.0-1-amd64 isn't installable Severity set to 'grave' from 'normal' Bug #1029388 [dkms] linux-image-6.1.0-2-amd64: system does not boot up when swap partion is a file Merged 1029063 1029388 1029507 -- 1029063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029063 1029388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029388 1029507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029507: linux-image-6.1.0-1-amd64 isn't installable
Control: reassign -1 dkms Control: forcemerge 1029063 -1 On Monday, 23 January 2023 14:53:18 CET Stefano Simonucci wrote: > Building module: > Cleaning build area... > make -j8 KERNELRELEASE=6.1.0-1-amd64 all > KERNEL_SRC=/lib/modules/6.1.0-1-amd64/b uild...(bad exit status: 2) > Error! Bad return status for module build on kernel: 6.1.0-1-amd64 (x86_64) > Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information. This isn't a kernel issue, but an issue with anbox-binder which apparently is incompatible with kernel 6.1. Reassigning/merging accordingly. It could be https://github.com/anbox/anbox-modules/issues/104 or if you're using https://github.com/Barronli/anbox_binder then it already says in the README.md: "Note it is already out of sync from Linux kernel tree, but it is still useful in certain situations." signature.asc Description: This is a digitally signed message part.
Bug#1029507: linux-image-6.1.0-1-amd64 isn't installable
Package: src:linux Version: 6.1.4-1 Severity: normal X-Debbugs-Cc: stefanosimonucci@alice.it Dear Maintainer, The package linux-image-6.1.0-1-amd64 with linux-headers-6.1.0-1-amd64 can't be configured on my system. I must boot the previous kernel. I get: stefano@debsim:~$ sudo apt install linux-headers-6.1.0-1-amd64 linux-image-6.1.0-1-amd64 Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze... Fatto Lettura informazioni sullo stato... Fatto Pacchetti suggeriti: linux-doc-6.1 debian-kernel-handbook I seguenti pacchetti NUOVI saranno installati: linux-headers-6.1.0-1-amd64 linux-image-6.1.0-1-amd64 0 aggiornati, 2 installati, 0 da rimuovere e 26 non aggiornati. È necessario scaricare 0 B/76,5 MB di archivi. Dopo quest'operazione, verranno occupati 509 MB di spazio su disco. Selezionato il pacchetto linux-headers-6.1.0-1-amd64 non precedentemente selezio nato. (Lettura del database... 1189678 file e directory attualmente installati.) Preparativi per estrarre .../linux-headers-6.1.0-1-amd64_6.1.4-1_amd64.deb... Estrazione di linux-headers-6.1.0-1-amd64 (6.1.4-1)... Selezionato il pacchetto linux-image-6.1.0-1-amd64 non precedentemente seleziona to. Preparativi per estrarre .../linux-image-6.1.0-1-amd64_6.1.4-1_amd64.deb... Estrazione di linux-image-6.1.0-1-amd64 (6.1.4-1)... Configurazione di linux-image-6.1.0-1-amd64 (6.1.4-1)... I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.0.0-4-amd64 I: /initrd.img.old is now a symlink to boot/initrd.img-6.0.0-4-amd64 I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-1-amd64 I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-1-amd64 /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-1-amd64:Sign command: / usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j8 KERNELRELEASE=6.1.0-1-amd64 all KERNEL_SRC=/lib/modules/6.1.0-1-amd64/b uild...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-1-amd64 (x86_64) Consult /var/lib/dkms/anbox-ashmem/1/build/make.log for more information. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j8 KERNELRELEASE=6.1.0-1-amd64 all KERNEL_SRC=/lib/modules/6.1.0-1-amd64/b uild...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-1-amd64 (x86_64) Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j8 KERNELRELEASE=6.1.0-1-amd64 all KVERSION=... Signing module /var/lib/dkms/v4l2loopback_dc/0.0.1/build/v4l2loopback-dc.ko Cleaning build area... v4l2loopback-dc.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.0-1-amd64/updates/dkms/ depmod... Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: errore nell'elaborare il pacchetto linux-image-6.1.0-1-amd64 (--configure) : il sottoprocesso installato pacchetto linux-image-6.1.0-1-amd64 script post-ins tallation ha restituito lo stato di errore 1 Configurazione di linux-headers-6.1.0-1-amd64 (6.1.4-1)... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-1-amd64:Sign command: / usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j8 KERNELRELEASE=6.1.0-1-amd64 all KERNEL_SRC=/lib/modules/6.1.0-1-amd64/b uild...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-1-amd64 (x86_64) Consult /var/lib/dkms/anbox-ashmem/1/build/make.log for more information. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j8 KERNELRELEASE=6.1.0-1-amd64 all KERNEL_SRC=/lib/modules/6.1.0-1-amd64/b uild...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-1-amd64 (x86_64) Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-head ers-6.1.0-1-amd64.postinst line 11. dpkg: errore nell'elaborare il pacchetto linux-headers-6.1.0-1-amd64
Bug#1004070: linux-image-4.19.0-18-amd64: kernel crashes when accessing files via nfs
Hi Salvatore, thanks for asking! If I remember correctly later kernels did not work at the time when I tested this. But have not tried more recent 4.19.x kernel. At the moment I do not have that much time but I will share the results here once I test that. Regards Friedrich > Am 21.01.2023 um 20:47 schrieb Salvatore Bonaccorso : > > Control: tags -1 + moreinfo > > Hi Friedrich, > > On Thu, Jan 20, 2022 at 11:08:35AM +0100, Friedrich Beckmann wrote: >> Package: src:linux >> Version: 4.19.208-1 >> Severity: important >> >> Dear Maintainer, >> >> after dist-upgrading to debian 10 the kernel crashes when accessing >> files on nfs mounted filesystems. The bug can be reproduced by writing >> between 100 and 1000 files á 50MByte to the mounted filesystem. The system >> crashes completely, i.e. you cannot ping and ssh is dead. I have >> to powercycle via ipmi to come back. >> >> The bug is not there when I boot the previous 4.9.0-16-amd64 kernel. >> >> This is a headless system with 4 nvidia gpus running with the proprietary >> nvidia driver version 470.82.01. I do not think that this is related as >> the bug happens even when nothing is happening on the gpus. The bios is from >> 2015 but I >> load the intel-microcode. >> >> Looking upstream, maybe this bug is related to >> >> Bug 203827 - NFS v4.1 and v4.2 still unstable - >> https://bugzilla.kernel.org/show_bug.cgi?id=203827 >> Bug 200145 - kernel: FS-Cache: Duplicate cookie detected - >> https://bugzilla.kernel.org/show_bug.cgi?id=200145 >> >> Regards >> >> Friedrich >> >> I can reproduce the bug with the following script: >> >> === killer script >> #! /bin/bash -xe >> cnt=1 >> for (( ; ; )) >> do >>echo "Run: $cnt" >>((cnt++)) >>dd if=/dev/urandom of=~/sf bs=1M count=50 >> rm ~/sf >> done >> === >> >> >> == kern.log >> Jan 20 09:51:50 breakout kernel: [ 133.957968] FS-Cache: Duplicate cookie >> detected >> Jan 20 09:51:50 breakout kernel: [ 133.959815] FS-Cache: O-cookie >> c=0d1e4bca [p=6521ae05 fl=212 nc=0 na=0] >> Jan 20 09:51:50 breakout kernel: [ 133.961667] FS-Cache: O-cookie d= >> (null) n= (null) >> Jan 20 09:51:50 breakout kernel: [ 133.963553] FS-Cache: O-key=[16] >> '0400010002000801c0a8505a' >> Jan 20 09:51:50 breakout kernel: [ 133.965407] FS-Cache: N-cookie >> c=883b7c78 [p=6521ae05 fl=2 nc=0 na=1] >> Jan 20 09:51:50 breakout kernel: [ 133.967273] FS-Cache: N-cookie >> d=dc94612b n=2d9b546b >> Jan 20 09:51:50 breakout kernel: [ 133.968059] FS-Cache: N-key=[16] >> '0400010002000801c0a8505a' >> Jan 20 09:51:58 breakout kernel: [ 141.528246] FS-Cache: Duplicate cookie >> detected >> Jan 20 09:51:58 breakout kernel: [ 141.529925] FS-Cache: O-cookie >> c=ab5caa2d [p=6521ae05 fl=212 nc=0 na=0] >> Jan 20 09:51:58 breakout kernel: [ 141.531542] FS-Cache: O-cookie d= >> (null) n= (null) >> Jan 20 09:51:58 breakout kernel: [ 141.533136] FS-Cache: O-key=[16] >> '0400010002000801c0a8505a' >> Jan 20 09:51:58 breakout kernel: [ 141.534743] FS-Cache: N-cookie >> c=65656ae5 [p=6521ae05 fl=2 nc=0 na=1] >> Jan 20 09:51:58 breakout kernel: [ 141.536340] FS-Cache: N-cookie >> d=dc94612b n=49e94c35 >> Jan 20 09:51:58 breakout kernel: [ 141.537919] FS-Cache: N-key=[16] >> '0400010002000801c0a8505a' >> Jan 20 09:52:27 breakout kernel: [ 170.456631] general protection fault: >> [#1] SMP PTI >> Jan 20 09:52:27 breakout kernel: [ 170.458602] CPU: 5 PID: 13651 Comm: dd >> Tainted: P OE 4.19.0-18-amd64 #1 Debian 4.19.208-1 >> Jan 20 09:52:27 breakout kernel: [ 170.460511] Hardware name: Supermicro >> SYS-7048GR-TR/X10DRG-Q, BIOS 2.0 12/31/2015 >> Jan 20 09:52:27 breakout kernel: [ 170.462416] RIP: >> 0010:__kmalloc+0xaa/0x220 >> Jan 20 09:52:27 breakout kernel: [ 170.464307] Code: 08 65 4c 03 05 cf 2e >> fe 78 49 83 78 10 00 49 8b 28 0f 84 0c 01 00 00 48 85 ed 0f 84 03 01 00 00 >> 41 8b 47 20 49 8b 3f 48 01 e8 <48> 8b 18 48 89 c1 49 33 9f 38 01 00 00 48 89 >> e8 48 0f c9 48 31 cb >> Jan 20 09:52:27 breakout kernel: [ 170.466332] RSP: 0018:9dfda84cf5b8 >> EFLAGS: 00010282 >> Jan 20 09:52:27 breakout kernel: [ 170.468343] RAX: bf0892e61936d294 RBX: >> RCX: 2a674397 >> Jan 20 09:52:27 breakout kernel: [ 170.470390] RDX: b080 RSI: >> 006000c0 RDI: 00025540 >> Jan 20 09:52:27 breakout kernel: [ 170.472401] RBP: bf0892e61936d294 R08: >> 8cbaff965540 R09: 8cbaff407300 >> Jan 20 09:52:27 breakout kernel: [ 170.474421] R10: 8cbaf2bed684 R11: >> 8cbae401a940 R12: 006000c0 >> Jan 20 09:52:27 breakout kernel: [ 170.476444] R13: 0029 R14: >> 8cbaff407780 R15: 8cbaff407780 >> Jan 20 09:52:27 breakout kernel: [ 170.478471] FS: 7f0afeeeb580() >> GS:8cbaff94()
