https://bugzilla.novell.com/show_bug.cgi?id=436384
User matthias.andree@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=436384#c3
--- Comment #3 from Matthias Andree 2009-01-29 08:38:32 MST ---
Well, the openSUSE 11.0 system was eaten by a disk hardware fault; I'm going to
replace it by 11.1 soon (I kept only /etc and /var in the backup, not /usr);
I'm currently running off FreeBSD 7.1 that survived on the second hard disk
drive, for lack of time.
Interestingly, FreeBSD exhibited a similar regression between 6.3 (or perhaps
early 7.0 (pre)releases) and 7.1. FreeBSD 7.1, too, fails most of the time to
shut down the system. Setting hw.acpi.handle_shutdown in FreeBSD helps for
(estimated) half of the time, whereas shutting down to legacy mode does not
seem to help. See
http://www.freebsd.org/cgi/man.cgi?query=acpi&apropos=0&sektion=0&manpath=FreeBSD+7.1-RELEASE&format=html
I also have a vague feeling that something during ACPI initialization or
operation (perhaps acpid attaching/configuring the firmware or similar), or
perhaps X11/ACPI interaction, trigger this issue; it's just a feeling, but
shutting down FreeBSD from single-user boots works reliably in either setting,
and seemed to help a bit with openSUSE 11.0 as well.
Question: do Linux and FreeBSD share ACPI code and/or updates?
Followup-Question: is that my BIOS at fault or an ACPI regression shared by
Linux and FreeBSD?
I presume I'll have to dig out some more debug information from either system,
and I'll do that ASAP.
Is there an easy way in 11.1 to "tee" the console logs out across Ethernet or
dump them to swap, or delay after messages, or copy to a slow serial console at
1200 Baud? That might help capturing the messages in case the monitor blanks
too quickly.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.