> My power button stops working after resume from suspend due to some
kernel issue.
> To work around this issue I reload the button module in my suspend
script and after reloading the module kacpimon shows events from the button.
> However, acpid still does not react to the button until restarted.
Are you still having trouble with this?
If so, here's an idea. Try killing acpid
sudo killall acpid
then running it in debug mode at the console.
sudo /usr/sbin/acpid -d
Now suspend and resume. In debug mode, acpid should print a bunch of
informational messages that might be of some help in tracking down why
it is getting confused. Post the output here and perhaps there will be
something in there that might lead to a solution.
I was able to stop and restart the button module and observe the
correct behavior from acpid. It looks like this:
sudo /sbin/rmmod button
acpid: input device has been disconnected
acpid: input device has been disconnected
acpid: input device has been disconnected
sudo /sbin/modprobe button
inotify read bytes: 32
inotify name len: 16
inotify about to open: /dev/input/event4
input layer /dev/input/event4 opened successfully
inotify read bytes: 32
inotify name len: 16
inotify about to open: /dev/input/event3
input layer /dev/input/event3 opened successfully
inotify read bytes: 32
inotify name len: 16
inotify about to open: /dev/input/event2
input layer /dev/input/event2 opened successfully
So, it appears to work for me.
Ted.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
