linux-kernel - 回复: [PATCH v13 0/21] Refactoring Microchip PCIe driver and add StarFive PCIe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <ZQ0PR01MB098128579D86207B4B9BA7D28266A@ZQ0PR01MB0981.CHNPR01.prod.partner.outlook.cn>
Date: Fri, 5 Jan 2024 02:35:10 +0000
From: Kevin Xie <kevin.xie@...rfivetech.com>
To: Kevin Hilman <khilman@...libre.com>, Minda Chen
	<minda.chen@...rfivetech.com>, Conor Dooley <conor@...nel.org>,
	Krzysztof Wilczy��ski <kw@...ux.com>, Rob Herring
	<robh+dt@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>, Lorenzo Pieralisi
	<lpieralisi@...nel.org>, Daire McNamara <daire.mcnamara@...rochip.com>, Emil
 Renner Berthing <emil.renner.berthing@...onical.com>, Krzysztof Kozlowski
	<krzysztof.kozlowski+dt@...aro.org>
CC: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, Paul Walmsley
	<paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>, Albert Ou
	<aou@...s.berkeley.edu>, Philipp Zabel <p.zabel@...gutronix.de>, Mason Huo
	<mason.huo@...rfivetech.com>, Leyfoon Tan <leyfoon.tan@...rfivetech.com>,
	Minda Chen <minda.chen@...rfivetech.com>
Subject:
 回复: [PATCH v13 0/21] Refactoring Microchip PCIe driver and add StarFive PCIe

> Minda Chen <minda.chen@...rfivetech.com> writes:
> 
> > This patchset final purpose is add PCIe driver for StarFive JH7110 SoC.
> > JH7110 using PLDA XpressRICH PCIe IP. Microchip PolarFire Using the
> > same IP and have commit their codes, which are mixed with PLDA
> > controller codes and Microchip platform codes.
> 
> Thank you for this series.
> 
> I tested this on a VisionFive v2 board, and it seems to probe and find my
> M.2 NVMe SSD, but then gets timeouts when trying to use the NVMe (e.g.
> 'blkid' command)
> 

Hi, Kevin:
Could you please provide the manufacturer and model of the M.2 NVMe SSD
you tested?

> Kernel logs below.
> 
> Kevin
> 
> [   15.131094] pcie-starfive 9c0000000.pcie: host bridge
> /soc/pcie@...000000 ranges:
> [   15.138637] pcie-starfive 9c0000000.pcie:      MEM
> 0x0038000000..0x003fffffff -> 0x0038000000
> [   15.147180] pcie-starfive 9c0000000.pcie:      MEM
> 0x0980000000..0x09bfffffff -> 0x0980000000
> [   15.368040] pcie-starfive 9c0000000.pcie: port link up
> [   15.374219] pcie-starfive 9c0000000.pcie: PCI host bridge to bus 0001:00
> [   15.380944] pci_bus 0001:00: root bus resource [bus 00-ff]
> [   15.386443] pci_bus 0001:00: root bus resource [mem
> 0x38000000-0x3fffffff]
> [   15.393330] pci_bus 0001:00: root bus resource [mem
> 0x980000000-0x9bfffffff pref]
> [   15.400882] pci 0001:00:00.0: [1556:1111] type 01 class 0x060400
> [   15.407165] pci 0001:00:00.0: supports D1 D2
> [   15.411447] pci 0001:00:00.0: PME# supported from D0 D1 D2 D3hot
> D3cold
> [   15.419964] pci 0001:00:00.0: bridge configuration invalid ([bus 00-00]),
> reconfiguring
> [   15.428245] pci 0001:01:00.0: [126f:2263] type 00 class 0x010802
> [   15.434331] pci 0001:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff
> 64bit]
> [   15.441578] pci 0001:01:00.0: 4.000 Gb/s available PCIe bandwidth,
> limited by 5.0 GT/s PCIe x1 link at 0001:00:00.0 (capable of 31.504 Gb/s with
> 8
> .0 GT/s PCIe x4 link)
> [   15.456910] pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
> [   15.463553] pci 0001:00:00.0: BAR 8: assigned [mem
> 0x38000000-0x380fffff]
> [   15.470352] pci 0001:01:00.0: BAR 0: assigned [mem
> 0x38000000-0x38003fff 64bit]
> [   15.477699] pci 0001:00:00.0: PCI bridge to [bus 01]
> [   15.482686] pci 0001:00:00.0:   bridge window [mem
> 0x38000000-0x380fffff]
> [   15.489632] pcieport 0001:00:00.0: enabling device (0000 -> 0002)
> [   15.496038] pcieport 0001:00:00.0: PME: Signaling with IRQ 56
> [   15.502472] usb 1-1: new high-speed USB device number 2 using xhci_hcd
> [   15.509755] usb usb2-port2: over-current condition
> [   15.515883] nvme nvme0: pci function 0001:01:00.0
> [   15.520615] nvme 0001:01:00.0: enabling device (0000 -> 0002)
> [   15.532685] nvme nvme0: allocated 64 MiB host memory buffer.
> [   15.550070] nvme nvme0: 4/0/0 default/read/poll queues
> [   15.562992] nvme nvme0: Ignoring bogus Namespace Identifiers
> [   15.663327] hub 1-1:1.0: USB hub found
> [   15.667320] hub 1-1:1.0: 4 ports detected
> 
> [   46.064052] nvme nvme0: I/O 424 QID 3 timeout, completion polled
> 
> [   76.784046] nvme nvme0: I/O 425 (I/O Cmd) QID 3 timeout, aborting
> [   76.790179] nvme nvme0: I/O 426 (I/O Cmd) QID 3 timeout, aborting
> [   76.796294] nvme nvme0: I/O 427 (I/O Cmd) QID 3 timeout, aborting
> [   76.802411] nvme nvme0: I/O 428 (I/O Cmd) QID 3 timeout, aborting
> [   76.808525] nvme nvme0: I/O 429 (I/O Cmd) QID 3 timeout, aborting