Xorg freeze

Bug #1821763 reported by Gus
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Expired
Undecided
Unassigned

Bug Description

System froze completely, no mouse and keyboard, caps and num lock keys didn't even light up.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 12:20:53 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:39c5]
InstallationDate: Installed on 2019-03-06 (19 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 13d3:5a02 IMC Networks
 Bus 001 Device 003: ID 8087:0a2a Intel Corp.
 Bus 001 Device 002: ID 413c:8505 Dell Computer Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80YH
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=e7f345fa-d4fb-4bf9-a5bc-6788d80fdfba ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/23/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 4WCN41WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 320-15IKB
dmi.modalias: dmi:bvnLENOVO:bvr4WCN41WW:bd07/23/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
dmi.product.family: ideapad 320-15IKB
dmi.product.name: 80YH
dmi.product.sku: LENOVO_MT_80YH_BU_idea_FM_ideapad 320-15IKB
dmi.product.version: Lenovo ideapad 320-15IKB
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
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

Revision history for this message
Gus (gus-antoniassi) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks for the bug report. Next time the problem happens, please:

1. Reboot.

2. Run: journalctl -b-1 > prevboot.txt

3. Send us the file 'prevboot.txt'.

affects: xorg (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Gus (gus-antoniassi) wrote :

Hi Daniel, thanks for the reply! I am attaching the prevboot.txt file.

This time the freeze happened while the machine was locked and I was away, when I came back the screen was black and mouse and keyboard weren't working. I can't pinpoint exactly when it froze, but looking at the logs I believe it was around 4:15 PM.

I tried to ssh to the machine but the client froze after asking the password, so I'm not able to get any logs from it while frozen.

Looking at the logs I can see some entries about Gnome Shell, I have these extensions enabled, should I uninstall them?

- Alt-Tab Switcher Popup Delay Removal
- AlternateTab
- Clock Override
- Dash to Panel
- NoAnnoyance
- Sound Input & Output Device Chooser
- Start Overlay in Application View

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes, please do uninstall all extensions and retest.

Revision history for this message
Gus (gus-antoniassi) wrote :

I tried uninstalling the extensions and reinstalling gnome-shell, but it froze again today.

I am attaching a new journalctl file, this time I booted in recovery mode to get the file so judging by the log timestamp it matches the time when it froze, so this one should be more precise.

There is an entry about killing process "TabNine" because it ran out of memory, this is a VSCode extension that I installed today, so I don't believe the other freezes were caused by it. Could it be that Ubuntu is freezing when it runs out of memory?

I will leave dstat running and logging to a file so maybe I can get some info about memory when it freezes again. Any other tips for debugging?

Thanks in advance for the support.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

TabNine is probably not the cause. But your machine did run out of memory, which is at least now the main problem here...

The process which pushed your system over the line was 'java' allocating more memory. But it doesn't look like java is the biggest problem.

The biggest problems appear to be:

  chrome (many tabs open)
  PostMan
  slack
  code

Those may be the main reasons why the system froze. So please try reducing/removing some of those. If you can't get by without all of those then please try installing more RAM in the laptop OR just set up swap memory:

  https://linuxize.com/post/how-to-add-swap-space-on-ubuntu-18-04/
  https://help.ubuntu.com/community/SwapFaq

Once you have added more physical or swap memory to the machine, please test again and tell us if the problem persists.

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

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

Changed in ubuntu:
status: Incomplete → Expired
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.