08-22-2018, 08:58 PM
I'm excited about the RockPro64. It just arrived the other day. Sadly, I can't get the PCI-E -> Sata adapter card (also bought through Pine64) to work.
Symptoms:
System locks up hard when anything tries to touch a drive connected to the PCI-E SATA ports. Something as simple as `lspci -v` or `cfdisk /dev/sda` will lock the system and force a reset. Attempting to mount a partition has the same result.
Things I've ruled out:
It's not the drive. I tried multiple drives, all of which work fine in other systems. I was able to mount and use the same drives on my rockpro64 using an old usb2->sata adapter that I had lying around.
I don't think it's the OS images. I tried ayufan's lxde and minimal images, the latest stable 0.7.9 version.
I don't think it's this flaw: https://forum.pine64.org/announcements.php?aid=6 ... my board has a date stamp of 2018-06-06 and the schematics in that engineering notice do not match the power regulator design on my board.
Things I suspect:
I'm not an EE and it's likely that I don't know what I'm looking at, but I suspect there may still be a PCI-E power regulation defect in these boards. Yes, despite the hardware rev. `grep pcie /var/log/syslog` turns up lots of weirdness, including:
...halp? What do? I'm not sure how to troubleshoot this further. I'm 90% sure this is hardware related. If there is a known fix, I'm a steady hand with a soldering iron or a rework station. If there's not a known fix, is there a way to return this whole setup?
Symptoms:
System locks up hard when anything tries to touch a drive connected to the PCI-E SATA ports. Something as simple as `lspci -v` or `cfdisk /dev/sda` will lock the system and force a reset. Attempting to mount a partition has the same result.
Things I've ruled out:
It's not the drive. I tried multiple drives, all of which work fine in other systems. I was able to mount and use the same drives on my rockpro64 using an old usb2->sata adapter that I had lying around.
I don't think it's the OS images. I tried ayufan's lxde and minimal images, the latest stable 0.7.9 version.
I don't think it's this flaw: https://forum.pine64.org/announcements.php?aid=6 ... my board has a date stamp of 2018-06-06 and the schematics in that engineering notice do not match the power regulator design on my board.
Things I suspect:
I'm not an EE and it's likely that I don't know what I'm looking at, but I suspect there may still be a PCI-E power regulation defect in these boards. Yes, despite the hardware rev. `grep pcie /var/log/syslog` turns up lots of weirdness, including:
Code:
Jul 26 08:43:40 rockpro64 kernel: [ 0.504648] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
Jul 26 08:43:40 rockpro64 kernel: [ 0.504700] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [ 0.504739] vcc3v3_pcie: supplied by dc_12v
Jul 26 08:43:40 rockpro64 kernel: [ 0.504804] vcc3v3_pcie: 3300 mV
Jul 26 08:43:40 rockpro64 kernel: [ 0.504959] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
Jul 26 08:43:40 rockpro64 kernel: [ 2.854241] vcc3v3_pcie: disabling
Jul 26 08:43:40 rockpro64 kernel: [ 3.185787] phy phy-pcie-phy.9: Looking up phy-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [ 3.185794] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
Jul 26 08:43:40 rockpro64 kernel: [ 3.242826] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
Jul 26 08:43:40 rockpro64 kernel: [ 3.242833] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
Jul 26 08:43:40 rockpro64 kernel: [ 3.242849] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
Jul 26 08:43:40 rockpro64 kernel: [ 3.242997] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [ 3.243058] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [ 3.243063] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
Jul 26 08:43:40 rockpro64 kernel: [ 3.243081] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
Jul 26 08:43:40 rockpro64 kernel: [ 3.246321] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [ 3.246332] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
Jul 26 08:43:40 rockpro64 kernel: [ 3.246349] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
Jul 26 08:43:40 rockpro64 kernel: [ 3.249224] rockchip-pcie f8000000.pcie: invalid power supply
Jul 26 08:43:40 rockpro64 kernel: [ 3.297572] PCI host bridge /pcie@f8000000 ranges:
Jul 26 08:43:40 rockpro64 kernel: [ 3.312065] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
Jul 26 08:43:40 rockpro64 kernel: [ 3.396326] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
Jul 26 08:43:40 rockpro64 kernel: [ 3.399224] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
Jul 26 08:43:40 rockpro64 kernel: [ 3.404688] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
Jul 26 08:43:40 rockpro64 kernel: [ 3.404779] aer 0000:00:00.0:pcie02: service driver aer loaded
Aug 23 01:44:21 rockpro64 kernel: [ 854.222319] Modules linked in: zram lz4_compress rockchip_saradc ip_tables x_tables autofs4 phy_rockchip_pcie midgard_kbase dw_hdmi_i2s_audio
Aug 23 01:48:14 rockpro64 kernel: [ 0.502604] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
Aug 23 01:48:14 rockpro64 kernel: [ 0.502653] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [ 0.502693] vcc3v3_pcie: supplied by dc_12v
Aug 23 01:48:14 rockpro64 kernel: [ 0.502758] vcc3v3_pcie: 3300 mV
Aug 23 01:48:14 rockpro64 kernel: [ 0.502914] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
Aug 23 01:48:14 rockpro64 kernel: [ 2.926112] vcc3v3_pcie: disabling
Aug 23 01:48:14 rockpro64 kernel: [ 3.390905] phy phy-pcie-phy.9: Looking up phy-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [ 3.390914] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
Aug 23 01:48:14 rockpro64 kernel: [ 3.479972] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
Aug 23 01:48:14 rockpro64 kernel: [ 3.479988] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
Aug 23 01:48:14 rockpro64 kernel: [ 3.480049] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
Aug 23 01:48:14 rockpro64 kernel: [ 3.480441] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [ 3.480703] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [ 3.480717] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
Aug 23 01:48:14 rockpro64 kernel: [ 3.480757] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
Aug 23 01:48:14 rockpro64 kernel: [ 3.489203] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [ 3.489223] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
Aug 23 01:48:14 rockpro64 kernel: [ 3.489259] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
Aug 23 01:48:14 rockpro64 kernel: [ 3.497732] rockchip-pcie f8000000.pcie: invalid power supply...halp? What do? I'm not sure how to troubleshoot this further. I'm 90% sure this is hardware related. If there is a known fix, I'm a steady hand with a soldering iron or a rework station. If there's not a known fix, is there a way to return this whole setup?