------- Comment on attachment From <email address hidden> 2018-10-18 09:05 EDT-------
With the following bash script alone we are able to recreate the panic within minutes.
It basically performs a series of network device enable/disable commands in parallel with collecting debug data using /sbin/dbginfo.sh from the s390tools package.
Replace the network device id "0.0.1d40" in the script to a device that exists on system running the OS.
Seems the problem happens when /sysfs files are being altered while dbginfo is used to collect data from sysfs at the same time.
------- Comment on attachment From <email address hidden> 2018-10-18 09:05 EDT-------
With the following bash script alone we are able to recreate the panic within minutes.
It basically performs a series of network device enable/disable commands in parallel with collecting debug data using /sbin/dbginfo.sh from the s390tools package.
Replace the network device id "0.0.1d40" in the script to a device that exists on system running the OS.
Seems the problem happens when /sysfs files are being altered while dbginfo is used to collect data from sysfs at the same time.