• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

How many crashes has your T2 experienced in a year/s?

Possibly - to investigate further you would need to run the crashdiag diagnostic which examines the error dumps in /mod/core and provides details of what was executing at time of crash.

You may be able to determine some commonality between the errors.

Interpreting the output of crashdiag is normally beyond me.
 
Did I read somewhere that some crashes may be related to the local network?

I was wondering if there was such a thing as an order of things the t2 does after it booted?
 
Ok, just seems to me that there is a large proportion of crashes occurring in a matter of few seconds after booting.
 
Just had a run of three crashes. The first two were the usual locked-up machine that had crashed after dealing with the queued auto-decryption etc. after 11pm so hadn't powered down at midnight and no record in crashlog.
But the last was one I've not seen before. It looked like the front panel had crashed - no display, red ring on full brightness and no response to the remote, so I power cycled it. Crashlog said it had crashed soon after the timed startup at 5pm but it had still recorded the BBC 6pm News and had been recording the local news when I'd interrupted it.
 
everthewatcher said:
Crashlog said it had crashed soon after the timed startup at 5pm but it had still recorded the BBC 6pm News and had been recording the local news when I'd interrupted it.
Click to expand...
Did you check the two recordings? Are they working?

I had a crash at beginning of december which knocked out loads of packages. It's weird that it doesn't say the date/time in crashlog, only someting like 1970. I was able to pinpoint it by looking at the temp graph in sysmon when the disk started heating up over the nice green graph.
 
Well with all the above in mind, mine has crashed a lot over the years, sometimes for ages before I even realise but the logs say this :-
Humax 1
Humax crashed at Tue Oct 5 06:31:02 UTC 2021 - Uptime: 495636
Humax crashed at Wed Sep 29 12:50:02 UTC 2021 - Uptime: 3532
-----------------------------------------------------------------------------
Humax 2
Humax crashed at Mon Jun 14 07:53:38 UTC 2021 - Uptime: 361250
I still think this custom firmware is the best thing to have ever happened to this device.
 
If that helps anything at all this is my crashdiag

Code: 
>>> Beginning diagnostic crashdiag

Running: crashdiag
1.03.12
*********** Core file /mod/core/humaxtv.1617402276.354 ***********
Fri Apr  2 23:24:36 BST 2021
Core was generated by `/usr/bin/humaxtv'.
Program terminated with signal 11, Segmentation fault.
#0  0x2b66b514 in ?? () from /usr/lib/libopera.so.3.2
[Current thread is 1 (Thread 959)]
Thread
#0  0x2b66b514 in ?? () from /usr/lib/libopera.so.3.2

Thread 112
#0  0x2c59ee3c in recvmsg () from /lib/libpthread.so.0
#1  0x2c59ee20 in recvmsg () from /lib/libpthread.so.0

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

Thread 86
#0  0x2c59ee3c in recvmsg () from /lib/libpthread.so.0
#1  0x2c59ee20 in recvmsg () from /lib/libpthread.so.0

Thread 74
#0  0x2c5b2c20 in select () from /lib/libc.so.0
#1  0x2aaf0638 in ?? () from /var/lib/humaxtv_backup/mod/libnugget.so

Thread 73
#0  0x2c58d1ec in mq_timedreceive () from /lib/librt.so.0
#1  0x2c58d1cc in mq_timedreceive () from /lib/librt.so.0

Thread 70
#0  0x2c59e5dc in read () from /lib/libpthread.so.0
#1  0x2c59e5c0 in read () from /lib/libpthread.so.0

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

Thread 6
#0  0x2c59ea6c in accept () from /lib/libpthread.so.0
#1  0x2c59ea50 in accept () from /lib/libpthread.so.0

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



*********** Core file /mod/core/humaxtv.1633103748.354 ***********
Fri Oct  1 16:55:48 BST 2021
Core was generated by `/usr/bin/humaxtv'.
Program terminated with signal 11, Segmentation fault.
#0  0x2c15f6b0 in BMEM_Heap_ConvertAddressToOffset ()
   from /usr/lib/libnexus.so
[Current thread is 1 (Thread 674)]
Thread
#0  0x2c15f6b0 in BMEM_Heap_ConvertAddressToOffset ()

Thread 112
#0  0x2c59ee3c in recvmsg () from /lib/libpthread.so.0
#1  0x2c59ee20 in recvmsg () from /lib/libpthread.so.0

Thread 110
#0  0x2c59e068 in __lll_lock_wait () from /lib/libpthread.so.0
#1  0x2c597568 in pthread_mutex_lock () from /lib/libpthread.so.0
#2  0x2c0f0be4 in NEXUS_P_Scheduler_Step () from /usr/lib/libnexus.so
#3  0x2c0f1160 in ?? () from /usr/lib/libnexus.so

Thread 87
#0  0x2c59ee3c in recvmsg () from /lib/libpthread.so.0
#1  0x2c59ee20 in recvmsg () from /lib/libpthread.so.0

Thread 75
#0  0x2c5b2c20 in select () from /lib/libc.so.0
#1  0x2aaf0638 in ?? () from /var/lib/humaxtv_backup/mod/libnugget.so

Thread 74
#0  0x2c58d1ec in mq_timedreceive () from /lib/librt.so.0
#1  0x2c58d1cc in mq_timedreceive () from /lib/librt.so.0

Thread 71
#0  0x2c59e5dc in read () from /lib/libpthread.so.0
#1  0x2c59e5c0 in read () from /lib/libpthread.so.0

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

Thread 6
#0  0x2c59ea6c in accept () from /lib/libpthread.so.0
#1  0x2c59ea50 in accept () from /lib/libpthread.so.0

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



*********** Core file /mod/core/humaxtv.1644479310.355 ***********
Thu Feb 10 07:48:30 GMT 2022
Core was generated by `/usr/bin/humaxtv'.
Program terminated with signal 10, Bus error.
#0  0x014a1762 in ?? ()
[Current thread is 1 (Thread 928)]
Thread
#0  0x014a1762 in ?? ()

Thread 112
#0  0x2c59ee3c in recvmsg () from /lib/libpthread.so.0
#1  0x2c59ee20 in recvmsg () from /lib/libpthread.so.0

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

Thread 99
#0  0x2c597a98 in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0
#1  0x008fb1d0 in ?? ()

Thread 86
#0  0x2c59ee3c in recvmsg () from /lib/libpthread.so.0
#1  0x2c59ee20 in recvmsg () from /lib/libpthread.so.0

Thread 74
#0  0x2c5b2c20 in select () from /lib/libc.so.0
#1  0x2aaf0638 in ?? () from /var/lib/humaxtv_backup/mod/libnugget.so

Thread 73
#0  0x2c58d1ec in mq_timedreceive () from /lib/librt.so.0
#1  0x2c58d1cc in mq_timedreceive () from /lib/librt.so.0

Thread 70
#0  0x2c59e5dc in read () from /lib/libpthread.so.0
#1  0x2c59e5c0 in read () from /lib/libpthread.so.0

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

Thread 6
#0  0x2c59ea6c in accept () from /lib/libpthread.so.0
#1  0x2c59ea50 in accept () from /lib/libpthread.so.0

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





>>> Ending diagnostic crashdiag
 
All of your crashes are within humaxtv so are unlikely to be fixable - the most recent was attempting to access a non-existent memory location
 
Well, I seem to remember that some people have speculated that the dreaded crashes were occurring because of problems with the "internet" connection of the hdr with the router or something like that. My second hdr was not connected to the internet (couldn't be bothered) for various periods of months and years. No crashes. Since january I've connected it again and crashes have returned. By the handful. A lot more than my ethernet hdr. The fact that the wifi signal is about the poorest where my second hdr is located looks like the problem.
 
You must log in or register to reply here.
Back
Top