From owner-freebsd-current Thu Apr 19 11: 0:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C044337B43E for ; Thu, 19 Apr 2001 11:00:10 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3JHxvG91279; Thu, 19 Apr 2001 10:59:57 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010419181419.G72816@wantadilla.lemis.com> Date: Thu, 19 Apr 2001 10:59:18 -0700 (PDT) From: John Baldwin To: Greg Lehey Subject: RE: Breakage in today's -CURRENT Cc: FreeBSD current users Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Apr-01 Greg Lehey wrote: > I've just built a couple of worlds from -CURRENT cvsupped at 2030 UTC > on the 18th, and at 0600 UTC on the 19th. In each case, I have > massive problems, apparently with the synchronization. Here's some > log file output: > > Apr 19 18:11:34 zaphod /boot/kernel/kernel: > fforrwwarardd__hsatradtcclloocckk:: ch ecchkesctkasttea te 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: ffrwaordr_whaarrdd_cstocakt:c > lock: checkstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: heckstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: forward_statclock: checkstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: forward_statclock: checkstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: fforwoarrwd_rds_hatacrldckckl:o > cckheckstate : c0h > Apr 19 18:11:34 zaphod /boot/kernel/kernel: eckstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: fforwarodr_whaarrdd_cstoactk:lo > ccheckstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: k: checkstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: forfwarod_rhaarrdcd_sltoactkc:l > occk: checkstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: heckstate 0 > Apr 19 18:11:34 zaphod /boot/kernel/kernel: forward_statclock: checkstate 0 > > These blocks repeat exactly every 30 seconds. Also, the display is > dead: the keyboard responds to NumLock and ScrollLock, but the last > line on the bottom of the display consists of random data in bright. > I can't enter ddb, or if I do, I can't tell that I've made it. I can > rlogin with no problems. zaphod is an Abit BP6 with 2 Celerons. > > Greg Try bumping the timeouts in forward_hardclock() and forward_statclock() in mp_machdep.c. I'm currently overhauling the clock stuff so that we don't need these timeouts. The problem is that these timeouts are CPU speed sensitive, so while they might be fine for a PPro 200, they are far too short for a P3 600. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message