Cannot use full resolution (2560x1440) of Dell U2715H

[Bryon Nevis]

While using Ubuntu 19.10 with either MATE or GNOME, I can use only 1920x1080 resolution instead of the full 2560x1440. If extra pixels are configured, they fall off the right side or bottom of the display and are not visible. Reproduced on Raspberry Pi 4 with 3GB max workaround.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: User Name 5.3.0-1008.9-raspi2 5.3.1
Uname: Linux 5.3.0-1008-raspi2 aarch64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: arm64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 10 18:18:23 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:

ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M video=HDMI-A-1:1920x1080@60 smsc95xx.macaddr=DC:A6:32:38:DF:15 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
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 N/A
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 N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Bryon Nevis (bnevis)]

Also noticed that v3d.ko is not included as one of the kernel modules int he build. This seems to cause Xorg to pick the VMware display driver instead of the Qualcom display driver.

[Sebastien Bacher (seb128)]

Thank you for your bug report, the previous comment seems to suggest it's a kernel issue?

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Bryon Nevis (bnevis)]

@Sebastien. I think the more likely root cause is that the Raspberry Pi firmware release (https://github.com/raspberrypi/firmware) consists of a 32-bit and 64-bit kernel, and a 32-bit-only userspace. For sure there are kernel modules missing (a reconciliation with the official kernel's config options may be in order?), but the larger problem may be the 32-bit Xorg shared libraries. I have doubts that just compiling the missing kernel module will fully resolve the issue.

[Hui Wang (hui.wang)]

For the missing of the module v3d.ko, we already have a bug to track it, and the v3d is enabled in the kernel from the next released kernel.

https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876

[Hui Wang (hui.wang)]

We are going to release a new kernel soon, right now it is in the proposed channel, Welcome to test with the new kernel:

edit the $rpi_rootfs/etc/apt/sources.list and add:
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse

boot the rpi board, then run:
sudo apt-get update
sudo apt install linux-image-5.3.0-1013-raspi2
sudo reboot

Then you could do the test with the proposed kernel.

At least the 1013 kernel fixed these bugs compared with 1012 kernel:
https://bugs.launchpad.net/bugs/1850876
https://bugs.launchpad.net/bugs/1852510

[Bryon Nevis (bnevis)]

 [ 20.005106] ieee80211 phy0: brcmf_cfg80211_scan: Connecting: status (3)
[ 22.175638] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI info frame
[ 35.824432] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI info frame
[ 59.528346] v3d fec00000.v3d: MMU error from client L2T (0) at 0x161000, pte invalid
[ 60.542090] v3d fec00000.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang.
[ 60.549816] v3d fec00000.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x0 0001000
[ 60.558638] v3d fec00000.v3d: MMU error from client L2T (0) at 0x9761000, pte invalid
[ 61.598102] v3d fec00000.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang.
[ 61.605839] v3d fec00000.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x0 0001000
[ 61.614690] v3d fec00000.v3d: MMU error from client L2T (0) at 0x9741000, pte invalid
[ 62.654095] v3d fec00000.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang.
[ 62.661828] v3d fec00000.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x0 0001000
[ 84.609153] v3d fec00000.v3d: MMU error from client L2T (0) at 0x54c1000, pte invalid
[ 84.617009] kernel BUG at arch/arm64/kernel/traps.c:405!
[ 84.622312] Internal error: Oops - BUG: 0 [#1] SMP
[ 84.625779] ------------[ cut here ]------------
[ 84.625784] ------------[ cut here ]------------
[ 84.625787] kernel BUG at arch/arm64/kernel/traps.c:405!
[ 84.627094] Modules linked in: bnep aufs overlay nls_ascii dm_multipath scsi_ dh_rdac scsi_dh_emc scsi_dh_alua vc4 drm_kms_helper snd_soc_core snd_compress sn d_seq_dummy ac97_bus snd_pcm_dmaengine snd_seq_oss snd_usb_audio snd_hwdep snd_u sbmidi_lib snd_seq_midi snd_pcm_oss snd_seq_midi_event btsdio snd_mixer_oss blue tooth snd_rawmidi joydev input_leds snd_pcm ecdh_generic ecc snd_seq brcmfmac sn d_seq_device snd_timer brcmutil bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) vc_sm_cm a(CE) v4l2_common snd videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 videobuf2_common fb_sys_fops syscopyarea sysfillrect videodev sysimgblt mc rasp berrypi_hwmon spidev rpivid_mem uio_pdrv_genirq uio sch_fq_codel ppdev lp parpor t ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_reco ...

[Bryon Nevis (bnevis)]

[ 22.661761] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI infoframe
[ 39.686565] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI infoframe
[ 70.888208] v3d fec00000.v3d: MMU error from client L2T (0) at 0x4f41000, pte invalid
[ 70.898755] kernel BUG at arch/arm64/kernel/traps.c:405!
[ 70.899951] ------------[ cut here ]------------
[ 70.899952] ------------[ cut here ]------------
[ 70.899955] kernel BUG at arch/arm64/kernel/traps.c:405!
[ 70.899959] Internal error: Oops - BUG: 0 [#1] SMP
[ 70.899962] Modules linked in: bnep aufs overlay nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vc4 drm_kms_helper snd_soc_core snd_compress snd_seq_dummy ac97_bus snd_usb_audio snd_pcm_dmaengine snd_seq_oss snd_hwdep snd_usbmidi_lib snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm_oss snd_mixer_oss joydev btsdio snd_seq input_leds snd_pcm bluetooth ecdh_generic ecc snd_seq_device brcmfmac snd_timer bcm2835_v4l2(CE) brcmutil bcm2835_mmal_vchiq(CE) snd vc_sm_cma(CE) v4l2_common cfg80211 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev raspberrypi_hwmon fb_sys_fops mc syscopyarea sysfillrect sysimgblt spidev rpivid_mem uio_pdrv_genirq uio sch_fq_codel ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid broadcom bcm_phy_lib mdio_bcm_unimac v3d gpu_sched drm crct10dif_ce sdhci_iproc
[ 70.900047] genet gpio_regulator phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
[ 70.900061] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C E 5.3.0-1013-raspi2 #15-Ubuntu
[ 70.900063] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)
[ 70.900068] pstate: 00400085 (nzcv daIf +PAN -UAO)
[ 70.900085] pc : do_undefinstr+0x64/0x68
[ 70.900087] lr : do_undefinstr+0x38/0x68
[ 70.900090] sp : ffff00001001bda0
[ 70.900091] x29: ffff00001001bda0 x28: ffffd680fbe33b00
[ 70.900095] x27: 000001088421d67a x26: ffff00001001c000
[ 70.900098] x25: ffff000010018000 x24: 0000000000000000
[ 70.900100] x23: 00000000a0400085 x22: ffff24b002b22da0
[ 70.900103] x21: 000000000100b000 x20: 0000ffffffffffff
[ 70.900106] x19: ffff00001001bdc0 x18: 0000000000000000
[ 70.900108] x17: 0000000000000000 x16: 0000000000000000
[ 70.900110] x15: 0000000000000000 x14: 0000000000000000
[ 70.900113] x13: 0000000000000000 x12: 0000000000000001
[ 70.900117] x11: ffff24b0030a5a20 x10: 0000000000000040
[ 70.900119] x9 : ffff24b00382e2b8 x8 : ffff24b00382e2b0
[ 70.900121] x7 : ffffd680fb800df0 x6 : ffff00001001bd98
[ 70.900124] x5 : ffff00001001bd98 x4 : ffff24b00393f0f8
[ 70.900126] x3 : ffff24b003813868 x2 : 4b3415783f25da00
[ 70.900128] x1 : 0000000000000000 x0 : 00000000a0400085
[ 70.900131] Call trace:
[ 70.900134] do_undefinstr+0x64/0x68
[ 70.900138] el1_undef+0x10/0xb4
[ 70.900143] arch_timer_handler_phys+0x30/0x50
[ 70.900146] handle_percpu_devid_irq+0x90/0x238
[ 70.900149] generic_handle_irq+0x34/0x50
[ 70.900152] __handle_domain_irq+0x6c/0xc0
[ 70.900154] gic_ha...

[Bryon Nevis (bnevis)]

Have instability with the 1013 kernel.

[Bryon Nevis (bnevis)]

USB issue with 4GB maxmem seems to be fixed.
2560x1440 resolution issue not fixed.
Cannot run glxinfo to get video driver information (immediate crash)

[Hui Wang (hui.wang)]

Could you tell us the detailed steps to install the desktop on the rpi4 board? Since we only released the server version, there is no desktop in the server version.

And the detailed steps to reproduce this issue.

Then we will setup the same environment to debug this issue.

[Bryon Nevis (bnevis)]

My configuration is the result of the server install, plus the proposed kernel above plus:

sudo apt-get install ^ubuntu-mate-core
(select lightdm when prompted).

After rebooting, the system comes up in graphical mode with a 1920x1080 viewport on a 2560x1440 screen buffer. It is useful for a few minutes before the kernel panic. I have an attached serial port to capture the panic output. The panic seems to occur with or without the total_mem=3072 workaround needed for previous kernels for the USB issue.

The system appears otherwise stable if I disable the lightdm service and continue using the system in text mode.

[Hui Wang (hui.wang)]

The upstream has some fixes for v3d driver, I applied them to the kernel and built a testing kernel:
https://people.canonical.com/~hwang4/v3d-fix/

Please also monitor the dmesg, to see if there are some "gpu mmc pte errors" in the dmesg.

thx.

[Bryon Nevis (bnevis)]

$ uname -a
Linux bnevis-pi 5.3.0-1013-raspi2 #15+v3d SMP Sun Nov 24 13:41:44 CST 2019 aarch64 aarch64 aarch64 GNU/Linux

[ 219.338309] raspberrypi-firmware soc:firmware: Request 0x00048019 returned status 0x80000001
[ 219.373813] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI infoframe
[ 219.381581] raspberrypi-firmware soc:firmware: Request 0x00048019 returned status 0x80000001
[ 225.633560] rfkill: input handler disabled
[ 310.783944] v3d fec00000.v3d: MMU error from client L2T (0) at 0x4b01000, pte invalid
[ 310.815954] v3d fec00000.v3d: MMU error from client L2T (0) at 0x62e1000, pte invalid
[ 310.846816] v3d fec00000.v3d: MMU error from client L2T (0) at 0x6601000, pte invalid
[ 310.875666] v3d fec00000.v3d: MMU error from client L2T (0) at 0x62e1000, pte invalid
[ 310.896849] v3d fec00000.v3d: MMU error from client L2T (0) at 0x6601000, pte invalid
[ 310.947578] v3d fec00000.v3d: MMU error from client L2T (0) at 0x6581000, pte invalid
[ 310.982421] v3d fec00000.v3d: MMU error from client L2T (0) at 0x7241000, pte invalid
[ 316.647853] v3d fec00000.v3d: MMU error from client L2T (0) at 0x1121000, pte invalid
[ 316.661628] v3d fec00000.v3d: MMU error from client L2T (0) at 0x65a1000, pte invalid
[ 316.694090] v3d fec00000.v3d: MMU error from client L2T (0) at 0x65c1000, pte invalid
[ 316.718344] v3d fec00000.v3d: MMU error from client L2T (0) at 0x6401000, pte invalid
[ 316.742765] v3d fec00000.v3d: MMU error from client L2T (0) at 0x6681000, pte invalid

glxinfo now reports the Broadcom rendering driver is being used (previously was VMware driver)
viewport issue still not fixed (but maybe in better shape to debug it)
kernel panic is resolved
pte invalid errors above occur when moving moving a foreground window that obscures a background window: noticable flickering and bleedthrough of background window while repainting.

[Hui Wang (hui.wang)]

Got it, thanks,

We will disable the driver v3d again in the kernel until the branch rpi-5.3.y has the perfect fix for this driver.

And set this bug duplicated to #1850876.