On Tue, Mar 07, 2006 at 09:25:12AM -0800, john stultz wrote:
> On Tue, 2006-03-07 at 15:33 +0100, Dominik Karall wrote:
> > On Tuesday, 7. March 2006 06:43, Andrew Morton wrote:
> > > Dominik Karall <[email protected]> wrote:
> > > > On Friday, 3. March 2006 13:56, Andrew Morton wrote:
> > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc
> > > > >5/2. 6.16-rc5-mm2/
> > > >
> > > > hi,
> > > > I don't know why, but it seems that the kernel doesn't use the correct
> > > > BIOS time. I set it to the 23:30 and after booting I got ~01:00 (next
> > > > day).
> > >
> > > Is that new behaviour? What's the most recent -mm kernel which that
> > > machine ran?
> > >
> > > The full dmesg output might tell us something.
> >
> > I bootet 2.6.16-rc5 now, but the bug is still present. I set BIOS time to
> > 15:07 and after booting linux showed 17:35.
>
> Interesting. Right off, I'm not sure where this would be coming from.
> >>From your dmesg it looks like this is running an x86-64 kernel, correct?
> Andi, do you have any ideas?
Normally the time is read again in the startup scripts of the distribution.
Sounds like he configured the wrong time zone. Usually distributions
can be configured to assume UTC real clock time or local time RTC.
You can test that theory by commenting out any calls to hwclock
in your boot scripts.
But that behaviour should be the same in all kernels.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
