Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1439152

Re: [PATCH v2] kexec: Fix kdump failure with notsc

From Ingo Molnar <mingo@kernel.org>
Newsgroups linux.kernel
Subject Re: [PATCH v2] kexec: Fix kdump failure with notsc
Date 2016-07-08 09:40 +0200
Message-ID <rSyyd-1Gq-1@gated-at.bofh.it> (permalink)
References <rSeJc-5D9-29@gated-at.bofh.it> <rSlUm-20z-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


* Eric W. Biederman <ebiederm@xmission.com> wrote:

> Sigh.  Can we please just do the work to rip out the apic shutdown code from the 
> kexec on panic code path?
> 
> I forgetting details but the only reason we have do any apic shutdown is bugs in 
> older kernels that could not initialize a system properly if we did not shut 
> down the apics.
> 
> I certainly don't see an issue with goofy cases like notsc not working on a 
> crash capture kernel if we are not initializing the hardware properly.
> 
> The strategy really needs to be to only do the absolutely essential hardware 
> shutdown in the crashing kernel, every adintional line of code we execute in the 
> crashing kernel increases our chances of hitting a bug.

Fully agreed.

> Under that policy things like requring we don't pass boot options that inhibit 
> the dump catpure kernel from initializing the hardware from a random state are 
> reasonable requirements.  AKA I don't see any justification in this as to why we 
> would even want to support notsc on the dump capture kernel.  Especially when 
> things clearly work when that option is not specified.

So at least on the surface it appears 'surprising' that the 'notsc' option (which, 
supposedly, disables TSC handling) interferes with being able to fully boot. Even 
if 'notsc' is specified we are still using the local APIC, right?

So it might be a good idea to find the root cause of this bootup fragility even if 
'notsc' is specified. And I fully agree that it should be fixed in the bootup path 
of the dump kernel, not the crash kernel reboot path.

Thanks,

	Ingo

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH v2] kexec: Fix kdump failure with notsc Wei Jiangang <weijg.fnst@cn.fujitsu.com> - 2016-07-07 12:30 +0200
  Re: [PATCH v2] kexec: Fix kdump failure with notsc ebiederm@xmission.com (Eric W. Biederman) - 2016-07-07 20:10 +0200
    Re: [PATCH v2] kexec: Fix kdump failure with notsc "Wei, Jiangang" <weijg.fnst@cn.fujitsu.com> - 2016-07-08 06:50 +0200
    Re: [PATCH v2] kexec: Fix kdump failure with notsc Ingo Molnar <mingo@kernel.org> - 2016-07-08 09:40 +0200
  Re: [PATCH v2] kexec: Fix kdump failure with notsc Nikolay Borisov <kernel@kyup.com> - 2016-07-08 10:30 +0200

csiph-web