linux-kernel - clockevents_program_event WARN

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-next>] [day] [month] [year] [list]

Message-ID: <20130430212007.GB18598@redhat.com>
Date:	Tue, 30 Apr 2013 17:20:07 -0400
From:	Dave Jones <davej@...hat.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: clockevents_program_event WARN_ON preventing boot.

I have a machine that crashes instantly on boot up on Linus'
post-3.9 tree. (8c55f1463c1fd318d5e785f02b80bcc32176d342)

By booting with boot_delay=100, I was able to take a photo
and capture the top of the trace.  (For some reason, larger boot
delay parameters seem to make it take forever before printing
even a single character, which made this a pain to debug).

The WARN_ON it prints right before locking up is this in clockevents_program_event

208         if (unlikely(expires.tv64 < 0)) {
209                 WARN_ON_ONCE(1);
210                 return -ETIME;
211         }

booting with maxcpus=1 avoids the problem.

I'm still trying to get a complete stack trace, though it's painful
due to the above reason.

	Dave

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