Jump to content

Boot and dmesg errors


Perier

Recommended Posts

Hello community!

 

I use in my project "Orange Pi Zero Plus (Alwinner H5 - 512mb)". When using the image downloaded from the official site (https://www.armbian.com/orange-pi-zero-plus/ - Armbian Stretch
mainline kernel 4.14.y), I get a set of errors when I boot and when I use the working OS, which I'm straining. The same mistakes I get if I build the kernel and the OS myself through "build" (linux-sunxi64-next).

 

My equipment:

  • Memory: SanDisk Ultra microSDHC Class 10 UHS-I 48MB/s 16GB
  • Power supply:  Raspberry Pi 3b+ Power Adapter (STONTRONICS) - 5.1V @ 2.5A

 

Boot: full log - https://pastebin.com/M9g6ipUp

Loading Environment from EXT4 ... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0: 1 **
Failed (-5)

 

dmesg: full log - https://pastebin.com/GyeUTQem

[0.668711] sun4i-usb-phy 1c19400.phy: Could not request ID GPIO
[0.670578] sun8i-h3-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver
[0.674095] sun50i-h5-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[0.680561] NOHZ: local_softirq_pending 80
[0.703353] cacheinfo: Unable to detect cache hierarchy for CPU 0
[0.776991] core: _opp_supported_by_regulators: OPP minuV: 1120000 maxuV: 1300000, not supported by regulator
[0.776999] cpu cpu0: _opp_add: OPP not supported by regulators (912000000)
[0.777077] core: _opp_supported_by_regulators: OPP minuV: 1160000 maxuV: 1300000, not supported by regulator
[0.777084] cpu cpu0: _opp_add: OPP not supported by regulators (960000000)
[0.777134] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1300000, not supported by regulator
[0.777140] cpu cpu0: _opp_add: OPP not supported by regulators (1008000000)
[0.777218] core: _opp_supported_by_regulators: OPP minuV: 1240000 maxuV: 1300000, not supported by regulator
[0.777224] cpu cpu0: _opp_add: OPP not supported by regulators (1056000000)
[0.777274] core: _opp_supported_by_regulators: OPP minuV: 1260000 maxuV: 1300000, not supported by regulator
[0.777280] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000)
[0.777357] core: _opp_supported_by_regulators: OPP minuV: 1300000 maxuV: 1300000, not supported by regulator
[0.777363] cpu cpu0: _opp_add: OPP is not supported by regulators (1152000000)
[0.777627] thermal thermal_zone0: binding zone cpu-thermal with cdev thermal-cpufreq-0 failed: -22
[0.862337] mmc0: host does not support reading read-only switch, assuming write-enable
[0.862561] NOHZ: local_softirq_pending 80
[1.265962] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found using dummy regulator
[11.340617] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit = 600, errors = remount-ro
[11.473725] 29
[11.473733] 81
[11.473738] 03
[11.473740] CC
[11.473742] 00
[11.473745] 00
[11.473747] 50
[11.473749] 00
[11.473752] 00
[11.473754] 00
[11.473756] 04
[11.473758] CC
[11.473760] 0A
[11.473762] 0C
[11.473765] 00
[11.473769] 00
[11.473770] FF
[11.473772] FF
[11.473775] FF
...
[11.474899] FF
[11.474901] FF
[11.474904] FF
[11.564425] g_serial gadget: Gadget Serial v2.4

 

It is difficult for me to estimate how much these errors are critical for stable use of the OS, since I am not an expert in this field. Ready for tight interaction to eliminate these problems, if they are.

 

Thank you for your attention and your answers - any information on this issue will be useful.

Link to comment
Share on other sites

21 hours ago, Evgeny said:

up

bumping is normally the best way to get a warning... 

 

On 10/1/2018 at 11:39 AM, Evgeny said:

It is difficult for me to estimate how much these errors are critical for stable use of the OS,

that's why h5 is marked testing.. nobody knows..

 

On 10/1/2018 at 11:39 AM, Evgeny said:

[0.862337] mmc0: host does not support reading read-only switch, assuming write-enable

nothing to care about... that's normal.. 

 

On 10/1/2018 at 11:39 AM, Evgeny said:

[0.776991] core: _opp_supported_by_regulators: OPP minuV: 1120000 maxuV: 1300000, not supported by regulator
[0.776999] cpu cpu0: _opp_add: OPP not supported by regulators (912000000)
[0.777077] core: _opp_supported_by_regulators: OPP minuV: 1160000 maxuV: 1300000, not supported by regulator
[0.777084] cpu cpu0: _opp_add: OPP not supported by regulators (960000000)
[0.777134] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1300000, not supported by regulator
[0.777140] cpu cpu0: _opp_add: OPP not supported by regulators (1008000000)
[0.777218] core: _opp_supported_by_regulators: OPP minuV: 1240000 maxuV: 1300000, not supported by regulator
[0.777224] cpu cpu0: _opp_add: OPP not supported by regulators (1056000000)
[0.777274] core: _opp_supported_by_regulators: OPP minuV: 1260000 maxuV: 1300000, not supported by regulator
[0.777280] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000)
[0.777357] core: _opp_supported_by_regulators: OPP minuV: 1300000 maxuV: 1300000, not supported by regulator
[0.777363] cpu cpu0: _opp_add: OPP is not supported by regulators (1152000000)
[0.777627] thermal thermal_zone0: binding zone cpu-thermal with cdev thermal-cpufreq-0 failed: -22

 

probably related to this one:

no idea, I don't follow H5 development close enough....

 

search.jpg.5549006196a9e503c95455e89ff022a5.jpg

and a lot of reading might give you a clue what's and how stable things are working on h5 for *random usecase*.. H5 and H6 are in development phase. 

 

@Igor I think our download-page here is 'part of the problem'. 

1930064568_Screenshotfrom2018-10-1715-33-59.thumb.png.298692739ace4c931760e4b16c72679d.png

 

I suggest that we mark those images as wip not supported. The only kernel we provide is in experimental or at least testing phase.. The exceptions from supported are higher than WIP.. 

Link to comment
Share on other sites

 

2 hours ago, chwe said:

nobody knows..


Knows, but it is expensive and virtually impossible to answer all questions and explain what those specifics kernel "errors" means. Over and over again. 

 

H5/A64 section is deliberately left out from forum support section since at least support remains limited. Mostly because of A64 which is staying behind H5.

 

14 hours ago, chwe said:

The only kernel we provide is in experimental or at least testing phase..

 

SUPPORTED devices are tested and they work apart from known issues and missing features.
 

Which is true.
 

Known issues info adds an information that there might be unknown issues. WIP goes mainly for boards based on new chips, where we are in the process of knowing things (RK3399) or where we know vital things are broken (A64) and needs longer time to fix. It's complicated.

This support is as is. "we" are no obligated to answer on anything.

Link to comment
Share on other sites

If Gozard anyway has a look into the DL page, we may want the Testing flag more obvious. Something like if kernel=testing then second supporting flag color = orange.  Which is then in conflict with WIP I know.. For 'us' dealing with support since long time it's obvious It may not be as obvious for a first time visitor. :) 

Link to comment
Share on other sites

1 hour ago, chwe said:

If Gozard anyway has a look


Add your ideas to the list "Download UX". Then it might not get lost. 
https://forum.armbian.com/topic/6281-board-support-general-discussion-project-aims/?do=findComment&comment=64049

 

 

On 10/1/2018 at 11:39 AM, Evgeny said:

It is difficult for me to estimate how much these errors are critical for stable use of the OS, since I am not an expert in this field. Ready for tight interaction to eliminate these problems, if they are.


Safe to ignore. They are mostly not even errors.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines