https://bugzilla.novell.com/show_bug.cgi?id=439461 User meik.piepmeyer@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c29 --- Comment #29 from Meik Piepmeyer <meik.piepmeyer@web.de> 2008-11-05 12:34:09 MST --- Here is the output: ffa4da2a25bb4ac08f710ac99827baf48a8f8d57 is first bad commit commit ffa4da2a25bb4ac08f710ac99827baf48a8f8d57 Author: Thomas Gleixner <tglx@linutronix.de> Date: Wed Sep 3 21:37:08 2008 +0000 clockevents: prevent multiple init/shutdown commit 9c17bcda991000351cb2373f78be7e4b1c44caa3 upstream While chasing the C1E/HPET bugreports I went through the clock events code inch by inch and found that the broadcast device can be initialized and shutdown multiple times. Multiple shutdowns are not critical, but useless waste of time. Multiple initializations are simply broken. Another CPU might have the device in use already after the first initialization and the second init could just render it unusable again. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> :040000 040000 6bb2c37ac2a45ce8f97a37094949575a63750e5c eda80c4051ed1fb945a997732253385a7c9982bf M kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.