------- Comment From dnban...@us.ibm.com 2018-04-24 10:39 EDT------- Doug, I somehow missed that note about the dump.
It is on boslcp3 (root/don2rry): /var/crash/201804181042 . I believe they may have mirrored it to some other location as well (I thought I saw a note about that, somewhere in this bug). Yes indeed, comment #85. Regarding the crash, for this particular invocation: In this case unfortunately it appears that threads on CPU 104 and CPU 129 interfered in the work object scheduling/execution. CPU 129 was executing the worker function when qla2xxx driver scheduled another instance of the same work object. As a result, after the object was deleted from 129's queue it was inserted into 104's queue and the work->data was first written with the correct pwq info (from the scheduling/insertion part) but then overwritten with the marker value from execution/deletion path. The pool->lock won't protect against this kind of accesses. As a result we have a work object in the list with the special value instead of the proper (pwq) queue value. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
