Comment # 4
on bug 107922
from Mike Lothian
So that gets the machine booting however there's still this back trace [ 0.370419] WARNING: CPU: 2 PID: 1 at drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1379 dcn_bw_update_from_pplib+0x166/0x270 [ 0.370422] Modules linked in: [ 0.370425] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.19.0-rc1-agd5f+ #260 [ 0.370427] Hardware name: System manufacturer System Product Name/ROG STRIX X470-I GAMING, BIOS 0901 07/23/2018 [ 0.370430] RIP: 0010:dcn_bw_update_from_pplib+0x166/0x270 [ 0.370433] Code: d8 ca d8 f1 d9 5a 50 8b 44 fc 14 49 8b 94 24 78 01 00 00 48 89 04 24 df 2c 24 d8 f1 db 42 78 de c9 de ca de f9 d9 5a 4c eb 02 <0f> 0b 48 89 da be 04 00 00 00 48 89 ef e8 68 96 fe ff 84 c 0 0f 84 [ 0.370438] RSP: 0018:ffffc9000003b9d8 EFLAGS: 00010246 [ 0.370440] RAX: 0000000000000001 RBX: ffffc9000003ba38 RCX: 0000000000000000 [ 0.370442] RDX: 0000000000000000 RSI: 0000000000000004 RDI: 00000000ffffffff [ 0.370445] RBP: ffff8807fb05a000 R08: 0000000000000000 R09: 0720072007200720 [ 0.370447] R10: ffff8807fb8c0f00 R11: 0720072007200720 R12: ffff8807fb015000 [ 0.370449] R13: ffff8807fb055420 R14: ffff8807fb015000 R15: ffff8807fb193098 [ 0.370449] FS: 0000000000000000(0000) GS:ffff8807ffa80000(0000) knlGS:0000000000000000 [ 0.370449] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 0.370449] CR2: ffffc900002c0000 CR3: 000000000360a000 CR4: 00000000003406a0 [ 0.370449] Call Trace: [ 0.370449] ? construct+0x7d8/0xa00 [ 0.370449] ? generic_reg_get+0x1b/0x30 [ 0.370449] ? dcn10_create_resource_pool+0x31/0x50 [ 0.370449] ? dc_create_resource_pool+0x3d/0x180 [ 0.370449] ? __kmalloc+0x15e/0x170 [ 0.370449] ? dc_create+0x1ec/0x5e0 [ 0.370449] ? kmem_cache_alloc+0x22/0x120 [ 0.370449] ? dm_hw_init+0xc3/0x130 [ 0.370449] ? amdgpu_device_init.cold.34+0xca7/0xe0d [ 0.370449] ? __alloc_pages_nodemask+0xc1/0x1d0 [ 0.370449] ? amdgpu_driver_load_kms+0x5e/0x190 [ 0.370449] ? drm_dev_register+0x104/0x140 [ 0.370449] ? amdgpu_pci_probe+0x122/0x19e [ 0.370449] ? _raw_spin_unlock_irqrestore+0xf/0x30 [ 0.370449] ? pci_device_probe+0xd1/0x160 [ 0.370449] ? really_probe+0x1e7/0x270 [ 0.370449] ? driver_probe_device+0x4a/0xb0 [ 0.370449] ? __driver_attach+0xaf/0xd0 [ 0.370449] ? driver_probe_device+0xb0/0xb0 [ 0.370449] ? bus_for_each_dev+0x71/0xb0 [ 0.370449] ? bus_add_driver+0x192/0x1d0 [ 0.370449] ? do_early_param+0x89/0x89 [ 0.370449] ? driver_register+0x66/0xb0 [ 0.370449] ? drm_sched_fence_slab_init+0x2c/0x2c [ 0.370449] ? do_one_initcall+0x42/0x162 [ 0.370449] ? do_early_param+0x89/0x89 [ 0.370449] ? kernel_init_freeable+0x14b/0x1d5 [ 0.370449] ? rest_init+0xb0/0xb0 [ 0.370449] ? kernel_init+0x5/0xf1 [ 0.370449] ? ret_from_fork+0x22/0x40 [ 0.370449] ---[ end trace 6cbafa0c2f65290d ]--- [ 0.370551] [drm] DM_PPLIB: values for Invalid clock But I think someone said that was harmless
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
