Bug 12891 - RTNL: assertion failed problem
Summary: RTNL: assertion failed problem
Status: RESOLVED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: All Linux
: P1 high
Assignee: drivers_network@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-18 01:30 UTC by André Fettouhi
Modified: 2009-03-26 07:50 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.28.7
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description André Fettouhi 2009-03-18 01:30:09 UTC
Latest working kernel version:
2.6.28.6
Earliest failing kernel version:
2.6.28.7
Distribution:
Arch Linux 32 bit
Hardware Environment:
DELL Studio PC
Quad Core Duo
Nvidia 9600 GT
4 GB RAM
2x500 GB HDD in RAID 0 (fake-RAID)
wifi (Broadcom)
Software Environment:
KDE 4.2.1 (KDEmod)

Problem Description:
I've reported this problem about 3 months ago (to Arch devs) 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 know this is very very annoying.

Steps to reproduce:
Comment 1 Alan 2009-03-18 08:15:44 UTC
Is this an upstream kernel or an arch supplied kernel. Also what are you using to drive the Nvidia card 
Comment 2 André Fettouhi 2009-03-18 11:29:39 UTC
This is an arch supplied kernel and I'm using the propriatery nvidia driver (latest beta 185.13).

Regards

André
Comment 3 Alan 2009-03-25 23:11:30 UTC
Can you reproduce it without ever having the proprietary nvidia stuff loaded ?
Comment 4 André Fettouhi 2009-03-26 07:39:13 UTC
Well, the problem is gone now since the latest kernel upgrade (to 2.6.28.8) and the errors I saw after grub are gone also.

Regards

André
Comment 5 Alan 2009-03-26 07:50:56 UTC
Thanks..

Note You need to log in before you can comment on or make changes to this bug.