*BSD News Article 83539


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!newsxfer2.itd.umich.edu!news.itd.umich.edu!not-for-mail
From: knassen@cochrane.bus.umich.edu (Kent Stefl Nassen)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: dos2unixtime() month value out of range?
Date: 24 Nov 1996 19:04:44 -0500
Organization: University of Michigan, Ann Arbor
Lines: 42
Sender: knassen@umich.edu
Message-ID: <57anqs$b90@cochrane.bus.umich.edu>
NNTP-Posting-Host: cochrane.bus.umich.edu
Keywords: dos2unixtime FreeBSD

I've been seeing the following error/warning message on my console
lately and am wondering what it relates to, if it is serious, and how
to get rid of it:

        dos2unixtime(): month value out of range (0)

The message is repeated five times on the console.

In /var/log/messages I see:

Nov 23 03:31:57 /kernel: dos2unixtime(): month value out of range (0)
Nov 16 03:32:00 /kernel: dos2unixtime(): month value out of range (0)
Oct 26 03:32:10 /kernel: dos2unixtime(): month value out of range (0)
Oct 26 17:52:42 /kernel: dos2unixtime(): month value out of range (0)
Oct 26 17:57:42 /kernel: dos2unixtime(): month value out of range (0)
Oct 26 18:26:29 /kernel: dos2unixtime(): month value out of range (0)
Oct 23 08:25:34 /kernel: dos2unixtime(): month value out of range (0)
Oct 23 19:16:08 /kernel: dos2unixtime(): month value out of range (0)
Oct 19 03:32:08 /kernel: dos2unixtime(): month value out of range (0)

My system is: FreeBSD 2.1.5R, 486DX2-80 (Cyrix), 40MB RAM, two IDE
drives (one 340MB the other 1.6GB) with 2 msdos partitions mounted (one
150MB, the other 520MB).  I run with wall_cmos_clock.  Does this
message relate to the change from daylight savings time to standard
time?

The system clock is correct (with the wall clock).  I'm also running
XFree86 v3.1.2 and fvwm2-95.  When FreeBSD 2.1.5 came out, I upgraded
from 2.0R.  I did not see this dos2unixtime() message at all with 2.0R,
nor for at least the first month of operation of 2.1.5R.  It looks like
it is being generated by msdosfs/msdosfs_conv.c but beyond that I have
no clue as to what is causing this message and how to stop it.

Any ideas?

Thanks in advance for any help you can give.

-- 
     ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ____ 
    ||k ||n ||a ||s ||s ||e ||n ||@ ||u ||m ||i ||c ||h ||. ||e ||d ||u ||
    ||__||__||__||__||__||__||__||__||__||__||__||__||__||__||__||__||__||
    |/__\/__\/__\/__\/__\/__\/__\/__\/__\/__\/__\/__\/__\/__\/__\/__\/__\|