Is it possible those thin clients don't have enough RAM? Do the "spare parts" thin clients use identical hardware? Any difference in BIOS settings between the good and bad units?
-Rob On Tue, Jun 23, 2009 at 03:47:06PM +0300, Eero Lemmelä wrote: > Hi there, > > We have a bunch of Fujitsu-Siemens Futro A255 thin clients[1] which wont > play nicely with our LTSP-5 system. We sent a problem report to > Fujitsu-Siemens and got the expected answer - they wont help us because > we're not running eLUX NG or Windows CE.net operating system... Hopefully > someone here can help us. > > Here's the <problem_report>: > > We are running an LTSP-5 system on Debian 5.0 (Lenny) using KDE as the > window manager. Only notable change we have made to the default setup > provided by Debian is that we are using XDMCP instead of SSH. > > Problem with our Futro A255 thin clients is that they start to freeze > randomly one by one when they are under use. By freezing I mean that the > client becomes totally unresponsive and the display freezes. > > Sometimes the first freezing occurs within minutes after log in and > sometimes it takes ~10 minutes or so. Some of them might last for an hour > or two but usually eventually they all end up dead. In the meanwhile > there are four clients that are built from spare parts that have been > running smoothly for 27 days now. > > Sometimes a client writes an occasional "nfs: server <our_server_ip> not > responding, still trying" appears to syslog moments before and sometimes > - very rarely though - a few minutes after the client freezes. Sometimes > there is also a "NETDEV WATCHDOG: eth0: transmit timed out" message which > might or might not be related to the problem. > > We have been doing a lot of testing and we think that the ethernet driver > (r8169) might be the culprit. We have tried to use different kernel > versions (2.6.26-1-486 and 2.6.26-2-486 provided by Debian and 2.6.29.4 > from kernel.org) with the in-kernel driver and the driver from > Fujitsu-Siemens website. Other tests we've done include but are not > limited to disabling ACPI, APM and apic, upgrading X.org display drivers, > using different swithes between the server and the clients, etc... > > </problem_report> > > The provided eLux NG operating system runs on Linux kernel 2.4.32 and > uses r1000 -module as the ethernet driver. Source for r1000 can be > downloaded from the Fujitsu-Siemens website and AFAIK it has been merged > with the r8169 driver which comes with the stock kernel. Anyway the r1000 > doesn't work with a 2.6 kernel. > > We propably wont have the chance to do any more tests with the clients > before July, but any ideas that we could try then are welcome. > > 1. http://ts.fujitsu.com/products/deskbound/thin_clients/futro_a.html > > > Regards, > > Eero Lemmelä > > ------------------------------------------------------------------------------ > Are you an open source citizen? Join us for the Open Source Bridge conference! > Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. > Need another reason to go? 24-hour hacker lounge. Register today! > http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org > _____________________________________________________________________ > 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 ------------------------------------------------------------------------------ _____________________________________________________________________ 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
