A crash with a diag - any use to anyone ?

peterworks

peterworks

Ye Olde Bowler
Had a crash on Friday as the box came out of standby to start a recording. Not sure if the crash diag output is of any use (I cannot fathom it !) but here it is:

Code: 
*** Core file /mod/core/humaxtv.1575647881.323 ***
Fri Dec  6 15:58:01 GMT 2019
Core was generated by `/usr/bin/humaxtv'.
Program terminated with signal 11, Segmentation fault.
#0  0x2c644414 in dlsym () from /lib/libdl.so.0
[Current thread is 1 (Thread 750)]
Thread
#0  0x2c644414 in dlsym () from /lib/libdl.so.0

Thread 102
#0  0x2c588e3c in recvmsg () from /lib/libpthread.so.0
#1  0x2c588e20 in recvmsg () from /lib/libpthread.so.0

Thread 101
#0  0x2c59b6bc in ioctl () from /lib/libc.so.0
#1  0x2c07724c in ?? () from /usr/lib/libnexus.so

Thread 76
#0  0x2c588e3c in recvmsg () from /lib/libpthread.so.0
#1  0x2c588e20 in recvmsg () from /lib/libpthread.so.0

Thread 64
#0  0x2c59cc20 in select () from /lib/libc.so.0
#1  0x2aada638 in ?? () from /var/lib/humaxtv_backup/mod/libnugget.so

Thread 61
#0  0x2c5885dc in read () from /lib/libpthread.so.0
#1  0x2c5885c0 in read () from /lib/libpthread.so.0

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

Thread 44
#0  0x2c582550 in pthread_getspecific () from /lib/libpthread.so.0
#1  0x2c0da9c0 in NEXUS_P_ThreadInfo_Get () from /usr/lib/libnexus.so
#2  0x2c0d8214 in NEXUS_Module_Lock_Tagged () from /usr/lib/libnexus.so
#3  0x2c0a0c44 in NEXUS_Message_Open () from /usr/lib/libnexus.so
#4  0x008f45bc in ?? ()
 
I had another one today - here is the crash diag output.
>> Beginning diagnostic crashdiag
Click to expand...


Running: crashdiag
1.03.12
*********** Core file /mod/core/humaxtv.1663817508.320 ***********
Thu Sep 22 04:31:48 BST 2022
Core was generated by `/usr/bin/humaxtv'.
Program terminated with signal 11, Segmentation fault.
#0 0x2c1fdf80 in BVDC_P_Scaler_SetInfo_isr () from /usr/lib/libnexus.so
[Current thread is 1 (Thread 650)]
Thread
#0 0x2c1fdf80 in BVDC_P_Scaler_SetInfo_isr () from /usr/lib/libnexus.so

Thread 110
#0 0x2c588e3c in recvmsg () from /lib/libpthread.so.0
#1 0x2c588e20 in recvmsg () from /lib/libpthread.so.0

Thread 85
#0 0x2c588e3c in recvmsg () from /lib/libpthread.so.0
#1 0x2c588e20 in recvmsg () from /lib/libpthread.so.0

Thread 73
#0 0x2c59cc20 in select () from /lib/libc.so.0
#1 0x2aada638 in ?? () from /var/lib/humaxtv_backup/mod/libnugget.so

Thread 70
#0 0x2c5885dc in read () from /lib/libpthread.so.0
#1 0x2c5885c0 in read () from /lib/libpthread.so.0

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

Thread 5
#0 0x2c588a6c in accept () from /lib/libpthread.so.0
#1 0x2c588a50 in accept () from /lib/libpthread.so.0

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






>> Ending diagnostic crashdiag
Click to expand...
Click to expand...

Is it worth me doing these as I am unsure if anyone is looking at them with a view to finding an answer.
 
It may be of use to about three (active) people, so please keep doing it if you can be bothered.
 
It would be useful to know what packages you have installed. Rather than trying to grab a screenshot of a long list you might find it easiest to cut and paste the output from opkg list-installed.
 
Installed packages:
HumaxTwo# opkg list-installed
anacron - 2.3-2
at - 3.1.18
auto-unprotect - 2.0.2
auto-update - 2.0.5
betaftpd - 0.0.8pre17-5
boot-settings - 1.0.4
busybox - 1.20.2-1
bzip2 - 1.0.4
ca-bundle - 3.41
crashdiag - 1.1
cron-daemon - 1.18.3-5
curl - 7.63.0
dbupdate - 1.0.0
disable-dso - 0.3-1
disable-ota - 1.0.3-4
dlna-servername - 1.0.3
e2fsprogs - 1.42.13
epg - 1.2.8
fan - 1.0.0
ffmpeg - 4.1-1
file - 5.0.4
gdb - 7.1-1
hmt - 2.0.11
hwctl - 1.0.0
id3v2 - 0.1.11-1
inotify-tools - 3.14
jim - 0.81-3
jim-cgi - 0.7-2
jim-xconv - 1.0.0
lamemp3 - 3.98.4
libpcre - 8.37-1
libreadline - 6.2-1
libutil - 0.9.29
libxconv - 1.0.3
lighttpd - 1.4.53-1
lsof - 4.87
multienv - 1.7-1
ncurses - 5.9
newk - 1.0.5-1
nicesplice - 1.8
ntpclient - 2010-365-5
nugget - 1.0
openssl - 1.1.1.d-1
openssl-command - 1.0.0.d
opkg-beta - 1.1-1
procps - 3.2.8-3
recmon - 2.2.1-1
redring - 2.20-1
rs - 1.5.1-3
rsvsync - 1.1.13
samba - 3.6.25-1
screensaver - 0.3.2
screensaver-glass-blue - 1.0.0
service-control - 2.5
sqlite3 - 3.38.5
sqlite3-xconv - 1.0.2
ssmtp - 2.64
stripts - 1.4.5
swapper - 1.0.1
sweeper - 2.2.5-2
sysmon - 1.2.6
tcpfix - 1.0.0
tcpping - 1.1
tidy-folders - 1.0.3
tmenu - 1.22
trm - 1.2
tunefix - 2.1.0
tunefix-update - 1.0.120
tvdiary - 0.0.4-4
tweak - 1.0
undelete - 1.6-6
webif - 1.5.0-7
webif-channelicons - 1.1.27
webif-charts - 1.3
webshell - 1.0.4
wget - 1.20.3
wireless-tools - 29-1
zip - 3.0-1
HumaxTwo#
Click to expand...
 
From the almost negligible information that has leaked into the web, the failing routine is a graphics function that probably received a wrongly sized or null buffer pointer from the calling layer ("Magnum Porting Interface"). As this doesn't happen all the time, one can only say that something bad must have happened earlier.
 
Another one today:

>> Beginning diagnostic crashdiag
Click to expand...

Running: crashdiag
1.03.12
*********** Core file /mod/core/humaxtv.1663817508.320 ***********
Thu Sep 22 04:31:48 BST 2022
Core was generated by `/usr/bin/humaxtv'.
Program terminated with signal 11, Segmentation fault.
#0 0x2c1fdf80 in BVDC_P_Scaler_SetInfo_isr () from /usr/lib/libnexus.so
[Current thread is 1 (Thread 650)]
Thread
#0 0x2c1fdf80 in BVDC_P_Scaler_SetInfo_isr () from /usr/lib/libnexus.so

Thread 110
#0 0x2c588e3c in recvmsg () from /lib/libpthread.so.0
#1 0x2c588e20 in recvmsg () from /lib/libpthread.so.0

Thread 85
#0 0x2c588e3c in recvmsg () from /lib/libpthread.so.0
#1 0x2c588e20 in recvmsg () from /lib/libpthread.so.0

Thread 73
#0 0x2c59cc20 in select () from /lib/libc.so.0
#1 0x2aada638 in ?? () from /var/lib/humaxtv_backup/mod/libnugget.so

Thread 70
#0 0x2c5885dc in read () from /lib/libpthread.so.0
#1 0x2c5885c0 in read () from /lib/libpthread.so.0

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

Thread 5
#0 0x2c588a6c in accept () from /lib/libpthread.so.0
#1 0x2c588a50 in accept () from /lib/libpthread.so.0

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



*********** Core file /mod/core/humaxtv.1669036390.320 ***********
Mon Nov 21 13:13:10 GMT 2022
Core was generated by `/usr/bin/humaxtv'.
Program terminated with signal 11, Segmentation fault.
#0 0x2c644414 in dlsym () from /lib/libdl.so.0
[Current thread is 1 (Thread 795)]
Thread
#0 0x2c644414 in dlsym () from /lib/libdl.so.0

Thread 106
#0 0x2c588e3c in recvmsg () from /lib/libpthread.so.0
#1 0x2c588e20 in recvmsg () from /lib/libpthread.so.0

Thread 105
#0 0x2c59b6bc in ioctl () from /lib/libc.so.0
#1 0x2c07724c in ?? () from /usr/lib/libnexus.so

Thread 80
#0 0x2c588e3c in recvmsg () from /lib/libpthread.so.0
#1 0x2c588e20 in recvmsg () from /lib/libpthread.so.0

Thread 68
#0 0x2c59cc20 in select () from /lib/libc.so.0
#1 0x2aada638 in ?? () from /var/lib/humaxtv_backup/mod/libnugget.so

Thread 65
#0 0x2c5885dc in read () from /lib/libpthread.so.0
#1 0x2c5885c0 in read () from /lib/libpthread.so.0

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

Thread 48
#0 0x2c588068 in __lll_lock_wait () from /lib/libpthread.so.0
#1 0x2c581568 in pthread_mutex_lock () from /lib/libpthread.so.0
#2 0x2c147370 in BKNI_AcquireMutex () from /usr/lib/libnexus.so
#3 0x2c0d8228 in NEXUS_Module_Lock_Tagged () from /usr/lib/libnexus.so
#4 0x2c09ff14 in NEXUS_PidChannel_Open () from /usr/lib/libnexus.so
#5 0x008f38fc in ?? ()

Thread 16
#0 0x2aaaa488 in _dl_find_hash () from /lib/ld-uClibc.so.0
#1 0x2aaaa890 in _dl_linux_resolver () from /lib/ld-uClibc.so.0
#2 0x2aaae694 in _dl_linux_resolve () from /lib/ld-uClibc.so.0
#3 0x0061f604 in ?? ()

Thread 5
#0 0x2c588068 in __lll_lock_wait () from /lib/libpthread.so.0
#1 0x2c581568 in pthread_mutex_lock () from /lib/libpthread.so.0
#2 0x2af92a20 in free () from /usr/lib/liboperamalloc.so
#3 0x2b7e6f8c in ?? () from /usr/lib/libopera.so.3.2

>> Ending diagnostic crashdiag
Click to expand...
Click to expand...
 
Well, that's the same as the previous one. What was happening to the box on these occasions?
 
You must log in or register to reply here.
Back
Top