[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEXux-aMZvkSH5vTeVN420sruhk29Cm0SnSJS0jcsYDKKiV2_g@mail.gmail.com>
Date: Wed, 3 Aug 2016 20:24:39 +0200
From: karol herbst <karolherbst@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: mmiotracer hangs the system
hi all,
mhhh exactly this commit fixed mmiotrace for me and a few other
nouveau devs on x86_64.
Also the error log doesn't really show a problem inside the tracer?
Maybe it would be helpful to provide full dmesg in the case of error,
just to rule silly things out.
I will try to figure out how that bug could happen at all.
Greetings
Karol
2016-08-02 18:13 GMT+02:00 Steven Rostedt <rostedt@...dmis.org>:
> On Tue, 2 Aug 2016 19:08:24 +0300
> Andy Shevchenko <andy.shevchenko@...il.com> 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
Powered by blists - more mailing lists