Christian Lamparter wrote: > On Friday 16 January 2009 10:13:07 Johannes Berg wrote: >> On Thu, 2009-01-15 at 21:18 -0600, Larry Finger wrote: >> >>>>> Object 0xddec18d0: >69< 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b ikkkkkkkkkkkkkkk >>> 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. >> 6b to 6a is often the result of a refcounting bug that happens to unref >> a value _after_ it has been freed. But that doesn't explain 6b to 69, >> unless you happen to have _two_ refcounting bugs. Not that I necessarily >> think that memory is bad > Well, this idiotic debug patch (kref-kernel-debug-patch) could shed some light into > the problem who's using a freed skb. didn't trigger anything here, just the usual: BUG kmalloc-4096: Poison overwritten ----------------------------------------------------------------------------- INFO: 0xdc8161b0-0xdc8161b0. First byte 0x6a instead of 0x6b INFO: Allocated in dev_alloc_skb+0x19/0x30 age=1762 cpu=0 pid=3530 INFO: Freed in __kfree_skb+0xf/0x90 age=613 cpu=0 pid=3527 INFO: Slab 0xc1390200 objects=7 used=5 fp=0xdc816120 flags=0x400020c2 INFO: Object 0xdc816120 @offset=24864 fp=0xdc8140c0 but no other warnings... 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
