Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760090AbYAJXdS (ORCPT ); Thu, 10 Jan 2008 18:33:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755823AbYAJXdI (ORCPT ); Thu, 10 Jan 2008 18:33:08 -0500 Received: from terminus.zytor.com ([198.137.202.10]:56393 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752270AbYAJXdH (ORCPT ); Thu, 10 Jan 2008 18:33:07 -0500 Message-ID: <4786AB1B.4030004@zytor.com> Date: Thu, 10 Jan 2008 15:32:43 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Kevin Winchester CC: Ingo Molnar , Thomas Gleixner , Linux Kernel Mailing List Subject: Re: hwclock failure in x86.git References: <4786AA11.5010805@gmail.com> In-Reply-To: <4786AA11.5010805@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 907 Lines: 22 Kevin Winchester wrote: > My first time building and booting the mm branch of x86.git was pretty > successful. The only error I noticed was the following in my dmesg: > > hwclock[622] general protection ip:804b226 sp:bff43e30 error:0 > > I'm not sure exactly how to debug this. I could bisect, but there seems > to be some useful debug information in there, so there might be > something better to try first. > That's a userspace IP; it implies the userspace hwclock binary did something bad, or the kernel didn't permit it to do something it should have. The best thing to do would probably to strace hwclock and see what it did when it died. -hpa -- 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/