Dmitriy Geels wrote: > 2009/3/3 Dmitriy Geels <dmitriy.geels@xxxxxxxxx>: >>> What about running fftest two times in succession, or just ffmvforce two >>> times in succession, does it trigger the problem? >> Tried already. No problem. Same with ffmvforce. > I was wrong: running ffmvforce twice leads to stuck device. There > should be some initialization/deinitialization problem in it. > >>> Also, try removing some effects from fftest one-by-one, and see if the >>> problem is still triggered. >> Will try this later, this evening. > ffmvforce gets stuck after any effect played in fftest. Does this mean it does not get stuck if you start fftest but do not play any effects? > Here is it's source, may be you'll see the problem: > http://paste.org.ru/index.pl?s8x9x5 Provide the kernel log again, this time with debug=2 set for hid module and having run "fftest" with only one effect and then "ffmvforce". -- Anssi Hannula -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
