From: Jim Cromie <jim.cromie@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
john stultz <johnstul@us.ibm.com>, Ted Phelps <phelps@gnusto.com>
Subject: Re: [rfc patch 1/1 -17rc1-mm3] time: add clocksource driver for Geode SC-1100 Hi-Res Timer
Date: Mon, 24 Apr 2006 18:22:28 -0400 [thread overview]
Message-ID: <444D4FA4.6020604@gmail.com> (raw)
In-Reply-To: <444CD732.5090703@gmail.com>
Jim Cromie wrote:
> Heres a patch (on 17rc1-mm3 + John Stultz's 4/21 fn-renames) that adds
> a new GTOD-clocksource driver for the hires timer in the Geode
> SC-1100. Ive been running it for most of the last 7 days now, and it
> seems to work well.
Ooof. Something is broken, causing kernel to 'lock'
No oops, just nothing.
$ while true; do sleep 30; uptime; done
..
14:25:23 up 1:09, 2 users, load average: 0.12, 0.08, 0.01
14:25:53 up 1:09, 2 users, load average: 0.07, 0.07, 0.01
14:26:23 up 1:10, 2 users, load average: 0.04, 0.06, 0.01
14:26:53 up 1:10, 2 users, load average: 0.02, 0.05, 0.00
14:27:24 up 1:11, 2 users, load average: 0.07, 0.06, 0.00
then freeze.
Heres the last bit of the syslog:
Apr 24 13:18:24 truck ntpd[1730]: configure: keyword "By" unknown, line
ignored
Apr 24 13:18:27 truck /usr/sbin/cron[1751]: (CRON) INFO (pidfile fd = 3)
Apr 24 13:18:27 truck /usr/sbin/cron[1752]: (CRON) STARTUP (fork ok)
Apr 24 13:18:28 truck /usr/sbin/cron[1752]: (CRON) INFO (Running @reboot
jobs)
Apr 24 13:19:17 truck snmpd[1680]: cannot open /proc/net/snmp6 ...
Apr 24 13:21:41 truck ntpd[1730]: synchronized to LOCAL(0), stratum 13
Apr 24 13:21:41 truck ntpd[1730]: kernel time sync disabled 0041
Apr 24 13:22:44 truck ntpd[1730]: synchronized to 64.5.1.130, stratum 2
Apr 24 13:25:59 truck ntpd[1730]: kernel time sync enabled 0001
Apr 24 13:38:02 truck -- MARK --
Apr 24 13:58:02 truck -- MARK --
Apr 24 14:17:01 truck /USR/SBIN/CRON[2015]: (root) CMD ( run-parts
--report /etc/cron.hourly)[jimc@harpo i2c-stuff]$
Im looking into it, startng with recent presentation tweaks :-/
Ill turn on whatever debug might be relevant, mutex debug included.
This is on an NFSroot setup, not that I suspect it.
Im still interested in feedback,
thanks
Jim Cromie
next prev parent reply other threads:[~2006-04-24 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 13:48 [rfc patch 1/1 -17rc1-mm3] time: add clocksource driver for Geode SC-1100 Hi-Res Timer Jim Cromie
2006-04-24 22:22 ` Jim Cromie [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-24 13:40 Jim Cromie
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=444D4FA4.6020604@gmail.com \
--to=jim.cromie@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phelps@gnusto.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.