From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754726AbcHSKf2 (ORCPT ); Fri, 19 Aug 2016 06:35:28 -0400 Received: from mail-it0-f46.google.com ([209.85.214.46]:35564 "EHLO mail-it0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754617AbcHSKfZ (ORCPT ); Fri, 19 Aug 2016 06:35:25 -0400 MIME-Version: 1.0 In-Reply-To: <20160802121305.64307a8a@gandalf.local.home> References: <20160802113148.6784f2de@gandalf.local.home> <20160802121305.64307a8a@gandalf.local.home> From: karol herbst Date: Fri, 19 Aug 2016 12:35:24 +0200 Message-ID: Subject: Re: mmiotracer hangs the system To: Steven Rostedt Cc: Andy Shevchenko , "linux-kernel@vger.kernel.org" , "Paul E. McKenney" , Ingo Molnar Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi everybody, is there any update on that issue I missed somehow? I really don't want to leave the mmiotracer in a state, where it breaks something while fixing other issues. But for now, without being able to even reproduce the issue, I can't really do much, because the code in the current state looks sane to me. Maybe this case includes the mmiotracer cleaning things up and arms new region for mmiotracing and that's why it fails? Besides that, I have no idea and no way to reproduce this, so I can't help this way. Greetings 2016-08-02 18:13 GMT+02:00 Steven Rostedt : > On Tue, 2 Aug 2016 19:08:24 +0300 > Andy Shevchenko wrote: > >> I don't think so, since linux-next doesn't work until I revert this commit. >> >> I can try exactly v4.6 (yep, I tried stable versions, including >> v4.4.16 that's why all of them failed to me) if you still would like >> me to do so. > > If linux-next doesn't work, then don't bother. > > That commit obviously broke something and you'll probably need help > from Karol to fix it. > > Thanks, > > -- Steve