On Fri, 12 Jul 2002, [EMAIL PROTECTED] said: > John, > > I've missed the first part of the problem. Which binary are > you trying to run that results in the segfault ?
It seems to be dhclient. Some of the details of my config are: Server: Asus P5a mobo, w/ AMD K6-II 500Mhz uP, Realtek 8139 NIC, running SuSE 7.3 I've tried various kernels on the server: 2.4.10, 2.2.20, and 2.2.21 as well as 2.4.9 and 2.2.20 on the client, all with the same result. During the early part of the client boot process the screen status msgs are: Searching for server (DHCP) ... ... Me: 192.168.1.31, Server: 192.168.1.23 [snip] Loading 192.168.1.23:/lts/vmlinuz-2.4.9-ltsp-lpp-6 ALERT: got a fragmented packet - reconfigure your server ALERT: got a fragmented packet - reconfigure your server ALERT: got a fragmented packet - reconfigure your server ALERT: got a fragmented packet - reconfigure your server ..(NBI) ... [loads kernel] . . [from here, everything seems normal until dhclient is called again] . . Running /linuxrc mounting /proc linuxrc: Installing 8139too modprobe 8139too /sbin/insmod /lib/modules/2.4.9 ... /8139too.o Using /lib/modules/2.4.9 ... /8139too.o . . . Running dhclient ----------------- the following is on 1 line ------------------------- eth0: Setting 100mbps full-duplex based on autonegotiated partner ability 45e1. ---------------------------------------------------------------------- Segmentation fault Internet Software Consortium DHCP Client 2.0pl5 Copyright, etc ..... . . . Listening on LPF/eth0/00:e0:7d:d1:d5:f8 Sending on LPF/eth0/00:e0:7d:d1:d5:f8 Sending on Socket/fallback/fallback-net DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 DHCPOFFER from 192.168.1.23 DHCPOFFER from 192.168.1.23 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.23 ERROR! dhclient failed! Kernel panic: Attempted to kill init! ---------------------------------------------------------------- John Karns [EMAIL PROTECTED] > > On Tue, 9 Jul 2002, John Karns said: > > > > > That's the part I wasn't sure about. Actually, I was thinking that the DC > > > perhaps was getting the dhclient binary which resides on the server and > > > executing it from within the LTSP environment, which uses a different set > > > of libraries than those which the binary was compiled under. I wasn't > > > questioning the internal consistencies of LTSP. > > > > > > It does indeed seem to be hardware related, but as far as I can tell, the > > > mobo (ASUS P5A) is to blame. I've swapped the entire client machine (with > > > the same mobo) as well as the hub and patch cables with the same problem. > > > Due to the intermittent nature it's difficult to say with real certainty, > > > but the problem appears to occur only when the P5A has an AGP card > > > installed. I tried two different AGP cards - a generic card employing a > > > Trident Blade3D chip, and an ATI Rage Pro. The problem disappears when I > > > replace the AGP card with an ISA video card. > > > > > > I am declaring the test a success though, because I won't be using the > > > ASUS P5A machines as clients for the main part of the project. Although > > > it's still disappointing because I do have a few of the P5A which I was > > > thinking I could use as DC's later on. > > > > Well I'm still grappling with this problem here. I've swapped absolutely > > everything, including making the former server machine the DC and > > vice-versa with the former client. Still getting a segfault. I don't > > think that the ASUS P5A mobo was / is at fault. > > > > Since the beginning, the 1st one or two boots are successful - sometimes > > up to 5 or so, other times it segfaults on the 2nd boot. I've tried > > both kernels 2.4.9 and 2.4.18 from the LTSP kernel tgz. > > > > I'm thinking that the problem lies on the server side, as once I had my > > laptop also booting from floppy as a DC to have 2 DC's - and after the > > problem ocurred, neither DC was able to boot due a segfault. > > > > I'm running out of ideas. Any hints on how to debug this? I've DL'd a > > busybox tar file and had the idea to compile it myself - that may be my > > next step. I'll have another look through the LTSP docs to see if there's > > info on building from BB source - any tips regarding that much > > appreciated. > > > > One other point is that the machine I'm testing as a client has an > > integrated Trident Blade3D chip. When there is a successful boot of the > > DC with runlevel 5, the X window manager fails to start and the screen > > shows the large X on the monochrome "checkered" background. When I had > > the client and server machines reversed, the Blade3D AGP card in the ASUS > > worked fine after successful boots. > > > > Thanks > > > > ---------------------------------------------------------------- > > John Karns [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________________________________ 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.openprojects.net
