Bug 4132 - Access to battery state after S3 resume causes system freeze
Summary: Access to battery state after S3 resume causes system freeze
Status: REJECTED UNREPRODUCIBLE
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Shaohua
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-30 04:27 UTC by David Drusowitsch
Modified: 2007-08-18 14:28 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.11-rc2
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description David Drusowitsch 2005-01-30 04:27:06 UTC
Distribution: Gentoo Linux
Hardware Environment: Acer TravleMate C100
Software Environment: gcc (GCC) 3.3.4 20040623
Problem Description: If you reaccessing battery state after S3 resume system
freezes.

Steps to reproduce:
Append acpi_sleep=S3_bios at startup.
Under Kde remove KLaptop applet from panel because KLaptop also causes system
freeze after resume.
From console echo mem > /sys/power/state 
System suspends to memory.
Wake up, Display and Kde comes up.
Starting KLaptop --> system frezes
Access /proc/acpi/battery/BAT0/state --> system freezes
Comment 1 Shaohua 2005-01-30 17:13:26 UTC
Hi, please attach your acpidmp. The reason possibly is we didn't invoke 
battery resume method.
Comment 2 David Drusowitsch 2005-01-31 11:59:56 UTC
Sorry acpidmp is not working correctly because the bios is broken. 
RSDP "Acer" @ 0x000ec2d0
  0000: 52 53 44 20 50 54 52 20 00 41 63 65 72 20 20 00  RSD PTR .Acer  .
  0010: 00 00 00 00                                      ....

acpidmp: cannot map the RSDT

I must allways apply a patch to get acpi support working.

This is what kernel output says without the patch:
ACPI: RSDP (v000 Acer                       ) @ 0x000ec2d0
   >>> ERROR: Invalid checksum

This is the kernel output with patch:
 BIOS-e820: 000000000ffe0000 - 000000000ffe8000 (ACPI data)
 BIOS-e820: 000000000ffe8000 - 0000000010000000 (ACPI NVS)
ACPI: RSDP (v000 Acer                                  ) @ 0x000fe030
ACPI: RSDT (v001 Acer   TM100    0x00000001 MSFT 0x00000001) @ 0x0ffe0000
ACPI: FADT (v001 Acer   TM100    0x00000001 MSFT 0x00000001) @ 0x0ffe0054
ACPI: BOOT (v001 Acer   TM100    0x00000001 MSFT 0x00000001) @ 0x0ffe002c
ACPI: DSDT (v001   Acer   AN100  0x00001000 MSFT 0x0100000e) @ 0x00000000
ACPI: setting ELCR to 0200 (from 0c00)
ACPI: Subsystem revision 20050125
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [PILA] (IRQs *10 15)
ACPI: PCI Interrupt Link [PILB] (IRQs *11 15)
ACPI: PCI Interrupt Link [PILD] (IRQs *10 15)
ACPI: PCI Root Bridge [PCI0] (00:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Embedded Controller [EC0] (gpe 24)
PCI: Using ACPI for IRQ routing
ACPI: AC Adapter [AC] (off-line)
ACPI: Battery Slot [BAT0] (battery present)
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Lid Switch [LID]
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3] C4[C3])
ACPI: Thermal Zone [THR1] (29 C)
ACPI: Thermal Zone [THR2] (27 C)
ACPI: PS/2 Keyboard Controller [KBC0] at I/O 0x60, 0x64, irq 1
ACPI: PS/2 Mouse Controller [PS2M] at irq 12
ACPI: PCI Interrupt Link [PILB] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:00.2[B] -> GSI 11 (level, low) -> IRQ 11
ACPI wakeup devices:
ACPI: (supports S0 S3 S4 S4bios S5)
ACPI: PCI Interrupt Link [PILD] enabled at IRQ 10
ACPI: PCI interrupt 0000:00:07.2[D] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:00:00.1[B] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [PILA] enabled at IRQ 10
ACPI: PCI interrupt 0000:00:03.0[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:00:03.1[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 10 (level, low) -> IRQ 10
 
The patch was posted somewere at sourceforge mailing lists:

http://sourceforge.net/mailarchive/message.php?msg_id=3658132
http://sourceforge.net/mailarchive/forum.php?forum_id=6102&max_rows=25&style=nested&viewmonth=200402

It also checks for vaild checksum after looking for the RSDP signature.
Comment 3 Rafael J. Wysocki 2007-06-04 10:02:08 UTC
Can anyone please close this bug?  It's completely stale.
Comment 4 Len Brown 2007-08-18 14:28:03 UTC
please re-open if this is still a problem in 2.6.22.stable or later

Note You need to log in before you can comment on or make changes to this bug.