> > by zero, the 2.1.126 time code survived this quick 'time travel' without
> > problems. Apart from processes getting killed during wraparound, there is
> > no big problem, is there?
>
> Im losing the entire tty subsystem for good when this occurs
wondering which bug this is, stuck timers or p->timeout irregularities.
(the tty layer depends quite much upon p->timeout semantics) Why the later
one means a probably too big change for 2.2, stuck timers should not
happen. (neither should network connection get lost)
-- mingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/