http://bugzilla.kernel.org/show_bug.cgi?id=6847
Summary: Reading from /proc/acpi/battery/BAT0/state kills acpi
iff it has not been preceeded by a button press
Kernel Version: 2.6.17.1 (mainline)
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
This is really odd.
1)COLD boot (into K 2.6.17.1). Log in at VT 1.
2)cat /proc/acpi/battery/BAT0/state
3)Now, you can't write to any of /proc/acpi/, and /dev/nvram no longer reacts to
the buttons being pressed. A cold reboot is required to recover.
BUT
1)COLD boot (into K 2.6.17.1)
2)Press Fn-F12...which triggers acpid...which causes a write to
/proc/acpi/ibm/light
3)cat /proc/acpi/battery/BAT0/state
4)All is still fine.
You must press the physical button; merely writing to the /proc/acpi/ibm/light
is insufficient. It seems that *any* software read from BAT0/state will mess
up
acpi/nvram unless at least one hardware write to acpi (press a button) has
previously occurred!
The machine is a thinkpad X20, with kernel 2.6.17.1
In the "broken" state, writing to /proc/acpi/ibm/foo will just time out, with
no effect. Furthermore, `cat /dev/nvram` no longer changes in response to the
volume buttons etc being pressed.
We're doing something horrid to the BIOS, I think.
Please let me know if there is anything else I can help with. I'm still a kernel
newbie :-)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------------------------
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
