Public bug reported:
This is a request to make a change in the hv-kvp-daemon systemd service
which is part of the linux-cloud-tools-common package to ensure the hv-
kvp-daemon service starts before the walinuxagent service. The default
dependencies make hv-kvp-daemon wait until the whole system
I also confirm the kernel 4.4.0-104.127 in xenial-proposed fixes the
issue. I am able to mount my CephFS filesystem normally. Benjamin also
confirmed the kernel works for him in comments #26 and #27. I am
changing the tag to verification-done-xenial. Thanks!
** Tags removed:
Hi Joseph,
I'm able to reproduce Benjamin's original issue with kernel
4.4.0-103-generic #126-Ubuntu:
# mount -t ceph :6789:/ /mnt/mycephfs -o name=admin,secret=
mount error 5 = Input/output error
I don't get this problem with 4.4.0-101-generic #124-Ubuntu. I'm working
with Jay Vosburgh to test
I forgot to mention that I was still able to reproduce the bug with the
kernel you built with a revert of commit ff467fd from
http://kernel.ubuntu.com/~jsalisbury/lp1737033
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
On the running system after you rollback to the previous kernel, can you
paste your /etc/fstab for the filesystems that failed to mount and the
corresponding lines from mount -v? I assume the issues are with nfshome
and officeshare:
cat /etc/fstab | grep -i -e nfshome -e officeshare -e
I tested a kernel without the following commits from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728739 and I was
able to mount the CephFS filesystem successfully:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/commit/?id=f14ca6ac3b198f30ee138f02c3c7d380d165736e
FYI, this patch seems to have introduced a regression, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737033
--
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/1728739
Title:
@Marcelo, I have a reply from Madhuri:
Created By: Madhuri Kaniganti (portal) (07/06/2018 11:40 AM)
Just these two fixes needed:
IB/mlx5: Respect new UMR capabilities
I have confirmation from a user running NFS stress tests on Xenial with
this kernel and has not seen any issues. Changed tag to verification-
done-xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a
Created By: David Coronel (28/05/2018 4:28 PM)
Good day Sam, Jamie,
The kernel 4.4.0-128-generic #154 is now ready for testing by Nvidia:
linux | 4.4.0-128.154 | xenial-proposed | source
linux-image-4.4.0-128-generic | 4.4.0-128.154 | xenial-proposed | amd64, arm64,
armhf, i386, ppc64el, s390x
I have confirmation from the user who reported this that they have
tested the new kernel 4.4.0-128.154 in their test environment for a 24
hours stress test and could not reproduce the issue. I changed the tag
to verification done.
** Tags removed: verification-needed-xenial
** Tags added:
Marking bug as invalid as it looks like the root of the issue was with
the user's own module.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Add support for 4/6/8 channel sound in 16.04 LTS kernel for future GPUs.
This commit should be what is needed:
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=74ec118152ea494a25ebb677cbc83a75c982ac5f
ALSA: hda - Add missing NVIDIA GPU codec IDs to
Public bug reported:
Request to pull this patch from upstream into the next 4.15 kernel
update:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b2adf22fdfba85a6701c481faccdbbb3a418ccfc
This fixes a regression in SMB 2/3 reconnect detection. The fix has been
I have confirmation from a user who has done verification for this
kernel. Changing to verification-done-bionic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
This request is to pull in the following patch for NVMe bug from
https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp kernel:
===
This patch adds full memory barrier into nvme_dbbuf_update_and_check_event
function to ensure that the shadow doorbell is written
I have confirmation that the kernel in -proposed fixes the issue in
xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have confirmation that the kernel in -proposed fixes the issue in
xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1793430
Title:
Page leaking in
@Guillaume: I am Eric's colleague from comment #21. I was able to
reproduce the issue in Azure with your reproducer in comment #5. I'll
show Eric how I reproduced the issue and he'll be able to follow up with
you. Thanks!
--
You received this bug notification because you are a member of Kernel
I have a user who confirms the 4.15.0-39 kernel fixes this issue:
# uname -a
Linux 4.15.0-39-generic #42~16.04.1-Ubuntu SMP Wed Oct 24 17:09:54
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
# cat /proc/fs/fscache/stats
FS-Cache statistics
Cookies: idx=2 dat=283731 spc=0
Objects: alc=278557 nal=0
Hi Guillaume, would it be possible to provide step-by-step instructions
to reproduce this issue?
--
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/1796376
Title:
Bug #1739107 fix causes
bionic-tree/4.18.0-1004 with all the packages:
$ sudo dpkg -i
linux-modules-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb \
linux-modules-extra-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb
\
bionic-tree/4.18.0-1004:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1004-azure #4~18.04.1 SMP Wed Nov 21 20:07:48 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[6.337786] mlx4_core: Mellanox ConnectX core driver v4.0-0
[6.374260]
4.18.0-1004:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1004-azure #5~lp1794477 SMP Wed Nov 21 19:19:16 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[6.009608] mlx4_core: Mellanox ConnectX core driver v4.0-0
[6.045063] mlx4_ib_add: mlx4_ib:
4.18.0-1003:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1003-azure #4~lp1794477 SMP Wed Nov 21 18:32:18 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.701478] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.732267] mlx4_ib_add: mlx4_ib:
I can reproduce the issue in Azure with Ubuntu 18.04 and the kernel
linux-azure-edge 4.18.0.1004.5 from bionic-proposed.
I use an instance of type "Standard F4s_v2 (4 vcpus, 8 GB memory)"
I launch the instance and get the 4.15.0-1030-azure kernel:
$ lsb_release -a
No LSB modules are available.
Hi Chris. I spoke to Joseph and I think we have everything we need to
start the bisect. We'll get started and keep you posted.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477
Hi Joseph,
Is there a special way I should install these? I tried:
sudo dpkg -i *
But I get:
Selecting previously unselected package linux-azure-cloud-tools-4.17.0-1001.
(Reading database ... 56547 files and directories currently installed.)
Preparing to unpack
These are the packages I see installed out of the box in the instance:
ubuntu@lp1794477:~/41701001$ dpkg -l | grep 4.15.0-1030.31 | sort
ii linux-azure-cloud-tools-4.15.0-1030 4.15.0-1030.31
amd64Linux kernel version specific cloud tools for version
I can see the Mellanox devices with that 4.17.0-1001-azure kernel.
I installed the new kernel:
sudo dpkg -i linux-
modules-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux-
modules-extra-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux-
Hi Marcelo,
Maybe I'm doing something wrong but I still don't see the Mellanox
devices with this 4.18.0-1005 kernel from the CKT PPA:
ubuntu@lp1794477:~$ sudo add-apt-repository ppa:canonical-kernel-team/ppa
ubuntu@lp1794477:~$ sudo apt install linux-azure-edge
ubuntu@lp1794477:~$ sudo
4.18.0-1002:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1002-azure #3~lp1794477 SMP Wed Nov 21 16:41:12 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.723350] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.751281] mlx4_ib_add: mlx4_ib:
4.18.0-1001:
ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1001-azure #2~lp1794477 SMP Wed Nov 21 16:06:45 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.701988] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.730013] mlx4_ib_add: mlx4_ib:
Public bug reported:
There was a previous request in bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
the IO scheduler to NOOP in linux-azure. The other schedulers were
turned off and NOOP was made the default.
However with new upstream releases, new schedulers where
Public bug reported:
This is a request to enable CONFIG_NO_HZ_FULL=y in the linux-azure
kernels(currently 4.15 and 4.18) in order to increase NVME disks
performance.
The current CONFIG_NO_HZ configuration in linux-azure kernels is the
following (tested on 4.15.0-1037, 4.15.0-1039 and
Public bug reported:
The InfiniBand configuration settings from the 4.15 linux-azure kernel
are not in the 4.18 linux-azure kernel.
This is a request to apply the same InfiniBand settings to the 4.18
linux-azure kernel.
The following settings are only in the 4.15 linux-azure kernel (tested
with
[VERIFICATION BIONIC]
I can modprobe the mq-deadline, kyber and bfq schedulers but it looks
like doing a modprobe of the cfq and deadline schedulers doesn't list
them as choices in the available schedulers:
# uname -r
4.18.0-1009-azure
# modprobe bfq
# modprobe cfq-iosched
# modprobe
@lazamarius1: Just to clarify, the fix is scheduled to go in the 4.15
kernel in Bionic which is the same kernel as the Xenial HWE kernel. So
there's no need to add anything to the Affects section. You will see a
new linux-hwe 4.15 kernel in xenial-proposed once this is ready to test.
Thanks!
--
Public bug reported:
Host changes have altered how the PCI GUID is presented to the guest and
the patches for PCI IDs in 4.15.0-1037 do not properly handle the new
condition.
Impact:
Instances with multiple GPUs are only seeing one.
Workaround:
4.15.0-1036 does not have this behavior.
You can clone the ubuntu-xenial kernel:
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git
And then grep for the commit you're looking for. There's a few different
ways to do it, I do:
git log --oneline | grep "Expose SMT control init function"
--
You received this bug notification
@overlord: AFAIK, there is no simple reproducer test case for this
issue. The ideal testing scenario for a bug and fix like this one would
be for each user who reported this issue to use a test kernel with the
fix in their environment and report back if the issue still manifests or
not after some
Hi overlord. An easy way to check the updates included in released
kernels is to look at the "-changes" mailing list for your Ubuntu
release.
In this situation it would be https://lists.ubuntu.com/archives/xenial-
changes/
And you can find that new kernel here:
I just found out about this. I wanted to get rid of the screen tearing
that I observed on my Nitro AN515-53 laptop running Ubuntu 18.04.3 LTS
with NVIDIA GeForce GTX 1050 Mobile GPU.
I used https://askubuntu.com/a/020 and set nvidia_drm modeset=1 but
then my external monitors didn't work
Public bug reported:
In Azure, updating an instance to the latest Azure optimised fips-
updates kernel (4.15.0-2007-azure-fips) leaves the system in an
unbootable state.
The serial console shows the following and reboots:
Checking kernel image: /boot/vmlinuz-4.15.0-2007-azure-fips
Kernel
** Attachment added: "Screenshot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893985/+attachment/5407094/+files/fips-azure-crash.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
46 matches
Mail list logo