[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change

2019-06-26 Thread Po-Hsu Lin
>From my point of view,
I think we should leave the test case as-is, it helped us to identify this 
firmware issue. And it might be able to catch another FW issues on other 
platforms in the future.

For this specific HW, we can make a note for the test result by using this bug 
report.
Thanks.

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

Title:
  hwclock test failed on Power9 due to 0.x sec differences / time out
  waiting for time change

Status in ubuntu-kernel-tests:
  New
Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  The hwclock test will fail on the Power9 system "baltar" due to a
  <0.02 second difference.

  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/hwclock/hwclock.py", line 50, in 
run_once
  raise error.TestFail("Failed to set hwclock back to Warthog's birthday. 
Output of hwclock is '%s'" % date)
  TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock 
is '2004-10-20 04:09:59.582146+'

  Didn't see this on Power8 boxes

  Sometimes it will fail because "time out waiting for time change" on the same 
node:
  $ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
  hwclock: Timed out waiting for time change.

  Workaround for these is to add "sleep 1".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 03:45 seq
   crw-rw 1 root audio 116, 33 Nov  8 03:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: ppc64el
  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:
  CurrentDmesg:

  Date: Thu Nov  8 06:03:54 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3544 00:17:582 0 EOF
   2: POSIX  ADVISORY  WRITE 1798 00:17:338 0 EOF
   3: POSIX  ADVISORY  WRITE 3603 00:17:576 0 EOF
   4: FLOCK  ADVISORY  WRITE 3535 00:17:564 0 EOF
   5: FLOCK  ADVISORY  WRITE 4081 00:17:481 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC 
2018
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 40
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 159)
   max: 2.862 GHz (cpu 1)
   avg: 2.862 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

  -- Firmware information on Baltar --
  pnor: P9DSU20190404_IBM_prod_sign.pnor
  bmc: SMT_P9_206.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+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 1827335] Re: Unable to put offline CPU back online on Bionic/B-hwe-edge P9

2019-06-26 Thread Po-Hsu Lin
Hello,

so does it means we have something inside this box that needs to be
replaced?

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

Title:
  Unable to put offline CPU back online on Bionic/B-hwe-edge P9

Status in The Ubuntu-power-systems project:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  You will see these CPUs in offline state after boot.

  ubuntu@baltar:~$ cat /sys/devices/system/cpu/offline
  156-159

  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu156/online
  1
  tee: /sys/devices/system/cpu/cpu156/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu157/online
  1
  tee: /sys/devices/system/cpu/cpu157/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu158/online
  1
  tee: /sys/devices/system/cpu/cpu158/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu159/online
  1
  tee: /sys/devices/system/cpu/cpu159/online: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-14-generic 5.0.0-14.15~18.04.1+signed1
  ProcVersionSignature: Ubuntu 5.0.0-14.15~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-14-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: ppc64el
  Date: Thu May  2 06:46:36 2019
  ProcLoadAvg: 0.00 0.00 0.00 1/1298 6496
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 5.0.0-14-generic (buildd@bos02-ppc64el-014) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #15~18.04.1-Ubuntu SMP Thu Apr 25 
18:55:27 UTC 2019
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 81)
   avg: 2.903 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827335/+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 1834310] Re: Handle overflow for file-max

2019-06-26 Thread Po-Hsu Lin
** Description changed:

  == SRU Justification ==
  Currently, when writing
-echo 18446744073709551616 > /proc/sys/fs/file-max
+    echo 18446744073709551616 > /proc/sys/fs/file-max
  
  /proc/sys/fs/file-max will overflow and be set to 0.
  
  The upper and lower limit need to be defined properly to avoid this
  issue.
+ 
+ This failure was reported by the case 2 and 3 of the sysctl02 test in LTP:
+ sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 
18446744073709551615
+ sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 
9223372036854775808
  
  == Fix ==
  * 32a5ad9c sysctl: handle overflow for file-max
  * 9002b214 kernel/sysctl.c: fix out-of-bounds access when setting file-max
  
  These patches can be cherry-picked into B/C.
  They have already been applied in X/D from stable update process.
  
  == Test ==
  This issue can be verified with the sysctl02 test in LTP.
  
  == Regression Potential ==
- Low
- 
+ Low, just adding boundaries to the file-max.
+ And it's been applied in some of our kernel for a while.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-52-generic 4.15.0-52.56
  ProcVersionSignature: User Name 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 25 11:03 seq
   crw-rw 1 root audio 116, 33 Jun 25 11:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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: Tue Jun 25 11:04:55 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.15.0-52-generic 
root=UUID=6f08d1c2-d443-47ee-97ca-2aeb1bf53f35 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-52-generic N/A
   linux-backports-modules-4.15.0-52-generic  N/A
   linux-firmware 1.173.6
  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

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

Title:
  Handle overflow for file-max

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  == SRU Justification ==
  Currently, when writing
     echo 18446744073709551616 > /proc/sys/fs/file-max

  /proc/sys/fs/file-max will overflow and be set to 0.

  The upper and lower limit need to be defined properly to avoid this
  issue.

  This failure was reported by the case 2 and 3 of the sysctl02 test in LTP:
  sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 
18446744073709551615
  sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 
9223372036854775808

  == Fix ==
  * 32a5ad9c sysctl: handle overflow for file-max
  * 9002b214 kernel/sysctl.c: fix out-of-bounds access when setting file-max

  These patches can be cherry-picked into B/C.
  They have already been applied in X/D from stable update process.

  == Test ==
  This issue can be verified with the sysctl02 test in LTP.

  == Regression Potential ==
  Low, just adding boundaries to the file-max.
  And it's been applied in some of our kernel for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-52-generic 4.15.0-52.56
  ProcVersionSignature: User Name 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 25 11:03 seq
   crw-rw 1 root audio 116, 33 Jun 25 11:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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: Tue Jun 25 11:04:55 2019
  IwConfig: Error: [Errno 

[Kernel-packages] [Bug 1834310] Re: Handle overflow for file-max

2019-06-26 Thread Po-Hsu Lin
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Description changed:

+ == SRU Justification ==
  Currently, when writing
- 
-   echo 18446744073709551616 > /proc/sys/fs/file-max
- 
+echo 18446744073709551616 > /proc/sys/fs/file-max
+ 
  /proc/sys/fs/file-max will overflow and be set to 0.
- That quickly crashes the system.
  
- This issue can be reproduced with the sysctl02 test in LTP.
+ The upper and lower limit need to be defined properly to avoid this
+ issue.
+ 
+ == Fix ==
+ * 32a5ad9c sysctl: handle overflow for file-max
+ * 9002b214 kernel/sysctl.c: fix out-of-bounds access when setting file-max
+ 
+ These patches can be cherry-picked into B/C.
+ They have already been applied in X/D from stable update process.
+ 
+ == Test ==
+ This issue can be verified with the sysctl02 test in LTP.
+ 
+ == Regression Potential ==
+ Low
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-52-generic 4.15.0-52.56
  ProcVersionSignature: User Name 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Jun 25 11:03 seq
-  crw-rw 1 root audio 116, 33 Jun 25 11:03 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Jun 25 11:03 seq
+  crw-rw 1 root audio 116, 33 Jun 25 11:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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: Tue Jun 25 11:04:55 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.15.0-52-generic 
root=UUID=6f08d1c2-d443-47ee-97ca-2aeb1bf53f35 ro
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-52-generic N/A
-  linux-backports-modules-4.15.0-52-generic  N/A
-  linux-firmware 1.173.6
+  linux-restricted-modules-4.15.0-52-generic N/A
+  linux-backports-modules-4.15.0-52-generic  N/A
+  linux-firmware 1.173.6
  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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => In Progress

** Tags added: 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/1834310

Title:
  Handle overflow for file-max

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  == SRU Justification ==
  Currently, when writing
 echo 18446744073709551616 > /proc/sys/fs/file-max

  /proc/sys/fs/file-max will overflow and be set to 0.

  The upper and lower limit need to be defined properly to avoid this
  issue.

  == Fix ==
  * 32a5ad9c sysctl: handle overflow for file-max
  * 9002b214 kernel/sysctl.c: fix out-of-bounds access when setting file-max

  These patches can be cherry-picked into B/C.
  They have already been applied in X/D from stable update process.

  == Test ==
  This issue can be verified with the sysctl02 test in LTP.

  == Regression Potential ==
  Low

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-52-generic 4.15.0-52.56
  ProcVersionSignature: User Name 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 25 11:03 seq
   crw-rw 1 root audio 116, 33 Jun 25 11:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Arecord

[Kernel-packages] [Bug 1833935] Re: sysctl02_sh from ubuntu_ltp failed with Cosmic kernel

2019-06-26 Thread Po-Hsu Lin
** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

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

Title:
  sysctl02_sh from ubuntu_ltp failed with Cosmic kernel

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-kvm source package in Cosmic:
  New

Bug description:
  Test complains about apparmor enabled.
  As it's enabled by default, I think we might need to disable this test.

  Furthermore, this test will need kallsyms to be enabled, which is not
  for KVM kernels.

  <<>>
  tag=sysctl02_sh stime=1561360893
  cmdline="sysctl02.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  sysctl02 1 TINFO: timeout per run is 0h 5m 0s
  sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0
  sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 
18446744073709551615
  sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 
9223372036854775808
  sysctl02 4 TCONF: /proc/kallsyms not enabled
  sysctl02 4 TINFO: AppArmor enabled, this may affect test results
  sysctl02 4 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
  sysctl02 4 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   0
  failed   3
  skipped  1
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=33 corefile=no
  cutime=2 cstime=1
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
  ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
  Uname: Linux 4.18.0-1015-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Mon Jun 24 07:21:41 2019
  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/1833935/+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 1834310] [NEW] Handle overflow for file-max

2019-06-26 Thread Po-Hsu Lin
Public bug reported:

Currently, when writing

  echo 18446744073709551616 > /proc/sys/fs/file-max

/proc/sys/fs/file-max will overflow and be set to 0.
That quickly crashes the system.

This issue can be reproduced with the sysctl02 test in LTP.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-52-generic 4.15.0-52.56
ProcVersionSignature: User Name 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jun 25 11:03 seq
 crw-rw 1 root audio 116, 33 Jun 25 11:03 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
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: Tue Jun 25 11:04:55 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.15.0-52-generic 
root=UUID=6f08d1c2-d443-47ee-97ca-2aeb1bf53f35 ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-52-generic N/A
 linux-backports-modules-4.15.0-52-generic  N/A
 linux-firmware 1.173.6
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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Cosmic)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

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

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

Title:
  Handle overflow for file-max

Status in linux package in Ubuntu:
  New
Status in linux source package in Cosmic:
  New

Bug description:
  Currently, when writing
  
echo 18446744073709551616 > /proc/sys/fs/file-max
  
  /proc/sys/fs/file-max will overflow and be set to 0.
  That quickly crashes the system.

  This issue can be reproduced with the sysctl02 test in LTP.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-52-generic 4.15.0-52.56
  ProcVersionSignature: User Name 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 25 11:03 seq
   crw-rw 1 root audio 116, 33 Jun 25 11:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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: Tue Jun 25 11:04:55 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.15.0-52-generic 
root=UUID=6f08d1c2-d443-47ee-97ca-2aeb1bf53f35 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-52-generic N/A
   linux-backports-modules-4.15.0-52-generic  N/A
   linux-firmware 1.173.6
  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/+source/linux/+bug/1834310/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1830362] Re: runpwtests03 from power_management_tests test suite in LTP failed

2019-06-26 Thread Po-Hsu Lin
Another patch to address the modprobe -l issue:
http://lists.linux.it/pipermail/ltp/2019-June/012555.html

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  runpwtests03 from power_management_tests test suite in LTP failed

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Issue found on Disco with node glameow:
   startup='Fri May 24 10:57:20 2019'
   /opt/ltp/testcases/bin/runpwtests03.sh: 29: 
/opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found
   find: ‘/sys/devices/system/cpu/cpu40/cpufreq/’: No such file or directory
   /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Checking cpu freq sysfs files
   Power_Management03 1 TPASS: CPUFREQ sysfs tests
   /opt/ltp/testcases/bin/runpwtests03.sh: 55: 
/opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found
   /opt/ltp/testcases/bin/runpwtests03.sh: 62: 
/opt/ltp/testcases/bin/runpwtests03.sh: cannot create 
/sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent
   /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- 
performance for cpu40
   /opt/ltp/testcases/bin/runpwtests03.sh: 62: 
/opt/ltp/testcases/bin/runpwtests03.sh: cannot create 
/sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent
   /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- 
powersave for cpu40
   Power_Management03 2 TFAIL: Changing governors
   cat: '/sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies': 
No such file or directory
   /opt/ltp/testcases/bin/runpwtests03.sh: 83: 
/opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found
   /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Changing cpu frequencies
   Power_Management03 3 TPASS: Changing frequncies
   modprobe: invalid option -- 'l'
   modprobe: invalid option -- 'l'
   Power_Management03 4 TPASS: Loading and Unloading of governor kernel modules
   tag=runpwtests03 stime=1558695440 dur=2 exit=exited stat=1 core=no cu=28 cs=7

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 07:49 seq
   crw-rw 1 root audio 116, 33 May 21 07:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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:
  CurrentDmesg:
   
  Date: Fri May 24 11:07:37 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  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/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830362/+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 1830362] Re: runpwtests03 from power_management_tests test suite in LTP failed

2019-06-25 Thread Po-Hsu Lin
Error caused by the cpu number calculation
http://lists.linux.it/pipermail/ltp/2019-June/012547.html

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

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

Title:
  runpwtests03 from power_management_tests test suite in LTP failed

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on Disco with node glameow:
   startup='Fri May 24 10:57:20 2019'
   /opt/ltp/testcases/bin/runpwtests03.sh: 29: 
/opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found
   find: ‘/sys/devices/system/cpu/cpu40/cpufreq/’: No such file or directory
   /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Checking cpu freq sysfs files
   Power_Management03 1 TPASS: CPUFREQ sysfs tests
   /opt/ltp/testcases/bin/runpwtests03.sh: 55: 
/opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found
   /opt/ltp/testcases/bin/runpwtests03.sh: 62: 
/opt/ltp/testcases/bin/runpwtests03.sh: cannot create 
/sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent
   /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- 
performance for cpu40
   /opt/ltp/testcases/bin/runpwtests03.sh: 62: 
/opt/ltp/testcases/bin/runpwtests03.sh: cannot create 
/sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent
   /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- 
powersave for cpu40
   Power_Management03 2 TFAIL: Changing governors
   cat: '/sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies': 
No such file or directory
   /opt/ltp/testcases/bin/runpwtests03.sh: 83: 
/opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found
   /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Changing cpu frequencies
   Power_Management03 3 TPASS: Changing frequncies
   modprobe: invalid option -- 'l'
   modprobe: invalid option -- 'l'
   Power_Management03 4 TPASS: Loading and Unloading of governor kernel modules
   tag=runpwtests03 stime=1558695440 dur=2 exit=exited stat=1 core=no cu=28 cs=7

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 07:49 seq
   crw-rw 1 root audio 116, 33 May 21 07:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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:
  CurrentDmesg:
   
  Date: Fri May 24 11:07:37 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  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/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830362/+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 1833935] Re: sysctl02_sh from ubuntu_ltp failed on KVM kernels because AppArmor enabled

2019-06-25 Thread Po-Hsu Lin
Built a Cosmic generic kernel with AppArmor disabled, failures still can be 
seen in the test report:
$  grep -i apparmor /boot/config-4.18.0-25-generic 
# CONFIG_SECURITY_APPARMOR is not set
$ uname -a
Linux amaura 4.18.0-25-generic #26 SMP Tue Jun 25 07:49:54 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

<<>>
incrementing stop
sysctl02 1 TINFO: timeout per run is 0h 5m 0s
sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0
sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 
18446744073709551615
sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 9223372036854775808
sysctl02 4 TCONF: kernel doesn't support KASAN

Summary:
passed   0
failed   3
skipped  1
warnings 0

And the commits mentioned in this test case does not exist in our
kernel, so this is a valid kernel issue.

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

** Summary changed:

- sysctl02_sh from ubuntu_ltp failed on KVM kernels because AppArmor enabled
+ sysctl02_sh from ubuntu_ltp failed

** Summary changed:

- sysctl02_sh from ubuntu_ltp failed
+ sysctl02_sh from ubuntu_ltp failed with Cosmic kernel

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

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

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

Title:
  sysctl02_sh from ubuntu_ltp failed with Cosmic kernel

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

Bug description:
  Test complains about apparmor enabled.
  As it's enabled by default, I think we might need to disable this test.

  Furthermore, this test will need kallsyms to be enabled, which is not
  for KVM kernels.

  <<>>
  tag=sysctl02_sh stime=1561360893
  cmdline="sysctl02.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  sysctl02 1 TINFO: timeout per run is 0h 5m 0s
  sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0
  sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 
18446744073709551615
  sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 
9223372036854775808
  sysctl02 4 TCONF: /proc/kallsyms not enabled
  sysctl02 4 TINFO: AppArmor enabled, this may affect test results
  sysctl02 4 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
  sysctl02 4 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   0
  failed   3
  skipped  1
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=33 corefile=no
  cutime=2 cstime=1
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
  ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
  Uname: Linux 4.18.0-1015-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Mon Jun 24 07:21:41 2019
  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/1833935/+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 1830362] Re: runpwtests03 from power_management_tests test suite in LTP failed

2019-06-25 Thread Po-Hsu Lin
** Tags added: cosmic sru-20190603 ubuntu-ltp

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

Title:
  runpwtests03 from power_management_tests test suite in LTP failed

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

Bug description:
  Issue found on Disco with node glameow:
   startup='Fri May 24 10:57:20 2019'
   /opt/ltp/testcases/bin/runpwtests03.sh: 29: 
/opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found
   find: ‘/sys/devices/system/cpu/cpu40/cpufreq/’: No such file or directory
   /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Checking cpu freq sysfs files
   Power_Management03 1 TPASS: CPUFREQ sysfs tests
   /opt/ltp/testcases/bin/runpwtests03.sh: 55: 
/opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found
   /opt/ltp/testcases/bin/runpwtests03.sh: 62: 
/opt/ltp/testcases/bin/runpwtests03.sh: cannot create 
/sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent
   /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- 
performance for cpu40
   /opt/ltp/testcases/bin/runpwtests03.sh: 62: 
/opt/ltp/testcases/bin/runpwtests03.sh: cannot create 
/sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent
   /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- 
powersave for cpu40
   Power_Management03 2 TFAIL: Changing governors
   cat: '/sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies': 
No such file or directory
   /opt/ltp/testcases/bin/runpwtests03.sh: 83: 
/opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found
   /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Changing cpu frequencies
   Power_Management03 3 TPASS: Changing frequncies
   modprobe: invalid option -- 'l'
   modprobe: invalid option -- 'l'
   Power_Management03 4 TPASS: Loading and Unloading of governor kernel modules
   tag=runpwtests03 stime=1558695440 dur=2 exit=exited stat=1 core=no cu=28 cs=7

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 07:49 seq
   crw-rw 1 root audio 116, 33 May 21 07:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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:
  CurrentDmesg:
   
  Date: Fri May 24 11:07:37 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  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/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830362/+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 1830584] Re: mkswap01_sh from commands test suite in LTP failed

2019-06-24 Thread Po-Hsu Lin
https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=ac3be5cac2786de3b2b15979ae482d88291afff9

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

Title:
  mkswap01_sh from commands test suite in LTP failed

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Test failed with file check timeout:
  mkswap01 8 TBROK: "check_for_file 
/dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out

  
  <<>>
  tag=mkswap01_sh stime=1558936352
  cmdline="mkswap01.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  mkswap01 1 TINFO: timeout per run is 0h 5m 0s
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop3'
  mkswap01 1 TPASS: 'mkswap   /dev/loop3 ' passed.
  mkswap01 2 TPASS: 'mkswap   /dev/loop3 262140' passed.
  mkswap01 3 TINFO: Can not do swapon on /dev/loop3.
  mkswap01 3 TINFO: Device size specified by 'mkswap' greater than real size.
  mkswap01 3 TINFO: Swapon failed expectedly.
  mkswap01 3 TPASS: 'mkswap -f  /dev/loop3 262148' passed.
  mkswap01 4 TPASS: 'mkswap -c  /dev/loop3 ' passed.
  mkswap01 5 TINFO: Can not do swapon on /dev/loop3.
  mkswap01 5 TINFO: Page size specified by 'mkswap -p' is not equal to system's 
page size.
  mkswap01 5 TINFO: Swapon failed expectedly.
  mkswap01 5 TPASS: 'mkswap -p 2048 /dev/loop3 ' passed.
  mkswap01 6 TPASS: 'mkswap -L ltp_testswap /dev/loop3 ' passed.
  mkswap01 7 TPASS: 'mkswap -v1  /dev/loop3 ' passed.
  mkswap01 8 TBROK: "check_for_file 
/dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out
  mkswap01 8 TINFO: AppArmor enabled, this may affect test results
  mkswap01 8 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
  mkswap01 8 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   7
  failed   0
  skipped  0
  warnings 0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 27 05:39 seq
   crw-rw 1 root audio 116, 33 May 27 05:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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: Mon May 27 05:53:16 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  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/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830584/+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 1830584] Re: mkswap01_sh from commands test suite in LTP failed

2019-06-24 Thread Po-Hsu Lin
** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

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

Title:
  mkswap01_sh from commands test suite in LTP failed

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Test failed with file check timeout:
  mkswap01 8 TBROK: "check_for_file 
/dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out

  
  <<>>
  tag=mkswap01_sh stime=1558936352
  cmdline="mkswap01.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  mkswap01 1 TINFO: timeout per run is 0h 5m 0s
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop3'
  mkswap01 1 TPASS: 'mkswap   /dev/loop3 ' passed.
  mkswap01 2 TPASS: 'mkswap   /dev/loop3 262140' passed.
  mkswap01 3 TINFO: Can not do swapon on /dev/loop3.
  mkswap01 3 TINFO: Device size specified by 'mkswap' greater than real size.
  mkswap01 3 TINFO: Swapon failed expectedly.
  mkswap01 3 TPASS: 'mkswap -f  /dev/loop3 262148' passed.
  mkswap01 4 TPASS: 'mkswap -c  /dev/loop3 ' passed.
  mkswap01 5 TINFO: Can not do swapon on /dev/loop3.
  mkswap01 5 TINFO: Page size specified by 'mkswap -p' is not equal to system's 
page size.
  mkswap01 5 TINFO: Swapon failed expectedly.
  mkswap01 5 TPASS: 'mkswap -p 2048 /dev/loop3 ' passed.
  mkswap01 6 TPASS: 'mkswap -L ltp_testswap /dev/loop3 ' passed.
  mkswap01 7 TPASS: 'mkswap -v1  /dev/loop3 ' passed.
  mkswap01 8 TBROK: "check_for_file 
/dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out
  mkswap01 8 TINFO: AppArmor enabled, this may affect test results
  mkswap01 8 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
  mkswap01 8 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   7
  failed   0
  skipped  0
  warnings 0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 27 05:39 seq
   crw-rw 1 root audio 116, 33 May 27 05:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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: Mon May 27 05:53:16 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  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/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830584/+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 1834006] [NEW] cpuset_hotplug from controllers in ubuntu_ltp failed on Cosmic

2019-06-24 Thread Po-Hsu Lin
Public bug reported:

Issue found on node amaura:
<<>>
tag=cpuset_hotplug stime=1561372131
cmdline="cpuset_hotplug_test.sh"
contacts=""
analysis=exit
<<>>
incrementing stop
cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded.
cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, 
Expect: 0-7).
cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded.
cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded.
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=19 cstime=81
<<>>

Test script:
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-22-generic 4.18.0-22.23
ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20
Uname: Linux 4.18.0-22-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jun 24 10:25 seq
 crw-rw 1 root audio 116, 33 Jun 24 10:25 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: Mon Jun 24 10:30:59 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Intel Corporation S1200RP
PciMultimedia:
 
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-22-generic N/A
 linux-backports-modules-4.18.0-22-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: 07/01/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
dmi.board.asset.tag: 
dmi.board.name: S1200RP
dmi.board.vendor: Intel Corporation
dmi.board.version: G62254-407
dmi.chassis.asset.tag: 
dmi.chassis.type: 17
dmi.chassis.vendor: ..
dmi.chassis.version: ..
dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: S1200RP
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 
dmi.sys.vendor: Intel Corporation

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug cosmic sru-20190603 ubuntu-ltp uec-images

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: sru-20190603 ubuntu-ltp

** Summary changed:

- cpuset_hotplug from ubuntu_ltp failed on Cosmic
+ cpuset_hotplug from controllers in ubuntu_ltp failed 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/1834006

Title:
  cpuset_hotplug from controllers in ubuntu_ltp failed on Cosmic

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

Bug description:
  Issue found on node amaura:
  <<>>
  tag=cpuset_hotplug stime=1561372131
  cmdline="cpuset_hotplug_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, 
Expect: 0-7).
  cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded.
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=1 corefile=no
  cutime=19 cstime=81
  <<>>

  Test script:
  
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-22-generic 4.18.0-22.23
  ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 

[Kernel-packages] [Bug 1812988] Re: ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes generate kernel traces on Cosmic

2019-06-24 Thread Po-Hsu Lin
For Cosmic generic kernel, it has passed on amd64 node amaura, but
failed with amd64 node gonzo.

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

Title:
  ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes
  generate kernel traces on Cosmic

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

Bug description:
  This issue can only be reproduced on certain HW, node "daedalus"
  (AMD64), "modoc" P8

  And this can only be reproduced when running the whole test suite, it
  will be fine if you just run this test:

Invoking test ff76b0565523319d7c1c0b51d5a5a8915d33efab

fix ff76b0565523319d7c1c0b51d5a5a8915d33efab

Btrfs: Don't allocate inode that is already in use

Due to an off-by-one error, it is possible to reproduce a bug
when the inode cache is used.

The same inode number is assigned twice, the second time this
leads to an EEXIST in btrfs_insert_empty_items().

Create subvolume '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s3'

Found kernel issue:

[ 2713.591492] WARNING: CPU: 18 PID: 61234 at fs/btrfs/inode.c:9256 
btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591494] Modules linked in: btrfs zstd_compress nls_iso8859_1 
ipmi_ssif intel_rapl skx_edac nfit x86_pkg_temp_thermal intel_powerclamp joydev 
input_leds coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel intel_cstate intel_rapl_perf mei_me mei ioatdma ipmi_si dca 
ipmi_devintf ipmi_msghandler acpi_pad acpi_power_meter mac_hid sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ast i2c_algo_bit ttm hid_generic 
drm_kms_helper aesni_intel aes_x86_64 syscopyarea usbhid sysfillrect 
crypto_simd hid sysimgblt cryptd fb_sys_fops ahci glue_helper i40e drm lpc_ich 
libahci wmi [last unloaded: zstd_compress]
[ 2713.591577] CPU: 18 PID: 61234 Comm: umount Tainted: GW 
4.18.0-14-generic #15-Ubuntu
[ 2713.591579] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.01.00.0412.020920172159 02/09/2017
[ 2713.591611] RIP: 0010:btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591612] Code: d0 31 d2 48 89 83 e0 fe ff ff 49 8b 85 e0 03 00 00 48 
85 c0 0f 94 c2 e9 4c ff ff ff 0f 0b e9 60 fe ff ff 0f 0b e9 67 fe ff ff <0f> 0b 
e9 6e fe ff ff 0f 0b e9 75 fe ff ff 0f 0b e9 7c fe ff ff 0f 
[ 2713.591666] RSP: 0018:a966b0bbfc48 EFLAGS: 00010206
[ 2713.591669] RAX: 90c5bf3e6800 RBX: 90c5e06bbc30 RCX: 

[ 2713.591671] RDX:  RSI:  RDI: 
90c5e06bbc30
[ 2713.591673] RBP: a966b0bbfc78 R08: 0001 R09: 
c08fe101
[ 2713.591674] R10: 90c58aac2510 R11: 0001 R12: 
90c5e06bbcb8
[ 2713.591676] R13: c0972940 R14: 90c5e06bbd88 R15: 
a966b0bbfd48
[ 2713.591679] FS:  7f31837e8080() GS:90c61fa8() 
knlGS:
[ 2713.591681] CS:  0010 DS:  ES:  CR0: 80050033
[ 2713.591682] CR2: 7f3183b70308 CR3: 00080167a002 CR4: 
007606e0
[ 2713.591685] DR0:  DR1:  DR2: 

[ 2713.591686] DR3:  DR6: fffe0ff0 DR7: 
0400
[ 2713.591688] PKRU: 5554
[ 2713.591689] Call Trace:
[ 2713.591702]  destroy_inode+0x3e/0x60
[ 2713.591707]  evict+0x139/0x1a0
[ 2713.591711]  iput+0x148/0x210
[ 2713.591739]  free_fs_root+0x1b/0xc0 [btrfs]
[ 2713.591766]  btrfs_drop_and_free_fs_root+0x7c/0xf0 [btrfs]
[ 2713.591793]  btrfs_free_fs_roots+0xdc/0x170 [btrfs]
[ 2713.591824]  ? __btrfs_sysfs_remove_fsid+0x68/0x70 [btrfs]
[ 2713.591852]  close_ctree+0x10c/0x2d0 [btrfs]
[ 2713.591872]  btrfs_put_super+0x15/0x20 [btrfs]
[ 2713.591878]  generic_shutdown_super+0x72/0x110
[ 2713.591882]  kill_anon_super+0x12/0x20
[ 2713.591904]  btrfs_kill_super+0x18/0x110 [btrfs]
[ 2713.591906]  deactivate_locked_super+0x3a/0x80
[ 2713.591907]  deactivate_super+0x51/0x60
[ 2713.591909]  cleanup_mnt+0x3f/0x70
[ 2713.591910]  __cleanup_mnt+0x12/0x20
[ 2713.591915]  task_work_run+0x9d/0xc0
[ 2713.591920]  

[Kernel-packages] [Bug 1784535] Re: ubuntu_quota_smoke_test failed with KVM kernel

2019-06-24 Thread Po-Hsu Lin
** Tags added: cosmic ubuntu-quota-smoke-test

** Tags added: linux-kvm

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

Title:
  ubuntu_quota_smoke_test failed with KVM kernel

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

Bug description:
  According to Kamal's comment:
  CONFIG_QUOTA (and various other quota-related-looking configs) appear to 
be enabled already in the linux-kvm kernels -- but the required modules just 
end up in the regular linux-modules package (e.g. linux-modules-x.y.z-a.b-kvm)

  
  However even with the linux-modules-x.y.z-a.b-kvm package installed, this 
test will still fail with KVM kernel.

  $ sudo
  
/home/ubuntu/autotest/client/tests/ubuntu_quota_smoke_test/ubuntu_quota_smoke_test.sh

  Using block device /dev/loop0 for path /home/ubuntu/mnt
  PASSED (quotacheck -vucmg)

  quotaon: using /home/ubuntu/mnt/aquota.group on /dev/loop0 
[/home/ubuntu/mnt]: No such process
  quotaon: Quota format not supported in kernel.
  quotaon: using /home/ubuntu/mnt/aquota.user on /dev/loop0 [/home/ubuntu/mnt]: 
No such process
  quotaon: Quota format not supported in kernel.
  FAILED (quotaon -v)

  Summary: 1 passed, 1 failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1016-kvm 4.15.0-1016.16
  ProcVersionSignature: User Name 4.15.0-1016.16-kvm 4.15.18
  Uname: Linux 4.15.0-1016-kvm x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 31 03:59:45 2018
  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/1784535/+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 1766565] Re: Unable to insert sysdig_probe module on KVM kernel

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm ubuntu-sysdig-smoke-test

** Tags added: sru-20190603

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

Title:
  Unable to insert sysdig_probe module on KVM kernel

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

Bug description:
  The sysdig-dkms module cannot be installed on the B-KVM kernel once
  before (bug 1764693), but now the installation works since 4.15.0-1007

  However, when you try to insert the module, it will complain about:
  $ sudo modprobe sysdig-probe
  modprobe: ERROR: could not insert 'sysdig_probe': Unknown symbol in module, 
or unknown parameter (see dmesg)

  Log in dmesg:
  [ 1989.967807] sysdig_probe: loading out-of-tree module taints kernel.
  [ 1989.967924] sysdig_probe: module verification failed: signature and/or 
required key missing - tainting kernel
  [ 1989.967986] sysdig_probe: Unknown symbol tracepoint_probe_unregister (err 
0)
  [ 1989.968090] sysdig_probe: Unknown symbol for_each_kernel_tracepoint (err 0)
  [ 1989.968094] sysdig_probe: Unknown symbol tracepoint_probe_register (err 0)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1007-kvm 4.15.0-1007.7
  ProcVersionSignature: User Name 4.15.0-1007.7-kvm 4.15.17
  Uname: Linux 4.15.0-1007-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 11:31:08 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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/1766565/+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 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on KVM / Cosmic kernels

2019-06-24 Thread Po-Hsu Lin
This is still valid for KVM kernels. Re-open the bug.

$ sudo ./test_bpf.sh 
test_bpf: [FAIL]
sudo /sbin/modprobe test_bpf
modprobe: FATAL: Module test_bpf not found in directory 
/lib/modules/4.18.0-1015-kvm


** Changed in: linux-kvm (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: linux-kvm (Ubuntu Bionic)
   Status: Invalid => Confirmed

** Changed in: linux-kvm (Ubuntu Xenial)
   Status: Invalid => Confirmed

** Changed in: linux-kvm (Ubuntu Cosmic)
   Status: Invalid => Confirmed

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

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

Title:
  test_bpf in net from ubuntu_kernel_selftests failed on KVM / Cosmic
  kernels

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This test will attempt to insert the test_bpf module, but this module
  does not exist in KVM kernels:

  $ sudo modprobe test_bpf
  modprobe: FATAL: Module test_bpf not found in directory 
/lib/modules/4.15.0-1028-kvm

  The script:
  $ sudo ./test_bpf.sh 
  test_bpf: [FAIL]

  $ cat test_bpf.sh 
  #!/bin/sh
  # SPDX-License-Identifier: GPL-2.0
  # Runs bpf test using test_bpf kernel module

  if /sbin/modprobe -q test_bpf ; then
/sbin/modprobe -q -r test_bpf;
echo "test_bpf: ok";
  else
echo "test_bpf: [FAIL]";
exit 1;
  fi

  This test_bpf module will need the CONFIG_TEST_BPF to be enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 08:29:29 2019
  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/1812189/+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 1812159] Re: q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels

2019-06-24 Thread Po-Hsu Lin
** Tags added: ubuntu-qrt-kernel-security

** Tags added: linux-kvm

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

Title:
  q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM
  kernels

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Xenial:
  In Progress
Status in linux-kvm source package in Bionic:
  In Progress
Status in linux-kvm source package in Cosmic:
  In Progress
Status in linux-kvm source package in Disco:
  In Progress

Bug description:
  == SRU Justification ==
  Security team requires the SCHED_STACK_END_CHECK config to be enabled
  on all of our kernel.

  The test_380_config_sched_stack_end_check test from q-r-t will fail on
  all the KVM kernels.

  Copied from the config help text:
  This option checks for a stack overrun on calls to schedule(). If the
  stack end location is found to be over written always panic as the
  content of the corrupted region can no longer be trusted. This is to
  ensure no erroneous behaviour occurs which could result in data
  corruption or a sporadic crash at a later stage once the region is
  examined. The runtime overhead introduced is minimal.

  == Test ==
  Test kernels could be found here: 
  https://people.canonical.com/~phlin/kernel/lp-1812159-kvm-sched-check/
  This issue case be verified with the test_380_config_sched_stack_end_check 
test from q-r-t, the test will pass with the patched kernel.

  == Regression Potential ==
  Low, the introduced runtime overhead is minimal, and it's already enabled in 
the generic kernel.

  == Original Bug report ==
  The test_380_config_sched_stack_end_check test failed on the Bionic
  KVM kernel

   FAIL: test_380_config_sched_stack_end_check 
(__main__.KernelSecurityConfigTest)
   Ensure SCHED_STACK_END_CHECK is set
   --
   Traceback (most recent call last):
   File "./test-kernel-security.py", line 2628, in 
test_380_config_sched_stack_end_check
   self.assertKernelConfig('SCHED_STACK_END_CHECK', expected)
   File "./test-kernel-security.py", line 207, in assertKernelConfig
   self.assertKernelConfigSet(name)
   File "./test-kernel-security.py", line 194, in assertKernelConfigSet
   '%s option was expected to be set in the kernel config' % name)
   AssertionError: SCHED_STACK_END_CHECK option was expected to be set in the 
kernel config

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 06:44:41 2019
  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/1812159/+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 1824794] Re: acct01 in ubuntu_ltp_syscalls reported as a failure with B-KVM

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm

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

Title:
  acct01 in ubuntu_ltp_syscalls reported as a failure with B-KVM

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

Bug description:
  This test was skipped in the ltp syscalls test, due to unmatched
  configs.

  However the ltp test suite will treat it as a failure, it's better to
  figure out how to skip this.

  <<>>
  tag=acct01 stime=1555326506
  cmdline="acct01"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  incrementing stop
  acct01.c:70: CONF: acct() system call isn't configured in kernel
  safe_macros.c:360: WARN: acct01.c:96: unlink(./tmpfile) failed: ENOENT
  safe_macros.c:360: WARN: acct01.c:97: unlink(test_file_eloop1) failed: ENOENT

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 2
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=36 corefile=no
  cutime=0 cstime=0
  <<>>
  INFO: ltp-pan reported some tests FAIL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1824794/+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 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603

** Tags added: 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/1829984

Title:
  memcg_usage_in_bytes from controllers test suite in LTP failed

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

Bug description:
   startup='Wed May 22 05:59:09 2019'
   memcg_usage_in_bytes_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689
   memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689
   memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 
expected
   memcg_usage_in_bytes_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled
   tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no 
cu=5 cs=3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 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.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  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/1829984/+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 1829989] Re: memcg_use_hierarchy from controllers test suite in LTP failed

2019-06-24 Thread Po-Hsu Lin
** Tags added: cosmic linux-kvm sru-20190603

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

Title:
  memcg_use_hierarchy from controllers test suite in LTP failed

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

Bug description:
  startup='Wed May 22 05:59:07 2019'
  memcg_use_hierarchy_test 1 TINFO: Starting test 1
  sh: echo: I/O error
  memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 1 TPASS: process 31577 is killed
  memcg_use_hierarchy_test 2 TINFO: Starting test 2
  sh: echo: I/O error
  memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 2 TFAIL: echo 1 > memory.use_hierarchy passed 
unexpectedly
  memcg_use_hierarchy_test 3 TINFO: Starting test 3
  sh: echo: I/O error
  memcg_use_hierarchy_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 3 TPASS: echo 0 > subgroup/memory.use_hierarchy 
failed as expected
  tag=memcg_use_hierarchy stime=1558504747 dur=1 exit=exited stat=1 core=no 
cu=5 cs=5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:33:33 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.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  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/1829989/+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 fails

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm ubuntu-ltp-syscalls

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

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-gke 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-gke 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
Status in linux source package in Eoan:
  Incomplete
Status in linux-aws source package in Eoan:
  New
Status in linux-azure source package in Eoan:
  New
Status in linux-gke source package in Eoan:
  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.
   

[Kernel-packages] [Bug 1830584] Re: mkswap01_sh from commands test suite in LTP failed

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-ltp

** Tags removed: ubunut-ltp

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

Title:
  mkswap01_sh from commands test suite in LTP failed

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

Bug description:
  Test failed with file check timeout:
  mkswap01 8 TBROK: "check_for_file 
/dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out

  
  <<>>
  tag=mkswap01_sh stime=1558936352
  cmdline="mkswap01.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  mkswap01 1 TINFO: timeout per run is 0h 5m 0s
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop3'
  mkswap01 1 TPASS: 'mkswap   /dev/loop3 ' passed.
  mkswap01 2 TPASS: 'mkswap   /dev/loop3 262140' passed.
  mkswap01 3 TINFO: Can not do swapon on /dev/loop3.
  mkswap01 3 TINFO: Device size specified by 'mkswap' greater than real size.
  mkswap01 3 TINFO: Swapon failed expectedly.
  mkswap01 3 TPASS: 'mkswap -f  /dev/loop3 262148' passed.
  mkswap01 4 TPASS: 'mkswap -c  /dev/loop3 ' passed.
  mkswap01 5 TINFO: Can not do swapon on /dev/loop3.
  mkswap01 5 TINFO: Page size specified by 'mkswap -p' is not equal to system's 
page size.
  mkswap01 5 TINFO: Swapon failed expectedly.
  mkswap01 5 TPASS: 'mkswap -p 2048 /dev/loop3 ' passed.
  mkswap01 6 TPASS: 'mkswap -L ltp_testswap /dev/loop3 ' passed.
  mkswap01 7 TPASS: 'mkswap -v1  /dev/loop3 ' passed.
  mkswap01 8 TBROK: "check_for_file 
/dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out
  mkswap01 8 TINFO: AppArmor enabled, this may affect test results
  mkswap01 8 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
  mkswap01 8 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   7
  failed   0
  skipped  0
  warnings 0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 27 05:39 seq
   crw-rw 1 root audio 116, 33 May 27 05:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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: Mon May 27 05:53:16 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  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/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830584/+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 1804594] Re: fanotify09 in LTP failed with first group got more than 2 events

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-ltp-syscalls

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

Title:
  fanotify09 in LTP failed with first group got more than 2 events

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Released

Bug description:
  There is a new test cases added into fanotify09:
  457e13c (fanotify09: check merging of events on child subdir)

   tag=fanotify09 stime=1542775332
   cmdline="fanotify09"
   contacts=""
   analysis=exit
   <<>>
   tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
   fanotify09.c:161: INFO: Test #0: Events on children with both inode and 
mount marks
   fanotify09.c:150: PASS: group 0 got event: mask 2 pid=19769 fd=23 
path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/tfile_19769
   fanotify09.c:234: PASS: group 1 got no event
   fanotify09.c:234: PASS: group 2 got no event
   fanotify09.c:161: INFO: Test #1: Events on children and subdirs with both 
inode and mount marks
   fanotify09.c:150: PASS: group 0 got event: mask 2 pid=19769 fd=23 
path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/tfile_19769
   fanotify09.c:150: PASS: group 0 got event: mask 10 pid=19769 fd=24 
path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/testdir
   fanotify09.c:202: FAIL: first group got more than 2 events (72 > 48)
   fanotify09.c:234: PASS: group 1 got no event
   fanotify09.c:234: PASS: group 2 got no event

   Summary:
   passed 7
   failed 1
   skipped 0
   warnings 0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 22 06:27 seq
   crw-rw 1 root audio 116, 33 Nov 22 06:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  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: Thu Nov 22 06:45:22 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R320
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=7e417b15-9c42-401c-b706-06eb693e6d19 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1804594/+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 1829971] Re: leapsec_timer from time test suite in LTP failed

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-ltp

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

Title:
  leapsec_timer from time test suite in LTP failed

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

Bug description:
  startup='Wed May 22 06:31:53 2019'
  leapsec_timer0  TINFO  :  test start at 2019-05-22 06:31:53.856622309 
+
  leapsec_timer0  TINFO  :  now is 2019-05-22 06:31:53.856669881 +
  leapsec_timer0  TINFO  :  sleep till 2019-05-22 06:31:54.856669881 +
  leapsec_timer0  TINFO  :  now is 2019-05-22 06:31:54.856816976 +
  leapsec_timer0  TINFO  :  hrtimer early expiration is not detected.
  leapsec_timer0  TINFO  :  scheduling leap second 2019-05-23 
00:00:00.0 +
  leapsec_timer0  TINFO  :  setting time to2019-05-22 
23:59:58.0 +
  leapsec_timer0  TINFO  :  2019-05-22 23:59:58.53707 + adjtimex: 
clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 23:59:58.000551000 + adjtimex: 
clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 23:59:58.000562000 + adjtimex: 
clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 23:59:58.000573000 + adjtimex: 
clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 06:31:55.357792794000 + 
adjtimex: clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 06:31:55.857973509000 + 
adjtimex: clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 06:31:56.358310277000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:56.858497565000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:57.358805606000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:57.858979489000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:58.359273808000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:58.859578599000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:59.35991891 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:59.860337395000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:00.360649484000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:00.860978405000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:01.361204884000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:01.861541113000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:02.361747253000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:02.862023631000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:03.362200035000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:03.862509446000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:04.362935772000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:04.863223244000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:05.36346277 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:05.863775778000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:06.364008145000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:06.864323759000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:07.364583789000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:07.864877576000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:08.365151603000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:08.865459198000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:09.365717696000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:09.866092913000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:10.366343699000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:10.866947893000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:11.367159166000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:11.86760044 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:12.367832925000 

[Kernel-packages] [Bug 1830675] Re: hackbench01 from sched test suite in LTP failed with KVM kernel

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm

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

Title:
  hackbench01 from sched test suite in LTP failed with KVM kernel

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

Bug description:
  Test failed with:
  fork() (error: Resource temporarily unavailable)

  <<>>
  tag=hackbench01 stime=1559023701
  cmdline="hackbench 50 process 1000"
  contacts=""
  analysis=exit
  <<>>
  Running with 50*40 (== 2000) tasks.
  fork() (error: Resource temporarily unavailable)
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=30
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1035-kvm 4.15.0-1035.35
  ProcVersionSignature: User Name 4.15.0-1035.35-kvm 4.15.18
  Uname: Linux 4.15.0-1035-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Tue May 28 06:10:47 2019
  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/1830675/+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 1797325] Re: quotactl01 / 02 / 03 in ubuntu_ltp_syscalls test failed with KVM kernel

2019-06-24 Thread Po-Hsu Lin
** Tags added: cosmic linux-kvm sru-20190603 ubuntu-ltp-syscalls

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

Title:
  quotactl01 / 02 / 03 in ubuntu_ltp_syscalls test failed with KVM
  kernel

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

Bug description:
  I think this issue has something to do with the quota related failure
  reported in bug 1784535

  For quotactl01:
   startup='Wed Nov 28 23:16:08 2018'
   tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop2'
   tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts=''
   mke2fs 1.44.4 (18-Aug-2018)
   tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
   quotactl01.c:195: FAIL: quotactl failed to turn on quota for user: ESRCH
   quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for user: 
ESRCH
   quotactl01.c:195: FAIL: quotactl failed to get disk quota limit for user: 
ESRCH
   quotactl01.c:195: FAIL: quotactl failed to set information about quotafile 
for user: ESRCH
   quotactl01.c:195: FAIL: quotactl failed to get information about quotafile 
for user: ESRCH
   quotactl01.c:195: FAIL: quotactl failed to get quota format for user: ESRCH
   quotactl01.c:206: PASS: quotactl succeeded to update quota usages for user
   quotactl01.c:206: PASS: quotactl succeeded to turn off quota for user
   quotactl01.c:195: FAIL: quotactl failed to turn on quota for group: ESRCH
   quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: 
ESRCH
   quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: 
ESRCH
   quotactl01.c:195: FAIL: quotactl failed to set information about quotafile 
for group: ESRCH
   quotactl01.c:195: FAIL: quotactl failed to get information about quotafile 
for group: ESRCH
   quotactl01.c:195: FAIL: quotactl failed to get quota format for group: ESRCH
   quotactl01.c:206: PASS: quotactl succeeded to update quota usages for group
   quotactl01.c:206: PASS: quotactl succeeded to turn off quota for group

   Summary:
   passed 4
   failed 12
   skipped 0
   warnings 0

  For quotactl02 / quotactl03, they both failed with xfs mounting:

   tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
   safe_macros.c:757: BROK: tst_test.c:759: mount(/dev/loop0, mnt_point, xfs, 
0, 0x40fbbd) failed: EINVAL

  <<>>
  tag=quotactl02 stime=1539242831
  cmdline="quotactl02"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
  tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
  safe_macros.c:757: BROK: tst_test.c:759: mount(/dev/loop0, mnt_point, xfs, 0, 
0x40fbbd) failed: EINVAL

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1036-kvm 4.4.0-1036.42
  ProcVersionSignature: User Name 4.4.0-1036.42-kvm 4.4.155
  Uname: Linux 4.4.0-1036-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Oct 11 07:27:17 2018
  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/1797325/+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-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603

-- 
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:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed

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 

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

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-kvm-unit-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 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on KVM / Cosmic kernels

2019-06-24 Thread Po-Hsu Lin
BTW fix in comment #5 is for generic kernel.

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

Title:
  test_bpf in net from ubuntu_kernel_selftests failed on KVM / Cosmic
  kernels

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This test will attempt to insert the test_bpf module, but this module
  does not exist in KVM kernels:

  $ sudo modprobe test_bpf
  modprobe: FATAL: Module test_bpf not found in directory 
/lib/modules/4.15.0-1028-kvm

  The script:
  $ sudo ./test_bpf.sh 
  test_bpf: [FAIL]

  $ cat test_bpf.sh 
  #!/bin/sh
  # SPDX-License-Identifier: GPL-2.0
  # Runs bpf test using test_bpf kernel module

  if /sbin/modprobe -q test_bpf ; then
/sbin/modprobe -q -r test_bpf;
echo "test_bpf: ok";
  else
echo "test_bpf: [FAIL]";
exit 1;
  fi

  This test_bpf module will need the CONFIG_TEST_BPF to be enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 08:29:29 2019
  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/1812189/+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 1748103] Re: apic test in kvm-unit-test failed on azure cloud with 4.13/4.14 kernel

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-kvm-unit-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/1748103

Title:
  apic test in kvm-unit-test failed on azure cloud with 4.13/4.14 kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure-edge source package in Xenial:
  New
Status in linux source package in Cosmic:
  New
Status in linux-azure source package in Cosmic:
  New
Status in linux-azure-edge source package in Cosmic:
  New

Bug description:
  With Joshua's comment in bug 1719524: "Nested KVM can only be tried on
  instance sizes with nested Hypervisor support: Ev3 and Dv3.", although
  the instance name is E4v3 here but I can start a KVM on it.

  Test apic will timeout on it.

  Steps:
  1. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests; ./configure; make
  3. Run the apic test as root:
   
  # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline
  timeout -k 1s --foreground 30 /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 # -initrd /tmp/tmp.onXtr5JVp7
  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
  FAIL: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  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
  PASS: nmi-after-sti
  qemu-system-x86_64: terminating on signal 15 from pid 7246

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4
  ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14
  Uname: Linux 4.14.0-1004-azure-edge x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 06:00:55 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: linux-azure-edge
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-1009-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev 
sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+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 1797348] Re: msgstress04 test in ubuntu_ltp_syscalls failed with X-KVM

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-ltp-syscalls

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

Title:
  msgstress04 test in ubuntu_ltp_syscalls failed with X-KVM

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Test failed with many "message queue mismatch" error message:
  Message queue mismatch in the reader of child group 75 for message queue 
id 545948306

  And

  <<>>
  tag=msgstress04 stime=1539249959
  cmdline="msgstress04"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  msgstress040  TINFO  :  Found 31997 available message queues
  msgstress040  TINFO  :  Using upto 1986 pids
  Message queue mismatch in the reader of child group 37 for message queue id 
524910642
  Message queue mismatch in the reader of child group 37 for message queue id 
524943411
  Message queue mismatch in the reader of child group 40 for message queue id 
525271101
  
  Child exit status = 1 from child group 37
  Message queue mismatch in the reader of child group 38 for message queue id 
526123096
  
  Child exit status = 1 from child group 39
  
  Child exit status = 1 from child group 42
  msgstress041  TFAIL  :  msgstress04.c:220: Child exit status = 1
  Message queue mismatch in the reader of child group 66 for message queue id 
543883860
  <<>>
  initiation_status="ok"
  duration=197 termination_type=exited termination_id=1 corefile=no
  cutime=575 cstime=1037
  <<>>

  
  Complete test log: https://pastebin.ubuntu.com/p/YtTXBh2tvP/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1036-kvm 4.4.0-1036.42
  ProcVersionSignature: User Name 4.4.0-1036.42-kvm 4.4.155
  Uname: Linux 4.4.0-1036-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Oct 11 09:33:08 2018
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1797348/+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 1830678] Re: netns_sysfs from containers test suite in LTP failed with KVM kernel

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-ltp

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

Title:
  netns_sysfs from containers test suite in LTP failed with KVM kernel

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

Bug description:
  <<>>
  tag=netns_sysfs stime=1559024934
  cmdline="netns_sysfs.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  RTNETLINK answers: Operation not supported
  netns_sysfs 1 TBROK: failed to add a new (host) dummy device
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=1 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1035-kvm 4.15.0-1035.35
  ProcVersionSignature: User Name 4.15.0-1035.35-kvm 4.15.18
  Uname: Linux 4.15.0-1035-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Tue May 28 06:22:51 2019
  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/1830678/+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 1829983] Re: memcg_stat from controllers test suite in LTP failed

2019-06-24 Thread Po-Hsu Lin
** Tags added: cosmic linux-kvm sru-20190603 ubuntu-ltp

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

Title:
  memcg_stat from controllers test suite in LTP failed

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

Bug description:
   memcg_stat_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168
   memcg_stat_test 1 TINFO: Warming up pid: 31352
   memcg_stat_test 1 TINFO: Process is still here after warm up: 31352
   memcg_stat_test 1 TPASS: cache is 135168 as expected
   memcg_stat_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168
   memcg_stat_test 2 TINFO: Warming up pid: 31380
   memcg_stat_test 2 TINFO: Process is still here after warm up: 31380
   memcg_stat_test 2 TPASS: mapped_file is 135168 as expected
   memcg_stat_test 3 TINFO: Starting test 3
   sh: echo: I/O error
   memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096
   memcg_stat_test 3 TINFO: Warming up pid: 31409
   memcg_stat_test 3 TINFO: Process is still here after warm up: 31409
   memcg_stat_test 3 TPASS: unevictable is 4096 as expected
   memcg_stat_test 4 TINFO: Starting test 4
   sh: echo: I/O error
   memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096
   memcg_stat_test 4 TINFO: Warming up pid: 31434
   memcg_stat_test 4 TINFO: Process is still here after warm up: 31434
   memcg_stat_test 4 TPASS: unevictable is 4096 as expected
   memcg_stat_test 5 TINFO: Starting test 5
   sh: echo: I/O error
   memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected
   memcg_stat_test 6 TINFO: Starting test 6
   sh: echo: I/O error
   memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   sh: echo: I/O error
   memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected
   memcg_stat_test 7 TINFO: Starting test 7
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   memcg_stat_test 7 TINFO: Starting test 8
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 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.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  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 + 

[Kernel-packages] [Bug 1748105] Re: port80 test in kvm-unit-test failed on E4v3 azure node with 4.13/4.14 kernel

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-kvm-unit-tests

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

Title:
  port80 test in kvm-unit-test failed on E4v3 azure node with 4.13/4.14
  kernel

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  With Joshua's comment in bug 1719524: "Nested KVM can only be tried on
  instance sizes with nested Hypervisor support: Ev3 and Dv3.", although
  the instance name is E4v3 here but I can start a KVM on it.

  Test port80 test will timeout on it.

  Steps:
  1. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests; ./configure; make
  3. Run the port80 test as root:

  # TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1
  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/port80.flat 
-smp 1 # -initrd /tmp/tmp.3p9PWc2SRi
  enabling apic
  begining port 0x80 write test
  qemu-system-x86_64: terminating on signal 15 from pid 7790

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4
  ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14
  Uname: Linux 4.14.0-1004-azure-edge x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 06:13:18 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure-edge
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748105/+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 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes

2019-06-24 Thread Po-Hsu Lin
** Tags added: amd64 linux-kvm sru-20190603 ubuntu-ltp-syscalls

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

Title:
  ltp-syscalls: msgstress03 fails because systemd limits number of
  processes

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

Bug description:
  As systemd limits the number of processes, this test will fail because
  it can't fork enough processes. That is limited to when the test is
  run after logging as user 1000, then running sudo. I guess that
  logging as root may not cause this to happen.

  # ./testcases/bin/msgstress03 
  Fork failed (may be OK if under stress)
  Fork failed (may be OK if under stress)
  msgstress031  TFAIL  :  msgstress03.c:157:  Fork failed (may be OK if 
under stress)
  #

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+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 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed

2019-06-24 Thread Po-Hsu Lin
** Tags added: cosmic linux-kvm sru-20190603

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

Title:
  getaddrinfo_01 from ipv6_lib test suite in LTP failed

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

Bug description:
  startup='Wed May 22 08:02:52 2019'
  getaddrinfo_011  TPASS  :  getaddrinfo IPv4 basic lookup
  getaddrinfo_012  TFAIL  :  getaddrinfo_01.c:140: getaddrinfo IPv4 
canonical name ("curly.maas") doesn't match hostname ("curly")
  getaddrinfo_013  TFAIL  :  getaddrinfo_01.c:578: getaddrinfo IPv6 basic 
lookup ("curly") returns -5 ("No address associated with hostname")
  tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  CurrentDmesg:
   
  Date: Wed May 22 08:04:30 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.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  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/1829995/+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 1830676] Re: ltp_acpi from kernel_misc test suite in LTP failed with KVM kernel

2019-06-24 Thread Po-Hsu Lin
*** This bug is a duplicate of bug 1829982 ***
https://bugs.launchpad.net/bugs/1829982

** Tags added: linux-kvm sru-20190603 ubuntu-ltp

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

Title:
  ltp_acpi from kernel_misc test suite in LTP failed with KVM kernel

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

Bug description:
  The 8th test case failed:
  ltp_acpi9  TFAIL  :  ltp_acpi.c:139: Test-case '8'

  
  <<>>
  tag=ltp_acpi stime=1559024090
  cmdline="ltp_acpi"
  contacts=""
  analysis=exit
  <<>>
  ltp_acpi1  TPASS  :  Test-case '0'
  ltp_acpi2  TPASS  :  Test-case '1'
  ltp_acpi3  TPASS  :  Test-case '2'
  ltp_acpi4  TPASS  :  Test-case '3'
  ltp_acpi5  TPASS  :  Test-case '4'
  ltp_acpi6  TPASS  :  Test-case '5'
  ltp_acpi7  TPASS  :  Test-case '6'
  ltp_acpi8  TPASS  :  Test-case '7'
  ltp_acpi9  TFAIL  :  ltp_acpi.c:139: Test-case '8'
  ltp_acpi   10  TPASS  :  Test-case '9'
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=1
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1035-kvm 4.15.0-1035.35
  ProcVersionSignature: User Name 4.15.0-1035.35-kvm 4.15.18
  Uname: Linux 4.15.0-1035-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Tue May 28 06:14:53 2019
  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/1830676/+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 1830670] Re: quota_remount_test01 from fs test suite in LTP failed with KVM kernel

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-ltp

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

Title:
  quota_remount_test01 from fs test suite in LTP failed with KVM kernel

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

Bug description:
  It has something to do with the quota support in the KVM kernel:

   startup='Mon May 27 11:44:24 2019'
   quota_remount_test010  TINFO  :  Successfully mounted the File System
   quota_remount_test010  TINFO  :  Successfully Created Quota Files 
   quotaon: using /tmp/ltp-yQeAGjcnpY/mnt/aquota.group on /dev/loop1 
[/tmp/ltp-yQeAGjcnpY/mnt]: No such process
   quotaon: Quota format not supported in kernel.
   quotaon: using /tmp/ltp-yQeAGjcnpY/mnt/aquota.user on /dev/loop1 
[/tmp/ltp-yQeAGjcnpY/mnt]: No such process
   quotaon: Quota format not supported in kernel.
   Could not turn quota on
   quota_remount_test011  TFAIL  :  ltpapicmd.c:188: Quota on Remount Failed
   tag=quota_remount_test01 stime=1558957464 dur=15 exit=exited stat=2 core=no 
cu=2 cs=23

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1035-kvm 4.15.0-1035.35
  ProcVersionSignature: User Name 4.15.0-1035.35-kvm 4.15.18
  Uname: Linux 4.15.0-1035-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Tue May 28 04:13:51 2019
  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/1830670/+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 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-ltp

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

Title:
  cpuacct_100_100 from controllers test suite in LTP failed

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

Bug description:
   startup='Wed May 22 06:50:45 2019'
   cpuacct 1 TINFO: timeout per run is 0h 5m 0s
   cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct
   cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes
   /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: 
/opt/ltp/testcases/bin/cpuacct.sh: Cannot fork
   tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 
cs=53

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  CurrentDmesg:
   
  Date: Wed May 22 06:59:27 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.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  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/1829978/+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 1830682] Re: cve-2017-5754 from cve test suite in LTP failed with KVM kernel

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-ltp

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

Title:
  cve-2017-5754 from cve test suite in LTP failed with KVM kernel

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

Bug description:
  It looks like this is cause by the absence of kallsyms:
  safe_file_ops.c:202: BROK: Failed to open FILE '/proc/kallsyms' for 
reading at meltdown.c:272: ENOENT

  
  <<>>
  tag=cve-2017-5754 stime=1559026443
  cmdline="meltdown"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  meltdown.c:259: INFO: access time: cached = 49, uncached = 290, threshold = 
119
  safe_file_ops.c:202: BROK: Failed to open FILE '/proc/kallsyms' for reading 
at meltdown.c:272: ENOENT

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=2 corefile=no
  cutime=21 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1013-kvm 4.18.0-1013.13
  ProcVersionSignature: User Name 4.18.0-1013.13-kvm 4.18.20
  Uname: Linux 4.18.0-1013-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Tue May 28 06:54:14 2019
  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/1830682/+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 1833905] Re: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm

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

Title:
  settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels

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

Bug description:
  Issue found on C-KVM, from the test case content, these two tests are:
   * Call settimeofday and verify the time was changed.
   * Call settimeofday with invalid Args and verify that the call fails.

  <<>>
  tag=settimeofday01 stime=1561358482
  cmdline="settimeofday01"
  contacts=""
  analysis=exit
  <<>>
  settimeofday011  TFAIL  :  settimeofday01.c:124: Test condition 1 failed
  settimeofday012  TPASS  :  Test condition 2 successful
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
  ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
  Uname: Linux 4.18.0-1015-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Mon Jun 24 06:41:26 2019
  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/1833905/+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 1833935] Re: sysctl02_sh from ubuntu_ltp failed on KVM kernels because AppArmor enabled

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm

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

Title:
  sysctl02_sh from ubuntu_ltp failed on KVM kernels because AppArmor
  enabled

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

Bug description:
  Test complains about apparmor enabled.
  As it's enabled by default, I think we might need to disable this test.

  Furthermore, this test will need kallsyms to be enabled, which is not
  for KVM kernels.

  <<>>
  tag=sysctl02_sh stime=1561360893
  cmdline="sysctl02.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  sysctl02 1 TINFO: timeout per run is 0h 5m 0s
  sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0
  sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 
18446744073709551615
  sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 
9223372036854775808
  sysctl02 4 TCONF: /proc/kallsyms not enabled
  sysctl02 4 TINFO: AppArmor enabled, this may affect test results
  sysctl02 4 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
  sysctl02 4 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   0
  failed   3
  skipped  1
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=33 corefile=no
  cutime=2 cstime=1
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
  ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
  Uname: Linux 4.18.0-1015-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Mon Jun 24 07:21:41 2019
  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/1833935/+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 1812988] Re: ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes generate kernel traces on Cosmic

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm ubuntu-btrfs-kernel-fixes

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

Title:
  ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes
  generate kernel traces on Cosmic

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

Bug description:
  This issue can only be reproduced on certain HW, node "daedalus"
  (AMD64), "modoc" P8

  And this can only be reproduced when running the whole test suite, it
  will be fine if you just run this test:

Invoking test ff76b0565523319d7c1c0b51d5a5a8915d33efab

fix ff76b0565523319d7c1c0b51d5a5a8915d33efab

Btrfs: Don't allocate inode that is already in use

Due to an off-by-one error, it is possible to reproduce a bug
when the inode cache is used.

The same inode number is assigned twice, the second time this
leads to an EEXIST in btrfs_insert_empty_items().

Create subvolume '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s3'

Found kernel issue:

[ 2713.591492] WARNING: CPU: 18 PID: 61234 at fs/btrfs/inode.c:9256 
btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591494] Modules linked in: btrfs zstd_compress nls_iso8859_1 
ipmi_ssif intel_rapl skx_edac nfit x86_pkg_temp_thermal intel_powerclamp joydev 
input_leds coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel intel_cstate intel_rapl_perf mei_me mei ioatdma ipmi_si dca 
ipmi_devintf ipmi_msghandler acpi_pad acpi_power_meter mac_hid sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ast i2c_algo_bit ttm hid_generic 
drm_kms_helper aesni_intel aes_x86_64 syscopyarea usbhid sysfillrect 
crypto_simd hid sysimgblt cryptd fb_sys_fops ahci glue_helper i40e drm lpc_ich 
libahci wmi [last unloaded: zstd_compress]
[ 2713.591577] CPU: 18 PID: 61234 Comm: umount Tainted: GW 
4.18.0-14-generic #15-Ubuntu
[ 2713.591579] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.01.00.0412.020920172159 02/09/2017
[ 2713.591611] RIP: 0010:btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591612] Code: d0 31 d2 48 89 83 e0 fe ff ff 49 8b 85 e0 03 00 00 48 
85 c0 0f 94 c2 e9 4c ff ff ff 0f 0b e9 60 fe ff ff 0f 0b e9 67 fe ff ff <0f> 0b 
e9 6e fe ff ff 0f 0b e9 75 fe ff ff 0f 0b e9 7c fe ff ff 0f 
[ 2713.591666] RSP: 0018:a966b0bbfc48 EFLAGS: 00010206
[ 2713.591669] RAX: 90c5bf3e6800 RBX: 90c5e06bbc30 RCX: 

[ 2713.591671] RDX:  RSI:  RDI: 
90c5e06bbc30
[ 2713.591673] RBP: a966b0bbfc78 R08: 0001 R09: 
c08fe101
[ 2713.591674] R10: 90c58aac2510 R11: 0001 R12: 
90c5e06bbcb8
[ 2713.591676] R13: c0972940 R14: 90c5e06bbd88 R15: 
a966b0bbfd48
[ 2713.591679] FS:  7f31837e8080() GS:90c61fa8() 
knlGS:
[ 2713.591681] CS:  0010 DS:  ES:  CR0: 80050033
[ 2713.591682] CR2: 7f3183b70308 CR3: 00080167a002 CR4: 
007606e0
[ 2713.591685] DR0:  DR1:  DR2: 

[ 2713.591686] DR3:  DR6: fffe0ff0 DR7: 
0400
[ 2713.591688] PKRU: 5554
[ 2713.591689] Call Trace:
[ 2713.591702]  destroy_inode+0x3e/0x60
[ 2713.591707]  evict+0x139/0x1a0
[ 2713.591711]  iput+0x148/0x210
[ 2713.591739]  free_fs_root+0x1b/0xc0 [btrfs]
[ 2713.591766]  btrfs_drop_and_free_fs_root+0x7c/0xf0 [btrfs]
[ 2713.591793]  btrfs_free_fs_roots+0xdc/0x170 [btrfs]
[ 2713.591824]  ? __btrfs_sysfs_remove_fsid+0x68/0x70 [btrfs]
[ 2713.591852]  close_ctree+0x10c/0x2d0 [btrfs]
[ 2713.591872]  btrfs_put_super+0x15/0x20 [btrfs]
[ 2713.591878]  generic_shutdown_super+0x72/0x110
[ 2713.591882]  kill_anon_super+0x12/0x20
[ 2713.591904]  btrfs_kill_super+0x18/0x110 [btrfs]
[ 2713.591906]  deactivate_locked_super+0x3a/0x80
[ 2713.591907]  deactivate_super+0x51/0x60
[ 2713.591909]  cleanup_mnt+0x3f/0x70
[ 2713.591910]  __cleanup_mnt+0x12/0x20
[ 2713.591915]  task_work_run+0x9d/0xc0
[ 2713.591920]  exit_to_usermode_loop+0xed/0xf0
[ 2713.591922]  

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

2019-06-24 Thread Po-Hsu Lin
** Tags removed: kvm
** Tags added: ubuntu-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/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 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on KVM / Cosmic kernels

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-kernel-selftests

** Tags removed: sru-20190603

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

Title:
  test_bpf in net from ubuntu_kernel_selftests failed on KVM / Cosmic
  kernels

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-kvm source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in linux-kvm source package in Cosmic:
  Invalid

Bug description:
  This test will attempt to insert the test_bpf module, but this module
  does not exist in KVM kernels:

  $ sudo modprobe test_bpf
  modprobe: FATAL: Module test_bpf not found in directory 
/lib/modules/4.15.0-1028-kvm

  The script:
  $ sudo ./test_bpf.sh 
  test_bpf: [FAIL]

  $ cat test_bpf.sh 
  #!/bin/sh
  # SPDX-License-Identifier: GPL-2.0
  # Runs bpf test using test_bpf kernel module

  if /sbin/modprobe -q test_bpf ; then
/sbin/modprobe -q -r test_bpf;
echo "test_bpf: ok";
  else
echo "test_bpf: [FAIL]";
exit 1;
  fi

  This test_bpf module will need the CONFIG_TEST_BPF to be enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 08:29:29 2019
  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/1812189/+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 1812618] Re: psock_snd from net test in ubuntu_kernel_selftests failed on C

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-kernel-selftests

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

Title:
  psock_snd from net test in ubuntu_kernel_selftests failed on C

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

Bug description:
  This test will fail with Resource temporarily unavailable

  $ sudo ./psock_snd.sh 
  dgram
  tx: 128
  rx: 142
  ./psock_snd: recv: Resource temporarily unavailable

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 21 07:41 seq
   crw-rw 1 root audio 116, 33 Jan 21 07:41 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: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jan 21 07:49:29 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-13-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  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/1812618/+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 1812176] Re: psock_tpacket from the net test in ubuntu_kernel_selftests failed on KVM kernels

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603

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

Title:
  psock_tpacket from the net test in ubuntu_kernel_selftests failed on
  KVM kernels

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

Bug description:
  The psock_tpacket in the net test from ubuntu_kernel_selftests failed with 
B-KVM
  $ sudo ./psock_tpacket 
  test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory

  Look into the code, it seems that this file not found error is caused
  by the attempt to access /proc/kallsyms in test_kernel_bit_width():

  static int test_kernel_bit_width(void)
  {
char in[512], *ptr;
int num = 0, fd;
ssize_t ret;

fd = open("/proc/kallsyms", O_RDONLY);
if (fd == -1) {
perror("open");
exit(1);
}

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 08:05:47 2019
  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/1812176/+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 1812318] Re: ftrace test in ubuntu_kernel_selftests failed on KVM kernels

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-kernel-selftests

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

Title:
  ftrace test in ubuntu_kernel_selftests failed on KVM kernels

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

Bug description:
  This test failed with:
  Error: No ftrace directory found

  In the script:
  DEBUGFS_DIR=`grep debugfs /proc/mounts | cut -f2 -d' ' | head -1`
  if [ -z "$DEBUGFS_DIR" ]; then
  TRACING_DIR=`grep tracefs /proc/mounts | cut -f2 -d' ' | head -1`
  else
  TRACING_DIR=$DEBUGFS_DIR/tracing
  fi

  The script exit here:
  # Verify parameters
  if [ -z "$TRACING_DIR" -o ! -d "$TRACING_DIR" ]; then
    errexit "No ftrace directory found"
  fi

  DEBUGFS_DIR=/sys/kernel/debug
  TRACING_DIR=/sys/kernel/debug/tracing

  ls: cannot access '/sys/kernel/debug/tracing': No such file or
  directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Jan 18 03:04:17 2019
  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/1812318/+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 1812620] Re: msg_zerocopy in net from ubuntu_kernel_selftests failed on C

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-kernel-selftests

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

Title:
  msg_zerocopy in net from ubuntu_kernel_selftests failed on C

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

Bug description:
  This test will return 1

  $ sudo ./msg_zerocopy.sh 
  ipv4 tcp -t 1
  ./msg_zerocopy: setaffinity 2
  ./msg_zerocopy: setaffinity 3
  $ echo $?
  1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 21 07:41 seq
   crw-rw 1 root audio 116, 33 Jan 21 07:41 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: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jan 21 07:50:33 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-13-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  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/1812620/+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 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed on C-KVM

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-kernel-selftests

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

Title:
  fib related test in net from ubuntu_kernel_selftests failed on C-KVM

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

Bug description:
  These tests:
  * fib_tests.sh
  * fib-onlink-tests.sh
  * fib_rule_tests.sh

  All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not
  supported:

  
   selftests: net: fib_tests.sh
  
   Single path route test
   RTNETLINK answers: Operation not supported
   not ok 1..11 selftests: net: fib_tests.sh [FAIL]

   selftests: net: fib-onlink-tests.sh
  
  
   Configuring interfaces
   RTNETLINK answers: Operation not supported
   not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL]

   selftests: net: fib_rule_tests.sh
   
   RTNETLINK answers: Operation not supported
   not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL]


  (works on generic Cosmic kernel)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
  ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
  Uname: Linux 4.18.0-1006-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Jan 21 08:00:22 2019
  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/1812622/+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 1812194] Re: RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603

** Tags added: ubuntu-kernel-selftests

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

Title:
  RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels

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

Bug description:
  This test failed because of the unsuccessful attempt to add a dummy device 
with ip link command:
  # devdummy="test-dummy0"
  # ip link add name "$devdummy" type dummy
  RTNETLINK answers: Operation not supported

  
   selftests: rtnetlink.sh
   
   RTNETLINK answers: Operation not supported
   Cannot find device "test-dummy0"
   FAIL: cannot add dummy interface
   not ok 1..10 selftests: rtnetlink.sh [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 10:21:02 2019
  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/1812194/+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 1833396] Re: ubuntu_bpf test failed on KVM kernels

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm

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

Title:
  ubuntu_bpf test failed on KVM kernels

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

Bug description:
  This should not considered as a regression, we just switching from the
  "cloud" test list to the "generic" list.

Summary: 775 PASSED, 0 SKIPPED, 123 FAILED

#165/u PTR_TO_STACK store/load - out of bounds low FAIL
Unexpected error message!
EXP: invalid stack off=-79992 size=8
RES: 0: (bf) r1 = r10
1: (07) r1 += -8
invalid stack off=-8 size=1
R1 stack pointer arithmetic goes out of range, prohibited for !root

0: (bf) r1 = r10
1: (07) r1 += -8
invalid stack off=-8 size=1
R1 stack pointer arithmetic goes out of range, prohibited for !root
#173/p unpriv: check that printk is disallowed FAIL
Failed to load prog 'Invalid argument'!
0: (7a) *(u64 *)(r10 -8) = 0
1: (bf) r1 = r10
2: (07) r1 += -8
3: (b7) r2 = 8
4: (bf) r3 = r1
5: (85) call bpf_trace_printk#6
unknown func bpf_trace_printk#6
#185/p unpriv: spill/fill of different pointers ldx FAIL
Unexpected error message!
EXP: same insn cannot be used with different pointers
RES: 
#193/u unpriv: adding of fp FAIL
Failed to load prog 'Permission denied'!
0: (b7) r0 = 0
1: (b7) r1 = 0
2: (0f) r1 += r10
invalid stack off=0 size=1
R1 stack pointer arithmetic goes out of range, prohibited for !root
#287/p constant register |= constant should keep constant type FAIL
Failed to load prog 'Invalid argument'!
#288/p constant register |= constant should not bypass stack boundary 
checks FAIL
Unexpected error message!
EXP: invalid stack type R1 off=-48 access_size=58
RES: 
#289/p constant register |= constant register should keep constant type FAIL
Failed to load prog 'Invalid argument'!
#290/p constant register |= constant register should not bypass stack 
boundary checks FAIL
Unexpected error message!
EXP: invalid stack type R1 off=-48 access_size=58
RES: 
#306/p helper access to map: full range FAIL
Failed to load prog 'Invalid argument'!
#307/p helper access to map: partial range FAIL
Failed to load prog 'Invalid argument'!
#308/p helper access to map: empty range FAIL
Unexpected error message!
EXP: invalid access to map value, value_size=48 off=0 size=0
RES: 
#309/p helper access to map: out-of-bound range FAIL
Unexpected error message!
EXP: invalid access to map value, value_size=48 off=0 size=56
RES: 
#310/p helper access to map: negative range FAIL
Unexpected error message!
EXP: R2 min value is negative
RES: 
#311/p helper access to adjusted map (via const imm): full range FAIL
Failed to load prog 'Invalid argument'!
#312/p helper access to adjusted map (via const imm): partial range FAIL
Failed to load prog 'Invalid argument'!
#313/p helper access to adjusted map (via const imm): empty range FAIL
Unexpected error message!
EXP: invalid access to map value, value_size=48 off=4 size=0
RES: 
#314/p helper access to adjusted map (via const imm): out-of-bound range 
FAIL
Unexpected error message!
EXP: invalid access to map value, value_size=48 off=4 size=52
RES: 
#315/p helper access to adjusted map (via const imm): negative range (> 
adjustment) FAIL
Unexpected error message!
EXP: R2 min value is negative
RES: 
#316/p helper access to adjusted map (via const imm): negative range (< 
adjustment) FAIL
Unexpected error message!
EXP: R2 min value is negative
RES: 
#317/p helper access to adjusted map (via const reg): full range FAIL
Failed to load prog 'Invalid argument'!
#318/p helper access to adjusted map (via const reg): partial range FAIL
Failed to load prog 'Invalid argument'!
#319/p helper access to adjusted map (via const reg): empty range FAIL
Unexpected error message!
EXP: R1 min value is outside of the array range
RES: 
#320/p helper access to adjusted map (via const reg): out-of-bound range 
FAIL
Unexpected error message!
EXP: invalid access to map value, value_size=48 off=4 size=52
RES: 
#321/p helper access to adjusted map (via const reg): negative range (> 
adjustment) FAIL
Unexpected error message!
EXP: R2 min value is negative
RES: 
#322/p helper access to adjusted map (via const reg): negative range (< 
adjustment) FAIL
Unexpected error message!
EXP: R2 min value is negative
RES: 
#323/p helper access to adjusted map (via variable): full range FAIL
Failed to load prog 'Invalid 

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

2019-06-24 Thread Po-Hsu Lin
** Tags added: linux-kvm sru-20190603 ubuntu-kernel-selftests

-- 
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 1821152] Re: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com'

2019-06-24 Thread Po-Hsu Lin
** Tags removed: kvm
** Tags added: linux-kvm

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

[Kernel-packages] [Bug 1832506] Re: linux-kvm: 4.18.0-1015.15 -proposed tracker

2019-06-24 Thread Po-Hsu Lin
4.18.0-1015.15 - kvm
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_bpf - failed on KVM kernels (bug 1833396)
  ubuntu_btrfs_kernel_fixes - ff76b0565523319d7c1c0b51d5a5a8915d33efab failed 
(bug 1812988)
  ubuntu_fan_smoke_test - should be blacklisted
  ubuntu_kernel_selftests - run_netsocktests in net (bug 1830016) psock_tpacket 
in net failed (bug 1812176) test_bpf in net (bug 1812189) RTNETLINK in net (bug 
1812194) fib_tests in net (bug 1812622) fib-onlink-tests in net (bug 1812622) 
fib_rule_tests in net (bug 1812622) msg_zerocopy in net (bug 1812620) psock_snd 
in net (bug 1812618) ftrace (bug 1812318)
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) apic-split timeouted 
(bug 1821390) port80 (bug 1748105) vmx (bug 1821394)
  ubuntu_ltp - quota_remount_test01 (bug 1830670) hackbench01 (bug 1830675) 
netns_sysfs (bug 1830678) cpuacct_100_100 (bug 1829978) memcg_usage_in_bytes 
(bug 1829984) memcg_stat (bug 1829983) memcg_usage_in_bytes (bug 1829984) 
memcg_use_hierarchy (bug 1829989) leapsec_timer (bug 1829971) mkswap01_sh (bug 
1830584) sysctl02_sh (bug 1833935) getaddrinfo_01 (bug 1829995) cve-2017-5754 
(bug 1830682) ltp_acpi (bug 1830676)
  ubuntu_ltp_syscalls - acct01 skipped (bug 1824794) fanotify09 case 2 (bug 
1804594) msgstress03 (bug 1797341) msgstress04 (bug 1797348) quotactl01, 
quotactl02, quotactl03 (bug 1797325) settimeofday01 (bug 1833905) 
sync_file_range02 (bug 1819116)
  ubuntu_qrt_kernel_security - SCHED_STACK_END_CHECK should be enabled (bug 
1812159)
  ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535)
  ubuntu_ramfs_stress - proxy issue for Intel Cloud (bug 1828786)
  ubuntu_sysdig_smoke_test - Unable to insert sysdig_probe module on KVM kernel 
(bug 1766565)
  ubuntu_unionmount_overlayfs_suite - proxy issue for Intel Cloud (bug 1828786)
  xfstests - no extra disk, this should be skipped (bug 1833407)

Skipped / blacklisted:
  * libhugetlbfs
  * ubuntu_blktrace_smoke_test
  * ubuntu_ecryptfs
  * ubuntu_ftrace_smoke_test
  * ubuntu_lttng_smoke_test
  * ubuntu_seccomp


** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** 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/1832506

Title:
  linux-kvm: 4.18.0-1015.15 -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-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: 1832508
  phase: Testing
  phase-changed: Tuesday, 18. June 2019 15: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
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832506/+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 1831229] Re: getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier = 3 on D-KVM

2019-06-24 Thread Po-Hsu Lin
https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=389617c59d93082c9cb937015879a8adece5bcc6

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

Title:
  getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier =
  3 on D-KVM

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Invalid

Bug description:
  Even with the timeout multiplier set to 3, the test is still failing:

   Waiting for pid 1892 for 21600 seconds
   Checking virt-what to see if we need to set LTP_TIMEOUT_MUL...
   Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 (lp:1797327)
   == Test Suite Summary ==
   7 test cases failed
   0 test cases blacklisted
   Failed test cases : acct01 getrandom02 msgstress03 quotactl01 quotactl02 
quotactl03 sync_file_range02 

  startup='Thu May 30 21:36:06 2019'
  tst_test.c:1096: INFO: Timeout per run is 0h 15m 00s
  getrandom02.c:72: PASS: getrandom returned 256
  Test timeouted, sending SIGKILL!
  tst_test.c:1136: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1137: BROK: Test killed! (timeout?)

  Summary:
  passed   1
  failed   0
  skipped  0
  warnings 0
  tag=getrandom02 stime=1559252166 dur=900 exit=exited stat=2 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831229/+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 1831229] Re: getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier = 3 on D-KVM

2019-06-24 Thread Po-Hsu Lin
** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-oracle (Ubuntu)
   Status: New => Invalid

** Changed in: linux-kvm (Ubuntu)
   Status: New => Invalid

** Tags added: amd64 cosmic sru-20190603 ubuntu-ltp-syscalls

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

Title:
  getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier =
  3 on D-KVM

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Invalid

Bug description:
  Even with the timeout multiplier set to 3, the test is still failing:

   Waiting for pid 1892 for 21600 seconds
   Checking virt-what to see if we need to set LTP_TIMEOUT_MUL...
   Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 (lp:1797327)
   == Test Suite Summary ==
   7 test cases failed
   0 test cases blacklisted
   Failed test cases : acct01 getrandom02 msgstress03 quotactl01 quotactl02 
quotactl03 sync_file_range02 

  startup='Thu May 30 21:36:06 2019'
  tst_test.c:1096: INFO: Timeout per run is 0h 15m 00s
  getrandom02.c:72: PASS: getrandom returned 256
  Test timeouted, sending SIGKILL!
  tst_test.c:1136: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1137: BROK: Test killed! (timeout?)

  Summary:
  passed   1
  failed   0
  skipped  0
  warnings 0
  tag=getrandom02 stime=1559252166 dur=900 exit=exited stat=2 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831229/+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 1830682] Re: cve-2017-5754 from cve test suite in LTP failed with KVM kernel

2019-06-24 Thread Po-Hsu Lin
This test would require CONFIG_KALLSYMS to be enabled, which was not
enabled on KVM kernels.

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

Title:
  cve-2017-5754 from cve test suite in LTP failed with KVM kernel

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

Bug description:
  It looks like this is cause by the absence of kallsyms:
  safe_file_ops.c:202: BROK: Failed to open FILE '/proc/kallsyms' for 
reading at meltdown.c:272: ENOENT

  
  <<>>
  tag=cve-2017-5754 stime=1559026443
  cmdline="meltdown"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  meltdown.c:259: INFO: access time: cached = 49, uncached = 290, threshold = 
119
  safe_file_ops.c:202: BROK: Failed to open FILE '/proc/kallsyms' for reading 
at meltdown.c:272: ENOENT

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=2 corefile=no
  cutime=21 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1013-kvm 4.18.0-1013.13
  ProcVersionSignature: User Name 4.18.0-1013.13-kvm 4.18.20
  Uname: Linux 4.18.0-1013-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Tue May 28 06:54:14 2019
  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/1830682/+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 1833935] [NEW] sysctl02_sh from ubuntu_ltp failed on KVM kernels because AppArmor enabled

2019-06-24 Thread Po-Hsu Lin
Public bug reported:

Test complains about apparmor enabled.
As it's enabled by default, I think we might need to disable this test.

Furthermore, this test will need kallsyms to be enabled, which is not
for KVM kernels.

<<>>
tag=sysctl02_sh stime=1561360893
cmdline="sysctl02.sh"
contacts=""
analysis=exit
<<>>
incrementing stop
sysctl02 1 TINFO: timeout per run is 0h 5m 0s
sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0
sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 
18446744073709551615
sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 9223372036854775808
sysctl02 4 TCONF: /proc/kallsyms not enabled
sysctl02 4 TINFO: AppArmor enabled, this may affect test results
sysctl02 4 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
sysctl02 4 TINFO: loaded AppArmor profiles: none

Summary:
passed   0
failed   3
skipped  1
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=33 corefile=no
cutime=2 cstime=1
<<>>

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
Uname: Linux 4.18.0-1015-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
Date: Mon Jun 24 07:21:41 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic package-from-proposed sru-20190603 ubuntu-ltp 
uec-images

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: sru-20190603 ubuntu-ltp

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

Title:
  sysctl02_sh from ubuntu_ltp failed on KVM kernels because AppArmor
  enabled

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

Bug description:
  Test complains about apparmor enabled.
  As it's enabled by default, I think we might need to disable this test.

  Furthermore, this test will need kallsyms to be enabled, which is not
  for KVM kernels.

  <<>>
  tag=sysctl02_sh stime=1561360893
  cmdline="sysctl02.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  sysctl02 1 TINFO: timeout per run is 0h 5m 0s
  sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0
  sysctl02 2 TFAIL: /proc/sys/fs/file-max overflows and set to 
18446744073709551615
  sysctl02 3 TFAIL: /proc/sys/fs/file-max overflows and set to 
9223372036854775808
  sysctl02 4 TCONF: /proc/kallsyms not enabled
  sysctl02 4 TINFO: AppArmor enabled, this may affect test results
  sysctl02 4 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
  sysctl02 4 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   0
  failed   3
  skipped  1
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=33 corefile=no
  cutime=2 cstime=1
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
  ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
  Uname: Linux 4.18.0-1015-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Mon Jun 24 07:21:41 2019
  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/1833935/+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 1830675] Re: hackbench01 from sched test suite in LTP failed with KVM kernel

2019-06-24 Thread Po-Hsu Lin
** Tags added: sru-20190603 ubuntu-ltp

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

Title:
  hackbench01 from sched test suite in LTP failed with KVM kernel

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

Bug description:
  Test failed with:
  fork() (error: Resource temporarily unavailable)

  <<>>
  tag=hackbench01 stime=1559023701
  cmdline="hackbench 50 process 1000"
  contacts=""
  analysis=exit
  <<>>
  Running with 50*40 (== 2000) tasks.
  fork() (error: Resource temporarily unavailable)
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=30
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1035-kvm 4.15.0-1035.35
  ProcVersionSignature: User Name 4.15.0-1035.35-kvm 4.15.18
  Uname: Linux 4.15.0-1035-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Tue May 28 06:10:47 2019
  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/1830675/+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 1833905] Re: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels

2019-06-24 Thread Po-Hsu Lin
It looks like if we run this test repeatedly, most of the time it will
pass:

$ sudo ./settimeofday01 -i 1000 | grep FAIL | wc -l
10
$ sudo ./settimeofday01 -i 1000 | grep FAIL | wc -l
8
$ sudo ./settimeofday01 -i 1000 | grep FAIL | wc -l
10

This might be able to explain why sometimes we cannot see this failure in the 
test report.
Not sure what is the cause of this

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

Title:
  settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels

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

Bug description:
  Issue found on C-KVM, from the test case content, these two tests are:
   * Call settimeofday and verify the time was changed.
   * Call settimeofday with invalid Args and verify that the call fails.

  <<>>
  tag=settimeofday01 stime=1561358482
  cmdline="settimeofday01"
  contacts=""
  analysis=exit
  <<>>
  settimeofday011  TFAIL  :  settimeofday01.c:124: Test condition 1 failed
  settimeofday012  TPASS  :  Test condition 2 successful
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
  ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
  Uname: Linux 4.18.0-1015-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Mon Jun 24 06:41:26 2019
  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/1833905/+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 1833905] Re: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels

2019-06-24 Thread Po-Hsu Lin
** Description changed:

- Issue found on C-KVM:
+ Issue found on C-KVM, from the test case content, these two tests are:
+  * Call settimeofday and verify the time was changed.
+  * Call settimeofday with invalid Args and verify that the call fails.
  
  <<>>
  tag=settimeofday01 stime=1561358482
  cmdline="settimeofday01"
  contacts=""
  analysis=exit
  <<>>
  settimeofday011  TFAIL  :  settimeofday01.c:124: Test condition 1 failed
  settimeofday012  TPASS  :  Test condition 2 successful
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
  ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
  Uname: Linux 4.18.0-1015-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Mon Jun 24 06:41:26 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels

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

Bug description:
  Issue found on C-KVM, from the test case content, these two tests are:
   * Call settimeofday and verify the time was changed.
   * Call settimeofday with invalid Args and verify that the call fails.

  <<>>
  tag=settimeofday01 stime=1561358482
  cmdline="settimeofday01"
  contacts=""
  analysis=exit
  <<>>
  settimeofday011  TFAIL  :  settimeofday01.c:124: Test condition 1 failed
  settimeofday012  TPASS  :  Test condition 2 successful
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
  ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
  Uname: Linux 4.18.0-1015-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Mon Jun 24 06:41:26 2019
  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/1833905/+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 1824794] Re: acct01 in ubuntu_ltp_syscalls reported as a failure with B-KVM

2019-06-24 Thread Po-Hsu Lin
** Tags added: ubuntu-ltp-syscalls

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

Title:
  acct01 in ubuntu_ltp_syscalls reported as a failure with B-KVM

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

Bug description:
  This test was skipped in the ltp syscalls test, due to unmatched
  configs.

  However the ltp test suite will treat it as a failure, it's better to
  figure out how to skip this.

  <<>>
  tag=acct01 stime=1555326506
  cmdline="acct01"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  incrementing stop
  acct01.c:70: CONF: acct() system call isn't configured in kernel
  safe_macros.c:360: WARN: acct01.c:96: unlink(./tmpfile) failed: ENOENT
  safe_macros.c:360: WARN: acct01.c:97: unlink(test_file_eloop1) failed: ENOENT

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 2
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=36 corefile=no
  cutime=0 cstime=0
  <<>>
  INFO: ltp-pan reported some tests FAIL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1824794/+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 1833905] [NEW] settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels

2019-06-24 Thread Po-Hsu Lin
Public bug reported:

Issue found on C-KVM:

<<>>
tag=settimeofday01 stime=1561358482
cmdline="settimeofday01"
contacts=""
analysis=exit
<<>>
settimeofday011  TFAIL  :  settimeofday01.c:124: Test condition 1 failed
settimeofday012  TPASS  :  Test condition 2 successful
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<>>

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
Uname: Linux 4.18.0-1015-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
Date: Mon Jun 24 06:41:26 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic package-from-proposed sru-20190603 
ubuntu-ltp-syscalls uec-images

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: sru-20190603 ubuntu-ltp-syscalls

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

Title:
  settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels

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

Bug description:
  Issue found on C-KVM:

  <<>>
  tag=settimeofday01 stime=1561358482
  cmdline="settimeofday01"
  contacts=""
  analysis=exit
  <<>>
  settimeofday011  TFAIL  :  settimeofday01.c:124: Test condition 1 failed
  settimeofday012  TPASS  :  Test condition 2 successful
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15
  ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20
  Uname: Linux 4.18.0-1015-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Mon Jun 24 06:41:26 2019
  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/1833905/+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 1824794] Re: acct01 in ubuntu_ltp_syscalls reported as a failure with B-KVM

2019-06-24 Thread Po-Hsu Lin
** Also affects: linux-kvm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  acct01 in ubuntu_ltp_syscalls reported as a failure with B-KVM

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

Bug description:
  This test was skipped in the ltp syscalls test, due to unmatched
  configs.

  However the ltp test suite will treat it as a failure, it's better to
  figure out how to skip this.

  <<>>
  tag=acct01 stime=1555326506
  cmdline="acct01"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  incrementing stop
  acct01.c:70: CONF: acct() system call isn't configured in kernel
  safe_macros.c:360: WARN: acct01.c:96: unlink(./tmpfile) failed: ENOENT
  safe_macros.c:360: WARN: acct01.c:97: unlink(test_file_eloop1) failed: ENOENT

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 2
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=36 corefile=no
  cutime=0 cstime=0
  <<>>
  INFO: ltp-pan reported some tests FAIL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1824794/+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 1831229] Re: getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier = 3 on D-KVM

2019-06-23 Thread Po-Hsu Lin
It looks like haveged helps a lot:

Before installing haveged:
ubuntu@groucho:~$ cat /proc/sys/kernel/random/entropy_avail
79
After:
ubuntu@groucho:~$ cat /proc/sys/kernel/random/entropy_avail
2424

The getrandom tests will finish in the blink of an eye.

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

Title:
  getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier =
  3 on D-KVM

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

Bug description:
  Even with the timeout multiplier set to 3, the test is still failing:

   Waiting for pid 1892 for 21600 seconds
   Checking virt-what to see if we need to set LTP_TIMEOUT_MUL...
   Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 (lp:1797327)
   == Test Suite Summary ==
   7 test cases failed
   0 test cases blacklisted
   Failed test cases : acct01 getrandom02 msgstress03 quotactl01 quotactl02 
quotactl03 sync_file_range02 

  startup='Thu May 30 21:36:06 2019'
  tst_test.c:1096: INFO: Timeout per run is 0h 15m 00s
  getrandom02.c:72: PASS: getrandom returned 256
  Test timeouted, sending SIGKILL!
  tst_test.c:1136: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1137: BROK: Test killed! (timeout?)

  Summary:
  passed   1
  failed   0
  skipped  0
  warnings 0
  tag=getrandom02 stime=1559252166 dur=900 exit=exited stat=2 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831229/+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 1833410] Re: idle-page oopses when accessing page frames that are out of range

2019-06-21 Thread Po-Hsu Lin
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  idle-page oopses when accessing page frames that are out of range

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  New

Bug description:
  == SRU [Xenial][Bionic][Cosmic][Disco] ==

  == Justification ==

  When accessing page frames that are greater than max_pfn using the
  idle-page sysfs interface an oops is triggered that kills the process
  that writes to the sysfs interface.

  == Fix ==

  Upstream fix currently in linux-next:

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/mm/page_idle.c?id=d96d6145d9796d5f1eac242538d45559e9a23404

  This fixes the maximum pfn threshold allowed.

  == Test ==

  sudo stress-ng --idle-page 0

  this should trigger the oops in ~50% of the cases due to the way the
  threshold calculation in the kernel was handling the maximum threshold
  based on pfn alignments. 31 of 63 of the times it may be under the
  threshold so no oops occurs.  If it does not, increase or decrease the
  number of available pages in a system to trigger the sweet spot of the
  bug.

  == Regression Potential ==

  Minimal, this touches a sysfs kernel interface that is not used much.
  The fix narrows the scope of touching specific page frames, so the
  page frame scope is reduced by the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833410/+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 1821903] Re: svm in ubuntu_kvm_unit_test failed on 3.13 / 4.4

2019-06-20 Thread Po-Hsu Lin
Issue still exist with Cosmic amd64 (node gonzo):
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/svm'
 BUILD_HEAD=b5d7d7f1
 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 /tmp/tmp.VnkI4knNSX -smp 2 
-cpu qemu64,+svm,+tsc-adjust # -initrd /tmp/tmp.Ool7CJM5vy
 qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.01H:ECX.vmx [bit 5]
 qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.01H:ECX.vmx [bit 5]
 enabling apic
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 467000
 cr4 = 20
 PASS: null
 PASS: vmrun
 PASS: ioio
 PASS: vmrun intercept check
 PASS: cr3 read intercept
 PASS: cr3 read nointercept
 PASS: cr3 read intercept emulate
 PASS: dr intercept check
 PASS: msr intercept check
 PASS: mode_switch
 PASS: asid_zero
 PASS: sel_cr0_bug
 FAIL: tsc_adjust
 Latency VMRUN : max: 169094 min: 17443 avg: 17769 
 Latency VMEXIT: max: 127855 min: 17870 avg: 18294 
 PASS: latency_run_exit
 Latency VMLOAD: max: 61609 min: 4802 avg: 4958
 Latency VMSAVE: max: 36274 min: 4676 avg: 4869
 Latency STGI: max: 72350 min: 3969 avg: 4070
 Latency CLGI: max: 69159 min: 3511 avg: 3534
 PASS: latency_svm_insn
 SUMMARY: 15 tests, 1 unexpected failures
 FAIL svm (15 tests, 1 unexpected failures)


** Tags added: cosmic

** Tags added: sru-20190603

** Tags added: ubuntu-kvm-unit-tests

** Summary changed:

- svm in ubuntu_kvm_unit_test failed on 3.13 / 4.4
+ svm in ubuntu_kvm_unit_tests failed on 3.13 / 4.4 / 4.18

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => 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/1821903

Title:
  svm in ubuntu_kvm_unit_tests failed on 3.13 / 4.4 / 4.18

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Incomplete
Status in linux-signed-lts-xenial source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-signed-lts-xenial source package in Xenial:
  Invalid
Status in linux source package in Cosmic:
  Confirmed
Status in linux-signed-lts-xenial source package in Cosmic:
  Invalid

Bug description:
  This svm test timeouted on T-3.13
  failed on T-4.4 with:

  
root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests#
  TESTNAME=svm TIMEOUT=90s ACCEL= ./x86/run x86/svm.flat -smp 2 -cpu qemu64,+svm
  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/svm.flat -smp 
2 -cpu qemu64,+svm # -initrd /tmp/tmp.PDi0UKyCcl

  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 466000
  cr4 = 20
  PASS: null
  PASS: vmrun
  PASS: ioio
  PASS: vmrun intercept check
  PASS: cr3 read intercept
  PASS: cr3 read nointercept
  PASS: cr3 read intercept emulate
  PASS: dr intercept check
  PASS: msr intercept check
  PASS: mode_switch
  PASS: asid_zero
  PASS: sel_cr0_bug
  FAIL: tsc_adjust
  Latency VMRUN : max: 80562 min: 19763 avg: 20374
  Latency VMEXIT: max: 83146 min: 20193 avg: 20834
  PASS: latency_run_exit
  Latency VMLOAD: max: 38298 min: 4619 avg: 4838
  Latency VMSAVE: max: 32870 min: 4637 avg: 4809
  Latency STGI:   max: 55478 min: 3846 avg: 3923
  Latency CLGI:   max: 67473 min: 3379 avg: 3437
  PASS: latency_svm_insn
  SUMMARY: 15 tests, 1 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2
  ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Wed Mar 27 11:00:42 2019
  SourcePackage: linux-signed-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821903/+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 1833396] Re: ubuntu_bpf test failed on KVM kernels

2019-06-19 Thread Po-Hsu Lin
** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: sru-20190603 ubuntu-bpf

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

Title:
  ubuntu_bpf test failed on KVM kernels

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

Bug description:
  This should not considered as a regression, we just switching from the
  "cloud" test list to the "generic" list.

Summary: 775 PASSED, 0 SKIPPED, 123 FAILED

#165/u PTR_TO_STACK store/load - out of bounds low FAIL
Unexpected error message!
EXP: invalid stack off=-79992 size=8
RES: 0: (bf) r1 = r10
1: (07) r1 += -8
invalid stack off=-8 size=1
R1 stack pointer arithmetic goes out of range, prohibited for !root

0: (bf) r1 = r10
1: (07) r1 += -8
invalid stack off=-8 size=1
R1 stack pointer arithmetic goes out of range, prohibited for !root
#173/p unpriv: check that printk is disallowed FAIL
Failed to load prog 'Invalid argument'!
0: (7a) *(u64 *)(r10 -8) = 0
1: (bf) r1 = r10
2: (07) r1 += -8
3: (b7) r2 = 8
4: (bf) r3 = r1
5: (85) call bpf_trace_printk#6
unknown func bpf_trace_printk#6
#185/p unpriv: spill/fill of different pointers ldx FAIL
Unexpected error message!
EXP: same insn cannot be used with different pointers
RES: 
#193/u unpriv: adding of fp FAIL
Failed to load prog 'Permission denied'!
0: (b7) r0 = 0
1: (b7) r1 = 0
2: (0f) r1 += r10
invalid stack off=0 size=1
R1 stack pointer arithmetic goes out of range, prohibited for !root
#287/p constant register |= constant should keep constant type FAIL
Failed to load prog 'Invalid argument'!
#288/p constant register |= constant should not bypass stack boundary 
checks FAIL
Unexpected error message!
EXP: invalid stack type R1 off=-48 access_size=58
RES: 
#289/p constant register |= constant register should keep constant type FAIL
Failed to load prog 'Invalid argument'!
#290/p constant register |= constant register should not bypass stack 
boundary checks FAIL
Unexpected error message!
EXP: invalid stack type R1 off=-48 access_size=58
RES: 
#306/p helper access to map: full range FAIL
Failed to load prog 'Invalid argument'!
#307/p helper access to map: partial range FAIL
Failed to load prog 'Invalid argument'!
#308/p helper access to map: empty range FAIL
Unexpected error message!
EXP: invalid access to map value, value_size=48 off=0 size=0
RES: 
#309/p helper access to map: out-of-bound range FAIL
Unexpected error message!
EXP: invalid access to map value, value_size=48 off=0 size=56
RES: 
#310/p helper access to map: negative range FAIL
Unexpected error message!
EXP: R2 min value is negative
RES: 
#311/p helper access to adjusted map (via const imm): full range FAIL
Failed to load prog 'Invalid argument'!
#312/p helper access to adjusted map (via const imm): partial range FAIL
Failed to load prog 'Invalid argument'!
#313/p helper access to adjusted map (via const imm): empty range FAIL
Unexpected error message!
EXP: invalid access to map value, value_size=48 off=4 size=0
RES: 
#314/p helper access to adjusted map (via const imm): out-of-bound range 
FAIL
Unexpected error message!
EXP: invalid access to map value, value_size=48 off=4 size=52
RES: 
#315/p helper access to adjusted map (via const imm): negative range (> 
adjustment) FAIL
Unexpected error message!
EXP: R2 min value is negative
RES: 
#316/p helper access to adjusted map (via const imm): negative range (< 
adjustment) FAIL
Unexpected error message!
EXP: R2 min value is negative
RES: 
#317/p helper access to adjusted map (via const reg): full range FAIL
Failed to load prog 'Invalid argument'!
#318/p helper access to adjusted map (via const reg): partial range FAIL
Failed to load prog 'Invalid argument'!
#319/p helper access to adjusted map (via const reg): empty range FAIL
Unexpected error message!
EXP: R1 min value is outside of the array range
RES: 
#320/p helper access to adjusted map (via const reg): out-of-bound range 
FAIL
Unexpected error message!
EXP: invalid access to map value, value_size=48 off=4 size=52
RES: 
#321/p helper access to adjusted map (via const reg): negative range (> 
adjustment) FAIL
Unexpected error message!
EXP: R2 min value is negative
RES: 
#322/p helper access to adjusted map (via const reg): negative range (< 
adjustment) FAIL
Unexpected error message!
EXP: R2 min value is negative
RES: 
#323/p 

[Kernel-packages] [Bug 1833396] [NEW] ubuntu_bpf test failed on KVM kernels

2019-06-19 Thread Po-Hsu Lin
Public bug reported:

This should not considered as a regression, we just switching from the
"cloud" test list to the "generic" list.

  Summary: 775 PASSED, 0 SKIPPED, 123 FAILED

  #165/u PTR_TO_STACK store/load - out of bounds low FAIL
  Unexpected error message!
EXP: invalid stack off=-79992 size=8
RES: 0: (bf) r1 = r10
  1: (07) r1 += -8
  invalid stack off=-8 size=1
  R1 stack pointer arithmetic goes out of range, prohibited for !root
  
  0: (bf) r1 = r10
  1: (07) r1 += -8
  invalid stack off=-8 size=1
  R1 stack pointer arithmetic goes out of range, prohibited for !root
  #173/p unpriv: check that printk is disallowed FAIL
  Failed to load prog 'Invalid argument'!
  0: (7a) *(u64 *)(r10 -8) = 0
  1: (bf) r1 = r10
  2: (07) r1 += -8
  3: (b7) r2 = 8
  4: (bf) r3 = r1
  5: (85) call bpf_trace_printk#6
  unknown func bpf_trace_printk#6
  #185/p unpriv: spill/fill of different pointers ldx FAIL
  Unexpected error message!
EXP: same insn cannot be used with different pointers
RES: 
  #193/u unpriv: adding of fp FAIL
  Failed to load prog 'Permission denied'!
  0: (b7) r0 = 0
  1: (b7) r1 = 0
  2: (0f) r1 += r10
  invalid stack off=0 size=1
  R1 stack pointer arithmetic goes out of range, prohibited for !root
  #287/p constant register |= constant should keep constant type FAIL
  Failed to load prog 'Invalid argument'!
  #288/p constant register |= constant should not bypass stack boundary checks 
FAIL
  Unexpected error message!
EXP: invalid stack type R1 off=-48 access_size=58
RES: 
  #289/p constant register |= constant register should keep constant type FAIL
  Failed to load prog 'Invalid argument'!
  #290/p constant register |= constant register should not bypass stack 
boundary checks FAIL
  Unexpected error message!
EXP: invalid stack type R1 off=-48 access_size=58
RES: 
  #306/p helper access to map: full range FAIL
  Failed to load prog 'Invalid argument'!
  #307/p helper access to map: partial range FAIL
  Failed to load prog 'Invalid argument'!
  #308/p helper access to map: empty range FAIL
  Unexpected error message!
EXP: invalid access to map value, value_size=48 off=0 size=0
RES: 
  #309/p helper access to map: out-of-bound range FAIL
  Unexpected error message!
EXP: invalid access to map value, value_size=48 off=0 size=56
RES: 
  #310/p helper access to map: negative range FAIL
  Unexpected error message!
EXP: R2 min value is negative
RES: 
  #311/p helper access to adjusted map (via const imm): full range FAIL
  Failed to load prog 'Invalid argument'!
  #312/p helper access to adjusted map (via const imm): partial range FAIL
  Failed to load prog 'Invalid argument'!
  #313/p helper access to adjusted map (via const imm): empty range FAIL
  Unexpected error message!
EXP: invalid access to map value, value_size=48 off=4 size=0
RES: 
  #314/p helper access to adjusted map (via const imm): out-of-bound range FAIL
  Unexpected error message!
EXP: invalid access to map value, value_size=48 off=4 size=52
RES: 
  #315/p helper access to adjusted map (via const imm): negative range (> 
adjustment) FAIL
  Unexpected error message!
EXP: R2 min value is negative
RES: 
  #316/p helper access to adjusted map (via const imm): negative range (< 
adjustment) FAIL
  Unexpected error message!
EXP: R2 min value is negative
RES: 
  #317/p helper access to adjusted map (via const reg): full range FAIL
  Failed to load prog 'Invalid argument'!
  #318/p helper access to adjusted map (via const reg): partial range FAIL
  Failed to load prog 'Invalid argument'!
  #319/p helper access to adjusted map (via const reg): empty range FAIL
  Unexpected error message!
EXP: R1 min value is outside of the array range
RES: 
  #320/p helper access to adjusted map (via const reg): out-of-bound range FAIL
  Unexpected error message!
EXP: invalid access to map value, value_size=48 off=4 size=52
RES: 
  #321/p helper access to adjusted map (via const reg): negative range (> 
adjustment) FAIL
  Unexpected error message!
EXP: R2 min value is negative
RES: 
  #322/p helper access to adjusted map (via const reg): negative range (< 
adjustment) FAIL
  Unexpected error message!
EXP: R2 min value is negative
RES: 
  #323/p helper access to adjusted map (via variable): full range FAIL
  Failed to load prog 'Invalid argument'!
  #324/p helper access to adjusted map (via variable): partial range FAIL
  Failed to load prog 'Invalid argument'!
  #325/p helper access to adjusted map (via variable): empty range FAIL
  Unexpected error message!
EXP: R1 min value is outside of the array range
RES: 
  #326/p helper access to adjusted map (via variable): no max check FAIL
  Unexpected error message!
EXP: R1 unbounded memory access
RES: 
  #327/p helper access to 

[Kernel-packages] [Bug 1812988] Re: ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes generate kernel traces on Cosmic

2019-06-19 Thread Po-Hsu Lin
For the KVM kernel,
the kernel trace is a bit different, but just like description here, it will 
pass when you just run this test alone.

https://pastebin.ubuntu.com/p/j6GtqdnDVR/

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

Title:
  ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes
  generate kernel traces on Cosmic

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

Bug description:
  This issue can only be reproduced on certain HW, node "daedalus"
  (AMD64), "modoc" P8

  And this can only be reproduced when running the whole test suite, it
  will be fine if you just run this test:

Invoking test ff76b0565523319d7c1c0b51d5a5a8915d33efab

fix ff76b0565523319d7c1c0b51d5a5a8915d33efab

Btrfs: Don't allocate inode that is already in use

Due to an off-by-one error, it is possible to reproduce a bug
when the inode cache is used.

The same inode number is assigned twice, the second time this
leads to an EEXIST in btrfs_insert_empty_items().

Create subvolume '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s3'

Found kernel issue:

[ 2713.591492] WARNING: CPU: 18 PID: 61234 at fs/btrfs/inode.c:9256 
btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591494] Modules linked in: btrfs zstd_compress nls_iso8859_1 
ipmi_ssif intel_rapl skx_edac nfit x86_pkg_temp_thermal intel_powerclamp joydev 
input_leds coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel intel_cstate intel_rapl_perf mei_me mei ioatdma ipmi_si dca 
ipmi_devintf ipmi_msghandler acpi_pad acpi_power_meter mac_hid sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ast i2c_algo_bit ttm hid_generic 
drm_kms_helper aesni_intel aes_x86_64 syscopyarea usbhid sysfillrect 
crypto_simd hid sysimgblt cryptd fb_sys_fops ahci glue_helper i40e drm lpc_ich 
libahci wmi [last unloaded: zstd_compress]
[ 2713.591577] CPU: 18 PID: 61234 Comm: umount Tainted: GW 
4.18.0-14-generic #15-Ubuntu
[ 2713.591579] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.01.00.0412.020920172159 02/09/2017
[ 2713.591611] RIP: 0010:btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591612] Code: d0 31 d2 48 89 83 e0 fe ff ff 49 8b 85 e0 03 00 00 48 
85 c0 0f 94 c2 e9 4c ff ff ff 0f 0b e9 60 fe ff ff 0f 0b e9 67 fe ff ff <0f> 0b 
e9 6e fe ff ff 0f 0b e9 75 fe ff ff 0f 0b e9 7c fe ff ff 0f 
[ 2713.591666] RSP: 0018:a966b0bbfc48 EFLAGS: 00010206
[ 2713.591669] RAX: 90c5bf3e6800 RBX: 90c5e06bbc30 RCX: 

[ 2713.591671] RDX:  RSI:  RDI: 
90c5e06bbc30
[ 2713.591673] RBP: a966b0bbfc78 R08: 0001 R09: 
c08fe101
[ 2713.591674] R10: 90c58aac2510 R11: 0001 R12: 
90c5e06bbcb8
[ 2713.591676] R13: c0972940 R14: 90c5e06bbd88 R15: 
a966b0bbfd48
[ 2713.591679] FS:  7f31837e8080() GS:90c61fa8() 
knlGS:
[ 2713.591681] CS:  0010 DS:  ES:  CR0: 80050033
[ 2713.591682] CR2: 7f3183b70308 CR3: 00080167a002 CR4: 
007606e0
[ 2713.591685] DR0:  DR1:  DR2: 

[ 2713.591686] DR3:  DR6: fffe0ff0 DR7: 
0400
[ 2713.591688] PKRU: 5554
[ 2713.591689] Call Trace:
[ 2713.591702]  destroy_inode+0x3e/0x60
[ 2713.591707]  evict+0x139/0x1a0
[ 2713.591711]  iput+0x148/0x210
[ 2713.591739]  free_fs_root+0x1b/0xc0 [btrfs]
[ 2713.591766]  btrfs_drop_and_free_fs_root+0x7c/0xf0 [btrfs]
[ 2713.591793]  btrfs_free_fs_roots+0xdc/0x170 [btrfs]
[ 2713.591824]  ? __btrfs_sysfs_remove_fsid+0x68/0x70 [btrfs]
[ 2713.591852]  close_ctree+0x10c/0x2d0 [btrfs]
[ 2713.591872]  btrfs_put_super+0x15/0x20 [btrfs]
[ 2713.591878]  generic_shutdown_super+0x72/0x110
[ 2713.591882]  kill_anon_super+0x12/0x20
[ 2713.591904]  btrfs_kill_super+0x18/0x110 [btrfs]
[ 2713.591906]  deactivate_locked_super+0x3a/0x80
[ 2713.591907]  deactivate_super+0x51/0x60
[ 2713.591909]  cleanup_mnt+0x3f/0x70
[ 2713.591910]  

[Kernel-packages] [Bug 1833375] Re: lp1262692 in ubuntu_cts_kernel test failed on KVM kernels

2019-06-19 Thread Po-Hsu Lin
** No longer affects: linux-kvm (Ubuntu)

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

Title:
  lp1262692 in ubuntu_cts_kernel test failed on KVM kernels

Status in ubuntu-kernel-tests:
  In Progress

Bug description:
  Test failed with:
Error: Unknown device type.

  
  Further inspection shows this has failed on the first line:
ip link add testdummy0 type dummy

  It is because the KVM kernel does not have the dummy module:
  $ sudo modprobe dummy
  modprobe: FATAL: Module dummy not found in directory 
/lib/modules/5.0.0-1008-kvm

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1008-kvm 5.0.0-1008.8
  ProcVersionSignature: User Name 5.0.0-1008.8-kvm 5.0.8
  Uname: Linux 5.0.0-1008-kvm x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed Jun 19 06:40:02 2019
  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/1833375/+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 1833375] [NEW] lp1262692 in ubuntu_cts_kernel test failed on KVM kernels

2019-06-19 Thread Po-Hsu Lin
Public bug reported:

Test failed with:
  Error: Unknown device type.


Further inspection shows this has failed on the first line:
  ip link add testdummy0 type dummy

It is because the KVM kernel does not have the dummy module:
$ sudo modprobe dummy
modprobe: FATAL: Module dummy not found in directory /lib/modules/5.0.0-1008-kvm

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-1008-kvm 5.0.0-1008.8
ProcVersionSignature: User Name 5.0.0-1008.8-kvm 5.0.8
Uname: Linux 5.0.0-1008-kvm x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Wed Jun 19 06:40:02 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Assignee: Po-Hsu Lin (cypressyew)
 Status: In Progress

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco sru-20190603 ubuntu-cts-kernel uec-images

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: sru-20190603 ubuntu-cts-kernel

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

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

Title:
  lp1262692 in ubuntu_cts_kernel test failed on KVM kernels

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

Bug description:
  Test failed with:
Error: Unknown device type.

  
  Further inspection shows this has failed on the first line:
ip link add testdummy0 type dummy

  It is because the KVM kernel does not have the dummy module:
  $ sudo modprobe dummy
  modprobe: FATAL: Module dummy not found in directory 
/lib/modules/5.0.0-1008-kvm

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1008-kvm 5.0.0-1008.8
  ProcVersionSignature: User Name 5.0.0-1008.8-kvm 5.0.8
  Uname: Linux 5.0.0-1008-kvm x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed Jun 19 06:40:02 2019
  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/1833375/+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 1812988] Re: ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes generate kernel traces on Cosmic

2019-06-18 Thread Po-Hsu Lin
** Also affects: linux-kvm (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: sru-20190603

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

Title:
  ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes
  generate kernel traces on Cosmic

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

Bug description:
  This issue can only be reproduced on certain HW, node "daedalus"
  (AMD64), "modoc" P8

  And this can only be reproduced when running the whole test suite, it
  will be fine if you just run this test:

Invoking test ff76b0565523319d7c1c0b51d5a5a8915d33efab

fix ff76b0565523319d7c1c0b51d5a5a8915d33efab

Btrfs: Don't allocate inode that is already in use

Due to an off-by-one error, it is possible to reproduce a bug
when the inode cache is used.

The same inode number is assigned twice, the second time this
leads to an EEXIST in btrfs_insert_empty_items().

Create subvolume '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s3'

Found kernel issue:

[ 2713.591492] WARNING: CPU: 18 PID: 61234 at fs/btrfs/inode.c:9256 
btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591494] Modules linked in: btrfs zstd_compress nls_iso8859_1 
ipmi_ssif intel_rapl skx_edac nfit x86_pkg_temp_thermal intel_powerclamp joydev 
input_leds coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel intel_cstate intel_rapl_perf mei_me mei ioatdma ipmi_si dca 
ipmi_devintf ipmi_msghandler acpi_pad acpi_power_meter mac_hid sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ast i2c_algo_bit ttm hid_generic 
drm_kms_helper aesni_intel aes_x86_64 syscopyarea usbhid sysfillrect 
crypto_simd hid sysimgblt cryptd fb_sys_fops ahci glue_helper i40e drm lpc_ich 
libahci wmi [last unloaded: zstd_compress]
[ 2713.591577] CPU: 18 PID: 61234 Comm: umount Tainted: GW 
4.18.0-14-generic #15-Ubuntu
[ 2713.591579] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.01.00.0412.020920172159 02/09/2017
[ 2713.591611] RIP: 0010:btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591612] Code: d0 31 d2 48 89 83 e0 fe ff ff 49 8b 85 e0 03 00 00 48 
85 c0 0f 94 c2 e9 4c ff ff ff 0f 0b e9 60 fe ff ff 0f 0b e9 67 fe ff ff <0f> 0b 
e9 6e fe ff ff 0f 0b e9 75 fe ff ff 0f 0b e9 7c fe ff ff 0f 
[ 2713.591666] RSP: 0018:a966b0bbfc48 EFLAGS: 00010206
[ 2713.591669] RAX: 90c5bf3e6800 RBX: 90c5e06bbc30 RCX: 

[ 2713.591671] RDX:  RSI:  RDI: 
90c5e06bbc30
[ 2713.591673] RBP: a966b0bbfc78 R08: 0001 R09: 
c08fe101
[ 2713.591674] R10: 90c58aac2510 R11: 0001 R12: 
90c5e06bbcb8
[ 2713.591676] R13: c0972940 R14: 90c5e06bbd88 R15: 
a966b0bbfd48
[ 2713.591679] FS:  7f31837e8080() GS:90c61fa8() 
knlGS:
[ 2713.591681] CS:  0010 DS:  ES:  CR0: 80050033
[ 2713.591682] CR2: 7f3183b70308 CR3: 00080167a002 CR4: 
007606e0
[ 2713.591685] DR0:  DR1:  DR2: 

[ 2713.591686] DR3:  DR6: fffe0ff0 DR7: 
0400
[ 2713.591688] PKRU: 5554
[ 2713.591689] Call Trace:
[ 2713.591702]  destroy_inode+0x3e/0x60
[ 2713.591707]  evict+0x139/0x1a0
[ 2713.591711]  iput+0x148/0x210
[ 2713.591739]  free_fs_root+0x1b/0xc0 [btrfs]
[ 2713.591766]  btrfs_drop_and_free_fs_root+0x7c/0xf0 [btrfs]
[ 2713.591793]  btrfs_free_fs_roots+0xdc/0x170 [btrfs]
[ 2713.591824]  ? __btrfs_sysfs_remove_fsid+0x68/0x70 [btrfs]
[ 2713.591852]  close_ctree+0x10c/0x2d0 [btrfs]
[ 2713.591872]  btrfs_put_super+0x15/0x20 [btrfs]
[ 2713.591878]  generic_shutdown_super+0x72/0x110
[ 2713.591882]  kill_anon_super+0x12/0x20
[ 2713.591904]  btrfs_kill_super+0x18/0x110 [btrfs]
[ 2713.591906]  deactivate_locked_super+0x3a/0x80
[ 2713.591907]  deactivate_super+0x51/0x60
[ 2713.591909]  cleanup_mnt+0x3f/0x70
[ 2713.591910]  __cleanup_mnt+0x12/0x20
[ 2713.591915]  task_work_run+0x9d/0xc0
[ 

[Kernel-packages] [Bug 1833028] Re: fanotify06 from ubuntu_ltp_syscalls failed

2019-06-17 Thread Po-Hsu Lin
** Description changed:

  == SRU Justification ==
- fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for overlayfs 
has received more than one expected event:
+ fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for
+ overlayfs has received more than one expected event:
+   <<>>
+   tag=fanotify06 stime=1560747299
+   cmdline="fanotify06"
+   contacts=""
+   analysis=exit
+   <<>>
+   incrementing stop
+   tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
+   tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
+   mke2fs 1.44.6 (5-Mar-2019)
+   tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s
+   fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark
+   fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15
+   
+   fanotify06.c:230: PASS: group 8 got no event
+   fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
+   fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24)
+   fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24)
+   fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24)
+   fanotify06.c:220: FAIL: group 3 got event
+   fanotify06.c:220: FAIL: group 4 got event
+   fanotify06.c:220: FAIL: group 5 got event
+   fanotify06.c:220: FAIL: group 6 got event
+   fanotify06.c:220: FAIL: group 7 got event
+   fanotify06.c:220: FAIL: group 8 got event
  
- <<>>
- tag=fanotify06 stime=1560747299
- cmdline="fanotify06"
- contacts=""
- analysis=exit
- <<>>
- incrementing stop
- tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
- tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
- mke2fs 1.44.6 (5-Mar-2019)
- tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s
- fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark
- fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15
- 
- fanotify06.c:230: PASS: group 8 got no event
- fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
- fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24)
- fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24)
- fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24)
- fanotify06.c:220: FAIL: group 3 got event
- fanotify06.c:220: FAIL: group 4 got event
- fanotify06.c:220: FAIL: group 5 got event
- fanotify06.c:220: FAIL: group 6 got event
- fanotify06.c:220: FAIL: group 7 got event
- fanotify06.c:220: FAIL: group 8 got event
+   Summary:
+   passed 9
+   failed 9
+   skipped 0
+   warnings 0
  
- Summary:
- passed   9
- failed   9
- skipped  0
- warnings 0
- <<>>
- initiation_status="ok"
- duration=3 termination_type=exited termination_id=1 corefile=no
- cutime=0 cstime=1
- <<>>
- 
- This duplicated event was generated with operations on files with "fake"
- path.
+ This duplicated event was generated with operations on files with
+ "fake" path.
  
  == Fix ==
  * d9899030 (ovl: do not generate duplicate fsnotify events for "fake" path)
  
  This patch can be cherry-picked into Disco.
  
- For older kernels, they are not affected by this issue (without commit
- d1d04ef8)
+ Older kernels are not affected by this issue (without commit d1d04ef8)
  
  == Test ==
  Test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1833028-fanotify06-ovl/
  
- Verified on a KVM node, the fanotify06 test will pass with this patched 
kernel:
+ Verified on a KVM node, the fanotify06 test will pass with this patched
+ disco kernel:
   fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
   fanotify06.c:147: PASS: group 0 got event: mask 2 pid=5997 fd=30
   fanotify06.c:147: PASS: group 1 got event: mask 2 pid=5997 fd=30
   fanotify06.c:147: PASS: group 2 got event: mask 2 pid=5997 fd=30
   fanotify06.c:230: PASS: group 3 got no event
   fanotify06.c:230: PASS: group 4 got no event
   fanotify06.c:230: PASS: group 5 got no event
   fanotify06.c:230: PASS: group 6 got no event
   fanotify06.c:230: PASS: group 7 got no event
   fanotify06.c:230: PASS: group 8 got no event
  
  == Regression Potential ==
- Low, fix limited to overlayfs and just corrects the flag behaviour with 
"fake" path.
+ Low, fix limited to the overlayfs and just corrects the flag behaviour
+ with "fake" path.
  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-16-generic 5.0.0-16.17
  ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 17 04:37 seq
   crw-rw 1 root audio 116, 33 Jun 17 04:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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:
  CurrentDmesg:
  
  Date: Mon Jun 

[Kernel-packages] [Bug 1833028] Re: fanotify06 from ubuntu_ltp_syscalls failed

2019-06-17 Thread Po-Hsu Lin
** Description changed:

- This is a new test for overlayfs:
+ == SRU Justification ==
+ fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for overlayfs 
has received more than one expected event:
+ 
  <<>>
  tag=fanotify06 stime=1560747299
  cmdline="fanotify06"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s
  fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark
  fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15
- fanotify06.c:147: PASS: group 1 got event: mask 2 pid=1136 fd=15
- fanotify06.c:147: PASS: group 2 got event: mask 2 pid=1136 fd=15
- fanotify06.c:230: PASS: group 3 got no event
- fanotify06.c:230: PASS: group 4 got no event
- fanotify06.c:230: PASS: group 5 got no event
- fanotify06.c:230: PASS: group 6 got no event
- fanotify06.c:230: PASS: group 7 got no event
+ 
  fanotify06.c:230: PASS: group 8 got no event
  fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
  fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24)
  fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24)
  fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24)
  fanotify06.c:220: FAIL: group 3 got event
  fanotify06.c:220: FAIL: group 4 got event
  fanotify06.c:220: FAIL: group 5 got event
  fanotify06.c:220: FAIL: group 6 got event
  fanotify06.c:220: FAIL: group 7 got event
  fanotify06.c:220: FAIL: group 8 got event
  
  Summary:
  passed   9
  failed   9
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=1
  <<>>
  
+ This duplicated event was generated with operations on files with "fake"
+ path.
+ 
+ == Fix ==
+ * d9899030 (ovl: do not generate duplicate fsnotify events for "fake" path)
+ 
+ This patch can be cherry-picked into Disco.
+ 
+ For older kernels, they are not affected by this issue (without commit
+ d1d04ef8)
+ 
+ == Test ==
+ Test kernel could be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1833028-fanotify06-ovl/
+ 
+ Verified on a KVM node, the fanotify06 test will pass with this patched 
kernel:
+  fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
+  fanotify06.c:147: PASS: group 0 got event: mask 2 pid=5997 fd=30
+  fanotify06.c:147: PASS: group 1 got event: mask 2 pid=5997 fd=30
+  fanotify06.c:147: PASS: group 2 got event: mask 2 pid=5997 fd=30
+  fanotify06.c:230: PASS: group 3 got no event
+  fanotify06.c:230: PASS: group 4 got no event
+  fanotify06.c:230: PASS: group 5 got no event
+  fanotify06.c:230: PASS: group 6 got no event
+  fanotify06.c:230: PASS: group 7 got no event
+  fanotify06.c:230: PASS: group 8 got no event
+ 
+ == Regression Potential ==
+ Low, fix limited to overlayfs and just corrects the flag behaviour with 
"fake" path.
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-16-generic 5.0.0-16.17
  ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Jun 17 04:37 seq
-  crw-rw 1 root audio 116, 33 Jun 17 04:37 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Jun 17 04:37 seq
+  crw-rw 1 root audio 116, 33 Jun 17 04:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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:
  CurrentDmesg:
-  
+ 
  Date: Mon Jun 17 04:40:18 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-5.0.0-16-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro
  RelatedPackageVersions:
-  linux-restricted-modules-5.0.0-16-generic N/A
-  linux-backports-modules-5.0.0-16-generic  N/A
-  linux-firmware1.178.1
+  linux-restricted-modules-5.0.0-16-generic N/A
+  linux-backports-modules-5.0.0-16-generic  N/A
+  linux-firmware1.178.1
  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: 

[Kernel-packages] [Bug 1833028] Re: fanotify06 from ubuntu_ltp_syscalls failed

2019-06-17 Thread Po-Hsu Lin
** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Disco)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  fanotify06 from ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  This is a new test for overlayfs:
  <<>>
  tag=fanotify06 stime=1560747299
  cmdline="fanotify06"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s
  fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark
  fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15
  fanotify06.c:147: PASS: group 1 got event: mask 2 pid=1136 fd=15
  fanotify06.c:147: PASS: group 2 got event: mask 2 pid=1136 fd=15
  fanotify06.c:230: PASS: group 3 got no event
  fanotify06.c:230: PASS: group 4 got no event
  fanotify06.c:230: PASS: group 5 got no event
  fanotify06.c:230: PASS: group 6 got no event
  fanotify06.c:230: PASS: group 7 got no event
  fanotify06.c:230: PASS: group 8 got no event
  fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
  fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24)
  fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24)
  fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24)
  fanotify06.c:220: FAIL: group 3 got event
  fanotify06.c:220: FAIL: group 4 got event
  fanotify06.c:220: FAIL: group 5 got event
  fanotify06.c:220: FAIL: group 6 got event
  fanotify06.c:220: FAIL: group 7 got event
  fanotify06.c:220: FAIL: group 8 got event

  Summary:
  passed   9
  failed   9
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=1
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-16-generic 5.0.0-16.17
  ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 17 04:37 seq
   crw-rw 1 root audio 116, 33 Jun 17 04:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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:
  CurrentDmesg:
   
  Date: Mon Jun 17 04:40:18 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-5.0.0-16-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.178.1
  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/1833028/+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 1833028] [NEW] fanotify06 from ubuntu_ltp_syscalls failed

2019-06-16 Thread Po-Hsu Lin
Public bug reported:

This is a new test for overlayfs:
<<>>
tag=fanotify06 stime=1560747299
cmdline="fanotify06"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
mke2fs 1.44.6 (5-Mar-2019)
tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s
fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark
fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15
fanotify06.c:147: PASS: group 1 got event: mask 2 pid=1136 fd=15
fanotify06.c:147: PASS: group 2 got event: mask 2 pid=1136 fd=15
fanotify06.c:230: PASS: group 3 got no event
fanotify06.c:230: PASS: group 4 got no event
fanotify06.c:230: PASS: group 5 got no event
fanotify06.c:230: PASS: group 6 got no event
fanotify06.c:230: PASS: group 7 got no event
fanotify06.c:230: PASS: group 8 got no event
fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24)
fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24)
fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24)
fanotify06.c:220: FAIL: group 3 got event
fanotify06.c:220: FAIL: group 4 got event
fanotify06.c:220: FAIL: group 5 got event
fanotify06.c:220: FAIL: group 6 got event
fanotify06.c:220: FAIL: group 7 got event
fanotify06.c:220: FAIL: group 8 got event

Summary:
passed   9
failed   9
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=3 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=1
<<>>

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-16-generic 5.0.0-16.17
ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jun 17 04:37 seq
 crw-rw 1 root audio 116, 33 Jun 17 04:37 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27
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:
CurrentDmesg:
 
Date: Mon Jun 17 04:40:18 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-5.0.0-16-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-16-generic N/A
 linux-backports-modules-5.0.0-16-generic  N/A
 linux-firmware1.178.1
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

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Status: Incomplete


** Tags: 5.0 amd64 apport-bug disco ubuntu-ltp-syscalls uec-images

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

** Tags added: 5.0 ubuntu-ltp-syscalls

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  fanotify06 from ubuntu_ltp_syscalls failed

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

Bug description:
  This is a new test for overlayfs:
  <<>>
  tag=fanotify06 stime=1560747299
  cmdline="fanotify06"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s
  fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark
  fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15
  fanotify06.c:147: PASS: group 1 got event: mask 2 pid=1136 fd=15
  fanotify06.c:147: PASS: group 2 got event: mask 2 pid=1136 fd=15
  fanotify06.c:230: PASS: group 3 got no event
  

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

2019-06-16 Thread Po-Hsu Lin
** Tags removed: 5.0.0
** Tags added: 5.0 ubuntu-kvm-unit-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/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:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed

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: 

[Kernel-packages] [Bug 1830316] Re: ksm06* from mm test suite in LTP failed on D

2019-06-16 Thread Po-Hsu Lin
These tests have passed on node amaura, not naunamm.
Need to check if this is hw-specific.

** Tags added: 5.0 disco oem-osp1 ubuntu-ltp

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

Title:
  ksm06* from mm test suite in LTP failed on D

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

Bug description:
  Issue found on node "grumman".

  Test failed with:
  Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: 
EBUSY

   startup='Thu May 23 14:41:43 2019'
   tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
   safe_file_ops.c:301: BROK: Failed to close FILE 
'/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   tag=ksm06 stime=1558622503 dur=0 exit=exited stat=2 core=no cu=0 cs=0
   

   startup='Thu May 23 14:41:44 2019'
   tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
   safe_file_ops.c:301: BROK: Failed to close FILE 
'/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   tag=ksm06_1 stime=1558622504 dur=0 exit=exited stat=2 core=no cu=0 cs=1
   

   startup='Thu May 23 14:41:44 2019'
   tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
   safe_file_ops.c:301: BROK: Failed to close FILE 
'/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   tag=ksm06_2 stime=1558622504 dur=1 exit=exited stat=2 core=no cu=0 cs=25

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830316/+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 1829812] Re: Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case fails to build on disco

2019-06-16 Thread Po-Hsu Lin
This is affecting OEM-OSP1 (5.0.0-1009.10-oem-osp1) as well, we might
need to rebase this fix to it.

-- 
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:
  Fix Committed
Status in linux-aws source package in Disco:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  [SRU Justification]

  == Impact ==
  Some upstream stable change modified the bpf selftest to use a function that 
probes for existing eBPF program types. However that function does not exist in 
the 5.0 kernel sources.

  == Fix ==
  Picking two additional changes from upstream (which only modify the tools 
sub-directory), allows to compile the selftests again.

  == Risk of Regression ==
  Since the kernel itself is not touched, the risk is low.

  == Testcase ==
  With build-essential installed and the Disco kernel tree cloned:

  cd tools/testing/selftests/
  TARGET=net make

  ---

  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 

[Kernel-packages] [Bug 1830584] Re: mkswap01_sh from commands test suite in LTP failed

2019-06-14 Thread Po-Hsu Lin
** Tags added: ubunut-ltp

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

Title:
  mkswap01_sh from commands test suite in LTP failed

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

Bug description:
  Test failed with file check timeout:
  mkswap01 8 TBROK: "check_for_file 
/dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out

  
  <<>>
  tag=mkswap01_sh stime=1558936352
  cmdline="mkswap01.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  mkswap01 1 TINFO: timeout per run is 0h 5m 0s
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop3'
  mkswap01 1 TPASS: 'mkswap   /dev/loop3 ' passed.
  mkswap01 2 TPASS: 'mkswap   /dev/loop3 262140' passed.
  mkswap01 3 TINFO: Can not do swapon on /dev/loop3.
  mkswap01 3 TINFO: Device size specified by 'mkswap' greater than real size.
  mkswap01 3 TINFO: Swapon failed expectedly.
  mkswap01 3 TPASS: 'mkswap -f  /dev/loop3 262148' passed.
  mkswap01 4 TPASS: 'mkswap -c  /dev/loop3 ' passed.
  mkswap01 5 TINFO: Can not do swapon on /dev/loop3.
  mkswap01 5 TINFO: Page size specified by 'mkswap -p' is not equal to system's 
page size.
  mkswap01 5 TINFO: Swapon failed expectedly.
  mkswap01 5 TPASS: 'mkswap -p 2048 /dev/loop3 ' passed.
  mkswap01 6 TPASS: 'mkswap -L ltp_testswap /dev/loop3 ' passed.
  mkswap01 7 TPASS: 'mkswap -v1  /dev/loop3 ' passed.
  mkswap01 8 TBROK: "check_for_file 
/dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out
  mkswap01 8 TINFO: AppArmor enabled, this may affect test results
  mkswap01 8 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
  mkswap01 8 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   7
  failed   0
  skipped  0
  warnings 0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 27 05:39 seq
   crw-rw 1 root audio 116, 33 May 27 05:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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: Mon May 27 05:53:16 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  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/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830584/+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 1830584] Re: mkswap01_sh from commands test suite in LTP failed

2019-06-14 Thread Po-Hsu Lin
Tested with Apparmor removed, this issue will gone.

mkswap01 1 TINFO: timeout per run is 0h 5m 0s
tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop0'
mkswap01 1 TPASS: 'mkswap   /dev/loop0 ' passed.
mkswap01 2 TPASS: 'mkswap   /dev/loop0 262140' passed.
mkswap01 3 TINFO: Can not do swapon on /dev/loop0.
mkswap01 3 TINFO: Device size specified by 'mkswap' greater than real size.
mkswap01 3 TINFO: Swapon failed expectedly.
mkswap01 3 TPASS: 'mkswap -f  /dev/loop0 262148' passed.
mkswap01 4 TPASS: 'mkswap -c  /dev/loop0 ' passed.
mkswap01 5 TINFO: Can not do swapon on /dev/loop0.
mkswap01 5 TINFO: Page size specified by 'mkswap -p' is not equal to system's 
page size.
mkswap01 5 TINFO: Swapon failed expectedly.
mkswap01 5 TPASS: 'mkswap -p 2048 /dev/loop0 ' passed.
mkswap01 6 TPASS: 'mkswap -L ltp_testswap /dev/loop0 ' passed.
mkswap01 7 TPASS: 'mkswap -v1  /dev/loop0 ' passed.
mkswap01 8 TPASS: 'mkswap -U 8ae72224-45b9-484c-999a-72a9e9a2a803 /dev/loop0 ' 
passed.
mkswap01 9 TPASS: 'mkswap -V  /dev/loop0 ' passed.
mkswap01 10 TPASS: 'mkswap -h  /dev/loop0 ' passed.

As we have apparmor enabled by default, this can be ignored.

However we will need to figure out how to do this from the test suite.

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

Title:
  mkswap01_sh from commands test suite in LTP failed

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

Bug description:
  Test failed with file check timeout:
  mkswap01 8 TBROK: "check_for_file 
/dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out

  
  <<>>
  tag=mkswap01_sh stime=1558936352
  cmdline="mkswap01.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  mkswap01 1 TINFO: timeout per run is 0h 5m 0s
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop3'
  mkswap01 1 TPASS: 'mkswap   /dev/loop3 ' passed.
  mkswap01 2 TPASS: 'mkswap   /dev/loop3 262140' passed.
  mkswap01 3 TINFO: Can not do swapon on /dev/loop3.
  mkswap01 3 TINFO: Device size specified by 'mkswap' greater than real size.
  mkswap01 3 TINFO: Swapon failed expectedly.
  mkswap01 3 TPASS: 'mkswap -f  /dev/loop3 262148' passed.
  mkswap01 4 TPASS: 'mkswap -c  /dev/loop3 ' passed.
  mkswap01 5 TINFO: Can not do swapon on /dev/loop3.
  mkswap01 5 TINFO: Page size specified by 'mkswap -p' is not equal to system's 
page size.
  mkswap01 5 TINFO: Swapon failed expectedly.
  mkswap01 5 TPASS: 'mkswap -p 2048 /dev/loop3 ' passed.
  mkswap01 6 TPASS: 'mkswap -L ltp_testswap /dev/loop3 ' passed.
  mkswap01 7 TPASS: 'mkswap -v1  /dev/loop3 ' passed.
  mkswap01 8 TBROK: "check_for_file 
/dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out
  mkswap01 8 TINFO: AppArmor enabled, this may affect test results
  mkswap01 8 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
  mkswap01 8 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   7
  failed   0
  skipped  0
  warnings 0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 27 05:39 seq
   crw-rw 1 root audio 116, 33 May 27 05:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  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: Mon May 27 05:53:16 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  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/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 1798185] Re: Enable CONFIG_INFINIBAND_USER_MAD

2019-06-13 Thread Po-Hsu Lin
I can see this in Disco too, mark this as Fix-released.

** Changed in: linux-azure (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Enable CONFIG_INFINIBAND_USER_MAD

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released

Bug description:
  Please enable CONFIG_INFINIBAND_USER_MAD in the linux-azure kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1798185/+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 1711230] Re: linux-azure: enable DAX config options

2019-06-13 Thread Po-Hsu Lin
** Changed in: linux-azure (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  linux-azure: enable DAX config options

Status in linux-azure package in Ubuntu:
  Fix Released

Bug description:
  Please enable requested kernel config options for DAX support:

  CONFIG_DEV_DAX
  CONFIG_BLK_DEV_PMEM
  CONFIG_OVERLAY_FS_REDIRECT_DIR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1711230/+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 1832634] Re: libhugetlbfs FAIL small_const is not hugepage

2019-06-12 Thread Po-Hsu Lin
s/enabled/disabled/ in comment #2

https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=2208088acc770d820fd57a6960ae9b2db8bdb08a

Tests disabled.

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

** Changed in: ubuntu-kernel-tests
   Importance: Undecided => Medium

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

Title:
  libhugetlbfs FAIL small_const is not hugepage

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  Invalid

Bug description:
  Series: Eoan
  Kernel: 5.2.0-4.5-generic
  Metal Or Clouds Affected: (Bare Metal Intel) & AWS
  Instance Type: Any

  This bug has been seen in prior series, however not really officially tracked 
 and followed up on. We will do that here. 
   
  libhugetlbfs fails with the following.

  06/12 18:56:14 DEBUG| utils:0153| [stdout] linkhuge_rw (2M: 64):  PASS
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R linkhuge_rw 
(2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W linkhuge_rw 
(2M: 64):
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW linkhuge_rw 
(2M: 64):FAILsmall_data is not hugepage
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=no linkhuge_rw 
(2M: 64):PASS
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64): FAILsmall_const is not 
hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64): FAILsmall_data is not hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=R linkhuge_rw (2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=R linkhuge_rw (2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64):
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64):
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=RW linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=RW linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64): 
PASS

  Full logs attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1832634/+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 1832634] Re: libhugetlbfs FAIL small_const is not hugepage

2019-06-12 Thread Po-Hsu Lin
Test should be enabled.

We can copy forward the blacklist file.
$ find ./ -name blacklist.disco
./libhugetlbfs/blacklist.disco
./ubuntu_seccomp/blacklist.disco
./ubuntu_ecryptfs/blacklist.disco


** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => Invalid

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

Title:
  libhugetlbfs FAIL small_const is not hugepage

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  Invalid

Bug description:
  Series: Eoan
  Kernel: 5.2.0-4.5-generic
  Metal Or Clouds Affected: (Bare Metal Intel) & AWS
  Instance Type: Any

  This bug has been seen in prior series, however not really officially tracked 
 and followed up on. We will do that here. 
   
  libhugetlbfs fails with the following.

  06/12 18:56:14 DEBUG| utils:0153| [stdout] linkhuge_rw (2M: 64):  PASS
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R linkhuge_rw 
(2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W linkhuge_rw 
(2M: 64):
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW linkhuge_rw 
(2M: 64):FAILsmall_data is not hugepage
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=no linkhuge_rw 
(2M: 64):PASS
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64): FAILsmall_const is not 
hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64): FAILsmall_data is not hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=R linkhuge_rw (2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=R linkhuge_rw (2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64):
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64):
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=RW linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=RW linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64): 
PASS

  Full logs attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1832634/+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 1387334] Re: linux: Add unionmount-testsuite to dep8 testing

2019-06-12 Thread Po-Hsu Lin
https://kernel.ubuntu.com/git/ubuntu/kernel-
testing.git/commit/?id=b3d5992b1cc2efc42be5906faf26029b89b0ea3a

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

** Changed in: linux (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  linux: Add unionmount-testsuite to dep8 testing

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Won't Fix

Bug description:
  https://lkml.org/lkml/2014/5/29/818

  git://git.infradead.org/users/dhowells/unionmount-testsuite.git

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1387334/+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 1830011] Re: cve-2017-17053 from cve test suite in LTP failed

2019-06-12 Thread Po-Hsu Lin
It's confirmed that this is caused by the block_dev test from
kernel_misc, suggestion from upstream is to run this test separately.

A test shows this can be fix if we move the kernel_misc test to the end.

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Cosmic)

** Tags added: ubuntu-ltp-syscalls

** Tags removed: ubuntu-ltp-syscalls
** Tags added: ubuntu-ltp

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

Title:
  cve-2017-17053 from cve test suite in LTP failed

Status in ubuntu-kernel-tests:
  Fix Released

Bug description:
  This CVE (2017-17053)[1] has been fixed in our kernels

  However the cve-2017-17053 test in CVE test suite from LTP will complain that:
   tag=cve-2017-17053 stime=1558483177
   cmdline="cve-2017-17053"
   contacts=""
   analysis=exit
   <<>> 
   tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
   tst_taint.c:88: BROK: Kernel is already tainted: 14849

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   <<>>

  This is because there are some other tests failed before this one, and
  taints the kernel.


  [1] https://people.canonical.com/~ubuntu-
  security/cve/2017/CVE-2017-17053.html

  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 09:49:10 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/1830011/+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 1812176] Re: psock_tpacket from the net test in ubuntu_kernel_selftests fail on KVM kernels

2019-06-12 Thread Po-Hsu Lin
After discussed with Kamal, we're not going to enable this for the KVM
kernel.

This test should be skipped if KALLSYMS was not enabled.

Patch sent to upstream:
https://lore.kernel.org/linux-kselftest/20190612064752.6701-1-po-hsu@canonical.com/T/#u

** Tags added: cosmic disco xenial

** Tags added: ubuntu-kernel-selftests

** Summary changed:

- psock_tpacket from the net test in ubuntu_kernel_selftests fail on KVM kernels
+ psock_tpacket from the net test in ubuntu_kernel_selftests failed on KVM 
kernels

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

Title:
  psock_tpacket from the net test in ubuntu_kernel_selftests failed on
  KVM kernels

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

Bug description:
  The psock_tpacket in the net test from ubuntu_kernel_selftests failed with 
B-KVM
  $ sudo ./psock_tpacket 
  test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory

  Look into the code, it seems that this file not found error is caused
  by the attempt to access /proc/kallsyms in test_kernel_bit_width():

  static int test_kernel_bit_width(void)
  {
char in[512], *ptr;
int num = 0, fd;
ssize_t ret;

fd = open("/proc/kallsyms", O_RDONLY);
if (fd == -1) {
perror("open");
exit(1);
}

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 08:05:47 2019
  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/1812176/+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 1809704] Re: efivarfs test in ubuntu_kernel_selftest failed on the second run

2019-06-11 Thread Po-Hsu Lin
C/D:
  * dff6d2ae56d0056261e2f7b19c4b96b86b893cd8
X/B:
  * 1f0ea95853bd55a1812f2903b2f776853069f21f
  * dff6d2ae56d0056261e2f7b19c4b96b86b893cd8

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

Title:
  efivarfs test in ubuntu_kernel_selftest failed on the second run

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  New

Bug description:
  This seems to be an issue to the test case, if you run the test suite
  twice, it will fail on the second run.

  The first run will create the test file:
  $ ll 
/sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27
  -rw--- 1 root root 0 Dec 24 07:16 
/sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27

  This is cause the open(O_WRONLY) test in test_create_read failed with 
premission denied on the second run.
  This issue can be reproduced with upstream kernel tree on Xenial as well.

  $ sudo make -C linux/tools/testing/selftests TARGETS=efivarfs run_tests
  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  for TARGET in efivarfs; do \
   make -C $TARGET; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  for TARGET in efivarfs; do \
   make -C $TARGET run_tests; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  
  running test_create
  
  ./efivarfs.sh: line 48: 
/sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: 
Permission denied
    [PASS]
  
  running test_create_empty
  
  ./efivarfs.sh: line 65: 
/sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27:
 Permission denied
    [PASS]
  
  running test_create_read
  
  open(O_WRONLY): Permission denied
    [FAIL]
  
  running test_delete
  
    [PASS]
  
  running test_zero_size_delete
  
    [PASS]
  
  running test_open_unlink
  
    [PASS]
  
  running test_valid_filenames
  
    [PASS]
  
  running test_invalid_filenames
  
    [PASS]
  selftests: efivarfs.sh [FAIL]
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-141-generic 4.4.0-141.167
  ProcVersionSignature: User Name 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 24 05:10 seq
   crw-rw 1 root audio 116, 33 Dec 24 05:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [92859.670497] smpboot: CPU 111 is now offline
   [92859.723040] kvm: disabled by bios
   [92859.750562] smpboot: Booting Node 1 Processor 111 APIC 0x7d
   [92859.821706] kvm: disabled by bios
  Date: Tue Dec 25 06:30:01 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp.
   Bus 001 Device 002: ID :0001
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation S2600WFT
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic.efi.signed 
root=UUID=e93f24ed-4e90-4ccb-ba6d-f3b97fe0436f ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-141-generic N/A
   linux-backports-modules-4.4.0-141-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present 

[Kernel-packages] [Bug 1729021] Re: lack of random bits on linux-kvm

2019-06-11 Thread Po-Hsu Lin
** Changed in: linux-kvm (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  lack of random bits on linux-kvm

Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Xenial:
  Fix Released

Bug description:
  The linux-kvm is missing a random source; there's a distinct lack of
  entropy on the system as discovered by finding out bugs in netplan,
  cloud-init, etc.

  Please enable at least CONFIG_HW_RANDOM, CONFIG_HW_RANDOM_VIRTIO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1729021/+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 1820157] Re: CONFIG_CIFS_POSIX=y needs to added to xenial/kvm kernel config

2019-06-11 Thread Po-Hsu Lin
** Changed in: linux-kvm (Ubuntu)
   Status: New => Fix Released

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

Title:
   CONFIG_CIFS_POSIX=y needs to added to xenial/kvm kernel config

Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Xenial:
  Fix Released

Bug description:
  For xenial/kvm, we need a commit equivalent to
  d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1820157/+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 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM

2019-06-11 Thread Po-Hsu Lin
For D/linux-kvm https://lists.ubuntu.com/archives/kernel-
team/2019-June/101294.html

** 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/1812624

Title:
  PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
  was expected to be set in C-KVM

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-aws source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-kvm source package in Cosmic:
  Fix Released
Status in linux-aws source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-kvm source package in Disco:
  In Progress

Bug description:
  Issue reported by the kernel-security test:

    ==
    FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
    Ensure page poisoning is enabled (LP: #1783651)
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 2676, in 
test_420_config_page_poisoning
    self.assertKernelConfig('PAGE_POISONING', expected)
  File "./test-kernel-security.py", line 207, in assertKernelConfig
    self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
    '%s option was expected to be set in the kernel config' % name)
    AssertionError: PAGE_POISONING option was expected to be set in the kernel 
config

  
==
FAIL: test_421_config_page_poisoning_no_sanity 
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2694, in 
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
  File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in 
the kernel config

==
FAIL: test_421_config_page_poisoning_zero 
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2685, in 
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
  File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the 
kernel config


  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
  ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
  Uname: Linux 4.18.0-1006-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Jan 21 08:12:54 2019
  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/1812624/+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 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM

2019-06-10 Thread Po-Hsu Lin
https://lists.ubuntu.com/archives/kernel-team/2019-June/101275.html

** Tags removed: ppc64el
** Tags added: amd64 cosmic disco ubuntu-kernel-security

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

Title:
  test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
  on B/C/D KVM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Bionic:
  In Progress
Status in linux-kvm source package in Cosmic:
  In Progress
Status in linux-kvm source package in Disco:
  In Progress

Bug description:
  == SRU Justification ==
  Security team requires the CONFIG_LOCK_DOWN_KERNEL to be enabled in all of 
our kernels.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1811981-kvm-lockdown/
  This issue can be verified with test_410_config_lock_down_kernel
  test from q-r-t, the test will pass with the patched kernel.

  == Regression Potential ==
  Low, we already have this config enabled in the generic kernel.

  
  == Original bug report ==
  Kernel Version: 4.15.0-44.47

  This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
  Power8 and Power9

  FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
  Ensure kernel efi lockdown is enabled
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2668, in 
test_410_config_lock_down_kernel
  self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
    File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel 
config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1811981/+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 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM

2019-06-10 Thread Po-Hsu Lin
** Description changed:

+ == SRU Justification ==
+ Security team requires the CONFIG_LOCK_DOWN_KERNEL to be enabled in all of 
our kernels.
+ 
+ == Test ==
+ Test kernels could be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1811981-kvm-lockdown/
+ This issue can be verified with test_410_config_lock_down_kernel
+ test from q-r-t, the test will pass with the patched kernel.
+ 
+ == Regression Potential ==
+ Low, we already have this config enabled in the generic kernel.
+ 
+ 
+ == Original bug report ==
  Kernel Version: 4.15.0-44.47
  
  This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
  Power8 and Power9
  
  FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
  Ensure kernel efi lockdown is enabled
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2668, in 
test_410_config_lock_down_kernel
  self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
    File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel 
config

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

Title:
  test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
  on B/C/D KVM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Bionic:
  In Progress
Status in linux-kvm source package in Cosmic:
  In Progress
Status in linux-kvm source package in Disco:
  In Progress

Bug description:
  == SRU Justification ==
  Security team requires the CONFIG_LOCK_DOWN_KERNEL to be enabled in all of 
our kernels.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1811981-kvm-lockdown/
  This issue can be verified with test_410_config_lock_down_kernel
  test from q-r-t, the test will pass with the patched kernel.

  == Regression Potential ==
  Low, we already have this config enabled in the generic kernel.

  
  == Original bug report ==
  Kernel Version: 4.15.0-44.47

  This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
  Power8 and Power9

  FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
  Ensure kernel efi lockdown is enabled
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2668, in 
test_410_config_lock_down_kernel
  self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
    File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel 
config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1811981/+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 1831873] Re: test_095_kernel_symbols_missing_proc_net_tcp from ubuntu_qrt_kernel_security failed on B/C KVM

2019-06-10 Thread Po-Hsu Lin
Thanks for the quick fix, tested on a KVM node and this cannot be
reproduced.

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

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

Title:
  test_095_kernel_symbols_missing_proc_net_tcp from
  ubuntu_qrt_kernel_security failed on B/C KVM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid

Bug description:
  This issue can only be reproduced on the first run. The second run it
  will pass.

ERROR: test_095_kernel_symbols_missing_proc_net_tcp 
(__main__.KernelSecurityTest)
kernel addresses in /proc/net/tcp are zeroed out
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1392, in 
test_095_kernel_symbols_missing_proc_net_tcp
self._check_pK_files(self. _095_kernel_symbols_missing_proc_net_tcp)
  File "./test-kernel-security.py", line 1235, in _check_pK_files
test_function(expected_unrestricted)
  File "./test-kernel-security.py", line 1350, in 
_095_kernel_symbols_missing_proc_net_tcp
expected)
  File "./test-kernel-security.py", line 1153, in _read_twice
self.assertFalse(0 == int(address, 16), "%s: root saw %s - 
contents:\n%s" % (filename, address, root))
ValueError: invalid literal for int() with base 16: '(ptrval)'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1013-kvm 4.18.0-1013.13
  ProcVersionSignature: User Name 4.18.0-1013.13-kvm 4.18.20
  Uname: Linux 4.18.0-1013-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Thu Jun  6 09:25:10 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1831873/+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 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8

2019-06-10 Thread Po-Hsu Lin
Status change as per request in comment #25

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

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

Title:
  kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 
1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can 
no longer boot with the 4.15.0-50 kernel installed with 1804.
  We tried various kernel flags without luck, and installed latest 4.18.0-20 
from HWE and got the same result.
  Unfortunately, no logs are created in /var/logs when the issue happens, and 
we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to 
get a backtrace in a photo.
  The issue happens consistently, i.e. the backtrace looks always the same just 
happens on different cores.
  Attached the boot-info output and the picture taken at the end of the kernel 
loading.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  steventang   2047 F pulseaudio
   /dev/snd/controlC0:  steventang   2047 F pulseaudio
   /dev/snd/controlC1:  steventang   2047 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870
  InstallationDate: Installed on 2019-05-28 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacPro5,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic 
root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-148-generic N/A
   linux-backports-modules-4.4.0-148-generic  N/A
   linux-firmware 1.173.6
  Tags:  bionic
  Uname: Linux 4.4.0-148-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MP51.88Z.0084.B00.1708080528
  dmi.board.asset.tag: 0
  dmi.board.name: Mac-F221BEC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F221BEC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
  dmi.product.name: MacPro5,1
  dmi.product.version: 0.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+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 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM

2019-06-10 Thread Po-Hsu Lin
** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-kvm (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-kvm (Ubuntu Bionic)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-kvm (Ubuntu Cosmic)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-kvm (Ubuntu Disco)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-kvm (Ubuntu Disco)
   Status: New => In Progress

** Changed in: linux-kvm (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: linux-kvm (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-kvm (Ubuntu)
   Status: New => In Progress

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

Title:
  test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
  on B/C/D KVM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Bionic:
  In Progress
Status in linux-kvm source package in Cosmic:
  In Progress
Status in linux-kvm source package in Disco:
  In Progress

Bug description:
  Kernel Version: 4.15.0-44.47

  This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
  Power8 and Power9

  FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
  Ensure kernel efi lockdown is enabled
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2668, in 
test_410_config_lock_down_kernel
  self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
    File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel 
config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1811981/+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   4   5   6   7   8   9   10   >