[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFz+moL9zem-gGnRtGSzYV0yL+GoA=3+XrUZy9t=cmhBhw@mail.gmail.com>
Date: Fri, 29 Dec 2017 12:12:38 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Toralf Förster <toralf.foerster@....de>,
Andy Lutomirski <luto@...capital.net>
Cc: stable <stable@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: 4.14.9 doesn't boot (regression)
On Fri, Dec 29, 2017 at 3:14 AM, Toralf Förster <toralf.foerster@....de> wrote:
>
> For the server the attached .config works fine but switching from
> CONFIG_GENERIC_CPU to CONFIG_MCORE2 legt them hang at boot w/op any
> messages. Similar picture at the desktop.
Ok, so there's another thread ("4.14.9 with CONFIG_MCORE2 fails to
boot") about this same thing, but one thing to try is to see if it's
just the
cflags-$(CONFIG_MCORE2) += \
$(call cc-option,-march=core2,$(call cc-option,-mtune=generic))
in arch/x86/Makefile that causes this.
The MCORE2 option does potentially have a few other effects (see
arch/x86/Kconfig.cpu), but the first one to check might be just that
compiler command line effect.
So if you can edit arch/x86/Makefile, and just make that say
cflags-$(CONFIG_MCORE2) += $(call cc-option,-mtune=generic)
instead, and see if that makes a difference, that would narrow down
the possible root cause of this problem.
Linus
Powered by blists - more mailing lists