Bug 5941

Summary: i810 driver failed with backtrace FontFileCompleteXLFD on i855 chipset
Product: xorg Reporter: Kang Jeong-Hee <keizie>
Component: Driver/intelAssignee: Alan Hourihane <alanh>
Status: RESOLVED DUPLICATE QA Contact:
Severity: critical    
Priority: high    
Version: 7.0.0   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
current xorg.conf
none
last Xorg.0.log
none
last dmsg
none
Xorg.0.log without dri module none

Description Kang Jeong-Hee 2006-02-19 04:50:13 UTC 
This is notebook with 1280x768 LCD panel. 915resulotion (was 855resolution) used
to tweak VBIOS resolution setting. Initial framebuffer is 1024x768 since boot time.

vesa driver works.

i810 driver makes

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x86) [0x80b49a6]
1: [0xffffe420]
2: /usr/lib/xorg/modules/drivers/i810_drv.so [0x379dbc92]
3: /usr/bin/X(AddScreen+0x1df) [0x806e5c9]
4: /usr/bin/X(InitOutput+0x47d) [0x809de5e]
5: /usr/bin/X(main+0x292) [0x806debe]
6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0x37d85ea2]
7: /usr/bin/X(FontFileCompleteXLFD+0x81) [0x806d611]

Fatal server error:
Caught signal 11.  Server aborting

I don't understand why XLFD is out there.
Comment 1 Kang Jeong-Hee 2006-02-19 04:51:40 UTC 
Created attachment 4662 [details]
current xorg.conf
Comment 2 Kang Jeong-Hee 2006-02-19 04:53:13 UTC 
Created attachment 4663 [details]
last Xorg.0.log
Comment 3 Kang Jeong-Hee 2006-02-19 04:55:20 UTC 
Created attachment 4664 [details]
last dmsg

no important information here. just for data.
Comment 4 Alan Hourihane 2006-02-19 05:43:10 UTC 

*** This bug has been marked as a duplicate of 5443 ***
Comment 5 Kang Jeong-Hee 2006-02-19 06:10:07 UTC 
Created attachment 4669 [details]
Xorg.0.log without dri module

Some more lines of backtrace
Comment 6 Kang Jeong-Hee 2006-02-20 22:21:54 UTC 
20060206 version of common, i810 and i915 from
http://dri.freedesktop.org/snapshots/ does not change Xorg.0.log

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.