5 5
martinayotte

H6 Famous Reboot problem

Recommended Posts

Errr from " H6 famous reboot problem " it seems just the orangepi's are affected (opioneplus and opilite2, opi3 )?

reiniting eth0 did work from cold boot ( of course ):

root@orangepioneplus:~# ip link set dev eth0 down && ip link set dev eth0 up


Apr 11 05:05:48 localhost kernel: [  425.696366] dwmac-sun8i 5020000.ethernet eth0: Link is Down
Apr 11 05:05:48 localhost kernel: [  425.705231] RTL8211E Gigabit Ethernet stmmac-0:01: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
Apr 11 05:05:48 localhost kernel: [  425.707898] dwmac-sun8i 5020000.ethernet eth0: No Safety Features support found
Apr 11 05:05:48 localhost kernel: [  425.707918] dwmac-sun8i 5020000.ethernet eth0: No MAC Management Counters available
Apr 11 05:05:48 localhost kernel: [  425.707930] dwmac-sun8i 5020000.ethernet eth0: PTP not supported by HW
Apr 11 05:05:53 localhost kernel: [  430.819302] dwmac-sun8i 5020000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx

so after that I thought to be fresh and smart but naye: no joy,

bringing in a WiFi dongle should help possibly to get more logs at this stage ... ...

root@orangepioneplus:~# ip link set dev eth0 down && reboot

 

Share this post


Link to post
Share on other sites
Just now, dolphs said:

Errr from " H6 famous reboot problem " it seems just the orangepi's are affected (opioneplus and opilite2, opi3 )?

reiniting eth0 did work from cold boot ( of course ):

 

 

Same error dwmac-sun8i 5020000.ethernet eth0 and very unstable last build, but reboot work:D

Back build.

Share this post


Link to post
Share on other sites
1 hour ago, greg798 said:

Same error dwmac-sun8i 5020000.ethernet eth0 and very unstable last build, but reboot work:D

Back build.

which means, once I will return home I can rebuild image and give it another shot on mu opioneplus devices?

cheers

Share this post


Link to post
Share on other sites
13 minutes ago, dolphs said:

which means, once I will return home I can rebuild image and give it another shot on mu opioneplus devices?

 cheers

 

It does not depend on me,  i am simple  user and have problem eth0 board opi3 

any monipulations with lan network dev in last Armbian bionic 190409 img beta.

Im back to img Armbian bionic 190407 and unplug power.

Share this post


Link to post
Share on other sites
6 hours ago, greg798 said:

Im back to img Armbian bionic 190407 and unplug power.

You don't need to go back to 190407 to be able to unplug the power ... :P

Share this post


Link to post
Share on other sites
2 hours ago, martinayotte said:

You don't need to go back to 190407 to be able to unplug the power ... :P

I'm happy

Install Armbian bionic 190411 + xorg + xsever + lxde + lightdm = boot to window lightdm and have not worked my opi3 usb(2.0,3.0) mouse, keyboard:D

Maybe Armbian alpha? 

Share this post


Link to post
Share on other sites

I am using lan to connect to opi3  and I cant see any problems with reboot and network after that, what is quite strange thing. compiled code with armbian build script docker option and booting from sd card.

 

 ssh orangepi3

Welcome to ARMBIAN 5.78 user-built Debian GNU/Linux 9 (stretch) 5.0.7-sunxi64
System load:   2.20 0.68 0.24   Up time:       0 min
Memory usage:  12 % of 1997MB   IP:            192.168.220.135
CPU temp:      41°C
Usage of /:    4% of 30G

Last login: Thu Apr 11 19:37:32 2019 from 192.168.220.1

 

 

while (sleep 60);do ssh orangepi3 'uptime;reboot';done
 19:42:13 up 4 min,  0 users,  load average: 1.05, 0.85, 0.39
Connection to orangepi3 closed by remote host.
 19:42:46 up 0 min,  0 users,  load average: 2.60, 0.66, 0.22
Connection to orangepi3 closed by remote host.
 19:43:48 up 0 min,  0 users,  load average: 2.29, 0.56, 0.19
Connection to orangepi3 closed by remote host.
 19:44:39 up 0 min,  0 users,  load average: 1.25, 0.29, 0.10
Connection to orangepi3 closed by remote host.
 19:45:39 up 0 min,  0 users,  load average: 2.11, 0.51, 0.17
Connection to orangepi3 closed by remote host.

 

Share this post


Link to post
Share on other sites
14 minutes ago, kexec said:

am using lan to connect to opi3  and I cant see any problems with reboot and network after that

When did you compile your image ? Is it using the newer U-Boot v2019.04 ?

Maybe the issue was only in v2019.01 used few days ago ... I will recompile ...

Share this post


Link to post
Share on other sites
5 minutes ago, martinayotte said:

When did you compile your image ? Is it using the newer U-Boot v2019.04 ?

Maybe the issue was only in v2019.01 used few days ago ... I will recompile ...

i just downloaded https://dl.armbian.com/orangepi3/nightly/Armbian_5.78.190411_Orangepi3_Ubuntu_bionic_dev_5.0.7.7z and done same test and as I can see reboot also works without loosing eth0.

 

 ssh orangepi3
Welcome to ARMBIAN 5.78.190411 nightly Ubuntu 18.04.2 LTS 5.0.7-sunxi64
System load:   0.87 0.44 0.17   Up time:       2 min
Memory usage:  5 % of 1997MB    IP:            192.168.220.135
CPU temp:      39°C
Usage of /:    2% of 58G

Last login: Thu Apr 11 20:02:18 2019 from 192.168.220.1

root@orangepi3:~# logout
Connection to orangepi3 closed.
[root@slowlaris ~]# while (sleep 60);do ssh orangepi3 'uptime;reboot';done
a 20:03:58 up 3 min,  0 users,  load average: 0.27, 0.35, 0.16
Connection to orangepi3 closed by remote host.
 20:04:58 up 0 min,  0 users,  load average: 1.08, 0.33, 0.12
Connection to orangepi3 closed by remote host.
 20:05:59 up 0 min,  0 users,  load average: 0.51, 0.19, 0.07
Connection to orangepi3 closed by remote host.
 20:06:57 up 0 min,  0 users,  load average: 1.09, 0.31, 0.11
Connection to orangepi3 closed by remote host.
 20:08:01 up 0 min,  0 users,  load average: 0.43, 0.16, 0.06
Connection to orangepi3 closed by remote host.
 20:09:02 up 0 min,  0 users,  load average: 1.12, 0.33, 0.12
Connection to orangepi3 closed by remote host.

Share this post


Link to post
Share on other sites

on emmc   U-Boot 2014.07 (Mar 14 2019 - 16:09:23) Allwinner Technology

on sd card U-Boot 2019.01-armbian (Apr 11 2019 - 11:38:28 +0200) Allwinner Technology

 

maybe u-boot works from emmc if present? i guess everyone who has reboot issue is using emmc boot ?

Share this post


Link to post
Share on other sites
4 minutes ago, kexec said:

i guess everyone who has reboot issue is using emmc boot ?

No, because the issue is also seen on OPiOnePlus which doesn't have any eMMC.

Share this post


Link to post
Share on other sites
1 hour ago, martinayotte said:

When did you compile your image ? Is it using the newer U-Boot v2019.04 ?

Maybe the issue was only in v2019.01 used few days ago ... I will recompile ...

Wow !!! With the U-Boot v2019.04, it seems the issue is magically gone !!! :o

I've just tested with OPi3 ... I will do a fresh build for OPiOnePlus and OPiLite2 to make sure ...

 

EDIT : No, the H6 build still using v2019.01, so it must be something else, maybe @megi branch got additional fix ?

EDIT2 : No, Megous 5.0.y branch didn't change since 6 days ... I feel like chasing a ghost ! :angry:

EDIT3 : I'm really chasing a ghost here ! The trouble is back again after renabling WiFi, then disabling WiFi, it stays in trouble... :wacko:

Share this post


Link to post
Share on other sites

Last update fix reboot yes, but im have error work usb port after boot window manager (lxde) 

host kernel: [    1.775927] sun50i-de2-bus 1000000.display-engine: Error couldn't map SRAM to device
Apr 11 22:31:39 localhost kernel: [    1.776339] sun4i-usb-phy 5100400.phy: Couldn't request ID GPIO
Apr 11 22:31:39 localhost kernel: [    1.776581] sun50i-usb3-phy 5210000.phy: failed to get phy clock

Maybe lxde problem?

Share this post


Link to post
Share on other sites
57 minutes ago, greg798 said:

Maybe lxde problem?

No ! As you can see by timestamp, it is early at boot up !

But those errors should not prevent you from using USB, at least in USB2 mode ...

Share this post


Link to post
Share on other sites
1 hour ago, martinayotte said:

EDIT3 : I'm really chasing a ghost here ! The trouble is back again after renabling WiFi, then disabling WiFi, it stays in trouble... :wacko:

I've finally "unmasked" the ghost !!! :P

 

Since I'm an old fashion guy, I'm usually defining my network settings in /etc/network/interfaces, for both WiFi and Wired...

As soon as I've commented out the "allow-hotplug eth0" and "iface eth0 inet dhcp" and leave NetworkManager managing it, after cold boot, of course, the wired network was working fine on every reboot ! ;)

 

It still amazed me to figure out that, because it is really like we opened a pandara box, why old /etc/init.d/networking could leave something dirty in memory that make the following errors after a warm reboot :

[    4.388263] platform 5020000.ethernet eth0: Could not attach to PHY
[    4.394739] platform 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

Maybe @froezus has an idea ?

 

In the mean time, don't be a old fashion guy like me, leave NetworkManager do things properly ...

 

EDIT : BTW, when I've said earlier the PineH64 doesn't behave like OPis for this wired networking issue, it is still true, because if I've the settings in /etc/network/interfaces, it still have proper networking after warm reboot ... So, still pandora box ! :(

Share this post


Link to post
Share on other sites

After reading these promising results I fired up my enigines and compiled a new dev image " Armbian_5.78_Orangepioneplus_Debian_stretch_dev_5.0.7 " .

 

As I am still waiting the SDCARD to be prepared I am replying to these 

4 hours ago, martinayotte said:

In the mean time, don't be a old fashion guy like me, leave NetworkManager do things properly ... 

this is quite " funny " as that makes two of us, I actually disabled NetworkManager as I thought this was the issue and besides that I am used to editing in to " interfaces "...

 

4 hours ago, martinayotte said:

Maybe @froezus has an idea ?

is this our guy who silently fixed stuff committing/updating a patch? if so KUDO's

 

now it is time to insert my freshly built sdcard image in to the OpiOnePlus...

setting root password, do absolutely nothing else than creating another login account and after that executing a " reboot " ( shutdown -r now ) on the command line

 

It looks like the shutdown takes longer than before, eg red light goes off a little later, however I can be mistaken as it is like 05.15am here

It all looked promising till the moment I realise the result improved somewhat having a red light back and an orange blining LAN light, with sometimes green popping up , BUT:

 

unable to access remotely ( SSH )...

Thus .... back to powercycling device ...

perhaps the newer U-Boot v2019.04 might be of help after all as currently it is still 01 ...

 

Almost there, but not just yet as @martinayotte

4 hours ago, martinayotte said:

I've finally "unmasked" the ghost !!!

which means the ghost happily resides now in my machine ... 

cheers :-), we're close ... let's stay positive and off to bed now ...  ...

Share this post


Link to post
Share on other sites
7 hours ago, martinayotte said:

No ! As you can see by timestamp, it is early at boot up !

But those errors should not prevent you from using USB, at least in USB2 mode ...

 

Im pointed out, usb2.0, 3.0 does not work (im see power my usb devises, but after boot windows manager not data work).

This error after your fix reboot problem.

I think all this concerns kernel drivers and power supply system of board allwinner h6

Share this post


Link to post
Share on other sites
10 minutes ago, greg798 said:

This error after your fix reboot problem. 

attempt to fix, as it concerns me at least (OpiOnePlus) ...

will check USB tonight.

Share this post


Link to post
Share on other sites

@martinayotte  I also don't use network manager. And I think it's more related to the timing here. Maybe the regulator as time to discharge because network manager is slower or maybe it makes the things more properly.

 

If you have an oscilloscope checking the phy reg should the easiest way to solve this. 

 

Else maybe you can try 

Ifdown eth0; sleep 2; reboot ? 

 

I'm not familiar with the kernel and how the regulator are shutdown with network.

 

Is it possible to compile Ethernet phy and stack as a module and try to rmmod / modprobe and see if you trig the same issue ?

 

Clement 

 

Share this post


Link to post
Share on other sites
23 minutes ago, froezus said:

I also don't use network manager. And I think it's more related to the timing here. Maybe the regulator as time to discharge because network manager is slower or maybe it makes the things more properly.

Also this is actually what I kind of tried the other day, unseccesful reboot attempt: " ip link set eth0 down && rmmod realtek && reboot ".

On my TODO for tonight to play a little more with this also will try disabling NetworkManager and use old school debian school " interfaces " file including proper hardware MAC

will report back when I can, cheers

Share this post


Link to post
Share on other sites

@martinayotte I only work on Opi3 support on opi3-5.1 branch. So all the most recent changes are there. For my u-boot I only work on v2019.04-rc*.

 

Share this post


Link to post
Share on other sites
3 hours ago, dolphs said:

unseccesful reboot attempt:

The ghost is laughing on us : right, all behaviour seen yesterday on OPi3 doesn't work on OPiOnePlus.

3 hours ago, froezus said:

If you have an oscilloscope checking the phy reg should the easiest way to solve this.

I have one, but not digital, it is an old CRT one. I will try, but I'm not even sure what to check, perhaps VCC33_EPHY, GMAC_EN ?

Share this post


Link to post
Share on other sites
2 hours ago, megi said:

I only work on Opi3 support on opi3-5.1 branch. So all the most recent changes are there. For my u-boot I only work on v2019.04-rc*.

it is interesting 5.1 is being worked on already, very nice.

Also noticed from Linux mainlining effort in coming 5.2, supposedly in May, the Opi3 is being supported : nice to know ...

 

 

2 hours ago, froezus said:

if you try to modprobe again the driver without the reboot does it works ?

 

built and flashed latest dev image just now and tried following:

ip link set eth0 down 
rmmod realtek 
insmod /lib/modules/5.0.7-sunxi64/kernel/drivers/net/phy/realtek.ko
ip link set eth0 up


[  282.600634] dwmac-sun8i 5020000.ethernet eth0: Link is Down
[  282.649231] RTL8211E Gigabit Ethernet stmmac-0:01: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
[  282.651961] dwmac-sun8i 5020000.ethernet eth0: No Safety Features support found
[  282.651981] dwmac-sun8i 5020000.ethernet eth0: No MAC Management Counters available
[  282.651993] dwmac-sun8i 5020000.ethernet eth0: PTP not supported by HW
[  287.776787] dwmac-sun8i 5020000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[  287.776816] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

this is a BINGO, thus so far so good.

However adding " reboot " after the " rmmod " command won't bring back the device, a powercycle is needed also added "  sleep 5 ".

This has been tested with NetworkManager , later tongight will disable and go " old school " interfaces way.

will report back when I can.

cheers

 

Share this post


Link to post
Share on other sites

You need also to rmmod the MAC module (something like dwmac-sun8i) it's him who manage the phy-supply.

 

rmmod phy && rmmod mac
modprobe mac (should also modprobe the phy)

Share this post


Link to post
Share on other sites
4 hours ago, megi said:

I only work on Opi3 support on opi3-5.1 branch.

I've done a 5.1.0-rc4 build from your branch, but unfortunately, it doesn't fix the issue, at least with OPiOnePlus ... :(

Share this post


Link to post
Share on other sites
5 5