Date: Thu, 12 Aug 2004 12:11:05 -0700 (PDT) From: Seth <bsd@cryptonym.net> To: FreeBSD-gnats-submit@FreeBSD.org Subject: misc/70378: Unexpected graceful shutdowns Message-ID: <200408121911.i7CJB5W8004972@lazarus.cryptonym.net> Resent-Message-ID: <200408121920.i7CJKIjZ059216@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 70378 >Category: misc >Synopsis: Unexpected graceful shutdowns >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Aug 12 19:20:18 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Seth >Release: FreeBSD 5.2.1-RELEASE-p8 i386 >Organization: >Environment: System: FreeBSD munged 5.2.1-RELEASE-p8 FreeBSD 5.2.1-RELEASE-p8 #1: Fri Jun 11 22:47:47 PDT 2004 seth@munged:/usr/src/sys/i386/compile/KERNEL-A i386 >Description: On 4 August 2004 the machine unexpectedly shut down and rebooted. The only logs are as follows: Aug 4 09:01:40 lazarus kernel: Shutting down daemon processes: followed by user processes and syslog notifying of SIGTERM. The system came back up 2 minutes later with filesystems marked as clean. On 11 August 2004 the machine did the same thing: Aug 11 14:01:29 lazarus kernel: Shutting down daemon processes: followed by the same process messages. System came back up clean. kldstat shows Id Refs Address Size Name 1 7 0xc0400000 368cdc kernel 2 1 0xc0769000 50dbc acpi.ko 3 1 0xc45cc000 19000 linux.ko so it's possible that it's acpi doing it. There are no temperature sensors on this motherboard, but I have sensors on the disks, and they show the following temps immediately prior to shutdown: (temps in C, 4 disks probed). Aug 4 09:00:01 lazarus root: temperature: 33 36 31 36 Aug 11 14:00:01 lazarus root: temperature: 35 36 32 38 The processor is a 1GHz P3 with its own fan (confirmed operational). >How-To-Repeat: It appears that this might be a weekly thing, but I only have two datapoints. There's nothing in cron that would cause this. >Fix: Unknown. What I'd really like is a way to turn on logging that would help pinpoint the problem. Is there any way to rule out acpi? Any other suggestions for logging / forensics would be great. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408121911.i7CJB5W8004972>