Привет всем! Есть два свежеарендованных серверочка в ЦОД. Один при ребуте завис с нижепроцитированным. После этого в dmesg на обоих обнаружил эту самую запись. Кто-нибудь в курсе, что это и лечится ли? Материнка: Gigabyte H55M-S2H ОС: Linux 2.6.27 ================================= [ 9.980020] ------------[ cut here ]------------ [ 9.980024] WARNING: at arch/x86/kernel/hpet.c:286 hpet_legacy_next_event+0x5c/0x70() [ 9.980027] Modules linked in: evdev(+) rtc_cmos rtc_core rtc_lib thermal processor button ohci_hcd uhci_hcd usbhid hid ff_ memless ehci_hcd usb_storage libusual usbcore ext3 jbd mbcache raid1 ahci libata dock sd_mod crc_t10dif scsi_mod [ 9.980043] Pid: 0, comm: swapper Not tainted 2.6.27-ovz-smp-alt12 #1 [ 9.980047] [<c022ca74>] warn_on_slowpath+0x54/0x70 [ 9.980051] [<c029e6df>] ? check_object+0xdf/0x210 [ 9.980056] [<c029f9a6>] ? __slab_free+0x1d6/0x270 [ 9.980059] [<c0312a45>] ? __next_cpu+0x15/0x30 [ 9.980064] [<c021bf8d>] ? walk_tg_tree+0x4d/0x80 [ 9.980067] [<c021c040>] ? tg_nop+0x0/0x10 [ 9.980070] [<c021c24b>] ? load_balance_next_fair+0xb/0x10 [ 9.980074] [<c0228cd8>] ? load_balance_fair+0x178/0x220 [ 9.980078] [<c0209642>] ? read_tsc+0x12/0x70 [ 9.980082] [<c0217f1c>] hpet_legacy_next_event+0x5c/0x70 [ 9.980086] [<c024abaa>] clockevents_program_event+0xaa/0x110 [ 9.980091] [<c024bdac>] tick_dev_program_event+0x3c/0xc0 [ 9.980094] [<c024b4b7>] tick_broadcast_set_event+0x17/0x20 [ 9.980097] [<c024bb05>] tick_broadcast_oneshot_control+0xf5/0x100 [ 9.980101] [<c024b2c5>] tick_notify+0x255/0x380 [ 9.980104] [<c0440357>] notifier_call_chain+0x37/0x70 [ 9.980109] [<c0245b19>] __raw_notifier_call_chain+0x19/0x20 [ 9.980112] [<c0245b3a>] raw_notifier_call_chain+0x1a/0x20 [ 9.980115] [<c024aaf1>] clockevents_do_notify+0x11/0x20 [ 9.980118] [<c024ae3c>] clockevents_notify+0x1c/0x70 [ 9.980121] [<f8d9ea37>] acpi_state_timer_broadcast+0x31/0x34 [processor] [ 9.980128] [<f8d9f527>] acpi_idle_enter_simple+0x81/0x12e [processor] [ 9.980134] [<f8d9f32d>] acpi_idle_enter_bm+0xbc/0x235 [processor] [ 9.980140] [<c03b15ce>] cpuidle_idle_call+0x6e/0xd0 [ 9.980144] [<c02029e6>] cpu_idle+0x56/0x100 [ 9.980146] [<c042e76e>] rest_init+0x4e/0x60 [ 9.980150] ======================= [ 9.980152] ---[ end trace dcfdae79ea55b6bd ]--- [ 9.984003] Marking TSC unstable due to TSC halts in idle -- Regards, Michael Bochkaryov www.rattler.kiev.ua