mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
To: Yinghai Lu <yinghai@kernel.org>, Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org
Subject: Re: Latest tip kernel(3.2-rc1-tip_cf6b3899) fails to boot on x3850x5 machine
Date: Thu, 15 Dec 2011 07:54:18 +0530	[thread overview]
Message-ID: <87y5ueo9m5.fsf@abhimanyu.in.ibm.com> (raw)
In-Reply-To: <CAE9FiQXz6n=2gR1CY29pEbfbwx-e27WrUoDQeH9qxmL_kwP+mA@mail.gmail.com>

On Wed, 14 Dec 2011 12:35:35 -0800, Yinghai Lu <yinghai@kernel.org> wrote:
> On Wed, Dec 14, 2011 at 12:17 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > On Wed, 14 Dec 2011, Thomas Gleixner wrote:
> >
> >> On Wed, 14 Dec 2011, Nikunj A Dadhania wrote:
> >>
> >> > Hi,
> >> >
> >> > I was trying the latest tip kernel and I am seeing the following
> >> > message. After some more logs the machine does not proceed.
> >> >
> >> > ------------[ cut here ]------------
> >> > WARNING: at kernel/time/clockevents.c:47 clockevent_delta2ns+0x79/0x90()
> >>
> >> Ok, that's caused by stupidity in the apic timer code. Fix
> >> below. Note, that patch wont fix the boot problem. It just prevents
> >> the warning.
> >>
> >> > Hardware name: System x3850 X5 -[71455RQ]-
> >> > Modules linked in:
> >> > Pid: 1, comm: swapper/0 Not tainted 3.2.0-rc4-tip #3
> >> > Call Trace:
> >> >  [<ffffffff8104d3af>] warn_slowpath_common+0x7f/0xc0
> >> >  [<ffffffff8104d40a>] warn_slowpath_null+0x1a/0x20
> >> >  [<ffffffff81097ab9>] clockevent_delta2ns+0x79/0x90
> >> >  [<ffffffff81e49109>] calibrate_APIC_clock+0x16e/0x377
> >> >  [<ffffffff81e4942c>] setup_boot_APIC_clock+0x59/0x7e
> >> >  [<ffffffff81e472d1>] native_smp_prepare_cpus+0x1f1/0x205
> >> >  [<ffffffff81e38767>] kernel_init+0x1b6/0x29a
> >> >  [<ffffffff815f9ca4>] kernel_thread_helper+0x4/0x10
> >> >  [<ffffffff81e385b1>] ? parse_early_options+0x20/0x20
> >> >  [<ffffffff815f9ca0>] ? gs_change+0x13/0x13
> >> > ---[ end trace a7919e7f17c0a725 ]---
> >> > APIC frequency too slow, disabling apic timer
> >>
> >> Ouch. This is really bad.
> >>
> >> > Performance Events: PEBS fmt1+, Nehalem events, Intel PMU driver.
> >> > CPU erratum AAJ80 worked around
> >> > CPUID marked event: 'bus cycles' unavailable
> >> > ... version:                3
> >> > ... bit width:              48
> >> > ... generic registers:      4
> >> > ... value mask:             0000ffffffffffff
> >> > ... max period:             000000007fffffff
> >> > ... fixed-purpose events:   3
> >> > ... event mask:             000000070000000f
> >> > NMI watchdog enabled, takes one hw-pmu counter.
> >> > Booting Node   0, Processors  #1
> >> > APIC never delivered???
> >> > APIC delivery error (ef).
> >> >  #2
> >
> > What's worse is that this problem exists on 3.2-rc5 as
> > well. Investigating.
> 
> 
> BIOS pre-enabled x2apic, and kernel config does not have x2apic enabled?
make oldconfig somehow skipped this!! I can see my previous kernel config
having this enabled.

Regards
Nikunj



  parent reply	other threads:[~2011-12-15  2:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 10:48 Nikunj A Dadhania
2011-12-14 13:30 ` Thomas Gleixner
2011-12-14 20:17   ` Thomas Gleixner
2011-12-14 20:35     ` Yinghai Lu
2011-12-14 20:56       ` Thomas Gleixner
2011-12-15  2:24       ` Nikunj A Dadhania [this message]
2011-12-15  2:40         ` Yinghai Lu
2011-12-15  7:19           ` Ingo Molnar
2011-12-15 19:16             ` Yinghai Lu
2011-12-15 20:25               ` Suresh Siddha
2011-12-16  3:41                 ` Nikunj A Dadhania
2011-12-16  8:36                 ` Ingo Molnar
2011-12-17  2:10                   ` Suresh Siddha
2011-12-18  8:32                     ` Ingo Molnar
2011-12-16  8:40               ` Ingo Molnar
2011-12-16 18:03                 ` Yinghai Lu
2011-12-17  2:18                   ` Suresh Siddha

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=87y5ueo9m5.fsf@abhimanyu.in.ibm.com \
    --to=nikunj@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.org \
    /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

all inboxes | Powered by JetHome®