linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Wang <wangxiao@hotmail.it>
To: Josh Taylor <joshuataylorx@gmail.com>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>, "hch@lst.de" <hch@lst.de>,
	"highenthalpyh@gmail.com" <highenthalpyh@gmail.com>,
	"kbusch@kernel.org" <kbusch@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	"xuwd1@hotmail.com" <xuwd1@hotmail.com>
Subject: Re: [PATCH] nvme-pci: add NVME_QUIRK_DELAY_BEFORE_CHK_RDY for MAXIO MAP1602
Date: Sat, 22 Jul 2023 14:42:22 +0000	[thread overview]
Message-ID: <MEAP282MB039184E1E94BC16523846876B33CA@MEAP282MB0391.AUSP282.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20230722140752.616073-1-joshuataylorx@gmail.com>

Try latest Manjaro(install with ISO and update the system with around 2GB downloads). That worked for me to recognize my both MAP1602 SSDs: Aigo P7000z and Fanxiang S790.

Sent from my mobile device.

> 在 2023年7月22日，22:08，Josh Taylor <joshuataylorx@gmail.com> 写道：
> 
> This is my first response to a Kernel patch, so I apologise for any formatting weirdness.
> 
> I have a Lexar NM790 (4TB), which uses the MAP1602. It looks like this is going to be a fairly popular controller, as it seems a few are using it - as of July 2023 it looks like ~18 M.2 2280 are using it according to techpowerup (https://www.techpowerup.com/ssd-specs/?f&controllerMfgr=Maxiotech#MAP1602).
> 
> I however cannot get this patch to work for me on 6.5-rc2 on ArchLinux, nor with 6.4.4.
> 
> This is my dmesg when booting (Linux archiso 6.3.9-arch1-1):
> 
> 
>    [    6.634874] nvme nvme0: pci function 0000:01:00.0
>    [    6.640698] r8169 0000:27:00.0: enabling device (0000 -> 0003)
>    [    6.643601] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0
> 
> 
> When doing a suspend, then resuming, I can then re-initialise the device using the rescan steps in the previous email.
> 
> I then get this in my dmesg (Linux archiso 6.3.9-arch1-1):
> 
> 
>    [  130.948667] pci 0000:01:00.0: Removing from iommu group 14
>    [  131.983938] pci 0000:01:00.0: [1d97:1602] type 00 class 0x010802
>    [  131.983963] pci 0000:01:00.0: reg 0x10: [mem 0xfcf00000-0xfcf03fff 64bit]
>    [  131.984212] pci 0000:01:00.0: 31.504 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x4 link at 0000:00:01.1 (capable of 63.012 Gb/s with 16.0 GT/s PCIe x4 link)
>    [  131.984346] pci 0000:01:00.0: Adding to iommu group 14
>    [  132.031556] pci 0000:01:00.0: BAR 0: assigned [mem 0xfcf00000-0xfcf03fff 64bit]
>    [  132.031662] nvme nvme0: pci function 0000:01:00.0
>    [  132.044095] nvme nvme0: allocated 40 MiB host memory buffer.
>    [  132.088892] nvme nvme0: 16/0/0 default/read/poll queues
> 
> 
> The "allocated 40 MiB host memory buffer" part is interesting, none of my other drives have this, as this is a DRAM-less drive.
> 
> # nvme get-feature /dev/nvme0 -f 0x0c -H
> get-feature:0x0c (Autonomous Power State Transition), Current value:0x00000001
>    Autonomous Power State Transition Enable (APSTE): Enabled
>    Auto PST Entries    .................
>    Entry[ 0]
>    .................
>    Idle Time Prior to Transition (ITPT): 100 ms
>    Idle Transition Power State   (ITPS): 3
>    .................
>    Entry[ 1]
>    .................
>    Idle Time Prior to Transition (ITPT): 100 ms
>    Idle Transition Power State   (ITPS): 3
>    .................
>    Entry[ 2]
>    .................
>    Idle Time Prior to Transition (ITPT): 100 ms
>    Idle Transition Power State   (ITPS): 3
>    .................
>    Entry[ 3]
>    .................
>    Idle Time Prior to Transition (ITPT): 2000 ms
>    Idle Transition Power State   (ITPS): 4
>    .................
>    Entry[ 4]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[ 5]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[ 6]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[ 7]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[ 8]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[ 9]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[10]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[11]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[12]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[13]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[14]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[15]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[16]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[17]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[18]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[19]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[20]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[21]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[22]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[23]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[24]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[25]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[26]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[27]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[28]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[29]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[30]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................
>    Entry[31]
>    .................
>    Idle Time Prior to Transition (ITPT): 0 ms
>    Idle Transition Power State   (ITPS): 0
>    .................

  reply	other threads:[~2023-07-22 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18  2:10 [PATCH] nvme-pci: add NVME_QUIRK_DELAY_BEFORE_CHK_RDY for MAXIO MAP1602 Sean Wang
2023-07-22 14:07 ` Josh Taylor
2023-07-22 14:42   ` Sean Wang [this message]
     [not found] <MEAP282MB039120C4DEF97CED9B4CE841B33BA@MEAP282MB0391.AUSP282.PROD.OUTLOOK.COM>
2023-07-17  8:03 ` Keith Busch
  -- strict thread matches above, loose matches on Subject: below --
2023-07-14 13:13 Han Gao
2023-08-17  5:32 ` Felix Yan

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=MEAP282MB039184E1E94BC16523846876B33CA@MEAP282MB0391.AUSP282.PROD.OUTLOOK.COM \
    --to=wangxiao@hotmail.it \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=highenthalpyh@gmail.com \
    --cc=joshuataylorx@gmail.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=xuwd1@hotmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).