On Sunday 10 August 2003 15:00, Juri Haberland wrote: > Juri Haberland wrote: > > Ok, I'll enable debugging then. > > So I did. And it did nothing good :( > > The first run ended in a locked up frontend after VDR started it's EPG > scan without any lockup-message in the logs: > > [loading the driver and starting vdr, then I switched to a couple of > channels:] > Aug 9 12:06:41 glotze kernel: sp8870_set_frontend: Delay (40 usec) > Aug 9 12:06:44 glotze vdr[32402]: switching to channel 3 > Aug 9 12:06:44 glotze kernel: sp8870_set_frontend: Delay (440 usec) > Aug 9 12:06:47 glotze vdr[32402]: switching to channel 4 > Aug 9 12:06:47 glotze kernel: sp8870_set_frontend: Delay (20 usec) > > [and after five hours the EPG scan kicks in:] > > Aug 9 17:07:07 glotze kernel: sp8870_set_frontend: Delay (20 usec) > Aug 9 17:07:28 glotze kernel: sp8870_set_frontend: Delay (50 usec) > Aug 9 17:07:49 glotze kernel: sp8870_set_frontend: Delay (50 usec) > ... > Aug 9 17:43:35 glotze kernel: sp8870_set_frontend: Delay (20 usec) > Aug 9 17:43:56 glotze kernel: sp8870_set_frontend: Delay (40 usec) > Aug 9 17:44:17 glotze kernel: sp8870_set_frontend: Delay (50 usec) > Aug 9 17:44:59 glotze kernel: sp8870_set_frontend: firmware lockup! > Aug 9 17:44:59 glotze kernel: sp8870_set_frontend: Delay (10 usec) > Aug 9 17:44:59 glotze kernel: sp8870_set_frontend: firmware lockup > recovered!
So far it looks ok to me, but then it starts: > Aug 9 17:45:01 glotze kernel: sp8870_set_frontend: Delay (0 usec) > Aug 9 17:45:32 glotze last message repeated 108 times This I don't understand. It seems like the EPG-scan tries to change channels very quickly. A 108 times in 31 seconds? > Aug 9 17:45:40 glotze last message repeated 44 times > ... same as above and it keeps on going on like that. > and so on for hours, until I came back in, tried to switch to different > channels and had to reload the driver. > Unfortunatly I forgot to change the script which reloads the driver so > the alps_tdlb7.o loaded without debug=1. > But after another five hours VDR's EPG-scan kicked in once again and I > got this in my logs: > > Aug 10 05:27:24 glotze kernel: sp8870_set_frontend: firmware > crash!!!!sp8870_set_frontend: firmware crash!!!!sp8870_set_frontend: > firmware crash!!!!sp8870_set_front > end: firmware crash!!!!sp8870_set_frontend: firmware > crash!!!!sp8870_set_frontend: firmware crash!!!!sp8870_set_frontend: > firmware crash!!!!sp8870_set_frontend: fir > mware crash!!!!sp8870_set_frontend: firmware > crash!!!!sp8870_set_frontend: firmware crash!!!!sp8870_set_frontend: > firmware crash!!!!sp8870_set_frontend: firmware cr > ash!!!!sp8870_set_frontend: firmware crash!!!!sp8870_set_frontend: > firmware crash!!!!sp8870_set_frontend: firmware > crash!!!!sp8870_set_frontend: firmware crash!!!!s > p8870_set_frontend: firmware crash!!!!sp8870_set_frontend: firmware > crash!!!!sp8870_set_frontend: firmware crash!!!!sp8870_set_frontend: > firmware crash!!!!sp8870_se > t_frontend: firmware crash!!!!sp8870_set_frontend: firmware > crash!!!!sp8870_set_frontend: firmware crash!!!!sp8870_set_frontend: > firmware crash!!!!sp8870_set_fronte > nd: firmware crash!!!!sp8870_set_frontend: here we have a detected firmware crash. The message repeats with every attemp to set frontend parameters, this is also normal - except that a crash shouldn't happen at all of course ;-). Seems that I forgot a "\n" in the printk that's why the messages looks strange. So the problem is the EPG-scan, did you had problems with it before? I mean without the patch? I normally always have EPG-scan disabled. Will enable it and see what will happen. Juergen -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
