[comet lake] Gnome freezes, icons missing, graphics corruption

Bug #1859730 reported by Alonso on 2020-01-14
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
mesa (Ubuntu)
Undecided
Unassigned
mutter (Ubuntu)
Undecided
Unassigned

Bug Description

ack please..

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 5.4.11-050411-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CompositorRunning: None
Date: Tue Jan 14 20:17:26 2020
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed
 backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0962]
InstallationDate: Installed on 2020-01-13 (1 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0029 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 7390
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0377MH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
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.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

Alonso (alonsgajparr) wrote :
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Changed in xorg (Ubuntu):
status: New → Incomplete
affects: xorg (Ubuntu) → ubuntu
Alonso (alonsgajparr) wrote :

Yes of course,

I bought a DELL xps 7390 notebook with intel core i7 10th and ssd 512gb. which comes by default with ubuntu installed.

Since I turned on the computer I could witness abnormal behaviors;
1. GNOME was freezing, the icons do not appear, unexpected applications are closed when you press any key, it is not useful to turn off or restart, but if blocking and not unlocking, the command console does not work and this gives an input and output error. The only option is to press the off button until the computer is turned off. After turning on the system does not report any failure.
2. Only when the computer is turned on or unlocked, the screen emits a flash that appears to be out of sync, press any key and the screen resets.
3. Only when I demand the computer with Firefox and many windows, terminal, visual code, and running applications, the system collapses and the screen goes black showing the message [1,407103] couldn't get size 0x800000000000000000e
and I can only retrieve it by pressing the off button.

Alonso (alonsgajparr) wrote :
Daniel van Vugt (vanvugt) wrote :

Thanks.

I should have noticed earlier that you're using very new hardware with a slightly old Ubuntu release. Although it is the latest LTS release.

I am guessing you probably need a newer version of Mesa for this GPU. To test that theory please try booting Ubuntu 20.04 from USB (http://cdimage.ubuntu.com/daily-live/current/) and tell us if it has the same issues.

summary: - Xorg freeze
+ [comet lake] Gnome freezes, icons missing, graphics corruption
affects: ubuntu → mesa (Ubuntu)
Daniel van Vugt (vanvugt) wrote :

This also appears once in your kernel log:

[ 24.955117] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

which might be associated with the flashing and out-of-sync screen you describe. See bug 1550779.

Daniel van Vugt (vanvugt) wrote :

Finally, the problem might be triggered by the atomic modesetting code used by Xorg sessions. Please try logging into 'Ubuntu on Wayland' and tell us if that avoids some of the problem.

Changed in linux (Ubuntu):
status: New → Incomplete
Alonso (alonsgajparr) wrote :

Hi everyone,
Thank you very much Daniel for your attention and recommendations but ..;
1. I installed ubuntu 20.04, everything started fine, but it failed again in the same way as in ubuntu 18, before this I was testing fedora 31 and the same errors were presented for both ubuntu 18, 20 and fedora 31, (screen crash, black screen with the message [2658.28 ...] systemd-journald [378]: failed to write entry (22 items, 749 bytes), ignoring: read-only file system).
2. Thinking that it may be a hardware error especially of the micron m2 SSD, contact dell technical service and just have an answer from them I will comment on it by this means.
3. I also cannot get the id of the .crash file, but when I select to report the error, an error window appears indicating the following:
"The problem cannot be reported:
It has some packages installed with obsolete versions ....
bsdutils, libblkid1, libmount1, libsmartcols1, libuuid1, mount, utillinux, uuid-runtime "
Any advice to fix those versions of the packages?

Thank you very much to all!

Daniel van Vugt (vanvugt) wrote :

Thanks but that crash report is not relevant here.

Please follow the instructions in comment #8.

Please also update your system by running:

  sudo apt update
  sudo apt full-upgrade

Alonso (alonsgajparr) wrote :

Dear, I have the same mistakes again with Wayland and especially with the updates.
I did everything you suggested, I no longer have outdated library problems but the bugs remain the same: c

Changed in mesa (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu):
status: Incomplete → New

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Timo Aaltonen (tjaalton) wrote :

The platform has gone through extensive testing when it was certified by us, so I wonder if the hw is faulty somehow, or if there's a BIOS update available that might help?

Alonso (alonsgajparr) wrote :

Hello, 7 days ago I received the notebook and the bios was version 1.2 and automatically updated to 1.4. dell support doesn't respond yet but since I tried 3 OS (ubuntu 18, fedora 31 and ubuntu 20.04) and all three failed in the same way, it could point to a problem of Hw that can be the Ssd. I attach new photos ...

Timo Aaltonen (tjaalton) wrote :

yep, best to get it serviced

Daniel van Vugt (vanvugt) wrote :

SSD or FS corruption doesn't seem to appear in the original kernel log attached to this bug. I suspect that's a new issue and not the cause of this bug, but it might be...

Daniel van Vugt (vanvugt) wrote :

Is this the kernel that ships with the machine? 5.4.11-050411-generic

Also is Mesa 19.0 expected to support Comet Lake fully?

Timo Aaltonen (tjaalton) wrote :

Comet Lake is a gen9 gpu like Skylake etc, it only needed pci-id's to gain support. I have the upcoming desktop version ('CML-S') running without issues, and don't recall seeing issues with the mobile version either ('CML-U').

Timo Aaltonen (tjaalton) wrote :

Oh actually, try booting with i915.enable_psr=0

It's possible the panel model has changed, and the platform was certified with another model which didn't support panel self refresh.

Alonso (alonsgajparr) wrote :

Hi,
I do not remember what was the kernel that came with the machine, but if it was a 4. etc, the current kernel I have is 5.4.0-12-generic # 15-Ubuntu SMP.
How can I edit the grub i915.enable_psr = 0 ?.
Are these steps that I found on the internet right?
sudo nano /etc/default/grub
edit line with
GRUB_CMDLINE_LINUX_DEFAULT = "quiet splash i915.enable_psr = 0”
save
sudo update-grub
reboot
Those steps are done, I will comment if it has no effect.
Thank you!

Timo Aaltonen (tjaalton) wrote :

it came preinstalled with 4.15.0-1042-oem

yes, you can edit /etc/default/grub but you miswrote the parameter, it has to be literally 'i915.enable_psr=0' without any spaces or it won't work

Alonso (alonsgajparr) wrote :

Thanks Timo, I will comment on some effect, however in the log viewer several messages disappeared that I had before, for example (drm: intel_cpu_fifo_underrun_irq_handler [i915]] * ERROR * CPU pipe A FIFO underrun)

Daniel van Vugt (vanvugt) wrote :

That's bug 1550779, as mentioned in comment #7.

Alonso (alonsgajparr) wrote :

Hi everyone,
I finally managed to make dell's technical service change my micron hard drive to a different one, obviously the computer didn't fail anymore. He never got stuck again. Also install ubuntu 18.04 offered in dell downloads, but I will return to ubuntu 20. Thank you all for your help.

Daniel van Vugt (vanvugt) wrote :

Thanks for letting us know.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Changed in mesa (Ubuntu):
status: New → Invalid
Changed in mutter (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers