http://bugzilla.kernel.org/show_bug.cgi?id=5904
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
------- Additional Comments From [EMAIL PROTECTED] 2006-08-23 19:36 -------
Rui,
Looking at the DSDT...
Device (LID)
{
Name (_HID, EisaId ("PNP0C0D"))
Method (_LID, 0, NotSerialized)
{
If (LIDS)
{
Return (0x01)
}
Else
{
Return (0x00)
}
}
Name (_PRW, Package (0x02)
{
0x18,
0x03
})
}
and LIDS is defined here:
OperationRegion (MNVS, SystemMemory, 0x0EEEBF09, 0x40)
Field (MNVS, AnyAcc, Lock, Preserve)
{
OSYS, 16,
SMIF, 8,
PRM0, 8,
PRM1, 8,
SCIF, 8,
PRM2, 8,
PRM3, 8,
LCKF, 8,
PRM4, 8,
PRM5, 8,
DBGS, 8,
DCKS, 4,
CDCK, 4,
FPEN, 8,
FPST, 8,
LIDS, 8,
PWRS, 8,
and LIDS is accessed here:
Method (_Q2E, 0, NotSerialized)
{
Store (0x2E, P80H)
If (LEqual (\_SB.PCI0.LPCB.EC.P54, 0x00))
{
Store (0x98, \_SB.PCI0.LPCB.EC.P54S)
Store (0x00, LIDS)
}
Else
{
Store (0x88, \_SB.PCI0.LPCB.EC.P54S)
Store (0x01, LIDS)
}
Notify (\_SB.LID, 0x80)
}
Which is an Embedded Controller event handler.
and P54 is defined here:
OperationRegion (ERAM, EmbeddedControl, 0x00, 0x7F)
Field (ERAM, AnyAcc, Lock, Preserve)
{
Offset (0x01),
SCIC, 8,
Offset (0x04),
CMCD, 8,
DAT1, 8,
DAT2, 8,
DAT3, 8,
Offset (0x18),
SMPR, 8,
SMST, 8,
SMAD, 8,
SMCM, 8,
SMD0, 264,
SMAA, 8,
Offset (0x43),
P50, 1,
, 2,
P43, 1,
P54, 1,
If you can access the valuyes of P54 and LIDS before
any lid events are triggered, then that will tell us
if the values are correct in the hardware and perhaps an
EC event was necessary to update LIDS and notify the OS.
(and maybe Linux has a bug where that even was dropped
and the EC handler was not invoked?)
or if the values are incorrect in P54 and LIDS until there is
an actual LID change, then this hardware and BIOS simply
work that way and Linux will not be able to fix this bug.
Fabian,
It would be interesting if you can boot the laptop with
the lid closed, log in over the network and observe the
lid status then. presumably it will say closed, as that
is apparently the inital value no matter what.
Then on 1st open the lid state should immediately switch
to open, because this ec event handler should run for
the first time (and you should see an increment under
acpi in /proc/interrupts) and update the value to be open.
If that doesn't work, then I'm off track here and the
issue is elsewhere.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
acpi-bugzilla mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
