[Kernel-packages] [Bug 1839461] Re: sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

2019-08-09 Thread Colin Ian King
** Changed in: linux-aws (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux-aws (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux-aws (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1839461

Title:
  sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-aws source package in Disco:
  New

Bug description:
  Issue found on arm64 node with D-AWS kernel

  sysfs failed on: a1.2xlarge / a1.large
  procfs failed on: a1.2xlarge / a1.medium

  
  sysfs failure:
  sysfs FAILED
  stress-ng: debug: [16876] 8 processors online, 8 processors configured
  stress-ng: info: [16876] dispatching hogs: 4 sysfs
  stress-ng: debug: [16876] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [16876] cache allocate: default cache size: 2048K
  stress-ng: debug: [16876] starting stressors
  stress-ng: debug: [16877] stress-ng-sysfs: started [16877] (instance 
0)
  stress-ng: debug: [16878] stress-ng-sysfs: started [16878] (instance 
1)
  stress-ng: debug: [16876] 4 stressors spawned
  stress-ng: debug: [16879] stress-ng-sysfs: started [16879] (instance 
2)
  stress-ng: debug: [16880] stress-ng-sysfs: started [16880] (instance 
3)
  stress-ng: error: [16877] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/power/pm_print_times, aborting
  stress-ng: debug: [16877] stress-ng-sysfs: exited [16877] (instance 0)
  stress-ng: error: [16876] process 16877 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16877] terminated
  stress-ng: error: [16878] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/kernel/irq/1/name, aborting
  stress-ng: debug: [16878] stress-ng-sysfs: exited [16878] (instance 1)
  stress-ng: error: [16876] process 16878 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16878] terminated
  stress-ng: debug: [16879] stress-ng-sysfs: exited [16879] (instance 2)
  stress-ng: debug: [16876] process [16879] terminated
  stress-ng: debug: [16880] stress-ng-sysfs: exited [16880] (instance 3)
  stress-ng: debug: [16876] process [16880] terminated
  stress-ng: info: [16876] unsuccessful run completed in 5.04s

  procfs failure:
  procfs FAILED
  stress-ng: debug: [27728] 8 processors online, 8 processors configured
  stress-ng: info: [27728] dispatching hogs: 4 procfs
  stress-ng: debug: [27728] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [27728] cache allocate: default cache size: 2048K
  stress-ng: debug: [27728] starting stressors
  stress-ng: debug: [27729] stress-ng-procfs: started [27729] (instance 
0)
  stress-ng: debug: [27730] stress-ng-procfs: started [27730] (instance 
1)
  stress-ng: debug: [27728] 4 stressors spawned
  stress-ng: debug: [27731] stress-ng-procfs: started [27731] (instance 
2)
  stress-ng: debug: [27732] stress-ng-procfs: started [27732] (instance 
3)
  *** stack smashing detected ***: terminated
  stress-ng: debug: [27730] stress-ng-procfs: exited [27730] (instance 
1)
  stress-ng: debug: [27729] stress-ng-procfs: exited [27729] (instance 
0)
  stress-ng: debug: [27728] process [27729] terminated
  stress-ng: debug: [27728] process [27730] terminated
  stress-ng: debug: [27728] process [27731] (stress-ng-procfs) 
terminated on signal: 6 (Aborted)
  stress-ng: debug: [27728] process [27731] terminated
  stress-ng: debug: [27732] stress-ng-procfs: exited [27732] (instance 
3)
  stress-ng: debug: [27728] process [27732] terminated
  stress-ng: info: [27728] unsuccessful run completed in 5.00s

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1011-aws 5.0.0-1011.12
  ProcVersionSignature: User Name 5.0.0-1011.12-aws 5.0.15
  Uname: Linux 5.0.0-1011-aws aarch64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: arm64
  Date: Thu Aug  8 11:03:32 2019
  Ec2AMI: ami-0ac1a3bc4f5c85238
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2c
  Ec2InstanceType: a1.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839461/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1839461] Re: sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

2019-08-09 Thread Po-Hsu Lin
** Also affects: linux-aws (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: sru-20190722 ubuntu-stress-smoke-test

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1839461

Title:
  sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  New

Bug description:
  Issue found on arm64 node with D-AWS kernel

  sysfs failed on: a1.2xlarge / a1.large
  procfs failed on: a1.2xlarge / a1.medium

  
  sysfs failure:
  sysfs FAILED
  stress-ng: debug: [16876] 8 processors online, 8 processors configured
  stress-ng: info: [16876] dispatching hogs: 4 sysfs
  stress-ng: debug: [16876] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [16876] cache allocate: default cache size: 2048K
  stress-ng: debug: [16876] starting stressors
  stress-ng: debug: [16877] stress-ng-sysfs: started [16877] (instance 
0)
  stress-ng: debug: [16878] stress-ng-sysfs: started [16878] (instance 
1)
  stress-ng: debug: [16876] 4 stressors spawned
  stress-ng: debug: [16879] stress-ng-sysfs: started [16879] (instance 
2)
  stress-ng: debug: [16880] stress-ng-sysfs: started [16880] (instance 
3)
  stress-ng: error: [16877] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/power/pm_print_times, aborting
  stress-ng: debug: [16877] stress-ng-sysfs: exited [16877] (instance 0)
  stress-ng: error: [16876] process 16877 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16877] terminated
  stress-ng: error: [16878] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/kernel/irq/1/name, aborting
  stress-ng: debug: [16878] stress-ng-sysfs: exited [16878] (instance 1)
  stress-ng: error: [16876] process 16878 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16878] terminated
  stress-ng: debug: [16879] stress-ng-sysfs: exited [16879] (instance 2)
  stress-ng: debug: [16876] process [16879] terminated
  stress-ng: debug: [16880] stress-ng-sysfs: exited [16880] (instance 3)
  stress-ng: debug: [16876] process [16880] terminated
  stress-ng: info: [16876] unsuccessful run completed in 5.04s

  procfs failure:
  procfs FAILED
  stress-ng: debug: [27728] 8 processors online, 8 processors configured
  stress-ng: info: [27728] dispatching hogs: 4 procfs
  stress-ng: debug: [27728] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [27728] cache allocate: default cache size: 2048K
  stress-ng: debug: [27728] starting stressors
  stress-ng: debug: [27729] stress-ng-procfs: started [27729] (instance 
0)
  stress-ng: debug: [27730] stress-ng-procfs: started [27730] (instance 
1)
  stress-ng: debug: [27728] 4 stressors spawned
  stress-ng: debug: [27731] stress-ng-procfs: started [27731] (instance 
2)
  stress-ng: debug: [27732] stress-ng-procfs: started [27732] (instance 
3)
  *** stack smashing detected ***: terminated
  stress-ng: debug: [27730] stress-ng-procfs: exited [27730] (instance 
1)
  stress-ng: debug: [27729] stress-ng-procfs: exited [27729] (instance 
0)
  stress-ng: debug: [27728] process [27729] terminated
  stress-ng: debug: [27728] process [27730] terminated
  stress-ng: debug: [27728] process [27731] (stress-ng-procfs) 
terminated on signal: 6 (Aborted)
  stress-ng: debug: [27728] process [27731] terminated
  stress-ng: debug: [27732] stress-ng-procfs: exited [27732] (instance 
3)
  stress-ng: debug: [27728] process [27732] terminated
  stress-ng: info: [27728] unsuccessful run completed in 5.00s

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1011-aws 5.0.0-1011.12
  ProcVersionSignature: User Name 5.0.0-1011.12-aws 5.0.15
  Uname: Linux 5.0.0-1011-aws aarch64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: arm64
  Date: Thu Aug  8 11:03:32 2019
  Ec2AMI: ami-0ac1a3bc4f5c85238
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2c
  Ec2InstanceType: a1.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839461/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1839461] Re: sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

2019-08-09 Thread Colin Ian King
I was incorrect, it's actually a racy read on /proc/bus/pci/:00/00.0
that's causing a hang:

sudo cat /proc/bus/pci/\:00/00.0

..takes a few seconds.. with stress-ng we have a multi-threaded
open/read/close on this file with random read sizes, this seems to cause
the machine to hang and reboot a while later.  Reduced this down to a
single threaded read and the same issue occurs.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1839461

Title:
  sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  New

Bug description:
  Issue found on arm64 node with D-AWS kernel

  sysfs failed on: a1.2xlarge / a1.large
  procfs failed on: a1.2xlarge / a1.medium

  
  sysfs failure:
  sysfs FAILED
  stress-ng: debug: [16876] 8 processors online, 8 processors configured
  stress-ng: info: [16876] dispatching hogs: 4 sysfs
  stress-ng: debug: [16876] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [16876] cache allocate: default cache size: 2048K
  stress-ng: debug: [16876] starting stressors
  stress-ng: debug: [16877] stress-ng-sysfs: started [16877] (instance 
0)
  stress-ng: debug: [16878] stress-ng-sysfs: started [16878] (instance 
1)
  stress-ng: debug: [16876] 4 stressors spawned
  stress-ng: debug: [16879] stress-ng-sysfs: started [16879] (instance 
2)
  stress-ng: debug: [16880] stress-ng-sysfs: started [16880] (instance 
3)
  stress-ng: error: [16877] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/power/pm_print_times, aborting
  stress-ng: debug: [16877] stress-ng-sysfs: exited [16877] (instance 0)
  stress-ng: error: [16876] process 16877 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16877] terminated
  stress-ng: error: [16878] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/kernel/irq/1/name, aborting
  stress-ng: debug: [16878] stress-ng-sysfs: exited [16878] (instance 1)
  stress-ng: error: [16876] process 16878 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16878] terminated
  stress-ng: debug: [16879] stress-ng-sysfs: exited [16879] (instance 2)
  stress-ng: debug: [16876] process [16879] terminated
  stress-ng: debug: [16880] stress-ng-sysfs: exited [16880] (instance 3)
  stress-ng: debug: [16876] process [16880] terminated
  stress-ng: info: [16876] unsuccessful run completed in 5.04s

  procfs failure:
  procfs FAILED
  stress-ng: debug: [27728] 8 processors online, 8 processors configured
  stress-ng: info: [27728] dispatching hogs: 4 procfs
  stress-ng: debug: [27728] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [27728] cache allocate: default cache size: 2048K
  stress-ng: debug: [27728] starting stressors
  stress-ng: debug: [27729] stress-ng-procfs: started [27729] (instance 
0)
  stress-ng: debug: [27730] stress-ng-procfs: started [27730] (instance 
1)
  stress-ng: debug: [27728] 4 stressors spawned
  stress-ng: debug: [27731] stress-ng-procfs: started [27731] (instance 
2)
  stress-ng: debug: [27732] stress-ng-procfs: started [27732] (instance 
3)
  *** stack smashing detected ***: terminated
  stress-ng: debug: [27730] stress-ng-procfs: exited [27730] (instance 
1)
  stress-ng: debug: [27729] stress-ng-procfs: exited [27729] (instance 
0)
  stress-ng: debug: [27728] process [27729] terminated
  stress-ng: debug: [27728] process [27730] terminated
  stress-ng: debug: [27728] process [27731] (stress-ng-procfs) 
terminated on signal: 6 (Aborted)
  stress-ng: debug: [27728] process [27731] terminated
  stress-ng: debug: [27732] stress-ng-procfs: exited [27732] (instance 
3)
  stress-ng: debug: [27728] process [27732] terminated
  stress-ng: info: [27728] unsuccessful run completed in 5.00s

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1011-aws 5.0.0-1011.12
  ProcVersionSignature: User Name 5.0.0-1011.12-aws 5.0.15
  Uname: Linux 5.0.0-1011-aws aarch64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: arm64
  Date: Thu Aug  8 11:03:32 2019
  Ec2AMI: ami-0ac1a3bc4f5c85238
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2c
  Ec2InstanceType: a1.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage 

[Kernel-packages] [Bug 1839461] Re: sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

2019-08-08 Thread Colin Ian King
OK, it seems to hang on PCI device 00:01.0: 00:01.0 Serial controller:
Amazon.com, Inc. Device 8250

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1839461

Title:
  sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

Status in linux-aws package in Ubuntu:
  New

Bug description:
  Issue found on arm64 node with D-AWS kernel

  sysfs failed on: a1.2xlarge / a1.large
  procfs failed on: a1.2xlarge / a1.medium

  
  sysfs failure:
  sysfs FAILED
  stress-ng: debug: [16876] 8 processors online, 8 processors configured
  stress-ng: info: [16876] dispatching hogs: 4 sysfs
  stress-ng: debug: [16876] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [16876] cache allocate: default cache size: 2048K
  stress-ng: debug: [16876] starting stressors
  stress-ng: debug: [16877] stress-ng-sysfs: started [16877] (instance 
0)
  stress-ng: debug: [16878] stress-ng-sysfs: started [16878] (instance 
1)
  stress-ng: debug: [16876] 4 stressors spawned
  stress-ng: debug: [16879] stress-ng-sysfs: started [16879] (instance 
2)
  stress-ng: debug: [16880] stress-ng-sysfs: started [16880] (instance 
3)
  stress-ng: error: [16877] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/power/pm_print_times, aborting
  stress-ng: debug: [16877] stress-ng-sysfs: exited [16877] (instance 0)
  stress-ng: error: [16876] process 16877 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16877] terminated
  stress-ng: error: [16878] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/kernel/irq/1/name, aborting
  stress-ng: debug: [16878] stress-ng-sysfs: exited [16878] (instance 1)
  stress-ng: error: [16876] process 16878 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16878] terminated
  stress-ng: debug: [16879] stress-ng-sysfs: exited [16879] (instance 2)
  stress-ng: debug: [16876] process [16879] terminated
  stress-ng: debug: [16880] stress-ng-sysfs: exited [16880] (instance 3)
  stress-ng: debug: [16876] process [16880] terminated
  stress-ng: info: [16876] unsuccessful run completed in 5.04s

  procfs failure:
  procfs FAILED
  stress-ng: debug: [27728] 8 processors online, 8 processors configured
  stress-ng: info: [27728] dispatching hogs: 4 procfs
  stress-ng: debug: [27728] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [27728] cache allocate: default cache size: 2048K
  stress-ng: debug: [27728] starting stressors
  stress-ng: debug: [27729] stress-ng-procfs: started [27729] (instance 
0)
  stress-ng: debug: [27730] stress-ng-procfs: started [27730] (instance 
1)
  stress-ng: debug: [27728] 4 stressors spawned
  stress-ng: debug: [27731] stress-ng-procfs: started [27731] (instance 
2)
  stress-ng: debug: [27732] stress-ng-procfs: started [27732] (instance 
3)
  *** stack smashing detected ***: terminated
  stress-ng: debug: [27730] stress-ng-procfs: exited [27730] (instance 
1)
  stress-ng: debug: [27729] stress-ng-procfs: exited [27729] (instance 
0)
  stress-ng: debug: [27728] process [27729] terminated
  stress-ng: debug: [27728] process [27730] terminated
  stress-ng: debug: [27728] process [27731] (stress-ng-procfs) 
terminated on signal: 6 (Aborted)
  stress-ng: debug: [27728] process [27731] terminated
  stress-ng: debug: [27732] stress-ng-procfs: exited [27732] (instance 
3)
  stress-ng: debug: [27728] process [27732] terminated
  stress-ng: info: [27728] unsuccessful run completed in 5.00s

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1011-aws 5.0.0-1011.12
  ProcVersionSignature: User Name 5.0.0-1011.12-aws 5.0.15
  Uname: Linux 5.0.0-1011-aws aarch64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: arm64
  Date: Thu Aug  8 11:03:32 2019
  Ec2AMI: ami-0ac1a3bc4f5c85238
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2c
  Ec2InstanceType: a1.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1839461/+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


[Kernel-packages] [Bug 1839461] Re: sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

2019-08-08 Thread Colin Ian King
I'm hitting hangs when exercising /proc/bus/pci/:00/00.0 - i believe
after a specific amount of time the watchdog reboots the machine

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1839461

Title:
  sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

Status in linux-aws package in Ubuntu:
  New

Bug description:
  Issue found on arm64 node with D-AWS kernel

  sysfs failed on: a1.2xlarge / a1.large
  procfs failed on: a1.2xlarge / a1.medium

  
  sysfs failure:
  sysfs FAILED
  stress-ng: debug: [16876] 8 processors online, 8 processors configured
  stress-ng: info: [16876] dispatching hogs: 4 sysfs
  stress-ng: debug: [16876] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [16876] cache allocate: default cache size: 2048K
  stress-ng: debug: [16876] starting stressors
  stress-ng: debug: [16877] stress-ng-sysfs: started [16877] (instance 
0)
  stress-ng: debug: [16878] stress-ng-sysfs: started [16878] (instance 
1)
  stress-ng: debug: [16876] 4 stressors spawned
  stress-ng: debug: [16879] stress-ng-sysfs: started [16879] (instance 
2)
  stress-ng: debug: [16880] stress-ng-sysfs: started [16880] (instance 
3)
  stress-ng: error: [16877] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/power/pm_print_times, aborting
  stress-ng: debug: [16877] stress-ng-sysfs: exited [16877] (instance 0)
  stress-ng: error: [16876] process 16877 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16877] terminated
  stress-ng: error: [16878] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/kernel/irq/1/name, aborting
  stress-ng: debug: [16878] stress-ng-sysfs: exited [16878] (instance 1)
  stress-ng: error: [16876] process 16878 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16878] terminated
  stress-ng: debug: [16879] stress-ng-sysfs: exited [16879] (instance 2)
  stress-ng: debug: [16876] process [16879] terminated
  stress-ng: debug: [16880] stress-ng-sysfs: exited [16880] (instance 3)
  stress-ng: debug: [16876] process [16880] terminated
  stress-ng: info: [16876] unsuccessful run completed in 5.04s

  procfs failure:
  procfs FAILED
  stress-ng: debug: [27728] 8 processors online, 8 processors configured
  stress-ng: info: [27728] dispatching hogs: 4 procfs
  stress-ng: debug: [27728] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [27728] cache allocate: default cache size: 2048K
  stress-ng: debug: [27728] starting stressors
  stress-ng: debug: [27729] stress-ng-procfs: started [27729] (instance 
0)
  stress-ng: debug: [27730] stress-ng-procfs: started [27730] (instance 
1)
  stress-ng: debug: [27728] 4 stressors spawned
  stress-ng: debug: [27731] stress-ng-procfs: started [27731] (instance 
2)
  stress-ng: debug: [27732] stress-ng-procfs: started [27732] (instance 
3)
  *** stack smashing detected ***: terminated
  stress-ng: debug: [27730] stress-ng-procfs: exited [27730] (instance 
1)
  stress-ng: debug: [27729] stress-ng-procfs: exited [27729] (instance 
0)
  stress-ng: debug: [27728] process [27729] terminated
  stress-ng: debug: [27728] process [27730] terminated
  stress-ng: debug: [27728] process [27731] (stress-ng-procfs) 
terminated on signal: 6 (Aborted)
  stress-ng: debug: [27728] process [27731] terminated
  stress-ng: debug: [27732] stress-ng-procfs: exited [27732] (instance 
3)
  stress-ng: debug: [27728] process [27732] terminated
  stress-ng: info: [27728] unsuccessful run completed in 5.00s

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1011-aws 5.0.0-1011.12
  ProcVersionSignature: User Name 5.0.0-1011.12-aws 5.0.15
  Uname: Linux 5.0.0-1011-aws aarch64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: arm64
  Date: Thu Aug  8 11:03:32 2019
  Ec2AMI: ami-0ac1a3bc4f5c85238
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2c
  Ec2InstanceType: a1.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1839461/+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


[Kernel-packages] [Bug 1839461] Re: sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

2019-08-08 Thread Colin Ian King
@Sam, I tested this out and the machine went off line, so I'm not sure
if it died or got reprovisioned.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1839461

Title:
  sysfs / procfs from ubuntu_stress_smoke_test failed on D-AWS ARM64

Status in linux-aws package in Ubuntu:
  New

Bug description:
  Issue found on arm64 node with D-AWS kernel

  sysfs failed on: a1.2xlarge / a1.large
  procfs failed on: a1.2xlarge / a1.medium

  
  sysfs failure:
  sysfs FAILED
  stress-ng: debug: [16876] 8 processors online, 8 processors configured
  stress-ng: info: [16876] dispatching hogs: 4 sysfs
  stress-ng: debug: [16876] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [16876] cache allocate: default cache size: 2048K
  stress-ng: debug: [16876] starting stressors
  stress-ng: debug: [16877] stress-ng-sysfs: started [16877] (instance 
0)
  stress-ng: debug: [16878] stress-ng-sysfs: started [16878] (instance 
1)
  stress-ng: debug: [16876] 4 stressors spawned
  stress-ng: debug: [16879] stress-ng-sysfs: started [16879] (instance 
2)
  stress-ng: debug: [16880] stress-ng-sysfs: started [16880] (instance 
3)
  stress-ng: error: [16877] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/power/pm_print_times, aborting
  stress-ng: debug: [16877] stress-ng-sysfs: exited [16877] (instance 0)
  stress-ng: error: [16876] process 16877 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16877] terminated
  stress-ng: error: [16878] stress-ng-sysfs: A SIGSEGV occurred while 
exercising /sys/kernel/irq/1/name, aborting
  stress-ng: debug: [16878] stress-ng-sysfs: exited [16878] (instance 1)
  stress-ng: error: [16876] process 16878 (stress-ng-sysfs) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [16876] process [16878] terminated
  stress-ng: debug: [16879] stress-ng-sysfs: exited [16879] (instance 2)
  stress-ng: debug: [16876] process [16879] terminated
  stress-ng: debug: [16880] stress-ng-sysfs: exited [16880] (instance 3)
  stress-ng: debug: [16876] process [16880] terminated
  stress-ng: info: [16876] unsuccessful run completed in 5.04s

  procfs failure:
  procfs FAILED
  stress-ng: debug: [27728] 8 processors online, 8 processors configured
  stress-ng: info: [27728] dispatching hogs: 4 procfs
  stress-ng: debug: [27728] cache allocate: reducing cache level from 
L3 (too high) to L2
  stress-ng: debug: [27728] cache allocate: default cache size: 2048K
  stress-ng: debug: [27728] starting stressors
  stress-ng: debug: [27729] stress-ng-procfs: started [27729] (instance 
0)
  stress-ng: debug: [27730] stress-ng-procfs: started [27730] (instance 
1)
  stress-ng: debug: [27728] 4 stressors spawned
  stress-ng: debug: [27731] stress-ng-procfs: started [27731] (instance 
2)
  stress-ng: debug: [27732] stress-ng-procfs: started [27732] (instance 
3)
  *** stack smashing detected ***: terminated
  stress-ng: debug: [27730] stress-ng-procfs: exited [27730] (instance 
1)
  stress-ng: debug: [27729] stress-ng-procfs: exited [27729] (instance 
0)
  stress-ng: debug: [27728] process [27729] terminated
  stress-ng: debug: [27728] process [27730] terminated
  stress-ng: debug: [27728] process [27731] (stress-ng-procfs) 
terminated on signal: 6 (Aborted)
  stress-ng: debug: [27728] process [27731] terminated
  stress-ng: debug: [27732] stress-ng-procfs: exited [27732] (instance 
3)
  stress-ng: debug: [27728] process [27732] terminated
  stress-ng: info: [27728] unsuccessful run completed in 5.00s

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1011-aws 5.0.0-1011.12
  ProcVersionSignature: User Name 5.0.0-1011.12-aws 5.0.15
  Uname: Linux 5.0.0-1011-aws aarch64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: arm64
  Date: Thu Aug  8 11:03:32 2019
  Ec2AMI: ami-0ac1a3bc4f5c85238
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2c
  Ec2InstanceType: a1.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1839461/+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