public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Kirby <sim@netnation.com>
To: linux-kernel@vger.kernel.org
Subject: [2.4.16] Clock locking bugs?
Date: Mon, 14 Jan 2002 10:02:15 -0800	[thread overview]
Message-ID: <20020114180215.GA20200@netnation.com> (raw)

Just had a server's clock stop at 9:02:30am.  Very interesting
results:

[sroot@pro:/]# cat /proc/interrupts
           CPU0       CPU1       
  0:  172839353  172896882    IO-APIC-edge  timer
  1:        578        522    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
  4:      22002      21840    IO-APIC-edge  serial
 10:  581309135  580556518   IO-APIC-level  eth0
 12:   63077142   63023533   IO-APIC-level  aic7xxx
NMI:          0          0 
LOC:  345979794  345980089 
ERR:          0
MIS:          0

...

[sroot@pro:/]# cat /proc/interrupts
           CPU0       CPU1       
  0:  172839353  172896882    IO-APIC-edge  timer
  1:        578        522    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
  4:      22002      21840    IO-APIC-edge  serial
 10:  581309219  580556518   IO-APIC-level  eth0
 12:   63077142   63023533   IO-APIC-level  aic7xxx
NMI:          0          0 
LOC:  345979883  345980178 
ERR:          0
MIS:          0

Alan says this is due to locking problems with the timer I/O code. 

On the console were a lot of "set_rtc_mmss: can't update from 79 to 32"
type messages that have always happened on SMP kernels with ntpd.

Has anybody created any patches for this?

Simon-

[  Stormix Technologies Inc.  ][  NetNation Communications Inc. ]
[       sim@stormix.com       ][       sim@netnation.com        ]
[ Opinions expressed are not necessarily those of my employers. ]

             reply	other threads:[~2002-01-14 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 18:02 Simon Kirby [this message]
2002-04-13 19:21 ` [2.4.16] Clock locking bugs? Simon Kirby
2002-04-16  5:51   ` Paul Gortmaker

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=20020114180215.GA20200@netnation.com \
    --to=sim@netnation.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox