[Bug 102202] "ERROR Requesting EDID firmware" (with amdgpu and EDID file)
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Aug 13 21:52:16 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=102202
Bug ID: 102202
Summary: "ERROR Requesting EDID firmware" (with amdgpu and EDID
file)
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel at lists.freedesktop.org
Reporter: jb5sgc1n.nya at 20mm.eu
I'm driving an LG 4k TV with an 4k HDMI signal from a RX 460 card, using the
amdgpu driver.
Since the TV is not always on when the computer is booted or woken up from S3
sleep, I dumped the TV's EDID to a file and use the kernel command line option
drm_kms_helper.edid_firmware=edid/LG_EG9609_edid.bin
to consistently let the driver know about the connected TV. In general, this
works fine, the EDID parsing provides the proper modes to be used.
But after every reboot, and also after waking from S3 sleep, sometimes also
triggered when using "xrandr" to change the video mode, I see scary kernel log
messages like this one:
Aug 13 18:14:46 ryzen kernel: firmware request while host is not available
Aug 13 18:14:46 ryzen kernel: ------------[ cut here ]------------
Aug 13 18:14:46 ryzen kernel: WARNING: CPU: 0 PID: 28930 at
drivers/base/firmware_class.c:1225 _request_firmware+0x3fd/0x8c0
Aug 13 18:14:46 ryzen kernel: Modules linked in: arc4 md4 nls_utf8 cifs ccm
dns_resolver fscache joydev mousedev hid_generic hidp hid blowfish_generic
blowfish_x86_64 blowfish_common
Aug 13 18:14:46 ryzen kernel: ecdh_generic edac_mce_amd rfkill ptp crc16
snd_hda_core kvm_amd pps_core snd_hwdep dca snd_pcm sp5100_tco snd_timer kvm
snd soundcore irqbypass evdev i2
Aug 13 18:14:46 ryzen kernel: CPU: 0 PID: 28930 Comm: kworker/u32:67 Tainted: G
W O 4.13.0-rc2-amd+ #1
Aug 13 18:14:46 ryzen kernel: Hardware name: System manufacturer System Product
Name/PRIME X370-PRO, BIOS 0805 06/20/2017
Aug 13 18:14:46 ryzen kernel: Workqueue: events_unbound async_run_entry_fn
Aug 13 18:14:46 ryzen kernel: task: ffff88069769e040 task.stack:
ffffc90008484000
Aug 13 18:14:46 ryzen kernel: RIP: 0010:_request_firmware+0x3fd/0x8c0
Aug 13 18:14:46 ryzen kernel: RSP: 0018:ffffc900084879f8 EFLAGS: 00010282
Aug 13 18:14:46 ryzen kernel: RAX: 000000000000002c RBX: ffff8807891071a0 RCX:
000000000000001f
Aug 13 18:14:46 ryzen kernel: RDX: 0000000000000000 RSI: 0000000000000002 RDI:
ffffffff81c4ef40
Aug 13 18:14:46 ryzen kernel: RBP: ffffc90008487a58 R08: 0000000000000000 R09:
000000000000002c
Aug 13 18:14:46 ryzen kernel: R10: ffffea001a71b400 R11: 0000000000000e19 R12:
ffff880789107660
Aug 13 18:14:46 ryzen kernel: R13: ffffc90008487ab0 R14: 0000000000000000 R15:
ffffffff81a36338
Aug 13 18:14:46 ryzen kernel: FS: 0000000000000000(0000)
GS:ffff88081ec00000(0000) knlGS:0000000000000000
Aug 13 18:14:46 ryzen kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 13 18:14:46 ryzen kernel: CR2: 000000000066f008 CR3: 00000007b3576000 CR4:
00000000003406f0
Aug 13 18:14:46 ryzen kernel: Call Trace:
Aug 13 18:14:46 ryzen kernel: request_firmware+0x37/0x50
Aug 13 18:14:46 ryzen kernel: drm_load_edid_firmware+0x269/0x4d0
[drm_kms_helper]
Aug 13 18:14:46 ryzen kernel:
drm_helper_probe_single_connector_modes+0x296/0x780 [drm_kms_helper]
Aug 13 18:14:46 ryzen kernel: drm_setup_crtcs+0x139/0x9e0 [drm_kms_helper]
Aug 13 18:14:46 ryzen kernel: ? kobj_ns_drop+0x50/0x50
Aug 13 18:14:46 ryzen kernel: ? ww_mutex_lock+0x17/0x80
Aug 13 18:14:46 ryzen kernel: drm_fb_helper_hotplug_event.part.21+0x8f/0xb0
[drm_kms_helper]
Aug 13 18:14:46 ryzen kernel: drm_fb_helper_hotplug_event+0x1a/0x20
[drm_kms_helper]
Aug 13 18:14:46 ryzen kernel: amdgpu_fb_output_poll_changed+0x1a/0x20 [amdgpu]
Aug 13 18:14:46 ryzen kernel: amdgpu_output_poll_changed+0x12/0x20 [amdgpu]
Aug 13 18:14:46 ryzen kernel: drm_kms_helper_hotplug_event+0x27/0x30
[drm_kms_helper]
Aug 13 18:14:46 ryzen kernel: amdgpu_device_resume+0x3a1/0x3e0 [amdgpu]
Aug 13 18:14:46 ryzen kernel: amdgpu_pmops_resume+0x53/0x60 [amdgpu]
Aug 13 18:14:46 ryzen kernel: pci_pm_resume+0x65/0xa0
Aug 13 18:14:46 ryzen kernel: ? pci_pm_freeze+0xe0/0xe0
Aug 13 18:14:46 ryzen kernel: dpm_run_callback+0x53/0x140
Aug 13 18:14:46 ryzen kernel: device_resume+0xe1/0x200
Aug 13 18:14:46 ryzen kernel: async_resume+0x1d/0x50
Aug 13 18:14:46 ryzen kernel: async_run_entry_fn+0x36/0x150
Aug 13 18:14:46 ryzen kernel: process_one_work+0x1db/0x3e0
Aug 13 18:14:46 ryzen kernel: worker_thread+0x47/0x3e0
Aug 13 18:14:46 ryzen kernel: kthread+0x125/0x140
Aug 13 18:14:46 ryzen kernel: ? process_one_work+0x3e0/0x3e0
Aug 13 18:14:46 ryzen kernel: ? kthread_create_on_node+0x70/0x70
Aug 13 18:14:46 ryzen kernel: ret_from_fork+0x22/0x30
Aug 13 18:14:46 ryzen kernel: Code: 08 48 83 fb 28 74 45 48 8b 8b e0 70 87 81
e9 3c ff ff ff 48 c7 c7 20 2b cb 81 e8 df b1 1b 00 48 c7 c7 40 e8 a0 81 e8 c4
01 c8 ff <0f> ff 41 b9 90 f
Aug 13 18:14:46 ryzen kernel: ---[ end trace 006f0a6880b1aacb ]---
Aug 13 18:14:46 ryzen kernel: [drm:drm_load_edid_firmware [drm_kms_helper]]
*ERROR* Requesting EDID firmware "edid/LG_EG9609_edid.bin" failed (err=-112)
This would not bother me if only those messages were occuring, but I also
experience complete system lockups when I leave the computer display on (with
"xlock" running) and switch off the TV - these crashes seem to occur at the
time the screen blanker deactivates the monitor, but they leave no messages at
all in any logs I could cite. I've got the suspicion that both symptoms are
related (and maybe also related to
https://bugs.freedesktop.org/show_bug.cgi?id=100375 )
I am currently using
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next as my
kernel, but experienced the same error also with previous kernel versions (like
4.12)
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170813/d7967853/attachment-0001.html>
More information about the dri-devel
mailing list