From: karol herbst <karolherbst@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: mmiotracer hangs the system
Date: Wed, 3 Aug 2016 20:24:39 +0200 [thread overview]
Message-ID: <CAEXux-aMZvkSH5vTeVN420sruhk29Cm0SnSJS0jcsYDKKiV2_g@mail.gmail.com> (raw)
In-Reply-To: <20160802121305.64307a8a@gandalf.local.home>
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@goodmis.org>:
> On Tue, 2 Aug 2016 19:08:24 +0300
> Andy Shevchenko <andy.shevchenko@gmail.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
next prev parent reply other threads:[~2016-08-03 18:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 10:08 mmiotracer hangs the system Andy Shevchenko
2016-08-02 10:36 ` Andy Shevchenko
2016-08-02 15:05 ` Andy Shevchenko
2016-08-02 15:07 ` Andy Shevchenko
2016-08-02 15:31 ` Steven Rostedt
2016-08-02 16:08 ` Andy Shevchenko
2016-08-02 16:13 ` Steven Rostedt
2016-08-03 18:24 ` karol herbst [this message]
2016-08-19 10:35 ` karol herbst
2016-08-19 13:02 ` Andy Shevchenko
2016-08-19 15:08 ` karol herbst
2016-08-19 15:35 ` Andy Shevchenko
2016-08-19 18:23 ` karol herbst
2016-08-19 20:46 ` Karol Herbst
2016-08-19 21:50 ` Andy Shevchenko
2016-10-13 21:12 ` Karol Herbst
2016-10-22 16:02 ` Andy Shevchenko
2016-11-19 10:56 ` Karol Herbst
2016-11-24 20:50 ` Karol Herbst
2016-08-19 13:34 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEXux-aMZvkSH5vTeVN420sruhk29Cm0SnSJS0jcsYDKKiV2_g@mail.gmail.com \
--to=karolherbst@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).