On Thu, Jul 13, 2017 at 03:04:58PM +0100, Chris Wilson wrote:
> Quoting Jiri Slaby (2017-07-13 14:57:31)
> > Stealing this thread as an opensuse user hit that too:
> > https://bugzilla.suse.com/show_bug.cgi?id=1045105
>
> It's a false positive. I did once upon a time send some patches to move
>
On Thu, Jul 13, 2017 at 03:57:31PM +0200, Jiri Slaby wrote:
> Hmm, not that easy:
> [ +0.011001] BUG: key 8807573ed758 not in .data!
> [ +0.000103] DEBUG_LOCKS_WARN_ON(1)
> [ +0.12] [ cut here ]
> [ +0.000147] WARNING: CPU: 1 PID: 282 at
>
Quoting Jiri Slaby (2017-07-13 14:57:31)
> Stealing this thread as an opensuse user hit that too:
> https://bugzilla.suse.com/show_bug.cgi?id=1045105
It's a false positive. I did once upon a time send some patches to move
the lockdep warning to kref so that didn't need to call it from drm
before
Stealing this thread as an opensuse user hit that too:
https://bugzilla.suse.com/show_bug.cgi?id=1045105
On 11/09/2016, 06:26 PM, Chris Wilson wrote:
> On Wed, Nov 09, 2016 at 06:02:40PM +0100, Hans de Goede wrote:
>> Hi,
>>
>> I noticed this while testing the displayport output attached
>> to
Hi,
On 09-11-16 18:26, Chris Wilson wrote:
> On Wed, Nov 09, 2016 at 06:02:40PM +0100, Hans de Goede wrote:
>> Hi,
>>
>> I noticed this while testing the displayport output attached
>> to the nvidia GPU on a Thinkpad P50 while the intel GPU
>> was driving the LCD panel (and was the primary GPU
Hi,
I noticed this while testing the displayport output attached
to the nvidia GPU on a Thinkpad P50 while the intel GPU
was driving the LCD panel (and was the primary GPU according
to Xorg). This was while logging into gnome-3 with Xorg-1.19-rc2,
from gdm (also running on top of Xorg-1.19-rc2).
On Wed, Nov 09, 2016 at 06:02:40PM +0100, Hans de Goede wrote:
> Hi,
>
> I noticed this while testing the displayport output attached
> to the nvidia GPU on a Thinkpad P50 while the intel GPU
> was driving the LCD panel (and was the primary GPU according
> to Xorg). This was while logging into
