Broken Fujitsu BIOS pokes at eDP VDD from ACPI AML code
Hi!
Im using a FUJITSU LifeBook U9312X on the latest drm-tip 6.1.0-rc3+ on X86_64.
Distro: Gentoo
During boot I always get:
[ 4.834189] ------------[ cut here ]------------
[ 4.834194] i915 0000:00:02.0: drm_WARN_ON(intel_dp->pps.vdd_wakeref)
[ 4.834204] WARNING: CPU: 2 PID: 9 at drivers/gpu/drm/i915/display/intel_pps.c:595 intel_pps_vdd_on_unlocked+0x27f/0x290
[ 4.834214] Modules linked in:
[ 4.834216] CPU: 2 PID: 9 Comm: kworker/u24:0 Not tainted 6.1.0-rc3+ #1
[ 4.834219] Hardware name: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U9312X/FJNB2F8, BIOS Version 2.11 09/02/2022
[ 4.834221] Workqueue: events_unbound async_run_entry_fn
[ 4.834225] RIP: 0010:intel_pps_vdd_on_unlocked+0x27f/0x290
[ 4.834229] Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 ea 76 11 00 48 c7 c1 48 68 7c 82 4c 89 ea 48 c7 c7 8f 9b 78 82 48 89 c6 e8 7b eb 6d 00 <0f> 0b e9 12 fe ff ff e8 05 9b 76 00 0f 1f 44 00 00 41 54 55 53 48
[ 4.834232] RSP: 0018:ffffc900000c3918 EFLAGS: 00010286
[ 4.834235] RAX: 0000000000000000 RBX: ffff888103210170 RCX: 00000000ffffdfff
[ 4.834238] RDX: 0000000000000000 RSI: 00000000ffffffea RDI: 0000000000000001
[ 4.834239] RBP: ffff888100920000 R08: ffffffff82b32048 R09: 00000000ffffdfff
[ 4.834241] R10: ffffffff82a52060 R11: ffffffff82b06338 R12: 0000000000000001
[ 4.834242] R13: ffff88810117cab0 R14: ffff888100921d10 R15: ffff888100920000
[ 4.834244] FS: 0000000000000000(0000) GS:ffff88849f480000(0000) knlGS:0000000000000000
[ 4.834246] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4.834248] CR2: 00000000004133e9 CR3: 0000000002a0c001 CR4: 0000000000770ee0
[ 4.834250] PKRU: 55555554
[ 4.834251] Call Trace:
[ 4.834253] <TASK>
[ 4.834255] ? intel_display_power_get+0x4d/0x60
[ 4.834260] intel_dp_aux_xfer+0xe7/0x6f0
[ 4.834265] ? _get_random_bytes.part.0+0x47/0x190
[ 4.834269] intel_dp_aux_transfer+0xe0/0x2a0
[ 4.834273] drm_dp_dpcd_access+0x68/0x120
[ 4.834277] drm_dp_dpcd_probe+0x35/0xf0
[ 4.834281] drm_dp_dpcd_read+0xbb/0x100
[ 4.834284] intel_dp_get_dsc_sink_cap+0x5f/0x160
[ 4.834287] intel_dp_detect+0x4f0/0x680
[ 4.834291] drm_helper_probe_detect+0x41/0xa0
[ 4.834296] drm_helper_probe_single_connector_modes+0x473/0x540
[ 4.834298] drm_client_modeset_probe+0x210/0x1460
[ 4.834304] ? sched_clock_local+0xe/0x80
[ 4.834306] __drm_fb_helper_initial_config_and_unlock+0x3f/0x4e0
[ 4.834309] ? __switch_to_asm+0x3a/0x60
[ 4.834312] intel_fbdev_initial_config+0xf/0x20
[ 4.834314] async_run_entry_fn+0x18/0xa0
[ 4.834316] process_one_work+0x1b1/0x310
[ 4.834320] worker_thread+0x48/0x3c0
[ 4.834323] ? process_one_work+0x310/0x310
[ 4.834325] kthread+0xd1/0x100
[ 4.834328] ? kthread_complete_and_exit+0x20/0x20
[ 4.834331] ret_from_fork+0x1f/0x30
[ 4.834333] </TASK>
[ 4.834334] ---[ end trace 0000000000000000 ]---
Additional I have the same behavior during Suspend as in #7378 (closed).
Best regards, Martin