This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1798722

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

Title:
  ubunut_nbd_smoke_test failed on Xenial (Intel Purley 2S)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The ubuntu_nbd_smoke_test is causing bug 1793464 on Xenial,

  however on this specific Intel Purley 2S node (daedalus) this test is
  totally not working:

  $ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_nbd_smoke_test/control 
   Writing results to /home/ubuntu/autotest/client/results/default
   Initializing the state engine
   Persistent state client.steps now set to []
   Persistent option harness now set to None
   Persistent option harness_args now set to None
   Selected harness: standalone
   START        ----    ----    timestamp=1539922474    localtime=Oct 19 
04:14:34       
   Persistent state client._record_indent now set to 1
   Test has timeout: 600 sec.
        START   ubuntu_nbd_smoke_test.nbd-smoke-test    
ubuntu_nbd_smoke_test.nbd-smoke-test    timestamp=1539922474    timeout=600     
localtime=Oct 19 04:14:34       
   Persistent state client._record_indent now set to 2
   Persistent state client.unexpected_reboot now set to 
('ubuntu_nbd_smoke_test.nbd-smoke-test', 'ubuntu_nbd_smoke_test.nbd-smoke-test')
   Waiting for pid 4567 for 600 seconds
   Running 'DEBIAN_FRONTEND=noninteractive apt-get install --yes --force-yes 
nbd-server nbd-client gdb'
   Reading package lists...
   Building dependency tree...
   Reading state information...
   gdb is already the newest version (7.11.1-0ubuntu1~16.5).
   The following package was automatically installed and is no longer required:
     grub-pc-bin
   Use 'sudo apt autoremove' to remove it.
   The following NEW packages will be installed:
     nbd-client nbd-server
   0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
   Need to get 101 kB of archives.
   After this operation, 327 kB of additional disk space will be used.
   Get:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 nbd-client 
amd64 1:3.13-1 [47.6 kB]
   Get:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 nbd-server amd64 
1:3.13-1 [52.9 kB]
   Preconfiguring packages ...
   Fetched 101 kB in 0s (358 kB/s)
   Selecting previously unselected package nbd-client.
  (Reading database ... 62023 files and directories currently installed.)
   Preparing to unpack .../nbd-client_1%3a3.13-1_amd64.deb ...
   Unpacking nbd-client (1:3.13-1) ...
   Selecting previously unselected package nbd-server.
   Preparing to unpack .../nbd-server_1%3a3.13-1_amd64.deb ...
   Unpacking nbd-server (1:3.13-1) ...
   Processing triggers for man-db (2.7.5-1) ...
   Processing triggers for systemd (229-4ubuntu21.4) ...
   Processing triggers for ureadahead (0.100.0-19) ...
   ureadahead will be reprofiled on next reboot
   Setting up nbd-client (1:3.13-1) ...
   update-initramfs: deferring update (trigger activated)
   update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults
   Setting up nbd-server (1:3.13-1) ...
   
   Creating config file /etc/nbd-server/config with new version
   Adding system user `nbd' (UID 113) ...
   Adding new group `nbd' (GID 117) ...
   Adding new user `nbd' (UID 113) with group `nbd' ...
   Not creating home directory `/etc/nbd-server'.
   Processing triggers for systemd (229-4ubuntu21.4) ...
   Processing triggers for ureadahead (0.100.0-19) ...
   Processing triggers for initramfs-tools (0.122ubuntu8.13) ...
   update-initramfs: Generating /boot/initrd.img-4.4.0-137-generic
   W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
   W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
   W: --force-yes is deprecated, use one of the options starting with --allow 
instead.
   Running 'rm -f /etc/*/S99autotest || true'
   Running 
'/home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke_test.sh'
   done
    
   
--------------------------------------------------------------------------------
   Image path:    /tmp/nbd_image.img
   Mount point:   /mnt/nbd-test-11862
   Date:          Fri Oct 19 04:14:56 UTC 2018
   Host:          daedalus
   Kernel:        4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018
   Machine:       daedalus x86_64 x86_64
   CPUs online:   112
   CPUs total:    112
   Page size:     4096
   Pages avail:   15892009
   Pages total:   16404535
   
--------------------------------------------------------------------------------
    
   tcp6       0      0 :::9999                 :::*                    LISTEN   
   12015/nbd-server
   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
          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
          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
          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 on /dev/nbd0 failed
   umount: /mnt/nbd-test-11862: not mounted
   disconnect, sock, done

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-137-generic 4.4.0-137.163
  ProcVersionSignature: User Name 4.4.0-137.163-generic 4.4.144
  Uname: Linux 4.4.0-137-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 Oct 19 04:02 seq
   crw-rw---- 1 root audio 116, 33 Oct 19 04:02 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Fri Oct 19 04:17:40 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. 
   Bus 001 Device 002: ID 0000:0001  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation S2600WFT
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-137-generic.efi.signed 
root=UUID=e93f24ed-4e90-4ccb-ba6d-f3b97fe0436f ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-137-generic N/A
   linux-backports-modules-4.4.0-137-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)
  dmi.bios.date: 11/29/2016
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C620.86B.01.00.0336.112920161700
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600WFT
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H48104-410
  dmi.chassis.asset.tag: ....................
  dmi.chassis.type: 23
  dmi.chassis.vendor: ...............................
  dmi.chassis.version: ..................
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0336.112920161700:bd11/29/2016:svnIntelCorporation:pnS2600WFT:pvr....................:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...............................:ct23:cvr..................:
  dmi.product.name: S2600WFT
  dmi.product.version: ....................
  dmi.sys.vendor: Intel Corporation

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

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

Reply via email to