From: Jet Chen <jet.chen@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"Wu, Fengguang" <fengguang.wu@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: CPU: 0 PID: 1935 at kernel/timer.c:1621 migrate_timer_list()
Date: Sat, 05 Apr 2014 15:18:01 +0800 [thread overview]
Message-ID: <533FAE29.4080209@intel.com> (raw)
In-Reply-To: <CAKohpokStOgdO-KFn8hcyV+neaNCvHLSG9od=qyi2-4rV62DRw@mail.gmail.com>
On 04/05/2014 02:26 PM, Viresh Kumar wrote:
> On 5 April 2014 10:00, Jet Chen <jet.chen@intel.com> wrote:
>> vmlinuz from our build system doesn't have debug information. It is hard to
>> use objdump to identify which routine is timer->function.
>
> I see...
>
>> But after several times trials, I get below dmesg messages.
>> It is clear to see address of "timer->function" is 0xffffffff810d7010.
>> In calling stack, " [<ffffffff810d7010>] ?
>> clocksource_watchdog_kthread+0x40/0x40 ". So I guess timer->function is
>> clocksource_watchdog_kthread.
>
> Hmm.. not exactly this function as this isn't timer->function for any timer.
> But I think I have found the right function with this hint:
> clocksource_watchdog()
>
> Can you please try to test the attached patch, which must fix it.
Your patch fixes it!
> Untested. I will
> then post it with your Tested-by :)
Thank you
>
> --
> viresh
>
next prev parent reply other threads:[~2014-04-05 7:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 3:19 WARNING: CPU: 0 PID: 1935 at kernel/timer.c:1621 migrate_timer_list() Fengguang Wu
2014-04-04 4:56 ` Viresh Kumar
2014-04-04 7:46 ` Jet Chen
2014-04-04 7:52 ` Viresh Kumar
2014-04-05 4:30 ` Jet Chen
2014-04-05 6:26 ` Viresh Kumar
2014-04-05 7:18 ` Jet Chen [this message]
2014-04-05 12:05 ` Viresh Kumar
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=533FAE29.4080209@intel.com \
--to=jet.chen@intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.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