Skip to contentSkip to conversation

3.15.0-rc2 radeon HD 7480D [Aruba] blank display

DISCUSSION Ken Moffat 3 participants 7 messages Apr 21, 2014 – Apr 29, 2014 2 messages not in the archive

Subsystems (2)
lore
Share & tools
lore

Ken Moffat

author
#0 lore raw

I've just built 3.15.0-rc2 on this box, and discovered that I get a
blank screen. The boot appears to complete (it sends me information from SMART which is from my last bootscript), and it responds to MagicSysRQ to reboot. I tried to login and run startx, but that didn't seem to make any difference - possibly something went wrong, it wasn't in my history when I booted a good kernel.

This machine uses a regular old VGA cable to connect it, the
following lines in dmesg make me think it has chosen the wrong connector:

Apr 21 19:32:45 bluesbreaker kernel: [    1.273246]
[drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
Apr 21 19:32:45 bluesbreaker kernel: [    1.273247]
[drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
Apr 21 19:32:45 bluesbreaker kernel: [    1.295116] Console:

switching to colour frame buffer device 85x34

On a boot with 3.14.0 and earlier I get a different console size -

Apr 21 20:42:44 bluesbreaker kernel: [    1.445992] Console:

switching to colour frame buffer device 133x54

My console font is 12x22, and my screen is 1600x1200 but it looks
as if 3.15-rc2 has fallen back to trying to use 1024x768.

I'm attaching what look like the relevant parts of the messages
from the system logs for 3.15-rc2 and 3.14.0.

Any ideas, please ? This is an AMD A4-5300 APU and not the world's
fastest machine for bisecting :-(

ĸen

Signature · 1 line
das eine Mal als Tragödie, dieses Mal als Farce
Apr 21 20:56:19 bluesbreaker kernel: [    0.766847] [drm] Initialized drm 1.1.0 20060810
Apr 21 20:56:19 bluesbreaker kernel: [    0.766901] [drm] radeon kernel modesetting enabled.
Apr 21 20:56:19 bluesbreaker kernel: [    0.767261] [drm] initializing kernel modesetting (ARUBA 0x1002:0x9993 0x1002:0x9993).
Apr 21 20:56:19 bluesbreaker kernel: [    0.767324] [drm] register mmio base: 0xFEF00000
Apr 21 20:56:19 bluesbreaker kernel: [    0.767357] [drm] register mmio size: 262144
Apr 21 20:56:19 bluesbreaker kernel: [    0.767441] ATOM BIOS: 113
Apr 21 20:56:19 bluesbreaker kernel: [    0.767558] radeon 0000:00:01.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used)
Apr 21 20:56:19 bluesbreaker kernel: [    0.767596] radeon 0000:00:01.0: GTT: 1024M 0x0000000020000000 - 0x000000005FFFFFFF
Apr 21 20:56:19 bluesbreaker kernel: [    0.767633] [drm] Detected VRAM RAM=512M, BAR=256M
Apr 21 20:56:19 bluesbreaker kernel: [    0.768866] [drm] RAM width 64bits DDR
Apr 21 20:56:19 bluesbreaker kernel: [    0.768943] [TTM] Zone  kernel: Available graphics memory: 1708830 kiB
Apr 21 20:56:19 bluesbreaker kernel: [    0.768976] [TTM] Initializing pool allocator
Apr 21 20:56:19 bluesbreaker kernel: [    0.769013] [TTM] Initializing DMA pool allocator
Apr 21 20:56:19 bluesbreaker kernel: [    0.769061] [drm] radeon: 512M of VRAM memory ready
Apr 21 20:56:19 bluesbreaker kernel: [    0.769094] [drm] radeon: 1024M of GTT memory ready.
Apr 21 20:56:19 bluesbreaker kernel: [    0.769140] [drm] Loading ARUBA Microcode
Apr 21 20:56:19 bluesbreaker kernel: [    0.769173] [drm] Internal thermal controller without fan control
Apr 21 20:56:19 bluesbreaker kernel: [    0.769407] [drm] radeon: dpm initialized
Apr 21 20:56:19 bluesbreaker kernel: [    0.769611] [drm] GART: num cpu pages 262144, num gpu pages 262144
Apr 21 20:56:19 bluesbreaker kernel: [    0.779832] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
Apr 21 20:56:19 bluesbreaker kernel: [    0.779985] radeon 0000:00:01.0: WB enabled
Apr 21 20:56:19 bluesbreaker kernel: [    0.780020] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff8800994f7c00
Apr 21 20:56:19 bluesbreaker kernel: [    0.780787] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90010235a18
Apr 21 20:56:19 bluesbreaker kernel: [    0.780826] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000020000c04 and cpu addr 0xffff8800994f7c04
Apr 21 20:56:19 bluesbreaker kernel: [    0.780864] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000020000c08 and cpu addr 0xffff8800994f7c08
Apr 21 20:56:19 bluesbreaker kernel: [    0.780902] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff8800994f7c0c
Apr 21 20:56:19 bluesbreaker kernel: [    0.780941] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000020000c10 and cpu addr 0xffff8800994f7c10
Apr 21 20:56:19 bluesbreaker kernel: [    0.780980] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Apr 21 20:56:19 bluesbreaker kernel: [    0.781013] [drm] Driver supports precise vblank timestamp query.
Apr 21 20:56:19 bluesbreaker kernel: [    0.781061] radeon 0000:00:01.0: irq 41 for MSI/MSI-X
Apr 21 20:56:19 bluesbreaker kernel: [    0.781072] radeon 0000:00:01.0: radeon: using MSI.
Apr 21 20:56:19 bluesbreaker kernel: [    0.781374] [drm] radeon: irq initialized.
Apr 21 20:56:19 bluesbreaker kernel: [    0.800502] [drm] ring test on 0 succeeded in 2 usecs
Apr 21 20:56:19 bluesbreaker kernel: [    0.800596] [drm] ring test on 3 succeeded in 2 usecs
Apr 21 20:56:19 bluesbreaker kernel: [    0.800634] [drm] ring test on 4 succeeded in 1 usecs
Apr 21 20:56:19 bluesbreaker kernel: [    0.856329] [drm] ring test on 5 succeeded in 1 usecs
Apr 21 20:56:19 bluesbreaker kernel: [    0.876237] [drm] UVD initialized successfully.
Apr 21 20:56:19 bluesbreaker kernel: [    0.877136] [drm] ib test on ring 0 succeeded in 0 usecs
Apr 21 20:56:19 bluesbreaker kernel: [    0.877702] [drm] ib test on ring 3 succeeded in 0 usecs
Apr 21 20:56:19 bluesbreaker kernel: [    0.878266] [drm] ib test on ring 4 succeeded in 1 usecs
Apr 21 20:56:19 bluesbreaker kernel: [    0.899250] [drm] ib test on ring 5 succeeded
Apr 21 20:56:19 bluesbreaker kernel: [    0.920172] [drm] Radeon Display Connectors
Apr 21 20:56:19 bluesbreaker kernel: [    0.920209] [drm] Connector 0:
Apr 21 20:56:19 bluesbreaker kernel: [    0.920243] [drm]   HDMI-A-1
Apr 21 20:56:19 bluesbreaker kernel: [    0.920277] [drm]   HPD1
Apr 21 20:56:19 bluesbreaker kernel: [    0.920310] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c
Apr 21 20:56:19 bluesbreaker kernel: [    0.920347] [drm]   Encoders:
Apr 21 20:56:19 bluesbreaker kernel: [    0.920379] [drm]     DFP1: INTERNAL_UNIPHY2
Apr 21 20:56:19 bluesbreaker kernel: [    0.920412] [drm] Connector 1:
Apr 21 20:56:19 bluesbreaker kernel: [    0.920444] [drm]   VGA-1
Apr 21 20:56:19 bluesbreaker kernel: [    0.920476] [drm]   HPD2
Apr 21 20:56:19 bluesbreaker kernel: [    0.920508] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c
Apr 21 20:56:19 bluesbreaker kernel: [    0.920545] [drm]   Encoders:
Apr 21 20:56:19 bluesbreaker kernel: [    0.920576] [drm]     CRT1: INTERNAL_UNIPHY2
Apr 21 20:56:19 bluesbreaker kernel: [    0.920609] [drm]     CRT1: NUTMEG
Apr 21 20:56:19 bluesbreaker kernel: [    0.920641] [drm] Connector 2:
Apr 21 20:56:19 bluesbreaker kernel: [    0.920674] [drm]   DVI-D-1
Apr 21 20:56:19 bluesbreaker kernel: [    0.920705] [drm]   HPD3
Apr 21 20:56:19 bluesbreaker kernel: [    0.920736] [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c
Apr 21 20:56:19 bluesbreaker kernel: [    0.920773] [drm]   Encoders:
Apr 21 20:56:19 bluesbreaker kernel: [    0.920804] [drm]     DFP2: INTERNAL_UNIPHY
Apr 21 20:56:19 bluesbreaker kernel: [    1.173963] [drm] fb mappable at 0xC047A000
Apr 21 20:56:19 bluesbreaker kernel: [    1.173997] [drm] vram apper at 0xC0000000
Apr 21 20:56:19 bluesbreaker kernel: [    1.174027] [drm] size 3145728
Apr 21 20:56:19 bluesbreaker kernel: [    1.174056] [drm] fb depth is 24
Apr 21 20:56:19 bluesbreaker kernel: [    1.174085] [drm]    pitch is 4096
Apr 21 20:56:19 bluesbreaker kernel: [    1.174206] fbcon: radeondrmfb (fb0) is primary device
Apr 21 20:56:19 bluesbreaker kernel: [    1.273253] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
Apr 21 20:56:19 bluesbreaker kernel: [    1.273254] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
Apr 21 20:56:19 bluesbreaker kernel: [    1.295093] Console: switching to colour frame buffer device 85x34
Apr 21 20:56:19 bluesbreaker kernel: [    1.296949] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device
Apr 21 20:56:19 bluesbreaker kernel: [    1.296999] radeon 0000:00:01.0: registered panic notifier
Apr 21 20:56:19 bluesbreaker kernel: [    1.297824] [drm] Initialized radeon 2.38.0 20080528 for 0000:00:01.0 on minor 0
Apr 21 20:57:26 bluesbreaker kernel: [    0.887023] [drm] Initialized drm 1.1.0 20060810
Apr 21 20:57:26 bluesbreaker kernel: [    0.887106] [drm] radeon kernel modesetting enabled.
Apr 21 20:57:26 bluesbreaker kernel: [    0.887495] [drm] initializing kernel modesetting (ARUBA 0x1002:0x9993 0x1002:0x9993).
Apr 21 20:57:26 bluesbreaker kernel: [    0.887559] [drm] register mmio base: 0xFEF00000
Apr 21 20:57:26 bluesbreaker kernel: [    0.887590] [drm] register mmio size: 262144
Apr 21 20:57:26 bluesbreaker kernel: [    0.887678] ATOM BIOS: 113
Apr 21 20:57:26 bluesbreaker kernel: [    0.887793] radeon 0000:00:01.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used)
Apr 21 20:57:26 bluesbreaker kernel: [    0.887831] radeon 0000:00:01.0: GTT: 1024M 0x0000000020000000 - 0x000000005FFFFFFF
Apr 21 20:57:26 bluesbreaker kernel: [    0.887868] [drm] Detected VRAM RAM=512M, BAR=256M
Apr 21 20:57:26 bluesbreaker kernel: [    0.887901] [drm] RAM width 64bits DDR
Apr 21 20:57:26 bluesbreaker kernel: [    0.888041] [TTM] Zone  kernel: Available graphics memory: 1708866 kiB
Apr 21 20:57:26 bluesbreaker kernel: [    0.889278] [TTM] Initializing pool allocator
Apr 21 20:57:26 bluesbreaker kernel: [    0.889315] [TTM] Initializing DMA pool allocator
Apr 21 20:57:26 bluesbreaker kernel: [    0.889363] [drm] radeon: 512M of VRAM memory ready
Apr 21 20:57:26 bluesbreaker kernel: [    0.889395] [drm] radeon: 1024M of GTT memory ready.
Apr 21 20:57:26 bluesbreaker kernel: [    0.889438] [drm] Loading ARUBA Microcode
Apr 21 20:57:26 bluesbreaker kernel: [    0.889472] [drm] Internal thermal controller without fan control
Apr 21 20:57:26 bluesbreaker kernel: [    0.889706] [drm] radeon: dpm initialized
Apr 21 20:57:26 bluesbreaker kernel: [    0.889897] [drm] GART: num cpu pages 262144, num gpu pages 262144
Apr 21 20:57:26 bluesbreaker kernel: [    0.903297] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
Apr 21 20:57:26 bluesbreaker kernel: [    0.903450] radeon 0000:00:01.0: WB enabled
Apr 21 20:57:26 bluesbreaker kernel: [    0.903485] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff880099ae3c00
Apr 21 20:57:26 bluesbreaker kernel: [    0.904254] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90010235a18
Apr 21 20:57:26 bluesbreaker kernel: [    0.904294] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000020000c04 and cpu addr 0xffff880099ae3c04
Apr 21 20:57:26 bluesbreaker kernel: [    0.904333] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000020000c08 and cpu addr 0xffff880099ae3c08
Apr 21 20:57:26 bluesbreaker kernel: [    0.904372] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff880099ae3c0c
Apr 21 20:57:26 bluesbreaker kernel: [    0.904410] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000020000c10 and cpu addr 0xffff880099ae3c10
Apr 21 20:57:26 bluesbreaker kernel: [    0.904449] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Apr 21 20:57:26 bluesbreaker kernel: [    0.904482] [drm] Driver supports precise vblank timestamp query.
Apr 21 20:57:26 bluesbreaker kernel: [    0.904532] radeon 0000:00:01.0: irq 41 for MSI/MSI-X
Apr 21 20:57:26 bluesbreaker kernel: [    0.904541] radeon 0000:00:01.0: radeon: using MSI.
Apr 21 20:57:26 bluesbreaker kernel: [    0.904842] [drm] radeon: irq initialized.
Apr 21 20:57:26 bluesbreaker kernel: [    0.923942] [drm] ring test on 0 succeeded in 2 usecs
Apr 21 20:57:26 bluesbreaker kernel: [    0.924035] [drm] ring test on 3 succeeded in 2 usecs
Apr 21 20:57:26 bluesbreaker kernel: [    0.924075] [drm] ring test on 4 succeeded in 1 usecs
Apr 21 20:57:26 bluesbreaker kernel: [    0.979756] [drm] ring test on 5 succeeded in 1 usecs
Apr 21 20:57:26 bluesbreaker kernel: [    0.999659] [drm] UVD initialized successfully.
Apr 21 20:57:26 bluesbreaker kernel: [    1.001669] [drm] ib test on ring 0 succeeded in 0 usecs
Apr 21 20:57:26 bluesbreaker kernel: [    1.002225] [drm] ib test on ring 3 succeeded in 0 usecs
Apr 21 20:57:26 bluesbreaker kernel: [    1.002779] [drm] ib test on ring 4 succeeded in 1 usecs
Apr 21 20:57:26 bluesbreaker kernel: [    1.023780] [drm] ib test on ring 5 succeeded
Apr 21 20:57:26 bluesbreaker kernel: [    1.045574] [drm] Radeon Display Connectors
Apr 21 20:57:26 bluesbreaker kernel: [    1.045609] [drm] Connector 0:
Apr 21 20:57:26 bluesbreaker kernel: [    1.045641] [drm]   HDMI-A-1
Apr 21 20:57:26 bluesbreaker kernel: [    1.045672] [drm]   HPD1
Apr 21 20:57:26 bluesbreaker kernel: [    1.045704] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c
Apr 21 20:57:26 bluesbreaker kernel: [    1.045740] [drm]   Encoders:
Apr 21 20:57:26 bluesbreaker kernel: [    1.045772] [drm]     DFP1: INTERNAL_UNIPHY2
Apr 21 20:57:26 bluesbreaker kernel: [    1.045804] [drm] Connector 1:
Apr 21 20:57:26 bluesbreaker kernel: [    1.045836] [drm]   VGA-1
Apr 21 20:57:26 bluesbreaker kernel: [    1.045867] [drm]   HPD2
Apr 21 20:57:26 bluesbreaker kernel: [    1.045898] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c
Apr 21 20:57:26 bluesbreaker kernel: [    1.045934] [drm]   Encoders:
Apr 21 20:57:26 bluesbreaker kernel: [    1.045966] [drm]     CRT1: INTERNAL_UNIPHY2
Apr 21 20:57:26 bluesbreaker kernel: [    1.045998] [drm]     CRT1: NUTMEG
Apr 21 20:57:26 bluesbreaker kernel: [    1.046030] [drm] Connector 2:
Apr 21 20:57:26 bluesbreaker kernel: [    1.046061] [drm]   DVI-D-1
Apr 21 20:57:26 bluesbreaker kernel: [    1.046093] [drm]   HPD3
Apr 21 20:57:26 bluesbreaker kernel: [    1.046125] [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c
Apr 21 20:57:26 bluesbreaker kernel: [    1.046161] [drm]   Encoders:
Apr 21 20:57:26 bluesbreaker kernel: [    1.046192] [drm]     DFP2: INTERNAL_UNIPHY
Apr 21 20:57:26 bluesbreaker kernel: [    1.307550] [drm] fb mappable at 0xC1488000
Apr 21 20:57:26 bluesbreaker kernel: [    1.307584] [drm] vram apper at 0xC0000000
Apr 21 20:57:26 bluesbreaker kernel: [    1.307614] [drm] size 7680000
Apr 21 20:57:26 bluesbreaker kernel: [    1.307643] [drm] fb depth is 24
Apr 21 20:57:26 bluesbreaker kernel: [    1.307672] [drm]    pitch is 6400
Apr 21 20:57:26 bluesbreaker kernel: [    1.307837] fbcon: radeondrmfb (fb0) is primary device
Apr 21 20:57:26 bluesbreaker kernel: [    1.441761] Console: switching to colour frame buffer device 133x54
Apr 21 20:57:26 bluesbreaker kernel: [    1.445997] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device
Apr 21 20:57:26 bluesbreaker kernel: [    1.446047] radeon 0000:00:01.0: registered panic notifier
Apr 21 20:57:26 bluesbreaker kernel: [    1.446191] [drm] Initialized radeon 2.37.0 20080528 for 0000:00:01.0 on minor 0
#1 lore raw
Quoted 10 lines · Ken Moffat

I've just built 3.15.0-rc2 on this box, and discovered that I get a
blank screen. The boot appears to complete (it sends me information from SMART which is from my last bootscript), and it responds to MagicSysRQ to reboot. I tried to login and run startx, but that didn't seem to make any difference - possibly something went wrong, it wasn't in my history when I booted a good kernel.

This machine uses a regular old VGA cable to connect it, the
following lines in dmesg make me think it has chosen the wrong connector:

VGA is implemented as a DP to VGA bridge on APUs.

Quoted 12 lines
Apr 21 19:32:45 bluesbreaker kernel: [    1.273246]
[drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
Apr 21 19:32:45 bluesbreaker kernel: [    1.273247]
[drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
Apr 21 19:32:45 bluesbreaker kernel: [    1.295116] Console:

switching to colour frame buffer device 85x34

On a boot with 3.14.0 and earlier I get a different console size -

Apr 21 20:42:44 bluesbreaker kernel: [    1.445992] Console:

switching to colour frame buffer device 133x54

Quoted 8 lines

My console font is 12x22, and my screen is 1600x1200 but it looks
as if 3.15-rc2 has fallen back to trying to use 1024x768.

I'm attaching what look like the relevant parts of the messages
from the system logs for 3.15-rc2 and 3.14.0.

Any ideas, please ? This is an AMD A4-5300 APU and not the world's
fastest machine for bisecting :-(

I'd guess it's either the pll rework patches or the switch to the common dp helper code patches. It would be helpful if you could bisect.

Alex

author
#2 lore raw
Quoted 32 lines · Alex Deucher
Quoted 10 lines · Ken Moffat

I've just built 3.15.0-rc2 on this box, and discovered that I get a
blank screen. The boot appears to complete (it sends me information from SMART which is from my last bootscript), and it responds to MagicSysRQ to reboot. I tried to login and run startx, but that didn't seem to make any difference - possibly something went wrong, it wasn't in my history when I booted a good kernel.

This machine uses a regular old VGA cable to connect it, the
following lines in dmesg make me think it has chosen the wrong connector:

VGA is implemented as a DP to VGA bridge on APUs.

Quoted 18 lines
Apr 21 19:32:45 bluesbreaker kernel: [    1.273246]
[drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
Apr 21 19:32:45 bluesbreaker kernel: [    1.273247]
[drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
Apr 21 19:32:45 bluesbreaker kernel: [    1.295116] Console:

switching to colour frame buffer device 85x34

On a boot with 3.14.0 and earlier I get a different console size -

Apr 21 20:42:44 bluesbreaker kernel: [    1.445992] Console:

switching to colour frame buffer device 133x54

My console font is 12x22, and my screen is 1600x1200 but it looks
as if 3.15-rc2 has fallen back to trying to use 1024x768.

I'm attaching what look like the relevant parts of the messages
from the system logs for 3.15-rc2 and 3.14.0.

Quoted 8 lines
Quoted 2 lines

Any ideas, please ? This is an AMD A4-5300 APU and not the world's
fastest machine for bisecting :-(

I'd guess it's either the pll rework patches or the switch to the common dp helper code patches. It would be helpful if you could bisect.

Alex

OK, I guess I can do the builds on a faster machine.

ĸen

Signature · 1 line
das eine Mal als Tragödie, dieses Mal als Farce
author
#5 lore raw
In reply to a message not in the archive

On Tue, Apr 22, 2014 at 03:31:06AM +0100, Ken Moffat wrote:

[ resending, somehow lkml dropped out of the Cc. ]

Quoted 58 lines · Ken Moffat
Quoted 17 lines · Ed Tomlinson
Quoted 16 lines

Ken,

You might want to try reverting:

commit 379dfc25e257ffe10eb53b86d2375f7c0f4f33ef

Author: Alex Deucher <[email protected]>
Date:   Mon Apr 7 10:33:46 2014 -0400

drm/radeon/dp: switch to the common i2c over aux code

Provides a nice cleanup in radeon.

Quoted 7 lines
Quoted 4 lines

This fixed a similar problem here (see the drm pull thread for rc1)

Thanks
Ed Tomlinson

Tried reverting that from rc2, but it didn't help. Thanks anyway.

Well, I *believed* I had created a patch for that commit, and
reverted it from -rc2 with patch -R. But I've now bisected through drivers/gpu/drm between v3.14.0 and v3.15-rc2 and the bisection pointed to that same commit, so I guess I did something wrong.

There were a couple of other issues along the way (mounting nfs
hung on one commit, startx hung on several of the commits, but I've marked those as "good" because I had a display, even if the system was not usable).

I've now gone back to linus' tree that I cloned a few hours ago,
i.e.
commit c089b229dfdd09d59a11d8bc2344bf8196d575ce
Merge: 9ac03675010a 0565103d1adb
Author: Linus Torvalds <[email protected]>
Date: Mon Apr 21 10:05:35 2014 -0700

Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml

created a branch, and *definitely* reverted 379dfc25e257ffe10eb53b86d2375f7c0f4f33ef (using git revert) in that branch. And this version works fine.

So belatedly I see that I seem to have the same problem as Ed. Or
at least that the same commit is causing both our problems.

Alex - do you need any more information from me to help with this ?

ĸen

Signature · 1 line
das eine Mal als Tragödie, dieses Mal als Farce
Signature · 1 line
das eine Mal als Tragödie, dieses Mal als Farce
#6 lore raw
Quoted 58 lines · Ken Moffat

On Tue, Apr 22, 2014 at 03:31:06AM +0100, Ken Moffat wrote:

[ resending, somehow lkml dropped out of the Cc. ]

Quoted 54 lines · Ken Moffat
Quoted 17 lines · Ed Tomlinson
Quoted 16 lines

Ken,

You might want to try reverting:

commit 379dfc25e257ffe10eb53b86d2375f7c0f4f33ef

Author: Alex Deucher <[email protected]>
Date:   Mon Apr 7 10:33:46 2014 -0400

drm/radeon/dp: switch to the common i2c over aux code

Provides a nice cleanup in radeon.

Quoted 7 lines
Quoted 4 lines

This fixed a similar problem here (see the drm pull thread for rc1)

Thanks
Ed Tomlinson

Tried reverting that from rc2, but it didn't help. Thanks anyway.

Well, I *believed* I had created a patch for that commit, and
reverted it from -rc2 with patch -R. But I've now bisected through drivers/gpu/drm between v3.14.0 and v3.15-rc2 and the bisection pointed to that same commit, so I guess I did something wrong.

There were a couple of other issues along the way (mounting nfs
hung on one commit, startx hung on several of the commits, but I've marked those as "good" because I had a display, even if the system was not usable).

I've now gone back to linus' tree that I cloned a few hours ago,
i.e.
commit c089b229dfdd09d59a11d8bc2344bf8196d575ce
Merge: 9ac03675010a 0565103d1adb
Author: Linus Torvalds <[email protected]>
Date: Mon Apr 21 10:05:35 2014 -0700

Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml

created a branch, and *definitely* reverted 379dfc25e257ffe10eb53b86d2375f7c0f4f33ef (using git revert) in that branch. And this version works fine.

So belatedly I see that I seem to have the same problem as Ed. Or
at least that the same commit is causing both our problems.

Alex - do you need any more information from me to help with this ?

The attached patch should fix it.

Thanks,

Alex

From 9cd764fd57bb2a4e5f618d0f8a64c8154a820688 Mon Sep 17 00:00:00 2001
From: Alex Deucher <[email protected]>
Date: Tue, 22 Apr 2014 01:49:28 -0400
Subject: [PATCH] drm/radeon/aux: fix hpd assignment for aux bus

The hpd (hot plug detect) pin assignment got lost
in the conversion to to the common i2c over aux
code. Without this information, aux transactions
do not work properly. Fixes DP failures.

---
 drivers/gpu/drm/radeon/atombios_dp.c | 1 +
 1 file changed, 1 insertion(+)
drivers/gpu/drm/radeon/atombios_dp.c +1 -0
index 1593652..bc0119f 100644
@@ -209,6 +209,7 @@ void radeon_dp_aux_init(struct radeon_connector *radeon_connector)
 {
 	int ret;
 
+	radeon_connector->ddc_bus->rec.hpd = radeon_connector->hpd.hpd;
 	radeon_connector->ddc_bus->aux.dev = radeon_connector->base.kdev;
 	radeon_connector->ddc_bus->aux.transfer = radeon_dp_aux_transfer;
 	ret = drm_dp_aux_register_i2c_bus(&radeon_connector->ddc_bus->aux);
Signature · 1 line
1.7.11.7
Tested-by
#7 lore raw
Quoted 55 lines · On Tuesday 22 April 2014 01:54:01 Alex Deucher wrote:
Quoted 54 lines · Ken Moffat

On Tue, Apr 22, 2014 at 03:31:06AM +0100, Ken Moffat wrote:

[ resending, somehow lkml dropped out of the Cc. ]

Quoted 50 lines · Ken Moffat
Quoted 17 lines · Ed Tomlinson
Quoted 16 lines

Ken,

You might want to try reverting:

commit 379dfc25e257ffe10eb53b86d2375f7c0f4f33ef

Author: Alex Deucher <[email protected]>
Date:   Mon Apr 7 10:33:46 2014 -0400

drm/radeon/dp: switch to the common i2c over aux code

Provides a nice cleanup in radeon.

Quoted 7 lines
Quoted 4 lines

This fixed a similar problem here (see the drm pull thread for rc1)

Thanks
Ed Tomlinson

Tried reverting that from rc2, but it didn't help. Thanks anyway.

Well, I *believed* I had created a patch for that commit, and
reverted it from -rc2 with patch -R. But I've now bisected through drivers/gpu/drm between v3.14.0 and v3.15-rc2 and the bisection pointed to that same commit, so I guess I did something wrong.

There were a couple of other issues along the way (mounting nfs
hung on one commit, startx hung on several of the commits, but I've marked those as "good" because I had a display, even if the system was not usable).

I've now gone back to linus' tree that I cloned a few hours ago,
i.e.
commit c089b229dfdd09d59a11d8bc2344bf8196d575ce
Merge: 9ac03675010a 0565103d1adb
Author: Linus Torvalds <[email protected]>
Date: Mon Apr 21 10:05:35 2014 -0700

Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml

created a branch, and *definitely* reverted 379dfc25e257ffe10eb53b86d2375f7c0f4f33ef (using git revert) in that branch. And this version works fine.

Quoted 6 lines
Quoted 4 lines
Quoted 4 lines

So belatedly I see that I seem to have the same problem as Ed. Or
at least that the same commit is causing both our problems.

Alex - do you need any more information from me to help with this ?

The attached patch should fix it.

And it does here (on bonaire, r7 260x). You can add my tested by

Thanks,
Ed Tomlinson

author
#8 lore raw
In reply to Alex Deucher
Quoted 12 lines · Alex Deucher

The attached patch should fix it.

Thanks,

Alex

From 9cd764fd57bb2a4e5f618d0f8a64c8154a820688 Mon Sep 17 00:00:00 2001
From: Alex Deucher <[email protected]>
Date: Tue, 22 Apr 2014 01:49:28 -0400
Subject: [PATCH] drm/radeon/aux: fix hpd assignment for aux bus

Sorry, my default mailbox (the one where personal mail ends up)
overflowed (the old "procmail thinks it cannot write to it" issue) and I've been reading mail on my netbook with a short 24-line term, didn't notice that my overflow mailbox had appeared because it was on the next screen. So, sorry for not replying.

And then when I did notice, I accidentally sent a personal reply
only to Ed.

The good news is that -rc3 obviously has the fix, and is working
fine. Thanks.

ĸen

Signature · 1 line
das eine Mal als Tragödie, dieses Mal als Farce