misc/70378: Unexpected graceful shutdowns
bsd at cryptonym.net
Thu Aug 12 12:20:19 PDT 2004
>Synopsis: Unexpected graceful shutdowns
>Arrival-Date: Thu Aug 12 19:20:18 GMT 2004
>Release: FreeBSD 5.2.1-RELEASE-p8 i386
System: FreeBSD munged 5.2.1-RELEASE-p8 FreeBSD 5.2.1-RELEASE-p8 #1: Fri Jun 11 22:47:47 PDT 2004 seth at munged:/usr/src/sys/i386/compile/KERNEL-A i386
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.
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).
It appears that this might be a weekly thing, but I only have two
datapoints. There's nothing in cron that would cause this.
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.
More information about the freebsd-bugs