On Thu, Mar 29, 2007 at 08:47:18PM +0200, Philipp Reisner ([EMAIL PROTECTED])
wrote:
> RIP: 0010:[<ffffffff8024f904>] [<ffffffff8024f904>]
> netlink_broadcast+0x123/0x2de
> RSP: 0018:ffff8100379bddc0 EFLAGS: 00010297
> RAX: 656b736968772d31 RBX: ffff810079d7f800 RCX: 0000000000000004
> RDX: ffff81007e113000 RSI: ffff810079d68280 RDI: ffffffff804c6a80
> RBP: ffff810079d68280 R08: 00000000000000d0 R09: ffff810079d68280
> R10: 0000000000000002 R11: ffff81007fd6fac0 R12: 0000000000000020
> R13: 0000000000000000 R14: ffff810079d7f818 R15: 0000000000000003
> FS: 0000000000000000(0000) GS:ffffffff804d6000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: 00002b2acc1ecb40 CR3: 0000000079ac1000 CR4: 00000000000026e0
> Process cqueue/0 (pid: 1948, threadinfo ffff8100379bc000, task
> ffff810037fd8040)
> Stack: ffff810079d7f400 00000000000000d0 ffff81007e113000 000000007e069a24
> 0000000000000000 0000000000000100 ffff810079d7f400 ffff81007e069a10
> ffff81007e069a24 ffffffff881e9d00 ffff81007cf07800 ffffffff881d5c23
...
> Code; ffffffff8024f904 <netlink_broadcast+123/2de> <=====
> 0: 44 0f a3 38 bt %r15d,(%rax) <=====
%rax contains 0x656b736968772d31
In my x86_64 it is obtained from %rbx, which seems to be correct, so I'm
a bit stuck, something has rewritten internals of the socket structure,
and it does not look like free poisoning.
0xffffffff8024ea14 <netlink_broadcast+289>: mov 0x268(%rbx),%rax
0xffffffff8024ea1b <netlink_broadcast+296>: bt %r15d,(%rax)
Can you describe your load? Is it too high to put a debug printk there?
Can you enable as much debug options as possible?
--
Evgeniy Polyakov
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
