On Thursday 15 January 2009 21:06:24 Artur Skawina wrote: > Christian Lamparter wrote: > > On Thursday 15 January 2009 20:12:03 Artur Skawina wrote: > >>>> Upgraded to current wireless-testing/pending on the problematic box > >>>> and almost immediately got [1]. No slab corruption this time (at least > >>>> not yet). Will switch to GFP_ATOMIC and retry w/ the new fw. > > >>> yes that's a bug, p54_set_tim must use GFP_ATOMIC, do you want to post the patch? > >> nah, too trivial :) fwiw i used this: > > well, it should be "done", right? :-) > > > > just add "John W. Linville" <linville@xxxxxxxxxxxxx>" to the cc, > > change the subject line to "[PATCH] p54: set_tim must be atomic." > > and put a Signed-off-by: your name <your@mail> in the mail body and a "---" to seperate the commit message > > and then the patch. And it will be in the next round of -rcX fixes. > > well, i really meant the 'too trivial' part and was hoping you'd do it ;) > ok, will resend. > well... I'm still looking for an explanation for your other problems: ============================================================================= BUG kmalloc-4096: Poison overwritten ----------------------------------------------------------------------------- Object 0xddec18c0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk Object 0xddec18d0: >69< 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b ikkkkkkkkkkkkkkk Object 0xddec18e0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk The odd thing is here that it's only a "single" bit in the object flipped and not more! And we all have slub/slab debug options enabled as well (in fact, we had to fix the usbdriver for that, see patch "p54usb: rewriting rx/tx routines to make use of usb_anchor's facilities" ) can you check your RAM with memtest or something? -------------------------- Disconnecting/reconnecting the wireless client resulted in this: > mac80211-phy0: failed to remove key (0, 00:1b:fb:12:34:56) from hardware (-12) followed later, when killing hostapd, by: > mac80211-phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-12) well, -12 is -ENOMEM. Well we can use GFP_KERNEL in p54_set_key so its unlikely that your "box" doesn't have enough space, but your p54usb device 'itself' has no more room left... and this is unlikely too, so it probably stalled/crashed. We fixed a something like this before for the 2nd generation devices: http://www.spinics.net/lists/linux-wireless/msg25692.html However, I don't know if the net2280 chip on your device needs it or not, but it should hurt if you try it. Regards, Chr -- 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
