[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKb7UvhtOBOcOcsZXXXa2qVDd6YWQaZrKtMwfPj5V8wk=97DXw@mail.gmail.com>
Date: Fri, 14 Jul 2017 11:20:01 -0400
From: Ilia Mirkin <imirkin@...m.mit.edu>
To: Tobias Klausmann <tobias.johannes.klausmann@....thm.de>
Cc: Karol Herbst <karolherbst@...il.com>,
Mike Galbraith <efault@....de>,
Peter Zijlstra <peterz@...radead.org>,
David Airlie <airlied@...ux.ie>,
"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
Ben Skeggs <bskeggs@...hat.com>
Subject: Re: [Nouveau] [regression drm/noveau] suspend to ram -> BOOM:
exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
On Fri, Jul 14, 2017 at 11:19 AM, Tobias Klausmann
<tobias.johannes.klausmann@....thm.de> wrote:
> The conversion is a nice catch, but i'd like to have a bit more context, see
> below!
>
> With a better description:
>
> Tobias Klausmann <tobias.johannes.klausmann@....thm.de>
I don't think it was meant as a serious patch. WARN_ON_ONCE should
work. The fix isn't to remove all instances of WARN_ON_ONCE. The fix
is to fix WARN_ON_ONCE.
Powered by blists - more mailing lists