Artur Skawina wrote: > 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... I too have seen real single bit changes - in my case 6b went to 6a, and my memory is fine. I wouldn't necessarily blame your hardware. Larry -- 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
