Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754832Ab0KIVaQ (ORCPT ); Tue, 9 Nov 2010 16:30:16 -0500 Received: from mail-ey0-f174.google.com ([209.85.215.174]:40337 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753431Ab0KIVaN convert rfc822-to-8bit (ORCPT ); Tue, 9 Nov 2010 16:30:13 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=igBPD3G0oJAVcSNyWAyW3YsSQEn/ilAS9G3gufUNfVRYxgos55VXN5gKsBHRCVEM+l iG8mwN2mxq/i7srCFeFDCBimURxBMgmnNVUYpc+5KUMopUkq2wEzeBfXp2BcCmDbmhA+ D4y5tun+saLJjDwwqbpO4qm5k/1VANtnYp79E= MIME-Version: 1.0 In-Reply-To: <20101109180123.GB31121@aftab> References: <4CD966D8.4000602@ladisch.de> <20101109153805.GB3146@kryptos.osrc.amd.com> <20101109180123.GB31121@aftab> From: Andrew Lutomirski Date: Tue, 9 Nov 2010 16:29:51 -0500 X-Google-Sender-Auth: QHehtvbnY5Pr1F9ggZKJJexbVFo Message-ID: Subject: Re: HPET (?) related hangs and breakage in 2.6.35,36 To: Borislav Petkov Cc: Clemens Ladisch , "linux-kernel@vger.kernel.org" , Thomas Gleixner , Peter Zijlstra , Ingo Molnar , "H. Peter Anvin" , x86 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1517 Lines: 37 On Tue, Nov 9, 2010 at 1:01 PM, Borislav Petkov wrote: > On Tue, Nov 09, 2010 at 12:44:48PM -0500, Andrew Lutomirski wrote: >> I may have just reproduced after a couple of days of uptime it in >> 2.6.36 with hpet=disable (in any case, the system hung and netconsole >> didn't work). >> >> I'm currently testing the hpet_min_tick stuff, backported to 2.6.36, >> with hpet on. ?Haven't had a problem yet, but I'll see what happens >> after a few hours. ?So far, it said: >> >> ACPI: HPET id: 0x8086a301 base: 0xfed00000 min tick: 128 > > This doesn't say what your BIOS has set it to originally. For that, do > > hexdump -C /sys/firmware/acpi/tables/HPET > > and check what does the u16 little endian value at offset 0x35 say. 0x37ee, which people have seen before. In any case, even with the patch applied my system hung, and I still got this off netconsole sometime around when the hang happened: Clocksource: tsc unstable (delta = -34355296774 ns) Switching: to clocksource hpet Another odd symptom: none of the SysRq hotkeys I could think of did anything *except for SysRq-b*. I have no idea what could cause that. My system appears to pass ingo's time-warp-test (when compiled with -O0 -- it segfaults with -O2), so I think my TSC is okay. --Andy -- 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/