[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.20.1709141849340.15926@er-systems.de>
Date: Thu, 14 Sep 2017 18:50:51 +0200 (CEST)
From: Thomas Voegtle <tv@...96.de>
To: Andy Lutomirski <luto@...nel.org>
cc: Paul Menzel <pmenzel@...gen.mpg.de>, X86 ML <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:237
initialize_tlbstate_and_flush+0x120/0x130
On Thu, 14 Sep 2017, Andy Lutomirski wrote:
> On Wed, Sep 13, 2017 at 5:59 AM, Thomas Voegtle <tv@...96.de> wrote:
>> On Sun, 10 Sep 2017, Andy Lutomirski wrote:
>>
>>> On Sat, Sep 9, 2017 at 11:48 PM, Paul Menzel <pmenzel@...gen.mpg.de>
>>> wrote:
>>>>
>>>> Dear Linux folks,
>>>>
>>>>
>>>> With Linux built from commit 4dfc2788033d (Merge tag
>>>> 'iommu-updates-v4.14'
>>>> of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu), I get the
>>>> warning below on a Lenovo X60t with a 32-bit CPU.
>>>
>>>
>>> Indeed. I sent a patch this morning. The warning is harmless -- the
>>> warning condition has a typo.
>>
>>
>>
>> I get that warning (4 times) with that typo fix:
>>
>>
>>
>> [ 0.000000] WARNING: CPU: 0 PID: 0 at arch/x86/mm/tlb.c:245
>> initialize_tlbstate_and_flush+0x6e/0xf0
>> [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted
>> 4.13.0-i5-11559-g6d8ef53e8b2f #176
>> [ 0.000000] Hardware name: BIOSTAR Group H81MG/H81MG, BIOS 4.6.5
>> 06/27/2014
>> [ 0.000000] task: ffffffff8680e480 task.stack: ffffffff86800000
>> [ 0.000000] RIP: 0010:initialize_tlbstate_and_flush+0x6e/0xf0
>> [ 0.000000] RSP: 0000:ffffffff86803e60 EFLAGS: 00010046
>> [ 0.000000] RAX: ffffffff8682c1c0 RBX: 0000000000000000 RCX:
>> 0000000062809000
>> [ 0.000000] RDX: 00000000000406b0 RSI: 0000000006809000 RDI:
>> 0000000000000000
>> [ 0.000000] RBP: ffffffff86803e60 R08: 0000000062809000 R09:
>> ffffffff8697b800
>> [ 0.000000] R10: 0000ffffffffffff R11: ffffffff0000ffff R12:
>> ffff8d7b00a16380
>> [ 0.000000] R13: 0000000000000000 R14: ffff8d7b00a0c3a0 R15:
>> ffffffff8680e480
>> [ 0.000000] FS: 0000000000000000(0000) GS:ffff8d7b00a00000(0000)
>> knlGS:0000000000000000
>> [ 0.000000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> [ 0.000000] CR2: ffff8d7b00dff000 CR3: 0000000062809000 CR4:
>> 00000000000406b0
>> [ 0.000000] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
>> 0000000000000000
>> [ 0.000000] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
>> 0000000000000400
>> [ 0.000000] Call Trace:
>> [ 0.000000] cpu_init+0x1bd/0x4a0
>> [ 0.000000] trap_init+0x3e/0x50
>> [ 0.000000] start_kernel+0x2ad/0x3fc
>> [ 0.000000] ? set_init_arg+0x55/0x55
>> [ 0.000000] x86_64_start_reservations+0x24/0x26
>> [ 0.000000] x86_64_start_kernel+0x6f/0x72
>> [ 0.000000] secondary_startup_64+0xa5/0xa5
>> [ 0.000000] Code: 48 01 f2 49 39 d0 0f 85 94 00 00 00 48 8b 15 be f6 84
>> 00 f7 c2 00 00 02 00 74 12 65 48 8b 15 7a c7 fd 79 f7 c2 00 00 02 00 75 02
>> <0f> ff 48 81 e1 00 f0 ff ff 0f 22 d9 65 66 c7 05 54 c7 fd 79 00
>>
>>
>> What's wrong here?
>>
>
> Try Linus' tree now -- it should be fixed.
Yes, done that already, no problems anymore.
Thanks
Powered by blists - more mailing lists