On Mon, 23 Apr 2012, Henrique de Moraes Holschuh wrote: > On Sun, 22 Apr 2012, Roger Leigh wrote: > > I'm not sure that this is definitely a sysvinit issue. The mouse > > and keyboard are entirely functional right up until X11 starts up. > > This may well be a red herring, but you're all using the latest 3.2 > kernel, aren't you? A Debian user went straight to LKML with an udev > issue related to the later 3.2 kernels (which was a _lot_ worse than > just input devices disappearing, I think. I will have to hunt down that > message).
Hmm, found it and it is a very different issue, related to udevadm settle and event filtering. It is unlikely to be related to this problem. > It is not impossible that an interaction of the latest sysvinit with the > later 3.2 kernels is causing problems if we changed _anything_ that has > direct interaction with the kernel (such as an ioctl, signal masks...) > in the latest sysvinit that could trigger a kernel issue. > > Did we? That's still a question worth considering. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
