Larry Finger wrote: > 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. In fact i was just trying Christian's URB_ZERO_PACKET suggestion, and got this (about the time when some useful packets started coming in): BUG kmalloc-4096: Poison overwritten ----------------------------------------------------------------------------- INFO: 0xdc8351c8-0xdc8351c8. First byte 0x6a instead of 0x6b INFO: Allocated in dev_alloc_skb+0x19/0x30 age=3720 cpu=0 pid=1952 INFO: Freed in __kfree_skb+0xf/0x90 age=238 cpu=0 pid=0 INFO: Slab 0xc1390600 objects=7 used=6 fp=0xdc8350f0 flags=0x400020c2 INFO: Object 0xdc8350f0 @offset=20720 fp=0x(null) Bytes b4 0xdc8350e0: fb 00 00 00 ae a2 fd ff 5a 5a 5a 5a 5a 5a 5a 5a û...®¢ýÿZZZZZZZZ Object 0xdc8350f0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk [...] Object 0xdc8351b0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk Object 0xdc8351c0: 6b 6b 6b 6b 6b 6b 6b 6b 6a 6b 6b 6b 6b 6b 6b 6b kkkkkkkkjkkkkkkk Object 0xdc8351d0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk [...] Object 0xdc8360e0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 kkkkkkkkkkkkkkk¥ Redzone 0xdc8360f0: bb bb bb bb »»»» Padding 0xdc836118: 5a 5a 5a 5a 5a 5a 5a 5a ZZZZZZZZ Pid: 0, comm: swapper Not tainted 2.6.29-rc1-00273-g0d39407-dirty #47 Call Trace: [<c016b79e>] check_bytes_and_report+0xce/0xf0 [<c016b9f7>] check_object+0x1e7/0x230 [<c016d115>] __slab_alloc+0x245/0x4f0 [<c016e3ff>] __kmalloc_track_caller+0xcf/0x110 [<c03af9f9>] dev_alloc_skb+0x19/0x30 [<c03af9f9>] dev_alloc_skb+0x19/0x30 [<c03aed95>] __alloc_skb+0x55/0x110 [<c03af9f9>] dev_alloc_skb+0x19/0x30 [<c02f1fcc>] p54u_rx_cb+0x1cc/0x1f0 [<c024552a>] kref_put+0x2a/0x80 [<c0340f51>] usb_hcd_giveback_urb+0x41/0xa0 [<c034f81f>] uhci_giveback_urb+0x7f/0x1f0 [<c034fdef>] uhci_scan_schedule+0x33f/0xa40 [<c035213d>] uhci_irq+0x7d/0x140 [<c0340bf5>] usb_hcd_irq+0x25/0x60 [<c0145ff8>] handle_IRQ_event+0x28/0x50 [<c0147210>] handle_level_irq+0x0/0xb0 [<c014725b>] handle_level_irq+0x4b/0xb0 <IRQ> [<c0103707>] common_interrupt+0x27/0x2c [<c0108392>] default_idle+0x42/0x50 [<c0102139>] cpu_idle+0x39/0x80 FIX kmalloc-4096: Restoring 0xdc8351c8-0xdc8351c8=0x6b FIX kmalloc-4096: Marking all objects used 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
