Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1466274 > unrolled thread

Re: mmiotracer hangs the system

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: mmiotracer hangs the system karol herbst <karolherbst@gmail.com> - 2016-08-19 12:40 +0200
    Re: mmiotracer hangs the system Andy Shevchenko <andy.shevchenko@gmail.com> - 2016-08-19 15:10 +0200
      Re: mmiotracer hangs the system karol herbst <karolherbst@gmail.com> - 2016-08-19 17:10 +0200
        Re: mmiotracer hangs the system Andy Shevchenko <andy.shevchenko@gmail.com> - 2016-08-19 17:40 +0200
          Re: mmiotracer hangs the system karol herbst <karolherbst@gmail.com> - 2016-08-19 20:30 +0200
          Re: mmiotracer hangs the system Karol Herbst <karolherbst@gmail.com> - 2016-08-19 23:00 +0200
            Re: mmiotracer hangs the system Andy Shevchenko <andy.shevchenko@gmail.com> - 2016-08-20 00:00 +0200
    Re: mmiotracer hangs the system Steven Rostedt <rostedt@goodmis.org> - 2016-08-19 15:40 +0200

#1466274 — Re: mmiotracer hangs the system

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 <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

[toc] | [next] | [standalone]

#1466379

On Fri, Aug 19, 2016 at 1:35 PM, karol herbst <karolherbst@gmail.com> wrote:
> 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.

No updates. I'm busy right now with more priority tasks and revert
works for me. Issue is reproducible in my case 100%.

So, I would able to attach dmesg in case it would be helpful.
Otherwise tell me exact instructions how to debug the issue.

Here you are:
http://pastebin.com/raw/VfTZENt7

> 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.

Maybe. First thing happened is iounmap().

> 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.

-- 
With Best Regards,
Andy Shevchenko

[toc] | [prev] | [next] | [standalone]

#1466483

2016-08-19 15:02 GMT+02:00 Andy Shevchenko <andy.shevchenko@gmail.com>:
> On Fri, Aug 19, 2016 at 1:35 PM, karol herbst <karolherbst@gmail.com> wrote:
>> 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.
>
> No updates. I'm busy right now with more priority tasks and revert
> works for me. Issue is reproducible in my case 100%.
>

Is there something I could do with a "normal" haswell desktop system
to reproduce this issue?

I'll try to play around the next days a bit and maybe I find something
that works out here as well. It seems to be related to
unmapping-mapping cycles.

Because if this only happens with the pwm-lpss driver, it may be
really troublesome to debug, because I don't really know the code that
well to be sure where the issue might be.

> So, I would able to attach dmesg in case it would be helpful.
> Otherwise tell me exact instructions how to debug the issue.
>
> Here you are:
> http://pastebin.com/raw/VfTZENt7
>
>> 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.
>
> Maybe. First thing happened is iounmap().
>
>> 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.
>
> --
> With Best Regards,
> Andy Shevchenko

[toc] | [prev] | [next] | [standalone]

#1466503

On Fri, Aug 19, 2016 at 6:08 PM, karol herbst <karolherbst@gmail.com> wrote:
> 2016-08-19 15:02 GMT+02:00 Andy Shevchenko <andy.shevchenko@gmail.com>:
>> On Fri, Aug 19, 2016 at 1:35 PM, karol herbst <karolherbst@gmail.com> wrote:
>>> 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.
>>
>> No updates. I'm busy right now with more priority tasks and revert
>> works for me. Issue is reproducible in my case 100%.
>>
>
> Is there something I could do with a "normal" haswell desktop system
> to reproduce this issue?

Try LPSS UART device(s)

>
> I'll try to play around the next days a bit and maybe I find something
> that works out here as well. It seems to be related to
> unmapping-mapping cycles.

That is the only thing I would think of.

>
> Because if this only happens with the pwm-lpss driver,

It has nothing to do with pwm-lpss since it's a HS UART and served by
intel-lpss driver.

> it may be
> really troublesome to debug, because I don't really know the code that
> well to be sure where the issue might be.
>
>> So, I would able to attach dmesg in case it would be helpful.
>> Otherwise tell me exact instructions how to debug the issue.
>>
>> Here you are:
>> http://pastebin.com/raw/VfTZENt7
>>
>>> 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.
>>
>> Maybe. First thing happened is iounmap().


-- 
With Best Regards,
Andy Shevchenko

[toc] | [prev] | [next] | [standalone]

#1466607

2016-08-19 17:35 GMT+02:00 Andy Shevchenko <andy.shevchenko@gmail.com>:
> On Fri, Aug 19, 2016 at 6:08 PM, karol herbst <karolherbst@gmail.com> wrote:
>> 2016-08-19 15:02 GMT+02:00 Andy Shevchenko <andy.shevchenko@gmail.com>:
>>> On Fri, Aug 19, 2016 at 1:35 PM, karol herbst <karolherbst@gmail.com> wrote:
>>>> 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.
>>>
>>> No updates. I'm busy right now with more priority tasks and revert
>>> works for me. Issue is reproducible in my case 100%.
>>>
>>
>> Is there something I could do with a "normal" haswell desktop system
>> to reproduce this issue?
>
> Try LPSS UART device(s)
>

isn't this a skylake thing? Because my CPU and motherboard is a bit
older than this.

>>
>> I'll try to play around the next days a bit and maybe I find something
>> that works out here as well. It seems to be related to
>> unmapping-mapping cycles.
>
> That is the only thing I would think of.
>
>>
>> Because if this only happens with the pwm-lpss driver,
>
> It has nothing to do with pwm-lpss since it's a HS UART and served by
> intel-lpss driver.
>
>> it may be
>> really troublesome to debug, because I don't really know the code that
>> well to be sure where the issue might be.
>>
>>> So, I would able to attach dmesg in case it would be helpful.
>>> Otherwise tell me exact instructions how to debug the issue.
>>>
>>> Here you are:
>>> http://pastebin.com/raw/VfTZENt7
>>>
>>>> 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.
>>>
>>> Maybe. First thing happened is iounmap().
>
>
> --
> With Best Regards,
> Andy Shevchenko

[toc] | [prev] | [next] | [standalone]

#1466678

Hi again,

I was able to get a crash/freeze/something while unbinding/binding my
nvidia gpu from nouveau.

Guess that means something is odd. I will investigate this more over
the weekend.

2016-08-19 17:35 GMT+02:00 Andy Shevchenko <andy.shevchenko@gmail.com>:
> On Fri, Aug 19, 2016 at 6:08 PM, karol herbst <karolherbst@gmail.com> wrote:
>> 2016-08-19 15:02 GMT+02:00 Andy Shevchenko <andy.shevchenko@gmail.com>:
>>> On Fri, Aug 19, 2016 at 1:35 PM, karol herbst <karolherbst@gmail.com> wrote:
>>>> 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.
>>>
>>> No updates. I'm busy right now with more priority tasks and revert
>>> works for me. Issue is reproducible in my case 100%.
>>>
>>
>> Is there something I could do with a "normal" haswell desktop system
>> to reproduce this issue?
>
> Try LPSS UART device(s)
>
>>
>> I'll try to play around the next days a bit and maybe I find something
>> that works out here as well. It seems to be related to
>> unmapping-mapping cycles.
>
> That is the only thing I would think of.
>
>>
>> Because if this only happens with the pwm-lpss driver,
>
> It has nothing to do with pwm-lpss since it's a HS UART and served by
> intel-lpss driver.
>
>> it may be
>> really troublesome to debug, because I don't really know the code that
>> well to be sure where the issue might be.
>>
>>> So, I would able to attach dmesg in case it would be helpful.
>>> Otherwise tell me exact instructions how to debug the issue.
>>>
>>> Here you are:
>>> http://pastebin.com/raw/VfTZENt7
>>>
>>>> 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.
>>>
>>> Maybe. First thing happened is iounmap().
>
>
> --
> With Best Regards,
> Andy Shevchenko

[toc] | [prev] | [next] | [standalone]

#1466698

On Fri, Aug 19, 2016 at 11:46 PM, Karol Herbst <karolherbst@gmail.com> wrote:
> I was able to get a crash/freeze/something while unbinding/binding my
> nvidia gpu from nouveau.

>
> Guess that means something is odd. I will investigate this more over
> the weekend.

Thanks. Will wait for further updates.

-- 
With Best Regards,
Andy Shevchenko

[toc] | [prev] | [next] | [standalone]

#1466413

Andy,

OK, the ball is in your court. Karol can't reproduce it, thus it will
require you sending debug information back so we can get this solved.

-- Steve


On Fri, 19 Aug 2016 12:35:24 +0200
karol herbst <karolherbst@gmail.com> wrote:

> 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 <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  

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web