Bug#1068356: linux-image-6.1.0-18-amd64: Debian 12.5 6.1.0-18-amd64 hibernate works the 1st time then "no space left on device" in journalctl
Package: src:linux Version: 6.1.76-1 Severity: important X-Debbugs-Cc: vek.m1...@gmail.com Dear Maintainer, * What led up to the situation? doing systemctl hibernate led to the issue * What exactly did you do (or not do) that was effective (or ineffective)? the swap space in the swap-partition is not free'd hence the issue. Doing swapoff /dev/sda3 and then swapon /dev/sda3 allows you to do a 2nd hibernation. -- Package-specific info: ** Version: Linux version 6.1.0-18-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-amd64 root=UUID=58b9f571-0c71-404b-bc1c-3c2bce44651e ro quiet ** Not tainted ** Kernel log: [ 7165.457863] psmouse serio1: synaptics: queried max coordinates: x [..5792], y [..4930] [ 7165.485066] psmouse serio1: synaptics: queried min coordinates: x [1142..], y [924..] [ 7165.600195] usb 1-1: reset high-speed USB device number 2 using ehci-pci [ 7165.600235] usb 3-1: reset high-speed USB device number 2 using ehci-pci [ 7165.624986] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7165.625033] ata1.00: Entering active power mode [ 7165.733802] ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out [ 7165.743730] ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out [ 7165.744385] ata1.00: configured for UDMA/133 [ 7166.076214] usb 1-1.2: reset full-speed USB device number 4 using ehci-pci [ 7166.264016] usb 1-1.3: reset high-speed USB device number 3 using ehci-pci [ 7166.685408] iwlwifi :02:00.0: Radio type=0x2-0x0-0x0 [ 7166.974423] iwlwifi :02:00.0: Radio type=0x2-0x0-0x0 [ 7167.060392] PM: hibernation: Basic memory bitmaps freed [ 7167.061723] OOM killer enabled. [ 7167.061729] Restarting tasks ... [ 7167.065019] Bluetooth: hci0: unexpected event for opcode 0x [ 7167.066972] done. [ 7167.079162] PM: hibernation: hibernation exit [ 7167.678674] wlp2s0: authenticate with 80:26:89:c3:6d:c2 [ 7167.681737] wlp2s0: send auth to 80:26:89:c3:6d:c2 (try 1/3) [ 7167.686166] wlp2s0: authenticated [ 7167.686461] wlp2s0: waiting for beacon from 80:26:89:c3:6d:c2 [ 7167.743863] wlp2s0: associate with 80:26:89:c3:6d:c2 (try 1/3) [ 7167.752254] wlp2s0: RX AssocResp from 80:26:89:c3:6d:c2 (capab=0x411 status=0 aid=1) [ 7167.766998] wlp2s0: associated [ 7279.848345] perf: interrupt took too long (3285 > 3278), lowering kernel.perf_event_max_sample_rate to 60750 [ 7846.625684] PM: hibernation: hibernation entry [ 7846.626180] (NULL device *): firmware: direct-loading firmware regulatory.db [ 7846.626528] (NULL device *): firmware: direct-loading firmware iwlwifi-2030-6.ucode [ 7846.627233] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s [ 7846.638138] Filesystems sync: 0.010 seconds [ 7846.638479] Freezing user space processes [ 7846.641720] Freezing user space processes completed (elapsed 0.003 seconds) [ 7846.641733] OOM killer disabled. [ 7846.641845] PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] [ 7846.641854] PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x000f] [ 7846.641864] PM: hibernation: Marking nosave pages: [mem 0x2000-0x201f] [ 7846.641898] PM: hibernation: Marking nosave pages: [mem 0x40004000-0x40004fff] [ 7846.641903] PM: hibernation: Marking nosave pages: [mem 0xca28f000-0x] [ 7846.649663] PM: hibernation: Basic memory bitmaps created [ 7846.649998] PM: hibernation: Preallocating image memory [ 7849.731022] PM: hibernation: Allocated 352092 pages for snapshot [ 7849.731036] PM: hibernation: Allocated 1408368 kbytes in 3.08 seconds (457.26 MB/s) [ 7849.731045] Freezing remaining freezable tasks [ 7849.732671] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [ 7849.733005] printk: Suspending console(s) (use no_console_suspend to debug) [ 7849.733217] wlp2s0: deauthenticating from 80:26:89:c3:6d:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 7849.752139] ata1.00: Entering standby power mode [ 7849.981920] ACPI: PM: Preparing to enter system sleep state S4 [ 7849.982658] ACPI: PM: Saving platform NVS memory [ 7849.984565] Disabling non-boot CPUs ... [ 7849.986646] smpboot: CPU 1 is now offline [ 7849.990274] smpboot: CPU 2 is now offline [ 7849.993445] smpboot: CPU 3 is now offline [ 7849.994083] PM: hibernation: Creating image: [ 7850.262253] PM: hibernation: Need to copy 345294 pages [ 7850.262262] PM: hibernation: Normal pages needed: 345294 + 1024, available pages: 676103 [ 7851.142004] PM: hibernation: Image created (345294 pages copied) [ 7849.994729] ACPI: PM: Restoring platform NVS memory [ 7849.995556] Enabling non-boot CPUs ... [ 7849.995669] x86: Booting SMP configuration: [ 7849.995672] smpboot: Booting Node 0 Processor 1 APIC 0x1 [ 7849.999557] CPU1 is up [ 7849.999647] smpboot: Booting Node 0 Processor 2 APIC 0x2 [ 7850.003682] CPU2 is up [ 7850.
Bug#1068249: linux-image-6.1.0-18-amd64: ax201 iwlwifi driver creates millions of 'Unhandled alg: 0x33f0707' messages
Please always reply to the bug report (I'll see it then too)! On woensdag 3 april 2024 22:01:20 CEST you wrote: > Thanks, I am working on that, but it's not trivial > > (1) About firmware > > These are provided by debian and cause the problem > -rw-r--r-- 1 root root 1299660 2023-05-01 21:30 > iwlwifi-QuZ-a0-hr-b0-59.ucode -rw-r--r-- 1 root root 1370356 2023-05-01 > 21:30 iwlwifi-QuZ-a0-hr-b0-72.ucode > > I grabbed new fw from a TI git repo, but the debian kernel does not load any > of them. Is fw signed? Do I need to sign it with my MOK? Use the upstream repo to get the files. The files aren't signed. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ The `dmesg` command will tell you which firmware files it's trying to load. Then DL that(/those) file(s) from the repo and put them in /lib/firmware/ Then on next boot the kernel will find them. > -rw-r--r-- 1 root root 1369976 2024-04-03 21:24 > iwlwifi-QuZ-a0-hr-b0-73.ucode -rw-r--r-- 1 root root 1371668 2024-04-03 > 21:24 iwlwifi-QuZ-a0-hr-b0-74.ucode -rw-r--r-- 1 root root 1404184 > 2024-04-03 21:24 iwlwifi-QuZ-a0-hr-b0-77.ucode > > (2) About kernel experiments, unfortunately it is a production server with > samba-ad and ad replication. It uses btrfs and snapshots work great, but it > needs some work (disable email services, make snapshots, stop all clients, > testing, restore snapshots, reenable email, restart clients). > > (3) Instead I will try first to use debian testing on a different NUC, but > this will take some time. > > 2. April 2024 20:28, "Diederik de Haas" schrieb: > > On Tuesday, 2 April 2024 19:54:41 CEST J. Pfennig wrote: > >> Package: src:linux > >> Version: 6.1.76-1 > >> Severity: important > >> Tags: upstream > > > > I am/was inclined to remove that tag, but the problem is likely caused by > > firmware which is too old for the 'backported' patches that upstream > > applied.> > >> The driver fills the eventlog with millions !!! of messages, see below. > >> It otherwise works. The problem can be reproduced on different NUC > >> systems. > > > > If you downgrade the kernel version, does the issue then go away? > > > >> ** Kernel log: > >> [30911.569896] BTRFS info (device sda4): disk space caching is enabled > >> [30974.905443] net_ratelimit: 67420 callbacks suppressed > >> [30974.905457] iwlwifi :00:14.3: Unhandled alg: 0x33f0707 > >> [30974.905728] iwlwifi :00:14.3: Unhandled alg: 0x33f0707 > >> [30974.906036] iwlwifi :00:14.3: Unhandled alg: 0x33f0707 > > > > https://unix.stackexchange.com/a/721474 looks related and the solution is > > to upgrade the firmware to a newer version. > > That isn't available on Stable, but grabbing ``firmware-iwlwifi`` from > > Testing should be safe. Not sure if that version is new enough though. > > > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.gi > > t > > is the upstream repo and you could 'grab' the firmware files which `dmesg` > > reports it can't find. > > > >> -- System Information: > >> Debian Release: 12.5 > >> APT prefers stable-security > >> APT policy: (500, 'stable-security'), (500, 'stable') > >> Architecture: amd64 (x86_64) > >> > >> Versions of packages linux-image-6.1.0-18-amd64 is related to: > >> ii firmware-amd-graphics 20230210-5 > >> pn firmware-atheros > >> pn firmware-bnx2 > >> pn firmware-bnx2x > >> pn firmware-brcm80211 > >> pn firmware-cavium > >> ii firmware-intel-sound 20230210-5 > >> pn firmware-intelwimax > >> pn firmware-ipw2x00 > >> pn firmware-ivtv > >> ii firmware-iwlwifi 20230210-5 > > > > My guess is that those 'backported' patches expect newer firmware then > > that. signature.asc Description: This is a digitally signed message part.
Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel
Dear Bastian,
Am 03.04.24 um 18:26 schrieb Paul Menzel:
Am 01.04.24 um 22:29 schrieb Bastian Blank:
On Fri, Jan 26, 2024 at 01:44:44PM +0100, Paul Menzel wrote:
$ grep UUID /etc/default/grub
# Uncomment if you don't want GRUB to pass "root=UUID=xxx"
parameter to Linux
GRUB_DISABLE_LINUX_UUID=true
I am now able to boot the VM image without an initrd, editing
`/boot/grub/grub.cfg`, which saves a little time, as the initrd does not
need to be loaded by GRUB and later dealt with (unpack/run) by the Linux
kernel.
Sou you already have all the infrastructure to create initrd. Please
use virtiofs for this case.
Sorry, I have the feeling we talk past each other. I do not want to
create an initrd. I want to boot *without* an initrd, and the only
missing piece is building VIRTIO_BLK into the Linux kernel.
Ubuntu also builds this into their “kvm” flavour [1].
I referenced the incorrect repository. With the help of
#ubuntu-ker...@irc.libera.chat, from `annotations` in *linux-kvm*
archive [2]:
CONFIG_VIRTIO_BLK policy<{'amd64': 'y'}>
If you think, that is unnecessary, could you please elaborate, how I
would achieve the goal with virtiofs?
Kind regards,
Paul
[1]:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/tree/debian.master/config/annotations#n611
[2]:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-kvm/+git/jammy/tree/debian.kvm/config/annotations?h=master-next#n476
Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel
Dear Bastian, Am 01.04.24 um 22:29 schrieb Bastian Blank: On Fri, Jan 26, 2024 at 01:44:44PM +0100, Paul Menzel wrote: $ grep UUID /etc/default/grub # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux GRUB_DISABLE_LINUX_UUID=true I am now able to boot the VM image without an initrd, editing `/boot/grub/grub.cfg`, which saves a little time, as the initrd does not need to be loaded by GRUB and later dealt with (unpack/run) by the Linux kernel. Sou you already have all the infrastructure to create initrd. Please use virtiofs for this case. Sorry, I have the feeling we talk past each other. I do not want to create an initrd. I want to boot *without* an initrd, and the only missing piece is building VIRTIO_BLK into the Linux kernel. Ubuntu also builds this into their “kvm” flavour [1]. If you think, that is unnecessary, could you please elaborate, how I would achieve the goal with virtiofs? Kind regards, Paul [1]: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/tree/debian.master/config/annotations#n611
Bug#1056428: /usr/sbin/lparstat: Could not open /proc/ppc64/lparcfg when lauch lparstat
Hello Thomas, On Wed, 2024-04-03 at 12:22 +, PEPONAS Thomas wrote: > On IBM Power paltform , add cpu entitlement can not be done without > LPARCFG=Y , because /proc/ppc64/lparcfg could not open: > Logs from drmgr : > ## Apr 03 10:54:41 2024 ## > drmgr: -c cpu -r -q 10 -p ent_capacity -w 5 -d 1 > Validating CPU DLPAR capability...yes. > Could not open "/proc/ppc64/lparcfg" > No such file or directory > CPU entitlement capability is not enabled on this platform. > Could not update system parameter ent_capacity > ## Apr 03 10:54:41 2024 ## > > will the LPARCFG option be activated on future versions? The Debian kernel maintainers are informed since I have reassigned the bug to the kernel package. I assume this will be fixed in the near future. I might do it myself if I find the time during the next weeks. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1056428: /usr/sbin/lparstat: Could not open /proc/ppc64/lparcfg when lauch lparstat
Hello, On IBM Power paltform , add cpu entitlement can not be done without LPARCFG=Y , because /proc/ppc64/lparcfg could not open: Logs from drmgr : ## Apr 03 10:54:41 2024 ## drmgr: -c cpu -r -q 10 -p ent_capacity -w 5 -d 1 Validating CPU DLPAR capability...yes. Could not open "/proc/ppc64/lparcfg" No such file or directory CPU entitlement capability is not enabled on this platform. Could not update system parameter ent_capacity ## Apr 03 10:54:41 2024 ## will the LPARCFG option be activated on future versions? Best Regards, Thomas. -Message d'origine- De : John Paul Adrian Glaubitz Envoyé : mercredi 22 novembre 2023 21:06 À : PEPONAS Thomas Cc : 1056...@bugs.debian.org Objet : Re: Bug#1056428: /usr/sbin/lparstat: Could not open /proc/ppc64/lparcfg when lauch lparstat Control: reassign -1 src:linux Control: retitle -1 "linux: Please enable CONFIG_LPARCFG for ppc64 and ppc64el" Hello Thomas! On Wed, 2023-11-22 at 13:02 +0100, peponas wrote: > lparstat report "Could not open /proc/ppc64/lparcfg" exemple : > lparstat 1 1 > Could not open /proc/ppc64/lparcfg > > System Configuration > type=Dedicated mode=Uncapped smt=8 lcpu=- mem=16653440 kB cpus=0 > ent=0.00 > > %user %sys %wait%idlephysc %entc lbusy app vcsw phint > - - --- - - - - - > Could not open /proc/ppc64/lparcfg > 0.12 0.12 0.0099.75 0.00 nan 0.25 0.00 - 350 > > kernel with config LPARCFG=Y resolv problem. Since this is obviously something that needs to be changed in the kernel configuration, the bug should be reported against src:linux and not against the powerpc-utils package. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
