Attachment 33810 Details for Bug 26926 – dmesg.log

dmesg.log

dmesg.log (text/plain), 3.46 KB, created by Rafał Miłecki on 2010-03-06 07:03:35 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Rafał Miłecki

Created: 2010-03-06 07:03:35 UTC

Size: 3.46 KB

patch

obsolete

>[    5.169376] [drm] Initialized drm 1.1.0 20060810
>[    5.881369] [drm] radeon defaulting to kernel modesetting.
>[    5.881422] [drm] radeon kernel modesetting enabled.
>[    5.882263] [drm] radeon: Initializing kernel modesetting.
>[    5.884019] [drm] register mmio base: 0xF5000000
>[    5.884071] [drm] register mmio size: 65536
>[    5.884959] [drm] Clocks initialized !
>[    5.885013] [drm] 4 Power State(s)
>[    5.885061] [drm] State 0 Performance 
>[    5.885108] [drm] 	16 PCIE Lanes
>[    5.885156] [drm] 	3 Clock Mode(s)
>[    5.885203] [drm] 		0 engine/memory: 300000/500000
>[    5.885252] [drm] 		1 engine/memory: 300000/500000
>[    5.885301] [drm] 		2 engine/memory: 725000/500000
>[    5.885349] [drm] State 1 Default 
>[    5.885397] [drm] 	16 PCIE Lanes
>[    5.885444] [drm] 	3 Clock Mode(s)
>[    5.885492] [drm] 		0 engine/memory: 725000/500000
>[    5.885540] [drm] 		1 engine/memory: 725000/500000
>[    5.885589] [drm] 		2 engine/memory: 725000/500000
>[    5.885637] [drm] State 2 Performance 
>[    5.885685] [drm] 	16 PCIE Lanes
>[    5.885732] [drm] 	3 Clock Mode(s)
>[    5.885780] [drm] 		0 engine/memory: 300000/500000
>[    5.885828] [drm] 		1 engine/memory: 300000/500000
>[    5.885877] [drm] 		2 engine/memory: 725000/500000
>[    5.885925] [drm] State 3 Default (default)
>[    5.885973] [drm] 	16 PCIE Lanes
>[    5.886024] [drm] 	1 Clock Mode(s)
>[    5.886072] [drm] 		0 engine/memory: 725000/500000
>[    5.886124] [drm] radeon: dynamic power management enabled
>[    5.886174] [drm] radeon: power management initialized
>[    5.887630] [drm] Detected VRAM RAM=256M, BAR=256M
>[    5.887683] [drm] RAM width 128bits DDR
>[    5.887889] [drm] radeon: 256M of VRAM memory ready
>[    5.887938] [drm] radeon: 512M of GTT memory ready.
>[    5.888040] [drm] radeon: using MSI.
>[    5.888110] [drm] radeon: irq initialized.
>[    5.888159] [drm] GART: num cpu pages 131072, num gpu pages 131072
>[    5.888584] [drm] Loading RV635 Microcode
>[    6.116370] [drm] ring test succeeded in 1 usecs
>[    6.116541] [drm] radeon: ib pool ready.
>[    6.116640] [drm] ib test succeeded in 0 usecs
>[    6.116689] [drm] Enabling audio support
>[    6.116816] [drm] Default TV standard: PAL
>[    6.116996] [drm] Radeon Display Connectors
>[    6.117050] [drm] Connector 0:
>[    6.117097] [drm]   DVI-I
>[    6.117144] [drm]   HPD1
>[    6.117192] [drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
>[    6.117265] [drm]   Encoders:
>[    6.117313] [drm]     DFP1: INTERNAL_UNIPHY
>[    6.117361] [drm]     CRT2: INTERNAL_KLDSCP_DAC2
>[    6.117409] [drm] Connector 1:
>[    6.117456] [drm]   DVI-I
>[    6.117503] [drm]   HPD2
>[    6.117551] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
>[    6.117624] [drm]   Encoders:
>[    6.117671] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
>[    6.117720] [drm]     DFP2: INTERNAL_KLDSCP_LVTMA
>[    6.117768] [drm] Connector 2:
>[    6.117815] [drm]   DIN
>[    6.117862] [drm]   Encoders:
>[    6.117909] [drm]     TV1: INTERNAL_KLDSCP_DAC2
>[    6.171625] [drm] Requested: e: 30000 m: 50000 p: 16
>[    6.171675] [drm] Setting: e: 30000 m: 50000 p: 16
>[    6.251452] [drm] fb mappable at 0xE0141000
>[    6.251511] [drm] vram apper at 0xE0000000
>[    6.251568] [drm] size 3145728
>[    6.251623] [drm] fb depth is 24
>[    6.251679] [drm]    pitch is 4096
>[    6.252523] [drm] Requested: e: 72500 m: 50000 p: 16
>[    6.452008] [drm] Setting: e: 72500 m: 50000 p: 16
>[    6.458167] fb0: radeondrmfb frame buffer device
>[    6.458208] [drm] Initialized radeon 2.1.0 20080528 for 0000:01:00.0 on minor 0

Actions: View

Attachments on bug 26926: 33810 | 33811 | 33812 | 33813 | 33814 | 35168

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.