system powers down after 10 hours, log says 'exiting on signal 15'
Bug #176932 reported by
Joachim Noreiko
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
acpi (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
My system powered itself down after about 10 hours of operation.
The logs show that it went through the steps to shut down.
The only thing I found in the log that seemed unusual was: 'exiting on signal 15'.
A google search suggested this might be a bug in power management.
Booting with acpi=off seems to let it run without this happening.
To post a comment you must log in.
It's done it again even with acpi=off.
Here's the lines from /var/log/syslog at the time of shutdown:
Dec 17 14:38:54 seaside-logger init: tty4 main process (4475) killed by TERM signal
Dec 17 14:38:54 seaside-logger init: tty5 main process (4476) killed by TERM signal
Dec 17 14:38:54 seaside-logger init: tty2 main process (4479) killed by TERM signal
Dec 17 14:38:54 seaside-logger init: tty3 main process (4480) killed by TERM signal
Dec 17 14:38:54 seaside-logger init: tty1 main process (4481) killed by TERM signal
Dec 17 14:38:54 seaside-logger init: tty6 main process (4482) killed by TERM signal
Dec 17 14:38:55 seaside-logger avahi-daemon[5181]: Got SIGTERM, quitting.
Dec 17 14:38:55 seaside-logger avahi-daemon[5181]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.86.
Dec 17 14:38:59 seaside-logger exiting on signal 15
There's nothing in kern.log at that time.