From owner-freebsd-current Sat Dec 11 23: 6:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DEE0214E53 for ; Sat, 11 Dec 1999 23:06:36 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA63683; Sun, 12 Dec 1999 00:06:34 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA37029; Sun, 12 Dec 1999 00:06:30 -0700 (MST) Message-Id: <199912120706.AAA37029@harmony.village.org> To: Kenneth Wayne Culver Subject: Re: rtc0 Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 11 Dec 1999 20:05:40 EST." References: Date: Sun, 12 Dec 1999 00:06:30 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kenneth Wayne Culver writes: : For some reason rtc0 was not working, and I think it's because this : variable was not initialized, here is the patch: : -int statclock_disable; : +int statclock_disable = 0; There is no difference between these two statements (well, other than statclock_disable moves from the bss area, which is zeroed, to a location in .data, which is zeroed). This cannot be the problem, although it may appear to fix it. It may be the case that some other buffer is overflowing into this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message