[Kernel-packages] [Bug 1836715] Re: selftests: Remove broken Power9 paste tests and fix compilation issue

2019-07-16 Thread Po-Hsu Lin
https://lists.ubuntu.com/archives/kernel-team/2019-July/102251.html


** Summary changed:

- selftests/powerpc: Remove Power9 paste tests
+ selftests: Remove broken Power9 paste tests and fix compilation issue

** Description changed:

- == SRU Justification
+ == SRU Justification ==
  With the Power9 copy_unaligned test removed in bug 1813118,
- we can now move forward and remove the broken paste_unaligned / 
paste_last_unaligned test in selftests/powerpc.
+ we can now move forward and remove the broken paste_unaligned /
+ paste_last_unaligned test in selftests/powerpc.
  
  From the commit message:
- Paste on POWER9 only works to accelerators and not on real memory. So 
these tests just generate a SIGILL.
+ Paste on POWER9 only works to accelerators and not on real memory.
+ So these tests just generate a SIGILL.
  
-  test: test_paste_unaligned
-  tags: git_version:unknown
-  !! child died by signal 4
-  failure: test_paste_unaligned
-  not ok 1..2 selftests: paste_unaligned [FAIL]
-  selftests: paste_last_unaligned
-  
-  test: test_paste_last_unaligned
-  tags: git_version:unknown
-  !! child died by signal 4
-  failure: test_paste_last_unaligned
-  not ok 1..3 selftests: paste_last_unaligned [FAIL]
-  selftests: alignment_handler
- 
+ Actual test output:
+ test: test_paste_unaligned
+ tags: git_version:unknown
+ !! child died by signal 4
+ failure: test_paste_unaligned
+ not ok 1..2 selftests: paste_unaligned [FAIL]
+ selftests: paste_last_unaligned
+ 
+ test: test_paste_last_unaligned
+ tags: git_version:unknown
+ !! child died by signal 4
+ failure: test_paste_last_unaligned
+ not ok 1..3 selftests: paste_last_unaligned [FAIL]
+ selftests: alignment_handler
  
  (On Power8 these two test will be skipped)
  
+ This patchset will also address the compilation intrduced by b2d35fa
+ (selftests: add headers_install to lib.mk) which landed with Bionic
+ upstream stable patchset 2019-07-12 (bug 1836426)
+ 
  == Fix ==
  * 525661ef (selftests/powerpc: Remove Power9 paste tests)
+ * 7e0cf1c9 (selftests/powerpc: Fix Makefiles for headers_install change)
  
- As Cosmic will reach EOL soon, and we don't have alignment test in
- Xenial we only need this for Bionic.
+ These has been applied in Disco.
  
+ As Cosmic will reach EOL soon, and we don't have alignment tests in
+ Xenial, we only need this for Bionic.
  
  == Test ==
- Patch tested on a P9 node "baltar" and these two tests were removed as 
expected.
+ Patch tested on a P9 node "baltar" and these two tests were
+ removed as expected.
  
  Note that this patch will need to be tested with the fix (7e0cf1c9) in
  bug 1836720 altogether to solve the test compilation issue.
  
- 
  == Regression Potential ==
  Low.
- Code change limited to testing tools for Power9 and just removing broken 
tests.
+ Code change limited to testing tools for Power9 and just removing
+ broken tests, fix build error.
  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 16 07:48 seq
   crw-rw 1 root audio 116, 33 Jul 16 07:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  Date: Tue Jul 16 09:25:26 2019
  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.09 1.71 2.01 1/1354 43576
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 4640 00:17:508 0 EOF
   2: POSIX  ADVISORY  WRITE 4182 00:17:587 0 EOF
   3: POSIX  ADVISORY  WRITE 4092 00:17:578 0 EOF
   4: POSIX  ADVISORY  WRITE 1775 00:17:348 0 EOF
   5: FLOCK  ADVISORY  WRITE 4156 00:17:583 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-54-generic (buildd@bos02-ppc64el-002) (gcc 
version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 
10:54:50 UTC 2019
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1836720] Re: Fix selftests/powerpc compilation for headers_install change

2019-07-16 Thread Po-Hsu Lin
*** This bug is a duplicate of bug 1836715 ***
https://bugs.launchpad.net/bugs/1836715

I decided to combine this with bug 1836715

** This bug has been marked a duplicate of bug 1836715
   selftests/powerpc: Remove Power9 paste tests

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

Title:
  Fix selftests/powerpc compilation for headers_install change

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress

Bug description:
  == SRU Justification ==
  With Bionic upstream stable patchset 2019-07-12 (bug 1836426) applied in 
Bionic master-next, which brings upstream commit b2d35fa (selftests: add 
headers_install to lib.mk) and break some test compilations in selftests.

  == Fixes ==
  * 7e0cf1c9 (selftests/powerpc: Fix Makefiles for headers_install change)
  Note that the patch in bug 1836715 needs to be applied first.

  == Test ==
  Patch tested on a Power9 node "baltar", test can be complied successfully.

  == Regression Potential ==
  Low, it just fixes the compilation for testing tools.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836720/+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 1836720] [NEW] Fix selftests/powerpc compilation for headers_install change

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

== SRU Justification ==
With Bionic upstream stable patchset 2019-07-12 (bug 1836426) applied in Bionic 
master-next, which brings upstream commit b2d35fa (selftests: add 
headers_install to lib.mk) and break some test compilations in selftests.

== Fixes ==
* 7e0cf1c9 (selftests/powerpc: Fix Makefiles for headers_install change)
Note that the patch in bug 1836715 needs to be applied first.

== Test ==
Patch tested on a Power9 node "baltar", test can be complied successfully.

== Regression Potential ==
Low, it just fixes the compilation for testing tools.

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Po-Hsu Lin (cypressyew)
 Status: In Progress


** Tags: bionic

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

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

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

** Tags added: bionic

** Description changed:

  == SRU Justification ==
  With Bionic upstream stable patchset 2019-07-12 (bug 1836426) applied in 
Bionic master-next, which brings upstream commit b2d35fa (selftests: add 
headers_install to lib.mk) and break some test compilations in selftests.
  
  == Fixes ==
  * 7e0cf1c9 (selftests/powerpc: Fix Makefiles for headers_install change)
+ Note that the patch in bug 1836715 needs to be applied first.
  
  == Test ==
  Patch tested on a Power9 node "baltar", test can be complied successfully.
  
  == Regression Potential ==
  Low, it just fixes the compilation for testing tools.

** Summary changed:

- Fix selftests makefiles for headers_install change
+ Fix selftests/powerpc compilation for headers_install change

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

Title:
  Fix selftests/powerpc compilation for headers_install change

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress

Bug description:
  == SRU Justification ==
  With Bionic upstream stable patchset 2019-07-12 (bug 1836426) applied in 
Bionic master-next, which brings upstream commit b2d35fa (selftests: add 
headers_install to lib.mk) and break some test compilations in selftests.

  == Fixes ==
  * 7e0cf1c9 (selftests/powerpc: Fix Makefiles for headers_install change)
  Note that the patch in bug 1836715 needs to be applied first.

  == Test ==
  Patch tested on a Power9 node "baltar", test can be complied successfully.

  == Regression Potential ==
  Low, it just fixes the compilation for testing tools.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836720/+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 1836715] Re: selftests/powerpc: Remove Power9 paste tests

2019-07-16 Thread Po-Hsu Lin
** Description changed:

+ == SRU Justification
  With the Power9 copy_unaligned test removed in bug 1813118,
- we can now move forward and remove the broken paste_unaligned / 
paste_last_unaligned test in selftests/powerpc
+ we can now move forward and remove the broken paste_unaligned / 
paste_last_unaligned test in selftests/powerpc.
+ 
+ From the commit message:
+ Paste on POWER9 only works to accelerators and not on real memory. So 
these tests just generate a SIGILL.
+ 
+  test: test_paste_unaligned
+  tags: git_version:unknown
+  !! child died by signal 4
+  failure: test_paste_unaligned
+  not ok 1..2 selftests: paste_unaligned [FAIL]
+  selftests: paste_last_unaligned
+  
+  test: test_paste_last_unaligned
+  tags: git_version:unknown
+  !! child died by signal 4
+  failure: test_paste_last_unaligned
+  not ok 1..3 selftests: paste_last_unaligned [FAIL]
+  selftests: alignment_handler
+ 
+ 
+ (On Power8 these two test will be skipped)
+ 
+ == Fix ==
+ * 525661ef (selftests/powerpc: Remove Power9 paste tests)
+ 
+ As Cosmic will reach EOL soon, and we don't have alignment test in
+ Xenial we only need this for Bionic.
+ 
+ 
+ == Test ==
+ Patch tested on a P9 node "baltar" and these two tests were removed as 
expected.
+ 
+ Note that this patch will need to be tested with the fix (7e0cf1c9) in
+ bug 1836720 altogether to solve the test compilation issue.
+ 
+ 
+ == Regression Potential ==
+ Low.
+ Code change limited to testing tools for Power9 and just removing broken 
tests.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic ppc64le
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Jul 16 07:48 seq
-  crw-rw 1 root audio 116, 33 Jul 16 07:48 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Jul 16 07:48 seq
+  crw-rw 1 root audio 116, 33 Jul 16 07:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  Date: Tue Jul 16 09:25:26 2019
  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
+  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.09 1.71 2.01 1/1354 43576
  ProcLocks:
-  1: FLOCK  ADVISORY  WRITE 4640 00:17:508 0 EOF
-  2: POSIX  ADVISORY  WRITE 4182 00:17:587 0 EOF
-  3: POSIX  ADVISORY  WRITE 4092 00:17:578 0 EOF
-  4: POSIX  ADVISORY  WRITE 1775 00:17:348 0 EOF
-  5: FLOCK  ADVISORY  WRITE 4156 00:17:583 0 EOF
+  1: FLOCK  ADVISORY  WRITE 4640 00:17:508 0 EOF
+  2: POSIX  ADVISORY  WRITE 4182 00:17:587 0 EOF
+  3: POSIX  ADVISORY  WRITE 4092 00:17:578 0 EOF
+  4: POSIX  ADVISORY  WRITE 1775 00:17:348 0 EOF
+  5: FLOCK  ADVISORY  WRITE 4156 00:17:583 0 EOF
  ProcSwaps:
-  Filename TypeSizeUsedPriority
-  /swap.img   file 8388544 0   -2
+  Filename TypeSizeUsedPriority
+  /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-54-generic (buildd@bos02-ppc64el-002) (gcc 
version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 
10:54:50 UTC 2019
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-54-generic N/A
-  linux-backports-modules-4.15.0-54-generic  N/A
-  linux-firmware 1.173.8
+  linux-restricted-modules-4.15.0-54-generic N/A
+  linux-backports-modules-4.15.0-54-generic  N/A
+  linux-firmware 1.173.8
  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 = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
-  min: 2.862 GHz (cpu 79)
-  max: 2.945 GHz (cpu 81)
-  

[Kernel-packages] [Bug 1813118] Re: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9

2019-07-16 Thread Po-Hsu Lin
The copy_unaligned test was removed as expected.

** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1813118

Title:
  alignment test in powerpc from ubuntu_kernel_selftests failed on B/C
  Power9

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

Bug description:
  == Justification ==
  The copy_unaligned / paste_unaligned / paste_last_unaligned test in 
powerpc/alignment will fail on a Power9 node as which implements ISA 3.0B, but 
the test was designed base on ISA 3.0.

  From the commit message:
  This is a test of the ISA 3.0 "copy" instruction. That instruction has
  an L field, which if set to 1 specifies that "the instruction
  identifies the beginning of a move group" (pp 858). That's also
  referred to as "copy first" vs "copy".

  In ISA 3.0B the copy instruction does not have an L field, and the
  corresponding bit in the instruction must be set to 1.

  This test is generating a "copy" instruction, not a "copy first", and
  so on Power9 (which implements 3.0B), this results in an illegal
  instruction.

  So just drop the test entirely. We still have copy_first_unaligned to
  test the "copy first" behaviour.

  == Fix ==
  * 83039f22 (selftests/powerpc: Remove Power9 copy_unaligned test)

  Patch can be cherry-picked into C, for Bionic it needs patches for bug
  1828935 to land first (8d191587) to make it a clean cherry-pick.

  It's already landed in D and onward.

  == Test ==
  Tested on a Power9 server with Cosmic, the broken tests will be removed 
correctly.

  == Regression Potential ==
  Low.
  Code change limited to testing tools and just removing broken tests. We still 
have copy_first_unaligned to test the "copy first" behaviour.

  == Original Bug Report ==
  This issue was only spotted on Power9 system "balter", for Power8 system, it 
has passed (skipped, and marked as passed) with this test:

   TAP version 13
   selftests: copy_unaligned
   
   test: test_copy_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_copy_unaligned
   not ok 1..1 selftests: copy_unaligned [FAIL]
   selftests: copy_first_unaligned
   
   test: test_copy_first_unaligned
   tags: git_version:unknown
   success: test_copy_first_unaligned
   ok 1..2 selftests: copy_first_unaligned [PASS]
   selftests: paste_unaligned
   
   test: test_paste_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_paste_unaligned
   not ok 1..3 selftests: paste_unaligned [FAIL]
   selftests: paste_last_unaligned
   
   test: test_paste_last_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_paste_last_unaligned
   not ok 1..4 selftests: paste_last_unaligned [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 06:50 seq
   crw-rw 1 root audio 116, 33 Jan 24 06:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  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:
  Date: Thu Jan 24 07:05:20 2019
  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: 1.24 0.89 0.66 3/1412 8319
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3876 00:17:569 0 EOF
   2: FLOCK  ADVISORY  WRITE 3556 00:17:497 0 EOF
   3: FLOCK  ADVISORY  WRITE 4090 00:17:596 0 EOF
   4: POSIX  ADVISORY  WRITE 3955 00:17:571 0 EOF
   5: POSIX  ADVISORY  WRITE 1823 00:17:348 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   

[Kernel-packages] [Bug 1836715] [NEW] selftests/powerpc: Remove Power9 paste tests

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

With the Power9 copy_unaligned test removed in bug 1813118,
we can now move forward and remove the broken paste_unaligned / 
paste_last_unaligned test in selftests/powerpc

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-54-generic 4.15.0-54.58
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic ppc64le
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 16 07:48 seq
 crw-rw 1 root audio 116, 33 Jul 16 07:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
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:
Date: Tue Jul 16 09:25:26 2019
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.09 1.71 2.01 1/1354 43576
ProcLocks:
 1: FLOCK  ADVISORY  WRITE 4640 00:17:508 0 EOF
 2: POSIX  ADVISORY  WRITE 4182 00:17:587 0 EOF
 3: POSIX  ADVISORY  WRITE 4092 00:17:578 0 EOF
 4: POSIX  ADVISORY  WRITE 1775 00:17:348 0 EOF
 5: FLOCK  ADVISORY  WRITE 4156 00:17:583 0 EOF
ProcSwaps:
 Filename   TypeSizeUsedPriority
 /swap.img   file   8388544 0   -2
ProcVersion: Linux version 4.15.0-54-generic (buildd@bos02-ppc64el-002) (gcc 
version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 
10:54:50 UTC 2019
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-54-generic N/A
 linux-backports-modules-4.15.0-54-generic  N/A
 linux-firmware 1.173.8
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 = 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

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Po-Hsu Lin (cypressyew)
 Status: In Progress


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

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

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

** Changed in: linux (Ubuntu Bionic)
   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/1836715

Title:
  selftests/powerpc: Remove Power9 paste tests

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress

Bug description:
  With the Power9 copy_unaligned test removed in bug 1813118,
  we can now move forward and remove the broken paste_unaligned / 
paste_last_unaligned test in selftests/powerpc

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 16 07:48 seq
   crw-rw 1 root audio 116, 33 Jul 16 07:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  Date: Tue Jul 16 09:25:26 2019
  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.09 1.71 2.01 1/1354 43576
  ProcLocks:
   1: FLOCK  ADVISORY 

[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.60 -proposed tracker

2019-07-16 Thread Po-Hsu Lin
 (bug 1775784) fanotify09-2 (bug 1804594) 
sync_file_range02 (bug 1819116)
  ubuntu_lxc - network issue 

50 / 52 tests were run, missing: ubuntu_btrfs_kernel_fixes, ubuntu_ltp
Issue to note in s390x (KVM):
  ubuntu_bpf - test_map failed (bug 1788562)
  ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) 
TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 
1811057)
  ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) 
sync_file_range02 (bug 1819116)

49 / 52 tests were run, missing: ubuntu_boot, ubuntu_btrfs_kernel_fixes, 
ubuntu_ltp
Issue to note in s390x (Ubuntu on LPAR):
  ubuntu_bpf - test_map failed (bug 1788562)
  ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) 
TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 
1811057)
  ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) 
sync_file_range02 (bug 1819116)
  ubuntu_lxc - lxc-test-api-reboot failed (bug 1776381) Container "reboot" is 
defined (bug 1788574)

49 / 52 tests were run, missing: ubuntu_boot, ubuntu_btrfs_kernel_fixes, 
ubuntu_ltp
Issue to note in s390x (zVM):
  ubuntu_bpf - test_map failed (bug 1788562)
  ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) 
TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 
1811057)
  ubuntu_kvm_unit_tests - skey failed (bug 1778705)
  ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) 
sync_file_range02 (bug 1819116)
  ubuntu_lxc - Container "reboot" is defined (bug 1788574)

Note: No xfstests for P9 as it does not have a scratch drive
Note: Missing ubuntu_btrfs_kernel_fixes for s390x (bug 1809860)

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1834954

Title:
  linux: 4.15.0-55.60 -proposed tracker

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

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

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

  backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 
(linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 
(linux-kvm), bug 1834941 (linux-ibm-gt), bug 1834943 (linux-oracle), bug 
1834944 (linux-fips), bug 1836172 (linux-oem)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 17:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834954/+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-07-16 Thread Po-Hsu Lin
** Tags removed: ubuntu-kernel-security
** Tags added: ubuntu-qrt-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:
  Fix Committed
Status in linux-kvm source package in Cosmic:
  Fix Committed
Status in linux-kvm source package in Disco:
  Fix Committed

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 1836694] Re: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic

2019-07-16 Thread Po-Hsu Lin
** Tags added: 4.15 sru-20190701 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/1836694

Title:
  memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with
  Bionic

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

Bug description:
  This failure could be found in the LTP test suite on a Moonshot ARM64
  node with B-4.15, but sometimes it will pass if you try to run it
  manually. (Sometimes not.)

  <<>>
  tag=memcg_test_3 stime=1563249678
  cmdline="memcg_test_3"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  Test timeouted, sending SIGKILL!
  tst_test.c:1140: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1141: BROK: Test killed! (timeout?)

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: 
unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: 
EPERM
  <<>>

  
  When it fails, the attempt to remove files will fail, and most of the 
cgroup_fj_* test will fail:
* cgroup_fj_function_memory
* cgroup_fj_stress_memory_10_3_each
* cgroup_fj_stress_memory_10_3_none
* cgroup_fj_stress_memory_10_3_one
* cgroup_fj_stress_memory_1_200_each
* cgroup_fj_stress_memory_1_200_none
* cgroup_fj_stress_memory_1_200_one
* cgroup_fj_stress_memory_200_1_each
* cgroup_fj_stress_memory_200_1_none
* cgroup_fj_stress_memory_200_1_one
* cgroup_fj_stress_memory_2_2_each
* cgroup_fj_stress_memory_2_2_none
* cgroup_fj_stress_memory_2_2_one
* cgroup_fj_stress_memory_2_9_each
* cgroup_fj_stress_memory_2_9_none
* cgroup_fj_stress_memory_2_9_one
* cgroup_fj_stress_memory_3_3_each
* cgroup_fj_stress_memory_3_3_none
* cgroup_fj_stress_memory_3_3_one
* cgroup_fj_stress_memory_4_4_each
* cgroup_fj_stress_memory_4_4_none
* cgroup_fj_stress_memory_4_4_one

  Steps to run this:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "memcg_test_3memcg_test_3" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 16 03:46 seq
   crw-rw 1 root audio 116, 33 Jul 16 03:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  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 Jul 16 04:16:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.173.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+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 1836694] Re: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic

2019-07-16 Thread Po-Hsu Lin
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with
  Bionic

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

Bug description:
  This failure could be found in the LTP test suite on a Moonshot ARM64
  node with B-4.15, but sometimes it will pass if you try to run it
  manually. (Sometimes not.)

  <<>>
  tag=memcg_test_3 stime=1563249678
  cmdline="memcg_test_3"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  Test timeouted, sending SIGKILL!
  tst_test.c:1140: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1141: BROK: Test killed! (timeout?)

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: 
unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: 
EPERM
  <<>>

  
  When it fails, the attempt to remove files will fail, and most of the 
cgroup_fj_* test will fail:
* cgroup_fj_function_memory
* cgroup_fj_stress_memory_10_3_each
* cgroup_fj_stress_memory_10_3_none
* cgroup_fj_stress_memory_10_3_one
* cgroup_fj_stress_memory_1_200_each
* cgroup_fj_stress_memory_1_200_none
* cgroup_fj_stress_memory_1_200_one
* cgroup_fj_stress_memory_200_1_each
* cgroup_fj_stress_memory_200_1_none
* cgroup_fj_stress_memory_200_1_one
* cgroup_fj_stress_memory_2_2_each
* cgroup_fj_stress_memory_2_2_none
* cgroup_fj_stress_memory_2_2_one
* cgroup_fj_stress_memory_2_9_each
* cgroup_fj_stress_memory_2_9_none
* cgroup_fj_stress_memory_2_9_one
* cgroup_fj_stress_memory_3_3_each
* cgroup_fj_stress_memory_3_3_none
* cgroup_fj_stress_memory_3_3_one
* cgroup_fj_stress_memory_4_4_each
* cgroup_fj_stress_memory_4_4_none
* cgroup_fj_stress_memory_4_4_one

  Steps to run this:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "memcg_test_3memcg_test_3" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 16 03:46 seq
   crw-rw 1 root audio 116, 33 Jul 16 03:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  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 Jul 16 04:16:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.173.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+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 1836694] [NEW] memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic

2019-07-15 Thread Po-Hsu Lin
Public bug reported:

This failure could be found in the LTP test suite on a Moonshot ARM64
node with B-4.15, but sometimes it will pass if you try to run it
manually. (Sometimes not.)

<<>>
tag=memcg_test_3 stime=1563249678
cmdline="memcg_test_3"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
Test timeouted, sending SIGKILL!
tst_test.c:1140: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
tst_test.c:1141: BROK: Test killed! (timeout?)

Summary:
passed   0
failed   0
skipped  0
warnings 0
tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: 
unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: 
EPERM
<<>>


When it fails, the attempt to remove files will fail, and most of the 
cgroup_fj_* test will fail:
  * cgroup_fj_function_memory
  * cgroup_fj_stress_memory_10_3_each
  * cgroup_fj_stress_memory_10_3_none
  * cgroup_fj_stress_memory_10_3_one
  * cgroup_fj_stress_memory_1_200_each
  * cgroup_fj_stress_memory_1_200_none
  * cgroup_fj_stress_memory_1_200_one
  * cgroup_fj_stress_memory_200_1_each
  * cgroup_fj_stress_memory_200_1_none
  * cgroup_fj_stress_memory_200_1_one
  * cgroup_fj_stress_memory_2_2_each
  * cgroup_fj_stress_memory_2_2_none
  * cgroup_fj_stress_memory_2_2_one
  * cgroup_fj_stress_memory_2_9_each
  * cgroup_fj_stress_memory_2_9_none
  * cgroup_fj_stress_memory_2_9_one
  * cgroup_fj_stress_memory_3_3_each
  * cgroup_fj_stress_memory_3_3_none
  * cgroup_fj_stress_memory_3_3_one
  * cgroup_fj_stress_memory_4_4_each
  * cgroup_fj_stress_memory_4_4_none
  * cgroup_fj_stress_memory_4_4_one

Steps to run this:
  git clone --depth=1 https://github.com/linux-test-project/ltp.git
  cd ltp; make autotools; ./configure; make; sudo make install
  echo "memcg_test_3memcg_test_3" > /tmp/jobs
  sudo /opt/ltp/runltp -f /tmp/jobs

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-54-generic 4.15.0-54.58
ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 16 03:46 seq
 crw-rw 1 root audio 116, 33 Jul 16 03:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: arm64
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 Jul 16 04:16:14 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-54-generic N/A
 linux-backports-modules-4.15.0-54-generic  N/A
 linux-firmware 1.173.8
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with
  Bionic

Status in linux package in Ubuntu:
  New

Bug description:
  This failure could be found in the LTP test suite on a Moonshot ARM64
  node with B-4.15, but sometimes it will pass if you try to run it
  manually. (Sometimes not.)

  <<>>
  tag=memcg_test_3 stime=1563249678
  cmdline="memcg_test_3"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  Test timeouted, sending SIGKILL!
  tst_test.c:1140: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1141: BROK: Test killed! (timeout?)

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: 
unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: 
EPERM
  <<>>

  
  When it fails, the attempt to remove files will fail, and most of the 
cgroup_fj_* test will fail:
* cgroup_fj_function_memory
* cgroup_fj_stress_memory_10_3_each
* cgroup_fj_stress_memory_10_3_none
* cgroup_fj_stress_memory_10_3_one
* cgroup_fj_stress_memory_1_200_each
* cgroup_fj_stress_memory_1_200_none
* cgroup_fj_stress_memory_1_200_one
* cgroup_fj_stress_memory_200_1_each
* cgroup_fj_stress_memory_200_1_none
* cgroup_fj_stress_memory_200_1_one
* cgroup_fj_stress_memory_2_2_each
* cgroup_fj_stress_memory_2_2_none
* cgroup_fj_stress_memory_2_2_one
* cgroup_fj_stress_memory_2_9_each
* 

[Kernel-packages] [Bug 1830682] Re: cve-2017-5754 from cve test suite in LTP failed with KVM kernel

2019-07-15 Thread Po-Hsu Lin
Didn't see this anymore, mark it as fix-released.

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

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

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

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 1835054] Re: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64

2019-07-15 Thread Po-Hsu Lin
V2 resubmitted. https://lists.ubuntu.com/archives/kernel-
team/2019-July/102171.html

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

Title:
  Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  == SRU Justification ==
  The mvpp2 is a driver for network controllers(s) in Marvell SOCs,
  particularly Armada 8040.

  However this driver was neither enabled as a module or a built-in for
  Disco arm64.

  == Fix ==
  Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can
  solve this problem.

  We need to enable the Armada SOCs support (CONFIG_ARCH_MVEBU) as well
  to meet the dependency requirement.

  Other configs were added by the updateconfigs process.

  == Test ==
  A test kernel for Disco ARM64 could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/V2/

  User has confirmed that the V1 kernel can fix this missing driver
  issue (V2 is just with CONFIG_ARCH_MULTI_V7 dropped and some configs
  added explicitly, I have it tested on an ARM64 node, the mvpp2 module
  can be loaded without any issue).

  == Regression Potential ==
  Low, this patch just enable the Armada SOCs and make this mvpp2 driver
  to be built as a module on ARM64, and we already have those for armhf.


  == Original Bug Report ==

  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a module or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+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-07-15 Thread Po-Hsu Lin
Fix applied upstream: ff95bf28c23490584b9d75913a520bb7bb1f2ecb

-- 
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 1834904] Re: linux: 4.18.0-26.27 -proposed tracker

2019-07-15 Thread Po-Hsu Lin
 1797341) 
sync_file_range02 (bug 1819116)

49 / 52 tests were run, missing: ubuntu_boot, ubuntu_btrfs_kernel_fixes, 
ubuntu_ltp
Issue to note in s390x (Ubuntu on LPAR):
  ubuntu_bpf - test_verifier in ubuntu_bpf test failed with 'Failed to load 
prog' on Cosmic s390x (bug 1801033)
  ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) 
run_netsocktests (bug 1830016) rtnetlink.sh in net (bug 1812978) psock_snd in 
net (bug 1812618) TRACE_syscall in ftrace (bug 1812824)
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 
1819116)
  ubuntu_lxc - lxc-test-api-reboot failed (bug 1776381) Container "reboot" is 
defined (bug 1788574)

49 / 52 tests were run, missing: ubuntu_boot, ubuntu_btrfs_kernel_fixes, 
ubuntu_ltp
Issue to note in s390x (zVM):
  ubuntu_bpf - test_verifier in ubuntu_bpf test failed with 'Failed to load 
prog' on Cosmic s390x (bug 1801033)
  ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) 
run_netsocktests (bug 1830016) rtnetlink.sh in net (bug 1812978) psock_snd in 
net (bug 1812618) TRACE_syscall in ftrace (bug 1812824)
  ubuntu_kvm_unit_tests - skey failed (bug 1778705)
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) msgstress03 (bug 1797341) 
sync_file_range02 (bug 1819116)
  ubuntu_lxc - Container "reboot" is defined (bug 1788574)

Note: No xfstests for P9 as it does not have a scratch drive
Note: Missing ubuntu_btrfs_kernel_fixes for s390x (bug 1809860)
Note: cgroup related failure in ltp/controllers seems to be caused by swapon 
failure, it can't be reproduced when you run the test directly


** Changed in: kernel-sru-workflow/regression-testing
   Status: Invalid => 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1834904

Title:
  linux: 4.18.0-26.27 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  derivatives: bug 1834880 (linux-raspi2), bug 1834883 (linux-aws), bug
  1834899 (linux-gcp), bug 1834901 (linux-kvm), bug 1835438 (linux-
  azure)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 20:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834904/+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 1836188] Re: cpuset_exclusive in controllers from ubuntu_ltp failed on C P9

2019-07-15 Thread Po-Hsu Lin
This is also affecting any script that's calling this cpuset_funcs.sh:
  * cpuset_base_ops
  * cpuset_exclusive
  * cpuset_hierarchy
  * cpuset_hotplug cpuset_inherit
  * cpuset_load_balance
  * cpuset_memory cpuset_memory_pressure
  * cpuset_memory_spread
  * cpuset_sched_domains
  * cpuset_syscall

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

Title:
  cpuset_exclusive in controllers from ubuntu_ltp failed on C P9

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

Bug description:
  This issue was only spotted on node Baltar (P9)

  This is caused by the return value in:
    $ cat /sys/devices/system/node/has_normal_memory
    0,8

  The test was trying to use do arithmetic operation with it, but didn't
  expect to get a return value with a comma in it.

  <<>>
  tag=cpuset_exclusive stime=1562844139
  cmdline="   cpuset_exclusive_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  /opt/ltp/testcases/bin/cpuset_exclusive_test.sh: 36: 
/opt/ltp/testcases/bin/cpuset_funcs.sh: arithmetic expression: expecting EOF: 
"0,8 + 1"
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  Not sure if this is a test case issue, or if we should see a comma in
  /sys/devices/system/node/has_normal_memory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 10:56 seq
   crw-rw 1 root audio 116, 33 Jul 11 10:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.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:
  Date: Thu Jul 11 11:25:40 2019
  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.74 1.52 0.74 1/1338 6264
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1805 00:17:364 0 EOF
   2: POSIX  ADVISORY  WRITE 3956 00:17:504 0 EOF
   3: FLOCK  ADVISORY  WRITE 3915 00:17:566 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.18.0-25-generic (buildd@bos02-ppc64el-009) (gcc 
version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10.1)) #26-Ubuntu SMP Mon Jun 24 
09:32:46 UTC 2019
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  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 = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 83)
   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-kernel-tests/+bug/1836188/+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 1835054] Re: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64

2019-07-15 Thread Po-Hsu Lin
** Description changed:

  == SRU Justification ==
- The mvpp2 is a driver for network controllers(s) in Marvell SOCs, 
particularly Armada 8040.
+ The mvpp2 is a driver for network controllers(s) in Marvell SOCs,
+ particularly Armada 8040.
  
  However this driver was neither enabled as a module or a built-in for
  Disco arm64.
  
  == Fix ==
- Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can solve 
this problem.
+ Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can
+ solve this problem.
  
- Corresponding configs like CONFIG_ARCH_MVEBU and CONFIG_ARCH_MULTI_V7
- need to be enabled as well to meet the dependency requirement.
+ We need to enable the Armada SOCs support (CONFIG_ARCH_MVEBU) as well
+ to meet the dependency requirement.
  
- CONFIG_CRYPTO_DEV_SAFEXCEL and CONFIG_PCI_AARDVARK are disabled
- explicitly to avoid interactive dialogues when building the kernel.
+ Other configs were added by the updateconfigs process.
  
  == Test ==
  A test kernel for Disco ARM64 could be found here:
- https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/
+ https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/V2/
  
- User has confirmed that the patched kernel can fix this missing driver
- issue.
+ User has confirmed that the V1 kernel can fix this missing driver
+ issue (V2 is just with CONFIG_ARCH_MULTI_V7 dropped and some configs
+ added explicitly, I have it tested on an ARM64 node, the mvpp2 module
+ can be loaded without any issue).
  
  == Regression Potential ==
- Low, this patch just make this driver to be built as a module, and we already 
have this enabled for armhf.
+ Low, this patch just enable the Armada SOCs and make this mvpp2 driver
+ to be built as a module on ARM64, and we already have those for armhf.
  
  
  == Original Bug Report ==
  
  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a module or a built-in:
  
  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic
  $
  
  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a
  reasonably priced and performant server/mini-desktop platform.
  
  Could it be added, please, and the installer image re-generated.

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

Title:
  Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  == SRU Justification ==
  The mvpp2 is a driver for network controllers(s) in Marvell SOCs,
  particularly Armada 8040.

  However this driver was neither enabled as a module or a built-in for
  Disco arm64.

  == Fix ==
  Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can
  solve this problem.

  We need to enable the Armada SOCs support (CONFIG_ARCH_MVEBU) as well
  to meet the dependency requirement.

  Other configs were added by the updateconfigs process.

  == Test ==
  A test kernel for Disco ARM64 could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/V2/

  User has confirmed that the V1 kernel can fix this missing driver
  issue (V2 is just with CONFIG_ARCH_MULTI_V7 dropped and some configs
  added explicitly, I have it tested on an ARM64 node, the mvpp2 module
  can be loaded without any issue).

  == Regression Potential ==
  Low, this patch just enable the Armada SOCs and make this mvpp2 driver
  to be built as a module on ARM64, and we already have those for armhf.


  == Original Bug Report ==

  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a module or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+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 1835054] Re: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64

2019-07-15 Thread Po-Hsu Lin
** Summary changed:

- Enable NIC driver for Armada SOCs in disco/generic arm64
+ Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64

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

Title:
  Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  == SRU Justification ==
  The mvpp2 is a driver for network controllers(s) in Marvell SOCs, 
particularly Armada 8040.

  However this driver was neither enabled as a module or a built-in for
  Disco arm64.

  == Fix ==
  Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can solve 
this problem.

  Corresponding configs like CONFIG_ARCH_MVEBU and CONFIG_ARCH_MULTI_V7
  need to be enabled as well to meet the dependency requirement.

  CONFIG_CRYPTO_DEV_SAFEXCEL and CONFIG_PCI_AARDVARK are disabled
  explicitly to avoid interactive dialogues when building the kernel.

  == Test ==
  A test kernel for Disco ARM64 could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/

  User has confirmed that the patched kernel can fix this missing driver
  issue.

  == Regression Potential ==
  Low, this patch just make this driver to be built as a module, and we already 
have this enabled for armhf.

  
  == Original Bug Report ==

  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a module or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+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 1775165] Re: fanotify07/fanotify08 in LTP syscall test generates kernel trace with T/X/X-AWS kernel

2019-07-14 Thread Po-Hsu Lin
Hi Matthew,

I think that's a valid point to mark this bug as a Won't Fix for X
(which applies to T as well).

Thanks for working on this one.
I will bring this to the LTP, to see if we can skip this one with older kernels.

** Changed in: linux (Ubuntu Trusty)
   Status: Triaged => Won't Fix

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

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Won't Fix

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

Title:
  fanotify07/fanotify08 in LTP syscall test generates kernel trace with
  T/X/X-AWS kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Won't Fix

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1775165

  [Impact]

  When userspace tasks which are processing fanotify permission events act 
  incorrectly, the fsnotify_mark_srcu SRCU is held indefinitely which causes
  the whole notification subsystem to hang. 

  This has been seen in production, and it can also be seen when running the 
  Linux Test Project testsuite, specifically fanotify07. 

  [Fix]

  Instead of holding the SRCU lock while waiting for userspace to respond, 
  which may never happen, or not in the order we are expecting, we drop the 
  fsnotify_mark_srcu SRCU lock before waiting for userspace response, and then 
  reacquire the lock again when userspace responds.

  The fixes are from a series of upstream commits:

  05f0e38724e8449184acd8fbf0473ee5a07adc6c (cherry-pick)
  9385a84d7e1f658bb2d96ab798393e4b16268aaa (backport)
  abc77577a669f424c5d0c185b9994f2621c52aa4 (backport)

  The following are upstream commits necessary for the fixes to
  function:

  35e481761cdc688dbee0ef552a13f49af8eba6cc (backport)
  0918f1c309b86301605650c836ddd2021d311ae2 (cherry-pick)

  [Testcase]

  You can reproduce the problem pretty quickly with the Linux Test
  Project:

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. cd /opt/ltp
8. echo -e "fanotify07 fanotify07 \nfanotify08 fanotify08" > /tmp/jobs
9. ./runltp -f /tmp/jobs

  On a stock Xenial kernel, the system will hang, and the testcase will look 
like:

  <<>>
  tag=fanotify07 stime=1554326200
  cmdline="fanotify07 "
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Cannot kill test processes!
  Congratulation, likely test hit a kernel bug.
  Exitting uncleanly...
  <<>>
  initiation_status="ok"
  duration=350 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  Looking at dmesg, we see the following call stack

  [  790.772792] LTP: starting fanotify07 (fanotify07 )
  [  960.140455] INFO: task fsnotify_mark:36 blocked for more than 120 seconds.
  [  960.140867]   Not tainted 4.4.0-142-generic #168-Ubuntu
  [  960.141185] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  960.141498] fsnotify_mark   D 8800b6703c98 036  2 
0x
  [  960.141516]  8800b6703c98 88013a558a00 8800b7797000 
8800b66f8000
  [  960.141524]  8800b6704000 7fff 8800b6703de0 
8800b66f8000
  [  960.141528]   8800b6703cb0 8185cb45 
8800b6703de8
  [  960.141532] Call Trace:
  [  960.141580]  [] schedule+0x35/0x80
  [  960.141588]  [] schedule_timeout+0x1b4/0x270
  [  960.141617]  [] ? mod_timer+0x10c/0x240
  [  960.141621]  [] ? __schedule+0x30d/0x810
  [  960.141625]  [] wait_for_completion+0xb2/0x190
  [  960.141636]  [] ? wake_up_q+0x70/0x70
  [  960.141641]  [] __synchronize_srcu+0x100/0x1a0
  [  960.141645]  [] ? 
trace_raw_output_rcu_utilization+0x60/0x60
  [  960.141664]  [] ? fsnotify_put_mark+0x40/0x40
  [  960.141669]  [] synchronize_srcu+0x24/0x30
  [  960.141672]  [] fsnotify_mark_destroy+0x84/0x130
  [  960.141680]  [] ? wake_atomic_t_function+0x60/0x60
  [  960.141691]  [] kthread+0xe7/0x100
  [  960.141694]  [] ? __schedule+0x301/0x810
  [  960.141699]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  960.141703]  [] ret_from_fork+0x55/0x80
  [  960.141706]  [] ? kthread_create_on_node+0x1e0/0x1e0

  The vanilla 4.4 kernel also shows the same call stack.

  On a patched kernel, the test will pass 

[Kernel-packages] [Bug 1835054] Re: Enable NIC driver for Armada SOCs in disco/generic arm64

2019-07-14 Thread Po-Hsu Lin
** Summary changed:

- Missing NIC driver for Armada 8040 (Macchiatobin)
+ Enable NIC driver for Armada SOCs in disco/generic arm64

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

Title:
  Enable NIC driver for Armada SOCs in disco/generic arm64

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  == SRU Justification ==
  The mvpp2 is a driver for network controllers(s) in Marvell SOCs, 
particularly Armada 8040.

  However this driver was neither enabled as a module or a built-in for
  Disco arm64.

  == Fix ==
  Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can solve 
this problem.

  Corresponding configs like CONFIG_ARCH_MVEBU and CONFIG_ARCH_MULTI_V7
  need to be enabled as well to meet the dependency requirement.

  CONFIG_CRYPTO_DEV_SAFEXCEL and CONFIG_PCI_AARDVARK are disabled
  explicitly to avoid interactive dialogues when building the kernel.

  == Test ==
  A test kernel for Disco ARM64 could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/

  User has confirmed that the patched kernel can fix this missing driver
  issue.

  == Regression Potential ==
  Low, this patch just make this driver to be built as a module, and we already 
have this enabled for armhf.

  
  == Original Bug Report ==

  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a module or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+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 1836188] Re: cpuset_exclusive in controllers from ubuntu_ltp failed on C P9

2019-07-12 Thread Po-Hsu Lin
http://lists.linux.it/pipermail/ltp/2019-July/012741.html

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

Title:
  cpuset_exclusive in controllers from ubuntu_ltp failed on C P9

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

Bug description:
  This issue was only spotted on node Baltar (P9)

  This is caused by the return value in:
    $ cat /sys/devices/system/node/has_normal_memory
    0,8

  The test was trying to use do arithmetic operation with it, but didn't
  expect to get a return value with a comma in it.

  <<>>
  tag=cpuset_exclusive stime=1562844139
  cmdline="   cpuset_exclusive_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  /opt/ltp/testcases/bin/cpuset_exclusive_test.sh: 36: 
/opt/ltp/testcases/bin/cpuset_funcs.sh: arithmetic expression: expecting EOF: 
"0,8 + 1"
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  Not sure if this is a test case issue, or if we should see a comma in
  /sys/devices/system/node/has_normal_memory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 10:56 seq
   crw-rw 1 root audio 116, 33 Jul 11 10:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.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:
  Date: Thu Jul 11 11:25:40 2019
  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.74 1.52 0.74 1/1338 6264
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1805 00:17:364 0 EOF
   2: POSIX  ADVISORY  WRITE 3956 00:17:504 0 EOF
   3: FLOCK  ADVISORY  WRITE 3915 00:17:566 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.18.0-25-generic (buildd@bos02-ppc64el-009) (gcc 
version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10.1)) #26-Ubuntu SMP Mon Jun 24 
09:32:46 UTC 2019
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  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 = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 83)
   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-kernel-tests/+bug/1836188/+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 1812796] Re: TRACE_syscall.ptrace_syscall_dropped in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC

2019-07-12 Thread Po-Hsu Lin
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1812796

Title:
  TRACE_syscall.ptrace_syscall_dropped in seccomp from
  ubuntu_kernel_selftests failed on B/C PowerPC

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

Bug description:
  == SRU Justification ==
  The TRACE_syscall.ptrace_syscall_dropped test in seccomp from 
ubuntu_kernel_selftests will fail on a Power8 node with B/C kernel.

  [ RUN  ] TRACE_syscall.ptrace_syscall_dropped
  seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == 
syscall(286) (18446744073709551615)
  TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13
  [ FAIL ] TRACE_syscall.ptrace_syscall_dropped

  == Fix ==
  * ed5f1326 (selftests/seccomp: Enhance per-arch ptrace syscall skip tests)

  This patch can be cherry-picked into B/C, and it's already in Disco.
  The ptrace_syscall_dropped will be changed into ptrace_syscall_faked, and a 
new ptrace_syscall_errno test will be added.

  == Test ==
  Patch tested with different arch (amd64 / power8 / arm64 / i386), the new 
test will pass on them except for PowerPC.

  Although the faked (bug 1829363) and errno (bug 1829359) test will
  fail on PowerPC, it's actually helping us to nail down a real issue in
  our kernel.

  == Regression Potential ==
  Low, changes limited to the testing tool in the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 22 04:30 seq
   crw-rw 1 root audio 116, 33 Jan 22 04:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  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:
  Date: Tue Jan 22 06:09:34 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.13 0.34 0.23 1/1487 35882
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC 
2018
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.694 GHz (cpu 152)
   max: 3.694 GHz (cpu 1)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812796/+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 1812796] Re: TRACE_syscall.ptrace_syscall_dropped in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC

2019-07-12 Thread Po-Hsu Lin
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-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/1812796

Title:
  TRACE_syscall.ptrace_syscall_dropped in seccomp from
  ubuntu_kernel_selftests failed on B/C PowerPC

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == SRU Justification ==
  The TRACE_syscall.ptrace_syscall_dropped test in seccomp from 
ubuntu_kernel_selftests will fail on a Power8 node with B/C kernel.

  [ RUN  ] TRACE_syscall.ptrace_syscall_dropped
  seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == 
syscall(286) (18446744073709551615)
  TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13
  [ FAIL ] TRACE_syscall.ptrace_syscall_dropped

  == Fix ==
  * ed5f1326 (selftests/seccomp: Enhance per-arch ptrace syscall skip tests)

  This patch can be cherry-picked into B/C, and it's already in Disco.
  The ptrace_syscall_dropped will be changed into ptrace_syscall_faked, and a 
new ptrace_syscall_errno test will be added.

  == Test ==
  Patch tested with different arch (amd64 / power8 / arm64 / i386), the new 
test will pass on them except for PowerPC.

  Although the faked (bug 1829363) and errno (bug 1829359) test will
  fail on PowerPC, it's actually helping us to nail down a real issue in
  our kernel.

  == Regression Potential ==
  Low, changes limited to the testing tool in the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 22 04:30 seq
   crw-rw 1 root audio 116, 33 Jan 22 04:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  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:
  Date: Tue Jan 22 06:09:34 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.13 0.34 0.23 1/1487 35882
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC 
2018
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.694 GHz (cpu 152)
   max: 3.694 GHz (cpu 1)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812796/+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 1836188] Re: cpuset_exclusive in controllers from ubuntu_ltp failed on C P9

2019-07-11 Thread Po-Hsu Lin
The code:
  N_NODES=${N_NODES#*-*}
  N_NODES=$(($N_NODES + 1))

Take cares only the case with a range of nodes:
  0-8

But not some specific nodes like in this case:
  0,8


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

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

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

** Changed in: linux (Ubuntu)
   Status: New => 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/1836188

Title:
  cpuset_exclusive in controllers from ubuntu_ltp failed on C P9

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

Bug description:
  This issue was only spotted on node Baltar (P9)

  This is caused by the return value in:
    $ cat /sys/devices/system/node/has_normal_memory
    0,8

  The test was trying to use do arithmetic operation with it, but didn't
  expect to get a return value with a comma in it.

  <<>>
  tag=cpuset_exclusive stime=1562844139
  cmdline="   cpuset_exclusive_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  /opt/ltp/testcases/bin/cpuset_exclusive_test.sh: 36: 
/opt/ltp/testcases/bin/cpuset_funcs.sh: arithmetic expression: expecting EOF: 
"0,8 + 1"
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  Not sure if this is a test case issue, or if we should see a comma in
  /sys/devices/system/node/has_normal_memory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 10:56 seq
   crw-rw 1 root audio 116, 33 Jul 11 10:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.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:
  Date: Thu Jul 11 11:25:40 2019
  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.74 1.52 0.74 1/1338 6264
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1805 00:17:364 0 EOF
   2: POSIX  ADVISORY  WRITE 3956 00:17:504 0 EOF
   3: FLOCK  ADVISORY  WRITE 3915 00:17:566 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.18.0-25-generic (buildd@bos02-ppc64el-009) (gcc 
version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10.1)) #26-Ubuntu SMP Mon Jun 24 
09:32:46 UTC 2019
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  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 = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 83)
   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-kernel-tests/+bug/1836188/+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 1836188] Re: cpuset_exclusive in controllers from ubuntu_ltp failed on C P9

2019-07-11 Thread Po-Hsu Lin
>From the document, it looks like a test case issue to me:
What:   /sys/devices/system/node/has_normal_memory
Date:   October 2002
Contact:Linux Memory Management list 
Description:
Nodes that have regular memory.

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

Title:
  cpuset_exclusive in controllers from ubuntu_ltp failed on C P9

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

Bug description:
  This issue was only spotted on node Baltar (P9)

  This is caused by the return value in:
    $ cat /sys/devices/system/node/has_normal_memory
    0,8

  The test was trying to use do arithmetic operation with it, but didn't
  expect to get a return value with a comma in it.

  <<>>
  tag=cpuset_exclusive stime=1562844139
  cmdline="   cpuset_exclusive_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  /opt/ltp/testcases/bin/cpuset_exclusive_test.sh: 36: 
/opt/ltp/testcases/bin/cpuset_funcs.sh: arithmetic expression: expecting EOF: 
"0,8 + 1"
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  Not sure if this is a test case issue, or if we should see a comma in
  /sys/devices/system/node/has_normal_memory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 10:56 seq
   crw-rw 1 root audio 116, 33 Jul 11 10:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.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:
  Date: Thu Jul 11 11:25:40 2019
  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.74 1.52 0.74 1/1338 6264
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1805 00:17:364 0 EOF
   2: POSIX  ADVISORY  WRITE 3956 00:17:504 0 EOF
   3: FLOCK  ADVISORY  WRITE 3915 00:17:566 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.18.0-25-generic (buildd@bos02-ppc64el-009) (gcc 
version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10.1)) #26-Ubuntu SMP Mon Jun 24 
09:32:46 UTC 2019
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  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 = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 83)
   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-kernel-tests/+bug/1836188/+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 1836188] [NEW] cpuset_exclusive in controllers from ubuntu_ltp failed on C P9

2019-07-11 Thread Po-Hsu Lin
Public bug reported:

This issue was only spotted on node Baltar (P9)

This is caused by the return value in:
  $ cat /sys/devices/system/node/has_normal_memory
  0,8

The test was trying to use do arithmetic operation with it, but didn't
expect to get a return value with a comma in it.

<<>>
tag=cpuset_exclusive stime=1562844139
cmdline="   cpuset_exclusive_test.sh"
contacts=""
analysis=exit
<<>>
incrementing stop
/opt/ltp/testcases/bin/cpuset_exclusive_test.sh: 36: 
/opt/ltp/testcases/bin/cpuset_funcs.sh: arithmetic expression: expecting EOF: 
"0,8 + 1"
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=2 corefile=no
cutime=0 cstime=0
<<>>

Not sure if this is a test case issue, or if we should see a comma in
/sys/devices/system/node/has_normal_memory

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-25-generic 4.18.0-25.26
ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
Uname: Linux 4.18.0-25-generic ppc64le
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 11 10:56 seq
 crw-rw 1 root audio 116, 33 Jul 11 10:56 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13.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:
Date: Thu Jul 11 11:25:40 2019
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.74 1.52 0.74 1/1338 6264
ProcLocks:
 1: POSIX  ADVISORY  WRITE 1805 00:17:364 0 EOF
 2: POSIX  ADVISORY  WRITE 3956 00:17:504 0 EOF
 3: FLOCK  ADVISORY  WRITE 3915 00:17:566 0 EOF
ProcSwaps:
 Filename   TypeSizeUsedPriority
 /swap.img   file   8388544 0   -2
ProcVersion: Linux version 4.18.0-25-generic (buildd@bos02-ppc64el-009) (gcc 
version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10.1)) #26-Ubuntu SMP Mon Jun 24 
09:32:46 UTC 2019
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-25-generic N/A
 linux-backports-modules-4.18.0-25-generic  N/A
 linux-firmware 1.175.6
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 = 39
cpu_dscr: DSCR is 16
cpu_freq:
 min:   2.862 GHz (cpu 79)
 max:   2.945 GHz (cpu 83)
 avg:   2.903 GHz
cpu_runmode:
 Could not retrieve current diagnostics mode,
 No kernel interface to firmware
cpu_smt: SMT=4

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

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

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


** Tags: 4.18 apport-bug cosmic ppc64el sru-20190701 ubuntu-ltp uec-images

** Description changed:

  This issue was only spotted on node Baltar (P9)
  
  This is caused by the return value in:
-   $ cat /sys/devices/system/node/has_normal_memory
-   0,8
+   $ cat /sys/devices/system/node/has_normal_memory
+   0,8
  
  The test was trying to use do arithmetic operation with it, but didn't
  expect to get a return value with a comma in it.
- 
  
  <<>>
  tag=cpuset_exclusive stime=1562844139
  cmdline="   cpuset_exclusive_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  /opt/ltp/testcases/bin/cpuset_exclusive_test.sh: 36: 
/opt/ltp/testcases/bin/cpuset_funcs.sh: arithmetic expression: expecting EOF: 
"0,8 + 1"
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>
  
+ Not sure if this is a test case issue, or if we should see a comma in
+ /sys/devices/system/node/has_normal_memory
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic ppc64le
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Jul 11 10:56 seq
-  crw-rw 1 root audio 116, 33 Jul 11 10:56 timer
+  total 0
+  crw-rw 1 root a

[Kernel-packages] [Bug 1783880] Re: ltp-syscalls: fallocate05 fails with btrfs on ppc64el

2019-07-11 Thread Po-Hsu Lin
** Tags added: ppc64le 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/1783880

Title:
  ltp-syscalls: fallocate05 fails with btrfs on ppc64el

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:
  This affects at least bionic and cosmic proposed kernels.

  This affects only ppc64el. My guess is the reason is the page size. In
  fact, changing the fallocate size to 64KiB, the test works.

  tst_test.c:1079: INFO: Testing on btrfs
  tst_mkfs.c:83: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts=''
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:61: INFO: write(): ENOSPC
  fallocate05.c:62: PASS: write() wrote 32768 bytes
  fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
  fallocate05.c:78: BROK: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE): ENOSPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783880/+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 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on B

2019-07-11 Thread Po-Hsu Lin
Issue found on a P8 node with 4.15 kernel on Xenial as well.

** Tags added: ppc64el

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

Title:
  move_pages12 test from ubuntu_ltp_syscalls failed on B

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

Bug description:
  This is a new test case landed 8 days ago, but we already have the patch in 
B, and it looks like this is not failing across all the nodes:
  move_pages12.c:114: FAIL: move_pages failed: ENOMEM


  <<>>
  tag=move_pages12 stime=1559209337
  cmdline="move_pages12"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  move_pages12.c:235: INFO: Free RAM 31883452 kB
  move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4
  move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4
  move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0
  move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1
  move_pages12.c:169: PASS: Bug not reproduced
  move_pages12.c:114: FAIL: move_pages failed: ENOMEM
  move_pages12.c:81: FAIL: madvise failed: SUCCESS
  move_pages12.c:81: FAIL: madvise failed: SUCCESS
  
  move_pages12.c:81: FAIL: madvise failed: SUCCESS
  move_pages12.c:81: FAIL: madvise failed: SUCCESS

  Summary:
  passed   1
  failed   998
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=4 termination_type=exited termination_id=1 corefile=no
  cutime=93 cstime=474
  <<>>

  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 30 09:29 seq
   crw-rw 1 root audio 116, 33 May 30 09:29 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: Thu May 30 09:42:46 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-4.15.0-50-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 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/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.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+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 1812796] Re: TRACE_syscall.ptrace_syscall_dropped in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC

2019-07-11 Thread Po-Hsu Lin
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  TRACE_syscall.ptrace_syscall_dropped in seccomp from
  ubuntu_kernel_selftests failed on B/C PowerPC

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == SRU Justification ==
  The TRACE_syscall.ptrace_syscall_dropped test in seccomp from 
ubuntu_kernel_selftests will fail on a Power8 node with B/C kernel.

  [ RUN  ] TRACE_syscall.ptrace_syscall_dropped
  seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == 
syscall(286) (18446744073709551615)
  TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13
  [ FAIL ] TRACE_syscall.ptrace_syscall_dropped

  == Fix ==
  * ed5f1326 (selftests/seccomp: Enhance per-arch ptrace syscall skip tests)

  This patch can be cherry-picked into B/C, and it's already in Disco.
  The ptrace_syscall_dropped will be changed into ptrace_syscall_faked, and a 
new ptrace_syscall_errno test will be added.

  == Test ==
  Patch tested with different arch (amd64 / power8 / arm64 / i386), the new 
test will pass on them except for PowerPC.

  Although the faked (bug 1829363) and errno (bug 1829359) test will
  fail on PowerPC, it's actually helping us to nail down a real issue in
  our kernel.

  == Regression Potential ==
  Low, changes limited to the testing tool in the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 22 04:30 seq
   crw-rw 1 root audio 116, 33 Jan 22 04:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  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:
  Date: Tue Jan 22 06:09:34 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.13 0.34 0.23 1/1487 35882
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC 
2018
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.694 GHz (cpu 152)
   max: 3.694 GHz (cpu 1)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

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

2019-07-11 Thread Po-Hsu Lin
Failed on ARM64 Moonshot node with Operation Not Supported:

<<>>
tag=cpuset_hotplug stime=1562841086
cmdline="cpuset_hotplug_test.sh"
contacts=""
analysis=exit
<<>>
incrementing stop
cpuset_hotplug 1 TINFO: /bin/echo: write error: Operation not supported
cpuset_hotplug 1 TFAIL:  CPU#1 failed.
cpuset_hotplug 3 TINFO: /bin/echo: write error: Operation not supported
cpuset_hotplug 3 TFAIL: setup test environment(offline CPU#1) failed
cpuset_hotplug 5 TINFO: /bin/echo: write error: Operation not supported
cpuset_hotplug 5 TFAIL:  CPU#1 failed.
cpuset_hotplug 7 TINFO: /bin/echo: write error: Operation not supported
cpuset_hotplug 7 TFAIL:  CPU#1 failed.
cpuset_hotplug 9 TINFO: /bin/echo: write error: Operation not supported
cpuset_hotplug 9 TFAIL:  CPU#1 failed.
cpuset_hotplug 11 TINFO: /bin/echo: write error: Operation not supported
cpuset_hotplug 11 TFAIL: setup test environment(offline CPU#1) failed
<<>>
initiation_status="ok"
duration=4 termination_type=exited termination_id=1 corefile=no
cutime=20 cstime=162
<<>>

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+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 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

2019-07-11 Thread Po-Hsu Lin
Note that on ThunderX ARM64 sometimes it will fail with:
cpuhotplug03 1 TFAIL: No cpuhotplug_do_spin_loop processes found on CPU1

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

Title:
  cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

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

Bug description:
  <<>>
  incrementing stop
  Name:   cpuhotplug03
  Date:   Thu Jul 11 08:31:48 UTC 2019
  Desc:   Do tasks get scheduled to a newly on-lined CPU?

  CPU is 1
  sh: echo: I/O error
  cpuhotplug03 1 TBROK: CPU1 cannot be offlined
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  root  4642  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4643  0.0  0.0   2020   480 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4644  0.0  0.0   2020   468 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4645  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4646  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4647  0.0  0.0   2020   480 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4648  0.0  0.0   2020   456 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4649  0.0  0.0   2020   508 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4650  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4651  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4652  0.0  0.0   2020   484 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4653  0.0  0.0   2020   496 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4654  0.0  0.0   2020   464 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4655  0.0  0.0   2020   492 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4656  0.0  0.0   2020   448 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4657  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  root  4661  0.0  0.0   7540   648 pts/0S08:31   0:00 grep 
cpuhotplug_do_spin_loop
  cpuhotplug03 1 TINFO: Onlining CPU 1
7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found onCPU1
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=2 corefile=no
  cutime=1060 cstime=9
  <<>>

  
  Test passed on ThunderX ARM64, probably a test case issue.

  
  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "cpuhotplug03 cpuhotplug03.sh -c 1 -l 1" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 

[Kernel-packages] [Bug 1836169] [NEW] cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on C ARM64

2019-07-11 Thread Po-Hsu Lin
Public bug reported:

This issue can be found on both ThunderX and Moonshot ARM64

<<>>
incrementing stop
Name:   cpuhotplug04
Date:   Thu Jul 11 08:34:50 UTC 2019
Desc:   Does it prevent us from offlining the last CPU?

sh: echo: I/O error
cpuhotplug04 1 TFAIL: Could not offline cpu0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=9 cstime=4
<<>>

Steps to run this test:
  git clone --depth=1 https://github.com/linux-test-project/ltp.git
  cd ltp; make autotools; ./configure; make; sudo make install
  echo "cpuhotplug04 cpuhotplug04.sh -l 1" > /tmp/jobs
  sudo /opt/ltp/runltp -f /tmp/jobs

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-25-generic 4.18.0-25.26
ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
Uname: Linux 4.18.0-25-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
 crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13.4
Architecture: arm64
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 Jul 11 08:28:42 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-25-generic N/A
 linux-backports-modules-4.18.0-25-generic  N/A
 linux-firmware 1.175.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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


** Tags: 4.18 apport-bug arm64 cosmic sru-20190701 ubuntu-ltp uec-images

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

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

** Tags added: 4.18 sru-20190701 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/1836169

Title:
  cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on C ARM64

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

Bug description:
  This issue can be found on both ThunderX and Moonshot ARM64

  <<>>
  incrementing stop
  Name:   cpuhotplug04
  Date:   Thu Jul 11 08:34:50 UTC 2019
  Desc:   Does it prevent us from offlining the last CPU?

  sh: echo: I/O error
  cpuhotplug04 1 TFAIL: Could not offline cpu0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=9 cstime=4
  <<>>

  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "cpuhotplug04 cpuhotplug04.sh -l 1" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  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 Jul 11 08:28:42 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1836170] [NEW] cpuhotplug06 in cpuhotplug from ubuntu_ltp failed on C ARM64

2019-07-11 Thread Po-Hsu Lin
Public bug reported:

This issue was only spotted on Moonshot ARM64, probably a test case
issue:

<<>>
incrementing stop
Name:   cpuhotplug06
Date:   Thu Jul 11 08:38:03 UTC 2019
Desc:   Does top work properly when CPU hotplug events occur?

CPU is 1
sh: echo: I/O error
cpuhotplug06 1 TBROK: CPU1 cannot be offlined
 5221 pts/000:00:00 top
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=2 corefile=no
cutime=2 cstime=1
<<>>

Steps to run this test:
  git clone --depth=1 https://github.com/linux-test-project/ltp.git
  cd ltp; make autotools; ./configure; make; sudo make install
  echo "cpuhotplug06 cpuhotplug06.sh -c 1 -l 1" > /tmp/jobs
  sudo /opt/ltp/runltp -f /tmp/jobs

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-25-generic 4.18.0-25.26
ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
Uname: Linux 4.18.0-25-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
 crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13.4
Architecture: arm64
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 Jul 11 08:30:02 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-25-generic N/A
 linux-backports-modules-4.18.0-25-generic  N/A
 linux-firmware 1.175.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: apport-bug arm64 cosmic sru-20190701 ubuntu-ltp uec-images

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

** Tags added: sru-20190701 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/1836170

Title:
  cpuhotplug06 in cpuhotplug from ubuntu_ltp failed on C ARM64

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

Bug description:
  This issue was only spotted on Moonshot ARM64, probably a test case
  issue:

  <<>>
  incrementing stop
  Name:   cpuhotplug06
  Date:   Thu Jul 11 08:38:03 UTC 2019
  Desc:   Does top work properly when CPU hotplug events occur?

  CPU is 1
  sh: echo: I/O error
  cpuhotplug06 1 TBROK: CPU1 cannot be offlined
   5221 pts/000:00:00 top
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=2 corefile=no
  cutime=2 cstime=1
  <<>>

  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "cpuhotplug06 cpuhotplug06.sh -c 1 -l 1" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  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 Jul 11 08:30:02 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836170/+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 1836166] Re: cpuhotplug02 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

2019-07-11 Thread Po-Hsu Lin
** Summary changed:

- cpuhotplug02 in cpuhotplug from ubuntu_ltp failed on C ARM64
+ cpuhotplug02 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

** Description changed:

  Steps to run this test:
-   git clone --depth=1 https://github.com/linux-test-project/ltp.git
-   cd ltp; make autotools; ./configure; make; sudo make install
-   echo "cpuhotplug02 cpuhotplug02.sh -c 1 -l 1" > /tmp/jobs
-   sudo /opt/ltp/runltp -f /tmp/jobs
- 
+   git clone --depth=1 https://github.com/linux-test-project/ltp.git
+   cd ltp; make autotools; ./configure; make; sudo make install
+   echo "cpuhotplug02 cpuhotplug02.sh -c 1 -l 1" > /tmp/jobs
+   sudo /opt/ltp/runltp -f /tmp/jobs
  
  <<>>
  incrementing stop
  Name:   cpuhotplug02
  Date:   Thu Jul 11 08:21:54 UTC 2019
  Desc:   What happens to a process when its CPU is offlined?
  
  CPU is 1
  sh: echo: I/O error
  cpuhotplug02 1 TFAIL: process did not change from CPU   1
  <<>>
  
+ Test passed on ThunderX ARM64, probably a test case issue.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
-  crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
+  crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  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 Jul 11 08:22:09 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
-  
+ 
  ProcFB:
-  
+ 
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
-  linux-restricted-modules-4.18.0-25-generic N/A
-  linux-backports-modules-4.18.0-25-generic  N/A
-  linux-firmware 1.175.6
+  linux-restricted-modules-4.18.0-25-generic N/A
+  linux-backports-modules-4.18.0-25-generic  N/A
+  linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

** Tags added: sru-20190701

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

Title:
  cpuhotplug02 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

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

Bug description:
  Steps to run this test:
    git clone --depth=1 https://github.com/linux-test-project/ltp.git
    cd ltp; make autotools; ./configure; make; sudo make install
    echo "cpuhotplug02 cpuhotplug02.sh -c 1 -l 1" > /tmp/jobs
    sudo /opt/ltp/runltp -f /tmp/jobs

  <<>>
  incrementing stop
  Name:   cpuhotplug02
  Date:   Thu Jul 11 08:21:54 UTC 2019
  Desc:   What happens to a process when its CPU is offlined?

  CPU is 1
  sh: echo: I/O error
  cpuhotplug02 1 TFAIL: process did not change from CPU   1
  <<>>

  Test passed on ThunderX ARM64, probably a test case issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  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 Jul 11 08:22:09 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1836167] [NEW] cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

2019-07-11 Thread Po-Hsu Lin
Public bug reported:

<<>>
incrementing stop
Name:   cpuhotplug03
Date:   Thu Jul 11 08:31:48 UTC 2019
Desc:   Do tasks get scheduled to a newly on-lined CPU?

CPU is 1
sh: echo: I/O error
cpuhotplug03 1 TBROK: CPU1 cannot be offlined
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root  4642  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4643  0.0  0.0   2020   480 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4644  0.0  0.0   2020   468 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4645  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4646  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4647  0.0  0.0   2020   480 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4648  0.0  0.0   2020   456 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4649  0.0  0.0   2020   508 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4650  0.0  0.0   2020   488 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4651  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4652  0.0  0.0   2020   484 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4653  0.0  0.0   2020   496 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4654  0.0  0.0   2020   464 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4655  0.0  0.0   2020   492 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4656  0.0  0.0   2020   448 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4657  0.0  0.0   2020   472 pts/0R08:31   0:00 /bin/sh 
/opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
root  4661  0.0  0.0   7540   648 pts/0S08:31   0:00 grep 
cpuhotplug_do_spin_loop
cpuhotplug03 1 TINFO: Onlining CPU 1
  7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
  5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop
cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found on  CPU1
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=2 corefile=no
cutime=1060 cstime=9
<<>>


Test passed on ThunderX ARM64, probably a test case issue.


Steps to run this test:
  git clone --depth=1 https://github.com/linux-test-project/ltp.git
  cd ltp; make autotools; ./configure; make; sudo make install
  echo "cpuhotplug03 cpuhotplug03.sh -c 1 -l 1" > /tmp/jobs
  sudo /opt/ltp/runltp -f /tmp/jobs

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-25-generic 4.18.0-25.26
ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
Uname: Linux 4.18.0-25-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
 crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13.4
Architecture: arm64
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 Jul 11 08:22:51 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-25-generic N/A
 linux-backports-modules-4.18.0-25-generic  N/A
 linux-firmware 1.175.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade 

[Kernel-packages] [Bug 1836166] [NEW] cpuhotplug02 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

2019-07-11 Thread Po-Hsu Lin
Public bug reported:

Steps to run this test:
  git clone --depth=1 https://github.com/linux-test-project/ltp.git
  cd ltp; make autotools; ./configure; make; sudo make install
  echo "cpuhotplug02 cpuhotplug02.sh -c 1 -l 1" > /tmp/jobs
  sudo /opt/ltp/runltp -f /tmp/jobs

<<>>
incrementing stop
Name:   cpuhotplug02
Date:   Thu Jul 11 08:21:54 UTC 2019
Desc:   What happens to a process when its CPU is offlined?

CPU is 1
sh: echo: I/O error
cpuhotplug02 1 TFAIL: process did not change from CPU   1
<<>>

Test passed on ThunderX ARM64, probably a test case issue.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-25-generic 4.18.0-25.26
ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
Uname: Linux 4.18.0-25-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
 crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13.4
Architecture: arm64
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 Jul 11 08:22:09 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:

ProcFB:

ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-25-generic N/A
 linux-backports-modules-4.18.0-25-generic  N/A
 linux-firmware 1.175.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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


** Tags: apport-bug arm64 cosmic sru-20190701 uec-images

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

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

Title:
  cpuhotplug02 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

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

Bug description:
  Steps to run this test:
    git clone --depth=1 https://github.com/linux-test-project/ltp.git
    cd ltp; make autotools; ./configure; make; sudo make install
    echo "cpuhotplug02 cpuhotplug02.sh -c 1 -l 1" > /tmp/jobs
    sudo /opt/ltp/runltp -f /tmp/jobs

  <<>>
  incrementing stop
  Name:   cpuhotplug02
  Date:   Thu Jul 11 08:21:54 UTC 2019
  Desc:   What happens to a process when its CPU is offlined?

  CPU is 1
  sh: echo: I/O error
  cpuhotplug02 1 TFAIL: process did not change from CPU   1
  <<>>

  Test passed on ThunderX ARM64, probably a test case issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  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 Jul 11 08:22:09 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836166/+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 1836162] [NEW] userns06 in containers from ubuntu_ltp failed on ARM64 / i386 / PowerPC

2019-07-11 Thread Po-Hsu Lin
Public bug reported:

This failure was spotted on ARM64  / i386 / PowerPC except amd64

<<>>
tag=userns06 stime=1562831689
cmdline="userns06"
contacts=""
analysis=exit
<<>>
incrementing stop
execvp unexpected error: (14) Bad address
execvp unexpected error: (14) Bad address
user_namespace60  TINFO  :  Child process returned TFAIL
user_namespace60  TINFO  :  Child process returned TFAIL
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<>>


Steps to run this test:
  git clone --depth=1 https://github.com/linux-test-project/ltp.git
  cd ltp; make autotools; ./configure; make; sudo make install
  echo "userns06 userns06" > /tmp/jobs
  sudo /opt/ltp/runltp -f /tmp/jobs

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-25-generic 4.18.0-25.26
ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
Uname: Linux 4.18.0-25-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
 crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13.4
Architecture: arm64
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 Jul 11 07:16:04 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-25-generic N/A
 linux-backports-modules-4.18.0-25-generic  N/A
 linux-firmware 1.175.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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


** Tags: apport-bug arm64 cosmic sru-20190701 ubuntu-ltp uec-images

** Summary changed:

- userns06 in containers from ubuntu_ltp failed on ARM64
+ userns06 in containers from ubuntu_ltp failed on ARM64 / i386 / PowerPC

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

** Tags added: sru-20190701

** Tags added: ubuntu-ltp

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

Title:
  userns06 in containers from ubuntu_ltp failed on ARM64 / i386 /
  PowerPC

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

Bug description:
  This failure was spotted on ARM64  / i386 / PowerPC except amd64

  <<>>
  tag=userns06 stime=1562831689
  cmdline="userns06"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  execvp unexpected error: (14) Bad address
  execvp unexpected error: (14) Bad address
  user_namespace60  TINFO  :  Child process returned TFAIL
  user_namespace60  TINFO  :  Child process returned TFAIL
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  
  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "userns06 userns06" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  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 Jul 11 07:16:04 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
 

[Kernel-packages] [Bug 1808107] Re: fanotify11 in ubuntu_ltp_syscalls failed

2019-07-10 Thread Po-Hsu Lin
** No longer affects: ubuntu-kernel-tests

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

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

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

Title:
  fanotify11 in ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  Invalid

Bug description:
  Timeouted on Trusty:
   startup='Tue Dec 11 11:58:36 2018'
   tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
   fanotify11.c:85: INFO: without FAN_REPORT_TID: tgid=5447, tid=5448, 
event.pid=5447
   fanotify11.c:89: PASS: event.pid == tgid
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Cannot kill test processes!
   Congratulation, likely test hit a kernel bug.
   Exitting uncleanly...
   tag=fanotify11 stime=1544529516 dur=350 exit=exited stat=1 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1808107/+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 1836134] Re: 361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours to run on a ThunderX ARM64 node

2019-07-10 Thread Po-Hsu Lin
** Description changed:

- This test will take about 2 hours to run on node wright (ThunderX ARM64):
+ This test will take about 2 hours to run on node wright (ThunderX ARM64) with 
Xenial kernel.
  Test history:
  4.4.0-155.182 - 1h45m
  4.4.0-152.179 - 1h57m
  4.4.0-150.176 - 2h00m
  4.4.0-149.175 - 2h03m
  4.4.0-147.173 - 1h55m
  4.4.0-146.172 - 1h57m
  4.4.0-145.171 - 1h59m
  
- However it took about 25min to run on Moonshot ARM64 (node 
ms10-35-mcdivittB0-kernel),
+ However it took about 25min to run on a Moonshot ARM64 
(ms10-35-mcdivittB0-kernel) with Xenial kernel.
  Test history:
  4.4.0-155.182 - 23m
  4.4.0-152.179 - 24m
  4.4.0-150.176 - 23m
  4.4.0-149.175 - 23m
  4.4.0-147.173 - 23m
  4.4.0-146.172 - 23m
  4.4.0-145.171 - 24m
  
  Not sure why there is such a huge difference, but it might needs to be
  investigated.
  
+ This is node wright performance with this test against different kernels:
+ 5.0.0-21.22 - 1h20m
+ 4.18.0-26.27 - 1h18m
+ 5.0.0-21.22~18.04.1 - 1h17m
+ 4.15.0-55.60 - 1h23m
+ 4.15.0-55.60~16.04.2 - 1h23m
+ 
+ And node ms10-35-mcdivittB0-kernel against different kernels:
+ 5.0.0-21.22 - 17m
+ 4.18.0-26.27 - 17m
+ 5.0.0-21.22~18.04.1 - 17m
+ 4.15.0-55.60 - 17m
+ 4.15.0-55.60~16.04.2 - 17m
+ 
+ 
  Step to run the test:
-   sudo apt-get install git python-minimal python-yaml gdb -y
-   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
-   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
-   rm -fr autotest/client/tests
-   ln -sf ~/autotest-client-tests autotest/client/tests
-   mkdir autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp
-   mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/* 
autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp
-   mv 
autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp/361c093d7f99c3f6cbb07d5c580ce778ab418c42.sh
 autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/
-   AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_btrfs_kernel_fixes/control
+   sudo apt-get install git python-minimal python-yaml gdb -y
+   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
+   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
+   rm -fr autotest/client/tests
+   ln -sf ~/autotest-client-tests autotest/client/tests
+   mkdir autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp
+   mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/* 
autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp
+   mv 
autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp/361c093d7f99c3f6cbb07d5c580ce778ab418c42.sh
 autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/
+   AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_btrfs_kernel_fixes/control
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-154-generic 4.4.0-154.181
  ProcVersionSignature: User Name 4.4.0-154.181-generic 4.4.179
  Uname: Linux 4.4.0-154-generic aarch64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Jul 10 08:25 seq
-  crw-rw 1 root audio 116, 33 Jul 10 08:25 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Jul 10 08:25 seq
+  crw-rw 1 root audio 116, 33 Jul 10 08:25 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: arm64
  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:
  CRDA: N/A
  CurrentDmesg:
-  
+ 
  Date: Thu Jul 11 02:56:23 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
-  
+ 
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic 
root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-154-generic N/A
-  linux-backports-modules-4.4.0-154-generic  N/A
-  linux-firmware 1.157.21
+  linux-restricted-modules-4.4.0-154-generic N/A
+  linux-backports-modules-4.4.0-154-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 (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 

[Kernel-packages] [Bug 1836134] Re: 361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours to run on a ThunderX ARM64 node

2019-07-10 Thread Po-Hsu Lin
** Tags added: sru-20190701 ubuntu-btrfs-kernel-fixes

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

Title:
  361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours
  to run on a ThunderX ARM64 node

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

Bug description:
  This test will take about 2 hours to run on node wright (ThunderX ARM64):
  Test history:
  4.4.0-155.182 - 1h45m
  4.4.0-152.179 - 1h57m
  4.4.0-150.176 - 2h00m
  4.4.0-149.175 - 2h03m
  4.4.0-147.173 - 1h55m
  4.4.0-146.172 - 1h57m
  4.4.0-145.171 - 1h59m

  However it took about 25min to run on Moonshot ARM64 (node 
ms10-35-mcdivittB0-kernel),
  Test history:
  4.4.0-155.182 - 23m
  4.4.0-152.179 - 24m
  4.4.0-150.176 - 23m
  4.4.0-149.175 - 23m
  4.4.0-147.173 - 23m
  4.4.0-146.172 - 23m
  4.4.0-145.171 - 24m

  Not sure why there is such a huge difference, but it might needs to be
  investigated.

  Step to run the test:
sudo apt-get install git python-minimal python-yaml gdb -y
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
mkdir autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp
mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/* 
autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp
mv 
autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp/361c093d7f99c3f6cbb07d5c580ce778ab418c42.sh
 autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_btrfs_kernel_fixes/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-154-generic 4.4.0-154.181
  ProcVersionSignature: User Name 4.4.0-154.181-generic 4.4.179
  Uname: Linux 4.4.0-154-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 10 08:25 seq
   crw-rw 1 root audio 116, 33 Jul 10 08:25 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: arm64
  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:
  CRDA: N/A
  CurrentDmesg:
   
  Date: Thu Jul 11 02:56:23 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic 
root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-154-generic N/A
   linux-backports-modules-4.4.0-154-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 (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836134/+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 1836134] [NEW] 361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours to run on a ThunderX ARM64 node

2019-07-10 Thread Po-Hsu Lin
Public bug reported:

This test will take about 2 hours to run on node wright (ThunderX ARM64):
Test history:
4.4.0-155.182 - 1h45m
4.4.0-152.179 - 1h57m
4.4.0-150.176 - 2h00m
4.4.0-149.175 - 2h03m
4.4.0-147.173 - 1h55m
4.4.0-146.172 - 1h57m
4.4.0-145.171 - 1h59m

However it took about 25min to run on Moonshot ARM64 (node 
ms10-35-mcdivittB0-kernel),
Test history:
4.4.0-155.182 - 23m
4.4.0-152.179 - 24m
4.4.0-150.176 - 23m
4.4.0-149.175 - 23m
4.4.0-147.173 - 23m
4.4.0-146.172 - 23m
4.4.0-145.171 - 24m

Not sure why there is such a huge difference, but it might needs to be
investigated.

Step to run the test:
  sudo apt-get install git python-minimal python-yaml gdb -y
  git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
  git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
  rm -fr autotest/client/tests
  ln -sf ~/autotest-client-tests autotest/client/tests
  mkdir autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp
  mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/* 
autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp
  mv 
autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp/361c093d7f99c3f6cbb07d5c580ce778ab418c42.sh
 autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/
  AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_btrfs_kernel_fixes/control

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-154-generic 4.4.0-154.181
ProcVersionSignature: User Name 4.4.0-154.181-generic 4.4.179
Uname: Linux 4.4.0-154-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 10 08:25 seq
 crw-rw 1 root audio 116, 33 Jul 10 08:25 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: arm64
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:
CRDA: N/A
CurrentDmesg:
 
Date: Thu Jul 11 02:56:23 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Cavium ThunderX CRB
PciMultimedia:
 
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic 
root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-154-generic N/A
 linux-backports-modules-4.4.0-154-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 (probably fresh install)
dmi.bios.date: 12/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 0
dmi.chassis.vendor: Cavium
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
dmi.product.name: ThunderX CRB
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Cavium

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

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

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


** Tags: apport-bug arm64 sru-20190701 ubuntu-btrfs-kernel-fixes uec-images 
xenial

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

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

Title:
  361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours
  to run on a ThunderX ARM64 node

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

Bug description:
  This test will take about 2 hours to run on node wright (ThunderX ARM64):
  Test history:
  4.4.0-155.182 - 1h45m
  4.4.0-152.179 - 1h57m
  4.4.0-150.176 - 2h00m
  4.4.0-149.175 - 2h03m
  4.4.0-147.173 - 1h55m
  4.4.0-146.172 - 1h57m
  4.4.0-145.171 - 1h59m

  However it took about 25min to run on Moonshot ARM64 (node 
ms10-35-mcdivittB0-kernel),
  Test history:
  4.4.0-155.182 - 23m
  4.4.0-152.179 - 24m
  4.4.0-150.176 - 23m
  4.4.0-149.175 - 23m
  4.4.0-147.173 - 23m
  4.4.0-146.172 - 23m
  4.4.0-145.171 - 24m

  Not sure why there is such a huge difference, but it might needs to be
  investigated.

  Step to run the test:
sudo apt-get install git python-minimal python-yaml gdb -y
git clone --depth=1 

[Kernel-packages] [Bug 1834918] Re: linux: 4.4.0-155.182 -proposed tracker

2019-07-10 Thread Po-Hsu Lin
4.4.0-155.182 - generic
Regression test CMPL, RTB.

55 / 56 tests were run, missing: xfstests
Issue to note in amd64:
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, 
fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 
1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 
(bug 1819116)

51 / 52 tests were run, missing: xfstests
Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - gicv2-mmio on X-ARM64 (bug 1828165) pmu on 
ms10-34-mcdivittB0-kernel (bug 1751000) gicv2 related test failed on ThunderX 
(bug 1828153)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, 
fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 
1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 
(bug 1819116)

Issue to note in i386:
  ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056)
  ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, 
fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 
1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 
(bug 1819116)
  xfstests - xfs generic/308 timed out (bug 1738152)

51 / 52 tests were run, missing: ubuntu_boot
Issue to note in ppc64le (P8):
  ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 
320M on Xenial P8 (bug 1813863)
  ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fsync01, 
preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) 
inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify06 (bug 1833028) 
fanotify07 causing timeout on fanotify08, fanotify09, fanotify10, fanotify11, 
fanotify12, fanotify13, fanotify14, fanotify15 (bug 1775165) fanotify09-2 (bug 
1804594) fanotify10 (bug 1802454)
  xfstests - btrfs generic/176 timed out

Issue to note in s390x (KVM):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452)
  ubuntu_kernel_selftests - test_bpf in net (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - test should be skipped for X s390x KVM
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, 
fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 
1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 
(bug 1819116)
  ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable 
on X s390x (bug 1813721)

50 / 51 tests were run, missing: ubuntu_boot
Issue to note in s390x (Ubuntu on LPAR):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452)
  ubuntu_kernel_selftests - test_bpf in net (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, 
fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 
1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 
(bug 1819116)
  ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable 
on X s390x (bug 1813721)

50 / 51 tests were run, missing: ubuntu_boot
Issue to note in s390x (zVM):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452)
  ubuntu_kernel_selftests - test_bpf in net (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, 
fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 
1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 
(bug 1819116)
  ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable 
on X s390x (bug 1813721)


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

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

2019-07-10 Thread Po-Hsu Lin
Didn't see this anymore.

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

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

Title:
  runpwtests03 from power_management_tests test suite in LTP failed

Status in ubuntu-kernel-tests:
  Fix Released
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 1830361] Re: cpuset_sched_domains from controller test suite in LTP failed

2019-07-10 Thread Po-Hsu Lin
** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   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/1830361

Title:
  cpuset_sched_domains from controller 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:
  New
Status in linux source package in Disco:
  New

Bug description:
  Issue found on Disco with node glameow:
   startup='Fri May 24 10:24:26 2019'
   cpuset_sched_domains 1 TINFO: root group load balance test
   cpuset_sched_domains 1 TINFO:  sched load balance: 0
   cpuset_sched_domains 1 TINFO: CPU hotplug:
   cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:72: 
partition domains failed.
   cpuset_sched_domains 1 TINFO: cpuset_sched_domains_check: find domain 
cpusets failed.
   cpuset_sched_domains 1 TFAIL: partition sched domains failed.
   cpuset_sched_domains 3 TINFO: root group load balance test
   cpuset_sched_domains 3 TINFO:  sched load balance: 1
   cpuset_sched_domains 3 TINFO: CPU hotplug:
   cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:72: 
partition domains failed.
   cpuset_sched_domains 3 TINFO: cpuset_sched_domains_check: find domain 
cpusets failed.
   cpuset_sched_domains 3 TFAIL: partition sched domains failed.
   cpuset_sched_domains 5 TINFO: root group load balance test
   cpuset_sched_domains 5 TINFO:  sched load balance: 0
   cpuset_sched_domains 5 TINFO: CPU hotplug:
   cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:72: 
partition domains failed.
   cpuset_sched_domains 5 TINFO: cpuset_sched_domains_check: find domain 
cpusets failed.
   cpuset_sched_domains 5 TFAIL: partition sched domains failed.
   cpuset_sched_domains 7 TINFO: root group load balance test
   cpuset_sched_domains 7 TINFO:  sched load balance: 0
   cpuset_sched_domains 7 TINFO: CPU hotplug:
   cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:72: 
partition domains failed.
   cpuset_sched_domains 7 TINFO: cpuset_sched_domains_check: find domain 
cpusets failed.
   cpuset_sched_domains 7 TFAIL: partition sched domains failed.
   cpuset_sched_domains 9 TINFO: root group load balance test
   cpuset_sched_domains 9 TINFO:  sched load balance: 1
   cpuset_sched_domains 9 TINFO: CPU hotplug:
   cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:72: 
partition domains failed.
   cpuset_sched_domains 9 TINFO: cpuset_sched_domains_check: find domain 
cpusets failed.
   cpuset_sched_domains 9 TFAIL: partition sched domains failed.
   cpuset_sched_domains 11 TINFO: root group load balance test
   cpuset_sched_domains 11 TINFO:  sched load balance: 1
   cpuset_sched_domains 11 TINFO: CPU hotplug:
   cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:72: 
partition domains failed.
   cpuset_sched_domains 11 TINFO: cpuset_sched_domains_check: find domain 
cpusets failed.
   cpuset_sched_domains 11 TFAIL: partition sched domains failed.
   cpuset_sched_domains 13 TINFO: general group load balance test
   cpuset_sched_domains 13 TINFO: root group info:
   cpuset_sched_domains 13 TINFO:  sched load balance: 0
   cpuset_sched_domains 13 TINFO: general group info:
   cpuset_sched_domains 13 TINFO:  cpus: -
   cpuset_sched_domains 13 TINFO:  sched load balance: 1
   cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:72: 
partition domains failed.
   cpuset_sched_domains 13 TINFO: cpuset_sched_domains_check: find domain 
cpusets failed.
   cpuset_sched_domains 13 TFAIL: partition sched domains failed.
   cpuset_sched_domains 15 TINFO: general group load balance test
   cpuset_sched_domains 15 TINFO: root group info:
   cpuset_sched_domains 15 TINFO:  sched load balance: 0
   cpuset_sched_domains 15 TINFO: general group info:
   cpuset_sched_domains 15 TINFO:  cpus: 1
   cpuset_sched_domains 15 TINFO:  sched load balance: 0
   cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:72: 
partition domains failed.
   cpuset_sched_domains 15 TINFO: cpuset_sched_domains_check: find domain 
cpusets failed.
   cpuset_sched_domains 15 TFAIL: partition sched domains failed.
   cpuset_sched_domains 17 TINFO: general group load balance test
   cpuset_sched_domains 17 TINFO: root group info:
   cpuset_sched_domains 17 TINFO:  sched load balance: 1
   cpuset_sched_domains 17 TINFO: general group info:
   cpuset_sched_domains 17 TINFO:  cpus: -
   cpuset_sched_domains 17 TINFO:  sched load balance: 1
   cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:72: 
partition domains failed.
   cpuset_sched_domains 17 TINFO: cpuset_sched_domains_check: find domain 
cpusets failed.
   cpuset_sched_domains 17 TFAIL: partition 

[Kernel-packages] [Bug 1830585] Re: cpuset_memory_spread from controllers test suite in LTP failed

2019-07-10 Thread Po-Hsu Lin
Found on node naumann with B-4.15

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

** Also affects: linux (Ubuntu Disco)
   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/1830585

Title:
  cpuset_memory_spread from controllers test suite in LTP failed

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 Disco:
  New

Bug description:
  Test failed with:
  cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected 
node(FilePages_For_Nodes(KB): _0: 2276
  _1: 102428, Expect Nodes: 1).

  <<>>
  tag=cpuset_memory_spread stime=1558937747
  cmdline="   cpuset_memory_spread_testset.sh"
  contacts=""
  analysis=exit
  <<>>
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 0.0993112 s, 1.1 GB/s
  cpuset_memory_spread 1 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 3 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 5 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected 
node(FilePages_For_Nodes(KB): _0: 2276
  _1: 102428, Expect Nodes: 1).
  cpuset_memory_spread 9 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 11 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 13 TPASS: Cpuset memory spread page test succeeded.
  <<>>
  initiation_status="ok"
  duration=10 termination_type=exited termination_id=1 corefile=no
  cutime=364 cstime=383
  <<>>

  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 06:16:49 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/1830585/+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 1830359] Re: cpuset_base_ops from controller test suite in LTP failed

2019-07-10 Thread Po-Hsu Lin
Found on amd64 node naumann with B 4.15

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

Title:
  cpuset_base_ops from controller 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:
  New
Status in linux source package in Disco:
  New

Bug description:
  Issue found on Disco with node glameow:
   startup='Fri May 24 10:23:44 2019'
   cpuset_base_ops 1 TPASS: cpuset.cpus(READONLY): Get the expected string
   cpuset_base_ops 3 TPASS: cpuset.mems(READONLY): Get the expected string
   cpuset_base_ops 5 TPASS: cpuset.memory_pressure(READONLY): Get the expected 
string
   cpuset_base_ops 7 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 9 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 11 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 13 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 15 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 17 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 19 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 21 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 23 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 25 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 27 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 29 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 31 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 33 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 35 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 37 TFAIL: cpuset.cpus: Test result -  Expected string - "0"
   cpuset_base_ops 39 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 41 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 43 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 45 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 47 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 49 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 51 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 53 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 55 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 57 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 59 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 61 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 63 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 65 TFAIL: cpuset.mems: Test result -  Expected string - "0"
   cpuset_base_ops 67 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 69 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 71 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 73 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 75 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 77 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 79 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 81 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 83 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 85 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 87 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 89 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 91 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 93 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 95 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 97 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 99 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 101 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 103 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 105 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 107 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 109 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 111 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 113 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 115 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 117 TPASS: cpuset.memory_spread_slab: Get the expected string
   cpuset_base_ops 119 TPASS: cpuset.memory_spread_slab: Get the expected string
   cpuset_base_ops 121 TPASS: cpuset.memory_spread_slab: Get the expected string
   cpuset_base_ops 123 TPASS: 

[Kernel-packages] [Bug 1830360] Re: cpuset_load_balance from controller test suite in LTP failed

2019-07-10 Thread Po-Hsu Lin
Found on node naumann with B-4.15


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

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

** Tags added: 4.15 bionic

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

Title:
  cpuset_load_balance from controller 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:
  New
Status in linux source package in Disco:
  New

Bug description:
  Issue found on Disco with node glameow:
   startup='Fri May 24 10:24:55 2019'
   cpuset_load_balance 1 TINFO: general group load balance test
   cpuset_load_balance 1 TINFO: root group info:
   cpuset_load_balance 1 TINFO:  sched load balance: 0
   cpuset_load_balance 1 TINFO: general group info:
   cpuset_load_balance 1 TINFO:  cpus: -
   cpuset_load_balance 1 TINFO:  sched load balance: 1
   cpuset_load_balance 1 TFAIL: load balance test failed.
   cpuset_load_balance 3 TINFO: general group load balance test
   cpuset_load_balance 3 TINFO: root group info:
   cpuset_load_balance 3 TINFO:  sched load balance: 0
   cpuset_load_balance 3 TINFO: general group info:
   cpuset_load_balance 3 TINFO:  cpus: 1
   cpuset_load_balance 3 TINFO:  sched load balance: 0
   cpuset_load_balance 3 TFAIL: load balance test failed.
   cpuset_load_balance 5 TINFO: general group load balance test
   cpuset_load_balance 5 TINFO: root group info:
   cpuset_load_balance 5 TINFO:  sched load balance: 1
   cpuset_load_balance 5 TINFO: general group info:
   cpuset_load_balance 5 TINFO:  cpus: -
   cpuset_load_balance 5 TINFO:  sched load balance: 1
   cpuset_load_balance 5 TFAIL: load balance test failed.
   cpuset_load_balance 7 TINFO: general group load balance test
   cpuset_load_balance 7 TINFO: root group info:
   cpuset_load_balance 7 TINFO:  sched load balance: 1
   cpuset_load_balance 7 TINFO: general group info:
   cpuset_load_balance 7 TINFO:  cpus: 1
   cpuset_load_balance 7 TINFO:  sched load balance: 1
   cpuset_load_balance 7 TFAIL: load balance test failed.
   cpuset_load_balance 9 TINFO: general group load balance test
   cpuset_load_balance 9 TINFO: root group info:
   cpuset_load_balance 9 TINFO:  sched load balance: 0
   cpuset_load_balance 9 TINFO: general group info:
   cpuset_load_balance 9 TINFO:  cpus: 1,2
   cpuset_load_balance 9 TINFO:  sched load balance: 0
   cpuset_load_balance 9 TFAIL: load balance test failed.
   cpuset_load_balance 11 TINFO: general group load balance test
   cpuset_load_balance 11 TINFO: root group info:
   cpuset_load_balance 11 TINFO:  sched load balance: 0
   cpuset_load_balance 11 TINFO: general group info:
   cpuset_load_balance 11 TINFO:  cpus: 1,2
   cpuset_load_balance 11 TINFO:  sched load balance: 1
   cpuset_load_balance 11 TFAIL: load balance test failed.
   cpuset_load_balance 13 TINFO: general group load balance test
   cpuset_load_balance 13 TINFO: root group info:
   cpuset_load_balance 13 TINFO:  sched load balance: 0
   cpuset_load_balance 13 TINFO: general group info:
   cpuset_load_balance 13 TINFO:  cpus: 
0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39
   cpuset_load_balance 13 TINFO:  sched load balance: 1
   cpuset_load_balance 13 TFAIL: load balance test failed.
   cpuset_load_balance 15 TINFO: general group load balance test
   cpuset_load_balance 15 TINFO: root group info:
   cpuset_load_balance 15 TINFO:  sched load balance: 0
   cpuset_load_balance 15 TINFO: general group1 info:
   cpuset_load_balance 15 TINFO:  cpus: 1
   cpuset_load_balance 15 TINFO:  sched load balance: 1
   cpuset_load_balance 15 TINFO: general group2 info:
   cpuset_load_balance 15 TINFO:  cpus: 0
   cpuset_load_balance 15 TINFO:  sched load balance: 1
   cpuset_load_balance 15 TINFO: CPU hotplug: none
   cpuset_load_balance 15 TFAIL: load balance test failed.
   cpuset_load_balance 17 TINFO: general group load balance test
   cpuset_load_balance 17 TINFO: root group info:
   cpuset_load_balance 17 TINFO:  sched load balance: 0
   cpuset_load_balance 17 TINFO: general group1 info:
   cpuset_load_balance 17 TINFO:  cpus: 1,2
   cpuset_load_balance 17 TINFO:  sched load balance: 1
   cpuset_load_balance 17 TINFO: general group2 info:
   cpuset_load_balance 17 TINFO:  cpus: 0-3
   cpuset_load_balance 17 TINFO:  sched load balance: 0
   cpuset_load_balance 17 TINFO: CPU hotplug: none
   cpuset_load_balance 17 TFAIL: load balance test failed.
   cpuset_load_balance 19 TINFO: general group load balance test
   cpuset_load_balance 19 TINFO: root group info:
   cpuset_load_balance 19 TINFO:  sched load balance: 0
   cpuset_load_balance 19 TINFO: 

[Kernel-packages] [Bug 1830359] Re: cpuset_base_ops from controller test suite in LTP failed

2019-07-10 Thread Po-Hsu Lin
** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   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/1830359

Title:
  cpuset_base_ops from controller 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:
  New
Status in linux source package in Disco:
  New

Bug description:
  Issue found on Disco with node glameow:
   startup='Fri May 24 10:23:44 2019'
   cpuset_base_ops 1 TPASS: cpuset.cpus(READONLY): Get the expected string
   cpuset_base_ops 3 TPASS: cpuset.mems(READONLY): Get the expected string
   cpuset_base_ops 5 TPASS: cpuset.memory_pressure(READONLY): Get the expected 
string
   cpuset_base_ops 7 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 9 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 11 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 13 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 15 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 17 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 19 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 21 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 23 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 25 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 27 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 29 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 31 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 33 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 35 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 37 TFAIL: cpuset.cpus: Test result -  Expected string - "0"
   cpuset_base_ops 39 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 41 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 43 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 45 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 47 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 49 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 51 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 53 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 55 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 57 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 59 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 61 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 63 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 65 TFAIL: cpuset.mems: Test result -  Expected string - "0"
   cpuset_base_ops 67 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 69 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 71 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 73 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 75 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 77 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 79 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 81 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 83 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 85 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 87 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 89 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 91 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 93 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 95 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 97 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 99 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 101 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 103 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 105 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 107 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 109 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 111 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 113 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 115 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 117 TPASS: cpuset.memory_spread_slab: Get the expected string
   cpuset_base_ops 119 TPASS: cpuset.memory_spread_slab: Get the expected string
   

[Kernel-packages] [Bug 1808107] Re: fanotify11 in ubuntu_ltp_syscalls failed

2019-07-10 Thread Po-Hsu Lin
Mark this as invalid for Xenial, this issue should be tracked in bug
1775165 for fanotify07

** Also affects: linux (Ubuntu Trusty)
   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/1808107

Title:
  fanotify11 in ubuntu_ltp_syscalls failed

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

Bug description:
  Timeouted on Trusty:
   startup='Tue Dec 11 11:58:36 2018'
   tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
   fanotify11.c:85: INFO: without FAN_REPORT_TID: tgid=5447, tid=5448, 
event.pid=5447
   fanotify11.c:89: PASS: event.pid == tgid
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Cannot kill test processes!
   Congratulation, likely test hit a kernel bug.
   Exitting uncleanly...
   tag=fanotify11 stime=1544529516 dur=350 exit=exited stat=1 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1808107/+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 1808107] Re: fanotify11 in ubuntu_ltp_syscalls failed

2019-07-10 Thread Po-Hsu Lin
Mark this as invalid, this issue should be tracked in bug 1775165 for
fanotify07

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

Title:
  fanotify11 in ubuntu_ltp_syscalls failed

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

Bug description:
  Timeouted on Trusty:
   startup='Tue Dec 11 11:58:36 2018'
   tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
   fanotify11.c:85: INFO: without FAN_REPORT_TID: tgid=5447, tid=5448, 
event.pid=5447
   fanotify11.c:89: PASS: event.pid == tgid
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Cannot kill test processes!
   Congratulation, likely test hit a kernel bug.
   Exitting uncleanly...
   tag=fanotify11 stime=1544529516 dur=350 exit=exited stat=1 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1808107/+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 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed

2019-07-10 Thread Po-Hsu Lin
For Xenial 4.4, if you run this test after a clean reboot you will get:
<>>
tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop0'
incrementing stop
tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
mke2fs 1.42.13 (17-May-2015)
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:331: INFO: Test #0: ignore mount events created on a specific file
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3049 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3049 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3049 fd=15
fanotify10.c:398: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:398: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:398: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:398: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:398: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:398: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:331: INFO: Test #1: ignore exec mount events created on a specific 
file
fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel?
fanotify10.c:331: INFO: Test #2: don't ignore mount events created on another 
file
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3050 fd=15
fanotify10.c:331: INFO: Test #3: don't ignore exec mount events created on 
another file
fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel?
fanotify10.c:331: INFO: Test #4: ignore inode events created on a specific 
mount point
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3051 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3051 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3051 fd=15
fanotify10.c:392: FAIL: group 0 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:392: FAIL: group 1 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:392: FAIL: group 2 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:392: FAIL: group 0 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:392: FAIL: group 1 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:392: FAIL: group 2 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:331: INFO: Test #5: ignore exec inode events created on a specific 
mount point
fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel?
fanotify10.c:331: INFO: Test #6: don't ignore inode events created on another 
mount point
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3052 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3052 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3052 fd=15
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3052 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3052 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3052 fd=15
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3052 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3052 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3052 fd=15
fanotify10.c:331: INFO: Test #7: don't ignore exec inode events created on 
another mount point
fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel?
fanotify10.c:331: INFO: Test #8: ignore fs events created on a specific file
fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel?
fanotify10.c:331: INFO: Test #9: ignore exec fs events created on a specific 
file
fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel?
fanotify10.c:331: INFO: Test #10: don't ignore mount events created on another 
file
fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel?
fanotify10.c:331: INFO: Test #11: don't ignore exec mount events created on 
another file
fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel?
fanotify10.c:331: INFO: Test #12: ignore fs events created on a specific mount 
point
fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel?
fanotify10.c:331: INFO: Test #13: ignore exec fs events created on a specific 
mount point
fanotify10.c:226: CONF: FAN_OPEN_EXEC not 

[Kernel-packages] [Bug 1775165] Re: fanotify07/fanotify08 in LTP syscall test generates kernel trace with T/X/X-AWS kernel

2019-07-10 Thread Po-Hsu Lin
It turns out the culprit is fanotify07.

On Xenial, if you run fanotify08 after a clean reboot it will be fine.

@Matthew
Thanks for the work, do you mind submit your patches to the mailing list 
"kernel-t...@lists.ubuntu.com"? (The title of your cover-letter needs some fix)

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

Title:
  fanotify07/fanotify08 in LTP syscall test generates kernel trace with
  T/X/X-AWS kernel

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1775165

  [Impact]

  When userspace tasks which are processing fanotify permission events act 
  incorrectly, the fsnotify_mark_srcu SRCU is held indefinitely which causes
  the whole notification subsystem to hang. 

  This has been seen in production, and it can also be seen when running the 
  Linux Test Project testsuite, specifically fanotify07. 

  [Fix]

  Instead of holding the SRCU lock while waiting for userspace to respond, 
  which may never happen, or not in the order we are expecting, we drop the 
  fsnotify_mark_srcu SRCU lock before waiting for userspace response, and then 
  reacquire the lock again when userspace responds.

  The fixes are from a series of upstream commits:

  05f0e38724e8449184acd8fbf0473ee5a07adc6c (cherry-pick)
  9385a84d7e1f658bb2d96ab798393e4b16268aaa (backport)
  abc77577a669f424c5d0c185b9994f2621c52aa4 (backport)

  The following are upstream commits necessary for the fixes to
  function:

  35e481761cdc688dbee0ef552a13f49af8eba6cc (backport)
  0918f1c309b86301605650c836ddd2021d311ae2 (cherry-pick)

  [Testcase]

  You can reproduce the problem pretty quickly with the Linux Test
  Project:

  Steps (with root):
1. sudo apt-get install git xfsprogs -y
2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
3. cd ltp
4. make autotools
5. ./configure
6. make; make install
7. cd /opt/ltp
8. echo -e "fanotify07 fanotify07 \nfanotify08 fanotify08" > /tmp/jobs
9. ./runltp -f /tmp/jobs

  On a stock Xenial kernel, the system will hang, and the testcase will look 
like:

  <<>>
  tag=fanotify07 stime=1554326200
  cmdline="fanotify07 "
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Test timeouted, sending SIGKILL!
  Cannot kill test processes!
  Congratulation, likely test hit a kernel bug.
  Exitting uncleanly...
  <<>>
  initiation_status="ok"
  duration=350 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  Looking at dmesg, we see the following call stack

  [  790.772792] LTP: starting fanotify07 (fanotify07 )
  [  960.140455] INFO: task fsnotify_mark:36 blocked for more than 120 seconds.
  [  960.140867]   Not tainted 4.4.0-142-generic #168-Ubuntu
  [  960.141185] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  960.141498] fsnotify_mark   D 8800b6703c98 036  2 
0x
  [  960.141516]  8800b6703c98 88013a558a00 8800b7797000 
8800b66f8000
  [  960.141524]  8800b6704000 7fff 8800b6703de0 
8800b66f8000
  [  960.141528]   8800b6703cb0 8185cb45 
8800b6703de8
  [  960.141532] Call Trace:
  [  960.141580]  [] schedule+0x35/0x80
  [  960.141588]  [] schedule_timeout+0x1b4/0x270
  [  960.141617]  [] ? mod_timer+0x10c/0x240
  [  960.141621]  [] ? __schedule+0x30d/0x810
  [  960.141625]  [] wait_for_completion+0xb2/0x190
  [  960.141636]  [] ? wake_up_q+0x70/0x70
  [  960.141641]  [] __synchronize_srcu+0x100/0x1a0
  [  960.141645]  [] ? 
trace_raw_output_rcu_utilization+0x60/0x60
  [  960.141664]  [] ? fsnotify_put_mark+0x40/0x40
  [  960.141669]  [] synchronize_srcu+0x24/0x30
  [  960.141672]  [] fsnotify_mark_destroy+0x84/0x130
  [  960.141680]  [] ? wake_atomic_t_function+0x60/0x60
  [  960.141691]  [] kthread+0xe7/0x100
  [  960.141694]  [] ? __schedule+0x301/0x810
  [  960.141699]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  960.141703]  [] ret_from_fork+0x55/0x80
  [  960.141706]  [] ? kthread_create_on_node+0x1e0/0x1e0

  The vanilla 4.4 kernel also shows the same call stack.

  On a patched kernel, the test will pass successfully, and there will be no
  messages in dmesg. 

  [Regression Potential]

  This makes modifications to how locking is performed in fsnotify / fanotify 
and 
  there may 

[Kernel-packages] [Bug 1775153] Re: fanotify09 in LTP syscall test failed with T/X/A kernel

2019-07-10 Thread Po-Hsu Lin
The timeout in X was caused by some other failures in previous tests.

If you run this test on X after a clean reboot, it will be:
<<>>
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
incrementing stop
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=2590 fd=9 
path=/tmp/ltp-N2EML7bHjo/2rOQpx/mntpoint/tfile_2590
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=2590 fd=9 
path=/tmp/ltp-N2EML7bHjo/2rOQpx/mntpoint/tfile_2590
fanotify09.c:150: PASS: group 0 got event: mask 10 pid=2590 fd=10 
path=/tmp/ltp-N2EML7bHjo/2rOQpx/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
<<>>

So it's the second test that's failing, which was report in bug 1804594

Therefore I will invalid the xenial related task here.

** Tags removed: xenial

** Summary changed:

- fanotify09 in LTP syscall test failed with T/X/A kernel
+ fanotify09 test case 0 in LTP syscall test failed with T kernel

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

Title:
  fanotify09 test case 0 in LTP syscall test failed with T kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Artful:
  Won't Fix

Bug description:
  The "fanotify09" from the LTP syscall tests has failed on a testing
  node with A/T kernel installed.

  Steps (with root):
    1. sudo apt-get install git xfsprogs -y
    2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
    3. cd ltp
    4. make autotools
    5. ./configure
    6. make; make install
    7. cd /opt/ltp
    8. echo "fanotify09" > /tmp/jobs
    9. ./runltp -f /tmp/jobs

  <<>>
  tag=fanotify09 stime=1528192114
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9
  fanotify09.c:182: FAIL: group 1 got event
  fanotify09.c:182: FAIL: group 2 got event

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-43-generic 4.13.0-43.48
  ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16
  Uname: Linux 4.13.0-43-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 08:30 seq
   crw-rw 1 root audio 116, 33 Jun  5 08:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: arm64
  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  5 09:14:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-43-generic N/A
   linux-backports-modules-4.13.0-43-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1804594] Re: fanotify09 in LTP failed with first group got more than 2 events

2019-07-10 Thread Po-Hsu Lin
** Tags added: xenial

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

** Summary changed:

- fanotify09 in LTP failed with first group got more than 2 events
+ fanotify09 test case 1 in LTP failed with first group got more than 2 events

-- 
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 test case 1 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 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:
  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 1828813] Re: fanotify12 in ubuntu_ltp_syscalls test failed on X

2019-07-10 Thread Po-Hsu Lin
This test will pass on X-4.4 as well, if you run it directly with a clean 
reboot.
<<>>
incrementing stop
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
fanotify12.c:137: INFO: Test #0: inode mark, FAN_OPEN events
fanotify12.c:239: PASS: Received event: mask=20, pid=1487, fd=7
fanotify12.c:239: PASS: Received event: mask=20, pid=1487, fd=8
fanotify12.c:137: INFO: Test #1: inode mark, FAN_OPEN_EXEC events
fanotify12.c:147: CONF: FAN_OPEN_EXEC not supported in kernel?
fanotify12.c:137: INFO: Test #2: inode mark, FAN_OPEN | FAN_OPEN_EXEC events
fanotify12.c:147: CONF: FAN_OPEN_EXEC not supported in kernel?
fanotify12.c:137: INFO: Test #3: inode mark, FAN_OPEN events, ignore 
FAN_OPEN_EXEC
fanotify12.c:174: CONF: FAN_OPEN_EXEC not supported in kernel?
fanotify12.c:137: INFO: Test #4: inode mark, FAN_OPEN_EXEC events, ignore 
FAN_OPEN
fanotify12.c:147: CONF: FAN_OPEN_EXEC not supported in kernel?
fanotify12.c:137: INFO: Test #5: inode mark, FAN_OPEN | FAN_OPEN_EXEC events, 
ignore FAN_OPEN_EXEC
fanotify12.c:147: CONF: FAN_OPEN_EXEC not supported in kernel?

Summary:
passed   2
failed   0
skipped  5
warnings 0

So it looks like this failure was caused by some other failures before
this (perhaps the fanotify07 / fanotify08)

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

Title:
  fanotify12 in ubuntu_ltp_syscalls test failed on X

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

Bug description:
   tag=fanotify12 stime=1557223465 dur=350 exit=exited stat=1 core=no cu=0 cs=0
   startup='Tue May 7 10:04:25 2019'
   tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
   fanotify12.c:137: INFO: Test #0: inode mark, FAN_OPEN events
   fanotify12.c:239: PASS: Received event: mask=20, pid=20859, fd=22
   fanotify12.c:239: PASS: Received event: mask=20, pid=20859, fd=23
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Cannot kill test processes!
   Congratulation, likely test hit a kernel bug.
   Exitting uncleanly...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828813/+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 1798524] Re: statx05 in ubuntu_ltp_syscalls failed with X-HWE-EDGE

2019-07-10 Thread Po-Hsu Lin
Issue reported upstream:
https://github.com/linux-test-project/ltp/issues/542

** Bug watch added: github.com/linux-test-project/ltp/issues #542
   https://github.com/linux-test-project/ltp/issues/542

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

** Tags added: 4.15

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

Title:
  statx05 in ubuntu_ltp_syscalls failed with X-HWE-EDGE

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

Bug description:
  
   tag=statx05 stime=1539405631
   cmdline="statx05"
   contacts=""
   analysis=exit
   <<>>
   tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
   tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
   tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts='-O 
encrypt -b 4096'
   mke2fs 1.42.13 (17-May-2015)
   Invalid filesystem option set: encrypt
   tst_mkfs.c:101: BROK: mkfs.ext4:1: statx05.c failed with 94

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798524/+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 1798524] Re: statx05 in ubuntu_ltp_syscalls failed with X-HWE-EDGE

2019-07-10 Thread Po-Hsu Lin
This is caused by the e2fsprogs package on Xenial.

e2fsprogs version> = 1.43 is required to support this flag.

** Tags added: ubuntu-ltp-syscalls xenial

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

Title:
  statx05 in ubuntu_ltp_syscalls failed with X-HWE-EDGE

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

Bug description:
  
   tag=statx05 stime=1539405631
   cmdline="statx05"
   contacts=""
   analysis=exit
   <<>>
   tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
   tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
   tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts='-O 
encrypt -b 4096'
   mke2fs 1.42.13 (17-May-2015)
   Invalid filesystem option set: encrypt
   tst_mkfs.c:101: BROK: mkfs.ext4:1: statx05.c failed with 94

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798524/+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 1813721] Re: SECURITY_SELINUX_DISABLE should be enable on X s390x

2019-07-09 Thread Po-Hsu Lin
** Also affects: qa-regression-testing
   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/1813721

Title:
  SECURITY_SELINUX_DISABLE should be enable on X s390x

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  == SRU Justification ==
  Security team requires the CONFIG_SECURITY_SELINUX_DISABLE should be
  enabled in all of our kernels.

  Currently it's not enabled for s390x in Xenial. And causing the
  test_081_config_security_selinux_disable test in ubuntu_kernel_security
  test suite complaining about this:

==
FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2158, in 
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', 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: SECURITY_SELINUX_DISABLE option was expected to be set in 
the kernel config

  == Test ==
  A test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1813721-s390x-selinux/

  This issue can be verified with a q-r-t test:
  test_081_config_security_selinux_disable, the test will pass with the
  patched kernel.

test_081_config_security_selinux_disable (__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315) ... 
(skipped: l) ok

  == Regression Potential ==
  Low, we already have this config enabled in all kernels except this
  specific Xenial s390x.


  --

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Tue Jan 29 02:30:42 2019
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-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 (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1813721/+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 1835614] Re: Touchpad not recognized

2019-07-09 Thread Po-Hsu Lin
Status changed to Incomplete as per request in comment #3

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

Title:
  Touchpad not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Ubuntu 19.04 installed on HP Omen 15ce-006nk
  I can not use the touchpad, it seems unrecognized by the OS
  I attached the output of cat /proc/bus/input/devices > devices

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  exo1549 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  6 16:40:01 2019
  InstallationDate: Installed on 2019-07-02 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:58e6 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 15-ce0xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=5c61d159-7664-4d88-86c0-b3884c70e5df ro acpi=off i18042.reset quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.178.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 838F
  dmi.board.vendor: HP
  dmi.board.version: 40.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.08:bd09/29/2017:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-ce0xx
  dmi.product.sku: 2HQ17EA#BH4
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835614/+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 1835054] Re: Missing NIC driver for Armada 8040 (Macchiatobin)

2019-07-09 Thread Po-Hsu Lin
Hello,

thanks for the feedback and the test.

I have submitted this patch for SRU:
https://lists.ubuntu.com/archives/kernel-team/2019-July/102028.html
We might need your help to test this once it got applied for the next cycle.

To note that it's unlikely to get installer image re-generated (except
for those daily build images). I have targeted the Eoan kernel (19.10)
as well, it should work out-of-box for Eoan in the future when it got
released if nothing goes wrong.

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
 Assignee: Po-Hsu Lin (cypressyew)
   Status: In Progress

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

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

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

Title:
  Missing NIC driver for Armada 8040 (Macchiatobin)

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  == SRU Justification ==
  The mvpp2 is a driver for network controllers(s) in Marvell SOCs, 
particularly Armada 8040.

  However this driver was neither enabled as a module or a built-in for
  Disco arm64.

  == Fix ==
  Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can solve 
this problem.

  Corresponding configs like CONFIG_ARCH_MVEBU and CONFIG_ARCH_MULTI_V7
  need to be enabled as well to meet the dependency requirement.

  CONFIG_CRYPTO_DEV_SAFEXCEL and CONFIG_PCI_AARDVARK are disabled
  explicitly to avoid interactive dialogues when building the kernel.

  == Test ==
  A test kernel for Disco ARM64 could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/

  User has confirmed that the patched kernel can fix this missing driver
  issue.

  == Regression Potential ==
  Low, this patch just make this driver to be built as a module, and we already 
have this enabled for armhf.

  
  == Original Bug Report ==

  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a module or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+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 1835054] Re: Missing NIC driver for Armada 8040 (Macchiatobin)

2019-07-09 Thread Po-Hsu Lin
** Description changed:

+ == SRU Justification ==
+ The mvpp2 is a driver for network controllers(s) in Marvell SOCs, 
particularly Armada 8040.
+ 
+ However this driver was neither enabled as a module or a built-in for
+ Disco arm64.
+ 
+ == Fix ==
+ Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can solve 
this problem.
+ 
+ Corresponding configs like CONFIG_ARCH_MVEBU and CONFIG_ARCH_MULTI_V7
+ need to be enabled as well to meet the dependency requirement.
+ 
+ CONFIG_CRYPTO_DEV_SAFEXCEL and CONFIG_PCI_AARDVARK are disabled
+ explicitly to avoid interactive dialogues when building the kernel.
+ 
+ == Test ==
+ A test kernel for Disco ARM64 could be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/
+ 
+ User has confirmed that the patched kernel can fix this missing driver
+ issue.
+ 
+ == Regression Potential ==
+ Low, this patch just make this driver to be built as a module, and we already 
have this enabled for armhf.
+ 
+ 
+ == Original Bug Report ==
+ 
  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a module or a built-in:
  
  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic
  $
  
  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a
  reasonably priced and performant server/mini-desktop platform.
  
  Could it be added, please, and the installer image re-generated.

** Tags added: arm64

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

Title:
  Missing NIC driver for Armada 8040 (Macchiatobin)

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  New

Bug description:
  == SRU Justification ==
  The mvpp2 is a driver for network controllers(s) in Marvell SOCs, 
particularly Armada 8040.

  However this driver was neither enabled as a module or a built-in for
  Disco arm64.

  == Fix ==
  Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can solve 
this problem.

  Corresponding configs like CONFIG_ARCH_MVEBU and CONFIG_ARCH_MULTI_V7
  need to be enabled as well to meet the dependency requirement.

  CONFIG_CRYPTO_DEV_SAFEXCEL and CONFIG_PCI_AARDVARK are disabled
  explicitly to avoid interactive dialogues when building the kernel.

  == Test ==
  A test kernel for Disco ARM64 could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/

  User has confirmed that the patched kernel can fix this missing driver
  issue.

  == Regression Potential ==
  Low, this patch just make this driver to be built as a module, and we already 
have this enabled for armhf.

  
  == Original Bug Report ==

  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a module or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+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 1835054] Re: Missing NIC driver for Armada 8040 (Macchiatobin)

2019-07-09 Thread Po-Hsu Lin
** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

Title:
  Missing NIC driver for Armada 8040 (Macchiatobin)

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  New

Bug description:
  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a module or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+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 1813721] Re: SECURITY_SELINUX_DISABLE should be enable on X s390x

2019-07-09 Thread Po-Hsu Lin
** Tags added: ubuntu-qrt-kernel-security

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

Title:
  SECURITY_SELINUX_DISABLE should be enable on X s390x

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

Bug description:
  == SRU Justification ==
  Security team requires the CONFIG_SECURITY_SELINUX_DISABLE should be
  enabled in all of our kernels.

  Currently it's not enabled for s390x in Xenial. And causing the
  test_081_config_security_selinux_disable test in ubuntu_kernel_security
  test suite complaining about this:

==
FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2158, in 
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', 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: SECURITY_SELINUX_DISABLE option was expected to be set in 
the kernel config

  == Test ==
  A test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1813721-s390x-selinux/

  This issue can be verified with a q-r-t test:
  test_081_config_security_selinux_disable, the test will pass with the
  patched kernel.

test_081_config_security_selinux_disable (__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315) ... 
(skipped: l) ok

  == Regression Potential ==
  Low, we already have this config enabled in all kernels except this
  specific Xenial s390x.


  --

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Tue Jan 29 02:30:42 2019
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-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 (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813721/+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 1813721] Re: SECURITY_SELINUX_DISABLE should be enable on X s390x

2019-07-08 Thread Po-Hsu Lin
** Description changed:

  == SRU Justification ==
- Security team requires the CONFIG_SECURITY_SELINUX_DISABLE to be enabled in 
all of our kernels.
+ Security team requires the CONFIG_SECURITY_SELINUX_DISABLE should be
+ enabled in all of our kernels.
+ 
+ Currently it's not enabled for s390x in Xenial. And causing the
+ test_081_config_security_selinux_disable test in ubuntu_kernel_security
+ test suite complaining about this:
+ 
+   ==
+   FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
+   Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
+   --
+   Traceback (most recent call last):
+ File "./test-kernel-security.py", line 2158, in 
test_081_config_security_selinux_disable
+   self.assertKernelConfig('SECURITY_SELINUX_DISABLE', 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: SECURITY_SELINUX_DISABLE option was expected to be set in 
the kernel config
  
  == Test ==
  A test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1813721-s390x-selinux/
  
- This issue can be verified with test_081_config_security_selinux_disable
- test from q-r-t, the test will pass with the patched kernel.
+ This issue can be verified with a q-r-t test:
+ test_081_config_security_selinux_disable, the test will pass with the
+ patched kernel.
  
test_081_config_security_selinux_disable (__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315) ... 
(skipped: l) ok
  
  == Regression Potential ==
- Low, we already have this config enabled in all kernels except this specific 
Xenial s390x.
+ Low, we already have this config enabled in all kernels except this
+ specific Xenial s390x.
  
- 
- == Original Bug Report ==
- 
- This test from q-r-t has failed exclusively on Xenial s390x:
-   ==
-   FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
-   Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
-   --
-   Traceback (most recent call last):
- File "./test-kernel-security.py", line 2158, in 
test_081_config_security_selinux_disable
-   self.assertKernelConfig('SECURITY_SELINUX_DISABLE', 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: SECURITY_SELINUX_DISABLE option was expected to be set in 
the kernel config
  
    --
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
  
  Date: Tue Jan 29 02:30:42 2019
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
  
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
  
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-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 (probably fresh install)

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

Title:
  SECURITY_SELINUX_DISABLE should be enable on X s390x

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

Bug 

[Kernel-packages] [Bug 1813721] Re: SECURITY_SELINUX_DISABLE should be enable on X s390x

2019-07-08 Thread Po-Hsu Lin
** Description changed:

+ == SRU Justification ==
+ Security team requires the CONFIG_SECURITY_SELINUX_DISABLE to be enabled in 
all of our kernels.
+ 
+ == Test ==
+ A test kernel could be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1813721-s390x-selinux/
+ 
+ This issue can be verified with test_081_config_security_selinux_disable
+ test from q-r-t, the test will pass with the patched kernel.
+ 
+   test_081_config_security_selinux_disable (__main__.KernelSecurityConfigTest)
+   Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315) ... 
(skipped: l) ok
+ 
+ == Regression Potential ==
+ Low, we already have this config enabled in all kernels except this specific 
Xenial s390x.
+ 
+ 
+ == Original Bug Report ==
+ 
  This test from q-r-t has failed exclusively on Xenial s390x:
-   ==
-   FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
-   Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
-   --
-   Traceback (most recent call last):
- File "./test-kernel-security.py", line 2158, in 
test_081_config_security_selinux_disable
-   self.assertKernelConfig('SECURITY_SELINUX_DISABLE', 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: SECURITY_SELINUX_DISABLE option was expected to be set in 
the kernel config
-   
-   --
+   ==
+   FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
+   Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
+   --
+   Traceback (most recent call last):
+ File "./test-kernel-security.py", line 2158, in 
test_081_config_security_selinux_disable
+   self.assertKernelConfig('SECURITY_SELINUX_DISABLE', 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: SECURITY_SELINUX_DISABLE option was expected to be set in 
the kernel config
+ 
+   --
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
-  
+ 
  Date: Tue Jan 29 02:30:42 2019
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
-  
+ 
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
-  
+ 
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-142-generic N/A
-  linux-backports-modules-4.4.0-142-generic  N/A
-  linux-firmware 1.157.21
+  linux-restricted-modules-4.4.0-142-generic N/A
+  linux-backports-modules-4.4.0-142-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 (probably fresh install)

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

Title:
  SECURITY_SELINUX_DISABLE should be enable on X s390x

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

Bug description:
  == SRU Justification ==
  Security team requires the CONFIG_SECURITY_SELINUX_DISABLE to be enabled in 
all of our kernels.

  == Test ==
  A test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1813721-s390x-selinux/

  This issue can be 

[Kernel-packages] [Bug 1813721] Re: SECURITY_SELINUX_DISABLE should be enable on X s390x

2019-07-08 Thread Po-Hsu Lin
** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

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

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => 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/1813721

Title:
  SECURITY_SELINUX_DISABLE should be enable on X s390x

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

Bug description:
  This test from q-r-t has failed exclusively on Xenial s390x:
==
FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2158, in 
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', 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: SECURITY_SELINUX_DISABLE option was expected to be set in 
the kernel config

--

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Tue Jan 29 02:30:42 2019
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-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 (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813721/+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 1808107] Re: fanotify11 in ubuntu_ltp_syscalls failed

2019-07-08 Thread Po-Hsu Lin
The test will pass if you run this directly:
tag=fanotify11 stime=1562574226
cmdline="fanotify11"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
fanotify11.c:66: INFO: Test #0: without FAN_REPORT_TID: tgid=2380, tid=0, 
event.pid=0
fanotify11.c:91: PASS: event.pid == tgid
fanotify11.c:66: INFO: Test #1: with FAN_REPORT_TID: tgid=2380, tid=2381, 
event.pid=2380
fanotify11.c:72: CONF: FAN_REPORT_TID not supported in kernel?

Summary:
passed   1
failed   0
skipped  1
warnings 0
<<>>
initiation_status="ok"

So this timeout failure is probably caused by some failures (fanotify07
or fanotify08) before this test.

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

Title:
  fanotify11 in ubuntu_ltp_syscalls failed

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

Bug description:
  Timeouted on Trusty:
   startup='Tue Dec 11 11:58:36 2018'
   tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
   fanotify11.c:85: INFO: without FAN_REPORT_TID: tgid=5447, tid=5448, 
event.pid=5447
   fanotify11.c:89: PASS: event.pid == tgid
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Cannot kill test processes!
   Congratulation, likely test hit a kernel bug.
   Exitting uncleanly...
   tag=fanotify11 stime=1544529516 dur=350 exit=exited stat=1 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1808107/+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 1828813] Re: fanotify12 in ubuntu_ltp_syscalls test failed on X

2019-07-08 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1828813

Title:
  fanotify12 in ubuntu_ltp_syscalls test failed on X

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

Bug description:
   tag=fanotify12 stime=1557223465 dur=350 exit=exited stat=1 core=no cu=0 cs=0
   startup='Tue May 7 10:04:25 2019'
   tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
   fanotify12.c:137: INFO: Test #0: inode mark, FAN_OPEN events
   fanotify12.c:239: PASS: Received event: mask=20, pid=20859, fd=22
   fanotify12.c:239: PASS: Received event: mask=20, pid=20859, fd=23
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Cannot kill test processes!
   Congratulation, likely test hit a kernel bug.
   Exitting uncleanly...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828813/+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 1775153] Re: fanotify09 in LTP syscall test failed with T/X/A kernel

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

** No longer affects: linux (Ubuntu Xenial)

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

Title:
  fanotify09 in LTP syscall test failed with T/X/A kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Artful:
  Won't Fix

Bug description:
  The "fanotify09" from the LTP syscall tests has failed on a testing
  node with A/T kernel installed.

  Steps (with root):
    1. sudo apt-get install git xfsprogs -y
    2. git clone --depth=1 https://github.com/linux-test-project/ltp.git
    3. cd ltp
    4. make autotools
    5. ./configure
    6. make; make install
    7. cd /opt/ltp
    8. echo "fanotify09" > /tmp/jobs
    9. ./runltp -f /tmp/jobs

  <<>>
  tag=fanotify09 stime=1528192114
  cmdline="fanotify09"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
  fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9
  fanotify09.c:182: FAIL: group 1 got event
  fanotify09.c:182: FAIL: group 2 got event

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-43-generic 4.13.0-43.48
  ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16
  Uname: Linux 4.13.0-43-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  5 08:30 seq
   crw-rw 1 root audio 116, 33 Jun  5 08:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: arm64
  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  5 09:14:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-43-generic N/A
   linux-backports-modules-4.13.0-43-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775153/+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] Re: fanotify06 from ubuntu_ltp_syscalls failed

2019-07-08 Thread Po-Hsu Lin
Checked with the recent SRU test result, this is failing with Xenial, it
needs to be investigated.

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

** Tags added: xenial

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

Bug description:
  == 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: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

  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.

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

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

2019-07-08 Thread Po-Hsu Lin
Passed with Disco amd64:
 startup='Fri Jul 5 03:52:26 2019'
 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:1100: 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=14414 fd=30
 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=14414 fd=30
 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=14414 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
 fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
 fanotify06.c:147: PASS: group 0 got event: mask 2 pid=14414 fd=30
 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=14414 fd=30
 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=14414 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

 Summary:
 passed 18
 failed 0
 skipped 0
 warnings 0


** Tags removed: verification-needed-disco
** Tags added: verification-done-disco

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 Xenial:
  New
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == 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: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

  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.

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

[Kernel-packages] [Bug 1835054] Re: Missing NIC driver for Armada 8040 (Macchiatobin)

2019-07-08 Thread Po-Hsu Lin
Hello,
can you give this ARM64 test kernel a try?
https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/

ubuntu@starmie-kernel:~$ grep MVPP /boot/config-5.0.0-2*
/boot/config-5.0.0-21-generic:CONFIG_MVPP2=m
ubuntu@starmie-kernel:~$ sudo modprobe mvpp2
ubuntu@starmie-kernel:~$ lsmod | grep mvpp2
mvpp2 110592  0
phylink36864  1 mvpp2


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

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

Title:
  Missing NIC driver for Armada 8040 (Macchiatobin)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a model or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic 
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+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 1829992] Re: zram02 from kernel_misc test suite in LTP failed

2019-07-03 Thread Po-Hsu Lin
This is probably caused by the unsuccessful zram01 test, which will
create 4 devices.


** No longer affects: linux (Ubuntu Cosmic)

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

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

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

Title:
  zram02 from kernel_misc test suite in LTP failed

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

Bug description:
  startup='Wed May 22 07:02:20 2019'
  zram02 1 TINFO: create '1' zram device(s)
  zram02 1 TFAIL: unexpected num of devices: 4
  zram02 2 TINFO: zram cleanup
  tag=zram02 stime=1558508540 dur=0 exit=exited stat=1 core=no cu=1 cs=0

  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 06:28 seq
   crw-rw 1 root audio 116, 33 May 22 06:28 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:
  CurrentDmesg:
   
  Date: Wed May 22 07:52:48 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/1829992/+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 1829991] Re: zram01 from kernel_misc test suite in LTP failed

2019-07-03 Thread Po-Hsu Lin
Confirmed to be a test case issue, invalid the kernel task.

Patch sent to upstream:
http://lists.linux.it/pipermail/ltp/2019-July/012617.html

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

** No longer affects: linux (Ubuntu 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/1829991

Title:
  zram01 from kernel_misc test suite in LTP failed

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

Bug description:
  startup='Wed May 22 07:02:19 2019'
  zram01 1 TINFO: create '4' zram device(s)
  zram01 1 TPASS: test succeeded
  zram01 2 TCONF: The device attribute max_comp_streams was introduced in 
kernel 3.15 and deprecated in 4.7
  zram01 2 TINFO: test that we can set compression algorithm
  /opt/ltp/testcases/bin/zram01.sh: 101: local: 842: bad variable name
  tag=zram01 stime=1558508539 dur=0 exit=exited stat=2 core=no cu=0 cs=1

  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 06:28 seq
   crw-rw 1 root audio 116, 33 May 22 06:28 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:
  CurrentDmesg:
   
  Date: Wed May 22 07:21:09 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/1829991/+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 1829991] Re: zram01 from kernel_misc test suite in LTP failed

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

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => 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/1829991

Title:
  zram01 from kernel_misc test suite in LTP failed

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

Bug description:
  startup='Wed May 22 07:02:19 2019'
  zram01 1 TINFO: create '4' zram device(s)
  zram01 1 TPASS: test succeeded
  zram01 2 TCONF: The device attribute max_comp_streams was introduced in 
kernel 3.15 and deprecated in 4.7
  zram01 2 TINFO: test that we can set compression algorithm
  /opt/ltp/testcases/bin/zram01.sh: 101: local: 842: bad variable name
  tag=zram01 stime=1558508539 dur=0 exit=exited stat=2 core=no cu=0 cs=1

  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 06:28 seq
   crw-rw 1 root audio 116, 33 May 22 06:28 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:
  CurrentDmesg:
   
  Date: Wed May 22 07:21:09 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/1829991/+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 1811819] Re: please include the kernel module VXLAN

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

Can you give this test kernel a try?
https://people.canonical.com/~phlin/kernel/lp-1811819-vxlan/X/

Config changed in this kernel:
+# CONFIG_GENEVE is not set
+# CONFIG_OPENVSWITCH_VXLAN is not set
-# CONFIG_VXLAN is not set
+CONFIG_VXLAN=m

$ sudo modprobe vxlan
$ lsmod | grep vxlan
vxlan  36864  0
ip6_udp_tunnel 12288  1 vxlan
udp_tunnel 12288  1 vxlan


Do you need this feature in other KVM kernels?
Thanks

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

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

Title:
  please include the kernel module VXLAN

Status in linux-kvm package in Ubuntu:
  Incomplete

Bug description:
  The kernel built with this packages does have VXLAN compiled.
  It would be nice if this could be fixed since VXLAN is used by Flannel and 
maybe other CNI plugins for Kubernetes.

  $ grep -i vxlan /boot/config-4.4.0-1039-kvm
  # CONFIG_VXLAN is not set

  When running a kubernetes cluster with Flannel with this image:

  $ kubectl logs kube-flannel-ds-amd64-jfkc8 -n kube-system 
--kubeconfig=case1-admin.conf 
  I0116 11:35:34.176962   1 main.go:475] Determining IP address of default 
interface
  I0116 11:35:34.177231   1 main.go:488] Using interface with name ens3 and 
address 10.32.192.14
  I0116 11:35:34.177259   1 main.go:505] Defaulting external address to 
interface address (10.32.192.14)
  I0116 11:35:34.191358   1 kube.go:131] Waiting 10m0s for node controller 
to sync
  I0116 11:35:34.273844   1 kube.go:294] Starting kube subnet manager
  I0116 11:35:35.274075   1 kube.go:138] Node controller sync successful
  I0116 11:35:35.274106   1 main.go:235] Created subnet manager: Kubernetes 
Subnet Manager - node-1-case1
  I0116 11:35:35.274113   1 main.go:238] Installing signal handlers
  I0116 11:35:35.274233   1 main.go:353] Found network config - Backend 
type: vxlan
  I0116 11:35:35.274292   1 vxlan.go:120] VXLAN config: VNI=1 Port=0 
GBP=false DirectRouting=false
  E0116 11:35:35.275803   1 main.go:280] Error registering network: 
operation not supported
  I0116 11:35:35.275860   1 main.go:333] Stopping shutdownHandler...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1811819/+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 1831595] Re: block_dev test from kernel_misc in LTP is causing kernel traces

2019-06-28 Thread Po-Hsu Lin
>From LTP upstream feedback, this seems to be an expected behaviour.

http://lists.linux.it/pipermail/ltp/2019-June/012255.html

Thus I'm closing this.

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

** Changed in: linux (Ubuntu)
   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/1831595

Title:
  block_dev test from kernel_misc in LTP is causing kernel traces

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

Bug description:
  Reproduce rate: 100%
  Steps:
1. git clone --depth=1 https://github.com/linux-test-project/ltp.git
2. cd ltp; make autotools; ./configure; make; sudo make install
3. Run the block_dev test:
   cd /opt/ltp/testcases/bin
   sudo ./block_dev

  All 7 test cases will pass, but there will be a kernel warning trace in dmesg:
  $ sudo ./block_dev 
  block_dev1  TPASS  :  Test-case '1'
  block_dev2  TPASS  :  Test-case '2'
  block_dev3  TPASS  :  Test-case '3'
  block_dev4  TPASS  :  Test-case '4'
  block_dev5  TPASS  :  Test-case '5'
  block_dev6  TPASS  :  Test-case '6'
  block_dev7  TPASS  :  Test-case '7'


  [  182.564296] ltp_block_dev: loading out-of-tree module taints kernel.
  [  182.564334] ltp_block_dev: module verification failed: signature and/or 
required key missing - tainting kernel
  [  182.564547] ltp_block_dev: Starting module
  [  182.564557] ltp_block_dev: device registered
  [  182.564698] ltp_block_dev: Test Case 1: register_blkdev() with auto 
allocating major numbers (major=0)
  [  182.564699] ltp_block_dev: Test Case Result: PASS
  [  182.564746] ltp_block_dev: Test Case 2: stress test of register_blkdev() 
with auto allocating major numbers (major=0)
  [  182.564776] register_blkdev: failed to get major for ltp_block_dev
  [  182.564776] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564777] register_blkdev: failed to get major for ltp_block_dev
  [  182.564777] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564777] register_blkdev: failed to get major for ltp_block_dev
  [  182.564778] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564778] register_blkdev: failed to get major for ltp_block_dev
  [  182.564778] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564779] register_blkdev: failed to get major for ltp_block_dev
  [  182.564779] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564780] register_blkdev: failed to get major for ltp_block_dev
  [  182.564780] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564780] register_blkdev: failed to get major for ltp_block_dev
  [  182.564781] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564781] register_blkdev: failed to get major for ltp_block_dev
  [  182.564781] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564782] register_blkdev: failed to get major for ltp_block_dev
  [  182.564782] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564782] register_blkdev: failed to get major for ltp_block_dev
  [  182.564783] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564783] register_blkdev: failed to get major for ltp_block_dev
  [  182.564784] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564784] register_blkdev: failed to get major for ltp_block_dev
  [  182.564784] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564785] register_blkdev: failed to get major for ltp_block_dev
  [  182.564785] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564785] register_blkdev: failed to get major for ltp_block_dev
  [  182.564786] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564786] register_blkdev: failed to get major for ltp_block_dev
  [  182.564786] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564787] register_blkdev: failed to get major for ltp_block_dev
  [  182.564787] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564788] register_blkdev: failed to get major for ltp_block_dev
  [  182.564788] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564788] register_blkdev: failed to get major for ltp_block_dev
  [  182.564789] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564789] register_blkdev: failed to get major for ltp_block_dev
  [  182.564789] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564790] register_blkdev: failed to get major for ltp_block_dev
  [  182.564790] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564790] register_blkdev: failed to get major for ltp_block_dev
  [  182.564791] ltp_block_dev: device is busy, register_blkdev() ret -16
  [  182.564791] register_blkdev: failed to get major for 

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

2019-06-28 Thread Po-Hsu Lin
** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Committed

-- 
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:
  Fix Committed
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 1830682] Re: cve-2017-5754 from cve test suite in LTP failed with KVM kernel

2019-06-28 Thread Po-Hsu Lin
http://lists.linux.it/pipermail/ltp/2019-June/012567.html

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

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

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

-- 
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:
  In Progress
Status in linux-kvm package in Ubuntu:
  Invalid

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 1782727] Re: DCCP protocol not enabled on KVM kernel - is this intentional?

2019-06-28 Thread Po-Hsu Lin
As per Kamal's comment, marking this as "Won't Fix" until any customer
asks for this.

** Changed in: linux-kvm (Ubuntu)
   Status: New => Won't Fix

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

Title:
  DCCP protocol not enabled on KVM kernel - is this intentional?

Status in linux-kvm package in Ubuntu:
  Won't Fix

Bug description:
  kvm 4.15.0 kernels don't have DCCP [1] enabled by default unlike our
  generic kernel.  Is this intentional?

  [1] https://en.wikipedia.org/wiki/Datagram_Congestion_Control_Protocol

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1782727/+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 1782728] Re: crypto AF_ALG protocol not enabled on KVM - is this intentional?

2019-06-28 Thread Po-Hsu Lin
As per Kamal's comment, marking this as "Won't Fix" until any customer
asks for this.

** Changed in: linux-kvm (Ubuntu)
   Status: New => Won't Fix

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

Title:
  crypto AF_ALG protocol not enabled on KVM - is this intentional?

Status in linux-kvm package in Ubuntu:
  Won't Fix

Bug description:
  The 4.15.0 KVM kernels do not enable AF_ALG crypto [1] by default.
  This userspace crypto can be useful - so is it intentional for this to
  be disabled?

  [1] https://en.wikipedia.org/wiki/Crypto_API_(Linux)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1782728/+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-28 Thread Po-Hsu Lin
** Description changed:

  == SRU Justification ==
- Currently, when writing
+ Currently, when writing 2^64-1 or 2^63 into file-max: 
     echo 18446744073709551616 > /proc/sys/fs/file-max
  
- /proc/sys/fs/file-max will overflow and be set to 0 and make the system
- stuck with "Too many open files in system" error within seconds.
+ Will make the system stuck with "Too many open files in system" error
+ within seconds.
  
  The upper and lower limit need to be defined properly to avoid this.
+ (The case for passing 2^64 will be addressed in bug 1833935)
  
  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 ==
  Test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1834310-file-max/
  
  Tested OK on KVM nodes with the following command (extracted from the
  sysctl02 test case in LTP):
    $ cat /proc/sys/fs/file-max
    $ sudo sysctl -w -q fs.file-max=18446744073709551615
    $ cat /proc/sys/fs/file-max
    $ sudo sysctl -w -q fs.file-max=9223372036854775808
    $ cat /proc/sys/fs/file-max
  
  All three file-max output should be identical with the patched kernel.
  
  This is because the file-max value is parsed via
  __do_proc_doulongvec_minmax(), which does not report error when min or
  max are exceeded but it will just keep the old value instead.
  
  == Regression Potential ==
  Low, just adding boundaries to the file-max.
  And it's been applied in some of our kernels 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:
  Fix Released
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 2^64-1 or 2^63 into file-max: 
     echo 18446744073709551616 > /proc/sys/fs/file-max

  Will make the system stuck with "Too many open files in system" error
  within seconds.

  The upper and lower limit need to be defined properly to avoid this.
  (The case for passing 2^64 will be addressed in bug 1833935)

  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 

[Kernel-packages] [Bug 1833935] Re: Handle overflow in proc_get_long of sysctl

2019-06-28 Thread Po-Hsu Lin
https://lists.ubuntu.com/archives/kernel-team/2019-June/101710.html

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

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

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Incomplete

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

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

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

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

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

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

** No longer affects: linux-kvm (Ubuntu Xenial)

** No longer affects: linux-kvm (Ubuntu Cosmic)

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

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

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

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

** No longer affects: linux-kvm (Ubuntu Bionic)

** No longer affects: linux-kvm (Ubuntu Disco)

** No longer affects: linux-kvm (Ubuntu Eoan)

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

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

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

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

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

** Changed in: linux (Ubuntu Eoan)
   Status: Incomplete => 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:
  Handle overflow in proc_get_long of sysctl

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

Bug description:
  == SRU Justification ==
  With the upper / lower boundary confined in bug 1834310, the file-max
  is still suffering with overflow issue.

  This is because the simple_strtoul() used in proc_get_long() to parse
  user input explicitly ignores overflows. So when you tried to put 2^64
  into file-max, it will:
  # echo 18446744073709551616 > /proc/sys/fs/file-max
  # cat /proc/sys/fs/file-max
  0

  Which will cause your system to silently die behind your back.

  This issue was reported by the case 1 of the sysctl02 test in LTP:
  sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0

  
  == Fix ==
  * 7f2923c4 (sysctl: handle overflow in proc_get_long)

  A new strtoul_lenient() was introduced here to solve this issue, with
  extra check to notify userspace with -EINVAL.

  This patch can be cherry-picked into B/C/D/E, it needs some content
  adjustment for X.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1833935-proc_get_long/

  The attempt to set file-max to 2^64 will be rejected:
  $ sudo sysctl -w -q fs.file-max=18446744073709551616
  sysctl: setting key "fs.file-max": Invalid argument

  Tested and passed with these kernels on AMD64 KVM nodes.

  == Regression Potential ==
  Low, the newly introduced function strtoul_lenient() is just for
  proc_get_long here.

  
  == Original bug report ==
  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=exit

[Kernel-packages] [Bug 1833935] Re: Handle overflow in proc_get_long of sysctl

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

+ == SRU Justification ==
+ With the upper / lower boundary confined in bug 1834310, the file-max
+ is still suffering with overflow issue.
+ 
+ This is because the simple_strtoul() used in proc_get_long() to parse
+ user input explicitly ignores overflows. So when you tried to put 2^64
+ into file-max, it will:
+ # echo 18446744073709551616 > /proc/sys/fs/file-max
+ # cat /proc/sys/fs/file-max
+ 0
+ 
+ Which will cause your system to silently die behind your back.
+ 
+ This issue was reported by the case 1 of the sysctl02 test in LTP:
+ sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0
+ 
+ 
+ == Fix ==
+ * 7f2923c4 (sysctl: handle overflow in proc_get_long)
+ 
+ A new strtoul_lenient() was introduced here to solve this issue, with
+ extra check to notify userspace with -EINVAL.
+ 
+ This patch can be cherry-picked into B/C/D/E, it needs some content
+ adjustment for X.
+ 
+ == Test ==
+ Test kernels could be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1833935-proc_get_long/
+ 
+ The attempt to set file-max to 2^64 will be rejected:
+ $ sudo sysctl -w -q fs.file-max=18446744073709551616
+ sysctl: setting key "fs.file-max": Invalid argument
+ 
+ Tested and passed with these kernels on AMD64 KVM nodes.
+ 
+ == Regression Potential ==
+ Low, the newly introduced function strtoul_lenient() is just for
+ proc_get_long here.
+ 
+ 
+ == Original bug report ==
  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)

-- 
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:
  Handle overflow in proc_get_long of sysctl

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

Bug description:
  == SRU Justification ==
  With the upper / lower boundary confined in bug 1834310, the file-max
  is still suffering with overflow issue.

  This is because the simple_strtoul() used in proc_get_long() to parse
  user input explicitly ignores overflows. So when you tried to put 2^64
  into file-max, it will:
  # echo 18446744073709551616 > /proc/sys/fs/file-max
  # cat /proc/sys/fs/file-max
  0

  Which will cause your system to silently die behind your back.

  This issue was reported by the case 1 of the sysctl02 test in LTP:
  sysctl02 1 TFAIL: /proc/sys/fs/file-max overflows and set to 0

  
  == Fix ==
  * 7f2923c4 (sysctl: handle overflow in proc_get_long)

  A new strtoul_lenient() was introduced here to solve this issue, with
  extra check to notify userspace with -EINVAL.

  This patch can be cherry-picked into B/C/D/E, it needs some content
  adjustment for X.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1833935-proc_get_long/

  The attempt to set file-max to 2^64 will be rejected:
  $ sudo sysctl -w -q fs.file-max=18446744073709551616
  sysctl: setting key "fs.file-max": Invalid argument

  Tested and passed with these kernels on AMD64 KVM nodes.

  == Regression Potential ==
  Low, the newly introduced function strtoul_lenient() is just for
  proc_get_long here.

  
  == Original bug report ==
  Test complains about apparmor enabled.
  As it's enabled by default, I think we might 

[Kernel-packages] [Bug 1833935] Re: Handle overflow in proc_get_long of sysctl

2019-06-27 Thread Po-Hsu Lin
** Summary changed:

- sysctl02_sh from ubuntu_ltp failed with Cosmic kernel
+ Handle overflow in proc_get_long of sysctl

-- 
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:
  Handle overflow in proc_get_long of sysctl

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 1830584] Re: mkswap01_sh from commands test suite in LTP failed

2019-06-27 Thread Po-Hsu Lin
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1830584

Title:
  mkswap01_sh from commands test suite in LTP failed

Status in ubuntu-kernel-tests:
  Fix Released
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 1813118] Re: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9

2019-06-27 Thread Po-Hsu Lin
Hmm wait a second, I think I was check on P8 instead of P9, let me check
this again.

** Tags added: verification-needed-cosmic

** Tags removed: verification-done-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/1813118

Title:
  alignment test in powerpc from ubuntu_kernel_selftests failed on B/C
  Power9

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == Justification ==
  The copy_unaligned / paste_unaligned / paste_last_unaligned test in 
powerpc/alignment will fail on a Power9 node as which implements ISA 3.0B, but 
the test was designed base on ISA 3.0.

  From the commit message:
  This is a test of the ISA 3.0 "copy" instruction. That instruction has
  an L field, which if set to 1 specifies that "the instruction
  identifies the beginning of a move group" (pp 858). That's also
  referred to as "copy first" vs "copy".

  In ISA 3.0B the copy instruction does not have an L field, and the
  corresponding bit in the instruction must be set to 1.

  This test is generating a "copy" instruction, not a "copy first", and
  so on Power9 (which implements 3.0B), this results in an illegal
  instruction.

  So just drop the test entirely. We still have copy_first_unaligned to
  test the "copy first" behaviour.

  == Fix ==
  * 83039f22 (selftests/powerpc: Remove Power9 copy_unaligned test)

  Patch can be cherry-picked into C, for Bionic it needs patches for bug
  1828935 to land first (8d191587) to make it a clean cherry-pick.

  It's already landed in D and onward.

  == Test ==
  Tested on a Power9 server with Cosmic, the broken tests will be removed 
correctly.

  == Regression Potential ==
  Low.
  Code change limited to testing tools and just removing broken tests. We still 
have copy_first_unaligned to test the "copy first" behaviour.

  == Original Bug Report ==
  This issue was only spotted on Power9 system "balter", for Power8 system, it 
has passed (skipped, and marked as passed) with this test:

   TAP version 13
   selftests: copy_unaligned
   
   test: test_copy_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_copy_unaligned
   not ok 1..1 selftests: copy_unaligned [FAIL]
   selftests: copy_first_unaligned
   
   test: test_copy_first_unaligned
   tags: git_version:unknown
   success: test_copy_first_unaligned
   ok 1..2 selftests: copy_first_unaligned [PASS]
   selftests: paste_unaligned
   
   test: test_paste_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_paste_unaligned
   not ok 1..3 selftests: paste_unaligned [FAIL]
   selftests: paste_last_unaligned
   
   test: test_paste_last_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_paste_last_unaligned
   not ok 1..4 selftests: paste_last_unaligned [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 06:50 seq
   crw-rw 1 root audio 116, 33 Jan 24 06:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  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:
  Date: Thu Jan 24 07:05:20 2019
  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: 1.24 0.89 0.66 3/1412 8319
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3876 00:17:569 0 EOF
   2: FLOCK  ADVISORY  WRITE 3556 00:17:497 0 EOF
   3: FLOCK  ADVISORY  WRITE 4090 00:17:596 0 EOF
   4: POSIX  ADVISORY  WRITE 3955 00:17:571 0 EOF
   5: POSIX  ADVISORY  WRITE 1823 00:17:348 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-43-generic 

[Kernel-packages] [Bug 1813118] Re: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9

2019-06-27 Thread Po-Hsu Lin
PowerPC test passed as expected on baltar with Cosmic kernel.

** Tags removed: verification-needed-cosmic
** Tags added: verification-done-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/1813118

Title:
  alignment test in powerpc from ubuntu_kernel_selftests failed on B/C
  Power9

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == Justification ==
  The copy_unaligned / paste_unaligned / paste_last_unaligned test in 
powerpc/alignment will fail on a Power9 node as which implements ISA 3.0B, but 
the test was designed base on ISA 3.0.

  From the commit message:
  This is a test of the ISA 3.0 "copy" instruction. That instruction has
  an L field, which if set to 1 specifies that "the instruction
  identifies the beginning of a move group" (pp 858). That's also
  referred to as "copy first" vs "copy".

  In ISA 3.0B the copy instruction does not have an L field, and the
  corresponding bit in the instruction must be set to 1.

  This test is generating a "copy" instruction, not a "copy first", and
  so on Power9 (which implements 3.0B), this results in an illegal
  instruction.

  So just drop the test entirely. We still have copy_first_unaligned to
  test the "copy first" behaviour.

  == Fix ==
  * 83039f22 (selftests/powerpc: Remove Power9 copy_unaligned test)

  Patch can be cherry-picked into C, for Bionic it needs patches for bug
  1828935 to land first (8d191587) to make it a clean cherry-pick.

  It's already landed in D and onward.

  == Test ==
  Tested on a Power9 server with Cosmic, the broken tests will be removed 
correctly.

  == Regression Potential ==
  Low.
  Code change limited to testing tools and just removing broken tests. We still 
have copy_first_unaligned to test the "copy first" behaviour.

  == Original Bug Report ==
  This issue was only spotted on Power9 system "balter", for Power8 system, it 
has passed (skipped, and marked as passed) with this test:

   TAP version 13
   selftests: copy_unaligned
   
   test: test_copy_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_copy_unaligned
   not ok 1..1 selftests: copy_unaligned [FAIL]
   selftests: copy_first_unaligned
   
   test: test_copy_first_unaligned
   tags: git_version:unknown
   success: test_copy_first_unaligned
   ok 1..2 selftests: copy_first_unaligned [PASS]
   selftests: paste_unaligned
   
   test: test_paste_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_paste_unaligned
   not ok 1..3 selftests: paste_unaligned [FAIL]
   selftests: paste_last_unaligned
   
   test: test_paste_last_unaligned
   tags: git_version:unknown
   !! child died by signal 4
   failure: test_paste_last_unaligned
   not ok 1..4 selftests: paste_last_unaligned [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 06:50 seq
   crw-rw 1 root audio 116, 33 Jan 24 06:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  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:
  Date: Thu Jan 24 07:05:20 2019
  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: 1.24 0.89 0.66 3/1412 8319
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3876 00:17:569 0 EOF
   2: FLOCK  ADVISORY  WRITE 3556 00:17:497 0 EOF
   3: FLOCK  ADVISORY  WRITE 4090 00:17:596 0 EOF
   4: POSIX  ADVISORY  WRITE 3955 00:17:571 0 EOF
   5: POSIX  ADVISORY  WRITE 1823 00:17:348 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) 

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

2019-06-27 Thread Po-Hsu Lin
https://lists.ubuntu.com/archives/kernel-team/2019-June/101655.html

-- 
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:
  Fix Released
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 and make the
  system stuck with "Too many open files in system" error within
  seconds.

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

  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 ==
  Test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1834310-file-max/

  Tested OK on KVM nodes with the following command (extracted from the
  sysctl02 test case in LTP):
    $ cat /proc/sys/fs/file-max
    $ sudo sysctl -w -q fs.file-max=18446744073709551615
    $ cat /proc/sys/fs/file-max
    $ sudo sysctl -w -q fs.file-max=9223372036854775808
    $ cat /proc/sys/fs/file-max

  All three file-max output should be identical with the patched kernel.

  This is because the file-max value is parsed via
  __do_proc_doulongvec_minmax(), which does not report error when min or
  max are exceeded but it will just keep the old value instead.

  == Regression Potential ==
  Low, just adding boundaries to the file-max.
  And it's been applied in some of our kernels 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

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@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 with Cosmic kernel

2019-06-27 Thread Po-Hsu Lin
Test case 2 and 3 split into bug 1834310
Test case 1 will be addressed here.

-- 
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] Re: Handle overflow for file-max

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

  == SRU Justification ==
  Currently, when writing
     echo 18446744073709551616 > /proc/sys/fs/file-max
  
- /proc/sys/fs/file-max will overflow and be set to 0 and crashed the
- system.
+ /proc/sys/fs/file-max will overflow and be set to 0 and make the system
+ stuck with "Too many open files in system" error within seconds.
  
  The upper and lower limit need to be defined properly to avoid this.
  
  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 ==
  Test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1834310-file-max/
  
  Tested OK on KVM nodes with the following command (extracted from the
  sysctl02 test case in LTP):
-   $ cat /proc/sys/fs/file-max
-   $ sudo sysctl -w -q fs.file-max=18446744073709551615
-   $ cat /proc/sys/fs/file-max
-   $ sudo sysctl -w -q fs.file-max=9223372036854775808
-   $ cat /proc/sys/fs/file-max
+   $ cat /proc/sys/fs/file-max
+   $ sudo sysctl -w -q fs.file-max=18446744073709551615
+   $ cat /proc/sys/fs/file-max
+   $ sudo sysctl -w -q fs.file-max=9223372036854775808
+   $ cat /proc/sys/fs/file-max
  
  All three file-max output should be identical with the patched kernel.
  
  This is because the file-max value is parsed via
  __do_proc_doulongvec_minmax(), which does not report error when min or
  max are exceeded but it will just keep the old value instead.
  
  == Regression Potential ==
  Low, just adding boundaries to the file-max.
  And it's been applied in some of our kernels 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:
  Fix Released
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 and make the
  system stuck with "Too many open files in system" error within
  seconds.

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

  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 

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

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

  == SRU Justification ==
  Currently, when writing
     echo 18446744073709551616 > /proc/sys/fs/file-max
  
- /proc/sys/fs/file-max will overflow and be set to 0.
+ /proc/sys/fs/file-max will overflow and be set to 0 and crashed the
+ system.
  
- The upper and lower limit need to be defined properly to avoid this
- issue.
+ The upper and lower limit need to be defined properly to avoid this.
  
  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.
+ Test kernel could be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1834310-file-max/
+ 
+ Tested OK on KVM nodes with the following command (extracted from the
+ sysctl02 test case in LTP):
+   $ cat /proc/sys/fs/file-max
+   $ sudo sysctl -w -q fs.file-max=18446744073709551615
+   $ cat /proc/sys/fs/file-max
+   $ sudo sysctl -w -q fs.file-max=9223372036854775808
+   $ cat /proc/sys/fs/file-max
+ 
+ All three file-max output should be identical with the patched kernel.
+ 
+ This is because the file-max value is parsed via
+ __do_proc_doulongvec_minmax(), which does not report error when min or
+ max are exceeded but it will just keep the old value instead.
  
  == Regression Potential ==
  Low, just adding boundaries to the file-max.
- And it's been applied in some of our kernel for a while.
+ And it's been applied in some of our kernels 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

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Handle overflow for file-max

Status in linux package in Ubuntu:
  Fix Released
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 and crashed the
  system.

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

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

[Kernel-packages] [Bug 1824794] Re: acct01 in ubuntu_ltp_syscalls reported as a failure with B-KVM

2019-06-26 Thread Po-Hsu Lin
Issue reported upstream: https://github.com/linux-test-
project/ltp/issues/540

** Bug watch added: github.com/linux-test-project/ltp/issues #540
   https://github.com/linux-test-project/ltp/issues/540

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

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

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

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

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 1824794] Re: acct01 in ubuntu_ltp_syscalls reported as a failure with B-KVM

2019-06-26 Thread Po-Hsu Lin
This issue was caused by the cleanup function, it will try to run SAFE_UNLINK() 
in the end of the test:
SAFE_UNLINK(TEST_TMPFILE);
SAFE_UNLINK(TEST_ELOOP);

As these should be the cleanup for the SAFE_SYMLINK() in the test:
SAFE_SYMLINK(TEST_ELOOP, "test_file_eloop2");
SAFE_SYMLINK("test_file_eloop2", TEST_ELOOP);

But the test was skipped due to the config issue. And the SAFE_UNLINK()
causes the ENOENT warning.

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

  1   2   3   4   5   6   7   8   9   10   >