I might find the root cause. It's not from linux-firmware, but from
upstream stable update patch which is included in 6.14.0-17.17.

Here is the test kernel, you need to disable secure boot from BIOS to boot from 
it.
https://people.canonical.com/~acelan/bugs/lp2115860/
Please try and see if it also works for you, thanks.

commit 21a0fc2c7458c7a28100b69f612df779c4efb20f
Author: Paul E. McKenney <[email protected]>
Date:   Tue Feb 25 10:33:28 2025 -0800

    Flush console log from kernel_power_off()
    
    BugLink: https://bugs.launchpad.net/bugs/2108854
    
    [ Upstream commit 6ea9a1781c70a8be1fcdc49134fc1bf4baba8bca ]
    
    Kernels built with CONFIG_PREEMPT_RT=y can lose significant console output
    and shutdown time, which hides shutdown-time RCU issues from rcutorture.
    Therefore, make pr_flush() public and invoke it after then last print
    in kernel_power_off().
    
    [ paulmck: Apply John Ogness feedback. ]
    [ paulmck: Appy Sebastian Andrzej Siewior feedback. ]
    [ paulmck: Apply kernel test robot feedback. ]
    
    Signed-off-by: Paul E. McKenney <[email protected]>
    Reviewed-by: John Ogness <[email protected]>
    Reviewed-by: Petr Mladek <[email protected]>
    Cc: Steven Rostedt <[email protected]>
    Cc: Sergey Senozhatsky <[email protected]>
    Link: 
https://lore.kernel.org/r/5f743488-dc2a-4f19-bdda-cf50b9314832@paulmck-laptop
    Signed-off-by: Boqun Feng <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>
    Signed-off-by: Manuel Diewald <[email protected]>
    Signed-off-by: Stefan Bader <[email protected]>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2115860

Title:
  poweroff not working after upgrading linux-firmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2115860/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to