Xorg crash

Bug #1771539 reported by Mario Costa
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg-server-hwe-16.04 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

When I try to use ubuntu with dual desktop display it crashes continuously, and entering into login mode.

I cannot use dual display.
To use an external monitor, I have to start the laptop with the computer closed.

It seems to be related to the graphic card, maybe dual graphic card of the laptop.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME-Classic:GNOME
Date: Wed May 16 10:36:05 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f]
 Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990]
InstallationDate: Installed on 2017-12-13 (153 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Hewlett-Packard HP EliteBook 840 G1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.39
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.59
dmi.chassis.asset.tag: 5CG44010XD
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 840 G1
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
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
xserver.bootTime: Thu Mar 8 12:39:32 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

Revision history for this message
Mario Costa (mario-silva-costa) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Mario Costa, thank you for reporting this and helping make Ubuntu better. Please advise to all of the following:

1) Is this something that started to happen after an update? If so, which and when precisely?

2) To see if this is already resolved in your release, could you please update your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the results?

tags: added: bios-outdated-1.44
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Mario Costa (mario-silva-costa) wrote :

Honestly, I think it got worst at some point, after some update or after I changed from Unity to Gnome. Unfortunately I don't really have any additional info.

Why do you "say" that the bios is outdated ? It is the last from the manufacturer, HP Elite Book 840 G1.

```
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x000D, DMI type 0, 24 bytes
BIOS Information
 Vendor: Hewlett-Packard
 Version: L71 Ver. 01.39
 Release Date: 09/26/2016
 Address: 0xF0000
 Runtime Size: 64 kB
 ROM Size: 8192 kB
 Characteristics:
  PCI is supported
  PC Card (PCMCIA) is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  EDD is supported
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  ACPI is supported
  USB legacy is supported
  Smart battery is supported
  BIOS boot specification is supported
  Function key-initiated network boot is supported
  Targeted content distribution is supported
  UEFI is supported
 BIOS Revision: 1.39
 Firmware Revision: 21.89
```

Thanks, for your reply.

Revision history for this message
penalvch (penalvch) wrote :

Mario Costa:

Your BIOS is outdated as per HP -> https://support.hp.com/us-en/drivers/selfservice/hp-elitebook-840-g1-notebook-pc/5405360

Also, you didn't respond to question 2).

Revision history for this message
Mario Costa (mario-silva-costa) wrote :

Hi, thanks for you promptly response, unfortunately only now I had the time to check the things above.

The HWE is the latest:
```
~$ sudo apt-get install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-generic-hwe-16.04 is already the newest version (4.13.0.43.62).
xserver-xorg-hwe-16.04 is already the newest version (1:7.7+16ubuntu3~16.04.1).
The following packages were automatically installed and are no longer required:
  dkms libllvm4.0 linux-headers-4.10.0-28 linux-headers-4.10.0-28-generic linux-image-4.10.0-28-generic linux-image-extra-4.10.0-28-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
```

The the bios is now updated, but the issue persists.

```
atritoman@atritoman-HP-EliteBook-840-G1:~$ sudo dmidecode -t 0
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x000D, DMI type 0, 24 bytes
BIOS Information
 Vendor: Hewlett-Packard
 Version: L71 Ver. 01.44
 Release Date: 04/12/2018
 Address: 0xF0000
 Runtime Size: 64 kB
 ROM Size: 8192 kB
 Characteristics:
  PCI is supported
  PC Card (PCMCIA) is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  EDD is supported
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  ACPI is supported
  USB legacy is supported
  Smart battery is supported
  BIOS boot specification is supported
  Function key-initiated network boot is supported
  Targeted content distribution is supported
  UEFI is supported
 BIOS Revision: 1.44
 Firmware Revision: 21.89
```

Meanwhile I had to reinstall ubuntu 16.04, its the default with Unity, same behavior.
When I've started the newly reinstalled system, it seemed to work well, the dual display, after a reboot or two, it stoped working.

The login screen works well and displays with dual display when I restart the laptop, but after I login it crashes, and it seems to restart the graphic environment/xserver maybe ...

I can post some additional logs.

penalvch (penalvch)
tags: added: latest-bios-1.44
removed: bios-outdated-1.44
Revision history for this message
penalvch (penalvch) wrote :

Mario Costa:

1) Please provide the output of the following terminal command (not manually attach anything found):
ls -la /var/crash

2) As per your Bug Description, you are using the non-default kernel parameter:
radeon.runpm=0

Could you please advise to if this is required to use?

Also, if you remove it, does the crash still happen?

3) As per the sticker of the monitor itself (not from the Bug Description, or the result of a terminal command), could you please provide the full monitor manufacturer and model?

4) How are you connecting the monitor to the computer, via DisplayPort-to-DisplayPort cable, DisplayPort-to-HDMI cable, dongle/adapter, etc.?

5) If you keep the external monitor disconnected from the computer on boot up, and after login then plug it in does this provide a WORKAROUND?

6) Does the crash only happen after coming up from a cold boot, only after resuming from suspend, etc.?

Changed in xorg (Ubuntu):
importance: Low → Medium
Revision history for this message
Mario Costa (mario-silva-costa) wrote :

1)
```
$ls -la /var/crash/
total 8080
drwxrwsrwt 2 root whoopsie 4096 Jun 7 01:30 .
drwxr-xr-x 14 root root 4096 Ago 1 2017 ..
-rwxrwxrwx 1 root whoopsie 0 Jun 7 01:17 .lock
-rw-r----- 1 root whoopsie 8265453 Jun 7 01:28 _usr_lib_xorg_Xorg.0.crash
-rw-r--r-- 1 root whoopsie 0 Jun 7 01:30 _usr_lib_xorg_Xorg.0.upload
-rw------- 1 whoopsie whoopsie 0 Jun 7 01:30 _usr_lib_xorg_Xorg.0.uploaded
```

2) I've probably added id, when trying to disable the graphic card, to use only one, as when trying to fix it came across some threads suggesting that (e.g. https://askubuntu.com/questions/771562/16-04-power-off-discrete-graphics-ati-amd). (I'll test removing this later on the day).

3) Dell U2715H (REV A01, 2015) (http://accessories.ap.dell.com/sna/productdetail.aspx?c=hk&l=en&s=bsd&cs=hkbsd1&sku=210-ADSZ)

4) DisplayPort-to-DisplayPort (pc DisplayPort-MiniDisplayPort monitor)

5) No, it crashes.

6) Both, no difference.

I start the laptop, from cold boot, first login screen displays properly in both monitors cloning the display. Afterwards I try to login and when setting new settings starts crashing repeatedly, trying to restart the xserver (as it seems).

Revision history for this message
Mario Costa (mario-silva-costa) wrote :

Since I've reinstalled the ubuntu 16.04, the problem persists, but the kernel parameter (radeon.runpm=0) is no longer present. I'll provide another log dump, when as soon as the problem occurs again.

mc

penalvch (penalvch)
Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
penalvch (penalvch) wrote :

Mario Costa:

A) Could you please provide the result of the following terminal command:
sudo cat /var/lib/whoopsie/whoopsie-id

B) To see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the result?

Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
Mario Costa (mario-silva-costa) wrote :

A) sudo cat /var/lib/whoopsie/whoopsie-id
126a6c719bcce7c3ad86f82dbca39dc81524233531d72481f4d5a2a4f2fac31510f8ea9e7daf5748cbe4667770413d4cc3e5644d79f968c0df829149ea1011b5

B) At the moment it is not possible to reinstall Ubuntu. I'm able to work more less fine as is, with the issue occurring. When I upgrade I'll check.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg (Ubuntu):
status: Incomplete → Expired
Changed in xorg (Ubuntu):
status: Expired → New
affects: xorg (Ubuntu) → xorg-server-hwe-16.04 (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Mario,

Your Xorg crashes for that whoopsie ID over the past 8 months or so are all one of three different crashes. What they all have in common is that they are in xorg-server-hwe-16.04 only, and are not retraceable/debuggable :(

If you can, please try upgrading to Ubuntu 18.04 and tell us if that improves the situation.

https://errors.ubuntu.com/bucket/?id=failed%3A/usr/lib/xorg/Xorg%3A6%3A/lib/x86_64-linux-gnu/libc-2.23.so%2B35428%3A/lib/x86_64-linux-gnu/libc-2.23.so%2B3702a%3A/usr/lib/xorg/Xorg%2B1b892a%3A/usr/lib/xorg/Xorg%2B972bc%3A/usr/lib/xorg/Xorg%2B1be502%3A/usr/lib/xorg/Xorg%2B1bf33d%3A/usr/lib/xorg/Xorg%2B1b5bde%3A/usr/lib/xorg/modules/drivers/modesetting_drv.so%2Ba2d5%3A/usr/lib/xorg/Xorg%2B58def%3A/usr/lib/xorg/Xorg%2B1af6c3%3A/usr/lib/xorg/Xorg%2B540c1%3A/usr/lib/xorg/Xorg%2B583b8%3A/lib/x86_64-linux-gnu/libc-2.23.so%2B20830%3A/usr/lib/xorg/Xorg%2B42329

https://errors.ubuntu.com/bucket/?id=failed%3A/usr/lib/xorg/Xorg%3A6%3A/lib/x86_64-linux-gnu/libc-2.23.so%2B35428%3A/lib/x86_64-linux-gnu/libc-2.23.so%2B3702a%3A/usr/lib/xorg/Xorg%2B1b859e%3A/usr/lib/xorg/Xorg%2B972bc%3A/usr/lib/xorg/Xorg%2B1be172%3A/usr/lib/xorg/Xorg%2B1befad%3A/usr/lib/xorg/Xorg%2B1b584e%3A/usr/lib/xorg/modules/drivers/modesetting_drv.so%2Ba255%3A/usr/lib/xorg/Xorg%2B58def%3A/usr/lib/xorg/Xorg%2B1af343%3A/usr/lib/xorg/Xorg%2B540c1%3A/usr/lib/xorg/Xorg%2B583b8%3A/lib/x86_64-linux-gnu/libc-2.23.so%2B20830%3A/usr/lib/xorg/Xorg%2B42329

https://errors.ubuntu.com/bucket/?id=failed%3A/usr/lib/xorg/Xorg%3A6%3A/lib/x86_64-linux-gnu/libc-2.23.so%2B35428%3A/lib/x86_64-linux-gnu/libc-2.23.so%2B3702a%3A/usr/lib/xorg/Xorg%2B1b892a%3A/usr/lib/xorg/Xorg%2B972bc%3A/usr/lib/xorg/Xorg%2B1be502%3A/usr/lib/xorg/Xorg%2B1bf33d%3A/usr/lib/xorg/Xorg%2B1b5bde%3A/usr/lib/xorg/modules/drivers/radeon_drv.so%2B49037%3A/usr/lib/xorg/modules/drivers/radeon_drv.so%2B49653%3A/usr/lib/xorg/modules/drivers/radeon_drv.so%2B4b0d8%3A/usr/lib/xorg/Xorg%2B58def%3A/usr/lib/xorg/Xorg%2B1af6c3%3A/usr/lib/xorg/Xorg%2B540c1%3A/usr/lib/xorg/Xorg%2B583b8%3A/lib/x86_64-linux-gnu/libc-2.23.so%2B20830

tags: added: radeon
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg-server-hwe-16.04 (Ubuntu):
status: New → Confirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

16.04 is EOL, if you can reproduce on a newer release, please open a new bug, thanks

Changed in xorg-server-hwe-16.04 (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.