Hi,

 

after pure installation Armbian_4.5_Lamobo-r1_Debian_wheezy_3.4.109.zip, the log is full of GMAC messages:

[43099.518189] GMAC TX status: VLAN frame
[43099.521192] GMAC TX status: VLAN frame
[43099.524646] GMAC TX status: VLAN frame
[43111.775611] GMAC TX status: VLAN frame
[43112.963963] GMAC TX status: VLAN frame
[43112.980989] GMAC TX status: VLAN frame
[43112.986370] GMAC TX status: VLAN frame
[43112.989681] GMAC TX status: VLAN frame
[43112.992410] GMAC TX status: VLAN frame
[43112.996184] GMAC TX status: VLAN frame
[43113.002038] GMAC TX status: VLAN frame
[43113.973308] GMAC TX status: VLAN frame
[43113.976078] GMAC TX status: VLAN frame
[43114.143583] GMAC TX status: VLAN frame
[43114.487643] GMAC TX status: VLAN frame
[43114.700444] GMAC TX status: VLAN frame
[43115.015755] GMAC TX status: VLAN frame
[43115.188027] GMAC TX status: VLAN frame

Bug? Or I configured something wrong?

 

PM

 

Yes, it's a bug ... I'll fix it asap. 

BTW.

 

There is a temporal solution by switching to alternative A20 kernel.

 

apt-get install linux-image-banana

 

...  but that kernel will not update anymore in the future so you will need later to come back to

 

linux-image-sun7i

The question is, if the device will overlive till evening. System is running on SD card and HD is only for data. Is the linux log so clever, that when there is no space for logging will flush logfiles?

 

BTW.

 

There is a temporal solution by switching to alternative A20 kernel.

 

apt-get install linux-image-banana

 

...  but that kernel will not update anymore in the future so you will need later to come back to

 

linux-image-sun7i

No, running out of space is not a good idea. Logs are archiving / compressing so should not happen so soon.

Ok, I will let it run as it is. Thanks.

 

No, running out of space is not a good idea. Logs are archiving / compressing so should not happen so soon.

https://github.com/igorpecovnik/lib/commit/0b4f6424b60b00cf088810e7f8387552ad9ae61d

 

Sources are fixed, kernel recompilation and repository update will follow asap.

apt-get update & upgrade will solve everything. 

 

It takes some time that all servers are populated so files might not yet be available in next minutes

Hello - I am having this problem as well, but update & upgrade have already been done - as far as I can tell, I'm on the very latest.   I did upgrade to jessie - did the fix make it into that branch?