12th attempt at posting (previous ones have bounced) I can induce a crash (total - kernel goes straight into cold reboot) on my win4lin 686M2 systems by pinging a plip interface (either from the parent machine or from the laptop on the other end of the link). The 486-laptop is stable though. A few checks seem to show that the effect is specific to version 3.0.x, and (apparently) to win4lin-kernels _compiled_ for a 686M2. I've tried some 2.2.13, 2.2.17 & 2.2.18 kernels. Those which are compiled eg for a 486, or without w4l support are stable when the plip interface is pinged. And I've reverted to w4l 5.1.0 and that also returns me to a stable system. Often the kernel goes down without trace, but occasionally, eg if pinging from the laptop as the kernel boots, I get the dreaded 'Aiee killing interrupt handler kernel panic: attempted to kill the idle task in interrupt handler - not syncing' then silence (and a long reboot to rescue the 10Gb disk!) Anyone seen anything similar please? (It's a 100% guaranteed bug of recent arrival - I reckon.) Bob -- robert w hall _______________________________________________ Win4Lin-users mailing list [EMAIL PROTECTED] https://lists.netraverse.com/mailman/listinfo/win4lin-users
