* [REGRESSION] Brightness control does not work after waking up from suspend
@ 2024-12-25 10:05 Fernando Ramos
2024-12-27 14:34 ` Fernando Ramos
0 siblings, 1 reply; 3+ messages in thread
From: Fernando Ramos @ 2024-12-25 10:05 UTC (permalink / raw)
To: stable; +Cc: alexander.deucher
Commit 73dae652dcac776296890da215ee7dec357a1032 (included in 6.13-rc2) was
backported to 6.12.5 as 99a02eab82515343d536796aa917dee50aec1551.
This causes a problem where brightness control no longer works after waking up
from suspend.
This is the output of "journalctl -f" when the issue is triggered:
> ...
> Dec 25 01:37:00 x395 kernel: usb 4-1: reset full-speed USB device number 2 using xhci_hcd
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
> Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
> Dec 25 01:37:00 x395 kernel: irq 7: nobody cared (try booting with the "irqpoll" option)
> Dec 25 01:37:00 x395 kernel: CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.7-rc1-gc157915828d8 #7 14cb019df871d9dae96d82113f6abf187f110b68
> Dec 25 01:37:00 x395 kernel: Hardware name: LENOVO 20NLCTO1WW/20NLCTO1WW, BIOS R13ET50W(1.24 ) 06/11/2021
> Dec 25 01:37:00 x395 kernel: Call Trace:
> Dec 25 01:37:00 x395 kernel: <IRQ>
> Dec 25 01:37:00 x395 kernel: dump_stack_lvl+0x5d/0x80
> Dec 25 01:37:00 x395 kernel: __report_bad_irq+0x35/0xa7
> Dec 25 01:37:00 x395 kernel: note_interrupt.cold+0xa/0x62
> Dec 25 01:37:00 x395 kernel: handle_irq_event+0x6f/0x80
> Dec 25 01:37:00 x395 kernel: handle_fasteoi_irq+0x78/0x200
> Dec 25 01:37:00 x395 kernel: __common_interrupt+0x3e/0x90
> Dec 25 01:37:00 x395 kernel: common_interrupt+0x42/0xa0
> Dec 25 01:37:00 x395 kernel: asm_common_interrupt+0x26/0x40
> Dec 25 01:37:00 x395 kernel: RIP: 0010:tmigr_handle_remote+0x87/0x470
> Dec 25 01:37:00 x395 kernel: Code: 24 04 00 0f 84 ac 00 00 00 48 b9 ff ff ff ff ff ff ff 7f 41 0f b6 54 24 10 48 89 4c 24 38 88 54 24 48 49 8b 44 24 08 8b 40 50 <0f> b6 c4 38 c2 74 0e 3c ff 74 0a 49 8b 44 24 18 48 39 c8 74 76 48
> Dec 25 01:37:00 x395 kernel: RSP: 0018:ffffafe000003ea8 EFLAGS: 00000202
> Dec 25 01:37:00 x395 kernel: RAX: 000000003de00141 RBX: 0000000000000002 RCX: 7fffffffffffffff
> Dec 25 01:37:00 x395 kernel: RDX: 0000000000000001 RSI: ffffafe000003ed8 RDI: ffffafe000003f10
> Dec 25 01:37:00 x395 kernel: RBP: 0000000000000101 R08: f1c92dc141c95fb9 R09: 263db225b099c5f2
> Dec 25 01:37:00 x395 kernel: R10: f1c92dc141c95fb9 R11: 263db225b099c5f2 R12: ffff989030a26300
> Dec 25 01:37:00 x395 kernel: R13: 0000000000000001 R14: 0000000000000282 R15: 0000000000000001
> Dec 25 01:37:00 x395 kernel: ? srso_return_thunk+0x5/0x5f
> Dec 25 01:37:00 x395 kernel: ? __run_timers+0x1fc/0x280
> Dec 25 01:37:00 x395 kernel: handle_softirqs+0xe4/0x2a0
> Dec 25 01:37:00 x395 kernel: __irq_exit_rcu+0x97/0xb0
> Dec 25 01:37:00 x395 kernel: sysvec_apic_timer_interrupt+0x71/0x90
> Dec 25 01:37:00 x395 kernel: </IRQ>
> Dec 25 01:37:00 x395 kernel: <TASK>
> Dec 25 01:37:00 x395 kernel: asm_sysvec_apic_timer_interrupt+0x1a/0x20
> Dec 25 01:37:00 x395 kernel: RIP: 0010:tick_nohz_idle_enter+0x59/0x70
> Dec 25 01:37:00 x395 kernel: Code: 02 00 01 83 45 7c 01 e8 05 c9 fe ff 48 89 85 80 00 00 00 48 83 8b 00 62 02 00 04 83 45 7c 01 e8 3d 93 f8 ff fb 0f 1f 44 00 00 <5b> 5d e9 10 d1 c8 00 0f 0b eb c6 66 66 2e 0f 1f 84 00 00 00 00 00
> Dec 25 01:37:00 x395 kernel: RSP: 0018:ffffffffa1c03e68 EFLAGS: 00000282
> Dec 25 01:37:00 x395 kernel: RAX: 0000000874467ae1 RBX: ffff989030a00000 RCX: 0000000874467ae1
> Dec 25 01:37:00 x395 kernel: RDX: 0000000874467ae1 RSI: 0000000000001d53 RDI: 0000000874467ae1
> Dec 25 01:37:00 x395 kernel: RBP: ffff989030a26200 R08: 0000000000000002 R09: 0000000000000000
> Dec 25 01:37:00 x395 kernel: R10: 0000000000000001 R11: 0000000000000000 R12: ffff98903efc9ff4
> Dec 25 01:37:00 x395 kernel: R13: 0000000000000000 R14: ffffffffa1c10038 R15: 00000000aafaf000
> Dec 25 01:37:00 x395 kernel: ? tick_nohz_idle_enter+0x53/0x70
> Dec 25 01:37:00 x395 kernel: do_idle+0x3f/0x210
> Dec 25 01:37:00 x395 kernel: cpu_startup_entry+0x29/0x30
> Dec 25 01:37:00 x395 kernel: rest_init+0xcc/0xd0
> Dec 25 01:37:00 x395 kernel: start_kernel+0x9be/0x9c0
> Dec 25 01:37:00 x395 kernel: x86_64_start_reservations+0x24/0x30
> Dec 25 01:37:00 x395 kernel: x86_64_start_kernel+0x95/0xa0
> Dec 25 01:37:00 x395 kernel: common_startup_64+0x13e/0x141
> Dec 25 01:37:00 x395 kernel: </TASK>
> Dec 25 01:37:00 x395 kernel: handlers:
> Dec 25 01:37:00 x395 kernel: [<00000000d69cbeca>] amd_gpio_irq_handler
> Dec 25 01:37:00 x395 kernel: Disabling IRQ #7
> Dec 25 01:37:00 x395 kernel: usb 4-2: reset high-speed USB device number 3 using xhci_hcd
> Dec 25 01:37:01 x395 kernel: usb 4-2.1: reset high-speed USB device number 4 using xhci_hcd
> Dec 25 01:37:01 x395 kernel: OOM killer enabled.
> Dec 25 01:37:01 x395 kernel: Restarting tasks ...
> Dec 25 01:37:01 x395 kernel: usb 4-2.2: USB disconnect, device number 5
> Dec 25 01:37:01 x395 kernel: done.
> ...
The problem only happens in the stable branch (v6.12.y) and not in the main
branch. More specifically:
Version Problem present
=================================================================
v6.12.5 Yes !!
v6.12.5 + revert 99a02eab No
v6.12.7-rc1 (c157915828d) Yes !!
v6.12.7-rc1 (c157915828d) + revert 99a02eab No
v6.13-rc4 No
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [REGRESSION] Brightness control does not work after waking up from suspend
2024-12-25 10:05 [REGRESSION] Brightness control does not work after waking up from suspend Fernando Ramos
@ 2024-12-27 14:34 ` Fernando Ramos
2025-01-02 18:10 ` Deucher, Alexander
0 siblings, 1 reply; 3+ messages in thread
From: Fernando Ramos @ 2024-12-27 14:34 UTC (permalink / raw)
To: stable, regressions; +Cc: alexander.deucher
I've been told to forward this message to regressions@lists.linux.dev in
addition to stable@vger.kernel.org.
On 24/12/25 11:06AM, Fernando Ramos wrote:
> Commit 73dae652dcac776296890da215ee7dec357a1032 (included in 6.13-rc2) was
> backported to 6.12.5 as 99a02eab82515343d536796aa917dee50aec1551.
>
> This causes a problem where brightness control no longer works after waking up
> from suspend.
>
> This is the output of "journalctl -f" when the issue is triggered:
>
> > ...
> > Dec 25 01:37:00 x395 kernel: usb 4-1: reset full-speed USB device number 2 using xhci_hcd
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
> > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
> > Dec 25 01:37:00 x395 kernel: irq 7: nobody cared (try booting with the "irqpoll" option)
> > Dec 25 01:37:00 x395 kernel: CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.7-rc1-gc157915828d8 #7 14cb019df871d9dae96d82113f6abf187f110b68
> > Dec 25 01:37:00 x395 kernel: Hardware name: LENOVO 20NLCTO1WW/20NLCTO1WW, BIOS R13ET50W(1.24 ) 06/11/2021
> > Dec 25 01:37:00 x395 kernel: Call Trace:
> > Dec 25 01:37:00 x395 kernel: <IRQ>
> > Dec 25 01:37:00 x395 kernel: dump_stack_lvl+0x5d/0x80
> > Dec 25 01:37:00 x395 kernel: __report_bad_irq+0x35/0xa7
> > Dec 25 01:37:00 x395 kernel: note_interrupt.cold+0xa/0x62
> > Dec 25 01:37:00 x395 kernel: handle_irq_event+0x6f/0x80
> > Dec 25 01:37:00 x395 kernel: handle_fasteoi_irq+0x78/0x200
> > Dec 25 01:37:00 x395 kernel: __common_interrupt+0x3e/0x90
> > Dec 25 01:37:00 x395 kernel: common_interrupt+0x42/0xa0
> > Dec 25 01:37:00 x395 kernel: asm_common_interrupt+0x26/0x40
> > Dec 25 01:37:00 x395 kernel: RIP: 0010:tmigr_handle_remote+0x87/0x470
> > Dec 25 01:37:00 x395 kernel: Code: 24 04 00 0f 84 ac 00 00 00 48 b9 ff ff ff ff ff ff ff 7f 41 0f b6 54 24 10 48 89 4c 24 38 88 54 24 48 49 8b 44 24 08 8b 40 50 <0f> b6 c4 38 c2 74 0e 3c ff 74 0a 49 8b 44 24 18 48 39 c8 74 76 48
> > Dec 25 01:37:00 x395 kernel: RSP: 0018:ffffafe000003ea8 EFLAGS: 00000202
> > Dec 25 01:37:00 x395 kernel: RAX: 000000003de00141 RBX: 0000000000000002 RCX: 7fffffffffffffff
> > Dec 25 01:37:00 x395 kernel: RDX: 0000000000000001 RSI: ffffafe000003ed8 RDI: ffffafe000003f10
> > Dec 25 01:37:00 x395 kernel: RBP: 0000000000000101 R08: f1c92dc141c95fb9 R09: 263db225b099c5f2
> > Dec 25 01:37:00 x395 kernel: R10: f1c92dc141c95fb9 R11: 263db225b099c5f2 R12: ffff989030a26300
> > Dec 25 01:37:00 x395 kernel: R13: 0000000000000001 R14: 0000000000000282 R15: 0000000000000001
> > Dec 25 01:37:00 x395 kernel: ? srso_return_thunk+0x5/0x5f
> > Dec 25 01:37:00 x395 kernel: ? __run_timers+0x1fc/0x280
> > Dec 25 01:37:00 x395 kernel: handle_softirqs+0xe4/0x2a0
> > Dec 25 01:37:00 x395 kernel: __irq_exit_rcu+0x97/0xb0
> > Dec 25 01:37:00 x395 kernel: sysvec_apic_timer_interrupt+0x71/0x90
> > Dec 25 01:37:00 x395 kernel: </IRQ>
> > Dec 25 01:37:00 x395 kernel: <TASK>
> > Dec 25 01:37:00 x395 kernel: asm_sysvec_apic_timer_interrupt+0x1a/0x20
> > Dec 25 01:37:00 x395 kernel: RIP: 0010:tick_nohz_idle_enter+0x59/0x70
> > Dec 25 01:37:00 x395 kernel: Code: 02 00 01 83 45 7c 01 e8 05 c9 fe ff 48 89 85 80 00 00 00 48 83 8b 00 62 02 00 04 83 45 7c 01 e8 3d 93 f8 ff fb 0f 1f 44 00 00 <5b> 5d e9 10 d1 c8 00 0f 0b eb c6 66 66 2e 0f 1f 84 00 00 00 00 00
> > Dec 25 01:37:00 x395 kernel: RSP: 0018:ffffffffa1c03e68 EFLAGS: 00000282
> > Dec 25 01:37:00 x395 kernel: RAX: 0000000874467ae1 RBX: ffff989030a00000 RCX: 0000000874467ae1
> > Dec 25 01:37:00 x395 kernel: RDX: 0000000874467ae1 RSI: 0000000000001d53 RDI: 0000000874467ae1
> > Dec 25 01:37:00 x395 kernel: RBP: ffff989030a26200 R08: 0000000000000002 R09: 0000000000000000
> > Dec 25 01:37:00 x395 kernel: R10: 0000000000000001 R11: 0000000000000000 R12: ffff98903efc9ff4
> > Dec 25 01:37:00 x395 kernel: R13: 0000000000000000 R14: ffffffffa1c10038 R15: 00000000aafaf000
> > Dec 25 01:37:00 x395 kernel: ? tick_nohz_idle_enter+0x53/0x70
> > Dec 25 01:37:00 x395 kernel: do_idle+0x3f/0x210
> > Dec 25 01:37:00 x395 kernel: cpu_startup_entry+0x29/0x30
> > Dec 25 01:37:00 x395 kernel: rest_init+0xcc/0xd0
> > Dec 25 01:37:00 x395 kernel: start_kernel+0x9be/0x9c0
> > Dec 25 01:37:00 x395 kernel: x86_64_start_reservations+0x24/0x30
> > Dec 25 01:37:00 x395 kernel: x86_64_start_kernel+0x95/0xa0
> > Dec 25 01:37:00 x395 kernel: common_startup_64+0x13e/0x141
> > Dec 25 01:37:00 x395 kernel: </TASK>
> > Dec 25 01:37:00 x395 kernel: handlers:
> > Dec 25 01:37:00 x395 kernel: [<00000000d69cbeca>] amd_gpio_irq_handler
> > Dec 25 01:37:00 x395 kernel: Disabling IRQ #7
> > Dec 25 01:37:00 x395 kernel: usb 4-2: reset high-speed USB device number 3 using xhci_hcd
> > Dec 25 01:37:01 x395 kernel: usb 4-2.1: reset high-speed USB device number 4 using xhci_hcd
> > Dec 25 01:37:01 x395 kernel: OOM killer enabled.
> > Dec 25 01:37:01 x395 kernel: Restarting tasks ...
> > Dec 25 01:37:01 x395 kernel: usb 4-2.2: USB disconnect, device number 5
> > Dec 25 01:37:01 x395 kernel: done.
> > ...
>
> The problem only happens in the stable branch (v6.12.y) and not in the main
> branch. More specifically:
>
> Version Problem present
> =================================================================
> v6.12.5 Yes !!
> v6.12.5 + revert 99a02eab No
> v6.12.7-rc1 (c157915828d) Yes !!
> v6.12.7-rc1 (c157915828d) + revert 99a02eab No
> v6.13-rc4 No
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: [REGRESSION] Brightness control does not work after waking up from suspend
2024-12-27 14:34 ` Fernando Ramos
@ 2025-01-02 18:10 ` Deucher, Alexander
0 siblings, 0 replies; 3+ messages in thread
From: Deucher, Alexander @ 2025-01-02 18:10 UTC (permalink / raw)
To: Fernando Ramos, stable@vger.kernel.org,
regressions@lists.linux.dev
[Public]
> -----Original Message-----
> From: Fernando Ramos <greenfoo@u92.eu>
> Sent: Friday, December 27, 2024 9:34 AM
> To: stable@vger.kernel.org; regressions@lists.linux.dev
> Cc: Deucher, Alexander <Alexander.Deucher@amd.com>
> Subject: Re: [REGRESSION] Brightness control does not work after waking up
> from suspend
>
> I've been told to forward this message to regressions@lists.linux.dev in addition to
> stable@vger.kernel.org.
>
Fixed in:
https://lore.kernel.org/all/20241227073700.3102801-1-alexander.deucher@amd.com/
once it lands in stable.
Alex
> On 24/12/25 11:06AM, Fernando Ramos wrote:
> > Commit 73dae652dcac776296890da215ee7dec357a1032 (included in 6.13-rc2)
> > was backported to 6.12.5 as 99a02eab82515343d536796aa917dee50aec1551.
> >
> > This causes a problem where brightness control no longer works after
> > waking up from suspend.
> >
> > This is the output of "journalctl -f" when the issue is triggered:
> >
> > > ...
> > > Dec 25 01:37:00 x395 kernel: usb 4-1: reset full-speed USB device number 2
> using xhci_hcd
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring gfx uses
> VM inv eng 0 on hub 0
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0
> uses VM inv eng 1 on hub 0
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0
> uses VM inv eng 4 on hub 0
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0
> uses VM inv eng 5 on hub 0
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0
> uses VM inv eng 6 on hub 0
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1
> uses VM inv eng 7 on hub 0
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1
> uses VM inv eng 8 on hub 0
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1
> uses VM inv eng 9 on hub 0
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1
> uses VM inv eng 10 on hub 0
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring kiq_0.2.1.0
> uses VM inv eng 11 on hub 0
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring sdma0
> uses VM inv eng 0 on hub 8
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_dec
> uses VM inv eng 1 on hub 8
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_enc0
> uses VM inv eng 4 on hub 8
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_enc1
> uses VM inv eng 5 on hub 8
> > > Dec 25 01:37:00 x395 kernel: amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec
> uses VM inv eng 6 on hub 8
> > > Dec 25 01:37:00 x395 kernel: irq 7: nobody cared (try booting with the "irqpoll"
> option)
> > > Dec 25 01:37:00 x395 kernel: CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not
> tainted 6.12.7-rc1-gc157915828d8 #7
> 14cb019df871d9dae96d82113f6abf187f110b68
> > > Dec 25 01:37:00 x395 kernel: Hardware name: LENOVO
> 20NLCTO1WW/20NLCTO1WW, BIOS R13ET50W(1.24 ) 06/11/2021
> > > Dec 25 01:37:00 x395 kernel: Call Trace:
> > > Dec 25 01:37:00 x395 kernel: <IRQ>
> > > Dec 25 01:37:00 x395 kernel: dump_stack_lvl+0x5d/0x80
> > > Dec 25 01:37:00 x395 kernel: __report_bad_irq+0x35/0xa7
> > > Dec 25 01:37:00 x395 kernel: note_interrupt.cold+0xa/0x62
> > > Dec 25 01:37:00 x395 kernel: handle_irq_event+0x6f/0x80
> > > Dec 25 01:37:00 x395 kernel: handle_fasteoi_irq+0x78/0x200
> > > Dec 25 01:37:00 x395 kernel: __common_interrupt+0x3e/0x90
> > > Dec 25 01:37:00 x395 kernel: common_interrupt+0x42/0xa0
> > > Dec 25 01:37:00 x395 kernel: asm_common_interrupt+0x26/0x40
> > > Dec 25 01:37:00 x395 kernel: RIP: 0010:tmigr_handle_remote+0x87/0x470
> > > Dec 25 01:37:00 x395 kernel: Code: 24 04 00 0f 84 ac 00 00 00 48 b9 ff ff ff ff
> ff ff ff 7f 41 0f b6 54 24 10 48 89 4c 24 38 88 54 24 48 49 8b 44 24 08 8b 40 50 <0f>
> b6 c4 38 c2 74 0e 3c ff 74 0a 49 8b 44 24 18 48 39 c8 74 76 48
> > > Dec 25 01:37:00 x395 kernel: RSP: 0018:ffffafe000003ea8 EFLAGS:
> 00000202
> > > Dec 25 01:37:00 x395 kernel: RAX: 000000003de00141 RBX:
> 0000000000000002 RCX: 7fffffffffffffff
> > > Dec 25 01:37:00 x395 kernel: RDX: 0000000000000001 RSI: ffffafe000003ed8
> RDI: ffffafe000003f10
> > > Dec 25 01:37:00 x395 kernel: RBP: 0000000000000101 R08:
> f1c92dc141c95fb9 R09: 263db225b099c5f2
> > > Dec 25 01:37:00 x395 kernel: R10: f1c92dc141c95fb9 R11:
> 263db225b099c5f2 R12: ffff989030a26300
> > > Dec 25 01:37:00 x395 kernel: R13: 0000000000000001 R14:
> 0000000000000282 R15: 0000000000000001
> > > Dec 25 01:37:00 x395 kernel: ? srso_return_thunk+0x5/0x5f
> > > Dec 25 01:37:00 x395 kernel: ? __run_timers+0x1fc/0x280
> > > Dec 25 01:37:00 x395 kernel: handle_softirqs+0xe4/0x2a0
> > > Dec 25 01:37:00 x395 kernel: __irq_exit_rcu+0x97/0xb0
> > > Dec 25 01:37:00 x395 kernel: sysvec_apic_timer_interrupt+0x71/0x90
> > > Dec 25 01:37:00 x395 kernel: </IRQ>
> > > Dec 25 01:37:00 x395 kernel: <TASK>
> > > Dec 25 01:37:00 x395 kernel: asm_sysvec_apic_timer_interrupt+0x1a/0x20
> > > Dec 25 01:37:00 x395 kernel: RIP: 0010:tick_nohz_idle_enter+0x59/0x70
> > > Dec 25 01:37:00 x395 kernel: Code: 02 00 01 83 45 7c 01 e8 05 c9 fe ff 48 89
> 85 80 00 00 00 48 83 8b 00 62 02 00 04 83 45 7c 01 e8 3d 93 f8 ff fb 0f 1f 44 00 00
> <5b> 5d e9 10 d1 c8 00 0f 0b eb c6 66 66 2e 0f 1f 84 00 00 00 00 00
> > > Dec 25 01:37:00 x395 kernel: RSP: 0018:ffffffffa1c03e68 EFLAGS: 00000282
> > > Dec 25 01:37:00 x395 kernel: RAX: 0000000874467ae1 RBX:
> ffff989030a00000 RCX: 0000000874467ae1
> > > Dec 25 01:37:00 x395 kernel: RDX: 0000000874467ae1 RSI:
> 0000000000001d53 RDI: 0000000874467ae1
> > > Dec 25 01:37:00 x395 kernel: RBP: ffff989030a26200 R08:
> 0000000000000002 R09: 0000000000000000
> > > Dec 25 01:37:00 x395 kernel: R10: 0000000000000001 R11:
> 0000000000000000 R12: ffff98903efc9ff4
> > > Dec 25 01:37:00 x395 kernel: R13: 0000000000000000 R14: ffffffffa1c10038
> R15: 00000000aafaf000
> > > Dec 25 01:37:00 x395 kernel: ? tick_nohz_idle_enter+0x53/0x70
> > > Dec 25 01:37:00 x395 kernel: do_idle+0x3f/0x210
> > > Dec 25 01:37:00 x395 kernel: cpu_startup_entry+0x29/0x30
> > > Dec 25 01:37:00 x395 kernel: rest_init+0xcc/0xd0
> > > Dec 25 01:37:00 x395 kernel: start_kernel+0x9be/0x9c0
> > > Dec 25 01:37:00 x395 kernel: x86_64_start_reservations+0x24/0x30
> > > Dec 25 01:37:00 x395 kernel: x86_64_start_kernel+0x95/0xa0
> > > Dec 25 01:37:00 x395 kernel: common_startup_64+0x13e/0x141
> > > Dec 25 01:37:00 x395 kernel: </TASK>
> > > Dec 25 01:37:00 x395 kernel: handlers:
> > > Dec 25 01:37:00 x395 kernel: [<00000000d69cbeca>] amd_gpio_irq_handler
> > > Dec 25 01:37:00 x395 kernel: Disabling IRQ #7
> > > Dec 25 01:37:00 x395 kernel: usb 4-2: reset high-speed USB device number 3
> using xhci_hcd
> > > Dec 25 01:37:01 x395 kernel: usb 4-2.1: reset high-speed USB device number
> 4 using xhci_hcd
> > > Dec 25 01:37:01 x395 kernel: OOM killer enabled.
> > > Dec 25 01:37:01 x395 kernel: Restarting tasks ...
> > > Dec 25 01:37:01 x395 kernel: usb 4-2.2: USB disconnect, device number 5
> > > Dec 25 01:37:01 x395 kernel: done.
> > > ...
> >
> > The problem only happens in the stable branch (v6.12.y) and not in the
> > main branch. More specifically:
> >
> > Version Problem present
> >
> ============================================================
> =====
> > v6.12.5 Yes !!
> > v6.12.5 + revert 99a02eab No
> > v6.12.7-rc1 (c157915828d) Yes !!
> > v6.12.7-rc1 (c157915828d) + revert 99a02eab No
> > v6.13-rc4 No
> >
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-01-02 18:10 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-12-25 10:05 [REGRESSION] Brightness control does not work after waking up from suspend Fernando Ramos
2024-12-27 14:34 ` Fernando Ramos
2025-01-02 18:10 ` Deucher, Alexander
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox