June 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1187454] New: kernel: iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187454 Bug ID: 1187454 Summary: kernel: iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Booting kernel 5.3.18-59.5-default on a ThinkPad E15 (2nd Gen) I see this message: Jun 17 11:30:24 localhost kernel: iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver Jun 17 11:30:24 localhost kernel: iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.22 Jun 17 11:30:24 localhost kernel: iwlwifi 0000:03:00.0: Found debug destination: EXTERNAL_DRAM Jun 17 11:30:24 localhost kernel: iwlwifi 0000:03:00.0: Found debug configuration: 0 Jun 17 11:30:24 localhost kernel: iwlwifi 0000:03:00.0: loaded firmware version 55.d9698065.0 cc-a0-55.ucode op_mode iwlmvm # lspci -s 0000:03:00.0 -v 03:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) Subsystem: Intel Corporation Device 0080 Physical Slot: 0 Flags: bus master, fast devsel, latency 0, IRQ 65 Memory at fd400000 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi # hwinfo --wlan 01: PCI 300.0: 0282 WLAN controller [Created at pci.386] Unique ID: y9sn.mxT2IIe1w3C Parent ID: aYFK.YRmKDJrJI5E SysFS ID: /devices/pci0000:00/0000:00:02.3/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: network Model: "Intel Wi-Fi 6 AX200" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2723 "Wi-Fi 6 AX200" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x0080 Revision: 0x1a Driver: "iwlwifi" Driver Modules: "iwlwifi" Device File: wlan0 Features: WLAN Memory Range: 0xfd400000-0xfd403fff (rw,non-prefetchable) IRQ: 65 (no events) HW Address: 2e:13:53:c9:95:d5 Permanent HW Address: c0:3c:59:0a:80:7a Link detected: no WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 36 40 44 48 52 56 60 64 68 72 76 80 84 88 92 96 100 104 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.34 5.36 5.38 5.4 5.42 5.44 5.46 5.48 5.5 5.52 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v00008086d00002723sv00008086sd00000080bc02sc80i00" Driver Info #0: Driver Status: iwlwifi is active Driver Activation Cmd: "modprobe iwlwifi" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #9 (PCI bridge) -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1186896] New: AMD Rhyzen 7 4700H Renoir: brightness + ext screen don't work
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186896 Bug ID: 1186896 Summary: AMD Rhyzen 7 4700H Renoir: brightness + ext screen don't work Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)pohw.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ** Platform Info ** Distribution: Leap 15.2 Kernel: 5.3.18-lp152.75-default CPU: Rhyzen 7 4700U Graphics: # lspci -nnk | grep -A3 VGA 05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) Subsystem: CLEVO/KAPOK Computer Device [1558:a500] Symptom: Changing the brightness of the laptop screen doesn't work. Turning the scroll wheel over de battery icon in the system tray does't do anything. No change in brightness. But I do get the mmediate and unexplainable popup of the external monitor widget (see attachment). Peculiarly, the settings are correctly registered. Before: rietgors:/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.0/backlight/acpi_video0 # cat actual_brightness max_brightness 21 49 After: rietgors:/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.0/backlight/acpi_video0 # cat actual_brightness max_brightness 36 49 Exactly the same happens when I directly echo values in the "brightness" device from the command line. No change in brightness and immediate popup of the external monitor widget. Some information you might find useful: xlgears: Accellaratioin seems to work normally. xlgears gives me > 3200 fps. xgamma: value changes are properly registered: koos@rietgors:~> xgamma -rgamma 0.2 -ggamma 0.4 -bgamma 0.6 -> Red 1.000, Green 1.000, Blue 1.000 <- Red 0.200, Green 0.400, Blue 0.600 However no change in color whatsoever. xbacklight: Doesn't work. koos@rietgors:~> xbacklight -get No outputs have backlight property Next to the default Leap 15.2 kernel, I've tried the following kernels: - kernel-default-5.13.rc3/rc4 from KOTD - kernel-default-5.12.9 from the Kernel Stable repo However those kernels don't work at all. They hang hard during the boot process. If I select the Fail Safe option from the boot menu, they both hang at the following location in the boot screen (typed over from photo, see attachment): [drm] amdgpu kernel modesetting enabled. Virtual CRAT table created for CPU amdgpu: Topology: Add CPU node fb0: switching to amdgpudrmfb from EFI VGA -- You are receiving this mail because: You are the assignee for the bug.

1 25

[Bug 1187504] New: 'bcm2835-sdhost' breaks on kernel updates
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187504 Bug ID: 1187504 Summary: 'bcm2835-sdhost' breaks on kernel updates Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: scott.bradnick(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fresh install of Tumbleweed on Raspberry Pi 3 (Raspberry Pi 3 Model B Rev 1.2) is rendered unbootable after 1st kernel update. I went about my configuration when 5.12.9 was installed (20210609, I believe) and when "zypper dup" put 5.12.10 on it, it no longer booted (errors on HDMI console [about librt.so.1?]) and neither kernel would boot - each with different errors. I did a fresh install with the same .xz file copied to the SDcard and immediately did a zypper dup ; this time paying closer attention to the output. This caught my eye: dracut-install: Failed to find module 'bcm2835-sdhost' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.jqeBqi/initramfs -N i2o_scsi --kerneldir /lib/modules/5.12.9-1-default/ -m sdhci_iproc bcm2835-sdhost bcm2835_dma mmc_block dwc2 and it was printed for both kernels. So I removed "bcm2835-sdhost" from "/etc/dracut.conf.d/raspberrypi_modules.conf" and ran mkinitrd manually. That message wasn't printed and I'm able to boot into 5.12.10. I'm not sure what's to provide "bcm28350-sdhost" but it appears it isn't provided by default and that FAILED dracut-install then renders the system unbootable. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1186672] New: 1wire modules not built
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186672 Bug ID: 1186672 Summary: 1wire modules not built Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)1.opensuse.bgcomp.co.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Seems none of the 1wire modules have been built for x86_64, although they do appear to be available for aarch64. I seriously need them. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1187798] New: BTRFS Enhancement - Option for Swapfile instead of swap partition.
by bugzilla_noreply＠suse.com 04 Jul '21

04 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187798 Bug ID: 1187798 Summary: BTRFS Enhancement - Option for Swapfile instead of swap partition. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As you go through the opensuse installer when you get to partition options, it would be nice to have another choice...swapfile, especially if you want to use full disk space -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1186194] New: Many processes and up in D state after system resume (5.12.3-1-default, git 25d4ec7)
by bugzilla_noreply＠suse.com 01 Jul '21

01 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1186194 Bug ID: 1186194 Summary: Many processes and up in D state after system resume (5.12.3-1-default, git 25d4ec7) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de CC: oneukum(a)suse.com Found By: --- Blocker: --- Created attachment 849440 --> https://bugzilla.suse.com/attachment.cgi?id=849440&action=edit Output of SysRq-T I'm using a Dell laptop (Inspiron 7373) with a USB ethernet adapter (17ef:7205 Lenovo Thinkpad LAN, driver r8152). Sometimes, after resume, network-related utilities (e.g. ip, ping) freeze in D state. No communication over IP networks is possible. Attached is SysRq-T from the malfunctioning state. From my POV, the following stand out: May 18 11:00:34 fmn kernel: task:teams state:D stack: 0 pid: 316 ppid: 3234 flags:0x00000000 May 18 11:00:34 fmn kernel: Call Trace: May 18 11:00:34 fmn kernel: __schedule+0x2ee/0x950 May 18 11:00:34 fmn kernel: schedule+0x46/0xb0 May 18 11:00:34 fmn kernel: rpm_resume+0x19c/0x7b0 May 18 11:00:34 fmn kernel: ? wait_woken+0x80/0x80 May 18 11:00:34 fmn kernel: rpm_resume+0x2e7/0x7b0 May 18 11:00:34 fmn kernel: ? kernfs_fop_open+0x2a8/0x3a0 May 18 11:00:34 fmn kernel: __pm_runtime_resume+0x4a/0x80 May 18 11:00:34 fmn kernel: usb_autopm_get_interface+0x18/0x50 [usbcore] May 18 11:00:34 fmn kernel: rtl8152_get_link_ksettings+0x27/0x80 [r8152] May 18 11:00:34 fmn kernel: speed_show+0x6e/0xb0 May 18 11:00:34 fmn kernel: dev_attr_show+0x19/0x40 May 18 11:00:34 fmn kernel: sysfs_kf_seq_show+0xa6/0xe0 May 18 11:00:34 fmn kernel: seq_read_iter+0x1e1/0x510 May 18 11:00:34 fmn kernel: new_sync_read+0x115/0x1a0 May 18 11:00:34 fmn kernel: vfs_read+0x14b/0x1a0 May 18 11:00:34 fmn kernel: ksys_read+0x5f/0xe0 May 18 11:00:34 fmn kernel: do_syscall_64+0x33/0x80 May 18 11:00:34 fmn kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae AND May 18 11:00:34 fmn kernel: task:kworker/3:2 state:D stack: 0 pid:23489 ppid: 2 flags:0x00004000 May 18 11:00:34 fmn kernel: Workqueue: pm pm_runtime_work May 18 11:00:34 fmn kernel: Call Trace: May 18 11:00:34 fmn kernel: __schedule+0x2ee/0x950 May 18 11:00:34 fmn kernel: schedule+0x46/0xb0 May 18 11:00:34 fmn kernel: schedule_timeout+0x8b/0x140 May 18 11:00:34 fmn kernel: ? __next_timer_interrupt+0x100/0x100 May 18 11:00:34 fmn kernel: msleep+0x2a/0x40 May 18 11:00:34 fmn kernel: napi_disable+0x2b/0x70 May 18 11:00:34 fmn kernel: rtl8152_suspend+0x2ad/0x340 [r8152] May 18 11:00:34 fmn kernel: usb_suspend_both+0x9d/0x230 [usbcore] May 18 11:00:34 fmn kernel: usb_runtime_suspend+0x2b/0x70 [usbcore] May 18 11:00:34 fmn kernel: ? usb_autoresume_device+0x50/0x50 [usbcore] May 18 11:00:34 fmn kernel: __rpm_callback+0x81/0x140 May 18 11:00:34 fmn kernel: rpm_callback+0x4f/0x70 May 18 11:00:34 fmn kernel: ? usb_autoresume_device+0x50/0x50 [usbcore] May 18 11:00:34 fmn kernel: rpm_suspend+0x147/0x6f0 May 18 11:00:34 fmn kernel: ? __switch_to+0x26f/0x450 May 18 11:00:34 fmn kernel: pm_runtime_work+0x8e/0x90 May 18 11:00:34 fmn kernel: process_one_work+0x1df/0x370 May 18 11:00:34 fmn kernel: worker_thread+0x50/0x400 May 18 11:00:34 fmn kernel: ? process_one_work+0x370/0x370 May 18 11:00:34 fmn kernel: kthread+0x11b/0x140 May 18 11:00:34 fmn kernel: ? __kthread_bind_mask+0x60/0x60 May 18 11:00:34 fmn kernel: ret_from_fork+0x22/0x30 -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 1137748] suspend to RAM no longer working after upgrade to Leap 15.1
by bugzilla_noreply＠suse.com 30 Jun '21

30 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1137748 http://bugzilla.opensuse.org/show_bug.cgi?id=1137748#c134 Frank Morawietz <nestolea(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(biswarupr(a)gmail.c | |om) --- Comment #134 from Frank Morawietz <nestolea(a)gmail.com> --- (In reply to Biswarup Ray from comment #133) > Today I booted the GeckoLinux_ROLLING_Cinnamon.x86_64-999.210526.0.iso which > is based on Tumbleweed, using a pen drive and was surprised to find that > suspend to ram is working fine. Which Kernel version was this? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186889] RTL8822CE Wi-Fi Bluetooth Combo Module Driver
by bugzilla_noreply＠suse.com 30 Jun '21

30 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186889 http://bugzilla.opensuse.org/show_bug.cgi?id=1186889#c32 --- Comment #32 from Ibrahim ERTURK <ierturk(a)ieee.org> --- (In reply to Larry Finger from comment #31) > If the system has no support for ASPM, then the option disable_aspm=y should > be required for rtw88. > > It seems that your BIOS is just plain funky. Is there an update? The BIOS version is the latest. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186889] New: RTL8822CE Wi-Fi Bluetooth Combo Module Driver
by bugzilla_noreply＠suse.com 30 Jun '21

30 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186889 Bug ID: 1186889 Summary: RTL8822CE Wi-Fi Bluetooth Combo Module Driver Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ierturk(a)ieee.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, The link of the the discussion on openSUSE forum regarding this bug is below. https://forums.opensuse.org/showthread.php/554865-RTL8822CE-Wi-Fi-Bluetooth… On the HP Laptop 15-da2xxx with RTL8822CE, there is no problem with Wi-Fi, but the openSUSE Leap 15.3 and Tumbleweed could not found BlueTooth module. I've tried a few solution and some other Linux distros, but not succeeded so far. The module works properly with Windows 10 x64. You can find some reports from command-line below. $ lsmod | grep rtw rtw_8822ce 16384 0 rtw_8822c 483328 1 rtw_8822ce rtw_pci 28672 1 rtw_8822ce rtw_core 221184 2 rtw_8822c,rtw_pci mac80211 1028096 2 rtw_core,rtw_pci cfg80211 872448 2 rtw_core,mac80211 $ uname -a Linux localhost.localdomain 5.3.18-57-default #1 SMP Wed Apr 28 10:54:41 UTC 2021 (ba3c2e9) x86_64 x86_64 x86_64 GNU/Linux $ lspci -nnk | grep -EiA3 'net|real' 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Hewlett-Packard Company Device [103c:86b4] Kernel driver in use: r8169 Kernel modules: r8169 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter [10ec:c822] Subsystem: Hewlett-Packard Company Device [103c:85f7] Kernel driver in use: rtw_8822ce Kernel modules: rtw88_8822ce, rtw_8822ce $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ sudo rfkill list all 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo dmesg | grep rtw [ 6.574405] rtw88_8822ce: disagrees about version of symbol rtw8822c_hw_spec [ 6.574406] rtw88_8822ce: Unknown symbol rtw8822c_hw_spec (err -22) [ 6.671156] rtw_8822ce 0000:03:00.0: enabling device (0000 -> 0003) [ 6.675069] rtw_8822ce 0000:03:00.0: Firmware version 9.9.10, H2C version 15 [ 6.697257] rtw_8822ce 0000:03:00.0: use rfe_def[1] [ 6.698841] rtw_8822ce 0000:03:00.0: Firmware version 9.9.4, H2C version 15 [ 8.376754] rtw_8822ce 0000:03:00.0: start vif c0:e4:34:dd:56:8d on port 0 [ 8.378394] rtw_8822ce 0000:03:00.0: stop vif c0:e4:34:dd:56:8d on port 0 [ 8.638466] rtw_8822ce 0000:03:00.0: start vif b6:8c:72:02:c5:86 on port 0 [ 16.830954] rtw_8822ce 0000:03:00.0: stop vif b6:8c:72:02:c5:86 on port 0 [ 17.094304] rtw_8822ce 0000:03:00.0: start vif c0:e4:34:dd:56:8d on port 0 [ 17.115654] rtw_8822ce 0000:03:00.0: stop vif c0:e4:34:dd:56:8d on port 0 [ 17.385296] rtw_8822ce 0000:03:00.0: start vif ba:4a:12:52:90:29 on port 0 [ 21.536673] rtw_8822ce 0000:03:00.0: stop vif ba:4a:12:52:90:29 on port 0 [ 21.798405] rtw_8822ce 0000:03:00.0: start vif c0:e4:34:dd:56:8d on port 0 [ 26.437421] rtw_8822ce 0000:03:00.0: sta d0:6f:82:61:c2:17 joined with macid 0 -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1187874] New: Kernel hwmon modules nct6775 no longer fully recognioses chip
by bugzilla_noreply＠suse.com 30 Jun '21

30 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187874 Bug ID: 1187874 Summary: Kernel hwmon modules nct6775 no longer fully recognioses chip Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)1.opensuse.bgcomp.co.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With opensuse 15.2, the nct6775 chip was recognise and the sensor command would print details of its sensors. This no longer happens with 15.3. Running sensors-detect, the chip is not recognised, but is when the the module is loaded, although it's sensors are still not listed. The output 15.2 when the module is loaded is: 2021-03-01T19:22:02.900605+00:00 ns2 kernel: [ 7.237799] nct6775: Enabling hardware monitor logical device mappings. 2021-03-01T19:22:02.900605+00:00 ns2 kernel: [ 7.237809] nct6775: Found NCT6791D or compatible chip at 0x2e:0x290 2021-03-01T19:22:02.900605+00:00 ns2 kernel: [ 7.237814] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\_GPE.HWM) (20190703/utaddress-213) 2021-03-01T19:22:02.900605+00:00 ns2 kernel: [ 7.237818] ACPI: This conflict may cause random problems and system instability 2021-03-01T19:22:02.900605+00:00 ns2 kernel: [ 7.237819] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver while the output from 15.3 is: 2021-06-02T11:53:24.172296+01:00 ns2 kernel: nct6775: Enabling hardware monitor logical device mappings. 2021-06-02T11:53:24.172369+01:00 ns2 kernel: nct6775: Found NCT6791D or compatible chip at 0x2e:0x290 2021-06-02T11:53:24.172408+01:00 ns2 kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\_GPE.HWM) (20200925/utaddress-213) 2021-06-02T11:53:24.172447+01:00 ns2 kernel: ACPI: This conflict may cause random problems and system instability 2021-06-02T11:53:24.172480+01:00 ns2 kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver The only difference between the 2 outputs are with the ACPI systemIO range, but that seems to be date related, 20200925 vs 20190703. This is on an Asus Z97I-Plus with the output of lscpu: localhost:/usr/local # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz Stepping: 3 CPU MHz: 3401.785 CPU max MHz: 3600.0000 CPU min MHz: 800.0000 BogoMIPS: 7195.92 Virtualization: VT-x L1d cache: 64 KiB L1i cache: 64 KiB L2 cache: 512 KiB L3 cache: 3 MiB NUMA node0 CPU(s): 0-3 Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling Vulnerability Srbds: Mitigation; Microcode Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulq dq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpi d ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm arat pln pts md_clear flush_l1d uname: Linux localhost 5.3.18-59.5-default #1 SMP Wed Jun 2 08:21:36 UTC 2021 (eaf040d) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are the assignee for the bug.

1 2