public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Cromie <jim.cromie@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
	Adrian Bunk <bunk@stusta.de>
Subject: Re: 2.6.17-rc4-mm1 nfsroot build err, looks related to klibc
Date: Wed, 17 May 2006 12:15:16 -0600	[thread overview]
Message-ID: <446B6834.2020909@gmail.com> (raw)
In-Reply-To: <446B5BC7.7080105@zytor.com>

H. Peter Anvin wrote:
> Jim Cromie wrote:
>> H. Peter Anvin wrote:
>>> Jim Cromie wrote:
>>>>>
>>>> Ok, it built clean, but broke on boot.
>>>>
>>>
>>> What does the full command line look like?
>>>
>>>     -hpa
>>>
>> I presume you mean the kernel boot-line, since last post included the 
>> 'Running ipconfig'
>>
>> Ive been banging at the kernel with permutations of the following 
>> pxelinux stanza.
>>
>> LABEL   I 2.6.17-rc4-mm1-sk
>>  MENU LABEL    ^i.  2.6.17-rc4-mm1-sk
>>  KERNEL        vmlinuz-2.6.17-rc4-mm1-sk
>>  APPEND        console=ttyS0,115200n81 root=/dev/nfs 
>> nfsroot=/nfshost/truck 
>> ip=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 
>> panic=5
>>
>> I think the problem lies with picking up a decent 'rootpath', since that
>> part of the output is always empty, for all variations tried so far..
>>
>
> Okay, this is probably a result of specifying the NFS server in the 
> ip= option and the nfsroot not having a server.  I will try to debug 
> this and straighten it out.
>
ok - that may need attention, but its also my misunderstanding of the 
rootpath field;
which describes only what it got from dhcp, I was looking for the 
cmd-line arg
to show up there also.  the 'complete' threw me.

Anyway, I passed it in via dhcp.conf, so I now get this, (and 
command-line override)

IP-Config: eth0 guessed nameserver address 192.168.42.1
IP-Config: eth0 complete (from 192.168.42.1):
 address: 192.168.42.100   broadcast: 192.168.42.255   netmask: 
255.255.255.0
 gateway: 0.0.0.0          dns0     : 192.168.42.1     dns1   : 0.0.0.0
 rootserver: 192.168.42.1 rootpath: /nfshost/truck
eth0: state = 4
kinit: do_mounts
kinit: name_to_dev_t(/dev/nfs) = dev(0,255)
kinit: root_dev = dev(0,255)
nfsroot=/nfshost/truck overrides boot server bootpath /nfshost/truck
NFS-Root: mo[   22.660000] Kernel panic - not syncing: Attempted to kill 
init!
unting ip= on /r[   22.668000]  oot with options<0>Rebooting in 5 
seconds.. 'none'
kinit: need a server
Checking for init: /sbin/init
Checking for init: /bin/init


Ive added this, but havent yet seen its output :-/


[jimc@harpo kinit]$ diff -u  nfsmount/main.c~ nfsmount/main.c
--- nfsmount/main.c~    2006-05-15 10:03:56.000000000 -0600
+++ nfsmount/main.c     2006-05-17 11:39:59.000000000 -0600
@@ -247,6 +247,10 @@
                return 1;
 #endif

+       fprintf(stderr, "nfs_mount:"
+               "rem_name %s, hostname %s, server %x, rem_path %s, path 
%s\n",
+               rem_name, hostname, server, rem_path, path);
+
        if (nfs_mount(rem_name, hostname, server, rem_path, path,
                      &mount_data) != 0)
                return 1;





>     -hpa
>

thanks

  reply	other threads:[~2006-05-17 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16  1:36 2.6.17-rc4-mm1 nfsroot build err, looks related to klibc Jim Cromie
2006-05-16  4:11 ` H. Peter Anvin
2006-05-16 10:18   ` Adrian Bunk
2006-05-16 19:04     ` H. Peter Anvin
2006-05-17  7:12       ` Jim Cromie
2006-05-17 16:14         ` H. Peter Anvin
2006-05-17 17:17           ` Jim Cromie
2006-05-17 17:22             ` H. Peter Anvin
2006-05-17 18:15               ` Jim Cromie [this message]
2006-05-17 23:25               ` Jim Cromie
2006-05-16  5:47 ` Jim Cromie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=446B6834.2020909@gmail.com \
    --to=jim.cromie@gmail.com \
    --cc=bunk@stusta.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox