LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
@ 2007-03-31 6:36 Jeremy Fitzhardinge
2007-03-31 9:31 ` Andi Kleen
` (2 more replies)
0 siblings, 3 replies; 19+ messages in thread
From: Jeremy Fitzhardinge @ 2007-03-31 6:36 UTC (permalink / raw)
To: Andi Kleen, Brown, Len
Cc: Linux Kernel Mailing List, linux-acpi, Andrew Morton
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
When I run 2.6.21-rc5 + Andi's x86 patches + paravirt_ops patches, I've
been getting my machine shut down with critical thermal shutdown messages:
Mar 30 23:19:03 localhost kernel: ACPI: Critical trip point
Mar 30 23:19:03 localhost kernel: Critical temperature reached (128 C), shutting down.
Mar 30 23:19:03 localhost kernel: Critical temperature reached (128 C), shutting down.
Mar 30 23:19:03 localhost shutdown[19417]: shutting down for system halt
and the machine does feel pretty hot. Interestingly, when the machine
reboots, the fan spins up to a noticeably higher speed, so it seems that
maybe something is getting fan speed control wrong.
The machine is a Thinkpad X60, with a 1.8GHz Core Duo. I can run it
indefinitely with the FC6 2.6.20-1.2933.fc6 kernel, so I don't think
there's anything wrong with the hardware. And it was sitting on a
desktop plugged into mains, so there's no problems with obstructed airflow.
I was running a normal email/browsing/editing/compiling workload, and I
don't think there was anything particularly CPU intensive running at the
time. I run cpufreq with the conservative governor.
Running now with the FC6 kernel, I get:
: ezr:pts/2; cat /proc/acpi/thermal_zone/THM?/temperature
temperature: 69 C
temperature: 82 C
Config attached.
J
[-- Attachment #2: config --]
[-- Type: text/plain, Size: 21488 bytes --]
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION="-paravirt"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_SYSFS_DEPRECATED=y
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_CFQ=y
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_SMP=y
CONFIG_X86_PC=y
CONFIG_PARAVIRT=y
CONFIG_VMI=y
CONFIG_MPENTIUMM=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_HPET_TIMER=y
CONFIG_NR_CPUS=8
CONFIG_SCHED_MC=y
CONFIG_PREEMPT_VOLUNTARY=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_P4THERMAL=y
CONFIG_VM86=y
CONFIG_X86_CPUID=m
CONFIG_EDD=m
CONFIG_HIGHMEM64G=y
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_X86_PAE=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_HIGHPTE=y
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
CONFIG_IRQBALANCE=y
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_PHYSICAL_START=0x100000
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_HOTPLUG_CPU=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_PM=y
CONFIG_PM_DEBUG=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION=""
CONFIG_SUSPEND_SMP=y
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_IBM=m
CONFIG_ACPI_IBM_BAY=y
CONFIG_ACPI_BLACKLIST_YEAR=1999
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
CONFIG_X86_ACPI_CPUFREQ=y
CONFIG_X86_SPEEDSTEP_CENTRINO=y
CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_PCIEAER=y
CONFIG_PCI_MSI=y
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_PCCARD=y
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y
CONFIG_YENTA=y
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PCCARD_NONSTATIC=y
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_ACPI=y
CONFIG_HOTPLUG_PCI_ACPI_IBM=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
CONFIG_NET_KEY=m
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_IP_VS=m
CONFIG_IP_VS_TAB_BITS=12
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m
CONFIG_IP_VS_FTP=m
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
CONFIG_BRIDGE_NETFILTER=y
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
CONFIG_LLC=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
CONFIG_IEEE80211=m
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m
CONFIG_WIRELESS_EXT=y
CONFIG_FIB_RULES=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y
CONFIG_PARPORT_PC_PCMCIA=m
CONFIG_PARPORT_1284=y
CONFIG_PARPORT_NOT_PC=y
CONFIG_PNP=y
CONFIG_PNPACPI=y
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_RAM_BLOCKSIZE=4096
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_SCSI=y
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y
CONFIG_BLK_DEV_SD=y
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_ATA=y
CONFIG_SATA_AHCI=y
CONFIG_SATA_INTEL_COMBINED=y
CONFIG_SATA_ACPI=y
CONFIG_IEEE1394=m
CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y
CONFIG_IEEE1394_CONFIG_ROM_IP1394=y
CONFIG_IEEE1394_PCILYNX=m
CONFIG_IEEE1394_OHCI1394=m
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
CONFIG_IEEE1394_ETH1394=m
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_TUN=m
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
CONFIG_NET_PCI=y
CONFIG_PCNET32=y
CONFIG_NE2K_PCI=y
CONFIG_8139TOO=y
CONFIG_8139TOO_PIO=y
CONFIG_E1000=m
CONFIG_E1000_NAPI=y
CONFIG_NET_RADIO=y
CONFIG_NET_WIRELESS_RTNETLINK=y
CONFIG_NET_WIRELESS=y
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_SLHC=m
CONFIG_NETCONSOLE=m
CONFIG_NETPOLL=y
CONFIG_NETPOLL_TRAP=y
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_VSXXXAA=m
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
CONFIG_JOYSTICK_A3D=m
CONFIG_JOYSTICK_ADI=m
CONFIG_JOYSTICK_COBRA=m
CONFIG_JOYSTICK_GF2K=m
CONFIG_JOYSTICK_GRIP=m
CONFIG_JOYSTICK_GRIP_MP=m
CONFIG_JOYSTICK_GUILLEMOT=m
CONFIG_JOYSTICK_INTERACT=m
CONFIG_JOYSTICK_SIDEWINDER=m
CONFIG_JOYSTICK_TMDC=m
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
CONFIG_JOYSTICK_IFORCE_232=y
CONFIG_JOYSTICK_WARRIOR=m
CONFIG_JOYSTICK_MAGELLAN=m
CONFIG_JOYSTICK_SPACEORB=m
CONFIG_JOYSTICK_SPACEBALL=m
CONFIG_JOYSTICK_STINGER=m
CONFIG_JOYSTICK_TWIDJOY=m
CONFIG_JOYSTICK_DB9=m
CONFIG_JOYSTICK_GAMECON=m
CONFIG_JOYSTICK_TURBOGRAFX=m
CONFIG_JOYSTICK_JOYDUMP=m
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
CONFIG_TOUCHSCREEN_MTOUCH=m
CONFIG_TOUCHSCREEN_MK712=m
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_WISTRON_BTNS=m
CONFIG_INPUT_UINPUT=m
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
CONFIG_GAMEPORT_L4=m
CONFIG_GAMEPORT_EMU10K1=m
CONFIG_GAMEPORT_FM801=m
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_SERIAL_NONSTANDARD=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
CONFIG_PRINTER=m
CONFIG_LP_CONSOLE=y
CONFIG_PPDEV=m
CONFIG_TIPAR=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=m
CONFIG_NVRAM=y
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
CONFIG_AGP=y
CONFIG_AGP_INTEL=y
CONFIG_DRM=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
CONFIG_HPET=y
CONFIG_HPET_RTC_IRQ=y
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=m
CONFIG_TCG_TPM=m
CONFIG_TCG_ATMEL=m
CONFIG_I2C=m
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCA=m
CONFIG_I2C_I810=m
CONFIG_I2C_PIIX4=m
CONFIG_SENSORS_DS1337=m
CONFIG_SENSORS_DS1374=m
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
CONFIG_SENSORS_PCA9539=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_MAX6875=m
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_FB=y
CONFIG_FB_DDC=m
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
CONFIG_FB_VGA16=m
CONFIG_FB_VESA=y
CONFIG_FB_I810=m
CONFIG_FB_I810_GTF=y
CONFIG_FB_I810_I2C=y
CONFIG_FB_INTEL=m
CONFIG_FB_INTEL_DEBUG=y
CONFIG_FB_INTEL_I2C=y
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_SOUND=m
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_MPU401_UART=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_MPU401=m
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDSP=m
CONFIG_SND_HDSPM=m
CONFIG_HID=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_STORAGE_ALAUDA=y
CONFIG_USB_LIBUSUAL=y
CONFIG_USB_HID=y
CONFIG_HID_FF=y
CONFIG_HID_PID=y
CONFIG_LOGITECH_FF=y
CONFIG_THRUSTMASTER_FF=y
CONFIG_USB_HIDDEV=y
CONFIG_USB_AIPTEK=m
CONFIG_USB_WACOM=m
CONFIG_USB_ACECAD=m
CONFIG_USB_KBTAB=m
CONFIG_USB_POWERMATE=m
CONFIG_USB_TOUCHSCREEN=m
CONFIG_USB_TOUCHSCREEN_EGALAX=y
CONFIG_USB_TOUCHSCREEN_PANJIT=y
CONFIG_USB_TOUCHSCREEN_3M=y
CONFIG_USB_TOUCHSCREEN_ITM=y
CONFIG_USB_TOUCHSCREEN_ETURBO=y
CONFIG_USB_TOUCHSCREEN_GUNZE=y
CONFIG_USB_TOUCHSCREEN_DMC_TSC10=y
CONFIG_USB_XPAD=m
CONFIG_USB_ATI_REMOTE=m
CONFIG_USB_ATI_REMOTE2=m
CONFIG_USB_KEYSPAN_REMOTE=m
CONFIG_USB_APPLETOUCH=m
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET_MII=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_NET_ZAURUS=m
CONFIG_USB_MON=y
CONFIG_USB_USS720=m
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRPRIME=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP2101=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_MPR=y
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_EZUSB=y
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_LED=m
CONFIG_USB_IDMOUSE=m
CONFIG_USB_APPLEDISPLAY=m
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_SISUSBVGA_CON=y
CONFIG_USB_LD=m
CONFIG_USB_TEST=m
CONFIG_MMC=m
CONFIG_MMC_BLOCK=m
CONFIG_MMC_SDHCI=m
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m
CONFIG_RTC_INTF_SYSFS=m
CONFIG_RTC_INTF_PROC=m
CONFIG_RTC_INTF_DEV=m
CONFIG_RTC_INTF_DEV_UIE_EMUL=y
CONFIG_RTC_DRV_CMOS=m
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_V3020=m
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y
CONFIG_FS_POSIX_ACL=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_DNOTIFY=y
CONFIG_AUTOFS4_FS=m
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="ascii"
CONFIG_NTFS_FS=m
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_CONFIGFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_PARTITION_ADVANCED=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_LDM_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
CONFIG_KPROBES=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_FS=y
CONFIG_DEBUG_KERNEL=y
CONFIG_LOG_BUF_SHIFT=17
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_SLAB_LEAK=y
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_PI_LIST=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_VM=y
CONFIG_FRAME_POINTER=y
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_STACK_USAGE=y
CONFIG_DEBUG_RODATA=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y
CONFIG_KEYS=y
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
CONFIG_SECURITY_CAPABILITIES=y
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-03-31 6:36 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns Jeremy Fitzhardinge
@ 2007-03-31 9:31 ` Andi Kleen
2007-04-01 16:30 ` Pavel Machek
[not found] ` <8f8ff01d0703310033y74421cfcl747ece1be003471@mail.gmail.com>
2007-04-01 18:57 ` Kyle Moffett
2 siblings, 1 reply; 19+ messages in thread
From: Andi Kleen @ 2007-03-31 9:31 UTC (permalink / raw)
To: Jeremy Fitzhardinge
Cc: Brown, Len, Linux Kernel Mailing List, linux-acpi, Andrew Morton
On Saturday 31 March 2007 08:36, Jeremy Fitzhardinge wrote:
> When I run 2.6.21-rc5 + Andi's x86 patches + paravirt_ops patches, I've
> been getting my machine shut down with critical thermal shutdown messages:
Hmm, don't think there's anything either in x86 that would touch this code.
But can you double check with plain rc5?
> Mar 30 23:19:03 localhost kernel: ACPI: Critical trip point
> Mar 30 23:19:03 localhost kernel: Critical temperature reached (128 C), shutting down.
> Mar 30 23:19:03 localhost kernel: Critical temperature reached (128 C), shutting down.
> Mar 30 23:19:03 localhost shutdown[19417]: shutting down for system halt
>
> and the machine does feel pretty hot.
Pavel has been complaining about higher power consumption on his laptop versus
.20 too.
-Andi
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
[not found] ` <8f8ff01d0703310033y74421cfcl747ece1be003471@mail.gmail.com>
@ 2007-04-01 6:28 ` Jeremy Fitzhardinge
2007-04-01 14:53 ` Matthew Garrett
` (2 more replies)
0 siblings, 3 replies; 19+ messages in thread
From: Jeremy Fitzhardinge @ 2007-04-01 6:28 UTC (permalink / raw)
To: Alexey Starikovskiy; +Cc: Linux Kernel Mailing List, linux-acpi
Alexey Starikovskiy wrote:
> Could you try to unload or disable hardware sensors and check if it
> helps?
> CONFIG_I2C=m
> CONFIG_I2C_ALGOBIT=m
> CONFIG_I2C_ALGOPCA=m
> CONFIG_I2C_I810=m
> CONFIG_I2C_PIIX4=m
> CONFIG_SENSORS_DS1337=m
> CONFIG_SENSORS_DS1374=m
> CONFIG_SENSORS_EEPROM=m
> CONFIG_SENSORS_PCF8574=m
> CONFIG_SENSORS_PCA9539=m
> CONFIG_SENSORS_PCF8591=m
> CONFIG_SENSORS_MAX6875=m
That seems to have helped. If I watch
/proc/acpi/thermal_zone/THM?/temperature, it seems stable even under
load. I didn't try watching the thermal_zones when these options were
enabled, but I presume the temperature was not controlled for it to hit
128 degC.
What's going on here? Does reading an i2c sensor from the kernel
prevent something else from doing it?
J
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-01 6:28 ` Jeremy Fitzhardinge
@ 2007-04-01 14:53 ` Matthew Garrett
2007-04-01 16:32 ` Pavel Machek
2007-04-01 23:19 ` Jeremy Fitzhardinge
2 siblings, 0 replies; 19+ messages in thread
From: Matthew Garrett @ 2007-04-01 14:53 UTC (permalink / raw)
To: Jeremy Fitzhardinge
Cc: Alexey Starikovskiy, Linux Kernel Mailing List, linux-acpi
On Sat, Mar 31, 2007 at 11:28:46PM -0700, Jeremy Fitzhardinge wrote:
> That seems to have helped. If I watch
> /proc/acpi/thermal_zone/THM?/temperature, it seems stable even under
> load. I didn't try watching the thermal_zones when these options were
> enabled, but I presume the temperature was not controlled for it to hit
> 128 degC.
>
> What's going on here? Does reading an i2c sensor from the kernel
> prevent something else from doing it?
The i2c drivers access the same hardware as the ACPI methods, and
there's no locking.
--
Matthew Garrett | mjg59@srcf.ucam.org
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-03-31 9:31 ` Andi Kleen
@ 2007-04-01 16:30 ` Pavel Machek
2007-04-01 22:44 ` Henrique de Moraes Holschuh
0 siblings, 1 reply; 19+ messages in thread
From: Pavel Machek @ 2007-04-01 16:30 UTC (permalink / raw)
To: Andi Kleen
Cc: Jeremy Fitzhardinge, Brown, Len, Linux Kernel Mailing List,
linux-acpi, Andrew Morton
Hi!
> > When I run 2.6.21-rc5 + Andi's x86 patches + paravirt_ops patches, I've
> > been getting my machine shut down with critical thermal shutdown messages:
>
> Hmm, don't think there's anything either in x86 that would touch this code.
> But can you double check with plain rc5?
>
> > Mar 30 23:19:03 localhost kernel: ACPI: Critical trip point
> > Mar 30 23:19:03 localhost kernel: Critical temperature reached (128 C), shutting down.
> > Mar 30 23:19:03 localhost kernel: Critical temperature reached (128 C), shutting down.
> > Mar 30 23:19:03 localhost shutdown[19417]: shutting down for system halt
> >
> > and the machine does feel pretty hot.
>
> Pavel has been complaining about higher power consumption on his laptop versus
> .20 too.
Yep, sometimes it takes 30W instead of 12W... Anyway, this seems to
be measurement error. Notice how acpi claims 128C. I do not think cpu
can work at 128C and hardware should kill us before cpu is that hot.
Are you running lm_sensors?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-01 6:28 ` Jeremy Fitzhardinge
2007-04-01 14:53 ` Matthew Garrett
@ 2007-04-01 16:32 ` Pavel Machek
2007-04-01 22:46 ` Henrique de Moraes Holschuh
2007-04-01 23:19 ` Jeremy Fitzhardinge
2 siblings, 1 reply; 19+ messages in thread
From: Pavel Machek @ 2007-04-01 16:32 UTC (permalink / raw)
To: Jeremy Fitzhardinge
Cc: Alexey Starikovskiy, Linux Kernel Mailing List, linux-acpi
Hi!
> > CONFIG_I2C=m
> > CONFIG_I2C_ALGOBIT=m
> > CONFIG_I2C_ALGOPCA=m
> > CONFIG_I2C_I810=m
> > CONFIG_I2C_PIIX4=m
> > CONFIG_SENSORS_DS1337=m
> > CONFIG_SENSORS_DS1374=m
> > CONFIG_SENSORS_EEPROM=m
> > CONFIG_SENSORS_PCF8574=m
> > CONFIG_SENSORS_PCA9539=m
> > CONFIG_SENSORS_PCF8591=m
> > CONFIG_SENSORS_MAX6875=m
>
> That seems to have helped. If I watch
> /proc/acpi/thermal_zone/THM?/temperature, it seems stable even under
> load. I didn't try watching the thermal_zones when these options were
> enabled, but I presume the temperature was not controlled for it to hit
> 128 degC.
>
> What's going on here? Does reading an i2c sensor from the kernel
> prevent something else from doing it?
ACPI is misdesigned, and lm_sensors can't cope with that.
One idea was to add 'big acpi lock' and make lm_sensors take it, too.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-03-31 6:36 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns Jeremy Fitzhardinge
2007-03-31 9:31 ` Andi Kleen
[not found] ` <8f8ff01d0703310033y74421cfcl747ece1be003471@mail.gmail.com>
@ 2007-04-01 18:57 ` Kyle Moffett
2007-04-01 21:13 ` Jeremy Fitzhardinge
2007-04-02 8:35 ` Rene Rebe
2 siblings, 2 replies; 19+ messages in thread
From: Kyle Moffett @ 2007-04-01 18:57 UTC (permalink / raw)
To: Jeremy Fitzhardinge
Cc: Andi Kleen, Brown, Len, Linux Kernel Mailing List, linux-acpi,
Andrew Morton
On Mar 31, 2007, at 02:36:08, Jeremy Fitzhardinge wrote:
> When I run 2.6.21-rc5 + Andi's x86 patches + paravirt_ops patches,
> I've been getting my machine shut down with critical thermal
> shutdown messages:
>
> Mar 30 23:19:03 localhost kernel: ACPI: Critical trip point
> Mar 30 23:19:03 localhost kernel: Critical temperature reached (128
> C), shutting down.
> Mar 30 23:19:03 localhost kernel: Critical temperature reached (128
> C), shutting down.
> Mar 30 23:19:03 localhost shutdown[19417]: shutting down for system
> halt
>
> and the machine does feel pretty hot. Interestingly, when the
> machine reboots, the fan spins up to a noticeably higher speed, so
> it seems that maybe something is getting fan speed control wrong.
Well, 128C is more than hot enough to boil water and well above the
thermal tolerances of most CPUs, so I would imagine that were your
CPU actually that hot it wouldn't be capable of printing the
"Critical temperature reached" messages, let alone properly rebooting.
Cheers,
Kyle Moffett
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-01 18:57 ` Kyle Moffett
@ 2007-04-01 21:13 ` Jeremy Fitzhardinge
2007-04-02 8:35 ` Rene Rebe
1 sibling, 0 replies; 19+ messages in thread
From: Jeremy Fitzhardinge @ 2007-04-01 21:13 UTC (permalink / raw)
To: Kyle Moffett
Cc: Andi Kleen, Brown, Len, Linux Kernel Mailing List, linux-acpi,
Andrew Morton
Kyle Moffett wrote:
> Well, 128C is more than hot enough to boil water and well above the
> thermal tolerances of most CPUs, so I would imagine that were your CPU
> actually that hot it wouldn't be capable of printing the "Critical
> temperature reached" messages, let alone properly rebooting.
Yes, its probably a bad reading, but its not complete absurd - chips can
operate up to ~100C, but they're definitely unhappy at that point. In
fact, I typically get 85-95 degrees from those sensors in normal
operation, but I have no idea whether that's a real measurement or not.
J
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-01 16:30 ` Pavel Machek
@ 2007-04-01 22:44 ` Henrique de Moraes Holschuh
0 siblings, 0 replies; 19+ messages in thread
From: Henrique de Moraes Holschuh @ 2007-04-01 22:44 UTC (permalink / raw)
To: Pavel Machek
Cc: Andi Kleen, Jeremy Fitzhardinge, Brown, Len,
Linux Kernel Mailing List, linux-acpi, Andrew Morton
On Sun, 01 Apr 2007, Pavel Machek wrote:
> Are you running lm_sensors?
lm-sensors can't confuse any recent thinkpad's thermal management. The i2c
buses that matter are all behind the EC, you have to ask the EC for data.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-01 16:32 ` Pavel Machek
@ 2007-04-01 22:46 ` Henrique de Moraes Holschuh
0 siblings, 0 replies; 19+ messages in thread
From: Henrique de Moraes Holschuh @ 2007-04-01 22:46 UTC (permalink / raw)
To: Pavel Machek
Cc: Jeremy Fitzhardinge, Alexey Starikovskiy,
Linux Kernel Mailing List, linux-acpi
On Sun, 01 Apr 2007, Pavel Machek wrote:
> ACPI is misdesigned, and lm_sensors can't cope with that.
Err, HOW exactly are you accessing the ThinkPad i2c buses directly? Or did
Lenovo change completely the hardware project of thinkpads in the X60?
Or did anyone add an lm-sensors that attach to the ACPI EC ports now?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-01 6:28 ` Jeremy Fitzhardinge
2007-04-01 14:53 ` Matthew Garrett
2007-04-01 16:32 ` Pavel Machek
@ 2007-04-01 23:19 ` Jeremy Fitzhardinge
2007-04-02 2:38 ` Henrique de Moraes Holschuh
2 siblings, 1 reply; 19+ messages in thread
From: Jeremy Fitzhardinge @ 2007-04-01 23:19 UTC (permalink / raw)
To: Jeremy Fitzhardinge
Cc: Alexey Starikovskiy, Linux Kernel Mailing List, linux-acpi, Ingo Molnar
Jeremy Fitzhardinge wrote:
> Alexey Starikovskiy wrote:
>
>> Could you try to unload or disable hardware sensors and check if it
>> helps?
>> CONFIG_I2C=m
>> CONFIG_I2C_ALGOBIT=m
>> CONFIG_I2C_ALGOPCA=m
>> CONFIG_I2C_I810=m
>> CONFIG_I2C_PIIX4=m
>> CONFIG_SENSORS_DS1337=m
>> CONFIG_SENSORS_DS1374=m
>> CONFIG_SENSORS_EEPROM=m
>> CONFIG_SENSORS_PCF8574=m
>> CONFIG_SENSORS_PCA9539=m
>> CONFIG_SENSORS_PCF8591=m
>> CONFIG_SENSORS_MAX6875=m
>>
>
> That seems to have helped. If I watch
> /proc/acpi/thermal_zone/THM?/temperature, it seems stable even under
> load. I didn't try watching the thermal_zones when these options were
> enabled, but I presume the temperature was not controlled for it to hit
> 128 degC.
Hm, perhaps I was too optimistic. I have lm_sensors disabled, and all
i2c options unconfigured in my kernel, but it still has temperature
control problems. Perhaps the ambient temperature was lower when I
reported success.
When I do a big compile, the temperature reported in
/proc/acpi/thermal_zone/THM0/temperature rapidly approaches 100C, and
when it goes over 100 it triggers the critical shutdown. When it shuts
down, it (mis-?)reports the temperature as 128C.
This seems to be real, and not a kernel artifact. If I reboot the same
kernel immediately, it boots up to the message "ACPI: Core revision
20070126" and then hangs. If I boot Windows immediately afterwards, it
reboots a short way into the boot process.
I've noticed one behavioral change with this kernel. On the older
kernels, the CPU frequency would sometimes drop to lowest speed,
apparently because of an ACPI thermal limiting event. This kernel
doesn't seem to drop speed. I seem to remember Ingo had a patch to
ignore the ACPI thermal limits in cpufreq; did that get merged?
J
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-01 23:19 ` Jeremy Fitzhardinge
@ 2007-04-02 2:38 ` Henrique de Moraes Holschuh
2007-04-02 4:53 ` Jeremy Fitzhardinge
0 siblings, 1 reply; 19+ messages in thread
From: Henrique de Moraes Holschuh @ 2007-04-02 2:38 UTC (permalink / raw)
To: Jeremy Fitzhardinge
Cc: Alexey Starikovskiy, Linux Kernel Mailing List, linux-acpi, Ingo Molnar
On Sun, 01 Apr 2007, Jeremy Fitzhardinge wrote:
> control problems. Perhaps the ambient temperature was lower when I
> reported success.
You can use ibm-acpi to properly track your thinkpad thermal sensors, load
it with the "experimental=1" parameter, and look at what gets exported at
/proc/acpi/ibm/thermal.
You can also use /proc/acpi/ibm/fan to check the fan's state. And use the
"level 7" /proc/acpi/ibm/fan command to set the emergency cooling level, and
"level disengaged" command to set the really badass fan cooling level (might
damage your hardware, we don't know if it is safe and IBM/Lenovo isn't
talking).
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-02 2:38 ` Henrique de Moraes Holschuh
@ 2007-04-02 4:53 ` Jeremy Fitzhardinge
2007-04-03 12:34 ` Henrique de Moraes Holschuh
0 siblings, 1 reply; 19+ messages in thread
From: Jeremy Fitzhardinge @ 2007-04-02 4:53 UTC (permalink / raw)
To: Henrique de Moraes Holschuh
Cc: Alexey Starikovskiy, Linux Kernel Mailing List, linux-acpi, Ingo Molnar
Henrique de Moraes Holschuh wrote:
> On Sun, 01 Apr 2007, Jeremy Fitzhardinge wrote:
>
>> control problems. Perhaps the ambient temperature was lower when I
>> reported success.
>>
>
> You can use ibm-acpi to properly track your thinkpad thermal sensors, load
> it with the "experimental=1" parameter, and look at what gets exported at
> /proc/acpi/ibm/thermal.
>
Interesting. The first number corresponds with the ACPI THM0
temperature, but I can't see anything corresponding to THM1. Is there
something that documents what all the temperatures are measuring in an
X60? Thinkwiki doesn't seem to have any info.
ezr:pts/1; cat /proc/acpi/ibm/thermal
temperatures: 72 55 -128 65 40 -128 35 -128 51 53 -128 -128 -128 -128
-128 -128
> You can also use /proc/acpi/ibm/fan to check the fan's state. And use the
> "level 7" /proc/acpi/ibm/fan command to set the emergency cooling level, and
> "level disengaged" command to set the really badass fan cooling level (might
> damage your hardware, we don't know if it is safe and IBM/Lenovo isn't
> talking).
>
It's set to auto. Presumably that means its tied into the temperature
sensors and will be able to keep the temp under control...
J
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-01 18:57 ` Kyle Moffett
2007-04-01 21:13 ` Jeremy Fitzhardinge
@ 2007-04-02 8:35 ` Rene Rebe
2007-04-08 19:09 ` Valdis.Kletnieks
1 sibling, 1 reply; 19+ messages in thread
From: Rene Rebe @ 2007-04-02 8:35 UTC (permalink / raw)
To: Kyle Moffett
Cc: Jeremy Fitzhardinge, Andi Kleen, Brown, Len,
Linux Kernel Mailing List, linux-acpi, Andrew Morton
On Sunday 01 April 2007 20:57:57 Kyle Moffett wrote:
> On Mar 31, 2007, at 02:36:08, Jeremy Fitzhardinge wrote:
> > When I run 2.6.21-rc5 + Andi's x86 patches + paravirt_ops patches,
> > I've been getting my machine shut down with critical thermal
> > shutdown messages:
> >
> > Mar 30 23:19:03 localhost kernel: ACPI: Critical trip point
> > Mar 30 23:19:03 localhost kernel: Critical temperature reached (128
> > C), shutting down.
> > Mar 30 23:19:03 localhost kernel: Critical temperature reached (128
> > C), shutting down.
> > Mar 30 23:19:03 localhost shutdown[19417]: shutting down for system
> > halt
> >
> > and the machine does feel pretty hot. Interestingly, when the
> > machine reboots, the fan spins up to a noticeably higher speed, so
> > it seems that maybe something is getting fan speed control wrong.
>
> Well, 128C is more than hot enough to boil water and well above the
> thermal tolerances of most CPUs, so I would imagine that were your
> CPU actually that hot it wouldn't be capable of printing the
> "Critical temperature reached" messages, let alone properly rebooting.
IIRC a MSI Megabook S270 (I formerly owned) BIOS notifies this
"Critical temperature reached (128C)" when the battery run empty
when the OS did no action due to battery low indications. I guess
the BIOS people thought this is a good last resort to let the OS
really shutdown before the box just turns off.
Yours,
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
+49 (0)30 / 255 897 45
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-02 4:53 ` Jeremy Fitzhardinge
@ 2007-04-03 12:34 ` Henrique de Moraes Holschuh
2007-04-03 18:35 ` Jeremy Fitzhardinge
0 siblings, 1 reply; 19+ messages in thread
From: Henrique de Moraes Holschuh @ 2007-04-03 12:34 UTC (permalink / raw)
To: Jeremy Fitzhardinge
Cc: Alexey Starikovskiy, Linux Kernel Mailing List, linux-acpi, Ingo Molnar
On Sun, 01 Apr 2007, Jeremy Fitzhardinge wrote:
> > You can use ibm-acpi to properly track your thinkpad thermal sensors, load
> > it with the "experimental=1" parameter, and look at what gets exported at
> > /proc/acpi/ibm/thermal.
>
> Interesting. The first number corresponds with the ACPI THM0
> temperature, but I can't see anything corresponding to THM1. Is there
> something that documents what all the temperatures are measuring in an
> X60? Thinkwiki doesn't seem to have any info.
Well, send me the DSDT and dmidecode output (mask off the UUID and serial
numbers), and I will be able to say more.
> ezr:pts/1; cat /proc/acpi/ibm/thermal
> temperatures: 72 55 -128 65 40 -128 35 -128 51 53 -128 -128 -128 -128
> -128 -128
This is a highly unusual output for thinkpads, but might be the expected one
for your X60, the X-series has always been a bit weird. I'd higly suggest
asking for X60 thermal data from other X60 owners on the linux-thinkpad ML.
Make sure to state your X60 model number, and to request that everyone does
the same.
> > You can also use /proc/acpi/ibm/fan to check the fan's state. And use the
>
> It's set to auto. Presumably that means its tied into the temperature
> sensors and will be able to keep the temp under control...
Yes, if all sensors are working fine. That said, people override the EC fan
control all the time, because it seems not to be doing what people want.
Thinkwiki has more on this, and you want to set your fan to level 7 when
doing CPU-intensive work for now, since you are experiencing some sort of
trouble anyway...
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-03 12:34 ` Henrique de Moraes Holschuh
@ 2007-04-03 18:35 ` Jeremy Fitzhardinge
2007-04-03 21:25 ` RusH
2007-04-04 3:46 ` Henrique de Moraes Holschuh
0 siblings, 2 replies; 19+ messages in thread
From: Jeremy Fitzhardinge @ 2007-04-03 18:35 UTC (permalink / raw)
To: Henrique de Moraes Holschuh
Cc: Alexey Starikovskiy, Linux Kernel Mailing List, linux-acpi, Ingo Molnar
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
Henrique de Moraes Holschuh wrote:
> Well, send me the DSDT and dmidecode output (mask off the UUID and serial
> numbers), and I will be able to say more.
>
Attached. Is there some tool for decoding the DSDT?
>> ezr:pts/1; cat /proc/acpi/ibm/thermal
>> temperatures: 72 55 -128 65 40 -128 35 -128 51 53 -128 -128 -128 -128
>> -128 -128
>>
>
> This is a highly unusual output for thinkpads, but might be the expected one
> for your X60, the X-series has always been a bit weird. I'd higly suggest
> asking for X60 thermal data from other X60 owners on the linux-thinkpad ML.
> Make sure to state your X60 model number, and to request that everyone does
> the same.
>
How would you expect it to look? I did some non-conclusive tests under
Windows, and I'm beginning to get the feeling that there is actually a
cooling problem with the hardware.
> Yes, if all sensors are working fine. That said, people override the EC fan
> control all the time, because it seems not to be doing what people want.
> Thinkwiki has more on this, and you want to set your fan to level 7 when
> doing CPU-intensive work for now, since you are experiencing some sort of
> trouble anyway...
>
It doesn't seem to help. When its failing to control cooling (temp
creeps towards 100C while under load), its going at ~3700RPM, which is
about what level 7 does.
What's a typical max RPM? I'm getting the impression that there's
either a thermal coupling problem between the CPU and its heatsink, or a
fan problem.
J
[-- Attachment #2: dmi.txt --]
[-- Type: text/plain, Size: 13254 bytes --]
# dmidecode 2.7
SMBIOS 2.4 present.
67 structures occupying 2239 bytes.
Table at 0x000E0010.
Handle 0x0000, DMI type 0, 24 bytes.
BIOS Information
Vendor: LENOVO
Version: 7BETC8WW (2.09 )
Release Date: 03/14/2007
Address: 0xE0000
Runtime Size: 128 kB
ROM Size: 2048 kB
Characteristics:
PCI is supported
PC Card (PCMCIA) is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 2.9
Firmware Revision: 1.16
Handle 0x0001, DMI type 1, 27 bytes.
System Information
Manufacturer: LENOVO
Product Name: 170997U
Version: ThinkPad X60
Serial Number: XXXX
UUID: XXXX
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: ThinkPad X60
Handle 0x0002, DMI type 2, 8 bytes.
Base Board Information
Manufacturer: LENOVO
Product Name: 170997U
Version: Not Available
Serial Number: XXXX
Handle 0x0003, DMI type 3, 13 bytes.
Chassis Information
Manufacturer: LENOVO
Type: Notebook
Lock: Not Present
Version: Not Available
Serial Number: Not Available
Asset Tag: No Asset Information
Boot-up State: Unknown
Power Supply State: Unknown
Thermal State: Unknown
Security Status: Unknown
Handle 0x0004, DMI type 126, 13 bytes.
Inactive
Handle 0x0005, DMI type 126, 13 bytes.
Inactive
Handle 0x0006, DMI type 4, 35 bytes.
Processor Information
Socket Designation: None
Type: Central Processor
Family: Other
Manufacturer: GenuineIntel
ID: E8 06 00 00 FF FB E9 BF
Version: Genuine Intel(R) CPU
Voltage: 1.3 V
External Clock: 167 MHz
Max Speed: 1833 MHz
Current Speed: 1833 MHz
Status: Populated, Enabled
Upgrade: None
L1 Cache Handle: 0x000A
L2 Cache Handle: 0x000C
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x0007, DMI type 5, 20 bytes.
Memory Controller Information
Error Detecting Method: None
Error Correcting Capabilities:
None
Supported Interleave: One-way Interleave
Current Interleave: One-way Interleave
Maximum Memory Module Size: 2048 MB
Maximum Total Memory Size: 4096 MB
Supported Speeds:
Other
Supported Memory Types:
DIMM
SDRAM
Memory Module Voltage: 2.9 V
Associated Memory Slots: 2
0x0008
0x0009
Enabled Error Correcting Capabilities:
Unknown
Handle 0x0008, DMI type 6, 12 bytes.
Memory Module Information
Socket Designation: DIMM Slot 1
Bank Connections: 0 3
Current Speed: Unknown
Type: DIMM SDRAM
Installed Size: 1024 MB (Double-bank Connection)
Enabled Size: 1024 MB (Double-bank Connection)
Error Status: OK
Handle 0x0009, DMI type 6, 12 bytes.
Memory Module Information
Socket Designation: DIMM Slot 2
Bank Connections: 4 7
Current Speed: Unknown
Type: DIMM SDRAM
Installed Size: 1024 MB (Double-bank Connection)
Enabled Size: 1024 MB (Double-bank Connection)
Error Status: OK
Handle 0x000A, DMI type 7, 19 bytes.
Cache Information
Socket Designation: Internal L1 Cache
Configuration: Enabled, Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 64 KB
Maximum Size: 64 KB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Instruction
Associativity: 8-way Set-associative
Handle 0x000B, DMI type 7, 19 bytes.
Cache Information
Socket Designation: Internal L1 Cache
Configuration: Enabled, Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 64 KB
Maximum Size: 64 KB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Data
Associativity: 8-way Set-associative
Handle 0x000C, DMI type 7, 19 bytes.
Cache Information
Socket Designation: Internal L2 Cache
Configuration: Enabled, Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 2048 KB
Maximum Size: 2048 KB
Supported SRAM Types:
Burst
Installed SRAM Type: Burst
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 8-way Set-associative
Handle 0x000D, DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: Not Available
Internal Connector Type: None
External Reference Designator: Infrared
External Connector Type: Infrared
Port Type: Other
Handle 0x000E, DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: Not Available
Internal Connector Type: None
External Reference Designator: External Monitor
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x000F, DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: Not Available
Internal Connector Type: None
External Reference Designator: Microphone Jack
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0010, DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: Not Available
Internal Connector Type: None
External Reference Designator: Headphone Jack
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0011, DMI type 126, 9 bytes.
Inactive
Handle 0x0012, DMI type 126, 9 bytes.
Inactive
Handle 0x0013, DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: Not Available
Internal Connector Type: None
External Reference Designator: Modem
External Connector Type: RJ-11
Port Type: Modem Port
Handle 0x0014, DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: Not Available
Internal Connector Type: None
External Reference Designator: Ethernet
External Connector Type: RJ-45
Port Type: Network Port
Handle 0x0015, DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: Not Available
Internal Connector Type: None
External Reference Designator: USB 1
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0016, DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: Not Available
Internal Connector Type: None
External Reference Designator: USB 2
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0017, DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: Not Available
Internal Connector Type: None
External Reference Designator: USB 3
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0018, DMI type 126, 9 bytes.
Inactive
Handle 0x0019, DMI type 126, 9 bytes.
Inactive
Handle 0x001A, DMI type 126, 9 bytes.
Inactive
Handle 0x001B, DMI type 126, 9 bytes.
Inactive
Handle 0x001C, DMI type 126, 9 bytes.
Inactive
Handle 0x001D, DMI type 126, 9 bytes.
Inactive
Handle 0x001E, DMI type 126, 9 bytes.
Inactive
Handle 0x001F, DMI type 126, 9 bytes.
Inactive
Handle 0x0020, DMI type 9, 13 bytes.
System Slot Information
Designation: ExpressCard Slot 1
Type: x1 PCI Express
Current Usage: Available
Length: Other
Characteristics:
Hot-plug devices are supported
Handle 0x0021, DMI type 9, 13 bytes.
System Slot Information
Designation: CardBus Slot 1
Type: 32-bit PC Card (PCMCIA)
Current Usage: Available
Length: Other
ID: Adapter 1, Socket 0
Characteristics:
5.0 V is provided
3.3 V is provided
PC Card-16 is supported
Cardbus is supported
Zoom Video is supported
Modem ring resume is supported
PME signal is supported
Hot-plug devices are supported
Handle 0x0022, DMI type 126, 13 bytes.
Inactive
Handle 0x0023, DMI type 126, 13 bytes.
Inactive
Handle 0x0024, DMI type 126, 13 bytes.
Inactive
Handle 0x0025, DMI type 10, 6 bytes.
On Board Device Information
Type: Other
Status: Enabled
Description: IBM Embedded Security hardware
Handle 0x0026, DMI type 11, 5 bytes.
OEM Strings
String 1: IBM ThinkPad Embedded Controller -[7BHT37WW-1.10 ]-
Handle 0x0027, DMI type 13, 22 bytes.
BIOS Language Information
Installable Languages: 1
enUS
Currently Installed Language: enUS
Handle 0x0028, DMI type 15, 25 bytes.
System Event Log
Area Length: 0 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions
Access Address: 0x0000
Status: Invalid, Not Full
Change Token: 0x00000000
Header Format: Type 1
Supported Log Type Descriptors: 1
Descriptor 1: POST error
Data Format 1: POST results bitmap
Handle 0x0029, DMI type 16, 15 bytes.
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 2 GB
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x002A, DMI type 17, 27 bytes.
Memory Device
Array Handle: 0x0029
Error Information Handle: No Error
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: SODIMM
Set: None
Locator: DIMM 1
Bank Locator: Bank 0/1
Type: DDR2
Type Detail: Synchronous
Speed: Unknown
Manufacturer: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x002B, DMI type 17, 27 bytes.
Memory Device
Array Handle: 0x0029
Error Information Handle: No Error
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: SODIMM
Set: None
Locator: DIMM 2
Bank Locator: Bank 2/3
Type: DDR2
Type Detail: Synchronous
Speed: Unknown
Manufacturer: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x002C, DMI type 18, 23 bytes.
32-bit Memory Error Information
Type: OK
Granularity: Unknown
Operation: Unknown
Vendor Syndrome: Unknown
Memory Array Address: Unknown
Device Address: Unknown
Resolution: Unknown
Handle 0x002D, DMI type 19, 15 bytes.
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Array Handle: 0x0029
Partition Width: 0
Handle 0x002E, DMI type 20, 19 bytes.
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0003FFFFFFF
Range Size: 1 GB
Physical Device Handle: 0x002A
Memory Array Mapped Address Handle: 0x002D
Partition Row Position: 1
Handle 0x002F, DMI type 20, 19 bytes.
Memory Device Mapped Address
Starting Address: 0x00040000000
Ending Address: 0x0007FFFFFFF
Range Size: 1 GB
Physical Device Handle: 0x002B
Memory Array Mapped Address Handle: 0x002D
Partition Row Position: 1
Handle 0x0030, DMI type 21, 7 bytes.
Built-in Pointing Device
Type: Track Point
Interface: PS/2
Buttons: 3
Handle 0x0031, DMI type 24, 5 bytes.
Hardware Security
Power-On Password Status: Disabled
Keyboard Password Status: Disabled
Administrator Password Status: Disabled
Front Panel Reset Status: Unknown
Handle 0x0032, DMI type 32, 11 bytes.
System Boot Information
Status: No errors detected
Handle 0x0033, DMI type 131, 17 bytes.
OEM-specific Type
Header and Data:
83 11 33 00 01 02 03 FF FF 1F 00 00 00 00 00 02
00
Strings:
BOOTINF 20h
BOOTDEV 21h
KEYPTRS 23h
Handle 0x0034, DMI type 131, 11 bytes.
OEM-specific Type
Header and Data:
83 0B 34 00 00 00 E8 FF C5 01 01
Strings:
IBM System Metrics
Handle 0x0035, DMI type 131, 22 bytes.
OEM-specific Type
Header and Data:
83 16 35 00 01 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 01
Strings:
TVT-Enablement
Handle 0x0036, DMI type 132, 7 bytes.
OEM-specific Type
Header and Data:
84 07 36 00 02 D8 36
Handle 0x0037, DMI type 133, 5 bytes.
OEM-specific Type
Header and Data:
85 05 37 00 01
Strings:
KHOIHGIUCCHHII
Handle 0x0038, DMI type 133, 17 bytes.
OEM-specific Type
Header and Data:
85 11 38 00 30 30 2E 35 00 60 6F 7F 00 00 00 00
01
Strings:
Audit Boot History
Handle 0x0039, DMI type 134, 13 bytes.
OEM-specific Type
Header and Data:
86 0D 39 00 21 05 06 20 00 00 00 00 00
Handle 0x003A, DMI type 134, 16 bytes.
OEM-specific Type
Header and Data:
86 10 3A 00 00 41 54 4D 4C 01 01 00 00 03 01 02
Strings:
TPM INFO
System Reserved
Handle 0x003B, DMI type 135, 13 bytes.
OEM-specific Type
Header and Data:
87 0D 3B 00 54 50 07 00 01 00 00 00 00
Handle 0x003C, DMI type 135, 18 bytes.
OEM-specific Type
Header and Data:
87 12 3C 00 54 50 07 01 01 A5 01 00 00 00 00 00
00 00
Handle 0x003D, DMI type 135, 35 bytes.
OEM-specific Type
Header and Data:
87 23 3D 00 54 50 07 02 42 41 59 20 49 2F 4F 20
01 00 02 00 00 0B 00 D0 18 C6 18 02 00 0E 00 F0
01 F6 03
Handle 0x003E, DMI type 136, 6 bytes.
OEM-specific Type
Header and Data:
88 06 3E 00 5A 5A
Handle 0x003F, DMI type 137, 26 bytes.
OEM-specific Type
Header and Data:
89 1A 3F 00 0A 01 00 01 00 00 50 57 4D 53 20 49
6E 66 6F 72 6D 61 74 69 6F 6E
Handle 0x0040, DMI type 138, 40 bytes.
OEM-specific Type
Header and Data:
8A 28 40 00 14 01 01 01 07 01 01 0C 01 01 0C 01
01 0C 00 00 42 49 4F 53 20 50 61 73 73 77 6F 72
64 20 46 6F 72 6D 61 74
Handle 0x0041, DMI type 139, 37 bytes.
OEM-specific Type
Header and Data:
8B 25 41 00 11 01 0A 00 00 00 00 00 00 00 00 00
00 50 57 4D 53 20 4B 65 79 20 49 6E 66 6F 72 6D
61 74 69 6F 6E
Handle 0x0042, DMI type 127, 4 bytes.
End Of Table
[-- Attachment #3: dsdt.bin --]
[-- Type: application/octet-stream, Size: 52982 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-03 18:35 ` Jeremy Fitzhardinge
@ 2007-04-03 21:25 ` RusH
2007-04-04 3:46 ` Henrique de Moraes Holschuh
1 sibling, 0 replies; 19+ messages in thread
From: RusH @ 2007-04-03 21:25 UTC (permalink / raw)
To: Jeremy Fitzhardinge
Cc: Henrique de Moraes Holschuh, Alexey Starikovskiy,
Linux Kernel Mailing List, linux-acpi, Ingo Molnar
On 4/3/07, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Attached. Is there some tool for decoding the DSDT?
iasl
http://www.intel.com/technology/iapc/acpi/downloads.htm
http://www.intel.com/technology/iapc/acpi/license2.htm
--
Who logs in to gdm? Not I, said the duck.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-03 18:35 ` Jeremy Fitzhardinge
2007-04-03 21:25 ` RusH
@ 2007-04-04 3:46 ` Henrique de Moraes Holschuh
1 sibling, 0 replies; 19+ messages in thread
From: Henrique de Moraes Holschuh @ 2007-04-04 3:46 UTC (permalink / raw)
To: Jeremy Fitzhardinge
Cc: Alexey Starikovskiy, Linux Kernel Mailing List, linux-acpi, Ingo Molnar
On Tue, 03 Apr 2007, Jeremy Fitzhardinge wrote:
> Attached. Is there some tool for decoding the DSDT?
iasl. The documentation is the ACPI Specification.
> >> ezr:pts/1; cat /proc/acpi/ibm/thermal
> >> temperatures: 72 55 -128 65 40 -128 35 -128 51 53 -128 -128 -128 -128
> >> -128 -128
> >
> > This is a highly unusual output for thinkpads, but might be the expected one
> > for your X60, the X-series has always been a bit weird. I'd higly suggest
>
> How would you expect it to look? I did some non-conclusive tests under
I would not expect a -128 on the third position. The other two -128 are
expected, as they are the thermal sensors for the secondary battery. There
is also one less sensor than I'd expect.
> Windows, and I'm beginning to get the feeling that there is actually a
> cooling problem with the hardware.
This must be at least the third complain I come across of a X60 which boils
the CPU. The standard fix from Lenovo is a planar card swap (motherboard
swap). Since this *does* mean they replace the thermal compounds, and a
full reassembly of the heat pipes, it might be that just fixing the thermal
coupling between cooling assembly and the CPU might do it.
> It doesn't seem to help. When its failing to control cooling (temp
> creeps towards 100C while under load), its going at ~3700RPM, which is
> about what level 7 does.
Well, at least the EC is not misbehaving, then.
> What's a typical max RPM? I'm getting the impression that there's
More than 4000rpm, in disengaged mode.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
2007-04-02 8:35 ` Rene Rebe
@ 2007-04-08 19:09 ` Valdis.Kletnieks
0 siblings, 0 replies; 19+ messages in thread
From: Valdis.Kletnieks @ 2007-04-08 19:09 UTC (permalink / raw)
To: Rene Rebe
Cc: Kyle Moffett, Jeremy Fitzhardinge, Andi Kleen, Brown, Len,
Linux Kernel Mailing List, linux-acpi, Andrew Morton
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Mon, 02 Apr 2007 10:35:40 +0200, Rene Rebe said:
(Sorry for the late reply..)
> IIRC a MSI Megabook S270 (I formerly owned) BIOS notifies this
> "Critical temperature reached (128C)" when the battery run empty
> when the OS did no action due to battery low indications. I guess
> the BIOS people thought this is a good last resort to let the OS
> really shutdown before the box just turns off.
It's not just MSI - I recently managed to put a Dell Latitude D820 into its bag
while still running, where it babbled to itself running on the warm side for
several hours. When I finally did get it out, it *was* quite hot to the touch,
but I was amazed that it managed to run the battery down to somewhere under 4%
(which took some 4 or 5 hours) and then throw the thermal check that made it
shut down - quite the coincidence indeed.
However, "ran warm but tolerable and then used the thermal to shut down when
the battery failed" matches the symptoms much better....
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2007-04-08 19:11 UTC | newest]
Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-03-31 6:36 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns Jeremy Fitzhardinge
2007-03-31 9:31 ` Andi Kleen
2007-04-01 16:30 ` Pavel Machek
2007-04-01 22:44 ` Henrique de Moraes Holschuh
[not found] ` <8f8ff01d0703310033y74421cfcl747ece1be003471@mail.gmail.com>
2007-04-01 6:28 ` Jeremy Fitzhardinge
2007-04-01 14:53 ` Matthew Garrett
2007-04-01 16:32 ` Pavel Machek
2007-04-01 22:46 ` Henrique de Moraes Holschuh
2007-04-01 23:19 ` Jeremy Fitzhardinge
2007-04-02 2:38 ` Henrique de Moraes Holschuh
2007-04-02 4:53 ` Jeremy Fitzhardinge
2007-04-03 12:34 ` Henrique de Moraes Holschuh
2007-04-03 18:35 ` Jeremy Fitzhardinge
2007-04-03 21:25 ` RusH
2007-04-04 3:46 ` Henrique de Moraes Holschuh
2007-04-01 18:57 ` Kyle Moffett
2007-04-01 21:13 ` Jeremy Fitzhardinge
2007-04-02 8:35 ` Rene Rebe
2007-04-08 19:09 ` Valdis.Kletnieks
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).