On Thu, Oct 09, 2014 at 04:26:42PM -0700, Mike Larkin wrote:
> On Thu, Oct 09, 2014 at 11:42:59PM +0200, Remi Locherer wrote:
> > On Tue, Oct 07, 2014 at 10:10:54PM +0200, Remi Locherer wrote:
> > > >Synopsis: Samsung Notebook: acpitz0 critical temp since sept 25 snapshot 
> > > >Environment:
> > >   System      : OpenBSD 5.6
> > >   Details     : OpenBSD 5.6-current (GENERIC.MP) #399: Sun Oct  5 
> > > 21:53:59 MDT 2014
> > >                    
> > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > > 
> > >   Architecture: OpenBSD.amd64
> > >   Machine     : amd64
> > > 
> > > >Description:
> > >   The Samsung 900X3F shuts down after boot with the message:
> > > "acpitz0: critical temperature exceeded 144C, shutting down". The snapshot
> > > from September 17 was working fine. Since snapshot September 25 I'm seeing
> > > this.
> > > 
> > > Strange thing: when I'm now booting the sept 17 snapshot kernel the 
> > > notebook
> > > also shuts itselfe down with the above message. Does th kernel modify the
> > > acpi tables?
> > > 
> > 
> > Now this is really strange: today I booted the Samsung notebook several
> > times with the kernel from snapshot oct 5. The problem with acpitz0
> > never occured. Can it be that the kernel sometimes is using a wrong
> > address to read acpi stuff? Or is Samsung using a strange acpi
> > implementation?
> > 
> > Remi 
> > 
> 
> Try turning on debug and see what it's really reading. There are some 
> dprintfs in there
> that will likely help.
> 
> -ml
> 

I figured out that to "fix" this issue once such a shutdown happens I have
to leave the notebook turned off for some hours (usually I just suspend it).
Should it happen again I'll compile a kernel with option ACPI_DEBUG and 
post the resulting dmesg.

Remi

Reply via email to