Laptop freeze randomly

Bug #1979265 reported by Paramjeet Dhiman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Incomplete
Undecided
Unassigned

Bug Description

Laptop freeze randomly and then its start displaying some errors on black screen

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 21 10:22:22 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 xtables-addons, 3.9, 5.11.0-46-generic, x86_64: installed
 xtables-addons, 3.9, 5.13.0-48-generic, x86_64: installed
 xtables-addons, 3.9, 5.13.0-51-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83a7]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp.
 Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. HP Wide Vision HD Camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ENVY Laptop 13-ad1xx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-51-generic root=UUID=504d89e1-19cf-4d1f-898a-a6ae719474fe ro quiet splash nvme_core.default_ps_max_latency_us=0 pci=noaer vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2020
dmi.bios.release: 15.31
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83A7
dmi.board.vendor: HP
dmi.board.version: KBC Version 39.35
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 39.35
dmi.modalias: dmi:bvnInsyde:bvrF.31:bd06/10/2020:br15.31:efr39.35:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A7:rvrKBCVersion39.35:cvnHP:ct10:cvrChassisVersion:sku2VL79PA#ACJ:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY Laptop 13-ad1xx
dmi.product.sku: 2VL79PA#ACJ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Thanks for the bug report.

Next time a freeze happens, please:

1. Wait 10 seconds.

2. Reboot.

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

4. Attach the resulting text file here.

5. Also check for crashes by following https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

affects: xorg (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Paramjeet Dhiman (paramjeetdhiman) wrote :

Hello, I tried step 3 cmd but its showing me this

Specifying boot ID or boot offset has no effect, no persistent journal was found.

but i attached a file with using cmd journalctl -b > prevboot.txt

Thanks!

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

We need "-b-1" to collect the correct timeframe or else it's not relevant log data. Although the log in comment #4 mentions some nvme0n1 hardware errors that are concerning and might be relevant.

The next step is to check for crashes so please:

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.

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

Thanks, that doesn't give a crash location but it does show unsupported extensions in use.

Please try removing your extensions:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again.

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

Bug 1980338 is private so I can't see it. And all I can see in comment #9 is more evidence of unsupported extensions.

Please follow the instructions in comment #7.

Revision history for this message
Paramjeet Dhiman (paramjeetdhiman) wrote :

okay now its public you can check and i remove all extensions now and previously as well but issue was still there

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1980338

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.