Flole

  • Content Count

    32
  • Joined

  • Last visited

Everything posted by Flole

  1. It does not work in the legacy branch, it just used to work on 4.13.x before I upgraded to focal (I think I was on bionic before but I need to check that again). I tried the legacy branch as I was hoping that it could be better, but unfortunately it isn't.
  2. Sure, I had to remove some sensitive information like IPv6 Addresses and NFS Paths though.
  3. This is what happened right before a crash, looks like it was adjusting the frequency quite often at that time. I would assume that many frequency adjustments are the cause of it and also that is the only thing I changed and since then it's running super stable. Not even my selfmade power supply that provides 5.25V 3A through the dc jack made a change, I still had the same crashes while the voltage that comes out of the USB ports is super stable (checked with an oscilloscope). Only after switching to the performance governor it started to run stable (at least until now, but's thats already lon
  4. I think I found the reason for my crashes: I used the ondemand power governor and apparently that caused the issues. Maybe the voltage regulator was set to an invalid level or something. Anyways, since I disabled it and used performance I now have had no crashes, that's an uptime of 8 days now. My absolute record was 14 days so I guess the next weeks will show if that was really the issue or not.
  5. I am running Armbian Focal with Linux 5.4.43-sunxi64 (and now downgraded to 4.19.125-sunxi64) on my Orange Pi PC 2. I use motion software to provide a "18ec:5555 Arkmicro Technologies Inc. USB2.0 PC CAMERA" to the network. I also use pjsip to provide SIP functionality for the same device as audio input. As soon as I start pjsip for some reason I get a very high load average until the kernel detectets stalled CPUs and finally the entire device crashes. This worked fine in a previous version and started after I upgraded to focal. I did a kernel backtrace and this is what I got: [ 401.002517
  6. That indeed disabled those messages. I have a few more, are those normal and necessary aswell or can I disable something to get rid of them:
  7. I assume there is no way to just disable the GPU completely? I don't need it at all, so if there is a way to disable it I would give that a try.
  8. Is anybody else experiencing stability issues? I have replaced the power supply now and double-checked with an oscilloscope to make sure the voltage is stable even under load. I have stable 5.25V at the USB Ports. I am using an USB HDD as rootfs, is anybody else using this with the system running stable? There are quite some regulator entries in the dmesg, but I think those are normal? I tried to enable the watchdog but that doesn't fix the lockups. My HDDs LED goes off when that lockup happens, the Ethernet LEDs stay on but it doesn't respond anymore at all, just as if the CPU
  9. But it is not "unsafe" to run it in this configuration, right? The regulators are all set now and there shouldn't be any need to change voltages now. Especially they shouldn't be set to an unsafe voltage, right? On the next reboot it'll become active again anyways but since last time I tried a reboot after unloading I got a complete lockup I would prefer to keep it running for 2 more days until I'm physically there again.
  10. I tried to unload i2c_mv64xxx using modprobe -r command and in dmesg I got [41723.377022] vcc-5v: Underflow of regulator enable count[41723.377036] vcc-5v: Underflow of regulator enable count[41723.377209] ------------[ cut here ]------------[41723.377223] WARNING: CPU: 1 PID: 23070 at drivers/regulator/core.c:5262 regulator_unregister+0xd0/0xd8[41723.377225] Modules linked in: nf_log_ipv4 nf_log_common xt_LOG xt_mac xt_conntrack iptable_filter xt_MASQUERADE xt_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 tun bridge zram sun4i_i2s snd_soc_simple_card sunxi_cedrus(C) snd
  11. My Power Supply has a micro usb plug attached, so if I want to use the dc jack I would have to remove that one first Every connector adds additional resistance so I try to avoid it whenever it's possible.
  12. I think this board has quite some issues though, even when I go in with 5V on the Micro USB it's not enough to power a HDD on the USB Ports (and I'm not the only one with that issue), so I was wondering if this might be another issue this board has.... I guess I need a 5.5V Power Supply to account for whatever losses happen on the board. Is it better to go in through the DC Jack? I read about issues with that some time ago aswell and as I would have to cut my USB Cable I want to be absolutely sure that it's better before I try it.
  13. As you can read (some posts) above I am using 2 Power supplies and the voltage should be stable at the board. I'll try to run a stresstest though once I rebooted the board to see if that could be the issue. Just to confirm: For you this board is running stable?
  14. Unfortunately my Orange Pi 3 is still very unstable, even with the latest version. I get a maximum uptime of 4 days, and sometimes like now it won't even reboot automatically when it crashes. I'll try to see if it's possible to setup kdump tomorrow to see if this is caused by a panic (and what causes it) or the CPU simply goes into reset. I am running Armbian from a USB Drive, I need to check if maybe USB initialization fails and that causes the reboot to fail. Has anybody else experienced something like this?
  15. The air should be moving upwards by itself but anyways, now that I know that this is a known problem I prepared a 40mm fan with a USB plug that I can just mount on my enclosure and it will blow straight onto the heatsink. That should be enough cooling to keep it under 80°C. Another thing I noticed: I have a 5.2V 3A Power supply connected to the Micro USB connector. On the USB3 Ports I have a HDD connected and that HDD just gets 4.7V, so either some rails are a little too thin on the board or the Micro USB connector adds quite some resistance. Has someone seen that before? Is it bet
  16. 1.6 is not low enough to keep it under 80°C, 1.32 keeps it barely on or below 80°C, that's not with all cores completely used though, I'm at about 50% on 3 cores and 90% on one core.
  17. Is anybody else seeing the issue that the CPU is constantly at around 80°C causing the CPU to be throttled down to 1.08Ghz maximum speed? I added a heatsink to the H6 CPU and switched the governor to conservative but that didn't really help.
  18. Unfortunately my SD cards are for some reason wearing out extremely fast, so I prefer other methods. Also my CPU temperature is constantly around 80-85°C. My board is one of the first ones by the way. Bought shortly after they launched it. The new kernel seems to have broken CPU frequency scaling, it's running now on 0Mhz according to htop and the CPU is on the limit..... # cpufreq-info -ecpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009Report errors and bugs to cpufreq@vger.kernel.org, please.analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum trans
  19. In order to solve my issues with the lockup I tried to enable the watchdog but I found the board locked up again this morning. Either the reboot is not working cleanly or the watchdog is not resetting the board correctly or my USB HDD is not initialized properly. I upgraded to the new kernel now (5.4) and hope that it's more stable with this one. I'll report back on the next lockup. As I'm facing those lockups on an almost daily basis I thought about adding a timer to the power supply that cuts the power once per day to do a clean restart. That would definitely work but if there are other wa
  20. Unfortunately I am suffering from stability issues in this (unstable) build aswell. I am booting from a USB HDD and I have connected the entire thing to a 5V 3A power supply that also really delivers the 3A (actually verified that). Also it's slightly above 5V at the Micro USB Plug so I think the power should be enough. Could this be related to the issue mentioned on the page before (increased voltage to the CPU)? How are chances that 5.4 kernel will be more stable for me? Is there anything I can do now to make it more reliable or at least to have it automatically reboot? I have set panic=1 al
  21. GND is actually pin 4 of a USB connector. The numbering is also not reversed cause then D+ and D- wouldn't be correct anymore. So that's just wrong in the schematics.
  22. Not only the block diagram is wrong but the Power Tree aswell (which is somewhat important). And Page 10 clearly says that the VCC-5V is connected to the GND Pin of the USB, which is also not correct..... I don't really trust these schematics anymore.... Just tried this aswell, and indeed it's a lot better. Weird..... Anyways, there doesn't seem to be some kind of regulator involved so it's all good now!
  23. Nope, it clearly says Orange_PI-3 on it, downloaded from the Google Drive. Dated at November 26th 2018.
  24. The schematic also states that VCC-5V is connected to GND of the USB Connector, thats also not the case here so I am very careful about believing that. Also in the powertree and the Block diagram it has a 12V in connected to a DC/DC Converter. Looking at DCIN that DC/DC regulator is gone. So I am really careful when it comes to reading this schematics....
  25. It's indeed a little low on mine aswell, using the manufacturer's OS it is higher. I think there is just something set wrong on a voltage regulator? The schematics also seem a little off when it comes to the USB Port: GND is connected to the VCC Pin of the Port and vice versa. I was looking for a voltage regulator there but other than the AXP805 I didn't find one. I looked at the AXP805 Datasheet to see if it could be this one, but as it can't output 5V this can't be it. This leaves 2 options: Either it's connected directly to the 5V Input, so does the armbian OS use that much more power than