El día Sunday, February 08, 2015 a las 11:14:10PM
+0100, Idwer Vollering escribió:
2015-02-08 21:55 GMT+01:00 Matthias Apitz
El día Sunday, February 08, 2015 a las 02:40:45PM
-0600, Alex G. escribió:
> Suspect number one is the device overheating. The shutdown is
> triggered by the EC. I don't know how you can enable ACPI debug output
> on BSD though. On linux, it would be "echo 1 >
> /sys/module/acpi/parameters/aml_debug_output", so whatever the FreeBSD
> equivalent of that is.
hw.acpi.verbose=1 would be a start.
Thanks for all the hints.
As I said, the events are sporadic, seldom, but complete power-off (like
as you would cut the cable from the motherboard). Of course the system has no
chance to write anything to /var/log/messages or console.
My hope while writing to coreboot@ was to get a pointer to the list of
open ore solved issues within coreboot and/or SeaBIOS to see if this
issue is somewhat known, solved or could be related to some known or
solved issue. Where can I find such a list which is normally (as we do
in my company) attached to the Release Notes of a new version of
only provides a list of high level features though. One can also read
through the SeaBIOS git commit history.
The symptons you report do not sound like a SeaBIOS issue. SeaBIOS
relies on coreboot to initialize most hardware. Once the OS starts,
it's unlikely that SeaBIOS would adversely impact the machine