linux 4.11.0-10.15 ADT test failure with linux 4.11.0-10.15

Bug #1702294 reported by Andy Whitcroft
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
Revision history for this message
Andy Whitcroft (apw) wrote :

02:27:29 DEBUG| [stdout] stress-ng: debug: [1529] 4 processors online, 4 processors configured
02:27:29 DEBUG| [stdout] stress-ng: info: [1529] dispatching hogs: 4 sockpair
02:27:29 DEBUG| [stdout] stress-ng: debug: [1529] cache allocate: reducing cache level from L3 (too high) to L2
02:27:29 DEBUG| [stdout] stress-ng: debug: [1529] cache allocate: default cache size: 512K
02:27:29 DEBUG| [stdout] stress-ng: debug: [1529] starting stressors
02:27:29 DEBUG| [stdout] stress-ng: debug: [1529] 4 stressors spawned
02:27:29 DEBUG| [stdout] stress-ng: debug: [1532] stress-ng-sockpair: started [1532] (instance 2)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1530] stress-ng-sockpair: started [1530] (instance 0)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1533] stress-ng-sockpair: started [1533] (instance 3)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1531] stress-ng-sockpair: started [1531] (instance 1)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1533] stress-ng-sockpair: child died: signal 9 (Killed) (instance 3)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1533] stress-ng-sockpair: assuming killed by OOM killer, restarting again (instance 3)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1529] process 1530 (stress-ng-sockpair) terminated on signal: 9 (Killed)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1529] process [1530] terminated
02:27:29 DEBUG| [stdout] stress-ng: debug: [1529] process 1531 (stress-ng-sockpair) terminated on signal: 9 (Killed)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1529] process [1531] terminated
02:27:29 DEBUG| [stdout] stress-ng: debug: [1533] stress-ng-sockpair: child died: signal 9 (Killed) (instance 3)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1533] stress-ng-sockpair: assuming killed by OOM killer, restarting again (instance 3)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1538] stress-ng-sockpair: read failed, errno=1 (Operation not permitted)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1545] stress-ng-sockpair: read failed, errno=1 (Operation not permitted)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1533] stress-ng-sockpair: OOM restarts: 2
02:27:29 DEBUG| [stdout] stress-ng: debug: [1533] stress-ng-sockpair: exited [1533] (instance 3)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1541] stress-ng-sockpair: read failed, errno=1 (Operation not permitted)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1532] stress-ng-sockpair: exited [1532] (instance 2)
02:27:29 DEBUG| [stdout] stress-ng: debug: [1529] process [1532] terminated
02:27:29 DEBUG| [stdout] stress-ng: debug: [1529] process [1533] terminated
02:27:29 DEBUG| [stdout] stress-ng: info: [1529] unsuccessful run completed in 5.44s

tags: added: kernel-adt-failure kernel-adt-failure-lts-trusty
Revision history for this message
Colin Ian King (colin-king) wrote :

I had disabled this, but there was a missing space (typo) in the list of stressors to disable, so it never got turned off. Doh.

Fixed committed: http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=775f7f8d656ef7e6b28cc94b2461cac985729070

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1702294

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
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.