On Fri, 2016-04-08 at 15:58 +0200, Sebastian Andrzej Siewior wrote: > On 04/08/2016 03:44 PM, Mike Galbraith wrote: > > On Thu, 2016-04-07 at 18:47 +0200, Sebastian Andrzej Siewior wrote: > > > > > just to be clear: The patch I attached did _not_ work for you. > > > > Did you perchance mean with "Reenable migration across schedule" > > reverted? Figured it would still explode in seconds.. it did. > > I meant 4.4.6-rt13 + my patch and nothing else. > > > [ 172.996232] kernel BUG at kernel/locking/rtmutex.c:1360! > > okay. and how did you trigger this? Just Steven's script or was there > more to it? I run stockfish, futextest, hackbench and tbench with it, terminating and restarting them at random intervals just to make sure nobody gets into a comfortable little rut. Stockfish and tbench are sized as to not saturate the box, hackbench runs periodically (and with no args to turn it into a hog), futextest run.sh just does its normal thing. Trying to grab an rtmutex while queued on an rtmutex... doesn't matter much if it's the lock that likes to deadlock us, or the one you added instead of making that blasted lock really really dead. -Mike -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
