------- Comment on attachment From [email protected] 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. ** Attachment added: "bash script to recreate the panic" https://bugs.launchpad.net/bugs/1797367/+attachment/5202593/+files/chzdev_dbginfo_sequential.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797367 Title: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1797367/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
