[K12OSN] Re: boot hang reproduced, Was: Another small K12LTSP 4.1.0 beta bug

jam at mcquil.com jam at mcquil.com
Sun Jul 18 15:13:40 UTC 2004


Eric,

Hmm, it seems that it is trying to run the /linuxrc script twice, and 
failing the 2nd time.

I'll look into it here too.

Also, i've got some updates for you, i'll send a separate email in a few 
minutes.

Jim.



On Sun, 18 Jul 2004, Eric Harrison wrote:

> On Sun, 18 Jul 2004 jam at mcquil.com wrote:
> 
> >I've had a couple of reports of this problem, but i've not yet been able 
> >to reproduce it myself.
> 
> Jim, I'm able to repoduce this on my laptop.
> 
> PXE boot works fine. BOOTP via an Etherboot iso image fails with
> the "/bin/dhcpdcd: already running" error. Looks like a NFS or
> init issue. Will dig in further.
> 
> 
> Here is the full text (written by hand, beware of typos ;-)
> 
> 
> Running dhcpcd on port 67
> Mounting root filesystem: /opt/ltps/i386 from: 192.168.0.254
> Doing the pivot_root
> Mounting the devfs filesystem
> Running /sbin/init
> Usage: init 0123456SoQaAaBbCcUu
> VSF: Mounted root (ext2 filesystem)
> Trying to move old root to /initrd ... failed
> Unmonting old root
> Trying to free ramdisk memory .. failed
> Mounted devfs on /dev
> Freeing unused kernel memory: 88k freed
> ============================================================
> Running /linuxrc
> Mounting /proc
> linuxrc: Installing e100 driver
> modprobe e100
> Runnng dhcpcd on port 67
> 
> ****  /bin/dhcpcd: already running
> ****  /bin/dhcpcd: if not then delete /etc/dhcpc/dhcpcd-eth0.pid file
> 
> 
> -Eric
> 
> >It is correct that there is a 2nd dhcp request.  that is because the 
> >bootrom doesn't pass the information to the kernel, so once the Linux 
> >kernel is running, the workstation needs to make a dhcp request of its 
> >own.
> >
> >Are you booting with PXE or Etherboot ?
> >
> >Jim McQuillan
> >jam at Ltsp.org
> >
> >
> >
> >On Sun, 18 Jul 2004, Jack wrote:
> >
> >> Just installed LTSP 410 and I keep running into a problem with all 3 of
> >> my terminals not booting.  They boot about halfway then fail.
> >> 
> >> All my terminals are getting kernel panics.  All 3 fail with identical
> >> errors, like so:
> >> --------------------------------
> >> Running /linuxrc
> >> Mounting /proc
> >> linuxrc: Installing e100 driver
> >> modprobe e100
> >> Running dhcpcd on port 67
> >> 
> >> **** /bin/dhcpdcd: already running
> >> **** /bin/dhcpcd: if not then delete /etc/dhcpc/dhcpcd-eth0.pid file
> >> 
> >> ERROR! dhcpcd failed!
> >> 
> >> Kernel panic: Attempted to kill init!
> >> <3>e100: eth0 NIC Link is Up 100 Mbps Full Duplex
> >> --------------------------------
> >> 
> >> On the server side I get this in the messages log:
> >> 
> >> --------------------------------
> >> Jul 18 03:13:30 tserver dhcpd: DHCPDISCOVER from 00:a0:c9:75:ca:27 via
> >> eth0
> >> Jul 18 03:13:31 tserver dhcpd: DHCPOFFER on 192.168.0.251 to
> >> 00:a0:c9:75:ca:27 via eth0
> >> Jul 18 03:13:31 tserver dhcpd: DHCPREQUEST for 192.168.0.251
> >> (192.168.0.254) from 00:a0:c9:75:ca:27 via eth0
> >> Jul 18 03:13:31 tserver dhcpd: DHCPACK on 192.168.0.251 to
> >> 00:a0:c9:75:ca:27 via eth0
> >> Jul 18 03:13:58 tserver dhcpd: DHCPDISCOVER from 00:a0:c9:75:ca:27 via
> >> eth0
> >> Jul 18 03:13:59 tserver dhcpd: DHCPOFFER on 192.168.0.252 to
> >> 00:a0:c9:75:ca:27 via eth0
> >> Jul 18 03:13:59 tserver dhcpd: DHCPREQUEST for 192.168.0.252
> >> (192.168.0.254) from 00:a0:c9:75:ca:27 via eth0
> >> Jul 18 03:13:59 tserver dhcpd: DHCPACK on 192.168.0.252 to
> >> 00:a0:c9:75:ca:27 via eth0
> >> Jul 18 03:13:59 tserver rpc.mountd: authenticated mount request from
> >> ws252.ltsp:657 for /opt/ltsp/i386 (/opt/ltsp/i386)
> >> --------------------------------
> >> 
> >> It looks to me like the client(terminal) is trying to get another IP for
> >> some reason.  All terminals are using e100 NICs (Intel e100).  I suspect
> >> this may be a problem with the Intel driver.  I'll have to try another
> >> NIC but right now all three of my terminals are using Intel 100's and I
> >> don't feel like ripping them apart at this moment.  Otherwise the server
> >> is looks and runs great.  Thanks again guys for the great work.
> >> 
> >> Jack
> >> 
> >> 
> >> On Sun, 2004-07-18 at 02:00, jam at mcquil.com wrote:
> >> > Eric,
> >> > 
> >> > Ok, I can take a hint :)
> >> > 
> >> > I've incorporated the updated build_x4_cfg script.
> >> > 
> >> > But, isn't there supposed to be a script that loads the usb modules too?
> >> > 
> >> > Jim.
> >> > 
> >> > 
> >> > On Sat, 17 Jul 2004, Eric Harrison wrote:
> >> > 
> >> > > 
> >> > > After more pounding on the K12LTSP 4.1.0 beta 1, I found another
> >> > > small bug: USB mice do not automagically work like they did in
> >> > > K12LTSP 4.0.0.
> >> > > 
> >> > > I missed one of the patches I apply (and keep sending to Jim ;-)
> >> > > that configure X to support both PS/2 & USB mice from the same
> >> > > config.
> >> > > 
> >> > > If you have K12LTSP 4.1.0 beta 1 installed & are using USB mice,
> >> > > the corrected file is attached. Save this as:
> >> > > 
> >> > > 	/opt/ltsp/i386/etc/build_x4_cfg
> >> > > 
> >> > > then make it executable:
> >> > > 
> >> > > 	chmod a+x /opt/ltsp/i386/etc/build_x4_cfg
> >> > > 
> >> > > and then all will be well.
> >> > > 
> >> > > 
> >> > > I'll build new LTSP packages & resend the patch off to Jim...
> >> > > 
> >> > > -Eric
> >> > > 
> 





More information about the K12OSN mailing list