Bug 104180 - [snb] GPU hang in java
Summary: [snb] GPU hang in java
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-09 13:21 UTC by kinazarov@gmail.com
Modified: 2019-09-25 19:06 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (48.44 KB, text/plain)
2017-12-09 13:21 UTC, kinazarov@gmail.com
Details

Description kinazarov@gmail.com 2017-12-09 13:21:01 UTC
Created attachment 136056 [details]
/sys/class/drm/card0/error

dmesg:
[  429.436286] [drm] GPU HANG: ecode 6:0:0x85fffffc, in java [1721], reason: Hang on rcs0, action: reset
[  429.436289] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  429.436290] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  429.436290] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  429.436291] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  429.436292] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  429.436428] i915 0000:00:02.0: Resetting chip after gpu hang
[  437.424143] i915 0000:00:02.0: Resetting chip after gpu hang
[  506.412398] i915 0000:00:02.0: Resetting chip after gpu hang
[  514.411939] i915 0000:00:02.0: Resetting chip after gpu hang
[  522.411482] i915 0000:00:02.0: Resetting chip after gpu hang
[  530.411025] i915 0000:00:02.0: Resetting chip after gpu hang
[  598.437137] i915 0000:00:02.0: Resetting chip after gpu hang
[  622.435120] i915 0000:00:02.0: Resetting chip after gpu hang
[  630.434435] i915 0000:00:02.0: Resetting chip after gpu hang
[  736.410369] i915 0000:00:02.0: Resetting chip after gpu hang
[  744.409811] i915 0000:00:02.0: Resetting chip after gpu hang
[  826.452143] i915 0000:00:02.0: Resetting chip after gpu hang
[  834.387622] i915 0000:00:02.0: Resetting chip after gpu hang
[  842.387087] i915 0000:00:02.0: Resetting chip after gpu hang
[  850.386548] i915 0000:00:02.0: Resetting chip after gpu hang
[  858.386026] i915 0000:00:02.0: Resetting chip after gpu hang


console error:
intel_do_flush_locked failed input/output error
Comment 1 kinazarov@gmail.com 2017-12-09 13:23:19 UTC
sudo lspci -v -s 00:02.0
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller
	Flags: bus master, fast devsel, latency 0, IRQ 24
	Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915
	Kernel modules: i915
Comment 2 kinazarov@gmail.com 2017-12-09 13:24:52 UTC
And another strange thing:
After this gpu hang system fails to reboot or poweroff normally.
Comment 3 Elizabeth 2017-12-13 22:35:48 UTC
Hello Kinazarov,
Is there any step to reproduce this hang? What desktop are you using? Could you share your Xorg and Mesa versions? What distro are you using?
Thank you.
Comment 4 GitLab Migration User 2019-09-25 19:06:24 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1664.


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.