(In reply to Chris Rainey from comment #119)
> Confirming that "intel_idle.max_cstate=1" has solved my complete freeze
> issues on Bay Trail running Linux 4.1.13(Slackware64-current(pre-4.2)
> formerly running Ubuntu 15.04/15.10 with stock kernels).
>
> Thanx for all the hard-work and
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
(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
Workaround is now merged into drm-intel-nightly, should land in 3.19
commit 14a369b6c9bdb40cebdac5a248321a05119fe02b
Author: Daniel Vetter daniel.vet...@ffwll.ch
Date: Thu Nov 20 09:26:30 2014 +0100
drm/i915: Pin tiled objects for L-shaped configs
Note that this is v2, v1 was a bit
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok I've finally gotten around to polish Chris' patch and update
testcase:
http://patchwork.freedesktop.org/patch/37073/
As soon as I have a few tested-by reports I'll pull this in, so please
go wild. Patch applies on top of latest drm-intel-nightly.
--
You received this bug notification
*** Bug 79675 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/1140716
Title:
[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on
Yeah I guess that's it, time to give up on this one. Wiggling the mouse
or running with wayland should fix this.
Thanks for reporting this bug and testing ideas, sorry that we couldn't
make this work :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251065
Title:
HP Mini 1000 fails to resume from suspend
*** Bug 79675 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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339939
Title:
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
First hit on google for kernel besicting ;-)
https://wiki.ubuntu.com/Kernel/KernelBisection
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282867
Title:
Many bugs in rendering with lockups, likely
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282867
Title:
Many bugs in rendering with lockups, likely caused by SNA
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
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
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.
(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
(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
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
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
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 #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 #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 #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 #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 #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 #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 #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 #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
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
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:
(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
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
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.
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
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
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
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
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
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
*** 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
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
--- 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
(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
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:
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
(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:
On Fri, Dec 28, 2012 at 3:31 AM, bugzilla-dae...@freedesktop.org wrote:
--- Comment #8 from Daniel Gnoutcheff dan...@gnoutcheff.name ---
Reported to Ubuntu kernel team at:
https://bugs.launchpad.net/linux/+bug/1094173
If the patch works on 3.7 you only need to send the commit sha1 (in
the
Ok, sounds like the original issue was a combination of busted hw/bios,
and we're robbed of any chances to do further debug :( Thanks for
reporting, I'll close this now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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]
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
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
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
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
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
Revert merged to -fixes:
commit 2f4f649a69a9eb51f6e98130e19dd90a260a4145
Author: Jani Nikula jani.nik...@intel.com
Date: Mon Nov 12 14:33:44 2012 +0200
drm/i915: do not ignore eDP bpc settings from vbt
Please yell if this is still an issue for you.
--
You received this bug notification
Loki, if you have a regression with i830M dvo support, please file a new
bug report. If it's just lack of support for a specific DVO chipset, we
can't really help you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
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
Created attachment 67628
disable all hdmi modes
Can you please test this quick debug hack to disable all hdmi modes? I
suspect that the hotplug detection we regularly do causes (eventually)
some havoc. Or at least we've had similar bugs, so better check this
first.
--
You received this bug
(In reply to comment #12)
I added the patch to the distro kernel (based on 3.2.29), and then after
maybe an hour of uptime I got a full system lockup, and after maybe half a
minute the monitor powered off.
That's pretty much guaranteed to be a different issue ;-) The question
is whether the
Hm, it's rather strange that -nightly worked, then broke again for you.
Do you still have the commits of the respective nigthly versions you've
tested? We need to full commit since -nightly gets rebuilt every time I
push a patch ...
--
You received this bug notification because you are a member
Actually I really prefer if you file a new bug for the new issue. It is
really confusing when half the bug report is about one issue and the
other half about something completely different.
Please attach a new dmesg and the video (or a link to it) to the new
report and add a link here.
--
You
The fix has landed in 3.5, if you want it in 3.4 you can submit it to
the stable team, reference the commit and this bug report here.
commit b03543857fd75876b96e10d4320b775e95041bb7
Author: Takashi Iwai ti...@suse.de
Date: Tue Mar 20 13:07:05 2012 +0100
drm/i915: Check VBIOS value for
Dave Airlie has found a little setup sequence issue for edp. Can you
please test the latest drm-intel-nightly branch from
http://cgit.freedesktop.org/~danvet/drm-intel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yep, this is an issue with the kernel modeset code in the drm/i915.ko
driver. But this bug is in the right bugzilla, we also handle the kernel
issues for the intel driver here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Patch merged (again) to drm-intel-next-queued:
commit 036223401d50594c35fc5f7eafdbd2ddbe3ec921
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,
I think it'd be much better to figure out the root cause and fix it -
since likely these rc6 issues don't have anything to do with these
models specifically, we just haven't figured out yet what the real
problem is.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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,
*** Bug 52042 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/806032
Title:
Fn + F[89] does not work for controlling brightness on Clevo laptops
Can you please get the latest git version of intel-gpu-tools and grab
the another reg dump with the magic workaround done, so that everything
works with i915.ko kms enabled?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My modeset-rework patchki has a few fixes for handling cpu eDP, please
test the modeset-rework git branch at
http://cgit.freedesktop.org/~danvet/drm
Nick Coghlan: There's a decent chance you have a different issue, can
you please file a separate bug with the usual information? Untangle this
bug
Can you please retest with 3.6-rc kernel? Just to ensure that we're not
hunting a duplicate here (since we've fixed quite a few issues around
audio support recently).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So then let's just close this as fixed, proper patch is merged:
commit e77166b5a653728f312d07e60a80819d1c54fca4
Author: Daniel Vetter daniel.vet...@ffwll.ch
Date: Fri Mar 30 22:14:05 2012 +0200
drm/i915: properly clear SSC1 bit in the pch refclock init code
--
You received this bug
1 - 100 of 161 matches
Mail list logo