Bug 88549 - Invalid ROM contents
Summary: Invalid ROM contents
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86 (IA32) Linux (All)
: medium minor
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-18 08:36 UTC by Jorge Araya Navarro
Modified: 2017-07-24 22:49 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
GPU crash dump (1.39 KB, text/plain)
2015-01-18 08:36 UTC, Jorge Araya Navarro
no flags Details

Description Jorge Araya Navarro 2015-01-18 08:36:25 UTC
Created attachment 112414 [details]
GPU crash dump

While booting, I get this error:

ene 17 13:35:11 abril.charola kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
ene 17 13:35:11 abril.charola kernel: [drm] Driver supports precise vblank timestamp query.
ene 17 13:35:11 abril.charola kernel: i915 0000:00:02.0: Invalid ROM contents
ene 17 13:35:11 abril.charola kernel: [drm] failed to find VBIOS tables
ene 17 13:35:11 abril.charola kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
ene 17 13:35:11 abril.charola kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
ene 17 13:35:11 abril.charola kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
ene 17 13:35:11 abril.charola kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
ene 17 13:35:11 abril.charola kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
ene 17 13:35:11 abril.charola kernel: i915: render error detected, EIR: 0x00000010
ene 17 13:35:11 abril.charola kernel: i915: page table error
ene 17 13:35:11 abril.charola kernel: i915:   PGTBL_ER: 0x00000012
ene 17 13:35:11 abril.charola kernel: [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
ene 17 13:35:11 abril.charola kernel: i915: render error detected, EIR: 0x00000010
ene 17 13:35:11 abril.charola kernel: i915: page table error
ene 17 13:35:11 abril.charola kernel: i915:   PGTBL_ER: 0x00000012


I can still play 3D games, with very some minors and graphic glitches. But I'm doing the report anyway. Attached is the GPU crash dump.

Here is everything related to the i915 driver:

~ 
> dmesg | grep -e i915
[  +0,000007] i915 0000:00:02.0: Invalid ROM contents
[  +0,000002] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  +0,000022] i915: render error detected, EIR: 0x00000010
[  +0,000006] i915: page table error
[  +0,000003] i915:   PGTBL_ER: 0x00000012
[  +0,000007] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
[  +0,000012] i915: render error detected, EIR: 0x00000010
[  +0,000005] i915: page table error
[  +0,000004] i915:   PGTBL_ER: 0x00000012
[  +0,007007] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[  +0,000002] i915 0000:00:02.0: registered panic notifier
[  +0,000017] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
~ 
>
Comment 1 Chris Wilson 2015-01-18 09:19:20 UTC
This is a GPU page fault during KMS takeover (the display engine is still trying to read the scanout left over by the BIOS, but the PTE no longer match). This should be fixed in 3.18+.


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.