Segmentation fault on a RasPi 4 (2GB)
Aaron2550 opened this issue · comments
AaronVB commented
Instantly segfaults after "Waiting for devices; press 'M+' to add, or 'Q' to quit"-message, i saw some earlier issues and already ran it thru gdb:
[New Thread 0xb2975230 (LWP 25628)]
[Thread 0xb2975230 (LWP 25628) exited]
Thread 11 "bfgminer" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb2174230 (LWP 25626)]
0xb6f1a0cc in ?? () from /lib/arm-linux-gnueabihf/libcurl-gnutls.so.4
(gdb) bt
#0 0xb6f1a0cc in ?? () from /lib/arm-linux-gnueabihf/libcurl-gnutls.so.4
#2 0x00046e78 in ?? ()30 (LWP 25622) exited]
Backtrace stopped: previous frame identical to this frame (corrupt stack?)5624)]
(gdb) thr app all bt
Thread 11 (Thread 0xb2174230 (LWP 25626)):
#0 0xb6f1a0cc in ?? () from /lib/arm-linux-gnueabihf/libcurl-gnutls.so.4
#2 0x00046e78 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 2 (Thread 0xb617c230 (LWP 25617)):
#0 __GI___poll (timeout=-1, nfds=2, fds=0xb617bc0c) at ../sysdeps/unix/sysv/linux/poll.c:29
#1 __GI___poll (fds=0xb617bc0c, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:26
#2 0xb6defa3c in ?? () from /lib/arm-linux-gnueabihf/libusb-1.0.so.0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 1 (Thread 0xb617e150 (LWP 25601)):
#0 __GI___nanosleep (remaining=0xbeffcff4, requested_time=0xbeffcff4) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
#1 __GI___nanosleep (requested_time=requested_time@entry=0xbeffcff4, remaining=remaining@entry=0xbeffcff4) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2 0xb6c0b578 in __sleep (seconds=0) at ../sysdeps/posix/sleep.c:55
#3 0x00018060 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
note: kernel 5.10.17-v71+, i havent even connected any asics yet.