Resolved by kernel update per #17 and #18. Closing
** Changed in: linux (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384297
Title:
After system resume
I get this on my Dell XPS 13 9360:
$ uname -a
Linux blackhole 4.10.0-19-generic #21~16.04.1-Ubuntu SMP Fri Apr 7 08:20:02 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codenam
how about 16.04? It does not hang any more, but the message is still
repeated many times in the dmesg log:
[1.940071] [ cut here ]
[1.940109] WARNING: CPU: 1 PID: 6 at
/build/linux-Ay7j_C/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326
drm_wait_one_vblank+0x1b5/0x1c0 [
utopic has seen the end of its life and is no longer receiving any
updates. Marking the utopic task for this ticket as "Won't Fix".
** Changed in: linux (Ubuntu Utopic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I think I am having the same problem on Thinkpad x260. It hangs up
during suspend and last message in syslog is:
Mar 19 22:58:26 periplum kernel: [ 29.322099] CPU: 1 PID: 843 Comm: Xorg
Tainted: GW 4.2.0-34-generic #39-Ubuntu
Mar 19 22:58:26 periplum kernel: [ 29.322100] Hardwar
I've migrated to the LST Enablement Stack and after a few days agree
that this seems to have been resolved with the newer kernel and xorg
components (although it's hard to know for sure - on the 3.16 kernel I
think I would have had a problem by now, however).
That's for 3.19.0-26-generic #28~14.04
I cannot be 100% certain, but I am reasonably sure this particular
problem has vanished for me after I upgraded to the latest LTS
enablement stack (kernel 3.19 and newer Xorg components from vivid). I
still see some suspend related traces in kernel log, but they are not
the same, and in practice I
Unfortunately, I've recently found that switching to a TTY doesn't
always work, and sometimes the screen remains black no matter what is
done and a forced reboot is required.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I'm also having this issue on a new Lenovo X1 Carbon generation 3 (model
20BS CT01 WW). The screen will go black at random intervals and a
similar stacktrace is produced on dmesg. Switching to a TTY and back
(ctrl+alt+F1 and then back to ctrl+alt+f7, for example) returns to a
functional Xorg. This
Although not upstream, this looks like the Redhat/Fedora bug for the same issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1120901
** Bug watch added: Red Hat Bugzilla #1120901
https://bugzilla.redhat.com/show_bug.cgi?id=1120901
--
You received this bug notification because you are a membe
Actually, I seem to be getting these kernel warnings every time display
comes back from DPMS sleep, and not only resume from suspend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384297
Title:
Aft
Same issue on Dell E7440 (Intel HD 4400 Haswell) running Ubuntu 14.04
with upgraded kernel 3.16 (LTS enablement).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384297
Title:
After system resume, In
Is there an upstream for 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/1384297
Title:
After system resume, Intel i915 graphics hangs
To manage notifications about this bug go to:
https://
I just tried with the Vivid kernel (3.18.0) and had the same error. I
needed to restart lightdm to get things going again.
[ 65.108123] WARNING: CPU: 0 PID: 6 at
/build/buildd/linux-3.18.0/drivers/gpu/drm/i915/intel_display.c:5158
intel_modeset_check_state+0x6cd/0
x770 [i915]()
[ 65.108125]
** Changed in: linux (Ubuntu)
Importance: Critical => High
** Changed in: linux (Ubuntu)
Status: Fix Released => Triaged
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Utopic)
Importance: Undecided => High
** Changed
Ack, sorry everyone, I changed the status to "Fix Released" by accident
and now I can't change it back to "Triaged". Can someone change it back?
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384297
Title:
17 matches
Mail list logo
