Just to check: the patch _does_ get rid of the oops?
For the blank screen issue: Please boot with drm.debug=0x4 added to your
kernel cmdline, reproduce the problem and then attach the full dmesg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Created attachment 56176
fixup dp bpc calculations
Can you please try this patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912387
Title:
[arrandale] Black screen on login regression
Please attach xrandr --verbose output. Also please boot with
drm.debug=0xe attached to your kernel cmdline, try to set a low working
resolution and then a high non-working resolution and attach the entire
dmesg. Please ensure that the attached dmesg is complete, if stuff at
the beginning is
Nope, no more debug information needed. We've fixed quite a few bugs for
snb lately and luckily yours was among them!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912992
Title:
[snb-m-gt2+]
Chris Wilson also reports occasional (really occasionl) transcoder
failures on his x201 at the same resolution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale] desktop is
Turning of audio might help, can you please try this:
xrandr --output DP1 --set audio off
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale] desktop is messed up with external
I've read the downstream bug report and it looks like the current issue
is a completely different one. No sightings of using Xv, so my patch
won't have any effect.
Now trying to kill init is rather serious business. Bryce, can you
triage this in launchpad and check whether it's indeed an issue
Reassign back to the public - this needs somebody with the motivation
and hw to write the corresponding dvo driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/6270
Title:
[i855] no
If drm-intel-fixes works flawless, but just backporting the patch does
not yet work so great, we likely miss a few of the recent dp fixes in
-stable trees.
Closing this, please reopen if it shows up again or file a new bug
reporter if you still have other issues left.
--
You received this bug
I'm gonna lean out the window a bit here and declare this a hw issue
with the ram. If the issue pops up again with the more conservative
memory timings please reopen the bug so I know why I've had a head-on
encounter with a slab of concrete.
--
You received this bug notification because you are
Closing this, the original reporter seems to have disappeared.
To unnikrishnan: Please reopen a new bug for your issue, but please test
first on kernel 3.3 - kernel 2.6.32 is pretty much stone-age for
graphics issues and far away from relevant for upstream development.
--
You received this bug
Created attachment 59339
properly clear SSC1
... a patch for you to try. Please test, maybe we're lucky.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/754799
Title:
[arrandale] external VGA output
OOPS-decoding for fun and profit:
A reasonable decode of the code from the OOPS
0x400641 array+1: mov0x16e0(%r12),%rdx
0x400649 array+9: lea0x16e0(%r12),%rcx
0x400651 array+17: cmp%rdx,%rcx
0x400654 array+20: lea-0xb0(%rdx),%rax
0x40065b array+27: je 0x400682
Created attachment 55880
use private slab for i915 gem objects
Please try to reproduce the issue with patch. Also ensure that you
either use the SLAB allocator or if your using SLUB, please boot with
slub_debug on the kernel cmdline.
--
You received this bug notification because you are a
Created attachment 55869
flush overlay regfile
A victim for my patch, awesome! Please try it and report how well it
fares ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903831
Title:
[i855] GPU
Hm, that's another report saying that plugging in a 2nd monitor and
switching it on on snb machine magically fixes things ...
A few things: Can you upgrade your kernel to the latest drm-intel-fixes
branch from Keith's git:
https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=summary
--- Comment #7 from Martin Pool m...@sourcefrog.net 2012-01-22 22:01:45 PST
---
You are missing one declaration of dev_priv, around line 205. With that
fixed,
it does build on the Ubuntu kernel. I'm going to test it with slub_debug.
Oops, I've fixed that locally but forgot to amend the
(In reply to comment #86)
Now two weeks passed, I submitted five versions for a patch of this bug to the
mailing list, one here in public, yet nothing shows up in the official git
repository at all.
Is it just me or is nobody actually interested in getting this working?
I've replied to your
(In reply to comment #43)
I have now successfully compiled kernel 3.4.0-rc4-custom and booted into this
kernel using the instructions on
https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
ie. using ..
CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd
Upstream reporter seems to have gone awol, closing because if missing
data. Please reopen only when the request dmesg is available (and
preferably the bisect result).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, till we have evidence to the contrary I'll shrug this off as a hw
bogosity ... crt detection is a funky business and we get way too much
hate-mail from people because every time we touch it we break something.
So I prefer not to touch it. Since you can easily work around the issue
with xrandr,
Marking as fixed then, pls reopen if it blows up again, and thanks for
submitting the status update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale] desktop is messed up
Please double-check whether your 3.6 tree contains:
commit 0c96c65b48fba3ffe9822a554cbc0cd610765cd5
Author: Jani Nikula jani.nik...@intel.com
Date: Wed Sep 26 18:43:10 2012 +0300
drm/i915: use adjusted_mode instead of mode for checking the 6bpc
force flag
This should fix fallout from the
Sounds like we're making progress. Dropping the regression part, since
that's now fixed. For the corrupted VGA issue, we're working on fixes
for fdi/pch handling, so maybe that will be resolved soon. For eDP iself
we're likely still missing some fixes somewhere, but it's rather awesome
that you
Thanks for the update, adjusting the comment to reflect that this is now
only an issue on an ivb asus UX32A.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946311
Title:
only external screen is
(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
(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 for more
(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 bsd
(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
(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] *ERROR*
(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
(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 for more
(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
(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] *ERROR*
The drm-intel-fixes branch from http://cgit.freedesktop.org/~danvet/drm-
intel/ has them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175533
Title:
[HSW] intel VGA driver i915 doesn't support
Patch is also included in latest drm-intel-nightly, linux-next. So you
can test it by grabbing a distro-build of one of those.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041790
Title:
[snb] GPU
Ping for the requested debug info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074844
Title:
Display resolutions missing on external VGA display [regressing] on
12.10
To manage notifications
Nope, the pipe off timeout in bug #54687 is for ilk, this here is an
ivb. Until proven otherwise we need to presume that they're different
bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021924
Can you please check whether cherry-picking the referenced patch to a
stable kernel fixes the issues, too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152165
Title:
[ivb] GPU lockup IPEHR:
(In reply to comment #76)
Chris, what is the upstream status for the ring kicker patch? Is that
likely to get incorporated upstream, or do you feel it needs further polish
before it's ready? Would this patch incur some risk of regressions in other
areas were it be backported for inclusion in
Also please test Paulo's patch from bug #60039
https://bugs.freedesktop.org/attachment.cgi?id=77018
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021924
Title:
Multiple Displays not working on
(In reply to comment #12)
Created attachment 72641 [details]
dmesg data for drm.debug=0xe
Just to check: Is that dmesg from 3.8-rc2?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021924
Title:
(In reply to comment #146)
I can confirm I have not experienced the bug with drm-intel-next after
several days of testing. What's the procedure next? Are the patches going to
be backported to 3.7.x?
The band-aid is backported already afaik, the real fix should show up in
the next 3.7.x point
(In reply to comment #148)
Ah, thanks, great! Now I see that the two patches from Comment #144 and
Comment #145 are included in 3.7.3. So I guess the real fix you're talking
about it the one from Comment #143.
Yep, that's right.
--
You received this bug notification because you are a member
Awesome that this works out. Patch is merged into 3.8-rc2 as
commit 4283908ef7f11a72c3b80dd4cf026f1a86429f82
Author: Daniel Vetter daniel.vet...@ffwll.ch
Date: Fri Dec 14 23:38:28 2012 +0100
drm/i915: Implement WaDisableHiZPlanesWhenMSAAEnabled
I'm writing the mail to the stable kernel
--- Comment #33 from mikhail.v.gavri...@gmail.com ---
Which patch I need applied for fix this issue?
We can't reproduce the bug, so those are just patches to test
different ideas. Please test them both each individually (i.e. remove
the first before testing the 2nd patch) and the report whether
drm-intel-fixes from http://cgit.freedesktop.org/~danvet/drm-intel has
fixes for all known fdi link issues. I'll lean out the window a bit here
and claim that this is fixed now, thanks for reporting this bug an
please reopen if you still have issues (I wouldn't be too surprised by
that ...).
--
We've certainly fixed tons of eDP bugs in recent kernels to warrant re-
testing. Please test the latest drm-intel-nightly branch and report on
what exactly is still broken on the ivb machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Created attachment 71524
implement Hiz w/a for msaa
Kernel patch, please test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002170
Title:
system halted while idled for a long time.
To manage
Also: Is this an SNB GT1? Please spec the exact model and pci id of the
VGA device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002170
Title:
system halted while idled for a long time.
To
Lionel, can you please file a separate bug for your issue? Chances are
really high that it's a different underlying bug with similar symptoms.
And since untangling bug reporter after the fact is messy we'd like to
keep bugs separate until we're sure we're dealing with duplicates.
--
You received
Please try out the patch at
https://patchwork.kernel.org/patch/1885411/
It has a decent chance to reduce gtt trashing, which might be good
enough to again ducttape over the hangs. Or maybe change the pattern to
be able to reproduce it much quicker. In any case, should be interesting
...
--
You
Created attachment 71805
make the shrinker less aggressive
Duct-tape solution if it is one, but imo very much worth a try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1081009
Title:
[arrandale]
*** Bug 61925 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
Ping.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/906086
Title:
[arrandale] kernel OOPS setting external monitor to a higher
resolution
To manage notifications about this bug go to:
Ok, it's unclear what fixed things, but things seem fixed. Thanks for
reporting this issue, I'll close it as unreproducible, please reopen if
this shows up again for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you please give us specific details about your monitors makemodel and
serial number?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946311
Title:
only external screen is working with asus
Patches which should fix this are queued to drm-intel-next at
http://cgit.freedesktop.org/~danvet/drm-intel/
Specifically:
commit b03543857fd75876b96e10d4320b775e95041bb7
Author: Takashi Iwai ti...@suse.de
Date: Tue Mar 20 13:07:05 2012 +0100
drm/i915: Check VBIOS value for determining
The patch is merged for 3.5 (and already in drm-next).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956046
Title:
intel driver fails to use dual-link LVDS if lid is down at boot
To manage
Hm, we do have some other patches in drm-intel-next-queued that might
apply for your situation here. Please test with that. I'll reopen the
bug meanwhile, problem is clearly not yet solved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Original reporter seems to have gone amiss, closing as unreproducible.
Please reopen if this is still an issue (in that case also please attach
complete dmesg with drm.debug=0xe added to your kernel cmdline).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You need to check where the dvo chip actually is, i915 has about 6
different i2c channels. The easiest way is to use one of the i2c-tools
to detect chips on all the i2c buses that drm/i915 exposes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Yeah, the second i2cdetect dump looks much more reasonable, and it looks
like you've indeed found the right bus for your i2c device. So the next
step is to use that one with dev_priv-gmbus[GMBUS_PORT_DPB] and see
whether it works better.
Btw, the gmbus reserved and disabled don't really exist,
Created attachment 60416
drm driver reload script
Looks like you've made a start alright. As I've said, I've you're
getting stuck somewhere, don't be afreaid to pop up on #intel-gfx on
irc. To speed up the development you can also only reload the
drm/i915.ko kernel module. It's a bit tricky, so I
Just to check: Does your problem of the dp screen disappearing correlate
with:
[47766.404715] [drm:intel_dp_check_link_status], TMDS-9: channel EQ not ok,
retraining
[47766.404927] [drm:intel_dp_start_link_train], training pattern 1 signal
levels
[47766.405653]
Oh and: Can you please boot with drm.debug=0xe and attach the full
dmesg, just so we know what your system looks like? While at it, also
please attacht the output of xrandr --verbose, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Patch merged to -fixes as:
commit 3eef8918ff440837f6af791942d8dd07e1a268ee
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Mon Jun 4 17:05:40 2012 +0100
drm/i915: Mark the ringbuffers as being in the GTT domain
Thanks a lot for reporting this bug.
--
You received this bug
It looks like the private slab works around foreign memory corruption
and for the remaining issues the reporter has gone awol. Also, I don't
quite see the evidence for why this is a regression.
Tentatively closing, please reopen if this is still an issue on latest
kernel version.
--
You
We've had to duplicate the hack in the hsw code:
commit 1021442098ee9328fdd4d113d63a3a7f2f40c37b
Author: Daniel Vetter daniel.vet...@ffwll.ch
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
Strange ... Can you please attach a drm.debug=0xe dmesg from that
kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265544
Title:
8086:0a16 [UX302LG] black screen on boot 3.12.0-7
To manage
Meh, haven't gotten around to tackle this yet, so let's keep this bug
around for a bit more ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071288
Title:
xrandr won't enable LVDS1 unless VGA1 is
(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.
-nightly on
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
(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
I guess it's time to give up - the only approach with restricting the
deep sleep states resulted in horrid power consumption figures ... Just
wiggle your mouse a bit :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Assigning to Ville so he can submit the patch. To avoid bikeshedding
this to death: I prefer if we add a new intel_ring_begin_cacheline_safe
or so which encapsulates the logic. And obviously puts a WARN_ON if the
requested length is bigger than 1 cachline ;-)
--
You received this bug
Thanks everyone for reporting this and testing patches, fix is now on
track for 3.14 and stable kernels:
commit 2f589112609b0a964b3d78c99c0f3a83ac16add6
Author: Jani Nikula jani.nik...@intel.com
Date: Tue Feb 11 11:52:05 2014 +0200
drm/i915/dp: add native aux defer retry limit
--
You
Oh, I've looked a bit harder and noticed that thing are pretty neatly
screwed up in sdvo land. So not something I can fix in 1-2 easy patches.
And since sdvo isn't a high prio thing for us I've postponed this for
now.
If you can code and want to fix this yourself I could point you into the
right
I've just sent out the stable backport request, so this should get fixed
in the next stable kernel releases (or one of the next, around the merge
window there's a bit a lag usually due to the high patch load).
Thanks for reporting this issue and please reopen if it breaks again.
--
You received
You have kernel modesetting disabled and your version of the intel ddx
does not support usermodesetting any more. Please remove any
i915.modset=0 or nomodeset boot options. If kernelmodesetting doesn't
work for you, then we need to fix that (please reopen in that case and
provide dmesg with
Cool, thanks for reporting back, and I'm happy that kms works ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088147
Title:
Intel 915GM/GMA900 upgrade fails 12.04-12.10
To manage notifications
Hw no longer available for testing, so closing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152165
Title:
[ivb] GPU lockup IPEHR: 0x upon context restore
To manage notifications about
(In reply to comment #20)
Hopefully https://patchwork.kernel.org/patch/2841344/ is the right fix.
Can you please test the above patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152165
Title:
Please retest with latest drm-intel-fixes, specifically
commit 2e6efddd203c15ca5c4700511f717c0e9a3ea31a
Author: Imre Deak imre.d...@intel.com
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
Can you please reenable vt-d support and instead boot with
intel_iommu=igfx_off? That should only disable vt-d for the intel
integrated gfx device (and usually helps as well as turning it off
completely).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(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
Please reopen if it's still broken after retesting with the latest bits.
We know that eDP is a bit flakey, but knowing which parts are still
broken exactly is always helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Merged to dinq as:
commit 3e52259264832dc8c8b94c91561f072ab1d192d8
Author: Lekensteyn lekenst...@gmail.com
Date: Tue Jun 26 00:36:24 2012 +0200
i915: initialize CADL in opregion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reopening because the patch had to be dropped - it caused regressions.
The issues are now root-caused (it simply brought a pre-existing bug to
light), but we first need to fix these bugs before I can merge the cadl
patch again.
Please do not close this bug before the cadl patch has landed in drm-
On Fri, Jun 29, 2012 at 5:08 PM, bugzilla-dae...@freedesktop.org wrote:
Have you already found out the root cause?
Yep, see Message-ID: 20120629144850.GB5463@phenom.ffwll.local on
dri-devel and http://cgit.freedesktop.org/~danvet/drm/log/?h=cpu_edp-abomination
for the totally hackish patches
On Tue, Jul 24, 2012 at 10:19 AM, bugzilla-dae...@freedesktop.org wrote:
--- Comment #10 from XiongZhang xiong.y.zh...@intel.com 2012-07-24 08:19:58
UTC ---
In the patch code, it treat CADL and DIDL as the same, but from spec, they are
different: DIDL is Supported Display Devices ID List and
Needinfo again, we need someone to actually test this on the latest
kernels ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137234
Title:
[i945] Second display not enabled with intel video driver
Np, and thanks for the update ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956046
Title:
intel driver fails to use dual-link LVDS if lid is down at boot
To manage notifications about this bug
Can you please try the modeset-rework branch from my personal git repo
at:
http://cgit.freedesktop.org/~danvet/drm
Among other things, this undoes the offending commit in a rather
through-rough manner.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Everyone please retest with latest drm-intel-fixes from
http://cgit.freedesktop.org/~danvet/drm-intel
I've just merged a bunch of duct-tapes for this issue. For those who can
only reproduce the hangs with rc6 enabled, please also try reenabling
that with i915.i915_enable_rc6=1.
--
You received
*** Bug 57122 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1081009
Title:
[arrandale] GPU lockup IPEHR: 0x0222
To manage notifications about
*** Bug 56916 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1081009
Title:
[arrandale] GPU lockup IPEHR: 0x0222
To manage notifications about
*** Bug 57136 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1081009
Title:
[arrandale] GPU lockup IPEHR: 0x0222
To manage notifications about
Created attachment 73560
write mbox regs twice on snb
Another piece of magic which might help. Please test this patch and the
one from Chris (Read back semaphore mboxes after update) separately
and report back whether anything changes.
--
You received this bug notification because you are a
Created attachment 73577
write mbox regs twice on snb, v2
Now actually the right patch attached, the old one didn't compile ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041790
Title:
1 - 100 of 161 matches
Mail list logo
