All right, I'm silly. Loading the Therman Zone module causes the system
to receive the (bogus) panic about the CPU being on fire. This time at
least, I have a log entry to show for my trouble:

Jul 24 22:10:43 localhost kernel: ACPI: Thermal Zone [THRM] (121 C)
Jul 24 22:10:43 localhost shutdown[3965]: shutting down for system halt

So, maybe it is a broken DSTD after all. Has anyone else had this
problem with an ABit K7V motherboard?

Russell

On Sat, 2004-07-24 at 21:57, Russell Neches wrote:
> Well, I seem to have found a work-around for this problem, but it raises
> another question. The work around was to build the ACPI extensions (AC
> Adapter, Battery, Button, Fan...) as modules. The culprit, I'm sure, was
> Thermal Zone.
> 
> On my laptop, I have all of them built-in, and this problem doesn't
> occur. Do ACPI extensions always have to be built as a module? Is it not
> *supposed* to work at boot-time? The Debian boot-scripts seem to assume
> that they will be built as modules...
> 
> Russell
> 
> On Tue, 2004-07-20 at 18:38, Russell Y. Neches wrote:
> > Hey there --
> > 
> > I have an "interesting" behavior with 2.6.6 and 2.6.7, and I was
> > wondering if this list would mind helping me figure out what's causing
> > it. 
> > 
> > Basically, my machine turns off while it's booting. It doesn't get far
> > enough to mount any filesystems, so there aren't any logs. On a hunch, I
> > turned on ACPI-debugging, and noticed that the kernel immediately begins
> > spewing warnings about a critical trap (that's from memory, I can't be
> > completely sure if that's literally the string), and that the CPU is
> > over 120 degrees C. Now, I'm actually *underclocking* my CPU because I
> > have very bad luck with hardware, and I happen to know that the
> > temperature never goes above 38 degrees C (according to my BIOS and the
> > hardware meter glued to the heat sync). 
> > 
> > 2.6.5 doesn't seem to have this problem (USB-related oopses
> > notwithstanding), and Debian's 2.6.7-1-k7 kernel package boots without
> > issue (Debian's module insanity notwithstanding). So, I know there is a
> > solution to the problem somewhere, but without logs, I'm not sure how to
> > even begin researching it.
> > 
> > If it weren't for the fact that there are recent ACPI-enabled kernels
> > that work fine, I'd guess that my motherboard has a broken DSTD. 
> > 
> > Would anyone mind orienting me and pointing me in the right direction? 
> > 
> > Thanks!
> > 
> > Russell
> > 
> > PS - The list moderator hasn't approved a previous email with some
> > system information attached. So, instead of attaching it, I'll just link
> > to it:
> > 	
> > 	http://vort.org/downloads/spew.txt
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by BEA Weblogic Workshop
> > FREE Java Enterprise J2EE developer tools!
> > Get your free copy of BEA WebLogic Workshop 8.1 today.
> > http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> > _______________________________________________
> > Acpi-devel mailing list
> > Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > https://lists.sourceforge.net/lists/listinfo/acpi-devel