Re: [Line6linux-user] line6linux problem with pod xt live

[Mariusz K. <mk...@la...>]

On Tue, Jan 08, 2013 at 09:21:49PM +0100, Markus Grabner wrote:
> In the meantime, you could try to find out the minimum values for the startup 
> delays (POD_STARTUP_DELAY[1|2] in pod.h) such that the driver works on your 
> system. The first value is the initial delay after the device is connected, 
> the second value is the delay between the following initialization steps. 
> Since we are currently touching the code, we should use the chance to make 
> device initialization faster if possible.

Ok so this is how I tested it:

1. <change pod.h> && make
2. <try to play some samples via POD alsa interface>
3. while true; do sudo insmod line6usb.ko; sleep 4; sudo rmmod line6usb; done

And that's left for a few miutes to see if anything blows up.

D1     D2
1000 + 100 -> works ok
100 + 50 -> works ok
50 + 10 -> oops on insmod from time to time
0 + 20 -> oops on insmod
0 + 0 -> sometimes works, sometimes oops

Tests with values of D1 below 100 produce lots of additional communication until firmware version request arrives.
That is not seen for values above 100 but maybe certain combination
of D1 + D2 triggers that additional messages.

So 100 + 50 seems reasonable.

BTW. I think I found another bug ... this is minor but probably should
get fixed. If you rmmod before driver finishes initialisation it
is likely to get oops.

Try something like this:

# while true; do insmod line6usb.ko; sleep 0.1; rmmod line6usb; sleep 1; done

I tested something like 0.1 to 5 seconds values of the first sleep.

Regards,
-- 
Mariusz Kozlowski