Re: [linux-dvb] Non blocking IO on dvr0 device
David Härdeman wrote: On Fri, November 9, 2007 03:33, Felix Domke wrote: Banana Banana wrote: On Nov 9, 2007 12:22 AM, Simon Hargreaves [EMAIL PROTECTED] wrote: I'm using 2.6.12-gentoo-r6 #1 SMP kernel. Try a more recent kernel? No, this is not the correct response to a bug. Of course it is when the poster's kernel is more than 2 years old (2.6.12 was released on June 17, 2005). snip I'm aware that the kernel release is somewhat ancient in terms of drivers and such. I was interested to find out if this was a known issue with a known fix. I have a number of machines with identical configurations and rolling out new kernel versions across a live system, and disrupting it's homogeneity, without knowing if it will fix the problem is something I was trying to avoid. I've started the process of doing a system wide update on one of the machines, because I realise that a lot happens between that many kernel versions, but the danger of losing a live system and having to rebuild is always there. I'll let you know if it fixes the problem. Thanks, Simon... ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Non blocking IO on dvr0 device
Simon Hargreaves wrote: David Härdeman wrote: On Fri, November 9, 2007 03:33, Felix Domke wrote: Banana Banana wrote: On Nov 9, 2007 12:22 AM, Simon Hargreaves [EMAIL PROTECTED] wrote: I'm using 2.6.12-gentoo-r6 #1 SMP kernel. Try a more recent kernel? No, this is not the correct response to a bug. Of course it is when the poster's kernel is more than 2 years old (2.6.12 was released on June 17, 2005). snip I'm aware that the kernel release is somewhat ancient in terms of drivers and such. I was interested to find out if this was a known issue with a known fix. I have a number of machines with identical configurations and rolling out new kernel versions across a live system, and disrupting it's homogeneity, without knowing if it will fix the problem is something I was trying to avoid. I've started the process of doing a system wide update on one of the machines, because I realise that a lot happens between that many kernel versions, but the danger of losing a live system and having to rebuild is always there. I'll let you know if it fixes the problem The update to the latest kernel version has broken my recording programme completely and now returns device busy. I'm using dvbtune to set up the dvr0 device for TS recording but it's now locking the device so no other program can read from it. Is this a driver level change as it used to work on the previous kernel version? Simon... ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Non blocking IO on dvr0 device
Il Friday 09 November 2007 17:37:24 Simon Hargreaves ha scritto: The update to the latest kernel version has broken my recording programme completely and now returns device busy. I'm using dvbtune to set up the dvr0 device for TS recording but it's now locking the device so no other program can read from it. Is this a driver level change as it used to work on the previous kernel version? Simon... IIRC dvbtune doesn't even touch the dvr0 device, let alone block it. BTW, for many years (and countless revisions of the drivers) dvbstream and mplayer have used the dvr0 in nonblocking mode, without the least problem; I suspect something buggy in your current tree ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Non blocking IO on dvr0 device
On Nov 9, 2007 12:22 AM, Simon Hargreaves [EMAIL PROTECTED] wrote: I'm using 2.6.12-gentoo-r6 #1 SMP kernel. Try a more recent kernel? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Non blocking IO on dvr0 device
Banana Banana wrote: On Nov 9, 2007 12:22 AM, Simon Hargreaves [EMAIL PROTECTED] wrote: I'm using 2.6.12-gentoo-r6 #1 SMP kernel. Try a more recent kernel? No, this is not the correct response to a bug. Or do you remember a bug which was present in that kernel version, and fixed later? In that case, why don't you point to the diff? If you want to hunt for the bug, then fine, do a git-bisect or a kernel diff from your version to the current version, or just try a new version. But I consider simply throwing in a please update your kernel, just because there isn't something better to say, as a bad thing. Yes, trying a new kernel is certainly a good idea, but I would think the poster did knew that before. And I would guess he has reasons to stay on that kernel, be it a customer request, a stable kernel or just the unwillingness to change something important as the kernel on a production system. This was a (perfectly fine) user question, not a developer request. His question was if there is or was a known bug regarding non-blocking IO on dvr0. If he wanted to be a kernel developer, he would probably have posted a patch fixing (or at least explaining) the issue. But he asked if there is a known issue. Not what he could do to maybe workaround that problem. Sorry, just my two cents. Back to the topic: No, i'm not aware of any leaks occuring using dvr0 recording, and we used that for quite a while on a 2.6.12 machine (until we finally backported dvb-core for other reasons). Simon, can you determine the exact moment when memory is lost, and how much it is? Is it definitely not lost when using blocking IO? Might this be an SMP bug? Felix ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
