From: Genes Lists <lists@sapience.com>
To: Ricky WU <ricky_wu@realtek.com>, Keith Busch <kbusch@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"hch@lst.de" <hch@lst.de>, "arnd@arndb.de" <arnd@arndb.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: Possible nvme regression in 6.4.11
Date: Thu, 24 Aug 2023 06:22:19 -0400 [thread overview]
Message-ID: <97cee217-e438-4fff-836a-186f59d6d256@sapience.com> (raw)
In-Reply-To: <903830f8-9f9a-4071-9ced-761a55018c5a@sapience.com>
On 8/24/23 05:48, Genes Lists wrote:
> On 8/23/23 22:44, Ricky WU wrote:
>> Hi Gene,
>>
>> I can't reproduce this issue on my side...
>>
>> So if you only revert this patch
>> (69304c8d285b77c9a56d68f5ddb2558f27abf406) can work fine?
>> This patch only do is pull our clock request to HIGH if HOST need also
>> can pull to LOW, and this only do on our device
>> I don’t think this will affect other ports...
>>
>> BR,
>> Ricky
>
> Thanks Ricky - I will test revering just that commit and report back. I
> wont be able to get to it till later today (sometime after 2pm EDT) but
> I will do it today.
>
> FYI, i see one mpre report of someone experiencing same problem [1]
>
> gene
>
> [1] https://bugs.archlinux.org/task/79439
>
>
That commit was what was reverted in the last step of the git bisect -
and indeed reverting that commit makes the problem go away and machine
then boots fine.
thanks
gene
next prev parent reply other threads:[~2023-08-24 10:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 20:39 Possible nvme regression in 6.4.11 Genes Lists
2023-08-16 21:04 ` Keith Busch
2023-08-17 1:30 ` Genes Lists
2023-08-17 9:16 ` Genes Lists
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 [this message]
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=97cee217-e438-4fff-836a-186f59d6d256@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