[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpom0yjSyU+OhK4vdi5R=+JsmAEw2nOsvupDOiWMYsdz3Pg@mail.gmail.com>
Date: Fri, 8 Feb 2013 20:15:22 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: sedat.dilek@...il.com, "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, x86@...nel.org,
linux-kernel@...r.kernel.org,
Linux ACPI <linux-acpi@...r.kernel.org>,
Hillf Danton <dhillf@...il.com>, linux-next@...r.kernel.org,
Linux PM List <linux-pm@...ts.linux-foundation.org>,
Chuansheng Liu <chuansheng.liu@...el.com>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [linux-pm] linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at
kernel/smp.c:245 smp_call_function_single ]
On 8 February 2013 18:51, Rafael J. Wysocki <rjw@...k.pl> wrote:
> On Friday, February 08, 2013 01:47:44 PM Sedat Dilek wrote:
>> >> [ 0.377473] [<ffffffff8105a5ef>] warn_slowpath_common+0x7f/0xc0
>> >> [ 0.377479] [<ffffffff81579130>] ? acpi_cpufreq_target+0x2c0/0x2c0
>> >> [ 0.377483] [<ffffffff8105a64a>] warn_slowpath_null+0x1a/0x20
>> >> [ 0.377487] [<ffffffff810bb7e6>] smp_call_function_single+0x146/0x190
>> >> [ 0.377492] [<ffffffff81579130>] ? acpi_cpufreq_target+0x2c0/0x2c0
>> >> [ 0.377496] [<ffffffff810bb881>] smp_call_function_any+0x51/0x100
>> >> [ 0.377500] [<ffffffff815788c9>] get_cur_val+0x99/0x130
>> >> [ 0.377504] [<ffffffff81579444>] ? acpi_cpufreq_cpu_init+0x2b4/0x6a0
>> >> [ 0.377508] [<ffffffff81578db0>] get_cur_freq_on_cpu+0x60/0x80
>> >> [ 0.377512] [<ffffffff815795a2>] acpi_cpufreq_cpu_init+0x412/0x6a0
>> >> [ 0.377517] [<ffffffff81575bb9>] cpufreq_add_dev+0x2d9/0x4f0
> This problem was introduced by some cpufreq changes that have been dropped from
> linux-next for now (they are still present in the one you're testing, though).
I know why you got this crash and a pull from following would
certainly fix it :)
http://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/heads/for-rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists