Author Topic: cubietruck NIC corrupting data?  (Read 28558 times)

Offline foef

  • Newbie
  • *
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #15 on: June 07, 2014, 08:06:04 am »
Also just tried the other kernel (3.4.91). Still same problem.

Offline foef

  • Newbie
  • *
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #16 on: June 08, 2014, 04:04:37 am »
Tried another debian.

http://www.cubieforums.com/index.php/topic,1087.0.html
https://googledrive.com/host/0B-WNHX6itPwQV1M0WXpNS291Q1k/


Code: [Select]
Linux debian 3.4.61+ #1 SMP PREEMPT Sat Nov 2 16:30:39 CST 2013 armv7l GNU/Linux
Cannot reproduce rsync ssh error. WORKS

Will stick to this one for now. Have a second sd card I can use to try future CTDebian releases with updated kernels.

Not sure whether the non-sun7i+ kernel is worse?

Offline db260179

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #17 on: June 11, 2014, 04:03:22 pm »
try https://github.com/cubieboard/linux-sunxi.git

ct/sunxi-3.4 branch

This is a more up to date of the original cubie kernel 3.4.79

Offline foef

  • Newbie
  • *
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #18 on: June 13, 2014, 09:26:50 pm »
try https://github.com/cubieboard/linux-sunxi.git

ct/sunxi-3.4 branch

This is a more up to date of the original cubie kernel 3.4.79

Do I need to compile? I don't have a build environment and unfortunately not the time and skill(?) to set one up.

Furthermore, CTDbebian 2.1 (3.4.91) was released. Just tried. Same problem.

Offline slovenia

  • Hero Member
  • *****
  • Posts: 511
  • Karma: +47/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #19 on: June 25, 2014, 01:36:30 am »
Since we still haven't found what is causing this it would be helpful if you could try this with some older images too.

1.6 and/or older.
http://www.igorpecovnik.com/2013/12/24/cubietruck-debian-wheezy-sd-card-image/

Thanks.

EDIT:
I got confirmation that the error reaper in all old images what means something is wrong down to 3.4.75 or more when I started this project. It looks that .61 (don't have source) have different gmac driver or else has been changed.

It's probably not related but jumbo frames can be enabled in that kernel while it's not available in others.
« Last Edit: June 26, 2014, 12:56:09 am by slovenia »
Debian and Ubuntu images with kernel 3.4.110, 4.3.3, 4.4
http://www.armbian.com

Offline foef

  • Newbie
  • *
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #20 on: June 26, 2014, 09:31:38 am »
Just put 1.6 on a SD card.

The kernel is 3.4.75-sun7i+

So far I must have copied around 10GB of data over rsync/ssh and so far NO CORRUPTION. Will check back once its finished.

Thank you for your effort with the CTDebian. Let me know if I can do any more testing.

On a side note: Should this thread be continued in OS section? It's not a hardware issue as it turned out.

Offline D_NRW

  • Jr. Member
  • **
  • Posts: 65
  • Karma: +3/-0
    • View Profile
    • Dan-And
Re: cubietruck NIC corrupting data?
« Reply #21 on: June 26, 2014, 10:59:58 am »
Slovenia, Foef,

Are there Voltage or DRAM Timing differenes between the 1.6 and newer images by Slovenia?

I own 8 cubieboards (A20 Boards and Cubietrucks) and I see great differences in the way how they react on timing and voltage changes. I'm just mention this here, as it is so tough to reproduce your issue and maybe it is caused by board settings of the FEX.

Regards

Daniel

Offline slovenia

  • Hero Member
  • *****
  • Posts: 511
  • Karma: +47/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #22 on: June 26, 2014, 01:28:34 pm »
Slovenia, Foef,

Are there Voltage or DRAM Timing differenes between the 1.6 and newer images by Slovenia?

I own 8 cubieboards (A20 Boards and Cubietrucks) and I see great differences in the way how they react on timing and voltage changes. I'm just mention this here, as it is so tough to reproduce your issue and maybe it is caused by board settings of the FEX.

Regards

Daniel

There were changes in settings but long time age: authored on 23 Nov 2013 https://github.com/cubieboard/cubie_configs

I think all my images are done with those settings but I am not 100% sure.

I also suspected this or at least to start here. rose28357 recently pointed me to this conversation regarding possible stability issues. Settings which I use (for a long time) are the same as in this patch. Question is - what are the safe limits to play with and has anyone already done anything on this?
Debian and Ubuntu images with kernel 3.4.110, 4.3.3, 4.4
http://www.armbian.com

Offline slovenia

  • Hero Member
  • *****
  • Posts: 511
  • Karma: +47/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #23 on: June 26, 2014, 01:38:50 pm »
Just put 1.6 on a SD card.

The kernel is 3.4.75-sun7i+

So far I must have copied around 10GB of data over rsync/ssh and so far NO CORRUPTION. Will check back once its finished.

Thank you for your effort with the CTDebian. Let me know if I can do any more testing.

On a side note: Should this thread be continued in OS section? It's not a hardware issue as it turned out.

Thanks for your input. It's very helpful! Linux is common work by definition and practise  :P

EDIT:
This is configuration (script.bin) from that old Debian 3.4.61+ reported as "working"
Use my latest image and use settings from attachment. Uncompress them to /boot and reboot.
« Last Edit: June 26, 2014, 02:04:57 pm by slovenia »
Debian and Ubuntu images with kernel 3.4.110, 4.3.3, 4.4
http://www.armbian.com

Offline foef

  • Newbie
  • *
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #24 on: June 26, 2014, 05:40:04 pm »
Rsync finished.

Code: [Select]
sent 412399 bytes  received 102268834796 bytes  7595473.07 bytes/sec
No corruption.

I will try the script.bin this weekend. Just to avoid confusion. You talk about kernel 3.4.61+ scripts, but the 1.6 version of CTDebian that I now tried is running 3.4.75.

Offline D_NRW

  • Jr. Member
  • **
  • Posts: 65
  • Karma: +3/-0
    • View Profile
    • Dan-And
Re: cubietruck NIC corrupting data?
« Reply #25 on: June 26, 2014, 06:50:18 pm »
@Slovenia

Regarding the voltage values of that conversation. I switched to this voltages a long time ago as my boards are all running on full load 24/7. As mentioned, I had freezed quite often with some boards while others had never any issues. Since the voltage adaption they all work very stable.

Good luck

Daniel

Offline slovenia

  • Hero Member
  • *****
  • Posts: 511
  • Karma: +47/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #26 on: June 27, 2014, 12:55:17 am »
Rsync finished.

Code: [Select]
sent 412399 bytes  received 102268834796 bytes  7595473.07 bytes/sec
No corruption.

I will try the script.bin this weekend. Just to avoid confusion. You talk about kernel 3.4.61+ scripts, but the 1.6 version of CTDebian that I now tried is running 3.4.75.

I had extracted this script from this one:
http://www.cubieforums.com/index.php/topic,1087.0.html
Debian and Ubuntu images with kernel 3.4.110, 4.3.3, 4.4
http://www.armbian.com

Offline foef

  • Newbie
  • *
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #27 on: June 27, 2014, 07:50:48 pm »
I used CTDebian 2.1 vga and extracted the scripts to /boot as instructed (I noticed after copying that you released a 2.2 version).
Code: [Select]
root@cubie:~# uname -a
Linux cubie 3.4.93-sun7i+ #1 SMP PREEMPT Fri Jun 13 17:45:46 CEST 2014 armv7l GNU/Linux
Result:
Code: [Select]
sent 412399 bytes  received 102268834796 bytes  6786505.67 bytes/sec
So NO CORRUPTION.

On a side note:
The LED's on the board are not turned off after booting. But I guess that's due to the replaced scripts.

Offline slovenia

  • Hero Member
  • *****
  • Posts: 511
  • Karma: +47/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #28 on: June 30, 2014, 09:39:37 am »
I forgot the most obvious reason. :P SoC is slightly over-clocked. What about using the default script-bins and down-clocking to its default speed? 960Mhz :)

edit /etc/inid.d/cpufrequtils

change
MAX_SPEED="1200000"
to
MAX_SPEED="960000"

service restart cpufrequtils
Debian and Ubuntu images with kernel 3.4.110, 4.3.3, 4.4
http://www.armbian.com

Offline ssvb

  • Jr. Member
  • **
  • Posts: 72
  • Karma: +5/-0
    • View Profile
Re: cubietruck NIC corrupting data?
« Reply #29 on: June 30, 2014, 11:06:11 am »
I forgot the most obvious reason. :P SoC is slightly over-clocked.
1.2GHz is not a slight overclock. It is far beyond normal operational limits of A10/A20 and is almost guaranteed to fail on certain heavy workloads. You can try the tests from the following thread for the start: https://www.mail-archive.com/linux-sunxi@googlegroups.com/msg04343.html

Yes, it is possible to improve reliability by increasing the core voltage, but then you have to deal with major overheating problems on heavy workloads (say hello to large heatsinks and active cooling if you want to resolve this): https://www.mail-archive.com/linux-sunxi@googlegroups.com/msg01029.html

To sum it up, you get some really serious reliability problems for merely 20% of potential performance improvement.