Re: Problem: wall-clock jumping like Mexican bean

2002-06-10 Thread Jonathan Matthews
On Mon, Jun 10, 2002 at 11:45:22PM +, Jonathan Matthews wrote:
> On Mon, Jun 10, 2002 at 11:43:17PM +, Jonathan Matthews wrote:
> > On Mon, Jun 10, 2002 at 03:46:45PM -0500, Rich Puhek wrote:
> > > 
> > > 
> > > Jonathan Matthews wrote:
> > > > 
> > > > I think it's possibly a dodgy RTC on the motherboard.  I saw
> > > > this exact complaint come up on linux-kernel a while ago, and
> > > > someone mentioned that it was specific to a certain brand
> > > > of mobo.
> > > > 
> > > > No URLs for you, I'm afraid, but if you google a bit, I'm sure
> > > > it'll appear.
> > > > 
> > > 
> > > But I thought that the RTC was ignored after boot? If so, a bad RTC
> > > would explain a clock that comes up bad on boot every now and then, but
> > > not why a running system would suddenly shift time.
> > 
> > I might be using the wrong terminology - I'm just remembering
> > the symptoms from the l-k thread.
> > 
> > Here's what I found from l-k.  Not the thread I was 
> > originally thinking of, but might fit as well.
> > 
> 
> Oops.  Here's the link:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=102348147820343&w=2

And another one.
The 1 hour 11 minutes (I think ..?) described in the OP is
obviously a known issue.  Hope this helps.

http://marc.theaimsgroup.com/?l=linux-kernel&m=102212413728493&w=2

jc

-- 
It may stop, it may not.  And stop calling me "dj".


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Problem: wall-clock jumping like Mexican bean

2002-06-10 Thread Jonathan Matthews
On Mon, Jun 10, 2002 at 11:43:17PM +, Jonathan Matthews wrote:
> On Mon, Jun 10, 2002 at 03:46:45PM -0500, Rich Puhek wrote:
> > 
> > 
> > Jonathan Matthews wrote:
> > > 
> > > I think it's possibly a dodgy RTC on the motherboard.  I saw
> > > this exact complaint come up on linux-kernel a while ago, and
> > > someone mentioned that it was specific to a certain brand
> > > of mobo.
> > > 
> > > No URLs for you, I'm afraid, but if you google a bit, I'm sure
> > > it'll appear.
> > > 
> > 
> > But I thought that the RTC was ignored after boot? If so, a bad RTC
> > would explain a clock that comes up bad on boot every now and then, but
> > not why a running system would suddenly shift time.
> 
> I might be using the wrong terminology - I'm just remembering
> the symptoms from the l-k thread.
> 
> Here's what I found from l-k.  Not the thread I was 
> originally thinking of, but might fit as well.
> 

Oops.  Here's the link:
http://marc.theaimsgroup.com/?l=linux-kernel&m=102348147820343&w=2

jc

-- 
It may stop, it may not.  And stop calling me "dj".


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Problem: wall-clock jumping like Mexican bean

2002-06-10 Thread Jonathan Matthews
On Mon, Jun 10, 2002 at 03:46:45PM -0500, Rich Puhek wrote:
> 
> 
> Jonathan Matthews wrote:
> > 
> > I think it's possibly a dodgy RTC on the motherboard.  I saw
> > this exact complaint come up on linux-kernel a while ago, and
> > someone mentioned that it was specific to a certain brand
> > of mobo.
> > 
> > No URLs for you, I'm afraid, but if you google a bit, I'm sure
> > it'll appear.
> > 
> 
> But I thought that the RTC was ignored after boot? If so, a bad RTC
> would explain a clock that comes up bad on boot every now and then, but
> not why a running system would suddenly shift time.

I might be using the wrong terminology - I'm just remembering
the symptoms from the l-k thread.

Here's what I found from l-k.  Not the thread I was 
originally thinking of, but might fit as well.

Y

jc

-- 
It may stop, it may not.  And stop calling me "dj".


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Problem: wall-clock jumping like Mexican bean

2002-06-10 Thread Rich Puhek


Jonathan Matthews wrote:
> 
> I think it's possibly a dodgy RTC on the motherboard.  I saw
> this exact complaint come up on linux-kernel a while ago, and
> someone mentioned that it was specific to a certain brand
> of mobo.
> 
> No URLs for you, I'm afraid, but if you google a bit, I'm sure
> it'll appear.
> 

But I thought that the RTC was ignored after boot? If so, a bad RTC
would explain a clock that comes up bad on boot every now and then, but
not why a running system would suddenly shift time.

--Rich

_
 
Rich Puhek   
ETN Systems Inc. 
_


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Problem: wall-clock jumping like Mexican bean

2002-06-10 Thread Jonathan Matthews
On Mon, Jun 10, 2002 at 10:24:28AM -0700, Kevin Buhr wrote:
> Damien <[EMAIL PROTECTED]> writes:
> > 
> > The problem must have occurred often enuff to other people, IMHO, but I
> > can't find the solution online. My 'wall-clock' (as xscreensaver calls it
> > in the error messages) keeps jumping ahead -- then back, semi-randomly. It
> > seems to do so by always the same amount(?): @ 1 hr 11 minutes.
> 
> I assume you aren't running an NTP daemon and that there are no
> messages in the logs about the time being stepped forward or back.
> 
> Does "@" mean "approximately"?  Is it closer to one hour, eight
> minutes, and 16 seconds?  That would be 4096 seconds, and a most
> suspicious number of seconds to be jumping.
> 
> Does it jump back and forth between two values, or does it jump
> several times in the same direction (so it quickly becomes many hours
> off)?
> 
> If it's jumping continually back and forth by 4096 seconds, I'd guess
> you have a bad SIMM.  One bit (which just happens to be where your
> kernel is storing the time-of-day clock) isn't being reliably set, and
> you see jumps forward and backward every 20 or 30 times (seconds) the
> kernel bumps the seconds counter.
> 
> If this is the case, you might try swapping SIMMs around.  However,
> I'd suggest labelling their original positions very carefully.  If the
> problem does "disappear", you want to be able to get back to where you
> can reliably reproduce it and eliminate the offending SIMM.

I think it's possibly a dodgy RTC on the motherboard.  I saw
this exact complaint come up on linux-kernel a while ago, and
someone mentioned that it was specific to a certain brand
of mobo.

No URLs for you, I'm afraid, but if you google a bit, I'm sure
it'll appear.

As I recall, there was no solution or workaround - the
board simply reports the wrong time every so often.  It's
a bug.

jc

-- 
It may stop, it may not.  And stop calling me "dj".


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Problem: wall-clock jumping like Mexican bean

2002-06-10 Thread Kevin Buhr
Damien <[EMAIL PROTECTED]> writes:
> 
> The problem must have occurred often enuff to other people, IMHO, but I
> can't find the solution online. My 'wall-clock' (as xscreensaver calls it
> in the error messages) keeps jumping ahead -- then back, semi-randomly. It
> seems to do so by always the same amount(?): @ 1 hr 11 minutes.

I assume you aren't running an NTP daemon and that there are no
messages in the logs about the time being stepped forward or back.

Does "@" mean "approximately"?  Is it closer to one hour, eight
minutes, and 16 seconds?  That would be 4096 seconds, and a most
suspicious number of seconds to be jumping.

Does it jump back and forth between two values, or does it jump
several times in the same direction (so it quickly becomes many hours
off)?

If it's jumping continually back and forth by 4096 seconds, I'd guess
you have a bad SIMM.  One bit (which just happens to be where your
kernel is storing the time-of-day clock) isn't being reliably set, and
you see jumps forward and backward every 20 or 30 times (seconds) the
kernel bumps the seconds counter.

If this is the case, you might try swapping SIMMs around.  However,
I'd suggest labelling their original positions very carefully.  If the
problem does "disappear", you want to be able to get back to where you
can reliably reproduce it and eliminate the offending SIMM.

-- 
Kevin Buhr <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]