Summary: | screen corruption after going from VT to X | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Fabio Pedretti <pedretti.fabio> | ||||||||||
Component: | General | Assignee: | Default DRI bug account <dri-devel> | ||||||||||
Status: | RESOLVED INVALID | QA Contact: | |||||||||||
Severity: | normal | ||||||||||||
Priority: | medium | CC: | pedretti.fabio | ||||||||||
Version: | XOrg git | ||||||||||||
Hardware: | x86 (IA32) | ||||||||||||
OS: | Linux (All) | ||||||||||||
Whiteboard: | |||||||||||||
i915 platform: | i915 features: | ||||||||||||
Attachments: |
|
Description
Fabio Pedretti
2014-03-24 16:31:37 UTC
Created attachment 96296 [details]
dmesg
Created attachment 96297 [details]
Xorg log after the corruption has been reproduced (X -> VT -> X) and restored changing resolution
This issue is still reproducible with Ubuntu 14.04 kernel (3.13.0-23.45), before I was using 3.11.0-18.32 (Ubuntu 13.10 kernel). This annoying issue is possibly not specific to radeon module. The following dmesg ERROR is interesting and may be of help. Maybe it needs a monitor quirk? [ 3.398641] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 58 [ 3.398646] Raw EDID: [ 3.398652] 00 ff ff ff ff ff ff 00 06 10 56 9c 00 00 00 00 [ 3.398656] 04 10 01 03 80 22 16 78 0a 87 f5 94 57 4f 8c 27 [ 3.398660] 27 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 [ 3.398664] 01 98 03 a2 01 01 9f 25 a0 40 51 84 0c 30 40 20 [ 3.398669] 33 00 4b cf 10 00 00 19 00 00 00 01 00 06 10 30 [ 3.398673] 00 00 00 00 00 00 00 00 0a 20 00 00 00 fe 00 4c [ 3.398677] 54 4e 31 35 34 58 37 00 00 00 0a 20 00 00 00 fc [ 3.398681] 00 43 6f 6c 6f 72 20 4c 43 44 0a 20 20 20 00 d5 [ 3.427467] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 58 [ 3.427471] Raw EDID: [ 3.427475] 00 ff ff ff ff ff ff 00 06 10 56 9c 00 00 00 00 [ 3.427479] 04 10 01 03 80 22 16 78 0a 87 f5 94 57 4f 8c 27 [ 3.427483] 27 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 [ 3.427487] 01 98 03 a2 01 01 9f 25 a0 40 51 84 0c 30 40 20 [ 3.427491] 33 00 4b cf 10 00 00 19 00 00 00 01 00 06 10 30 [ 3.427495] 00 00 00 00 00 00 00 00 0a 20 00 00 00 fe 00 4c [ 3.427499] 54 4e 31 35 34 58 37 00 00 00 0a 20 00 00 00 fc [ 3.427503] 00 43 6f 6c 6f 72 20 4c 43 44 0a 20 20 20 00 d5 [ 3.456273] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 58 [ 3.456278] Raw EDID: [ 3.456283] 00 ff ff ff ff ff ff 00 06 10 56 9c 00 00 00 00 [ 3.456287] 04 10 01 03 80 22 16 78 0a 87 f5 94 57 4f 8c 27 [ 3.456292] 27 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 [ 3.456296] 01 98 03 a2 01 01 9f 25 a0 40 51 84 0c 30 40 20 [ 3.456300] 33 00 4b cf 10 00 00 19 00 00 00 01 00 06 10 30 [ 3.456304] 00 00 00 00 00 00 00 00 0a 20 00 00 00 fe 00 4c [ 3.456308] 54 4e 31 35 34 58 37 00 00 00 0a 20 00 00 00 fc [ 3.456312] 00 43 6f 6c 6f 72 20 4c 43 44 0a 20 20 20 00 d5 [ 3.484997] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 58 [ 3.485001] Raw EDID: [ 3.485005] 00 ff ff ff ff ff ff 00 06 10 56 9c 00 00 00 00 [ 3.485009] 04 10 01 03 80 22 16 78 0a 87 f5 94 57 4f 8c 27 [ 3.485013] 27 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 [ 3.485017] 01 98 03 a2 01 01 9f 25 a0 40 51 84 0c 30 40 20 [ 3.485021] 33 00 4b cf 10 00 00 19 00 00 00 01 00 06 10 30 [ 3.485025] 00 00 00 00 00 00 00 00 0a 20 00 00 00 fe 00 4c [ 3.485029] 54 4e 31 35 34 58 37 00 00 00 0a 20 00 00 00 fc [ 3.485033] 00 43 6f 6c 6f 72 20 4c 43 44 0a 20 20 20 00 d5 [ 3.485041] radeon 0000:01:00.0: LVDS-1: EDID block 0 invalid. Created attachment 118045 [details]
dmesg with 3.19.0-26-generic
Any news on this issue?
It is still reproducible with Ubuntu 15.04 kernel:
Linux fabio-mac 3.19.0-26-generic #28-Ubuntu SMP Tue Aug 11 14:16:45 UTC 2015 i686 i686 i686 GNU/Linux
Attached updated dmesg.
Let me know if something other is needed.
this seems suspect: [ 61.916143] ------------[ cut here ]------------ [ 61.916157] WARNING: CPU: 0 PID: 31 at /build/linux-eVPZfP/linux-3.19.0/arch/x86/kernel/check.c:140 check_for_bios_corruption+0x8d/0xd0() [ 61.916161] Memory corruption detected in low memory Maybe some Mac firmware issue? Created attachment 118051 [details] dmesg with 3.19.0-26-generic > Maybe some Mac firmware issue? Possibly, but I think that may not be related, as that doesn’t always happen and maybe be a different issue. I attach a different dmesg where the crash doesn't happen, but the corruption problem is still present. Hi, Freedesktop's Bugzilla instance is EOLed and open bugs are about to be migrated to http://gitlab.freedesktop.org. To avoid migrating out of date bugs, I am now closing all the bugs that did not see any activity in the past year. If the issue is still happening, please create a new bug in the relevant project at https://gitlab.freedesktop.org/drm (use misc by default). Sorry about the noise! |
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.