linux-kernel - Re: 2.6.25-rc1 panics on boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Feb 2008 22:32:02 -0800
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Dhaval Giani" <dhaval@...ux.vnet.ibm.com>
Cc:	"Chris Snook" <csnook@...hat.com>, lenb@...nel.org,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.25-rc1 panics on boot

On Wed, Feb 13, 2008 at 10:20 PM, Dhaval Giani
<dhaval@...ux.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?

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