Hello Juan, > Jul 12 06:39:27 star-warrior kernel: eth0: Too much work at interrupt, > IntrStatus=0x0010. > Jul 12 06:39:32 star-warrior kernel: eth0: Too much work at interrupt, > IntrStatus=0x0040. > Jul 12 06:39:42 star-warrior kernel: eth0: Too much work at interrupt, > IntrStatus=0x0040.
> Actually we discconect the last connected ws but the server (a SuSE 7.2 with > 1.5 Memo) freeze and dont work again, the only solution its to reboot the > system , breaking the service, we try to restar network, route, dhcp, but > nothing work, only the system reboot. > Do you know wahts happening ??? > Its there a solution ?? I actually bought a new network card for my home server when it issued these messages. The old via-rhine board obviously had gone bogus - after just a long time of reliable work. What can I expect for 7,5 EUR? :-) You could investigate if the nic shares interrupt with another PCI device (USB controllers often share interrupts with near-to-anything as modern boards have lots of them). Try to move those interrupts around - that *could* solve it. HTH, Anselm ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
