This should fix it:
https://lore.kernel.org/linux-scsi/20240711174815.work.689-k...@kernel.org/
Applied to 6.12/scsi-queue.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/20
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2078038
Title:
UBSAN ar
Can you try this kernel? https://people.canonical.com/~juergh/lp2078038/
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2078038
Title:
UBSAN array-index-out-of-bounds repo
** Attachment added: "adt.log"
https://bugs.launchpad.net/auto-package-testing/+bug/1992738/+attachment/5623813/+files/adt.log
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/
Public bug reported:
Since a couple of weeks ago, the magic trigger qemu-efi-noacpi/0 no
longer works. By no longer works I mean that the special script that
sets the ForceNoAcpi EFI variable is run and the VM comes back with ACPI
disabled after the first reboot following the testbed setup. But fo
** Description changed:
+ [Impact]
+
Issue found with Noble 6.8.0-41-generic on P9 node baltar.
[1.628868] i40e 0002:01:00.0: enabling device (0140 -> 0142)
[1.631444] [ cut here ]
[1.631460] UBSAN: array-index-out-of-bounds in
/build/linux-k1IV9m/l
6 matches
Mail list logo
