Hi Gianfranco,
Great! Let's work this out together.
I have strong doubts that:
commit ef40d28f17bd384d7e0b630c7d83f108a526351b
Author: Kees Cook
Date: Wed Jun 19 14:47:15 2024 -0700
Subject: randomize_kstack: Remove non-functional per-arch entropy filtering
Link:
https://git.kernel.org/pub/s
Hello everyone,
Lets get this problem solved.
Now, doing a major version update to virtualbox in Jammy from
6.1.50-dfsg-1~ubuntu1.20.04.1 to 7.0.20 is against Ubuntu SRU policy,
and would also come with the consequence that it would break all
existing VMs that use guest additions, as guest additi
Hello everyone,
Lets get this problem solved.
Now, doing a major version update to virtualbox in Jammy from
6.1.50-dfsg-1~ubuntu1.20.04.1 to 7.0.20 is against Ubuntu SRU policy,
and would also come with the consequence that it would break all
existing VMs that use guest additions, as guest additi
Hi Detlef,
>a) crash by start
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu
You system was affected by bug 2068738, which has now been fixed as of
5.15.0-116-generic. Sorry for the inconvenience.
We will try fix c) soon.
Thanks,
Matthew
Hi Detlef,
>a) crash by start
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu
You system was affected by bug 2068738, which has now been fixed as of
5.15.0-116-generic. Sorry for the inconvenience.
We will try fix c) soon.
Thanks,
Matthew
Patches are on the kernel team mailing list:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-July/152506.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-July/152507.html
--
You received this bug notification because you are a member of Kernel
Packages, which is su
l or Jammy.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: noble sts
** Also affects: linux (Ubuntu Noble)
Importance:
Hi everyone,
SRU template is written. The patch has been submitted to the Ubuntu
Kernel mailing list.
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-July/152495.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-July/152496.html
TJ, I cc'd you incase the kernel team
dy fixed upstream by the mini C
+ runtime in 6.9 and later. This patch is for noble only.
** Changed in: linux (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => High
** Changed in: linux (Ubuntu Noble)
Assignee: (
Great, thanks for trying the test kernel.
I think the best way forward is to submit TJ's patch, it really is a
better solution that backporting the entire mini c runtime or reverting
the commit that introduced the problem.
I can write a SRU template and submit it tomorrow.
We need to try catch t
Hi TJ, Shantur, Chris,
If you wait 3 hours from this message, the kernels will likely be ready. They
are building in:
https://launchpad.net/~mruffell/+archive/ubuntu/lp2069534-test
They are 6.8.0-39-generic + your patch. Both for Noble and Jammy HWE.
Test whatever you like.
Please note this pa
Hi TJ,
Thanks for your fix, this looks much, much more palatable than
backporting the entire mini C runtime, or reverting the commit that
caused this problem.
Now, just as Greg K-H says, 6.8.y is EOL upstream, and is closed to new
patches.
We can probably pick this up as a SAUCE patch for Ubuntu
Patches are on the kernel team mailing list:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-July/152506.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-July/152507.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
l or Jammy.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: noble sts
** Also affects: linux (Ubuntu Noble)
Importance:
Hi everyone,
SRU template is written. The patch has been submitted to the Ubuntu
Kernel mailing list.
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-July/152495.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-July/152496.html
TJ, I cc'd you incase the kernel team
dy fixed upstream by the mini C
+ runtime in 6.9 and later. This patch is for noble only.
** Changed in: linux (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => High
** Changed in: linux (Ubuntu Noble)
Assignee: (
Great, thanks for trying the test kernel.
I think the best way forward is to submit TJ's patch, it really is a
better solution that backporting the entire mini c runtime or reverting
the commit that introduced the problem.
I can write a SRU template and submit it tomorrow.
We need to try catch t
Hi TJ, Shantur, Chris,
If you wait 3 hours from this message, the kernels will likely be ready. They
are building in:
https://launchpad.net/~mruffell/+archive/ubuntu/lp2069534-test
They are 6.8.0-39-generic + your patch. Both for Noble and Jammy HWE.
Test whatever you like.
Please note this pa
Hi TJ,
Thanks for your fix, this looks much, much more palatable than
backporting the entire mini C runtime, or reverting the commit that
caused this problem.
Now, just as Greg K-H says, 6.8.y is EOL upstream, and is closed to new
patches.
We can probably pick this up as a SAUCE patch for Ubuntu
*** This bug is a duplicate of bug 2072755 ***
https://bugs.launchpad.net/bugs/2072755
Fantastic. Keep an eye out on that bug, and we will get this fixed.
Thanks,
Matthew
** This bug has been marked a duplicate of bug 2072755
i915: Fixup regressions introduced with enabling single CCS eng
Hi nyanmisaka, TheDreadPirate,
Thanks for trying the test kernel, and great to hear that it works.
I wrote up a SRU template, as you can see, in the description of the
bug.
I also submitted the patch to the Ubuntu kernel mailing list:
Cover Letter:
https://lists.ubuntu.com/archives/kernel-team/
hanged in: linux (Ubuntu Noble)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
- Hello Ubuntu Linux Kernel Team,
+ BugLink: https://bugs.launchpad.net/bugs/2072755
- Recently, Ubuntu 24.04 bumped the kernel version to linux 6.8.8
- (6.8.0-38.38 pkg versio
Hi Filip,
I think this is a duplicate of bug 2072755. Can you head over there and
try the test kernel I linked?
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072933
Title:
Intel G
Hi Dong,
Yes, the tag is correct, great news that the kernel fixes the issue.
As for a release schedule, have a look at https://kernel.ubuntu.com/
under 2024.07.08, where we will likely see a release to -updates around
the week of the 5th August, if everything goes well.
Thanks,
Matthew
--
You
Hi nyanmisaka,
I have built you a test kernel based on 6.8.0-38-generic with the
following two commits added ontop:
commit aee54e282002a127612b71255bbe879ec0103afd
Author: Andi Shyti
Date: Fri Apr 26 02:07:23 2024 +0200
Subject: drm/i915/gt: Automate CCS Mode setting during engine resets
Link:
Hi Dong,
The Kernel team has built the new kernel with the fix. Would be able to
help test it and verify that it fixes the issue?
Instructions to Install (On a noble system):
1) cat << EOF | sudo tee /etc/apt/sources.list.d/ubuntu-$(lsb_release
-cs)-proposed.list
# Enable Ubuntu proposed archive
Hi nyanmisaka,
"drm/i915/gt: Automate CCS Mode setting during engine resets" is already
queued up in master-next, so it should be available in the next SRU
cycle or so:
commit aee54e282002a127612b71255bbe879ec0103afd
Author: Andi Shyti
Date: Fri Apr 26 02:07:23 2024 +0200
Subject: drm/i915/gt:
Performing verification for jammy.
I started a fresh jammy VM, that had an attached 50gb NVMe device:
$ lsblk
nvme0n1 259:00 46.6G 0 disk
nvme1n1 259:108G 0 disk
├─nvme1n1p1 259:20 7.9G 0 part /
├─nvme1n1p14 259:304M 0 part
└─nvme1n1p15 259:40 106M
Thanks for testing Matt, H.A.
I marked the bug as verified. We should be all good for a release to -updates
early next week. I'll write a new message as soon as the kernel has been
released for everyone.
Thanks,
Matthew
** Tags removed: verification-needed-jammy-linux
** Tags added: verification
cular, which means we are clear for SRU.
Heitor, would you please help with sponsoring to F, J, M, N?
Thanks,
Matthew
** Also affects: e2fsprogs (Ubuntu Oracular)
Importance: Critical
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Changed in: e2fsprogs (Ubuntu Ora
Hi everyone,
The Kernel Team have respun the latest 5.15 kernel with the fix, and have placed
it into -proposed for verification.
Could someone more technically minded help test it and let me know if it fixes
the problem?
Instructions to Install (On a jammy system):
1) cat << EOF | sudo tee /etc
Hi Kashad,
Great to hear so far. Definitely work on your assignment. Let me know how
6.10-rc4 goes over the next day or two.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071854
Tit
Hi Kashad,
Firstly, lets get you a nice stable kernel for you to use in the meantime.
You mentioned 23.10 worked okay right? So let's get you back on that 6.5
kernel.
I don't usually recommend mixing 23.10 and 24.04 packages, but it will be
alright for the kernel.
We are going to release 6.5.0-4
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
** This bug has been marked a duplicate of bug 2068738
AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
black screen
--
You received this bug notification because you are a me
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
** This bug has been marked a duplicate of bug 2068738
AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
black screen
--
You received this bug notification because you are a me
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
** This bug has been marked a duplicate of bug 2068738
AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
black screen
--
You received this bug notification because you are a me
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
** This bug has been marked a duplicate of bug 2068738
AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
black screen
--
You received this bug notification because you are a me
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
** This bug is no longer a duplicate of bug 2071351
Kernel 5.15.113 and AMD graphics
** This bug has been marked a duplicate of bug 2068738
AMD GPUs fail with null pointer dereference when IOMMU enable
Hi everyone,
The patch was not present in 5.15.0-113-generic, as this kernel only contained
CVE fixes.
It should be in the next kernel update. Still waiting on the Kernel team to
respin.
I will write back as soon as we have a kernel tagged and in -proposed to
test.
Thanks,
Matthew
--
You rece
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
** This bug has been marked a duplicate of bug 2068738
AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
black screen
--
You received this bug notification because you are a me
Hi Robert, and to Jorg_Mertin too,
Thanks for trying the test kernel, sorry it didn't fix the issue. It
seems I have the wrong commit, and I was hoping it was that one too.
I'll have another look though the changelog to see if anything else
jumps out, but we might have to do a full bisect. I can
Public bug reported:
[Impact]
Ubuntu Release Upgrader uses python-apt for apt operations, including
parsing and making sure the sources.list file is sensible.
Options are placed in square brackets [] after the initial deb as key
value pairs.
e.g.
deb [lang=en] http://archive.ubuntu.com/ubuntu
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069961
Title:
turbostat and powerstat not working on 22.04
To manage
Hi everyone,
Okay, I have gotten test kernels building. They have the below commit
reverted on 6.5.0-41-generic:
commit 286f3a7ccae334cef008c6be713c7c30427243c1 ubuntu-mantic
Author: Wayne Lin
Date: Tue Jan 2 14:20:37 2024 +0800
Subject: drm/amd/display: Align the returned error code with lega
Hi everyone,
I noticed you were all using AMD processors... and I had a browse
through the 1100 commits or so that are between 6.5.0-25-generic to
6.5.0-41-generic, and this one caught my eye:
commit 286f3a7ccae334cef008c6be713c7c30427243c1 ubuntu-mantic
Author: Wayne Lin
Date: Tue Jan 2 14:20
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-hwe-6.5 (Ubuntu)
** No longer affects: linux-oem-6.5 (Ubuntu)
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
St
*** This bug is a duplicate of bug 2070020 ***
https://bugs.launchpad.net/bugs/2070020
Hi Robert,
Come talk on bug 2070020 and let's try figure this out.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
*** This bug is a duplicate of bug 2070020 ***
https://bugs.launchpad.net/bugs/2070020
Hi Ken,
Do you happen to have an AMD processor? Come and talk on bug 2070020 and
we will try figure this out.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs
*** This bug is a duplicate of bug 2070020 ***
https://bugs.launchpad.net/bugs/2070020
** This bug has been marked a duplicate of bug 2070020
Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
--
You received this bug notification because you are a member of Ubuntu
Bugs
Hi Dong,
The Kernel Team reviewed the patch, and it got 3 acks by Senior Kernel Team
members.
https://lists.ubuntu.com/archives/kernel-team/2024-June/151552.html
https://lists.ubuntu.com/archives/kernel-team/2024-June/151564.html
https://lists.ubuntu.com/archives/kernel-team/2024-June/151583.html
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
Hi Thos,
This is a known regression. See bug 2068738. We will try have it fixed
in the current SRU cycle.
Thanks,
Matthew
** This bug has been marked a duplicate of bug 2068738
AMD GPUs fail with null
Hi everyone,
I spoke with Stefan Bader of the Kernel Team again. They are planning to include
the patch in a respin of the current 2024.06.10 SRU cycle.
https://kernel.ubuntu.com/
I will let you know once the kernel has been built and placed into -proposed for
verification.
But at this stage, a
Hi Dong,
Thanks for trying the test kernel and letting me know it works. And for
the help with the testcase.
I have submitted the patch to the Ubuntu Kernel Team mailing list:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-June/151550.html
Patch:
https://lists.ubuntu.com/archiv
** Description changed:
- In the Ubuntu 24's 6.8.0-31-generic kernel version, the capability
-
https://github.com/torvalds/linux/commit/fd27ef6b44bec26915c5b2b22c13856d9f0ba17a
- (virtio-pci: Introduce admin virtqueue) was added. However, an issue was
- overlooked by the upstream community, which
Ubuntu Noble)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2067862
Title:
Removing legacy virtio-pci devices causes kernel panic
Hi Shantur,
It is not fixed, I just marked it as fixed for "Ubuntu" a.k.a the
development release oracular, since it will pick up a 6.10+ kernel when
it eventually becomes available.
I added a noble entry, since noble's kernel is the one that actually
needs to be fixed.
I did have a look at "arm
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
Known regression. See bug 2068738
** This bug has been marked a duplicate of bug 2068738
AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
black screen
--
You received this bu
*** This bug is a duplicate of bug 2069534 ***
https://bugs.launchpad.net/bugs/2069534
** This bug has been marked a duplicate of bug 2069534
linux 6.8 fails to boot on arm64 if any param is more than 140 chars
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069534
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
** This bug has been marked a duplicate of bug 2068738
AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
black screen
--
You received this bug notification because you are a me
Hi Roger,
Does your HP laptop have an AMD APU? AMD GPU?
You are probably suffering from:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Hi Pramod,
I downloaded the driver version you listed, 550.90.07 from the NVIDIA
website:
https://www.nvidia.com/download/driverResults.aspx/226768/en-us/
This gave me NVIDIA-Linux-x86_64-550.90.07.run.
I managed to successfully install this to 6.8.0-31-generic, and 6.8.0-35-generic
without any
Performing verification for Focal.
I started a fresh focal VM, and installed irqtop 2.4-2ubuntu0.5 and
ruby-curses 1.2.4-1build1 from -updates.
I then started irqtop:
$ sudo irqtop
/usr/bin/irqtop:598: warning: rb_safe_level will be removed in Ruby 3.0
Performing verification for Jammy.
I started a fresh jammy VM, and installed irqtop 2.6-2ubuntu3 with ruby-
curses 1.2.4-1build3, from -updates.
I then ran:
$ sudo irqtop
:85:in
`require': /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/curses.so:
undefined symbol: rb_safe_level -
/usr/lib/x
Hi Dong,
I have been reading:
https://lore.kernel.org/kvm/CACGkMEs1t-ipP7TasHkKNKd=peVEES6Xdw1zSsJkb-
bc9et...@mail.gmail.com/T/#m167335bf7ab09b12fec3bdc5d46a30bc2e26cac7
and I tried to reproduce the problem with 23.10's userspace, but I can't
see the same crash.
By virtio legacy devices, you m
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs
Hi everyone,
An update:
Greg KH has picked up the patch and added it to upstream stable now:
https://lore.kernel.org/amd-gfx/2024061223-suitable-handler-b6f2@gregkh/
https://lore.kernel.org/amd-gfx/2024061239-rehydrate-flyable-343e@gregkh/
I suppose we can drop the UBUNTU: SAUCE tags.
I talke
Attached is a V2 that corrects a minor omission in the changelog.
** Patch added: "Debdiff for nvme-cli on Jammy V2"
https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/2051299/+attachment/5788982/+files/lp2051299_jammy_V2.debdiff
** Patch removed: "Debdiff for nvme-cli on Jammy"
http
it required a minor backport. In later versions, a major
refactor occurred that changed nvme_uuid_to_string() among numerous
other functions, that is not appropriate to backport. Instead, just take
the current implementation of nvme_uuid_to_string() and move it like the
patch suggests, so j
Hi Greg KH, Sasha,
Please pick up this patch for 5.15 stable tree. I have built a test kernel and
can confirm that it fixes affected users.
Downstream bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738
Thanks,
Matthew
Hi Greg KH, Sasha,
Please pick up this patch for 5.15 stable tree. I have built a test kernel and
can confirm that it fixes affected users.
Downstream bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738
Thanks,
Matthew
Hi Ariel,
Are you using zfs? I see you have the module listed.
Your oops looks very similar to this discussion here:
https://github.com/openzfs/zfs/issues/15140
It doesn't seem anyone has come to any conclusions yet. I'll do some
more research.
Thanks,
Matthew
** Bug watch added: github.com/o
Hi everyone,
Patches are on the Ubuntu Kernel Team mailing list:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-June/151409.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-June/151410.html
I will go talk to the kernel team now, I can't promise anything, but
will
** Summary changed:
- Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs
+ AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
black screen
** Description changed:
- System is not booting while using AMD Picasso/Raven 2 graphics after
- update to
Hello Evgueni,
Are you sure it is an Nvidia card? We have a known regression for
5.15.0-112-generic with AMD cards, over in bug 2068738. The symptom is a
black screen on boot.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Hi Xie,
Thanks for trying the test kernel, and its great news that we have
identified the fix. I'll write up a SRU template, and get the patch sent
off to the kernel team today.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Tino,
It says Fix Released for Ubuntu, aka, the latest Ubuntu release, which
is 24.10 Oracular, as it isn't affected. Maybe I should have marked it
invalid in the first place.
Anyway, once someone tries the test kernel I built yesterday to see if
it fixes the issue, I can go about getting the
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068738
Title:
Kerne
PS. Please remove the workaround "nomodeset" if you applied it before
you try the test kernel. I really just want to know if the reverted
patch fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
** This bug has been marked a duplicate of bug 2068738
Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs
--
You received this bug notification because you are a member of Ubunt
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/206
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
** This bug has been marked a duplicate of bug 2068738
Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs
--
You received this bug notification because you are a member of Ubunt
Hi Pramod,
Yes, this changed recently, in mantic and onward I believe.
CONFIG_DRM is set to "y" for all architectures except s390x, which is
why you still see drm.ko.zst for s390x only.
In Ubuntu Noble kernel sources:
debian.master/config/annotations:
177:CONFIG_DRM
Hi Daniel,
Thanks for your contributions!
There's two ways we get patches into our Ubuntu kernels, the first is a LP bug
per patchset that ideally fixes one specific issue, has a testcase etc and then
we submit patches for review to the Ubuntu Kernel Mailing list.
The process is:
https://wiki.ub
*** This bug is a duplicate of bug 2058052 ***
https://bugs.launchpad.net/bugs/2058052
** This bug has been marked a duplicate of bug 2058052
Enable Intel IDPF support on ARM64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
in: linux-gcp (Ubuntu Oracular)
Importance: Undecided => High
** Changed in: linux-gcp (Ubuntu Noble)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux-gcp (Ubuntu Oracular)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux
Public bug reported:
BugLink: https://bugs.launchpad.net/bugs/
[Impact]
GCE C3 Metal instance type requires the Intel IDPF driver for networking
to function.
On the Mantic kernel, this was built into the kernel:
# grep IDPF /boot/config-6.5.0-1020-gcp
CONFIG_IDPF=y
On Noble, this is now been
Attached is a debdiff which solves this issue for focal.
** Patch added: "Attached is a debdiff for ruby-curses on focal"
https://bugs.launchpad.net/ubuntu/+source/ruby-curses/+bug/1907932/+attachment/5779433/+files/lp1907932_focal.debdiff
--
You received this bug notification because you ar
Attached is a debdiff for jammy which solves this issue.
** Summary changed:
- ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0",
affects at least irqtop
+ drop rb_safe_level() from ruby-curses to fix irqtop from missing symbols and
deprecation warnings
** Description cha
rses (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: ruby-curses (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: ruby-curses (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: ruby-curses (Ubuntu Jammy)
** Also affects: calibre (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** Also affects: calibre (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Hi Light_Kernel_Ops,
The linux-signed package is signed with Canonical's Secure Boot Signing
Key, making the kernel bootable on systems that have secure boot
enabled. This key is not public for obvious reasons, and only particular
Kernel team members have access to it.
Where do you want to publis
Hi Theodore,
Ubuntu carries a little delta ontop of debian, and requires a merge, so
I think it is best to wait a week for the final e2fsprogs release before
we perform the merge.
https://merges.ubuntu.com/e/e2fsprogs/REPORT
Thanks,
Matthew
--
You received this bug notification because you are
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
Hi JB2Cool,
Yes, you are correct. You are seeing the exact same as bug 2060780, that
was introduced between 5.15.0-101 and 5.15.0-102 and fixed in
5.15.0-105.
For AWS, the fix is in:
$ git log --grep "smb
Hi Bernard,
These are userspace application crashes.
Try and wait for a kernel crash to occur.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064291
Title:
Ubuntu 24.04 crashed mu
Hi Bernard,
The crash seems to bring your system down before the logs are able to be
written to disk, so there is no oops present in your dmesg.
Its pretty common. Would you be able to capture a kernel crashdump
(kdump).
Follow the instructions in:
https://ubuntu.com/server/docs/kernel-crash-du
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: jammy sts
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux
Hi Sophi,
The 5.19 HWE kernel for Jammy is no longer supported. Its support period
was for the lifetime of the 22.10 Kinetic Kudu release, which is now end
of life.
Can you upgrade to a supported kernel, e.g. the latest 5.15 Jammy kernel
or the current 6.5 HWE kernel, and retry?
Is there any rea
Hi everyone,
Thank you for testing, and its great to hear that it fixes the issue.
The Jammy HWE kernel is still queued up to be built, it should be built
over the next few days. You can keep an eye on it at
https://kernel.ubuntu.com/reports/kernel-stable-board/
Regardless, we should be on track
Hi everyone,
Thank you for testing, and its great to hear that it fixes the issue.
The Jammy HWE kernel is still queued up to be built, it should be built
over the next few days. You can keep an eye on it at
https://kernel.ubuntu.com/reports/kernel-stable-board/
Regardless, we should be on track
101 - 200 of 1192 matches
Mail list logo
