I built the current upstream master branch of adcli, and it too fails on
Bionic:
https://paste.ubuntu.com/p/vsgfxyb9X7/
This must be why the exact same patches work on Focal. The problem
probably isn't adcli itself, but more likely a library it depends on.
# apt depends adcli
adcli
Depends: li
med => Fix Released
** Changed in: adcli (Ubuntu Bionic)
Status: New => In Progress
** Changed in: adcli (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: adcli (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug no
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906627
Title:
adcli fails, can't contact LDAP server
To manage notifications about this bug go to:
https://bugs.launc
** Also affects: adcli (Ubuntu Bionic)
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/1906627
Title:
adcli fails, can't contact LDAP server
To manage noti
Hi Benjamin,
I have good news. The SRU has completed, and the new kernels have now
been released to -updates. Their versions are:
Bionic:
4.15.0-126-generic
Focal:
5.4.0-56-generic
You can go ahead and schedule that maintenance window now, to install
the latest kernel from -updates. These kerne
Hi Benjamin,
No worries about being busy.
Now, the kernel is scheduled to be released early next week, around the
30th of November. I think at this stage it is best to wait it out and
install the kernel once it reaches -updates.
That way you will have a fixed kernel that is supported by livepatc
Verification for sssd on Bionic:
The customer tested sssd from -updates, version 1.16.1-1ubuntu1.6 and
the package from -proposed, version 1.16.1-1ubuntu1.7.
Begins:
Before applying the patch [package from -proposed] I confirmed open
ports to our domain controllers using ss and grepping for the
Verification for sssd on Focal:
The customer tested sssd from -updates, version 2.2.3-3 and the package
from -proposed, version 2.2.3-3ubuntu0.1.
Begins:
I have successfully tested the [package from -proposed] on Ubuntu
20.04.1.
Before applying the patch [package from -proposed] I confirmed ope
Performing verification for Bionic.
Since Benjamin hasn't responded, I will try and verify the best I can.
I made a instance on AWS. I used a c5d.large instance type, and added
8gb extra EBS storage.
I installed the latest kernel from -updates to get a performance
baseline. kernel is 4.15.0-124-
Performing verification for Focal.
Since Benjamin hasn't responded, I will try and verify the best I can.
I made a instance on AWS. I used a c5d.large instance type, and added
8gb extra EBS storage.
I installed the latest kernel from -updates to get a performance
baseline. kernel is 5.4.0-54-gen
Performing verification of adcli on Bionic
The patches for Bionic are a bit more involved, as it adds the whole
--use-ldaps ecosystem.
Firstly, I installed adcli 0.8.2-1 from -updates. The manpage did not
have any mention of --use-ldaps, and if I ran a command with --use-
ldaps, it would complain
Performing verification of adcli on Focal
The patches for Focal are a bit more involved, as it adds the whole
--use-ldaps ecosystem.
Firstly, I installed adcli 0.9.0-1 from -updates. The manpage did not
have any mention of --use-ldaps, and if I ran a command with --use-
ldaps, it would complain i
Performing verification of adcli on Groovy.
Groovy only required one patch, which fixed a missed enablement of
--use-ldaps for the testjoin and update commands.
So, just testing those two.
I installed adcli 0.9.0-1ubuntu1 from -updates, and I set everything up
by issuing a join command. After th
Hi Tobias, thanks for testing and verifying! I really appreciate it, and
it's good to hear that everything works.
I'll just add some of my own test output below, and we should be good to
go for a release to -updates in about a week's time.
--
You received this bug notification because you are a
Hi Benjamin,
The kernel team have built the next kernel update, and they have placed
it in -proposed for verification.
The versions are 4.15.0-125-generic for Bionic, and 5.4.0-55-generic for
Focal.
Can you please schedule a maintenance window for the Launchpad git
server, to install the new ker
Performing verification for Bionic.
I enabled -proposed and installed 4.15.0-125-generic to a i3.8xlarge AWS
instance.
>From there, I followed the testcase steps:
$ uname -rv
4.15.0-125-generic #128-Ubuntu SMP Mon Nov 9 20:51:00 UTC 2020
$ lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda
Performing verification for Focal.
I enabled -proposed and installed 5.4.0-55-generic to a i3.8xlarge AWS
instance.
>From there, I followed the testcase steps:
$ uname -rv
5.4.0-55-generic #61-Ubuntu SMP Mon Nov 9 20:49:56 UTC 2020
$ lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda202:
Performing verification for Groovy.
I enabled -proposed and installed 5.8.0-30-generic to a i3.8xlarge AWS
instance.
>From there, I followed the testcase steps:
$ uname -rv
5.8.0-30-generic #32-Ubuntu SMP Mon Nov 9 21:03:15 UTC 2020
$ lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda202
Performing verification for Focal.
I created a i3.large instance on AWS, since it has 1x NVMe drive that
supports trim and block discard.
I ensured that I could reproduce the problem with 5.4.0-54-generic from
-updates, and I followed the instructions in the Testcase section, and
the final fstrim
** Description changed:
[Impact]
Microsoft has released a new security advisory for Active Directory (AD)
which outlines that man-in-the-middle attacks can be performed on a LDAP
server, such as AD DS, that works by an attacker forwarding an
authentication request to a Windows LDAP se
Attached is a revised debdiff for adcli in Bionic.
** Patch added: "adcli debdiff for Bionic v2"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432874/+files/lp1868703_adcli_bionic_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
B
Attached is a revised debdiff for adcli for Focal.
** Patch added: "adcli debdiff for Focal v2"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432871/+files/lp1868703_adcli_focal_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bug
Attached is a debdiff for adcli in Groovy.
** Patch added: "adcli debdiff for groovy"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432870/+files/lp1868703_adcli_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Attached is a debdiff for adcli for Hirsute.
** Patch added: "adcli debdiff for hirsute"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432869/+files/lp1868703_adcli_hirsute.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Attached is a revised debdiff for sssd for Bionic.
** Patch added: "sssd debdiff for Bionic v2"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432867/+files/lp1868703_sssd_bionic_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bug
Attached is a revised debdiff for sssd for Focal.
** Patch added: "sssd debdiff for Focal v2"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432866/+files/lp1868703_sssd_focal_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Patch removed: "adcli debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432450/+files/lp1868703_adcli_focal.debdiff
** Patch removed: "sssd debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432451/+files
** Description changed:
[Impact]
Microsoft has released a new security advisory for Active Directory (AD)
which outlines that man-in-the-middle attacks can be performed on a LDAP
server, such as AD DS, that works by an attacker forwarding an
authentication request to a Windows LDAP se
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868703
Title:
Support "ad_use_ldaps" flag for new AD requirements (ADV190023)
To manage notifications about this bug go to:
Attached is a sssd debdiff for Focal
** Patch added: "sssd debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432451/+files/lp1868703_sssd_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Attached is a sssd debdiff for Bionic
** Patch added: "sssd debdiff for Bionic"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432453/+files/lp1868703_sssd_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Attached is a debdiff for adcli on Focal.
** Patch added: "adcli debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432450/+files/lp1868703_adcli_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Attached is a adcli debdiff for Bionic
** Patch added: "adcli debdiff for Bionic"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432452/+files/lp1868703_adcli_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Summary changed:
- Support new AD requirements (ADV190023)
+ Support "ad_use_ldaps" flag for new AD requirements (ADV190023)
** Description changed:
- Please backport the following patch to add the option ad_use_ldaps.
+ [Impact]
- With this new boolean option the AD provider should only u
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
Hi Tobias, Thorstein, and anyone who is after a backport of these
patches,
I have completed backporting the below patches to the Bionic and Focal
adcli and sssd packages, and I am looking for some help with testing. If
you have some spare time, a Windows Active Directory server available,
and some
** Changed in: adcli (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: adcli (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: adcli (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: adcli (Ubuntu Focal)
I
Patches have been submitted to the Ubuntu kernel mailing list:
Patchset for Bionic:
https://lists.ubuntu.com/archives/kernel-team/2020-October/114166.html
https://lists.ubuntu.com/archives/kernel-team/2020-October/114167.html
https://lists.ubuntu.com/archives/kernel-team/2020-October/114168.html
h
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1898786
[Impact]
Systems that utilise bcache can experience extremely high IO wait times
when under constant IO pressure. The IO wait times seem to stay at a
consistent 1 second, and never drop as long as the bcache s
ed => Medium
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
- Hello,
+ BugLink: https://bugs.launchpad.net/bugs/1898786
Attached is a debdiff for gnome-shell for Focal with the required
patches to implement VMware Horizon SSO support.
** Patch added: "gnome-shell debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886592/+attachment/5423914/+files/lp1886592_focal.debdiff
--
You rece
Attached is a debdiff for Bionic which implements support for VMware
Horizon SSO in gnome-shell.
** Patch added: "gnome-shell debdiff for Bionic"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886592/+attachment/5423915/+files/lp1886592_bionic.debdiff
--
You received this bug no
** Description changed:
[Impact]
VMware Horizon is a VDI product that runs atop of VMware's normal
virtualisation stack, and it supports SSO authentication for login.
In the past, the VMware Horizon agent has been pretty buggy, and
requires SSO patches to be present to function, ot
Hi Benjamin,
Great to hear that the early results look promising.
Yes, let's give it a week, so we can ensure that these patches do their
job under the high loads the git server faces each day over the week.
If things still look good early next week, I will go ahead and prepare
the patches for S
Hi Benjamin,
I think Dan is onto something.
The following commit was merged in upstream 5.5-rc1, but was backported
to 4.15.0-87-generic through upstream stable:
commit 9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b
Author: Coly Li
Date: Wed Nov 13 16:03:24 2019 +0800
Subject: bcache: at least try
Verifying for xenial:
I enabled -proposed, and installed 4.4.0-1116-aws:
$ uname -rv
4.4.0-1116-aws #129-Ubuntu SMP Tue Sep 29 18:17:22 UTC 2020
I rebooted, and was able to ssh in, and dmesg was clean.
I then installed 4.4.0-192-generic:
$ uname -rv
4.4.0-192-generic #222-Ubuntu SMP Tue Sep 29
Hello @shaynagar, thank you very much for reporting! We will look into
this asap.
More details: 4.4.0-190-generic is fine, 4.4.0-191-generic contains the
regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Description changed:
- This is a POTENTIAL REGRESSION.
+ [Impact]
- This issue occurs on one of the AWS instance "t2.medium"
+ The new xe
Performing verification:
First, reproducing on older kernel:
$ uname -rv
4.4.0-190-generic #220-Ubuntu SMP Fri Aug 28 23:02:15 UTC 2020
$ grep "clocksource" /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc"
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.4.0-190-generic
root=UUID=f6
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
h support block discard will be affected.
Traditional hard disks, or SSD devices which do not support block
discard would not be affected.
If a regression were to occur, users could work around the issue by
running "mkfs.xfs -K " which would skip block discard entirely.
** Affects: linux
d to upstream stable, and are trusted by
the community.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Also affects:
*** This bug is a duplicate of bug 1756315 ***
https://bugs.launchpad.net/bugs/1756315
** This bug has been marked a duplicate of bug 1756315
fstrim and discard operations take too long to complete - Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bug
Hello Alexandre,
I tried to reproduce this bug, and I believe it has been fixed.
I started a i3.4xlarge instance on AWS, with Xenial as the distro:
$ uname -rv
4.4.0-1112-aws #124-Ubuntu SMP Fri Jul 24 11:10:25 UTC 2020
>From there, I checked the NVMe disks:
$ lsblk
NAMEMAJ:MIN RM SIZE RO
As promised, I have an update on the lab machine I left running
ksm_refcnt_overflow.sh for a week straight.
The machine was running 4.15.0-116-generic from -proposed:
$ uname -rv
4.15.0-116-generic #117-Ubuntu SMP Fri Aug 28 16:04:22 UTC 2020
$ uptime
04:36:14 up 7 days, 1 min, 1 user, load av
How about you try a slightly older kernel then:
To install 5.4.0-31-generic:
$ sudo apt install linux-image-5.4.0-31-generic linux-
modules-5.4.0-31-generic linux-modules-extra-5.4.0-31-generic linux-
headers-5.4.0-31-generic linux-headers-5.4.0-31
Then reboot your computer. Do the same as you d
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1894591
[Impact]
The default clocksource for a KVM VM is kvm-clock, and I happen to need
tsc.
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
kvm-clock
If I edit /etc/default/grub and
.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Xenial)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
@braingateway
Can you please try booting into the 5.4.0-42-generic kernel and see if
that works?
When you turn your computer on, press and hold the shift key to access the GRUB
boot menu.
Select "Advanced Options" and then "Ubuntu, with Linux 5.4.0-42-generic"
If 5.4.0-42-generic works and 5.4.
As requested by the kernel team (in https://lists.ubuntu.com/archives
/kernel-team/2020-August/112775.html), I will do some additional testing
for this SRU to really make sure it won't cause any regressions.
I provisioned a lab machine on segmaas, running Bionic. I installed the
4.15.0-116-generic
Verification steps for focal:
Again, I made sure I can reproduce on the existing 5.4.0-42-generic
kernel.
I copied ksm_refcnt_overflow.sh and zero_page_refcount.c to the VM, and
built the kernel module, and inserted it into the kernel:
$ sudo insmod zero_page_refcount.ko
$ cat /proc/zero_page_re
Verification steps for Bionic:
First, I made sure I could reproduce the problem on 4.15.0-115-generic.
I made a fresh Bionic VM, and copied over the ksm_refcnt_overflow.sh and
zero_page_refcound.c files.
I built the kernel module, and inserted it into the kernel.
>From there, I checked the zero
As 5.8.0-16-generic has now been released to the -release pocket,
CONFIG_SECURITY_DMESG_RESTRICT is now enabled in Groovy. Marking the
changes to the kernel as Fix Released.
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification be
As per my most recent email to ubuntu-devel, I am marking the changes to
util-linux as Won't Fix.
Relevant mailing list discussion (for future reference):
Ansgar responded on debian-devel mentioning that adding cap_syslog to
dmesg enables the user to clear the kernel log buffer:
https://lists.de
I asked the customer to test 4.15.0-114-generic on Xenial HWE from
-proposed on their HP DL360 Gen10 machines with the Intel Xeon Gold 5120
CPU. The machine has Sub-NUMA Clustering enabled and it is active.
The machine boots successfully, and there are no call traces or kernel
oops present:
# una
I installed 4.15.0-114-generic from -proposed to my test client machine,
which is a Ubuntu 18.04 Desktop VM.
I mounted two NFS shares, one with sec=sys, and the other with
sec=krb5p. I then opened each share up in separate tabs in Nautilus.
I then CUT a file from the sec=sys share, and PASTED it
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: cloud-init (Ubuntu Xenial)
Status: In Progress => Won't Fix
** Changed in: cloud-init (Ubuntu Bionic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a
Hi @pau-capdevila
Your USB problem is unrelated to the issue in this bug, since your USB
device fails to do the initial handshake and enumeration.
> usb 1-1.2.1: device descriptor read/64, error -32
>From /usr/include/asm-generic/errno-base.h, Error -32 is:
#define EPIPE 32 /* Bro
Hi @jeremyn54
> the error can be consistently reproduced on both signed and testing
kernels.
Reproduced on the test kernel? The one that I built in the ppa? If
that's the case, then "usb: handle warm-reset port requests on hub
resume" might not be to blame after all.
I had a look at your kernel
Wrote to debian-devel to see if upstream is interested in carrying the
debian postinstall changes for util-linux: https://lists.debian.org
/debian-devel/2020/08/msg00107.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Attached is a script to create and destroy VMs in a loop, to try and
increment the zero_page reference counter.
** Attachment added: "Reproducer script to create and destroy VMs"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837810/+attachment/5402013/+files/ksm_refcnt_overflow.sh
--
Attached is a kernel module which lets you see the contents of the
zero_page reference counter, and to set it to near overflow.
** Attachment added: "kernel module to view zero_page reference counter"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837810/+attachment/5402014/+files/zero_
** Summary changed:
- qemu instance gets paused with error: kvm run failed Bad address
+ KVM: Fix zero_page reference counter overflow when using KSM on KVM compute
host
** Description changed:
- We are occasionally running into the below qemu error on our Ubuntu16
- KVM hypervisors managed usi
ee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837810
Title:
@jeremyn54
Thanks for testing the test kernel. I suppose this means that "usb:
handle warm-reset port requests on hub resume" is still causing us
trouble.
@everyone
Can you please unplug all USB devices from your computer, and connect
them one by one until you find the device which causes the "u
The customer that suffered the perceived regression enabled -proposed
and installed the 4.15.0-113-generic kernel to their Bionic test
machine.
This test machine has had its non-spec complaint USB cable replaced with
a fresh known good USB compliant cable.
The 4.15.0-113-generic kernel performed
Attached is a rebased debdiff for util-linux, which implements the
permission changes to the dmesg binary.
** Patch removed: "util-linux debdiff for Groovy"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+attachment/5395389/+files/lp1886112_util-linux_groovy.debdiff
** Patch add
Hello @pooja-9, @kphatak-pf9 and @vlee,
You wouldn't happen to have Kernel Samepage Merging (KSM) enabled on
your compute nodes would you?
You can check by looking at the value of:
$ cat /sys/kernel/mm/ksm/run
If it is 1, your nodes have it enabled, and if it is 0 or "missing", you
don't have i
@bamoqi, @speedym, @david-sinnott-morgan:
I have prepared a test kernel based on 5.4.0-42-generic, for Ubuntu 20.04 in
the following ppa.
It hasn't finished building yet, Launchpad is taking a long time. Please make
sure it has finished building before installing.
https://launchpad.net/~mruffe
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1887607
[Impact]
There is a bug in NFS v4.1 that causes a large amount of RPC calls
between a client and server when a previous RPC call is interrupted.
This uses a large amount of bandwidth and can saturate the netwo
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1887607
[Impact]
There is a bug in NFS v4.1 that causes a large amount of RPC calls
between a client and server when a previous RPC call is interrupted.
This uses a large amount of bandwidth and can saturate the netwo
** Summary changed:
- NFS4.2: Cutting and Pasting files from NFS sec=sys to NFS sec=krb5p causes
NFS to hang
+ NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between
client and server
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1887607
[Impact]
As a final sanity check, I built a new debian-installer monolithic
netinstall ISO image, along with the usual vmlinuz / initrd.gz files.
When I built them, I enabled -proposed, and debootstrap-udeb
1.0.95ubuntu0.7 was included in the generated MANIFEST.udeb file.
The ISO images and initrd.gz files
Performing verification of debootstrap using Mauricio's script from
comment #10.
Focal
==
Original
First, using debootstrap from -updates:
$ apt-cache policy debootstrap | grep Installed
Installed: 1.0.118ubuntu1.1
$ tail -n1 *-focal-*.log
==> debootstrap-updates-focal-buildd-http
Performing verification of debootstrap in -proposed using Mauricio's
script from comment #10.
Bionic
==
Original
First, using debootstrap from -updates:
$ apt-cache policy debootstrap | grep Installed
Installed: 1.0.95ubuntu0.6
$ tail -n1 *-bionic-*.log
==> debootstrap-updates-bio
I looked into the autopkgtest regressions.
The pbuilder and sbuilder failures are due to them attempting to build
procenv in a Groovy chroot which was made with debootstrap. procenv
currently FTBFS on Groovy, due to changes in GCC10 to -Werror=format-
overflow.
```
gcc -DHAVE_CONFIG_H -I. -I..
Public bug reported:
[Impact]
procenv is currently FTBFS on Ubuntu 20.10 Groovy Gorilla with GCC 10
version (Ubuntu 10.2.0-3ubuntu1) 10.2.0.
Details:
```
gcc -DHAVE_CONFIG_H -I. -I.. -I . -I ./platform -I ./platform/linux -D
PROCENV_PLATFORM_LINUX -pedantic -std=gnu99 -Wall -Wunused
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Eoan)
Assignee: Matthew Ruffell (mruffell) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Description changed:
- This bug tracks the reapplication of "usb: handle warm-reset port
- requests on hub resume".
+ [Impact]
+
+ We wish to reapply "usb: handle warm-reset port requests on hub resume".
We reverted "usb: handle warm-reset port requests on hub resume" from
- the Ubuntu ke
** No longer affects: linux (Ubuntu Focal)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => In Progress
--
You received this bug not
Attached is a debdiff for util-linux which implements the permission and
capability changes to the dmesg binary.
** Patch added: "util-linux debdiff for Groovy"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+attachment/5395389/+files/lp1886112_util-linux_groovy.debdiff
--
You
Attached is a procps debdiff for groovy, which adds documentation to
/etc/sysctl.d/10-kernel-hardening.conf and a commented out way to
disable DMESG_RESTRICT.
** Patch added: "procps debdiff for Groovy"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+attachment/5395388/+files/lp1
I emailed Seth Forshee asking about what happens when Groovy's kernel
becomes Focal's HWE kernel, and he mentioned that the kernel team has
processes in place to handle config changes, and that it isn't a
problem.
So we will go with the more secure by default way, and enable
CONFIG_SECURITY_DMESG_
The VM on the left is using the current 18.04.4 LTS mini.iso provided
from http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main
/installer-amd64/current/images/netboot/ with a date of 2020-01-30.
The VM on the right is using the mini.iso I created that contains the
test debootstrap package,
501 - 600 of 829 matches
Mail list logo
