drm-tip works, nothing in dmesg to indicate failure. Pretty much the
only way to get progress is to get a bisect result.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751268
Title:
bionic desktop d
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 recei
I don't think Jesse will be working on this anymore...
Have you tried more recent kernels?
--
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
To
(In reply to Pranith Kumar from comment #55)
> Is this really resolved? The problem is gone, but I don't think anyone
> identified what is really causing the problem to occur.
In a perfect world we'd get to the roots of every problem, but in
reality we don't have the time to keep debugging issues
Thanks, closing. Please reopen or file new bugs if the problems persist.
(Please be careful about not reopening this one if you have bug 91393)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554613
Ti
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 v
(In reply to tigrangab from comment #18)
> Bug still exists in 4.6 rc1. Is there anything I can provide to help with
> this issue?
Did you bisect this to the same commit reported in comment #0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
(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 kerne
(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 receive
(In reply to Joakim Koed from comment #23)
> Just wanted to let you know (if you were unaware) this bug does also make
> the system freeze randomly. I have tried to figure out what triggers it, but
> it seems just random. If anything it happens after 2-3 hours of activity and
> then 2-5 mins idle?
(In reply to darkbasic from comment #26)
> When did you shut up the messages for the first time? I always saw them in
> every RC, including latest 4.4-rc8.
drm-next, not Linus' upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
commit 2dfb0b816d224379efc534764388745c474abeb4
Author: Jani Nikula
Date: Thu Jan 7 10:29:10 2016 +0200
drm/i915: shut up gen8+ SDE irq dmesg noise, again
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
(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 receive
(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 h
*** Bug 92187 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/1496433
Title:
Error in i915 driver
To manage notifications about this bug go to:
https:/
(In reply to Jonathan McDowell from comment #7)
> I have upgraded to 4.3-rc2 and have not so far been able to reproduce the
> problem. I will update here if I can do so.
Presumed fixed, please reopen if the problem reappears with 4.3-rc2 or
later.
--
You received this bug notification because yo
(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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458136
Title:
[MS-7823,
(In reply to Kim Carlsen from comment #16)
> When 4k resolution is working, these error message is still present in
> kernel.log. Maybe resolution issue is unrelated to IRQ issue
Please file that as a separate bug to not conflate this one, thanks.
--
You received this bug notification because yo
(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 handlin
(In reply to Doug Smythies from comment #7)
> (In reply to Jani Nikula from comment #6)
> > Did you double check the bisect by running both dc4be6071a24 and
> > dc4be6071a24^ ?
>
> Yes, of course, and I said so in my initial e-mail.
> Truth be known, this was my second b
Did you double check the bisect by running both dc4be6071a24 and
dc4be6071a24^ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504584
Title:
As of kernel 4.3-rc1 system will not stay in S3 suspend
(In reply to Timo Aaltonen from comment #0)
> Booting 4.3-rc1 or nightly on SKL-S results in
>
> [1.139104] [drm:i915_dump_device_info] i915 device info: gen=9,
> pciid=0x1912 rev=0x06 flags
> =need_gfx_hws,is_skylake,has_fbc,has_hotplug,has_llc,has_ddi,
> [1.139115] [drm:intel_detect_pch]
*** Bug 90381 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/1420290
Title:
WARNING: CPU: 0 PID: 2517 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/
Please try v4.2-rc7 or drm-intel-nightly branch of [1], drop all i915
module parameters (such as i915.enable_rc6 i915.enable_fbc
i915.lvds_downclock and i915.semaphores, they are not for regular use),
add drm.debug=14, attach dmesg all the way from early boot.
[1] http://cgit.freedesktop.org/drm-i
(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 no
(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 Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
(In reply to Christian Hartmann from comment #11)
> still present in:
> -> 3.19.5 and
> -> 4.0.0
...
> [3.935536] WARNING: CPU: 3 PID: 262 at drivers/gpu/drm/drm_irq.c:1130
> drm_wait_one_vblank+0x177/0x180()
> [3.935546] vblank wait timed out on crtc 0
Please observe that this is a dif
Please reopen if you can reproduce on v4.0-rc1 or later. The backport
request for v3.19.y has been sent, see comment #7, nothing more we can
do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432405
T
(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 not
(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 becaus
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 the
(In reply to D B from comment #33)
> I would do the testing, but I'm unable to successfully install the new
> kernel. It would be appreciated if someone could give me a walk-through of
> how to accomplish this.
I'm afraid that's beyond our scope here; please try to look at your
distro's documentat
(In reply to Daniel Vetter from comment #28)
> 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 ...
Ping for the testing.
--
You received this bug notification because you are a member of Ubuntu
B
(In reply to comment #6)
> (In reply to comment #0)
> > Copied from launchpad.
>
> What's the launchpad bug?
Sorry, saw that now in the see also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315369
Any idea if an adapter was used? One reporter at launchpad says the
problem is not present after switching from VGA to HDMI:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1315369/comments/63
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
(In reply to comment #0)
> Copied from launchpad.
What's the launchpad bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315369
Title:
Log in not available after lock screen with multi-monitor
T
Timeout, please re-test on current drm-intel-nightly.
--
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
To manage notifications about this bug g
Fixed by
commit ece4a17d237a79f63fbfaf3f724a12b6d500555c
Author: Jiri Kosina
Date: Thu Aug 7 16:29:53 2014 +0200
drm/i915: read HEAD register back in init_ring_common() to enforce
ordering
(In reply to comment #102)
> Will Linux 3.16.2 include this fix/workaround?
It will eventually be ba
(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 Ubuntu
Bugs, which is subscribe
commit ca79d888eb63cdacf80653ae23ce8f7d9ac52c68
Author: Chris Wilson
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
commit ca79d888eb63cdacf80653ae23ce8f7d9ac52c68
Author: Chris Wilson
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
(In reply to comment #57)
> Fix pushed to drm-intel-fixes as
commit e95a2f7509f5219177d6821a0a8754f93892ca56
> Author: Ville Syrjälä
> 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 notifica
Fix pushed to drm-intel-fixes as
commit 94b93bc0093a37230ea7a0e91f04bfce677c430f
Author: Ville Syrjälä
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 because you are a member of Ubuntu
B
So one or some of our fixes has indeed fixed the bug. If anyone wants to
reverse bisect from broken to first good, we'd be able to identify and
backport the fix(es) to stable kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
We've merged a number of patches that might affect this since the last
comments. Please try recent drm-intel-nightly branch and report back.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/126554
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12391
(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 ba
(In reply to comment #35)
> I notice that the bug hasn't been updated in a while, a patch that fixes the
> issue exists and can be integrated in the same way as bug 71049 (quirk-based
> bpp clamping bypass).
The fix for bug 71049 is specifically *not* quirk based.
> Can this patch be reviewed & i
(In reply to comment #147)
> Created attachment 94007 [details]
> dmesg with patch applied, old firmware
>
> I applied the patch on the FC20 3.12 kernel and although there was no
> freeze, I got some scary error messages in my kernel logs. See attached
> output. This is a Lenovo W540 laptop runnin
(In reply to comment #156)
> Additional datapoint since I just ran into this bug but haven't yet managed
> to upgrade the firmware.
>
> I am running Debian Testing right now on a new x240 with the ultradock. I
> was testing this and, just as gdm was about to start up, I docked the system.
>
> Ke
(In reply to comment #151)
> Do you know when there is an official new driver including this fix
> available on https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=13815
> or similar site (I for some reason cannot connect to the site right now, but
> I think it's where I got my last Intel lin
(In reply to comment #85)
> I care about getting this fixed, so I'm offering USD 100.00 via
> FreedomSponsors to the first person who fix it.
>
> Offer link:
> http://www.freedomsponsors.org/core/issue/433/sna-haswell-x-server-freezes-
> when-enabling-dp-at-docking-station
>
> You can also join m
(In reply to comment #114)
> Thanks, the logs confirm we are indeed receiving plenty of aux defer replies
> from the sink. I sent the patches to the list [1], on top of
> drm-intel-nightly (3.13 requires trivial backporting). I'm not too
> optimistic about them fixing the actual output, just the ha
(In reply to comment #129)
> It seems the hang is resolved with the dock firmware update (2.17) provided
> by Lenovo. As far as I am concerned I think this bug can be closed.
>From the kernel perspective it's fixed when we don't freeze the machine
even when a dock with buggy firmware is connected,
(In reply to comment #124)
> There seems to be still a problem enumerating the devices connected to the
> DP hub
We currently do not support MST (multistream) DP branch devices. If it
works for multiple monitors, great, but it's more or less by accident.
--
You received this bug notification bec
(In reply to comment #133)
> (In reply to comment #132)
> > I have got the following devices:
> >* T440s (Kernel 3.13.2)
> >* Dock (fw2.10)
> >* Dock (fw2.17)
> >
> > If I can provide additional logs, please give me infos on which scenarios
> > (/patches).
>
> Apply the patches from t
(In reply to comment #125)
> These patches did not work for me with my T440s. During bootup it hangs
> upon switch to FB. Once booted undocked, it hangs when docked and external
> monitor is enabled through xrandr.
Dmesg with drm.debug=0xe please.
--
You received this bug notification because
(In reply to comment #111)
> Tests:
> - boot without any connectors: hotplugging of all connectors works
> - boot once with each connector: works
>
> dmesg logs for both tests (with DP) following ...
Thanks, the logs confirm we are indeed receiving plenty of aux defer
replies from the sink. I sen
Created attachment 93781
drm/i915/dp: add max retries in native aux
Please try this for 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/1275794
Title:
Lenovo T440s freezes when connected
(In reply to comment #29)
> (In reply to comment #28)
> > Why "acpi_osi=" in kernel cmdline?
>
> Fixes a couple of other issues : Airplane mode key and Screen backlight
> control key (doesn't work otherwise, c.f.
> https://bugs.launchpad.net/ubuntu/+bug/1270661) Yeah, that laptop is a gift
> :)
D
(In reply to comment #27)
> Tried with 2014-01-28 nightly and didn't work (screen on boot, blank on
> resume from suspend).
> Output from dmesg with drm.debug=0xe added.
Why "acpi_osi=" in kernel cmdline?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
(In reply to comment #24)
> I just double checked again and yes with the commit before
Alberto, thanks for checking this.
(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
(In reply to comment #21)
> I just noticed the latest drm-intel-nightly (commit
> f27f16540be56813df2ebb8e1106dd5c258f07c3) has fixed the issue.
>
> After bisecting, it seems the blank screen issues I was getting after
> modesetting or suspend/resume have been fixed starting from commit:
>
> comm
(In reply to comment #0)
> Any sequence that turns off/on the panel (suspend/resume, modesetting)
> results in a blank screen.
Wait. Does this mean it works when you first boot it?
Does 'dmesg | grep intel_ddi_get_config' give you multiple results, with
possibly different output?
--
You receive
(In reply to comment #17)
> Does 'dmesg | grep intel_ddi_get_config' give you multiple results, with
> possibly different output?
*with* the patch from comment #15, if that wasn't clear.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(In reply to comment #9)
> I'm not the original reporter of the bug, I have an identical machine :
> UX302LG w/ the same issue: I'm the reporter of
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265544 that helped/led
> to this bugreport.
Thanks for verifying this, and apologies; we just
(In reply to comment #6)
> (In reply to comment #5)
> > BTW, kernel 3.13rc8 must be working.
>
> I just tried 3.13-rc8 from
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc8-trusty/ and it is
> NOT working : blank screen on boot.
Are you the original reporter of this bug? If not, do you h
(In reply to comment #13)
> Daniel,
>
> I'm already running drm-intel-nightly which includes that commit.
> That particular hack does indeed run (see attached dmesg log at the
> beginning) but the panel is still blank. I saw the same hack at
> intel_dp_get_config, but in my machine intel_dp_get_c
(In reply to comment #24)
> Now we find ourselves without uptodate information on what your bug is, so
> please do attach the full dmesg from the failure case.
Rodney, please post the full dmesg from the failure case. Since plenty
of time has passed, please use a later kernel. Thanks.
--
You rec
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 Ubuntu
Bugs, which is subscribed t
(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 Ubuntu
Bugs, which is subscri
(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
The upstream bug report is
https://bugzilla.kernel.org/show_bug.cgi?id=59841
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195483
Title:
Installation, Live and Check disc do not start on Asus ZenBo
Oleksij, if I may ask for another test round with current drm-intel-
nightly branch of git://people.freedesktop.org/~danvet/drm as there have
been some relevant fixes since we last heard from you. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
(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 Ubuntu
Bugs, which is subscribe
If you're having this problem on an Acer/eMachines/Packard Bell/Gateway
laptop, try booting with i915.invert_brightness=1 module parameter
(https://help.ubuntu.com/community/BootOptions). If it works, consider
filing an upstream bug on Product=DRI, Component=DRM/Intel
(https://01.org/linuxgraphics/
I've had the stubborn hard blocked phy0 rfkill problem on a Lenovo
s10-3t. Turning off the machine, removing the battery, unplugging the
power cable, and pressing and holding the power button for 30-40 seconds
to reset BIOS settings fixed it for me.
Source: http://blog.davidron.com/2012/03/lenovo-
(In reply to comment #13)
> (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?
BOOT_IMAGE=/vmlinuz-3.8.0-030800rc2-generic in the dmesg suggests so...
but there's no FDI link train errors and I don't spo
Please test and provide the requested info.
--
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 notifications about this bug go to:
htt
Please attach full dmesg from boot with drm.debug=0xe module parameter,
up to exhibiting the problem. Thanks.
--
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 worki
Related to https://bugzilla.kernel.org/show_bug.cgi?id=47641
Robert, please add the hex dump of your EDID from /sys/class/drm/*/edid,
where * is your display.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
81 matches
Mail list logo
