From: Genes Lists <lists@sapience.com>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk, sagi@grimberg.me,
linux-nvme@lists.infradead.org, hch@lst.de, arnd@arndb.de,
ricky_wu@realtek.com, gregkh@linuxfoundation.org
Subject: Re: Possible nvme regression in 6.4.11
Date: Thu, 17 Aug 2023 05:16:01 -0400 [thread overview]
Message-ID: <570d465a-7500-4b58-98f0-fd781c8740cc@sapience.com> (raw)
In-Reply-To: <30b69186-5a6e-4f53-b24c-2221926fc3b4@sapience.com>
On 8/16/23 21:30, Genes Lists wrote:
> On 8/16/23 17:04, Keith Busch wrote:
> ...
>> It sounds like you can recreate this. Since .10 worked and .11 doesn't,
>> could you bisect the git commits? It looks like it will take 7 steps
>> between those two versions.
>>
>> I don't think there are any nvme specific patches that could contribute
>> to what you're seeing, it's more likely some lower level platform patch
>> if a kernel change really did cause the regression. None of the recent
>> commits really stood out to me, so bisect is what I'd recommend.
>
> Thank you
>
> Bisect done - This is result:
>
> ----------------------------------------------------------------
> 69304c8d285b77c9a56d68f5ddb2558f27abf406 is the first bad commit
> commit 69304c8d285b77c9a56d68f5ddb2558f27abf406
> Author: Ricky WU <ricky_wu@realtek.com>
> Date: Tue Jul 25 09:10:54 2023 +0000
>
> misc: rtsx: judge ASPM Mode to set PETXCFG Reg
>
> commit 101bd907b4244a726980ee67f95ed9cafab6ff7a upstream.
>
> ASPM Mode is ASPM_MODE_CFG need to judge the value of clkreq_0
> to set HIGH or LOW, if the ASPM Mode is ASPM_MODE_REG
> always set to HIGH during the initialization.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Ricky Wu <ricky_wu@realtek.com>
> Link:
> https://lore.kernel.org/r/52906c6836374c8cb068225954c5543a@realtek.com
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> drivers/misc/cardreader/rts5227.c | 2 +-
> drivers/misc/cardreader/rts5228.c | 18 ------------------
> drivers/misc/cardreader/rts5249.c | 3 +--
> drivers/misc/cardreader/rts5260.c | 18 ------------------
> drivers/misc/cardreader/rts5261.c | 18 ------------------
> drivers/misc/cardreader/rtsx_pcr.c | 5 ++++-
> 6 files changed, 6 insertions(+), 58 deletions(-)
>
> ------------------------------------------------------
>
> And the machine does have this hardware:
>
> 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A
> PCI Express Card Reader (rev 01)
> Subsystem: Dell RTS525A PCI Express Card Reader
> Physical Slot: 1
> Flags: bus master, fast devsel, latency 0, IRQ 141
> Memory at ed100000 (32-bit, non-prefetchable) [size=4K]
> Capabilities: [80] Power Management version 3
> Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit+
> Capabilities: [b0] Express Endpoint, MSI 00
> Kernel driver in use: rtsx_pci
> Kernel modules: rtsx_pci
>
>
>
Adding to CC list since bisect landed on
drivers/misc/cardreader/rtsx_pcr.c
Thread starts here: https://lkml.org/lkml/2023/8/16/1154
Thank you,
gene
next prev parent reply other threads:[~2023-08-17 9:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 20:39 Genes Lists
2023-08-16 21:04 ` Keith Busch
2023-08-17 1:30 ` Genes Lists
2023-08-17 9:16 ` Genes Lists [this message]
2023-08-17 17:28 ` Keith Busch
2023-08-17 17:43 ` Genes Lists
2023-08-23 17:41 ` Keith Busch
2023-08-23 20:25 ` Genes Lists
2023-08-24 2:44 ` Ricky WU
2023-08-24 9:48 ` Genes Lists
2023-08-24 10:22 ` Genes Lists
2023-08-25 12:51 ` Ricky WU
2023-08-30 21:09 ` Genes Lists
2023-09-11 8:02 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-11 11:38 ` Thorsten Leemhuis
2023-09-18 17:07 ` [Revert] " Jade Lovelace
2023-09-18 17:07 ` [PATCH] Revert "misc: rtsx: judge ASPM Mode to set PETXCFG Reg" Jade Lovelace
2023-09-11 15:41 ` Possible nvme regression in 6.4.11 Augusto Zanellato
2023-08-24 11:29 ` Genes Lists
2023-08-17 3:00 ` Bagas Sanjaya
2023-09-29 11:49 ` Linux regression tracking #update (Thorsten Leemhuis)
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=570d465a-7500-4b58-98f0-fd781c8740cc@sapience.com \
--to=lists@sapience.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ricky_wu@realtek.com \
--cc=sagi@grimberg.me \
/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
all inboxes | Powered by JetHome®