This morning I booted Linus' latest tree which is after the DRM merge. I have a MacBookPro 10,2 that produces the following backtrace: [ 1.970292] ------------[ cut here ]------------ [ 1.970319] WARNING: CPU: 0 PID: 107 at drivers/gpu/drm/i915/intel_audio.c:294 ilk_audio_codec_disable+0x170/0x1b0 [i915]() [ 1.970321] WARN_ON(!port) [ 1.970327] Modules linked in: i915 i2c_algo_bit drm_kms_helper drm video [ 1.970330] CPU: 0 PID: 107 Comm: kworker/u16:6 Not tainted 3.20.0-0.rc0.git7.1.fc23.x86_64 #1 [ 1.970332] Hardware name: Apple Inc. MacBookPro10,2/Mac-AFD8A9D944EA4843, BIOS MBP102.88Z.0106.B03.1211161133 11/16/2012 [ 1.970336] Workqueue: events_unbound async_run_entry_fn [ 1.970340] 0000000000000000 0000000002cedd04 ffff880087ac7538 ffffffff81876738 [ 1.970343] 0000000000000000 ffff880087ac7590 ffff880087ac7578 ffffffff810ab5da [ 1.970355] ffff880260750000 ffff880260750000 00000000fffffeee 0000000030000000 [ 1.970356] Call Trace: [ 1.970359] [<ffffffff81876738>] dump_stack+0x4c/0x65 [ 1.970363] [<ffffffff810ab5da>] warn_slowpath_common+0x8a/0xc0 [ 1.970365] [<ffffffff810ab665>] warn_slowpath_fmt+0x55/0x70 [ 1.970387] [<ffffffffa0102d60>] ilk_audio_codec_disable+0x170/0x1b0 [i915] [ 1.970408] [<ffffffffa010376e>] intel_audio_codec_disable+0x1e/0x30 [i915] [ 1.970430] [<ffffffffa013f99d>] intel_disable_dp+0x9d/0xe0 [i915] [ 1.970462] [<ffffffffa011720a>] ironlake_crtc_disable+0x16a/0x800 [i915] [ 1.970484] [<ffffffffa01187e4>] __intel_set_mode+0x984/0xb50 [i915] [ 1.970506] [<ffffffffa011fb8b>] intel_crtc_set_config+0xc4b/0x1030 [i915] [ 1.970521] [<ffffffffa002ed17>] ? drm_atomic_state_free+0x27/0x60 [drm] [ 1.970532] [<ffffffffa001e9e9>] drm_mode_set_config_internal+0x69/0x120 [drm] [ 1.970538] [<ffffffffa00867d8>] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] [ 1.970544] [<ffffffffa0088849>] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x80 [drm_kms_helper] [ 1.970548] [<ffffffffa00888c2>] drm_fb_helper_set_par+0x22/0x50 [drm_kms_helper] [ 1.970573] [<ffffffffa012f25a>] intel_fbdev_set_par+0x1a/0x60 [i915] [ 1.970604] [<ffffffff8149e518>] fbcon_init+0x588/0x610 [ 1.970608] [<ffffffff8153965c>] visual_init+0xbc/0x120 [ 1.970610] [<ffffffff8153c03e>] do_bind_con_driver+0x17e/0x3c0 [ 1.970613] [<ffffffff8153c7e4>] do_take_over_console+0xb4/0x1b0 [ 1.970616] [<ffffffff81499313>] do_fbcon_takeover+0x63/0xd0 [ 1.970619] [<ffffffff8149f06d>] fbcon_event_notify+0x6dd/0x7e0 [ 1.970624] [<ffffffff810d50f2>] notifier_call_chain+0x62/0x100 [ 1.970627] [<ffffffff810d53a1>] __blocking_notifier_call_chain+0x51/0x70 [ 1.970630] [<ffffffff810d53d6>] blocking_notifier_call_chain+0x16/0x20 [ 1.970633] [<ffffffff814a510b>] fb_notifier_call_chain+0x1b/0x20 [ 1.970635] [<ffffffff814a75c2>] register_framebuffer+0x222/0x370 [ 1.970641] [<ffffffffa0088b54>] drm_fb_helper_initial_config+0x264/0x3c0 [drm_kms_helper] [ 1.970665] [<ffffffffa013058b>] intel_fbdev_initial_config+0x1b/0x20 [i915] [ 1.970667] [<ffffffff810d79da>] async_run_entry_fn+0x4a/0x150 [ 1.970669] [<ffffffff810ccc25>] process_one_work+0x215/0x860 [ 1.970672] [<ffffffff810ccb8e>] ? process_one_work+0x17e/0x860 [ 1.970674] [<ffffffff810cd36b>] ? worker_thread+0xfb/0x490 [ 1.970676] [<ffffffff810cd2db>] worker_thread+0x6b/0x490 [ 1.970679] [<ffffffff810cd270>] ? process_one_work+0x860/0x860 [ 1.970681] [<ffffffff810d378f>] kthread+0x11f/0x140 [ 1.970684] [<ffffffff810e9a05>] ? local_clock+0x25/0x30 [ 1.970688] [<ffffffff810d3670>] ? kthread_create_on_node+0x250/0x250 [ 1.970691] [<ffffffff8188077c>] ret_from_fork+0x7c/0xb0 [ 1.970693] [<ffffffff810d3670>] ? kthread_create_on_node+0x250/0x250 [ 1.970695] ---[ end trace d0ffc484dcd1cb40 ]---
Please add drm.debug=14 module parameter and provide dmesg from boot to problem.
Best guess before further info, bios is silly and enables audio on eDP.
Created attachment 113577 [details] drm.debug=14 dmesg Requested dmesg. And it's a macbook. So the firmware is guaranteed to be stupid.
Yes, looks like the firmware is stupid. But in theory we could also get the warning by forcing audio on for eDP port A. Needs to be fixed, but there's no need to worry about the warning per se. It's a sanity check, which accomplished its intented purpose by detecting insanity.
(In reply to Jani Nikula from comment #4) > Yes, looks like the firmware is stupid. But in theory we could also get the > warning by forcing audio on for eDP port A. Needs to be fixed, but there's > no need to worry about the warning per se. It's a sanity check, which > accomplished its intented purpose by detecting insanity. OK, thanks. I wasn't overly worried about it other than the fact that it will get auto-filed by things like ABRT. I could probably just locally comment it out if it becomes an issue.
*** This bug has been marked as a duplicate of bug 89958 ***
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.