You are not logged in.
Hello,
The laptop is an old Toshiba dynabook CX1/212CMEW, Celeron M CPU, so it doesn't have most of the power saving features. I frequently see the following message when monitoring with journalctl -f
Apr 19 18:14:04 Elder logger[750]: ACPI action undefined: PNP0C0A:00
Apr 19 18:14:21 Elder logger[771]: ACPI action undefined: PNP0C0A:00
Apr 19 18:14:37 Elder logger[792]: ACPI action undefined: PNP0C0A:00
Apr 19 18:14:54 Elder logger[813]: ACPI action undefined: PNP0C0A:00
Apr 19 18:15:11 Elder logger[831]: ACPI action undefined: PNP0C0A:00
Apr 19 18:15:28 Elder logger[852]: ACPI action undefined: PNP0C0A:00
Apr 19 18:15:45 Elder logger[874]: ACPI action undefined: PNP0C0A:00
Apr 19 18:16:19 Elder logger[910]: ACPI action undefined: PNP0C0A:00
Apr 19 18:16:35 Elder logger[928]: ACPI action undefined: PNP0C0A:00
Apr 19 18:16:52 Elder logger[950]: ACPI action undefined: PNP0C0A:00
Apr 19 18:17:09 Elder logger[968]: ACPI action undefined: PNP0C0A:00
Apr 19 18:17:26 Elder logger[989]: ACPI action undefined: PNP0C0A:00
Apr 19 18:17:59 Elder logger[1025]: ACPI action undefined: PNP0C0A:00
Apr 19 18:18:16 Elder logger[1046]: ACPI action undefined: PNP0C0A:00
Apr 19 18:18:33 Elder logger[1064]: ACPI action undefined: PNP0C0A:00
Apr 19 18:19:04 Elder logger[1100]: ACPI action undefined: PNP0C0A:00
Apr 19 18:19:06 Elder logger[1105]: ACPI action undefined: PNP0C0A:00
Apr 19 18:19:40 Elder logger[1141]: ACPI action undefined: PNP0C0A:00
Apr 19 18:19:56 Elder logger[1159]: ACPI action undefined: PNP0C0A:00
Apr 19 18:20:30 Elder logger[1198]: ACPI action undefined: PNP0C0A:00
Apr 19 18:21:04 Elder logger[1236]: ACPI action undefined: PNP0C0A:00
Apr 19 18:21:20 Elder logger[1254]: ACPI action undefined: PNP0C0A:00
Apr 19 18:21:37 Elder logger[1275]: ACPI action undefined: PNP0C0A:00
Apr 19 18:22:27 Elder logger[1314]: ACPI action undefined: PNP0C0A:00
Apr 19 18:23:01 Elder logger[1335]: ACPI action undefined: PNP0C0A:00
Apr 19 18:23:35 Elder logger[1359]: ACPI action undefined: PNP0C0A:00
Apr 19 18:23:51 Elder logger[1371]: ACPI action undefined: PNP0C0A:00
Apr 19 18:26:06 Elder logger[1457]: ACPI action undefined: PNP0C0A:00
Apr 19 18:26:39 Elder logger[1481]: ACPI action undefined: PNP0C0A:00
Apr 19 18:26:56 Elder logger[1493]: ACPI action undefined: PNP0C0A:00
Apr 19 18:27:13 Elder logger[1508]: ACPI action undefined: PNP0C0A:00
Apr 19 18:28:03 Elder logger[1541]: ACPI action undefined: PNP0C0A:00
Apr 19 18:28:37 Elder logger[1564]: ACPI action undefined: PNP0C0A:00
Apr 19 18:29:27 Elder logger[1598]: ACPI action undefined: PNP0C0A:00
Apr 19 18:29:43 Elder logger[1610]: ACPI action undefined: PNP0C0A:00
Apr 19 18:31:07 Elder logger[1666]: ACPI action undefined: PNP0C0A:00
Apr 19 18:32:48 Elder logger[1729]: ACPI action undefined: PNP0C0A:00
Looking around, it seems to be related to the AC adapter somehow. I have the default handler.sh, modified for also handling the brightness keys:
#!/bin/bash
# Default acpi script that takes an entry for all actions
case "$1" in
button/power)
case "$2" in
PBTN|PWRF)
logger 'PowerButton pressed'
;;
*)
logger "ACPI action undefined: $2"
;;
esac
;;
button/sleep)
case "$2" in
SLPB|SBTN)
logger 'SleepButton pressed'
echo -n mem >/sys/power/state
;;
*)
logger "ACPI action undefined: $2"
;;
esac
;;
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
logger 'AC unpluged'
;;
00000001)
logger 'AC pluged'
;;
esac
;;
*)
logger "ACPI action undefined: $2"
;;
esac
;;
battery)
case "$2" in
BAT0)
case "$4" in
00000000)
logger 'Battery online'
;;
00000001)
logger 'Battery offline'
;;
esac
;;
CPU0)
;;
*) logger "ACPI action undefined: $2" ;;
esac
;;
button/lid)
case "$3" in
close)
logger 'LID closed'
;;
open)
logger 'LID opened'
;;
*)
logger "ACPI action undefined: $3"
;;
esac
;;
video/brightnessdown)
echo $(($(< /sys/class/backlight/toshiba/brightness) - 1)) > /sys/class/backlight/toshiba/brightness
;;
video/brightnessup)
echo $(($(< /sys/class/backlight/toshiba/brightness) + 1)) > /sys/class/backlight/toshiba/brightness
;;
# button/screenlock)
# xs=$(ps -C xscreensaver -o user=)
# if test $xs; then su $xs -c "xscreensaver-command -lock"; fi
# ;;
*)
logger "ACPI group/action undefined: $1 / $2"
;;
esac
# vim:set ts=4 sw=4 ft=sh et:
It appears whether the laptop is running on battery or on AC. When unplugging, the following appears in the log:
Apr 19 18:41:47 Elder kernel: toshiba_acpi: Unknown key e00
Apr 19 18:41:47 Elder logger[2226]: ACPI action undefined: ACPI0003:00
Plugging in shows the following:
Apr 19 18:44:31 Elder logger[2362]: ACPI action undefined: ACPI0003:00
I expected to see :01 while either plugging or unplugging the AC adaptor... Though (dis)charging state seems to be correctly reported to LXDE's battery widget.
Quite new to linux, so I'm a bit lost on how to "fix" that. Or can I safely ignore that without any side-effects on the battery? I can provide more info if you tell me where to get it.
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
You could ignore it, but I suggest you adapt that default handler.sh to ignore events with PNP in them. That would prevent flooding of your journal.
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline