First step would be for us to reproduce. I somehow feel like this is not a hardware issue where interrupts are blocked. Because normally this only happens when there is still a load for instance Network but you say you stop scanning and it is there minutes later. Strange.
New kernel? 4.9.177?
Latest nightly yes. It still might be that it was caused by a crash of the sundtek driver (mediasrv) which happens from time to time for coreelec.
Iām having an odd issue trying to connect my PS4 controller via Bluetooth. It seems to pair fine, I can see it listed with the MAC id and everything, but every time I actually connect it, CoreELEC freezes and reboots its self. Iāve been searching the logs, and canāt seem to really find any errors besides these lines. There may be some debug info that I donāt recognize.
2019-06-01 08:34:16.392 T:3642749808 ERROR: ## CoreELEC Addon ## bluetooth::dbus_error_handler ## ERROR: (Input/output error)
2019-06-01 08:34:16.392 T:3642749808 ERROR: None
Did you ever fix your usb issues?
Other BT devices (headphones etc) have issues too?
Partially by using the micro-USB port. The discussion is still ongoing here:
https://forum.odroid.com/viewtopic.php?f=181&t=34849&start=50
It seems people at Hardkernel found something, but I only have information provided at this thread.
Iām even seeing random reboots of the box running Ubuntu, like 5 within two weeks. I hope it is all related with the USB issues.
However, the mediasrv crashes seem not related with the USB issues because I canāt see any dmesg errors when it happens.
No issues, two different Bluetooth speakers connected right up and worked perfectly, no reboot and freezing.
Trying to duplicate your problem.
I can try setting up an SMB server to see if that makes a difference.
Are you using Ethernet or WiFi? If WiFi which adapter?
Is there anything beyond a basic/default install that you are doing. Any Additional hardware attached, etcā¦
Latest nightly and quite a few issues.
- I am having the same issue as another user with 4K switching on a Vizio TV results in blank screen. I couldnāt follow the conversation on exactly what the fix was (test buildā¦but I thought these were test builds)
-Onkyo receiver I am hearing little āpopsā of sound every minute or so when no audio is playing. Keep audio alive is off.
-When powering on with my remote (that has been working all along) now I just get a black screen. I have to pull the power with the TV on, and then the Coreelec logo displays. Maybe this is related to the resolution switching issue specific to Vizio?
Also, thank you for releasing nightly builds and keeping them up to date for the N2.
For 4k please execute dispinfo while you see black screen and send a link you receive.
For every minute āpopsā please make Screenshots for system->audio page. I have also onkyo and no issues
For powering on itās a already known issue for this build. Please clarify if you have some overclocking?
Am I the only one with this issue?
Just checked, all is working
Need a log as usual
Kodi and dmesg
Yes I was waiting for a confirmation. Will do that tomorrow.
No further issues here since updating to 20190531, lots of USB DVB and other USB testing, all fine.
@jarda , try latest nightly. In New kernel it works faster 60-70 Mb/s for read operations for my disk.
Hey
as I mentioned before in this thread I am experiencing frequent (and reproducible) hangs on my N2 when trying to do various operations (navigate, search on an NFS fs) via kodi.
I cross-compiled strace and tried to hunt down the issue, you can see it happening here at 13:19:56
Sadly I canāt upload logs to the forum so Iāll just link them:
kodi open fds http://paste.debian.net/plain/1085447
strace logs http://paste.debian.net/plain/1085449
dmesg will be on next post as I am also not allwed to post itā¦
The offending line seems to be the futex() but I have no idea on thisā¦
13:19:56.631510 nanosleep({tv_sec=0, tv_nsec=40000000}, NULL) = 0 <0.040216>
13:19:56.672079 clock_gettime(CLOCK_MONOTONIC_RAW, {tv_sec=7231, tv_nsec=625805531}) = 0 <0.000952>
13:19:56.673276 clock_gettime(CLOCK_MONOTONIC_RAW, {tv_sec=7231, tv_nsec=626168448}) = 0 <0.000122>
13:19:56.673909 clock_gettime(CLOCK_MONOTONIC_RAW, {tv_sec=7231, tv_nsec=626863656}) = 0 <0.000175>
13:19:56.674384 clock_gettime(CLOCK_REALTIME, {tv_sec=1559474396, tv_nsec=674579654}) = 0 <0.000157>
13:19:56.674749 futex(0x292bb78, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1563769363, tv_nsec=969579654}, FUTEX_BITSET_MATCH_ANY) = 0 <18.076223>
13:20:14.751234 futex(0x2c77374, FUTEX_WAIT_PRIVATE, 2, NULL) = 0 <0.000235>
13:20:14.751659 clock_gettime(CLOCK_REALTIME, {tv_sec=1559474414, tv_nsec=751727774}) = 0 <0.000056>
13:20:14.751858 futex(0x2c77374, FUTEX_WAKE_PRIVATE, 1) = 0 <0.000050>
13:20:14.752008 futex(0x292bc38, FUTEX_LOCK_PI_PRIVATE, NULL) = 0 <0.000302>
13:20:14.752504 futex(0x292bc38, FUTEX_UNLOCK_PI_PRIVATE) = 0 <0.000061>dmesg log:
date && uptime && dmesg http://paste.debian.net/plain/1085450
Debug log: http://ix.io/1KH7
dmesg: http://ix.io/1KH8
systemd journal: http://ix.io/1KH9
I got the exact same issue with my C2. The files are on a Synology server, mounted as systemd nfs shares.
It has not been an issue for a long timeā¦
Btw: strace should be available in system-tools addon.