Just to say, the liquorix fix is no longer a great solution as it now
has moved to the 6.10 kernel series which doesn't seem to be compatible
with nvidia drivers (at least, the 470 driver I need). It would be
really great to have this issue fixed! The recently released 6.8.0-40.40
kernel doesn't ch
*** This bug is a duplicate of bug 2073267 ***
https://bugs.launchpad.net/bugs/2073267
Thx.
Kernel 118 is the same.
In the future, kernel 119 will be better ^^
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
** Changed in: linux-oem-6.8 (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/2073282
Title:
Fix power consumption while using HW
** Changed in: linux-oem-6.8 (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/2073358
Title:
Kubuntu 24.04 freezes after plugging
I've stacked a copy of the patch on my netfs-fixes branch:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-
fs.git/log/?h=netfs-fixes
It builds and seems to work with the test in comment #46 - except that
it causes the generic/210 xfstest to fail with afs.
--
You received this bu
Thanks @David, but unfortunately that patch doesn't apply cleanly either
to 6.8.0-40:
$ patch -p1 --dry-run < ../david_howells_fix.patch
checking file fs/9p/vfs_addr.c
Hunk #1 succeeded at 73 (offset -2 lines).
checking file fs/netfs/io.c
Hunk #1 succeeded at 523 (offset -7 lines).
Hunk #2 succee
Looks like most recent kernel for Noble is now 6.8.0-40 as of this
morning. Patch doesn't apply to it either:
$ patch -p1 --dry-run <
../0001-WIP-tenative-fix-to-allow-reads-past-cached-size-for.patch
checking file fs/9p/vfs_addr.c
Hunk #1 succeeded at 73 (offset -2 lines).
checking file fs/netf
This kernel added the SKL ID to the quirk which did the same thing as
intel_iommu=igfx_off
We may have to carry these quirks before Intel provides a real fix.
Please give it a try and I'll submit SRU later.
https://people.canonical.com/~acelan/bugs/lp2062951/
--
You received this bug notificati
test rebuild of a package with this dpkg upload:
https://launchpad.net/~doko/+archive/ubuntu/ppa/+sourcepub/16312933/+listing-archive-extra
reference build:
https://launchpad.net/ubuntu/+source/lz4/1.9.4-1build1
- ppc64el: the -fno-omit-frame-pointer flags are gone
- s390x: only -mbackchain is us
test rebuild of a package with this dpkg upload:
https://launchpad.net/~doko/+archive/ubuntu/ppa/+sourcepub/16312933/+listing-archive-extra
reference build:
https://launchpad.net/ubuntu/+source/lz4/1.9.4-1build1
- ppc64el: the -fno-omit-frame-pointer flags are gone
- s390x: only -mbackchain is us
This patch has been verified on PS6 for few weeks
** Tags removed: verification-needed-jammy-linux verification-needed-noble-linux
** Tags added: verification-done-jammy-linux verification-done-noble-linux
--
You received this bug notification because you are a member of Kernel
Packages, which i
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-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-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux/5.15.0-120.130 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
This bug is awaiting verification that the linux/5.15.0-120.130 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
This bug is awaiting verification that the linux/5.15.0-120.130 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
This bug is awaiting verification that the linux/5.4.0-195.215 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-focal-linux' to 'verification-done-focal-linux'. If
the problem still exi
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-ubuntu-server
--
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/2076216
Title:
Ubun
Thanks for testing TheDreadPirate. I marked the bug as verified.
** 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 in Ubuntu.
https://bugs.l
All autopkgtests for the newly accepted linux-meta (6.8.0-43.43) for noble have
finished running.
The following regressions have been reported in tests triggered by the package:
diffoscope/259 (armhf, ppc64el)
dracut/060+5-1ubuntu3.2 (amd64)
dropbear/2022.83-4 (armhf)
glibc/2.39-0ubuntu8.2 (armhf
I have confirmed that ffmpeg transcoding on my Arc A380 works with
6.8.0-43. I tested multiple scenarios that failed on 6.8.0-38 now work
on 43.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
tracking bug
** Affects: qrtr (Ubuntu)
Importance: Undecided
Status: New
** Merge proposal linked:
https://code.launchpad.net/~sudipmuk/ubuntu/+source/qrtr/+git/qrtr/+merge/469425
--
You received this bug notification because you are a member of Kernel
Pa
Hi Chris!
I have added inline comments suggesting the changes to make the patch conform
to dep-3 header format.
Would it be also possible to run `quilt refresh` once you've applied the
patches to ensure that we do not introduce spurious diffs in the future?
Best Regards,
Vladimir.
--
You
AceLan Kao,
In summary, I did not see any improvement, but perhaps some of the extended
debugging is helpful.
I did the following steps over the course of my work day, so I might have
missed a step, but here is the order of what I did:
I added the ubuntu kernel repo:
$ sudo add-apt-repository p
20240808_victus-syslog.txt
** Attachment added: "20240808_victus-syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+attachment/5803967/+files/20240808_victus-syslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Hi Ian,
I have since found out that I need to apply this against linux-firmware.
So ignore those test kernels for now.
** Package changed: linux (Ubuntu Noble) => linux-firmware (Ubuntu
Noble)
** Changed in: linux-firmware (Ubuntu Noble)
Assignee: (unassigned) => Michael Reed (mreed8855)
-
Public bug reported:
The nvidia-fs prebuilt module linux-modules-nvidia-fs-5.15.0-ABIN-
nvidia(-lowlatency) packages provide nvidia-fs-dkms. The linux-
nvidia(-lowlatency) meta packages depend on either the latest linux-
modules-nvidia-fs-5.15.0-ABIN-nvidia(-lowlatency), or "nvidia-fs-dkms"
as an
Adding the "verification-done-focal-linux-aws-5.15" since this bug
doesn't affect focal:linux-azure-5.15
** Tags removed: kernel-spammed-bionic-linux-azure-5.4-v2
kernel-spammed-focal-linux-ibm-5.15-v2
verification-needed-bionic-linux-azure-5.4
verification-needed-focal-linux-aws-5.15
verifica
All autopkgtests for the newly accepted dpkg (1.22.6ubuntu6.1) for noble have
finished running.
The following regressions have been reported in tests triggered by the package:
aodh/unknown (s390x)
apache2/2.4.58-1ubuntu8.4 (armhf)
apache2/unknown (s390x)
apt/2.7.14build2 (s390x)
apt-cacher/unknow
All autopkgtests for the newly accepted dpkg (1.22.6ubuntu6.1) for noble have
finished running.
The following regressions have been reported in tests triggered by the package:
aodh/unknown (s390x)
apache2/2.4.58-1ubuntu8.4 (armhf)
apache2/unknown (s390x)
apt/2.7.14build2 (s390x)
apt-cacher/unknow
Wanting to test whether the fix had also made it into the focal-proposed
(Ubuntu 20.04) kernel version -119, despite the absence of any
indication of that in the bug status description, I tried to install the
proposed kernel, but I can't:
# trying to install from proposed2 (also tested proposed, w
This bug is awaiting verification that the linux-
azure-5.4/5.4.0-1135.142~18.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-bionic-linux-
azure-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
ibm-5.15/5.15.0-1060.63~20.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-focal-linux-
ibm-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
azure-5.4/5.4.0-1135.142~18.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-bionic-linux-
azure-5.4' to 'verification-done-bionic
This bug was fixed in the package linux-azure - 6.8.0-1012.14
---
linux-azure (6.8.0-1012.14) noble; urgency=medium
* noble/linux-azure: 6.8.0-1012.14 -proposed tracker (LP: #2072175)
* Packaging resync (LP: #1786013)
- [Packaging] debian.azure/dkms-versions -- update from ke
This bug was fixed in the package linux-azure - 6.8.0-1012.14
---
linux-azure (6.8.0-1012.14) noble; urgency=medium
* noble/linux-azure: 6.8.0-1012.14 -proposed tracker (LP: #2072175)
* Packaging resync (LP: #1786013)
- [Packaging] debian.azure/dkms-versions -- update from ke
This bug was fixed in the package linux-azure - 6.8.0-1012.14
---
linux-azure (6.8.0-1012.14) noble; urgency=medium
* noble/linux-azure: 6.8.0-1012.14 -proposed tracker (LP: #2072175)
* Packaging resync (LP: #1786013)
- [Packaging] debian.azure/dkms-versions -- update from ke
This bug was fixed in the package linux-azure - 5.15.0-1070.79
---
linux-azure (5.15.0-1070.79) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1070.79 -proposed tracker (LP: #2072209)
* Packaging resync (LP: #1786013)
- [Packaging] debian.azure/dkms-versions -- update from
This bug was fixed in the package linux-nvidia-tegra-igx -
5.15.0-1013.13
---
linux-nvidia-tegra-igx (5.15.0-1013.13) jammy; urgency=medium
* jammy/linux-nvidia-tegra-igx: 5.15.0-1013.13 -proposed tracker
(LP: #2072515)
* Add OOTM branching to fix GPU driver version mismatch
This bug was fixed in the package linux-azure - 5.4.0-1135.142
---
linux-azure (5.4.0-1135.142) focal; urgency=medium
* focal/linux-azure: 5.4.0-1135.142 -proposed tracker (LP: #2072263)
* Packaging resync (LP: #1786013)
- [Packaging] debian.azure/dkms-versions -- update from
** Description changed:
[Impact]
* Microsoft has requested a patch to address a kernel panic issue
+ similar to the upstream issue here -
+
https://patchwork.kernel.org/project/netdevbpf/patch/20240731213046.6194-2-pa...@netfilter.org/
[Fix]
* Clean cherry-pick upstream commit 58
** Changed in: ubuntu-z-systems
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/2074380
Title:
[UBUNTU 22.04] s390/cpum_cf: make crypto counter
It seems to fix the problem for me too.
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/2073358
** Also affects: linux-signed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-signed (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ub
Hi Ranjan,
What is the regression risk? Also in your steps for testing, what does
r0 and r1 stand for in this step "ro and r1 creation and deletion"?
** Description changed:
[Impact]
This update has been initiated to incorporate the mpi3mr driver from upstream
into the upcoming Ubuntu rele
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2076361/+attachment/5803836/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency in U
Public bug reported:
I've been using a Lenovo X12 Detachable Gen 2 model from 2024 [1] to
encode some video files with ffmpeg, and the system becomes completely
unresponsive for as long as the process executes. Although small, this
is a pretty good device hardware wise, and while executing the sys
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2076361/+attachment/5803835/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency in Ubuntu.
htt
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2076361/+attachment/5803834/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency in Ubuntu.
solution in linux/6.8.0-43.43 works for me.
--
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/2073358
Title:
Kubuntu 24.04 freezes after plugging in ethernet cable
Status in linux package
This cherry pick will cover noble and oracular. Backporting this from
6.10 to 5.15 is not feasible for the Jammy kernel. Also this will be
in the 6.8 kernel in 22.04.5.
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Won't Fix
--
You received this bug notification because you
No, I shouldn't have mentioned it. This laptops have a problem, and it's
work-arounded by doing the masking and unmasking of interrupt 0x6E. The
fix is not in the kernel yet, so I have the work-around enabled since
one year ago.
This is a totally different problem: since one month ago, the compute
Public bug reported:
My touchpad was working fine, but suddenly it stopped working. I've
tried all the solutions available on the internet, but nothing has
solved the issue. When I tried to list the detected devices (less
/proc/bus/input/devices), the touchpad didn't appear. I'm not sure how
to so
** Tags removed: verification-needed-focal-linux-azure
** Tags added: verification-done-focal-linux-azure
--
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/2073414
Title:
Include Azure Site
I will test out -43 when I get home tonight.
--
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/2072755
Title:
i915: Fixup regressions introduced with enabling single CCS engine
Status in l
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
** Changed in: linux-meta-oem-6.5 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2038752
Title:
6.5.1005.7 has broken Proton pref
Already resolved long time ago.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2038752
Title:
6.5.1005.7 has broken Proton prefix creation
Status in linux-meta-oem-6.5 pack
Hi @schopin, I agree - that is what is now under option 1) under test
plan in the SRU Justification.
--
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/2064539
Title:
Revert back frame point
** Description changed:
- Power's Linux ABIs all require an explicit call chain be stored on the call
stack frames which are all accessible via the stack pointer.
- Therefore, having a (soft/simulated) frame pointer does not improve
backtraces at all on Power.
+ SRU Justification:
- However,
** Description changed:
SRU Justification:
[ Impact ]
- * The preferred way of doing stack unwinding on Linux on Z is via dwarf call
frame information.
+ * The preferred way of doing stack unwinding on Linux on Z is via dwarf call
frame information.
In absence of a dwarf unwinder (
** Description changed:
- The preferred way of doing stack unwinding on Linux on Z is via dwarf call
frame information.
+ SRU Justification:
+
+ [ Impact ]
+
+ * The preferred way of doing stack unwinding on Linux on Z is via dwarf call
frame information.
In absence of a dwarf unwinder (as
Hi @ktecho,
Thank you for taking the time to open this bug report.
I just want to make sure I understand everything going on here...
There is a fix upstream that Diogo submitted, and you would like for it
to make it into the Noble (24.04) kernel. That patch should fix the
issue you are hitting
Would running https://gist.githubusercontent.com/julian-
klode/85e3f85c410a1b856a93dce77208/raw/488b8509e6f23fe48f917961fe711b285dcb2e28/dwprod.py
on /usr/lib/libc.so.6 to find the relevant flag (or absence thereof) be
enough as a test case?
--
You received this bug notification because you a
** No longer affects: linux-kvm (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/2076213
Title:
eventinj ubuntu_kvm_unit_test bionic:oracle-5.4 flaky "vec 32/int $33"
Status
** Tags removed: verification-needed-noble-linux-lowlatency
** Tags added: verification-done-noble-linux-lowlatency
--
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/2071889
Title:
a critic
--- Comment From fran...@de.ibm.com 2024-08-08 08:52 EDT---
Three additional commits are necessary to allow cherry picking with minimal
effort:
3c724f1a1caa s390: uv: Add offset comments to UV query struct and fix naming
ac640db3a026 s390/uv: Add SE hdr query information
daec8d408308 Docum
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-lowlatency' to
'verification-done-noble-linux-low
1 - 100 of 239 matches
Mail list logo
