Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
Hello! I am very happy having found this bug report as it is possible that the NMI watchdog mechanism has given me serious headaches since Debian kernel 2.6.38 was released! I cannot tell it definitely yet as it is an intermittent error in my case which may take up to a week to appear once, and I disabled the NMI watchdog mechanism by adding nowatchdog not until a few hours ago when I came across this bug report. A short summary of my problem: - among several uniprocessor systems with Debian and Ubuntu, I am running several older multiprocessor servers (IBM Netfinity 5000 (Dual-P3), IBM Netfinity 7000 M10 (Quad-P3-Xeon) and IBM xSeries 232 (Dual P3-Tualatin)) with Debian (using testing as rolling release after a long time with lenny) - the systems were running rock-solid up to and including the Debian-packaged kernel 2.6.32 - when Debian-packaged kernel 2.6.38 came out, my problem started and appeared mainly on the Netfinity 5000 (but less often also on the other systems): after running continuously for one to eight days, the system suddenly locked up hard, in most cases it was just idle when this happened - this lockup was a classic livelock which can be diagnosed nicely on these IBM machines as they have activity LEDs for each CPU which glowed with identical brightness and without any modulation, so both CPUs were switching between each other with short cycles - when comparing the basic system data and properties, I noticed a difference between kernel 2.6.32 and 2.6.38: the latter caused a continuously rising NMI count on each CPU which could not be seen with 2.6.32! Today I know where these NMIs are coming from: it is the watchdog mechanism also causing your laptop problem - I hoped that the problem might disappear with kernel 3.4 as there were a few discussions on LKML about several livelocks/deadlocks related to timers and the like (the config change concerning the lockup detector which got enabled from 2.6.32 to 2.6.38 remained unnoticed for me) - as you see it on the laptop, this lockup NEVER allows to get any message out via the debugging mechanisms, not even by attaching a serial cable and logging the console output on a second machine - now using kernel 3.4.2, the problem still exists, but has changed a bit in its consequences - instead of a livelock, it is a deadlock in most cases and activity stays on a single CPU, sometimes even causing a reboot instead of staying locked up - on a German forum I described the problem, but nobody could point me to this lockup-detector change in the kernel config though I posted this significant change from no NMIs to continuous NMIs. Here we see again how bad the documentation of open-source projects sometimes is cared about... even when configuring a kernel, the config help says that the nmi watchdog had to be enabled consciously by a boot parameter - in fact it seems to be activated by default as soon as SMP code is loaded and/or an APIC is detected (but though the presence of an APIC, I have not seen those NMIs on my uniprocessor P3 machines yet). Here is a link to my description on the German debianforum: http://debianforum.de/forum/viewtopic.php?f=33t=134210 I would like to report the bug to http://bugzilla.kernel.org if it has not yet been done by someone else. Therefore it would be great if you could give me a short note if you have reported it already. Basically I think this mechanism has its bugs and/or wrong assumptions on some machines and should undergo a critical review. I'm wondering if there are more people in the world getting set up by strange lockups of their machines which are wrongly diagnosed as hardware errors etc. Hope to read from you soon! Thanks and best regards, Hans-Juergen -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fe23d88.4060...@gmx.net
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
Hi Hans-Juergen, Hans-Juergen Mauser wrote: I am very happy having found this bug report as it is possible that Please file a separate bug. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120620214521.GI6142@burratino
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
Ben Hutchings wrote: On Wed, Aug 31, 2011 at 11:08:30PM +0200, Thibault Manlay wrote: Issue comes from CONFIG_LOCKUP_DETECTOR=y (issue disappears when unsetting it). But why would this option/feature locks-up the system? It doesn't. It just tells you when a process is stuck for a long time. If the process eventually recovers, and this option is disabled, then you might not notice. That's the theory, but if Thibault has to use the power button to reboot to recover, then something's going wrong, no? Anyway, it seems it's time to take this upstream. Thibault, could you send a summary of findings so far (i.e., what the state is like when closing the lid, problem only shows up with CONFIG_LOCKUP_DETECTOR=y, the nolapic kernel parameter works around it, whatever logs it was possible to get of what happens until the lid closes, and an acpidump) to the linux-a...@vger.kernel.org list (no subscription needed, since the convention is to always reply-to-all), cc-ing this bug log? Sorry for the trouble, and good luck. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110912193656.GA30915@elie
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
On 12/09/11 21:36, Jonathan Nieder wrote: That's the theory, but if Thibault has to use the power button to reboot to recover, then something's going wrong, no? Anyway, it seems it's time to take this upstream. Thibault, could you send a summary of findings so far (i.e., what the state is like when closing the lid, problem only shows up with CONFIG_LOCKUP_DETECTOR=y, the nolapic kernel parameter works around it, whatever logs it was possible to get of what happens until the lid closes, and an acpidump) to the linux-a...@vger.kernel.org list (no subscription needed, since the convention is to always reply-to-all), cc-ing this bug log? Sorry for the trouble, and good luck. Hello, I tried to get a kernel dump with kdump/kexec to have something I could work on, but no success. The kernel hangs and doesn't reboot on the crash kernel. Disabling SMP solves the problem too (it is required for kdump, but SMP can be enabled if you tell kdump to use one cpu), I feel a little bit discouraged. Since I can't find any pertinent similar problem (they are either too old or with no answer, or both) I begin to believe this is a hardware problem on my laptop. I'll try to patch the BIOS someday. Fun fact : closing lid hangs the system, but after I have done a single suspend-to-ram, I can close the lid as much as I want without getting the system to hang... Thanks, -- Thibault Manlay signature.asc Description: OpenPGP digital signature
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
Thibault Manlay wrote: Since I can't find any pertinent similar problem (they are either too old or with no answer, or both) I begin to believe this is a hardware problem on my laptop. I'll try to patch the BIOS someday. Fun fact : closing lid hangs the system, but after I have done a single suspend-to-ram, I can close the lid as much as I want without getting the system to hang... Neat. Yes, it's probably a BIOS bug, but with acpidump output from before and after suspending, the people at linux-acpi@vger might be able to help. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110912202545.ga2...@elie.gateway.2wire.net
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
On 29/08/11 04:44, Jonathan Nieder wrote: Nice. Have you found which item in the .config caused it? Found it. Issue comes from CONFIG_LOCKUP_DETECTOR=y (issue disappears when unsetting it). But why would this option/feature locks-up the system? -- Thibault Manlay signature.asc Description: OpenPGP digital signature
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
On Wed, Aug 31, 2011 at 11:08:30PM +0200, Thibault Manlay wrote: On 29/08/11 04:44, Jonathan Nieder wrote: Nice. Have you found which item in the .config caused it? Found it. Issue comes from CONFIG_LOCKUP_DETECTOR=y (issue disappears when unsetting it). But why would this option/feature locks-up the system? It doesn't. It just tells you when a process is stuck for a long time. If the process eventually recovers, and this option is disabled, then you might not notice. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110831223116.gd2...@decadent.org.uk
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
On 29/08/11 04:44, Jonathan Nieder wrote: Ah, that must have been painful. I should have included confirming that v2.6.36-rc6 is broken in the list of steps; sorry. :/ Np Nice. Have you found which item in the .config caused it? No, not yet. I should report back this week or next week. -- Thibault Manlay signature.asc Description: OpenPGP digital signature
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
Thibault Manlay wrote: Ok, finished bisecting v2.6.35 to v2.6.36-rc6 and found nothing. Ah, that must have been painful. I should have included confirming that v2.6.36-rc6 is broken in the list of steps; sorry. :/ [...] - 2.6.36-rc6 (git) + minimal configuration is ok; - 2.6.36-rc6 (git) + Debian 2.6.36-rc5-686-bigmem config is ok; - 2.6.36-rc6 (git) + Debian 2.6.36-rc6-686-bigmem config is crashing when closing lid. Nice. Have you found which item in the .config caused it? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110829024430.ga18...@elie.gateway.2wire.net
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
Thibault Manlay wrote: [...] I will do this sometime tomorrow but I think this may take a while :-) Thanks! I have a friend with the same hardware as me, although he is running stable I think it would be pertinent trying a recent kernel on his laptop even if I'm pretty sure of the result. Btw, would a debug of APIC/LAPIC informations at boot be useful here? (kernel parameters apic=debug show_lapic=all) In that direction, the most useful things might be: 1. Report this upstream at http://bugzilla.kernel.org/, product ACPI and let us know the bug number so we can move to there. :) 2. Run acpidump and attach its output to the upstream bug. 3. Enable CONFIG_ACPI_DEBUG (make nconfig → Power Management and ACPI options → ACPI Support → Debug Statements) and run something like echo _LID /sys/module/acpi/parameters/trace_method_name echo 0x /sys/module/acpi/parameters/trace_debug_layer echo 0x /sys/module/acpi/parameters/trace_debug_level echo 1 /sys/module/acpi/parameters/trace_state grep . /proc/acpi/button/lid/LID*/state (see Documentation/acpi/method-tracing.txt for details). -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110826154122.gd2...@elie.gateway.2wire.net
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
On 26/08/11 17:41, Jonathan Nieder wrote: Thanks! Ok, finished bisecting v2.6.35 to v2.6.36-rc6 and found nothing. After all maybe it is not a bug in the kernel code. This may come from the kernel configuration then. Well, I narrowed the search space : issue comes between linux-image-2.6.36-rc5-686-bigmem (2.6.36~rc5-1~experimental.1) (which works) and linux-image-2.6.36-rc6-686-bigmem (2.6.36~rc6-1~experimental.1) (which doesn't work). I compiled rc6 from source with Debian package kernel configuration and got it crashing. I join a diff file between 2.6.36-rc5 and rc6, but I did not find anything relevant. Using the rc5 kernel configuration from Debian experimental package for use with source kernel (checkout on v2.6.36-rc6) produces no crash. I suppose something's wrong in kernel configuration. So to sum up: - 2.6.36-rc6 (git) + minimal configuration is ok; - 2.6.36-rc6 (git) + Debian 2.6.36-rc5-686-bigmem config is ok; - 2.6.36-rc6 (git) + Debian 2.6.36-rc6-686-bigmem config is crashing when closing lid. I'll look around in that direction.. Thanks anyway :) -- Thibault Manlay --- /boot/config-2.6.36-rc5-686-bigmem 2010-09-25 18:16:20.0 +0200 +++ /boot/config-2.6.36-rc6-686-bigmem 2010-10-04 13:52:52.0 +0200 @@ -1,7 +1,7 @@ # # Automatically generated make config: don't edit -# Linux kernel version: 2.6.36-rc5 -# Sat Sep 25 13:43:12 2010 +# Linux kernel version: 2.6.36-rc6 +# Mon Oct 4 09:18:53 2010 # # CONFIG_64BIT is not set CONFIG_X86_32=y @@ -142,7 +142,7 @@ CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y -CONFIG_KALLSYMS_ALL=y +# CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y @@ -747,14 +747,14 @@ # # Xtables targets # -# CONFIG_NETFILTER_XT_TARGET_CHECKSUM is not set +CONFIG_NETFILTER_XT_TARGET_CHECKSUM=m CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m CONFIG_NETFILTER_XT_TARGET_CONNMARK=m CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m CONFIG_NETFILTER_XT_TARGET_CT=m CONFIG_NETFILTER_XT_TARGET_DSCP=m CONFIG_NETFILTER_XT_TARGET_HL=m -# CONFIG_NETFILTER_XT_TARGET_IDLETIMER is not set +CONFIG_NETFILTER_XT_TARGET_IDLETIMER=m CONFIG_NETFILTER_XT_TARGET_LED=m CONFIG_NETFILTER_XT_TARGET_MARK=m CONFIG_NETFILTER_XT_TARGET_NFLOG=m @@ -777,7 +777,7 @@ CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m CONFIG_NETFILTER_XT_MATCH_CONNMARK=m CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m -# CONFIG_NETFILTER_XT_MATCH_CPU is not set +CONFIG_NETFILTER_XT_MATCH_CPU=m CONFIG_NETFILTER_XT_MATCH_DCCP=m CONFIG_NETFILTER_XT_MATCH_DSCP=m CONFIG_NETFILTER_XT_MATCH_ESP=m @@ -785,7 +785,7 @@ CONFIG_NETFILTER_XT_MATCH_HELPER=m CONFIG_NETFILTER_XT_MATCH_HL=m CONFIG_NETFILTER_XT_MATCH_IPRANGE=m -# CONFIG_NETFILTER_XT_MATCH_IPVS is not set +CONFIG_NETFILTER_XT_MATCH_IPVS=m CONFIG_NETFILTER_XT_MATCH_LENGTH=m CONFIG_NETFILTER_XT_MATCH_LIMIT=m CONFIG_NETFILTER_XT_MATCH_MAC=m @@ -1120,7 +1120,7 @@ # CAN USB interfaces # CONFIG_CAN_EMS_USB=m -# CONFIG_CAN_ESD_USB2 is not set +CONFIG_CAN_ESD_USB2=m # CONFIG_CAN_DEBUG_DEVICES is not set CONFIG_IRDA=m @@ -1198,7 +1198,7 @@ CONFIG_BT_HCIUART=m CONFIG_BT_HCIUART_H4=y CONFIG_BT_HCIUART_BCSP=y -# CONFIG_BT_HCIUART_ATH3K is not set +CONFIG_BT_HCIUART_ATH3K=y CONFIG_BT_HCIUART_LL=y CONFIG_BT_HCIBCM203X=m CONFIG_BT_HCIBPA10X=m @@ -1504,7 +1504,7 @@ # CONFIG_BLK_DEV_HD is not set CONFIG_MISC_DEVICES=y CONFIG_AD525X_DPOT=m -# CONFIG_AD525X_DPOT_I2C is not set +CONFIG_AD525X_DPOT_I2C=m # CONFIG_AD525X_DPOT_SPI is not set CONFIG_IBM_ASM=m CONFIG_PHANTOM=m @@ -1929,7 +1929,7 @@ CONFIG_FIREWIRE_SBP2=m CONFIG_FIREWIRE_NET=m # CONFIG_IEEE1394 is not set -# CONFIG_FIREWIRE_NOSY is not set +CONFIG_FIREWIRE_NOSY=m CONFIG_I2O=m CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y CONFIG_I2O_EXT_ADAPTEC=y @@ -2120,7 +2120,7 @@ CONFIG_CHELSIO_T4_DEPENDS=y CONFIG_CHELSIO_T4=m CONFIG_CHELSIO_T4VF_DEPENDS=y -# CONFIG_CHELSIO_T4VF is not set +CONFIG_CHELSIO_T4VF=m CONFIG_ENIC=m CONFIG_IXGBE=m CONFIG_IXGBE_DCA=y @@ -2251,7 +2251,7 @@ CONFIG_NORTEL_HERMES=m CONFIG_PCMCIA_HERMES=m CONFIG_PCMCIA_SPECTRUM=m -# CONFIG_ORINOCO_USB is not set +CONFIG_ORINOCO_USB=m CONFIG_P54_COMMON=m CONFIG_P54_USB=m CONFIG_P54_PCI=m @@ -2285,8 +2285,8 @@ CONFIG_WL1251_SPI=m CONFIG_WL1251_SDIO=m CONFIG_WL1271=m -# CONFIG_WL1271_SPI is not set -# CONFIG_WL1271_SDIO is not set +CONFIG_WL1271_SPI=m +CONFIG_WL1271_SDIO=m CONFIG_ZD1211RW=m # CONFIG_ZD1211RW_DEBUG is not set @@ -2738,7 +2738,7 @@ # CONFIG_SERIAL_MAX3100=m # CONFIG_SERIAL_MAX3107 is not set -# CONFIG_SERIAL_MFD_HSU is not set +CONFIG_SERIAL_MFD_HSU=m CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_SERIAL_JSM=m @@ -2798,7 +2798,7 @@ CONFIG_TCG_INFINEON=m CONFIG_TELCLOCK=m CONFIG_DEVPORT=y -# CONFIG_RAMOOPS is not set +CONFIG_RAMOOPS=m CONFIG_I2C=m CONFIG_I2C_BOARDINFO=y CONFIG_I2C_COMPAT=y @@ -2897,7 +2897,7 @@ # PPS clients support # # CONFIG_PPS_CLIENT_KTIMER is not set -# CONFIG_PPS_CLIENT_LDISC is not set
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
Package: linux-2.6 Version: 2.6.36~rc6-1~experimental.1 Severity: important Tags: upstream Hello, I have a problem occurring for some time now, my system hangs each time I close the lid of my laptop (Dell studio 1555) whether I'm on a tty or in a X session, and the only solution is to restart manually the system (power button). This also happens in single boot mode. I found a workaround to prevent the system hanging, which is to boot with the 'nolapic' kernel option. I assume this issue would be APIC-based. The option disables others CPU cores which is a bit problematic. I'm running Debian testing. This problem was not present in the 2.6.32 version and appeared in the 2.6.38 version. I had not much time to determine at which version this problem began to be present but now I have time I had a closer look. I installed some versions of 'old' Debian kernel packages I found on http://snapshot.debian.org/ and I determined that the issue appeared between linux-image-2.6.35-trunk-686-bigmem (2.6.35-1~experimental.3) and linux-image-2.6.36-rc6-686-bigmem (2.6.36~rc6-1~experimental.1). Everything works fine in 2.6.35-trunk and issue in 2.6.36-rc6. I checked the configurations difference but found nothing pertinent. Hope this will help. Thanks in advance, -- Thibault Manlay -- Configuration diff: --- /boot/config-2.6.35-trunk-686-bigmem2010-09-06 21:19:30.0 +0200 +++ /boot/config-2.6.36-rc6-686-bigmem 2010-10-04 13:52:52.0 +0200 @@ -1,7 +1,7 @@ # # Automatically generated make config: don't edit -# Linux kernel version: 2.6.35 -# Mon Sep 6 16:49:05 2010 +# Linux kernel version: 2.6.36-rc6 +# Mon Oct 4 09:18:53 2010 # # CONFIG_64BIT is not set CONFIG_X86_32=y @@ -10,7 +10,6 @@ CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT=elf32-i386 CONFIG_ARCH_DEFCONFIG=arch/x86/configs/i386_defconfig -CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y @@ -93,14 +92,13 @@ CONFIG_TASK_IO_ACCOUNTING=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y +CONFIG_AUDIT_WATCH=y CONFIG_AUDIT_TREE=y # # RCU Subsystem # CONFIG_TREE_RCU=y -# CONFIG_TREE_PREEMPT_RCU is not set -# CONFIG_TINY_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RCU_FANOUT=32 # CONFIG_RCU_FANOUT_EXACT is not set @@ -144,7 +142,7 @@ CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y -CONFIG_KALLSYMS_ALL=y +# CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y @@ -173,7 +171,6 @@ # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set CONFIG_SLUB=y -# CONFIG_SLOB is not set CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y CONFIG_OPROFILE=m @@ -195,13 +192,12 @@ CONFIG_HAVE_HW_BREAKPOINT=y CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y CONFIG_HAVE_USER_RETURN_NOTIFIER=y +CONFIG_HAVE_PERF_EVENTS_NMI=y # # GCOV-based kernel profiling # # CONFIG_GCOV_KERNEL is not set -CONFIG_SLOW_WORK=y -# CONFIG_SLOW_WORK_DEBUG is not set CONFIG_HAVE_GENERIC_DMA_COHERENT=y CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y @@ -278,6 +274,7 @@ CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_PARAVIRT_GUEST=y CONFIG_XEN=y +CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=32 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set @@ -313,10 +310,8 @@ # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set -# CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_MATOM is not set -# CONFIG_GENERIC_CPU is not set CONFIG_X86_GENERIC=y CONFIG_X86_CPU=y CONFIG_X86_INTERNODE_CACHE_SHIFT=6 @@ -386,7 +381,6 @@ CONFIG_ILLEGAL_POINTER_VALUE=0 CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y -# CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y @@ -461,6 +455,7 @@ # CONFIG_ACPI_PROCFS_POWER is not set CONFIG_ACPI_POWER_METER=m CONFIG_ACPI_SYSFS_POWER=y +# CONFIG_ACPI_EC_DEBUGFS is not set # CONFIG_ACPI_PROC_EVENT is not set CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m @@ -483,6 +478,7 @@ CONFIG_ACPI_APEI=y CONFIG_ACPI_APEI_GHES=m # CONFIG_ACPI_APEI_EINJ is not set +# CONFIG_ACPI_APEI_ERST_DEBUG is not set CONFIG_SFI=y CONFIG_X86_APM_BOOT=y CONFIG_APM=m @@ -501,7 +497,6 @@ CONFIG_CPU_FREQ_STAT=m # CONFIG_CPU_FREQ_STAT_DETAILS is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set -# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set @@ -539,7 +534,7 @@ CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y -CONFIG_INTEL_IDLE=m +# CONFIG_INTEL_IDLE is not set # # Bus options (PCI etc.) @@ -548,7 +543,6 @@ # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set -# CONFIG_PCI_GOOLPC is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y @@ -680,13 +674,7 @@
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
Hi Thibault, Thibault Manlay wrote: I have a problem occurring for some time now, my system hangs each time I close the lid of my laptop [...] This problem was not present in the 2.6.32 version and appeared in the 2.6.38 version. I had not much time to determine at which version this problem began to be present but now I have time I had a closer look. I installed some versions of 'old' Debian kernel packages I found on http://snapshot.debian.org/ and I determined that the issue appeared between linux-image-2.6.35-trunk-686-bigmem (2.6.35-1~experimental.3) and linux-image-2.6.36-rc6-686-bigmem (2.6.36~rc6-1~experimental.1). Everything works fine in 2.6.35-trunk and issue in 2.6.36-rc6. Thanks, that's very useful. Does the latest -pae or -amd64 kernel from sid produce the same symptoms? Are you able to get logs from right before the hang (for example with netconsole)? If you have time to bisect to find the exact change that introduced this, that would be best of all --- it works like this: 1. Name an executable with the following content as and put it in your $PATH before /usr/bin, to work around Bug#620448. #!/bin/sh exec /usr/bin/as --size-check=warning $@ 2. # apt-get install build-essential git-core $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ git bisect start v2.6.36-rc6 v2.6.35 $ make localmodconfig; # minimal configuration $ make deb-pkg # dpkg -i ../name of package # reboot ... test test test ... $ cd ~/src/linux $ git bisect good; # if it works $ git bisect bad; # if the hang occurs $ git bisect skip; # if some other bug makes it hard to test # git checks out an appropriate next revision to test $ make silentoldconfig; # reuse configuration $ make deb-pkg # dpkg -i ../name of package # reboot ... test test test ... 3. Continue until it says the first bad commit, or until bored. In the latter case, run git bisect log to present the results. If the gitk package is installed, you can run git bisect visualize at any time to watch the regression range narrowing. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110826010402.gb14...@elie.gateway.2wire.net
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
On 26/08/11 03:04, Jonathan Nieder wrote: Does the latest -pae or -amd64 kernel from sid produce the same symptoms? Are you able to get logs from right before the hang (for Same issue on sid kernels linux-image-3.0.0-1-amd64 (3.0.0-2) and linux-image-3.0.0-1-686-pae (3.0.0-2). I tried to get logs with netconsole ; I remotely receive everything as expected during the boot, nevertheless nothing come when I reproduce the issue, for both of the kernels above. example with netconsole)? If you have time to bisect to find the exact change that introduced this, that would be best of all --- it works like this: I will do this sometime tomorrow but I think this may take a while :-) I have a friend with the same hardware as me, although he is running stable I think it would be pertinent trying a recent kernel on his laptop even if I'm pretty sure of the result. Btw, would a debug of APIC/LAPIC informations at boot be useful here? (kernel parameters apic=debug show_lapic=all) Thanks, -- Thibault Manlay signature.asc Description: OpenPGP digital signature
