On Sun, Feb 22, 2009 at 8:45 PM, Jonathan Isom <jeisom@xxxxxxxxx> wrote: > On Sun, Feb 22, 2009 at 2:43 PM, CityK <cityk@xxxxxxxxxx> wrote: >> Jonathan Isom wrote: >>> Hi >>> I was looking over my logs and I'm wondering is >>> "nxt200x: Timeout waiting for nxt2004 to init" >>> common HI all I am not sure if this is actually related to my lockups, however I think I may have figured out something. If I boot my system with clocksource equal to hpet it occurs right after boot(~8secs in), but if I set it to jiffies I don't see it(note early testing, may still end up occuring). In nxt2004_microcontroller_init there is a msleep(10) and I'm wondering if 200 msec(loop) is long enough. Any Thoughts? Jonathan >> No its not common >> >>> or is this womething I need to worry about. I got one shortly before a >>> lockup(No backtrace). Nothing was doing other than dvbstreamer sitting idle. >>> I'll provide further logs if it should be needed. I would think that >>> It would need to >>> only be initialize at module load. Am I wrong in this thinking? >>> >>> in kernel drivers 2.6.28.4 > Hi > Looking at the logs I found that there was a backtrace. However I believe it > is related to dvbstreamer and the kworld cards. I cycle thru the channels to > download epg info. The previous crash I forgot that I was running the script > to cycle them and export the xmltv data. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
