Christian Lamparter wrote: > 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! yes, that does not look good. i didn't find anything obvious under wireless/p54 that could be responsible for it, didn't look at the rest of the stack yet. I'd say ignore this for now, until i'm able to reproduce it; one try on a very different machine didn't help and i didn't have a lot of time to retest after the kernel upgrade(s) today. > 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? yes, i just need to plan for enough downtime... > -------------------------- > 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. Hmm, could having it plugged into a full speed usb port be relevant? On the other computer, i tried both w/ the card connected directly (high speed) and through a full speed hub - didn't make any difference (no crash, same arp etc problems). > 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. ok, will look into it. Thanks, artur -- 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
