From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fengguang Wu Subject: Re: 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. Date: Tue, 4 Jun 2013 08:43:19 +0800 Message-ID: <20130604004319.GA11618@localhost> References: <20130602042033.GB16050@localhost> <51AC7B2C.5000204@intel.com> <20130603112624.GA7623@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mga01.intel.com ([192.55.52.88]:4799 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756101Ab3FDAnX (ORCPT ); Mon, 3 Jun 2013 20:43:23 -0400 Content-Disposition: inline In-Reply-To: <20130603112624.GA7623@localhost> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: "Rafael J. Wysocki" Cc: linux-acpi@vger.kernel.org On Mon, Jun 03, 2013 at 07:26:24PM +0800, Fengguang Wu wrote: > On Mon, Jun 03, 2013 at 01:17:00PM +0200, Rafael J. Wysocki wrote: > > On 6/2/2013 6:20 AM, Fengguang Wu wrote: > > >Greetings, > > > > > >FYI, I got this occasionally in some of my machines when testing the > > >pm/bleeding-edge branch: > > > > > >[ 0.040000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 > > >[ 0.044000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC > > >[ 0.044000] ...trying to set up timer (IRQ0) through the 8259A ... > > >[ 0.044000] ..... (found apic 0 pin 2) ... > > >[ 0.048000] ....... failed. > > >[ 0.048000] ...trying to set up timer as Virtual Wire IRQ... > > >[ 0.048000] ..... failed. > > >[ 0.048000] ...trying to set up timer as ExtINT IRQ... > > >[ 0.052000] ..... failed :(. > > >[ 0.052000] 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. > > > > > >Bisect result is unfortunately not reliable.. > > > > Can you please check if this is reproducible with the acpi-hotplug > > branch alone? > > Nope, it also shows up in upstream kernel. Sorry.. I'll try more bisect. FYI, linux-next boots fine, so it should have been fixed somewhere. Sorry for the noises! Thanks, Fengguang