From: Linus Torvalds <torvalds@linux-foundation.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Ingo Molnar <mingo@kernel.org>, Andy Lutomirski <luto@kernel.org>,
X86 ML <x86@kernel.org>, Borislav Petkov <bpetkov@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [4.14-rc0 regression] Re: x60: warnings on boot and resume, arch/x86/mm/tlb.c:257 initialize_ ... was Re: [PATCH 0/2] Fix resume failure due to PCID
Date: Fri, 15 Sep 2017 11:47:49 -0700 [thread overview]
Message-ID: <CA+55aFys0htimG6C-BYAyJMUSrOg75s8oJM-w8i7BeLrUk6cvA@mail.gmail.com> (raw)
In-Reply-To: <20170915102219.GA4312@amd>
On Fri, Sep 15, 2017 at 3:22 AM, Pavel Machek <pavel@ucw.cz> wrote:
>
> Let me pull latest...
>
> 711aab1dbb324d321e3d84368a435a78908c7bce
>
> (Strange. Not authored by Linus and old?)
That's the author date, the committer date is new. Top of tree right
now just happens to be a patch I applied, it's much more commonly a
merge I've done.
> But result is still similar, this time with more debug information.
> [ 0.116813] x86: Booting SMP configuration:
> [ 0.116893] .... node #0, CPUs: #1
> [ 0.004000] Initializing CPU#1
> [ 0.004000] ------------[ cut here ]------------
> [ 0.004000] WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:257 initialize_tlbstate_and_flush+0x2e/0xed
> [ 0.004000] Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW (2.19 ) 03/31/2011
> [ 0.004000] task: f5ca2080 task.stack: f5cc4000
> [ 0.004000] EIP: initialize_tlbstate_and_flush+0x2e/0xed
> [ 0.004000] EFLAGS: 00210087 CPU: 1
> [ 0.004000] EAX: 0504b000 EBX: c4f15540 ECX: c4f15710 EDX: 00000000
> [ 0.004000] ESI: 04ee7000 EDI: f5ca2080 EBP: f5cc5f54 ESP: f5cc5f44
> [ 0.004000] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
> [ 0.004000] CR0: 80050033 CR2: 00000000 CR3: 04ee7000 CR4: 000006b0
> [ 0.004000] Call Trace:
> [ 0.004000] cpu_init+0xdc/0x2f0
> [ 0.004000] start_secondary+0x34/0x1c6
> [ 0.004000] startup_32_smp+0x164/0x166
> [ 0.004000] ? startup_32_smp+0x164/0x166
> [ 0.004000] Code: 56 53 83 ec 08 64 8b 1d c0 c0 03 c5 b9 10 57 f1 c4 e8 de 65 9e 00 89 45 f0 89 55 f4 0f 20 de 8b 43 20 05 00 00 00 40 39 c6 74 11 <0f> ff 50 56 68 74 9c d8 c4 e8 d1 cd 04 00 83 c4 0c a1 20 90 f8
> [ 0.004000] ---[ end trace 7439e29925a49b51 ]---
> [ 0.004000] # CR3: 0000000004ee7000, __pa(mm->pgd): 000000000504b000
Ok, clearly Andy didn't get the 32-bit SMP bringup path right.
Presumable tested a 32-bit UP image, or in a single-cpu VM?
Andy?
Linus
next prev parent reply other threads:[~2017-09-15 18:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 2:54 [PATCH 0/2] Fix resume failure due to PCID Andy Lutomirski
2017-09-07 2:54 ` [PATCH 1/2] x86/mm: Reinitialize TLB state on hotplug and resume Andy Lutomirski
2017-09-07 7:01 ` [PATCH] mm/debug: Change BUG_ON() crashes to survivable WARN_ON() warnings Ingo Molnar
2017-09-07 20:50 ` Linus Torvalds
2017-09-07 7:31 ` [PATCH 1/2] x86/mm: Reinitialize TLB state on hotplug and resume Jiri Kosina
2017-09-07 7:48 ` Ingo Molnar
2017-09-07 19:55 ` Jiri Kosina
2017-09-08 1:23 ` Andy Lutomirski
2017-09-07 9:54 ` Borislav Petkov
2017-09-07 9:59 ` Ingo Molnar
2017-09-07 10:10 ` Borislav Petkov
2017-09-07 2:54 ` [PATCH 2/2] x86/mm: Document how CR4.PCIDE restore works Andy Lutomirski
2017-09-07 3:25 ` [PATCH 0/2] Fix resume failure due to PCID Linus Torvalds
2017-09-07 4:15 ` Andy Lutomirski
2017-09-15 6:59 ` x60: warnings on boot and resume, arch/x86/mm/tlb.c:257 initialize_ ... was " Pavel Machek
2017-09-15 8:39 ` Ingo Molnar
2017-09-15 9:16 ` Pavel Machek
2017-09-15 9:35 ` Ingo Molnar
2017-09-15 10:22 ` [4.14-rc0 regression] " Pavel Machek
2017-09-15 18:47 ` Linus Torvalds [this message]
2017-09-15 19:29 ` Andy Lutomirski
2017-09-15 21:06 ` Andy Lutomirski
2017-09-07 8:59 ` Borislav Petkov
2017-09-15 11:01 ` Pavel Machek
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+55aFys0htimG6C-BYAyJMUSrOg75s8oJM-w8i7BeLrUk6cvA@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=bpetkov@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=pavel@ucw.cz \
--cc=x86@kernel.org \
/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).