Help debugging freeze

[kowalski]

Hello,
I have a Gigablue Quad and OpenVix. Randomly, expecially on night, I found the decoder freezed, stuck with clock fixed. It doesn't happen every day but it happens once a week approximatly. I'm trying to understand what happens but the decoder is inaccessible (ssh or telnet too) and come back to work fine only switching it off and on, but after the restart I lost every log (I have log only from start, not from previous day).
Can you suggest me some tips to debug its behaviour?
Thanks in advance

 

[Larry-G]

Try setting your logs manager to save both crash logs and debug logs to a HDD or USB stick (be aware that using a HDD for debug logging will prevent that HDD from going to sleep as the log is written to the HDD continiously). This way all your logs are saved to a external device and will be safe from unexpected loss.

 

[2stein]

had the same behaviour on a vu duo... after a while it turned out to be a hardware problem: defective capacitor.

 

[pembo]

what about /var/log/messages, do you see anything in there that might give a clue over the period where it freezes?

 

[Larry-G]

had the same behaviour on a vu duo... after a while it turned out to be a hardware problem: defective capacitor.

The fauly capacitor only really affected a small batch of Vu+ Duo's. No other issue has had this issue nor are the likely to either.

 

[kowalski]

what about /var/log/messages, do you see anything in there that might give a clue over the period where it freezes?

I can't access the decoder while freezing... it's the reason why I'm asking how to preserve logs after forced physical reboot

 

[kowalski]

had the same behaviour on a vu duo... after a while it turned out to be a hardware problem: defective capacitor.

it's not that issue, I had a vu duo in the past and I replaced defective capacitor. On Gigablue Quad it seems a software failure, like kernel fault. But if I can't access o preserve logs I can't be sure.

 

[judge]

A debug log should remain on the system even after a forced reboot.

 

[kowalski]

Try setting your logs manager to save both crash logs and debug logs to a HDD or USB stick (be aware that using a HDD for debug logging will prevent that HDD from going to sleep as the log is written to the HDD continiously). This way all your logs are saved to a external device and will be safe from unexpected loss.

it was already enabled on /home/root/logs but I can't find anything

Is there a way to make append and rotate /var/log/messages instead of overwrite it?

 

[divil_a_bit]

Do you stream to other devices or via the webif?
I have a gb quad plus and if I remote stream with or without transcode the box will hang and will require switching off and on to recover.

 

[kowalski]

Do you stream to other devices or via the webif?
I have a gb quad plus and if I remote stream with or without transcode the box will hang and will require switching off and on to recover.

I do use remote stream (without transcode) very often and it works well. There are open issue on it?

 

[kowalski]

I was able to grab a kernel issue, do you notice something of known?

Jan 12 19:38:55 gbquad user.alert kernel: CPU 0 Unable to handle kernel paging request at virtual address 00000248, epc == e0dfada0, ra == e0dfb5a4
Jan 12 19:38:55 gbquad user.warn kernel: Oops[#1]:
Jan 12 19:38:55 gbquad user.warn kernel: CPU: 0 PID: 128 Comm: nx_sched_high_s Tainted: G           O 3.14.2 #1
Jan 12 19:38:55 gbquad user.warn kernel: task: cf685a40 ti: cf6c4000 task.ti: cf6c4000
Jan 12 19:38:55 gbquad user.warn kernel: $ 0   : 00000000 10008700 e0dfada0 00000001
Jan 12 19:38:55 gbquad user.warn kernel: $ 4   : 00000000 00000094 00000000 00000020
Jan 12 19:38:55 gbquad user.warn kernel: $ 8   : cf685a40 00000001 8180b670 00000000
Jan 12 19:38:55 gbquad user.warn kernel: $12   : 00000000 0000001b 00000000 77339020
Jan 12 19:38:55 gbquad user.warn kernel: $16   : e156c130 e17a2000 e17b7000 00000060
Jan 12 19:38:55 gbquad user.warn kernel: $20   : 00000080 00000094 e0dcde48 e0dd0000
Jan 12 19:38:55 gbquad user.warn kernel: $24   : 00000002 e0e75848                  
Jan 12 19:38:55 gbquad user.warn kernel: $28   : cf6c4000 cf6c5d98 e0e70000 e0dfb5a4
Jan 12 19:38:55 gbquad user.warn kernel: Hi    : 00000000
Jan 12 19:38:55 gbquad user.warn kernel: Lo    : 00000000
Jan 12 19:38:55 gbquad user.warn kernel: epc   : e0dfada0 NEXUS_Message_ReadComplete_impl+0x0/0x13c [dvb]
Jan 12 19:38:55 gbquad user.warn kernel:     Tainted: G           O
Jan 12 19:38:55 gbquad user.warn kernel: ra    : e0dfb5a4 NEXUS_Message_ReadComplete+0x30/0x50 [dvb]
Jan 12 19:38:55 gbquad user.warn kernel: Status: 10008703	KERNEL EXL IE 
Jan 12 19:38:55 gbquad user.warn kernel: Cause : 00800008
Jan 12 19:38:55 gbquad user.warn kernel: BadVA : 00000248
Jan 12 19:38:55 gbquad user.warn kernel: PrId  : 00025a11 (Broadcom BMIPS5000)
Jan 12 19:38:55 gbquad user.warn kernel: Modules linked in: ipv6 smsc75xx usbnet dvb(O) 8192cu(O)
Jan 12 19:38:55 gbquad user.warn kernel: Process nx_sched_high_s (pid: 128, threadinfo=cf6c4000, task=cf685a40, tls=00000000)
Jan 12 19:38:55 gbquad user.warn kernel: Stack : cf6c5ddc e156c0d0 e17a2000 e17b7000 00000000 00000094 00000091 e0d3ae88
Jan 12 19:38:55 gbquad user.warn kernel: 	  8005f1dc 00100100 cea66684 80072a40 e17a2000 00000000 8ad66000 00000000
Jan 12 19:38:55 gbquad user.warn kernel: 	  00000094 00000000 cea66680 ccd02180 e1630000 cea66780 e0dca8e4 e0dca920
Jan 12 19:38:55 gbquad user.warn kernel: 	  cf6c5e20 e0dcca28 81813600 cfe3fa40 cfe3feec 10008b00 cf6c5e38 00000001
Jan 12 19:38:55 gbquad user.warn kernel: 	  807af394 fffb8bc1 003f5662 cea66700 ccdda180 00000001 807af394 cfc4fa40
Jan 12 19:38:55 gbquad user.warn kernel: 	  ...
Jan 12 19:38:55 gbquad user.warn kernel: Call Trace:
Jan 12 19:38:55 gbquad user.warn kernel: [<e0dfada0>] NEXUS_Message_ReadComplete_impl+0x0/0x13c [dvb]
Jan 12 19:38:55 gbquad user.warn kernel: [<e0dfb5a4>] NEXUS_Message_ReadComplete+0x30/0x50 [dvb]
Jan 12 19:38:55 gbquad user.warn kernel: [<e0d3ae88>] dev_dmx_msg_cb_dataReady+0x22c/0x288 [dvb]
Jan 12 19:38:55 gbquad user.warn kernel: [<e0dcca28>] NEXUS_P_Scheduler_Step+0x57c/0x918 [dvb]
Jan 12 19:38:55 gbquad user.warn kernel: [<e0dcce00>] NEXUS_P_Scheduler_Thread+0x3c/0x60 [dvb]
Jan 12 19:38:55 gbquad user.warn kernel: [<e0dcddf8>] NEXUS_P_ThreadStart+0x78/0xc8 [dvb]
Jan 12 19:38:55 gbquad user.warn kernel: [<8004f704>] kthread+0x10c/0x124
Jan 12 19:38:55 gbquad user.warn kernel: [<80006c68>] ret_from_kernel_thread+0x14/0x1c
Jan 12 19:38:55 gbquad user.warn kernel: Code: afa20018  0837eb2f  8fa20018 <90820248> 27bdffe8  afb00010  afbf0014  00808021  1040001c 
Jan 12 19:38:55 gbquad user.warn kernel: ---[ end trace 5ab5c7de1a37737b ]---