Latest working kernel version:2.6.22
Earliest failing kernel version:
Hardware Environment: Sony vaio fz315s
When the ac_adapter is disconnected, acpi in theory should generate 2 events,
ac_adapter AC 00000080 00000000
battery BAT0 00000080 00000001
but in my case it only generates the BAT0 event.
Steps to reproduce:
Install a 2.6.24 kernel, execute acpi_listen and plug/unplug the ac_adapter.
Created attachment 16137 [details]
Created attachment 16138 [details]
Created attachment 16139 [details]
acpidump (real) output
> When the ac_adapter is disconnected,
> acpi in theory should generate 2 events,
> ac_adapter AC 00000080 00000000
> battery BAT0 00000080 00000001
The DSDT for this machine does have an AC Adapter.
It is callled "ADP1", matching the (arbitrary) example in the ACPI spec,
rather than "AC" in the example above.
Name (_HID, "ACPI0003")
Method (_PSR, 0, NotSerialized)
If (LEqual (ECON, Zero))
And (PHSB (0xD4, Zero), 0x80, Local0)
Store (^^PCI0.LPCB.EC.RPWR, Local0)
If (LEqual (Local0, Zero))
Method (_PCL, 0, NotSerialized)
There is a single place in the AML where a notify is sent
to Device(ADP1) -- GPE21.
you should be able to see what GPE fires on AC/DC events with
grep . /sys/firmware/acpi/interrupts/*
and watching which one increments. (2.6.25 and later)
Hopefully it is gpe21 (hex).
Method (_Q21, 0, NotSerialized)
P8XH (Zero, 0x21)
Store (RPWR, PWRS)
Notify (ADP1, 0x81)
Notify (BAT0, 0x80)
The problem here may be that the AML is sending 0x81
when the ac driver expects 0x80.
If CONFIG_ACPI_DEBUG=y, then ac will print a message when
it receives an unknown notify value.
Created attachment 16152 [details]
patch vs 2.6.26-rc2
please try this patch
Hi, this patch work perfectly! I tested it with all my laptops and it works very well.
A note, I tested it under 2.6.24 kernel.
len, I think this bug can be closed. :)
patch in comment #5 applied to acpi-test
shipped in linux-2.6.26-rc7
Author: Len Brown <firstname.lastname@example.org>
Date: Sat Jun 14 01:26:37 2008 -0400
ACPI: no AC status notification
*** Bug 10511 has been marked as a duplicate of this bug. ***