HWE Next

Fix System cannot detect bluetooth after running suspend stress test

Bug #1998727 reported by koba
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HWE Next
New
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Undecided
koba
Jammy
In Progress
Medium
koba
Kinetic
Won't Fix
Medium
koba
Lunar
Fix Released
Undecided
koba
linux-oem-6.0 (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Undecided
koba
Kinetic
Invalid
Undecided
Unassigned
Lunar
Invalid
Undecided
Unassigned

Bug Description

[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.

See original description
koba (kobako)
Changed in linux (Ubuntu Kinetic):
status: New → In Progress
assignee: nobody → koba (kobako)
Changed in linux (Ubuntu Lunar):
status: New → In Progress
assignee: nobody → koba (kobako)
Changed in linux (Ubuntu Jammy):
status: New → In Progress
assignee: nobody → koba (kobako)
Changed in linux-oem-6.0 (Ubuntu Jammy):
status: New → In Progress
assignee: nobody → koba (kobako)
tags: added: oem-priority originate-from-1993095 somerville
description: updated
description: updated
Stefan Bader (smb)
Changed in linux (Ubuntu Kinetic):
importance: Undecided → Medium
Changed in linux (Ubuntu Jammy):
importance: Undecided → Medium
Revision history for this message
koba (kobako) wrote :

Sent V2 for U/J/K.
Add build summary
https://lists.ubuntu.com/archives/kernel-team/2022-December/135478.html

Timo Aaltonen (tjaalton)
Changed in linux-oem-6.0 (Ubuntu Kinetic):
status: New → Invalid
Changed in linux-oem-6.0 (Ubuntu Lunar):
status: New → Invalid
Timo Aaltonen (tjaalton)
Changed in linux-oem-6.0 (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-oem-6.0/6.0.0-1009.9 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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-jammy-linux-oem-6.0 verification-needed-jammy
Revision history for this message
koba (kobako) wrote :

Upgrade to linux-oem-6.0-1009 and didn't reproduce with 600 times.
@Ian, thanks

tags: added: verification-done-jammy
removed: verification-needed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1009.9

---------------
linux-oem-6.0 (6.0.0-1009.9) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1009.9 -proposed tracker (LP: #1999041)

  * Support Intel IPU6 MIPI camera (LP: #1987595)
    - debian/dkms-versions -- manual update for IPU6/IVSC.

  * Gnome doesn't run smooth when performing normal usage with RPL-P CPU
    (LP: #1998419)
    - drm/i915/rpl-p: Add stepping info

  * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115)
    - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled

  * Fix System cannot detect bluetooth after running suspend stress test
    (LP: #1998727)
    - wifi: rtw88: 8821c: enable BT device recovery mechanism

  * Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
    (LP: #1998905)
    - SAUCE: ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.

 -- Timo Aaltonen <email address hidden> Wed, 07 Dec 2022 20:00:55 +0200

Changed in linux-oem-6.0 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1004.4 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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-jammy-linux-oem-6.1 verification-needed-jammy
removed: verification-done-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.1.0-16.16

---------------
linux (6.1.0-16.16) lunar; urgency=medium

  * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- temporarily drop broken dkms

 -- Andrea Righi <email address hidden> Fri, 24 Feb 2023 14:24:48 +0100

Changed in linux (Ubuntu Lunar):
status: In Progress → Fix Released
Revision history for this message
Utkarsh Gupta (utkarsh) wrote :

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release.

Changed in linux (Ubuntu Kinetic):
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.