From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751752AbdBLWVT (ORCPT ); Sun, 12 Feb 2017 17:21:19 -0500 Received: from mail-wr0-f194.google.com ([209.85.128.194]:34116 "EHLO mail-wr0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751418AbdBLWVR (ORCPT ); Sun, 12 Feb 2017 17:21:17 -0500 Subject: Re: Linux 4.9.6 ( Restore IO-APIC irq_chip retrigger callback , breaks my box ) To: Borislav Petkov References: <1e88cc0e-4d34-a314-a44f-8324335b79e3@gmail.com> <73c6bd86-3ebb-c6db-b522-47a48b847227@gmail.com> <20170211142059.447eo6bgxycmp6kb@pd.tnic> <20170211213221.p6xs6c7qccz2w42r@pd.tnic> <0da9ef61-f3ee-13a8-2877-c235d710c50f@gmail.com> <20170212211228.iycyl76o4auxk2jy@pd.tnic> Cc: Thomas Gleixner , Linus Torvalds , Greg KH , Linux Kernel Mailing List , Andrew Morton , stable , lwn@lwn.net, Jiri Slaby , Ruslan Ruslichenko From: Gabriel C Message-ID: Date: Sun, 12 Feb 2017 23:21:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <20170212211228.iycyl76o4auxk2jy@pd.tnic> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12.02.2017 22:12, Borislav Petkov wrote: > 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. There are both videos .. however the output seems kind same this time.. http://ftp.frugalware.org/pub/other/people/crazy/kernel/t/crash_initcall_debug.mp4 http://ftp.frugalware.org/pub/other/people/crazy/kernel/t/crash_intcall_debug_ucode_off.mp4 I try to find out more tomorrow but right now I don't even have a clue where to add some printk's to get some more output :(