From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: [x86-64, CMOS/RTC] Re: 2.6.19.2: bad reads/writes from/to CMOS clock
Date: Fri, 26 Jan 2007 21:01:01 +0000 (UTC) [thread overview]
Message-ID: <slrnerkrgn.ae0.olecom@flower.upol.cz> (raw)
In-Reply-To: 9e18e56a85195bf4a507163df8e2f62e@teksavvy.com
26-01-2007:
> I am running 2.6.19.2 kernel from kernel.org.
2.6.18 debian, didn't see before, but maybe it was just big uptime ;)
> This is my first SMP kernel.
>
> The problem I describe below has not happend with non-SMP kernels ever...
>
> I have installed my new AMD64 x2 4800 CPU just a few days ago. My mobo is Asus A8N SLI
> (Nvidia chipset).
UP ASUS A4K x86-64 CPU Mobile Athlon 64 3200+
> My problem with this new setup is that my CMOS clock is thrown off by varying
> amounts of time. I have seen system times as long as ten months into future, and as
> long as 25 days in the past. At the moment my system clock has correct
> hh:mm:ss, but it shows the date Jan 1st, instead of correct 25th.
I saw bad CMOS read, but CMOS itself was OK, after checking it with
hwclock or reboot by magic IRQ.
[]
> I would appreciate any ideas on how to follow-up on this problem.
>
> I am eager to try things, collect data as needed. Just tell me what to do.
>
> Thanks in advance.
> Yavuz Onder
I don't know, because it was month or so ago. And i'm usual for bugs
(or curved hands ;).
____
next prev parent reply other threads:[~2007-01-26 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 14:46 2.6.19.2: bad reads/writes from/to CMOS clock yavuz
2007-01-26 21:01 ` Oleg Verych [this message]
2007-01-30 1:37 ` Yavuz Onder
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=slrnerkrgn.ae0.olecom@flower.upol.cz \
--to=olecom@flower.upol.cz \
--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 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.