Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1730026 > unrolled thread
| Started by | Andy Lutomirski <luto@kernel.org> |
|---|---|
| First post | 2017-09-10 19:50 +0200 |
| Last post | 2017-09-15 19:10 +0200 |
| Articles | 6 — 3 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:237 initialize_tlbstate_and_flush+0x120/0x130 Andy Lutomirski <luto@kernel.org> - 2017-09-10 19:50 +0200
Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:237 initialize_tlbstate_and_flush+0x120/0x130 Thomas Voegtle <tv@lio96.de> - 2017-09-13 15:10 +0200
Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:237 initialize_tlbstate_and_flush+0x120/0x130 Andy Lutomirski <luto@kernel.org> - 2017-09-14 18:50 +0200
Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:237 initialize_tlbstate_and_flush+0x120/0x130 Thomas Voegtle <tv@lio96.de> - 2017-09-14 19:00 +0200
Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:237 initialize_tlbstate_and_flush+0x120/0x130 Paul Menzel <pmenzel@molgen.mpg.de> - 2017-09-15 11:30 +0200
Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:237 initialize_tlbstate_and_flush+0x120/0x130 Andy Lutomirski <luto@kernel.org> - 2017-09-15 19:10 +0200
| From | Andy Lutomirski <luto@kernel.org> |
|---|---|
| Date | 2017-09-10 19:50 +0200 |
| Subject | Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:237 initialize_tlbstate_and_flush+0x120/0x130 |
| Message-ID | <uoewO-7d2-9@gated-at.bofh.it> |
On Sat, Sep 9, 2017 at 11:48 PM, Paul Menzel <pmenzel@molgen.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.
[toc] | [next] | [standalone]
| From | Thomas Voegtle <tv@lio96.de> |
|---|---|
| Date | 2017-09-13 15:10 +0200 |
| Subject | Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:237 initialize_tlbstate_and_flush+0x120/0x130 |
| Message-ID | <upfAt-7M6-7@gated-at.bofh.it> |
| In reply to | #1730026 |
On Sun, 10 Sep 2017, Andy Lutomirski wrote:
> On Sat, Sep 9, 2017 at 11:48 PM, Paul Menzel <pmenzel@molgen.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?
That is v4.13-11559-g6d8ef53e8b2f
CONFIG_DEBUG_VM is not set
Haswell i5-4570
Thomas
[toc] | [prev] | [next] | [standalone]
| From | Andy Lutomirski <luto@kernel.org> |
|---|---|
| Date | 2017-09-14 18:50 +0200 |
| Message-ID | <upFuV-7wa-7@gated-at.bofh.it> |
| In reply to | #1731598 |
On Wed, Sep 13, 2017 at 5:59 AM, Thomas Voegtle <tv@lio96.de> wrote: > On Sun, 10 Sep 2017, Andy Lutomirski wrote: > >> On Sat, Sep 9, 2017 at 11:48 PM, Paul Menzel <pmenzel@molgen.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.
[toc] | [prev] | [next] | [standalone]
| From | Thomas Voegtle <tv@lio96.de> |
|---|---|
| Date | 2017-09-14 19:00 +0200 |
| Subject | Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:237 initialize_tlbstate_and_flush+0x120/0x130 |
| Message-ID | <upFEB-7zL-1@gated-at.bofh.it> |
| In reply to | #1732451 |
On Thu, 14 Sep 2017, Andy Lutomirski wrote: > On Wed, Sep 13, 2017 at 5:59 AM, Thomas Voegtle <tv@lio96.de> wrote: >> On Sun, 10 Sep 2017, Andy Lutomirski wrote: >> >>> On Sat, Sep 9, 2017 at 11:48 PM, Paul Menzel <pmenzel@molgen.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
[toc] | [prev] | [next] | [standalone]
| From | Paul Menzel <pmenzel@molgen.mpg.de> |
|---|---|
| Date | 2017-09-15 11:30 +0200 |
| Subject | Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:237 initialize_tlbstate_and_flush+0x120/0x130 |
| Message-ID | <upV6G-Sy-13@gated-at.bofh.it> |
| In reply to | #1730026 |
Dear Andy, On 09/10/17 19:42, Andy Lutomirski wrote: > On Sat, Sep 9, 2017 at 11:48 PM, Paul Menzel <pmenzel@molgen.mpg.de> wrote: >> 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 am still seeing this with commit 711aab1dbb32 (vfs: constify path argument to kernel_read_file_from_path), which is the latest from Linus’ master branch. ``` [ 0.004000] ------------[ cut here ]------------ [ 0.004000] WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:257 initialize_tlbstate_and_flush+0x120/0x130 [ 0.004000] Modules linked in: [ 0.004000] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.13.0+ #132 [ 0.004000] Hardware name: LENOVO 636338U/636338U, BIOS CBET4000 TIMELESS 01/01/1970 [ 0.004000] task: f4113380 task.stack: f4118000 [ 0.004000] EIP: initialize_tlbstate_and_flush+0x120/0x130 [ 0.004000] EFLAGS: 00210006 CPU: 1 [ 0.004000] EAX: 159bd000 EBX: d5892d00 ECX: d59c0000 EDX: 159c0000 [ 0.004000] ESI: 00000000 EDI: 00000000 EBP: f4119f60 ESP: f4119f50 [ 0.004000] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 0.004000] CR0: 80050033 CR2: 00000000 CR3: 159bd000 CR4: 00000690 [ 0.004000] Call Trace: [ 0.004000] cpu_init+0xc3/0x260 [ 0.004000] start_secondary+0x33/0x1c0 [ 0.004000] startup_32_smp+0x164/0x166 [ 0.004000] Code: 04 00 00 00 00 89 c8 50 9d 8d 74 26 00 83 c3 10 81 fb 4c 50 9b d5 75 c9 58 5b 5e 5f 5d c3 90 8d 74 26 00 0f ff e9 3c ff ff ff 90 <0f> ff e9 13 ff ff ff 89 f6 8d bc 27 00 00 00 00 3e 8d 74 26 00 [ 0.004000] ---[ end trace 17f2b31512589856 ]--- ``` Kind regards, Paul
[toc] | [prev] | [next] | [standalone]
| From | Andy Lutomirski <luto@kernel.org> |
|---|---|
| Date | 2017-09-15 19:10 +0200 |
| Message-ID | <uq2hP-5TN-7@gated-at.bofh.it> |
| In reply to | #1732794 |
On Fri, Sep 15, 2017 at 2:25 AM, Paul Menzel <pmenzel@molgen.mpg.de> wrote: > Dear Andy, > > > On 09/10/17 19:42, Andy Lutomirski wrote: >> >> On Sat, Sep 9, 2017 at 11:48 PM, Paul Menzel <pmenzel@molgen.mpg.de> >> wrote: > > >>> 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 am still seeing this with commit 711aab1dbb32 (vfs: constify path argument > to kernel_read_file_from_path), which is the latest from Linus’ master > branch. > > ``` > [ 0.004000] ------------[ cut here ]------------ > [ 0.004000] WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:257 > initialize_tlbstate_and_flush+0x120/0x130 > [ 0.004000] Modules linked in: > [ 0.004000] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.13.0+ #132 > [ 0.004000] Hardware name: LENOVO 636338U/636338U, BIOS CBET4000 TIMELESS > 01/01/1970 > [ 0.004000] task: f4113380 task.stack: f4118000 > [ 0.004000] EIP: initialize_tlbstate_and_flush+0x120/0x130 > [ 0.004000] EFLAGS: 00210006 CPU: 1 > [ 0.004000] EAX: 159bd000 EBX: d5892d00 ECX: d59c0000 EDX: 159c0000 > [ 0.004000] ESI: 00000000 EDI: 00000000 EBP: f4119f60 ESP: f4119f50 > [ 0.004000] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 > [ 0.004000] CR0: 80050033 CR2: 00000000 CR3: 159bd000 CR4: 00000690 > [ 0.004000] Call Trace: > [ 0.004000] cpu_init+0xc3/0x260 > [ 0.004000] start_secondary+0x33/0x1c0 > [ 0.004000] startup_32_smp+0x164/0x166 > [ 0.004000] Code: 04 00 00 00 00 89 c8 50 9d 8d 74 26 00 83 c3 10 81 fb > 4c 50 9b d5 75 c9 58 5b 5e 5f 5d c3 90 8d 74 26 00 0f ff e9 3c ff ff ff 90 > <0f> ff e9 13 ff ff ff 89 f6 8d bc 27 00 00 00 00 3e 8d 74 26 00 > [ 0.004000] ---[ end trace 17f2b31512589856 ]--- > ``` I can reproduce this on a 32-bit build. The code is Obviously Correct (tm), so I'm adding tracing to figure out what's going on. Stay tuned...
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web