public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de>,
	Ilia Mirkin <imirkin@alum.mit.edu>,
	Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
	David Airlie <airlied@linux.ie>, Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
Date: Fri, 14 Jul 2017 17:11:57 +0200	[thread overview]
Message-ID: <1500045117.5763.18.camel@gmx.de> (raw)
In-Reply-To: <6341f91f-1c56-2188-f55b-2f47d23262fc@mni.thm.de>

On Fri, 2017-07-14 at 17:05 +0200, Tobias Klausmann wrote:
> On 7/14/17 3:41 PM, Mike Galbraith wrote:
> > On Fri, 2017-07-14 at 15:36 +0200, Mike Galbraith wrote:
> >>   All DRM did was to slip a
> >> WARN_ON_ONCE() that nouveau triggers into a kernel module where such
> >> things no longer warn, they blow the box out of the water.
> > BTW, turn that irksome WARN_ON_ONCE() in drivers/gpu/drm/drm_vblank.c
> > into a WARN_ONCE(), and all is peachy, you get the warning, box lives.
> >
> > ---
> >   drivers/gpu/drm/drm_vblank.c |    3 ++-
> >   1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > --- a/drivers/gpu/drm/drm_vblank.c
> > +++ b/drivers/gpu/drm/drm_vblank.c
> > @@ -605,7 +605,8 @@ bool drm_calc_vbltimestamp_from_scanoutp
> >   	 */
> >   	if (mode->crtc_clock == 0) {
> >   		DRM_DEBUG("crtc %u: Noop due to uninitialized mode.\n", pipe);
> > -		WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev));
> > +		WARN_ONCE(drm_drv_uses_atomic_modeset(dev), "%s: report me.\n",
> > +			  dev->driver->name);
> >   
> >   		return false;
> >   	}
> 
> 
> Hey,
> 
> confirmed this helps saving the box, but we still have to find the root 
> cause! Backtrace with the above fix applied (and the one which came in 
> with the latest drm-fixes merge)!

Yeah, I'll be reporting some extra whining from my 8600 GT backup box.

	-Mike

  parent reply	other threads:[~2017-07-14 15:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 17:32 [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith
2017-07-11 17:51 ` Ilia Mirkin
2017-07-11 18:08   ` Mike Galbraith
2017-07-11 18:22     ` Ilia Mirkin
2017-07-11 18:53       ` Mike Galbraith
2017-07-12  7:45         ` Mike Galbraith
2017-07-12  9:55       ` Mike Galbraith
2017-07-12 11:25         ` Mike Galbraith
2017-07-12 11:37           ` Ilia Mirkin
2017-07-12 17:19             ` Mike Galbraith
2017-07-12 19:33               ` Tobias Klausmann
2017-07-14 13:36             ` Mike Galbraith
2017-07-14 13:41               ` Mike Galbraith
2017-07-14 15:05                 ` Tobias Klausmann
2017-07-14 15:10                   ` [Nouveau] " Karol Herbst
2017-07-14 15:15                     ` Mike Galbraith
2017-07-14 15:16                       ` Ilia Mirkin
2017-07-14 15:19                     ` Tobias Klausmann
2017-07-14 15:20                       ` Ilia Mirkin
2017-07-14 15:55                         ` Peter Zijlstra
2017-07-14 15:11                   ` Mike Galbraith [this message]
2017-07-14 15:50               ` Peter Zijlstra
2017-07-14 15:58                 ` Mike Galbraith
2017-07-14 16:10                   ` Peter Zijlstra
2017-07-14 16:33                     ` Mike Galbraith
2017-07-14 19:42                       ` Josh Poimboeuf
2017-07-15  2:45                         ` Mike Galbraith
2017-07-17 17:20                     ` Jessica Yu

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=1500045117.5763.18.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=airlied@linux.ie \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imirkin@alum.mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=peterz@infradead.org \
    --cc=tobias.johannes.klausmann@mni.thm.de \
    /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