| Summary: | GPU HANG: ecode 8:0:0x85dffffb, in Xorg [398], reason: Ring hung, action: reset | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Marcin Mielniczuk <marcin.marcin.m> | ||||||||||||||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||||||||
| Severity: | normal | ||||||||||||||||||||
| Priority: | medium | CC: | ciri, derlafff, freedesktop, gary.c.wang, intel-gfx-bugs, jan.hicken, rumpelsepp | ||||||||||||||||||
| Version: | XOrg git | ||||||||||||||||||||
| Hardware: | Other | ||||||||||||||||||||
| OS: | All | ||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||
| i915 platform: | BDW | i915 features: | GPU hang | ||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||
|
Description
Marcin Mielniczuk
2016-04-01 15:57:54 UTC
Created attachment 122665 [details]
The dmesg output
Created attachment 122666 [details]
/var/log/Xorg.0.log
Created attachment 122667 [details]
/sys/class/drm/card0/error
I'm able to reproduce this in another usecase: opening a file in Eclipse. This seems to affect Java applications in some special way This is my whole setup (including HW setup, which was missing)
$ inxi -F
System: Host: arch Kernel: 4.1.21-1-lts x86_64 (64 bit)
Desktop: Cinnamon 2.8.8 Distro: Arch Linux
Machine: System: ASUSTeK (portable) product: X555LB v: 1.0
Mobo: ASUSTeK model: X555LB v: 1.0
Bios: American Megatrends v: X555LB.204 date: 01/13/2015
CPU: Dual core Intel Core i5-5200U (-HT-MCP-) cache: 3072 KB
clock speeds: max: 2700 MHz 1: 2200 MHz 2: 2200 MHz 3: 2200 MHz
4: 2200 MHz
Graphics: Card-1: Intel Broadwell-U Integrated Graphics
Card-2: NVIDIA GM108M [GeForce 940M]
Display Server: X.Org 1.18.3 driver: intel
Resolution: 1366x768@60.00hz
GLX Renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2)
GLX Version: 3.0 Mesa 11.2.0
Audio: Card-1 Intel Wildcat Point-LP High Definition Audio Controller
driver: snd_hda_intel
Card-2 Intel Broadwell-U Audio Controller driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.1.21-1-lts
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169
IF: enp2s0 state: up speed: 100 Mbps duplex: full
mac: 1c:b7:2c:0c:e6:7d
Card-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
driver: ath9k
IF: wlp3s0 state: down mac: 40:e2:30:f1:3d:73
Drives: HDD Total Size: 128.0GB (22.9% used)
ID-1: /dev/sda model: LITEONIT_LCS size: 128.0GB
Partition: ID-1: / size: 73G used: 24G (34%) fs: ext4 dev: /dev/sda5
ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda4
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 143 Uptime: 8 min Memory: 1410.7/7889.2MB
Client: Shell (fish) inxi: 2.2.38
*** Bug 92314 has been marked as a duplicate of this bug. *** *** Bug 94493 has been marked as a duplicate of this bug. *** *** Bug 95512 has been marked as a duplicate of this bug. *** Able to reproduce it (not saved the card dump yet -- system hangs) Reproducible: 50/50 when I launch some intensive load (like package compilation) Created attachment 124089 [details]
journald log
Created attachment 124092 [details]
/sys/class/drm/card0/error
Created attachment 124093 [details]
corresponding dmesg
Created attachment 124094 [details]
corresponding Xorg.log
I've tried to use xorg modesetting driver, but it seems to cause gpu hang on xorg startup. Created attachment 124108 [details]
got more verbose dmesg this time
I have found out that hangs disappear when I disable VT-d in BIOS. Marcin, Alexey - I'm sorry about this delay on getting back to you. Is this problem still valid? Have you tried the newest kernel, preferable generated from drm-tip? If yes then please provide new dmesg and card0/error data. *** This bug has been marked as a duplicate of bug 89360 *** I can't reproduce it anymore. |
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.