If the hardware issues a hotplug irq when the cable is still connected,
there's not much the driver can do, really. We check the link on
hotplug, it's still there, do nothing. The HDMI live status checks that
have been merged *might* help a bit, but otherwise, I'm closing as
WONTFIX.
--
You
Everyone hitting the issue, please attach
/sys/kernel/debug/dri/0/i915_vbt (or if that doesn't exist,
i915_opregion).
Mika, just an idea... please check the vswing/pre-emph values in VBT.
I'm not sure if we parse them in either the driver or intel_bios_reader.
Check the VBT spec. Perhaps the VBT
(In reply to Daniel Vetter from comment #126)
> (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
(In reply to Sander Eikelenboom from comment #250)
> Is there a way to get off the CC-list of this slightly depressing kind of
> "catch-all" bug ?
CC list is at the top right corner. Choose the address, tick "Remove
selected CCs", and hit Save Changes.
I've done this for you now.
--
You
(In reply to Sander Eikelenboom from comment #250)
> Is there a way to get off the CC-list of this slightly depressing kind of
> "catch-all" bug ?
CC list is at the top right corner. Choose the address, tick "Remove
selected CCs", and hit Save Changes.
I've done this for you now.
--
You
(In reply to John from comment #102)
> Given Luka Karinja's results, I checked my kernel args to see if something
> else could account for my results. I found - i915.i915_enable_rc6=1
> i915.lvds_downclock=1 i915.semaphores=1 i915.i915_enable_fbc=1.
i915.i915_enable_rc6 and i915.i915_enable_fbc
(In reply to michel.verbist from comment #7)
> And my sound works again.
>
> Thanks for everything.
Awesome, thanks, closing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
(In reply to Robert Ancell from comment #1)
> We are currently working around this issue in Ubuntu 15.04 by reverting that
> one commmit.
That one commit being
commit 7d9a74622e5a936e4860fcef8358619bf59adae8
Author: Chris Wilson
Date: Mon Jun 15 14:16:34 2015 +0100
sna: Be robust in
(In reply to matthias.a.lee from comment #23)
Please let me know if I can be of any assistance in debugging this.
Please try this patch http://patchwork.freedesktop.org/patch/50675
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
(In reply to matthias.a.lee from comment #27)
Is there a build including that patch or will I have to build it myself?
As an upstream we don't provide builds, you're expected to be able to
apply and test patches. Sometimes your distro developers may be able to
help.
--
You received this bug
(In reply to Oleksij Rempel from comment #139)
New Bug is 89578
Many thanks Oleksij. I'm resolving this as dupe of the new one (usually
we'd go about this the other way round) so we have links both ways.
*** This bug has been marked as a duplicate of bug 89578 ***
--
You received this bug
(In reply to Oleksij Rempel from comment #137)
I'm ok with it.
Should i open new bug, you open it with needed description?
I would really appreciate you doing it, so you describe your symptoms,
instead of me putting words in your mouth. Thanks.
--
You received this bug notification because
Looking at this bug for the umpteent time, I would suggest closing this
one, RESOLVED WESUCK, and starting with a clean slate by filing a new
bug against v4.0-rc1 or drm-intel-nightly. There's too much baggage here
for anyone to look at this with fresh eyes, or if they were fresh while
starting
(In reply to comment #14)
Created attachment 95147 [details] [review]
drm/i915/sdvo: Fix LVDS connector status detection
Aitor, please try Chris' patch on top of a recent kernel and report
back.
--
You received this bug notification because you are a member of Desktop
Packages, which is
commit ca79d888eb63cdacf80653ae23ce8f7d9ac52c68
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Fri Jun 6 10:22:29 2014 +0100
drm/i915: Reorder semaphore deadlock check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in
commit ca79d888eb63cdacf80653ae23ce8f7d9ac52c68
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Fri Jun 6 10:22:29 2014 +0100
drm/i915: Reorder semaphore deadlock check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Fix pushed to drm-intel-fixes as
commit 94b93bc0093a37230ea7a0e91f04bfce677c430f
Author: Ville Syrjälä ville.syrj...@linux.intel.com
Date: Thu May 8 15:09:19 2014 +0300
drm/i915: Increase WM memory latency values on SNB
Thanks for the report.
--
You received this bug notification
(In reply to comment #57)
Fix pushed to drm-intel-fixes as
commit e95a2f7509f5219177d6821a0a8754f93892ca56
Author: Ville Syrjälä ville.syrj...@linux.intel.com
Date: Thu May 8 15:09:19 2014 +0300
drm/i915: Increase WM memory latency values on SNB
Thanks for the report.
--
You
I posted Ville's patch for review [1]. Some further work is needed.
[1] http://mid.gmane.org/1395392448-6337-1-git-send-email-
jani.nik...@intel.com
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
(In reply to comment #40)
Created attachment 94766 [details] [review]
drm/i915: Increase WM memory latency values on SNB with high pixel clock
This patch should make the driver automagically increase the latency values
when encoutering a high resolution display. Please test and report back
Timeout.
Michael, are you stills seeing the issue with later kernels? There seems
to have been some back and forth with the patch referenced by Chris in
comment #6 - please try 3.13-rc1 or later.
--
You received this bug notification because you are a member of Desktop
Packages, which is
(In reply to comment #124)
Created attachment 87441 [details]
dmesg-3.12.0-rc4-00468-g16b4e9b
Start with previously attached VGA. Both displays seems to be detected, and
listed by xrandr. But DP is blank with backlight on.
And does intel_iommu=igfx_off still fix this? If it does, please
(In reply to comment #122)
Created attachment 87403 [details]
dmesg-3.12.0-rc4-00468-g16b4e9b
Please do the same with drm.debug=0xe module parameter. Sorry I forgot
to mention this before. Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is
(In reply to comment #10)
Oh, an sdvo lvds output. That explains a lot (dmesg with debug output was
key, Xorg.log is pretty irrelevant here). I'm looking into a fix.
Daniel, ping for the fix. ;D
--
You received this bug notification because you are a member of Desktop
Packages, which is
24 matches
Mail list logo
