Noble seems to work fine on 6.8.0-62 and nvidia-driver-570. However I
could only test with one monitor. The machine where the bug happens has
three monitors and this might be important.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Changed in: linux-azure-nvidia (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2115453
Title:
[GB200] MANA patch updates
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bug
The upstream patch "gpio: mlxbf3: only get IRQ for device instance 0"
does NOT apply cleanly to the BF3 GPIO driver in Jammy. There's
additional logic required in Jammy that affects this patch merge.
For now, let's just use this bug for Noble repo.
--
You received this bug notification because
For plucky:gcp, boot testing was performed. Google has approved the
patchset.
** Tags removed: verification-needed-plucky-linux-gcp
** Tags added: verification-done-plucky-linux-gcp
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gc
Logs were attached, so I'm moving the bug status away from incomplete.
** Changed in: netplan.io (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
I only have bridge create by LXD, libvirtd, docker0 but none of these
are in the netplan
mastier@drakkar:~$ sudo grep -iHR bridge /etc/netplan/
mastier@drakkar:~$ echo $?
1
mastier@drakkar:~$ brctl show
bridge name bridge id STP enabled interfaces
br-151565677dbc 80
** Description changed:
SRU Justification
[Impact]
* Microsoft requested MANA patches for the following:
* Better spread IRQs per cpu
* Allocate MSI-X vectors in PCI dynamically
[Fix]
* Plucky:
* 4 clean cherry-picks from linux-next
- * 0792c36: "PCI/MSI
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
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/2115367
Title:
System display update hangs after erro
This has now been fixed in Linux sys76 5.15.0-142-generic
#152~20.04.1-Ubuntu SMP Fri May 23 15:12:38 UTC 2025 x86_64 x86_64
x86_64 GNU/Linux
** Changed in: linux-signed-hwe-5.15 (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of
** Changed in: linux-azure-nvidia (Ubuntu Noble)
Assignee: (unassigned) => John Cabaj (john-cabaj)
** Changed in: linux-azure-nvidia (Ubuntu)
Assignee: (unassigned) => John Cabaj (john-cabaj)
--
You received this bug notification because you are a member of Kernel
Packages, which is su
The bug is not reproducible in 6.14.0-24-generic
--
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/2115447
Title:
Ubuntu 24.04.2: NULL pointer dereference with Ceph and selinux
Status in l
The issue is easily reproducible on my side:
$ uname -r
6.8.0-62-generic
$ sudo snap install microceph
2025-06-27T09:12:27Z INFO Waiting for automatic snapd restart...
microceph (squid/stable) 19.2.0+snapab139d4a1f from Canonical✓ installed
$ sudo microceph cluster bootstrap
$ sudo microceph.cep
I am doing a re-spin of noble:linux-hwe-6.14 in 2025.06.16 so we do not
roll into a regression.
** Also affects: linux-hwe-6.14 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubunt
** Changed in: linux-hwe-6.14 (Ubuntu Noble)
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/2113992
Title:
Creating a VXLAN interface with a F
The LTS's default to Xorg, so if restore works on Xorg then this risks
being a regression for the default experience users.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
[ Impact ]
On certain USB3 device topologies, the hub will enter runtime resume
before the down stream device to wake up. When a device is connect to
such hub, the hub will enter runtime resume before the device generates
any activities, making it not able to get detected.
[
OK, good point. Let's say this is only fixed in 25.10 and later. That
makes sense given 26.04 will be the first LTS where we actually
recommend and default to Wayland on Nvidia.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphi
Does not seem to affect kernel.
** No longer affects: linux-bluefield (Ubuntu)
** No longer affects: linux-bluefield (Ubuntu Focal)
** No longer affects: linux-bluefield (Ubuntu Jammy)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-oem-6.14 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.14 in Ubuntu.
https://bugs.launchpad.
Given how broken the original bug here is, perhaps a failure to resume
on older LTS kernels is OK. At least HWE LTS machines could have the
fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https:/
> Should we expect the fix to work its way back to LTS releases over
time?
Not automatically. We could, but I feel like this is a large change, and
I previously had trouble (comment #39) with kernels 6.8 and 6.11 that
are shipping in noble and jammy for non-HWE.
--
You received this bug notifica
22 matches
Mail list logo
