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

Groups > linux.kernel > #1462145 > unrolled thread

Re: [PATCH 3.14 42/79] drm/qxl: only report first monitor as connected if we have no state

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: [PATCH 3.14 42/79] drm/qxl: only report first monitor as  connected if we have no state Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2016-08-14 17:00 +0200
    Re: [PATCH 3.14 42/79] drm/qxl: only report first monitor as  connected if we have no state Jiri Slaby <jslaby@suse.cz> - 2016-08-16 10:30 +0200

#1462145 — Re: [PATCH 3.14 42/79] drm/qxl: only report first monitor as connected if we have no state

On Fri, May 27, 2016 at 01:06:24PM +0200, Jiri Slaby wrote:
> On 10/18/2015, 04:05 AM, Greg Kroah-Hartman wrote:
> > 3.14-stable review patch.  If anyone has any objections, please let me know.
> > 
> > ------------------
> > 
> > From: Dave Airlie <airlied@redhat.com>
> > 
> > commit 69e5d3f893e19613486f300fd6e631810338aa4b upstream.
> > 
> > If the server isn't new enough to give us state, report the first
> > monitor as always connected, otherwise believe the server side.
> 
> Hi,
> 
> I've got a bug report, that this commit breaks 3.12-stable:
> ===============
> While testing KDE5 packages which will be landing in Package Hub for
> SP1, we found a issue with qxl drm driver in kernel.
> 
> When booting SLES (or SLED) 12 SP1, in a libvirt KVM environment, with
> QXL as video driver, KDE5 plasma was not rendered on screen, you could
> only see mouse cursor.
> 
> Booting with nomodeset=1 or qxl.modeset=0 fixes the issue.
> ===============
> 
> Does it make sense? Is 3.12 missing some prerequisite? Or should we just
> revert the commit in 3.12? And what about 3.14, 4.1?

What ever happened to this?  Did you revert this in 3.12-stable?

thanks,

greg k-h

[toc] | [next] | [standalone]

#1463538

On 08/14/2016, 04:51 PM, Greg Kroah-Hartman wrote:
> On Fri, May 27, 2016 at 01:06:24PM +0200, Jiri Slaby wrote:
>> On 10/18/2015, 04:05 AM, Greg Kroah-Hartman wrote:
>>> 3.14-stable review patch.  If anyone has any objections, please let me know.
>>>
>>> ------------------
>>>
>>> From: Dave Airlie <airlied@redhat.com>
>>>
>>> commit 69e5d3f893e19613486f300fd6e631810338aa4b upstream.
>>>
>>> If the server isn't new enough to give us state, report the first
>>> monitor as always connected, otherwise believe the server side.
>>
>> Hi,
>>
>> I've got a bug report, that this commit breaks 3.12-stable:
>> ===============
>> While testing KDE5 packages which will be landing in Package Hub for
>> SP1, we found a issue with qxl drm driver in kernel.
>>
>> When booting SLES (or SLED) 12 SP1, in a libvirt KVM environment, with
>> QXL as video driver, KDE5 plasma was not rendered on screen, you could
>> only see mouse cursor.
>>
>> Booting with nomodeset=1 or qxl.modeset=0 fixes the issue.
>> ===============
>>
>> Does it make sense? Is 3.12 missing some prerequisite? Or should we just
>> revert the commit in 3.12? And what about 3.14, 4.1?
> 
> What ever happened to this?  Did you revert this in 3.12-stable?

I forgot about this completely, so I took no action back then. Neither
was this reverted in SLE. Neither I saw any other report since then. And
given it was released in Nov 2015, perhaps, I won't do anything with
that, assuming this was kvm issue or something.

thanks,
-- 
js
suse labs

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web