Bug#419872: linux-source-2.6.18: apm's suspend-to-ram freezes on DELL Latitude C640 (regression)
> [Moritz Muehlenhoff, 17 Dec 2008 (21:44)]
> ...
> If you're running Etch, could you try to reproduce this bug
> with the 2.6.24 based kernel added in 4.0r4?
> http://packages.qa.debian.org/l/linux-2.6.24.html
Hi. It now seems to be OK again:
I did install
ii linux-image-2.6.24-etchnhalf.1-686 2.6.24-6~etchnhalf.7 Linux 2.6.24 image on PPro/Celeron/PII/PIII/P4
ii linux-source-2.6.24 2.6.24-6~etchnhalf.7 Linux kernel source for version 2.6.24 with Debian patches
and compiled the latter with the configuration of the former, just selecting APM instead of ACPI
and the proper processor type (see diff of config. files below). Suspend now seems to work fine
again (directly using the Fn-F1 key combination):
Dec 19 13:33:07 soma apmd[2060]: Suspending now
Dec 19 14:21:47 soma kernel: parport_pc 00:0e: disabled
Dec 19 14:21:47 soma kernel: serial 00:0c: disabled
Dec 19 14:21:47 soma kernel: atkbd.c: Spurious NAK on isa0060/serio0. Some program might be trying access hardware directly.
Dec 19 14:21:47 soma kernel: Intel machine check architecture supported.
Dec 19 14:21:47 soma kernel: Intel machine check reporting enabled on CPU#0.
Dec 19 14:21:47 soma kernel: CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
Dec 19 14:21:47 soma kernel: CPU0: Thermal LVT vector (0xf0) already installed
Dec 19 14:21:47 soma kernel: serial 00:0c: activated
Dec 19 14:21:47 soma kernel: parport_pc 00:0e: activated
Dec 19 14:21:47 soma kernel: PCI: Found IRQ 11 for device 0000:00:1d.0
Dec 19 14:21:47 soma kernel: PCI: Sharing IRQ 11 with 0000:01:00.0
Dec 19 14:21:47 soma kernel: PCI: Setting latency timer of device 0000:00:1d.0 to 64
Dec 19 14:21:47 soma kernel: PCI: Setting latency timer of device 0000:00:1e.0 to 64
Dec 19 14:21:47 soma kernel: PM: Writing back config space on device 0000:00:1f.1 at offset 9 (was 0, writing 20000000)
Dec 19 14:21:47 soma kernel: PM: Writing back config space on device 0000:00:1f.1 at offset 7 (was 1, writing 375)
Dec 19 14:21:47 soma kernel: PM: Writing back config space on device 0000:00:1f.1 at offset 6 (was 1, writing 171)
Dec 19 14:21:47 soma kernel: PM: Writing back config space on device 0000:00:1f.1 at offset 5 (was 1, writing 3f5)
Dec 19 14:21:47 soma kernel: PM: Writing back config space on device 0000:00:1f.1 at offset 4 (was 1, writing 1f1)
Dec 19 14:21:47 soma kernel: PCI: Found IRQ 11 for device 0000:00:1f.1
Dec 19 14:21:47 soma kernel: PCI: Sharing IRQ 11 with 0000:02:00.0
Dec 19 14:21:47 soma kernel: PCI: Found IRQ 11 for device 0000:00:1f.5
Dec 19 14:21:47 soma kernel: PCI: Sharing IRQ 11 with 0000:00:1f.6
Dec 19 14:21:47 soma kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64
Dec 19 14:21:48 soma kernel: PCI: Found IRQ 11 for device 0000:00:1f.6
Dec 19 14:21:48 soma kernel: PCI: Sharing IRQ 11 with 0000:00:1f.5
Dec 19 14:21:48 soma kernel: PCI: Setting latency timer of device 0000:00:1f.6 to 64
Dec 19 14:21:49 soma kernel: PM: Writing back config space on device 0000:02:00.0 at offset c (was 0, writing f9000000)
Dec 19 14:21:49 soma kernel: eth0: setting full-duplex.
Dec 19 14:21:50 soma kernel: hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
Dec 19 14:21:50 soma kernel: hda: UDMA/100 mode selected
Note that while I was there, I also tried using directly linux-image-2.6.24-etchnhalf.1-686 with
ACPI. In this case, the Fn-F1 key combination does not work anymore but it is possible to suspend
using `hibernate-ram`. The resume phase however is broken as I end up either with a functional
computer but with unusable garbled screen (including VTs) or (if the suspend phase is sufficiently
long) a non responding computer (with fan spinning out loud).
..................................................................................................
$ diff /boot/config-2.6.24-etchnhalf.1-686 /boot/config-2.6.24-soma
3,4c3,4
< # Linux kernel version: 2.6.24
< # Tue Dec 2 06:17:02 2008
---
> # Linux kernel version: 2.6.24-soma
> # Fri Dec 19 11:00:41 2008
168c168
< CONFIG_M686=y
---
> # CONFIG_M686 is not set
172c172
< # CONFIG_MPENTIUM4 is not set
---
> CONFIG_MPENTIUM4=y
191c191
< CONFIG_X86_L1_CACHE_SHIFT=5
---
> CONFIG_X86_L1_CACHE_SHIFT=7
193d192
< CONFIG_X86_PPRO_FENCE=y
198a198
> CONFIG_X86_INTEL_USERCOPY=y
249d248
< CONFIG_EFI=y
251d249
< CONFIG_BOOT_IOREMAP=y
280,306c278,279
< CONFIG_ACPI=y
< CONFIG_ACPI_SLEEP=y
< CONFIG_ACPI_PROCFS=y
< CONFIG_ACPI_PROCFS_POWER=y
< CONFIG_ACPI_SYSFS_POWER=y
< CONFIG_ACPI_PROC_EVENT=y
< CONFIG_ACPI_AC=m
< CONFIG_ACPI_BATTERY=m
< CONFIG_ACPI_BUTTON=m
< CONFIG_ACPI_VIDEO=m
< CONFIG_ACPI_FAN=m
< CONFIG_ACPI_DOCK=m
< CONFIG_ACPI_BAY=m
< CONFIG_ACPI_PROCESSOR=m
< CONFIG_ACPI_HOTPLUG_CPU=y
< CONFIG_ACPI_THERMAL=m
< CONFIG_ACPI_ASUS=m
< CONFIG_ACPI_TOSHIBA=m
< CONFIG_ACPI_BLACKLIST_YEAR=0
< # CONFIG_ACPI_DEBUG is not set
< CONFIG_ACPI_EC=y
< CONFIG_ACPI_POWER=y
< CONFIG_ACPI_SYSTEM=y
< CONFIG_X86_PM_TIMER=y
< CONFIG_ACPI_CONTAINER=m
< CONFIG_ACPI_SBS=m
< CONFIG_APM=m
---
> # CONFIG_ACPI is not set
> CONFIG_APM=y
309c282
< # CONFIG_APM_CPU_IDLE is not set
---
> CONFIG_APM_CPU_IDLE=y
335d307
< CONFIG_X86_ACPI_CPUFREQ=m
338d309
< CONFIG_X86_POWERNOW_K7_ACPI=y
340d310
< CONFIG_X86_POWERNOW_K8_ACPI=y
349d318
< CONFIG_X86_LONGHAUL=m
355d323
< # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
372d339
< CONFIG_PCI_MMCONFIG=y
416,417d382
< CONFIG_HOTPLUG_PCI_ACPI=m
< CONFIG_HOTPLUG_PCI_ACPI_IBM=m
1143c1108
< CONFIG_PNPACPI=y
---
> # CONFIG_PNPACPI is not set
1204,1211d1168
< CONFIG_ASUS_LAPTOP=m
< CONFIG_FUJITSU_LAPTOP=m
< CONFIG_MSI_LAPTOP=m
< CONFIG_SONY_LAPTOP=m
< CONFIG_SONYPI_COMPAT=y
< CONFIG_THINKPAD_ACPI=m
< # CONFIG_THINKPAD_ACPI_DEBUG is not set
< CONFIG_THINKPAD_ACPI_BAY=y
1228d1184
< # CONFIG_BLK_DEV_IDEACPI is not set
1437d1392
< CONFIG_ATA_ACPI=y
1454d1408
< # CONFIG_PATA_ACPI is not set
2215d2168
< CONFIG_INPUT_ATLAS_BTNS=m
2334,2336d2286
< CONFIG_HPET=y
< # CONFIG_HPET_RTC_IRQ is not set
< CONFIG_HPET_MMAP=y
2339,2340d2288
< CONFIG_TCG_TIS=m
< CONFIG_TCG_NSC=m
2342d2289
< CONFIG_TCG_INFINEON=m
2648d2594
< CONFIG_VIDEO_MEYE=m
2921d2866
< # CONFIG_FB_IMAC is not set
3572d3516
< CONFIG_EFI_VARS=m
Reply to: