HDR-T2 locks up on putting into standby

Walshy

New Member
My box has recently started locking up on placing into standby. By this I mean that it works fine when on, then, when placing into standby, which we do when not in use, it becomes unresponsive and will not record. It will not switch on via the remote or the button on the front.
The only way out of this is to power cycle it using the switch at the back.
I am running 1.03.12 / 2.22(cf installed, but decided on posting here in case it's a generic issue) and have recently played around with samba settings. Last night I switched off samba to see if this would fix it, but it appears not to have helped.
I also have a WD NAS running twonky, which I've read can cause problems, but I've disabled content sharing, which is supposed to get around this.

Any ideas people? Without the recording functionality, the box is technically broken.
 
The lock-up you describe (only recoverable by a cold start) is not uncommon when the HDR-FOX is on but idle for long periods, but this is the first report I can recall of being able to trigger it at will by switching to stand-by. It does not correlate with the delinquent half-awake state - see Things Every... (click) section 18.
 
Having read about the delinquent half-awake state, it is similar in that the HDD doesn't power down and the attached usb drive remained powered, until I removed it yesterday at least.
I don't use power on/off timers. I've deleted a failed recording. The only thing I've not checked is the missing files as not sure how to check for this.

Any clues on how to fix this?
 
I think you will find it is not that. The difference is that delinquent half-awake responds to power-up commands, whereas the system freeze does not. I bet you can't access the WebF when you have your freeze, and you can in the half-awake state.
 
I bet you can't access the WebF when you have your freeze, and you can in the half-awake state.
Worth checking. This could be a front panel fault.
I haven't seen anyone post these symptoms before.

I would enable logging for humaxtv (run the debugtv diagnostic) and then get onto the box via telnet and drop to the command line. Then watch the debug log in real-time as you put the box into standby - the command is: tail -f /tmp/humaxtv.log
Hopefully there will be something near the end of that pointing to a cause.

If not, then install the redring package and enable debugging for that. Watch the redring log file during shutdown as that records communication between the Humax software and front panel - tail -f /mod/tmp/redring.log
 
Surprisingly I can access the web-if and I can telnet onto the box when in the fault condition.

I've installed redring, but the log remains empty.

The contents of humaxtv.log are as follows, with only the last line being output on putting the box into standby:

grep: /var/lib/humaxtv/mod/redring.conf: No such file or directory
grep: /var/lib/humaxtv/mod/redring.conf: No such file or directory
grep: /var/lib/humaxtv/mod/redring.conf: No such file or directory
grep: /var/lib/humaxtv/mod/redring.conf: No such file or directory
grep: /var/lib/humaxtv/mod/redring.conf: No such file or directory
grep: /var/lib/humaxtv/mod/redring.conf: No such file or directory
grep: /var/lib/humaxtv/mod/redring.conf: No such file or directory
grep: /var/lib/humaxtv/mod/redring.conf: No such file or directory
Micom Timestamp: 10 - Thu Jan 1 00:00:10 1970
USER=root
macaddr=00:03:78:B9:46:C0
HOME=/
bcmsata2=1
TERM=vt102
PATH=/sbin:/bin:/usr/sbin:/usr/bin
LD_PRELOAD=/var/lib/humaxtv_backup/mod/libdustbin.so /var/lib/humaxtv_backup/mod/libir3.so /var/lib/humaxtv_backup/mod/libredring.so
SHELL=/bin/sh
DUSTBIN_PATH=[Deleted Items]
PWD=/
IR3_OPTIONS=0
REDRING_TZ=GMT
VERBOSE=no
[RR] Sat Jan 1 00:00:08 2000: -------------------------------------
[RR] Sat Jan 1 00:00:08 2000: Initialising v2.14
[RR] Sat Jan 1 00:00:08 2000: Got Micom TX fd = 8
[RR] Sat Jan 1 00:00:08 2000: Could not get options.
[RR] Sat Jan 1 00:00:08 2000: Options 0x3
[RR] Sat Jan 1 00:00:08 2000: Timezone: GMT (0)
[RR] Sat Jan 1 00:00:08 2000: Level: ha_blue = 0x40
[RR] Sat Jan 1 00:00:08 2000: Level: ha_rec = 0xfc
[RR] Sat Jan 1 00:00:08 2000: -------------------------------------
-------------------------------------
Initialising IR3 v1.07
IR3 debug: 0
IR3 Mode: (0x1000)
IR3 Options: 0
Found at +00000000
getplns() = 0x100ad58 (@00000000)
NEXUS_IrInput_Open(00000000, 7fb08ad0, 2aab205c, 7fb08aec) = 01018448
-------------------------------------
Initialising Dustbin v1.0
Dustbin debug: 0
Dustbin media root: /mnt/hd2/My Video/
Dustbin path: /mnt/hd2/My Video/[Deleted Items]
-------------------------------------
route: SIOCADDRT: File exists
killall: tinyftp: no process killed
[RR] Sat Jan 2 00:00:00 1971: Standby ring dim detected.
[RR] Sat Jan 2 00:00:01 1971: Ring trying to go amber.
[RR] Sat Jan 2 00:00:01 1971: Changing to dim blue.
DRV_DSC_Init_Begin
SIOCDELRT failed , ret->-1
[P_MEDIA_CheckValidMediaId] Invalid Media ID.
[DI_MEDIA_MP_GetStreamInfo] Error - Invalid Media Id.
[RR]: Switched to persistent log file.
[scanFonts:448] [scanFonts:448] [scanFonts:448] [AP_BrowserManager_Proc:608] [AP_BrowserNetTime_startNetTimeTask:171] [AP_BrowserNetTime_startNetTimeTask:208] [AP_BrowserManager_Proc:733] ########################################
Domain :.humaxtvportal.com
CertPath :htvdev_portal_ccert_2k_20101106.p12
###### New Cert is Added
########################################
########################################
Domain :none
CertPath :humax_tvportal_rootcert_2k_20101106_pub.pem
###### New Cert is Added
########################################
########################################
Domain :.bbc.co.uk
CertPath :hdrfoxt2_20101001.p12
###### New Cert is Added
########################################
########################################
Domain :.bbc.co.uk
CertPath :rootcert_1k.pem
###### New Cert is Added
########################################
[syncBoxInfo:1240] killall: tinyftp: no process killed
humax#
 
Is this line, "Micom Timestamp: 10 - Thu Jan 1 00:00:10 1970" saying the front panel does not contain the current time?
 
Is this line, "Micom Timestamp: 10 - Thu Jan 1 00:00:10 1970" saying the front panel does not contain the current time?
Yes, but if it has just been power cycled by the switch on the back then that's expected.
 
I've installed redring, but the log remains empty.
Once you've installed it, go to the settings screen in the web interface and enable debug mode. That won't take effect until after the next restart unfortunately, but a reboot from the web interface should do it rather than having to power cycle from the back.
 
Once you've installed it, go to the settings screen in the web interface and enable debug mode. That won't take effect until after the next restart unfortunately, but a reboot from the web interface should do it rather than having to power cycle from the back.

I'm not sure what I'm doing wrong, but I can't get it to take the 'debug mode'. I change it to yes, then 'update settings' but going back to the page shows it set as 'no'.
Don't know whether this is related, but the page doesn't seem to render correctly (firefox on windows 7) as the redring options appear under 'epgkeywords' package.

Hence still no output in redring.log
 
Don't know whether this is related, but the page doesn't seem to render correctly (firefox on windows 7) as the redring options appear under 'epgkeywords' package.

Hence still no output in redring.log
Try removing the epgkeywords package, this is obsolete, and has been known to cause issues with the settings page.
 
Try removing the epgkeywords package, this is obsolete, and has been known to cause issues with the settings page.

Thanks, that worked. Settings page now renders properly and, more importantly, works, so thank you!

Output from redring.log on placing box into standby:
RR] Fri Jul 18 16:05:28 2014: -> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:05:28 2014: +> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:05:28 2014: !> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:05:31 2014: -> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:05:31 2014: +> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:05:31 2014: !> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:05:55 2014: -> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:05:55 2014: +> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:05:55 2014: !> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:06:06 2014: -> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:06:06 2014: +> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:06:06 2014: !> RingBrightness(0x1a) fc
[RR] Fri Jul 18 16:06:06 2014: -> DisplayBrightness(0x19) 1d
[RR] Fri Jul 18 16:06:06 2014: +> DisplayBrightness(0x19) 1d
[RR] Fri Jul 18 16:06:06 2014: !> DisplayBrightness(0x19) 1d
[RR] Fri Jul 18 16:06:06 2014: -> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:06:06 2014: Standby ring dim detected.
[RR] Fri Jul 18 16:06:06 2014: +> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:06:06 2014: !> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:06:06 2014: -> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:06:06 2014: Standby ring dim detected.
[RR] Fri Jul 18 16:06:06 2014: +> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:06:06 2014: !> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:06:07 2014: -> ClockControl(0x13) 01
[RR] Fri Jul 18 16:06:07 2014: +> ClockControl(0x13) 01
[RR] Fri Jul 18 16:06:07 2014: !> ClockControl(0x13) 01
[RR] Fri Jul 18 16:06:07 2014: -> RingColour(0xe) 00
[RR] Fri Jul 18 16:06:07 2014: Ring trying to go amber.
[RR] Fri Jul 18 16:06:07 2014: Changing to dim blue.
[RR] Fri Jul 18 16:06:07 2014: +> RingBrightness(0x1a) 3f
[RR] Fri Jul 18 16:06:07 2014: !> RingBrightness(0x1a) 3f
[RR] Fri Jul 18 16:06:07 2014: +> RingColour(0xe) 01
[RR] Fri Jul 18 16:06:07 2014: !> RingColour(0xe) 01
[RR] Fri Jul 18 16:06:07 2014: -> LEDControl(0x10) 00 00 01 00
[RR] Fri Jul 18 16:06:07 2014: [ TV = OFF ]
[RR] Fri Jul 18 16:06:07 2014: +> LEDControl(0x10) 00 00 01 00
[RR] Fri Jul 18 16:06:07 2014: [ TV = OFF ]
[RR] Fri Jul 18 16:06:07 2014: !> LEDControl(0x10) 00 00 01 00
[RR] Fri Jul 18 16:06:07 2014: [ TV = OFF ]
[RR] Fri Jul 18 16:06:07 2014: -> LEDControl(0x10) 00 00 08 00
[RR] Fri Jul 18 16:06:07 2014: [ HD = OFF ]
[RR] Fri Jul 18 16:06:07 2014: +> LEDControl(0x10) 00 00 08 00
[RR] Fri Jul 18 16:06:07 2014: [ HD = OFF ]
[RR] Fri Jul 18 16:06:07 2014: !> LEDControl(0x10) 00 00 08 00
[RR] Fri Jul 18 16:06:07 2014: [ HD = OFF ]
[RR] Fri Jul 18 16:06:07 2014: -> LEDControl(0x10) 00 80 00 00
[RR] Fri Jul 18 16:06:07 2014: [ Disk space 1 = OFF ]
[RR] Fri Jul 18 16:06:07 2014: +> LEDControl(0x10) 00 80 00 00
[RR] Fri Jul 18 16:06:07 2014: [ Disk space 1 = OFF ]
[RR] Fri Jul 18 16:06:07 2014: !> LEDControl(0x10) 00 80 00 00
[RR] Fri Jul 18 16:06:07 2014: [ Disk space 1 = OFF ]
[RR] Fri Jul 18 16:06:07 2014: -> LEDControl(0x10) 01 00 00 00
[RR] Fri Jul 18 16:06:07 2014: [ Disk space 2 = OFF ]
[RR] Fri Jul 18 16:06:07 2014: +> LEDControl(0x10) 01 00 00 00
[RR] Fri Jul 18 16:06:07 2014: [ Disk space 2 = OFF ]
[RR] Fri Jul 18 16:06:07 2014: !> LEDControl(0x10) 01 00 00 00
[RR] Fri Jul 18 16:06:07 2014: [ Disk space 2 = OFF ]
[RR] Fri Jul 18 16:06:08 2014: -> LEDControl(0x10) 02 00 00 00
[RR] Fri Jul 18 16:06:08 2014: [ Disk space 3 = OFF ]
[RR] Fri Jul 18 16:06:08 2014: +> LEDControl(0x10) 02 00 00 00
[RR] Fri Jul 18 16:06:08 2014: [ Disk space 3 = OFF ]
[RR] Fri Jul 18 16:06:08 2014: !> LEDControl(0x10) 02 00 00 00
[RR] Fri Jul 18 16:06:08 2014: [ Disk space 3 = OFF ]
[RR] Fri Jul 18 16:06:08 2014: -> SetClock(0x3) 53 c9 45 f0
[RR] Fri Jul 18 16:06:08 2014: +> SetClock(0x3) 53 c9 45 f0
[RR] Fri Jul 18 16:06:08 2014: !> SetClock(0x3) 53 c9 45 f0
[RR] Fri Jul 18 16:06:08 2014: -> SetWakeup(0x5) 01 53 c9 61 18
[RR] Fri Jul 18 16:06:08 2014: -> SetWakeup(0x5) 01 00 00 00 00
[RR] Fri Jul 18 16:06:09 2014: -> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:06:09 2014: Standby ring dim detected.
[RR] Fri Jul 18 16:06:09 2014: +> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:06:09 2014: !> RingBrightness(0x1a) 1d

Does this explain my problem to anyone?
 
I have compared your redring log with one the goes into standby correctly and the only difference I can find is the line 5 lines from the end, e.g. :-
Code:
[RR] Fri Jul 18 16:06:08 2014: -> SetWakeup(0x5) 01 00 00 00 00

My last 6 lines look like this :-
Code:
[RR] Fri Jul 18 16:37:03 2014: !> SetClock(0x3) 53 c9 4d 2f
[RR] Fri Jul 18 16:37:03 2014: -> SetWakeup(0x5) 01 53 c9 c2 5c
[RR] Fri Jul 18 16:37:03 2014: -> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:37:03 2014: Standby ring dim detected.
[RR] Fri Jul 18 16:37:03 2014: +> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:37:03 2014: !> RingBrightness(0x1a) 1d
af123 will be able to say if this is significant or not, I'm afraid I don't know
 
[RR] Fri Jul 18 16:06:09 2014: -> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:06:09 2014: Standby ring dim detected.
[RR] Fri Jul 18 16:06:09 2014: +> RingBrightness(0x1a) 1d
[RR] Fri Jul 18 16:06:09 2014: !> RingBrightness(0x1a) 1d

Does it just stop at that point or do you still get occasional things printed? What I'm not seeing is the final power-off code being sent to the front panel. Ezra's log doesn't have it either but that's expected as there isn't usually time for it to be written to the log before the disk is powered off.

I have a utility for talking directly to the front panel which we could try but first, can you try a couple of things?

I see you have the ir package installed. Out of interest, can you wake the box back up again through the web interface remote control even though the front panel and real remote aren't working?
Enable ir debug via the ir3/debugon diagnostic, reboot and then watch humaxtv.log to see if the commands from the remote control are being seen once it's in the broken state.

Also, when it's in this state where it no longer responds to the front panel or remote control, can you get access to the command line over telnet and run the following command?

Code:
humax# /mod/boot/tzget

That will check whether the Micom has been properly programmed with the date.

Next, try a reboot from the web interface when in the broken state and see if it comes back ok.

If it weren't for the fact that it can't be woken up again, I'd think this was a corrupt recording somewhere..
 
Right, out from humaxtv.log, first, in response to using the real remote:
Real IR code: 00000000 0xff001000
Real IR code: 0x000001 0xff001000
Real IR code: 0x000001 0xff001000
Real IR code: 0x000001 0xff001000
Real IR code: 0x000001 0xff001000
Real IR code: 0x000001 0xff001000
Real IR code: 0x000001 0xff001000
Real IR code: 0x000001 0xff001000
Real IR code: 0x000001 0xff001000
Real IR code: 0x000001 0xff001000
Real IR code: 0x000001 0xff001000


So it is seeing the remote attempt to power it back on.

And then in response to the web ir package:

mq_receive: 00
Injecting 00

InjectCommand: Got mutex
get_inbuf: Popped existing.
get_inbuf: Popped existing.
InjectCommand: Buffers 0 0100ad00 1 0100ad0c
InjectCommand: Input list 0
InjectCommand: setting signal (0x100ab90)
GetQueueSize: 1
GetEvents(): faking key 00 (2)
Real IR code: 00000000 0xff001000
GetQueueSize: 1
GetEvents(): faking key 00 (1)
Real IR code: 0x000001 0xff001000

Output from tzget shows it is getting the correct time:
humax# /mod/boot/tzget
Micom Timestamp: 1405764006 - Sat Jul 19 11:00:06 2014
BST

Is there a way to check for corrupt recordings? I've had a look, but can't see anything obvious. I'm assuming you've script for this?

I've set up a recording to start in five mins, so will post the output from the log for that too.
 
Nothing at all in humaxtv.log when the recording was supposed to start, but did see this in scanmounts.log:

or
Mount failed...
umount: can't forcibly umount /media/myBook: Invalid argument
192.168.1.101 is on-line - attempting to mount myBook
mount -o soft 192.168.1.101:/Public /media/myBook
mount: 192.168.1.101:/Public failed, reason given by server: Permission denied
mount: mounting 192.168.1.101:/Public on /media/myBook failed: Bad file descriptor
Mount failed...
umount: can't forcibly umount /media/myBook: Invalid argument

Which makes me think it could be something to do with my playing around with samba (myBook is my WD NAS).
Is there a way to undo this. Contents of mtab:
rootfs / rootfs rw 0 0
/dev/root / squashfs ro 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
devpts /dev/pts devpts rw 0 0
tmpfs /tmp tmpfs rw 0 0
tmpfs /media tmpfs rw 0 0
/dev/mtdblock1 /var/lib/humaxtv jffs2 rw 0 0
/dev/mtdblock2 /var/lib/humaxtv_backup jffs2 rw 0 0
/dev/sda1 /mnt/hd1 ext3 rw,data=ordered 0 0
/dev/sda2 /mnt/hd2 ext3 rw,data=ordered 0 0
/dev/sda3 /mnt/hd3 ext3 rw,data=ordered 0 0
/dev/sda2 /mnt/hd2/My\040Video/[ModSettings] ext3 rw,data=ordered 0 0
//192.168.1.101/Public /media/wd cifs rw,mand,unc=\\192.168.1.101\Public,username=admin,domain=WORKGROUP,rsize=16384,wsize=57344 0 0
//192.168.1.101/Public /mnt/hd2/My\040Video/[Shares]\040\040\040\040\040\040\040Do\040not\040delete!/wd cifs rw,mand,unc=\\192.168.1.101\Public,username=admin,domain=WORKGROUP,rsize=16384,wsize=57344 0 0
 
You are using quote tags instead of code tags. If you are using the WYSIWYG post editor (with a tool bar) the code tag is the one with the # icon instead of the " icon.

And then in response to the web ir package:
I take it this was while frozen, and failed to turn the box back on?
 
Right, it's working again. I've uninstalled network-shares-automount, and we're good as new.
I was playing with trying to get my NAS mounted as well as the samba settings before it all went wrong so I'm assuming my automount settings were what was causing the problem.

Af123, is there any logs/settings files I can post that would help figure out what is causing this?

Thanks for all your help in this.
 
Back
Top