mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 13:43:55 -0400	[thread overview]
Message-ID: <144d4c08-2cd4-4d77-acb5-5c89d8dede46@sapience.com> (raw)
In-Reply-To: <ZN5YqPuT0+j8kP3l@kbusch-mbp.dhcp.thefacebook.com>

On 8/17/23 13:28, Keith Busch wrote:
...
>>>
>>> Bisect done - This is result:
> 
> Sounds like the driver's ASPM suspicion was justified, however the
> recommended work-around doesn't appear to apply to this hardware.
> Thanks for running the bisect!

Happy to help :)

gene


  reply	other threads:[~2023-08-17 17:44 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
2023-08-17 17:28       ` Keith Busch
2023-08-17 17:43         ` Genes Lists [this message]
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=144d4c08-2cd4-4d77-acb5-5c89d8dede46@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®