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:	Mon, 30 Apr 2007 23:33:13 -0400
From:	Mark Lord <lkml@....ca>
To:	Daniel Walker <dwalker@...sta.com>
Cc:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	tglx@...utronix.de, Linus Torvalds <torvalds@...l.org>
Subject: Re: [BUG] 2.6.21: Kernel won't boot with either/both of	CONFIG_NO_HZ,
 CONFIG_HIGH_RES_TIMERS

Daniel Walker wrote:
> 
> I'm interested in which clocksource is getting used, which is in the
> boot log.

Well then, send me a patch that dumps that information out just before it locks up.
We know (first post in this thread) that the lockup occurs just after
these two messages:

  "switched to high resolution mode on cpu 1"
  "switched to high resolution mode on cpu 0"

So just dump out anything else you need to see at the same time,
and it'll still be on my screen when the darned thing locks up.

Simple, eh.  We both get to run around a treadmill this way.  ;)
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ