acpitz3: critical temperature exceeded with HP nc6320 Laptop

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

acpitz3: critical temperature exceeded with HP nc6320 Laptop

Steve Quinn
Hi folks

I have been recently playing with OpenBSD.
I am very impressed with the whole experience, great job people !!

I am using an HP nc6320 Laptop.

Quite often, I get an error similar to this with amd64 5.4 and 5.5
acpitz3: critical temperature exceeded 3786C, shutting down

For me it was a nice error to get, because it introduced me to the
coolness of using boot -c and config -e
I have no problems working around the issue.

I did some digging and see others with the same issue on similar hardware

http://comments.gmane.org/gmane.os.openbsd.misc/176044
http://comments.gmane.org/gmane.os.openbsd.misc/205033

I'd like to offer the use of my HP nc6320 if a Developer would like to
play directly with the hardware to assist others in the community with
the issue.
I'll be at BSDCan 2014 and can bring it along.  Otherwise, please let
me know if/how I can be of any help.

Take care

Steve Quinn

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Riccardo Mottola
Hi,

Steve Quinn wrote:
> I have been recently playing with OpenBSD.
> I am very impressed with the whole experience, great job people !!
>
> I am using an HP nc6320 Laptop.
>
> Quite often, I get an error similar to this with amd64 5.4 and 5.5
> acpitz3: critical temperature exceeded 3786C, shutting down
If that temperature were to be correct, your Silicon would be liquid or
possibly even gaseous :)

I had a nc6120 and there was an ACPI bug very similar to this, solved
with 5.3, if I remember correctly.

Sadly, my hardware broke, so I cannot verify if it surfaced again.

Riccardo

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Tomas Bodzar-4
In reply to this post by Steve Quinn
On Thu, Apr 10, 2014 at 12:37 AM, Steve Quinn <[hidden email]>wrote:

> Hi folks
>
> I have been recently playing with OpenBSD.
> I am very impressed with the whole experience, great job people !!
>


Just one side note. Most (or all?) "major" operating systems are using
implementation of ACPI from Intel, but OpenBSD has own implementation
http://www.openbsd.org/cgi-bin/man.cgi?query=acpi&sektion=4&apropos=0&manpath=OpenBSD+Current&arch=i386,
which may be sometimes problematic, but generally fixes are available
very quickly compared to that general implementation.


>
> I am using an HP nc6320 Laptop.
>
> Quite often, I get an error similar to this with amd64 5.4 and 5.5
> acpitz3: critical temperature exceeded 3786C, shutting down
>
> For me it was a nice error to get, because it introduced me to the
> coolness of using boot -c and config -e
> I have no problems working around the issue.
>
> I did some digging and see others with the same issue on similar hardware
>
> http://comments.gmane.org/gmane.os.openbsd.misc/176044
> http://comments.gmane.org/gmane.os.openbsd.misc/205033
>
> I'd like to offer the use of my HP nc6320 if a Developer would like to
> play directly with the hardware to assist others in the community with
> the issue.
> I'll be at BSDCan 2014 and can bring it along.  Otherwise, please let
> me know if/how I can be of any help.
>


Good quick start is to send dmesg output from latest -current (both i386
and amd64 IF there's some difference) and something which you probably
already checked ; BIOS versions


>
> Take care
>
> Steve Quinn

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Steve Quinn
In reply to this post by Riccardo Mottola
On Thu, Apr 10, 2014 at 3:53 AM, Riccardo Mottola
<[hidden email]> wrote:

> If that temperature were to be correct, your Silicon would be liquid or possibly even gaseous :)

:-)  I noticed it would even boil a Titanium case !
http://www.chemicalelements.com/elements/ti.html

> I had a nc6120 and there was an ACPI bug very similar to this, solved with 5.3, if I remember correctly.

Interesting, I'll try that out if necessary

> Sadly, my hardware broke, so I cannot verify if it surfaced again.

Bummer. Thanks for sharing your experience with the issue

Steve Quinn

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

mbregg
In reply to this post by Steve Quinn
I had the same issue a couple of weeks ago with my Sager laptop. An update to a newer snapshot seemed to "solve" it.

Sorry, I can't really offer any advice as the issue seemed to resolve on its own after the update and hasn't surfaced on any snapshots since then.

Mike

On Apr 9, 2014 4:37 PM, Steve Quinn <[hidden email]> wrote:

>
> Hi folks
>
> I have been recently playing with OpenBSD.
> I am very impressed with the whole experience, great job people !!
>
> I am using an HP nc6320 Laptop.
>
> Quite often, I get an error similar to this with amd64 5.4 and 5.5
> acpitz3: critical temperature exceeded 3786C, shutting down
>
> For me it was a nice error to get, because it introduced me to the
> coolness of using boot -c and config -e
> I have no problems working around the issue.
>
> I did some digging and see others with the same issue on similar hardware
>
> http://comments.gmane.org/gmane.os.openbsd.misc/176044 
> http://comments.gmane.org/gmane.os.openbsd.misc/205033 
>
> I'd like to offer the use of my HP nc6320 if a Developer would like to
> play directly with the hardware to assist others in the community with
> the issue.
> I'll be at BSDCan 2014 and can bring it along.  Otherwise, please let
> me know if/how I can be of any help.
>
> Take care
>
> Steve Quinn

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Theo de Raadt
In reply to this post by Steve Quinn
> I had the same issue a couple of weeks ago with my Sager laptop. An
> update to a newer snapshot seemed to "solve" it.

From time to time we have to explain this one.

There is unknown and not yet understood bug, which we think is related
to acpi EC handling.  It seems to affect HP laptops more than others.
It's been there since the beginning, so that would be 5+ years.  There
have been numerous efforts to fix it.

For some reason it wanders around a bit.  We've never actually managed
to get one of the affected laptops into the hands of a serious
developer who would hunt it down.

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Steve Quinn
In reply to this post by Tomas Bodzar-4
On Thu, Apr 10, 2014 at 7:31 AM, Tomas Bodzar <[hidden email]> wrote:

> Just one side note. Most (or all?) "major" operating systems are using
> implementation of ACPI from Intel, but OpenBSD has own implementation
> http://www.openbsd.org/cgi-bin/man.cgi?query=acpi&sektion=4&apropos=0&manpath=OpenBSD+Current&arch=i386
> , which may be sometimes problematic, but generally fixes are available very
> quickly compared to that general implementation.

Wow, thanks for the great reference

> Good quick start is to send dmesg output from latest -current (both i386 and
> amd64 IF there's some difference) and something which you probably already
> checked ; BIOS versions

Ok.  Sounds great, thank you.
I've yet to install -current and want to do it properly so it will be
a few days until I have a dmesg to share
Regarding the BIOS version, I will triple check but I'm usually quite
anal about these things :-)

Steve

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Steve Quinn
In reply to this post by Theo de Raadt
On Thu, Apr 10, 2014 at 9:16 PM, Theo de Raadt <[hidden email]> wrote:

>> I had the same issue a couple of weeks ago with my Sager laptop. An
>> update to a newer snapshot seemed to "solve" it.
>
> From time to time we have to explain this one.
>
> There is unknown and not yet understood bug, which we think is related
> to acpi EC handling.  It seems to affect HP laptops more than others.
> It's been there since the beginning, so that would be 5+ years.  There
> have been numerous efforts to fix it.
>
> For some reason it wanders around a bit.  We've never actually managed
> to get one of the affected laptops into the hands of a serious
> developer who would hunt it down.

Hi Theo

I'd like to help in any way I can and hopefully get this bug squashed for good

I have access to several of these HP models and can test locally,
provide remote access or ship one if required
Again, I'm from the Toronto area and am hitting my first BSDCan in May
if that helps.

Take care

Steve Quinn

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Theo de Raadt
In reply to this post by Steve Quinn
> I have access to several of these HP models and can test locally,
> provide remote access or ship one if required
> Again, I'm from the Toronto area and am hitting my first BSDCan in May
> if that helps.

A very helpful approach would be:

1. Find a few cheap machines that are 100% confirmed to have this
   issue repeatable.
2. Flood the ACPI subsystem developer community with them, by ninja
   action where you suddenly handcuff it to them at some conference,
   other evento, or even a pub.

But please, I am exempt from this.

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Tomas Bodzar-4
In reply to this post by Steve Quinn
On Fri, Apr 11, 2014 at 3:18 AM, Steve Quinn <[hidden email]> wrote:

> On Thu, Apr 10, 2014 at 7:31 AM, Tomas Bodzar <[hidden email]>
> wrote:
>
> > Just one side note. Most (or all?) "major" operating systems are using
> > implementation of ACPI from Intel, but OpenBSD has own implementation
> >
> http://www.openbsd.org/cgi-bin/man.cgi?query=acpi&sektion=4&apropos=0&manpath=OpenBSD+Current&arch=i386
> > , which may be sometimes problematic, but generally fixes are available
> very
> > quickly compared to that general implementation.
>
> Wow, thanks for the great reference
>

One correction I did not have single issue with ACPI over the years on Dell
or Lenovo HW with OpenBSD, but had number of those with other BSDs,
OpenSolaris or Linux with their Intel implementation. Especially cheaper
consumer models from HP, Toshiba, Sony and similar has very "interesting"
workarounds implemented to get it working at least somewhat even on Windows
and Linux so these are often very funny :-)


>
> > Good quick start is to send dmesg output from latest -current (both i386
> and
> > amd64 IF there's some difference) and something which you probably
> already
> > checked ; BIOS versions
>
> Ok.  Sounds great, thank you.
> I've yet to install -current and want to do it properly so it will be
> a few days until I have a dmesg to share
> Regarding the BIOS version, I will triple check but I'm usually quite
> anal about these things :-)
>

Using -current is easy, just start with latest snapshot from mirror and use
snapshot path for packages in PKG_PATH as well. From that time on easy like
with regular system. Plus is you have binary upgrades to new snapshot
mostly everyday (if you want to) -> man sysmerge -> checking current.html
page IF some manual intervention needed -> pkg_add -u . All of that takes
like 15 minutes or so, depends on speed of your network and interval how
often you will update between snapshots. Generally more stable then some so
called stable/lts/whatever distros and you have latest fixes.

For BIOS I meant if there's something related to ACPI in fixes from vendor.



>
> Steve

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Steve Quinn
On Fri, Apr 11, 2014 at 1:34 AM, Tomas Bodzar <[hidden email]> wrote:

> Using -current is easy, just start with latest snapshot from mirror and use
> snapshot path for packages in PKG_PATH as well. From that time on easy like
> with regular system. Plus is you have binary upgrades to new snapshot mostly
> everyday (if you want to) -> man sysmerge -> checking current.html page IF
> some manual intervention needed -> pkg_add -u . All of that takes like 15
> minutes or so, depends on speed of your network and interval how often you
> will update between snapshots. Generally more stable then some so called
> stable/lts/whatever distros and you have latest fixes.

My gosh Tomas, you are so incredibly helpful thank you.

I now have an avenue to supply a laptop to a Dev :-)
In parallel though, I'll still be taking this opportunity to learn
-current and other shiny new (to me) things

> For BIOS I meant if there's something related to ACPI in fixes from vendor.

Oh, right, sorry. I will check

Steve

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Paul Irofti-4
In reply to this post by Steve Quinn
Steve,

can you test this diff for me and tell me if it fixes anything for you.

I'll also be attending BSDCan to give a talk, see you there!


Index: dsdt.c
===================================================================
RCS file: /cvs/src/sys/dev/acpi/dsdt.c,v
retrieving revision 1.205
diff -u -p -r1.205 dsdt.c
--- dsdt.c 12 Dec 2013 20:56:01 -0000 1.205
+++ dsdt.c 12 Apr 2014 10:45:02 -0000
@@ -736,72 +736,58 @@ static long global_lock_count = 0;
 void
 acpi_glk_enter(void)
 {
- acpi_acquire_glk(&acpi_softc->sc_facs->global_lock);
-}
-
-void
-acpi_glk_leave(void)
-{
- int x;
-
- if (acpi_release_glk(&acpi_softc->sc_facs->global_lock)) {
- /*
- * If pending, notify the BIOS that the lock was released
- * by the OSPM. No locking is needed because nobody outside
- * the ACPI thread is touching this register.
- */
- x = acpi_read_pmreg(acpi_softc, ACPIREG_PM1_CNT, 0);
- x |= ACPI_PM1_GBL_RLS;
- acpi_write_pmreg(acpi_softc, ACPIREG_PM1_CNT, 0, x);
- }
-}
-
-void
-aml_lockfield(struct aml_scope *scope, struct aml_value *field)
-{
  int st = 0;
 
- if (AML_FIELD_LOCK(field->v_field.flags) != AML_FIELD_LOCK_ON)
- return;
-
- /* If lock is already ours, just continue */
+ /* If lock is already ours, just continue. */
  if (global_lock_count++)
  return;
 
- /* Spin to acquire lock */
+ /* Spin to acquire the lock. */
  while (!st) {
  st = acpi_acquire_glk(&acpi_softc->sc_facs->global_lock);
  /* XXX - yield/delay? */
  }
-
- return;
 }
 
 void
-aml_unlockfield(struct aml_scope *scope, struct aml_value *field)
+acpi_glk_leave(void)
 {
- int st, x, s;
+ int st, x;
 
- if (AML_FIELD_LOCK(field->v_field.flags) != AML_FIELD_LOCK_ON)
- return;
-
- /* If we are the last ones, turn out the lights */
+ /* If we are the last one, turn out the lights. */
  if (--global_lock_count)
  return;
 
- /* Release lock */
  st = acpi_release_glk(&acpi_softc->sc_facs->global_lock);
  if (!st)
  return;
 
- /* Signal others if someone waiting */
- s = spltty();
+ /*
+ * If pending, notify the BIOS that the lock was released by
+ * OSPM.  No locking is needed because nobody outside the ACPI
+ * thread is supposed to touch this register.
+ */
  x = acpi_read_pmreg(acpi_softc, ACPIREG_PM1_CNT, 0);
  x |= ACPI_PM1_GBL_RLS;
  acpi_write_pmreg(acpi_softc, ACPIREG_PM1_CNT, 0, x);
- splx(s);
+}
+
+void
+aml_lockfield(struct aml_scope *scope, struct aml_value *field)
+{
+ if (AML_FIELD_LOCK(field->v_field.flags) != AML_FIELD_LOCK_ON)
+ return;
+
+ acpi_glk_enter();
+}
+
+void
+aml_unlockfield(struct aml_scope *scope, struct aml_value *field)
+{
+ if (AML_FIELD_LOCK(field->v_field.flags) != AML_FIELD_LOCK_ON)
+ return;
 
- return;
+ acpi_glk_leave();
 }
 
 /*
Index: acpiec.c
===================================================================
RCS file: /cvs/src/sys/dev/acpi/acpiec.c,v
retrieving revision 1.48
diff -u -p -r1.48 acpiec.c
--- acpiec.c 2 Jul 2013 18:37:47 -0000 1.48
+++ acpiec.c 12 Apr 2014 10:45:03 -0000
@@ -34,6 +34,7 @@
 
 int acpiec_match(struct device *, void *, void *);
 void acpiec_attach(struct device *, struct device *, void *);
+int acpiec_activate(struct device *, int);
 
 u_int8_t acpiec_status(struct acpiec_softc *);
 u_int8_t acpiec_read_data(struct acpiec_softc *);
@@ -54,6 +55,7 @@ int acpiec_getregister(const u_int8_t *
 
 void acpiec_wait(struct acpiec_softc *, u_int8_t, u_int8_t);
 void acpiec_sci_event(struct acpiec_softc *);
+void acpiec_clear_events(struct acpiec_softc *);
 
 void acpiec_get_events(struct acpiec_softc *);
 
@@ -82,7 +84,8 @@ void acpiec_unlock(struct acpiec_softc
 int acpiec_reg(struct acpiec_softc *);
 
 struct cfattach acpiec_ca = {
- sizeof(struct acpiec_softc), acpiec_match, acpiec_attach
+ sizeof(struct acpiec_softc), acpiec_match, acpiec_attach,
+ NULL, acpiec_activate
 };
 
 struct cfdriver acpiec_cd = {
@@ -296,6 +299,8 @@ acpiec_attach(struct device *parent, str
  acpi_set_gpehandler(sc->sc_acpi, sc->sc_gpe, acpiec_gpehandler,
     sc, 1);
 #endif
+
+ acpiec_clear_events(sc);
 
  if (aml_evalname(sc->sc_acpi, sc->sc_devnode, "_GLK", 0, NULL, &res))
  sc->sc_glk = 0;
@@ -307,6 +312,20 @@ acpiec_attach(struct device *parent, str
  printf("\n");
 }
 
+int
+acpiec_activate(struct device *self, int act)
+{
+ struct acpiec_softc *sc = (struct acpiec_softc *)self;
+
+
+ switch (act) {
+ case DVACT_RESUME:
+ acpiec_clear_events(sc);
+ break;
+ }
+ return (0);
+}
+
 void
 acpiec_get_events(struct acpiec_softc *sc)
 {
@@ -552,4 +571,18 @@ acpiec_unlock(struct acpiec_softc *sc)
  }
 
  sc->sc_ecbusy = 0;
+}
+
+void
+acpiec_clear_events(struct acpiec_softc *sc)
+{
+ int i;
+
+ for (i = 0; i < 100; i++) {
+ acpiec_write_cmd(sc, EC_CMD_QR);
+ sc->sc_gotsci = 0;
+ if ((acpiec_status(sc) & EC_STAT_SCI_EVT) != EC_STAT_SCI_EVT) {
+ break;
+ }
+ }
 }

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Steve Quinn
On Sat, Apr 12, 2014 at 9:04 AM, Paul Irofti <[hidden email]> wrote:
> can you test this diff for me and tell me if it fixes anything for you.

Cool, yes, thank you

> I'll also be attending BSDCan to give a talk, see you there!

Sweet, D-Link DSR, interesting.
3 Scheduled Talk Tracks and only 1 me.  I need to clone myself.

Steve

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Peter Nicolai Mathias Hansteen
Steve Quinn <[hidden email]> writes:

> 3 Scheduled Talk Tracks and only 1 me.  I need to clone myself.

I think they're planning to record the talks and make the videos
available via youtube or similar.

- P

--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Tomas Bodzar-4
In reply to this post by Steve Quinn
On Sat, Apr 12, 2014 at 4:22 AM, Steve Quinn <[hidden email]> wrote:

> On Fri, Apr 11, 2014 at 1:34 AM, Tomas Bodzar <[hidden email]>
> wrote:
>
> > Using -current is easy, just start with latest snapshot from mirror and
> use
> > snapshot path for packages in PKG_PATH as well. From that time on easy
> like
> > with regular system. Plus is you have binary upgrades to new snapshot
> mostly
> > everyday (if you want to) -> man sysmerge -> checking current.html page
> IF
> > some manual intervention needed -> pkg_add -u . All of that takes like 15
> > minutes or so, depends on speed of your network and interval how often
> you
> > will update between snapshots. Generally more stable then some so called
> > stable/lts/whatever distros and you have latest fixes.
>
> My gosh Tomas, you are so incredibly helpful thank you.
>
> I now have an avenue to supply a laptop to a Dev :-)
> In parallel though, I'll still be taking this opportunity to learn
> -current and other shiny new (to me) things
>


You're welcome. You will find it quickly very easy. Especially for
desktop/workstation/laptop not much reasons to be on release/stable. I
don't say that there are not use cases, but very small amount of those.


>
> > For BIOS I meant if there's something related to ACPI in fixes from
> vendor.
>
> Oh, right, sorry. I will check
>
> Steve

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Steve Quinn
Hi Folks

Sorry about the delay.  Heartbleed conversations took much time away :-)
The acpitz3 shutdown issue remains.

It's no big deal because I'm witnessing more OpenBSD awesomeness.

I have two dmesg's for those interested
Please don't flame me too much for any goof up's.  I'm really taking
it slow, learning and reading as I go.

"dmesg-55-amd64-snapshot-fresh"
5.5 amd64 PXE booted cd55.iso fetching from /pub/OpenBSD/snapshots/amd64/

"dmesg-55-amd64-snapshot-cvscurrent-diff"
5.5 amd64 as above, CVS -current last night patched with the diff
supplied by Paul Irofti

Steve



On Sat, Apr 12, 2014 at 11:36 AM, Tomas Bodzar <[hidden email]> wrote:

>
>
> On Sat, Apr 12, 2014 at 4:22 AM, Steve Quinn <[hidden email]> wrote:
>>
>> On Fri, Apr 11, 2014 at 1:34 AM, Tomas Bodzar <[hidden email]>
>> wrote:
>>
>> > Using -current is easy, just start with latest snapshot from mirror and
>> > use
>> > snapshot path for packages in PKG_PATH as well. From that time on easy
>> > like
>> > with regular system. Plus is you have binary upgrades to new snapshot
>> > mostly
>> > everyday (if you want to) -> man sysmerge -> checking current.html page
>> > IF
>> > some manual intervention needed -> pkg_add -u . All of that takes like
>> > 15
>> > minutes or so, depends on speed of your network and interval how often
>> > you
>> > will update between snapshots. Generally more stable then some so called
>> > stable/lts/whatever distros and you have latest fixes.
>>
>> My gosh Tomas, you are so incredibly helpful thank you.
>>
>> I now have an avenue to supply a laptop to a Dev :-)
>> In parallel though, I'll still be taking this opportunity to learn
>> -current and other shiny new (to me) things
>
>
>
> You're welcome. You will find it quickly very easy. Especially for
> desktop/workstation/laptop not much reasons to be on release/stable. I don't
> say that there are not use cases, but very small amount of those.
>
>>
>>
>> > For BIOS I meant if there's something related to ACPI in fixes from
>> > vendor.
>>
>> Oh, right, sorry. I will check
>>
>> Steve

[demime 1.01d removed an attachment of type application/octet-stream which had a name of dmesg-55-amd64-snapshot-fresh]

[demime 1.01d removed an attachment of type application/octet-stream which had a name of dmesg-55-amd64-snapshot-cvscurrent-diff]

Reply | Threaded
Open this post in threaded view
|

Re: acpitz3: critical temperature exceeded with HP nc6320 Laptop

Kevin Chadwick-2
previously on this list Steve Quinn contributed:

> The acpitz3 shutdown issue remains.

I haven't tried the latest patch however I have an nc6220 with the
issue but whilst I don't use this laptop daily personally I believe it
has never occurred if you remove the battery and power before each
boot, we also don't use suspend currently and so I actually encourage
users to remove the battery anyway via a message when shutting down. I
don't mind testing any patches and let me know if you want me to get
the hw.sensors and dmesg from a patched kernel when the bug fires.


When the bug is triggered the console says:

acpitz2: critical temperature exceeded 3632C, shutting down

and sysctl hw.sensors grabbed via rc.local says -662.57

Full dmesg at bottom and diff of a boot with the bug showing and without
above it, note the screwed up date on the acpibat0 and stating AC as
offline on the boot with the bug present even though the power was
plugged in.


--- /mnt/usb0/acpi2/hw.sensors  Tue Apr 15 22:56:24 2014
+++ /mnt/usb0/acpi3/hw.sensors.bugpresent(nobattremoval)        Tue Apr
15 23:06:50 2014 @@ -1,14 +1,14 @@
 hw.sensors.acpitz0.temp0=45.00 degC (zone temperature)
-hw.sensors.acpitz1.temp0=40.00 degC (zone temperature)
-hw.sensors.acpitz2.temp0=23.10 degC (zone temperature)
-hw.sensors.acpitz3.temp0=20.00 degC (zone temperature)
-hw.sensors.acpibat0.volt0=10.80 VDC (voltage)
-hw.sensors.acpibat0.volt1=12.50 VDC (current voltage)
-hw.sensors.acpibat0.current0=0.00 A (rate)
-hw.sensors.acpibat0.amphour0=3.57 Ah (last full capacity)
-hw.sensors.acpibat0.amphour1=0.18 Ah (warning capacity)
-hw.sensors.acpibat0.amphour2=0.04 Ah (low capacity)
-hw.sensors.acpibat0.amphour3=3.53 Ah (remaining capacity), OK
+hw.sensors.acpitz1.temp0=41.00 degC (zone temperature)
+hw.sensors.acpitz2.temp0=-662.57 degC (zone temperature)
+hw.sensors.acpitz3.temp0=100.00 degC (zone temperature)
+hw.sensors.acpibat0.volt0=12.43 VDC (voltage)
+hw.sensors.acpibat0.volt1=53.90 VDC (current voltage)
+hw.sensors.acpibat0.current0=0.14 A (rate)
+hw.sensors.acpibat0.amphour0=62.10 Ah (last full capacity)
+hw.sensors.acpibat0.amphour1=3.10 Ah (warning capacity)
+hw.sensors.acpibat0.amphour2=0.62 Ah (low capacity)
+hw.sensors.acpibat0.amphour3=52.37 Ah (remaining capacity), OK
 hw.sensors.acpibat0.raw0=0 (battery idle), OK
-hw.sensors.acpiac0.indicator0=On (power supply)
+hw.sensors.acpiac0.indicator0=Off (power supply)
 hw.sensors.acpibtn1.indicator0=On (lid open)

--- /mnt/usb0/dmesg-nc6220 Tue Apr 15 22:38:34 2014
+++ /mnt/usb0/acpi3/dmesg-bugpresent(nobattremoval) Tue Apr 15
23:06:40 2014 @@ -41,9 +41,9 @@
 acpitz1 at acpi0: critical temperature is 103 degC
 acpitz2 at acpi0: critical temperature is 105 degC
 acpitz3 at acpi0: critical temperature is 110 degC
-acpibat0 at acpi0: C177 model "Primary" serial 01099 2007/10/19 type
LIon oem "Hewlett-Packard" +acpibat0 at acpi0: C177 model "Primary"
serial 19344 2021/12/16 type LIon oem "Hewlett-Packard" acpibat1 at
acpi0: C176 not present -acpiac0 at acpi0: AC unit online
+acpiac0 at acpi0: AC unit offline
 acpibtn0 at acpi0: C1F1
 acpibtn1 at acpi0: C1F2
 acpivideo0 at acpi0: C05A
@@ -120,41 +120,11 @@
 pcppi0 at isa0 port 0x61
 spkr0 at pcppi0
 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
+acpitz2: critical temperature exceeded 3632C, shutting down
 vscsi0 at root
 scsibus2 at vscsi0: 256 targets
 softraid0 at root
 scsibus3 at softraid0: 256 targets
 root on wd0a (616804515c82c3c2.a) swap on wd0b dump on wd0b
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
-umass0 at uhub0 port 3 configuration 1 interface 0 "USB 2.0 Flash
Disk" rev 2.00/1.00 addr 2 -umass0: using SCSI over Bulk-Only
-scsibus4 at umass0: 2 targets, initiator 0
-sd0 at scsibus4 targ 1 lun 0: <USB 2.0, Flash Disk, 5.00> SCSI2
0/direct removable serial.020460252400260AF313 -sd0: 1010MB, 512
bytes/sector, 2068480 sectors -acpitz3: TZ4_: failed to read _TMP
-acpitz3: TZ4_: failed to read temp
+Process (pid 1) got signal 31
+acpitz2: critical temperature exceeded 3632C, shutting down
_______________________________________________________________________

Just calls differ here

kern.malloc.kmemstat.ACPI=(inuse = 3137, calls = 17765, memuse = 201K,
limblocks = 0, mapblocks = 0, maxused = 223K, limit = 39322K, spare =
0, sizes = (16,32,64,128,256,1024,4096,8192))


kern.malloc.kmemstat.ACPI=(inuse = 3137, calls = 17794, memuse = 201K,
limblocks = 0, mapblocks = 0, maxused = 223K, limit = 39322K, spare =
0, sizes = (16,32,64,128,256,1024,4096,8192))
_______________________________________________________________________

OpenBSD 5.5-current (GENERIC) #32: Tue Apr  8 16:53:39 MDT 2014
    [hidden email]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) M processor 1.73GHz ("GenuineIntel"
686-class) 1.73 GHz cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,NXE,EST,TM2,PERF
real mem  = 1601531904 (1527MB) avail mem = 1562918912 (1490MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/24/09, BIOS32 rev. 0 @
0xf0000, SMBIOS rev. 2.3 @ 0xf2c4f (23 entries) bios0: vendor
Hewlett-Packard version "68DTU Ver. F.16" date 07/24/2009 bios0:
Hewlett-Packard HP Compaq nc6220 (EM012EC#ABU) acpi0 at bios0: rev 0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC MCFG SSDT
acpi0: wakeup devices C06D(S5) C0BE(S3) C0C5(S3) C0C6(S3) C0C8(S3)
C006(S5) C007(S5) C0DE(S5) C1D3(S5) acpitimer0 at acpi0: 3579545 Hz, 24
bits acpimadt0 at acpi0 addr 0xfec01000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 133MHz
ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpimcfg0 at acpi0 addr 0xe0000000, bus 0-255
acpiprt0 at acpi0: bus 2 (C06D)
acpiprt1 at acpi0: bus 16 (C006)
acpiprt2 at acpi0: bus 32 (C0DE)
acpiprt3 at acpi0: bus 0 (C002)
acpiec0 at acpi0
acpicpu0 at acpi0: C3, C2, C1, PSS
acpipwrres0 at acpi0: C1D0, resource for C072
acpipwrres1 at acpi0: C1A9, resource for C1A5
acpipwrres2 at acpi0: C1B1, resource for C1AA
acpipwrres3 at acpi0: C1B8, resource for C1B2
acpipwrres4 at acpi0: C1C8, resource for C1C6
acpipwrres5 at acpi0: C251, resource for C255
acpipwrres6 at acpi0: C252, resource for C256
acpipwrres7 at acpi0: C253, resource for C257
acpipwrres8 at acpi0: C254, resource for C258
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 103 degC
acpitz2 at acpi0: critical temperature is 105 degC
acpitz3 at acpi0: critical temperature is 110 degC
acpibat0 at acpi0: C177 model "Primary" serial 01099 2007/10/19 type
LIon oem "Hewlett-Packard" acpibat1 at acpi0: C176 not present
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: C1F1
acpibtn1 at acpi0: C1F2
acpivideo0 at acpi0: C05A
bios0: ROM list: 0xc0000/0x10000!
cpu0: Enhanced SpeedStep 1730 MHz: speeds: 1733, 1333, 1067, 800 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82915GM Host" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel 82915GM Video" rev 0x03
intagp0 at vga1
agp0 at intagp0: aperture at 0xc0000000, size 0x10000000
inteldrm0 at vga1
drm0 at inteldrm0
inteldrm0: 1400x1050
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel 82915GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
ppb0 at pci0 dev 28 function 0 "Intel 82801FB PCIE" rev 0x03: apic 1
int 16 pci1 at ppb0 bus 16
bge0 at pci1 dev 0 function 0 "Broadcom BCM5751M" rev 0x11, BCM5750 B1
(0x4101): apic 1 int 16, address 00:14:c2:d8:3c:ae brgphy0 at bge0 phy
1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb1 at pci0 dev 28 function 1
"Intel 82801FB PCIE" rev 0x03: apic 1 int 17 pci2 at ppb1 bus 32
uhci0 at pci0 dev 29 function 0 "Intel 82801FB USB" rev 0x03: apic 1
int 20 uhci1 at pci0 dev 29 function 1 "Intel 82801FB USB" rev 0x03:
apic 1 int 17 uhci2 at pci0 dev 29 function 2 "Intel 82801FB USB" rev
0x03: apic 1 int 18 ehci0 at pci0 dev 29 function 7 "Intel 82801FB USB"
rev 0x03: apic 1 int 20 usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb2 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xd3
pci3 at ppb2 bus 2
iwi0 at pci3 dev 4 function 0 "Intel PRO/Wireless 2915ABG" rev 0x05:
apic 1 int 21, address 00:12:f0:a5:9f:ec cbb0 at pci3 dev 6 function 0
"TI PCI7XX1 CardBus" rev 0x00: apic 1 int 18 "TI PCI7XX1 Flash" rev
0x00 at pci3 dev 6 function 3 not configured sdhc0 at pci3 dev 6
function 4 "TI PCI7XX1 SD" rev 0x00: apic 1 int 22 sdmmc0 at sdhc0
sdmmc1 at sdhc0
sdmmc2 at sdhc0
"TI PCI7XX1 Smart Card" rev 0x00 at pci3 dev 6 function 5 not configured
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 3 device 0 cacheline 0x10, lattimer 0x20
pcmcia0 at cardslot0
auich0 at pci0 dev 30 function 2 "Intel 82801FB AC97" rev 0x03: apic 1
int 21, ICH6 AC97 ac97: codec id 0x41445374 (Analog Devices AD1981B)
ac97: codec features headphone, 20 bit DAC, No 3D Stereo
audio0 at auich0
ichpcib0 at pci0 dev 31 function 0 "Intel 82801FBM LPC" rev 0x03: PM
disabled pciide0 at pci0 dev 31 function 1 "Intel 82801FB IDE" rev
0x03: DMA, channel 0 configured to compatibility, channel 1 configured
to compatibility wd0 at pciide0 channel 0 drive 0: <Hitachi
HTS541680J9AT00> wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors atapiscsi0 at pciide0 channel 0 drive 1
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: <HL-DT-ST, RW/DVD GCC-4246N, 0C07> ATAPI
5/cdrom removable wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
cd0(pciide0:0:1): using PIO mode 4, DMA mode 2
pciide0: channel 1 ignored (disabled)
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at ichpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
wsmouse1 at pms0 mux 0
pms0: Synaptics touchpad, firmware 6.2
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on wd0a (616804515c82c3c2.a) swap on wd0b dump on wd0b
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp
umass0 at uhub0 port 3 configuration 1 interface 0 "USB 2.0 Flash Disk"
rev 2.00/1.00 addr 2 umass0: using SCSI over Bulk-Only
scsibus4 at umass0: 2 targets, initiator 0
sd0 at scsibus4 targ 1 lun 0: <USB 2.0, Flash Disk, 5.00> SCSI2
0/direct removable serial.020460252400260AF313 sd0: 1010MB, 512
bytes/sector, 2068480 sectors acpitz3: TZ4_: failed to read _TMP
acpitz3: TZ4_: failed to read temp


--
_______________________________________________________________________

'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface'

(Doug McIlroy)

In Other Words - Don't design like polkit or systemd
_______________________________________________________________________

I have no idea why RTFM is used so aggressively on LINUX mailing lists
because whilst 'apropos' is traditionally the most powerful command on
Unix-like systems it's 'modern' replacement 'apropos' on Linux is a tool
to help psychopaths learn to control their anger.

(Kevin Chadwick)

_______________________________________________________________________