Judging by the bug reports, this seems to have stopped happening in
24.04 and later(?)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: mutter (Ubuntu)
Status: Triaged => Incomplete
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Incomple
Hi Ubuntu Kernel Team
I have added the proposed source to my sources.list: deb
http://archive.ubuntu.com/ubuntu/ noble-proposed restricted main
multiverse universe.
However, I did not find any related content for linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1. What should I do next?
Thanks，
Dong
--
You
Public bug reported:
Placeholder for backporting required fixes for Lunar Lake graphics.
** Affects: linux-oem-6.10 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.10 i
When do we get this new kernel? It seems to solve the problem.
--
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/2068738
Title:
AMD GPUs fail with null pointer dereference when IOMMU enable
Hi Philip,
The crash was happening on u-12tb1.112xlarge instances (448 cores, 12TB
RAM), and would happen once very few hours on average when the system
was busy.
Our systems worked fine for months after the upgrade to 24.04. Then we
started experiencing (different) crashes with the now retracted
The latest version in mantic-updates is (should be) 6.5.0-44.44 but the
riscv64 package set seems to be incomplete. Hm.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/2076170
Title:
List of firmware files wanted by the 6.8 kernel but not in jammy linux-
firmware:
cs42l43.bin
amd/amd_sev_fam19h_model1xh.sbin
amdgpu/aldebaran_sjt_mec.bin
amdgpu/aldebaran_sjt_mec2.bin
amdgpu/dcn_3_5_dmcub.bin
amdgpu/gc_11_0_0_rlc_1.bin
amdgpu/gc_11_5_0_imu.bin
amdgpu/gc_11_5_0_me.bin
amdgpu/gc_1
Performing verification for Jammy.
I deployed a fresh baremetal server running Jammy in the Server Lab, installed
ubuntu-desktop and rebooted.
The kernel is 5.15.0-117-generic from updates:
5.15.0-117-generic #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024
$ sudo apt-cache policy virtualbox
virtualb
** Summary changed:
- Virtualbox fails when starting a VM
+ Virtualbox fails when starting a VM with kernel 5.15.0-116/117
--
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/2076201
Title:
** Description changed:
With kernel 5.15.0-107 it works.
I tested with 116 and 117. On both kernels all VMs starts fails with:
ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005)
aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap}
aText={The console is not powered up (setVid
** Attachment added: "Win11_64bit-2024-08-07-03-01-34.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076201/+attachment/5803265/+files/Win11_64bit-2024-08-07-03-01-34.log
** Description changed:
With kernel 5.15.0-107 it works.
I tested with 116 and 117. On both kernels all VM
Please try my .38 here.
https://people.canonical.com/~mschiu77/lp2073676/
--
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/2073676
Title:
after update of kernel HDMI audio is not working
** Description changed:
With kernel 5.15.0-107 it works.
- I tested with 116 and 117. On both kernels the VMs start fails with:
+ I tested with 116 and 117. On both kernels all VMs starts fails with:
ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005)
aIID={4680b2de-8690-11e9-b83d-5719e53cf1de}
Public bug reported:
With kernel 5.15.0-107 it works.
I tested with 116 and 117. On both kernels the VMs start fails with:
ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005)
aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap}
aText={The console is not powered up (setVideoModeHint)}, pr
Thanks. If the OSD doesn't show decimal places in "60Hz" then it doesn't
prove anything.
Since this seems to be fundamentally a signal synchronization problem I
can only recommend installing an official Nvidia graphics driver.
According the the Nvidia website, your GeForce GTX 1660 SUPER should be
*** This bug is a duplicate of bug 2064595 ***
https://bugs.launchpad.net/bugs/2064595
Great to hear it! Everyone else, hold tight, 6.8.0-40-generic will be
released soon.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
*** This bug is a duplicate of bug 2064595 ***
https://bugs.launchpad.net/bugs/2064595
Hi,
I have installed 6.8.0-40-generic, and it appears to have resolved the
issue. Thank you.
For the technically challenged like myself who are reading, here is how
I installed it:
sudo nano /etc/apt/sour
*** This bug is a duplicate of bug 2064595 ***
https://bugs.launchpad.net/bugs/2064595
I think this is going to be fixed in 6.8.0-40-generic, currently in
-proposed. You could try install it now and see if it fixes your issue.
Let me know if it doesn't.
** This bug has been marked a duplicate
** Changed in: linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: Fix Committed
** Changed in: linux (Ubuntu Oracular)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Jammy)
Yes, I am confirming that I downloaded the 24.04 LTS iso from the
website, imaged it to a USB, and booted from it. When booting from the
USB, the ubuntu installer opens by default. I closed the installer,
which drops you into the live USB Ubuntu environment.
I clicked suspend from the power menu i
Public bug reported:
Since commit 92550b568d, the perf build for Ubuntu kernels does not link
to libtraceevent, and thus cannot perform any operations on tracepoints,
including processing perf.data files that contain tracepoint events.
This is a significant loss of functionality.
Attempts to util
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
This bug is awaiting verification that the linux-ibm-gt-
tdx/6.8.0-1009.10+tdx1 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-gt-tdx' to
'verification-done-noble-linu
Is there a reason why a fix has not yet been committed for focal (Ubuntu
20.04), which is likewise affected..?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Virtu
AceLan Kao,
Going the HP support route we all know will be extremely painful, if, I
can convince their support to forward my query along to the right people.
Is there no method to debug or expose the reason for the failed PPM init and/or
what the GPE17 triggers are called from?
I am assumin
I think that has been tried, as described in the first post: “I have run
Ubuntu from a Live USB on the same machine, and when suspending, all
appears to work OK.” :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
This bug is awaiting verification that the linux/5.15.0-119.129 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' to 'verification-done-jammy-linux'. If
the problem still ex
Using 5.15.0-1050.52.21.gf22d8b5-bluefield after reboot and power cycle
test on both BF2 and BF3, oob_net0 interface is up, IP is assigned, and
there were no RX errors.
** Tags removed: verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy-linux-bluefield
--
You receiv
Thank you for taking the time to report this bug.
Would you be able to boot off of the Noble (24.04) USB install media,
and select the "Try Ubuntu", and see if it reproduces with the kernel
that is on the install media? I would like to know if this is a
regression from when Noble originally shipp
This fix will be available in Noble in Ubuntu-xilinx-6.8.0-1006.7
** Description changed:
[ Impact ]
* Backports support for rs485 to the uartps driver from the tty staging
tree
[ Test Plan ]
* Testing is needed to ensure this doesn't break the serial console on
current platforms
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-xilinx-zynqmp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu.
https://bugs.
@Portia - DT update is required: https://github.com/Xilinx/linux-
xlnx/commit/6472141dd7401ff43fc0fbb3dbc253454c5be2ee
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu.
https://bugs.launchpad.net/bugs/2055237
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2075137
Title:
testptp send timestam
The Samsung SyncMaster 2233 does have a menu button that leads to an
information panel which reports:
64.6kHz
60Hz
PN
1680x1050
Alas, 'Adjust for TV' broke everything. I had to Alt + SysRq + REISUB,
and reboot into recovery mode. Remounted the file system for read/write
and removed ~/.config/moni
Public bug reported:
TBW
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status:
That's right, it was a fix for a Virtualbox error that arose when kernel stack
randomization was first introduced in the 5.13 kernel.
My speculation was that it might have been a similar issue, and if so, its fix
might give a clue to a way to fix the current issue in Virtualbox.
One might naivel
Hi, i encounter that issue again in Supermicro AS-2015CS-TNR
Will try to get more information
** Changed in: maas
Status: Expired => Incomplete
** Changed in: linux (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Kernel
Pac
okay - where do you want me to download the .deb files from? - mainline
Kernels ?
--
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/2073676
Title:
after update of kernel HDMI audio is not w
@montagy
The change you mention is part of virtualbox since 6.1.26
commit d0c8c1d9763108e99a60822c3441881cf0007e24 (tag: upstream/6.1.26-dfsg)
Author: Gianfranco Costamagna
Date: Thu Jul 29 11:18:35 2021 +0200
New upstream version 6.1.26-dfsg
diff --git a/src/VBox/VMM/VMMR0/VMMR0JmpA-amd64
I have access to a certified laptop which has this problem.
If you have any test kernels one could use, please tell. Or better yet,
a fixed kernel from Canonical/Lenovo (is there any proposed section in
the OEM archives?).
Not willing to update to 24.04 since in production use and updating
might
I picked the commit and started a test build of the patched kernel that is
currently building here:
launchpad.net/~fheimes/+archive/ubuntu/lp2076147
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Public bug reported:
I was trying to switch nvidia drivers from 535 to 545 with Drivers tab
in Software Properties
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2
ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
Uname: Linux 6.8.
Public bug reported:
[Impact]
Full build log:
https://launchpadlibrarian.net/741978316/buildlog_ubuntu-oracular-
amd64.linux-restricted-modules_6.10.0-18.18+1_BUILDING.txt.gz
As soon as you fix one, another one shows up, and so on - it turned out,
the conftest.sh & Kbuild framework NVIDIA DKMS u
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/2076100
Title:
Jammy update: v5.15.164 upstream stable rele
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/2076097
Title:
Focal update: v5.4.281 upstream stable relea
Hi Ariel,
Thank you for taking the time to report this bug.
Which instance type (or types) are you using, and do you have a set of
steps for me to reproduce this?
Also, is this something that worked on a previous kernel, but only
stopped failing after you upgraded?
** Changed in: linux-signed-a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => 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/2068103
** Package changed: linux (Ubuntu) => linux-riscv (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/2076170
Title:
riscv64 linux image/header/module package versions don't ex
Public bug reported:
Hi,
Running mantic on a riscv64 system, trying (a little late) to upgrade
from mantic to noble, I ran into "Please install all available updates
for your release before upgrading" even after a dist-upgrade.
On closer inspection, I see:
The following packages have been kept
Hello and thanks for raising this issue.
Do you have a reproducer on this issue?
Since it's common code (memory mgnt) this needs to be handled with care, since
it will affect all installations.
Is it correct that you faced this issue while running the LTP Test suite?
Could you provide more detail
I'll revert 2 suspicious patches and provide a test kernel debian
package.
You will simply need to download all .deb files and go into the download
directory and do
dpkg -i *.deb
to install my test kernel. Will provide it later.
--
You received this bug notification because you are a member o
Verified linux/noble-proposed.
** Tags removed: verification-needed-noble-linux
verification-needed-noble-linux-oem-6.8
** Tags added: verification-done-noble-linux
verification-done-noble-linux-oem-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is
Verified linux/noble version 6.8.0-40.40.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2066233
Title:
amdgpu hangs on DCN 3.5 at bootup: RIP:
0010:dcn35_clk_mgr_construct+0x1
This is not for Strix-Halo, which targets v6.11. Mark verified for
linux/noble-proposed and linux-oem-6.8/noble.
** Tags removed: verification-failed-noble-linux
verification-failed-noble-linux-oem-6.8
** Tags added: verification-done-noble-linux
verification-done-noble-linux-oem-6.8
--
You re
Verified linux/noble-proposed.
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2070251
Verified linux-oem-6.10/noble-proposed and linux/noble-proposed.
** Tags removed: verification-needed-noble-linux
verification-needed-noble-linux-oem-6.10
** Tags added: verification-done-noble-linux
verification-done-noble-linux-oem-6.10
--
You received this bug notification because you are a
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2066233
Title:
amdgpu hangs on DCN 3.
Verification failed on a AMD CRB, and is sorting out the problem. It
appears we may need more patches on this board.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2058330
Title:
** Tags removed: verification-needed-noble-linux
verification-needed-noble-linux-oem-6.8
** Tags added: verification-failed-noble-linux-oem-6.8
verification-filed-noble-linux
** Tags removed: verification-filed-noble-linux
** Tags added: verification-failed-noble-linux
--
You received this bug
*** This bug is a duplicate of bug 2068107 ***
https://bugs.launchpad.net/bugs/2068107
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2068107, so it is being marked as such. Please look
** Tags added: kern-11402
--
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/2076073
Title:
Support Mediatek MT7920e
Status in HWE Next:
New
Status in linux-firmware package in U
The test-suite is again executed in the latest upload:
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/amd64/l/linux/20240712_053727_9b0f1@/log.gz
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
You received this bug notification b
80 matches
Mail list logo
