[vdr] Re: to all vdr gurus: why is the watchdog so important ?

[chris <chris-tux@wanadoo.fr>]

Le Dimanche 14 Mars 2004 12:16, Klaus Schmidinger a écrit :
> chris wrote:
> > Le Samedi 13 Mars 2004 23:19, Klaus Schmidinger a écrit :
> > > chris wrote:
> > > > 1- With vdr 1.2.6 when I run 'vdr', I got a segmentation fault but
> > > > running 'vdr -w 60' works ok. Why ?
> > >
> > > Was this a single event or is it reproducable?
> > > Is this "plain vanilla" VDR or are there any patches and/or plugins
> > > involved?
> > >
> > > Klaus
> >
> > It is reproducable ad libitum.
>
I don't think it has something to do with vdr or the watchdog because it is 
reproducable when I ran dvb-szap before in a certain order relative to vdr. I 
don't want to waste your time until I fix the order that cause each time the 
seg fault.
Sometimes it is working but I got 
mar 14 12:44:44 tux vdr[3736]: VDR version 1.2.6 started
mar 14 12:44:44 tux vdr[3736]: loading /video/setup.conf
mar 14 12:44:44 tux vdr[3736]: loading /video/sources.conf
mar 14 12:44:44 tux vdr[3736]: loading /video/diseqc.conf
mar 14 12:44:44 tux vdr[3736]: loading /video/channels.conf
mar 14 12:44:44 tux vdr[3736]: loading /video/svdrphosts.conf
mar 14 12:44:44 tux vdr[3736]: loading /video/ca.conf
mar 14 12:44:44 tux vdr[3736]: loading /video/remote.conf
mar 14 12:44:44 tux vdr[3736]: loading /video/keymacros.conf
mar 14 12:44:44 tux vdr[3736]: found 1 video device
mar 14 12:44:44 tux vdr[3736]: setting primary device to 1
mar 14 12:44:44 tux vdr[3736]: device 1 has no MPEG decoder
mar 14 12:44:44 tux vdr[3736]: SVDRP listening on port 2001
mar 14 12:44:49 tux vdr[3736]: switching to channel 2
mar 14 12:45:00 tux vdr[3736]: switching to channel 3
mar 14 12:45:01 tux vdr[3736]: switching to channel 4

Is it normal to have 'device 1 has no MPEG decoder' ?
Anyway, thanks for the answer
> Must be something special about your setup, because I start VDR here
> quite often, with or without watchdog, and don't have this.
>
I think so too because other guys told me they are using vdr on a mdk distro 
with no problem, but I can't know what IS the problem. I can't understand why 
I can't used a channels.conf file that I know is working on another 
config...even if I use the original channels.conf file I can only receive one 
or two channels and it seems that the settings are not correct for my config 
(astra) ie i receive dsf with the sat1 settings ...

> What I do have is that every 10th time or so (haven't really counted it)
> when I kill a running VDR, the computer locks up completely. Must be
> something in the DVB driver, but I haven't spent time into investigating
> that yet. Maybe it's gone with the dvb-kernel driver, anyway...
>

> > I have pasted in a previous thread the
> > /var/log/messages data after the segmentation fault (but can do it again
> > if you feel it interesting).
>
> Please do so, and also check whether there is a core file and do a
> backtrace (start with 'gdb vdr core' and enter 'bt').
>
there is no core, here is the /var/log/messages (sorry a bit long...)
mar 14 12:28:36 tux vdr[3361]: VDR version 1.2.6 started
mar 14 12:28:36 tux vdr[3361]: loading /video/setup.conf
mar 14 12:28:36 tux vdr[3361]: loading /video/sources.conf
mar 14 12:28:36 tux vdr[3361]: loading /video/diseqc.conf
mar 14 12:28:36 tux vdr[3361]: loading /video/channels.conf
mar 14 12:28:36 tux vdr[3361]: loading /video/svdrphosts.conf
mar 14 12:28:36 tux vdr[3361]: loading /video/ca.conf
mar 14 12:28:36 tux vdr[3361]: loading /video/remote.conf
mar 14 12:28:36 tux vdr[3361]: loading /video/keymacros.conf
Mar 14 12:28:36 tux kernel: Linux video capture interface: v1.00
Mar 14 12:28:37 tux kernel: DVB: registering new adapter 
(Technotrend/Hauppauge PCI rev2.1 or 2.2).
Mar 14 12:28:37 tux kernel: PCI: Found IRQ 10 for device 02:0a.0
Mar 14 12:28:37 tux kernel: PCI: Sharing IRQ 10 with 00:1f.2
Mar 14 12:28:38 tux kernel: stv0299.c: setup for tuner BSRU6, TDQB-S00x
Mar 14 12:28:38 tux kernel: DVB: registering frontend 0:0 
(STV0299/TSA5059/SL1935 based)...
Mar 14 12:28:41 tux kernel: DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 
71010068, app 8000261a
Mar 14 12:28:41 tux kernel: DVB: AV7111(0) - firmware supports CI link layer 
interface
Mar 14 12:28:41 tux kernel: av7110(0): adac type set to 0
Mar 14 12:28:41 tux kernel: Technotrend/Hauppauge PCI rev2.1 or 2.2 adapter 0 
has MAC addr = 00:d0:5c:20:43:0cMar 14 12:28:41 tux kernel: sda: Unit Not 
Ready, sense:
Mar 14 12:28:41 tux kernel: Current 00:00: sense key Not Ready
Mar 14 12:28:41 tux kernel: Additional sense indicates Medium not present
Mar 14 12:28:41 tux kernel: sda: Unit Not Ready, sense:
Mar 14 12:28:41 tux kernel: Current 00:00: sense key Not Ready
Mar 14 12:28:41 tux kernel: Additional sense indicates Medium not present
Mar 14 12:28:41 tux kernel: Unable to handle kernel NULL pointer dereference 
at virtual address 00000ed8
Mar 14 12:28:41 tux kernel:  printing eip:
Mar 14 12:28:41 tux kernel: d0dff0e9
Mar 14 12:28:41 tux kernel: *pde = 00000000
Mar 14 12:28:41 tux kernel: Oops: 0000
Mar 14 12:28:41 tux kernel: dvb-ttpci alps_bsrv2 alps_tdmb7 alps_tdlb7 
grundig_29504-401 grundig_29504-491 stv0299 ves1820 dvb-core videodev input 
parport_pc lp parport ipt_TOS ipt_REJECT ipt_LOG ipt_state ip_nat_irc 
ip_nat_tftp ip_nat_ftp ip_conntrack_irc ip_conntrack_tftp ip_conntrack_ftp 
ipt_multiport ipt_conntrack iptable_filter iptable_mangle iptable_nat 
ip_conntrack ip_tables snd-seq-midi snd-seq-oss snd-seq-midi-event snd-seq 
snd-pcm-oss snd-mixer-oss snd-au8810 snd-pcm snd-page-alloc snd-timer 
gameport snd-mpu401-uart snd-rawmidi snd-seq-device snd-ac97-codec snd 
soundcore af_packet floppy tulip sr_mod sd_mod scsimon usb-storage supermount 
ide-cd cdrom ide-scsi scsi_mod usb-uhci usbcore rtc ext3 jbd
Mar 14 12:28:41 tux kernel: CPU:    0
Mar 14 12:28:41 tux kernel: EIP:    
0010:[usb-storage:transferred+2215781/93409191]    Not tainted
Mar 14 12:28:41 tux kernel: EIP:    0010:[<d0dff0e9>]    Not tainted
Mar 14 12:28:41 tux kernel: EFLAGS: 00210046
Mar 14 12:28:41 tux kernel: EIP is at dvb_video_open+0x29/0xb0 [dvb-ttpci]
Mar 14 12:28:41 tux kernel: eax: 00000000   ebx: 00000000   ecx: c2ea57e0   
edx: 00000ed0
Mar 14 12:28:41 tux kernel: esi: c2ea57e0   edi: c28e8060   ebp: c2a71f28   
esp: c2a71f20
Mar 14 12:28:41 tux kernel: ds: 0018   es: 0018   ss: 0018
Mar 14 12:28:41 tux kernel: Process vdr (pid: 3361, stackpage=c2a71000)
Mar 14 12:28:41 tux kernel: Stack: c8b06ca0 c28e8060 c2a71f4c c0233f40 
c28e8060 c2ea57e0 c015fca0 c8b06ca8
Mar 14 12:28:41 tux kernel:        c2ea57e0 c28e8060 00000000 c2a71f68 
c0200844 c28e8060 c2ea57e0 00000802
Mar 14 12:28:41 tux kernel:        ce237000 00000004 c2a71fa0 c02006ae 
c2a653c0 c12cf320 00000802 c2a653c0
Mar 14 12:28:41 tux kernel: Call Trace:
Mar 14 12:28:41 tux kernel:  [devfs_open+304/432] devfs_open+0x130/0x1b0 
[kernel]
Mar 14 12:28:41 tux kernel:  [<c0233f40>] devfs_open+0x130/0x1b0 [kernel]
Mar 14 12:28:41 tux kernel:  [dentry_open+388/464] dentry_open+0x184/0x1d0 
[kernel]
Mar 14 12:28:41 tux kernel:  [<c0200844>] dentry_open+0x184/0x1d0 [kernel]
Mar 14 12:28:41 tux kernel:  [filp_open+78/96] filp_open+0x4e/0x60 [kernel]
Mar 14 12:28:41 tux kernel:  [<c02006ae>] filp_open+0x4e/0x60 [kernel]
Mar 14 12:28:41 tux kernel:  [sys_open+61/144] sys_open+0x3d/0x90 [kernel]
Mar 14 12:28:41 tux kernel:  [<c0200a5d>] sys_open+0x3d/0x90 [kernel]
Mar 14 12:28:41 tux kernel:  [system_call+51/64] system_call+0x33/0x40 
[kernel]
Mar 14 12:28:41 tux kernel:  [<c01c4333>] system_call+0x33/0x40 [kernel]
Mar 14 12:28:41 tux kernel:
Mar 14 12:28:41 tux kernel: Code: 8b 42 08 89 42 0c fb ba 03 00 00 00 8d 83 e0 
0e 00 00 b9 01
mar 14 12:29:43 tux su(pam_unix)[3414]: session opened for user root by 
chris(uid=501)
[root@tux vdr-1.2.6]# tail -n80 /var/log/messages
Mar 14 12:17:40 tux kernel: sda: Unit Not Ready, sense:
Mar 14 12:17:40 tux kernel: Current 00:00: sense key Not Ready
Mar 14 12:17:40 tux kernel: Additional sense indicates Medium not present
Mar 14 12:17:41 tux kernel: sda: Unit Not Ready, sense:
Mar 14 12:17:41 tux kernel: Current 00:00: sense key Not Ready
Mar 14 12:17:41 tux kernel: Additional sense indicates Medium not present
Mar 14 12:17:41 tux kernel: sda: Unit Not Ready, sense:
Mar 14 12:17:41 tux kernel: Current 00:00: sense key Not Ready
Mar 14 12:17:41 tux kernel: Additional sense indicates Medium not present
Mar 14 12:25:12 tux kde3(pam_unix)[2061]: session opened for user chris by 
(uid=0)
Mar 14 12:25:13 tux kernel: sda: Unit Not Ready, sense:
Mar 14 12:25:13 tux kernel: Current 00:00: sense key Not Ready
Mar 14 12:25:13 tux kernel: Additional sense indicates Medium not present
Mar 14 12:25:13 tux kernel: sda: Unit Not Ready, sense:
Mar 14 12:25:13 tux kernel: Current 00:00: sense key Not Ready
Mar 14 12:25:13 tux kernel: Additional sense indicates Medium not present
Mar 14 12:25:14 tux kernel: sda: Unit Not Ready, sense:
Mar 14 12:25:14 tux kernel: Current 00:00: sense key Not Ready


> > Note that i have a kernel panic when i log out.

sorry for the bad expression it should have been when I quit mdk.
> When you "log out"??? Does the mean "when you log out from your shell"?
> That's very odd...
>
> > I just dl the plain 1.2.6 VDR.
>
> Does this mean you have downloaded it, or you are going to download it?
I have downloaded it, compiled it following the instructions as I understood 
them (perhaps made some mistakes but got no error messages during the 
compilation process)
>
> Klaus



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.