Bug 558138

Summary: X fails to read EDID
Product: [Fedora] Fedora Reporter: Piotr Drąg <piotrdrag>
Component: kernelAssignee: Dave Airlie <airlied>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: anton, dougsland, gansalmon, itamar, jonathan, kernel-maint, mcepl, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-03 13:50:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Smolt profile, Xorg.0.log, dmesg, messages, and stack trace
none
dmesg
none
stack trace from gdb
none
messages
none
Smolt profile
none
Xorg.0.log
none
dmesg from working kernel (2.6.31.12-174.2.3)
none
Xorg.0.log from working kernel (2.6.31.12-174.2.3)
none
edid extracted with working kernel
none
Patch fixing this issue none

Description Piotr Drąg 2010-01-23 20:45:25 UTC
Created attachment 386378 [details]
Smolt profile, Xorg.0.log, dmesg, messages, and stack trace

Description of problem:
Xorg crashes on start up, before running plymouth splash. It's a NVA5 chip with KMS, and with nomodeset it also crashes when text mode plymouth splash ends.

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.7.4-3.fc12.x86_64
xorg-x11-drv-nouveau-0.0.15-19.20091105gite1c2efd.fc12.x86_64
kernel-2.6.32.4-30.fc12.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Boot a 2.6.32 kernel from koji.
  
Actual results:
Crash. Screen looks like it's off.

Expected results:
You know, seeing gdm etc. :)

Additional info:
Smolt profile, Xorg.0.log, dmesg, messages, and stack trace are attached.

With 2.6.31 from updates laptop boots, but crashes randomly several times a day. I don't know if I should file this too (I figured out that it's better to use the newest kernel).

Comment 1 Piotr Drąg 2010-01-27 14:23:15 UTC
Created attachment 387084 [details]
dmesg

Comment 2 Piotr Drąg 2010-01-27 14:24:11 UTC
Created attachment 387085 [details]
stack trace from gdb

Comment 3 Piotr Drąg 2010-01-27 14:24:37 UTC
Created attachment 387086 [details]
messages

Comment 4 Piotr Drąg 2010-01-27 14:24:59 UTC
Created attachment 387087 [details]
Smolt profile

Comment 5 Piotr Drąg 2010-01-27 14:25:48 UTC
Created attachment 387088 [details]
Xorg.0.log

Comment 6 Piotr Drąg 2010-02-01 03:10:46 UTC
I'd be glad to know if it's a software bug that could be fixed some time later, my video card model issue, or issue with my specific card or machine that's needed to be reported to my vendor's support.

Comment 7 Matěj Cepl 2010-02-02 16:25:25 UTC
This looks pretty straightforward:

Backtrace:
0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x49ea68]
1: /usr/bin/Xorg (0x400000+0x61a89) [0x461a89]
2: /lib64/libpthread.so.0 (0x3063000000+0xf0f0) [0x306300f0f0]
3: /usr/bin/Xorg (xf86InitViewport+0x4b) [0x51e26b]
4: /usr/bin/Xorg (InitOutput+0xb23) [0x470223]
5: /usr/bin/Xorg (0x400000+0x21bfa) [0x421bfa]
6: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x306281eb1d]
7: /usr/bin/Xorg (0x400000+0x21949) [0x421949]
Segmentation fault at address 0x24

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting

Comment 8 Piotr Drąg 2010-02-11 15:12:59 UTC
Created attachment 390267 [details]
dmesg from working kernel (2.6.31.12-174.2.3)

Comment 9 Piotr Drąg 2010-02-11 15:14:08 UTC
Created attachment 390268 [details]
Xorg.0.log from working kernel (2.6.31.12-174.2.3)

Comment 10 Piotr Drąg 2010-02-11 15:16:58 UTC
Created attachment 390271 [details]
edid extracted with working kernel

It's AUO B156XW02 flat panel.

Comment 11 Piotr Drąg 2010-02-18 01:41:29 UTC
Patch fixing this issue is now in process of upstream integration.

Comment 12 Piotr Drąg 2010-03-09 21:50:11 UTC
Created attachment 398948 [details]
Patch fixing this issue

Attaching patch which is fixing this issue from Ben Skeggs, to avoid accidentally losing it.

Comment 13 Piotr Drąg 2010-05-03 13:50:33 UTC
Fixed in f13 kernels and upstream.