loop / pty test in ubuntu_stress_smoke_test failed with P-3.2

Bug #1797544 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Stress-ng
Fix Released
High
Colin Ian King
ubuntu-kernel-tests
Fix Released
Undecided
Unassigned

Bug Description

This is a KVM node with 3.13 kernel on Precise

$ uname -a
Linux curly 3.2.0-136-generic #182-Ubuntu SMP Tue Sep 25 10:57:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

The loop and test in ubuntu_stress_smoke_test will fail:

10:16:55 DEBUG| [stdout] loop STARTING
10:16:55 DEBUG| [stdout] loop RETURNED 2
10:16:55 DEBUG| [stdout] loop FAILED
10:16:55 DEBUG| [stdout] stress-ng: debug: [7616] 2 processors online, 2 processors configured
10:16:55 DEBUG| [stdout] stress-ng: info: [7616] dispatching hogs: 4 loop
10:16:55 DEBUG| [stdout] stress-ng: debug: [7616] cache allocate: reducing cache level from L3 (too high) to L2
10:16:55 DEBUG| [stdout] stress-ng: debug: [7616] cache allocate: default cache size: 4096K
10:16:55 DEBUG| [stdout] stress-ng: debug: [7616] starting stressors
10:16:55 DEBUG| [stdout] stress-ng: debug: [7616] 4 stressors spawned
10:16:55 DEBUG| [stdout] stress-ng: debug: [7617] stress-ng-loop: started [7617] (instance 0)
10:16:55 DEBUG| [stdout] stress-ng: debug: [7619] stress-ng-loop: started [7619] (instance 2)
10:16:55 DEBUG| [stdout] stress-ng: debug: [7620] stress-ng-loop: started [7620] (instance 3)
10:16:55 DEBUG| [stdout] stress-ng: fail: [7617] stress-ng-loop: failed to disassociate /dev/loop0 from backing store, errno=16 (Device or resource busy)
10:16:55 DEBUG| [stdout] stress-ng: debug: [7618] stress-ng-loop: started [7618] (instance 1)
10:16:55 DEBUG| [stdout] stress-ng: fail: [7620] stress-ng-loop: failed to disassociate /dev/loop2 from backing store, errno=16 (Device or resource busy)
10:16:55 DEBUG| [stdout] stress-ng: fail: [7619] stress-ng-loop: failed to disassociate /dev/loop2 from backing store, errno=16 (Device or resource busy)
10:16:55 DEBUG| [stdout] stress-ng: fail: [7617] stress-ng-loop: failed to disassociate /dev/loop3 from backing store, errno=16 (Device or resource busy)
10:16:55 DEBUG| [stdout] stress-ng: fail: [7619] stress-ng-loop: failed to disassociate /dev/loop4 from backing store, errno=16 (Device or resource busy)
10:16:55 DEBUG| [stdout] stress-ng: fail: [7620] stress-ng-loop: failed to disassociate /dev/loop5 from backing store, errno=16 (Device or resource busy)
10:16:55 DEBUG| [stdout] info: 5 failures reached, aborting stress process
10:16:55 DEBUG| [stdout] stress-ng: fail: [7619] stress-ng-loop: failed to disassociate /dev/loop7 from backing store, errno=16 (Device or resource busy)
10:16:55 DEBUG| [stdout] info: 5 failures reached, aborting stress process
10:16:55 DEBUG| [stdout] stress-ng: debug: [7620] stress-ng-loop: exited [7620] (instance 3)
10:16:55 DEBUG| [stdout] stress-ng: fail: [7617] stress-ng-loop: failed to disassociate /dev/loop2 from backing store, errno=16 (Device or resource busy)
10:16:55 DEBUG| [stdout] info: 5 failures reached, aborting stress process
10:16:55 DEBUG| [stdout] stress-ng: debug: [7619] stress-ng-loop: exited [7619] (instance 2)
10:16:55 DEBUG| [stdout] stress-ng: debug: [7617] stress-ng-loop: exited [7617] (instance 0)
10:16:55 DEBUG| [stdout] stress-ng: error: [7616] process 7617 (stress-ng-loop) terminated with an error, exit status=1 (stress-ng core failure)
10:16:55 DEBUG| [stdout] stress-ng: debug: [7616] process [7617] terminated
10:16:55 DEBUG| [stdout] stress-ng: fail: [7618] stress-ng-loop: failed to disassociate /dev/loop2 from backing store, errno=16 (Device or resource busy)
10:16:55 DEBUG| [stdout] stress-ng: fail: [7618] stress-ng-loop: failed to disassociate /dev/loop0 from backing store, errno=16 (Device or resource busy)
10:16:55 DEBUG| [stdout] info: 5 failures reached, aborting stress process
10:16:55 DEBUG| [stdout] stress-ng: debug: [7618] stress-ng-loop: exited [7618] (instance 1)
10:16:55 DEBUG| [stdout] stress-ng: error: [7616] process 7618 (stress-ng-loop) terminated with an error, exit status=1 (stress-ng core failure)
10:16:55 DEBUG| [stdout] stress-ng: debug: [7616] process [7618] terminated
10:16:55 DEBUG| [stdout] stress-ng: error: [7616] process 7619 (stress-ng-loop) terminated with an error, exit status=1 (stress-ng core failure)
10:16:55 DEBUG| [stdout] stress-ng: debug: [7616] process [7619] terminated
10:16:55 DEBUG| [stdout] stress-ng: error: [7616] process 7620 (stress-ng-loop) terminated with an error, exit status=1 (stress-ng core failure)
10:16:55 DEBUG| [stdout] stress-ng: debug: [7616] process [7620] terminated
10:16:55 DEBUG| [stdout] stress-ng: info: [7616] unsuccessful run completed in 0.14s

10:21:03 DEBUG| [stdout] pty STARTING
10:21:08 DEBUG| [stdout] pty RETURNED 2
10:21:08 DEBUG| [stdout] pty FAILED
10:21:08 DEBUG| [stdout] stress-ng: debug: [24423] 2 processors online, 2 processors configured
10:21:08 DEBUG| [stdout] stress-ng: info: [24423] dispatching hogs: 4 pty
10:21:08 DEBUG| [stdout] stress-ng: debug: [24423] cache allocate: reducing cache level from L3 (too high) to L2
10:21:08 DEBUG| [stdout] stress-ng: debug: [24423] cache allocate: default cache size: 4096K
10:21:08 DEBUG| [stdout] stress-ng: debug: [24423] starting stressors
10:21:08 DEBUG| [stdout] stress-ng: debug: [24423] 4 stressors spawned
10:21:08 DEBUG| [stdout] stress-ng: debug: [24426] stress-ng-pty: started [24426] (instance 2)
10:21:08 DEBUG| [stdout] stress-ng: debug: [24427] stress-ng-pty: started [24427] (instance 3)
10:21:08 DEBUG| [stdout] stress-ng: debug: [24424] stress-ng-pty: started [24424] (instance 0)
10:21:08 DEBUG| [stdout] stress-ng: debug: [24425] stress-ng-pty: started [24425] (instance 1)
10:21:08 DEBUG| [stdout] stress-ng: fail: [24426] stress-ng-pty: open /dev/ptmx failed, errno=5 (Input/output error)
10:21:08 DEBUG| [stdout] stress-ng: fail: [24424] stress-ng-pty: open /dev/ptmx failed, errno=5 (Input/output error)
10:21:08 DEBUG| [stdout] stress-ng: fail: [24426] stress-ng-pty: open /dev/ptmx failed, errno=5 (Input/output error)
10:21:08 DEBUG| [stdout] stress-ng: fail: [24424] stress-ng-pty: open /dev/ptmx failed, errno=5 (Input/output error)
10:21:08 DEBUG| [stdout] stress-ng: fail: [24425] stress-ng-pty: open /dev/ptmx failed, errno=5 (Input/output error)
10:21:08 DEBUG| [stdout] stress-ng: fail: [24424] stress-ng-pty: open /dev/ptmx failed, errno=5 (Input/output error)
10:21:08 DEBUG| [stdout] info: 5 failures reached, aborting stress process
10:21:08 DEBUG| [stdout] stress-ng: fail: [24427] stress-ng-pty: open /dev/ptmx failed, errno=5 (Input/output error)
10:21:08 DEBUG| [stdout] info: 5 failures reached, aborting stress process
10:21:08 DEBUG| [stdout] stress-ng: fail: [24426] stress-ng-pty: open /dev/ptmx failed, errno=5 (Input/output error)
10:21:08 DEBUG| [stdout] info: 5 failures reached, aborting stress process
10:21:08 DEBUG| [stdout] stress-ng: debug: [24427] stress-ng-pty: exited [24427] (instance 3)
10:21:08 DEBUG| [stdout] stress-ng: debug: [24426] stress-ng-pty: exited [24426] (instance 2)
10:21:08 DEBUG| [stdout] stress-ng: debug: [24424] stress-ng-pty: exited [24424] (instance 0)
10:21:08 DEBUG| [stdout] stress-ng: error: [24423] process 24424 (stress-ng-pty) terminated with an error, exit status=1 (stress-ng core failure)
10:21:08 DEBUG| [stdout] stress-ng: debug: [24423] process [24424] terminated
10:21:08 DEBUG| [stdout] stress-ng: debug: [24425] stress-ng-pty: exited [24425] (instance 1)
10:21:08 DEBUG| [stdout] stress-ng: debug: [24423] process [24425] terminated
10:21:08 DEBUG| [stdout] stress-ng: error: [24423] process 24426 (stress-ng-pty) terminated with an error, exit status=1 (stress-ng core failure)
10:21:08 DEBUG| [stdout] stress-ng: debug: [24423] process [24426] terminated
10:21:08 DEBUG| [stdout] stress-ng: error: [24423] process 24427 (stress-ng-pty) terminated with an error, exit status=1 (stress-ng core failure)
10:21:08 DEBUG| [stdout] stress-ng: debug: [24423] process [24427] terminated
10:21:08 DEBUG| [stdout] stress-ng: info: [24423] unsuccessful run completed in 5.03s

Tags: precise
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Can be reproduce on bare-metal system with 3.2.0-137.183-generic

Changed in ubuntu-kernel-tests:
status: New → Confirmed
tags: added: precise
Revision history for this message
Colin Ian King (colin-king) wrote :

Loop test failure required a retry if EBUSY occurred, fix committed:

http://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=017f646bb0efbc548fd791cceab0d425a733be57

Revision history for this message
Colin Ian King (colin-king) wrote :
Changed in stress-ng:
importance: Undecided → High
status: New → Fix Committed
assignee: nobody → Colin Ian King (colin-king)
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Re-tested on two bare-metal systems, the stress smoke test passed without any issue.
Thanks!

Changed in stress-ng:
status: Fix Committed → Fix Released
Changed in ubuntu-kernel-tests:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.