Re: gpilotd, kernel crashes, and having to reboot



> Is anyone else seeing issues like this, and does anyone know where the
> fault lies and what can be done to fix this horribly unsocial behavior?

	If the kernel crashes, the kernel is at fault. The kernel should not
present a condition where it can just render the machine unusable, even if
some piece of bad code in userland threw it a bad return value or some other
value.

	insmod your visor driver with 'insmod visor debug=1' and send those
(VERY verbose) kernel logs to Greg Kroah (greg kroah com), and see if he can
figure out why it is happening. If you're running hotplug, make sure your
visor driver is getting inserted with 'debug=1' at dynamic load time.

	I know this used to happen with previous kernels (.20 and earlier)
but it was fixed in .21 and later. It might help your debugging if you
changed your syslog output to put kernel errors into their own separate
logfile (kern.* /var/log/kern.log or something like that).

	Good luck.

d.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]