search for: br_device_ev

...nd try and add eth0, it says it's already part of a bridge (it isn't - no bridges yet... may possibly be 'up' as it's listed by ifconfig.) Everytime I try something like ifconfig eth0 down, I get a kernel panic/lockup. Copying what I think is useful from the screen: EIP is at br_device_event+0x94/0x110 [bridge] ... Process ifconfig (pid 22092, threadinfo:c18e9999 task:c165c600) Stack: ....(I assume this is ifconfig's stack, and probably not a lot of interest to the problem...) Call Trace: notifier_call_chain dev_close dev_change_flags devinet_ioctl inet_ioctl sock_ioctl do_ioct...

...state when the lost packet arrived. In fact, the packet is thrown by the bridge because, in br_input.c::br_handle_frame(), state==BR_STATE_DISABLED which force the code to jump to the err: tag at the end of this function. The state is set to this value while an event is received inside br_notify.c::br_device_event(), which do a br_stp_disable_port(). After putting some printk in br_notify.c, i remarked that this event come regularly, and always related to the same bridge port (eth1). It don't hurt me that this event come regularly, but problem is when a packet is flowing in the same time thru the brid...