------- Comment From jac...@de.ibm.com 2017-06-08 10:28 EDT------- I shut down the test system I used for the repros here yesterday. And all of a sudden during the shutdown process the system ran into a hang scenario again. I don't know whether that hang is related to the problem addressed here (blk_mq()), but I took a dump and uploaded it to Box as a precaution though ->
mclint_20170607_kernel_4_11_0-041100rc8_without_openafs.dump.bz2 General dump info: Dump format........: s390mv Version............: 5 Dump created.......: Wed, 07 Jun 2017 16:56:28 +0200 Dump ended.........: Wed, 07 Jun 2017 16:57:06 +0200 Dump CPU ID........: 9efc729648000 UTS node name......: mclint UTS kernel release.: 4.11.0-041100rc8-generic UTS kernel version.: #201704232131 SMP Mon Apr 24 02:10:15 UTC 2017 Build arch.........: s390x (64 bit) System arch........: s390x (64 bit) CPU count (online).: 2 CPU count (real)...: 4 Dump memory range..: 8192 MB Real memory range..: 8192 MB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670634 Title: blk-mq: possible deadlock on CPU hot(un)plug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1670634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
