linux-kernel - Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no stop-machine, update stack tracer

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1325696759.12696.24.camel@gandalf.stny.rr.com>
Date:	Wed, 04 Jan 2012 12:05:59 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no
 stop-machine, update stack tracer

On Wed, 2012-01-04 at 15:11 +0100, Ingo Molnar wrote:
> * Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > My mistake, I forgot to add the "minimum config" for booting 
> > the box. When I did that, it booted fine. I kicked off the 
> > bisect again, and lets see what happens.
> 
> Okay.
> 
> I too did a lot of testing, breaking my promise to do other 
> stuff ;-)
> 
> *Both* of your trees [the NMI and the cleanup/fixes tree], when 
> merged produced hangs or spontaneous reboots, within 5 
> iterations typically.

I actually haven't looked at the NMI branch yet. I'm still trying to
figure out why the ftrace one would lockup. I'll try another box to see
if that one also locks up on tip/master with your config.

> 
> The failure modes were different: the NMI tree tended to do the 
> spontaneous reboot thing, the fixes tree produced the soft 
> hangs.

Did you just merge in the branches, or do you see the same problem if
you test the head of the branch itself?

In other words, did the branch have the issue, or is the branch causing
an issue with something already in tip?

> 
> I'm now re-testing pristine -tip again - which did the 50 and 70 
> series of successful bootups ...

BTW, I did a make oldconfig with the config you gave me, and the result
is a bit different:

diffconfig your-config .config

-BOOTPARAM_SUPPORT_NOT_WANTED y
-BROKEN_BOOT_ALLOWED2 y
-BROKEN_BOOT_ALLOWED3 y
-BROKEN_BOOT_ALLOWED4 y
-BROKEN_BOOT_DISALLOWED y
-BROKEN_BOOT_EUROPE n
-BROKEN_BOOT_TITAN n
-FORCE_MINIMAL_CONFIG y
-FORCE_MINIMAL_CONFIG_64 y
-FORCE_MINIMAL_CONFIG_PHYS y
-FORCE_SUCCESSFUL_BUILD y
-SMP_SUPPORT y
-UP_WANTED y
-UP_WANTED_1 y
-UP_WANTED_2 y
-USB_MOUSE y
+CMDLINE_OVERRIDE n
+DEBUG_BLOCK_EXT_DEVT n
+DEBUG_INFO n
+DEBUG_KOBJECT n
+EUROTECH_WDT n
+FB_ASILIANT n
+FB_CIRRUS n
+FB_RADEON n
+FB_VESA n
+FB_VGA16 n
+FB_VIRTUAL n
+FRAMEBUFFER_CONSOLE n
+FTRACE_STARTUP_TEST n
+IDE n
+KGDB_TESTS_ON_BOOT n
+KPROBES_SANITY_TEST n
+MTD n
+PARIDE n
+PM_TEST_SUSPEND n
+PROFILE_ALL_BRANCHES n
+PROFILE_ANNOTATED_BRANCHES n
+RING_BUFFER_BENCHMARK n
+SECURITY_SELINUX_POLICYDB_VERSION_MAX n
+SECURITY_SMACK n
+SECURITY_TOMOYO_OMIT_USERSPACE_LOADER n
+SENSORS_LM90 n
+SENSORS_LM92 n
+SENSORS_LM93 n
+SENSORS_W83627HF n
+SENSORS_W83793 n
+STAGING n
+W83697HF_WDT n
+W83697UG_WDT n

Was the config based off of tip/master? I'm a missing a branch?

Thanks,

-- Steve


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