From: Sedat Dilek <sedat.dilek@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Kristen Carlson Accardi <kristen@linux.intel.com>
Subject: Re: linux-next: Tree for Feb 4
Date: Thu, 5 Feb 2015 00:48:35 +0100 [thread overview]
Message-ID: <CA+icZUVFFMFFmx8tSTZ9YB=FbmjtD_ZfQa3JTOwb5K7eLW=k-w@mail.gmail.com> (raw)
In-Reply-To: <1777022.KaV9ILjeny@vostro.rjw.lan>
On Thu, Feb 5, 2015 at 12:30 AM, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> On Wednesday, February 04, 2015 11:46:32 PM Sedat Dilek wrote:
>> On Wed, Feb 4, 2015 at 10:54 PM, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
>> > On Wednesday, February 04, 2015 09:18:03 PM Sedat Dilek wrote:
>> >> On Wed, Feb 4, 2015 at 9:35 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> >> > Hi all,
>> >> >
>> >> > The next release I will be making will be next-20150209 - which will
>> >> > probably be after the v3.19 release.
>> >> >
>> >> > Changes since 20150203:
>> >> >
>> >> > The sound-asoc tree gained a conflict against the sound tree.
>> >> >
>> >> > The scsi tree gained a build failure caused by an interaction with the
>> >> > driver-core tree. I applied a merge fix patch.
>> >> >
>> >> > The akpm-current tree gained a build failure for which I disabled
>> >> > CONFIG_KASAN.
>> >> >
>> >> > Non-merge commits (relative to Linus' tree): 7461
>> >> > 7314 files changed, 309736 insertions(+), 172363 deletions(-)
>> >> >
>> >> > ----------------------------------------------------------------------------
>> >> >
>> >>
>> >> [ CC linux-rcu | linux-pm | intel_pstate maintainers ]
>> >
>> > Dirk is not the maintainer of intel_pstate any more, CC: Kristen.
>> >
>> >> Hi,
>> >>
>> >> after suspend-and-resume I see the following call-trace:
>> >
>> > Do you see that after CPU1 offline too?
>> >
>>
>> NO.
>>
>> After...
>>
>> root# echo 0 > /sys/devices/system/cpu/cpu1/online
>>
>> ...I see this:
>>
>> +[ 707.936668] PM: Saving platform NVS memory
>> +[ 707.936674] Disabling non-boot CPUs ...
>> +[ 707.936712] intel_pstate CPU 2 exiting
>> +[ 707.938024] smpboot: CPU 2 didn't die...
>> +[ 707.949128] intel_pstate CPU 3 exiting
>> +[ 707.950369] smpboot: CPU 3 didn't die...
>> +[ 707.966248] ACPI: Low-level resume complete
>> +[ 707.966302] PM: Restoring platform NVS memory
>>
>> Full dmesg attached.
>
> The dmesg doesn't match what you said above.
>
> Anyway, that's not what I meant. Does the CPU1 offlining alone:
>
> # echo 0 > /sys/devices/system/cpu/cpu1/online
>
> trigger the trace? It should.
>
YES, I see this...
...
[ 84.668616] PPP BSD Compression module registered
[ 84.678072] PPP Deflate Compression module registered
[ 101.143582] intel_pstate CPU 1 exiting
[ 101.157134]
[ 101.157135] ===============================
[ 101.157136] [ INFO: suspicious RCU usage. ]
[ 101.157139] 3.19.0-rc7-next-20150204.3-iniza-small #1 Not tainted
[ 101.157140] -------------------------------
[ 101.157142] include/trace/events/tlb.h:35 suspicious
rcu_dereference_check() usage!
[ 101.157142]
[ 101.157142] other info that might help us debug this:
[ 101.157142]
[ 101.157143]
[ 101.157143] RCU used illegally from offline CPU!
[ 101.157143] rcu_scheduler_active = 1, debug_locks = 0
[ 101.157144] no locks held by swapper/1/0.
[ 101.157144]
[ 101.157144] stack backtrace:
[ 101.157146] CPU: 1 PID: 0 Comm: swapper/1 Not tainted
3.19.0-rc7-next-20150204.3-iniza-small #1
[ 101.157147] Hardware name: SAMSUNG ELECTRONICS CO., LTD.
530U3BI/530U4BI/530U4BH/530U3BI/530U4BI/530U4BH, BIOS 13XK 03/28/2013
[ 101.157151] 0000000000000001 ffff88011a44fe18 ffffffff817e35fd
0000000000000011
[ 101.157153] ffff88011a448290 ffff88011a44fe48 ffffffff810d6847
ffff8800d3b96100
[ 101.157155] 0000000000000001 ffff88011a44c000 0000000000000005
ffff88011a44fe78
[ 101.157156] Call Trace:
[ 101.157162] [<ffffffff817e35fd>] dump_stack+0x4c/0x65
[ 101.157166] [<ffffffff810d6847>] lockdep_rcu_suspicious+0xe7/0x120
[ 101.157170] [<ffffffff810b71a5>] idle_task_exit+0x205/0x2c0
[ 101.157173] [<ffffffff81054c4e>] play_dead_common+0xe/0x50
[ 101.157175] [<ffffffff81054ca5>] native_play_dead+0x15/0x140
[ 101.157179] [<ffffffff8102963f>] arch_cpu_idle_dead+0xf/0x20
[ 101.157181] [<ffffffff810cd89e>] cpu_startup_entry+0x37e/0x580
[ 101.157183] [<ffffffff81053e20>] start_secondary+0x140/0x150
[ 101.157228] smpboot: CPU 1 is now offline
- Sedat -
next prev parent reply other threads:[~2015-02-04 23:48 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 8:35 linux-next: Tree for Feb 4 Stephen Rothwell
2015-02-04 12:26 ` Sedat Dilek
2015-02-04 15:16 ` Jens Axboe
2015-02-04 15:21 ` Sedat Dilek
2015-02-04 15:31 ` Jens Axboe
2015-02-04 15:36 ` Sedat Dilek
2015-02-04 15:58 ` Martin K. Petersen
2015-02-04 16:06 ` Sedat Dilek
2015-02-05 3:17 ` Martin K. Petersen
2015-02-05 3:41 ` Sedat Dilek
2015-02-05 19:46 ` Sedat Dilek
2015-02-06 15:24 ` Sedat Dilek
2015-02-04 20:18 ` Sedat Dilek
2015-02-04 21:54 ` Rafael J. Wysocki
2015-02-04 21:53 ` Paul E. McKenney
2015-02-04 22:59 ` Rafael J. Wysocki
2015-02-04 23:51 ` Paul E. McKenney
2015-02-04 23:58 ` Sedat Dilek
2015-02-05 0:10 ` Paul E. McKenney
2015-02-05 0:30 ` Sedat Dilek
2015-02-05 0:57 ` Paul E. McKenney
2015-02-05 1:18 ` Sedat Dilek
2015-02-05 1:51 ` Paul E. McKenney
2015-02-05 1:53 ` Sedat Dilek
2015-02-05 2:12 ` Sedat Dilek
2015-02-05 4:13 ` Paul E. McKenney
2015-02-05 7:14 ` Dave Hansen
2015-02-05 14:37 ` Paul E. McKenney
2015-02-05 14:57 ` Sedat Dilek
2015-02-05 16:58 ` Paul E. McKenney
2015-02-05 18:03 ` Steven Rostedt
2015-02-05 18:08 ` Steven Rostedt
2015-02-05 18:11 ` Dave Hansen
2015-02-05 18:34 ` Paul E. McKenney
2015-02-05 18:35 ` Dave Hansen
2015-02-05 18:45 ` Paul E. McKenney
2015-02-05 19:25 ` Sedat Dilek
2015-02-05 19:33 ` Paul E. McKenney
2015-02-05 19:42 ` Sedat Dilek
2015-02-05 19:58 ` Steven Rostedt
2015-02-05 20:07 ` Sedat Dilek
2015-02-05 20:22 ` Steven Rostedt
2015-02-05 20:50 ` Sedat Dilek
2015-02-05 21:45 ` Sedat Dilek
2015-02-05 22:09 ` Steven Rostedt
2015-02-05 22:16 ` Sedat Dilek
2015-02-05 23:11 ` Steven Rostedt
2015-02-05 23:53 ` Sedat Dilek
2015-02-06 0:03 ` Sedat Dilek
2015-02-06 0:12 ` Steven Rostedt
2015-02-06 0:14 ` Sedat Dilek
2015-02-04 22:38 ` Sedat Dilek
2015-02-04 23:25 ` Rafael J. Wysocki
2015-02-04 23:54 ` Sedat Dilek
2015-02-04 22:46 ` Sedat Dilek
2015-02-04 23:30 ` Rafael J. Wysocki
2015-02-04 23:48 ` Sedat Dilek [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-04 4:14 Stephen Rothwell
2021-02-04 9:13 Stephen Rothwell
2020-02-04 4:19 Stephen Rothwell
2019-02-04 5:35 Stephen Rothwell
2016-02-04 3:48 Stephen Rothwell
2014-02-04 5:07 Stephen Rothwell
[not found] ` <CAP=VYLpgLC_4yuPtQH_yAd8S9cqQAVu2uB2=Wf3q_zgY4uzkLw@mail.gmail.com>
2014-02-04 22:23 ` Stephen Rothwell
2014-02-05 0:41 ` Stephen Rothwell
2013-02-04 7:39 Stephen Rothwell
2013-02-04 13:56 ` James Hogan
2013-02-04 20:33 ` Stephen Rothwell
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='CA+icZUVFFMFFmx8tSTZ9YB=FbmjtD_ZfQa3JTOwb5K7eLW=k-w@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=sfr@canb.auug.org.au \
/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).