Bug #1837683 “Screen stops updating after about 8 hours - (EE) m...” : Bugs : xorg-server package : Ubuntu

Revision history for this message

Alex Tu (alextu) wrote on 2019-07-24:

#1

CurrentDmesg.txt Edit (73.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (11.9 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (1.8 MiB, text/plain; charset="utf-8")
Lspci.txt Edit (17.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (346 bytes, text/plain; charset="utf-8")
MonitorsUser.xml.txt Edit (5.4 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (10.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (289 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (6.8 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (8.6 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (201.3 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (44.3 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (163.4 MiB, text/plain; charset="utf-8")
Xrandr.txt Edit (25.5 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (24.3 KiB, text/plain; charset="utf-8")

Daniel van Vugt (vanvugt) on 2019-07-24

affects:	xorg (Ubuntu) → xorg-server (Ubuntu)
summary:	- Xorg freeze + Screen stops updating after about 8 hours - (EE) modeset(0): present + flip failed
Changed in xorg-server (Ubuntu):
importance:	Undecided → High

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2019-07-24:

#2

When the problem is happening, does the kernel log show any problems? (run: dmesg)

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2019-07-24:

#3

1. When the problem is happening, does the kernel log show any problems? (run: dmesg)

2. When the problem is happening, what do you get from running these commands?

ls -l /proc/`pidof Xorg`/fd | wc -l
ls -l /proc/`pidof Xorg`/fd

3. When the problem is happening, what do you get from:

ps auxw | grep Xorg

4. Please try the same test with "Ubuntu on Wayland" and tell us if it has the same bug.

Changed in xorg-server (Ubuntu):
status:	New → Incomplete

Revision history for this message

Alex Tu (alextu) wrote on 2019-07-24: Re: [Bug 1837683] Re: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed

#4

Download full text (5.2 KiB)

1. When the problem is happening, does the kernel log show any problems?
(run: dmesg)
When the problem is happening, the screen is black, so no easy to type
command. I can try ssh before reproducing, but might not soon, I need to
handover this machine to another guy today.

Before that, can you get message you need in syslog? or I can upload
kern.log for your reference.

2. When the problem is happening, what do you get from running these
commands?

ls -l /proc/`pidof Xorg`/fd | wc -l
ls -l /proc/`pidof Xorg`/fd

When the problem is happening, the screen is black, so no easy to type
command. I can try ssh before reproducing, but might not soon, I need to
handover this machine to another guy today.

Is there other way to get information you need in next boot? So that I can
provide more on current environment that next boot of issue happened.

3. When the problem is happening, what do you get from:

ps auxw | grep Xorg

Same response as 2.

4. Please try the same test with "Ubuntu on Wayland" and tell us if it
has the same bug.

This would be my lower priory, the target of my testing is to make sure end
user's experience on LTS.

Daniel van Vugt <email address hidden> 於 2019年7月24日週三上午10:30 寫道：

> 1. When the problem is happening, does the kernel log show any problems?
> (run: dmesg)
>
> 2. When the problem is happening, what do you get from running these
> commands?
>
> ls -l /proc/`pidof Xorg`/fd | wc -l
> ls -l /proc/`pidof Xorg`/fd
>
> 3. When the problem is happening, what do you get from:
>
> ps auxw | grep Xorg
>
> 4. Please try the same test with "Ubuntu on Wayland" and tell us if it
> has the same bug.
>
>
> ** Changed in: xorg-server (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1837683
>
> Title:
> Screen stops updating after about 8 hours - (EE) modeset(0): present
> flip failed
>
> Status in xorg-server package in Ubuntu:
> Incomplete
>
> Bug description:
> environment:
> - XPS-13-938
> - connect 5G ac wifi
> - disabled suspend in power setting
> - disabled blank screen in power setting
>
> steps:
> - play 4k video by chrome on youtube[1] overnight
>
> symptom:
> - after about 8 hours, the screen is black and keyboard and mouse can
> not wake up screen.
> - the audio of 4K video is still playing, I can hear that when screen
> is black.
> - magic key still work, so I can reboot system by magic key.
> - a repeat error message in syslog:
> "
> Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW)
> modeset(0): Page flip failed: Invalid argument
> Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (EE)
> modeset(0): present flip failed
> "
>
> [1] https://www.youtube.com/watch?v=pkKBXH2qc_I&t=11701s
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: xorg 1:7.7+19ubuntu7.1
> ProcVersionSignature: Ubuntu 4.15.0-1047.52-oem 4.15.18
> Uname: Linux 4.15.0-1047-oem x86_64
> ApportVersion: 2.20.9-0ubuntu7.7
> Architecture: amd64
> BootLog: Error: [Errno 13] Permission denied: '/var/log/...

1. When the problem is happening, does the kernel log show any problems?
(run: dmesg)
When the problem is happening, the screen is black, so no easy to type
command. I can try ssh before reproducing, but might not soon,  I need to
handover this machine to another guy today.

Before that, can you get message you need in syslog? or I can upload
kern.log for your reference.

2. When the problem is happening, what do you get from running these
commands?

ls -l /proc/`pidof Xorg`/fd | wc -l
   ls -l /proc/`pidof Xorg`/fd

When the problem is happening, the screen is black, so no easy to type
command. I can try ssh before reproducing, but might not soon,  I need to
handover this machine to another guy today.

Is there other way to get information you need in next boot? So that I can
provide more on current environment that next boot of issue happened.

3. When the problem is happening, what do you get from:

ps auxw | grep Xorg

Same response as 2.

4. Please try the same test with "Ubuntu on Wayland" and tell us if it
has the same bug.

This would be my lower priory, the target of my testing is to make sure end
user's experience on LTS.

Daniel van Vugt <daniel.van.vugt@canonical.com> 於 2019年7月24日 週三 上午10:30 寫道：

> 1. When the problem is happening, does the kernel log show any problems?
> (run: dmesg)
>
> 2. When the problem is happening, what do you get from running these
> commands?
>
>    ls -l /proc/`pidof Xorg`/fd | wc -l
>    ls -l /proc/`pidof Xorg`/fd
>
> 3. When the problem is happening, what do you get from:
>
>    ps auxw | grep Xorg
>
> 4. Please try the same test with "Ubuntu on Wayland" and tell us if it
> has the same bug.
>
>
> ** Changed in: xorg-server (Ubuntu)
>        Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1837683
>
> Title:
>   Screen stops updating after about 8 hours - (EE) modeset(0): present
>   flip failed
>
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   environment:
>    - XPS-13-938
>    - connect 5G ac wifi
>    - disabled suspend in power setting
>    - disabled blank screen  in power setting
>
>   steps:
>    - play 4k video by chrome on youtube[1] overnight
>
>   symptom:
>    - after about 8 hours, the screen is black and keyboard and mouse can
> not wake up screen.
>    - the audio of 4K video is still playing, I can hear that when screen
> is black.
>    - magic key still work, so I can reboot system by magic key.
>    - a repeat error message in syslog:
>   "
>   Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW)
> modeset(0): Page flip failed: Invalid argument
>   Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (EE)
> modeset(0): present flip failed
>   "
>
>   [1] https://www.youtube.com/watch?v=pkKBXH2qc_I&t=11701s
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-1047.52-oem 4.15.18
>   Uname: Linux 4.15.0-1047-oem x86_64
>   ApportVersion: 2.20.9-0ubuntu7.7
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Jul 24 09:47:59 2019
>   DistUpgraded: Fresh install
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a week
>   GpuHangReproducibility: Seems to happen randomly
>   GpuHangStarted: Within the last few days
>   GraphicsCard:
>    Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
>      Subsystem: Dell Device [1028:08af]
>   InstallationDate: Installed on 2019-07-20 (3 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   MachineType: Dell Inc. XPS 13 9380
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1047-oem
> root=UUID=77efb06b-1ce6-4749-a131-67f57aa8b21b ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 03/29/2019
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.3.2
>   dmi.board.name: 0KTW76
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.family: XPS
>   dmi.product.name: XPS 13 9380
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
>   version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
>   version.xserver-xorg-core: xserver-xorg-core N/A
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837683/+subscriptions
>

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2019-07-24:

#5

1. If there's a relevant message in the kernel log then if will be obvious -- filling it up. Though if you have a full syslog already then that might contain the answer, so yes please attach it.

2. I guess log in via ssh and stay logged in before the problem starts.

4. We still need to test Wayland as a confirmation that the problem is confined to Xorg. It's not a matter of Ubuntu not recommending Wayland, it's to help us triage and understand this bug so it can be assigned to the right package and communicated clearly to the right upstream project.

Revision history for this message

Alex Tu (alextu) wrote on 2019-07-24:

#6

syslog.no-screen-after-4k-overnight.tar.gz Edit (2.7 MiB, application/x-tar)

Revision history for this message

Alex Tu (alextu) wrote on 2019-07-24:

#7

kern.log Edit (2.7 MiB, application/octet-stream)

not see much fishy message in kerne.log, the only message around the time of issue happened is:
"
Jul 24 01:25:24 u-XPS-13-9380 kernel: [ 2201.963876] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
"

Revision history for this message

Alex Tu (alextu) wrote on 2019-07-24:

#8

collect some public bugs which look similar to this one:
- https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821059
- https://uwot.eu/blog/xorg-present-flip-failed/

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2019-07-24:

#9

Thanks!

Yes that kernel message happens just before the Xorg failure, so it sounds related.

Jul 24 01:21:56 u-XPS-13-9380 kernel: [ 1993.239046] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
...
Jul 24 01:25:24 u-XPS-13-9380 kernel: [ 2201.963876] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
Jul 24 01:25:24 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (EE) modeset(0): failed to set mode: Invalid argument
Jul 24 01:25:24 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (II) event10 - ELAN2934:00 04F3:2934: is tagged by udev as: Touchscreen
Jul 24 01:25:24 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (II) event10 - ELAN2934:00 04F3:2934: device is a touch device
Jul 24 01:25:24 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW) modeset(0): flip queue failed: Invalid argument
...

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2019-07-24:

#10

Though there's at least one other case where kernel failures happen just before Xorg failures:

Jul 24 01:09:40 u-XPS-13-9380 kernel: [ 1257.973610] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.196769] thunderbolt 0000:05:00.0: control channel starting...
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.196772] thunderbolt 0000:05:00.0: starting TX ring 0
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.196780] thunderbolt 0000:05:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1)
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.196782] thunderbolt 0000:05:00.0: starting RX ring 0
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.196790] thunderbolt 0000:05:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001)
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.197236] usb usb3: root hub lost power or was reset
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.197238] usb usb4: root hub lost power or was reset
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.530275] [drm:intel_dp_check_link_status [i915]] *ERROR* Failed to get link status
Jul 24 01:09:41 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (II) modeset(0): Allocate new frame buffer 5760x2160 stride
Jul 24 01:09:43 u-XPS-13-9380 wpa_supplicant[838]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-49 noise=-97 txrate=6000
Jul 24 01:09:43 u-XPS-13-9380 kernel: [ 1261.069294] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
Jul 24 01:09:44 u-XPS-13-9380 kernel: [ 1261.566585] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
Jul 24 01:09:44 u-XPS-13-9380 org.gnome.Shell.desktop[2345]: Window manager warning: Configuring CRTC 64 with mode 186 (1920 x 1080 @ 60.000000) at position 3840, 0 and transform 0 failed
Jul 24 01:09:44 u-XPS-13-9380 gnome-shell[2345]: g_array_unref: assertion 'array' failed
Jul 24 01:09:44 u-XPS-13-9380 gnome-shell[2345]: message repeated 2 times: [ g_array_unref: assertion 'array' failed]
Jul 24 01:09:44 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW) modeset(0): hotplug event: connector 68's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...

Though there's at least one other case where kernel failures happen just before Xorg failures:

Jul 24 01:09:40 u-XPS-13-9380 kernel: [ 1257.973610] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.196769] thunderbolt 0000:05:00.0: control channel starting...
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.196772] thunderbolt 0000:05:00.0: starting TX ring 0
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.196780] thunderbolt 0000:05:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1)
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.196782] thunderbolt 0000:05:00.0: starting RX ring 0
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.196790] thunderbolt 0000:05:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001)
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.197236] usb usb3: root hub lost power or was reset
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.197238] usb usb4: root hub lost power or was reset
Jul 24 01:09:41 u-XPS-13-9380 kernel: [ 1258.530275] [drm:intel_dp_check_link_status [i915]] *ERROR* Failed to get link status
Jul 24 01:09:41 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (II) modeset(0): Allocate new frame buffer 5760x2160 stride
Jul 24 01:09:43 u-XPS-13-9380 wpa_supplicant[838]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-49 noise=-97 txrate=6000
Jul 24 01:09:43 u-XPS-13-9380 kernel: [ 1261.069294] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
Jul 24 01:09:44 u-XPS-13-9380 kernel: [ 1261.566585] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
Jul 24 01:09:44 u-XPS-13-9380 org.gnome.Shell.desktop[2345]: Window manager warning: Configuring CRTC 64 with mode 186 (1920 x 1080 @ 60.000000) at position 3840, 0 and transform 0 failed
Jul 24 01:09:44 u-XPS-13-9380 gnome-shell[2345]: g_array_unref: assertion 'array' failed
Jul 24 01:09:44 u-XPS-13-9380 gnome-shell[2345]: message repeated 2 times: [ g_array_unref: assertion 'array' failed]
Jul 24 01:09:44 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW) modeset(0): hotplug event: connector 68's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...

Changed in xorg-server (Ubuntu):
status:	Incomplete → New
Changed in linux (Ubuntu):
importance:	Undecided → High

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2019-07-24:

#11

I wonder if using a different kernel helps?

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2019-07-24:

#12

Ah comment #10 seems to be related to connector 68 (an external DisplayPort/Thunderbolt). Whereas you reported this bug first without any external monitor connected.

Was the original 8 hour test with or without an external monitor?

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2019-07-24:

#13

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc1/

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2019-07-24: Status changed to Confirmed

#14

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Alex Tu (alextu) wrote on 2019-07-24: Re: [Bug 1837683] Re: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed

#15

Download full text (3.8 KiB)

The original 8 hour test without external monitor.
I removed all wired connection before testing.

Kai-Heng Feng <email address hidden> 於 2019年7月24日週三下午4:00 寫道：

> Please test latest mainline kernel:
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc1/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1837683
>
> Title:
> Screen stops updating after about 8 hours - (EE) modeset(0): present
> flip failed
>
> Status in linux package in Ubuntu:
> Confirmed
> Status in xorg-server package in Ubuntu:
> New
>
> Bug description:
> environment:
> - XPS-13-938
> - connect 5G ac wifi
> - disabled suspend in power setting
> - disabled blank screen in power setting
>
> steps:
> - play 4k video by chrome on youtube[1] overnight
>
> symptom:
> - after about 8 hours, the screen is black and keyboard and mouse can
> not wake up screen.
> - the audio of 4K video is still playing, I can hear that when screen
> is black.
> - magic key still work, so I can reboot system by magic key.
> - a repeat error message in syslog:
> "
> Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW)
> modeset(0): Page flip failed: Invalid argument
> Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (EE)
> modeset(0): present flip failed
> "
>
> [1] https://www.youtube.com/watch?v=pkKBXH2qc_I&t=11701s
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: xorg 1:7.7+19ubuntu7.1
> ProcVersionSignature: Ubuntu 4.15.0-1047.52-oem 4.15.18
> Uname: Linux 4.15.0-1047-oem x86_64
> ApportVersion: 2.20.9-0ubuntu7.7
> Architecture: amd64
> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
> CompositorRunning: None
> CurrentDesktop: ubuntu:GNOME
> Date: Wed Jul 24 09:47:59 2019
> DistUpgraded: Fresh install
> DistroCodename: bionic
> DistroVariant: ubuntu
> ExtraDebuggingInterest: Yes
> GpuHangFrequency: Several times a week
> GpuHangReproducibility: Seems to happen randomly
> GpuHangStarted: Within the last few days
> GraphicsCard:
> Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
> Subsystem: Dell Device [1028:08af]
> InstallationDate: Installed on 2019-07-20 (3 days ago)
> InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
> MachineType: Dell Inc. XPS 13 9380
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1047-oem
> root=UUID=77efb06b-1ce6-4749-a131-67f57aa8b21b ro quiet splash vt.handoff=1
> SourcePackage: xorg
> Symptom: display
> Title: Xorg freeze
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 03/29/2019
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: 1.3.2
> dmi.board.name: 0KTW76
> dmi.board.vendor: Dell Inc.
> dmi.board.version: A00
> dmi.chassis.type: 10
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
> dmi.product.family: XPS
> dmi.product.name: XPS 13 9380
> dmi.sys.vendor: Dell Inc.
> version....

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	High	Unassigned
	xorg-server (Ubuntu)	Expired	High	Unassigned

Ubuntu
xorg-server package

Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Changed in xorg-server (Ubuntu):
status:	Incomplete → Expired

Ubuntuxorg-server package

Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
xorg-server package