From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: 2.6.24-rc4-mm1: acpi reboots machine... solved Date: Tue, 11 Dec 2007 18:44:43 +0100 Message-ID: <20071211174443.GA5013@gollum.tnic> References: <20071209075001.GA4686@gollum.tnic> <20071209091946.GA4501@gollum.tnic> Reply-To: bbpetkov@yahoo.de Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <20071209091946.GA4501@gollum.tnic> Sender: linux-kernel-owner@vger.kernel.org To: Andrew Morton , len.brown@intel.com, Bjorn Helgaas Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-acpi@vger.kernel.org On Sun, Dec 09, 2007 at 10:19:47AM +0100, Borislav Petkov wrote: > On Sun, Dec 09, 2007 at 08:50:02AM +0100, Borislav Petkov wrote: > > Hi Andrew, > > Hi Len, > >=20 > > after booting 2.6.24-rc4-mm1 (2.6.24-rc4-190-g94545ba, otoh, boots = just > > fine) on my asus laptop, the machine reboots after claiming that > > "Critical temperature reached (255 C)." However, the degrees number > > is kinda hinting at 0xff all-ones field. Will try dump_stack in > > acpi_thermal_critical() to checkout the call path. For now here's t= he netconsole bootlog: >=20 > Here's what i got so far: >=20 > [ 50.287939] Pid: 1, comm: swapper Not tainted 2.6.24-rc4-mm1 #14 > [ 50.287999] [] show_trace_log_lvl+0x12/0x25 > [ 50.288103] [] show_trace+0xd/0x10 > [ 50.288202] [] dump_stack+0x57/0x5f > [ 50.288303] [] acpi_thermal_check+0x150/0x3bb > [ 50.288415] [] acpi_thermal_add+0x261/0x2cf > [ 50.288515] [] acpi_device_probe+0x3e/0xdb > [ 50.288615] [] driver_probe_device+0xaf/0x12a > [ 50.288717] [] __driver_attach+0x6c/0xa5 > [ 50.288817] [] bus_for_each_dev+0x3e/0x60 > [ 50.288916] [] driver_attach+0x14/0x16 > [ 50.289015] [] bus_add_driver+0xa6/0x1a8 > [ 50.289114] [] driver_register+0x42/0x47 > [ 50.289214] [] acpi_bus_register_driver+0x3a/0x3c > [ 50.289316] [] acpi_thermal_init+0x57/0x76 > [ 50.289424] [] kernel_init+0x138/0x280 > [ 50.289525] [] kernel_thread_helper+0x7/0x10 > [ 50.289625] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D > [ 50.289680] ACPI: Critical trip point > [ 50.289736] Critical temperature reached (255 C), shutting down. >=20 > so in acpi_thermal_get_temperature() called in acpi_thermal_add() the > tz->temperature thingy is not set properly (printk's added): >=20 > [ 50.276607] Old temp: 4294967023 > [ 50.281890] Got temp: 255 > [ 50.282567] Old temp: 255 > [ 50.287882] Got temp: 255 >=20 > What's also strange is that the tz acpi_thermal is alloc'd with kzall= oc and > there's still garbage in it after reading it in acpi_thermal_get_temp= erature() > for the first time. Debugging continues... (i almost suspected that the problem might be something completely diff= erent.) well, after bisecting the rc4-mm1 tree for a whole day today, the evild= oer turned out to be broken-out/pnp-request-ioport-and-iomem-resources-used-by-active-device= s.patch. After backing this one out, mm1 boots just fine here. --=20 Regards/Gru=DF, Boris. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel"= in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/