Hi,
we connected a network Storage (QNAP) on 10 GbE on Nvidia PX2 for data logging purposes. While testing, we noticed that somethimes network driver crashes, and that the writing speed can’t go over 130/150 Mbs. Is there some writing speed limit? If not, do you know why is it happening?
Thanks in advance,
Anja
anja,
Could you share the dmesg when this error is reproduced?
Hi,
here is the dmsg log:
[ 440.645833] NOHZ: local_softirq_pending 80
[ 441.073823] NOHZ: local_softirq_pending 80
[ 441.352947] ixgbe 0000:03:00.0 enp3s0: Received unrecoverable ECC Err,initiating reset.
[ 441.357872] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 441.368547] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 441.374803] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 441.384298] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 441.393814] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 441.403348] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 441.412834] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 447.277819] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 448.210210] ixgbe 0000:03:00.0 enp3s0: Detected Tx Unit Hang
Tx Queue <2>
TDH, TDT <0>, <3>
next_to_use <3>
next_to_clean <0>
[ 448.210214] ixgbe 0000:03:00.0 enp3s0: Detected Tx Unit Hang
Tx Queue <3>
TDH, TDT <0>, <4>
next_to_use <4>
next_to_clean <0>
[ 448.210222] ixgbe 0000:03:00.0 enp3s0: tx_buffer_info[next_to_clean]
time_stamp <100008fd6>
jiffies <1000090bc>
[ 448.210225] ixgbe 0000:03:00.0 enp3s0: Detected Tx Unit Hang
Tx Queue <0>
TDH, TDT <0>, <5>
next_to_use <5>
next_to_clean <0>
[ 448.210227] ixgbe 0000:03:00.0 enp3s0: tx hang 2 detected on queue 3, resetting adapter
[ 448.210229] ixgbe 0000:03:00.0 enp3s0: tx_buffer_info[next_to_clean]
time_stamp <100008fd3>
jiffies <1000090bc>
[ 448.210232] ixgbe 0000:03:00.0 enp3s0: tx hang 2 detected on queue 0, resetting adapter
[ 448.210244] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 448.216427] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 448.216576] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 448.216702] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 448.216819] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 448.216948] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 448.217073] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 448.362440] ixgbe 0000:03:00.0 enp3s0: tx_buffer_info[next_to_clean]
time_stamp <100009080>
jiffies <1000090e2>
[ 448.377755] ixgbe 0000:03:00.0 enp3s0: tx hang 3 detected on queue 2, resetting adapter
[ 454.203769] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 455.048774] ixgbe 0000:03:00.0 enp3s0: Detected Tx Unit Hang
Tx Queue <0>
TDH, TDT <0>, <5>
next_to_use <5>
next_to_clean <0>
[ 455.066577] ixgbe 0000:03:00.0 enp3s0: tx_buffer_info[next_to_clean]
time_stamp <100009696>
jiffies <10000976e>
[ 455.081726] ixgbe 0000:03:00.0 enp3s0: tx hang 3 detected on queue 0, resetting adapter
[ 455.081743] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 455.092949] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 455.099208] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 455.108699] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 455.118275] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 455.127677] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 455.137251] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 460.932291] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 461.938211] ixgbe 0000:03:00.0 enp3s0: Detected Tx Unit Hang
Tx Queue <0>
TDH, TDT <0>, <5>
next_to_use <5>
next_to_clean <0>
[ 461.938249] ixgbe 0000:03:00.0 enp3s0: Detected Tx Unit Hang
Tx Queue <3>
TDH, TDT <0>, <1>
next_to_use <1>
next_to_clean <0>
[ 461.938255] ixgbe 0000:03:00.0 enp3s0: Detected Tx Unit Hang
Tx Queue <4>
TDH, TDT <0>, <2>
next_to_use <2>
next_to_clean <0>
[ 461.938261] ixgbe 0000:03:00.0 enp3s0: tx_buffer_info[next_to_clean]
time_stamp <100009d2d>
jiffies <100009e24>
[ 461.938271] ixgbe 0000:03:00.0 enp3s0: tx_buffer_info[next_to_clean]
time_stamp <100009d94>
jiffies <100009e24>
[ 461.938274] ixgbe 0000:03:00.0 enp3s0: tx hang 4 detected on queue 3, resetting adapter
[ 461.938280] ixgbe 0000:03:00.0 enp3s0: tx hang 4 detected on queue 4, resetting adapter
[ 461.938307] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 461.944485] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 461.944610] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 461.944735] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 461.944861] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 461.944981] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 461.945106] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 462.090435] ixgbe 0000:03:00.0 enp3s0: tx_buffer_info[next_to_clean]
time_stamp <100009d28>
jiffies <100009e4a>
[ 462.105754] ixgbe 0000:03:00.0 enp3s0: tx hang 5 detected on queue 0, resetting adapter
[ 467.665817] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 467.781968] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 467.782231] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 468.769783] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 468.776824] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 468.783077] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 468.792569] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 468.802057] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 468.811553] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 468.821031] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 474.407560] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 474.526228] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 474.526494] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 475.489776] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 475.497565] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 475.503818] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 475.513307] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 475.522796] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 475.532285] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 475.542975] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 481.190251] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 481.305714] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 481.306018] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 482.209782] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 482.243971] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 482.250235] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 482.259718] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 482.269206] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 482.278695] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 482.288265] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 487.867890] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 487.984538] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 487.984801] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 488.961776] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 494.748936] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 494.869723] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 494.870024] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 495.649792] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 501.230376] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 501.347230] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 501.347493] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 502.337783] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 502.343840] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 502.350088] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 502.359581] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 502.369068] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 502.378558] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 502.388044] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 508.042855] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 509.202127] ixgbe 0000:03:00.0 enp3s0: Detected Tx Unit Hang
Tx Queue <0>
TDH, TDT <0>, <6>
next_to_use <6>
next_to_clean <0>
[ 509.202140] ixgbe 0000:03:00.0 enp3s0: Detected Tx Unit Hang
Tx Queue <3>
TDH, TDT <0>, <3>
next_to_use <3>
next_to_clean <0>
[ 509.202153] ixgbe 0000:03:00.0 enp3s0: tx_buffer_info[next_to_clean]
time_stamp <10000cb2a>
jiffies <10000cc4c>
[ 509.202158] ixgbe 0000:03:00.0 enp3s0: tx hang 11 detected on queue 3, resetting adapter
[ 509.202184] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 509.208358] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 509.208476] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 509.208593] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 509.208711] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 509.208829] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 509.208947] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 509.318145] ixgbe 0000:03:00.0 enp3s0: tx_buffer_info[next_to_clean]
time_stamp <10000cb2d>
jiffies <10000cc69>
[ 509.333296] ixgbe 0000:03:00.0 enp3s0: tx hang 12 detected on queue 0, resetting adapter
[ 515.173875] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 515.293773] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 515.294036] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 516.001781] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 521.783521] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 521.902115] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 521.902379] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 522.689777] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 522.697571] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 522.703902] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 522.713389] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 522.722878] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 522.732370] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 522.741881] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 528.595255] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 528.711801] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 528.712065] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 529.441792] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 529.449588] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 529.455925] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 529.465414] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 529.474912] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 529.484401] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 529.494091] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 535.502990] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 535.622142] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 535.622405] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 536.193785] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 541.990710] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 542.109711] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 542.110005] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 542.881779] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 548.549815] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 548.667745] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 548.668007] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 549.569782] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 555.378137] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 556.361791] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 556.362056] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 556.465784] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 562.052750] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 562.171356] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 562.171620] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
[ 563.137787] ixgbe 0000:03:00.0 enp3s0: Reset adapter
[ 563.145576] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
[ 563.151839] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
[ 563.161317] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
[ 563.170808] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
[ 563.180373] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
[ 563.189885] ixgbe 0000:03:00.0 enp3s0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
[ 568.773422] ixgbe 0000:03:00.0 enp3s0: NIC Link is Up 10 Gbps, Flow Control: None
[ 568.890444] ixgbe 0000:03:00.0 enp3s0: NIC Link is Down
[ 568.890707] ixgbe 0000:03:00.0 enp3s0: initiating reset due to lost link with pending Tx work
anja,
What is the network layout in your usecase?
PX id directly connected with eth cable from 10GbE interface to QNAP 10GbE interface.
anja,
Could you get better performance if you connect your storage to a ubutnu host?
yes, we connected it to the ubuntu host and the speed was up to 400 MB/s, and it didn’t crash
Hi Anja,
Could you provide the QNAP model you tested? We didn’t run the test for direct connected with eth cable from PX2 10GbE interface to QNAP 10GbE interface before, may need to check if able to final similar device to reproduce the issue.
Thanks
anja,
Please also try to run with script “sudo ./jetson_clock.sh” and see if performance has enhancement. Do you install any extra driver by yourself?
Hi,
QNAP model is TS-453B. Ok, I’ll try to run with that script and let u know the results.
Thanks
Hi,
I haven’t installed any additional drivers, also were can I find jetson_clocks script on my NVIDIA PX2?
Thanks,
anja,
Sorry for my wrong reply. jetson_clocks is for TX2 but not PX2.
Could you share the result of your tegrastats?
cd /home/nvidia
sudo ./tegrastats
Hi,
here is the result in the moment of the crash.
RAM 1146/6668MB (lfb 1256x4MB) CPU [5%@1990,0%@2035,0%@2034,4%@1988,0%@1991,0%@1991] EMC_FREQ 2%@1600 GR3D_FREQ 0%@1275 APE 245 MTS fg 0% bg 0% GR3D_PCI 0%@2 PLL@45.5C MCPU@45.5C Tegra@0C Tdiode@51.25C AO@45C GPU@51.5C BCPU@45.5C thermal@51.25C Tegra@51.25C Tj@51.25C
RAM 1146/6668MB (lfb 1256x4MB) CPU [3%@1991,0%@2035,0%@2034,2%@1991,1%@1994,0%@1995] EMC_FREQ 2%@1600 GR3D_FREQ 0%@1275 APE 245 MTS fg 0% bg 0% GR3D_PCI 0%@2 PLL@45.5C MCPU@45.5C Tegra@0C Tdiode@51.5C AO@45C GPU@51.5C BCPU@45.5C thermal@51.25C Tegra@51.5C Tj@51.5C
RAM 1147/6668MB (lfb 1256x4MB) CPU [6%@1994,0%@2035,0%@2035,2%@1992,1%@1989,0%@1991] EMC_FREQ 2%@1600 GR3D_FREQ 0%@1275 APE 245 MTS fg 0% bg 0% GR3D_PCI 0%@2 PLL@45.5C MCPU@45.5C Tegra@0C Tdiode@51.25C AO@45C GPU@51.5C BCPU@45.5C thermal@51.25C Tegra@51.25C Tj@51.25C
RAM 1146/6668MB (lfb 1256x4MB) CPU [4%@1994,0%@2035,0%@2035,1%@1991,0%@1993,0%@1994] EMC_FREQ 1%@1600 GR3D_FREQ 0%@1275 APE 245 MTS fg 0% bg 0% GR3D_PCI 0%@2 PLL@45.5C MCPU@45.5C Tegra@0C Tdiode@51.5C AO@45C GPU@51.5C BCPU@45.5C thermal@51.25C Tegra@51.5C Tj@51.5C
RAM 1146/6668MB (lfb 1256x4MB) CPU [9%@1996,0%@2034,0%@2035,4%@1997,3%@1996,2%@1996] EMC_FREQ 1%@1600 GR3D_FREQ 0%@1275 APE 245 MTS fg 0% bg 0% GR3D_PCI 0%@2 PLL@45.5C MCPU@45.5C Tegra@0C Tdiode@51.5C AO@45C GPU@51.5C BCPU@45.5C thermal@51.25C Tegra@51.5C Tj@51.5C
RAM 1146/6668MB (lfb 1256x4MB) CPU [8%@1992,0%@2034,0%@2035,5%@1990,4%@1991,2%@1992] EMC_FREQ 1%@1600 GR3D_FREQ 0%@1275 APE 245 MTS fg 0% bg 0% GR3D_PCI 0%@2 PLL@46C MCPU@46C Tegra@0C Tdiode@51.5C AO@45C GPU@52C BCPU@46C thermal@51.5C Tegra@51.5C Tj@51.5C
RAM 1151/6668MB (lfb 1255x4MB) CPU [22%@1993,11%@2036,12%@2035,22%@1990,15%@1992,13%@1992] EMC_FREQ 2%@1600 GR3D_FREQ 0%@1275 APE 245 MTS fg 0% bg 1% GR3D_PCI 0%@2 PLL@46C MCPU@46C Tegra@0C Tdiode@51.5C AO@45C GPU@52C BCPU@46C thermal@51.5C Tegra@51.5C Tj@51.5C
RAM 1151/6668MB (lfb 1255x4MB) CPU [11%@1990,0%@2034,0%@2034,9%@1989,4%@1990,8%@1990] EMC_FREQ 2%@1600 GR3D_FREQ 0%@1275 APE 245 MTS fg 0% bg 0% GR3D_PCI 0%@2 PLL@46C MCPU@46C Tegra@0C Tdiode@51.5C AO@45C GPU@52C BCPU@46C thermal@51.5C Tegra@51.5C Tj@51.5C
anja,
Sorry that we don’t have such devices that can reproduce this issue. Could you elaborate more about what interface is it using?
Is it a SSD or mounting?
Hi,
it’s SSD.
Is there some other configuration or way how we can connect some storage to work faster?
anja,
Sorry for the late reply. Our internal team would like to know more about your usecase
So it is a SSD storage and connected through 10GbE port with PX2, is it correct?
How does tegra r/w file to that storage? Any step to set up this device?
Could you share the full dmesg (along with the error message)?
Please share how to reproduce this issue.
Hi,
to reproduce the issue, one of the ways is to use iperf. Connect Nvidia to some other computer with 10GbE. On Nvidia write in terminal, for example “iperf -c 192.168.x.x (IP address of server) -t 100”. On the other computer write iperf -s. It usually crashes in couple of seconds. Just to mention one more time, this bug happens just on one of our Nvidia computers, the other we tested was ok!
anja,
If all devices are using same SW BSP, it feels like it is a hardware issue on that PX2…
I’ll try to see if I can reproduce issue on our side.