[vdr] Re: VDR keeps restarting (gdb output)

["Koch, Steffen" <steffen.koch@sphinx-electronics.de>]

Maybe Pro-7 starts sending malformed EPG-Packets.... ;-))

> -----Original Message-----
> From: Stefan Schluenss [mailto:Stefan.Schluenss@gmx.de]
> Sent: Tuesday, January 29, 2002 10:11 AM
> To: vdr@linuxtv.org
> Subject: [vdr] Re: VDR keeps restarting (gdb output)
> 
> 
> Hi,
> 
> exact the same for me. Wondering why i can found the 
> reloading entries in
> /var/logmessages at nearly the same time (1:00).
> 
> First i thought that my dish has lost adjustment during the 
> last night storm
> here in northern germany and the EPG scan process can't get 
> any valid data.
> But at the same time as reported below?! Wow, what a storm.
> 
> I'm using VDR 0.98 with one DVB-s and one Nova.
> 
> > 
> > hello,
> > same here
> > on my both vdr systems
> > one is a clean vdr099pre2 with 1 DVB-s and 2 novas
> > and one is vdr099pre1 with AIO patch.
> > i tested with driver siemens_dvb-0.9-20011117
> > an older one and the actual cvs.
> > 
> > everytime i switch to the transponder of pro7,nt-v,kabel1,9-live
> > and wait some time, or switch to the an other channel, vdr 
> stops with an
> > segmentation fault. i discoverd this at 01:00 this morning.
> > 
> > here is a debugsession:
> > 
> > (gdb) run -v /video/video0 -c /video/conf -w 120 -l 3
> > Starting program: /video/src/DVDB/VDR/vdr -v /video/video0 
> -c /video/conf
> > -w 120 -l 3
> > [New Thread 1024 (LWP 4719)]
> > [New Thread 2049 (LWP 4720)]
> > Delayed SIGSTOP caught for LWP 4720.
> > [New Thread 1026 (LWP 4721)]
> > Delayed SIGSTOP caught for LWP 4721.
> > [New Thread 2051 (LWP 4722)]
> > Delayed SIGSTOP caught for LWP 4722.
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 1026 (LWP 4721)]
> > 0x0809ddab in siParseDescriptors (Descriptors=0x8193040, 
> Buffer=0xbf7ffaaf
> > "", Length=3584, TableID=80 'P') at si_parser.c:528
> > 528           DescriptorLength += GetDescriptorLength (Ptr);
> > (gdb) bt
> > #0  0x0809ddab in siParseDescriptors (Descriptors=0x8193040,
> > Buffer=0xbf7ffaaf "", Length=3584, TableID=80 'P') at 
> si_parser.c:528
> > #1  0x0809db22 in siParseEIT (Buffer=0xbf7fe9dc 
> "PA\237\003\203A") at
> > si_parser.c:302
> > #2  0x0809cb79 in createVdrProgramInfos (siBuffer=0xbf7fe9dc
> > "PA\237\003\203A") at libvdr.c:53
> > #3  0x0805b41a in ProcessEIT__4cEITPUc (this=0xbf7fe9d4, 
> buffer=0xbf7fe9dc
> > "PA\237\003\203A") at eit.c:761
> > #4  0x0805be79 in Action__12cSIProcessor (this=0x8115158) 
> at eit.c:1005
> > #5  0x080709ce in StartThread__7cThreadP7cThread 
> (Thread=0x8115158) at
> > thread.c:117
> > #6  0x40093f37 in pthread_start_thread () from /lib/libpthread.so.0
> > #7  0x40093f8e in pthread_start_thread_event () from 
> /lib/libpthread.so.0
> > (gdb) quit
> > 
> > 
> > 
> > 
> > 
> > On 29 Jan 2002, Michael Schlegel wrote:
> > 
> > > Falk Spitzberg <fspitzb@spitzberg.de> writes:
> > >
> > > > Since last night, vdr crashes right after startup 
> (about 5 seconds)
> > > > and is then restarted by runvdr.
> > > >
> > > > I have two DVB-S cards, vdr099pre1. That worked great 
> for about two
> > months
> > > >
> > > > There are no error messages in /var/log/messages. vdr logs it's
> > > > startup quite nomal. The only things that looks unusual 
> to me are two
> > > > processen called fu_thread.
> > >
> > >
> > > hey this is strange. Exact the same problem occurs here since last
> > > night.
> > >
> > > In my /var/log/messages are also no error messages.
> > >
> > > I've got an DBV-s and a Nova.
> > >
> > > cu
> > >   miki
> > >
> > >
> > > --
> > > Michael Schlegel <miki@schlegel-net.de>
> > >
> > > Gibt's ein anderes Wort fuer Synonym?
> > >
> > >
> > 
> > 
> > 
> 
> -- 
> GMX - Die Kommunikationsplattform im Internet.
> http://www.gmx.net
> 
> 
>