Bug 1585414 - [abrt] radeon_dp_get_dp_link_config: WARNING: CPU: 5 PID: 403 at drivers/gpu/drm/drm_dp_helper.c:157 drm_dp_bw_code_to_link_rate+0x3e/0x50 [drm_kms_helper] [radeon] [NEEDINFO]
Summary: [abrt] radeon_dp_get_dp_link_config: WARNING: CPU: 5 PID: 403 at drivers/gpu/...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:1040c03e4ff157e4340ab553186...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-02 14:52 UTC by Dan Loomis
Modified: 2018-08-29 15:08 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-08-29 15:08:32 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (107.11 KB, text/plain)
2018-06-02 14:52 UTC, Dan Loomis
no flags Details

Description Dan Loomis 2018-06-02 14:52:10 UTC
Additional info:
reporter:       libreport-2.9.5
WARNING: CPU: 5 PID: 403 at drivers/gpu/drm/drm_dp_helper.c:157 drm_dp_bw_code_to_link_rate+0x3e/0x50 [drm_kms_helper]
Modules linked in: hid_logitech_hidpp hid_logitech_dj uas usb_storage radeon(+) rtsx_pci_sdmmc mmc_core i2c_algo_bit drm_kms_helper ttm e1000e crc32c_intel drm serio_raw ptp rtsx_pci pps_core
CPU: 5 PID: 403 Comm: systemd-udevd Not tainted 4.16.11-300.fc28.x86_64 #1
Hardware name: Hewlett-Packard HP ZBook 17 G2/2255, BIOS M70 Ver. 01.07 02/26/2015
RIP: 0010:drm_dp_bw_code_to_link_rate+0x3e/0x50 [drm_kms_helper]
RSP: 0018:ffffb4b64394f848 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff9d1d6ffb3000 RCX: 0000000000000006
RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff9d1d9dd56930
RBP: ffff9d1d730e7000 R08: 0000000000000038 R09: 0000000000000394
R10: 0000000000000000 R11: 0000000000000001 R12: ffff9d1d6ffb3000
R13: 0000000000000018 R14: 0000000000006257 R15: ffff9d1d73940304
FS:  00007f3557925180(0000) GS:ffff9d1d9dd40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005600ea40f3f8 CR3: 0000000872974003 CR4: 00000000001606e0
Call Trace:
 radeon_dp_get_dp_link_config+0x43/0x150 [radeon]
 radeon_dp_mode_valid_helper+0x4d/0xa0 [radeon]
 drm_helper_probe_single_connector_modes+0x4b3/0x6d0 [drm_kms_helper]
 drm_setup_crtcs+0x148/0xaa0 [drm_kms_helper]
 ? atombios_powergate_crtc+0x4c/0x70 [radeon]
 ? __drm_fb_helper_initial_config_and_unlock+0x3d/0x420 [drm_kms_helper]
 ? drm_modeset_unlock+0x16/0x40 [drm]
 ? _cond_resched+0x15/0x30
 ? radeon_fbdev_init+0x110/0x130 [radeon]
 ? radeon_modeset_init.cold.9+0x196/0x4ea [radeon]
 ? radeon_driver_load_kms+0xd8/0x300 [radeon]
 ? drm_dev_register+0x129/0x160 [drm]
 ? drm_get_pci_dev+0x96/0x180 [drm]
 ? local_pci_probe+0x41/0x90
 ? pci_device_probe+0x188/0x1a0
 ? driver_probe_device+0x2b9/0x460
 ? __driver_attach+0xb6/0xe0
 ? driver_probe_device+0x460/0x460
 ? bus_for_each_dev+0x76/0xc0
 ? klist_add_tail+0x3b/0x60
 ? bus_add_driver+0x152/0x230
 ? driver_register+0x6b/0xb0
 ? 0xffffffffc03e5000
 ? do_one_initcall+0x48/0x13b
 ? _cond_resched+0x15/0x30
 ? kmem_cache_alloc_trace+0x111/0x1c0
 ? do_init_module+0x22/0x210
 ? do_init_module+0x5a/0x210
 ? load_module+0x210f/0x24a0
 ? SYSC_init_module+0x138/0x180
 ? SYSC_init_module+0x138/0x180
 ? do_syscall_64+0x74/0x180
 ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Code: 08 00 40 80 ff 14 74 2e b8 d0 78 02 00 40 80 ff 06 74 23 48 83 ec 08 40 0f b6 f7 48 c7 c7 98 bb 1f c0 89 44 24 04 e8 5c 25 ec c8 <0f> 0b 8b 44 24 04 48 83 c4 08 c3 c3 66 0f 1f 44 00 00 0f 1f 44

Comment 1 Dan Loomis 2018-06-02 14:52:16 UTC
Created attachment 1447033 [details]
File: dmesg

Comment 2 Justin M. Forbes 2018-07-23 15:00:34 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.

Fedora 28 has now been rebased to 4.17.7-200.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2018-08-29 15:08:32 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.