commit 97e5eddcc5300a0f59a55248cd243937a8ab
Author: Daniel Vetter
Date: Fri Oct 23 10:56:12 2015 +0200
drm/i915: shut up gen8+ SDE irq dmesg noise
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
(In reply to Jesse Barnes from comment #39)
> Looks like a crash (on resume?), I'll take a look.
Yes this is the drm_mm fumble I think. It's fixed in latest kernels, so
unfortunately you need to retest. Relevant patch
commit 046d669c62f37323ef0329c41d83a03c06b2087d
Author: Krzysztof Kolasa
Date:
Can someone lease retest with latest drm-intel-nightly from
http://cgit.freedesktop.org/drm-intel Thanks. Still no idea though
what's amiss here ...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
*** Bug 79675 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1140716
Title:
[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs
Bug reporter seems to have disappeared, so closing. If this is still an
issue please reopen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1251065
Title:
HP Mini 1000 fails to resume fr
*** Bug 79675 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaro
Created attachment 104227
head start before enabling
Another crazy idea. Looking at logs and Jiri's patch, the critical step
seems to be when we set the valid bit. Let's see what happens if we give
the ring a headstart, hopefully catching the moving ring.
You can experiment with different values,
It's still very strange that HEAD starts to move once we've initialized
the ring. So it seems like we can properly reset it, but then it goes
banas ...
More dmesgs from different machines with that frob+debug patch
definitely appreciated.
--
You received this bug notification because you are a m
Jiri, can you please submit your patch from commment #83 to upstream?
It's not perfect, but ducttape is good, so I'll merge it as an interim
solution.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Created attachment 104181
frob ring_stop a bit
I think this is something we haven't tried yet. dmesg with results
highly welcome.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1339939
Ti
Created attachment 104208
frob + debug ring head
Ok, I'm honestly lost what's going on right now. Can you please retest
with this patch, which has piles of debug output?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Chris comment was just about your statement in comment #17 that this is
i915 related: The kernel driver is called i915, but the mesa driver for
your hw is i965. And like Chris said the kernel is just the messenger.
In short, the bisect of mesa is still required, nothing changed.
--
You received
It's a mesa thing, it's me being confused since the bugzilla update
somehow ended up in my kernel bugs folder.
For bisecting mesa you can simply build from sources without any need to
install anything. You only need to set LIBGL_DRIVERS_PATH to the
i965_dri.so binary built by mesa, e.g.
LIBGL_DRI
You need to check out the same version of mesa you have currently
installed, to make sure you can reproduce the issue correctly when
building from sources. Then the same for the last known working version.
Only once that's confirmed should you start the bisect.
--
You received this bug notificat
First hit on google for kernel besicting ;-)
https://wiki.ubuntu.com/Kernel/KernelBisection
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1282867
Title:
Many bugs in rendering with loc
Can you try to bisect through the mesa git history to find this
regression?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1282867
Title:
Many bugs in rendering with lockups, likely caus
Thanks everyone for reporting this and testing patches, fix is now on
track for 3.14 and stable kernels:
commit 2f589112609b0a964b3d78c99c0f3a83ac16add6
Author: Jani Nikula
Date: Tue Feb 11 11:52:05 2014 +0200
drm/i915/dp: add native aux defer retry limit
--
You received this bug notific
(In reply to comment #23)
> I have to refute this:
> trying to modset or suspend using intel-drm-nightly from 2014-01-26 doesn't
> work with my machine (UX302LG).
> Though I have screen from boot using the intel-drm-nightly kernels, for me
> the issue still is present whatever the branch.
-nightl
(In reply to comment #22)
> I tried today's drm-intel-nightly and all I get is a black screen,
> spinning CPU and I can't ssh in to see what's happening.
Ville went right away and created another regression in the load detect
code ;-) Patch should get merged soon.
--
You received this bug noti
Can you please attach a new dmesg when trying to set up the output
configuration on 3.13? Please boot with drm.debug=0xe.
Also please do the manual xrandr dance which makes things work and again
grab the complete dmesg. You might need to increase the dmesg buffer
with log_buf_len if messages start
Strange ... Can you please attach a drm.debug=0xe dmesg from that
kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1265544
Title:
8086:0a16 [UX302LG] black screen on boot 3.12.0-7
We've had to duplicate the hack in the hsw code:
commit 1021442098ee9328fdd4d113d63a3a7f2f40c37b
Author: Daniel Vetter
Date: Mon Nov 18 07:38:16 2013 +0100
drm/i915: Replicate BIOS eDP bpp clamping hack for hsw
*** This bug has been marked as a duplicate of bug 71049 ***
--
You received
(In reply to comment #28)
> I just had:
> [155147.011667] [drm] stuck on bsd ring
> [155147.012432] [drm:i915_set_reset_status] *ERROR* bsd ring hung inside bo
> (0x11d6c000 ctx 0) at 0x11d6c2cc
> with mesa 10 (with fixes from comment #20)...
> It's happened only twice in two days...
A hang in the
(In reply to comment #115)
> Created attachment 87857 [details]
> i915_error_state
>
> I also met this bug while I was watching video in mplayer. It every 1-2
> hours.
>
> [40787.765816] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
> [40787.765852] [drm] capturing error event; look f
(In reply to comment #112)
> Just a few remarks.
> I still see this bug with Kernel 3.8, Mesa 9.2.1 and DRI 2.99.904.
> Moreover, with switching from Mesa 9.1.x to Mesa 9.2.x the number of lockups
> highly increased (especially in games).
On snb the blorp engine in mesa has become a bit more hang-
(In reply to comment #115)
> Created attachment 87857 [details]
> i915_error_state
>
> I also met this bug while I was watching video in mplayer. It every 1-2
> hours.
>
> [40787.765816] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
> [40787.765852] [drm] capturing error event; look f
(In reply to comment #112)
> Just a few remarks.
> I still see this bug with Kernel 3.8, Mesa 9.2.1 and DRI 2.99.904.
> Moreover, with switching from Mesa 9.1.x to Mesa 9.2.x the number of lockups
> highly increased (especially in games).
On snb the blorp engine in mesa has become a bit more hang-
(In reply to comment #110)
> Hello. Same problem here.
>
> [ 485.443455] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
> [ 485.443467] [drm] capturing error event; look for more information in
> /sys/kernel/debug/dri/0/i915_error_state
> [ 485.452727] [drm:i915_set_reset_status] *ER
(In reply to comment #110)
> Hello. Same problem here.
>
> [ 485.443455] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
> [ 485.443467] [drm] capturing error event; look for more information in
> /sys/kernel/debug/dri/0/i915_error_state
> [ 485.452727] [drm:i915_set_reset_status] *ER
(In reply to comment #104)
> I'm not sure my problem is related to this bug.
Most likely it isn't - gpu hang is similar to an application crashing.
Please file a new bug report and don't forget to attach the error state
file. That's the first thing we need to triage the bug.
And of course list th
(In reply to comment #104)
> I'm not sure my problem is related to this bug.
Most likely it isn't - gpu hang is similar to an application crashing.
Please file a new bug report and don't forget to attach the error state
file. That's the first thing we need to triage the bug.
And of course list th
Please retest with latest drm-intel-fixes, specifically
commit 2e6efddd203c15ca5c4700511f717c0e9a3ea31a
Author: Imre Deak
Date: Fri Aug 23 23:50:23 2013 +0300
drm/i915: ivb: fix edp voltage swing reg val
--
You received this bug notification because you are a member of Kernel
Packages, w
(In reply to comment #111)
> yes, intel_iommu=igfx_off helps too. Thanks!
Ok, that's proof that something _really_ fishy is going on here. Big WTF
moment ... Imre do you have any ideas what this could be? Seen anything
like this when you've done the sg conversion?
--
You received this bug notifi
33 matches
Mail list logo