[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 2.6.37 and other things.

On Mon, 28 Feb 2011, Michael Tomkins wrote:

> > 
> > > be that debian is misconfigured (it thinks the hardware clock is in 
> > > UTC but it is actually localtime. MacOS uses localtime so 
> > > dual-booting means you have to tell Linux about this).
> > 
> > I think the configuration for Linux is on the hwclock layer for this.
> > 
> > > The -1 month is a bit odd. It sounds like an off-by-one bug 
> > > somewhere but I've no idea where... Perhaps try # strace -v hwclock 
> > > --localtime --show
> > 
> > Doesn?t the kernel set the clock now, before that?
> Yes, 

Well, this won't work correctly unless your RTC is in UTC, and MacOS uses 
localtime not UTC.

> but seems to have a out by -1 on the month. Date was set to ~28 Feb 8:50 
> 2011 by network time control panel on macOS and then came up with this. 
> http://mich431.net/m68k/IMG_1282s.jpg Currently have turned off network 
> time and MacOS time set to 31/3/2011
> And the boot sequence fsck doesn't fix the mount errors on the /dev/sda8 
> but still continues to boot. The drive has errors but continues to login 
> prompt (doesn't reboot), and the next boot might go through the same 
> error/check. http://mich431.net/m68k/IMG_1284s.jpg

If two consecutive boots give the same error "Superblock last mount time 
is in the future" then perhaps you didn't run fsck manually when it asked 
you to?

(The logs you sent indicate that hwclock doesn't work, so I'd say that the 
clock isn't being adjusted at shutdown ... but I don't know if that result 
relates to the Debian kernel rather than your own build ...)

One needs to see the entire boot log -- kernel messages together with init 
script messages. I googled the problem and learnt that you can set 
BOOTLOGD_ENABLE=Yes in /etc/default/bootlogd and all the interesting stuff 
should theoretically appear in /var/log/boot. There may be more to it than 
that (I never tried it) but it should be easy enough to set up.


Reply to: