From: Mario Limonciello <mario.limonciello@amd.com>
To: "Paweł Frelek" <pawel.frelek@gmail.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
westeri@kernel.org, linux-usb@vger.kernel.org,
andreas.noever@gmail.com, YehezkelShB@gmail.com,
Sanath S <Sanath.S@amd.com>,
Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Subject: Re: [BUG] thunderbolt: NULL pointer dereference in tb_dp_dprx_work after device disconnect (7.2.6)
Date: Tue, 20 Oct 2026 08:49:13 -0500 [thread overview]
Message-ID: <a9cfb8f4-1bfa-4d4c-af0f-9166c295300b@amd.com> (raw)
In-Reply-To: <CABL4uFkv9E1e1qbM-e_5-sS+wvV95Mxm3V79LUftbLDSebAddA@mail.gmail.com>
On 10/20/26 08:41, Paweł Frelek wrote:
> pon., 19 paź 2026 o 23:00 Mario Limonciello
> <mario.limonciello@amd.com> napisał(a):
>> I have a few patches I was going to propose for this area. Can you see
>> if these help?
>
> Hi Mario,
>
> These are the same three patches you shared on
> https://gitlab.freedesktop.org/drm/amd/-/issues/5981 on Oct 15.
>
> I tested them on v7.3. 0002 and 0003 apply cleanly. 0001 doesn’t
> apply, so I ported it by hand with a lot of help from Claude (AI):
> amdgpu_dm_release_irq_stream() is a plain static function placed
> before manage_dm_interrupts(), with no header change and the KUnit
> test left out. The port is attached in case I got something wrong.
>
> Test: power off the external monitors, wait 60 s, power them on
> again, done 3 times, each from a fresh boot.
>
> “Sending link address failed with -5”: 2 of 3
> “Step 2 of creating MST payload failed: -5”: 1 of 3
> link_hwss_dpia WARN (line 60 with 0002 applied): 1 of 3
>
> For comparison, with only 0002+0003 on v7.3 (2 tries) I had the
> “Step 2” error 2 of 2 and the dpia WARN 1 of 2.
>
> Thanks,
> Paweł
>
>
>
Thanks, it hadn't occurred to me you were the OP for that issue :)
Let's continue to follow up on the gitlab ticket.
prev parent reply other threads:[~2026-10-20 13:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 14:48 [BUG] thunderbolt: NULL pointer dereference in tb_dp_dprx_work after device disconnect (7.2.6) Paweł Frelek
2026-09-24 16:28 ` Paweł Frelek
2026-09-25 5:29 ` Mika Westerberg
2026-10-13 15:31 ` Paweł Frelek
2026-10-16 5:58 ` Mika Westerberg
2026-10-16 16:55 ` Paweł Frelek
2026-10-16 17:20 ` Paweł Frelek
2026-10-19 6:11 ` Mika Westerberg
2026-10-19 17:43 ` Paweł Frelek
2026-10-19 21:00 ` Mario Limonciello
2026-10-20 13:41 ` Paweł Frelek
2026-10-20 13:49 ` Mario Limonciello [this message]
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=a9cfb8f4-1bfa-4d4c-af0f-9166c295300b@amd.com \
--to=mario.limonciello@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Sanath.S@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pawel.frelek@gmail.com \
--cc=westeri@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox