LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: hwclock failure in x86.git
Date: Thu, 10 Jan 2008 17:13:51 -0800 [thread overview]
Message-ID: <4786C2CF.4070204@zytor.com> (raw)
In-Reply-To: <4786AF4C.6050509@gmail.com>
Kevin Winchester wrote:
> H. Peter Anvin wrote:
>> 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.
>>
>
> Unfortunately, but the time I can get a chance to run hwclock, the
> problem seems to have fixed itself. I tried booting into single user
> mode, but `/etc/init.d/hwclock.sh restart` succeeds once I have my prompt.
>
The other thing you can do is to download the debug information and
source code for hwclock from your particular distro, and find out
exactly what operation inside the hwclock binary is triggering the segfault.
The only other option is to bisect.
-hpa
next prev parent reply other threads:[~2008-01-11 1:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 23:28 Kevin Winchester
2008-01-10 23:32 ` H. Peter Anvin
2008-01-10 23:50 ` Kevin Winchester
2008-01-11 1:13 ` H. Peter Anvin [this message]
2008-01-11 2:04 ` Kevin Winchester
2008-01-11 14:03 ` Ingo Molnar
2008-01-11 23:58 ` Miguel Botón
2008-01-12 1:04 ` [PATCH] x86: fix ioport unification on 32-bit [was: Re: hwclock failure in x86.git] Chris Wright
2008-01-12 1:06 ` [PATCH] x86: refactor ioport unification Chris Wright
2008-01-14 8:32 ` Ingo Molnar
2008-01-14 8:27 ` [PATCH] x86: fix ioport unification on 32-bit [was: Re: hwclock failure in x86.git] Ingo Molnar
2008-01-11 2:27 ` hwclock failure in x86.git Kevin Winchester
2008-01-11 2:55 ` Zach Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4786C2CF.4070204@zytor.com \
--to=hpa@zytor.com \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--subject='Re: hwclock failure in x86.git' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).