Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1731700 > unrolled thread
| Started by | Jens Axboe <axboe@kernel.dk> |
|---|---|
| First post | 2017-09-13 18:20 +0200 |
| Last post | 2017-09-13 23:00 +0200 |
| Articles | 5 — 2 participants |
Back to article view | Back to linux.kernel
WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x6a/0x100 Jens Axboe <axboe@kernel.dk> - 2017-09-13 18:20 +0200
Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x6a/0x100 Linus Torvalds <torvalds@linux-foundation.org> - 2017-09-13 18:30 +0200
Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x6a/0x100 Jens Axboe <axboe@kernel.dk> - 2017-09-13 18:30 +0200
Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x6a/0x100 Linus Torvalds <torvalds@linux-foundation.org> - 2017-09-13 22:50 +0200
Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x6a/0x100 Jens Axboe <axboe@kernel.dk> - 2017-09-13 23:00 +0200
| From | Jens Axboe <axboe@kernel.dk> |
|---|---|
| Date | 2017-09-13 18:20 +0200 |
| Subject | WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x6a/0x100 |
| Message-ID | <upiym-1dH-5@gated-at.bofh.it> |
Hi,
I get this new warning when I suspend/resume my gen4 x1 laptop running
current -git. Looks like this commit is the problematic one:
commit 72c0098d92cedb11c7e0151e84918840a4e96b31
Author: Andy Lutomirski <luto@kernel.org>
Date: Wed Sep 6 19:54:53 2017 -0700
x86/mm: Reinitialize TLB state on hotplug and resume
Full trace:
[13570.177554] x86: Booting SMP configuration:
[13570.177558] smpboot: Booting Node 0 Processor 1 APIC 0x2
[13570.186919] ------------[ cut here ]------------
[13570.186942] WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x6a/0x100
[13570.186945] Modules linked in: rfcomm fuse ctr ccm arc4 bnep snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec binfmt_misc iwlmvm snd_hwdep snd_hda_core mac80211 snd_pcm nls_iso8859_1 snd_seq_midi nls_cp437 snd_seq_midi_event x86_pkg_temp_thermal vfat fat iwlwifi snd_rawmidi intel_powerclamp kvm_intel snd_seq kvm btusb uvcvideo btintel bluetooth snd_seq_device irqbypass snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd videobuf2_core aesni_intel videodev aes_x86_64 crypto_simd cryptd glue_helper ecdh_generic cfg80211 soundcore hid_generic usbhid hid i915 psmouse e1000e ptp pps_core xhci_pci xhci_hcd intel_gtt
[13570.187074] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G U W 4.13.0+ #109
[13570.187077] Hardware name: LENOVO 20FBCTO1WW/20FBCTO1WW, BIOS N1FET54W (1.28 ) 08/10/2017
[13570.187082] task: ffff88042e983900 task.stack: ffff88042e99c000
[13570.187093] RIP: 0010:initialize_tlbstate_and_flush+0x6a/0x100
[13570.187097] RSP: 0000:ffff88042e99feb0 EFLAGS: 00010046
[13570.187103] RAX: 00000000000000a0 RBX: 0000000000000001 RCX: ffffffff81a5c900
[13570.187107] RDX: 0000000002a09000 RSI: 0000000002a09000 RDI: 0000000000000000
[13570.187110] RBP: ffff88042e99feb0 R08: 0000000001000000 R09: 000000000000007f
[13570.187113] R10: ffff88042e560000 R11: 0000000000000000 R12: ffff880441497540
[13570.187117] R13: ffff88042e983900 R14: ffff88044148c3e0 R15: 0000000000000001
[13570.187122] FS: 0000000000000000(0000) GS:ffff880441480000(0000) knlGS:0000000000000000
[13570.187126] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[13570.187129] CR2: 0000000000000000 CR3: 0000000002a09000 CR4: 00000000000000a0
[13570.187132] Call Trace:
[13570.187150] cpu_init+0x1e8/0x490
[13570.187160] ? arch_cpu_idle_dead+0xf/0x20
[13570.187168] start_secondary+0xa/0x100
[13570.187173] ? start_secondary+0xa/0x100
[13570.187186] secondary_startup_64+0xa5/0xa5
[13570.187191] Code: 00 00 4c 01 c0 48 39 c6 0f 85 92 00 00 00 48 8b 05 30 9b a8 00 a9 00 00 02 00 74 11 65 48 8b 05 4d ea fc 7e a9 00 00 02 00 75 02 <0f> ff 48 81 e2 00 f0 ff ff 0f 22 da 65 66 c7 05 28 ea fc 7e 00
[13570.187299] ---[ end trace bb794a6054f8e764 ]---
[13570.188170] cache: parent cpu1 should not be sleeping
[13570.188799] CPU1 is up
--
Jens Axboe
[toc] | [next] | [standalone]
| From | Linus Torvalds <torvalds@linux-foundation.org> |
|---|---|
| Date | 2017-09-13 18:30 +0200 |
| Subject | Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x6a/0x100 |
| Message-ID | <upiI1-1gS-13@gated-at.bofh.it> |
| In reply to | #1731700 |
On Wed, Sep 13, 2017 at 9:11 AM, Jens Axboe <axboe@kernel.dk> wrote:
>
> I get this new warning when I suspend/resume my gen4 x1 laptop running
> current -git. Looks like this commit is the problematic one:
Yes, ths fix should be percolating up from the x86 tip tree later
today, I'm hoping. In the meantime, things should work with current
-git (as long as you don't hibernate), apart from the ugly warning.
Linus
[toc] | [prev] | [next] | [standalone]
| From | Jens Axboe <axboe@kernel.dk> |
|---|---|
| Date | 2017-09-13 18:30 +0200 |
| Message-ID | <upiI1-1gS-11@gated-at.bofh.it> |
| In reply to | #1731706 |
On 09/13/2017 10:26 AM, Linus Torvalds wrote: > On Wed, Sep 13, 2017 at 9:11 AM, Jens Axboe <axboe@kernel.dk> wrote: >> >> I get this new warning when I suspend/resume my gen4 x1 laptop running >> current -git. Looks like this commit is the problematic one: > > Yes, ths fix should be percolating up from the x86 tip tree later > today, I'm hoping. In the meantime, things should work with current > -git (as long as you don't hibernate), apart from the ugly warning. Great, sounds good. Things work fine, just noticed that I get a lot of spew from that. -- Jens Axboe
[toc] | [prev] | [next] | [standalone]
| From | Linus Torvalds <torvalds@linux-foundation.org> |
|---|---|
| Date | 2017-09-13 22:50 +0200 |
| Subject | Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and_flush+0x6a/0x100 |
| Message-ID | <upmLD-3Lv-5@gated-at.bofh.it> |
| In reply to | #1731706 |
On Wed, Sep 13, 2017 at 9:26 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> Yes, ths fix should be percolating up from the x86 tip tree later
> today, I'm hoping.
Ok, this should all be ok in current -git now.
Linus "knock wood" Torvalds
[toc] | [prev] | [next] | [standalone]
| From | Jens Axboe <axboe@kernel.dk> |
|---|---|
| Date | 2017-09-13 23:00 +0200 |
| Message-ID | <upmVl-3P1-33@gated-at.bofh.it> |
| In reply to | #1731847 |
On 09/13/2017 02:44 PM, Linus Torvalds wrote: > On Wed, Sep 13, 2017 at 9:26 AM, Linus Torvalds > <torvalds@linux-foundation.org> wrote: >> Yes, ths fix should be percolating up from the x86 tip tree later >> today, I'm hoping. > > Ok, this should all be ok in current -git now. Confirmed, no more warnings with current -git. Now it's just missing the pci bridge enable fixup, and my laptop is happy with current -git again. -- Jens Axboe
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web