[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170212211228.iycyl76o4auxk2jy@pd.tnic>
Date: Sun, 12 Feb 2017 22:12:28 +0100
From: Borislav Petkov <bp@...en8.de>
To: Gabriel C <nix.or.die@...il.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg KH <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
stable <stable@...r.kernel.org>, lwn@....net,
Jiri Slaby <jslaby@...e.cz>,
Ruslan Ruslichenko <rruslich@...co.com>
Subject: Re: Linux 4.9.6 ( Restore IO-APIC irq_chip retrigger callback ,
breaks my box )
On Sun, Feb 12, 2017 at 09:21:53PM +0100, Gabriel C wrote:
> There is what I get :
>
> http://ftp.frugalware.org/pub/other/people/crazy/kernel/t/crash2.mp4
Ok, I'm watching it frame-by-frame. I can see the microcode getting
updated to revision 0x19 as in your working dmesg.
The machine hangs here at the
clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x20ac7f6ecc6, max_idle_ns: 440795315461 ns
line too. The exact same numbers even as in the previous run! Strange.
> With dis_ucode_ldr there is some more output , with it will stay like this , nothing more.
Ok, can you do redo the first video but with "initcall_debug" on the
kernel command line?
And then do video of another run with "initcall_debug dis_ucode_ldr" on
the kernel command line?
I'd like to see which of the initcalls doesn't return.
Thanks!
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists