OpenWrt Forum Archive

Topic: KERNEL problem with frottle running

The content of this topic has been archived on 2 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Post #1
carlopires
9 Jun 2005, 19:57

Hi,

After put frottle to run I'm getting these strange KERNEL messages in dmesg:

..
...
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 88k freed
Algorithmics/MIPS FPU Emulator v1.5
diag boardtype: 00000101
jffs2.bbc: SIZE compression mode activated.
PCI: Setting latency timer of device 00:02.0 to 64
5325E   phy=FFFFFFFF
5325E   VLAN programming for BCM5325E-MDIO I/F switch
eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.60.13.0
PCI: Setting latency timer of device 00:01.0 to 64
eth1: Broadcom BCM4320 802.11 Wireless Controller 3.60.13.0
device eth0 entered promiscuous mode
vlan0: add 01:00:5e:00:00:01 mcast address to master interface
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
br0: port 1(vlan0) entering learning state
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(vlan0) entering forwarding state
br0: topology change detected, propagating
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
br1: port 1(vlan1) entering listening state
br1: port 1(vlan1) entering learning state
br1: port 1(vlan1) entering forwarding state
br1: topology change detected, propagating
device wds0.2 entered promiscuous mode
br1: port 2(wds0.2) entering listening state
br1: port 2(wds0.2) entering learning state
br1: port 2(wds0.2) entering forwarding state
br1: topology change detected, propagating
Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
br1: received tcn bpdu on port 2(wds0.2)
br1: topology change detected, propagating
br1: received tcn bpdu on port 2(wds0.2)
br1: topology change detected, propagating
KERNEL: assertion (dev->ip_ptr==NULL) failed at dev.c(2607)
Freeing alive device 8026ae00, vlan1
KERNEL: assertion (dev->ip_ptr==NULL) failed at dev.c(2607)
Freeing alive device 8026ae00, vlan1
KERNEL: assertion (dev->ip_ptr==NULL) failed at dev.c(2607)
Freeing alive device 8026ae00, vlan1

My hardware is a WRT54Gv3 with last experimental kernel. Anyone know about incompatibilites of frottle with this kernel ?

(Last edited by carlopires on 9 Jun 2005, 20:00)

Post #2
TheRoDent
9 Jun 2005, 23:33

Looks like the ethernet driver module is being removed...

Try "logread -f", and then start frottle to double check if those messages are in actual fact being generated due to frottle, or perhaps something else.

et.o being removed like that is very odd, and it's the only reason I know of to see the "Freeing alive device" message.

Post #3
carlopires
10 Jun 2005, 13:21

Yes. This messages is due to frottle running. I didn't know frottle eat too much resources. :-(
I'm going to test if the fact of I'm bridging vlan1 with wds node make some diference.

The discussion might have continued from here.