On Monday 16 July 2007 09:14:04 am Ivan Voras wrote:
> John Baldwin wrote:
>
> > It's more that we use the filesystem's timestamp as a way to validate the
> > timestamp from the RTC and to do a fixup if the RTC appears to be dead.
>
> Why not use something that doesn't depend on external factors
John Baldwin wrote:
> It's more that we use the filesystem's timestamp as a way to validate the
> timestamp from the RTC and to do a fixup if the RTC appears to be dead.
Why not use something that doesn't depend on external factors, like
kernel build time (AFAIK it's embedded somewhere - at leas
On Monday 16 July 2007 04:08:39 am Ivan Voras wrote:
> Victor Snezhko wrote:
>
> > Also, this was a surprise to an unexperienced me, but I have also
> > found that vfs_mount initializes RTC with the latest timestamp found
> > on local file systems - this explains why kernel "worked" for Ivan on
>
Ivan Voras <[EMAIL PROTECTED]> writes:
>> Also, this was a surprise to an unexperienced me, but I have also
>> found that vfs_mount initializes RTC with the latest timestamp found
>> on local file systems - this explains why kernel "worked" for Ivan on
>> a hard drive. It didn't actually work, but
Victor Snezhko wrote:
Also, this was a surprise to an unexperienced me, but I have also
found that vfs_mount initializes RTC with the latest timestamp found
on local file systems - this explains why kernel "worked" for Ivan on
a hard drive. It didn't actually work, but used timestamp which was
s
David Malone <[EMAIL PROTECTED]> writes:
>> Yes, I'll test them.
>>
>> The problem is - the same kernel works when booted off a hard drive, so
>> unless the VMWare BIOS is very messed up (it's the first time I see such
>> problems) it may not help. Please, scatter debug printf's around so I
>> ca
On Sun, Jul 15, 2007 at 11:37:57AM +0200, Dominique Goncalves wrote:
> >Yes, it does! Setting ct.dow to -1 fixes the time in a correct way.
> It works also for me with qemu 0.9.0.
Great - I'll work on getting it merged in.
David.
___
freebsd-ha
Hi,
On 7/13/07, Ivan Voras <[EMAIL PROTECTED]> wrote:
David Malone wrote:
> Ah - that's interesting. Could you look for the comment in
> src/sys/i386/isa/clock.c that says:
>
> /* Should we set dow = -1 because some clocks don't set it correctly? */
>
> and add a line afterwards to say:
>
On Thu, Jul 12, 2007 at 12:14:43AM +0200, Ivan Voras wrote:
> I've got interesting results (in the bad sense of the phrase): I do get
> the message "Invalid time in real time clock. Check and reset the time
> immediately" (the i386 message) BUT my time gets reset to 0 (midnight
> 1970.)
Ah - that'
On Tue, Jul 10, 2007 at 12:29:26AM +0200, Ivan Voras wrote:
> Yes, I'll test them.
>
> The problem is - the same kernel works when booted off a hard drive, so
> unless the VMWare BIOS is very messed up (it's the first time I see such
> problems) it may not help. Please, scatter debug printf's arou
On Mon, Jul 09, 2007 at 11:25:46PM +0200, Ivan Voras wrote:
> The date is set wrong either on boot or very early after the kernel has
> booted (I've verified it's wrong before hostid rc.d script, which is one
> of the first to be executed).
I have some patches to make the code that reads the date
11 matches
Mail list logo
