The term you're looking for is workaround, not triage or fixes. Triage
is the process of understanding the bug and marking it the correct
things.
Not using the same language as everyone else and writing very long
comments makes it hard to understand.
First I thought you reported an out of memory
Public bug reported:
[Impact]
The Bluetooth connection cannot be established between two Ubuntu 22.04 systems
with Realtek 8821.
[Fix]
Use the updated firmware for rtl8821c to fix issue.
[Test]
1. Prepare two Ubuntu 22.04 systems with Realtek 8821.
2. Open Bluetooth Settings and launch
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1989334
Title:
remove circular dep between
** Tags added: kern-5200
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1999375
Title:
Update dg2_dmc to 2.08
Status in linux-firmware package in Ubuntu:
Fix Released
Status
** Tags added: kern-5201
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1999406
Title:
Update firmware for hwe kernel migration
Status in linux-firmware package in Ubuntu:
Verified with 5.17.0-1025-oem and 6.0.0-1009, tried reboot 3 times with
each kernel, the audio output is normal.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is
Verified with 5.17.0-1025-oem and 5.19.0-27 kernel, confirmed the issue
could not be reproduced on the reported machine.
** Tags removed: verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-jammy verification-done-kinetic
--
You received this bug notification
I am facing same issue On Ubuntu 22.04, the web camera does not work.
anyone please give me solution whati have to do
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1978881
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,
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,
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,
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,
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,
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
All autopkgtests for the newly accepted linux-meta-oem-6.0 (6.0.0.1009.9) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
backport-iwlwifi-dkms/9858-0ubuntu3.1 (amd64)
systemd/249.11-0ubuntu3.6 (amd64)
Please visit the excuses
Hi juliank, I understand completely you want me to have insights related
to verification of the update in lunar-proposed and that I am confusing
you with my #131 post.
I was mentioning that to help people who need the triage, since it is
not possible to say locked out nor without updates until
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1992266
Title:
input/keyboard: the keyboard on some Asus
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996121
Title:
alsa: soc: the kernel print UBSAN
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912935
Title:
battery drain while notebook off / shutdown
Status in linux
@thedoctar Add it to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub
file.
$ sudo dmesg | grep "Command line"
[0.00] Command line: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic
root=/dev/mapper/vgubuntu-root ro quiet splash intel_pstate=passive
eisa_bus.disable_dev=1,2,3,4,5,6,7,8 vt.handoff=7
Turns out my issue was a faulty drive, and the system would lock up when
mdadm hit the bad sectors on resync. The issue seemed like it was lower
in the blockdev code causing a deadlock.
I replaced the drive and the problem went away.
--
You received this bug notification because you are a
Thanks, Don... sorry to ask but to make this easier on me (I'm the one who has
to find the time do do this) could you revise the list in the summary with all
the desired patches (including the ones from the 6.2 MKP tree) in pick order?
DON> Sure.
And just to be sure, they all cleanly pick with
This bug was fixed in the package linux-azure - 5.15.0-1029.36
---
linux-azure (5.15.0-1029.36) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1029.36 -proposed tracker (LP: #1998845)
* Azure: Jammy fio test hangs, swiotlb buffers exhausted (LP: #1998838)
- SAUCE: scsi:
Hi Daniel,
I replaced the DP cable. After inserting the cable, the full resolution was
immediately back available. However, the problem/bug still remains: after a
suspend, the screen only gives a poor resolution and the full resolution is not
available. After a reboot, the full resolution is
Hi ybdjkfd I don't really understand what you are doing and how it's
relevant. This issue should be fixed in lunar-proposed 2.06-2ubuntu16,
please only add comments if you have meaningful insights regarding the
verification of that update.
--
You received this bug notification because you are a
What happened here is that we dropped the 510 driver in lrm
5.4.0-135.152+1, transitioning it to the 515 driver. It therefore did
not produce a 5.4.0-135.152+1 version of linux-modules-
nvidia-510-server-5.4.0-135-generic. Ubuntu always keeps the latest
version of a binary package in the archive,
Bringing one the original triage fixes I posted in #41 and #45 after
gathering some information on changes to grub2 for Raspberry Pi that
exposed this issue (i.e., I know the fix to get things to boot), after
upgrading to 22.10, I now have an updated set of events on a specific
kernel.
I still
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8
---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8
---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8
---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8
---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8
---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8
---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8
---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8
---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8
---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8
---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8
---
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912935
Title:
battery drain while notebook off / shutdown
Status in linux
No, my BIOS version is K5CN34WW
Do you have exactly the same computer model (Yoga 7 14ARB7)?
Do you have exactly the same Lenovo TB Dock?
12.12.2022 19:05:22 Steven Hong <1998...@bugs.launchpad.net>:
> I have same issue like u. did you update your bios?
> I have same issue after updating my
I have same issue like u. did you update your bios?
I have same issue after updating my BIOS.
Used so well until bios updates.
The bios Code is : JVEC31WW
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thank you for your reply to my comment #3. Your English is good enough
foe me.
Unfortunately Ubuntu has never had enough users, volunteers or
developers that have had the time to respond to bug reports in a timely
manner.
I'm closing this as 'Invalid' which doesn't mean that your initial
report
All autopkgtests for the newly accepted linux-meta-nvidia (5.15.0.1011.11) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-nvidia/5.15.0-1011.11 (amd64)
Please visit the excuses page listed below and investigate the
I don't use Ubuntu anymore, i did not have no answer and helping solution
at this moment, too Bad cause i like using Ubuntu but so disapointed !
Thanks for this answer anyway, a little bit late.(Hope my english is
correct)
Cordialement
Le lun. 12 déc. 2022 à 15:16, Paul White
Thanks, Don... sorry to ask but to make this easier on me (I'm the one
who has to find the time do do this) could you revise the list in the
summary with all the desired patches (including the ones from the 6.2
MKP tree) in pick order?
And just to be sure, they all cleanly pick with no missing
Hi,
I found a workaround to this problem. I solved the problem by installing new
packages:
"sudo apt install linux-modules-nvidia-390-5.15.0-56-generic"
where:
- "390" is the main version of the Nvidia driver (390.157);
- "5.15.0-56-generic" is the name of the kernel ("uname -r" output).
This
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635411/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635415/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635413/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635416/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635412/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635414/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635410/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635408/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635409/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635407/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635406/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635404/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999387
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635405/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635403/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635401/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635402/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999387
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635400/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected una
** Description changed:
Bluetooth-app crashes when i try to active bluetooth inside the application.
Using app: "blueman-manager".
Last kernel working: 5.4.0-132
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.25
+
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1999387/+attachment/5635399/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999387
Public bug reported:
TBD.
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1999406
Title:
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1995041
Title:
Fix ath11k deadlock on WCN6855
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1980621
Title:
Fix blank screen on Thinkpad ADL
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999387
Title:
Bluetooth crashes on kernel 5.4.0-135
Status in
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1999396
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: zfs-linux (Ubuntu Focal)
Assignee: Heitor Alves de Siqueira (halves) => Ghadi Rahme (ghadi-rahme)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964992
Title:
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Do you still see a problem
Here it is:
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor= Product=0001 Version=
N:
Public bug reported:
At the moment fallback pnvm firmware files exists, but are undeclared.
Ensure that if ucode for such devices is copied, that pnvm files are
copied too.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
The "Kinetic Ubuntu 22.10" version is also affected.
Backport from fix from comment #33 above? (
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/comments/33
)
Please someone who has permission could you please add Kinect as
affected and backport the fix? (google translated)
$
--- Comment From sig...@de.ibm.com 2022-12-12 08:36 EDT---
still fine with latest updates:
# uname -a
Linux a83lp78.lnxne.boe 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:57:26
UTC 2022 s390x s390x s390x GNU/Linux
# grep qcrdinfo /sys/kernel/debug/s390dbf/qeth*/hex_ascii | wc -l
0
#
2022-12-12 13:37:30.762 :: 2022-12-12 13:36:02.048 :: +
/root/parts/kernel/src/trim-firmware /root/parts/kernel/install/lib
2022-12-12 13:37:30.762 :: 2022-12-12 13:36:13.710 :: Overriding
iwlwifi-so-a0-gf-a0-66.ucode with iwlwifi-so-a0-gf-a0-64.ucode
2022-12-12 13:37:30.762 :: 2022-12-12
** Tags added: verification-done-jammy
** Tags removed: verification-needed-focal verification-needed-jammy
verification-needed-kinetic
** Tags added: verification-done-focal verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is
This bug was not opened against linux-nvidia/5.15.0-1011.11 and is also not
relevant for this kernel.
However, I'm setting the tag to done to unblock the process.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you
This bug was not opened against linux-nvidia/5.15.0-1011.11 and is also not
relevant for this kernel.
However, I'm setting the tag to done to unblock the process.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-bluefield (Ubuntu
Kernel panic message snippet from the log attachment
papat-221211-reboot_mainline-6.0.9-060009-generic_kernel-panic.log:
[ 835.504178] [ cut here ]
[ 835.504183] kernel BUG at kernel/irq_work.c:235!
[ 835.504184] Internal error: Oops - BUG: 0 [#1] SMP
[ 835.504186]
I rebooted the system with mainline kernel v6.0.9, and I can similar
kernel panic at 302th reboot. See the log attachment
papat-221211-reboot_mainline-6.0.9-060009-generic_kernel-panic.log for
the kernel panic message.
** Attachment added:
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
No worries, thank you for the patience, Robie!
With further testing, we've found out that there's an additional upstream
patch required for Focal, which fixes the "inversion" when setting the ARC
limits.
I'll amend the description and re-spin this SRU to include the proper
fixes. I'll then
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11
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
1 - 100 of 124 matches
Mail list logo
