From: Mario Limonciello <mario.limonciello@amd.com>
To: Alvin Lim <alvinwylim@gmail.com>,
mikael1022bzh@gmail.com, cassel@kernel.org
Cc: roland.waltersson@netinsight.net, artmoty@gmail.com,
linux-ide@vger.kernel.org, david.laight.linux@gmail.com,
kernel@wantstofly.org
Subject: Re: [PATCH] ahci: force 32-bit DMA for JMicron JMB582/JMB585
Date: Sat, 5 Sep 2026 07:26:49 -0500 [thread overview]
Message-ID: <1c3df04b-7929-4b43-adb7-6007347a954e@amd.com> (raw)
In-Reply-To: <20260905113848.1397882-1-alvinwylim@gmail.com>
< snip >
> So: tell me which test would actually be useful and I will run it and
> report the result either way, including a negative one. I would rather
> spend the window on the question you want answered than guess at it.
>
> Alvin Lim
Two things:
1. lspci -ttvvnn
2. Turn on amd_smn_debugfs_enable=1 on kernel command line.
Then use debugfs to get me the outputs from the SMN reads of these
registers:
0x111401d0,
0x111411d0,
0x111421d0,
0x111431d0,
0x111441d0,
0x112401d0,
0x112411d0,
0x112421d0,
0x112431d0,
0x112441d0,
0x112451d0,
0x113401d0,
0x114401d0,
Something like this might work.
sudo bash <<'EOF'
set -euo pipefail
if ! mountpoint -q /sys/kernel/debug; then
mount -t debugfs debugfs /sys/kernel/debug
fi
dir=/sys/kernel/debug/x86/amd_smn
test -d "$dir" || {
echo "Missing $dir; verify CONFIG_DEBUG_FS and
amd_smn_debugfs_enable=1"
exit 1
}
addresses=(
0x111401d0
0x111411d0
0x111421d0
0x111431d0
0x111441d0
0x112401d0
0x112411d0
0x112421d0
0x112431d0
0x112441d0
0x112451d0
0x113401d0
0x114401d0
)
printf '0\n' > "$dir/node"
for address in "${addresses[@]}"; do
printf '%s\n' "$address" > "$dir/address"
old=$(cat "$dir/value")
[[ $old =~ ^0x[[:xdigit:]]{8}$ ]] || {
echo "$address: invalid read: $old"
exit 1
}
printf '%s: %s\n' "$address" "$old"
done
EOF
next prev parent reply other threads:[~2026-09-05 12:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 13:35 [PATCH] ahci: force 32-bit DMA for JMicron JMB582/JMB585 Roland Waltersson
2026-09-03 21:40 ` Niklas Cassel
2026-09-03 22:36 ` Mario Limonciello
2026-09-04 5:20 ` Roland Waltersson
2026-09-04 11:14 ` Niklas Cassel
2026-09-04 12:38 ` Mario Limonciello
2026-09-04 12:50 ` Niklas Cassel
2026-09-04 16:55 ` Mikael Etienne
2026-09-05 11:38 ` Alvin Lim
2026-09-05 12:26 ` Mario Limonciello [this message]
2026-09-06 5:05 ` Alvin Lim
2026-09-06 19:27 ` John Smith
2026-09-05 14:13 ` Lennert Buytenhek
[not found] <AM8P193MB2659454F98AD53DEB002CF8AA9B42@AM8P193MB2659.EURP193.PROD.OUTLOOK.COM>
2026-09-07 10:28 ` Niklas Cassel
-- strict thread matches above, loose matches on Subject: below --
2026-09-06 11:48 snoep
2026-04-03 5:04 Arthur Husband
2026-04-03 7:02 ` Damien Le Moal
2026-04-03 8:12 ` Niklas Cassel
2026-04-03 8:19 ` Niklas Cassel
2026-04-03 5:02 Arthur Husband
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=1c3df04b-7929-4b43-adb7-6007347a954e@amd.com \
--to=mario.limonciello@amd.com \
--cc=alvinwylim@gmail.com \
--cc=artmoty@gmail.com \
--cc=cassel@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=kernel@wantstofly.org \
--cc=linux-ide@vger.kernel.org \
--cc=mikael1022bzh@gmail.com \
--cc=roland.waltersson@netinsight.net \
/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.