Re: 4.14.9 doesn't boot (regression)

В Sat, 30 Dec 2017 11:57:46 -0600 Josh Poimboeuf <jpoim...@redhat.com> пишет: > On Sat, Dec 30, 2017 at 11:09:46AM -0600, Josh Poimboeuf wrote: > > On Sat, Dec 30, 2017 at 11:45:13AM +0300, Alexander Tsoy wrote: > > > В Пт, 29/12/2017 в 21:49 -0600, Josh Poimboeuf пише

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 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 doesn't boot (regression)

В Пт, 29/12/2017 в 12:14 +0100, Toralf Förster пишет: > I can confirm now, that that kernel breaks both a desktop (an > ThinkPad T440s i5) and a headless server (i3930) setup. For the > server the attached .config works fine but switching from > CONFIG_GENERIC_CPU to CONFIG_MCORE2 legt them hang

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 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

В Пт, 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: > &

Re: 4.14.9 doesn't boot (regression)

В Пт, 29/12/2017 в 13:39 -0800, Linus Torvalds пишет: > On Fri, Dec 29, 2017 at 1:17 PM, Linus Torvalds > wrote: > > > > Yeah, other reporters of this have used gcc-6.4.0 too. > > > > But there's been some muddying of the waters there too - changing > > compilers

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 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

В Пт, 29/12/2017 в 12:34 -0800, Linus Torvalds пишет: > On Fri, Dec 29, 2017 at 12:22 PM, Alexander Tsoy <alexan...@tsoy.me> > wrote: > > > But double-checking that "-march=core2" case is definitely worth > > > looking into. Especially since there are cle

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 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

В Пт, 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/bzImag

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 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 doesn't boot (regression)

В Пт, 29/12/2017 в 17:10 -0700, Andy Lutomirski пишет: > > Also, you wouldn't happen to be using Gentoo perchance?  I already > have two reports of a Gentoo system miscompiling the vDSO due to > Gentoo enabling -fstack-check and GCC generating stack check code > that is highly suboptimal,

Re: 4.14.9 doesn't boot (regression)

В Пт, 29/12/2017 в 21:49 -0600, Josh Poimboeuf пишет: > On Fri, Dec 29, 2017 at 05:10:35PM -0700, Andy Lutomirski wrote: > > (Also, Josh, the oops code should have printed the contents of the > > struct pt_regs at the top of the DF stack.  Any idea why it > > didn't?) > > Looking at one of the

Re: 4.14.9 doesn't boot (regression)

В Пт, 29/12/2017 в 17:34 -0800, Linus Torvalds пишет: > On Fri, Dec 29, 2017 at 5:00 PM, Linus Torvalds > wrote: > > > > Good. I was not feeling so happy about this bug report, but now I > > can > > firmly just blame the gentoo compiler for having some shit-for- >

4.14.9 with CONFIG_MCORE2 fails to boot

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

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

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 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

В Пт, 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 doesn't boot (regression)

В Пт, 29/12/2017 в 12:14 +0100, Toralf Förster пишет: > I can confirm now, that that kernel breaks both a desktop (an > ThinkPad T440s i5) and a headless server (i3930) setup. For the > server the attached .config works fine but switching from > CONFIG_GENERIC_CPU to CONFIG_MCORE2 legt them hang

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 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: > &

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 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

В Пт, 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

В Пт, 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 >

Re: 4.14.9 doesn't boot (regression)

В Пт, 29/12/2017 в 13:39 -0800, Linus Torvalds пишет: > On Fri, Dec 29, 2017 at 1:17 PM, Linus Torvalds > wrote: > > > > Yeah, other reporters of this have used gcc-6.4.0 too. > > > > But there's been some muddying of the waters there too - changing > > compilers have fixed it for some cases,

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 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 doesn't boot (regression)

В Пт, 29/12/2017 в 17:10 -0700, Andy Lutomirski пишет: > > Also, you wouldn't happen to be using Gentoo perchance?  I already > have two reports of a Gentoo system miscompiling the vDSO due to > Gentoo enabling -fstack-check and GCC generating stack check code > that is highly suboptimal,

Re: 4.14.9 with CONFIG_MCORE2 fails to boot

В Пт, 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/bzImag

Re: 4.14.9 doesn't boot (regression)

В Пт, 29/12/2017 в 21:49 -0600, Josh Poimboeuf пишет: > On Fri, Dec 29, 2017 at 05:10:35PM -0700, Andy Lutomirski wrote: > > (Also, Josh, the oops code should have printed the contents of the > > struct pt_regs at the top of the DF stack.  Any idea why it > > didn't?) > > Looking at one of the

Re: 4.14.9 doesn't boot (regression)

В Пт, 29/12/2017 в 17:34 -0800, Linus Torvalds пишет: > On Fri, Dec 29, 2017 at 5:00 PM, Linus Torvalds > wrote: > > > > Good. I was not feeling so happy about this bug report, but now I > > can > > firmly just blame the gentoo compiler for having some shit-for- > > brains > > "feature". > >

Re: 4.14.9 doesn't boot (regression)

В Sat, 30 Dec 2017 11:57:46 -0600 Josh Poimboeuf пишет: > On Sat, Dec 30, 2017 at 11:09:46AM -0600, Josh Poimboeuf wrote: > > On Sat, Dec 30, 2017 at 11:45:13AM +0300, Alexander Tsoy wrote: > > > В Пт, 29/12/2017 в 21:49 -0600, Josh Poimboeuf пишет: > > > > On F

[PATCH] Input: joydev - extend absolute mouse detection

Extend event signature matching to catch more input devices emulated by BMC firmwares, QEMU and VMware. Signed-off-by: Alexander Tsoy --- drivers/input/joydev.c | 24 ++-- 1 file changed, 22 insertions(+), 2 deletions(-) diff --git a/drivers/input/joydev.c b/drivers/input

Re: [PATCH 4.9 026/191] ALSA: usb-audio: Improve frames size computation

В Пн, 29/06/2020 в 11:37 -0400, Sasha Levin пишет: > From: Alexander Tsoy > > [ Upstream commit f0bd62b64016508938df9babe47f65c2c727d25c ] > > For computation of the the next frame size current value of fs/fps > and > accumulated fractional parts of fs/fps are used, wher

Re: Beginning 5.8rc1 kernel USB headsets (ASUS ROG Delta and HyperX Cloud Orbit S) play sound as if in slow-motion.

В Пт, 10/07/2020 в 10:46 +0500, Mikhail Gavrilov пишет: > Beginning 5.8rc1 (git 69119673bd50) kernel USB headsets (ASUS ROG > Delta and HyperX Cloud Orbit S) play sound as if in slow-motion. > > And in 5.8rc4 (git dcde237b9b0e) this still not fixed yet. > The bisecting is problematic because rc1