Interpreting call trace

Daniel Baluta daniel.baluta at gmail.com
Wed Apr 6 08:56:29 EDT 2011


Hello,

I have the following stack trace:

[3992.172/0] BUG: soft lockup - CPU#0 stuck for 61s! [events/0:39]
[ 3992.215/0] Pid: 39, comm: events/0 Tainted: P        W  2.6.32 #1 X8DTT-H
[ 3992.222/0] RIP: 0010:[<ffffffff8115f989>]  [<ffffffff8115f989>]
__write_lock_failed+0x9/0x20
[ 3992.231/0] RSP: 0018:ffff880028203908  EFLAGS: 00000287
[ 3992.236/0] RAX: ffff88063ce0bfd8 RBX: ffff880028203920 RCX: ffffffff814e1b00
[ 3992.243/0] RDX: ffff8800282144e0 RSI: ffff880028203abc RDI: ffffffff814e1b04
[ 3992.250/0] RBP: ffffffff8100c6f3 R08: 0000000000000004 R09: ffff880028203ab0
[ 3992.257/0] R10: ffff88061851fa08 R11: 0000000000000000 R12: ffff880028203880
[ 3992.264/0] R13: ffff88060404f800 R14: ffffffff814e1b04 R15: ffffffff8101fd88
[ 3992.272/0] FS:  0000000000000000(0000) GS:ffff880028200000(0000)
knlGS:0000000000000000
[ 3992.280/0] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[ 3992.286/0] CR2: 00007f9cc9fb9000 CR3: 0000000001001000 CR4: 00000000000006f0
[ 3992.293/0] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 3992.300/0] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 3992.307/0] Call Trace:
[ 3992.309/0]  <IRQ>  [<ffffffff81374e12>] ? _write_lock_bh+0x22/0x30
[ 3992.316/0]  [<ffffffff81297751>] ? neigh_create+0x2f1/0x6b0
[ 3992.321/0]  [<ffffffff81374f00>] ? _read_unlock_bh+0x10/0x20
[ 3992.327/0]  [<ffffffff81296401>] ? neigh_lookup+0xd1/0xf0
[ 3992.333/0]  [<ffffffff81297b96>] ? neigh_event_ns+0x86/0xc0
[ 3992.338/0]  [<ffffffff812f2cdb>] ? arp_process+0x9fb/0xbf0
[ 3992.344/0]  [<ffffffff812f2ffc>] ? arp_rcv+0x11c/0x130

How could one interpret this?

For example having:
[ 3992.316/0]  [<ffffffff81297751>] ? neigh_create+0x2f1/0x6b0
[ 3992.321/0]  [<ffffffff81374f00>] ? _read_unlock_bh+0x10/0x20

means that _read_unlock_bh has been called & finished ? Or it has been
interrupted by
next function in trace (neigh_create).

Any other info about interpreting call traces are welcomed.


thanks,
Daniel.



More information about the Kernelnewbies mailing list