From owner-freebsd-current Sat Jun 30 14:35:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 54C3B37B403 for ; Sat, 30 Jun 2001 14:35:29 -0700 (PDT) (envelope-from daeron@wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id BD14F1FE7; Sat, 30 Jun 2001 23:35:27 +0200 (CEST) Date: Sat, 30 Jun 2001 23:35:27 +0200 From: Pascal Hofstee To: current@freebsd.org Subject: (Almost) "ClockWork" Instability of CURRENT Message-ID: <20010630233527.A1633@shadowmere.student.utwente.nl> Reply-To: daeron@shadowmere.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ever since about a week or 2 now (iirc) my box running CURRENT has been showing an almost ClockWork Instability. [ Output from `last reboot` ] reboot ~ Sat Jun 30 22:59 reboot ~ Fri Jun 29 22:56 reboot ~ Thu Jun 28 22:46 reboot ~ Wed Jun 27 20:07 reboot ~ Tue Jun 26 19:57 reboot ~ Mon Jun 25 19:47 reboot ~ Sun Jun 24 19:19 reboot ~ Sun Jun 24 19:04 reboot ~ Sat Jun 23 19:01 reboot ~ Fri Jun 22 18:55 reboot ~ Fri Jun 22 18:50 reboot ~ Thu Jun 21 00:44 reboot ~ Wed Jun 20 00:39 reboot ~ Tue Jun 19 00:37 reboot ~ Sun Jun 17 20:56 reboot ~ Sun Jun 17 20:42 reboot ~ Sat Jun 9 11:20 Some of these entries have been reboots for installworlds ... but a lot of them seem to show a rather frightening "clockwork" in their succession. It looks like somehow my system runs perfectly smooth up to 24 hours. Within the next 10 minutes after that ... it seems to suddenly collapse. I haven't gotten to get actually getting it to trigger so i can (hopefully) catch a console message (because of a rather busy work-schedule). If any other people are having similair issues, i would like to hear about it and try to find out what might be triggering this. If i recall correctly the instability started occuring shortly after the introduction of diskcheckd. I don't know if this might be involved or not. I have disabled it for now, and can hopefully tell if that stops the frequent crashes. [ Output from `dmesg` ] Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #36: Sun Jun 24 23:35:56 CEST 2001 daeron@shadowmere.student.utwente.nl:/usr/obj/usr/src/sys/ARSENIC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 336804078 Hz CPU: AMD-K6(tm) 3D processor (336.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 100663296 (98304K bytes) avail memory = 94072832 (91868K bytes) Preloaded elf kernel "kernel" at 0xc03b3000. Preloaded elf module "random.ko" at 0xc03b309c. K6-family MTRR support enabled (2 registers) Using $PIR table, 5 entries at 0xc00f0a90 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0xe000-0xe00f at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 1.2 (no driver attached) intpm0: port 0xe800-0xe80f irq 9 at device 1.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 pcm0: port 0xd400-0xd41f irq 9 at device 9.0 on pci0 pci0: at 10.0 (no driver attached) pci0: at 11.0 (no driver attached) orm0: