LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Chris Snook <csnook@redhat.com>,
lenb@kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25-rc1 panics on boot
Date: Thu, 14 Feb 2008 12:06:31 +0530 [thread overview]
Message-ID: <20080214063631.GD17151@linux.vnet.ibm.com> (raw)
In-Reply-To: <86802c440802132232g79fe5eaew3f86e412eeff41a9@mail.gmail.com>
On Wed, Feb 13, 2008 at 10:32:02PM -0800, Yinghai Lu wrote:
> On Wed, Feb 13, 2008 at 10:20 PM, Dhaval Giani
> <dhaval@linux.vnet.ibm.com> wrote:
> > On Wed, Feb 13, 2008 at 01:08:42PM -0500, Chris Snook wrote:
> > > Dhaval Giani wrote:
> > >> I am getting the following oops on bootup on 2.6.25-rc1
> > > ...
> > >> I am booting using kexec with maxcpus=1. It does not have any problems
> > >> with maxcpus=2 or higher.
> > >
> > > Sounds like another (the same?) kexec cpu numbering bug. Can you post/link
> > > the entire dmesg from both a cold boot and a kexec boot so we can compare?
> > >
> >
> > Don't think its a kexec bug. Get the same on cold boot. dmesg from kexec boot.
>
> how about without "crashkernel=64M@16M nmi_watchdog=2"
>
> also does intel cpu support nmi_watchdog=2?
>
Yes it does. I've used it to get some useful debug information. I will try
that out.
> YH
--
regards,
Dhaval
next prev parent reply other threads:[~2008-02-14 6:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 17:03 Dhaval Giani
2008-02-13 18:08 ` Chris Snook
2008-02-14 6:20 ` Dhaval Giani
2008-02-14 6:32 ` Yinghai Lu
2008-02-14 6:36 ` Dhaval Giani [this message]
2008-02-14 6:41 ` Dhaval Giani
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=20080214063631.GD17151@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=csnook@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yhlu.kernel@gmail.com \
--subject='Re: 2.6.25-rc1 panics on boot' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).