Attached is a debdiff that fixes this issue on jammy.
** Patch added: "Debdiff for sssd on jammy"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2081129/+attachment/5819098/+files/lp2081129_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
022 +0100
Subject: pam: better SC fallback message
Link:
https://github.com/SSSD/sssd/commit/4d2277f8c3065771a8c3bbc7938309a4905640f0
** Affects: sssd (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: sssd (Ubuntu Jammy)
Importance: Medium
Assignee: Matth
Upstream threads:
V1:
https://lore.kernel.org/netdev/a76ac35a-9be2-4849-985c-2f3b2a922...@akamai.com/T/
V2:
https://www.spinics.net/lists/netdev/msg1027412.html
V3:
https://lore.kernel.org/netdev/CADVnQy=xv_qy77nzk2wvjxdkjsiba+k5b4lhgf4msr-v1r2...@mail.gmail.com/T/
Josh, if you need any help bu
Upstream threads:
V1:
https://lore.kernel.org/netdev/a76ac35a-9be2-4849-985c-2f3b2a922...@akamai.com/T/
V2:
https://www.spinics.net/lists/netdev/msg1027412.html
V3:
https://lore.kernel.org/netdev/CADVnQy=xv_qy77nzk2wvjxdkjsiba+k5b4lhgf4msr-v1r2...@mail.gmail.com/T/
Josh, if you need any help bu
*** This bug is a duplicate of bug 2078704 ***
https://bugs.launchpad.net/bugs/2078704
Hi Andrew,
I believe this is the same as bug 2078704. We narrowed it down to
"sunrpc: exclude from freezer when waiting for requests:" that fixed the
issue. It should be present in 5.15.0-121-generic or lat
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
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/2078704
Title:
[REGRESSION] Unable to suspend-to-ram with
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => 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/2078704
Title:
[REGRESSION] Unable to suspend-to-ram with NFS mounted o
*** This bug is a duplicate of bug 2078704 ***
https://bugs.launchpad.net/bugs/2078704
Hi Andrew,
I believe this is the same as bug 2078704. We narrowed it down to
"sunrpc: exclude from freezer when waiting for requests:" that fixed the
issue. It should be present in 5.15.0-121-generic or lat
Hi Paul,
Let's have a look.
ubuntu-noble$ git log --grep "thermal: core: Change PM notifier priority to the
minimum" origin/master-next
commit 80123fe6fcc3f72ee6fbe7bc6c64043b9e4c91e1
Author: Rafael J. Wysocki
Date: Fri Jun 14 17:26:00 2024 +0200
thermal: core: Change PM notifier priorit
Hi Paul,
Let's have a look.
ubuntu-noble$ git log --grep "thermal: core: Change PM notifier priority to the
minimum" origin/master-next
commit 80123fe6fcc3f72ee6fbe7bc6c64043b9e4c91e1
Author: Rafael J. Wysocki
Date: Fri Jun 14 17:26:00 2024 +0200
thermal: core: Change PM notifier priorit
Performing verification for Jammy.
I started a n2-highcpu-32 instance on GCP due to bare metal systems
being unavailable due to the certification lab move.
I edited /etc/default/grub.d/50-cloudimg-settings.cfg and set:
GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0,115200 isolcpus=4-7,16-20
rcu_nocb_
Performing verification for Jammy.
I started a n2-highcpu-32 instance on GCP due to bare metal systems
being unavailable due to the certification lab move.
I edited /etc/default/grub.d/50-cloudimg-settings.cfg and set:
GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0,115200 isolcpus=4-7,16-20
rcu_nocb_
6.8.0-44-generic for noble was released to -updates this morning.
** Changed in: linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
6.8.0-44-generic for noble was released to -updates this morning.
** Changed in: linux (Ubuntu Noble)
Status: Fix Committed => 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/2080039
Hi Andre,
Great research! Lets have a look at that patch you found.
ubuntu-noble$ git log --grep "btrfs: protect folio::private when attaching
extent buffer folios" origin/master-next
commit 78f0e5fd1fce33785a3454f5712a6f6160201bd5
Author: Qu Wenruo
Date: Thu Jun 6 11:01:51 2024 +0930
Subject
Hi Andre,
Great research! Lets have a look at that patch you found.
ubuntu-noble$ git log --grep "btrfs: protect folio::private when attaching
extent buffer folios" origin/master-next
commit 78f0e5fd1fce33785a3454f5712a6f6160201bd5
Author: Qu Wenruo
Date: Thu Jun 6 11:01:51 2024 +0930
Subject
Hi Mateusz,
ubuntu-jammy$ git log --grep "sunrpc: exclude from freezer when waiting for
requests:" origin/master-next
commit 4bf93c02ba241ccde7e00572138c1175ac09b242
Author: NeilBrown
Date: Fri Jun 7 09:10:48 2024 -0400
Subject: sunrpc: exclude from freezer when waiting for requests:
$ git des
Hi Mateusz,
ubuntu-jammy$ git log --grep "sunrpc: exclude from freezer when waiting for
requests:" origin/master-next
commit 4bf93c02ba241ccde7e00572138c1175ac09b242
Author: NeilBrown
Date: Fri Jun 7 09:10:48 2024 -0400
Subject: sunrpc: exclude from freezer when waiting for requests:
$ git des
Hi Marc,
You can use the test packages I made in comment #31 as a workaround for
the time being.
We are currently waiting on upstream to review the merge request here:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1608
There hasn't been a lot of movement, but we can't move forwar
Hi Marc,
You can use the test packages I made in comment #31 as a workaround for
the time being.
We are currently waiting on upstream to review the merge request here:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1608
There hasn't been a lot of movement, but we can't move forwar
Hi Marc,
You can use the test packages I made in comment #31 as a workaround for
the time being.
We are currently waiting on upstream to review the merge request here:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1608
There hasn't been a lot of movement, but we can't move forwar
Hi Krister,
Yes, we are still planning to get this released for focal. To be able to
release, it needs to pass all of its autopkgtests.
If you have a look here:
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/focal/update_excuses.html#e2fsprogs
Its failing on a few of them for some a
Hi Krister,
Yes, we are still planning to get this released for focal. To be able to
release, it needs to pass all of its autopkgtests.
If you have a look here:
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/focal/update_excuses.html#e2fsprogs
Its failing on a few of them for some a
Patch on Kernel Team mailing list:
Cover Letter:
https://lists.ubuntu.com/archives/kernel-team/2024-August/153135.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-August/153136.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Patch on Kernel Team mailing list:
Cover Letter:
https://lists.ubuntu.com/archives/kernel-team/2024-August/153135.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-August/153136.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2069961
[Impact]
On large systems, e.g. with 512 cpus or more, turbostat fails to run due
to exceeding the rlimit for number of files. 512 cpus requires 1028 file
descriptors, but the current limit is 999.
$ lscp
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2069961
[Impact]
On large systems, e.g. with 512 cpus or more, turbostat fails to run due
to exceeding the rlimit for number of files. 512 cpus requires 1028 file
descriptors, but the current limit is 999.
$ lscp
Noble (6.8) got fixed already in 6.8.0-40-generic as a part of bug
2070349.
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Released
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2069961
[Impact]
On large systems, e.g. with 512 cpus or more, t
Noble (6.8) got fixed already in 6.8.0-40-generic as a part of bug
2070349.
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Released
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2069961
[Impact]
On large systems, e.g. with 512 cpus or more, t
** Description changed:
- We're unable to run Turbostat on Turin 2P Volcano systems with core
- count greater than 400 on Ubuntu 22.04. On Ubuntu 24.04 turbostat works
- fine.
+ BugLink: https://bugs.launchpad.net/bugs/2069961
- The following commit fixes the turbostat problem :
+ [Impact]
** Description changed:
- We're unable to run Turbostat on Turin 2P Volcano systems with core
- count greater than 400 on Ubuntu 22.04. On Ubuntu 24.04 turbostat works
- fine.
+ BugLink: https://bugs.launchpad.net/bugs/2069961
- The following commit fixes the turbostat problem :
+ [Impact]
* Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: sts
--
* Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: sts
--
Hi Tormod,
Could you check 6.11.0-4-generic for Oracular in this particular ppa?
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
The 6.10 kernel in -proposed will be replaced by this one, or a newer
build eventually.
Just waiting for the kernel team to make the source avai
Hi Tormod,
Could you check 6.11.0-4-generic for Oracular in this particular ppa?
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
The 6.10 kernel in -proposed will be replaced by this one, or a newer
build eventually.
Just waiting for the kernel team to make the source avai
This should land in 5.15.0-121-generic and 6.8.0-44-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/2077044
Title:
zap_pid_ns_processes() gets stuck in a busy loop when zombie pr
This should land in 5.15.0-121-generic and 6.8.0-44-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077044
Title:
zap_pid_ns_processes() gets stuck in a busy loop when zombie processes
are
: Fix Released
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: Fix Committed
** Affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: Fix Committed
** Tags: sts
** Also
: Fix Released
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: Fix Committed
** Affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: Fix Committed
** Tags: sts
** Also
Patches are on kernel team mailing list.
https://lists.ubuntu.com/archives/kernel-team/2024-August/152811.html
https://lists.ubuntu.com/archives/kernel-team/2024-August/152812.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Patches are on kernel team mailing list.
https://lists.ubuntu.com/archives/kernel-team/2024-August/152811.html
https://lists.ubuntu.com/archives/kernel-team/2024-August/152812.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
fixing this isolcpus bug.
If a regression were to occur, it would affect cgroups V2 only, and it
could cause resource limits to be applied incorrectly in the worst case.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Jammy)
Impo
fixing this isolcpus bug.
If a regression were to occur, it would affect cgroups V2 only, and it
could cause resource limits to be applied incorrectly in the worst case.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Jammy)
Impo
Hi Doug,
You have done some awesome work! Thank you very much for debugging and
opening a merge request upstream.
I can reproduce the issue, and yes, your patch with the help of previous
authors does fix the issue.
Hopefully we can try and get the attention of the maintainers, and see
if they ar
Hi Doug,
You have done some awesome work! Thank you very much for debugging and
opening a merge request upstream.
I can reproduce the issue, and yes, your patch with the help of previous
authors does fix the issue.
Hopefully we can try and get the attention of the maintainers, and see
if they ar
Hi Doug,
You have done some awesome work! Thank you very much for debugging and
opening a merge request upstream.
I can reproduce the issue, and yes, your patch with the help of previous
authors does fix the issue.
Hopefully we can try and get the attention of the maintainers, and see
if they ar
** Also affects: xorg-server (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ub
** Also affects: xorg-server (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ub
** Also affects: xorg-server (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ub
Performing verification for Jammy.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvm
Performing verification for Jammy.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvm
Performing verification for Noble.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.47.0 (5-Feb-2023)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvme
Performing verification for Noble.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.47.0 (5-Feb-2023)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvme
Performing verification for Focal.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.45.5 (07-Jan-2020)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvm
Performing verification for Focal.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.45.5 (07-Jan-2020)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvm
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Performing verification for Noble.
I started a n2-standard-2 instance on Google cloud, running Noble.
I installed 6.8.0-39-generic from -updates, rebooted, and followed the
instructions in the
testcase.
$ sudo ./check md/001
md/001 (Raid with bitmap on tcp nvmet with opt-io-size over bitmap siz
Performing verification for Noble.
I started a n2-standard-2 instance on Google cloud, running Noble.
I installed 6.8.0-39-generic from -updates, rebooted, and followed the
instructions in the
testcase.
$ sudo ./check md/001
md/001 (Raid with bitmap on tcp nvmet with opt-io-size over bitmap siz
Performing verification for Noble.
I again started two T2A instances on Google Cloud, both running Noble.
One instance has:
6.8.0-39-generic #39-Ubuntu SMP PREEMPT_DYNAMIC Sat Jul 6 02:50:39 UTC 2024
The other, 6.8.0-41-generic from -proposed2:
6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri
Performing verification for Noble.
I again started two T2A instances on Google Cloud, both running Noble.
One instance has:
6.8.0-39-generic #39-Ubuntu SMP PREEMPT_DYNAMIC Sat Jul 6 02:50:39 UTC 2024
The other, 6.8.0-41-generic from -proposed2:
6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri
*** This bug is a duplicate of bug 2073267 ***
https://bugs.launchpad.net/bugs/2073267
** This bug has been marked a duplicate of bug 2073267
Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 2073267 ***
https://bugs.launchpad.net/bugs/2073267
** This bug has been marked a duplicate of bug 2073267
Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
--
You received this bug notification because you are a member of Kernel
Hi Arrigo,
Kernel SRU cycles are a little tricky... the Kernel Team make 150 kernels twice
a month, so not everything goes in the distro -proposed pocket.
This one is a respin, and hasn't made its way to the main -proposed pocket yet,
and because its a part of the security SRU cycle, it gets plac
Hi Dong,
There is nothing more to do. Don't worry about all these derivative
kernels spamming the comments, we just needed to verify the main
-generic kernel only. There will be more bot spam in the future, you can
ignore it.
Thanks,
Matthew
--
You received this bug notification because you are
Hi Dong,
There is nothing more to do. Don't worry about all these derivative
kernels spamming the comments, we just needed to verify the main
-generic kernel only. There will be more bot spam in the future, you can
ignore it.
Thanks,
Matthew
--
You received this bug notification because you are
Hi Arrigo,
Kernel SRU cycles are a little tricky... the Kernel Team make 150 kernels twice
a month, so not everything goes in the distro -proposed pocket.
This one is a respin, and hasn't made its way to the main -proposed pocket yet,
and because its a part of the security SRU cycle, it gets plac
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
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
*** 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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
*** 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
*** 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
*** This bug is a duplicate of bug 2076004 ***
https://bugs.launchpad.net/bugs/2076004
** This bug has been marked a duplicate of bug 2076004
Shows Unknown display with 6.8.0-39
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Beginning verification for noble
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
Each instance is running the GA kernel, 6.8.0-1012-aws.
One is -updates, the other is e2fsprogs from -proposed:
-
Hi everyone,
I see that Greg KH just assigned CVE-2024-35918 to "randomize_kstack:
Improve entropy diffusion".
I suppose that means that we cannot revert it now.
https://lore.kernel.org/linux-cve-announce/2024073029-clerk-
trophy-b84c@gregkh/T/
This is going to take some time.
Thanks,
Matthew
Hi Chris,
Yes, jammy-hwe-6.8 got fixed because Stefan Bader had to respin the kernel
for another regression anyway, so he opportunistically pulled it in.
For Noble, I think it will be part of the s2024.07.08 SRU cycle, as per
https://kernel.ubuntu.com/, as Manuel Diewald mentioned when I spoke to
Hi David,
Yes, it does indeed seem that the CVE has now been rejected.
https://lore.kernel.org/linux-cve-announce/2024073029-clerk-
trophy-b84c@gregkh/
https://nvd.nist.gov/vuln/detail/CVE-2024-35918
https://www.cve.org/CVERecord/?id=CVE-2024-35918
Maybe we can revert it after all!
I will have
Hi everyone,
$ cd Work/kernel/ubuntu-jammy/
~/Work/kernel/ubuntu-jammy$ git log --grep 'Revert "drm/qxl: simplify
qxl_fence_wait"'
commit 1b146e3dc802253fd9a6e29e2d3b06d003fe9182
Author: Alex Constantino
Date: Thu Apr 4 19:14:48 2024 +0100
Revert "drm/qxl: simplify qxl_fence_wait"
..
Beginning verification for jammy
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
I downgraded the HWE kernels down to GA kernels, and each is running
5.15.0-1066-aws.
One is -updates, the other
Beginning verification for focal
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
I downgraded the HWE kernels down to GA kernels, and each is running
5.4.0-1129-aws.
One is -updates, the other i
Performing verification for jammy-hwe-6.8
I started two T2A instances on google cloud, which are arm64, with
jammy.
One instance has:
6.8.0-39-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 10 16:59:11 UTC
2
The other, 6.8.0-40-generic from -proposed:
6.8.0-40-generic #40~22.04.3-Ubuntu
Hi everyone,
Keith, thanks for testing! It is fantastic news that the test kernel
fixes the issue, and our theory is correct, and we are on the right
track.
I also tested both test kernels myself, and can confirm that reverting
"randomize_kstack: Improve entropy diffusion" fixes the issue, and th
Hi everyone,
The Jammy HWE kernel will be rolling to the 6.8 kernel from Noble in a
couple days / or a week or so. The 6.5 mantic kernel is closed to any
new commits now, so best to just move to the 6.8 kernel now where this
is already fixed.
Thanks,
Matthew
--
You received this bug notificatio
Hi everyone,
$ cd Work/kernel/ubuntu-jammy/
~/Work/kernel/ubuntu-jammy$ git log --grep 'Revert "drm/qxl: simplify
qxl_fence_wait"'
commit 1b146e3dc802253fd9a6e29e2d3b06d003fe9182
Author: Alex Constantino
Date: Thu Apr 4 19:14:48 2024 +0100
Revert "drm/qxl: simplify qxl_fence_wait"
..
*** This bug is a duplicate of bug 2072755 ***
https://bugs.launchpad.net/bugs/2072755
** This bug has been marked a duplicate of bug 2072755
i915: Fixup regressions introduced with enabling single CCS engine
--
You received this bug notification because you are a member of Kernel
Package
Hi everyone,
$ cd Work/kernel/ubuntu-jammy/
~/Work/kernel/ubuntu-jammy$ git log --grep 'Revert "drm/qxl: simplify
qxl_fence_wait"'
commit 1b146e3dc802253fd9a6e29e2d3b06d003fe9182
Author: Alex Constantino
Date: Thu Apr 4 19:14:48 2024 +0100
Revert "drm/qxl: simplify qxl_fence_wait"
..
Hi everyone,
$ cd Work/kernel/ubuntu-jammy/
~/Work/kernel/ubuntu-jammy$ git log --grep 'Revert "drm/qxl: simplify
qxl_fence_wait"'
commit 1b146e3dc802253fd9a6e29e2d3b06d003fe9182
Author: Alex Constantino
Date: Thu Apr 4 19:14:48 2024 +0100
Revert "drm/qxl: simplify qxl_fence_wait"
..
Hi everyone,
The Jammy HWE kernel will be rolling to the 6.8 kernel from Noble in a
couple days / or a week or so. The 6.5 mantic kernel is closed to any
new commits now, so best to just move to the 6.8 kernel now where this
is already fixed.
Thanks,
Matthew
--
You received this bug notificatio
*** This bug is a duplicate of bug 2076004 ***
https://bugs.launchpad.net/bugs/2076004
** This bug has been marked a duplicate of bug 2076004
Shows Unknown display with 6.8.0-39
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Hi Chris,
Yes, jammy-hwe-6.8 got fixed because Stefan Bader had to respin the kernel
for another regression anyway, so he opportunistically pulled it in.
For Noble, I think it will be part of the s2024.07.08 SRU cycle, as per
https://kernel.ubuntu.com/, as Manuel Diewald mentioned when I spoke to
Performing verification for jammy-hwe-6.8
I started two T2A instances on google cloud, which are arm64, with
jammy.
One instance has:
6.8.0-39-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 10 16:59:11 UTC
2
The other, 6.8.0-40-generic from -proposed:
6.8.0-40-generic #40~22.04.3-Ubuntu
Beginning verification for noble
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
Each instance is running the GA kernel, 6.8.0-1012-aws.
One is -updates, the other is e2fsprogs from -proposed:
-
Beginning verification for jammy
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
I downgraded the HWE kernels down to GA kernels, and each is running
5.15.0-1066-aws.
One is -updates, the other
Beginning verification for focal
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
I downgraded the HWE kernels down to GA kernels, and each is running
5.4.0-1129-aws.
One is -updates, the other i
Hi David,
Yes, it does indeed seem that the CVE has now been rejected.
https://lore.kernel.org/linux-cve-announce/2024073029-clerk-
trophy-b84c@gregkh/
https://nvd.nist.gov/vuln/detail/CVE-2024-35918
https://www.cve.org/CVERecord/?id=CVE-2024-35918
Maybe we can revert it after all!
I will have
Hi everyone,
I see that Greg KH just assigned CVE-2024-35918 to "randomize_kstack:
Improve entropy diffusion".
I suppose that means that we cannot revert it now.
https://lore.kernel.org/linux-cve-announce/2024073029-clerk-
trophy-b84c@gregkh/T/
This is going to take some time.
Thanks,
Matthew
Hi everyone,
Keith, thanks for testing! It is fantastic news that the test kernel
fixes the issue, and our theory is correct, and we are on the right
track.
I also tested both test kernels myself, and can confirm that reverting
"randomize_kstack: Improve entropy diffusion" fixes the issue, and th
*** This bug is a duplicate of bug 2072755 ***
https://bugs.launchpad.net/bugs/2072755
** This bug has been marked a duplicate of bug 2072755
i915: Fixup regressions introduced with enabling single CCS engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
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
1 - 100 of 1087 matches
Mail list logo
