Bug#1036644: linux-image-6.1.0-9-amd64: System crashes. Netconsole reports CPUs not responding to MCE broadcast
I was able to resolve the issue with my ASRock J4105-ITX board (Celeron J4105) on Debian-12. I just had to apt install intel-microcode and reboot. After 4 weeks of running the system 23/7 I had no further crashes. Without that intel-microcode package /sys/devices/system/cpu/cpu*/microcode/version is 0x26 (38 decimal). And with intel-microcode-3.20230512.1 the version is 0x3e (decimal 62). I'm not sure why intel-microcode was not installed by default. All my other Debian computers have that package installed automatically. I had some very rare crashes with Debian-11. So Debian-12 maybe just worsened the issue and it already existed before updating to Debian-12. In theory a BIOS update might also do the job. I run BIOS 1.40 and there is a 1.60 version from 2021. But 1.60 does not list a microcode update. https://www.asrock.com/mb/Intel/J4105-ITX/#BIOS (haven't updated to BIOS 1.60 yet) Kind regards, kolAflash OpenPGP_0xEA831012D83C3408.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1038424: hostapd systemd template only works when matching interface name
Package: hostapd Version: 2:2.10-12 The file /usr/share/doc/hostapd/README.Debian tells, that you can run hostapd by creating a config /etc/hostapd/wifi.conf and using the template hostapd@wifi.service systemd unit. So you run systemctl enable --now hostapd@wifi.service to enable and start it. Side note: systemctl command not mentioned in the README.debian. But that's how systemd unit templates are handled as far as I know. Maybe this should be added to the README.debian. PROBLEM: That only works if your wlan interface is namend "wifi". If your interface is named differently, the templated name has to be changed accordingly. E.g. for "wlan0": hostapd@wlan0.service If the name doesn't matched the systemd unit is somehow immediately stopped again: Jun 18 04:53:00 myhost systemd[1]: Starting hostapd@wifi.service - Access point and authentication server for Wi-Fi and Ethernet (wifi)... Jun 18 04:53:01 myhost hostapd[45039]: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE Jun 18 04:53:01 myhost hostapd[45039]: wlan0: interface state COUNTRY_UPDATE->ENABLED Jun 18 04:53:01 myhost hostapd[45039]: wlan0: AP-ENABLED Jun 18 04:53:01 myhost systemd[1]: Started hostapd@wifi.service - Access point and authentication server for Wi-Fi and Ethernet (wifi). Jun 18 04:53:01 myhost systemd[1]: Stopping hostapd@wifi.service - Access point and authentication server for Wi-Fi and Ethernet (wifi)... Jun 18 04:53:02 myhost systemd[1]: hostapd@wifi.service: Deactivated successfully. Jun 18 04:53:02 myhost systemd[1]: Stopped hostapd@wifi.service - Access point and authentication server for Wi-Fi and Ethernet (wifi). IF this behavior is not intended, it's a bug. IF this behavior is intended, the README.Debian should mention it! -> "documentation bug" (just spend 30 minutes figuring it out) Kind regards, kolAflash OpenPGP_0xEA831012D83C3408.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1035535: Debian 11 -> 12: manual "apt install" needed to update some packages (vkd3d, appindicator, wx)
Hi Paul, I tried to reproduce the problems with: https://cloud.debian.org/images/cloud/bullseye/20230601-1398/debian-11-nocloud-amd64-20230601-1398.qcow2 Looks like libappindicator1 may has been a leftover from Debian-10. -> my fault And the vkd3d problem seems to be caused by the vkd3d-compiler package from the WineHQ apt repo. https://wiki.winehq.org/Debian -> probably a fault of the WineHQ repo Only problem left is wx3.0-headers not being upgraded to wx3.2-headers. As said, I tested using the debian-11-nocloud-amd64-20230601-1398.qcow2 image. Just these steps: apt install wx3.0-headers # update /etc/apt/sources.list apt clean apt update apt full-upgrade And wx3.0-headers/oldstable is still installed. Running apt full-upgrade again doesn't upgrade the package either. Kind regards, kolAflash OpenPGP_0xEA831012D83C3408.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1035535: Debian 11 -> 12: manual "apt install" needed to update some packages (vkd3d, appindicator, wx)
Same for chromium and chromium-l10n packages. But I guess this will be resolved when a new chromium version is provided for Bookworm.
Bug#1035535: Debian 11 -> 12: manual "apt install" needed to update some packages (vkd3d, appindicator, wx)
Package: upgrade-reports I upgraded my system from Debian 11 to 12 some days ago. But "apt dist-upgrade" didn't upgrade some packages. So I had to do it manually. Should it be that way? apt install \ vkd3d-compiler/bookworm \ libvkd3d-dev/bookworm \ libvkd3d-dev:i386/bookworm \ libappindicator1/bookworm By this the vkd3d packages where upgraded to bookworm and libappindicator1 was replaced with libayatana-appindicator1 and libayatana-indicator7. I also had wx3.0-headers installed. And I had to install the new +version manually. apt install wx3.2-headers Maybe related: My "apt dist-upgrade" from Debian 11 to 12 ended with an error. See here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994081#32 OpenPGP_0xEA831012D83C3408.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#994081: libdvd-pkg: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting...
Hi, I got the following error when running "apt dist-upgrade" to get from Debian-11 to Debian-12. (German locale) --> I guess this should maybe be fixed before Debian-12 release!? Maybe related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824078 libdvd-pkg: Downloading orig source... I: libdvdcss_1.4.3 /usr/bin/wget --tries=3 --timeout=40 --read-timeout=40 --continue -O libdvdcss_1.4.3.orig.tar.bz2 \ https://download.videolan.org/pub/libdvdcss/1.4.3/libdvdcss-1.4.3.tar.bz2 \ || /usr/bin/uscan --noconf --verbose --rename --destdir=/usr/src/libdvd-pkg --check-dirname-level=0 --force-download --download-current-version /usr/share/libdvd-pkg/debian --2023-04-28 15:37:01-- https://download.videolan.org/pub/libdvdcss/1.4.3/libdvdcss-1.4.3.tar.bz2 Auflösen des Hostnamens download.videolan.org (download.videolan.org)… 2a01:e0d:1:3:58bf:fa02:c0de:5, 213.36.253.2 Verbindungsaufbau zu download.videolan.org (download.videolan.org)|2a01:e0d:1:3:58bf:fa02:c0de:5|:443 … verbunden. HTTP-Anforderung gesendet, auf Antwort wird gewartet … 200 OK Länge: 388404 (379K) [application/octet-stream] Wird in »libdvdcss_1.4.3.orig.tar.bz2« gespeichert. libdvdcss_1.4.3.orig.tar.bz2100%[=>] 379,30K 2,42MB/sin 0,2s 2023-04-28 15:37:01 (2,42 MB/s) - »libdvdcss_1.4.3.orig.tar.bz2« gespeichert [388404/388404] libdvd-pkg: Checking orig.tar integrity... /usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: OK libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... OpenPGP_0xEA831012D83C3408.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1023067: Bookworm netinstall CD: X-Server crashing on virtio-gpu
Package: debian-installer Version: 20220917 Hi, the X-Server on the netinstall CD crashes when using a virtio GPU. qemu-system-x86_64 \ -m 1G -machine pc,accel=kvm \ -device virtio-vga \ -cdrom \ debian-12-netinstall-amd64_testing-20221029-1721/debian-testing-amd64-netinst.iso CD image downloaded here: https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso I attached some logfiles. The bug should be really easy to reproduce. Just boot up the graphical installer. This is a regression. Using a Debian-11 CD works fine. https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.5.0-amd64-netinst.iso Sincerely, kolAflash -- PGP: https://misc.kolahilft.de/pgp/MoritzDuge_0xC49633CB.asc bookworm_netinstall_virtio-gpu.tar.xz Description: application/xz OpenPGP_0xEA831012D83C3408.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1021919: virtionet device not found in debian testing netinst ISO 20221017
Hi, I got the same problem using Qemu. (Debian-11 host, using Debian's Qemu-5.2.0) qemu-system-x86_64 \ -m 1G -machine pc,accel=kvm \ -device virtio-net-pci,netdev=user.1 -netdev user,id=user.1 \ -cdrom debian-12-netinstall-amd64_testing-20221029-1721/debian-testing-amd64-netinst.iso When the installer begins detecting the network hardware. (after selecting the keyboard layout) dmesg: [ 52.822967] BPF: [97154] STRUCT [ 52.822970] BPF: size=896 vlen=72 [ 52.822970] BPF: [ 52.822971] BPF: invalid name [ 52.822971] BPF: [ 52.822972] failed to validate module [failover] BTF: -22 Maybe related? arm64+virtio: "No device for installation media was detected" error https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998087 Sincerely, kolAflash OpenPGP_0xEA831012D83C3408.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1016776: channel 13 broken on b43 (brcmsmac) driver since wireless-regdb-2022.04.08-2~deb11u1
Package: wireless-regdb Version: 2022.04.08-2~deb11u1 Since version 2022.04.08-2~deb11u1 of wireless-regdb my Lenovo notebook doesn't show up channel 13 wireless networks. Downgrading to version wireless-regdb-2020.04.29-2 fixes the problem. https://snapshot.debian.org/archive/debian/20200630T204925Z/pool/main/w/wireless-regdb/wireless-regdb_2020.04.29-2_all.deb OS: Debian-11 (KDE with NetworkManager) Notebook: Lenovo G560 (Model: 0679) CPU: Intel(R) Core(TM) i3 CPU M 350 @ 2.27GHz NIC: 06:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01) product: BCM4313 802.11bgn Wireless Network Adapter configuration: broadcast=yes driver=brcmsmac driverversion=5.10.0-16-amd64 firmware=610.812 ip=192.168.37.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11 I have no experience with the wireless stack. But please feel free to tell me what to test or which logs to send. Maybe related: wireless-regdb stable policy https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006127 I'm not sure how this is caused. I guess maybe it's an error in the regdb, maybe the b43 driver is interpreting the regdb wrongly. I got another notebook (HP) with RTL8822BE wireless which is still connecting to channel 13 networks with wireless-regdb-2022.04.08-2~deb11u1. I've tried rmmod b43; modprobe b43 allhwsupport=1 but that didn't help. I picked some interesting dmesg lines. But they also show up when rebooting after downgrading to wireless-regdb-2020.04.29-2 789 Aug 7 08:45:41 AnnaMargaretePC kernel: [ 23.466425] cfg80211: Loading compiled-in X.509 certificates for regulatory database 790 Aug 7 08:45:41 AnnaMargaretePC kernel: [ 23.466920] cfg80211: Loaded X.509 cert 'b...@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf' 791 Aug 7 08:45:41 AnnaMargaretePC kernel: [ 23.467404] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328' 792 Aug 7 08:45:41 AnnaMargaretePC kernel: [ 23.467890] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' 793 Aug 7 08:45:41 AnnaMargaretePC kernel: [ 23.740967] platform regulatory.0: firmware: direct-loading firmware regulatory.db 794 Aug 7 08:45:41 AnnaMargaretePC kernel: [ 23.763353] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s 795 Aug 7 08:45:41 AnnaMargaretePC kernel: [ 24.706741] Support for cores revisions 0x17 and 0x18 disabled by module param allhwsupport=0. Try b43.allhwsupport=1 796 Aug 7 08:45:41 AnnaMargaretePC kernel: [ 24.706756] b43: probe of bcma0:1 failed with error -524 797 Aug 7 08:45:41 AnnaMargaretePC kernel: [ 24.706811] Broadcom 43xx driver loaded [ Features: PNLS ] [...] 804 Aug 7 08:45:41 AnnaMargaretePC kernel: [ 25.350732] brcmsmac bcma0:1: mfg 4bf core 812 rev 24 class 0 irq 17 805 Aug 7 08:45:41 AnnaMargaretePC kernel: [ 25.351802] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' rmmod b43; rmmod brcmsmac; rmmod mac80211; rmmod cfg80211; iw reg get; iw reg set DE; iw reg get; modprobe -v cfg80211 ieee80211_regdom=DE; iw reg get; modprobe -v mac80211; iw reg get; iw reg get; modprobe -v brcmsmac; iw reg get; modprobe -v b43; iw reg get global country 00: DFS-UNSET (755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN (2402 - 2472 @ 40), (N/A, 20), (N/A) (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) global country DE: DFS-ETSI (2400 - 2483 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS (5725 - 5875 @ 80), (N/A, 13), (N/A) (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW (57000 - 66000 @ 2160), (N/A, 40), (N/A) global country DE: DFS-ETSI (2400 - 2483 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS (5725 - 5875 @ 80), (N/A, 13), (N/A) (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW (57000 - 66000 @ 2160), (N/A, 40), (N/A) insmod /lib/modules/5.10.0-16-amd64/kernel/net/mac80211/mac80211.ko global country DE: DFS-ETSI (2400 - 2483 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
Bug#994960: can't set RADV_DEBUG (apply patch or update to 0.5.8.4)
Package: lutris Version: 0.5.8.3-2 There's a bug in lutris-0.5.8.3 making it impossible to set the RADV_DEBUG environment variable. https://github.com/lutris/lutris/issues/3419 Please either apply the small upstream patch for Bullseye or update to lutris-0.5.8.4. Kind regards, kolAflash
Bug#983390: mesa-vulkan-drivers: bad interactions between VkLayer_MESA_device_select and other layers
On Thu, 25 Mar 2021 11:51:22 + Simon McVittie wrote: Version: 21.0.0-1 On Thu, 25 Mar 2021 at 11:46:36 +, Simon McVittie wrote: > This appears to be fixed in the new upstream 20.3.5 release (and also > in 21.0.0). This might be related. https://bugs.winehq.org/show_bug.cgi?id=51081#c8 In any case it's also fixed by upstream 20.3.5-1 So it would be helpful to include Mesa-20.3.5-1 into Bullseye. Regards, kolAflash OpenPGP_signature Description: OpenPGP digital signature
Bug#974112: libkdecorations2-5v5: libkdecorations (5.19) seems wrong Plasma version (5.17.5) in Debian Bullseye, causes crashes
Here's a KDE bug about the same issue. It's been set to "RESOLVED DOWNSTREAM", linking to this Debian bug. But I used that KDE bug to post some detailed workaround instructions, which might be helpful to users. https://bugs.kde.org/show_bug.cgi?id=428897 signature.asc Description: OpenPGP digital signature
Bug#970877: hostapd with rt2800 not stable on Debian-10, but on Debian-11 (testing)
Package: hostapd Version: 2:2.7+git20190128+0c1e29f-6+deb10u2 Hi, I'm trying to use my new WLAN / Wi-Fi USB adapter via Debian-10 to set up an access point (master / ap /infrastructure mode). Sadly that doesn't work on Debian-10. After a few minutes the client is always disconnected with hostapd telling me: handle_probe_req: send failed On the other hand the device works great with Debian-11 (testing) and also openSUSE-15.2. I've tried using a backports Linux-5.7 kernel and I tried hostapd-2.9 (hostapd-2.9 compiled from source). None of both helped to solve the bug. So I'm actually not sure it's the fault of hostapd. But I just don't know what else could make the difference to Debian-11 (testing). So I'm opening this bug for hostapd. I've tested the USB device with different hosts. And even if Debian is being run inside Qemu it's always the same (regardless of the Qemu host os) I've even made positive and negative tests with Debian-10 and Debian-11 inside Qemu and the results are always the same. I attached the "hostapd -d ..." output as file. USB device details Brand: CSL Brand Model: 27395 Brand WDP No.: 300649 WEEE-Reg-No. DE 67896761 It's probably equivalent to the: Panda Wireless PAU09 (at least it looks exactly the same, except the labeling) https://deviwiki.com/wiki/Panda_Wireless_PAU09 https://wiki.debian.org/rt2800usb Chip: Ralink RT5572 Used driver: rt2800usb by Debian standard kernel hostapd -d -iwlan0 hostapd.conf interface=wlan0 ssid=a country_code=DE hw_mode=a channel=36 wpa=2 auth_algs=1 wpa_pairwise=CCMP wpa_key_mgmt=WPA-PSK wpa_passphrase=aa logger_stdout=-1 logger_stdout_level=2 I tested several variations of this. Including 2.4 GHz and 5 GHz modes. I just didn't test it without encryption. Interestingly I've had a very similar problem before with another USB WLAN adapter. ALFA Network AWUS036ACH - 802.11ac AC1200 It has no upstream driver, so I used aircrack-ng/rtl8812au Interestingly it showed very similar problems on Debian-10 and also works fine with Debian-11 (testing) and openSUSE-15.2. I've opened an issue for aircrack-ng/rtl8812au before. But after finding out that the bug only appears on Debian-10, I'm still trying to gather additional details. But I'm hoping it's maybe the same root cause as with the Ralink RT5572 adapter. https://github.com/aircrack-ng/rtl8812au/issues/695 Regards, kolAflash nl80211: BSS Event 59 (NL80211_CMD_FRAME) received for wlxdc4ef408653b nl80211: RX frame da=ff:ff:ff:ff:ff:ff sa=76:47:cd:a0:c3:b9 bssid=ff:ff:ff:ff:ff:ff freq=5180 ssi_signal=-58 fc=0x40 seq_ctrl=0x43a0 stype=4 (WLAN_FC_STYPE_PROBE_REQ) len=223 nl80211: send_mlme - da= 76:47:cd:a0:c3:b9 noack=0 freq=0 no_cck=0 offchanok=0 wait_time=0 fc=0x50 (WLAN_FC_STYPE_PROBE_RESP) nlmode=3 nl80211: send_mlme -> send_frame nl80211: send_frame - Use bss->freq=5180 nl80211: send_frame -> send_frame_cmd nl80211: Drop oldest pending send action cookie 0x1a nl80211: BSS Event 59 (NL80211_CMD_FRAME) received for wlxdc4ef408653b nl80211: RX frame da=ff:ff:ff:ff:ff:ff sa=76:47:cd:a0:c3:b9 bssid=ff:ff:ff:ff:ff:ff freq=5180 ssi_signal=-58 fc=0x40 seq_ctrl=0x43b0 stype=4 (WLAN_FC_STYPE_PROBE_REQ) len=214 nl80211: send_mlme - da= 76:47:cd:a0:c3:b9 noack=1 freq=0 no_cck=0 offchanok=0 wait_time=0 fc=0x50 (WLAN_FC_STYPE_PROBE_RESP) nlmode=3 nl80211: send_mlme -> send_frame nl80211: send_frame - Use bss->freq=5180 nl80211: send_frame -> send_frame_cmd nl80211: Drop oldest pending send action cookie 0x0 nl80211: Drv Event 60 (NL80211_CMD_FRAME_TX_STATUS) received for wlxdc4ef408653b nl80211: Frame TX status event wlxdc4ef408653b: Event TX_STATUS (16) received nl80211: BSS Event 59 (NL80211_CMD_FRAME) received for wlxdc4ef408653b nl80211: RX frame da=ff:ff:ff:ff:ff:ff sa=76:47:cd:a0:c3:b9 bssid=ff:ff:ff:ff:ff:ff freq=5180 ssi_signal=-50 fc=0x40 seq_ctrl=0x45a0 stype=4 (WLAN_FC_STYPE_PROBE_REQ) len=223 nl80211: send_mlme - da= 76:47:cd:a0:c3:b9 noack=0 freq=0 no_cck=0 offchanok=0 wait_time=0 fc=0x50 (WLAN_FC_STYPE_PROBE_RESP) nlmode=3 nl80211: send_mlme -> send_frame nl80211: send_frame - Use bss->freq=5180 nl80211: send_frame -> send_frame_cmd nl80211: Drop oldest pending send action cookie 0x1b nl80211: BSS Event 59 (NL80211_CMD_FRAME) received for wlxdc4ef408653b nl80211: RX frame da=ff:ff:ff:ff:ff:ff sa=76:47:cd:a0:c3:b9 bssid=ff:ff:ff:ff:ff:ff freq=5180 ssi_signal=-50 fc=0x40 seq_ctrl=0x45b0 stype=4 (WLAN_FC_STYPE_PROBE_REQ) len=214 nl80211: send_mlme - da= 76:47:cd:a0:c3:b9 noack=1 freq=0 no_cck=0 offchanok=0 wait_time=0 fc=0x50 (WLAN_FC_STYPE_PROBE_RESP) nlmode=3 nl80211: send_mlme -> send_frame nl80211: send_frame - Use bss->freq=5180 nl80211: send_frame -> send_frame_cmd nl80211: Drop oldest pending send action cookie 0x0 nl80211: Drv Event 60 (NL80211_CMD_FRAME_TX_STATUS) received for wlxdc4ef408653b nl80211: Frame TX status event wlxdc4ef408653b: Event TX_STATUS (16) received nl80211: Drv Event 20
Bug#960900: black screen after s2ram while 3D graphics (amdgpu - workaround: no_console_suspend)
Package: linux-image-amd64 Version: 5.6.7-1 Hi, I'm running KDE which uses 3d acceleration by default. If I activate standby (s2ram) via the KDE menu, the screen stays black after waking up from standby. dmesg looks like this is a bug in amdgpu / drm. Workaround: Disable 3d (ALT + SHIFT + F12) or boot with kernel parameter "no_console_suspend". Switching "no_console_suspend" via echo Y > /sys/module/printk/parameters/console_suspend also works. It's quite interesting that this helps, because "no_console_suspend" doesn't look like a switch to workaround bugs. https://www.kernel.org/doc/html/v5.6/admin-guide/kernel-parameters.html no_console_suspend [HW] Never suspend the console Disable suspending of consoles during suspend and hibernate operations. Once disabled, debugging messages can reach various consoles while the rest of the system is being put to sleep (ie, while debugging driver suspend/resume hooks). This may not work reliably with all consoles, but is known to work with serial and VGA consoles. To facilitate more flexible debugging, we also add console_suspend, a printk module parameter to control it. Users could use console_suspend (usually /sys/module/printk/parameters/console_suspend) to turn on/off it dynamically. Reproduction: The bug may only happen on the first standby after boot. So if the first standby was successful (e.g. because 3d was disabled) successive standby's may work fine. Reproduced with a live cd and an installed system (bullseye-20200511): debian-live-testing-amd64-kde+nonfree.iso Computer: HP EliteBook 735 G6 CPU + GPU: Ryzen 7 3700U (Vega 10) BIOS version: R74 Ver. 01.05.00 04/15/2020 Boot mode: EFI It's a little of a Heisenbug. After wakeup dmesg is immediately spammed with messages and I can't get up to the first error anymore. And if I run "dmesg -w > logfile" while s2ram, I won't be able to connect via ssh after wakeup and "logfile" will stop at standby. (even Alt+SysRq+B won't help) But issuing "sleep 2; dmesg -w > logfile" got me a useful result, which I attached to this email. Where I found the workarounds: https://bbs.archlinux.org/viewtopic.php?pid=1882244#p1882244 https://github.com/Pergravis?tab=projects Note: I didn't tried ArchLinux. But I couldn't reproduce with openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20200511-Media.iso So I'm not sure if it's maybe an upstream bug. Maybe related: https://bugs.freedesktop.org/show_bug.cgi?id=111244 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1842954 Regards, kolAflash [0.00] Linux version 5.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 (Debian 9.3.0-11)) #1 SMP Debian 5.6.7-1 (2020-04-29) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.6.0-1-amd64 root=UUID=a1a4ba2d-3695-4569-9fba-784ab5a194e3 ro quiet [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0008efff] usable [0.00] BIOS-e820: [mem 0x0008f000-0x0008] reserved [0.00] BIOS-e820: [mem 0x0009-0x0009] usable [0.00] BIOS-e820: [mem 0x0010-0x09ef] usable [0.00] BIOS-e820: [mem 0x09f0-0x09f0afff] ACPI NVS [0.00] BIOS-e820: [mem 0x09f0b000-0x381cefff] usable [0.00] BIOS-e820: [mem 0x381cf000-0x387cefff] type 20 [0.00] BIOS-e820: [mem 0x387cf000-0x38fcefff] reserved [0.00] BIOS-e820: [mem 0x38fcf000-0x396cefff] ACPI NVS [0.00] BIOS-e820: [mem 0x396cf000-0x3974efff] ACPI data [0.00] BIOS-e820: [mem 0x3974f000-0x5dff] usable [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [0.00] BIOS-e820: [mem 0xfd10-0xfd1f] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfec1-0xfec10fff] reserved [0.00] BIOS-e820: [mem 0xfed8-0xfed80fff] reserved [0.00] BIOS-e820: [mem 0xfedf1000-0xfedf1fff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00041f33] usable [0.00] NX (Execute Disable) protection: active [0.00] efi: EFI v2.60 by HP [0.00] efi:
Bug#945172: still a problem
I'm still having the same problem in the current Debian testing. Reproduced with a live cd and an installed system (bullseye-20200511): debian-live-testing-amd64-kde+nonfree.iso Package: firmware-realtek-20190717-2 It wasn't fun to find out what's wrong. So please fix this :-) Looks like kernel.org has that file in both places. Interestingly with two different sizes... https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/rtw88/rtw8822b_fw.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/rtlwifi/rtl8822befw.bin dlf29's workaround works for me too (also with a symlink instead of a hardlink). But I just replaced it with the rtw88 file from kernel.org which works fine too. Thanks, kolAflash signature.asc Description: OpenPGP digital signature
