From: Jani Nikula <jani.nikula@intel.com>
To: Raag Jadav <raag.jadav@intel.com>,
rodrigo.vivi@intel.com, lucas.demarchi@intel.com,
ville.syrjala@intel.com
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: Rare divide error during display resume
Date: Mon, 28 Apr 2025 10:31:23 +0300 [thread overview]
Message-ID: <87ldrkyc6s.fsf@intel.com> (raw)
In-Reply-To: <aA5xvOhy9qKiVcE0@black.fi.intel.com>
PCI ID of the platform?
On Sun, 27 Apr 2025, Raag Jadav <raag.jadav@intel.com> wrote:
> I came across this while testing an unrelated feature. It's not easily
> reproducible so thought I'd share here.
>
> [ 1802.992726] PM: suspend entry (s2idle)
> [ 1802.993986] Filesystems sync: 0.001 seconds
> [ 1826.223060] xe 0000:03:00.0: [drm] *ERROR* Writing dc state to 0xbffffff4 failed, now 0xffffffff
> [ 1826.315308] xe 0000:03:00.0: [drm] *ERROR* DC state mismatch (0x0 -> 0x4000000b)
> [ 1830.528929] xe 0000:03:00.0: [drm] *ERROR* Writing dc state to 0xbffffff4 failed, now 0xffffffff
> [ 1831.130028] xe 0000:03:00.0: [drm] *ERROR* timeout waiting for CDCLK PLL unlock
> [ 1831.140420] Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI
> [ 1831.145976] CPU: 14 UID: 0 PID: 9834 Comm: kworker/u128:32 Kdump: loaded Tainted: G U W 6.14.0-xe+ #14
> [ 1831.156426] Tainted: [U]=USER, [W]=WARN
> [ 1831.160246] Hardware name: Intel Corporation Raptor Lake Client Platform/RPL-S ADP-S DDR5 UDIMM CRB, BIOS RPLSFWI1.R00.5045.A00.2401260733 01/26/2024
> [ 1831.173536] Workqueue: async async_run_entry_fn
> [ 1831.178051] RIP: 0010:bxt_cdclk_ctl.isra.0+0x6c/0x2a0 [xe]
> [ 1831.183599] Code: c2 c1 e1 04 0f b7 f8 f3 0f b8 c7 90 0f af c3 85 c0 40 0f 9e c6 85 c9 0f 9f c2 40 38 d6 89 ca 0f 84 71 01 00 00 d1 fa 01 d0 99 <f7> f9 83 f8 04 0f 84 71 01 00 00 0f 8f 90 00 00 00 45 31 ff 83 f8
> [ 1831.202219] RSP: 0018:ffffc9000b69fa18 EFLAGS: 00010246
> [ 1831.207419] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
> [ 1831.214515] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 000000000000ffff
> [ 1831.221611] RBP: ffffc9000b69fa58 R08: 0000000000000000 R09: ffffc9000b69f858
> [ 1831.228706] R10: ffffc9000b69f850 R11: ffff88888c5fffe8 R12: 0000000000000000
> [ 1831.235796] R13: ffff888173adb3f0 R14: ffffffffffffffff R15: 0000000000000000
> [ 1831.242891] FS: 0000000000000000(0000) GS:ffff88888d500000(0000) knlGS:0000000000000000
> [ 1831.250931] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 1831.256647] CR2: 00005632ddf55000 CR3: 0000000003258001 CR4: 0000000000f72ef0
> [ 1831.263741] PKRU: 55555554
> [ 1831.266450] Call Trace:
> [ 1831.268900] <TASK>
> [ 1831.271006] ? show_regs+0x6d/0x80
> [ 1831.274400] ? die+0x3c/0xa0
> [ 1831.277276] ? do_trap+0xcf/0xf0
> [ 1831.280497] ? do_error_trap+0x7a/0x100
> [ 1831.284319] ? bxt_cdclk_ctl.isra.0+0x6c/0x2a0 [xe]
> [ 1831.289264] ? exc_divide_error+0x3f/0x60
> [ 1831.293260] ? bxt_cdclk_ctl.isra.0+0x6c/0x2a0 [xe]
> [ 1831.298200] ? asm_exc_divide_error+0x1f/0x30
> [ 1831.302539] ? bxt_cdclk_ctl.isra.0+0x6c/0x2a0 [xe]
> [ 1831.307479] ? bxt_cdclk_ctl.isra.0+0x35/0x2a0 [xe]
> [ 1831.312421] ? cdclk_squash_waveform+0x9f/0xc0 [xe]
> [ 1831.317361] _bxt_set_cdclk+0x295/0x650 [xe]
> [ 1831.321699] bxt_set_cdclk+0x80/0x570 [xe]
> [ 1831.325863] ? bxt_calc_cdclk_pll_vco+0xa2/0xc0 [xe]
> [ 1831.330890] intel_cdclk_init_hw+0x238/0x470 [xe]
> [ 1831.335655] icl_display_core_init+0xde/0x800 [xe]
> [ 1831.340513] intel_power_domains_init_hw+0x1bc/0x660 [xe]
> [ 1831.345972] intel_power_domains_resume+0xa4/0x100 [xe]
> [ 1831.351256] intel_display_power_resume_early+0x5a/0xf0 [xe]
> [ 1831.356971] xe_display_pm_resume_early+0x27/0x30 [xe]
> [ 1831.362172] xe_pm_resume+0x12c/0x280 [xe]
> [ 1831.366324] ? __pfx_pci_pm_resume+0x10/0x10
> [ 1831.370580] xe_pci_resume+0x60/0x70 [xe]
> [ 1831.374645] pci_pm_resume+0x78/0x110
> [ 1831.378300] dpm_run_callback+0x58/0x100
> [ 1831.382213] device_resume+0x13c/0x350
> [ 1831.385950] ? __pfx_dpm_watchdog_handler+0x10/0x10
> [ 1831.390808] async_resume+0x22/0x40
> [ 1831.394287] async_run_entry_fn+0x36/0x140
> [ 1831.398368] process_one_work+0x217/0x680
> [ 1831.402365] worker_thread+0x1a2/0x340
> [ 1831.406103] ? __pfx_worker_thread+0x10/0x10
> [ 1831.410358] kthread+0x10b/0x270
> [ 1831.413585] ? __pfx_kthread+0x10/0x10
> [ 1831.417324] ret_from_fork+0x3d/0x60
> [ 1831.420894] ? __pfx_kthread+0x10/0x10
> [ 1831.424632] ret_from_fork_asm+0x1a/0x30
> [ 1831.428546] </TASK>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-04-28 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 18:04 Rare divide error during display resume Raag Jadav
2025-04-28 7:31 ` Jani Nikula [this message]
2025-04-28 7:59 ` Raag Jadav
2025-04-28 19:46 ` Vivi, Rodrigo
2025-05-02 12:43 ` Raag Jadav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ldrkyc6s.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=raag.jadav@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.