From: Ricky WU <ricky_wu@realtek.com>
To: Paul Grandperrin <paul.grandperrin@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
Wei_wang <wei_wang@realsil.com.cn>,
Roger Tseng <rogerable@realtek.com>
Subject: RE: Regression since 6.1.46 (commit 8ee39ec): rtsx_pci from drivers/misc/cardreader breaks NVME power state, preventing system boot
Date: Wed, 13 Sep 2023 03:10:14 +0000 [thread overview]
Message-ID: <c7bdd821686e496eb31e4298050dfb72@realtek.com> (raw)
In-Reply-To: <5DHV0S.D0F751ZF65JA1@gmail.com>
Hi Paul,
We have notice this issue....
https://lore.kernel.org/lkml/fa82d9dcbe83403abc644c20922b47f9@realtek.com/t/#m90373a16017f07ca32f43d6b4327164fb31bf9bb
main reason is:
"it is a system power saving issue....
In the past if the BIOS(config space) not set L1-substate our driver will keep drive low CLKREQ# when HOST want to enter power saving state that make whole system not enter the power saving state.
But this patch we release the CLKREQ# to HOST, make whole system can enter power saving state success when the HOST want to enter the power saving state, but I don't know why this system can not wake out success from power saving state"
This is a PCIE CLKREQ# design problem on those platform, the pcie spec allow device release the CLKREQ# to HOST, this patch only do this....
We are thinking about how to compatible with these potentially problematic platforms
Ricky
> -----Original Message-----
> From: Paul Grandperrin <paul.grandperrin@gmail.com>
> Sent: Tuesday, September 12, 2023 8:29 PM
> To: stable@vger.kernel.org
> Cc: regressions@lists.linux.dev; Wei_wang <wei_wang@realsil.com.cn>; Roger
> Tseng <rogerable@realtek.com>; Ricky WU <ricky_wu@realtek.com>
> Subject: Regression since 6.1.46 (commit 8ee39ec): rtsx_pci from
> drivers/misc/cardreader breaks NVME power state, preventing system boot
>
>
> External mail.
>
>
>
> Hi kernel maintainers!
>
> My computer doesn't boot with kernels newer than 6.1.45.
>
> Here's what happens:
> - system boots in initramfs
> - detects my encrypted ZFS pool and asks for password
> - mount system, pivots to it, starts real init
> - before any daemon had time to start, the system hangs and the kernel
> writes on the console
> "nvme 0000:04:00.0: Unable to change power state from D3cold to D0,
> device inaccessible"
> - if I reboot directly without powering off (using magic sysrq or
> panic=10), even the UEFI complains about not finding any storage to
> boot from.
> - after a real power off, I can boot using a kernel <= 6.1.45.
>
> The bug has been discussed here:
> https://bugzilla.kernel.org/show_bug.cgi?id=217705
>
> My laptop is a Dell XPS 15 9560 (Intel 7700hq).
>
> I bisected between 6.1.45 and 6.1.46 and found this commit
>
> commit 8ee39ec479147e29af704639f8e55fce246ed2d9
> 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(-)
>
> If I build 6.1.51 with this commit reverted, my laptop works again,
> confirming that this commit is to blame.
>
> Also, blacklisting `rtsx_pci_sdmmc` and `rtsx_pci`, while preventing to
> use the sd card reading, allows to boot the system.
>
> I can't try 6.4 or 6.5 because my system is dependent on ZFS..
>
> Have a nice day,
> Paul Grandperrin
>
next prev parent reply other threads:[~2023-09-13 3:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 12:29 Regression since 6.1.46 (commit 8ee39ec): rtsx_pci from drivers/misc/cardreader breaks NVME power state, preventing system boot Paul Grandperrin
2023-09-12 17:10 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-13 5:03 ` Greg KH
2023-09-19 2:20 ` Ricky WU
2023-09-19 7:06 ` Greg KH
2023-09-20 7:30 ` Ricky WU
2023-09-20 7:34 ` Greg KH
2023-09-20 8:32 ` Ricky WU
2023-09-26 11:23 ` Salvatore Bonaccorso
2023-09-26 11:51 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-20 9:33 ` Paul Grandperrin
2023-09-13 3:10 ` Ricky WU [this message]
2023-09-19 8:04 ` Jade Lovelace
2023-09-19 9:11 ` Ricky WU
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=c7bdd821686e496eb31e4298050dfb72@realtek.com \
--to=ricky_wu@realtek.com \
--cc=paul.grandperrin@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=rogerable@realtek.com \
--cc=stable@vger.kernel.org \
--cc=wei_wang@realsil.com.cn \
/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