From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Kacur <jkacur@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.12.9-rt13: BUG: soft lockup
Date: Fri, 7 Mar 2014 14:13:41 +0100 [thread overview]
Message-ID: <20140307131341.GC8637@linutronix.de> (raw)
In-Reply-To: <52FD4D89.2000207@localhost>
* Fernando Lopez-Lezcano | 2014-02-13 14:56:09 [-0800]:
>On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
>>On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
>>>[771508.546449] RIP: 0010:[<ffffffff810dc60a>] [<ffffffff810dc60a>]
>>>smp_call_function_many+0x2ca/0x330
>>
>>Can you decode the exact location inside of smp_call_function_many via
>>addr2line please ?
>
>Hope this is useful (adding 0x2ce/0x330 as offsets does not make any
>difference, don't know if it should)...
ffffffff810dc60a is the location where the CPU is atm. The address of
smp_call_function_many() + 0x2ca should give the same value. 0x330 says
that the function is 0x330 bytes in size.
that means, if you do the math, you learn that smp_call_function_many()
starts at 0xffffffff810dc340 and ends at 0xffffffff810dc66f.
Sebastian
prev parent reply other threads:[~2014-03-07 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 22:17 3.12.9-rt13: BUG: soft lockup Fernando Lopez-Lezcano
2014-02-13 22:25 ` Thomas Gleixner
2014-02-13 22:56 ` Fernando Lopez-Lezcano
2014-02-13 23:55 ` Thomas Gleixner
2014-02-14 6:26 ` Fernando Lopez-Lezcano
2014-02-14 10:43 ` Thomas Gleixner
2014-02-14 18:54 ` Fernando Lopez-Lezcano
2014-02-19 9:50 ` Thomas Gleixner
2014-03-07 13:15 ` Sebastian Andrzej Siewior
2014-03-07 13:13 ` Sebastian Andrzej Siewior [this message]
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=20140307131341.GC8637@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.