Attachment 131472 Details for Bug 101160 – radeonsi dmesg

radeonsi dmesg

radeonsi_dmesg.txt (text/plain), 3.49 KB, created by mercuriete on 2017-05-24 18:39:02 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: mercuriete

Created: 2017-05-24 18:39:02 UTC

Size: 3.49 KB

patch

obsolete

>[    0.634127] ATOM BIOS: Venus
>[    0.634155] [drm] GPU not posted. posting now...
>[    0.637905] radeon 0000:01:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
>[    0.637925] radeon 0000:01:00.0: GTT: 2048M 0x0000000080000000 - 0x00000000FFFFFFFF
>[    0.637944] [drm] Detected VRAM RAM=2048M, BAR=256M
>[    0.637955] [drm] RAM width 128bits DDR
>[    0.638029] [TTM] Zone  kernel: Available graphics memory: 8186956 kiB
>[    0.638053] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
>[    0.638068] [TTM] Initializing pool allocator
>[    0.638080] [TTM] Initializing DMA pool allocator
>[    0.638102] [drm] radeon: 2048M of VRAM memory ready
>[    0.638113] [drm] radeon: 2048M of GTT memory ready.
>[    0.638129] [drm] Loading verde Microcode
>[    0.638142] [drm] Internal thermal controller without fan control
>[    0.638178] [drm] probing gen 2 caps for device 8086:c01 = 261ac83/e
>[    0.639442] ACPI: Battery Slot [BAT0] (battery present)
>[    0.644519] [drm] radeon: dpm initialized
>[    0.646116] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
>[    0.646184] [drm] GART: num cpu pages 524288, num gpu pages 524288
>[    0.646925] [drm] probing gen 2 caps for device 8086:c01 = 261ac83/e
>[    0.646945] [drm] PCIE gen 3 link speeds already enabled
>[    0.649118] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
>[    0.649242] radeon 0000:01:00.0: WB enabled
>[    0.649254] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff88041b19bc00
>[    0.649278] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff88041b19bc04
>[    0.649901] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff88041b19bc08
>[    0.650510] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff88041b19bc0c
>[    0.651111] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff88041b19bc10
>[    0.651959] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90001235a18
>[    0.672823] radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000080000c18 and cpu addr 0xffff88041b19bc18
>[    0.673438] radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000080000c1c and cpu addr 0xffff88041b19bc1c
>[    0.674040] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>[    0.674659] [drm] Driver supports precise vblank timestamp query.
>[    0.675256] radeon 0000:01:00.0: radeon: MSI limited to 32-bit
>[    0.675930] radeon 0000:01:00.0: radeon: using MSI.
>[    0.676580] [drm] radeon: irq initialized.
>[    1.224268] [drm] ring test on 0 succeeded in 1 usecs
>[    1.224896] [drm] ring test on 1 succeeded in 1 usecs
>[    1.225516] [drm] ring test on 2 succeeded in 1 usecs
>[    1.226135] [drm] ring test on 3 succeeded in 10 usecs
>[    1.226799] [drm] ring test on 4 succeeded in 9 usecs
>[    1.405111] [drm] ring test on 5 succeeded in 2 usecs
>[    1.405721] [drm] UVD initialized successfully.
>[    1.516589] [drm] ring test on 6 succeeded in 20 usecs
>[    1.517197] [drm] ring test on 7 succeeded in 4 usecs
>[    1.517752] [drm] VCE initialized successfully.
>[    1.518497] [drm] ib test on ring 0 succeeded in 0 usecs
>[    1.519130] [drm] ib test on ring 1 succeeded in 0 usecs
>[    1.519795] [drm] ib test on ring 2 succeeded in 0 usecs
>[    1.520453] [drm] ib test on ring 3 succeeded in 0 usecs
>[    1.521056] [drm] ib test on ring 4 succeeded in 0 usecs

Actions: View

Attachments on bug 101160: 131471 | 131472 | 131473

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.