From: Dave Hansen <dave.hansen@linux.intel.com> To: Eduardo Valentin <eduval@amazon.com> Cc: Ingo Molnar <mingo@kernel.org>, kernel test robot <fengguang.wu@intel.com>, LKP <lkp@01.org>, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>, wfg@linux.intel.com, aliguori@amazon.com Subject: Re: 2f47e7e19f ("x86/mm/kaiser: Use PCID feature to make user and .."): WARNING: CPU: 0 PID: 1 at mm/early_ioremap.c:114 __early_ioremap Date: Mon, 27 Nov 2017 10:28:35 -0800 [thread overview] Message-ID: <f5382aac-3714-e1e2-8ac9-94b23bd8fe6e@linux.intel.com> (raw) In-Reply-To: <20171127180328.GA12661@u40b0340c692b58f6553c.ant.amazon.com> On 11/27/2017 10:03 AM, Eduardo Valentin wrote: > On top of VM crashes, on your branch: > https://git.kernel.org/pub/scm/linux/kernel/git/daveh/x86-kaiser.git/log/?h=kaiser-414-tipwip-20171123 > > I am also getting crashes in early userspace, during tlb flushes. When KAISER is enabled and whenever userspace is loaded, I get a stack trace around __do_page_fault() called from restore_regs_and_return_to_kernel(). I saw this very same behavior in your v3 branch (kaiser-414-tipwip-20171121) too. > > The crashes are followed by a machine halt via NMI. They also get the following warning: > WARNING: can't dereference iret registers at fffffffffe198048 for ip page_fault+0x11/0x60 There was a known bug in my branch with not mapping some of the interrupt entry routines. Random alignment makes it break or work. Ingo/Thomas, correct me if I'm wrong, but I think we need folks testing here at the moment: > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=auto-latest My tree from last week is ancient gunk at this point. :)
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave.hansen@linux.intel.com> To: lkp@lists.01.org Subject: Re: 2f47e7e19f ("x86/mm/kaiser: Use PCID feature to make user and .."): WARNING: CPU: 0 PID: 1 at mm/early_ioremap.c:114 __early_ioremap Date: Mon, 27 Nov 2017 10:28:35 -0800 [thread overview] Message-ID: <f5382aac-3714-e1e2-8ac9-94b23bd8fe6e@linux.intel.com> (raw) In-Reply-To: <20171127180328.GA12661@u40b0340c692b58f6553c.ant.amazon.com> [-- Attachment #1: Type: text/plain, Size: 1068 bytes --] On 11/27/2017 10:03 AM, Eduardo Valentin wrote: > On top of VM crashes, on your branch: > https://git.kernel.org/pub/scm/linux/kernel/git/daveh/x86-kaiser.git/log/?h=kaiser-414-tipwip-20171123 > > I am also getting crashes in early userspace, during tlb flushes. When KAISER is enabled and whenever userspace is loaded, I get a stack trace around __do_page_fault() called from restore_regs_and_return_to_kernel(). I saw this very same behavior in your v3 branch (kaiser-414-tipwip-20171121) too. > > The crashes are followed by a machine halt via NMI. They also get the following warning: > WARNING: can't dereference iret registers at fffffffffe198048 for ip page_fault+0x11/0x60 There was a known bug in my branch with not mapping some of the interrupt entry routines. Random alignment makes it break or work. Ingo/Thomas, correct me if I'm wrong, but I think we need folks testing here at the moment: > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=auto-latest My tree from last week is ancient gunk at this point. :)
next prev parent reply other threads:[~2017-11-27 18:28 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-26 11:49 2f47e7e19f ("x86/mm/kaiser: Use PCID feature to make user and .."): WARNING: CPU: 0 PID: 1 at mm/early_ioremap.c:114 __early_ioremap kernel test robot 2017-11-26 11:49 ` kernel test robot 2017-11-27 10:18 ` Ingo Molnar 2017-11-27 10:18 ` Ingo Molnar 2017-11-27 14:51 ` Dave Hansen 2017-11-27 14:51 ` Dave Hansen 2017-11-27 18:03 ` Eduardo Valentin 2017-11-27 18:28 ` Dave Hansen [this message] 2017-11-27 18:28 ` Dave Hansen 2017-11-27 19:08 ` Eduardo Valentin 2017-11-27 16:14 ` Dave Hansen 2017-11-27 16:14 ` Dave Hansen 2017-11-27 22:13 ` Rafael J. Wysocki 2017-11-27 22:13 ` Rafael J. Wysocki 2017-11-27 22:33 ` Rafael J. Wysocki 2017-11-27 22:33 ` Rafael J. Wysocki 2017-11-28 1:22 ` Dave Hansen 2017-11-28 1:22 ` Dave Hansen
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=f5382aac-3714-e1e2-8ac9-94b23bd8fe6e@linux.intel.com \ --to=dave.hansen@linux.intel.com \ --cc=aliguori@amazon.com \ --cc=eduval@amazon.com \ --cc=fengguang.wu@intel.com \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lkp@01.org \ --cc=mingo@kernel.org \ --cc=tglx@linutronix.de \ --cc=wfg@linux.intel.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.