[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <903830f8-9f9a-4071-9ced-761a55018c5a@sapience.com>
Date: Thu, 24 Aug 2023 05:48:20 -0400
From: Genes Lists <lists@...ience.com>
To: Ricky WU <ricky_wu@...ltek.com>, Keith Busch <kbusch@...nel.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"sagi@...mberg.me" <sagi@...mberg.me>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"hch@....de" <hch@....de>, "arnd@...db.de" <arnd@...db.de>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Subject: Re: Possible nvme regression in 6.4.11
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
Powered by blists - more mailing lists