Attachment 106873 Details for Bug 82889 – dmesg | grep drm

dmesg | grep drm

dmesg.txt (text/plain), 3.49 KB, created by Lorenzo Bona on 2014-09-25 19:12:28 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Lorenzo Bona

Created: 2014-09-25 19:12:28 UTC

Size: 3.49 KB

patch

obsolete

>[    1.977393] [drm] Initialized drm 1.1.0 20060810
>[    1.995655] [drm] radeon kernel modesetting enabled.
>[    1.996062] [drm] initializing kernel modesetting (PITCAIRN 0x1002:0x6819 0x174B:0xA001).
>[    1.996079] [drm] register mmio base: 0xFEA00000
>[    1.996080] [drm] register mmio size: 262144
>[    1.996271] [drm] Detected VRAM RAM=2048M, BAR=256M
>[    1.996272] [drm] RAM width 256bits DDR
>[    1.996387] [drm] radeon: 2048M of VRAM memory ready
>[    1.996389] [drm] radeon: 1024M of GTT memory ready.
>[    1.996402] [drm] Loading pitcairn Microcode
>[    1.996409] [drm] Internal thermal controller with fan control
>[    1.996474] [drm] probing gen 2 caps for device 1022:1707 = 300d02/0
>[    2.006208] [drm] radeon: dpm initialized
>[    2.008454] [drm] GART: num cpu pages 262144, num gpu pages 262144
>[    2.010078] [drm] probing gen 2 caps for device 1022:1707 = 300d02/0
>[    2.010084] [drm] PCIE gen 2 link speeds already enabled
>[    2.039482] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
>[    2.040728] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>[    2.040729] [drm] Driver supports precise vblank timestamp query.
>[    2.040801] [drm] radeon: irq initialized.
>[    2.225371] [drm] ring test on 0 succeeded in 1 usecs
>[    2.225387] [drm] ring test on 1 succeeded in 1 usecs
>[    2.225397] [drm] ring test on 2 succeeded in 1 usecs
>[    2.225416] [drm] ring test on 3 succeeded in 2 usecs
>[    2.225434] [drm] ring test on 4 succeeded in 2 usecs
>[    2.411441] [drm] ring test on 5 succeeded in 2 usecs
>[    2.411460] [drm] UVD initialized successfully.
>[    2.412464] [drm] ib test on ring 0 succeeded in 0 usecs
>[    2.412628] [drm] ib test on ring 1 succeeded in 0 usecs
>[    2.412783] [drm] ib test on ring 2 succeeded in 0 usecs
>[    2.412836] [drm] ib test on ring 3 succeeded in 0 usecs
>[    2.412875] [drm] ib test on ring 4 succeeded in 1 usecs
>[    2.564352] [drm] ib test on ring 5 succeeded
>[    2.567141] [drm] Radeon Display Connectors
>[    2.567150] [drm] Connector 0:
>[    2.567155] [drm]   DP-1
>[    2.567159] [drm]   HPD4
>[    2.567165] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c
>[    2.567169] [drm]   Encoders:
>[    2.567173] [drm]     DFP1: INTERNAL_UNIPHY2
>[    2.567177] [drm] Connector 1:
>[    2.567181] [drm]   HDMI-A-1
>[    2.567184] [drm]   HPD5
>[    2.567190] [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c
>[    2.567194] [drm]   Encoders:
>[    2.567198] [drm]     DFP2: INTERNAL_UNIPHY2
>[    2.567202] [drm] Connector 2:
>[    2.567205] [drm]   DVI-I-1
>[    2.567209] [drm]   HPD6
>[    2.567214] [drm]   DDC: 0x6580 0x6580 0x6584 0x6584 0x6588 0x6588 0x658c 0x658c
>[    2.567218] [drm]   Encoders:
>[    2.567222] [drm]     DFP3: INTERNAL_UNIPHY
>[    2.567227] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
>[    2.567230] [drm] Connector 3:
>[    2.567234] [drm]   DVI-D-1
>[    2.567237] [drm]   HPD1
>[    2.567243] [drm]   DDC: 0x6570 0x6570 0x6574 0x6574 0x6578 0x6578 0x657c 0x657c
>[    2.567246] [drm]   Encoders:
>[    2.567250] [drm]     DFP4: INTERNAL_UNIPHY1
>[    2.691387] [drm] fb mappable at 0xC0478000
>[    2.691394] [drm] vram apper at 0xC0000000
>[    2.691397] [drm] size 8294400
>[    2.691400] [drm] fb depth is 24
>[    2.691403] [drm]    pitch is 7680
>[    2.691541] fbcon: radeondrmfb (fb0) is primary device
>[    2.860794] [drm:si_dpm_set_power_state] *ERROR* si_disable_ulv failed
>[    2.966815] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
>[    2.974414] [drm] Initialized radeon 2.40.0 20080528 for 0000:01:00.0 on minor 0

Actions: View

Attachments on bug 82889: 105003 | 105455 | 105456 | 106873 | 106884 | 107784 | 108125

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.