i915 Resetting rcs0 for hang on rcs0

Bug #1888981 reported by Petr Nosek
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hi,

  there is a bug in Linux kernel. Problem is with graphic card.

  I see these lines in dmesg:

[ 1269.113618] i915 0000:00:02.0: GPU HANG: ecode 9:1:0x87f99eb9, in blender [7901], hang on rcs0
[ 1269.114626] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0

  And graphical software are very unstable. They're crashing. It looks like, that graphical software is unstable, but problem is in the kernel.

  For example - using Blender is totaly unstable.

  I was looking for a solution. I found some discussion and there was written, kernel >5.5 is solution. So I tried kernel 5.7.7 and bug still persist. Kernel 5.7.7 was installed from Ubuntu repository. Log from kernel 5.7.7 is attached.

  Modeling in Blender for an 30 minutes is the best way, how to repruduce this bug.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nosek 2378 F.... pulseaudio
 /dev/snd/pcmC0D0p: nosek 2378 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 26 09:59:03 2020
InstallationDate: Installed on 2019-04-04 (478 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam
 Bus 001 Device 003: ID 8087:0aaa Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. ZenBook UX362FA_UX362FA
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/hostname-ubuntu_crypt ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic N/A
 linux-firmware 1.187.2
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-05-10 (76 days ago)
dmi.bios.date: 05/30/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX362FA.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX362FA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX362FA.303:bd05/30/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX362FA_UX362FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX362FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
dmi.product.family: ZenBook Flip
dmi.product.name: ZenBook UX362FA_UX362FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Petr Nosek (petr-nosek) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Petr Nosek (petr-nosek) wrote :

Hi, I'm on ubuntu 20.10 now.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.10
Release: 20.10
Codename: groovy

$ uname -a
Linux zenbook 5.8.0-29-generic #31-Ubuntu SMP Fri Nov 6 12:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

problem still presists:
[ 740.719785] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[ 740.719793] i915 0000:00:02.0: [drm] blender[7445] context reset due to GPU hang
[ 740.744451] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:87f99eb9, in blender [7445]
[ 770.159058] rfkill: input handler enabled

When I'm using Blender and modeling, desktop freezes.

dmes report attached

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.