From: Jim Cromie <jim.cromie@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Adrian Bunk <bunk@stusta.de>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.17-rc4-mm1 nfsroot build err, looks related to klibc
Date: Wed, 17 May 2006 01:12:15 -0600 [thread overview]
Message-ID: <446ACCCF.1030406@gmail.com> (raw)
In-Reply-To: <446A2243.6050109@zytor.com>
H. Peter Anvin wrote:
> Adrian Bunk wrote:
>> On Mon, May 15, 2006 at 09:11:15PM -0700, H. Peter Anvin wrote:
>>> Jim Cromie wrote:
>>>> Im getting nfsroot build error on 2 configs, both carried forward
>>> >from good rc4 and from rc3-mm1 builds.
>>>> turning off nfsroot fixes the err.
>>>>
>>> Could you throw me your configs, so I can try to reproduce it here?
>>
>> The problem is:
>>
>> CONFIG_IP_PNP=y
>> CONFIG_NFS_FS=y
>> CONFIG_ROOT_NFS=y
>>
>> A (compile-only) .config exhibiting this error is attached.
>>
>
> Yeah, OK, problem recovered; total thinko on my part -- I forgot to
> remove the in-kernel nfsroot code. Just setting CONFIG_ROOT_NFS=n
> will work just fine; right now kinit doesn't depend on the
> configuration (another buglet for my list), so if you set
> CONFIG_ROOT_NFS=n the kernel will compile *and* nfsroot should still
> work.
>
> -hpa
>
Ok, it built clean, but broke on boot.
Running ipconfig
IP-Config: argc == 3
argv[1]: '-n'
argv[2]:
'nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0'
IP-Config: parse_device: "nfsaddrs=192.168.4[ 58.550017] eth0: DSPCFG
accepted after 0 usec.
[ 58.555452] eth0: link up.
[ 58.558221] eth0: Setting full-duplex based on negotiated link
capability.
2.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0"
IP-Config: opt #0: '192.168.42.100'
IP-Config: opt #1: '192.168.42.1'
IP-Config: opt #2: '192.168.42.1'
IP-Config: opt #3: '255.255.255.0'
IP-Config: opt #4: 'soekris'
IP-Config: opt #5: 'eth0'
IP-Config: eth0 hardware address 00:00:24:c2:46:c8 mtu 1500
IP-Config: eth0 guessed broadcast address 192.168.42.255
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: 192.168.42.1 [ 58.616298] Kernel panic - not syncing:
Attempted to kill init!
dns0 : 192.[ 58.622750] 168.42.1 dns<0>Rebooting in 5
seconds..1 : 0.0.0.0
host : soekris
rootserver: 192.168.42.1 rootpath:
kinit: do_mounts
kinit: name_to_dev_t(/dev/nfs) = dev(0,255)
kinit: root_dev = dev(0,255)
NFS-Root: mounting console=ttyS0,115200n81 on /root with options 'none'
kinit: need a server
Checking for init: /sbin/init
Checking for init: /bin/init
Checking for init: /etc/init
Checking for init: /bin/sh
kinit: init not found!
POST: 0123456789bcefghipajklnopq,,,tvwxy
next prev parent reply other threads:[~2006-05-17 7:12 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 [this message]
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
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=446ACCCF.1030406@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.