stress-ng-sockfd failed on Zesty i386

Bug #1700052 reported by Po-Hsu Lin on 2017-06-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Colin Ian King

Bug Description

This test has failed on node gonzo with Zesty i386

But it has passed on node gonzo with Zesty amd64

Full log: http://pastebin.ubuntu.com/24932093/

Here is the error log:
 sock PASSED
 sockfd STARTING
 sockfd RETURNED 2
 sockfd FAILED
 stress-ng: debug: [23647] 6 processors online, 6 processors configured
 stress-ng: info: [23647] dispatching hogs: 4 sockfd
 stress-ng: debug: [23647] cache allocate: default cache size: 8192K
 stress-ng: debug: [23647] starting stressors
 stress-ng: debug: [23648] stress-ng-sockfd: started [23648] (instance 0)
 stress-ng: debug: [23649] stress-ng-sockfd: started [23649] (instance 1)
 stress-ng: debug: [23647] 4 stressors spawned
 stress-ng: debug: [23650] stress-ng-sockfd: started [23650] (instance 2)
 stress-ng: debug: [23651] stress-ng-sockfd: started [23651] (instance 3)
 stress-ng: debug: [23649] stress-ng-sockfd: process [23649] using socket port 8001
 stress-ng: debug: [23648] stress-ng-sockfd: process [23648] using socket port 8000
 stress-ng: debug: [23650] stress-ng-sockfd: process [23650] using socket port 8002
 stress-ng: debug: [23651] stress-ng-sockfd: process [23651] using socket port 8003
 stress-ng: debug: [23647] process 23648 (stress-ng-sockfd) terminated on signal: 9 (Killed)
 stress-ng: debug: [23647] process [23648] terminated
 stress-ng: debug: [23647] process 23649 (stress-ng-sockfd) terminated on signal: 9 (Killed)
 stress-ng: debug: [23647] process [23649] terminated
 stress-ng: debug: [23647] process 23650 (stress-ng-sockfd) terminated on signal: 13 (Broken pipe)
 stress-ng: debug: [23647] process [23650] terminated
 stress-ng: debug: [23647] process 23651 (stress-ng-sockfd) terminated on signal: 13 (Broken pipe)
 stress-ng: debug: [23647] process [23651] terminated
 stress-ng: info: [23647] unsuccessful run completed in 11.72s

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 1700052

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
tags: added: zesty
Changed in linux (Ubuntu):
importance: Undecided → High
assignee: nobody → Colin Ian King (colin-king)
Colin Ian King (colin-king) wrote :

Fix committed: http://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=6ef400f874410a8c414923748f79cf944d06f6af

This fix is now in stress-ng and should therefore be picked up on the next ADT run. Can you verify that this now works on the ADT tests for the 4.11 kernel?

Changed in linux (Ubuntu):
status: Incomplete → In Progress
importance: High → Medium
status: In Progress → Fix Committed
Po-Hsu Lin (cypressyew) wrote :

Hello Colin,
Yes this sockfd test has passed on Artful i386 ADT test.

But for Zesty i386, it failed with a different error:
22:46:46 DEBUG| [stdout] sockfd STARTING
22:46:51 DEBUG| [stdout] sockfd RETURNED 137
22:46:51 ERROR| [stderr] /tmp/autopkgtest.IXyugT/build.zB5/linux-4.10.0/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh: line 96: 10762 Killed ./stress-ng -v -t ${DURATION} --${s} ${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
22:46:51 DEBUG| [stdout] sockfd BADRET (unknown return status 137)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers