Link to fedora patch
https://github.com/shvr/fedora-surface-pro-3-kernel/blob/master/drm-i915-turn-off-wc-mmaps.patch
On Oct 31, 2015 5:09 PM, "Bryan Cebuliak" <[email protected]> wrote:

>
> https://lists.fedoraproject.org/pipermail/package-announce/2015-June/160562.html
>
> From Fedora kernel change log:
> "...- Add patch to turn of WC mmaps on i915 from airlied (rhbz 1226743)..."
> On Oct 31, 2015 2:55 PM, "Bryan Cebuliak" <[email protected]>
> wrote:
>
>> https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1432194
>>
>> Is this the same bug?
>> On Oct 31, 2015 2:00 PM, "Bryan Cebuliak" <[email protected]>
>> wrote:
>>
>>>
>>> http://fedoramagazine.org/solution-graphics-issues-intel-graphics-chipsets-fedora-22/
>>>
>>> That is    how   fedora    approached  the  issue.
>>>
>>> On 31 October 2015 at 12:02, Bryan Cebuliak <[email protected]>
>>> wrote:
>>>
>>>> Lacking   resources  to do full kernel  commit bisect, "adjacent"
>>>> kernels
>>>> in  the order of
>>>> http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
>>>>
>>>> we  have last  good kernel
>>>> v3.19.8-ckt9-vivid/
>>>>
>>>> first bad  kernel:
>>>> v4.0-rc1-vivid/
>>>>
>>>> kernels   tested:
>>>> 3.19.8ckt4
>>>> 3.19.8ckt7
>>>> 3.19.8ckt9
>>>> 4.0.5
>>>> 4.0rc1
>>>> 4.1.2
>>>> 4.2.1
>>>> 4.2.5
>>>> 4.3rc7
>>>> I take it all back...  As I was working on my WebGL code just now it
>>>> crashed again.  I've attached my Xorg.2.log which clearly shows a
>>>> problem:
>>>>
>>>> [  1329.968] (WW) Falling back to old probe method for vesa
>>>> [  1332.117] (EE) intel(0): [drm] failed to set drm interface version:
>>>> Permission denied [13].
>>>> [  1332.117] (EE) intel(0): Failed to claim DRM device.
>>>> [  1332.117] (II) UnloadModule: "intel"
>>>> [  1332.117] (EE) Screen(s) found, but none have a usable configuration.
>>>> [  1332.117] (EE)
>>>> Fatal server error:
>>>> [  1332.117] (EE) no screens found(EE)
>>>> [  1332.117] (EE)
>>>> Please consult the The X.Org Foundation support
>>>>          at http://wiki.x.org
>>>>  for help.
>>>> [  1332.117] (EE) Please also check the log file at
>>>> "/var/log/Xorg.2.log" for additional information.
>>>> [  1332.117] (EE)
>>>> [  1332.142] (EE) Server terminated with error (1). Closing log file.
>>>>
>>>> What's up with that permissions error?  Also, why is it even getting
>>>> such an error so late after running just fine for hours?
>>>>
>>>> ** Attachment added: "Xorg.2.log"
>>>>
>>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509556/+attachment/4509620/+files/Xorg.2.log
>>>>
>>>> --
>>>> You received this bug notification because you are subscribed to the bug
>>>> report.
>>>> https://bugs.launchpad.net/bugs/1509556
>>>>
>>>> Title:
>>>>   Kubuntu Wily upgrade screen glitch with  4.2 kernel
>>>>
>>>> To manage notifications about this bug go to:
>>>>
>>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509556/+subscriptions
>>>>
>>>
>>>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509556

Title:
  Kubuntu Wily upgrade screen glitch with  4.2 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509556/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to