mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <waiman.long@hpe.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"Theodore Ts'o" <tytso@mit.edu>, Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Scott J Norton <scott.norton@hpe.com>,
	Douglas Hatch <doug.hatch@hpe.com>, Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH] random: Fix kernel panic due to system_wq use before init
Date: Mon, 19 Sep 2016 10:48:12 -0400	[thread overview]
Message-ID: <57DFFAAC.4010108@hpe.com> (raw)
In-Reply-To: <20160919124325.GE2892@codeblueprint.co.uk>

On 09/19/2016 08:43 AM, Matt Fleming wrote:
> On Sun, 18 Sep, at 11:09:08PM, Waiman Long wrote:
>> On 09/14/2016 03:19 PM, Linus Torvalds wrote:
>>> On Wed, Sep 14, 2016 at 12:14 PM, Waiman Long<waiman.long@hpe.com>   wrote:
>>>> In the stack backtrace above, the kernel hadn't even reached SMP boot after
>>>> about 50s. That was extremely slow. I tried the 4.7.3 kernel and it booted
>>>> up fine. So I suspect that there may be too many interrupts going on and it
>>>> consumes most of the CPU cycles. The prime suspect is the random driver, I
>>>> think.
>>> Any chance of bisecting it at least partially? The random driver
>>> doesn't do interrupts itself, it just gets called by other drivers
>>> doing intterrupts. So if there are too many of them, that would be
>>> something else..
>>>
>>>                 Linus
>> I have finally finished bisecting the problem. I was wrong in saying that
>> the 4.7.3 kernel had no problem. It did have. There were some slight
>> differences between the 4.8 and 4.7 kernel config files that I used. After
>> some further testing, it was found that the bootup problem only happened
>> when the following kernel config option was defined:
>>
>> CONFIG_EFI_MIXED=y
>
> Could you try this patch? It won't be the final version, because it
> doesn't address the root cause of the crash, which looks like page
> table corruption of some kind, but it should at least confirm that
> this is the buggy code,
>
> ---
>
> diff --git a/arch/x86/platform/efi/efi_64.c b/arch/x86/platform/efi/efi_64.c
> index 677e29e29473..8dd3784eb075 100644
> --- a/arch/x86/platform/efi/efi_64.c
> +++ b/arch/x86/platform/efi/efi_64.c
> @@ -245,7 +245,7 @@ int __init efi_setup_page_tables(unsigned long pa_memmap, unsigned num_pages)
>   	 * text and allocate a new stack because we can't rely on the
>   	 * stack pointer being<  4GB.
>   	 */
> -	if (!IS_ENABLED(CONFIG_EFI_MIXED))
> +	if (!IS_ENABLED(CONFIG_EFI_MIXED) || efi_is_native())
>   		return 0;
>
>   	/*

With this patch applied, I am able to successfully boot both the 
16-socket 12-TB and 8-socket 6TB configurations without problem.

Tested-by: Waiman Long <Waiman.Long@hpe.com>

  reply	other threads:[~2016-09-19 14:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 19:03 Waiman Long
2016-09-14 19:14 ` Linus Torvalds
2016-09-14 19:24   ` Waiman Long
2016-09-14 19:55   ` Tejun Heo
2016-09-14 22:26     ` Tejun Heo
2016-09-14 19:14 ` Waiman Long
2016-09-14 19:19   ` Linus Torvalds
2016-09-14 19:34     ` Waiman Long
2016-09-14 21:06       ` Linus Torvalds
2016-09-14 22:15         ` Waiman Long
2016-09-19  3:09     ` Waiman Long
2016-09-19  9:25       ` Matt Fleming
2016-09-19 12:43       ` Matt Fleming
2016-09-19 14:48         ` Waiman Long [this message]
2016-09-19 14:51           ` Matt Fleming
2016-09-19 17:09             ` Waiman Long
2016-09-20 14:04               ` Matt Fleming

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=57DFFAAC.4010108@hpe.com \
    --to=waiman.long@hpe.com \
    --cc=arnd@arndb.de \
    --cc=bp@suse.de \
    --cc=doug.hatch@hpe.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=scott.norton@hpe.com \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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

Powered by JetHome