Messages in this thread | | | Date | Fri, 24 Jul 2009 16:07:58 +0200 | From | Victor Mataré <> | Subject | clock freezes?? |
| |
Hello,
I have a dual Xeon server (old Xeon HT) with an Intel E7505 chipset, with hrtimer and dynticks enabled. On bootup, the kernel (2.6.29-gentoo-r5) tells me it's using the PM-Timer bug workaround, but then it uses tsc as clocksource. Now the clock was running slow for about 15sec/12hrs, which is quite a lot. So in a careless moment, I just tried "echo jiffies > clocksource0/current_clocksource". This froze the system time. Now I couldn't switch back to tsc or acpi_pm, echoing those was just ignored. Subsequently, the entire system locked up and I needed to reboot.
Now what does that mean? Is this supposed to happen? Should I disable dynticks and/or hrtimer?
thanks...
-- Victor Mataré Server- & Netzwerk-Administration
Lehrstuhl für Ingenieurgeologie und Hydrogeologie der RWTH-Aachen Lochnerstraße 4-20, 52064 Aachen
Tel: 0241 80 96778 Fax: 0241 80 92280
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |