From: daniel.baluta@gmail.com (Daniel Baluta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Interpreting call trace
Date: Wed, 6 Apr 2011 15:56:29 +0300 [thread overview]
Message-ID: <BANLkTi=hNu5NV_6e+4Vg0wc1j0ySsDJJdg@mail.gmail.com> (raw)
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.
next reply other threads:[~2011-04-06 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 12:56 Daniel Baluta [this message]
2011-04-06 16:47 ` Interpreting call trace Michael Blizek
2011-04-06 17:32 ` Mulyadi Santosa
2011-04-07 3:10 ` Kaustubh Ashtekar
2011-04-07 8:26 ` Daniel Baluta
2011-04-07 9:16 ` nilesh
2011-04-07 9:34 ` Sowmya Sridharan
2011-04-07 17:04 ` Manish Katiyar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=hNu5NV_6e+4Vg0wc1j0ySsDJJdg@mail.gmail.com' \
--to=daniel.baluta@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).