Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 213660 - sys-apps/iproute2-2.6.23.20071016 - RTNETLINK: Invalid Argument when starting net
Summary: sys-apps/iproute2-2.6.23.20071016 - RTNETLINK: Invalid Argument when starting...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-17 08:43 UTC by Ralf Folkerts
Modified: 2008-03-29 17:25 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
/etc/conf.d/net (net,26.91 KB, text/plain)
2008-03-17 17:28 UTC, Ralf Folkerts
Details
emerge --info (knox_emerge--info.txt,3.28 KB, text/plain)
2008-03-17 17:29 UTC, Ralf Folkerts
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Folkerts 2008-03-17 08:43:30 UTC
Hi,

after Updating my Gentoo-System yesterday the Network didn't start up any longer. For each Interface there were RTNETLINK: Invalid Argument errors.

When issuing ifconfig -a all Interfaces were there and configured OK (i.e. IP Address was set); however, I was unable to get a link.

Issuing a

ifconfig eth0|eth1|lo up

brought up the Interfaces.

I then reverted my /etc/conf.d/net to use ifconfig and the System almost started up, however, lo was not up, i.e. "ping localhost" didn't work.

I added a "ifconfig lo up" at the end of the start-Function in /etc/nit.d/net.lo and then also got Loopback during start.

However, my Xen Domains didn't start -- the came up with the status "P" and then died after a while.

I then reverted to sys-apps/iproute2-2.6.22.20070710 and the System bootet fine, i.e. I re-commented the 

#modules=( "iproute2" )

and removed my "ifconfig lo up" code from /etc/init.d/net.lo and the System still came up 1a, incl. the Xen Domains.

I checked /etc/conf.d/net.examples but it was dated 01/24/08.

I also checked /var/log/portage/elog/summary.log to look if I forgot a Migration-step but didn't find any.

The System runs on Gentoo since ~2005, so probably I did forgot a Migration-Step at any time in the Past that leads to this desastrous result -- however, I have no idea where to look.

Reproducible: Always

Steps to Reproduce:
1. Emerge to the iproute2-2.6.23.20071016.ebuild
2. Restart the System
Actual Results:  
Network Interfaces are not being brought up.

Expected Results:  
The Interfaces should be brought up. When "downgrading" iproute2 Networking runs fine again.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2008-03-17 08:50:49 UTC
Attach your /etc/conf.d/net here and post emerge --info output; thanks.
Comment 2 Ralf Folkerts 2008-03-17 17:28:06 UTC
Created attachment 146399 [details]
/etc/conf.d/net
Comment 3 Ralf Folkerts 2008-03-17 17:29:14 UTC
Created attachment 146401 [details]
emerge --info

Hi,

here's my /etc/conf.d/net and the output of emerge --info. Sorry, I should at least have included the last.

Cheers,
_ralf_
Comment 4 Lorenz Kiefner 2008-03-23 08:46:37 UTC
Same here. After upgrading to iproute2-2.6.23.20071016 all interfaces are configured, but not brought up. Every call of /etc/init.d/net.* shows a lot of "RTNETLINK answers: Invalid argument"-Errors. Calling "ip link set lo up" from bash returns also a "RTNETLINK answers: Invalid argument"-error, "ifconfig lo up" works fine.
I think this is only a bug in iproute2 and not related to any init-scripts.

sys-apps/iproute2-2.6.23.20071016 should be masked meanwhile. Using this version on a remote box without physical access locks you out.
Comment 5 Ralf Folkerts 2008-03-23 16:42:35 UTC
I yesterday updated my @home System; on that maschine, the iproute2-2.6.23-20071016 indeed does work 1a. Not sure, maybe a Kernel-related issue (on the machine where the problem occured I tried Kernels 2.6.21-xen, 2.6.20-r2-xen, and 2.6.18-gentoo, i.e. 2 Xen Kernels and one rather old "normal" Kernel). On the @home-Machine I don't use Xen and it runs with Kernel 2.6.24-gentoo-r3.
Comment 6 Ralf Folkerts 2008-03-23 17:22:09 UTC
One more note: On my @home-System, to check my assumption the Problem is Kernel-related I just emerged & compiled a 2.6.19-gentoo-r5 Kernel. Upon booting this "old" Kernel I got exactly the same errors (i.e, RTNETLINK: invalid argument and no usable Interfaces) as on the Xen-Host @work. So it seems the "new" iproute2 needs either a more recent Kernel OR some feature turned on on an "old" Kernel...
Comment 7 Vincent Le Ligeour 2008-03-26 09:24:38 UTC
Confirmed here.
Working configuration:

sys-apps/iproute2-2.6.22.20070710
sys-kernel/xen-sources-2.6.20-r6
or:
sys-apps/iproute2-2.6.23.20071016
sys-kernel/gentoo-sources-2.6.23-r8

Not working configuration:

sys-apps/iproute2-2.6.23.20071016
sys-kernel/xen-sources-2.6.20-r6

Vincent
Comment 8 Sebastián González 2008-03-29 10:18:20 UTC
I confirm also:

everything works fine for me with: 
sys-apps/iproute2-2.6.22.20070710
sys-kernel/gentoo-sources-2.6.19-r5

and I get "RTNETLINK: Invalid Argument" errors if I upgrade to

sys-apps/iproute2-2.6.23.20071016
(same kernel, which I cannot upgrade for other reasons)


(In reply to comment #7)
> Confirmed here.
> Working configuration:
> 
> sys-apps/iproute2-2.6.22.20070710
> sys-kernel/xen-sources-2.6.20-r6
> or:
> sys-apps/iproute2-2.6.23.20071016
> sys-kernel/gentoo-sources-2.6.23-r8
> 
> Not working configuration:
> 
> sys-apps/iproute2-2.6.23.20071016
> sys-kernel/xen-sources-2.6.20-r6
> 
> Vincent
> 

Comment 9 SpanKY gentoo-dev 2008-03-29 17:25:06 UTC
re-open if iproute2-2.6.24.20080108 doesnt work