[BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Hi Ping-Ke,

I am writing to formally report a critical bug that causes a hard
system freeze on laptops equipped with the RTL8821CE WiFi module, and
to propose solutions.

Description:
On an HP laptop equipped with a Realtek RTL8821CE 802.11ac PCIe
adapter (PCI ID: 10ec:c821), the system experiences a hard lockup
(complete freeze of the UI and kernel, sysrq doesn't work, requires
holding the power button) when the WiFi adapter enters the power
saving state.

This issue occurs consistently across multiple Linux distributions and
kernel versions (reproduced on upstream kernel 6.13 and 6.19-rc).

Steps to Reproduce:
1. Use a system with RTL8821CE (pci:10ec:c821).
2. Ensure NetworkManager is configured with wifi.powersave = 3 (or
power saving is enabled via TLP/iw).
3. Connect to a WiFi network and let the system idle.
4. The system will eventually freeze completely.

Workarounds that successfully prevent the freeze:
* Passing disable_lps_deep=y to rtw88_core.
* Passing disable_aspm=y to rtw88_pci (or pcie_aspm=off).
* Disabling WiFi power save via NetworkManager.

Technical Analysis:
The root cause appears to be an unhandled race condition or hardware
bug between the adapter's Low Power State (LPS) Deep mode
(LPS_DEEP_MODE_LCLK) and the PCIe Active State Power Management (ASPM
L1) mechanism.

When the firmware drops into LPS_DEEP_MODE_LCLK concurrently with the
PCIe bus entering ASPM L1, the chip fails to handle PCIe Wake
signaling correctly. While there is an existing workaround in
rtw_pci_napi_poll (pci.c:1806) that sets `rtwpci->rx_no_aspm = true`
during NAPI poll for 8821CE, this polling wrapper is insufficient. The
deadlock often occurs during idle states when polling isn't actively
disabling ASPM, but the system suddenly needs to wake the radio.

Proposed Solutions:
Given that LPS_DEEP_MODE_LCLK seems fundamentally unreliable on 8821ce
PCIe variants when paired with standard Windows-era ASPM
implementations on laptops (HP, Lenovo, ASUS are all affected), the
most robust solution is to strip the unsupported deep sleep flag from
the hardware spec.

```diff
--- a/drivers/net/wireless/realtek/rtw88/rtw8821c.c
+++ b/drivers/net/wireless/realtek/rtw88/rtw8821c.c
@@ -1999,7 +1999,7 @@ struct rtw_chip_info rtw8821c_hw_spec = {
.bt_supported = true,
.fbtc_has_ext_ctrl = true,
.coex_info_hw_supported = true,
- .lps_deep_mode_supported = BIT(LPS_DEEP_MODE_LCLK),
+ .lps_deep_mode_supported = 0, /* Disabled due to ASPM L1 hard locks */
.dpk_supported = true,
.pstdma_type = COEX_PSTDMA_FORCE_LPSOFF,
.bfee_support = false,
```

Alternatively, a PCI Subsystem-based quirk should be introduced in
rtw_pci_aspm_set() to refuse ASPM BIT_L1_SW_EN transitions for
affected hardware IDs, similar to how CLKREQ issues are handled for
8822C via efuse->rfe_option.

Cross-Reference Analysis of other RTL8821CE Bugs:
After aggregating recent open bug reports for the 8821ce chip on
Bugzilla (https://bugzilla.kernel.org), it is apparent that almost all
of them are victims of the exact same underlying race condition.
1. Bug 215131: System freeze preceded by 'pci bus timeout, check dma
status'. Workaround used: disable_aspm=1.
2. Bug 219830: Log shows 'firmware failed to leave lps state' and
'failed to send h2c command'. A direct smoking gun for LPS Deep mode
freezing.
3. Bug 218697 & Bug 217491: Endless 'timed out to flush queue' floods.
4. Bug 217781 & Bug 216685: Random dropouts and low wireless speed.

Given the volume and age of these unresolved reports, disabling
.lps_deep_mode_supported (or restricting ASPM L1) specifically for
10ec:c821 is desperately needed.

System Information:
- Hardware: HP Notebook (SKU: P3S95EA#ACB, Family: 103C_5335KV)
- CPU: Intel Core i3-5005U
- WiFi PCI ID: 10ec:c821, Subsystem: 103c:831a
- Kernel: 6.13 / 6.19
- Driver module: rtw88_8821ce

I am happy to test any patches provided or formally submit the patch
above if maintainers agree it is the right approach. Thank you!

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> Hi Ping-Ke,
> 
> I am writing to formally report a critical bug that causes a hard
> system freeze on laptops equipped with the RTL8821CE WiFi module, and
> to propose solutions.
> 
> Description:
> On an HP laptop equipped with a Realtek RTL8821CE 802.11ac PCIe
> adapter (PCI ID: 10ec:c821), the system experiences a hard lockup
> (complete freeze of the UI and kernel, sysrq doesn't work, requires
> holding the power button) when the WiFi adapter enters the power
> saving state.
> 
> This issue occurs consistently across multiple Linux distributions and
> kernel versions (reproduced on upstream kernel 6.13 and 6.19-rc).
> 
> Steps to Reproduce:
> 1. Use a system with RTL8821CE (pci:10ec:c821).
> 2. Ensure NetworkManager is configured with wifi.powersave = 3 (or
> power saving is enabled via TLP/iw).
> 3. Connect to a WiFi network and let the system idle.
> 4. The system will eventually freeze completely.

Can you dig kernel log (by netconsole or ramoops) if something useful?
I'd like to know this is hardware level freeze or kernel can capture
something wrong. 

> 
> Workarounds that successfully prevent the freeze:
> * Passing disable_lps_deep=y to rtw88_core.
> * Passing disable_aspm=y to rtw88_pci (or pcie_aspm=off).
> * Disabling WiFi power save via NetworkManager.

Are these totally needed to workaround the problem? Or disable_aspm is
enough?

I'd list them in order of power consumption impact: (the topmost is lower impact)
  1. disable_aspm=y
  2. disable_lps_deep=y
  3. disable WiFi power save

If you can do experiments on your platform, we can be easier to decide
which workarounds are adopted.

> 
> Technical Analysis:
> The root cause appears to be an unhandled race condition or hardware
> bug between the adapter's Low Power State (LPS) Deep mode
> (LPS_DEEP_MODE_LCLK) and the PCIe Active State Power Management (ASPM
> L1) mechanism.
> 
> When the firmware drops into LPS_DEEP_MODE_LCLK concurrently with the
> PCIe bus entering ASPM L1, the chip fails to handle PCIe Wake
> signaling correctly. While there is an existing workaround in
> rtw_pci_napi_poll (pci.c:1806) that sets `rtwpci->rx_no_aspm = true`
> during NAPI poll for 8821CE, this polling wrapper is insufficient. The
> deadlock often occurs during idle states when polling isn't actively
> disabling ASPM, but the system suddenly needs to wake the radio.

`rtwpci->rx_no_aspm = true` was another workaround years ago on certain
platform. I'd say ASPM has many interoperability problems, even years ago.

But what does 'deadlock' mean? As I know NAPI poll is scheduled by ISR,
and going to receive packets. The rx_no_aspm workaround is to forcely turn
off ASPM during this period. 

> 
> Proposed Solutions:
> Given that LPS_DEEP_MODE_LCLK seems fundamentally unreliable on 8821ce
> PCIe variants when paired with standard Windows-era ASPM
> implementations on laptops (HP, Lenovo, ASUS are all affected), the
> most robust solution is to strip the unsupported deep sleep flag from
> the hardware spec.
> 
> ```diff
> --- a/drivers/net/wireless/realtek/rtw88/rtw8821c.c
> +++ b/drivers/net/wireless/realtek/rtw88/rtw8821c.c
> @@ -1999,7 +1999,7 @@ struct rtw_chip_info rtw8821c_hw_spec = {
> .bt_supported = true,
> .fbtc_has_ext_ctrl = true,
> .coex_info_hw_supported = true,
> - .lps_deep_mode_supported = BIT(LPS_DEEP_MODE_LCLK),
> + .lps_deep_mode_supported = 0, /* Disabled due to ASPM L1 hard locks */
> .dpk_supported = true,
> .pstdma_type = COEX_PSTDMA_FORCE_LPSOFF,
> .bfee_support = false,
> ```
> 
> Alternatively, a PCI Subsystem-based quirk should be introduced in
> rtw_pci_aspm_set() to refuse ASPM BIT_L1_SW_EN transitions for
> affected hardware IDs, similar to how CLKREQ issues are handled for
> 8822C via efuse->rfe_option.

I'd add a quirk to your platforms, so other platforms can still have
better power consumption. 

> 
> Cross-Reference Analysis of other RTL8821CE Bugs:
> After aggregating recent open bug reports for the 8821ce chip on
> Bugzilla (https://bugzilla.kernel.org), it is apparent that almost all
> of them are victims of the exact same underlying race condition.
> 1. Bug 215131: System freeze preceded by 'pci bus timeout, check dma
> status'. Workaround used: disable_aspm=1.
> 2. Bug 219830: Log shows 'firmware failed to leave lps state' and
> 'failed to send h2c command'. A direct smoking gun for LPS Deep mode
> freezing.
> 3. Bug 218697 & Bug 217491: Endless 'timed out to flush queue' floods.
> 4. Bug 217781 & Bug 216685: Random dropouts and low wireless speed.
> 
> Given the volume and age of these unresolved reports, disabling
> .lps_deep_mode_supported (or restricting ASPM L1) specifically for
> 10ec:c821 is desperately needed.
> 
> System Information:
> - Hardware: HP Notebook (SKU: P3S95EA#ACB, Family: 103C_5335KV)
> - CPU: Intel Core i3-5005U
> - WiFi PCI ID: 10ec:c821, Subsystem: 103c:831a
> - Kernel: 6.13 / 6.19
> - Driver module: rtw88_8821ce
> 
> I am happy to test any patches provided or formally submit the patch
> above if maintainers agree it is the right approach. Thank you!

We have not modified RTL8821CE for a long time, so I'd add workaround
to specific platform as mentioned above. 

Ping-Ke

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Hi Ping-Ke,

Thank you for the incredibly fast response and assistance!

> Can you dig kernel log (by netconsole or ramoops) if something useful?
> I'd like to know this is hardware level freeze or kernel can capture something wrong.

I managed to pull a call trace from a historic journald log just
before the system hung. The kernel gets trapped in an IRQ thread
inside `rtw_pci_interrupt_threadfn`, calling up into `mac80211`
`ieee80211_rx_list` before everything freezes. Here is the relevant
snippet:

```text
Call Trace:
<IRQ>
? __alloc_skb+0x23a/0x2a0
? __alloc_skb+0x10c/0x2a0
? __pfx_irq_thread_fn+0x10/0x10
[ ... truncated module list ... ]
Tainted: G W I 6.19.6-2-cachyos #1 PREEMPT(full)
Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
RIP: 0010:ieee80211_rx_list+0x1012/0x1020 [mac80211]
CPU: 2 UID: 0 PID: 765 Comm: irq/56-rtw88_pc
rtw_pci_interrupt_threadfn+0x239/0x310 [rtw88_pci]
```

It behaves exactly like a PCIe bus deadlock or a hardware fault that
eventually brings down the CPU handling the IRQ.

> Are these totally needed to workaround the problem? Or disable_aspm is enough?
> I'd list them in order of power consumption impact:
> 1. disable_aspm=y
> 2. disable_lps_deep=y
> 3. disable WiFi power save

To verify which parameters are strictly necessary, I performed
isolated testing today. I ensured no other modprobe configs were
active, rebuilt the initramfs, and manually enforced that
`wifi.powersave` was active via `iw dev wlan0 set power_save on`
during all tests (as the OS power management profiles were defaulting
it to off, which initially masked the issue).

I tested each workaround individually across multiple sleep/wake
cycles and active usage:

**Test 1 (ASPM Disabled, LPS Deep Enabled):**
- Kernel parameters: `rtw88_pci disable_aspm=y` (and `rtw88_core
disable_lps_deep=n`)
- Result: Stable. No freezes were observed during usage or transitions
into/out of S3 sleep while power saving was enforced.

**Test 2 (ASPM Enabled, LPS Deep Disabled):**
- Kernel parameters: `rtw88_core disable_lps_deep=y` (and `rtw88_pci
disable_aspm=n`)
- Result: Stable. No freezes were observed under the same forced power
save conditions.

**Conclusion:** It appears we do not need both workarounds
simultaneously for this specific hardware. Using only `disable_aspm=y`
seems to be sufficient to prevent the system freeze. Given your note
about the power consumption impact ranking, this looks like the
optimal path forward.

> But what does 'deadlock' mean? As I know NAPI poll is scheduled by ISR,
> and going to receive packets. The rx_no_aspm workaround is to forcely turn
> off ASPM during this period.

By "deadlock" I meant a hardware-level bus lockup. It seems the
physical RTL8821CE chip itself crashes or hangs the system's PCIe bus
when trying to negotiate waking up from ASPM L1 while simultaneously
existing in `LPS_DEEP_MODE_LCLK`. The `rx_no_aspm` workaround in NAPI
helps during active Rx decoding, but the laptop often freezes while
completely idle, presumably when the AP sends a basic beacon, the chip
attempts to leave LPS Deep + L1, and the hardware simply gives up and
halts the system.

> We have not modified RTL8821CE for a long time, so I'd add workaround
> to specific platform as mentioned above.

Adding a DMI/platform quirk specifically for this laptop to disable
ASPM would be wonderful and deeply appreciated. I agree it is safer
than touching the global flags for hardware that is functioning
correctly out in the wild.

Here is the exact identifying information for my system:

System Vendor: HP
Product Name: HP Notebook
SKU Number: P3S95EA#ACB
Family: 103C_5335KV
PCI ID: 10ec:c821
Subsystem ID: 103c:831a

I am completely ready to test any patch or quirk you send my way.
Thank you so much for your time and helping track this down!

Best regards,
Oleksandr

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Hi Ping-Ke,

Thank you for your guidance. To provide you with the cleanest possible
diagnostic data, we devised a strict testing environment:

1. **Live USB Environment:** We booted a completely fresh Live USB of
CachyOS (Kernel 6.19.6) to eliminate any potential interference from
installed software, TLP profiles, or custom NetworkManager
configurations.
2. **Aggressive Local Logging:** Because the system freeze physically
locks the PCIe bus and disables the Wi-Fi adapter instantly, using
`netconsole` was impossible (the network drops microseconds before the
freeze).

To overcome this, we wrote an "aggressive logger" script that pipes
`dmesg -w` directly to an independent FAT32 USB drive while issuing a
`sync` command twice a second. This bypassed RAM caching and
physically burned the logs to the drive right up to the moment of the
hard freeze. The script we used was:

```bash
#!/bin/bash
LOG_FILE="/run/media/liveuser/LOGS/kernel_freeze.log"
dmesg -w > "$LOG_FILE" &
while true; do
    sync
    sleep 0.5
done
```

3. No workarounds (`disable_aspm=n`, `disable_lps_deep=n`) were active
in this test. We manually enabled power saving (`iw dev wlan0 set
power_save on`) and triggered the freeze via typical web browsing.

Here are the precise, unadulterated logs showing the adapter
successfully connecting to the network, sitting idle for about 10
seconds (presumably entering power-saving states), and then suffering
a fatal firmware lockup right before the PCIe bus froze:

```
[  304.709201] audit: type=1111 ... op=connection-add-activate ...
name="Andrey_5G" ...
[  305.617785] wlan0: authenticate with 6c:68:a4:1c:97:5b ...
[  305.660333] wlan0: authenticated
[  305.661661] wlan0: associate with 6c:68:a4:1c:97:5b (try 1/3)
[  305.663404] wlan0: associated
[  305.719997] wlan0: Limiting TX power to 30 (30 - 0) dBm as
advertised by 6c:68:a4:1c:97:5b
... (~10 seconds of idle network time) ...
[  316.907114] rtw88_8821ce 0000:13:00.0: failed to send h2c command
[  316.911190] rtw88_8821ce 0000:13:00.0: failed to send h2c command
[  316.921504] rtw88_8821ce 0000:13:00.0: coex request time out
...
[  349.630952] rtw88_8821ce 0000:13:00.0: failed to send h2c command
[  349.635023] rtw88_8821ce 0000:13:00.0: failed to send h2c command
[  357.811235] rtw88_8821ce 0000:13:00.0: firmware failed to leave lps state
[  359.797238] rtw88_8821ce 0000:13:00.0: firmware failed to leave lps state
... (repeats indefinitely until hard reset) ...
```

As the logs clearly demonstrate, the adapter authenticates perfectly
but the firmware explicitly fails to leave the LPS state after a brief
idle period, dropping all H2C commands immediately before the
system-wide hard freeze begins.

We will upload the full, unabridged `.log` file to our Bugzilla thread
(Bug 221195) momentarily, but we wanted to provide you with this exact
'smoking gun' trace right away to help identify the root cause.

Please let us know if this information is helpful or if there are any
specific module patches or further tests you would like us to perform
to assist with debugging.

Best regards,
Oleksandr

вт, 10 мар. 2026 г. в 13:01, LB F <goainwo@gmail.com>:
>
> Hi Ping-Ke,
>
> Thank you for the incredibly fast response and assistance!
>
> > Can you dig kernel log (by netconsole or ramoops) if something useful?
> > I'd like to know this is hardware level freeze or kernel can capture something wrong.
>
> I managed to pull a call trace from a historic journald log just
> before the system hung. The kernel gets trapped in an IRQ thread
> inside `rtw_pci_interrupt_threadfn`, calling up into `mac80211`
> `ieee80211_rx_list` before everything freezes. Here is the relevant
> snippet:
>
> ```text
> Call Trace:
> <IRQ>
> ? __alloc_skb+0x23a/0x2a0
> ? __alloc_skb+0x10c/0x2a0
> ? __pfx_irq_thread_fn+0x10/0x10
> [ ... truncated module list ... ]
> Tainted: G W I 6.19.6-2-cachyos #1 PREEMPT(full)
> Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
> RIP: 0010:ieee80211_rx_list+0x1012/0x1020 [mac80211]
> CPU: 2 UID: 0 PID: 765 Comm: irq/56-rtw88_pc
> rtw_pci_interrupt_threadfn+0x239/0x310 [rtw88_pci]
> ```
>
> It behaves exactly like a PCIe bus deadlock or a hardware fault that
> eventually brings down the CPU handling the IRQ.
>
> > Are these totally needed to workaround the problem? Or disable_aspm is enough?
> > I'd list them in order of power consumption impact:
> > 1. disable_aspm=y
> > 2. disable_lps_deep=y
> > 3. disable WiFi power save
>
> To verify which parameters are strictly necessary, I performed
> isolated testing today. I ensured no other modprobe configs were
> active, rebuilt the initramfs, and manually enforced that
> `wifi.powersave` was active via `iw dev wlan0 set power_save on`
> during all tests (as the OS power management profiles were defaulting
> it to off, which initially masked the issue).
>
> I tested each workaround individually across multiple sleep/wake
> cycles and active usage:
>
> **Test 1 (ASPM Disabled, LPS Deep Enabled):**
> - Kernel parameters: `rtw88_pci disable_aspm=y` (and `rtw88_core
> disable_lps_deep=n`)
> - Result: Stable. No freezes were observed during usage or transitions
> into/out of S3 sleep while power saving was enforced.
>
> **Test 2 (ASPM Enabled, LPS Deep Disabled):**
> - Kernel parameters: `rtw88_core disable_lps_deep=y` (and `rtw88_pci
> disable_aspm=n`)
> - Result: Stable. No freezes were observed under the same forced power
> save conditions.
>
> **Conclusion:** It appears we do not need both workarounds
> simultaneously for this specific hardware. Using only `disable_aspm=y`
> seems to be sufficient to prevent the system freeze. Given your note
> about the power consumption impact ranking, this looks like the
> optimal path forward.
>
> > But what does 'deadlock' mean? As I know NAPI poll is scheduled by ISR,
> > and going to receive packets. The rx_no_aspm workaround is to forcely turn
> > off ASPM during this period.
>
> By "deadlock" I meant a hardware-level bus lockup. It seems the
> physical RTL8821CE chip itself crashes or hangs the system's PCIe bus
> when trying to negotiate waking up from ASPM L1 while simultaneously
> existing in `LPS_DEEP_MODE_LCLK`. The `rx_no_aspm` workaround in NAPI
> helps during active Rx decoding, but the laptop often freezes while
> completely idle, presumably when the AP sends a basic beacon, the chip
> attempts to leave LPS Deep + L1, and the hardware simply gives up and
> halts the system.
>
> > We have not modified RTL8821CE for a long time, so I'd add workaround
> > to specific platform as mentioned above.
>
> Adding a DMI/platform quirk specifically for this laptop to disable
> ASPM would be wonderful and deeply appreciated. I agree it is safer
> than touching the global flags for hardware that is functioning
> correctly out in the wild.
>
> Here is the exact identifying information for my system:
>
> System Vendor: HP
> Product Name: HP Notebook
> SKU Number: P3S95EA#ACB
> Family: 103C_5335KV
> PCI ID: 10ec:c821
> Subsystem ID: 103c:831a
>
> I am completely ready to test any patch or quirk you send my way.
> Thank you so much for your time and helping track this down!
>
> Best regards,
> Oleksandr

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> 
> Hi Ping-Ke,
> 
> Thank you for your guidance. To provide you with the cleanest possible
> diagnostic data, we devised a strict testing environment:
> 
> 1. **Live USB Environment:** We booted a completely fresh Live USB of
> CachyOS (Kernel 6.19.6) to eliminate any potential interference from
> installed software, TLP profiles, or custom NetworkManager
> configurations.
> 2. **Aggressive Local Logging:** Because the system freeze physically
> locks the PCIe bus and disables the Wi-Fi adapter instantly, using
> `netconsole` was impossible (the network drops microseconds before the
> freeze).
> 
> To overcome this, we wrote an "aggressive logger" script that pipes
> `dmesg -w` directly to an independent FAT32 USB drive while issuing a
> `sync` command twice a second. This bypassed RAM caching and
> physically burned the logs to the drive right up to the moment of the
> hard freeze. The script we used was:
> 
> ```bash
> #!/bin/bash
> LOG_FILE="/run/media/liveuser/LOGS/kernel_freeze.log"
> dmesg -w > "$LOG_FILE" &
> while true; do
>     sync
>     sleep 0.5
> done
> ```
> 
> 3. No workarounds (`disable_aspm=n`, `disable_lps_deep=n`) were active
> in this test. We manually enabled power saving (`iw dev wlan0 set
> power_save on`) and triggered the freeze via typical web browsing.
> 
> Here are the precise, unadulterated logs showing the adapter
> successfully connecting to the network, sitting idle for about 10
> seconds (presumably entering power-saving states), and then suffering
> a fatal firmware lockup right before the PCIe bus froze:
> 
> ```
> [  304.709201] audit: type=1111 ... op=connection-add-activate ...
> name="Andrey_5G" ...
> [  305.617785] wlan0: authenticate with 6c:68:a4:1c:97:5b ...
> [  305.660333] wlan0: authenticated
> [  305.661661] wlan0: associate with 6c:68:a4:1c:97:5b (try 1/3)
> [  305.663404] wlan0: associated
> [  305.719997] wlan0: Limiting TX power to 30 (30 - 0) dBm as
> advertised by 6c:68:a4:1c:97:5b
> ... (~10 seconds of idle network time) ...
> [  316.907114] rtw88_8821ce 0000:13:00.0: failed to send h2c command
> [  316.911190] rtw88_8821ce 0000:13:00.0: failed to send h2c command
> [  316.921504] rtw88_8821ce 0000:13:00.0: coex request time out
> ...
> [  349.630952] rtw88_8821ce 0000:13:00.0: failed to send h2c command
> [  349.635023] rtw88_8821ce 0000:13:00.0: failed to send h2c command
> [  357.811235] rtw88_8821ce 0000:13:00.0: firmware failed to leave lps state
> [  359.797238] rtw88_8821ce 0000:13:00.0: firmware failed to leave lps state
> ... (repeats indefinitely until hard reset) ...
> ```

Just want to clarify that these logs only appear in test 3, right?
No these logs in test 1/2. 

> 
> As the logs clearly demonstrate, the adapter authenticates perfectly
> but the firmware explicitly fails to leave the LPS state after a brief
> idle period, dropping all H2C commands immediately before the
> system-wide hard freeze begins.
> 
> We will upload the full, unabridged `.log` file to our Bugzilla thread
> (Bug 221195) momentarily, but we wanted to provide you with this exact
> 'smoking gun' trace right away to help identify the root cause.
> 
> Please let us know if this information is helpful or if there are any
> specific module patches or further tests you would like us to perform
> to assist with debugging.

Thanks for your detail tests and logs. With this kind of hardware problem,
to dig the cause, we need real hardware and hardware scope to measure
signals. I'd apply quirk or some validations on RX path. That'd be a
better way.

Ping-Ke

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> 
> Hi Ping-Ke,
> 
> Thank you for the incredibly fast response and assistance!
> 
> > Can you dig kernel log (by netconsole or ramoops) if something useful?
> > I'd like to know this is hardware level freeze or kernel can capture something
> wrong.
> 
> I managed to pull a call trace from a historic journald log just
> before the system hung. The kernel gets trapped in an IRQ thread
> inside `rtw_pci_interrupt_threadfn`, calling up into `mac80211`
> `ieee80211_rx_list` before everything freezes. Here is the relevant
> snippet:
> 
> ```text
> Call Trace:
> <IRQ>
> ? __alloc_skb+0x23a/0x2a0
> ? __alloc_skb+0x10c/0x2a0
> ? __pfx_irq_thread_fn+0x10/0x10
> [ ... truncated module list ... ]
> Tainted: G W I 6.19.6-2-cachyos #1 PREEMPT(full)
> Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
> RIP: 0010:ieee80211_rx_list+0x1012/0x1020 [mac80211]
> CPU: 2 UID: 0 PID: 765 Comm: irq/56-rtw88_pc
> rtw_pci_interrupt_threadfn+0x239/0x310 [rtw88_pci]
> ```
> 
> It behaves exactly like a PCIe bus deadlock or a hardware fault that
> eventually brings down the CPU handling the IRQ.

I wonder if there is a malformed data, causing this trace and the leads
kernel freezes. If we can do validation on RX data before calling 
ieee80211_rx_list(), maybe trace disappears and everything will be fine?
Even no need workaround.

> 
> > Are these totally needed to workaround the problem? Or disable_aspm is enough?
> > I'd list them in order of power consumption impact:
> > 1. disable_aspm=y
> > 2. disable_lps_deep=y
> > 3. disable WiFi power save
> 
> To verify which parameters are strictly necessary, I performed
> isolated testing today. I ensured no other modprobe configs were
> active, rebuilt the initramfs, and manually enforced that
> `wifi.powersave` was active via `iw dev wlan0 set power_save on`
> during all tests (as the OS power management profiles were defaulting
> it to off, which initially masked the issue).
> 
> I tested each workaround individually across multiple sleep/wake
> cycles and active usage:
> 
> **Test 1 (ASPM Disabled, LPS Deep Enabled):**
> - Kernel parameters: `rtw88_pci disable_aspm=y` (and `rtw88_core
> disable_lps_deep=n`)
> - Result: Stable. No freezes were observed during usage or transitions
> into/out of S3 sleep while power saving was enforced.
> 
> **Test 2 (ASPM Enabled, LPS Deep Disabled):**
> - Kernel parameters: `rtw88_core disable_lps_deep=y` (and `rtw88_pci
> disable_aspm=n`)
> - Result: Stable. No freezes were observed under the same forced power
> save conditions.
> 
> **Conclusion:** It appears we do not need both workarounds
> simultaneously for this specific hardware. Using only `disable_aspm=y`
> seems to be sufficient to prevent the system freeze. Given your note
> about the power consumption impact ranking, this looks like the
> optimal path forward.

Let's test my RFT patch to disable ASPM then.

> 
> > But what does 'deadlock' mean? As I know NAPI poll is scheduled by ISR,
> > and going to receive packets. The rx_no_aspm workaround is to forcely turn
> > off ASPM during this period.
> 
> By "deadlock" I meant a hardware-level bus lockup. It seems the
> physical RTL8821CE chip itself crashes or hangs the system's PCIe bus
> when trying to negotiate waking up from ASPM L1 while simultaneously
> existing in `LPS_DEEP_MODE_LCLK`. The `rx_no_aspm` workaround in NAPI
> helps during active Rx decoding, but the laptop often freezes while
> completely idle, presumably when the AP sends a basic beacon, the chip
> attempts to leave LPS Deep + L1, and the hardware simply gives up and
> halts the system.

I think this is your perspective and induction, right? Did you measure
real hardware signals?

My point is that if this is a hardware-level bus lockup, let's apply
quirk. If some malformed data causing kernel hangs, I'd add sanity check
on RX data, but I don't actually know what we should check for now. 

> 
> > We have not modified RTL8821CE for a long time, so I'd add workaround
> > to specific platform as mentioned above.
> 
> Adding a DMI/platform quirk specifically for this laptop to disable
> ASPM would be wonderful and deeply appreciated. I agree it is safer
> than touching the global flags for hardware that is functioning
> correctly out in the wild.
> 
> Here is the exact identifying information for my system:
> 
> System Vendor: HP
> Product Name: HP Notebook
> SKU Number: P3S95EA#ACB
> Family: 103C_5335KV
> PCI ID: 10ec:c821
> Subsystem ID: 103c:831a
> 
> I am completely ready to test any patch or quirk you send my way.
> Thank you so much for your time and helping track this down!

I sent a RFT [1] for test. Please check if it works on your HP notebook.
If you check rtw88 log, you can see I added similar patch 5 years ago,
and replaced by preferred the change of "rtwpci->rx_no_aspm", which I
think it can only resolve problem on partial notebooks though.... 

[1] https://lore.kernel.org/linux-wireless/20260311020816.7065-1-pkshih@realtek.com/T/#u

Ping-Ke

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

Ping-Ke Shih <pkshih@realtek.com> wrote:
> 
> LB F <goainwo@gmail.com> wrote:
> >
> > Hi Ping-Ke,
> >
> > Thank you for the incredibly fast response and assistance!
> >
> > > Can you dig kernel log (by netconsole or ramoops) if something useful?
> > > I'd like to know this is hardware level freeze or kernel can capture something
> > wrong.
> >
> > I managed to pull a call trace from a historic journald log just
> > before the system hung. The kernel gets trapped in an IRQ thread
> > inside `rtw_pci_interrupt_threadfn`, calling up into `mac80211`
> > `ieee80211_rx_list` before everything freezes. Here is the relevant
> > snippet:
> >
> > ```text
> > Call Trace:
> > <IRQ>
> > ? __alloc_skb+0x23a/0x2a0
> > ? __alloc_skb+0x10c/0x2a0
> > ? __pfx_irq_thread_fn+0x10/0x10
> > [ ... truncated module list ... ]
> > Tainted: G W I 6.19.6-2-cachyos #1 PREEMPT(full)
> > Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
> > RIP: 0010:ieee80211_rx_list+0x1012/0x1020 [mac80211]
> > CPU: 2 UID: 0 PID: 765 Comm: irq/56-rtw88_pc
> > rtw_pci_interrupt_threadfn+0x239/0x310 [rtw88_pci]
> > ```
> >
> > It behaves exactly like a PCIe bus deadlock or a hardware fault that
> > eventually brings down the CPU handling the IRQ.
> 
> I wonder if there is a malformed data, causing this trace and the leads
> kernel freezes. If we can do validation on RX data before calling
> ieee80211_rx_list(), maybe trace disappears and everything will be fine?
> Even no need workaround.
> 
> >
> > > Are these totally needed to workaround the problem? Or disable_aspm is enough?
> > > I'd list them in order of power consumption impact:
> > > 1. disable_aspm=y
> > > 2. disable_lps_deep=y
> > > 3. disable WiFi power save
> >
> > To verify which parameters are strictly necessary, I performed
> > isolated testing today. I ensured no other modprobe configs were
> > active, rebuilt the initramfs, and manually enforced that
> > `wifi.powersave` was active via `iw dev wlan0 set power_save on`
> > during all tests (as the OS power management profiles were defaulting
> > it to off, which initially masked the issue).
> >
> > I tested each workaround individually across multiple sleep/wake
> > cycles and active usage:
> >
> > **Test 1 (ASPM Disabled, LPS Deep Enabled):**
> > - Kernel parameters: `rtw88_pci disable_aspm=y` (and `rtw88_core
> > disable_lps_deep=n`)
> > - Result: Stable. No freezes were observed during usage or transitions
> > into/out of S3 sleep while power saving was enforced.
> >
> > **Test 2 (ASPM Enabled, LPS Deep Disabled):**
> > - Kernel parameters: `rtw88_core disable_lps_deep=y` (and `rtw88_pci
> > disable_aspm=n`)
> > - Result: Stable. No freezes were observed under the same forced power
> > save conditions.
> >
> > **Conclusion:** It appears we do not need both workarounds
> > simultaneously for this specific hardware. Using only `disable_aspm=y`
> > seems to be sufficient to prevent the system freeze. Given your note
> > about the power consumption impact ranking, this looks like the
> > optimal path forward.
> 
> Let's test my RFT patch to disable ASPM then.
> 
> >
> > > But what does 'deadlock' mean? As I know NAPI poll is scheduled by ISR,
> > > and going to receive packets. The rx_no_aspm workaround is to forcely turn
> > > off ASPM during this period.
> >
> > By "deadlock" I meant a hardware-level bus lockup. It seems the
> > physical RTL8821CE chip itself crashes or hangs the system's PCIe bus
> > when trying to negotiate waking up from ASPM L1 while simultaneously
> > existing in `LPS_DEEP_MODE_LCLK`. The `rx_no_aspm` workaround in NAPI
> > helps during active Rx decoding, but the laptop often freezes while
> > completely idle, presumably when the AP sends a basic beacon, the chip
> > attempts to leave LPS Deep + L1, and the hardware simply gives up and
> > halts the system.
> 
> I think this is your perspective and induction, right? Did you measure
> real hardware signals?
> 
> My point is that if this is a hardware-level bus lockup, let's apply
> quirk. If some malformed data causing kernel hangs, I'd add sanity check
> on RX data, but I don't actually know what we should check for now.
> 
> >
> > > We have not modified RTL8821CE for a long time, so I'd add workaround
> > > to specific platform as mentioned above.
> >
> > Adding a DMI/platform quirk specifically for this laptop to disable
> > ASPM would be wonderful and deeply appreciated. I agree it is safer
> > than touching the global flags for hardware that is functioning
> > correctly out in the wild.
> >
> > Here is the exact identifying information for my system:
> >
> > System Vendor: HP
> > Product Name: HP Notebook
> > SKU Number: P3S95EA#ACB
> > Family: 103C_5335KV
> > PCI ID: 10ec:c821
> > Subsystem ID: 103c:831a
> >
> > I am completely ready to test any patch or quirk you send my way.
> > Thank you so much for your time and helping track this down!
> 
> I sent a RFT [1] for test. Please check if it works on your HP notebook.
> If you check rtw88 log, you can see I added similar patch 5 years ago,
> and replaced by preferred the change of "rtwpci->rx_no_aspm", which I
> think it can only resolve problem on partial notebooks though....
> 
> [1]
> https://lore.kernel.org/linux-wireless/20260311020816.7065-1-pkshih@realtek.
> com/T/#u

Forgot to say. Could you share your full name for me as a reporter
in commit message?

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Hi Ping-Ke,

Thank you for the incredibly fast turnaround and for providing the RFT
patch with the DMI quirk!

First, I want to mention that I am not an IT professional or a
programmer. I am just a regular Linux user who really wants to help
solve this problem. I am trying my best to verify everything
carefully, so please forgive me if my terminology or induction was
slightly off.

To answer your clarifying questions from the previous emails:

> Just want to clarify that these logs only appear in test 3, right?
> No these logs in test 1/2.

Yes, exactly. The `failed to send h2c command` errors only caused a
complete system freeze when no workarounds were active and the adapter
attempted to sleep (Test 3).

> I think this is your perspective and induction, right? Did you measure
> real hardware signals?

You are entirely correct. This is just my induction based solely on
the timing of the logs and system behavior. I do not have access to an
oscilloscope or any hardware diagnostic tools. Given this, I
completely agree that your approach of applying a platform-specific
quirk is the safest and best solution.

> Forgot to say. Could you share your full name for me as a reporter
> in commit message?

My full name is Oleksandr Havrylov. I would be honored to be included
as the reporter in the commit message.

### Recent Baseline Testing Before Your Patch

Before applying your patch today, we ran a few more controlled tests
to double-check our baseline. We verified that our local workaround
(`modprobe.d disable_aspm=y`) **does indeed keep the system completely
stable** and prevents the hard freeze, even when NetworkManager's
`wifi.powersave` is set to ON (default).

However, we noticed one interesting detail in the kernel logs: while
the system no longer freezes with `disable_aspm=y`, `dmesg` still
constantly logs `firmware failed to leave lps state` and `failed to
send h2c command` when the laptop is completely idle. It seems the
firmware still crashes during LPS, but because ASPM is disabled, the
PCIe bus ignores the crash and the system survives perfectly fine. I
just wanted to mention this for completeness!

### Testing Plan

I have **not** applied your RFT patch just yet. I wanted to make sure
our testing baseline was 100% clean and documented first.

I will compile your patch and perform rigorous testing this evening (I
am in the EET timezone, Ukraine). I will test it with the native
`power_save` fully enabled to ensure your patch successfully prevents
the hard lockups as intended.

I will stay in touch and reply back to this thread with a formal
`Tested-by` confirmation (and any logs if needed) as soon as my
testing is complete. Thank you again for all your help!

Best regards,
Oleksandr Havrylov

ср, 11 мар. 2026 г. в 04:22, Ping-Ke Shih <pkshih@realtek.com>:
>
> Ping-Ke Shih <pkshih@realtek.com> wrote:
> >
> > LB F <goainwo@gmail.com> wrote:
> > >
> > > Hi Ping-Ke,
> > >
> > > Thank you for the incredibly fast response and assistance!
> > >
> > > > Can you dig kernel log (by netconsole or ramoops) if something useful?
> > > > I'd like to know this is hardware level freeze or kernel can capture something
> > > wrong.
> > >
> > > I managed to pull a call trace from a historic journald log just
> > > before the system hung. The kernel gets trapped in an IRQ thread
> > > inside `rtw_pci_interrupt_threadfn`, calling up into `mac80211`
> > > `ieee80211_rx_list` before everything freezes. Here is the relevant
> > > snippet:
> > >
> > > ```text
> > > Call Trace:
> > > <IRQ>
> > > ? __alloc_skb+0x23a/0x2a0
> > > ? __alloc_skb+0x10c/0x2a0
> > > ? __pfx_irq_thread_fn+0x10/0x10
> > > [ ... truncated module list ... ]
> > > Tainted: G W I 6.19.6-2-cachyos #1 PREEMPT(full)
> > > Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
> > > RIP: 0010:ieee80211_rx_list+0x1012/0x1020 [mac80211]
> > > CPU: 2 UID: 0 PID: 765 Comm: irq/56-rtw88_pc
> > > rtw_pci_interrupt_threadfn+0x239/0x310 [rtw88_pci]
> > > ```
> > >
> > > It behaves exactly like a PCIe bus deadlock or a hardware fault that
> > > eventually brings down the CPU handling the IRQ.
> >
> > I wonder if there is a malformed data, causing this trace and the leads
> > kernel freezes. If we can do validation on RX data before calling
> > ieee80211_rx_list(), maybe trace disappears and everything will be fine?
> > Even no need workaround.
> >
> > >
> > > > Are these totally needed to workaround the problem? Or disable_aspm is enough?
> > > > I'd list them in order of power consumption impact:
> > > > 1. disable_aspm=y
> > > > 2. disable_lps_deep=y
> > > > 3. disable WiFi power save
> > >
> > > To verify which parameters are strictly necessary, I performed
> > > isolated testing today. I ensured no other modprobe configs were
> > > active, rebuilt the initramfs, and manually enforced that
> > > `wifi.powersave` was active via `iw dev wlan0 set power_save on`
> > > during all tests (as the OS power management profiles were defaulting
> > > it to off, which initially masked the issue).
> > >
> > > I tested each workaround individually across multiple sleep/wake
> > > cycles and active usage:
> > >
> > > **Test 1 (ASPM Disabled, LPS Deep Enabled):**
> > > - Kernel parameters: `rtw88_pci disable_aspm=y` (and `rtw88_core
> > > disable_lps_deep=n`)
> > > - Result: Stable. No freezes were observed during usage or transitions
> > > into/out of S3 sleep while power saving was enforced.
> > >
> > > **Test 2 (ASPM Enabled, LPS Deep Disabled):**
> > > - Kernel parameters: `rtw88_core disable_lps_deep=y` (and `rtw88_pci
> > > disable_aspm=n`)
> > > - Result: Stable. No freezes were observed under the same forced power
> > > save conditions.
> > >
> > > **Conclusion:** It appears we do not need both workarounds
> > > simultaneously for this specific hardware. Using only `disable_aspm=y`
> > > seems to be sufficient to prevent the system freeze. Given your note
> > > about the power consumption impact ranking, this looks like the
> > > optimal path forward.
> >
> > Let's test my RFT patch to disable ASPM then.
> >
> > >
> > > > But what does 'deadlock' mean? As I know NAPI poll is scheduled by ISR,
> > > > and going to receive packets. The rx_no_aspm workaround is to forcely turn
> > > > off ASPM during this period.
> > >
> > > By "deadlock" I meant a hardware-level bus lockup. It seems the
> > > physical RTL8821CE chip itself crashes or hangs the system's PCIe bus
> > > when trying to negotiate waking up from ASPM L1 while simultaneously
> > > existing in `LPS_DEEP_MODE_LCLK`. The `rx_no_aspm` workaround in NAPI
> > > helps during active Rx decoding, but the laptop often freezes while
> > > completely idle, presumably when the AP sends a basic beacon, the chip
> > > attempts to leave LPS Deep + L1, and the hardware simply gives up and
> > > halts the system.
> >
> > I think this is your perspective and induction, right? Did you measure
> > real hardware signals?
> >
> > My point is that if this is a hardware-level bus lockup, let's apply
> > quirk. If some malformed data causing kernel hangs, I'd add sanity check
> > on RX data, but I don't actually know what we should check for now.
> >
> > >
> > > > We have not modified RTL8821CE for a long time, so I'd add workaround
> > > > to specific platform as mentioned above.
> > >
> > > Adding a DMI/platform quirk specifically for this laptop to disable
> > > ASPM would be wonderful and deeply appreciated. I agree it is safer
> > > than touching the global flags for hardware that is functioning
> > > correctly out in the wild.
> > >
> > > Here is the exact identifying information for my system:
> > >
> > > System Vendor: HP
> > > Product Name: HP Notebook
> > > SKU Number: P3S95EA#ACB
> > > Family: 103C_5335KV
> > > PCI ID: 10ec:c821
> > > Subsystem ID: 103c:831a
> > >
> > > I am completely ready to test any patch or quirk you send my way.
> > > Thank you so much for your time and helping track this down!
> >
> > I sent a RFT [1] for test. Please check if it works on your HP notebook.
> > If you check rtw88 log, you can see I added similar patch 5 years ago,
> > and replaced by preferred the change of "rtwpci->rx_no_aspm", which I
> > think it can only resolve problem on partial notebooks though....
> >
> > [1]
> > https://lore.kernel.org/linux-wireless/20260311020816.7065-1-pkshih@realtek.
> > com/T/#u
>
> Forgot to say. Could you share your full name for me as a reporter
> in commit message?
>
>

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Hi Ping-Ke,

I successfully applied your patch out-of-tree and performed rigorous
testing on the host machine.

I can officially confirm that the patch works flawlessly. The DMI
quirk triggered correctly and successfully prevented the
hardware-level PCIe bus lockups on my HP P3S95EA#ACB.

Testing Environment & Methodology:
- Kernel: CachyOS Linux 6.19.6-2-cachyos x86_64
- Toolchain: Clang/LLVM 21.1.8 (`make CC=clang LLVM=1 modules`)
- Extraction: We fetched the strict
`drivers/net/wireless/realtek/rtw88` sub-tree out of the
torvalds/linux `v6.19` tree utilizing `git sparse-checkout` to cleanly
apply the patch without having to compile the entire 2.5GB+ kernel.
- The resulting `.ko` object files were compressed to `.zst` and
installed successfully over the generic CachyOS system driver objects.

Verification Conditions:
- Removed ALL local workarounds. `disable_aspm=Y` is no longer forced
via `/etc/modprobe.d/` overrides.
- Power saving remains natively ON `wifi.powersave = 3` (managed by
NetworkManager).
- Left the laptop in multiple 5-10 minute complete idle states to
enforce sleep modes.

Post-Boot Log Analysis & Potential Improvement Proposition:
The system remained 100% stable without any kernel panics or UI freezes.
However, I continuously monitored the `dmesg` ring buffer and noticed
an intriguing behavior. While the laptop sits completely idle
(NetworkManager connected, but no active traffic), the `rtw88` driver
starts flooded the logs with thousands of firmware errors:

[ 1084.746485] rtw88_8821ce 0000:13:00.0: firmware failed to leave lps state
[ 1084.749662] rtw88_8821ce 0000:13:00.0: failed to send h2c command
[ 1084.752895] rtw88_8821ce 0000:13:00.0: failed to send h2c command

If my understanding of this architecture is correct, previously, when
ASPM wasn't disabled, this exact failure of the adapter firmare inside
`LPS_DEEP_MODE_LCLK` would violently lock up the PCIe bus and crash
the host. Now, thanks to your DMI ASPM quirk at the `rtw88_pci` level,
the host PCIe controller doesn't enter `L1` and is perfectly shielded
from the adapter locking itself up! The OS handles the timeouts
gracefully and driver recovery prevents a hard freeze.

A question for your consideration: Given the immense volume of these
`h2c` timeout errors (and the underlying firmware's fundamental
inability to cleanly enter/exit its own sleep states without L1
participation on this HP model), do you think it would be beneficial
to *also* dynamically disable LPS Deep sleep when this specific ASPM
quirk is triggered?

For example, dynamically forcing `rtwdev->lps_conf.deep_mode =
LPS_DEEP_MODE_NONE` when the DMI ASPM flag is active, strictly to
prevent the firmware from attempting a sleep cycle that is doomed to
fail and polluting the queues and logs? Perhaps this might also save
microscopic CPU interrupts from continuous H2C polling timeouts?

If you believe that simply letting the driver recover and tolerating
the error spam in `dmesg` is the preferred/safer upstream approach, I
am perfectly happy. The patch functions as advertised and system
stability is unequivocally restored!

Thank you immensely for your rapid debugging and definitive patch for
this long-standing issue and for bringing stability to this model.

Tested-by: Oleksandr Havrylov <goainwo@gmail.com>

*(Note: I was a bit unsure which of the two active mailing list
threads was the most appropriate place for this final report — the
original bug discussion or the new RFT patch submission thread — so I
replied to both just to ensure it is correctly attached to the patch.
Apologies for the duplicate email!)*

Best regards,
Oleksandr Havrylov

ср, 11 мар. 2026 г. в 13:00, LB F <goainwo@gmail.com>:
>
> Hi Ping-Ke,
>
> Thank you for the incredibly fast turnaround and for providing the RFT
> patch with the DMI quirk!
>
> First, I want to mention that I am not an IT professional or a
> programmer. I am just a regular Linux user who really wants to help
> solve this problem. I am trying my best to verify everything
> carefully, so please forgive me if my terminology or induction was
> slightly off.
>
> To answer your clarifying questions from the previous emails:
>
> > Just want to clarify that these logs only appear in test 3, right?
> > No these logs in test 1/2.
>
> Yes, exactly. The `failed to send h2c command` errors only caused a
> complete system freeze when no workarounds were active and the adapter
> attempted to sleep (Test 3).
>
> > I think this is your perspective and induction, right? Did you measure
> > real hardware signals?
>
> You are entirely correct. This is just my induction based solely on
> the timing of the logs and system behavior. I do not have access to an
> oscilloscope or any hardware diagnostic tools. Given this, I
> completely agree that your approach of applying a platform-specific
> quirk is the safest and best solution.
>
> > Forgot to say. Could you share your full name for me as a reporter
> > in commit message?
>
> My full name is Oleksandr Havrylov. I would be honored to be included
> as the reporter in the commit message.
>
> ### Recent Baseline Testing Before Your Patch
>
> Before applying your patch today, we ran a few more controlled tests
> to double-check our baseline. We verified that our local workaround
> (`modprobe.d disable_aspm=y`) **does indeed keep the system completely
> stable** and prevents the hard freeze, even when NetworkManager's
> `wifi.powersave` is set to ON (default).
>
> However, we noticed one interesting detail in the kernel logs: while
> the system no longer freezes with `disable_aspm=y`, `dmesg` still
> constantly logs `firmware failed to leave lps state` and `failed to
> send h2c command` when the laptop is completely idle. It seems the
> firmware still crashes during LPS, but because ASPM is disabled, the
> PCIe bus ignores the crash and the system survives perfectly fine. I
> just wanted to mention this for completeness!
>
> ### Testing Plan
>
> I have **not** applied your RFT patch just yet. I wanted to make sure
> our testing baseline was 100% clean and documented first.
>
> I will compile your patch and perform rigorous testing this evening (I
> am in the EET timezone, Ukraine). I will test it with the native
> `power_save` fully enabled to ensure your patch successfully prevents
> the hard lockups as intended.
>
> I will stay in touch and reply back to this thread with a formal
> `Tested-by` confirmation (and any logs if needed) as soon as my
> testing is complete. Thank you again for all your help!
>
> Best regards,
> Oleksandr Havrylov
>
> ср, 11 мар. 2026 г. в 04:22, Ping-Ke Shih <pkshih@realtek.com>:
> >
> > Ping-Ke Shih <pkshih@realtek.com> wrote:
> > >
> > > LB F <goainwo@gmail.com> wrote:
> > > >
> > > > Hi Ping-Ke,
> > > >
> > > > Thank you for the incredibly fast response and assistance!
> > > >
> > > > > Can you dig kernel log (by netconsole or ramoops) if something useful?
> > > > > I'd like to know this is hardware level freeze or kernel can capture something
> > > > wrong.
> > > >
> > > > I managed to pull a call trace from a historic journald log just
> > > > before the system hung. The kernel gets trapped in an IRQ thread
> > > > inside `rtw_pci_interrupt_threadfn`, calling up into `mac80211`
> > > > `ieee80211_rx_list` before everything freezes. Here is the relevant
> > > > snippet:
> > > >
> > > > ```text
> > > > Call Trace:
> > > > <IRQ>
> > > > ? __alloc_skb+0x23a/0x2a0
> > > > ? __alloc_skb+0x10c/0x2a0
> > > > ? __pfx_irq_thread_fn+0x10/0x10
> > > > [ ... truncated module list ... ]
> > > > Tainted: G W I 6.19.6-2-cachyos #1 PREEMPT(full)
> > > > Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
> > > > RIP: 0010:ieee80211_rx_list+0x1012/0x1020 [mac80211]
> > > > CPU: 2 UID: 0 PID: 765 Comm: irq/56-rtw88_pc
> > > > rtw_pci_interrupt_threadfn+0x239/0x310 [rtw88_pci]
> > > > ```
> > > >
> > > > It behaves exactly like a PCIe bus deadlock or a hardware fault that
> > > > eventually brings down the CPU handling the IRQ.
> > >
> > > I wonder if there is a malformed data, causing this trace and the leads
> > > kernel freezes. If we can do validation on RX data before calling
> > > ieee80211_rx_list(), maybe trace disappears and everything will be fine?
> > > Even no need workaround.
> > >
> > > >
> > > > > Are these totally needed to workaround the problem? Or disable_aspm is enough?
> > > > > I'd list them in order of power consumption impact:
> > > > > 1. disable_aspm=y
> > > > > 2. disable_lps_deep=y
> > > > > 3. disable WiFi power save
> > > >
> > > > To verify which parameters are strictly necessary, I performed
> > > > isolated testing today. I ensured no other modprobe configs were
> > > > active, rebuilt the initramfs, and manually enforced that
> > > > `wifi.powersave` was active via `iw dev wlan0 set power_save on`
> > > > during all tests (as the OS power management profiles were defaulting
> > > > it to off, which initially masked the issue).
> > > >
> > > > I tested each workaround individually across multiple sleep/wake
> > > > cycles and active usage:
> > > >
> > > > **Test 1 (ASPM Disabled, LPS Deep Enabled):**
> > > > - Kernel parameters: `rtw88_pci disable_aspm=y` (and `rtw88_core
> > > > disable_lps_deep=n`)
> > > > - Result: Stable. No freezes were observed during usage or transitions
> > > > into/out of S3 sleep while power saving was enforced.
> > > >
> > > > **Test 2 (ASPM Enabled, LPS Deep Disabled):**
> > > > - Kernel parameters: `rtw88_core disable_lps_deep=y` (and `rtw88_pci
> > > > disable_aspm=n`)
> > > > - Result: Stable. No freezes were observed under the same forced power
> > > > save conditions.
> > > >
> > > > **Conclusion:** It appears we do not need both workarounds
> > > > simultaneously for this specific hardware. Using only `disable_aspm=y`
> > > > seems to be sufficient to prevent the system freeze. Given your note
> > > > about the power consumption impact ranking, this looks like the
> > > > optimal path forward.
> > >
> > > Let's test my RFT patch to disable ASPM then.
> > >
> > > >
> > > > > But what does 'deadlock' mean? As I know NAPI poll is scheduled by ISR,
> > > > > and going to receive packets. The rx_no_aspm workaround is to forcely turn
> > > > > off ASPM during this period.
> > > >
> > > > By "deadlock" I meant a hardware-level bus lockup. It seems the
> > > > physical RTL8821CE chip itself crashes or hangs the system's PCIe bus
> > > > when trying to negotiate waking up from ASPM L1 while simultaneously
> > > > existing in `LPS_DEEP_MODE_LCLK`. The `rx_no_aspm` workaround in NAPI
> > > > helps during active Rx decoding, but the laptop often freezes while
> > > > completely idle, presumably when the AP sends a basic beacon, the chip
> > > > attempts to leave LPS Deep + L1, and the hardware simply gives up and
> > > > halts the system.
> > >
> > > I think this is your perspective and induction, right? Did you measure
> > > real hardware signals?
> > >
> > > My point is that if this is a hardware-level bus lockup, let's apply
> > > quirk. If some malformed data causing kernel hangs, I'd add sanity check
> > > on RX data, but I don't actually know what we should check for now.
> > >
> > > >
> > > > > We have not modified RTL8821CE for a long time, so I'd add workaround
> > > > > to specific platform as mentioned above.
> > > >
> > > > Adding a DMI/platform quirk specifically for this laptop to disable
> > > > ASPM would be wonderful and deeply appreciated. I agree it is safer
> > > > than touching the global flags for hardware that is functioning
> > > > correctly out in the wild.
> > > >
> > > > Here is the exact identifying information for my system:
> > > >
> > > > System Vendor: HP
> > > > Product Name: HP Notebook
> > > > SKU Number: P3S95EA#ACB
> > > > Family: 103C_5335KV
> > > > PCI ID: 10ec:c821
> > > > Subsystem ID: 103c:831a
> > > >
> > > > I am completely ready to test any patch or quirk you send my way.
> > > > Thank you so much for your time and helping track this down!
> > >
> > > I sent a RFT [1] for test. Please check if it works on your HP notebook.
> > > If you check rtw88 log, you can see I added similar patch 5 years ago,
> > > and replaced by preferred the change of "rtwpci->rx_no_aspm", which I
> > > think it can only resolve problem on partial notebooks though....
> > >
> > > [1]
> > > https://lore.kernel.org/linux-wireless/20260311020816.7065-1-pkshih@realtek.
> > > com/T/#u
> >
> > Forgot to say. Could you share your full name for me as a reporter
> > in commit message?
> >
> >

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> Hi Ping-Ke,
> 
> I successfully applied your patch out-of-tree and performed rigorous
> testing on the host machine.
> 
> I can officially confirm that the patch works flawlessly. The DMI
> quirk triggered correctly and successfully prevented the
> hardware-level PCIe bus lockups on my HP P3S95EA#ACB.

Thanks for your quickly test with my patch. :)

> 
> Testing Environment & Methodology:
> - Kernel: CachyOS Linux 6.19.6-2-cachyos x86_64
> - Toolchain: Clang/LLVM 21.1.8 (`make CC=clang LLVM=1 modules`)
> - Extraction: We fetched the strict
> `drivers/net/wireless/realtek/rtw88` sub-tree out of the
> torvalds/linux `v6.19` tree utilizing `git sparse-checkout` to cleanly
> apply the patch without having to compile the entire 2.5GB+ kernel.
> - The resulting `.ko` object files were compressed to `.zst` and
> installed successfully over the generic CachyOS system driver objects.
> 
> Verification Conditions:
> - Removed ALL local workarounds. `disable_aspm=Y` is no longer forced
> via `/etc/modprobe.d/` overrides.
> - Power saving remains natively ON `wifi.powersave = 3` (managed by
> NetworkManager).
> - Left the laptop in multiple 5-10 minute complete idle states to
> enforce sleep modes.
> 
> Post-Boot Log Analysis & Potential Improvement Proposition:
> The system remained 100% stable without any kernel panics or UI freezes.
> However, I continuously monitored the `dmesg` ring buffer and noticed
> an intriguing behavior. While the laptop sits completely idle
> (NetworkManager connected, but no active traffic), the `rtw88` driver
> starts flooded the logs with thousands of firmware errors:
> 
> [ 1084.746485] rtw88_8821ce 0000:13:00.0: firmware failed to leave lps state
> [ 1084.749662] rtw88_8821ce 0000:13:00.0: failed to send h2c command
> [ 1084.752895] rtw88_8821ce 0000:13:00.0: failed to send h2c command
> 
> If my understanding of this architecture is correct, previously, when
> ASPM wasn't disabled, this exact failure of the adapter firmare inside
> `LPS_DEEP_MODE_LCLK` would violently lock up the PCIe bus and crash
> the host. Now, thanks to your DMI ASPM quirk at the `rtw88_pci` level,
> the host PCIe controller doesn't enter `L1` and is perfectly shielded
> from the adapter locking itself up! The OS handles the timeouts
> gracefully and driver recovery prevents a hard freeze.

I'm really not sure how/why kernel becomes frozen. As I mentioned before
it might because of received malformed data and no complete validation
before reporting RX packet to mac80211.

Not sure if you can try to dig and add some validation?

(Current DMI patch is fine to me.)

> 
> A question for your consideration: Given the immense volume of these
> `h2c` timeout errors (and the underlying firmware's fundamental
> inability to cleanly enter/exit its own sleep states without L1
> participation on this HP model), do you think it would be beneficial
> to *also* dynamically disable LPS Deep sleep when this specific ASPM
> quirk is triggered?
> 
> For example, dynamically forcing `rtwdev->lps_conf.deep_mode =
> LPS_DEEP_MODE_NONE` when the DMI ASPM flag is active, strictly to
> prevent the firmware from attempting a sleep cycle that is doomed to
> fail and polluting the queues and logs? Perhaps this might also save
> microscopic CPU interrupts from continuous H2C polling timeouts?

Are the 'h2c' timeout messages flooding? or appears periodically? 
Does it really affect connection stable?

If you change another AP or connection on 5GHz band, does the messages
still present? 

I think it isn't easy to find out the cause without measuring hardware
signals, since I saw the message very very rare. So, I'd adopt your
suggestion (dynamic LPS_DEEP_MODE_NONE) if the test is positive.

> 
> If you believe that simply letting the driver recover and tolerating
> the error spam in `dmesg` is the preferred/safer upstream approach, I
> am perfectly happy. The patch functions as advertised and system
> stability is unequivocally restored!
> 
> Thank you immensely for your rapid debugging and definitive patch for
> this long-standing issue and for bringing stability to this model.
> 
> Tested-by: Oleksandr Havrylov <goainwo@gmail.com>

I will add this to my patch then.

> 
> *(Note: I was a bit unsure which of the two active mailing list
> threads was the most appropriate place for this final report — the
> original bug discussion or the new RFT patch submission thread — so I
> replied to both just to ensure it is correctly attached to the patch.
> Apologies for the duplicate email!)*
> 

Let's discuss in this thread. For RFT patch, I suppose you only reply
me about the test result and give me Tested-by tag if it works. 

By the way, your this reply is top posting that mailing list isn't
preferred, so I delete old discussion. Please avoid this in the future.

Ping-Ke

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Ping-Ke Shih <pkshih@realtek.com> wrote:
> I'm really not sure how/why kernel becomes frozen. As I mentioned before
> it might because of received malformed data and no complete validation
> before reporting RX packet to mac80211.
> Not sure if you can try to dig and add some validation?

I reviewed both rx.c and pci.c in detail and found a genuine validation
gap specific to the 8821CE chip.

In rtw_pci_rx_napi() (pci.c), the RX path allocates a new skb based
on the pkt_len field from the RX descriptor:

  new_len = pkt_stat.pkt_len + pkt_offset;
  new = dev_alloc_skb(new_len);
  skb_put_data(new, skb->data, new_len);
  /* ... */
  skb_pull(new, pkt_offset);
  ieee80211_rx_napi(rtwdev->hw, NULL, new, napi);

If pkt_stat.pkt_len is zero, new_len equals pkt_offset, skb_put_data
copies only the descriptor header, and skb_pull then removes that header
-- leaving an empty skb (len=0) that is passed unconditionally to
ieee80211_rx_napi() with no length guard.

Protection already exists for the 8703B chip in rtw_rx_fill_rx_status():

  if (rtwdev->chip->id == RTW_CHIP_TYPE_8703B && pkt_stat->pkt_len == 0) {
      rx_status->flag |= RX_FLAG_NO_PSDU;
      rtw_dbg(rtwdev, RTW_DBG_RX, "zero length packet");
  }

No equivalent check exists for RTW_CHIP_TYPE_8821CE. Removing the
chip-id restriction would be a minimal, safe fix for all chips:

--- a/rx.c
+++ b/rx.c
-  if (rtwdev->chip->id == RTW_CHIP_TYPE_8703B && pkt_stat->pkt_len == 0) {
+  if (pkt_stat->pkt_len == 0) {

I also checked PHY-level error counters from debugfs during normal
operation (phy_info):

  OFDM cnt (ok, err) = (867,  11)  ->   1.3% PHY CRC error rate
  VHT  cnt (ok, err) = (267,  32)  ->  10.7% PHY CRC error rate

Frames with crc_err are passed to mac80211 with RX_FLAG_FAILED_FCS_CRC
set (not dropped by the driver), which is the correct approach.

However, I do not believe the freeze is caused by malformed RX data.
The freeze occurs deterministically about 10 seconds after the system
becomes fully idle with zero active network traffic, which matches the
LPS_DEEP_MODE_LCLK entry sequence rather than a random data corruption
pattern. The freeze behaviour also disappears entirely when ASPM L1 is
disabled (as confirmed by the Live USB logs I provided earlier), which
is the hallmark of a PCIe bus gating deadlock, not a data path issue.

> Are the 'h2c' timeout messages flooding? or appears periodically? Does it
> really affect connection stable?

The errors appear periodically in bursts during idle; network
connectivity is never affected (parallel ping tests show 0% packet
loss). The flooding documented in previous tests (hundreds per minute)
was observed under conditions where the LPS state machine had reached
a persistent failure mode after extended uptime. In shorter tests from
a fresh module load, the errors are sporadic (3-5 per 10 minutes).

> If you change another AP or connection on 5GHz band, does the messages
> still present?

Yes. The issue has persisted for 2 years across 3 completely different
Access Points. It is reproducible on 5GHz only (2.4GHz is disabled on
all my networks).

> I think it isn't easy to find out the cause without measuring hardware
> signals, since I saw the message very very rare. So, I'd adopt your
> suggestion (dynamic LPS_DEEP_MODE_NONE) if the test is positive.

The test is definitively positive.

Test environment: stock CachyOS 6.19.6 kernel, PCIe ASPM L1 confirmed
ENABLED via lspci ('LnkCtl: ASPM L1 Enabled'), no out-of-tree patches.
The rtw88 module stack was fully reloaded (including rtw88_core) for
each scenario. The disable_lps_deep parameter, which belongs to
rtw88_core, was verified via /sys/module/rtw88_core/parameters/
before and after each reload.

Test protocol: after module reload and Wi-Fi reconnect (verified via
HTTP 204 check), a 5-minute warm-up period elapsed before the
5-minute measurement window began. This ensures the firmware's LPS
state machine has fully initialised before results are recorded.

Methodology verified: 'modprobe -r rtw88_8821ce' removes only the
chip-specific modules, leaving rtw88_core in memory. The correct
procedure used was to explicitly also remove rtw88_core, then reload
all modules with the desired parameter.

Results (battery power, true idle each):

  disable_lps_deep=N (DEFAULT):
    Warm-up (5 min cumulative):  h2c=4   lps=0
    Measurement (5 min):         h2c=0   lps=0  [errors are bursty]

  disable_lps_deep=Y (CONFIRMED via sysfs):
    Warm-up (5 min cumulative):  h2c=0   lps=0
    Measurement (5 min):         h2c=0   lps=0
    ALL 10 minutes:              h2c=0

With disable_lps_deep=Y, not a single h2c timeout was recorded across
the entire 10-minute observation window (warm-up + measurement). With
disable_lps_deep=N, errors appeared within the first 5 minutes of idle.
Setting disable_lps_deep=Y completely eliminates the firmware timeout
loop, confirming that the root cause is the firmware attempting
LPS_DEEP_MODE_LCLK while PCIe constraints prevent it from completing.

Dynamic LPS_DEEP_MODE_NONE for the ASPM DMI quirk entry is the correct
and complete architectural solution.

--- Technical Appendix: RX Validation Audit Findings ---

I performed a deep audit of the RX descriptor parsing logic in rx.c and pci.c.
I found two concrete areas where validation is incomplete for the 8821CE:

1. Out-of-Bounds Read in rtw_pci_rx_napi (pci.c):
The DMA buffer size is fixed at ~11.5KB (RTK_PCI_RX_BUF_SIZE).
However, the hardware
descriptor (W0_PKT_LEN) is 14 bits, allowing it to indicate up to 16KB.
The driver calculates new_len = pkt_stat.pkt_len + pkt_offset and calls
skb_put_data(new, skb->data, new_len) without checking if new_len exceeds the
DMA source buffer. If hardware sends a malformed large length, this leads
to an OOB read of adjacent memory.

2. Missing 8821CE guard in rtw_rx_fill_rx_status (rx.c):
The check for pkt_len == 0 (which results in an empty SKB being passed
to mac80211)
is manually restricted to RTW_CHIP_TYPE_8703B:
  if (rtwdev->chip->id == RTW_CHIP_TYPE_8703B && pkt_stat->pkt_len == 0)

Expanding this guard to all chips (or specifically 8821CE) would be safer.

While these vulnerabilities exist, I still believe the freeze is
PCIe-timing related
(LCLK entry/ASPM conflict), as no RX-related warnings or memory corruption
traces were found in dmesg prior to the hard freeze.

Best regards,
Oleksandr Havrylov

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Ping-Ke Shih <pkshih@realtek.com> wrote:
> I'm really not sure how/why kernel becomes frozen. As I mentioned before
> it might because of received malformed data and no complete validation
> before reporting RX packet to mac80211.
> Not sure if you can try to dig and add some validation?

Hi Ping-Ke,

I took your advice and performed a deeper audit of the rtw88 PCI implementation,
focusing on both validation and concurrency. While the RX gaps I previously
mentioned are real, I found two critical architectural issues in the TX path
that likely contribute to the "hard freezes" and DMA stalls we've seen.

1. Concurrency: TX Descriptor Management Race (pci.c:836)
---------------------------------------------------------
In rtw_pci_tx_write_data(), rtw88 fetches the descriptor address based on
the current write pointer (wp) BEFORE acquiring the irq_lock:

```c
/* drivers/net/wireless/realtek/rtw88/pci.c:836 */
buf_desc = get_tx_buffer_desc(ring, tx_buf_desc_sz);
memset(buf_desc, 0, tx_buf_desc_sz);
/* ... packets are filled ... */
spin_lock_bh(&rtwpci->irq_lock); // [!] Lock is taken too late
```

Since mac80211 can call rtw_ops_tx and rtw_ops_wake_tx_queue (the latter
calling __rtw_tx_work) concurrently on different CPUs—especially for
high-priority AC_VO traffic—two threads can fetch the same wp for the
same queue simultaneously.

Result: CPU 0 prepares data in slot [N], while CPU 1 simultaneously zeros out
or overwrites slot [N]. This explains why we see intermittent descriptor
corruption and subsequent DMA/firmware hangs.

2. Synchronization: Missing DMA Memory Barrier (pci.c:786)
----------------------------------------------------------
In rtw_pci_tx_kick_off_queue(), the doorbell is hit without a memory barrier:

```c
/* drivers/net/wireless/realtek/rtw88/pci.c:786 */
rtw_write16(rtwdev, bd_idx, ring->r.wp & TRX_BD_IDX_MASK);
```

For PCIe DMA, it is vital to ensure descriptor RAM writes are visible to
the device before the MMIO register doorbell hits. Standard Linux practice
usually dictates a wmb() here. Without it, the Wi-Fi controller may read
stale or uninitialized memory, leading to the "failed to leave lps state"
timeouts and H2C command failures we've logged.

3. Confirmed RX Limit Mismatch (rtw8821c.c:254)
-----------------------------------------------
I verified that the hardware is explicitly programmed with a 12KB limit:

```c
/* drivers/net/wireless/realtek/rtw88/rtw8821c.c:254 */
rtw_write8(rtwdev, REG_RX_PKT_LIMIT, WLAN_RX_PKT_LIMIT_512);
```

Since the driver's RX buffer (RTK_PCI_RX_BUF_SIZE) is only 11.2KB, any
malformed or large packet will result in an OOB read in rtw_pci_rx_napi().

I believe addressing these three points (TX locking, TX barriers, and
RX buffer consistency) would significantly harden the driver against
the stability issues reported in Bug 221195.

Best regards,
Oleksandr Havrylov

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Hi Ping-Ke,

I apologize for the rapid follow-up and for being perhaps a bit over-assertive
in my previous email. As I continued to dig into the code, I realized that
some of my interpretations of hardware registers (like REG_RX_PKT_LIMIT)
and kernel serialization might be simplified compared to the real-world
complexities you deal with.

I'd like to reframe my previous notes as "curious observations" that I
stumbled upon while testing, and I'd value your professional take on whether
they are relevant:

1. RX Host-Side Validation:
While searching for the 12KB limit I mentioned, I noticed that in
rtw_pci_rx_napi(), the driver uses the pkt_len field from the descriptor
directly for skb_put_data() without checking it against the host buffer
size (RTK_PCI_RX_BUF_SIZE). Even if the hardware normally clips DMA,
would it be worth adding a host-side guard there as a "hardening" measure
against potentially malformed hardware reports?

2. TX Write Pointer (wp) Fetch:
I noticed that in rtw_pci_tx_write_data(), get_tx_buffer_desc() fetches
the wp outside the irq_lock. I wasn't sure if mac80211 guarantees that
the direct TX path and the background worker threads can never collide on
the same queue, but I thought it was worth mentioning just in case.

3. Memory Barriers:
The wmb() point was more of an architectural observation regarding
PCI best practices for non-x86 platforms. I understand x86 is quite
forgiving here, but I noticed it was a pattern that stood out.

Please treat these as humble suggestions from someone trying to learn
the driver's internals. I didn't mean to imply these were "critical bugs"
without your expert verification.

Thank you for your patience with my technical excitement!

Best regards,
Oleksandr

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

After extended testing with your DMI patch applied, the hard freeze is
gone. However, with ASPM disabled but LPS Deep still active, I observe
periodic h2c timeouts during idle which cause occasional WiFi
throughput drops and Bluetooth audio stuttering. When I additionally
set disable_lps_deep=Y, all symptoms disappear completely. This
confirms that combining the ASPM quirk with dynamic LPS_DEEP_MODE_NONE
would be the complete fix. Ready to test an updated patch if you
decide to include this.

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Ping-Ke Shih <pkshih@realtek.com> wrote:
> I'd adopt your suggestion (dynamic LPS_DEEP_MODE_NONE) if the test
> is positive.

Hi Ping-Ke,

Following your suggestion, I performed an additional experiment to
validate the dynamic LPS_DEEP_MODE_NONE idea. Please treat this
purely as a field test report -- I am not a kernel developer, and the
implementation below is certainly not upstream-quality. I am sharing
it only in the hope that it helps you design a proper solution.

What I did:

I extended your DMI quirk in pci.c with an additional capability flag
for LPS Deep mode. The only file touched was pci.c (your patch) --
main.c was left completely unmodified.

The changes to your patch are as follows:

  /* 1. Extended the capabilities enum */
  enum rtw88_quirk_dis_pci_caps {
          QUIRK_DIS_PCI_CAP_ASPM,
          QUIRK_DIS_PCI_CAP_LPS_DEEP,  /* test addition */
  };

  /* 2. Extended disable_pci_caps() callback */
  static int disable_pci_caps(const struct dmi_system_id *dmi)
  {
          uintptr_t dis_caps = (uintptr_t)dmi->driver_data;

          if (dis_caps & BIT(QUIRK_DIS_PCI_CAP_ASPM))
                  rtw_pci_disable_aspm = true;

          if (dis_caps & BIT(QUIRK_DIS_PCI_CAP_LPS_DEEP))
                  rtw_disable_lps_deep_mode = true;

          return 1;
  }

  /* 3. Both flags set for the HP P3S95EA#ACB entry */
  .driver_data = (void *)(BIT(QUIRK_DIS_PCI_CAP_ASPM) |
                          BIT(QUIRK_DIS_PCI_CAP_LPS_DEEP)),

I am aware that setting rtw_disable_lps_deep_mode from pci.c is
architecturally impure -- it is a global flag that would affect all
rtw88 devices in a hypothetical multi-adapter system. A proper
per-device solution (e.g. a flag inside struct rtw_dev set during
probe) would be cleaner. I simply used the existing global as the
most straightforward way to validate the concept.

Verification:

Confirmed no rtw88-related entries exist in /etc/modprobe.d/,
/lib/modprobe.d/, or /run/modprobe.d/, ruling out any external
parameter injection.

After loading the patched modules, the following was confirmed via
sysfs:

  /sys/module/rtw88_core/parameters/disable_lps_deep_mode = Y
  /sys/module/rtw88_pci/parameters/disable_aspm = Y

This confirms the DMI quirk is the sole source of both values.

Results (10-minute idle observation, battery power, wifi.powersave=3):

  With your ASPM patch alone (LPS Deep still active):
    - periodic "failed to send h2c command" bursts observed
    - occasional WiFi throughput drops and Bluetooth audio stuttering

  With ASPM patch + LPS Deep disabled via the quirk:
    - h2c=0, lps=0 across the entire observation window
    - WiFi throughput stable, Bluetooth audio uninterrupted

The result confirms that disabling LPS Deep Mode in addition to ASPM
completely eliminates the remaining firmware timeout loop on this
platform.

I hope this experiment is useful as a data point. Please feel free to
discard the implementation and design a proper solution -- I am ready
to test any updated patch you send.

Best regards,
Oleksandr Havrylov

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Oleksandr Havrylov <goainwo@gmail.com> wrote:
> After extended testing with your DMI patch applied, the hard freeze is
> gone. However, with ASPM disabled but LPS Deep still active, I observe
> periodic h2c timeouts during idle which cause occasional WiFi throughput
> drops and Bluetooth audio stuttering. When I additionally set
> disable_lps_deep=Y, all symptoms disappear completely. This confirms
> that combining the ASPM quirk with dynamic LPS_DEEP_MODE_NONE would be
> the complete fix. Ready to test an updated patch if you decide to
> include this.

Hi Ping-Ke,

While monitoring logs with the current patch applied, I noticed two
things that might be useful.

First, the following message appears each time the driver loads:

  rtw88_8821ce 0000:13:00.0: can't disable ASPM; OS doesn't have ASPM control

This suggests the BIOS retains control over ASPM and prevents any
OS-level override via pci_disable_link_state(). The system remains
stable regardless, which confirms that the rtw_pci_disable_aspm flag
approach in your patch is the correct and effective method here.

Second, during normal operation I observe this warning periodically:

  WARNING: net/mac80211/rx.c:5491 at ieee80211_rx_list+0x177/0x1020 [mac80211]

This is the same location that appeared in the call trace just before
the hard freeze. You mentioned earlier that malformed RX data reaching
mac80211 could be a factor. I'm not sure if this warning is related,
but I wanted to flag it in case it is useful for your RX validation
investigation.

No h2c timeouts or firmware errors have been observed. The system
remains fully stable.

Best regards,
Oleksandr Havrylov

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> 
> Oleksandr Havrylov <goainwo@gmail.com> wrote:
> > After extended testing with your DMI patch applied, the hard freeze is
> > gone. However, with ASPM disabled but LPS Deep still active, I observe
> > periodic h2c timeouts during idle which cause occasional WiFi throughput
> > drops and Bluetooth audio stuttering. When I additionally set
> > disable_lps_deep=Y, all symptoms disappear completely. This confirms
> > that combining the ASPM quirk with dynamic LPS_DEEP_MODE_NONE would be
> > the complete fix. Ready to test an updated patch if you decide to
> > include this.
> 
> Hi Ping-Ke,
> 
> While monitoring logs with the current patch applied, I noticed two
> things that might be useful.
> 
> First, the following message appears each time the driver loads:
> 
>   rtw88_8821ce 0000:13:00.0: can't disable ASPM; OS doesn't have ASPM control
> 
> This suggests the BIOS retains control over ASPM and prevents any
> OS-level override via pci_disable_link_state(). The system remains
> stable regardless, which confirms that the rtw_pci_disable_aspm flag
> approach in your patch is the correct and effective method here.

Not sure if this is because PCIE bridge has no ASPM capability?

> 
> Second, during normal operation I observe this warning periodically:
> 
>   WARNING: net/mac80211/rx.c:5491 at ieee80211_rx_list+0x177/0x1020 [mac80211]

LN5491 (kernel v6.19.6) is:

                case RX_ENC_VHT:
                        if (WARN_ONCE(status->rate_idx > 11 ||
                                      !status->nss ||
                                      status->nss > 8,
                                      "Rate marked as a VHT rate but data is invalid: MCS: %d, NSS: %d\n",
                                      status->rate_idx, status->nss))
                                goto drop;
                        break;

Looks like driver reports improper VHT nss/rate? But this warns once, and
you message isn't like this. 

Could you check the source code LN5491 you are using?

Ping-Ke

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Ping-Ke Shih <pkshih@realtek.com> wrote:
> Not sure if this is because PCIE bridge has no ASPM capability?

That could indeed be the case -- I do not have a way to confirm
without further hardware-level inspection.

> LN5491 (kernel v6.19.6) is:
>                 case RX_ENC_VHT:
>                         if (WARN_ONCE(status->rate_idx > 11 ||
>                                       !status->nss ||
>                                       status->nss > 8,
>                                       "Rate marked as a VHT rate but data is invalid: MCS: %d, NSS: %d\n",
>                                       status->rate_idx, status->nss))
>                                 goto drop;
>                         break;
> Looks like driver reports improper VHT nss/rate? But this warns once, and
> you message isn't like this.
> Could you check the source code LN5491 you are using?

The file net/mac80211/rx.c is not available on disk on my system
(CachyOS ships only .h files in the headers package), but I located
the exact warning message in journalctl:

  Rate marked as a VHT rate but data is invalid: MCS: 0, NSS: 0

This confirms that line 5491 in my kernel matches exactly what you
showed from v6.19.6 -- the RX_ENC_VHT case checking for
status->nss == 0. The offset in my trace is slightly different
(+0x183 vs +0x177), which is likely due to CachyOS's LTO/AutoFDO
compiler optimizations.

The warning appeared once in my initial test session:

  Rate marked as a VHT rate but data is invalid: MCS: 0, NSS: 0
  WARNING: net/mac80211/rx.c:5491 at ieee80211_rx_list+0x183/0x1020 [mac80211]

However, in subsequent module reload and reconnect cycles I was unable
to reproduce it. This is consistent with WARN_ONCE behavior -- it
likely fired on the first invalid nss=0 packet after the initial
driver load and has not triggered since. I cannot confirm it as a
reliable symptom.

---

Regarding patch stability: the results below are from testing your
original RFT patch [1], not any newer submission. I want to be
explicit to avoid confusion:

  [1] https://lore.kernel.org/linux-wireless/20260311020816.7065-1-pkshih@realtek.com/

This is the exact diff I compiled and tested:

--- a/drivers/net/wireless/realtek/rtw88/pci.c
+++ b/drivers/net/wireless/realtek/rtw88/pci.c
@@ -2,6 +2,7 @@
 /* Copyright(c) 2018-2019  Realtek Corporation
  */

+#include <linux/dmi.h>
 #include <linux/module.h>
 #include <linux/pci.h>
 #include "main.h"
@@ -1744,6 +1745,34 @@ const struct pci_error_handlers rtw_pci_err_handler = {
 };
 EXPORT_SYMBOL(rtw_pci_err_handler);

+enum rtw88_quirk_dis_pci_caps {
+ QUIRK_DIS_PCI_CAP_ASPM,
+};
+
+static int disable_pci_caps(const struct dmi_system_id *dmi)
+{
+ uintptr_t dis_caps = (uintptr_t)dmi->driver_data;
+
+ if (dis_caps & BIT(QUIRK_DIS_PCI_CAP_ASPM))
+ rtw_pci_disable_aspm = true;
+
+ return 1;
+}
+
+static const struct dmi_system_id rtw88_pci_quirks[] = {
+ {
+ .callback = disable_pci_caps,
+ .ident = "HP Notebook - P3S95EA#ACB",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "HP"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "HP Notebook"),
+ DMI_MATCH(DMI_PRODUCT_SKU, "P3S95EA#ACB"),
+ },
+ .driver_data = (void *)BIT(QUIRK_DIS_PCI_CAP_ASPM),
+ },
+ {}
+};
+
 int rtw_pci_probe(struct pci_dev *pdev,
    const struct pci_device_id *id)
 {
@@ -1808,6 +1837,7 @@ int rtw_pci_probe(struct pci_dev *pdev,
      bridge && bridge->vendor == PCI_VENDOR_ID_INTEL)
  rtwpci->rx_no_aspm = true;

+ dmi_check_system(rtw88_pci_quirks);
  rtw_pci_phy_cfg(rtwdev);

  ret = rtw_register_hw(rtwdev, hw);

Results with only this patch applied:

  - The hard freeze lockup is gone.
  - However, during idle the logs are flooded with:

      rtw88_8821ce 0000:13:00.0: failed to send h2c command
      rtw88_8821ce 0000:13:00.0: firmware failed to leave lps state

  - To give a concrete sense of the volume: over an ~80-minute
    observation window after a clean module reload, I recorded
    11,757 "failed to send h2c command" events and 2 "firmware
    failed to leave lps state" events -- approximately 110 errors
    per minute during active periods.
  - These errors cause Bluetooth audio stuttering and WiFi
    throughput drops.

When I additionally set disable_lps_deep=Y alongside your ASPM patch,
all h2c errors vanish completely and Bluetooth/WiFi remain fully
stable. This confirms that disabling LPS Deep is necessary for
complete stability on this specific HP SKU.

I also noticed what appears to be a new patch in a separate mailing
list thread. I will test it shortly and report back with the results.

Best regards,
Oleksandr Havrylov

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> 
> Ping-Ke Shih <pkshih@realtek.com> wrote:
> > Not sure if this is because PCIE bridge has no ASPM capability?
> 
> That could indeed be the case -- I do not have a way to confirm
> without further hardware-level inspection.
> 
> > LN5491 (kernel v6.19.6) is:
> >                 case RX_ENC_VHT:
> >                         if (WARN_ONCE(status->rate_idx > 11 ||
> >                                       !status->nss ||
> >                                       status->nss > 8,
> >                                       "Rate marked as a VHT rate but data is
> invalid: MCS: %d, NSS: %d\n",
> >                                       status->rate_idx, status->nss))
> >                                 goto drop;
> >                         break;
> > Looks like driver reports improper VHT nss/rate? But this warns once, and
> > you message isn't like this.
> > Could you check the source code LN5491 you are using?
> 
> The file net/mac80211/rx.c is not available on disk on my system
> (CachyOS ships only .h files in the headers package), but I located
> the exact warning message in journalctl:
> 
>   Rate marked as a VHT rate but data is invalid: MCS: 0, NSS: 0
> 
> This confirms that line 5491 in my kernel matches exactly what you
> showed from v6.19.6 -- the RX_ENC_VHT case checking for
> status->nss == 0. The offset in my trace is slightly different
> (+0x183 vs +0x177), which is likely due to CachyOS's LTO/AutoFDO
> compiler optimizations.
> 
> The warning appeared once in my initial test session:
> 
>   Rate marked as a VHT rate but data is invalid: MCS: 0, NSS: 0
>   WARNING: net/mac80211/rx.c:5491 at ieee80211_rx_list+0x183/0x1020 [mac80211]
> 
> However, in subsequent module reload and reconnect cycles I was unable
> to reproduce it. This is consistent with WARN_ONCE behavior -- it
> likely fired on the first invalid nss=0 packet after the initial
> driver load and has not triggered since. I cannot confirm it as a
> reliable symptom.

To reproduce this reliable, you need to remove driver ko and mac80211.ko,
and reinstall them.

However, you have confirmed this is the symptom. I think only if you
want to dig why the rate reported by hardware is weird, otherwise we
can ignore this warning.

> 
> ---
> 
> Regarding patch stability: the results below are from testing your
> original RFT patch [1], not any newer submission. I want to be
> explicit to avoid confusion:
> 
>   [1]
> https://lore.kernel.org/linux-wireless/20260311020816.7065-1-pkshih@realtek.
> com/
> 
> This is the exact diff I compiled and tested:
> 
> --- a/drivers/net/wireless/realtek/rtw88/pci.c
> +++ b/drivers/net/wireless/realtek/rtw88/pci.c
> @@ -2,6 +2,7 @@
>  /* Copyright(c) 2018-2019  Realtek Corporation
>   */
> 
> +#include <linux/dmi.h>
>  #include <linux/module.h>
>  #include <linux/pci.h>
>  #include "main.h"
> @@ -1744,6 +1745,34 @@ const struct pci_error_handlers rtw_pci_err_handler = {
>  };
>  EXPORT_SYMBOL(rtw_pci_err_handler);
> 
> +enum rtw88_quirk_dis_pci_caps {
> + QUIRK_DIS_PCI_CAP_ASPM,
> +};
> +
> +static int disable_pci_caps(const struct dmi_system_id *dmi)
> +{
> + uintptr_t dis_caps = (uintptr_t)dmi->driver_data;
> +
> + if (dis_caps & BIT(QUIRK_DIS_PCI_CAP_ASPM))
> + rtw_pci_disable_aspm = true;
> +
> + return 1;
> +}
> +
> +static const struct dmi_system_id rtw88_pci_quirks[] = {
> + {
> + .callback = disable_pci_caps,
> + .ident = "HP Notebook - P3S95EA#ACB",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "HP"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "HP Notebook"),
> + DMI_MATCH(DMI_PRODUCT_SKU, "P3S95EA#ACB"),
> + },
> + .driver_data = (void *)BIT(QUIRK_DIS_PCI_CAP_ASPM),
> + },
> + {}
> +};
> +
>  int rtw_pci_probe(struct pci_dev *pdev,
>     const struct pci_device_id *id)
>  {
> @@ -1808,6 +1837,7 @@ int rtw_pci_probe(struct pci_dev *pdev,
>       bridge && bridge->vendor == PCI_VENDOR_ID_INTEL)
>   rtwpci->rx_no_aspm = true;
> 
> + dmi_check_system(rtw88_pci_quirks);
>   rtw_pci_phy_cfg(rtwdev);
> 
>   ret = rtw_register_hw(rtwdev, hw);
> 
> Results with only this patch applied:
> 
>   - The hard freeze lockup is gone.
>   - However, during idle the logs are flooded with:
> 
>       rtw88_8821ce 0000:13:00.0: failed to send h2c command
>       rtw88_8821ce 0000:13:00.0: firmware failed to leave lps state
> 
>   - To give a concrete sense of the volume: over an ~80-minute
>     observation window after a clean module reload, I recorded
>     11,757 "failed to send h2c command" events and 2 "firmware
>     failed to leave lps state" events -- approximately 110 errors
>     per minute during active periods.
>   - These errors cause Bluetooth audio stuttering and WiFi
>     throughput drops.
> 
> When I additionally set disable_lps_deep=Y alongside your ASPM patch,
> all h2c errors vanish completely and Bluetooth/WiFi remain fully
> stable. This confirms that disabling LPS Deep is necessary for
> complete stability on this specific HP SKU.
> 
> I also noticed what appears to be a new patch in a separate mailing
> list thread. I will test it shortly and report back with the results.

Thanks for your experiments in detail. :)

Ping-Ke

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Ping-Ke Shih <pkshih@realtek.com> wrote:
> To reproduce this reliable, you need to remove driver ko and mac80211.ko,
> and reinstall them.
>
> However, you have confirmed this is the symptom. I think only if you
> want to dig why the rate reported by hardware is weird, otherwise we
> can ignore this warning.

Following your suggestion, I performed a full stack reload including
mac80211.ko and cfg80211.ko, and was able to reproduce the warning:

  [152.226055] Rate marked as a VHT rate but data is invalid: MCS: 0, NSS: 0
  [152.226057] WARNING: net/mac80211/rx.c:5491 at
ieee80211_rx_list+0x177/0x1020 [mac80211]
  [152.226336] CPU: 2 UID: 0 PID: 638 Comm: irq/56-rtw_pci Tainted: G
IOE 6.19.7-1-cachyos
  [152.226344] Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020

One observation worth mentioning: the warning triggered approximately
72 seconds after initial association, coinciding with a Bluetooth
device connecting to the system. This may suggest the NSS=0 condition
occurs during BT coexistence negotiation rather than during normal
WiFi traffic. I am not sure if this is relevant, but I wanted to
mention it in case it helps narrow down the root cause.

I also noticed the offset is now +0x177, which matches exactly what
you showed from v6.19.6. The earlier +0x183 was likely an artifact of
CachyOS's LTO optimizations while mac80211 had been resident for a
long time.

As you noted, this appears to be a separate issue from the freeze and
h2c timeout problems, so I leave it to your judgment whether it
warrants further investigation.

---

I would like to take this opportunity to thank you sincerely for your
time, patience, and expertise throughout this whole process. From your
very first response to the final v2 patch, your guidance made it
possible to properly identify and resolve a bug that had been causing
real frustration for users of this hardware for a long time.

If any further testing of the rtw88 driver is needed -- whether for
this hardware or for other patches -- I am happy to help to the best
of my abilities and available time. This HP Notebook with RTL8821CE
will remain available for testing whenever it is useful.

Best regards,
Oleksandr Havrylov

вт, 17 мар. 2026 г. в 03:28, Ping-Ke Shih <pkshih@realtek.com>:
>
> LB F <goainwo@gmail.com> wrote:
> >
> > Ping-Ke Shih <pkshih@realtek.com> wrote:
> > > Not sure if this is because PCIE bridge has no ASPM capability?
> >
> > That could indeed be the case -- I do not have a way to confirm
> > without further hardware-level inspection.
> >
> > > LN5491 (kernel v6.19.6) is:
> > >                 case RX_ENC_VHT:
> > >                         if (WARN_ONCE(status->rate_idx > 11 ||
> > >                                       !status->nss ||
> > >                                       status->nss > 8,
> > >                                       "Rate marked as a VHT rate but data is
> > invalid: MCS: %d, NSS: %d\n",
> > >                                       status->rate_idx, status->nss))
> > >                                 goto drop;
> > >                         break;
> > > Looks like driver reports improper VHT nss/rate? But this warns once, and
> > > you message isn't like this.
> > > Could you check the source code LN5491 you are using?
> >
> > The file net/mac80211/rx.c is not available on disk on my system
> > (CachyOS ships only .h files in the headers package), but I located
> > the exact warning message in journalctl:
> >
> >   Rate marked as a VHT rate but data is invalid: MCS: 0, NSS: 0
> >
> > This confirms that line 5491 in my kernel matches exactly what you
> > showed from v6.19.6 -- the RX_ENC_VHT case checking for
> > status->nss == 0. The offset in my trace is slightly different
> > (+0x183 vs +0x177), which is likely due to CachyOS's LTO/AutoFDO
> > compiler optimizations.
> >
> > The warning appeared once in my initial test session:
> >
> >   Rate marked as a VHT rate but data is invalid: MCS: 0, NSS: 0
> >   WARNING: net/mac80211/rx.c:5491 at ieee80211_rx_list+0x183/0x1020 [mac80211]
> >
> > However, in subsequent module reload and reconnect cycles I was unable
> > to reproduce it. This is consistent with WARN_ONCE behavior -- it
> > likely fired on the first invalid nss=0 packet after the initial
> > driver load and has not triggered since. I cannot confirm it as a
> > reliable symptom.
>
> To reproduce this reliable, you need to remove driver ko and mac80211.ko,
> and reinstall them.
>
> However, you have confirmed this is the symptom. I think only if you
> want to dig why the rate reported by hardware is weird, otherwise we
> can ignore this warning.
>
> >
> > ---
> >
> > Regarding patch stability: the results below are from testing your
> > original RFT patch [1], not any newer submission. I want to be
> > explicit to avoid confusion:
> >
> >   [1]
> > https://lore.kernel.org/linux-wireless/20260311020816.7065-1-pkshih@realtek.
> > com/
> >
> > This is the exact diff I compiled and tested:
> >
> > --- a/drivers/net/wireless/realtek/rtw88/pci.c
> > +++ b/drivers/net/wireless/realtek/rtw88/pci.c
> > @@ -2,6 +2,7 @@
> >  /* Copyright(c) 2018-2019  Realtek Corporation
> >   */
> >
> > +#include <linux/dmi.h>
> >  #include <linux/module.h>
> >  #include <linux/pci.h>
> >  #include "main.h"
> > @@ -1744,6 +1745,34 @@ const struct pci_error_handlers rtw_pci_err_handler = {
> >  };
> >  EXPORT_SYMBOL(rtw_pci_err_handler);
> >
> > +enum rtw88_quirk_dis_pci_caps {
> > + QUIRK_DIS_PCI_CAP_ASPM,
> > +};
> > +
> > +static int disable_pci_caps(const struct dmi_system_id *dmi)
> > +{
> > + uintptr_t dis_caps = (uintptr_t)dmi->driver_data;
> > +
> > + if (dis_caps & BIT(QUIRK_DIS_PCI_CAP_ASPM))
> > + rtw_pci_disable_aspm = true;
> > +
> > + return 1;
> > +}
> > +
> > +static const struct dmi_system_id rtw88_pci_quirks[] = {
> > + {
> > + .callback = disable_pci_caps,
> > + .ident = "HP Notebook - P3S95EA#ACB",
> > + .matches = {
> > + DMI_MATCH(DMI_SYS_VENDOR, "HP"),
> > + DMI_MATCH(DMI_PRODUCT_NAME, "HP Notebook"),
> > + DMI_MATCH(DMI_PRODUCT_SKU, "P3S95EA#ACB"),
> > + },
> > + .driver_data = (void *)BIT(QUIRK_DIS_PCI_CAP_ASPM),
> > + },
> > + {}
> > +};
> > +
> >  int rtw_pci_probe(struct pci_dev *pdev,
> >     const struct pci_device_id *id)
> >  {
> > @@ -1808,6 +1837,7 @@ int rtw_pci_probe(struct pci_dev *pdev,
> >       bridge && bridge->vendor == PCI_VENDOR_ID_INTEL)
> >   rtwpci->rx_no_aspm = true;
> >
> > + dmi_check_system(rtw88_pci_quirks);
> >   rtw_pci_phy_cfg(rtwdev);
> >
> >   ret = rtw_register_hw(rtwdev, hw);
> >
> > Results with only this patch applied:
> >
> >   - The hard freeze lockup is gone.
> >   - However, during idle the logs are flooded with:
> >
> >       rtw88_8821ce 0000:13:00.0: failed to send h2c command
> >       rtw88_8821ce 0000:13:00.0: firmware failed to leave lps state
> >
> >   - To give a concrete sense of the volume: over an ~80-minute
> >     observation window after a clean module reload, I recorded
> >     11,757 "failed to send h2c command" events and 2 "firmware
> >     failed to leave lps state" events -- approximately 110 errors
> >     per minute during active periods.
> >   - These errors cause Bluetooth audio stuttering and WiFi
> >     throughput drops.
> >
> > When I additionally set disable_lps_deep=Y alongside your ASPM patch,
> > all h2c errors vanish completely and Bluetooth/WiFi remain fully
> > stable. This confirms that disabling LPS Deep is necessary for
> > complete stability on this specific HP SKU.
> >
> > I also noticed what appears to be a new patch in a separate mailing
> > list thread. I will test it shortly and report back with the results.
>
> Thanks for your experiments in detail. :)
>
> Ping-Ke
>

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> Ping-Ke Shih <pkshih@realtek.com> wrote:
> > To reproduce this reliable, you need to remove driver ko and mac80211.ko,
> > and reinstall them.
> >
> > However, you have confirmed this is the symptom. I think only if you
> > want to dig why the rate reported by hardware is weird, otherwise we
> > can ignore this warning.
> 
> Following your suggestion, I performed a full stack reload including
> mac80211.ko and cfg80211.ko, and was able to reproduce the warning:
> 
>   [152.226055] Rate marked as a VHT rate but data is invalid: MCS: 0, NSS: 0
>   [152.226057] WARNING: net/mac80211/rx.c:5491 at
> ieee80211_rx_list+0x177/0x1020 [mac80211]
>   [152.226336] CPU: 2 UID: 0 PID: 638 Comm: irq/56-rtw_pci Tainted: G
> IOE 6.19.7-1-cachyos
>   [152.226344] Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
> 
> One observation worth mentioning: the warning triggered approximately
> 72 seconds after initial association, coinciding with a Bluetooth
> device connecting to the system. This may suggest the NSS=0 condition
> occurs during BT coexistence negotiation rather than during normal
> WiFi traffic. I am not sure if this is relevant, but I wanted to
> mention it in case it helps narrow down the root cause.
> 
> I also noticed the offset is now +0x177, which matches exactly what
> you showed from v6.19.6. The earlier +0x183 was likely an artifact of
> CachyOS's LTO optimizations while mac80211 had been resident for a
> long time.
> 
> As you noted, this appears to be a separate issue from the freeze and
> h2c timeout problems, so I leave it to your judgment whether it
> warrants further investigation.

I add a printk to show the case VHT and NSS==0 as below. Please help to
collect the output, and then I can see what it happened. 

diff --git a/drivers/net/wireless/realtek/rtw88/rx.c b/drivers/net/wireless/realtek/rtw88/rx.c
index 8b0afaaffaa0..a4e3a3bce748 100644
--- a/drivers/net/wireless/realtek/rtw88/rx.c
+++ b/drivers/net/wireless/realtek/rtw88/rx.c
@@ -230,6 +230,11 @@ static void rtw_rx_fill_rx_status(struct rtw_dev *rtwdev,
                                    &rx_status->nss);
        }

+       if (rx_status->encoding == RX_ENC_VHT && rx_status->nss == 0) {
+               printk("VHT NSS=0 pkt_stat->rate=0x%x rx_status->band=%d rx_status->rate_idx=%d\n",
+                       pkt_stat->rate, rx_status->band, rx_status->rate_idx);
+       }
+
        rx_status->flag |= RX_FLAG_MACTIME_START;
        rx_status->mactime = pkt_stat->tsf_low;

> 
> ---
> 
> I would like to take this opportunity to thank you sincerely for your
> time, patience, and expertise throughout this whole process. From your
> very first response to the final v2 patch, your guidance made it
> possible to properly identify and resolve a bug that had been causing
> real frustration for users of this hardware for a long time.

I also thanks for your time and help. :)

Ping-Ke

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Ping-Ke Shih <pkshih@realtek.com> wrote:
> I add a printk to show the case VHT and NSS==0 as below. Please help to
> collect the output, and then I can see what it happened.

Hi Ping-Ke,

I applied your diagnostic patch (using pr_err for maximum log
visibility) and spent the last couple of days testing it on the
affected hardware. The results answer both open questions cleanly.

---

Regarding your earlier question:
> Not sure if this is because PCIE bridge has no ASPM capability?

You were correct. The very beginning of the boot log shows:

  [0.177872] ACPI FADT declares the system doesn't support PCIe ASPM,
              so disable it
  [15.157752] r8169 0000:07:00.0: can't disable ASPM; OS doesn't have
               ASPM control

The BIOS on this HP laptop uses the ACPI FADT table to globally revoke
OS control over PCIe ASPM before Linux even takes over. This has an
important implication: since ASPM is already disabled at the hardware
level by firmware, the instability on this specific SKU is caused
entirely by LPS Deep Mode, not ASPM itself.

This explains why the ASPM-only quirk (v1 patch) did not stop the h2c
timeouts -- ASPM was never actually active on this machine to begin
with. Disabling LPS Deep Mode via the v2 quirk is what eliminates the
firmware timeout loop entirely.

---

Regarding the VHT NSS=0 diagnostic patch:

During normal idle, active pinging, and heavy VHT throughput
(175.5 Mb/s), the pr_err condition never triggered -- no
"VHT NSS=0" lines appeared in dmesg during active use.

However, the standard WARNING at mac80211/rx.c:5491 does reliably
appear exactly once after a fresh full stack reload (including
mac80211.ko and cfg80211.ko) or after resume from suspend:

  [167.708201] WARNING: net/mac80211/rx.c:5491 at
               ieee80211_rx_list+0x177/0x1020 [mac80211]

This suggests the hardware reports a malformed nss=0 VHT rate only
during initial link establishment. Since mac80211 uses WARN_ONCE, it
is suppressed on all subsequent packets.

The diagnostic module remains installed. I will report back
immediately if the pr_err condition is caught, or if any other
relevant symptoms appear.

Best regards,
Oleksandr Havrylov

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Hi Ping-Ke,

I successfully collected the output with your diagnostic printk.

Here is the exact log entry triggered when the warning fires:

[  180.424146] VHT NSS=0 pkt_stat->rate=0x65 rx_status->band=1
rx_status->rate_idx=0
[  180.424157] WARNING: net/mac80211/rx.c:5491 at
ieee80211_rx_list+0x177/0x1020 [mac80211]

Looking at the rtw88 source code, this perfectly explains why `nss` is 0:
1. The hardware/firmware reports `pkt_stat->rate = 0x65` (101 in decimal).
2. `rtw_rx_fill_rx_status()` checks if `pkt_stat->rate >=
DESC_RATEVHT1SS_MCS0` (which is `0x2c`). Since `0x65 >= 0x2c`, it
correctly sets `rx_status->encoding = RX_ENC_VHT`.
3. It then calls `rtw_desc_to_mcsrate(pkt_stat->rate,
&rx_status->rate_idx, &rx_status->nss)`.
4. Inside `rtw_desc_to_mcsrate()`, the value `0x65` falls completely
outside any known bounds. The highest defined rate in `enum
rtw_trx_desc_rate` is `DESC_RATEVHT4SS_MCS9` (`0x53`). The HT range
(`DESC_RATEMCS0` to `DESC_RATEMCS31`) ends at `0x2b`.
5. Because `0x65` matches absolutely none of the `if/else` brackets in
`rtw_desc_to_mcsrate()`, the function simply returns without mutating
`mcs` and `nss`.
6. Since `rx_status` was initialized with `memset(rx_status, 0, ...)`
at the beginning of the function, `rx_status->nss` remains `0`.

So mac80211 complains because the rtw88 driver doesn't know what rate
`0x65` means, leaves NSS at 0, but still flags it as a VHT packet.

Any idea what `0x65` represents from the hardware's perspective? Is it
a firmware bug or a proprietary control/management frame rate index?

Looking forward to your thoughts!

Best regards,
Oleksandr

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> Hi Ping-Ke,
> 
> I successfully collected the output with your diagnostic printk.
> 
> Here is the exact log entry triggered when the warning fires:
> 
> [  180.424146] VHT NSS=0 pkt_stat->rate=0x65 rx_status->band=1
> rx_status->rate_idx=0
> [  180.424157] WARNING: net/mac80211/rx.c:5491 at
> ieee80211_rx_list+0x177/0x1020 [mac80211]
> 
> Looking at the rtw88 source code, this perfectly explains why `nss` is 0:
> 1. The hardware/firmware reports `pkt_stat->rate = 0x65` (101 in decimal).
> 2. `rtw_rx_fill_rx_status()` checks if `pkt_stat->rate >=
> DESC_RATEVHT1SS_MCS0` (which is `0x2c`). Since `0x65 >= 0x2c`, it
> correctly sets `rx_status->encoding = RX_ENC_VHT`.
> 3. It then calls `rtw_desc_to_mcsrate(pkt_stat->rate,
> &rx_status->rate_idx, &rx_status->nss)`.
> 4. Inside `rtw_desc_to_mcsrate()`, the value `0x65` falls completely
> outside any known bounds. The highest defined rate in `enum
> rtw_trx_desc_rate` is `DESC_RATEVHT4SS_MCS9` (`0x53`). The HT range
> (`DESC_RATEMCS0` to `DESC_RATEMCS31`) ends at `0x2b`.
> 5. Because `0x65` matches absolutely none of the `if/else` brackets in
> `rtw_desc_to_mcsrate()`, the function simply returns without mutating
> `mcs` and `nss`.
> 6. Since `rx_status` was initialized with `memset(rx_status, 0, ...)`
> at the beginning of the function, `rx_status->nss` remains `0`.
> 
> So mac80211 complains because the rtw88 driver doesn't know what rate
> `0x65` means, leaves NSS at 0, but still flags it as a VHT packet.
> 
> Any idea what `0x65` represents from the hardware's perspective? Is it
> a firmware bug or a proprietary control/management frame rate index?
> 
> Looking forward to your thoughts!

Not sure what hardware get wrong. Let's validate rate when reading from
hardware. Since 1M rate can only 20MHz, I set it together. 

Please help to test below. I suppose you can see "weird rate=xxx", but 
"WARNING: net/mac80211/rx.c:5491" disappears. 

diff --git a/drivers/net/wireless/realtek/rtw88/rx.c b/drivers/net/wireless/realtek/rtw88/rx.c
index 8b0afaaffaa0..3d5e48264fc5 100644
--- a/drivers/net/wireless/realtek/rtw88/rx.c
+++ b/drivers/net/wireless/realtek/rtw88/rx.c
@@ -295,6 +295,12 @@ void rtw_rx_query_rx_desc(struct rtw_dev *rtwdev, void *rx_desc8,

        pkt_stat->tsf_low = le32_get_bits(rx_desc->w5, RTW_RX_DESC_W5_TSFL);

+       if (pkt_stat->rate >= DESC_RATE_MAX) {
+               printk("weird rate=%d\n", pkt_stat->rate);
+               pkt_stat->rate = DESC_RATE1M;
+               pkt_stat->bw = RTW_CHANNEL_WIDTH_20;
+       }
+
        /* drv_info_sz is in unit of 8-bytes */
        pkt_stat->drv_info_sz *= 8;

Ping-Ke

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> Ping-Ke Shih <pkshih@realtek.com> wrote:
> > I add a printk to show the case VHT and NSS==0 as below. Please help to
> > collect the output, and then I can see what it happened.
> 
> Hi Ping-Ke,
> 
> I applied your diagnostic patch (using pr_err for maximum log
> visibility) and spent the last couple of days testing it on the
> affected hardware. The results answer both open questions cleanly.
> 
> ---
> 
> Regarding your earlier question:
> > Not sure if this is because PCIE bridge has no ASPM capability?
> 
> You were correct. The very beginning of the boot log shows:
> 
>   [0.177872] ACPI FADT declares the system doesn't support PCIe ASPM,
>               so disable it
>   [15.157752] r8169 0000:07:00.0: can't disable ASPM; OS doesn't have
>                ASPM control
> 
> The BIOS on this HP laptop uses the ACPI FADT table to globally revoke
> OS control over PCIe ASPM before Linux even takes over. This has an
> important implication: since ASPM is already disabled at the hardware
> level by firmware, the instability on this specific SKU is caused
> entirely by LPS Deep Mode, not ASPM itself.

Checking rtw88 code related to rtw_pci_disable_aspm, I found that driver
does check device ASPM capability before configuring ASPM. It looks 
a little weird why OS doesn't turn off these capabilities of device.
Maybe we should check the capabilities of PCI bridge side? 

> 
> This explains why the ASPM-only quirk (v1 patch) did not stop the h2c
> timeouts -- ASPM was never actually active on this machine to begin
> with. Disabling LPS Deep Mode via the v2 quirk is what eliminates the
> firmware timeout loop entirely.

I think there are two problems. One is ASPM causing system frozen, and
the other is LPS deep mode causing H2C timeouts. If you turn on ASPM
and disable LPS deep mode, I feel H2C timeout can disappear, but it
might go frozen first though. 

Ping-Ke

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Ping-Ke Shih <pkshih@realtek.com> wrote:
> Maybe we should check the capabilities of PCI bridge side?
> I think there are two problems. One is ASPM causing system frozen,
> and the other is LPS deep mode causing H2C timeouts.

Hi Ping-Ke,

You were right on both counts. Here are the PCI bridge capabilities.

The upstream bridge for the RTL8821CE (13:00.0) is:
  Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (00:1c.4)

Bridge (00:1c.4):
  LnkCap: Port #5, Speed 5GT/s, Width x1, ASPM L0s L1,
          Exit Latency L0s <512ns, L1 <16us
  LnkCtl: ASPM L0s L1 Enabled

WiFi card (13:00.0):
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
          Exit Latency L0s <2us, L1 <64us
  LnkCtl: ASPM L0s L1 Enabled

So ASPM L0s and L1 are enabled by the BIOS on both ends of the bus,
despite the ACPI FADT claiming the OS has no ASPM control. ASPM was
active on this machine all along. I apologize for the incorrect
earlier conclusion that ASPM was not active.

This confirms your analysis: there are indeed two separate problems --
ASPM causing the hard freeze, and LPS Deep Mode causing the H2C
timeouts. The v2 patch correctly addresses both.

---

Regarding your rate validation patch: I applied it (removing the
earlier pr_err block and inserting the new check in
rtw_rx_query_rx_desc). The patch compiled and installed correctly --
verified via strings on the installed .zst module.

I was unable to reproduce the "weird rate" condition or the WARNING
during this test session. The diagnostic module remains installed and
active -- I will report back immediately if I manage to catch it.

Best regards,
Oleksandr Havrylov

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Ping-Ke Shih <pkshih@realtek.com> wrote:
> Not sure what hardware get wrong. Let's validate rate when reading
> from hardware.

Hi Ping-Ke,

One additional observation while monitoring logs with your rate
validation patch installed.

During normal usage with Wi-Fi connected and a Bluetooth A2DP device
connecting to the system, the following message appeared in dmesg:

  [180.420000] rtw_8821ce 0000:13:00.0: unused phy status page (11)

Looking at rtw_rx_fill_phy_info() in rx.c, this message is emitted
when the firmware sends a PHY status report with a page number that
the driver does not recognize. In this case page 11 appeared at the
moment the Bluetooth device was establishing its connection.

We have not observed any stability issues or connectivity drops
associated with this message -- the driver appears to handle it
gracefully by ignoring it. We are not sure whether this is related
to the rate=0x65 issue or is simply a separate artifact of BT/Wi-Fi
coexistence on this chip. We wanted to mention it in case it is
useful context.

Best regards,
Oleksandr Havrylov

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> Ping-Ke Shih <pkshih@realtek.com> wrote:
> > Not sure what hardware get wrong. Let's validate rate when reading
> > from hardware.
> 
> Hi Ping-Ke,
> 
> One additional observation while monitoring logs with your rate
> validation patch installed.
> 
> During normal usage with Wi-Fi connected and a Bluetooth A2DP device
> connecting to the system, the following message appeared in dmesg:
> 
>   [180.420000] rtw_8821ce 0000:13:00.0: unused phy status page (11)
> 
> Looking at rtw_rx_fill_phy_info() in rx.c, this message is emitted
> when the firmware sends a PHY status report with a page number that
> the driver does not recognize. In this case page 11 appeared at the
> moment the Bluetooth device was establishing its connection.

It seems like hardware reports incorrect about the PHY status, which
only 0 or 1 is expected. I don't know how it could be. Maybe, we
can ignore this message, or change it to debug level if it appears
frequently and you don't want to see it.

> 
> We have not observed any stability issues or connectivity drops
> associated with this message -- the driver appears to handle it
> gracefully by ignoring it. We are not sure whether this is related
> to the rate=0x65 issue or is simply a separate artifact of BT/Wi-Fi
> coexistence on this chip. We wanted to mention it in case it is
> useful context.

Two messages look like hardware goes weird. The report values become
unpredictable. Maybe we need more validation.... However, driver
will become very dirty since I can't conclude a single rule to
address them.

Ping-Ke

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Ping-Ke Shih <pkshih@realtek.com> wrote:
> Not sure what hardware get wrong. Let's validate rate when reading
> from hardware. Since 1M rate can only 20MHz, I set it together.
> Please help to test below. I suppose you can see "weird rate=xxx",
> but "WARNING: net/mac80211/rx.c:5491" disappears.

Hi Ping-Ke,

I can confirm your patch works as expected. Here are the full results.

--- Test environment ---

Kernel:  6.19.7-1-cachyos
Patch:   your rate validation patch applied to rtw_rx_query_rx_desc(),
         on top of the v2 DMI quirk (ASPM + LPS Deep disabled)

--- Captured log (relevant excerpt) ---

  [  43.046] input: Soundcore Q10i (AVRCP)   <-- BT headset connected
  [ 111.551] rtw_8821ce 0000:13:00.0: unused phy status page (13)
  [ 111.635] weird rate=101
  [ 111.635] rtw_8821ce 0000:13:00.0: unused phy status page (7)
  [ 111.741] weird rate=102
  [ 115.045] weird rate=98
  [ 118.371] weird rate=104

--- Analysis ---

1. Timing: the anomalous events began approximately 68 seconds after
   the Bluetooth A2DP headset (Soundcore Q10i) established its
   connection. No anomalies were observed before BT connected.

2. Multiple invalid rate values were captured, not just 0x65:

     weird rate=101  (0x65)
     weird rate=102  (0x66)
     weird rate=98   (0x62)
     weird rate=104  (0x68)

   All four values exceed DESC_RATE_MAX (0x53 = 83 decimal). This
   suggests the hardware occasionally reports a range of out-of-bounds
   rate values during BT/Wi-Fi coexistence, not a single fixed value.

3. The "unused phy status page" messages (pages 13 and 7) appeared
   immediately before and alongside the "weird rate" events. As noted
   in my previous message, only pages 0 and 1 are expected. This
   further suggests the firmware leaks internal coexistence state
   into the RX ring during BT antenna arbitration.

4. Most importantly: the WARNING: net/mac80211/rx.c:5491 did NOT
   appear anywhere in the log. Your rate clamping patch successfully
   intercepts the out-of-bounds values before they propagate to
   mac80211, preventing the invalid VHT NSS=0 warning entirely.

--- Conclusion ---

Your patch achieves the intended result. The "weird rate" printk
confirms the hardware is the source of the invalid values (occurring
during BT coexistence), and the mac80211 WARNING is suppressed.

Please let me know if you need any additional data or further testing.

Best regards,
Oleksandr Havrylov

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> Ping-Ke Shih <pkshih@realtek.com> wrote:
> > Not sure what hardware get wrong. Let's validate rate when reading
> > from hardware. Since 1M rate can only 20MHz, I set it together.
> > Please help to test below. I suppose you can see "weird rate=xxx",
> > but "WARNING: net/mac80211/rx.c:5491" disappears.
> 
> Hi Ping-Ke,
> 
> I can confirm your patch works as expected. Here are the full results.
> 
> --- Test environment ---
> 
> Kernel:  6.19.7-1-cachyos
> Patch:   your rate validation patch applied to rtw_rx_query_rx_desc(),
>          on top of the v2 DMI quirk (ASPM + LPS Deep disabled)
> 
> --- Captured log (relevant excerpt) ---
> 
>   [  43.046] input: Soundcore Q10i (AVRCP)   <-- BT headset connected
>   [ 111.551] rtw_8821ce 0000:13:00.0: unused phy status page (13)
>   [ 111.635] weird rate=101
>   [ 111.635] rtw_8821ce 0000:13:00.0: unused phy status page (7)
>   [ 111.741] weird rate=102
>   [ 115.045] weird rate=98
>   [ 118.371] weird rate=104
> 
> --- Analysis ---
> 
> 1. Timing: the anomalous events began approximately 68 seconds after
>    the Bluetooth A2DP headset (Soundcore Q10i) established its
>    connection. No anomalies were observed before BT connected.
> 
> 2. Multiple invalid rate values were captured, not just 0x65:
> 
>      weird rate=101  (0x65)
>      weird rate=102  (0x66)
>      weird rate=98   (0x62)
>      weird rate=104  (0x68)
> 
>    All four values exceed DESC_RATE_MAX (0x53 = 83 decimal). This
>    suggests the hardware occasionally reports a range of out-of-bounds
>    rate values during BT/Wi-Fi coexistence, not a single fixed value.
> 
> 3. The "unused phy status page" messages (pages 13 and 7) appeared
>    immediately before and alongside the "weird rate" events. As noted
>    in my previous message, only pages 0 and 1 are expected. This
>    further suggests the firmware leaks internal coexistence state
>    into the RX ring during BT antenna arbitration.
> 
> 4. Most importantly: the WARNING: net/mac80211/rx.c:5491 did NOT
>    appear anywhere in the log. Your rate clamping patch successfully
>    intercepts the out-of-bounds values before they propagate to
>    mac80211, preventing the invalid VHT NSS=0 warning entirely.
> 
> --- Conclusion ---
> 
> Your patch achieves the intended result. The "weird rate" printk
> confirms the hardware is the source of the invalid values (occurring
> during BT coexistence), and the mac80211 WARNING is suppressed.
> 
> Please let me know if you need any additional data or further testing.

I'll send formal patch (Cc you) for the invalid VHT NSS=0, but not to
handle "unused phy status page". Please give me Tested-by tag on the
patch after I send it.

Ping-Ke

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Ping-Ke Shih <pkshih@realtek.com> wrote:
> I'll send formal patch (Cc you) for the invalid VHT NSS=0, but not
> to handle "unused phy status page". Please give me Tested-by tag on
> the patch after I send it.

Hi Ping-Ke,

Just a quick update to keep you informed -- no rush on anything.

My kernel updated from 6.19.7 to 6.19.9, which wiped the previously
installed out-of-tree modules. I rebuilt and reinstalled both patches:

  1. The v2 DMI quirk (main.h + pci.c) disabling ASPM and LPS Deep
     Mode for the HP P3S95EA#ACB SKU.
  2. The rate validation patch (rx.c) clamping out-of-bounds rate
     values before they reach mac80211.

Both patches apply cleanly and the system remains fully stable on
6.19.9. The DMI quirk is confirmed active via sysfs (disable_aspm=Y,
disable_lps_deep=Y) with no manual modprobe overrides.

I am looking forward to your formal patch for the VHT NSS=0 issue and
will provide a Tested-by tag as soon as it arrives. Thank you again
for all your work and patience throughout this process.

Best regards,
Oleksandr Havrylov

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> Ping-Ke Shih <pkshih@realtek.com> wrote:
> > I'll send formal patch (Cc you) for the invalid VHT NSS=0, but not
> > to handle "unused phy status page". Please give me Tested-by tag on
> > the patch after I send it.
> 
> Hi Ping-Ke,
> 
> Just a quick update to keep you informed -- no rush on anything.
> 
> My kernel updated from 6.19.7 to 6.19.9, which wiped the previously
> installed out-of-tree modules. I rebuilt and reinstalled both patches:
> 
>   1. The v2 DMI quirk (main.h + pci.c) disabling ASPM and LPS Deep
>      Mode for the HP P3S95EA#ACB SKU.
>   2. The rate validation patch (rx.c) clamping out-of-bounds rate
>      values before they reach mac80211.
> 
> Both patches apply cleanly and the system remains fully stable on
> 6.19.9. The DMI quirk is confirmed active via sysfs (disable_aspm=Y,
> disable_lps_deep=Y) with no manual modprobe overrides.
> 
> I am looking forward to your formal patch for the VHT NSS=0 issue and
> will provide a Tested-by tag as soon as it arrives. Thank you again
> for all your work and patience throughout this process.

I sent the VHT NSS=0 patch [1]. Please help to give it a test.
Thanks.

[1] https://lore.kernel.org/linux-wireless/20260323015849.9424-1-pkshih@realtek.com/T/#u

Ping-Ke

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Subject: Cross-platform analysis: RTL8821CE ASPM/LPS instability
        affects multiple OEM platforms beyond HP P3S95EA#ACB

Hi Ping-Ke,

First of all, thank you very much for your work on the rtw88 driver
and for the time you spent helping us resolve the issues on our HP
laptop. Both patches -- the v2 DMI quirk (ASPM + LPS Deep) and the
v2 RX rate validation (rx.c) -- have been tested and verified stable
on our system across two kernel updates (6.19.9-1 and 6.19.9-2),
sustained network load (~1.9 GB), and multiple suspend/resume cycles.
The system is now completely free of freezes, h2c errors, and
mac80211 warnings. Your patches genuinely solved every issue we had.

While working through this, I noticed that many other users across
different hardware platforms appear to be experiencing the same
problems that your patches resolved for us. I decided to collect
and organize these observations in case they might be useful to you.

Please note that this is an amateur analysis, not a professional
one -- I am just a user trying to help. It is entirely possible
that I have missed nuances or made incorrect assumptions. My only
goal is to share what I found, in case it provides useful data
points or sparks ideas for broader improvements. If any of this
is not relevant or not useful, please feel free to disregard it.


1. KERNEL BUGZILLA: OPEN RTL8821CE REPORTS
==========================================

I reviewed all open RTL8821CE bugs in kernel.org Bugzilla. Three
of the six show symptoms that directly match the root causes
addressed by your patches (ASPM deadlock and LPS Deep h2c failures).

--- Directly correlated with ASPM/LPS patches ---

Bug 215131 - System freeze (ASPM L1 deadlock)
  Title:    "Realtek 8821CE makes the system freeze after 9e2fd29864c5
             (rtw88: add napi support)"
  Reporter: Kai-Heng Feng (Canonical)
  Kernel:   5.15+
  Symptoms: Hard freeze preceded by "pci bus timeout, check dma status"
            warnings. RX tag mismatch in rtw_pci_dma_check().
  Workaround confirmed by reporter: rtw88_pci.disable_aspm=1
  Reporter note: "disable_aspm=1 is not a viable workaround because
                  it increases power consumption significantly"
  Status:   OPEN since 2021-11-24.
  Link:     https://bugzilla.kernel.org/show_bug.cgi?id=215131
  Relevance: Identical root cause to Bug 221195. The reporter's
             confirmed workaround (disable_aspm=1) is exactly what
             the DMI quirk implements.

Bug 219830 - h2c/LPS failures + BT crackling
  Title:    "rtw88_8821ce (RTL8821CE) slow performance and error
             messages in dmesg"
  Reporter: Bmax Y14 laptop, Fedora 41, kernel 6.13.5
  Symptoms: - "failed to send h2c command" (periodic)
            - "firmware failed to leave lps state" (periodic)
            - Lower signal strength vs Windows
            - Bluetooth crackling during audio playback
  Cross-ref: https://github.com/lwfinger/rtw88/issues/306
  Status:   OPEN since 2025-03-02.
  Link:     https://bugzilla.kernel.org/show_bug.cgi?id=219830
  Relevance: The h2c/lps errors are the same messages we observed
             before the DMI quirk disabled LPS Deep Mode. The BT
             crackling may correlate with the invalid RX rate
             condition addressed by your rx.c validation patch.

Bug 218697 - TX queue flush timeout during scan
  Title:    "rtw88_8821ce timed out to flush queue 2"
  Reporter: Arch Linux, kernel 6.8.4 / 6.8.5
  Symptoms: - "timed out to flush queue 2" every ~30 seconds
            - "failed to get tx report from firmware"
            - Stack trace: ieee80211_scan_work -> rtw_ops_flush ->
              rtw_mac_flush_queues timeout
  Status:   OPEN since 2024-04-08.
  Link:     https://bugzilla.kernel.org/show_bug.cgi?id=218697
  Relevance: The flush timeout occurs when the firmware cannot
             respond to TX queue operations -- consistent with
             firmware being stuck in LPS Deep during scan.

--- Potentially related (no confirmed workaround data) ---

Bug 217491 - "timed out to flush queue 1" regression (kernel 6.3)
  Manjaro user. Floods of "timed out to flush queue 1/2".
  Similar pattern to Bug 218697.
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=217491

Bug 217781 - Random sudden dropouts
  Arch user. Random disconnections during streaming/transfers.
  Reproduced on Ubuntu and Fedora (kernels 5.15 to 6.4).
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=217781

Bug 216685 - Low wireless speed
  Reduced throughput vs expected 802.11ac performance.
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=216685


2. SYMPTOM-TO-PATCH MAPPING
=============================

dmesg signature                    Patch that resolves it
--------------------------         ----------------------
Hard system freeze                 pci.c DMI quirk (disable ASPM)
"pci bus timeout, check dma"       pci.c DMI quirk (disable ASPM)
"firmware failed to leave lps"     pci.c DMI quirk (disable LPS Deep)
"failed to send h2c command"       pci.c DMI quirk (disable LPS Deep)
"timed out to flush queue N"       pci.c DMI quirk (disable LPS Deep) [1]
"failed to get tx report"          pci.c DMI quirk (disable LPS Deep) [1]
VHT NSS=0 mac80211 WARNING        rx.c rate validation (v2)

Confirmed in bugs: 215131, 219830, 218697, 221195.
[1] Inferred: flush timeout occurs when firmware cannot exit LPS
    to process TX queue operations.


3. AFFECTED HARDWARE
=====================

Current DMI quirk coverage: HP P3S95EA#ACB only.

Platforms confirmed affected in Bugzilla:
  Bug 221195: HP Notebook 81F0 (P3S95EA#ACB)
  Bug 215131: unknown (Canonical upstream testing)
  Bug 219830: Bmax Y14
  Bug 218697: unknown (Arch Linux user)

Platforms reported in community forums as requiring
disable_aspm=Y and/or disable_lps_deep=Y for stable RTL8821CE:
  - HP 17-by4063CL
  - Lenovo IdeaPad S145-15AST, IdeaPad 3, IdeaPad 330S
  - ASUS VivoBook X series
  - Acer Aspire 3/5 series

All use PCI Device ID 10ec:c821 with different Subsystem IDs.


4. LPS_DEEP_MODE_LCLK IN THE rtw88 TREE
=========================================

I verified in the source which chips have the same
lps_deep_mode_supported flag:

Chip file       lps_deep_mode_supported            PCIe variant
---------       -----------------------            ------------
rtw8821c.c      BIT(LPS_DEEP_MODE_LCLK)            rtw8821ce ✓
rtw8822c.c      BIT(LPS_DEEP_MODE_LCLK) | PG       rtw8822ce ✓
rtw8822b.c      BIT(LPS_DEEP_MODE_LCLK)            rtw8822be ✓
rtw8814a.c      BIT(LPS_DEEP_MODE_LCLK)            rtw8814ae ✓
rtw8723d.c      0                                   rtw8723de ✗
rtw8703b.c      0                                   (SDIO)     -
rtw8821a.c      0                                   (legacy)   -

Source references:
  rtw8821c.c:2002  rtw8822c.c:5365  rtw8822b.c:2545
  rtw8814a.c:2211  rtw8723d.c:2144

RTL8822CE community reports (Manjaro, Arch forums) confirm the
same disable_aspm=Y + disable_lps_deep=Y workaround is effective,
consistent with rtw8822c.c having LCLK enabled.


5. COMMUNITY WORKAROUND REFERENCES
====================================

The following are concrete examples of forums and wikis where the
same modprobe workarounds are actively recommended:

Arch Wiki - RTW88 section:
  https://wiki.archlinux.org/title/Network_configuration/Wireless
  (section "RTW88" and "rtl8821ce" under Troubleshooting/Realtek)
  Recommends rtw88-dkms-git and documents the rtw88_8821ce issues.

Arch Wiki - RTW89 section (same page):
  Documents the identical ASPM pattern for the newer RTW89 driver:
    options rtw89_pci disable_aspm_l1=y disable_aspm_l1ss=y
    options rtw89_core disable_ps_mode=y
  This suggests the ASPM/LPS interaction is a systemic Realtek
  design issue, not specific to rtw88 or the 8821CE chip.

Arch Linux Forum - RTL8821CE thread:
  https://bbs.archlinux.org/viewtopic.php?id=273440
  Referenced by the Arch Wiki as the primary rtl8821ce discussion.

lwfinger/rtw88 GitHub:
  https://github.com/lwfinger/rtw88/issues/306
  Directly cross-referenced by Bug 219830. Reporter reports h2c
  errors and investigated antenna hardware (no fault found).

lwfinger/rtw89 GitHub:
  https://github.com/lwfinger/rtw89/issues/275#issuecomment-1784155449
  Same ASPM-disable pattern documented for the newer RTW89 driver
  on HP and Lenovo laptops.


6. OBSERVATIONS
================

a) Three open Bugzilla reporters (215131, 219830, 218697) show
   symptoms identical to those resolved by your patches but have
   no upstream fix available since they are not the HP P3S95EA#ACB.

b) Bug 215131 reporter (Kai-Heng Feng, Canonical) explicitly
   confirmed disable_aspm=1 as a workaround and called it
   "not viable" due to power cost. A DMI quirk for their
   platform would give them a proper fix.

c) The Arch Wiki documents the same ASPM-disable pattern for
   both RTW88 and RTW89 drivers, suggesting the underlying
   hardware/firmware limitation is shared across generations.

d) Asking Bugzilla reporters to provide their DMI data
   (dmidecode -t 1,2) could allow extending the quirk table
   with minimal effort and zero risk to unaffected platforms.

e) The rx.c rate validation patch is chip-agnostic and requires
   no platform-specific consideration.


7. REFERENCES
==============

Kernel Bugzilla:
  https://bugzilla.kernel.org/show_bug.cgi?id=215131
  https://bugzilla.kernel.org/show_bug.cgi?id=219830
  https://bugzilla.kernel.org/show_bug.cgi?id=218697
  https://bugzilla.kernel.org/show_bug.cgi?id=217491
  https://bugzilla.kernel.org/show_bug.cgi?id=217781
  https://bugzilla.kernel.org/show_bug.cgi?id=216685

GitHub:
  https://github.com/lwfinger/rtw88/issues/306
  https://github.com/lwfinger/rtw89/issues/275

Arch Wiki:
  https://wiki.archlinux.org/title/Network_configuration/Wireless

Arch Linux Forum:
  https://bbs.archlinux.org/viewtopic.php?id=273440

Source code (lps_deep_mode_supported):
  drivers/net/wireless/realtek/rtw88/rtw8821c.c:2002
  drivers/net/wireless/realtek/rtw88/rtw8822c.c:5365
  drivers/net/wireless/realtek/rtw88/rtw8822b.c:2545
  drivers/net/wireless/realtek/rtw88/rtw8814a.c:2211
  drivers/net/wireless/realtek/rtw88/rtw8723d.c:2144


Best regards,
Oleksandr Havrylov <goainwo@gmail.com>

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Hi Ping-Ke,

This is Oleksandr Havrylov again. Thank you for the ASPM/LPS Deep
quirk and the rate validation patches — they are both working correctly
(zero h2c timeouts, zero lps failures, zero mac80211 warnings).

However, I'm experiencing a different, separate bug that causes kernel
oops and makes the system completely unresponsive, requiring a hard
power-off. After disassembling the crash site, I believe I've found
the root cause.

== Summary ==

When firmware sends a C2H_ADAPTIVITY (0x37) command to an RTL8821CE
adapter, rtw_fw_adaptivity_result() dereferences rtwdev->chip->edcca_th
without a NULL check. The RTL8821C chip_info (rtw8821c_hw_spec) does
not define edcca_th, so the pointer is NULL, causing a kernel oops.

The crash occurs on the phy0 workqueue while holding rtwdev->mutex,
which never gets released. This causes all subsequent processes that
touch the network stack to hang in uninterruptible D-state, making
the system completely unresponsive and requiring a hard power-off.

== Root cause analysis ==

rtw_fw_adaptivity_result() in fw.c (line ~282):

  static void rtw_fw_adaptivity_result(struct rtw_dev *rtwdev, u8 *payload,
                                       u8 length)
  {
      const struct rtw_hw_reg_offset *edcca_th = rtwdev->chip->edcca_th;
      ...
      rtw_dbg(rtwdev, RTW_DBG_ADAPTIVITY, "Reg Setting: L2H %x H2L %x\n",
              rtw_read32_mask(rtwdev, edcca_th[EDCCA_TH_L2H_IDX].hw_reg.addr,
                                             ^^^^^^^^^ NULL dereference here
                              edcca_th[EDCCA_TH_L2H_IDX].hw_reg.mask),
              ...

The RTL8822C defines .edcca_th = rtw8822c_edcca_th in its chip_info,
but RTL8821C does not set this field at all — it remains NULL.

I verified this by disassembling the compiled rtw_core.ko module:

  Crash RIP: rtw_fw_c2h_cmd_handle+0x127
  Address:   0x1d527 = movl (%r12), %esi

  R12 is loaded at +0xe5 (0x1d4e5):
    movq 0x140(%rax), %r12    ; rax = rtwdev->chip
                              ; 0x140 = offset of edcca_th in rtw_chip_info
                              ; R12 = chip->edcca_th = NULL for 8821c

  The function is entered via:
    +0xd8 (0x1d4d8): cmpl $0x37, %ecx  ; c2h->id == C2H_ADAPTIVITY (0x37)

  With R12 = 0, the instruction at +0x127:
    movl (%r12), %esi   ; reads from address 0x0 → NULL pointer dereference

I also confirmed that rtw8821c_hw_spec in the mainline kernel
(torvalds/linux master, rtw8821c.c) does NOT set .edcca_th.

== Reproduction ==

The crash is highly reproducible: it occurred in 4 out of 7 recent
boots. It happens during normal active usage with no specific trigger.

  boot  date/time of crash         uptime at crash
  -5    2026-03-25 00:58:06        ~2 min
  -4    2026-03-25 21:32:00        ~6h
  -3    2026-03-26 00:28:14        ~2.5h
  -1    2026-03-27 00:56:58        ~23.5h

Both ASPM and LPS Deep are disabled via the DMI quirk. The crash
occurs every time with the same pattern and same RIP offset (+0x127).

== Crash pattern ==

Every crash follows the same sequence:

  1) Burst of 50-60 "unused phy status page" messages in ~1 second:

     rtw_8821ce 0000:13:00.0: unused phy status page (8)
     rtw_8821ce 0000:13:00.0: unused phy status page (2)
     ... (50+ more within same second)

  2) Immediately followed by the kernel oops:

     BUG: kernel NULL pointer dereference, address: 0000000000000000
     Oops: 0000 [#1] SMP PTI
     Workqueue: phy0 rtw_c2h_work [rtw_core]
     RIP: 0010:rtw_fw_c2h_cmd_handle+0x127/0x380 [rtw_core]

     CR2: 0000000000000000
     R12: 0000000000000000   ← edcca_th = NULL

     Call Trace:
      <TASK>
      rtw_c2h_work+0x49/0x70 [rtw_core]
      process_scheduled_works+0x1f3/0x5e0
      worker_thread+0x18d/0x340
      </TASK>

     note: kworker/u16:6[262] exited with irqs disabled

  3) After the oops, processes hang in D-state indefinitely:
     warp-svc, avahi-daemon, kdeconnectd — all survive SIGKILL,
     making clean shutdown impossible.

== Suggested fix ==

Add a NULL check for edcca_th in rtw_fw_adaptivity_result():

  static void rtw_fw_adaptivity_result(struct rtw_dev *rtwdev, u8 *payload,
                                       u8 length)
  {
      const struct rtw_hw_reg_offset *edcca_th = rtwdev->chip->edcca_th;
      struct rtw_c2h_adaptivity *result = (struct rtw_c2h_adaptivity *)payload;

  +   if (!edcca_th)
  +       return;
  +
      rtw_dbg(rtwdev, RTW_DBG_ADAPTIVITY,
              ...

Alternatively, the C2H_ADAPTIVITY case in rtw_fw_c2h_cmd_handle()
could check edcca_th before calling the handler. However, since
RTL8821CE firmware does occasionally send C2H_ADAPTIVITY commands
(as observed in this bug), you may have a better understanding of
whether a more complete fix is needed (e.g., defining edcca_th for
RTL8821C, or preventing the firmware from sending C2H_ADAPTIVITY
responses when the feature is not fully configured).

== Hardware ==

  Machine:   HP HP Notebook (board: 81F0, SKU: P3S95EA#ACB)
  Adapter:   RTL8821CE (PCI 10ec:c821, bus 0000:13:00.0)
  CPU:       Intel 5005U
  Kernel:    6.19.9-2-cachyos (PREEMPT full, SMP PTI, LLVM build)
  Driver:    lwfinger/rtw88 out-of-tree with DMI quirk + rate v2

== Confirmation that this is NOT a local modification ==

I verified that:
  - fw.c: rtw_fw_c2h_cmd_handle() and rtw_fw_adaptivity_result() are
    byte-for-byte identical to torvalds/linux master and lwfinger/rtw88
  - rtw8821c.c: rtw8821c_hw_spec does not define .edcca_th in any of
    the three sources (mainline, lwfinger, our local copy)
  - The only local modifications are your DMI quirk (pci.c + main.h)
    and rate validation v2 (rx.c). Neither touches fw.c.

Please let me know if you need additional diagnostics or if you'd
like me to test a patch.

Best regards,
Oleksandr Havrylov <goainwo@gmail.com>

Tested on:
  Kernel: 6.19.9-2-cachyos
  Driver: lwfinger/rtw88 out-of-tree with DMI quirk + rate v2 patch
  Distro: CachyOS (Arch-based)

ср, 25 мар. 2026 г. в 22:38, LB F <goainwo@gmail.com>:
>
> Subject: Cross-platform analysis: RTL8821CE ASPM/LPS instability
>         affects multiple OEM platforms beyond HP P3S95EA#ACB
>
> Hi Ping-Ke,
>
> First of all, thank you very much for your work on the rtw88 driver
> and for the time you spent helping us resolve the issues on our HP
> laptop. Both patches -- the v2 DMI quirk (ASPM + LPS Deep) and the
> v2 RX rate validation (rx.c) -- have been tested and verified stable
> on our system across two kernel updates (6.19.9-1 and 6.19.9-2),
> sustained network load (~1.9 GB), and multiple suspend/resume cycles.
> The system is now completely free of freezes, h2c errors, and
> mac80211 warnings. Your patches genuinely solved every issue we had.
>
> While working through this, I noticed that many other users across
> different hardware platforms appear to be experiencing the same
> problems that your patches resolved for us. I decided to collect
> and organize these observations in case they might be useful to you.
>
> Please note that this is an amateur analysis, not a professional
> one -- I am just a user trying to help. It is entirely possible
> that I have missed nuances or made incorrect assumptions. My only
> goal is to share what I found, in case it provides useful data
> points or sparks ideas for broader improvements. If any of this
> is not relevant or not useful, please feel free to disregard it.
>
>
> 1. KERNEL BUGZILLA: OPEN RTL8821CE REPORTS
> ==========================================
>
> I reviewed all open RTL8821CE bugs in kernel.org Bugzilla. Three
> of the six show symptoms that directly match the root causes
> addressed by your patches (ASPM deadlock and LPS Deep h2c failures).
>
> --- Directly correlated with ASPM/LPS patches ---
>
> Bug 215131 - System freeze (ASPM L1 deadlock)
>   Title:    "Realtek 8821CE makes the system freeze after 9e2fd29864c5
>              (rtw88: add napi support)"
>   Reporter: Kai-Heng Feng (Canonical)
>   Kernel:   5.15+
>   Symptoms: Hard freeze preceded by "pci bus timeout, check dma status"
>             warnings. RX tag mismatch in rtw_pci_dma_check().
>   Workaround confirmed by reporter: rtw88_pci.disable_aspm=1
>   Reporter note: "disable_aspm=1 is not a viable workaround because
>                   it increases power consumption significantly"
>   Status:   OPEN since 2021-11-24.
>   Link:     https://bugzilla.kernel.org/show_bug.cgi?id=215131
>   Relevance: Identical root cause to Bug 221195. The reporter's
>              confirmed workaround (disable_aspm=1) is exactly what
>              the DMI quirk implements.
>
> Bug 219830 - h2c/LPS failures + BT crackling
>   Title:    "rtw88_8821ce (RTL8821CE) slow performance and error
>              messages in dmesg"
>   Reporter: Bmax Y14 laptop, Fedora 41, kernel 6.13.5
>   Symptoms: - "failed to send h2c command" (periodic)
>             - "firmware failed to leave lps state" (periodic)
>             - Lower signal strength vs Windows
>             - Bluetooth crackling during audio playback
>   Cross-ref: https://github.com/lwfinger/rtw88/issues/306
>   Status:   OPEN since 2025-03-02.
>   Link:     https://bugzilla.kernel.org/show_bug.cgi?id=219830
>   Relevance: The h2c/lps errors are the same messages we observed
>              before the DMI quirk disabled LPS Deep Mode. The BT
>              crackling may correlate with the invalid RX rate
>              condition addressed by your rx.c validation patch.
>
> Bug 218697 - TX queue flush timeout during scan
>   Title:    "rtw88_8821ce timed out to flush queue 2"
>   Reporter: Arch Linux, kernel 6.8.4 / 6.8.5
>   Symptoms: - "timed out to flush queue 2" every ~30 seconds
>             - "failed to get tx report from firmware"
>             - Stack trace: ieee80211_scan_work -> rtw_ops_flush ->
>               rtw_mac_flush_queues timeout
>   Status:   OPEN since 2024-04-08.
>   Link:     https://bugzilla.kernel.org/show_bug.cgi?id=218697
>   Relevance: The flush timeout occurs when the firmware cannot
>              respond to TX queue operations -- consistent with
>              firmware being stuck in LPS Deep during scan.
>
> --- Potentially related (no confirmed workaround data) ---
>
> Bug 217491 - "timed out to flush queue 1" regression (kernel 6.3)
>   Manjaro user. Floods of "timed out to flush queue 1/2".
>   Similar pattern to Bug 218697.
>   Link: https://bugzilla.kernel.org/show_bug.cgi?id=217491
>
> Bug 217781 - Random sudden dropouts
>   Arch user. Random disconnections during streaming/transfers.
>   Reproduced on Ubuntu and Fedora (kernels 5.15 to 6.4).
>   Link: https://bugzilla.kernel.org/show_bug.cgi?id=217781
>
> Bug 216685 - Low wireless speed
>   Reduced throughput vs expected 802.11ac performance.
>   Link: https://bugzilla.kernel.org/show_bug.cgi?id=216685
>
>
> 2. SYMPTOM-TO-PATCH MAPPING
> =============================
>
> dmesg signature                    Patch that resolves it
> --------------------------         ----------------------
> Hard system freeze                 pci.c DMI quirk (disable ASPM)
> "pci bus timeout, check dma"       pci.c DMI quirk (disable ASPM)
> "firmware failed to leave lps"     pci.c DMI quirk (disable LPS Deep)
> "failed to send h2c command"       pci.c DMI quirk (disable LPS Deep)
> "timed out to flush queue N"       pci.c DMI quirk (disable LPS Deep) [1]
> "failed to get tx report"          pci.c DMI quirk (disable LPS Deep) [1]
> VHT NSS=0 mac80211 WARNING        rx.c rate validation (v2)
>
> Confirmed in bugs: 215131, 219830, 218697, 221195.
> [1] Inferred: flush timeout occurs when firmware cannot exit LPS
>     to process TX queue operations.
>
>
> 3. AFFECTED HARDWARE
> =====================
>
> Current DMI quirk coverage: HP P3S95EA#ACB only.
>
> Platforms confirmed affected in Bugzilla:
>   Bug 221195: HP Notebook 81F0 (P3S95EA#ACB)
>   Bug 215131: unknown (Canonical upstream testing)
>   Bug 219830: Bmax Y14
>   Bug 218697: unknown (Arch Linux user)
>
> Platforms reported in community forums as requiring
> disable_aspm=Y and/or disable_lps_deep=Y for stable RTL8821CE:
>   - HP 17-by4063CL
>   - Lenovo IdeaPad S145-15AST, IdeaPad 3, IdeaPad 330S
>   - ASUS VivoBook X series
>   - Acer Aspire 3/5 series
>
> All use PCI Device ID 10ec:c821 with different Subsystem IDs.
>
>
> 4. LPS_DEEP_MODE_LCLK IN THE rtw88 TREE
> =========================================
>
> I verified in the source which chips have the same
> lps_deep_mode_supported flag:
>
> Chip file       lps_deep_mode_supported            PCIe variant
> ---------       -----------------------            ------------
> rtw8821c.c      BIT(LPS_DEEP_MODE_LCLK)            rtw8821ce ✓
> rtw8822c.c      BIT(LPS_DEEP_MODE_LCLK) | PG       rtw8822ce ✓
> rtw8822b.c      BIT(LPS_DEEP_MODE_LCLK)            rtw8822be ✓
> rtw8814a.c      BIT(LPS_DEEP_MODE_LCLK)            rtw8814ae ✓
> rtw8723d.c      0                                   rtw8723de ✗
> rtw8703b.c      0                                   (SDIO)     -
> rtw8821a.c      0                                   (legacy)   -
>
> Source references:
>   rtw8821c.c:2002  rtw8822c.c:5365  rtw8822b.c:2545
>   rtw8814a.c:2211  rtw8723d.c:2144
>
> RTL8822CE community reports (Manjaro, Arch forums) confirm the
> same disable_aspm=Y + disable_lps_deep=Y workaround is effective,
> consistent with rtw8822c.c having LCLK enabled.
>
>
> 5. COMMUNITY WORKAROUND REFERENCES
> ====================================
>
> The following are concrete examples of forums and wikis where the
> same modprobe workarounds are actively recommended:
>
> Arch Wiki - RTW88 section:
>   https://wiki.archlinux.org/title/Network_configuration/Wireless
>   (section "RTW88" and "rtl8821ce" under Troubleshooting/Realtek)
>   Recommends rtw88-dkms-git and documents the rtw88_8821ce issues.
>
> Arch Wiki - RTW89 section (same page):
>   Documents the identical ASPM pattern for the newer RTW89 driver:
>     options rtw89_pci disable_aspm_l1=y disable_aspm_l1ss=y
>     options rtw89_core disable_ps_mode=y
>   This suggests the ASPM/LPS interaction is a systemic Realtek
>   design issue, not specific to rtw88 or the 8821CE chip.
>
> Arch Linux Forum - RTL8821CE thread:
>   https://bbs.archlinux.org/viewtopic.php?id=273440
>   Referenced by the Arch Wiki as the primary rtl8821ce discussion.
>
> lwfinger/rtw88 GitHub:
>   https://github.com/lwfinger/rtw88/issues/306
>   Directly cross-referenced by Bug 219830. Reporter reports h2c
>   errors and investigated antenna hardware (no fault found).
>
> lwfinger/rtw89 GitHub:
>   https://github.com/lwfinger/rtw89/issues/275#issuecomment-1784155449
>   Same ASPM-disable pattern documented for the newer RTW89 driver
>   on HP and Lenovo laptops.
>
>
> 6. OBSERVATIONS
> ================
>
> a) Three open Bugzilla reporters (215131, 219830, 218697) show
>    symptoms identical to those resolved by your patches but have
>    no upstream fix available since they are not the HP P3S95EA#ACB.
>
> b) Bug 215131 reporter (Kai-Heng Feng, Canonical) explicitly
>    confirmed disable_aspm=1 as a workaround and called it
>    "not viable" due to power cost. A DMI quirk for their
>    platform would give them a proper fix.
>
> c) The Arch Wiki documents the same ASPM-disable pattern for
>    both RTW88 and RTW89 drivers, suggesting the underlying
>    hardware/firmware limitation is shared across generations.
>
> d) Asking Bugzilla reporters to provide their DMI data
>    (dmidecode -t 1,2) could allow extending the quirk table
>    with minimal effort and zero risk to unaffected platforms.
>
> e) The rx.c rate validation patch is chip-agnostic and requires
>    no platform-specific consideration.
>
>
> 7. REFERENCES
> ==============
>
> Kernel Bugzilla:
>   https://bugzilla.kernel.org/show_bug.cgi?id=215131
>   https://bugzilla.kernel.org/show_bug.cgi?id=219830
>   https://bugzilla.kernel.org/show_bug.cgi?id=218697
>   https://bugzilla.kernel.org/show_bug.cgi?id=217491
>   https://bugzilla.kernel.org/show_bug.cgi?id=217781
>   https://bugzilla.kernel.org/show_bug.cgi?id=216685
>
> GitHub:
>   https://github.com/lwfinger/rtw88/issues/306
>   https://github.com/lwfinger/rtw89/issues/275
>
> Arch Wiki:
>   https://wiki.archlinux.org/title/Network_configuration/Wireless
>
> Arch Linux Forum:
>   https://bbs.archlinux.org/viewtopic.php?id=273440
>
> Source code (lps_deep_mode_supported):
>   drivers/net/wireless/realtek/rtw88/rtw8821c.c:2002
>   drivers/net/wireless/realtek/rtw88/rtw8822c.c:5365
>   drivers/net/wireless/realtek/rtw88/rtw8822b.c:2545
>   drivers/net/wireless/realtek/rtw88/rtw8814a.c:2211
>   drivers/net/wireless/realtek/rtw88/rtw8723d.c:2144
>
>
> Best regards,
> Oleksandr Havrylov <goainwo@gmail.com>

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Bitterblue Smith]

On 27/03/2026 01:52, LB F wrote:
> Hi Ping-Ke,
> 
> This is Oleksandr Havrylov again. Thank you for the ASPM/LPS Deep
> quirk and the rate validation patches — they are both working correctly
> (zero h2c timeouts, zero lps failures, zero mac80211 warnings).
> 
> However, I'm experiencing a different, separate bug that causes kernel
> oops and makes the system completely unresponsive, requiring a hard
> power-off. After disassembling the crash site, I believe I've found
> the root cause.
> 
> == Summary ==
> 
> When firmware sends a C2H_ADAPTIVITY (0x37) command to an RTL8821CE
> adapter, rtw_fw_adaptivity_result() dereferences rtwdev->chip->edcca_th
> without a NULL check. The RTL8821C chip_info (rtw8821c_hw_spec) does
> not define edcca_th, so the pointer is NULL, causing a kernel oops.
> 
> The crash occurs on the phy0 workqueue while holding rtwdev->mutex,
> which never gets released. This causes all subsequent processes that
> touch the network stack to hang in uninterruptible D-state, making
> the system completely unresponsive and requiring a hard power-off.
> 
> == Root cause analysis ==
> 
> rtw_fw_adaptivity_result() in fw.c (line ~282):
> 
>   static void rtw_fw_adaptivity_result(struct rtw_dev *rtwdev, u8 *payload,
>                                        u8 length)
>   {
>       const struct rtw_hw_reg_offset *edcca_th = rtwdev->chip->edcca_th;
>       ...
>       rtw_dbg(rtwdev, RTW_DBG_ADAPTIVITY, "Reg Setting: L2H %x H2L %x\n",
>               rtw_read32_mask(rtwdev, edcca_th[EDCCA_TH_L2H_IDX].hw_reg.addr,
>                                              ^^^^^^^^^ NULL dereference here
>                               edcca_th[EDCCA_TH_L2H_IDX].hw_reg.mask),
>               ...
> 
> The RTL8822C defines .edcca_th = rtw8822c_edcca_th in its chip_info,
> but RTL8821C does not set this field at all — it remains NULL.
> 
> I verified this by disassembling the compiled rtw_core.ko module:
> 
>   Crash RIP: rtw_fw_c2h_cmd_handle+0x127
>   Address:   0x1d527 = movl (%r12), %esi
> 
>   R12 is loaded at +0xe5 (0x1d4e5):
>     movq 0x140(%rax), %r12    ; rax = rtwdev->chip
>                               ; 0x140 = offset of edcca_th in rtw_chip_info
>                               ; R12 = chip->edcca_th = NULL for 8821c
> 
>   The function is entered via:
>     +0xd8 (0x1d4d8): cmpl $0x37, %ecx  ; c2h->id == C2H_ADAPTIVITY (0x37)
> 
>   With R12 = 0, the instruction at +0x127:
>     movl (%r12), %esi   ; reads from address 0x0 → NULL pointer dereference
> 
> I also confirmed that rtw8821c_hw_spec in the mainline kernel
> (torvalds/linux master, rtw8821c.c) does NOT set .edcca_th.
> 
> == Reproduction ==
> 
> The crash is highly reproducible: it occurred in 4 out of 7 recent
> boots. It happens during normal active usage with no specific trigger.
> 
>   boot  date/time of crash         uptime at crash
>   -5    2026-03-25 00:58:06        ~2 min
>   -4    2026-03-25 21:32:00        ~6h
>   -3    2026-03-26 00:28:14        ~2.5h
>   -1    2026-03-27 00:56:58        ~23.5h
> 
> Both ASPM and LPS Deep are disabled via the DMI quirk. The crash
> occurs every time with the same pattern and same RIP offset (+0x127).
> 
> == Crash pattern ==
> 
> Every crash follows the same sequence:
> 
>   1) Burst of 50-60 "unused phy status page" messages in ~1 second:
> 
>      rtw_8821ce 0000:13:00.0: unused phy status page (8)
>      rtw_8821ce 0000:13:00.0: unused phy status page (2)
>      ... (50+ more within same second)
> 

It looks like the firmware is not sending C2H_ADAPTIVITY (unexpected
for RTL8821CE), but rather you are getting garbage RX data. I am
curious what kind of garbage it is. Can you try this?


diff --git a/drivers/net/wireless/realtek/rtw88/rtw8821c.c b/drivers/net/wireless/realtek/rtw88/rtw8821c.c
index da67a6845fd5..aae246c2bc8e 100644
--- a/drivers/net/wireless/realtek/rtw88/rtw8821c.c
+++ b/drivers/net/wireless/realtek/rtw88/rtw8821c.c
@@ -665,6 +665,7 @@ static void query_phy_status(struct rtw_dev *rtwdev, u8 *phy_status,
 			     struct rtw_rx_pkt_stat *pkt_stat)
 {
 	u8 page;
+	u8 *rxdesc = phy_status - rtwdev->chip->rx_pkt_desc_sz - pkt_stat->shift;
 
 	page = *phy_status & 0xf;
 
@@ -677,6 +678,10 @@ static void query_phy_status(struct rtw_dev *rtwdev, u8 *phy_status,
 		break;
 	default:
 		rtw_warn(rtwdev, "unused phy status page (%d)\n", page);
+		print_hex_dump(KERN_INFO, "", DUMP_PREFIX_OFFSET, 4, 4,
+			       rxdesc, 56, true);
+		print_hex_dump(KERN_INFO, "", DUMP_PREFIX_OFFSET, 16, 1,
+			       rxdesc, 40, true);
 		return;
 	}
 }

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Hi Bitterblue,

Apologies for the delayed response. I applied your diagnostic patch
right away but held off on replying because the NULL pointer crash
has not reproduced since — it has been over 36 hours now with no
oops, which is unusual (previously it occurred in 4 out of 7 boots,
typically within 2 minutes to 24 hours).

I wanted to wait and collect the hex dumps from the crash-time burst
(the 50+ "unused phy status page" events that always preceded the
oops), as those would be the most valuable. Unfortunately, the crash
hasn't happened yet during this session. If/when it does, I will
follow up immediately with those dumps.

In the meantime, here is what I have so far. The patch is working
and producing output. I collected 76 "unused phy status page" events
during this boot, with the following time distribution:

  14:01       1 event  (isolated)
  16:33       1 event
  16:57-17:00 73 events (burst over ~3 minutes, no crash followed)
  00:03       1 event  (isolated)

Page number distribution (no page 0 or 1, all are "garbage" pages):

  page 10: 10    page  7:  8    page  8:  7    page 13:  7
  page 11:  7    page  9:  6    page 15:  6    page 12:  6
  page  4:  5    page  2:  5    page 14:  4    page  5:  2
  page  3:  2    page  6:  1

Here are representative hex dumps. I'm showing the byte-level dump
(second print_hex_dump) since it is easier to read:

Isolated event (page 9):

  rtw_8821ce 0000:13:00.0: unused phy status page (9)
  00000000: c7 5e 9c 9d 91 69 4d dc b0 67 c2 09 84 33 00 00  .^...iM..g...3..
  00000010: 00 1e fe 3f cf f2 f0 08 01 29 00 00 00 11 2a 01  ...?.....)....*.
  00000020: 0e 00 00 00 00 00 00 20                           .......

Burst event (page 14):

  rtw_8821ce 0000:13:00.0: unused phy status page (14)
  00000000: bd 2c e0 3d 00 00 00 11 87 0a 40 80 88 33 00 00  .,.=......@..3..
  00000010: 00 1e fe 3f 3e b6 9b 44 01 2e 00 00 00 11 2a 01  ...?>..D......*.
  00000020: 20 00 00 00 00 00 00 20                            ......

Burst event (page 12) — byte 0x10 is 0x7e instead of usual 0x00:

  rtw_8821ce 0000:13:00.0: unused phy status page (12)
  00000000: 1c b3 7f 15 d1 94 95 7e 70 5e f4 e3 b4 a1 bf 10  .......~p^......
  00000010: 7e 1e fe 3f 2e f1 62 44 01 2c 00 00 00 11 2a 01  ~..?..bD.,....*.
  00000020: 14 00 00 00 00 00 00 20                           .......

Burst event (page 2) — contains MAC addresses:

  rtw_8821ce 0000:13:00.0: unused phy status page (2)
  00000000: 88 55 51 95 d1 66 ad 50 2f 25 3f 89 ae 35 ef 77  .UQ..f.P/%?..5.w
  00000010: 00 1e fe 3f 89 68 62 4d 88 42 40 00 8c c8 4b 68  ...?.hbM.B@...Kh
  00000020: d1 63 6c 68 a4 1c 97 5b                           .clh...[

  Note: bytes 0x1a-0x1f are 8c:c8:4b:68:d1:63 — my adapter's MAC.
        bytes 0x20-0x25 are 6c:68:a4:1c:97:5b — the AP's BSSID (partially,
        the dump is only 40 bytes so it cuts off after 0x25).

Burst event (page 15) — completely random, no recognizable structure:

  rtw_8821ce 0000:13:00.0: unused phy status page (15)
  00000000: c6 a1 92 1c a7 68 6b 97 12 bd ad 89 30 98 ab 94  .....hk.....0...
  00000010: 00 1e fe 3f ec 3f 3e 44 1f c2 91 41 0e 9b 54 5f  ...?.?>D...A..T_
  00000020: 30 eb 40 18 6f d3 25 62                           0.@.o.%b

Burst event (page 10) — offset 0x10 is completely different pattern:

  rtw_8821ce 0000:13:00.0: unused phy status page (10)
  00000000: cb 1c 2a df f1 69 d0 05 58 c0 e8 0e d0 59 87 6e  ..*..i..X....Y.n
  00000010: 63 7e 56 f0 95 fa b8 d3 d5 4b 3e fa b0 0c 0e be  c~V......K>.....
  00000020: 42 28 14 89 15 c1 fd ad                           B(......

Last isolated event (page 4):

  rtw_8821ce 0000:13:00.0: unused phy status page (4)
  00000000: 97 ee fa 4e 04 90 00 21 c0 0f 89 80 b3 33 00 00  ...N...!.....3..
  00000010: 00 1e fe 3f 97 7e 64 90 5d 3e 74 fa 70 e0 39 65  ...?.~d.]>t.p.9e
  00000020: 48 a4 40 d3 de a9 85 15                           H.@.....

Observations:

  - Bytes at offset 0x0e-0x0f are usually 00 00 or have low values
    in most dumps, but some are completely random.
  - Bytes 0x11-0x13 are almost always 1e fe 3f (with byte 0x10
    being 00 or 7e), suggesting this is a consistent part of the
    RX descriptor that is not corrupted.
  - The "page 2" dump at 17:00:23 clearly contains the adapter
    and AP MAC addresses, confirming this is real RX frame data.
  - Some dumps (page 10, page 5, page 15) have completely random
    data with no recognizable RX descriptor structure at all.
  - The 73-event burst at 16:57-17:00 happened over ~3 minutes but
    did NOT result in a crash this time. Previously, similar bursts
    of 50+ events within ~1 second always led to the NULL pointer
    dereference in rtw_fw_c2h_cmd_handle+0x127.

I will keep monitoring and will send the crash-time dumps as soon as
the oops reproduces.

Thanks for looking into this.

Best regards,
Oleksandr Havrylov

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Bitterblue Smith]

On 28/03/2026 13:41, LB F wrote:
> Hi Bitterblue,
> 
> Apologies for the delayed response. I applied your diagnostic patch
> right away but held off on replying because the NULL pointer crash
> has not reproduced since — it has been over 36 hours now with no
> oops, which is unusual (previously it occurred in 4 out of 7 boots,
> typically within 2 minutes to 24 hours).
> 
> I wanted to wait and collect the hex dumps from the crash-time burst
> (the 50+ "unused phy status page" events that always preceded the
> oops), as those would be the most valuable. Unfortunately, the crash
> hasn't happened yet during this session. If/when it does, I will
> follow up immediately with those dumps.
> 
> In the meantime, here is what I have so far. The patch is working
> and producing output. I collected 76 "unused phy status page" events
> during this boot, with the following time distribution:
> 
>   14:01       1 event  (isolated)
>   16:33       1 event
>   16:57-17:00 73 events (burst over ~3 minutes, no crash followed)
>   00:03       1 event  (isolated)
> 
> Page number distribution (no page 0 or 1, all are "garbage" pages):
> 
>   page 10: 10    page  7:  8    page  8:  7    page 13:  7
>   page 11:  7    page  9:  6    page 15:  6    page 12:  6
>   page  4:  5    page  2:  5    page 14:  4    page  5:  2
>   page  3:  2    page  6:  1
> 
> Here are representative hex dumps. I'm showing the byte-level dump
> (second print_hex_dump) since it is easier to read:
> 
> Isolated event (page 9):
> 
>   rtw_8821ce 0000:13:00.0: unused phy status page (9)
>   00000000: c7 5e 9c 9d 91 69 4d dc b0 67 c2 09 84 33 00 00  .^...iM..g...3..
>   00000010: 00 1e fe 3f cf f2 f0 08 01 29 00 00 00 11 2a 01  ...?.....)....*.
>   00000020: 0e 00 00 00 00 00 00 20                           .......
> 
> Burst event (page 14):
> 
>   rtw_8821ce 0000:13:00.0: unused phy status page (14)
>   00000000: bd 2c e0 3d 00 00 00 11 87 0a 40 80 88 33 00 00  .,.=......@..3..
>   00000010: 00 1e fe 3f 3e b6 9b 44 01 2e 00 00 00 11 2a 01  ...?>..D......*.
>   00000020: 20 00 00 00 00 00 00 20                            ......
> 
> Burst event (page 12) — byte 0x10 is 0x7e instead of usual 0x00:
> 
>   rtw_8821ce 0000:13:00.0: unused phy status page (12)
>   00000000: 1c b3 7f 15 d1 94 95 7e 70 5e f4 e3 b4 a1 bf 10  .......~p^......
>   00000010: 7e 1e fe 3f 2e f1 62 44 01 2c 00 00 00 11 2a 01  ~..?..bD.,....*.
>   00000020: 14 00 00 00 00 00 00 20                           .......
> 
> Burst event (page 2) — contains MAC addresses:
> 
>   rtw_8821ce 0000:13:00.0: unused phy status page (2)
>   00000000: 88 55 51 95 d1 66 ad 50 2f 25 3f 89 ae 35 ef 77  .UQ..f.P/%?..5.w
>   00000010: 00 1e fe 3f 89 68 62 4d 88 42 40 00 8c c8 4b 68  ...?.hbM.B@...Kh
>   00000020: d1 63 6c 68 a4 1c 97 5b                           .clh...[
> 
>   Note: bytes 0x1a-0x1f are 8c:c8:4b:68:d1:63 — my adapter's MAC.
>         bytes 0x20-0x25 are 6c:68:a4:1c:97:5b — the AP's BSSID (partially,
>         the dump is only 40 bytes so it cuts off after 0x25).
> 
> Burst event (page 15) — completely random, no recognizable structure:
> 
>   rtw_8821ce 0000:13:00.0: unused phy status page (15)
>   00000000: c6 a1 92 1c a7 68 6b 97 12 bd ad 89 30 98 ab 94  .....hk.....0...
>   00000010: 00 1e fe 3f ec 3f 3e 44 1f c2 91 41 0e 9b 54 5f  ...?.?>D...A..T_
>   00000020: 30 eb 40 18 6f d3 25 62                           0.@.o.%b
> 
> Burst event (page 10) — offset 0x10 is completely different pattern:
> 
>   rtw_8821ce 0000:13:00.0: unused phy status page (10)
>   00000000: cb 1c 2a df f1 69 d0 05 58 c0 e8 0e d0 59 87 6e  ..*..i..X....Y.n
>   00000010: 63 7e 56 f0 95 fa b8 d3 d5 4b 3e fa b0 0c 0e be  c~V......K>.....
>   00000020: 42 28 14 89 15 c1 fd ad                           B(......
> 
> Last isolated event (page 4):
> 
>   rtw_8821ce 0000:13:00.0: unused phy status page (4)
>   00000000: 97 ee fa 4e 04 90 00 21 c0 0f 89 80 b3 33 00 00  ...N...!.....3..
>   00000010: 00 1e fe 3f 97 7e 64 90 5d 3e 74 fa 70 e0 39 65  ...?.~d.]>t.p.9e
>   00000020: 48 a4 40 d3 de a9 85 15                           H.@.....
> 
> Observations:
> 
>   - Bytes at offset 0x0e-0x0f are usually 00 00 or have low values
>     in most dumps, but some are completely random.
>   - Bytes 0x11-0x13 are almost always 1e fe 3f (with byte 0x10
>     being 00 or 7e), suggesting this is a consistent part of the
>     RX descriptor that is not corrupted.
>   - The "page 2" dump at 17:00:23 clearly contains the adapter
>     and AP MAC addresses, confirming this is real RX frame data.
>   - Some dumps (page 10, page 5, page 15) have completely random
>     data with no recognizable RX descriptor structure at all.
>   - The 73-event burst at 16:57-17:00 happened over ~3 minutes but
>     did NOT result in a crash this time. Previously, similar bursts
>     of 50+ events within ~1 second always led to the NULL pointer
>     dereference in rtw_fw_c2h_cmd_handle+0x127.
> 
> I will keep monitoring and will send the crash-time dumps as soon as
> the oops reproduces.
> 
> Thanks for looking into this.
> 
> Best regards,
> Oleksandr Havrylov

The other print_hex_dump is important too, so please attach the
full dmesg.

You don't need to wait for a crash. It appears to be caused by
random data, so I don't expect those dumps to be more useful than
these. Of course, adding a NULL check like you said before is a
good idea.

The one dump that contains your MAC addresses has them 24 bytes
lower than they are supposed to be.

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

Hi Bitterblue,

Thank you for the quick feedback. Full dmesg from the current boot
session is attached (dmesg_boot0_clean.txt, 332K, 3349 lines).

It contains all 76 "unused phy status page" events with both hex
dumps (4-byte grouped and byte-level) in full, plus all surrounding
kernel context.

The interesting observation you made about the MAC addresses being
24 bytes lower than expected is very helpful — I hadn't noticed the
offset discrepancy. If you need the adapter and AP MAC addresses
for reference:

  Adapter: 8c:c8:4b:68:d1:63
  AP:      6c:68:a4:1c:97:5b

And yes, adding a NULL check in rtw_fw_adaptivity_result() seems
like a good defensive measure regardless of the root cause.

Let me know if you need anything else or a different format.

Best regards,
Oleksandr Havrylov

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: dmesg_boot0_clean.txt --]
[-- Type: text/plain; charset="US-ASCII"; name="dmesg_boot0_clean.txt", Size: 336524 bytes --]

[    1.832670] cachyos kernel: Linux version 6.19.9-2-cachyos (linux-cachyos@cachyos) (clang version 22.1.1, LLD 22.1.1) #1 SMP PREEMPT_DYNAMIC Tue, 24 Mar 2026 22:12:07 +0000
[    1.832853] cachyos kernel: Command line: resume=UUID=450aafdc-613a-4cf9-bdbb-eb338b606697 resume_offset=7243593 quiet nowatchdog splash rw rootflags=subvol=/@ root=UUID=450aafdc-613a-4cf9-bdbb-eb338b606697
[    1.832880] cachyos kernel: BIOS-provided physical RAM map:
[    1.832900] cachyos kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[    1.832920] cachyos kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[    1.832940] cachyos kernel: BIOS-e820: [mem 0x0000000000059000-0x0000000000085fff] usable
[    1.832964] cachyos kernel: BIOS-e820: [mem 0x0000000000086000-0x000000000009ffff] reserved
[    1.832983] cachyos kernel: BIOS-e820: [mem 0x0000000000100000-0x000000009b88dfff] usable
[    1.833036] cachyos kernel: BIOS-e820: [mem 0x000000009b88e000-0x000000009cc8dfff] reserved
[    1.833058] cachyos kernel: BIOS-e820: [mem 0x000000009cc8e000-0x000000009cf8dfff] ACPI NVS
[    1.833077] cachyos kernel: BIOS-e820: [mem 0x000000009cf8e000-0x000000009cffdfff] ACPI data
[    1.833096] cachyos kernel: BIOS-e820: [mem 0x000000009cffe000-0x000000009cffefff] usable
[    1.833115] cachyos kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[    1.833135] cachyos kernel: BIOS-e820: [mem 0x00000000feb00000-0x00000000feb03fff] reserved
[    1.833159] cachyos kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    1.833179] cachyos kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[    1.833198] cachyos kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    1.833216] cachyos kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    1.833235] cachyos kernel: BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved
[    1.833254] cachyos kernel: BIOS-e820: [mem 0x0000000100000000-0x000000035effffff] usable
[    1.833273] cachyos kernel: NX (Execute Disable) protection: active
[    1.833292] cachyos kernel: APIC: Static calls initialized
[    1.833311] cachyos kernel: efi: EFI v2.4 by INSYDE Corp.
[    1.833329] cachyos kernel: efi: SMBIOS=0x9be80000 ESRT=0x9bf8c118 ACPI 2.0=0x9cffd014 
[    1.833348] cachyos kernel: efi: Remove mem36: MMIO range=[0xe0000000-0xefffffff] (256MB) from e820 map
[    1.833367] cachyos kernel: e820: remove [mem 0xe0000000-0xefffffff] reserved
[    1.833387] cachyos kernel: efi: Not removing mem37: MMIO range=[0xfeb00000-0xfeb03fff] (16KB) from e820 map
[    1.833407] cachyos kernel: efi: Not removing mem38: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map
[    1.833426] cachyos kernel: efi: Not removing mem39: MMIO range=[0xfed10000-0xfed19fff] (40KB) from e820 map
[    1.833445] cachyos kernel: efi: Not removing mem40: MMIO range=[0xfed1c000-0xfed1ffff] (16KB) from e820 map
[    1.833464] cachyos kernel: efi: Not removing mem41: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map
[    1.833483] cachyos kernel: efi: Remove mem42: MMIO range=[0xffa00000-0xffffffff] (6MB) from e820 map
[    1.833502] cachyos kernel: e820: remove [mem 0xffa00000-0xffffffff] reserved
[    1.833521] cachyos kernel: SMBIOS 2.8 present.
[    1.833540] cachyos kernel: DMI: HP HP Notebook/81F0, BIOS F.50 11/20/2020
[    1.833559] cachyos kernel: DMI: Memory slots populated: 2/2
[    1.833578] cachyos kernel: tsc: Fast TSC calibration using PIT
[    1.833597] cachyos kernel: tsc: Detected 1995.399 MHz processor
[    1.833616] cachyos kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    1.833638] cachyos kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
[    1.833664] cachyos kernel: last_pfn = 0x35f000 max_arch_pfn = 0x400000000
[    1.833684] cachyos kernel: total RAM covered: 14799M
[    1.833707] cachyos kernel:  gran_size: 64K         chunk_size: 64K         num_reg: 10          lose cover RAM: 12583164K
[    1.833729] cachyos kernel:  gran_size: 64K         chunk_size: 128K         num_reg: 8          lose cover RAM: 60K
[    1.833751] cachyos kernel:  gran_size: 64K         chunk_size: 256K         num_reg: 8          lose cover RAM: 60K
[    1.833773] cachyos kernel:  gran_size: 64K         chunk_size: 512K         num_reg: 8          lose cover RAM: 60K
[    1.833794] cachyos kernel:  gran_size: 64K         chunk_size: 1M         num_reg: 8          lose cover RAM: 60K
[    1.833816] cachyos kernel:  gran_size: 64K         chunk_size: 2M         num_reg: 8          lose cover RAM: 60K
[    1.833837] cachyos kernel:  gran_size: 64K         chunk_size: 4M         num_reg: 8          lose cover RAM: 60K
[    1.833858] cachyos kernel:  gran_size: 64K         chunk_size: 8M         num_reg: 8          lose cover RAM: 60K
[    1.833880] cachyos kernel:  gran_size: 64K         chunk_size: 16M         num_reg: 8          lose cover RAM: 60K
[    1.833901] cachyos kernel:  gran_size: 64K         chunk_size: 32M         num_reg: 9          lose cover RAM: 60K
[    1.833922] cachyos kernel:  gran_size: 64K         chunk_size: 64M         num_reg: 7          lose cover RAM: 60K
[    1.833943] cachyos kernel:  gran_size: 64K         chunk_size: 128M         num_reg: 7          lose cover RAM: 60K
[    1.833965] cachyos kernel:  gran_size: 64K         chunk_size: 256M         num_reg: 7          lose cover RAM: 60K
[    1.833986] cachyos kernel:  gran_size: 64K         chunk_size: 512M         num_reg: 7          lose cover RAM: 60K
[    1.835249] cachyos kernel:  gran_size: 64K         chunk_size: 1G         num_reg: 8          lose cover RAM: 60K
[    1.835293] cachyos kernel:  gran_size: 64K         chunk_size: 2G         num_reg: 8          lose cover RAM: 60K
[    1.835324] cachyos kernel:  gran_size: 128K         chunk_size: 128K         num_reg: 10          lose cover RAM: 12583164K
[    1.835352] cachyos kernel:  gran_size: 128K         chunk_size: 256K         num_reg: 8          lose cover RAM: 124K
[    1.835380] cachyos kernel:  gran_size: 128K         chunk_size: 512K         num_reg: 8          lose cover RAM: 124K
[    1.835407] cachyos kernel:  gran_size: 128K         chunk_size: 1M         num_reg: 8          lose cover RAM: 124K
[    1.835434] cachyos kernel:  gran_size: 128K         chunk_size: 2M         num_reg: 8          lose cover RAM: 124K
[    1.835461] cachyos kernel:  gran_size: 128K         chunk_size: 4M         num_reg: 8          lose cover RAM: 124K
[    1.835487] cachyos kernel:  gran_size: 128K         chunk_size: 8M         num_reg: 8          lose cover RAM: 124K
[    1.835513] cachyos kernel:  gran_size: 128K         chunk_size: 16M         num_reg: 8          lose cover RAM: 124K
[    1.835540] cachyos kernel:  gran_size: 128K         chunk_size: 32M         num_reg: 9          lose cover RAM: 124K
[    1.835567] cachyos kernel:  gran_size: 128K         chunk_size: 64M         num_reg: 7          lose cover RAM: 124K
[    1.835593] cachyos kernel:  gran_size: 128K         chunk_size: 128M         num_reg: 7          lose cover RAM: 124K
[    1.835619] cachyos kernel:  gran_size: 128K         chunk_size: 256M         num_reg: 7          lose cover RAM: 124K
[    1.835645] cachyos kernel:  gran_size: 128K         chunk_size: 512M         num_reg: 7          lose cover RAM: 124K
[    1.835671] cachyos kernel:  gran_size: 128K         chunk_size: 1G         num_reg: 8          lose cover RAM: 124K
[    1.835697] cachyos kernel:  gran_size: 128K         chunk_size: 2G         num_reg: 8          lose cover RAM: 124K
[    1.835724] cachyos kernel:  gran_size: 256K         chunk_size: 256K         num_reg: 10          lose cover RAM: 12583164K
[    1.835751] cachyos kernel:  gran_size: 256K         chunk_size: 512K         num_reg: 8          lose cover RAM: 252K
[    1.835777] cachyos kernel:  gran_size: 256K         chunk_size: 1M         num_reg: 8          lose cover RAM: 252K
[    1.835803] cachyos kernel:  gran_size: 256K         chunk_size: 2M         num_reg: 8          lose cover RAM: 252K
[    1.835830] cachyos kernel:  gran_size: 256K         chunk_size: 4M         num_reg: 8          lose cover RAM: 252K
[    1.835856] cachyos kernel:  gran_size: 256K         chunk_size: 8M         num_reg: 8          lose cover RAM: 252K
[    1.835883] cachyos kernel:  gran_size: 256K         chunk_size: 16M         num_reg: 8          lose cover RAM: 252K
[    1.835910] cachyos kernel:  gran_size: 256K         chunk_size: 32M         num_reg: 9          lose cover RAM: 252K
[    1.835938] cachyos kernel:  gran_size: 256K         chunk_size: 64M         num_reg: 7          lose cover RAM: 252K
[    1.835965] cachyos kernel:  gran_size: 256K         chunk_size: 128M         num_reg: 7          lose cover RAM: 252K
[    1.835993] cachyos kernel:  gran_size: 256K         chunk_size: 256M         num_reg: 7          lose cover RAM: 252K
[    1.836030] cachyos kernel:  gran_size: 256K         chunk_size: 512M         num_reg: 7          lose cover RAM: 252K
[    1.836057] cachyos kernel:  gran_size: 256K         chunk_size: 1G         num_reg: 8          lose cover RAM: 252K
[    1.836084] cachyos kernel:  gran_size: 256K         chunk_size: 2G         num_reg: 8          lose cover RAM: 252K
[    1.836112] cachyos kernel:  gran_size: 512K         chunk_size: 512K         num_reg: 10          lose cover RAM: 8389116K
[    1.836140] cachyos kernel:  gran_size: 512K         chunk_size: 1M         num_reg: 8          lose cover RAM: 508K
[    1.836165] cachyos kernel:  gran_size: 512K         chunk_size: 2M         num_reg: 8          lose cover RAM: 508K
[    1.836191] cachyos kernel:  gran_size: 512K         chunk_size: 4M         num_reg: 8          lose cover RAM: 508K
[    1.836212] cachyos kernel:  gran_size: 512K         chunk_size: 8M         num_reg: 8          lose cover RAM: 508K
[    1.836233] cachyos kernel:  gran_size: 512K         chunk_size: 16M         num_reg: 8          lose cover RAM: 508K
[    1.836254] cachyos kernel:  gran_size: 512K         chunk_size: 32M         num_reg: 9          lose cover RAM: 508K
[    1.836276] cachyos kernel:  gran_size: 512K         chunk_size: 64M         num_reg: 7          lose cover RAM: 508K
[    1.836297] cachyos kernel:  gran_size: 512K         chunk_size: 128M         num_reg: 7          lose cover RAM: 508K
[    1.836318] cachyos kernel:  gran_size: 512K         chunk_size: 256M         num_reg: 7          lose cover RAM: 508K
[    1.836340] cachyos kernel:  gran_size: 512K         chunk_size: 512M         num_reg: 7          lose cover RAM: 508K
[    1.836361] cachyos kernel:  gran_size: 512K         chunk_size: 1G         num_reg: 8          lose cover RAM: 508K
[    1.836382] cachyos kernel:  gran_size: 512K         chunk_size: 2G         num_reg: 8          lose cover RAM: 508K
[    1.836404] cachyos kernel:  gran_size: 1M         chunk_size: 1M         num_reg: 10          lose cover RAM: 1020K
[    1.836425] cachyos kernel:  gran_size: 1M         chunk_size: 2M         num_reg: 8          lose cover RAM: 1020K
[    1.836447] cachyos kernel:  gran_size: 1M         chunk_size: 4M         num_reg: 8          lose cover RAM: 1020K
[    1.836468] cachyos kernel:  gran_size: 1M         chunk_size: 8M         num_reg: 8          lose cover RAM: 1020K
[    1.836491] cachyos kernel:  gran_size: 1M         chunk_size: 16M         num_reg: 8          lose cover RAM: 1020K
[    1.836513] cachyos kernel:  gran_size: 1M         chunk_size: 32M         num_reg: 9          lose cover RAM: 1020K
[    1.836535] cachyos kernel:  gran_size: 1M         chunk_size: 64M         num_reg: 7          lose cover RAM: 1020K
[    1.836558] cachyos kernel:  gran_size: 1M         chunk_size: 128M         num_reg: 7          lose cover RAM: 1020K
[    1.836580] cachyos kernel:  gran_size: 1M         chunk_size: 256M         num_reg: 7          lose cover RAM: 1020K
[    1.836602] cachyos kernel:  gran_size: 1M         chunk_size: 512M         num_reg: 7          lose cover RAM: 1020K
[    1.836623] cachyos kernel:  gran_size: 1M         chunk_size: 1G         num_reg: 8          lose cover RAM: 1020K
[    1.836644] cachyos kernel:  gran_size: 1M         chunk_size: 2G         num_reg: 8          lose cover RAM: 1020K
[    1.836666] cachyos kernel:  gran_size: 2M         chunk_size: 2M         num_reg: 9          lose cover RAM: 2044K
[    1.836687] cachyos kernel:  gran_size: 2M         chunk_size: 4M         num_reg: 8          lose cover RAM: 2044K
[    1.836708] cachyos kernel:  gran_size: 2M         chunk_size: 8M         num_reg: 8          lose cover RAM: 2044K
[    1.836729] cachyos kernel:  gran_size: 2M         chunk_size: 16M         num_reg: 8          lose cover RAM: 2044K
[    1.836751] cachyos kernel:  gran_size: 2M         chunk_size: 32M         num_reg: 9          lose cover RAM: 2044K
[    1.836773] cachyos kernel:  gran_size: 2M         chunk_size: 64M         num_reg: 7          lose cover RAM: 2044K
[    1.836799] cachyos kernel:  gran_size: 2M         chunk_size: 128M         num_reg: 7          lose cover RAM: 2044K
[    1.836820] cachyos kernel:  gran_size: 2M         chunk_size: 256M         num_reg: 7          lose cover RAM: 2044K
[    1.836842] cachyos kernel:  gran_size: 2M         chunk_size: 512M         num_reg: 7          lose cover RAM: 2044K
[    1.836863] cachyos kernel:  gran_size: 2M         chunk_size: 1G         num_reg: 8          lose cover RAM: 2044K
[    1.836884] cachyos kernel:  gran_size: 2M         chunk_size: 2G         num_reg: 8          lose cover RAM: 2044K
[    1.836910] cachyos kernel:  gran_size: 4M         chunk_size: 4M         num_reg: 8          lose cover RAM: 4092K
[    1.836932] cachyos kernel:  gran_size: 4M         chunk_size: 8M         num_reg: 8          lose cover RAM: 4092K
[    1.836950] cachyos kernel:  gran_size: 4M         chunk_size: 16M         num_reg: 8          lose cover RAM: 4092K
[    1.836962] cachyos kernel:  gran_size: 4M         chunk_size: 32M         num_reg: 9          lose cover RAM: 4092K
[    1.836974] cachyos kernel:  gran_size: 4M         chunk_size: 64M         num_reg: 7          lose cover RAM: 4092K
[    1.836986] cachyos kernel:  gran_size: 4M         chunk_size: 128M         num_reg: 7          lose cover RAM: 4092K
[    1.836997] cachyos kernel:  gran_size: 4M         chunk_size: 256M         num_reg: 7          lose cover RAM: 4092K
[    1.837022] cachyos kernel:  gran_size: 4M         chunk_size: 512M         num_reg: 7          lose cover RAM: 4092K
[    1.837033] cachyos kernel:  gran_size: 4M         chunk_size: 1G         num_reg: 8          lose cover RAM: 4092K
[    1.837045] cachyos kernel:  gran_size: 4M         chunk_size: 2G         num_reg: 8          lose cover RAM: 4092K
[    1.837057] cachyos kernel:  gran_size: 8M         chunk_size: 8M         num_reg: 7          lose cover RAM: 8188K
[    1.837068] cachyos kernel:  gran_size: 8M         chunk_size: 16M         num_reg: 8          lose cover RAM: 8188K
[    1.837080] cachyos kernel:  gran_size: 8M         chunk_size: 32M         num_reg: 9          lose cover RAM: 8188K
[    1.837092] cachyos kernel:  gran_size: 8M         chunk_size: 64M         num_reg: 7          lose cover RAM: 8188K
[    1.837104] cachyos kernel:  gran_size: 8M         chunk_size: 128M         num_reg: 7          lose cover RAM: 8188K
[    1.837116] cachyos kernel:  gran_size: 8M         chunk_size: 256M         num_reg: 7          lose cover RAM: 8188K
[    1.837127] cachyos kernel:  gran_size: 8M         chunk_size: 512M         num_reg: 7          lose cover RAM: 8188K
[    1.837139] cachyos kernel:  gran_size: 8M         chunk_size: 1G         num_reg: 8          lose cover RAM: 8188K
[    1.837151] cachyos kernel:  gran_size: 8M         chunk_size: 2G         num_reg: 8          lose cover RAM: 8188K
[    1.837163] cachyos kernel:  gran_size: 16M         chunk_size: 16M         num_reg: 6          lose cover RAM: 16380K
[    1.837174] cachyos kernel:  gran_size: 16M         chunk_size: 32M         num_reg: 6          lose cover RAM: 16380K
[    1.837186] cachyos kernel:  gran_size: 16M         chunk_size: 64M         num_reg: 6          lose cover RAM: 16380K
[    1.837198] cachyos kernel:  gran_size: 16M         chunk_size: 128M         num_reg: 5          lose cover RAM: 16380K
[    1.837210] cachyos kernel:  gran_size: 16M         chunk_size: 256M         num_reg: 5          lose cover RAM: 16380K
[    1.837221] cachyos kernel:  gran_size: 16M         chunk_size: 512M         num_reg: 5          lose cover RAM: 16380K
[    1.837233] cachyos kernel:  gran_size: 16M         chunk_size: 1G         num_reg: 6          lose cover RAM: 16380K
[    1.837245] cachyos kernel:  gran_size: 16M         chunk_size: 2G         num_reg: 6          lose cover RAM: 16380K
[    1.837256] cachyos kernel:  gran_size: 32M         chunk_size: 32M         num_reg: 6          lose cover RAM: 16380K
[    1.837268] cachyos kernel:  gran_size: 32M         chunk_size: 64M         num_reg: 6          lose cover RAM: 16380K
[    1.837280] cachyos kernel:  gran_size: 32M         chunk_size: 128M         num_reg: 5          lose cover RAM: 16380K
[    1.837292] cachyos kernel:  gran_size: 32M         chunk_size: 256M         num_reg: 5          lose cover RAM: 16380K
[    1.837303] cachyos kernel:  gran_size: 32M         chunk_size: 512M         num_reg: 5          lose cover RAM: 16380K
[    1.837315] cachyos kernel:  gran_size: 32M         chunk_size: 1G         num_reg: 6          lose cover RAM: 16380K
[    1.837327] cachyos kernel:  gran_size: 32M         chunk_size: 2G         num_reg: 6          lose cover RAM: 16380K
[    1.837338] cachyos kernel:  gran_size: 64M         chunk_size: 64M         num_reg: 6          lose cover RAM: 16380K
[    1.837350] cachyos kernel:  gran_size: 64M         chunk_size: 128M         num_reg: 5          lose cover RAM: 16380K
[    1.837362] cachyos kernel:  gran_size: 64M         chunk_size: 256M         num_reg: 5          lose cover RAM: 16380K
[    1.837373] cachyos kernel:  gran_size: 64M         chunk_size: 512M         num_reg: 5          lose cover RAM: 16380K
[    1.837385] cachyos kernel:  gran_size: 64M         chunk_size: 1G         num_reg: 6          lose cover RAM: 16380K
[    1.837397] cachyos kernel:  gran_size: 64M         chunk_size: 2G         num_reg: 6          lose cover RAM: 16380K
[    1.837409] cachyos kernel:  gran_size: 128M         chunk_size: 128M         num_reg: 5          lose cover RAM: 81916K
[    1.837421] cachyos kernel:  gran_size: 128M         chunk_size: 256M         num_reg: 5          lose cover RAM: 81916K
[    1.837432] cachyos kernel:  gran_size: 128M         chunk_size: 512M         num_reg: 5          lose cover RAM: 81916K
[    1.837444] cachyos kernel:  gran_size: 128M         chunk_size: 1G         num_reg: 6          lose cover RAM: 81916K
[    1.837456] cachyos kernel:  gran_size: 128M         chunk_size: 2G         num_reg: 6          lose cover RAM: 81916K
[    1.837468] cachyos kernel:  gran_size: 256M         chunk_size: 256M         num_reg: 4          lose cover RAM: 212988K
[    1.837480] cachyos kernel:  gran_size: 256M         chunk_size: 512M         num_reg: 5          lose cover RAM: 212988K
[    1.837492] cachyos kernel:  gran_size: 256M         chunk_size: 1G         num_reg: 6          lose cover RAM: 212988K
[    1.837504] cachyos kernel:  gran_size: 256M         chunk_size: 2G         num_reg: 6          lose cover RAM: 212988K
[    1.837515] cachyos kernel:  gran_size: 512M         chunk_size: 512M         num_reg: 3          lose cover RAM: 475132K
[    1.837527] cachyos kernel:  gran_size: 512M         chunk_size: 1G         num_reg: 3          lose cover RAM: 475132K
[    1.837539] cachyos kernel:  gran_size: 512M         chunk_size: 2G         num_reg: 3          lose cover RAM: 475132K
[    1.837550] cachyos kernel:  gran_size: 1G         chunk_size: 1G         num_reg: 3          lose cover RAM: 475132K
[    1.837562] cachyos kernel:  gran_size: 1G         chunk_size: 2G         num_reg: 3          lose cover RAM: 475132K
[    1.837574] cachyos kernel:  gran_size: 2G         chunk_size: 2G         num_reg: 3          lose cover RAM: 475132K
[    1.837586] cachyos kernel: mtrr_cleanup: can not find optimal value
[    1.837597] cachyos kernel: please specify mtrr_gran_size/mtrr_chunk_size
[    1.837609] cachyos kernel: MTRR map: 8 entries (5 fixed + 3 variable; max 25), built from 10 variable MTRRs
[    1.837620] cachyos kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[    1.837632] cachyos kernel: e820: update [mem 0x9cfff000-0xffffffff] usable ==> reserved
[    1.837644] cachyos kernel: last_pfn = 0x9cfff max_arch_pfn = 0x400000000
[    1.837656] cachyos kernel: esrt: Reserving ESRT space from 0x000000009bf8c118 to 0x000000009bf8c150.
[    1.837668] cachyos kernel: Using GB pages for direct mapping
[    1.837679] cachyos kernel: Secure boot could not be determined
[    1.837691] cachyos kernel: RAMDISK: [mem 0x7e800000-0x7ff70fff]
[    1.837702] cachyos kernel: ACPI: Early table checksum verification disabled
[    1.837714] cachyos kernel: ACPI: RSDP 0x000000009CFFD014 000024 (v02 HPQOEM)
[    1.837725] cachyos kernel: ACPI: XSDT 0x000000009CFCB188 000104 (v01 HPQOEM SLIC-MPC 00000001 HP   01000013)
[    1.837737] cachyos kernel: ACPI: FACP 0x000000009CFE6000 00010C (v05 HPQOEM SLIC-MPC 00000001 HP   00040000)
[    1.837749] cachyos kernel: ACPI: DSDT 0x000000009CFD0000 010934 (v02 HPQOEM SLIC-MPC 00000000 ACPI 00040000)
[    1.837760] cachyos kernel: ACPI: FACS 0x000000009CF74000 000040
[    1.837772] cachyos kernel: ACPI: TCPA 0x000000009CFFC000 000032 (v02 HPQOEM INSYDE   00000000 HP   00040000)
[    1.837783] cachyos kernel: ACPI: UEFI 0x000000009CFFB000 000236 (v01 HPQOEM INSYDE   00000001 HP   00040000)
[    1.837795] cachyos kernel: ACPI: UEFI 0x000000009CFFA000 000042 (v01 HPQOEM INSYDE   00000000 HP   00040000)
[    1.837806] cachyos kernel: ACPI: SSDT 0x000000009CFF9000 000496 (v02 HPQOEM INSYDE   00001000 ACPI 00040000)
[    1.837818] cachyos kernel: ACPI: SSDT 0x000000009CFF8000 00004B (v02 HPQOEM INSYDE   00003000 ACPI 00040000)
[    1.837829] cachyos kernel: ACPI: TPM2 0x000000009CFF7000 000034 (v03 HPQOEM INSYDE   00000000 HP   00040000)
[    1.837841] cachyos kernel: ACPI: SSDT 0x000000009CFF0000 00680A (v01 HPQOEM INSYDE   00001000 ACPI 00040000)
[    1.837853] cachyos kernel: ACPI: MSDM 0x000000009CFEF000 000055 (v03 HPQOEM SLIC-MPC 00000001 HP   00040000)
[    1.837864] cachyos kernel: ACPI: SSDT 0x000000009CFEB000 003B2D (v02 HPQOEM INSYDE   00001000 ACPI 00040000)
[    1.837876] cachyos kernel: ACPI: ASF! 0x000000009CFEA000 0000A5 (v32 HPQOEM INSYDE   00000001 HP   00040000)
[    1.837887] cachyos kernel: ACPI: ASPT 0x000000009CFE9000 000034 (v07 HPQOEM INSYDE   00000001 HP   00040000)
[    1.837899] cachyos kernel: ACPI: BOOT 0x000000009CFE8000 000028 (v01 HPQOEM INSYDE   00000001 HP   00040000)
[    1.837910] cachyos kernel: ACPI: DBGP 0x000000009CFE7000 000034 (v01 HPQOEM SLIC-MPC 00000001 HP   00040000)
[    1.837922] cachyos kernel: ACPI: HPET 0x000000009CFE5000 000038 (v01 HPQOEM INSYDE   00000001 HP   00040000)
[    1.837933] cachyos kernel: ACPI: LPIT 0x000000009CFE4000 000094 (v01 HPQOEM INSYDE   00000000 HP   00040000)
[    1.837944] cachyos kernel: ACPI: APIC 0x000000009CFE3000 00008C (v03 HPQOEM SLIC-MPC 00000001 HP   00040000)
[    1.837956] cachyos kernel: ACPI: MCFG 0x000000009CFE2000 00003C (v01 HPQOEM INSYDE   00000001 HP   00040000)
[    1.837968] cachyos kernel: ACPI: WDAT 0x000000009CFE1000 000224 (v01 HPQOEM INSYDE   00000001 HP   00040000)
[    1.837979] cachyos kernel: ACPI: SSDT 0x000000009CFCD000 002F87 (v02 HPQOEM INSYDE   00001000 ACPI 00040000)
[    1.837991] cachyos kernel: ACPI: SSDT 0x000000009CFCC000 000C12 (v02 HPQOEM INSYDE   00001000 ACPI 00040000)
[    1.838013] cachyos kernel: ACPI: SSDT 0x000000009CFCA000 000539 (v02 HPQOEM INSYDE   00003000 ACPI 00040000)
[    1.838026] cachyos kernel: ACPI: SSDT 0x000000009CFC9000 000B74 (v02 HPQOEM INSYDE   00003000 ACPI 00040000)
[    1.838037] cachyos kernel: ACPI: SSDT 0x000000009CFC3000 005FEF (v02 HPQOEM INSYDE   00003000 ACPI 00040000)
[    1.838049] cachyos kernel: ACPI: SSDT 0x000000009CFC1000 001AD0 (v01 HPQOEM INSYDE   00001000 ACPI 00040000)
[    1.838061] cachyos kernel: ACPI: DMAR 0x000000009CFC0000 0000B0 (v01 HPQOEM INSYDE   00000001 HP   00040000)
[    1.838072] cachyos kernel: ACPI: FPDT 0x000000009CFBF000 000044 (v01 HPQOEM SLIC-MPC 00000002 HP   00040000)
[    1.838084] cachyos kernel: ACPI: BGRT 0x000000009CFBE000 000038 (v01 HPQOEM INSYDE   00000001 HP   00040000)
[    1.838104] cachyos kernel: ACPI: Reserving FACP table memory at [mem 0x9cfe6000-0x9cfe610b]
[    1.838117] cachyos kernel: ACPI: Reserving DSDT table memory at [mem 0x9cfd0000-0x9cfe0933]
[    1.838128] cachyos kernel: ACPI: Reserving FACS table memory at [mem 0x9cf74000-0x9cf7403f]
[    1.838140] cachyos kernel: ACPI: Reserving TCPA table memory at [mem 0x9cffc000-0x9cffc031]
[    1.838151] cachyos kernel: ACPI: Reserving UEFI table memory at [mem 0x9cffb000-0x9cffb235]
[    1.838163] cachyos kernel: ACPI: Reserving UEFI table memory at [mem 0x9cffa000-0x9cffa041]
[    1.838174] cachyos kernel: ACPI: Reserving SSDT table memory at [mem 0x9cff9000-0x9cff9495]
[    1.838186] cachyos kernel: ACPI: Reserving SSDT table memory at [mem 0x9cff8000-0x9cff804a]
[    1.838197] cachyos kernel: ACPI: Reserving TPM2 table memory at [mem 0x9cff7000-0x9cff7033]
[    1.838208] cachyos kernel: ACPI: Reserving SSDT table memory at [mem 0x9cff0000-0x9cff6809]
[    1.838219] cachyos kernel: ACPI: Reserving MSDM table memory at [mem 0x9cfef000-0x9cfef054]
[    1.838231] cachyos kernel: ACPI: Reserving SSDT table memory at [mem 0x9cfeb000-0x9cfeeb2c]
[    1.838243] cachyos kernel: ACPI: Reserving ASF! table memory at [mem 0x9cfea000-0x9cfea0a4]
[    1.838254] cachyos kernel: ACPI: Reserving ASPT table memory at [mem 0x9cfe9000-0x9cfe9033]
[    1.838266] cachyos kernel: ACPI: Reserving BOOT table memory at [mem 0x9cfe8000-0x9cfe8027]
[    1.838278] cachyos kernel: ACPI: Reserving DBGP table memory at [mem 0x9cfe7000-0x9cfe7033]
[    1.838288] cachyos kernel: ACPI: Reserving HPET table memory at [mem 0x9cfe5000-0x9cfe5037]
[    1.838300] cachyos kernel: ACPI: Reserving LPIT table memory at [mem 0x9cfe4000-0x9cfe4093]
[    1.838311] cachyos kernel: ACPI: Reserving APIC table memory at [mem 0x9cfe3000-0x9cfe308b]
[    1.838323] cachyos kernel: ACPI: Reserving MCFG table memory at [mem 0x9cfe2000-0x9cfe203b]
[    1.838334] cachyos kernel: ACPI: Reserving WDAT table memory at [mem 0x9cfe1000-0x9cfe1223]
[    1.838345] cachyos kernel: ACPI: Reserving SSDT table memory at [mem 0x9cfcd000-0x9cfcff86]
[    1.838357] cachyos kernel: ACPI: Reserving SSDT table memory at [mem 0x9cfcc000-0x9cfccc11]
[    1.838367] cachyos kernel: ACPI: Reserving SSDT table memory at [mem 0x9cfca000-0x9cfca538]
[    1.838379] cachyos kernel: ACPI: Reserving SSDT table memory at [mem 0x9cfc9000-0x9cfc9b73]
[    1.838390] cachyos kernel: ACPI: Reserving SSDT table memory at [mem 0x9cfc3000-0x9cfc8fee]
[    1.838401] cachyos kernel: ACPI: Reserving SSDT table memory at [mem 0x9cfc1000-0x9cfc2acf]
[    1.838413] cachyos kernel: ACPI: Reserving DMAR table memory at [mem 0x9cfc0000-0x9cfc00af]
[    1.838425] cachyos kernel: ACPI: Reserving FPDT table memory at [mem 0x9cfbf000-0x9cfbf043]
[    1.838436] cachyos kernel: ACPI: Reserving BGRT table memory at [mem 0x9cfbe000-0x9cfbe037]
[    1.838448] cachyos kernel: No NUMA configuration found
[    1.838459] cachyos kernel: Faking a node at [mem 0x0000000000000000-0x000000035effffff]
[    1.838470] cachyos kernel: NODE_DATA(0) allocated [mem 0x35efd3280-0x35effdfff]
[    1.838482] cachyos kernel: Zone ranges:
[    1.838493] cachyos kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    1.838505] cachyos kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    1.838516] cachyos kernel:   Normal   [mem 0x0000000100000000-0x000000035effffff]
[    1.838528] cachyos kernel:   Device   empty
[    1.838539] cachyos kernel: Movable zone start for each node
[    1.838550] cachyos kernel: Early memory node ranges
[    1.838562] cachyos kernel:   node   0: [mem 0x0000000000001000-0x0000000000057fff]
[    1.838573] cachyos kernel:   node   0: [mem 0x0000000000059000-0x0000000000085fff]
[    1.838585] cachyos kernel:   node   0: [mem 0x0000000000100000-0x000000009b88dfff]
[    1.838596] cachyos kernel:   node   0: [mem 0x000000009cffe000-0x000000009cffefff]
[    1.838608] cachyos kernel:   node   0: [mem 0x0000000100000000-0x000000035effffff]
[    1.838620] cachyos kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000035effffff]
[    1.838631] cachyos kernel: On node 0, zone DMA: 1 pages in unavailable ranges
[    1.838643] cachyos kernel: On node 0, zone DMA: 1 pages in unavailable ranges
[    1.838654] cachyos kernel: On node 0, zone DMA: 122 pages in unavailable ranges
[    1.838665] cachyos kernel: On node 0, zone DMA32: 6000 pages in unavailable ranges
[    1.838677] cachyos kernel: On node 0, zone Normal: 12289 pages in unavailable ranges
[    1.838688] cachyos kernel: On node 0, zone Normal: 4096 pages in unavailable ranges
[    1.838700] cachyos kernel: Reserving Intel graphics memory at [mem 0x9e000000-0x9fffffff]
[    1.838711] cachyos kernel: ACPI: PM-Timer IO Port: 0x1808
[    1.838723] cachyos kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-39
[    1.838734] cachyos kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    1.838746] cachyos kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    1.838757] cachyos kernel: ACPI: Using ACPI (MADT) for SMP configuration information
[    1.838768] cachyos kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    1.838780] cachyos kernel: e820: update [mem 0x8d2fa000-0x8d303fff] usable ==> reserved
[    1.838792] cachyos kernel: TSC deadline timer available
[    1.838803] cachyos kernel: CPU topo: Max. logical packages:   1
[    1.838815] cachyos kernel: CPU topo: Max. logical nodes:      1
[    1.838826] cachyos kernel: CPU topo: Num. nodes per package:  1
[    1.838838] cachyos kernel: CPU topo: Max. logical dies:       1
[    1.838849] cachyos kernel: CPU topo: Max. dies per package:   1
[    1.838860] cachyos kernel: CPU topo: Max. threads per core:   2
[    1.838871] cachyos kernel: CPU topo: Num. cores per package:     2
[    1.838890] cachyos kernel: CPU topo: Num. threads per package:   4
[    1.838911] cachyos kernel: CPU topo: Allowing 4 present CPUs plus 0 hotplug CPUs
[    1.838932] cachyos kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    1.838953] cachyos kernel: PM: hibernation: Registered nosave memory: [mem 0x00058000-0x00058fff]
[    1.838974] cachyos kernel: PM: hibernation: Registered nosave memory: [mem 0x00086000-0x000fffff]
[    1.838994] cachyos kernel: PM: hibernation: Registered nosave memory: [mem 0x8d2fa000-0x8d303fff]
[    1.839023] cachyos kernel: PM: hibernation: Registered nosave memory: [mem 0x9b88e000-0x9cffdfff]
[    1.839045] cachyos kernel: PM: hibernation: Registered nosave memory: [mem 0x9cfff000-0xffffffff]
[    1.839066] cachyos kernel: [mem 0xa0000000-0xfeafffff] available for PCI devices
[    1.839088] cachyos kernel: Booting paravirtualized kernel on bare hardware
[    1.839111] cachyos kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[    1.839134] cachyos kernel: setup_percpu: NR_CPUS:8192 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1
[    1.839153] cachyos kernel: percpu: Embedded 63 pages/cpu s221184 r8192 d28672 u524288
[    1.839174] cachyos kernel: pcpu-alloc: s221184 r8192 d28672 u524288 alloc=1*2097152
[    1.839196] cachyos kernel: pcpu-alloc: [0] 0 1 2 3 
[    1.839219] cachyos kernel: Kernel command line: resume=UUID=450aafdc-613a-4cf9-bdbb-eb338b606697 resume_offset=7243593 quiet nowatchdog splash rw rootflags=subvol=/@ root=UUID=450aafdc-613a-4cf9-bdbb-eb338b606697
[    1.839244] cachyos kernel: Unknown kernel command line parameters "splash", will be passed to user space.
[    1.839266] cachyos kernel: random: crng init done
[    1.839289] cachyos kernel: printk: log buffer data + meta data: 131072 + 458752 = 589824 bytes
[    1.839312] cachyos kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[    1.839335] cachyos kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[    1.839357] cachyos kernel: software IO TLB: area num 4.
[    1.839380] cachyos kernel: Fallback order for Node 0: 0 
[    1.839402] cachyos kernel: Built 1 zonelists, mobility grouping on.  Total pages: 3123219
[    1.839426] cachyos kernel: Policy zone: Normal
[    1.839448] cachyos kernel: mem auto-init: stack:all(zero), heap alloc:on, heap free:off
[    1.839473] cachyos kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    1.839496] cachyos kernel: Kernel/User page tables isolation: enabled
[    1.839520] cachyos kernel: ftrace: allocating 56386 entries in 221 pages
[    1.839543] cachyos kernel: ftrace: allocated 221 pages with 6 groups
[    1.839565] cachyos kernel: Dynamic Preempt: full
[    1.839588] cachyos kernel: rcu: Preemptible hierarchical RCU implementation.
[    1.839612] cachyos kernel: rcu:         RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=4.
[    1.839635] cachyos kernel: rcu:         RCU priority boosting: priority 1 delay 500 ms.
[    1.839658] cachyos kernel:         Trampoline variant of Tasks RCU enabled.
[    1.839681] cachyos kernel:         Rude variant of Tasks RCU enabled.
[    1.839704] cachyos kernel:         Tracing variant of Tasks RCU enabled.
[    1.839724] cachyos kernel: rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[    1.839746] cachyos kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    1.839768] cachyos kernel: RCU Tasks: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
[    1.839790] cachyos kernel: RCU Tasks Rude: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
[    1.839811] cachyos kernel: RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
[    1.839830] cachyos kernel: NR_IRQS: 524544, nr_irqs: 728, preallocated irqs: 16
[    1.839849] cachyos kernel: rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    1.839871] cachyos kernel: kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval____)-0x(____ptrval____)
[    1.839892] cachyos kernel: Console: colour dummy device 80x25
[    1.839915] cachyos kernel: printk: legacy console [tty0] enabled
[    1.839936] cachyos kernel: ACPI: Core revision 20250807
[    1.839958] cachyos kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
[    1.839981] cachyos kernel: APIC: Switch to symmetric I/O mode setup
[    1.840011] cachyos kernel: DMAR: Host address width 39
[    1.840033] cachyos kernel: DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    1.840056] cachyos kernel: DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e1ff0505e
[    1.840077] cachyos kernel: DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    1.840100] cachyos kernel: DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c20660462 ecap f010da
[    1.840121] cachyos kernel: DMAR: RMRR base: 0x0000009cc63000 end: 0x0000009cc82fff
[    1.840143] cachyos kernel: DMAR: RMRR base: 0x0000009d800000 end: 0x0000009fffffff
[    1.840167] cachyos kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000009d800000-0x000000009fffffff], contact BIOS vendor for fixes
[    1.840192] cachyos kernel: DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x000000009d800000-0x000000009fffffff]
                               BIOS vendor: Insyde; Ver: F.50; Product Version: Type1ProductConfigId
[    1.840217] cachyos kernel: DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    1.840238] cachyos kernel: DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    1.840261] cachyos kernel: DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[    1.840284] cachyos kernel: DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
[    1.840310] cachyos kernel: DMAR-IR: Enabled IRQ remapping in xapic mode
[    1.840332] cachyos kernel: x2apic: IRQ remapping doesn't support X2APIC mode
[    1.840354] cachyos kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    1.840376] cachyos kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x398667e26cb, max_idle_ns: 881590510388 ns
[    1.840399] cachyos kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3990.79 BogoMIPS (lpj=1995399)
[    1.840421] cachyos kernel: CPU0: Thermal monitoring enabled (TM1)
[    1.840443] cachyos kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
[    1.840464] cachyos kernel: Last level dTLB entries: 4KB 64, 2MB 32, 4MB 32, 1GB 4
[    1.840487] cachyos kernel: process: using mwait in idle threads
[    1.840509] cachyos kernel: mitigations: Enabled attack vectors: user_kernel, user_user, guest_host, guest_guest, SMT mitigations: auto
[    1.840532] cachyos kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
[    1.840553] cachyos kernel: SRBDS: Mitigation: Microcode
[    1.840574] cachyos kernel: Spectre V2 : Mitigation: Retpolines
[    1.840594] cachyos kernel: Spectre V2 : User space: Mitigation: STIBP via prctl
[    1.840615] cachyos kernel: MDS: Mitigation: Clear CPU buffers
[    1.840635] cachyos kernel: VMSCAPE: Mitigation: IBPB before exit to userspace
[    1.840656] cachyos kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    1.840676] cachyos kernel: Spectre V2 : Spectre v2 / SpectreRSB: Filling RSB on context switch and VMEXIT
[    1.840697] cachyos kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls
[    1.840719] cachyos kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    1.840739] cachyos kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    1.840760] cachyos kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    1.840782] cachyos kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    1.840804] cachyos kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    1.840827] cachyos kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[    1.840849] cachyos kernel: Freeing SMP alternatives memory: 64K
[    1.840871] cachyos kernel: pid_max: default: 32768 minimum: 301
[    1.840892] cachyos kernel: landlock: Up and running.
[    1.840913] cachyos kernel: Yama: becoming mindful.
[    1.840935] cachyos kernel: LSM support for eBPF active
[    1.840957] cachyos kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    1.840979] cachyos kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    1.841009] cachyos kernel: smpboot: CPU0: Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz (family: 0x6, model: 0x3d, stepping: 0x4)
[    1.841033] cachyos kernel: Performance Events: PEBS fmt2+, Broadwell events, 16-deep LBR, full-width counters, Intel PMU driver.
[    1.841054] cachyos kernel: ... version:                   3
[    1.841076] cachyos kernel: ... bit width:                 48
[    1.841098] cachyos kernel: ... generic counters:          4
[    1.841120] cachyos kernel: ... generic bitmap:            000000000000000f
[    1.841141] cachyos kernel: ... fixed-purpose counters:    3
[    1.841162] cachyos kernel: ... fixed-purpose bitmap:      0000000000000007
[    1.841184] cachyos kernel: ... value mask:                0000ffffffffffff
[    1.841205] cachyos kernel: ... max period:                00007fffffffffff
[    1.841226] cachyos kernel: ... global_ctrl mask:          000000070000000f
[    1.841247] cachyos kernel: signal: max sigframe size: 1776
[    1.841268] cachyos kernel: Estimated ratio of average max frequency by base frequency (times 1024): 1024
[    1.841288] cachyos kernel: rcu: Hierarchical SRCU implementation.
[    1.841309] cachyos kernel: rcu:         Max phase no-delay instances is 400.
[    1.841329] cachyos kernel: Timer migration: 1 hierarchy levels; 8 children per group; 1 crossnode level
[    1.841349] cachyos kernel: smp: Bringing up secondary CPUs ...
[    1.841369] cachyos kernel: smpboot: x86: Booting SMP configuration:
[    1.841389] cachyos kernel: .... node  #0, CPUs:      #1 #2 #3
[    1.841410] cachyos kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    1.841432] cachyos kernel: VMSCAPE: SMT on, STIBP is required for full protection. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/vmscape.html for more details.
[    1.841451] cachyos kernel: smp: Brought up 1 node, 4 CPUs
[    1.841470] cachyos kernel: smpboot: Total of 4 processors activated (15963.19 BogoMIPS)
[    1.841490] cachyos kernel: Memory: 12061248K/12492876K available (22081K kernel code, 2851K rwdata, 16320K rodata, 4676K init, 4652K bss, 419492K reserved, 0K cma-reserved)
[    1.841511] cachyos kernel: le9 Unofficial (le9uo) working set protection 1.15a by Masahito Suzuki (forked from hakavlad's original le9 patch)
[    1.841533] cachyos kernel: devtmpfs: initialized
[    1.841553] cachyos kernel: x86/mm: Memory block size: 128MB
[    1.841573] cachyos kernel: ACPI: PM: Registering ACPI NVS region [mem 0x9cc8e000-0x9cf8dfff] (3145728 bytes)
[    1.841594] cachyos kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[    1.841615] cachyos kernel: posixtimers hash table entries: 2048 (order: 3, 32768 bytes, linear)
[    1.841635] cachyos kernel: futex hash table entries: 1024 (65536 bytes on 1 NUMA nodes, total 64 KiB, linear).
[    1.841654] cachyos kernel: PM: RTC time: 11:58:47, date: 2026-03-27
[    1.841675] cachyos kernel: NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    1.841696] cachyos kernel: DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations
[    1.841716] cachyos kernel: DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    1.841738] cachyos kernel: DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    1.841759] cachyos kernel: audit: initializing netlink subsys (disabled)
[    1.841780] cachyos kernel: audit: type=2000 audit(1774612727.047:1): state=initialized audit_enabled=0 res=1
[    1.841800] cachyos kernel: thermal_sys: Registered thermal governor 'fair_share'
[    1.841821] cachyos kernel: thermal_sys: Registered thermal governor 'bang_bang'
[    1.841842] cachyos kernel: thermal_sys: Registered thermal governor 'step_wise'
[    1.841863] cachyos kernel: thermal_sys: Registered thermal governor 'user_space'
[    1.841884] cachyos kernel: thermal_sys: Registered thermal governor 'power_allocator'
[    1.841904] cachyos kernel: cpuidle: using governor ladder
[    1.841926] cachyos kernel: cpuidle: using governor menu
[    1.841946] cachyos kernel: Simple Boot Flag at 0x44 set to 0x1
[    1.841966] cachyos kernel: efi: Freeing EFI boot services memory: 46472K
[    1.841987] cachyos kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    1.842016] cachyos kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    1.842038] cachyos kernel: PCI: ECAM [mem 0xe0000000-0xefffffff] (base 0xe0000000) for domain 0000 [bus 00-ff]
[    1.842059] cachyos kernel: PCI: Using configuration type 1 for base access
[    1.842080] cachyos kernel: kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
[    1.842102] cachyos kernel: HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[    1.842122] cachyos kernel: HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page
[    1.842143] cachyos kernel: HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[    1.842162] cachyos kernel: HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page
[    1.842181] cachyos kernel: raid6: skipped pq benchmark and selected avx2x4
[    1.842201] cachyos kernel: raid6: using avx2x2 recovery algorithm
[    1.842222] cachyos kernel: ACPI: Added _OSI(Module Device)
[    1.842244] cachyos kernel: ACPI: Added _OSI(Processor Device)
[    1.842265] cachyos kernel: ACPI: Added _OSI(Processor Aggregator Device)
[    1.842286] cachyos kernel: ACPI: 11 ACPI AML tables successfully acquired and loaded
[    1.842307] cachyos kernel: ACPI: Dynamic OEM Table Load:
[    1.842328] cachyos kernel: ACPI: SSDT 0xFFFF88E68140F400 0003D3 (v02 PmRef  Cpu0Cst  00003001 INTL 20120711)
[    1.842348] cachyos kernel: ACPI: Dynamic OEM Table Load:
[    1.842369] cachyos kernel: ACPI: SSDT 0xFFFF88E680FED800 0005AA (v02 PmRef  ApIst    00003000 INTL 20120711)
[    1.842389] cachyos kernel: ACPI: Dynamic OEM Table Load:
[    1.842410] cachyos kernel: ACPI: SSDT 0xFFFF88E680F86000 000119 (v02 PmRef  ApCst    00003000 INTL 20120711)
[    1.842431] cachyos kernel: ACPI: EC: EC started
[    1.842451] cachyos kernel: ACPI: EC: interrupt blocked
[    1.842472] cachyos kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    1.842495] cachyos kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: Boot DSDT EC used to handle transactions
[    1.842516] cachyos kernel: ACPI: Interpreter enabled
[    1.842536] cachyos kernel: ACPI: PM: (supports S0 S3 S4 S5)
[    1.842557] cachyos kernel: ACPI: Using IOAPIC for interrupt routing
[    1.842579] cachyos kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    1.842600] cachyos kernel: PCI: Using E820 reservations for host bridge windows
[    1.842621] cachyos kernel: ACPI: watchdog: Skipping WDAT on this system because it uses RTC SRAM
[    1.842642] cachyos kernel: ACPI: Enabled 8 GPEs in block 00 to 7F
[    1.842663] cachyos kernel: ACPI: \_SB_.PCI0.RP05.PC05: New power resource
[    1.842685] cachyos kernel: ACPI: \_TZ_.FN00: New power resource
[    1.842706] cachyos kernel: ACPI: \_TZ_.FN01: New power resource
[    1.842727] cachyos kernel: ACPI: \_TZ_.FN02: New power resource
[    1.842749] cachyos kernel: ACPI: \_TZ_.FN03: New power resource
[    1.842770] cachyos kernel: ACPI: \_TZ_.FN04: New power resource
[    1.842791] cachyos kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
[    1.843423] cachyos kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
[    1.843855] cachyos kernel: acpi PNP0A08:00: _OSC: OS requested [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR DPC]
[    1.844281] cachyos kernel: acpi PNP0A08:00: _OSC: platform willing to grant [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR DPC]
[    1.844699] cachyos kernel: acpi PNP0A08:00: _OSC: platform retains control of PCIe features (AE_ERROR)
[    1.844734] cachyos kernel: PCI host bridge to bus 0000:00
[    1.845186] cachyos kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    1.845593] cachyos kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    1.845980] cachyos kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000fffff window]
[    1.846373] cachyos kernel: pci_bus 0000:00: root bus resource [mem 0xa0000000-0xdfffffff window]
[    1.846747] cachyos kernel: pci_bus 0000:00: root bus resource [mem 0xfe000000-0xfe113fff window]
[    1.847129] cachyos kernel: pci_bus 0000:00: root bus resource [bus 00-fe]
[    1.847576] cachyos kernel: pci 0000:00:00.0: [8086:1604] type 00 class 0x060000 conventional PCI endpoint
[    1.847996] cachyos kernel: pci 0000:00:02.0: [8086:1616] type 00 class 0x030000 conventional PCI endpoint
[    1.848425] cachyos kernel: pci 0000:00:02.0: BAR 0 [mem 0xd2000000-0xd2ffffff 64bit]
[    1.848835] cachyos kernel: pci 0000:00:02.0: BAR 2 [mem 0xc0000000-0xcfffffff 64bit pref]
[    1.849255] cachyos kernel: pci 0000:00:02.0: BAR 4 [io  0x7000-0x703f]
[    1.849655] cachyos kernel: pci 0000:00:02.0: DMAR: Disabling IOMMU for graphics on this chipset
[    1.850074] cachyos kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    1.850506] cachyos kernel: pci 0000:00:03.0: [8086:160c] type 00 class 0x040300 PCIe Root Complex Integrated Endpoint
[    1.850798] cachyos kernel: pci 0000:00:03.0: BAR 0 [mem 0xd6218000-0xd621bfff 64bit]
[    1.851083] cachyos kernel: pci 0000:00:04.0: [8086:1603] type 00 class 0x118000 conventional PCI endpoint
[    1.851350] cachyos kernel: pci 0000:00:04.0: BAR 0 [mem 0xd6210000-0xd6217fff 64bit]
[    1.851626] cachyos kernel: pci 0000:00:14.0: [8086:9cb1] type 00 class 0x0c0330 conventional PCI endpoint
[    1.851894] cachyos kernel: pci 0000:00:14.0: BAR 0 [mem 0xd6200000-0xd620ffff 64bit]
[    1.852171] cachyos kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
[    1.852431] cachyos kernel: pci 0000:00:16.0: [8086:9cba] type 00 class 0x078000 conventional PCI endpoint
[    1.852692] cachyos kernel: pci 0000:00:16.0: BAR 0 [mem 0xd6221000-0xd622101f 64bit]
[    1.852951] cachyos kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[    1.853228] cachyos kernel: pci 0000:00:1b.0: [8086:9ca0] type 00 class 0x040300 conventional PCI endpoint
[    1.853489] cachyos kernel: pci 0000:00:1b.0: BAR 0 [mem 0xd621c000-0xd621ffff 64bit]
[    1.853749] cachyos kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[    1.854032] cachyos kernel: pci 0000:00:1c.0: [8086:9c90] type 01 class 0x060400 PCIe Root Port
[    1.854297] cachyos kernel: pci 0000:00:1c.0: PCI bridge to [bus 01-06]
[    1.854561] cachyos kernel: pci 0000:00:1c.0:   bridge window [io  0x6000-0x6fff]
[    1.854823] cachyos kernel: pci 0000:00:1c.0:   bridge window [mem 0xd7000000-0xd7ffffff]
[    1.855096] cachyos kernel: pci 0000:00:1c.0:   bridge window [mem 0xd0000000-0xd0ffffff 64bit pref]
[    1.855358] cachyos kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    1.855627] cachyos kernel: pci 0000:00:1c.2: [8086:9c94] type 01 class 0x060400 PCIe Root Port
[    1.855891] cachyos kernel: pci 0000:00:1c.2: PCI bridge to [bus 07-0c]
[    1.856166] cachyos kernel: pci 0000:00:1c.2:   bridge window [io  0x5000-0x5fff]
[    1.856428] cachyos kernel: pci 0000:00:1c.2:   bridge window [mem 0xd5000000-0xd60fffff]
[    1.856693] cachyos kernel: pci 0000:00:1c.2:   bridge window [mem 0xd6100000-0xd61fffff 64bit pref]
[    1.856954] cachyos kernel: pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
[    1.857367] cachyos kernel: pci 0000:00:1c.4: [8086:9c98] type 01 class 0x060400 PCIe Root Port
[    1.857813] cachyos kernel: pci 0000:00:1c.4: PCI bridge to [bus 0d-12]
[    1.858233] cachyos kernel: pci 0000:00:1c.4:   bridge window [io  0x4000-0x4fff]
[    1.858683] cachyos kernel: pci 0000:00:1c.4:   bridge window [mem 0xd4000000-0xd4ffffff]
[    1.859136] cachyos kernel: pci 0000:00:1c.4:   bridge window [mem 0xb0000000-0xbfffffff 64bit pref]
[    1.859523] cachyos kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[    1.859804] cachyos kernel: pci 0000:00:1c.5: [8086:9c9a] type 01 class 0x060400 PCIe Root Port
[    1.860097] cachyos kernel: pci 0000:00:1c.5: PCI bridge to [bus 13-18]
[    1.860365] cachyos kernel: pci 0000:00:1c.5:   bridge window [io  0x3000-0x3fff]
[    1.860632] cachyos kernel: pci 0000:00:1c.5:   bridge window [mem 0xd3000000-0xd3ffffff]
[    1.860893] cachyos kernel: pci 0000:00:1c.5:   bridge window [mem 0xd1000000-0xd1ffffff 64bit pref]
[    1.861167] cachyos kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[    1.861432] cachyos kernel: pci 0000:00:1d.0: [8086:9ca6] type 00 class 0x0c0320 conventional PCI endpoint
[    1.861696] cachyos kernel: pci 0000:00:1d.0: BAR 0 [mem 0xd6225000-0xd62253ff]
[    1.861957] cachyos kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[    1.862230] cachyos kernel: pci 0000:00:1f.0: [8086:9cc5] type 00 class 0x060100 conventional PCI endpoint
[    1.862493] cachyos kernel: pci 0000:00:1f.2: [8086:9c83] type 00 class 0x010601 conventional PCI endpoint
[    1.862764] cachyos kernel: pci 0000:00:1f.2: BAR 0 [io  0x7088-0x708f]
[    1.863042] cachyos kernel: pci 0000:00:1f.2: BAR 1 [io  0x7094-0x7097]
[    1.863304] cachyos kernel: pci 0000:00:1f.2: BAR 2 [io  0x7080-0x7087]
[    1.863566] cachyos kernel: pci 0000:00:1f.2: BAR 3 [io  0x7090-0x7093]
[    1.863829] cachyos kernel: pci 0000:00:1f.2: BAR 4 [io  0x7060-0x707f]
[    1.864100] cachyos kernel: pci 0000:00:1f.2: BAR 5 [mem 0xd6224000-0xd62247ff]
[    1.864362] cachyos kernel: pci 0000:00:1f.2: PME# supported from D3hot
[    1.864624] cachyos kernel: pci 0000:00:1f.3: [8086:9ca2] type 00 class 0x0c0500 conventional PCI endpoint
[    1.864885] cachyos kernel: pci 0000:00:1f.3: BAR 0 [mem 0xd6220000-0xd62200ff 64bit]
[    1.865155] cachyos kernel: pci 0000:00:1f.3: BAR 4 [io  0x7040-0x705f]
[    1.865416] cachyos kernel: pci 0000:00:1f.6: [8086:9ca4] type 00 class 0x118000 conventional PCI endpoint
[    1.865672] cachyos kernel: pci 0000:00:1f.6: BAR 0 [mem 0xd6223000-0xd6223fff 64bit]
[    1.865934] cachyos kernel: pci 0000:00:1c.0: PCI bridge to [bus 01-06]
[    1.866217] cachyos kernel: pci 0000:07:00.0: [10ec:8136] type 00 class 0x020000 PCIe Endpoint
[    1.866487] cachyos kernel: pci 0000:07:00.0: BAR 0 [io  0x5000-0x50ff]
[    1.866758] cachyos kernel: pci 0000:07:00.0: BAR 2 [mem 0xd6000000-0xd6000fff 64bit]
[    1.867037] cachyos kernel: pci 0000:07:00.0: BAR 4 [mem 0xd6100000-0xd6103fff 64bit pref]
[    1.867310] cachyos kernel: pci 0000:07:00.0: supports D1 D2
[    1.867579] cachyos kernel: pci 0000:07:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    1.867841] cachyos kernel: pci 0000:00:1c.2: PCI bridge to [bus 07-0c]
[    1.868147] cachyos kernel: pci 0000:0d:00.0: [1002:6660] type 00 class 0x038000 PCIe Legacy Endpoint
[    1.868420] cachyos kernel: pci 0000:0d:00.0: BAR 0 [mem 0xb0000000-0xbfffffff 64bit pref]
[    1.868690] cachyos kernel: pci 0000:0d:00.0: BAR 2 [mem 0xd4000000-0xd403ffff 64bit]
[    1.868957] cachyos kernel: pci 0000:0d:00.0: BAR 4 [io  0x4000-0x40ff]
[    1.869239] cachyos kernel: pci 0000:0d:00.0: ROM [mem 0xfffe0000-0xffffffff pref]
[    1.869512] cachyos kernel: pci 0000:0d:00.0: enabling Extended Tags
[    1.869782] cachyos kernel: pci 0000:0d:00.0: supports D1 D2
[    1.870064] cachyos kernel: pci 0000:0d:00.0: PME# supported from D1 D2 D3hot
[    1.870338] cachyos kernel: pci 0000:0d:00.0: 16.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x4 link at 0000:00:1c.4 (capable of 32.000 Gb/s with 5.0 GT/s PCIe x8 link)
[    1.870601] cachyos kernel: pci 0000:00:1c.4: PCI bridge to [bus 0d-12]
[    1.870872] cachyos kernel: pci 0000:13:00.0: [10ec:c821] type 00 class 0x028000 PCIe Endpoint
[    1.871155] cachyos kernel: pci 0000:13:00.0: BAR 0 [io  0x3000-0x30ff]
[    1.871429] cachyos kernel: pci 0000:13:00.0: BAR 2 [mem 0xd3000000-0xd300ffff 64bit]
[    1.871699] cachyos kernel: pci 0000:13:00.0: supports D1 D2
[    1.871968] cachyos kernel: pci 0000:13:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    1.872245] cachyos kernel: pci 0000:00:1c.5: PCI bridge to [bus 13-18]
[    1.872262] cachyos kernel: ACPI: PCI: Interrupt link LNKA configured for IRQ 0
[    1.872275] cachyos kernel: ACPI: PCI: Interrupt link LNKA disabled
[    1.872287] cachyos kernel: ACPI: PCI: Interrupt link LNKB configured for IRQ 0
[    1.872298] cachyos kernel: ACPI: PCI: Interrupt link LNKB disabled
[    1.872310] cachyos kernel: ACPI: PCI: Interrupt link LNKC configured for IRQ 0
[    1.872321] cachyos kernel: ACPI: PCI: Interrupt link LNKC disabled
[    1.872333] cachyos kernel: ACPI: PCI: Interrupt link LNKD configured for IRQ 0
[    1.872344] cachyos kernel: ACPI: PCI: Interrupt link LNKD disabled
[    1.872355] cachyos kernel: ACPI: PCI: Interrupt link LNKE configured for IRQ 0
[    1.872367] cachyos kernel: ACPI: PCI: Interrupt link LNKE disabled
[    1.872378] cachyos kernel: ACPI: PCI: Interrupt link LNKF configured for IRQ 0
[    1.872390] cachyos kernel: ACPI: PCI: Interrupt link LNKF disabled
[    1.872401] cachyos kernel: ACPI: PCI: Interrupt link LNKG configured for IRQ 0
[    1.872412] cachyos kernel: ACPI: PCI: Interrupt link LNKG disabled
[    1.872424] cachyos kernel: ACPI: PCI: Interrupt link LNKH configured for IRQ 0
[    1.872435] cachyos kernel: ACPI: PCI: Interrupt link LNKH disabled
[    1.872447] cachyos kernel: ACPI: EC: interrupt unblocked
[    1.872458] cachyos kernel: ACPI: EC: event unblocked
[    1.872470] cachyos kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    1.872481] cachyos kernel: ACPI: EC: GPE=0xa
[    1.872494] cachyos kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: Boot DSDT EC initialization complete
[    1.872506] cachyos kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: EC: Used to handle transactions and events
[    1.872517] cachyos kernel: iommu: Default domain type: Translated
[    1.872529] cachyos kernel: iommu: DMA domain TLB invalidation policy: lazy mode
[    1.872540] cachyos kernel: SCSI subsystem initialized
[    1.872551] cachyos kernel: libata version 3.00 loaded.
[    1.872562] cachyos kernel: ACPI: bus type USB registered
[    1.872573] cachyos kernel: usbcore: registered new interface driver usbfs
[    1.872584] cachyos kernel: usbcore: registered new interface driver hub
[    1.872595] cachyos kernel: usbcore: registered new device driver usb
[    1.872605] cachyos kernel: EDAC MC: Ver: 3.0.0
[    1.872616] cachyos kernel: efivars: Registered efivars operations
[    1.872627] cachyos kernel: NetLabel: Initializing
[    1.872638] cachyos kernel: NetLabel:  domain hash size = 128
[    1.872649] cachyos kernel: NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    1.872659] cachyos kernel: NetLabel:  unlabeled traffic allowed by default
[    1.872670] cachyos kernel: mctp: management component transport protocol core
[    1.872681] cachyos kernel: NET: Registered PF_MCTP protocol family
[    1.872692] cachyos kernel: PCI: Using ACPI for IRQ routing
[    1.872702] cachyos kernel: PCI: pci_cache_line_size set to 64 bytes
[    1.872714] cachyos kernel: e820: reserve RAM buffer [mem 0x00058000-0x0005ffff]
[    1.872726] cachyos kernel: e820: reserve RAM buffer [mem 0x00086000-0x0008ffff]
[    1.872738] cachyos kernel: e820: reserve RAM buffer [mem 0x8d2fa000-0x8fffffff]
[    1.872749] cachyos kernel: e820: reserve RAM buffer [mem 0x9b88e000-0x9bffffff]
[    1.872761] cachyos kernel: e820: reserve RAM buffer [mem 0x9cfff000-0x9fffffff]
[    1.872772] cachyos kernel: e820: reserve RAM buffer [mem 0x35f000000-0x35fffffff]
[    1.873035] cachyos kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device
[    1.873296] cachyos kernel: pci 0000:00:02.0: vgaarb: bridge control possible
[    1.873553] cachyos kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[    1.873570] cachyos kernel: vgaarb: loaded
[    1.873582] cachyos kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[    1.873593] cachyos kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[    1.873604] cachyos kernel: clocksource: Switched to clocksource tsc-early
[    1.873616] cachyos kernel: VFS: Disk quotas dquot_6.6.0
[    1.873628] cachyos kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.873640] cachyos kernel: pnp: PnP ACPI init
[    1.873893] cachyos kernel: system 00:00: [io  0x0680-0x069f] has been reserved
[    1.874149] cachyos kernel: system 00:00: [io  0xfd60-0xfd63] has been reserved
[    1.874397] cachyos kernel: system 00:00: [io  0xffff] has been reserved
[    1.874640] cachyos kernel: system 00:00: [io  0xffff] has been reserved
[    1.874886] cachyos kernel: system 00:00: [io  0xffff] has been reserved
[    1.875136] cachyos kernel: system 00:00: [io  0x1800-0x18fe] could not be reserved
[    1.875382] cachyos kernel: system 00:00: [io  0x164e-0x164f] has been reserved
[    1.875628] cachyos kernel: system 00:05: [mem 0xfed1c000-0xfed1ffff] has been reserved
[    1.875873] cachyos kernel: system 00:05: [mem 0xfed10000-0xfed17fff] has been reserved
[    1.876137] cachyos kernel: system 00:05: [mem 0xfed18000-0xfed18fff] has been reserved
[    1.876385] cachyos kernel: system 00:05: [mem 0xfed19000-0xfed19fff] has been reserved
[    1.876630] cachyos kernel: system 00:05: [mem 0xe0000000-0xefffffff] has been reserved
[    1.876874] cachyos kernel: system 00:05: [mem 0xfed20000-0xfed3ffff] has been reserved
[    1.877143] cachyos kernel: system 00:05: [mem 0xfed90000-0xfed93fff] could not be reserved
[    1.877387] cachyos kernel: system 00:05: [mem 0xfed45000-0xfed8ffff] could not be reserved
[    1.877631] cachyos kernel: system 00:05: [mem 0xff000000-0xff000fff] has been reserved
[    1.877874] cachyos kernel: system 00:05: [mem 0xff010000-0xffffffff] has been reserved
[    1.878124] cachyos kernel: system 00:05: [mem 0xfee00000-0xfeefffff] could not be reserved
[    1.878367] cachyos kernel: system 00:05: [mem 0xa0010000-0xa001ffff] has been reserved
[    1.878612] cachyos kernel: system 00:05: [mem 0xa0000000-0xa000ffff] has been reserved
[    1.878629] cachyos kernel: pnp: PnP ACPI: found 6 devices
[    1.878641] cachyos kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    1.878653] cachyos kernel: NET: Registered PF_INET protocol family
[    1.878665] cachyos kernel: IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    1.878677] cachyos kernel: tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear)
[    1.878688] cachyos kernel: Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    1.878700] cachyos kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    1.878712] cachyos kernel: TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear)
[    1.878723] cachyos kernel: TCP: Hash tables configured (established 131072 bind 65536)
[    1.878735] cachyos kernel: MPTCP token hash table entries: 16384 (order: 7, 393216 bytes, linear)
[    1.878746] cachyos kernel: UDP hash table entries: 8192 (order: 7, 524288 bytes, linear)
[    1.878758] cachyos kernel: UDP-Lite hash table entries: 8192 (order: 7, 524288 bytes, linear)
[    1.878769] cachyos kernel: NET: Registered PF_UNIX/PF_LOCAL protocol family
[    1.878781] cachyos kernel: NET: Registered PF_XDP protocol family
[    1.879056] cachyos kernel: pci 0000:0d:00.0: ROM [mem 0xfffe0000-0xffffffff pref]: can't claim; no compatible bridge window
[    1.879321] cachyos kernel: pci 0000:00:1c.0: PCI bridge to [bus 01-06]
[    1.879582] cachyos kernel: pci 0000:00:1c.0:   bridge window [io  0x6000-0x6fff]
[    1.879844] cachyos kernel: pci 0000:00:1c.0:   bridge window [mem 0xd7000000-0xd7ffffff]
[    1.880118] cachyos kernel: pci 0000:00:1c.0:   bridge window [mem 0xd0000000-0xd0ffffff 64bit pref]
[    1.880380] cachyos kernel: pci 0000:00:1c.2: PCI bridge to [bus 07-0c]
[    1.880642] cachyos kernel: pci 0000:00:1c.2:   bridge window [io  0x5000-0x5fff]
[    1.880958] cachyos kernel: pci 0000:00:1c.2:   bridge window [mem 0xd5000000-0xd60fffff]
[    1.881360] cachyos kernel: pci 0000:00:1c.2:   bridge window [mem 0xd6100000-0xd61fffff 64bit pref]
[    1.881669] cachyos kernel: pci 0000:0d:00.0: ROM [mem 0xd4040000-0xd405ffff pref]: assigned
[    1.881939] cachyos kernel: pci 0000:00:1c.4: PCI bridge to [bus 0d-12]
[    1.882220] cachyos kernel: pci 0000:00:1c.4:   bridge window [io  0x4000-0x4fff]
[    1.882493] cachyos kernel: pci 0000:00:1c.4:   bridge window [mem 0xd4000000-0xd4ffffff]
[    1.882756] cachyos kernel: pci 0000:00:1c.4:   bridge window [mem 0xb0000000-0xbfffffff 64bit pref]
[    1.883031] cachyos kernel: pci 0000:00:1c.5: PCI bridge to [bus 13-18]
[    1.883296] cachyos kernel: pci 0000:00:1c.5:   bridge window [io  0x3000-0x3fff]
[    1.883630] cachyos kernel: pci 0000:00:1c.5:   bridge window [mem 0xd3000000-0xd3ffffff]
[    1.883962] cachyos kernel: pci 0000:00:1c.5:   bridge window [mem 0xd1000000-0xd1ffffff 64bit pref]
[    1.884235] cachyos kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    1.884484] cachyos kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
[    1.884726] cachyos kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000fffff window]
[    1.884976] cachyos kernel: pci_bus 0000:00: resource 7 [mem 0xa0000000-0xdfffffff window]
[    1.885227] cachyos kernel: pci_bus 0000:00: resource 8 [mem 0xfe000000-0xfe113fff window]
[    1.885498] cachyos kernel: pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
[    1.885753] cachyos kernel: pci_bus 0000:01: resource 1 [mem 0xd7000000-0xd7ffffff]
[    1.886050] cachyos kernel: pci_bus 0000:01: resource 2 [mem 0xd0000000-0xd0ffffff 64bit pref]
[    1.886322] cachyos kernel: pci_bus 0000:07: resource 0 [io  0x5000-0x5fff]
[    1.886578] cachyos kernel: pci_bus 0000:07: resource 1 [mem 0xd5000000-0xd60fffff]
[    1.886831] cachyos kernel: pci_bus 0000:07: resource 2 [mem 0xd6100000-0xd61fffff 64bit pref]
[    1.887107] cachyos kernel: pci_bus 0000:0d: resource 0 [io  0x4000-0x4fff]
[    1.887364] cachyos kernel: pci_bus 0000:0d: resource 1 [mem 0xd4000000-0xd4ffffff]
[    1.887616] cachyos kernel: pci_bus 0000:0d: resource 2 [mem 0xb0000000-0xbfffffff 64bit pref]
[    1.887880] cachyos kernel: pci_bus 0000:13: resource 0 [io  0x3000-0x3fff]
[    1.888195] cachyos kernel: pci_bus 0000:13: resource 1 [mem 0xd3000000-0xd3ffffff]
[    1.888448] cachyos kernel: pci_bus 0000:13: resource 2 [mem 0xd1000000-0xd1ffffff 64bit pref]
[    1.888721] cachyos kernel: pci 0000:00:14.0: can't derive routing for PCI INT A
[    1.888987] cachyos kernel: pci 0000:00:14.0: PCI INT A: not connected
[    1.889263] cachyos kernel: pci 0000:00:1d.0: __UNIQUE_ID_quirk_usb_early_handoff_633+0x0/0x870 took 11021 usecs
[    1.889282] cachyos kernel: PCI: CLS 64 bytes, default 64
[    1.889294] cachyos kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    1.889306] cachyos kernel: software IO TLB: mapped [mem 0x00000000973be000-0x000000009b3be000] (64MB)
[    1.889318] cachyos kernel: Trying to unpack rootfs image as initramfs...
[    1.889330] cachyos kernel: Initialise system trusted keyrings
[    1.889341] cachyos kernel: Key type blacklist registered
[    1.889353] cachyos kernel: workingset: timestamp_bits=36 max_order=22 bucket_order=0
[    1.889365] cachyos kernel: fuse: init (API version 7.45)
[    1.889376] cachyos kernel: integrity: Platform Keyring initialized
[    1.889388] cachyos kernel: integrity: Machine keyring initialized
[    1.889400] cachyos kernel: xor: automatically using best checksumming function   avx       
[    1.889411] cachyos kernel: Key type asymmetric registered
[    1.889423] cachyos kernel: Asymmetric key parser 'x509' registered
[    1.889434] cachyos kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    1.889446] cachyos kernel: io scheduler mq-deadline registered
[    1.889457] cachyos kernel: io scheduler kyber registered
[    1.889469] cachyos kernel: Adaptive Deadline I/O Scheduler 3.1.9 by Masahito Suzuki
[    1.889481] cachyos kernel: io scheduler adios registered
[    1.889492] cachyos kernel: io scheduler bfq registered
[    1.889504] cachyos kernel: ledtrig-cpu: registered to indicate activity on CPUs
[    1.889515] cachyos kernel: ACPI: AC: AC Adapter [ACAD] (off-line)
[    1.889527] cachyos kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C0D:00/input/input0
[    1.889539] cachyos kernel: ACPI: button: Lid Switch [LID0]
[    1.889551] cachyos kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[    1.889563] cachyos kernel: ACPI: button: Power Button [PWRB]
[    1.889575] cachyos kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[    1.889586] cachyos kernel: ACPI: button: Power Button [PWRF]
[    1.889599] cachyos kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20250807/psargs-332)
[    1.889612] cachyos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[    1.889625] cachyos kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20250807/psargs-332)
[    1.889636] cachyos kernel: ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[    1.889649] cachyos kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20250807/psargs-332)
[    1.889661] cachyos kernel: ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[    1.889673] cachyos kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20250807/psargs-332)
[    1.889685] cachyos kernel: ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[    1.889972] cachyos kernel: thermal LNXTHERM:02: registered as thermal_zone0
[    1.889991] cachyos kernel: ACPI: thermal: Thermal Zone [TZ02] (28 C)
[    1.890008] cachyos kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    1.890020] cachyos kernel: Non-volatile memory driver v1.3
[    1.890031] cachyos kernel: Linux agpgart interface v0.103
[    1.890043] cachyos kernel: ACPI: battery: Slot [BAT1] (battery present)
[    1.890054] cachyos kernel: Freeing initrd memory: 24004K
[    1.890320] cachyos kernel: ahci 0000:00:1f.2: AHCI vers 0001.0300, 32 command slots, 6 Gbps, SATA mode
[    1.890583] cachyos kernel: ahci 0000:00:1f.2: 1/2 ports implemented (port mask 0x1)
[    1.890909] cachyos kernel: ahci 0000:00:1f.2: flags: 64bit ncq pm led clo only pio slum part deso sadm sds apst 
[    1.891281] cachyos kernel: scsi host0: ahci
[    1.891564] cachyos kernel: scsi host1: ahci
[    1.891584] cachyos kernel: ata1: SATA max UDMA/133 abar m2048@0xd6224000 port 0xd6224100 irq 44 lpm-pol 3
[    1.891597] cachyos kernel: ata2: DUMMY
[    1.891609] cachyos kernel: ACPI: bus type drm_connector registered
[    1.891873] cachyos kernel: xhci_hcd 0000:00:14.0: can't derive routing for PCI INT A
[    1.892202] cachyos kernel: xhci_hcd 0000:00:14.0: PCI INT A: no GSI
[    1.892469] cachyos kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
[    1.892733] cachyos kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[    1.893038] cachyos kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x000000000004b810
[    1.893408] cachyos kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
[    1.893682] cachyos kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[    1.893949] cachyos kernel: ehci-pci 0000:00:1d.0: debug port 2
[    1.894336] cachyos kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
[    1.894615] cachyos kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[    1.894951] cachyos kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
[    1.895237] cachyos kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.19
[    1.895485] cachyos kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.895775] cachyos kernel: usb usb1: Product: xHCI Host Controller
[    1.895993] cachyos kernel: usb usb1: Manufacturer: Linux 6.19.9-2-cachyos xhci-hcd
[    1.896317] cachyos kernel: usb usb1: SerialNumber: 0000:00:14.0
[    1.896629] cachyos kernel: hub 1-0:1.0: USB hub found
[    1.897035] cachyos kernel: hub 1-0:1.0: 11 ports detected
[    1.897270] cachyos kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.19
[    1.897564] cachyos kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.897803] cachyos kernel: usb usb3: Product: xHCI Host Controller
[    1.898057] cachyos kernel: usb usb3: Manufacturer: Linux 6.19.9-2-cachyos xhci-hcd
[    1.898348] cachyos kernel: usb usb3: SerialNumber: 0000:00:14.0
[    1.898652] cachyos kernel: hub 3-0:1.0: USB hub found
[    1.899055] cachyos kernel: hub 3-0:1.0: 4 ports detected
[    1.899077] cachyos kernel: usbcore: registered new interface driver usbserial_generic
[    1.899090] cachyos kernel: usbserial: USB Serial support registered for generic
[    1.899102] cachyos kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[    1.899371] cachyos kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xd6225000
[    1.899740] cachyos kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[    1.899975] cachyos kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.19
[    1.900274] cachyos kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.900525] cachyos kernel: usb usb2: Product: EHCI Host Controller
[    1.900787] cachyos kernel: usb usb2: Manufacturer: Linux 6.19.9-2-cachyos ehci_hcd
[    1.901071] cachyos kernel: usb usb2: SerialNumber: 0000:00:1d.0
[    1.901391] cachyos kernel: hub 2-0:1.0: USB hub found
[    1.901758] cachyos kernel: hub 2-0:1.0: 2 ports detected
[    1.901779] cachyos kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
[    1.901792] cachyos kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
[    1.902061] cachyos kernel: rtc_cmos 00:01: RTC can wake from S4
[    1.902413] cachyos kernel: rtc_cmos 00:01: registered as rtc0
[    1.902668] cachyos kernel: rtc_cmos 00:01: setting system clock to 2026-03-27T11:58:50 UTC (1774612730)
[    1.902916] cachyos kernel: rtc_cmos 00:01: alarms up to one month, 242 bytes nvram
[    1.902933] cachyos kernel: intel_pstate: Intel P-state driver initializing
[    1.903214] cachyos kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
[    1.903233] cachyos kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
[    1.903245] cachyos kernel: fbcon: Deferring console take-over
[    1.903505] cachyos kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[    1.903523] cachyos kernel: hid: raw HID events driver (C) Jiri Kosina
[    1.903535] cachyos kernel: usbcore: registered new interface driver usbhid
[    1.903546] cachyos kernel: usbhid: USB HID core driver
[    1.903558] cachyos kernel: drop_monitor: Initializing network drop monitor service
[    1.903569] cachyos kernel: NET: Registered PF_INET6 protocol family
[    1.903581] cachyos kernel: Segment Routing with IPv6
[    1.903592] cachyos kernel: RPL Segment Routing with IPv6
[    1.903603] cachyos kernel: In-situ OAM (IOAM) with IPv6
[    1.903615] cachyos kernel: NET: Registered PF_PACKET protocol family
[    1.903627] cachyos kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    1.903639] cachyos kernel: microcode: Current revision: 0x0000002f
[    1.903650] cachyos kernel: IPI shorthand broadcast: enabled
[    1.903662] cachyos kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[    1.903674] cachyos kernel: sched_clock: Marking stable (767321168, 1577430)->(3185114007, -2416215409)
[    1.903686] cachyos kernel: registered taskstats version 1
[    1.903697] cachyos kernel: Loading compiled-in X.509 certificates
[    1.903710] cachyos kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 20342e1ea425e4b7dbe50e51e8d07a0c04e796ed'
[    1.903722] cachyos kernel: zswap: loaded using pool zstd
[    1.903733] cachyos kernel: Demotion targets for Node 0: null
[    1.903745] cachyos kernel: Key type .fscrypt registered
[    1.903756] cachyos kernel: Key type fscrypt-provisioning registered
[    1.903768] cachyos kernel: Btrfs loaded, zoned=yes, fsverity=yes
[    1.903780] cachyos kernel: Key type big_key registered
[    1.903791] cachyos kernel: integrity: Loading X.509 certificate: UEFI:db
[    1.903803] cachyos kernel: integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[    1.903815] cachyos kernel: integrity: Loading X.509 certificate: UEFI:db
[    1.903826] cachyos kernel: integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[    1.903838] cachyos kernel: integrity: Loading X.509 certificate: UEFI:db
[    1.903850] cachyos kernel: integrity: Loaded X.509 cert 'Hewlett-Packard Company: HP UEFI Secure Boot 2013 DB key: 1d7cf2c2b92673f69c8ee1ec7063967ab9b62bec'
[    1.903861] cachyos kernel: PM:   Magic number: 2:619:985
[    1.903873] cachyos kernel: RAS: Correctable Errors collector initialized.
[    1.904186] cachyos kernel: usb 1-3: new full-speed USB device number 2 using xhci_hcd
[    1.904491] cachyos kernel: usb 2-1: new high-speed USB device number 2 using ehci-pci
[    1.904511] cachyos kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.904524] cachyos kernel: ata1.00: Model 'Apacer AS340 240GB', rev 'V4.11', applying quirks: nolpm
[    1.904535] cachyos kernel: ata1.00: ATA-10: Apacer AS340 240GB, V4.11, max UDMA/133
[    1.904547] cachyos kernel: ata1.00: NCQ Send/Recv Log not supported
[    1.904559] cachyos kernel: ata1.00: 468862128 sectors, multi 0: LBA48 NCQ (depth 32), AA
[    1.904570] cachyos kernel: ata1.00: LPM support broken, forcing max_power
[    1.904582] cachyos kernel: ata1.00: NCQ Send/Recv Log not supported
[    1.904593] cachyos kernel: ata1.00: configured for UDMA/133
[    1.904902] cachyos kernel: scsi 0:0:0:0: Direct-Access     ATA      Apacer AS340 240 1    PQ: 0 ANSI: 5
[    1.905221] cachyos kernel: sd 0:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/224 GiB)
[    1.905520] cachyos kernel: sd 0:0:0:0: [sda] Write Protect is off
[    1.905816] cachyos kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.906125] cachyos kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.906447] cachyos kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[    1.906477] cachyos kernel:  sda: sda1 sda2
[    1.906881] cachyos kernel: sd 0:0:0:0: [sda] Attached SCSI disk
[    1.906902] cachyos kernel: clk: Disabling unused clocks
[    1.906914] cachyos kernel: PM: genpd: Disabling unused power domains
[    1.906926] cachyos kernel: Freeing unused decrypted memory: 2028K
[    1.906938] cachyos kernel: Freeing unused kernel image (initmem) memory: 4676K
[    1.906950] cachyos kernel: Write protecting the kernel read-only data: 38912k
[    1.906961] cachyos kernel: Freeing unused kernel image (text/rodata gap) memory: 444K
[    1.906973] cachyos kernel: Freeing unused kernel image (rodata/data gap) memory: 64K
[    1.907223] cachyos kernel: usb 1-3: New USB device found, idVendor=379a, idProduct=0cf0, bcdDevice= 2.02
[    1.907457] cachyos kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.907683] cachyos kernel: usb 1-3: Product: Quasar 3WL
[    1.907908] cachyos kernel: usb 1-3: Manufacturer: Compx
[    1.907926] cachyos kernel: input: Compx Quasar 3WL as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:379A:0CF0.0001/input/input5
[    1.908161] cachyos kernel: usb 2-1: New USB device found, idVendor=8087, idProduct=8001, bcdDevice= 0.03
[    1.908384] cachyos kernel: usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.908691] cachyos kernel: hub 2-1:1.0: USB hub found
[    1.908993] cachyos kernel: hub 2-1:1.0: 8 ports detected
[    1.909019] cachyos kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    1.909032] cachyos kernel: rodata_test: all tests were successful
[    1.909043] cachyos kernel: x86/mm: Checking user space page tables
[    1.909363] cachyos kernel: hid-generic 0003:379A:0CF0.0001: input,hidraw0: USB HID v1.11 Keyboard [Compx Quasar 3WL] on usb-0000:00:14.0-3/input0
[    1.909384] cachyos kernel: input: Compx Quasar 3WL as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:379A:0CF0.0002/input/input6
[    1.909396] cachyos kernel: input: Compx Quasar 3WL as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:379A:0CF0.0002/input/input7
[    1.909408] cachyos kernel: input: Compx Quasar 3WL Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:379A:0CF0.0002/input/input8
[    1.909420] cachyos kernel: input: Compx Quasar 3WL System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:379A:0CF0.0002/input/input9
[    1.909432] cachyos kernel: input: Compx Quasar 3WL as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:379A:0CF0.0002/input/input10
[    1.909742] cachyos kernel: hid-generic 0003:379A:0CF0.0002: input,hiddev96,hidraw1: USB HID v1.11 Device [Compx Quasar 3WL] on usb-0000:00:14.0-3/input1
[    1.909762] cachyos kernel: input: Compx Quasar 3WL as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.2/0003:379A:0CF0.0003/input/input11
[    1.910078] cachyos kernel: hid-generic 0003:379A:0CF0.0003: input,hidraw2: USB HID v1.11 Mouse [Compx Quasar 3WL] on usb-0000:00:14.0-3/input2
[    1.910097] cachyos kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    1.910109] cachyos kernel: Run /init as init process
[    1.910121] cachyos kernel:   with arguments:
[    1.910132] cachyos kernel:     /init
[    1.910144] cachyos kernel:     splash
[    1.910155] cachyos kernel:   with environment:
[    1.910167] cachyos kernel:     HOME=/
[    1.910178] cachyos kernel:     TERM=linux
[    1.910479] cachyos kernel: usb 1-4: new full-speed USB device number 3 using xhci_hcd
[    1.910501] cachyos systemd[1]: Successfully made /usr/ read-only.
[    1.910733] cachyos kernel: usb 1-4: New USB device found, idVendor=0bda, idProduct=b00a, bcdDevice= 1.10
[    1.910959] cachyos kernel: usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.911195] cachyos kernel: usb 1-4: Product: Bluetooth Radio 
[    1.911417] cachyos kernel: usb 1-4: Manufacturer: Realtek 
[    1.911638] cachyos kernel: usb 1-4: SerialNumber: 00e04c000001
[    1.911658] cachyos kernel: tsc: Refined TSC clocksource calibration: 1995.380 MHz
[    1.911670] cachyos kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x39864456686, max_idle_ns: 881590680204 ns
[    1.911682] cachyos kernel: clocksource: Switched to clocksource tsc
[    1.911974] cachyos kernel: usb 1-5: new high-speed USB device number 4 using xhci_hcd
[    1.911997] cachyos systemd[1]: systemd 260.1-1-arch running in system mode (+PAM +AUDIT -SELINUX +APPARMOR -IMA +IPE +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF +XKBCOMMON +UTMP +LIBARCHIVE)
[    1.912021] cachyos systemd[1]: Detected architecture x86-64.
[    1.912034] cachyos systemd[1]: Running in initrd.
[    1.912047] cachyos systemd[1]: Initializing machine ID from random generator.
[    1.912276] cachyos kernel: usb 1-5: New USB device found, idVendor=04f2, idProduct=b52d, bcdDevice=40.60
[    1.912500] cachyos kernel: usb 1-5: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[    1.912722] cachyos kernel: usb 1-5: Product: HP Webcam
[    1.912943] cachyos kernel: usb 1-5: Manufacturer: Chicony Electronics Co.,Ltd.
[    1.913181] cachyos kernel: usb 1-5: SerialNumber: 0x0001
[    1.913202] cachyos systemd[1]: Queued start job for default target Initrd Default Target.
[    1.913217] cachyos systemd[1]: Expecting device /dev/disk/by-uuid/450aafdc-613a-4cf9-bdbb-eb338b606697...
[    1.913229] cachyos systemd[1]: Reached target Path Units.
[    1.913242] cachyos systemd[1]: Reached target Slice Units.
[    1.913254] cachyos systemd[1]: Reached target Swaps.
[    1.913267] cachyos systemd[1]: Reached target Timer Units.
[    1.913279] cachyos systemd[1]: Listening on Journal Socket (/dev/log).
[    1.913292] cachyos systemd[1]: Listening on Journal Sockets.
[    1.913304] cachyos systemd[1]: Listening on udev Control Socket.
[    1.913318] cachyos systemd[1]: Listening on udev Kernel Socket.
[    1.913330] cachyos systemd[1]: Reached target Socket Units.
[    1.913343] cachyos systemd[1]: Create List of Static Device Nodes skipped, unmet condition check ConditionFileNotEmpty=/lib/modules/6.19.9-2-cachyos/modules.devname
[    1.913356] cachyos systemd[1]: Starting Journal Service...
[    1.913368] cachyos systemd[1]: Starting Load Kernel Modules...
[    1.913381] cachyos systemd[1]: TPM PCR Barrier (initrd) skipped, unmet condition check ConditionSecurity=measured-uki
[    1.913394] cachyos systemd[1]: Starting Create Static Device Nodes in /dev...
[    1.913406] cachyos systemd[1]: Starting Coldplug All udev Devices...
[    1.913418] cachyos systemd[1]: Starting Virtual Console Setup...
[    1.913431] cachyos systemd[1]: Finished Load Kernel Modules.
[    1.913475] cachyos systemd-journald[137]: Collecting audit messages is disabled.
[    1.913509] cachyos systemd[1]: Finished Create Static Device Nodes in /dev.
[    1.913522] cachyos systemd[1]: Starting Rule-based Manager for Device Events and Files...
[    1.913534] cachyos systemd[1]: Finished Virtual Console Setup.
[    1.913547] cachyos systemd[1]: Started Rule-based Manager for Device Events and Files.
[    1.914401] cachyos systemd[1]: Started Journal Service.
[    2.401028] cachyos kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: 8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances
[    2.401555] cachyos kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances
[    2.401995] cachyos kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances
[    2.403991] cachyos kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: DF4E63B6-3BBC-4858-9737-C74F82F821F3 has zero instances
[    2.426032] cachyos kernel: ACPI: watchdog: Skipping WDAT on this system because it uses RTC SRAM
[    2.431339] cachyos kernel: PM: Image not found (code -22)
[    2.478031] cachyos kernel: BTRFS: device fsid 450aafdc-613a-4cf9-bdbb-eb338b606697 devid 1 transid 31449 /dev/sda2 (8:2) scanned by mount (208)
[    2.478107] cachyos kernel: BTRFS info (device sda2): first mount of filesystem 450aafdc-613a-4cf9-bdbb-eb338b606697
[    2.478152] cachyos kernel: BTRFS info (device sda2): using crc32c (crc32c-lib) checksum algorithm
[    2.509026] cachyos kernel: BTRFS info (device sda2): enabling ssd optimizations
[    2.509100] cachyos kernel: BTRFS info (device sda2): turning on async discard
[    2.509135] cachyos kernel: BTRFS info (device sda2): enabling free space tree
[    3.607029] cachyos kernel: i915 0000:00:02.0: [drm] Found broadwell/ult (device ID 1616) integrated display version 8.00 stepping N/A
[    3.629030] cachyos kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
[    3.633024] cachyos kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    3.683058] cachyos kernel: i915 0000:00:02.0: [drm] Registered 3 planes with drm panic
[    3.692073] cachyos kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1
[    3.694053] cachyos kernel: ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    3.697036] cachyos kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
[    4.056100] cachyos kernel: fbcon: i915drmfb (fb0) is primary device
[    4.056222] cachyos kernel: fbcon: Deferring console take-over
[    4.056289] cachyos kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[    5.989100] cachyos-x8664 systemd-journald[137]: Received SIGTERM from PID 1 (systemd).
[    5.989358] cachyos-x8664 systemd[1]: systemd 260.1-1-arch running in system mode (+PAM +AUDIT -SELINUX +APPARMOR -IMA +IPE +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF +XKBCOMMON +UTMP +LIBARCHIVE)
[    5.989403] cachyos-x8664 systemd[1]: Detected architecture x86-64.
[    5.989434] cachyos-x8664 systemd[1]: Hostname set to <cachyos-x8664>.
[    5.989462] cachyos-x8664 systemd[1]: bpf-restrict-fs: LSM BPF program attached
[    5.989491] cachyos-x8664 kernel: zram: Added device: zram0
[    5.989527] cachyos-x8664 systemd[1]: /usr/lib/systemd/system/ananicy-cpp.service:16: Support for option CPUAccounting= has been removed and it is ignored
[    5.989558] cachyos-x8664 systemd[1]: initrd-switch-root.service: Deactivated successfully.
[    5.989588] cachyos-x8664 systemd[1]: Stopped Switch Root.
[    5.989617] cachyos-x8664 systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
[    5.989646] cachyos-x8664 systemd[1]: Created slice Slice /system/dirmngr.
[    5.989684] cachyos-x8664 systemd[1]: Created slice Slice /system/getty.
[    5.989723] cachyos-x8664 systemd[1]: Created slice Slice /system/gpg-agent.
[    5.989753] cachyos-x8664 systemd[1]: Created slice Slice /system/gpg-agent-browser.
[    5.989785] cachyos-x8664 systemd[1]: Created slice Slice /system/gpg-agent-extra.
[    5.989814] cachyos-x8664 systemd[1]: Created slice Slice /system/gpg-agent-ssh.
[    5.989844] cachyos-x8664 systemd[1]: Created slice Slice /system/keyboxd.
[    5.989873] cachyos-x8664 systemd[1]: Created slice Slice /system/modprobe.
[    5.989901] cachyos-x8664 systemd[1]: Created slice Slice /system/systemd-fsck.
[    5.989931] cachyos-x8664 systemd[1]: Created slice Slice /system/systemd-zram-setup.
[    5.989961] cachyos-x8664 systemd[1]: Created slice User and Session Slice.
[    5.989991] cachyos-x8664 systemd[1]: Dispatch Password Requests to Console Directory Watch skipped, unmet condition check ConditionPathExists=!/run/plymouth/pid
[    5.990737] cachyos-x8664 systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    5.990775] cachyos-x8664 systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    5.990805] cachyos-x8664 systemd[1]: Expecting device /dev/disk/by-uuid/450aafdc-613a-4cf9-bdbb-eb338b606697...
[    5.990833] cachyos-x8664 systemd[1]: Expecting device /dev/disk/by-uuid/BB97-8FDF...
[    5.990861] cachyos-x8664 systemd[1]: Expecting device /dev/zram0...
[    5.990890] cachyos-x8664 systemd[1]: Reached target Local Encrypted Volumes.
[    5.990919] cachyos-x8664 systemd[1]: Reached target Login Prompts.
[    5.990948] cachyos-x8664 systemd[1]: Reached target Image Downloads.
[    5.990975] cachyos-x8664 systemd[1]: Stopped target Switch Root.
[    5.991009] cachyos-x8664 systemd[1]: Stopped target Initrd File Systems.
[    5.991396] cachyos-x8664 systemd[1]: Stopped target Initrd Root File System.
[    5.991436] cachyos-x8664 systemd[1]: Reached target Local Integrity Protected Volumes.
[    5.991465] cachyos-x8664 systemd[1]: Reached target Remote File Systems.
[    5.991503] cachyos-x8664 systemd[1]: Reached target Slice Units.
[    5.991532] cachyos-x8664 systemd[1]: Reached target Local Verity Protected Volumes.
[    5.991560] cachyos-x8664 systemd[1]: Listening on Device-mapper event daemon FIFOs.
[    5.991589] cachyos-x8664 systemd[1]: Listening on LVM2 poll daemon socket.
[    5.991619] cachyos-x8664 systemd[1]: Listening on Query the User Interactively for a Password.
[    5.991651] cachyos-x8664 systemd[1]: Listening on Process Core Dump Socket.
[    5.992049] cachyos-x8664 systemd[1]: Listening on Credential Encryption/Decryption.
[    5.992085] cachyos-x8664 systemd[1]: Listening on Factory Reset Management.
[    5.992113] cachyos-x8664 systemd[1]: Listening on Console Output Muting Service Socket.
[    5.992140] cachyos-x8664 systemd[1]: TPM PCR Measurements skipped, unmet condition check ConditionSecurity=measured-uki
[    5.992177] cachyos-x8664 systemd[1]: Make TPM PCR Policy skipped, unmet condition check ConditionSecurity=measured-uki
[    5.992213] cachyos-x8664 systemd[1]: Listening on Disk Repartitioning Service Socket.
[    5.992245] cachyos-x8664 systemd[1]: Listening on Resolve Monitor Varlink Socket.
[    5.992273] cachyos-x8664 systemd[1]: Listening on Resolve Service Varlink Socket.
[    5.992300] cachyos-x8664 systemd[1]: Listening on udev Control Socket.
[    5.992329] cachyos-x8664 systemd[1]: Listening on udev Varlink Socket.
[    5.992355] cachyos-x8664 systemd[1]: Listening on User Database Manager Socket.
[    5.992381] cachyos-x8664 systemd[1]: Mounting Huge Pages File System...
[    5.992407] cachyos-x8664 systemd[1]: Mounting POSIX Message Queue File System...
[    5.992434] cachyos-x8664 systemd[1]: Mounting Kernel Debug File System...
[    5.992460] cachyos-x8664 systemd[1]: Mounting Kernel Trace File System...
[    5.992486] cachyos-x8664 systemd[1]: Starting Create List of Static Device Nodes...
[    5.992513] cachyos-x8664 systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
[    5.992540] cachyos-x8664 systemd[1]: Load Kernel Module configfs skipped, unmet condition check ConditionKernelModuleLoaded=!configfs
[    5.992566] cachyos-x8664 systemd[1]: Mounting Kernel Configuration File System...
[    5.992593] cachyos-x8664 systemd[1]: Load Kernel Module drm skipped, unmet condition check ConditionKernelModuleLoaded=!drm
[    5.992621] cachyos-x8664 systemd[1]: Load Kernel Module fuse skipped, unmet condition check ConditionKernelModuleLoaded=!fuse
[    5.993344] cachyos-x8664 systemd[1]: Mounting FUSE Control File System...
[    5.993380] cachyos-x8664 systemd[1]: plymouth-switch-root.service: Deactivated successfully.
[    5.993410] cachyos-x8664 systemd[1]: Stopped Plymouth switch root service.
[    5.993440] cachyos-x8664 systemd[1]: Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
[    5.993469] cachyos-x8664 systemd[1]: Starting Journal Service...
[    5.993498] cachyos-x8664 systemd[1]: Starting Load Kernel Modules...
[    5.993526] cachyos-x8664 systemd[1]: TPM PCR Machine ID Measurement skipped, unmet condition check ConditionSecurity=measured-uki
[    5.993554] cachyos-x8664 systemd[1]: TPM NvPCR Product ID Measurement skipped, unmet condition check ConditionSecurity=measured-uki
[    5.993583] cachyos-x8664 systemd[1]: Starting Remount Root and Kernel File Systems...
[    5.993612] cachyos-x8664 systemd[1]: Early TPM SRK Setup skipped, unmet condition check ConditionSecurity=measured-uki
[    5.993644] cachyos-x8664 systemd[1]: Starting Load udev Rules from Credentials...
[    5.993675] cachyos-x8664 systemd[1]: Starting Coldplug All udev Devices...
[    5.993706] cachyos-x8664 systemd[1]: Mounted Huge Pages File System.
[    5.993735] cachyos-x8664 systemd[1]: Mounted POSIX Message Queue File System.
[    5.993766] cachyos-x8664 systemd[1]: Mounted Kernel Debug File System.
[    5.993795] cachyos-x8664 systemd[1]: Mounted Kernel Trace File System.
[    5.993825] cachyos-x8664 systemd[1]: Finished Create List of Static Device Nodes.
[    5.993856] cachyos-x8664 systemd[1]: Mounted Kernel Configuration File System.
[    5.993886] cachyos-x8664 systemd[1]: Mounted FUSE Control File System.
[    5.993916] cachyos-x8664 systemd[1]: Starting Create Static Device Nodes in /dev gracefully...
[    5.994067] cachyos-x8664 systemd-journald[425]: Collecting audit messages is disabled.
[    5.994147] cachyos-x8664 systemd[1]: Finished Load udev Rules from Credentials.
[    5.994178] cachyos-x8664 kernel: Asymmetric key parser 'pkcs8' registered
[    5.995655] cachyos-x8664 systemd[1]: Started Journal Service.
[    6.010296] cachyos-x8664 kernel: i2c_dev: i2c /dev entries driver
[    6.046024] cachyos-x8664 kernel: device-mapper: uevent: version 1.0.3
[    6.047075] cachyos-x8664 kernel: device-mapper: ioctl: 4.50.0-ioctl (2025-04-28) initialised: dm-devel@lists.linux.dev
[    6.061031] cachyos-x8664 kernel: BTRFS info (device sda2 state M): use zstd compression, level 3
[    7.396021] cachyos-x8664 kernel: zram0: detected capacity change from 0 to 24301568
[    7.760024] cachyos-x8664 kernel: Adding 12150780k swap on /dev/zram0.  Priority:100 extents:1 across:12150780k SSDsc
[    7.978022] cachyos-x8664 kernel: mousedev: PS/2 mouse device common for all mice
[    8.021403] cachyos-x8664 kernel: input: Wireless hotkeys as /devices/virtual/input/input13
[    8.084018] cachyos-x8664 kernel: Adding 14680060k swap on /swap/swapfile.  Priority:-1 extents:246 across:34819056k SS
[    8.175466] cachyos-x8664 systemd-journald[425]: Received client request to flush runtime journal.
[    8.341117] cachyos-x8664 kernel: mc: Linux media interface: v0.10
[    8.413076] cachyos-x8664 kernel: videodev: Linux video capture interface: v2.00
[    8.443022] cachyos-x8664 kernel: input: PC Speaker as /devices/platform/pcspkr/input/input14
[    8.576039] cachyos-x8664 kernel: Bluetooth: Core ver 2.22
[    8.576150] cachyos-x8664 kernel: NET: Registered PF_BLUETOOTH protocol family
[    8.576225] cachyos-x8664 kernel: Bluetooth: HCI device and connection manager initialized
[    8.576293] cachyos-x8664 kernel: Bluetooth: HCI socket layer initialized
[    8.576342] cachyos-x8664 kernel: Bluetooth: L2CAP socket layer initialized
[    8.576404] cachyos-x8664 kernel: Bluetooth: SCO socket layer initialized
[    8.580020] cachyos-x8664 kernel: i801_smbus 0000:00:1f.3: SPD Write Disable is set
[    8.580739] cachyos-x8664 kernel: i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
[    8.581339] cachyos-x8664 kernel: ACPI: watchdog: Skipping WDAT on this system because it uses RTC SRAM
[    8.585023] cachyos-x8664 kernel: i2c i2c-6: Successfully instantiated SPD at 0x50
[    8.751025] cachyos-x8664 kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    8.756026] cachyos-x8664 kernel: intel_rapl_common: Found RAPL domain package
[    8.756144] cachyos-x8664 kernel: intel_rapl_common: Found RAPL domain core
[    8.756223] cachyos-x8664 kernel: intel_rapl_common: Found RAPL domain uncore
[    8.756283] cachyos-x8664 kernel: intel_rapl_common: Found RAPL domain dram
[    8.756342] cachyos-x8664 kernel: intel_rapl_common: package-0:package:long_term locked by BIOS
[    8.756388] cachyos-x8664 kernel: intel_rapl_common: package-0:package:short_term locked by BIOS
[    8.761023] cachyos-x8664 kernel: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    8.761126] cachyos-x8664 kernel: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    8.762017] cachyos-x8664 kernel: spi-nor spi0.0: supply vcc not found, using dummy regulator
[    8.771020] cachyos-x8664 kernel: Creating 1 MTD partitions on "intel-spi":
[    8.771132] cachyos-x8664 kernel: 0x000000000000-0x000000800000 : "BIOS"
[    8.913021] cachyos-x8664 kernel: at24 6-0050: supply vcc not found, using dummy regulator
[    8.916576] cachyos-x8664 kernel: at24 6-0050: 256 byte spd EEPROM, read-only
[    8.918018] cachyos-x8664 kernel: [drm] radeon kernel modesetting enabled.
[    8.941123] cachyos-x8664 kernel: r8169 0000:07:00.0: can't disable ASPM; OS doesn't have ASPM control
[    8.963021] cachyos-x8664 kernel: RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer
[    8.963133] cachyos-x8664 kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[    8.963195] cachyos-x8664 kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
[    8.963231] cachyos-x8664 kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules
[    8.963276] cachyos-x8664 kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[    8.993036] cachyos-x8664 kernel: r8169 0000:07:00.0 eth0: RTL8106e, c8:d3:ff:1d:3a:1a, XID 449, IRQ 52
[    9.011017] cachyos-x8664 kernel: uvcvideo 1-5:1.0: Found UVC 1.00 device HP Webcam (04f2:b52d)
[    9.027113] cachyos-x8664 kernel: usbcore: registered new interface driver uvcvideo
[    9.035023] cachyos-x8664 kernel: r8169 0000:07:00.0 enp7s0: renamed from eth0
[    9.199059] cachyos-x8664 kernel: psmouse serio1: synaptics: queried max coordinates: x [..5652], y [..4846]
[    9.225036] cachyos-x8664 kernel: usbcore: registered new interface driver btusb
[    9.228403] cachyos-x8664 kernel: Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
[    9.228480] cachyos-x8664 kernel: snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [i915])
[    9.230036] cachyos-x8664 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
[    9.230102] cachyos-x8664 kernel: psmouse serio1: synaptics: queried min coordinates: x [1330..], y [1094..]
[    9.230653] cachyos-x8664 kernel: psmouse serio1: synaptics: Trying to set up SMBus access
[    9.231837] cachyos-x8664 kernel: Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[    9.231916] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
[    9.236030] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
[    9.236720] cachyos-x8664 kernel: Bluetooth: hci0: RTL: cfg_sz 10, total sz 34926
[    9.279066] cachyos-x8664 kernel: rtw_core: loading out-of-tree module taints kernel.
[    9.279148] cachyos-x8664 kernel: rtw_core: module verification failed: signature and/or required key missing - tainting kernel
[    9.328068] cachyos-x8664 kernel: input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input17
[    9.328176] cachyos-x8664 kernel: input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input18
[    9.328217] cachyos-x8664 kernel: input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input19
[    9.382032] cachyos-x8664 kernel: input: HP WMI hotkeys as /devices/virtual/input/input16
[    9.403029] cachyos-x8664 kernel: rmi4_smbus 6-002c: registering SMbus-connected sensor
[    9.622023] cachyos-x8664 kernel: rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: TM3127-001, fw id: 1819280
[    9.646201] cachyos-x8664 kernel: snd_hda_codec_alc269 hdaudioC1D0: ALC3227: picked fixup  (pin match)
[    9.649061] cachyos-x8664 kernel: snd_hda_codec_alc269 hdaudioC1D0: autoconfig for ALC3227: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[    9.650952] cachyos-x8664 kernel: snd_hda_codec_alc269 hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    9.651481] cachyos-x8664 kernel: snd_hda_codec_alc269 hdaudioC1D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[    9.651934] cachyos-x8664 kernel: snd_hda_codec_alc269 hdaudioC1D0:    mono: mono_out=0x0
[    9.654542] cachyos-x8664 kernel: snd_hda_codec_alc269 hdaudioC1D0:    inputs:
[    9.655019] cachyos-x8664 kernel: snd_hda_codec_alc269 hdaudioC1D0:      Internal Mic=0x12
[    9.655465] cachyos-x8664 kernel: snd_hda_codec_alc269 hdaudioC1D0:      Mic=0x19
[    9.702071] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: Firmware version 24.11.0, H2C version 12
[    9.704036] cachyos-x8664 kernel: Bluetooth: hci0: RTL: fw version 0x75b8f098
[    9.710039] cachyos-x8664 kernel: input: Synaptics TM3127-001 as /devices/pci0000:00/0000:00:1f.3/i2c-6/6-002c/rmi4-00/input/input20
[    9.710249] cachyos-x8664 kernel: input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input21
[    9.711032] cachyos-x8664 kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card1/input22
[   18.494347] cachyos-x8664 kernel: amdgpu: Virtual CRAT table created for CPU
[   18.494422] cachyos-x8664 kernel: amdgpu: Topology: Add CPU node
[   18.515143] cachyos-x8664 kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (20250807/dsopcode-133)
[   18.515258] cachyos-x8664 kernel: ACPI Error: Aborting method \_SB.WMID.WQBD due to previous error (AE_AML_OPERAND_VALUE) (20250807/psparse-531)
[   18.520029] cachyos-x8664 kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (20250807/dsopcode-133)
[   18.520099] cachyos-x8664 kernel: ACPI Error: Aborting method \_SB.WMID.WQBC due to previous error (AE_AML_OPERAND_VALUE) (20250807/psparse-531)
[   18.521028] cachyos-x8664 kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (20250807/dsopcode-133)
[   18.521121] cachyos-x8664 kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous error (AE_AML_OPERAND_VALUE) (20250807/psparse-531)
[   18.726075] cachyos-x8664 kernel: hp_bioscfg: Returned error 0x3, "Invalid command value/Feature not supported"
[   18.812167] cachyos-x8664 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   18.812210] cachyos-x8664 kernel: Bluetooth: BNEP filters: protocol multicast
[   18.812255] cachyos-x8664 kernel: Bluetooth: BNEP socket layer initialized
[   18.814907] cachyos-x8664 kernel: Bluetooth: MGMT ver 1.23
[   18.830027] cachyos-x8664 kernel: NET: Registered PF_ALG protocol family
[   19.216225] cachyos-x8664 kernel: RTL8208 Fast Ethernet r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
[   19.482069] cachyos-x8664 kernel: r8169 0000:07:00.0 enp7s0: Link is Down
[   24.124027] cachyos-x8664 kernel: wlan0: authenticate with 6c:68:a4:1c:97:5b (local address=8c:c8:4b:68:d1:63)
[   24.166037] cachyos-x8664 kernel: wlan0: send auth to 6c:68:a4:1c:97:5b (try 1/3)
[   24.166113] cachyos-x8664 kernel: wlan0: authenticated
[   24.166196] cachyos-x8664 kernel: wlan0: associate with 6c:68:a4:1c:97:5b (try 1/3)
[   24.168146] cachyos-x8664 kernel: wlan0: RX AssocResp from 6c:68:a4:1c:97:5b (capab=0x431 status=0 aid=2)
[   24.168191] cachyos-x8664 kernel: wlan0: associated
[   24.171037] cachyos-x8664 kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 6c:68:a4:1c:97:5b
[   24.423013] cachyos-x8664 kernel: warning: `tokio-runtime-w' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[   25.273027] cachyos-x8664 kernel: Bluetooth: RFCOMM TTY layer initialized
[   25.273101] cachyos-x8664 kernel: Bluetooth: RFCOMM socket layer initialized
[   25.273137] cachyos-x8664 kernel: Bluetooth: RFCOMM ver 1.11
[   26.401041] cachyos-x8664 kernel: uvcvideo 1-5:1.0: UVC non compliance: permanently disabling control 9a090c (Focus, Automatic Continuous), due to error -5
[   30.551183] cachyos-x8664 rtw88-boot-hook: saved to /home/pc/Загрузки/test/logs/boot_dmesg_20260327_135915.txt
[   39.040240] cachyos-x8664 kernel: input: Soundcore Q10i (AVRCP) as /devices/virtual/input/input23
[  174.366025] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (9)
[  174.366603] cachyos-x8664 kernel: 00000000: 9d9c5ec7 dc4d6991 09c267b0 00003384  .^...iM..g...3..
[  174.366637] cachyos-x8664 kernel: 00000010: 3ffe1e00 08f0f2cf 00002901 012a1100  ...?.....)....*.
[  174.366684] cachyos-x8664 kernel: 00000020: 0000000e 20000000 000000dc 0000000f  ....... ........
[  174.366737] cachyos-x8664 kernel: 00000030: 0000001a 00000000                    ........
[  174.366766] cachyos-x8664 kernel: 00000000: c7 5e 9c 9d 91 69 4d dc b0 67 c2 09 84 33 00 00  .^...iM..g...3..
[  174.366789] cachyos-x8664 kernel: 00000010: 00 1e fe 3f cf f2 f0 08 01 29 00 00 00 11 2a 01  ...?.....)....*.
[  174.366815] cachyos-x8664 kernel: 00000020: 0e 00 00 00 00 00 00 20                          ....... 
[ 1237.142511] cachyos-x8664 kernel: wlan0: deauthenticating from 6c:68:a4:1c:97:5b by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1237.696020] cachyos-x8664 kernel: PM: hibernation: hibernation entry
[ 1237.722052] cachyos-x8664 kernel: Filesystems sync: 0.020 seconds
[ 1249.633975] cachyos-x8664 kernel: Freezing user space processes
[ 1249.635145] cachyos-x8664 kernel: Freezing user space processes completed (elapsed 0.000 seconds)
[ 1249.635227] cachyos-x8664 kernel: OOM killer disabled.
[ 1249.635286] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
[ 1249.635348] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00058000-0x00058fff]
[ 1249.635393] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00086000-0x000fffff]
[ 1249.635438] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x8d2fa000-0x8d303fff]
[ 1249.635477] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x9b88e000-0x9cffdfff]
[ 1249.635538] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x9cfff000-0xffffffff]
[ 1249.635578] cachyos-x8664 kernel: PM: hibernation: Basic memory bitmaps created
[ 1249.635648] cachyos-x8664 kernel: PM: hibernation: Preallocating image memory
[ 1249.635687] cachyos-x8664 kernel: PM: hibernation: Allocated 315876 pages for snapshot
[ 1249.635734] cachyos-x8664 kernel: PM: hibernation: Allocated 1263504 kbytes in 10.41 seconds (121.37 MB/s)
[ 1249.635784] cachyos-x8664 kernel: Freezing remaining freezable tasks
[ 1249.635830] cachyos-x8664 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[ 1249.635864] cachyos-x8664 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
[ 1249.635923] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[ 1249.636119] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN04._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[ 1249.636171] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[ 1249.636208] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN03._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[ 1249.636253] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[ 1249.636300] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN02._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[ 1249.636340] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[ 1249.636408] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN01._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[ 1249.636450] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[ 1249.636483] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN00._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[ 1249.636530] cachyos-x8664 kernel: ACPI: EC: interrupt blocked
[ 1249.636571] cachyos-x8664 kernel: ACPI: PM: Preparing to enter system sleep state S4
[ 1249.636611] cachyos-x8664 kernel: ACPI: EC: event blocked
[ 1249.636643] cachyos-x8664 kernel: ACPI: EC: EC stopped
[ 1249.636681] cachyos-x8664 kernel: ACPI: PM: Saving platform NVS memory
[ 1249.636714] cachyos-x8664 kernel: Disabling non-boot CPUs ...
[ 1249.636760] cachyos-x8664 kernel: smpboot: CPU 3 is now offline
[ 1249.636799] cachyos-x8664 kernel: smpboot: CPU 2 is now offline
[ 1249.636849] cachyos-x8664 kernel: smpboot: CPU 1 is now offline
[ 1249.636883] cachyos-x8664 kernel: PM: hibernation: Normal pages needed: 315427 + 1024, available pages: 2806985
[ 1249.636915] cachyos-x8664 kernel: ACPI: PM: Restoring platform NVS memory
[ 1249.636954] cachyos-x8664 kernel: ACPI: EC: EC started
[ 1249.637008] cachyos-x8664 kernel: Enabling non-boot CPUs ...
[ 1249.637042] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 1249.637084] cachyos-x8664 kernel: CPU1 is up
[ 1249.637142] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
[ 1249.637174] cachyos-x8664 kernel: CPU2 is up
[ 1249.637205] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 1249.637237] cachyos-x8664 kernel: CPU3 is up
[ 1249.637275] cachyos-x8664 kernel: ACPI: PM: Waking up from system sleep state S4
[ 1249.637307] cachyos-x8664 kernel: ACPI: EC: interrupt unblocked
[ 1249.637345] cachyos-x8664 kernel: ACPI: EC: event unblocked
[ 1249.637390] cachyos-x8664 kernel: usb usb1: root hub lost power or was reset
[ 1249.646542] cachyos-x8664 kernel: usb usb3: root hub lost power or was reset
[ 1249.652327] cachyos-x8664 kernel: usb usb2: root hub lost power or was reset
[ 1249.653391] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[ 1249.653438] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN00._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[ 1249.653475] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: Error updating fan power state
[ 1249.654234] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: dpm_run_callback(): platform_pm_restore returns -19
[ 1249.654845] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: failed to restore: error -19
[ 1249.655357] cachyos-x8664 kernel: usb 1-5: reset high-speed USB device number 4 using xhci_hcd
[ 1249.659392] cachyos-x8664 kernel: usb 2-1: reset high-speed USB device number 2 using ehci-pci
[ 1249.663267] cachyos-x8664 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1249.663318] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[ 1249.663386] cachyos-x8664 kernel: sd 0:0:0:0: [sda] Starting disk
[ 1249.664101] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[ 1249.664149] cachyos-x8664 kernel: ata1.00: configured for UDMA/133
[ 1249.664191] cachyos-x8664 kernel: usb 1-4: WARN: invalid context state for evaluate context command.
[ 1249.666392] cachyos-x8664 kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[ 1249.667045] cachyos-x8664 kernel: usb 1-3: WARN: invalid context state for evaluate context command.
[ 1249.667837] cachyos-x8664 kernel: usb 1-3: reset full-speed USB device number 2 using xhci_hcd
[ 1249.668679] cachyos-x8664 kernel: PM: hibernation: Basic memory bitmaps freed
[ 1249.668725] cachyos-x8664 kernel: OOM killer enabled.
[ 1249.668760] cachyos-x8664 kernel: Restarting tasks: Starting
[ 1249.668795] cachyos-x8664 kernel: Restarting tasks: Done
[ 1249.668830] cachyos-x8664 kernel: efivarfs: resyncing variable state
[ 1249.668873] cachyos-x8664 kernel: efivarfs: removing variable HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
[ 1249.668908] cachyos-x8664 kernel: Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
[ 1249.668941] cachyos-x8664 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 1249.668985] cachyos-x8664 kernel: Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[ 1249.669030] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
[ 1249.669080] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
[ 1249.669115] cachyos-x8664 kernel: Bluetooth: hci0: RTL: cfg_sz 10, total sz 34926
[ 1249.780056] cachyos-x8664 kernel: efivarfs: finished resyncing variable state
[ 1249.783589] cachyos-x8664 kernel: PM: hibernation: hibernation exit
[ 1249.955085] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[ 1249.956196] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[ 1249.956947] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[ 1249.957339] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[ 1249.957627] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[ 1249.957896] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[ 1249.958172] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[ 1249.958438] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[ 1250.121088] cachyos-x8664 kernel: Bluetooth: hci0: RTL: fw version 0x75b8f098
[ 1250.189031] cachyos-x8664 kernel: Bluetooth: MGMT ver 1.23
[ 1254.909027] cachyos-x8664 rtw88-nss0-hook: resume log saved to /home/pc/Загрузки/test/logs/resume_dmesg_20260327_143023.txt
[ 1254.996440] cachyos-x8664 kernel: RTL8208 Fast Ethernet r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
[ 1255.348214] cachyos-x8664 kernel: r8169 0000:07:00.0 enp7s0: Link is Down
[ 1258.039047] cachyos-x8664 kernel: input: Soundcore Q10i (AVRCP) as /devices/virtual/input/input24
[ 1260.124195] cachyos-x8664 kernel: wlan0: authenticate with 6c:68:a4:1c:97:5b (local address=8c:c8:4b:68:d1:63)
[ 1260.166194] cachyos-x8664 kernel: wlan0: send auth to 6c:68:a4:1c:97:5b (try 1/3)
[ 1260.166240] cachyos-x8664 kernel: wlan0: authenticated
[ 1260.166288] cachyos-x8664 kernel: wlan0: associate with 6c:68:a4:1c:97:5b (try 1/3)
[ 1260.168030] cachyos-x8664 kernel: wlan0: RX AssocResp from 6c:68:a4:1c:97:5b (capab=0x431 status=0 aid=2)
[ 1260.168105] cachyos-x8664 kernel: wlan0: associated
[ 1260.259054] cachyos-x8664 kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 6c:68:a4:1c:97:5b
[ 7577.672038] cachyos-x8664 kernel: Bluetooth: hci0: unexpected event for opcode 0xfc19
[ 7586.032050] cachyos-x8664 kernel: input: Soundcore Q10i (AVRCP) as /devices/virtual/input/input25
[ 7894.357062] cachyos-x8664 kernel: wlan0: deauthenticating from 6c:68:a4:1c:97:5b by local choice (Reason: 3=DEAUTH_LEAVING)
[ 7895.708257] cachyos-x8664 kernel: PM: suspend entry (deep)
[ 7895.812039] cachyos-x8664 kernel: Filesystems sync: 0.103 seconds
[ 7897.290588] cachyos-x8664 kernel: Freezing user space processes
[ 7897.294749] cachyos-x8664 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
[ 7897.298891] cachyos-x8664 kernel: OOM killer disabled.
[ 7897.298958] cachyos-x8664 kernel: Freezing remaining freezable tasks
[ 7897.299724] cachyos-x8664 kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
[ 7897.299823] cachyos-x8664 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
[ 7897.299881] cachyos-x8664 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 7897.300991] cachyos-x8664 kernel: ata1.00: Entering standby power mode
[ 7897.301241] cachyos-x8664 kernel: ACPI: EC: interrupt blocked
[ 7897.301329] cachyos-x8664 kernel: ACPI: PM: Preparing to enter system sleep state S3
[ 7897.301418] cachyos-x8664 kernel: ACPI: EC: event blocked
[ 7897.301470] cachyos-x8664 kernel: ACPI: EC: EC stopped
[ 7897.301501] cachyos-x8664 kernel: ACPI: PM: Saving platform NVS memory
[ 7897.301541] cachyos-x8664 kernel: Disabling non-boot CPUs ...
[ 7897.301580] cachyos-x8664 kernel: smpboot: CPU 3 is now offline
[ 7897.301619] cachyos-x8664 kernel: smpboot: CPU 2 is now offline
[ 7897.301650] cachyos-x8664 kernel: smpboot: CPU 1 is now offline
[ 7897.301713] cachyos-x8664 kernel: ACPI: PM: Low-level resume complete
[ 7897.301848] cachyos-x8664 kernel: ACPI: EC: EC started
[ 7897.301914] cachyos-x8664 kernel: ACPI: PM: Restoring platform NVS memory
[ 7897.301979] cachyos-x8664 kernel: Enabling non-boot CPUs ...
[ 7897.302051] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 7897.302120] cachyos-x8664 kernel: CPU1 is up
[ 7897.302266] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
[ 7897.302386] cachyos-x8664 kernel: CPU2 is up
[ 7897.302442] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 7897.302527] cachyos-x8664 kernel: CPU3 is up
[ 7897.302582] cachyos-x8664 kernel: ACPI: PM: Waking up from system sleep state S3
[ 7897.302651] cachyos-x8664 kernel: ACPI: button: The lid device is not compliant to SW_LID.
[ 7897.302702] cachyos-x8664 kernel: ACPI: EC: interrupt unblocked
[ 7897.302753] cachyos-x8664 kernel: ACPI: EC: event unblocked
[ 7897.302794] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[ 7897.302836] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN00._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[ 7897.302870] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: Error updating fan power state
[ 7897.304131] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: dpm_run_callback(): platform_pm_resume returns -19
[ 7897.304747] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: failed to resume: error -19
[ 7897.305462] cachyos-x8664 kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[ 7897.306566] cachyos-x8664 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 7897.306717] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[ 7897.306800] cachyos-x8664 kernel: sd 0:0:0:0: [sda] Starting disk
[ 7897.307563] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[ 7897.307833] cachyos-x8664 kernel: ata1.00: configured for UDMA/133
[ 7897.307904] cachyos-x8664 kernel: usb 1-5: reset high-speed USB device number 4 using xhci_hcd
[ 7897.308708] cachyos-x8664 kernel: usb 1-3: reset full-speed USB device number 2 using xhci_hcd
[ 7897.309808] cachyos-x8664 kernel: OOM killer enabled.
[ 7897.310019] cachyos-x8664 kernel: Restarting tasks: Starting
[ 7897.310162] cachyos-x8664 kernel: Restarting tasks: Done
[ 7897.310336] cachyos-x8664 kernel: efivarfs: resyncing variable state
[ 7897.310440] cachyos-x8664 kernel: Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
[ 7897.310533] cachyos-x8664 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 7897.310618] cachyos-x8664 kernel: Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[ 7897.310822] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
[ 7897.310986] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
[ 7897.311127] cachyos-x8664 kernel: Bluetooth: hci0: RTL: cfg_sz 10, total sz 34926
[ 7897.397182] cachyos-x8664 kernel: efivarfs: finished resyncing variable state
[ 7897.397835] cachyos-x8664 kernel: random: crng reseeded on system resumption
[ 7897.397883] cachyos-x8664 kernel: PM: suspend exit
[ 7897.615138] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[ 7897.616042] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[ 7897.617149] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[ 7897.618200] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[ 7897.618902] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[ 7897.619611] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[ 7897.620169] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[ 7897.620443] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[ 7897.776059] cachyos-x8664 kernel: Bluetooth: hci0: RTL: fw version 0x75b8f098
[ 7897.845067] cachyos-x8664 kernel: Bluetooth: MGMT ver 1.23
[ 7902.451026] cachyos-x8664 rtw88-nss0-hook: resume log saved to /home/pc/Загрузки/test/logs/resume_dmesg_20260327_162345.txt
[ 7902.507037] cachyos-x8664 kernel: RTL8208 Fast Ethernet r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
[ 7902.941340] cachyos-x8664 kernel: r8169 0000:07:00.0 enp7s0: Link is Down
[ 7907.550045] cachyos-x8664 kernel: wlan0: authenticate with 6c:68:a4:1c:97:5b (local address=8c:c8:4b:68:d1:63)
[ 7907.593017] cachyos-x8664 kernel: wlan0: send auth to 6c:68:a4:1c:97:5b (try 1/3)
[ 7907.659023] cachyos-x8664 kernel: wlan0: authenticated
[ 7907.659113] cachyos-x8664 kernel: wlan0: associate with 6c:68:a4:1c:97:5b (try 1/3)
[ 7907.660022] cachyos-x8664 kernel: wlan0: RX AssocResp from 6c:68:a4:1c:97:5b (capab=0x431 status=0 aid=2)
[ 7907.661108] cachyos-x8664 kernel: wlan0: associated
[ 7907.746022] cachyos-x8664 kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 6c:68:a4:1c:97:5b
[ 7930.055371] cachyos-x8664 kernel: input: Soundcore Q10i (AVRCP) as /devices/virtual/input/input26
[ 8253.921280] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 8253.923200] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8253.932049] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 8253.932528] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8254.482029] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 8254.482817] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8254.493023] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 8254.493507] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8255.844064] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 8255.845405] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8255.855021] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 8255.855491] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8256.734042] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 8256.734514] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8256.744747] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 8256.745247] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8257.630070] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 8257.630534] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8257.639509] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 8257.639991] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8258.092047] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 8258.092508] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8258.102051] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 8258.102536] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 8434.786024] cachyos-x8664 kernel: wlan0: deauthenticating from 6c:68:a4:1c:97:5b by local choice (Reason: 3=DEAUTH_LEAVING)
[ 8434.849149] cachyos-x8664 kernel: Bluetooth: hci0: unexpected event for opcode 0xfc19
[ 8442.985025] cachyos-x8664 kernel: wlan0: authenticate with 6c:68:a4:1c:97:5b (local address=8c:c8:4b:68:d1:63)
[ 8443.027018] cachyos-x8664 kernel: wlan0: send auth to 6c:68:a4:1c:97:5b (try 1/3)
[ 8443.027070] cachyos-x8664 kernel: wlan0: authenticated
[ 8443.027114] cachyos-x8664 kernel: wlan0: associate with 6c:68:a4:1c:97:5b (try 1/3)
[ 8443.028025] cachyos-x8664 kernel: wlan0: RX AssocResp from 6c:68:a4:1c:97:5b (capab=0x431 status=0 aid=2)
[ 8443.029034] cachyos-x8664 kernel: wlan0: associated
[ 8443.092026] cachyos-x8664 kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 6c:68:a4:1c:97:5b
[ 8446.030073] cachyos-x8664 kernel: input: Soundcore Q10i (AVRCP) as /devices/virtual/input/input27
[ 8473.453443] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (7)
[ 8473.455124] cachyos-x8664 kernel: 00000000: a66135a6 2100b004 a0890228 000033b1  .5a....!(....3..
[ 8473.455198] cachyos-x8664 kernel: 00000010: 3ffe1e00 01d4aa4c 14677368 3296c5de  ...?L...hsg....2
[ 8473.455418] cachyos-x8664 kernel: 00000020: 640c84b9 9d87ad3a c468e252 5916b449  ...d:...R.h.I..Y
[ 8473.455746] cachyos-x8664 kernel: 00000030: e495d172 e3d14ba0                    r....K..
[ 8473.455812] cachyos-x8664 kernel: 00000000: a6 35 61 a6 04 b0 00 21 28 02 89 a0 b1 33 00 00  .5a....!(....3..
[ 8473.455860] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 4c aa d4 01 68 73 67 14 de c5 96 32  ...?L...hsg....2
[ 8473.455913] cachyos-x8664 kernel: 00000020: b9 84 0c 64 3a ad 87 9d                          ...d:...
[ 8645.468044] cachyos-x8664 kernel: wlan0: deauthenticating from 6c:68:a4:1c:97:5b by local choice (Reason: 3=DEAUTH_LEAVING)
[ 8646.436032] cachyos-x8664 kernel: PM: hibernation: hibernation entry
[ 8677.186487] cachyos-x8664 kernel: Filesystems sync: 0.217 seconds
[ 8677.200816] cachyos-x8664 kernel: Freezing user space processes
[ 8677.200893] cachyos-x8664 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
[ 8677.200954] cachyos-x8664 kernel: OOM killer disabled.
[ 8677.208598] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
[ 8677.208683] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00058000-0x00058fff]
[ 8677.208726] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00086000-0x000fffff]
[ 8677.208783] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x8d2fa000-0x8d303fff]
[ 8677.208823] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x9b88e000-0x9cffdfff]
[ 8677.208874] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x9cfff000-0xffffffff]
[ 8677.211574] cachyos-x8664 kernel: PM: hibernation: Basic memory bitmaps created
[ 8677.211678] cachyos-x8664 kernel: PM: hibernation: Preallocating image memory
[ 8677.211723] cachyos-x8664 kernel: PM: hibernation: Allocated 734777 pages for snapshot
[ 8677.211780] cachyos-x8664 kernel: PM: hibernation: Allocated 2939108 kbytes in 29.04 seconds (101.20 MB/s)
[ 8677.211832] cachyos-x8664 kernel: Freezing remaining freezable tasks
[ 8677.211872] cachyos-x8664 kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
[ 8677.211905] cachyos-x8664 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
[ 8677.211944] cachyos-x8664 kernel: ACPI: EC: interrupt blocked
[ 8677.213085] cachyos-x8664 kernel: ACPI: PM: Preparing to enter system sleep state S4
[ 8677.213188] cachyos-x8664 kernel: ACPI: EC: event blocked
[ 8677.213239] cachyos-x8664 kernel: ACPI: EC: EC stopped
[ 8677.213285] cachyos-x8664 kernel: ACPI: PM: Saving platform NVS memory
[ 8677.213332] cachyos-x8664 kernel: Disabling non-boot CPUs ...
[ 8677.213372] cachyos-x8664 kernel: smpboot: CPU 3 is now offline
[ 8677.213418] cachyos-x8664 kernel: smpboot: CPU 2 is now offline
[ 8677.213451] cachyos-x8664 kernel: smpboot: CPU 1 is now offline
[ 8677.213489] cachyos-x8664 kernel: PM: hibernation: Normal pages needed: 721162 + 1024, available pages: 2401365
[ 8677.213532] cachyos-x8664 kernel: ACPI: PM: Restoring platform NVS memory
[ 8677.213581] cachyos-x8664 kernel: ACPI: EC: EC started
[ 8677.213626] cachyos-x8664 kernel: Enabling non-boot CPUs ...
[ 8677.213657] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 8677.213694] cachyos-x8664 kernel: CPU1 is up
[ 8677.213737] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
[ 8677.213767] cachyos-x8664 kernel: CPU2 is up
[ 8677.213804] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 8677.213841] cachyos-x8664 kernel: CPU3 is up
[ 8677.213879] cachyos-x8664 kernel: ACPI: PM: Waking up from system sleep state S4
[ 8677.213918] cachyos-x8664 kernel: ACPI: EC: interrupt unblocked
[ 8677.213961] cachyos-x8664 kernel: usb usb1: root hub lost power or was reset
[ 8677.218395] cachyos-x8664 kernel: usb usb3: root hub lost power or was reset
[ 8677.220093] cachyos-x8664 kernel: ACPI: EC: event unblocked
[ 8677.220182] cachyos-x8664 kernel: usb usb2: root hub lost power or was reset
[ 8677.222551] cachyos-x8664 kernel: drm card1-eDP-1: Skipping unprepare of already unprepared panel
[ 8677.223284] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[ 8677.223352] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN00._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[ 8677.223400] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: Error updating fan power state
[ 8677.224434] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: dpm_run_callback(): platform_pm_restore returns -19
[ 8677.229897] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: failed to restore: error -19
[ 8677.232406] cachyos-x8664 kernel: usb 1-3: WARN: invalid context state for evaluate context command.
[ 8677.233796] cachyos-x8664 kernel: ------------[ cut here ]------------
[ 8677.233853] cachyos-x8664 kernel: i915 0000:00:02.0: [drm] primary A assertion failure (expected off, current on)
[ 8677.233886] cachyos-x8664 kernel: WARNING: drivers/gpu/drm/i915/display/intel_display.c:410 at assert_plane+0xd6/0x140 [i915], CPU#2: kworker/u16:13/100075
[ 8677.233939] cachyos-x8664 kernel: Modules linked in: uinput snd_seq_dummy snd_hrtimer rfcomm snd_seq snd_seq_device ccm cmac algif_hash algif_skcipher af_alg bnep hp_bioscfg firmware_attributes_class amdgpu x86_pkg_temp_thermal intel_powerclamp coretemp rtw_8821ce(OE) kvm_intel snd_ctl_led snd_hda_codec_alc269 snd_hda_scodec_component rtw_8821c(OE) rmi_smbus snd_hda_codec_realtek_lib rtw_pci(OE) kvm snd_hda_codec_intelhdmi processor_thermal_device_pci_legacy snd_hda_codec_generic rmi_core drm_panel_backlight_quirks snd_hda_codec_hdmi rtw_core(OE) processor_thermal_device processor_thermal_power_floor irqbypass amdxcp processor_thermal_wt_hint snd_hda_intel btusb gpu_sched btmtk ghash_clmulni_intel processor_thermal_wt_req snd_hda_codec uvcvideo mac80211 aesni_intel vfat btbcm uvc fat rapl videobuf2_vmalloc snd_hda_core videobuf2_memops r8169 at24 btintel intel_cstate videobuf2_v4l2 processor_thermal_rfim snd_intel_dspcfg mei_hdcp mei_pxp intel_rapl_msr radeon btrtl spi_nor i2c_i801 intel_uncore processor_thermal_mbox realtek hp_wmi
[ 8677.234057] cachyos-x8664 kernel:  snd_intel_sdw_acpi wmi_bmof videobuf2_common drm_suballoc_helper snd_hwdep mtd sparse_keymap mdio_devres bluetooth cfg80211 drm_exec platform_temperature_control i2c_smbus psmouse pcspkr snd_pcm drm_ttm_helper libphy videodev i2c_mux processor_thermal_rapl intel_pch_thermal mei_me mc libarc4 rfkill snd_timer mdio_bus intel_rapl_common mei processor_thermal_soc_slider platform_profile snd int340x_thermal_zone intel_soc_dts_iosf soundcore intel_oc_wdt i2c_hid_acpi int3400_thermal i2c_hid acpi_thermal_rel wireless_hotkey acpi_pad mousedev joydev mac_hid tcp_bbr dm_mod ntsync i2c_dev crypto_user pkcs8_key_parser nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress i915 spi_intel_platform drm_buddy spi_intel intel_gtt ttm i2c_algo_bit drm_display_helper video cec lpc_ich wmi serio_raw
[ 8677.234156] cachyos-x8664 kernel: CPU: 2 UID: 0 PID: 100075 Comm: kworker/u16:13 Tainted: G          IOE       6.19.9-2-cachyos #1 PREEMPT(full)  02bb0ae94e3484fd95eb7c5534d2c734ca97d599
[ 8677.234210] cachyos-x8664 kernel: Tainted: [I]=FIRMWARE_WORKAROUND, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[ 8677.234256] cachyos-x8664 kernel: Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
[ 8677.234326] cachyos-x8664 kernel: Workqueue: async async_run_entry_fn
[ 8677.234414] cachyos-x8664 kernel: RIP: 0010:assert_plane+0x135/0x140 [i915]
[ 8677.234456] cachyos-x8664 kernel: Code: 4e 18 48 c7 c6 31 55 c4 c0 84 db 49 c7 c0 c6 9a c2 c0 4c 0f 45 c6 49 c7 c1 c6 9a c2 c0 40 84 ed 4c 0f 45 ce 4c 89 ff 48 89 c6 <67> 48 0f b9 3a e9 19 ff ff ff cc 90 90 90 90 90 90 90 90 90 90 90
[ 8677.234513] cachyos-x8664 kernel: RSP: 0000:ffffcfebcc7dba38 EFLAGS: 00010202
[ 8677.234559] cachyos-x8664 kernel: RAX: ffffffffc0c497b5 RBX: 0000000000000000 RCX: ffff88e68730b840
[ 8677.234615] cachyos-x8664 kernel: RDX: ffff88e681e81fb0 RSI: ffffffffc0c497b5 RDI: ffffffffc0682650
[ 8677.234663] cachyos-x8664 kernel: RBP: 0000000000000001 R08: ffffffffc0c29ac6 R09: ffffffffc0c45531
[ 8677.234721] cachyos-x8664 kernel: R10: 0000000000000004 R11: ffffffffa0d856e0 R12: ffff88e68ac06000
[ 8677.234777] cachyos-x8664 kernel: R13: ffff88e68ac06000 R14: ffff88e68caba000 R15: ffffffffc0682650
[ 8677.234828] cachyos-x8664 kernel: FS:  0000000000000000(0000) GS:ffff88e92efd3000(0000) knlGS:0000000000000000
[ 8677.234880] cachyos-x8664 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 8677.234910] cachyos-x8664 kernel: CR2: 0000000000000000 CR3: 0000000021014001 CR4: 00000000003726f0
[ 8677.234953] cachyos-x8664 kernel: Call Trace:
[ 8677.234983] cachyos-x8664 kernel:  <TASK>
[ 8677.235024] cachyos-x8664 kernel:  intel_disable_transcoder+0xbb/0x340 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.235063] cachyos-x8664 kernel:  intel_ddi_post_disable+0x10d/0x910 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.235117] cachyos-x8664 kernel:  hsw_crtc_disable+0x143/0x2e0 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.235170] cachyos-x8664 kernel:  intel_old_crtc_state_disables+0xdf/0x1a0 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.235254] cachyos-x8664 kernel:  intel_atomic_commit_tail+0xb28/0x19d0 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.235296] cachyos-x8664 kernel:  ? __pfx_pci_pm_restore.llvm.12419904442660537214+0x10/0x10
[ 8677.235343] cachyos-x8664 kernel:  intel_atomic_commit+0x247/0x280 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.235389] cachyos-x8664 kernel:  drm_atomic_commit+0xc3/0xf0
[ 8677.235421] cachyos-x8664 kernel:  ? __pfx___drm_printfn_info+0x10/0x10
[ 8677.235460] cachyos-x8664 kernel:  drm_atomic_helper_commit_duplicated_state+0x105/0x120
[ 8677.235523] cachyos-x8664 kernel:  __intel_display_driver_resume+0x8d/0xf0 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.235601] cachyos-x8664 kernel:  intel_display_driver_resume+0xdc/0x180 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.235652] cachyos-x8664 kernel:  i915_drm_resume+0x1d6/0x290 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.235684] cachyos-x8664 kernel:  device_resume+0x39c/0xa60
[ 8677.235716] cachyos-x8664 kernel:  async_resume+0x1d/0x40
[ 8677.235748] cachyos-x8664 kernel:  async_run_entry_fn+0x32/0x180
[ 8677.235790] cachyos-x8664 kernel:  process_scheduled_works+0x1f3/0x5e0
[ 8677.235823] cachyos-x8664 kernel:  worker_thread+0x18d/0x340
[ 8677.235863] cachyos-x8664 kernel:  ? __pfx_worker_thread+0x10/0x10
[ 8677.235918] cachyos-x8664 kernel:  kthread+0x205/0x280
[ 8677.235958] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 8677.235990] cachyos-x8664 kernel:  ret_from_fork+0x118/0x260
[ 8677.236035] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 8677.236070] cachyos-x8664 kernel:  ret_from_fork_asm+0x1a/0x30
[ 8677.236104] cachyos-x8664 kernel:  </TASK>
[ 8677.236143] cachyos-x8664 kernel: ---[ end trace 0000000000000000 ]---
[ 8677.236190] cachyos-x8664 kernel: usb 1-3: reset full-speed USB device number 2 using xhci_hcd
[ 8677.236977] cachyos-x8664 kernel: usb 2-1: reset high-speed USB device number 2 using ehci-pci
[ 8677.237842] cachyos-x8664 kernel: ------------[ cut here ]------------
[ 8677.237910] cachyos-x8664 kernel: i915 0000:00:02.0: [drm] primary A assertion failure (expected off, current on)
[ 8677.237978] cachyos-x8664 kernel: WARNING: drivers/gpu/drm/i915/display/intel_display.c:410 at assert_plane+0xd6/0x140 [i915], CPU#2: kworker/u16:13/100075
[ 8677.238041] cachyos-x8664 kernel: Modules linked in: uinput snd_seq_dummy snd_hrtimer rfcomm snd_seq snd_seq_device ccm cmac algif_hash algif_skcipher af_alg bnep hp_bioscfg firmware_attributes_class amdgpu x86_pkg_temp_thermal intel_powerclamp coretemp rtw_8821ce(OE) kvm_intel snd_ctl_led snd_hda_codec_alc269 snd_hda_scodec_component rtw_8821c(OE) rmi_smbus snd_hda_codec_realtek_lib rtw_pci(OE) kvm snd_hda_codec_intelhdmi processor_thermal_device_pci_legacy snd_hda_codec_generic rmi_core drm_panel_backlight_quirks snd_hda_codec_hdmi rtw_core(OE) processor_thermal_device processor_thermal_power_floor irqbypass amdxcp processor_thermal_wt_hint snd_hda_intel btusb gpu_sched btmtk ghash_clmulni_intel processor_thermal_wt_req snd_hda_codec uvcvideo mac80211 aesni_intel vfat btbcm uvc fat rapl videobuf2_vmalloc snd_hda_core videobuf2_memops r8169 at24 btintel intel_cstate videobuf2_v4l2 processor_thermal_rfim snd_intel_dspcfg mei_hdcp mei_pxp intel_rapl_msr radeon btrtl spi_nor i2c_i801 intel_uncore processor_thermal_mbox realtek hp_wmi
[ 8677.238240] cachyos-x8664 kernel:  snd_intel_sdw_acpi wmi_bmof videobuf2_common drm_suballoc_helper snd_hwdep mtd sparse_keymap mdio_devres bluetooth cfg80211 drm_exec platform_temperature_control i2c_smbus psmouse pcspkr snd_pcm drm_ttm_helper libphy videodev i2c_mux processor_thermal_rapl intel_pch_thermal mei_me mc libarc4 rfkill snd_timer mdio_bus intel_rapl_common mei processor_thermal_soc_slider platform_profile snd int340x_thermal_zone intel_soc_dts_iosf soundcore intel_oc_wdt i2c_hid_acpi int3400_thermal i2c_hid acpi_thermal_rel wireless_hotkey acpi_pad mousedev joydev mac_hid tcp_bbr dm_mod ntsync i2c_dev crypto_user pkcs8_key_parser nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress i915 spi_intel_platform drm_buddy spi_intel intel_gtt ttm i2c_algo_bit drm_display_helper video cec lpc_ich wmi serio_raw
[ 8677.238313] cachyos-x8664 kernel: CPU: 2 UID: 0 PID: 100075 Comm: kworker/u16:13 Tainted: G        W IOE       6.19.9-2-cachyos #1 PREEMPT(full)  02bb0ae94e3484fd95eb7c5534d2c734ca97d599
[ 8677.238359] cachyos-x8664 kernel: Tainted: [W]=WARN, [I]=FIRMWARE_WORKAROUND, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[ 8677.238403] cachyos-x8664 kernel: Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
[ 8677.238436] cachyos-x8664 kernel: Workqueue: async async_run_entry_fn
[ 8677.238469] cachyos-x8664 kernel: RIP: 0010:assert_plane+0x135/0x140 [i915]
[ 8677.238510] cachyos-x8664 kernel: Code: 4e 18 48 c7 c6 31 55 c4 c0 84 db 49 c7 c0 c6 9a c2 c0 4c 0f 45 c6 49 c7 c1 c6 9a c2 c0 40 84 ed 4c 0f 45 ce 4c 89 ff 48 89 c6 <67> 48 0f b9 3a e9 19 ff ff ff cc 90 90 90 90 90 90 90 90 90 90 90
[ 8677.238552] cachyos-x8664 kernel: RSP: 0000:ffffcfebcc7dbb70 EFLAGS: 00010202
[ 8677.238594] cachyos-x8664 kernel: RAX: ffffffffc0c497b5 RBX: 0000000000000000 RCX: ffff88e68730b840
[ 8677.238641] cachyos-x8664 kernel: RDX: ffff88e681e81fb0 RSI: ffffffffc0c497b5 RDI: ffffffffc0682650
[ 8677.238703] cachyos-x8664 kernel: RBP: 0000000000000001 R08: ffffffffc0c29ac6 R09: ffffffffc0c45531
[ 8677.238747] cachyos-x8664 kernel: R10: ffff88e73b884000 R11: ffffffffa0d856e0 R12: ffff88e68ac06000
[ 8677.238792] cachyos-x8664 kernel: R13: ffff88e81d7a0000 R14: ffff88e68caba000 R15: ffffffffc0682650
[ 8677.238830] cachyos-x8664 kernel: FS:  0000000000000000(0000) GS:ffff88e92efd3000(0000) knlGS:0000000000000000
[ 8677.238861] cachyos-x8664 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 8677.238891] cachyos-x8664 kernel: CR2: 0000000000000000 CR3: 0000000021014001 CR4: 00000000003726f0
[ 8677.238939] cachyos-x8664 kernel: Call Trace:
[ 8677.238981] cachyos-x8664 kernel:  <TASK>
[ 8677.239059] cachyos-x8664 kernel:  intel_atomic_commit_tail+0x17d8/0x19d0 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.239130] cachyos-x8664 kernel:  ? __pfx_pci_pm_restore.llvm.12419904442660537214+0x10/0x10
[ 8677.239200] cachyos-x8664 kernel:  intel_atomic_commit+0x247/0x280 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.239237] cachyos-x8664 kernel:  drm_atomic_commit+0xc3/0xf0
[ 8677.239266] cachyos-x8664 kernel:  ? __pfx___drm_printfn_info+0x10/0x10
[ 8677.239297] cachyos-x8664 kernel:  drm_atomic_helper_commit_duplicated_state+0x105/0x120
[ 8677.239350] cachyos-x8664 kernel:  __intel_display_driver_resume+0x8d/0xf0 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.239380] cachyos-x8664 kernel:  intel_display_driver_resume+0xdc/0x180 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.239410] cachyos-x8664 kernel:  i915_drm_resume+0x1d6/0x290 [i915 52486d6213de99fc09458245751ac9837780e941]
[ 8677.239439] cachyos-x8664 kernel:  device_resume+0x39c/0xa60
[ 8677.239477] cachyos-x8664 kernel:  async_resume+0x1d/0x40
[ 8677.239507] cachyos-x8664 kernel:  async_run_entry_fn+0x32/0x180
[ 8677.239537] cachyos-x8664 kernel:  process_scheduled_works+0x1f3/0x5e0
[ 8677.239566] cachyos-x8664 kernel:  worker_thread+0x18d/0x340
[ 8677.239934] cachyos-x8664 kernel:  ? __pfx_worker_thread+0x10/0x10
[ 8677.239978] cachyos-x8664 kernel:  kthread+0x205/0x280
[ 8677.240033] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 8677.240083] cachyos-x8664 kernel:  ret_from_fork+0x118/0x260
[ 8677.240121] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 8677.240150] cachyos-x8664 kernel:  ret_from_fork_asm+0x1a/0x30
[ 8677.240179] cachyos-x8664 kernel:  </TASK>
[ 8677.240216] cachyos-x8664 kernel: ---[ end trace 0000000000000000 ]---
[ 8677.240255] cachyos-x8664 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 8677.240286] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[ 8677.240316] cachyos-x8664 kernel: sd 0:0:0:0: [sda] Starting disk
[ 8677.240990] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[ 8677.241046] cachyos-x8664 kernel: ata1.00: configured for UDMA/133
[ 8677.241080] cachyos-x8664 kernel: usb 1-5: reset high-speed USB device number 4 using xhci_hcd
[ 8677.242143] cachyos-x8664 kernel: usb 1-4: WARN: invalid context state for evaluate context command.
[ 8677.243258] cachyos-x8664 kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[ 8677.244378] cachyos-x8664 kernel: PM: hibernation: Basic memory bitmaps freed
[ 8677.244430] cachyos-x8664 kernel: OOM killer enabled.
[ 8677.244478] cachyos-x8664 kernel: Restarting tasks: Starting
[ 8677.244517] cachyos-x8664 kernel: Restarting tasks: Done
[ 8677.244555] cachyos-x8664 kernel: efivarfs: resyncing variable state
[ 8677.244592] cachyos-x8664 kernel: efivarfs: removing variable HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
[ 8677.263693] cachyos-x8664 kernel: Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
[ 8677.263842] cachyos-x8664 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 8677.265059] cachyos-x8664 kernel: Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[ 8677.266227] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
[ 8677.266297] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
[ 8677.266352] cachyos-x8664 kernel: Bluetooth: hci0: RTL: cfg_sz 10, total sz 34926
[ 8677.327024] cachyos-x8664 kernel: efivarfs: finished resyncing variable state
[ 8677.328161] cachyos-x8664 kernel: PM: hibernation: hibernation exit
[ 8677.502201] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[ 8677.503179] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[ 8677.503496] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[ 8677.504057] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[ 8677.504614] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[ 8677.505151] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[ 8677.505863] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[ 8677.506697] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[ 8677.739040] cachyos-x8664 kernel: Bluetooth: hci0: RTL: fw version 0x75b8f098
[ 8677.807164] cachyos-x8664 kernel: Bluetooth: MGMT ver 1.23
[ 8682.421028] cachyos-x8664 rtw88-nss0-hook: resume log saved to /home/pc/Загрузки/test/logs/resume_dmesg_20260327_163833.txt
[ 8682.993173] cachyos-x8664 kernel: RTL8208 Fast Ethernet r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
[ 8683.479029] cachyos-x8664 kernel: r8169 0000:07:00.0 enp7s0: Link is Down
[ 8688.142056] cachyos-x8664 kernel: wlan0: authenticate with 6c:68:a4:1c:97:5b (local address=8c:c8:4b:68:d1:63)
[ 8688.185048] cachyos-x8664 kernel: wlan0: send auth to 6c:68:a4:1c:97:5b (try 1/3)
[ 8688.254021] cachyos-x8664 kernel: wlan0: authenticated
[ 8688.254086] cachyos-x8664 kernel: wlan0: associate with 6c:68:a4:1c:97:5b (try 1/3)
[ 8688.256052] cachyos-x8664 kernel: wlan0: RX AssocResp from 6c:68:a4:1c:97:5b (capab=0x431 status=0 aid=2)
[ 8688.256125] cachyos-x8664 kernel: wlan0: associated
[ 8688.322049] cachyos-x8664 kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 6c:68:a4:1c:97:5b
[ 8707.162025] cachyos-x8664 kernel: input: Soundcore Q10i (AVRCP) as /devices/virtual/input/input28
[ 9570.111088] cachyos-x8664 kernel: usb 1-3: USB disconnect, device number 2
[ 9573.289061] cachyos-x8664 kernel: usb 1-3: new full-speed USB device number 5 using xhci_hcd
[ 9573.416292] cachyos-x8664 kernel: usb 1-3: New USB device found, idVendor=379a, idProduct=0cf0, bcdDevice= 2.02
[ 9573.417042] cachyos-x8664 kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9573.418449] cachyos-x8664 kernel: usb 1-3: Product: Quasar 3WL
[ 9573.418932] cachyos-x8664 kernel: usb 1-3: Manufacturer: Compx
[ 9573.419374] cachyos-x8664 kernel: input: Compx Quasar 3WL as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:379A:0CF0.0004/input/input29
[ 9573.486042] cachyos-x8664 kernel: hid-generic 0003:379A:0CF0.0004: input,hidraw0: USB HID v1.11 Keyboard [Compx Quasar 3WL] on usb-0000:00:14.0-3/input0
[ 9573.488028] cachyos-x8664 kernel: input: Compx Quasar 3WL as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:379A:0CF0.0005/input/input30
[ 9573.488159] cachyos-x8664 kernel: input: Compx Quasar 3WL as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:379A:0CF0.0005/input/input31
[ 9573.488219] cachyos-x8664 kernel: input: Compx Quasar 3WL Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:379A:0CF0.0005/input/input32
[ 9573.539057] cachyos-x8664 kernel: input: Compx Quasar 3WL System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:379A:0CF0.0005/input/input33
[ 9573.539373] cachyos-x8664 kernel: input: Compx Quasar 3WL as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:379A:0CF0.0005/input/input34
[ 9573.540182] cachyos-x8664 kernel: hid-generic 0003:379A:0CF0.0005: input,hiddev96,hidraw1: USB HID v1.11 Device [Compx Quasar 3WL] on usb-0000:00:14.0-3/input1
[ 9573.542026] cachyos-x8664 kernel: input: Compx Quasar 3WL as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.2/0003:379A:0CF0.0006/input/input35
[ 9573.543024] cachyos-x8664 kernel: hid-generic 0003:379A:0CF0.0006: input,hidraw2: USB HID v1.11 Mouse [Compx Quasar 3WL] on usb-0000:00:14.0-3/input2
[ 9590.224046] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9590.224626] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.236073] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9590.236534] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.513840] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9590.514483] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.523019] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9590.523594] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.578101] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9590.578769] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.590024] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9590.590737] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.643258] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9590.643905] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.654020] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9590.654478] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.709267] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9590.709906] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.720032] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9590.720500] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.778278] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9590.779488] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.788820] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9590.790101] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.843028] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9590.843551] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.854017] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9590.854467] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.908018] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9590.908487] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.920053] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9590.920513] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.974589] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9590.975045] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9590.985188] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9590.985667] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.043061] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9591.044651] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.052031] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9591.052619] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.105094] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9591.106721] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.117045] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9591.118107] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.171034] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9591.171623] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.183356] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9591.184424] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.239285] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9591.239757] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.250034] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9591.250485] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.305236] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9591.306550] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.315046] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9591.315509] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.370028] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9591.370489] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.381038] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9591.381540] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.438103] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9591.439197] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.449040] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9591.449758] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.580321] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9591.581534] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.590792] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9591.592447] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.938976] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9591.939486] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9591.948563] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9591.949172] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9592.197171] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9592.197901] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9592.206041] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9592.206494] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9592.505094] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9592.505644] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9592.515052] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9592.515603] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9592.886918] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9592.888079] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9592.898825] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9592.899390] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9593.410044] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9593.410578] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9593.421037] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9593.421491] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.108532] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9594.108999] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.120055] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9594.120523] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.394021] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9594.394661] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.406030] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9594.406719] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.462046] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9594.462562] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.473034] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9594.473525] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.528167] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9594.528819] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.539052] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9594.539558] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.594234] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9594.595864] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.604046] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9594.604471] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.658277] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9594.658769] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.670040] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9594.670744] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.723707] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9594.724149] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.736032] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9594.737268] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.793015] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9594.793524] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.803053] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9594.803497] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.856019] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9594.856455] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.867020] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9594.867469] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.925213] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9594.926078] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.935025] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9594.935514] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9594.989069] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9594.989542] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.000061] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.000810] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.056035] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.056721] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.065289] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.066043] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.120356] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.120810] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.132084] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.132530] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.187111] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.187717] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.200048] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.200504] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.255353] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.256978] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.265064] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.265810] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.320024] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.320485] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.330512] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.331074] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.387092] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.387530] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.396033] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.396639] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.451232] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.451878] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.462053] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.462577] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.517025] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.518032] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.528048] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.528890] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.583031] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.583526] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.595037] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.595667] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.652029] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.652488] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.662092] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.663219] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.717132] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.717705] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.728033] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.728697] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.782834] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.783735] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.796946] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.798565] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.849053] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.849538] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.860037] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.860718] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.914070] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.914536] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.924781] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.925366] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.981128] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9595.981742] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9595.992023] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9595.993859] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.045032] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.045770] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.059048] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.059500] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.112035] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.112580] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.122556] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.123179] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.179261] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.180498] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.190055] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.190492] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.246335] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.246941] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.255895] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.256372] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.310041] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.310487] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.322092] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.322534] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.377043] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.377759] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.386044] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.386858] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.442029] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.442505] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.452065] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.452500] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.508114] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.508774] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.519024] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.519597] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.575044] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.575497] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.587469] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.587897] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.641203] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.641987] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.652021] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.652550] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.708059] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.708518] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.719030] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.719463] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.772130] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.772719] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.783059] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.783491] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.838374] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.838834] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.849056] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.849507] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.904061] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.904510] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.917041] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.917514] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.973026] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9596.973641] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9596.982046] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9596.983043] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.037175] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.037757] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.048068] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.048540] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.103042] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.103469] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.113365] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.113821] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.170062] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.170528] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.179031] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.179611] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.235046] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.235734] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.245117] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.245864] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.300097] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.300723] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.310677] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.311177] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.368096] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.368551] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.379056] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.379553] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.433306] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.433758] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.446092] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.447591] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.499084] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.499878] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.509048] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.510108] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.565042] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.565620] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.577044] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.577536] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.630049] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.630480] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.641091] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.641581] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.698751] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.699313] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.709050] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.709933] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.765067] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.765518] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.777156] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.777781] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.831147] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.831758] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.840602] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.841034] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.896034] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.896516] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.907088] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.907518] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.961087] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9597.962566] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9597.972047] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9597.972475] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.027121] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9598.028110] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.037546] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9598.037982] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.096869] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9598.097620] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.104542] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9598.105372] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.158070] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9598.158821] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.171019] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9598.171611] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.225019] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9598.225451] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.236029] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9598.236502] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.292023] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9598.292528] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.303058] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9598.303495] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.357105] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9598.357660] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.368044] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9598.368491] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.421625] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9598.422066] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.433230] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9598.433686] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.489916] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9598.490608] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.502019] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9598.502453] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.665867] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9598.666330] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.678034] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9598.678678] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.957118] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9598.957826] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9598.967050] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9598.967551] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.022052] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.022860] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.033050] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.033525] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.087230] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.087687] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.098441] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.098898] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.154030] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.154920] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.166439] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.167425] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.219167] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.219900] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.230036] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.230465] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.287386] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.287924] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.298023] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.298450] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.352028] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.352461] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.363385] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.364138] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.420023] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.420473] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.431122] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.433148] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.485141] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.485718] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.495032] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.495496] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.552033] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.552652] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.562712] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.564135] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.616054] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.616518] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.627039] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.627667] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.683047] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.683487] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.694235] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.695090] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.749337] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.749918] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.760046] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.760830] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.815042] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.815558] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.827087] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.827884] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.880027] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.880763] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.891053] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.891791] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.946041] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9599.946486] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9599.957055] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9599.957598] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.012131] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.012744] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.024219] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.024870] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.080061] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.080902] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.092367] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.093121] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.144848] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.146089] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.157179] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.158704] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.212046] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.212788] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.224085] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.224772] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.277209] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.277916] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.288024] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.288491] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.345237] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.345789] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.355060] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.355543] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.408046] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.409487] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.419716] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.420502] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.475040] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.475606] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.486024] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.486544] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.541151] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.541926] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.552036] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.552665] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.608090] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.608602] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.618029] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.618489] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.673024] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.673646] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.685018] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.685495] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.739035] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.739593] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.750052] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.750800] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.807118] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.808697] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.818030] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.819044] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.871018] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.871482] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.881516] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.882089] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.937021] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9600.937503] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9600.950031] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9600.950679] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9601.004038] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9601.004843] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9601.015519] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9601.016281] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9601.333061] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9601.333520] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9601.344036] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9601.344729] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9601.746312] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9601.747081] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9601.757027] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9601.758704] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9602.100109] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9602.100589] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9602.111033] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9602.111805] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9602.519051] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[ 9602.519567] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9602.530023] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[ 9602.530579] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[ 9789.289023] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (11)
[ 9789.289834] cachyos-x8664 kernel: 00000000: 45cc9769 4b3aff7c c769fd09 00003388  i..E|.:K..i..3..
[ 9789.289883] cachyos-x8664 kernel: 00000010: 3ffe1e00 41a51108 00002b01 012a1100  ...?...A.+....*.
[ 9789.289918] cachyos-x8664 kernel: 00000020: 00000020 20000000 000000d6 00000012   ...... ........
[ 9789.290116] cachyos-x8664 kernel: 00000030: 0000001e 00000000                    ........
[ 9789.290181] cachyos-x8664 kernel: 00000000: 69 97 cc 45 7c ff 3a 4b 09 fd 69 c7 88 33 00 00  i..E|.:K..i..3..
[ 9789.290255] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 08 11 a5 41 01 2b 00 00 00 11 2a 01  ...?...A.+....*.
[ 9789.290305] cachyos-x8664 kernel: 00000020: 20 00 00 00 00 00 00 20                           ...... 
[ 9802.321033] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (10)
[ 9802.321667] cachyos-x8664 kernel: 00000000: 474f339c 21009004 80890976 000033b0  .3OG...!v....3..
[ 9802.321734] cachyos-x8664 kernel: 00000010: 3ffe1e00 426c5f7c 6ad43a41 e0b8e58f  ...?|_lBA:.j....
[ 9802.321777] cachyos-x8664 kernel: 00000020: ccb0713b dd2aa160 e2fc5cf7 c9eda0c3  ;q..`.*..\......
[ 9802.321839] cachyos-x8664 kernel: 00000030: 9dd8071e 0ca4f974                    ....t...
[ 9802.321878] cachyos-x8664 kernel: 00000000: 9c 33 4f 47 04 90 00 21 76 09 89 80 b0 33 00 00  .3OG...!v....3..
[ 9802.321898] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 7c 5f 6c 42 41 3a d4 6a 8f e5 b8 e0  ...?|_lBA:.j....
[ 9802.321916] cachyos-x8664 kernel: 00000020: 3b 71 b0 cc 60 a1 2a dd                          ;q..`.*.
[ 9819.025079] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (8)
[ 9819.025659] cachyos-x8664 kernel: 00000000: cced3e4e 72756ac2 6212bf68 c9cd5dcb  N>...jurh..b.]..
[ 9819.025723] cachyos-x8664 kernel: 00000010: e27f977c 64cfe3ec cba73f28 4ce593e5  |......d(?.....L
[ 9819.025756] cachyos-x8664 kernel: 00000020: a2248b01 d30ba802 fcec19e3 71a514b9  ..$............q
[ 9819.025789] cachyos-x8664 kernel: 00000030: f91a49dd c6dba3e2                    .I......
[ 9819.025819] cachyos-x8664 kernel: 00000000: 4e 3e ed cc c2 6a 75 72 68 bf 12 62 cb 5d cd c9  N>...jurh..b.]..
[ 9819.025843] cachyos-x8664 kernel: 00000010: 7c 97 7f e2 ec e3 cf 64 28 3f a7 cb e5 93 e5 4c  |......d(?.....L
[ 9819.025873] cachyos-x8664 kernel: 00000020: 01 8b 24 a2 02 a8 0b d3                          ..$.....
[ 9829.355023] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (14)
[ 9829.355919] cachyos-x8664 kernel: 00000000: 0566b662 dd6ce81d e040093d 00003388  b.f...l.=.@..3..
[ 9829.356014] cachyos-x8664 kernel: 00000010: 3ffe1e00 4408da4b 00002e01 012a1100  ...?K..D......*.
[ 9829.356077] cachyos-x8664 kernel: 00000020: 00000020 20000000 000000d0 0000000d   ...... ........
[ 9829.356120] cachyos-x8664 kernel: 00000030: 00000027 00000000                    '.......
[ 9829.356215] cachyos-x8664 kernel: 00000000: 62 b6 66 05 1d e8 6c dd 3d 09 40 e0 88 33 00 00  b.f...l.=.@..3..
[ 9829.356264] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 4b da 08 44 01 2e 00 00 00 11 2a 01  ...?K..D......*.
[ 9829.356297] cachyos-x8664 kernel: 00000020: 20 00 00 00 00 00 00 20                           ...... 
[ 9832.889021] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (15)
[ 9832.889560] cachyos-x8664 kernel: 00000000: 1c92a1c6 976b68a7 89adbd12 94ab9830  .....hk.....0...
[ 9832.889603] cachyos-x8664 kernel: 00000010: 3ffe1e00 443e3fec 4191c21f 5f549b0e  ...?.?>D...A..T_
[ 9832.889637] cachyos-x8664 kernel: 00000020: 1840eb30 6225d36f 2def7192 afce1a81  0.@.o.%b.q.-....
[ 9832.889669] cachyos-x8664 kernel: 00000030: abb0fc91 4c335f2f                    ..../_3L
[ 9832.889703] cachyos-x8664 kernel: 00000000: c6 a1 92 1c a7 68 6b 97 12 bd ad 89 30 98 ab 94  .....hk.....0...
[ 9832.889745] cachyos-x8664 kernel: 00000010: 00 1e fe 3f ec 3f 3e 44 1f c2 91 41 0e 9b 54 5f  ...?.?>D...A..T_
[ 9832.889776] cachyos-x8664 kernel: 00000020: 30 eb 40 18 6f d3 25 62                          0.@.o.%b
[ 9835.274022] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (15)
[ 9835.274504] cachyos-x8664 kernel: 00000000: 8e231297 a361d9ac cafc9653 a0cea374  ..#...a.S...t...
[ 9835.274531] cachyos-x8664 kernel: 00000010: 33be266f 4f515fe8 e80f73a3 d932a3fa  o&.3._QO.s....2.
[ 9835.274574] cachyos-x8664 kernel: 00000020: 1f91282c 86e28b8e 27205d38 eb87b9b6  ,(......8] '....
[ 9835.274600] cachyos-x8664 kernel: 00000030: b515f5bc 26cb7954                    ....Ty.&
[ 9835.274619] cachyos-x8664 kernel: 00000000: 97 12 23 8e ac d9 61 a3 53 96 fc ca 74 a3 ce a0  ..#...a.S...t...
[ 9835.274648] cachyos-x8664 kernel: 00000010: 6f 26 be 33 e8 5f 51 4f a3 73 0f e8 fa a3 32 d9  o&.3._QO.s....2.
[ 9835.274683] cachyos-x8664 kernel: 00000020: 2c 28 91 1f 8e 8b e2 86                          ,(......
[ 9835.288025] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (12)
[ 9835.288628] cachyos-x8664 kernel: 00000000: 157fb31c 7e9594d1 e3f45e70 10bfa1b4  .......~p^......
[ 9835.288669] cachyos-x8664 kernel: 00000010: 3ffe1e7e 4462f12e 00002c01 012a1100  ~..?..bD.,....*.
[ 9835.288695] cachyos-x8664 kernel: 00000020: 00000014 20000000 000000d0 0000000e  ....... ........
[ 9835.288746] cachyos-x8664 kernel: 00000030: 00000024 00000000                    $.......
[ 9835.288800] cachyos-x8664 kernel: 00000000: 1c b3 7f 15 d1 94 95 7e 70 5e f4 e3 b4 a1 bf 10  .......~p^......
[ 9835.288878] cachyos-x8664 kernel: 00000010: 7e 1e fe 3f 2e f1 62 44 01 2c 00 00 00 11 2a 01  ~..?..bD.,....*.
[ 9835.288928] cachyos-x8664 kernel: 00000020: 14 00 00 00 00 00 00 20                          ....... 
[ 9837.993016] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (11)
[ 9837.993599] cachyos-x8664 kernel: 00000000: 4cf56350 2f0e8d29 0c6466c4 28e3d7fd  Pc.L)../.fd....(
[ 9837.993636] cachyos-x8664 kernel: 00000010: 8aa9ce95 582a68f4 05e0713b 012a0900  .....h*X;q....*.
[ 9837.993659] cachyos-x8664 kernel: 00000020: 00000014 20000000 000000e2 0000000e  ....... ........
[ 9837.993720] cachyos-x8664 kernel: 00000030: 00000023 00000000                    #.......
[ 9837.993757] cachyos-x8664 kernel: 00000000: 50 63 f5 4c 29 8d 0e 2f c4 66 64 0c fd d7 e3 28  Pc.L)../.fd....(
[ 9837.993803] cachyos-x8664 kernel: 00000010: 95 ce a9 8a f4 68 2a 58 3b 71 e0 05 00 09 2a 01  .....h*X;q....*.
[ 9837.993824] cachyos-x8664 kernel: 00000020: 14 00 00 00 00 00 00 20                          ....... 
[ 9839.002023] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (14)
[ 9839.002643] cachyos-x8664 kernel: 00000000: 3de02cbd 11000000 80400a87 00003388  .,.=......@..3..
[ 9839.002676] cachyos-x8664 kernel: 00000010: 3ffe1e00 449bb63e 00002e01 012a1100  ...?>..D......*.
[ 9839.002725] cachyos-x8664 kernel: 00000020: 00000020 20000000 000000d8 0000000e   ...... ........
[ 9839.002760] cachyos-x8664 kernel: 00000030: 00000025 00000000                    %.......
[ 9839.002796] cachyos-x8664 kernel: 00000000: bd 2c e0 3d 00 00 00 11 87 0a 40 80 88 33 00 00  .,.=......@..3..
[ 9839.002840] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 3e b6 9b 44 01 2e 00 00 00 11 2a 01  ...?>..D......*.
[ 9839.002927] cachyos-x8664 kernel: 00000020: 20 00 00 00 00 00 00 20                           ...... 
[ 9849.846045] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (11)
[ 9849.846585] cachyos-x8664 kernel: 00000000: f6cf9d61 98993be6 80890691 000033b0  a....;.......3..
[ 9849.846623] cachyos-x8664 kernel: 00000010: 3ffe1e00 4540992a 187bb941 23e0fef0  ...?*.@EA.{....#
[ 9849.846677] cachyos-x8664 kernel: 00000020: 6e711a40 901f0901 e0ad38b3 4a68ceb1  @.qn.....8....hJ
[ 9849.846703] cachyos-x8664 kernel: 00000030: cb7462e5 2d2f015c                    .bt.\./-
[ 9849.846729] cachyos-x8664 kernel: 00000000: 61 9d cf f6 e6 3b 99 98 91 06 89 80 b0 33 00 00  a....;.......3..
[ 9849.846754] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 2a 99 40 45 41 b9 7b 18 f0 fe e0 23  ...?*.@EA.{....#
[ 9849.846779] cachyos-x8664 kernel: 00000020: 40 1a 71 6e 01 09 1f 90                          @.qn....
[ 9853.262018] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (5)
[ 9853.262555] cachyos-x8664 kernel: 00000000: 5701c89e 7698b5da 80f602a8 798170ff  ...W...v.....p.y
[ 9853.262601] cachyos-x8664 kernel: 00000010: cedcd5ae caf2ea84 95d37684 812a53bb  .........v...S*.
[ 9853.262628] cachyos-x8664 kernel: 00000020: 000009bd 20007fc2 000000df 0000000e  ....... ........
[ 9853.262655] cachyos-x8664 kernel: 00000030: 00000018 00000000                    ........
[ 9853.262684] cachyos-x8664 kernel: 00000000: 9e c8 01 57 da b5 98 76 a8 02 f6 80 ff 70 81 79  ...W...v.....p.y
[ 9853.262710] cachyos-x8664 kernel: 00000010: ae d5 dc ce 84 ea f2 ca 84 76 d3 95 bb 53 2a 81  .........v...S*.
[ 9853.262735] cachyos-x8664 kernel: 00000020: bd 09 00 00 c2 7f 00 20                          ....... 
[ 9853.310065] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (11)
[ 9853.310619] cachyos-x8664 kernel: 00000000: f47b49df b9c49c92 888e9e11 928f1de4  .I{.............
[ 9853.310669] cachyos-x8664 kernel: 00000010: fb1428b1 df354b98 133c7e7b 812a0000  .(...K5.{~<...*.
[ 9853.310698] cachyos-x8664 kernel: 00000020: 000009b7 20007fc2 000000df 0000000e  ....... ........
[ 9853.310722] cachyos-x8664 kernel: 00000030: 0000001a 00000000                    ........
[ 9853.310741] cachyos-x8664 kernel: 00000000: df 49 7b f4 92 9c c4 b9 11 9e 8e 88 e4 1d 8f 92  .I{.............
[ 9853.310771] cachyos-x8664 kernel: 00000010: b1 28 14 fb 98 4b 35 df 7b 7e 3c 13 00 00 2a 81  .(...K5.{~<...*.
[ 9853.310790] cachyos-x8664 kernel: 00000020: b7 09 00 00 c2 7f 00 20                          ....... 
[ 9853.739052] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (13)
[ 9853.739645] cachyos-x8664 kernel: 00000000: 9d1f427e 659de08e eced0266 000033af  ~B.....ef....3..
[ 9853.739680] cachyos-x8664 kernel: 00000010: 3ffe1e00 457aa256 afa5bd6b 6bb0569f  ...?V.zEk....V.k
[ 9853.739709] cachyos-x8664 kernel: 00000020: a56309ec 3812b969 13539eae f8eb42b2  ..c.i..8..S..B..
[ 9853.739749] cachyos-x8664 kernel: 00000030: f8a3df06 c9e07d75                    ....u}..
[ 9853.739790] cachyos-x8664 kernel: 00000000: 7e 42 1f 9d 8e e0 9d 65 66 02 ed ec af 33 00 00  ~B.....ef....3..
[ 9853.739846] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 56 a2 7a 45 6b bd a5 af 9f 56 b0 6b  ...?V.zEk....V.k
[ 9853.739886] cachyos-x8664 kernel: 00000020: ec 09 63 a5 69 b9 12 38                          ..c.i..8
[ 9866.346054] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (10)
[ 9866.346703] cachyos-x8664 kernel: 00000000: cdfd4a33 b893d00f e089da34 000033b0  3J......4....3..
[ 9866.346762] cachyos-x8664 kernel: 00000010: 3ffe1e00 463d2b31 00002a01 812a0900  ...?1+=F.*....*.
[ 9866.346806] cachyos-x8664 kernel: 00000020: 0000097b 20007fc2 000000dd 00000009  {...... ........
[ 9866.346840] cachyos-x8664 kernel: 00000030: 00000019 00000000                    ........
[ 9866.346879] cachyos-x8664 kernel: 00000000: 33 4a fd cd 0f d0 93 b8 34 da 89 e0 b0 33 00 00  3J......4....3..
[ 9866.346943] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 31 2b 3d 46 01 2a 00 00 00 09 2a 81  ...?1+=F.*....*.
[ 9866.346990] cachyos-x8664 kernel: 00000020: 7b 09 00 00 c2 7f 00 20                          {...... 
[ 9875.962029] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (9)
[ 9875.963800] cachyos-x8664 kernel: 00000000: fdb01dd4 8d6cfb78 2e24342b 6904bd7d  ....x.l.+4$.}..i
[ 9875.963864] cachyos-x8664 kernel: 00000010: ce836234 91dcddf5 00002901 012a1100  4b.......)....*.
[ 9875.963901] cachyos-x8664 kernel: 00000020: 00000020 20000000 000000d6 0000000e   ...... ........
[ 9875.963928] cachyos-x8664 kernel: 00000030: 0000001e 00000000                    ........
[ 9875.963997] cachyos-x8664 kernel: 00000000: d4 1d b0 fd 78 fb 6c 8d 2b 34 24 2e 7d bd 04 69  ....x.l.+4$.}..i
[ 9875.964062] cachyos-x8664 kernel: 00000010: 34 62 83 ce f5 dd dc 91 01 29 00 00 00 11 2a 01  4b.......)....*.
[ 9875.964130] cachyos-x8664 kernel: 00000020: 20 00 00 00 00 00 00 20                           ...... 
[ 9879.542028] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (9)
[ 9879.542682] cachyos-x8664 kernel: 00000000: cded0f3d a8c7c275 6c439f39 000033b0  =...u...9.Cl.3..
[ 9879.542724] cachyos-x8664 kernel: 00000010: 3ffe1e00 470679c2 c720d949 cf15f00b  ...?.y.GI. .....
[ 9879.542753] cachyos-x8664 kernel: 00000020: 1eb6ef50 d1eb60ce 7d82305b 3c9e36ae  P....`..[0.}.6.<
[ 9879.542782] cachyos-x8664 kernel: 00000030: 18d560bb 7770c694                    .`....pw
[ 9879.542805] cachyos-x8664 kernel: 00000000: 3d 0f ed cd 75 c2 c7 a8 39 9f 43 6c b0 33 00 00  =...u...9.Cl.3..
[ 9879.542831] cachyos-x8664 kernel: 00000010: 00 1e fe 3f c2 79 06 47 49 d9 20 c7 0b f0 15 cf  ...?.y.GI. .....
[ 9879.542855] cachyos-x8664 kernel: 00000020: 50 ef b6 1e ce 60 eb d1                          P....`..
[ 9881.748036] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (8)
[ 9881.748893] cachyos-x8664 kernel: 00000000: 842440d7 00032f16 80890f79 000033b0  .@$../..y....3..
[ 9881.749016] cachyos-x8664 kernel: 00000010: 3ffe1e00 4727ded6 f2bb4028 6c2e863b  ...?..'G(@..;..l
[ 9881.749080] cachyos-x8664 kernel: 00000020: f2c07d65 b0e6ea26 2ca68bd7 716f5dbc  e}..&......,.]oq
[ 9881.749128] cachyos-x8664 kernel: 00000030: 8c4e49ab 0471c73c                    .IN.<.q.
[ 9881.749180] cachyos-x8664 kernel: 00000000: d7 40 24 84 16 2f 03 00 79 0f 89 80 b0 33 00 00  .@$../..y....3..
[ 9881.749226] cachyos-x8664 kernel: 00000010: 00 1e fe 3f d6 de 27 47 28 40 bb f2 3b 86 2e 6c  ...?..'G(@..;..l
[ 9881.749270] cachyos-x8664 kernel: 00000020: 65 7d c0 f2 26 ea e6 b0                          e}..&...
[ 9884.239034] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (9)
[ 9884.239618] cachyos-x8664 kernel: 00000000: 25ce3a25 c6565f5c 80400187 00003388  %:.%\_V...@..3..
[ 9884.239657] cachyos-x8664 kernel: 00000010: 3ffe9e00 474e16ee 00002901 112a0000  ...?..NG.)....*.
[ 9884.239694] cachyos-x8664 kernel: 00000020: 00000014 20000000 000000e2 0000000e  ....... ........
[ 9884.239731] cachyos-x8664 kernel: 00000030: 0000001e 00000000                    ........
[ 9884.239750] cachyos-x8664 kernel: 00000000: 25 3a ce 25 5c 5f 56 c6 87 01 40 80 88 33 00 00  %:.%\_V...@..3..
[ 9884.239774] cachyos-x8664 kernel: 00000010: 00 9e fe 3f ee 16 4e 47 01 29 00 00 00 00 2a 11  ...?..NG.)....*.
[ 9884.239798] cachyos-x8664 kernel: 00000020: 14 00 00 00 00 00 00 20                          ....... 
[ 9887.449084] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (13)
[ 9887.450023] cachyos-x8664 kernel: 00000000: deff7058 f3d353f0 c14e0431 11c96c51  Xp...S..1.N.Ql..
[ 9887.450104] cachyos-x8664 kernel: 00000010: 3ffe1e00 477f1ace 16ad5e47 f519951c  ...?...GG^......
[ 9887.450156] cachyos-x8664 kernel: 00000020: 38937dfa 5554d69a 2de4b617 80fd8d23  .}.8..TU...-#...
[ 9887.450207] cachyos-x8664 kernel: 00000030: 3435f881 7e1bf0e5                    ..54...~
[ 9887.450232] cachyos-x8664 kernel: 00000000: 58 70 ff de f0 53 d3 f3 31 04 4e c1 51 6c c9 11  Xp...S..1.N.Ql..
[ 9887.450263] cachyos-x8664 kernel: 00000010: 00 1e fe 3f ce 1a 7f 47 47 5e ad 16 1c 95 19 f5  ...?...GG^......
[ 9887.450287] cachyos-x8664 kernel: 00000020: fa 7d 93 38 9a d6 54 55                          .}.8..TU
[ 9888.122051] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (10)
[ 9888.122789] cachyos-x8664 kernel: 00000000: e636c748 5dd4ae0a 6d46dcda 26c7a447  H.6....]..FmG..&
[ 9888.122848] cachyos-x8664 kernel: 00000010: f28486a4 51c0b4d1 a07aa588 d7f13cb3  .......Q..z..<..
[ 9888.122883] cachyos-x8664 kernel: 00000020: 6fbc3eea 4a704377 723e6d27 07d63497  .>.owCpJ'm>r.4..
[ 9888.122916] cachyos-x8664 kernel: 00000030: 70e70ced 2dc066e5                    ...p.f.-
[ 9888.122973] cachyos-x8664 kernel: 00000000: 48 c7 36 e6 0a ae d4 5d da dc 46 6d 47 a4 c7 26  H.6....]..FmG..&
[ 9888.123060] cachyos-x8664 kernel: 00000010: a4 86 84 f2 d1 b4 c0 51 88 a5 7a a0 b3 3c f1 d7  .......Q..z..<..
[ 9888.123110] cachyos-x8664 kernel: 00000020: ea 3e bc 6f 77 43 70 4a                          .>.owCpJ
[ 9890.511029] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (15)
[ 9890.512757] cachyos-x8664 kernel: 00000000: 3fee7ef9 c258bf15 8943a7eb 99da6176  .~.?..X...C.va..
[ 9890.512820] cachyos-x8664 kernel: 00000010: 7ad23564 e5dad312 affbac7f 012a1100  d5.z..........*.
[ 9890.512919] cachyos-x8664 kernel: 00000020: 00000020 20000000 000000d0 0000000c   ...... ........
[ 9890.512968] cachyos-x8664 kernel: 00000030: 00000023 00000000                    #.......
[ 9890.513087] cachyos-x8664 kernel: 00000000: f9 7e ee 3f 15 bf 58 c2 eb a7 43 89 76 61 da 99  .~.?..X...C.va..
[ 9890.513159] cachyos-x8664 kernel: 00000010: 64 35 d2 7a 12 d3 da e5 7f ac fb af 00 11 2a 01  d5.z..........*.
[ 9890.513211] cachyos-x8664 kernel: 00000020: 20 00 00 00 00 00 00 20                           ...... 
[ 9891.343315] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (4)
[ 9891.344052] cachyos-x8664 kernel: 00000000: 34ae9c86 cdb3f4d3 29952ee5 5c2eeca4  ...4.......)...\
[ 9891.344096] cachyos-x8664 kernel: 00000010: 2090ef87 47ba8793 3d316e64 9a2cf7b4  ... ...Gdn1=..,.
[ 9891.344150] cachyos-x8664 kernel: 00000020: 6c4d14c6 c82d3967 bddc198b a4ba576d  ..Mlg9-.....mW..
[ 9891.344191] cachyos-x8664 kernel: 00000030: d79b120d ec55b2f0                    ......U.
[ 9891.344222] cachyos-x8664 kernel: 00000000: 86 9c ae 34 d3 f4 b3 cd e5 2e 95 29 a4 ec 2e 5c  ...4.......)...\
[ 9891.344245] cachyos-x8664 kernel: 00000010: 87 ef 90 20 93 87 ba 47 64 6e 31 3d b4 f7 2c 9a  ... ...Gdn1=..,.
[ 9891.344371] cachyos-x8664 kernel: 00000020: c6 14 4d 6c 67 39 2d c8                          ..Mlg9-.
[ 9907.244107] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (12)
[ 9907.244967] cachyos-x8664 kernel: 00000000: c76f5ff1 f1816a5f a426503c 32afca04  ._o._j..<P&....2
[ 9907.245066] cachyos-x8664 kernel: 00000010: 374ab03b 0dce6465 cc2c3f0a 012a1100  ;.J7ed...?,...*.
[ 9907.245134] cachyos-x8664 kernel: 00000020: 00000020 20000000 000000d8 0000000f   ...... ........
[ 9907.245194] cachyos-x8664 kernel: 00000030: 0000001e 00000000                    ........
[ 9907.245260] cachyos-x8664 kernel: 00000000: f1 5f 6f c7 5f 6a 81 f1 3c 50 26 a4 04 ca af 32  ._o._j..<P&....2
[ 9907.245315] cachyos-x8664 kernel: 00000010: 3b b0 4a 37 65 64 ce 0d 0a 3f 2c cc 00 11 2a 01  ;.J7ed...?,...*.
[ 9907.245374] cachyos-x8664 kernel: 00000020: 20 00 00 00 00 00 00 20                           ...... 
[ 9925.130052] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (10)
[ 9925.130655] cachyos-x8664 kernel: 00000000: 04000000 52af3b63 efcaebc8 67bff503  ....c;.R.......g
[ 9925.130717] cachyos-x8664 kernel: 00000010: 3ffe1e00 49c03a96 dbf5ba5a 2f33359c  ...?.:.IZ....53/
[ 9925.130746] cachyos-x8664 kernel: 00000020: 3273eafc 819cbfbb 6084c57d 3c3adf8b  ..s2....}..`..:<
[ 9925.130776] cachyos-x8664 kernel: 00000030: 8521fa0c dc69465c                    ..!.\Fi.
[ 9925.130801] cachyos-x8664 kernel: 00000000: 00 00 00 04 63 3b af 52 c8 eb ca ef 03 f5 bf 67  ....c;.R.......g
[ 9925.130837] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 96 3a c0 49 5a ba f5 db 9c 35 33 2f  ...?.:.IZ....53/
[ 9925.130860] cachyos-x8664 kernel: 00000020: fc ea 73 32 bb bf 9c 81                          ..s2....
[ 9925.130893] cachyos-x8664 kernel: ------------[ cut here ]------------
[ 9925.130935] cachyos-x8664 kernel: 1
[ 9925.130963] cachyos-x8664 kernel: WARNING: net/mac80211/rx.c:896 at ieee80211_rx_list+0x1033/0x1040 [mac80211], CPU#0: irq/61-rtw_pci/631
[ 9925.131021] cachyos-x8664 kernel: Modules linked in: udp_diag tcp_diag inet_diag uinput snd_seq_dummy snd_hrtimer rfcomm snd_seq snd_seq_device ccm cmac algif_hash algif_skcipher af_alg bnep hp_bioscfg firmware_attributes_class amdgpu x86_pkg_temp_thermal intel_powerclamp coretemp rtw_8821ce(OE) kvm_intel snd_ctl_led snd_hda_codec_alc269 snd_hda_scodec_component rtw_8821c(OE) rmi_smbus snd_hda_codec_realtek_lib rtw_pci(OE) kvm snd_hda_codec_intelhdmi processor_thermal_device_pci_legacy snd_hda_codec_generic rmi_core drm_panel_backlight_quirks snd_hda_codec_hdmi rtw_core(OE) processor_thermal_device processor_thermal_power_floor irqbypass amdxcp processor_thermal_wt_hint snd_hda_intel btusb gpu_sched btmtk ghash_clmulni_intel processor_thermal_wt_req snd_hda_codec uvcvideo mac80211 aesni_intel vfat btbcm uvc fat rapl videobuf2_vmalloc snd_hda_core videobuf2_memops r8169 at24 btintel intel_cstate videobuf2_v4l2 processor_thermal_rfim snd_intel_dspcfg mei_hdcp mei_pxp intel_rapl_msr radeon btrtl spi_nor i2c_i801 intel_uncore
[ 9925.131303] cachyos-x8664 kernel:  processor_thermal_mbox realtek hp_wmi snd_intel_sdw_acpi wmi_bmof videobuf2_common drm_suballoc_helper snd_hwdep mtd sparse_keymap mdio_devres bluetooth cfg80211 drm_exec platform_temperature_control i2c_smbus psmouse pcspkr snd_pcm drm_ttm_helper libphy videodev i2c_mux processor_thermal_rapl intel_pch_thermal mei_me mc libarc4 rfkill snd_timer mdio_bus intel_rapl_common mei processor_thermal_soc_slider platform_profile snd int340x_thermal_zone intel_soc_dts_iosf soundcore intel_oc_wdt i2c_hid_acpi int3400_thermal i2c_hid acpi_thermal_rel wireless_hotkey acpi_pad mousedev joydev mac_hid tcp_bbr dm_mod ntsync i2c_dev crypto_user pkcs8_key_parser nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress i915 spi_intel_platform drm_buddy spi_intel intel_gtt ttm i2c_algo_bit drm_display_helper video cec lpc_ich wmi serio_raw
[ 9925.131366] cachyos-x8664 kernel: CPU: 0 UID: 0 PID: 631 Comm: irq/61-rtw_pci Tainted: G        W IOE       6.19.9-2-cachyos #1 PREEMPT(full)  02bb0ae94e3484fd95eb7c5534d2c734ca97d599
[ 9925.131402] cachyos-x8664 kernel: Tainted: [W]=WARN, [I]=FIRMWARE_WORKAROUND, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[ 9925.131431] cachyos-x8664 kernel: Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
[ 9925.131470] cachyos-x8664 kernel: RIP: 0010:ieee80211_rx_list+0x1033/0x1040 [mac80211]
[ 9925.131500] cachyos-x8664 kernel: Code: 0b e9 9f f1 ff ff 0f 0b e9 08 f6 ff ff 39 c8 0f 86 7a fa ff ff eb 89 4c 89 e7 e8 c8 e0 78 df 45 31 ff 4c 89 f3 e9 ba f6 ff ff <0f> 0b e9 e4 f5 ff ff e8 71 ff a2 e0 cc 90 90 90 90 90 90 90 90 90
[ 9925.131557] cachyos-x8664 kernel: RSP: 0018:ffffcfebc0003c38 EFLAGS: 00010297
[ 9925.131607] cachyos-x8664 kernel: RAX: 0000000000020000 RBX: 0000000000000000 RCX: 0000000000000004
[ 9925.131639] cachyos-x8664 kernel: RDX: 0000000000000000 RSI: ffff88e683593cd8 RDI: 0000000000000000
[ 9925.131668] cachyos-x8664 kernel: RBP: 00000000000001be R08: 0000000000000004 R09: 67bff503efcaebc8
[ 9925.131692] cachyos-x8664 kernel: R10: 67bff503efcaebc8 R11: 49c03a963ffe1e00 R12: ffff88e6fa730f00
[ 9925.131711] cachyos-x8664 kernel: R13: ffff88e6a13c0940 R14: ffffcfebc0003d30 R15: ffff88e6fa730f00
[ 9925.131741] cachyos-x8664 kernel: FS:  0000000000000000(0000) GS:ffff88e92eed3000(0000) knlGS:0000000000000000
[ 9925.131769] cachyos-x8664 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 9925.131803] cachyos-x8664 kernel: CR2: 00007f772eace000 CR3: 0000000021014006 CR4: 00000000003726f0
[ 9925.131827] cachyos-x8664 kernel: Call Trace:
[ 9925.131872] cachyos-x8664 kernel:  <IRQ>
[ 9925.131905] cachyos-x8664 kernel:  ? __alloc_skb+0x1f9/0x260
[ 9925.131925] cachyos-x8664 kernel:  ? __alloc_skb+0x10c/0x260
[ 9925.131948] cachyos-x8664 kernel:  ieee80211_rx_napi+0x51/0xe0 [mac80211 ff89233669c8b6a4dc82d34be183d0d6ad14e88c]
[ 9925.131968] cachyos-x8664 kernel:  rtw_pci_rx_napi+0x2fd/0x400 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9925.132017] cachyos-x8664 kernel:  rtw_pci_napi_poll+0x79/0x1d0 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9925.132051] cachyos-x8664 kernel:  net_rx_action+0x195/0x290
[ 9925.132079] cachyos-x8664 kernel:  ? psi_task_change+0x7d/0x310
[ 9925.132106] cachyos-x8664 kernel:  handle_softirqs+0x12d/0x1c0
[ 9925.132130] cachyos-x8664 kernel:  do_softirq+0x56/0x70
[ 9925.132149] cachyos-x8664 kernel:  </IRQ>
[ 9925.132172] cachyos-x8664 kernel:  <TASK>
[ 9925.132191] cachyos-x8664 kernel:  __local_bh_enable_ip.cold+0xc/0x11
[ 9925.132214] cachyos-x8664 kernel:  rtw_pci_interrupt_threadfn+0x270/0x360 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9925.132241] cachyos-x8664 kernel:  ? __pfx_irq_thread_fn+0x10/0x10
[ 9925.132265] cachyos-x8664 kernel:  irq_thread_fn+0x24/0x50
[ 9925.132302] cachyos-x8664 kernel:  irq_thread+0xbc/0x160
[ 9925.132352] cachyos-x8664 kernel:  ? __pfx_irq_thread_dtor+0x10/0x10
[ 9925.132401] cachyos-x8664 kernel:  ? __pfx_irq_thread+0x10/0x10
[ 9925.132434] cachyos-x8664 kernel:  kthread+0x205/0x280
[ 9925.132471] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 9925.132503] cachyos-x8664 kernel:  ret_from_fork+0x118/0x260
[ 9925.132531] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 9925.132552] cachyos-x8664 kernel:  ret_from_fork_asm+0x1a/0x30
[ 9925.132574] cachyos-x8664 kernel:  </TASK>
[ 9925.132606] cachyos-x8664 kernel: ---[ end trace 0000000000000000 ]---
[ 9925.163035] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (8)
[ 9925.163619] cachyos-x8664 kernel: 00000000: 95c0b362 dcbbea66 699d186b 0053ca98  b...f...k..i..S.
[ 9925.163648] cachyos-x8664 kernel: 00000010: 3ffe1e00 49c05d2a 00002801 112a1100  ...?*].I.(....*.
[ 9925.163667] cachyos-x8664 kernel: 00000020: 00000014 20000000 000000dc 00000008  ....... ........
[ 9925.163685] cachyos-x8664 kernel: 00000030: 0000001c 00000000                    ........
[ 9925.163717] cachyos-x8664 kernel: 00000000: 62 b3 c0 95 66 ea bb dc 6b 18 9d 69 98 ca 53 00  b...f...k..i..S.
[ 9925.163746] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 2a 5d c0 49 01 28 00 00 00 11 2a 11  ...?*].I.(....*.
[ 9925.163775] cachyos-x8664 kernel: 00000020: 14 00 00 00 00 00 00 20                          ....... 
[ 9925.189055] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (7)
[ 9925.189519] cachyos-x8664 kernel: 00000000: 3ddd2620 25bb6fdb e42e222a 93a86400   &.=.o.%*"...d..
[ 9925.189545] cachyos-x8664 kernel: 00000010: 3ffe1e00 49c0760c c2b817ac 2c9c56c3  ...?.v.I.....V.,
[ 9925.189564] cachyos-x8664 kernel: 00000020: 33713de4 120a6bcc 86a4fe46 d35dc136  .=q3.k..F...6.].
[ 9925.189601] cachyos-x8664 kernel: 00000030: cf8830d1 ad3f2a95                    .0...*?.
[ 9925.189628] cachyos-x8664 kernel: 00000000: 20 26 dd 3d db 6f bb 25 2a 22 2e e4 00 64 a8 93   &.=.o.%*"...d..
[ 9925.189659] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 0c 76 c0 49 ac 17 b8 c2 c3 56 9c 2c  ...?.v.I.....V.,
[ 9925.189682] cachyos-x8664 kernel: 00000020: e4 3d 71 33 cc 6b 0a 12                          .=q3.k..
[ 9925.189707] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (7)
[ 9925.190103] cachyos-x8664 kernel: 00000000: b75db375 4f50a885 66983760 cab1f97f  u.]...PO`7.f....
[ 9925.190138] cachyos-x8664 kernel: 00000010: 3ffe1e00 49c0760c 3790660e c0bf244f  ...?.v.I.f.7O$..
[ 9925.190164] cachyos-x8664 kernel: 00000020: fb2bfb6f 01b13730 b20fcb94 99aea6d1  o.+.07..........
[ 9925.190189] cachyos-x8664 kernel: 00000030: 968211b1 b355fd20                    .... .U.
[ 9925.190208] cachyos-x8664 kernel: 00000000: 75 b3 5d b7 85 a8 50 4f 60 37 98 66 7f f9 b1 ca  u.]...PO`7.f....
[ 9925.190240] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 0c 76 c0 49 0e 66 90 37 4f 24 bf c0  ...?.v.I.f.7O$..
[ 9925.190259] cachyos-x8664 kernel: 00000020: 6f fb 2b fb 30 37 b1 01                          o.+.07..
[ 9925.194038] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (12)
[ 9925.194526] cachyos-x8664 kernel: 00000000: dd27455b 6d9cbca6 ae77bef8 8f7e983b  [E'....m..w.;.~.
[ 9925.194590] cachyos-x8664 kernel: 00000010: 3ffe1e00 49c08461 63da0cbb 162b3a5f  ...?a..I...c_:+.
[ 9925.194621] cachyos-x8664 kernel: 00000020: 8973cca4 90d76d5f 220c7ffa 00ea56ed  ..s._m.....".V..
[ 9925.194650] cachyos-x8664 kernel: 00000030: 10b9cb5f e271b796                    _.....q.
[ 9925.194669] cachyos-x8664 kernel: 00000000: 5b 45 27 dd a6 bc 9c 6d f8 be 77 ae 3b 98 7e 8f  [E'....m..w.;.~.
[ 9925.194693] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 61 84 c0 49 bb 0c da 63 5f 3a 2b 16  ...?a..I...c_:+.
[ 9925.194722] cachyos-x8664 kernel: 00000020: a4 cc 73 89 5f 6d d7 90                          ..s._m..
[ 9925.603028] cachyos-x8664 kernel: ------------[ cut here ]------------
[ 9925.603140] cachyos-x8664 kernel: 1
[ 9925.603179] cachyos-x8664 kernel: WARNING: net/mac80211/rx.c:896 at ieee80211_rx_list+0x1033/0x1040 [mac80211], CPU#0: irq/61-rtw_pci/631
[ 9925.603237] cachyos-x8664 kernel: Modules linked in: udp_diag tcp_diag inet_diag uinput snd_seq_dummy snd_hrtimer rfcomm snd_seq snd_seq_device ccm cmac algif_hash algif_skcipher af_alg bnep hp_bioscfg firmware_attributes_class amdgpu x86_pkg_temp_thermal intel_powerclamp coretemp rtw_8821ce(OE) kvm_intel snd_ctl_led snd_hda_codec_alc269 snd_hda_scodec_component rtw_8821c(OE) rmi_smbus snd_hda_codec_realtek_lib rtw_pci(OE) kvm snd_hda_codec_intelhdmi processor_thermal_device_pci_legacy snd_hda_codec_generic rmi_core drm_panel_backlight_quirks snd_hda_codec_hdmi rtw_core(OE) processor_thermal_device processor_thermal_power_floor irqbypass amdxcp processor_thermal_wt_hint snd_hda_intel btusb gpu_sched btmtk ghash_clmulni_intel processor_thermal_wt_req snd_hda_codec uvcvideo mac80211 aesni_intel vfat btbcm uvc fat rapl videobuf2_vmalloc snd_hda_core videobuf2_memops r8169 at24 btintel intel_cstate videobuf2_v4l2 processor_thermal_rfim snd_intel_dspcfg mei_hdcp mei_pxp intel_rapl_msr radeon btrtl spi_nor i2c_i801 intel_uncore
[ 9925.603400] cachyos-x8664 kernel:  processor_thermal_mbox realtek hp_wmi snd_intel_sdw_acpi wmi_bmof videobuf2_common drm_suballoc_helper snd_hwdep mtd sparse_keymap mdio_devres bluetooth cfg80211 drm_exec platform_temperature_control i2c_smbus psmouse pcspkr snd_pcm drm_ttm_helper libphy videodev i2c_mux processor_thermal_rapl intel_pch_thermal mei_me mc libarc4 rfkill snd_timer mdio_bus intel_rapl_common mei processor_thermal_soc_slider platform_profile snd int340x_thermal_zone intel_soc_dts_iosf soundcore intel_oc_wdt i2c_hid_acpi int3400_thermal i2c_hid acpi_thermal_rel wireless_hotkey acpi_pad mousedev joydev mac_hid tcp_bbr dm_mod ntsync i2c_dev crypto_user pkcs8_key_parser nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress i915 spi_intel_platform drm_buddy spi_intel intel_gtt ttm i2c_algo_bit drm_display_helper video cec lpc_ich wmi serio_raw
[ 9925.603480] cachyos-x8664 kernel: CPU: 0 UID: 0 PID: 631 Comm: irq/61-rtw_pci Tainted: G        W IOE       6.19.9-2-cachyos #1 PREEMPT(full)  02bb0ae94e3484fd95eb7c5534d2c734ca97d599
[ 9925.603528] cachyos-x8664 kernel: Tainted: [W]=WARN, [I]=FIRMWARE_WORKAROUND, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[ 9925.603563] cachyos-x8664 kernel: Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
[ 9925.603606] cachyos-x8664 kernel: RIP: 0010:ieee80211_rx_list+0x1033/0x1040 [mac80211]
[ 9925.603641] cachyos-x8664 kernel: Code: 0b e9 9f f1 ff ff 0f 0b e9 08 f6 ff ff 39 c8 0f 86 7a fa ff ff eb 89 4c 89 e7 e8 c8 e0 78 df 45 31 ff 4c 89 f3 e9 ba f6 ff ff <0f> 0b e9 e4 f5 ff ff e8 71 ff a2 e0 cc 90 90 90 90 90 90 90 90 90
[ 9925.603689] cachyos-x8664 kernel: RSP: 0018:ffffcfebc0003c38 EFLAGS: 00010297
[ 9925.603716] cachyos-x8664 kernel: RAX: 0000000000020120 RBX: 0000000000000000 RCX: 0000000000000004
[ 9925.603748] cachyos-x8664 kernel: RDX: 0000000000000000 RSI: ffff88e6835916b2 RDI: 0000000000000000
[ 9925.603767] cachyos-x8664 kernel: RBP: 00000000000000fa R08: 0000000000000004 R09: 11b9d85106370040
[ 9925.603796] cachyos-x8664 kernel: R10: 004073f1dc050045 R11: ef7f11b9d8510637 R12: ffff88e685d3f700
[ 9925.603824] cachyos-x8664 kernel: R13: ffff88e6a13c0940 R14: ffffcfebc0003d30 R15: ffff88e685d3f700
[ 9925.603848] cachyos-x8664 kernel: FS:  0000000000000000(0000) GS:ffff88e92eed3000(0000) knlGS:0000000000000000
[ 9925.603872] cachyos-x8664 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 9925.603908] cachyos-x8664 kernel: CR2: 00007fa6946f0000 CR3: 0000000021014002 CR4: 00000000003726f0
[ 9925.603928] cachyos-x8664 kernel: Call Trace:
[ 9925.603955] cachyos-x8664 kernel:  <IRQ>
[ 9925.603975] cachyos-x8664 kernel:  ? __alloc_skb+0x1f9/0x260
[ 9925.603994] cachyos-x8664 kernel:  ? __alloc_skb+0x10c/0x260
[ 9925.604024] cachyos-x8664 kernel:  ieee80211_rx_napi+0x51/0xe0 [mac80211 ff89233669c8b6a4dc82d34be183d0d6ad14e88c]
[ 9925.604074] cachyos-x8664 kernel:  rtw_pci_rx_napi+0x2fd/0x400 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9925.604099] cachyos-x8664 kernel:  rtw_pci_napi_poll+0x79/0x1d0 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9925.604130] cachyos-x8664 kernel:  net_rx_action+0x195/0x290
[ 9925.604161] cachyos-x8664 kernel:  ? psi_task_change+0x7d/0x310
[ 9925.604184] cachyos-x8664 kernel:  handle_softirqs+0x12d/0x1c0
[ 9925.604215] cachyos-x8664 kernel:  do_softirq+0x56/0x70
[ 9925.604238] cachyos-x8664 kernel:  </IRQ>
[ 9925.604267] cachyos-x8664 kernel:  <TASK>
[ 9925.604296] cachyos-x8664 kernel:  __local_bh_enable_ip.cold+0xc/0x11
[ 9925.604320] cachyos-x8664 kernel:  rtw_pci_interrupt_threadfn+0x270/0x360 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9925.604350] cachyos-x8664 kernel:  ? __pfx_irq_thread_fn+0x10/0x10
[ 9925.604380] cachyos-x8664 kernel:  irq_thread_fn+0x24/0x50
[ 9925.604403] cachyos-x8664 kernel:  irq_thread+0xbc/0x160
[ 9925.604433] cachyos-x8664 kernel:  ? __pfx_irq_thread_dtor+0x10/0x10
[ 9925.604457] cachyos-x8664 kernel:  ? __pfx_irq_thread+0x10/0x10
[ 9925.604486] cachyos-x8664 kernel:  kthread+0x205/0x280
[ 9925.604517] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 9925.604551] cachyos-x8664 kernel:  ret_from_fork+0x118/0x260
[ 9925.604588] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 9925.604611] cachyos-x8664 kernel:  ret_from_fork_asm+0x1a/0x30
[ 9925.604636] cachyos-x8664 kernel:  </TASK>
[ 9925.604659] cachyos-x8664 kernel: ---[ end trace 0000000000000000 ]---
[ 9925.937029] cachyos-x8664 kernel: ------------[ cut here ]------------
[ 9925.937163] cachyos-x8664 kernel: 1
[ 9925.937210] cachyos-x8664 kernel: WARNING: net/mac80211/rx.c:896 at ieee80211_rx_list+0x1033/0x1040 [mac80211], CPU#0: irq/61-rtw_pci/631
[ 9925.937249] cachyos-x8664 kernel: Modules linked in: udp_diag tcp_diag inet_diag uinput snd_seq_dummy snd_hrtimer rfcomm snd_seq snd_seq_device ccm cmac algif_hash algif_skcipher af_alg bnep hp_bioscfg firmware_attributes_class amdgpu x86_pkg_temp_thermal intel_powerclamp coretemp rtw_8821ce(OE) kvm_intel snd_ctl_led snd_hda_codec_alc269 snd_hda_scodec_component rtw_8821c(OE) rmi_smbus snd_hda_codec_realtek_lib rtw_pci(OE) kvm snd_hda_codec_intelhdmi processor_thermal_device_pci_legacy snd_hda_codec_generic rmi_core drm_panel_backlight_quirks snd_hda_codec_hdmi rtw_core(OE) processor_thermal_device processor_thermal_power_floor irqbypass amdxcp processor_thermal_wt_hint snd_hda_intel btusb gpu_sched btmtk ghash_clmulni_intel processor_thermal_wt_req snd_hda_codec uvcvideo mac80211 aesni_intel vfat btbcm uvc fat rapl videobuf2_vmalloc snd_hda_core videobuf2_memops r8169 at24 btintel intel_cstate videobuf2_v4l2 processor_thermal_rfim snd_intel_dspcfg mei_hdcp mei_pxp intel_rapl_msr radeon btrtl spi_nor i2c_i801 intel_uncore
[ 9925.937332] cachyos-x8664 kernel:  processor_thermal_mbox realtek hp_wmi snd_intel_sdw_acpi wmi_bmof videobuf2_common drm_suballoc_helper snd_hwdep mtd sparse_keymap mdio_devres bluetooth cfg80211 drm_exec platform_temperature_control i2c_smbus psmouse pcspkr snd_pcm drm_ttm_helper libphy videodev i2c_mux processor_thermal_rapl intel_pch_thermal mei_me mc libarc4 rfkill snd_timer mdio_bus intel_rapl_common mei processor_thermal_soc_slider platform_profile snd int340x_thermal_zone intel_soc_dts_iosf soundcore intel_oc_wdt i2c_hid_acpi int3400_thermal i2c_hid acpi_thermal_rel wireless_hotkey acpi_pad mousedev joydev mac_hid tcp_bbr dm_mod ntsync i2c_dev crypto_user pkcs8_key_parser nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress i915 spi_intel_platform drm_buddy spi_intel intel_gtt ttm i2c_algo_bit drm_display_helper video cec lpc_ich wmi serio_raw
[ 9925.937402] cachyos-x8664 kernel: CPU: 0 UID: 0 PID: 631 Comm: irq/61-rtw_pci Tainted: G        W IOE       6.19.9-2-cachyos #1 PREEMPT(full)  02bb0ae94e3484fd95eb7c5534d2c734ca97d599
[ 9925.937447] cachyos-x8664 kernel: Tainted: [W]=WARN, [I]=FIRMWARE_WORKAROUND, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[ 9925.937480] cachyos-x8664 kernel: Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
[ 9925.937513] cachyos-x8664 kernel: RIP: 0010:ieee80211_rx_list+0x1033/0x1040 [mac80211]
[ 9925.937544] cachyos-x8664 kernel: Code: 0b e9 9f f1 ff ff 0f 0b e9 08 f6 ff ff 39 c8 0f 86 7a fa ff ff eb 89 4c 89 e7 e8 c8 e0 78 df 45 31 ff 4c 89 f3 e9 ba f6 ff ff <0f> 0b e9 e4 f5 ff ff e8 71 ff a2 e0 cc 90 90 90 90 90 90 90 90 90
[ 9925.937593] cachyos-x8664 kernel: RSP: 0018:ffffcfebc0003c38 EFLAGS: 00010297
[ 9925.937625] cachyos-x8664 kernel: RAX: 0000000000020100 RBX: 0000000000000000 RCX: 0000000000000004
[ 9925.937683] cachyos-x8664 kernel: RDX: 0000000000000000 RSI: ffff88e683592158 RDI: 0000000000000000
[ 9925.937738] cachyos-x8664 kernel: RBP: 0000000000000070 R08: 0000000000000004 R09: db79fb264a263ace
[ 9925.937769] cachyos-x8664 kernel: R10: db79fb264a263ace R11: 49ca95353ffe1e00 R12: ffff88e68b5a4100
[ 9925.937811] cachyos-x8664 kernel: R13: ffff88e6a13c0940 R14: ffffcfebc0003d30 R15: ffff88e68b5a4100
[ 9925.937849] cachyos-x8664 kernel: FS:  0000000000000000(0000) GS:ffff88e92eed3000(0000) knlGS:0000000000000000
[ 9925.937880] cachyos-x8664 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 9925.937911] cachyos-x8664 kernel: CR2: 000019f408725000 CR3: 000000014632c002 CR4: 00000000003726f0
[ 9925.937942] cachyos-x8664 kernel: Call Trace:
[ 9925.937979] cachyos-x8664 kernel:  <IRQ>
[ 9925.938036] cachyos-x8664 kernel:  ? __alloc_skb+0x1f9/0x260
[ 9925.938081] cachyos-x8664 kernel:  ? __alloc_skb+0x10c/0x260
[ 9925.938139] cachyos-x8664 kernel:  ieee80211_rx_napi+0x51/0xe0 [mac80211 ff89233669c8b6a4dc82d34be183d0d6ad14e88c]
[ 9925.938172] cachyos-x8664 kernel:  rtw_pci_rx_napi+0x2fd/0x400 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9925.938213] cachyos-x8664 kernel:  rtw_pci_napi_poll+0x79/0x1d0 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9925.938245] cachyos-x8664 kernel:  net_rx_action+0x195/0x290
[ 9925.938275] cachyos-x8664 kernel:  ? psi_task_change+0x7d/0x310
[ 9925.938305] cachyos-x8664 kernel:  handle_softirqs+0x12d/0x1c0
[ 9925.938335] cachyos-x8664 kernel:  do_softirq+0x56/0x70
[ 9925.938364] cachyos-x8664 kernel:  </IRQ>
[ 9925.938408] cachyos-x8664 kernel:  <TASK>
[ 9925.938438] cachyos-x8664 kernel:  __local_bh_enable_ip.cold+0xc/0x11
[ 9925.938468] cachyos-x8664 kernel:  rtw_pci_interrupt_threadfn+0x270/0x360 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9925.938508] cachyos-x8664 kernel:  ? __pfx_irq_thread_fn+0x10/0x10
[ 9925.938548] cachyos-x8664 kernel:  irq_thread_fn+0x24/0x50
[ 9925.938579] cachyos-x8664 kernel:  irq_thread+0xbc/0x160
[ 9925.938616] cachyos-x8664 kernel:  ? __pfx_irq_thread_dtor+0x10/0x10
[ 9925.938647] cachyos-x8664 kernel:  ? __pfx_irq_thread+0x10/0x10
[ 9925.938684] cachyos-x8664 kernel:  kthread+0x205/0x280
[ 9925.938723] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 9925.938754] cachyos-x8664 kernel:  ret_from_fork+0x118/0x260
[ 9925.938792] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 9925.938830] cachyos-x8664 kernel:  ret_from_fork_asm+0x1a/0x30
[ 9925.938869] cachyos-x8664 kernel:  </TASK>
[ 9925.938899] cachyos-x8664 kernel: ---[ end trace 0000000000000000 ]---
[ 9926.167049] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (7)
[ 9926.167519] cachyos-x8664 kernel: 00000000: fc78fe37 ed7ae57f 60d1abeb 2eb91a1d  7.x...z....`....
[ 9926.167543] cachyos-x8664 kernel: 00000010: 3ffe1e00 49cd9b89 754679d7 fe05fb09  ...?...I.yFu....
[ 9926.167583] cachyos-x8664 kernel: 00000020: d877776a 74056fef 57922451 43666a26  jww..o.tQ$.W&jfC
[ 9926.167611] cachyos-x8664 kernel: 00000030: 9c7f1e5c 0467783a                    \...:xg.
[ 9926.167637] cachyos-x8664 kernel: 00000000: 37 fe 78 fc 7f e5 7a ed eb ab d1 60 1d 1a b9 2e  7.x...z....`....
[ 9926.167656] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 89 9b cd 49 d7 79 46 75 09 fb 05 fe  ...?...I.yFu....
[ 9926.167680] cachyos-x8664 kernel: 00000020: 6a 77 77 d8 ef 6f 05 74                          jww..o.t
[ 9926.173022] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (14)
[ 9926.173578] cachyos-x8664 kernel: 00000000: f67c5396 29444b2e 6da770c3 30377e23  .S|..KD).p.m#~70
[ 9926.173619] cachyos-x8664 kernel: 00000010: 3ffe1e00 49cdb98c ecdee7ef bd57d9b1  ...?...I......W.
[ 9926.173647] cachyos-x8664 kernel: 00000020: 06b20045 03707ea6 0cb9c354 b767b6fe  E....~p.T.....g.
[ 9926.173673] cachyos-x8664 kernel: 00000030: 5457d41f 8f044107                    ..WT.A..
[ 9926.173692] cachyos-x8664 kernel: 00000000: 96 53 7c f6 2e 4b 44 29 c3 70 a7 6d 23 7e 37 30  .S|..KD).p.m#~70
[ 9926.173710] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 8c b9 cd 49 ef e7 de ec b1 d9 57 bd  ...?...I......W.
[ 9926.173729] cachyos-x8664 kernel: 00000020: 45 00 b2 06 a6 7e 70 03                          E....~p.
[ 9926.202105] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (11)
[ 9926.202850] cachyos-x8664 kernel: 00000000: 8ea838b2 b9bcdd4c 23cff204 4700098f  .8..L......#...G
[ 9926.202915] cachyos-x8664 kernel: 00000010: 3ffe1e00 49ce2e95 839bc68e 36712132  ...?...I....2!q6
[ 9926.202959] cachyos-x8664 kernel: 00000020: 1242f42e 7ccdd401 f80ad622 5e746f4a  ..B....|"...Jot^
[ 9926.202993] cachyos-x8664 kernel: 00000030: 396340d3 bb8b7af0                    .@c9.z..
[ 9926.203042] cachyos-x8664 kernel: 00000000: b2 38 a8 8e 4c dd bc b9 04 f2 cf 23 8f 09 00 47  .8..L......#...G
[ 9926.203075] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 95 2e ce 49 8e c6 9b 83 32 21 71 36  ...?...I....2!q6
[ 9926.203120] cachyos-x8664 kernel: 00000020: 2e f4 42 12 01 d4 cd 7c                          ..B....|
[ 9926.210030] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (9)
[ 9926.210713] cachyos-x8664 kernel: 00000000: bd0dd5fd 0fbde20d 45cf2abd 248639cb  .........*.E.9.$
[ 9926.210756] cachyos-x8664 kernel: 00000010: 3ffe1e00 49ce5e8f 00002901 812a0900  ...?.^.I.)....*.
[ 9926.210819] cachyos-x8664 kernel: 00000020: 00000972 20007fc2 000000dc 00000008  r...... ........
[ 9926.210853] cachyos-x8664 kernel: 00000030: 0000001b 00000000                    ........
[ 9926.210886] cachyos-x8664 kernel: 00000000: fd d5 0d bd 0d e2 bd 0f bd 2a cf 45 cb 39 86 24  .........*.E.9.$
[ 9926.210919] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 8f 5e ce 49 01 29 00 00 00 09 2a 81  ...?.^.I.)....*.
[ 9926.210952] cachyos-x8664 kernel: 00000020: 72 09 00 00 c2 7f 00 20                          r...... 
[ 9926.363025] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (13)
[ 9926.363560] cachyos-x8664 kernel: 00000000: 4ce80395 d88b3632 e74d169a be9e1d57  ...L26....M.W...
[ 9926.363588] cachyos-x8664 kernel: 00000010: 3ffe1e00 49d10a2b ed56151d 8b3919d5  ...?+..I..V...9.
[ 9926.363607] cachyos-x8664 kernel: 00000020: d2f76d32 f2b0d77a 9d339812 bfbcea53  2m..z.....3.S...
[ 9926.363646] cachyos-x8664 kernel: 00000030: 6c4229c2 7b9115a0                    .)Bl...{
[ 9926.363688] cachyos-x8664 kernel: 00000000: 95 03 e8 4c 32 36 8b d8 9a 16 4d e7 57 1d 9e be  ...L26....M.W...
[ 9926.363721] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 2b 0a d1 49 1d 15 56 ed d5 19 39 8b  ...?+..I..V...9.
[ 9926.363742] cachyos-x8664 kernel: 00000020: 32 6d f7 d2 7a d7 b0 f2                          2m..z...
[ 9926.365048] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (7)
[ 9926.365451] cachyos-x8664 kernel: 00000000: 05da26ac b587f0af 0aa2e765 f48d78f5  .&......e....x..
[ 9926.365475] cachyos-x8664 kernel: 00000010: 3ffe9e00 49d11a5c 00002701 012a0000  ...?\..I.'....*.
[ 9926.365496] cachyos-x8664 kernel: 00000020: 00000014 20000000 000000e2 0000000a  ....... ........
[ 9926.365537] cachyos-x8664 kernel: 00000030: 0000001c 00000000                    ........
[ 9926.365563] cachyos-x8664 kernel: 00000000: ac 26 da 05 af f0 87 b5 65 e7 a2 0a f5 78 8d f4  .&......e....x..
[ 9926.365589] cachyos-x8664 kernel: 00000010: 00 9e fe 3f 5c 1a d1 49 01 27 00 00 00 00 2a 01  ...?\..I.'....*.
[ 9926.365609] cachyos-x8664 kernel: 00000020: 14 00 00 00 00 00 00 20                          ....... 
[ 9926.422046] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (10)
[ 9926.422527] cachyos-x8664 kernel: 00000000: c55a224e d8371714 e94b82f0 ab1d98cf  N"Z...7...K.....
[ 9926.422552] cachyos-x8664 kernel: 00000010: 3ffe1e00 49d1fbc1 00002a01 812a0000  ...?...I.*....*.
[ 9926.422592] cachyos-x8664 kernel: 00000020: 000002a0 20007fc2 000000dc 00000009  ....... ........
[ 9926.422613] cachyos-x8664 kernel: 00000030: 0000001b 00000000                    ........
[ 9926.422639] cachyos-x8664 kernel: 00000000: 4e 22 5a c5 14 17 37 d8 f0 82 4b e9 cf 98 1d ab  N"Z...7...K.....
[ 9926.422671] cachyos-x8664 kernel: 00000010: 00 1e fe 3f c1 fb d1 49 01 2a 00 00 00 00 2a 81  ...?...I.*....*.
[ 9926.422691] cachyos-x8664 kernel: 00000020: a0 02 00 00 c2 7f 00 20                          ....... 
[ 9926.422728] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (8)
[ 9926.423109] cachyos-x8664 kernel: 00000000: 9df7e9cc 9f3de14b 4954225f 8a5263a5  ....K.=._"TI.cR.
[ 9926.423137] cachyos-x8664 kernel: 00000010: 3ffe1e00 49d1fffd 00002801 012a1100  ...?...I.(....*.
[ 9926.423168] cachyos-x8664 kernel: 00000020: 00000020 20000000 000000d6 00000009   ...... ........
[ 9926.423193] cachyos-x8664 kernel: 00000030: 0000001c 00000000                    ........
[ 9926.423212] cachyos-x8664 kernel: 00000000: cc e9 f7 9d 4b e1 3d 9f 5f 22 54 49 a5 63 52 8a  ....K.=._"TI.cR.
[ 9926.423241] cachyos-x8664 kernel: 00000010: 00 1e fe 3f fd ff d1 49 01 28 00 00 00 11 2a 01  ...?...I.(....*.
[ 9926.423267] cachyos-x8664 kernel: 00000020: 20 00 00 00 00 00 00 20                           ...... 
[ 9926.722028] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (11)
[ 9926.722721] cachyos-x8664 kernel: 00000000: 6e0e28b6 4e507227 0934c90c 0b43beb0  .(.n'rPN..4...C.
[ 9926.722769] cachyos-x8664 kernel: 00000010: 3ffe1e00 49d655f5 c51bce2a 25fc4449  ...?.U.I*...ID.%
[ 9926.722852] cachyos-x8664 kernel: 00000020: eb81fee9 d1a90a7a 7f9003d4 e90621b9  ....z........!..
[ 9926.722883] cachyos-x8664 kernel: 00000030: 2661b82d 0f84c168                    -.a&h...
[ 9926.722911] cachyos-x8664 kernel: 00000000: b6 28 0e 6e 27 72 50 4e 0c c9 34 09 b0 be 43 0b  .(.n'rPN..4...C.
[ 9926.722941] cachyos-x8664 kernel: 00000010: 00 1e fe 3f f5 55 d6 49 2a ce 1b c5 49 44 fc 25  ...?.U.I*...ID.%
[ 9926.722969] cachyos-x8664 kernel: 00000020: e9 fe 81 eb 7a 0a a9 d1                          ....z...
[ 9926.722994] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (13)
[ 9926.723450] cachyos-x8664 kernel: 00000000: 84985bd4 2c1f6507 62997193 31010501  .[...e.,.q.b...1
[ 9926.723484] cachyos-x8664 kernel: 00000010: 3ffe1e00 49d655f5 5d1c2add bfaf8c9d  ...?.U.I.*.]....
[ 9926.723509] cachyos-x8664 kernel: 00000020: 34d9b55b b6f23df7 2da83c8b 93d7e436  [..4.=...<.-6...
[ 9926.723534] cachyos-x8664 kernel: 00000030: 9a7aa4d6 1329c58f                    ..z...).
[ 9926.723554] cachyos-x8664 kernel: 00000000: d4 5b 98 84 07 65 1f 2c 93 71 99 62 01 05 01 31  .[...e.,.q.b...1
[ 9926.723573] cachyos-x8664 kernel: 00000010: 00 1e fe 3f f5 55 d6 49 dd 2a 1c 5d 9d 8c af bf  ...?.U.I.*.]....
[ 9926.723597] cachyos-x8664 kernel: 00000020: 5b b5 d9 34 f7 3d f2 b6                          [..4.=..
[ 9926.872038] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (14)
[ 9926.872527] cachyos-x8664 kernel: 00000000: 064f629e 8138c1df 0f631930 bd52edb8  .bO...8.0.c...R.
[ 9926.872575] cachyos-x8664 kernel: 00000010: 3ffe1e00 49d89f48 525e192e 1c7b91b3  ...?H..I..^R..{.
[ 9926.872608] cachyos-x8664 kernel: 00000020: e1ac052d b5c2f13f 2a1ef008 527cc5a3  -...?......*..|R
[ 9926.872628] cachyos-x8664 kernel: 00000030: 4091ba56 666e5d1b                    V..@.]nf
[ 9926.872646] cachyos-x8664 kernel: 00000000: 9e 62 4f 06 df c1 38 81 30 19 63 0f b8 ed 52 bd  .bO...8.0.c...R.
[ 9926.872665] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 48 9f d8 49 2e 19 5e 52 b3 91 7b 1c  ...?H..I..^R..{.
[ 9926.872692] cachyos-x8664 kernel: 00000020: 2d 05 ac e1 3f f1 c2 b5                          -...?...
[ 9927.193026] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (10)
[ 9927.193505] cachyos-x8664 kernel: 00000000: a69f3d68 670f1c5e 031a6963 ec35fd16  h=..^..gci....5.
[ 9927.193531] cachyos-x8664 kernel: 00000010: 3ffe1e00 49dd8b98 05ba6aad 189ac7d7  ...?...I.j......
[ 9927.193551] cachyos-x8664 kernel: 00000020: 9e5eb96d dc34c177 c08dfe07 fc78ce80  m.^.w.4.......x.
[ 9927.193591] cachyos-x8664 kernel: 00000030: 04145339 285d9c0b                    9S....](
[ 9927.193611] cachyos-x8664 kernel: 00000000: 68 3d 9f a6 5e 1c 0f 67 63 69 1a 03 16 fd 35 ec  h=..^..gci....5.
[ 9927.193630] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 98 8b dd 49 ad 6a ba 05 d7 c7 9a 18  ...?...I.j......
[ 9927.193655] cachyos-x8664 kernel: 00000020: 6d b9 5e 9e 77 c1 34 dc                          m.^.w.4.
[ 9927.193691] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (7)
[ 9927.194055] cachyos-x8664 kernel: 00000000: bdad5da0 e86d2e47 698c500e 7f5604dc  .]..G.m..P.i..V.
[ 9927.194077] cachyos-x8664 kernel: 00000010: 3ffe1e00 49dd9e36 00002701 012a1100  ...?6..I.'....*.
[ 9927.194095] cachyos-x8664 kernel: 00000020: 00000020 20000000 000000d6 00000009   ...... ........
[ 9927.194113] cachyos-x8664 kernel: 00000030: 0000001b 00000000                    ........
[ 9927.194141] cachyos-x8664 kernel: 00000000: a0 5d ad bd 47 2e 6d e8 0e 50 8c 69 dc 04 56 7f  .]..G.m..P.i..V.
[ 9927.194161] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 36 9e dd 49 01 27 00 00 00 11 2a 01  ...?6..I.'....*.
[ 9927.194180] cachyos-x8664 kernel: 00000020: 20 00 00 00 00 00 00 20                           ...... 
[ 9927.212028] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (13)
[ 9927.213136] cachyos-x8664 kernel: 00000000: acaa126c 461e9a51 4c90082b 4f7e5355  l...Q..F+..LUS~O
[ 9927.213181] cachyos-x8664 kernel: 00000010: 3ffe1e00 49dde0a8 cc6e2b4d 662af93c  ...?...IM+n.<.*f
[ 9927.213212] cachyos-x8664 kernel: 00000020: bb6af4e1 4855a351 df6fb634 439224f1  ..j.Q.UH4.o..$.C
[ 9927.213246] cachyos-x8664 kernel: 00000030: 4f3e0200 6c86af14                    ..>O...l
[ 9927.213279] cachyos-x8664 kernel: 00000000: 6c 12 aa ac 51 9a 1e 46 2b 08 90 4c 55 53 7e 4f  l...Q..F+..LUS~O
[ 9927.213315] cachyos-x8664 kernel: 00000010: 00 1e fe 3f a8 e0 dd 49 4d 2b 6e cc 3c f9 2a 66  ...?...IM+n.<.*f
[ 9927.213349] cachyos-x8664 kernel: 00000020: e1 f4 6a bb 51 a3 55 48                          ..j.Q.UH
[ 9927.224040] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (8)
[ 9927.224503] cachyos-x8664 kernel: 00000000: 1edb1eba d2b57bce 2b637915 8e2c2526  .....{...yc+&%,.
[ 9927.224554] cachyos-x8664 kernel: 00000010: 3ffe1e00 49de0f10 f1f8f233 cc2b6e82  ...?...I3....n+.
[ 9927.224576] cachyos-x8664 kernel: 00000020: f4e5ae63 fa854448 7f32fb26 f76a6dc4  c...HD..&.2..mj.
[ 9927.224604] cachyos-x8664 kernel: 00000030: 457e1b66 3efa45ca                    f.~E.E.>
[ 9927.224624] cachyos-x8664 kernel: 00000000: ba 1e db 1e ce 7b b5 d2 15 79 63 2b 26 25 2c 8e  .....{...yc+&%,.
[ 9927.224643] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 10 0f de 49 33 f2 f8 f1 82 6e 2b cc  ...?...I3....n+.
[ 9927.224669] cachyos-x8664 kernel: 00000020: 63 ae e5 f4 48 44 85 fa                          c...HD..
[ 9927.226022] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (10)
[ 9927.226475] cachyos-x8664 kernel: 00000000: 0773d0e6 b1c72e2b 48f4ced0 ac65b478  ..s.+......Hx.e.
[ 9927.226501] cachyos-x8664 kernel: 00000010: 3ffe1e00 49de1f1b fa896de7 6725f606  ...?...I.m....%g
[ 9927.226540] cachyos-x8664 kernel: 00000020: 276a0651 95329857 4a2476da e70f8346  Q.j'W.2..v$JF...
[ 9927.226570] cachyos-x8664 kernel: 00000030: 134a6a4c 2bc5a15e                    LjJ.^..+
[ 9927.226589] cachyos-x8664 kernel: 00000000: e6 d0 73 07 2b 2e c7 b1 d0 ce f4 48 78 b4 65 ac  ..s.+......Hx.e.
[ 9927.226614] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 1b 1f de 49 e7 6d 89 fa 06 f6 25 67  ...?...I.m....%g
[ 9927.226633] cachyos-x8664 kernel: 00000020: 51 06 6a 27 57 98 32 95                          Q.j'W.2.
[ 9927.245033] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (6)
[ 9927.247012] cachyos-x8664 kernel: 00000000: 258a70c5 8290b688 025c2774 9a842d3a  .p.%....t'\.:-..
[ 9927.247457] cachyos-x8664 kernel: 00000010: 3ffe1e00 49de6a01 a6d2768a b532fda4  ...?.j.I.v....2.
[ 9927.247505] cachyos-x8664 kernel: 00000020: e0bda82e d4c72df9 09876b6b 944ff7f3  .....-..kk....O.
[ 9927.247556] cachyos-x8664 kernel: 00000030: ed4dadef 929fe93a                    ..M.:...
[ 9927.247588] cachyos-x8664 kernel: 00000000: c5 70 8a 25 88 b6 90 82 74 27 5c 02 3a 2d 84 9a  .p.%....t'\.:-..
[ 9927.247628] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 01 6a de 49 8a 76 d2 a6 a4 fd 32 b5  ...?.j.I.v....2.
[ 9927.247825] cachyos-x8664 kernel: 00000020: 2e a8 bd e0 f9 2d c7 d4                          .....-..
[ 9928.204025] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (2)
[ 9928.205233] cachyos-x8664 kernel: 00000000: 95064d8e bdd0b6c1 83f7d74a bc00543a  .M......J...:T..
[ 9928.205296] cachyos-x8664 kernel: 00000010: 3ffe1e00 49ece559 72cf927d 42ccd544  ...?Y..I}..rD..B
[ 9928.205342] cachyos-x8664 kernel: 00000020: 1f49db42 5143e51f 9e7e1e25 a1de2a36  B.I...CQ%.~.6*..
[ 9928.205453] cachyos-x8664 kernel: 00000030: ce7beb7b 17b278d9                    {.{..x..
[ 9928.205537] cachyos-x8664 kernel: 00000000: 8e 4d 06 95 c1 b6 d0 bd 4a d7 f7 83 3a 54 00 bc  .M......J...:T..
[ 9928.205600] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 59 e5 ec 49 7d 92 cf 72 44 d5 cc 42  ...?Y..I}..rD..B
[ 9928.205659] cachyos-x8664 kernel: 00000020: 42 db 49 1f 1f e5 43 51                          B.I...CQ
[ 9928.538175] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (12)
[ 9928.539035] cachyos-x8664 kernel: 00000000: 24b88657 4f333b6c 299dbe1a ddaaec11  W..$l;3O...)....
[ 9928.539091] cachyos-x8664 kernel: 00000010: 3ffe1e00 49f1f717 f536a82c 0828e0ff  ...?...I,.6...(.
[ 9928.539136] cachyos-x8664 kernel: 00000020: 242245bd b9f6a58e a62a3519 dcc847ce  .E"$.....5*..G..
[ 9928.539169] cachyos-x8664 kernel: 00000030: 01ad9c39 56521f6a                    9...j.RV
[ 9928.539223] cachyos-x8664 kernel: 00000000: 57 86 b8 24 6c 3b 33 4f 1a be 9d 29 11 ec aa dd  W..$l;3O...)....
[ 9928.539282] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 17 f7 f1 49 2c a8 36 f5 ff e0 28 08  ...?...I,.6...(.
[ 9928.539317] cachyos-x8664 kernel: 00000020: bd 45 22 24 8e a5 f6 b9                          .E"$....
[ 9928.539373] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (2)
[ 9928.540252] cachyos-x8664 kernel: 00000000: 0f5cc9c9 c965725c 6b1826c4 ce9c244c  ..\.\re..&.kL$..
[ 9928.540360] cachyos-x8664 kernel: 00000010: 3ffe1e00 49f204c3 6210a434 c4a21004  ...?...I4..b....
[ 9928.540412] cachyos-x8664 kernel: 00000020: acd672a9 573e2b1b cd3a1651 69910dca  .r...+>WQ.:....i
[ 9928.540450] cachyos-x8664 kernel: 00000030: 5533993d 0c7ecbc6                    =.3U..~.
[ 9928.540518] cachyos-x8664 kernel: 00000000: c9 c9 5c 0f 5c 72 65 c9 c4 26 18 6b 4c 24 9c ce  ..\.\re..&.kL$..
[ 9928.540595] cachyos-x8664 kernel: 00000010: 00 1e fe 3f c3 04 f2 49 34 a4 10 62 04 10 a2 c4  ...?...I4..b....
[ 9928.540662] cachyos-x8664 kernel: 00000020: a9 72 d6 ac 1b 2b 3e 57                          .r...+>W
[ 9928.643021] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (10)
[ 9928.643566] cachyos-x8664 kernel: 00000000: 5c91e7f2 383b35c6 a4002fd9 fcbe05bc  ...\.5;8./......
[ 9928.643596] cachyos-x8664 kernel: 00000010: 3ffe1e00 49f3a19a ceab177a ff91bb68  ...?...Iz...h...
[ 9928.643618] cachyos-x8664 kernel: 00000020: 901c1f8f f86852c5 01507469 ab270e51  .....Rh.itP.Q.'.
[ 9928.643662] cachyos-x8664 kernel: 00000030: 3e81d0b3 8e777943                    ...>Cyw.
[ 9928.643685] cachyos-x8664 kernel: 00000000: f2 e7 91 5c c6 35 3b 38 d9 2f 00 a4 bc 05 be fc  ...\.5;8./......
[ 9928.643714] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 9a a1 f3 49 7a 17 ab ce 68 bb 91 ff  ...?...Iz...h...
[ 9928.643735] cachyos-x8664 kernel: 00000020: 8f 1f 1c 90 c5 52 68 f8                          .....Rh.
[ 9928.643762] cachyos-x8664 kernel: ------------[ cut here ]------------
[ 9928.643783] cachyos-x8664 kernel: 1
[ 9928.643802] cachyos-x8664 kernel: WARNING: net/mac80211/rx.c:896 at ieee80211_rx_list+0x1033/0x1040 [mac80211], CPU#0: irq/61-rtw_pci/631
[ 9928.643829] cachyos-x8664 kernel: Modules linked in: udp_diag tcp_diag inet_diag uinput snd_seq_dummy snd_hrtimer rfcomm snd_seq snd_seq_device ccm cmac algif_hash algif_skcipher af_alg bnep hp_bioscfg firmware_attributes_class amdgpu x86_pkg_temp_thermal intel_powerclamp coretemp rtw_8821ce(OE) kvm_intel snd_ctl_led snd_hda_codec_alc269 snd_hda_scodec_component rtw_8821c(OE) rmi_smbus snd_hda_codec_realtek_lib rtw_pci(OE) kvm snd_hda_codec_intelhdmi processor_thermal_device_pci_legacy snd_hda_codec_generic rmi_core drm_panel_backlight_quirks snd_hda_codec_hdmi rtw_core(OE) processor_thermal_device processor_thermal_power_floor irqbypass amdxcp processor_thermal_wt_hint snd_hda_intel btusb gpu_sched btmtk ghash_clmulni_intel processor_thermal_wt_req snd_hda_codec uvcvideo mac80211 aesni_intel vfat btbcm uvc fat rapl videobuf2_vmalloc snd_hda_core videobuf2_memops r8169 at24 btintel intel_cstate videobuf2_v4l2 processor_thermal_rfim snd_intel_dspcfg mei_hdcp mei_pxp intel_rapl_msr radeon btrtl spi_nor i2c_i801 intel_uncore
[ 9928.643880] cachyos-x8664 kernel:  processor_thermal_mbox realtek hp_wmi snd_intel_sdw_acpi wmi_bmof videobuf2_common drm_suballoc_helper snd_hwdep mtd sparse_keymap mdio_devres bluetooth cfg80211 drm_exec platform_temperature_control i2c_smbus psmouse pcspkr snd_pcm drm_ttm_helper libphy videodev i2c_mux processor_thermal_rapl intel_pch_thermal mei_me mc libarc4 rfkill snd_timer mdio_bus intel_rapl_common mei processor_thermal_soc_slider platform_profile snd int340x_thermal_zone intel_soc_dts_iosf soundcore intel_oc_wdt i2c_hid_acpi int3400_thermal i2c_hid acpi_thermal_rel wireless_hotkey acpi_pad mousedev joydev mac_hid tcp_bbr dm_mod ntsync i2c_dev crypto_user pkcs8_key_parser nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress i915 spi_intel_platform drm_buddy spi_intel intel_gtt ttm i2c_algo_bit drm_display_helper video cec lpc_ich wmi serio_raw
[ 9928.643915] cachyos-x8664 kernel: CPU: 0 UID: 0 PID: 631 Comm: irq/61-rtw_pci Tainted: G        W IOE       6.19.9-2-cachyos #1 PREEMPT(full)  02bb0ae94e3484fd95eb7c5534d2c734ca97d599
[ 9928.643935] cachyos-x8664 kernel: Tainted: [W]=WARN, [I]=FIRMWARE_WORKAROUND, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[ 9928.643954] cachyos-x8664 kernel: Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
[ 9928.643981] cachyos-x8664 kernel: RIP: 0010:ieee80211_rx_list+0x1033/0x1040 [mac80211]
[ 9928.644030] cachyos-x8664 kernel: Code: 0b e9 9f f1 ff ff 0f 0b e9 08 f6 ff ff 39 c8 0f 86 7a fa ff ff eb 89 4c 89 e7 e8 c8 e0 78 df 45 31 ff 4c 89 f3 e9 ba f6 ff ff <0f> 0b e9 e4 f5 ff ff e8 71 ff a2 e0 cc 90 90 90 90 90 90 90 90 90
[ 9928.644053] cachyos-x8664 kernel: RSP: 0000:ffffcfebc0003c38 EFLAGS: 00010297
[ 9928.644073] cachyos-x8664 kernel: RAX: 0000000000020100 RBX: 0000000000000000 RCX: 0000000000000004
[ 9928.644092] cachyos-x8664 kernel: RDX: 0000000000000000 RSI: ffff88e6d7bcd398 RDI: 0000000000000000
[ 9928.644110] cachyos-x8664 kernel: RBP: 00000000000000aa R08: 0000000000000004 R09: d70d65c6a7e74ee4
[ 9928.644138] cachyos-x8664 kernel: R10: d70d65c6a7e74ee4 R11: 49f3a19a3ffe1e00 R12: ffff88e7e9388900
[ 9928.644164] cachyos-x8664 kernel: R13: ffff88e6a13c0940 R14: ffffcfebc0003d30 R15: ffff88e7e9388900
[ 9928.644190] cachyos-x8664 kernel: FS:  0000000000000000(0000) GS:ffff88e92eed3000(0000) knlGS:0000000000000000
[ 9928.644215] cachyos-x8664 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 9928.644234] cachyos-x8664 kernel: CR2: 000019f408829000 CR3: 00000001e7460006 CR4: 00000000003726f0
[ 9928.644260] cachyos-x8664 kernel: Call Trace:
[ 9928.644279] cachyos-x8664 kernel:  <IRQ>
[ 9928.644296] cachyos-x8664 kernel:  ? __alloc_skb+0x1f9/0x260
[ 9928.644321] cachyos-x8664 kernel:  ? __alloc_skb+0x10c/0x260
[ 9928.644339] cachyos-x8664 kernel:  ieee80211_rx_napi+0x51/0xe0 [mac80211 ff89233669c8b6a4dc82d34be183d0d6ad14e88c]
[ 9928.644358] cachyos-x8664 kernel:  rtw_pci_rx_napi+0x2fd/0x400 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9928.644383] cachyos-x8664 kernel:  rtw_pci_napi_poll+0x79/0x1d0 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9928.644418] cachyos-x8664 kernel:  net_rx_action+0x195/0x290
[ 9928.644438] cachyos-x8664 kernel:  ? __wake_up+0x42/0xd0
[ 9928.644471] cachyos-x8664 kernel:  handle_softirqs+0x12d/0x1c0
[ 9928.644501] cachyos-x8664 kernel:  do_softirq+0x56/0x70
[ 9928.644543] cachyos-x8664 kernel:  </IRQ>
[ 9928.644586] cachyos-x8664 kernel:  <TASK>
[ 9928.644610] cachyos-x8664 kernel:  __local_bh_enable_ip.cold+0xc/0x11
[ 9928.644629] cachyos-x8664 kernel:  rtw_pci_interrupt_threadfn+0x270/0x360 [rtw_pci 8e4158c5f68a8bdf828972b62725e1ec6236cdc3]
[ 9928.644655] cachyos-x8664 kernel:  ? __pfx_irq_thread_fn+0x10/0x10
[ 9928.644673] cachyos-x8664 kernel:  irq_thread_fn+0x24/0x50
[ 9928.644693] cachyos-x8664 kernel:  irq_thread+0xbc/0x160
[ 9928.644717] cachyos-x8664 kernel:  ? __pfx_irq_thread_dtor+0x10/0x10
[ 9928.644741] cachyos-x8664 kernel:  ? __pfx_irq_thread+0x10/0x10
[ 9928.644759] cachyos-x8664 kernel:  kthread+0x205/0x280
[ 9928.644777] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 9928.644795] cachyos-x8664 kernel:  ret_from_fork+0x118/0x260
[ 9928.644821] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[ 9928.644862] cachyos-x8664 kernel:  ret_from_fork_asm+0x1a/0x30
[ 9928.644892] cachyos-x8664 kernel:  </TASK>
[ 9928.644922] cachyos-x8664 kernel: ---[ end trace 0000000000000000 ]---
[ 9929.206052] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (4)
[ 9929.206607] cachyos-x8664 kernel: 00000000: dd41e6c2 b3d5933d 8e5dd78a b17e841f  ..A.=.....]...~.
[ 9929.206645] cachyos-x8664 kernel: 00000010: 3ffe1e00 49fbb2d5 bc0ec403 026b5b81  ...?...I.....[k.
[ 9929.206678] cachyos-x8664 kernel: 00000020: 46341de5 1b0cf21d b158f973 29534a11  ..4F....s.X..JS)
[ 9929.206724] cachyos-x8664 kernel: 00000030: 366d9443 02876701                    C.m6.g..
[ 9929.206758] cachyos-x8664 kernel: 00000000: c2 e6 41 dd 3d 93 d5 b3 8a d7 5d 8e 1f 84 7e b1  ..A.=.....]...~.
[ 9929.206787] cachyos-x8664 kernel: 00000010: 00 1e fe 3f d5 b2 fb 49 03 c4 0e bc 81 5b 6b 02  ...?...I.....[k.
[ 9929.206812] cachyos-x8664 kernel: 00000020: e5 1d 34 46 1d f2 0c 1b                          ..4F....
[ 9929.815090] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (15)
[ 9929.815609] cachyos-x8664 kernel: 00000000: ec565ef9 5a69b84e c6972cd7 3cee5e9f  .^V.N.iZ.,...^.<
[ 9929.815656] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a053147 f43130ef 27e7856e  ...?G1.J.01.n..'
[ 9929.815679] cachyos-x8664 kernel: 00000020: 65644980 f9ebb599 4ab2e7ca 9d1bdfb0  .Ide.......J....
[ 9929.815705] cachyos-x8664 kernel: 00000030: a70f9d05 35924b64                    ....dK.5
[ 9929.815726] cachyos-x8664 kernel: 00000000: f9 5e 56 ec 4e b8 69 5a d7 2c 97 c6 9f 5e ee 3c  .^V.N.iZ.,...^.<
[ 9929.815775] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 47 31 05 4a ef 30 31 f4 6e 85 e7 27  ...?G1.J.01.n..'
[ 9929.815809] cachyos-x8664 kernel: 00000020: 80 49 64 65 99 b5 eb f9                          .Ide....
[ 9930.165018] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (7)
[ 9930.165513] cachyos-x8664 kernel: 00000000: d681e7db e53c2a34 c5cd360e 823b078d  ....4*<..6....;.
[ 9930.165540] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a0ac5d2 833724fb 41d49bb1  ...?...J.$7....A
[ 9930.165560] cachyos-x8664 kernel: 00000020: 53c14a4f ca825f00 d2a23149 b6e5b7c0  OJ.S._..I1......
[ 9930.165579] cachyos-x8664 kernel: 00000030: 5493dd08 5868880f                    ...T..hX
[ 9930.165598] cachyos-x8664 kernel: 00000000: db e7 81 d6 34 2a 3c e5 0e 36 cd c5 8d 07 3b 82  ....4*<..6....;.
[ 9930.165618] cachyos-x8664 kernel: 00000010: 00 1e fe 3f d2 c5 0a 4a fb 24 37 83 b1 9b d4 41  ...?...J.$7....A
[ 9930.165655] cachyos-x8664 kernel: 00000020: 4f 4a c1 53 00 5f 82 ca                          OJ.S._..
[ 9931.088049] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (9)
[ 9931.088535] cachyos-x8664 kernel: 00000000: 6fe06b6d 184af02b 8f569970 5cd576d7  mk.o+.J.p.V..v.\
[ 9931.088583] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a188c9b 4989e6fa 7c4d9d67  ...?...J...Ig.M|
[ 9931.088605] cachyos-x8664 kernel: 00000020: 749a21b2 175f9aa6 aa958589 76e34636  .!.t.._.....6F.v
[ 9931.088637] cachyos-x8664 kernel: 00000030: 0e221e13 1f3534a7                    .."..45.
[ 9931.088656] cachyos-x8664 kernel: 00000000: 6d 6b e0 6f 2b f0 4a 18 70 99 56 8f d7 76 d5 5c  mk.o+.J.p.V..v.\
[ 9931.088675] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 9b 8c 18 4a fa e6 89 49 67 9d 4d 7c  ...?...J...Ig.M|
[ 9931.088699] cachyos-x8664 kernel: 00000020: b2 21 9a 74 a6 9a 5f 17                          .!.t.._.
[ 9933.997023] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (12)
[ 9933.997696] cachyos-x8664 kernel: 00000000: 5d67df65 2100b004 a0890cc4 000033b0  e.g]...!.....3..
[ 9933.997740] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a44414a 6d893c63 b2c82c87  ...?JADJc<.m.,..
[ 9933.997799] cachyos-x8664 kernel: 00000020: fb5233c2 9922020e 5453d055 45d7dfb1  .3R...".U.ST...E
[ 9933.997841] cachyos-x8664 kernel: 00000030: 56fd2836 c804820a                    6(.V....
[ 9933.997872] cachyos-x8664 kernel: 00000000: 65 df 67 5d 04 b0 00 21 c4 0c 89 a0 b0 33 00 00  e.g]...!.....3..
[ 9933.997903] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 4a 41 44 4a 63 3c 89 6d 87 2c c8 b2  ...?JADJc<.m.,..
[ 9933.997933] cachyos-x8664 kernel: 00000020: c2 33 52 fb 0e 02 22 99                          .3R...".
[ 9937.622038] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (8)
[ 9937.622561] cachyos-x8664 kernel: 00000000: de27d473 09f008d7 4ddc1cdd 18f4fff0  s.'........M....
[ 9937.622588] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a7c6807 2f48130e 8bcc3d95  ...?.h|J..H/.=..
[ 9937.622608] cachyos-x8664 kernel: 00000020: 593d4251 54dfecf5 db3a99ce 565483d2  QB=Y...T..:...TV
[ 9937.622628] cachyos-x8664 kernel: 00000030: 30e3a3cc c487f486                    ...0....
[ 9937.622646] cachyos-x8664 kernel: 00000000: 73 d4 27 de d7 08 f0 09 dd 1c dc 4d f0 ff f4 18  s.'........M....
[ 9937.622665] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 07 68 7c 4a 0e 13 48 2f 95 3d cc 8b  ...?.h|J..H/.=..
[ 9937.622707] cachyos-x8664 kernel: 00000020: 51 42 3d 59 f5 ec df 54                          QB=Y...T
[ 9938.056019] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (3)
[ 9938.056809] cachyos-x8664 kernel: 00000000: e6a47b12 f34842bc afbf35a5 dc7e1cac  .{...BH..5....~.
[ 9938.056906] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a80f5a8 fd134218 d56b9484  ...?...J.B....k.
[ 9938.056986] cachyos-x8664 kernel: 00000020: ce5a7513 1216471c edf7014d 8ca6a2e3  .uZ..G..M.......
[ 9938.057070] cachyos-x8664 kernel: 00000030: 217a89ac 7d121efe                    ..z!...}
[ 9938.057132] cachyos-x8664 kernel: 00000000: 12 7b a4 e6 bc 42 48 f3 a5 35 bf af ac 1c 7e dc  .{...BH..5....~.
[ 9938.057188] cachyos-x8664 kernel: 00000010: 00 1e fe 3f a8 f5 80 4a 18 42 13 fd 84 94 6b d5  ...?...J.B....k.
[ 9938.057245] cachyos-x8664 kernel: 00000020: 13 75 5a ce 1c 47 16 12                          .uZ..G..
[ 9939.179151] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (2)
[ 9939.180057] cachyos-x8664 kernel: 00000000: 7faa0f34 1b112611 8dfb35cb c70f74f3  4....&...5...t..
[ 9939.180133] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a91d971 724f1e16 c27a4faa  ...?q..J..Or.Oz.
[ 9939.180203] cachyos-x8664 kernel: 00000020: e17544fb 75352591 fd5aa32a 6a6490bd  .Du..%5u*.Z...dj
[ 9939.180272] cachyos-x8664 kernel: 00000030: bf294a5c ecc4cff3                    \J).....
[ 9939.180325] cachyos-x8664 kernel: 00000000: 34 0f aa 7f 11 26 11 1b cb 35 fb 8d f3 74 0f c7  4....&...5...t..
[ 9939.180370] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 71 d9 91 4a 16 1e 4f 72 aa 4f 7a c2  ...?q..J..Or.Oz.
[ 9939.180423] cachyos-x8664 kernel: 00000020: fb 44 75 e1 91 25 35 75                          .Du..%5u
[ 9939.182507] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (13)
[ 9939.185813] cachyos-x8664 kernel: 00000000: 9f61e237 34107384 cb29fed8 0c1881db  7.a..s.4..).....
[ 9939.186110] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a91e4a8 1dcbefae dd9bc081  ...?...J........
[ 9939.186169] cachyos-x8664 kernel: 00000020: 6d68b92c 50e20517 eb4c5292 b089147d  ,.hm...P.RL.}...
[ 9939.186248] cachyos-x8664 kernel: 00000030: 1e609c40 9b6666fa                    @.`..ff.
[ 9939.186524] cachyos-x8664 kernel: 00000000: 37 e2 61 9f 84 73 10 34 d8 fe 29 cb db 81 18 0c  7.a..s.4..).....
[ 9939.186606] cachyos-x8664 kernel: 00000010: 00 1e fe 3f a8 e4 91 4a ae ef cb 1d 81 c0 9b dd  ...?...J........
[ 9939.186666] cachyos-x8664 kernel: 00000020: 2c b9 68 6d 17 05 e2 50                          ,.hm...P
[ 9939.231026] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (8)
[ 9939.231596] cachyos-x8664 kernel: 00000000: 5e6ad48d ffda4899 24a64557 4b9ec0fc  ..j^.H..WE.$...K
[ 9939.231638] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a92b38c 6808856d 215d48ba  ...?...Jm..h.H]!
[ 9939.231664] cachyos-x8664 kernel: 00000020: 37c0a6e2 015d5812 53f06e1e ba210059  ...7.X]..n.SY.!.
[ 9939.231700] cachyos-x8664 kernel: 00000030: 8ed9393a 791b66c7                    :9...f.y
[ 9939.231735] cachyos-x8664 kernel: 00000000: 8d d4 6a 5e 99 48 da ff 57 45 a6 24 fc c0 9e 4b  ..j^.H..WE.$...K
[ 9939.231760] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 8c b3 92 4a 6d 85 08 68 ba 48 5d 21  ...?...Jm..h.H]!
[ 9939.231793] cachyos-x8664 kernel: 00000020: e2 a6 c0 37 12 58 5d 01                          ...7.X].
[ 9939.593966] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (4)
[ 9939.595141] cachyos-x8664 kernel: 00000000: b638b611 b05fb465 49d6ba72 82c04adf  ..8.e._.r..I.J..
[ 9939.595237] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a97e0ea b2b4833b e69841bb  ...?...J;....A..
[ 9939.595292] cachyos-x8664 kernel: 00000020: 6b15753f e7b52a52 5795b861 ad5eaf4a  ?u.kR*..a..WJ.^.
[ 9939.595352] cachyos-x8664 kernel: 00000030: 8c898d10 38e6e1f0                    .......8
[ 9939.595395] cachyos-x8664 kernel: 00000000: 11 b6 38 b6 65 b4 5f b0 72 ba d6 49 df 4a c0 82  ..8.e._.r..I.J..
[ 9939.595438] cachyos-x8664 kernel: 00000010: 00 1e fe 3f ea e0 97 4a 3b 83 b4 b2 bb 41 98 e6  ...?...J;....A..
[ 9939.595480] cachyos-x8664 kernel: 00000020: 3f 75 15 6b 52 2a b5 e7                          ?u.kR*..
[ 9939.595527] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (4)
[ 9939.596547] cachyos-x8664 kernel: 00000000: e5f572fe 22d8b1a8 a97e45f3 e6431c04  .r.....".E~...C.
[ 9939.596640] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a97ee26 eccc34cd 809a4479  ...?&..J.4..yD..
[ 9939.596690] cachyos-x8664 kernel: 00000020: c985d764 96b59730 6e4c9311 53335a48  d...0.....LnHZ3S
[ 9939.596733] cachyos-x8664 kernel: 00000030: aae09612 30656dd6                    .....me0
[ 9939.596790] cachyos-x8664 kernel: 00000000: fe 72 f5 e5 a8 b1 d8 22 f3 45 7e a9 04 1c 43 e6  .r.....".E~...C.
[ 9939.596832] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 26 ee 97 4a cd 34 cc ec 79 44 9a 80  ...?&..J.4..yD..
[ 9939.596868] cachyos-x8664 kernel: 00000020: 64 d7 85 c9 30 97 b5 96                          d...0...
[ 9939.596909] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (3)
[ 9939.597575] cachyos-x8664 kernel: 00000000: c5e1fbcb c8df2a98 4f9fa869 5841bde8  .....*..i..O..AX
[ 9939.597615] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a97fc5b ec8c63ef 0cd99599  ...?[..J.c......
[ 9939.597660] cachyos-x8664 kernel: 00000020: 5cca09b2 1237ca21 0c5c17ce cce056e2  ...\!.7...\..V..
[ 9939.597696] cachyos-x8664 kernel: 00000030: 2e01c0e3 8627d8b7                    ......'.
[ 9939.613518] cachyos-x8664 kernel: 00000000: cb fb e1 c5 98 2a df c8 69 a8 9f 4f e8 bd 41 58  .....*..i..O..AX
[ 9939.613753] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 5b fc 97 4a ef 63 8c ec 99 95 d9 0c  ...?[..J.c......
[ 9939.613811] cachyos-x8664 kernel: 00000020: b2 09 ca 5c 21 ca 37 12                          ...\!.7.
[ 9939.974042] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (10)
[ 9939.974582] cachyos-x8664 kernel: 00000000: d4b11304 dfede746 ec27578c 2dcf02b0  ....F....W'....-
[ 9939.974620] cachyos-x8664 kernel: 00000010: 3ffe1e00 4a9dd2fc 16e0867a f1342795  ...?...Jz....'4.
[ 9939.974650] cachyos-x8664 kernel: 00000020: aeca6a96 210f7a65 4fbc5d85 113a7fe3  .j..ez.!.].O..:.
[ 9939.974679] cachyos-x8664 kernel: 00000030: d73a1512 590eefb5                    ..:....Y
[ 9939.974702] cachyos-x8664 kernel: 00000000: 04 13 b1 d4 46 e7 ed df 8c 57 27 ec b0 02 cf 2d  ....F....W'....-
[ 9939.974721] cachyos-x8664 kernel: 00000010: 00 1e fe 3f fc d2 9d 4a 7a 86 e0 16 95 27 34 f1  ...?...Jz....'4.
[ 9939.974746] cachyos-x8664 kernel: 00000020: 96 6a ca ae 65 7a 0f 21                          .j..ez.!
[ 9941.593048] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (2)
[ 9941.594734] cachyos-x8664 kernel: 00000000: 56ab51d8 dbc5eaed e66e2186 867729a7  .Q.V.....!n..)w.
[ 9941.594830] cachyos-x8664 kernel: 00000010: 3ffe1e00 4ab7098a e7d21dbf 5f44fc1a  ...?...J......D_
[ 9941.594874] cachyos-x8664 kernel: 00000020: 5313ad37 c70bfb4e d9ec1b3f 3f976bef  7..SN...?....k.?
[ 9941.594928] cachyos-x8664 kernel: 00000030: a6892256 4b964d70                    V"..pM.K
[ 9941.594974] cachyos-x8664 kernel: 00000000: d8 51 ab 56 ed ea c5 db 86 21 6e e6 a7 29 77 86  .Q.V.....!n..)w.
[ 9941.595035] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 8a 09 b7 4a bf 1d d2 e7 1a fc 44 5f  ...?...J......D_
[ 9941.595112] cachyos-x8664 kernel: 00000020: 37 ad 13 53 4e fb 0b c7                          7..SN...
[ 9945.116091] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (15)
[ 9945.117094] cachyos-x8664 kernel: 00000000: 649dc214 d4a16b10 41283a16 4d4bcf60  ...d.k...:(A`.KM
[ 9945.117174] cachyos-x8664 kernel: 00000010: 3ffe1e00 4aeec0d4 d25fefef fb69b382  ...?...J.._...i.
[ 9945.117206] cachyos-x8664 kernel: 00000020: e3ed1b44 9f1b40f0 ad8ac696 9ce10ec3  D....@..........
[ 9945.117236] cachyos-x8664 kernel: 00000030: ae0d3b70 eecb2551                    p;..Q%..
[ 9945.117470] cachyos-x8664 kernel: 00000000: 14 c2 9d 64 10 6b a1 d4 16 3a 28 41 60 cf 4b 4d  ...d.k...:(A`.KM
[ 9945.117504] cachyos-x8664 kernel: 00000010: 00 1e fe 3f d4 c0 ee 4a ef ef 5f d2 82 b3 69 fb  ...?...J.._...i.
[ 9945.117545] cachyos-x8664 kernel: 00000020: 44 1b ed e3 f0 40 1b 9f                          D....@..
[ 9946.598023] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (7)
[ 9946.598812] cachyos-x8664 kernel: 00000000: 0d6df800 e3464d32 a0890ed3 000033b0  ..m.2MF......3..
[ 9946.598921] cachyos-x8664 kernel: 00000010: 3ffe1e00 4b05930e 63f40738 c11039c3  ...?...K8..c.9..
[ 9946.598967] cachyos-x8664 kernel: 00000020: 667b1cbd 254f6f7c c88c614a 63d1684b  ..{f|oO%Ja..Kh.c
[ 9946.599020] cachyos-x8664 kernel: 00000030: 1ca4686c e4055a97                    lh...Z..
[ 9946.599050] cachyos-x8664 kernel: 00000000: 00 f8 6d 0d 32 4d 46 e3 d3 0e 89 a0 b0 33 00 00  ..m.2MF......3..
[ 9946.599077] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 0e 93 05 4b 38 07 f4 63 c3 39 10 c1  ...?...K8..c.9..
[ 9946.599103] cachyos-x8664 kernel: 00000020: bd 1c 7b 66 7c 6f 4f 25                          ..{f|oO%
[ 9948.522029] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (12)
[ 9948.522711] cachyos-x8664 kernel: 00000000: 641e8dca b8a85fb6 e08906bd 000033b0  ...d._.......3..
[ 9948.522778] cachyos-x8664 kernel: 00000010: 3ffe1e00 4b22ada7 6e0e184c 50aa9bae  ...?.."KL..n...P
[ 9948.522801] cachyos-x8664 kernel: 00000020: 87248539 50b66687 63e15a37 6cba8926  9.$..f.P7Z.c&..l
[ 9948.522827] cachyos-x8664 kernel: 00000030: 11a91236 5194cf1d                    6......Q
[ 9948.522851] cachyos-x8664 kernel: 00000000: ca 8d 1e 64 b6 5f a8 b8 bd 06 89 e0 b0 33 00 00  ...d._.......3..
[ 9948.522871] cachyos-x8664 kernel: 00000010: 00 1e fe 3f a7 ad 22 4b 4c 18 0e 6e ae 9b aa 50  ...?.."KL..n...P
[ 9948.522889] cachyos-x8664 kernel: 00000020: 39 85 24 87 87 66 b6 50                          9.$..f.P
[ 9964.095408] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (13)
[ 9964.096865] cachyos-x8664 kernel: 00000000: 67d811ae 0804eb20 e1060cc2 18213adf  ...g ........:!.
[ 9964.096941] cachyos-x8664 kernel: 00000010: 3ffe1e00 4c108e16 cdc77076 180661a8  ...?...Lvp...a..
[ 9964.096974] cachyos-x8664 kernel: 00000020: c9708c4c c3da1877 88ddf980 729988b0  L.p.w..........r
[ 9964.097162] cachyos-x8664 kernel: 00000030: 2a0d2dc0 8f9f0e8d                    .-.*....
[ 9964.097199] cachyos-x8664 kernel: 00000000: ae 11 d8 67 20 eb 04 08 c2 0c 06 e1 df 3a 21 18  ...g ........:!.
[ 9964.097251] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 16 8e 10 4c 76 70 c7 cd a8 61 06 18  ...?...Lvp...a..
[ 9964.097285] cachyos-x8664 kernel: 00000020: 4c 8c 70 c9 77 18 da c3                          L.p.w...
[ 9969.903032] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (5)
[ 9969.903679] cachyos-x8664 kernel: 00000000: 3f2e72b6 1d61a98e 6482a885 d3b56971  .r.?..a....dqi..
[ 9969.903708] cachyos-x8664 kernel: 00000010: 3ffe1e00 4c693834 2571553d eb86711a  ...?48iL=Uq%.q..
[ 9969.903728] cachyos-x8664 kernel: 00000020: 97aa44e3 18855af1 d75b9cd9 2043d49f  .D...Z....[...C 
[ 9969.903746] cachyos-x8664 kernel: 00000030: d0e82d30 9f774f87                    0-...Ow.
[ 9969.903765] cachyos-x8664 kernel: 00000000: b6 72 2e 3f 8e a9 61 1d 85 a8 82 64 71 69 b5 d3  .r.?..a....dqi..
[ 9969.903783] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 34 38 69 4c 3d 55 71 25 1a 71 86 eb  ...?48iL=Uq%.q..
[ 9969.903819] cachyos-x8664 kernel: 00000020: e3 44 aa 97 f1 5a 85 18                          .D...Z..
[ 9975.855026] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (15)
[ 9975.855552] cachyos-x8664 kernel: 00000000: bc946a80 901870c2 ab5065bf aa3230d7  .j...p...eP..02.
[ 9975.855591] cachyos-x8664 kernel: 00000010: 3ffe1e00 4cc021da f00cd10f 28f7b590  ...?.!.L.......(
[ 9975.855628] cachyos-x8664 kernel: 00000020: 5714459a cb3d7c2c 43e249df ba12db02  .E.W,|=..I.C....
[ 9975.855661] cachyos-x8664 kernel: 00000030: 4a26b732 7fb5f41c                    2.&J....
[ 9975.855754] cachyos-x8664 kernel: 00000000: 80 6a 94 bc c2 70 18 90 bf 65 50 ab d7 30 32 aa  .j...p...eP..02.
[ 9975.855859] cachyos-x8664 kernel: 00000010: 00 1e fe 3f da 21 c0 4c 0f d1 0c f0 90 b5 f7 28  ...?.!.L.......(
[ 9975.855983] cachyos-x8664 kernel: 00000020: 9a 45 14 57 2c 7c 3d cb                          .E.W,|=.
[ 9986.214022] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (2)
[ 9986.214512] cachyos-x8664 kernel: 00000000: 95515588 50ad66d1 893f252f 77ef35ae  .UQ..f.P/%?..5.w
[ 9986.214544] cachyos-x8664 kernel: 00000010: 3ffe1e00 4d626889 00404288 684bc88c  ...?.hbM.B@...Kh
[ 9986.214572] cachyos-x8664 kernel: 00000020: 686c63d1 5b971ca4 1ca4686c 73205a97  .clh...[lh...Z s
[ 9986.214599] cachyos-x8664 kernel: 00000030: 4a670000 000b2000                    ..gJ. ..
[ 9986.214623] cachyos-x8664 kernel: 00000000: 88 55 51 95 d1 66 ad 50 2f 25 3f 89 ae 35 ef 77  .UQ..f.P/%?..5.w
[ 9986.214642] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 89 68 62 4d 88 42 40 00 8c c8 4b 68  ...?.hbM.B@...Kh
[ 9986.214664] cachyos-x8664 kernel: 00000020: d1 63 6c 68 a4 1c 97 5b                          .clh...[
[ 9987.025020] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (10)
[ 9987.025511] cachyos-x8664 kernel: 00000000: df2a1ccb 05d069f1 0ee8c058 6e8759d0  ..*..i..X....Y.n
[ 9987.025537] cachyos-x8664 kernel: 00000010: f0567e63 d3b8fa95 fa3e4bd5 be0e0cb0  c~V......K>.....
[ 9987.025562] cachyos-x8664 kernel: 00000020: 89142842 adfdc115 81dbcad1 fc8ed25f  B(.........._...
[ 9987.025582] cachyos-x8664 kernel: 00000030: 9c5a1b24 5ef0fdb9                    $.Z....^
[ 9987.025600] cachyos-x8664 kernel: 00000000: cb 1c 2a df f1 69 d0 05 58 c0 e8 0e d0 59 87 6e  ..*..i..X....Y.n
[ 9987.025622] cachyos-x8664 kernel: 00000010: 63 7e 56 f0 95 fa b8 d3 d5 4b 3e fa b0 0c 0e be  c~V......K>.....
[ 9987.025646] cachyos-x8664 kernel: 00000020: 42 28 14 89 15 c1 fd ad                          B(......
[ 9990.199044] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (11)
[ 9990.199617] cachyos-x8664 kernel: 00000000: 7714c04e 2f94e5ca ae8ee0f4 79e4559f  N..w.../.....U.y
[ 9990.199659] cachyos-x8664 kernel: 00000010: 3ffe1e00 4d9ed1f7 eb4bc4dd c1815607  ...?...M..K..V..
[ 9990.199686] cachyos-x8664 kernel: 00000020: 638dc1cf 08655fd8 6ae854ab c42dba80  ...c._e..T.j..-.
[ 9990.199707] cachyos-x8664 kernel: 00000030: 80786881 bca27e5f                    .hx._~..
[ 9990.199726] cachyos-x8664 kernel: 00000000: 4e c0 14 77 ca e5 94 2f f4 e0 8e ae 9f 55 e4 79  N..w.../.....U.y
[ 9990.199744] cachyos-x8664 kernel: 00000010: 00 1e fe 3f f7 d1 9e 4d dd c4 4b eb 07 56 81 c1  ...?...M..K..V..
[ 9990.199762] cachyos-x8664 kernel: 00000020: cf c1 8d 63 d8 5f 65 08                          ...c._e.
[11224.235030] cachyos-x8664 kernel: wlan0: deauthenticating from 6c:68:a4:1c:97:5b by local choice (Reason: 3=DEAUTH_LEAVING)
[11224.827070] cachyos-x8664 kernel: PM: hibernation: hibernation entry
[11253.847102] cachyos-x8664 kernel: Filesystems sync: 0.036 seconds
[11253.847652] cachyos-x8664 kernel: Freezing user space processes
[11253.847717] cachyos-x8664 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
[11253.847802] cachyos-x8664 kernel: OOM killer disabled.
[11253.847851] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
[11253.847974] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00058000-0x00058fff]
[11253.850926] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00086000-0x000fffff]
[11253.857924] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x8d2fa000-0x8d303fff]
[11253.857991] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x9b88e000-0x9cffdfff]
[11253.858041] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x9cfff000-0xffffffff]
[11253.858104] cachyos-x8664 kernel: PM: hibernation: Basic memory bitmaps created
[11253.858169] cachyos-x8664 kernel: PM: hibernation: Preallocating image memory
[11253.858234] cachyos-x8664 kernel: PM: hibernation: Allocated 691900 pages for snapshot
[11253.858275] cachyos-x8664 kernel: PM: hibernation: Allocated 2767600 kbytes in 27.56 seconds (100.42 MB/s)
[11253.860692] cachyos-x8664 kernel: Freezing remaining freezable tasks
[11253.860794] cachyos-x8664 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[11253.860853] cachyos-x8664 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
[11253.860906] cachyos-x8664 kernel: ACPI: EC: interrupt blocked
[11253.860956] cachyos-x8664 kernel: ACPI: PM: Preparing to enter system sleep state S4
[11253.861045] cachyos-x8664 kernel: ACPI: EC: event blocked
[11253.861110] cachyos-x8664 kernel: ACPI: EC: EC stopped
[11253.861153] cachyos-x8664 kernel: ACPI: PM: Saving platform NVS memory
[11253.861193] cachyos-x8664 kernel: Disabling non-boot CPUs ...
[11253.861230] cachyos-x8664 kernel: smpboot: CPU 3 is now offline
[11253.861262] cachyos-x8664 kernel: smpboot: CPU 2 is now offline
[11253.861288] cachyos-x8664 kernel: smpboot: CPU 1 is now offline
[11253.861324] cachyos-x8664 kernel: PM: hibernation: Normal pages needed: 690507 + 1024, available pages: 2432023
[11253.861364] cachyos-x8664 kernel: ACPI: PM: Restoring platform NVS memory
[11253.861403] cachyos-x8664 kernel: ACPI: EC: EC started
[11253.861434] cachyos-x8664 kernel: Enabling non-boot CPUs ...
[11253.861603] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
[11253.861638] cachyos-x8664 kernel: CPU1 is up
[11253.861678] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
[11253.861718] cachyos-x8664 kernel: CPU2 is up
[11253.861757] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
[11253.861795] cachyos-x8664 kernel: CPU3 is up
[11253.861838] cachyos-x8664 kernel: ACPI: PM: Waking up from system sleep state S4
[11253.861869] cachyos-x8664 kernel: ACPI: EC: interrupt unblocked
[11253.861906] cachyos-x8664 kernel: usb usb1: root hub lost power or was reset
[11253.882008] cachyos-x8664 kernel: usb usb3: root hub lost power or was reset
[11253.883604] cachyos-x8664 kernel: ACPI: EC: event unblocked
[11253.883658] cachyos-x8664 kernel: usb usb2: root hub lost power or was reset
[11253.884847] cachyos-x8664 kernel: drm card1-eDP-1: Skipping unprepare of already unprepared panel
[11253.885577] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[11253.885633] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN00._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[11253.885670] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: Error updating fan power state
[11253.886698] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: dpm_run_callback(): platform_pm_restore returns -19
[11253.887239] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: failed to restore: error -19
[11253.887697] cachyos-x8664 kernel: ------------[ cut here ]------------
[11253.887736] cachyos-x8664 kernel: i915 0000:00:02.0: [drm] primary A assertion failure (expected off, current on)
[11253.887769] cachyos-x8664 kernel: WARNING: drivers/gpu/drm/i915/display/intel_display.c:410 at assert_plane+0xd6/0x140 [i915], CPU#0: kworker/u16:3/121275
[11253.887829] cachyos-x8664 kernel: Modules linked in: udp_diag tcp_diag inet_diag uinput snd_seq_dummy snd_hrtimer rfcomm snd_seq snd_seq_device ccm cmac algif_hash algif_skcipher af_alg bnep hp_bioscfg firmware_attributes_class amdgpu x86_pkg_temp_thermal intel_powerclamp coretemp rtw_8821ce(OE) kvm_intel snd_ctl_led snd_hda_codec_alc269 snd_hda_scodec_component rtw_8821c(OE) rmi_smbus snd_hda_codec_realtek_lib rtw_pci(OE) kvm snd_hda_codec_intelhdmi processor_thermal_device_pci_legacy snd_hda_codec_generic rmi_core drm_panel_backlight_quirks snd_hda_codec_hdmi rtw_core(OE) processor_thermal_device processor_thermal_power_floor irqbypass amdxcp processor_thermal_wt_hint snd_hda_intel btusb gpu_sched btmtk ghash_clmulni_intel processor_thermal_wt_req snd_hda_codec uvcvideo mac80211 aesni_intel vfat btbcm uvc fat rapl videobuf2_vmalloc snd_hda_core videobuf2_memops r8169 at24 btintel intel_cstate videobuf2_v4l2 processor_thermal_rfim snd_intel_dspcfg mei_hdcp mei_pxp intel_rapl_msr radeon btrtl spi_nor i2c_i801 intel_uncore
[11253.888717] cachyos-x8664 kernel:  processor_thermal_mbox realtek hp_wmi snd_intel_sdw_acpi wmi_bmof videobuf2_common drm_suballoc_helper snd_hwdep mtd sparse_keymap mdio_devres bluetooth cfg80211 drm_exec platform_temperature_control i2c_smbus psmouse pcspkr snd_pcm drm_ttm_helper libphy videodev i2c_mux processor_thermal_rapl intel_pch_thermal mei_me mc libarc4 rfkill snd_timer mdio_bus intel_rapl_common mei processor_thermal_soc_slider platform_profile snd int340x_thermal_zone intel_soc_dts_iosf soundcore intel_oc_wdt i2c_hid_acpi int3400_thermal i2c_hid acpi_thermal_rel wireless_hotkey acpi_pad mousedev joydev mac_hid tcp_bbr dm_mod ntsync i2c_dev crypto_user pkcs8_key_parser nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress i915 spi_intel_platform drm_buddy spi_intel intel_gtt ttm i2c_algo_bit drm_display_helper video cec lpc_ich wmi serio_raw
[11253.888821] cachyos-x8664 kernel: CPU: 0 UID: 0 PID: 121275 Comm: kworker/u16:3 Tainted: G        W IOE       6.19.9-2-cachyos #1 PREEMPT(full)  02bb0ae94e3484fd95eb7c5534d2c734ca97d599
[11253.888860] cachyos-x8664 kernel: Tainted: [W]=WARN, [I]=FIRMWARE_WORKAROUND, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[11253.888896] cachyos-x8664 kernel: Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
[11253.888930] cachyos-x8664 kernel: Workqueue: async async_run_entry_fn
[11253.888962] cachyos-x8664 kernel: RIP: 0010:assert_plane+0x135/0x140 [i915]
[11253.889022] cachyos-x8664 kernel: Code: 4e 18 48 c7 c6 31 55 c4 c0 84 db 49 c7 c0 c6 9a c2 c0 4c 0f 45 c6 49 c7 c1 c6 9a c2 c0 40 84 ed 4c 0f 45 ce 4c 89 ff 48 89 c6 <67> 48 0f b9 3a e9 19 ff ff ff cc 90 90 90 90 90 90 90 90 90 90 90
[11253.889059] cachyos-x8664 kernel: RSP: 0018:ffffcfebcd547a38 EFLAGS: 00010202
[11253.889094] cachyos-x8664 kernel: RAX: ffffffffc0c497b5 RBX: 0000000000000000 RCX: ffff88e68730b840
[11253.889129] cachyos-x8664 kernel: RDX: ffff88e681e81fb0 RSI: ffffffffc0c497b5 RDI: ffffffffc0682650
[11253.889160] cachyos-x8664 kernel: RBP: 0000000000000001 R08: ffffffffc0c29ac6 R09: ffffffffc0c45531
[11253.889191] cachyos-x8664 kernel: R10: 0000000000000004 R11: ffffffffa0d856e0 R12: ffff88e68ac06000
[11253.889223] cachyos-x8664 kernel: R13: ffff88e68ac06000 R14: ffff88e68caba000 R15: ffffffffc0682650
[11253.889253] cachyos-x8664 kernel: FS:  0000000000000000(0000) GS:ffff88e92eed3000(0000) knlGS:0000000000000000
[11253.889297] cachyos-x8664 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[11253.889328] cachyos-x8664 kernel: CR2: 00007fca674933d0 CR3: 0000000021014003 CR4: 00000000003726f0
[11253.889369] cachyos-x8664 kernel: Call Trace:
[11253.889401] cachyos-x8664 kernel:  <TASK>
[11253.889431] cachyos-x8664 kernel:  intel_disable_transcoder+0xbb/0x340 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.889462] cachyos-x8664 kernel:  intel_ddi_post_disable+0x10d/0x910 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.889493] cachyos-x8664 kernel:  hsw_crtc_disable+0x143/0x2e0 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.889523] cachyos-x8664 kernel:  intel_old_crtc_state_disables+0xdf/0x1a0 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.889562] cachyos-x8664 kernel:  intel_atomic_commit_tail+0xb28/0x19d0 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.889594] cachyos-x8664 kernel:  ? __pfx_pci_pm_restore.llvm.12419904442660537214+0x10/0x10
[11253.889625] cachyos-x8664 kernel:  intel_atomic_commit+0x247/0x280 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.889655] cachyos-x8664 kernel:  drm_atomic_commit+0xc3/0xf0
[11253.889685] cachyos-x8664 kernel:  ? __pfx___drm_printfn_info+0x10/0x10
[11253.889716] cachyos-x8664 kernel:  drm_atomic_helper_commit_duplicated_state+0x105/0x120
[11253.889748] cachyos-x8664 kernel:  __intel_display_driver_resume+0x8d/0xf0 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.889780] cachyos-x8664 kernel:  intel_display_driver_resume+0xdc/0x180 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.889810] cachyos-x8664 kernel:  i915_drm_resume+0x1d6/0x290 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.889850] cachyos-x8664 kernel:  device_resume+0x39c/0xa60
[11253.889881] cachyos-x8664 kernel:  async_resume+0x1d/0x40
[11253.889912] cachyos-x8664 kernel:  async_run_entry_fn+0x32/0x180
[11253.889942] cachyos-x8664 kernel:  process_scheduled_works+0x1f3/0x5e0
[11253.889973] cachyos-x8664 kernel:  worker_thread+0x18d/0x340
[11253.890432] cachyos-x8664 kernel:  ? __pfx_worker_thread+0x10/0x10
[11253.890490] cachyos-x8664 kernel:  kthread+0x205/0x280
[11253.890523] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[11253.890581] cachyos-x8664 kernel:  ret_from_fork+0x118/0x260
[11253.890612] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[11253.890642] cachyos-x8664 kernel:  ret_from_fork_asm+0x1a/0x30
[11253.890672] cachyos-x8664 kernel:  </TASK>
[11253.890702] cachyos-x8664 kernel: ---[ end trace 0000000000000000 ]---
[11253.890732] cachyos-x8664 kernel: usb 1-5: reset high-speed USB device number 4 using xhci_hcd
[11253.899059] cachyos-x8664 kernel: usb 2-1: reset high-speed USB device number 2 using ehci-pci
[11253.899913] cachyos-x8664 kernel: ------------[ cut here ]------------
[11253.899982] cachyos-x8664 kernel: i915 0000:00:02.0: [drm] primary A assertion failure (expected off, current on)
[11253.901281] cachyos-x8664 kernel: WARNING: drivers/gpu/drm/i915/display/intel_display.c:410 at assert_plane+0xd6/0x140 [i915], CPU#0: kworker/u16:3/121275
[11253.901346] cachyos-x8664 kernel: Modules linked in: udp_diag tcp_diag inet_diag uinput snd_seq_dummy snd_hrtimer rfcomm snd_seq snd_seq_device ccm cmac algif_hash algif_skcipher af_alg bnep hp_bioscfg firmware_attributes_class amdgpu x86_pkg_temp_thermal intel_powerclamp coretemp rtw_8821ce(OE) kvm_intel snd_ctl_led snd_hda_codec_alc269 snd_hda_scodec_component rtw_8821c(OE) rmi_smbus snd_hda_codec_realtek_lib rtw_pci(OE) kvm snd_hda_codec_intelhdmi processor_thermal_device_pci_legacy snd_hda_codec_generic rmi_core drm_panel_backlight_quirks snd_hda_codec_hdmi rtw_core(OE) processor_thermal_device processor_thermal_power_floor irqbypass amdxcp processor_thermal_wt_hint snd_hda_intel btusb gpu_sched btmtk ghash_clmulni_intel processor_thermal_wt_req snd_hda_codec uvcvideo mac80211 aesni_intel vfat btbcm uvc fat rapl videobuf2_vmalloc snd_hda_core videobuf2_memops r8169 at24 btintel intel_cstate videobuf2_v4l2 processor_thermal_rfim snd_intel_dspcfg mei_hdcp mei_pxp intel_rapl_msr radeon btrtl spi_nor i2c_i801 intel_uncore
[11253.902834] cachyos-x8664 kernel:  processor_thermal_mbox realtek hp_wmi snd_intel_sdw_acpi wmi_bmof videobuf2_common drm_suballoc_helper snd_hwdep mtd sparse_keymap mdio_devres bluetooth cfg80211 drm_exec platform_temperature_control i2c_smbus psmouse pcspkr snd_pcm drm_ttm_helper libphy videodev i2c_mux processor_thermal_rapl intel_pch_thermal mei_me mc libarc4 rfkill snd_timer mdio_bus intel_rapl_common mei processor_thermal_soc_slider platform_profile snd int340x_thermal_zone intel_soc_dts_iosf soundcore intel_oc_wdt i2c_hid_acpi int3400_thermal i2c_hid acpi_thermal_rel wireless_hotkey acpi_pad mousedev joydev mac_hid tcp_bbr dm_mod ntsync i2c_dev crypto_user pkcs8_key_parser nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress i915 spi_intel_platform drm_buddy spi_intel intel_gtt ttm i2c_algo_bit drm_display_helper video cec lpc_ich wmi serio_raw
[11253.905081] cachyos-x8664 kernel: CPU: 0 UID: 0 PID: 121275 Comm: kworker/u16:3 Tainted: G        W IOE       6.19.9-2-cachyos #1 PREEMPT(full)  02bb0ae94e3484fd95eb7c5534d2c734ca97d599
[11253.905139] cachyos-x8664 kernel: Tainted: [W]=WARN, [I]=FIRMWARE_WORKAROUND, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[11253.905172] cachyos-x8664 kernel: Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020
[11253.905228] cachyos-x8664 kernel: Workqueue: async async_run_entry_fn
[11253.905260] cachyos-x8664 kernel: RIP: 0010:assert_plane+0x135/0x140 [i915]
[11253.905290] cachyos-x8664 kernel: Code: 4e 18 48 c7 c6 31 55 c4 c0 84 db 49 c7 c0 c6 9a c2 c0 4c 0f 45 c6 49 c7 c1 c6 9a c2 c0 40 84 ed 4c 0f 45 ce 4c 89 ff 48 89 c6 <67> 48 0f b9 3a e9 19 ff ff ff cc 90 90 90 90 90 90 90 90 90 90 90
[11253.905322] cachyos-x8664 kernel: RSP: 0018:ffffcfebcd547b70 EFLAGS: 00010202
[11253.905363] cachyos-x8664 kernel: RAX: ffffffffc0c497b5 RBX: 0000000000000000 RCX: ffff88e68730b840
[11253.905394] cachyos-x8664 kernel: RDX: ffff88e681e81fb0 RSI: ffffffffc0c497b5 RDI: ffffffffc0682650
[11253.905424] cachyos-x8664 kernel: RBP: 0000000000000001 R08: ffffffffc0c29ac6 R09: ffffffffc0c45531
[11253.905455] cachyos-x8664 kernel: R10: ffff88e7385d8000 R11: ffffffffa0d856e0 R12: ffff88e68ac06000
[11253.905486] cachyos-x8664 kernel: R13: ffff88e7cd244000 R14: ffff88e68caba000 R15: ffffffffc0682650
[11253.905517] cachyos-x8664 kernel: FS:  0000000000000000(0000) GS:ffff88e92eed3000(0000) knlGS:0000000000000000
[11253.905547] cachyos-x8664 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[11253.905578] cachyos-x8664 kernel: CR2: 00007fca674933d0 CR3: 0000000021014003 CR4: 00000000003726f0
[11253.905610] cachyos-x8664 kernel: Call Trace:
[11253.905640] cachyos-x8664 kernel:  <TASK>
[11253.905682] cachyos-x8664 kernel:  intel_atomic_commit_tail+0x17d8/0x19d0 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.905715] cachyos-x8664 kernel:  ? __pfx_pci_pm_restore.llvm.12419904442660537214+0x10/0x10
[11253.905747] cachyos-x8664 kernel:  intel_atomic_commit+0x247/0x280 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.905779] cachyos-x8664 kernel:  drm_atomic_commit+0xc3/0xf0
[11253.905809] cachyos-x8664 kernel:  ? __pfx___drm_printfn_info+0x10/0x10
[11253.905851] cachyos-x8664 kernel:  drm_atomic_helper_commit_duplicated_state+0x105/0x120
[11253.905884] cachyos-x8664 kernel:  __intel_display_driver_resume+0x8d/0xf0 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.905917] cachyos-x8664 kernel:  intel_display_driver_resume+0xdc/0x180 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.905946] cachyos-x8664 kernel:  i915_drm_resume+0x1d6/0x290 [i915 52486d6213de99fc09458245751ac9837780e941]
[11253.905976] cachyos-x8664 kernel:  device_resume+0x39c/0xa60
[11253.907051] cachyos-x8664 kernel:  async_resume+0x1d/0x40
[11253.907118] cachyos-x8664 kernel:  async_run_entry_fn+0x32/0x180
[11253.907151] cachyos-x8664 kernel:  process_scheduled_works+0x1f3/0x5e0
[11253.907182] cachyos-x8664 kernel:  worker_thread+0x18d/0x340
[11253.907212] cachyos-x8664 kernel:  ? __pfx_worker_thread+0x10/0x10
[11253.907243] cachyos-x8664 kernel:  kthread+0x205/0x280
[11253.907274] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[11253.907307] cachyos-x8664 kernel:  ret_from_fork+0x118/0x260
[11253.907340] cachyos-x8664 kernel:  ? __pfx_kthread+0x10/0x10
[11253.907372] cachyos-x8664 kernel:  ret_from_fork_asm+0x1a/0x30
[11253.907439] cachyos-x8664 kernel:  </TASK>
[11253.907507] cachyos-x8664 kernel: ---[ end trace 0000000000000000 ]---
[11253.907553] cachyos-x8664 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[11253.908502] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[11253.908541] cachyos-x8664 kernel: sd 0:0:0:0: [sda] Starting disk
[11253.909208] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[11253.909244] cachyos-x8664 kernel: ata1.00: configured for UDMA/133
[11253.909277] cachyos-x8664 kernel: usb 1-3: WARN: invalid context state for evaluate context command.
[11253.909892] cachyos-x8664 kernel: usb 1-3: reset full-speed USB device number 5 using xhci_hcd
[11253.910692] cachyos-x8664 kernel: usb 1-4: WARN: invalid context state for evaluate context command.
[11253.911377] cachyos-x8664 kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[11253.911923] cachyos-x8664 kernel: PM: hibernation: Basic memory bitmaps freed
[11253.911980] cachyos-x8664 kernel: OOM killer enabled.
[11253.912045] cachyos-x8664 kernel: Restarting tasks: Starting
[11253.912093] cachyos-x8664 kernel: Restarting tasks: Done
[11253.912132] cachyos-x8664 kernel: efivarfs: resyncing variable state
[11253.912164] cachyos-x8664 kernel: efivarfs: removing variable HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
[11253.916176] cachyos-x8664 kernel: Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
[11253.917149] cachyos-x8664 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
[11253.918026] cachyos-x8664 kernel: Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[11253.918107] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
[11253.934036] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
[11253.934127] cachyos-x8664 kernel: Bluetooth: hci0: RTL: cfg_sz 10, total sz 34926
[11253.994039] cachyos-x8664 kernel: efivarfs: finished resyncing variable state
[11253.995018] cachyos-x8664 kernel: PM: hibernation: hibernation exit
[11254.160024] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[11254.160465] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[11254.160918] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[11254.161339] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[11254.161700] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[11254.162053] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[11254.162394] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[11254.162748] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[11254.410076] cachyos-x8664 kernel: Bluetooth: hci0: RTL: fw version 0x75b8f098
[11254.478049] cachyos-x8664 kernel: Bluetooth: MGMT ver 1.23
[11259.116068] cachyos-x8664 rtw88-nss0-hook: resume log saved to /home/pc/Загрузки/test/logs/resume_dmesg_20260327_172519.txt
[11259.320019] cachyos-x8664 kernel: RTL8208 Fast Ethernet r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
[11259.628024] cachyos-x8664 kernel: r8169 0000:07:00.0 enp7s0: Link is Down
[11264.599035] cachyos-x8664 kernel: wlan0: authenticate with 6c:68:a4:1c:97:5b (local address=8c:c8:4b:68:d1:63)
[11264.641061] cachyos-x8664 kernel: wlan0: send auth to 6c:68:a4:1c:97:5b (try 1/3)
[11264.709020] cachyos-x8664 kernel: wlan0: authenticated
[11264.709157] cachyos-x8664 kernel: wlan0: associate with 6c:68:a4:1c:97:5b (try 1/3)
[11264.711353] cachyos-x8664 kernel: wlan0: RX AssocResp from 6c:68:a4:1c:97:5b (capab=0x431 status=0 aid=2)
[11264.711433] cachyos-x8664 kernel: wlan0: associated
[11264.715016] cachyos-x8664 kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 6c:68:a4:1c:97:5b
[11279.578026] cachyos-x8664 kernel: input: Soundcore Q10i (AVRCP) as /devices/virtual/input/input36
[12360.451663] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[12360.452204] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[12360.462661] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[12360.463132] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[12361.071025] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[12361.071485] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[12361.080560] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[12361.081595] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[25859.701018] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[25859.701855] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[25859.711925] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[25859.712413] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[25860.239016] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[25860.239773] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[25860.252013] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[25860.252457] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[33792.858278] cachyos-x8664 kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 8:0:00000000
[33792.865875] cachyos-x8664 kernel: i915 0000:00:02.0: [drm] GPU error state saved to /sys/class/drm/card1/error
[33792.867470] cachyos-x8664 kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0
[35162.238032] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (4)
[35162.239539] cachyos-x8664 kernel: 00000000: 4efaee97 21009004 80890fc0 000033b3  ...N...!.....3..
[35162.239623] cachyos-x8664 kernel: 00000010: 3ffe1e00 90647e97 fa743e5d 6539e070  ...?.~d.]>t.p.9e
[35162.239690] cachyos-x8664 kernel: 00000020: d340a448 1585a9de 75584c8e 80e221af  H.@......LXu.!..
[35162.239736] cachyos-x8664 kernel: 00000030: c599af5a e97f7244                    Z...Dr..
[35162.239811] cachyos-x8664 kernel: 00000000: 97 ee fa 4e 04 90 00 21 c0 0f 89 80 b3 33 00 00  ...N...!.....3..
[35162.239877] cachyos-x8664 kernel: 00000010: 00 1e fe 3f 97 7e 64 90 5d 3e 74 fa 70 e0 39 65  ...?.~d.]>t.p.9e
[35162.239919] cachyos-x8664 kernel: 00000020: 48 a4 40 d3 de a9 85 15                          H.@.....
[36720.500038] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[36720.503437] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[36720.510022] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[36720.510478] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[36721.410243] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[36721.410735] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[36721.420389] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[36721.420846] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[41436.732028] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0).
[41436.734901] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
[41436.742381] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
[41436.742852] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
[41437.269700] cachyos-x8664 kernel: wlan0: deauthenticating from 6c:68:a4:1c:97:5b by local choice (Reason: 3=DEAUTH_LEAVING)
[41438.151138] cachyos-x8664 kernel: PM: hibernation: hibernation entry
[41465.584856] cachyos-x8664 kernel: Filesystems sync: 0.067 seconds
[41465.589385] cachyos-x8664 kernel: Freezing user space processes
[41465.593938] cachyos-x8664 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
[41465.595368] cachyos-x8664 kernel: OOM killer disabled.
[41465.595459] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
[41465.595514] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00058000-0x00058fff]
[41465.595560] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00086000-0x000fffff]
[41465.595666] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x8d2fa000-0x8d303fff]
[41465.595761] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x9b88e000-0x9cffdfff]
[41465.595814] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x9cfff000-0xffffffff]
[41465.595852] cachyos-x8664 kernel: PM: hibernation: Basic memory bitmaps created
[41465.595943] cachyos-x8664 kernel: PM: hibernation: Preallocating image memory
[41465.595987] cachyos-x8664 kernel: PM: hibernation: Allocated 732603 pages for snapshot
[41465.596051] cachyos-x8664 kernel: PM: hibernation: Allocated 2930412 kbytes in 26.02 seconds (112.62 MB/s)
[41465.596130] cachyos-x8664 kernel: Freezing remaining freezable tasks
[41465.596189] cachyos-x8664 kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
[41465.596265] cachyos-x8664 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
[41465.596344] cachyos-x8664 kernel: ACPI: EC: interrupt blocked
[41465.596376] cachyos-x8664 kernel: ACPI: PM: Preparing to enter system sleep state S4
[41465.596415] cachyos-x8664 kernel: ACPI: EC: event blocked
[41465.596462] cachyos-x8664 kernel: ACPI: EC: EC stopped
[41465.596502] cachyos-x8664 kernel: ACPI: PM: Saving platform NVS memory
[41465.596556] cachyos-x8664 kernel: Disabling non-boot CPUs ...
[41465.596604] cachyos-x8664 kernel: smpboot: CPU 3 is now offline
[41465.596645] cachyos-x8664 kernel: smpboot: CPU 2 is now offline
[41465.596709] cachyos-x8664 kernel: smpboot: CPU 1 is now offline
[41465.596791] cachyos-x8664 kernel: PM: hibernation: Normal pages needed: 730536 + 1024, available pages: 2392009
[41465.596846] cachyos-x8664 kernel: ACPI: PM: Restoring platform NVS memory
[41465.596894] cachyos-x8664 kernel: ACPI: EC: EC started
[41465.596935] cachyos-x8664 kernel: Enabling non-boot CPUs ...
[41465.596987] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
[41465.597094] cachyos-x8664 kernel: CPU1 is up
[41465.597173] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
[41465.597207] cachyos-x8664 kernel: CPU2 is up
[41465.597239] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
[41465.597281] cachyos-x8664 kernel: CPU3 is up
[41465.597323] cachyos-x8664 kernel: ACPI: PM: Waking up from system sleep state S4
[41465.597355] cachyos-x8664 kernel: ACPI: EC: interrupt unblocked
[41465.597401] cachyos-x8664 kernel: usb usb1: root hub lost power or was reset
[41465.600920] cachyos-x8664 kernel: usb usb3: root hub lost power or was reset
[41465.602788] cachyos-x8664 kernel: ACPI: EC: event unblocked
[41465.602833] cachyos-x8664 kernel: usb usb2: root hub lost power or was reset
[41465.603860] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[41465.603935] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN00._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[41465.603980] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: Error updating fan power state
[41465.605949] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: dpm_run_callback(): platform_pm_restore returns -19
[41465.606602] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: failed to restore: error -19
[41465.607149] cachyos-x8664 kernel: usb 1-5: reset high-speed USB device number 4 using xhci_hcd
[41465.607859] cachyos-x8664 kernel: usb 2-1: reset high-speed USB device number 2 using ehci-pci
[41465.612174] cachyos-x8664 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[41465.612238] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[41465.612294] cachyos-x8664 kernel: sd 0:0:0:0: [sda] Starting disk
[41465.612892] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[41465.612940] cachyos-x8664 kernel: ata1.00: configured for UDMA/133
[41465.612990] cachyos-x8664 kernel: usb 1-3: WARN: invalid context state for evaluate context command.
[41465.613641] cachyos-x8664 kernel: usb 1-3: reset full-speed USB device number 5 using xhci_hcd
[41465.614233] cachyos-x8664 kernel: usb 1-4: WARN: invalid context state for evaluate context command.
[41465.614866] cachyos-x8664 kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[41465.615999] cachyos-x8664 kernel: PM: hibernation: Basic memory bitmaps freed
[41465.616055] cachyos-x8664 kernel: OOM killer enabled.
[41465.616100] cachyos-x8664 kernel: Restarting tasks: Starting
[41465.616132] cachyos-x8664 kernel: Restarting tasks: Done
[41465.616162] cachyos-x8664 kernel: efivarfs: resyncing variable state
[41465.616201] cachyos-x8664 kernel: efivarfs: removing variable HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
[41465.657032] cachyos-x8664 kernel: Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
[41465.657177] cachyos-x8664 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
[41465.658445] cachyos-x8664 kernel: Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[41465.660023] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
[41465.660084] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
[41465.660119] cachyos-x8664 kernel: Bluetooth: hci0: RTL: cfg_sz 10, total sz 34926
[41465.711025] cachyos-x8664 kernel: efivarfs: finished resyncing variable state
[41465.712015] cachyos-x8664 kernel: PM: hibernation: hibernation exit
[41465.903078] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[41465.904070] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[41465.904381] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[41465.904690] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[41465.904979] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[41465.905271] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[41465.905556] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[41465.905827] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[41466.132126] cachyos-x8664 kernel: Bluetooth: hci0: RTL: fw version 0x75b8f098
[41466.199185] cachyos-x8664 kernel: Bluetooth: MGMT ver 1.23
[41470.830030] cachyos-x8664 rtw88-nss0-hook: resume log saved to /home/pc/Загрузки/test/logs/resume_dmesg_20260328_130152.txt
[41471.169035] cachyos-x8664 kernel: RTL8208 Fast Ethernet r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
[41471.705034] cachyos-x8664 kernel: r8169 0000:07:00.0 enp7s0: Link is Down
[41476.396083] cachyos-x8664 kernel: wlan0: authenticate with 6c:68:a4:1c:97:5b (local address=8c:c8:4b:68:d1:63)
[41476.438038] cachyos-x8664 kernel: wlan0: send auth to 6c:68:a4:1c:97:5b (try 1/3)
[41476.509022] cachyos-x8664 kernel: wlan0: authenticated
[41476.509070] cachyos-x8664 kernel: wlan0: associate with 6c:68:a4:1c:97:5b (try 1/3)
[41476.511022] cachyos-x8664 kernel: wlan0: RX AssocResp from 6c:68:a4:1c:97:5b (capab=0x431 status=0 aid=5)
[41476.511097] cachyos-x8664 kernel: wlan0: associated
[41476.596058] cachyos-x8664 kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 6c:68:a4:1c:97:5b
[42398.245062] cachyos-x8664 kernel: input: Soundcore Q10i (AVRCP) as /devices/virtual/input/input37
[49578.500043] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[49578.638709] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[49578.639472] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[49578.640097] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[49579.843051] cachyos-x8664 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[49579.843553] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[49579.853557] cachyos-x8664 kernel: atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[49579.854055] cachyos-x8664 kernel: atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[49664.026030] cachyos-x8664 kernel: input: Soundcore Q10i (AVRCP) as /devices/virtual/input/input38
[49672.299050] cachyos-x8664 kernel: wlan0: deauthenticating from 6c:68:a4:1c:97:5b by local choice (Reason: 3=DEAUTH_LEAVING)
[49673.128030] cachyos-x8664 kernel: PM: suspend entry (deep)
[49673.224040] cachyos-x8664 kernel: Filesystems sync: 0.095 seconds
[49674.234992] cachyos-x8664 kernel: Freezing user space processes
[49674.236769] cachyos-x8664 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
[49674.236835] cachyos-x8664 kernel: OOM killer disabled.
[49674.236889] cachyos-x8664 kernel: Freezing remaining freezable tasks
[49674.236947] cachyos-x8664 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[49674.237021] cachyos-x8664 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
[49674.237430] cachyos-x8664 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
[49674.239602] cachyos-x8664 kernel: ata1.00: Entering standby power mode
[49674.239662] cachyos-x8664 kernel: ACPI: EC: interrupt blocked
[49674.239720] cachyos-x8664 kernel: ACPI: PM: Preparing to enter system sleep state S3
[49674.239820] cachyos-x8664 kernel: ACPI: EC: event blocked
[49674.239870] cachyos-x8664 kernel: ACPI: EC: EC stopped
[49674.239945] cachyos-x8664 kernel: ACPI: PM: Saving platform NVS memory
[49674.239987] cachyos-x8664 kernel: Disabling non-boot CPUs ...
[49674.240045] cachyos-x8664 kernel: smpboot: CPU 3 is now offline
[49674.240119] cachyos-x8664 kernel: smpboot: CPU 2 is now offline
[49674.240171] cachyos-x8664 kernel: smpboot: CPU 1 is now offline
[49674.240237] cachyos-x8664 kernel: ACPI: PM: Low-level resume complete
[49674.240312] cachyos-x8664 kernel: ACPI: EC: EC started
[49674.240367] cachyos-x8664 kernel: ACPI: PM: Restoring platform NVS memory
[49674.240413] cachyos-x8664 kernel: Enabling non-boot CPUs ...
[49674.240451] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
[49674.240482] cachyos-x8664 kernel: CPU1 is up
[49674.240529] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
[49674.240569] cachyos-x8664 kernel: CPU2 is up
[49674.240613] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
[49674.240652] cachyos-x8664 kernel: CPU3 is up
[49674.240696] cachyos-x8664 kernel: ACPI: PM: Waking up from system sleep state S3
[49674.240741] cachyos-x8664 kernel: ACPI: EC: interrupt unblocked
[49674.240785] cachyos-x8664 kernel: ACPI: EC: event unblocked
[49674.240821] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[49674.240871] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN00._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[49674.240927] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: Error updating fan power state
[49674.241655] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: dpm_run_callback(): platform_pm_resume returns -19
[49674.242180] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: failed to resume: error -19
[49674.242641] cachyos-x8664 kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[49674.243742] cachyos-x8664 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[49674.243803] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[49674.243898] cachyos-x8664 kernel: sd 0:0:0:0: [sda] Starting disk
[49674.244607] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[49674.244670] cachyos-x8664 kernel: ata1.00: configured for UDMA/133
[49674.244751] cachyos-x8664 kernel: usb 1-5: reset high-speed USB device number 4 using xhci_hcd
[49674.245807] cachyos-x8664 kernel: OOM killer enabled.
[49674.245899] cachyos-x8664 kernel: Restarting tasks: Starting
[49674.245954] cachyos-x8664 kernel: Restarting tasks: Done
[49674.246059] cachyos-x8664 kernel: efivarfs: resyncing variable state
[49674.246108] cachyos-x8664 kernel: Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
[49674.246194] cachyos-x8664 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
[49674.246269] cachyos-x8664 kernel: Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[49674.246318] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
[49674.248164] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
[49674.248269] cachyos-x8664 kernel: Bluetooth: hci0: RTL: cfg_sz 10, total sz 34926
[49674.337247] cachyos-x8664 kernel: efivarfs: finished resyncing variable state
[49674.337353] cachyos-x8664 kernel: random: crng reseeded on system resumption
[49674.340510] cachyos-x8664 kernel: PM: suspend exit
[49674.561209] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[49674.562545] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[49674.563634] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[49674.564764] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[49674.565533] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[49674.566254] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[49674.566937] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[49674.567321] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[49674.731133] cachyos-x8664 kernel: Bluetooth: hci0: RTL: fw version 0x75b8f098
[49674.798027] cachyos-x8664 kernel: Bluetooth: MGMT ver 1.23
[49679.402042] cachyos-x8664 rtw88-nss0-hook: resume log saved to /home/pc/Загрузки/test/logs/resume_dmesg_20260328_151855.txt
[49679.449026] cachyos-x8664 kernel: RTL8208 Fast Ethernet r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
[49679.789965] cachyos-x8664 kernel: r8169 0000:07:00.0 enp7s0: Link is Down
[49683.051116] cachyos-x8664 kernel: input: Soundcore Q10i (AVRCP) as /devices/virtual/input/input39
[49684.625094] cachyos-x8664 kernel: wlan0: authenticate with 6c:68:a4:1c:97:5b (local address=8c:c8:4b:68:d1:63)
[49684.667052] cachyos-x8664 kernel: wlan0: send auth to 6c:68:a4:1c:97:5b (try 1/3)
[49684.677045] cachyos-x8664 kernel: wlan0: authenticated
[49684.677081] cachyos-x8664 kernel: wlan0: associate with 6c:68:a4:1c:97:5b (try 1/3)
[49684.679756] cachyos-x8664 kernel: wlan0: RX AssocResp from 6c:68:a4:1c:97:5b (capab=0x431 status=0 aid=1)
[49684.679997] cachyos-x8664 kernel: wlan0: associated
[49684.681031] cachyos-x8664 kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 6c:68:a4:1c:97:5b
[49705.735218] cachyos-x8664 kernel: wlan0: deauthenticating from 6c:68:a4:1c:97:5b by local choice (Reason: 3=DEAUTH_LEAVING)
[49706.720035] cachyos-x8664 kernel: PM: hibernation: hibernation entry
[49706.830021] cachyos-x8664 kernel: Filesystems sync: 0.104 seconds
[49733.996946] cachyos-x8664 kernel: Freezing user space processes
[49734.003979] cachyos-x8664 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
[49734.004105] cachyos-x8664 kernel: OOM killer disabled.
[49734.004195] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
[49734.004344] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00058000-0x00058fff]
[49734.004423] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x00086000-0x000fffff]
[49734.004516] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x8d2fa000-0x8d303fff]
[49734.004572] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x9b88e000-0x9cffdfff]
[49734.004619] cachyos-x8664 kernel: PM: hibernation: Marking nosave pages: [mem 0x9cfff000-0xffffffff]
[49734.004651] cachyos-x8664 kernel: PM: hibernation: Basic memory bitmaps created
[49734.004834] cachyos-x8664 kernel: PM: hibernation: Preallocating image memory
[49734.004882] cachyos-x8664 kernel: PM: hibernation: Allocated 760252 pages for snapshot
[49734.004938] cachyos-x8664 kernel: PM: hibernation: Allocated 3041008 kbytes in 25.38 seconds (119.81 MB/s)
[49734.004986] cachyos-x8664 kernel: Freezing remaining freezable tasks
[49734.006127] cachyos-x8664 kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
[49734.006202] cachyos-x8664 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
[49734.006268] cachyos-x8664 kernel: ACPI: EC: interrupt blocked
[49734.006340] cachyos-x8664 kernel: ACPI: PM: Preparing to enter system sleep state S4
[49734.006390] cachyos-x8664 kernel: ACPI: EC: event blocked
[49734.006442] cachyos-x8664 kernel: ACPI: EC: EC stopped
[49734.006489] cachyos-x8664 kernel: ACPI: PM: Saving platform NVS memory
[49734.006553] cachyos-x8664 kernel: Disabling non-boot CPUs ...
[49734.006629] cachyos-x8664 kernel: smpboot: CPU 3 is now offline
[49734.006737] cachyos-x8664 kernel: smpboot: CPU 2 is now offline
[49734.006789] cachyos-x8664 kernel: smpboot: CPU 1 is now offline
[49734.006848] cachyos-x8664 kernel: PM: hibernation: Normal pages needed: 759837 + 1024, available pages: 2362710
[49734.006903] cachyos-x8664 kernel: ACPI: PM: Restoring platform NVS memory
[49734.006943] cachyos-x8664 kernel: ACPI: EC: EC started
[49734.006990] cachyos-x8664 kernel: Enabling non-boot CPUs ...
[49734.007879] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
[49734.007953] cachyos-x8664 kernel: CPU1 is up
[49734.008040] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
[49734.008115] cachyos-x8664 kernel: CPU2 is up
[49734.008155] cachyos-x8664 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
[49734.008210] cachyos-x8664 kernel: CPU3 is up
[49734.008250] cachyos-x8664 kernel: ACPI: PM: Waking up from system sleep state S4
[49734.008291] cachyos-x8664 kernel: ACPI: EC: interrupt unblocked
[49734.008343] cachyos-x8664 kernel: ACPI: EC: event unblocked
[49734.008411] cachyos-x8664 kernel: usb usb1: root hub lost power or was reset
[49734.013870] cachyos-x8664 kernel: usb usb3: root hub lost power or was reset
[49734.015049] cachyos-x8664 kernel: usb usb2: root hub lost power or was reset
[49734.016152] cachyos-x8664 kernel: drm card1-eDP-1: Skipping unprepare of already unprepared panel
[49734.016978] cachyos-x8664 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECWT], AE_NOT_FOUND (20250807/psargs-332)
[49734.017048] cachyos-x8664 kernel: ACPI Error: Aborting method \_TZ.FN00._ON due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
[49734.017094] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: Error updating fan power state
[49734.018026] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: dpm_run_callback(): platform_pm_restore returns -19
[49734.018712] cachyos-x8664 kernel: acpi-fan PNP0C0B:00: PM: failed to restore: error -19
[49734.019370] cachyos-x8664 kernel: usb 1-5: reset high-speed USB device number 4 using xhci_hcd
[49734.021320] cachyos-x8664 kernel: usb 2-1: reset high-speed USB device number 2 using ehci-pci
[49734.023994] cachyos-x8664 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[49734.024065] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[49734.024128] cachyos-x8664 kernel: sd 0:0:0:0: [sda] Starting disk
[49734.025468] cachyos-x8664 kernel: ata1.00: NCQ Send/Recv Log not supported
[49734.025512] cachyos-x8664 kernel: ata1.00: configured for UDMA/133
[49734.025551] cachyos-x8664 kernel: usb 1-3: WARN: invalid context state for evaluate context command.
[49734.026560] cachyos-x8664 kernel: usb 1-3: reset full-speed USB device number 5 using xhci_hcd
[49734.027453] cachyos-x8664 kernel: usb 1-4: WARN: invalid context state for evaluate context command.
[49734.028385] cachyos-x8664 kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[49734.029572] cachyos-x8664 kernel: PM: hibernation: Basic memory bitmaps freed
[49734.029614] cachyos-x8664 kernel: OOM killer enabled.
[49734.029673] cachyos-x8664 kernel: Restarting tasks: Starting
[49734.029714] cachyos-x8664 kernel: Restarting tasks: Done
[49734.029745] cachyos-x8664 kernel: efivarfs: resyncing variable state
[49734.029788] cachyos-x8664 kernel: efivarfs: removing variable HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
[49734.029828] cachyos-x8664 kernel: Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
[49734.029873] cachyos-x8664 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
[49734.029921] cachyos-x8664 kernel: Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[49734.029952] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
[49734.029988] cachyos-x8664 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
[49734.030051] cachyos-x8664 kernel: Bluetooth: hci0: RTL: cfg_sz 10, total sz 34926
[49734.152031] cachyos-x8664 kernel: efivarfs: finished resyncing variable state
[49734.153021] cachyos-x8664 kernel: PM: hibernation: hibernation exit
[49734.323054] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[49734.323624] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[49734.324025] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[49734.324331] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[49734.324617] cachyos-x8664 kernel: pci_bus 0000:01: Allocating resources
[49734.324886] cachyos-x8664 kernel: pci_bus 0000:07: Allocating resources
[49734.325165] cachyos-x8664 kernel: pci_bus 0000:0d: Allocating resources
[49734.325431] cachyos-x8664 kernel: pci_bus 0000:13: Allocating resources
[49734.505189] cachyos-x8664 kernel: Bluetooth: hci0: RTL: fw version 0x75b8f098
[49734.573062] cachyos-x8664 kernel: Bluetooth: MGMT ver 1.23
[49739.275020] cachyos-x8664 rtw88-nss0-hook: resume log saved to /home/pc/Загрузки/test/logs/resume_dmesg_20260328_152442.txt
[49739.796031] cachyos-x8664 kernel: RTL8208 Fast Ethernet r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
[49740.079323] cachyos-x8664 kernel: r8169 0000:07:00.0 enp7s0: Link is Down
[49744.756036] cachyos-x8664 kernel: wlan0: authenticate with 6c:68:a4:1c:97:5b (local address=8c:c8:4b:68:d1:63)
[49744.799024] cachyos-x8664 kernel: wlan0: send auth to 6c:68:a4:1c:97:5b (try 1/3)
[49744.868041] cachyos-x8664 kernel: wlan0: authenticated
[49744.868109] cachyos-x8664 kernel: wlan0: associate with 6c:68:a4:1c:97:5b (try 1/3)
[49744.869379] cachyos-x8664 kernel: wlan0: RX AssocResp from 6c:68:a4:1c:97:5b (capab=0x431 status=0 aid=1)
[49744.870018] cachyos-x8664 kernel: wlan0: associated
[49744.904034] cachyos-x8664 kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 6c:68:a4:1c:97:5b
[49839.888038] cachyos-x8664 kernel: input: Soundcore Q10i (AVRCP) as /devices/virtual/input/input40

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Bitterblue Smith]

On 28/03/2026 15:40, LB F wrote:
> Hi Bitterblue,
> 
> Thank you for the quick feedback. Full dmesg from the current boot
> session is attached (dmesg_boot0_clean.txt, 332K, 3349 lines).
> 
> It contains all 76 "unused phy status page" events with both hex
> dumps (4-byte grouped and byte-level) in full, plus all surrounding
> kernel context.
> 
> The interesting observation you made about the MAC addresses being
> 24 bytes lower than expected is very helpful — I hadn't noticed the
> offset discrepancy. If you need the adapter and AP MAC addresses
> for reference:
> 
>   Adapter: 8c:c8:4b:68:d1:63
>   AP:      6c:68:a4:1c:97:5b
> 
> And yes, adding a NULL check in rtw_fw_adaptivity_result() seems
> like a good defensive measure regardless of the root cause.
> 
> Let me know if you need anything else or a different format.
> 
> Best regards,
> Oleksandr Havrylov

I made a mistake with the second print_hex_dump. It was supposed to
print from rxdesc + 56. But not to worry, I think this is sufficient.

Some of the frames have what looks like a valid PHY status at byte 24:

[ 9926.365048] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (7)
[ 9926.365451] cachyos-x8664 kernel: 00000000: 05da26ac b587f0af 0aa2e765 f48d78f5  .&......e....x..
[ 9926.365475] cachyos-x8664 kernel: 00000010: 3ffe9e00 49d11a5c 00002701 012a0000  ...?\..I.'....*.
[ 9926.365496] cachyos-x8664 kernel: 00000020: 00000014 20000000 000000e2 0000000a  ....... ........
[ 9926.365537] cachyos-x8664 kernel: 00000030: 0000001c 00000000                    ........

But RTW_RX_DESC_W0_SHIFT is not 0. Then rtw88 looks for the PHY
status in the wrong place, in this case at byte 25. The official
driver always looks for it at byte 24:

https://github.com/lwfinger/rtw88/blob/master/alt_rtl8821ce/hal/rtl8821c/pci/rtl8821ce_recv.c#L272

Unfortunately fixing that won't be enough.

The way rtw88 configures the chip, RTW_RX_DESC_W0_DRV_INFO_SIZE is
supposed to be either 0 or 4, but in these frames it has many other
values.

In this case:

[ 9986.214022] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status page (2)
[ 9986.214512] cachyos-x8664 kernel: 00000000: 95515588 50ad66d1 893f252f 77ef35ae  .UQ..f.P/%?..5.w
[ 9986.214544] cachyos-x8664 kernel: 00000010: 3ffe1e00 4d626889 00404288 684bc88c  ...?.hbM.B@...Kh
[ 9986.214572] cachyos-x8664 kernel: 00000020: 686c63d1 5b971ca4 1ca4686c 73205a97  .clh...[lh...Z s
[ 9986.214599] cachyos-x8664 kernel: 00000030: 4a670000 000b2000                    ..gJ. ..

the 802.11 header immediately follows the RX descriptor (there is
no PHY status, which is not unusual) but RTW_RX_DESC_W0_PHYST is 1.

In station mode RTW_RX_DESC_W1_MACID is supposed to be 0 or 1 (I think),
mostly 0. In these frames it has many other values.

RTW_RX_DESC_W0_PKT_LEN sometimes exceeds 11454. In one case it's 0.

In many of these frames bytes 25..31 don't look like a PHY status
or 802.11 header.

If we can't find the reason for these weird frames, maybe the best
way to filter them out is to check RTW_RX_DESC_W0_DRV_INFO_SIZE.
It takes care of 67 out of the 76 weird frames in dmesg_boot0_clean.txt.

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Hi Bitterblue,

Thank you for the thorough analysis of the RX descriptor fields.
I found your observations very insightful — especially the 24-byte
MAC address offset and the DRV_INFO_SIZE anomalies.

I fixed the second print_hex_dump to start at rxdesc + 56 as you
originally intended:

-               print_hex_dump(KERN_INFO, "", DUMP_PREFIX_OFFSET, 16, 1,
-                              rxdesc, 40, true);
+               print_hex_dump(KERN_INFO, "", DUMP_PREFIX_OFFSET, 16, 1,
+                              rxdesc + 56, 40, true);

The corrected patch is compiled and installed. I will send a new
full dmesg with the additional data after the next reboot once
some events accumulate.

I'm ready to test any further patches you or Ping-Ke may propose,
including the DRV_INFO_SIZE filter or any other approach. Just let
me know.

Best regards,
Oleksandr Havrylov

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Following up on the corrected patch — I tried to trace the RX path
myself to understand the full picture. I am not a developer
and may be misreading the code, so please take this with a grain
of salt. But I thought some of these observations might be useful.

---

Tracing the RX path from DMA to crash
--------------------------------------

In rtw_pci_rx_napi() (pci.c), each frame from the DMA ring is
processed like this:

  1. rtw_pci_dma_check()           — compares rx_tag, but only
                                     warns on mismatch, does not
                                     skip the frame (pci.c:696)

  2. dma_sync_single_for_cpu()     — syncs 11478 bytes
                                     (RTK_PCI_RX_BUF_SIZE) from
                                     device to CPU

  3. rtw_rx_query_rx_desc()        — parses all RX descriptor
                                     fields from W0..W5 with no
                                     validation (rx.c:305-325):

       pkt_len      = W0[13:0]     range 0..16383
       drv_info_sz  = W0[19:16]    range 0..15, then *8 = 0..120
       shift        = W0[25:24]    range 0..3
       physt        = W0[26]       0 or 1
       is_c2h       = W2[28]       0 or 1

     None of these fields are checked against expected values.

  4. pkt_offset = 24 + drv_info_sz + shift
     With garbage, this can be up to 24 + 120 + 3 = 147.

  5. new_len = pkt_len + pkt_offset      (pci.c:1088)
     With garbage, this can be up to 16383 + 147 = 16530,
     which exceeds RTK_PCI_RX_BUF_SIZE (11478).
     skb_put_data() then copies new_len bytes from the DMA
     buffer — potentially reading past the end.

  6. If is_c2h == 1 (from garbage W2 bit 28), the frame goes
     to rtw_fw_c2h_cmd_rx_irqsafe() (pci.c:1096-1097).

In rtw_fw_c2h_cmd_rx_irqsafe() (fw.c:351):

  7. c2h = skb->data + pkt_offset
     c2h->id is simply read from that offset — a random byte
     from garbage data. No validation against known C2H IDs.

  8. If c2h->id is not C2H_BT_MP_INFO, C2H_WLAN_RFON, or
     C2H_SCAN_RESULT, the skb goes to c2h_queue for deferred
     processing via the default case (fw.c:377-381).

In rtw_c2h_work() -> rtw_fw_c2h_cmd_handle() (fw.c:302):

  9. mutex_lock(&rtwdev->mutex)
     c2h->id is matched against the switch cases.
     If it happens to be 0x37 (C2H_ADAPTIVITY):
       rtw_fw_adaptivity_result() dereferences
       rtwdev->chip->edcca_th, which is NULL for RTL8821C.
       Kernel oops. Mutex never unlocked.

So the crash is probabilistic — it requires a garbage frame
where W2 bit 28 is 1 (is_c2h) AND the byte at pkt_offset
happens to be 0x37. This explains why not every burst of
corrupted frames results in a crash.

---

Concrete example with a captured dump
--------------------------------------

Taking the "page 2" dump with MAC addresses:

  00000000: 88 55 51 95 d1 66 ad 50 2f 25 3f 89 ae 35 ef 77

  W0 (bytes 0-3, little-endian) = 0x95515588
    pkt_len      = 0x588      = 1416
    drv_info_sz  = 0x5        -> *8 = 40
    shift        = 1
    physt        = 1

  W2 (bytes 8-11, little-endian) = 0x893f252f
    is_c2h = bit 28 = (0x893f252f >> 28) = 0x8 -> bit 0 = 0
    (In this particular frame is_c2h = 0, so no C2H path.)

  But drv_info_sz = 5 (should be 0 or 4 per your observation),
  confirming the frame is corrupted.

---

pci bus timeout
---------------

I checked all our saved logs across 29 boots and 41 resume
cycles: zero "pci bus timeout" messages anywhere. This means
rtw_pci_dma_check() never detects a rx_tag mismatch — the
buffer descriptor passes validation, but the buffer content
is corrupted. So the corruption seems to happen at a level
that rx_tag does not catch.

---

I also noticed that new_len is not bounds-checked against
RTK_PCI_RX_BUF_SIZE before the skb_put_data() copy
(pci.c:1088-1094), which might be worth looking at
independently of this bug.

Again, I'm sure you will see things I've missed. Happy to
test anything.

Best regards,
Oleksandr Havrylov

Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[LB F]

Hi Bitterblue, Ping-Ke,

Apologies — I made errors in the hex dump analysis from my
previous message. Corrections:

  pkt_len:     I wrote 0x588 (1416), correct is 0x1588 (5512).
  drv_info_sz: I wrote 5, correct is 1 (raw) -> *8 = 8.
  macid:       81 (I didn't mention this, but it also confirms
               corruption — it should be 0 or 1).

The is_c2h = 0 part was correct for that particular frame.

Sorry for the confusion. I should have verified the bit field
extraction more carefully before sending. Please disregard my
specific calculations and rely on your own analysis — you
clearly have a much better understanding of the descriptor
layout than I do.

I remain happy to test any patches.

Best regards,
Oleksandr Havrylov

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> 
> On 28/03/2026 15:40, LB F wrote:
> > Hi Bitterblue,
> >
> > Thank you for the quick feedback. Full dmesg from the current boot
> > session is attached (dmesg_boot0_clean.txt, 332K, 3349 lines).
> >
> > It contains all 76 "unused phy status page" events with both hex
> > dumps (4-byte grouped and byte-level) in full, plus all surrounding
> > kernel context.
> >
> > The interesting observation you made about the MAC addresses being
> > 24 bytes lower than expected is very helpful — I hadn't noticed the
> > offset discrepancy. If you need the adapter and AP MAC addresses
> > for reference:
> >
> >   Adapter: 8c:c8:4b:68:d1:63
> >   AP:      6c:68:a4:1c:97:5b
> >
> > And yes, adding a NULL check in rtw_fw_adaptivity_result() seems
> > like a good defensive measure regardless of the root cause.
> >
> > Let me know if you need anything else or a different format.
> >
> > Best regards,
> > Oleksandr Havrylov
> 
> I made a mistake with the second print_hex_dump. It was supposed to
> print from rxdesc + 56. But not to worry, I think this is sufficient.
> 
> Some of the frames have what looks like a valid PHY status at byte 24:
> 
> [ 9926.365048] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status
> page (7)
> [ 9926.365451] cachyos-x8664 kernel: 00000000: 05da26ac b587f0af 0aa2e765
> f48d78f5  .&......e....x..
> [ 9926.365475] cachyos-x8664 kernel: 00000010: 3ffe9e00 49d11a5c 00002701
> 012a0000  ...?\..I.'....*.
> [ 9926.365496] cachyos-x8664 kernel: 00000020: 00000014 20000000 000000e2
> 0000000a  ....... ........
> [ 9926.365537] cachyos-x8664 kernel: 00000030: 0000001c
> 00000000                    ........
> 
> But RTW_RX_DESC_W0_SHIFT is not 0. Then rtw88 looks for the PHY
> status in the wrong place, in this case at byte 25. The official
> driver always looks for it at byte 24:
> 
> https://github.com/lwfinger/rtw88/blob/master/alt_rtl8821ce/hal/rtl8821c/pci
> /rtl8821ce_recv.c#L272
> 
> Unfortunately fixing that won't be enough.
> 
> The way rtw88 configures the chip, RTW_RX_DESC_W0_DRV_INFO_SIZE is
> supposed to be either 0 or 4, but in these frames it has many other
> values.
> 
> In this case:
> 
> [ 9986.214022] cachyos-x8664 kernel: rtw_8821ce 0000:13:00.0: unused phy status
> page (2)
> [ 9986.214512] cachyos-x8664 kernel: 00000000: 95515588 50ad66d1 893f252f
> 77ef35ae  .UQ..f.P/%?..5.w
> [ 9986.214544] cachyos-x8664 kernel: 00000010: 3ffe1e00 4d626889 00404288
> 684bc88c  ...?.hbM.B@...Kh
> [ 9986.214572] cachyos-x8664 kernel: 00000020: 686c63d1 5b971ca4 1ca4686c
> 73205a97  .clh...[lh...Z s
> [ 9986.214599] cachyos-x8664 kernel: 00000030: 4a670000
> 000b2000                    ..gJ. ..
> 
> the 802.11 header immediately follows the RX descriptor (there is
> no PHY status, which is not unusual) but RTW_RX_DESC_W0_PHYST is 1.
> 
> In station mode RTW_RX_DESC_W1_MACID is supposed to be 0 or 1 (I think),
> mostly 0. In these frames it has many other values.
> 
> RTW_RX_DESC_W0_PKT_LEN sometimes exceeds 11454. In one case it's 0.
> 
> In many of these frames bytes 25..31 don't look like a PHY status
> or 802.11 header.
> 
> If we can't find the reason for these weird frames, maybe the best
> way to filter them out is to check RTW_RX_DESC_W0_DRV_INFO_SIZE.
> It takes care of 67 out of the 76 weird frames in dmesg_boot0_clean.txt.


Agree. It looks like we need more validations to drop weird frames.

I have never seen lots of this kind of weird frames before.
Oleksandr, is it possible to sum up the conditions these weird frames
happened? such as enter LPS? with BT devices? or something else. 

Ping-Ke

RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)

[Ping-Ke Shih]

LB F <goainwo@gmail.com> wrote:
> Ping-Ke Shih <pkshih@realtek.com> wrote:
> > I'd adopt your suggestion (dynamic LPS_DEEP_MODE_NONE) if the test
> > is positive.
> 
> Hi Ping-Ke,
> 
> Following your suggestion, I performed an additional experiment to
> validate the dynamic LPS_DEEP_MODE_NONE idea. Please treat this
> purely as a field test report -- I am not a kernel developer, and the
> implementation below is certainly not upstream-quality. I am sharing
> it only in the hope that it helps you design a proper solution.
> 
> What I did:
> 
> I extended your DMI quirk in pci.c with an additional capability flag
> for LPS Deep mode. The only file touched was pci.c (your patch) --
> main.c was left completely unmodified.
> 
> The changes to your patch are as follows:
> 
>   /* 1. Extended the capabilities enum */
>   enum rtw88_quirk_dis_pci_caps {
>           QUIRK_DIS_PCI_CAP_ASPM,
>           QUIRK_DIS_PCI_CAP_LPS_DEEP,  /* test addition */
>   };
> 
>   /* 2. Extended disable_pci_caps() callback */
>   static int disable_pci_caps(const struct dmi_system_id *dmi)
>   {
>           uintptr_t dis_caps = (uintptr_t)dmi->driver_data;
> 
>           if (dis_caps & BIT(QUIRK_DIS_PCI_CAP_ASPM))
>                   rtw_pci_disable_aspm = true;
> 
>           if (dis_caps & BIT(QUIRK_DIS_PCI_CAP_LPS_DEEP))
>                   rtw_disable_lps_deep_mode = true;
> 
>           return 1;
>   }
> 
>   /* 3. Both flags set for the HP P3S95EA#ACB entry */
>   .driver_data = (void *)(BIT(QUIRK_DIS_PCI_CAP_ASPM) |
>                           BIT(QUIRK_DIS_PCI_CAP_LPS_DEEP)),
> 
> I am aware that setting rtw_disable_lps_deep_mode from pci.c is
> architecturally impure -- it is a global flag that would affect all
> rtw88 devices in a hypothetical multi-adapter system. A proper
> per-device solution (e.g. a flag inside struct rtw_dev set during
> probe) would be cleaner. I simply used the existing global as the
> most straightforward way to validate the concept.
> 
> Verification:
> 
> Confirmed no rtw88-related entries exist in /etc/modprobe.d/,
> /lib/modprobe.d/, or /run/modprobe.d/, ruling out any external
> parameter injection.
> 
> After loading the patched modules, the following was confirmed via
> sysfs:
> 
>   /sys/module/rtw88_core/parameters/disable_lps_deep_mode = Y
>   /sys/module/rtw88_pci/parameters/disable_aspm = Y
> 
> This confirms the DMI quirk is the sole source of both values.
> 
> Results (10-minute idle observation, battery power, wifi.powersave=3):
> 
>   With your ASPM patch alone (LPS Deep still active):
>     - periodic "failed to send h2c command" bursts observed
>     - occasional WiFi throughput drops and Bluetooth audio stuttering
> 
>   With ASPM patch + LPS Deep disabled via the quirk:
>     - h2c=0, lps=0 across the entire observation window
>     - WiFi throughput stable, Bluetooth audio uninterrupted
> 
> The result confirms that disabling LPS Deep Mode in addition to ASPM
> completely eliminates the remaining firmware timeout loop on this
> platform.
> 
> I hope this experiment is useful as a data point. Please feel free to
> discard the implementation and design a proper solution -- I am ready
> to test any updated patch you send.

Thanks for your analysis of TX/RX paths, and the changes above and
verifications. :)

I'd update the patch as your proposal and send a patch. For suggestions of
TX/RX paths, I only read them a little bit, and I will study them entirely
when I have more free time. 

Ping-Ke