From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751660AbdBEBXA (ORCPT ); Sat, 4 Feb 2017 20:23:00 -0500 Received: from bh-25.webhostbox.net ([208.91.199.152]:58981 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751033AbdBEBW7 (ORCPT ); Sat, 4 Feb 2017 20:22:59 -0500 Subject: Re: Regression on next-20170203 spi/for-next 3f87493930a0f qemu on x86_64 To: "Luis R. Rodriguez" , Stephen Rothwell , Mark Brown References: Cc: Fengguang Wu , "linux-kernel@vger.kernel.org" , X86 ML , Andy Lutomirski , Borislav Petkov From: Guenter Roeck Message-ID: <99a373c8-2ae2-677a-4053-4b3f7273635f@roeck-us.net> Date: Sat, 4 Feb 2017 17:22:55 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: authenticated_id: linux@roeck-us.net X-Authenticated-Sender: bh-25.webhostbox.net: linux@roeck-us.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/04/2017 12:05 PM, Luis R. Rodriguez wrote: > I could not boot next-20170203 on my x86_64 qemu instance. It stalls at: > > [ 0.015549] CPU: Physical Processor ID: 0 > [ 0.015842] mce: CPU supports 10 MCE banks > [ 0.016032] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0 > [ 0.016393] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0 > [ 0.016871] Freeing SMP alternatives memory: 24K > [ 0.017710] ftrace: allocating 25888 entries in 102 pages > [ 0.024102] smpboot: Max logical packages: 4 > [ 0.024524] x2apic enabled > [ 0.024851] Switched APIC routing to physical x2apic. > [ 0.025755] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 > There may be a possible problem or change in the timer code. For the most part the "kvm64" cpu works for me, but I saw this once: smpboot: Max logical packages: 1 ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 ..MP-BIOS bug: 8254 timer not connected to IO-APIC ...trying to set up timer (IRQ0) through the 8259A ... ..... (found apic 0 pin 2) ... ....... failed. ...trying to set up timer as Virtual Wire IRQ... ..... failed. ...trying to set up timer as ExtINT IRQ... ..... failed :(. Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. The "normal" log with -next looks as follows: smpboot: Max logical packages: 4 ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 ..MP-BIOS bug: 8254 timer not connected to IO-APIC ...trying to set up timer (IRQ0) through the 8259A ... ..... (found apic 0 pin 2) ... ....... failed. ...trying to set up timer as Virtual Wire IRQ... ..... failed. ...trying to set up timer as ExtINT IRQ... ..... works. Upstream (v4.10-rc6-193-ga572a1b99948), the same command yields no error at all: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 smpboot: CPU0: Intel Common KVM processor (family: 0xf, model: 0x6, stepping: 0x1) The "new" error message is also seen with other CPUs, not just with "kvm64". I am using qemu 2.8. Maybe we should try to figure out where the new error messages come from ? Thanks, Guenter