Did not boot. Might try to flash to IT mode. Serial output:
Code:
DDR Version 1.20 20190314
This is an IBM br10i SAS card. I flashed it to IT mode, still no joy. This is the 4th card I've tried to use, the only success I've had is on a single SAS 4 port card. Anyone know what's going on? Thanks
Flashing success:
Code:
****************************************************************************
Serial boot messages:
Code:
DDR Version 1.20 20190314
In the log you presented, the following two failed at the initial stage of device detection.
This is almost equivalent to the absence of the card itself, and the kernel does nothing after that.
That is why the kernel did not crash.
https://forum.pine64.org/showthread.php?tid=8091
"EVGA geforce GT 730 P / N 01G-P3-2730-KR dmesg"
[3.347302] rockchip-pcie f8000000.pcie: PCIe link training gen1 timed out.
"Asus Hyper M.2 X4 dmesg"
[3.290551] rockchip-pcie f8000000.pcie: PCIe link training gen1 timed out.
---
Next is about the crash log you presented.
Other than you, there are quite a few reports of crashes in equivalent places.
It may be the same cause.
I do n’t know if a workaround exists,
It is recommended that you increase the loglevel and compare with other reports.
(* The log that you presented does not show what was executed before the crash because the loglevel is low)
https://forum.pine64.org/showthread.php?tid=8161
[3.240205] PC is at rockchip_pcie_rd_conf + 0x164 / 0x1b4
[3.240656] LR is at rockchip_pcie_rd_conf + 0x154 / 0x1b4
Thanks for the reply. I changed loglevel to 6 and got a new capture. Not really sure where to go from here, what should I look into to work on this? I think the synchronous external abort errors are the problem, but I don't know how to troubleshoot further.
Code:
DDR Version 1.20 20190314
Please try with "loglevel=7".
11-05-2019, 11:26 AM
(This post was last modified: 11-05-2019, 11:41 AM by kram0000 .
Edit Reason: Update
)
Very strange, I noticed a login prompt while using loglevel 7. Was able to login. I'll see if I can start running some debugging tools.
Attached Files ll7.txt (Size: 90.07 KB / Downloads: 404)
11-05-2019, 12:27 PM
(This post was last modified: 11-05-2019, 01:13 PM by kram0000 .)
rock@localhost:~$ lspci -vvv
Disabling msi by adding pci=nomsi to kernel boot options makes for a very quiet (no errors) boot, but still no card detected. Did get a PCIe gen 1 training confirmation.
[ 2.336232] rockchip-pcie f8000000.pcie: PCIe asserting reset
[ 2.337168] rockchip-pcie f8000000.pcie: advertising gen2/1 training
[ 2.337785] rockchip-pcie f8000000.pcie: PCIe reset released
[ 2.362277] rockchip-pcie f8000000.pcie: PCIe Gen1 link training completed
rock@localhost:~$ sudo lspci -vvv
00:00.0 PCI bridge: Device 1d87:0100 (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
Interrupt: pin A routed to IRQ 243
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00000000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: 00000000-000fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
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: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [b0] MSI-X: Enable- Count=1 Masked-
Vector table: BAR=0 offset=00000000
PBA: BAR=0 offset=00000008
Capabilities: [c0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x4, ASPM L1, Exit Latency L0s <256ns, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt+ AutBWInt+
LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
Slot #0, PowerLimit 0.000W; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
Control: AttnInd Off, PwrInd Off, 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 B, TimeoutDis+, LTR+, OBFF Via message ARIFwd+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 5GT/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: [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- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [274 v1] Transaction Processing Hints
Interrupt vector mode supported
Device specific mode supported
Steering table in TPH capability structure
Kernel driver in use: pcieport
rock@localhost:~$
Well, I might have found the problem. mrfixit's kernel doesn't have SAS support built.
rock@localhost:~$ cat running.config |grep -i sas
CONFIG_SCSI_SAS_ATTRS=m
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_ESAS2R is not set
# CONFIG_MEGARAID_SAS is not set
CONFIG_SCSI_MPT3SAS=m
CONFIG_SCSI_MPT2SAS_MAX_SGE=128
CONFIG_SCSI_MPT3SAS_MAX_SGE=128
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_NET_VENDOR_RENESAS is not set
# CONFIG_SND_SOC_STI_SAS is not set
rock@localhost:~$
I don't have the same card as you, but the crash points are the same.
And there are many other similar reports. For example, the report shown below.
https://github.com/ayufan-rock64/linux-build/issues/254
Unfortunately, in my case, using the "wait" insertion method suggested in this thread did not improve the situation.
---
Next, I would like to express my view on "ll7.txt" that you presented.
The log shows that "Gen1 Training" succeeded, but "Gen2 Training" failed and fell back to "Gen1".
And it crashes right after "pci 0000: 00: 00.0: bridge configuration invalid ([bus 00-00]), reconfiguring".
If it is functioning properly, the vendor ID acquisition should continue after this, but it ended in a crash before that.
[ 2.434952] rockchip-pcie f8000000.pcie: PCIe Gen1 link training completed
...
[ 2.935625] rockchip-pcie f8000000.pcie: PCIe link training gen2 timeout, fall back to gen1!
[ 2.936458] PCI host bridge /pcie@f8000000 ranges:
[ 2.936903] MEM 0xfa000000..0xfbdfffff -> 0xfa000000
[ 2.938606] IO 0xfbe00000..0xfbefffff -> 0xfbe00000
[ 2.939665] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[ 2.940277] pci_bus 0000:00: root bus resource [bus 00-1f]
[ 2.940763] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[ 2.941405] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[ 2.942889] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
--- Crash occurred ---
[ 2.943789] Synchronous External Abort: synchronous external abort (0x96000210) at 0xffffff800c100000
[ 2.944600] Internal error: : 96000210 [#1] SMP
[ 2.945000] Modules linked in: midgard_kbase dw_hdmi_i2s_audio phy_rockchip_pcie rockchip_saradc
[ 2.945796] CPU: 2 PID: 6 Comm: kworker/u12:0 Not tainted 4.4.180 #1
[ 2.946352] Hardware name: Pine64 RockPro64 (DT)
[ 2.946771] Workqueue: deferwq deferred_probe_work_func
[ 2.947234] task: ffffffc0f3244380 task.stack: ffffffc0f3278000
[ 2.947758] PC is at rockchip_pcie_rd_conf+0x164/0x1b4
[ 2.948210] LR is at rockchip_pcie_rd_conf+0x154/0x1b4
[ 2.948661] pc : [<ffffff80084a1220>] lr : [<ffffff80084a1210>] pstate: 600001c5
[ 2.949305] sp : ffffffc0f327b7e0
[ 2.949598] x29: ffffffc0f327b7e0 x28: 0000000000000000
[ 2.950070] x27: 0000000000000001 x26: 0000000000000000
[ 2.950542] x25: 0000000000000000 x24: ffffffc0f0d6c800
> but still no card detected
This is why the card is not detected by sudo lspci -vvv
If "rockchip-pcie f8000000.pcie: PCIe probe completed successfully" is executed correctly,
Even if there is no driver, the card itself is detected by "lspci -vvv".
Like the "PNY Nvidia Quadro lspci -vvv" log you presented.
---
This is a proposal.
You point out kernel build options.
Therefore, I think that you are at a level where you can easily change "dtb".
First try to limit the number of lanes ("num-lanes")
If there is still no improvement, try limiting the link speed ("max-link-speed")
I hope the situation will improve, even a little.
And the "driver presence" that you point out is after this hurdle has been overcome.
---
Finally, I will state my view.
My conclusion is that Rockpro64's "PCIE-Express" originally has little margin.
Many people point out that power supply is suspected, but I think this is not correct.
Because, I own three Rockpro64, but all three work differently.
(One unit is unstable, two units operate stably, but performance is different)
Except for Rockpro64, all conditions are the same, so it is not reasonable to doubt the power supply.
Thanks for your input, I got the card to recognize in lspci. First try was max_link_speed 1 and num_lanes 1, the rockpro booted but lspci was blank.
I changed num-lanes to 4 and now I have lspci output! Still on link speed 1 though...
Here's the lspci output and dmesg is attached.
Code:
01:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08)
Attached Files dmesg_lanes_4_speed_1.txt (Size: 81.68 KB / Downloads: 469)
(11-14-2019, 12:21 AM) kram0000 Wrote:
Could you please let me know how did you manage to change number of lines?
I've got the SBC not booting up with the RAID H1110 and suspect the power isn't enough to supply it.
