On Mon, Oct 05, 2015 at 01:18:53PM -0400, dewey.hyl...@gmail.com wrote: > unfortunately, not on my end. i have hopes that mike larkin may find something > when he gets a chance to look, but i am past the limit of my capabilities and > supermicro support has discontinued responding to me. their last suggestion > was > to switch to linux or windows, and their last message was of the "we'll get > back to you" variety. >
I had thought this was acpi related earlier (before we realized that disabling lm* fixes it). So I have no news here, as I don't think the solution is going to be found in the AML. The lm(4) sensor is probably getting wedged somehow, which is causing the bios to think the machine is too hot on reboot. Even though it's not. I don't know a lot about the lm(4) driver so I don't think I'll be able to help much here. One of the things I do know about it is that sometimes you don't actually even have a real lm(4), and that it's simulated by some other component or even SMM. Maybe the manufacturer did a poor job. Shrug. Sorry, I'm out of ideas. Maybe someone else can debug it for you. -ml > so on a related note, i'm on the hunt for something which can replace this > board's functionality without breaking the bank. something not supported by > supermicro, as this is a brand new board and they seem to be unwilling to > provide support anyway. remote kvm/power is the sole purpose for choosing this > supermicro device in the first place. i have plenty much more expensive and > more powerful supermicro devices at customer sites which do not show this > issue - but their non-support of this brand-new motherboard shows me that they > are not who i want to be relying on. > > ----- On Oct 5, 2015, at 12:08 PM, Sonic sonicsm...@gmail.com wrote: > > Any progress on this issue? > > On Thu, Sep 17, 2015 at 1:26 PM, Mike Larkin <mlar...@azathoth.net> wrote: > > On Thu, Sep 17, 2015 at 12:40:12PM +0000, Dewey Hylton wrote: > >> Dewey Hylton <dewey.hylton <at> gmail.com> writes: > >> > >> > > >> > Mike Larkin <mlarkin <at> azathoth.net> writes: > >> > > >> > > > >> > > On Tue, Sep 15, 2015 at 07:16:40PM +0000, Dewey Hylton wrote: > >> > > > Dewey Hylton <dewey.hylton <at> gmail.com> writes: > >> > > > > >> > > > > > >> > > > > Mike Larkin <mlarkin <at> azathoth.net> writes: > >> > > > > >> > > > > > acpidump please. > >> > >> > motherboard: supermicro x7spe-hf-d525 rev 1.0 > >> > bios: 1.2b > >> > > >> > at the end of this link is an archive containing acpidump output for all > >> > three acpi settings in the bios (1.0, 2.0, 3.0). > >> > > >> > https://goo.gl/tWGL6C > >> > > >> > i apologize for the somewhat hidden link; gmane wouldn't allow me to post > >> > the full link because it's greater than 80 characters. > >> > > >> > please let me know if i can help in any way; i honestly know nothing > >> > about > >> > acpi but am willing to learn or assist otherwise if it means > >> > understanding > >> > and potentially fixing this issue. > >> > >> i was able to export the DSDT files into something human-readable. while i > >> don't really understand much of what i'm seeing in the resulting text > >> files, > >> diff shows that the differences between the three acpi versions are > >> nonexistent. i have no idea about the other files, of which there are > >> several. > >> > >> Mike, does the acpidump output help at all? if not, am i simply at the > >> point > >> where this hardware is not compatible with OpenBSD? > >> > > > > Haven't had a chance to look at it yet. > > > > -ml
