Bug 141278

Summary: wait_for_sysfs[6744] - udev warning
Product: [Fedora] Fedora Reporter: Jon W <jonathan>
Component: udevAssignee: Harald Hoyer <harald>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-11-30 05:54:26 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Jon W 2004-11-29 19:18:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020
Firefox/0.10.1

Description of problem:
From dmesg ...
 
wait_for_sysfs[6744]: either wait_for_sysfs (udev 039) needs an update
to handle the device '/class/net/nlv0' properly (no device symlink) or
the sysfs-support of your device's driver needs to be fixed, please
report to <linux-hotplug-devel@lists.sourceforge.net>
Nov 29 23:51:38 ldnukslx38502 kernel: Unable to handle kernel NULL
pointer dereference at virtual address 0000002c
Nov 29 23:51:38 ldnukslx38502 kernel:  printing eip:
...
...

When starting Apani netlock VPN service using net device nlv0
unhappiness reigns! Whether kernel is 2.6.9-1.667 or kernel is custom
built and is PREEMPT using 2.6.10-rc2 error occurs on dev-up.


Version-Release number of selected component (if applicable):
udev-039-8.FC3

How reproducible:
Always

Steps to Reproduce:
1.start netlock service
2.connect to vpn 
3.bring up interface
    

Actual Results:  - Networking had to be restarted
- Netlock service stopped


Expected Results:  Netlock service connects through VPN, nlv0
interface ups and encapsulates traffic on default route device

Additional info:

Nov 29 23:50:28 ldnukslx38502 wait_for_sysfs[6744]: either
wait_for_sysfs (udev 039) needs an update to handle the device
'/class/net/nlv0' properly (no device symlink) or the sysfs-support of
your device's driver needs to be fixed, please report to
<linux-hotplug-devel@lists.sourceforge.net>
Nov 29 23:51:38 ldnukslx38502 kernel: Unable to handle kernel NULL
pointer dereference at virtual address 0000002c
Nov 29 23:51:38 ldnukslx38502 kernel:  printing eip:
Nov 29 23:51:38 ldnukslx38502 kernel: c02a5351
Nov 29 23:51:38 ldnukslx38502 kernel: *pde = 00000000
Nov 29 23:51:38 ldnukslx38502 kernel: Oops: 0000 [#1]
Nov 29 23:51:38 ldnukslx38502 kernel: PREEMPT
Nov 29 23:51:38 ldnukslx38502 kernel: Modules linked in: nlvcard
mishim ipt_LOG ipt_multiport ipt_state ip_conntrack_tftp
ip_conntrack_proto_sctp ip_conntrack_irc ip_conntrack_ftp
ip_conntrack_amanda ip_conntrack iptable_filter ip_tables ndiswrapper
i915 md5 ipv6 parport_pc lp parport autofs4 sunrpc dm_mod video button
battery ac ohci1394 hci_usb bluetooth ieee1394 uhci_hcd ehci_hcd
i2c_i801 i2c_core snd_intel8x0m snd_intel8x0 snd_ac97_codec
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore
snd_page_alloc tg3 ext3 jbd
Nov 29 23:51:38 ldnukslx38502 kernel: CPU:    0
Nov 29 23:51:38 ldnukslx38502 kernel: EIP:    0060:[<c02a5351>]   
Tainted: P    VLI
Nov 29 23:51:38 ldnukslx38502 kernel: EFLAGS: 00210202   (2.6.10-rc2)
...
...
Comment 1 Jon W 2004-11-29 19:48:21 EST
Udev entry before actually tunneling, but after service is started:

[root@ldnukslx38502 cvc_linux-rh-gcc3-3.1.1e]# udevinfo  -a -p
/sys/class/net/nlv0/

udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful
attributes
in the udev key format.
Only attributes within one device section may be used together in one
rule,
to match the device for which the node will be created.

  looking at class device '/sys/class/net/nlv0':
    SYSFS{addr_len}="6"
    SYSFS{address}="00:00:00:00:00:00"
    SYSFS{broadcast}="ff:ff:ff:ff:ff:ff"
    SYSFS{features}="0x0"
    SYSFS{flags}="0x82"
    SYSFS{ifindex}="6"
    SYSFS{iflink}="6"
    SYSFS{mtu}="1500"
    SYSFS{tx_queue_len}="0"
    SYSFS{type}="1"

Comment 2 Harald Hoyer 2004-11-30 05:54:26 EST
the udev warning is harmless and will be removed in the next update...
Your kernel oops isn't harmless...