[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bug
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launc
Thanks. Please ensure you don't have any external monitor plugged in
while diagnosing this bug as it seems to have caused some confusion.
Per comment #13, please test latest mainline kernel which is now:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc2/
** Changed in: xorg-server (Ubuntu)
** Tags added: ubuntu-certified
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1837683
Title:
Screen stops updating after about 8 hours - (EE) modeset(0): present
flip failed
To manage
The original 8 hour test without external monitor.
I removed all wired connection before testing.
Kai-Heng Feng 於 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
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc1/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1837683
Title:
Screen stops updating after abou
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?
--
You received this bug notification because you are a member o
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 :0
I wonder if using a different kernel helps?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1837683
Title:
Screen stops updating after about 8 hours - (EE) modeset(0): present
flip faile
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 t
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/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu
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 i
** Attachment added: "syslog.no-screen-after-4k-overnight.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837683/+attachment/5278844/+files/syslog.no-screen-after-4k-overnight.tar.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subsc
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 Wayla
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 ge
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:
p
16 matches
Mail list logo
