All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	kernel list <linux-kernel@vger.kernel.org>,
	daniel.vetter@intel.com, jani.nikula@linux.intel.com,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [regression] Re: 4.11-rc0, thinkpad x220: GPU hang
Date: Tue, 21 Mar 2017 15:02:34 +0100	[thread overview]
Message-ID: <20170321140234.GA23242@amd> (raw)
In-Reply-To: <20170306122341.GA3201@nuc-i3427.alporthouse.com>


[-- Attachment #1.1: Type: text/plain, Size: 2324 bytes --]

Hi!

> > > > > > mplayer stopped working after a while. Dmesg says:
> > > > > > 
> > > > > > [ 3000.266533] cdc_ether 2-1.2:1.0 usb0: register 'cdc_ether' at
> > > > 
> > > > Now I'm pretty sure it is a regression in v4.11-rc0. Any ideas what to
> > > > try? Bisect will be slow and nasty :-(.
> > > 
> > > I came the conclusion that #99671 is the ring HEAD overtaking the TAIL,
> > > and under the presumption that your bug matches (as the symptoms do):
> > > 
> > > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > > index 4ffa35faff49..62e31a7438ac 100644
> > > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > > @@ -782,10 +782,10 @@ static void i9xx_submit_request(struct drm_i915_gem_request *request)
> > >  {
> > >         struct drm_i915_private *dev_priv = request->i915;
> > >  
> > > -       i915_gem_request_submit(request);
> > > -
> > >         GEM_BUG_ON(!IS_ALIGNED(request->tail, 8));
> > >         I915_WRITE_TAIL(request->engine, request->tail);
> > > +
> > > +       i915_gem_request_submit(request);
> > >  }
> > >  
> > >  static void i9xx_emit_breadcrumb(struct drm_i915_gem_request *req, u32 *cs)
> > 
> > I applied it as:
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > index 91bc4ab..9c49c7a 100644
> > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > @@ -1338,9 +1338,9 @@ static void i9xx_submit_request(struct drm_i915_gem_request *request)
> >  {
> >  	struct drm_i915_private *dev_priv = request->i915;
> >  
> > -	i915_gem_request_submit(request);
> > -
> >  	I915_WRITE_TAIL(request->engine, request->tail);
> > +
> > +	i915_gem_request_submit(request);
> >  }
> >  
> >  static void i9xx_emit_breadcrumb(struct drm_i915_gem_request *req,
> > 
> > Hmm. But your next mail suggest that it may not be smart to try to
> > boot it? :-).
> 
> Don't bother, it'll promptly hang.

Any news here?

Is there something I can revert to get back to working system?

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	kernel list <linux-kernel@vger.kernel.org>,
	daniel.vetter@intel.com, jani.nikula@linux.intel.com,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [regression] Re: 4.11-rc0, thinkpad x220: GPU hang
Date: Tue, 21 Mar 2017 15:02:34 +0100	[thread overview]
Message-ID: <20170321140234.GA23242@amd> (raw)
In-Reply-To: <20170306122341.GA3201@nuc-i3427.alporthouse.com>

[-- Attachment #1: Type: text/plain, Size: 2324 bytes --]

Hi!

> > > > > > mplayer stopped working after a while. Dmesg says:
> > > > > > 
> > > > > > [ 3000.266533] cdc_ether 2-1.2:1.0 usb0: register 'cdc_ether' at
> > > > 
> > > > Now I'm pretty sure it is a regression in v4.11-rc0. Any ideas what to
> > > > try? Bisect will be slow and nasty :-(.
> > > 
> > > I came the conclusion that #99671 is the ring HEAD overtaking the TAIL,
> > > and under the presumption that your bug matches (as the symptoms do):
> > > 
> > > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > > index 4ffa35faff49..62e31a7438ac 100644
> > > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > > @@ -782,10 +782,10 @@ static void i9xx_submit_request(struct drm_i915_gem_request *request)
> > >  {
> > >         struct drm_i915_private *dev_priv = request->i915;
> > >  
> > > -       i915_gem_request_submit(request);
> > > -
> > >         GEM_BUG_ON(!IS_ALIGNED(request->tail, 8));
> > >         I915_WRITE_TAIL(request->engine, request->tail);
> > > +
> > > +       i915_gem_request_submit(request);
> > >  }
> > >  
> > >  static void i9xx_emit_breadcrumb(struct drm_i915_gem_request *req, u32 *cs)
> > 
> > I applied it as:
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > index 91bc4ab..9c49c7a 100644
> > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > @@ -1338,9 +1338,9 @@ static void i9xx_submit_request(struct drm_i915_gem_request *request)
> >  {
> >  	struct drm_i915_private *dev_priv = request->i915;
> >  
> > -	i915_gem_request_submit(request);
> > -
> >  	I915_WRITE_TAIL(request->engine, request->tail);
> > +
> > +	i915_gem_request_submit(request);
> >  }
> >  
> >  static void i9xx_emit_breadcrumb(struct drm_i915_gem_request *req,
> > 
> > Hmm. But your next mail suggest that it may not be smart to try to
> > boot it? :-).
> 
> Don't bother, it'll promptly hang.

Any news here?

Is there something I can revert to get back to working system?

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2017-03-21 14:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 14:34 4.11-rc0, thinkpad x220: GPU hang Pavel Machek
2017-02-28 15:02 ` Chris Wilson
2017-02-28 15:02   ` Chris Wilson
2017-03-05 23:01   ` [regression] " Pavel Machek
2017-03-05 23:01     ` Pavel Machek
2017-03-06 11:15     ` Chris Wilson
2017-03-06 11:15       ` Chris Wilson
2017-03-06 11:47       ` Chris Wilson
2017-03-06 11:47         ` Chris Wilson
2017-03-06 12:10       ` Pavel Machek
2017-03-06 12:10         ` Pavel Machek
2017-03-06 12:23         ` Chris Wilson
2017-03-06 12:23           ` Chris Wilson
2017-03-21 14:02           ` Pavel Machek [this message]
2017-03-21 14:02             ` Pavel Machek
2017-03-25 21:33           ` Pavel Machek
2017-03-25 21:33             ` Pavel Machek
2017-04-09 10:33           ` Pavel Machek
2017-04-09 10:33             ` Pavel Machek
2017-03-14  9:08     ` Thorsten Leemhuis
2017-03-14 11:35       ` Pavel Machek
2017-03-14 11:35         ` Pavel Machek

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=20170321140234.GA23242@amd \
    --to=pavel@ucw.cz \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.