public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <ak@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents
Date: Tue, 25 Sep 2007 22:07:01 +0200	[thread overview]
Message-ID: <200709252207.02532.rjw@sisk.pl> (raw)
In-Reply-To: <1190726273.4035.331.camel@chaos>

[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]

On Tuesday, 25 September 2007 15:17, Thomas Gleixner wrote:
> On Tue, 2007-09-25 at 15:16 +0200, Rafael J. Wysocki wrote:
[--snip--]
> 
> I start to get desperate. Below is a patch, which moves the apic timer
> disable check after the calibration routine. Can you please apply on top
> of -hrt and add "noapictimer" to the command line ? Does it boot ?

2.6.23-rc7 with patch-2.6.23-rc7-hrt1.patch and the patch below applied boots
with noapictimer and doesn't boot without it.

Also, attached is the output of

# cat /proc/interrupts; sleep 10; cat /proc/interrupts

from the current mainline.

Greetings,
Rafael


> Index: linux-2.6.23-rc7/arch/x86_64/kernel/apic.c
> ===================================================================
> --- linux-2.6.23-rc7.orig/arch/x86_64/kernel/apic.c	2007-09-24 20:30:00.000000000 +0200
> +++ linux-2.6.23-rc7/arch/x86_64/kernel/apic.c	2007-09-25 15:05:32.000000000 +0200
> @@ -927,6 +927,7 @@ static void __init calibrate_APIC_clock(
>  
>  void __init setup_boot_APIC_clock (void)
>  {
> +#if 0
>  	/*
>  	 * The local apic timer can be disabled via the kernel commandline.
>  	 * Register the lapic timer as a dummy clock event source on SMP
> @@ -940,7 +941,7 @@ void __init setup_boot_APIC_clock (void)
>  			setup_APIC_timer();
>  		return;
>  	}
> -
> +#endif
>  	printk(KERN_INFO "Using local APIC timer interrupts.\n");
>  	calibrate_APIC_clock();
>  
> @@ -949,11 +950,13 @@ void __init setup_boot_APIC_clock (void)
>  	 * PIT/HPET going.  Otherwise register lapic as a dummy
>  	 * device.
>  	 */
> -	if (nmi_watchdog != NMI_IO_APIC)
> +	if (!disable_apic_timer && nmi_watchdog != NMI_IO_APIC)
>  		lapic_clockevent.features &= ~CLOCK_EVT_FEAT_DUMMY;
> +#if 0
>  	else
>  		printk(KERN_WARNING "APIC timer registered as dummy,"
>  		       " due to nmi_watchdog=1!\n");
> +#endif
>  
>  	setup_APIC_timer();
>  }
> 
> 
> 
> 

-- 
"Premature optimization is the root of all evil." - Donald Knuth

[-- Attachment #2: interrupts.txt --]
[-- Type: text/x-log, Size: 1395 bytes --]

albercik:~ # cat /proc/interrupts; sleep 10; cat /proc/interrupts
           CPU0       CPU1
  0:      62489          0  local-APIC-edge      timer
  1:          3        232   IO-APIC-edge      i8042
  8:          0          0   IO-APIC-edge      rtc
 12:          1        147   IO-APIC-edge      i8042
 14:         15       1947   IO-APIC-edge      ide0
 16:        193      14151   IO-APIC-fasteoi   sata_sil, HDA Intel
 19:         76      43153   IO-APIC-fasteoi   ohci_hcd:usb1, ehci_hcd:usb2, ohci_hcd:usb3
 20:          0          4   IO-APIC-fasteoi   ohci1394, tifm_7xx1, yenta, sdhci:slot0
 21:          7        172   IO-APIC-fasteoi   acpi
NMI:          0          0
LOC:      62454      62082
ERR:          0
           CPU0       CPU1
  0:      64993          0  local-APIC-edge      timer
  1:          3        233   IO-APIC-edge      i8042
  8:          0          0   IO-APIC-edge      rtc
 12:          1        147   IO-APIC-edge      i8042
 14:         15       2037   IO-APIC-edge      ide0
 16:        194      14265   IO-APIC-fasteoi   sata_sil, HDA Intel
 19:         77      45155   IO-APIC-fasteoi   ohci_hcd:usb1, ehci_hcd:usb2, ohci_hcd:usb3
 20:          0          4   IO-APIC-fasteoi   ohci1394, tifm_7xx1, yenta, sdhci:slot0
 21:          7        176   IO-APIC-fasteoi   acpi
NMI:          0          0
LOC:      64958      64586
ERR:          0
albercik:~ #

  reply	other threads:[~2007-09-25 19:53 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-23 10:57 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents Rafael J. Wysocki
2007-09-23 19:10 ` Thomas Gleixner
2007-09-23 20:08   ` Rafael J. Wysocki
2007-09-23 19:59     ` Thomas Gleixner
2007-09-23 20:52       ` Rafael J. Wysocki
2007-09-24  8:07         ` Thomas Gleixner
2007-09-24 12:57           ` Rafael J. Wysocki
2007-09-24 13:05             ` Thomas Gleixner
2007-09-24 13:52               ` Rafael J. Wysocki
2007-09-24 14:23                 ` Thomas Gleixner
2007-09-24 15:18                   ` Rafael J. Wysocki
2007-09-24 16:46                     ` Thomas Gleixner
2007-09-24 19:11                       ` Rafael J. Wysocki
2007-09-24 19:13                         ` Thomas Gleixner
2007-09-25 13:16                           ` Rafael J. Wysocki
2007-09-25 13:17                             ` Thomas Gleixner
2007-09-25 20:07                               ` Rafael J. Wysocki [this message]
2007-09-25 20:46                                 ` Thomas Gleixner
2007-09-25 21:28                                   ` Rafael J. Wysocki
2007-09-25 21:24                                     ` Thomas Gleixner
2007-09-26 15:25                                       ` Rafael J. Wysocki
2007-09-26 18:51                                         ` Thomas Gleixner
2007-09-26 19:49                                           ` Rafael J. Wysocki
2007-09-26 21:00                                             ` [REGRESSION from 2.6.23-rc8] (was: Re: 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents) Rafael J. Wysocki
2007-09-26 21:34                                               ` Thomas Gleixner
2007-09-26 22:22                                                 ` Linus Torvalds
2007-09-26 22:35                                                   ` Thomas Gleixner
2007-09-26 23:30                                                     ` [REGRESSION from 2.6.23-rc8] Chuck Ebbert
2007-09-28 15:07                                                     ` Chuck Ebbert
2007-09-28 15:10                                                       ` Thomas Gleixner
2007-09-30  9:58                                                   ` [REGRESSION from 2.6.23-rc8] (was: Re: 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents) Andi Kleen
2007-09-30 14:06                                                     ` Thomas Gleixner
2007-09-30 15:03                                                       ` Andi Kleen
2007-09-26 23:30                                                 ` Rafael J. Wysocki
2007-09-26 23:21                                                   ` Thomas Gleixner
2007-09-27 15:58                                                     ` Rafael J. Wysocki
2007-09-30  9:52                                                 ` Andi Kleen
     [not found] <20070925101418.68d30a72@localhost>
2007-09-25  8:07 ` 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents Thomas Gleixner
2007-09-25  9:30   ` Thomas Gleixner
2007-09-25 12:20     ` Rafael J. Wysocki
2007-09-25 12:28       ` Thomas Gleixner
2007-09-25 12:52         ` Rafael J. Wysocki
2007-09-25 13:15           ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200709252207.02532.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox