[BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Hello,

 Trying to get the Framework Laptop 13 AMD to work with QubesOS I hit the
following Xen issue :

Xen version : 4.17.2
Kernel : 6.5.12-300.fc39.x86_64
CPU  model name : AMD Ryzen 7 7840U w/ Radeon  780M Graphics

The touchpad is not working (not detected by evtest) because ( see below
for XXXXXXX values) :
[   10.215870] i2c_hid_acpi i2c-FRMXXXXXXX: failed to reset device: -61

which is maybe related to the previous messages :

[    2.065750] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
...
[    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt

QubesOS issue : https://github.com/QubesOS/qubes-issues/issues/8734

Possibly related issues :

 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971597

Here's the complete diff of dmesg with and without xen loaded up to the
failed i2c_hid_acpi init :

[    0.000000] Command line: placeholder
root=UUID=71b1dc59-ea00-484c-b5e4-ee77ede771db ro rhgb quiet
[    0.000000] Released 0 page(s)
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] efi: ACPI=0x5affe000 ACPI 2.0=0x5affe014
TPMFinalLog=0x5af3f000 SMBIOS=0x51677000 SMBIOS 3.0=0x51674000
(MEMATTR=0x4b719018 unusable) ESRT=0x5af9b018 MOKvar=0x5187c000
[    0.000000] Hypervisor detected: Xen PV
[    0.026644] tsc: Detected 3294.105 MHz processor
[    0.026645] tsc: Detected 3293.856 MHz TSC
[    0.026732] MTRR map: 3 entries (0 fixed + 3 variable; max 16), built
from 8 variable MTRRs
[    0.026733] MTRRs set to read-only
[    0.026735] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WC  WP  UC  UC

[    0.026753] esrt: Reserving ESRT space from 0x000000005af9b018 to
0x000000005af9b050.
[    1.042047] ACPI: BGRT 0x000000005AFB8000 000038 (v01 INSYDE EDK2
00000002 ACPI 00040000)
[    1.042095] Setting APIC routing to Xen PV.
[    1.042116] NUMA turned off
[    1.101730] On node 0, zone DMA: 128 pages in unavailable ranges
[    1.136828] p2m virtual area at (____ptrval____), size is 40000000
[    1.401457] Remapped 728641 page(s)
[    1.402499] Booting kernel on Xen
[    1.402500] Xen version: 4.17.2 (preserve-AD)
[    1.406607] xen: PV spinlocks enabled
[    1.406609] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes,
linear)
[    1.406610] Kernel command line: placeholder
root=UUID=71b1dc59-ea00-484c-b5e4-ee77ede771db ro rhgb quiet
[    1.406661] Unknown kernel command line parameters "placeholder rhgb",
will be passed to user space.
[    1.406867] random: crng init done
[    1.411447] Built 1 zonelists, mobility grouping on.  Total pages:
15403418
[    1.497107] Memory: 60184272K/62591736K available (18432K kernel code,
3267K rwdata, 14476K rodata, 4532K init, 17364K bss, 2407212K reserved, 0K
cma-reserved)
[    1.508627] xen:events: Using FIFO-based ABI
[    1.508634] xen: --> pirq=1 -> irq=1 (gsi=1)
[    1.508636] xen: --> pirq=2 -> irq=2 (gsi=2)
[    1.508638] xen: --> pirq=3 -> irq=3 (gsi=3)
[    1.508639] xen: --> pirq=4 -> irq=4 (gsi=4)
[    1.508640] xen: --> pirq=5 -> irq=5 (gsi=5)
[    1.508642] xen: --> pirq=6 -> irq=6 (gsi=6)
[    1.508643] xen: --> pirq=7 -> irq=7 (gsi=7)
[    1.508644] xen: --> pirq=8 -> irq=8 (gsi=8)
[    1.508646] xen: --> pirq=9 -> irq=9 (gsi=9)
[    1.508647] xen: --> pirq=10 -> irq=10 (gsi=10)
[    1.508649] xen: --> pirq=11 -> irq=11 (gsi=11)
[    1.508650] xen: --> pirq=12 -> irq=12 (gsi=12)
[    1.508652] xen: --> pirq=13 -> irq=13 (gsi=13)
[    1.508653] xen: --> pirq=14 -> irq=14 (gsi=14)
[    1.508654] xen: --> pirq=15 -> irq=15 (gsi=15)
[    1.508913] printk: console [hvc0] enabled
[    1.543395] ACPI BIOS Warning (bug): Incorrect checksum in table [BGRT]
- 0xC1, should be 0x4C (20230331/utcksum-58)
[    1.543432] clocksource: xen: mask: 0xffffffffffffffff max_cycles:
0x1cd42e4dffb, max_idle_ns: 881590591483 ns
[    1.543434] Xen: using vcpuop timer interface
[    1.543436] installing Xen timer for CPU 0
[    1.543449] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles:
0x2f7aa0787ee, max_idle_ns: 440795321263 ns
[    1.543452] Calibrating delay loop (skipped), value calculated using
timer frequency.. 6587.71 BogoMIPS (lpj=3293856)
[    1.543485] Spectre V2 : Mitigation: Retpolines
[    1.543487] Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT
[    1.543489] Speculative Store Bypass: Vulnerable
[    1.543505] x86/fpu: Enabled xstate features 0xe7, context size is 2432
bytes, using 'compacted' format.
[    1.556516] cpu 0 spinlock event irq 57
[    1.556526] VPMU disabled by hypervisor.
[    1.556812] Performance Events: PMU not available due to virtualization,
using software events only.
[    1.559433] NMI watchdog: Perf NMI watchdog permanently disabled
[    1.559727] installing Xen timer for CPU 1
[    1.559965] installing Xen timer for CPU 2
[    1.560180] installing Xen timer for CPU 3
[    1.560396] installing Xen timer for CPU 4
[    1.560599] installing Xen timer for CPU 5
[    1.560813] installing Xen timer for CPU 6
[    1.561021] installing Xen timer for CPU 7
[    1.561230] installing Xen timer for CPU 8
[    1.561420] installing Xen timer for CPU 9
[    1.561597] installing Xen timer for CPU 10
[    1.561783] installing Xen timer for CPU 11
[    1.561980] installing Xen timer for CPU 12
[    1.562155] installing Xen timer for CPU 13
[    1.562327] installing Xen timer for CPU 14
[    1.562503] installing Xen timer for CPU 15
[    1.562551] cpu 1 spinlock event irq 137
[    1.562551] cpu 2 spinlock event irq 138
[    1.562551] cpu 3 spinlock event irq 139
[    1.562551] cpu 4 spinlock event irq 140
[    1.562551] cpu 5 spinlock event irq 141
[    1.562551] cpu 6 spinlock event irq 142
[    1.562551] cpu 7 spinlock event irq 143
[    1.562551] cpu 8 spinlock event irq 144
[    1.563499] cpu 9 spinlock event irq 145
[    1.563502] cpu 10 spinlock event irq 146
[    1.563502] cpu 11 spinlock event irq 147
[    1.563502] cpu 12 spinlock event irq 148
[    1.563502] cpu 13 spinlock event irq 149
[    1.563502] cpu 14 spinlock event irq 150
[    1.563502] cpu 15 spinlock event irq 151
[    1.573211] PM: RTC time: 09:08:20, date: 2023-12-03
[    1.573947] xen:grant_table: Grant tables using version 1 layout
[    1.573958] Grant table initialized
[    1.574502] audit: type=2000 audit(1701594499.512:1): state=initialized
audit_enabled=0 res=1
[    1.606054] xen: registering gsi 9 triggering 0 polarity 1
[    1.697597] xen: registering gsi 8 triggering 1 polarity 0
[    1.697705] xen: registering gsi 13 triggering 1 polarity 0
[    1.700360] xen: registering gsi 7 triggering 0 polarity 1
[    1.700819] xen: registering gsi 10 triggering 1 polarity 0
[    1.701110] xen: registering gsi 6 triggering 1 polarity 0
[    1.701690] xen: registering gsi 50 triggering 0 polarity 1
[    1.701706] xen: --> pirq=50 -> irq=50 (gsi=50)
[    1.701757] xen: registering gsi 51 triggering 0 polarity 1
[    1.701768] xen: --> pirq=51 -> irq=51 (gsi=51)
[    1.701810] xen: registering gsi 52 triggering 0 polarity 1
[    1.701818] xen: --> pirq=52 -> irq=52 (gsi=52)
[    1.701860] xen: registering gsi 53 triggering 0 polarity 1
[    1.701869] xen: --> pirq=53 -> irq=53 (gsi=53)
[    1.707071] xen:balloon: Initialising balloon driver
[    1.743187] resource: Expanded resource Reserved due to conflict with
PCI Bus 0000:00
[    1.743524] sysfb: VRAM smaller than advertised
[    1.759417] hugetlbfs: disabling because there are no supported hugepage
sizes
[    1.765826] xen: registering gsi 1 triggering 1 polarity 0
[    1.771944] PM-Timer failed consistency check  (0xffffff) - aborting.
[    1.775360] xen: registering gsi 40 triggering 0 polarity 1
[    1.775387] xen: --> pirq=40 -> irq=40 (gsi=40)
[    1.775481] xen: registering gsi 37 triggering 0 polarity 1
[    1.775494] xen: --> pirq=37 -> irq=37 (gsi=37)
[    1.775841] xen: registering gsi 38 triggering 0 polarity 1
[    1.775855] xen: --> pirq=38 -> irq=38 (gsi=38)
[    1.776235] xen: registering gsi 40 triggering 0 polarity 1
[    1.776238] Already setup the GSI :40
[    1.776281] xen: registering gsi 46 triggering 0 polarity 1
[    1.776293] xen: --> pirq=46 -> irq=46 (gsi=46)
[    1.776646] xen: registering gsi 47 triggering 0 polarity 1
[    1.776656] xen: --> pirq=47 -> irq=47 (gsi=47)
[    1.777614] clocksource: tsc: mask: 0xffffffffffffffff max_cycles:
0x2f7aa0787ee, max_idle_ns: 440795321263 ns
[    1.777677] clocksource: Switched to clocksource tsc
[    2.061207] pcieport 0000:00:02.2: PME: Signaling with IRQ 162
[    2.061369] pcieport 0000:00:02.4: PME: Signaling with IRQ 163
[    2.061604] pcieport 0000:00:03.1: PME: Signaling with IRQ 164
[    2.062263] pcieport 0000:00:04.1: PME: Signaling with IRQ 165
[    2.062813] pcieport 0000:00:08.1: PME: Signaling with IRQ 166
[    2.062953] xen: registering gsi 40 triggering 0 polarity 1
[    2.062967] Already setup the GSI :40
[    2.063063] pcieport 0000:00:08.2: PME: Signaling with IRQ 167
[    2.063213] pcieport 0000:00:08.3: PME: Signaling with IRQ 168
[    2.063345] efifb: probing for efifb
[    2.063985] efifb: No BGRT, not showing boot graphics
[    2.063986] efifb: framebuffer at 0x8800000000, using 13536k, total
13536k
[    2.063988] efifb: mode is 2256x1504x32, linelength=9216, pages=1
[    2.063989] efifb: scrolling: redraw
[    2.063990] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[    2.064032] fbcon: Deferring console take-over
[    2.064033] fb0: EFI VGA frame buffer device
[    2.065750] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.065860] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.066008] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.066140] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.066370] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.066586] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.066818] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.066923] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.067082] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.067170] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.067296] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.067473] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.067669] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.067973] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.068215] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.068522] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
(0x0)
[    2.068923] ACPI: thermal: Thermal Zone [TZ00] (26 C)
[    2.069085] ACPI: thermal: Thermal Zone [TZ01] (30 C)
[    2.069242] ACPI: thermal: Thermal Zone [TZ02] (28 C)
[    2.069402] ACPI: thermal: Thermal Zone [TZ03] (46 C)
[    2.072038] hpet_acpi_add: no address or irqs in _CRS
[    2.092763] xen: registering gsi 37 triggering 0 polarity 1
[    2.092769] Already setup the GSI :37
[    2.101751] xen: registering gsi 38 triggering 0 polarity 1
[    2.101755] Already setup the GSI :38
[    2.105493] xen: registering gsi 46 triggering 0 polarity 1
[    2.105496] Already setup the GSI :46
[    2.109521] xen: registering gsi 47 triggering 0 polarity 1
[    2.109525] Already setup the GSI :47
[    2.116721] rtc_cmos 00:01: setting system clock to 2023-12-03T09:08:21
UTC (1701594501)
[    2.117134] amd_pstate: driver load is disabled, boot with specific mode
to enable this
[    2.130271] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input2
[    2.138905] sched_clock: Marking stable (2104001974,
34790120)->(2142780210, -3988116)
[    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.465229] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.465462] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.465694] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.466003] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.466189] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.466387] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.466584] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    3.790268]     placeholder
[    3.809946] usb 1-2: New USB device found, idVendor=1e7d,
idProduct=2e22, bcdDevice= 1.01
[    3.809950] usb 1-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[    3.809952] usb 1-2: Product: ROCCAT Kone XTD
[    3.809953] usb 1-2: Manufacturer: ROCCAT
[    3.826019] systemd[1]: Detected virtualization vm-other.
[    3.941883] usb 1-4: new full-speed USB device number 3 using xhci_hcd
[    4.099853] usb 1-4: New USB device found, idVendor=27c6,
idProduct=609c, bcdDevice= 1.00
[    4.099862] usb 1-4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[    4.099866] usb 1-4: Product: Goodix USB2.0 MISC
[    4.099869] usb 1-4: Manufacturer: Goodix Technology Co., Ltd.
[    4.099873] usb 1-4: SerialNumber: UIDD5F04A7B_XXXX_MOC_B0
[    4.193119] systemd[1]: Finished kmod-static-nodes.service - Create List
of Static Device Nodes.
[    4.221808] usb 1-5: new high-speed USB device number 4 using xhci_hcd
[    4.936497] xen: registering gsi 36 triggering 0 polarity 1
[    4.936543] xen: --> pirq=36 -> irq=36 (gsi=36)
[    4.948276] ccp 0000:c1:00.2: tee: ring init command failed (0x00000005)
[    4.948285] ccp 0000:c1:00.2: tee: failed to init ring buffer
[    4.948287] ccp 0000:c1:00.2: tee initialization failed
[    4.948302] ccp 0000:c1:00.2: psp initialization failed
[    5.018031] fbcon: Taking over console
[    5.018181] Console: switching to colour frame buffer device 282x94
[   10.215870] i2c_hid_acpi i2c-FRMW0005:00: failed to reset device: -61
[   10.215917] i2c_hid_acpi i2c-PIXA3854:00: failed to reset device: -61
[   10.215950] i2c_hid_acpi i2c-FRMW0004:00: failed to reset device: -61
[   10.220217] i2c_hid_acpi i2c-FRMW0004:00: failed to change power setting.
[   16.359856] i2c_hid_acpi i2c-PIXA3854:00: failed to reset device: -61
[   16.359856] i2c_hid_acpi i2c-FRMW0004:00: failed to reset device: -61
[   16.359871] i2c_hid_acpi i2c-FRMW0005:00: failed to reset device: -61
[   22.503879] i2c_hid_acpi i2c-FRMW0005:00: failed to reset device: -61
[   22.503915] i2c_hid_acpi i2c-PIXA3854:00: failed to reset device: -61
[   22.503921] i2c_hid_acpi i2c-FRMW0004:00: failed to reset device: -61
[   28.647874] i2c_hid_acpi i2c-FRMW0005:00: failed to reset device: -61
[   28.647879] i2c_hid_acpi i2c-PIXA3854:00: failed to reset device: -61
[   28.647910] i2c_hid_acpi i2c-FRMW0004:00: failed to reset device: -61
[   29.671873] i2c_hid_acpi i2c-FRMW0005:00: can't add hid device: -61
[   29.671874] i2c_hid_acpi i2c-FRMW0004:00: can't add hid device: -61
[   29.671874] i2c_hid_acpi i2c-PIXA3854:00: can't add hid device: -61
[   29.686460] i2c_hid_acpi: probe of i2c-FRMW0005:00 failed with error -61
[   29.686492] i2c_hid_acpi: probe of i2c-PIXA3854:00 failed with error -61
[   29.686683] i2c_hid_acpi: probe of i2c-FRMW0004:00 failed with error -61

Thanks
Sébastien

[-- Attachment #2: Type: text/html, Size: 17010 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 03.12.2023 10:56, Sébastien Chaumat wrote:
> Hello,
> 
>  Trying to get the Framework Laptop 13 AMD to work with QubesOS I hit the
> following Xen issue :
> 
> Xen version : 4.17.2
> Kernel : 6.5.12-300.fc39.x86_64
> CPU  model name : AMD Ryzen 7 7840U w/ Radeon  780M Graphics
> 
> The touchpad is not working (not detected by evtest) because ( see below
> for XXXXXXX values) :
> [   10.215870] i2c_hid_acpi i2c-FRMXXXXXXX: failed to reset device: -61
> 
> which is maybe related to the previous messages :
> 
> [    2.065750] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW
> (0x0)

Not very likely to be connected to this. Afaict you'll see these on all
systems.

> ...
> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt

Possibly releated to this. You'll want to obtain a full-verbosity hypervisor
log with a debug hypervisor, as there may be hypervisor debug messages
telling us what Xen may not like.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

[-- Attachment #1.1: Type: text/plain, Size: 736 bytes --]

Le lun. 4 déc. 2023 à 10:06, Jan Beulich <jbeulich@suse.com> a écrit :

> On 03.12.2023 10:56, Sébastien Chaumat wrote:
> > Hello,
> >
> >  Trying to get the Framework Laptop 13 AMD to work with QubesOS I hit the
> > following Xen issue :
> >
> > Xen version : 4.17.2
>
+ tested with 4.18.0


> > Kernel : 6.5.12-300.fc39.x86_64
> > CPU  model name : AMD Ryzen 7 7840U w/ Radeon  780M Graphics
>


> > [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
>
> Possibly releated to this. You'll want to obtain a full-verbosity
> hypervisor
> log with a debug hypervisor, as there may be hypervisor debug messages
> telling us what Xen may not like.
>

xl dmesg with some traces attached.

[-- Attachment #1.2: Type: text/html, Size: 1444 bytes --]

[-- Attachment #2: xl-dmesg-4.18.txt.gz --]
[-- Type: application/gzip, Size: 7105 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 04.12.2023 20:17, Sébastien Chaumat wrote:
> Le lun. 4 déc. 2023 à 10:06, Jan Beulich <jbeulich@suse.com> a écrit :
> 
>> On 03.12.2023 10:56, Sébastien Chaumat wrote:
>>> Hello,
>>>
>>>  Trying to get the Framework Laptop 13 AMD to work with QubesOS I hit the
>>> following Xen issue :
>>>
>>> Xen version : 4.17.2
>>
> + tested with 4.18.0
> 
> 
>>> Kernel : 6.5.12-300.fc39.x86_64
>>> CPU  model name : AMD Ryzen 7 7840U w/ Radeon  780M Graphics
>>
> 
> 
>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
>>
>> Possibly releated to this. You'll want to obtain a full-verbosity
>> hypervisor
>> log with a debug hypervisor, as there may be hypervisor debug messages
>> telling us what Xen may not like.
>>
> 
> xl dmesg with some traces attached.

Nothing that looks relevant here. The anomalies are related to you also
having enabled lock debugging and ubsan.

I'm afraid this needs looking into from the kernel side first, to understand
what's going wrong there. Once that's known, it'll hopefully be more clear
whether this is a Xen or a kernel issue.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Any direction on how I can enhance the debugging at the kernel level ?

There was an old issue with amd_gpio there :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971597
Coud the kernel be confused by IRQ/GSI mapping ? Any way to test this
hypothesis?

Thanks




Le mar. 5 déc. 2023 à 09:17, Jan Beulich <jbeulich@suse.com> a écrit :

> On 04.12.2023 20:17, Sébastien Chaumat wrote:
> > Le lun. 4 déc. 2023 à 10:06, Jan Beulich <jbeulich@suse.com> a écrit :
> >
> >> On 03.12.2023 10:56, Sébastien Chaumat wrote:
> >>> Hello,
> >>>
> >>>  Trying to get the Framework Laptop 13 AMD to work with QubesOS I hit
> the
> >>> following Xen issue :
> >>>
> >>> Xen version : 4.17.2
> >>
> > + tested with 4.18.0
> >
> >
> >>> Kernel : 6.5.12-300.fc39.x86_64
> >>> CPU  model name : AMD Ryzen 7 7840U w/ Radeon  780M Graphics
> >>
> >
> >
> >>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> >>
> >> Possibly releated to this. You'll want to obtain a full-verbosity
> >> hypervisor
> >> log with a debug hypervisor, as there may be hypervisor debug messages
> >> telling us what Xen may not like.
> >>
> >
> > xl dmesg with some traces attached.
>
> Nothing that looks relevant here. The anomalies are related to you also
> having enabled lock debugging and ubsan.
>
> I'm afraid this needs looking into from the kernel side first, to
> understand
> what's going wrong there. Once that's known, it'll hopefully be more clear
> whether this is a Xen or a kernel issue.
>
> Jan
>

[-- Attachment #2: Type: text/html, Size: 2346 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

Le mar. 5 déc. 2023 à 09:50, Sébastien Chaumat <euidzero@gmail.com> a écrit :
>
> Any direction on how I can enchance the debugging at the kernel level ?
>
> There was an old issue with amd_gpio there : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971597
> Coud the kernel be confused by IRQ/GSI mapping ? Any way to test this hypothesis?
>

Interestingly only one result when searching for the amg_gpio " failed
to enable wake-up interrupt" message :

in the dmesg attached to thread about Ryzen 6000 :
 https://lists.xenproject.org/archives/html/xen-devel/2022-08/msg00927.html

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

 booting kernel with "dyndbg=file drivers/gpio/* +p"

[    1.997798] i2c_designware AMDI0010:00: using ACPI '\_SB.I2CA' for
'scl' GPIO lookup
[    1.997804] acpi AMDI0010:00: GPIO: looking up scl-gpios
[    1.997806] acpi AMDI0010:00: GPIO: looking up scl-gpio
[    1.997807] i2c_designware AMDI0010:00: using lookup tables for GPIO lookup
[    1.997809] i2c_designware AMDI0010:00: No GPIO consumer scl found
[    2.007517] i2c_designware AMDI0010:03: using ACPI '\_SB.I2CD' for
'scl' GPIO lookup
[    2.007521] acpi AMDI0010:03: GPIO: looking up scl-gpios
[    2.007523] acpi AMDI0010:03: GPIO: looking up scl-gpio
[    2.007524] i2c_designware AMDI0010:03: using lookup tables for GPIO lookup
[    2.007526] i2c_designware AMDI0010:03: No GPIO consumer scl found
[    2.343905] gpiochip_find_base: found new base at 512
[    2.344408] gpio gpiochip0: Persistence not supported for GPIO 0
[    2.344436] gpio gpiochip0: Persistence not supported for GPIO 61
[    2.344458] gpio gpiochip0: Persistence not supported for GPIO 62
[    2.344480] gpio gpiochip0: Persistence not supported for GPIO 58
[    2.344502] gpio gpiochip0: Persistence not supported for GPIO 59
[    2.344523] gpio gpiochip0: Persistence not supported for GPIO 2
[    2.344546] gpio gpiochip0: Persistence not supported for GPIO 6
[    2.344571] gpio gpiochip0: Persistence not supported for GPIO 54
[    2.344646] gpio gpiochip0: (AMDI0030:00): added GPIO chardev (254:0)
[    2.344648] gpio gpiochip0: registered GPIOs 512 to 767 on AMDI0030:00
[    2.344650] gpio gpiochip0: (AMDI0030:00): created GPIO range
0->255 ==> AMDI0030:00 PIN 0->255
[    2.357663] acpi MSFT0101:00: GPIO: looking up 0 in _CRS
[    2.376188] mdio_bus fixed-0: using lookup tables for GPIO lookup
[    2.376193] mdio_bus fixed-0: No GPIO consumer reset found
[    2.401459] rtc_cmos 00:01: using ACPI '\_SB.PCI0.LPC0.RTC' for
'wp' GPIO lookup
[    2.401464] acpi PNP0B00:00: GPIO: looking up wp-gpios
[    2.401465] acpi PNP0B00:00: GPIO: looking up wp-gpio
[    2.401467] rtc_cmos 00:01: using lookup tables for GPIO lookup
[    2.401468] rtc_cmos 00:01: No GPIO consumer wp found
[    2.659765] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.660047] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.660162] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.660277] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.660393] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.660504] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.660609] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    2.660726] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    5.445265] acpi FRMW0004:00: GPIO: looking up 0 in _CRS
[    5.445396] acpi FRMW0005:00: GPIO: looking up 0 in _CRS
[    5.448467] acpi PIXA3854:00: GPIO: looking up 0 in _CRS
[    5.448483] gpio gpiochip0: Persistence not supported for GPIO 84
[    5.452476] gpio gpiochip0: Persistence not supported for GPIO 5
[    5.463304] gpio gpiochip0: Persistence not supported for GPIO 8

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 05.12.2023 15:14, Sébastien Chaumat wrote:
>  booting kernel with "dyndbg=file drivers/gpio/* +p"

I'm afraid this doesn't tell me anything. I'm simply not familiar with
Linux'es GPIO handling.

Jan

> [    1.997798] i2c_designware AMDI0010:00: using ACPI '\_SB.I2CA' for
> 'scl' GPIO lookup
> [    1.997804] acpi AMDI0010:00: GPIO: looking up scl-gpios
> [    1.997806] acpi AMDI0010:00: GPIO: looking up scl-gpio
> [    1.997807] i2c_designware AMDI0010:00: using lookup tables for GPIO lookup
> [    1.997809] i2c_designware AMDI0010:00: No GPIO consumer scl found
> [    2.007517] i2c_designware AMDI0010:03: using ACPI '\_SB.I2CD' for
> 'scl' GPIO lookup
> [    2.007521] acpi AMDI0010:03: GPIO: looking up scl-gpios
> [    2.007523] acpi AMDI0010:03: GPIO: looking up scl-gpio
> [    2.007524] i2c_designware AMDI0010:03: using lookup tables for GPIO lookup
> [    2.007526] i2c_designware AMDI0010:03: No GPIO consumer scl found
> [    2.343905] gpiochip_find_base: found new base at 512
> [    2.344408] gpio gpiochip0: Persistence not supported for GPIO 0
> [    2.344436] gpio gpiochip0: Persistence not supported for GPIO 61
> [    2.344458] gpio gpiochip0: Persistence not supported for GPIO 62
> [    2.344480] gpio gpiochip0: Persistence not supported for GPIO 58
> [    2.344502] gpio gpiochip0: Persistence not supported for GPIO 59
> [    2.344523] gpio gpiochip0: Persistence not supported for GPIO 2
> [    2.344546] gpio gpiochip0: Persistence not supported for GPIO 6
> [    2.344571] gpio gpiochip0: Persistence not supported for GPIO 54
> [    2.344646] gpio gpiochip0: (AMDI0030:00): added GPIO chardev (254:0)
> [    2.344648] gpio gpiochip0: registered GPIOs 512 to 767 on AMDI0030:00
> [    2.344650] gpio gpiochip0: (AMDI0030:00): created GPIO range
> 0->255 ==> AMDI0030:00 PIN 0->255
> [    2.357663] acpi MSFT0101:00: GPIO: looking up 0 in _CRS
> [    2.376188] mdio_bus fixed-0: using lookup tables for GPIO lookup
> [    2.376193] mdio_bus fixed-0: No GPIO consumer reset found
> [    2.401459] rtc_cmos 00:01: using ACPI '\_SB.PCI0.LPC0.RTC' for
> 'wp' GPIO lookup
> [    2.401464] acpi PNP0B00:00: GPIO: looking up wp-gpios
> [    2.401465] acpi PNP0B00:00: GPIO: looking up wp-gpio
> [    2.401467] rtc_cmos 00:01: using lookup tables for GPIO lookup
> [    2.401468] rtc_cmos 00:01: No GPIO consumer wp found
> [    2.659765] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> [    2.660047] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> [    2.660162] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> [    2.660277] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> [    2.660393] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> [    2.660504] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> [    2.660609] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> [    2.660726] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> [    5.445265] acpi FRMW0004:00: GPIO: looking up 0 in _CRS
> [    5.445396] acpi FRMW0005:00: GPIO: looking up 0 in _CRS
> [    5.448467] acpi PIXA3854:00: GPIO: looking up 0 in _CRS
> [    5.448483] gpio gpiochip0: Persistence not supported for GPIO 84
> [    5.452476] gpio gpiochip0: Persistence not supported for GPIO 5
> [    5.463304] gpio gpiochip0: Persistence not supported for GPIO 8

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

Le mar. 5 déc. 2023 à 15:18, Jan Beulich <jbeulich@suse.com> a écrit :
>
> On 05.12.2023 15:14, Sébastien Chaumat wrote:
> >  booting kernel with "dyndbg=file drivers/gpio/* +p"
>
> I'm afraid this doesn't tell me anything. I'm simply not familiar with
> Linux'es GPIO handling.
>
Thanks for your help so far.
I moved  the issue to linux-gpio devs  :

https://marc.info/?l=linux-gpio&m=170177779023453&w=1

Sébastien

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt

Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
ioapic-edge and IRQ9 to ioapic-level ?

IR-IO-APIC    7-fasteoi   pinctrl_amd
IR-IO-APIC    9-fasteoi   acpi

to (xen 4.18.0)

xen-pirq     -ioapic-edge  pinctrl_amd
xen-pirq     -ioapic-level  acpi

?

THX

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 05.12.2023 21:31, Sébastien Chaumat wrote:
>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> 
> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
> ioapic-edge and IRQ9 to ioapic-level ?
> 
> IR-IO-APIC    7-fasteoi   pinctrl_amd
> IR-IO-APIC    9-fasteoi   acpi
> 
> to (xen 4.18.0)
> 
> xen-pirq     -ioapic-edge  pinctrl_amd
> xen-pirq     -ioapic-level  acpi
> 
> ?

Aren't you comparing different things here? IR-* pretty clearly is on a
native kernel (no Xen). It being "edge" looks suspicious, though.

But again - I'm not primarily a kernel person, and hence you continuing
to send replies To: me feels at least odd.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

> On 05.12.2023 21:31, Sébastien Chaumat wrote:
> >> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> >
> > Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
> > ioapic-edge and IRQ9 to ioapic-level ?
> >
> > IR-IO-APIC    7-fasteoi   pinctrl_amd
> > IR-IO-APIC    9-fasteoi   acpi
> >
> > to (xen 4.18.0)
> >
> > xen-pirq     -ioapic-edge  pinctrl_amd
> > xen-pirq     -ioapic-level  acpi
> >
> > ?

On the i2c side I managed to isolate the following error with
xen-4.19-unstable and Linux 6.7.0-rc4 :

i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: slave address not
acknowledged (7bit mode)

Any ideas  ? What kernel debug messages would be useful next ?

Thanks
Sébastien

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

Le lun. 11 déc. 2023 à 10:18, Sébastien Chaumat <euidzero@gmail.com> a écrit :
>
> > On 05.12.2023 21:31, Sébastien Chaumat wrote:
> > >> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> > >
> > > Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
> > > ioapic-edge and IRQ9 to ioapic-level ?
> > >
> > > IR-IO-APIC    7-fasteoi   pinctrl_amd
> > > IR-IO-APIC    9-fasteoi   acpi
> > >
> > > to (xen 4.18.0)
> > >
> > > xen-pirq     -ioapic-edge  pinctrl_amd
> > > xen-pirq     -ioapic-level  acpi
> > >
> > > ?

This look similar to
https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/

This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
(so level type) while in xen it  is mapped to oapic-edge  instead of
oapic-level
as the SSDT indicates :

 Device (GPIO)

     {
         Name (_HID, "AMDI0030")  // _HID: Hardware ID
         Name (_CID, "AMDI0030")  // _CID: Compatible ID
         Name (_UID, Zero)  // _UID: Unique ID
         Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
         {
             Name (RBUF, ResourceTemplate ()
             {
                 Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
                 {
                     0x00000007,
           }
Any idea why ?

Sébastien

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 11.12.2023 12:09, Sébastien Chaumat wrote:
> Le lun. 11 déc. 2023 à 10:18, Sébastien Chaumat <euidzero@gmail.com> a écrit :
>>
>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
>>>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
>>>>
>>>> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
>>>> ioapic-edge and IRQ9 to ioapic-level ?
>>>>
>>>> IR-IO-APIC    7-fasteoi   pinctrl_amd
>>>> IR-IO-APIC    9-fasteoi   acpi
>>>>
>>>> to (xen 4.18.0)
>>>>
>>>> xen-pirq     -ioapic-edge  pinctrl_amd
>>>> xen-pirq     -ioapic-level  acpi
>>>>
>>>> ?
> 
> This look similar to
> https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/
> 
> This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
> (so level type) while in xen it  is mapped to oapic-edge  instead of
> oapic-level
> as the SSDT indicates :
> 
>  Device (GPIO)
> 
>      {
>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
>          Name (_UID, Zero)  // _UID: Unique ID
>          Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
>          {
>              Name (RBUF, ResourceTemplate ()
>              {
>                  Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
>                  {
>                      0x00000007,
>            }
> Any idea why ?

Information coming from AML is required to be handed down by Dom0 to Xen.
May want checking that (a) Dom0 properly does so and (b) Xen doesn't screw
up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7 is
also the spurious vector. You may want to retry with the tip of the 4.17
branch (soon to become 4.17.3) - while it doesn't look very likely to me
that recent backports there were related, it may still be that they make
a difference.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

Le lun. 11 déc. 2023 à 12:27, Jan Beulich <jbeulich@suse.com> a écrit :
>
> On 11.12.2023 12:09, Sébastien Chaumat wrote:
> > Le lun. 11 déc. 2023 à 10:18, Sébastien Chaumat <euidzero@gmail.com> a écrit :
> >>
> >>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
> >>>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> >>>>
> >>>> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
> >>>> ioapic-edge and IRQ9 to ioapic-level ?
> >>>>
> >>>> IR-IO-APIC    7-fasteoi   pinctrl_amd
> >>>> IR-IO-APIC    9-fasteoi   acpi
> >>>>
> >>>> to (xen 4.18.0)
> >>>>
> >>>> xen-pirq     -ioapic-edge  pinctrl_amd
> >>>> xen-pirq     -ioapic-level  acpi
> >>>>
> >>>> ?
> >
> > This look similar to
> > https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/
> >
> > This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
> > (so level type) while in xen it  is mapped to oapic-edge  instead of
> > oapic-level
> > as the SSDT indicates :
> >
> >  Device (GPIO)
> >
> >      {
> >          Name (_HID, "AMDI0030")  // _HID: Hardware ID
> >          Name (_CID, "AMDI0030")  // _CID: Compatible ID
> >          Name (_UID, Zero)  // _UID: Unique ID
> >          Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
> >          {
> >              Name (RBUF, ResourceTemplate ()
> >              {
> >                  Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
> >                  {
> >                      0x00000007,
> >            }
> > Any idea why ?
>
> Information coming from AML is required to be handed down by Dom0 to Xen.
> May want checking that (a) Dom0 properly does so and (b) Xen doesn't screw
> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
> specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7 is
> also the spurious vector. You may want to retry with the tip of the 4.17
> branch (soon to become 4.17.3) - while it doesn't look very likely to me
> that recent backports there were related, it may still be that they make
> a difference.

Tried 4.17.3-pre : no change
How would you check (a) and (b) exactly (I need technical directions here)?

Any way to force IRQ7 to ioapic-level to test the hypothesis ?

Thanks
Sébastien

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

> > Information coming from AML is required to be handed down by Dom0 to Xen.
> > May want checking that (a) Dom0 properly does so and (b) Xen doesn't screw
> > up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
> > specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7 is
> > also the spurious vector. You may want to retry with the tip of the 4.17
> > branch (soon to become 4.17.3) - while it doesn't look very likely to me
> > that recent backports there were related, it may still be that they make
> > a difference.
>
> Tried 4.17.3-pre : no change
> How would you check (a) and (b) exactly (I need technical directions here)?
>
b) hvm_level=512 ?

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

> >>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
> >>>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> >>>>
> >>>> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
> >>>> ioapic-edge and IRQ9 to ioapic-level ?
> >>>>
> >>>> IR-IO-APIC    7-fasteoi   pinctrl_amd
> >>>> IR-IO-APIC    9-fasteoi   acpi
> >>>>
> >>>> to (xen 4.18.0)
> >>>>
> >>>> xen-pirq     -ioapic-edge  pinctrl_amd
> >>>> xen-pirq     -ioapic-level  acpi
> >>>>
> >>>> ?
> >

> > This look similar to
> > https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/
> >
> > This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
> > (so level type) while in xen it  is mapped to oapic-edge  instead of
> > oapic-level
> > as the SSDT indicates :
> >
> >  Device (GPIO)
> >
> >      {
> >          Name (_HID, "AMDI0030")  // _HID: Hardware ID
> >          Name (_CID, "AMDI0030")  // _CID: Compatible ID
> >          Name (_UID, Zero)  // _UID: Unique ID
> >          Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
> >          {
> >              Name (RBUF, ResourceTemplate ()
> >              {
> >                  Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
> >                  {
> >                      0x00000007,
> >            }
> > Any idea why ?
>
> Information coming from AML is required to be handed down by Dom0 to Xen.
> May want checking that (a) Dom0 properly does so and (b) Xen doesn't screw
> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
> specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7 is
> also the spurious vector. You may want to retry with the tip of the 4.17
> branch (soon to become 4.17.3) - while it doesn't look very likely to me
> that recent backports there were related, it may still be that they make
> a difference.
>

testing with 4.17.3:

Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)  that
(XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1 polarity: 1

but later on in dmesg I see :
[    1.747958] xen: registering gsi 7 triggering 0 polarity 1

So triggering is flipped from 1 to 0 (cannot find the definition for
those values).
Could this be the culprit ?

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 18.12.2023 17:21, Sébastien Chaumat wrote:
>>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
>>> This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
>>> (so level type) while in xen it  is mapped to oapic-edge  instead of
>>> oapic-level
>>> as the SSDT indicates :
>>>
>>>  Device (GPIO)
>>>
>>>      {
>>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
>>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
>>>          Name (_UID, Zero)  // _UID: Unique ID
>>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
>>>          {
>>>              Name (RBUF, ResourceTemplate ()
>>>              {
>>>                  Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
>>>                  {
>>>                      0x00000007,
>>>            }
>>> Any idea why ?
>>
>> Information coming from AML is required to be handed down by Dom0 to Xen.
>> May want checking that (a) Dom0 properly does so and (b) Xen doesn't screw
>> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
>> specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7 is
>> also the spurious vector. You may want to retry with the tip of the 4.17
>> branch (soon to become 4.17.3) - while it doesn't look very likely to me
>> that recent backports there were related, it may still be that they make
>> a difference.
>>
> 
> testing with 4.17.3:
> 
> Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)  that
> (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1 polarity: 1
> 
> but later on in dmesg I see :
> [    1.747958] xen: registering gsi 7 triggering 0 polarity 1
> 
> So triggering is flipped from 1 to 0 (cannot find the definition for
> those values).
> Could this be the culprit ?

Possibly. Since it would be the kernel to invoke PHYSDEVOP_setup_gsi, it
looks as if the kernel was confused about which trigger mode to use. Have
you figured from where the kernel takes the two different values?

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le lun. 18 déc. 2023, 17:44, Jan Beulich <jbeulich@suse.com> a écrit :

> On 18.12.2023 17:21, Sébastien Chaumat wrote:
> >>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
> >>> This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
> >>> (so level type) while in xen it  is mapped to oapic-edge  instead of
> >>> oapic-level
> >>> as the SSDT indicates :
> >>>
> >>>  Device (GPIO)
> >>>
> >>>      {
> >>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
> >>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
> >>>          Name (_UID, Zero)  // _UID: Unique ID
> >>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource
> Settings
> >>>          {
> >>>              Name (RBUF, ResourceTemplate ()
> >>>              {
> >>>                  Interrupt (ResourceConsumer, Level, ActiveLow,
> Shared, ,, )
> >>>                  {
> >>>                      0x00000007,
> >>>            }
> >>> Any idea why ?
> >>
> >> Information coming from AML is required to be handed down by Dom0 to
> Xen.
> >> May want checking that (a) Dom0 properly does so and (b) Xen doesn't
> screw
> >> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
> >> specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7
> is
> >> also the spurious vector. You may want to retry with the tip of the 4.17
> >> branch (soon to become 4.17.3) - while it doesn't look very likely to me
> >> that recent backports there were related, it may still be that they make
> >> a difference.
> >>
> >
> > testing with 4.17.3:
> >
> > Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)  that
> > (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1 polarity: 1
> >
> > but later on in dmesg I see :
> > [    1.747958] xen: registering gsi 7 triggering 0 polarity 1
> >
> > So triggering is flipped from 1 to 0 (cannot find the definition for
> > those values).
> > Could this be the culprit ?
>
> Possibly. Since it would be the kernel to invoke PHYSDEVOP_setup_gsi, it
> looks as if the kernel was confused about which trigger mode to use. Have
> you figured from where the kernel takes the two different values?
>

> Would you mind pointing me to the definition for those values first ? I
did not find what 0/1 means in this context.

Thanks

[-- Attachment #2: Type: text/html, Size: 3703 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

Le lun. 18 déc. 2023 à 18:04, Sébastien Chaumat <euidzero@gmail.com> a écrit :
>
>
>
> Le lun. 18 déc. 2023, 17:44, Jan Beulich <jbeulich@suse.com> a écrit :
>>
>> On 18.12.2023 17:21, Sébastien Chaumat wrote:
>> >>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
>> >>> This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
>> >>> (so level type) while in xen it  is mapped to oapic-edge  instead of
>> >>> oapic-level
>> >>> as the SSDT indicates :
>> >>>
>> >>>  Device (GPIO)
>> >>>
>> >>>      {
>> >>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
>> >>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
>> >>>          Name (_UID, Zero)  // _UID: Unique ID
>> >>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
>> >>>          {
>> >>>              Name (RBUF, ResourceTemplate ()
>> >>>              {
>> >>>                  Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
>> >>>                  {
>> >>>                      0x00000007,
>> >>>            }
>> >>> Any idea why ?
>> >>
>> >> Information coming from AML is required to be handed down by Dom0 to Xen.
>> >> May want checking that (a) Dom0 properly does so and (b) Xen doesn't screw
>> >> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
>> >> specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7 is
>> >> also the spurious vector. You may want to retry with the tip of the 4.17
>> >> branch (soon to become 4.17.3) - while it doesn't look very likely to me
>> >> that recent backports there were related, it may still be that they make
>> >> a difference.
>> >>
>> >
>> > testing with 4.17.3:
>> >
>> > Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)  that
>> > (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1 polarity: 1
>> >
>> > but later on in dmesg I see :
>> > [    1.747958] xen: registering gsi 7 triggering 0 polarity 1
>> >
>> > So triggering is flipped from 1 to 0 (cannot find the definition for
>> > those values).
>> > Could this be the culprit ?
>>
>> Possibly. Since it would be the kernel to invoke PHYSDEVOP_setup_gsi, it
>> looks as if the kernel was confused about which trigger mode to use. Have
>> you figured from where the kernel takes the two different values?
>>
side note : dom0 is PV.

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 18.12.2023 18:04, Sébastien Chaumat wrote:
> Le lun. 18 déc. 2023, 17:44, Jan Beulich <jbeulich@suse.com> a écrit :
> 
>> On 18.12.2023 17:21, Sébastien Chaumat wrote:
>>>>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
>>>>> This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
>>>>> (so level type) while in xen it  is mapped to oapic-edge  instead of
>>>>> oapic-level
>>>>> as the SSDT indicates :
>>>>>
>>>>>  Device (GPIO)
>>>>>
>>>>>      {
>>>>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
>>>>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
>>>>>          Name (_UID, Zero)  // _UID: Unique ID
>>>>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource
>> Settings
>>>>>          {
>>>>>              Name (RBUF, ResourceTemplate ()
>>>>>              {
>>>>>                  Interrupt (ResourceConsumer, Level, ActiveLow,
>> Shared, ,, )
>>>>>                  {
>>>>>                      0x00000007,
>>>>>            }
>>>>> Any idea why ?
>>>>
>>>> Information coming from AML is required to be handed down by Dom0 to
>> Xen.
>>>> May want checking that (a) Dom0 properly does so and (b) Xen doesn't
>> screw
>>>> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
>>>> specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7
>> is
>>>> also the spurious vector. You may want to retry with the tip of the 4.17
>>>> branch (soon to become 4.17.3) - while it doesn't look very likely to me
>>>> that recent backports there were related, it may still be that they make
>>>> a difference.
>>>>
>>>
>>> testing with 4.17.3:
>>>
>>> Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)  that
>>> (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1 polarity: 1
>>>
>>> but later on in dmesg I see :
>>> [    1.747958] xen: registering gsi 7 triggering 0 polarity 1
>>>
>>> So triggering is flipped from 1 to 0 (cannot find the definition for
>>> those values).
>>> Could this be the culprit ?
>>
>> Possibly. Since it would be the kernel to invoke PHYSDEVOP_setup_gsi, it
>> looks as if the kernel was confused about which trigger mode to use. Have
>> you figured from where the kernel takes the two different values?
>>
> 
>> Would you mind pointing me to the definition for those values first ? I
> did not find what 0/1 means in this context.

See e.g. the IO-APIC spec, or Xen's io_apic.h:

struct IO_APIC_route_entry {
    ...
            unsigned int polarity:1;      /* 0: low, 1: high */
    ...
            unsigned int trigger:1;       /* 0: edge, 1: level */

(Sadly the comment may be the wrong way round for polarity, but then I
may also be missing something, as msi.h and apicdef.h suggest things
are as the comment above says.)

In any event the PHYSDEVOP_setup_gsi invocation looks fishy, at least
if this was a PCI IRQ. Just to mention it - according to the hypervisor
log you sent earlier there's also no source override for IRQ 7 (in the
log lines starting "ACPI: INT_SRC_OVR ").

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 18.12.2023 17:21, Sébastien Chaumat wrote:
>>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
>>>>>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
>>>>>>
>>>>>> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
>>>>>> ioapic-edge and IRQ9 to ioapic-level ?
>>>>>>
>>>>>> IR-IO-APIC    7-fasteoi   pinctrl_amd
>>>>>> IR-IO-APIC    9-fasteoi   acpi
>>>>>>
>>>>>> to (xen 4.18.0)
>>>>>>
>>>>>> xen-pirq     -ioapic-edge  pinctrl_amd
>>>>>> xen-pirq     -ioapic-level  acpi
>>>>>>
>>>>>> ?
>>>
> 
>>> This look similar to
>>> https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/
>>>
>>> This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
>>> (so level type) while in xen it  is mapped to oapic-edge  instead of
>>> oapic-level
>>> as the SSDT indicates :
>>>
>>>  Device (GPIO)
>>>
>>>      {
>>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
>>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
>>>          Name (_UID, Zero)  // _UID: Unique ID
>>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
>>>          {
>>>              Name (RBUF, ResourceTemplate ()
>>>              {
>>>                  Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
>>>                  {
>>>                      0x00000007,
>>>            }
>>> Any idea why ?
>>
>> Information coming from AML is required to be handed down by Dom0 to Xen.
>> May want checking that (a) Dom0 properly does so and (b) Xen doesn't screw
>> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
>> specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7 is
>> also the spurious vector. You may want to retry with the tip of the 4.17
>> branch (soon to become 4.17.3) - while it doesn't look very likely to me
>> that recent backports there were related, it may still be that they make
>> a difference.
>>
> 
> testing with 4.17.3:
> 
> Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)  that
> (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1 polarity: 1
> 
> but later on in dmesg I see :
> [    1.747958] xen: registering gsi 7 triggering 0 polarity 1

Linux has exactly one place where this message is logged from, and that's
ahead of it calling PHYSDEVOP_setup_gsi. Since you said "later", can you
confirm that actually you see two instances of the Xen message and two
instances of the Linux one (each of them with respectively matching
trigger and polarity values)? Or are we indeed observing what would look
to be corruption of a hypercall argument?

If there were two calls, it would be important to realize that Xen will
respect only the first one.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 19.12.2023 14:15, Jan Beulich wrote:
> On 18.12.2023 17:21, Sébastien Chaumat wrote:
>>>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
>>>>>>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
>>>>>>>
>>>>>>> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
>>>>>>> ioapic-edge and IRQ9 to ioapic-level ?
>>>>>>>
>>>>>>> IR-IO-APIC    7-fasteoi   pinctrl_amd
>>>>>>> IR-IO-APIC    9-fasteoi   acpi
>>>>>>>
>>>>>>> to (xen 4.18.0)
>>>>>>>
>>>>>>> xen-pirq     -ioapic-edge  pinctrl_amd
>>>>>>> xen-pirq     -ioapic-level  acpi
>>>>>>>
>>>>>>> ?
>>>>
>>
>>>> This look similar to
>>>> https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/
>>>>
>>>> This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
>>>> (so level type) while in xen it  is mapped to oapic-edge  instead of
>>>> oapic-level
>>>> as the SSDT indicates :
>>>>
>>>>  Device (GPIO)
>>>>
>>>>      {
>>>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
>>>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
>>>>          Name (_UID, Zero)  // _UID: Unique ID
>>>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
>>>>          {
>>>>              Name (RBUF, ResourceTemplate ()
>>>>              {
>>>>                  Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
>>>>                  {
>>>>                      0x00000007,
>>>>            }
>>>> Any idea why ?
>>>
>>> Information coming from AML is required to be handed down by Dom0 to Xen.
>>> May want checking that (a) Dom0 properly does so and (b) Xen doesn't screw
>>> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
>>> specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7 is
>>> also the spurious vector. You may want to retry with the tip of the 4.17
>>> branch (soon to become 4.17.3) - while it doesn't look very likely to me
>>> that recent backports there were related, it may still be that they make
>>> a difference.
>>>
>>
>> testing with 4.17.3:
>>
>> Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)  that
>> (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1 polarity: 1
>>
>> but later on in dmesg I see :
>> [    1.747958] xen: registering gsi 7 triggering 0 polarity 1
> 
> Linux has exactly one place where this message is logged from, and that's
> ahead of it calling PHYSDEVOP_setup_gsi. Since you said "later", can you
> confirm that actually you see two instances of the Xen message and two
> instances of the Linux one (each of them with respectively matching
> trigger and polarity values)? Or are we indeed observing what would look
> to be corruption of a hypercall argument?

Oh, no - what Linux logs are still the ACPI values (level: 0, edge: 1).
What Xen logs are the IO-APIC values (level: 1, edge: 0). So all consistent
here, and presumably indeed only a single call occurring.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 05.12.2023 21:31, Sébastien Chaumat wrote:
>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> 
> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
> ioapic-edge and IRQ9 to ioapic-level ?
> 
> IR-IO-APIC    7-fasteoi   pinctrl_amd
> IR-IO-APIC    9-fasteoi   acpi
> 
> to (xen 4.18.0)
> 
> xen-pirq     -ioapic-edge  pinctrl_amd
> xen-pirq     -ioapic-level  acpi
> 
> ?

So we need to come back to here: If the IRQ is indeed treated as level
triggered in the native kernel, it needs sorting where that information
is coming from there, and why different information is used under Xen.
Clearly xen_register_gsi() is passed ACPI_EDGE_SENSITIVE (and
ACPI_ACTIVE_LOW), supposedly coming from ACPI.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

I did add an extra printk in PHYSDEVOP_setup_gsi
so the "first one" is my printk (available in xl dmesg)
the second message is from xen_register_gsi (from linux kernel)

Le mar. 19 déc. 2023 à 14:15, Jan Beulich <jbeulich@suse.com> a écrit :
>
> On 18.12.2023 17:21, Sébastien Chaumat wrote:
> >>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
> >>>>>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> >>>>>>
> >>>>>> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
> >>>>>> ioapic-edge and IRQ9 to ioapic-level ?
> >>>>>>
> >>>>>> IR-IO-APIC    7-fasteoi   pinctrl_amd
> >>>>>> IR-IO-APIC    9-fasteoi   acpi
> >>>>>>
> >>>>>> to (xen 4.18.0)
> >>>>>>
> >>>>>> xen-pirq     -ioapic-edge  pinctrl_amd
> >>>>>> xen-pirq     -ioapic-level  acpi
> >>>>>>
> >>>>>> ?
> >>>
> >
> >>> This look similar to
> >>> https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/
> >>>
> >>> This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
> >>> (so level type) while in xen it  is mapped to oapic-edge  instead of
> >>> oapic-level
> >>> as the SSDT indicates :
> >>>
> >>>  Device (GPIO)
> >>>
> >>>      {
> >>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
> >>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
> >>>          Name (_UID, Zero)  // _UID: Unique ID
> >>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
> >>>          {
> >>>              Name (RBUF, ResourceTemplate ()
> >>>              {
> >>>                  Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
> >>>                  {
> >>>                      0x00000007,
> >>>            }
> >>> Any idea why ?
> >>
> >> Information coming from AML is required to be handed down by Dom0 to Xen.
> >> May want checking that (a) Dom0 properly does so and (b) Xen doesn't screw
> >> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
> >> specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7 is
> >> also the spurious vector. You may want to retry with the tip of the 4.17
> >> branch (soon to become 4.17.3) - while it doesn't look very likely to me
> >> that recent backports there were related, it may still be that they make
> >> a difference.
> >>
> >
> > testing with 4.17.3:
> >
> > Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)  that
> > (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1 polarity: 1
> >
> > but later on in dmesg I see :
> > [    1.747958] xen: registering gsi 7 triggering 0 polarity 1
>
> Linux has exactly one place where this message is logged from, and that's
> ahead of it calling PHYSDEVOP_setup_gsi. Since you said "later", can you
> confirm that actually you see two instances of the Xen message and two
> instances of the Linux one (each of them with respectively matching
> trigger and polarity values)? Or are we indeed observing what would look
> to be corruption of a hypercall argument?
>
> If there were two calls, it would be important to realize that Xen will
> respect only the first one.
>
> Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

Le mar. 19 déc. 2023 à 16:15, Sébastien Chaumat <euidzero@gmail.com> a écrit :
>
> I did add an extra printk in PHYSDEVOP_setup_gsi
> so the "first one" is my printk (available in xl dmesg)
> the second message is from xen_register_gsi (from linux kernel)
>
> Le mar. 19 déc. 2023 à 14:15, Jan Beulich <jbeulich@suse.com> a écrit :
> >
> > On 18.12.2023 17:21, Sébastien Chaumat wrote:
> > >>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
> > >>>>>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> > >>>>>>
> > >>>>>> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
> > >>>>>> ioapic-edge and IRQ9 to ioapic-level ?
> > >>>>>>
> > >>>>>> IR-IO-APIC    7-fasteoi   pinctrl_amd
> > >>>>>> IR-IO-APIC    9-fasteoi   acpi
> > >>>>>>
> > >>>>>> to (xen 4.18.0)
> > >>>>>>
> > >>>>>> xen-pirq     -ioapic-edge  pinctrl_amd
> > >>>>>> xen-pirq     -ioapic-level  acpi
> > >>>>>>
> > >>>>>> ?
> > >>>
> > >
> > >>> This look similar to
> > >>> https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/
> > >>>
> > >>> This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
> > >>> (so level type) while in xen it  is mapped to oapic-edge  instead of
> > >>> oapic-level
> > >>> as the SSDT indicates :
> > >>>
> > >>>  Device (GPIO)
> > >>>
> > >>>      {
> > >>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
> > >>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
> > >>>          Name (_UID, Zero)  // _UID: Unique ID
> > >>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
> > >>>          {
> > >>>              Name (RBUF, ResourceTemplate ()
> > >>>              {
> > >>>                  Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
> > >>>                  {
> > >>>                      0x00000007,
> > >>>            }
> > >>> Any idea why ?
> > >>
> > >> Information coming from AML is required to be handed down by Dom0 to Xen.
> > >> May want checking that (a) Dom0 properly does so and (b) Xen doesn't screw
> > >> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if this is
> > >> specific to it being IRQ7 which GPIO uses, as at the (master) PIC IRQ7 is
> > >> also the spurious vector. You may want to retry with the tip of the 4.17
> > >> branch (soon to become 4.17.3) - while it doesn't look very likely to me
> > >> that recent backports there were related, it may still be that they make
> > >> a difference.
> > >>
> > >
> > > testing with 4.17.3:
> > >
> > > Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)  that
> > > (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1 polarity: 1
> > >
> > > but later on in dmesg I see :
> > > [    1.747958] xen: registering gsi 7 triggering 0 polarity 1
> >
> > Linux has exactly one place where this message is logged from, and that's
> > ahead of it calling PHYSDEVOP_setup_gsi. Since you said "later", can you
> > confirm that actually you see two instances of the Xen message and two
> > instances of the Linux one (each of them with respectively matching
> > trigger and polarity values)? Or are we indeed observing what would look
> > to be corruption of a hypercall argument?
> >
> > If there were two calls, it would be important to realize that Xen will
> > respect only the first one.
> >
> > Jan

Adding a printk to catch the gsi immediately before the hypercall in
linux/arch/x86/pci/xen.c

#ifdef CONFIG_XEN_PV_DOM0
static int xen_register_gsi(u32 gsi, int triggering, int polarity)
{
int rc, irq;
struct physdev_setup_gsi setup_gsi;

if (!xen_pv_domain())
return -1;

printk(KERN_DEBUG "xen: registering gsi %u triggering %d polarity %d\n",
gsi, triggering, polarity);

irq = xen_register_pirq(gsi, triggering, true);

setup_gsi.gsi = gsi;
setup_gsi.triggering = (triggering == ACPI_EDGE_SENSITIVE ? 0 : 1);
setup_gsi.polarity = (polarity == ACPI_ACTIVE_HIGH ? 0 : 1);

printk(KERN_INFO "Before PHYSDEVOP_setup_gsi gsi: %d,triggering: %u,
polarity: %u\n", setup_gsi.gsi, setup_gsi.triggering,
setup_gsi.polarity);
rc = HYPERVISOR_physdev_op(PHYSDEVOP_setup_gsi, &setup_gsi);
if (rc == -EEXIST)
  printk(KERN_INFO "Already setup the GSI :%d\n", gsi);
else if (rc) {
   printk(KERN_ERR "Failed to setup GSI :%d, err_code:%d\n",
gsi, rc);
}

return irq;
}

I got the following :
[    1.848051] xen: registering gsi 7 triggering 0 polarity 1
[    1.848056] Before PHYSDEVOP_setup_gsi  gsi: 7,triggering: 1, polarity: 1

So the reversal occurs
there

irq = xen_register_pirq(gsi, triggering, true);

Or there :

setup_gsi.gsi = gsi;
setup_gsi.triggering = (triggering == ACPI_EDGE_SENSITIVE ? 0 : 1);
setup_gsi.polarity = (polarity == ACPI_ACTIVE_HIGH ? 0 : 1);

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le mar. 19 déc. 2023 à 20:03, Sébastien Chaumat <euidzero@gmail.com> a
écrit :

> Le mar. 19 déc. 2023 à 16:15, Sébastien Chaumat <euidzero@gmail.com> a
> écrit :
> >
> > I did add an extra printk in PHYSDEVOP_setup_gsi
> > so the "first one" is my printk (available in xl dmesg)
> > the second message is from xen_register_gsi (from linux kernel)
> >
> > Le mar. 19 déc. 2023 à 14:15, Jan Beulich <jbeulich@suse.com> a écrit :
> > >
> > > On 18.12.2023 17:21, Sébastien Chaumat wrote:
> > > >>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
> > > >>>>>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up
> interrupt
> > > >>>>>>
> > > >>>>>> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
> > > >>>>>> ioapic-edge and IRQ9 to ioapic-level ?
> > > >>>>>>
> > > >>>>>> IR-IO-APIC    7-fasteoi   pinctrl_amd
> > > >>>>>> IR-IO-APIC    9-fasteoi   acpi
> > > >>>>>>
> > > >>>>>> to (xen 4.18.0)
> > > >>>>>>
> > > >>>>>> xen-pirq     -ioapic-edge  pinctrl_amd
> > > >>>>>> xen-pirq     -ioapic-level  acpi
> > > >>>>>>
> > > >>>>>> ?
> > > >>>
> > > >
> > > >>> This look similar to
> > > >>> https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/
> > > >>>
> > > >>> This issue seems that IRQ 7 (the GPIO controller) is natively
> fasteoi
> > > >>> (so level type) while in xen it  is mapped to oapic-edge  instead
> of
> > > >>> oapic-level
> > > >>> as the SSDT indicates :
> > > >>>
> > > >>>  Device (GPIO)
> > > >>>
> > > >>>      {
> > > >>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
> > > >>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
> > > >>>          Name (_UID, Zero)  // _UID: Unique ID
> > > >>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current
> Resource Settings
> > > >>>          {
> > > >>>              Name (RBUF, ResourceTemplate ()
> > > >>>              {
> > > >>>                  Interrupt (ResourceConsumer, Level, ActiveLow,
> Shared, ,, )
> > > >>>                  {
> > > >>>                      0x00000007,
> > > >>>            }
> > > >>> Any idea why ?
> > > >>
> > > >> Information coming from AML is required to be handed down by Dom0
> to Xen.
> > > >> May want checking that (a) Dom0 properly does so and (b) Xen
> doesn't screw
> > > >> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if
> this is
> > > >> specific to it being IRQ7 which GPIO uses, as at the (master) PIC
> IRQ7 is
> > > >> also the spurious vector. You may want to retry with the tip of the
> 4.17
> > > >> branch (soon to become 4.17.3) - while it doesn't look very likely
> to me
> > > >> that recent backports there were related, it may still be that they
> make
> > > >> a difference.
> > > >>
> > > >
> > > > testing with 4.17.3:
> > > >
> > > > Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)  that
> > > > (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1 polarity:
> 1
> > > >
> > > > but later on in dmesg I see :
> > > > [    1.747958] xen: registering gsi 7 triggering 0 polarity 1
> > >
> > > Linux has exactly one place where this message is logged from, and
> that's
> > > ahead of it calling PHYSDEVOP_setup_gsi. Since you said "later", can
> you
> > > confirm that actually you see two instances of the Xen message and two
> > > instances of the Linux one (each of them with respectively matching
> > > trigger and polarity values)? Or are we indeed observing what would
> look
> > > to be corruption of a hypercall argument?
> > >
> > > If there were two calls, it would be important to realize that Xen will
> > > respect only the first one.
> > >
> > > Jan
>
> Adding a printk to catch the gsi immediately before the hypercall in
> linux/arch/x86/pci/xen.c
>
> #ifdef CONFIG_XEN_PV_DOM0
> static int xen_register_gsi(u32 gsi, int triggering, int polarity)
> {
> int rc, irq;
> struct physdev_setup_gsi setup_gsi;
>
> if (!xen_pv_domain())
> return -1;
>
> printk(KERN_DEBUG "xen: registering gsi %u triggering %d polarity %d\n",
> gsi, triggering, polarity);
>

there we have :
  [    1.848051] xen: registering gsi 7 triggering 0 polarity 1

then in the next call :

irq = xen_register_pirq(gsi, triggering, true);


 I added a printk at the very beginning  :

  static int xen_register_pirq(u32 gsi, int triggering, bool set_pirq)
  {
    int rc, pirq = -1, irq;
    struct physdev_map_pirq map_irq;
    int shareable = 0;
    char *name;

    printk(KERN_DEBUG "xen_register_pirq start gsi %u triggering %d
set_pirq %d\n", gsi, triggering, set_pirq)

And I get  in this printk result for IRQ7 : triggering=1 while it was
passed with value 0 in the call !?

Any idea ?

[-- Attachment #2: Type: text/html, Size: 6982 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le mer. 20 déc. 2023 à 00:06, Sébastien Chaumat <euidzero@gmail.com> a
écrit :

>
>
> Le mar. 19 déc. 2023 à 20:03, Sébastien Chaumat <euidzero@gmail.com> a
> écrit :
>
>> Le mar. 19 déc. 2023 à 16:15, Sébastien Chaumat <euidzero@gmail.com> a
>> écrit :
>> >
>> > I did add an extra printk in PHYSDEVOP_setup_gsi
>> > so the "first one" is my printk (available in xl dmesg)
>> > the second message is from xen_register_gsi (from linux kernel)
>> >
>> > Le mar. 19 déc. 2023 à 14:15, Jan Beulich <jbeulich@suse.com> a écrit :
>> > >
>> > > On 18.12.2023 17:21, Sébastien Chaumat wrote:
>> > > >>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
>> > > >>>>>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up
>> interrupt
>> > > >>>>>>
>> > > >>>>>> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
>> > > >>>>>> ioapic-edge and IRQ9 to ioapic-level ?
>> > > >>>>>>
>> > > >>>>>> IR-IO-APIC    7-fasteoi   pinctrl_amd
>> > > >>>>>> IR-IO-APIC    9-fasteoi   acpi
>> > > >>>>>>
>> > > >>>>>> to (xen 4.18.0)
>> > > >>>>>>
>> > > >>>>>> xen-pirq     -ioapic-edge  pinctrl_amd
>> > > >>>>>> xen-pirq     -ioapic-level  acpi
>> > > >>>>>>
>> > > >>>>>> ?
>> > > >>>
>> > > >
>> > > >>> This look similar to
>> > > >>> https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/
>> > > >>>
>> > > >>> This issue seems that IRQ 7 (the GPIO controller) is natively
>> fasteoi
>> > > >>> (so level type) while in xen it  is mapped to oapic-edge  instead
>> of
>> > > >>> oapic-level
>> > > >>> as the SSDT indicates :
>> > > >>>
>> > > >>>  Device (GPIO)
>> > > >>>
>> > > >>>      {
>> > > >>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
>> > > >>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
>> > > >>>          Name (_UID, Zero)  // _UID: Unique ID
>> > > >>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current
>> Resource Settings
>> > > >>>          {
>> > > >>>              Name (RBUF, ResourceTemplate ()
>> > > >>>              {
>> > > >>>                  Interrupt (ResourceConsumer, Level, ActiveLow,
>> Shared, ,, )
>> > > >>>                  {
>> > > >>>                      0x00000007,
>> > > >>>            }
>> > > >>> Any idea why ?
>> > > >>
>> > > >> Information coming from AML is required to be handed down by Dom0
>> to Xen.
>> > > >> May want checking that (a) Dom0 properly does so and (b) Xen
>> doesn't screw
>> > > >> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if
>> this is
>> > > >> specific to it being IRQ7 which GPIO uses, as at the (master) PIC
>> IRQ7 is
>> > > >> also the spurious vector. You may want to retry with the tip of
>> the 4.17
>> > > >> branch (soon to become 4.17.3) - while it doesn't look very likely
>> to me
>> > > >> that recent backports there were related, it may still be that
>> they make
>> > > >> a difference.
>> > > >>
>> > > >
>> > > > testing with 4.17.3:
>> > > >
>> > > > Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)
>> that
>> > > > (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1
>> polarity: 1
>> > > >
>> > > > but later on in dmesg I see :
>> > > > [    1.747958] xen: registering gsi 7 triggering 0 polarity 1
>> > >
>> > > Linux has exactly one place where this message is logged from, and
>> that's
>> > > ahead of it calling PHYSDEVOP_setup_gsi. Since you said "later", can
>> you
>> > > confirm that actually you see two instances of the Xen message and two
>> > > instances of the Linux one (each of them with respectively matching
>> > > trigger and polarity values)? Or are we indeed observing what would
>> look
>> > > to be corruption of a hypercall argument?
>> > >
>> > > If there were two calls, it would be important to realize that Xen
>> will
>> > > respect only the first one.
>> > >
>> > > Jan
>>
>> Adding a printk to catch the gsi immediately before the hypercall in
>> linux/arch/x86/pci/xen.c
>>
>> #ifdef CONFIG_XEN_PV_DOM0
>> static int xen_register_gsi(u32 gsi, int triggering, int polarity)
>> {
>> int rc, irq;
>> struct physdev_setup_gsi setup_gsi;
>>
>> if (!xen_pv_domain())
>> return -1;
>>
>> printk(KERN_DEBUG "xen: registering gsi %u triggering %d polarity %d\n",
>> gsi, triggering, polarity);
>>
>
> there we have :
>   [    1.848051] xen: registering gsi 7 triggering 0 polarity 1
>
> then in the next call :
>
> irq = xen_register_pirq(gsi, triggering, true);
>
>
>  I added a printk at the very beginning  :
>
>   static int xen_register_pirq(u32 gsi, int triggering, bool set_pirq)
>   {
>     int rc, pirq = -1, irq;
>     struct physdev_map_pirq map_irq;
>     int shareable = 0;
>     char *name;
>
>     printk(KERN_DEBUG "xen_register_pirq start gsi %u triggering %d
> set_pirq %d\n", gsi, triggering, set_pirq)
>
> And I get  in this printk result for IRQ7 : triggering=1 while it was
> passed with value 0 in the call !?
>

Sorry bad format %d instead of %i for triggering ...

[-- Attachment #2: Type: text/html, Size: 7430 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le mer. 20 déc. 2023 à 00:11, Sébastien Chaumat <euidzero@gmail.com> a
écrit :

>
>
> Le mer. 20 déc. 2023 à 00:06, Sébastien Chaumat <euidzero@gmail.com> a
> écrit :
>
>>
>>
>> Le mar. 19 déc. 2023 à 20:03, Sébastien Chaumat <euidzero@gmail.com> a
>> écrit :
>>
>>> Le mar. 19 déc. 2023 à 16:15, Sébastien Chaumat <euidzero@gmail.com> a
>>> écrit :
>>> >
>>> > I did add an extra printk in PHYSDEVOP_setup_gsi
>>> > so the "first one" is my printk (available in xl dmesg)
>>> > the second message is from xen_register_gsi (from linux kernel)
>>> >
>>> > Le mar. 19 déc. 2023 à 14:15, Jan Beulich <jbeulich@suse.com> a écrit
>>> :
>>> > >
>>> > > On 18.12.2023 17:21, Sébastien Chaumat wrote:
>>> > > >>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
>>> > > >>>>>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable
>>> wake-up interrupt
>>> > > >>>>>>
>>> > > >>>>>> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
>>> > > >>>>>> ioapic-edge and IRQ9 to ioapic-level ?
>>> > > >>>>>>
>>> > > >>>>>> IR-IO-APIC    7-fasteoi   pinctrl_amd
>>> > > >>>>>> IR-IO-APIC    9-fasteoi   acpi
>>> > > >>>>>>
>>> > > >>>>>> to (xen 4.18.0)
>>> > > >>>>>>
>>> > > >>>>>> xen-pirq     -ioapic-edge  pinctrl_amd
>>> > > >>>>>> xen-pirq     -ioapic-level  acpi
>>> > > >>>>>>
>>> > > >>>>>> ?
>>> > > >>>
>>> > > >
>>> > > >>> This look similar to
>>> > > >>> https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/
>>> > > >>>
>>> > > >>> This issue seems that IRQ 7 (the GPIO controller) is natively
>>> fasteoi
>>> > > >>> (so level type) while in xen it  is mapped to oapic-edge
>>> instead of
>>> > > >>> oapic-level
>>> > > >>> as the SSDT indicates :
>>> > > >>>
>>> > > >>>  Device (GPIO)
>>> > > >>>
>>> > > >>>      {
>>> > > >>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
>>> > > >>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
>>> > > >>>          Name (_UID, Zero)  // _UID: Unique ID
>>> > > >>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current
>>> Resource Settings
>>> > > >>>          {
>>> > > >>>              Name (RBUF, ResourceTemplate ()
>>> > > >>>              {
>>> > > >>>                  Interrupt (ResourceConsumer, Level, ActiveLow,
>>> Shared, ,, )
>>> > > >>>                  {
>>> > > >>>                      0x00000007,
>>> > > >>>            }
>>> > > >>> Any idea why ?
>>> > > >>
>>> > > >> Information coming from AML is required to be handed down by Dom0
>>> to Xen.
>>> > > >> May want checking that (a) Dom0 properly does so and (b) Xen
>>> doesn't screw
>>> > > >> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if
>>> this is
>>> > > >> specific to it being IRQ7 which GPIO uses, as at the (master) PIC
>>> IRQ7 is
>>> > > >> also the spurious vector. You may want to retry with the tip of
>>> the 4.17
>>> > > >> branch (soon to become 4.17.3) - while it doesn't look very
>>> likely to me
>>> > > >> that recent backports there were related, it may still be that
>>> they make
>>> > > >> a difference.
>>> > > >>
>>> > > >
>>> > > > testing with 4.17.3:
>>> > > >
>>> > > > Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)
>>> that
>>> > > > (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1
>>> polarity: 1
>>> > > >
>>> > > > but later on in dmesg I see :
>>> > > > [    1.747958] xen: registering gsi 7 triggering 0 polarity 1
>>> > >
>>> > > Linux has exactly one place where this message is logged from, and
>>> that's
>>> > > ahead of it calling PHYSDEVOP_setup_gsi. Since you said "later", can
>>> you
>>> > > confirm that actually you see two instances of the Xen message and
>>> two
>>> > > instances of the Linux one (each of them with respectively matching
>>> > > trigger and polarity values)? Or are we indeed observing what would
>>> look
>>> > > to be corruption of a hypercall argument?
>>> > >
>>> > > If there were two calls, it would be important to realize that Xen
>>> will
>>> > > respect only the first one.
>>> > >
>>> > > Jan
>>>
>>> Adding a printk to catch the gsi immediately before the hypercall in
>>> linux/arch/x86/pci/xen.c
>>>
>>> #ifdef CONFIG_XEN_PV_DOM0
>>> static int xen_register_gsi(u32 gsi, int triggering, int polarity)
>>> {
>>> int rc, irq;
>>> struct physdev_setup_gsi setup_gsi;
>>>
>>> if (!xen_pv_domain())
>>> return -1;
>>>
>>> printk(KERN_DEBUG "xen: registering gsi %u triggering %d polarity %d\n",
>>> gsi, triggering, polarity);
>>>
>>
>> there we have :
>>   [    1.848051] xen: registering gsi 7 triggering 0 polarity 1
>>
>> then in the next call :
>>
>> irq = xen_register_pirq(gsi, triggering, true);
>>
>>
>>  I added a printk at the very beginning  :
>>
>>   static int xen_register_pirq(u32 gsi, int triggering, bool set_pirq)
>>   {
>>     int rc, pirq = -1, irq;
>>     struct physdev_map_pirq map_irq;
>>     int shareable = 0;
>>     char *name;
>>
>>     printk(KERN_DEBUG "xen_register_pirq start gsi %u triggering %d
>> set_pirq %d\n", gsi, triggering, set_pirq)
>>
>> And I get  in this printk result for IRQ7 : triggering=1 while it was
>> passed with value 0 in the call !?
>>
>
> Sorry bad format %d instead of %i for triggering ...
>

So I replaced the format with %i and suprise :

There are 2 calls to  xen_register_pirq as I  can see 2 messages per IRQ

 the first call is  right after the message "NR_IRQS: ..."from
early_irq_init()   ( kernel/irq/irqdec.c )

 I see :
xen_register_pirq start gsi 7 triggering 1 set_pirq 1   ... so in
xen_register_pirq()
Then I get the message "Before PHYSDEVOPS_setup_gsi) proving we are called
by xen_register_gsi()

Then right after the message "ACPI: 26 ACPI AML tables successfully
acquired and loaded"

I get again, but with reversed triggering :
xen: registering gsi 7 triggering 0 polarity 1
xen_register_pirq start gsi 7 triggering 0 set_pirq 1
Before PHYSDEVOPS_setup_gsi ...

So once again a call to  xen_register_gsi()

[-- Attachment #2: Type: text/html, Size: 8914 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le mer. 20 déc. 2023 à 00:50, Sébastien Chaumat <euidzero@gmail.com> a
écrit :

>
>
> Le mer. 20 déc. 2023 à 00:11, Sébastien Chaumat <euidzero@gmail.com> a
> écrit :
>
>>
>>
>> Le mer. 20 déc. 2023 à 00:06, Sébastien Chaumat <euidzero@gmail.com> a
>> écrit :
>>
>>>
>>>
>>> Le mar. 19 déc. 2023 à 20:03, Sébastien Chaumat <euidzero@gmail.com> a
>>> écrit :
>>>
>>>> Le mar. 19 déc. 2023 à 16:15, Sébastien Chaumat <euidzero@gmail.com> a
>>>> écrit :
>>>> >
>>>> > I did add an extra printk in PHYSDEVOP_setup_gsi
>>>> > so the "first one" is my printk (available in xl dmesg)
>>>> > the second message is from xen_register_gsi (from linux kernel)
>>>> >
>>>> > Le mar. 19 déc. 2023 à 14:15, Jan Beulich <jbeulich@suse.com> a
>>>> écrit :
>>>> > >
>>>> > > On 18.12.2023 17:21, Sébastien Chaumat wrote:
>>>> > > >>>>> On 05.12.2023 21:31, Sébastien Chaumat wrote:
>>>> > > >>>>>>> [    2.464598] amd_gpio AMDI0030:00: failed to enable
>>>> wake-up interrupt
>>>> > > >>>>>>
>>>> > > >>>>>> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
>>>> > > >>>>>> ioapic-edge and IRQ9 to ioapic-level ?
>>>> > > >>>>>>
>>>> > > >>>>>> IR-IO-APIC    7-fasteoi   pinctrl_amd
>>>> > > >>>>>> IR-IO-APIC    9-fasteoi   acpi
>>>> > > >>>>>>
>>>> > > >>>>>> to (xen 4.18.0)
>>>> > > >>>>>>
>>>> > > >>>>>> xen-pirq     -ioapic-edge  pinctrl_amd
>>>> > > >>>>>> xen-pirq     -ioapic-level  acpi
>>>> > > >>>>>>
>>>> > > >>>>>> ?
>>>> > > >>>
>>>> > > >
>>>> > > >>> This look similar to
>>>> > > >>> https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/
>>>> > > >>>
>>>> > > >>> This issue seems that IRQ 7 (the GPIO controller) is natively
>>>> fasteoi
>>>> > > >>> (so level type) while in xen it  is mapped to oapic-edge
>>>> instead of
>>>> > > >>> oapic-level
>>>> > > >>> as the SSDT indicates :
>>>> > > >>>
>>>> > > >>>  Device (GPIO)
>>>> > > >>>
>>>> > > >>>      {
>>>> > > >>>          Name (_HID, "AMDI0030")  // _HID: Hardware ID
>>>> > > >>>          Name (_CID, "AMDI0030")  // _CID: Compatible ID
>>>> > > >>>          Name (_UID, Zero)  // _UID: Unique ID
>>>> > > >>>          Method (_CRS, 0, NotSerialized)  // _CRS: Current
>>>> Resource Settings
>>>> > > >>>          {
>>>> > > >>>              Name (RBUF, ResourceTemplate ()
>>>> > > >>>              {
>>>> > > >>>                  Interrupt (ResourceConsumer, Level, ActiveLow,
>>>> Shared, ,, )
>>>> > > >>>                  {
>>>> > > >>>                      0x00000007,
>>>> > > >>>            }
>>>> > > >>> Any idea why ?
>>>> > > >>
>>>> > > >> Information coming from AML is required to be handed down by
>>>> Dom0 to Xen.
>>>> > > >> May want checking that (a) Dom0 properly does so and (b) Xen
>>>> doesn't screw
>>>> > > >> up in consuming that data. See PHYSDEVOP_setup_gsi. I wonder if
>>>> this is
>>>> > > >> specific to it being IRQ7 which GPIO uses, as at the (master)
>>>> PIC IRQ7 is
>>>> > > >> also the spurious vector. You may want to retry with the tip of
>>>> the 4.17
>>>> > > >> branch (soon to become 4.17.3) - while it doesn't look very
>>>> likely to me
>>>> > > >> that recent backports there were related, it may still be that
>>>> they make
>>>> > > >> a difference.
>>>> > > >>
>>>> > > >
>>>> > > > testing with 4.17.3:
>>>> > > >
>>>> > > > Adding some printk in PHYSDEVOP_setup_gsi, I  see (in xl dmesg)
>>>> that
>>>> > > > (XEN) PHYSDEVOP_setup_gsi setup_gsi : gsi: 7 triggering: 1
>>>> polarity: 1
>>>> > > >
>>>> > > > but later on in dmesg I see :
>>>> > > > [    1.747958] xen: registering gsi 7 triggering 0 polarity 1
>>>> > >
>>>> > > Linux has exactly one place where this message is logged from, and
>>>> that's
>>>> > > ahead of it calling PHYSDEVOP_setup_gsi. Since you said "later",
>>>> can you
>>>> > > confirm that actually you see two instances of the Xen message and
>>>> two
>>>> > > instances of the Linux one (each of them with respectively matching
>>>> > > trigger and polarity values)? Or are we indeed observing what would
>>>> look
>>>> > > to be corruption of a hypercall argument?
>>>> > >
>>>> > > If there were two calls, it would be important to realize that Xen
>>>> will
>>>> > > respect only the first one.
>>>> > >
>>>> > > Jan
>>>>
>>>> Adding a printk to catch the gsi immediately before the hypercall in
>>>> linux/arch/x86/pci/xen.c
>>>>
>>>> #ifdef CONFIG_XEN_PV_DOM0
>>>> static int xen_register_gsi(u32 gsi, int triggering, int polarity)
>>>> {
>>>> int rc, irq;
>>>> struct physdev_setup_gsi setup_gsi;
>>>>
>>>> if (!xen_pv_domain())
>>>> return -1;
>>>>
>>>> printk(KERN_DEBUG "xen: registering gsi %u triggering %d polarity %d\n",
>>>> gsi, triggering, polarity);
>>>>
>>>
>>> there we have :
>>>   [    1.848051] xen: registering gsi 7 triggering 0 polarity 1
>>>
>>> then in the next call :
>>>
>>> irq = xen_register_pirq(gsi, triggering, true);
>>>
>>>
>>>  I added a printk at the very beginning  :
>>>
>>>   static int xen_register_pirq(u32 gsi, int triggering, bool set_pirq)
>>>   {
>>>     int rc, pirq = -1, irq;
>>>     struct physdev_map_pirq map_irq;
>>>     int shareable = 0;
>>>     char *name;
>>>
>>>     printk(KERN_DEBUG "xen_register_pirq start gsi %u triggering %d
>>> set_pirq %d\n", gsi, triggering, set_pirq)
>>>
>>> And I get  in this printk result for IRQ7 : triggering=1 while it was
>>> passed with value 0 in the call !?
>>>
>>
>> Sorry bad format %d instead of %i for triggering ...
>>
>
> So I replaced the format with %i and suprise :
>
> There are 2 calls to  xen_register_pirq as I  can see 2 messages per IRQ
>
>  the first call is  right after the message "NR_IRQS: ..."from
> early_irq_init()   ( kernel/irq/irqdec.c )
>
>  I see :
> xen_register_pirq start gsi 7 triggering 1 set_pirq 1   ... so in
> xen_register_pirq()
> Then I get the message "Before PHYSDEVOPS_setup_gsi) proving we are called
> by xen_register_gsi()
>
> Then right after the message "ACPI: 26 ACPI AML tables successfully
> acquired and loaded"
>
> I get again, but with reversed triggering :
> xen: registering gsi 7 triggering 0 polarity 1
> xen_register_pirq start gsi 7 triggering 0 set_pirq 1
> Before PHYSDEVOPS_setup_gsi ...
>
> So once again a call to  xen_register_gsi()
>

I had to triple check:

The first call is from xen_register_pirq()  and seem to originate from
early_irq_init()  : triggering is 1
in this first call the HYPERVISOR_physdev_ops is called with triggering 1
shareable 0

The second call is from xen_register_pirq() called from xen_register_gsi() :
  trigger=0 polarity 1 at the start of  xen_register_pirq()
but then trigger=1 polarity=1 just before the call to PHYSDEVOPS_setup_gsi

[-- Attachment #2: Type: text/html, Size: 9824 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 20.12.2023 01:23, Sébastien Chaumat wrote:
> I had to triple check:
> 
> The first call is from xen_register_pirq()  and seem to originate from
> early_irq_init()  : triggering is 1
> in this first call the HYPERVISOR_physdev_ops is called with triggering 1
> shareable 0
> 
> The second call is from xen_register_pirq() called from xen_register_gsi() :
>   trigger=0 polarity 1 at the start of  xen_register_pirq()
> but then trigger=1 polarity=1 just before the call to PHYSDEVOPS_setup_gsi

I'm sorry, but this is getting extremely confusing. Can you please supply
a complete kernel log, where also other potentially relevant messages
would be present (like those issued when PHYSDEVOP_setup_gsi has failed,
as ought to happen when invoked the 2nd time for the same GSI)? It's fine
if you want to leave your extra printk()s in place for this, but please
be sure (perhaps by way of also supplying the patch you use) to make clear
where exactly they live, so we can make sense of those extra log messages.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

[-- Attachment #1.1: Type: text/plain, Size: 1288 bytes --]

Le mer. 20 déc. 2023 à 11:06, Jan Beulich <jbeulich@suse.com> a écrit :

> On 20.12.2023 01:23, Sébastien Chaumat wrote:
> > I had to triple check:
> >
> > The first call is from xen_register_pirq()  and seem to originate from
> > early_irq_init()  : triggering is 1
> > in this first call the HYPERVISOR_physdev_ops is called with triggering 1
> > shareable 0
> >
> > The second call is from xen_register_pirq() called from
> xen_register_gsi() :
> >   trigger=0 polarity 1 at the start of  xen_register_pirq()
> > but then trigger=1 polarity=1 just before the call to
> PHYSDEVOPS_setup_gsi
>
> I'm sorry, but this is getting extremely confusing. Can you please supply
> a complete kernel log, where also other potentially relevant messages
> would be present (like those issued when PHYSDEVOP_setup_gsi has failed,
> as ought to happen when invoked the 2nd time for the same GSI)? It's fine
> if you want to leave your extra printk()s in place for this, but please
> be sure (perhaps by way of also supplying the patch you use) to make clear
> where exactly they live, so we can make sense of those extra log messages.
>
> Jan
>
>
Sorry for the confusion.
Here are the patches I made to xen and linux kernel
Plus dmesg (bare metal,xen) and "xl dmesg"

[-- Attachment #1.2: Type: text/html, Size: 1741 bytes --]

[-- Attachment #2: xen-debug_irq_setup.diff --]
[-- Type: text/x-patch, Size: 598 bytes --]

diff --git a/xen/arch/x86/physdev.c b/xen/arch/x86/physdev.c
index 2f1d955a96..4f264896d5 100644
--- a/xen/arch/x86/physdev.c
+++ b/xen/arch/x86/physdev.c
@@ -570,6 +570,7 @@ ret_t do_physdev_op(int cmd, XEN_GUEST_HANDLE_PARAM(void) arg)
 
         ret = mp_register_gsi(setup_gsi.gsi, setup_gsi.triggering,
                               setup_gsi.polarity);
+        printk(KERN_INFO "PHYSDEVOP_setup_gsi: setup_gsi.gsi: %d, setup_gsi.triggering: %u,setup_gsi.polarity: %u\n", setup_gsi.gsi, setup_gsi.triggering, setup_gsi.polarity);
         break; 
     }
     case PHYSDEVOP_get_free_pirq: {

[-- Attachment #3: dmesg-baremetal-6.6.7xen-irq-dbg-1+ --]
[-- Type: application/octet-stream, Size: 145254 bytes --]

[    0.000000] Linux version 6.6.7xen-irq-dbg-1+ (sch@fedora) (gcc (GCC) 13.2.1 20231205 (Red Hat 13.2.1-6), GNU ld version 2.40-13.fc39) #6 SMP PREEMPT_DYNAMIC Wed Dec 20 16:13:29 CET 2023
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.6.7xen-irq-dbg-1+ root=UUID=71b1dc59-ea00-484c-b5e4-ee77ede771db ro "dyndbg=file drivers/gpio/* +p; file drivers/pinctrl/* +p; file arch/x86/pci/xen.c +p"
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009f000-0x00000000000bffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000009afffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000009b00000-0x0000000009dfffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000009e00000-0x0000000009efffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000009f00000-0x0000000009f3bfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x0000000009f3c000-0x000000004235ffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000042360000-0x000000004455ffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000044560000-0x0000000044568fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000044569000-0x000000004456cfff] reserved
[    0.000000] BIOS-e820: [mem 0x000000004456d000-0x000000004456efff] usable
[    0.000000] BIOS-e820: [mem 0x000000004456f000-0x000000004456ffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000044570000-0x000000005077efff] usable
[    0.000000] BIOS-e820: [mem 0x000000005077f000-0x0000000052f7efff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000052f7f000-0x000000005af7efff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000005af7f000-0x000000005affefff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000005afff000-0x000000005affffff] usable
[    0.000000] BIOS-e820: [mem 0x000000005b000000-0x000000005bffffff] reserved
[    0.000000] BIOS-e820: [mem 0x000000005d790000-0x000000005d7effff] reserved
[    0.000000] BIOS-e820: [mem 0x000000005d7f5000-0x000000005fffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000c0300000-0x00000000c03fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fed80fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000107e2fffff] usable
[    0.000000] BIOS-e820: [mem 0x0000001080000000-0x00000010c01fffff] reserved
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] APIC: Static calls initialized
[    0.000000] e820: update [mem 0x44575018-0x44579257] usable ==> usable
[    0.000000] e820: update [mem 0x44575018-0x44579257] usable ==> usable
[    0.000000] extended physical RAM map:
[    0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
[    0.000000] reserve setup_data: [mem 0x000000000009f000-0x00000000000bffff] reserved
[    0.000000] reserve setup_data: [mem 0x0000000000100000-0x0000000009afffff] usable
[    0.000000] reserve setup_data: [mem 0x0000000009b00000-0x0000000009dfffff] reserved
[    0.000000] reserve setup_data: [mem 0x0000000009e00000-0x0000000009efffff] usable
[    0.000000] reserve setup_data: [mem 0x0000000009f00000-0x0000000009f3bfff] ACPI NVS
[    0.000000] reserve setup_data: [mem 0x0000000009f3c000-0x000000004235ffff] usable
[    0.000000] reserve setup_data: [mem 0x0000000042360000-0x000000004455ffff] reserved
[    0.000000] reserve setup_data: [mem 0x0000000044560000-0x0000000044568fff] usable
[    0.000000] reserve setup_data: [mem 0x0000000044569000-0x000000004456cfff] reserved
[    0.000000] reserve setup_data: [mem 0x000000004456d000-0x000000004456efff] usable
[    0.000000] reserve setup_data: [mem 0x000000004456f000-0x000000004456ffff] reserved
[    0.000000] reserve setup_data: [mem 0x0000000044570000-0x0000000044575017] usable
[    0.000000] reserve setup_data: [mem 0x0000000044575018-0x0000000044579257] usable
[    0.000000] reserve setup_data: [mem 0x0000000044579258-0x000000005077efff] usable
[    0.000000] reserve setup_data: [mem 0x000000005077f000-0x0000000052f7efff] reserved
[    0.000000] reserve setup_data: [mem 0x0000000052f7f000-0x000000005af7efff] ACPI NVS
[    0.000000] reserve setup_data: [mem 0x000000005af7f000-0x000000005affefff] ACPI data
[    0.000000] reserve setup_data: [mem 0x000000005afff000-0x000000005affffff] usable
[    0.000000] reserve setup_data: [mem 0x000000005b000000-0x000000005bffffff] reserved
[    0.000000] reserve setup_data: [mem 0x000000005d790000-0x000000005d7effff] reserved
[    0.000000] reserve setup_data: [mem 0x000000005d7f5000-0x000000005fffffff] reserved
[    0.000000] reserve setup_data: [mem 0x00000000c0300000-0x00000000c03fffff] reserved
[    0.000000] reserve setup_data: [mem 0x00000000fed80000-0x00000000fed80fff] reserved
[    0.000000] reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000107e2fffff] usable
[    0.000000] reserve setup_data: [mem 0x0000001080000000-0x00000010c01fffff] reserved
[    0.000000] efi: EFI v2.8 by INSYDE Corp.
[    0.000000] efi: ACPI=0x5affe000 ACPI 2.0=0x5affe014 SMBIOS=0x51677000 SMBIOS 3.0=0x51674000 MEMATTR=0x4b7fe018 ESRT=0x4d16c898 MOKvar=0x5187c000 RNG=0x5af9d018 
[    0.000000] random: crng init done
[    0.000000] efi: Remove mem60: MMIO range=[0xc0300000-0xc03fffff] (1MB) from e820 map
[    0.000000] e820: remove [mem 0xc0300000-0xc03fffff] reserved
[    0.000000] efi: Not removing mem61: MMIO range=[0xfed80000-0xfed80fff] (4KB) from e820 map
[    0.000000] efi: Remove mem62: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
[    0.000000] e820: remove [mem 0xff000000-0xffffffff] reserved
[    0.000000] efi: Remove mem64: MMIO range=[0x10a0000000-0x10c01fffff] (514MB) from e820 map
[    0.000000] e820: remove [mem 0x10a0000000-0x10c01fffff] reserved
[    0.000000] SMBIOS 3.5.0 present.
[    0.000000] DMI: Framework Laptop 13 (AMD Ryzen 7040Series)/FRANMDCP07, BIOS 03.03 10/17/2023
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 3293.731 MHz processor
[    0.000123] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000125] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000130] last_pfn = 0x107e300 max_arch_pfn = 0x400000000
[    0.000135] MTRR map: 7 entries (3 fixed + 4 variable; max 20), built from 9 variable MTRRs
[    0.000136] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[    0.000523] last_pfn = 0x5b000 max_arch_pfn = 0x400000000
[    0.003061] esrt: Reserving ESRT space from 0x000000004d16c898 to 0x000000004d16c8d0.
[    0.003066] e820: update [mem 0x4d16c000-0x4d16cfff] usable ==> reserved
[    0.003081] Using GB pages for direct mapping
[    0.003651] Secure boot disabled
[    0.003651] RAMDISK: [mem 0x2468a000-0x3217efff]
[    0.003655] ACPI: Early table checksum verification disabled
[    0.003657] ACPI: RSDP 0x000000005AFFE014 000024 (v02 INSYDE)
[    0.003660] ACPI: XSDT 0x000000005AF9E228 00016C (v01 INSYDE EDK2     00000002      01000013)
[    0.003664] ACPI: FACP 0x000000005AFEF000 00010C (v05 INSYDE EDK2     00000002 ACPI 00040000)
[    0.003666] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20230628/tbfadt-615)
[    0.003669] ACPI: DSDT 0x000000005AFDF000 0093A6 (v02 INSYDE EDK2     00000002 ACPI 00040000)
[    0.003671] ACPI: FACS 0x000000005AEB7000 000040
[    0.003672] ACPI: UEFI 0x000000005AF67000 0001CF (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003674] ACPI: SSDT 0x000000005AFF4000 008416 (v02 INSYDE EDK2     00000002 ACPI 00040000)
[    0.003675] ACPI: SSDT 0x000000005AFF2000 000ABD (v02 INSYDE EDK2     00001000 ACPI 00040000)
[    0.003676] ACPI: ASF! 0x000000005AFF1000 0000A5 (v32 INSYDE EDK2     00000002 ACPI 00040000)
[    0.003678] ACPI: BOOT 0x000000005AFF0000 000028 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    0.003679] ACPI: HPET 0x000000005AFEE000 000038 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    0.003681] ACPI: APIC 0x000000005AFED000 000138 (v03 INSYDE EDK2     00000002 ACPI 00040000)
[    0.003682] ACPI: MCFG 0x000000005AFEC000 00003C (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    0.003683] ACPI: SLIC 0x000000005AFEB000 000176 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    0.003684] ACPI: VFCT 0x000000005AFDA000 004284 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003686] ACPI: SSDT 0x000000005AFD9000 0000F8 (v02 INSYDE EDK2     00001000 ACPI 00040000)
[    0.003687] ACPI: SSDT 0x000000005AFD3000 00547E (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003688] ACPI: CRAT 0x000000005AFD2000 000F10 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003690] ACPI: CDIT 0x000000005AFD1000 000029 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003691] ACPI: SSDT 0x000000005AFD0000 000F8D (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003692] ACPI: SSDT 0x000000005AFCF000 000EC1 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003694] ACPI: SSDT 0x000000005AFCE000 000931 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003695] ACPI: SSDT 0x000000005AFCB000 0013EC (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003696] ACPI: SSDT 0x000000005AFFD000 00077A (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003698] ACPI: SSDT 0x000000005AFCA000 000737 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003699] ACPI: SSDT 0x000000005AFC8000 0015C8 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003700] ACPI: SSDT 0x000000005AFC5000 002A8F (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003701] ACPI: SSDT 0x000000005AFBB000 009821 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003703] ACPI: FPDT 0x000000005AFBA000 000044 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    0.003704] ACPI: BGRT 0x000000005AFB9000 000038 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    0.003705] ACPI: WSMT 0x000000005AFB8000 000028 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003707] ACPI: MHSP 0x000000005AFEA000 0000C8 (v04 INSYDE EDK2     20505348 ACPI 00040000)
[    0.003708] ACPI: SSDT 0x000000005AFE9000 0000E5 (v02 INSYDE EDK2     00000004 ACPI 00040000)
[    0.003709] ACPI: IVRS 0x000000005AFB7000 0001A4 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003711] ACPI: SSDT 0x000000005AFB6000 000747 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003712] ACPI: SSDT 0x000000005AFB5000 000C88 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003713] ACPI: SSDT 0x000000005AFB4000 000057 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003715] ACPI: SSDT 0x000000005AFB2000 00170B (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003716] ACPI: SSDT 0x000000005AFB1000 000FF7 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003717] ACPI: SSDT 0x000000005AFA7000 0097E3 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003718] ACPI: SSDT 0x000000005AFA2000 004FEB (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003720] ACPI: SSDT 0x000000005AFA1000 000C7F (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003721] ACPI: SSDT 0x000000005AFA0000 000956 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003722] ACPI: SSDT 0x000000005AF9F000 00008D (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003724] ACPI: SSDT 0x000000005AFCD000 000EAD (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.003725] ACPI: Reserving FACP table memory at [mem 0x5afef000-0x5afef10b]
[    0.003725] ACPI: Reserving DSDT table memory at [mem 0x5afdf000-0x5afe83a5]
[    0.003726] ACPI: Reserving FACS table memory at [mem 0x5aeb7000-0x5aeb703f]
[    0.003726] ACPI: Reserving UEFI table memory at [mem 0x5af67000-0x5af671ce]
[    0.003727] ACPI: Reserving SSDT table memory at [mem 0x5aff4000-0x5affc415]
[    0.003727] ACPI: Reserving SSDT table memory at [mem 0x5aff2000-0x5aff2abc]
[    0.003727] ACPI: Reserving ASF! table memory at [mem 0x5aff1000-0x5aff10a4]
[    0.003728] ACPI: Reserving BOOT table memory at [mem 0x5aff0000-0x5aff0027]
[    0.003728] ACPI: Reserving HPET table memory at [mem 0x5afee000-0x5afee037]
[    0.003729] ACPI: Reserving APIC table memory at [mem 0x5afed000-0x5afed137]
[    0.003729] ACPI: Reserving MCFG table memory at [mem 0x5afec000-0x5afec03b]
[    0.003729] ACPI: Reserving SLIC table memory at [mem 0x5afeb000-0x5afeb175]
[    0.003730] ACPI: Reserving VFCT table memory at [mem 0x5afda000-0x5afde283]
[    0.003730] ACPI: Reserving SSDT table memory at [mem 0x5afd9000-0x5afd90f7]
[    0.003730] ACPI: Reserving SSDT table memory at [mem 0x5afd3000-0x5afd847d]
[    0.003731] ACPI: Reserving CRAT table memory at [mem 0x5afd2000-0x5afd2f0f]
[    0.003731] ACPI: Reserving CDIT table memory at [mem 0x5afd1000-0x5afd1028]
[    0.003731] ACPI: Reserving SSDT table memory at [mem 0x5afd0000-0x5afd0f8c]
[    0.003732] ACPI: Reserving SSDT table memory at [mem 0x5afcf000-0x5afcfec0]
[    0.003732] ACPI: Reserving SSDT table memory at [mem 0x5afce000-0x5afce930]
[    0.003733] ACPI: Reserving SSDT table memory at [mem 0x5afcb000-0x5afcc3eb]
[    0.003733] ACPI: Reserving SSDT table memory at [mem 0x5affd000-0x5affd779]
[    0.003733] ACPI: Reserving SSDT table memory at [mem 0x5afca000-0x5afca736]
[    0.003734] ACPI: Reserving SSDT table memory at [mem 0x5afc8000-0x5afc95c7]
[    0.003734] ACPI: Reserving SSDT table memory at [mem 0x5afc5000-0x5afc7a8e]
[    0.003734] ACPI: Reserving SSDT table memory at [mem 0x5afbb000-0x5afc4820]
[    0.003735] ACPI: Reserving FPDT table memory at [mem 0x5afba000-0x5afba043]
[    0.003735] ACPI: Reserving BGRT table memory at [mem 0x5afb9000-0x5afb9037]
[    0.003736] ACPI: Reserving WSMT table memory at [mem 0x5afb8000-0x5afb8027]
[    0.003736] ACPI: Reserving MHSP table memory at [mem 0x5afea000-0x5afea0c7]
[    0.003736] ACPI: Reserving SSDT table memory at [mem 0x5afe9000-0x5afe90e4]
[    0.003737] ACPI: Reserving IVRS table memory at [mem 0x5afb7000-0x5afb71a3]
[    0.003737] ACPI: Reserving SSDT table memory at [mem 0x5afb6000-0x5afb6746]
[    0.003738] ACPI: Reserving SSDT table memory at [mem 0x5afb5000-0x5afb5c87]
[    0.003738] ACPI: Reserving SSDT table memory at [mem 0x5afb4000-0x5afb4056]
[    0.003738] ACPI: Reserving SSDT table memory at [mem 0x5afb2000-0x5afb370a]
[    0.003739] ACPI: Reserving SSDT table memory at [mem 0x5afb1000-0x5afb1ff6]
[    0.003739] ACPI: Reserving SSDT table memory at [mem 0x5afa7000-0x5afb07e2]
[    0.003739] ACPI: Reserving SSDT table memory at [mem 0x5afa2000-0x5afa6fea]
[    0.003740] ACPI: Reserving SSDT table memory at [mem 0x5afa1000-0x5afa1c7e]
[    0.003740] ACPI: Reserving SSDT table memory at [mem 0x5afa0000-0x5afa0955]
[    0.003741] ACPI: Reserving SSDT table memory at [mem 0x5af9f000-0x5af9f08c]
[    0.003741] ACPI: Reserving SSDT table memory at [mem 0x5afcd000-0x5afcdeac]
[    0.003795] Zone ranges:
[    0.003796]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.003797]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.003798]   Normal   [mem 0x0000000100000000-0x000000107e2fffff]
[    0.003799]   Device   empty
[    0.003799] Movable zone start for each node
[    0.003800] Early memory node ranges
[    0.003800]   node   0: [mem 0x0000000000001000-0x000000000009efff]
[    0.003801]   node   0: [mem 0x0000000000100000-0x0000000009afffff]
[    0.003801]   node   0: [mem 0x0000000009e00000-0x0000000009efffff]
[    0.003802]   node   0: [mem 0x0000000009f3c000-0x000000004235ffff]
[    0.003802]   node   0: [mem 0x0000000044560000-0x0000000044568fff]
[    0.003803]   node   0: [mem 0x000000004456d000-0x000000004456efff]
[    0.003803]   node   0: [mem 0x0000000044570000-0x000000005077efff]
[    0.003803]   node   0: [mem 0x000000005afff000-0x000000005affffff]
[    0.003804]   node   0: [mem 0x0000000100000000-0x000000107e2fffff]
[    0.003807] Initmem setup node 0 [mem 0x0000000000001000-0x000000107e2fffff]
[    0.003811] On node 0, zone DMA: 1 pages in unavailable ranges
[    0.003819] On node 0, zone DMA: 97 pages in unavailable ranges
[    0.003884] On node 0, zone DMA32: 768 pages in unavailable ranges
[    0.004253] On node 0, zone DMA32: 60 pages in unavailable ranges
[    0.004277] On node 0, zone DMA32: 8704 pages in unavailable ranges
[    0.004277] On node 0, zone DMA32: 4 pages in unavailable ranges
[    0.004420] On node 0, zone DMA32: 1 pages in unavailable ranges
[    0.004552] On node 0, zone DMA32: 43136 pages in unavailable ranges
[    0.042211] On node 0, zone Normal: 20480 pages in unavailable ranges
[    0.042233] On node 0, zone Normal: 7424 pages in unavailable ranges
[    0.042516] ACPI: PM-Timer IO Port: 0x408
[    0.042522] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.042523] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.042523] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.042523] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    0.042524] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[    0.042524] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
[    0.042525] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
[    0.042525] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
[    0.042525] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
[    0.042526] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
[    0.042526] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
[    0.042526] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
[    0.042527] ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
[    0.042527] ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
[    0.042527] ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
[    0.042528] ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
[    0.042541] IOAPIC[0]: apic_id 33, version 33, address 0xfec00000, GSI 0-23
[    0.042545] IOAPIC[1]: apic_id 34, version 33, address 0xfec01000, GSI 24-55
[    0.042546] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.042547] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[    0.042550] ACPI: Using ACPI (MADT) for SMP configuration information
[    0.042550] ACPI: HPET id: 0x10228210 base: 0xfed00000
[    0.042557] e820: update [mem 0x4b822000-0x4b870fff] usable ==> reserved
[    0.042566] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
[    0.042580] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.042581] PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000bffff]
[    0.042582] PM: hibernation: Registered nosave memory: [mem 0x000c0000-0x000fffff]
[    0.042583] PM: hibernation: Registered nosave memory: [mem 0x09b00000-0x09dfffff]
[    0.042584] PM: hibernation: Registered nosave memory: [mem 0x09f00000-0x09f3bfff]
[    0.042584] PM: hibernation: Registered nosave memory: [mem 0x42360000-0x4455ffff]
[    0.042585] PM: hibernation: Registered nosave memory: [mem 0x44569000-0x4456cfff]
[    0.042586] PM: hibernation: Registered nosave memory: [mem 0x4456f000-0x4456ffff]
[    0.042587] PM: hibernation: Registered nosave memory: [mem 0x44575000-0x44575fff]
[    0.042588] PM: hibernation: Registered nosave memory: [mem 0x44579000-0x44579fff]
[    0.042589] PM: hibernation: Registered nosave memory: [mem 0x4b822000-0x4b870fff]
[    0.042590] PM: hibernation: Registered nosave memory: [mem 0x4d16c000-0x4d16cfff]
[    0.042591] PM: hibernation: Registered nosave memory: [mem 0x5077f000-0x52f7efff]
[    0.042591] PM: hibernation: Registered nosave memory: [mem 0x52f7f000-0x5af7efff]
[    0.042592] PM: hibernation: Registered nosave memory: [mem 0x5af7f000-0x5affefff]
[    0.042592] PM: hibernation: Registered nosave memory: [mem 0x5b000000-0x5bffffff]
[    0.042593] PM: hibernation: Registered nosave memory: [mem 0x5c000000-0x5d78ffff]
[    0.042593] PM: hibernation: Registered nosave memory: [mem 0x5d790000-0x5d7effff]
[    0.042593] PM: hibernation: Registered nosave memory: [mem 0x5d7f0000-0x5d7f4fff]
[    0.042594] PM: hibernation: Registered nosave memory: [mem 0x5d7f5000-0x5fffffff]
[    0.042594] PM: hibernation: Registered nosave memory: [mem 0x60000000-0xfed7ffff]
[    0.042594] PM: hibernation: Registered nosave memory: [mem 0xfed80000-0xfed80fff]
[    0.042595] PM: hibernation: Registered nosave memory: [mem 0xfed81000-0xffffffff]
[    0.042596] [mem 0x60000000-0xfed7ffff] available for PCI devices
[    0.042597] Booting paravirtualized kernel on bare hardware
[    0.042598] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[    0.046202] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:16 nr_cpu_ids:16 nr_node_ids:1
[    0.046436] percpu: Embedded 64 pages/cpu s225280 r8192 d28672 u262144
[    0.046440] pcpu-alloc: s225280 r8192 d28672 u262144 alloc=1*2097152
[    0.046441] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15 
[    0.046458] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.6.7xen-irq-dbg-1+ root=UUID=71b1dc59-ea00-484c-b5e4-ee77ede771db ro "dyndbg=file drivers/gpio/* +p; file drivers/pinctrl/* +p; file arch/x86/pci/xen.c +p"
[    0.046494] Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-6.6.7xen-irq-dbg-1+", will be passed to user space.
[    0.048721] Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes, linear)
[    0.049762] Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
[    0.049798] Built 1 zonelists, mobility grouping on.  Total pages: 16306474
[    0.049877] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
[    0.049923] software IO TLB: area num 16.
[    0.094595] Memory: 64692184K/66261876K available (18432K kernel code, 3168K rwdata, 14456K rodata, 3944K init, 3704K bss, 1569436K reserved, 0K cma-reserved)
[    0.094742] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
[    0.094759] ftrace: allocating 53307 entries in 209 pages
[    0.101822] ftrace: allocated 209 pages with 4 groups
[    0.102375] Dynamic Preempt: voluntary
[    0.102410] rcu: Preemptible hierarchical RCU implementation.
[    0.102411] rcu: 	RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=16.
[    0.102411] 	Trampoline variant of Tasks RCU enabled.
[    0.102412] 	Rude variant of Tasks RCU enabled.
[    0.102412] 	Tracing variant of Tasks RCU enabled.
[    0.102412] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[    0.102413] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=16
[    0.104074] NR_IRQS: 524544, nr_irqs: 1096, preallocated irqs: 16
[    0.104265] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.104403] kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval____)-0x(____ptrval____)
[    0.104428] Console: colour dummy device 80x25
[    0.104429] printk: console [tty0] enabled
[    0.104731] ACPI: Core revision 20230628
[    0.104918] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns
[    0.104938] APIC: Switch to symmetric I/O mode setup
[    0.105543] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR0, rdevid:160
[    0.105546] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR1, rdevid:160
[    0.105547] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR2, rdevid:160
[    0.105548] AMD-Vi: ivrs, add hid:AMDI0020, uid:\_SB.FUR3, rdevid:160
[    0.105550] AMD-Vi: Using global IVHD EFR:0x246577efa2254afa, EFR2:0x0
[    0.106124] x2apic: IRQ remapping doesn't support X2APIC mode
[    0.106143] APIC: Switched APIC routing to: physical flat
[    0.106922] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.111943] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x2f7a2ab2f4c, max_idle_ns: 440795361553 ns
[    0.111948] Calibrating delay loop (skipped), value calculated using timer frequency.. 6587.46 BogoMIPS (lpj=3293731)
[    0.111968] x86/cpu: User Mode Instruction Prevention (UMIP) activated
[    0.112012] LVT offset 1 assigned for vector 0xf9
[    0.112174] LVT offset 2 assigned for vector 0xf4
[    0.112212] process: using mwait in idle threads
[    0.112213] Last level iTLB entries: 4KB 512, 2MB 512, 4MB 256
[    0.112215] Last level dTLB entries: 4KB 2048, 2MB 2048, 4MB 1024, 1GB 0
[    0.112218] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.112221] Spectre V2 : Mitigation: Enhanced / Automatic IBRS
[    0.112222] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.112225] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.112227] Spectre V2 : User space: Mitigation: STIBP always-on protection
[    0.112229] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
[    0.112231] Speculative Return Stack Overflow: IBPB-extending microcode not applied!
[    0.112232] Speculative Return Stack Overflow: WARNING: See https://kernel.org/doc/html/latest/admin-guide/hw-vuln/srso.html for mitigation options.
[    0.112233] Speculative Return Stack Overflow: Vulnerable: Safe RET, no microcode
[    0.112239] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.112241] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.112242] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.112244] x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
[    0.112245] x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
[    0.112246] x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
[    0.112247] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
[    0.112249] x86/fpu: Supporting XSAVE feature 0x800: 'Control-flow User registers'
[    0.112251] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.112252] x86/fpu: xstate_offset[5]:  832, xstate_sizes[5]:   64
[    0.112254] x86/fpu: xstate_offset[6]:  896, xstate_sizes[6]:  512
[    0.112255] x86/fpu: xstate_offset[7]: 1408, xstate_sizes[7]: 1024
[    0.112256] x86/fpu: xstate_offset[9]: 2432, xstate_sizes[9]:    8
[    0.112257] x86/fpu: xstate_offset[11]: 2440, xstate_sizes[11]:   16
[    0.112259] x86/fpu: Enabled xstate features 0xae7, context size is 2456 bytes, using 'compacted' format.
[    0.128651] Freeing SMP alternatives memory: 48K
[    0.128655] pid_max: default: 32768 minimum: 301
[    0.130985] LSM: initializing lsm=lockdown,capability,yama,selinux,bpf,landlock,integrity
[    0.131003] Yama: becoming mindful.
[    0.131007] SELinux:  Initializing.
[    0.131045] LSM support for eBPF active
[    0.131048] landlock: Up and running.
[    0.131106] Mount-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.131150] Mountpoint-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.234048] smpboot: CPU0: AMD Ryzen 7 7840U w/ Radeon  780M Graphics (family: 0x19, model: 0x74, stepping: 0x1)
[    0.234217] RCU Tasks: Setting shift to 4 and lim to 1 rcu_task_cb_adjust=1.
[    0.234233] RCU Tasks Rude: Setting shift to 4 and lim to 1 rcu_task_cb_adjust=1.
[    0.234250] RCU Tasks Trace: Setting shift to 4 and lim to 1 rcu_task_cb_adjust=1.
[    0.234269] Performance Events: Fam17h+ 16-deep LBR, core perfctr, AMD PMU driver.
[    0.234295] ... version:                2
[    0.234297] ... bit width:              48
[    0.234300] ... generic registers:      6
[    0.234302] ... value mask:             0000ffffffffffff
[    0.234305] ... max period:             00007fffffffffff
[    0.234307] ... fixed-purpose events:   0
[    0.234309] ... event mask:             000000000000003f
[    0.234375] signal: max sigframe size: 3376
[    0.234397] rcu: Hierarchical SRCU implementation.
[    0.234400] rcu: 	Max phase no-delay instances is 400.
[    0.236934] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[    0.237066] smp: Bringing up secondary CPUs ...
[    0.237159] smpboot: x86: Booting SMP configuration:
[    0.237162] .... node  #0, CPUs:        #2  #4  #6  #8 #10 #12 #14  #1  #3  #5  #7  #9 #11 #13 #15
[    0.248033] Spectre V2 : Update user space SMT mitigation: STIBP always-on
[    0.254977] smp: Brought up 1 node, 16 CPUs
[    0.254977] smpboot: Max logical packages: 1
[    0.254977] smpboot: Total of 16 processors activated (105399.39 BogoMIPS)
[    0.257999] devtmpfs: initialized
[    0.258000] x86/mm: Memory block size: 2048MB
[    0.258361] ACPI: PM: Registering ACPI NVS region [mem 0x09f00000-0x09f3bfff] (245760 bytes)
[    0.258361] ACPI: PM: Registering ACPI NVS region [mem 0x52f7f000-0x5af7efff] (134217728 bytes)
[    0.260323] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[    0.260329] futex hash table entries: 4096 (order: 6, 262144 bytes, linear)
[    0.260393] pinctrl core: initialized pinctrl subsystem
[    0.260506] PM: RTC time: 16:27:16, date: 2023-12-20
[    0.260741] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.260859] DMA: preallocated 4096 KiB GFP_KERNEL pool for atomic allocations
[    0.260865] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.260870] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.260886] audit: initializing netlink subsys (disabled)
[    0.260895] audit: type=2000 audit(1703089636.154:1): state=initialized audit_enabled=0 res=1
[    0.260992] thermal_sys: Registered thermal governor 'fair_share'
[    0.260994] thermal_sys: Registered thermal governor 'bang_bang'
[    0.260997] thermal_sys: Registered thermal governor 'step_wise'
[    0.260999] thermal_sys: Registered thermal governor 'user_space'
[    0.261011] cpuidle: using governor menu
[    0.261047] Simple Boot Flag at 0x44 set to 0x80
[    0.261047] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.261087] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    0.261095] PCI: not using MMCONFIG
[    0.261098] PCI: Using configuration type 1 for base access
[    0.261101] PCI: Using configuration type 1 for extended access
[    0.261577] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
[    0.261997] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[    0.261997] HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page
[    0.261997] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[    0.261997] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page
[    0.262046] cryptd: max_cpu_qlen set to 1000
[    0.262046] raid6: skipped pq benchmark and selected avx512x4
[    0.262046] raid6: using avx512x2 recovery algorithm
[    0.262046] fbcon: Taking over console
[    0.262072] ACPI: Added _OSI(Module Device)
[    0.262075] ACPI: Added _OSI(Processor Device)
[    0.262078] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.262082] ACPI: Added _OSI(Processor Aggregator Device)
[    0.286756] ACPI: 26 ACPI AML tables successfully acquired and loaded
[    0.304035] ACPI: USB4 _OSC: OS supports USB3+ DisplayPort+ PCIe+ XDomain+
[    0.304040] ACPI: USB4 _OSC: OS controls USB3+ DisplayPort+ PCIe+ XDomain+
[    0.304119] ACPI: _OSC evaluation for CPUs failed, trying _PDC
[    0.304657] ACPI: EC: EC started
[    0.304659] ACPI: EC: interrupt blocked
[    0.304768] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.304772] ACPI: \_SB_.PCI0.LPC0.EC0_: Boot DSDT EC used to handle transactions
[    0.304776] ACPI: Interpreter enabled
[    0.304790] ACPI: PM: (supports S0 S4 S5)
[    0.304793] ACPI: Using IOAPIC for interrupt routing
[    0.306259] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    0.310365] [Firmware Info]: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] not reserved in ACPI motherboard resources
[    0.310371] PCI: not using MMCONFIG
[    0.310375] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.310379] PCI: Ignoring E820 reservations for host bridge windows
[    0.310792] ACPI: Enabled 3 GPEs in block 00 to 1F
[    0.313818] ACPI: \_SB_.PCI0.GPP8.P0NV: New power resource
[    0.315950] ACPI: \_SB_.PCI0.GP11.PWRS: New power resource
[    0.317497] ACPI: \_SB_.PCI0.GP11.SWUS.PWRS: New power resource
[    0.319021] ACPI: \_SB_.PCI0.GP12.PWRS: New power resource
[    0.320484] ACPI: \_SB_.PCI0.GP12.SWUS.PWRS: New power resource
[    0.320759] ACPI: \_SB_.PCI0.GP17.PWRS: New power resource
[    0.321048] ACPI: \_SB_.PCI0.GP17.VGA_.PWRS: New power resource
[    0.321422] ACPI: \_SB_.PCI0.GP17.ACP_.PWRS: New power resource
[    0.322126] ACPI: \_SB_.PCI0.GP17.AZAL.PWRS: New power resource
[    0.322623] ACPI: \_SB_.PCI0.GP17.HDAU.PWRS: New power resource
[    0.323075] ACPI: \_SB_.PCI0.GP17.XHC0.PWRS: New power resource
[    0.326251] ACPI: \_SB_.PCI0.GP17.XHC1.PWRS: New power resource
[    0.328201] ACPI: \_SB_.PCI0.GP19.XHC2.PWRS: New power resource
[    0.329808] ACPI: \_SB_.PCI0.GP19.NHI0.PWRS: New power resource
[    0.330724] ACPI: \_SB_.PCI0.GP19.XHC3.PWRS: New power resource
[    0.332387] ACPI: \_SB_.PCI0.GP19.NHI1.PWRS: New power resource
[    0.333304] ACPI: \_SB_.PCI0.GP19.XHC4.PWRS: New power resource
[    0.340663] ACPI: \_SB_.PRWL: New power resource
[    0.340693] ACPI: \_SB_.PRWB: New power resource
[    0.341700] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.341707] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
[    0.341894] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug AER]
[    0.342245] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME PCIeCapability LTR DPC]
[    0.342738] PCI host bridge to bus 0000:00
[    0.342741] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    0.342745] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    0.342749] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    0.342753] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000cffff window]
[    0.342757] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000effff window]
[    0.342761] pci_bus 0000:00: root bus resource [mem 0x60000000-0x90bfffff window]
[    0.342765] pci_bus 0000:00: root bus resource [mem 0xf0000000-0xfec00000 window]
[    0.342768] pci_bus 0000:00: root bus resource [mem 0xfed45000-0xfed814ff window]
[    0.342772] pci_bus 0000:00: root bus resource [mem 0xfed81900-0xfed81fff window]
[    0.342776] pci_bus 0000:00: root bus resource [mem 0xfedc0000-0xfedc0fff window]
[    0.342780] pci_bus 0000:00: root bus resource [mem 0xfedc6000-0xfedc6fff window]
[    0.342783] pci_bus 0000:00: root bus resource [mem 0x10c0200000-0x891fffffff window]
[    0.342787] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.342808] pci 0000:00:00.0: [1022:14e8] type 00 class 0x060000
[    0.342873] pci 0000:00:00.2: [1022:14e9] type 00 class 0x080600
[    0.342955] pci 0000:00:01.0: [1022:14ea] type 00 class 0x060000
[    0.343022] pci 0000:00:02.0: [1022:14ea] type 00 class 0x060000
[    0.343088] pci 0000:00:02.2: [1022:14ee] type 01 class 0x060400
[    0.343147] pci 0000:00:02.2: PME# supported from D0 D3hot D3cold
[    0.343246] pci 0000:00:02.4: [1022:14ee] type 01 class 0x060400
[    0.343304] pci 0000:00:02.4: PME# supported from D0 D3hot D3cold
[    0.343386] pci 0000:00:03.0: [1022:14ea] type 00 class 0x060000
[    0.343454] pci 0000:00:03.1: [1022:14ef] type 01 class 0x060400
[    0.343895] pci 0000:00:03.1: PME# supported from D0 D3hot D3cold
[    0.345017] pci 0000:00:04.0: [1022:14ea] type 00 class 0x060000
[    0.345086] pci 0000:00:04.1: [1022:14ef] type 01 class 0x060400
[    0.345517] pci 0000:00:04.1: PME# supported from D0 D3hot D3cold
[    0.346724] pci 0000:00:08.0: [1022:14ea] type 00 class 0x060000
[    0.347055] pci 0000:00:08.1: [1022:14eb] type 01 class 0x060400
[    0.347079] pci 0000:00:08.1: enabling Extended Tags
[    0.347105] pci 0000:00:08.1: PME# supported from D0 D3hot D3cold
[    0.347204] pci 0000:00:08.2: [1022:14eb] type 01 class 0x060400
[    0.347260] pci 0000:00:08.2: enabling Extended Tags
[    0.347285] pci 0000:00:08.2: PME# supported from D0 D3hot D3cold
[    0.347358] pci 0000:00:08.3: [1022:14eb] type 01 class 0x060400
[    0.347382] pci 0000:00:08.3: enabling Extended Tags
[    0.347407] pci 0000:00:08.3: PME# supported from D0 D3hot D3cold
[    0.347659] pci 0000:00:14.0: [1022:790b] type 00 class 0x0c0500
[    0.347790] pci 0000:00:14.3: [1022:790e] type 00 class 0x060100
[    0.347938] pci 0000:00:18.0: [1022:14f0] type 00 class 0x060000
[    0.347974] pci 0000:00:18.1: [1022:14f1] type 00 class 0x060000
[    0.348008] pci 0000:00:18.2: [1022:14f2] type 00 class 0x060000
[    0.348042] pci 0000:00:18.3: [1022:14f3] type 00 class 0x060000
[    0.348076] pci 0000:00:18.4: [1022:14f4] type 00 class 0x060000
[    0.348110] pci 0000:00:18.5: [1022:14f5] type 00 class 0x060000
[    0.348145] pci 0000:00:18.6: [1022:14f6] type 00 class 0x060000
[    0.348179] pci 0000:00:18.7: [1022:14f7] type 00 class 0x060000
[    0.348307] pci 0000:01:00.0: [14c3:0616] type 00 class 0x028000
[    0.348329] pci 0000:01:00.0: reg 0x10: [mem 0x8810900000-0x88109fffff 64bit pref]
[    0.348345] pci 0000:01:00.0: reg 0x18: [mem 0x90b00000-0x90b07fff 64bit]
[    0.348420] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[    0.348510] pci 0000:00:02.2: PCI bridge to [bus 01]
[    0.348517] pci 0000:00:02.2:   bridge window [mem 0x90b00000-0x90bfffff]
[    0.348523] pci 0000:00:02.2:   bridge window [mem 0x8810900000-0x88109fffff 64bit pref]
[    0.348806] pci 0000:02:00.0: [15b7:5030] type 00 class 0x010802
[    0.348824] pci 0000:02:00.0: reg 0x10: [mem 0x90a00000-0x90a03fff 64bit]
[    0.348971] pci 0000:00:02.4: PCI bridge to [bus 02]
[    0.348978] pci 0000:00:02.4:   bridge window [mem 0x90a00000-0x90afffff]
[    0.349088] pci 0000:00:03.1: PCI bridge to [bus 03-61]
[    0.349095] pci 0000:00:03.1:   bridge window [io  0x6000-0x9fff]
[    0.349100] pci 0000:00:03.1:   bridge window [mem 0x78000000-0x8fffffff]
[    0.349107] pci 0000:00:03.1:   bridge window [mem 0x7800000000-0x87ffffffff 64bit pref]
[    0.349216] pci 0000:00:04.1: PCI bridge to [bus 62-c0]
[    0.349223] pci 0000:00:04.1:   bridge window [io  0x2000-0x5fff]
[    0.349228] pci 0000:00:04.1:   bridge window [mem 0x60000000-0x77ffffff]
[    0.349235] pci 0000:00:04.1:   bridge window [mem 0x6800000000-0x77ffffffff 64bit pref]
[    0.349341] pci 0000:c1:00.0: [1002:15bf] type 00 class 0x030000
[    0.349356] pci 0000:c1:00.0: reg 0x10: [mem 0x8800000000-0x880fffffff 64bit pref]
[    0.349367] pci 0000:c1:00.0: reg 0x18: [mem 0x90000000-0x901fffff 64bit pref]
[    0.349375] pci 0000:c1:00.0: reg 0x20: [io  0x1000-0x10ff]
[    0.349383] pci 0000:c1:00.0: reg 0x24: [mem 0x90500000-0x9057ffff]
[    0.349395] pci 0000:c1:00.0: enabling Extended Tags
[    0.349405] pci 0000:c1:00.0: BAR 0: assigned to efifb
[    0.349435] pci 0000:c1:00.0: PME# supported from D1 D2 D3hot D3cold
[    0.349525] pci 0000:c1:00.1: [1002:1640] type 00 class 0x040300
[    0.349535] pci 0000:c1:00.1: reg 0x10: [mem 0x905c8000-0x905cbfff]
[    0.349562] pci 0000:c1:00.1: enabling Extended Tags
[    0.349594] pci 0000:c1:00.1: PME# supported from D1 D2 D3hot D3cold
[    0.349678] pci 0000:c1:00.2: [1022:15c7] type 00 class 0x108000
[    0.349695] pci 0000:c1:00.2: reg 0x18: [mem 0x90400000-0x904fffff]
[    0.349708] pci 0000:c1:00.2: reg 0x24: [mem 0x905cc000-0x905cdfff]
[    0.349718] pci 0000:c1:00.2: enabling Extended Tags
[    0.349832] pci 0000:c1:00.3: [1022:15b9] type 00 class 0x0c0330
[    0.349847] pci 0000:c1:00.3: reg 0x10: [mem 0x90200000-0x902fffff 64bit]
[    0.349877] pci 0000:c1:00.3: enabling Extended Tags
[    0.349911] pci 0000:c1:00.3: PME# supported from D0 D3hot D3cold
[    0.350254] pci 0000:c1:00.4: [1022:15ba] type 00 class 0x0c0330
[    0.350268] pci 0000:c1:00.4: reg 0x10: [mem 0x90300000-0x903fffff 64bit]
[    0.350299] pci 0000:c1:00.4: enabling Extended Tags
[    0.350333] pci 0000:c1:00.4: PME# supported from D0 D3hot D3cold
[    0.350665] pci 0000:c1:00.5: [1022:15e2] type 00 class 0x048000
[    0.350675] pci 0000:c1:00.5: reg 0x10: [mem 0x90580000-0x905bffff]
[    0.350688] pci 0000:c1:00.5: reg 0x18: [mem 0x8810000000-0x88107fffff 64bit pref]
[    0.350705] pci 0000:c1:00.5: enabling Extended Tags
[    0.350737] pci 0000:c1:00.5: PME# supported from D0 D3hot D3cold
[    0.350827] pci 0000:c1:00.6: [1022:15e3] type 00 class 0x040300
[    0.350838] pci 0000:c1:00.6: reg 0x10: [mem 0x905c0000-0x905c7fff]
[    0.350864] pci 0000:c1:00.6: enabling Extended Tags
[    0.350896] pci 0000:c1:00.6: PME# supported from D0 D3hot D3cold
[    0.351006] pci 0000:00:08.1: PCI bridge to [bus c1]
[    0.351011] pci 0000:00:08.1:   bridge window [io  0x1000-0x1fff]
[    0.351015] pci 0000:00:08.1:   bridge window [mem 0x90000000-0x905fffff]
[    0.351020] pci 0000:00:08.1:   bridge window [mem 0x8800000000-0x88107fffff 64bit pref]
[    0.351078] pci 0000:c2:00.0: [1022:14ec] type 00 class 0x130000
[    0.351111] pci 0000:c2:00.0: enabling Extended Tags
[    0.351145] pci 0000:c2:00.0: PME# supported from D3hot D3cold
[    0.351203] pci 0000:c2:00.1: [1022:1502] type 00 class 0x118000
[    0.351221] pci 0000:c2:00.1: reg 0x10: [mem 0x90900000-0x9097ffff]
[    0.351228] pci 0000:c2:00.1: reg 0x14: [mem 0x909c0000-0x909c1fff]
[    0.351237] pci 0000:c2:00.1: reg 0x18: [mem 0x8810800000-0x881083ffff 64bit pref]
[    0.351244] pci 0000:c2:00.1: reg 0x20: [mem 0x90980000-0x909bffff]
[    0.351257] pci 0000:c2:00.1: enabling Extended Tags
[    0.351374] pci 0000:00:08.2: PCI bridge to [bus c2]
[    0.351380] pci 0000:00:08.2:   bridge window [mem 0x90900000-0x909fffff]
[    0.351385] pci 0000:00:08.2:   bridge window [mem 0x8810800000-0x88108fffff 64bit pref]
[    0.351465] pci 0000:c3:00.0: [1022:14ec] type 00 class 0x130000
[    0.351498] pci 0000:c3:00.0: enabling Extended Tags
[    0.351856] pci 0000:c3:00.3: [1022:15c0] type 00 class 0x0c0330
[    0.351871] pci 0000:c3:00.3: reg 0x10: [mem 0x90600000-0x906fffff 64bit]
[    0.351901] pci 0000:c3:00.3: enabling Extended Tags
[    0.351936] pci 0000:c3:00.3: PME# supported from D0 D3hot D3cold
[    0.352268] pci 0000:c3:00.4: [1022:15c1] type 00 class 0x0c0330
[    0.352283] pci 0000:c3:00.4: reg 0x10: [mem 0x90700000-0x907fffff 64bit]
[    0.352313] pci 0000:c3:00.4: enabling Extended Tags
[    0.352348] pci 0000:c3:00.4: PME# supported from D0 D3hot D3cold
[    0.352678] pci 0000:c3:00.5: [1022:1668] type 00 class 0x0c0340
[    0.352696] pci 0000:c3:00.5: reg 0x10: [mem 0x90800000-0x9087ffff 64bit]
[    0.352731] pci 0000:c3:00.5: Max Payload Size set to 128 (was 256, max 256)
[    0.352737] pci 0000:c3:00.5: enabling Extended Tags
[    0.352771] pci 0000:c3:00.5: PME# supported from D0 D3hot D3cold
[    0.352858] pci 0000:c3:00.6: [1022:1669] type 00 class 0x0c0340
[    0.352876] pci 0000:c3:00.6: reg 0x10: [mem 0x90880000-0x908fffff 64bit]
[    0.352911] pci 0000:c3:00.6: Max Payload Size set to 128 (was 256, max 256)
[    0.352916] pci 0000:c3:00.6: enabling Extended Tags
[    0.352952] pci 0000:c3:00.6: PME# supported from D0 D3hot D3cold
[    0.353053] pci 0000:00:08.3: PCI bridge to [bus c3]
[    0.353060] pci 0000:00:08.3:   bridge window [mem 0x90600000-0x908fffff]
[    0.353127] pci_bus 0000:00: on NUMA node 0
[    0.361415] ACPI: PCI: Interrupt link LNKA configured for IRQ 0
[    0.361420] ACPI: PCI: Interrupt link LNKA disabled
[    0.361646] ACPI: PCI: Interrupt link LNKB configured for IRQ 0
[    0.361649] ACPI: PCI: Interrupt link LNKB disabled
[    0.361859] ACPI: PCI: Interrupt link LNKC configured for IRQ 0
[    0.361862] ACPI: PCI: Interrupt link LNKC disabled
[    0.362088] ACPI: PCI: Interrupt link LNKD configured for IRQ 0
[    0.362091] ACPI: PCI: Interrupt link LNKD disabled
[    0.362311] ACPI: PCI: Interrupt link LNKE configured for IRQ 0
[    0.362314] ACPI: PCI: Interrupt link LNKE disabled
[    0.362487] ACPI: PCI: Interrupt link LNKF configured for IRQ 0
[    0.362490] ACPI: PCI: Interrupt link LNKF disabled
[    0.362662] ACPI: PCI: Interrupt link LNKG configured for IRQ 0
[    0.362665] ACPI: PCI: Interrupt link LNKG disabled
[    0.362837] ACPI: PCI: Interrupt link LNKH configured for IRQ 0
[    0.362840] ACPI: PCI: Interrupt link LNKH disabled
[    0.367648] Low-power S0 idle used by default for system suspend
[    0.367763] ACPI: EC: interrupt unblocked
[    0.367766] ACPI: EC: event unblocked
[    0.367774] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.367778] ACPI: EC: GPE=0xb
[    0.367781] ACPI: \_SB_.PCI0.LPC0.EC0_: Boot DSDT EC initialization complete
[    0.367786] ACPI: \_SB_.PCI0.LPC0.EC0_: EC: Used to handle transactions and events
[    0.367986] iommu: Default domain type: Translated
[    0.367986] iommu: DMA domain TLB invalidation policy: lazy mode
[    0.368019] SCSI subsystem initialized
[    0.368019] libata version 3.00 loaded.
[    0.368019] ACPI: bus type USB registered
[    0.368019] usbcore: registered new interface driver usbfs
[    0.368019] usbcore: registered new interface driver hub
[    0.368019] usbcore: registered new device driver usb
[    0.375549] i2c_designware AMDI0010:00: using ACPI '\_SB.I2CA' for 'scl' GPIO lookup
[    0.375553] acpi AMDI0010:00: GPIO: looking up scl-gpios
[    0.375554] acpi AMDI0010:00: GPIO: looking up scl-gpio
[    0.375556] i2c_designware AMDI0010:00: using lookup tables for GPIO lookup
[    0.375557] i2c_designware AMDI0010:00: No GPIO consumer scl found
[    0.383854] i2c_designware AMDI0010:03: using ACPI '\_SB.I2CD' for 'scl' GPIO lookup
[    0.383857] acpi AMDI0010:03: GPIO: looking up scl-gpios
[    0.383858] acpi AMDI0010:03: GPIO: looking up scl-gpio
[    0.383859] i2c_designware AMDI0010:03: using lookup tables for GPIO lookup
[    0.383860] i2c_designware AMDI0010:03: No GPIO consumer scl found
[    0.384819] pps_core: LinuxPPS API ver. 1 registered
[    0.384823] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.384829] PTP clock support registered
[    0.384962] EDAC MC: Ver: 3.0.0
[    0.385201] efivars: Registered efivars operations
[    0.385201] NetLabel: Initializing
[    0.385201] NetLabel:  domain hash size = 128
[    0.385201] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.385201] NetLabel:  unlabeled traffic allowed by default
[    0.385201] mctp: management component transport protocol core
[    0.385201] NET: Registered PF_MCTP protocol family
[    0.385201] PCI: Using ACPI for IRQ routing
[    0.385201] PCI: pci_cache_line_size set to 64 bytes
[    0.385232] e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
[    0.385233] e820: reserve RAM buffer [mem 0x09b00000-0x0bffffff]
[    0.385234] e820: reserve RAM buffer [mem 0x09f00000-0x0bffffff]
[    0.385235] e820: reserve RAM buffer [mem 0x42360000-0x43ffffff]
[    0.385236] e820: reserve RAM buffer [mem 0x44569000-0x47ffffff]
[    0.385236] e820: reserve RAM buffer [mem 0x4456f000-0x47ffffff]
[    0.385237] e820: reserve RAM buffer [mem 0x44575018-0x47ffffff]
[    0.385238] e820: reserve RAM buffer [mem 0x4b822000-0x4bffffff]
[    0.385239] e820: reserve RAM buffer [mem 0x4d16c000-0x4fffffff]
[    0.385239] e820: reserve RAM buffer [mem 0x5077f000-0x53ffffff]
[    0.385240] e820: reserve RAM buffer [mem 0x5b000000-0x5bffffff]
[    0.385241] e820: reserve RAM buffer [mem 0x107e300000-0x107fffffff]
[    0.385276] pci 0000:c1:00.0: vgaarb: setting as boot VGA device
[    0.385276] pci 0000:c1:00.0: vgaarb: bridge control possible
[    0.385276] pci 0000:c1:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
[    0.385276] vgaarb: loaded
[    0.385276] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[    0.385276] hpet0: 3 comparators, 32-bit 14.318180 MHz counter
[    0.387946] clocksource: Switched to clocksource tsc-early
[    0.390815] VFS: Disk quotas dquot_6.6.0
[    0.390829] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.390903] pnp: PnP ACPI init
[    0.391105] system 00:00: [mem 0xfec00000-0xfec01fff] could not be reserved
[    0.391111] system 00:00: [mem 0xfee00000-0xfee00fff] has been reserved
[    0.395688] system 00:02: [io  0x0400-0x04cf] has been reserved
[    0.395693] system 00:02: [io  0x04d0-0x04d1] has been reserved
[    0.395696] system 00:02: [io  0x04d6] has been reserved
[    0.395699] system 00:02: [io  0x0c00-0x0c01] has been reserved
[    0.395702] system 00:02: [io  0x0c14] has been reserved
[    0.395705] system 00:02: [io  0x0c50-0x0c52] has been reserved
[    0.395708] system 00:02: [io  0x0c6c] has been reserved
[    0.395711] system 00:02: [io  0x0c6f] has been reserved
[    0.395714] system 00:02: [io  0x0cd0-0x0cdb] has been reserved
[    0.395778] system 00:03: [mem 0x000e0000-0x000fffff] could not be reserved
[    0.395782] system 00:03: [mem 0xfe000000-0xffffffff] could not be reserved
[    0.397258] pnp: PnP ACPI: found 5 devices
[    0.403135] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.403280] NET: Registered PF_INET protocol family
[    0.403393] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.405376] tcp_listen_portaddr_hash hash table entries: 32768 (order: 7, 524288 bytes, linear)
[    0.405403] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.405416] TCP established hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    0.405616] TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear)
[    0.405718] TCP: Hash tables configured (established 524288 bind 65536)
[    0.405864] MPTCP token hash table entries: 65536 (order: 8, 1572864 bytes, linear)
[    0.405910] UDP hash table entries: 32768 (order: 8, 1048576 bytes, linear)
[    0.405962] UDP-Lite hash table entries: 32768 (order: 8, 1048576 bytes, linear)
[    0.406078] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.406085] NET: Registered PF_XDP protocol family
[    0.406095] pci 0000:00:02.2: PCI bridge to [bus 01]
[    0.406106] pci 0000:00:02.2:   bridge window [mem 0x90b00000-0x90bfffff]
[    0.406110] pci 0000:00:02.2:   bridge window [mem 0x8810900000-0x88109fffff 64bit pref]
[    0.406117] pci 0000:00:02.4: PCI bridge to [bus 02]
[    0.406122] pci 0000:00:02.4:   bridge window [mem 0x90a00000-0x90afffff]
[    0.406129] pci 0000:00:03.1: PCI bridge to [bus 03-61]
[    0.406133] pci 0000:00:03.1:   bridge window [io  0x6000-0x9fff]
[    0.406144] pci 0000:00:03.1:   bridge window [mem 0x78000000-0x8fffffff]
[    0.406156] pci 0000:00:03.1:   bridge window [mem 0x7800000000-0x87ffffffff 64bit pref]
[    0.406171] pci 0000:00:04.1: PCI bridge to [bus 62-c0]
[    0.406175] pci 0000:00:04.1:   bridge window [io  0x2000-0x5fff]
[    0.406185] pci 0000:00:04.1:   bridge window [mem 0x60000000-0x77ffffff]
[    0.406198] pci 0000:00:04.1:   bridge window [mem 0x6800000000-0x77ffffffff 64bit pref]
[    0.406214] pci 0000:00:08.1: PCI bridge to [bus c1]
[    0.406217] pci 0000:00:08.1:   bridge window [io  0x1000-0x1fff]
[    0.406222] pci 0000:00:08.1:   bridge window [mem 0x90000000-0x905fffff]
[    0.406226] pci 0000:00:08.1:   bridge window [mem 0x8800000000-0x88107fffff 64bit pref]
[    0.406232] pci 0000:00:08.2: PCI bridge to [bus c2]
[    0.406236] pci 0000:00:08.2:   bridge window [mem 0x90900000-0x909fffff]
[    0.406241] pci 0000:00:08.2:   bridge window [mem 0x8810800000-0x88108fffff 64bit pref]
[    0.406246] pci 0000:00:08.3: PCI bridge to [bus c3]
[    0.406250] pci 0000:00:08.3:   bridge window [mem 0x90600000-0x908fffff]
[    0.406257] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    0.406260] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
[    0.406264] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[    0.406267] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000cffff window]
[    0.406270] pci_bus 0000:00: resource 8 [mem 0x000d0000-0x000effff window]
[    0.406274] pci_bus 0000:00: resource 9 [mem 0x60000000-0x90bfffff window]
[    0.406277] pci_bus 0000:00: resource 10 [mem 0xf0000000-0xfec00000 window]
[    0.406281] pci_bus 0000:00: resource 11 [mem 0xfed45000-0xfed814ff window]
[    0.406284] pci_bus 0000:00: resource 12 [mem 0xfed81900-0xfed81fff window]
[    0.406287] pci_bus 0000:00: resource 13 [mem 0xfedc0000-0xfedc0fff window]
[    0.406291] pci_bus 0000:00: resource 14 [mem 0xfedc6000-0xfedc6fff window]
[    0.406294] pci_bus 0000:00: resource 15 [mem 0x10c0200000-0x891fffffff window]
[    0.406298] pci_bus 0000:01: resource 1 [mem 0x90b00000-0x90bfffff]
[    0.406301] pci_bus 0000:01: resource 2 [mem 0x8810900000-0x88109fffff 64bit pref]
[    0.406305] pci_bus 0000:02: resource 1 [mem 0x90a00000-0x90afffff]
[    0.406308] pci_bus 0000:03: resource 0 [io  0x6000-0x9fff]
[    0.406311] pci_bus 0000:03: resource 1 [mem 0x78000000-0x8fffffff]
[    0.406314] pci_bus 0000:03: resource 2 [mem 0x7800000000-0x87ffffffff 64bit pref]
[    0.406317] pci_bus 0000:62: resource 0 [io  0x2000-0x5fff]
[    0.406320] pci_bus 0000:62: resource 1 [mem 0x60000000-0x77ffffff]
[    0.406323] pci_bus 0000:62: resource 2 [mem 0x6800000000-0x77ffffffff 64bit pref]
[    0.406327] pci_bus 0000:c1: resource 0 [io  0x1000-0x1fff]
[    0.406330] pci_bus 0000:c1: resource 1 [mem 0x90000000-0x905fffff]
[    0.406333] pci_bus 0000:c1: resource 2 [mem 0x8800000000-0x88107fffff 64bit pref]
[    0.406336] pci_bus 0000:c2: resource 1 [mem 0x90900000-0x909fffff]
[    0.406339] pci_bus 0000:c2: resource 2 [mem 0x8810800000-0x88108fffff 64bit pref]
[    0.406343] pci_bus 0000:c3: resource 1 [mem 0x90600000-0x908fffff]
[    0.406675] pci 0000:c1:00.1: D0 power state depends on 0000:c1:00.0
[    0.407228] PCI: CLS 64 bytes, default 64
[    0.407238] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
[    0.407266] Trying to unpack rootfs image as initramfs...
[    0.407286] pci 0000:00:01.0: Adding to iommu group 0
[    0.407320] pci 0000:00:02.0: Adding to iommu group 1
[    0.407334] pci 0000:00:02.2: Adding to iommu group 1
[    0.407349] pci 0000:00:02.4: Adding to iommu group 1
[    0.407378] pci 0000:00:03.0: Adding to iommu group 2
[    0.407393] pci 0000:00:03.1: Adding to iommu group 2
[    0.407422] pci 0000:00:04.0: Adding to iommu group 3
[    0.407438] pci 0000:00:04.1: Adding to iommu group 3
[    0.407479] pci 0000:00:08.0: Adding to iommu group 4
[    0.407496] pci 0000:00:08.1: Adding to iommu group 4
[    0.407511] pci 0000:00:08.2: Adding to iommu group 4
[    0.407526] pci 0000:00:08.3: Adding to iommu group 4
[    0.407554] pci 0000:00:14.0: Adding to iommu group 5
[    0.407570] pci 0000:00:14.3: Adding to iommu group 5
[    0.407636] pci 0000:00:18.0: Adding to iommu group 6
[    0.407653] pci 0000:00:18.1: Adding to iommu group 6
[    0.407669] pci 0000:00:18.2: Adding to iommu group 6
[    0.407686] pci 0000:00:18.3: Adding to iommu group 6
[    0.407704] pci 0000:00:18.4: Adding to iommu group 6
[    0.407721] pci 0000:00:18.5: Adding to iommu group 6
[    0.407737] pci 0000:00:18.6: Adding to iommu group 6
[    0.407753] pci 0000:00:18.7: Adding to iommu group 6
[    0.407761] pci 0000:01:00.0: Adding to iommu group 1
[    0.407770] pci 0000:02:00.0: Adding to iommu group 1
[    0.407777] pci 0000:c1:00.0: Adding to iommu group 4
[    0.407784] pci 0000:c1:00.1: Adding to iommu group 4
[    0.407792] pci 0000:c1:00.2: Adding to iommu group 4
[    0.407799] pci 0000:c1:00.3: Adding to iommu group 4
[    0.407806] pci 0000:c1:00.4: Adding to iommu group 4
[    0.407814] pci 0000:c1:00.5: Adding to iommu group 4
[    0.407821] pci 0000:c1:00.6: Adding to iommu group 4
[    0.407830] pci 0000:c2:00.0: Adding to iommu group 4
[    0.407838] pci 0000:c2:00.1: Adding to iommu group 4
[    0.407846] pci 0000:c3:00.0: Adding to iommu group 4
[    0.407853] pci 0000:c3:00.3: Adding to iommu group 4
[    0.407861] pci 0000:c3:00.4: Adding to iommu group 4
[    0.407868] pci 0000:c3:00.5: Adding to iommu group 4
[    0.407876] pci 0000:c3:00.6: Adding to iommu group 4
[    0.409475] pci 0000:00:00.2: can't derive routing for PCI INT A
[    0.409481] pci 0000:00:00.2: PCI INT A: not connected
[    0.409607] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
[    0.409612] AMD-Vi: Extended features (0x246577efa2254afa, 0x0): PPR NX GT [5] IA GA PC GA_vAPIC
[    0.409624] AMD-Vi: Interrupt remapping enabled
[    0.409737] AMD-Vi: Virtual APIC enabled
[    0.409790] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.409794] software IO TLB: mapped [mem 0x0000000046c56000-0x000000004ac56000] (64MB)
[    0.409840] LVT offset 0 assigned for vector 0x400
[    0.410041] perf: AMD IBS detected (0x00000bff)
[    0.410055] amd_uncore: 4  amd_df counters detected
[    0.410067] amd_uncore: 6  amd_l3 counters detected
[    0.414157] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
[    0.416258] Initialise system trusted keyrings
[    0.416269] Key type blacklist registered
[    0.416299] workingset: timestamp_bits=46 max_order=24 bucket_order=0
[    0.416313] zbud: loaded
[    0.416696] integrity: Platform Keyring initialized
[    0.416702] integrity: Machine keyring initialized
[    0.422258] NET: Registered PF_ALG protocol family
[    0.422262] xor: automatically using best checksumming function   avx       
[    0.422266] Key type asymmetric registered
[    0.422269] Asymmetric key parser 'x509' registered
[    1.417682] tsc: Refined TSC clocksource calibration: 3293.781 MHz
[    1.417703] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2f7a5979f7a, max_idle_ns: 440795279213 ns
[    1.417790] clocksource: Switched to clocksource tsc
[    1.959424] Freeing initrd memory: 224212K
[    1.964122] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    1.964177] io scheduler mq-deadline registered
[    1.964180] io scheduler kyber registered
[    1.964189] io scheduler bfq registered
[    1.965667] atomic64_test: passed for x86-64 platform with CX8 and with SSE
[    1.966022] amd_gpio AMDI0030:00: iomux not supported
[    1.966026] amd_gpio AMDI0030:00: try to register 183 pins ...
[    1.966028] pinctrl core: registered pin 0 (GPIO_0) on AMDI0030:00
[    1.966031] pinctrl core: registered pin 1 (GPIO_1) on AMDI0030:00
[    1.966033] pinctrl core: registered pin 2 (GPIO_2) on AMDI0030:00
[    1.966035] pinctrl core: registered pin 3 (GPIO_3) on AMDI0030:00
[    1.966037] pinctrl core: registered pin 4 (GPIO_4) on AMDI0030:00
[    1.966039] pinctrl core: registered pin 5 (GPIO_5) on AMDI0030:00
[    1.966040] pinctrl core: registered pin 6 (GPIO_6) on AMDI0030:00
[    1.966042] pinctrl core: registered pin 7 (GPIO_7) on AMDI0030:00
[    1.966044] pinctrl core: registered pin 8 (GPIO_8) on AMDI0030:00
[    1.966045] pinctrl core: registered pin 9 (GPIO_9) on AMDI0030:00
[    1.966047] pinctrl core: registered pin 10 (GPIO_10) on AMDI0030:00
[    1.966049] pinctrl core: registered pin 11 (GPIO_11) on AMDI0030:00
[    1.966051] pinctrl core: registered pin 12 (GPIO_12) on AMDI0030:00
[    1.966053] pinctrl core: registered pin 13 (GPIO_13) on AMDI0030:00
[    1.966055] pinctrl core: registered pin 14 (GPIO_14) on AMDI0030:00
[    1.966057] pinctrl core: registered pin 15 (GPIO_15) on AMDI0030:00
[    1.966058] pinctrl core: registered pin 16 (GPIO_16) on AMDI0030:00
[    1.966060] pinctrl core: registered pin 17 (GPIO_17) on AMDI0030:00
[    1.966062] pinctrl core: registered pin 18 (GPIO_18) on AMDI0030:00
[    1.966064] pinctrl core: registered pin 19 (GPIO_19) on AMDI0030:00
[    1.966065] pinctrl core: registered pin 20 (GPIO_20) on AMDI0030:00
[    1.966067] pinctrl core: registered pin 21 (GPIO_21) on AMDI0030:00
[    1.966069] pinctrl core: registered pin 22 (GPIO_22) on AMDI0030:00
[    1.966071] pinctrl core: registered pin 23 (GPIO_23) on AMDI0030:00
[    1.966072] pinctrl core: registered pin 24 (GPIO_24) on AMDI0030:00
[    1.966074] pinctrl core: registered pin 25 (GPIO_25) on AMDI0030:00
[    1.966076] pinctrl core: registered pin 26 (GPIO_26) on AMDI0030:00
[    1.966078] pinctrl core: registered pin 27 (GPIO_27) on AMDI0030:00
[    1.966079] pinctrl core: registered pin 28 (GPIO_28) on AMDI0030:00
[    1.966081] pinctrl core: registered pin 29 (GPIO_29) on AMDI0030:00
[    1.966083] pinctrl core: registered pin 30 (GPIO_30) on AMDI0030:00
[    1.966085] pinctrl core: registered pin 31 (GPIO_31) on AMDI0030:00
[    1.966086] pinctrl core: registered pin 32 (GPIO_32) on AMDI0030:00
[    1.966090] pinctrl core: registered pin 33 (GPIO_33) on AMDI0030:00
[    1.966091] pinctrl core: registered pin 34 (GPIO_34) on AMDI0030:00
[    1.966093] pinctrl core: registered pin 35 (GPIO_35) on AMDI0030:00
[    1.966095] pinctrl core: registered pin 36 (GPIO_36) on AMDI0030:00
[    1.966097] pinctrl core: registered pin 37 (GPIO_37) on AMDI0030:00
[    1.966098] pinctrl core: registered pin 38 (GPIO_38) on AMDI0030:00
[    1.966100] pinctrl core: registered pin 39 (GPIO_39) on AMDI0030:00
[    1.966102] pinctrl core: registered pin 40 (GPIO_40) on AMDI0030:00
[    1.966104] pinctrl core: registered pin 41 (GPIO_41) on AMDI0030:00
[    1.966105] pinctrl core: registered pin 42 (GPIO_42) on AMDI0030:00
[    1.966107] pinctrl core: registered pin 43 (GPIO_43) on AMDI0030:00
[    1.966109] pinctrl core: registered pin 44 (GPIO_44) on AMDI0030:00
[    1.966111] pinctrl core: registered pin 45 (GPIO_45) on AMDI0030:00
[    1.966112] pinctrl core: registered pin 46 (GPIO_46) on AMDI0030:00
[    1.966114] pinctrl core: registered pin 47 (GPIO_47) on AMDI0030:00
[    1.966116] pinctrl core: registered pin 48 (GPIO_48) on AMDI0030:00
[    1.966118] pinctrl core: registered pin 49 (GPIO_49) on AMDI0030:00
[    1.966119] pinctrl core: registered pin 50 (GPIO_50) on AMDI0030:00
[    1.966121] pinctrl core: registered pin 51 (GPIO_51) on AMDI0030:00
[    1.966123] pinctrl core: registered pin 52 (GPIO_52) on AMDI0030:00
[    1.966125] pinctrl core: registered pin 53 (GPIO_53) on AMDI0030:00
[    1.966126] pinctrl core: registered pin 54 (GPIO_54) on AMDI0030:00
[    1.966128] pinctrl core: registered pin 55 (GPIO_55) on AMDI0030:00
[    1.966130] pinctrl core: registered pin 56 (GPIO_56) on AMDI0030:00
[    1.966132] pinctrl core: registered pin 57 (GPIO_57) on AMDI0030:00
[    1.966133] pinctrl core: registered pin 58 (GPIO_58) on AMDI0030:00
[    1.966135] pinctrl core: registered pin 59 (GPIO_59) on AMDI0030:00
[    1.966137] pinctrl core: registered pin 60 (GPIO_60) on AMDI0030:00
[    1.966139] pinctrl core: registered pin 61 (GPIO_61) on AMDI0030:00
[    1.966140] pinctrl core: registered pin 62 (GPIO_62) on AMDI0030:00
[    1.966143] pinctrl core: registered pin 64 (GPIO_64) on AMDI0030:00
[    1.966144] pinctrl core: registered pin 65 (GPIO_65) on AMDI0030:00
[    1.966146] pinctrl core: registered pin 66 (GPIO_66) on AMDI0030:00
[    1.966148] pinctrl core: registered pin 67 (GPIO_67) on AMDI0030:00
[    1.966150] pinctrl core: registered pin 68 (GPIO_68) on AMDI0030:00
[    1.966152] pinctrl core: registered pin 69 (GPIO_69) on AMDI0030:00
[    1.966153] pinctrl core: registered pin 70 (GPIO_70) on AMDI0030:00
[    1.966155] pinctrl core: registered pin 71 (GPIO_71) on AMDI0030:00
[    1.966157] pinctrl core: registered pin 72 (GPIO_72) on AMDI0030:00
[    1.966159] pinctrl core: registered pin 73 (GPIO_73) on AMDI0030:00
[    1.966160] pinctrl core: registered pin 74 (GPIO_74) on AMDI0030:00
[    1.966162] pinctrl core: registered pin 75 (GPIO_75) on AMDI0030:00
[    1.966164] pinctrl core: registered pin 76 (GPIO_76) on AMDI0030:00
[    1.966166] pinctrl core: registered pin 77 (GPIO_77) on AMDI0030:00
[    1.966167] pinctrl core: registered pin 78 (GPIO_78) on AMDI0030:00
[    1.966169] pinctrl core: registered pin 79 (GPIO_79) on AMDI0030:00
[    1.966171] pinctrl core: registered pin 80 (GPIO_80) on AMDI0030:00
[    1.966173] pinctrl core: registered pin 81 (GPIO_81) on AMDI0030:00
[    1.966174] pinctrl core: registered pin 82 (GPIO_82) on AMDI0030:00
[    1.966176] pinctrl core: registered pin 83 (GPIO_83) on AMDI0030:00
[    1.966178] pinctrl core: registered pin 84 (GPIO_84) on AMDI0030:00
[    1.966180] pinctrl core: registered pin 85 (GPIO_85) on AMDI0030:00
[    1.966181] pinctrl core: registered pin 86 (GPIO_86) on AMDI0030:00
[    1.966183] pinctrl core: registered pin 87 (GPIO_87) on AMDI0030:00
[    1.966185] pinctrl core: registered pin 88 (GPIO_88) on AMDI0030:00
[    1.966187] pinctrl core: registered pin 89 (GPIO_89) on AMDI0030:00
[    1.966188] pinctrl core: registered pin 90 (GPIO_90) on AMDI0030:00
[    1.966190] pinctrl core: registered pin 91 (GPIO_91) on AMDI0030:00
[    1.966192] pinctrl core: registered pin 92 (GPIO_92) on AMDI0030:00
[    1.966194] pinctrl core: registered pin 93 (GPIO_93) on AMDI0030:00
[    1.966195] pinctrl core: registered pin 94 (GPIO_94) on AMDI0030:00
[    1.966197] pinctrl core: registered pin 95 (GPIO_95) on AMDI0030:00
[    1.966199] pinctrl core: registered pin 96 (GPIO_96) on AMDI0030:00
[    1.966201] pinctrl core: registered pin 97 (GPIO_97) on AMDI0030:00
[    1.966204] pinctrl core: registered pin 98 (GPIO_98) on AMDI0030:00
[    1.966206] pinctrl core: registered pin 99 (GPIO_99) on AMDI0030:00
[    1.966207] pinctrl core: registered pin 100 (GPIO_100) on AMDI0030:00
[    1.966209] pinctrl core: registered pin 101 (GPIO_101) on AMDI0030:00
[    1.966211] pinctrl core: registered pin 102 (GPIO_102) on AMDI0030:00
[    1.966213] pinctrl core: registered pin 103 (GPIO_103) on AMDI0030:00
[    1.966215] pinctrl core: registered pin 104 (GPIO_104) on AMDI0030:00
[    1.966216] pinctrl core: registered pin 105 (GPIO_105) on AMDI0030:00
[    1.966218] pinctrl core: registered pin 106 (GPIO_106) on AMDI0030:00
[    1.966220] pinctrl core: registered pin 107 (GPIO_107) on AMDI0030:00
[    1.966222] pinctrl core: registered pin 108 (GPIO_108) on AMDI0030:00
[    1.966223] pinctrl core: registered pin 109 (GPIO_109) on AMDI0030:00
[    1.966225] pinctrl core: registered pin 110 (GPIO_110) on AMDI0030:00
[    1.966227] pinctrl core: registered pin 111 (GPIO_111) on AMDI0030:00
[    1.966229] pinctrl core: registered pin 112 (GPIO_112) on AMDI0030:00
[    1.966230] pinctrl core: registered pin 113 (GPIO_113) on AMDI0030:00
[    1.966232] pinctrl core: registered pin 114 (GPIO_114) on AMDI0030:00
[    1.966234] pinctrl core: registered pin 115 (GPIO_115) on AMDI0030:00
[    1.966236] pinctrl core: registered pin 116 (GPIO_116) on AMDI0030:00
[    1.966237] pinctrl core: registered pin 117 (GPIO_117) on AMDI0030:00
[    1.966239] pinctrl core: registered pin 118 (GPIO_118) on AMDI0030:00
[    1.966241] pinctrl core: registered pin 119 (GPIO_119) on AMDI0030:00
[    1.966243] pinctrl core: registered pin 120 (GPIO_120) on AMDI0030:00
[    1.966244] pinctrl core: registered pin 121 (GPIO_121) on AMDI0030:00
[    1.966246] pinctrl core: registered pin 122 (GPIO_122) on AMDI0030:00
[    1.966248] pinctrl core: registered pin 123 (GPIO_123) on AMDI0030:00
[    1.966250] pinctrl core: registered pin 124 (GPIO_124) on AMDI0030:00
[    1.966252] pinctrl core: registered pin 125 (GPIO_125) on AMDI0030:00
[    1.966253] pinctrl core: registered pin 126 (GPIO_126) on AMDI0030:00
[    1.966255] pinctrl core: registered pin 127 (GPIO_127) on AMDI0030:00
[    1.966257] pinctrl core: registered pin 128 (GPIO_128) on AMDI0030:00
[    1.966259] pinctrl core: registered pin 129 (GPIO_129) on AMDI0030:00
[    1.966261] pinctrl core: registered pin 130 (GPIO_130) on AMDI0030:00
[    1.966262] pinctrl core: registered pin 131 (GPIO_131) on AMDI0030:00
[    1.966264] pinctrl core: registered pin 132 (GPIO_132) on AMDI0030:00
[    1.966266] pinctrl core: registered pin 133 (GPIO_133) on AMDI0030:00
[    1.966268] pinctrl core: registered pin 134 (GPIO_134) on AMDI0030:00
[    1.966270] pinctrl core: registered pin 135 (GPIO_135) on AMDI0030:00
[    1.966271] pinctrl core: registered pin 136 (GPIO_136) on AMDI0030:00
[    1.966273] pinctrl core: registered pin 137 (GPIO_137) on AMDI0030:00
[    1.966275] pinctrl core: registered pin 138 (GPIO_138) on AMDI0030:00
[    1.966277] pinctrl core: registered pin 139 (GPIO_139) on AMDI0030:00
[    1.966278] pinctrl core: registered pin 140 (GPIO_140) on AMDI0030:00
[    1.966280] pinctrl core: registered pin 141 (GPIO_141) on AMDI0030:00
[    1.966282] pinctrl core: registered pin 142 (GPIO_142) on AMDI0030:00
[    1.966284] pinctrl core: registered pin 143 (GPIO_143) on AMDI0030:00
[    1.966285] pinctrl core: registered pin 144 (GPIO_144) on AMDI0030:00
[    1.966287] pinctrl core: registered pin 145 (GPIO_145) on AMDI0030:00
[    1.966289] pinctrl core: registered pin 146 (GPIO_146) on AMDI0030:00
[    1.966291] pinctrl core: registered pin 147 (GPIO_147) on AMDI0030:00
[    1.966292] pinctrl core: registered pin 148 (GPIO_148) on AMDI0030:00
[    1.966294] pinctrl core: registered pin 149 (GPIO_149) on AMDI0030:00
[    1.966296] pinctrl core: registered pin 150 (GPIO_150) on AMDI0030:00
[    1.966298] pinctrl core: registered pin 151 (GPIO_151) on AMDI0030:00
[    1.966299] pinctrl core: registered pin 152 (GPIO_152) on AMDI0030:00
[    1.966301] pinctrl core: registered pin 153 (GPIO_153) on AMDI0030:00
[    1.966303] pinctrl core: registered pin 154 (GPIO_154) on AMDI0030:00
[    1.966305] pinctrl core: registered pin 155 (GPIO_155) on AMDI0030:00
[    1.966307] pinctrl core: registered pin 156 (GPIO_156) on AMDI0030:00
[    1.966308] pinctrl core: registered pin 157 (GPIO_157) on AMDI0030:00
[    1.966310] pinctrl core: registered pin 158 (GPIO_158) on AMDI0030:00
[    1.966312] pinctrl core: registered pin 159 (GPIO_159) on AMDI0030:00
[    1.966314] pinctrl core: registered pin 160 (GPIO_160) on AMDI0030:00
[    1.966315] pinctrl core: registered pin 161 (GPIO_161) on AMDI0030:00
[    1.966318] pinctrl core: registered pin 162 (GPIO_162) on AMDI0030:00
[    1.966320] pinctrl core: registered pin 163 (GPIO_163) on AMDI0030:00
[    1.966322] pinctrl core: registered pin 164 (GPIO_164) on AMDI0030:00
[    1.966323] pinctrl core: registered pin 165 (GPIO_165) on AMDI0030:00
[    1.966325] pinctrl core: registered pin 166 (GPIO_166) on AMDI0030:00
[    1.966327] pinctrl core: registered pin 167 (GPIO_167) on AMDI0030:00
[    1.966329] pinctrl core: registered pin 168 (GPIO_168) on AMDI0030:00
[    1.966331] pinctrl core: registered pin 169 (GPIO_169) on AMDI0030:00
[    1.966332] pinctrl core: registered pin 170 (GPIO_170) on AMDI0030:00
[    1.966334] pinctrl core: registered pin 171 (GPIO_171) on AMDI0030:00
[    1.966336] pinctrl core: registered pin 172 (GPIO_172) on AMDI0030:00
[    1.966338] pinctrl core: registered pin 173 (GPIO_173) on AMDI0030:00
[    1.966339] pinctrl core: registered pin 174 (GPIO_174) on AMDI0030:00
[    1.966341] pinctrl core: registered pin 175 (GPIO_175) on AMDI0030:00
[    1.966343] pinctrl core: registered pin 176 (GPIO_176) on AMDI0030:00
[    1.966345] pinctrl core: registered pin 177 (GPIO_177) on AMDI0030:00
[    1.966346] pinctrl core: registered pin 178 (GPIO_178) on AMDI0030:00
[    1.966348] pinctrl core: registered pin 179 (GPIO_179) on AMDI0030:00
[    1.966350] pinctrl core: registered pin 180 (GPIO_180) on AMDI0030:00
[    1.966352] pinctrl core: registered pin 181 (GPIO_181) on AMDI0030:00
[    1.966353] pinctrl core: registered pin 182 (GPIO_182) on AMDI0030:00
[    1.966355] pinctrl core: registered pin 183 (GPIO_183) on AMDI0030:00
[    1.966358] amd_gpio AMDI0030:00: failed to lookup the default state
[    1.966360] amd_gpio AMDI0030:00: failed to lookup the sleep state
[    1.966874] gpiochip_find_base: found new base at 512
[    1.967320] amd_gpio AMDI0030:00: Invalid config param 0014
[    1.967323] gpio gpiochip0: Persistence not supported for GPIO 0
[    1.967347] amd_gpio AMDI0030:00: Invalid config param 0014
[    1.967349] gpio gpiochip0: Persistence not supported for GPIO 61
[    1.967367] amd_gpio AMDI0030:00: Invalid config param 0014
[    1.967370] gpio gpiochip0: Persistence not supported for GPIO 62
[    1.967388] amd_gpio AMDI0030:00: Invalid config param 0014
[    1.967390] gpio gpiochip0: Persistence not supported for GPIO 58
[    1.967410] amd_gpio AMDI0030:00: Invalid config param 0014
[    1.967412] gpio gpiochip0: Persistence not supported for GPIO 59
[    1.967430] amd_gpio AMDI0030:00: Invalid config param 0014
[    1.967432] gpio gpiochip0: Persistence not supported for GPIO 2
[    1.967449] amd_gpio AMDI0030:00: Invalid config param 0014
[    1.967452] gpio gpiochip0: Persistence not supported for GPIO 6
[    1.967470] amd_gpio AMDI0030:00: Invalid config param 0014
[    1.967472] gpio gpiochip0: Persistence not supported for GPIO 54
[    1.967527] gpio gpiochip0: (AMDI0030:00): added GPIO chardev (254:0)
[    1.967538] gpio gpiochip0: registered GPIOs 512 to 767 on AMDI0030:00
[    1.967540] gpio gpiochip0: (AMDI0030:00): created GPIO range 0->255 ==> AMDI0030:00 PIN 0->255
[    1.967618] amd_gpio AMDI0030:00: amd gpio driver loaded
[    1.967793] pcieport 0000:00:02.2: PME: Signaling with IRQ 38
[    1.967957] pcieport 0000:00:02.4: PME: Signaling with IRQ 39
[    1.968191] pcieport 0000:00:03.1: PME: Signaling with IRQ 40
[    1.968222] pcieport 0000:00:03.1: pciehp: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+
[    1.968761] pcieport 0000:00:04.1: PME: Signaling with IRQ 41
[    1.968792] pcieport 0000:00:04.1: pciehp: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+
[    1.969222] pcieport 0000:00:08.1: PME: Signaling with IRQ 42
[    1.969457] pcieport 0000:00:08.2: PME: Signaling with IRQ 43
[    1.969615] pcieport 0000:00:08.3: PME: Signaling with IRQ 44
[    1.969700] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    1.970379] ACPI: AC: AC Adapter [ACAD] (on-line)
[    1.970427] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/PNP0C09:00/PNP0C0D:00/input/input0
[    1.970447] ACPI: button: Lid Switch [LID0]
[    1.970473] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[    1.970490] ACPI: button: Power Button [PWRB]
[    1.970557] Estimated ratio of average max frequency by base frequency (times 1024): 1548
[    1.970574] Monitor-Mwait will be used to enter C-1 state
[    1.970578] ACPI: \_SB_.PLTF.C000: Found 3 idle states
[    1.970691] ACPI: \_SB_.PLTF.C001: Found 3 idle states
[    1.970788] ACPI: \_SB_.PLTF.C002: Found 3 idle states
[    1.970877] ACPI: \_SB_.PLTF.C003: Found 3 idle states
[    1.970973] ACPI: \_SB_.PLTF.C004: Found 3 idle states
[    1.971069] ACPI: \_SB_.PLTF.C005: Found 3 idle states
[    1.971165] ACPI: \_SB_.PLTF.C006: Found 3 idle states
[    1.971260] ACPI: \_SB_.PLTF.C007: Found 3 idle states
[    1.971356] ACPI: \_SB_.PLTF.C008: Found 3 idle states
[    1.971452] ACPI: \_SB_.PLTF.C009: Found 3 idle states
[    1.971549] ACPI: \_SB_.PLTF.C00A: Found 3 idle states
[    1.971644] ACPI: \_SB_.PLTF.C00B: Found 3 idle states
[    1.971754] ACPI: \_SB_.PLTF.C00C: Found 3 idle states
[    1.971850] ACPI: \_SB_.PLTF.C00D: Found 3 idle states
[    1.971946] ACPI: \_SB_.PLTF.C00E: Found 3 idle states
[    1.972044] ACPI: \_SB_.PLTF.C00F: Found 3 idle states
[    1.972393] thermal LNXTHERM:00: registered as thermal_zone0
[    1.972397] ACPI: thermal: Thermal Zone [TZ00] (35 C)
[    1.972547] thermal LNXTHERM:01: registered as thermal_zone1
[    1.972550] ACPI: thermal: Thermal Zone [TZ01] (37 C)
[    1.972701] thermal LNXTHERM:02: registered as thermal_zone2
[    1.972705] ACPI: thermal: Thermal Zone [TZ02] (35 C)
[    1.972850] thermal LNXTHERM:03: registered as thermal_zone3
[    1.972853] ACPI: thermal: Thermal Zone [TZ03] (73 C)
[    1.973009] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    1.974231] ACPI: battery: Slot [BAT1] (battery present)
[    1.975109] Non-volatile memory driver v1.3
[    1.975116] Linux agpgart interface v0.103
[    1.975649] ACPI: bus type drm_connector registered
[    1.975903] [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
[    1.979912] Console: switching to colour frame buffer device 282x94
[    1.983679] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[    1.987118] mdio_bus fixed-0: using lookup tables for GPIO lookup
[    1.987122] mdio_bus fixed-0: No GPIO consumer reset found
[    1.987559] xhci_hcd 0000:c1:00.3: xHCI Host Controller
[    1.987668] xhci_hcd 0000:c1:00.3: new USB bus registered, assigned bus number 1
[    1.988148] xhci_hcd 0000:c1:00.3: hcc params 0x0128ffc5 hci version 0x120 quirks 0x0000000200000410
[    1.988590] xhci_hcd 0000:c1:00.3: xHCI Host Controller
[    1.988644] xhci_hcd 0000:c1:00.3: new USB bus registered, assigned bus number 2
[    1.988714] xhci_hcd 0000:c1:00.3: Host supports USB 3.1 Enhanced SuperSpeed
[    1.988804] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    1.988829] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.988850] usb usb1: Product: xHCI Host Controller
[    1.988869] usb usb1: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    1.988891] usb usb1: SerialNumber: 0000:c1:00.3
[    1.989117] hub 1-0:1.0: USB hub found
[    1.989157] hub 1-0:1.0: 5 ports detected
[    1.993414] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.993504] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    1.993517] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.993535] usb usb2: Product: xHCI Host Controller
[    1.993546] usb usb2: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    1.993561] usb usb2: SerialNumber: 0000:c1:00.3
[    1.993780] hub 2-0:1.0: USB hub found
[    1.993830] hub 2-0:1.0: 2 ports detected
[    1.995639] xhci_hcd 0000:c1:00.4: xHCI Host Controller
[    1.995728] xhci_hcd 0000:c1:00.4: new USB bus registered, assigned bus number 3
[    1.996165] xhci_hcd 0000:c1:00.4: hcc params 0x0110ffc5 hci version 0x120 quirks 0x0000000200000410
[    1.996505] xhci_hcd 0000:c1:00.4: xHCI Host Controller
[    1.996579] xhci_hcd 0000:c1:00.4: new USB bus registered, assigned bus number 4
[    1.996649] xhci_hcd 0000:c1:00.4: Host supports USB 3.1 Enhanced SuperSpeed
[    1.996726] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    1.996740] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.996759] usb usb3: Product: xHCI Host Controller
[    1.996772] usb usb3: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    1.996787] usb usb3: SerialNumber: 0000:c1:00.4
[    1.997009] hub 3-0:1.0: USB hub found
[    1.997061] hub 3-0:1.0: 1 port detected
[    1.997979] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.998065] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    1.998078] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.998097] usb usb4: Product: xHCI Host Controller
[    1.998111] usb usb4: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    1.998126] usb usb4: SerialNumber: 0000:c1:00.4
[    1.998319] hub 4-0:1.0: USB hub found
[    1.998381] hub 4-0:1.0: 1 port detected
[    1.999483] xhci_hcd 0000:c3:00.3: xHCI Host Controller
[    1.999572] xhci_hcd 0000:c3:00.3: new USB bus registered, assigned bus number 5
[    2.000028] xhci_hcd 0000:c3:00.3: hcc params 0x0110ffc5 hci version 0x120 quirks 0x0000000200000410
[    2.000553] xhci_hcd 0000:c3:00.3: xHCI Host Controller
[    2.000626] xhci_hcd 0000:c3:00.3: new USB bus registered, assigned bus number 6
[    2.000696] xhci_hcd 0000:c3:00.3: Host supports USB 3.1 Enhanced SuperSpeed
[    2.000767] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    2.000781] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.000799] usb usb5: Product: xHCI Host Controller
[    2.000811] usb usb5: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    2.000827] usb usb5: SerialNumber: 0000:c3:00.3
[    2.001042] hub 5-0:1.0: USB hub found
[    2.001095] hub 5-0:1.0: 1 port detected
[    2.002053] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.002146] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    2.002159] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.002177] usb usb6: Product: xHCI Host Controller
[    2.002190] usb usb6: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    2.002206] usb usb6: SerialNumber: 0000:c3:00.3
[    2.002424] hub 6-0:1.0: USB hub found
[    2.002448] hub 6-0:1.0: 1 port detected
[    2.003720] xhci_hcd 0000:c3:00.4: xHCI Host Controller
[    2.003810] xhci_hcd 0000:c3:00.4: new USB bus registered, assigned bus number 7
[    2.004215] xhci_hcd 0000:c3:00.4: hcc params 0x0110ffc5 hci version 0x120 quirks 0x0000000200000410
[    2.004732] xhci_hcd 0000:c3:00.4: xHCI Host Controller
[    2.004819] xhci_hcd 0000:c3:00.4: new USB bus registered, assigned bus number 8
[    2.005717] xhci_hcd 0000:c3:00.4: Host supports USB 3.1 Enhanced SuperSpeed
[    2.007134] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    2.007802] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.008442] usb usb7: Product: xHCI Host Controller
[    2.009012] usb usb7: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    2.009528] usb usb7: SerialNumber: 0000:c3:00.4
[    2.010291] hub 7-0:1.0: USB hub found
[    2.010983] hub 7-0:1.0: 1 port detected
[    2.012858] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.013616] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    2.014717] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.015238] usb usb8: Product: xHCI Host Controller
[    2.015747] usb usb8: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    2.016532] usb usb8: SerialNumber: 0000:c3:00.4
[    2.017653] hub 8-0:1.0: USB hub found
[    2.018256] hub 8-0:1.0: 1 port detected
[    2.021154] usbcore: registered new interface driver usbserial_generic
[    2.022537] usbserial: USB Serial support registered for generic
[    2.023102] i8042: PNP: PS/2 Controller [PNP0303:KBC0] at 0x60,0x64 irq 1
[    2.023633] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[    2.027561] i8042: Warning: Keylock active
[    2.030874] serio: i8042 KBD port at 0x60,0x64 irq 1
[    2.032299] mousedev: PS/2 mouse device common for all mice
[    2.033128] rtc_cmos 00:01: RTC can wake from S4
[    2.034020] rtc_cmos 00:01: registered as rtc0
[    2.034620] rtc_cmos 00:01: setting system clock to 2023-12-20T16:27:18 UTC (1703089638)
[    2.035279] rtc_cmos 00:01: using ACPI '\_SB.PCI0.LPC0.RTC' for 'wp' GPIO lookup
[    2.035296] acpi PNP0B00:00: GPIO: looking up wp-gpios
[    2.035300] acpi PNP0B00:00: GPIO: looking up wp-gpio
[    2.035301] rtc_cmos 00:01: using lookup tables for GPIO lookup
[    2.035304] rtc_cmos 00:01: No GPIO consumer wp found
[    2.035348] rtc_cmos 00:01: alarms up to one month, 114 bytes nvram, hpet irqs
[    2.036196] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[    2.037088] device-mapper: uevent: version 1.0.3
[    2.038099] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
[    2.042145] hid: raw HID events driver (C) Jiri Kosina
[    2.042353] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
[    2.043432] usbcore: registered new interface driver usbhid
[    2.044607] usbhid: USB HID core driver
[    2.045472] drop_monitor: Initializing network drop monitor service
[    2.055516] Initializing XFRM netlink socket
[    2.056581] NET: Registered PF_INET6 protocol family
[    2.062510] Segment Routing with IPv6
[    2.063663] RPL Segment Routing with IPv6
[    2.064174] In-situ OAM (IOAM) with IPv6
[    2.064598] mip6: Mobile IPv6
[    2.065016] NET: Registered PF_PACKET protocol family
[    2.070375] microcode: CPU2: patch_level=0x0a704103
[    2.070377] microcode: CPU6: patch_level=0x0a704103
[    2.070378] microcode: CPU7: patch_level=0x0a704103
[    2.070388] microcode: CPU3: patch_level=0x0a704103
[    2.070389] microcode: CPU12: patch_level=0x0a704103
[    2.070388] microcode: CPU13: patch_level=0x0a704103
[    2.070389] microcode: CPU14: patch_level=0x0a704103
[    2.070391] microcode: CPU15: patch_level=0x0a704103
[    2.070392] microcode: CPU4: patch_level=0x0a704103
[    2.070393] microcode: CPU5: patch_level=0x0a704103
[    2.070399] microcode: CPU9: patch_level=0x0a704103
[    2.070399] microcode: CPU8: patch_level=0x0a704103
[    2.070399] microcode: CPU0: patch_level=0x0a704103
[    2.070411] microcode: CPU11: patch_level=0x0a704103
[    2.070411] microcode: CPU10: patch_level=0x0a704103
[    2.070498] microcode: CPU1: patch_level=0x0a704103
[    2.077968] microcode: Microcode Update Driver: v2.2.
[    2.083396] resctrl: L3 allocation detected
[    2.084803] resctrl: MB allocation detected
[    2.085185] resctrl: SMBA allocation detected
[    2.085573] resctrl: L3 monitoring detected
[    2.085970] IPI shorthand broadcast: enabled
[    2.086358] AVX2 version of gcm_enc/dec engaged.
[    2.087909] AES CTR mode by8 optimization enabled
[    2.091234] sched_clock: Marking stable (2089010819, 1655784)->(2111863983, -21197380)
[    2.092146] registered taskstats version 1
[    2.094724] Loading compiled-in X.509 certificates
[    2.102125] Loaded X.509 cert 'Build time autogenerated kernel key: 3f6a57fb3f3898b7be9c82c1820e4f9123e8e07f'
[    2.106007] page_owner is disabled
[    2.107273] Key type .fscrypt registered
[    2.108137] Key type fscrypt-provisioning registered
[    2.109681] Btrfs loaded, zoned=yes, fsverity=yes
[    2.110540] Key type big_key registered
[    2.116740] Key type encrypted registered
[    2.120642] integrity: Loading X.509 certificate: UEFI:db
[    2.121565] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[    2.122013] integrity: Loading X.509 certificate: UEFI:db
[    2.122426] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[    2.122836] integrity: Loading X.509 certificate: UEFI:db
[    2.123221] integrity: Loaded X.509 cert 'frame.work-LaptopAMDDB: 02'
[    2.134875] ima: No TPM chip found, activating TPM-bypass!
[    2.135360] Loading compiled-in module X.509 certificates
[    2.136038] Loaded X.509 cert 'Build time autogenerated kernel key: 3f6a57fb3f3898b7be9c82c1820e4f9123e8e07f'
[    2.136412] ima: Allocated hash algorithm: sha256
[    2.136886] ima: No architecture policies found
[    2.138028] evm: Initialising EVM extended attributes:
[    2.138566] evm: security.selinux
[    2.139077] evm: security.SMACK64 (disabled)
[    2.139586] evm: security.SMACK64EXEC (disabled)
[    2.140180] evm: security.SMACK64TRANSMUTE (disabled)
[    2.140558] evm: security.SMACK64MMAP (disabled)
[    2.140953] evm: security.apparmor (disabled)
[    2.141317] evm: security.ima
[    2.141740] evm: security.capability
[    2.142209] evm: HMAC attrs: 0x1
[    2.193959] alg: No test for 842 (842-scomp)
[    2.195731] alg: No test for 842 (842-generic)
[    2.235745] usb 1-1: new full-speed USB device number 2 using xhci_hcd
[    2.251684] usb 7-1: new high-speed USB device number 2 using xhci_hcd
[    2.265912] PM:   Magic number: 3:165:490
[    2.378263] RAS: Correctable Errors collector initialized.
[    2.380829] clk: Disabling unused clocks
[    2.382850] Freeing unused decrypted memory: 2028K
[    2.384260] Freeing unused kernel image (initmem) memory: 3944K
[    2.385701] Write protecting the kernel read-only data: 34816k
[    2.385706] usb 7-1: New USB device found, idVendor=17ef, idProduct=a392, bcdDevice= d.24
[    2.386637] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.387206] usb 7-1: Product: USB2.0 Hub
[    2.387746] usb 7-1: Manufacturer: VIA Labs, Inc.
[    2.388710] Freeing unused kernel image (rodata/data gap) memory: 1928K
[    2.392728] usb 1-1: New USB device found, idVendor=046d, idProduct=c548, bcdDevice= 5.01
[    2.393911] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.394548] usb 1-1: Product: USB Receiver
[    2.395012] usb 1-1: Manufacturer: Logitech
[    2.413072] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-1/1-1:1.0/0003:046D:C548.0001/input/input3
[    2.419939] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    2.420635] Run /init as init process
[    2.421099]   with arguments:
[    2.421101]     /init
[    2.421102]   with environment:
[    2.421103]     HOME=/
[    2.421103]     TERM=linux
[    2.421104]     BOOT_IMAGE=/boot/vmlinuz-6.6.7xen-irq-dbg-1+
[    2.424195] hub 7-1:1.0: USB hub found
[    2.425469] hub 7-1:1.0: 4 ports detected
[    2.443406] systemd[1]: systemd 254.7-1.fc39 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[    2.445076] systemd[1]: Detected architecture x86-64.
[    2.446016] systemd[1]: Running in initrd.
[    2.450014] systemd[1]: No hostname configured, using default hostname.
[    2.450856] systemd[1]: Hostname set to <fedora>.
[    2.466136] hid-generic 0003:046D:C548.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:c1:00.3-1/input0
[    2.472104] input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-1/1-1:1.1/0003:046D:C548.0002/input/input4
[    2.476414] input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-1/1-1:1.1/0003:046D:C548.0002/input/input5
[    2.518567] usb 8-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd
[    2.528943] input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-1/1-1:1.1/0003:046D:C548.0002/input/input6
[    2.532047] hid-generic 0003:046D:C548.0002: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:c1:00.3-1/input1
[    2.537805] hid-generic 0003:046D:C548.0003: hiddev96,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:c1:00.3-1/input2
[    2.614231] usb 8-1: New USB device found, idVendor=17ef, idProduct=a391, bcdDevice= d.24
[    2.615667] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.616455] usb 8-1: Product: USB3.1 Hub
[    2.616880] usb 8-1: Manufacturer: VIA Labs, Inc.
[    2.638695] systemd[1]: bpf-lsm: LSM BPF program attached
[    2.648233] hub 8-1:1.0: USB hub found
[    2.650973] hub 8-1:1.0: 4 ports detected
[    2.654710] usb 1-4: new full-speed USB device number 3 using xhci_hcd
[    2.689401] systemd[1]: Queued start job for default target initrd.target.
[    2.703745] systemd[1]: Reached target initrd-usr-fs.target - Initrd /usr File System.
[    2.704785] systemd[1]: Reached target slices.target - Slice Units.
[    2.705690] systemd[1]: Reached target swap.target - Swaps.
[    2.706590] systemd[1]: Reached target timers.target - Timer Units.
[    2.709634] systemd[1]: Listening on dbus.socket - D-Bus System Message Bus Socket.
[    2.712550] systemd[1]: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
[    2.714918] systemd[1]: Listening on systemd-journald.socket - Journal Socket.
[    2.717067] systemd[1]: Listening on systemd-udevd-control.socket - udev Control Socket.
[    2.718832] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
[    2.720497] systemd[1]: Reached target sockets.target - Socket Units.
[    2.724529] systemd[1]: Starting kmod-static-nodes.service - Create List of Static Device Nodes...
[    2.726942] systemd[1]: memstrack.service - Memstrack Anylazing Service was skipped because no trigger condition checks were met.
[    2.730488] systemd[1]: Starting systemd-journald.service - Journal Service...
[    2.734723] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...
[    2.738030] systemd[1]: Starting systemd-sysusers.service - Create System Users...
[    2.740579] systemd-journald[343]: Collecting audit messages is disabled.
[    2.744804] systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup...
[    2.753860] fuse: init (API version 7.39)
[    2.757479] i2c_dev: i2c /dev entries driver
[    2.768963] systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes.
[    2.797960] systemd[1]: Finished systemd-sysusers.service - Create System Users.
[    2.800458] systemd[1]: Started systemd-journald.service - Journal Service.
[    2.817772] usb 1-4: New USB device found, idVendor=27c6, idProduct=609c, bcdDevice= 1.00
[    2.818878] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.819417] usb 1-4: Product: Goodix USB2.0 MISC
[    2.819931] usb 1-4: Manufacturer: Goodix Technology Co., Ltd.
[    2.820427] usb 1-4: SerialNumber: UIDD5F04A7B_XXXX_MOC_B0
[    2.946670] usb 1-5: new high-speed USB device number 4 using xhci_hcd
[    2.999547] Rounding down aligned max_sectors from 4294967295 to 4294967288
[    3.000278] db_root: cannot open: /etc/target
[    3.080229] usb 1-5: New USB device found, idVendor=0e8d, idProduct=e616, bcdDevice= 1.00
[    3.081424] usb 1-5: New USB device strings: Mfr=5, Product=6, SerialNumber=7
[    3.082007] usb 1-5: Product: Wireless_Device
[    3.082557] usb 1-5: Manufacturer: MediaTek Inc.
[    3.083103] usb 1-5: SerialNumber: 000000000
[    3.172180] acpi FRMW0004:00: GPIO: looking up 0 in _CRS
[    3.172243] acpi FRMW0005:00: GPIO: looking up 0 in _CRS
[    3.172346] amd_gpio AMDI0030:00: Invalid config param 0014
[    3.172351] gpio gpiochip0: Persistence not supported for GPIO 84
[    3.172486] amd_gpio AMDI0030:00: Invalid config param 0014
[    3.172490] gpio gpiochip0: Persistence not supported for GPIO 5
[    3.172492] acpi PIXA3854:00: GPIO: looking up 0 in _CRS
[    3.172570] amd_gpio AMDI0030:00: Invalid config param 0014
[    3.172574] gpio gpiochip0: Persistence not supported for GPIO 8
[    3.173068] ACPI: video: Video Device [VGA] (multi-head: yes  rom: no  post: no)
[    3.174942] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:16/LNXVIDEO:00/input/input7
[    3.176549] GPIO 8 is active: 0x18141b00
[    3.177698] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[    3.179285] sp5100-tco sp5100-tco: Using 0xfeb00000 for watchdog MMIO address
[    3.180672] sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
[    3.183629] GPIO 8 is active: 0x18141b00
[    3.184721] ccp 0000:c1:00.2: enabling device (0000 -> 0002)
[    3.190711] GPIO 8 is active: 0x18141b00
[    3.196188] ccp 0000:c1:00.2: tee enabled
[    3.197793] GPIO 8 is active: 0x18141b00
[    3.197864] ccp 0000:c1:00.2: psp enabled
[    3.200669] usb 7-1.3: new high-speed USB device number 3 using xhci_hcd
[    3.236145] GPIO 8 is active: 0x18141b00
[    3.257917] GPIO 84 is active: 0x10141b00
[    3.259431] GPIO 5 is active: 0x10141b00
[    3.259455] GPIO 84 is active: 0x10140b00
[    3.318687] input: PIXA3854:00 093A:0274 Mouse as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0004/input/input8
[    3.320059] input: PIXA3854:00 093A:0274 Touchpad as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0004/input/input9
[    3.320858] hid-generic 0018:093A:0274.0004: input,hidraw3: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00
[    3.342265] input: FRMW0004:00 32AC:0006 Wireless Radio Control as /devices/platform/AMDI0010:00/i2c-0/i2c-FRMW0004:00/0018:32AC:0006.0005/input/input10
[    3.343003] usb 7-1.3: New USB device found, idVendor=17ef, idProduct=a394, bcdDevice= d.23
[    3.343015] usb 7-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.343025] usb 7-1.3: Product: USB2.0 Hub
[    3.343032] usb 7-1.3: Manufacturer: VIA Labs, Inc.
[    3.343759] input: FRMW0004:00 32AC:0006 Consumer Control as /devices/platform/AMDI0010:00/i2c-0/i2c-FRMW0004:00/0018:32AC:0006.0005/input/input11
[    3.349359] GPIO 8 is active: 0x18141b00
[    3.360497] GPIO 8 is active: 0x18141b00
[    3.365966] hid-generic 0018:32AC:0006.0005: input,hidraw3: I2C HID v1.00 Device [FRMW0004:00 32AC:0006] on i2c-FRMW0004:00
[    3.367290] input: PIXA3854:00 093A:0274 Mouse as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0004/input/input12
[    3.367507] GPIO 8 is active: 0x18141b00
[    3.367583] input: PIXA3854:00 093A:0274 Touchpad as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0004/input/input13
[    3.367749] hid-multitouch 0018:093A:0274.0004: input,hidraw4: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00
[    3.374616] GPIO 8 is active: 0x18141b00
[    3.381670] GPIO 8 is active: 0x18141b00
[    3.383437] hub 7-1.3:1.0: USB hub found
[    3.383995] hub 7-1.3:1.0: 4 ports detected
[    3.388622] GPIO 8 is active: 0x18141b00
[    3.395711] GPIO 8 is active: 0x18141b00
[    3.402801] GPIO 8 is active: 0x18141b00
[    3.409883] GPIO 8 is active: 0x18141b00
[    3.415285] usb 8-1.1: new SuperSpeed USB device number 3 using xhci_hcd
[    3.416948] GPIO 8 is active: 0x18141b00
[    3.423994] GPIO 8 is active: 0x18141b00
[    3.428022] usb 8-1.1: New USB device found, idVendor=17ef, idProduct=a387, bcdDevice=31.03
[    3.428064] usb 8-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[    3.428095] usb 8-1.1: Product: USB-C Dock Ethernet
[    3.428118] usb 8-1.1: Manufacturer: Realtek
[    3.428139] usb 8-1.1: SerialNumber: 301000001
[    3.428792] hid-generic 0018:32AC:001B.0006: hidraw5: I2C HID v1.00 Device [FRMW0005:00 32AC:001B] on i2c-FRMW0005:00
[    3.430945] GPIO 8 is active: 0x18141b00
[    3.431136] hid-sensor-hub 0018:32AC:001B.0006: hidraw5: I2C HID v1.00 Device [FRMW0005:00 32AC:001B] on i2c-FRMW0005:00
[    3.438029] GPIO 8 is active: 0x18141b00
[    3.444705] nvme 0000:02:00.0: platform quirk: setting simple suspend
[    3.444879] nvme nvme0: pci function 0000:02:00.0
[    3.445186] GPIO 8 is active: 0x18141b00
[    3.452196] GPIO 8 is active: 0x18141b00
[    3.459279] GPIO 8 is active: 0x18141b00
[    3.466321] GPIO 8 is active: 0x18141b00
[    3.473292] GPIO 8 is active: 0x18141b00
[    3.480405] GPIO 8 is active: 0x18141b00
[    3.484129] nvme nvme0: 16/0/0 default/read/poll queues
[    3.487412] GPIO 8 is active: 0x18141b00
[    3.488423]  nvme0n1: p1 p2 p3 p4
[    3.494381] GPIO 8 is active: 0x18141b00
[    3.496243] BTRFS: device fsid 71b1dc59-ea00-484c-b5e4-ee77ede771db devid 1 transid 6117 /dev/nvme0n1p1 scanned by (udev-worker) (519)
[    3.501465] GPIO 8 is active: 0x18141b00
[    3.508550] GPIO 8 is active: 0x18141b00
[    3.515615] GPIO 8 is active: 0x18141b00
[    3.522591] GPIO 8 is active: 0x18141b00
[    3.529672] GPIO 8 is active: 0x18141b00
[    3.536705] GPIO 8 is active: 0x18141b00
[    3.543678] GPIO 8 is active: 0x18141b00
[    3.550750] GPIO 8 is active: 0x18141b00
[    3.554461] usb 8-1.3: new SuperSpeed Plus Gen 2x1 USB device number 4 using xhci_hcd
[    3.557839] GPIO 8 is active: 0x18141b00
[    3.587031] usb 8-1.3: New USB device found, idVendor=17ef, idProduct=a393, bcdDevice= d.23
[    3.587066] usb 8-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.587089] usb 8-1.3: Product: USB3.1 Hub
[    3.587103] usb 8-1.3: Manufacturer: VIA Labs, Inc.
[    3.607304] hub 8-1.3:1.0: USB hub found
[    3.607443] hub 8-1.3:1.0: 4 ports detected
[    3.616638] usbcore: registered new device driver r8152-cfgselector
[    3.783377] r8152-cfgselector 8-1.1: reset SuperSpeed USB device number 3 using xhci_hcd
[    3.804282] r8152 8-1.1:1.0: load rtl8153b-2 v2 04/27/23 successfully
[    3.835690] r8152 8-1.1:1.0 eth0: v1.12.13
[    3.835743] usbcore: registered new interface driver r8152
[    3.843885] r8152 8-1.1:1.0 enp195s0f4u1u1: renamed from eth0
[    4.168695] usb 7-1.3.3: new high-speed USB device number 4 using xhci_hcd
[    4.279325] GPIO 5 is active: 0x10141b00
[    4.326722] usb 7-1.3.3: New USB device found, idVendor=17ef, idProduct=a395, bcdDevice=60.70
[    4.326752] usb 7-1.3.3: New USB device strings: Mfr=10, Product=11, SerialNumber=0
[    4.326775] usb 7-1.3.3: Product: USB2.0 Hub
[    4.326790] usb 7-1.3.3: Manufacturer: Lenovo
[    4.375550] hub 7-1.3.3:1.0: USB hub found
[    4.376109] hub 7-1.3.3:1.0: 4 ports detected
[    4.651698] usb 7-1.3.3.1: new full-speed USB device number 5 using xhci_hcd
[    4.750123] usb 7-1.3.3.1: New USB device found, idVendor=04b4, idProduct=521a, bcdDevice= 0.00
[    4.750152] usb 7-1.3.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.750175] usb 7-1.3.3.1: Product: USB-I2C Bridge
[    4.750191] usb 7-1.3.3.1: Manufacturer: Cypress Semiconductor
[    4.858698] usb 7-1.3.3.2: new full-speed USB device number 6 using xhci_hcd
[    4.881222] [drm] amdgpu kernel modesetting enabled.
[    4.891588] amdgpu: Virtual CRAT table created for CPU
[    4.891609] amdgpu: Topology: Add CPU node
[    4.891699] amdgpu 0000:c1:00.0: enabling device (0006 -> 0007)
[    4.891753] [drm] initializing kernel modesetting (IP DISCOVERY 0x1002:0x15BF 0xF111:0x0006 0xC4).
[    4.891858] [drm] register mmio base: 0x90500000
[    4.891866] [drm] register mmio size: 524288
[    4.894712] [drm] add ip block number 0 <soc21_common>
[    4.894723] [drm] add ip block number 1 <gmc_v11_0>
[    4.894732] [drm] add ip block number 2 <ih_v6_0>
[    4.894742] [drm] add ip block number 3 <psp>
[    4.894749] [drm] add ip block number 4 <smu>
[    4.894756] [drm] add ip block number 5 <dm>
[    4.894762] [drm] add ip block number 6 <gfx_v11_0>
[    4.894770] [drm] add ip block number 7 <sdma_v6_0>
[    4.894778] [drm] add ip block number 8 <vcn_v4_0>
[    4.894785] [drm] add ip block number 9 <jpeg_v4_0>
[    4.894793] [drm] add ip block number 10 <mes_v11_0>
[    4.894818] amdgpu 0000:c1:00.0: amdgpu: Fetched VBIOS from VFCT
[    4.894828] amdgpu: ATOM BIOS: 113-PHXGENERIC-001
[    4.912792] [drm] VCN(0) encode/decode are enabled in VM mode
[    4.922815] amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_early_init [amdgpu]] JPEG decode is enabled in VM mode
[    4.930892] Console: switching to colour dummy device 80x25
[    4.943108] amdgpu 0000:c1:00.0: vgaarb: deactivate vga console
[    4.943113] amdgpu 0000:c1:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
[    4.943157] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
[    4.943181] amdgpu 0000:c1:00.0: amdgpu: VRAM: 512M 0x0000008000000000 - 0x000000801FFFFFFF (512M used)
[    4.943186] amdgpu 0000:c1:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[    4.943190] amdgpu 0000:c1:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF
[    4.943205] [drm] Detected VRAM RAM=512M, BAR=512M
[    4.943207] [drm] RAM width 128bits DDR5
[    4.943360] [drm] amdgpu: 512M of VRAM memory ready
[    4.943364] [drm] amdgpu: 31741M of GTT memory ready.
[    4.943384] [drm] GART: num cpu pages 131072, num gpu pages 131072
[    4.943906] [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
[    4.944172] [drm] Loading DMUB firmware via PSP: version=0x08002A81
[    4.946396] [drm] Found VCN firmware Version ENC: 1.10 DEC: 5 VEP: 0 Revision: 0
[    4.946405] amdgpu 0000:c1:00.0: amdgpu: Will use PSP to load VCN firmware
[    4.970498] [drm] reserve 0x4000000 from 0x8018000000 for PSP TMR
[    4.997117] usb 7-1.3.3.2: New USB device found, idVendor=17ef, idProduct=30d1, bcdDevice= 0.42
[    4.997127] usb 7-1.3.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.997135] usb 7-1.3.3.2: Product: ThinkPad USB-C Dock Gen2 USB Audio
[    4.997142] usb 7-1.3.3.2: Manufacturer: Lenovo
[    4.997147] usb 7-1.3.3.2: SerialNumber: 000000000000
[    5.089503] hid-generic 0003:17EF:30D1.0007: hiddev97,hidraw6: USB HID v1.11 Device [Lenovo ThinkPad USB-C Dock Gen2 USB Audio] on usb-0000:c3:00.4-1.3.3.2/input3
[    5.288903] GPIO 5 is active: 0x10141b00
[    5.486392] amdgpu 0000:c1:00.0: amdgpu: RAS: optional ras ta ucode is not available
[    5.493872] amdgpu 0000:c1:00.0: amdgpu: RAP: optional rap ta ucode is not available
[    5.493882] amdgpu 0000:c1:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[    5.527507] amdgpu 0000:c1:00.0: amdgpu: SMU is initialized successfully!
[    5.527934] [drm] Display Core v3.2.247 initialized on DCN 3.1.4
[    5.527939] [drm] DP-HDMI FRL PCON supported
[    5.529878] [drm] DMUB hardware initialized: version=0x08002A81
[    5.612959] [drm] PSR support 1, DC PSR ver 0, sink PSR ver 3 DPCD caps 0x7b su_y_granularity 4
[    5.678582] [drm] DM_MST: Differing MST start on aconnector: 00000000b23238de [id: 112]
[    5.679879] [drm] kiq ring mec 3 pipe 1 q 0
[    5.682385] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[    5.682421] amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
[    5.694547] amdgpu: HMM registered 512MB device memory
[    5.695310] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[    5.695321] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[    5.695412] amdgpu: Virtual CRAT table created for GPU
[    5.695549] amdgpu: Topology: Add dGPU node [0x15bf:0x1002]
[    5.695552] kfd kfd: amdgpu: added device 1002:15bf
[    5.695563] amdgpu 0000:c1:00.0: amdgpu: SE 1, SH per SE 2, CU per SH 6, active_cu_number 12
[    5.695706] amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[    5.695711] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[    5.695714] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[    5.695718] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[    5.695721] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[    5.695725] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[    5.695728] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[    5.695731] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[    5.695735] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[    5.695738] amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[    5.695742] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[    5.695745] amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
[    5.695749] amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
[    5.700112] [drm] ring gfx_32768.1.1 was added
[    5.700668] [drm] ring compute_32768.2.2 was added
[    5.701178] [drm] ring sdma_32768.3.3 was added
[    5.701224] [drm] ring gfx_32768.1.1 ib test pass
[    5.701265] [drm] ring compute_32768.2.2 ib test pass
[    5.701324] [drm] ring sdma_32768.3.3 ib test pass
[    5.703686] [drm] Initialized amdgpu 3.54.0 20150101 for 0000:c1:00.0 on minor 1
[    5.708515] fbcon: amdgpudrmfb (fb0) is primary device
[    5.708638] [drm] DSC precompute is not needed.
[    6.296855] GPIO 5 is active: 0x10141b00
[    6.522055] Console: switching to colour frame buffer device 282x94
[    6.541147] amdgpu 0000:c1:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[    6.753127] [drm] Downstream port present 1, type 2
[    7.285019] BTRFS info (device nvme0n1p1): first mount of filesystem 71b1dc59-ea00-484c-b5e4-ee77ede771db
[    7.285049] BTRFS info (device nvme0n1p1): using crc32c (crc32c-intel) checksum algorithm
[    7.285062] BTRFS info (device nvme0n1p1): using free space tree
[    7.298451] BTRFS info (device nvme0n1p1): enabling ssd optimizations
[    7.298471] BTRFS info (device nvme0n1p1): auto enabling async discard
[    7.303902] GPIO 5 is active: 0x10141b00
[    7.746992] systemd-journald[343]: Received SIGTERM from PID 1 (systemd).
[    7.833277] audit: type=1404 audit(1703089644.298:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
[    7.869414] SELinux:  policy capability network_peer_controls=1
[    7.870054] SELinux:  policy capability open_perms=1
[    7.870526] SELinux:  policy capability extended_socket_class=1
[    7.870979] SELinux:  policy capability always_check_network=0
[    7.871420] SELinux:  policy capability cgroup_seclabel=1
[    7.871860] SELinux:  policy capability nnp_nosuid_transition=1
[    7.872296] SELinux:  policy capability genfs_seclabel_symlinks=1
[    7.872728] SELinux:  policy capability ioctl_skip_cloexec=0
[    7.904294] audit: type=1403 audit(1703089644.369:3): auid=4294967295 ses=4294967295 lsm=selinux res=1
[    7.904991] systemd[1]: Successfully loaded SELinux policy in 71.839ms.
[    7.932990] systemd[1]: Relabeled /dev, /dev/shm, /run, /sys/fs/cgroup in 23.072ms.
[    7.938263] systemd[1]: systemd 254.7-1.fc39 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[    7.939284] systemd[1]: Detected architecture x86-64.
[    8.097369] systemd[1]: bpf-lsm: LSM BPF program attached
[    8.174091] systemd-sysv-generator[748]: SysV service '/etc/rc.d/init.d/xencommons' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !
[    8.188231] zram: Added device: zram0
[    8.297085] systemd[1]: initrd-switch-root.service: Deactivated successfully.
[    8.305810] systemd[1]: Stopped initrd-switch-root.service - Switch Root.
[    8.307789] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
[    8.308114] systemd[1]: Created slice machine.slice - Virtual Machine and Container Slice.
[    8.310299] systemd[1]: Created slice system-getty.slice - Slice /system/getty.
[    8.310750] GPIO 5 is active: 0x10141b00
[    8.311300] systemd[1]: Created slice system-sshd\x2dkeygen.slice - Slice /system/sshd-keygen.
[    8.312355] systemd[1]: Created slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck.
[    8.313389] systemd[1]: Created slice system-systemd\x2dzram\x2dsetup.slice - Slice /system/systemd-zram-setup.
[    8.314504] systemd[1]: Created slice user.slice - User and Session Slice.
[    8.315305] systemd[1]: systemd-ask-password-plymouth.path: Deactivated successfully.
[    8.315807] systemd[1]: Stopped systemd-ask-password-plymouth.path.
[    8.316508] systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
[    8.317732] systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
[    8.318409] systemd[1]: Stopped target initrd-switch-root.target - Switch Root.
[    8.319418] systemd[1]: Stopped target initrd-fs.target - Initrd File Systems.
[    8.319953] systemd[1]: Stopped target initrd-root-fs.target - Initrd Root File System.
[    8.320981] systemd[1]: Reached target integritysetup.target - Local Integrity Protected Volumes.
[    8.322087] systemd[1]: Reached target slices.target - Slice Units.
[    8.323112] systemd[1]: Reached target veritysetup.target - Local Verity Protected Volumes.
[    8.325580] systemd[1]: Listening on dm-event.socket - Device-mapper event daemon FIFOs.
[    8.328577] systemd[1]: Listening on lvm2-lvmpolld.socket - LVM2 poll daemon socket.
[    8.330161] systemd[1]: Listening on systemd-coredump.socket - Process Core Dump Socket.
[    8.331229] systemd[1]: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe.
[    8.332845] systemd[1]: Listening on systemd-journald-audit.socket - Journal Audit Socket.
[    8.334210] systemd[1]: Listening on systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket.
[    8.335823] systemd[1]: Listening on systemd-udevd-control.socket - udev Control Socket.
[    8.336618] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
[    8.337866] systemd[1]: Listening on systemd-userdbd.socket - User Database Manager Socket.
[    8.351912] systemd[1]: Mounting dev-hugepages.mount - Huge Pages File System...
[    8.354867] systemd[1]: Mounting dev-mqueue.mount - POSIX Message Queue File System...
[    8.356188] systemd[1]: proc-xen.mount - Mount /proc/xen files was skipped because of an unmet condition check (ConditionPathExists=/proc/xen).
[    8.357829] systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System...
[    8.359901] systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace File System...
[    8.360798] systemd[1]: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab).
[    8.361306] systemd[1]: iscsi-starter.service was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/var/lib/iscsi/nodes).
[    8.362848] systemd[1]: Starting kmod-static-nodes.service - Create List of Static Device Nodes...
[    8.365005] systemd[1]: Starting lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
[    8.367391] systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs...
[    8.369768] systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
[    8.372287] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
[    8.374708] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
[    8.377693] systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse...
[    8.380020] systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
[    8.380947] systemd[1]: Stopping plymouth-start.service...
[    8.382215] systemd[1]: plymouth-switch-root.service: Deactivated successfully.
[    8.382904] systemd[1]: Stopped plymouth-switch-root.service.
[    8.384921] systemd[1]: systemd-fsck-root.service: Deactivated successfully.
[    8.385972] systemd[1]: Stopped systemd-fsck-root.service - File System Check on Root Device.
[    8.387004] loop: module loaded
[    8.388394] systemd[1]: Starting systemd-journald.service - Journal Service...
[    8.391317] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...
[    8.393205] systemd[1]: Starting systemd-network-generator.service - Generate network units from Kernel command line...
[    8.394662] systemd[1]: systemd-pcrmachine.service - TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
[    8.396983] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
[    8.397260] systemd-journald[773]: Collecting audit messages is enabled.
[    8.400319] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices...
[    8.401697] systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
[    8.402353] systemd[1]: Stopped systemd-vconsole-setup.service - Virtual Console Setup.
[    8.403659] audit: type=1131 audit(1703089644.868:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    8.405825] systemd[1]: Started systemd-journald.service - Journal Service.
[    8.407244] audit: type=1130 audit(1703089644.872:5): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    8.419322] audit: type=1131 audit(1703089644.884:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    8.439782] audit: type=1130 audit(1703089644.905:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    8.453583] audit: type=1130 audit(1703089644.918:8): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    8.480549] audit: type=1130 audit(1703089644.945:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    8.481874] audit: type=1131 audit(1703089644.945:10): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    8.501239] audit: type=1130 audit(1703089644.966:11): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=modprobe@dm_mod comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    8.649957] systemd-journald[773]: Received client request to flush runtime journal.
[    8.696253] systemd-journald[773]: /var/log/journal/c80b79eae1794302b76e09e5265106e3/system.journal: Journal file uses a different sequence number ID, rotating.
[    8.697207] systemd-journald[773]: Rotating system journal.
[    8.877822] zram0: detected capacity change from 0 to 16777216
[    8.908506] amd-pmf AMDI0102:00: registered PMF device successfully
[    8.964962] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[    8.966701] piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection
[    8.968461] input: PC Speaker as /devices/platform/pcspkr/input/input14
[    8.969270] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
[    8.975237] ACPI: bus type thunderbolt registered
[    8.997915] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    9.005875] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    9.010618] Adding 8388604k swap on /dev/zram0.  Priority:100 extents:1 across:8388604k SSDsc
[    9.014489] RAPL PMU: API unit is 2^-32 Joules, 1 fixed counters, 163840 ms ovfl timer
[    9.015918] RAPL PMU: hw unit of domain package 2^-16 Joules
[    9.032176] Bluetooth: Core ver 2.22
[    9.032203] NET: Registered PF_BLUETOOTH protocol family
[    9.032205] Bluetooth: HCI device and connection manager initialized
[    9.032209] Bluetooth: HCI socket layer initialized
[    9.032211] Bluetooth: L2CAP socket layer initialized
[    9.032218] Bluetooth: SCO socket layer initialized
[    9.047786] usb 1-5: using ACPI '\_SB.PCI0.GP17.XHC0.RHUB.PRT5' for 'reset' GPIO lookup
[    9.047794] acpi device:29: GPIO: looking up reset-gpios
[    9.047796] acpi device:29: GPIO: looking up reset-gpio
[    9.047797] usb 1-5: using lookup tables for GPIO lookup
[    9.047798] usb 1-5: No GPIO consumer reset found
[    9.047890] usbcore: registered new interface driver btusb
[    9.050798] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20231120183620
[    9.126093] kvm_amd: TSC scaling supported
[    9.126990] kvm_amd: Nested Virtualization enabled
[    9.127706] kvm_amd: Nested Paging enabled
[    9.129692] kvm_amd: Virtual VMLOAD VMSAVE supported
[    9.130867] kvm_amd: Virtual GIF supported
[    9.131764] kvm_amd: Virtual NMI enabled
[    9.131765] kvm_amd: LBR virtualization supported
[    9.145631] MCE: In-kernel MCE decoding enabled.
[    9.162608] mt7921e 0000:01:00.0: enabling device (0000 -> 0002)
[    9.174672] mt7921e 0000:01:00.0: ASIC revision: 79220010
[    9.189840] intel_rapl_common: Found RAPL domain package
[    9.190832] Bluetooth: hci0: Device setup in 139554 usecs
[    9.191158] intel_rapl_common: Found RAPL domain core
[    9.191984] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[    9.252113] mt7921e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20231120183400a

[    9.254049] Bluetooth: hci0: AOSP extensions version v1.00
[    9.255758] Bluetooth: hci0: AOSP quality report is supported
[    9.276439] mt7921e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20231120183441
[    9.317586] GPIO 5 is active: 0x10141b00
[    9.498431] RPC: Registered named UNIX socket transport module.
[    9.499284] RPC: Registered udp transport module.
[    9.500045] RPC: Registered tcp transport module.
[    9.500725] RPC: Registered tcp-with-tls transport module.
[    9.501335] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    9.624197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    9.625776] Bluetooth: BNEP filters: protocol multicast
[    9.626781] Bluetooth: BNEP socket layer initialized
[    9.628966] Bluetooth: MGMT ver 1.22
[    9.754042] NET: Registered PF_QIPCRTR protocol family
[    9.853250] GPIO 5 is active: 0x10141b00
[    9.953835] GPIO 5 is active: 0x10141b00
[    9.962589] r8152 8-1.1:1.0 enp195s0f4u1u1: carrier on
[   10.055542] GPIO 5 is active: 0x10141b00
[   10.156242] GPIO 5 is active: 0x10141b00
[   10.256825] GPIO 5 is active: 0x10141b00
[   10.358653] GPIO 5 is active: 0x10141b00
[   10.375454] mt7921e 0000:01:00.0 wlp1s0: renamed from wlan0
[   10.459252] GPIO 5 is active: 0x10141b00
[   10.561314] GPIO 5 is active: 0x10141b00
[   10.662217] GPIO 5 is active: 0x10141b00
[   10.762363] GPIO 5 is active: 0x10141b00
[   10.864168] GPIO 5 is active: 0x10141b00
[   10.965600] GPIO 5 is active: 0x10141b00
[   11.067125] GPIO 5 is active: 0x10141b00
[   11.168429] GPIO 5 is active: 0x10141b00
[   11.269035] GPIO 5 is active: 0x10141b00
[   11.370210] GPIO 5 is active: 0x10141b00
[   11.471284] GPIO 5 is active: 0x10141b00
[   11.572678] GPIO 5 is active: 0x10141b00
[   11.673815] GPIO 5 is active: 0x10141b00
[   11.774354] GPIO 5 is active: 0x10141b00
[   11.876426] GPIO 5 is active: 0x10141b00
[   11.976989] GPIO 5 is active: 0x10141b00
[   12.078760] GPIO 5 is active: 0x10141b00
[   12.179416] GPIO 5 is active: 0x10141b00
[   12.279840] GPIO 5 is active: 0x10141b00
[   12.381769] GPIO 5 is active: 0x10141b00
[   12.482368] GPIO 5 is active: 0x10141b00
[   12.583714] GPIO 5 is active: 0x10141b00
[   12.684432] GPIO 5 is active: 0x10141b00
[   12.785119] GPIO 5 is active: 0x10141b00
[   12.886896] GPIO 5 is active: 0x10141b00
[   12.987864] GPIO 5 is active: 0x10141b00
[   13.089616] GPIO 5 is active: 0x10141b00
[   13.190404] GPIO 5 is active: 0x10141b00
[   13.290564] GPIO 5 is active: 0x10141b00
[   13.392568] GPIO 5 is active: 0x10141b00
[   13.492984] GPIO 5 is active: 0x10141b00
[   13.594981] GPIO 5 is active: 0x10141b00
[   13.695242] GPIO 5 is active: 0x10141b00
[   13.795893] GPIO 5 is active: 0x10141b00
[   13.897206] GPIO 5 is active: 0x10141b00
[   13.998253] GPIO 5 is active: 0x10141b00
[   14.100213] GPIO 5 is active: 0x10141b00
[   14.201680] GPIO 5 is active: 0x10141b00
[   14.302428] GPIO 5 is active: 0x10141b00
[   14.403802] GPIO 5 is active: 0x10141b00
[   14.504509] GPIO 5 is active: 0x10141b00
[   14.508484] wlp1s0: authenticate with 60:22:32:37:20:46
[   14.608190] GPIO 5 is active: 0x10141b00
[   14.708743] GPIO 5 is active: 0x10141b00
[   14.810543] GPIO 5 is active: 0x10141b00
[   14.911961] GPIO 5 is active: 0x10141b00
[   15.015545] wlp1s0: send auth to 60:22:32:37:20:46 (try 1/3)
[   15.024157] GPIO 5 is active: 0x10141b00
[   15.126253] GPIO 5 is active: 0x10141b00
[   15.128032] wlp1s0: authenticate with 60:22:32:37:20:46
[   15.137754] wlp1s0: send auth to 60:22:32:37:20:46 (try 1/3)
[   15.169767] wlp1s0: authenticated
[   15.170721] wlp1s0: associate with 60:22:32:37:20:46 (try 1/3)
[   15.186689] wlp1s0: RX AssocResp from 60:22:32:37:20:46 (capab=0x1111 status=0 aid=10)
[   15.221703] wlp1s0: associated
[   15.227667] GPIO 5 is active: 0x10141b00
[   15.329482] GPIO 5 is active: 0x10141b00
[   15.429042] wlp1s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 60:22:32:37:20:46
[   15.430223] GPIO 5 is active: 0x10141b00
[   15.530755] GPIO 5 is active: 0x10141b00
[   15.633741] GPIO 5 is active: 0x10141b00
[   15.734317] GPIO 5 is active: 0x10141b00
[   15.836436] GPIO 5 is active: 0x10141b00
[   15.867210] systemd-journald[773]: /var/log/journal/c80b79eae1794302b76e09e5265106e3/user-1000.journal: Journal file uses a different sequence number ID, rotating.
[   15.937325] GPIO 5 is active: 0x10141b00
[   16.050585] GPIO 5 is active: 0x10141b00
[   16.152958] GPIO 5 is active: 0x10141b00
[   16.253512] GPIO 5 is active: 0x10141b00
[   16.355597] GPIO 5 is active: 0x10141b00
[   16.457164] GPIO 5 is active: 0x10141b00
[   16.557252] GPIO 5 is active: 0x10141b00
[   16.660502] GPIO 5 is active: 0x10141b00
[   16.760768] GPIO 5 is active: 0x10141b00
[   16.864190] GPIO 5 is active: 0x10141b00
[   16.964566] GPIO 5 is active: 0x10141b00
[   17.077981] GPIO 5 is active: 0x10141b00
[   17.180038] GPIO 5 is active: 0x10141b00
[   17.281517] GPIO 5 is active: 0x10141b00
[   17.383331] GPIO 5 is active: 0x10141b00
[   17.484002] GPIO 5 is active: 0x10141b00
[   17.585104] GPIO 5 is active: 0x10141b00
[   17.686593] GPIO 5 is active: 0x10141b00
[   17.787611] GPIO 5 is active: 0x10141b00
[   17.890686] GPIO 5 is active: 0x10141b00
[   17.990781] GPIO 5 is active: 0x10141b00
[   18.112549] GPIO 5 is active: 0x10141b00
[   18.212948] GPIO 5 is active: 0x10141b00
[   18.313707] GPIO 5 is active: 0x10141b00
[   18.415949] GPIO 5 is active: 0x10141b00
[   18.517195] GPIO 5 is active: 0x10141b00
[   18.619340] GPIO 5 is active: 0x10141b00
[   18.720515] GPIO 5 is active: 0x10141b00
[   18.820887] GPIO 5 is active: 0x10141b00
[   18.923419] GPIO 5 is active: 0x10141b00
[   19.024373] GPIO 5 is active: 0x10141b00
[   19.143670] GPIO 5 is active: 0x10141b00
[   19.143872] GPIO 5 is active: 0x10141b00
[   19.244283] GPIO 5 is active: 0x10141b00
[   19.346400] GPIO 5 is active: 0x10141b00
[   19.447768] GPIO 5 is active: 0x10141b00
[   19.548927] GPIO 5 is active: 0x10141b00
[   19.651120] GPIO 5 is active: 0x10141b00
[   19.752236] GPIO 5 is active: 0x10141b00
[   19.853397] GPIO 5 is active: 0x10141b00
[   19.955937] GPIO 5 is active: 0x10141b00
[   20.056758] GPIO 5 is active: 0x10141b00
[   20.170203] GPIO 5 is active: 0x10141b00
[   20.270295] GPIO 5 is active: 0x10141b00
[   20.372905] GPIO 5 is active: 0x10141b00
[   20.473604] GPIO 5 is active: 0x10141b00
[   20.575288] GPIO 5 is active: 0x10141b00
[   20.677656] GPIO 5 is active: 0x10141b00
[   20.778823] GPIO 5 is active: 0x10141b00
[   20.880428] GPIO 5 is active: 0x10141b00
[   20.981349] GPIO 5 is active: 0x10141b00
[   21.082006] GPIO 5 is active: 0x10141b00
[   21.194295] GPIO 5 is active: 0x10141b00
[   21.295481] GPIO 5 is active: 0x10141b00
[   21.398584] GPIO 5 is active: 0x10141b00
[   21.498813] GPIO 5 is active: 0x10141b00
[   21.599754] GPIO 5 is active: 0x10141b00
[   21.701359] GPIO 5 is active: 0x10141b00
[   21.803314] GPIO 5 is active: 0x10141b00
[   21.905114] GPIO 5 is active: 0x10141b00
[   22.006787] GPIO 5 is active: 0x10141b00
[   22.107908] GPIO 5 is active: 0x10141b00
[   22.220951] GPIO 5 is active: 0x10141b00
[   22.321337] GPIO 5 is active: 0x10141b00
[   22.424645] GPIO 5 is active: 0x10141b00
[   22.524756] GPIO 5 is active: 0x10141b00
[   22.627134] GPIO 5 is active: 0x10141b00
[   22.728070] GPIO 5 is active: 0x10141b00
[   22.829691] GPIO 5 is active: 0x10141b00
[   22.931994] GPIO 5 is active: 0x10141b00
[   23.033214] GPIO 5 is active: 0x10141b00
[   23.134386] GPIO 5 is active: 0x10141b00
[   23.241647] GPIO 5 is active: 0x10141b00
[   23.342505] GPIO 5 is active: 0x10141b00
[   23.445205] GPIO 5 is active: 0x10141b00
[   23.545785] GPIO 5 is active: 0x10141b00
[   23.648879] GPIO 5 is active: 0x10141b00
[   23.749895] GPIO 5 is active: 0x10141b00
[   23.851258] GPIO 5 is active: 0x10141b00
[   23.953259] GPIO 5 is active: 0x10141b00
[   24.055041] GPIO 5 is active: 0x10141b00
[   24.155842] GPIO 5 is active: 0x10141b00
[   24.272733] GPIO 5 is active: 0x10141b00
[   24.373073] GPIO 5 is active: 0x10141b00
[   24.475415] GPIO 5 is active: 0x10141b00
[   24.575589] GPIO 5 is active: 0x10141b00
[   24.679238] GPIO 5 is active: 0x10141b00
[   24.780012] GPIO 5 is active: 0x10141b00
[   24.881155] GPIO 5 is active: 0x10141b00
[   24.983275] GPIO 5 is active: 0x10141b00
[   25.084696] GPIO 5 is active: 0x10141b00
[   25.187150] GPIO 5 is active: 0x10141b00
[   25.303787] GPIO 5 is active: 0x10141b00
[   25.405525] GPIO 5 is active: 0x10141b00
[   25.507314] GPIO 5 is active: 0x10141b00
[   25.608519] GPIO 5 is active: 0x10141b00
[   25.710829] GPIO 5 is active: 0x10141b00
[   25.811892] GPIO 5 is active: 0x10141b00
[   25.913791] GPIO 5 is active: 0x10141b00
[   26.015207] GPIO 5 is active: 0x10141b00
[   26.116356] GPIO 5 is active: 0x10141b00
[   26.218161] GPIO 5 is active: 0x10141b00
[   26.323868] GPIO 5 is active: 0x10141b00
[   26.425118] GPIO 5 is active: 0x10141b00
[   26.526309] GPIO 5 is active: 0x10141b00
[   26.627138] GPIO 5 is active: 0x10141b00
[   26.729643] GPIO 5 is active: 0x10141b00
[   26.829976] GPIO 5 is active: 0x10141b00
[   26.932683] GPIO 5 is active: 0x10141b00
[   27.034049] GPIO 5 is active: 0x10141b00
[   27.134955] GPIO 5 is active: 0x10141b00
[   27.236899] GPIO 5 is active: 0x10141b00
[   27.344359] GPIO 5 is active: 0x10141b00
[   27.445438] GPIO 5 is active: 0x10141b00
[   27.547652] GPIO 5 is active: 0x10141b00
[   27.647997] GPIO 5 is active: 0x10141b00
[   27.751805] GPIO 5 is active: 0x10141b00
[   27.852417] GPIO 5 is active: 0x10141b00
[   27.954558] GPIO 5 is active: 0x10141b00
[   28.055559] GPIO 5 is active: 0x10141b00
[   28.157146] GPIO 5 is active: 0x10141b00
[   28.259267] GPIO 5 is active: 0x10141b00
[   28.370520] GPIO 5 is active: 0x10141b00
[   28.472469] GPIO 5 is active: 0x10141b00
[   28.574286] GPIO 5 is active: 0x10141b00
[   28.674793] GPIO 5 is active: 0x10141b00
[   28.776443] GPIO 5 is active: 0x10141b00
[   28.877356] GPIO 5 is active: 0x10141b00
[   28.980305] GPIO 5 is active: 0x10141b00
[   29.081015] GPIO 5 is active: 0x10141b00
[   29.182725] GPIO 5 is active: 0x10141b00
[   29.284133] GPIO 5 is active: 0x10141b00
[   29.396118] GPIO 5 is active: 0x10141b00
[   29.498128] GPIO 5 is active: 0x10141b00
[   29.599554] GPIO 5 is active: 0x10141b00
[   29.599784] GPIO 5 is active: 0x10141b00
[   29.701024] GPIO 5 is active: 0x10141b00
[   29.803224] GPIO 5 is active: 0x10141b00
[   29.903731] GPIO 5 is active: 0x10141b00
[   30.006719] GPIO 5 is active: 0x10141b00
[   30.107336] GPIO 5 is active: 0x10141b00
[   30.209741] GPIO 5 is active: 0x10141b00
[   30.310156] GPIO 5 is active: 0x10141b00
[   30.428092] GPIO 5 is active: 0x10141b00
[   30.530480] GPIO 5 is active: 0x10141b00
[   30.631771] GPIO 5 is active: 0x10141b00
[   30.733802] GPIO 5 is active: 0x10141b00
[   30.835052] GPIO 5 is active: 0x10141b00
[   30.935570] GPIO 5 is active: 0x10141b00
[   31.038967] GPIO 5 is active: 0x10141b00
[   31.139615] GPIO 5 is active: 0x10141b00
[   31.242500] GPIO 5 is active: 0x10141b00
[   31.343155] GPIO 5 is active: 0x10141b00
[   31.462510] GPIO 5 is active: 0x10141b00
[   31.563585] GPIO 5 is active: 0x10141b00
[   31.665149] GPIO 5 is active: 0x10141b00
[   31.767088] GPIO 5 is active: 0x10141b00
[   31.868672] GPIO 5 is active: 0x10141b00
[   31.970152] GPIO 5 is active: 0x10141b00
[   32.072172] GPIO 5 is active: 0x10141b00
[   32.172844] GPIO 5 is active: 0x10141b00
[   32.275610] GPIO 5 is active: 0x10141b00
[   32.376334] GPIO 5 is active: 0x10141b00
[   32.491234] GPIO 5 is active: 0x10141b00
[   32.591385] GPIO 5 is active: 0x10141b00
[   32.692518] GPIO 5 is active: 0x10141b00
[   32.794907] GPIO 5 is active: 0x10141b00
[   32.896050] GPIO 5 is active: 0x10141b00
[   32.997786] GPIO 5 is active: 0x10141b00
[   33.099878] GPIO 5 is active: 0x10141b00
[   33.201000] GPIO 5 is active: 0x10141b00
[   33.302710] GPIO 5 is active: 0x10141b00
[   33.403914] GPIO 5 is active: 0x10141b00
[   33.512166] GPIO 5 is active: 0x10141b00
[   33.613234] GPIO 5 is active: 0x10141b00
[   33.715046] GPIO 5 is active: 0x10141b00
[   33.816750] GPIO 5 is active: 0x10141b00
[   33.917846] GPIO 5 is active: 0x10141b00
[   34.019711] GPIO 5 is active: 0x10141b00
[   34.121127] GPIO 5 is active: 0x10141b00
[   34.221865] GPIO 5 is active: 0x10141b00
[   34.324652] GPIO 5 is active: 0x10141b00
[   34.425262] GPIO 5 is active: 0x10141b00
[   34.532079] GPIO 5 is active: 0x10141b00
[   34.632251] GPIO 5 is active: 0x10141b00
[   34.734721] GPIO 5 is active: 0x10141b00
[   34.835806] GPIO 5 is active: 0x10141b00
[   34.936862] GPIO 5 is active: 0x10141b00
[   35.038611] GPIO 5 is active: 0x10141b00
[   35.140705] GPIO 5 is active: 0x10141b00
[   35.241794] GPIO 5 is active: 0x10141b00
[   35.343262] GPIO 5 is active: 0x10141b00
[   35.444169] GPIO 5 is active: 0x10141b00
[   35.557506] GPIO 5 is active: 0x10141b00
[   35.658119] GPIO 5 is active: 0x10141b00
[   35.760111] GPIO 5 is active: 0x10141b00
[   35.860639] GPIO 5 is active: 0x10141b00
[   35.961717] GPIO 5 is active: 0x10141b00
[   36.063739] GPIO 5 is active: 0x10141b00
[   36.165242] GPIO 5 is active: 0x10141b00
[   36.266908] GPIO 5 is active: 0x10141b00
[   36.368892] GPIO 5 is active: 0x10141b00
[   36.469423] GPIO 5 is active: 0x10141b00
[   36.582941] GPIO 5 is active: 0x10141b00
[   36.683549] GPIO 5 is active: 0x10141b00
[   36.786466] GPIO 5 is active: 0x10141b00
[   36.887028] GPIO 5 is active: 0x10141b00
[   36.988667] GPIO 5 is active: 0x10141b00
[   37.090651] GPIO 5 is active: 0x10141b00
[   37.090971] GPIO 5 is active: 0x10141b00
[   37.192155] GPIO 5 is active: 0x10141b00
[   37.294263] GPIO 5 is active: 0x10141b00
[   37.396077] GPIO 5 is active: 0x10141b00
[   37.496816] GPIO 5 is active: 0x10141b00
[   37.607935] GPIO 5 is active: 0x10141b00
[   37.708701] GPIO 5 is active: 0x10141b00
[   37.811903] GPIO 5 is active: 0x10141b00
[   37.912531] GPIO 5 is active: 0x10141b00
[   38.014477] GPIO 5 is active: 0x10141b00
[   38.115627] GPIO 5 is active: 0x10141b00
[   38.217496] GPIO 5 is active: 0x10141b00
[   38.318941] GPIO 5 is active: 0x10141b00
[   38.420605] GPIO 5 is active: 0x10141b00
[   38.521542] GPIO 5 is active: 0x10141b00
[   38.639795] GPIO 5 is active: 0x10141b00
[   38.740290] GPIO 5 is active: 0x10141b00
[   38.843255] GPIO 5 is active: 0x10141b00
[   38.943879] GPIO 5 is active: 0x10141b00
[   39.047874] GPIO 5 is active: 0x10141b00
[   39.148777] GPIO 5 is active: 0x10141b00
[   39.250270] GPIO 5 is active: 0x10141b00
[   39.351523] GPIO 5 is active: 0x10141b00
[   39.453101] GPIO 5 is active: 0x10141b00
[   39.554800] GPIO 5 is active: 0x10141b00
[   39.665125] GPIO 5 is active: 0x10141b00
[   39.765913] GPIO 5 is active: 0x10141b00
[   39.867692] GPIO 5 is active: 0x10141b00
[   39.968256] GPIO 5 is active: 0x10141b00
[   40.071287] GPIO 5 is active: 0x10141b00
[   40.171661] GPIO 5 is active: 0x10141b00
[   40.273352] GPIO 5 is active: 0x10141b00
[   40.374951] GPIO 5 is active: 0x10141b00
[   40.476347] GPIO 5 is active: 0x10141b00
[   40.578340] GPIO 5 is active: 0x10141b00
[   40.692013] GPIO 5 is active: 0x10141b00
[   40.792713] GPIO 5 is active: 0x10141b00
[   40.894125] GPIO 5 is active: 0x10141b00
[   40.994656] GPIO 5 is active: 0x10141b00
[   41.097630] GPIO 5 is active: 0x10141b00
[   41.198393] GPIO 5 is active: 0x10141b00
[   41.301523] GPIO 5 is active: 0x10141b00
[   41.401711] GPIO 5 is active: 0x10141b00
[   41.503745] GPIO 5 is active: 0x10141b00
[   41.605642] GPIO 5 is active: 0x10141b00
[   41.733515] GPIO 5 is active: 0x10141b00
[   41.835307] GPIO 5 is active: 0x10141b00
[   41.936658] GPIO 5 is active: 0x10141b00
[   42.037772] GPIO 5 is active: 0x10141b00
[   42.140171] GPIO 5 is active: 0x10141b00
[   42.240734] GPIO 5 is active: 0x10141b00
[   42.343894] GPIO 5 is active: 0x10141b00
[   42.444479] GPIO 5 is active: 0x10141b00
[   42.546507] GPIO 5 is active: 0x10141b00
[   42.647802] GPIO 5 is active: 0x10141b00
[   42.759555] GPIO 5 is active: 0x10141b00
[   42.861184] GPIO 5 is active: 0x10141b00
[   42.962623] GPIO 5 is active: 0x10141b00
[   43.064014] GPIO 5 is active: 0x10141b00
[   43.166052] GPIO 5 is active: 0x10141b00
[   43.266673] GPIO 5 is active: 0x10141b00
[   43.369320] GPIO 5 is active: 0x10141b00
[   43.470317] GPIO 5 is active: 0x10141b00
[   43.572177] GPIO 5 is active: 0x10141b00
[   43.672747] GPIO 5 is active: 0x10141b00
[   43.791376] GPIO 5 is active: 0x10141b00
[   43.893167] GPIO 5 is active: 0x10141b00
[   43.994788] GPIO 5 is active: 0x10141b00
[   44.096777] GPIO 5 is active: 0x10141b00
[   44.197916] GPIO 5 is active: 0x10141b00
[   44.298851] GPIO 5 is active: 0x10141b00
[   44.401861] GPIO 5 is active: 0x10141b00
[   44.502511] GPIO 5 is active: 0x10141b00
[   44.605012] GPIO 5 is active: 0x10141b00
[   44.706244] GPIO 5 is active: 0x10141b00
[   44.820565] GPIO 5 is active: 0x10141b00
[   44.921652] GPIO 5 is active: 0x10141b00
[   45.023213] GPIO 5 is active: 0x10141b00
[   45.125304] GPIO 5 is active: 0x10141b00
[   45.226638] GPIO 5 is active: 0x10141b00
[   45.327671] GPIO 5 is active: 0x10141b00
[   45.429773] GPIO 5 is active: 0x10141b00
[   45.530920] GPIO 5 is active: 0x10141b00
[   45.632864] GPIO 5 is active: 0x10141b00
[   45.733328] GPIO 5 is active: 0x10141b00
[   45.856747] GPIO 5 is active: 0x10141b00
[   45.957360] GPIO 5 is active: 0x10141b00
[   46.059250] GPIO 5 is active: 0x10141b00
[   46.160928] GPIO 5 is active: 0x10141b00
[   46.262504] GPIO 5 is active: 0x10141b00
[   46.364773] GPIO 5 is active: 0x10141b00
[   46.466385] GPIO 5 is active: 0x10141b00
[   46.566832] GPIO 5 is active: 0x10141b00
[   46.670075] GPIO 5 is active: 0x10141b00
[   46.770678] GPIO 5 is active: 0x10141b00
[   46.882748] GPIO 5 is active: 0x10141b00
[   46.983852] GPIO 5 is active: 0x10141b00
[   47.086187] GPIO 5 is active: 0x10141b00
[   47.186554] GPIO 5 is active: 0x10141b00
[   47.288432] GPIO 5 is active: 0x10141b00
[   47.390157] GPIO 5 is active: 0x10141b00
[   47.491721] GPIO 5 is active: 0x10141b00
[   47.592305] GPIO 5 is active: 0x10141b00
[   47.695638] GPIO 5 is active: 0x10141b00
[   47.795855] GPIO 5 is active: 0x10141b00
[   47.902688] GPIO 5 is active: 0x10141b00
[   48.003137] GPIO 5 is active: 0x10141b00
[   48.105388] GPIO 5 is active: 0x10141b00
[   48.206314] GPIO 5 is active: 0x10141b00
[   48.307555] GPIO 5 is active: 0x10141b00
[   48.409681] GPIO 5 is active: 0x10141b00
[   48.511308] GPIO 5 is active: 0x10141b00
[   48.612366] GPIO 5 is active: 0x10141b00
[   48.713858] GPIO 5 is active: 0x10141b00
[   48.814602] GPIO 5 is active: 0x10141b00
[   48.929051] GPIO 5 is active: 0x10141b00
[   49.029677] GPIO 5 is active: 0x10141b00
[   49.132597] GPIO 5 is active: 0x10141b00
[   49.233330] GPIO 5 is active: 0x10141b00
[   49.335124] GPIO 5 is active: 0x10141b00
[   49.437321] GPIO 5 is active: 0x10141b00
[   49.538951] GPIO 5 is active: 0x10141b00
[   49.640095] GPIO 5 is active: 0x10141b00
[   49.742181] GPIO 5 is active: 0x10141b00
[   49.842646] GPIO 5 is active: 0x10141b00
[   49.953709] GPIO 5 is active: 0x10141b00
[   50.054390] GPIO 5 is active: 0x10141b00
[   50.157181] GPIO 5 is active: 0x10141b00
[   50.257269] GPIO 5 is active: 0x10141b00
[   50.360132] GPIO 5 is active: 0x10141b00
[   50.461605] GPIO 5 is active: 0x10141b00
[   50.562151] GPIO 5 is active: 0x10141b00
[   50.663692] GPIO 5 is active: 0x10141b00
[   50.764713] GPIO 5 is active: 0x10141b00
[   50.865814] GPIO 5 is active: 0x10141b00
[   50.978939] GPIO 5 is active: 0x10141b00
[   51.079542] GPIO 5 is active: 0x10141b00
[   51.182470] GPIO 5 is active: 0x10141b00
[   51.283128] GPIO 5 is active: 0x10141b00
[   51.384889] GPIO 5 is active: 0x10141b00
[   51.485749] GPIO 5 is active: 0x10141b00
[   51.587622] GPIO 5 is active: 0x10141b00
[   51.689525] GPIO 5 is active: 0x10141b00
[   51.791628] GPIO 5 is active: 0x10141b00
[   51.892376] GPIO 5 is active: 0x10141b00
[   51.999520] GPIO 5 is active: 0x10141b00
[   52.100057] GPIO 5 is active: 0x10141b00
[   52.201665] GPIO 5 is active: 0x10141b00
[   52.302662] GPIO 5 is active: 0x10141b00
[   52.404606] GPIO 5 is active: 0x10141b00
[   52.505226] GPIO 5 is active: 0x10141b00
[   52.606200] GPIO 5 is active: 0x10141b00
[   52.707947] GPIO 5 is active: 0x10141b00
[   52.809727] GPIO 5 is active: 0x10141b00
[   52.912639] GPIO 5 is active: 0x10141b00
[   53.019122] GPIO 5 is active: 0x10141b00
[   53.119661] GPIO 5 is active: 0x10141b00
[   53.222635] GPIO 5 is active: 0x10141b00
[   53.323246] GPIO 5 is active: 0x10141b00
[   53.426185] GPIO 5 is active: 0x10141b00
[   53.526885] GPIO 5 is active: 0x10141b00
[   53.628769] GPIO 5 is active: 0x10141b00
[   53.730336] GPIO 5 is active: 0x10141b00
[   53.832210] GPIO 5 is active: 0x10141b00
[   53.934241] GPIO 5 is active: 0x10141b00
[   54.039261] GPIO 5 is active: 0x10141b00
[   54.140396] GPIO 5 is active: 0x10141b00
[   54.242226] GPIO 5 is active: 0x10141b00
[   54.342947] GPIO 5 is active: 0x10141b00
[   54.445779] GPIO 5 is active: 0x10141b00
[   54.546457] GPIO 5 is active: 0x10141b00
[   54.648691] GPIO 5 is active: 0x10141b00
[   54.749193] GPIO 5 is active: 0x10141b00
[   54.850884] GPIO 5 is active: 0x10141b00
[   54.952328] GPIO 5 is active: 0x10141b00
[   55.070501] GPIO 5 is active: 0x10141b00
[   55.171695] GPIO 5 is active: 0x10141b00
[   55.273526] GPIO 5 is active: 0x10141b00
[   55.374428] GPIO 5 is active: 0x10141b00
[   55.477057] GPIO 5 is active: 0x10141b00
[   55.577668] GPIO 5 is active: 0x10141b00
[   55.679607] GPIO 5 is active: 0x10141b00
[   55.780352] GPIO 5 is active: 0x10141b00
[   55.881585] GPIO 5 is active: 0x10141b00
[   55.983065] GPIO 5 is active: 0x10141b00
[   56.095441] GPIO 5 is active: 0x10141b00
[   56.197270] GPIO 5 is active: 0x10141b00
[   56.299081] GPIO 5 is active: 0x10141b00
[   56.400042] GPIO 5 is active: 0x10141b00
[   56.502315] GPIO 5 is active: 0x10141b00
[   56.602810] GPIO 5 is active: 0x10141b00
[   56.705615] GPIO 5 is active: 0x10141b00
[   56.806458] GPIO 5 is active: 0x10141b00
[   56.907824] GPIO 5 is active: 0x10141b00
[   57.009563] GPIO 5 is active: 0x10141b00
[   57.122068] GPIO 5 is active: 0x10141b00
[   57.223143] GPIO 5 is active: 0x10141b00
[   57.325373] GPIO 5 is active: 0x10141b00
[   57.426523] GPIO 5 is active: 0x10141b00
[   57.528951] GPIO 5 is active: 0x10141b00
[   57.629339] GPIO 5 is active: 0x10141b00
[   57.732417] GPIO 5 is active: 0x10141b00
[   57.833344] GPIO 5 is active: 0x10141b00
[   57.934989] GPIO 5 is active: 0x10141b00
[   58.036081] GPIO 5 is active: 0x10141b00
[   58.152698] GPIO 5 is active: 0x10141b00
[   58.254475] GPIO 5 is active: 0x10141b00
[   58.357026] GPIO 5 is active: 0x10141b00
[   58.458278] GPIO 5 is active: 0x10141b00
[   58.560176] GPIO 5 is active: 0x10141b00
[   58.660748] GPIO 5 is active: 0x10141b00
[   58.763712] GPIO 5 is active: 0x10141b00
[   58.864215] GPIO 5 is active: 0x10141b00
[   58.966679] GPIO 5 is active: 0x10141b00
[   59.066890] GPIO 5 is active: 0x10141b00
[   59.187138] GPIO 5 is active: 0x10141b00
[   59.288624] GPIO 5 is active: 0x10141b00
[   59.389761] GPIO 5 is active: 0x10141b00
[   59.390025] GPIO 5 is active: 0x10141b00
[   59.491488] GPIO 5 is active: 0x10141b00
[   59.593452] GPIO 5 is active: 0x10141b00
[   59.694411] GPIO 5 is active: 0x10141b00
[   59.797127] GPIO 5 is active: 0x10141b00
[   59.898028] GPIO 5 is active: 0x10141b00
[   60.000487] GPIO 5 is active: 0x10141b00
[   60.100681] GPIO 5 is active: 0x10141b00
[   60.214798] GPIO 5 is active: 0x10141b00
[   60.315418] GPIO 5 is active: 0x10141b00
[   60.417285] GPIO 5 is active: 0x10141b00
[   60.519374] GPIO 5 is active: 0x10141b00
[   60.620816] GPIO 5 is active: 0x10141b00
[   60.722305] GPIO 5 is active: 0x10141b00
[   60.824404] GPIO 5 is active: 0x10141b00
[   60.925041] GPIO 5 is active: 0x10141b00
[   61.027449] GPIO 5 is active: 0x10141b00
[   61.128432] GPIO 5 is active: 0x10141b00
[   61.248951] GPIO 5 is active: 0x10141b00
[   61.349448] GPIO 5 is active: 0x10141b00
[   61.451970] GPIO 5 is active: 0x10141b00
[   61.553153] GPIO 5 is active: 0x10141b00
[   61.653618] GPIO 5 is active: 0x10141b00
[   61.755975] GPIO 5 is active: 0x10141b00
[   61.857650] GPIO 5 is active: 0x10141b00
[   61.958492] GPIO 5 is active: 0x10141b00

[-- Attachment #4: dmesg-xen-4.17.3-pre-6.6.7xen-irq-dbg-1+ --]
[-- Type: application/octet-stream, Size: 132018 bytes --]

[    0.000000] Linux version 6.6.7xen-irq-dbg-1+ (sch@fedora) (gcc (GCC) 13.2.1 20231205 (Red Hat 13.2.1-6), GNU ld version 2.40-13.fc39) #6 SMP PREEMPT_DYNAMIC Wed Dec 20 16:13:29 CET 2023
[    0.000000] Command line: placeholder root=UUID=71b1dc59-ea00-484c-b5e4-ee77ede771db ro "dyndbg=file drivers/gpio/* +p; file drivers/pinctrl/* +p; file arch/x86/pci/xen.c +p"
[    0.000000] [Firmware Bug]: TSC doesn't count with P0 frequency!
[    0.000000] initrd moved from [mem 0x08000000-0x15af4271] to [mem 0x1d795000-0x2b289271]
[    0.000000] Released 0 page(s)
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] Xen: [mem 0x0000000000000000-0x000000000007ffff] usable
[    0.000000] Xen: [mem 0x0000000000080000-0x00000000000fffff] reserved
[    0.000000] Xen: [mem 0x0000000000100000-0x0000000009afffff] usable
[    0.000000] Xen: [mem 0x0000000009b00000-0x0000000009dfffff] reserved
[    0.000000] Xen: [mem 0x0000000009e00000-0x0000000009efffff] usable
[    0.000000] Xen: [mem 0x0000000009f00000-0x0000000009f3bfff] ACPI NVS
[    0.000000] Xen: [mem 0x0000000009f3c000-0x000000004235ffff] usable
[    0.000000] Xen: [mem 0x0000000042360000-0x000000004455ffff] reserved
[    0.000000] Xen: [mem 0x0000000044560000-0x0000000044568fff] usable
[    0.000000] Xen: [mem 0x0000000044569000-0x000000004456cfff] reserved
[    0.000000] Xen: [mem 0x000000004456d000-0x000000004456efff] usable
[    0.000000] Xen: [mem 0x000000004456f000-0x000000004456ffff] reserved
[    0.000000] Xen: [mem 0x0000000044570000-0x000000005077efff] usable
[    0.000000] Xen: [mem 0x000000005077f000-0x0000000052f7efff] reserved
[    0.000000] Xen: [mem 0x0000000052f7f000-0x000000005af7efff] ACPI NVS
[    0.000000] Xen: [mem 0x000000005af7f000-0x000000005affefff] ACPI data
[    0.000000] Xen: [mem 0x000000005afff000-0x000000005affffff] usable
[    0.000000] Xen: [mem 0x000000005b000000-0x000000005bffffff] reserved
[    0.000000] Xen: [mem 0x000000005d790000-0x000000005d7effff] reserved
[    0.000000] Xen: [mem 0x000000005d7f5000-0x000000005fffffff] reserved
[    0.000000] Xen: [mem 0x00000000c0200000-0x00000000c0203fff] reserved
[    0.000000] Xen: [mem 0x00000000c0300000-0x00000000c03fffff] reserved
[    0.000000] Xen: [mem 0x00000000fec00000-0x00000000fec01fff] reserved
[    0.000000] Xen: [mem 0x00000000fed80000-0x00000000fed80fff] reserved
[    0.000000] Xen: [mem 0x00000000fee00000-0x00000000feefffff] reserved
[    0.000000] Xen: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] Xen: [mem 0x0000000100000000-0x000000107e2fffff] usable
[    0.000000] Xen: [mem 0x0000001080000000-0x00000010c01fffff] reserved
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] APIC: Static calls initialized
[    0.000000] efi: EFI v2.8 by INSYDE Corp.
[    0.000000] efi: ACPI=0x5affe000 ACPI 2.0=0x5affe014 SMBIOS=0x51677000 SMBIOS 3.0=0x51674000 (MEMATTR=0x4b714018 unusable) ESRT=0x5af9d018 MOKvar=0x5187c000 
[    0.000000] SMBIOS 3.5.0 present.
[    0.000000] DMI: Framework Laptop 13 (AMD Ryzen 7040Series)/FRANMDCP07, BIOS 03.03 10/17/2023
[    0.000000] Hypervisor detected: Xen PV
[    0.026639] tsc: Fast TSC calibration using PIT
[    0.026640] tsc: Detected 3293.501 MHz processor
[    0.026640] tsc: Detected 3293.816 MHz TSC
[    0.026715] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.026717] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.026724] last_pfn = 0x107e300 max_arch_pfn = 0x400000000
[    0.026726] MTRR map: 3 entries (0 fixed + 3 variable; max 16), built from 8 variable MTRRs
[    0.026727] MTRRs set to read-only
[    0.026729] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WC  WP  UC  UC  
[    0.026730] last_pfn = 0x5b000 max_arch_pfn = 0x400000000
[    0.026747] esrt: Reserving ESRT space from 0x000000005af9d018 to 0x000000005af9d050.
[    1.019522] Secure boot disabled
[    1.019525] RAMDISK: [mem 0x1d795000-0x2b289fff]
[    1.019531] ACPI: Early table checksum verification disabled
[    1.019538] ACPI: RSDP 0x000000005AFFE014 000024 (v02 INSYDE)
[    1.019543] ACPI: XSDT 0x000000005AF9E228 00016C (v01 INSYDE EDK2     00000002      01000013)
[    1.019595] ACPI: FACP 0x000000005AFEF000 00010C (v05 INSYDE EDK2     00000002 ACPI 00040000)
[    1.019635] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20230628/tbfadt-615)
[    1.019641] ACPI: DSDT 0x000000005AFDF000 0093A6 (v02 INSYDE EDK2     00000002 ACPI 00040000)
[    1.019645] ACPI: FACS 0x000000005AEB7000 000040
[    1.019650] ACPI: UEFI 0x000000005AF67000 0001CF (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019654] ACPI: SSDT 0x000000005AFF4000 008416 (v02 INSYDE EDK2     00000002 ACPI 00040000)
[    1.019658] ACPI: SSDT 0x000000005AFF2000 000ABD (v02 INSYDE EDK2     00001000 ACPI 00040000)
[    1.019663] ACPI: ASF! 0x000000005AFF1000 0000A5 (v32 INSYDE EDK2     00000002 ACPI 00040000)
[    1.019667] ACPI: BOOT 0x000000005AFF0000 000028 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    1.019672] ACPI: HPET 0x000000005AFEE000 000038 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    1.019676] ACPI: APIC 0x000000005AFED000 000138 (v03 INSYDE EDK2     00000002 ACPI 00040000)
[    1.019680] ACPI: MCFG 0x000000005AFEC000 00003C (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    1.019685] ACPI: SLIC 0x000000005AFEB000 000176 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    1.019689] ACPI: VFCT 0x000000005AFDA000 004284 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019694] ACPI: SSDT 0x000000005AFD9000 0000F8 (v02 INSYDE EDK2     00001000 ACPI 00040000)
[    1.019698] ACPI: SSDT 0x000000005AFD3000 00547E (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019703] ACPI: CRAT 0x000000005AFD2000 000F10 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019707] ACPI: CDIT 0x000000005AFD1000 000029 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019711] ACPI: SSDT 0x000000005AFD0000 000F8D (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019716] ACPI: SSDT 0x000000005AFCF000 000EC1 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019720] ACPI: SSDT 0x000000005AFCE000 000931 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019725] ACPI: SSDT 0x000000005AFCB000 0013EC (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019729] ACPI: SSDT 0x000000005AFFD000 00077A (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019734] ACPI: SSDT 0x000000005AFCA000 000737 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019738] ACPI: SSDT 0x000000005AFC8000 0015C8 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019742] ACPI: SSDT 0x000000005AFC5000 002A8F (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019747] ACPI: SSDT 0x000000005AFBB000 009821 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019751] ACPI: FPDT 0x000000005AFBA000 000044 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    1.019755] ACPI: BGRT 0x000000005AFB9000 000038 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    1.019760] ACPI: WSMT 0x000000005AFB8000 000028 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019764] ACPI: MHSP 0x000000005AFEA000 0000C8 (v04 INSYDE EDK2     20505348 ACPI 00040000)
[    1.019768] ACPI: SSDT 0x000000005AFE9000 0000E5 (v02 INSYDE EDK2     00000004 ACPI 00040000)
[    1.019773] ACPI: IVRS 0x000000005AFB7000 0001A4 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019777] ACPI: SSDT 0x000000005AFB6000 000747 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019781] ACPI: SSDT 0x000000005AFB5000 000C88 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019786] ACPI: SSDT 0x000000005AFB4000 000057 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019790] ACPI: SSDT 0x000000005AFB2000 00170B (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019794] ACPI: SSDT 0x000000005AFB1000 000FF7 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019799] ACPI: SSDT 0x000000005AFA7000 0097E3 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019803] ACPI: SSDT 0x000000005AFA2000 004FEB (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019808] ACPI: SSDT 0x000000005AFA1000 000C7F (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019812] ACPI: SSDT 0x000000005AFA0000 000956 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019816] ACPI: SSDT 0x000000005AF9F000 00008D (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019821] ACPI: SSDT 0x000000005AFCD000 000EAD (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    1.019823] ACPI: Reserving FACP table memory at [mem 0x5afef000-0x5afef10b]
[    1.019823] ACPI: Reserving DSDT table memory at [mem 0x5afdf000-0x5afe83a5]
[    1.019824] ACPI: Reserving FACS table memory at [mem 0x5aeb7000-0x5aeb703f]
[    1.019824] ACPI: Reserving UEFI table memory at [mem 0x5af67000-0x5af671ce]
[    1.019825] ACPI: Reserving SSDT table memory at [mem 0x5aff4000-0x5affc415]
[    1.019825] ACPI: Reserving SSDT table memory at [mem 0x5aff2000-0x5aff2abc]
[    1.019826] ACPI: Reserving ASF! table memory at [mem 0x5aff1000-0x5aff10a4]
[    1.019826] ACPI: Reserving BOOT table memory at [mem 0x5aff0000-0x5aff0027]
[    1.019827] ACPI: Reserving HPET table memory at [mem 0x5afee000-0x5afee037]
[    1.019827] ACPI: Reserving APIC table memory at [mem 0x5afed000-0x5afed137]
[    1.019828] ACPI: Reserving MCFG table memory at [mem 0x5afec000-0x5afec03b]
[    1.019828] ACPI: Reserving SLIC table memory at [mem 0x5afeb000-0x5afeb175]
[    1.019828] ACPI: Reserving VFCT table memory at [mem 0x5afda000-0x5afde283]
[    1.019829] ACPI: Reserving SSDT table memory at [mem 0x5afd9000-0x5afd90f7]
[    1.019829] ACPI: Reserving SSDT table memory at [mem 0x5afd3000-0x5afd847d]
[    1.019830] ACPI: Reserving CRAT table memory at [mem 0x5afd2000-0x5afd2f0f]
[    1.019830] ACPI: Reserving CDIT table memory at [mem 0x5afd1000-0x5afd1028]
[    1.019831] ACPI: Reserving SSDT table memory at [mem 0x5afd0000-0x5afd0f8c]
[    1.019831] ACPI: Reserving SSDT table memory at [mem 0x5afcf000-0x5afcfec0]
[    1.019832] ACPI: Reserving SSDT table memory at [mem 0x5afce000-0x5afce930]
[    1.019832] ACPI: Reserving SSDT table memory at [mem 0x5afcb000-0x5afcc3eb]
[    1.019832] ACPI: Reserving SSDT table memory at [mem 0x5affd000-0x5affd779]
[    1.019833] ACPI: Reserving SSDT table memory at [mem 0x5afca000-0x5afca736]
[    1.019833] ACPI: Reserving SSDT table memory at [mem 0x5afc8000-0x5afc95c7]
[    1.019834] ACPI: Reserving SSDT table memory at [mem 0x5afc5000-0x5afc7a8e]
[    1.019834] ACPI: Reserving SSDT table memory at [mem 0x5afbb000-0x5afc4820]
[    1.019835] ACPI: Reserving FPDT table memory at [mem 0x5afba000-0x5afba043]
[    1.019835] ACPI: Reserving BGRT table memory at [mem 0x5afb9000-0x5afb9037]
[    1.019836] ACPI: Reserving WSMT table memory at [mem 0x5afb8000-0x5afb8027]
[    1.019836] ACPI: Reserving MHSP table memory at [mem 0x5afea000-0x5afea0c7]
[    1.019836] ACPI: Reserving SSDT table memory at [mem 0x5afe9000-0x5afe90e4]
[    1.019837] ACPI: Reserving IVRS table memory at [mem 0x5afb7000-0x5afb71a3]
[    1.019837] ACPI: Reserving SSDT table memory at [mem 0x5afb6000-0x5afb6746]
[    1.019838] ACPI: Reserving SSDT table memory at [mem 0x5afb5000-0x5afb5c87]
[    1.019838] ACPI: Reserving SSDT table memory at [mem 0x5afb4000-0x5afb4056]
[    1.019839] ACPI: Reserving SSDT table memory at [mem 0x5afb2000-0x5afb370a]
[    1.019839] ACPI: Reserving SSDT table memory at [mem 0x5afb1000-0x5afb1ff6]
[    1.019840] ACPI: Reserving SSDT table memory at [mem 0x5afa7000-0x5afb07e2]
[    1.019840] ACPI: Reserving SSDT table memory at [mem 0x5afa2000-0x5afa6fea]
[    1.019841] ACPI: Reserving SSDT table memory at [mem 0x5afa1000-0x5afa1c7e]
[    1.019841] ACPI: Reserving SSDT table memory at [mem 0x5afa0000-0x5afa0955]
[    1.019841] ACPI: Reserving SSDT table memory at [mem 0x5af9f000-0x5af9f08c]
[    1.019842] ACPI: Reserving SSDT table memory at [mem 0x5afcd000-0x5afcdeac]
[    1.019908] APIC: Switched APIC routing to: Xen PV
[    1.106226] Zone ranges:
[    1.106228]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    1.106229]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    1.106230]   Normal   [mem 0x0000000100000000-0x000000107e2fffff]
[    1.106231]   Device   empty
[    1.106232] Movable zone start for each node
[    1.106233] Early memory node ranges
[    1.106233]   node   0: [mem 0x0000000000001000-0x000000000007ffff]
[    1.106234]   node   0: [mem 0x0000000000100000-0x0000000009afffff]
[    1.106235]   node   0: [mem 0x0000000009e00000-0x0000000009efffff]
[    1.106235]   node   0: [mem 0x0000000009f3c000-0x000000004235ffff]
[    1.106236]   node   0: [mem 0x0000000044560000-0x0000000044568fff]
[    1.106236]   node   0: [mem 0x000000004456d000-0x000000004456efff]
[    1.106237]   node   0: [mem 0x0000000044570000-0x000000005077efff]
[    1.106237]   node   0: [mem 0x000000005afff000-0x000000005affffff]
[    1.106237]   node   0: [mem 0x0000000100000000-0x000000107e2fffff]
[    1.106241] Initmem setup node 0 [mem 0x0000000000001000-0x000000107e2fffff]
[    1.106246] On node 0, zone DMA: 1 pages in unavailable ranges
[    1.106259] On node 0, zone DMA: 128 pages in unavailable ranges
[    1.106358] On node 0, zone DMA32: 768 pages in unavailable ranges
[    1.106970] On node 0, zone DMA32: 60 pages in unavailable ranges
[    1.106997] On node 0, zone DMA32: 8704 pages in unavailable ranges
[    1.106998] On node 0, zone DMA32: 4 pages in unavailable ranges
[    1.107139] On node 0, zone DMA32: 1 pages in unavailable ranges
[    1.107264] On node 0, zone DMA32: 43136 pages in unavailable ranges
[    1.143155] On node 0, zone Normal: 20480 pages in unavailable ranges
[    1.143177] On node 0, zone Normal: 7424 pages in unavailable ranges
[    1.143179] p2m virtual area at (____ptrval____), size is 40000000
[    1.453003] Remapped 728641 page(s)
[    1.453502] ACPI: PM-Timer IO Port: 0x408
[    1.453552] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    1.453554] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    1.453556] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    1.453557] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    1.453559] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[    1.453560] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
[    1.453561] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
[    1.453563] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
[    1.453564] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
[    1.453565] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
[    1.453567] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
[    1.453568] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
[    1.453569] ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
[    1.453571] ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
[    1.453572] ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
[    1.453573] ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
[    1.453602] IOAPIC[0]: apic_id 33, version 33, address 0xfec00000, GSI 0-23
[    1.453609] IOAPIC[1]: apic_id 34, version 33, address 0xfec01000, GSI 24-55
[    1.453620] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    1.453622] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[    1.453648] ACPI: Using ACPI (MADT) for SMP configuration information
[    1.453650] ACPI: HPET id: 0x10228210 base: 0xfed00000
[    1.454105] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
[    1.454121] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    1.454123] PM: hibernation: Registered nosave memory: [mem 0x00080000-0x000fffff]
[    1.454124] PM: hibernation: Registered nosave memory: [mem 0x09b00000-0x09dfffff]
[    1.454125] PM: hibernation: Registered nosave memory: [mem 0x09f00000-0x09f3bfff]
[    1.454126] PM: hibernation: Registered nosave memory: [mem 0x42360000-0x4455ffff]
[    1.454127] PM: hibernation: Registered nosave memory: [mem 0x44569000-0x4456cfff]
[    1.454128] PM: hibernation: Registered nosave memory: [mem 0x4456f000-0x4456ffff]
[    1.454129] PM: hibernation: Registered nosave memory: [mem 0x5077f000-0x52f7efff]
[    1.454129] PM: hibernation: Registered nosave memory: [mem 0x52f7f000-0x5af7efff]
[    1.454129] PM: hibernation: Registered nosave memory: [mem 0x5af7f000-0x5affefff]
[    1.454130] PM: hibernation: Registered nosave memory: [mem 0x5b000000-0x5bffffff]
[    1.454131] PM: hibernation: Registered nosave memory: [mem 0x5c000000-0x5d78ffff]
[    1.454131] PM: hibernation: Registered nosave memory: [mem 0x5d790000-0x5d7effff]
[    1.454132] PM: hibernation: Registered nosave memory: [mem 0x5d7f0000-0x5d7f4fff]
[    1.454132] PM: hibernation: Registered nosave memory: [mem 0x5d7f5000-0x5fffffff]
[    1.454133] PM: hibernation: Registered nosave memory: [mem 0x60000000-0xc01fffff]
[    1.454133] PM: hibernation: Registered nosave memory: [mem 0xc0200000-0xc0203fff]
[    1.454133] PM: hibernation: Registered nosave memory: [mem 0xc0204000-0xc02fffff]
[    1.454134] PM: hibernation: Registered nosave memory: [mem 0xc0300000-0xc03fffff]
[    1.454134] PM: hibernation: Registered nosave memory: [mem 0xc0400000-0xfebfffff]
[    1.454135] PM: hibernation: Registered nosave memory: [mem 0xfec00000-0xfec01fff]
[    1.454135] PM: hibernation: Registered nosave memory: [mem 0xfec02000-0xfed7ffff]
[    1.454135] PM: hibernation: Registered nosave memory: [mem 0xfed80000-0xfed80fff]
[    1.454136] PM: hibernation: Registered nosave memory: [mem 0xfed81000-0xfedfffff]
[    1.454136] PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfeefffff]
[    1.454137] PM: hibernation: Registered nosave memory: [mem 0xfef00000-0xfeffffff]
[    1.454137] PM: hibernation: Registered nosave memory: [mem 0xff000000-0xffffffff]
[    1.454138] [mem 0x60000000-0xc01fffff] available for PCI devices
[    1.454140] Booting kernel on Xen
[    1.454141] Xen version: 4.17.3-pre (preserve-AD)
[    1.454143] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[    1.457783] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:16 nr_cpu_ids:16 nr_node_ids:1
[    1.458074] percpu: Embedded 64 pages/cpu s225280 r8192 d28672 u262144
[    1.458078] pcpu-alloc: s225280 r8192 d28672 u262144 alloc=1*2097152
[    1.458080] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15 
[    1.458119] xen: PV spinlocks enabled
[    1.458120] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes, linear)
[    1.458122] Kernel command line: placeholder root=UUID=71b1dc59-ea00-484c-b5e4-ee77ede771db ro "dyndbg=file drivers/gpio/* +p; file drivers/pinctrl/* +p; file arch/x86/pci/xen.c +p"
[    1.458165] Unknown kernel command line parameters "placeholder", will be passed to user space.
[    1.458374] random: crng init done
[    1.461263] Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes, linear)
[    1.462766] Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
[    1.462975] Built 1 zonelists, mobility grouping on.  Total pages: 16306586
[    1.463087] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
[    1.463090] software IO TLB: area num 16.
[    1.549382] Memory: 63582808K/66261752K available (18432K kernel code, 3168K rwdata, 14456K rodata, 3944K init, 3704K bss, 2678692K reserved, 0K cma-reserved)
[    1.549636] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
[    1.549958] ftrace: allocating 53307 entries in 209 pages
[    1.556926] ftrace: allocated 209 pages with 4 groups
[    1.557498] Dynamic Preempt: voluntary
[    1.557592] rcu: Preemptible hierarchical RCU implementation.
[    1.557593] rcu: 	RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=16.
[    1.557593] 	Trampoline variant of Tasks RCU enabled.
[    1.557594] 	Rude variant of Tasks RCU enabled.
[    1.557594] 	Tracing variant of Tasks RCU enabled.
[    1.557595] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[    1.557595] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=16
[    1.560692] NR_IRQS: 524544, nr_irqs: 1096, preallocated irqs: 16
[    1.560760] xen:events: Using FIFO-based ABI
[    1.560762] xen_register_pirq: before xen_irq_from_gsi: gsi 1 triggering 1 set_pirq 1
[    1.560766] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 1 triggering 1 shareable 0 name ioapic-edge
[    1.560770] xen_register_pirq: xen: --> pirq=1 -> irq=1 (gsi=1)
[    1.560771] xen_register_pirq: before xen_irq_from_gsi: gsi 2 triggering 1 set_pirq 1
[    1.560771] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 2 triggering 1 shareable 0 name ioapic-edge
[    1.560773] xen_register_pirq: xen: --> pirq=2 -> irq=2 (gsi=2)
[    1.560773] xen_register_pirq: before xen_irq_from_gsi: gsi 3 triggering 1 set_pirq 1
[    1.560774] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 3 triggering 1 shareable 0 name ioapic-edge
[    1.560775] xen_register_pirq: xen: --> pirq=3 -> irq=3 (gsi=3)
[    1.560776] xen_register_pirq: before xen_irq_from_gsi: gsi 4 triggering 1 set_pirq 1
[    1.560777] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 4 triggering 1 shareable 0 name ioapic-edge
[    1.560778] xen_register_pirq: xen: --> pirq=4 -> irq=4 (gsi=4)
[    1.560778] xen_register_pirq: before xen_irq_from_gsi: gsi 5 triggering 1 set_pirq 1
[    1.560779] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 5 triggering 1 shareable 0 name ioapic-edge
[    1.560780] xen_register_pirq: xen: --> pirq=5 -> irq=5 (gsi=5)
[    1.560780] xen_register_pirq: before xen_irq_from_gsi: gsi 6 triggering 1 set_pirq 1
[    1.560781] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 6 triggering 1 shareable 0 name ioapic-edge
[    1.560782] xen_register_pirq: xen: --> pirq=6 -> irq=6 (gsi=6)
[    1.560783] xen_register_pirq: before xen_irq_from_gsi: gsi 7 triggering 1 set_pirq 1
[    1.560784] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 7 triggering 1 shareable 0 name ioapic-edge
[    1.560785] xen_register_pirq: xen: --> pirq=7 -> irq=7 (gsi=7)
[    1.560785] xen_register_pirq: before xen_irq_from_gsi: gsi 8 triggering 1 set_pirq 1
[    1.560786] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 8 triggering 1 shareable 0 name ioapic-edge
[    1.560787] xen_register_pirq: xen: --> pirq=8 -> irq=8 (gsi=8)
[    1.560788] xen_register_pirq: before xen_irq_from_gsi: gsi 9 triggering 0 set_pirq 1
[    1.560789] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 9 triggering 0 shareable 1 name ioapic-level
[    1.560790] xen_register_pirq: xen: --> pirq=9 -> irq=9 (gsi=9)
[    1.560790] xen_register_pirq: before xen_irq_from_gsi: gsi 10 triggering 1 set_pirq 1
[    1.560791] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 10 triggering 1 shareable 0 name ioapic-edge
[    1.560792] xen_register_pirq: xen: --> pirq=10 -> irq=10 (gsi=10)
[    1.560793] xen_register_pirq: before xen_irq_from_gsi: gsi 11 triggering 1 set_pirq 1
[    1.560794] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 11 triggering 1 shareable 0 name ioapic-edge
[    1.560795] xen_register_pirq: xen: --> pirq=11 -> irq=11 (gsi=11)
[    1.560795] xen_register_pirq: before xen_irq_from_gsi: gsi 12 triggering 1 set_pirq 1
[    1.560796] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 12 triggering 1 shareable 0 name ioapic-edge
[    1.560797] xen_register_pirq: xen: --> pirq=12 -> irq=12 (gsi=12)
[    1.560798] xen_register_pirq: before xen_irq_from_gsi: gsi 13 triggering 1 set_pirq 1
[    1.560798] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 13 triggering 1 shareable 0 name ioapic-edge
[    1.560800] xen_register_pirq: xen: --> pirq=13 -> irq=13 (gsi=13)
[    1.560800] xen_register_pirq: before xen_irq_from_gsi: gsi 14 triggering 1 set_pirq 1
[    1.560801] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 14 triggering 1 shareable 0 name ioapic-edge
[    1.560802] xen_register_pirq: xen: --> pirq=14 -> irq=14 (gsi=14)
[    1.560802] xen_register_pirq: before xen_irq_from_gsi: gsi 15 triggering 1 set_pirq 1
[    1.560803] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 15 triggering 1 shareable 0 name ioapic-edge
[    1.560805] xen_register_pirq: xen: --> pirq=15 -> irq=15 (gsi=15)
[    1.560810] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    1.561038] kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval____)-0x(____ptrval____)
[    1.561072] Console: colour dummy device 80x25
[    1.561074] printk: console [tty0] enabled
[    1.561359] printk: console [hvc0] enabled
[    1.561645] ACPI: Core revision 20230628
[    1.585170] ACPI BIOS Warning (bug): Incorrect checksum in table [BGRT] - 0x70, should be 0xFFFFFFFB (20230628/utcksum-58)
[    1.595525] clocksource: xen: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
[    1.595531] Xen: using vcpuop timer interface
[    1.595532] installing Xen timer for CPU 0
[    1.595611] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x2f7a7a7f221, max_idle_ns: 440795289726 ns
[    1.595616] Calibrating delay loop (skipped), value calculated using timer frequency.. 6587.63 BogoMIPS (lpj=3293816)
[    1.595648] Last level iTLB entries: 4KB 512, 2MB 512, 4MB 256
[    1.595650] Last level dTLB entries: 4KB 2048, 2MB 2048, 4MB 1024, 1GB 0
[    1.595655] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    1.595659] Spectre V2 : Mitigation: Retpolines
[    1.595661] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    1.595664] Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT
[    1.595667] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    1.595670] Speculative Store Bypass: Vulnerable
[    1.595673] Speculative Return Stack Overflow: IBPB-extending microcode not applied!
[    1.595675] Speculative Return Stack Overflow: WARNING: See https://kernel.org/doc/html/latest/admin-guide/hw-vuln/srso.html for mitigation options.
[    1.595676] Speculative Return Stack Overflow: Vulnerable: Safe RET, no microcode
[    1.595691] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    1.595694] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    1.595696] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    1.595699] x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
[    1.595701] x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
[    1.595703] x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
[    1.595706] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    1.595708] x86/fpu: xstate_offset[5]:  832, xstate_sizes[5]:   64
[    1.595711] x86/fpu: xstate_offset[6]:  896, xstate_sizes[6]:  512
[    1.595713] x86/fpu: xstate_offset[7]: 1408, xstate_sizes[7]: 1024
[    1.595715] x86/fpu: Enabled xstate features 0xe7, context size is 2432 bytes, using 'compacted' format.
[    1.606999] Freeing SMP alternatives memory: 48K
[    1.607008] pid_max: default: 32768 minimum: 301
[    1.607061] LSM: initializing lsm=lockdown,capability,yama,selinux,bpf,landlock,integrity
[    1.607087] Yama: becoming mindful.
[    1.607092] SELinux:  Initializing.
[    1.607147] LSM support for eBPF active
[    1.607152] landlock: Up and running.
[    1.607209] Mount-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    1.607255] Mountpoint-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    1.607673] cpu 0 spinlock event irq 57
[    1.607686] VPMU disabled by hypervisor.
[    1.607924] RCU Tasks: Setting shift to 4 and lim to 1 rcu_task_cb_adjust=1.
[    1.607959] RCU Tasks Rude: Setting shift to 4 and lim to 1 rcu_task_cb_adjust=1.
[    1.607985] RCU Tasks Trace: Setting shift to 4 and lim to 1 rcu_task_cb_adjust=1.
[    1.608011] Performance Events: PMU not available due to virtualization, using software events only.
[    1.608022] signal: max sigframe size: 3376
[    1.608055] rcu: Hierarchical SRCU implementation.
[    1.608059] rcu: 	Max phase no-delay instances is 400.
[    1.612802] NMI watchdog: Perf NMI watchdog permanently disabled
[    1.613162] smp: Bringing up secondary CPUs ...
[    1.613408] installing Xen timer for CPU 1
[    1.613763] installing Xen timer for CPU 2
[    1.613967] installing Xen timer for CPU 3
[    1.614163] installing Xen timer for CPU 4
[    1.614356] installing Xen timer for CPU 5
[    1.614545] installing Xen timer for CPU 6
[    1.614743] installing Xen timer for CPU 7
[    1.614931] installing Xen timer for CPU 8
[    1.615101] installing Xen timer for CPU 9
[    1.615265] installing Xen timer for CPU 10
[    1.615434] installing Xen timer for CPU 11
[    1.615608] installing Xen timer for CPU 12
[    1.615798] installing Xen timer for CPU 13
[    1.615973] installing Xen timer for CPU 14
[    1.616148] installing Xen timer for CPU 15
[    1.616198] cpu 1 spinlock event irq 137
[    1.616198] cpu 2 spinlock event irq 138
[    1.616198] cpu 3 spinlock event irq 139
[    1.616628] cpu 4 spinlock event irq 140
[    1.616673] cpu 5 spinlock event irq 141
[    1.616682] cpu 6 spinlock event irq 142
[    1.616682] cpu 7 spinlock event irq 143
[    1.616682] cpu 8 spinlock event irq 144
[    1.616682] cpu 9 spinlock event irq 145
[    1.616682] cpu 10 spinlock event irq 146
[    1.616682] cpu 11 spinlock event irq 147
[    1.616682] cpu 12 spinlock event irq 148
[    1.616682] cpu 13 spinlock event irq 149
[    1.617665] cpu 14 spinlock event irq 150
[    1.617672] cpu 15 spinlock event irq 151
[    1.617719] smp: Brought up 1 node, 16 CPUs
[    1.617724] smpboot: Max logical packages: 1
[    1.618894] devtmpfs: initialized
[    1.618894] x86/mm: Memory block size: 128MB
[    1.623794] ACPI: PM: Registering ACPI NVS region [mem 0x09f00000-0x09f3bfff] (245760 bytes)
[    1.623794] ACPI: PM: Registering ACPI NVS region [mem 0x52f7f000-0x5af7efff] (134217728 bytes)
[    1.625907] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[    1.625917] futex hash table entries: 4096 (order: 6, 262144 bytes, linear)
[    1.626001] pinctrl core: initialized pinctrl subsystem
[    1.626141] PM: RTC time: 16:20:49, date: 2023-12-20
[    1.627064] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    1.627088] xen:grant_table: Grant tables using version 1 layout
[    1.627102] Grant table initialized
[    1.627541] DMA: preallocated 4096 KiB GFP_KERNEL pool for atomic allocations
[    1.627550] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    1.627558] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    1.627582] audit: initializing netlink subsys (disabled)
[    1.627624] audit: type=2000 audit(1703089248.098:1): state=initialized audit_enabled=0 res=1
[    1.627686] thermal_sys: Registered thermal governor 'fair_share'
[    1.627686] thermal_sys: Registered thermal governor 'bang_bang'
[    1.627692] thermal_sys: Registered thermal governor 'step_wise'
[    1.627696] thermal_sys: Registered thermal governor 'user_space'
[    1.627748] Simple Boot Flag at 0x44 set to 0x80
[    1.627748] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    1.627925] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    1.627935] PCI: not using MMCONFIG
[    1.627941] PCI: Using configuration type 1 for base access
[    1.627946] PCI: Using configuration type 1 for extended access
[    1.629143] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
[    1.633735] cryptd: max_cpu_qlen set to 1000
[    1.634693] raid6: skipped pq benchmark and selected avx512x4
[    1.634707] raid6: using avx512x2 recovery algorithm
[    1.634806] fbcon: Taking over console
[    1.634866] ACPI: Added _OSI(Module Device)
[    1.634877] ACPI: Added _OSI(Processor Device)
[    1.634886] ACPI: Added _OSI(3.0 _SCP Extensions)
[    1.634896] ACPI: Added _OSI(Processor Aggregator Device)
[    1.666629] ACPI: 26 ACPI AML tables successfully acquired and loaded
[    1.668915] xen_register_gsi: xen: registering gsi 9 triggering 0 polarity 1
[    1.668917] xen_register_pirq: before xen_irq_from_gsi: gsi 9 triggering 0 set_pirq 1
[    1.668919] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 9, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.695059] ACPI: USB4 _OSC: OS supports USB3+ DisplayPort+ PCIe+ XDomain+
[    1.695067] ACPI: USB4 _OSC: OS controls USB3+ DisplayPort+ PCIe+ XDomain+
[    1.695189] ACPI: _OSC evaluation for CPUs failed, trying _PDC
[    1.695979] ACPI: EC: EC started
[    1.695983] ACPI: EC: interrupt blocked
[    1.696129] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    1.696135] ACPI: \_SB_.PCI0.LPC0.EC0_: Boot DSDT EC used to handle transactions
[    1.696141] ACPI: Interpreter enabled
[    1.696158] ACPI: PM: (supports S0 S4 S5)
[    1.696163] ACPI: Using IOAPIC for interrupt routing
[    1.698529] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    1.704810] [Firmware Info]: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] not reserved in ACPI motherboard resources
[    1.704819] PCI: not using MMCONFIG
[    1.704825] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    1.704832] PCI: Ignoring E820 reservations for host bridge windows
[    1.705439] ACPI: Enabled 3 GPEs in block 00 to 1F
[    1.709862] ACPI: \_SB_.PCI0.GPP8.P0NV: New power resource
[    1.713149] ACPI: \_SB_.PCI0.GP11.PWRS: New power resource
[    1.715479] ACPI: \_SB_.PCI0.GP11.SWUS.PWRS: New power resource
[    1.717897] ACPI: \_SB_.PCI0.GP12.PWRS: New power resource
[    1.720247] ACPI: \_SB_.PCI0.GP12.SWUS.PWRS: New power resource
[    1.720710] ACPI: \_SB_.PCI0.GP17.PWRS: New power resource
[    1.721175] ACPI: \_SB_.PCI0.GP17.VGA_.PWRS: New power resource
[    1.721763] ACPI: \_SB_.PCI0.GP17.ACP_.PWRS: New power resource
[    1.722857] ACPI: \_SB_.PCI0.GP17.AZAL.PWRS: New power resource
[    1.723687] ACPI: \_SB_.PCI0.GP17.HDAU.PWRS: New power resource
[    1.724407] ACPI: \_SB_.PCI0.GP17.XHC0.PWRS: New power resource
[    1.729407] ACPI: \_SB_.PCI0.GP17.XHC1.PWRS: New power resource
[    1.732466] ACPI: \_SB_.PCI0.GP19.XHC2.PWRS: New power resource
[    1.735011] ACPI: \_SB_.PCI0.GP19.NHI0.PWRS: New power resource
[    1.736491] ACPI: \_SB_.PCI0.GP19.XHC3.PWRS: New power resource
[    1.739118] ACPI: \_SB_.PCI0.GP19.NHI1.PWRS: New power resource
[    1.740591] ACPI: \_SB_.PCI0.GP19.XHC4.PWRS: New power resource
[    1.751261] ACPI: \_SB_.PRWL: New power resource
[    1.751301] ACPI: \_SB_.PRWB: New power resource
[    1.752938] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    1.752948] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
[    1.753273] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug AER]
[    1.753889] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME PCIeCapability LTR DPC]
[    1.754646] PCI host bridge to bus 0000:00
[    1.754651] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    1.754657] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    1.754663] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    1.754669] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000cffff window]
[    1.754676] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000effff window]
[    1.754682] pci_bus 0000:00: root bus resource [mem 0x60000000-0x90bfffff window]
[    1.754687] pci_bus 0000:00: root bus resource [mem 0xf0000000-0xfec00000 window]
[    1.754695] pci_bus 0000:00: root bus resource [mem 0xfed45000-0xfed814ff window]
[    1.754701] pci_bus 0000:00: root bus resource [mem 0xfed81900-0xfed81fff window]
[    1.754706] pci_bus 0000:00: root bus resource [mem 0xfedc0000-0xfedc0fff window]
[    1.754712] pci_bus 0000:00: root bus resource [mem 0xfedc6000-0xfedc6fff window]
[    1.754718] pci_bus 0000:00: root bus resource [mem 0x10c0200000-0x891fffffff window]
[    1.754724] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.754766] pci 0000:00:00.0: [1022:14e8] type 00 class 0x060000
[    1.754884] pci 0000:00:00.2: [1022:14e9] type 00 class 0x080600
[    1.755044] pci 0000:00:01.0: [1022:14ea] type 00 class 0x060000
[    1.755165] pci 0000:00:02.0: [1022:14ea] type 00 class 0x060000
[    1.755287] pci 0000:00:02.2: [1022:14ee] type 01 class 0x060400
[    1.755401] pci 0000:00:02.2: PME# supported from D0 D3hot D3cold
[    1.755549] pci 0000:00:02.4: [1022:14ee] type 01 class 0x060400
[    1.755664] pci 0000:00:02.4: PME# supported from D0 D3hot D3cold
[    1.755788] pci 0000:00:03.0: [1022:14ea] type 00 class 0x060000
[    1.755914] pci 0000:00:03.1: [1022:14ef] type 01 class 0x060400
[    1.756509] pci 0000:00:03.1: PME# supported from D0 D3hot D3cold
[    1.758315] pci 0000:00:04.0: [1022:14ea] type 00 class 0x060000
[    1.758439] pci 0000:00:04.1: [1022:14ef] type 01 class 0x060400
[    1.759031] pci 0000:00:04.1: PME# supported from D0 D3hot D3cold
[    1.760826] pci 0000:00:08.0: [1022:14ea] type 00 class 0x060000
[    1.760938] pci 0000:00:08.1: [1022:14eb] type 01 class 0x060400
[    1.760992] pci 0000:00:08.1: enabling Extended Tags
[    1.761045] pci 0000:00:08.1: PME# supported from D0 D3hot D3cold
[    1.761206] pci 0000:00:08.2: [1022:14eb] type 01 class 0x060400
[    1.761290] pci 0000:00:08.2: enabling Extended Tags
[    1.761342] pci 0000:00:08.2: PME# supported from D0 D3hot D3cold
[    1.761459] pci 0000:00:08.3: [1022:14eb] type 01 class 0x060400
[    1.761510] pci 0000:00:08.3: enabling Extended Tags
[    1.761565] pci 0000:00:08.3: PME# supported from D0 D3hot D3cold
[    1.761934] pci 0000:00:14.0: [1022:790b] type 00 class 0x0c0500
[    1.762134] pci 0000:00:14.3: [1022:790e] type 00 class 0x060100
[    1.762368] pci 0000:00:18.0: [1022:14f0] type 00 class 0x060000
[    1.762452] pci 0000:00:18.1: [1022:14f1] type 00 class 0x060000
[    1.762536] pci 0000:00:18.2: [1022:14f2] type 00 class 0x060000
[    1.762620] pci 0000:00:18.3: [1022:14f3] type 00 class 0x060000
[    1.762704] pci 0000:00:18.4: [1022:14f4] type 00 class 0x060000
[    1.762790] pci 0000:00:18.5: [1022:14f5] type 00 class 0x060000
[    1.762873] pci 0000:00:18.6: [1022:14f6] type 00 class 0x060000
[    1.762959] pci 0000:00:18.7: [1022:14f7] type 00 class 0x060000
[    1.763167] pci 0000:01:00.0: [14c3:0616] type 00 class 0x028000
[    1.763200] pci 0000:01:00.0: reg 0x10: [mem 0x8810900000-0x88109fffff 64bit pref]
[    1.763224] pci 0000:01:00.0: reg 0x18: [mem 0x90b00000-0x90b07fff 64bit]
[    1.763334] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[    1.763464] pci 0000:00:02.2: PCI bridge to [bus 01]
[    1.763476] pci 0000:00:02.2:   bridge window [mem 0x90b00000-0x90bfffff]
[    1.763487] pci 0000:00:02.2:   bridge window [mem 0x8810900000-0x88109fffff 64bit pref]
[    1.763662] pci 0000:02:00.0: [15b7:5030] type 00 class 0x010802
[    1.763693] pci 0000:02:00.0: reg 0x10: [mem 0x90a00000-0x90a03fff 64bit]
[    1.763935] pci 0000:00:02.4: PCI bridge to [bus 02]
[    1.763947] pci 0000:00:02.4:   bridge window [mem 0x90a00000-0x90afffff]
[    1.764107] pci 0000:00:03.1: PCI bridge to [bus 03-61]
[    1.764118] pci 0000:00:03.1:   bridge window [io  0x6000-0x9fff]
[    1.764126] pci 0000:00:03.1:   bridge window [mem 0x78000000-0x8fffffff]
[    1.764138] pci 0000:00:03.1:   bridge window [mem 0x7800000000-0x87ffffffff 64bit pref]
[    1.764296] pci 0000:00:04.1: PCI bridge to [bus 62-c0]
[    1.764308] pci 0000:00:04.1:   bridge window [io  0x2000-0x5fff]
[    1.764316] pci 0000:00:04.1:   bridge window [mem 0x60000000-0x77ffffff]
[    1.764328] pci 0000:00:04.1:   bridge window [mem 0x6800000000-0x77ffffffff 64bit pref]
[    1.764495] pci 0000:c1:00.0: [1002:15bf] type 00 class 0x030000
[    1.764522] pci 0000:c1:00.0: reg 0x10: [mem 0x8800000000-0x880fffffff 64bit pref]
[    1.764542] pci 0000:c1:00.0: reg 0x18: [mem 0x90000000-0x901fffff 64bit pref]
[    1.764557] pci 0000:c1:00.0: reg 0x20: [io  0x1000-0x10ff]
[    1.764571] pci 0000:c1:00.0: reg 0x24: [mem 0x90500000-0x9057ffff]
[    1.764593] pci 0000:c1:00.0: enabling Extended Tags
[    1.764617] pci 0000:c1:00.0: BAR 0: assigned to efifb
[    1.764673] pci 0000:c1:00.0: PME# supported from D1 D2 D3hot D3cold
[    1.764830] pci 0000:c1:00.1: [1002:1640] type 00 class 0x040300
[    1.764849] pci 0000:c1:00.1: reg 0x10: [mem 0x905c8000-0x905cbfff]
[    1.764899] pci 0000:c1:00.1: enabling Extended Tags
[    1.764958] pci 0000:c1:00.1: PME# supported from D1 D2 D3hot D3cold
[    1.765088] pci 0000:c1:00.2: [1022:15c7] type 00 class 0x108000
[    1.765120] pci 0000:c1:00.2: reg 0x18: [mem 0x90400000-0x904fffff]
[    1.765144] pci 0000:c1:00.2: reg 0x24: [mem 0x905cc000-0x905cdfff]
[    1.765163] pci 0000:c1:00.2: enabling Extended Tags
[    1.765353] pci 0000:c1:00.3: [1022:15b9] type 00 class 0x0c0330
[    1.765380] pci 0000:c1:00.3: reg 0x10: [mem 0x90200000-0x902fffff 64bit]
[    1.765437] pci 0000:c1:00.3: enabling Extended Tags
[    1.765510] pci 0000:c1:00.3: PME# supported from D0 D3hot D3cold
[    1.766086] pci 0000:c1:00.4: [1022:15ba] type 00 class 0x0c0330
[    1.766113] pci 0000:c1:00.4: reg 0x10: [mem 0x90300000-0x903fffff 64bit]
[    1.766173] pci 0000:c1:00.4: enabling Extended Tags
[    1.766244] pci 0000:c1:00.4: PME# supported from D0 D3hot D3cold
[    1.766804] pci 0000:c1:00.5: [1022:15e2] type 00 class 0x048000
[    1.766825] pci 0000:c1:00.5: reg 0x10: [mem 0x90580000-0x905bffff]
[    1.766848] pci 0000:c1:00.5: reg 0x18: [mem 0x8810000000-0x88107fffff 64bit pref]
[    1.766880] pci 0000:c1:00.5: enabling Extended Tags
[    1.766939] pci 0000:c1:00.5: PME# supported from D0 D3hot D3cold
[    1.767078] pci 0000:c1:00.6: [1022:15e3] type 00 class 0x040300
[    1.767097] pci 0000:c1:00.6: reg 0x10: [mem 0x905c0000-0x905c7fff]
[    1.767147] pci 0000:c1:00.6: enabling Extended Tags
[    1.767206] pci 0000:c1:00.6: PME# supported from D0 D3hot D3cold
[    1.767407] pci 0000:00:08.1: PCI bridge to [bus c1]
[    1.767417] pci 0000:00:08.1:   bridge window [io  0x1000-0x1fff]
[    1.767424] pci 0000:00:08.1:   bridge window [mem 0x90000000-0x905fffff]
[    1.767434] pci 0000:00:08.1:   bridge window [mem 0x8800000000-0x88107fffff 64bit pref]
[    1.767532] pci 0000:c2:00.0: [1022:14ec] type 00 class 0x130000
[    1.767597] pci 0000:c2:00.0: enabling Extended Tags
[    1.767660] pci 0000:c2:00.0: PME# supported from D3hot D3cold
[    1.767769] pci 0000:c2:00.1: [1022:1502] type 00 class 0x118000
[    1.767796] pci 0000:c2:00.1: reg 0x10: [mem 0x90900000-0x9097ffff]
[    1.767808] pci 0000:c2:00.1: reg 0x14: [mem 0x909c0000-0x909c1fff]
[    1.767824] pci 0000:c2:00.1: reg 0x18: [mem 0x8810800000-0x881083ffff 64bit pref]
[    1.767837] pci 0000:c2:00.1: reg 0x20: [mem 0x90980000-0x909bffff]
[    1.767862] pci 0000:c2:00.1: enabling Extended Tags
[    1.768066] pci 0000:00:08.2: PCI bridge to [bus c2]
[    1.768077] pci 0000:00:08.2:   bridge window [mem 0x90900000-0x909fffff]
[    1.768088] pci 0000:00:08.2:   bridge window [mem 0x8810800000-0x88108fffff 64bit pref]
[    1.768218] pci 0000:c3:00.0: [1022:14ec] type 00 class 0x130000
[    1.768280] pci 0000:c3:00.0: enabling Extended Tags
[    1.768885] pci 0000:c3:00.3: [1022:15c0] type 00 class 0x0c0330
[    1.768912] pci 0000:c3:00.3: reg 0x10: [mem 0x90600000-0x906fffff 64bit]
[    1.768969] pci 0000:c3:00.3: enabling Extended Tags
[    1.769042] pci 0000:c3:00.3: PME# supported from D0 D3hot D3cold
[    1.769598] pci 0000:c3:00.4: [1022:15c1] type 00 class 0x0c0330
[    1.769626] pci 0000:c3:00.4: reg 0x10: [mem 0x90700000-0x907fffff 64bit]
[    1.769683] pci 0000:c3:00.4: enabling Extended Tags
[    1.769754] pci 0000:c3:00.4: PME# supported from D0 D3hot D3cold
[    1.770312] pci 0000:c3:00.5: [1022:1668] type 00 class 0x0c0340
[    1.770338] pci 0000:c3:00.5: reg 0x10: [mem 0x90800000-0x9087ffff 64bit]
[    1.770402] pci 0000:c3:00.5: Max Payload Size set to 128 (was 256, max 256)
[    1.770411] pci 0000:c3:00.5: enabling Extended Tags
[    1.770482] pci 0000:c3:00.5: PME# supported from D0 D3hot D3cold
[    1.770620] pci 0000:c3:00.6: [1022:1669] type 00 class 0x0c0340
[    1.770646] pci 0000:c3:00.6: reg 0x10: [mem 0x90880000-0x908fffff 64bit]
[    1.770711] pci 0000:c3:00.6: Max Payload Size set to 128 (was 256, max 256)
[    1.770720] pci 0000:c3:00.6: enabling Extended Tags
[    1.770790] pci 0000:c3:00.6: PME# supported from D0 D3hot D3cold
[    1.770984] pci 0000:00:08.3: PCI bridge to [bus c3]
[    1.770996] pci 0000:00:08.3:   bridge window [mem 0x90600000-0x908fffff]
[    1.771103] pci_bus 0000:00: on NUMA node 0
[    1.783231] xen_register_gsi: xen: registering gsi 8 triggering 1 polarity 0
[    1.783233] xen_register_pirq: before xen_irq_from_gsi: gsi 8 triggering 1 set_pirq 1
[    1.783234] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 8, setup_gsi.triggering: 0, setup_gsi.polarity: 0
[    1.783318] xen_register_gsi: xen: registering gsi 13 triggering 1 polarity 0
[    1.783319] xen_register_pirq: before xen_irq_from_gsi: gsi 13 triggering 1 set_pirq 1
[    1.783321] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 13, setup_gsi.triggering: 0, setup_gsi.polarity: 0
[    1.784231] ACPI: PCI: Interrupt link LNKA configured for IRQ 0
[    1.784237] ACPI: PCI: Interrupt link LNKA disabled
[    1.784592] ACPI: PCI: Interrupt link LNKB configured for IRQ 0
[    1.784597] ACPI: PCI: Interrupt link LNKB disabled
[    1.784922] ACPI: PCI: Interrupt link LNKC configured for IRQ 0
[    1.784927] ACPI: PCI: Interrupt link LNKC disabled
[    1.785282] ACPI: PCI: Interrupt link LNKD configured for IRQ 0
[    1.785287] ACPI: PCI: Interrupt link LNKD disabled
[    1.785631] ACPI: PCI: Interrupt link LNKE configured for IRQ 0
[    1.785636] ACPI: PCI: Interrupt link LNKE disabled
[    1.785914] ACPI: PCI: Interrupt link LNKF configured for IRQ 0
[    1.785919] ACPI: PCI: Interrupt link LNKF disabled
[    1.786200] ACPI: PCI: Interrupt link LNKG configured for IRQ 0
[    1.786205] ACPI: PCI: Interrupt link LNKG disabled
[    1.786487] ACPI: PCI: Interrupt link LNKH configured for IRQ 0
[    1.786492] ACPI: PCI: Interrupt link LNKH disabled
[    1.786652] xen_register_gsi: xen: registering gsi 7 triggering 0 polarity 1
[    1.786653] xen_register_pirq: before xen_irq_from_gsi: gsi 7 triggering 0 set_pirq 1
[    1.786654] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 7, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.787191] xen_register_gsi: xen: registering gsi 10 triggering 1 polarity 0
[    1.787192] xen_register_pirq: before xen_irq_from_gsi: gsi 10 triggering 1 set_pirq 1
[    1.787194] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 10, setup_gsi.triggering: 0, setup_gsi.polarity: 0
[    1.787516] xen_register_gsi: xen: registering gsi 6 triggering 1 polarity 0
[    1.787517] xen_register_pirq: before xen_irq_from_gsi: gsi 6 triggering 1 set_pirq 1
[    1.787518] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 6, setup_gsi.triggering: 0, setup_gsi.polarity: 0
[    1.788122] xen_register_gsi: xen: registering gsi 50 triggering 0 polarity 1
[    1.788124] xen_register_pirq: before xen_irq_from_gsi: gsi 50 triggering 0 set_pirq 1
[    1.788130] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 50 triggering 0 shareable 1 name ioapic-level
[    1.788142] xen_register_pirq: xen: --> pirq=50 -> irq=50 (gsi=50)
[    1.788143] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 50, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.788176] xen_register_gsi: xen: registering gsi 51 triggering 0 polarity 1
[    1.788177] xen_register_pirq: before xen_irq_from_gsi: gsi 51 triggering 0 set_pirq 1
[    1.788179] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 51 triggering 0 shareable 1 name ioapic-level
[    1.788187] xen_register_pirq: xen: --> pirq=51 -> irq=51 (gsi=51)
[    1.788188] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 51, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.788211] xen_register_gsi: xen: registering gsi 52 triggering 0 polarity 1
[    1.788212] xen_register_pirq: before xen_irq_from_gsi: gsi 52 triggering 0 set_pirq 1
[    1.788215] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 52 triggering 0 shareable 1 name ioapic-level
[    1.788225] xen_register_pirq: xen: --> pirq=52 -> irq=52 (gsi=52)
[    1.788226] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 52, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.788249] xen_register_gsi: xen: registering gsi 53 triggering 0 polarity 1
[    1.788250] xen_register_pirq: before xen_irq_from_gsi: gsi 53 triggering 0 set_pirq 1
[    1.788252] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 53 triggering 0 shareable 1 name ioapic-level
[    1.788259] xen_register_pirq: xen: --> pirq=53 -> irq=53 (gsi=53)
[    1.788261] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 53, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.794059] Low-power S0 idle used by default for system suspend
[    1.794208] ACPI: EC: interrupt unblocked
[    1.794212] ACPI: EC: event unblocked
[    1.794225] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    1.794230] ACPI: EC: GPE=0xb
[    1.794234] ACPI: \_SB_.PCI0.LPC0.EC0_: Boot DSDT EC initialization complete
[    1.794240] ACPI: \_SB_.PCI0.LPC0.EC0_: EC: Used to handle transactions and events
[    1.794269] xen:balloon: Initialising balloon driver
[    1.808656] iommu: Default domain type: Translated
[    1.808656] iommu: DMA domain TLB invalidation policy: lazy mode
[    1.808727] SCSI subsystem initialized
[    1.808741] libata version 3.00 loaded.
[    1.808741] ACPI: bus type USB registered
[    1.808741] usbcore: registered new interface driver usbfs
[    1.808741] usbcore: registered new interface driver hub
[    1.808741] usbcore: registered new device driver usb
[    1.820712] i2c_designware AMDI0010:00: using ACPI '\_SB.I2CA' for 'scl' GPIO lookup
[    1.820717] acpi AMDI0010:00: GPIO: looking up scl-gpios
[    1.820719] acpi AMDI0010:00: GPIO: looking up scl-gpio
[    1.820721] i2c_designware AMDI0010:00: using lookup tables for GPIO lookup
[    1.820722] i2c_designware AMDI0010:00: No GPIO consumer scl found
[    1.833755] i2c_designware AMDI0010:03: using ACPI '\_SB.I2CD' for 'scl' GPIO lookup
[    1.833759] acpi AMDI0010:03: GPIO: looking up scl-gpios
[    1.833761] acpi AMDI0010:03: GPIO: looking up scl-gpio
[    1.833762] i2c_designware AMDI0010:03: using lookup tables for GPIO lookup
[    1.833764] i2c_designware AMDI0010:03: No GPIO consumer scl found
[    1.835301] pps_core: LinuxPPS API ver. 1 registered
[    1.835307] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    1.835316] PTP clock support registered
[    1.835341] EDAC MC: Ver: 3.0.0
[    1.835746] efivars: Registered efivars operations
[    1.835831] NetLabel: Initializing
[    1.835837] NetLabel:  domain hash size = 128
[    1.835842] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    1.835861] NetLabel:  unlabeled traffic allowed by default
[    1.835869] mctp: management component transport protocol core
[    1.835874] NET: Registered PF_MCTP protocol family
[    1.835881] PCI: Using ACPI for IRQ routing
[    1.835885] PCI: pci_cache_line_size set to 64 bytes
[    1.836006] resource: Expanded resource Reserved due to conflict with PCI Bus 0000:00
[    1.836012] e820: reserve RAM buffer [mem 0x09b00000-0x0bffffff]
[    1.836015] e820: reserve RAM buffer [mem 0x09f00000-0x0bffffff]
[    1.836016] e820: reserve RAM buffer [mem 0x42360000-0x43ffffff]
[    1.836017] e820: reserve RAM buffer [mem 0x44569000-0x47ffffff]
[    1.836018] e820: reserve RAM buffer [mem 0x4456f000-0x47ffffff]
[    1.836019] e820: reserve RAM buffer [mem 0x5077f000-0x53ffffff]
[    1.836020] e820: reserve RAM buffer [mem 0x5b000000-0x5bffffff]
[    1.836022] e820: reserve RAM buffer [mem 0x107e300000-0x107fffffff]
[    1.836040] pci 0000:c1:00.0: vgaarb: setting as boot VGA device
[    1.836040] pci 0000:c1:00.0: vgaarb: bridge control possible
[    1.836040] pci 0000:c1:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
[    1.836040] vgaarb: loaded
[    1.836638] sysfb: VRAM smaller than advertised
[    1.836804] clocksource: Switched to clocksource tsc-early
[    1.840271] VFS: Disk quotas dquot_6.6.0
[    1.840286] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.840312] hugetlbfs: disabling because there are no supported hugepage sizes
[    1.840352] pnp: PnP ACPI init
[    1.840632] system 00:00: [mem 0xfec00000-0xfec01fff] could not be reserved
[    1.840652] system 00:00: [mem 0xfee00000-0xfee00fff] has been reserved
[    1.848189] system 00:02: [io  0x0400-0x04cf] has been reserved
[    1.848196] system 00:02: [io  0x04d0-0x04d1] has been reserved
[    1.848202] system 00:02: [io  0x04d6] has been reserved
[    1.848207] system 00:02: [io  0x0c00-0x0c01] has been reserved
[    1.848212] system 00:02: [io  0x0c14] has been reserved
[    1.848217] system 00:02: [io  0x0c50-0x0c52] has been reserved
[    1.848222] system 00:02: [io  0x0c6c] has been reserved
[    1.848227] system 00:02: [io  0x0c6f] has been reserved
[    1.848234] system 00:02: [io  0x0cd0-0x0cdb] has been reserved
[    1.848328] system 00:03: [mem 0x000e0000-0x000fffff] could not be reserved
[    1.848334] system 00:03: [mem 0xfe000000-0xffffffff] could not be reserved
[    1.848516] xen_register_gsi: xen: registering gsi 1 triggering 1 polarity 0
[    1.848518] xen_register_pirq: before xen_irq_from_gsi: gsi 1 triggering 1 set_pirq 1
[    1.848519] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 1, setup_gsi.triggering: 0, setup_gsi.polarity: 0
[    1.850502] pnp: PnP ACPI: found 5 devices
[    1.855783] PM-Timer failed consistency check  (0xffffff) - aborting.
[    1.855839] NET: Registered PF_INET protocol family
[    1.855938] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    1.857594] tcp_listen_portaddr_hash hash table entries: 32768 (order: 7, 524288 bytes, linear)
[    1.857632] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    1.857658] TCP established hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    1.857882] TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear)
[    1.857988] TCP: Hash tables configured (established 524288 bind 65536)
[    1.858143] MPTCP token hash table entries: 65536 (order: 8, 1572864 bytes, linear)
[    1.858194] UDP hash table entries: 32768 (order: 8, 1048576 bytes, linear)
[    1.858246] UDP-Lite hash table entries: 32768 (order: 8, 1048576 bytes, linear)
[    1.858355] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    1.858366] NET: Registered PF_XDP protocol family
[    1.858378] pci 0000:00:02.2: PCI bridge to [bus 01]
[    1.858395] pci 0000:00:02.2:   bridge window [mem 0x90b00000-0x90bfffff]
[    1.858403] pci 0000:00:02.2:   bridge window [mem 0x8810900000-0x88109fffff 64bit pref]
[    1.858415] pci 0000:00:02.4: PCI bridge to [bus 02]
[    1.858424] pci 0000:00:02.4:   bridge window [mem 0x90a00000-0x90afffff]
[    1.858437] pci 0000:00:03.1: PCI bridge to [bus 03-61]
[    1.858444] pci 0000:00:03.1:   bridge window [io  0x6000-0x9fff]
[    1.858459] pci 0000:00:03.1:   bridge window [mem 0x78000000-0x8fffffff]
[    1.858473] pci 0000:00:03.1:   bridge window [mem 0x7800000000-0x87ffffffff 64bit pref]
[    1.858490] pci 0000:00:04.1: PCI bridge to [bus 62-c0]
[    1.858496] pci 0000:00:04.1:   bridge window [io  0x2000-0x5fff]
[    1.858511] pci 0000:00:04.1:   bridge window [mem 0x60000000-0x77ffffff]
[    1.858525] pci 0000:00:04.1:   bridge window [mem 0x6800000000-0x77ffffffff 64bit pref]
[    1.858543] pci 0000:00:08.1: PCI bridge to [bus c1]
[    1.858549] pci 0000:00:08.1:   bridge window [io  0x1000-0x1fff]
[    1.858557] pci 0000:00:08.1:   bridge window [mem 0x90000000-0x905fffff]
[    1.858565] pci 0000:00:08.1:   bridge window [mem 0x8800000000-0x88107fffff 64bit pref]
[    1.858576] pci 0000:00:08.2: PCI bridge to [bus c2]
[    1.858584] pci 0000:00:08.2:   bridge window [mem 0x90900000-0x909fffff]
[    1.858592] pci 0000:00:08.2:   bridge window [mem 0x8810800000-0x88108fffff 64bit pref]
[    1.858603] pci 0000:00:08.3: PCI bridge to [bus c3]
[    1.858611] pci 0000:00:08.3:   bridge window [mem 0x90600000-0x908fffff]
[    1.858630] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    1.858636] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
[    1.858642] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[    1.858649] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000cffff window]
[    1.858655] pci_bus 0000:00: resource 8 [mem 0x000d0000-0x000effff window]
[    1.858662] pci_bus 0000:00: resource 9 [mem 0x60000000-0x90bfffff window]
[    1.858669] pci_bus 0000:00: resource 10 [mem 0xf0000000-0xfec00000 window]
[    1.858675] pci_bus 0000:00: resource 11 [mem 0xfed45000-0xfed814ff window]
[    1.858681] pci_bus 0000:00: resource 12 [mem 0xfed81900-0xfed81fff window]
[    1.858686] pci_bus 0000:00: resource 13 [mem 0xfedc0000-0xfedc0fff window]
[    1.858692] pci_bus 0000:00: resource 14 [mem 0xfedc6000-0xfedc6fff window]
[    1.858697] pci_bus 0000:00: resource 15 [mem 0x10c0200000-0x891fffffff window]
[    1.858704] pci_bus 0000:01: resource 1 [mem 0x90b00000-0x90bfffff]
[    1.858709] pci_bus 0000:01: resource 2 [mem 0x8810900000-0x88109fffff 64bit pref]
[    1.858715] pci_bus 0000:02: resource 1 [mem 0x90a00000-0x90afffff]
[    1.858720] pci_bus 0000:03: resource 0 [io  0x6000-0x9fff]
[    1.858725] pci_bus 0000:03: resource 1 [mem 0x78000000-0x8fffffff]
[    1.858730] pci_bus 0000:03: resource 2 [mem 0x7800000000-0x87ffffffff 64bit pref]
[    1.858736] pci_bus 0000:62: resource 0 [io  0x2000-0x5fff]
[    1.858741] pci_bus 0000:62: resource 1 [mem 0x60000000-0x77ffffff]
[    1.858746] pci_bus 0000:62: resource 2 [mem 0x6800000000-0x77ffffffff 64bit pref]
[    1.858752] pci_bus 0000:c1: resource 0 [io  0x1000-0x1fff]
[    1.858757] pci_bus 0000:c1: resource 1 [mem 0x90000000-0x905fffff]
[    1.858762] pci_bus 0000:c1: resource 2 [mem 0x8800000000-0x88107fffff 64bit pref]
[    1.858768] pci_bus 0000:c2: resource 1 [mem 0x90900000-0x909fffff]
[    1.858773] pci_bus 0000:c2: resource 2 [mem 0x8810800000-0x88108fffff 64bit pref]
[    1.858779] pci_bus 0000:c3: resource 1 [mem 0x90600000-0x908fffff]
[    1.859213] pci 0000:c1:00.1: D0 power state depends on 0000:c1:00.0
[    1.859347] xen_register_gsi: xen: registering gsi 40 triggering 0 polarity 1
[    1.859349] xen_register_pirq: before xen_irq_from_gsi: gsi 40 triggering 0 set_pirq 1
[    1.859363] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 40 triggering 0 shareable 1 name ioapic-level
[    1.859375] xen_register_pirq: xen: --> pirq=40 -> irq=40 (gsi=40)
[    1.859376] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 40, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.859450] xen_register_gsi: xen: registering gsi 37 triggering 0 polarity 1
[    1.859451] xen_register_pirq: before xen_irq_from_gsi: gsi 37 triggering 0 set_pirq 1
[    1.859454] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 37 triggering 0 shareable 1 name ioapic-level
[    1.859463] xen_register_pirq: xen: --> pirq=37 -> irq=37 (gsi=37)
[    1.859464] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 37, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.859955] xen_register_gsi: xen: registering gsi 38 triggering 0 polarity 1
[    1.859957] xen_register_pirq: before xen_irq_from_gsi: gsi 38 triggering 0 set_pirq 1
[    1.859959] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 38 triggering 0 shareable 1 name ioapic-level
[    1.859974] xen_register_pirq: xen: --> pirq=38 -> irq=38 (gsi=38)
[    1.859975] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 38, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.860407] xen_register_gsi: xen: registering gsi 40 triggering 0 polarity 1
[    1.860408] xen_register_pirq: before xen_irq_from_gsi: gsi 40 triggering 0 set_pirq 1
[    1.860410] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 40, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.860412] Already setup the GSI :40
[    1.860463] xen_register_gsi: xen: registering gsi 46 triggering 0 polarity 1
[    1.860465] xen_register_pirq: before xen_irq_from_gsi: gsi 46 triggering 0 set_pirq 1
[    1.860467] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 46 triggering 0 shareable 1 name ioapic-level
[    1.860476] xen_register_pirq: xen: --> pirq=46 -> irq=46 (gsi=46)
[    1.860477] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 46, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.860875] xen_register_gsi: xen: registering gsi 47 triggering 0 polarity 1
[    1.860876] xen_register_pirq: before xen_irq_from_gsi: gsi 47 triggering 0 set_pirq 1
[    1.860879] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 47 triggering 0 shareable 1 name ioapic-level
[    1.860888] xen_register_pirq: xen: --> pirq=47 -> irq=47 (gsi=47)
[    1.860889] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 47, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    1.861248] PCI: CLS 64 bytes, default 64
[    1.861258] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    1.861263] software IO TLB: mapped [mem 0x000000103b000000-0x000000103f000000] (64MB)
[    1.861309] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2f7a7a7f221, max_idle_ns: 440795289726 ns
[    1.861323] Trying to unpack rootfs image as initramfs...
[    1.861358] clocksource: Switched to clocksource tsc
[    1.866845] Initialise system trusted keyrings
[    1.866859] Key type blacklist registered
[    1.866932] workingset: timestamp_bits=46 max_order=24 bucket_order=0
[    1.866946] zbud: loaded
[    1.867991] integrity: Platform Keyring initialized
[    1.867998] integrity: Machine keyring initialized
[    1.873607] NET: Registered PF_ALG protocol family
[    1.873613] xor: automatically using best checksumming function   avx       
[    1.873620] Key type asymmetric registered
[    1.873624] Asymmetric key parser 'x509' registered
[    3.485212] Freeing initrd memory: 224212K
[    3.491414] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    3.491520] io scheduler mq-deadline registered
[    3.491531] io scheduler kyber registered
[    3.491557] io scheduler bfq registered
[    3.493725] atomic64_test: passed for x86-64 platform with CX8 and with SSE
[    3.493945] amd_gpio AMDI0030:00: iomux not supported
[    3.493948] amd_gpio AMDI0030:00: try to register 183 pins ...
[    3.493950] pinctrl core: registered pin 0 (GPIO_0) on AMDI0030:00
[    3.493952] pinctrl core: registered pin 1 (GPIO_1) on AMDI0030:00
[    3.493953] pinctrl core: registered pin 2 (GPIO_2) on AMDI0030:00
[    3.493954] pinctrl core: registered pin 3 (GPIO_3) on AMDI0030:00
[    3.493956] pinctrl core: registered pin 4 (GPIO_4) on AMDI0030:00
[    3.493957] pinctrl core: registered pin 5 (GPIO_5) on AMDI0030:00
[    3.493958] pinctrl core: registered pin 6 (GPIO_6) on AMDI0030:00
[    3.493959] pinctrl core: registered pin 7 (GPIO_7) on AMDI0030:00
[    3.493960] pinctrl core: registered pin 8 (GPIO_8) on AMDI0030:00
[    3.493961] pinctrl core: registered pin 9 (GPIO_9) on AMDI0030:00
[    3.493962] pinctrl core: registered pin 10 (GPIO_10) on AMDI0030:00
[    3.493964] pinctrl core: registered pin 11 (GPIO_11) on AMDI0030:00
[    3.493965] pinctrl core: registered pin 12 (GPIO_12) on AMDI0030:00
[    3.493966] pinctrl core: registered pin 13 (GPIO_13) on AMDI0030:00
[    3.493967] pinctrl core: registered pin 14 (GPIO_14) on AMDI0030:00
[    3.493968] pinctrl core: registered pin 15 (GPIO_15) on AMDI0030:00
[    3.493969] pinctrl core: registered pin 16 (GPIO_16) on AMDI0030:00
[    3.493971] pinctrl core: registered pin 17 (GPIO_17) on AMDI0030:00
[    3.493972] pinctrl core: registered pin 18 (GPIO_18) on AMDI0030:00
[    3.493973] pinctrl core: registered pin 19 (GPIO_19) on AMDI0030:00
[    3.493974] pinctrl core: registered pin 20 (GPIO_20) on AMDI0030:00
[    3.493975] pinctrl core: registered pin 21 (GPIO_21) on AMDI0030:00
[    3.493976] pinctrl core: registered pin 22 (GPIO_22) on AMDI0030:00
[    3.493977] pinctrl core: registered pin 23 (GPIO_23) on AMDI0030:00
[    3.493978] pinctrl core: registered pin 24 (GPIO_24) on AMDI0030:00
[    3.493979] pinctrl core: registered pin 25 (GPIO_25) on AMDI0030:00
[    3.493981] pinctrl core: registered pin 26 (GPIO_26) on AMDI0030:00
[    3.493982] pinctrl core: registered pin 27 (GPIO_27) on AMDI0030:00
[    3.493983] pinctrl core: registered pin 28 (GPIO_28) on AMDI0030:00
[    3.493984] pinctrl core: registered pin 29 (GPIO_29) on AMDI0030:00
[    3.493985] pinctrl core: registered pin 30 (GPIO_30) on AMDI0030:00
[    3.493986] pinctrl core: registered pin 31 (GPIO_31) on AMDI0030:00
[    3.493987] pinctrl core: registered pin 32 (GPIO_32) on AMDI0030:00
[    3.493988] pinctrl core: registered pin 33 (GPIO_33) on AMDI0030:00
[    3.493990] pinctrl core: registered pin 34 (GPIO_34) on AMDI0030:00
[    3.493991] pinctrl core: registered pin 35 (GPIO_35) on AMDI0030:00
[    3.493992] pinctrl core: registered pin 36 (GPIO_36) on AMDI0030:00
[    3.493993] pinctrl core: registered pin 37 (GPIO_37) on AMDI0030:00
[    3.493994] pinctrl core: registered pin 38 (GPIO_38) on AMDI0030:00
[    3.493995] pinctrl core: registered pin 39 (GPIO_39) on AMDI0030:00
[    3.493996] pinctrl core: registered pin 40 (GPIO_40) on AMDI0030:00
[    3.493997] pinctrl core: registered pin 41 (GPIO_41) on AMDI0030:00
[    3.493999] pinctrl core: registered pin 42 (GPIO_42) on AMDI0030:00
[    3.494000] pinctrl core: registered pin 43 (GPIO_43) on AMDI0030:00
[    3.494001] pinctrl core: registered pin 44 (GPIO_44) on AMDI0030:00
[    3.494002] pinctrl core: registered pin 45 (GPIO_45) on AMDI0030:00
[    3.494004] pinctrl core: registered pin 46 (GPIO_46) on AMDI0030:00
[    3.494005] pinctrl core: registered pin 47 (GPIO_47) on AMDI0030:00
[    3.494006] pinctrl core: registered pin 48 (GPIO_48) on AMDI0030:00
[    3.494007] pinctrl core: registered pin 49 (GPIO_49) on AMDI0030:00
[    3.494008] pinctrl core: registered pin 50 (GPIO_50) on AMDI0030:00
[    3.494009] pinctrl core: registered pin 51 (GPIO_51) on AMDI0030:00
[    3.494010] pinctrl core: registered pin 52 (GPIO_52) on AMDI0030:00
[    3.494011] pinctrl core: registered pin 53 (GPIO_53) on AMDI0030:00
[    3.494012] pinctrl core: registered pin 54 (GPIO_54) on AMDI0030:00
[    3.494014] pinctrl core: registered pin 55 (GPIO_55) on AMDI0030:00
[    3.494015] pinctrl core: registered pin 56 (GPIO_56) on AMDI0030:00
[    3.494016] pinctrl core: registered pin 57 (GPIO_57) on AMDI0030:00
[    3.494017] pinctrl core: registered pin 58 (GPIO_58) on AMDI0030:00
[    3.494018] pinctrl core: registered pin 59 (GPIO_59) on AMDI0030:00
[    3.494019] pinctrl core: registered pin 60 (GPIO_60) on AMDI0030:00
[    3.494020] pinctrl core: registered pin 61 (GPIO_61) on AMDI0030:00
[    3.494021] pinctrl core: registered pin 62 (GPIO_62) on AMDI0030:00
[    3.494023] pinctrl core: registered pin 64 (GPIO_64) on AMDI0030:00
[    3.494024] pinctrl core: registered pin 65 (GPIO_65) on AMDI0030:00
[    3.494025] pinctrl core: registered pin 66 (GPIO_66) on AMDI0030:00
[    3.494026] pinctrl core: registered pin 67 (GPIO_67) on AMDI0030:00
[    3.494027] pinctrl core: registered pin 68 (GPIO_68) on AMDI0030:00
[    3.494028] pinctrl core: registered pin 69 (GPIO_69) on AMDI0030:00
[    3.494030] pinctrl core: registered pin 70 (GPIO_70) on AMDI0030:00
[    3.494031] pinctrl core: registered pin 71 (GPIO_71) on AMDI0030:00
[    3.494032] pinctrl core: registered pin 72 (GPIO_72) on AMDI0030:00
[    3.494033] pinctrl core: registered pin 73 (GPIO_73) on AMDI0030:00
[    3.494034] pinctrl core: registered pin 74 (GPIO_74) on AMDI0030:00
[    3.494035] pinctrl core: registered pin 75 (GPIO_75) on AMDI0030:00
[    3.494037] pinctrl core: registered pin 76 (GPIO_76) on AMDI0030:00
[    3.494039] pinctrl core: registered pin 77 (GPIO_77) on AMDI0030:00
[    3.494040] pinctrl core: registered pin 78 (GPIO_78) on AMDI0030:00
[    3.494041] pinctrl core: registered pin 79 (GPIO_79) on AMDI0030:00
[    3.494042] pinctrl core: registered pin 80 (GPIO_80) on AMDI0030:00
[    3.494043] pinctrl core: registered pin 81 (GPIO_81) on AMDI0030:00
[    3.494044] pinctrl core: registered pin 82 (GPIO_82) on AMDI0030:00
[    3.494046] pinctrl core: registered pin 83 (GPIO_83) on AMDI0030:00
[    3.494047] pinctrl core: registered pin 84 (GPIO_84) on AMDI0030:00
[    3.494048] pinctrl core: registered pin 85 (GPIO_85) on AMDI0030:00
[    3.494049] pinctrl core: registered pin 86 (GPIO_86) on AMDI0030:00
[    3.494050] pinctrl core: registered pin 87 (GPIO_87) on AMDI0030:00
[    3.494051] pinctrl core: registered pin 88 (GPIO_88) on AMDI0030:00
[    3.494052] pinctrl core: registered pin 89 (GPIO_89) on AMDI0030:00
[    3.494053] pinctrl core: registered pin 90 (GPIO_90) on AMDI0030:00
[    3.494054] pinctrl core: registered pin 91 (GPIO_91) on AMDI0030:00
[    3.494056] pinctrl core: registered pin 92 (GPIO_92) on AMDI0030:00
[    3.494057] pinctrl core: registered pin 93 (GPIO_93) on AMDI0030:00
[    3.494058] pinctrl core: registered pin 94 (GPIO_94) on AMDI0030:00
[    3.494059] pinctrl core: registered pin 95 (GPIO_95) on AMDI0030:00
[    3.494060] pinctrl core: registered pin 96 (GPIO_96) on AMDI0030:00
[    3.494061] pinctrl core: registered pin 97 (GPIO_97) on AMDI0030:00
[    3.494062] pinctrl core: registered pin 98 (GPIO_98) on AMDI0030:00
[    3.494063] pinctrl core: registered pin 99 (GPIO_99) on AMDI0030:00
[    3.494065] pinctrl core: registered pin 100 (GPIO_100) on AMDI0030:00
[    3.494066] pinctrl core: registered pin 101 (GPIO_101) on AMDI0030:00
[    3.494067] pinctrl core: registered pin 102 (GPIO_102) on AMDI0030:00
[    3.494068] pinctrl core: registered pin 103 (GPIO_103) on AMDI0030:00
[    3.494069] pinctrl core: registered pin 104 (GPIO_104) on AMDI0030:00
[    3.494070] pinctrl core: registered pin 105 (GPIO_105) on AMDI0030:00
[    3.494071] pinctrl core: registered pin 106 (GPIO_106) on AMDI0030:00
[    3.494073] pinctrl core: registered pin 107 (GPIO_107) on AMDI0030:00
[    3.494074] pinctrl core: registered pin 108 (GPIO_108) on AMDI0030:00
[    3.494075] pinctrl core: registered pin 109 (GPIO_109) on AMDI0030:00
[    3.494076] pinctrl core: registered pin 110 (GPIO_110) on AMDI0030:00
[    3.494077] pinctrl core: registered pin 111 (GPIO_111) on AMDI0030:00
[    3.494078] pinctrl core: registered pin 112 (GPIO_112) on AMDI0030:00
[    3.494079] pinctrl core: registered pin 113 (GPIO_113) on AMDI0030:00
[    3.494080] pinctrl core: registered pin 114 (GPIO_114) on AMDI0030:00
[    3.494082] pinctrl core: registered pin 115 (GPIO_115) on AMDI0030:00
[    3.494083] pinctrl core: registered pin 116 (GPIO_116) on AMDI0030:00
[    3.494084] pinctrl core: registered pin 117 (GPIO_117) on AMDI0030:00
[    3.494085] pinctrl core: registered pin 118 (GPIO_118) on AMDI0030:00
[    3.494086] pinctrl core: registered pin 119 (GPIO_119) on AMDI0030:00
[    3.494087] pinctrl core: registered pin 120 (GPIO_120) on AMDI0030:00
[    3.494088] pinctrl core: registered pin 121 (GPIO_121) on AMDI0030:00
[    3.494089] pinctrl core: registered pin 122 (GPIO_122) on AMDI0030:00
[    3.494090] pinctrl core: registered pin 123 (GPIO_123) on AMDI0030:00
[    3.494092] pinctrl core: registered pin 124 (GPIO_124) on AMDI0030:00
[    3.494093] pinctrl core: registered pin 125 (GPIO_125) on AMDI0030:00
[    3.494094] pinctrl core: registered pin 126 (GPIO_126) on AMDI0030:00
[    3.494095] pinctrl core: registered pin 127 (GPIO_127) on AMDI0030:00
[    3.494096] pinctrl core: registered pin 128 (GPIO_128) on AMDI0030:00
[    3.494098] pinctrl core: registered pin 129 (GPIO_129) on AMDI0030:00
[    3.494099] pinctrl core: registered pin 130 (GPIO_130) on AMDI0030:00
[    3.494100] pinctrl core: registered pin 131 (GPIO_131) on AMDI0030:00
[    3.494101] pinctrl core: registered pin 132 (GPIO_132) on AMDI0030:00
[    3.494102] pinctrl core: registered pin 133 (GPIO_133) on AMDI0030:00
[    3.494103] pinctrl core: registered pin 134 (GPIO_134) on AMDI0030:00
[    3.494104] pinctrl core: registered pin 135 (GPIO_135) on AMDI0030:00
[    3.494105] pinctrl core: registered pin 136 (GPIO_136) on AMDI0030:00
[    3.494107] pinctrl core: registered pin 137 (GPIO_137) on AMDI0030:00
[    3.494108] pinctrl core: registered pin 138 (GPIO_138) on AMDI0030:00
[    3.494109] pinctrl core: registered pin 139 (GPIO_139) on AMDI0030:00
[    3.494111] pinctrl core: registered pin 140 (GPIO_140) on AMDI0030:00
[    3.494112] pinctrl core: registered pin 141 (GPIO_141) on AMDI0030:00
[    3.494113] pinctrl core: registered pin 142 (GPIO_142) on AMDI0030:00
[    3.494114] pinctrl core: registered pin 143 (GPIO_143) on AMDI0030:00
[    3.494115] pinctrl core: registered pin 144 (GPIO_144) on AMDI0030:00
[    3.494116] pinctrl core: registered pin 145 (GPIO_145) on AMDI0030:00
[    3.494117] pinctrl core: registered pin 146 (GPIO_146) on AMDI0030:00
[    3.494119] pinctrl core: registered pin 147 (GPIO_147) on AMDI0030:00
[    3.494120] pinctrl core: registered pin 148 (GPIO_148) on AMDI0030:00
[    3.494121] pinctrl core: registered pin 149 (GPIO_149) on AMDI0030:00
[    3.494122] pinctrl core: registered pin 150 (GPIO_150) on AMDI0030:00
[    3.494123] pinctrl core: registered pin 151 (GPIO_151) on AMDI0030:00
[    3.494124] pinctrl core: registered pin 152 (GPIO_152) on AMDI0030:00
[    3.494125] pinctrl core: registered pin 153 (GPIO_153) on AMDI0030:00
[    3.494126] pinctrl core: registered pin 154 (GPIO_154) on AMDI0030:00
[    3.494127] pinctrl core: registered pin 155 (GPIO_155) on AMDI0030:00
[    3.494129] pinctrl core: registered pin 156 (GPIO_156) on AMDI0030:00
[    3.494130] pinctrl core: registered pin 157 (GPIO_157) on AMDI0030:00
[    3.494131] pinctrl core: registered pin 158 (GPIO_158) on AMDI0030:00
[    3.494132] pinctrl core: registered pin 159 (GPIO_159) on AMDI0030:00
[    3.494133] pinctrl core: registered pin 160 (GPIO_160) on AMDI0030:00
[    3.494134] pinctrl core: registered pin 161 (GPIO_161) on AMDI0030:00
[    3.494135] pinctrl core: registered pin 162 (GPIO_162) on AMDI0030:00
[    3.494136] pinctrl core: registered pin 163 (GPIO_163) on AMDI0030:00
[    3.494138] pinctrl core: registered pin 164 (GPIO_164) on AMDI0030:00
[    3.494139] pinctrl core: registered pin 165 (GPIO_165) on AMDI0030:00
[    3.494140] pinctrl core: registered pin 166 (GPIO_166) on AMDI0030:00
[    3.494141] pinctrl core: registered pin 167 (GPIO_167) on AMDI0030:00
[    3.494142] pinctrl core: registered pin 168 (GPIO_168) on AMDI0030:00
[    3.494143] pinctrl core: registered pin 169 (GPIO_169) on AMDI0030:00
[    3.494144] pinctrl core: registered pin 170 (GPIO_170) on AMDI0030:00
[    3.494145] pinctrl core: registered pin 171 (GPIO_171) on AMDI0030:00
[    3.494147] pinctrl core: registered pin 172 (GPIO_172) on AMDI0030:00
[    3.494148] pinctrl core: registered pin 173 (GPIO_173) on AMDI0030:00
[    3.494149] pinctrl core: registered pin 174 (GPIO_174) on AMDI0030:00
[    3.494150] pinctrl core: registered pin 175 (GPIO_175) on AMDI0030:00
[    3.494151] pinctrl core: registered pin 176 (GPIO_176) on AMDI0030:00
[    3.494152] pinctrl core: registered pin 177 (GPIO_177) on AMDI0030:00
[    3.494153] pinctrl core: registered pin 178 (GPIO_178) on AMDI0030:00
[    3.494154] pinctrl core: registered pin 179 (GPIO_179) on AMDI0030:00
[    3.494155] pinctrl core: registered pin 180 (GPIO_180) on AMDI0030:00
[    3.494157] pinctrl core: registered pin 181 (GPIO_181) on AMDI0030:00
[    3.494158] pinctrl core: registered pin 182 (GPIO_182) on AMDI0030:00
[    3.494159] pinctrl core: registered pin 183 (GPIO_183) on AMDI0030:00
[    3.494160] amd_gpio AMDI0030:00: failed to lookup the default state
[    3.494162] amd_gpio AMDI0030:00: failed to lookup the sleep state
[    3.494657] gpiochip_find_base: found new base at 512
[    3.495145] amd_gpio AMDI0030:00: Invalid config param 0014
[    3.495148] gpio gpiochip0: Persistence not supported for GPIO 0
[    3.495174] amd_gpio AMDI0030:00: Invalid config param 0014
[    3.495177] gpio gpiochip0: Persistence not supported for GPIO 61
[    3.495197] amd_gpio AMDI0030:00: Invalid config param 0014
[    3.495200] gpio gpiochip0: Persistence not supported for GPIO 62
[    3.495220] amd_gpio AMDI0030:00: Invalid config param 0014
[    3.495223] gpio gpiochip0: Persistence not supported for GPIO 58
[    3.495242] amd_gpio AMDI0030:00: Invalid config param 0014
[    3.495245] gpio gpiochip0: Persistence not supported for GPIO 59
[    3.495264] amd_gpio AMDI0030:00: Invalid config param 0014
[    3.495267] gpio gpiochip0: Persistence not supported for GPIO 2
[    3.495291] amd_gpio AMDI0030:00: Invalid config param 0014
[    3.495294] gpio gpiochip0: Persistence not supported for GPIO 6
[    3.495314] amd_gpio AMDI0030:00: Invalid config param 0014
[    3.495317] gpio gpiochip0: Persistence not supported for GPIO 54
[    3.495388] gpio gpiochip0: (AMDI0030:00): added GPIO chardev (254:0)
[    3.495401] gpio gpiochip0: registered GPIOs 512 to 767 on AMDI0030:00
[    3.495404] gpio gpiochip0: (AMDI0030:00): created GPIO range 0->255 ==> AMDI0030:00 PIN 0->255
[    3.495490] amd_gpio AMDI0030:00: amd gpio driver loaded
[    3.495646] pcieport 0000:00:02.2: PME: Signaling with IRQ 162
[    3.495813] pcieport 0000:00:02.4: PME: Signaling with IRQ 163
[    3.496051] pcieport 0000:00:03.1: PME: Signaling with IRQ 164
[    3.496090] pcieport 0000:00:03.1: pciehp: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+
[    3.496793] pcieport 0000:00:04.1: PME: Signaling with IRQ 165
[    3.496838] pcieport 0000:00:04.1: pciehp: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+
[    3.497422] pcieport 0000:00:08.1: PME: Signaling with IRQ 166
[    3.497567] xen_register_gsi: xen: registering gsi 40 triggering 0 polarity 1
[    3.497569] xen_register_pirq: before xen_irq_from_gsi: gsi 40 triggering 0 set_pirq 1
[    3.497581] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 40, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    3.497585] Already setup the GSI :40
[    3.497683] pcieport 0000:00:08.2: PME: Signaling with IRQ 167
[    3.497835] pcieport 0000:00:08.3: PME: Signaling with IRQ 168
[    3.497944] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    3.497972] efifb: probing for efifb
[    3.499187] efifb: No BGRT, not showing boot graphics
[    3.499193] efifb: framebuffer at 0x8800000000, using 13536k, total 13536k
[    3.499198] efifb: mode is 2256x1504x32, linelength=9216, pages=1
[    3.499204] efifb: scrolling: redraw
[    3.499207] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[    3.499312] Console: switching to colour frame buffer device 282x94
[    3.500613] fb0: EFI VGA frame buffer device
[    3.502100] ACPI: AC: AC Adapter [ACAD] (on-line)
[    3.502183] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/PNP0C09:00/PNP0C0D:00/input/input0
[    3.502235] ACPI: button: Lid Switch [LID0]
[    3.502279] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[    3.502314] ACPI: button: Power Button [PWRB]
[    3.502379] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.502415] ACPI: \_SB_.PLTF.C000: Found 3 idle states
[    3.502506] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.502561] ACPI: \_SB_.PLTF.C001: Found 3 idle states
[    3.502652] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.502706] ACPI: \_SB_.PLTF.C002: Found 3 idle states
[    3.502800] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.502859] ACPI: \_SB_.PLTF.C003: Found 3 idle states
[    3.502949] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.503004] ACPI: \_SB_.PLTF.C004: Found 3 idle states
[    3.503090] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.503160] ACPI: \_SB_.PLTF.C005: Found 3 idle states
[    3.503269] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.503327] ACPI: \_SB_.PLTF.C006: Found 3 idle states
[    3.503428] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.503483] ACPI: \_SB_.PLTF.C007: Found 3 idle states
[    3.503584] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.503634] ACPI: \_SB_.PLTF.C008: Found 3 idle states
[    3.503736] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.503789] ACPI: \_SB_.PLTF.C009: Found 3 idle states
[    3.503895] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.503948] ACPI: \_SB_.PLTF.C00A: Found 3 idle states
[    3.504050] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.504101] ACPI: \_SB_.PLTF.C00B: Found 3 idle states
[    3.504203] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.504256] ACPI: \_SB_.PLTF.C00C: Found 3 idle states
[    3.504357] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.504409] ACPI: \_SB_.PLTF.C00D: Found 3 idle states
[    3.504510] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.504563] ACPI: \_SB_.PLTF.C00E: Found 3 idle states
[    3.504660] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[    3.504709] ACPI: \_SB_.PLTF.C00F: Found 3 idle states
[    3.505118] thermal LNXTHERM:00: registered as thermal_zone0
[    3.505152] ACPI: thermal: Thermal Zone [TZ00] (38 C)
[    3.505381] thermal LNXTHERM:01: registered as thermal_zone1
[    3.505414] ACPI: thermal: Thermal Zone [TZ01] (41 C)
[    3.505663] thermal LNXTHERM:02: registered as thermal_zone2
[    3.505695] ACPI: thermal: Thermal Zone [TZ02] (35 C)
[    3.505928] thermal LNXTHERM:03: registered as thermal_zone3
[    3.505960] ACPI: thermal: Thermal Zone [TZ03] (80 C)
[    3.507180] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    3.507746] ACPI: battery: Slot [BAT1] (battery present)
[    3.509630] hpet_acpi_add: no address or irqs in _CRS
[    3.509697] Non-volatile memory driver v1.3
[    3.509726] Linux agpgart interface v0.103
[    3.510576] ACPI: bus type drm_connector registered
[    3.513451] mdio_bus fixed-0: using lookup tables for GPIO lookup
[    3.513456] mdio_bus fixed-0: No GPIO consumer reset found
[    3.513886] xen_register_gsi: xen: registering gsi 37 triggering 0 polarity 1
[    3.513888] xen_register_pirq: before xen_irq_from_gsi: gsi 37 triggering 0 set_pirq 1
[    3.513891] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 37, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    3.513894] Already setup the GSI :37
[    3.514082] xhci_hcd 0000:c1:00.3: xHCI Host Controller
[    3.514135] xhci_hcd 0000:c1:00.3: new USB bus registered, assigned bus number 1
[    3.514621] xhci_hcd 0000:c1:00.3: hcc params 0x0128ffc5 hci version 0x120 quirks 0x0000000200000410
[    3.515005] xhci_hcd 0000:c1:00.3: xHCI Host Controller
[    3.515054] xhci_hcd 0000:c1:00.3: new USB bus registered, assigned bus number 2
[    3.515075] xhci_hcd 0000:c1:00.3: Host supports USB 3.1 Enhanced SuperSpeed
[    3.515142] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    3.515161] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.515176] usb usb1: Product: xHCI Host Controller
[    3.515187] usb usb1: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    3.515203] usb usb1: SerialNumber: 0000:c1:00.3
[    3.515326] hub 1-0:1.0: USB hub found
[    3.515368] hub 1-0:1.0: 5 ports detected
[    3.523316] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.523371] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    3.523399] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.523977] usb usb2: Product: xHCI Host Controller
[    3.524545] usb usb2: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    3.525121] usb usb2: SerialNumber: 0000:c1:00.3
[    3.525776] hub 2-0:1.0: USB hub found
[    3.526378] hub 2-0:1.0: 2 ports detected
[    3.530388] xen_register_gsi: xen: registering gsi 38 triggering 0 polarity 1
[    3.530390] xen_register_pirq: before xen_irq_from_gsi: gsi 38 triggering 0 set_pirq 1
[    3.530393] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 38, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    3.530396] Already setup the GSI :38
[    3.531154] xhci_hcd 0000:c1:00.4: xHCI Host Controller
[    3.531750] xhci_hcd 0000:c1:00.4: new USB bus registered, assigned bus number 3
[    3.532690] xhci_hcd 0000:c1:00.4: hcc params 0x0110ffc5 hci version 0x120 quirks 0x0000000200000410
[    3.533598] xhci_hcd 0000:c1:00.4: xHCI Host Controller
[    3.534232] xhci_hcd 0000:c1:00.4: new USB bus registered, assigned bus number 4
[    3.534845] xhci_hcd 0000:c1:00.4: Host supports USB 3.1 Enhanced SuperSpeed
[    3.535552] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    3.536746] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.537300] usb usb3: Product: xHCI Host Controller
[    3.537862] usb usb3: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    3.538414] usb usb3: SerialNumber: 0000:c1:00.4
[    3.539107] hub 3-0:1.0: USB hub found
[    3.539676] hub 3-0:1.0: 1 port detected
[    3.541883] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.542477] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    3.543035] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.543574] usb usb4: Product: xHCI Host Controller
[    3.544115] usb usb4: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    3.544651] usb usb4: SerialNumber: 0000:c1:00.4
[    3.545328] hub 4-0:1.0: USB hub found
[    3.545890] hub 4-0:1.0: 1 port detected
[    3.548251] xen_register_gsi: xen: registering gsi 46 triggering 0 polarity 1
[    3.548253] xen_register_pirq: before xen_irq_from_gsi: gsi 46 triggering 0 set_pirq 1
[    3.548256] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 46, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    3.548259] Already setup the GSI :46
[    3.548962] xhci_hcd 0000:c3:00.3: xHCI Host Controller
[    3.549604] xhci_hcd 0000:c3:00.3: new USB bus registered, assigned bus number 5
[    3.550513] xhci_hcd 0000:c3:00.3: hcc params 0x0110ffc5 hci version 0x120 quirks 0x0000000200000410
[    3.551665] xhci_hcd 0000:c3:00.3: xHCI Host Controller
[    3.552257] xhci_hcd 0000:c3:00.3: new USB bus registered, assigned bus number 6
[    3.552814] xhci_hcd 0000:c3:00.3: Host supports USB 3.1 Enhanced SuperSpeed
[    3.553371] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    3.553910] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.554440] usb usb5: Product: xHCI Host Controller
[    3.554970] usb usb5: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    3.555485] usb usb5: SerialNumber: 0000:c3:00.3
[    3.556213] hub 5-0:1.0: USB hub found
[    3.556745] hub 5-0:1.0: 1 port detected
[    3.558951] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.559528] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    3.560056] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.560572] usb usb6: Product: xHCI Host Controller
[    3.561087] usb usb6: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    3.561593] usb usb6: SerialNumber: 0000:c3:00.3
[    3.562304] hub 6-0:1.0: USB hub found
[    3.562866] hub 6-0:1.0: 1 port detected
[    3.565731] xen_register_gsi: xen: registering gsi 47 triggering 0 polarity 1
[    3.565733] xen_register_pirq: before xen_irq_from_gsi: gsi 47 triggering 0 set_pirq 1
[    3.565736] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 47, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    3.565739] Already setup the GSI :47
[    3.566426] xhci_hcd 0000:c3:00.4: xHCI Host Controller
[    3.567052] xhci_hcd 0000:c3:00.4: new USB bus registered, assigned bus number 7
[    3.567882] xhci_hcd 0000:c3:00.4: hcc params 0x0110ffc5 hci version 0x120 quirks 0x0000000200000410
[    3.569015] xhci_hcd 0000:c3:00.4: xHCI Host Controller
[    3.569671] xhci_hcd 0000:c3:00.4: new USB bus registered, assigned bus number 8
[    3.570224] xhci_hcd 0000:c3:00.4: Host supports USB 3.1 Enhanced SuperSpeed
[    3.570781] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    3.571279] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.571771] usb usb7: Product: xHCI Host Controller
[    3.572258] usb usb7: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    3.572747] usb usb7: SerialNumber: 0000:c3:00.4
[    3.573443] hub 7-0:1.0: USB hub found
[    3.573968] hub 7-0:1.0: 1 port detected
[    3.576149] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.576704] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    3.577207] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.577696] usb usb8: Product: xHCI Host Controller
[    3.578180] usb usb8: Manufacturer: Linux 6.6.7xen-irq-dbg-1+ xhci-hcd
[    3.578665] usb usb8: SerialNumber: 0000:c3:00.4
[    3.579384] hub 8-0:1.0: USB hub found
[    3.579930] hub 8-0:1.0: 1 port detected
[    3.582764] usbcore: registered new interface driver usbserial_generic
[    3.583284] usbserial: USB Serial support registered for generic
[    3.583828] i8042: PNP: PS/2 Controller [PNP0303:KBC0] at 0x60,0x64 irq 1
[    3.584345] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[    3.587532] i8042: Warning: Keylock active
[    3.588328] serio: i8042 KBD port at 0x60,0x64 irq 1
[    3.589020] mousedev: PS/2 mouse device common for all mice
[    3.589879] rtc_cmos 00:01: RTC can wake from S4
[    3.590816] rtc_cmos 00:01: registered as rtc0
[    3.591388] rtc_cmos 00:01: setting system clock to 2023-12-20T16:20:50 UTC (1703089250)
[    3.591946] rtc_cmos 00:01: using ACPI '\_SB.PCI0.LPC0.RTC' for 'wp' GPIO lookup
[    3.591953] acpi PNP0B00:00: GPIO: looking up wp-gpios
[    3.591955] acpi PNP0B00:00: GPIO: looking up wp-gpio
[    3.591957] rtc_cmos 00:01: using lookup tables for GPIO lookup
[    3.591958] rtc_cmos 00:01: No GPIO consumer wp found
[    3.591998] rtc_cmos 00:01: alarms up to one month, 114 bytes nvram
[    3.592537] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[    3.593071] device-mapper: uevent: version 1.0.3
[    3.593701] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
[    3.594444] amd_pstate: driver load is disabled, boot with specific mode to enable this
[    3.595605] hid: raw HID events driver (C) Jiri Kosina
[    3.596196] usbcore: registered new interface driver usbhid
[    3.596742] usbhid: USB HID core driver
[    3.597427] drop_monitor: Initializing network drop monitor service
[    3.600139] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
[    3.608433] Initializing XFRM netlink socket
[    3.609033] NET: Registered PF_INET6 protocol family
[    3.616709] Segment Routing with IPv6
[    3.617318] RPL Segment Routing with IPv6
[    3.617850] In-situ OAM (IOAM) with IPv6
[    3.618408] mip6: Mobile IPv6
[    3.618977] NET: Registered PF_PACKET protocol family
[    3.620779] IPI shorthand broadcast: enabled
[    3.621372] AVX2 version of gcm_enc/dec engaged.
[    3.622537] AES CTR mode by8 optimization enabled
[    3.625177] sched_clock: Marking stable (3590001784, 34803970)->(3629667163, -4861409)
[    3.626147] registered taskstats version 1
[    3.629858] Loading compiled-in X.509 certificates
[    3.637039] Loaded X.509 cert 'Build time autogenerated kernel key: 3f6a57fb3f3898b7be9c82c1820e4f9123e8e07f'
[    3.640240] page_owner is disabled
[    3.640977] Key type .fscrypt registered
[    3.642041] Key type fscrypt-provisioning registered
[    3.643230] Btrfs loaded, zoned=yes, fsverity=yes
[    3.643833] Key type big_key registered
[    3.650301] Key type encrypted registered
[    3.654185] integrity: Loading X.509 certificate: UEFI:db
[    3.654865] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[    3.655408] integrity: Loading X.509 certificate: UEFI:db
[    3.655969] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[    3.656517] integrity: Loading X.509 certificate: UEFI:db
[    3.657087] integrity: Loaded X.509 cert 'frame.work-LaptopAMDDB: 02'
[    3.668807] ima: No TPM chip found, activating TPM-bypass!
[    3.669405] Loading compiled-in module X.509 certificates
[    3.670256] Loaded X.509 cert 'Build time autogenerated kernel key: 3f6a57fb3f3898b7be9c82c1820e4f9123e8e07f'
[    3.670851] ima: Allocated hash algorithm: sha256
[    3.671414] ima: No architecture policies found
[    3.671994] evm: Initialising EVM extended attributes:
[    3.672576] evm: security.selinux
[    3.673148] evm: security.SMACK64 (disabled)
[    3.673734] evm: security.SMACK64EXEC (disabled)
[    3.674306] evm: security.SMACK64TRANSMUTE (disabled)
[    3.674879] evm: security.SMACK64MMAP (disabled)
[    3.675429] evm: security.apparmor (disabled)
[    3.675988] evm: security.ima
[    3.676533] evm: security.capability
[    3.677078] evm: HMAC attrs: 0x1
[    3.739415] alg: No test for 842 (842-scomp)
[    3.739988] alg: No test for 842 (842-generic)
[    3.767874] usb 1-1: new full-speed USB device number 2 using xhci_hcd
[    3.814911] usb 7-1: new high-speed USB device number 2 using xhci_hcd
[    3.819325] PM:   Magic number: 3:509:338
[    3.819949] thermal thermal_zone1: hash matches
[    3.820517] tty tty59: hash matches
[    3.821075] acpi ACPI0007:00: hash matches
[    3.821640] memory memory188: hash matches
[    3.827251] RAS: Correctable Errors collector initialized.
[    3.827959] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    3.828724] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    3.829366] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    3.829961] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    3.830536] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    3.831162] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    3.831774] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    3.832380] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
[    3.832914] clk: Disabling unused clocks
[    3.834832] Freeing unused decrypted memory: 2028K
[    3.836676] Freeing unused kernel image (initmem) memory: 3944K
[    3.837289] Write protecting the kernel read-only data: 34816k
[    3.848397] Freeing unused kernel image (rodata/data gap) memory: 1928K
[    3.920182] usb 1-1: New USB device found, idVendor=046d, idProduct=c548, bcdDevice= 5.01
[    3.921326] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.922113] usb 1-1: Product: USB Receiver
[    3.922602] usb 1-1: Manufacturer: Logitech
[    3.941614] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-1/1-1:1.0/0003:046D:C548.0001/input/input3
[    3.994179] hid-generic 0003:046D:C548.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:c1:00.3-1/input0
[    3.999679] input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-1/1-1:1.1/0003:046D:C548.0002/input/input4
[    4.000461] input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-1/1-1:1.1/0003:046D:C548.0002/input/input5
[    4.052994] input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-1/1-1:1.1/0003:046D:C548.0002/input/input6
[    4.054106] hid-generic 0003:046D:C548.0002: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:c1:00.3-1/input1
[    4.059586] hid-generic 0003:046D:C548.0003: hiddev96,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:c1:00.3-1/input2
[    4.173867] usb 1-4: new full-speed USB device number 3 using xhci_hcd
[    4.331188] usb 1-4: New USB device found, idVendor=27c6, idProduct=609c, bcdDevice= 1.00
[    4.332337] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.332855] usb 1-4: Product: Goodix USB2.0 MISC
[    4.333363] usb 1-4: Manufacturer: Goodix Technology Co., Ltd.
[    4.333870] usb 1-4: SerialNumber: UIDD5F04A7B_XXXX_MOC_B0
[    4.455868] usb 1-5: new high-speed USB device number 4 using xhci_hcd
[    4.586538] usb 1-5: New USB device found, idVendor=0e8d, idProduct=e616, bcdDevice= 1.00
[    4.587740] usb 1-5: New USB device strings: Mfr=5, Product=6, SerialNumber=7
[    4.588334] usb 1-5: Product: Wireless_Device
[    4.588837] usb 1-5: Manufacturer: MediaTek Inc.
[    4.589331] usb 1-5: SerialNumber: 000000000
[    5.140011] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    5.140651] Run /init as init process
[    5.141834]   with arguments:
[    5.141838]     /init
[    5.141841]     placeholder
[    5.141844]   with environment:
[    5.141846]     HOME=/
[    5.141849]     TERM=linux
[    5.167475] systemd[1]: systemd 254.7-1.fc39 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[    5.168549] systemd[1]: Detected virtualization vm-other.
[    5.169080] systemd[1]: Detected architecture x86-64.
[    5.169592] systemd[1]: Running in initrd.
[    5.172792] systemd[1]: No hostname configured, using default hostname.
[    5.173462] systemd[1]: Hostname set to <fedora>.
[    5.207794] usb 7-1: New USB device found, idVendor=17ef, idProduct=a392, bcdDevice= d.24
[    5.208898] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.209752] usb 7-1: Product: USB2.0 Hub
[    5.210276] usb 7-1: Manufacturer: VIA Labs, Inc.
[    5.268344] hub 7-1:1.0: USB hub found
[    5.269161] hub 7-1:1.0: 4 ports detected
[    5.285405] systemd[1]: bpf-lsm: LSM BPF program attached
[    5.330850] usb 8-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd
[    5.395298] systemd[1]: Queued start job for default target initrd.target.
[    5.402828] systemd[1]: Reached target initrd-usr-fs.target - Initrd /usr File System.
[    5.404153] systemd[1]: Reached target slices.target - Slice Units.
[    5.405285] systemd[1]: Reached target swap.target - Swaps.
[    5.406463] systemd[1]: Reached target timers.target - Timer Units.
[    5.407704] systemd[1]: Listening on dbus.socket - D-Bus System Message Bus Socket.
[    5.409012] systemd[1]: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
[    5.410378] systemd[1]: Listening on systemd-journald.socket - Journal Socket.
[    5.411768] systemd[1]: Listening on systemd-udevd-control.socket - udev Control Socket.
[    5.413165] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
[    5.414448] systemd[1]: Reached target sockets.target - Socket Units.
[    5.417373] systemd[1]: Starting kmod-static-nodes.service - Create List of Static Device Nodes...
[    5.418771] systemd[1]: memstrack.service - Memstrack Anylazing Service was skipped because no trigger condition checks were met.
[    5.421707] systemd[1]: Starting systemd-journald.service - Journal Service...
[    5.424450] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...
[    5.427152] systemd[1]: Starting systemd-sysusers.service - Create System Users...
[    5.429861] systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup...
[    5.431634] systemd-journald[343]: Collecting audit messages is disabled.
[    5.448268] fuse: init (API version 7.39)
[    5.450991] i2c_dev: i2c /dev entries driver
[    5.455473] usb 8-1: New USB device found, idVendor=17ef, idProduct=a391, bcdDevice= d.24
[    5.456175] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.456856] usb 8-1: Product: USB3.1 Hub
[    5.457527] usb 8-1: Manufacturer: VIA Labs, Inc.
[    5.460646] xen:xen_evtchn: Event-channel device installed
[    5.484211] xen_pciback: backend is vpci
[    5.491794] hub 8-1:1.0: USB hub found
[    5.492715] hub 8-1:1.0: 4 ports detected
[    5.507117] systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes.
[    5.509334] systemd[1]: Started systemd-journald.service - Journal Service.
[    5.513755] Rounding down aligned max_sectors from 4294967295 to 4294967288
[    5.514496] db_root: cannot open: /etc/target
[    5.520192] xen_acpi_processor: Uploading Xen processor PM info
[    6.034860] usb 7-1.3: new high-speed USB device number 3 using xhci_hcd
[    6.178506] usb 7-1.3: New USB device found, idVendor=17ef, idProduct=a394, bcdDevice= d.23
[    6.179957] usb 7-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.181377] usb 7-1.3: Product: USB2.0 Hub
[    6.182785] usb 7-1.3: Manufacturer: VIA Labs, Inc.
[    6.226975] hub 7-1.3:1.0: USB hub found
[    6.228755] hub 7-1.3:1.0: 4 ports detected
[    6.258918] usb 8-1.1: new SuperSpeed USB device number 3 using xhci_hcd
[    6.273627] usb 8-1.1: New USB device found, idVendor=17ef, idProduct=a387, bcdDevice=31.03
[    6.275001] usb 8-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[    6.276363] usb 8-1.1: Product: USB-C Dock Ethernet
[    6.277712] usb 8-1.1: Manufacturer: Realtek
[    6.279071] usb 8-1.1: SerialNumber: 301000001
[    6.399571] usb 8-1.3: new SuperSpeed Plus Gen 2x1 USB device number 4 using xhci_hcd
[    6.432260] usb 8-1.3: New USB device found, idVendor=17ef, idProduct=a393, bcdDevice= d.23
[    6.433735] usb 8-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.435192] usb 8-1.3: Product: USB3.1 Hub
[    6.436957] usb 8-1.3: Manufacturer: VIA Labs, Inc.
[    6.445418] acpi FRMW0004:00: GPIO: looking up 0 in _CRS
[    6.445485] amd_gpio AMDI0030:00: Invalid config param 0014
[    6.445489] gpio gpiochip0: Persistence not supported for GPIO 84
[    6.445983] acpi FRMW0005:00: GPIO: looking up 0 in _CRS
[    6.446971] acpi PIXA3854:00: GPIO: looking up 0 in _CRS
[    6.446987] amd_gpio AMDI0030:00: Invalid config param 0014
[    6.446997] gpio gpiochip0: Persistence not supported for GPIO 5
[    6.447025] amd_gpio AMDI0030:00: Invalid config param 0014
[    6.447030] gpio gpiochip0: Persistence not supported for GPIO 8
[    6.470213] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[    6.471338] hub 8-1.3:1.0: USB hub found
[    6.471396] sp5100-tco sp5100-tco: Using 0xfeb00000 for watchdog MMIO address
[    6.472464] hub 8-1.3:1.0: 4 ports detected
[    6.476169] ccp 0000:c1:00.2: enabling device (0000 -> 0002)
[    6.476964] xen_register_gsi: xen: registering gsi 36 triggering 0 polarity 1
[    6.476966] xen_register_pirq: before xen_irq_from_gsi: gsi 36 triggering 0 set_pirq 1
[    6.476995] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 36 triggering 0 shareable 1 name ioapic-level
[    6.477016] xen_register_pirq: xen: --> pirq=36 -> irq=36 (gsi=36)
[    6.477018] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 36, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[    6.478244] sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
[    6.487556] ccp 0000:c1:00.2: tee: ring init command failed (0x00000006)
[    6.488432] ccp 0000:c1:00.2: tee: failed to init ring buffer
[    6.489276] ccp 0000:c1:00.2: tee initialization failed
[    6.490091] ccp 0000:c1:00.2: psp initialization failed
[    6.511297] GPIO 8 is active: 0x18141b00
[    6.594051] input: PIXA3854:00 093A:0274 Mouse as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0004/input/input7
[    6.595827] input: PIXA3854:00 093A:0274 Touchpad as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0004/input/input8
[    6.596058] hid-generic 0018:093A:0274.0004: input,hidraw3: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00
[    6.736650] input: PIXA3854:00 093A:0274 Mouse as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0004/input/input9
[    6.738732] input: PIXA3854:00 093A:0274 Touchpad as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0004/input/input10
[    6.740825] hid-multitouch 0018:093A:0274.0004: input,hidraw3: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00
[    7.021071] usb 7-1.3.3: new high-speed USB device number 4 using xhci_hcd
[    7.181839] usb 7-1.3.3: New USB device found, idVendor=17ef, idProduct=a395, bcdDevice=60.70
[    7.181954] usb 7-1.3.3: New USB device strings: Mfr=10, Product=11, SerialNumber=0
[    7.182002] usb 7-1.3.3: Product: USB2.0 Hub
[    7.182029] usb 7-1.3.3: Manufacturer: Lenovo
[    7.220014] hub 7-1.3.3:1.0: USB hub found
[    7.220761] hub 7-1.3.3:1.0: 4 ports detected
[    7.514391] usb 7-1.3.3.1: new full-speed USB device number 5 using xhci_hcd
[    7.618898] usb 7-1.3.3.1: New USB device found, idVendor=04b4, idProduct=521a, bcdDevice= 0.00
[    7.618981] usb 7-1.3.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    7.619022] usb 7-1.3.3.1: Product: USB-I2C Bridge
[    7.619051] usb 7-1.3.3.1: Manufacturer: Cypress Semiconductor
[    7.739398] usb 7-1.3.3.2: new full-speed USB device number 6 using xhci_hcd
[    7.861913] usb 7-1.3.3.2: New USB device found, idVendor=17ef, idProduct=30d1, bcdDevice= 0.42
[    7.861987] usb 7-1.3.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    7.862025] usb 7-1.3.3.2: Product: ThinkPad USB-C Dock Gen2 USB Audio
[    7.862059] usb 7-1.3.3.2: Manufacturer: Lenovo
[    7.862085] usb 7-1.3.3.2: SerialNumber: 000000000000
[    7.967374] hid-generic 0003:17EF:30D1.0005: hiddev97,hidraw4: USB HID v1.11 Device [Lenovo ThinkPad USB-C Dock Gen2 USB Audio] on usb-0000:c3:00.4-1.3.3.2/input3
[   11.804373] i2c_hid_acpi i2c-FRMW0004:00: failed to reset device: -61
[   11.804374] i2c_hid_acpi i2c-FRMW0005:00: failed to reset device: -61
[   17.948362] i2c_hid_acpi i2c-FRMW0004:00: failed to reset device: -61
[   17.948362] i2c_hid_acpi i2c-FRMW0005:00: failed to reset device: -61
[   24.092360] i2c_hid_acpi i2c-FRMW0004:00: failed to reset device: -61
[   24.092360] i2c_hid_acpi i2c-FRMW0005:00: failed to reset device: -61
[   30.236338] i2c_hid_acpi i2c-FRMW0004:00: failed to reset device: -61
[   30.236337] i2c_hid_acpi i2c-FRMW0005:00: failed to reset device: -61
[   31.260334] i2c_hid_acpi i2c-FRMW0004:00: can't add hid device: -61
[   31.260333] i2c_hid_acpi i2c-FRMW0005:00: can't add hid device: -61
[   31.279635] i2c_hid_acpi: probe of i2c-FRMW0004:00 failed with error -61
[   31.280084] i2c_hid_acpi: probe of i2c-FRMW0005:00 failed with error -61
[   31.288999] usbcore: registered new device driver r8152-cfgselector
[   31.292174] ACPI: video: Video Device [VGA] (multi-head: yes  rom: no  post: no)
[   31.292989] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:16/LNXVIDEO:00/input/input11
[   31.313050] nvme 0000:02:00.0: platform quirk: setting simple suspend
[   31.313274] nvme nvme0: pci function 0000:02:00.0
[   31.313709] xen_register_gsi: xen: registering gsi 42 triggering 0 polarity 1
[   31.313713] xen_register_pirq: before xen_irq_from_gsi: gsi 42 triggering 0 set_pirq 1
[   31.313733] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 42 triggering 0 shareable 1 name ioapic-level
[   31.313762] xen_register_pirq: xen: --> pirq=42 -> irq=42 (gsi=42)
[   31.313765] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 42, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[   31.352932] nvme nvme0: 16/0/0 default/read/poll queues
[   31.359717]  nvme0n1: p1 p2 p3 p4
[   31.384874] BTRFS: device fsid 71b1dc59-ea00-484c-b5e4-ee77ede771db devid 1 transid 6106 /dev/nvme0n1p1 scanned by (udev-worker) (526)
[   31.458995] r8152-cfgselector 8-1.1: reset SuperSpeed USB device number 3 using xhci_hcd
[   31.485713] r8152 8-1.1:1.0: load rtl8153b-2 v2 04/27/23 successfully
[   31.514621] r8152 8-1.1:1.0 eth0: v1.12.13
[   31.514701] usbcore: registered new interface driver r8152
[   31.547423] r8152 8-1.1:1.0 enp195s0f4u1u1: renamed from eth0
[   32.945238] [drm] amdgpu kernel modesetting enabled.
[   32.961317] amdgpu: Virtual CRAT table created for CPU
[   32.961353] amdgpu: Topology: Add CPU node
[   32.961702] amdgpu 0000:c1:00.0: enabling device (0006 -> 0007)
[   32.961775] xen_register_gsi: xen: registering gsi 38 triggering 0 polarity 1
[   32.961777] xen_register_pirq: before xen_irq_from_gsi: gsi 38 triggering 0 set_pirq 1
[   32.961788] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 38, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[   32.961792] Already setup the GSI :38
[   32.961830] [drm] initializing kernel modesetting (IP DISCOVERY 0x1002:0x15BF 0xF111:0x0006 0xC4).
[   32.962050] [drm] register mmio base: 0x90500000
[   32.962081] [drm] register mmio size: 524288
[   32.964925] [drm] add ip block number 0 <soc21_common>
[   32.964958] [drm] add ip block number 1 <gmc_v11_0>
[   32.964969] [drm] add ip block number 2 <ih_v6_0>
[   32.964978] [drm] add ip block number 3 <psp>
[   32.964987] [drm] add ip block number 4 <smu>
[   32.964995] [drm] add ip block number 5 <dm>
[   32.965004] [drm] add ip block number 6 <gfx_v11_0>
[   32.965013] [drm] add ip block number 7 <sdma_v6_0>
[   32.965022] [drm] add ip block number 8 <vcn_v4_0>
[   32.965031] [drm] add ip block number 9 <jpeg_v4_0>
[   32.965040] [drm] add ip block number 10 <mes_v11_0>
[   32.965292] amdgpu 0000:c1:00.0: amdgpu: Fetched VBIOS from VFCT
[   32.965327] amdgpu: ATOM BIOS: 113-PHXGENERIC-001
[   32.995413] [drm] VCN(0) encode/decode are enabled in VM mode
[   33.007497] amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_early_init [amdgpu]] JPEG decode is enabled in VM mode
[   33.015913] Console: switching to colour dummy device 80x25
[   33.017734] amdgpu 0000:c1:00.0: vgaarb: deactivate vga console
[   33.017742] amdgpu 0000:c1:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
[   33.017793] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
[   33.017826] amdgpu 0000:c1:00.0: amdgpu: VRAM: 512M 0x0000008000000000 - 0x000000801FFFFFFF (512M used)
[   33.017833] amdgpu 0000:c1:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[   33.017840] amdgpu 0000:c1:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF
[   33.017857] [drm] Detected VRAM RAM=512M, BAR=512M
[   33.017862] [drm] RAM width 128bits DDR5
[   33.081259] [drm] amdgpu: 512M of VRAM memory ready
[   33.081273] [drm] amdgpu: 31159M of GTT memory ready.
[   33.081304] [drm] GART: num cpu pages 131072, num gpu pages 131072
[   33.081855] [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
[   33.082579] [drm] Loading DMUB firmware via PSP: version=0x08002A81
[   33.088436] [drm] Found VCN firmware Version ENC: 1.10 DEC: 5 VEP: 0 Revision: 0
[   33.088450] amdgpu 0000:c1:00.0: amdgpu: Will use PSP to load VCN firmware
[   33.114244] [drm] reserve 0x4000000 from 0x8018000000 for PSP TMR
[   33.629701] amdgpu 0000:c1:00.0: amdgpu: RAS: optional ras ta ucode is not available
[   33.638277] amdgpu 0000:c1:00.0: amdgpu: RAP: optional rap ta ucode is not available
[   33.638309] amdgpu 0000:c1:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[   33.672591] amdgpu 0000:c1:00.0: amdgpu: SMU is initialized successfully!
[   33.673698] [drm] Display Core v3.2.247 initialized on DCN 3.1.4
[   33.673717] [drm] DP-HDMI FRL PCON supported
[   33.676123] [drm] DMUB hardware initialized: version=0x08002A81
[   33.763283] [drm] PSR support 1, DC PSR ver 0, sink PSR ver 3 DPCD caps 0x7b su_y_granularity 4
[   33.829816] [drm] DM_MST: Differing MST start on aconnector: 0000000085716dab [id: 112]
[   33.832901] [drm] kiq ring mec 3 pipe 1 q 0
[   33.835708] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[   33.835761] amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
[   33.849922] amdgpu: HMM registered 512MB device memory
[   33.853383] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[   33.853411] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[   33.853542] amdgpu: Virtual CRAT table created for GPU
[   33.853694] amdgpu: Topology: Add dGPU node [0x15bf:0x1002]
[   33.853700] kfd kfd: amdgpu: added device 1002:15bf
[   33.853715] amdgpu 0000:c1:00.0: amdgpu: SE 1, SH per SE 2, CU per SH 6, active_cu_number 12
[   33.853881] amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[   33.853887] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[   33.853893] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[   33.853899] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[   33.853905] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[   33.853910] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[   33.853916] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[   33.853921] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[   33.853927] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[   33.853933] amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[   33.853939] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[   33.853944] amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
[   33.853950] amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
[   33.858872] [drm] ring gfx_32768.1.1 was added
[   33.859389] [drm] ring compute_32768.2.2 was added
[   33.859889] [drm] ring sdma_32768.3.3 was added
[   33.859965] [drm] ring gfx_32768.1.1 ib test pass
[   33.860020] [drm] ring compute_32768.2.2 ib test pass
[   33.860084] [drm] ring sdma_32768.3.3 ib test pass
[   33.863361] [drm] Initialized amdgpu 3.54.0 20150101 for 0000:c1:00.0 on minor 0
[   33.870240] fbcon: amdgpudrmfb (fb0) is primary device
[   33.870438] [drm] DSC precompute is not needed.
[   34.798762] Console: switching to colour frame buffer device 282x94
[   34.837995] amdgpu 0000:c1:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[   35.044417] [drm] Downstream port present 1, type 2
[   35.684903] BTRFS info (device nvme0n1p1): first mount of filesystem 71b1dc59-ea00-484c-b5e4-ee77ede771db
[   35.684990] BTRFS info (device nvme0n1p1): using crc32c (crc32c-intel) checksum algorithm
[   35.685030] BTRFS info (device nvme0n1p1): using free space tree
[   35.705421] BTRFS info (device nvme0n1p1): enabling ssd optimizations
[   35.705467] BTRFS info (device nvme0n1p1): auto enabling async discard
[   36.428373] ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
[   36.545992] systemd-journald[343]: Received SIGTERM from PID 1 (systemd).
[   36.704556] audit: type=1404 audit(1703089283.612:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
[   36.758757] SELinux:  policy capability network_peer_controls=1
[   36.759436] SELinux:  policy capability open_perms=1
[   36.760152] SELinux:  policy capability extended_socket_class=1
[   36.760683] SELinux:  policy capability always_check_network=0
[   36.761337] SELinux:  policy capability cgroup_seclabel=1
[   36.761897] SELinux:  policy capability nnp_nosuid_transition=1
[   36.762402] SELinux:  policy capability genfs_seclabel_symlinks=1
[   36.762899] SELinux:  policy capability ioctl_skip_cloexec=0
[   36.820222] audit: type=1403 audit(1703089283.728:3): auid=4294967295 ses=4294967295 lsm=selinux res=1
[   36.823639] systemd[1]: Successfully loaded SELinux policy in 119.603ms.
[   36.912835] systemd[1]: Relabeled /dev, /dev/shm, /run, /sys/fs/cgroup in 44.046ms.
[   36.924193] systemd[1]: systemd 254.7-1.fc39 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[   36.930207] systemd[1]: Detected virtualization vm-other.
[   36.931715] systemd[1]: Detected architecture x86-64.
[   37.075396] systemd[1]: bpf-lsm: LSM BPF program attached
[   37.289254] systemd-sysv-generator[745]: SysV service '/etc/rc.d/init.d/xencommons' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !
[   37.318417] zram: Added device: zram0
[   37.626898] systemd[1]: initrd-switch-root.service: Deactivated successfully.
[   37.636392] systemd[1]: Stopped initrd-switch-root.service - Switch Root.
[   37.650185] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
[   37.653676] systemd[1]: Created slice machine.slice - Virtual Machine and Container Slice.
[   37.657102] systemd[1]: Created slice system-getty.slice - Slice /system/getty.
[   37.660839] systemd[1]: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty.
[   37.664476] systemd[1]: Created slice system-sshd\x2dkeygen.slice - Slice /system/sshd-keygen.
[   37.668147] systemd[1]: Created slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck.
[   37.671967] systemd[1]: Created slice system-systemd\x2dzram\x2dsetup.slice - Slice /system/systemd-zram-setup.
[   37.675833] systemd[1]: Created slice user.slice - User and Session Slice.
[   37.678366] systemd[1]: systemd-ask-password-plymouth.path: Deactivated successfully.
[   37.680111] systemd[1]: Stopped systemd-ask-password-plymouth.path.
[   37.683496] systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
[   37.685636] systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
[   37.687344] systemd[1]: Stopped target initrd-switch-root.target - Switch Root.
[   37.689870] systemd[1]: Stopped target initrd-fs.target - Initrd File Systems.
[   37.691480] systemd[1]: Stopped target initrd-root-fs.target - Initrd Root File System.
[   37.692750] systemd[1]: Reached target integritysetup.target - Local Integrity Protected Volumes.
[   37.694129] systemd[1]: Reached target slices.target - Slice Units.
[   37.695298] systemd[1]: Reached target veritysetup.target - Local Verity Protected Volumes.
[   37.701423] systemd[1]: Listening on dm-event.socket - Device-mapper event daemon FIFOs.
[   37.719004] systemd[1]: Listening on lvm2-lvmpolld.socket - LVM2 poll daemon socket.
[   37.727200] systemd[1]: Listening on systemd-coredump.socket - Process Core Dump Socket.
[   37.729779] systemd[1]: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe.
[   37.736227] systemd[1]: Listening on systemd-journald-audit.socket - Journal Audit Socket.
[   37.741134] systemd[1]: Listening on systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket.
[   37.746968] systemd[1]: Listening on systemd-udevd-control.socket - udev Control Socket.
[   37.749776] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
[   37.754596] systemd[1]: Listening on systemd-userdbd.socket - User Database Manager Socket.
[   37.759378] systemd[1]: dev-hugepages.mount - Huge Pages File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/mm/hugepages).
[   37.779139] systemd[1]: Mounting dev-mqueue.mount - POSIX Message Queue File System...
[   37.795049] systemd[1]: Mounting proc-xen.mount - Mount /proc/xen files...
[   37.805431] systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System...
[   37.812891] systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace File System...
[   37.814183] systemd[1]: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab).
[   37.814831] systemd[1]: iscsi-starter.service was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/var/lib/iscsi/nodes).
[   37.820548] systemd[1]: Starting kmod-static-nodes.service - Create List of Static Device Nodes...
[   37.827139] systemd[1]: Starting lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
[   37.834185] systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs...
[   37.840710] systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
[   37.848429] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
[   37.854962] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
[   37.862915] systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse...
[   37.869302] systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
[   37.870505] systemd[1]: Stopping plymouth-start.service...
[   37.874303] systemd[1]: plymouth-switch-root.service: Deactivated successfully.
[   37.875648] systemd[1]: Stopped plymouth-switch-root.service.
[   37.881354] systemd[1]: systemd-fsck-root.service: Deactivated successfully.
[   37.882137] systemd[1]: Stopped systemd-fsck-root.service - File System Check on Root Device.
[   37.886215] loop: module loaded
[   37.889300] systemd[1]: Starting systemd-journald.service - Journal Service...
[   37.897019] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...
[   37.904359] systemd[1]: Starting systemd-network-generator.service - Generate network units from Kernel command line...
[   37.907463] systemd[1]: systemd-pcrmachine.service - TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
[   37.914436] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
[   37.915750] systemd-journald[767]: Collecting audit messages is enabled.
[   37.923720] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices...
[   37.925607] systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
[   37.926396] systemd[1]: Stopped systemd-vconsole-setup.service - Virtual Console Setup.
[   37.928434] audit: type=1131 audit(1703089284.836:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   37.934345] systemd[1]: Started systemd-journald.service - Journal Service.
[   37.936652] audit: type=1130 audit(1703089284.844:5): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   38.054001] audit: type=1131 audit(1703089284.962:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   38.165584] audit: type=1130 audit(1703089285.073:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   38.255788] audit: type=1130 audit(1703089285.163:8): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   38.290161] audit: type=1130 audit(1703089285.198:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   38.292707] audit: type=1131 audit(1703089285.198:10): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   38.306137] audit: type=1130 audit(1703089285.214:11): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=modprobe@dm_mod comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   38.546875] systemd-journald[767]: Received client request to flush runtime journal.
[   38.603230] systemd-journald[767]: /var/log/journal/c80b79eae1794302b76e09e5265106e3/system.journal: Journal file uses a different sequence number ID, rotating.
[   38.606672] systemd-journald[767]: Rotating system journal.
[   39.074619] zram0: detected capacity change from 0 to 16777216
[   39.163912] amd-pmf AMDI0102:00: registered PMF device successfully
[   39.180829] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[   39.182652] piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection
[   39.188036] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
[   39.200288] ACPI: bus type thunderbolt registered
[   39.201949] xen_register_gsi: xen: registering gsi 44 triggering 0 polarity 1
[   39.201952] xen_register_pirq: before xen_irq_from_gsi: gsi 44 triggering 0 set_pirq 1
[   39.201972] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 44 triggering 0 shareable 1 name ioapic-level
[   39.202579] input: PC Speaker as /devices/platform/pcspkr/input/input12
[   39.203551] xen_register_pirq: xen: --> pirq=44 -> irq=44 (gsi=44)
[   39.203863] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 44, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[   39.251528] xen_register_gsi: xen: registering gsi 45 triggering 0 polarity 1
[   39.251535] xen_register_pirq: before xen_irq_from_gsi: gsi 45 triggering 0 set_pirq 1
[   39.251571] xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi 45 triggering 0 shareable 1 name ioapic-level
[   39.251604] xen_register_pirq: xen: --> pirq=45 -> irq=45 (gsi=45)
[   39.251606] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 45, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[   39.256570] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   39.268060] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   39.299450] Adding 8388604k swap on /dev/zram0.  Priority:100 extents:1 across:8388604k SSDsc
[   39.330768] Bluetooth: Core ver 2.22
[   39.335414] NET: Registered PF_BLUETOOTH protocol family
[   39.337202] Bluetooth: HCI device and connection manager initialized
[   39.339137] Bluetooth: HCI socket layer initialized
[   39.343261] Bluetooth: L2CAP socket layer initialized
[   39.344808] Bluetooth: SCO socket layer initialized
[   39.363395] usb 1-5: using ACPI '\_SB.PCI0.GP17.XHC0.RHUB.PRT5' for 'reset' GPIO lookup
[   39.363410] acpi device:29: GPIO: looking up reset-gpios
[   39.363413] acpi device:29: GPIO: looking up reset-gpio
[   39.363415] usb 1-5: using lookup tables for GPIO lookup
[   39.363417] usb 1-5: No GPIO consumer reset found
[   39.363571] usbcore: registered new interface driver btusb
[   39.369259] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20231120183620
[   39.511066] Bluetooth: hci0: Device setup in 143958 usecs
[   39.513384] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[   39.573971] Bluetooth: hci0: AOSP extensions version v1.00
[   39.576040] Bluetooth: hci0: AOSP quality report is supported
[   39.609806] mt7921e 0000:01:00.0: enabling device (0000 -> 0002)
[   39.612306] xen_register_gsi: xen: registering gsi 46 triggering 0 polarity 1
[   39.612313] xen_register_pirq: before xen_irq_from_gsi: gsi 46 triggering 0 set_pirq 1
[   39.612357] xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: 46, setup_gsi.triggering: 1, setup_gsi.polarity: 1
[   39.612371] Already setup the GSI :46
[   39.647661] mt7921e 0000:01:00.0: ASIC revision: 79220010
[   39.732611] mt7921e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20231120183400a

[   39.768922] mt7921e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20231120183441
[   40.224298] RPC: Registered named UNIX socket transport module.
[   40.225758] RPC: Registered udp transport module.
[   40.226795] RPC: Registered tcp transport module.
[   40.227601] RPC: Registered tcp-with-tls transport module.
[   40.228353] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   40.584280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   40.585545] Bluetooth: BNEP filters: protocol multicast
[   40.588311] Bluetooth: BNEP socket layer initialized
[   40.591552] Bluetooth: MGMT ver 1.22
[   40.899078] mt7921e 0000:01:00.0 wlp1s0: renamed from wlan0
[   40.987298] NET: Registered PF_QIPCRTR protocol family
[   41.429820] r8152 8-1.1:1.0 enp195s0f4u1u1: carrier on
[   45.545611] wlp1s0: authenticate with 60:22:32:37:20:46
[   46.051225] wlp1s0: send auth to 60:22:32:37:20:46 (try 1/3)
[   46.171592] wlp1s0: authenticate with 60:22:32:37:20:46
[   46.181255] wlp1s0: send auth to 60:22:32:37:20:46 (try 1/3)
[   46.212961] wlp1s0: authenticated
[   46.216890] wlp1s0: associate with 60:22:32:37:20:46 (try 1/3)
[   46.231035] wlp1s0: RX AssocResp from 60:22:32:37:20:46 (capab=0x1111 status=0 aid=10)
[   46.265679] wlp1s0: associated
[   46.267046] wlp1s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 60:22:32:37:20:46
[   60.011874] systemd-journald[767]: /var/log/journal/c80b79eae1794302b76e09e5265106e3/user-1000.journal: Journal file uses a different sequence number ID, rotating.

[-- Attachment #5: linux-debug_xen_irq_setup.diff --]
[-- Type: text/x-patch, Size: 2045 bytes --]

diff --git a/arch/x86/pci/xen.c b/arch/x86/pci/xen.c
index 652cd53e77f6..ccee3e331eb8 100644
--- a/arch/x86/pci/xen.c
+++ b/arch/x86/pci/xen.c
@@ -69,6 +69,8 @@ static int xen_register_pirq(u32 gsi, int triggering, bool set_pirq)
 	int shareable = 0;
 	char *name;
 
+	printk(KERN_DEBUG "xen_register_pirq: before xen_irq_from_gsi: gsi %u triggering %i set_pirq %d\n", gsi, triggering, set_pirq);
+
 	irq = xen_irq_from_gsi(gsi);
 	if (irq > 0)
 		return irq;
@@ -94,12 +96,13 @@ static int xen_register_pirq(u32 gsi, int triggering, bool set_pirq)
 		shareable = 1;
 		name = "ioapic-level";
 	}
+	printk(KERN_DEBUG "xen_register_pirq: after HYPERVISOR_physdev_op, before xen_bind_pirq_gsi_to_irq: gsi %u triggering %i shareable %i name %s\n", gsi, triggering, shareable, name);
 
 	irq = xen_bind_pirq_gsi_to_irq(gsi, map_irq.pirq, shareable, name);
 	if (irq < 0)
 		goto out;
 
-	printk(KERN_DEBUG "xen: --> pirq=%d -> irq=%d (gsi=%d)\n", map_irq.pirq, irq, gsi);
+	printk(KERN_DEBUG "xen_register_pirq: xen: --> pirq=%d -> irq=%d (gsi=%d)\n", map_irq.pirq, irq, gsi);
 out:
 	return irq;
 }
@@ -123,7 +126,7 @@ static int xen_register_gsi(u32 gsi, int triggering, int polarity)
 	if (!xen_pv_domain())
 		return -1;
 
-	printk(KERN_DEBUG "xen: registering gsi %u triggering %d polarity %d\n",
+	printk(KERN_DEBUG "xen_register_gsi: xen: registering gsi %u triggering %i polarity %i\n",
 			gsi, triggering, polarity);
 
 	irq = xen_register_pirq(gsi, triggering, true);
@@ -132,6 +135,8 @@ static int xen_register_gsi(u32 gsi, int triggering, int polarity)
 	setup_gsi.triggering = (triggering == ACPI_EDGE_SENSITIVE ? 0 : 1);
 	setup_gsi.polarity = (polarity == ACPI_ACTIVE_HIGH ? 0 : 1);
 
+    printk(KERN_DEBUG "xen_register_gsi: Before HYPERVISOR_physdev_op  setup_gsi.gsi: %u, setup_gsi.triggering: %i, setup_gsi.polarity: %i\n", setup_gsi.gsi, setup_gsi.triggering, setup_gsi.polarity);
+   
 	rc = HYPERVISOR_physdev_op(PHYSDEVOP_setup_gsi, &setup_gsi);
 	if (rc == -EEXIST)
 		printk(KERN_INFO "Already setup the GSI :%d\n", gsi);

[-- Attachment #6: xl-dmesg-xen-4.17.3-pre-6.6.7xen-irq-dbg-1+ --]
[-- Type: application/octet-stream, Size: 23388 bytes --]

(XEN) parameter "irq_deadline_ms" unknown!
 Xen 4.17.3-pre
(XEN) Xen version 4.17.3-pre (sch@) (gcc (GCC) 13.2.1 20231205 (Red Hat 13.2.1-6)) debug=y Mon Dec 18 16:47:31 CET 2023
(XEN) Latest ChangeSet: Mon Dec 18 16:23:14 2023 +0100 git:89612cf732
(XEN) build-id: 7b05b3f90c160aef7b340d1ecd784b37e1507cfd
(XEN) Bootloader: GRUB 2.06
(XEN) Command line: placeholder irq_deadline_ms=40 no-real-mode edd=off
(XEN) Xen image load base address: 0x4f400000
(XEN) Video information:
(XEN)  VGA is graphics mode 2256x1504, 32 bpp
(XEN) Disc information:
(XEN)  Found 0 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) CPU Vendor: AMD, Family 25 (0x19), Model 116 (0x74), Stepping 1 (raw 00a70f41)
(XEN) Enabling Supervisor Shadow Stacks
(XEN) EFI RAM map:
(XEN)  [0000000000000000, 000000000009efff] (usable)
(XEN)  [000000000009f000, 00000000000bffff] (reserved)
(XEN)  [0000000000100000, 0000000009afffff] (usable)
(XEN)  [0000000009b00000, 0000000009dfffff] (reserved)
(XEN)  [0000000009e00000, 0000000009efffff] (usable)
(XEN)  [0000000009f00000, 0000000009f3bfff] (ACPI NVS)
(XEN)  [0000000009f3c000, 000000004235ffff] (usable)
(XEN)  [0000000042360000, 000000004455ffff] (reserved)
(XEN)  [0000000044560000, 0000000044568fff] (usable)
(XEN)  [0000000044569000, 000000004456cfff] (reserved)
(XEN)  [000000004456d000, 000000004456efff] (usable)
(XEN)  [000000004456f000, 000000004456ffff] (reserved)
(XEN)  [0000000044570000, 000000005077efff] (usable)
(XEN)  [000000005077f000, 0000000052f7efff] (reserved)
(XEN)  [0000000052f7f000, 000000005af7efff] (ACPI NVS)
(XEN)  [000000005af7f000, 000000005affefff] (ACPI data)
(XEN)  [000000005afff000, 000000005affffff] (usable)
(XEN)  [000000005b000000, 000000005bffffff] (reserved)
(XEN)  [000000005d790000, 000000005d7effff] (reserved)
(XEN)  [000000005d7f5000, 000000005fffffff] (reserved)
(XEN)  [00000000c0300000, 00000000c03fffff] (reserved)
(XEN)  [00000000fed80000, 00000000fed80fff] (reserved)
(XEN)  [00000000ff000000, 00000000ffffffff] (reserved)
(XEN)  [0000000100000000, 000000107e2fffff] (usable)
(XEN)  [0000001080000000, 00000010c01fffff] (reserved)
(XEN) ACPI: RSDP 5AFFE014, 0024 (r2 INSYDE)
(XEN) ACPI: XSDT 5AF9E228, 016C (r1 INSYDE EDK2            2       1000013)
(XEN) ACPI: FACP 5AFEF000, 010C (r5 INSYDE EDK2            2 ACPI    40000)
(XEN) ACPI Warning (tbfadt-0459): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000000/1 [20070126]
(XEN) ACPI: DSDT 5AFDF000, 93A6 (r2 INSYDE EDK2            2 ACPI    40000)
(XEN) ACPI: FACS 5AEB7000, 0040
(XEN) ACPI: UEFI 5AF67000, 01CF (r1 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFF4000, 8416 (r2 INSYDE EDK2            2 ACPI    40000)
(XEN) ACPI: SSDT 5AFF2000, 0ABD (r2 INSYDE EDK2         1000 ACPI    40000)
(XEN) ACPI: ASF! 5AFF1000, 00A5 (r32 INSYDE EDK2            2 ACPI    40000)
(XEN) ACPI: BOOT 5AFF0000, 0028 (r1 INSYDE EDK2            2 ACPI    40000)
(XEN) ACPI: HPET 5AFEE000, 0038 (r1 INSYDE EDK2            2 ACPI    40000)
(XEN) ACPI: APIC 5AFED000, 0138 (r3 INSYDE EDK2            2 ACPI    40000)
(XEN) ACPI: MCFG 5AFEC000, 003C (r1 INSYDE EDK2            2 ACPI    40000)
(XEN) ACPI: SLIC 5AFEB000, 0176 (r1 INSYDE EDK2            2 ACPI    40000)
(XEN) ACPI: VFCT 5AFDA000, 4284 (r1 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFD9000, 00F8 (r2 INSYDE EDK2         1000 ACPI    40000)
(XEN) ACPI: SSDT 5AFD3000, 547E (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: CRAT 5AFD2000, 0F10 (r1 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: CDIT 5AFD1000, 0029 (r1 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFD0000, 0F8D (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFCF000, 0EC1 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFCE000, 0931 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFCB000, 13EC (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFFD000, 077A (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFCA000, 0737 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFC8000, 15C8 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFC5000, 2A8F (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFBB000, 9821 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: FPDT 5AFBA000, 0044 (r1 INSYDE EDK2            2 ACPI    40000)
(XEN) ACPI: BGRT 5AFB9000, 0038 (r1 INSYDE EDK2            2 ACPI    40000)
(XEN) ACPI: WSMT 5AFB8000, 0028 (r1 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: MHSP 5AFEA000, 00C8 (r4 INSYDE EDK2     20505348 ACPI    40000)
(XEN) ACPI: SSDT 5AFE9000, 00E5 (r2 INSYDE EDK2            4 ACPI    40000)
(XEN) ACPI: IVRS 5AFB7000, 01A4 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFB6000, 0747 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFB5000, 0C88 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFB4000, 0057 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFB2000, 170B (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFB1000, 0FF7 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFA7000, 97E3 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFA2000, 4FEB (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFA1000, 0C7F (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFA0000, 0956 (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AF9F000, 008D (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) ACPI: SSDT 5AFCD000, 0EAD (r2 INSYDE EDK2            1 ACPI    40000)
(XEN) System RAM: 64708MB (66261880kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-000000107e300000
(XEN) Domain heap initialised
(XEN) vesafb: framebuffer at 0x0000008800000000, mapped to 0xffff82c000201000, using 13568k, total 13568k
(XEN) vesafb: mode is 2256x1504x32, linelength=9216, font 8x16
(XEN) vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
(XEN) SMBIOS 3.5 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408 (32 bits)
(XEN) ACPI: v5 SLEEP INFO: control[0:0], status[0:0]
(XEN) ACPI: SLEEP INFO: pm1x_cnt[1:404,1:0], pm1x_evt[1:400,1:0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT - 5aeb7000/0000000000000000, using 32
(XEN) ACPI:             wakeup_vec[5aeb700c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) Overriding APIC driver with bigsmp
(XEN) ACPI: IOAPIC (id[0x21] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 33, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x22] address[0xfec01000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 34, version 33, address 0xfec01000, GSI 24-55
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) ACPI: HPET id: 0x10228210 base: 0xfed00000
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff
(XEN) PCI: Not using MCFG for segment 0000 bus 00-ff
(XEN) ACPI: BGRT: invalidating v1 image at 0x4b822018
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 16 CPUs (0 hotplug CPUs)
(XEN) IRQ limits: 56 GSI, 3272 MSI/MSI-X
(XEN) AMD-Vi: IOMMU Extended Features:
(XEN) - Peripheral Page Service Request
(XEN) - NX bit
(XEN) - Guest APIC Physical Processor Interrupt
(XEN) - Invalidate All Command
(XEN) - Guest APIC
(XEN) - Performance Counters
(XEN) - Host Address Translation Size: 0x2
(XEN) - Guest Address Translation Size: 0
(XEN) - Guest CR3 Root Table Level: 0x1
(XEN) - Maximum PASID: 0xf
(XEN) - SMI Filter Register: 0x1
(XEN) - SMI Filter Register Count: 0x1
(XEN) - Guest Virtual APIC Modes: 0x1
(XEN) - Dual PPR Log: 0x2
(XEN) - Dual Event Log: 0x2
(XEN) - Secure ATS
(XEN) - User / Supervisor Page Protection
(XEN) - Device Table Segmentation: 0x3
(XEN) - PPR Log Overflow Early Warning
(XEN) - PPR Automatic Response
(XEN) - Memory Access Routing and Control: 0x1
(XEN) - Block StopMark Message
(XEN) - Performance Optimization
(XEN) - MSI Capability MMIO Access
(XEN) - Guest I/O Protection
(XEN) - Enhanced PPR Handling
(XEN) - Invalidate IOTLB Type
(XEN) - VM Table Size: 0x2
(XEN) - Guest Access Bit Update Disable
(XEN) Switched to APIC driver x2apic_mixed
(XEN) CPU0: 1600 ... 3300 MHz
(XEN) xstate: size: 0x988 and states: 0x2e7
(XEN) CPU0: AMD Fam19h machine check reporting enabled
(XEN) Fixup #GP[0000]: ffff82d04044ca4e [init_speculation_mitigations+0xae0/0x1ece] -> ffff82d04038f0b5
(XEN) Vulnerable to SRSO, without suitable microcode to mitigate
(XEN) Speculative mitigation facilities:
(XEN)   Hardware hints: STIBP_ALWAYS IBRS_FAST IBRS_SAME_MODE BTC_NO IBPB_RET
(XEN)   Hardware features: IBPB IBRS STIBP SSBD PSFD L1D_FLUSH
(XEN)   Compiled-in support: INDIRECT_THUNK SHADOW_PAGING
(XEN)   Xen settings: BTI-Thunk JMP, SPEC_CTRL: IBRS+ STIBP+ SSBD- PSFD-, Other: IBPB-ctxt BRANCH_HARDEN
(XEN)   Support for HVM VMs: MSR_SPEC_CTRL MSR_VIRT_SPEC_CTRL RSB
(XEN)   Support for PV VMs: None
(XEN)   XPTI (64-bit PV only): Dom0 disabled, DomU disabled (without PCID)
(XEN)   PV L1TF shadowing: Dom0 disabled, DomU disabled
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN)  load_precision_shift: 18
(XEN)  load_window_shift: 30
(XEN)  underload_balance_tolerance: 0
(XEN)  overload_balance_tolerance: -3
(XEN)  runqueues arrangement: socket
(XEN)  cap enforcement granularity: 10ms
(XEN) load tracking window length 1073741824 ns
(XEN) Platform timer is 14.318MHz HPET
(XEN) Detected 3293.817 MHz processor.
(XEN) Freed 1016kB unused BSS memory
(XEN) EFI memory map:
(XEN)  0000000000000-0000000003fff type=2 attr=000000000000000f
(XEN)  0000000004000-0000000086fff type=7 attr=000000000000000f
(XEN)  0000000087000-0000000087fff type=4 attr=000000000000000f
(XEN)  0000000088000-000000008efff type=7 attr=000000000000000f
(XEN)  000000008f000-000000009efff type=2 attr=000000000000000f
(XEN)  000000009f000-000000009ffff type=0 attr=000000000000000f
(XEN)  0000000100000-0000000ee0fff type=2 attr=000000000000000f
(XEN)  0000000ee1000-0000009afffff type=7 attr=000000000000000f
(XEN)  0000009b00000-0000009dfffff type=0 attr=000000000000000f
(XEN)  0000009e00000-0000009efffff type=7 attr=000000000000000f
(XEN)  0000009f00000-0000009f3bfff type=10 attr=000000000000000f
(XEN)  0000009f3c000-0000017a30fff type=2 attr=000000000000000f
(XEN)  0000017a31000-000003108cfff type=7 attr=000000000000000f
(XEN)  000003108d000-000003437efff type=1 attr=000000000000000f
(XEN)  000003437f000-00000343fefff type=4 attr=000000000000000f
(XEN)  00000343ff000-000003f941fff type=7 attr=000000000000000f
(XEN)  000003f942000-000003fc9ffff type=1 attr=000000000000000f
(XEN)  000003fca0000-000003fffdfff type=2 attr=000000000000000f
(XEN)  000003fffe000-00000403fffff type=4 attr=000000000000000f
(XEN)  0000040400000-00000404a2fff type=7 attr=000000000000000f
(XEN)  00000404a3000-00000404c2fff type=4 attr=000000000000000f
(XEN)  00000404c3000-00000404d8fff type=3 attr=000000000000000f
(XEN)  00000404d9000-00000404e9fff type=4 attr=000000000000000f
(XEN)  00000404ea000-000004051afff type=3 attr=000000000000000f
(XEN)  000004051b000-000004056bfff type=4 attr=000000000000000f
(XEN)  000004056c000-0000040574fff type=3 attr=000000000000000f
(XEN)  0000040575000-0000041d42fff type=4 attr=000000000000000f
(XEN)  0000041d43000-0000041d5ffff type=3 attr=000000000000000f
(XEN)  0000041d60000-000004235ffff type=4 attr=000000000000000f
(XEN)  0000042360000-000004455ffff type=0 attr=000000000000000f
(XEN)  0000044560000-0000044566fff type=3 attr=000000000000000f
(XEN)  0000044567000-0000044568fff type=4 attr=000000000000000f
(XEN)  0000044569000-000004456cfff type=6 attr=800000000000000f
(XEN)  000004456d000-000004456efff type=4 attr=000000000000000f
(XEN)  000004456f000-000004456ffff type=6 attr=800000000000000f
(XEN)  0000044570000-0000044579fff type=7 attr=000000000000000f
(XEN)  000004457a000-000004457cfff type=2 attr=000000000000000f
(XEN)  000004457d000-00000446acfff type=7 attr=000000000000000f
(XEN)  00000446ad000-000004477efff type=1 attr=000000000000000f
(XEN)  000004477f000-000004ac55fff type=7 attr=000000000000000f
(XEN)  000004ac56000-000004b382fff type=4 attr=000000000000000f
(XEN)  000004b383000-000004b3fffff type=7 attr=000000000000000f
(XEN)  000004b400000-000004b5cefff type=4 attr=000000000000000f
(XEN)  000004b5cf000-000004b713fff type=7 attr=000000000000000f
(XEN)  000004b714000-000004b714fff type=4 attr=000000000000000f
(XEN)  000004b715000-000004b716fff type=7 attr=000000000000000f
(XEN)  000004b717000-000004e77efff type=4 attr=000000000000000f
(XEN)  000004e77f000-000004f5fffff type=7 attr=000000000000000f
(XEN)  000004f600000-000004f9f4fff type=2 attr=000000000000000f
(XEN)  000004f9f5000-000004fa50fff type=7 attr=000000000000000f
(XEN)  000004fa51000-000005077efff type=3 attr=000000000000000f
(XEN)  000005077f000-0000050f7efff type=5 attr=800000000000000f
(XEN)  0000050f7f000-0000051f7efff type=6 attr=800000000000000f
(XEN)  0000051f7f000-0000052f7efff type=0 attr=000000000000000f
(XEN)  0000052f7f000-000005af7efff type=10 attr=000000000000000f
(XEN)  000005af7f000-000005affefff type=9 attr=000000000000000f
(XEN)  000005afff000-000005affffff type=4 attr=000000000000000f
(XEN)  0000100000000-000107e2fffff type=7 attr=000000000000000f
(XEN)  00000000a0000-00000000bffff type=0 attr=0000000000000000
(XEN)  000005b000000-000005bffffff type=0 attr=0000000000000009
(XEN)  000005d790000-000005d7effff type=0 attr=0000000000000000
(XEN)  000005d7f5000-000005fffffff type=0 attr=0000000000000000
(XEN)  00000c0300000-00000c03fffff type=11 attr=8000000000000001
(XEN)  00000fed80000-00000fed80fff type=11 attr=8000000000000001
(XEN)  00000ff000000-00000ffffffff type=11 attr=8000000000000001
(XEN)  0001080000000-000109fffffff type=0 attr=0000000000000000
(XEN)  00010a0000000-00010c01fffff type=11 attr=8000000000000001
(XEN) alt table ffff82d04049b1d0 -> ffff82d0404a85ba
(XEN) AMD-Vi: Disabled HAP memory map sharing with IOMMU
(XEN) AMD-Vi: IOMMU 0 Enabled.
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) nr_sockets: 1
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) Enabling APIC mode.  Using 2 I/O APICs
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using old ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) Allocated console ring of 128 KiB.
(XEN) mwait-idle: does not run on family 25 model 116
(XEN) HVM: ASIDs enabled.
(XEN) SVM: Supported advanced features:
(XEN)  - Nested Page Tables (NPT)
(XEN)  - Last Branch Record (LBR) Virtualisation
(XEN)  - Next-RIP Saved on #VMEXIT
(XEN)  - VMCB Clean Bits
(XEN)  - DecodeAssists
(XEN)  - Virtual VMLOAD/VMSAVE
(XEN)  - Virtual GIF
(XEN)  - Pause-Intercept Filter
(XEN)  - Pause-Intercept Filter Threshold
(XEN)  - TSC Rate MSR
(XEN)  - NPT Supervisor Shadow Stack
(XEN)  - MSR_SPEC_CTRL virtualisation
(XEN) HVM: SVM enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) alt table ffff82d04049b1d0 -> ffff82d0404a85ba
(XEN) Brought up 16 CPUs
(XEN) Scheduling granularity: cpu, 1 CPU per sched-resource
(XEN) Initializing Credit2 scheduler
(XEN)  load_precision_shift: 18
(XEN)  load_window_shift: 30
(XEN)  underload_balance_tolerance: 0
(XEN)  overload_balance_tolerance: -3
(XEN)  runqueues arrangement: socket
(XEN)  cap enforcement granularity: 10ms
(XEN) load tracking window length 1073741824 ns
(XEN) Adding cpu 0 to runqueue 0
(XEN)  First cpu on runqueue, activating
(XEN) Adding cpu 1 to runqueue 0
(XEN) Adding cpu 2 to runqueue 0
(XEN) Adding cpu 3 to runqueue 0
(XEN) Adding cpu 4 to runqueue 0
(XEN) Adding cpu 5 to runqueue 0
(XEN) Adding cpu 6 to runqueue 0
(XEN) Adding cpu 7 to runqueue 0
(XEN) Adding cpu 8 to runqueue 0
(XEN) Adding cpu 9 to runqueue 0
(XEN) Adding cpu 10 to runqueue 0
(XEN) Adding cpu 11 to runqueue 0
(XEN) Adding cpu 12 to runqueue 0
(XEN) Adding cpu 13 to runqueue 0
(XEN) Adding cpu 14 to runqueue 0
(XEN) Adding cpu 15 to runqueue 0
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) xenoprof: Initialization failed. AMD processor family 25 is not supported
(XEN) Running stub recovery selftests...
(XEN) Fixup #UD[0000]: ffff82d07fffe044 [ffff82d07fffe044] -> ffff82d04038efbb
(XEN) Fixup #GP[0000]: ffff82d07fffe045 [ffff82d07fffe045] -> ffff82d04038efbb
(XEN) Fixup #SS[0000]: ffff82d07fffe044 [ffff82d07fffe044] -> ffff82d04038efbb
(XEN) Fixup #BP[0000]: ffff82d07fffe045 [ffff82d07fffe045] -> ffff82d04038efbb
(XEN) NX (Execute Disable) protection active
(XEN) Dom0 has maximum 1096 PIRQs
(XEN) *** Building a PV Dom0 ***
(XEN) ELF: phdr: paddr=0x1000000 memsz=0x201d3ec
(XEN) ELF: phdr: paddr=0x3200000 memsz=0x87b000
(XEN) ELF: phdr: paddr=0x3a7b000 memsz=0x37000
(XEN) ELF: phdr: paddr=0x3ab2000 memsz=0xd4e000
(XEN) ELF: memory: 0x1000000 -> 0x4800000
(XEN) ELF: note: PHYS32_ENTRY = 0x1000000
(XEN) ELF: note: GUEST_OS = "linux"
(XEN) ELF: note: GUEST_VERSION = "2.6"
(XEN) ELF: note: XEN_VERSION = "xen-3.0"
(XEN) ELF: note: VIRT_BASE = 0xffffffff80000000
(XEN) ELF: note: INIT_P2M = 0x8000000000
(XEN) ELF: note: ENTRY = 0xffffffff83ac4390
(XEN) ELF: note: FEATURES = "!writable_page_tables"
(XEN) ELF: note: PAE_MODE = "yes"
(XEN) ELF: note: unknown (0xd)
(XEN) ELF: note: MOD_START_PFN = 0x1
(XEN) ELF: note: PADDR_OFFSET = 0
(XEN) ELF: note: HYPERCALL_PAGE = 0xffffffff81fc7000
(XEN) ELF: note: SUPPORTED_FEATURES = 0x8801
(XEN) ELF: note: LOADER = "generic"
(XEN) ELF: note: SUSPEND_CANCEL = 0x1
(XEN) ELF: addresses:
(XEN)     virt_base        = 0xffffffff80000000
(XEN)     elf_paddr_offset = 0x0
(XEN)     virt_offset      = 0xffffffff80000000
(XEN)     virt_kstart      = 0xffffffff81000000
(XEN)     virt_kend        = 0xffffffff84800000
(XEN)     virt_entry       = 0xffffffff83ac4390
(XEN)     p2m_base         = 0x8000000000
(XEN)  Xen  kernel: 64-bit, lsb
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x4800000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000001038000000->0000001040000000 (16244129 pages to be allocated)
(XEN)  Init. ramdisk: 000000107070b000->000000107e1ff271
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff84800000
(XEN)  Phys-Mach map: 0000008000000000->0000008007c9c4b0
(XEN)  Start info:    ffffffff84800000->ffffffff848004b8
(XEN)  Page tables:   ffffffff84801000->ffffffff8482a000
(XEN)  Boot stack:    ffffffff8482a000->ffffffff8482b000
(XEN)  TOTAL:         ffffffff80000000->ffffffff84c00000
(XEN)  ENTRY ADDRESS: ffffffff83ac4390
(XEN) Dom0 has maximum 16 VCPUs
(XEN) ELF: phdr 0 at 0xffffffff81000000 -> 0xffffffff8301d3ec
(XEN) ELF: phdr 1 at 0xffffffff83200000 -> 0xffffffff83a7b000
(XEN) ELF: phdr 2 at 0xffffffff83a7b000 -> 0xffffffff83ab2000
(XEN) ELF: phdr 3 at 0xffffffff83ab2000 -> 0xffffffff84800000
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Scrubbing Free RAM in background
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 632kB init memory
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 9, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PCI add device 0000:00:00.0
(XEN) PCI add device 0000:00:00.2
(XEN) PCI add device 0000:00:01.0
(XEN) PCI add device 0000:00:02.0
(XEN) PCI add device 0000:00:02.2
(XEN) PCI add device 0000:00:02.4
(XEN) PCI add device 0000:00:03.0
(XEN) PCI add device 0000:00:03.1
(XEN) PCI add device 0000:00:04.0
(XEN) PCI add device 0000:00:04.1
(XEN) PCI add device 0000:00:08.0
(XEN) PCI add device 0000:00:08.1
(XEN) PCI add device 0000:00:08.2
(XEN) PCI add device 0000:00:08.3
(XEN) PCI add device 0000:00:14.0
(XEN) PCI add device 0000:00:14.3
(XEN) PCI add device 0000:00:18.0
(XEN) PCI add device 0000:00:18.1
(XEN) PCI add device 0000:00:18.2
(XEN) PCI add device 0000:00:18.3
(XEN) PCI add device 0000:00:18.4
(XEN) PCI add device 0000:00:18.5
(XEN) PCI add device 0000:00:18.6
(XEN) PCI add device 0000:00:18.7
(XEN) PCI add device 0000:01:00.0
(XEN) PCI add device 0000:02:00.0
(XEN) PCI add device 0000:c1:00.0
(XEN) PCI add device 0000:c1:00.1
(XEN) PCI add device 0000:c1:00.2
(XEN) PCI add device 0000:c1:00.3
(XEN) PCI add device 0000:c1:00.4
(XEN) PCI add device 0000:c1:00.5
(XEN) PCI add device 0000:c1:00.6
(XEN) PCI add device 0000:c2:00.0
(XEN) PCI add device 0000:c2:00.1
(XEN) PCI add device 0000:c3:00.0
(XEN) PCI add device 0000:c3:00.3
(XEN) PCI add device 0000:c3:00.4
(XEN) PCI add device 0000:c3:00.5
(XEN) PCI add device 0000:c3:00.6
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 8, setup_gsi.triggering: 0,setup_gsi.polarity: 0
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 13, setup_gsi.triggering: 0,setup_gsi.polarity: 0
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 7, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 10, setup_gsi.triggering: 0,setup_gsi.polarity: 0
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 6, setup_gsi.triggering: 0,setup_gsi.polarity: 0
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 50, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 51, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 52, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 53, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 1, setup_gsi.triggering: 0,setup_gsi.polarity: 0
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 40, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 37, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 38, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 40, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 46, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 47, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 40, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) d0: Forcing read-only access to MFN fed00
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 37, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 38, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 46, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 47, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 36, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 42, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 38, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 44, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 45, setup_gsi.triggering: 1,setup_gsi.polarity: 1
(XEN) arch/x86/pv/emul-priv-op.c:1027:d0v0 RDMSR 0xc001029b unimplemented
(XEN) arch/x86/pv/emul-priv-op.c:1027:d0v0 RDMSR 0xc001029a unimplemented
(XEN) PHYSDEVOP_setup_gsi: setup_gsi.gsi: 46, setup_gsi.triggering: 1,setup_gsi.polarity: 1

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 20.12.2023 17:34, Sébastien Chaumat wrote:
> Here are the patches I made to xen and linux kernel
> Plus dmesg (bare metal,xen) and "xl dmesg"

So only a single setup_gsi then, after all. Or else I must be missing
something. And there it's all consistent as well: Level/low like for any
other pin (IO-APIC) based PCI IRQ. The issue may then rather be with
xen_register_pirq(), where 1st and 2nd invocation are clearly different.
I'll try to get to looking into that some more later in the day.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 20.12.2023 17:34, Sébastien Chaumat wrote:
> Here are the patches I made to xen and linux kernel
> Plus dmesg (bare metal,xen) and "xl dmesg"

So the problem looks to be that pci_xen_initial_domain() results in
permanent setup of IRQ7, when there only "static" ACPI tables (in
particular source overrides in MADT) are consulted. The necessary
settings, however, are known only after _CRS for the device was
evaluated (and possibly _PRS followed by invocation of _SRS). All of
this happens before xen_register_gsi() is called. But that function's
call to xen_register_pirq() is short-circuited by the very first if()
in xen_register_pirq() when there was an earlier invocation. Hence
the (wrong) "edge" binding remains in place, as was established by
the earlier call here.

Jürgen, there's an interesting comment in xen_bind_pirq_gsi_to_irq(),
right before invoking irq_set_chip_and_handler_name(). Despite what
the comment says (according to my reading), the fasteoi one is _not_
used in all cases. Assuming there's a reason for this, it's not clear
to me whether updating the handler later on is a valid thing to do.
__irq_set_handler() being even an exported symbol suggests that might
be an option to use here. Then again merely updating the handler may
not be sufficient, seeing there are also e.g. IRQD_TRIGGER_MASK and
IRQD_LEVEL.

Sébastien, to prove the (still pretty weak) theory that the change in
handler is all that's needed to make things work in your case, could
you fiddle with pci_xen_initial_domain() to have it skip IRQ7? (That
of course won't be a proper solution, but ought to be okay for your
system.) The main weakness of the theory is that IRQ7 really isn't
very special in this regard - other PCI IRQs routed to the low 16
IO-APIC pins ought to have similar issues (from the log, on your
system this would be at least IRQ6 and IRQ10, except that they happen
to be edge/low, so fitting the ISA defaults); only IRQ16 and up would
work okay.

Furthermore it might be interesting to know whether ELCR would give us
any hint in this case. Sadly depending on where you look,
applicability of this pair of registers (I/O ports 0x4d0 and 0x4d1)
to other than EISA systems is claimed true or false. Could you perhaps
make Xen simply log the values read from those two ports, by e.g.
inserting

    printk("ELCR: %02x, %02x\n", inb(0x4d0), inb(0x4d1));

in, say, setup_dump_irqs()?

Jürgen, looking at pci_xen_initial_domain(), what's the purpose of
the loop in the final if()? Can this ever do anything useful when
the earlier comment suggests nr_legacy_irqs() is zero anyway? Or is
the comment simply inaccurate in not covering the "no IO-APICs" case?

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Juergen Gross]

[-- Attachment #1.1.1: Type: text/plain, Size: 3382 bytes --]

On 21.12.23 13:40, Jan Beulich wrote:
> On 20.12.2023 17:34, Sébastien Chaumat wrote:
>> Here are the patches I made to xen and linux kernel
>> Plus dmesg (bare metal,xen) and "xl dmesg"
> 
> So the problem looks to be that pci_xen_initial_domain() results in
> permanent setup of IRQ7, when there only "static" ACPI tables (in
> particular source overrides in MADT) are consulted. The necessary
> settings, however, are known only after _CRS for the device was
> evaluated (and possibly _PRS followed by invocation of _SRS). All of
> this happens before xen_register_gsi() is called. But that function's
> call to xen_register_pirq() is short-circuited by the very first if()
> in xen_register_pirq() when there was an earlier invocation. Hence
> the (wrong) "edge" binding remains in place, as was established by
> the earlier call here.
> 
> Jürgen, there's an interesting comment in xen_bind_pirq_gsi_to_irq(),
> right before invoking irq_set_chip_and_handler_name(). Despite what
> the comment says (according to my reading), the fasteoi one is _not_
> used in all cases. Assuming there's a reason for this, it's not clear
> to me whether updating the handler later on is a valid thing to do.
> __irq_set_handler() being even an exported symbol suggests that might
> be an option to use here. Then again merely updating the handler may
> not be sufficient, seeing there are also e.g. IRQD_TRIGGER_MASK and
> IRQD_LEVEL.

I understand the last paragraph of that comment to reason, that in case
pirq_needs_eoi() return true even in case of an edge triggered interrupt,
the outcome is still okay.

I don't think updating the handler later is valid.

> Sébastien, to prove the (still pretty weak) theory that the change in
> handler is all that's needed to make things work in your case, could
> you fiddle with pci_xen_initial_domain() to have it skip IRQ7? (That
> of course won't be a proper solution, but ought to be okay for your
> system.) The main weakness of the theory is that IRQ7 really isn't
> very special in this regard - other PCI IRQs routed to the low 16
> IO-APIC pins ought to have similar issues (from the log, on your
> system this would be at least IRQ6 and IRQ10, except that they happen
> to be edge/low, so fitting the ISA defaults); only IRQ16 and up would
> work okay.
> 
> Furthermore it might be interesting to know whether ELCR would give us
> any hint in this case. Sadly depending on where you look,
> applicability of this pair of registers (I/O ports 0x4d0 and 0x4d1)
> to other than EISA systems is claimed true or false. Could you perhaps
> make Xen simply log the values read from those two ports, by e.g.
> inserting
> 
>      printk("ELCR: %02x, %02x\n", inb(0x4d0), inb(0x4d1));
> 
> in, say, setup_dump_irqs()?
> 
> Jürgen, looking at pci_xen_initial_domain(), what's the purpose of
> the loop in the final if()? Can this ever do anything useful when
> the earlier comment suggests nr_legacy_irqs() is zero anyway? Or is
> the comment simply inaccurate in not covering the "no IO-APICs" case?

No, I think the final loop would only do something in case probe_8259A()
is detecting a working PIC (which should not be the case IMHO). Could it
be that there have been Xen versions emulating a PIC?

The call of probe_8259A() is in no way depending on nr_ioapics.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 21.12.2023 14:29, Juergen Gross wrote:
> On 21.12.23 13:40, Jan Beulich wrote:
>> On 20.12.2023 17:34, Sébastien Chaumat wrote:
>>> Here are the patches I made to xen and linux kernel
>>> Plus dmesg (bare metal,xen) and "xl dmesg"
>>
>> So the problem looks to be that pci_xen_initial_domain() results in
>> permanent setup of IRQ7, when there only "static" ACPI tables (in
>> particular source overrides in MADT) are consulted. The necessary
>> settings, however, are known only after _CRS for the device was
>> evaluated (and possibly _PRS followed by invocation of _SRS). All of
>> this happens before xen_register_gsi() is called. But that function's
>> call to xen_register_pirq() is short-circuited by the very first if()
>> in xen_register_pirq() when there was an earlier invocation. Hence
>> the (wrong) "edge" binding remains in place, as was established by
>> the earlier call here.
>>
>> Jürgen, there's an interesting comment in xen_bind_pirq_gsi_to_irq(),
>> right before invoking irq_set_chip_and_handler_name(). Despite what
>> the comment says (according to my reading), the fasteoi one is _not_
>> used in all cases. Assuming there's a reason for this, it's not clear
>> to me whether updating the handler later on is a valid thing to do.
>> __irq_set_handler() being even an exported symbol suggests that might
>> be an option to use here. Then again merely updating the handler may
>> not be sufficient, seeing there are also e.g. IRQD_TRIGGER_MASK and
>> IRQD_LEVEL.
> 
> I understand the last paragraph of that comment to reason, that in case
> pirq_needs_eoi() return true even in case of an edge triggered interrupt,
> the outcome is still okay.
> 
> I don't think updating the handler later is valid.

In which case fixing this is going to be interesting.

>> Jürgen, looking at pci_xen_initial_domain(), what's the purpose of
>> the loop in the final if()? Can this ever do anything useful when
>> the earlier comment suggests nr_legacy_irqs() is zero anyway? Or is
>> the comment simply inaccurate in not covering the "no IO-APICs" case?
> 
> No, I think the final loop would only do something in case probe_8259A()
> is detecting a working PIC (which should not be the case IMHO). Could it
> be that there have been Xen versions emulating a PIC?

Not as far back as I can recall (for PV Dom0). Even in 3.2 Dom0 was
already denied access to the respective I/O ports. And iirc upstream
Linux wants at least 4.0?

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le jeu. 21 déc. 2023 à 14:29, Juergen Gross <jgross@suse.com> a écrit :

> On 21.12.23 13:40, Jan Beulich wrote:
> > On 20.12.2023 17:34, Sébastien Chaumat wrote:
> >> Here are the patches I made to xen and linux kernel
> >> Plus dmesg (bare metal,xen) and "xl dmesg"
> >
> > So the problem looks to be that pci_xen_initial_domain() results in
> > permanent setup of IRQ7, when there only "static" ACPI tables (in
> > particular source overrides in MADT) are consulted. The necessary
> > settings, however, are known only after _CRS for the device was
> > evaluated (and possibly _PRS followed by invocation of _SRS). All of
> > this happens before xen_register_gsi() is called. But that function's
> > call to xen_register_pirq() is short-circuited by the very first if()
> > in xen_register_pirq() when there was an earlier invocation. Hence
> > the (wrong) "edge" binding remains in place, as was established by
> > the earlier call here.
> >
> > Jürgen, there's an interesting comment in xen_bind_pirq_gsi_to_irq(),
> > right before invoking irq_set_chip_and_handler_name(). Despite what
> > the comment says (according to my reading), the fasteoi one is _not_
> > used in all cases. Assuming there's a reason for this, it's not clear
> > to me whether updating the handler later on is a valid thing to do.
> > __irq_set_handler() being even an exported symbol suggests that might
> > be an option to use here. Then again merely updating the handler may
> > not be sufficient, seeing there are also e.g. IRQD_TRIGGER_MASK and
> > IRQD_LEVEL.
>
> I understand the last paragraph of that comment to reason, that in case
> pirq_needs_eoi() return true even in case of an edge triggered interrupt,
> the outcome is still okay.
>
> I don't think updating the handler later is valid.
>
> > Sébastien, to prove the (still pretty weak) theory that the change in
> > handler is all that's needed to make things work in your case, could
> > you fiddle with pci_xen_initial_domain() to have it skip IRQ7? (That
> > of course won't be a proper solution, but ought to be okay for your
> > system.) The main weakness of the theory is that IRQ7 really isn't
> > very special in this regard - other PCI IRQs routed to the low 16
> > IO-APIC pins ought to have similar issues (from the log, on your
> > system this would be at least IRQ6 and IRQ10, except that they happen
> > to be edge/low, so fitting the ISA defaults); only IRQ16 and up would
> > work okay.
> >
>

Doing just that : IQR7 is now  of type level
  xen-pirq     -ioapic-level  pinctrl_amd


(but is ioapic-level there totally equivalent to the fasteoi of baremetal)
Still the touchpad does not work.

And we have now :
Dec 21 20:13:57 fedora kernel: i2c_hid_acpi i2c-PIXA3854:00: failed to
reset device: -61
Dec 21 20:14:17 fedora kernel: i2c_hid_acpi: probe of i2c-PIXA3854:00
failed with error -61

in addition to
Dec 21 20:13:57 fedora kernel: i2c_hid_acpi i2c-FRMW0004:00: failed to
reset device: -61
Dec 21 20:13:57 fedora kernel: i2c_hid_acpi i2c-FRMW0005:00: failed to
reset device: -61
Dec 21 20:14:17 fedora kernel: i2c_hid_acpi: probe of i2c-FRMW0004:00
failed with error -61
Dec 21 20:14:17 fedora kernel: i2c_hid_acpi: probe of i2c-FRMW0005:00
failed with error -61


I noticed that on baremetal :

  53:          0          0          0          0          0       1268
     0          0          0          0          0          0          0
       0          0          0  amd_gpio    5  FRMW0005:00
  54:          0          0          0          0          0          1
     0          0          0          0          0          0          0
       0          0          0  amd_gpio   84  FRMW0004:00
  55:          0          0          0          0          0       1403
     0          0          0          0          0          0          0
       0          0          0  amd_gpio    8  PIXA3854:00

with xen with IRQ7 setup only once there's only (the touchpad is
PIXA3854:00)

 176:          0          0          0          0          0          0
     1          0          0          0          0          0          0
       0          0          0  amd_gpio    8

Interestingly when IRQ7 is setup twice (normal xen)
 176:          0          0          0          0          0          0
     1          0          0          0          0          0          0
       0          0          0  amd_gpio    8  PIXA3854:00


> Furthermore it might be interesting to know whether ELCR would give us
> > any hint in this case. Sadly depending on where you look,
> > applicability of this pair of registers (I/O ports 0x4d0 and 0x4d1)
> > to other than EISA systems is claimed true or false. Could you perhaps
> > make Xen simply log the values read from those two ports, by e.g.
> > inserting
> >
> >      printk("ELCR: %02x, %02x\n", inb(0x4d0), inb(0x4d1));
> >
> > in, say, setup_dump_irqs()?
> >
>
did that but I don't know how to trigger the dump.

Sébastien

[-- Attachment #2: Type: text/html, Size: 6681 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 21.12.2023 21:41, Sébastien Chaumat wrote:
> Le jeu. 21 déc. 2023 à 14:29, Juergen Gross <jgross@suse.com> a écrit :
> 
>> On 21.12.23 13:40, Jan Beulich wrote:
>>> On 20.12.2023 17:34, Sébastien Chaumat wrote:
>>>> Here are the patches I made to xen and linux kernel
>>>> Plus dmesg (bare metal,xen) and "xl dmesg"
>>>
>>> So the problem looks to be that pci_xen_initial_domain() results in
>>> permanent setup of IRQ7, when there only "static" ACPI tables (in
>>> particular source overrides in MADT) are consulted. The necessary
>>> settings, however, are known only after _CRS for the device was
>>> evaluated (and possibly _PRS followed by invocation of _SRS). All of
>>> this happens before xen_register_gsi() is called. But that function's
>>> call to xen_register_pirq() is short-circuited by the very first if()
>>> in xen_register_pirq() when there was an earlier invocation. Hence
>>> the (wrong) "edge" binding remains in place, as was established by
>>> the earlier call here.
>>>
>>> Jürgen, there's an interesting comment in xen_bind_pirq_gsi_to_irq(),
>>> right before invoking irq_set_chip_and_handler_name(). Despite what
>>> the comment says (according to my reading), the fasteoi one is _not_
>>> used in all cases. Assuming there's a reason for this, it's not clear
>>> to me whether updating the handler later on is a valid thing to do.
>>> __irq_set_handler() being even an exported symbol suggests that might
>>> be an option to use here. Then again merely updating the handler may
>>> not be sufficient, seeing there are also e.g. IRQD_TRIGGER_MASK and
>>> IRQD_LEVEL.
>>
>> I understand the last paragraph of that comment to reason, that in case
>> pirq_needs_eoi() return true even in case of an edge triggered interrupt,
>> the outcome is still okay.
>>
>> I don't think updating the handler later is valid.
>>
>>> Sébastien, to prove the (still pretty weak) theory that the change in
>>> handler is all that's needed to make things work in your case, could
>>> you fiddle with pci_xen_initial_domain() to have it skip IRQ7? (That
>>> of course won't be a proper solution, but ought to be okay for your
>>> system.) The main weakness of the theory is that IRQ7 really isn't
>>> very special in this regard - other PCI IRQs routed to the low 16
>>> IO-APIC pins ought to have similar issues (from the log, on your
>>> system this would be at least IRQ6 and IRQ10, except that they happen
>>> to be edge/low, so fitting the ISA defaults); only IRQ16 and up would
>>> work okay.
>>>
>>
> 
> Doing just that : IQR7 is now  of type level
>   xen-pirq     -ioapic-level  pinctrl_amd
> 
> 
> (but is ioapic-level there totally equivalent to the fasteoi of baremetal)
> Still the touchpad does not work.
> 
> And we have now :
> Dec 21 20:13:57 fedora kernel: i2c_hid_acpi i2c-PIXA3854:00: failed to
> reset device: -61
> Dec 21 20:14:17 fedora kernel: i2c_hid_acpi: probe of i2c-PIXA3854:00
> failed with error -61
> 
> in addition to
> Dec 21 20:13:57 fedora kernel: i2c_hid_acpi i2c-FRMW0004:00: failed to
> reset device: -61
> Dec 21 20:13:57 fedora kernel: i2c_hid_acpi i2c-FRMW0005:00: failed to
> reset device: -61
> Dec 21 20:14:17 fedora kernel: i2c_hid_acpi: probe of i2c-FRMW0004:00
> failed with error -61
> Dec 21 20:14:17 fedora kernel: i2c_hid_acpi: probe of i2c-FRMW0005:00
> failed with error -61

So there's more to this, which I'm afraid will (first) need looking into
by a person familiar with the involved drivers.

> I noticed that on baremetal :
> 
>   53:          0          0          0          0          0       1268
>      0          0          0          0          0          0          0
>        0          0          0  amd_gpio    5  FRMW0005:00
>   54:          0          0          0          0          0          1
>      0          0          0          0          0          0          0
>        0          0          0  amd_gpio   84  FRMW0004:00
>   55:          0          0          0          0          0       1403
>      0          0          0          0          0          0          0
>        0          0          0  amd_gpio    8  PIXA3854:00
> 
> with xen with IRQ7 setup only once there's only (the touchpad is
> PIXA3854:00)
> 
>  176:          0          0          0          0          0          0
>      1          0          0          0          0          0          0
>        0          0          0  amd_gpio    8
> 
> Interestingly when IRQ7 is setup twice (normal xen)
>  176:          0          0          0          0          0          0
>      1          0          0          0          0          0          0
>        0          0          0  amd_gpio    8  PIXA3854:00

That's odd, as with IRQ7 (wrongly) setup as edge, it should also be marked
as non-sharable. Otoh with the "i2c-PIXA3854:00:" error above it's no
surprise no interrupt is set up there.

>> Furthermore it might be interesting to know whether ELCR would give us
>>> any hint in this case. Sadly depending on where you look,
>>> applicability of this pair of registers (I/O ports 0x4d0 and 0x4d1)
>>> to other than EISA systems is claimed true or false. Could you perhaps
>>> make Xen simply log the values read from those two ports, by e.g.
>>> inserting
>>>
>>>      printk("ELCR: %02x, %02x\n", inb(0x4d0), inb(0x4d1));
>>>
>>> in, say, setup_dump_irqs()?
>>>
>>
> did that but I don't know how to trigger the dump.

There's no need to trigger the dump. The message will be logged during
boot, and hence ought to be visible in "xl dmesg" output.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le ven. 22 déc. 2023 à 15:37, Sébastien Chaumat <euidzero@gmail.com> a
écrit :

> By request of the laptop vendor (Framework) I'm going to open the bug
> @fedora for them to jump in.
>
>

 https://bugzilla.redhat.com/show_bug.cgi?id=2255625

Sébastien

[-- Attachment #2: Type: text/html, Size: 737 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

found the following issue with this similar HW setup :

https://marc.info/?l=linux-gpio&m=150605230614677&w=2

while in bare metal, I wonder if being in dom0 does not lead to the same
configuration :

Quoting :
---
"Under the I2C-HID spec, the device interrupt is level-triggered. When
the touchpad has data to report, it will bring the GPIO level low
(this is active-low), which should signal the host to read input
report data. The device will hold the GPIO low until there is no more
data that needs to be delivered.

The user-visible problem is that the touchpad appears to stop
responding after a short period of usage. At the i2c-hid driver level,
no more interrupts are arriving. We have checked with a scope that the
interrupt line is being held low at this point, which should mean that
the interrupt handler should be executed again since there is more
data to be read, but that is not happening here.

An easy way to reproduce this issue is to press multiple fingers on
the touchpad, which will result in a large amount of input data to be
queued up on the device side; however the interrupt handler will soon
stop firing so not all the data will be read, and everything stops
there...
"
^
 in my case the interrupt handler stop after one trigger.

"We observed that at the point where no more interrupts arrive, no
EOI_MASK write was sent at the point when i2c_irq_hid returned for the
last time (and is never called again). We found a potential solution
to this problem: by adding the IRQCHIP_EOI_THREADED flag, an EOI will
be sent at this point, and we are now unable to get the touchpad to
hang."
---


Sébastien
>

[-- Attachment #2: Type: text/html, Size: 2320 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le ven. 22 déc. 2023 à 15:37, Sébastien Chaumat <euidzero@gmail.com> a
écrit :

> By request of the laptop vendor (Framework) I'm going to open the bug
> @fedora for them to jump in.
>
>
>> > I noticed that on baremetal :
>> >
>> >   53:          0          0          0          0          0       1268
>> >      0          0          0          0          0          0          0
>> >        0          0          0  amd_gpio    5  FRMW0005:00
>> >   54:          0          0          0          0          0          1
>> >      0          0          0          0          0          0          0
>> >        0          0          0  amd_gpio   84  FRMW0004:00
>> >   55:          0          0          0          0          0       1403
>> >      0          0          0          0          0          0          0
>> >        0          0          0  amd_gpio    8  PIXA3854:00
>> >
>> > with xen with IRQ7 setup only once there's only (the touchpad is
>> > PIXA3854:00)
>> >
>> >  176:          0          0          0          0          0          0
>> >      1          0          0          0          0          0          0
>> >        0          0          0  amd_gpio    8
>> >
>>
> > Interestingly when IRQ7 is setup twice (normal xen)
>> >  176:          0          0          0          0          0          0
>> >      1          0          0          0          0          0          0
>> >        0          0          0  amd_gpio    8  PIXA3854:00
>>
>> That's odd, as with IRQ7 (wrongly) setup as edge, it should also be marked
>> as non-sharable. Otoh with the "i2c-PIXA3854:00:" error above it's no
>> surprise no interrupt is set up there.
>>
>
> forget this one, I made a mistake when skipping IRQ7.
>
> The "amd_gpio    8  PIXA3854:00"for  IRQ176 is identical with or without
> IRQ7 double initialization
>

 output of gpioinfo

kernel alone :

        line   5: unnamed         input active-low consumer=interrupt
        line  84: unnamed         input active-low consumer=interrupt

xen:

        line   5: unnamed         input active-low
        line  84: unnamed         input active-low

xen with skipping IRQ7 double init :

        line   5: unnamed         input active-low consumer=interrupt
        line  84: unnamed         input active-low


So definitely progressing.

[-- Attachment #2: Type: text/html, Size: 3721 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

>  output of gpioinfo
>
> kernel alone :
>
>         line   5: unnamed         input active-low consumer=interrupt
>         line  84: unnamed         input active-low consumer=interrupt
>
> xen:
>
>         line   5: unnamed         input active-low
>         line  84: unnamed         input active-low
>
> xen with skipping IRQ7 double init :
>
>         line   5: unnamed         input active-low consumer=interrupt
>         line  84: unnamed         input active-low
>
>
> So definitely progressing.
>

Checking /sys/kernel/irq/7

kernel alone :
 actions: pinctrl_amd
 chip_name: IR-IO-APIC
 hwirq: 7
 name: fasteoi
 per_cpu_count: 0,0,0,0,0,20,0,0,0,0,0,0,0,0,0,0
 type: level
 wakeup: enabled

xen skipping IRQ7 double init :

actions: pinctrl_amd
 chip_name: xen-pirq
 hwirq:
 name: ioapic-level
 per_cpu_count: 0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0
 type: edge
 wakeup: disabled

So the skip of IRQ7 in pci_xen_initial_domain() sets the correct handler
 (IIUC xen uses the ioapic-level and handles the eoi separately), but not
the correct type (still edge).
I guess this may explains the results above.

Sébastien

[-- Attachment #2: Type: text/html, Size: 1726 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le mar. 2 janv. 2024 à 21:23, Sébastien Chaumat <euidzero@gmail.com> a
écrit :

>
>  output of gpioinfo
>>
>> kernel alone :
>>
>>         line   5: unnamed         input active-low consumer=interrupt
>>         line  84: unnamed         input active-low consumer=interrupt
>>
>> xen:
>>
>>         line   5: unnamed         input active-low
>>         line  84: unnamed         input active-low
>>
>> xen with skipping IRQ7 double init :
>>
>>         line   5: unnamed         input active-low consumer=interrupt
>>         line  84: unnamed         input active-low
>>
>>
>> So definitely progressing.
>>
>
> Checking /sys/kernel/irq/7
>
> kernel alone :
>  actions: pinctrl_amd
>  chip_name: IR-IO-APIC
>  hwirq: 7
>  name: fasteoi
>  per_cpu_count: 0,0,0,0,0,20,0,0,0,0,0,0,0,0,0,0
>  type: level
>  wakeup: enabled
>
> xen skipping IRQ7 double init :
>
> actions: pinctrl_amd
>  chip_name: xen-pirq
>  hwirq:
>  name: ioapic-level
>  per_cpu_count: 0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0
>  type: edge
>  wakeup: disabled
>
> So the skip of IRQ7 in pci_xen_initial_domain() sets the correct handler
>  (IIUC xen uses the ioapic-level and handles the eoi separately), but not
> the correct type (still edge).
> I guess this may explains the results above.
>
>
 Mario (in CC) patched the pinctrl_amd to flush pending interrupt before
starting the driver for the GPIO.

This helped in  the sense of there's no more pending interrupt on IRQ7
(whatever the handler is, level or edge) but then the touchpad is not
detected by i2c-hid.

Is there any work in progress related to the incorrect IRQ configuration ?

Thanks,
Sébastien

[-- Attachment #2: Type: text/html, Size: 2689 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 16.01.2024 16:52, Sébastien Chaumat wrote:
> Le mar. 2 janv. 2024 à 21:23, Sébastien Chaumat <euidzero@gmail.com> a
> écrit :
> 
>>
>>  output of gpioinfo
>>>
>>> kernel alone :
>>>
>>>         line   5: unnamed         input active-low consumer=interrupt
>>>         line  84: unnamed         input active-low consumer=interrupt
>>>
>>> xen:
>>>
>>>         line   5: unnamed         input active-low
>>>         line  84: unnamed         input active-low
>>>
>>> xen with skipping IRQ7 double init :
>>>
>>>         line   5: unnamed         input active-low consumer=interrupt
>>>         line  84: unnamed         input active-low
>>>
>>>
>>> So definitely progressing.
>>>
>>
>> Checking /sys/kernel/irq/7
>>
>> kernel alone :
>>  actions: pinctrl_amd
>>  chip_name: IR-IO-APIC
>>  hwirq: 7
>>  name: fasteoi
>>  per_cpu_count: 0,0,0,0,0,20,0,0,0,0,0,0,0,0,0,0
>>  type: level
>>  wakeup: enabled
>>
>> xen skipping IRQ7 double init :
>>
>> actions: pinctrl_amd
>>  chip_name: xen-pirq
>>  hwirq:
>>  name: ioapic-level
>>  per_cpu_count: 0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0
>>  type: edge
>>  wakeup: disabled
>>
>> So the skip of IRQ7 in pci_xen_initial_domain() sets the correct handler
>>  (IIUC xen uses the ioapic-level and handles the eoi separately), but not
>> the correct type (still edge).
>> I guess this may explains the results above.
>>
>>
>  Mario (in CC) patched the pinctrl_amd to flush pending interrupt before
> starting the driver for the GPIO.
> 
> This helped in  the sense of there's no more pending interrupt on IRQ7
> (whatever the handler is, level or edge) but then the touchpad is not
> detected by i2c-hid.
> 
> Is there any work in progress related to the incorrect IRQ configuration ?

I'm not aware of any. As per my recollection it's still not entirely
clear where in the kernel things go astray. And to be honest I don't
feel comfortable trying to half-blindly address this, e.g. by trying
to circumvent / defer the early setting up of the low 16 IRQs.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 1/16/2024 10:18, Jan Beulich wrote:
> On 16.01.2024 16:52, Sébastien Chaumat wrote:
>> Le mar. 2 janv. 2024 à 21:23, Sébastien Chaumat <euidzero@gmail.com> a
>> écrit :
>>
>>>
>>>   output of gpioinfo
>>>>
>>>> kernel alone :
>>>>
>>>>          line   5: unnamed         input active-low consumer=interrupt
>>>>          line  84: unnamed         input active-low consumer=interrupt
>>>>
>>>> xen:
>>>>
>>>>          line   5: unnamed         input active-low
>>>>          line  84: unnamed         input active-low
>>>>
>>>> xen with skipping IRQ7 double init :
>>>>
>>>>          line   5: unnamed         input active-low consumer=interrupt
>>>>          line  84: unnamed         input active-low
>>>>
>>>>
>>>> So definitely progressing.
>>>>
>>>
>>> Checking /sys/kernel/irq/7
>>>
>>> kernel alone :
>>>   actions: pinctrl_amd
>>>   chip_name: IR-IO-APIC
>>>   hwirq: 7
>>>   name: fasteoi
>>>   per_cpu_count: 0,0,0,0,0,20,0,0,0,0,0,0,0,0,0,0
>>>   type: level
>>>   wakeup: enabled
>>>
>>> xen skipping IRQ7 double init :
>>>
>>> actions: pinctrl_amd
>>>   chip_name: xen-pirq
>>>   hwirq:
>>>   name: ioapic-level
>>>   per_cpu_count: 0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0
>>>   type: edge
>>>   wakeup: disabled
>>>
>>> So the skip of IRQ7 in pci_xen_initial_domain() sets the correct handler
>>>   (IIUC xen uses the ioapic-level and handles the eoi separately), but not
>>> the correct type (still edge).
>>> I guess this may explains the results above.
>>>
>>>
>>   Mario (in CC) patched the pinctrl_amd to flush pending interrupt before
>> starting the driver for the GPIO.
>>
>> This helped in  the sense of there's no more pending interrupt on IRQ7
>> (whatever the handler is, level or edge) but then the touchpad is not
>> detected by i2c-hid.
>>
>> Is there any work in progress related to the incorrect IRQ configuration ?
> 
> I'm not aware of any. As per my recollection it's still not entirely
> clear where in the kernel things go astray. And to be honest I don't
> feel comfortable trying to half-blindly address this, e.g. by trying
> to circumvent / defer the early setting up of the low 16 IRQs.
> 
> Jan

Shot in the dark - but could this be a problem where PCAT_COMPAT from 
the MADT is being ignored causing PIC not to be setup properly in the 
Xen case?

See https://lore.kernel.org/all/875y2u5s8g.ffs@tglx/ for some context.

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le mer. 17 janv. 2024 à 03:20, Mario Limonciello <mario.limonciello@amd.com>
a écrit :

> On 1/16/2024 10:18, Jan Beulich wrote:
> > On 16.01.2024 16:52, Sébastien Chaumat wrote:
> >> Le mar. 2 janv. 2024 à 21:23, Sébastien Chaumat <euidzero@gmail.com> a
> >> écrit :
> >>
> >>>
> >>>   output of gpioinfo
> >>>>
> >>>> kernel alone :
> >>>>
> >>>>          line   5: unnamed         input active-low consumer=interrupt
> >>>>          line  84: unnamed         input active-low consumer=interrupt
> >>>>
> >>>> xen:
> >>>>
> >>>>          line   5: unnamed         input active-low
> >>>>          line  84: unnamed         input active-low
> >>>>
> >>>> xen with skipping IRQ7 double init :
> >>>>
> >>>>          line   5: unnamed         input active-low consumer=interrupt
> >>>>          line  84: unnamed         input active-low
> >>>>
> >>>>
> >>>> So definitely progressing.
> >>>>
> >>>
> >>> Checking /sys/kernel/irq/7
> >>>
> >>> kernel alone :
> >>>   actions: pinctrl_amd
> >>>   chip_name: IR-IO-APIC
> >>>   hwirq: 7
> >>>   name: fasteoi
> >>>   per_cpu_count: 0,0,0,0,0,20,0,0,0,0,0,0,0,0,0,0
> >>>   type: level
> >>>   wakeup: enabled
> >>>
> >>> xen skipping IRQ7 double init :
> >>>
> >>> actions: pinctrl_amd
> >>>   chip_name: xen-pirq
> >>>   hwirq:
> >>>   name: ioapic-level
> >>>   per_cpu_count: 0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0
> >>>   type: edge
> >>>   wakeup: disabled
> >>>
> >>> So the skip of IRQ7 in pci_xen_initial_domain() sets the correct
> handler
> >>>   (IIUC xen uses the ioapic-level and handles the eoi separately), but
> not
> >>> the correct type (still edge).
> >>> I guess this may explains the results above.
> >>>
> >>>
> >>   Mario (in CC) patched the pinctrl_amd to flush pending interrupt
> before
> >> starting the driver for the GPIO.
> >>
> >> This helped in  the sense of there's no more pending interrupt on IRQ7
> >> (whatever the handler is, level or edge) but then the touchpad is not
> >> detected by i2c-hid.
> >>
> >> Is there any work in progress related to the incorrect IRQ
> configuration ?
> >
> > I'm not aware of any. As per my recollection it's still not entirely
> > clear where in the kernel things go astray. And to be honest I don't
> > feel comfortable trying to half-blindly address this, e.g. by trying
> > to circumvent / defer the early setting up of the low 16 IRQs.
> >
> > Jan
>
> Shot in the dark - but could this be a problem where PCAT_COMPAT from
> the MADT is being ignored causing PIC not to be setup properly in the
> Xen case?
>
> See https://lore.kernel.org/all/875y2u5s8g.ffs@tglx/ for some context.
>
> At least we know that no MADT override is found by xen for INT7 as no
INT_SRC_OVR message is printed.

Do we expect one @Mario Limonciello <mario.limonciello@amd.com>  ?

[-- Attachment #2: Type: text/html, Size: 4299 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 1/22/2024 11:06, Sébastien Chaumat wrote:
> 
> 
> Le mer. 17 janv. 2024 à 03:20, Mario Limonciello 
> <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>> a écrit :
> 
>     On 1/16/2024 10:18, Jan Beulich wrote:
>      > On 16.01.2024 16:52, Sébastien Chaumat wrote:
>      >> Le mar. 2 janv. 2024 à 21:23, Sébastien Chaumat
>     <euidzero@gmail.com <mailto:euidzero@gmail.com>> a
>      >> écrit :
>      >>
>      >>>
>      >>>   output of gpioinfo
>      >>>>
>      >>>> kernel alone :
>      >>>>
>      >>>>          line   5: unnamed         input active-low
>     consumer=interrupt
>      >>>>          line  84: unnamed         input active-low
>     consumer=interrupt
>      >>>>
>      >>>> xen:
>      >>>>
>      >>>>          line   5: unnamed         input active-low
>      >>>>          line  84: unnamed         input active-low
>      >>>>
>      >>>> xen with skipping IRQ7 double init :
>      >>>>
>      >>>>          line   5: unnamed         input active-low
>     consumer=interrupt
>      >>>>          line  84: unnamed         input active-low
>      >>>>
>      >>>>
>      >>>> So definitely progressing.
>      >>>>
>      >>>
>      >>> Checking /sys/kernel/irq/7
>      >>>
>      >>> kernel alone :
>      >>>   actions: pinctrl_amd
>      >>>   chip_name: IR-IO-APIC
>      >>>   hwirq: 7
>      >>>   name: fasteoi
>      >>>   per_cpu_count: 0,0,0,0,0,20,0,0,0,0,0,0,0,0,0,0
>      >>>   type: level
>      >>>   wakeup: enabled
>      >>>
>      >>> xen skipping IRQ7 double init :
>      >>>
>      >>> actions: pinctrl_amd
>      >>>   chip_name: xen-pirq
>      >>>   hwirq:
>      >>>   name: ioapic-level
>      >>>   per_cpu_count: 0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0
>      >>>   type: edge
>      >>>   wakeup: disabled
>      >>>
>      >>> So the skip of IRQ7 in pci_xen_initial_domain() sets the
>     correct handler
>      >>>   (IIUC xen uses the ioapic-level and handles the eoi
>     separately), but not
>      >>> the correct type (still edge).
>      >>> I guess this may explains the results above.
>      >>>
>      >>>
>      >>   Mario (in CC) patched the pinctrl_amd to flush pending
>     interrupt before
>      >> starting the driver for the GPIO.
>      >>
>      >> This helped in  the sense of there's no more pending interrupt
>     on IRQ7
>      >> (whatever the handler is, level or edge) but then the touchpad
>     is not
>      >> detected by i2c-hid.
>      >>
>      >> Is there any work in progress related to the incorrect IRQ
>     configuration ?
>      >
>      > I'm not aware of any. As per my recollection it's still not entirely
>      > clear where in the kernel things go astray. And to be honest I don't
>      > feel comfortable trying to half-blindly address this, e.g. by trying
>      > to circumvent / defer the early setting up of the low 16 IRQs.
>      >
>      > Jan
> 
>     Shot in the dark - but could this be a problem where PCAT_COMPAT from
>     the MADT is being ignored causing PIC not to be setup properly in the
>     Xen case?
> 
>     See https://lore.kernel.org/all/875y2u5s8g.ffs@tglx/
>     <https://lore.kernel.org/all/875y2u5s8g.ffs@tglx/> for some context.
> 
> At least we know that no MADT override is found by xen for INT7 as no 
> INT_SRC_OVR message is printed.
> 
> Do we expect one @Mario Limonciello <mailto:mario.limonciello@amd.com>  ?

No; the INT_SRV_OVR you'll see on Framework 13 AMD is on IRQ 2 and IRQ 9.

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

I spotted the following warning for IRQ7 (along with IRQ6 and 10)

[    0.686073] fedora kernel: __irq_set_trigger: genirq: No set_type
function for IRQ 7 (IR-IO-APIC)

This comes from kernel/irq/manage.c


int __irq_set_trigger(struct irq_desc *desc, unsigned long flags)
{
struct irq_chip *chip = desc->irq_data.chip;
int ret, unmask = 0;

if (!chip || !chip->irq_set_type) {
/*
* IRQF_TRIGGER_* but the PIC does not support multiple
* flow-types?
*/
pr_debug("No set_type function for IRQ %d (%s)\n",
irq_desc_get_irq(desc),
chip ? (chip->name ? : "unknown") : "unknown");
return 0;
}

Could this have a role in the IRQ misconfiguration by xen ?




Le lun. 22 janv. 2024 à 21:59, Mario Limonciello <mario.limonciello@amd.com>
a écrit :

> On 1/22/2024 11:06, Sébastien Chaumat wrote:
> >
> >
> > Le mer. 17 janv. 2024 à 03:20, Mario Limonciello
> > <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>> a écrit :
> >
> >     On 1/16/2024 10:18, Jan Beulich wrote:
> >      > On 16.01.2024 16:52, Sébastien Chaumat wrote:
> >      >> Le mar. 2 janv. 2024 à 21:23, Sébastien Chaumat
> >     <euidzero@gmail.com <mailto:euidzero@gmail.com>> a
> >      >> écrit :
> >      >>
> >      >>>
> >      >>>   output of gpioinfo
> >      >>>>
> >      >>>> kernel alone :
> >      >>>>
> >      >>>>          line   5: unnamed         input active-low
> >     consumer=interrupt
> >      >>>>          line  84: unnamed         input active-low
> >     consumer=interrupt
> >      >>>>
> >      >>>> xen:
> >      >>>>
> >      >>>>          line   5: unnamed         input active-low
> >      >>>>          line  84: unnamed         input active-low
> >      >>>>
> >      >>>> xen with skipping IRQ7 double init :
> >      >>>>
> >      >>>>          line   5: unnamed         input active-low
> >     consumer=interrupt
> >      >>>>          line  84: unnamed         input active-low
> >      >>>>
> >      >>>>
> >      >>>> So definitely progressing.
> >      >>>>
> >      >>>
> >      >>> Checking /sys/kernel/irq/7
> >      >>>
> >      >>> kernel alone :
> >      >>>   actions: pinctrl_amd
> >      >>>   chip_name: IR-IO-APIC
> >      >>>   hwirq: 7
> >      >>>   name: fasteoi
> >      >>>   per_cpu_count: 0,0,0,0,0,20,0,0,0,0,0,0,0,0,0,0
> >      >>>   type: level
> >      >>>   wakeup: enabled
> >      >>>
> >      >>> xen skipping IRQ7 double init :
> >      >>>
> >      >>> actions: pinctrl_amd
> >      >>>   chip_name: xen-pirq
> >      >>>   hwirq:
> >      >>>   name: ioapic-level
> >      >>>   per_cpu_count: 0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0
> >      >>>   type: edge
> >      >>>   wakeup: disabled
> >      >>>
> >      >>> So the skip of IRQ7 in pci_xen_initial_domain() sets the
> >     correct handler
> >      >>>   (IIUC xen uses the ioapic-level and handles the eoi
> >     separately), but not
> >      >>> the correct type (still edge).
> >      >>> I guess this may explains the results above.
> >      >>>
> >      >>>
> >      >>   Mario (in CC) patched the pinctrl_amd to flush pending
> >     interrupt before
> >      >> starting the driver for the GPIO.
> >      >>
> >      >> This helped in  the sense of there's no more pending interrupt
> >     on IRQ7
> >      >> (whatever the handler is, level or edge) but then the touchpad
> >     is not
> >      >> detected by i2c-hid.
> >      >>
> >      >> Is there any work in progress related to the incorrect IRQ
> >     configuration ?
> >      >
> >      > I'm not aware of any. As per my recollection it's still not
> entirely
> >      > clear where in the kernel things go astray. And to be honest I
> don't
> >      > feel comfortable trying to half-blindly address this, e.g. by
> trying
> >      > to circumvent / defer the early setting up of the low 16 IRQs.
> >      >
> >      > Jan
> >
> >     Shot in the dark - but could this be a problem where PCAT_COMPAT from
> >     the MADT is being ignored causing PIC not to be setup properly in the
> >     Xen case?
> >
> >     See https://lore.kernel.org/all/875y2u5s8g.ffs@tglx/
> >     <https://lore.kernel.org/all/875y2u5s8g.ffs@tglx/> for some context.
> >
> > At least we know that no MADT override is found by xen for INT7 as no
> > INT_SRC_OVR message is printed.
> >
> > Do we expect one @Mario Limonciello <mailto:mario.limonciello@amd.com>
> ?
>
> No; the INT_SRV_OVR you'll see on Framework 13 AMD is on IRQ 2 and IRQ 9.
>
>

[-- Attachment #2: Type: text/html, Size: 11026 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le jeu. 1 févr. 2024 à 13:30, Sébastien Chaumat <euidzero@gmail.com> a
écrit :

> I spotted the following warning for IRQ7 (along with IRQ6 and 10)
>
> [    0.686073] fedora kernel: __irq_set_trigger: genirq: No set_type
> function for IRQ 7 (IR-IO-APIC)
>
> This comes from kernel/irq/manage.c
>
>
> int __irq_set_trigger(struct irq_desc *desc, unsigned long flags)
> {
> struct irq_chip *chip = desc->irq_data.chip;
> int ret, unmask = 0;
>
> if (!chip || !chip->irq_set_type) {
> /*
> * IRQF_TRIGGER_* but the PIC does not support multiple
> * flow-types?
> */
> pr_debug("No set_type function for IRQ %d (%s)\n",
> irq_desc_get_irq(desc),
> chip ? (chip->name ? : "unknown") : "unknown");
> return 0;
> }
> Could this have a role in the IRQ misconfiguration by xen ?
>

 Things are getting even weirder :

xen 4.18.1-pre (vanilla, no patching of pci_xen_initial_domain()), kernel
6.8.0-rc2) :

checking /sys/kernel/irq/7 :

actions: pinctrl_amd
chip_name: xen-pirq
hwirq:
name: ioapic-edge
per_cpu_count: 0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0
type: edge
wakeup: disabled

now checking  xen with xl debug-key i

(XEN)    IRQ:   7 vec:51 IO-APIC-level   status=030 aff:{13}/{13}
in-flight=0 d0:  7(---)
(XEN)     IRQ  7 Vec 81:
(XEN)       Apic 0x00, Pin  7: vec=51 delivery=Fixed dest=P status=1
polarity=1 irr=1 trig=L mask=0 dest_id:0000510d

So even after dom0 is set up, the kernel considers  IRQ7 is of type edge
while xen has it registered as IO-APIC-level.

[-- Attachment #2: Type: text/html, Size: 2338 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le jeu. 1 févr. 2024 à 13:30, Sébastien Chaumat <euidzero@gmail.com> a
écrit :

> I spotted the following warning for IRQ7 (along with IRQ6 and 10)
>>
>> [    0.686073] fedora kernel: __irq_set_trigger: genirq: No set_type
>> function for IRQ 7 (IR-IO-APIC)
>>
>> This comes from kernel/irq/manage.c
>>
>>
>> int __irq_set_trigger(struct irq_desc *desc, unsigned long flags)
>> {
>> struct irq_chip *chip = desc->irq_data.chip;
>> int ret, unmask = 0;
>>
>> if (!chip || !chip->irq_set_type) {
>> /*
>> * IRQF_TRIGGER_* but the PIC does not support multiple
>> * flow-types?
>> */
>> pr_debug("No set_type function for IRQ %d (%s)\n",
>> irq_desc_get_irq(desc),
>> chip ? (chip->name ? : "unknown") : "unknown");
>> return 0;
>> }
>> Could this have a role in the IRQ misconfiguration by xen ?
>>
>
>  Things are getting even weirder :
>
> xen 4.18.1-pre (vanilla, no patching of pci_xen_initial_domain()), kernel
> 6.8.0-rc2) :
>
> checking /sys/kernel/irq/7 :
>
> actions: pinctrl_amd
> chip_name: xen-pirq
> hwirq:
> name: ioapic-edge
> per_cpu_count: 0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0
> type: edge
> wakeup: disabled
>
> now checking  xen with xl debug-key i
>
> (XEN)    IRQ:   7 vec:51 IO-APIC-level   status=030 aff:{13}/{13}
> in-flight=0 d0:  7(---)
> (XEN)     IRQ  7 Vec 81:
> (XEN)       Apic 0x00, Pin  7: vec=51 delivery=Fixed dest=P status=1
> polarity=1 irr=1 trig=L mask=0 dest_id:0000510d
>
> So even after dom0 is set up, the kernel considers  IRQ7 is of type edge
> while xen has it registered as IO-APIC-level.
>
> Reasoning backward  (using a  kernel without the pinctrl_amd driver to
ensure xen only is at stake) :
 checking the diff in IOAPIC  between bare metal and xen  (IRQ7 is on pin07
on APIC )

using kernel argument : apic=debug

bare metal :
[    0.715330] fedora kernel: ... APIC VERSION: 81050010
...
[    0.715433] fedora kernel:  pin07, disabled, edge , high, V(00), IRR(0),
S(0), physical, D(0000), M(0)

xen :
[    2.249582] fedora kernel: ... APIC VERSION: 00000014
...
[    2.249730] fedora kernel:  pin07, disabled, level, low , V(60), IRR(0),
S(0), physical, D(0000), M(0)

So the APIC table is not the same.

As strange as it looks the  (IOAPIC 0) pin07 is correctly described by the
APIC in xen but yet differently than in baremetal.
But the APIC message comes long after the
[    1.833145] fedora kernel: xen: registering gsi 7 triggering 0 polarity 1

so I wonder if the APIC pin07 info had any influence.

[-- Attachment #2: Type: text/html, Size: 3636 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Reasoning backward  (using a  kernel without the pinctrl_amd driver to
> ensure xen only is at stake) :
>  checking the diff in IOAPIC  between bare metal and xen  (IRQ7 is on
> pin07 on APIC )
>
> using kernel argument : apic=debug
>
> bare metal :
> [    0.715330] fedora kernel: ... APIC VERSION: 81050010
> ...
> [    0.715433] fedora kernel:  pin07, disabled, edge , high, V(00),
> IRR(0), S(0), physical, D(0000), M(0)
>
> xen :
> [    2.249582] fedora kernel: ... APIC VERSION: 00000014
> ...
> [    2.249730] fedora kernel:  pin07, disabled, level, low , V(60),
> IRR(0), S(0), physical, D(0000), M(0)
>
> So the APIC table is not the same.
>
> As strange as it looks the  (IOAPIC 0) pin07 is correctly described by the
> APIC in xen but yet differently than in baremetal.
> But the APIC message comes long after the
> [    1.833145] fedora kernel: xen: registering gsi 7 triggering 0 polarity
> 1
>
> so I wonder if the APIC pin07 info had any influence.
>
> Finally found the fix : adding ioapic_ack=new to xen boot parameters.
Not only the trackpad is now working but also the ACPI Embedded Controller
which is completely disabled.

Sébastien

[-- Attachment #2: Type: text/html, Size: 1900 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 3/6/2024 11:28, Sébastien Chaumat wrote:
> 
> 
> 
> 
>     Reasoning backward  (using a  kernel without the pinctrl_amd driver
>     to ensure xen only is at stake) :
>       checking the diff in IOAPIC  between bare metal and xen  (IRQ7 is
>     on pin07 on APIC )
> 
>     using kernel argument : apic=debug
> 
>     bare metal :
>     [    0.715330] fedora kernel: ... APIC VERSION: 81050010
>     ...
>     [    0.715433] fedora kernel:  pin07, disabled, edge , high, V(00),
>     IRR(0), S(0), physical, D(0000), M(0)
> 
>     xen :
>     [    2.249582] fedora kernel: ... APIC VERSION: 00000014
>     ...
>     [    2.249730] fedora kernel:  pin07, disabled, level, low , V(60),
>     IRR(0), S(0), physical, D(0000), M(0)
> 
>     So the APIC table is not the same.
> 
>     As strange as it looks the  (IOAPIC 0) pin07 is correctly described
>     by the APIC in xen but yet differently than in baremetal.
>     But the APIC message comes long after the
>     [    1.833145] fedora kernel: xen: registering gsi 7 triggering 0
>     polarity 1
> 
>     so I wonder if the APIC pin07 info had any influence.
> 
> Finally found the fix : adding ioapic_ack=new to xen boot parameters.
> Not only the trackpad is now working but also the ACPI Embedded 
> Controller which is completely disabled.
> 
> Sébastien
> 
That's great news!  I'm personally totally unfamiliar with 
ioapic_ack=new, so I did a quick search and found out it's a Xen 
parameter (I came across
https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html).

This mentions that "new" should be the default, so why isn't it the case?

Also; I'd be really interested to hear what happens with s2idle with Xen 
now (if it works).

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le mer. 6 mars 2024 à 18:33, Mario Limonciello <mario.limonciello@amd.com>
a écrit :

> On 3/6/2024 11:28, Sébastien Chaumat wrote:
> >
> >
> >
> >
> >     Reasoning backward  (using a  kernel without the pinctrl_amd driver
> >     to ensure xen only is at stake) :
> >       checking the diff in IOAPIC  between bare metal and xen  (IRQ7 is
> >     on pin07 on APIC )
> >
> >     using kernel argument : apic=debug
> >
> >     bare metal :
> >     [    0.715330] fedora kernel: ... APIC VERSION: 81050010
> >     ...
> >     [    0.715433] fedora kernel:  pin07, disabled, edge , high, V(00),
> >     IRR(0), S(0), physical, D(0000), M(0)
> >
> >     xen :
> >     [    2.249582] fedora kernel: ... APIC VERSION: 00000014
> >     ...
> >     [    2.249730] fedora kernel:  pin07, disabled, level, low , V(60),
> >     IRR(0), S(0), physical, D(0000), M(0)
> >
> >     So the APIC table is not the same.
> >
> >     As strange as it looks the  (IOAPIC 0) pin07 is correctly described
> >     by the APIC in xen but yet differently than in baremetal.
> >     But the APIC message comes long after the
> >     [    1.833145] fedora kernel: xen: registering gsi 7 triggering 0
> >     polarity 1
> >
> >     so I wonder if the APIC pin07 info had any influence.
> >
> > Finally found the fix : adding ioapic_ack=new to xen boot parameters.
> > Not only the trackpad is now working but also the ACPI Embedded
> > Controller which is completely disabled.
> >
> > Sébastien
> >
> That's great news!  I'm personally totally unfamiliar with
> ioapic_ack=new, so I did a quick search and found out it's a Xen
> parameter (I came across
> https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html).
>
> This mentions that "new" should be the default, so why isn't it the case?
>

 "This is the the default unless directed-EOI is supported"
xl dmesg without forcing the parameters shows :

(XEN) Enabled directed EOI with ioapic_ack_old on!


> Also; I'd be really interested to hear what happens with s2idle with Xen
> now (if it works).
>

suspend to RAM now works :)

[-- Attachment #2: Type: text/html, Size: 3079 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 3/6/2024 12:05, Sébastien Chaumat wrote:
> 
> 
> Le mer. 6 mars 2024 à 18:33, Mario Limonciello 
> <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>> a écrit :
> 
>     On 3/6/2024 11:28, Sébastien Chaumat wrote:
>      >
>      >
>      >
>      >
>      >     Reasoning backward  (using a  kernel without the pinctrl_amd
>     driver
>      >     to ensure xen only is at stake) :
>      >       checking the diff in IOAPIC  between bare metal and xen 
>     (IRQ7 is
>      >     on pin07 on APIC )
>      >
>      >     using kernel argument : apic=debug
>      >
>      >     bare metal :
>      >     [    0.715330] fedora kernel: ... APIC VERSION: 81050010
>      >     ...
>      >     [    0.715433] fedora kernel:  pin07, disabled, edge , high,
>     V(00),
>      >     IRR(0), S(0), physical, D(0000), M(0)
>      >
>      >     xen :
>      >     [    2.249582] fedora kernel: ... APIC VERSION: 00000014
>      >     ...
>      >     [    2.249730] fedora kernel:  pin07, disabled, level, low ,
>     V(60),
>      >     IRR(0), S(0), physical, D(0000), M(0)
>      >
>      >     So the APIC table is not the same.
>      >
>      >     As strange as it looks the  (IOAPIC 0) pin07 is correctly
>     described
>      >     by the APIC in xen but yet differently than in baremetal.
>      >     But the APIC message comes long after the
>      >     [    1.833145] fedora kernel: xen: registering gsi 7 triggering 0
>      >     polarity 1
>      >
>      >     so I wonder if the APIC pin07 info had any influence.
>      >
>      > Finally found the fix : adding ioapic_ack=new to xen boot parameters.
>      > Not only the trackpad is now working but also the ACPI Embedded
>      > Controller which is completely disabled.
>      >
>      > Sébastien
>      >
>     That's great news!  I'm personally totally unfamiliar with
>     ioapic_ack=new, so I did a quick search and found out it's a Xen
>     parameter (I came across
>     https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html
>     <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>).
> 
>     This mentions that "new" should be the default, so why isn't it the
>     case?
> 
> 
>   "This is the the default unless directed-EOI is supported"
> xl dmesg without forcing the parameters shows :
> 
> (XEN) Enabled directed EOI with ioapic_ack_old on!

Got it; it sounds to me like a logic mismatch in Xen then.

> 
>     Also; I'd be really interested to hear what happens with s2idle with
>     Xen
>     now (if it works).
> 
> 
> suspend to RAM now works :)

Do you see /sys/power/suspend_stats/last_hw_sleep increasing with your 
suspend cycle?

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le mer. 6 mars 2024 à 19:08, Mario Limonciello <mario.limonciello@amd.com>
a écrit :

> On 3/6/2024 12:05, Sébastien Chaumat wrote:
> >
> >
> > Le mer. 6 mars 2024 à 18:33, Mario Limonciello
> > <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>> a écrit :
> >
> >     On 3/6/2024 11:28, Sébastien Chaumat wrote:
> >      >
> >      >
> >      >
> >      >
> >      >     Reasoning backward  (using a  kernel without the pinctrl_amd
> >     driver
> >      >     to ensure xen only is at stake) :
> >      >       checking the diff in IOAPIC  between bare metal and xen
> >     (IRQ7 is
> >      >     on pin07 on APIC )
> >      >
> >      >     using kernel argument : apic=debug
> >      >
> >      >     bare metal :
> >      >     [    0.715330] fedora kernel: ... APIC VERSION: 81050010
> >      >     ...
> >      >     [    0.715433] fedora kernel:  pin07, disabled, edge , high,
> >     V(00),
> >      >     IRR(0), S(0), physical, D(0000), M(0)
> >      >
> >      >     xen :
> >      >     [    2.249582] fedora kernel: ... APIC VERSION: 00000014
> >      >     ...
> >      >     [    2.249730] fedora kernel:  pin07, disabled, level, low ,
> >     V(60),
> >      >     IRR(0), S(0), physical, D(0000), M(0)
> >      >
> >      >     So the APIC table is not the same.
> >      >
> >      >     As strange as it looks the  (IOAPIC 0) pin07 is correctly
> >     described
> >      >     by the APIC in xen but yet differently than in baremetal.
> >      >     But the APIC message comes long after the
> >      >     [    1.833145] fedora kernel: xen: registering gsi 7
> triggering 0
> >      >     polarity 1
> >      >
> >      >     so I wonder if the APIC pin07 info had any influence.
> >      >
> >      > Finally found the fix : adding ioapic_ack=new to xen boot
> parameters.
> >      > Not only the trackpad is now working but also the ACPI Embedded
> >      > Controller which is completely disabled.
> >      >
> >      > Sébastien
> >      >
> >     That's great news!  I'm personally totally unfamiliar with
> >     ioapic_ack=new, so I did a quick search and found out it's a Xen
> >     parameter (I came across
> >     https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html
> >     <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html
> >).
> >
> >     This mentions that "new" should be the default, so why isn't it the
> >     case?
> >
> >
> >   "This is the the default unless directed-EOI is supported"
> > xl dmesg without forcing the parameters shows :
> >
> > (XEN) Enabled directed EOI with ioapic_ack_old on!
>
> Got it; it sounds to me like a logic mismatch in Xen then.
>
> >
> >     Also; I'd be really interested to hear what happens with s2idle with
> >     Xen
> >     now (if it works).
> >
> >
> > suspend to RAM now works :)
>
> Do you see /sys/power/suspend_stats/last_hw_sleep increasing with your
> suspend cycle?
>

No,  it does not increase (0).

[-- Attachment #2: Type: text/html, Size: 4546 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 3/6/2024 12:49, Sébastien Chaumat wrote:
> 
> 
> Le mer. 6 mars 2024 à 19:08, Mario Limonciello 
> <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>> a écrit :
> 
>     On 3/6/2024 12:05, Sébastien Chaumat wrote:
>      >
>      >
>      > Le mer. 6 mars 2024 à 18:33, Mario Limonciello
>      > <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>
>     <mailto:mario.limonciello@amd.com
>     <mailto:mario.limonciello@amd.com>>> a écrit :
>      >
>      >     On 3/6/2024 11:28, Sébastien Chaumat wrote:
>      >      >
>      >      >
>      >      >
>      >      >
>      >      >     Reasoning backward  (using a  kernel without the
>     pinctrl_amd
>      >     driver
>      >      >     to ensure xen only is at stake) :
>      >      >       checking the diff in IOAPIC  between bare metal and xen
>      >     (IRQ7 is
>      >      >     on pin07 on APIC )
>      >      >
>      >      >     using kernel argument : apic=debug
>      >      >
>      >      >     bare metal :
>      >      >     [    0.715330] fedora kernel: ... APIC VERSION: 81050010
>      >      >     ...
>      >      >     [    0.715433] fedora kernel:  pin07, disabled, edge ,
>     high,
>      >     V(00),
>      >      >     IRR(0), S(0), physical, D(0000), M(0)
>      >      >
>      >      >     xen :
>      >      >     [    2.249582] fedora kernel: ... APIC VERSION: 00000014
>      >      >     ...
>      >      >     [    2.249730] fedora kernel:  pin07, disabled, level,
>     low ,
>      >     V(60),
>      >      >     IRR(0), S(0), physical, D(0000), M(0)
>      >      >
>      >      >     So the APIC table is not the same.
>      >      >
>      >      >     As strange as it looks the  (IOAPIC 0) pin07 is correctly
>      >     described
>      >      >     by the APIC in xen but yet differently than in baremetal.
>      >      >     But the APIC message comes long after the
>      >      >     [    1.833145] fedora kernel: xen: registering gsi 7
>     triggering 0
>      >      >     polarity 1
>      >      >
>      >      >     so I wonder if the APIC pin07 info had any influence.
>      >      >
>      >      > Finally found the fix : adding ioapic_ack=new to xen boot
>     parameters.
>      >      > Not only the trackpad is now working but also the ACPI
>     Embedded
>      >      > Controller which is completely disabled.
>      >      >
>      >      > Sébastien
>      >      >
>      >     That's great news!  I'm personally totally unfamiliar with
>      >     ioapic_ack=new, so I did a quick search and found out it's a Xen
>      >     parameter (I came across
>      >
>     https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html
>     <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>
>      >   
>       <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>>).
>      >
>      >     This mentions that "new" should be the default, so why isn't
>     it the
>      >     case?
>      >
>      >
>      >   "This is the the default unless directed-EOI is supported"
>      > xl dmesg without forcing the parameters shows :
>      >
>      > (XEN) Enabled directed EOI with ioapic_ack_old on!
> 
>     Got it; it sounds to me like a logic mismatch in Xen then.
> 
>      >
>      >     Also; I'd be really interested to hear what happens with
>     s2idle with
>      >     Xen
>      >     now (if it works).
>      >
>      >
>      > suspend to RAM now works :)
> 
>     Do you see /sys/power/suspend_stats/last_hw_sleep increasing with your
>     suspend cycle?
> 
> 
> No,  it does not increase (0).
> 

OK, then in that case I suggest you run 
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py 
in the hypervisor to find out what's wrong.

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le mer. 6 mars 2024 à 19:51, Mario Limonciello <mario.limonciello@amd.com>
a écrit :

> On 3/6/2024 12:49, Sébastien Chaumat wrote:
> >
> >
> > Le mer. 6 mars 2024 à 19:08, Mario Limonciello
> > <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>> a écrit :
> >
> >     On 3/6/2024 12:05, Sébastien Chaumat wrote:
> >      >
> >      >
> >      > Le mer. 6 mars 2024 à 18:33, Mario Limonciello
> >      > <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>
> >     <mailto:mario.limonciello@amd.com
> >     <mailto:mario.limonciello@amd.com>>> a écrit :
> >      >
> >      >     On 3/6/2024 11:28, Sébastien Chaumat wrote:
> >      >      >
> >      >      >
> >      >      >
> >      >      >
> >      >      >     Reasoning backward  (using a  kernel without the
> >     pinctrl_amd
> >      >     driver
> >      >      >     to ensure xen only is at stake) :
> >      >      >       checking the diff in IOAPIC  between bare metal and
> xen
> >      >     (IRQ7 is
> >      >      >     on pin07 on APIC )
> >      >      >
> >      >      >     using kernel argument : apic=debug
> >      >      >
> >      >      >     bare metal :
> >      >      >     [    0.715330] fedora kernel: ... APIC VERSION:
> 81050010
> >      >      >     ...
> >      >      >     [    0.715433] fedora kernel:  pin07, disabled, edge ,
> >     high,
> >      >     V(00),
> >      >      >     IRR(0), S(0), physical, D(0000), M(0)
> >      >      >
> >      >      >     xen :
> >      >      >     [    2.249582] fedora kernel: ... APIC VERSION:
> 00000014
> >      >      >     ...
> >      >      >     [    2.249730] fedora kernel:  pin07, disabled, level,
> >     low ,
> >      >     V(60),
> >      >      >     IRR(0), S(0), physical, D(0000), M(0)
> >      >      >
> >      >      >     So the APIC table is not the same.
> >      >      >
> >      >      >     As strange as it looks the  (IOAPIC 0) pin07 is
> correctly
> >      >     described
> >      >      >     by the APIC in xen but yet differently than in
> baremetal.
> >      >      >     But the APIC message comes long after the
> >      >      >     [    1.833145] fedora kernel: xen: registering gsi 7
> >     triggering 0
> >      >      >     polarity 1
> >      >      >
> >      >      >     so I wonder if the APIC pin07 info had any influence.
> >      >      >
> >      >      > Finally found the fix : adding ioapic_ack=new to xen boot
> >     parameters.
> >      >      > Not only the trackpad is now working but also the ACPI
> >     Embedded
> >      >      > Controller which is completely disabled.
> >      >      >
> >      >      > Sébastien
> >      >      >
> >      >     That's great news!  I'm personally totally unfamiliar with
> >      >     ioapic_ack=new, so I did a quick search and found out it's a
> Xen
> >      >     parameter (I came across
> >      >
> >     https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html
> >     <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html
> >
> >      >
> >       <
> https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html <
> https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>>).
> >      >
> >      >     This mentions that "new" should be the default, so why isn't
> >     it the
> >      >     case?
> >      >
> >      >
> >      >   "This is the the default unless directed-EOI is supported"
> >      > xl dmesg without forcing the parameters shows :
> >      >
> >      > (XEN) Enabled directed EOI with ioapic_ack_old on!
> >
> >     Got it; it sounds to me like a logic mismatch in Xen then.
> >
> >      >
> >      >     Also; I'd be really interested to hear what happens with
> >     s2idle with
> >      >     Xen
> >      >     now (if it works).
> >      >
> >      >
> >      > suspend to RAM now works :)
> >
> >     Do you see /sys/power/suspend_stats/last_hw_sleep increasing with
> your
> >     suspend cycle?
> >
> >
> > No,  it does not increase (0).
> >
>
> OK, then in that case I suggest you run
> https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py
> in the hypervisor to find out what's wrong.
>
>
It fails with xen (not bare metal) during the prerequisite tests :

✅ GPIO driver `pinctrl_amd` available
Traceback (most recent call last):
  File "/home/sch/Downloads/amd_s2idle.py", line 2447, in <module>
    test = app.prerequisites()
           ^^^^^^^^^^^^^^^^^^^
  File "/home/sch/Downloads/amd_s2idle.py", line 1938, in prerequisites
    if not check():
           ^^^^^^^
  File "/home/sch/Downloads/amd_s2idle.py", line 826, in check_msr
    val = read_msr(reg, 0)
          ^^^^^^^^^^^^^^^^
  File "/home/sch/Downloads/amd_s2idle.py", line 813, in read_msr
    val = struct.unpack("Q", os.read(f, 8))[0]
                             ^^^^^^^^^^^^^
OSError: [Errno 5] Input/output error

Last line in the log is :
2024-03-06 21:29:33,146 DEBUG: Lockdown: [none] integrity confidentiality

[-- Attachment #2: Type: text/html, Size: 8041 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 3/6/2024 14:34, Sébastien Chaumat wrote:
> 
> 
> Le mer. 6 mars 2024 à 19:51, Mario Limonciello 
> <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>> a écrit :
> 
>     On 3/6/2024 12:49, Sébastien Chaumat wrote:
>      >
>      >
>      > Le mer. 6 mars 2024 à 19:08, Mario Limonciello
>      > <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>
>     <mailto:mario.limonciello@amd.com
>     <mailto:mario.limonciello@amd.com>>> a écrit :
>      >
>      >     On 3/6/2024 12:05, Sébastien Chaumat wrote:
>      >      >
>      >      >
>      >      > Le mer. 6 mars 2024 à 18:33, Mario Limonciello
>      >      > <mario.limonciello@amd.com
>     <mailto:mario.limonciello@amd.com> <mailto:mario.limonciello@amd.com
>     <mailto:mario.limonciello@amd.com>>
>      >     <mailto:mario.limonciello@amd.com
>     <mailto:mario.limonciello@amd.com>
>      >     <mailto:mario.limonciello@amd.com
>     <mailto:mario.limonciello@amd.com>>>> a écrit :
>      >      >
>      >      >     On 3/6/2024 11:28, Sébastien Chaumat wrote:
>      >      >      >
>      >      >      >
>      >      >      >
>      >      >      >
>      >      >      >     Reasoning backward  (using a  kernel without the
>      >     pinctrl_amd
>      >      >     driver
>      >      >      >     to ensure xen only is at stake) :
>      >      >      >       checking the diff in IOAPIC  between bare
>     metal and xen
>      >      >     (IRQ7 is
>      >      >      >     on pin07 on APIC )
>      >      >      >
>      >      >      >     using kernel argument : apic=debug
>      >      >      >
>      >      >      >     bare metal :
>      >      >      >     [    0.715330] fedora kernel: ... APIC VERSION:
>     81050010
>      >      >      >     ...
>      >      >      >     [    0.715433] fedora kernel:  pin07, disabled,
>     edge ,
>      >     high,
>      >      >     V(00),
>      >      >      >     IRR(0), S(0), physical, D(0000), M(0)
>      >      >      >
>      >      >      >     xen :
>      >      >      >     [    2.249582] fedora kernel: ... APIC VERSION:
>     00000014
>      >      >      >     ...
>      >      >      >     [    2.249730] fedora kernel:  pin07, disabled,
>     level,
>      >     low ,
>      >      >     V(60),
>      >      >      >     IRR(0), S(0), physical, D(0000), M(0)
>      >      >      >
>      >      >      >     So the APIC table is not the same.
>      >      >      >
>      >      >      >     As strange as it looks the  (IOAPIC 0) pin07 is
>     correctly
>      >      >     described
>      >      >      >     by the APIC in xen but yet differently than in
>     baremetal.
>      >      >      >     But the APIC message comes long after the
>      >      >      >     [    1.833145] fedora kernel: xen: registering
>     gsi 7
>      >     triggering 0
>      >      >      >     polarity 1
>      >      >      >
>      >      >      >     so I wonder if the APIC pin07 info had any
>     influence.
>      >      >      >
>      >      >      > Finally found the fix : adding ioapic_ack=new to
>     xen boot
>      >     parameters.
>      >      >      > Not only the trackpad is now working but also the ACPI
>      >     Embedded
>      >      >      > Controller which is completely disabled.
>      >      >      >
>      >      >      > Sébastien
>      >      >      >
>      >      >     That's great news!  I'm personally totally unfamiliar with
>      >      >     ioapic_ack=new, so I did a quick search and found out
>     it's a Xen
>      >      >     parameter (I came across
>      >      >
>      >
>     https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html
>     <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>
>      >   
>       <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>>
>      >      >
>      >     
>       <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html> <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>>>).
>      >      >
>      >      >     This mentions that "new" should be the default, so why
>     isn't
>      >     it the
>      >      >     case?
>      >      >
>      >      >
>      >      >   "This is the the default unless directed-EOI is supported"
>      >      > xl dmesg without forcing the parameters shows :
>      >      >
>      >      > (XEN) Enabled directed EOI with ioapic_ack_old on!
>      >
>      >     Got it; it sounds to me like a logic mismatch in Xen then.
>      >
>      >      >
>      >      >     Also; I'd be really interested to hear what happens with
>      >     s2idle with
>      >      >     Xen
>      >      >     now (if it works).
>      >      >
>      >      >
>      >      > suspend to RAM now works :)
>      >
>      >     Do you see /sys/power/suspend_stats/last_hw_sleep increasing
>     with your
>      >     suspend cycle?
>      >
>      >
>      > No,  it does not increase (0).
>      >
> 
>     OK, then in that case I suggest you run
>     https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py <https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py>
>     in the hypervisor to find out what's wrong.
> 
> 
> It fails with xen (not bare metal) during the prerequisite tests :
> 

The script might need some modifications for tests that don't make sense 
in the context of Xen.

> ✅ GPIO driver `pinctrl_amd` available
> Traceback (most recent call last):
>    File "/home/sch/Downloads/amd_s2idle.py", line 2447, in <module>
>      test = app.prerequisites()
>             ^^^^^^^^^^^^^^^^^^^
>    File "/home/sch/Downloads/amd_s2idle.py", line 1938, in prerequisites
>      if not check():
>             ^^^^^^^
>    File "/home/sch/Downloads/amd_s2idle.py", line 826, in check_msr
>      val = read_msr(reg, 0)
>            ^^^^^^^^^^^^^^^^
>    File "/home/sch/Downloads/amd_s2idle.py", line 813, in read_msr
>      val = struct.unpack("Q", os.read(f, 8))[0]
>                               ^^^^^^^^^^^^^
> OSError: [Errno 5] Input/output error
> 
> Last line in the log is :
> 2024-03-06 21:29:33,146 DEBUG: Lockdown: [none] integrity confidentiality
> 

Do you have userspace MSR support compiled in?  If not; that could 
explain that problem.  But it's very unlikely you changed the MSRs.
For the purpose of finding where the suspend problem is, I'd comment out 
that specific check for now.

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Marek Marczykowski-Górecki]

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

On Wed, Mar 06, 2024 at 02:37:20PM -0600, Mario Limonciello wrote:
> On 3/6/2024 14:34, Sébastien Chaumat wrote:
> > 
> > 
> > Le mer. 6 mars 2024 à 19:51, Mario Limonciello
> > <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>> a écrit :
> > 
> >     On 3/6/2024 12:49, Sébastien Chaumat wrote:
> >      >
> >      >
> >      > Le mer. 6 mars 2024 à 19:08, Mario Limonciello
> >      > <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>
> >     <mailto:mario.limonciello@amd.com
> >     <mailto:mario.limonciello@amd.com>>> a écrit :
> >      >
> >      >     On 3/6/2024 12:05, Sébastien Chaumat wrote:
> >      >      >
> >      >      >
> >      >      > Le mer. 6 mars 2024 à 18:33, Mario Limonciello
> >      >      > <mario.limonciello@amd.com
> >      >      >     Also; I'd be really interested to hear what happens with
> >      >     s2idle with
> >      >      >     Xen
> >      >      >     now (if it works).
> >      >      >
> >      >      >
> >      >      > suspend to RAM now works :)
> >      >
> >      >     Do you see /sys/power/suspend_stats/last_hw_sleep increasing
> >     with your
> >      >     suspend cycle?
> >      >
> >      >
> >      > No,  it does not increase (0).
> >      >
> > 
> >     OK, then in that case I suggest you run
> >     https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py <https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py>
> >     in the hypervisor to find out what's wrong.
> > 
> > 
> > It fails with xen (not bare metal) during the prerequisite tests :
> > 
> 
> The script might need some modifications for tests that don't make sense in
> the context of Xen.
> 
> > ✅ GPIO driver `pinctrl_amd` available
> > Traceback (most recent call last):
> >    File "/home/sch/Downloads/amd_s2idle.py", line 2447, in <module>
> >      test = app.prerequisites()
> >             ^^^^^^^^^^^^^^^^^^^
> >    File "/home/sch/Downloads/amd_s2idle.py", line 1938, in prerequisites
> >      if not check():
> >             ^^^^^^^
> >    File "/home/sch/Downloads/amd_s2idle.py", line 826, in check_msr
> >      val = read_msr(reg, 0)
> >            ^^^^^^^^^^^^^^^^
> >    File "/home/sch/Downloads/amd_s2idle.py", line 813, in read_msr
> >      val = struct.unpack("Q", os.read(f, 8))[0]
> >                               ^^^^^^^^^^^^^
> > OSError: [Errno 5] Input/output error
> > 
> > Last line in the log is :
> > 2024-03-06 21:29:33,146 DEBUG: Lockdown: [none] integrity confidentiality
> > 
> 
> Do you have userspace MSR support compiled in?  If not; that could explain
> that problem.  But it's very unlikely you changed the MSRs.
> For the purpose of finding where the suspend problem is, I'd comment out
> that specific check for now.

The s2idle isn't supported in Xen yet. Only S3 is. In fact, I have some
work-in-progress patches for that, I may try testing them on this
system.

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 3/6/2024 15:31, Marek Marczykowski-Górecki wrote:
> On Wed, Mar 06, 2024 at 02:37:20PM -0600, Mario Limonciello wrote:
>> On 3/6/2024 14:34, Sébastien Chaumat wrote:
>>>
>>>
>>> Le mer. 6 mars 2024 à 19:51, Mario Limonciello
>>> <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>> a écrit :
>>>
>>>      On 3/6/2024 12:49, Sébastien Chaumat wrote:
>>>       >
>>>       >
>>>       > Le mer. 6 mars 2024 à 19:08, Mario Limonciello
>>>       > <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>
>>>      <mailto:mario.limonciello@amd.com
>>>      <mailto:mario.limonciello@amd.com>>> a écrit :
>>>       >
>>>       >     On 3/6/2024 12:05, Sébastien Chaumat wrote:
>>>       >      >
>>>       >      >
>>>       >      > Le mer. 6 mars 2024 à 18:33, Mario Limonciello
>>>       >      > <mario.limonciello@amd.com
>>>       >      >     Also; I'd be really interested to hear what happens with
>>>       >     s2idle with
>>>       >      >     Xen
>>>       >      >     now (if it works).
>>>       >      >
>>>       >      >
>>>       >      > suspend to RAM now works :)
>>>       >
>>>       >     Do you see /sys/power/suspend_stats/last_hw_sleep increasing
>>>      with your
>>>       >     suspend cycle?
>>>       >
>>>       >
>>>       > No,  it does not increase (0).
>>>       >
>>>
>>>      OK, then in that case I suggest you run
>>>      https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py <https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py>
>>>      in the hypervisor to find out what's wrong.
>>>
>>>
>>> It fails with xen (not bare metal) during the prerequisite tests :
>>>
>>
>> The script might need some modifications for tests that don't make sense in
>> the context of Xen.
>>
>>> ✅ GPIO driver `pinctrl_amd` available
>>> Traceback (most recent call last):
>>>     File "/home/sch/Downloads/amd_s2idle.py", line 2447, in <module>
>>>       test = app.prerequisites()
>>>              ^^^^^^^^^^^^^^^^^^^
>>>     File "/home/sch/Downloads/amd_s2idle.py", line 1938, in prerequisites
>>>       if not check():
>>>              ^^^^^^^
>>>     File "/home/sch/Downloads/amd_s2idle.py", line 826, in check_msr
>>>       val = read_msr(reg, 0)
>>>             ^^^^^^^^^^^^^^^^
>>>     File "/home/sch/Downloads/amd_s2idle.py", line 813, in read_msr
>>>       val = struct.unpack("Q", os.read(f, 8))[0]
>>>                                ^^^^^^^^^^^^^
>>> OSError: [Errno 5] Input/output error
>>>
>>> Last line in the log is :
>>> 2024-03-06 21:29:33,146 DEBUG: Lockdown: [none] integrity confidentiality
>>>
>>
>> Do you have userspace MSR support compiled in?  If not; that could explain
>> that problem.  But it's very unlikely you changed the MSRs.
>> For the purpose of finding where the suspend problem is, I'd comment out
>> that specific check for now.
> 
> The s2idle isn't supported in Xen yet. Only S3 is. In fact, I have some
> work-in-progress patches for that, I may try testing them on this
> system.
> 

OK; the "most important parts" I want to point out that are on bare 
metal and might not be obvious:
  * Infra from drivers/acpi/x86/s2idle.c
  * amd-pmc driver
  * USB4 driver (thunderbolt.ko)
  * NVME needs to use "simple suspend"

FYI - I'm going to be MIA for a while on personal leave starting this 
weekend, please keep me on CC on your progress and if you need help when 
I get back from my leave I'll comment on it.

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Jan Beulich]

On 06.03.2024 18:28, Sébastien Chaumat wrote:
> Reasoning backward  (using a  kernel without the pinctrl_amd driver to
>> ensure xen only is at stake) :
>>  checking the diff in IOAPIC  between bare metal and xen  (IRQ7 is on
>> pin07 on APIC )
>>
>> using kernel argument : apic=debug
>>
>> bare metal :
>> [    0.715330] fedora kernel: ... APIC VERSION: 81050010
>> ...
>> [    0.715433] fedora kernel:  pin07, disabled, edge , high, V(00),
>> IRR(0), S(0), physical, D(0000), M(0)
>>
>> xen :
>> [    2.249582] fedora kernel: ... APIC VERSION: 00000014
>> ...
>> [    2.249730] fedora kernel:  pin07, disabled, level, low , V(60),
>> IRR(0), S(0), physical, D(0000), M(0)
>>
>> So the APIC table is not the same.
>>
>> As strange as it looks the  (IOAPIC 0) pin07 is correctly described by the
>> APIC in xen but yet differently than in baremetal.
>> But the APIC message comes long after the
>> [    1.833145] fedora kernel: xen: registering gsi 7 triggering 0 polarity
>> 1
>>
>> so I wonder if the APIC pin07 info had any influence.
>>
>> Finally found the fix : adding ioapic_ack=new to xen boot parameters.
> Not only the trackpad is now working but also the ACPI Embedded Controller
> which is completely disabled.

Hmm, interesting. From someone else's laptop many years ago I had actually
an indication in the opposite direction: That didn't work because of our
defaulting to new (no directed EOI in sight yet back at that time). I
wonder if overriding the ack method isn't actually just papering over the
underlying actual issue here, whatever that is. IOW with the edge vs level
mismatch addressed I'd hope the override could then be dropped again.

Jan

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Sébastien Chaumat]

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

Le jeu. 7 mars 2024, 09:39, Jan Beulich <jbeulich@suse.com> a écrit :

> On 06.03.2024 18:28, Sébastien Chaumat wrote:
> > Reasoning backward  (using a  kernel without the pinctrl_amd driver to
> >> ensure xen only is at stake) :
> >>  checking the diff in IOAPIC  between bare metal and xen  (IRQ7 is on
> >> pin07 on APIC )
> >>
> >> using kernel argument : apic=debug
> >>
> >> bare metal :
> >> [    0.715330] fedora kernel: ... APIC VERSION: 81050010
> >> ...
> >> [    0.715433] fedora kernel:  pin07, disabled, edge , high, V(00),
> >> IRR(0), S(0), physical, D(0000), M(0)
> >>
> >> xen :
> >> [    2.249582] fedora kernel: ... APIC VERSION: 00000014
> >> ...
> >> [    2.249730] fedora kernel:  pin07, disabled, level, low , V(60),
> >> IRR(0), S(0), physical, D(0000), M(0)
> >>
> >> So the APIC table is not the same.
> >>
> >> As strange as it looks the  (IOAPIC 0) pin07 is correctly described by
> the
> >> APIC in xen but yet differently than in baremetal.
> >> But the APIC message comes long after the
> >> [    1.833145] fedora kernel: xen: registering gsi 7 triggering 0
> polarity
> >> 1
> >>
> >> so I wonder if the APIC pin07 info had any influence.
> >>
> >> Finally found the fix : adding ioapic_ack=new to xen boot parameters.
> > Not only the trackpad is now working but also the ACPI Embedded
> Controller
> > which is completely disabled.
>
> Hmm, interesting. From someone else's laptop many years ago I had actually
> an indication in the opposite direction: That didn't work because of our
> defaulting to new (no directed EOI in sight yet back at that time). I
> wonder if overriding the ack method isn't actually just papering over the
> underlying actual issue here, whatever that is. IOW with the edge vs level
> mismatch addressed I'd hope the override could then be dropped again.
>

I suppose you refert to  :
https://xen-devel.narkive.com/1Lbaex65/irq-issues-with-directed-eoi-and-io-apic-ack-methods


 - I did override the IRQ configuration all allong my debugs (the handler
was correctly set to level, yet not all flags were identical between dom0
and bare metal). In the end, with the ioapic_ack=new, I could even leave
the wrong edge binding for IRQ7.

 - besides the touchpad, the ACPI EC was also non functional without
forcing ioapic_ack. And in bare metal the EC does a lot of work of during
early kernel setup.

 Sébastien

[-- Attachment #2: Type: text/html, Size: 3276 bytes --]