FS#13845 - network uses again with udev (takes 90 seconds to start now)

Attached to Project: Arch Linux
Opened by André Fettouhi (A.Fettouhi) - Wednesday, 18 March 2009, 07:24 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 14 April 2009, 21:56 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

I've reported this problem about 3 months ago and at that time it disappeared. I have a DELL pc with an Intel QUAD Core processor and Nvidia graphics card (9600GT). My machine has two network cards (one wifi (Broadcom) and one normal cable (Realtek)). In the last two or three days now I haven't had any internet/network connection and udev takes like 90 seconds (normally it takes a second) to start up. When I boot my machine right after grub I get these warnings

RTNL: assertion failed at net/core/fub_rules.c (625)
RTNL: assertion failed at net/ipv4/devinet.c (1045)
RTNL: assertion failed at net/ipv4/imgp.c (1348)
RTNL: assertion failed at net/ipv4/imgp.c (1199)

I first thought my machine had switched the order of dependence it loads the network cards (eth0=wifi, eth1=cable) to (eth1=wifi, eth0=cable). So I tried to change the order in wicd but that doesn't help. So something is broken again in Arch Linux. I've haven't making ANY changes to my system all other than updating my machine when updates are available (using KDEmod 4.2.1). So I have no clue what the problem is, if it's the kernel or udev or klibc-udev. I just no this is very very annoying.

Additional info:
* package version(s)
* config and/or log files etc.
udev 139
kernel 2.6.28.7

Steps to reproduce:
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Tuesday, 14 April 2009, 21:56 GMT
Reason for closing:  Fixed
Comment by André Fettouhi (A.Fettouhi) - Wednesday, 18 March 2009, 07:25 GMT
Here is the thread is posted my problems in 3 months ago.

http://bbs.archlinux.org/viewtopic.php?id=62502

Regards

André
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 18 March 2009, 08:15 GMT
Is a kernel issue, there was a similar problem in old version (but in bonding driver [#1]), seems to be a locking problem.

See complete errors at dmesg.

And please report it to Linux Kernel Mailing List.

[#1] http://bugzilla.kernel.org/show_bug.cgi?id=9543
Comment by André Fettouhi (A.Fettouhi) - Wednesday, 18 March 2009, 08:23 GMT
OK, I will do that. I've had this problem 3 times now. First back in October with my old machine and again in December on both my old and new machine and now again...

Regards

André
Comment by André Fettouhi (A.Fettouhi) - Wednesday, 18 March 2009, 08:32 GMT
Made a bugreport on kernel.org

http://bugzilla.kernel.org/show_bug.cgi?id=12891

Regards

André
Comment by André Fettouhi (A.Fettouhi) - Wednesday, 25 March 2009, 08:39 GMT
Errors are gone now since latest update of udev and kernel yesterday.

Regards

André

Loading...