uncommanded shutdown

As of today the non-commanded shut down occurred again, I added "noapic" back to the boot line but it shut down again.

The message on the screen after it quits is:

[ 5904.836193] Power down.
[ 6280.181570] System halted.

This morning my system did an un-commanded shut down again. I added "noapic" back to the boot line but it shut down again.

The message on the terminal after shut down says:

[ 5904.836193] Power down.
[ 6280.181570] System halted.

I see in the logs messages about hibernate starting, but I ca;t see what triggers it.

I have flashed my BIOS with the latest version. and upgraded to the new kernel (2.6.32-24.39).

I reset all boot parameters and /etc/pm/sleep.d to default (as installed).

After an uptime of over 39 hrs, system went into hibernation again.

I can find nothing untoward in the logs (except there was an automatic
system update about 2230 last night, system went to hibernation at
0018 this morning, about 1.7 hrs after the update), temps were normal.

I have made the following BIOS changes, rebooted, and started the
uptime watch again:

      ACPI Suspend Type: from S3(STR) to S1(POS)
      HPET Support : from enabled (32-bit) to disabled

I can find lots of info about trouble shooting failure to suspend or
hibernate, but not much about uncommanded hibernation (or hibernation
command from unknown sources).

BTW, my mobo is: is Gigabyte GA-P35-DS3L, Rev. 2

I have run a complete memtest86+ on my 8 Gb RAM with no errors.

I have not built a custom kernel for many years, but I would be happy to volunteer my time and mobo to help find this irritating bug.

I have subscribed to the "Automating BIOS testing to find BIOS errors" blueprint on Ubuntu Launchpad, and I have linked this bug to it.

@Tom, can you install the package fwts, and next time this occurs can you do the following:

1. Attach /var/log/messages
2. Attach /var/log/kern.log

and also run:

sudo fwts --dump

and attach:

the files it generates: acpidump.log, dmesg.log, dmidecode.log and lspci.log

thanks

On Mon, Aug 9, 2010 at 08:25, Colin King <email address hidden> wrote:
> @Tom, can you install the package fwts, and next time this occurs can

Colin, thanks, I am so happy to hear from you.

I have obtained package 'fwts_0.17.2.tar.gz' from launchpad and
installed it according to instructions in its README.

I'll attach requested log files after reboot after the next incident.

Regards,

-Tom

Where should requested log files go when ready, the pastebin (with link in comment) or attached here?

Shutdown occurred again after 36+ hours. Requested logs are attached as gzipped files.

Last requested log file for the shut down event is attached as a gzipped file.

I have attached another, special log file (compressed with bzip2) I produce which shows date/time, uptime, and output from "sensors" at every minute for the up time prior to the shut down event.

Note: the kern.log file attached earlier was NOT produced by "sudo fwts --dumo"--it is a normal log.

[Expired for acpi (Ubuntu) because there has been no activity for 60 days.]