Messages in this thread |  | | | Date | Thu, 14 Feb 2008 12:11:19 +0530 | | From | Dhaval Giani <> | | Subject | Re: 2.6.25-rc1 panics on boot |
On Thu, Feb 14, 2008 at 12:06:31PM +0530, Dhaval Giani wrote:
> 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.>
Panics at same point.
--
regards,
Dhaval
|  |