From: Askar Safin <safinaskar@gmail.com>
To: ville.syrjala@linux.intel.com
Cc: alex.zuo@intel.com, chris.p.wilson@linux.intel.com,
intel-gfx@lists.freedesktop.org, jia.yao@intel.com,
piliu@redhat.com, shuicheng.lin@intel.com
Subject: Re: [PATCH v2] drm/i915: Setting/clearing the memory access bit when en/disabling i915
Date: Sat, 11 Oct 2025 15:35:43 +0300 [thread overview]
Message-ID: <20251011123546.3085-1-safinaskar@gmail.com> (raw)
In-Reply-To: <aOaOJ1YI-NgTloIy@intel.com>
"Ville Syrjälä" <ville.syrjala@linux.intel.com>:
> I was asking you whether that invalid access was caused by that
> pxp stuff or not?
I just tested patch, which adds intel_pxp_fini(i915) to
i915_driver_shutdown and does nothing else.
The bug was not fixed.
Also, do you have machines for testing, except for my laptop? :)
Anyway, if you want me to test something, just ask.
--
Askar Safin
next prev parent reply other threads:[~2025-10-13 19:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 18:06 [PATCH] drm/i915: Setting/clearing the memory access bit when enabling/disabling i915 Jia Yao
2025-10-07 20:25 ` [PATCH v2] drm/i915: Setting/clearing the memory access bit when en/disabling i915 Jia Yao
2025-10-07 21:25 ` Ville Syrjälä
2025-10-07 21:40 ` Yao, Jia
2025-10-08 12:21 ` Ville Syrjälä
2025-10-08 16:06 ` Yao, Jia
2025-10-08 16:15 ` Ville Syrjälä
2025-10-08 17:14 ` Yao, Jia
2025-10-09 1:55 ` Pingfan Liu
2025-10-11 12:35 ` Askar Safin [this message]
2025-10-11 12:49 ` Askar Safin
2025-10-13 16:16 ` Yao, Jia
2025-10-14 6:29 ` Pingfan Liu
2025-11-01 16:02 ` Askar Safin
2025-10-08 5:17 ` Pingfan Liu
2025-10-08 7:05 ` Yao, Jia
2025-10-08 10:58 ` Pingfan Liu
2025-10-08 8:50 ` Askar Safin
2025-10-09 1:10 ` Askar Safin
2025-10-08 4:06 ` ✓ i915.CI.BAT: success for drm/i915: Setting/clearing the memory access bit when enabling/disabling i915 Patchwork
2025-10-08 4:29 ` ✓ i915.CI.BAT: success for drm/i915: Setting/clearing the memory access bit when enabling/disabling i915 (rev2) Patchwork
2026-01-20 4:42 ` [PATCH v3] drm/i915: Clearing the Memory Space Enable bit when disabling i915 Jia Yao
2026-01-20 9:50 ` Jani Nikula
2026-01-21 21:51 ` Yao, Jia
2026-01-20 16:11 ` Ville Syrjälä
2026-01-21 7:19 ` Yao, Jia
2026-01-21 15:02 ` Ville Syrjälä
2026-01-22 6:43 ` Yao, Jia
2026-01-20 5:31 ` ✗ i915.CI.BAT: failure for drm/i915: Setting/clearing the memory access bit when enabling/disabling i915 (rev3) Patchwork
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=20251011123546.3085-1-safinaskar@gmail.com \
--to=safinaskar@gmail.com \
--cc=alex.zuo@intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jia.yao@intel.com \
--cc=piliu@redhat.com \
--cc=shuicheng.lin@intel.com \
--cc=ville.syrjala@linux.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.