On Tuesday 17 March 2009, Johannes Berg wrote: > On Tue, 2009-03-17 at 23:04 +0100, Ivo van Doorn wrote: > > > I think I found something interesting in the log from Antonio which does > > suggest a mac80211 bug: > > > > > > > [108565.280398] phy3 -> rt73usb_config_intf: Error - TXRX_CSR9 WRITE: 0x000d0000, READ: 0x000d0000 > > > [108565.385291] phy3 -> rt73usb_write_beacon: Error - TXRX_CSR9 WRITE: 0x00040000, READ: 0x00040000 > > > [108565.492687] phy3 -> rt73usb_kick_tx_queue: Error - TXRX_CSR9 WRITE: 0x001d0000, READ: 0x001d0000 > > > > These 3 commands mean that mac80211 has send the beacon data. > > > > > [108565.603206] phy3 -> rt73usb_init_registers: Error - TXRX_CSR9 WRITE: 0x00000000, READ: 0x00000000 > > > > This command means that mac80211 uses the start() callback function. This triggers rt2x00 to initialize > > the registers which resets the beacon generation. > > Strange, that doesn't seem right. If you look at net/mac80211/iface.c, > you'll see it call ->start(), then ->add_interface(), and later > ieee80211_start_mesh(), which calls _if_config() and sets > beacon/beacon_enabled. ok, I gone through the rt2x00 code a couple of times now to see how this bug can be triggered by rt2x00, But the only other scenario I could find, is when the open() callback for the netdevice structure doesn't end with a call to the config() callback function. But as far as I see it that is happening correctly. Ivo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
