Bug 112322 - i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000, hang on rcs0
Summary: i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000, hang on rcs0
Status: RESOLVED DUPLICATE of bug 111970
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-18 14:48 UTC by Hin-Tak Leung
Modified: 2019-11-18 20:34 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
cat /sys/class/drm/card0/error > sys-class-drm-card0-error (15.05 KB, text/plain)
2019-11-18 14:48 UTC, Hin-Tak Leung
no flags Details

Description Hin-Tak Leung 2019-11-18 14:48:09 UTC
Created attachment 145992 [details]
cat /sys/class/drm/card0/error > sys-class-drm-card0-error

It is probably the same/similar to one of the other 4 with such a error message:

https://bugzilla.freedesktop.org/show_bug.cgi?id=111812
https://bugzilla.freedesktop.org/show_bug.cgi?id=111854
https://bugzilla.freedesktop.org/show_bug.cgi?id=111919
https://bugzilla.freedesktop.org/show_bug.cgi?id=112116

but it is not obvious which one should be - all of them have some follow-ups and non-trivial responses.

[177570.522360] i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000, hang on rcs0
[177570.522364] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[177570.522365] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[177570.522366] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[177570.522367] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[177570.522368] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[177570.523407] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0


It happened almost 4 days ago - but evidently recovered, as I did not notice until I look at dmesg - the system is still up and functional after 4 days after that event.

I am filing here, mostly because the message said I should. Please feel free to resolve the duplicate of one of the others, etc.
Comment 1 Hin-Tak Leung 2019-11-18 14:54:19 UTC
According to Ubuntu's apt, the version is:

xserver-xorg-video-intel/disco,now 2:2.99.917+git20180925-2 amd64 [installed,automatic]
  X.Org X server -- Intel i8xx, i9xx display driver

linux-firmware/disco-updates,disco-updates,disco-security,disco-security,now 1.178.6 all [installed,automatic]
  Firmware for Linux kernel drivers

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop)
	Flags: bus master, fast devsel, latency 0, IRQ 128
	Memory at a0000000 (64-bit, non-prefetchable) [size=16M]
	Memory at 90000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 4000 [size=64]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [40] Vendor Specific Information: Len=0c <?>
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [100] Process Address Space ID (PASID)
	Capabilities: [200] Address Translation Service (ATS)
	Capabilities: [300] Page Request Interface (PRI)
	Kernel driver in use: i915
	Kernel modules: i915

$ uname -r
5.3.10-050310-lowlatency
Comment 2 Chris Wilson 2019-11-18 20:34:09 UTC

*** This bug has been marked as a duplicate of bug 111970 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.