** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760638
Title:
dccp test in ubuntu_stress_smoke_test failed with 4.4/4.15 KVM kernel
Status in linux package in Ubuntu:
Triaged
Status in linux-kvm package in Ubuntu:
New
Status in linux source package in Xenial:
Triaged
Status in linux-kvm source package in Xenial:
New
Status in linux source package in Bionic:
Triaged
Status in linux-kvm source package in Bionic:
New
Bug description:
The test failed with:
16:26:24 DEBUG| [stdout] dccp STARTING
16:26:24 DEBUG| [stdout] dccp RETURNED 2
16:26:24 DEBUG| [stdout] dccp FAILED
16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] 2 processors online, 2
processors configured
16:26:24 DEBUG| [stdout] stress-ng: info: [2228] dispatching hogs: 4 dccp
16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] cache allocate: reducing
cache level from L3 (too high) to L2
16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] cache allocate: default
cache size: 4096K
16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] starting stressors
16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] 4 stressors spawned
16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: started
[2231] (instance 2)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: started
[2232] (instance 3)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: started
[2229] (instance 0)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: started
[2230] (instance 1)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: process
[2231] using socket port 10002
16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: process
[2229] using socket port 10000
16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: process
[2232] using socket port 10003
16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: process
[2230] using socket port 10001
16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: socket
failed, errno=94 (Socket type not supported)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: 0 messages
sent
16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: exited
[2231] (instance 2)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2239] stress-ng-dccp: socket
failed, errno=94 (Socket type not supported)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: socket
failed, errno=94 (Socket type not supported)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: 0 messages
sent
16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: exited
[2230] (instance 1)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: socket
failed, errno=94 (Socket type not supported)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: 0 messages
sent
16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: exited
[2232] (instance 3)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2235] stress-ng-dccp: socket
failed, errno=94 (Socket type not supported)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: socket
failed, errno=94 (Socket type not supported)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: 0 messages
sent
16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: exited
[2229] (instance 0)
16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2229
(stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core
failure)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] process [2229] terminated
16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2230
(stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core
failure)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] process [2230] terminated
16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2231
(stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core
failure)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] process [2231] terminated
16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2232
(stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core
failure)
16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] process [2232] terminated
16:26:24 DEBUG| [stdout] stress-ng: info: [2228] unsuccessful run completed
in 0.01s
16:26:24 DEBUG| [stdout]
Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local
--verbose autotest/client/tests/ubuntu_stress_smoke_test/control
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
Uname: Linux 4.4.0-1019-kvm x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Mon Apr 2 16:31:05 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760638/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
