[Kernel-packages] [Bug 1824690] Re: proc_thermal flooding dmesg

2019-04-23 Thread Colin Ian King
Thanks Srinivas for the update. If you can let us know when the patch
has landed I can add this into the older kernels as part of a SRU
procedure.

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

Title:
  proc_thermal flooding dmesg

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  New

Bug description:
  [   11.520358] proc_thermal :00:00.1: Unsupported event [0x91]
  [   16.532358] proc_thermal :00:00.1: Unsupported event [0x91]
  [   21.572719] proc_thermal :00:00.1: Unsupported event [0x91]
  [   26.580855] proc_thermal :00:00.1: Unsupported event [0x91]
  [   31.588851] proc_thermal :00:00.1: Unsupported event [0x91]
  [   36.592827] proc_thermal :00:00.1: Unsupported event [0x91]
  [   41.572682] random: crng init done
  [   41.572690] random: 7 urandom warning(s) missed due to ratelimiting

  Kernel 4.18.0-18-generic
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juno   1175 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-04-15 (0 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 1ea7:0064  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N24_25GU
  Package: thermald 1.7.0-5ubuntu2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=a23ca3ac-6284-45ce-9aa8-6670879910e7 ro quiet splash acpi_osi= 
acpi_os_name=Linux vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-generic N/A
   linux-backports-modules-4.18.0-18-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.18.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N24_25GU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.06:bd05/18/2018:svnNotebook:pnN24_25GU:pvrNotApplicable:rvnNotebook:rnN24_25GU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N24_25GU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824690/+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 1824690] Re: proc_thermal flooding dmesg

2019-04-23 Thread Colin Ian King
When a laptop reaches a CPU specific temperature threshold it will cause
rapid and immediate shutdown to avoid physically damaging the machine.
Older laptops sometimes have issues because the cooling paths are not
100% effective and can lead to overheating, so you may be OK with
disabling thermald if you laptop has good thermal dissipation.

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

Title:
  proc_thermal flooding dmesg

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  New

Bug description:
  [   11.520358] proc_thermal :00:00.1: Unsupported event [0x91]
  [   16.532358] proc_thermal :00:00.1: Unsupported event [0x91]
  [   21.572719] proc_thermal :00:00.1: Unsupported event [0x91]
  [   26.580855] proc_thermal :00:00.1: Unsupported event [0x91]
  [   31.588851] proc_thermal :00:00.1: Unsupported event [0x91]
  [   36.592827] proc_thermal :00:00.1: Unsupported event [0x91]
  [   41.572682] random: crng init done
  [   41.572690] random: 7 urandom warning(s) missed due to ratelimiting

  Kernel 4.18.0-18-generic
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juno   1175 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-04-15 (0 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 1ea7:0064  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N24_25GU
  Package: thermald 1.7.0-5ubuntu2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=a23ca3ac-6284-45ce-9aa8-6670879910e7 ro quiet splash acpi_osi= 
acpi_os_name=Linux vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-generic N/A
   linux-backports-modules-4.18.0-18-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.18.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N24_25GU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.06:bd05/18/2018:svnNotebook:pnN24_25GU:pvrNotApplicable:rvnNotebook:rnN24_25GU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N24_25GU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824690/+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 1824690] Re: proc_thermal flooding dmesg

2019-04-23 Thread Colin Ian King
This would require a kernel fix to disable this kernel message.

Perhaps just disabling thermald may be the best way forward for the
moment.

sudo systemctl disable thermald

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

Title:
  proc_thermal flooding dmesg

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  New

Bug description:
  [   11.520358] proc_thermal :00:00.1: Unsupported event [0x91]
  [   16.532358] proc_thermal :00:00.1: Unsupported event [0x91]
  [   21.572719] proc_thermal :00:00.1: Unsupported event [0x91]
  [   26.580855] proc_thermal :00:00.1: Unsupported event [0x91]
  [   31.588851] proc_thermal :00:00.1: Unsupported event [0x91]
  [   36.592827] proc_thermal :00:00.1: Unsupported event [0x91]
  [   41.572682] random: crng init done
  [   41.572690] random: 7 urandom warning(s) missed due to ratelimiting

  Kernel 4.18.0-18-generic
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juno   1175 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-04-15 (0 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 1ea7:0064  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N24_25GU
  Package: thermald 1.7.0-5ubuntu2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=a23ca3ac-6284-45ce-9aa8-6670879910e7 ro quiet splash acpi_osi= 
acpi_os_name=Linux vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-generic N/A
   linux-backports-modules-4.18.0-18-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.18.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N24_25GU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.06:bd05/18/2018:svnNotebook:pnN24_25GU:pvrNotApplicable:rvnNotebook:rnN24_25GU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N24_25GU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824690/+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 1825136] Re: ubuntu_nbd_smoke_test failed with 4.15 kernel

2019-04-17 Thread Colin Ian King
*** This bug is a duplicate of bug 1822247 ***
https://bugs.launchpad.net/bugs/1822247

** This bug has been marked a duplicate of bug 1822247
   ubuntu_nbd_smoke_test failed on P9 with Bionic 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/1825136

Title:
  ubuntu_nbd_smoke_test failed with 4.15 kernel

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

Bug description:
  ubuntu_nbd_smoke_test is failing with 4.15 kernel, can be reproduced
  on KVM / bare metals:

  creating backing nbd image /tmp/nbd_image.img

  

  Image path: /tmp/nbd_image.img
  Mount point: /mnt/nbd-test-11013
  Date: Fri Apr 12 00:41:45 UTC 2019
  Host: curly
  Kernel: 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019
  Machine: curly x86_64 x86_64
  CPUs online: 2
  CPUs total: 2
  Page size: 4096
  Pages avail: 249824
  Pages total: 510259
  Free space:
  Filesystem Size Used Avail Use% Mounted on
  udev 967M 0 967M 0% /dev
  tmpfs 200M 752K 199M 1% /run
  /dev/vda1 7.3G 4.1G 2.9G 59% /
  tmpfs 997M 0 997M 0% /dev/shm
  tmpfs 5.0M 0 5.0M 0% /run/lock
  tmpfs 997M 0 997M 0% /sys/fs/cgroup
  tmpfs 200M 0 200M 0% /run/user/1000
  


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

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

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

  creating large file /mnt/nbd-test-11013/largefile
  -rw-r--r-- 1 root root 100M Apr 12 00:41 /mnt/nbd-test-11013/largefile

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

  removing file /mnt/nbd-test-11013/largefile
  unmounting /mnt/nbd-test-11013
  stopping client
  disconnect, sock, done
  Found kernel warning, IO error and/or call trace
  echo
  [ 487.485530] creating backing nbd image /tmp/nbd_image.img
  [ 489.055452] NBD device /dev/nbd0 created
  [ 489.755524] found nbd export
  [ 490.810667] starting client with NBD device /dev/nbd0
  [ 490.819578] creating ext4 on /dev/nbd0
  [ 491.171437] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
  [ 491.369456] checking ext4 on /dev/nbd0
  [ 491.391980] EXT4-fs (nbd0): mounted filesystem with ordered data mode. 
Opts: (null)
  [ 491.403665] mounted on /dev/nbd0
  [ 491.406022] creating large file /mnt/nbd-test-11013/largefile
  [ 492.853579] removing file /mnt/nbd-test-11013/largefile
  [ 493.011021] unmounting /mnt/nbd-test-11013
  [ 494.062904] stopping client
  [ 494.066127] block nbd0: NBD_DISCONNECT
  [ 494.066593] block nbd0: shutting down sockets
  [ 494.066983] nbd0: detected capacity change from 0 to 134217728
  [ 494.067033] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.068313] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.069987] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.070790] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.071799] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.072608] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.073606] ldm_validate_partition_table(): Disk read failed.
  [ 494.073613] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.074400] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.075390] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.076206] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.077208] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.077995] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.078985] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.079772] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.080771] Dev nbd0: unable to read RDB block 0
  [ 494.081734] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.082522] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.083518] print_req_error: I/O error, dev nbd0, sector 24
  [ 494.084465] Buffer I/O error on dev nbd0, logical block 3, async page read
  [ 494.085729] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.086517] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.087509] nbd0: unable to read partition table
  [ 494.171320] Found kernel warning, IO error and/or call trace
  [ 494.171374] echo
  killing server
  

[Kernel-packages] [Bug 1825089] Re: enosys test in ubuntu_stress_smoke_test won't terminate after the test has finished

2019-04-17 Thread Colin Ian King
Fix committed: https://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=66c09c1a1b73d58855173474daaec98138926e62

Was accidentally killing a child before that child could complete a wait
and reap of it's own child.

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

Title:
  enosys test in ubuntu_stress_smoke_test won't terminate after the test
  has finished

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  On a s390x Bionic / Cosmic KVM, the enosys test is still running even
  the test has completed

  $ ps uax| grep stress
  ubuntu2037  0.0  0.4  93020  9564 ?Ssl  03:46   0:00 python3 
ckct/runner --cloud maas ubuntu_stress_smoke_test
  root  2383  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  root  2384  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  ubuntu   13161  0.0  0.0   6072   696 ttysclp0 S+   05:31   0:00 grep 
--color=auto stress
  root 19352  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19395  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19449  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19481  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable

  04:03:13 INFO | enosys STARTING
  04:03:13 INFO | enosys RETURNED 0
  04:03:13 INFO | enosys PASSED
  
  04:03:13 WARNI| Please verify 
/home/ubuntu/autotest/client/results/default/ubuntu_stress_smoke_test.stress-smoke-test/debug/crash.stress-ng-bad-a.13395
 for more info
  04:03:13 INFO |   GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13   completed successfully
  04:03:13 INFO |   END GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13
  04:03:13 DEBUG| Persistent state client._record_indent now set to 1
  04:03:13 DEBUG| Persistent state client.unexpected_reboot deleted
  04:03:13 INFO | END GOOD  timestamp=1555473793
localtime=Apr 17 04:03:13
  04:03:13 DEBUG| Persistent state client._record_indent now set to 0

  And the job on jenkins will eventually times out.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: User Name 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Wed Apr 17 05:28:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:

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

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=690e3389-e7e5-4fce-a58c-c7df1314da25
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825089/+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 1825089] Re: enosys test in ubuntu_stress_smoke_test won't terminate after the test has finished

2019-04-17 Thread Colin Ian King
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  enosys test in ubuntu_stress_smoke_test won't terminate after the test
  has finished

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

Bug description:
  On a s390x Bionic / Cosmic KVM, the enosys test is still running even
  the test has completed

  $ ps uax| grep stress
  ubuntu2037  0.0  0.4  93020  9564 ?Ssl  03:46   0:00 python3 
ckct/runner --cloud maas ubuntu_stress_smoke_test
  root  2383  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  root  2384  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  ubuntu   13161  0.0  0.0   6072   696 ttysclp0 S+   05:31   0:00 grep 
--color=auto stress
  root 19352  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19395  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19449  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19481  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable

  04:03:13 INFO | enosys STARTING
  04:03:13 INFO | enosys RETURNED 0
  04:03:13 INFO | enosys PASSED
  
  04:03:13 WARNI| Please verify 
/home/ubuntu/autotest/client/results/default/ubuntu_stress_smoke_test.stress-smoke-test/debug/crash.stress-ng-bad-a.13395
 for more info
  04:03:13 INFO |   GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13   completed successfully
  04:03:13 INFO |   END GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13
  04:03:13 DEBUG| Persistent state client._record_indent now set to 1
  04:03:13 DEBUG| Persistent state client.unexpected_reboot deleted
  04:03:13 INFO | END GOOD  timestamp=1555473793
localtime=Apr 17 04:03:13
  04:03:13 DEBUG| Persistent state client._record_indent now set to 0

  And the job on jenkins will eventually times out.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: User Name 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Wed Apr 17 05:28:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:

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

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=690e3389-e7e5-4fce-a58c-c7df1314da25
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825089/+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 1822247] Re: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel

2019-04-12 Thread Colin Ian King
Fix sent to mailing list: https://lists.ubuntu.com/archives/kernel-
team/2019-April/099806.html


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

Title:
  ubuntu_nbd_smoke_test failed on P9 with Bionic kernel

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

Bug description:
  == SRU Justification, BIONIC ==

  [Impact]

  Running the autotest regression test ubuntu_nbd_smoke occasionally
  trips I/O errors such as:

  [  700.668758] print_req_error: I/O error, dev nbd0, sector 0
  [  700.668840] Buffer I/O error on dev nbd0, logical block 0, async page read

  This happens when the nbd client detaches and the backing store is
  removed. The fix is to ensure a rescan occurs.

  [Fix]

  Upstream fix fe1f9e6659ca6124f500a0f829202c7c902fab0c (" nbd: fix how we set 
bd_invalidated"). If a disconnect action happens the
  partition table gets invalidated and rescanned properly.

  [Test]

  Without the fix running the Ubuntu Kernel Team nbd smoke test will
  occasionally trip the bug and the error message from the kernel
  appears and the test fails. With the fix, this test has been run tens
  of times without showing the failure.

  To test run:
  autotest/client/local-test autotest/client/tests/ubuntu_nbd_smoke_test/control

  [Regression Potential]

  This fix touches just the NBD driver and has been upstream since May
  2018 without any subsequent bug reports against it, so it is a known
  good fix. At most it sets the bd_invalidated flag more aggressively,
  so the rescan will occur, so I believe the regression potential is
  very limited just to ndb client connect/disconnect activity.

  -

  Reproduce rate: 2 out of 3 runs
  This issue can be found on other arches as well, normally it will fail with 
the first run and pass with the second attempt.

    * Command:
    
/home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke
    _test.sh
    Exit status: 1
    Duration: 7.90551400185

    stdout:
    creating backing nbd image /tmp/nbd_image.img

    

    Image path:/tmp/nbd_image.img
    Mount point:   /mnt/nbd-test-13924
    Date:  Fri Mar 29 06:06:04 UTC 2019
    Host:  baltar
    Kernel:4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019
    Machine:   baltar ppc64le ppc64le
    CPUs online:   160
    CPUs total:160
    Page size: 65536
    Pages avail:   1904339
    Pages total:   2089666
    Free space:
    Filesystem  Size  Used Avail Use% Mounted on
    udev 61G 0   61G   0% /dev
    tmpfs13G   12M   13G   1% /run
    /dev/sda2   1.8T   11G  1.7T   1% /
    tmpfs64G 0   64G   0% /dev/shm
    tmpfs   5.0M 0  5.0M   0% /run/lock
    tmpfs64G 0   64G   0% /sys/fs/cgroup
    tmpfs13G 0   13G   0% /run/user/1000
    


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

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

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

    creating large file /mnt/nbd-test-13924/largefile
    -rw-r--r-- 1 root root 100M Mar 29 06:06 /mnt/nbd-test-13924/largefile

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

    removing file /mnt/nbd-test-13924/largefile
    unmounting /mnt/nbd-test-13924
    stopping client
    disconnect, sock, done
    Found kernel warning, IO error and/or call trace
    echo
    [  694.662746] creating backing nbd image /tmp/nbd_image.img
    [  695.821047] NBD device /dev/nbd0 created
    [  696.271555] found nbd export
    [  697.318393] starting client with NBD device /dev/nbd0
    [  697.323210] creating ext4 on /dev/nbd0
    [  697.589620] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
    [  697.821953] checking ext4 on /dev/nbd0
    [  697.919173] EXT4-fs (nbd0): mounted filesystem with ordered data mode. 
Opts: (null)
    [  697.925418] mounted on /dev/nbd0
    [  697.927107] creating large file /mnt/nbd-test-13924/largefile
    [  698.839327] removing file 

[Kernel-packages] [Bug 1822175] Re: i3.metal flavour type fails to respond after a reboot

2019-04-05 Thread Colin Ian King
I can't repro this specific issue, I believe it may be a H/W issue as
reported in this bug.  Other reasons for the reboot tests failing are
marked in comment #3. Marking this as won't fix.

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

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

Title:
  i3.metal flavour type fails to respond after a reboot

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

Bug description:
  Series: Cosmic
  Instance Size: I3.Metal
  Region: (Default) US-WEST-2
  Kernel: linux-aws

  During SRU testing the i3.metal instance flavor type will sometimes
  fail to respond after the instance is rebooted. Usually this has been
  seen at least 2 or 3 times during at test cycle.

  While rebooting an I3.Metal instance on the AWS Cloud. I observed the
  following crash which resulting in tearing down the instance and
  starting over. The instance was only restarted ~4 times at the time of
  this failure.

  
  [[0;32m  OK  [0m] Reached target Shutdown.
  [[0;32m  OK  [0m] Reached target Final Step.
   Starting Reboot...
   Stopping LVM2 metadata daemon...
  [[0;32m  OK  [0m] Stopped LVM2 metadata daemon.
  [  447.340575] INFO: rcu_sched self-detected stall on CPU
  [  447.340577] INFO: rcu_sched self-detected stall on CPU
  [  447.340580] INFO: rcu_sched self-detected stall on CPU
  [  447.340587] INFO: rcu_sched self-detected stall on CPU
  [  447.340590] INFO: rcu_sched self-detected stall on CPU
  [  447.340592] INFO: rcu_sched self-detected stall on CPU
  [  447.340595] Uhhuh. NMI received for unknown reason 21 on CPU 0.
  [  447.340599] INFO: rcu_sched self-detected stall on CPU
  [  447.340602] INFO: rcu_sched self-detected stall on CPU
  [  447.340606] INFO: rcu_sched self-detected stall on CPU
  [  447.340614]53-...!: (43 GPs behind) idle=7ce/1/0 softirq=392/392 
fqs=0 
  [  447.340617] INFO: rcu_sched self-detected stall on CPU
  [  447.340621] Do you have a strange power saving mode enabled?
  [  447.340628]1-...!: (1 ticks this GP) idle=79e/1/0 softirq=881/881 
fqs=0 
  [  447.340632] INFO: rcu_sched self-detected stall on CPU
  [  447.340634] INFO: rcu_sched self-detected stall on CPU
  [  447.340636] INFO: rcu_sched self-detected stall on CPU
  [  447.340639] INFO: rcu_sched self-detected stall on CPU
  [  447.340641] INFO: rcu_sched self-detected stall on CPU
  [  447.340644] INFO: rcu_sched self-detected stall on CPU
  [  447.340647] INFO: rcu_sched self-detected stall on CPU

  The full log can be seen in the attached file.

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

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


[Kernel-packages] [Bug 1822175] Re: i3.metal flavour type fails to respond after a reboot

2019-04-03 Thread Colin Ian King
I've been running this for 3+ days now and cannot reproduce this
specific issue. From the look of the error it appears to be a hardware
related NMI issue, so perhaps we have some faulty H/W in this specific
case.

When running these tests for several days now with and without the
kernel parameters I have observed the following:

1. It can take >10-15 minutes for a reboot.
2. Our instances were being accidentally deleted by a jenkins job which could 
be a reason why some of our original assumptions that the VM had died on reboot 
were incorrect. 
3. When rebooting almost immediately when ssh access becomes available reboot 
gets stuck with systemd issues:

sudo reboot
systemctl status reboot.target
Failed to get properties: Connection timed out

and the only way to reboot is using the following:
sudo systemctl --force reboot

This could also be a reason why the automated reboot testing got locked
up and we mistakenly believed that reboots were failing due to H/W
issues.

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

Title:
  i3.metal flavour type fails to respond after a reboot

Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  Series: Cosmic
  Instance Size: I3.Metal
  Region: (Default) US-WEST-2
  Kernel: linux-aws

  During SRU testing the i3.metal instance flavor type will sometimes
  fail to respond after the instance is rebooted. Usually this has been
  seen at least 2 or 3 times during at test cycle.

  While rebooting an I3.Metal instance on the AWS Cloud. I observed the
  following crash which resulting in tearing down the instance and
  starting over. The instance was only restarted ~4 times at the time of
  this failure.

  
  [[0;32m  OK  [0m] Reached target Shutdown.
  [[0;32m  OK  [0m] Reached target Final Step.
   Starting Reboot...
   Stopping LVM2 metadata daemon...
  [[0;32m  OK  [0m] Stopped LVM2 metadata daemon.
  [  447.340575] INFO: rcu_sched self-detected stall on CPU
  [  447.340577] INFO: rcu_sched self-detected stall on CPU
  [  447.340580] INFO: rcu_sched self-detected stall on CPU
  [  447.340587] INFO: rcu_sched self-detected stall on CPU
  [  447.340590] INFO: rcu_sched self-detected stall on CPU
  [  447.340592] INFO: rcu_sched self-detected stall on CPU
  [  447.340595] Uhhuh. NMI received for unknown reason 21 on CPU 0.
  [  447.340599] INFO: rcu_sched self-detected stall on CPU
  [  447.340602] INFO: rcu_sched self-detected stall on CPU
  [  447.340606] INFO: rcu_sched self-detected stall on CPU
  [  447.340614]53-...!: (43 GPs behind) idle=7ce/1/0 softirq=392/392 
fqs=0 
  [  447.340617] INFO: rcu_sched self-detected stall on CPU
  [  447.340621] Do you have a strange power saving mode enabled?
  [  447.340628]1-...!: (1 ticks this GP) idle=79e/1/0 softirq=881/881 
fqs=0 
  [  447.340632] INFO: rcu_sched self-detected stall on CPU
  [  447.340634] INFO: rcu_sched self-detected stall on CPU
  [  447.340636] INFO: rcu_sched self-detected stall on CPU
  [  447.340639] INFO: rcu_sched self-detected stall on CPU
  [  447.340641] INFO: rcu_sched self-detected stall on CPU
  [  447.340644] INFO: rcu_sched self-detected stall on CPU
  [  447.340647] INFO: rcu_sched self-detected stall on CPU

  The full log can be seen in the attached file.

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

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


[Kernel-packages] [Bug 1822247] Re: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel

2019-04-02 Thread Colin Ian King
** Description changed:

+ == SRU Justification, BIONIC ==
+ 
+ Running the autotest regression test ubuntu_nbd_smoke occasionally trips
+ I/O errors such as:
+ 
+ [  700.668758] print_req_error: I/O error, dev nbd0, sector 0
+ [  700.668840] Buffer I/O error on dev nbd0, logical block 0, async page read
+ 
+ This happens when the nbd client detaches and the backing store is
+ removed. The fix is to ensure a rescan occurs.
+ 
+ == Fix ==
+ 
+ Upstream fix fe1f9e6659ca6124f500a0f829202c7c902fab0c (" nbd: fix how we set 
bd_invalidated"). If a disconnect action happens the
+ partition table gets invalidated and rescanned properly. 
+ 
+ == Testcase ==
+ 
+ Without the fix running the Ubuntu Kernel Team nbd smoke test will
+ occasionally trip the bug and the error message from the kernel appears
+ and the test fails. With the fix, this test has been run tens of times
+ without showing the failure.
+ 
+ To test run:
+ autotest/client/local-test autotest/client/tests/ubuntu_nbd_smoke_test/control
+ 
+ == Regression Potential ==
+ 
+ This fix touches just the NBD driver and has been upstream since May
+ 2018 without any subsequent bug reports against it, so it is a known
+ good fix. At most it sets the bd_invalidated flag more aggressively, so
+ the rescan will occur, so I believe the regression potential is very
+ limited just to ndb client connect/disconnect activity.
+ 
+ -
+ 
+ 
  Reproduce rate: 2 out of 3 runs
  This issue can be found on other arches as well, normally it will fail with 
the first run and pass with the second attempt.
  
- 
-   * Command: 
-   
/home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke
-   _test.sh
-   Exit status: 1
-   Duration: 7.90551400185
-   
-   stdout:
-   creating backing nbd image /tmp/nbd_image.img
-
-   

-   Image path:/tmp/nbd_image.img
-   Mount point:   /mnt/nbd-test-13924
-   Date:  Fri Mar 29 06:06:04 UTC 2019
-   Host:  baltar
-   Kernel:4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019
-   Machine:   baltar ppc64le ppc64le
-   CPUs online:   160
-   CPUs total:160
-   Page size: 65536
-   Pages avail:   1904339
-   Pages total:   2089666
-   Free space:
-   Filesystem  Size  Used Avail Use% Mounted on
-   udev 61G 0   61G   0% /dev
-   tmpfs13G   12M   13G   1% /run
-   /dev/sda2   1.8T   11G  1.7T   1% /
-   tmpfs64G 0   64G   0% /dev/shm
-   tmpfs   5.0M 0  5.0M   0% /run/lock
-   tmpfs64G 0   64G   0% /sys/fs/cgroup
-   tmpfs13G 0   13G   0% /run/user/1000
-   

-
-   NBD device /dev/nbd0 created
-   found nbd export
-   NBD exports found:
-   test
-   starting client with NBD device /dev/nbd0
-   Negotiation: ..size = 128MB
-   creating ext4 on /dev/nbd0
-   mkfs on /dev/nbd0 succeeded after 0 attempt(s)
-   checking ext4 on /dev/nbd0
-   fsck from util-linux 2.31.1
-   /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks
-   
-   mount: 
-   /dev/nbd0 on /mnt/nbd-test-13924 type ext4 (rw,relatime,data=ordered)
-   mounted on /dev/nbd0
-   
-   free: 
-   Filesystem 1K-blocks  Used Available Use% Mounted on
-   /dev/nbd0 122835  1550112111   2% /mnt/nbd-test-13924
-   
-   creating large file /mnt/nbd-test-13924/largefile
-   -rw-r--r-- 1 root root 100M Mar 29 06:06 /mnt/nbd-test-13924/largefile
-   
-   free: 
-   Filesystem 1K-blocks   Used Available Use% Mounted on
-   /dev/nbd0 122835 103951  9710  92% /mnt/nbd-test-13924
-   
-   removing file /mnt/nbd-test-13924/largefile
-   unmounting /mnt/nbd-test-13924
-   stopping client
-   disconnect, sock, done
-   Found kernel warning, IO error and/or call trace
-   echo
-   [  694.662746] creating backing nbd image /tmp/nbd_image.img
-   [  695.821047] NBD device /dev/nbd0 created
-   [  696.271555] found nbd export
-   [  697.318393] starting client with NBD device /dev/nbd0
-   [  697.323210] creating ext4 on /dev/nbd0
-   [  697.589620] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
-   [  697.821953] checking ext4 on /dev/nbd0
-   [  697.919173] EXT4-fs (nbd0): mounted filesystem with ordered data mode. 
Opts: (null)
-   [  697.925418] mounted on /dev/nbd0
-   [  697.927107] creating large file /mnt/nbd-test-13924/largefile
-   [  698.839327] removing file /mnt/nbd-test-13924/largefile
-   [  699.596736] unmounting /mnt/nbd-test-13924
-   [  700.664881] stopping client
-   [  700.667573] block nbd0: NBD_DISCONNECT
-   [  700.667733] block nbd0: shutting down sockets
-   [  700.668690] nbd0: detected capacity change from 0 to 134217728
-   [  700.668758] print_req_error: I/O error, dev nbd0, sector 0
-   [  700.668840] Buffer I/O error on dev nbd0, logical block 0, async page 
read
-   [  700.669068] print_req_error: I/O 

[Kernel-packages] [Bug 1822175] Re: i3.metal flavour type fails to respond after a reboot

2019-03-29 Thread Colin Ian King
I've been running 4 i3 instances running bionic, cosmic and xenial
without any boot hangs using the following kernel boot parameters:
nmi_watchdog=0 pcie_aspm=off nohpet

These have been running now for 8+ hours, with easily over 70 reboots
per instance w/o any issues. I'll try and factor out which one(s) are
the ones that are required.

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

Title:
  i3.metal flavour type fails to respond after a reboot

Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  Series: Cosmic
  Instance Size: I3.Metal
  Region: (Default) US-WEST-2
  Kernel: linux-aws

  During SRU testing the i3.metal instance flavor type will sometimes
  fail to respond after the instance is rebooted. Usually this has been
  seen at least 2 or 3 times during at test cycle.

  While rebooting an I3.Metal instance on the AWS Cloud. I observed the
  following crash which resulting in tearing down the instance and
  starting over. The instance was only restarted ~4 times at the time of
  this failure.

  
  [[0;32m  OK  [0m] Reached target Shutdown.
  [[0;32m  OK  [0m] Reached target Final Step.
   Starting Reboot...
   Stopping LVM2 metadata daemon...
  [[0;32m  OK  [0m] Stopped LVM2 metadata daemon.
  [  447.340575] INFO: rcu_sched self-detected stall on CPU
  [  447.340577] INFO: rcu_sched self-detected stall on CPU
  [  447.340580] INFO: rcu_sched self-detected stall on CPU
  [  447.340587] INFO: rcu_sched self-detected stall on CPU
  [  447.340590] INFO: rcu_sched self-detected stall on CPU
  [  447.340592] INFO: rcu_sched self-detected stall on CPU
  [  447.340595] Uhhuh. NMI received for unknown reason 21 on CPU 0.
  [  447.340599] INFO: rcu_sched self-detected stall on CPU
  [  447.340602] INFO: rcu_sched self-detected stall on CPU
  [  447.340606] INFO: rcu_sched self-detected stall on CPU
  [  447.340614]53-...!: (43 GPs behind) idle=7ce/1/0 softirq=392/392 
fqs=0 
  [  447.340617] INFO: rcu_sched self-detected stall on CPU
  [  447.340621] Do you have a strange power saving mode enabled?
  [  447.340628]1-...!: (1 ticks this GP) idle=79e/1/0 softirq=881/881 
fqs=0 
  [  447.340632] INFO: rcu_sched self-detected stall on CPU
  [  447.340634] INFO: rcu_sched self-detected stall on CPU
  [  447.340636] INFO: rcu_sched self-detected stall on CPU
  [  447.340639] INFO: rcu_sched self-detected stall on CPU
  [  447.340641] INFO: rcu_sched self-detected stall on CPU
  [  447.340644] INFO: rcu_sched self-detected stall on CPU
  [  447.340647] INFO: rcu_sched self-detected stall on CPU

  The full log can be seen in the attached file.

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

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


[Kernel-packages] [Bug 1822247] Re: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel

2019-03-29 Thread Colin Ian King
I've not been able to reproduce this on my VMs, can I get access to one
of these machines to figure out why it is failing and how to fix this.

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

Title:
  ubuntu_nbd_smoke_test failed on P9 with Bionic kernel

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

Bug description:
  Reproduce rate: 2 out of 3 runs
  This issue can be found on other arches as well, normally it will fail with 
the first run and pass with the second attempt.

  
* Command: 

/home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke
_test.sh
Exit status: 1
Duration: 7.90551400185

stdout:
creating backing nbd image /tmp/nbd_image.img
 


Image path:/tmp/nbd_image.img
Mount point:   /mnt/nbd-test-13924
Date:  Fri Mar 29 06:06:04 UTC 2019
Host:  baltar
Kernel:4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019
Machine:   baltar ppc64le ppc64le
CPUs online:   160
CPUs total:160
Page size: 65536
Pages avail:   1904339
Pages total:   2089666
Free space:
Filesystem  Size  Used Avail Use% Mounted on
udev 61G 0   61G   0% /dev
tmpfs13G   12M   13G   1% /run
/dev/sda2   1.8T   11G  1.7T   1% /
tmpfs64G 0   64G   0% /dev/shm
tmpfs   5.0M 0  5.0M   0% /run/lock
tmpfs64G 0   64G   0% /sys/fs/cgroup
tmpfs13G 0   13G   0% /run/user/1000


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

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

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

creating large file /mnt/nbd-test-13924/largefile
-rw-r--r-- 1 root root 100M Mar 29 06:06 /mnt/nbd-test-13924/largefile

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

removing file /mnt/nbd-test-13924/largefile
unmounting /mnt/nbd-test-13924
stopping client
disconnect, sock, done
Found kernel warning, IO error and/or call trace
echo
[  694.662746] creating backing nbd image /tmp/nbd_image.img
[  695.821047] NBD device /dev/nbd0 created
[  696.271555] found nbd export
[  697.318393] starting client with NBD device /dev/nbd0
[  697.323210] creating ext4 on /dev/nbd0
[  697.589620] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
[  697.821953] checking ext4 on /dev/nbd0
[  697.919173] EXT4-fs (nbd0): mounted filesystem with ordered data mode. 
Opts: (null)
[  697.925418] mounted on /dev/nbd0
[  697.927107] creating large file /mnt/nbd-test-13924/largefile
[  698.839327] removing file /mnt/nbd-test-13924/largefile
[  699.596736] unmounting /mnt/nbd-test-13924
[  700.664881] stopping client
[  700.667573] block nbd0: NBD_DISCONNECT
[  700.667733] block nbd0: shutting down sockets
[  700.668690] nbd0: detected capacity change from 0 to 134217728
[  700.668758] print_req_error: I/O error, dev nbd0, sector 0
[  700.668840] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  700.669068] print_req_error: I/O error, dev nbd0, sector 0
[  700.669124] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  700.669203] print_req_error: I/O error, dev nbd0, sector 0
[  700.669243] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  700.669315] ldm_validate_partition_table(): Disk read failed.
[  700.669324] print_req_error: I/O error, dev nbd0, sector 0
[  700.669364] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  700.669542] print_req_error: I/O error, dev nbd0, sector 0
[  700.669580] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  700.669646] print_req_error: I/O error, dev nbd0, sector 0
[  700.669686] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  700.669747] print_req_error: I/O error, dev nbd0, sector 0
[  700.669785] Buffer I/O error on 

[Kernel-packages] [Bug 1822247] Re: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel

2019-03-29 Thread Colin Ian King
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  ubuntu_nbd_smoke_test failed on P9 with Bionic kernel

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

Bug description:
  Reproduce rate: 2 out of 3 runs
  This issue can be found on other arches as well, normally it will fail with 
the first run and pass with the second attempt.

  
* Command: 

/home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke
_test.sh
Exit status: 1
Duration: 7.90551400185

stdout:
creating backing nbd image /tmp/nbd_image.img
 


Image path:/tmp/nbd_image.img
Mount point:   /mnt/nbd-test-13924
Date:  Fri Mar 29 06:06:04 UTC 2019
Host:  baltar
Kernel:4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019
Machine:   baltar ppc64le ppc64le
CPUs online:   160
CPUs total:160
Page size: 65536
Pages avail:   1904339
Pages total:   2089666
Free space:
Filesystem  Size  Used Avail Use% Mounted on
udev 61G 0   61G   0% /dev
tmpfs13G   12M   13G   1% /run
/dev/sda2   1.8T   11G  1.7T   1% /
tmpfs64G 0   64G   0% /dev/shm
tmpfs   5.0M 0  5.0M   0% /run/lock
tmpfs64G 0   64G   0% /sys/fs/cgroup
tmpfs13G 0   13G   0% /run/user/1000


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

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

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

creating large file /mnt/nbd-test-13924/largefile
-rw-r--r-- 1 root root 100M Mar 29 06:06 /mnt/nbd-test-13924/largefile

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

removing file /mnt/nbd-test-13924/largefile
unmounting /mnt/nbd-test-13924
stopping client
disconnect, sock, done
Found kernel warning, IO error and/or call trace
echo
[  694.662746] creating backing nbd image /tmp/nbd_image.img
[  695.821047] NBD device /dev/nbd0 created
[  696.271555] found nbd export
[  697.318393] starting client with NBD device /dev/nbd0
[  697.323210] creating ext4 on /dev/nbd0
[  697.589620] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
[  697.821953] checking ext4 on /dev/nbd0
[  697.919173] EXT4-fs (nbd0): mounted filesystem with ordered data mode. 
Opts: (null)
[  697.925418] mounted on /dev/nbd0
[  697.927107] creating large file /mnt/nbd-test-13924/largefile
[  698.839327] removing file /mnt/nbd-test-13924/largefile
[  699.596736] unmounting /mnt/nbd-test-13924
[  700.664881] stopping client
[  700.667573] block nbd0: NBD_DISCONNECT
[  700.667733] block nbd0: shutting down sockets
[  700.668690] nbd0: detected capacity change from 0 to 134217728
[  700.668758] print_req_error: I/O error, dev nbd0, sector 0
[  700.668840] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  700.669068] print_req_error: I/O error, dev nbd0, sector 0
[  700.669124] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  700.669203] print_req_error: I/O error, dev nbd0, sector 0
[  700.669243] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  700.669315] ldm_validate_partition_table(): Disk read failed.
[  700.669324] print_req_error: I/O error, dev nbd0, sector 0
[  700.669364] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  700.669542] print_req_error: I/O error, dev nbd0, sector 0
[  700.669580] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  700.669646] print_req_error: I/O error, dev nbd0, sector 0
[  700.669686] Buffer I/O error on dev nbd0, logical block 0, async page 
read
[  7

[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

2019-03-28 Thread Colin Ian King
@Sean, can you add the info for Joseph?

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

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description:   In the event a particular Azure cloud instance is
  rebooted it's possible that it may never recover and the instance will
  break indefinitely.

  In My case, it was a kernel panic. See specifics below..

  
  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  
  I had a simple script to reboot an instance (X) amount of times, I chose 50, 
so the machine would power cycle by issuing a "reboot" from the terminal prompt 
just as a user would.   Once the machine came up, it captured dmesg and other 
bits then rebooted again until it reached 50. 

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  
  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  
  this only occurred once in my testing.

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

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


[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.

2019-03-28 Thread Colin Ian King
I believe the "ERROR ExtHandler /proc/net/route contains no routes" is
from the "Azure Linux Agent", so that's proprietary code that I don't
have any idea how or why it is emitting that message.

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

Title:
  Azure Instance never recovered during series of instance reboots.

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description: During SRU Testing of various Azure Instances, there will
  be some cases where the instance will not respond following a system
  reboot.  SRU Testing only restarts a giving instance once, after it
  preps all of the necessary files to-be-tested.

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I initiated a series of tests which rebooted Azure Cloud instances 50
  times. During the 49th Reboot, an Instance failed to return from a
  reboot.. Upon grabbing the console output the following was seen
  scrolling endlessly. I have seen this failure in cases where the
  instance only restarted a handful of times >5

  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus

  In another test attempt I saw the following failure:

  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes

  
  Both of these failures broke networking, Both of these failures were seen at 
least twice to three times, thus may explain why in some cases we never recover 
from an instance reboot.

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

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


[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.

2019-03-28 Thread Colin Ian King
The "hyperv_fb: Unable to send packet via vmbus" message is from
synthvid_send(), drivers/video/fbdev/hyperv_fb.c (the Microsoft Hyper-V
Synthetic Video Frame Buffer Driver). This error occurs when
vmbus_sendpacket() fails to send a packet via the write ring buffer (see
hv_ringbuffer_write())

This failure is either because:

1. the channel->rescind is zero 
2. the ring buffer is full

adding some more debug into hv_ringbuffer_write in the error paths may
shed some more light on that.

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

Title:
  Azure Instance never recovered during series of instance reboots.

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description: During SRU Testing of various Azure Instances, there will
  be some cases where the instance will not respond following a system
  reboot.  SRU Testing only restarts a giving instance once, after it
  preps all of the necessary files to-be-tested.

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I initiated a series of tests which rebooted Azure Cloud instances 50
  times. During the 49th Reboot, an Instance failed to return from a
  reboot.. Upon grabbing the console output the following was seen
  scrolling endlessly. I have seen this failure in cases where the
  instance only restarted a handful of times >5

  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus

  In another test attempt I saw the following failure:

  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes

  
  Both of these failures broke networking, Both of these failures were seen at 
least twice to three times, thus may explain why in some cases we never recover 
from an instance reboot.

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

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


[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

2019-03-28 Thread Colin Ian King
So I don't think this is a kernel related issue.  The error message
"error while loading shared library" is being emitted from the libc
"fatal_error" shared library dynamic loader from init and an exit() is
being called, causing the kernel to report that init has exited, which
leads to the stack dump and the shutdown failure.

I suspect that there is some kind of race on shutdown causing systemd to
be unable to load a necessary shared library (perhaps the file system is
unmounted prematurely?) causing process 1 fail and hence to exit.

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

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description:   In the event a particular Azure cloud instance is
  rebooted it's possible that it may never recover and the instance will
  break indefinitely.

  In My case, it was a kernel panic. See specifics below..

  
  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  
  I had a simple script to reboot an instance (X) amount of times, I chose 50, 
so the machine would power cycle by issuing a "reboot" from the terminal prompt 
just as a user would.   Once the machine came up, it captured dmesg and other 
bits then rebooted again until it reached 50. 

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  
  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  
  this only occurred once in my testing.

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

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


[Kernel-packages] [Bug 1822175] Re: i3.metal flavour type fails to respond after a reboot

2019-03-28 Thread Colin Ian King
** Changed in: linux-aws (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  i3.metal flavour type fails to respond after a reboot

Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  Series: Cosmic
  Instance Size: I3.Metal
  Region: (Default) US-WEST-2
  Kernel: linux-aws

  During SRU testing the i3.metal instance flavor type will sometimes
  fail to respond after the instance is rebooted. Usually this has been
  seen at least 2 or 3 times during at test cycle.

  While rebooting an I3.Metal instance on the AWS Cloud. I observed the
  following crash which resulting in tearing down the instance and
  starting over. The instance was only restarted ~4 times at the time of
  this failure.

  
  [[0;32m  OK  [0m] Reached target Shutdown.
  [[0;32m  OK  [0m] Reached target Final Step.
   Starting Reboot...
   Stopping LVM2 metadata daemon...
  [[0;32m  OK  [0m] Stopped LVM2 metadata daemon.
  [  447.340575] INFO: rcu_sched self-detected stall on CPU
  [  447.340577] INFO: rcu_sched self-detected stall on CPU
  [  447.340580] INFO: rcu_sched self-detected stall on CPU
  [  447.340587] INFO: rcu_sched self-detected stall on CPU
  [  447.340590] INFO: rcu_sched self-detected stall on CPU
  [  447.340592] INFO: rcu_sched self-detected stall on CPU
  [  447.340595] Uhhuh. NMI received for unknown reason 21 on CPU 0.
  [  447.340599] INFO: rcu_sched self-detected stall on CPU
  [  447.340602] INFO: rcu_sched self-detected stall on CPU
  [  447.340606] INFO: rcu_sched self-detected stall on CPU
  [  447.340614]53-...!: (43 GPs behind) idle=7ce/1/0 softirq=392/392 
fqs=0 
  [  447.340617] INFO: rcu_sched self-detected stall on CPU
  [  447.340621] Do you have a strange power saving mode enabled?
  [  447.340628]1-...!: (1 ticks this GP) idle=79e/1/0 softirq=881/881 
fqs=0 
  [  447.340632] INFO: rcu_sched self-detected stall on CPU
  [  447.340634] INFO: rcu_sched self-detected stall on CPU
  [  447.340636] INFO: rcu_sched self-detected stall on CPU
  [  447.340639] INFO: rcu_sched self-detected stall on CPU
  [  447.340641] INFO: rcu_sched self-detected stall on CPU
  [  447.340644] INFO: rcu_sched self-detected stall on CPU
  [  447.340647] INFO: rcu_sched self-detected stall on CPU

  The full log can be seen in the attached file.

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

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


[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

2019-03-28 Thread Colin Ian King
Minor note: this appears to be a kernel panic during shutdown rather
than a boot hang issue.

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

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description:   In the event a particular Azure cloud instance is
  rebooted it's possible that it may never recover and the instance will
  break indefinitely.

  In My case, it was a kernel panic. See specifics below..

  
  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  
  I had a simple script to reboot an instance (X) amount of times, I chose 50, 
so the machine would power cycle by issuing a "reboot" from the terminal prompt 
just as a user would.   Once the machine came up, it captured dmesg and other 
bits then rebooted again until it reached 50. 

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  
  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  
  this only occurred once in my testing.

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

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


[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.

2019-03-28 Thread Colin Ian King
** Changed in: linux-azure (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Azure Instance never recovered during series of instance reboots.

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description: During SRU Testing of various Azure Instances, there will
  be some cases where the instance will not respond following a system
  reboot.  SRU Testing only restarts a giving instance once, after it
  preps all of the necessary files to-be-tested.

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I initiated a series of tests which rebooted Azure Cloud instances 50
  times. During the 49th Reboot, an Instance failed to return from a
  reboot.. Upon grabbing the console output the following was seen
  scrolling endlessly. I have seen this failure in cases where the
  instance only restarted a handful of times >5

  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus

  In another test attempt I saw the following failure:

  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes

  
  Both of these failures broke networking, Both of these failures were seen at 
least twice to three times, thus may explain why in some cases we never recover 
from an instance reboot.

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

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


[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

2019-03-28 Thread Colin Ian King
** Changed in: linux-azure (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description:   In the event a particular Azure cloud instance is
  rebooted it's possible that it may never recover and the instance will
  break indefinitely.

  In My case, it was a kernel panic. See specifics below..

  
  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  
  I had a simple script to reboot an instance (X) amount of times, I chose 50, 
so the machine would power cycle by issuing a "reboot" from the terminal prompt 
just as a user would.   Once the machine came up, it captured dmesg and other 
bits then rebooted again until it reached 50. 

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  
  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  
  this only occurred once in my testing.

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

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


[Kernel-packages] [Bug 1813847] Re: af-alg stressor triggers modprobe throttling

2019-03-28 Thread Colin Ian King
** Changed in: stress-ng
   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/1813847

Title:
  af-alg stressor triggers modprobe throttling

Status in Stress-ng:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Due to the combination of high core counts and perhaps a lack of
  available hash/crypto hardware acceleration drivers, arm64 server
  platforms generate a lot of noisy modprobe throttling messages when
  running the af-alg stressor. This appears to be partially mitigated in
  master by disabling hashes/ciphers once they are found to be not
  present. But, w/ 96 cores/hogs, we presumably still hit the kernel
  with 96 * (nr_hashes + nr_ciphers) before that mitigation takes
  effect, and that is sufficient to cause the kernel to emit throttling
  messages.

  
  $ sudo dmesg -c > /dev/null ; ./stress-ng --af-alg 0 --af-alg-ops=20; 
sudo dmesg -c
  stress-ng: info:  [76141] defaulting to a 86400 second (1 day, 0.00 secs) run 
per stressor
  stress-ng: info:  [76141] dispatching hogs: 96 af-alg
  stress-ng: info:  [76141] successful run completed in 0.40s
  [ 5808.489046] __request_module: 25 callbacks suppressed
  [ 5808.489050] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489503] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489724] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489731] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490092] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-xor-all, throttling...
  [ 5808.490235] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash-all, throttling...
  [ 5808.490308] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490367] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490597] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1813847/+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 1813847] Re: af-alg stressor triggers modprobe throttling

2019-03-21 Thread Colin Ian King
Fix committed: https://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=a4e26439837ce6e472b502da430ff863f6c7c265

** Changed in: stress-ng
   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/1813847

Title:
  af-alg stressor triggers modprobe throttling

Status in Stress-ng:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Due to the combination of high core counts and perhaps a lack of
  available hash/crypto hardware acceleration drivers, arm64 server
  platforms generate a lot of noisy modprobe throttling messages when
  running the af-alg stressor. This appears to be partially mitigated in
  master by disabling hashes/ciphers once they are found to be not
  present. But, w/ 96 cores/hogs, we presumably still hit the kernel
  with 96 * (nr_hashes + nr_ciphers) before that mitigation takes
  effect, and that is sufficient to cause the kernel to emit throttling
  messages.

  
  $ sudo dmesg -c > /dev/null ; ./stress-ng --af-alg 0 --af-alg-ops=20; 
sudo dmesg -c
  stress-ng: info:  [76141] defaulting to a 86400 second (1 day, 0.00 secs) run 
per stressor
  stress-ng: info:  [76141] dispatching hogs: 96 af-alg
  stress-ng: info:  [76141] successful run completed in 0.40s
  [ 5808.489046] __request_module: 25 callbacks suppressed
  [ 5808.489050] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489503] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489724] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489731] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490092] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-xor-all, throttling...
  [ 5808.490235] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash-all, throttling...
  [ 5808.490308] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490367] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490597] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1813847/+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 1788432] Re: 4.15 s390x kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!

2019-02-18 Thread Colin Ian King
Just to confirm that 2448a299ec416a80f699940a86f4a6d9a4f643b1 and
78b1a52e05c9db11d293342e8d6d8a230a04b4e7 are in the Ubuntu 5.0 kernel
since Ubuntu-5.0.0-0.1

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

Title:
  4.15 s390x kernel BUG at /build/linux-
  Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  uname -a
  Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 
s390x s390x s390x GNU/Linux

  and same for 4.15.0-29-generic and 4.17.0-8-generic

  Steps to reproduce this bug:

  git clone git://kernel.ubuntu.com/cking/stress-ng
  cd stress-ng
  make clean
  make

  And run with:

  ./stress-ng --sysfs 0 -t 60

  .. wait a few seconds and then:

  [  119.445891] [ cut here ]
  [  119.445898] kernel BUG at 
/build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!
  [  119.446093] illegal operation: 0001 ilc:1 [#3] SMP
  [  119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) 
icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 
des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common 
mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl 
lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk
  [  119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P  DO  
   4.15.0-33-generic #36-Ubuntu
  [  119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux)
  [  119.446170] Krnl PSW : 12d313d3 405835bc 
(virtblk_cache_type_show+0x82/0x88 [virtio_blk])
  [  119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [  119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 
6545
  [  119.446196]03ff800058da 6546 6bf537c0 
6b60a100
  [  119.446198] 00690648 7cc3de40 
7a74b000
  [  119.446202]03ff80008210  03ff800058da 
7ac1bce8
  [  119.446210] Krnl Code: 03ff80005912: ebbff0a80004  lmg 
%r11,%r15,168(%r15)
  [  119.446210]03ff80005918: c0f40560  brcl
15,3ff800063d8
  [  119.446210]   #03ff8000591e: a7f40001  brc 
15,3ff80005920
  [  119.446210]   >03ff80005922: 0707  bcr 0,%r7
  [  119.446210]03ff80005924: 0707  bcr 0,%r7
  [  119.446210]03ff80005926: 0707  bcr 0,%r7
  [  119.446210]03ff80005928: c004  brcl
0,3ff80005928
  [  119.446210]03ff8000592e: eb6ff0480024  stmg
%r6,%r15,72(%r15)
  [  119.446226] Call Trace:
  [  119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 
[virtio_blk])
  [  119.446234]  [<00690684>] dev_attr_show+0x3c/0x80
  [  119.446240]  [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8
  [  119.446259]  [<003b048c>] seq_read+0xec/0x4c8
  [  119.446262]  [<003821ea>] vfs_read+0x8a/0x150
  [  119.446274]  [<00382786>] SyS_read+0x66/0xe0
  [  119.446278]  [<008e3028>] system_call+0xdc/0x2c8
  [  119.446279] Last Breaking-Event-Address:
  [  119.446281]  [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 
[virtio_blk]
  [  119.446283]
  [  119.446284] ---[ end trace 2c2403d726047e4a ]---

  For  4.17.0-8-generic:
  [   25.170715] kernel BUG at drivers/block/virtio_blk.c:574!
  [   25.170795] illegal operation: 0001 ilc:1 [#1] SMP
  [   25.170797] Modules linked in: lttng_statedump(OE) lttng_clock(OE) 
lttng_lib_ring_buffer(OE) binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) 
isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 
des_generic sha512_s390 sha256_s390 sha1_s390 sha_common vfio_ccw vfio_mdev 
mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm nfsd 
ib_core auth_rpcgss iscsi_tcp nfs_acl lockd grace libiscsi_tcp libiscsi 
scsi_transport_iscsi sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 linear virtio_net virtio_blk crc32_vx_s390
  [   25.170835] CPU: 0 PID: 5590 Comm: stress-ng-sysfs Tainted: P   OE 
4.17.0-8-generic #9-Ubuntu
  [   25.170837] Hardware name: IBM 2964 N63 400 (KVM/Linux)
  [   25.170839] Krnl PSW : 05f0c968 26542d57 

[Kernel-packages] [Bug 1813899] Re: pthread in stress-smoke test failed on GCP X-4.15

2019-02-05 Thread Colin Ian King
** Changed in: stress-ng
   Status: Fix Committed => Fix Released

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

Title:
  pthread in stress-smoke test failed on GCP X-4.15

Status in Stress-ng:
  Fix Released
Status in ubuntu-kernel-tests:
  New
Status in linux-gcp package in Ubuntu:
  New

Bug description:
   4.15.0-1027-gcp #28~16.04.1-Ubuntu
   Only spotted on node n1-standard-8

   pthread FAILED
   stress-ng: debug: [19921] 1 processor online, 1 processor configured
   stress-ng: info:  [19921] dispatching hogs: 4 pthread
   stress-ng: debug: [19921] cache allocate: default cache size: 56320K
   stress-ng: debug: [19921] starting stressors
   stress-ng: debug: [19921] 4 stressors spawned
   stress-ng: debug: [19925] stress-ng-pthread: started [19925] (instance 3)
   stress-ng: debug: [19924] stress-ng-pthread: started [19924] (instance 2)
   stress-ng: debug: [19923] stress-ng-pthread: started [19923] (instance 1)
   stress-ng: debug: [19922] stress-ng-pthread: started [19922] (instance 0)
   stress-ng: debug: [19923] stress-ng-pthread: exited [19923] (instance 1)
   stress-ng: debug: [19922] stress-ng-pthread: exited [19922] (instance 0)
   stress-ng: debug: [19921] process [19922] terminated
   stress-ng: debug: [19924] stress-ng-pthread: exited [19924] (instance 2)
   stress-ng: fail:  [19924] stress-ng-pthread: mutex unlock failed, errno=22 
(Invalid argument)
   stress-ng: debug: [19921] process [19923] (stress-ng-pthread) terminated on 
signal: 11 (Segmentation fault)
   stress-ng: debug: [19921] process [19923] terminated
   stress-ng: debug: [19921] process [19924] terminated
   stress-ng: debug: [19921] process [19925] (stress-ng-pthread) terminated on 
signal: 11 (Segmentation fault)
   stress-ng: debug: [19921] process [19925] terminated
   stress-ng: info:  [19921] unsuccessful run completed in 5.05s

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1813899/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-02-01 Thread Colin Ian King
I see that the verification-done-cosmic tag has been set, I'll also set
the verification-done tag too

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

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  Fix Released
Status in thermald source package in Cosmic:
  Fix Committed
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

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

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


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

2019-02-01 Thread Colin Ian King
Can we re-run this to see if it's 100% reproduceable?

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

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

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

Bug description:
  Kernel: 4.15.0-45.48~16.04.1

  creating backing nbd image /tmp/nbd_image.img

  

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


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

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

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

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

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

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

[Kernel-packages] [Bug 1813847] Re: af-alg stressor triggers modprobe throttling

2019-01-31 Thread Colin Ian King
** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

Title:
  af-alg stressor triggers modprobe throttling

Status in Stress-ng:
  In Progress
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Due to the combination of high core counts and perhaps a lack of
  available hash/crypto hardware acceleration drivers, arm64 server
  platforms generate a lot of noisy modprobe throttling messages when
  running the af-alg stressor. This appears to be partially mitigated in
  master by disabling hashes/ciphers once they are found to be not
  present. But, w/ 96 cores/hogs, we presumably still hit the kernel
  with 96 * (nr_hashes + nr_ciphers) before that mitigation takes
  effect, and that is sufficient to cause the kernel to emit throttling
  messages.

  
  $ sudo dmesg -c > /dev/null ; ./stress-ng --af-alg 0 --af-alg-ops=20; 
sudo dmesg -c
  stress-ng: info:  [76141] defaulting to a 86400 second (1 day, 0.00 secs) run 
per stressor
  stress-ng: info:  [76141] dispatching hogs: 96 af-alg
  stress-ng: info:  [76141] successful run completed in 0.40s
  [ 5808.489046] __request_module: 25 callbacks suppressed
  [ 5808.489050] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489503] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489724] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489731] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490092] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-xor-all, throttling...
  [ 5808.490235] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash-all, throttling...
  [ 5808.490308] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490367] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490597] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1813847/+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 1813899] Re: pthread in stress-smoke test failed on GCP X-4.15

2019-01-30 Thread Colin Ian King
Added some extra debug and some more sanity checking. Looks like on a
single CPU the pthread reaping was not unlocking a mutex causing the
issue.

Fixes committed:
https://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=e5ecba459754d4bdb3e858caaaf41a87e485c8ce
"stress-pthread: make error messages a bit more informative"

and
https://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=a50c7466634e194e3169bc63591a86342cb10c67
stress-pthread: add better error recovery and locking prevention checks

** Changed in: stress-ng
   Status: New => Fix Committed

** Changed in: stress-ng
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: stress-ng
   Importance: Undecided => High

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

Title:
  pthread in stress-smoke test failed on GCP X-4.15

Status in Stress-ng:
  Fix Committed
Status in ubuntu-kernel-tests:
  New
Status in linux-gcp package in Ubuntu:
  New

Bug description:
   4.15.0-1027-gcp #28~16.04.1-Ubuntu
   Only spotted on node n1-standard-8

   pthread FAILED
   stress-ng: debug: [19921] 1 processor online, 1 processor configured
   stress-ng: info:  [19921] dispatching hogs: 4 pthread
   stress-ng: debug: [19921] cache allocate: default cache size: 56320K
   stress-ng: debug: [19921] starting stressors
   stress-ng: debug: [19921] 4 stressors spawned
   stress-ng: debug: [19925] stress-ng-pthread: started [19925] (instance 3)
   stress-ng: debug: [19924] stress-ng-pthread: started [19924] (instance 2)
   stress-ng: debug: [19923] stress-ng-pthread: started [19923] (instance 1)
   stress-ng: debug: [19922] stress-ng-pthread: started [19922] (instance 0)
   stress-ng: debug: [19923] stress-ng-pthread: exited [19923] (instance 1)
   stress-ng: debug: [19922] stress-ng-pthread: exited [19922] (instance 0)
   stress-ng: debug: [19921] process [19922] terminated
   stress-ng: debug: [19924] stress-ng-pthread: exited [19924] (instance 2)
   stress-ng: fail:  [19924] stress-ng-pthread: mutex unlock failed, errno=22 
(Invalid argument)
   stress-ng: debug: [19921] process [19923] (stress-ng-pthread) terminated on 
signal: 11 (Segmentation fault)
   stress-ng: debug: [19921] process [19923] terminated
   stress-ng: debug: [19921] process [19924] terminated
   stress-ng: debug: [19921] process [19925] (stress-ng-pthread) terminated on 
signal: 11 (Segmentation fault)
   stress-ng: debug: [19921] process [19925] terminated
   stress-ng: info:  [19921] unsuccessful run completed in 5.05s

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1813899/+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 1813899] Re: pthread in stress-smoke test failed on GCP X-4.15

2019-01-30 Thread Colin Ian King
Do we have any more logs of the run, e.g. kernel messages etc?

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

Title:
  pthread in stress-smoke test failed on GCP X-4.15

Status in Stress-ng:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-gcp package in Ubuntu:
  New

Bug description:
   4.15.0-1027-gcp #28~16.04.1-Ubuntu
   Only spotted on node n1-standard-8

   pthread FAILED
   stress-ng: debug: [19921] 1 processor online, 1 processor configured
   stress-ng: info:  [19921] dispatching hogs: 4 pthread
   stress-ng: debug: [19921] cache allocate: default cache size: 56320K
   stress-ng: debug: [19921] starting stressors
   stress-ng: debug: [19921] 4 stressors spawned
   stress-ng: debug: [19925] stress-ng-pthread: started [19925] (instance 3)
   stress-ng: debug: [19924] stress-ng-pthread: started [19924] (instance 2)
   stress-ng: debug: [19923] stress-ng-pthread: started [19923] (instance 1)
   stress-ng: debug: [19922] stress-ng-pthread: started [19922] (instance 0)
   stress-ng: debug: [19923] stress-ng-pthread: exited [19923] (instance 1)
   stress-ng: debug: [19922] stress-ng-pthread: exited [19922] (instance 0)
   stress-ng: debug: [19921] process [19922] terminated
   stress-ng: debug: [19924] stress-ng-pthread: exited [19924] (instance 2)
   stress-ng: fail:  [19924] stress-ng-pthread: mutex unlock failed, errno=22 
(Invalid argument)
   stress-ng: debug: [19921] process [19923] (stress-ng-pthread) terminated on 
signal: 11 (Segmentation fault)
   stress-ng: debug: [19921] process [19923] terminated
   stress-ng: debug: [19921] process [19924] terminated
   stress-ng: debug: [19921] process [19925] (stress-ng-pthread) terminated on 
signal: 11 (Segmentation fault)
   stress-ng: debug: [19921] process [19925] terminated
   stress-ng: info:  [19921] unsuccessful run completed in 5.05s

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1813899/+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 1813749] Re: zfs-linux 0.6.5.6-0ubuntu26 ADT test failure with linux-snapdragon 4.4.0-1107.112

2019-01-29 Thread Colin Ian King
** Also affects: zfs-linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  zfs-linux 0.6.5.6-0ubuntu26 ADT test failure with linux-snapdragon
  4.4.0-1107.112

Status in zfs-linux package in Ubuntu:
  New
Status in zfs-linux source package in Xenial:
  New

Bug description:
  Testing failed on:
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/z/zfs-linux/20190125_170958_97a22@/log.gz

  The debian test script (debian/tests/kernel-smoke-test) doesn't load
  the zfs module causing the tests to fail.

  However, the tests were not failing before. I suspect that's being
  caused by a change in the order that the packages are installed before
  the tests start. With previous ADT runs, the zfsutils-linux package
  was installed after zfs-dkms, so that caused systemd to start the zfs-
  import-scan service, which loaded the modules. On these later ADT
  failed runs, zfs-dkms is installed last, so the service is not
  reloaded and the modules stay unloaded.

  The solution is to load the zfs module before starting the tests, as
  done by the test script shipped by the packages for Bionic and later
  series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1813749/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-23 Thread Colin Ian King
@Alex, ignore the message in comment #12, I meant to ask you to test it
for Cosmic. That would be really helpful. Thanks!

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  Fix Committed
Status in thermald source package in Cosmic:
  Fix Committed
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-23 Thread Colin Ian King
@Alex, I don't have the H/W to verify this update for xenial. Do you
mind testing it for Xenial too so I can get this released?  Thanks!

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  Fix Committed
Status in thermald source package in Cosmic:
  Fix Committed
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1811259] Re: 4.20 kernel on s390x VM crashes

2019-01-16 Thread Colin Ian King
Fixes sent to kt mailing list for review

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

Title:
  4.20 kernel on s390x VM crashes

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  Booting with  4.20.0-2-generic on a s390x 2 CPU VM we hit a panic:

  [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc 
version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 
2019 (Ubuntu 4.20.0-2.3-generic 4.20.0)
  [0.394838] setup.289988: Linux is running under KVM in 64-bit mode
  [0.394846] setup.b050d0: The maximum memory size is 2048MB
  [0.394866] numa.196305: NUMA mode: plain
  [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs
  [0.394999] Write protected kernel read-only data: 10464k
  [0.395034] Zone ranges:
  [0.395035]   DMA  [mem 0x-0x7fff]
  [0.395037]   Normal   empty
  [0.395038] Movable zone start for each node
  [0.395039] Early memory node ranges
  [0.395041]   node   0: [mem 0x-0x7fff]
  [0.395042] Initmem setup node 0 [mem 
0x-0x7fff]
  [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 
d32000 u102400
  [0.413824] Built 1 zonelists, mobility grouping on.  Total pages: 516096
  [0.413825] Policy zone: DMA
  [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs
  [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K 
rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved)
  [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 
with crng_init=0
  [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1
  [0.450434] ftrace: allocating 27385 entries in 107 pages
  [0.473325] rcu: Hierarchical RCU implementation.
  [0.473327] rcu:   RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3.
  [0.473328]Tasks RCU enabled.
  [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 
jiffies.
  [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3
  [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3
  [0.475402] clocksource: tod: mask: 0x max_cycles: 
0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
  [0.475558] printk: console [ttyS1] enabled
  [0.475623] pid_max: default: 32768 minimum: 301
  [0.475658] LSM: Security Framework initializing
  [0.475660] Yama: becoming mindful.
  [0.475677] AppArmor: AppArmor initialized
  [0.476134] Dentry cache hash table entries: 262144 (order: 9, 2097152 
bytes)
  [0.476352] Inode-cache hash table entries: 131072 (order: 8, 1048576 
bytes)
  [0.476370] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
  [0.476377] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 
bytes)
  [0.476726] rcu: Hierarchical SRCU implementation.
  [0.476927] smp: Bringing up secondary CPUs ...
  [0.477181] smp: Brought up 1 node, 2 CPUs
  [0.477549] devtmpfs: initialized
  [0.477882] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 1911260446275 ns
  [0.477902] futex hash table entries: 1024 (order: 6, 262144 bytes)
  [0.478105] NET: Registered protocol family 16
  [0.478134] audit: initializing netlink subsys (disabled)
  [0.478183] audit: type=2000 audit(1547122707.960:1): state=initialized 
audit_enabled=0 res=1
  [0.478222] Spectre V2 mitigation: execute trampolines
  [0.479205] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages
  [0.479623] SCSI subsystem initialized
  [0.479856] NetLabel: Initializing
  [0.479858] NetLabel:  domain hash size = 128
  [0.479859] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
  [0.479871] NetLabel:  unlabeled traffic allowed by default
  [0.507362] VFS: Disk quotas dquot_6.6.0
  [0.507378] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
  [0.507486] AppArmor: AppArmor Filesystem Enabled
  [0.507847] NET: Registered protocol family 2
  [0.507976] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 
16384 bytes)
  [0.507994] TCP established hash table entries: 16384 (order: 5, 131072 
bytes)
  [0.508126] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
  [0.508235] TCP: Hash tables configured (established 16384 bind 16384)
  [0.508269] UDP hash table entries: 1024 (order: 3, 32768 bytes)
  [0.508287] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
  [0.508336] NET: Registered protocol family 1
  [0.508343] NET: Registered protocol family 44
  [0.508374] Unpacking initramfs...
  [0.742412] 

[Kernel-packages] [Bug 1811259] Re: 4.20 kernel on s390x VM crashes

2019-01-16 Thread Colin Ian King
The following fixes in vhost.git fix the issue:

https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/commit/?h
=linux-next=bf4dc0b2beebfd9338df7c0bcf473b356f67cf66

https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/commit/?h
=linux-next=a229989d975eb926076307c1f2f5e4c6111768e7

https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/commit/?h
=linux-next=ddbeac07a39a81d82331a312d0578fab94fccbf1

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  4.20 kernel on s390x VM crashes

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  Booting with  4.20.0-2-generic on a s390x 2 CPU VM we hit a panic:

  [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc 
version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 
2019 (Ubuntu 4.20.0-2.3-generic 4.20.0)
  [0.394838] setup.289988: Linux is running under KVM in 64-bit mode
  [0.394846] setup.b050d0: The maximum memory size is 2048MB
  [0.394866] numa.196305: NUMA mode: plain
  [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs
  [0.394999] Write protected kernel read-only data: 10464k
  [0.395034] Zone ranges:
  [0.395035]   DMA  [mem 0x-0x7fff]
  [0.395037]   Normal   empty
  [0.395038] Movable zone start for each node
  [0.395039] Early memory node ranges
  [0.395041]   node   0: [mem 0x-0x7fff]
  [0.395042] Initmem setup node 0 [mem 
0x-0x7fff]
  [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 
d32000 u102400
  [0.413824] Built 1 zonelists, mobility grouping on.  Total pages: 516096
  [0.413825] Policy zone: DMA
  [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs
  [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K 
rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved)
  [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 
with crng_init=0
  [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1
  [0.450434] ftrace: allocating 27385 entries in 107 pages
  [0.473325] rcu: Hierarchical RCU implementation.
  [0.473327] rcu:   RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3.
  [0.473328]Tasks RCU enabled.
  [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 
jiffies.
  [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3
  [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3
  [0.475402] clocksource: tod: mask: 0x max_cycles: 
0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
  [0.475558] printk: console [ttyS1] enabled
  [0.475623] pid_max: default: 32768 minimum: 301
  [0.475658] LSM: Security Framework initializing
  [0.475660] Yama: becoming mindful.
  [0.475677] AppArmor: AppArmor initialized
  [0.476134] Dentry cache hash table entries: 262144 (order: 9, 2097152 
bytes)
  [0.476352] Inode-cache hash table entries: 131072 (order: 8, 1048576 
bytes)
  [0.476370] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
  [0.476377] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 
bytes)
  [0.476726] rcu: Hierarchical SRCU implementation.
  [0.476927] smp: Bringing up secondary CPUs ...
  [0.477181] smp: Brought up 1 node, 2 CPUs
  [0.477549] devtmpfs: initialized
  [0.477882] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 1911260446275 ns
  [0.477902] futex hash table entries: 1024 (order: 6, 262144 bytes)
  [0.478105] NET: Registered protocol family 16
  [0.478134] audit: initializing netlink subsys (disabled)
  [0.478183] audit: type=2000 audit(1547122707.960:1): state=initialized 
audit_enabled=0 res=1
  [0.478222] Spectre V2 mitigation: execute trampolines
  [0.479205] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages
  [0.479623] SCSI subsystem initialized
  [0.479856] NetLabel: Initializing
  [0.479858] NetLabel:  domain hash size = 128
  [0.479859] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
  [0.479871] NetLabel:  unlabeled traffic allowed by default
  [0.507362] VFS: Disk quotas dquot_6.6.0
  [0.507378] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
  [0.507486] AppArmor: AppArmor Filesystem Enabled
  [0.507847] NET: Registered protocol family 2
  [0.507976] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 
16384 bytes)
  [0.507994] TCP established hash table entries: 16384 (or

[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-16 Thread Colin Ian King
@Kai-Heng,

do you mind giving these packages a test now?

Thanks.

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  Fix Committed
Status in thermald source package in Cosmic:
  Fix Committed
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1811259] Re: 4.20 kernel on s390x VM crashes

2019-01-15 Thread Colin Ian King
** Bug watch added: Linux Kernel Bug Tracker #202283
   https://bugzilla.kernel.org/show_bug.cgi?id=202283

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=202283
   Importance: Unknown
   Status: Unknown

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

Title:
  4.20 kernel on s390x VM crashes

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  Booting with  4.20.0-2-generic on a s390x 2 CPU VM we hit a panic:

  [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc 
version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 
2019 (Ubuntu 4.20.0-2.3-generic 4.20.0)
  [0.394838] setup.289988: Linux is running under KVM in 64-bit mode
  [0.394846] setup.b050d0: The maximum memory size is 2048MB
  [0.394866] numa.196305: NUMA mode: plain
  [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs
  [0.394999] Write protected kernel read-only data: 10464k
  [0.395034] Zone ranges:
  [0.395035]   DMA  [mem 0x-0x7fff]
  [0.395037]   Normal   empty
  [0.395038] Movable zone start for each node
  [0.395039] Early memory node ranges
  [0.395041]   node   0: [mem 0x-0x7fff]
  [0.395042] Initmem setup node 0 [mem 
0x-0x7fff]
  [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 
d32000 u102400
  [0.413824] Built 1 zonelists, mobility grouping on.  Total pages: 516096
  [0.413825] Policy zone: DMA
  [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs
  [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K 
rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved)
  [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 
with crng_init=0
  [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1
  [0.450434] ftrace: allocating 27385 entries in 107 pages
  [0.473325] rcu: Hierarchical RCU implementation.
  [0.473327] rcu:   RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3.
  [0.473328]Tasks RCU enabled.
  [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 
jiffies.
  [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3
  [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3
  [0.475402] clocksource: tod: mask: 0x max_cycles: 
0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
  [0.475558] printk: console [ttyS1] enabled
  [0.475623] pid_max: default: 32768 minimum: 301
  [0.475658] LSM: Security Framework initializing
  [0.475660] Yama: becoming mindful.
  [0.475677] AppArmor: AppArmor initialized
  [0.476134] Dentry cache hash table entries: 262144 (order: 9, 2097152 
bytes)
  [0.476352] Inode-cache hash table entries: 131072 (order: 8, 1048576 
bytes)
  [0.476370] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
  [0.476377] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 
bytes)
  [0.476726] rcu: Hierarchical SRCU implementation.
  [0.476927] smp: Bringing up secondary CPUs ...
  [0.477181] smp: Brought up 1 node, 2 CPUs
  [0.477549] devtmpfs: initialized
  [0.477882] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 1911260446275 ns
  [0.477902] futex hash table entries: 1024 (order: 6, 262144 bytes)
  [0.478105] NET: Registered protocol family 16
  [0.478134] audit: initializing netlink subsys (disabled)
  [0.478183] audit: type=2000 audit(1547122707.960:1): state=initialized 
audit_enabled=0 res=1
  [0.478222] Spectre V2 mitigation: execute trampolines
  [0.479205] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages
  [0.479623] SCSI subsystem initialized
  [0.479856] NetLabel: Initializing
  [0.479858] NetLabel:  domain hash size = 128
  [0.479859] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
  [0.479871] NetLabel:  unlabeled traffic allowed by default
  [0.507362] VFS: Disk quotas dquot_6.6.0
  [0.507378] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
  [0.507486] AppArmor: AppArmor Filesystem Enabled
  [0.507847] NET: Registered protocol family 2
  [0.507976] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 
16384 bytes)
  [0.507994] TCP established hash table entries: 16384 (order: 5, 131072 
bytes)
  [0.508126] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
  [0.508235] TCP: Hash tables configured (established 16384 bind 16384)
  [0.508269] UDP hash table entries: 1024 (order: 3, 32768 bytes)
  [0.508287] UDP-Lite hash table 

[Kernel-packages] [Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL

2019-01-15 Thread Colin Ian King
** Changed in: thermald (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu)
   Importance: Undecided => High

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

Title:
  Thermald does not set max CPU after reseting the voltage using RAPL

Status in thermald package in Ubuntu:
  New

Bug description:
  Hi,

  I was using Ubuntu 18.10 thermald package, but I noted that, after few
  seconds at max CPU usage (max temp), thermald send the signal to RALP
  to reduce the voltage of the CPU. It set the freq to minimum (800MHz
  in my case). But when the CPU is idle and temp is lowered (35-40ºC) it
  did not send the signal to resume normal operation of the CPU.

  I compiled the latest version of thermald from git
  (https://github.com/intel/thermal_daemon) and now everything works
  fine.

  I started to thought that the problem was the hardware or BIOS
  problem, as I disabled the CPU scaling on the BIOS, but intel_pstate
  continued doing freq scaling (I think for Turbo mode).

  But the real problem was Thermald. The latest version from git works
  really fine and it automatically disables and enable the Intel Turbo
  state and balance the freqs and fan control fine.

  My hardware is a Lenovo Thinkpad P52 with i7-8850H.

  I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7
  processor but with Ubuntu default config (except processor
  family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low-
  Latency Desktop)" and Timer frequency="1000HZ". (Only changed those
  settings from make oldconfig and make deb-pkg).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: thermald (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 14 23:45:01 2019
  InstallationDate: Installed on 2018-12-11 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: thermald
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+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 1811259] Re: 4.20 kernel on s390x VM crashes

2019-01-15 Thread Colin Ian King
Finally bisected:

git bisect good
86a559787e6f5cf662c081363f64a20cad654195 is the first bad commit
commit 86a559787e6f5cf662c081363f64a20cad654195
Author: Wei Wang 
Date:   Mon Aug 27 09:32:17 2018 +0800

virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT

Negotiation of the VIRTIO_BALLOON_F_FREE_PAGE_HINT feature indicates the
support of reporting hints of guest free pages to host via virtio-balloon.
Currenlty, only free page blocks of MAX_ORDER - 1 are reported. They are
obtained one by one from the mm free list via the regular allocation
function.

Host requests the guest to report free page hints by sending a new cmd id
to the guest via the free_page_report_cmd_id configuration register. When
the guest starts to report, it first sends a start cmd to host via the
free page vq, which acks to host the cmd id received. When the guest
finishes reporting free pages, a stop cmd is sent to host via the vq.
Host may also send a stop cmd id to the guest to stop the reporting.

VIRTIO_BALLOON_CMD_ID_STOP: Host sends this cmd to stop the guest
reporting.
VIRTIO_BALLOON_CMD_ID_DONE: Host sends this cmd to tell the guest that
the reported pages are ready to be freed.

Why does the guest free the reported pages when host tells it is ready to
free?
This is because freeing pages appears to be expensive for live migration.
free_pages() dirties memory very quickly and makes the live migraion not
converge in some cases. So it is good to delay the free_page operation
when the migration is done, and host sends a command to guest about that.

Why do we need the new VIRTIO_BALLOON_CMD_ID_DONE, instead of reusing
VIRTIO_BALLOON_CMD_ID_STOP?
This is because live migration is usually done in several rounds. At the
end of each round, host needs to send a VIRTIO_BALLOON_CMD_ID_STOP cmd to
the guest to stop (or say pause) the reporting. The guest resumes the
reporting when it receives a new command id at the beginning of the next
round. So we need a new cmd id to distinguish between "stop reporting" and
"ready to free the reported pages".

TODO:
- Add a batch page allocation API to amortize the allocation overhead.

Signed-off-by: Wei Wang 
Signed-off-by: Liang Li 
Cc: Michael S. Tsirkin 
Cc: Michal Hocko 
Cc: Andrew Morton 
Cc: Linus Torvalds 
Signed-off-by: Michael S. Tsirkin 

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

Title:
  4.20 kernel on s390x VM crashes

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  Booting with  4.20.0-2-generic on a s390x 2 CPU VM we hit a panic:

  [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc 
version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 
2019 (Ubuntu 4.20.0-2.3-generic 4.20.0)
  [0.394838] setup.289988: Linux is running under KVM in 64-bit mode
  [0.394846] setup.b050d0: The maximum memory size is 2048MB
  [0.394866] numa.196305: NUMA mode: plain
  [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs
  [0.394999] Write protected kernel read-only data: 10464k
  [0.395034] Zone ranges:
  [0.395035]   DMA  [mem 0x-0x7fff]
  [0.395037]   Normal   empty
  [0.395038] Movable zone start for each node
  [0.395039] Early memory node ranges
  [0.395041]   node   0: [mem 0x-0x7fff]
  [0.395042] Initmem setup node 0 [mem 
0x-0x7fff]
  [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 
d32000 u102400
  [0.413824] Built 1 zonelists, mobility grouping on.  Total pages: 516096
  [0.413825] Policy zone: DMA
  [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs
  [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K 
rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved)
  [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 
with crng_init=0
  [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1
  [0.450434] ftrace: allocating 27385 entries in 107 pages
  [0.473325] rcu: Hierarchical RCU implementation.
  [0.473327] rcu:   RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3.
  [0.473328]Tasks RCU enabled.
  [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 
jiffies.
  [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3
  [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3
  [0.475402] clocksource: tod: mask: 0x max_cycles: 
0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
  [0.475558] printk: console [ttyS1] 

[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-15 Thread Colin Ian King
** Changed in: thermald (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: thermald (Ubuntu Xenial)
 Assignee: Colin Ian King (colin-king) => (unassigned)

** Changed in: thermald (Ubuntu Xenial)
   Importance: High => Undecided

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  In Progress
Status in thermald source package in Cosmic:
  In Progress
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-15 Thread Colin Ian King
The xenial version of thermald does not support the INT340X, so I'm
reluctant to back port the fix as I need to add the INT340X support in
which is quite a few changes.  As this is adding extra functionality to
thermald I believe this falls outside the remit of a SRU.

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

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  New
Status in thermald source package in Bionic:
  In Progress
Status in thermald source package in Cosmic:
  In Progress
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-14 Thread Colin Ian King
** Changed in: thermald (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu Bionic)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu Cosmic)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: thermald (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: thermald (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: thermald (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

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

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-14 Thread Colin Ian King
** Description changed:

+ == SRU Justification, Cosmic, Bionic, Xenial ==
+ 
  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.
  
  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.
+ 
+ == Fix ==
+  
+ Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9
+ 
+ == Testing ==
+ 
+ Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and try
+ and reach the trip point. Without the fix thermal overrun occurs and
+ this trips CPU shutdown. With the fix, thermald will start to throttle
+ the system and get it out of the thermal overrun zone.
+ 
+ == Regression Potential ==
+ 
+ This modifies the behavior for just INT340X devices with ACPI _CRT
+ objects, specifically, now to honor this setting.  This is a small
+ subset of devices with these objects and the change will in face make
+ thermald catch systems before they hit thermal overrun, so the risk of
+ regression is small. This fix also has been reviewed by the thermal
+ experts at Intel, so it seems like a very reasonable workaround for
+ these specific use cases.

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

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

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-14 Thread Colin Ian King
** Also affects: thermald (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: thermald (Ubuntu Disco)
   Importance: High
 Assignee: Colin Ian King (colin-king)
   Status: In Progress

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

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

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

Bug description:
  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-14 Thread Colin Ian King
OK, will sort that out this week.

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1811259] Re: 4.20 kernel on s390x VM crashes

2019-01-14 Thread Colin Ian King
5.0-rc2 also fails to boot:

[0.761280] CPU: 0 PID: 7 Comm: kworker/u6:0 Not tainted 5.0.0-rc2 #1
[0.761282] Hardware name: IBM 2964 N63 400 (KVM/Linux)
[0.761288] Workqueue: events_unbound call_usermodehelper_exec_work
[0.761291] Krnl PSW : 0404e0018000 0016a360 
(release_task_stack+0x78/0x1b0)
[0.761297]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
[0.761301] Krnl GPRS: f000 01ee6320 0700 

[0.761303]fffc 7f26 7ff92300 
7f9e6790
[0.761306]0080 01c15d00 01cd9000 
0003
[0.761309]0008 008f1228 0016a3ae 
03e00034fb40
[0.761320] Krnl Code: 0016a34e: e320f0a4lg  
%r2,160(%r15)
[0.761320]0016a354: c004brcl0,16a354
[0.761320]   #0016a35a: e35003b4lg  %r5,944
[0.761320]   >0016a360: e3103514lg  
%r1,1296(%r3)
[0.761320]0016a366: a71b0118aghi%r1,280
[0.761320]0016a36a: b9040041lgr %r4,%r1
[0.761320]0016a36e: e3454004lg  
%r4,0(%r5,%r4)
[0.761320]0016a374: a74bfffcaghi%r4,-4
[0.761343] Call Trace:
[0.761346] ([<0016a3ae>] release_task_stack+0xc6/0x1b0)
[0.761352]  [<0019c914>] finish_task_switch+0x274/0x308 
[0.761356]  [<008deb4e>] __schedule+0x46e/0x8e8 
[0.761359]  [<008df00a>] schedule+0x42/0xa0 
[0.761363]  [<00173036>] do_wait+0x1f6/0x288 
[0.761366]  [<00174382>] kernel_wait4+0x9a/0x130 
[0.761370]  [<001887ac>] call_usermodehelper_exec_work+0x94/0xd8 
[0.761373]  [<0018c5d8>] process_one_work+0x278/0x4b8 
[0.761376]  [<0018c868>] worker_thread+0x50/0x4e0 
[0.761380]  [<001936ac>] kthread+0x144/0x160 
[0.761383]  [<008e3cc2>] kernel_thread_starter+0xa/0x10 
[0.761386]  [<008e3cb8>] kernel_thread_starter+0x0/0x10 
[0.761387] Last Breaking-Event-Address:
[0.761435]  [<0016a3ae>] release_task_stack+0xc6/0x1b0

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

Title:
  4.20 kernel on s390x VM crashes

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  Booting with  4.20.0-2-generic on a s390x 2 CPU VM we hit a panic:

  [0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc 
version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 
2019 (Ubuntu 4.20.0-2.3-generic 4.20.0)
  [0.394838] setup.289988: Linux is running under KVM in 64-bit mode
  [0.394846] setup.b050d0: The maximum memory size is 2048MB
  [0.394866] numa.196305: NUMA mode: plain
  [0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs
  [0.394999] Write protected kernel read-only data: 10464k
  [0.395034] Zone ranges:
  [0.395035]   DMA  [mem 0x-0x7fff]
  [0.395037]   Normal   empty
  [0.395038] Movable zone start for each node
  [0.395039] Early memory node ranges
  [0.395041]   node   0: [mem 0x-0x7fff]
  [0.395042] Initmem setup node 0 [mem 
0x-0x7fff]
  [0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 
d32000 u102400
  [0.413824] Built 1 zonelists, mobility grouping on.  Total pages: 516096
  [0.413825] Policy zone: DMA
  [0.413827] Kernel command line: root=LABEL=cloudimg-rootfs
  [0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K 
rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved)
  [0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 
with crng_init=0
  [0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1
  [0.450434] ftrace: allocating 27385 entries in 107 pages
  [0.473325] rcu: Hierarchical RCU implementation.
  [0.473327] rcu:   RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3.
  [0.473328]Tasks RCU enabled.
  [0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 
jiffies.
  [0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3
  [0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3
  [0.475402] clocksource: tod: mask: 0x max_cycles: 
0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
  [0.475558] printk: console [ttyS1] enabled
  [0.475623] pid_max: default: 32768 minimum: 301
  [0.475658] LSM: Security Framework 

[Kernel-packages] [Bug 1811259] Re: 4.20 kernel on s390x VM crashes

2019-01-10 Thread Colin Ian King
5.0-rc1, no dice:

[0.398768] Linux version 5.0.0-rc1+ (ubuntu@ckingvm1) (gcc version 8.2.0 
(Ubuntu 8.2.0-7ubuntu1)) #1 SMP Thu Jan 10 17:45:01 UTC 2019
[0.398770] setup: Linux is running under KVM in 64-bit mode
[0.398778] setup: The maximum memory size is 2048MB
[0.398799] numa: NUMA mode: plain
[0.398823] cpu: 2 configured CPUs, 0 standby CPUs
[0.398925] Write protected kernel read-only data: 10420k
[0.398958] Zone ranges:
[0.398959]   DMA  [mem 0x-0x7fff]
[0.398961]   Normal   empty
[0.398962] Movable zone start for each node
[0.398963] Early memory node ranges
[0.398964]   node   0: [mem 0x-0x7fff]
[0.398965] Initmem setup node 0 [mem 0x-0x7fff]
[0.416530] percpu: Embedded 25 pages/cpu @(ptrval) s61696 r8192 
d32512 u102400
[0.416551] Built 1 zonelists, mobility grouping on.  Total pages: 516096
[0.416552] Policy zone: DMA
[0.416553] Kernel command line: root=LABEL=cloudimg-rootfs
[0.452308] Memory: 2034240K/2097152K available (8092K kernel code, 1084K 
rwdata, 2324K rodata, 992K init, 776K bss, 62912K reserved, 0K cma-reserved)
[0.452316] random: get_random_u64 called from 
__kmem_cache_create+0x4c/0x5f0 with crng_init=0
[0.452464] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1
[0.452466] ftrace: allocating 27127 entries in 106 pages
[0.475936] rcu: Hierarchical RCU implementation.
[0.475938] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3.
[0.475939]  Tasks RCU enabled.
[0.475940] rcu: RCU calculated value of scheduler-enlistment delay is 10 
jiffies.
[0.475941] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3
[0.478033] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3
[0.478069] clocksource: tod: mask: 0x max_cycles: 
0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
[0.478241] printk: console [ttyS1] enabled
[0.478311] pid_max: default: 32768 minimum: 301
[0.478345] LSM: Security Framework initializing
[0.478347] Yama: becoming mindful.
[0.478365] AppArmor: AppArmor initialized
[0.478805] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[0.479032] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[0.479050] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
[0.479057] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
[0.479413] rcu: Hierarchical SRCU implementation.
[0.479629] smp: Bringing up secondary CPUs ...
[0.479884] smp: Brought up 1 node, 2 CPUs
[0.480226] devtmpfs: initialized
[0.480464] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 1911260446275 ns
[0.480486] futex hash table entries: 1024 (order: 6, 262144 bytes)
[0.480692] NET: Registered protocol family 16
[0.480721] audit: initializing netlink subsys (disabled)
[0.480758] audit: type=2000 audit(1547126955.184:1): state=initialized 
audit_enabled=0 res=1
[0.480800] Spectre V2 mitigation: execute trampolines
[0.481735] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages
[0.482061] SCSI subsystem initialized
[0.482269] NetLabel: Initializing
[0.482270] NetLabel:  domain hash size = 128
[0.482271] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[0.482283] NetLabel:  unlabeled traffic allowed by default
[0.511560] VFS: Disk quotas dquot_6.6.0
[0.511580] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[0.511690] AppArmor: AppArmor Filesystem Enabled
[0.511972] NET: Registered protocol family 2
[0.512106] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 
16384 bytes)
[0.512127] TCP established hash table entries: 16384 (order: 5, 131072 
bytes)
[0.512199] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[0.512381] TCP: Hash tables configured (established 16384 bind 16384)
[0.512414] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[0.512433] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[0.512477] NET: Registered protocol family 1
[0.512483] NET: Registered protocol family 44
[0.512518] Unpacking initramfs...
[0.747003] Freeing initrd memory: 15780K
[0.747282] kvm-s390: SIE not available
[0.747301] hypfs: The hardware system does not support hypfs
[0.747310] hypfs: Initialization of hypfs failed with rc=-61
[0.747678] Initialise system trusted keyrings
[0.747689] Key type blacklist registered
[0.747715] workingset: timestamp_bits=42 max_order=19 bucket_order=0
[0.749162] zbud: loaded
[0.749614] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[0.749785] fuse init (API version 7.28)
[0.773883] Key type asymmetric registered
[0.773886] Asymmetric key parser 'x509' registered
[0.773900] Block layer SCSI generic (bsg) driver 

[Kernel-packages] [Bug 1811259] [NEW] 4.20 kernel on s390x VM crashes

2019-01-10 Thread Colin Ian King
Public bug reported:

Booting with  4.20.0-2-generic on a s390x 2 CPU VM we hit a panic:

[0.394835] Linux version 4.20.0-2-generic (buildd@bos02-s390x-015) (gcc 
version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)) #3-Ubuntu SMP Thu Jan 3 18:43:01 UTC 
2019 (Ubuntu 4.20.0-2.3-generic 4.20.0)
[0.394838] setup.289988: Linux is running under KVM in 64-bit mode
[0.394846] setup.b050d0: The maximum memory size is 2048MB
[0.394866] numa.196305: NUMA mode: plain
[0.394893] cpu.33a262: 2 configured CPUs, 0 standby CPUs
[0.394999] Write protected kernel read-only data: 10464k
[0.395034] Zone ranges:
[0.395035]   DMA  [mem 0x-0x7fff]
[0.395037]   Normal   empty
[0.395038] Movable zone start for each node
[0.395039] Early memory node ranges
[0.395041]   node   0: [mem 0x-0x7fff]
[0.395042] Initmem setup node 0 [mem 0x-0x7fff]
[0.413802] percpu: Embedded 25 pages/cpu @(ptrval) s62208 r8192 
d32000 u102400
[0.413824] Built 1 zonelists, mobility grouping on.  Total pages: 516096
[0.413825] Policy zone: DMA
[0.413827] Kernel command line: root=LABEL=cloudimg-rootfs
[0.450276] Memory: 2034164K/2097152K available (8116K kernel code, 1079K 
rwdata, 2344K rodata, 992K init, 772K bss, 62988K reserved, 0K cma-reserved)
[0.450283] random: get_random_u64 called from kmem_cache_open+0x4c/0x4f0 
with crng_init=0
[0.450432] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=3, Nodes=1
[0.450434] ftrace: allocating 27385 entries in 107 pages
[0.473325] rcu: Hierarchical RCU implementation.
[0.473327] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=3.
[0.473328]  Tasks RCU enabled.
[0.473329] rcu: RCU calculated value of scheduler-enlistment delay is 10 
jiffies.
[0.473330] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=3
[0.475371] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3
[0.475402] clocksource: tod: mask: 0x max_cycles: 
0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
[0.475558] printk: console [ttyS1] enabled
[0.475623] pid_max: default: 32768 minimum: 301
[0.475658] LSM: Security Framework initializing
[0.475660] Yama: becoming mindful.
[0.475677] AppArmor: AppArmor initialized
[0.476134] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[0.476352] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[0.476370] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
[0.476377] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
[0.476726] rcu: Hierarchical SRCU implementation.
[0.476927] smp: Bringing up secondary CPUs ...
[0.477181] smp: Brought up 1 node, 2 CPUs
[0.477549] devtmpfs: initialized
[0.477882] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 1911260446275 ns
[0.477902] futex hash table entries: 1024 (order: 6, 262144 bytes)
[0.478105] NET: Registered protocol family 16
[0.478134] audit: initializing netlink subsys (disabled)
[0.478183] audit: type=2000 audit(1547122707.960:1): state=initialized 
audit_enabled=0 res=1
[0.478222] Spectre V2 mitigation: execute trampolines
[0.479205] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages
[0.479623] SCSI subsystem initialized
[0.479856] NetLabel: Initializing
[0.479858] NetLabel:  domain hash size = 128
[0.479859] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[0.479871] NetLabel:  unlabeled traffic allowed by default
[0.507362] VFS: Disk quotas dquot_6.6.0
[0.507378] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[0.507486] AppArmor: AppArmor Filesystem Enabled
[0.507847] NET: Registered protocol family 2
[0.507976] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 
16384 bytes)
[0.507994] TCP established hash table entries: 16384 (order: 5, 131072 
bytes)
[0.508126] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[0.508235] TCP: Hash tables configured (established 16384 bind 16384)
[0.508269] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[0.508287] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[0.508336] NET: Registered protocol family 1
[0.508343] NET: Registered protocol family 44
[0.508374] Unpacking initramfs...
[0.742412] Freeing initrd memory: 15824K
[0.742685] kvm-s390: SIE not available
[0.742706] hypfs.7f5705: The hardware system does not support hypfs
[0.742714] hypfs.7a79f0: Initialization of hypfs failed with rc=-61
[0.743110] Initialise system trusted keyrings
[0.743119] Key type blacklist registered
[0.743140] workingset: timestamp_bits=42 max_order=19 bucket_order=0
[0.744539] zbud: loaded
[0.745012] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[0.745211] fuse init (API version 

[Kernel-packages] [Bug 1667838] Re: zpool export mpu1pool cannot export 'mpu1pool': pool is busy

2018-12-26 Thread Colin Ian King
OK, thanks for the update.

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

Title:
  zpool export mpu1pool  cannot export 'mpu1pool': pool is busy

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

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  Linux 4.4.0-64-generic

  $ apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu15

  # modinfo zfs |head
  filename:   /lib/modules/4.4.0-64-generic/kernel/zfs/zfs/zfs.ko
  version:0.6.5.6-0ubuntu15

  
  I was not able to unmount a ZFS pool:

  # zpool export mpu1pool 
  cannot export 'mpu1pool': pool is busy

  The filesystems were unmounted and there was nothing that would be blocking 
them FS.
  Neither sync, echo 3 > /proc/sys/vm/drop_caches helped.

  The only way worked to export a ZFS pool was to turn off the SWAP:

  # lsof -Pn |grep -i mpu1
  lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
  # free -mh
totalusedfree  shared  buff/cache   
available
  Mem:   7.7G5.1G502M837M2.1G
1.0G
  Swap:  8.0G428M7.6G

  # swapoff -a 
  # free -mh
totalusedfree  shared  buff/cache   
available
  Mem:   7.7G1.5G4.8G366M1.4G
5.2G
  Swap:0B  0B  0B

  # zpool export mpu1pool 
  # echo $?
  0
  # swapon -a

  
  It is not obvious that the SWAP has to be freed before one can export ZFS 
pool.
  Would it be possible to improve this situation?

  
  Kind regards,
  Andrey Arapov

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+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 1807869] Re: ubuntu_nbd_smoke_test failed with Xenial

2018-12-11 Thread Colin Ian King
@Sam, can you give this fix a 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/1807869

Title:
  ubuntu_nbd_smoke_test failed with Xenial

Status in ubuntu-kernel-tests:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Spotted in this cycle with node:
   * daedalus (amd64-lowlatency) - https://pastebin.ubuntu.com/p/JxYNh9JPJd/
   * daedalus (amd64-generic) - https://pastebin.ubuntu.com/p/4W8gDSDVqm/
   * kernel01 (s390x.zVM) - https://pastebin.ubuntu.com/p/kFW7KQbbkf/
   
  Error log from kernel01:
  creating backing nbd image /tmp/nbd_image.img
   
  

  Image path:/tmp/nbd_image.img
  Mount point:   /mnt/nbd-test-22282
  Date:  Mon Dec 10 05:22:47 EST 2018
  Host:  kernel01
  Kernel:4.4.0-141-generic #167-Ubuntu SMP Wed Dec 5 10:32:22 UTC 2018
  Machine:   kernel01 s390x s390x
  CPUs online:   8
  CPUs total:8
  Page size: 4096
  Pages avail:   641567
  Pages total:   977383
  Free space:
  Filesystem   Size  Used Avail Use% 
Mounted on
  udev 1.9G 0  1.9G   0% 
/dev
  tmpfs382M   39M  344M  11% 
/run
  /dev/dasda1  6.7G  6.2G  187M  98% /
  tmpfs1.9G  4.0K  1.9G   1% 
/dev/shm
  tmpfs5.0M 0  5.0M   0% 
/run/lock
  tmpfs1.9G 0  1.9G   0% 
/sys/fs/cgroup
  /dev/mapper/datavg-home   21G  3.1G   17G  17% 
/home
  testpool.3622624G  128K   24G   1% 
/testpool.36226
  testpool.36226/testfs.36226   24G  128K   24G   1% 
/var/tmp/testdir36226
  testpool.36226/testfs.36226/clone 24G  128K   24G   1% 
/var/tmp/testdir36226/clone
  testpool.36226/testfs.36226/renameme  24G  128K   24G   1% 
/var/tmp/testdir36226/renameme
  testpool.36226/testfs.36226/shared24G  128K   24G   1% 
/var/tmp/testdir36226/shared
  testpool.36226/testfs.36226/testfs2.36226 24G  128K   24G   1% 
/var/tmp/testdir36226/testfs2.36226
  testpool.36226/testfs.36226/testfs2.36226.unmounted   24G  128K   24G   1% 
/var/tmp/testdir36226/testfs2.36226.unmounted
  testpool.36226/testfs.36226/unshared  24G  128K   24G   1% 
/var/tmp/testdir36226/unshared
  tmpfs382M 0  382M   0% 
/run/user/1000
  tmpfs100K 0  100K   0% 
/var/lib/lxd/shmounts
  tmpfs100K 0  100K   0% 
/var/lib/lxd/devlxd
  

   
  NBD device /dev/nbd0 created
  found nbd export
  NBD exports found:
  test
  starting clien with NBD device /dev/nbd0
  Negotiation: ..size = 128MB
  creating ext4 on /dev/nbd0
  mkfs on /dev/nbd0 failed
  unmounting /mnt/nbd-test-22282
  stopping client
  disconnect, sock, done
  killing server
  stderr:
  bs=1024, sz=134217728 bytes
  timeout=30
  umount: /mnt/nbd-test-22282: mountpoint not found

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-141-generic 4.4.0-141.167
  ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-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.
  Date: Tue Dec 11 04:08:37 2018
  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=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-141-generic N/A
   linux-backports-modules-4.4.0-141-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1807869] Re: ubuntu_nbd_smoke_test failed with Xenial

2018-12-11 Thread Colin Ian King
Fix committed: http://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=42e9d7328c470d0e6599289db16085e4b9261271

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

Title:
  ubuntu_nbd_smoke_test failed with Xenial

Status in ubuntu-kernel-tests:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Spotted in this cycle with node:
   * daedalus (amd64-lowlatency) - https://pastebin.ubuntu.com/p/JxYNh9JPJd/
   * daedalus (amd64-generic) - https://pastebin.ubuntu.com/p/4W8gDSDVqm/
   * kernel01 (s390x.zVM) - https://pastebin.ubuntu.com/p/kFW7KQbbkf/
   
  Error log from kernel01:
  creating backing nbd image /tmp/nbd_image.img
   
  

  Image path:/tmp/nbd_image.img
  Mount point:   /mnt/nbd-test-22282
  Date:  Mon Dec 10 05:22:47 EST 2018
  Host:  kernel01
  Kernel:4.4.0-141-generic #167-Ubuntu SMP Wed Dec 5 10:32:22 UTC 2018
  Machine:   kernel01 s390x s390x
  CPUs online:   8
  CPUs total:8
  Page size: 4096
  Pages avail:   641567
  Pages total:   977383
  Free space:
  Filesystem   Size  Used Avail Use% 
Mounted on
  udev 1.9G 0  1.9G   0% 
/dev
  tmpfs382M   39M  344M  11% 
/run
  /dev/dasda1  6.7G  6.2G  187M  98% /
  tmpfs1.9G  4.0K  1.9G   1% 
/dev/shm
  tmpfs5.0M 0  5.0M   0% 
/run/lock
  tmpfs1.9G 0  1.9G   0% 
/sys/fs/cgroup
  /dev/mapper/datavg-home   21G  3.1G   17G  17% 
/home
  testpool.3622624G  128K   24G   1% 
/testpool.36226
  testpool.36226/testfs.36226   24G  128K   24G   1% 
/var/tmp/testdir36226
  testpool.36226/testfs.36226/clone 24G  128K   24G   1% 
/var/tmp/testdir36226/clone
  testpool.36226/testfs.36226/renameme  24G  128K   24G   1% 
/var/tmp/testdir36226/renameme
  testpool.36226/testfs.36226/shared24G  128K   24G   1% 
/var/tmp/testdir36226/shared
  testpool.36226/testfs.36226/testfs2.36226 24G  128K   24G   1% 
/var/tmp/testdir36226/testfs2.36226
  testpool.36226/testfs.36226/testfs2.36226.unmounted   24G  128K   24G   1% 
/var/tmp/testdir36226/testfs2.36226.unmounted
  testpool.36226/testfs.36226/unshared  24G  128K   24G   1% 
/var/tmp/testdir36226/unshared
  tmpfs382M 0  382M   0% 
/run/user/1000
  tmpfs100K 0  100K   0% 
/var/lib/lxd/shmounts
  tmpfs100K 0  100K   0% 
/var/lib/lxd/devlxd
  

   
  NBD device /dev/nbd0 created
  found nbd export
  NBD exports found:
  test
  starting clien with NBD device /dev/nbd0
  Negotiation: ..size = 128MB
  creating ext4 on /dev/nbd0
  mkfs on /dev/nbd0 failed
  unmounting /mnt/nbd-test-22282
  stopping client
  disconnect, sock, done
  killing server
  stderr:
  bs=1024, sz=134217728 bytes
  timeout=30
  umount: /mnt/nbd-test-22282: mountpoint not found

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-141-generic 4.4.0-141.167
  ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-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.
  Date: Tue Dec 11 04:08:37 2018
  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=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-141-generic N/A
   linux-backports-modules-4.4.0-141-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: 

[Kernel-packages] [Bug 1807341] Re: ubuntu_squashfs_smoke_test failed with Disco

2018-12-11 Thread Colin Ian King
Fix committed: http://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=30d50ff103fa914a349413de5002a1a53390c9a3

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

Title:
  ubuntu_squashfs_smoke_test failed with Disco

Status in ubuntu-kernel-tests:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Tested on a KVM node with generic kernel.

  $ sudo 
/home/ubuntu/autotest/client/tests/ubuntu_squashfs_smoke_test/ubuntu_squashfs_smoke_test.sh
 
  Testing with compression method gzip
  Testing mount of squashfs: PASSED (gzip)
  Testing umount of squashfs: PASSED (gzip)
  Checking data integrity: FAILED (squashed /bin different from original /bin, 
gzip)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec  7 07:39 seq
   crw-rw 1 root audio 116, 33 Dec  7 07:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu14
  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 Dec  7 07:44:11 2018
  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-11-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  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/1807341/+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 1807341] Re: ubuntu_squashfs_smoke_test failed with Disco

2018-12-11 Thread Colin Ian King
@Sam, do you mind retesting this?

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

Title:
  ubuntu_squashfs_smoke_test failed with Disco

Status in ubuntu-kernel-tests:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Tested on a KVM node with generic kernel.

  $ sudo 
/home/ubuntu/autotest/client/tests/ubuntu_squashfs_smoke_test/ubuntu_squashfs_smoke_test.sh
 
  Testing with compression method gzip
  Testing mount of squashfs: PASSED (gzip)
  Testing umount of squashfs: PASSED (gzip)
  Checking data integrity: FAILED (squashed /bin different from original /bin, 
gzip)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec  7 07:39 seq
   crw-rw 1 root audio 116, 33 Dec  7 07:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu14
  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 Dec  7 07:44:11 2018
  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-11-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  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/1807341/+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 1807869] Re: ubuntu_nbd_smoke_test failed with Xenial

2018-12-11 Thread Colin Ian King
** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

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

Title:
  ubuntu_nbd_smoke_test failed with Xenial

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

Bug description:
  Spotted in this cycle with node:
   * daedalus (amd64-lowlatency) - https://pastebin.ubuntu.com/p/JxYNh9JPJd/
   * daedalus (amd64-generic) - https://pastebin.ubuntu.com/p/4W8gDSDVqm/
   * kernel01 (s390x.zVM) - https://pastebin.ubuntu.com/p/kFW7KQbbkf/
   
  Error log from kernel01:
  creating backing nbd image /tmp/nbd_image.img
   
  

  Image path:/tmp/nbd_image.img
  Mount point:   /mnt/nbd-test-22282
  Date:  Mon Dec 10 05:22:47 EST 2018
  Host:  kernel01
  Kernel:4.4.0-141-generic #167-Ubuntu SMP Wed Dec 5 10:32:22 UTC 2018
  Machine:   kernel01 s390x s390x
  CPUs online:   8
  CPUs total:8
  Page size: 4096
  Pages avail:   641567
  Pages total:   977383
  Free space:
  Filesystem   Size  Used Avail Use% 
Mounted on
  udev 1.9G 0  1.9G   0% 
/dev
  tmpfs382M   39M  344M  11% 
/run
  /dev/dasda1  6.7G  6.2G  187M  98% /
  tmpfs1.9G  4.0K  1.9G   1% 
/dev/shm
  tmpfs5.0M 0  5.0M   0% 
/run/lock
  tmpfs1.9G 0  1.9G   0% 
/sys/fs/cgroup
  /dev/mapper/datavg-home   21G  3.1G   17G  17% 
/home
  testpool.3622624G  128K   24G   1% 
/testpool.36226
  testpool.36226/testfs.36226   24G  128K   24G   1% 
/var/tmp/testdir36226
  testpool.36226/testfs.36226/clone 24G  128K   24G   1% 
/var/tmp/testdir36226/clone
  testpool.36226/testfs.36226/renameme  24G  128K   24G   1% 
/var/tmp/testdir36226/renameme
  testpool.36226/testfs.36226/shared24G  128K   24G   1% 
/var/tmp/testdir36226/shared
  testpool.36226/testfs.36226/testfs2.36226 24G  128K   24G   1% 
/var/tmp/testdir36226/testfs2.36226
  testpool.36226/testfs.36226/testfs2.36226.unmounted   24G  128K   24G   1% 
/var/tmp/testdir36226/testfs2.36226.unmounted
  testpool.36226/testfs.36226/unshared  24G  128K   24G   1% 
/var/tmp/testdir36226/unshared
  tmpfs382M 0  382M   0% 
/run/user/1000
  tmpfs100K 0  100K   0% 
/var/lib/lxd/shmounts
  tmpfs100K 0  100K   0% 
/var/lib/lxd/devlxd
  

   
  NBD device /dev/nbd0 created
  found nbd export
  NBD exports found:
  test
  starting clien with NBD device /dev/nbd0
  Negotiation: ..size = 128MB
  creating ext4 on /dev/nbd0
  mkfs on /dev/nbd0 failed
  unmounting /mnt/nbd-test-22282
  stopping client
  disconnect, sock, done
  killing server
  stderr:
  bs=1024, sz=134217728 bytes
  timeout=30
  umount: /mnt/nbd-test-22282: mountpoint not found

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-141-generic 4.4.0-141.167
  ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-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.
  Date: Tue Dec 11 04:08:37 2018
  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=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-141-generic N/A
   linux-backports-modules-4.4.0-141-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory

[Kernel-packages] [Bug 1807341] Re: ubuntu_squashfs_smoke_test failed with Disco

2018-12-11 Thread Colin Ian King
Thanks for the analysis Seth, I'll fix that up.

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

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  ubuntu_squashfs_smoke_test failed with Disco

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

Bug description:
  Tested on a KVM node with generic kernel.

  $ sudo 
/home/ubuntu/autotest/client/tests/ubuntu_squashfs_smoke_test/ubuntu_squashfs_smoke_test.sh
 
  Testing with compression method gzip
  Testing mount of squashfs: PASSED (gzip)
  Testing umount of squashfs: PASSED (gzip)
  Checking data integrity: FAILED (squashed /bin different from original /bin, 
gzip)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec  7 07:39 seq
   crw-rw 1 root audio 116, 33 Dec  7 07:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu14
  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 Dec  7 07:44:11 2018
  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-11-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  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/1807341/+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 1806013] Re: ubuntu_nbd_smoke_test failed when running with the smoke test suite on X 4.4 s390x zVM

2018-12-04 Thread Colin Ian King
Fix committed, commit http://kernel.ubuntu.com/git/ubuntu/autotest-
client-tests.git/commit/?id=9aba531dcecbd1505ac9bac3736f2124af942d34

This makes the server export detection more robust, tested on xenial,
bionic, cosmic and disco, amd64/i386/ppc64el.  Hopefully this will
address all weird mount failures.

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

Title:
  ubuntu_nbd_smoke_test failed when running with the smoke test suite on
  X 4.4 s390x zVM

Status in ubuntu-kernel-tests:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This test can pass if you run it manually on s390x zVM.

  But it will fail when you try to run it with the smoke test suite on
  jenkins.

  And this issue was only spotted on this s390x zVM (kernel01)

    

    Image path:/tmp/nbd_image.img
    Mount point:   /mnt/nbd-test-21931
    Date:  Fri Nov 30 03:13:05 EST 2018
    Host:  kernel01
    Kernel:4.4.0-140-generic #166-Ubuntu SMP Wed Nov 14 20:08:28 UTC 
2018
    Machine:   kernel01 s390x s390x
    CPUs online:   8
    CPUs total:8
    Page size: 4096
    Pages avail:   636227
    Pages total:   977383
    Free space:
    Filesystem   Size  Used Avail Use% 
Mounted on
    udev 1.9G 0  1.9G   0% 
/dev
    tmpfs382M   39M  344M  11% 
/run
    /dev/dasda1  6.7G  5.1G  1.2G  82% /
    tmpfs1.9G  4.0K  1.9G   1% 
/dev/shm
    tmpfs5.0M 0  5.0M   0% 
/run/lock
    tmpfs1.9G 0  1.9G   0% 
/sys/fs/cgroup
    /dev/mapper/datavg-home   21G  1.8G   18G  10% 
/home
    testpool.3622624G 0   24G   0% 
/testpool.36226
    testpool.36226/testfs.36226   24G  128K   24G   1% 
/var/tmp/testdir36226
    testpool.36226/testfs.36226/clone 24G 0   24G   0% 
/var/tmp/testdir36226/clone
    testpool.36226/testfs.36226/renameme  24G 0   24G   0% 
/var/tmp/testdir36226/renameme
    testpool.36226/testfs.36226/shared24G 0   24G   0% 
/var/tmp/testdir36226/shared
    testpool.36226/testfs.36226/testfs2.36226 24G 0   24G   0% 
/var/tmp/testdir36226/testfs2.36226
    testpool.36226/testfs.36226/testfs2.36226.unmounted   24G 0   24G   0% 
/var/tmp/testdir36226/testfs2.36226.unmounted
    testpool.36226/testfs.36226/unshared  24G 0   24G   0% 
/var/tmp/testdir36226/unshared
    tmpfs382M 0  382M   0% 
/run/user/1000
    tmpfs100K 0  100K   0% 
/var/lib/lxd/shmounts
    tmpfs100K 0  100K   0% 
/var/lib/lxd/devlxd
    


    tcp6   0  0 ::: :::*LISTEN  
21955/nbd-server
    mount on /dev/nbd0 failed
    disconnect, sock, done
    stderr:
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on 

[Kernel-packages] [Bug 1806681] Re: hp_wmi: query 0xd returned error 0x5

2018-12-04 Thread Colin Ian King
This does not appear to be an error to worry about. The WMI driver for
your machine is performing a feature query with the ACPI driver with
HPWMI_FEATURE2_QUERY.  This seems to be a feature that is enabled on HP
WMI firmware from around 2009 onwards. Some machines may support this,
however it seems that your firmware does not seem to have support for
this, hence the query failure.

The kernel throws a warning message to indicate that this feature is not
supported. I doubt this is something you need to worry about.

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

Title:
  hp_wmi: query 0xd returned error 0x5

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [   18.296366] hp_wmi: query 0xd returned error 0x5

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2739 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 09:05:38 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806681/+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 1806013] Re: ubuntu_nbd_smoke_test failed when running with the smoke test suite on X 4.4 s390x zVM

2018-12-04 Thread Colin Ian King
** Changed in: ubuntu-kernel-tests
   Importance: Undecided => Medium

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  ubuntu_nbd_smoke_test failed when running with the smoke test suite on
  X 4.4 s390x zVM

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

Bug description:
  This test can pass if you run it manually on s390x zVM.

  But it will fail when you try to run it with the smoke test suite on
  jenkins.

  And this issue was only spotted on this s390x zVM (kernel01)

    

    Image path:/tmp/nbd_image.img
    Mount point:   /mnt/nbd-test-21931
    Date:  Fri Nov 30 03:13:05 EST 2018
    Host:  kernel01
    Kernel:4.4.0-140-generic #166-Ubuntu SMP Wed Nov 14 20:08:28 UTC 
2018
    Machine:   kernel01 s390x s390x
    CPUs online:   8
    CPUs total:8
    Page size: 4096
    Pages avail:   636227
    Pages total:   977383
    Free space:
    Filesystem   Size  Used Avail Use% 
Mounted on
    udev 1.9G 0  1.9G   0% 
/dev
    tmpfs382M   39M  344M  11% 
/run
    /dev/dasda1  6.7G  5.1G  1.2G  82% /
    tmpfs1.9G  4.0K  1.9G   1% 
/dev/shm
    tmpfs5.0M 0  5.0M   0% 
/run/lock
    tmpfs1.9G 0  1.9G   0% 
/sys/fs/cgroup
    /dev/mapper/datavg-home   21G  1.8G   18G  10% 
/home
    testpool.3622624G 0   24G   0% 
/testpool.36226
    testpool.36226/testfs.36226   24G  128K   24G   1% 
/var/tmp/testdir36226
    testpool.36226/testfs.36226/clone 24G 0   24G   0% 
/var/tmp/testdir36226/clone
    testpool.36226/testfs.36226/renameme  24G 0   24G   0% 
/var/tmp/testdir36226/renameme
    testpool.36226/testfs.36226/shared24G 0   24G   0% 
/var/tmp/testdir36226/shared
    testpool.36226/testfs.36226/testfs2.36226 24G 0   24G   0% 
/var/tmp/testdir36226/testfs2.36226
    testpool.36226/testfs.36226/testfs2.36226.unmounted   24G 0   24G   0% 
/var/tmp/testdir36226/testfs2.36226.unmounted
    testpool.36226/testfs.36226/unshared  24G 0   24G   0% 
/var/tmp/testdir36226/unshared
    tmpfs382M 0  382M   0% 
/run/user/1000
    tmpfs100K 0  100K   0% 
/var/lib/lxd/shmounts
    tmpfs100K 0  100K   0% 
/var/lib/lxd/devlxd
    


    tcp6   0  0 ::: :::*LISTEN  
21955/nbd-server
    mount on /dev/nbd0 failed
    disconnect, sock, done
    stderr:
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   

[Kernel-packages] [Bug 1805778] Re: ubuntu_vfat_stress failed again with P8/P9 Bionic

2018-11-30 Thread Colin Ian King
** Changed in: ubuntu-kernel-tests
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu_vfat_stress failed again with P8/P9 Bionic

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

Bug description:
  This issue just like bug 1801907, but this time it's passed with P8
  "modoc", failed with P8 "entei" and P9 "baltar"

  I haven't run them directly, this is the result when testing with the
  whole test suite.

  06:21:04 INFO |   START   ubuntu_vfat_stress.vfat-stress  
ubuntu_vfat_stress.vfat-stress  timestamp=1543472464timeout=18000   
localtime=Nov 29 06:21:04   
  06:21:04 DEBUG| Persistent state client._record_indent now set to 2
  06:21:04 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_vfat_stress.vfat-stress', 'ubuntu_vfat_stress.vfat-stress')
  06:21:04 DEBUG| Waiting for pid 56149 for 18000 seconds
  06:21:04 DEBUG| Running 'LOG=/tmp/vfat-falure.log 
STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
 DURATION=10s bash -c 
/home/ubuntu/autotest/client/tests/ubuntu_vfat_stress/ubuntu_vfat_stress.sh 
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src 2>&1'
  06:21:04 DEBUG| [stdout] Testing: --verify --times --metrics-brief --syslog 
--keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd 
--lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order 
stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 
--hdd-bytes 4M --fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
  06:21:04 DEBUG| [stdout] Mounting tmpfs /mnt/vfat-test-56154
  06:21:05 DEBUG| [stdout] Created loop image 
/mnt/vfat-test-56154/vfat-loop-data
  06:21:05 DEBUG| [stdout] mkfs.fat 4.1 (2017-01-24)
  06:21:06 DEBUG| [stdout]  
  06:21:06 DEBUG| [stdout] 

  06:21:06 DEBUG| [stdout] VFAT options:  allow_utime=20
  06:21:06 DEBUG| [stdout] Stress test:   
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng 
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M 
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
  06:21:06 DEBUG| [stdout] VFAT_IMAGE path: /mnt/vfat-test-56154
  06:21:06 DEBUG| [stdout] Mount point:   /mnt/vfat-test-56154
  06:21:06 DEBUG| [stdout] Date:  Thu Nov 29 06:21:06 UTC 2018
  06:21:06 DEBUG| [stdout] Host:  baltar
  06:21:06 DEBUG| [stdout] Kernel:4.15.0-42-generic #45-Ubuntu SMP Thu 
Nov 15 19:29:37 UTC 2018
  06:21:06 DEBUG| [stdout] Machine:   baltar ppc64le ppc64le
  06:21:06 DEBUG| [stdout] CPUs online:   40
  06:21:06 DEBUG| [stdout] CPUs total:160
  06:21:06 DEBUG| [stdout] Page size: 65536
  06:21:06 DEBUG| [stdout] Pages avail:   1935143
  06:21:06 DEBUG| [stdout] Pages total:   2089666
  06:21:06 DEBUG| [stdout] 

  06:21:06 DEBUG| [stdout]  
  06:21:06 DEBUG| [stdout]  
  06:21:06 DEBUG| [stdout] Started, PID 56225
  06:23:13 DEBUG| [stdout] Timed out waiting for stress-ng to finish
  06:23:13 DEBUG| [stdout] Forcefully killing, PID 56225 (after 121 seconds)
  06:23:23 DEBUG| [stdout] Found kernel warning and/or call trace:
  06:23:23 DEBUG| [stdout]  
  06:23:23 DEBUG| [stdout] [ 4940.791800] Testing: --verify --times 
--metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M 
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
  06:23:23 DEBUG| [stdout] [ 4941.855398] Created loop image 
/mnt/vfat-test-56154/vfat-loop-data
  06:23:23 DEBUG| [stdout] [ 4942.232934] ubuntu_vfat_str (56154): drop_caches: 
1
  06:23:23 DEBUG| [stdout] [ 4942.593708] ubuntu_vfat_str (56154): drop_caches: 
2
  06:23:23 DEBUG| [stdout] [ 4942.597717] ubuntu_vfat_str (56154): drop_caches: 
3
  06:23:23 DEBUG| [stdout] [ 4943.125332] VFAT options:  allow_utime=20
  06:23:23 DEBUG| [stdout] [ 4943.125392] Stress test:   
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng 
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride 

[Kernel-packages] [Bug 1806013] Re: ubuntu_nbd_smoke_test failed when running with the smoke test suite on X 4.4 s390x zVM

2018-11-30 Thread Colin Ian King
Nov 30 03:13:38 kernel01 kernel: [ 1885.704953] block nbd0: NBD_DISCONNECT
Nov 30 03:13:38 kernel01 kernel: [ 1885.704986] block nbd0: shutting down socket
Nov 30 03:13:38 kernel01 kernel: [ 1885.705647] block nbd0: Receive control 
failed (result -32)
Nov 30 03:13:55 kernel01 kernel: [ 1903.026715] EXT4-fs (loop0): mounted 
filesystem with ordered data mode. Opts: usrquota,grpquota
Nov 30 05:06:56 kernel01 kernel: [ 8683.703581] EXT4-fs (nbd0): mounted 
filesystem with ordered data mode. Opts: (null)
Nov 30 05:06:58 kernel01 kernel: [ 8685.937445] block nbd0: NBD_DISCONNECT
Nov 30 05:06:58 kernel01 kernel: [ 8685.937476] block nbd0: shutting down socket
Nov 30 05:06:58 kernel01 kernel: [ 8685.937490] block nbd0: Receive control 
failed (result -32)
Nov 30 05:07:00 kernel01 kernel: [ 8688.261623] nbd: unregistered device at 
major 43
Nov 30 05:15:24 kernel01 kernel: [ 9191.712604] nbd: registered device at major 
43
Nov 30 05:15:35 kernel01 kernel: [ 9202.811133] EXT4-fs (nbd0): mounted 
filesystem with ordered data mode. Opts: (null)
Nov 30 05:15:37 kernel01 kernel: [ 9204.826330] block nbd0: NBD_DISCONNECT
Nov 30 05:15:37 kernel01 kernel: [ 9204.826364] block nbd0: shutting down socket
Nov 30 05:15:37 kernel01 kernel: [ 9204.826391] block nbd0: Receive control 
failed (result -32)
Nov 30 05:15:39 kernel01 kernel: [ 9207.201777] nbd: unregistered device at 
major 43

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

Title:
  ubuntu_nbd_smoke_test failed when running with the smoke test suite on
  X 4.4 s390x zVM

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

Bug description:
  This test can pass if you run it manually on s390x zVM.

  But it will fail when you try to run it with the smoke test suite on
  jenkins.

  And this issue was only spotted on this s390x zVM (kernel01)

    

    Image path:/tmp/nbd_image.img
    Mount point:   /mnt/nbd-test-21931
    Date:  Fri Nov 30 03:13:05 EST 2018
    Host:  kernel01
    Kernel:4.4.0-140-generic #166-Ubuntu SMP Wed Nov 14 20:08:28 UTC 
2018
    Machine:   kernel01 s390x s390x
    CPUs online:   8
    CPUs total:8
    Page size: 4096
    Pages avail:   636227
    Pages total:   977383
    Free space:
    Filesystem   Size  Used Avail Use% 
Mounted on
    udev 1.9G 0  1.9G   0% 
/dev
    tmpfs382M   39M  344M  11% 
/run
    /dev/dasda1  6.7G  5.1G  1.2G  82% /
    tmpfs1.9G  4.0K  1.9G   1% 
/dev/shm
    tmpfs5.0M 0  5.0M   0% 
/run/lock
    tmpfs1.9G 0  1.9G   0% 
/sys/fs/cgroup
    /dev/mapper/datavg-home   21G  1.8G   18G  10% 
/home
    testpool.3622624G 0   24G   0% 
/testpool.36226
    testpool.36226/testfs.36226   24G  128K   24G   1% 
/var/tmp/testdir36226
    testpool.36226/testfs.36226/clone 24G 0   24G   0% 
/var/tmp/testdir36226/clone
    testpool.36226/testfs.36226/renameme  24G 0   24G   0% 
/var/tmp/testdir36226/renameme
    testpool.36226/testfs.36226/shared24G 0   24G   0% 
/var/tmp/testdir36226/shared
    testpool.36226/testfs.36226/testfs2.36226 24G 0   24G   0% 
/var/tmp/testdir36226/testfs2.36226
    testpool.36226/testfs.36226/testfs2.36226.unmounted   24G 0   24G   0% 
/var/tmp/testdir36226/testfs2.36226.unmounted
    testpool.36226/testfs.36226/unshared  24G 0   24G   0% 
/var/tmp/testdir36226/unshared
    tmpfs382M 0  382M   0% 
/run/user/1000
    tmpfs100K 0  100K   0% 
/var/lib/lxd/shmounts
    tmpfs100K 0  100K   0% 
/var/lib/lxd/devlxd
    


    tcp6   0  0 ::: :::*LISTEN  
21955/nbd-server
    mount on /dev/nbd0 failed
    disconnect, sock, done
    stderr:
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
    mount: wrong fs type, bad option, bad superblock on /dev/nbd0,
   missing codepage or helper program, or other error

   In some cases useful info is found in 

[Kernel-packages] [Bug 1805778] Re: ubuntu_vfat_stress failed again with P8/P9 Bionic

2018-11-29 Thread Colin Ian King
Sam, can this be retested, I think we were getting into dirty page write
amplification because of using vfat on a tmpfs backing store file. I've
reworked the test now to use bog standard vfat on a loopbacked file.

Fix committed: http://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=e39a7d03a6dbda3039514096737d72150877017b

** No longer affects: stress-ng

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

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

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  ubuntu_vfat_stress failed again with P8/P9 Bionic

Status in ubuntu-kernel-tests:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  This issue just like bug 1801907, but this time it's passed with P8
  "modoc", failed with P8 "entei" and P9 "baltar"

  I haven't run them directly, this is the result when testing with the
  whole test suite.

  06:21:04 INFO |   START   ubuntu_vfat_stress.vfat-stress  
ubuntu_vfat_stress.vfat-stress  timestamp=1543472464timeout=18000   
localtime=Nov 29 06:21:04   
  06:21:04 DEBUG| Persistent state client._record_indent now set to 2
  06:21:04 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_vfat_stress.vfat-stress', 'ubuntu_vfat_stress.vfat-stress')
  06:21:04 DEBUG| Waiting for pid 56149 for 18000 seconds
  06:21:04 DEBUG| Running 'LOG=/tmp/vfat-falure.log 
STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
 DURATION=10s bash -c 
/home/ubuntu/autotest/client/tests/ubuntu_vfat_stress/ubuntu_vfat_stress.sh 
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src 2>&1'
  06:21:04 DEBUG| [stdout] Testing: --verify --times --metrics-brief --syslog 
--keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd 
--lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order 
stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 
--hdd-bytes 4M --fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
  06:21:04 DEBUG| [stdout] Mounting tmpfs /mnt/vfat-test-56154
  06:21:05 DEBUG| [stdout] Created loop image 
/mnt/vfat-test-56154/vfat-loop-data
  06:21:05 DEBUG| [stdout] mkfs.fat 4.1 (2017-01-24)
  06:21:06 DEBUG| [stdout]  
  06:21:06 DEBUG| [stdout] 

  06:21:06 DEBUG| [stdout] VFAT options:  allow_utime=20
  06:21:06 DEBUG| [stdout] Stress test:   
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng 
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M 
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
  06:21:06 DEBUG| [stdout] VFAT_IMAGE path: /mnt/vfat-test-56154
  06:21:06 DEBUG| [stdout] Mount point:   /mnt/vfat-test-56154
  06:21:06 DEBUG| [stdout] Date:  Thu Nov 29 06:21:06 UTC 2018
  06:21:06 DEBUG| [stdout] Host:  baltar
  06:21:06 DEBUG| [stdout] Kernel:4.15.0-42-generic #45-Ubuntu SMP Thu 
Nov 15 19:29:37 UTC 2018
  06:21:06 DEBUG| [stdout] Machine:   baltar ppc64le ppc64le
  06:21:06 DEBUG| [stdout] CPUs online:   40
  06:21:06 DEBUG| [stdout] CPUs total:160
  06:21:06 DEBUG| [stdout] Page size: 65536
  06:21:06 DEBUG| [stdout] Pages avail:   1935143
  06:21:06 DEBUG| [stdout] Pages total:   2089666
  06:21:06 DEBUG| [stdout] 

  06:21:06 DEBUG| [stdout]  
  06:21:06 DEBUG| [stdout]  
  06:21:06 DEBUG| [stdout] Started, PID 56225
  06:23:13 DEBUG| [stdout] Timed out waiting for stress-ng to finish
  06:23:13 DEBUG| [stdout] Forcefully killing, PID 56225 (after 121 seconds)
  06:23:23 DEBUG| [stdout] Found kernel warning and/or call trace:
  06:23:23 DEBUG| [stdout]  
  06:23:23 DEBUG| [stdout] [ 4940.791800] Testing: --verify --times 
--metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M 
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
  06:23:23 DEBUG| [stdout] [ 4941.855398] Created loop image 
/mnt/vfat-test-56154/vfa

[Kernel-packages] [Bug 1805778] Re: ubuntu_vfat_stress failed again with P8/P9 Bionic

2018-11-29 Thread Colin Ian King
OK, managed to reproduce this:

[ 3913.025219] VFAT options:  check=s
[ 3913.025268] Stress test:   
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng 
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M 
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
[ 3913.025287] Mount point:   /mnt/vfat-test-75202
[ 3913.025760] Started, PID 74908

Nov 29 12:53:00 baltar kernel: [ 4110.095234] INFO: task kworker/u321:3:80990 
blocked for more than 120 seconds.
Nov 29 12:53:00 baltar kernel: [ 4110.095309]   Not tainted 
4.15.0-39-generic #42-Ubuntu
Nov 29 12:53:00 baltar kernel: [ 4110.095345] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 29 12:53:00 baltar kernel: [ 4110.095398] kworker/u321:3  D0 80990  
2 0x0800
Nov 29 12:53:00 baltar kernel: [ 4110.095406] Workqueue: writeback wb_workfn 
(flush-7:0)
Nov 29 12:53:00 baltar kernel: [ 4110.095408] Call Trace:
Nov 29 12:53:00 baltar kernel: [ 4110.095411] [c00feb7b6af0] 
[c00feb7b6b60] 0xc00feb7b6b60 (unreliable)
Nov 29 12:53:00 baltar kernel: [ 4110.095416] [c00feb7b6cc0] 
[c001c1d0] __switch_to+0x2a0/0x4d0
Nov 29 12:53:00 baltar kernel: [ 4110.095419] [c00feb7b6d20] 
[c0cfd2e4] __schedule+0x2a4/0xaf0
Nov 29 12:53:00 baltar kernel: [ 4110.095423] [c00feb7b6df0] 
[c0cfdb70] schedule+0x40/0xc0
Nov 29 12:53:00 baltar kernel: [ 4110.095426] [c00feb7b6e10] 
[c0152e7c] io_schedule+0x2c/0x50
Nov 29 12:53:00 baltar kernel: [ 4110.095429] [c00feb7b6e40] 
[c06d1e04] wbt_wait+0x484/0x4e0
Nov 29 12:53:00 baltar kernel: [ 4110.095432] [c00feb7b6ee0] 
[c0698e74] blk_mq_make_request+0x104/0x6e0
Nov 29 12:53:00 baltar kernel: [ 4110.095436] [c00feb7b6f80] 
[c0686a34] generic_make_request+0x124/0x380
Nov 29 12:53:00 baltar kernel: [ 4110.095439] [c00feb7b6ff0] 
[c0686d4c] submit_bio+0xbc/0x1d0
Nov 29 12:53:00 baltar kernel: [ 4110.095442] [c00feb7b70a0] 
[c042de2c] submit_bh_wbc+0x1dc/0x240
Nov 29 12:53:00 baltar kernel: [ 4110.095445] [c00feb7b70f0] 
[c042e108] __block_write_full_page+0x278/0x570
Nov 29 12:53:00 baltar kernel: [ 4110.095448] [c00feb7b7190] 
[c054ac6c] fat_writepage+0x2c/0x40
Nov 29 12:53:00 baltar kernel: [ 4110.095451] [c00feb7b71b0] 
[c043bdf0] __mpage_writepage+0x170/0x7b0
Nov 29 12:53:00 baltar kernel: [ 4110.095455] [c00feb7b76e0] 
[c02f2d9c] write_cache_pages+0x25c/0x590
Nov 29 12:53:00 baltar kernel: [ 4110.095457] [c00feb7b7820] 
[c043bac8] mpage_writepages+0x78/0x150
Nov 29 12:53:00 baltar kernel: [ 4110.095460] [c00feb7b78b0] 
[c054abe8] fat_writepages+0x28/0x40
Nov 29 12:53:00 baltar kernel: [ 4110.095463] [c00feb7b78d0] 
[c02f5f1c] do_writepages+0x4c/0x130
Nov 29 12:53:00 baltar kernel: [ 4110.095465] [c00feb7b7940] 
[c041eff0] __writeback_single_inode+0x70/0x570
Nov 29 12:53:00 baltar kernel: [ 4110.095468] [c00feb7b79a0] 
[c041fb8c] writeback_sb_inodes+0x26c/0x5d0
Nov 29 12:53:00 baltar kernel: [ 4110.095470] [c00feb7b7ab0] 
[c042024c] wb_writeback+0x13c/0x460
Nov 29 12:53:00 baltar kernel: [ 4110.095472] [c00feb7b7b80] 
[c0420f20] wb_workfn+0x100/0x5e0
Nov 29 12:53:00 baltar kernel: [ 4110.095475] [c00feb7b7c90] 
[c0134bd8] process_one_work+0x298/0x5a0
Nov 29 12:53:00 baltar kernel: [ 4110.095478] [c00feb7b7d20] 
[c0134f78] worker_thread+0x98/0x630
Nov 29 12:53:00 baltar kernel: [ 4110.095480] [c00feb7b7dc0] 
[c013db48] kthread+0x1a8/0x1b0
Nov 29 12:53:00 baltar kernel: [ 4110.095484] [c00feb7b7e30] 
[c000b658] ret_from_kernel_thread+0x5c/0x84
Nov 29 12:53:00 baltar kernel: [ 4110.095487] INFO: task stress-ng:74924 
blocked for more than 120 seconds.
Nov 29 12:53:00 baltar kernel: [ 4110.095531]   Not tainted 
4.15.0-39-generic #42-Ubuntu

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

Title:
  ubuntu_vfat_stress failed again with P8/P9 Bionic

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

Bug description:
  This issue just like bug 1801907, but this time it's passed with P8
  "modoc", failed with P8 "entei" and P9 "baltar"

  I haven't run them directly, this is the result when testing with the
  whole test suite.

  06:21:04 INFO |   START   ubuntu_vfat_stress.vfat-stress  
ubuntu_vfat_stress.vfat-stress  timestamp=1543472464timeout=18000   
localtime=Nov 29 06:21:04   
  06:21:04 DEBUG| Persistent state client._record_indent now 

[Kernel-packages] [Bug 1805778] Re: ubuntu_vfat_stress failed again with P8/P9 Bionic

2018-11-29 Thread Colin Ian King
Started, PID 107847
  stress-ng now terminated
  Stopped, PID 107847 (after 4 seconds)
  umounting vfat
  umount: /mnt/vfat-test-15951: target is busy.
  umount vfat /mnt/vfat-test-15951 failed
  umounting tmpfs
  umount: /mnt/vfat-test-15951: target is busy.
  umount /mnt/vfat-test-15951 failed
  rmdir: failed to remove '/mnt/vfat-test-15951': Device or resource busy

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

Title:
  ubuntu_vfat_stress failed again with P8/P9 Bionic

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

Bug description:
  This issue just like bug 1801907, but this time it's passed with P8
  "modoc", failed with P8 "entei" and P9 "baltar"

  I haven't run them directly, this is the result when testing with the
  whole test suite.

  06:21:04 INFO |   START   ubuntu_vfat_stress.vfat-stress  
ubuntu_vfat_stress.vfat-stress  timestamp=1543472464timeout=18000   
localtime=Nov 29 06:21:04   
  06:21:04 DEBUG| Persistent state client._record_indent now set to 2
  06:21:04 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_vfat_stress.vfat-stress', 'ubuntu_vfat_stress.vfat-stress')
  06:21:04 DEBUG| Waiting for pid 56149 for 18000 seconds
  06:21:04 DEBUG| Running 'LOG=/tmp/vfat-falure.log 
STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
 DURATION=10s bash -c 
/home/ubuntu/autotest/client/tests/ubuntu_vfat_stress/ubuntu_vfat_stress.sh 
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src 2>&1'
  06:21:04 DEBUG| [stdout] Testing: --verify --times --metrics-brief --syslog 
--keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd 
--lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order 
stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 
--hdd-bytes 4M --fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
  06:21:04 DEBUG| [stdout] Mounting tmpfs /mnt/vfat-test-56154
  06:21:05 DEBUG| [stdout] Created loop image 
/mnt/vfat-test-56154/vfat-loop-data
  06:21:05 DEBUG| [stdout] mkfs.fat 4.1 (2017-01-24)
  06:21:06 DEBUG| [stdout]  
  06:21:06 DEBUG| [stdout] 

  06:21:06 DEBUG| [stdout] VFAT options:  allow_utime=20
  06:21:06 DEBUG| [stdout] Stress test:   
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng 
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M 
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
  06:21:06 DEBUG| [stdout] VFAT_IMAGE path: /mnt/vfat-test-56154
  06:21:06 DEBUG| [stdout] Mount point:   /mnt/vfat-test-56154
  06:21:06 DEBUG| [stdout] Date:  Thu Nov 29 06:21:06 UTC 2018
  06:21:06 DEBUG| [stdout] Host:  baltar
  06:21:06 DEBUG| [stdout] Kernel:4.15.0-42-generic #45-Ubuntu SMP Thu 
Nov 15 19:29:37 UTC 2018
  06:21:06 DEBUG| [stdout] Machine:   baltar ppc64le ppc64le
  06:21:06 DEBUG| [stdout] CPUs online:   40
  06:21:06 DEBUG| [stdout] CPUs total:160
  06:21:06 DEBUG| [stdout] Page size: 65536
  06:21:06 DEBUG| [stdout] Pages avail:   1935143
  06:21:06 DEBUG| [stdout] Pages total:   2089666
  06:21:06 DEBUG| [stdout] 

  06:21:06 DEBUG| [stdout]  
  06:21:06 DEBUG| [stdout]  
  06:21:06 DEBUG| [stdout] Started, PID 56225
  06:23:13 DEBUG| [stdout] Timed out waiting for stress-ng to finish
  06:23:13 DEBUG| [stdout] Forcefully killing, PID 56225 (after 121 seconds)
  06:23:23 DEBUG| [stdout] Found kernel warning and/or call trace:
  06:23:23 DEBUG| [stdout]  
  06:23:23 DEBUG| [stdout] [ 4940.791800] Testing: --verify --times 
--metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M 
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
  06:23:23 DEBUG| [stdout] [ 4941.855398] Created loop image 
/mnt/vfat-test-56154/vfat-loop-data
  06:23:23 DEBUG| [stdout] [ 4942.232934] ubuntu_vfat_str (56154): drop_caches: 
1
  06:23:23 DEBUG| [stdout] [ 4942.593708] ubuntu_vfat_str (56154): drop_caches: 
2
  06:23:23 DEBUG| [stdout] [ 4942.597717] ubuntu_vfat_str (56154): drop_caches: 
3
  06:23:23 DEBUG| [stdout] [ 4943.125332] VFAT options:  allow_utime=20
  06:23:23 DEBUG| [stdout] [ 4943.125392] Stress test:   

[Kernel-packages] [Bug 1805778] Re: ubuntu_vfat_stress failed again with P8/P9 Bionic

2018-11-29 Thread Colin Ian King
Seems like a process is still running at umount time and a re-mount
fails. I think it snowballs after that.

[ 1209.031563] Mount point:   /mnt/vfat-test-15951
[ 1209.032392] Started, PID 67047
[ 1224.249103] stress-ng now terminated
[ 1224.249203] Stopped, PID 67047 (after 14 seconds)
[ 1224.249312] umounting vfat
[ 1224.468077] umounting tmpfs
[ 1224.548526] Testing: --verify --times --metrics-brief --syslog --keep-name 
-t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 
--seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order stride 
--fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 
--hdd-bytes 4M --fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
[ 1225.606221] Created loop image /mnt/vfat-test-15951/vfat-loop-data
[ 1225.684994] ubuntu_vfat_str (15951): drop_caches: 1
[ 1225.692320] ubuntu_vfat_str (15951): drop_caches: 2
[ 1225.695075] ubuntu_vfat_str (15951): drop_caches: 3
[ 1226.046191] VFAT options:  fmask=777
[ 1226.046241] Stress test:   
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng 
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M 
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
[ 1226.046261] Mount point:   /mnt/vfat-test-15951
[ 1226.046733] Started, PID 107847
[ 1230.696549] stress-ng now terminated
[ 1230.696689] Stopped, PID 107847 (after 4 seconds)
[ 1230.696870] umounting vfat
[ 1230.729214] umount vfat /mnt/vfat-test-15951 failed
[ 1230.729283] umounting tmpfs
[ 1230.730847] umount /mnt/vfat-test-15951 failed
[ 1230.746365] /mnt/vfat-test-15951 is already mounted!

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

Title:
  ubuntu_vfat_stress failed again with P8/P9 Bionic

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

Bug description:
  This issue just like bug 1801907, but this time it's passed with P8
  "modoc", failed with P8 "entei" and P9 "baltar"

  I haven't run them directly, this is the result when testing with the
  whole test suite.

  06:21:04 INFO |   START   ubuntu_vfat_stress.vfat-stress  
ubuntu_vfat_stress.vfat-stress  timestamp=1543472464timeout=18000   
localtime=Nov 29 06:21:04   
  06:21:04 DEBUG| Persistent state client._record_indent now set to 2
  06:21:04 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_vfat_stress.vfat-stress', 'ubuntu_vfat_stress.vfat-stress')
  06:21:04 DEBUG| Waiting for pid 56149 for 18000 seconds
  06:21:04 DEBUG| Running 'LOG=/tmp/vfat-falure.log 
STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
 DURATION=10s bash -c 
/home/ubuntu/autotest/client/tests/ubuntu_vfat_stress/ubuntu_vfat_stress.sh 
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src 2>&1'
  06:21:04 DEBUG| [stdout] Testing: --verify --times --metrics-brief --syslog 
--keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd 
--lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order 
stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 
--hdd-bytes 4M --fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
  06:21:04 DEBUG| [stdout] Mounting tmpfs /mnt/vfat-test-56154
  06:21:05 DEBUG| [stdout] Created loop image 
/mnt/vfat-test-56154/vfat-loop-data
  06:21:05 DEBUG| [stdout] mkfs.fat 4.1 (2017-01-24)
  06:21:06 DEBUG| [stdout]  
  06:21:06 DEBUG| [stdout] 

  06:21:06 DEBUG| [stdout] VFAT options:  allow_utime=20
  06:21:06 DEBUG| [stdout] Stress test:   
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng 
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M 
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
  06:21:06 DEBUG| [stdout] VFAT_IMAGE path: /mnt/vfat-test-56154
  06:21:06 DEBUG| [stdout] Mount point:   /mnt/vfat-test-56154
  06:21:06 DEBUG| [stdout] Date:  Thu Nov 29 06:21:06 UTC 2018
  06:21:06 DEBUG| [stdout] Host:  baltar
  06:21:06 DEBUG| [stdout] Kernel:4.15.0-42-generic #45-Ubuntu SMP Thu 
Nov 15 19:29:37 UTC 2018
  06:21:06 DEBUG| [stdout] Machine:   baltar ppc64le ppc64le
  06:21:06 DEBUG| [stdout] CPUs online:   40
  06:21:06 DEBUG| [stdout] CPUs total:160
  06:21:06 DEBUG| [stdout] Page 

[Kernel-packages] [Bug 1805627] Re: zfs-linux 0.7.12-1ubuntu1 ADT test failure with linux 4.19.0-7.8

2018-11-28 Thread Colin Ian King
Unless I am mistaken, the autotests for ZFS blacklist i386 platforms, so
no idea why this is being run.

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

Title:
  zfs-linux 0.7.12-1ubuntu1 ADT test failure with linux 4.19.0-7.8

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-bootstrap/disco/i386/z/zfs-linux/20181128_052301_6f831@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1805627/+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 1805627] Re: zfs-linux 0.7.12-1ubuntu1 ADT test failure with linux 4.19.0-7.8

2018-11-28 Thread Colin Ian King
ZFS is not intended for 32 bit targets, no idea why this is being tested
on this arch.

@Sam, any ideas?

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

** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  zfs-linux 0.7.12-1ubuntu1 ADT test failure with linux 4.19.0-7.8

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-bootstrap/disco/i386/z/zfs-linux/20181128_052301_6f831@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1805627/+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 1782565] Re: s390 illegal operation

2018-11-19 Thread Colin Ian King
Nor on 4.15 anymore, I suspect this may have been fixed with a stable
fix.

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

** Changed in: linux (Ubuntu Bionic)
   Status: Incomplete => Won't Fix

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

** Changed in: linux (Ubuntu Bionic)
   Status: Won't Fix => Fix Released

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

Title:
  s390 illegal operation

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Managed to break sysfs when running:

  sudo ./stress-ng  --sysfs 4 -t 60 -v --verify

  
  Kernel: 4.15.0-29-generic and 4.17 too, this seems to occur on previous 4.15 
kernels but I've not tested too far back.

  
  [   45.057702] [ cut here ]
  [   45.057704] kernel BUG at 
/build/linux-4OqUyO/linux-4.15.0/drivers/block/virtio_blk.c:565!
  [   45.057773] illegal operation: 0001 ilc:1 [#1] SMP 
  [   45.057775] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) 
icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 
des_generic sha512_s390 sha256_s390 sha1_s390 sha_common vfio_ccw vfio_mdev 
mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi nfsd auth_rpcgss nfs_acl lockd grace 
scsi_transport_iscsi sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 linear crc32_vx_s390 virtio_net virtio_blk
  [   45.057805] CPU: 0 PID: 5056 Comm: stress-ng-sysfs Tainted: P   O  
   4.15.0-29-generic #31-Ubuntu
  [   45.057806] Hardware name: IBM 2964 N63 400 (KVM/Linux)
  [   45.057809] Krnl PSW : 2a20609d 800ebb38 
(virtblk_cache_type_show+0x82/0x88 [virtio_blk])
  [   45.057814]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [   45.057816] Krnl GPRS: de6dc5c2778317a7 7ff93a20 0080 
1164
  [   45.057818]03ff800058da 1165 6b9cc840 
7061a100
  [   45.057819] 0068feb8 72c30d80 
71972000
  [   45.057821]03ff80008210 1000 03ff800058da 
70a47ce8
  [   45.057830] Krnl Code: 03ff80005912: ebbff0a80004  lmg 
%r11,%r15,168(%r15)
03ff80005918: c0f40560  brcl
15,3ff800063d8
   #03ff8000591e: a7f40001  brc 
15,3ff80005920
   >03ff80005922: 0707  bcr 0,%r7
03ff80005924: 0707  bcr 0,%r7
03ff80005926: 0707  bcr 0,%r7
03ff80005928: c004  brcl
0,3ff80005928
03ff8000592e: eb6ff0480024  stmg
%r6,%r15,72(%r15)
  [   45.057844] Call Trace:
  [   45.057847] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 
[virtio_blk])
  [   45.057852]  [<0068fef4>] dev_attr_show+0x3c/0x80 
  [   45.057858]  [<00424414>] sysfs_kf_seq_show+0xbc/0x1a8 
  [   45.057862]  [<003afddc>] seq_read+0xec/0x4c8 
  [   45.057865]  [<00381bba>] vfs_read+0x8a/0x150 
  [   45.057867]  [<00382156>] SyS_read+0x66/0xe0 
  [   45.057872]  [<008e2350>] system_call+0xdc/0x2c8 
  [   45.057873] Last Breaking-Event-Address:
  [   45.057875]  [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 
[virtio_blk]
  [   45.057876]  
  [   45.057877] ---[ end trace 49fd8401e53e0e99 ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782565/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2018-11-19 Thread Colin Ian King
Pending on what upstream says about this fix.

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1782565] Re: s390 illegal operation

2018-11-19 Thread Colin Ian King
Can't hit this now on 4.18

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

Title:
  s390 illegal operation

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Managed to break sysfs when running:

  sudo ./stress-ng  --sysfs 4 -t 60 -v --verify

  
  Kernel: 4.15.0-29-generic and 4.17 too, this seems to occur on previous 4.15 
kernels but I've not tested too far back.

  
  [   45.057702] [ cut here ]
  [   45.057704] kernel BUG at 
/build/linux-4OqUyO/linux-4.15.0/drivers/block/virtio_blk.c:565!
  [   45.057773] illegal operation: 0001 ilc:1 [#1] SMP 
  [   45.057775] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) 
icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 
des_generic sha512_s390 sha256_s390 sha1_s390 sha_common vfio_ccw vfio_mdev 
mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi nfsd auth_rpcgss nfs_acl lockd grace 
scsi_transport_iscsi sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 linear crc32_vx_s390 virtio_net virtio_blk
  [   45.057805] CPU: 0 PID: 5056 Comm: stress-ng-sysfs Tainted: P   O  
   4.15.0-29-generic #31-Ubuntu
  [   45.057806] Hardware name: IBM 2964 N63 400 (KVM/Linux)
  [   45.057809] Krnl PSW : 2a20609d 800ebb38 
(virtblk_cache_type_show+0x82/0x88 [virtio_blk])
  [   45.057814]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [   45.057816] Krnl GPRS: de6dc5c2778317a7 7ff93a20 0080 
1164
  [   45.057818]03ff800058da 1165 6b9cc840 
7061a100
  [   45.057819] 0068feb8 72c30d80 
71972000
  [   45.057821]03ff80008210 1000 03ff800058da 
70a47ce8
  [   45.057830] Krnl Code: 03ff80005912: ebbff0a80004  lmg 
%r11,%r15,168(%r15)
03ff80005918: c0f40560  brcl
15,3ff800063d8
   #03ff8000591e: a7f40001  brc 
15,3ff80005920
   >03ff80005922: 0707  bcr 0,%r7
03ff80005924: 0707  bcr 0,%r7
03ff80005926: 0707  bcr 0,%r7
03ff80005928: c004  brcl
0,3ff80005928
03ff8000592e: eb6ff0480024  stmg
%r6,%r15,72(%r15)
  [   45.057844] Call Trace:
  [   45.057847] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 
[virtio_blk])
  [   45.057852]  [<0068fef4>] dev_attr_show+0x3c/0x80 
  [   45.057858]  [<00424414>] sysfs_kf_seq_show+0xbc/0x1a8 
  [   45.057862]  [<003afddc>] seq_read+0xec/0x4c8 
  [   45.057865]  [<00381bba>] vfs_read+0x8a/0x150 
  [   45.057867]  [<00382156>] SyS_read+0x66/0xe0 
  [   45.057872]  [<008e2350>] system_call+0xdc/0x2c8 
  [   45.057873] Last Breaking-Event-Address:
  [   45.057875]  [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 
[virtio_blk]
  [   45.057876]  
  [   45.057877] ---[ end trace 49fd8401e53e0e99 ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782565/+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 1793464] Re: Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel

2018-11-19 Thread Colin Ian King
** Changed in: linux (Ubuntu)
   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/1793464

Title:
  Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel

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

Bug description:
  == SRU Justification ==

  When running the Ubuntu nbd autotest regression test we trip a hang
  and then a little later a panic message.  There are two upstream
  fixes required as this is actually two issues in one. One fix is to 
  not to shutdown the sock when IRQs are disable and a second to fix is
  to race in the nbd ioctl.

  == Fix ==

  Upstream commits:

  23272a6754b81ff6503e09c743bb4ceeeab39997
nbd: Remove signal usage

  1f7b5cf1be4351e60cf8ae7aab976503dd73c5f8
nbd: Timeouts are not user requested disconnects

  0e4f0f6f63d3416a9e529d99febfe98545427b81
nbd: Cleanup reset of nbd and bdev after a disconnect

  c261189862c6f65117eb3b1748622a08ef49c262
nbd: don't shutdown sock with irq's disabled

  97240963eb308d8d21a89c0459822f7ea98463b4
nbd: fix race in ioctl

  The first 3 patches are prerequisites required for the latter two fixes to 
apply and work correctly.  Most of these backports are minor patch wiggles
  required because later patches have been applied to the driver in earlier 
fixes to this driver.
 

  == Regression Potential ==

  These fixes just touch nbd, so the regression potential is just
  limited to this. Secondly, we are pulling in upstream fixes that exist
  in Bionic and Cosmic kernels, so these are tried and tested fixes.

  == Test Case ==

1. Deploy a node with 4.4 Xenial
2. Run the ubuntu_nbd_smoke_test

  Without the fix, we get hang/crashes.  With the fix one can run this test
  multiple times without any issues at all.

  
  

  This issue can be reproduced on AMD64 KVM //bare-metal node, s390x
  zKVM node

  The test itself will pass, but the system will hang after a few
  second.

  Steps:
    1. Deploy a node with 4.4 Xenial
    2. Run the ubuntu_nbd_smoke_test

  If you have access to the console, you will see that this system
  actually bumped into a kernel panic:

   Unable to handle kernel pointer dereference in virtual kernel address space
   failing address: 03ff802c1000 TEID: 03ff802c1803
   Fault in home space mode while using kernel ASCE.
   Log here (s390x KVM): https://pastebin.ubuntu.com/p/dNmtvbGjmz/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-136-generic 4.4.0-136.162
  ProcVersionSignature: Ubuntu 4.4.0-136.162-generic 4.4.144
  Uname: Linux 4.4.0-136-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.
  Date: Thu Sep 20 03:46:00 2018
  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-136-generic N/A
   linux-backports-modules-4.4.0-136-generic  N/A
   linux-firmware 1.157.20
  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/1793464/+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 1782565] Re: s390 illegal operation

2018-11-18 Thread Colin Ian King
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

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

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

Title:
  s390 illegal operation

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  Managed to break sysfs when running:

  sudo ./stress-ng  --sysfs 4 -t 60 -v --verify

  
  Kernel: 4.15.0-29-generic and 4.17 too, this seems to occur on previous 4.15 
kernels but I've not tested too far back.

  
  [   45.057702] [ cut here ]
  [   45.057704] kernel BUG at 
/build/linux-4OqUyO/linux-4.15.0/drivers/block/virtio_blk.c:565!
  [   45.057773] illegal operation: 0001 ilc:1 [#1] SMP 
  [   45.057775] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) 
icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 
des_generic sha512_s390 sha256_s390 sha1_s390 sha_common vfio_ccw vfio_mdev 
mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi nfsd auth_rpcgss nfs_acl lockd grace 
scsi_transport_iscsi sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 linear crc32_vx_s390 virtio_net virtio_blk
  [   45.057805] CPU: 0 PID: 5056 Comm: stress-ng-sysfs Tainted: P   O  
   4.15.0-29-generic #31-Ubuntu
  [   45.057806] Hardware name: IBM 2964 N63 400 (KVM/Linux)
  [   45.057809] Krnl PSW : 2a20609d 800ebb38 
(virtblk_cache_type_show+0x82/0x88 [virtio_blk])
  [   45.057814]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [   45.057816] Krnl GPRS: de6dc5c2778317a7 7ff93a20 0080 
1164
  [   45.057818]03ff800058da 1165 6b9cc840 
7061a100
  [   45.057819] 0068feb8 72c30d80 
71972000
  [   45.057821]03ff80008210 1000 03ff800058da 
70a47ce8
  [   45.057830] Krnl Code: 03ff80005912: ebbff0a80004  lmg 
%r11,%r15,168(%r15)
03ff80005918: c0f40560  brcl
15,3ff800063d8
   #03ff8000591e: a7f40001  brc 
15,3ff80005920
   >03ff80005922: 0707  bcr 0,%r7
03ff80005924: 0707  bcr 0,%r7
03ff80005926: 0707  bcr 0,%r7
03ff80005928: c004  brcl
0,3ff80005928
03ff8000592e: eb6ff0480024  stmg
%r6,%r15,72(%r15)
  [   45.057844] Call Trace:
  [   45.057847] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 
[virtio_blk])
  [   45.057852]  [<0068fef4>] dev_attr_show+0x3c/0x80 
  [   45.057858]  [<00424414>] sysfs_kf_seq_show+0xbc/0x1a8 
  [   45.057862]  [<003afddc>] seq_read+0xec/0x4c8 
  [   45.057865]  [<00381bba>] vfs_read+0x8a/0x150 
  [   45.057867]  [<00382156>] SyS_read+0x66/0xe0 
  [   45.057872]  [<008e2350>] system_call+0xdc/0x2c8 
  [   45.057873] Last Breaking-Event-Address:
  [   45.057875]  [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 
[virtio_blk]
  [   45.057876]  
  [   45.057877] ---[ end trace 49fd8401e53e0e99 ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782565/+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 1797546] Re: dev test in ubuntu_stress_smoke_test cause kernel oops on T-3.13

2018-11-16 Thread Colin Ian King
@Sam, this needs to be verified and I don't have access to the H/W. Do
you mind either providing me with an instance to test it on, or running
the verification yourself.

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

Title:
  dev test in ubuntu_stress_smoke_test cause kernel oops on T-3.13

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  SRU Request [Trusty]

  == Justification ==

  It is possible to cause an oops in drm with an unimplemented ioctl call
  with the following reproducer run as root:

  #include 
  #include 
  #include 
  #include 

  int main(void)
  {
  int ptnum, fd;

  fd = open("/dev/dri/card0", O_RDWR);
  return ioctl(fd, TIOCGPTN, );
  }

  == Fix ==

  A backport (minor wiggle) of upstream commit 1539fb9bd405
  ("drm: fix NULL pointer access by wrong ioctl").

  == Testing ==

  Run the reproducer above as root, it will trip the oops. With the fix
  this oops won't occur.

  == Regression Potential ==

  Minimal, this is an upstream fix to this exact issue and has been in
  the kernel since 3.16

  


  This is a bare-metal node running with 3.13.0-160 amd64 kernel.

  The dev test will cause kernel oops:
    dev STARTING
    dev RETURNED 0
    dev FAILED (kernel oopsed)
    [  222.555784] BUG: unable to handle kernel NULL pointer dereference at 
  (null)
    [  222.564547] IP: [] memset+0x9/0xb0
    [  222.570101] PGD 8004586b1067 PUD 45784a067 PMD 0
    [  222.575767] Oops: 0002 [#1] SMP
    [  222.579385] Modules linked in: macvlan(+) dccp_ipv4 dccp ghash_generic 
salsa20_generic salsa20_x86_64 camellia_generic camellia_aesni_avx2 
camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 cast6_generic 
cast_common serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic 
twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 
twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 
algif_hash af_alg ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt 
x86_pkg_temp_thermal coretemp kvm_intel kvm joydev lpc_ich shpchp mac_hid 
hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel igb 
aesni_intel aes_x86_64 i915_bdw dca lrw gf128mul ahci intel_ips glue_helper ptp 
ablk_helper drm_kms_helper cryptd pps_core libahci i2c_algo_bit drm video
    [  222.647301] CPU: 0 PID: 23159 Comm: stress-ng-dev Not tainted 
3.13.0-160-generic #210-Ubuntu
    [  222.647301] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS 
S1200RP.86B.03.02.0003.070120151022 07/01/2015
    [  222.647302] task: 880035bf1800 ti: 880453b6 task.ti: 
880453b6
    [  222.647303] RIP: 0010:[]  [] 
memset+0x9/0xb0
    [  222.647306] RSP: 0018:880453b61db8  EFLAGS: 00010246
    [  222.647306] RAX: 88045af55d00 RBX: 880455538000 RCX: 
0004
    [  222.647307] RDX: 0004 RSI:  RDI: 

    [  222.647307] RBP: 880453b61ec0 R08: 81c43740 R09: 

    [  222.647308] R10: a002f260 R11: 880453b61e10 R12: 
880455f07a00
    [  222.647309] R13: 0004 R14:  R15: 
0030
    [  222.647310] FS:  7f64909ef700() GS:88047040() 
knlGS:
    [  222.647310] CS:  0010 DS:  ES:  CR0: 80050033
    [  222.647311] CR2:  CR3: 000458904000 CR4: 
00360770
    [  222.647312] DR0:  DR1:  DR2: 

    [  222.647312] DR3:  DR6: fffe0ff0 DR7: 
0400
    [  222.647313] Stack:
    [  222.647314]  a0010c05 88040001 a003ace4 
00410086
    [  222.647316]  880453b61e10 880453b61e10 a00185d0 
643054506240
    [  222.647317]  7f64909ebce0 88040004 a002f260 

    [  222.647317] Call Trace:
    [  222.647329]  [] ? drm_ioctl+0x4d5/0x630 [drm]
    [  222.647337]  [] ? drm_agp_info_ioctl+0x10/0x10 [drm]
    [  222.647341]  [] do_vfs_ioctl+0x2e3/0x4d0
    [  222.647343]  [] ? SYSC_newfstat+0x25/0x30
    [  222.647344]  [] SyS_ioctl+0x81/0xa0
    [  222.647347]  [] system_call_fastpath+0x26/0x2b
    [  222.647359] Code: 16 fe 66 44 89 1f 66 44 89 54 17 fe eb 0c 48 83 fa 01 
72 06 44 8a 1e 44 88 1f c3 90 90 90 90 90 90 90 49 89 f9 40 88 f0 48 89 d1  
aa 4c 89 c8 c3 0f 1f 84 00 00 00 00 00 0f 1f 84 00 00 00 00
    [  222.647360] RIP  [] memset+0x9/0xb0
    [  222.647361]  RSP 
    [  222.647361] CR2: 
    [  222.647363] ---[ end trace f74524d41bff5843 ]---
    [  222.678166] program stress-ng-dev is using a deprecated SCSI 

[Kernel-packages] [Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

2018-11-16 Thread Colin Ian King
** Changed in: stress-ng
   Status: New => Invalid

** Changed in: stress-ng
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  stress-ng triggering oomkiller running brk and stack stressors on all
  arches.

Status in Stress-ng:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Won't Fix

Bug description:
  During regression testing on a z/VM instance, I noticed call traces
  being dumped to dmesg that seem to be related to stress-ng.

  The stress-ng invocation we're using is:
  stress-ng --aggressive --verify --timeout $runtime \
   --metrics-brief --tz --times \
   --af-alg 0 --bsearch 0 --context 0 --cpu 0 \
   --crypt 0 --hsearch 0 --longjmp 0 --lsearch 
0 \
   --matrix 0 --qsort 0 --str 0 --stream 0 \
   --tsearch 0 --vecmath 0 --wcs 0

  as executed by the cpu_stress script from the cpu/cpu_stress_ng test
  in the certification suite.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Nov  3 11:12:04 2017
  HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  --- 
  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
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M 
BOOT_IMAGE=0
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  artful
  Uname: Linux 4.13.0-16-generic s390x
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  UserGroups: adm cdrom cpacfstats dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1729878/+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 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2018-11-14 Thread Colin Ian King
** Changed in: thermald (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+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 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

2018-11-14 Thread Colin Ian King
** Changed in: linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => (unassigned)

** No longer affects: linux (Ubuntu)

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

Title:
  zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

Status in OpenStack LXD Charm:
  New

Bug description:
  Test: tests/gate-basic-cosmic-rocky

  As part of the config, the lxd charm creates a pool device depending
  on the config.  The test config is:

  lxd_config = {
  'block-devices': '/dev/vdb',
  'ephemeral-unmount': '/mnt',
  'storage-type': 'zfs',
  'overwrite': True
  }

  The config drive is normally mounted on /mnt, and the lxd charm
  umounts it as part of the start up.  The /etc/fstab on the unit is:

  # cat /etc/fstab 
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  LABEL=UEFI  /boot/efi   vfatdefaults0 0
  /dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  /dev/vdcnoneswapsw,comment=cloudconfig  0   0

  
  However, even after umount-ing the /mnt off of /dev/vdb, the zpool create 
command still fails:

  # zpool create -f lxd /dev/vdb
  /dev/vdb is in use and contains a unknown filesystem.

  
  If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then 
rebooted, then the zpool create command succeeds:

  # zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxd   14.9G   106K  14.9G - 0% 0%  1.00x  ONLINE  -

  # zpool status lxd
pool: lxd
   state: ONLINE
scan: none requested
  config:

  NAMESTATE READ WRITE CKSUM
  lxd ONLINE   0 0 0
vdb   ONLINE   0 0 0

  errors: No known data errors

  Something odd is going on with cosmic (18.10) and the combination of
  lxd, zfs and the kernel

  lxd version: 3.6
  zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
  Linux: 4.18.0-10-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+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 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

2018-11-13 Thread Colin Ian King
After adding a lot of debug into the kernel I can see what is causing
the issue:


1.  /dev/vdb is being mounted onto /mnt by systemd:

Nov 13 11:26:06 devstack kernel: [  259.373361] mount: 1658 mount, parent 1 
systemd
Nov 13 11:26:06 devstack kernel: [  259.394961] mount: 1658 mount /dev/vdb
Nov 13 11:26:06 devstack kernel: [  259.412916] do_mount: 1658 mount dev: 
/dev/vdb opts: '(null)' dir: '/mnt'

2. snap-confine is mounting /tmp/snap.rootfs_2SnJZF//mnt onto /mnt:

Nov 13 11:26:07 devstack kernel: [  261.546874] mount: 1706 snap-confine /mnt
/inaccessible/dir opts: '(null)' dir: '/run/systemd/unit-root/root'
Nov 13 11:26:07 devstack kernel: [  261.554827] do_mount: 1706 snap-confine 
dev: /mnt opts: '(null)' dir: '/tmp/snap.rootfs_2SnJZF//mnt'

So unmounting /mnt still leaves /dev/vdb marked as in use because of the
snap-confine mount.  There is no kernel bug here, the kernel still sees
/dev/vdb as being, hence it's doing the correct thing in not allowing
zfs to mount on the in-use /tmp/snap.rootfs_2SnJZF//mnt mount.

Colin

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

Title:
  zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

Status in OpenStack LXD Charm:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Test: tests/gate-basic-cosmic-rocky

  As part of the config, the lxd charm creates a pool device depending
  on the config.  The test config is:

  lxd_config = {
  'block-devices': '/dev/vdb',
  'ephemeral-unmount': '/mnt',
  'storage-type': 'zfs',
  'overwrite': True
  }

  The config drive is normally mounted on /mnt, and the lxd charm
  umounts it as part of the start up.  The /etc/fstab on the unit is:

  # cat /etc/fstab 
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  LABEL=UEFI  /boot/efi   vfatdefaults0 0
  /dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  /dev/vdcnoneswapsw,comment=cloudconfig  0   0

  
  However, even after umount-ing the /mnt off of /dev/vdb, the zpool create 
command still fails:

  # zpool create -f lxd /dev/vdb
  /dev/vdb is in use and contains a unknown filesystem.

  
  If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then 
rebooted, then the zpool create command succeeds:

  # zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxd   14.9G   106K  14.9G - 0% 0%  1.00x  ONLINE  -

  # zpool status lxd
pool: lxd
   state: ONLINE
scan: none requested
  config:

  NAMESTATE READ WRITE CKSUM
  lxd ONLINE   0 0 0
vdb   ONLINE   0 0 0

  errors: No known data errors

  Something odd is going on with cosmic (18.10) and the combination of
  lxd, zfs and the kernel

  lxd version: 3.6
  zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
  Linux: 4.18.0-10-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+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 1697132] Re: CPU Cores Stalls/Lock

2018-11-09 Thread Colin Ian King
OK, lets mark that as fixed released

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

Title:
  CPU Cores Stalls/Lock

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  CPU Stalls or Locks up after a random period of time. Can not trace
  issue to high resources or heat. System will crash while sitting
  essentially idle. Sometimes system will crash after a few minutes some
  times it will take days. A large file transfer will usually force the
  crash though.

  I have been having similar issue since Ubuntu 14.04. I have upgrade to
  every version along the way to 17.04 with the same issue. I have
  replaced every piece of hardware except HDD. MB, Proc, power supply,
  memory, video card. With and without AMD micro code. This is a server
  so no GUI.

  I've tried upstream kernels but they don't support ZFS and I haven't
  had any luck shimming it in. Happy to try newer kernels if someone can
  provide one with ZFS support.

  
  Jun  9 18:54:57 TheSource kernel: [46465.931527] INFO: rcu_sched detected 
stalls on CPUs/tasks:
  Jun  9 18:54:57 TheSource kernel: [46465.931583]9-...: (12 GPs 
behind) idle=f03/1/0 softirq=261811/261811 fqs=6599
  Jun  9 18:54:57 TheSource kernel: [46465.931624](detected by 0, 
t=15002 jiffies, g=380049, c=380048, q=118270)
  Jun  9 18:54:57 TheSource kernel: [46465.931665] Task dump for CPU 9:
  Jun  9 18:54:57 TheSource kernel: [46465.931666] swapper/9   R  running 
task0 0  1 0x0008
  Jun  9 18:54:57 TheSource kernel: [46465.931670] Call Trace:
  Jun  9 18:54:57 TheSource kernel: [46465.931677]  ? 
cpuidle_enter_state+0x122/0x2c0
  Jun  9 18:54:57 TheSource kernel: [46465.931680]  ? 
cpuidle_enter_state+0x110/0x2c0
  Jun  9 18:54:57 TheSource kernel: [46465.931683]  ? cpuidle_enter+0x17/0x20
  Jun  9 18:54:57 TheSource kernel: [46465.931685]  ? call_cpuidle+0x23/0x40
  Jun  9 18:54:57 TheSource kernel: [46465.931688]  ? do_idle+0x189/0x200
  Jun  9 18:54:57 TheSource kernel: [46465.931690]  ? 
cpu_startup_entry+0x71/0x80
  Jun  9 18:54:57 TheSource kernel: [46465.931693]  ? 
start_secondary+0x154/0x190
  Jun  9 18:54:57 TheSource kernel: [46465.931696]  ? start_cpu+0x14/0x14

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Fri Jun  9 20:17:45 2017
  InstallationDate: Installed on 2017-06-03 (6 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=bba67c63-3cd9-4475-bf3a-a0890087330d ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Kernel-packages] [Bug 1667838] Re: zpool export mpu1pool cannot export 'mpu1pool': pool is busy

2018-11-09 Thread Colin Ian King
There has been no reply to this information request in comment #1, so I
am closing this bug. Please re-open it if it still an issue.

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

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

Title:
  zpool export mpu1pool  cannot export 'mpu1pool': pool is busy

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

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  Linux 4.4.0-64-generic

  $ apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu15

  # modinfo zfs |head
  filename:   /lib/modules/4.4.0-64-generic/kernel/zfs/zfs/zfs.ko
  version:0.6.5.6-0ubuntu15

  
  I was not able to unmount a ZFS pool:

  # zpool export mpu1pool 
  cannot export 'mpu1pool': pool is busy

  The filesystems were unmounted and there was nothing that would be blocking 
them FS.
  Neither sync, echo 3 > /proc/sys/vm/drop_caches helped.

  The only way worked to export a ZFS pool was to turn off the SWAP:

  # lsof -Pn |grep -i mpu1
  lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
  # free -mh
totalusedfree  shared  buff/cache   
available
  Mem:   7.7G5.1G502M837M2.1G
1.0G
  Swap:  8.0G428M7.6G

  # swapoff -a 
  # free -mh
totalusedfree  shared  buff/cache   
available
  Mem:   7.7G1.5G4.8G366M1.4G
5.2G
  Swap:0B  0B  0B

  # zpool export mpu1pool 
  # echo $?
  0
  # swapon -a

  
  It is not obvious that the SWAP has to be freed before one can export ZFS 
pool.
  Would it be possible to improve this situation?

  
  Kind regards,
  Andrey Arapov

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+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 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

2018-11-08 Thread Colin Ian King
Hi Alex,

Is it possible to get the necessary commands to allow me to create the
instances so I can do some experimental changes? I'm wrestling with
getting a sane debugging environment with the instance you provided.

Colin

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

Title:
  zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

Status in OpenStack LXD Charm:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Test: tests/gate-basic-cosmic-rocky

  As part of the config, the lxd charm creates a pool device depending
  on the config.  The test config is:

  lxd_config = {
  'block-devices': '/dev/vdb',
  'ephemeral-unmount': '/mnt',
  'storage-type': 'zfs',
  'overwrite': True
  }

  The config drive is normally mounted on /mnt, and the lxd charm
  umounts it as part of the start up.  The /etc/fstab on the unit is:

  # cat /etc/fstab 
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  LABEL=UEFI  /boot/efi   vfatdefaults0 0
  /dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  /dev/vdcnoneswapsw,comment=cloudconfig  0   0

  
  However, even after umount-ing the /mnt off of /dev/vdb, the zpool create 
command still fails:

  # zpool create -f lxd /dev/vdb
  /dev/vdb is in use and contains a unknown filesystem.

  
  If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then 
rebooted, then the zpool create command succeeds:

  # zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxd   14.9G   106K  14.9G - 0% 0%  1.00x  ONLINE  -

  # zpool status lxd
pool: lxd
   state: ONLINE
scan: none requested
  config:

  NAMESTATE READ WRITE CKSUM
  lxd ONLINE   0 0 0
vdb   ONLINE   0 0 0

  errors: No known data errors

  Something odd is going on with cosmic (18.10) and the combination of
  lxd, zfs and the kernel

  lxd version: 3.6
  zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
  Linux: 4.18.0-10-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+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 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

2018-11-08 Thread Colin Ian King
Is the above commit a fix to this issue?

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

Title:
  zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

Status in OpenStack LXD Charm:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Test: tests/gate-basic-cosmic-rocky

  As part of the config, the lxd charm creates a pool device depending
  on the config.  The test config is:

  lxd_config = {
  'block-devices': '/dev/vdb',
  'ephemeral-unmount': '/mnt',
  'storage-type': 'zfs',
  'overwrite': True
  }

  The config drive is normally mounted on /mnt, and the lxd charm
  umounts it as part of the start up.  The /etc/fstab on the unit is:

  # cat /etc/fstab 
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  LABEL=UEFI  /boot/efi   vfatdefaults0 0
  /dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  /dev/vdcnoneswapsw,comment=cloudconfig  0   0

  
  However, even after umount-ing the /mnt off of /dev/vdb, the zpool create 
command still fails:

  # zpool create -f lxd /dev/vdb
  /dev/vdb is in use and contains a unknown filesystem.

  
  If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then 
rebooted, then the zpool create command succeeds:

  # zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxd   14.9G   106K  14.9G - 0% 0%  1.00x  ONLINE  -

  # zpool status lxd
pool: lxd
   state: ONLINE
scan: none requested
  config:

  NAMESTATE READ WRITE CKSUM
  lxd ONLINE   0 0 0
vdb   ONLINE   0 0 0

  errors: No known data errors

  Something odd is going on with cosmic (18.10) and the combination of
  lxd, zfs and the kernel

  lxd version: 3.6
  zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
  Linux: 4.18.0-10-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+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 1797546] Re: dev test in ubuntu_stress_smoke_test cause kernel oops on T-3.13

2018-11-08 Thread Colin Ian King
** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: ubuntu-kernel-tests
 Assignee: Colin Ian King (colin-king) => (unassigned)

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

Title:
  dev test in ubuntu_stress_smoke_test cause kernel oops on T-3.13

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  SRU Request [Trusty]

  == Justification ==

  It is possible to cause an oops in drm with an unimplemented ioctl call
  with the following reproducer run as root:

  #include 
  #include 
  #include 
  #include 

  int main(void)
  {
  int ptnum, fd;

  fd = open("/dev/dri/card0", O_RDWR);
  return ioctl(fd, TIOCGPTN, );
  }

  == Fix ==

  A backport (minor wiggle) of upstream commit 1539fb9bd405
  ("drm: fix NULL pointer access by wrong ioctl").

  == Testing ==

  Run the reproducer above as root, it will trip the oops. With the fix
  this oops won't occur.

  == Regression Potential ==

  Minimal, this is an upstream fix to this exact issue and has been in
  the kernel since 3.16

  


  This is a bare-metal node running with 3.13.0-160 amd64 kernel.

  The dev test will cause kernel oops:
    dev STARTING
    dev RETURNED 0
    dev FAILED (kernel oopsed)
    [  222.555784] BUG: unable to handle kernel NULL pointer dereference at 
  (null)
    [  222.564547] IP: [] memset+0x9/0xb0
    [  222.570101] PGD 8004586b1067 PUD 45784a067 PMD 0
    [  222.575767] Oops: 0002 [#1] SMP
    [  222.579385] Modules linked in: macvlan(+) dccp_ipv4 dccp ghash_generic 
salsa20_generic salsa20_x86_64 camellia_generic camellia_aesni_avx2 
camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 cast6_generic 
cast_common serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic 
twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 
twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 
algif_hash af_alg ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt 
x86_pkg_temp_thermal coretemp kvm_intel kvm joydev lpc_ich shpchp mac_hid 
hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel igb 
aesni_intel aes_x86_64 i915_bdw dca lrw gf128mul ahci intel_ips glue_helper ptp 
ablk_helper drm_kms_helper cryptd pps_core libahci i2c_algo_bit drm video
    [  222.647301] CPU: 0 PID: 23159 Comm: stress-ng-dev Not tainted 
3.13.0-160-generic #210-Ubuntu
    [  222.647301] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS 
S1200RP.86B.03.02.0003.070120151022 07/01/2015
    [  222.647302] task: 880035bf1800 ti: 880453b6 task.ti: 
880453b6
    [  222.647303] RIP: 0010:[]  [] 
memset+0x9/0xb0
    [  222.647306] RSP: 0018:880453b61db8  EFLAGS: 00010246
    [  222.647306] RAX: 88045af55d00 RBX: 880455538000 RCX: 
0004
    [  222.647307] RDX: 0004 RSI:  RDI: 

    [  222.647307] RBP: 880453b61ec0 R08: 81c43740 R09: 

    [  222.647308] R10: a002f260 R11: 880453b61e10 R12: 
880455f07a00
    [  222.647309] R13: 0004 R14:  R15: 
0030
    [  222.647310] FS:  7f64909ef700() GS:88047040() 
knlGS:
    [  222.647310] CS:  0010 DS:  ES:  CR0: 80050033
    [  222.647311] CR2:  CR3: 000458904000 CR4: 
00360770
    [  222.647312] DR0:  DR1:  DR2: 

    [  222.647312] DR3:  DR6: fffe0ff0 DR7: 
0400
    [  222.647313] Stack:
    [  222.647314]  a0010c05 88040001 a003ace4 
00410086
    [  222.647316]  880453b61e10 880453b61e10 a00185d0 
643054506240
    [  222.647317]  7f64909ebce0 88040004 a002f260 

    [  222.647317] Call Trace:
    [  222.647329]  [] ? drm_ioctl+0x4d5/0x630 [drm]
    [  222.647337]  [] ? drm_agp_info_ioctl+0x10/0x10 [drm]
    [  222.647341]  [] do_vfs_ioctl+0x2e3/0x4d0
    [  222.647343]  [] ? SYSC_newfstat+0x25/0x30
    [  222.647344]  [] SyS_ioctl+0x81/0xa0
    [  222.647347]  [] system_call_fastpath+0x26/0x2b
    [  222.647359] Code: 16 fe 66 44 89 1f 66 44 89 54 17 fe eb 0c 48 83 fa 01 
72 06 44 8a 1e 44 88 1f c3 90 90 90 90 90 90 90 49 89 f9 40 88 f0 48 89 d1  
aa 4c 89 c8 c3 0f 1f 84 00 00 00 00 00 0f 1f 84 00 00 00 00
    [  222.647360] RIP  [] memset+

[Kernel-packages] [Bug 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

2018-11-07 Thread Colin Ian King
I added debug into the kernel and observed /dev/vdb is being mounted by
systemd:

[9.859895] mount: 1624 mount, parent 1 systemd
[9.866398] mount: 1624 mount /dev/vdb

and also snap-confine is mounting mount too:

[9.966827] mount: 1663 snap-confine /mnt

Curiously, I've not seen any associated umounts.

I wonder if the namespace/confinement is causing the issue of not being
able to see the mount. I need to debug this further.

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

Title:
  zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

Status in OpenStack LXD Charm:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Test: tests/gate-basic-cosmic-rocky

  As part of the config, the lxd charm creates a pool device depending
  on the config.  The test config is:

  lxd_config = {
  'block-devices': '/dev/vdb',
  'ephemeral-unmount': '/mnt',
  'storage-type': 'zfs',
  'overwrite': True
  }

  The config drive is normally mounted on /mnt, and the lxd charm
  umounts it as part of the start up.  The /etc/fstab on the unit is:

  # cat /etc/fstab 
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  LABEL=UEFI  /boot/efi   vfatdefaults0 0
  /dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  /dev/vdcnoneswapsw,comment=cloudconfig  0   0

  
  However, even after umount-ing the /mnt off of /dev/vdb, the zpool create 
command still fails:

  # zpool create -f lxd /dev/vdb
  /dev/vdb is in use and contains a unknown filesystem.

  
  If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then 
rebooted, then the zpool create command succeeds:

  # zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxd   14.9G   106K  14.9G - 0% 0%  1.00x  ONLINE  -

  # zpool status lxd
pool: lxd
   state: ONLINE
scan: none requested
  config:

  NAMESTATE READ WRITE CKSUM
  lxd ONLINE   0 0 0
vdb   ONLINE   0 0 0

  errors: No known data errors

  Something odd is going on with cosmic (18.10) and the combination of
  lxd, zfs and the kernel

  lxd version: 3.6
  zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
  Linux: 4.18.0-10-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+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 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

2018-11-07 Thread Colin Ian King
Some notes:

1. /dev/vdb did appear to have an ext4 file system on it before we created the 
file system.
2. [jbd2/vdb-8] running implies the file system was mounted at some point on 
/dev/vdb
3. Nothing seemed to have mounted /dev/vdb

The file system was indeed mounted during boot:

[   94.945578] EXT4-fs (vdb): mounted filesystem with ordered data mode.
Opts: (null)

After a reboot the [jbd2/vdb-8] thread is no longer running and zfs can
create the file systems w/o any issues.

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

Title:
  zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

Status in OpenStack LXD Charm:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Test: tests/gate-basic-cosmic-rocky

  As part of the config, the lxd charm creates a pool device depending
  on the config.  The test config is:

  lxd_config = {
  'block-devices': '/dev/vdb',
  'ephemeral-unmount': '/mnt',
  'storage-type': 'zfs',
  'overwrite': True
  }

  The config drive is normally mounted on /mnt, and the lxd charm
  umounts it as part of the start up.  The /etc/fstab on the unit is:

  # cat /etc/fstab 
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  LABEL=UEFI  /boot/efi   vfatdefaults0 0
  /dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  /dev/vdcnoneswapsw,comment=cloudconfig  0   0

  
  However, even after umount-ing the /mnt off of /dev/vdb, the zpool create 
command still fails:

  # zpool create -f lxd /dev/vdb
  /dev/vdb is in use and contains a unknown filesystem.

  
  If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then 
rebooted, then the zpool create command succeeds:

  # zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxd   14.9G   106K  14.9G - 0% 0%  1.00x  ONLINE  -

  # zpool status lxd
pool: lxd
   state: ONLINE
scan: none requested
  config:

  NAMESTATE READ WRITE CKSUM
  lxd ONLINE   0 0 0
vdb   ONLINE   0 0 0

  errors: No known data errors

  Something odd is going on with cosmic (18.10) and the combination of
  lxd, zfs and the kernel

  lxd version: 3.6
  zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
  Linux: 4.18.0-10-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+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 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

2018-11-07 Thread Colin Ian King
This is not a zfs related bug per se, it's more of a kernel related, so
I'm re-assigned the bug

** Package changed: zfs-linux (Ubuntu) => linux (Ubuntu)

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

Title:
  zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

Status in OpenStack LXD Charm:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Test: tests/gate-basic-cosmic-rocky

  As part of the config, the lxd charm creates a pool device depending
  on the config.  The test config is:

  lxd_config = {
  'block-devices': '/dev/vdb',
  'ephemeral-unmount': '/mnt',
  'storage-type': 'zfs',
  'overwrite': True
  }

  The config drive is normally mounted on /mnt, and the lxd charm
  umounts it as part of the start up.  The /etc/fstab on the unit is:

  # cat /etc/fstab 
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  LABEL=UEFI  /boot/efi   vfatdefaults0 0
  /dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  /dev/vdcnoneswapsw,comment=cloudconfig  0   0

  
  However, even after umount-ing the /mnt off of /dev/vdb, the zpool create 
command still fails:

  # zpool create -f lxd /dev/vdb
  /dev/vdb is in use and contains a unknown filesystem.

  
  If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then 
rebooted, then the zpool create command succeeds:

  # zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxd   14.9G   106K  14.9G - 0% 0%  1.00x  ONLINE  -

  # zpool status lxd
pool: lxd
   state: ONLINE
scan: none requested
  config:

  NAMESTATE READ WRITE CKSUM
  lxd ONLINE   0 0 0
vdb   ONLINE   0 0 0

  errors: No known data errors

  Something odd is going on with cosmic (18.10) and the combination of
  lxd, zfs and the kernel

  lxd version: 3.6
  zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
  Linux: 4.18.0-10-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+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 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

2018-11-07 Thread Colin Ian King
Can you supply me the commands required to reproduce this issue, I'm not
familiar with the test environment you are using.

Thanks

** Changed in: charm-lxd
   Status: Incomplete => In Progress

** Changed in: charm-lxd
   Status: In Progress => New

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

** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: charm-lxd
 Assignee: Colin Ian King (colin-king) => (unassigned)

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

Title:
  zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

Status in OpenStack LXD Charm:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Test: tests/gate-basic-cosmic-rocky

  As part of the config, the lxd charm creates a pool device depending
  on the config.  The test config is:

  lxd_config = {
  'block-devices': '/dev/vdb',
  'ephemeral-unmount': '/mnt',
  'storage-type': 'zfs',
  'overwrite': True
  }

  The config drive is normally mounted on /mnt, and the lxd charm
  umounts it as part of the start up.  The /etc/fstab on the unit is:

  # cat /etc/fstab 
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  LABEL=UEFI  /boot/efi   vfatdefaults0 0
  /dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  /dev/vdcnoneswapsw,comment=cloudconfig  0   0

  
  However, even after umount-ing the /mnt off of /dev/vdb, the zpool create 
command still fails:

  # zpool create -f lxd /dev/vdb
  /dev/vdb is in use and contains a unknown filesystem.

  
  If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then 
rebooted, then the zpool create command succeeds:

  # zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxd   14.9G   106K  14.9G - 0% 0%  1.00x  ONLINE  -

  # zpool status lxd
pool: lxd
   state: ONLINE
scan: none requested
  config:

  NAMESTATE READ WRITE CKSUM
  lxd ONLINE   0 0 0
vdb   ONLINE   0 0 0

  errors: No known data errors

  Something odd is going on with cosmic (18.10) and the combination of
  lxd, zfs and the kernel

  lxd version: 3.6
  zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
  Linux: 4.18.0-10-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+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 1801856] Re: seccomp in ubuntu_stress_smoke_test failed on ARM64/Power8 Trusty

2018-11-07 Thread Colin Ian King
The arches don't have HAVE_ARCH_SECCOMP_FILTER enabled as this has not
been implemented, so seccomp filtering does not exist. I'll fix stress-
ng to handle this corner case without an error.

** Changed in: stress-ng
   Status: New => In Progress

** Changed in: stress-ng
   Importance: Undecided => High

** Changed in: stress-ng
 Assignee: (unassigned) => Colin Ian King (colin-king)

** No longer affects: linux (Ubuntu)

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

Title:
  seccomp in ubuntu_stress_smoke_test failed on ARM64/Power8 Trusty

Status in Stress-ng:
  In Progress
Status in ubuntu-kernel-tests:
  Confirmed

Bug description:
  Didn't see this on amd64 / i386, but it can be reproduced on power8
  and ARM64

seccomp STARTING
seccomp RETURNED 2
seccomp FAILED
stress-ng: debug: [7528] 8 processors online, 8 processors configured
stress-ng: info:  [7528] dispatching hogs: 4 seccomp
stress-ng: debug: [7528] /sys/devices/system/cpu/cpu0/cache does not exist
stress-ng: info:  [7528] cache allocate: using built-in defaults as unable 
to determine cache details
stress-ng: debug: [7528] cache allocate: default cache size: 2048K
stress-ng: debug: [7528] starting stressors
stress-ng: debug: [7529] stress-ng-seccomp: started [7529] (instance 0)
stress-ng: debug: [7528] 4 stressors spawned
stress-ng: debug: [7530] stress-ng-seccomp: started [7530] (instance 1)
stress-ng: fail:  [7533] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: fail:  [7534] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: debug: [7531] stress-ng-seccomp: started [7531] (instance 2)
stress-ng: fail:  [7530] stress-ng-seccomp: aborting because of unexpected 
failure in child process
stress-ng: debug: [7530] stress-ng-seccomp: exited [7530] (instance 1)
stress-ng: fail:  [7529] stress-ng-seccomp: aborting because of unexpected 
failure in child process
stress-ng: debug: [7529] stress-ng-seccomp: exited [7529] (instance 0)
stress-ng: debug: [7532] stress-ng-seccomp: started [7532] (instance 3)
stress-ng: error: [7528] process 7529 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7529] terminated
stress-ng: error: [7528] process 7530 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7530] terminated
stress-ng: fail:  [7535] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: fail:  [7536] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: fail:  [7532] stress-ng-seccomp: aborting because of unexpected 
failure in child process
stress-ng: debug: [7531] stress-ng-seccomp: exited [7531] (instance 2)
stress-ng: error: [7528] process 7531 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7531] terminated
stress-ng: error: [7528] process 7532 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7532] terminated
stress-ng: info:  [7528] unsuccessful run completed in 0.00s

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-161-generic 3.13.0-161.211
  ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-161-generic aarch64
  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.14.1-0ubuntu3.29
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg:
   
  Date: Tue Nov  6 06:23:27 2018
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   enp1s0d1  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-161-generic N/A
   linux-backports-modules-3.13.0-161-generic  N/A
   linux-firmware  1.127.24
  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/stress-ng/+bug/1801856/+subscriptions

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

[Kernel-packages] [Bug 1801856] Re: seccomp in ubuntu_stress_smoke_test failed on ARM64/Power8 Trusty

2018-11-07 Thread Colin Ian King
CONFIG_SECCOMP_FILTER does not appear to be configured for the ARM64
system, I presume this is the same for the Power8 box too.

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

Title:
  seccomp in ubuntu_stress_smoke_test failed on ARM64/Power8 Trusty

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

Bug description:
  Didn't see this on amd64 / i386, but it can be reproduced on power8
  and ARM64

seccomp STARTING
seccomp RETURNED 2
seccomp FAILED
stress-ng: debug: [7528] 8 processors online, 8 processors configured
stress-ng: info:  [7528] dispatching hogs: 4 seccomp
stress-ng: debug: [7528] /sys/devices/system/cpu/cpu0/cache does not exist
stress-ng: info:  [7528] cache allocate: using built-in defaults as unable 
to determine cache details
stress-ng: debug: [7528] cache allocate: default cache size: 2048K
stress-ng: debug: [7528] starting stressors
stress-ng: debug: [7529] stress-ng-seccomp: started [7529] (instance 0)
stress-ng: debug: [7528] 4 stressors spawned
stress-ng: debug: [7530] stress-ng-seccomp: started [7530] (instance 1)
stress-ng: fail:  [7533] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: fail:  [7534] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: debug: [7531] stress-ng-seccomp: started [7531] (instance 2)
stress-ng: fail:  [7530] stress-ng-seccomp: aborting because of unexpected 
failure in child process
stress-ng: debug: [7530] stress-ng-seccomp: exited [7530] (instance 1)
stress-ng: fail:  [7529] stress-ng-seccomp: aborting because of unexpected 
failure in child process
stress-ng: debug: [7529] stress-ng-seccomp: exited [7529] (instance 0)
stress-ng: debug: [7532] stress-ng-seccomp: started [7532] (instance 3)
stress-ng: error: [7528] process 7529 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7529] terminated
stress-ng: error: [7528] process 7530 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7530] terminated
stress-ng: fail:  [7535] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: fail:  [7536] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: fail:  [7532] stress-ng-seccomp: aborting because of unexpected 
failure in child process
stress-ng: debug: [7531] stress-ng-seccomp: exited [7531] (instance 2)
stress-ng: error: [7528] process 7531 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7531] terminated
stress-ng: error: [7528] process 7532 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7532] terminated
stress-ng: info:  [7528] unsuccessful run completed in 0.00s

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-161-generic 3.13.0-161.211
  ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-161-generic aarch64
  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.14.1-0ubuntu3.29
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg:
   
  Date: Tue Nov  6 06:23:27 2018
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   enp1s0d1  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-161-generic N/A
   linux-backports-modules-3.13.0-161-generic  N/A
   linux-firmware  1.127.24
  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/stress-ng/+bug/1801856/+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 1801865] Re: af-alg in ubuntu_stress_smoke_test failed with Trusty Power8

2018-11-06 Thread Colin Ian King
ENOMEM is not a critical failure, adding a skip on the test if sendmsg
fails.

Commit pushed:

http://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=55375dcae101a995dc1d932acd90b86f1ea7b4a7

** Changed in: stress-ng
   Importance: Undecided => High

** Changed in: stress-ng
   Status: New => In Progress

** Changed in: stress-ng
 Assignee: (unassigned) => Colin Ian King (colin-king)

** No longer affects: linux (Ubuntu)

** Changed in: stress-ng
   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/1801865

Title:
  af-alg in ubuntu_stress_smoke_test failed with Trusty Power8

Status in Stress-ng:
  Fix Committed
Status in ubuntu-kernel-tests:
  New

Bug description:
  The af-alg test failed with Trusty 3.13.0-161-generic Power8,
  reproduce rate 5/5

  06:48:39 DEBUG| [stdout] af-alg STARTING
  06:48:39 DEBUG| [stdout] af-alg RETURNED 2
  06:48:39 DEBUG| [stdout] af-alg FAILED
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] 128 processors online, 128 
processors configured
  06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] dispatching hogs: 4 af-alg
  06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] cache allocate: using 
built-in defaults as unable to determine cache details
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] cache allocate: default 
cache size: 2048K
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] starting stressors
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] 4 stressors spawned
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19625] stress-ng-af-alg: started 
[19625] (instance 0)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19626] stress-ng-af-alg: started 
[19626] (instance 1)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19627] stress-ng-af-alg: started 
[19627] (instance 2)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19628] stress-ng-af-alg: started 
[19628] (instance 3)
  06:48:39 DEBUG| [stdout] stress-ng: fail:  [19628] stress-ng-af-alg: sendmsg 
using cbc(aes) failed: errno=12 (Cannot allocate memory)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19626] stress-ng-af-alg: exited 
[19626] (instance 1)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19628] stress-ng-af-alg: exited 
[19628] (instance 3)
  06:48:39 DEBUG| [stdout] stress-ng: fail:  [19627] stress-ng-af-alg: sendmsg 
using cbc(aes) failed: errno=12 (Cannot allocate memory)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19625] stress-ng-af-alg: exited 
[19625] (instance 0)
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19625 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19625] terminated
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19626 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19626] terminated
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19627 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19627] terminated
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19628 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19628] terminated
  06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] unsuccessful run completed 
in 0.08s
  06:48:39 DEBUG| [stdout]

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1801865/+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 1801347] Re: ubuntu_vfat_stress will pass even with error reported by stress-ng

2018-11-02 Thread Colin Ian King
Fix committed: http://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=7358ec3b7ffc243168f22da482377c16902320f0

** No longer affects: stress-ng

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

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

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  ubuntu_vfat_stress will pass even with error reported by stress-ng

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

Bug description:
  The test will pass even with stress-ng complaining about "No space
  left on device", not sure if this is an expected behaviour, but it
  might be confusing to testers.

   stress-ng: info:  [36588] dispatching hogs: 2 hdd, 2 lockf, 2 seek, 2 aio, 2 
dentry, 2 dir, 2 fallocate, 2 fstat, 2 lease, 2 open, 2 rename, 2 chdir, 2 
rename
   stress-ng: fail:  [36609] stress-ng-chdir: mkdir failed, errno=28 (No space 
left on device)
   stress-ng: fail:  [36623] stress-ng-chdir: mkdir failed, errno=28 (No space 
left on device)
   stress-ng: fail:  [36611] stress-ng-hdd: read failed, errno=28 (No space 
left on device)
   stress-ng: error: [36588] process 36611 (stress-ng-hdd) terminated with an 
error, exit status=1 (stress-ng core failure)
   stress-ng: error: [36588] process [36609] (stress-ng-chdir) aborted early, 
out of system resources
   stress-ng: error: [36588] process [36623] (stress-ng-chdir) aborted early, 
out of system resources
   stress-ng: info:  [36588] unsuccessful run completed in 14.35s
   stress-ng: info:  [36588] stressor   bogo ops real time  usr time  sys 
time   bogo ops/s   bogo ops/s
   stress-ng: info:  [36588]   (secs)(secs)
(secs)   (real time) (usr+sys time)
   stress-ng: info:  [36588] hdd   16391  7.39  0.44  
6.44  2218.21  2382.41
   stress-ng: info:  [36588] lockf131604 10.16  0.05 
12.43 12947.00 10545.19
   stress-ng: info:  [36588] seek1987284 10.17  1.33 
10.40195448.06169418.93
   stress-ng: info:  [36588] aio2496 10.15  0.00  
0.00   245.83 0.00
   stress-ng: info:  [36588] dentry  171 10.42  0.00  
0.6116.41   280.33
   stress-ng: info:  [36588] dir2539 14.09  0.00 
15.40   180.14   164.87
   stress-ng: info:  [36588] fallocate   170 10.17  0.04  
5.3516.7131.54
   stress-ng: info:  [36588] fstat  2147 10.00  0.02  
0.26   214.64  7667.86
   stress-ng: info:  [36588] lease66 10.14  0.61  
5.15 6.5111.46
   stress-ng: info:  [36588] open1434208 10.11  0.44 
12.20141807.28113465.82
   stress-ng: info:  [36588] rename 6526 10.01  0.00  
2.94   651.86  2219.73
   stress-ng: info:  [36588] rename 6820 10.00  0.00  
2.49   681.85  2738.96
   stress-ng: info:  [36588] for a 14.35s run time:
   stress-ng: info:  [36588] 114.80s available CPU time
   stress-ng: info:  [36588]   3.05s user time   (  2.66%)
   stress-ng: info:  [36588]  75.50s system time ( 65.77%)
   stress-ng: info:  [36588]  78.55s total time  ( 68.43%)
   stress-ng: info:  [36588] load average: 17.49 10.98 4.90
   Stress-ng stressor failed, error: 2
   umounting vfat /mnt/vfat-test-29590
   umounting tmpfs /mnt/vfat-test-29590
   


   Completed

   Kernel issues: NONE

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-139-generic 4.4.0-139.165
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-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: Fri Nov  2 08:20:40 2018
  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'
  ProcKe

[Kernel-packages] [Bug 1801347] Re: ubuntu_vfat_stress will pass even with error reported by stress-ng

2018-11-02 Thread Colin Ian King
This is intentional behavior as the test is seeing how to deal with file
operations when a block device is full.

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

Title:
  ubuntu_vfat_stress will pass even with error reported by stress-ng

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

Bug description:
  The test will pass even with stress-ng complaining about "No space
  left on device", not sure if this is an expected behaviour, but it
  might be confusing to testers.

   stress-ng: info:  [36588] dispatching hogs: 2 hdd, 2 lockf, 2 seek, 2 aio, 2 
dentry, 2 dir, 2 fallocate, 2 fstat, 2 lease, 2 open, 2 rename, 2 chdir, 2 
rename
   stress-ng: fail:  [36609] stress-ng-chdir: mkdir failed, errno=28 (No space 
left on device)
   stress-ng: fail:  [36623] stress-ng-chdir: mkdir failed, errno=28 (No space 
left on device)
   stress-ng: fail:  [36611] stress-ng-hdd: read failed, errno=28 (No space 
left on device)
   stress-ng: error: [36588] process 36611 (stress-ng-hdd) terminated with an 
error, exit status=1 (stress-ng core failure)
   stress-ng: error: [36588] process [36609] (stress-ng-chdir) aborted early, 
out of system resources
   stress-ng: error: [36588] process [36623] (stress-ng-chdir) aborted early, 
out of system resources
   stress-ng: info:  [36588] unsuccessful run completed in 14.35s
   stress-ng: info:  [36588] stressor   bogo ops real time  usr time  sys 
time   bogo ops/s   bogo ops/s
   stress-ng: info:  [36588]   (secs)(secs)
(secs)   (real time) (usr+sys time)
   stress-ng: info:  [36588] hdd   16391  7.39  0.44  
6.44  2218.21  2382.41
   stress-ng: info:  [36588] lockf131604 10.16  0.05 
12.43 12947.00 10545.19
   stress-ng: info:  [36588] seek1987284 10.17  1.33 
10.40195448.06169418.93
   stress-ng: info:  [36588] aio2496 10.15  0.00  
0.00   245.83 0.00
   stress-ng: info:  [36588] dentry  171 10.42  0.00  
0.6116.41   280.33
   stress-ng: info:  [36588] dir2539 14.09  0.00 
15.40   180.14   164.87
   stress-ng: info:  [36588] fallocate   170 10.17  0.04  
5.3516.7131.54
   stress-ng: info:  [36588] fstat  2147 10.00  0.02  
0.26   214.64  7667.86
   stress-ng: info:  [36588] lease66 10.14  0.61  
5.15 6.5111.46
   stress-ng: info:  [36588] open1434208 10.11  0.44 
12.20141807.28113465.82
   stress-ng: info:  [36588] rename 6526 10.01  0.00  
2.94   651.86  2219.73
   stress-ng: info:  [36588] rename 6820 10.00  0.00  
2.49   681.85  2738.96
   stress-ng: info:  [36588] for a 14.35s run time:
   stress-ng: info:  [36588] 114.80s available CPU time
   stress-ng: info:  [36588]   3.05s user time   (  2.66%)
   stress-ng: info:  [36588]  75.50s system time ( 65.77%)
   stress-ng: info:  [36588]  78.55s total time  ( 68.43%)
   stress-ng: info:  [36588] load average: 17.49 10.98 4.90
   Stress-ng stressor failed, error: 2
   umounting vfat /mnt/vfat-test-29590
   umounting tmpfs /mnt/vfat-test-29590
   


   Completed

   Kernel issues: NONE

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-139-generic 4.4.0-139.165
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-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: Fri Nov  2 08:20:40 2018
  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=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  

[Kernel-packages] [Bug 1800609] Re: dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR

2018-10-30 Thread Colin Ian King
** No longer affects: linux (Ubuntu)

** Summary changed:

- dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR
+ dev test in ubuntu_stress_smoke_tests throws usercopy warning s390x Ubuntu on 
LPAR

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

Title:
  dev test in ubuntu_stress_smoke_tests throws usercopy warning s390x
  Ubuntu on LPAR

Status in Stress-ng:
  Fix Committed
Status in ubuntu-kernel-tests:
  New

Bug description:
  The dev test on a s390x node (Ubuntu on LPAR) will hang, kernel bug
  could be found in the syslog

  [54084.082277] [ cut here ]
  [54084.082279] kernel BUG at mm/usercopy.c:100!
  [54084.082294] illegal operation: 0001 ilc:1 [#256] SMP 
  [54084.082297] Modules linked in: vhost_net vhost tap cuse dccp_ipv4 dccp 
algif_rng salsa20_generic camellia_generic cast6_generic cast_common 
serpent_generic twofish_generic twofish_common lrw algif_skcipher tgr192 wp512 
rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg aufs ip6t_MASQUERADE 
ip6table_nat ip6table_filter ip6_tables xt_comment xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE iptable_nat xt_tcpudp bridge iptable_filter bpfilter openvswitch 
nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_defrag_ipv6 nf_conncount nf_nat nf_conntrack 8021q garp mrp stp llc 
binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) dm_service_time zcommon(PO) 
znvpair(PO) dm_multipath scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua 
ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390
  [54084.082354]  sha1_s390 sha_common genwqe_card crc_itu_t chsc_sch eadm_sch 
ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd 
ib_iser rdma_cm auth_rpcgss nfs_acl iw_cm lockd grace ib_cm iscsi_tcp 
libiscsi_tcp sunrpc libiscsi scsi_transport_iscsi ip_tables x_tables btrfs 
zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx4_en 
mlx4_ib qeth_l2 ib_core ptp pps_core crc32_vx_s390 mlx4_core devlink zfcp 
scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod
  [54084.082418] CPU: 3 PID: 217520 Comm: stress-ng-dev Tainted: P  DO  
4.18.0-11-generic #12-Ubuntu
  [54084.082420] Hardware name: IBM 2964 N63 400 (LPAR)
  [54084.082422] Krnl PSW : ed7ed85f 816ddc5c 
(usercopy_abort+0xb2/0xb8)
  [54084.082433]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 
RI:0 EA:3
  [54084.082436] Krnl GPRS: 0320 0006 0056 
0007
  [54084.082438]0007 7fe0 00a96d3a 

  [54084.082441]03ff 0006 0006 
0002acb4ee00
  [54084.082443]00a96d3a 00914430 00386606 
00038f087a78
  [54084.082449] Krnl Code: 003865fa: c02000390dc4  larl
%r2,aa8182
00386600: c0e5fff2b418  brasl   
%r14,1dce30
   #00386606: a7f40001  brc 
15,386608
   >0038660a: 0707  bcr 0,%r7
0038660c: 0707  bcr 0,%r7
0038660e: 0707  bcr 0,%r7
00386610: c004  brcl0,386610
00386616: ebcff0780024  stmg
%r12,%r15,120(%r15)
  [54084.082484] Call Trace:
  [54084.082487] ([<00386606>] usercopy_abort+0xae/0xb8)
  [54084.082489]  [<00386522>] __check_object_size+0x19a/0x1d0 
  [54084.082492]  [<005c69d8>] sg_scsi_ioctl+0x120/0x3d8 
  [54084.082495]  [<005c75b6>] scsi_cmd_ioctl+0x3ce/0x3d8 
  [54084.082497]  [<005c87d0>] bsg_ioctl+0x118/0x250 
  [54084.082499]  [<003a3c9c>] do_vfs_ioctl+0xac/0x650 
  [54084.082502]  [<003a42cc>] ksys_ioctl+0x8c/0xb8 
  [54084.082504]  [<003a432a>] sys_ioctl+0x32/0x40 
  [54084.082507]  [<008f0dc0>] system_call+0xdc/0x2c8 
  [54084.082508] Last Breaking-Event-Address:
  [54084.082510]  [<00386606>] usercopy_abort+0xae/0xb8
  [54084.082512]  
  [54084.082513] ---[ end trace 5009dd6293a23031 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: s390x
  

[Kernel-packages] [Bug 1800609] Re: dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR

2018-10-30 Thread Colin Ian King
Fix committed to stress-ng:

http://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=53e5a98cd58d3b146cf8ffe52540722ff410a5ad

FIBMAP on a block device is plainly wrong, it should only be applied to
a file. The FIBMAP ioctl to a scsi block device is the same as the
SCSI_IOCTL_SEND_COMMAND ioctl that requires a scsi_ioctl_command struct.
As it stands, we are passing an int with stack garbage as this struct
which is passing garbage to the ioctl. The deprecated SCSI ioctl creates
a scsi_request from the garbage and this causes the kernel to correctly
warn with a usercopy_abort that the structure is bogos. Fix this by not
calling FIBMAP on a raw SCSI device.


** Changed in: stress-ng
   Status: New => Fix Committed

** Changed in: stress-ng
   Importance: Undecided => High

** Changed in: stress-ng
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on
  LPAR

Status in Stress-ng:
  Fix Committed
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  The dev test on a s390x node (Ubuntu on LPAR) will hang, kernel bug
  could be found in the syslog

  [54084.082277] [ cut here ]
  [54084.082279] kernel BUG at mm/usercopy.c:100!
  [54084.082294] illegal operation: 0001 ilc:1 [#256] SMP 
  [54084.082297] Modules linked in: vhost_net vhost tap cuse dccp_ipv4 dccp 
algif_rng salsa20_generic camellia_generic cast6_generic cast_common 
serpent_generic twofish_generic twofish_common lrw algif_skcipher tgr192 wp512 
rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg aufs ip6t_MASQUERADE 
ip6table_nat ip6table_filter ip6_tables xt_comment xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE iptable_nat xt_tcpudp bridge iptable_filter bpfilter openvswitch 
nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_defrag_ipv6 nf_conncount nf_nat nf_conntrack 8021q garp mrp stp llc 
binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) dm_service_time zcommon(PO) 
znvpair(PO) dm_multipath scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua 
ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390
  [54084.082354]  sha1_s390 sha_common genwqe_card crc_itu_t chsc_sch eadm_sch 
ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd 
ib_iser rdma_cm auth_rpcgss nfs_acl iw_cm lockd grace ib_cm iscsi_tcp 
libiscsi_tcp sunrpc libiscsi scsi_transport_iscsi ip_tables x_tables btrfs 
zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx4_en 
mlx4_ib qeth_l2 ib_core ptp pps_core crc32_vx_s390 mlx4_core devlink zfcp 
scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod
  [54084.082418] CPU: 3 PID: 217520 Comm: stress-ng-dev Tainted: P  DO  
4.18.0-11-generic #12-Ubuntu
  [54084.082420] Hardware name: IBM 2964 N63 400 (LPAR)
  [54084.082422] Krnl PSW : ed7ed85f 816ddc5c 
(usercopy_abort+0xb2/0xb8)
  [54084.082433]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 
RI:0 EA:3
  [54084.082436] Krnl GPRS: 0320 0006 0056 
0007
  [54084.082438]0007 7fe0 00a96d3a 

  [54084.082441]03ff 0006 0006 
0002acb4ee00
  [54084.082443]00a96d3a 00914430 00386606 
00038f087a78
  [54084.082449] Krnl Code: 003865fa: c02000390dc4  larl
%r2,aa8182
00386600: c0e5fff2b418  brasl   
%r14,1dce30
   #00386606: a7f40001  brc 
15,386608
   >0038660a: 0707  bcr 0,%r7
0038660c: 0707  bcr 0,%r7
0038660e: 0707  bcr 0,%r7
00386610: c004  brcl0,386610
00386616: ebcff0780024  stmg
%r12,%r15,120(%r15)
  [54084.082484] Call Trace:
  [54084.082487] ([<00386606>] usercopy_abort+0xae/0xb8)
  [54084.082489]  [<00386522>] __check_object_size+0x19a/0x1d0 
  [54084.082492]  [<005c69d8>] sg_scsi_ioctl+0x120/0x3d8 
  [54084.082495]  [<005c75b6>] scsi_cmd_ioctl+0x3ce/0x3d8 
  [54084.082497]  [<005c87d0>] bsg_ioctl+0x118/0x250 
  [54084.082499]  [<003a3c9c>] do_vfs_ioctl+0xac/0x650 
  [54084.082502]  [<003a42cc>] ksys_ioctl+0x8c/0xb8 
  [54084.082504]  [<003a432a

[Kernel-packages] [Bug 1800609] Re: dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR

2018-10-30 Thread Colin Ian King
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on
  LPAR

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

Bug description:
  The dev test on a s390x node (Ubuntu on LPAR) will hang, kernel bug
  could be found in the syslog

  [54084.082277] [ cut here ]
  [54084.082279] kernel BUG at mm/usercopy.c:100!
  [54084.082294] illegal operation: 0001 ilc:1 [#256] SMP 
  [54084.082297] Modules linked in: vhost_net vhost tap cuse dccp_ipv4 dccp 
algif_rng salsa20_generic camellia_generic cast6_generic cast_common 
serpent_generic twofish_generic twofish_common lrw algif_skcipher tgr192 wp512 
rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg aufs ip6t_MASQUERADE 
ip6table_nat ip6table_filter ip6_tables xt_comment xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE iptable_nat xt_tcpudp bridge iptable_filter bpfilter openvswitch 
nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_defrag_ipv6 nf_conncount nf_nat nf_conntrack 8021q garp mrp stp llc 
binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) dm_service_time zcommon(PO) 
znvpair(PO) dm_multipath scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua 
ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390
  [54084.082354]  sha1_s390 sha_common genwqe_card crc_itu_t chsc_sch eadm_sch 
ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd 
ib_iser rdma_cm auth_rpcgss nfs_acl iw_cm lockd grace ib_cm iscsi_tcp 
libiscsi_tcp sunrpc libiscsi scsi_transport_iscsi ip_tables x_tables btrfs 
zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx4_en 
mlx4_ib qeth_l2 ib_core ptp pps_core crc32_vx_s390 mlx4_core devlink zfcp 
scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod
  [54084.082418] CPU: 3 PID: 217520 Comm: stress-ng-dev Tainted: P  DO  
4.18.0-11-generic #12-Ubuntu
  [54084.082420] Hardware name: IBM 2964 N63 400 (LPAR)
  [54084.082422] Krnl PSW : ed7ed85f 816ddc5c 
(usercopy_abort+0xb2/0xb8)
  [54084.082433]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 
RI:0 EA:3
  [54084.082436] Krnl GPRS: 0320 0006 0056 
0007
  [54084.082438]0007 7fe0 00a96d3a 

  [54084.082441]03ff 0006 0006 
0002acb4ee00
  [54084.082443]00a96d3a 00914430 00386606 
00038f087a78
  [54084.082449] Krnl Code: 003865fa: c02000390dc4  larl
%r2,aa8182
00386600: c0e5fff2b418  brasl   
%r14,1dce30
   #00386606: a7f40001  brc 
15,386608
   >0038660a: 0707  bcr 0,%r7
0038660c: 0707  bcr 0,%r7
0038660e: 0707  bcr 0,%r7
00386610: c004  brcl0,386610
00386616: ebcff0780024  stmg
%r12,%r15,120(%r15)
  [54084.082484] Call Trace:
  [54084.082487] ([<00386606>] usercopy_abort+0xae/0xb8)
  [54084.082489]  [<00386522>] __check_object_size+0x19a/0x1d0 
  [54084.082492]  [<005c69d8>] sg_scsi_ioctl+0x120/0x3d8 
  [54084.082495]  [<005c75b6>] scsi_cmd_ioctl+0x3ce/0x3d8 
  [54084.082497]  [<005c87d0>] bsg_ioctl+0x118/0x250 
  [54084.082499]  [<003a3c9c>] do_vfs_ioctl+0xac/0x650 
  [54084.082502]  [<003a42cc>] ksys_ioctl+0x8c/0xb8 
  [54084.082504]  [<003a432a>] sys_ioctl+0x32/0x40 
  [54084.082507]  [<008f0dc0>] system_call+0xdc/0x2c8 
  [54084.082508] Last Breaking-Event-Address:
  [54084.082510]  [<00386606>] usercopy_abort+0xae/0xb8
  [54084.082512]  
  [54084.082513] ---[ end trace 5009dd6293a23031 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No suc

[Kernel-packages] [Bug 1800609] Re: dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on LPAR

2018-10-30 Thread Colin Ian King
Occurs when performing the FIBMAP ioctl on /dev/bsg/rport-1:0-0

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

Title:
  dev test in ubuntu_stress_smoke_tests will hang on s390x Ubuntu on
  LPAR

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

Bug description:
  The dev test on a s390x node (Ubuntu on LPAR) will hang, kernel bug
  could be found in the syslog

  [54084.082277] [ cut here ]
  [54084.082279] kernel BUG at mm/usercopy.c:100!
  [54084.082294] illegal operation: 0001 ilc:1 [#256] SMP 
  [54084.082297] Modules linked in: vhost_net vhost tap cuse dccp_ipv4 dccp 
algif_rng salsa20_generic camellia_generic cast6_generic cast_common 
serpent_generic twofish_generic twofish_common lrw algif_skcipher tgr192 wp512 
rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg aufs ip6t_MASQUERADE 
ip6table_nat ip6table_filter ip6_tables xt_comment xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE iptable_nat xt_tcpudp bridge iptable_filter bpfilter openvswitch 
nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_defrag_ipv6 nf_conncount nf_nat nf_conntrack 8021q garp mrp stp llc 
binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) dm_service_time zcommon(PO) 
znvpair(PO) dm_multipath scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua 
ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390
  [54084.082354]  sha1_s390 sha_common genwqe_card crc_itu_t chsc_sch eadm_sch 
ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd 
ib_iser rdma_cm auth_rpcgss nfs_acl iw_cm lockd grace ib_cm iscsi_tcp 
libiscsi_tcp sunrpc libiscsi scsi_transport_iscsi ip_tables x_tables btrfs 
zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx4_en 
mlx4_ib qeth_l2 ib_core ptp pps_core crc32_vx_s390 mlx4_core devlink zfcp 
scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod
  [54084.082418] CPU: 3 PID: 217520 Comm: stress-ng-dev Tainted: P  DO  
4.18.0-11-generic #12-Ubuntu
  [54084.082420] Hardware name: IBM 2964 N63 400 (LPAR)
  [54084.082422] Krnl PSW : ed7ed85f 816ddc5c 
(usercopy_abort+0xb2/0xb8)
  [54084.082433]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 
RI:0 EA:3
  [54084.082436] Krnl GPRS: 0320 0006 0056 
0007
  [54084.082438]0007 7fe0 00a96d3a 

  [54084.082441]03ff 0006 0006 
0002acb4ee00
  [54084.082443]00a96d3a 00914430 00386606 
00038f087a78
  [54084.082449] Krnl Code: 003865fa: c02000390dc4  larl
%r2,aa8182
00386600: c0e5fff2b418  brasl   
%r14,1dce30
   #00386606: a7f40001  brc 
15,386608
   >0038660a: 0707  bcr 0,%r7
0038660c: 0707  bcr 0,%r7
0038660e: 0707  bcr 0,%r7
00386610: c004  brcl0,386610
00386616: ebcff0780024  stmg
%r12,%r15,120(%r15)
  [54084.082484] Call Trace:
  [54084.082487] ([<00386606>] usercopy_abort+0xae/0xb8)
  [54084.082489]  [<00386522>] __check_object_size+0x19a/0x1d0 
  [54084.082492]  [<005c69d8>] sg_scsi_ioctl+0x120/0x3d8 
  [54084.082495]  [<005c75b6>] scsi_cmd_ioctl+0x3ce/0x3d8 
  [54084.082497]  [<005c87d0>] bsg_ioctl+0x118/0x250 
  [54084.082499]  [<003a3c9c>] do_vfs_ioctl+0xac/0x650 
  [54084.082502]  [<003a42cc>] ksys_ioctl+0x8c/0xb8 
  [54084.082504]  [<003a432a>] sys_ioctl+0x32/0x40 
  [54084.082507]  [<008f0dc0>] system_call+0xdc/0x2c8 
  [54084.082508] Last Breaking-Event-Address:
  [54084.082510]  [<00386606>] usercopy_abort+0xae/0xb8
  [54084.082512]  
  [54084.082513] ---[ end trace 5009dd6293a23031 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with 

[Kernel-packages] [Bug 1769937] Re: Error reported when creating ZFS pool with "-t" option, despite successful pool creation

2018-10-30 Thread Colin Ian King
Tested with linux 4.4.0-139-generic #165 and zfsutils 0.6.5.6-0ubuntu26
- marking as verified for xenial

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

Title:
  Error reported when creating ZFS pool with "-t" option, despite
  successful pool creation

Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, Xenial, Bionic ==

  Bug:

  When creating a pool with the -t option on Ubuntu 18.04 LTS, it will
  report an error and return a non-zero exit code, but the pool appears
  to be successfully created.

  For example:

  # zpool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t 
rpool-25582 rpool /dev/mapper/loop2p1
  cannot create 'rpool': no such pool or dataset
  # zpool list
  NAME  SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  
ALTROOT
  rpool-25582  69.5G  92.5K  69.5G - 0% 0%  1.00x  ONLINE  
/mnt/rpool-25582
  # zpool export rpool-25582
  # zpool import rpool
  # zpool list
  NAMESIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  rpool  69.5G   134K  69.5G - 0% 0%  1.00x  ONLINE  -

  I opened an upstream bug against ZFS on Linux, here:
  https://github.com/zfsonlinux/zfs/issues/7502

  And it has been recently fixed, here:
  https://github.com/zfsonlinux/zfs/pull/7509

  Can this upstream fix be pulled into the Ubuntu 18.04 LTS packages?

  Thanks,
  Prakash

  == Fix ==

  Upstream zfs commit 4ceb8dd6fdfd ("Fix 'zpool create -t '")

  == Test ==

  Without the fix, creating a pool with -t will show an error message
  such as:

  "cannot create 'rpool': no such pool or dataset" and will return an
  error number even though it successfully created the pool. With the
  fix, the error is not shown and it exits with 0.

  E.g.

  pool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t 
rpool-25582 rpool /dev/mapper/loop2p1 
  cannot create 'rpool': no such pool or dataset

  == Regression Potential ==

  Small. This is an upstream fix that is know to fix the error. There
  are no known subsequent changes to the fix hence suggesting it is a
  good fix. The change is very limited and testing shows it does not
  break any of the kernel team's ZFS regression testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769937/+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 1793464] Re: Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel

2018-10-25 Thread Colin Ian King
Tested against -proposed kernel 4.4.0-139-generic, nbd tests no longer
fail. Marking as verified.

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

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

Title:
  Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==

  When running the Ubuntu nbd autotest regression test we trip a hang
  and then a little later a panic message.  There are two upstream
  fixes required as this is actually two issues in one. One fix is to 
  not to shutdown the sock when IRQs are disable and a second to fix is
  to race in the nbd ioctl.

  == Fix ==

  Upstream commits:

  23272a6754b81ff6503e09c743bb4ceeeab39997
nbd: Remove signal usage

  1f7b5cf1be4351e60cf8ae7aab976503dd73c5f8
nbd: Timeouts are not user requested disconnects

  0e4f0f6f63d3416a9e529d99febfe98545427b81
nbd: Cleanup reset of nbd and bdev after a disconnect

  c261189862c6f65117eb3b1748622a08ef49c262
nbd: don't shutdown sock with irq's disabled

  97240963eb308d8d21a89c0459822f7ea98463b4
nbd: fix race in ioctl

  The first 3 patches are prerequisites required for the latter two fixes to 
apply and work correctly.  Most of these backports are minor patch wiggles
  required because later patches have been applied to the driver in earlier 
fixes to this driver.
 

  == Regression Potential ==

  These fixes just touch nbd, so the regression potential is just
  limited to this. Secondly, we are pulling in upstream fixes that exist
  in Bionic and Cosmic kernels, so these are tried and tested fixes.

  == Test Case ==

1. Deploy a node with 4.4 Xenial
2. Run the ubuntu_nbd_smoke_test

  Without the fix, we get hang/crashes.  With the fix one can run this test
  multiple times without any issues at all.

  
  

  This issue can be reproduced on AMD64 KVM //bare-metal node, s390x
  zKVM node

  The test itself will pass, but the system will hang after a few
  second.

  Steps:
    1. Deploy a node with 4.4 Xenial
    2. Run the ubuntu_nbd_smoke_test

  If you have access to the console, you will see that this system
  actually bumped into a kernel panic:

   Unable to handle kernel pointer dereference in virtual kernel address space
   failing address: 03ff802c1000 TEID: 03ff802c1803
   Fault in home space mode while using kernel ASCE.
   Log here (s390x KVM): https://pastebin.ubuntu.com/p/dNmtvbGjmz/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-136-generic 4.4.0-136.162
  ProcVersionSignature: Ubuntu 4.4.0-136.162-generic 4.4.144
  Uname: Linux 4.4.0-136-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.
  Date: Thu Sep 20 03:46:00 2018
  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-136-generic N/A
   linux-backports-modules-4.4.0-136-generic  N/A
   linux-firmware 1.157.20
  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/1793464/+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 1769937] Re: Error reported when creating ZFS pool with "-t" option, despite successful pool creation

2018-10-25 Thread Colin Ian King
Tested with linux 4.4.0-193 and zfsutils 0.6.5.6-0ubuntu25 - marking as
verified for xenial

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

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

Title:
  Error reported when creating ZFS pool with "-t" option, despite
  successful pool creation

Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  New
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, Xenial, Bionic ==

  Bug:

  When creating a pool with the -t option on Ubuntu 18.04 LTS, it will
  report an error and return a non-zero exit code, but the pool appears
  to be successfully created.

  For example:

  # zpool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t 
rpool-25582 rpool /dev/mapper/loop2p1
  cannot create 'rpool': no such pool or dataset
  # zpool list
  NAME  SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  
ALTROOT
  rpool-25582  69.5G  92.5K  69.5G - 0% 0%  1.00x  ONLINE  
/mnt/rpool-25582
  # zpool export rpool-25582
  # zpool import rpool
  # zpool list
  NAMESIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  rpool  69.5G   134K  69.5G - 0% 0%  1.00x  ONLINE  -

  I opened an upstream bug against ZFS on Linux, here:
  https://github.com/zfsonlinux/zfs/issues/7502

  And it has been recently fixed, here:
  https://github.com/zfsonlinux/zfs/pull/7509

  Can this upstream fix be pulled into the Ubuntu 18.04 LTS packages?

  Thanks,
  Prakash

  == Fix ==

  Upstream zfs commit 4ceb8dd6fdfd ("Fix 'zpool create -t '")

  == Test ==

  Without the fix, creating a pool with -t will show an error message
  such as:

  "cannot create 'rpool': no such pool or dataset" and will return an
  error number even though it successfully created the pool. With the
  fix, the error is not shown and it exits with 0.

  E.g.

  pool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t 
rpool-25582 rpool /dev/mapper/loop2p1 
  cannot create 'rpool': no such pool or dataset

  == Regression Potential ==

  Small. This is an upstream fix that is know to fix the error. There
  are no known subsequent changes to the fix hence suggesting it is a
  good fix. The change is very limited and testing shows it does not
  break any of the kernel team's ZFS regression testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769937/+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 1797327] Re: getrandom02 in ubuntu_ltp_syscalls failed with X-kvm

2018-10-11 Thread Colin Ian King
I suspect that the entropy pool ran out of bits

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

Title:
  getrandom02 in ubuntu_ltp_syscalls failed with X-kvm

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

Bug description:
  This test will time out with X-KVM kernel on a KVM node.

  <<>>
  tag=getrandom02 stime=1539245024
  cmdline="getrandom02"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
  getrandom02.c:72: PASS: getrandom returned 256
  getrandom02.c:72: PASS: getrandom returned 6
  getrandom02.c:72: PASS: getrandom returned 256
  Test timeouted, sending SIGKILL!
  tst_test.c:1112: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1113: BROK: Test killed! (timeout?)

  Summary:
  passed   3
  failed   0
  skipped  0
  warnings 0

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1797327/+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 1793464] Re: Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel

2018-10-11 Thread Colin Ian King
** Description changed:

+ == SRU Justification ==
+ 
+ When running the Ubuntu nbd autotest regression test we trip a hang
+ and then a little later a panic message.  There are two upstream
+ fixes required as this is actually two issues in one. One fix is to 
+ not to shutdown the sock when IRQs are disable and a second to fix is
+ to race in the nbd ioctl.
+ 
+ == Fix ==
+ 
+ Upstream commits:
+ 
+ 23272a6754b81ff6503e09c743bb4ceeeab39997
+   nbd: Remove signal usage
+ 
+ 1f7b5cf1be4351e60cf8ae7aab976503dd73c5f8
+   nbd: Timeouts are not user requested disconnects
+ 
+ 0e4f0f6f63d3416a9e529d99febfe98545427b81
+   nbd: Cleanup reset of nbd and bdev after a disconnect
+ 
+ c261189862c6f65117eb3b1748622a08ef49c262
+   nbd: don't shutdown sock with irq's disabled
+ 
+ 97240963eb308d8d21a89c0459822f7ea98463b4
+   nbd: fix race in ioctl
+ 
+ The first 3 patches are prerequisites required for the latter two fixes to 
apply and work correctly.  Most of these backports are minor patch wiggles
+ required because later patches have been applied to the driver in earlier 
fixes to this driver.
+
+ 
+ == Regression Potential ==
+ 
+ These fixes just touch nbd, so the regression potential is just limited
+ to this. Secondly, we are pulling in upstream fixes that exist in Bionic
+ and Cosmic kernels, so these are tried and tested fixes.
+ 
+ == Test Case ==
+ 
+   1. Deploy a node with 4.4 Xenial
+   2. Run the ubuntu_nbd_smoke_test
+ 
+ Without the fix, we get hang/crashes.  With the fix one can run this test
+ multiple times without any issues at all.
+ 
+ 
+ 
+ 
  This issue can be reproduced on AMD64 KVM //bare-metal node, s390x zKVM
  node
  
  The test itself will pass, but the system will hang after a few second.
  
  Steps:
    1. Deploy a node with 4.4 Xenial
    2. Run the ubuntu_nbd_smoke_test
  
  If you have access to the console, you will see that this system
  actually bumped into a kernel panic:
  
   Unable to handle kernel pointer dereference in virtual kernel address space
   failing address: 03ff802c1000 TEID: 03ff802c1803
   Fault in home space mode while using kernel ASCE.
   Log here (s390x KVM): https://pastebin.ubuntu.com/p/dNmtvbGjmz/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-136-generic 4.4.0-136.162
  ProcVersionSignature: Ubuntu 4.4.0-136.162-generic 4.4.144
  Uname: Linux 4.4.0-136-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.
  Date: Thu Sep 20 03:46:00 2018
  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-136-generic N/A
   linux-backports-modules-4.4.0-136-generic  N/A
   linux-firmware 1.157.20
  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/1793464

Title:
  Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel

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

Bug description:
  == SRU Justification ==

  When running the Ubuntu nbd autotest regression test we trip a hang
  and then a little later a panic message.  There are two upstream
  fixes required as this is actually two issues in one. One fix is to 
  not to shutdown the sock when IRQs are disable and a second to fix is
  to race in the nbd ioctl.

  == Fix ==

  Upstream commits:

  23272a6754b81ff6503e09c743bb4ceeeab39997
nbd: Remove signal usage

  1f7b5cf1be4351e60cf8ae7aab976503dd73c5f8
nbd: Timeouts are not user requested disconnects

  0e4f0f6f63d3416a9e529d99febfe98545427b81
nbd: Cleanup reset of nbd and bdev after a disconnect

  c261189862c6f65117eb3b1748622a08ef49c262
nbd: don't shutdown sock with irq's disabled

  97240963eb308d8d21a89c0459822f7ea98463b4
nbd: fix race in ioctl

  The first 3 patches are prerequisites required for the latter two fixes to 
apply and work correctly.  Most of these backports are minor patch wiggles
  required because later patches have been applied to the 

[Kernel-packages] [Bug 1796250] Re: sysfs test ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency

2018-10-11 Thread Colin Ian King
** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1796250

Title:
  sysfs test ubuntu_stress_smoke_test will cause kernel oops on
  X-lowlatency

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

Bug description:
  This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
  kernel.

  This issue cannot be reproduced with the kernel 4.4.0-137 in -updates (a bit 
random, see comment #4)
  And cannot be reproduced with the AMD64 generic kernel in -proposed 
(4.4.0-138) as well

  16:50:01 DEBUG| [stdout] timer STARTING
  16:50:05 ERROR| [stderr] 
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
 line 111: 39506 Killed  ./stress-ng -v -t ${DURATION} --${s} 
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
  16:50:05 DEBUG| [stdout] timer RETURNED 137
  16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
  16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging 
request at 00010001
  16:50:05 DEBUG| [stdout] [ 1419.065329] IP: [] 
kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
  16:50:05 DEBUG| [stdout] [ 1419.175602] Oops:  [#6] SMP
  16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag 
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp 
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64 
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64 
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way 
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif 
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds 
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid 
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi
  16:50:05 DEBUG| [stdout] [ 1420.062172]  scsi_transport_iscsi autofs4 btrfs 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel mptsas mptscsih pata_acpi hid_generic aesni_intel 
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid 
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
  16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm: 
ubuntu_stress_s Tainted: G  D 4.4.0-138-generic #164-Ubuntu
  16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge 
R415/08WNM9, BIOS 1.9.3 04/26/2012
  16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti: 
88016a5b task.ti: 88016a5b
  16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]  
[] kmem_cache_alloc+0x77/0x1f0
  16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0  EFLAGS: 
00010202
  16:50:05 DEBUG| [stdout] [ 1420.931924] RAX:  RBX: 
024000c0 RCX: 0129e216
  16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI: 
024000c0 RDI: 0001a5c0
  16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08: 
8802156da5c0 R09: 00010001
  16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11: 
0ff0 R12: 024000c0
  16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14: 
880215003b00 R15: 880215003b00
  16:50:05 DEBUG| [stdout] [ 1421.358354] FS:  7f1323076700() 
GS:8802156c() knlGS:
  16:50:05 DEBUG| [stdout] [ 1421.455081] CS:  0010 DS:  ES:  CR0: 
80050033
  16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3: 
00016f6dc000 CR4: 000406f0
  16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
  16:50:05 DEBUG| [stdout] [ 1421.632941]   88019c080a28 
 cfff
  16:50:05 DEBUG| [stdout] [ 1421.721371]  7fffefec 88020ff29000 
88016a5b3c38 811d53e8
  16:50:05 DEBUG| [stdout] [ 1421.809805]  0002 88019c080a28 
cfff 7fffefec
  16:50:05 DEBUG| [stdout] [ 1421.898237] Call Trace:
  16:50:05 DEBUG| [stdout] [ 1421.927367]  [] 
anon_vma_prepare+0x48/0x180
  16:50:05 DEBUG| [stdout] [ 1421.996017]  [] 
handle_mm_fault+0x13ed/0x1b70
  16:50:05 DEBUG| [stdout] [ 1422.066743]  [] ? 
atime_needs_update+0x6f/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.138510]  [] ? 
touch_atime+0x33/0xd0
  16:50:05 DEBUG| [stdout] [ 1422.202997]  [] ? 
generic_file_read_iter+0x5dc/0x6b0
  16:50:05 DEBUG| [stdout] [ 1422.281009]  [] ? 

  1   2   3   4   5   6   7   8   9   10   >