Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] FW: [vdr] Re: error during replay



hi list, 

i just installed the vdr 1.0.3-aio. due the replay of a recorded movie,
(especially while pressing >> or || etc.) the system crashes with the
error 

"No accelerated IMDCT transform found"


and i knew from the vdr-list that this is not the problem, its something
about the driver/system. 


did anybody of u had the same problem and found a solution?


ok the output in /var/log/messages is

Jun  3 14:40:51 video vdr[950]: VDR version 1.0.3 AIO-2605 started Jun
3 14:40:51 video vdr[950]: MP3 extention version 0.4.3 Jun  3 14:40:51
video vdr[950]: MPlayer extention version 0.4.3 Jun  3 14:40:51 video
vdr[950]: loading /video/setup.conf Jun  3 14:40:51 video vdr[950]:
loading /video/channels.conf Jun  3 14:40:51 video vdr[950]: loading
/video/timers.conf Jun  3 14:40:51 video vdr[950]: loading
/video/commands.conf Jun  3 14:40:51 video vdr[950]: loading
/video/svdrphosts.conf Jun  3 14:40:51 video vdr[950]: loading
/video/ca.conf Jun  3 14:40:51 video vdr[950]: loading
/video/mp3sources.conf Jun  3 14:40:51 video automount[606]: attempting
to mount entry /mnt/nfs Jun  3 14:40:51 video automount[951]:
lookup(file): lookup for nfs failed Jun  3 14:40:51 video vdr[950]:
WARNING: source base /mnt/nfs/mp3 not found/permission denied Jun  3
14:40:51 video automount[606]: attempting to mount entry /mnt/cdrom Jun
3 14:40:51 video kernel: VFS: Disk change detected on device
ide1(22,0)
Jun  3 14:40:51 video vdr[950]: loading /video/mplayersources.conf Jun
3 14:40:51 video vdr[950]: probing /dev/ost/frontend0 Jun  3 14:40:51
video vdr[955]: EIT processing thread started (pid=955)
- master
Jun  3 14:40:51 video vdr[950]: probing /dev/ost/frontend1
Jun  3 14:40:51 video vdr[950]: found 1 video device
Jun  3 14:40:51 video vdr[950]: setting primary DVB to 1
Jun  3 14:40:51 video vdr[950]: reading EPG data from /video/epg.data
Jun  3 14:40:51 video vdr[956]: TELESPY processing thread started
(pid=956)
Jun  3 14:40:51 video vdr[950]: switching to channel 3
Jun  3 14:40:51 video vdr[950]: SVDRP listening on port 2001 Jun  3
14:40:51 video vdr[950]: setting watchdog timer to 60 seconds Jun  3
14:40:51 video vdr[958]: LIRC remote control thread started
(pid=958)
Jun  3 14:40:52 video kernel: lirc_serial: auto-detected active high
receiver Jun  3 14:40:56 video automount[959]: expired /mnt/cdrom Jun  3
14:40:58 video vdr[950]: max. latency time 1 seconds Jun  3 14:41:25
video vdr[950]: no translation found for 'VCD' in language 1 (Deutsch)
Jun  3 14:41:25 video vdr[950]: no translation found for 'Teletext' in
language 1 (Deutsch) Jun  3 14:41:32 video vdr[950]: loading
/video/SciFi/Outer_Limits_-_Die_unbekannte_Dimension/Spurlos_verschwunde
n/2002-06-03.03.18.50.98.rec//marks.vdr
Jun  3 14:41:32 video vdr[950]: replay
/video/SciFi/Outer_Limits_-_Die_unbekannte_Dimension/Spurlos_verschwunde
n/2002-06-03.03.18.50.98.rec
Jun  3 14:41:32 video vdr[950]: playing
'/video/SciFi/Outer_Limits_-_Die_unbekannte_Dimension/Spurlos_verschwund
en/2002-06-03.03.18.50.98.rec/001.vdr'
Jun  3 14:41:33 video vdr[965]: output thread started (pid=965) Jun  3
14:41:33 video vdr[966]: input thread started (pid=966) Jun  3 14:41:33
video vdr[966]: resuming replay at index 7176
(0:04:47.02)
Jun  3 14:41:58 video kernel: dvb0: ARM crashed!

i just thought that "No accelerated IMDCT transform found" ist the
error, because it was the last message appearing before the restart



thx, Mich@


-----Original Message-----
From: vdr-bounce@linuxtv.org [mailto:vdr-bounce@linuxtv.org] On Behalf
Of Andreas Schultz
Sent: Monday, June 03, 2002 2:26 PM
To: vdr@linuxtv.org
Subject: [vdr] Re: error during replay


On Monday 03 June 2002 13:50, michael dawart wrote:
> hi list,
>
> i just installed the vdr 1.0.3-aio. due the replay of a recorded
> movie, (especially while pressing >> or || etc.) the system crashes 
> with the error
>
> "No accelerated IMDCT transform found"

The above message is totaly unrelated to any and all crashes. It's just
an 
indication wether liba52 was compiled with djbfft or not.
To narrow your crash down, check your syslog for any suspicious
messages, or 
strace vdr and/or try to run vdr under gdb and post the output

Andreas

-- 
Andreas Schultz <aschultz@cs.uni-magdeburg.de>
Student of computer science

"In accordance with plans for Linux OS world domination
      infiltration of governments is vital (:-))."









-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.



Home | Main Index | Thread Index