linux-kernel - Re: 2.6.24-rc8-mm1: WARN_ON() in clockevents_register

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: <20080120102440.GA507@elte.hu>
Date:	Sun, 20 Jan 2008 11:24:40 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: 2.6.24-rc8-mm1: WARN_ON() in clockevents_register_device() on
	HP nx6325


* Rafael J. Wysocki <rjw@...k.pl> wrote:

> Something goes wrong in the timers land.  I get this on boot:
> 
> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> Disabling APIC timer
> ------------[ cut here ]------------
> WARNING: at /home/rafael/src/mm/linux-2.6.24-rc8-mm1/kernel/time/clockevents.c:1
> 65 clockevents_register_device+0x36/0xc4()

ok, since we disable the APIC timer, i suspect this warning can be 
disregarded - the bootup is otherwise fine, right?

Thomas - why do we register it while it's disabled? I have put in that 
warning to detect APIC miscalibrations.

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