Bug 67964

Summary: [HD4000] Driver crash starting Enlightenment
Product: xorg Reporter: John Hall <hall.john>
Component: Driver/intelAssignee: Chris Wilson <chris>
Status: RESOLVED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg log none

Description John Hall 2013-08-10 01:34:43 UTC
Created attachment 83914 [details]
Xorg log

Bug description: The driver crashes after the Englightenment loading splash but before showing the desktop.  See the attached log for the backtrace.

System environment:
-- chipset: Intel(R) HD Graphics 4000
-- system architecture: 64-bit
-- xf86-video-intel: 2.21.14-1
-- xserver: 1.14.2-2
-- mesa: 9.1.6-1
-- libdrm: 2.4.46-2
-- kernel: 3.10.5-1
-- Linux distribution: Arch
-- Machine or mobo model: FORCE/MSI 16F3 (36-024) 680M
-- Display connector: unknown (laptop)

Reproducing steps:
Add "exec enlightenment_start" to $HOME/.xinitrc and run startx.

Additional info:
enlightenment17 version 0.17.3-1
Comment 1 John Hall 2013-08-10 01:37:32 UTC
Crash does not occur with xf86-video-intel 2.21.11-1.
Comment 2 Chris Wilson 2013-08-10 07:20:41 UTC
Can you try two (perhaps 3) things:

Run addr2line -i -e /usr/lib/xorg/modules/drivers/intel_drv.so 0x26324 0x4dc38 0x4fc30 0xbd6a8 0x33257 0x431e8

Recompile the ddx with --enable-debug and see if it catches the error earlier. Or even --enable-debug=full and attach the Xorg.0.log.

Run under gdb for a better backtrace.
Comment 3 Chris Wilson 2013-08-10 09:24:32 UTC
Not seeing the issue locally, so please do grab that symbolic backtrace and as much info as you can gather.
Comment 4 Chris Wilson 2013-08-26 16:14:41 UTC
Ping?
Comment 5 John Hall 2013-08-29 11:07:27 UTC
Sorry for the delay - I've been having hardware trouble as well. I should be able to provide an update this weekend.
Comment 6 John Hall 2013-09-02 16:48:08 UTC
Good news.  The issue, whatever it was, is fixed in 2.21.15-1.

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.