+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=98)
+--- Forum: RockPro64 Hardware and Accessories (https://forum.pine64.org/forumdisplay.php?fid=102)
+--- Thread: Discovered issues with PCIe NVMe & GPU Load in desktop 4.4.174 causing board lockup (/showthread.php?tid=7360)
Discovered issues with PCIe NVMe & GPU Load in desktop 4.4.174 causing board lockup - axelf - 04-08-2019
I suspect that this is something I need to bring to Ayufan but I am running the following kernel rockpro64 4.4.174-rockchip64
I can recreate stability issues caused by the PCIe Kernel Driver.
While it works in server mode with no desktop, it is inherently unstable while in desktop display mode and hangs the entire Board every time when booting into XOrg using this kernel. Every time I remove the PCIe I get a desktop that boots into the desktop. With other kernels I get a desktop that hangs repeatably when loading a browser that triggers the GPU to draw power.
Looking at the power Specifications for PCIe x 4 => Suggest that it can be powered from 3.3v (9.9W) & 12v (25W), however from the RockPro64 Power schema it looks like they negate to feed the 12v rail from the Supply voltage.
Instead it suggests to me Pine feeds the PCIe Interface on the board only by the 3.3v rail (9.9W).
From the Power schema It also looks like the board designers feed PCIe from the 5.1v rail converted by the RK808 PMU to 1.8v on vcc1v8_pcie (not sure how this is intended to be used on PCIe)
I am using the Pine PCIe ver 3.0 NVMe Card with a Samsung 970 EVO 500GB and a RockPro64 v2.1 Board. PSU is a 102W 12v LRS-100-12
The Max power draw of the EVO 970 NVMe is 5.8W which should be within spec ...
But this bit worry's me "vcc_sys: could not add device link regulator.6 err -2"
vcc_sys is the 3.3v rail that feeds the vcc3v3_pcie feed into the PCIe Socket.
I also see this warning;
"Apr 8 19:09:24 localhost kernel: [ 2.010352] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus 00-1f] (conflicts with (null) [bus 00-1f])"
Anybody else have this issue when running as desktop + PCIe NVMe ?
When I check dmesg it looks like there is a driver issue ...
Apr 8 19:09:24 localhost kernel: [ 2.009280] PCI host bridge /pcie@f8000000 ranges:
Apr 8 19:09:24 localhost kernel: [ 2.009313] MEM 0xfa000000..0xfbdfffff -> 0xfa000000
Apr 8 19:09:24 localhost kernel: [ 2.009326] IO 0xfbe00000..0xfbefffff -> 0xfbe00000
Apr 8 19:09:24 localhost kernel: [ 2.009679] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
Apr 8 19:09:24 localhost kernel: [ 2.009695] pci_bus 0000:00: root bus resource [bus 00-1f]
Apr 8 19:09:24 localhost kernel: [ 2.009708] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
Apr 8 19:09:24 localhost kernel: [ 2.009721] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
Apr 8 19:09:24 localhost kernel: [ 2.009760] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
Apr 8 19:09:24 localhost kernel: [ 2.009867] pci 0000:00:00.0: supports D1
Apr 8 19:09:24 localhost kernel: [ 2.009878] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
Apr 8 19:09:24 localhost kernel: [ 2.010213] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
Apr 8 19:09:24 localhost kernel: [ 2.010352] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus 00-1f] (conflicts with (null) [bus 00-1f])
Apr 8 19:09:24 localhost kernel: [ 2.010388] pci 0000:01:00.0: [144d:a808] type 00 class 0x010802
Apr 8 19:09:24 localhost kernel: [ 2.010445] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
Apr 8 19:09:24 localhost kernel: [ 2.016093] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
Apr 8 19:09:24 localhost kernel: [ 2.016136] pci 0000:00:00.0: BAR 8: assigned [mem 0xfa000000-0xfa0fffff]
Apr 8 19:09:24 localhost kernel: [ 2.016153] pci 0000:01:00.0: BAR 0: assigned [mem 0xfa000000-0xfa003fff 64bit]
Apr 8 19:09:24 localhost kernel: [ 2.016175] pci 0000:00:00.0: PCI bridge to [bus 01]
Apr 8 19:09:24 localhost kernel: [ 2.016190] pci 0000:00:00.0: bridge window [mem 0xfa000000-0xfa0fffff]
Apr 8 19:09:24 localhost kernel: [ 2.016263] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
Apr 8 19:09:24 localhost kernel: [ 2.016556] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
Apr 8 19:09:24 localhost kernel: [ 2.016567] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Apr 8 19:09:24 localhost kernel: [ 2.016581] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
Apr 8 19:09:24 localhost kernel: [ 2.016710] aer 0000:00:00.0:pcie02: service driver aer loaded
Apr 8 19:09:24 localhost kernel: [ 1.440486] of_get_named_gpiod_flags: parsed 'rockchip,power-ctrl' property of node '/rockchip-suspend[0]' - status (0)
Apr 8 19:09:24 localhost kernel: [ 1.440524] of_get_named_gpiod_flags: parsed 'rockchip,power-ctrl' property of node '/rockchip-suspend[1]' - status (0)
Apr 8 19:09:24 localhost kernel: [ 1.440774] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/dc-12v[0]'
Apr 8 19:09:24 localhost kernel: [ 1.440795] dc_12v: 12000 mV
Apr 8 19:09:24 localhost kernel: [ 1.440960] reg-fixed-voltage dc-12v: dc_12v supplying 12000000uV
Apr 8 19:09:24 localhost kernel: [ 1.441128] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
Apr 8 19:09:24 localhost kernel: [ 1.441173] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
Apr 8 19:09:24 localhost kernel: [ 1.441213] vcc3v3_pcie: supplied by dc_12v
Apr 8 19:09:24 localhost kernel: [ 1.441221] dc_12v: could not add device link regulator.2 err -2
Apr 8 19:09:24 localhost kernel: [ 1.441262] vcc3v3_pcie: 3300 mV
Apr 8 19:09:24 localhost kernel: [ 1.441414] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
Apr 8 19:09:24 localhost kernel: [ 1.441466] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc1v8-s0[0]'
Apr 8 19:09:24 localhost kernel: [ 1.441481] vcc1v8_s0: 1800 mV
Apr 8 19:09:24 localhost kernel: [ 1.441637] reg-fixed-voltage vcc1v8-s0: vcc1v8_s0 supplying 1800000uV
Apr 8 19:09:24 localhost kernel: [ 1.441691] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc-sys[0]'
Apr 8 19:09:24 localhost kernel: [ 1.441711] reg-fixed-voltage vcc-sys: Looking up vin-supply from device tree
Apr 8 19:09:24 localhost kernel: [ 1.441745] vcc_sys: supplied by dc_12v
Apr 8 19:09:24 localhost kernel: [ 1.441753] dc_12v: could not add device link regulator.4 err -2
Apr 8 19:09:24 localhost kernel: [ 1.441780] vcc_sys: 5000 mV
Apr 8 19:09:24 localhost kernel: [ 1.441922] reg-fixed-voltage vcc-sys: vcc_sys supplying 5000000uV
Apr 8 19:09:24 localhost kernel: [ 1.441969] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc-phy-regulator[0]'
Apr 8 19:09:24 localhost kernel: [ 1.441984] vcc_phy: no parameters
Apr 8 19:09:24 localhost kernel: [ 1.442133] reg-fixed-voltage vcc-phy-regulator: vcc_phy supplying 0uV
Apr 8 19:09:24 localhost kernel: [ 1.442185] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc3v3-sys[0]'
Apr 8 19:09:24 localhost kernel: [ 1.442204] reg-fixed-voltage vcc3v3-sys: Looking up vin-supply from device tree
Apr 8 19:09:24 localhost kernel: [ 1.442239] vcc3v3_sys: supplied by vcc_sys
Apr 8 19:09:24 localhost kernel: [ 1.442247] vcc_sys: could not add device link regulator.6 err -2
Apr 8 19:09:24 localhost kernel: [ 1.442272] vcc3v3_sys: 3300 mV
Apr 8 19:09:24 localhost kernel: [ 1.442418] reg-fixed-voltage vcc3v3-sys: vcc3v3_sys supplying 3300000uV
Apr 8 19:09:24 localhost kernel: [ 1.442547] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc5v0-host-regulator[0]' - status (0)
Apr 8 19:09:24 localhost kernel: [ 1.442586] vcc5v0_host: no parameters
Apr 8 19:09:24 localhost kernel: [ 1.442746] reg-fixed-voltage vcc5v0-host-regulator: vcc5v0_host supplying 0uV
Apr 8 19:09:24 localhost kernel: [ 1.443353] iommu: Adding device ff8f0000.vop to group 0
Apr 8 19:09:24 localhost kernel: [ 1.443432] platform ff8f0000.vop: iommu /iommu@ff8f3f00 not found
Apr 8 19:09:24 localhost kernel: [ 1.443438] iommu: Removing device ff8f0000.vop from group 0
Apr 8 19:09:24 localhost kernel: [ 1.443494] iommu: Adding device ff900000.vop to group 0