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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1751268
Title:
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1251065
Title:
HP Mini 1000 fails to resume
(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 Kernel
Packages, which is subscribed to linux in Ubuntu.
(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 Kernel
Packages, which is
(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
commit 2dfb0b816d224379efc534764388745c474abeb4
Author: Jani Nikula <jani.nik...@intel.com>
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 Kernel
Packages, which is subs
(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 Kernel
Packages, which is subscribed to
(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 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
*** Bug 92187 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/1496433
Title:
Error in i915 driver
Status in Linux:
Fix Released
Status
(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
(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
(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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1504584
Title:
As of kernel 4.3-rc1 system will not stay
*** Bug 90381 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/1420290
Title:
WARNING: CPU: 0 PID: 2517 at
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]
(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 different
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
(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 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
(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 Kernel
(In reply to comment #0)
Copied from launchpad.
What's the launchpad 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/1315369
Title:
Log in not available after lock screen with
(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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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 Kernel
Packages, which is
Timeout, please re-test on current drm-intel-nightly.
--
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 from suspend
Status in The Linux
Fixed by
commit ece4a17d237a79f63fbfaf3f724a12b6d500555c
Author: Jiri Kosina jkos...@suse.cz
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
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 Kernel
Packages, which is subscribed to linux 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 Kernel
Packages, which is subscribed to linux in
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 Kernel
Packages, which is subscribed to linux
(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
(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 me and
(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 running
(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 linux
(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.
Kernel
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1275794
Title:
Lenovo T440s freezes
(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 #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 sent
(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
(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 this thread:
(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 #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 hang.
(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:
commit
(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 Kernel
Packages, which is
(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 #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
:)
Did you
(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 received
(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 Kernel
Packages, which is subscribed to
(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_config
(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 have an
(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 #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
(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 Kernel
Packages, which is
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1195483
Title:
Installation, Live and Check disc do not start
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 Kernel
Packages, which is
57 matches
Mail list logo
