Native mode 2560x1080 is randomly unavailable on some boots

Bug #1859071 reported by Tizzy on 2020-01-09
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned

Bug Description

$ lsb_release -rd
Description: Ubuntu 19.10
Release: 19.10
$ apt-cache policy gdm3
gdm3:
  Installed: 3.34.1-1ubuntu1
  Candidate: 3.34.1-1ubuntu1
  Version table:
 *** 3.34.1-1ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
        100 /var/lib/dpkg/status
$ apt-cache policy lightdm
lightdm:
  Installed: 1.30.0-0ubuntu1
  Candidate: 1.30.0-0ubuntu1
  Version table:
 *** 1.30.0-0ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
        100 /var/lib/dpkg/status
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)

I have a 3rd gen Intel laptop with only Ubuntu 19.10 installed, and a monitor attached via DisplayPort. The monitor has a native resolution of 2560x1080. When I power on my laptop, it is seemingly random whether one of the three following situations occurs.
1. Displays at the proper native resolution of 2560x1080,
2. Displays at 1600x1200 but not let me select a higher resolution in display settings, or
3. The display will fail to connect and stay blank (when I enter display settings it will be on "Single Monitor" mode, but from there I can enable Join Displays and set it to its native resolution).

Please note I selected "I don't know" instead of gdm3 or lightdm since i've been having this issue since before installing/switching to lightdm.

Please let me know what additional information I can provide at this time.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: Fresh install
DistroCodename: eoan
DistroRelease: Ubuntu 19.10
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f7]
InstallationDate: Installed on 2020-01-05 (9 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 2478A44
Package: xorg-server (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=5b93649d-7f54-41f8-85e1-dc9d5d494872 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Tags: eoan ubuntu
Uname: Linux 5.3.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 08/23/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G3ET96WW(2.56)
dmi.board.asset.tag: Not Available
dmi.board.name: 2478A44
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG3ET96WW(2.56):bd08/23/2013:svnLENOVO:pn2478A44:pvrThinkPadL530:rvnLENOVO:rn2478A44:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad L530
dmi.product.name: 2478A44
dmi.product.sku: LENOVO_MT_2478
dmi.product.version: ThinkPad L530
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: Fresh install
DistroCodename: eoan
DistroRelease: Ubuntu 19.10
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f7]
InstallationDate: Installed on 2020-01-05 (9 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 2478A44
Package: xorg-server (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=5b93649d-7f54-41f8-85e1-dc9d5d494872 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Tags: eoan ubuntu
Uname: Linux 5.3.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 08/23/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G3ET96WW(2.56)
dmi.board.asset.tag: Not Available
dmi.board.name: 2478A44
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG3ET96WW(2.56):bd08/23/2013:svnLENOVO:pn2478A44:pvrThinkPadL530:rvnLENOVO:rn2478A44:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad L530
dmi.product.name: 2478A44
dmi.product.sku: LENOVO_MT_2478
dmi.product.version: ThinkPad L530
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1859071/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → xorg (Ubuntu)
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1859071

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

tags: added: disco
affects: xorg (Ubuntu) → xorg-server (Ubuntu)
Changed in xorg-server (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected eoan ubuntu
description: updated
Tizzy (salterio) wrote : DpkgLog.txt

apport information

apport information

apport information

Tizzy (salterio) wrote : Lspci.txt

apport information

Tizzy (salterio) wrote : Lsusb.txt

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Tizzy (salterio) wrote : UdevDb.txt

apport information

Tizzy (salterio) wrote : XorgLog.txt

apport information

apport information

Tizzy (salterio) wrote : Xrandr.txt

apport information

apport information

Thanks. Those attachments appear to have been created when the correct resolution was in use:

[ 6.555] (II) modeset(0): Output DP-2 using initial mode 2560x1080 +1366+0

So they don't demonstrate the bug. I wonder can you please reproduce the bug such that the wrong resolution is in use and then run 'apport-collect 1859071' again?

summary: - Secondary monitor unpredictable behavior at boot
+ Secondary monitor unpredictable behavior at boot (Ivy Bridge,
+ DisplayPort)

apport information

description: updated
Tizzy (salterio) wrote : DpkgLog.txt

apport information

apport information

apport information

Tizzy (salterio) wrote : Lspci.txt

apport information

Tizzy (salterio) wrote : Lsusb.txt

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Tizzy (salterio) wrote : UdevDb.txt

apport information

Tizzy (salterio) wrote : XorgLog.txt

apport information

apport information

Tizzy (salterio) wrote : Xrandr.txt

apport information

apport information

Download full text (4.7 KiB)

Thanks.

Comment #36 shows the bug:

DP-2 connected 1600x900+1366+0 (0x95) normal (normal left inverted right x axis y axis) 798mm x 334mm

Comment #34 does not show the bug:

[ 6.555] (II) modeset(0): Output DP-2 using initial mode 2560x1080 +1366+0

So I wonder if those are from different logins? Either way, when it's using the wrong mode of 1600x900 it's also showing an EDID which decodes nicely and includes 2560x1080:

---- Decoded from the EDID in comment #36 ----

EDID version: 1.4
Manufacturer: GSM Model 30485 Serial Number 297684
Made in week 2 of 2019
Digital display
10 bits per primary color channel
DisplayPort interface
Maximum image size: 80 cm x 34 cm
Gamma: 2.20
DPMS levels: Standby
Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2
Default (sRGB) color space is primary color space
First detailed timing includes the native pixel format and preferred refresh rate
Display is continuous frequency
Color Characteristics
  Red: 0.6513, 0.3320
  Green: 0.3066, 0.6308
  Blue: 0.1503, 0.0595
  White: 0.3134, 0.3291
Established Timings I & II
    640x480 59.940 Hz 4:3 31.469 kHz 25.175 MHz (DMT)
    640x480 75.000 Hz 4:3 37.500 kHz 31.500 MHz (DMT)
    800x600 60.317 Hz 4:3 37.879 kHz 40.000 MHz (DMT)
    800x600 75.000 Hz 4:3 46.875 kHz 49.500 MHz (DMT)
    832x624 74.551 Hz 4:3 49.726 kHz 57.284 MHz (Apple)
   1024x768 60.004 Hz 4:3 48.363 kHz 65.000 MHz (DMT)
   1024x768 75.029 Hz 4:3 60.023 kHz 78.750 MHz (DMT)
   1280x1024 75.025 Hz 5:4 79.976 kHz 135.000 MHz (DMT)
   1152x870 75.062 Hz 192:145 68.681 kHz 100.000 MHz (Apple)
Standard Timings
   1152x864 59.959 Hz 4:3 53.783 kHz 81.750 MHz (EDID 1.4 source: CVT)
   1152x864 60.000 Hz 4:3 53.700 kHz 81.624 MHz (EDID 1.3 source: GTF)
   1280x1024 60.020 Hz 5:4 63.981 kHz 108.000 MHz (DMT)
   1280x720 60.000 Hz 16:9 45.000 kHz 74.250 MHz (DMT)
   1600x900 60.000 Hz 16:9 60.000 kHz 108.000 MHz (DMT, RB)
   1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz (DMT)
   1920x1080 60.000 Hz 16:9 67.500 kHz 148.500 MHz (DMT)
   1280x800 59.810 Hz 16:10 49.702 kHz 83.500 MHz (DMT)
   1920x1080 74.906 Hz 16:9 84.643 kHz 220.750 MHz (EDID 1.4 source: CVT)
   1920x1080 75.000 Hz 16:9 84.600 kHz 220.637 MHz (EDID 1.3 source: GTF)
Detailed mode: Clock 181.250 MHz, 798 mm x 334 mm
               2560 2608 2640 2720 ( 48 32 80)
               1080 1083 1093 1111 ( 3 10 18)
               +hsync -vsync
               VertFreq: 59.978 Hz, HorFreq: 66.636 kHz
Detailed mode: Clock 148.500 MHz, 798 mm x 334 mm
               1920 2008 2052 2200 ( 88 44 148)
               1080 1084 1089 1125 ( 4 5 36)
               +hsync +vsync
               VertFreq: 60.000 Hz, HorFreq: 67.500 kHz
Display Range Limits
  Monitor ranges (Bare Limits): 40-75 Hz V, 90-90 kHz H, max dotclock 240 MHz
Display Product Name: LG HDR WFHD
Has 1 extension block
Checksum: 0x97

----------------

CTA-861 Extension Block Revision 3
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
26 bytes of CTA data blocks
  Audio Data Block
    Lin...

Read more...

summary: - Secondary monitor unpredictable behavior at boot (Ivy Bridge,
- DisplayPort)
+ Modesetting randomly fails to offer modes available in the EDID (CTA-861
+ Extension Block Revision 3)
Changed in xorg-server (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → High

Please try logging into "Ubuntu on Wayland" and tell us if you experience similar problems there.

summary: - Modesetting randomly fails to offer modes available in the EDID (CTA-861
- Extension Block Revision 3)
+ Modesetting randomly fails to offer all modes available in the EDID
Changed in xorg-server (Ubuntu):
status: Triaged → Incomplete
Tizzy (salterio) wrote :

Hello Daniel,
Today the issue occured again, so I was sure to login with "Ubuntu on Wayland", but the issue persisted until I rebooted (as usual). Please keep in mind the screen is in the wrong resolution while on the login screen, as well.
Let me know if i can do anything else to help.

Daniel van Vugt (vanvugt) wrote :

Thanks!

The login screen uses Wayland so that's also a good test in itself. If the issue affects the Wayland backend then it sounds like this is a kernel or hardware problem. To check that, next time the issue happens, please run:

  grep . /sys/class/drm/*/modes > modes.txt

and then attach the file 'modes.txt' here.

---

Just a guess: The problem might be timeouts on the i2c bus waiting for the monitor to return its EDID. So that could happen randomly. In that case, maybe try a different DisplayPort cable if you can.

Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → High
Tizzy (salterio) wrote :

It took me many reboots, but i finally got it for you! =)

Daniel van Vugt (vanvugt) wrote :

Great, thanks. Indeed the native mode of the monitor is missing from that list so this is a kernel or hardware problem.

I assume the same command /usually/ shows more modes..?

no longer affects: xorg-server (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
summary: - Modesetting randomly fails to offer all modes available in the EDID
+ Native mode 2560x1080 is randomly unavailable on some boots

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Tizzy (salterio) wrote :

Yes, it usually shows more modes, notably with some duplicates (different refresh rates, perhaps)?
it basically looks like the modes.txt i already posted except also with this at the top:

/sys/class/drm/card0-DP-2/modes:2560x1080
/sys/class/drm/card0-DP-2/modes:2560x1080
/sys/class/drm/card0-DP-2/modes:2560x1080
/sys/class/drm/card0-DP-2/modes:1920x1080
/sys/class/drm/card0-DP-2/modes:1920x1080
/sys/class/drm/card0-DP-2/modes:1920x1080
/sys/class/drm/card0-DP-2/modes:1920x1080
/sys/class/drm/card0-DP-2/modes:1920x1080
/sys/class/drm/card0-DP-2/modes:1680x1050

Anyway, I wanted to comment that I was able to reproduce this bug on a fresh install of CentOS 8 on the same laptop, albeit only once and after waking the computer from suspend, instead of during boot. I did the same command to dump all the modes to a text file and saw the results were the same after waking that install from suspend. So, i'm assuming it's not a Ubuntu problem, instead it's either a hardware issue as you suggested it could be, or a Wayland issue - since this CentOS 8 install is also using Wayland to log in.

Daniel van Vugt (vanvugt) wrote :

I believe this is a kernel bug or a hardware fault. So that's why it's assigned to the kernel now.

This is not a Wayland issue since the same applies to Xorg, and we've confirmed in comment #42 that the problem is originating in the kernel.

The next step I think will be to play with different "i2c timeouts", which you can google. But I am guessing now and we need the help of the kernel team.

Kai-Heng Feng (kaihengfeng) wrote :

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

If it doesn't solve the issue, please file an upstream bug at intel graphics upstream:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs

To post a comment you must log in.