[linux-dvb] Re: Skystar2 i2c lockup

["Augusto Cardoso" <augusto@carhil.net>]

Hi!

Thanks for the info.

Does it happen every time?
I have multiple cards in my system and I always load the mt312 and the stv0299. The mt312 probe all cards and finds the right ones. Then the stv0299 find the other cards.
This sounds like a race condition or some other odd situation.
Since I wasn't able to reproduce yet, I'll take another look at the code.

Thanks.

	Augusto 

*********** REPLY SEPARATOR  ***********

On 12/9/2003 at 8:18 AM Niklas Peinecke wrote:

>Augusto Cardoso wrote:
>> Hi!
>> 
>> I haven't been able to reproduce this problem.
>> Can some one that has the problem provide some information?
>> For example, order that the modules are loaded, some system information,
>what version of the driver and kernel, etc.
>> 
>
>I experienced this last week:
>
>System: K6/2 400Mhz, Skystar2 rev2.6B with FlexcopII, Suse 8.0 (with 
>losts of non-standard extensions), kernel 2.4.23, driver dvb-kernel from
>CVS
>
>I compile the driver using getlinks && make
>and then insmod.sh
>All the modules are loaded without problems (of course, because most of 
>them are unused) then skystar2 and mt312 are loaded. mt312 tries to 
>attach itself to skystar2 and hangs during initialize. Both modules are 
>marked as "used" and can therefor no more be removed.
>Nothing to see on dmesg.
>
>Things work without problems when mt312 is left out.
>
>Niklas
>
>
>
>-- 
>Info:
>To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.





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