Resolving HDR-FOX Crash/Reboot Issues

[Trev]

Well, to be honest I couldn't find the thread referred to

It's fairly simple, disconnect the network at the HDR and see if it still crashes.

 

[Black Hole]

Steps for Resolving HDR-FOX Crash/Reboot Issues (click)

The following also find it:

• Forum search bar "steps for resolving crash" (with search titles only ticked)
• Google "site:hummy.tv steps for resolving crash"

 

[prpr]

Can anything be deduced from this:

humax ~ # diag crashdiag
Running: crashdiag
1.03.12
*********** Core file /mod/core/humaxtv.1490890264.277 ***********
Thu Mar 30 17:11:04 BST 2017
Core was generated by `/usr/bin/humaxtv'.
Program terminated with signal 4, Illegal instruction.
#0  0x01297b68 in ?? ()
[Current thread is 1 (Thread 694)]
Thread
#0  0x01297b68 in ?? ()

Thread 112
#0  0x2c583e3c in recvmsg () from /lib/libpthread.so.0
#1  0x2c583e20 in recvmsg () from /lib/libpthread.so.0

Thread 111
#0  0x2c5966bc in ioctl () from /lib/libc.so.0
#1  0x2c07224c in ?? () from /usr/lib/libnexus.so

Thread 86
#0  0x2c583e3c in recvmsg () from /lib/libpthread.so.0
#1  0x2c583e20 in recvmsg () from /lib/libpthread.so.0

Thread 74
#0  0x2c597c20 in select () from /lib/libc.so.0
#1  0x2aaefdf8 in _ftext () from /var/lib/humaxtv_backup/mod/libnugget.so
#2  0x00000020 in ?? ()

Thread 73
#0  0x2c5721ec in mq_timedreceive () from /lib/librt.so.0
#1  0x2c5721cc in mq_timedreceive () from /lib/librt.so.0

Thread 70
#0  0x2c5835dc in read () from /lib/libpthread.so.0
#1  0x2c5835c0 in read () from /lib/libpthread.so.0

Thread 68
#0  0x2c597c20 in select () from /lib/libc.so.0
#1  0x008fd36c in ?? ()

Thread 6
#0  0x2c583a6c in accept () from /lib/libpthread.so.0
#1  0x2c583a50 in accept () from /lib/libpthread.so.0

Thread 5
#0  0x2c597c20 in select () from /lib/libc.so.0
#1  0x0089b848 in ?? ()

or is it just put down to "one of those things"?

The second timestamp is wrong too:

Humax crashed at Thu Mar 30 16:11:05 UTC 2017 - Uptime: 40439
Humax crashed at Thu Mar 30 18:28:13 UTC 2017 - Uptime: 13

The first crash was at 17:11 (BST) and the second at 18:28 (BST). The latter was a crash after starting it up again after it had erroneously gone to sleep after the 17:11 crash and a subsequent recording.

 

[Deleted member 473]

is it just put down to "one of those things"

The thing being Humax?

 

[af123]

Can anything be deduced from this:

I can't get anything from that. Illegal instruction at a memory address that isn't part of the humaxtv space.