[Kernel-packages] [Bug 1812978] Re: rtnetlink.sh in net from ubuntu_kernel_selftests fails

2019-05-24 Thread Sean Feole
I'm seeing similar , possibly related failures on Bionic linux-aws, 
4.15.0-1040.42, 
I'm going to start consolidating this bug to track these failures on the 
various clouds.

05/20 17:49:07 DEBUG| utils:0153| [stdout] 

05/20 17:49:09 DEBUG| utils:0153| [stdout] test_bpf: ok
05/20 17:49:09 DEBUG| utils:0153| [stdout] ok 1..8 selftests: test_bpf.sh 
[PASS]
05/20 17:49:09 DEBUG| utils:0153| [stdout] selftests: netdevice.sh
05/20 17:49:09 DEBUG| utils:0153| [stdout] 

05/20 17:49:09 DEBUG| utils:0153| [stdout] SKIP: enp4s0: interface already 
up
05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: enp4s0: ethtool list 
features
05/20 17:49:09 ERROR| utils:0153| [stderr] Cannot get register dump: 
Operation not supported
05/20 17:49:09 DEBUG| utils:0153| [stdout] SKIP: enp4s0: ethtool dump not 
supported
05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: enp4s0: ethtool stats
05/20 17:49:09 DEBUG| utils:0153| [stdout] SKIP: enp4s0: interface kept up
05/20 17:49:09 DEBUG| utils:0153| [stdout] ok 1..9 selftests: netdevice.sh 
[PASS]
05/20 17:49:09 DEBUG| utils:0153| [stdout] selftests: rtnetlink.sh
05/20 17:49:09 DEBUG| utils:0153| [stdout] 

05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: policy routing
05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: route get
05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: tc htb hierarchy
05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: gre tunnel endpoint
05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: bridge setup
05/20 17:49:11 DEBUG| utils:0153| [stdout] PASS: ipv6 addrlabel
05/20 17:49:11 DEBUG| utils:0153| [stdout] PASS: set ifalias 
4488186b-9d9c-473a-89bc-29dba7fd5d44 for test-dummy0
05/20 17:49:11 ERROR| utils:0153| [stderr] RTNETLINK answers: Operation not 
supported
05/20 17:49:11 DEBUG| utils:0153| [stdout] FAIL: can't add vrf interface, 
skipping test
05/20 17:49:11 DEBUG| utils:0153| [stdout] PASS: vxlan
05/20 17:49:11 DEBUG| utils:0153| [stdout] FAIL: can't add fou port , 
skipping test
05/20 17:49:11 ERROR| utils:0153| [stderr] RTNETLINK answers: Operation not 
supported
05/20 17:49:11 DEBUG| utils:0153| [stdout] FAIL: can't add macsec 
interface, skipping test
05/20 17:49:11 DEBUG| utils:0153| [stdout] not ok 1..10 selftests:  
rtnetlink.sh [FAIL]

** Summary changed:

- rtnetlink.sh in net from ubuntu_kernel_selftests failed on Cosmic
+ rtnetlink.sh in net from ubuntu_kernel_selftests fails

** Also affects: linux-aws (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-aws (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux-aws (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-kernel-tests
   Status: New => Confirmed

-- 
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/1812978

Title:
  rtnetlink.sh in net from ubuntu_kernel_selftests fails

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-aws source package in Cosmic:
  New

Bug description:
  There are several failures in this test:
* ipv6 addrlabel
* macsec
* ipsec

  $ sudo ./rtnetlink.sh 
  PASS: policy routing
  PASS: route get
  PASS: tc htb hierarchy
  PASS: gre tunnel endpoint
  PASS: gretap
  PASS: ip6gretap
  PASS: erspan
  PASS: ip6erspan
  PASS: bridge setup
  FAIL: ipv6 addrlabel
  PASS: set ifalias 485dc5aa-b024-4952-88a7-414355fc2bdc for test-dummy0
  PASS: vrf
  PASS: vxlan
  FAIL: can't add fou port , skipping test
  *** stack smashing detected ***:  terminated
  ./rtnetlink.sh: line 468:  5132 Aborted (core dumped) ip 
macsec show > /dev/null
  FAIL: macsec
  ./rtnetlink.sh: line 527:  5146 Terminated  ip x m > $tmpfile
  FAIL: ipsec

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-14-generic 4.18.0-14.15
  ProcVersionSignature: User Name 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 23 09:53 seq
   crw-rw 1 root audio 116, 33 Jan 23 09:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: 

[Kernel-packages] [Bug 1829180] Re: linux-azure: 4.18.0-1019.19 -proposed tracker

2019-05-24 Thread Sean Feole
Regression Testing:

amd64

monotonic_time: (1774959): clock test in monotonic_time will fail on Azure 
Instances
ubuntu_kernel_selftests:(1830016): run_netsocktests from net in 
ubuntu_kernel_selftests failed with Socket type not supported
ubuntu_ltp_syscalls:(1819116): sync_file_range02 in ubuntu_ltp_syscalls fails 
C/D
ubuntu_lxc: (1821152): lxc-test-no-new-privs failed with Temporary failure 
resolving 'archive.ubuntu.com'
ubuntu_unionmount_overlayfs_suite:(1727290) ubuntu_unionmount_overlayfs_suite 
failed on Azure


** Tags added: regression-testing-passed

-- 
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/1829180

Title:
  linux-azure: 4.18.0-1019.19 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1829179 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829186
  phase: Testing
  phase-changed: Monday, 20. May 2019 10:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829180/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1727290] Re: ubuntu_unionmount_overlayfs_suite failed on Azure

2019-05-24 Thread Sean Feole
So far the previous comment has cropped up on the following instance
types:

- Basic_A2
- Standard_B1ms
- Standard_D2_v3
- Standard_D2s_v3
- Standard_D16s_v3
- Standard_A2_v2
- Standard_F2s_v2
- Standard_F32s_v2
- Standard_E2s_v3
- Standard_F1s
- Standard_D11_v2
- Standard_L4s
- Standard_L8s_v2

-- 
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/1727290

Title:
  ubuntu_unionmount_overlayfs_suite failed on Azure

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Kernel 4.15.0-1022.23 azure
  This test has failed on all the azure instances this cycle, it looks like it 
has stopped at the "rename-empty-dir" test:

TEST rename-file.py:110: Rename file over a dir
./run --rename /mnt/a/foo108/ /mnt/a/empty108/ -E ENOTDIR
./run --rename /mnt/a/foo108/ /mnt/a/dir108/ -E ENOTDIR
./run --open-file /mnt/a/foo108/ -r -R :xxx:yyy:zzz -E ENOTDIR
TEST rename-file.py:121: Rename file over parent dir
./run --rename /mnt/a/foo109/ /mnt/a -E ENOTDIR
./run --open-file /mnt/a/foo109/ -r -R :xxx:yyy:zzz -E ENOTDIR
***
*** ./run --ov --ts=0 rename-empty-dir
***
TEST rename-empty-dir.py:10: Rename empty dir and rename back
./run --rename /mnt/a/empty100 /mnt/a/no_dir100 -E EXDEV
/mnt/a/empty100: Expected error (Invalid cross-device link) was not 
produced

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1727290/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1727290] Re: ubuntu_unionmount_overlayfs_suite failed on 4.15 Azure

2019-05-24 Thread Sean Feole
This is affecting azure linux-azure cosmic 4.18.0-1019.19.

Logs attached.

** Also affects: linux-azure (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: azure cosmic

** Attachment added: "client.DEBUG-azure-union"
   
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1727290/+attachment/5266283/+files/client.DEBUG-azure-union

** Changed in: linux-azure (Ubuntu)
   Status: New => Confirmed

** Summary changed:

- ubuntu_unionmount_overlayfs_suite failed on 4.15 Azure
+ ubuntu_unionmount_overlayfs_suite failed on Azure

-- 
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/1727290

Title:
  ubuntu_unionmount_overlayfs_suite failed on Azure

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Kernel 4.15.0-1022.23 azure
  This test has failed on all the azure instances this cycle, it looks like it 
has stopped at the "rename-empty-dir" test:

TEST rename-file.py:110: Rename file over a dir
./run --rename /mnt/a/foo108/ /mnt/a/empty108/ -E ENOTDIR
./run --rename /mnt/a/foo108/ /mnt/a/dir108/ -E ENOTDIR
./run --open-file /mnt/a/foo108/ -r -R :xxx:yyy:zzz -E ENOTDIR
TEST rename-file.py:121: Rename file over parent dir
./run --rename /mnt/a/foo109/ /mnt/a -E ENOTDIR
./run --open-file /mnt/a/foo109/ -r -R :xxx:yyy:zzz -E ENOTDIR
***
*** ./run --ov --ts=0 rename-empty-dir
***
TEST rename-empty-dir.py:10: Rename empty dir and rename back
./run --rename /mnt/a/empty100 /mnt/a/no_dir100 -E EXDEV
/mnt/a/empty100: Expected error (Invalid cross-device link) was not 
produced

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1727290/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829177] Re: linux-aws: 4.18.0-1017.19 -proposed tracker

2019-05-22 Thread Sean Feole
kernel bugs:
amd64

ubuntu_kvm_unit_tests: (1821390): apic-split will fail in kvm_units_tests, 
(1821394): vmx tests fail in kvm_unit_tests, (1822308) vmx_hlt_with_rvi_test in 
kvm_unit_tests fails
ubuntu_ltp_syscalls: (1819116): sync_file_range02 in ubuntu_ltp_syscalls fails 
C/D
arm64

ubuntu_ltp_syscalls: (1819116): sync_file_range02 in ubuntu_ltp_syscalls fails 
C/D
ubuntu_kernel_selftests:(1830016): run_netsocktests from net in 
ubuntu_kernel_selftests failed with Socket type not supported


** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1829177

Title:
  linux-aws: 4.18.0-1017.19 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1829176 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829186
  phase: Testing
  phase-changed: Friday, 17. May 2019 18:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829177/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1821152] Re: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com'

2019-05-22 Thread Sean Feole
** Also affects: linux-aws (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux-aws (Ubuntu)

-- 
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/1821152

Title:
  lxc-test-no-new-privs failed with Temporary failure resolving
  'archive.ubuntu.com'

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  It seems this failure only exist in KVM instances.

FAIL: lxc-tests: lxc-test-no-new-privs (37s)
---
+ DONE=0
+ trap cleanup EXIT SIGHUP SIGINT SIGTERM
+ mkdir -p /etc/lxc/
+ cat
+ ARCH=i386
+ type dpkg
++ dpkg --print-architecture
+ ARCH=amd64
+ lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
Setting up the GPG keyring
Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs

---
You just created an Ubuntu xenial amd64 (20190320_07:42) container.

To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
+ echo 'lxc.no_new_privs = 1'
+ lxc-start -n c1
++ lxc-info -n c1 -p -H
+ p1=8818
+ '[' 8818 '!=' -1 ']'
+ sleep 5s
+ lxc-attach -n c1 --clear-env -- apt update -y

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
+ lxc-attach -n c1 --clear-env -- apt install -y gcc make

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev 
libcc1-0
  libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 
libmpfr4
  libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages 
manpages-dev
Suggested packages:
  binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool
  flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg
  libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg
  libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc
  make-doc man-browser
The following NEW packages will be installed:
  binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev
  libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 
libmpc3
  libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make
  manpages manpages-dev
0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.7 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 
3.1.4-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 
1.0.3-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2
  Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils 
amd64 2.26.1-1ubuntu1~16.04.8
  Temporary failure resolving 'archive.ubuntu.com'
Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 
0.16.1-1
  Temporary failure resolving 'archive.ubuntu.com'

  
  It's a bit weird that if I run the command manually, it looks OK
  lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
  lxc-start -n c1
  lxc-attach -n c1 --clear-env -- apt update -y
  Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Get:2 http://archive.ubuntu.com/ubuntu xenial-updates 

[Kernel-packages] [Bug 1830016] Re: run_netsocktests from net in ubuntu_kernel_selftests failed with Socket type not supported

2019-05-22 Thread Sean Feole
affects cosmic, AWS cloud, 4.18.0-1017.19-aws

** Also affects: linux-aws (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-aws (Ubuntu Cosmic)
   Status: New => Incomplete

** Changed in: linux-aws (Ubuntu)
   Status: New => Confirmed

** Changed in: linux-aws (Ubuntu Cosmic)
   Status: Incomplete => Confirmed

** Tags added: arm64

** Tags added: aws

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1830016

Title:
  run_netsocktests from net in ubuntu_kernel_selftests failed with
  Socket type not supported

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  Confirmed

Bug description:
  After fixing 1825777, the run_netsocktests is failing correctly, it's failing 
with:
  
  running socket test
  
  socket(44, 0, 0) expected err (Address family not supported by protocol) 
got (Socket type not supported)
  [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-20-generic 4.18.0-20.21
  ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 09:45 seq
   crw-rw 1 root audio 116, 33 May 22 09:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed May 22 10:31:17 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-20-generic N/A
   linux-backports-modules-4.18.0-20-generic  N/A
   linux-firmware 1.175.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830016/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829166] Re: linux-azure: 5.0.0-1007.7 -proposed tracker

2019-05-22 Thread Sean Feole
Testing Results:

monotonic_time: (1774959): clock test in monotonic_time will fail on Azure 
Instances
ubuntu_kernel_selftests: (1829812): ubuntu_kernel_selftests [net] ubuntu_bpf 
test case fails to build on disco, (1830084) :ubuntu_kernel_tests ftrace fails 
on disco, linux-azure
ubuntu_kvm_unittests:1821394 : vmx tests fail in kvm_unit_tests
ubuntu_ltp_syscalls:1819116: sync_file_range02 in ubuntu_ltp_syscalls fails C/D
ubuntu_lxc:1821152:lxc-test-no-new-privs failed with Temporary failure 
resolving 'archive.ubuntu.com'


** Tags added: regression-testing-passed

-- 
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/1829166

Title:
  linux-azure: 5.0.0-1007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829173
  phase: Testing
  phase-changed: Monday, 20. May 2019 11:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829166/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1821152] Re: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com'

2019-05-22 Thread Sean Feole
affects linux-azure 5.0.0-1007.7

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1821152

Title:
  lxc-test-no-new-privs failed with Temporary failure resolving
  'archive.ubuntu.com'

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  It seems this failure only exist in KVM instances.

FAIL: lxc-tests: lxc-test-no-new-privs (37s)
---
+ DONE=0
+ trap cleanup EXIT SIGHUP SIGINT SIGTERM
+ mkdir -p /etc/lxc/
+ cat
+ ARCH=i386
+ type dpkg
++ dpkg --print-architecture
+ ARCH=amd64
+ lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
Setting up the GPG keyring
Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs

---
You just created an Ubuntu xenial amd64 (20190320_07:42) container.

To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
+ echo 'lxc.no_new_privs = 1'
+ lxc-start -n c1
++ lxc-info -n c1 -p -H
+ p1=8818
+ '[' 8818 '!=' -1 ']'
+ sleep 5s
+ lxc-attach -n c1 --clear-env -- apt update -y

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
+ lxc-attach -n c1 --clear-env -- apt install -y gcc make

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev 
libcc1-0
  libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 
libmpfr4
  libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages 
manpages-dev
Suggested packages:
  binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool
  flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg
  libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg
  libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc
  make-doc man-browser
The following NEW packages will be installed:
  binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev
  libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 
libmpc3
  libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make
  manpages manpages-dev
0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.7 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 
3.1.4-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 
1.0.3-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2
  Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils 
amd64 2.26.1-1ubuntu1~16.04.8
  Temporary failure resolving 'archive.ubuntu.com'
Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 
0.16.1-1
  Temporary failure resolving 'archive.ubuntu.com'

  
  It's a bit weird that if I run the command manually, it looks OK
  lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
  lxc-start -n c1
  lxc-attach -n c1 --clear-env -- apt update -y
  Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
  Get:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 

[Kernel-packages] [Bug 1819116] Re: sync_file_range02 in ubuntu_ltp_syscalls fails C/D

2019-05-22 Thread Sean Feole
affects disco, 5.0.0-1007.7 linux-azure

** Also affects: linux-azure (Ubuntu)
   Importance: Undecided
   Status: New

** Attachment added: "ltp_syscalls-azure-disco"
   
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819116/+attachment/5265775/+files/ltp_syscalls-azure-disco

-- 
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/1819116

Title:
  sync_file_range02 in ubuntu_ltp_syscalls fails C/D

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-aws source package in Cosmic:
  New
Status in linux-azure source package in Cosmic:
  New
Status in linux source package in Disco:
  Incomplete
Status in linux-aws source package in Disco:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  syslog output attached as attachment.

  <<>>
  incrementing stop
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1157: INFO: Testing on ext2
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext3
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext4
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on vfat
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ntfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts=''
  The partition start sector was not specified for /dev/loop2 and it could not 
be obtained automatically.  It has been set to 0.
  The number of sectors per track was not specified for /dev/loop2 and it could 
not be obtained automatically.  It has been set to 0.
  The number of heads was not specified for /dev/loop2 and it could not be 
obtained automatically.  It has been set to 0.
  To boot from a device, Windows needs the 'partition start sector', the 
'sectors per track' and the 'number of heads' to be set.
  Windows will not be able to boot from this device.
  safe_macros.c:739: INFO: Trying FUSE...
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:56: FAIL: Synced 0, expected 33554432

  Summary:
  passed   6
  failed   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=11 termination_type=exited termination_id=1 corefile=no
  cutime=10 cstime=157
  <<>>
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20190115

 ###

  Done executing testcases.
  LTP Version:  20190115
 

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

2019-05-22 Thread Sean Feole
affects , linux-azure 5.0.0-1007.7

** Tags added: 5.0.0

-- 
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/1821394

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
  FAIL: Enable-EPT enabled; 

[Kernel-packages] [Bug 1829812] Re: Regression for ubuntu_bpf test case fails to build on disco

2019-05-22 Thread Sean Feole
Affects: Disco, 5.0.0-1007.7 linux-azure

** Summary changed:

- Regression for ubuntu_bpf test case fails to build on disco
+ Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case fails to 
build on disco

-- 
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/1829812

Title:
  Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case
  fails to build on disco

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  This test will failed to build on 5.0.0-16 Disco.

  5.0.0-16 Disco + 5.0.0-15 source code - build OK
  5.0.0-16 Disco + 5.0.0-16 source code - Failed

  Bisect shows this one e38969c9 (selftests/bpf: skip verifier tests for
  unsupported program types) in our tree is the cause (upstream commit:
  8184d44c)

  Which uses a "recently introduced bpf_probe_prog_type()" to skip test.
  And we don't have it implemented.

    make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
    gcc -o 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/urandom_read
 -static urandom_read.c -Wl,--build-id
    make -C ../../../lib/bpf 
OUTPUT=/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/
    make[2]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf'

    Auto-detecting system features:
    ...libelf: [ on  ]
    ...   bpf: [ on  ]

  HOSTCC   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep.o
  HOSTLD   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep-in.o
  LINK 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep
  CC   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.o
  CC   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf.o
  CC   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/nlattr.o
  CC   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/btf.o
  CC   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf_errno.o
  CC   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/str_error.o
  CC   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/netlink.o
  CC   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_prog_linfo.o
  LD   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf-in.o
  LINK 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.a
  LINK 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.so
  LINK 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_libbpf
    make[2]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf'
    gcc -Wall -O2 -I../../../include/uapi -I../../../lib -I../../../lib/bpf 
-I../../../../include/generated  -I../../../includetest_verifier.c 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.a
 -lcap -lelf -lrt -lpthread -o 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_verifier
    make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
    make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
    stderr:
    Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs 
from latest version at 'include/uapi/linux/if_link.h'
    test_verifier.c: In function ‘do_test_single’:
    test_verifier.c:15951:22: warning: implicit declaration of function 
‘bpf_probe_prog_type’; did you mean ‘bpf_program__set_type’? 
[-Wimplicit-function-declaration]
  if (fd_prog < 0 && !bpf_probe_prog_type(prog_type, 0)) {
  ^~~
  bpf_program__set_type
    /usr/bin/ld: /tmp/ccRNIovw.o: in function `do_test_single':
    test_verifier.c:(.text+0xf41): undefined reference to `bpf_probe_prog_type'
    collect2: error: ld returned 1 exit status
    make[1]: *** [../lib.mk:152: 

[Kernel-packages] [Bug 1829812] Re: Regression for ubuntu_bpf test case fails to build on disco

2019-05-22 Thread Sean Feole
This is coming up on the azure kernel as well.  Various instance flavor
types:

05/20 14:12:08 DEBUG| utils:0153| [stdout] make[2]: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/lib/bpf'
05/20 14:12:08 DEBUG| utils:0153| [stdout] gcc -Wall -O2 
-I../../../include/uapi -I../../../lib -I../../../lib/bpf 
-I../../../../include/generated  -I../../../includetest_verifier.c 
/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/libbpf.a
 -lcap -lelf -lrt -lpthread -o 
/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/test_verifier
05/20 14:12:09 ERROR| utils:0153| [stderr] test_verifier.c: In function 
‘do_test_single’:
05/20 14:12:09 ERROR| utils:0153| [stderr] test_verifier.c:15951:22: 
warning: implicit declaration of function ‘bpf_probe_prog_type’; did you 
mean ‘bpf_program__set_type’? [-Wimplicit-function-declaration]
05/20 14:12:09 ERROR| utils:0153| [stderr]   if (fd_prog < 0 && 
!bpf_probe_prog_type(prog_type, 0)) {
05/20 14:12:09 ERROR| utils:0153| [stderr]   
^~~
05/20 14:12:09 ERROR| utils:0153| [stderr]   
bpf_program__set_type
05/20 14:12:09 ERROR| utils:0153| [stderr] /usr/bin/ld: /tmp/ccUGUMFc.o: in 
function `do_test_single':
05/20 14:12:09 ERROR| utils:0153| [stderr] test_verifier.c:(.text+0xf41): 
undefined reference to `bpf_probe_prog_type'
05/20 14:12:10 ERROR| utils:0153| [stderr] collect2: error: ld returned 1 
exit status
05/20 14:12:10 ERROR| utils:0153| [stderr] make[1]: *** [../lib.mk:152: 
/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/test_verifier]
 Error 1
05/20 14:12:10 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf'
05/20 14:12:10 DEBUG| utils:0153| [stdout] make: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
05/20 14:12:10 ERROR| utils:0153| [stderr] make: *** [Makefile:90: all] 
Error 2
05/20 14:12:10 ERROR|  test:0414| Exception escaping from test:
Traceback (most recent call last):
  File "/home/azure/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/azure/autotest/client/shared/test.py", line 823, in 
_call_test_function
return func(*args, **dargs)
  File "/home/azure/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
  File "/home/azure/autotest/client/shared/test.py", line 212, in _call_run_once
self.run_once(*args, **dargs)
  File 
"/home/azure/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py",
 line 144, in run_once
utils.system(cmd)
  File "/home/azure/autotest/client/shared/utils.py", line 1232, in system
verbose=verbose).exit_status
  File "/home/azure/autotest/client/shared/utils.py", line 918, in run
"Command returned non-zero exit status")
CmdError: Command  failed, 
rc=2, Command returned non-zero exit status
* Command: 
make -C linux/tools/testing/selftests TARGETS=bpf
Exit status: 2
Duration: 5.6805369854


** Also affects: linux-azure (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: aws azure

-- 
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/1829812

Title:
  Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case
  fails to build on disco

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  This test will failed to build on 5.0.0-16 Disco.

  5.0.0-16 Disco + 5.0.0-15 source code - build OK
  5.0.0-16 Disco + 5.0.0-16 source code - Failed

  Bisect shows this one e38969c9 (selftests/bpf: skip verifier tests for
  unsupported program types) in our tree is the cause (upstream commit:
  8184d44c)

  Which uses a "recently introduced bpf_probe_prog_type()" to skip test.
  And we don't have it implemented.

    make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
    gcc -o 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/urandom_read
 -static urandom_read.c -Wl,--build-id
    make -C ../../../lib/bpf 
OUTPUT=/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/
    make[2]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf'

    

[Kernel-packages] [Bug 1830084] [NEW] ubuntu_kernel_tests ftrace fails on disco, linux-azure

2019-05-22 Thread Sean Feole
Public bug reported:

Cloud: Azure
Series: Disco
Kernel: 5.0.0-1007.7linux-azure
Instance: Standard_D2_v3 and others. 

05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C 
linux/tools/testing/selftests TARGETS=ftrace run_tests'
05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done for 
'all'.
05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13
05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest
05/20 14:24:27 DEBUG| utils:0153| [stdout] 

05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal 
number: 
05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests ===
05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file check
05/20 14:24:27 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for tracers
05/20 14:24:31 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock test
05/20 14:24:32 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing 
check
05/20 14:24:32 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the ringbuffer 
size
05/20 14:24:33 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing 
setting
05/20 14:24:33 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and 
trace_marker
05/20 14:24:33 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic event 
- add/remove kprobe events
05/20 14:24:33 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic event 
- add/remove synthetic events
05/20 14:24:33 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic event 
- selective clear (compatibility)
05/20 14:24:34 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic event 
- generic clear event
05/20 14:24:34 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - 
enable/disable with event level files
05/20 14:24:34 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - 
restricts events based on pid
05/20 14:24:35 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - 
enable/disable with subsystem level files
05/20 14:24:35 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - 
enable/disable with top level files
05/20 14:24:35 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [16] Test trace_printk 
from module
05/20 14:24:36 DEBUG| utils:0153| [stdout] -e   [UNRESOLVED]
05/20 14:24:36 DEBUG| utils:0153| [stdout] -e -n [17] ftrace - function 
graph filters with stack tracer
05/20 14:24:38 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:38 DEBUG| utils:0153| [stdout] -e -n [18] ftrace - function 
graph filters
05/20 14:24:40 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:40 DEBUG| utils:0153| [stdout] -e -n [19] ftrace - function pid 
filters
05/20 14:24:41 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:41 DEBUG| utils:0153| [stdout] -e -n [20] ftrace - stacktrace 
filter command
05/20 14:24:42 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:42 DEBUG| utils:0153| [stdout] -e -n [21] ftrace - function 
trace with cpumask
05/20 14:24:42 DEBUG| utils:0153| [stdout] -e   [PASS]
05/20 14:24:42 DEBUG| utils:0153| [stdout] -e -n [22] ftrace - test for 
function event triggers
05/20 14:24:46 

[Kernel-packages] [Bug 1830016] Re: run_netsocktests from net in ubuntu_kernel_selftests failed with Socket type not supported

2019-05-22 Thread Sean Feole
** Changed in: ubuntu-kernel-tests
   Status: New => Confirmed

-- 
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/1830016

Title:
  run_netsocktests from net in ubuntu_kernel_selftests failed with
  Socket type not supported

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  After fixing 1825777, the run_netsocktests is failing correctly, it's failing 
with:
  
  running socket test
  
  socket(44, 0, 0) expected err (Address family not supported by protocol) 
got (Socket type not supported)
  [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-20-generic 4.18.0-20.21
  ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 09:45 seq
   crw-rw 1 root audio 116, 33 May 22 09:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed May 22 10:31:17 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-20-generic N/A
   linux-backports-modules-4.18.0-20-generic  N/A
   linux-firmware 1.175.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830016/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1774959] Re: clock test in monotonic_time will fail on Azure Instances

2019-05-22 Thread Sean Feole
Affects: 5.0.0-1007.7

** Tags added: azure disco

-- 
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/1774959

Title:
  clock test in monotonic_time will fail on Azure Instances

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Among all of the Azure node, this test only failed on these two nodes:

  Seen on the following instances:

  Basic_A2
  Standard_D2_v3
  Standard_D2s_v3
  Standard_E4s_v3
  Standard_E64-16s 
  Standard_F2s_v2
   

  
  Steps to reproduce:
   1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
   2. make -C autotest-client-tests/monotonic_time/src
   3. sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc

  Results:
  $ sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc

   Running 'make '
   cc -O -std=gnu99 -Wall -c -o time_test.o time_test.c
   cc -O -std=gnu99 -Wall -c -o cpuset.o cpuset.c
   cc -O -std=gnu99 -Wall -c -o threads.o threads.c
   cc -O -std=gnu99 -Wall -c -o logging.o logging.c
   cc -o time_test time_test.o cpuset.o threads.o logging.o -lpthread -lrt
   Running '/home/azure/autotest/client/tmp/monotonic_time/src/time_test 
--duration 300 clock'
   Time test command exit status: 1
   Exception escaping from test:
   Traceback (most recent call last):
   File "/home/azure/autotest/client/shared/test.py", line 411, in
   _exec_call_test_function(self.execute, *p_args, **p_dargs)
   File "/home/azure/autotest/client/shared/test.py", line 823, in 
_call_test_function
   return func(*args, **dargs)
   File "/home/azure/autotest/client/shared/test.py", line 291, in execute
   postprocess_profiled_run, args, dargs)
   File "/home/azure/autotest/client/shared/test.py", line 212, in 
_call_run_once
   self.run_once(*args, **dargs)
   File "/home/azure/autotest/client/tests/monotonic_time/monotonic_time.py", 
line 53, in run_once
   raise error.TestFail(line)
   TestFail: FAIL: clock-worst-warp=-100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774959/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1774959] Re: clock test in monotonic_time will fail on Azure Instances

2019-05-22 Thread Sean Feole
Affects: 5.0.0-1007.7-azure

-- 
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/1774959

Title:
  clock test in monotonic_time will fail on Azure Instances

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Among all of the Azure node, this test only failed on these two nodes:

  Seen on the following instances:

  Basic_A2
  Standard_D2_v3
  Standard_D2s_v3
  Standard_E4s_v3
  Standard_E64-16s 
  Standard_F2s_v2
   

  
  Steps to reproduce:
   1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
   2. make -C autotest-client-tests/monotonic_time/src
   3. sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc

  Results:
  $ sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc

   Running 'make '
   cc -O -std=gnu99 -Wall -c -o time_test.o time_test.c
   cc -O -std=gnu99 -Wall -c -o cpuset.o cpuset.c
   cc -O -std=gnu99 -Wall -c -o threads.o threads.c
   cc -O -std=gnu99 -Wall -c -o logging.o logging.c
   cc -o time_test time_test.o cpuset.o threads.o logging.o -lpthread -lrt
   Running '/home/azure/autotest/client/tmp/monotonic_time/src/time_test 
--duration 300 clock'
   Time test command exit status: 1
   Exception escaping from test:
   Traceback (most recent call last):
   File "/home/azure/autotest/client/shared/test.py", line 411, in
   _exec_call_test_function(self.execute, *p_args, **p_dargs)
   File "/home/azure/autotest/client/shared/test.py", line 823, in 
_call_test_function
   return func(*args, **dargs)
   File "/home/azure/autotest/client/shared/test.py", line 291, in execute
   postprocess_profiled_run, args, dargs)
   File "/home/azure/autotest/client/shared/test.py", line 212, in 
_call_run_once
   self.run_once(*args, **dargs)
   File "/home/azure/autotest/client/tests/monotonic_time/monotonic_time.py", 
line 53, in run_once
   raise error.TestFail(line)
   TestFail: FAIL: clock-worst-warp=-100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774959/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1819116] Re: sync_file_range02 in ubuntu_ltp_syscalls failed on D

2019-05-21 Thread Sean Feole
affects cosmic 4.18.0-1017.19-aws amd64 & arm64

** Tags added: cosmic

** Also affects: linux-aws (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- sync_file_range02 in ubuntu_ltp_syscalls failed on D
+ sync_file_range02 in ubuntu_ltp_syscalls fails C/D

-- 
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/1819116

Title:
  sync_file_range02 in ubuntu_ltp_syscalls fails C/D

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-aws source package in Cosmic:
  New
Status in linux source package in Disco:
  Incomplete
Status in linux-aws source package in Disco:
  New

Bug description:
  syslog output attached as attachment.

  <<>>
  incrementing stop
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1157: INFO: Testing on ext2
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext3
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext4
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on vfat
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ntfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts=''
  The partition start sector was not specified for /dev/loop2 and it could not 
be obtained automatically.  It has been set to 0.
  The number of sectors per track was not specified for /dev/loop2 and it could 
not be obtained automatically.  It has been set to 0.
  The number of heads was not specified for /dev/loop2 and it could not be 
obtained automatically.  It has been set to 0.
  To boot from a device, Windows needs the 'partition start sector', the 
'sectors per track' and the 'number of heads' to be set.
  Windows will not be able to boot from this device.
  safe_macros.c:739: INFO: Trying FUSE...
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:56: FAIL: Synced 0, expected 33554432

  Summary:
  passed   6
  failed   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=11 termination_type=exited termination_id=1 corefile=no
  cutime=10 cstime=157
  <<>>
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20190115

 ###

  Done executing testcases.
  LTP Version:  20190115
 ###

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Uname: Linux 

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

2019-05-21 Thread Sean Feole
affects , linux-aws-4.18.0 amd64, i3.metal

-- 
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/1821394

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits 

[Kernel-packages] [Bug 1822308] Re: vmx_hlt_with_rvi_test in kvm_unit_tests fails

2019-05-21 Thread Sean Feole
affects , linux-aws-4.18.0 amd64, i3.metal

** Summary changed:

- vmx_hlt_with_rvi_test in kvm_unit_tests failed with X-KVM
+ vmx_hlt_with_rvi_test in kvm_unit_tests fails

** Tags added: amd64 cosmic xenial

** Also affects: linux-aws (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1822308

Title:
  vmx_hlt_with_rvi_test in kvm_unit_tests fails

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
   TESTNAME=vmx_hlt_with_rvi_test TIMEOUT=10 ACCEL= ./x86/run x86/vmx.flat -smp 
1 -cpu host,+vmx -append vmx_hlt_with_rvi_test
   FAIL vmx_hlt_with_rvi_test (timeout; duration=10)

  
  Detailed report will be appended here later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822308/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825777] Re: False positive test result in run_netsocktests from net in ubuntu_kernel_selftest

2019-05-21 Thread Sean Feole
Re-triggered a variety of cloud jobs that have failed due to this bug.
will verify passed on Cosmic

-- 
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/1825777

Title:
  False positive test result in run_netsocktests from net in
  ubuntu_kernel_selftest

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  In Progress

Bug description:
  == SRU Justification ==

  The run_netsocktests from net in ubuntu_kernel_selftest will be marked
  as passed regardless the actual test result from the ./socket:

  selftests: net: run_netsocktests
  
  
  running socket test
  
  [FAIL]
  ok 1..6 selftests: net: run_netsocktests [PASS]

  This is because the test script itself has been successfully executed,
  and make it return 0.

  == Fix ==
  30c04d79 (selftests/net: correct the return value for run_netsocktests)

  This can be cherry-picked into all of our kernels.

  == Test ==
  Patch tested and submitted to the upstream.

  == Regression Potential ==
  Changes limit to the testing tool, and it's is expected to see failures
  from this test in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825777/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829165] Re: linux-aws: 5.0.0-1007.7 -proposed tracker

2019-05-21 Thread Sean Feole
Test Results

amd64:

ubuntu-kernel-tests: (1821394): vmx tests fail in kvm_unit_tests
ubuntu_ltp_syscalls: (1819116):sync_file_range02 in ubuntu_ltp_syscalls failed 
on D

arm64:
ubuntu_kernel_selftests: (1829812): Regression for ubuntu_bpf test case fails 
to build on disco
ubuntu_ltp_syscalls: (1819116):sync_file_range02 in ubuntu_ltp_syscalls failed 
on D


** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1829165

Title:
  linux-aws: 5.0.0-1007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829173
  phase: Testing
  phase-changed: Friday, 17. May 2019 16:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829165/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1819116] Re: sync_file_range02 in ubuntu_ltp_syscalls failed on D

2019-05-21 Thread Sean Feole
affects disco 5.0.0-1007.7-aws amd64 & arm64

** Tags added: arm64

-- 
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/1819116

Title:
  sync_file_range02 in ubuntu_ltp_syscalls failed on D

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  Incomplete

Bug description:
  syslog output attached as attachment.

  <<>>
  incrementing stop
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1157: INFO: Testing on ext2
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext3
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext4
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on vfat
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ntfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts=''
  The partition start sector was not specified for /dev/loop2 and it could not 
be obtained automatically.  It has been set to 0.
  The number of sectors per track was not specified for /dev/loop2 and it could 
not be obtained automatically.  It has been set to 0.
  The number of heads was not specified for /dev/loop2 and it could not be 
obtained automatically.  It has been set to 0.
  To boot from a device, Windows needs the 'partition start sector', the 
'sectors per track' and the 'number of heads' to be set.
  Windows will not be able to boot from this device.
  safe_macros.c:739: INFO: Trying FUSE...
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:56: FAIL: Synced 0, expected 33554432

  Summary:
  passed   6
  failed   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=11 termination_type=exited termination_id=1 corefile=no
  cutime=10 cstime=157
  <<>>
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20190115

 ###

  Done executing testcases.
  LTP Version:  20190115
 ###

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  8 06:01 seq
   crw-rw 1 root audio 116, 33 Mar  8 06:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command 

[Kernel-packages] [Bug 1829812] Re: Regression for ubuntu_bpf test case in 5.0.0-16

2019-05-21 Thread Sean Feole
Caught this failing on arm64 , disco, 5.0.0-1007.7 linux-aws,

05/18 08:00:22 DEBUG| utils:0153| [stdout] make[2]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/lib/bpf'
05/18 08:00:22 DEBUG| utils:0153| [stdout] gcc -Wall -O2 
-I../../../include/uapi -I../../../lib -I../../../lib/bpf 
-I../../../../include/generated -I../../../include test_verifier.c 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/libbpf.a
 -lcap -lelf -lrt -lpthread -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/test_verifier
05/18 08:00:23 ERROR| utils:0153| [stderr] test_verifier.c: In function 
‘do_test_single’:
05/18 08:00:23 ERROR| utils:0153| [stderr] test_verifier.c:15951:22: warning: 
implicit declaration of function ‘bpf_probe_prog_type’; did you mean 
‘bpf_program__set_type’? [-Wimplicit-function-declaration]
05/18 08:00:23 ERROR| utils:0153| [stderr] if (fd_prog < 0 && 
!bpf_probe_prog_type(prog_type, 0)) {
05/18 08:00:23 ERROR| utils:0153| [stderr] ^~~
05/18 08:00:23 ERROR| utils:0153| [stderr] bpf_program__set_type
05/18 08:00:23 ERROR| utils:0153| [stderr] /usr/bin/ld: /tmp/cc9290dq.o: in 
function `do_test_single':
05/18 08:00:23 ERROR| utils:0153| [stderr] test_verifier.c:(.text+0x8c8): 
undefined reference to `bpf_probe_prog_type'
05/18 08:00:23 ERROR| utils:0153| [stderr] collect2: error: ld returned 1 exit 
status
05/18 08:00:23 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf'
05/18 08:00:23 DEBUG| utils:0153| [stdout] make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
05/18 08:00:23 ERROR| utils:0153| [stderr] make[1]: *** [../lib.mk:152: 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/test_verifier]
 Error 1
05/18 08:00:23 ERROR| utils:0153| [stderr] make: *** [Makefile:90: all] Error 2
05/18 08:00:23 ERROR| test:0414| Exception escaping from test:
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
self.run_once(*args, **dargs)
  File 
"/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py",
 line 144, in run_once
utils.system(cmd)
  File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system
verbose=verbose).exit_status
  File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
"Command returned non-zero exit status")
CmdError: Command  failed, 
rc=2, Command returned non-zero exit status
* Command:
make -C linux/tools/testing/selftests TARGETS=bpf
Exit status: 2
Duration: 5.29515004158

stdout:


** Tags added: arm64

** Tags added: linux-aws

** Also affects: linux-aws (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Regression for ubuntu_bpf test case in 5.0.0-16
+ Regression for ubuntu_bpf test case fails to build on disco

-- 
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/1829812

Title:
  Regression for ubuntu_bpf test case fails to build on disco

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New

Bug description:
  This test will failed to build on 5.0.0-16 Disco.

  5.0.0-16 Disco + 5.0.0-15 source code - build OK
  5.0.0-16 Disco + 5.0.0-16 source code - Failed

  Bisect shows this one e38969c9 (selftests/bpf: skip verifier tests for
  unsupported program types) in our tree is the cause (upstream commit:
  8184d44c)

  Which uses a "recently introduced bpf_probe_prog_type()" to skip test.
  And we don't have it implemented.

    make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
    gcc -o 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/urandom_read
 -static urandom_read.c -Wl,--build-id
    make -C ../../../lib/bpf 
OUTPUT=/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/
    make[2]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf'

    Auto-detecting system features:
    ...libelf: [ on  ]
    ...  

[Kernel-packages] [Bug 1829812] Re: Regression for ubuntu_bpf test case in 5.0.0-16

2019-05-21 Thread Sean Feole
also affects disco, 5.0.0-1007.7 linux-aws


05/18 08:00:22 DEBUG| utils:0153| [stdout] make[2]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/lib/bpf'
05/18 08:00:22 DEBUG| utils:0153| [stdout] gcc -Wall -O2 
-I../../../include/uapi -I../../../lib -I../../../lib/bpf 
-I../../../../include/generated  -I../../../includetest_verifier.c 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/libbpf.a
 -lcap -lelf -lrt -lpthread -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/test_verifier
05/18 08:00:23 ERROR| utils:0153| [stderr] test_verifier.c: In function 
‘do_test_single’:
05/18 08:00:23 ERROR| utils:0153| [stderr] test_verifier.c:15951:22: 
warning: implicit declaration of function ‘bpf_probe_prog_type’; did you 
mean ‘bpf_program__set_type’? [-Wimplicit-function-declaration]
05/18 08:00:23 ERROR| utils:0153| [stderr]   if (fd_prog < 0 && 
!bpf_probe_prog_type(prog_type, 0)) {
05/18 08:00:23 ERROR| utils:0153| [stderr]   
^~~
05/18 08:00:23 ERROR| utils:0153| [stderr]   
bpf_program__set_type
05/18 08:00:23 ERROR| utils:0153| [stderr] /usr/bin/ld: /tmp/cc9290dq.o: in 
function `do_test_single':
05/18 08:00:23 ERROR| utils:0153| [stderr] test_verifier.c:(.text+0x8c8): 
undefined reference to `bpf_probe_prog_type'
05/18 08:00:23 ERROR| utils:0153| [stderr] collect2: error: ld returned 1 
exit status
05/18 08:00:23 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf'
05/18 08:00:23 DEBUG| utils:0153| [stdout] make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
05/18 08:00:23 ERROR| utils:0153| [stderr] make[1]: *** [../lib.mk:152: 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/test_verifier]
 Error 1
05/18 08:00:23 ERROR| utils:0153| [stderr] make: *** [Makefile:90: all] 
Error 2
05/18 08:00:23 ERROR|  test:0414| Exception escaping from test:
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
self.run_once(*args, **dargs)
  File 
"/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py",
 line 144, in run_once
utils.system(cmd)
  File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system
verbose=verbose).exit_status
  File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
"Command returned non-zero exit status")
CmdError: Command  failed, 
rc=2, Command returned non-zero exit status
* Command: 
make -C linux/tools/testing/selftests TARGETS=bpf
Exit status: 2
Duration: 5.29515004158

stdout:

-- 
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/1829812

Title:
  Regression for ubuntu_bpf test case fails to build on disco

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New

Bug description:
  This test will failed to build on 5.0.0-16 Disco.

  5.0.0-16 Disco + 5.0.0-15 source code - build OK
  5.0.0-16 Disco + 5.0.0-16 source code - Failed

  Bisect shows this one e38969c9 (selftests/bpf: skip verifier tests for
  unsupported program types) in our tree is the cause (upstream commit:
  8184d44c)

  Which uses a "recently introduced bpf_probe_prog_type()" to skip test.
  And we don't have it implemented.

    make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
    gcc -o 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/urandom_read
 -static urandom_read.c -Wl,--build-id
    make -C ../../../lib/bpf 
OUTPUT=/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/
    make[2]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf'

    Auto-detecting system features:
    ...libelf: [ on  ]
    ...   bpf: [ on  ]

  HOSTCC   
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep.o
  HOSTLD   

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

2019-05-21 Thread Sean Feole
affects 5.0.0-1007.7-aws

** Changed in: ubuntu-kernel-tests
   Status: New => Confirmed

** Changed in: linux-aws (Ubuntu)
   Status: New => Confirmed

-- 
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/1821394

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails

[Kernel-packages] [Bug 1829196] Re: linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker

2019-05-21 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1829196

Title:
  linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  derivatives: bug 1829847 (linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829200
  phase: Testing
  phase-changed: Monday, 20. May 2019 18:14 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
promote-to-updates: Pending -- Nvidia object not found -- 
current-driver-4.15.0-1033-gcp-amd64
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829196/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829183] Re: linux-gcp: 4.18.0-1012.13 -proposed tracker

2019-05-21 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1829183

Title:
  linux-gcp: 4.18.0-1012.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1829182 (bionic/linux-gcp-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829186
  phase: Testing
  phase-changed: Monday, 20. May 2019 14:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829183/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829200] Re: linux-gcp: 4.15.0-1033.35 -proposed tracker

2019-05-21 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1829200

Title:
  linux-gcp: 4.15.0-1033.35 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1829196 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Testing
  phase-changed: Monday, 20. May 2019 16:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829200/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826345] Re: linux-ibm-gt: 4.15.0-1020.22 -proposed tracker

2019-05-13 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1826345

Title:
  linux-ibm-gt: 4.15.0-1020.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Ready for Testing
  phase-changed: Monday, 13. May 2019 04:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826345/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826169] Re: linux-kvm: 4.18.0-1011.11 -proposed tracker

2019-05-13 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1826169

Title:
  linux-kvm: 4.18.0-1011.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826171
  phase: Holding before Release
  phase-changed: Monday, 13. May 2019 15:14 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826169/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826145] Re: linux-kvm: 5.0.0-1005.5 -proposed tracker

2019-05-13 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1826145

Title:
  linux-kvm: 5.0.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826150
  phase: Holding before Release
  phase-changed: Monday, 13. May 2019 15:14 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826145/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1760087] Re: net test in ubuntu_kernel_selftest failed on linux-kvm

2019-05-13 Thread Sean Feole
** Summary changed:

- net test in ubuntu_kernel_selftest failed on linux-kvm 4.4
+ net test in ubuntu_kernel_selftest failed on linux-kvm

-- 
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/1760087

Title:
  net test in ubuntu_kernel_selftest failed on linux-kvm

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Steps:
1. Deploy a KVM node with Xenial, install linux-kvm on it.
2. git clone --depth 1 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial linux
3. Run the "net" sub set in the kernel_selftest

  Result:
* test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory
* test_bpf: [FAIL]
* selftests: test_bpf.sh [FAIL]

  Output:
  $ sudo make -C linux/tools/testing/selftests/net all run_tests
  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  make: Nothing to be done for 'all'.
  
  running socket test
  
  [PASS]
  selftests: run_netsocktests [PASS]
  
  running psock_fanout test
  
  test: control single socket
  test: control multiple sockets
  test: datapath 0x0
  info: count=0,0, expect=0,0
  info: count=15,5, expect=15,5
  info: count=20,5, expect=20,5
  test: datapath 0x1000
  info: count=0,0, expect=0,0
  info: count=15,5, expect=15,5
  info: count=20,15, expect=20,15
  test: datapath 0x1
  info: count=0,0, expect=0,0
  info: count=10,10, expect=10,10
  info: count=18,17, expect=18,17
  test: datapath 0x3
  info: count=0,0, expect=0,0
  info: count=15,5, expect=15,5
  info: count=20,15, expect=20,15
  test: datapath 0x6
  info: count=0,0, expect=0,0
  info: count=5,15, expect=15,5
  info: count=20,15, expect=15,20
  test: datapath 0x7
  bpf: Function not implemented
  bpf verifier:
  ���ߟ
  [FAIL]
  
  running psock_tpacket test
  
  test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory
  [FAIL]
  selftests: run_afpackettests [PASS]
  test_bpf: [FAIL]
  selftests: test_bpf.sh [FAIL]
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 12:12:46 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1760087/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826352] Re: linux-azure: 4.15.0-1044.48~14.04.1 -proposed tracker

2019-05-13 Thread Sean Feole
Regression Tests:
monotonic:1774959(clock test in monotonic_time will fail on Azure Instances 
Edit)
umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4(1821905), apic test in 
kvm-unit-test failed on azure cloud with 4.13/4.14 kernel(1748103)


** Tags added: regression-testing-passed

-- 
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/1826352

Title:
  linux-azure: 4.15.0-1044.48~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826354
  phase: Ready for Testing
  phase-changed: Monday, 13. May 2019 04:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826352/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826034] Re: linux-aws: 4.4.0-1043.46 -proposed tracker

2019-05-13 Thread Sean Feole
regression-testing

ftrace_smoke: 1828796:ubuntu_ftrace_smoke_test failed on T-4.4 AWS node i3en
ubuntu_kvm_unit_tests - apic timeouted (bug 1748103 vmx (bug 1821394) 
vmx_hlt_with_rvi_test (bug 1822308) vmx_apicv_test (bug 1827866) 
vmx_apic_passthrough_thread (bug 1822309) debug (bug 1821906)


** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1826034

Title:
  linux-aws: 4.4.0-1043.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826036
  phase: Ready for Testing
  phase-changed: Monday, 13. May 2019 05:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826034/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826354] Re: linux-azure: 4.15.0-1044.48 -proposed tracker

2019-05-08 Thread Sean Feole
monotonic_time: 1774959 : clock test in monotonic_time will fail on Azure 
Instances
kvm_unit_tests: 1824228: ept test fails in kvm_unit_tests , 1821394: vmx tests 
fail in kvm_unit_tests , 1821152:


** Tags added: regression-testing-passed

-- 
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/1826354

Title:
  linux-azure: 4.15.0-1044.48 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1826352 (trusty/linux-azure)
  derivatives: bug 1826351 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Signoff
  phase-changed: Tuesday, 07. May 2019 12:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826346] Re: linux-oracle: 4.15.0-1012.14~16.04.1 -proposed tracker

2019-05-08 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1826346

Title:
  linux-oracle: 4.15.0-1012.14~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826348
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 07:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826346/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826339] Re: linux-gcp: 4.15.0-1031.33~16.04.1 -proposed tracker

2019-05-07 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1826339

Title:
  linux-gcp: 4.15.0-1031.33~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  derivatives: bug 1827360 (linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826340
  phase: Signoff
  phase-changed: Wednesday, 01. May 2019 10:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- nvidia GCP object not found -- 
current-driver-4.15.0-1031-gcp-amd64
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826024] Re: linux-aws: 4.4.0-1082.92 -proposed tracker

2019-05-07 Thread Sean Feole
Issue to note in x86_64 (aws):
  libhugetlbfs - 1 failed (alloc-instantiate-race shared), bad config 3, only 
spotted on t2.small, passed on the rest


ubuntu_kvm_tests: 1821394 - vmx tests fail in kvm_unit_tests
ubuntu_kvm_tests: 1821390 - apic-split will fail in kvm_units_tests
libhugetlbfs - 1 failed (alloc-instantiate-race shared), bad config 3, only 
spotted on t2.small, passed on the rest
ubuntu_kernel_selftests - CPU Hotplug Failed t2.small Only. : running 
psock_fanout test failed on net test t2.small ONLY
vmx tests fail in kvm_unit_tests (1821394)
cpu_hotplug test failed because there is only 1 CPU (1812149)


** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1826024

Title:
  linux-aws: 4.4.0-1082.92 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826036
  phase: Signoff
  phase-changed: Monday, 06. May 2019 05:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826024/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826348] Re: linux-oracle: 4.15.0-1012.14 -proposed tracker

2019-05-07 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1826348

Title:
  linux-oracle: 4.15.0-1012.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1826346 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 10:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826348/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826340] Re: linux-gcp: 4.15.0-1031.33 -proposed tracker

2019-05-03 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1826340

Title:
  linux-gcp: 4.15.0-1031.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1826339 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 08:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826340/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826165] Re: linux-azure: 4.18.0-1017.17~18.04.1 -proposed tracker

2019-05-03 Thread Sean Feole
regressiontesting:
amd64:

monotonic_time: 1774959 : clock test in monotonic_time will fail on Azure 
Instances
kvm_unit_tests: 1824228: ept test fails in kvm_unit_tests , 1821394: vmx tests 
fail in kvm_unit_tests , 1821152:
lxc_test : 1821152: lxc-test-no-new-privs failed with Temporary failure 
resolving 'archive.ubuntu.com'


** Tags added: regression-testing-passed

-- 
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/1826165

Title:
  linux-azure: 4.18.0-1017.17~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  derivatives: bug 1826164 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826166
  phase: Signoff
  phase-changed: Friday, 03. May 2019 04:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826165/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826166] Re: linux-azure: 4.18.0-1017.17 -proposed tracker

2019-05-03 Thread Sean Feole
Regression Tests:

monotonic_time: 1774959 : clock test in monotonic_time will fail on
Azure Instances

kvm_unit_tests: 1824228: ept test fails in kvm_unit_tests , 1821394: vmx
tests fail in kvm_unit_tests , 1821152: lxc-test-no-new-privs failed
with Temporary failure resolving 'archive.ubuntu.com'

lxc_test : 1821152: lxc-test-no-new-privs failed with Temporary failure
resolving 'archive.ubuntu.com'


** Tags added: regression-testing-passed

-- 
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/1826166

Title:
  linux-azure: 4.18.0-1017.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1826165 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826171
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 10:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826166/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826338] Re: linux-aws: 4.15.0-1038.40 -proposed tracker

2019-05-03 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1826338

Title:
  linux-aws: 4.15.0-1038.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1826337 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 10:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826338/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826144] Re: linux-gcp: 5.0.0-1005.5 -proposed tracker

2019-05-02 Thread Sean Feole
Regression Testing:

ubuntu_lxc: 1827383: lxc-test-share-ns fails in ubuntu-lxc   -- I was
unable to reproduce.


** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1826144

Title:
  linux-gcp: 5.0.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826150
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 10:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826144/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1821152] Re: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com'

2019-05-02 Thread Sean Feole
affects linux-azure: disco: 5.0.0-1005.5 , Standard_B1ms , Standard_F1s
, Standard_F2s_v2

** Tags added: disco

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1821152

Title:
  lxc-test-no-new-privs failed with Temporary failure resolving
  'archive.ubuntu.com'

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  It seems this failure only exist in KVM instances.

FAIL: lxc-tests: lxc-test-no-new-privs (37s)
---
+ DONE=0
+ trap cleanup EXIT SIGHUP SIGINT SIGTERM
+ mkdir -p /etc/lxc/
+ cat
+ ARCH=i386
+ type dpkg
++ dpkg --print-architecture
+ ARCH=amd64
+ lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
Setting up the GPG keyring
Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs

---
You just created an Ubuntu xenial amd64 (20190320_07:42) container.

To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
+ echo 'lxc.no_new_privs = 1'
+ lxc-start -n c1
++ lxc-info -n c1 -p -H
+ p1=8818
+ '[' 8818 '!=' -1 ']'
+ sleep 5s
+ lxc-attach -n c1 --clear-env -- apt update -y

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
+ lxc-attach -n c1 --clear-env -- apt install -y gcc make

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev 
libcc1-0
  libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 
libmpfr4
  libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages 
manpages-dev
Suggested packages:
  binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool
  flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg
  libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg
  libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc
  make-doc man-browser
The following NEW packages will be installed:
  binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev
  libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 
libmpc3
  libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make
  manpages manpages-dev
0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.7 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 
3.1.4-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 
1.0.3-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2
  Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils 
amd64 2.26.1-1ubuntu1~16.04.8
  Temporary failure resolving 'archive.ubuntu.com'
Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 
0.16.1-1
  Temporary failure resolving 'archive.ubuntu.com'

  
  It's a bit weird that if I run the command manually, it looks OK
  lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
  lxc-start -n c1
  lxc-attach -n c1 --clear-env -- apt update -y
  Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
  

[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests

2019-05-02 Thread Sean Feole
also affects disco, linux-azure 5.0.0-1005.5

04/26 18:31:44 DEBUG| utils:0153| [stdout] FAIL ept (7822 tests, 8 
unexpected failures)
90. 04/26 18:31:44 DEBUG| utils:0153| [stdout] 
TESTNAME=vmx_eoi_bitmap_ioapic_scan TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat 
-smp 2 -cpu host,+vmx -m 2048 -append vmx_eoi_bitmap_ioapic_scan_test

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1824228

Title:
  ept test fails in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Reproducible: Yes,
  Series: cosmic
  Kernel: "linux-azure 4.18.0-1015.15"
  Steps:

  1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,host-phys-bits,+vmx -m 2560 -append "ept_access*"
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 
1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd 
/tmp/tmp.RcwfbGP5Ou
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 477000
  cr4 = 20

  Test suite: ept_access_test_not_present

  Test suite: ept_access_test_read_only

  Test suite: ept_access_test_write_only

  Test suite: ept_access_test_read_write

  Test suite: ept_access_test_execute_only

  Test suite: ept_access_test_read_execute

  Test suite: ept_access_test_write_execute

  Test suite: ept_access_test_read_write_execute

  Test suite: ept_access_test_reserved_bits

  Test suite: ept_access_test_ignored_bits

  Test suite: ept_access_test_paddr_not_present_ad_disabled

  Test suite: ept_access_test_paddr_not_present_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_only_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312

  Test suite: ept_access_test_paddr_read_only_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_write

  Test suite: ept_access_test_paddr_read_write_execute

  Test suite: ept_access_test_paddr_read_execute_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == 

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

2019-05-02 Thread Sean Feole
also affecting linux-azure Disco, 5.0.0-1005.5
Instances:  Standard_D16s_v3 , Standard_D2_v3 , Standard_D2s_v3, 
Standard_E2s_v3, Standard_F2s_v2, Standard_F32s_v2

-- 
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/1821394

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: 

[Kernel-packages] [Bug 1826143] Re: linux-azure: 5.0.0-1005.5 -proposed tracker

2019-05-02 Thread Sean Feole
regression testing:

monotonic_time: 1774959 : clock test in monotonic_time will fail on Azure 
Instances
kvm_unit_tests: 1824228: ept test fails in kvm_unit_tests , 1821394: vmx tests 
fail in kvm_unit_tests , 1821152: lxc-test-no-new-privs failed with Temporary 
failure resolving 'archive.ubuntu.com'


** Tags added: regression-testing-passed

-- 
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/1826143

Title:
  linux-azure: 5.0.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826150
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 10:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826143/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1774959] Re: clock test in monotonic_time will fail on Azure Instances

2019-05-02 Thread Sean Feole
Stats for Comment #3  
Kernel: 5.0.0-1005.5-azure  
Cloud: Azure
Series: Disco

-- 
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/1774959

Title:
  clock test in monotonic_time will fail on Azure Instances

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Among all of the Azure node, this test only failed on these two nodes:

  Seen on the following instances:

  Basic_A2
  Standard_D2_v3
  Standard_D2s_v3
  Standard_E4s_v3
  Standard_E64-16s 
  Standard_F2s_v2
   

  
  Steps to reproduce:
   1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
   2. make -C autotest-client-tests/monotonic_time/src
   3. sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc

  Results:
  $ sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc

   Running 'make '
   cc -O -std=gnu99 -Wall -c -o time_test.o time_test.c
   cc -O -std=gnu99 -Wall -c -o cpuset.o cpuset.c
   cc -O -std=gnu99 -Wall -c -o threads.o threads.c
   cc -O -std=gnu99 -Wall -c -o logging.o logging.c
   cc -o time_test time_test.o cpuset.o threads.o logging.o -lpthread -lrt
   Running '/home/azure/autotest/client/tmp/monotonic_time/src/time_test 
--duration 300 clock'
   Time test command exit status: 1
   Exception escaping from test:
   Traceback (most recent call last):
   File "/home/azure/autotest/client/shared/test.py", line 411, in
   _exec_call_test_function(self.execute, *p_args, **p_dargs)
   File "/home/azure/autotest/client/shared/test.py", line 823, in 
_call_test_function
   return func(*args, **dargs)
   File "/home/azure/autotest/client/shared/test.py", line 291, in execute
   postprocess_profiled_run, args, dargs)
   File "/home/azure/autotest/client/shared/test.py", line 212, in 
_call_run_once
   self.run_once(*args, **dargs)
   File "/home/azure/autotest/client/tests/monotonic_time/monotonic_time.py", 
line 53, in run_once
   raise error.TestFail(line)
   TestFail: FAIL: clock-worst-warp=-100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774959/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1774959] Re: clock test in monotonic_time will fail on Azure Instances

2019-05-02 Thread Sean Feole
Failures on Azure still crop up from time to time even after fixes have
been applied.  Latest batch is on Standard_E2s_v3 instances.

04/26 21:05:17 DEBUG| utils:0116| Running 
'/home/azure/autotest/client/tmp/monotonic_time/src/time_test --duration 300 
tsc_lfence'
04/26 21:10:17 INFO |monotonic_:0048| Time test command exit status: 1
04/26 21:10:17 ERROR|  test:0414| Exception escaping from test:
Traceback (most recent call last):
  File "/home/azure/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/azure/autotest/client/shared/test.py", line 823, in 
_call_test_function
return func(*args, **dargs)
  File "/home/azure/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
  File "/home/azure/autotest/client/shared/test.py", line 212, in _call_run_once
self.run_once(*args, **dargs)
  File "/home/azure/autotest/client/tests/monotonic_time/monotonic_time.py", 
line 54, in run_once
raise error.TestFail(line)
TestFail: FAIL: tsc_lfence-worst-warp=-3
04/26 21:10:17 ERROR|  parallel:0033| child process failed
04/26 21:10:17 DEBUG|  parallel:0037| Traceback (most recent call last):
04/26 21:10:17 DEBUG|  parallel:0037|   File 
"/home/azure/autotest/client/parallel.py", line 25, in fork_start
04/26 21:10:17 DEBUG|  parallel:0037| l()
04/26 21:10:17 DEBUG|  parallel:0037|   File 
"/home/azure/autotest/client/job.py", line 505, in 
04/26 21:10:17 DEBUG|  parallel:0037| l = lambda: test.runtest(self, url, 
tag, args, dargs)
04/26 21:10:17 DEBUG|  parallel:0037|   File 
"/home/azure/autotest/client/test.py", line 125, in runtest
04/26 21:10:17 DEBUG|  parallel:0037| job.sysinfo.log_after_each_iteration)
04/26 21:10:17 DEBUG|  parallel:0037|   File 
"/home/azure/autotest/client/shared/test.py", line 913, in runtest
04/26 21:10:17 DEBUG|  parallel:0037| mytest._exec(args, dargs)
04/26 21:10:17 DEBUG|  parallel:0037|   File 
"/home/azure/autotest/client/shared/test.py", line 411, in _exec
04/26 21:10:17 DEBUG|  parallel:0037| _call_test_function(self.execute, 
*p_args, **p_dargs)
04/26 21:10:17 DEBUG|  parallel:0037|   File 
"/home/azure/autotest/client/shared/test.py", line 823, in _call_test_function
04/26 21:10:17 DEBUG|  parallel:0037| return func(*args, **dargs)
04/26 21:10:17 DEBUG|  parallel:0037|   File 
"/home/azure/autotest/client/shared/test.py", line 291, in execute
04/26 21:10:17 DEBUG|  parallel:0037| postprocess_profiled_run, args, dargs)
04/26 21:10:17 DEBUG|  parallel:0037|   File 
"/home/azure/autotest/client/shared/test.py", line 212, in _call_run_once
04/26 21:10:17 DEBUG|  parallel:0037| self.run_once(*args, **dargs)
04/26 21:10:17 DEBUG|  parallel:0037|   File 
"/home/azure/autotest/client/tests/monotonic_time/monotonic_time.py", line 54, 
in run_once
04/26 21:10:17 DEBUG|  parallel:0037| raise error.TestFail(line)
04/26 21:10:17 DEBUG|  parallel:0037| TestFail: FAIL: tsc_lfence-worst-warp=-3
04/26 21:10:17 INFO |   job:0215|   FAILmonotonic_time.tsc  
monotonic_time.tsc  timestamp=1556313017localtime=Apr 26 21:10:17   
FAIL: tsc_lfence-worst-warp=-3
04/26 21:10:17 INFO |   job:0215|   END FAILmonotonic_time.tsc  
monotonic_time.tsc  timestamp=1556313017localtime=Apr 26 21:10:17

-- 
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/1774959

Title:
  clock test in monotonic_time will fail on Azure Instances

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Among all of the Azure node, this test only failed on these two nodes:

  Seen on the following instances:

  Basic_A2
  Standard_D2_v3
  Standard_D2s_v3
  Standard_E4s_v3
  Standard_E64-16s 
  Standard_F2s_v2
   

  
  Steps to reproduce:
   1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
   2. make -C autotest-client-tests/monotonic_time/src
   3. sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc

  Results:
  $ sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc

   Running 'make '
   cc -O -std=gnu99 -Wall -c -o time_test.o time_test.c
   cc -O -std=gnu99 -Wall -c -o cpuset.o cpuset.c
   cc -O -std=gnu99 -Wall -c -o threads.o threads.c
   cc -O -std=gnu99 -Wall -c -o logging.o logging.c
   cc -o time_test time_test.o cpuset.o threads.o logging.o -lpthread -lrt
   Running '/home/azure/autotest/client/tmp/monotonic_time/src/time_test 
--duration 300 clock'
   Time test command exit status: 1
   Exception escaping from test:
   Traceback (most recent call last):
   File "/home/azure/autotest/client/shared/test.py", line 411, in
   _exec_call_test_function(self.execute, *p_args, **p_dargs)
   File "/home/azure/autotest/client/shared/test.py", line 823, in 
_call_test_function

[Kernel-packages] [Bug 1826163] Re: linux-aws: 4.18.0-1015.17 -proposed tracker

2019-05-02 Thread Sean Feole
regression testing

amd64
ubuntu_kvm_tests: 1821390 - apic-split will fail in kvm_units_tests
ubuntu_kvm_tests: 1821394 - vmx tests fail in kvm_unit_tests


** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1826163

Title:
  linux-aws: 4.18.0-1015.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1826161 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826171
  phase: Testing
  phase-changed: Thursday, 25. April 2019 23:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826163/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826141] Re: linux-aws: 5.0.0-1005.5 -proposed tracker

2019-05-02 Thread Sean Feole
regression tests:

amd64:
ubuntu_kvm_tests: 1821394 - vmx tests fail in kvm_unit_tests

arm64:
ubuntu_stress_smoke: 1827376 - ubuntu_stress_smoke failures on disco - arm64 - 
linux-aws


** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1826141

Title:
  linux-aws: 5.0.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826150
  phase: Testing
  phase-changed: Friday, 26. April 2019 15:44 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826141/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1821390] Re: apic-split will fail in kvm_units_tests

2019-05-02 Thread Sean Feole
also affects aws i3.metal disco , cosmic 4.18.0-1015.17

-- 
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/1821390

Title:
  apic-split will fail in kvm_units_tests

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-aws source package in Cosmic:
  New
Status in linux-azure source package in Cosmic:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make

  4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split 
TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 
2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd 
/tmp/tmp.ZHQwPUOuLD
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  PASS: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  PASS: apic_disable: Local apic enabled in xAPIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 1050014
  PASS: apic_disable: *0xfee00080: 0
  PASS: apic_disable: *0xfee00080: f0
  PASS: apic_disable: Local apic enabled in x2APIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: x2apic enabled to disabled state
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  FAIL: PV IPIs testing
  PASS: nmi-after-sti
  PASS: multiple nmi
  PASS: APIC LVT timer one shot
  starting apic change mode
  PASS: TMICT value reset
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should have reached 0
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should not be reset to TMICT value
  PASS: TMCCT should be reset to the initial-count
  PASS: TMCCT should not be reset to init
  PASS: TMCCT should have reach zero
  PASS: TMCCT should stay at zero
  PASS: tsc deadline timer
  PASS: tsc deadline timer clearing
  SUMMARY: 51 tests, 1 unexpected failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

2019-05-02 Thread Sean Feole
I have seen this fail in Disco on linux-aws but only on i3.metal.

TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx 
-append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test -vmx_controls_test"
04/30 02:54:41 DEBUG| utils:0153| [stdout] FAIL vmx (timeout; duration=90s)


** Tags added: disco

-- 
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/1821394

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; 

[Kernel-packages] [Bug 1826168] Re: linux-gcp: 4.18.0-1010.11 -proposed tracker

2019-04-30 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1826168

Title:
  linux-gcp: 4.18.0-1010.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1826167 (bionic/linux-gcp-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826171
  phase: Testing
  phase-changed: Friday, 26. April 2019 15:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826168/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822830] Re: linux-fips: 4.4.0-1008.10 -proposed tracker

2019-04-23 Thread Sean Feole
** Tags added: regression-testsing-passed

** Tags removed: regression-testsing-passed
** Tags added: regression-testing-passed

-- 
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/1822830

Title:
  linux-fips: 4.4.0-1008.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Ready for Testing
  phase-changed: Tuesday, 23. April 2019 10:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822830/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

2019-04-19 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1822810

Title:
  linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Wednesday, 17. April 2019 17:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822810/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker

2019-04-19 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1822811

Title:
  linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822812
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824592] Re: linux-fips: 4.15.0-1005.6 -proposed tracker

2019-04-18 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1824592

Title:
  linux-fips: 4.15.0-1005.6 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Wednesday, 17. April 2019 15:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824592/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker

2019-04-18 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1822817

Title:
  linux-azure: 4.15.0-1042.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 14:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822817/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1814237] Re: ubuntu_nbd_smoke_test failed with I/O error on X-4.15

2019-04-18 Thread Sean Feole
Affects , 4.15.0-1036.38~16.04.1 linux-aws-hwe

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1814237

Title:
  ubuntu_nbd_smoke_test failed with I/O error on X-4.15

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Kernel: 4.15.0-45.48~16.04.1

  creating backing nbd image /tmp/nbd_image.img

  

  Image path:/tmp/nbd_image.img
  Mount point:   /mnt/nbd-test-25789
  Date:  Thu Jan 31 14:42:42 UTC 2019
  Host:  onibi
  Kernel:4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 
UTC 2019
  Machine:   onibi x86_64 x86_64
  CPUs online:   4
  CPUs total:4
  Page size: 4096
  Pages avail:   1351388
  Pages total:   2038431
  Free space:
  Filesystem  Size  Used Avail Use% Mounted on
  udev3.9G 0  3.9G   0% /dev
  tmpfs   797M   17M  780M   3% /run
  /dev/sda1   917G  9.1G  861G   2% /
  tmpfs   3.9G  4.0K  3.9G   1% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   3.9G 0  3.9G   0% /sys/fs/cgroup
  tmpfs   797M 0  797M   0% /run/user/1000
  tmpfs   100K 0  100K   0% /var/lib/lxd/shmounts
  tmpfs   100K 0  100K   0% /var/lib/lxd/devlxd
  cgmfs   100K 0  100K   0% /run/cgmanager/fs
  


  NBD device /dev/nbd0 created
  found nbd export
  NBD exports found:
  test
  starting client with NBD device /dev/nbd0
  Negotiation: ..size = 128MB
  creating ext4 on /dev/nbd0
  mkfs on /dev/nbd0 succeeded after 0 attempt(s)
  checking ext4 on /dev/nbd0
  fsck from util-linux 2.27.1
  /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks

  mount:
  /dev/nbd0 on /mnt/nbd-test-25789 type ext4 (rw,relatime,data=ordered)
  mounted on /dev/nbd0

  free:
  Filesystem 1K-blocks  Used Available Use% Mounted on
  /dev/nbd0 122835  1550112111   2% /mnt/nbd-test-25789

  creating large file /mnt/nbd-test-25789/largefile
  -rw-r--r-- 1 root root 100M Jan 31 14:42 /mnt/nbd-test-25789/largefile

  free:
  Filesystem 1K-blocks   Used Available Use% Mounted on
  /dev/nbd0 122835 103951  9710  92% /mnt/nbd-test-25789

  removing file /mnt/nbd-test-25789/largefile
  unmounting /mnt/nbd-test-25789
  stopping client
  disconnect, sock, done
  Found kernel warning, IO error and/or call trace
  echo
  [ 4593.254552] creating backing nbd image /tmp/nbd_image.img
  [ 4595.506134] NBD device /dev/nbd0 created
  [ 4595.557990] found nbd export
  [ 4596.604855] starting client with NBD device /dev/nbd0
  [ 4596.606795] creating ext4 on /dev/nbd0
  [ 4597.013721] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
  [ 4597.390241] checking ext4 on /dev/nbd0
  [ 4597.455371] EXT4-fs (nbd0): mounted filesystem with ordered data mode. 
Opts: (null)
  [ 4597.460552] mounted on /dev/nbd0
  [ 4597.461810] creating large file /mnt/nbd-test-25789/largefile
  [ 4599.056704] removing file /mnt/nbd-test-25789/largefile
  [ 4599.276298] unmounting /mnt/nbd-test-25789
  [ 4600.319460] stopping client
  [ 4600.320083] block nbd0: NBD_DISCONNECT
  [ 4600.320127] block nbd0: shutting down sockets
  [ 4600.320267] nbd0: detected capacity change from 0 to 134217728
  [ 4600.320306] print_req_error: 7 callbacks suppressed
  [ 4600.320308] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.325890] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.333002] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.338653] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.345687] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.351253] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.358279] ldm_validate_partition_table(): Disk read failed.
  [ 4600.358305] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.363892] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.371075] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.376645] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.383687] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.389230] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.396307] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.401819] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.408826] Dev nbd0: unable to read RDB block 0
  [ 4600.413467] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.418955] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.425858] print_req_error: I/O error, dev nbd0, sector 24
  [ 4600.431433] Buffer I/O error on dev nbd0, logical block 3, async page 

[Kernel-packages] [Bug 1824774] Re: linux-aws: 4.4.0-1081.91 -proposed tracker

2019-04-18 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1824774

Title:
  linux-aws: 4.4.0-1081.91 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:09 UTC
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822812] Re: linux-oracle: 4.15.0-1011.13 -proposed tracker

2019-04-18 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1822812

Title:
  linux-oracle: 4.15.0-1011.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822811 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 08:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822812/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824839] Re: linux-azure: 4.18.0-1016.16~18.04.1 -proposed tracker

2019-04-18 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1824839

Title:
  linux-azure: 4.18.0-1016.16~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  derivatives: bug 1824838 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1824841
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824839/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824773] Re: linux-aws: 4.15.0-1037.39 -proposed tracker

2019-04-18 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1824773

Title:
  linux-aws: 4.15.0-1037.39 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824773/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker

2019-04-17 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1824771

Title:
  linux-aws: 4.18.0-1014.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822787 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824771/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1809624] Re: net test in ubuntu_kernel_selftest failed on s390x KVM

2019-04-17 Thread Sean Feole
** Summary changed:

- net test in ubuntu_kernel_selftest failed on B s390x KVM
+ net test in ubuntu_kernel_selftest failed on s390x KVM

-- 
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/1809624

Title:
  net test in ubuntu_kernel_selftest failed on s390x KVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New

Bug description:
  Verified with the testing tool in the upstream kernel, this issue can
  be reproduced with it.

   not ok 1..4 selftests:  reuseport_dualstack [FAIL]
   selftests: reuseaddr_conflict

  Please find the complete test report here:
  https://pastebin.ubuntu.com/p/3sRh6Nr9KR/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Dec 24 03:10:49 2018
  HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809624/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1768452] Re: Unable to insert test_bpf module for ubuntu_bpf_jit s390x

2019-04-17 Thread Sean Feole
** Summary changed:

- Unable to insert test_bpf module for ubuntu_bpf_jit on Xenial s390x
+ Unable to insert test_bpf module for ubuntu_bpf_jit s390x

-- 
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/1768452

Title:
  Unable to insert test_bpf module for ubuntu_bpf_jit s390x

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  After the test_bpf insert issue for Xenial was fixed in bug 1765698

  But it looks like the s390x needs some extra work.
  $ sudo modprobe test_bpf
  modprobe: ERROR: could not insert 'test_bpf': Invalid argument

  4 tests failed here:
test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create 
err=-524 len=4096
test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create 
err=-524 len=4096
test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096
test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524

  Complete test result:
  https://pastebin.ubuntu.com/p/zMDwVjwF7X/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-123-generic 4.4.0-123.147
  ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128
  Uname: Linux 4.4.0-123-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed May  2 03:45:22 2018
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-123-generic N/A
   linux-backports-modules-4.4.0-123-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1768452/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824841] Re: linux-azure: 4.18.0-1016.16 -proposed tracker

2019-04-17 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1824841

Title:
  linux-azure: 4.18.0-1016.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1824839 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824841/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

2019-04-16 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1822807

Title:
  linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822808
  phase: Testing
  phase-changed: Thursday, 11. April 2019 12:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822807/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker

2019-04-15 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1822808

Title:
  linux-gcp: 4.15.0-1030.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822807 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Friday, 12. April 2019 01:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822808/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1821152] Re: LXC test on KVM instances failed with Temporary failure resolving 'archive.ubuntu.com'

2019-04-10 Thread Sean Feole
** Tags added: aws azure bionic

** Tags removed: aws
** Tags added: kvm

** Summary changed:

- LXC test on KVM instances failed with Temporary failure resolving 
'archive.ubuntu.com'
+ lxc-test-no-new-privs failed with Temporary failure resolving 
'archive.ubuntu.com'

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1821152

Title:
  lxc-test-no-new-privs failed with Temporary failure resolving
  'archive.ubuntu.com'

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  It seems this failure only exist in KVM instances.

FAIL: lxc-tests: lxc-test-no-new-privs (37s)
---
+ DONE=0
+ trap cleanup EXIT SIGHUP SIGINT SIGTERM
+ mkdir -p /etc/lxc/
+ cat
+ ARCH=i386
+ type dpkg
++ dpkg --print-architecture
+ ARCH=amd64
+ lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
Setting up the GPG keyring
Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs

---
You just created an Ubuntu xenial amd64 (20190320_07:42) container.

To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
+ echo 'lxc.no_new_privs = 1'
+ lxc-start -n c1
++ lxc-info -n c1 -p -H
+ p1=8818
+ '[' 8818 '!=' -1 ']'
+ sleep 5s
+ lxc-attach -n c1 --clear-env -- apt update -y

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
+ lxc-attach -n c1 --clear-env -- apt install -y gcc make

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev 
libcc1-0
  libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 
libmpfr4
  libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages 
manpages-dev
Suggested packages:
  binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool
  flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg
  libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg
  libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc
  make-doc man-browser
The following NEW packages will be installed:
  binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev
  libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 
libmpc3
  libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make
  manpages manpages-dev
0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.7 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 
3.1.4-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 
1.0.3-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2
  Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils 
amd64 2.26.1-1ubuntu1~16.04.8
  Temporary failure resolving 'archive.ubuntu.com'
Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 
0.16.1-1
  Temporary failure resolving 'archive.ubuntu.com'

  
  It's a bit weird that if I run the command manually, it looks OK
  lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
  lxc-start -n c1
  lxc-attach -n c1 

[Kernel-packages] [Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker

2019-04-10 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1822790

Title:
  linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  derivatives: bug 1822789 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822790/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests

2019-04-10 Thread Sean Feole
also affects bionic, linux-azure 4.18.0-1015.15~18.04.1

** Tags added: bionic

-- 
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/1824228

Title:
  ept test fails in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  Reproducible: Yes,
  Series: cosmic
  Kernel: "linux-azure 4.18.0-1015.15"
  Steps:

  1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,host-phys-bits,+vmx -m 2560 -append "ept_access*"
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 
1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd 
/tmp/tmp.RcwfbGP5Ou
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 477000
  cr4 = 20

  Test suite: ept_access_test_not_present

  Test suite: ept_access_test_read_only

  Test suite: ept_access_test_write_only

  Test suite: ept_access_test_read_write

  Test suite: ept_access_test_execute_only

  Test suite: ept_access_test_read_execute

  Test suite: ept_access_test_write_execute

  Test suite: ept_access_test_read_write_execute

  Test suite: ept_access_test_reserved_bits

  Test suite: ept_access_test_ignored_bits

  Test suite: ept_access_test_paddr_not_present_ad_disabled

  Test suite: ept_access_test_paddr_not_present_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_only_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312

  Test suite: ept_access_test_paddr_read_only_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_write

  Test suite: ept_access_test_paddr_read_write_execute

  Test suite: ept_access_test_paddr_read_execute_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fe15 401577 4039d0 

[Kernel-packages] [Bug 1821152] Re: LXC test on KVM instances failed with Temporary failure resolving 'archive.ubuntu.com'

2019-04-10 Thread Sean Feole
appears to affect linux-azure: 4.18.0-1015.15, Standard_F2s_v2-ubuntu_lxc
04/05 16:42:33 DEBUG| utils:0153| [stdout] FAIL: lxc-tests: 
lxc-test-no-new-privs (37s)


** Also affects: linux-azure (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1821152

Title:
  LXC test on KVM instances failed with Temporary failure resolving
  'archive.ubuntu.com'

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  It seems this failure only exist in KVM instances.

FAIL: lxc-tests: lxc-test-no-new-privs (37s)
---
+ DONE=0
+ trap cleanup EXIT SIGHUP SIGINT SIGTERM
+ mkdir -p /etc/lxc/
+ cat
+ ARCH=i386
+ type dpkg
++ dpkg --print-architecture
+ ARCH=amd64
+ lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
Setting up the GPG keyring
Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs

---
You just created an Ubuntu xenial amd64 (20190320_07:42) container.

To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
+ echo 'lxc.no_new_privs = 1'
+ lxc-start -n c1
++ lxc-info -n c1 -p -H
+ p1=8818
+ '[' 8818 '!=' -1 ']'
+ sleep 5s
+ lxc-attach -n c1 --clear-env -- apt update -y

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
+ lxc-attach -n c1 --clear-env -- apt install -y gcc make

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev 
libcc1-0
  libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 
libmpfr4
  libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages 
manpages-dev
Suggested packages:
  binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool
  flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg
  libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg
  libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc
  make-doc man-browser
The following NEW packages will be installed:
  binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev
  libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 
libmpc3
  libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make
  manpages manpages-dev
0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.7 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 
3.1.4-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 
1.0.3-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2
  Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils 
amd64 2.26.1-1ubuntu1~16.04.8
  Temporary failure resolving 'archive.ubuntu.com'
Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 
0.16.1-1
  Temporary failure resolving 'archive.ubuntu.com'

  
  It's a bit weird that if I run the command manually, it looks OK
  lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
  lxc-start -n c1
  lxc-attach -n c1 --clear-env -- apt 

[Kernel-packages] [Bug 1822791] Re: linux-azure: 4.18.0-1015.15 -proposed tracker

2019-04-10 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1822791

Title:
  linux-azure: 4.18.0-1015.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822790 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Thursday, 04. April 2019 17:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822791/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests

2019-04-10 Thread Sean Feole
Affected instances:
Standard_D2s_v3
Standard_D2_v3
Standard_DC2s
Standard_E2s_v3
Standard_F2s_v2

-- 
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/1824228

Title:
  ept test fails in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  Reproducible: Yes,
  Series: cosmic
  Kernel: "linux-azure 4.18.0-1015.15"
  Steps:

  1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,host-phys-bits,+vmx -m 2560 -append "ept_access*"
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 
1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd 
/tmp/tmp.RcwfbGP5Ou
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 477000
  cr4 = 20

  Test suite: ept_access_test_not_present

  Test suite: ept_access_test_read_only

  Test suite: ept_access_test_write_only

  Test suite: ept_access_test_read_write

  Test suite: ept_access_test_execute_only

  Test suite: ept_access_test_read_execute

  Test suite: ept_access_test_write_execute

  Test suite: ept_access_test_read_write_execute

  Test suite: ept_access_test_reserved_bits

  Test suite: ept_access_test_ignored_bits

  Test suite: ept_access_test_paddr_not_present_ad_disabled

  Test suite: ept_access_test_paddr_not_present_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_only_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312

  Test suite: ept_access_test_paddr_read_only_ad_enabled
  Host skipping test: EPT AD bits not supported.

  Test suite: ept_access_test_paddr_read_write

  Test suite: ept_access_test_paddr_read_write_execute

  Test suite: ept_access_test_paddr_read_execute_ad_disabled
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312
  EPT_VLT_RD expected
  FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 

[Kernel-packages] [Bug 1824228] [NEW] ept test fails in kvm_unit_tests

2019-04-10 Thread Sean Feole
Public bug reported:

Reproducible: Yes,
Series: cosmic
Kernel: "linux-azure 4.18.0-1015.15"
Steps:

1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib
2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
3.) cd kvm-unit-tests; ./configure; make
4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,host-phys-bits,+vmx -m 2560 -append "ept_access*"
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu 
host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd 
/tmp/tmp.RcwfbGP5Ou
enabling apic
paging enabled
cr0 = 80010011
cr3 = 477000
cr4 = 20

Test suite: ept_access_test_not_present

Test suite: ept_access_test_read_only

Test suite: ept_access_test_write_only

Test suite: ept_access_test_read_write

Test suite: ept_access_test_execute_only

Test suite: ept_access_test_read_execute

Test suite: ept_access_test_write_execute

Test suite: ept_access_test_read_write_execute

Test suite: ept_access_test_reserved_bits

Test suite: ept_access_test_ignored_bits

Test suite: ept_access_test_paddr_not_present_ad_disabled

Test suite: ept_access_test_paddr_not_present_ad_enabled
Host skipping test: EPT AD bits not supported.

Test suite: ept_access_test_paddr_read_only_ad_disabled
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x008b - 
''''''''''''''1000'1011 
- 139
RHS: 0x008a - 
''''''''''''''1000'1010 
- 138
STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312

Test suite: ept_access_test_paddr_read_only_ad_enabled
Host skipping test: EPT AD bits not supported.

Test suite: ept_access_test_paddr_read_write

Test suite: ept_access_test_paddr_read_write_execute

Test suite: ept_access_test_paddr_read_execute_ad_disabled
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fe15 401577 4039d0 400312
EPT_VLT_RD expected
FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual)
LHS: 0x00ab - 
''''''''''''''1010'1011 
- 171
RHS: 0x00aa - 
''''''''''''''1010'1010 
- 170
STACK: 40f328 40f8fb 40fb0b 40fe42 401577 4039d0 400312

Test suite: ept_access_test_paddr_read_execute_ad_enabled

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

2019-04-10 Thread Sean Feole
** Also affects: linux-azure (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1821394

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
  FAIL: Enable-EPT 

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

2019-04-10 Thread Sean Feole
affects 4.18.0-1013.15 linux-aws

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1821394

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8192: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits 

[Kernel-packages] [Bug 1822788] Re: linux-aws: 4.18.0-1013.15 -proposed tracker

2019-04-10 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1822788

Title:
  linux-aws: 4.18.0-1013.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822787 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 03. April 2019 23:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822788/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1821390] Re: apic-split will fail in kvm_units_tests

2019-04-10 Thread Sean Feole
affects, 4.18.0-1013.15 linux-aws

** Summary changed:

- apic-split will fail in kvm_units_tests on aws i3.metal 
+ apic-split will fail in kvm_units_tests

-- 
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/1821390

Title:
  apic-split will fail in kvm_units_tests

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-aws source package in Cosmic:
  New
Status in linux-azure source package in Cosmic:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make

  4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split 
TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 
2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd 
/tmp/tmp.ZHQwPUOuLD
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  PASS: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  PASS: apic_disable: Local apic enabled in xAPIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 1050014
  PASS: apic_disable: *0xfee00080: 0
  PASS: apic_disable: *0xfee00080: f0
  PASS: apic_disable: Local apic enabled in x2APIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: x2apic enabled to disabled state
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  FAIL: PV IPIs testing
  PASS: nmi-after-sti
  PASS: multiple nmi
  PASS: APIC LVT timer one shot
  starting apic change mode
  PASS: TMICT value reset
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should have reached 0
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should not be reset to TMICT value
  PASS: TMCCT should be reset to the initial-count
  PASS: TMCCT should not be reset to init
  PASS: TMCCT should have reach zero
  PASS: TMCCT should stay at zero
  PASS: tsc deadline timer
  PASS: tsc deadline timer clearing
  SUMMARY: 51 tests, 1 unexpected failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1774959] Re: clock test in monotonic_time will fail on Azure Standard_E4s_v3 / Standard_E64-16s / AWS m5a.large

2019-04-05 Thread Sean Feole
We still see random fails on Azure instances, it does not appear to be
isolated to a particular instance

03:19:44 DEBUG| Running 
'/home/azure/autotest/client/tmp/monotonic_time/src/time_test --duration 300 
tsc_lfence'
03:24:44 INFO | Time test command exit status: 1
03:24:44 ERROR| Exception escaping from test:
Traceback (most recent call last):
  File "/home/azure/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/azure/autotest/client/shared/test.py", line 823, in 
_call_test_function
return func(*args, **dargs)
  File "/home/azure/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
  File "/home/azure/autotest/client/shared/test.py", line 212, in _call_run_once
self.run_once(*args, **dargs)
  File "/home/azure/autotest/client/tests/monotonic_time/monotonic_time.py", 
line 54, in run_once
raise error.TestFail(line)
TestFail: FAIL: tsc_lfence-worst-warp=-30

** Changed in: ubuntu-kernel-tests
   Status: New => Confirmed

** Changed in: linux-azure (Ubuntu)
   Status: New => Confirmed

** Description changed:

  Among all of the Azure node, this test only failed on these two nodes:
  
+ Seen on the following instances:
+ 
+ Basic_A2
+ Standard_D2_v3
+ Standard_D2s_v3
+ Standard_E4s_v3
+ Standard_E64-16s 
+ Standard_F2s_v2
+  
+ 
+ 
  Steps to reproduce:
-  1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
-  2. make -C autotest-client-tests/monotonic_time/src
-  3. sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc
+  1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
+  2. make -C autotest-client-tests/monotonic_time/src
+  3. sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc
  
  Results:
  $ sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc
  
-  Running 'make '
-  cc -O -std=gnu99 -Wall -c -o time_test.o time_test.c
-  cc -O -std=gnu99 -Wall -c -o cpuset.o cpuset.c
-  cc -O -std=gnu99 -Wall -c -o threads.o threads.c
-  cc -O -std=gnu99 -Wall -c -o logging.o logging.c
-  cc -o time_test time_test.o cpuset.o threads.o logging.o -lpthread -lrt
-  Running '/home/azure/autotest/client/tmp/monotonic_time/src/time_test 
--duration 300 clock'
-  Time test command exit status: 1
-  Exception escaping from test:
-  Traceback (most recent call last):
-  File "/home/azure/autotest/client/shared/test.py", line 411, in 
-  _exec_call_test_function(self.execute, *p_args, **p_dargs)
-  File "/home/azure/autotest/client/shared/test.py", line 823, in 
_call_test_function
-  return func(*args, **dargs)
-  File "/home/azure/autotest/client/shared/test.py", line 291, in execute
-  postprocess_profiled_run, args, dargs)
-  File "/home/azure/autotest/client/shared/test.py", line 212, in 
_call_run_once
-  self.run_once(*args, **dargs)
-  File "/home/azure/autotest/client/tests/monotonic_time/monotonic_time.py", 
line 53, in run_once
-  raise error.TestFail(line)
-  TestFail: FAIL: clock-worst-warp=-100
+  Running 'make '
+  cc -O -std=gnu99 -Wall -c -o time_test.o time_test.c
+  cc -O -std=gnu99 -Wall -c -o cpuset.o cpuset.c
+  cc -O -std=gnu99 -Wall -c -o threads.o threads.c
+  cc -O -std=gnu99 -Wall -c -o logging.o logging.c
+  cc -o time_test time_test.o cpuset.o threads.o logging.o -lpthread -lrt
+  Running '/home/azure/autotest/client/tmp/monotonic_time/src/time_test 
--duration 300 clock'
+  Time test command exit status: 1
+  Exception escaping from test:
+  Traceback (most recent call last):
+  File "/home/azure/autotest/client/shared/test.py", line 411, in
+  _exec_call_test_function(self.execute, *p_args, **p_dargs)
+  File "/home/azure/autotest/client/shared/test.py", line 823, in 
_call_test_function
+  return func(*args, **dargs)
+  File "/home/azure/autotest/client/shared/test.py", line 291, in execute
+  postprocess_profiled_run, args, dargs)
+  File "/home/azure/autotest/client/shared/test.py", line 212, in 
_call_run_once
+  self.run_once(*args, **dargs)
+  File "/home/azure/autotest/client/tests/monotonic_time/monotonic_time.py", 
line 53, in run_once
+  raise error.TestFail(line)
+  TestFail: FAIL: clock-worst-warp=-100

** Summary changed:

- clock test in monotonic_time will fail on Azure Standard_E4s_v3 / 
Standard_E64-16s / AWS m5a.large
+ clock test in monotonic_time will fail on Azure Instances

-- 
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/1774959

Title:
  clock test in monotonic_time will fail on Azure Instances

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Among all of the Azure node, this test only failed on these two nodes:

  Seen on the following instances:

  Basic_A2
  Standard_D2_v3
  Standard_D2s_v3
  Standard_E4s_v3
  Standard_E64-16s 
  

[Kernel-packages] [Bug 1822793] Re: linux-gcp: 4.18.0-1009.10 -proposed tracker

2019-04-05 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1822793

Title:
  linux-gcp: 4.18.0-1009.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1822792 (bionic/linux-gcp-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Thursday, 04. April 2019 01:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822793/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1819707] Re: linux-fips: 4.15.0-1002.3 -proposed tracker

2019-04-04 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1819707

Title:
  linux-fips: 4.15.0-1002.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Holding before Release
  phase-changed: Friday, 05. April 2019 01:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag 
present

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819707/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker

2019-04-03 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1820326

Title:
  linux-fips: 4.4.0-1007.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1821724
  phase: Ready for Testing
  phase-changed: Tuesday, 02. April 2019 10:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820326/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

2019-04-01 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1819701

Title:
  linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Signoff
  phase-changed: Monday, 01. April 2019 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819701/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker

2019-04-01 Thread Sean Feole
We are still blocked in fips-proposed for SRU testing

-- 
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/1820326

Title:
  linux-fips: 4.4.0-1007.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1821724
  phase: Signoff
  phase-changed: Monday, 01. April 2019 11:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820326/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker

2019-03-29 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1819658

Title:
  linux-aws: 4.4.0-1040.43 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1821724
  phase: Testing
  phase-changed: Wednesday, 27. March 2019 20:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819658/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1819711] Re: linux-azure: 4.15.0-1041.45~14.04.1 -proposed tracker

2019-03-29 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1819711

Title:
  linux-azure: 4.15.0-1041.45~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819713
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 21:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819711/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1821726] Re: linux-aws: 4.4.0-1079.89 -proposed tracker

2019-03-29 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1821726

Title:
  linux-aws: 4.4.0-1079.89 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1821724
  phase: Testing
  phase-changed: Wednesday, 27. March 2019 12:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821726/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

2019-03-28 Thread Sean Feole
Hey Joe, Please see attached.  Simply update the system variable with
the username@ip  and run it.

** Attachment added: "rebootme.py"
   
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+attachment/5250368/+files/rebootme.py

-- 
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/1822118

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description:   In the event a particular Azure cloud instance is
  rebooted it's possible that it may never recover and the instance will
  break indefinitely.

  In My case, it was a kernel panic. See specifics below..

  
  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  
  I had a simple script to reboot an instance (X) amount of times, I chose 50, 
so the machine would power cycle by issuing a "reboot" from the terminal prompt 
just as a user would.   Once the machine came up, it captured dmesg and other 
bits then rebooted again until it reached 50. 

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  
  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  
  this only occurred once in my testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1819713] Re: linux-azure: 4.15.0-1041.45 -proposed tracker

2019-03-28 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1819713

Title:
  linux-azure: 4.15.0-1041.45 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1819711 (trusty/linux-azure)
  derivatives: bug 1819710 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 20:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819713/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822175] [NEW] i3.metal flavour type fails to respond after a reboot

2019-03-28 Thread Sean Feole
Public bug reported:

Series: Cosmic
Instance Size: I3.Metal
Region: (Default) US-WEST-2
Kernel: linux-aws

During SRU testing the i3.metal instance flavor type will sometimes fail
to respond after the instance is rebooted. Usually this has been seen at
least 2 or 3 times during at test cycle.

While rebooting an I3.Metal instance on the AWS Cloud. I observed the
following crash which resulting in tearing down the instance and
starting over. The instance was only restarted ~4 times at the time of
this failure.


[[0;32m  OK  [0m] Reached target Shutdown.
[[0;32m  OK  [0m] Reached target Final Step.
 Starting Reboot...
 Stopping LVM2 metadata daemon...
[[0;32m  OK  [0m] Stopped LVM2 metadata daemon.
[  447.340575] INFO: rcu_sched self-detected stall on CPU
[  447.340577] INFO: rcu_sched self-detected stall on CPU
[  447.340580] INFO: rcu_sched self-detected stall on CPU
[  447.340587] INFO: rcu_sched self-detected stall on CPU
[  447.340590] INFO: rcu_sched self-detected stall on CPU
[  447.340592] INFO: rcu_sched self-detected stall on CPU
[  447.340595] Uhhuh. NMI received for unknown reason 21 on CPU 0.
[  447.340599] INFO: rcu_sched self-detected stall on CPU
[  447.340602] INFO: rcu_sched self-detected stall on CPU
[  447.340606] INFO: rcu_sched self-detected stall on CPU
[  447.340614]  53-...!: (43 GPs behind) idle=7ce/1/0 softirq=392/392 fqs=0 
[  447.340617] INFO: rcu_sched self-detected stall on CPU
[  447.340621] Do you have a strange power saving mode enabled?
[  447.340628]  1-...!: (1 ticks this GP) idle=79e/1/0 softirq=881/881 fqs=0 
[  447.340632] INFO: rcu_sched self-detected stall on CPU
[  447.340634] INFO: rcu_sched self-detected stall on CPU
[  447.340636] INFO: rcu_sched self-detected stall on CPU
[  447.340639] INFO: rcu_sched self-detected stall on CPU
[  447.340641] INFO: rcu_sched self-detected stall on CPU
[  447.340644] INFO: rcu_sched self-detected stall on CPU
[  447.340647] INFO: rcu_sched self-detected stall on CPU

The full log can be seen in the attached file.

** Affects: linux-aws (Ubuntu)
 Importance: High
 Assignee: Colin Ian King (colin-king)
 Status: In Progress

** Attachment added: "awscrash.txt"
   
https://bugs.launchpad.net/bugs/1822175/+attachment/5250246/+files/awscrash.txt

** Changed in: linux-aws (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1822175

Title:
  i3.metal flavour type fails to respond after a reboot

Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  Series: Cosmic
  Instance Size: I3.Metal
  Region: (Default) US-WEST-2
  Kernel: linux-aws

  During SRU testing the i3.metal instance flavor type will sometimes
  fail to respond after the instance is rebooted. Usually this has been
  seen at least 2 or 3 times during at test cycle.

  While rebooting an I3.Metal instance on the AWS Cloud. I observed the
  following crash which resulting in tearing down the instance and
  starting over. The instance was only restarted ~4 times at the time of
  this failure.

  
  [[0;32m  OK  [0m] Reached target Shutdown.
  [[0;32m  OK  [0m] Reached target Final Step.
   Starting Reboot...
   Stopping LVM2 metadata daemon...
  [[0;32m  OK  [0m] Stopped LVM2 metadata daemon.
  [  447.340575] INFO: rcu_sched self-detected stall on CPU
  [  447.340577] INFO: rcu_sched self-detected stall on CPU
  [  447.340580] INFO: rcu_sched self-detected stall on CPU
  [  447.340587] INFO: rcu_sched self-detected stall on CPU
  [  447.340590] INFO: rcu_sched self-detected stall on CPU
  [  447.340592] INFO: rcu_sched self-detected stall on CPU
  [  447.340595] Uhhuh. NMI received for unknown reason 21 on CPU 0.
  [  447.340599] INFO: rcu_sched self-detected stall on CPU
  [  447.340602] INFO: rcu_sched self-detected stall on CPU
  [  447.340606] INFO: rcu_sched self-detected stall on CPU
  [  447.340614]53-...!: (43 GPs behind) idle=7ce/1/0 softirq=392/392 
fqs=0 
  [  447.340617] INFO: rcu_sched self-detected stall on CPU
  [  447.340621] Do you have a strange power saving mode enabled?
  [  447.340628]1-...!: (1 ticks this GP) idle=79e/1/0 softirq=881/881 
fqs=0 
  [  447.340632] INFO: rcu_sched self-detected stall on CPU
  [  447.340634] INFO: rcu_sched self-detected stall on CPU
  [  447.340636] INFO: rcu_sched self-detected stall on CPU
  [  447.340639] INFO: rcu_sched self-detected stall on CPU
  [  447.340641] INFO: rcu_sched self-detected stall on CPU
  [  447.340644] INFO: rcu_sched self-detected stall on CPU
  [  447.340647] INFO: rcu_sched self-detected stall on CPU

  The full log can be seen in the attached file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1822175/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to   

[Kernel-packages] [Bug 1819703] Re: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker

2019-03-28 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1819703

Title:
  linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819704
  phase: Testing
  phase-changed: Monday, 25. March 2019 14:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819703/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1819704] Re: linux-oracle: 4.15.0-1010.12 -proposed tracker

2019-03-28 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1819704

Title:
  linux-oracle: 4.15.0-1010.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1819703 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 17:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819704/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

2019-03-28 Thread Sean Feole
** Summary changed:

- vmx tests fail in kvm_unit_tests on aws i3.metal
+ vmx tests fail in kvm_unit_tests

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1821394

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8192: vmlaunch fails
  FAIL: Enable-EPT 

[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.

2019-03-28 Thread Sean Feole
** Description changed:

  Description: During SRU Testing of various Azure Instances, there will
  be some cases where the instance will not respond following a system
  reboot.  SRU Testing only restarts a giving instance once, after it
  preps all of the necessary files to-be-tested.
  
  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  
  I initiated a series of tests which rebooted Azure Cloud instances 50
  times. During the 49th Reboot, an Instance failed to return from a
  reboot.. Upon grabbing the console output the following was seen
  scrolling endlessly. I have seen this failure in cases where the
  instance only restarted a handful of times >5
  
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
+ 
+ In another test attempt I saw the following failure:
+ 
+ ERROR ExtHandler /proc/net/route contains no routes
+ ERROR ExtHandler /proc/net/route contains no routes
+ ERROR ExtHandler /proc/net/route contains no routes
+ ERROR ExtHandler /proc/net/route contains no routes
+ ERROR ExtHandler /proc/net/route contains no routes
+ ERROR ExtHandler /proc/net/route contains no routes
+ ERROR ExtHandler /proc/net/route contains no routes
+ 
+ 
+ Both of these failures broke networking, Both of these failures were seen at 
least twice to three times, thus may explain why in some cases we never recover 
from an instance reboot.

-- 
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/1822133

Title:
  Azure Instance never recovered during series of instance reboots.

Status in linux-azure package in Ubuntu:
  New

Bug description:
  Description: During SRU Testing of various Azure Instances, there will
  be some cases where the instance will not respond following a system
  reboot.  SRU Testing only restarts a giving instance once, after it
  preps all of the necessary files to-be-tested.

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I initiated a series of tests which rebooted Azure Cloud instances 50
  times. During the 49th Reboot, an Instance failed to return from a
  reboot.. Upon grabbing the console output the following was seen
  scrolling endlessly. I have seen this failure in cases where the
  instance only restarted a handful of times >5

  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus

  In another test attempt I saw the following failure:

  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes

  
  Both of these failures broke networking, Both of these failures were seen at 
least twice to three times, thus may explain why in some cases we never recover 
from an instance reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1819617] Re: linux-azure: 4.18.0-1014.14~18.04.1 -proposed tracker

2019-03-28 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1819617

Title:
  linux-azure: 4.18.0-1014.14~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  derivatives: bug 1819616 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819618
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 19:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819617/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


  1   2   3   >