All of lore.kernel.org
 help / color / mirror / Atom feed
* KXG60ZNV256G not recognized
@ 2019-02-13 10:07 Gerd Pokorra
  2019-02-13 10:27 ` Johannes Thumshirn
  0 siblings, 1 reply; 22+ messages in thread
From: Gerd Pokorra @ 2019-02-13 10:07 UTC (permalink / raw)


Dear Sir or Madam,

in a Laptop is a NVMe SSD from Toshiba with the type name KXG60ZNV256G 
that will not be recognized from Linux. I can load the module nvme but 
there is no /dev/nvme*. I tried it with the kernel version 4.18.16-300. 
The command 'nvme list' show no device.

Could you help or have an idea how to access the device?

-- Gerd

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 10:07 KXG60ZNV256G not recognized Gerd Pokorra
@ 2019-02-13 10:27 ` Johannes Thumshirn
  2019-02-13 10:45   ` Gerd Pokorra
  0 siblings, 1 reply; 22+ messages in thread
From: Johannes Thumshirn @ 2019-02-13 10:27 UTC (permalink / raw)


On 13/02/2019 11:07, Gerd Pokorra wrote:
> Dear Sir or Madam,
> 
> in a Laptop is a NVMe SSD from Toshiba with the type name KXG60ZNV256G
> that will not be recognized from Linux. I can load the module nvme but
> there is no /dev/nvme*. I tried it with the kernel version 4.18.16-300.
> The command 'nvme list' show no device.
> 
> Could you help or have an idea how to access the device?

Hi Gerd,

Can you please send the output of 'lspci -vvv' for the device in question?

Thanks a lot,
	Johannes

-- 
Johannes Thumshirn                            SUSE Labs Filesystems
jthumshirn at suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 10:27 ` Johannes Thumshirn
@ 2019-02-13 10:45   ` Gerd Pokorra
  2019-02-13 10:51     ` Johannes Thumshirn
  0 siblings, 1 reply; 22+ messages in thread
From: Gerd Pokorra @ 2019-02-13 10:45 UTC (permalink / raw)


Hello Johannes,

I attached the whole output of 'lspci -vvv' as file lspci.out.

-- Gerd


Am 13.02.2019 um 11:27 schrieb Johannes Thumshirn:
> On 13/02/2019 11:07, Gerd Pokorra wrote:
>> Dear Sir or Madam,
>>
>> in a Laptop is a NVMe SSD from Toshiba with the type name KXG60ZNV256G
>> that will not be recognized from Linux. I can load the module nvme but
>> there is no /dev/nvme*. I tried it with the kernel version 4.18.16-300.
>> The command 'nvme list' show no device.
>>
>> Could you help or have an idea how to access the device?
> Hi Gerd,
>
> Can you please send the output of 'lspci -vvv' for the device in question?
>
> Thanks a lot,
> 	Johannes
>

-------------- next part --------------
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information: Len=10 <?>

00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 122
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 00003000-00003fff [size=4K]
	Memory behind bridge: b4200000-b42fffff [size=1M]
	Prefetchable memory behind bridge: 0000004100000000-00000043ffffffff [size=12G]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [88] Subsystem: Dell Device 0832
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee00258  Data: 0000
	Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us
			ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (downgraded), Width x16 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt+
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet+ LinkState-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd-
			 AtomicOpsCap: Routing- 32bit+ 64bit+ 128bitCAS+
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+
			 EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [140 v1] Root Complex Link
		Desc:	PortNumber=02 ComponentID=01 EltType=Config
		Link0:	Desc:	TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+
			Addr:	00000000fed19000
	Capabilities: [d94 v1] Secondary PCI Express <?>
	Kernel driver in use: pcieport

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile) (prog-if 00 [VGA controller])
	DeviceName: Onboard - Video
	Subsystem: Dell Device 0832
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 130
	Region 0: Memory at b3000000 (64-bit, non-prefetchable) [size=16M]
	Region 2: Memory at 60000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 4000 [size=64]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [40] Vendor Specific Information: Len=0c <?>
	Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
			 AtomicOpsCtl: ReqEn-
	Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee00018  Data: 0000
	Capabilities: [d0] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Process Address Space ID (PASID)
		PASIDCap: Exec- Priv-, Max PASID Width: 14
		PASIDCtl: Enable- Exec- Priv-
	Capabilities: [200 v1] Address Translation Service (ATS)
		ATSCap:	Invalidate Queue Depth: 00
		ATSCtl:	Enable-, Smallest Translation Unit: 00
	Capabilities: [300 v1] Page Request Interface (PRI)
		PRICtl: Enable- Reset-
		PRISta: RF- UPRGI- Stopped+
		Page Request Capacity: 00008000, Page Request Allocation: 00000000
	Kernel driver in use: i915
	Kernel modules: i915

00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 404a100000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [d0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	Kernel driver in use: proc_thermal
	Kernel modules: processor_thermal_device

00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 255
	Region 0: Memory at 404a10f000 (64-bit, non-prefetchable) [disabled] [size=4K]
	Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [f0] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-

00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at b43bd000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Kernel driver in use: intel_pch_thermal
	Kernel modules: intel_pch_thermal

00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) (prog-if 30 [XHCI])
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 126
	Region 0: Memory at b43a0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
		Address: 00000000fee00318  Data: 0000
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: xhci_hcd

00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at 404a108000 (64-bit, non-prefetchable) [disabled] [size=8K]
	Region 2: Memory at 404a10e000 (64-bit, non-prefetchable) [disabled] [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-

00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: [virtual] Memory at 404a10c000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 17
	Region 0: [virtual] Memory at 404a10d000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 129
	Region 0: Memory at 404a10b000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee00378  Data: 0000
	Capabilities: [a4] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 10)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at b43b0000 (32-bit, non-prefetchable) [size=32K]
	Region 1: Memory at b43bc000 (32-bit, non-prefetchable) [size=256]
	Region 2: I/O ports at 4090 [size=8]
	Region 3: I/O ports at 4080 [size=4]
	Region 4: I/O ports at 4060 [size=32]
	Region 5: Memory at b4300000 (32-bit, non-prefetchable) [size=512K]
	Capabilities: [d0] MSI-X: Enable- Count=34 Masked-
		Vector table: BAR=0 offset=00000000
		PBA: BAR=1 offset=00000000
	Capabilities: [70] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
	Kernel driver in use: ahci

00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 123
	Bus: primary=00, secondary=02, subordinate=6c, sec-latency=0
	I/O behind bridge: 00005000-00005fff [size=4K]
	Memory behind bridge: 84000000-b20fffff [size=737M]
	Prefetchable memory behind bridge: 0000004000000000-0000004049ffffff [size=1184M]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #1, Speed 8GT/s, Width x4, ASPM not supported
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (downgraded), Width x0 (downgraded)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
			Slot #4, PowerLimit 25.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq+ LinkChg+
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd+
			 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee00278  Data: 0000
	Capabilities: [90] Subsystem: Dell Device 0832
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO+ CmpltAbrt- UnxCmplt+ RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
		RootCmd: CERptEn- NFERptEn- FERptEn-
		RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
			 FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
		ErrorSrc: ERR_COR: 0000 ERR_FATAL/NONFATAL: 0000
	Capabilities: [140 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd- EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [150 v1] Precision Time Measurement
		PTMCap: Requester:- Responder:+ Root:+
		PTMClockGranularity: 4ns
		PTMControl: Enabled:+ RootSelected:+
		PTMEffectiveGranularity: Unknown
	Capabilities: [220 v1] Secondary PCI Express <?>
	Capabilities: [250 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:1c.5 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #6 (rev f0) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 124
	Bus: primary=00, secondary=6d, subordinate=6d, sec-latency=0
	I/O behind bridge: 0000f000-00000fff [empty]
	Memory behind bridge: b4100000-b41fffff [size=1M]
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff [empty]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #6, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #9, PowerLimit 10.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState+
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd+
			 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+
			 EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee002b8  Data: 0000
	Capabilities: [90] Subsystem: Dell Device 0832
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
		RootCmd: CERptEn- NFERptEn- FERptEn-
		RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
			 FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
		ErrorSrc: ERR_COR: 0000 ERR_FATAL/NONFATAL: 0000
	Capabilities: [140 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd- EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [150 v1] Precision Time Measurement
		PTMCap: Requester:- Responder:+ Root:+
		PTMClockGranularity: 4ns
		PTMControl: Enabled:+ RootSelected:+
		PTMEffectiveGranularity: Unknown
	Capabilities: [200 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=40us PortTPowerOnTime=44us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=60us LTR1.2_Threshold=81920ns
		L1SubCtl2: T_PwrOn=60us
	Capabilities: [220 v1] Secondary PCI Express <?>
	Capabilities: [250 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:1c.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #7 (rev f0) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin C routed to IRQ 125
	Bus: primary=00, secondary=6e, subordinate=6e, sec-latency=0
	I/O behind bridge: 0000f000-00000fff [empty]
	Memory behind bridge: b4000000-b40fffff [size=1M]
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff [empty]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #7, Speed 8GT/s, Width x1, ASPM L1, Exit Latency L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s (downgraded), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #10, PowerLimit 10.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState+
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd+
			 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee002f8  Data: 0000
	Capabilities: [90] Subsystem: Dell Device 0832
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
		RootCmd: CERptEn- NFERptEn- FERptEn-
		RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
			 FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
		ErrorSrc: ERR_COR: 0000 ERR_FATAL/NONFATAL: 0000
	Capabilities: [140 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd- EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [150 v1] Precision Time Measurement
		PTMCap: Requester:- Responder:+ Root:+
		PTMClockGranularity: 4ns
		PTMControl: Enabled:+ RootSelected:+
		PTMEffectiveGranularity: Unknown
	Capabilities: [200 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=40us PortTPowerOnTime=44us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=40us LTR1.2_Threshold=81920ns
		L1SubCtl2: T_PwrOn=60us
	Capabilities: [220 v1] Secondary PCI Express <?>
	Capabilities: [250 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
	DeviceName: Onboard - Sound
	Subsystem: Dell Device 0832
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 146
	Region 0: Memory at b43b8000 (64-bit, non-prefetchable) [size=16K]
	Region 4: Memory at 404a000000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] Vendor Specific Information: Len=14 <?>
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee00578  Data: 0000
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 404a10a000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at efa0 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at fe010000 (32-bit, non-prefetchable) [size=4K]

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10)
	DeviceName: Onboard - Ethernet
	Subsystem: Dell Device 0832
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 128
	Region 0: Memory at b4380000 (32-bit, non-prefetchable) [size=128K]
	Capabilities: [c8] Power Management version 3
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee00358  Data: 0000
	Kernel driver in use: e1000e
	Kernel modules: e1000e

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100 Mobile] (prog-if 00 [VGA controller])
	Subsystem: Dell Device 0832
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 147
	Region 0: [virtual] Memory at 4200000000 (64-bit, prefetchable) [size=8G]
	Region 2: [virtual] Memory at 4100000000 (64-bit, prefetchable) [size=2M]
	Region 4: I/O ports at 3000 [size=256]
	Region 5: Memory at b4200000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at b4240000 [disabled] [size=128K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x16, ASPM L1, Exit Latency L1 <1us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (downgraded), Width x16 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported
			 AtomicOpsCap: 32bit+ 64bit+ 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
			 AtomicOpsCtl: ReqEn+
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+
			 EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee00598  Data: 0000
	Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [150 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [200 v1] Resizable BAR <?>
	Capabilities: [270 v1] Secondary PCI Express <?>
	Capabilities: [2b0 v1] Address Translation Service (ATS)
		ATSCap:	Invalidate Queue Depth: 00
		ATSCtl:	Enable-, Smallest Translation Unit: 00
	Capabilities: [2c0 v1] Page Request Interface (PRI)
		PRICtl: Enable- Reset-
		PRISta: RF- UPRGI- Stopped+
		Page Request Capacity: 00000020, Page Request Allocation: 00000000
	Capabilities: [2d0 v1] Process Address Space ID (PASID)
		PASIDCap: Exec+ Priv+, Max PASID Width: 10
		PASIDCtl: Enable- Exec- Priv-
	Capabilities: [320 v1] Latency Tolerance Reporting
		Max snoop latency: 0ns
		Max no snoop latency: 0ns
	Capabilities: [328 v1] Alternative Routing-ID Interpretation (ARI)
		ARICap:	MFVC- ACS-, Next Function: 1
		ARICtl:	MFVC- ACS-, Function Group: 0
	Capabilities: [370 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=0us PortTPowerOnTime=170us
		L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
			   T_CommonMode=0us LTR1.2_Threshold=0ns
		L1SubCtl2: T_PwrOn=10us
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 580]
	Subsystem: Dell Device aaf0
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 145
	Region 0: Memory at b4260000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x16, ASPM L1, Exit Latency L1 <1us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (downgraded), Width x16 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported
			 AtomicOpsCap: 32bit+ 64bit+ 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
			 AtomicOpsCtl: ReqEn-
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee00558  Data: 0000
	Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [150 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [328 v1] Alternative Routing-ID Interpretation (ARI)
		ARICap:	MFVC- ACS-, Next Function: 0
		ARICtl:	MFVC- ACS-, Function Group: 0
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

6d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5260 (rev 01)
	Subsystem: Dell Device 0832
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 127
	Region 0: Memory at b4100000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee00338  Data: 0000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 512 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 unlimited
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, OBFF Via message/WAKE#
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
			 AtomicOpsCtl: ReqEn-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+
			 EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [148 v1] Device Serial Number 00-00-00-01-00-4c-e0-00
	Capabilities: [158 v1] Secondary PCI Express <?>
	Capabilities: [168 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [170 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=60us PortTPowerOnTime=60us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=0us LTR1.2_Threshold=81920ns
		L1SubCtl2: T_PwrOn=60us
	Kernel driver in use: rtsx_pci
	Kernel modules: rtsx_pci

6e:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
	Subsystem: Intel Corporation Device 4010
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 18
	Region 0: Memory at b4000000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [c8] Power Management version 3
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [40] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 5GT/s, Width x1, ASPM L1, Exit Latency L1 <8us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR+, OBFF Via WAKE#
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis-, LTR+, OBFF Disabled
			 AtomicOpsCtl: ReqEn-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
		Vector table: BAR=0 offset=00002000
		PBA: BAR=0 offset=00003000
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [14c v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [154 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=30us PortTPowerOnTime=18us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=0us LTR1.2_Threshold=81920ns
		L1SubCtl2: T_PwrOn=60us
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 10:45   ` Gerd Pokorra
@ 2019-02-13 10:51     ` Johannes Thumshirn
  2019-02-13 11:06       ` Gerd Pokorra
  0 siblings, 1 reply; 22+ messages in thread
From: Johannes Thumshirn @ 2019-02-13 10:51 UTC (permalink / raw)


On 13/02/2019 11:45, Gerd Pokorra wrote:
> Hello Johannes,
> 
> I attached the whole output of 'lspci -vvv' as file lspci.out.

OK, I can't find an NVMe device in there but this one raises concerns:

00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA
Controller [RAID mode] (rev 10)
	DeviceName: Onboard - Other
	Subsystem: Dell Device 0832
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at b43b0000 (32-bit, non-prefetchable) [size=32K]
	Region 1: Memory at b43bc000 (32-bit, non-prefetchable) [size=256]
	Region 2: I/O ports at 4090 [size=8]
	Region 3: I/O ports at 4080 [size=4]
	Region 4: I/O ports at 4060 [size=32]
	Region 5: Memory at b4300000 (32-bit, non-prefetchable) [size=512K]
	Capabilities: [d0] MSI-X: Enable- Count=34 Masked-
		Vector table: BAR=0 offset=00000000
		PBA: BAR=1 offset=00000000
	Capabilities: [70] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
	Kernel driver in use: ahci

Please check your BIOS if the NVMe is in the AHCI remapped NVMe device mode?

Your dmesg should contain an entry like:
Found %d remapped NVMe devices.

Byte,
	Johannes
-- 
Johannes Thumshirn                            SUSE Labs Filesystems
jthumshirn at suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 10:51     ` Johannes Thumshirn
@ 2019-02-13 11:06       ` Gerd Pokorra
  2019-02-13 11:28         ` Gerd Pokorra
  0 siblings, 1 reply; 22+ messages in thread
From: Gerd Pokorra @ 2019-02-13 11:06 UTC (permalink / raw)


Hello Johannes,

the output of 'dmeg | grep -i nvm' shows that is remapped:

[??? 4.403742] ahci 0000:00:17.0: Found 1 remapped NVMe devices.

-- Gerd

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 11:06       ` Gerd Pokorra
@ 2019-02-13 11:28         ` Gerd Pokorra
  2019-02-13 11:50           ` Johannes Thumshirn
  0 siblings, 1 reply; 22+ messages in thread
From: Gerd Pokorra @ 2019-02-13 11:28 UTC (permalink / raw)


Hello Johannes,

in the BIOS I see 'System Configuration' -> 'SATA Operation'

- Disabled

- AHCI

- RAID On


Currently it is set to 'RAID On'.

-- Gerd


Am 13.02.2019 um 12:06 schrieb Gerd Pokorra:
> Hello Johannes,
>
> the output of 'dmeg | grep -i nvm' shows that is remapped:
>
> [??? 4.403742] ahci 0000:00:17.0: Found 1 remapped NVMe devices.
>
> -- Gerd
>
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 11:28         ` Gerd Pokorra
@ 2019-02-13 11:50           ` Johannes Thumshirn
  2019-02-13 13:58             ` Gerd Pokorra
  0 siblings, 1 reply; 22+ messages in thread
From: Johannes Thumshirn @ 2019-02-13 11:50 UTC (permalink / raw)


On 13/02/2019 12:28, Gerd Pokorra wrote:
> Hello Johannes,
> 
> in the BIOS I see 'System Configuration' -> 'SATA Operation'
> 
> - Disabled
> 
> - AHCI
> 
> - RAID On
> 
> 
> Currently it is set to 'RAID On'.

Yes the 'RAID On' would be the setting in question, but I have no idea
what consequences turning it off will have. E.g. wrecking an existing
Windows installation and so on.

Byte,
	Johannes
-- 
Johannes Thumshirn                            SUSE Labs Filesystems
jthumshirn at suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 11:50           ` Johannes Thumshirn
@ 2019-02-13 13:58             ` Gerd Pokorra
  2019-02-13 14:04               ` Johannes Thumshirn
  0 siblings, 1 reply; 22+ messages in thread
From: Gerd Pokorra @ 2019-02-13 13:58 UTC (permalink / raw)


Hello Johannes,

after setting it to 'Disabled' I see no hard disks of the laptop any 
more with linux and an existing Windows installation is wrecked.

Setting the BIOS to the 'Factory Defaults' bring the Windows 
Installation back. It will be hard to install an Linux on this Laptop.

-- Gerd

Am 13.02.2019 um 12:50 schrieb Johannes Thumshirn:
> On 13/02/2019 12:28, Gerd Pokorra wrote:
>> Hello Johannes,
>>
>> in the BIOS I see 'System Configuration' -> 'SATA Operation'
>>
>> - Disabled
>>
>> - AHCI
>>
>> - RAID On
>>
>>
>> Currently it is set to 'RAID On'.
> Yes the 'RAID On' would be the setting in question, but I have no idea
> what consequences turning it off will have. E.g. wrecking an existing
> Windows installation and so on.
>
> Byte,
> 	Johannes

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 13:58             ` Gerd Pokorra
@ 2019-02-13 14:04               ` Johannes Thumshirn
  2019-02-13 14:29                 ` Gerd Pokorra
  0 siblings, 1 reply; 22+ messages in thread
From: Johannes Thumshirn @ 2019-02-13 14:04 UTC (permalink / raw)


On 13/02/2019 14:58, Gerd Pokorra wrote:
> Hello Johannes,
> 
> after setting it to 'Disabled' I see no hard disks of the laptop any
> more with linux and an existing Windows installation is wrecked.
> 
> Setting the BIOS to the 'Factory Defaults' bring the Windows
> Installation back. It will be hard to install an Linux on this Laptop.

Yes this is exactly what I expected TBH.

There's not really a lot we can do about without any specs for the AHCI
remapped NVMe thingy.

Lenovo used to have an different BIOS built for Linux on the Yoga series
some years ago if I remember correctly.

Byte,
	Johannes
-- 
Johannes Thumshirn                            SUSE Labs Filesystems
jthumshirn at suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 14:04               ` Johannes Thumshirn
@ 2019-02-13 14:29                 ` Gerd Pokorra
  2019-02-13 15:25                   ` Keith Busch
  2019-02-13 18:00                   ` Christoph Hellwig
  0 siblings, 2 replies; 22+ messages in thread
From: Gerd Pokorra @ 2019-02-13 14:29 UTC (permalink / raw)


Hello Johannes,

it is a Dell Presision 7730.

-- Gerd


Am 13.02.2019 um 15:04 schrieb Johannes Thumshirn:
> On 13/02/2019 14:58, Gerd Pokorra wrote:
>> Hello Johannes,
>>
>> after setting it to 'Disabled' I see no hard disks of the laptop any
>> more with linux and an existing Windows installation is wrecked.
>>
>> Setting the BIOS to the 'Factory Defaults' bring the Windows
>> Installation back. It will be hard to install an Linux on this Laptop.
> Yes this is exactly what I expected TBH.
>
> There's not really a lot we can do about without any specs for the AHCI
> remapped NVMe thingy.
>
> Lenovo used to have an different BIOS built for Linux on the Yoga series
> some years ago if I remember correctly.
>
> Byte,
> 	Johannes

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 14:29                 ` Gerd Pokorra
@ 2019-02-13 15:25                   ` Keith Busch
  2019-02-13 18:00                   ` Christoph Hellwig
  1 sibling, 0 replies; 22+ messages in thread
From: Keith Busch @ 2019-02-13 15:25 UTC (permalink / raw)


On Wed, Feb 13, 2019@03:29:53PM +0100, Gerd Pokorra wrote:
> Hello Johannes,
> 
> it is a Dell Presision 7730.


I'm not familiar with this product, but if it's like others, the 'AHCI'
'SATA Operation' mode is the one you'd want to select, not 'Disabled'.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 14:29                 ` Gerd Pokorra
  2019-02-13 15:25                   ` Keith Busch
@ 2019-02-13 18:00                   ` Christoph Hellwig
  2019-02-13 18:04                     ` Mario.Limonciello
  1 sibling, 1 reply; 22+ messages in thread
From: Christoph Hellwig @ 2019-02-13 18:00 UTC (permalink / raw)


Mario,

any idea how to turn off the Intel anti-competitive fake RAID mode
for NVMe for the Dell Presision 7730?

On Wed, Feb 13, 2019@03:29:53PM +0100, Gerd Pokorra wrote:
> Hello Johannes,
> 
> it is a Dell Presision 7730.
> 
> -- Gerd
> 
> 
> Am 13.02.2019 um 15:04 schrieb Johannes Thumshirn:
> > On 13/02/2019 14:58, Gerd Pokorra wrote:
> > > Hello Johannes,
> > > 
> > > after setting it to 'Disabled' I see no hard disks of the laptop any
> > > more with linux and an existing Windows installation is wrecked.
> > > 
> > > Setting the BIOS to the 'Factory Defaults' bring the Windows
> > > Installation back. It will be hard to install an Linux on this Laptop.
> > Yes this is exactly what I expected TBH.
> > 
> > There's not really a lot we can do about without any specs for the AHCI
> > remapped NVMe thingy.
> > 
> > Lenovo used to have an different BIOS built for Linux on the Yoga series
> > some years ago if I remember correctly.
> > 
> > Byte,
> > 	Johannes
> 
> 
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
---end quoted text---

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 18:00                   ` Christoph Hellwig
@ 2019-02-13 18:04                     ` Mario.Limonciello
  2019-02-13 18:18                       ` Keith Busch
  0 siblings, 1 reply; 22+ messages in thread
From: Mario.Limonciello @ 2019-02-13 18:04 UTC (permalink / raw)


> -----Original Message-----
> From: Christoph Hellwig <hch at infradead.org>
> Sent: Wednesday, February 13, 2019 12:01 PM
> To: Limonciello, Mario; Gerd Pokorra
> Cc: Johannes Thumshirn; linux-nvme at lists.infradead.org
> Subject: Re: KXG60ZNV256G not recognized
> 
> 
> [EXTERNAL EMAIL]
> 
> Mario,
> 
> any idea how to turn off the Intel anti-competitive fake RAID mode
> for NVMe for the Dell Presision 7730?

If you go into BIOS setup and choose SATA mode change from 
"RAID ON" to "AHCI".

I know it's an NVME disk, and you're changing SATA mode, but it adjusts
relevant settings on the PCH whether you were using a SATA disk or NVME.

Systems shipped with Linux have it set properly and it should persist
even when BIOS is reset to factory defaults.

> 
> On Wed, Feb 13, 2019@03:29:53PM +0100, Gerd Pokorra wrote:
> > Hello Johannes,
> >
> > it is a Dell Presision 7730.
> >
> > -- Gerd
> >
> >
> > Am 13.02.2019 um 15:04 schrieb Johannes Thumshirn:
> > > On 13/02/2019 14:58, Gerd Pokorra wrote:
> > > > Hello Johannes,
> > > >
> > > > after setting it to 'Disabled' I see no hard disks of the laptop any
> > > > more with linux and an existing Windows installation is wrecked.
> > > >
> > > > Setting the BIOS to the 'Factory Defaults' bring the Windows
> > > > Installation back. It will be hard to install an Linux on this Laptop.
> > > Yes this is exactly what I expected TBH.
> > >
> > > There's not really a lot we can do about without any specs for the AHCI
> > > remapped NVMe thingy.
> > >
> > > Lenovo used to have an different BIOS built for Linux on the Yoga series
> > > some years ago if I remember correctly.
> > >
> > > Byte,
> > > 	Johannes
> >
> >
> > _______________________________________________
> > Linux-nvme mailing list
> > Linux-nvme at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-nvme
> ---end quoted text---

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 18:04                     ` Mario.Limonciello
@ 2019-02-13 18:18                       ` Keith Busch
  2019-02-13 18:51                         ` Mario.Limonciello
  0 siblings, 1 reply; 22+ messages in thread
From: Keith Busch @ 2019-02-13 18:18 UTC (permalink / raw)


On Wed, Feb 13, 2019@06:04:39PM +0000, Mario.Limonciello@dell.com wrote:
> 
> If you go into BIOS setup and choose SATA mode change from 
> "RAID ON" to "AHCI".
> 
> I know it's an NVME disk, and you're changing SATA mode, but it adjusts
> relevant settings on the PCH whether you were using a SATA disk or NVME.

Right, "RAID" mode has the PCH compbine multiple devices into one. AHCI
mode doesn't capture other devices behind the SATA controller, so the
NVMe device is visible.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 18:18                       ` Keith Busch
@ 2019-02-13 18:51                         ` Mario.Limonciello
  2019-02-13 19:00                           ` Christoph Hellwig
  0 siblings, 1 reply; 22+ messages in thread
From: Mario.Limonciello @ 2019-02-13 18:51 UTC (permalink / raw)


> -----Original Message-----
> From: Keith Busch <keith.busch at intel.com>
> Sent: Wednesday, February 13, 2019 12:19 PM
> To: Limonciello, Mario
> Cc: hch at infradead.org; pokorra at uni-siegen.de; linux-nvme at lists.infradead.org;
> jthumshirn at suse.de
> Subject: Re: KXG60ZNV256G not recognized
> 
> 
> [EXTERNAL EMAIL]
> 
> On Wed, Feb 13, 2019@06:04:39PM +0000, Mario.Limonciello@dell.com wrote:
> >
> > If you go into BIOS setup and choose SATA mode change from
> > "RAID ON" to "AHCI".
> >
> > I know it's an NVME disk, and you're changing SATA mode, but it adjusts
> > relevant settings on the PCH whether you were using a SATA disk or NVME.
> 
> Right, "RAID" mode has the PCH compbine multiple devices into one. AHCI
> mode doesn't capture other devices behind the SATA controller, so the
> NVMe device is visible.

> the Intel anti-competitive fake RAID mode

Chris Hellwig,

I am aware there was a patch series submitted at one point for this
technology that was rejected. From your perspective is there (realistically) anything
that Intel can do here for the kernel?  The particular PCH functionality referred above
has been in the industry from Intel silicon for a while now, and is going to continue to
be a barrier to entry for anyone who purchases a machine "with Windows" and tries to
load Linux.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 18:51                         ` Mario.Limonciello
@ 2019-02-13 19:00                           ` Christoph Hellwig
  2019-02-13 20:37                             ` Mario.Limonciello
  0 siblings, 1 reply; 22+ messages in thread
From: Christoph Hellwig @ 2019-02-13 19:00 UTC (permalink / raw)


What we really need is Intel stopping to do amazingly stupid things like
this.  Hiding PCIe devices from their drivers is anti-competitive
behavior from a company controlling much of the PC market.

And at the very least we need a way to disable this behavior from the
OS.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 19:00                           ` Christoph Hellwig
@ 2019-02-13 20:37                             ` Mario.Limonciello
  2019-02-13 21:22                               ` Keith Busch
  0 siblings, 1 reply; 22+ messages in thread
From: Mario.Limonciello @ 2019-02-13 20:37 UTC (permalink / raw)


> What we really need is Intel stopping to do amazingly stupid things like
> this.  Hiding PCIe devices from their drivers is anti-competitive
> behavior from a company controlling much of the PC market.
> 

My take on this is that the way this thing works and the things it does makes a lot more
sense in the Windows kernel driver model than it does for Linux.  I've heard there are
quantifiable tangible benefits to using this technology on Windows.

Given its been around now for at least 4 generations of Intel silicon (maybe more if
I'm miscounting), I really don't think its going to away from the PC market any time soon.

As such, I don't think that disdaining the technology will get Intel to change it.
So I'm hoping we can constructively come up with something that works in the confines
of its existence to make it a better experience at least.

> And at the very least we need a way to disable this behavior from the
> OS.

At least on Dell I could offer a way to accomplish this with SMM today with a small kernel
patch, but it will require a reboot to be effective.

An idea of how it could look:
# cat /sys/platform/devices/dell-laptop/current-sata-mode
ahci [raid] needs-reboot
# echo ahci > /sys/platform/devices/dell-laptop/current-sata-mode
# cat /sys/platform/devices/dell-laptop/current-sata-mode
ahci raid [needs-reboot]
(reboot)
# cat /sys/platform/devices/dell-laptop/current-sata-mode
[ahci] raid needs-reboot

It's not pretty, but maybe it's an improvement?  At least on Dell systems the
distro installers could probe that sysfs node and warn people/fix it across a reboot cycle.

If the relevant Intel PCH registers that are affected were documented, I would think something
similar could be done by kernel PCH initialization code,  but the PCH might need to be reset after
writing them.  That could make the BIOS setting effectively ignored on Linux.
Keith, what do you think on this?

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 20:37                             ` Mario.Limonciello
@ 2019-02-13 21:22                               ` Keith Busch
  2019-02-13 21:56                                 ` Mario.Limonciello
  2019-02-14  8:30                                 ` Christoph Hellwig
  0 siblings, 2 replies; 22+ messages in thread
From: Keith Busch @ 2019-02-13 21:22 UTC (permalink / raw)


On Wed, Feb 13, 2019@08:37:37PM +0000, Mario.Limonciello@dell.com wrote:
> > What we really need is Intel stopping to do amazingly stupid things like
> > this.  Hiding PCIe devices from their drivers is anti-competitive
> > behavior from a company controlling much of the PC market.
> 
> My take on this is that the way this thing works and the things it does makes a lot more
> sense in the Windows kernel driver model than it does for Linux.  I've heard there are
> quantifiable tangible benefits to using this technology on Windows.

To the best of my knowledge, the hardware mode is working around a
software limitation that doesn't apply to Linux.
 
> Given its been around now for at least 4 generations of Intel silicon (maybe more if
> I'm miscounting), I really don't think its going to away from the PC market any time soon.

That might depend on if said software overcomes those limitations, but I'm
out of the loop to know if that's going to change any time soon, if ever.

> As such, I don't think that disdaining the technology will get Intel to change it.
> So I'm hoping we can constructively come up with something that works in the confines
> of its existence to make it a better experience at least.

I assumed Chritoph's comment was directed toward said software that runs
on the majority of the client PC market, leaving hardware vendors to
think up "creative" work-arounds to its quirks to the detriment of other
software environments. :(

> At least on Dell I could offer a way to accomplish this with SMM today with a small kernel
> patch, but it will require a reboot to be effective.

Pre-boot settings like you already have are preferable, right? Otherwise
it's a little more difficult to use the NVMe as your boot drive.

> It's not pretty, but maybe it's an improvement?  At least on Dell systems the
> distro installers could probe that sysfs node and warn people/fix it across a reboot cycle.
> 
> If the relevant Intel PCH registers that are affected were documented, I would think something
> similar could be done by kernel PCH initialization code,  but the PCH might need to be reset after
> writing them.  That could make the BIOS setting effectively ignored on Linux.
> Keith, what do you think on this?

I think the recommended Linux implementation would treat this like a host
bridge and expose the PCI device to the OS without changing any hardware
settings.

But as far as I know, the Intel group that owns this mode has not reached
out to the Linux enabling with hardware specs that we can make public.
The OEMS are probably in a better position to compel this to change than
I am.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 21:22                               ` Keith Busch
@ 2019-02-13 21:56                                 ` Mario.Limonciello
  2019-02-14  8:33                                   ` Christoph Hellwig
  2019-02-14  8:30                                 ` Christoph Hellwig
  1 sibling, 1 reply; 22+ messages in thread
From: Mario.Limonciello @ 2019-02-13 21:56 UTC (permalink / raw)


> On Wed, Feb 13, 2019@08:37:37PM +0000, Mario.Limonciello@dell.com wrote:
> > > What we really need is Intel stopping to do amazingly stupid things like
> > > this.  Hiding PCIe devices from their drivers is anti-competitive
> > > behavior from a company controlling much of the PC market.
> >
> > My take on this is that the way this thing works and the things it does makes a lot
> more
> > sense in the Windows kernel driver model than it does for Linux.  I've heard there
> are
> > quantifiable tangible benefits to using this technology on Windows.
> 
> To the best of my knowledge, the hardware mode is working around a
> software limitation that doesn't apply to Linux.
> 
> > Given its been around now for at least 4 generations of Intel silicon (maybe more
> if
> > I'm miscounting), I really don't think its going to away from the PC market any
> time soon.
> 
> That might depend on if said software overcomes those limitations, but I'm
> out of the loop to know if that's going to change any time soon, if ever.
> 
> > As such, I don't think that disdaining the technology will get Intel to change it.
> > So I'm hoping we can constructively come up with something that works in the
> confines
> > of its existence to make it a better experience at least.
> 
> I assumed Chritoph's comment was directed toward said software that runs
> on the majority of the client PC market, leaving hardware vendors to
> think up "creative" work-arounds to its quirks to the detriment of other
> software environments. :(
> 
> > At least on Dell I could offer a way to accomplish this with SMM today with a
> small kernel
> > patch, but it will require a reboot to be effective.
> 
> Pre-boot settings like you already have are preferable, right? Otherwise
> it's a little more difficult to use the NVMe as your boot drive.

The SMM thing I mentioned would basically just be modifying those pre-boot settings
so the next boot it could DTRT for Linux.

It's definitely just a band-aid to the problem.

> 
> > It's not pretty, but maybe it's an improvement?  At least on Dell systems the
> > distro installers could probe that sysfs node and warn people/fix it across a
> reboot cycle.
> >
> > If the relevant Intel PCH registers that are affected were documented, I would
> think something
> > similar could be done by kernel PCH initialization code,  but the PCH might need
> to be reset after
> > writing them.  That could make the BIOS setting effectively ignored on Linux.
> > Keith, what do you think on this?
> 
> I think the recommended Linux implementation would treat this like a host
> bridge and expose the PCI device to the OS without changing any hardware
> settings.

When the patch series was submitted by Dan the last time (Fall 2016) the
conversation stalled with:

>Let's get some coherent text on how this device even operates out
>first and then we can decide if and how we can support it.

Christoph - are you looking for a whitepaper explaining this beyond the ACHI BAR
remapping documentation that was shared?
http://www.intel.com/content/www/us/en/chipsets/100-series-chipset-datasheet-vol-2.html

I think if we can have start with a list of actionable things needed for another
go at this and an acceptable design architecture before this thing is revisited again
to have a chance at solving it.  Are you amenable to a host bridge?

> Whatever answer we, in the Linux kernel community, come up with,
>leaving storage inaccessible is not an acceptable answer.

The thing that lives in the kernel now (aecec8b60422118b52e3347430ba9382e57d6d76)
really does a disservice to people trying to use Linux today:
>	dev_warn(&pdev->dev, "Found %d remapped NVMe devices.\n", count);
>	dev_warn(&pdev->dev, "Switch your BIOS from RAID to AHCI mode to use them.\n");

> 
> But as far as I know, the Intel group that owns this mode has not reached
> out to the Linux enabling with hardware specs that we can make public.
> The OEMS are probably in a better position to compel this to change than
> I am.

You mean the PCH registers associated with this stuff?

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 21:22                               ` Keith Busch
  2019-02-13 21:56                                 ` Mario.Limonciello
@ 2019-02-14  8:30                                 ` Christoph Hellwig
  1 sibling, 0 replies; 22+ messages in thread
From: Christoph Hellwig @ 2019-02-14  8:30 UTC (permalink / raw)


On Wed, Feb 13, 2019@02:22:53PM -0700, Keith Busch wrote:
> To the best of my knowledge, the hardware mode is working around a
> software limitation that doesn't apply to Linux.

More correctly it works around a business model limitation that allows
Intel to sell an "integrated" fake raid driver.  Even more importantly
it works around that business model limitation in a completely gross
way, unlike the vmd solution to the same problem in another intel
division, which at least allows to recover from that workaround.

> > As such, I don't think that disdaining the technology will get Intel to change it.
> > So I'm hoping we can constructively come up with something that works in the confines
> > of its existence to make it a better experience at least.
> 
> I assumed Chritoph's comment was directed toward said software that runs
> on the majority of the client PC market, leaving hardware vendors to
> think up "creative" work-arounds to its quirks to the detriment of other
> software environments. :(

It affects everyone but Intel, that is vendors of non-Intel NVMe SSDs
that have no control on what windows driver is used for their devices,
and it includes any OS that does not have an Intel driver that knows
how to deal with the magic intel AHCI device, which is entirely Intel
private.

Even with the patches from Dan we can't properly use the NVMe device:

 - there is no support for MSI/MSI-X and thus no support for per-queue
   interrupts, thus severly limiting performance
 - there is no support for PCI ID based quirks, which we require
   to support various devices properly
 - there is no way to make SR-IOV work
 - there is no way to make PCI-level FLRs work, or to unbind the
   device in case of a fatal failure

All in all Intel is using their domniance of the CPU and shipset
business to harm various other parties.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-13 21:56                                 ` Mario.Limonciello
@ 2019-02-14  8:33                                   ` Christoph Hellwig
  2019-02-14 11:41                                     ` Gerd Pokorra
  0 siblings, 1 reply; 22+ messages in thread
From: Christoph Hellwig @ 2019-02-14  8:33 UTC (permalink / raw)


On Wed, Feb 13, 2019@09:56:38PM +0000, Mario.Limonciello@dell.com wrote:
> > Pre-boot settings like you already have are preferable, right? Otherwise
> > it's a little more difficult to use the NVMe as your boot drive.
> 
> The SMM thing I mentioned would basically just be modifying those pre-boot settings
> so the next boot it could DTRT for Linux.
> 
> It's definitely just a band-aid to the problem.

So it is a one time setting?  If it was permanent it might at least
be useful for a little tool in the installer to offer that choice.
But either way it doesn't help to make the broken intel platforms to
just work.

> Christoph - are you looking for a whitepaper explaining this beyond the ACHI BAR
> remapping documentation that was shared?
> http://www.intel.com/content/www/us/en/chipsets/100-series-chipset-datasheet-vol-2.html
> 
> I think if we can have start with a list of actionable things needed for another
> go at this and an acceptable design architecture before this thing is revisited again
> to have a chance at solving it.  Are you amenable to a host bridge?

See the last mail for the functionality that is currently broken and
which needs to work.  Preferably without changes in the NVMe driver
itself, as that is not the place to work around intentionally buggy
platforms.

> 
> > Whatever answer we, in the Linux kernel community, come up with,
> >leaving storage inaccessible is not an acceptable answer.
> 
> The thing that lives in the kernel now (aecec8b60422118b52e3347430ba9382e57d6d76)
> really does a disservice to people trying to use Linux today:
> >	dev_warn(&pdev->dev, "Found %d remapped NVMe devices.\n", count);
> >	dev_warn(&pdev->dev, "Switch your BIOS from RAID to AHCI mode to use them.\n");
> 

Yes, we really need to ammend this message to tell people to complain
to Intel and their platform vendor for fucking up things this badly.

^ permalink raw reply	[flat|nested] 22+ messages in thread

* KXG60ZNV256G not recognized
  2019-02-14  8:33                                   ` Christoph Hellwig
@ 2019-02-14 11:41                                     ` Gerd Pokorra
  0 siblings, 0 replies; 22+ messages in thread
From: Gerd Pokorra @ 2019-02-14 11:41 UTC (permalink / raw)


Hello,

in the BIOS I set 'System Configuration' -> 'SATA Operation' from

 ? 'RAID On' to 'AHCI'.

After that I installed Windows new. Then I installed Ubuntu 18.04.1 
Sever. The installation works fine. I get the Dual-Boot menu and was 
able to create a partition for Linux on the NVMe SSD. This is what the 
owner of the laptop requested me to do for him.

Thank you for your great support!!!

-- Gerd


Am 14.02.2019 um 09:33 schrieb Christoph Hellwig:
> On Wed, Feb 13, 2019 at 09:56:38PM +0000, Mario.Limonciello at dell.com wrote:I
>>> Pre-boot settings like you already have are preferable, right? Otherwise
>>> it's a little more difficult to use the NVMe as your boot drive.
>> The SMM thing I mentioned would basically just be modifying those pre-boot settings
>> so the next boot it could DTRT for Linux.
>>
>> It's definitely just a band-aid to the problem.
> So it is a one time setting?  If it was permanent it might at least
> be useful for a little tool in the installer to offer that choice.
> But either way it doesn't help to make the broken intel platforms to
> just work.
>
>> Christoph - are you looking for a whitepaper explaining this beyond the ACHI BAR
>> remapping documentation that was shared?
>> http://www.intel.com/content/www/us/en/chipsets/100-series-chipset-datasheet-vol-2.html
>>
>> I think if we can have start with a list of actionable things needed for another
>> go at this and an acceptable design architecture before this thing is revisited again
>> to have a chance at solving it.  Are you amenable to a host bridge?
> See the last mail for the functionality that is currently broken and
> which needs to work.  Preferably without changes in the NVMe driver
> itself, as that is not the place to work around intentionally buggy
> platforms.
>
>>> Whatever answer we, in the Linux kernel community, come up with,
>>> leaving storage inaccessible is not an acceptable answer.
>> The thing that lives in the kernel now (aecec8b60422118b52e3347430ba9382e57d6d76)
>> really does a disservice to people trying to use Linux today:
>>> 	dev_warn(&pdev->dev, "Found %d remapped NVMe devices.\n", count);
>>> 	dev_warn(&pdev->dev, "Switch your BIOS from RAID to AHCI mode to use them.\n");
> Yes, we really need to ammend this message to tell people to complain
> to Intel and their platform vendor for fucking up things this badly.

^ permalink raw reply	[flat|nested] 22+ messages in thread

end of thread, other threads:[~2019-02-14 11:41 UTC | newest]

Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-13 10:07 KXG60ZNV256G not recognized Gerd Pokorra
2019-02-13 10:27 ` Johannes Thumshirn
2019-02-13 10:45   ` Gerd Pokorra
2019-02-13 10:51     ` Johannes Thumshirn
2019-02-13 11:06       ` Gerd Pokorra
2019-02-13 11:28         ` Gerd Pokorra
2019-02-13 11:50           ` Johannes Thumshirn
2019-02-13 13:58             ` Gerd Pokorra
2019-02-13 14:04               ` Johannes Thumshirn
2019-02-13 14:29                 ` Gerd Pokorra
2019-02-13 15:25                   ` Keith Busch
2019-02-13 18:00                   ` Christoph Hellwig
2019-02-13 18:04                     ` Mario.Limonciello
2019-02-13 18:18                       ` Keith Busch
2019-02-13 18:51                         ` Mario.Limonciello
2019-02-13 19:00                           ` Christoph Hellwig
2019-02-13 20:37                             ` Mario.Limonciello
2019-02-13 21:22                               ` Keith Busch
2019-02-13 21:56                                 ` Mario.Limonciello
2019-02-14  8:33                                   ` Christoph Hellwig
2019-02-14 11:41                                     ` Gerd Pokorra
2019-02-14  8:30                                 ` Christoph Hellwig

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.