On 12/10/14 16:42, Klaus Schmidinger wrote:
> On 12.10.2014 16:30, Chris Mayo wrote:
>> I occasionally see vdr crashing when a recording starts like this:
>>
>> kernel: traps: recording[352] trap divide error ip:4cfeff sp:7fc8e9523e00
>> error:0 in vdr[40+15600
I occasionally see vdr crashing when a recording starts like this:
kernel: traps: recording[352] trap divide error ip:4cfeff sp:7fc8e9523e00
error:0 in vdr[40+156000]
runvdr[300]: Floating point exception
$ gdb /usr/bin/vdr
(gdb) disass /m 0x4cfeff
1514in remux.c
0x004cfee6 <
Been sitting on this for ages but in anticipation of 2.0:
--- PLUGINS/src/dvbhddevice/Makefile.orig
+++ PLUGINS/src/dvbhddevice/Makefile
@@ -98,7 +98,7 @@
$(SOFILE): $(OBJS) libhdffcmd
@$(MAKE) --no-print-directory -C libhdffcmd all
- $(CXX) $(CXXFLAGS) -shared $(OBJS) libhdffcmd/
On 27/08/11 15:24, Klaus Schmidinger wrote:
> On 27.08.2011 15:35, Chris Mayo wrote:
>> Progress bar display shows excessive times for radio programmes (no
>> video).
>>
>> A recording of about 5 minutes starts at 5:22:13 and ends at
>> 27404:47:54. The actual rec
Progress bar display shows excessive times for radio programmes (no video).
A recording of about 5 minutes starts at 5:22:13 and ends at
27404:47:54. The actual recording is fine. Recording is from BBC Radio 3
using DVB-T. ffmpeg -i shows:
Input #0, mpegts, from '1.ts':
Duration: 00:05:06.1
I'm getting a repeated (but not frequent or reproducible) oops that
occurs when the OSD is already displayed and I do more OSD operations
(quickly?).
Recently the oopses have been written to syslog (because of some of the
newer patches or firmware?) and I have attached one.
This is my current set