linux-kernel - Re: 2.6.26-rc2-mm1 - machine stuck while booting up with CONFIG_FTRACE_STARTUP

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]

Message-ID: <48317A72.701@redhat.com>
Date:	Mon, 19 May 2008 09:02:42 -0400
From:	Steven Rostedt <srostedt@...hat.com>
To:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andy Whitcroft <apw@...dowen.org>,
	Balbir Singh <balbir@...ux.vnet.ibm.com>
Subject: Re: 2.6.26-rc2-mm1 - machine stuck while booting up with CONFIG_FTRACE_STARTUP_TEST
 enabled

Kamalesh Babulal wrote:
> Hi Andrew,
> 
> The 2.6.26-rc2-mm1 kernel gets stuck, while booting up on x86_64 machine,
> with the CONFIG_FTRACE_STARTUP_TEST enabled. The following .config
> options related to FTRACE are enabled. 
> 
> CONFIG_FTRACE_SELFTEST=y
> CONFIG_FTRACE_STARTUP_TEST=y
> CONFIG_FTRACE=y
> CONFIG_HAVE_FTRACE=y
> CONFIG_DYNAMIC_FTRACE=y
> 

[...]

> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 1805035
> Policy zone: Normal
> Kernel command line: root=/dev/sda1 ro console=tty0 console=ttyS0,38400n1 noapci IDENT=1211176695

Hi, could you do nmi_watchdog=1 and see if that gives you a stack dump?

Thanks.

-- Steve

[...]

> checking if image is initramfs... it is
> Freeing initrd memory: 1466k freed
> audit: initializing netlink socket (disabled)
> type=2000 audit(1211176950.517:1): initialized
> Testing tracer sched_switch: PASSED
> Testing tracer sysprof: PASSED
> Testing tracer ftrace: 
> 

--
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/