Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 17:04 -0800, Dave Hansen пишет: > On 12/29/2017 10:46 AM, Alexander Tsoy wrote: > > В Пт, 29/12/2017 в 09:32 -0800, Dave Hansen пишет: > > > Does anyone have the results of build that they can > > > share?  (vmlinux, > > > vmlinuz/bzImage, System.map, .config).  That, plus a > >

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 17:04 -0800, Dave Hansen пишет: > On 12/29/2017 10:46 AM, Alexander Tsoy wrote: > > В Пт, 29/12/2017 в 09:32 -0800, Dave Hansen пишет: > > > Does anyone have the results of build that they can > > > share?  (vmlinux, > > > vmlinuz/bzImage, System.map, .config).  That, plus a > >

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Dave Hansen
On 12/29/2017 10:46 AM, Alexander Tsoy wrote: > В Пт, 29/12/2017 в 09:32 -0800, Dave Hansen пишет: >> Does anyone have the results of build that they can share?  (vmlinux, >> vmlinuz/bzImage, System.map, .config).  That, plus a corresponding >> serial log with an oops would be helpful. > > Here

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Dave Hansen
On 12/29/2017 10:46 AM, Alexander Tsoy wrote: > В Пт, 29/12/2017 в 09:32 -0800, Dave Hansen пишет: >> Does anyone have the results of build that they can share?  (vmlinux, >> vmlinuz/bzImage, System.map, .config).  That, plus a corresponding >> serial log with an oops would be helpful. > > Here

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Linus Torvalds
On Fri, Dec 29, 2017 at 3:15 PM, Alexander Tsoy wrote: > В Пт, 29/12/2017 в 14:09 -0800, Linus Torvalds пишет: >> >> What happens if you take a failing kernel, and then in >> arch/x86/kernel/traps.c do_double_fault(), you change the >> >> #ifdef CONFIG_X86_ESPFIX64 >> >> to

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Linus Torvalds
On Fri, Dec 29, 2017 at 3:15 PM, Alexander Tsoy wrote: > В Пт, 29/12/2017 в 14:09 -0800, Linus Torvalds пишет: >> >> What happens if you take a failing kernel, and then in >> arch/x86/kernel/traps.c do_double_fault(), you change the >> >> #ifdef CONFIG_X86_ESPFIX64 >> >> to just a >> >> #if 0

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 14:09 -0800, Linus Torvalds пишет: > ... > The fact that double faults seem to be implicated does make me want > to > try to disable that ESPFIX64 code in the #DF handler. > > What happens if you take a failing kernel, and then in > arch/x86/kernel/traps.c do_double_fault(),

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 14:09 -0800, Linus Torvalds пишет: > ... > The fact that double faults seem to be implicated does make me want > to > try to disable that ESPFIX64 code in the #DF handler. > > What happens if you take a failing kernel, and then in > arch/x86/kernel/traps.c do_double_fault(),

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Linus Torvalds
On Fri, Dec 29, 2017 at 1:50 PM, Alexander Tsoy wrote: >> >> Ho humm. What happens if you change the "-march=core2" to >> "-mtune=core2"? Does it still boot? > > That's interesting. Compiled with -mtune=core2, the kernel fails to > boot. [ Insert "twilight zone" theme music ]

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Linus Torvalds
On Fri, Dec 29, 2017 at 1:50 PM, Alexander Tsoy wrote: >> >> Ho humm. What happens if you change the "-march=core2" to >> "-mtune=core2"? Does it still boot? > > That's interesting. Compiled with -mtune=core2, the kernel fails to > boot. [ Insert "twilight zone" theme music ] Damn. I was hoping

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 12:34 -0800, Linus Torvalds пишет: > On Fri, Dec 29, 2017 at 12:22 PM, Alexander Tsoy > wrote: > > > But double-checking that "-march=core2" case is definitely worth > > > looking into. Especially since there are clear indications that > > > it's > > > gcc

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 12:34 -0800, Linus Torvalds пишет: > On Fri, Dec 29, 2017 at 12:22 PM, Alexander Tsoy > wrote: > > > But double-checking that "-march=core2" case is definitely worth > > > looking into. Especially since there are clear indications that > > > it's > > > gcc version-dependent

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Linus Torvalds
On Fri, Dec 29, 2017 at 12:22 PM, Alexander Tsoy wrote: >> But double-checking that "-march=core2" case is definitely worth >> looking into. Especially since there are clear indications that it's >> gcc version-dependent anyway. Alexander? > > Yes, the change suggested by Dave

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Linus Torvalds
On Fri, Dec 29, 2017 at 12:22 PM, Alexander Tsoy wrote: >> But double-checking that "-march=core2" case is definitely worth >> looking into. Especially since there are clear indications that it's >> gcc version-dependent anyway. Alexander? > > Yes, the change suggested by Dave makes the problem

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 11:31 -0800, Linus Torvalds пишет: > On Fri, Dec 29, 2017 at 9:32 AM, Dave Hansen > --->%--- > > > > MCORE2 seems to get one oddball compiler flag (-march=core2): > > > > > cflags-$(CONFIG_MCORE2) += \ > > >

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 11:31 -0800, Linus Torvalds пишет: > On Fri, Dec 29, 2017 at 9:32 AM, Dave Hansen > --->%--- > > > > MCORE2 seems to get one oddball compiler flag (-march=core2): > > > > > cflags-$(CONFIG_MCORE2) += \ > > > $(call

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Linus Torvalds
On Fri, Dec 29, 2017 at 9:32 AM, Dave Hansen wrote: > > From the various oopses, it looks like this happens when getting a > double fault while trying to go idle. The CPU gets is probably trying > to return from the double fault, but it didn't do anything useful in the >

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Linus Torvalds
On Fri, Dec 29, 2017 at 9:32 AM, Dave Hansen wrote: > > From the various oopses, it looks like this happens when getting a > double fault while trying to go idle. The CPU gets is probably trying > to return from the double fault, but it didn't do anything useful in the > fault handler so it just

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 09:32 -0800, Dave Hansen пишет: > Does anyone have the results of build that they can share?  (vmlinux, > vmlinuz/bzImage, System.map, .config).  That, plus a corresponding > serial log with an oops would be helpful. Here you are:

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 09:32 -0800, Dave Hansen пишет: > Does anyone have the results of build that they can share?  (vmlinux, > vmlinuz/bzImage, System.map, .config).  That, plus a corresponding > serial log with an oops would be helpful. Here you are:

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Dave Hansen
Does anyone have the results of build that they can share? (vmlinux, vmlinuz/bzImage, System.map, .config). That, plus a corresponding serial log with an oops would be helpful. I tried just adding MCORE2=y to my normal config but it didn't reproduce this. If you can't send the entire build

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Dave Hansen
Does anyone have the results of build that they can share? (vmlinux, vmlinuz/bzImage, System.map, .config). That, plus a corresponding serial log with an oops would be helpful. I tried just adding MCORE2=y to my normal config but it didn't reproduce this. If you can't send the entire build

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 17:11 +0100, Thomas Gleixner пишет: > On Fri, 29 Dec 2017, Alexander Tsoy wrote: > > > Just tested Linus's master branch and it have the same problem. > > > All I > > > can catch with a serial console is the following: > > > > > So for completeness sake: > >       

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 17:11 +0100, Thomas Gleixner пишет: > On Fri, 29 Dec 2017, Alexander Tsoy wrote: > > > Just tested Linus's master branch and it have the same problem. > > > All I > > > can catch with a serial console is the following: > > > > > So for completeness sake: > >       

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Thomas Gleixner
On Fri, 29 Dec 2017, Alexander Tsoy wrote: > > Just tested Linus's master branch and it have the same problem. All I > > can catch with a serial console is the following: > > So for completeness sake: MCORE2=y MCORE2=n GCC5.xworks works GCC6.xfail works

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Thomas Gleixner
On Fri, 29 Dec 2017, Alexander Tsoy wrote: > > Just tested Linus's master branch and it have the same problem. All I > > can catch with a serial console is the following: > > So for completeness sake: MCORE2=y MCORE2=n GCC5.xworks works GCC6.xfail works

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 17:31 +0300, Alexander Tsoy пишет: > В Пт, 29/12/2017 в 10:17 +0100, Greg KH пишет: > > On Thu, Dec 28, 2017 at 12:33:22PM +0300, Alexander Tsoy wrote: > > > Hello, > > > > > > 4.14.9 fails to boot if CONFIG_MCORE2 is enabled and when &

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 17:31 +0300, Alexander Tsoy пишет: > В Пт, 29/12/2017 в 10:17 +0100, Greg KH пишет: > > On Thu, Dec 28, 2017 at 12:33:22PM +0300, Alexander Tsoy wrote: > > > Hello, > > > > > > 4.14.9 fails to boot if CONFIG_MCORE2 is enabled and when &

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 10:17 +0100, Greg KH пишет: > On Thu, Dec 28, 2017 at 12:33:22PM +0300, Alexander Tsoy wrote: > > Hello, > > > > 4.14.9 fails to boot if CONFIG_MCORE2 is enabled and when compiled > > with > > gcc 6+. More details in the following bug reports

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Alexander Tsoy
В Пт, 29/12/2017 в 10:17 +0100, Greg KH пишет: > On Thu, Dec 28, 2017 at 12:33:22PM +0300, Alexander Tsoy wrote: > > Hello, > > > > 4.14.9 fails to boot if CONFIG_MCORE2 is enabled and when compiled > > with > > gcc 6+. More details in the following bug reports

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Greg KH
On Thu, Dec 28, 2017 at 12:33:22PM +0300, Alexander Tsoy wrote: > Hello, > > 4.14.9 fails to boot if CONFIG_MCORE2 is enabled and when compiled with > gcc 6+. More details in the following bug reports: > https://bugzilla.kernel.org/show_bug.cgi?id=198263 > https://bugs.gentoo

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-29 Thread Greg KH
On Thu, Dec 28, 2017 at 12:33:22PM +0300, Alexander Tsoy wrote: > Hello, > > 4.14.9 fails to boot if CONFIG_MCORE2 is enabled and when compiled with > gcc 6+. More details in the following bug reports: > https://bugzilla.kernel.org/show_bug.cgi?id=198263 > https://bugs.gentoo

4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-28 Thread Alexander Tsoy
Hello, 4.14.9 fails to boot if CONFIG_MCORE2 is enabled and when compiled with gcc 6+. More details in the following bug reports: https://bugzilla.kernel.org/show_bug.cgi?id=198263 https://bugs.gentoo.org/642268 I bisected it to the commit below: $ git bisect good

4.14.9 with CONFIG_MCORE2 fails to boot

2017-12-28 Thread Alexander Tsoy
Hello, 4.14.9 fails to boot if CONFIG_MCORE2 is enabled and when compiled with gcc 6+. More details in the following bug reports: https://bugzilla.kernel.org/show_bug.cgi?id=198263 https://bugs.gentoo.org/642268 I bisected it to the commit below: $ git bisect good