Edward Pilatowicz wrote:
> well presumably select() isn't telling X that there's data to read since
> theres no underlying device to produce data.
>
> so when you tested the fix for 6844148, how did the X server get
> notified? did select() return and indicate there was data?
As noted in 6914848 (which was closed as dup of 6844148, but is where the
explanation of my testing was put):
truss & pfiles shows it's in a loop getting signaled by poll
that there's something to read on the fd that had opened
/devices/pci at 0,0/pci108e,5354 at 1d,1/hub at 1/mouse at 2:mouse but reads
from that just return ENODEV, which causes it to just go on and
try again later, infinitely.
--
-Alan Coopersmith- alan.coopersmith at oracle.com
Oracle Solaris Platform Engineering: X Window System
