Good try, but no banana: I wasn't using raw IO! (I use devfs
which didn't support raw devices last time I looked). I experimented
a bit with raw io, your sleep idea and other things though:
devfs vs no devfs : no difference (problem present)
no raw io (devfs) + sleep : problem present
raw io (no devfs) : problem present, but less frequent (one time in three)
raw io (no devfs) + sleep : problem not present (tried three times)
I'm not sure whether the fact that xine didn't get stuck with raw io + sleep
means that it will never get stuck, or that I didn't try long enough. I
rebooted the machine after every test since if I run xine several times
without rebooting, I get a pattern like this:
problem
problem
...
problem
correct
correct
correct...
So rebooting seemed like the best way to reset everything to the
same state for each test. But it means that it takes time to run
each test, which is why there are not so many...
Thanks for looking into this,
Duncan.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/