Re: SIOCSIFBRDADDR: Can't assign... (2.1.109ac1)

Adam Sulmicki (adam@cfar.UMD.EDU)
Fri, 17 Jul 1998 23:37:02 -0400

Claus Hindsgaul Hansen writes:
->Hello all you donators of Linux!
->
->I have some network-related problems with my Redhat5.1 system, kernel
->2.1.109ac1. I have a 3c590 net-card on a 486DX100, SiS8859 chipset.
->
->I do not know, if the flaws are in the net-card, TCP/IP or NFS client
->drivers (or something else).
->
->I did not know, which maintainer to bother - so why not bother all of you
->on the list :)
->
->
->BOOTING:
->-------
->My 3c590 card is detected nicely (correct media, irq and io).
->
->I get these messages during the boot-sequence between kmod is started
->and the bootp request is sent:
->
->SIOCSIFBREDADDR: Cannot assign requested address
->SIOCSIFNETMASK: Cannot assign requested address
->
->Then the bootp-request is sent, but fails to get a response (this works
->with 2.0.xx). Network access is available using stored values though.
->(I haven't even experienced the 1-3 minute lockups, others have reported
->with the 3c590 at any time)

AFAIK, it is result of IP-PNP being enabled. It is not realy clear from
documentation, however if you read source code you will see that if you
append

ip=::::::off

to turn off rarp and boopt, but it sill will look at the values
for ip et all at the command line. and

ip=off

to turn off PNP at all. Why does it fail for bootp? Did you remember to
enable it in kernel? Did you try explitly enable it as :

ip=::::::bootp

->NFS-MOUNTING
->------------
->Mounting NFS-dirs takes about 17 seconds. After this, they are useable..
->While mounting, I get some error messages. It seems, some kind of lock is
->left over, when multiple mount-operations are done. These are the errors
->from mounting two NFS-dirs:
->
->[pbk2906@qake pbk2906]$ mount /pbk2906/
->portmap: RPC call returned error 111
->RPC: task of released request still queued!
->RPC: (task is on xprt_pending)
->portmap: RPC call returned error 111
->RPC: task of released request still queued!
->RPC: (task is on xprt_pending)
->lockd_up: makesock failed, error=-111
->portmap: RPC call returned error 111
->RPC: task of released request still queued!
->RPC: (task is on xprt_pending)
->[pbk2906@qake pbk2906]$ mount /lillebror/
->lockd_up: no pid, 2 users??
->portmap: RPC call returned error 111
->RPC: task of released request still queued!
->RPC: (task is on xprt_pending)
->portmap: RPC call returned error 111
->RPC: task of released request still queued!
->RPC: (task is on xprt_pending)
->lockd_up: makesock failed, error=-111
->portmap: RPC call returned error 111
->RPC: task of released request still queued!
->RPC: (task is on xprt_pending)
->[pbk2906@qake pbk2906]$
->
->This happens with both rw and ro shares.
->Mounting and unmounting more drives shows, that the "no pid, <x> users??"
->is always so <x> equals the number of current NFS-mounts.

If you use 2.1.x series kernels make sure you have nfs/rpc daemons up to date
on both server and client side. I think it is the reason

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html