[Bug 2147494] Re: Fix speaker mute led on a HP EliteBoard G1a platform

This bug is awaiting verification that the linux-oem-6.17/6.17.0-1019.19 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-oem-6.17' to 'verification-done- noble-linux-oem-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux-oem-6.17' to 'verification-failed- noble-linux-oem-6.17'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-oem-6.17-v2 verification-needed-noble-linux-oem-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147494 Title: Fix speaker mute led on a HP EliteBoard G1a platform Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: Fix Committed Status in linux-oem-6.17 source package in Resolute: New Bug description: SRU Justification: [Impact] New HP platform with Realtek ALC3315+TAS2783 audio solution fail to toggle the speaker mute led accordingly while the speaker mute function work w/o problem. This SRU includes fix for the particular SSID only (NexusX) [Fix] Backport the upstream fix: d3be95efc6a1 ("ALSA: hda/realtek - Fixed Speaker Mute LED for HP EliteBoard G1a platform") [Test Case] 1. Boot up the machine of new HP platforms NexusX 2. Press Fn+F1 for speaker mute function 3. Click led lights up/down in according with the speaker mute functions. [Where problems could occur] It fixes the quirk for particular SSIDs of the audio solution. No regression expected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2147494/+subscriptions

[Bug 2148662] Re: firewire fw_device_workfn [firewire_core]

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148662 Title: firewire fw_device_workfn [firewire_core] Status in linux package in Ubuntu: New Bug description: [ 247.143126] INFO: task kworker/0:0:9 blocked for more than 122 seconds. [ 247.143145] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 247.143149] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 247.143153] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 247.143163] Workqueue: firewire fw_device_workfn [firewire_core] [ 247.143210] Call Trace: [ 247.143215] <TASK> [ 247.143220] __schedule+0x2ed/0x7c0 [ 247.143233] schedule+0x27/0x90 [ 247.143239] schedule_timeout+0xcf/0x110 [ 247.143247] wait_for_completion+0x82/0x160 [ 247.143253] fw_run_transaction+0xed/0x130 [firewire_core] [ 247.143288] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 247.143322] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 247.143355] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 247.143388] read_rom+0x64/0xb0 [firewire_core] [ 247.143421] read_config_rom+0x9f/0x440 [firewire_core] [ 247.143454] ? psi_task_switch+0x17e/0x390 [ 247.143462] fw_device_init+0x48/0x470 [firewire_core] [ 247.143495] fw_device_workfn+0x12/0x20 [firewire_core] [ 247.143527] process_one_work+0x18e/0x370 [ 247.143535] worker_thread+0x317/0x450 [ 247.143541] ? __pfx_worker_thread+0x10/0x10 [ 247.143547] kthread+0x10b/0x220 [ 247.143552] ? __pfx_kthread+0x10/0x10 [ 247.143557] ret_from_fork+0x134/0x150 [ 247.143562] ? __pfx_kthread+0x10/0x10 [ 247.143567] ret_from_fork_asm+0x1a/0x30 [ 247.143575] </TASK> [ 370.022713] INFO: task kworker/0:0:9 blocked for more than 245 seconds. [ 370.022733] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 370.022738] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 370.022741] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 370.022751] Workqueue: firewire fw_device_workfn [firewire_core] [ 370.022798] Call Trace: [ 370.022802] <TASK> [ 370.022807] __schedule+0x2ed/0x7c0 [ 370.022819] schedule+0x27/0x90 [ 370.022826] schedule_timeout+0xcf/0x110 [ 370.022833] wait_for_completion+0x82/0x160 [ 370.022839] fw_run_transaction+0xed/0x130 [firewire_core] [ 370.022874] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 370.022908] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 370.022941] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 370.022975] read_rom+0x64/0xb0 [firewire_core] [ 370.023008] read_config_rom+0x9f/0x440 [firewire_core] [ 370.023041] ? psi_task_switch+0x17e/0x390 [ 370.023049] fw_device_init+0x48/0x470 [firewire_core] [ 370.023082] fw_device_workfn+0x12/0x20 [firewire_core] [ 370.023114] process_one_work+0x18e/0x370 [ 370.023122] worker_thread+0x317/0x450 [ 370.023128] ? __pfx_worker_thread+0x10/0x10 [ 370.023134] kthread+0x10b/0x220 [ 370.023139] ? __pfx_kthread+0x10/0x10 [ 370.023144] ret_from_fork+0x134/0x150 [ 370.023149] ? __pfx_kthread+0x10/0x10 [ 370.023154] ret_from_fork_asm+0x1a/0x30 [ 370.023161] </TASK> [ 465.208692] perf: interrupt took too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 79000 [ 492.900268] INFO: task kworker/0:0:9 blocked for more than 368 seconds. [ 492.900287] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 492.900292] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 492.900296] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 492.900306] Workqueue: firewire fw_device_workfn [firewire_core] [ 492.900354] Call Trace: [ 492.900358] <TASK> [ 492.900364] __schedule+0x2ed/0x7c0 [ 492.900377] schedule+0x27/0x90 [ 492.900383] schedule_timeout+0xcf/0x110 [ 492.900391] wait_for_completion+0x82/0x160 [ 492.900397] fw_run_transaction+0xed/0x130 [firewire_core] [ 492.900432] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 492.900466] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 492.900499] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 492.900533] read_rom+0x64/0xb0 [firewire_core] [ 492.900566] read_config_rom+0x9f/0x440 [firewire_core] [ 492.900599] ? psi_task_switch+0x17e/0x390 [ 492.900607] fw_device_init+0x48/0x470 [firewire_core] [ 492.900641] fw_device_workfn+0x12/0x20 [firewire_core] [ 492.900673] process_one_work+0x18e/0x370 [ 492.900681] worker_thread+0x317/0x450 [ 492.900688] ? __pfx_worker_thread+0x10/0x10 [ 492.900694] kthread+0x10b/0x220 [ 492.900699] ? __pfx_kthread+0x10/0x10 [ 492.900704] ret_from_fork+0x134/0x150 [ 492.900709] ? __pfx_kthread+0x10/0x10 [ 492.900714] ret_from_fork_asm+0x1a/0x30 [ 492.900722] </TASK> [ 615.779806] INFO: task kworker/0:0:9 blocked for more than 491 seconds. [ 615.779837] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 615.779841] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 615.779844] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 615.779853] Workqueue: firewire fw_device_workfn [firewire_core] [ 615.779937] Call Trace: [ 615.779942] <TASK> [ 615.779949] __schedule+0x2ed/0x7c0 [ 615.779964] schedule+0x27/0x90 [ 615.779968] schedule_timeout+0xcf/0x110 [ 615.779975] wait_for_completion+0x82/0x160 [ 615.779979] fw_run_transaction+0xed/0x130 [firewire_core] [ 615.780004] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 615.780028] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 615.780051] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 615.780074] read_rom+0x64/0xb0 [firewire_core] [ 615.780097] read_config_rom+0x9f/0x440 [firewire_core] [ 615.780120] ? psi_task_switch+0x17e/0x390 [ 615.780127] fw_device_init+0x48/0x470 [firewire_core] [ 615.780151] fw_device_workfn+0x12/0x20 [firewire_core] [ 615.780173] process_one_work+0x18e/0x370 [ 615.780181] worker_thread+0x317/0x450 [ 615.780185] ? __pfx_worker_thread+0x10/0x10 [ 615.780189] kthread+0x10b/0x220 [ 615.780194] ? __pfx_kthread+0x10/0x10 [ 615.780198] ret_from_fork+0x134/0x150 [ 615.780202] ? __pfx_kthread+0x10/0x10 [ 615.780205] ret_from_fork_asm+0x1a/0x30 [ 615.780213] </TASK> [ 738.657061] INFO: task kworker/0:0:9 blocked for more than 614 seconds. [ 738.657079] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 738.657084] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 738.657087] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 738.657097] Workqueue: firewire fw_device_workfn [firewire_core] [ 738.657142] Call Trace: [ 738.657146] <TASK> [ 738.657151] __schedule+0x2ed/0x7c0 [ 738.657163] schedule+0x27/0x90 [ 738.657170] schedule_timeout+0xcf/0x110 [ 738.657177] wait_for_completion+0x82/0x160 [ 738.657183] fw_run_transaction+0xed/0x130 [firewire_core] [ 738.657218] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 738.657252] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 738.657285] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 738.657318] read_rom+0x64/0xb0 [firewire_core] [ 738.657351] read_config_rom+0x9f/0x440 [firewire_core] [ 738.657383] ? psi_task_switch+0x17e/0x390 [ 738.657391] fw_device_init+0x48/0x470 [firewire_core] [ 738.657425] fw_device_workfn+0x12/0x20 [firewire_core] [ 738.657457] process_one_work+0x18e/0x370 [ 738.657465] worker_thread+0x317/0x450 [ 738.657471] ? __pfx_worker_thread+0x10/0x10 [ 738.657477] kthread+0x10b/0x220 [ 738.657482] ? __pfx_kthread+0x10/0x10 [ 738.657487] ret_from_fork+0x134/0x150 [ 738.657492] ? __pfx_kthread+0x10/0x10 [ 738.657497] ret_from_fork_asm+0x1a/0x30 [ 738.657504] </TASK> [ 845.725853] perf: interrupt took too long (3153 > 3147), lowering kernel.perf_event_max_sample_rate to 63000 [ 861.535406] INFO: task kworker/0:0:9 blocked for more than 737 seconds. [ 861.535425] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 861.535430] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 861.535434] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 861.535443] Workqueue: firewire fw_device_workfn [firewire_core] [ 861.535490] Call Trace: [ 861.535494] <TASK> [ 861.535499] __schedule+0x2ed/0x7c0 [ 861.535511] schedule+0x27/0x90 [ 861.535518] schedule_timeout+0xcf/0x110 [ 861.535525] wait_for_completion+0x82/0x160 [ 861.535531] fw_run_transaction+0xed/0x130 [firewire_core] [ 861.535566] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 861.535599] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 861.535632] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 861.535665] read_rom+0x64/0xb0 [firewire_core] [ 861.535699] read_config_rom+0x9f/0x440 [firewire_core] [ 861.535731] ? psi_task_switch+0x17e/0x390 [ 861.535739] fw_device_init+0x48/0x470 [firewire_core] [ 861.535773] fw_device_workfn+0x12/0x20 [firewire_core] [ 861.535805] process_one_work+0x18e/0x370 [ 861.535812] worker_thread+0x317/0x450 [ 861.535818] ? __pfx_worker_thread+0x10/0x10 [ 861.535824] kthread+0x10b/0x220 [ 861.535830] ? __pfx_kthread+0x10/0x10 [ 861.535835] ret_from_fork+0x134/0x150 [ 861.535839] ? __pfx_kthread+0x10/0x10 [ 861.535844] ret_from_fork_asm+0x1a/0x30 [ 861.535852] </TASK> [ 984.413795] INFO: task kworker/0:0:9 blocked for more than 860 seconds. [ 984.413813] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 984.413817] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 984.413821] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 984.413830] Workqueue: firewire fw_device_workfn [firewire_core] [ 984.413879] Call Trace: [ 984.413883] <TASK> [ 984.413889] __schedule+0x2ed/0x7c0 [ 984.413901] schedule+0x27/0x90 [ 984.413907] schedule_timeout+0xcf/0x110 [ 984.413915] wait_for_completion+0x82/0x160 [ 984.413921] fw_run_transaction+0xed/0x130 [firewire_core] [ 984.413956] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 984.413989] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 984.414022] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 984.414055] read_rom+0x64/0xb0 [firewire_core] [ 984.414089] read_config_rom+0x9f/0x440 [firewire_core] [ 984.414127] ? psi_task_switch+0x17e/0x390 [ 984.414135] fw_device_init+0x48/0x470 [firewire_core] [ 984.414169] fw_device_workfn+0x12/0x20 [firewire_core] [ 984.414202] process_one_work+0x18e/0x370 [ 984.414210] worker_thread+0x317/0x450 [ 984.414216] ? __pfx_worker_thread+0x10/0x10 [ 984.414222] kthread+0x10b/0x220 [ 984.414228] ? __pfx_kthread+0x10/0x10 [ 984.414233] ret_from_fork+0x134/0x150 [ 984.414237] ? __pfx_kthread+0x10/0x10 [ 984.414242] ret_from_fork_asm+0x1a/0x30 [ 984.414250] </TASK> [ 1107.292039] INFO: task kworker/0:0:9 blocked for more than 983 seconds. [ 1107.292055] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 1107.292058] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1107.292061] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 1107.292068] Workqueue: firewire fw_device_workfn [firewire_core] [ 1107.292107] Call Trace: [ 1107.292110] <TASK> [ 1107.292114] __schedule+0x2ed/0x7c0 [ 1107.292123] schedule+0x27/0x90 [ 1107.292127] schedule_timeout+0xcf/0x110 [ 1107.292132] wait_for_completion+0x82/0x160 [ 1107.292137] fw_run_transaction+0xed/0x130 [firewire_core] [ 1107.292160] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 1107.292183] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 1107.292205] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 1107.292227] read_rom+0x64/0xb0 [firewire_core] [ 1107.292249] read_config_rom+0x9f/0x440 [firewire_core] [ 1107.292271] ? psi_task_switch+0x17e/0x390 [ 1107.292277] fw_device_init+0x48/0x470 [firewire_core] [ 1107.292299] fw_device_workfn+0x12/0x20 [firewire_core] [ 1107.292321] process_one_work+0x18e/0x370 [ 1107.292326] worker_thread+0x317/0x450 [ 1107.292330] ? __pfx_worker_thread+0x10/0x10 [ 1107.292334] kthread+0x10b/0x220 [ 1107.292338] ? __pfx_kthread+0x10/0x10 [ 1107.292342] ret_from_fork+0x134/0x150 [ 1107.292345] ? __pfx_kthread+0x10/0x10 [ 1107.292348] ret_from_fork_asm+0x1a/0x30 [ 1107.292354] </TASK> [ 1230.171464] INFO: task kworker/0:0:9 blocked for more than 1105 seconds. [ 1230.171489] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 1230.171492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1230.171495] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 1230.171504] Workqueue: firewire fw_device_workfn [firewire_core] [ 1230.171573] Call Trace: [ 1230.171578] <TASK> [ 1230.171584] __schedule+0x2ed/0x7c0 [ 1230.171597] schedule+0x27/0x90 [ 1230.171602] schedule_timeout+0xcf/0x110 [ 1230.171610] wait_for_completion+0x82/0x160 [ 1230.171615] fw_run_transaction+0xed/0x130 [firewire_core] [ 1230.171639] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 1230.171661] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 1230.171684] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 1230.171706] read_rom+0x64/0xb0 [firewire_core] [ 1230.171728] read_config_rom+0x9f/0x440 [firewire_core] [ 1230.171750] ? psi_task_switch+0x17e/0x390 [ 1230.171758] fw_device_init+0x48/0x470 [firewire_core] [ 1230.171781] fw_device_workfn+0x12/0x20 [firewire_core] [ 1230.171802] process_one_work+0x18e/0x370 [ 1230.171809] worker_thread+0x317/0x450 [ 1230.171813] ? __pfx_worker_thread+0x10/0x10 [ 1230.171817] kthread+0x10b/0x220 [ 1230.171822] ? __pfx_kthread+0x10/0x10 [ 1230.171825] ret_from_fork+0x134/0x150 [ 1230.171830] ? __pfx_kthread+0x10/0x10 [ 1230.171833] ret_from_fork_asm+0x1a/0x30 [ 1230.171839] </TASK> [ 1353.048685] INFO: task kworker/0:0:9 blocked for more than 1228 seconds. [ 1353.048702] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 1353.048707] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1353.048710] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 1353.048720] Workqueue: firewire fw_device_workfn [firewire_core] [ 1353.048765] Call Trace: [ 1353.048768] <TASK> [ 1353.048774] __schedule+0x2ed/0x7c0 [ 1353.048786] schedule+0x27/0x90 [ 1353.048792] schedule_timeout+0xcf/0x110 [ 1353.048799] wait_for_completion+0x82/0x160 [ 1353.048805] fw_run_transaction+0xed/0x130 [firewire_core] [ 1353.048840] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 1353.048874] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 1353.048907] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 1353.048940] read_rom+0x64/0xb0 [firewire_core] [ 1353.048973] read_config_rom+0x9f/0x440 [firewire_core] [ 1353.049006] ? psi_task_switch+0x17e/0x390 [ 1353.049014] fw_device_init+0x48/0x470 [firewire_core] [ 1353.049047] fw_device_workfn+0x12/0x20 [firewire_core] [ 1353.049079] process_one_work+0x18e/0x370 [ 1353.049087] worker_thread+0x317/0x450 [ 1353.049093] ? __pfx_worker_thread+0x10/0x10 [ 1353.049099] kthread+0x10b/0x220 [ 1353.049104] ? __pfx_kthread+0x10/0x10 [ 1353.049109] ret_from_fork+0x134/0x150 [ 1353.049114] ? __pfx_kthread+0x10/0x10 [ 1353.049119] ret_from_fork_asm+0x1a/0x30 [ 1353.049126] </TASK> [ 1353.049129] Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: linux-image-6.17.0-20-generic 6.17.0-20.20 ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13 Uname: Linux 6.17.0-20-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: js1 1905 F.... wireplumber /dev/snd/controlC1: js1 1905 F.... wireplumber /dev/snd/seq: js1 1884 F.... pipewire CasperMD5CheckResult: unknown Date: Fri Apr 17 08:30:03 2026 InstallationDate: Installed on 2018-12-10 (2685 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=591ea17a-5ac6-4e8b-adb3-75a3dab238d5 ro irqpoll cryptdevice=UUID=6416a2a8-8a76-44df-8d5f-9c465982298a:luks-6416a2a8-8a76-44df-8d5f-9c465982298a root=/dev/mapper/luks-6416a2a8-8a76-44df-8d5f-9c465982298a resume=/dev/mapper/luks-6416a2a8-8a76-44df-8d5f-9c465982298a ipv6.disable=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2007 dmi.bios.release: 0.0 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97520J.86A.2674.2007.0315.1546 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX2 dmi.board.vendor: Intel Corporation dmi.board.version: AAD53350-507 dmi.chassis.type: 2 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97520J.86A.2674.2007.0315.1546:bd03/15/2007:br0.0:efr0.0:svn:pn:pvr:rvnIntelCorporation:rnD975XBX2:rvrAAD53350-507:cvn:ct2:cvr:sku: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148662/+subscriptions

[Bug 2144577] Re: BUG: kernel NULL pointer dereference in amdgpu

I tested Ubuntu 25.10 with kernel 6.17.0-24-generic and it does boot on my PC. ** Tags removed: verification-needed-questing-linux ** Tags added: verification-done-questing-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2144577 Title: BUG: kernel NULL pointer dereference in amdgpu Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: In Progress Status in linux source package in Questing: In Progress Status in linux source package in Resolute: Fix Released Bug description: SRU Justification [Impact] System freezes during boot on machines with AMD Southern Islands (SI) GPUs using the amdgpu driver . The amdgpu driver calls flush_gpu_tlb_pasid() in a workqueue, but on SI hardware this function pointer is NULL. The kernel hits a NULL pointer dereference in amdgpu_gmc_flush_gpu_tlb_pasid() and crashes. Error log: kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu] kernel: RIP: 0010:0x0 kernel: Call Trace: kernel: amdgpu_gmc_flush_gpu_tlb_pasid+0xfd/0x480 [amdgpu] kernel: amdgpu_tlb_fence_work+0x77/0x110 [amdgpu] Hits every boot on affected hardware. Regression from 6.17.0-14 to 6.17.0-19. [Fix] Two patches fix this together: 1. f4db9913e4d3 ("drm/amdgpu: validate the flush_gpu_tlb_pasid()") Adds a NULL check for flush_gpu_tlb_pasid before calling it. Upstream in v7.0-rc1. 2. e3a6eff92bbd ("drm/amdgpu: Fix validating flush_gpu_tlb_pasid()") Fixes the first patch — the early return skipped the unlock, causing a deadlock. Changes the bare return to a goto that unlocks first. Upstream in v7.0-rc1. Fixes: f4db9913e4d3 [Test Plan] On a machine with an AMD SI GPU (Tahiti, Pitcairn, Verde, Oland, Hainan) booted with amdgpu.si_support=1: $ sudo reboot Without patches: kernel NULL pointer dereference during boot, system freezes. With patches: system boots normally, no crash or error in dmesg. Check dmesg after boot: $ dmesg | grep -i "BUG\|NULL pointer\|amdgpu" Without patches: "BUG: kernel NULL pointer dereference" present. With patches: no BUG or NULL pointer lines. [Where problems could occur] Could break TLB flushing on amdgpu. If the NULL check gates too broadly, TLB flushes could be skipped on GPUs that do have flush_gpu_tlb_pasid. This would cause stale TLB entries and GPU page faults or rendering corruption. The unlock path change in the second patch touches the reset/lock logic in amdgpu_gmc_flush_gpu_tlb_pasid(). A wrong goto target could leave the reset domain lock held, deadlocking the GPU. [Other Info] Both patches are upstream in v7.0-rc1. =========================================================== Ubuntu 25.10 with kernel 6.17.0-19-generic doesn't boot on my PC. I freezes on the booting screen, and the kernel logs show a bug: kernel: Linux version 6.17.0-19-generic (buildd@lcy02-amd64-084) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-4ubuntu4) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.45) #19-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 6 14:02:58 UTC 2026 (Ubuntu 6.17.0-19.19-generic 6.17.13) kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=354e3c09-bfde-4e47-850f-fe872a882ae5 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 # ... kernel: [drm] Initialized amdgpu 3.64.0 for 0000:01:00.0 on minor 1 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 kernel: #PF: supervisor instruction fetch in kernel mode kernel: #PF: error_code(0x0010) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: Oops: 0010 [#1] SMP PTI kernel: CPU: 3 UID: 0 PID: 109 Comm: kworker/3:1 Not tainted 6.17.0-19-generic #19-Ubuntu PREEMPT(voluntary) kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z77 Pro3, BIOS P1.10 04/10/2012 kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu] kernel: RIP: 0010:0x0 kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. kernel: RSP: 0018:ffffce560061fdb0 EFLAGS: 00010246 kernel: RAX: 0000000000000000 RBX: 0000000000008000 RCX: 0000000000000001 kernel: RDX: 0000000000000002 RSI: 0000000000008000 RDI: ffff8a4a6d180000 kernel: RBP: ffffce560061fe08 R08: 0000000000000000 R09: 0000000000000000 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001 kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000 kernel: FS: 0000000000000000(0000) GS:ffff8a4da87ff000(0000) knlGS:0000000000000000 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel: CR2: ffffffffffffffd6 CR3: 00000003de040002 CR4: 00000000001726f0 kernel: Call Trace: kernel: <TASK> kernel: amdgpu_gmc_flush_gpu_tlb_pasid+0xfd/0x480 [amdgpu] kernel: amdgpu_tlb_fence_work+0x77/0x110 [amdgpu] kernel: process_one_work+0x18e/0x370 kernel: worker_thread+0x317/0x450 kernel: ? _raw_spin_lock_irqsave+0xe/0x20 kernel: ? __pfx_worker_thread+0x10/0x10 kernel: kthread+0x10b/0x220 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x134/0x150 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork_asm+0x1a/0x30 kernel: </TASK> kernel: Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg bnep ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limit xt_addrtype xt_mac xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat binfmt_misc nf_tables amdgpu(+) usblp intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel amdxcp at24 mei_hdcp mei_pxp kvm snd_hda_codec_atihdmi drm_panel_backlight_quirks gpu_sched irqbypass snd_hda_codec_hdmi drm_buddy snd_hda_codec_alc662 rapl btusb snd_hda_codec_realtek_lib intel_cstate snd_hda_codec_generic radeon btrtl snd_hda_intel btintel i2c_i801 btbcm snd_hda_codec btmtk i2c_smbus drm_ttm_helper i2c_mux ttm bluetooth snd_seq_midi snd_hda_core snd_seq_midi_event drm_exec snd_intel_dspcfg snd_rawmidi drm_suballoc_helper snd_intel_sdw_acpi drm_display_helper lpc_ich snd_hwdep snd_seq snd_pcm snd_seq_device cec snd_timer rc_core snd i2c_algo_bit soundcore mei_me mei intel_smartconnect joydev kernel: input_leds mac_hid sch_fq_codel msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 dm_crypt wacom uas usb_storage hid_generic usbhid hid r8169 polyval_clmulni ghash_clmulni_intel psmouse ahci realtek serio_raw libahci video wmi aesni_intel kernel: CR2: 0000000000000000 kernel: ---[ end trace 0000000000000000 ]--- kernel: RIP: 0010:0x0 kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. kernel: RSP: 0018:ffffce560061fdb0 EFLAGS: 00010246 kernel: RAX: 0000000000000000 RBX: 0000000000008000 RCX: 0000000000000001 kernel: RDX: 0000000000000002 RSI: 0000000000008000 RDI: ffff8a4a6d180000 kernel: RBP: ffffce560061fe08 R08: 0000000000000000 R09: 0000000000000000 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001 kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000 kernel: FS: 0000000000000000(0000) GS:ffff8a4da87ff000(0000) knlGS:0000000000000000 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel: CR2: ffffffffffffffd6 CR3: 00000003de040002 CR4: 00000000001726f0 kernel: note: kworker/3:1[109] exited with irqs disabled kernel: loop50: detected capacity change from 0 to 8 kernel: fbcon: amdgpudrmfb (fb0) is primary device kernel: fbcon: Deferring console take-over kernel: amdgpu 0000:01:00.0: [drm] fb0: amdgpudrmfb frame buffer device kernel: NET: Registered PF_QIPCRTR protocol family kernel: sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 > kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 kernel: #PF: supervisor instruction fetch in kernel mode kernel: #PF: error_code(0x0010) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: Oops: 0010 [#2] SMP PTI kernel: CPU: 1 UID: 0 PID: 91 Comm: kworker/1:1 Tainted: G D 6.17.0-19-generic #19-Ubuntu PREEMPT(voluntary) kernel: Tainted: [D]=DIE kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z77 Pro3, BIOS P1.10 04/10/2012 kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu] kernel: RIP: 0010:0x0 kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. kernel: RSP: 0000:ffffce5600477db0 EFLAGS: 00010246 kernel: RAX: 0000000000000000 RBX: 0000000000008001 RCX: 0000000000000001 kernel: RDX: 0000000000000002 RSI: 0000000000008001 RDI: ffff8a4a6d180000 kernel: RBP: ffffce5600477e08 R08: 0000000000000000 R09: 0000000000000000 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001 kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000 kernel: FS: 0000000000000000(0000) GS:ffff8a4da86ff000(0000) knlGS:0000000000000000 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel: CR2: ffffffffffffffd6 CR3: 0000000101242006 CR4: 00000000001726f0 kernel: Call Trace: kernel: <TASK> kernel: amdgpu_gmc_flush_gpu_tlb_pasid+0xfd/0x480 [amdgpu] kernel: amdgpu_tlb_fence_work+0x77/0x110 [amdgpu] kernel: process_one_work+0x18e/0x370 kernel: worker_thread+0x317/0x450 kernel: ? _raw_spin_lock_irqsave+0xe/0x20 kernel: ? __pfx_worker_thread+0x10/0x10 kernel: kthread+0x10b/0x220 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x134/0x150 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork_asm+0x1a/0x30 kernel: </TASK> kernel: Modules linked in: qrtr rfcomm cmac algif_hash algif_skcipher af_alg bnep ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limit xt_addrtype xt_mac xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat binfmt_misc nf_tables amdgpu usblp intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel amdxcp at24 mei_hdcp mei_pxp kvm snd_hda_codec_atihdmi drm_panel_backlight_quirks gpu_sched irqbypass snd_hda_codec_hdmi drm_buddy snd_hda_codec_alc662 rapl btusb snd_hda_codec_realtek_lib intel_cstate snd_hda_codec_generic radeon btrtl snd_hda_intel btintel i2c_i801 btbcm snd_hda_codec btmtk i2c_smbus drm_ttm_helper i2c_mux ttm bluetooth snd_seq_midi snd_hda_core snd_seq_midi_event drm_exec snd_intel_dspcfg snd_rawmidi drm_suballoc_helper snd_intel_sdw_acpi drm_display_helper lpc_ich snd_hwdep snd_seq snd_pcm snd_seq_device cec snd_timer rc_core snd i2c_algo_bit soundcore mei_me mei intel_smartconnect joydev kernel: input_leds mac_hid sch_fq_codel msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 dm_crypt wacom uas usb_storage hid_generic usbhid hid r8169 polyval_clmulni ghash_clmulni_intel psmouse ahci realtek serio_raw libahci video wmi aesni_intel kernel: CR2: 0000000000000000 kernel: ---[ end trace 0000000000000000 ]--- kernel: RIP: 0010:0x0 kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. kernel: RSP: 0018:ffffce560061fdb0 EFLAGS: 00010246 kernel: RAX: 0000000000000000 RBX: 0000000000008000 RCX: 0000000000000001 kernel: RDX: 0000000000000002 RSI: 0000000000008000 RDI: ffff8a4a6d180000 kernel: RBP: ffffce560061fe08 R08: 0000000000000000 R09: 0000000000000000 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001 kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000 kernel: FS: 0000000000000000(0000) GS:ffff8a4da86ff000(0000) knlGS:0000000000000000 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel: CR2: ffffffffffffffd6 CR3: 0000000101242006 CR4: 00000000001726f0 kernel: note: kworker/1:1[91] exited with irqs disabled The previous kernel 6.17.0-14-generic boots without any issues. I'll try to attach the required information using `apport-collect -p linux BUG#`, but it'll be collected after successfully booting with 6.17.0-14, whereas the bug occurs with 6.17.0-19. --- ProblemType: Bug ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC0: mateusz 3017 F.... wireplumber  /dev/snd/controlC1: mateusz 3017 F.... wireplumber  /dev/snd/seq: mateusz 2999 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 25.10 InstallationDate: Installed on 2020-10-14 (1979 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron:  LANG=pl_PL.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=354e3c09-bfde-4e47-850f-fe872a882ae5 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9 RelatedPackageVersions:  firmware-sof N/A  linux-firmware 20250901.git993ff19b-0ubuntu1.9 RfKill:  0: hci0: Bluetooth   Soft blocked: yes   Hard blocked: no Tags: questing Uname: Linux 6.17.0-14-generic x86_64 UpgradeStatus: Upgraded to questing on 2026-01-10 (65 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/10/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: Z77 Pro3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd04/10/2012:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Pro3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144577/+subscriptions

[Bug 2148742] [NEW] R9 m370x amdgpu bug

Public bug reported: in ubuntu 26.04 daily the new linux kernel and amdgpu is causing a conflict with the r9 m370x in the macbook pro 2015. it crashes the whole computer even trying to start the installer. to replicate this bug get a macbook pro 2015 with a r9 and try to start the ubuntu 26.04 daily live image. this appears to be some type of graphics bug. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148742 Title: R9 m370x amdgpu bug Status in linux package in Ubuntu: New Bug description: in ubuntu 26.04 daily the new linux kernel and amdgpu is causing a conflict with the r9 m370x in the macbook pro 2015. it crashes the whole computer even trying to start the installer. to replicate this bug get a macbook pro 2015 with a r9 and try to start the ubuntu 26.04 daily live image. this appears to be some type of graphics bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148742/+subscriptions

[Bug 2083638] Re: overnight crashes

It's hard to be certain with system crashes that don't have reliable reproducers, but my system has not crashed since I disabled swap on zfs. It worked fine for years until it didn't, and it took me 15 months of occasional overnight crashes to remember it. ** Changed in: linux (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2083638 Title: overnight crashes Status in linux package in Ubuntu: Won't Fix Bug description: Hello, twice recently my 20.04 LTS laptop in a docking station was very unhappy after leaving it unattended overnight: - the external monitor did not wake from dpms sleep when pressing keys on either the external keyboard or the built-in keyboard - the built-in monitor did not wake from xrandr "off" state (I use this command to use only my external monitor within X11: xrandr --output DP-1-3 --auto --output eDP-1 --off) - nmap port scan could find the open ssh port on my network - connecting via ssh hangs long enough that I decided to force-power the laptop - nothing stands out in journalctl logs for the two boots in question, except it is a little strange that the last log entries appear to be within thirty seconds of the cron.daily run: $ journalctl -b-3 | tail -20 Sep 27 06:23:26 millbarge rtkit-daemon[4551]: Supervising 8 threads of 3 processes of 1 users. Sep 27 06:23:44 millbarge ubxtool[4438]: Fri, 27 Sep 2024 06:23:44 +0000 src 46 (fix: 3) currently receiving: 0,6@0 0,12@0 0,14@0 0,15@0 0,17@0 0,19@0 0,22@0 0,24@0 1,131@0 1,133@0 1,135@0 2,2@1 2,10@1 2,11@1 2,14@1 2,24@1 2,25@1 2,36@1 3,27@0 3,29@0 3,30@0 Sep 27 06:23:45 millbarge ubxtool[4437]: Fri, 27 Sep 2024 06:23:45 +0000 src 45 (fix: 3) currently receiving: 0,6@0 0,14@0 0,17@0 0,19@0 0,22@0 1,131@0 1,135@0 2,2@1 2,10@1 2,11@1 2,24@1 2,25@1 2,36@1 6,11@0 6,12@0 6,22@0 Sep 27 06:24:15 millbarge ubxtool[4438]: Fri, 27 Sep 2024 06:24:15 +0000 src 46 (fix: 3) currently receiving: 0,6@0 0,12@0 0,14@0 0,15@0 0,17@0 0,19@0 0,22@0 0,24@0 1,131@0 1,133@0 1,135@0 2,2@1 2,8@1 2,10@1 2,11@1 2,14@1 2,24@1 2,25@1 2,36@1 3,27@0 3,29@0 3,30@0 Sep 27 06:24:16 millbarge ubxtool[4437]: Fri, 27 Sep 2024 06:24:16 +0000 src 45 (fix: 3) currently receiving: 0,6@0 0,14@0 0,17@0 0,19@0 0,22@0 1,131@0 1,135@0 2,2@1 2,10@1 2,11@1 2,24@1 2,25@1 2,36@1 6,11@0 6,12@0 6,22@0 Sep 27 06:24:46 millbarge ubxtool[4438]: Fri, 27 Sep 2024 06:24:46 +0000 src 46 (fix: 3) currently receiving: 0,6@0 0,12@0 0,14@0 0,15@0 0,17@0 0,19@0 0,22@0 0,24@0 1,131@0 1,133@0 1,135@0 2,2@1 2,8@1 2,10@1 2,11@1 2,14@1 2,24@1 2,25@1 2,36@1 3,27@0 3,29@0 3,30@0 Sep 27 06:24:47 millbarge ubxtool[4437]: Fri, 27 Sep 2024 06:24:47 +0000 src 45 (fix: 3) currently receiving: 0,6@0 0,14@0 0,17@0 0,19@0 0,22@0 1,131@0 1,135@0 2,2@1 2,7@1 2,10@1 2,11@1 2,24@1 2,25@1 2,36@1 6,11@0 6,12@0 6,22@0 Sep 27 06:24:47 millbarge rtkit-daemon[4551]: Supervising 8 threads of 3 processes of 1 users. Sep 27 06:24:47 millbarge rtkit-daemon[4551]: Supervising 8 threads of 3 processes of 1 users. Sep 27 06:25:01 millbarge audit[864607]: USER_ACCT pid=864607 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_permit acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' Sep 27 06:25:01 millbarge audit[864607]: CRED_ACQ pid=864607 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit,pam_cap acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' Sep 27 06:25:01 millbarge audit[864607]: SYSCALL arch=c000003e syscall=1 success=yes exit=1 a0=7 a1=7fff051b2380 a2=1 a3=7f4ea1523371 items=0 ppid=2950 pid=864607 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=825 comm="cron" exe="/usr/sbin/cron" key=(null) Sep 27 06:25:01 millbarge audit: PROCTITLE proctitle=2F7573722F7362696E2F43524F4E002D66 Sep 27 06:25:02 millbarge CRON[864607]: pam_unix(cron:session): session opened for user root by (uid=0) Sep 27 06:25:01 millbarge audit[864607]: USER_START pid=864607 uid=0 auid=0 ses=825 msg='op=PAM:session_open grantors=pam_loginuid,pam_env,pam_env,pam_permit,pam_umask,pam_unix,pam_limits acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' Sep 27 06:25:02 millbarge CRON[864608]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Sep 27 06:25:17 millbarge ubxtool[4438]: Fri, 27 Sep 2024 06:25:17 +0000 src 46 (fix: 3) currently receiving: 0,6@0 0,12@0 0,14@0 0,15@0 0,17@0 0,19@0 0,22@0 0,24@0 1,131@0 1,133@0 1,135@0 2,2@1 2,8@1 2,10@1 2,11@1 2,14@1 2,24@1 2,36@1 3,27@0 3,29@0 3,30@0 Sep 27 06:25:18 millbarge ubxtool[4437]: Fri, 27 Sep 2024 06:25:18 +0000 src 45 (fix: 3) currently receiving: 0,6@0 0,14@0 0,17@0 0,19@0 0,22@0 1,131@0 1,135@0 2,2@1 2,7@1 2,10@1 2,11@1 2,24@1 2,25@1 2,36@1 6,11@0 6,12@0 6,21@0 6,22@0 Sep 27 06:25:19 millbarge rtkit-daemon[4551]: Supervising 8 threads of 3 processes of 1 users. Sep 27 06:25:19 millbarge rtkit-daemon[4551]: Supervising 8 threads of 3 processes of 1 users. $ journalctl -b-2 | tail -20 Oct 03 06:24:19 millbarge rtkit-daemon[6412]: Supervising 10 threads of 5 processes of 1 users. Oct 03 06:24:19 millbarge rtkit-daemon[6412]: Supervising 10 threads of 5 processes of 1 users. Oct 03 06:24:21 millbarge rtkit-daemon[6412]: Supervising 10 threads of 5 processes of 1 users. Oct 03 06:24:21 millbarge rtkit-daemon[6412]: Supervising 10 threads of 5 processes of 1 users. Oct 03 06:24:26 millbarge ubxtool[7429]: Thu, 03 Oct 2024 06:24:26 +0000 src 46 (fix: 3) currently receiving: 0,6@0 0,12@0 0,14@0 0,17@0 0,19@0 0,22@0 0,24@0 1,131@0 1,133@0 1,135@0 2,2@1 2,14@1 2,15@1 2,27@1 2,29@1 2,34@1 2,36@1 3,24@0 3,26@0 3,29@0 Oct 03 06:24:30 millbarge ubxtool[7428]: Thu, 03 Oct 2024 06:24:30 +0000 src 45 (fix: 3) currently receiving: 0,6@0 0,11@0 0,14@0 0,17@0 0,19@0 0,22@0 0,24@0 1,135@0 2,2@1 2,14@1 2,15@1 2,27@1 2,29@1 2,30@1 2,34@1 6,9@0 6,10@0 6,11@0 Oct 03 06:24:50 millbarge rtkit-daemon[6412]: Supervising 10 threads of 5 processes of 1 users. Oct 03 06:24:50 millbarge rtkit-daemon[6412]: Supervising 10 threads of 5 processes of 1 users. Oct 03 06:24:57 millbarge ubxtool[7429]: Thu, 03 Oct 2024 06:24:57 +0000 src 46 (fix: 3) currently receiving: 0,6@0 0,12@0 0,14@0 0,17@0 0,19@0 0,22@0 0,24@0 1,131@0 1,133@0 1,135@0 2,2@1 2,14@1 2,15@1 2,27@1 2,29@1 2,34@1 2,36@1 3,24@0 3,26@0 3,29@0 Oct 03 06:25:01 millbarge ubxtool[7428]: Thu, 03 Oct 2024 06:25:01 +0000 src 45 (fix: 3) currently receiving: 0,6@0 0,11@0 0,14@0 0,17@0 0,19@0 0,22@0 0,24@0 1,135@0 2,2@1 2,14@1 2,15@1 2,27@1 2,29@1 2,30@1 2,34@1 6,9@0 6,10@0 6,11@0 Oct 03 06:25:01 millbarge audit[707426]: USER_ACCT pid=707426 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_permit acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' Oct 03 06:25:01 millbarge audit[707426]: CRED_ACQ pid=707426 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit,pam_cap acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' Oct 03 06:25:01 millbarge audit[707426]: SYSCALL arch=c000003e syscall=1 success=yes exit=1 a0=7 a1=7ffd017ae180 a2=1 a3=7fdf89ba1371 items=0 ppid=3908 pid=707426 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=701 comm="cron" exe="/usr/sbin/cron" key=(null) Oct 03 06:25:01 millbarge audit: PROCTITLE proctitle=2F7573722F7362696E2F43524F4E002D66 Oct 03 06:25:01 millbarge CRON[707426]: pam_unix(cron:session): session opened for user root by (uid=0) Oct 03 06:25:01 millbarge audit[707426]: USER_START pid=707426 uid=0 auid=0 ses=701 msg='op=PAM:session_open grantors=pam_loginuid,pam_env,pam_env,pam_permit,pam_umask,pam_unix,pam_limits acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' Oct 03 06:25:01 millbarge CRON[707427]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Oct 03 06:25:21 millbarge rtkit-daemon[6412]: Supervising 10 threads of 5 processes of 1 users. Oct 03 06:25:21 millbarge rtkit-daemon[6412]: Supervising 10 threads of 5 processes of 1 users. Oct 03 06:25:28 millbarge ubxtool[7429]: Thu, 03 Oct 2024 06:25:28 +0000 src 46 (fix: 3) currently receiving: 0,6@0 0,11@0 0,12@0 0,14@0 0,17@0 0,19@0 0,22@0 0,24@0 1,131@0 1,133@0 1,135@0 2,2@1 2,14@1 2,15@1 2,27@1 2,29@1 2,30@1 2,34@1 2,36@1 3,24@0 3,26@0 3,29@0 Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-196-generic 5.4.0-196.216 ProcVersionSignature: Ubuntu 5.4.0-196.216-generic 5.4.280 Uname: Linux 5.4.0-196-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-196-generic. ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,00100002 HDA:8086280b,80860101,00100000' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-0000:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 Card2.Amixer.info: Card hw:2 'Device'/'USB Audio Device at usb-0000:00:14.0-4.4.1.3.3, full speed' Mixer name : 'USB Mixer' Components : 'USB0c76:160a' Controls : 5 Simple ctrls : 2 CasperMD5CheckResult: skip Date: Thu Oct 3 18:20:17 2024 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 20KHCTO1WW ProcEnviron: LC_TIME=C TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-196-generic root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" LC_TIME=C vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-196-generic N/A linux-backports-modules-5.4.0-196-generic N/A linux-firmware 1.187.39 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-24 (1713 days ago) dmi.bios.date: 10/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET75W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-196-generic. ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: sarnold 6487 F.... pulseaudio /dev/snd/controlC1: sarnold 6487 F.... pulseaudio /dev/snd/controlC0: sarnold 6487 F.... pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,00100002 HDA:8086280b,80860101,00100000' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-0000:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 Card2.Amixer.info: Card hw:2 'Device'/'USB Audio Device at usb-0000:00:14.0-4.4.1.3.3, full speed' Mixer name : 'USB Mixer' Components : 'USB0c76:160a' Controls : 5 Simple ctrls : 2 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 20KHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_TIME=C TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-196-generic root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" LC_TIME=C vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-196.216-generic 5.4.280 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-196-generic N/A linux-backports-modules-5.4.0-196-generic N/A linux-firmware 1.187.39 Tags: focal Uname: Linux 5.4.0-196-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-24 (1721 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET75W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-200-generic. ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,00100002 HDA:8086280b,80860101,00100000' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-0000:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 Card2.Amixer.info: Card hw:2 'Device'/'USB Audio Device at usb-0000:00:14.0-4.4.1.3.3, full speed' Mixer name : 'USB Mixer' Components : 'USB0c76:160a' Controls : 5 Simple ctrls : 2 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 20KHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_TIME=C TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-200-generic root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" LC_TIME=C vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-200.220-generic 5.4.284 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-200-generic N/A linux-backports-modules-5.4.0-200-generic N/A linux-firmware 1.187.39 Tags: focal Uname: Linux 5.4.0-200-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-24 (1782 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET75W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083638/+subscriptions

[Bug 2144530] Re: Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up internal eDP and Radeon-routed USB-C/DP outputs

** Attachment added: "daily live 2026-04-18 normal boot with builtin display via eDP and external display via USB-C-Radeon - both are working!" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+attachment/5962794/+files/gpu-goodboot23-u2604.zip -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2144530 Title: Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up internal eDP and Radeon-routed USB-C/DP outputs Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware-amd-graphics package in Ubuntu: Fix Released Status in linux source package in Resolute: Invalid Status in linux-firmware source package in Resolute: Invalid Status in linux-firmware-amd-graphics source package in Resolute: Fix Released Bug description: [ Impact ] here’s a regression reported by community in 1e2c1534: https://gitlab.freedesktop.org/drm/amd/-/work_items/5143#note_3411517 The last known good version is 43c969c1, and there’s a revert happening in upstream: https://gitlab.freedesktop.org/drm/amd/-/work_items/5143#note_3418637 [ Fix ] Cherry-pick the following revert commit: - d3a8c25 (amdgpu: Revert Yellow Carp DMUB fw to 0x4000045) Firmware in Noble and Questing currently doesn't include the bad version. Only Resolute needs this. [ Test ] Install the firmware package including this revert and boot. The display should light up normally. [ Where the problem could occur] Whatever was introduce after commit 43c969c1 would be reverted. Also, there's an ongoing SRU in Q and N to update the very same file in LP:#2147396. If it happens that they need firmware after commit 43c969c1 to fix the issue, then one of those 2 issues will likely not get fixed. ================= ORIGINAL DESCRIPTION ================= Problem summary =============== On an Acer Nitro AN17-41 laptop, Ubuntu 26.04 development branch with kernel 6.19.0-9-generic fails to display video when the internal panel and/or external USB-C display output are owned by the AMD iGPU. This appears to be a regression or behavior change in the newer Linux graphics stack, because the same machine and same monitor path work under: - Windows 11 - Ubuntu 24.04.4 live ISO The machine has: - Acer Nitro AN17-41 - BIOS V1.25 - AMD Rembrandt / Radeon 680M iGPU (1002:1681) - NVIDIA GeForce RTX 4050 Mobile / Max-Q dGPU (10de:28e1) I collected logs over SSH from another device in the failing cases because the machine was still alive even when both displays were black. Observed behavior on Ubuntu 26.04 / kernel 6.19 ================================================ When AMD owns the display outputs, the system boots but the displays stay black. This affects: - the internal eDP panel - an external monitor connected through the USB-C / DP output routed to Radeon The logs repeatedly show amdgpu DC / DMUB failures such as: - "Failed to enable ASSR" - "No reply for DMUB command: status=3" - "DMCUB error - collecting diagnostic data" - "Error queueing DMUB command: status=2" - "enabling link ... failed: 15" In the failing cases, DRM can still detect AMD-owned outputs as connected and enabled, but they remain black. Environment =========== OS: - Ubuntu 26.04 (Resolute Raccoon development branch) Kernel: - 6.19.0-9-generic Secure Boot: - enabled Hardware: - Acer Nitro AN17-41 - BIOS V1.25 - AMD Radeon 680M iGPU - NVIDIA RTX 4050 Mobile dGPU Regression evidence =================== I now have a working Linux control case on the same laptop and same physical USB-C monitor path. Tested with: - Ubuntu 24.04.4 LTS live ISO Results on Ubuntu 24.04.4: 1. Auto / hybrid mode:    - internal panel works    - external monitor connected to the Radeon-routed USB-C/DP output also works 2. NVIDIA GPU Only mode:    - internal panel works    - the same external monitor on the Radeon-routed USB-C/DP output also works in my test In both Ubuntu 24.04.4 test cases, the displays light up normally and I do not see the repeated amdgpu DC/DMUB failure pattern that appears on Ubuntu 26.04 / kernel 6.19. This strongly suggests: - the hardware is capable of driving both outputs under Linux - the Radeon-routed USB-C output is not fundamentally broken on this laptop - the issue is more likely a regression or missing quirk in the newer graphics/kernel stack used in Ubuntu 26.04 Additional control evidence =========================== The same USB-C monitor connected to the Radeon-routed USB-C output also works in Windows 11 when switching to Extend mode with Win+P. This further suggests that the physical hardware path is functional, and that the failing configuration is specific to the newer Linux graphics stack. What works ========== 1. NVIDIA GPU Only mode in firmware / BIOS on Ubuntu 26.04:    - the internal laptop panel works 2. Windows 11:    - the USB-C monitor connected to the Radeon-routed USB-C output works in Extend mode 3. Ubuntu 24.04.4 live ISO:    - Auto / hybrid mode works    - internal panel works    - Radeon-routed USB-C/DP external monitor works    - NVIDIA GPU Only mode also worked in my test, including the same USB-C monitor What does not work ================== On Ubuntu 26.04 / kernel 6.19: 1. Hybrid / normal mode:    - if the internal panel is owned by AMD, the panel stays black 2. AMD-only test:    - booting with      module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm    - internal eDP stays black    - external USB-C/DP monitor routed to Radeon also stays black This strongly suggests the issue is not caused by nvidia-drm handoff or by both DRM stacks loading together. How to reproduce ================ Case A: Hybrid / normal mode on Ubuntu 26.04 1. Boot Ubuntu 26.04 on Acer Nitro AN17-41. 2. Let the machine use its normal hybrid graphics routing. 3. If the internal panel is owned by AMD, the panel remains black. Case B: AMD-only test on Ubuntu 26.04 1. Boot with:    module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm 2. Connect an external monitor to the USB-C / DP output routed to Radeon before power-on. 3. Boot Ubuntu. 4. Result: both the internal panel and the external USB-C display remain black, although the system is alive and reachable over SSH. Case C: Verbose DRM logging on Ubuntu 26.04 1. Boot with:    drm.debug=0x1e log_buf_len=4M module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm 2. Result: same black screens, with detailed DRM / amdgpu logging showing DMUB / ASSR / link enable failures. Expected result =============== When AMD owns the internal eDP panel and/or Radeon-routed USB-C/DP output, the displays should light up normally and the system should reach a visible graphical session. Actual result ============= The system boots, but the displays stay black. Logs indicate failures in amdgpu DC / DMUB while trying to bring up AMD-owned display links. Important log patterns ====================== Examples consistently seen in the affected Ubuntu 26.04 boots: - "Skipping amdgpu DM backlight registration" - "Failed to get EDID from ACPI: -19" (seen in verbose DRM logging) - "boot timing validation failed ..." - "Failed to enable ASSR" - "No reply for DMUB command: status=3" - "DMCUB error - collecting diagnostic data" - "Error queueing DMUB command: status=2" - "enabling link 0 failed: 15" - "enabling link 2 failed: 15" Why I think this is a kernel/amdgpu issue ========================================= The issue reproduces when NVIDIA modules are blacklisted, so it does not appear to depend on nvidia-drm being active. The internal panel and the Radeon-routed external USB-C/DP output can both be detected as connected/enabled by DRM, but they still remain black. The same hardware and same USB-C path work: - on Windows 11 - on Ubuntu 24.04.4 live ISO This makes it look like an amdgpu DC / DMUB / link bring-up failure in the newer Ubuntu 26.04 graphics stack, rather than: - a simple EDID-not-found case - a generic Optimus/MUX problem - a pure backlight-only issue - a userspace / compositor-only issue - a fundamental hardware limitation of the laptop Tests already performed ======================= On Ubuntu 26.04: 1. Normal hybrid boot    - black internal display when AMD owns it 2. NVIDIA GPU Only mode    - internal panel works 3. AMD-only boot with:    module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm    - both internal eDP and Radeon-routed USB-C/DP stayed black 4. Verbose DRM boot with:    drm.debug=0x1e log_buf_len=4M    - same failure, more detailed DMUB / ASSR / link logs 5. Test with:    amdgpu.sg_display=0    - no improvement 6. Test with:    amdgpu.abmlevel=0    - no improvement On Ubuntu 24.04.4 live ISO: 7. Auto / hybrid mode    - internal panel works    - Radeon-routed USB-C/DP external monitor works 8. NVIDIA GPU Only mode    - internal panel works    - the same Radeon-routed USB-C/DP external monitor also worked in my test Attachments =========== I am attaching log bundles from these scenarios: - gpu-badboot4-nvidiablacklist.zip - gpu-badboot5-nvidiablacklistamdusbc.zip - gpu-badboot6-nvidiablacklistamdusbcdbg.zip - gpu-goodboot7-nvidiaonly-w-usbc-radeon.zip - gpu-badboot8-sgzero.zip - gpu-badboot9-abmzero.zip - gpu-goodboot10-u24044.zip - gpu-goodboot11-u24045.zip These include: - journalctl / dmesg output - DRM connector status and enabled state - lspci / module state - backlight info - EDID decode output - verbose DRM logs where applicable I can reproduce this reliably and I can collect additional logs over SSH because the machine stays alive even when both displays are black. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-6.19.0-9-generic 6.19.0-9.9 ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5 Uname: Linux 6.19.0-9-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC2: denixx 6079 F.... wireplumber  /dev/snd/controlC0: denixx 6079 F.... wireplumber  /dev/snd/controlC1: denixx 6079 F.... wireplumber  /dev/snd/seq: denixx 6059 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 16 08:26:28 2026 InstallationDate: Installed on 2026-03-15 (1 days ago) InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260313) IwDevWlp4s0Link: Not connected. MachineType: Acer Nitro AN17-41 ProcEnviron:  LANG=uk_UA.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color ProcFB:  0 amdgpudrmfb  1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.19.0-9-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2024 dmi.bios.release: 1.25 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Spacia_PEH dmi.board.vendor: RB dmi.board.version: V1.25 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000: dmi.product.family: Acer Nitro 17 dmi.product.name: Nitro AN17-41 dmi.product.sku: 0000000000000000 dmi.product.version: V1.25 dmi.sys.vendor: Acer --- ProblemType: Bug ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC2: ubuntu 4446 F.... wireplumber  /dev/snd/controlC0: ubuntu 4446 F.... wireplumber  /dev/snd/controlC1: ubuntu 4446 F.... wireplumber  /dev/snd/seq: ubuntu 4430 F.... pipewire CasperMD5CheckResult: pass CasperVersion: 26.04.0 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 IwDevWlp4s0Link: Not connected. LiveMediaBuild: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260316) MachineType: Acer Nitro AN17-41 NonfreeKernelModules: zfs Package: linux (not installed) ProcEnviron:  LANG=C.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB:  0 amdgpudrmfb  1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5 Tags: resolute wayland-session Uname: Linux 6.19.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 09/18/2024 dmi.bios.release: 1.25 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Spacia_PEH dmi.board.vendor: RB dmi.board.version: V1.25 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000: dmi.product.family: Acer Nitro 17 dmi.product.name: Nitro AN17-41 dmi.product.sku: 0000000000000000 dmi.product.version: V1.25 dmi.sys.vendor: Acer --- ProblemType: Bug ApportVersion: 2.33.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC2: ubuntu 4386 F.... wireplumber  /dev/snd/controlC0: ubuntu 4386 F.... wireplumber  /dev/snd/controlC1: ubuntu 4386 F.... wireplumber  /dev/snd/seq: ubuntu 4370 F.... pipewire CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CasperVersion: 26.04.1 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 IwDevWlp4s0Link: Not connected. LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260322) MachineType: Acer Nitro AN17-41 NonfreeKernelModules: zfs Package: linux (not installed) ProcEnviron:  LANG=C.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB:  0 amdgpudrmfb  1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash drm.debug=0x1e log_buf_len=4M ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3 Tags: resolute wayland-session Uname: Linux 7.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 09/18/2024 dmi.bios.release: 1.25 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Spacia_PEH dmi.board.vendor: RB dmi.board.version: V1.25 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:pfaAcerNitro17: dmi.product.family: Acer Nitro 17 dmi.product.name: Nitro AN17-41 dmi.product.sku: 0000000000000000 dmi.product.version: V1.25 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+subscriptions

[Bug 2144976] Re: no file /etc/default/grub

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2144976 Title: no file /etc/default/grub Status in linux package in Ubuntu: Confirmed Bug description: the file /etc/default/grub is not here jpb@jpb-B760M-U26: ~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Resolute Raccoon (development branch) Release: 26.04 Codename: resolute jpb@jpb-B760M-U26: ~ $ uname -a Linux jpb-B760M-U26.04 7.0.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 12 11:34:39 UTC 2026 x86_64 GNU/Linux jpb@jpb-B760M-U26: ~ $ jpb@jpb-B760M-U26: ~ $ ls -als /etc/default/g* total 12 4 drwxr-xr-x 2 root root 4096 Mar 13 06:32 . 4 drwxr-xr-x 4 root root 4096 Mar 18 08:15 .. 4 -rw-r--r-- 1 root root 133 Feb 11 23:26 kdump-tools.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144976/+subscriptions

[Bug 2148735] Kernel logs, boot history, lspci, lsusb, and report text

Logs and hardware details collected from affected host. ** Attachment added: "Kernel logs, boot history, lspci, lsusb, and report text" https://bugs.launchpad.net/bugs/2148735/+attachment/5962747/+files/linux-kernel-usb-hard-reset-report.tar.gz -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148735 Title: AMD host hard reset during sustained USB/ADB access, data fabric sync flood event Status in linux package in Ubuntu: New Bug description: # Draft Bug Report: AMD Host Hard Reset During USB Access To Lenovo A7600 Tablet ## Summary Linux host hard-resets during sustained USB access to Android tablets over ADB. The reset happened with a Lenovo A7600-H and also with an Amazon Fire HD 10. It occurred with different USB cables, with and without a powered USB hub, and before updating to the current kernel, so it is not known to be specific to one tablet, one cable, one hub, or `6.17.0-20-generic`. ## System - Distribution: Linux Mint 22.3 (Zena), Ubuntu noble base - Current affected kernel: `6.17.0-20-generic` - Current version signature: `Ubuntu 6.17.0-20.20~24.04.1-generic 6.17.13` - Previous affected kernel before update: `6.14.0-37-generic` - Previous version signature from boot logs: `Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11` - Architecture: x86_64 - Machine hostname: `sven-X600M-STX-R2-0` - CPU/platform: AMD system; kernel reports AMD data fabric reset reason ## Affected Devices - Lenovo A7600-H: - USB device: `17ef:7731 Lenovo Lenovo A7600` - Android build: `A7600H_A442_000_029_150324_ROW` - Android version: 4.4.2 - Amazon Fire HD 10: - Also triggered the same type of host reset during USB tablet access - Used a different USB cable - Also reproduced with a powered USB hub ## What Happened During ADB access, especially long `adb pull` operations from shared storage, the host hard-resets. The session is lost and the next boot reports a crash, not a clean shutdown. The failure happened: - while the tablet was attached directly - while the tablet was attached through a powered USB hub - with more than one USB cable - before and after the kernel was updated from `6.14.0-37-generic` to `6.17.0-20-generic` - with this Lenovo A7600-H tablet - previously with an Amazon Fire HD 10 tablet as well ## Expected Result ADB read operations should either complete or fail gracefully. The host should not hard-reset. ## Actual Result The host resets. After reboot, logs show: ```text x86/amd: Previous system reset reason [0x08000800]: an uncorrected error caused a data fabric sync flood event ``` Other relevant log lines: ```text usb: port power management may be unreliable usb 1-2.3.1: New USB device found, idVendor=17ef, idProduct=7731 usb 1-2.3.1: Product: Lenovo A7600 smscufx: I2C access timed out, resetting I2C hardware smscufx: Timeout waiting for I2C BUSY to clear ``` ## USB Topology At Time Of Investigation The tablet was on a hub path shared with several USB devices: - VIA Labs USB hub - Microchip/SMSC UFX6000 USB display adapter using `smscufx` - ASIX USB Ethernet adapter - C-Media USB audio adapter - USB mass-storage device `lsusb` included: ```text Bus 001 Device 004: ID 17ef:7731 Lenovo Lenovo A7600 Bus 001 Device 006: ID 0424:9d01 Microchip Technology, Inc. (formerly SMSC) UFX6000 Bus 001 Device 007: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter Bus 001 Device 008: ID 0b95:772b ASIX Electronics Corp. AX88772B Bus 002 Device 004: ID 1234:5678 Brain Actuated Technologies VLI Product String ``` ## Reproduction Steps 1. Boot Linux Mint 22.3 with kernel `6.17.0-20-generic`. 2. Connect Lenovo A7600-H Android tablet with USB debugging enabled. 3. Confirm ADB authorization. 4. Start a long ADB read operation, for example: ```bash adb pull -a /storage/emulated/legacy ./sdcard-backup ``` 5. Wait for sustained transfer. 6. Host hard-resets. ## Notes - This is a host stability issue. The tablet remains bootable after the host reset. - Because it reproduced with two tablets and different cables, it is less likely to be a single-device or single-cable fault. - Because the host resets during read-only operations, it is unsafe to use this host for SP Flash Tool or firmware flashing until resolved. - A useful next diagnostic would be reproducing with a minimal USB setup: direct USB 2.0 port, no dock, no USB display, no USB Ethernet, no USB audio, no USB mass storage, and USB autosuspend disabled. - The bug should not be described as a confirmed regression unless a known-good kernel and first-bad kernel are identified. Current evidence says it affects at least `6.14.0-37-generic` and `6.17.0-20-generic`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148735/+subscriptions

[Bug 2148686] Re: FrameworkDesktop: System randomly hangs / freezes after using Chrome (Youtube or Screen-Sharing)

** Tags added: amdgpu ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148686 Title: FrameworkDesktop: System randomly hangs / freezes after using Chrome (Youtube or Screen-Sharing) Status in linux package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Quite recently (last week) my system started to hang/freeze randomly when using Chrome and browsing youtube or when having a Video Call. The system either hangs completely or stops working and blanking the displays. Sometimes it recovers from this state. The usage pattern is always the same * Chrome * Video Quite interestingly during gaming via Steam I did not experience any hang/freeze. It seems to be related to Video handling in Chrome. > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 25.10 Release: 25.10 Codename: questing Hardware: Framework Desktop _AMD Ryzen AI Max 300 Series Processor: AMD RYZEN AI MAX+ 395 w/ Radeon™ 8060S × 32 dmesg gives plenty of information pointing to amdgpu: [ 3536.625642] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3536.625654] amdgpu 0000:c2:00.0: amdgpu: Failed to power gate VPE! [ 3536.625658] [drm:amdgpu_dpm_enable_vpe [amdgpu]] *ERROR* Dpm disable vpe failed, ret = -62. [ 3541.439018] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3541.439025] amdgpu 0000:c2:00.0: amdgpu: Failed to power gate VCN instance 1! [ 3541.439027] [drm:amdgpu_dpm_enable_vcn [amdgpu]] *ERROR* Dpm disable uvd failed, ret = -62. [ 3544.902422] amdgpu 0000:c2:00.0: amdgpu: Dumping IP State [ 3549.702445] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3549.702453] amdgpu 0000:c2:00.0: amdgpu: Failed to disable gfxoff! [ 3554.505681] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3554.505693] amdgpu 0000:c2:00.0: amdgpu: Failed to disable gfxoff! [ 3559.308523] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3559.308535] amdgpu 0000:c2:00.0: amdgpu: Failed to disable gfxoff! [ 3564.111256] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3564.111268] amdgpu 0000:c2:00.0: amdgpu: Failed to disable gfxoff! [ 3564.111361] amdgpu 0000:c2:00.0: amdgpu: Dumping IP State Completed [ 3564.111451] amdgpu 0000:c2:00.0: amdgpu: [drm] AMDGPU device coredump file has been created [ 3564.111458] amdgpu 0000:c2:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data [ 3564.111461] amdgpu 0000:c2:00.0: amdgpu: ring sdma0 timeout, signaled seq=74533, emitted seq=74537 [ 3564.111465] amdgpu 0000:c2:00.0: amdgpu: GPU reset begin! [ 3568.703656] amdgpu 0000:c2:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 [ 3568.703665] amdgpu 0000:c2:00.0: amdgpu: Failed to disable gfxoff! [ 3687.240764] INFO: task kworker/16:1:46905 blocked for more than 122 seconds. [ 3687.240765] Tainted: G W L 6.17.0-22-generic #22-Ubuntu [ 3687.240765] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3687.240766] task:kworker/16:1 state:D stack:0 pid:46905 tgid:46905 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 3687.240767] Workqueue: events amdgpu_tlb_fence_work [amdgpu] [ 3687.240846] Call Trace: [ 3687.240847] <TASK> [ 3687.240847] __schedule+0x2ed/0x7c0 [ 3687.240848] ? __pick_eevdf+0x150/0x280 [ 3687.240851] schedule+0x27/0x90 [ 3687.240852] schedule_timeout+0xcf/0x110 [ 3687.240853] dma_fence_default_wait+0x1be/0x240 [ 3687.240855] ? __pfx_dma_fence_default_wait_cb+0x10/0x10 [ 3687.240856] dma_fence_wait_timeout+0x13a/0x170 [ 3687.240857] amdgpu_tlb_fence_work+0x2d/0x110 [amdgpu] [ 3687.240941] process_one_work+0x18b/0x370 [ 3687.240942] worker_thread+0x317/0x450 [ 3687.240943] ? __pfx_worker_thread+0x10/0x10 [ 3687.240944] kthread+0x108/0x220 [ 3687.240945] ? __pfx_kthread+0x10/0x10 [ 3687.240946] ret_from_fork+0x131/0x150 [ 3687.240947] ? __pfx_kthread+0x10/0x10 [ 3687.240948] ret_from_fork_asm+0x1a/0x30 [ 3687.240949] </TASK> [ 3710.568331] amdgpu 0000:c2:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE [ 3710.568342] amdgpu 0000:c2:00.0: amdgpu: failed to unmap legacy queue [ 3710.784931] [drm:gfx_v11_0_cp_gfx_enable.isra.0 [amdgpu]] *ERROR* failed to halt cp gfx ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: xserver-xorg-video-amdgpu (not installed) ProcVersionSignature: Ubuntu 6.17.0-22.22-generic 6.17.13 Uname: Linux 6.17.0-22-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 17:49:22 2026 InstallationDate: Installed on 2025-10-10 (189 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148686/+subscriptions

[Bug 2148725] Re: Green screen after KMS on Intel Jasper Lake (Beelink U59) – Kubuntu 26.04 daily

Same model, same firmeware. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148725 Title: Green screen after KMS on Intel Jasper Lake (Beelink U59) – Kubuntu 26.04 daily Status in kwin package in Ubuntu: New Status in linux package in Ubuntu: New Status in plasma-desktop package in Ubuntu: New Bug description: Collected from Kubuntu 26.04 daily live session (booted with nomodeset due to graphics issue). System: Beelink U59 mini PC (Intel Jasper Lake, Intel UHD Graphics) Environment: Kubuntu 26.04 daily build (pre-release) Issue: System boots normally through early kernel messages. After the display switches to higher resolution (KMS activation), the screen turns solid green. Behavior: - Splash screen appears normally - Resolution changes (text becomes very small, likely 4K mode) - Several additional lines print - Screen turns completely green Workarounds tested: - nomodeset → boots successfully (no acceleration) - i915.enable_psr=0 → no change - i915.enable_dc=0 → no change - i915.enable_fbc=0 → no change - combinations of the above → no change This suggests a failure in i915 during KMS initialization. Reproducible: Yes, occurs consistently on every boot without nomodeset. Additional notes: The same Kubuntu 26.04 daily ISO boots and operates normally on another system at 1080p, indicating the issue is specific to this hardware (Beelink U59 / Intel Jasper Lake). System is stable in Windows 11 with 4K video playback, indicating hardware is functioning correctly. Ubuntu 7.0.0-14.14-generic 7.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2148725/+subscriptions

[Bug 2148088] Re: Visual artifacts on GPU usage - Framework Desktop (Strix Halo))

** Tags added: amdgpu -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148088 Title: Visual artifacts on GPU usage - Framework Desktop (Strix Halo)) Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: This is difficult to pin down, but it's pretty easy to reproduce by exercising the GPU. When running an LLM this happens every time it loads the GPU. I can also reproduce it by hovering the mouse over the ubuntu dock icons and moving the mouse. It seems to be more difficult to reproduce it when blacklisting amdxdna, but that could be a bit of stretch. This wasn't a problem with 25.10, only introduced when updating to the devel series a couple of weeks ago. I wasn't able to reproduce this in the live session, so I did a clean install and was able to reproduce it in a clean install. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-13-generic 7.0.0-13.13 ProcVersionSignature: Ubuntu 7.0.0-13.13-generic 7.0.0-rc7 Uname: Linux 7.0.0-13-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.33.1-0ubuntu7 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:53:21 2026 InstallationDate: Installed on 2026-04-11 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260410) MachineType: Framework Desktop (AMD Ryzen AI Max 300 Series) ProcEnviron:  LANG=en_US.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-13-generic root=UUID=61ed6c34-fbfc-4b15-b399-fcebea69dcff ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2025 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMFCP06 dmi.board.vendor: Framework dmi.board.version: A6 dmi.chassis.asset.tag: FRAMDACPA65322007F dmi.chassis.type: 35 dmi.chassis.vendor: Framework dmi.chassis.version: A6 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd11/19/2025:br3.4:svnFramework:pnDesktop(AMDRyzenAIMax300Series):pvrA6:rvnFramework:rnFRANMFCP06:rvrA6:cvnFramework:ct35:cvrA6:skuFRAMDACP06:pfaDesktop: dmi.product.family: Desktop dmi.product.name: Desktop (AMD Ryzen AI Max 300 Series) dmi.product.sku: FRAMDACP06 dmi.product.version: A6 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148088/+subscriptions

[Bug 2148725] Re: Green screen after KMS on Intel Jasper Lake (Beelink U59) – Kubuntu 26.04 daily

Bug Report Update Additional findings after further testing: Hardware Model: Beelink U59 mini PC GPU: Intel Jasper Lake UHD (i915) Systems Compared Two units of the same model were tested: U591 (failing unit) BIOS: JTKT001 Build date: 2022-05-05 Result: Fails to boot live session without nomodeset U592 (working unit) BIOS: JTKT001 Build date: 2022-03-09 Result: Boots live session normally Live USB Testing (Critical Observation) Using the same Kubuntu 26.04 live USB: U591: Hangs after plymouth-quit.service Black or green screen Requires nomodeset to boot (limited to 800×600) U592: Boots to desktop normally i915 loads successfully Full resolution available Cross-Distro Testing Debian live installer: fails on U591 Kubuntu 26.04 live: fails on U591 Kubuntu 26.04 live: works on U592 → Indicates issue is not distro-specific, but likely kernel/i915 related. Installed System Behavior (U591) Boots only with nomodeset Without it: System hangs during graphics initialization Suggests failure occurs during i915 KMS (Kernel Mode Setting) Working Reference System (U592) Running Live installer Kubuntu 26.04 LTS i915 loads successfully Wayland session works Resolution: 2048×1152 Windows Behavior Windows 11 runs normally on both units No display or GPU issues observed → Confirms hardware is functional Summary This appears to be a firmware-dependent i915 initialization issue: Reproducible on one unit (U591) Does not occur on another unit of the same model (U592) Occurs in live environment (not install-specific) Likely triggered during i915 KMS takeover from firmware PS, Congrats to Canonical for 26.04 LTS. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148725 Title: Green screen after KMS on Intel Jasper Lake (Beelink U59) – Kubuntu 26.04 daily Status in kwin package in Ubuntu: New Status in linux package in Ubuntu: New Status in plasma-desktop package in Ubuntu: New Bug description: Collected from Kubuntu 26.04 daily live session (booted with nomodeset due to graphics issue). System: Beelink U59 mini PC (Intel Jasper Lake, Intel UHD Graphics) Environment: Kubuntu 26.04 daily build (pre-release) Issue: System boots normally through early kernel messages. After the display switches to higher resolution (KMS activation), the screen turns solid green. Behavior: - Splash screen appears normally - Resolution changes (text becomes very small, likely 4K mode) - Several additional lines print - Screen turns completely green Workarounds tested: - nomodeset → boots successfully (no acceleration) - i915.enable_psr=0 → no change - i915.enable_dc=0 → no change - i915.enable_fbc=0 → no change - combinations of the above → no change This suggests a failure in i915 during KMS initialization. Reproducible: Yes, occurs consistently on every boot without nomodeset. Additional notes: The same Kubuntu 26.04 daily ISO boots and operates normally on another system at 1080p, indicating the issue is specific to this hardware (Beelink U59 / Intel Jasper Lake). System is stable in Windows 11 with 4K video playback, indicating hardware is functioning correctly. Ubuntu 7.0.0-14.14-generic 7.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2148725/+subscriptions

[Bug 2144522] Re: Dell Machines cannot boot into OS with 6.17.0-1012-oem

This bug is awaiting verification that the linux/6.17.0-23.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-questing-linux' to 'verification-done-questing- linux'. If the problem still exists, change the tag 'verification- needed-questing-linux' to 'verification-failed-questing-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-questing-linux-v2 verification-needed-questing-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2144522 Title: Dell Machines cannot boot into OS with 6.17.0-1012-oem Status in linux package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: In Progress Status in linux-oem-6.17 source package in Questing: Invalid Bug description: [Impact] Dell systems (CID: 202506-36819, 202506-36820, 202506-36823, 202506-36826) with AMD GFX 11.0.4 (gfx11) graphics cannot boot into the OS after upgrading to 6.17.0-1012-oem. The machine becomes stuck during boot and cannot reach the desktop. Booting with `nomodeset` works as a workaround, pointing to an amdgpu driver initialization failure. Failure rate: 4/4 (100%) on affected Dell systems. [Fix] Two patches fix this boot regression: 1. Raise the minimum MES firmware version for calling set_hw_resources_1 on GC 11.0.4 from 0x50 to 0x52, ensuring firmware that cannot properly initialize this call is not used. upstream in mainline kernel v7.0: 1478a34470bf drm/amd: Set minimum version for set_hw_resource_1 on gfx11 to 0x52 2. Remove the MES LR compute workaround (enable_lr_compute_wa) from both mes_v11_0.c and mes_v12_0.c, since the underlying issue was already fixed by adjusting the VGPR size, and keeping the workaround causes instability with newer GC microcode. upstream in mainline kernel v7.0: 6b0d812971370 drm/amd: Disable MES LR compute W/A [Test Plan] Boot the affected machine with kernel 6.17.0-1012-oem (or later oem kernel). Without the patches: System gets stuck during boot and cannot reach the OS (amdgpu fails to initialize). With the patches: System boots normally to the desktop without requiring `nomodeset`. To verify: 1. Boot without `nomodeset` 2. Check that the desktop loads successfully 3. Confirm no amdgpu-related errors blocking boot in dmesg: $ sudo dmesg | grep -i "amdgpu\|mes\|drm" [Where problems could occur] These changes affect the amdgpu MES initialization path for gfx11 (mes_v11_0.c) and gfx12 (mes_v12_0.c) hardware. For patch 1: If the version threshold 0x52 is incorrect, machines with MES firmware between 0x50 and 0x51 that previously worked could stop calling set_hw_resources_1, potentially causing degraded GPU performance or missing hardware resource configuration. This would manifest as graphical glitches, GPU compute failures, or silent capability loss after MES initialization. For patch 2: If the LR compute workaround was actually needed for some gfx11/gfx12 product beyond gfx1151, removing it could cause GPU hangs or compute workload failures on those variants. Symptoms would include GPU hangs, DRM timeout errors, or compute job failures under load. [Other Info] Both patches are upstream in Linux 7.0 (merged via drm-next-2026-02-11). ================================================================= [Summary] Several Dell Machines failed to boot into OS on 6.17.0-1012-oem. [Reproduce Steps] 1. Install the GM image (6.11). 2. Run the dist-upgrade to 6.17 3. sudo reboot On 6.11, the machine can boot into OS after reboot. However, after upgrading to 6.17, it becomes stuck during boot and cannot reach the OS. However, if root is modified to nomodeset in 6.17, the machine can boot into the OS successfully. [Affected Machines] https://certification.canonical.com/hardware/202506-36819/ https://certification.canonical.com/hardware/202506-36820/ https://certification.canonical.com/hardware/202506-36823/ https://certification.canonical.com/hardware/202506-36826/ [Failed Rate] 4/4 (100%) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.17.0-1012-oem 6.17.0-1012.12 ProcVersionSignature: Ubuntu 6.17.0-1012.12-oem 6.17.9 Uname: Linux 6.17.0-1012-oem x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: ubuntu 1271 F.... wireplumber  /dev/snd/controlC0: ubuntu 1271 F.... wireplumber  /dev/snd/seq: ubuntu 1266 F.... pipewire CRDA: N/A CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Mon Mar 16 03:28:36 2026 DistributionChannelDescriptor:  # This is the distribution channel descriptor for Ubuntu 24.04 for Dell  # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor  canonical-oem-somerville-noble-oem-24.04b-proposed-20250617-524 InstallationDate: Installed on 2026-03-16 (0 days ago) InstallationMedia: Ubuntu OEM 24.04.2 LTS "Noble Numbat" - Release amd64 (20250615) MachineType: Dell Inc. Dell 16 DC16255 ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1012-oem root=UUID=d1b47013-8d11-47bc-9f6a-8046300ab97d ro nomodeset quiet splash vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-6.17.0-1012-oem N/A  linux-backports-modules-6.17.0-1012-oem N/A  linux-firmware 20240318.git3b128b60-0ubuntu2.25 SourcePackage: linux-oem-6.17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2025 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.10 dmi.board.asset.tag: AFTPASS dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: AFTPASS dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.4.10 dmi.modalias: dmi:bvnDellInc.:bvr0.4.10:bd06/18/2025:br5.3:svnDellInc.:pnDell16DC16255:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr0.4.10:sku0D95: dmi.product.family: Inspiron dmi.product.name: Dell 16 DC16255 dmi.product.sku: 0D95 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144522/+subscriptions