Attachment 137303 Details for Bug 105036 – journalctl output for amdgpu with amdgpu.dc_log=1 and drm.debug=6

journalctl output for amdgpu with amdgpu.dc_log=1 and drm.debug=6

journalctl-amdgpu.log (text/x-log), 11.36 KB, created by Kyle De'Vir on 2018-02-12 17:01:32 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Kyle De'Vir

Created: 2018-02-12 17:01:32 UTC

Size: 11.36 KB

patch

obsolete

>Feb 12 16:48:56 valmar-desktop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux-bcachefs-git root=UUID=3a14dc3c-ae21-4e5b-8df6-51e6fd734f58 rw rcu_nocbs=0-5 processor.max_cstate=1 ipv6.disable=1 amdgpu.dc=1 amdgpu.dc_log=1 drm.debug=6
>Feb 12 16:48:56 valmar-desktop kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-bcachefs-git root=UUID=3a14dc3c-ae21-4e5b-8df6-51e6fd734f58 rw rcu_nocbs=0-5 processor.max_cstate=1 ipv6.disable=1 amdgpu.dc=1 amdgpu.dc_log=1 drm.debug=6
>Feb 12 16:48:56 valmar-desktop kernel: [drm] amdgpu kernel modesetting enabled.
>Feb 12 16:48:56 valmar-desktop kernel: fb: switching to amdgpudrmfb from simple
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: VRAM: 8192M 0x000000F400000000 - 0x000000F5FFFFFFFF (8192M used)
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: GTT: 256M 0x0000000000000000 - 0x000000000FFFFFFF
>Feb 12 16:48:56 valmar-desktop kernel: [drm] amdgpu: 8192M of VRAM memory ready
>Feb 12 16:48:56 valmar-desktop kernel: [drm] amdgpu: 8192M of GTT memory ready.
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: amdgpu: using MSI.
>Feb 12 16:48:56 valmar-desktop kernel: [drm] amdgpu: irq initialized.
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu: [powerplay] amdgpu: powerplay sw initialized
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 0 use gpu addr 0x0000000000400040, cpu addr 0x00000000c6074e95
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 1 use gpu addr 0x00000000004000c0, cpu addr 0x000000002c4b692c
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 2 use gpu addr 0x0000000000400140, cpu addr 0x000000008ab0ddb7
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 3 use gpu addr 0x00000000004001c0, cpu addr 0x0000000075c0bdcf
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 4 use gpu addr 0x0000000000400240, cpu addr 0x00000000083fee01
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 5 use gpu addr 0x00000000004002c0, cpu addr 0x00000000cba65108
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 6 use gpu addr 0x0000000000400340, cpu addr 0x000000001dd1a80b
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 7 use gpu addr 0x00000000004003c0, cpu addr 0x00000000526be4ab
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 8 use gpu addr 0x0000000000400440, cpu addr 0x00000000747cf7e2
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 9 use gpu addr 0x00000000004004e0, cpu addr 0x0000000066119b2b
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 10 use gpu addr 0x0000000000400560, cpu addr 0x0000000000ba8a64
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 11 use gpu addr 0x00000000004005e0, cpu addr 0x0000000034d0cbd2
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 12 use gpu addr 0x000000f4001e7a80, cpu addr 0x0000000042086a3a
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 13 use gpu addr 0x00000000004006e0, cpu addr 0x000000002d3c8093
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 14 use gpu addr 0x0000000000400760, cpu addr 0x00000000be5a7e4e
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 15 use gpu addr 0x00000000004007e0, cpu addr 0x0000000065871625
>Feb 12 16:48:56 valmar-desktop kernel: amdgpu 0000:1f:00.0: fence driver on ring 16 use gpu addr 0x0000000000400860, cpu addr 0x000000003789ed21
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_init [amdgpu]] DM_IRQ
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] amdgpu: freesync_module init done 000000008c202ab2.
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] amdgpu_dm_connector_init()
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] DCHPD: connector_id=0: dc_sink didn't change.
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] amdgpu_dm_connector_init()
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] DCHPD: connector_id=1: dc_sink didn't change.
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] amdgpu_dm_connector_init()
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] DCHPD: connector_id=2: dc_sink didn't change.
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] amdgpu_dm_connector_init()
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] DCHPD: connector_id=3: dc_sink didn't change.
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] amdgpu_dm_connector_init()
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] DCHPD: connector_id=4: dc_sink didn't change.
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 00000000b6615c6b for: dal_src=78, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 00000000a9dbe02e for: dal_src=79, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 000000009fc39a5e for: dal_src=80, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 000000002b666246 for: dal_src=81, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 000000006e0a396f for: dal_src=82, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 00000000012853c7 for: dal_src=83, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 00000000fc43a71e for: dal_src=26, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 0000000025b2862d for: dal_src=27, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 000000001a61c918 for: dal_src=28, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 00000000c7b1c507 for: dal_src=29, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 0000000043beb962 for: dal_src=30, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 00000000317c851f for: dal_src=31, irq context=1
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 0000000059012433 for: dal_src=6, irq context=0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 0000000039348aa1 for: dal_src=12, irq context=0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 00000000ec16f56a for: dal_src=4, irq context=0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 000000004513405f for: dal_src=10, irq context=0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 000000000d15914f for: dal_src=1, irq context=0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 00000000f38b1359 for: dal_src=7, irq context=0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 000000007283e90e for: dal_src=5, irq context=0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_irq_register_interrupt [amdgpu]] DM_IRQ: added irq handler: 000000008ba5ca65 for: dal_src=3, irq context=0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_hw_init [amdgpu]] KMS initialized.
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_update_crtcs_state [amdgpu]] Mode change not required, setting mode_changed to 0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_update_crtcs_state [amdgpu]] Mode change not required, setting mode_changed to 0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_update_crtcs_state [amdgpu]] Mode change not required, setting mode_changed to 0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_update_crtcs_state [amdgpu]] Mode change not required, setting mode_changed to 0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_update_crtcs_state [amdgpu]] Mode change not required, setting mode_changed to 0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_update_crtcs_state [amdgpu]] Mode change not required, setting mode_changed to 0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] No FB bound
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] amdgpu_crtc id:0 crtc_state_flags: enable:0, active:0, planes_changed:0, mode_changed:0,active_changed:0,connectors_changed:0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] amdgpu_crtc id:1 crtc_state_flags: enable:0, active:0, planes_changed:0, mode_changed:0,active_changed:0,connectors_changed:0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] amdgpu_crtc id:2 crtc_state_flags: enable:0, active:0, planes_changed:0, mode_changed:0,active_changed:0,connectors_changed:0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] amdgpu_crtc id:3 crtc_state_flags: enable:0, active:0, planes_changed:0, mode_changed:0,active_changed:0,connectors_changed:0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] amdgpu_crtc id:4 crtc_state_flags: enable:0, active:0, planes_changed:0, mode_changed:0,active_changed:0,connectors_changed:0
>Feb 12 16:48:56 valmar-desktop kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] amdgpu_crtc id:5 crtc_state_flags: enable:0, active:0, planes_changed:0, mode_changed:0,active_changed:0,connectors_changed:0
>Feb 12 16:48:56 valmar-desktop kernel: [drm] Initialized amdgpu 3.23.0 20150101 for 0000:1f:00.0 on minor 0

Actions: View

Attachments on bug 105036: 137260 | 137261 | 137303 | 137304

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.