[linux-dvb] Why xawtv crash my computer (hard) ?

[Gregoire Favre <Gregoire.Favre@freesurf.ch>]

Hello,

I finally found why my computer had hard crash when I start a vrdsync.pl
with -pipe or when I do a large cp of data on my computer...

If xawtv is on I got quiete immediatly (with vdrsync.pl or cp) an hard
crash (my system don't even react any more on MagicSysRq, but after that
crash I still can hear the sound from VDR). If I use fbtv in console, I
don't have the problem.

I run xawtv this way: 

xawtv -c /dev/v4l/video0 -geometry 770x580-0-0 -xvport 61 &

And xawtv -hwscan gives :
This is xawtv-3.94, running on Linux/x86_64 (2.6.9-rc4)
looking for available devices
port 61-61                              [ -xvport 61 ]
    type : Xvideo, video overlay
    name : video4linux

port 62-62                              [ -xvport 62 ]
    type : Xvideo, video overlay
    name : video4linux

port 63-63
    type : Xvideo, image scaler
    name : Matrox G-Series Backend Scaler

/dev/video0: OK                         [ -device /dev/video0 ]
    type : v4l2
    name : dvb
    flags: overlay capture  

I am under a 2.6.9-rc4 kernel with dvb CVS from 15.X.2004 under an amd64
gentoo system, but I was also having this problem with my "old" P4, and
also on the oldest P3 with same PCI/AGP cards :

1 Matrox Graphics, Inc. MGA G550 AGP (rev 01)
2 DVB-s rev 1.3 Hauppauge Philips Semiconductors SAA7146 (rev 01)
1 SCSI Adaptec AIC-7892A U160/m (rev 02)
1 SCSI Adaptec AHA-2940U/UW/D / AIC-7881U
1 Creative Labs SB Live! EMU10k1 (rev 06)

And same result if GLIBC is NPTL or not.

Which other info could be needed to track this problem down ?

I have just tried tvtime, but it take much much CPU and the quality is
really not the one I got with xawtv...

Thank you very much,
-- 
	Grégoire Favre
________________________________________________________________________
http://magma.epfl.ch/greg ICQ:16624071 mailto:Gregoire.Favre@freesurf.ch