From: Andy Lutomirski <luto@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Andy Lutomirski <luto@kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Sep 12
Date: Thu, 14 Sep 2017 09:48:27 -0700 [thread overview]
Message-ID: <CALCETrUoVT4DXJo-QU7mX0X5tUCp=jjkyGbomt1pd3Yt+GNd6g@mail.gmail.com> (raw)
In-Reply-To: <20170912131825.GA485@tigerII.localdomain>
On Tue, Sep 12, 2017 at 6:18 AM, Sergey Senozhatsky
<sergey.senozhatsky@gmail.com> wrote:
> Hi Andy,
>
> got the following warn for each CPU
>
>
> [ 0.000000] ------------[ cut here ]------------
> [ 0.000000] WARNING: CPU: 0 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x60/0xd4
> [ 0.000000] Modules linked in:
> [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.13.0-next-20170912-00021-g7df61d682d25-dirty #406
> [ 0.000000] task: ffffffff8180d480 task.stack: ffffffff81800000
> [ 0.000000] RIP: 0010:initialize_tlbstate_and_flush+0x60/0xd4
> [ 0.000000] RSP: 0000:ffffffff81803eb8 EFLAGS: 00010046
> [ 0.000000] RAX: 00000000000406b0 RBX: ffff88042fa16440 RCX: 0000000001808000
> [ 0.000000] RDX: ffffffff8182f3e0 RSI: 0000000001808000 RDI: 0000000000000000
> [ 0.000000] RBP: ffffffff81803f10 R08: 0000000000000000 R09: ffffffff0000ffff
> [ 0.000000] R10: ffff0000ffffffff R11: 0000ffffffffffff R12: 0000000000000000
> [ 0.000000] R13: 0000000000000000 R14: ffff88042fa0c3a0 R15: ffffffff8180d480
> [ 0.000000] FS: 0000000000000000(0000) GS:ffff88042fa00000(0000) knlGS:0000000000000000
> [ 0.000000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 0.000000] CR2: ffff88042fdff000 CR3: 0000000001808000 CR4: 00000000000406b0
> [ 0.000000] Call Trace:
> [ 0.000000] cpu_init+0x174/0x2dc
> [ 0.000000] trap_init+0x3a/0x4a
> [ 0.000000] start_kernel+0x1da/0x3f6
> [ 0.000000] secondary_startup_64+0xa5/0xa5
> [ 0.000000] Code: 00 80 ff 77 00 00 48 01 f8 48 39 c6 74 02 0f ff 48 8b 05 7d b9 82 00 0f ba e0 11 73 10 65 48 8b 05 fb 92 fe 7e 0f ba e0 11 72 02 <0f> ff 48 81 e1 00 f0 ff ff 0f 22 d9 65 66 c7 05 d7 92 fe 7e 00
> [ 0.000000] ---[ end trace e43a322026e46189 ]---
>
Should be fixed upstream now.
>
> -ss
next prev parent reply other threads:[~2017-09-14 16:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 4:16 linux-next: Tree for Sep 12 Stephen Rothwell
2017-09-12 13:18 ` Sergey Senozhatsky
2017-09-14 16:48 ` Andy Lutomirski [this message]
2017-09-14 22:31 ` Sergey Senozhatsky
-- strict thread matches above, loose matches on Subject: below --
2023-09-12 5:26 Stephen Rothwell
2022-09-12 10:09 Stephen Rothwell
2018-09-12 4:39 Stephen Rothwell
2016-09-12 5:42 Stephen Rothwell
2015-09-12 5:09 Stephen Rothwell
2014-09-12 7:38 Stephen Rothwell
2014-09-12 17:39 ` Randy Dunlap
2014-09-13 1:59 ` Stephen Rothwell
2014-09-13 2:09 ` Stephen Rothwell
2013-09-12 4:34 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='CALCETrUoVT4DXJo-QU7mX0X5tUCp=jjkyGbomt1pd3Yt+GNd6g@mail.gmail.com' \
--to=luto@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sergey.senozhatsky@gmail.com \
--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).