This bug is awaiting verification that the linux-
riscv-6.5/6.5.0-45.45.1~22.04.1 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-linux-
riscv-6.5' to
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
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-fips' to 'verification-done-noble-
linux-fips'. If
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1023.23~22.04.1 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-linux-
aws-6.5' to
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-44.44.1~22.04.1 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-linux-
lowlatency-hwe-6.5' to
This bug is awaiting verification that the linux-
oracle-6.5/6.5.0-1026.26~22.04.1 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-linux-
oracle-6.5' to
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-38.38.1~22.04.1 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-linux-
riscv-6.8' to
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux-firmware (Ubuntu Mantic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug is awaiting verification that the linux-oracle/6.8.0-1008.8
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-oracle' to 'verification-done-
noble-linux-oracle'. If
This bug is awaiting verification that the linux-riscv/6.8.0-38.38.1
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-riscv' to 'verification-done-noble-
linux-riscv'. If
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1009.9~22.04.1 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-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~22.04.1 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-linux-
aws-6.8' to
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.1
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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
This bug is awaiting verification that the linux-
lowlatency/6.5.0-44.44.1 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-mantic-linux-lowlatency' to
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1008.8~22.04.1 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-linux-
ibm-6.8' to
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2006.6 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-raspi-realtime'
to
This bug is awaiting verification that the linux-
gcp-6.5/6.5.0-1024.26~22.04.1 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-linux-
gcp-6.5' to
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-38.38.1~22.04.2 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-linux-
lowlatency-hwe-6.8' to
This bug is awaiting verification that the linux-
azure-6.8/6.8.0-1010.10~22.04.1 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-linux-
azure-6.8' to
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-44.44~22.04.1 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-linux-
hwe-6.5' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1023.24 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-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-oracle/6.5.0-1026.26
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-mantic-linux-oracle' to 'verification-done-
mantic-linux-oracle'.
This bug is awaiting verification that the linux-laptop/6.5.0-1019.22
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-mantic-linux-laptop' to 'verification-done-
mantic-linux-laptop'.
This bug is awaiting verification that the linux-azure/6.5.0-1024.25
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-aws/6.5.0-1023.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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-
hwe-6.8/6.8.0-38.38~22.04.1 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-linux-
hwe-6.8' to
This bug is awaiting verification that the linux-nvidia/6.8.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-noble-linux-nvidia' to 'verification-done-
noble-linux-nvidia'. If
This bug is awaiting verification that the linux-ibm/6.8.0-1008.8 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-ibm' to 'verification-done-noble-linux-
ibm'. If the
This bug is awaiting verification that the linux-gke/6.8.0-1006.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-noble-linux-gke' to 'verification-done-noble-linux-
gke'. If the
This bug was fixed in the package linux - 6.8.0-38.38
---
linux (6.8.0-38.38) noble; urgency=medium
* noble/linux: 6.8.0-38.38 -proposed tracker (LP: #2068318)
* race_sched in ubuntu_stress_smoke_test will cause kernel panic on 6.8 with
Azure Standard_A2_v2 instance (LP:
This bug was fixed in the package linux-oem-6.8 - 6.8.0-1008.8
---
linux-oem-6.8 (6.8.0-1008.8) noble; urgency=medium
* noble/linux-oem-6.8: 6.8.0-1008.8 -proposed tracker (LP: #2068307)
* failed to enable IPU6 camera sensor on kernel >= 6.8: ivsc_ace
This bug was fixed in the package linux - 6.5.0-44.44
---
linux (6.5.0-44.44) mantic; urgency=medium
* mantic/linux: 6.5.0-44.44 -proposed tracker (LP: #2068341)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
This bug is awaiting verification that the linux-nvidia-
lowlatency/6.8.0-1009.9.1 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-nvidia-
lowlatency' to
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.31
---
linux-firmware (20220329.git681281e4-0ubuntu3.31) jammy; urgency=medium
* Fix the RTL8852CE BT FW Crash based on SER false alarm (LP: #2060904)
- rtw89: 8852c: update fw to v0.27.56.14
*
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.1
---
linux-firmware (20240318.git3b128b60-0ubuntu2.1) noble; urgency=medium
* Fix the RTL8852CE BT FW Crash based on SER false alarm (LP: #2060904)
- rtw89: 8852c: update fw to v0.27.56.14
* Add
This bug is awaiting verification that the linux/6.8.0-38.38 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' to 'verification-done-noble-linux'. If
the problem still
This bug is awaiting verification that the linux/6.5.0-44.44 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
I removed verification-done-jammy-linux-oem-6.5, I already verified the
SRU with the jammy and noble, and the tag has been added accordingly.
** Tags removed: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
JFYI verification-done-jammy-linux-oem-6.5 is not a verification tag
that any of our SRU tooling accepts. The bugs will still appear as
unverified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Jammy)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1023.24
---
linux-oem-6.5 (6.5.0-1023.24) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1023.24 -proposed tracker (LP: #2063580)
* Add support for Quectel RM520N-GL modem [1eac:1007] (LP: #2063529)
- bus: mhi:
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060904
Title:
Fix the RTL8852CE BT FW
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1023.24
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-linux-oem-6.5' to 'verification-done-
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-oem-6.8 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
About the #3, the so-called regression has nothing to do with this SRU:
For arm64:
682s : failure: setup script failed with code 1:
/home/ubuntu/autopkgtest/ssh-setup/nova open --flavor autopkgtest-big
--security-groups ...
For armhf:
345s Error: Failed to fetch instance
Hello Hui, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.31 in a few hours, and then in
the -proposed repository.
Please help us by testing
Hello Hui, or anyone else affected,
Accepted linux-firmware into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20240318.git3b128b60-0ubuntu2.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
** Tags added: kern-10584
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060904
Title:
Fix the RTL8852CE BT FW Crash based on SER false alarm
To manage notifications about this bug go to:
** Description changed:
+ This is SRU template for linux kernel:
+
+ [Impact]
+
+ On a Dell laptop, let it connect to a WiFi router, connect a BT
+ device, then disconnect it, connect the bt device again, we expect
+ the device could be connected successfully, but it couldn't and
+ the BT
** Changed in: linux-firmware (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux-firmware (Ubuntu Mantic)
** Description changed:
- This bug is for tracking purpose
+ This SRU template is for linux-firmware:
+
+ BugLink: https://bugs.launchpad.net/bugs/2060904
+
+ [Impact]
+
+ On a Dell laptop, let it connect to a WiFi router, connect a BT
+ device, then disconnect it, connect the bt device again,
52 matches
Mail list logo
