Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1756729Ab3D3Vhb (ORCPT <rfc822;w@1wt.eu>);
	Tue, 30 Apr 2013 17:37:31 -0400
Received: from mx1.redhat.com ([209.132.183.28]:23473 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751268Ab3D3Vh0 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 30 Apr 2013 17:37:26 -0400
Date: Tue, 30 Apr 2013 17:37:19 -0400
From: Dave Jones <davej@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
        Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: clockevents_program_event WARN_ON preventing boot.
Message-ID: <20130430213719.GA14988@redhat.com>
Mail-Followup-To: Dave Jones <davej@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>
References: <20130430212007.GB18598@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130430212007.GB18598@redhat.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1711
Lines: 56

On Tue, Apr 30, 2013 at 05:20:07PM -0400, Dave Jones wrote:
 > I have a machine that crashes instantly on boot up on Linus'
 > post-3.9 tree. (8c55f1463c1fd318d5e785f02b80bcc32176d342)
 > 
 > By booting with boot_delay=100, I was able to take a photo
 > and capture the top of the trace.  (For some reason, larger boot
 > delay parameters seem to make it take forever before printing
 > even a single character, which made this a pain to debug).
 > 
 > The WARN_ON it prints right before locking up is this in clockevents_program_event
 > 
 > 208         if (unlikely(expires.tv64 < 0)) {
 > 209                 WARN_ON_ONCE(1);
 > 210                 return -ETIME;
 > 211         }
 > 
 > booting with maxcpus=1 avoids the problem.
 > 
 > I'm still trying to get a complete stack trace, though it's painful
 > due to the above reason.

On a second machine, I'm seeing an oops even earlier. As soon as I
exit grub, I get a blinking cursor.  If I boot with earlyprintk=vga
I can see..

Call Trace:
 <IRQ>
  tick_check_oneshot_broadcast
  tick_check_idle
  irq_enter
  do_IRQ
  common_interrupt
 <EOI>
  x86_64_start_reservations
  x86_64_start_kernel
RIP: clockevents_set_mode+0x18

Matching up the Code: line of the trace with the disassembly I see..

        if (dev->mode != mode) {
 4c8:   39 77 38                cmp    %esi,0x38(%rdi)


the comment above that code is telling..

/*
 * Must be called with interrupts disabled !
 */

So how did we get an IRQ ?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/