On Mon, Sep 11, 2006 at 04:10:36PM +0200, Rafael J. Wysocki wrote: > On Monday, 11 September 2006 11:46, Stefan Seyfried wrote: > > On Mon, Sep 04, 2006 at 11:40:59PM +0200, Pavel Machek wrote: > > > Hi! > > > > > > x60 shut down after quite a while of uptime, in period of quite heavy > > > load: > > > > > > Sep 4 23:33:01 amd kernel: ACPI: Critical trip point > > > Sep 4 23:33:01 amd kernel: Critical temperature reached (128 C), shutting down. > > > Sep 4 23:33:01 amd shutdown[32585]: shutting down for system halt > > > Sep 4 23:34:42 amd init: Switching to runlevel: 0 > > > > > > I do not think cpu reached 128C, as I still have my machine... Did > > > anyone else see that? > > > > my usual suspect: use ec_intr=0. > > Is this a kernel command line parameter? yes. seife@susi:~> dmesg | grep "^ACPI: EC" ACPI: EC polling mode. seife@susi:~> cat /proc/cmdline root=/dev/hda5 vga=0x317 sysrq=yes resume=/dev/hda1 splash=silent showopts ec_intr=0 with ec_intr=1 (default), you'll get "ACPI: EC interrupt mode." > I'm having some suspend/resume related problems on HPC 6325 now, and they > seem to be related to the embedded controller. Well, polling mode is always on my "things to try"-list for those unspecified ACPI failures :-) -- Stefan Seyfried QA / R&D Team Mobile Devices | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out." - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
