While it's nice to supposedly have narowed this down to the SMP cleanup,
that doesn't make those of us who are running single processor machines
very cofident that the bug's been found.  Here's my guess: there may be
something interupt driven related to the SMP stuff, but there's also
something wrong with moused, as at least two people (one being myself)
have said that going to direct reading of the device eliminted their
problem.  I just didn't want the legitimate bug reports from single
processor users to be lost in the search for a SMP cause.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to