From: Salvatore Bonaccorso <carnil@debian.org>
To: Ricky WU <ricky_wu@realtek.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Paul Grandperrin <paul.grandperrin@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Wei_wang <wei_wang@realsil.com.cn>,
Roger Tseng <rogerable@realtek.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Regression since 6.1.46 (commit 8ee39ec): rtsx_pci from drivers/misc/cardreader breaks NVME power state, preventing system boot
Date: Tue, 26 Sep 2023 13:23:14 +0200 [thread overview]
Message-ID: <ZRK_Iqj1ZSjx1fZS@eldamar.lan> (raw)
In-Reply-To: <3ddcf5fae0164fbda79081650da79600@realtek.com>
Hi
[apologies if I missed some followup but was not able to find the
answer]
On Wed, Sep 20, 2023 at 08:32:17AM +0000, Ricky WU wrote:
> > On Wed, Sep 20, 2023 at 07:30:00AM +0000, Ricky WU wrote:
> > > Hi Greg k-h,
> > >
> > > This patch is our solution for this issue...
> > > And now how can I push this?
> >
> > Submit it properly like any other patch, what is preventing that from
> > happening?
> >
>
> (commit 8ee39ec) some reader no longer force #CLKREQ to low when system need to enter ASPM.
> But some platform maybe not implement complete ASPM? I don't know..... it causes problems...
>
> Like in the past Only the platform support L1ss we release the #CLKREQ.
> But new patch we move the judgment (L1ss) to probe, because we met some host will clean the config space from S3 or some power saving mode
> And also we think just to read config space one time when the driver start is enough
Is there a potential fix which is queued for this or would be the
safest option to unbreak the regression to revert the commit in the
stable trees temporarily?
I'm asking because in Debian we got the report at
https://bugs.debian.org/1052063
(and ideally to unbreak the situation for the user I would like to
include a fix in the next upload we do, but following what you as
upstream will do ideally).
Regards,
Salvatore
next prev parent reply other threads:[~2023-09-26 11:23 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 [this message]
2023-09-26 11:51 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-20 9:33 ` Paul Grandperrin
2023-09-13 3:10 ` Ricky WU
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=ZRK_Iqj1ZSjx1fZS@eldamar.lan \
--to=carnil@debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=paul.grandperrin@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=ricky_wu@realtek.com \
--cc=rogerable@realtek.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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