NACK[K/J]: [PATCH 0/1][SRU][U/K/J/OEM-6.0] Fix System cannot detect bluetooth after running suspend stress test

[Stefan Bader]

On 05.12.22 18:03, Koba Ko wrote:
> On Mon, Dec 5, 2022 at 9:27 PM Stefan Bader <stefan.bader at canonical.com 
> <mailto:stefan.bader at canonical.com>> wrote:
> 
>     On 05.12.22 03:06, Koba Ko wrote:
>      > BugLink: https://bugs.launchpad.net/bugs/1998727
>     <https://bugs.launchpad.net/bugs/1998727>
>      >
>      > [Impact]
>      >   System cannot detect bluetooth after running
>     power-management/suspend-30-cycles-with-reboots
>      >
>      > [Fix]
>      >   Enable BT recovery on Realtek 8852CE FW, FW would detect and recover.
>      >
>      > [Test Case]
>      > 1. checkbox-cli run
>     com.canonical.certification::power-management/suspend_30_cycles_with_reboots
>      > 2. check settings > bluetooth
>      >
>      > [Where problems could occur]
>      > just enable a function from kernel and run the code in the fw.
>      > the main risk would be related to FW.
>      >
>      > Ping-Ke Shih (1):
>      >    [U/K/J/OEM-6.0] wifi: rtw88: 8821c: enable BT device recovery mechanism
>      >
>      >   drivers/net/wireless/realtek/rtw88/fw.c  | 10 ++++++++++
>      >   drivers/net/wireless/realtek/rtw88/fw.h  |  6 ++++++
>      >   drivers/net/wireless/realtek/rtw88/mac.c | 18 +++++++++++++++++-
>      >   3 files changed, 33 insertions(+), 1 deletion(-)
>      >
> 
>     I see no indication that this has been tested to build/work with Kinetic/Jammy.
>     After recent incidents with code breaking the build in distro kernels I would
>     expect at least the build summary.
>     But also one cycle in the OEM kernel before pulling things into the distro
>     kernels would be better.
> 
> I will provide the build summary after.
> It's  nice to be in SRU.

Please submit as a v2 thread for K/J. I probably should not have NACKed 
immediately but now that its there it would become confusing with taking that back.

-Stefan

> * Kinetic build
> remote: *** kernel-cbd *********************************************************
> remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt
> remote: * For results:  ssh cbd ls kobako-kinetic-93113911c2fe-eQys
> remote: * 480/960 cores busy (5/10 hosts), 0 builds queued
> remote: 2022-12-05 16:27:42  kobako-kinetic-93113911c2fe-eQys/amd64/BUILD-OK
> remote: 2022-12-05 16:30:36  kobako-kinetic-93113911c2fe-eQys/arm64/BUILD-OK
> remote: 2022-12-05 16:24:03  kobako-kinetic-93113911c2fe-eQys/armhf/BUILD-OK
> remote: 2022-12-05 16:28:56  kobako-kinetic-93113911c2fe-eQys/ppc64el/BUILD-OK
> remote: 2022-12-05 16:23:04  kobako-kinetic-93113911c2fe-eQys/s390x/BUILD-OK
> remote: 2022-12-05 16:38:16  kobako-kinetic-93113911c2fe-e7lc/riscv64/BUILD-FAILED
> remote: ************************************************************************
> * Jammy build
> remote: *** kernel-cbd *********************************************************
> remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt
> remote: * For results:  ssh cbd ls kobako-jammy-0456a95c8835-UE46
> remote: * 0/864 cores busy (0/9 hosts), 0 builds queued
> remote: 2022-12-05 16:58:04  kobako-jammy-0456a95c8835-UE46/amd64/BUILD-OK
> remote: 2022-12-05 16:56:40  kobako-jammy-0456a95c8835-UE46/arm64/BUILD-OK
> remote: 2022-12-05 16:53:17  kobako-jammy-0456a95c8835-UE46/armhf/BUILD-OK
> remote: 2022-12-05 16:55:31  kobako-jammy-0456a95c8835-UE46/ppc64el/BUILD-OK
> remote: 2022-12-05 16:51:10  kobako-jammy-0456a95c8835-UE46/s390x/BUILD-OK
> remote: ************************************************************************
> 
> 
>     -Stefan
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20221206/e69b94f5/attachment.sig>