Hali! Well, I've upgraded from the default 2.2.20 kernel to 2.4.x, and the problem disappeared. (I mean, I haven't met with it since Nov 20 last year)
So it might have been an already solved kernel 2.2.x bug (or conflict with kde2 or xfree86), sorry. Miki
