You are not logged in.

Pages: 1

#1 2015-06-22 22:23:47

AndrzejL
Member
Registered: 2012-12-07
Posts: 160

[SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

Hi there.

Upgraded the machine with pacman -Syu several minutes ago as one would.

[2015-06-22 23:01] [PACMAN] Running 'pacman -Syu'
[2015-06-22 23:01] [PACMAN] synchronizing package lists
[2015-06-22 23:01] [PACMAN] starting full system upgrade
[2015-06-22 23:02] [ALPM] transaction started
[2015-06-22 23:02] [ALPM] upgraded ca-certificates-mozilla (3.19.1-1 -> 3.19.1-2)
[2015-06-22 23:02] [ALPM] upgraded libsystemd (219-6 -> 221-1)
[2015-06-22 23:02] [ALPM] warning: /etc/systemd/journald.conf installed as /etc/systemd/journald.conf.pacnew
[2015-06-22 23:02] [ALPM] warning: /etc/systemd/logind.conf installed as /etc/systemd/logind.conf.pacnew
[2015-06-22 23:02] [ALPM] upgraded systemd (219-6 -> 221-1)
[2015-06-22 23:02] [ALPM] installed libgudev (230-1)
[2015-06-22 23:02] [ALPM] upgraded colord (1.2.9-2 -> 1.2.9-3)
[2015-06-22 23:02] [ALPM] upgraded nss (3.19.1-1 -> 3.19.1-2)
[2015-06-22 23:02] [ALPM] upgraded systemd-sysvcompat (219-6 -> 221-1)
[2015-06-22 23:02] [ALPM] upgraded upower (0.99.2-2 -> 0.99.3-1)
[2015-06-22 23:02] [ALPM] transaction completed
[2015-06-22 23:03] [PACMAN] Running 'pacman -Syu'
[2015-06-22 23:03] [PACMAN] synchronizing package lists
[2015-06-22 23:03] [PACMAN] starting full system upgrade
[2015-06-22 23:09] [PACMAN] Running 'pacman -S cgroup_event_listener'
[2015-06-22 23:09] [ALPM] transaction started
[2015-06-22 23:09] [ALPM] installed cgroup_event_listener (4.0-3)
[2015-06-22 23:09] [ALPM] transaction completed

Noticed the pacnew files and merged them. Also noticed that there was a systemd upgrade so *just in case* I've decided to run mkinitcpio -p linux and reboot.

Noticed this message right after the grub window disappeared:

Failed to get cgroup: no such file or directory.

And I get this message:

[root@andrzejl andrzejl]# journalctl -b -l -x --no-pager -p 1
-- Logs begin at Thu 2015-01-15 15:52:24 GMT, end at Mon 2015-06-22 23:13:58 IST. --
Failed to get journal fields: Cannot assign requested address
[root@andrzejl andrzejl]# journalctl -b -l -x --no-pager -p 2
-- Logs begin at Thu 2015-01-15 15:52:24 GMT, end at Mon 2015-06-22 23:16:13 IST. --
Failed to get journal fields: Cannot assign requested address

in the journal.

Should I be worried?

Edit 01: On my _VERY_ old laptop IBM Thinkpad 600E all of the sudden I got this in journal:

[root@wishthinkpad andrzejl]# journalctl -b -l -x --no-pager -p 1
-- Logs begin at Sat 2014-12-20 09:00:02 GMT, end at Tue 2015-06-23 00:04:00 IST. --
Failed to get journal fields: Cannot assign requested address
[root@wishthinkpad andrzejl]# journalctl -b -l -x --no-pager -p 2
-- Logs begin at Sat 2014-12-20 09:00:02 GMT, end at Tue 2015-06-23 00:04:18 IST. --
Failed to get journal fields: Cannot assign requested address
[root@wishthinkpad andrzejl]# journalctl -b -l -x --no-pager -p 3
-- Logs begin at Sat 2014-12-20 09:00:02 GMT, end at Tue 2015-06-23 00:04:18 IST. --
Jun 22 23:55:37 wishthinkpad.loc kernel: serial 00:03: unable to assign resources
Jun 22 23:55:46 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x1, key code 236): Invalid argument
Jun 22 23:55:46 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x2, key code 152): Invalid argument
Jun 22 23:55:46 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x3, key code 142): Invalid argument
Jun 22 23:55:46 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x4, key code 238): Invalid argument
Jun 22 23:55:46 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x6, key code 227): Invalid argument
Jun 22 23:55:46 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x7, key code 372): Invalid argument
Jun 22 23:55:46 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x8, key code 194): Invalid argument
Jun 22 23:55:46 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xb, key code 205): Invalid argument
Jun 22 23:55:49 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xf, key code 225): Invalid argument
Jun 22 23:55:49 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x10, key code 224): Invalid argument
Jun 22 23:55:49 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x11, key code 228): Invalid argument
Jun 22 23:55:49 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x13, key code 372): Invalid argument
Jun 22 23:55:49 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x14, key code 115): Invalid argument
Jun 22 23:55:49 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x15, key code 114): Invalid argument
Jun 22 23:55:49 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x16, key code 113): Invalid argument
Jun 22 23:55:49 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x17, key code 148): Invalid argument
Jun 22 23:55:52 wishthinkpad.loc kernel: ACPI: Fatal opcode executed
Jun 22 23:55:52 wishthinkpad.loc kernel: piix4_smbus 0000:00:07.3: IBM system detected; this module may corrupt your serial eeprom! Refusing to load module!
Jun 23 00:03:50 wishthinkpad.loc kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 23 00:03:55 wishthinkpad.loc kernel: ata1.00: BMDMA stat 0x25
Jun 23 00:03:55 wishthinkpad.loc kernel: ata1.00: failed command: READ DMA
Jun 23 00:03:55 wishthinkpad.loc kernel: ata1.00: cmd c8/00:08:b7:21:b0/00:00:00:00:00/e0 tag 0 dma 4096 in
                                                  res 51/40:05:ba:21:b0/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 23 00:03:55 wishthinkpad.loc kernel: ata1.00: status: { DRDY ERR }
Jun 23 00:03:55 wishthinkpad.loc kernel: ata1.00: error: { UNC }
Jun 23 00:03:55 wishthinkpad.loc kernel: end_request: I/O error, dev sda, sector 11542970
Jun 23 00:03:55 wishthinkpad.loc kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 23 00:03:55 wishthinkpad.loc kernel: ata1.00: BMDMA stat 0x25
Jun 23 00:03:55 wishthinkpad.loc kernel: ata1.00: failed command: READ DMA
Jun 23 00:03:55 wishthinkpad.loc kernel: ata1.00: cmd c8/00:08:b7:21:b0/00:00:00:00:00/e0 tag 0 dma 4096 in
                                                  res 51/40:05:ba:21:b0/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 23 00:03:55 wishthinkpad.loc kernel: ata1.00: status: { DRDY ERR }
Jun 23 00:03:55 wishthinkpad.loc kernel: ata1.00: error: { UNC }
Jun 23 00:03:55 wishthinkpad.loc kernel: end_request: I/O error, dev sda, sector 11542970
Jun 23 00:04:00 wishthinkpad.loc kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 23 00:04:00 wishthinkpad.loc kernel: ata1.00: BMDMA stat 0x25
Jun 23 00:04:00 wishthinkpad.loc kernel: ata1.00: failed command: READ DMA
Jun 23 00:04:00 wishthinkpad.loc kernel: ata1.00: cmd c8/00:08:b7:21:b0/00:00:00:00:00/e0 tag 0 dma 4096 in
                                                  res 51/40:05:ba:21:b0/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 23 00:04:00 wishthinkpad.loc kernel: ata1.00: status: { DRDY ERR }
Jun 23 00:04:00 wishthinkpad.loc kernel: ata1.00: error: { UNC }
Jun 23 00:04:00 wishthinkpad.loc kernel: end_request: I/O error, dev sda, sector 11542970

Downgrading systemd colord gstreamer0.10-good gstreamer0.10-good-plugins udisks2 gvfs libmbim libmm-glib nss libnm-glib modemmanager networkmanager systemd-sysvcompat upower and removing libgudev and udisks (it was failing because of no libgudev) and the journal is "clean" again.

[root@wishthinkpad andrzejl]# journalctl -b -l -x --no-pager -p 1-- Logs begin at Sat 2014-12-20 09:00:02 GMT, end at Tue 2015-06-23 00:34:54 IST. --
[root@wishthinkpad andrzejl]# journalctl -b -l -x --no-pager -p 2
-- Logs begin at Sat 2014-12-20 09:00:02 GMT, end at Tue 2015-06-23 00:34:54 IST. --
[root@wishthinkpad andrzejl]# journalctl -b -l -x --no-pager -p 3
-- Logs begin at Sat 2014-12-20 09:00:02 GMT, end at Tue 2015-06-23 00:34:54 IST. --
Jun 23 00:32:58 wishthinkpad.loc kernel: serial 00:03: unable to assign resources
Jun 23 00:33:12 wishthinkpad.loc kernel: ACPI: Fatal opcode executed
Jun 23 00:33:12 wishthinkpad.loc kernel: piix4_smbus 0000:00:07.3: IBM system detected; this module may corrupt your serial eeprom! Refusing to load module!

Cheers.

Andrzej

Last edited by AndrzejL (2015-06-24 05:12:59)

The worst thing about censorship is ██████ ██ ████ ████████████ and ██████ ███████ ███ ███████████.

Offline

#2 2015-06-23 05:37:03

mauritiusdadd
Member
From: Benevento, Italy
Registered: 2013-10-27
Posts: 776

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

Hi AndrzejL, please edit your post and replace the quote tags with code tags, like the following: [⁣code]code goes here[/code⁣].

AndrzejL wrote:
Jun 22 23:55:46 wishthinkpad.loc systemd-udevd[328]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x1, key code 236): Invalid argument

Do you have a custom udev hwdb rule by any chance (look in /etc/udev/hwdb.d/)? If so, note that the udev hwdb ABI changed from systemd 220.

AndrzejL wrote:
-- Logs begin at Thu 2015-01-15 15:52:24 GMT, end at Mon 2015-06-22 23:13:58 IST. --
Failed to get journal fields: Cannot assign requested address
[root@andrzejl andrzejl]# journalctl -b -l -x --no-pager -p 2
-- Logs begin at Thu 2015-01-15 15:52:24 GMT, end at Mon 2015-06-22 23:16:13 IST. --
Failed to get journal fields: Cannot assign requested address

That happens probably because there is no message with the priority alert and crit and it seems that journalctl now informs you about that.

Last edited by mauritiusdadd (2015-06-23 06:18:17)

About me - github

-- When you have eliminated the impossible, whatever remains, however improbable, must be the truth -- Spock | Sherlock Holmes

Offline

#3 2015-06-23 07:12:09

dkaylor
Member
Registered: 2015-04-10
Posts: 7

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

I get the same "Failed to get cgroup: no such file or directory." message. A very quick google search doesn't show much EXACTLY matching. Not having any issues with journalctl, so not sure about that.

My system seems to be running normally, so it MAY be harmless. I will keep looking around, and post here anything further.

Offline

#4 2015-06-23 08:09:03

AndrzejL
Member
Registered: 2012-12-07
Posts: 160

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

mauritiusdadd wrote:

Do you have a custom udev hwdb rule by any chance (look in /etc/udev/hwdb.d/)? If so, note that the udev hwdb ABI changed from systemd 220.

[root@wishthinkpad andrzejl]# ls /etc/udev/hwdb.d/
[root@wishthinkpad andrzejl]#

No custom rules.

Cheers.

Andrzej

Last edited by AndrzejL (2015-06-23 17:18:21)

The worst thing about censorship is ██████ ██ ████ ████████████ and ██████ ███████ ███ ███████████.

Offline

#5 2015-06-23 08:49:02

mauritiusdadd
Member
From: Benevento, Italy
Registered: 2013-10-27
Posts: 776

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

Unfortunately I have no clue on what causes the cgroup error message.

AndrzejL wrote:
[root@wishthinkpad andrzejl]# ls /etc/udev/hwdb.d/
[root@wishthinkpad andrzejl]#

No custom rules.

Cheers.

Andrzej

Can you post the output of the following commands on the updated system?

uname -a
udevadm test /sys/class/input/event0

Also, apart the messages in the journal, do you have any actual problem with your system? Is there something not working?

About me - github

-- When you have eliminated the impossible, whatever remains, however improbable, must be the truth -- Spock | Sherlock Holmes

Offline

#6 2015-06-23 09:34:19

AndrzejL
Member
Registered: 2012-12-07
Posts: 160

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

mauritiusdadd wrote:

Unfortunately I have no clue on what causes the cgroup error message.

AndrzejL wrote:
[root@wishthinkpad andrzejl]# ls /etc/udev/hwdb.d/
[root@wishthinkpad andrzejl]#

No custom rules.

Cheers.

Andrzej

Can you post the output of the following commands on the updated system?

uname -a
udevadm test /sys/class/input/event0

Also, apart the messages in the journal, do you have any actual problem with your system? Is there something not working?

Hi

On the downgraded / properly working machine:

[root@wishthinkpad andrzejl]# uname -a
Linux wishthinkpad.loc 3.14.44-1-lts #1 SMP Sat Jun 6 20:44:29 CEST 2015 i686 GNU/Linux
[root@wishthinkpad andrzejl]# udevadm test /sys/class/input/event0
calling: test
version 219
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

=== trie on-disk ===
tool version:          219
file size:         6870071 bytes
header size             80 bytes
strings            1722743 bytes
nodes              5147248 bytes
Load module index
timestamp of '/etc/systemd/network' changed
timestamp of '/usr/lib/systemd/network' changed
Parsed configuration file /usr/lib/systemd/network/99-default.link
Created link configuration context.
timestamp of '/etc/udev/rules.d' changed
timestamp of '/usr/lib/udev/rules.d' changed
Reading rules file: /usr/lib/udev/rules.d/10-dm.rules
Reading rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
Reading rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
Reading rules file: /usr/lib/udev/rules.d/39-usbmuxd.rules
Reading rules file: /usr/lib/udev/rules.d/40-gphoto.rules
Reading rules file: /usr/lib/udev/rules.d/40-hpet-permissions.rules
Reading rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
Reading rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
Reading rules file: /usr/lib/udev/rules.d/49-sane.rules
Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules
Reading rules file: /usr/lib/udev/rules.d/56-hpmud.rules
Reading rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
Reading rules file: /usr/lib/udev/rules.d/60-drm.rules
Reading rules file: /usr/lib/udev/rules.d/60-keyboard.rules
Reading rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
Reading rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
Reading rules file: /usr/lib/udev/rules.d/61-kde-bluetooth-rfkill.rules
Reading rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
Reading rules file: /usr/lib/udev/rules.d/64-btrfs.rules
Reading rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
Reading rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
Reading rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
Reading rules file: /usr/lib/udev/rules.d/69-libftdi.rules
Reading rules file: /usr/lib/udev/rules.d/69-libmtp.rules
Reading rules file: /usr/lib/udev/rules.d/70-infrared.rules
Reading rules file: /usr/lib/udev/rules.d/70-mouse.rules
Reading rules file: /etc/udev/rules.d/70-persistent-net.rules
Reading rules file: /usr/lib/udev/rules.d/70-power-switch.rules
Reading rules file: /usr/lib/udev/rules.d/70-touchpad.rules
Reading rules file: /usr/lib/udev/rules.d/70-uaccess.rules
Reading rules file: /etc/udev/rules.d/71-persistent-net.rules
Reading rules file: /usr/lib/udev/rules.d/71-seat.rules
Reading rules file: /usr/lib/udev/rules.d/73-seat-late.rules
Reading rules file: /usr/lib/udev/rules.d/75-net-description.rules
Reading rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
Reading rules file: /usr/lib/udev/rules.d/75-tty-description.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-cinterion-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-ericsson-mbm.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-huawei-net-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-longcheer-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-mtk-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-nokia-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-pcmcia-device-blacklist.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-platform-serial-whitelist.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-simtech-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-telit-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-usb-device-blacklist.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-usb-serial-adapters-greylist.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-x22x-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-zte-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-nm-olpc-mesh.rules
Reading rules file: /usr/lib/udev/rules.d/78-sound-card.rules
Reading rules file: /usr/lib/udev/rules.d/80-drivers.rules
Reading rules file: /usr/lib/udev/rules.d/80-libinput-device-groups.rules
Reading rules file: /usr/lib/udev/rules.d/80-mm-candidate.rules
Reading rules file: /usr/lib/udev/rules.d/80-net-setup-link.rules
Reading rules file: /usr/lib/udev/rules.d/80-udisks.rules
Reading rules file: /usr/lib/udev/rules.d/80-udisks2.rules
Reading rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
Reading rules file: /usr/lib/udev/rules.d/90-libinput-model-quirks.rules
Reading rules file: /usr/lib/udev/rules.d/90-pulseaudio.rules
Reading rules file: /usr/lib/udev/rules.d/90-vconsole.rules
Reading rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
Reading rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
Reading rules file: /usr/lib/udev/rules.d/95-udev-late.rules
Reading rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
Reading rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
Reading rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
Reading rules file: /usr/lib/udev/rules.d/99-systemd.rules
rules contain 393216 bytes tokens (32768 * 12 bytes), 31344 bytes strings
20788 strings (172250 bytes), 17810 de-duplicated (143885 bytes), 2979 trie nodes used
device 0xb8898770 has devpath '/devices/platform/thinkpad_acpi/input/input0/event0'
device 0xb88aa008 filled with db file data
device 0xb88acb40 has devpath '/devices/platform/thinkpad_acpi/input/input0'
device 0xb88acfb8 has devpath '/devices/platform/thinkpad_acpi'
device 0xb88ad1e0 has devpath '/devices/platform'
IMPORT builtin 'input_id' /usr/lib/udev/rules.d/50-udev-default.rules:10
capabilities/ev raw kernel attribute: 1
capabilities/abs raw kernel attribute: 0
capabilities/rel raw kernel attribute: 0
capabilities/key raw kernel attribute: 0
test_key: no EV_KEY capability
GROUP 97 /usr/lib/udev/rules.d/50-udev-default.rules:26
IMPORT builtin 'usb_id' /usr/lib/udev/rules.d/56-hpmud.rules:10
unable to access usb_interface device of '/sys/devices/platform/thinkpad_acpi/input/input0/event0'
IMPORT builtin 'usb_id' returned non-zero
IMPORT builtin 'path_id' /usr/lib/udev/rules.d/60-persistent-input.rules:31
LINK 'input/by-path/platform-thinkpad_acpi-event' /usr/lib/udev/rules.d/60-persistent-input.rules:36
device 0xb88acb40 filled with db file data
PROGRAM 'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input0/event0' /usr/lib/udev/rules.d/80-libinput-device-groups.rules:6
starting 'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input0/event0'
'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input0/event0'(out) 'thinkpad_acpi'
'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input0/event0' [801] exit with return code 0
device 0xb88a1ab8 has devpath '/devices/virtual/dmi/id'
value '[dmi/id]modalias' is 'dmi:bvnIBM:bvrINET24WW:bd05/24/1999:svnIBM:pn26458A0:pvrNotAvailable:rvnIBM:rn26458A0:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:'
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/90-libinput-model-quirks.rules:24
IMPORT builtin 'hwdb' returned non-zero
handling device node '/dev/input/event0', devnum=c13:64, mode=0660, uid=0, gid=97
preserve permissions /dev/input/event0, 020660, uid=0, gid=97
preserve already existing symlink '/dev/char/13:64' to '../input/event0'
found 'c13:64' claiming '/run/udev/links/\x2finput\x2fby-path\x2fplatform-thinkpad_acpi-event'
creating link '/dev/input/by-path/platform-thinkpad_acpi-event' to '/dev/input/event0'
preserve already existing symlink '/dev/input/by-path/platform-thinkpad_acpi-event' to '../event0'
created db file '/run/udev/data/c13:64' for '/devices/platform/thinkpad_acpi/input/input0/event0'
ACTION=add
DEVLINKS=/dev/input/by-path/platform-thinkpad_acpi-event
DEVNAME=/dev/input/event0
DEVPATH=/devices/platform/thinkpad_acpi/input/input0/event0
ID_INPUT=1
ID_PATH=platform-thinkpad_acpi
ID_PATH_TAG=platform-thinkpad_acpi
LIBINPUT_DEVICE_GROUP=thinkpad_acpi
MAJOR=13
MINOR=64
SUBSYSTEM=input
TAGS=:power-switch:
USEC_INITIALIZED=614468
Unload module index
Unloaded link configuration context.
[root@wishthinkpad andrzejl]#

Beside the error messages I've noticed that the system (which never was super fast to begin with - its a Pentium 2 machine) is slightly more sluggish then normally.

Later today I will upgrade it again and I will provide the same commands for the "broken" system.

Cheers.

Andrzej

Last edited by AndrzejL (2015-06-23 17:18:54)

The worst thing about censorship is ██████ ██ ████ ████████████ and ██████ ███████ ███ ███████████.

Offline

#7 2015-06-23 10:16:06

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,896
Website

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

Andrzej, you have already been asked to do this, but please use code tags, not quote tags. Please fix your posts.

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#8 2015-06-23 11:58:05

archex
Member
Registered: 2010-08-13
Posts: 4

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

I just installed a fresh arch this night and get the same message directly after GRUB...

Also I have no network connection until I manually start dhcpd. I don't know if this is connected.

Offline

#9 2015-06-23 12:04:09

ntruessel
Member
Registered: 2015-06-23
Posts: 1

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

AndrzejL wrote:

(...)
Noticed this message right after the grub window disappeared:

Failed to get cgroup: no such file or directory.

(...)

I get the same error. This issue is already fixed upstream and I think we can safely ignore it.
Reference: https://github.com/systemd/systemd/issues/309

Offline

#10 2015-06-23 13:09:14

mauritiusdadd
Member
From: Benevento, Italy
Registered: 2013-10-27
Posts: 776

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

@ntruessel: nice catch!

@archex: your issue has nothing to do with the cgroup message which is totally harmless. Please, read this article of the wiki and if you still have problems then start a new thread. https://wiki.archlinux.org/index.php/Ne … figuration

Last edited by mauritiusdadd (2015-06-23 13:09:57)

About me - github

-- When you have eliminated the impossible, whatever remains, however improbable, must be the truth -- Spock | Sherlock Holmes

Offline

#11 2015-06-23 17:16:56

AndrzejL
Member
Registered: 2012-12-07
Posts: 160

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

WorMzy wrote:

Andrzej, you have already been asked to do this, but please use code tags, not quote tags. Please fix your posts.

It makes no sense but ok...

Command output from the terminal is not a code... Code is a code. Output from a command line is something that the command line "said" after a certain command was used. Quote tags make it much more readable too. Anyway. Just so there is no doubt - I am not arguing I am just saiyan. Your wish is my command. Fixing it right after I will add this post.

Cheers.

Andrzej

The worst thing about censorship is ██████ ██ ████ ████████████ and ██████ ███████ ███ ███████████.

Offline

#12 2015-06-23 17:53:27

AndrzejL
Member
Registered: 2012-12-07
Posts: 160

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

mauritiusdadd wrote:

Unfortunately I have no clue on what causes the cgroup error message.

AndrzejL wrote:
[root@wishthinkpad andrzejl]# ls /etc/udev/hwdb.d/
[root@wishthinkpad andrzejl]#

No custom rules.

Cheers.

Andrzej

Can you post the output of the following commands on the updated system?

uname -a
udevadm test /sys/class/input/event0

Also, apart the messages in the journal, do you have any actual problem with your system? Is there something not working?

Ok - I've upgraded - the messages in journal are back:

[root@wishthinkpad andrzejl]# journalctl -b -l -x --no-pager -p 1
-- Logs begin at Sat 2014-12-20 09:00:02 GMT, end at Tue 2015-06-23 18:49:54 IST. --
Failed to get journal fields: Cannot assign requested address
[root@wishthinkpad andrzejl]# journalctl -b -l -x --no-pager -p 2
-- Logs begin at Sat 2014-12-20 09:00:02 GMT, end at Tue 2015-06-23 18:49:54 IST. --
Failed to get journal fields: Cannot assign requested address
[root@wishthinkpad andrzejl]# journalctl -b -l -x --no-pager -p 3
-- Logs begin at Sat 2014-12-20 09:00:02 GMT, end at Tue 2015-06-23 18:49:54 IST. --
Jun 23 18:37:44 wishthinkpad.loc kernel: serial 00:03: unable to assign resources
Jun 23 18:37:53 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x1, key code 236): Invalid argument
Jun 23 18:37:53 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x2, key code 152): Invalid argument
Jun 23 18:37:53 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x3, key code 142): Invalid argument
Jun 23 18:37:53 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x4, key code 238): Invalid argument
Jun 23 18:37:53 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x6, key code 227): Invalid argument
Jun 23 18:37:53 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x7, key code 372): Invalid argument
Jun 23 18:37:53 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x8, key code 194): Invalid argument
Jun 23 18:37:53 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xb, key code 205): Invalid argument
Jun 23 18:37:56 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xf, key code 225): Invalid argument
Jun 23 18:37:56 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x10, key code 224): Invalid argument
Jun 23 18:37:56 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x11, key code 228): Invalid argument
Jun 23 18:37:56 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x13, key code 372): Invalid argument
Jun 23 18:37:56 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x14, key code 115): Invalid argument
Jun 23 18:37:56 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x15, key code 114): Invalid argument
Jun 23 18:37:56 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x16, key code 113): Invalid argument
Jun 23 18:37:56 wishthinkpad.loc systemd-udevd[357]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0x17, key code 148): Invalid argument
Jun 23 18:37:58 wishthinkpad.loc kernel: ACPI: Fatal opcode executed
Jun 23 18:37:59 wishthinkpad.loc kernel: piix4_smbus 0000:00:07.3: IBM system detected; this module may corrupt your serial eeprom! Refusing to load module!
[root@wishthinkpad andrzejl]#

And here is the info you've requested.

[root@wishthinkpad andrzejl]# uname -a
Linux wishthinkpad.loc 3.14.44-1-lts #1 SMP Sat Jun 6 20:44:29 CEST 2015 i686 GNU/Linux
[root@wishthinkpad andrzejl]# udevadm test /sys/class/input/event0
calling: test
version 221
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

=== trie on-disk ===
tool version:          221
file size:         6998814 bytes
header size             80 bytes
strings            1754406 bytes
nodes              5244328 bytes
Load module index
timestamp of '/etc/systemd/network' changed
timestamp of '/usr/lib/systemd/network' changed
Parsed configuration file /usr/lib/systemd/network/99-default.link
Created link configuration context.
timestamp of '/etc/udev/rules.d' changed
timestamp of '/usr/lib/udev/rules.d' changed
Reading rules file: /usr/lib/udev/rules.d/10-dm.rules
Reading rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
Reading rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
Reading rules file: /usr/lib/udev/rules.d/39-usbmuxd.rules
Reading rules file: /usr/lib/udev/rules.d/40-gphoto.rules
Reading rules file: /usr/lib/udev/rules.d/40-hpet-permissions.rules
Reading rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
Reading rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
Reading rules file: /usr/lib/udev/rules.d/49-sane.rules
Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules
Reading rules file: /usr/lib/udev/rules.d/56-hpmud.rules
Reading rules file: /usr/lib/udev/rules.d/60-block.rules
Reading rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
Reading rules file: /usr/lib/udev/rules.d/60-drm.rules
Reading rules file: /usr/lib/udev/rules.d/60-evdev.rules
Reading rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
Reading rules file: /usr/lib/udev/rules.d/60-serial.rules
Reading rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
Reading rules file: /usr/lib/udev/rules.d/61-kde-bluetooth-rfkill.rules
Reading rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
Reading rules file: /usr/lib/udev/rules.d/64-btrfs.rules
Reading rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
Reading rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
Reading rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
Reading rules file: /usr/lib/udev/rules.d/69-libftdi.rules
Reading rules file: /usr/lib/udev/rules.d/69-libmtp.rules
Reading rules file: /usr/lib/udev/rules.d/70-infrared.rules
Reading rules file: /usr/lib/udev/rules.d/70-mouse.rules
Reading rules file: /etc/udev/rules.d/70-persistent-net.rules
Reading rules file: /usr/lib/udev/rules.d/70-power-switch.rules
Reading rules file: /usr/lib/udev/rules.d/70-touchpad.rules
Reading rules file: /usr/lib/udev/rules.d/70-uaccess.rules
Reading rules file: /etc/udev/rules.d/71-persistent-net.rules
Reading rules file: /usr/lib/udev/rules.d/71-seat.rules
Reading rules file: /usr/lib/udev/rules.d/73-seat-late.rules
Reading rules file: /usr/lib/udev/rules.d/75-net-description.rules
Reading rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-cinterion-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-ericsson-mbm.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-huawei-net-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-longcheer-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-mtk-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-nokia-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-pcmcia-device-blacklist.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-platform-serial-whitelist.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-simtech-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-telit-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-usb-device-blacklist.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-usb-serial-adapters-greylist.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-x22x-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-zte-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-nm-olpc-mesh.rules
Reading rules file: /usr/lib/udev/rules.d/78-sound-card.rules
Reading rules file: /usr/lib/udev/rules.d/80-drivers.rules
Reading rules file: /usr/lib/udev/rules.d/80-libinput-device-groups.rules
Reading rules file: /usr/lib/udev/rules.d/80-mm-candidate.rules
Reading rules file: /usr/lib/udev/rules.d/80-net-setup-link.rules
Reading rules file: /usr/lib/udev/rules.d/80-udisks.rules
Reading rules file: /usr/lib/udev/rules.d/80-udisks2.rules
Reading rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
Reading rules file: /usr/lib/udev/rules.d/90-libinput-model-quirks.rules
Reading rules file: /usr/lib/udev/rules.d/90-pulseaudio.rules
Reading rules file: /usr/lib/udev/rules.d/90-vconsole.rules
Reading rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
Reading rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
Reading rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
Reading rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
Reading rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
Reading rules file: /usr/lib/udev/rules.d/99-systemd.rules
rules contain 393216 bytes tokens (32768 * 12 bytes), 31246 bytes strings
20788 strings (172163 bytes), 17811 de-duplicated (143895 bytes), 2978 trie nodes used
IMPORT builtin 'input_id' /usr/lib/udev/rules.d/50-udev-default.rules:14
capabilities/ev raw kernel attribute: 1
capabilities/abs raw kernel attribute: 0
capabilities/rel raw kernel attribute: 0
capabilities/key raw kernel attribute: 0
properties raw kernel attribute: 0
test_key: no EV_KEY capability
GROUP 97 /usr/lib/udev/rules.d/50-udev-default.rules:30
IMPORT builtin 'usb_id' /usr/lib/udev/rules.d/56-hpmud.rules:10
unable to access usb_interface device of '/sys/devices/platform/thinkpad_acpi/input/input0/event0'
IMPORT builtin 'usb_id' returned non-zero
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/60-evdev.rules:8
IMPORT builtin 'hwdb' returned non-zero
value '[dmi/id]modalias' is 'dmi:bvnIBM:bvrINET24WW:bd05/24/1999:svnIBM:pn26458A0:pvrNotAvailable:rvnIBM:rn26458A0:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:'
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/60-evdev.rules:17
RUN 'keyboard' /usr/lib/udev/rules.d/60-evdev.rules:17
IMPORT builtin 'path_id' /usr/lib/udev/rules.d/60-persistent-input.rules:31
LINK 'input/by-path/platform-thinkpad_acpi-event' /usr/lib/udev/rules.d/60-persistent-input.rules:36
PROGRAM 'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input0/event0' /usr/lib/udev/rules.d/80-libinput-device-groups.rules:6
starting 'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input0/event0'
'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input0/event0'(out) 'thinkpad_acpi'
Process 'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input0/event0' succeeded.
value '[dmi/id]modalias' is 'dmi:bvnIBM:bvrINET24WW:bd05/24/1999:svnIBM:pn26458A0:pvrNotAvailable:rvnIBM:rn26458A0:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:'
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/90-libinput-model-quirks.rules:24
IMPORT builtin 'hwdb' returned non-zero
handling device node '/dev/input/event0', devnum=c13:64, mode=0660, uid=0, gid=97
preserve permissions /dev/input/event0, 020660, uid=0, gid=97
preserve already existing symlink '/dev/char/13:64' to '../input/event0'
found 'c13:64' claiming '/run/udev/links/\x2finput\x2fby-path\x2fplatform-thinkpad_acpi-event'
creating link '/dev/input/by-path/platform-thinkpad_acpi-event' to '/dev/input/event0'
preserve already existing symlink '/dev/input/by-path/platform-thinkpad_acpi-event' to '../event0'
created db file '/run/udev/data/c13:64' for '/devices/platform/thinkpad_acpi/input/input0/event0'
ACTION=add
DEVLINKS=/dev/input/by-path/platform-thinkpad_acpi-event
DEVNAME=/dev/input/event0
DEVPATH=/devices/platform/thinkpad_acpi/input/input0/event0
ID_INPUT=1
ID_PATH=platform-thinkpad_acpi
ID_PATH_TAG=platform-thinkpad_acpi
KEYBOARD_KEY_01=battery
KEYBOARD_KEY_02=screenlock
KEYBOARD_KEY_03=sleep
KEYBOARD_KEY_04=wlan
KEYBOARD_KEY_06=switchvideomode
KEYBOARD_KEY_07=zoom
KEYBOARD_KEY_08=f24
KEYBOARD_KEY_0b=suspend
KEYBOARD_KEY_0f=brightnessup
KEYBOARD_KEY_10=brightnessdown
KEYBOARD_KEY_11=kbdillumtoggle
KEYBOARD_KEY_13=zoom
KEYBOARD_KEY_14=volumeup
KEYBOARD_KEY_15=volumedown
KEYBOARD_KEY_16=mute
KEYBOARD_KEY_17=prog1
LIBINPUT_DEVICE_GROUP=thinkpad_acpi
MAJOR=13
MINOR=64
SUBSYSTEM=input
TAGS=:power-switch:
USEC_INITIALIZED=33572649
run: 'keyboard'
Unload module index
Unloaded link configuration context.
[root@wishthinkpad andrzejl]#

Cheers.

Andrzej

P.S. I cannot use the most recent kernels and have to stick to lts on this machine... possibly its time to downgrade and chmod -x pacman wink.

The worst thing about censorship is ██████ ██ ████ ████████████ and ██████ ███████ ███ ███████████.

Offline

#13 2015-06-23 18:37:30

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,896
Website

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

AndrzejL wrote:

It makes no sense but ok...

Command output from the terminal is not a code... Code is a code. Output from a command line is something that the command line "said" after a certain command was used.

I can see where you're coming from, but the benefits of using code tags over quote tags are a) code tags use a monospaced font, which preserves the formatting (and whitespace) of terminal output and makes it (and config files) much easier to parse, and b) code tag boxes scroll after a certain number of lines or characters, preventing vertical page stretching and word-wrapping. If in doubt, use quotes for people, and code tags for computers.

Thank you for changing your posts. While you may not appreciate the difference it makes, I and (I suspect) a large proportion of the other forum users do.

/off-topic

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#14 2015-06-23 18:46:51

mauritiusdadd
Member
From: Benevento, Italy
Registered: 2013-10-27
Posts: 776

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

AndrzejL wrote:
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/60-evdev.rules:17
RUN 'keyboard' /usr/lib/udev/rules.d/60-evdev.rules:17

This is the problem, it seems that with the new hwdb ABI, udev invokes /usr/lib/udev/rules.d/60-evdev.rules for /sys/class/input/event0 which wrongly applies the keyboard mapping rules defined in /lib/udev/hwdb.d/60-keyboard.hwdb.

# thinkpad_acpi driver
evdev:name:ThinkPad Extra Buttons:dmi:bvn*:bvr*:bd*:svnIBM*:pn*:pvr*
 KEYBOARD_KEY_01=battery                                # Fn+F2
 KEYBOARD_KEY_02=screenlock                             # Fn+F3
 KEYBOARD_KEY_03=sleep                                  # Fn+F4
 KEYBOARD_KEY_04=wlan                                   # Fn+F5
 KEYBOARD_KEY_06=switchvideomode                        # Fn+F7
 KEYBOARD_KEY_07=zoom                                   # Fn+F8 screen expand
 KEYBOARD_KEY_08=f24                                    # Fn+F9 undock
 KEYBOARD_KEY_0b=suspend                                # Fn+F12
 KEYBOARD_KEY_0f=brightnessup                           # Fn+Home
 KEYBOARD_KEY_10=brightnessdown                         # Fn+End
 KEYBOARD_KEY_11=kbdillumtoggle                         # Fn+PgUp - ThinkLight
 KEYBOARD_KEY_13=zoom                                   # Fn+Space
 KEYBOARD_KEY_14=volumeup
 KEYBOARD_KEY_15=volumedown
 KEYBOARD_KEY_16=mute
 KEYBOARD_KEY_17=prog1                                  # ThinkPad/ThinkVantage button (high keycode: "vendor")

but event0 is not a keyboard but it is your power switch. I think you should file a report for systemd.

Meanwhile you can try to see if it works if you edit the file /usr/lib/udev/rules.d/60-evdev.rules and replace these line

# device matching the input device name and the machine's DMI data
KERNELS=="input*", IMPORT{builtin}="hwdb 'evdev:name:$attr{name}:$attr{[dmi/id]modalias}'", \
  RUN{builtin}+="keyboard", GOTO="evdev_end"

with these ones

# device matching the input device name and the machine's DMI data
ENV{ID_INPUT_KEY}=="?*", KERNELS=="input*", IMPORT{builtin}="hwdb 'evdev:name:$attr{name}:$attr{[dmi/id]modalias}'", \
  RUN{builtin}+="keyboard", GOTO="evdev_end"

Last edited by mauritiusdadd (2015-06-23 18:47:31)

About me - github

-- When you have eliminated the impossible, whatever remains, however improbable, must be the truth -- Spock | Sherlock Holmes

Offline

#15 2015-06-23 19:05:00

AndrzejL
Member
Registered: 2012-12-07
Posts: 160

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

WorMzy wrote:
AndrzejL wrote:

It makes no sense but ok...

Command output from the terminal is not a code... Code is a code. Output from a command line is something that the command line "said" after a certain command was used.

I can see where you're coming from, but the benefits of using code tags over quote tags are a) code tags use a monospaced font, which preserves the formatting (and whitespace) of terminal output and makes it (and config files) much easier to parse, and b) code tag boxes scroll after a certain number of lines or characters, preventing vertical page stretching and word-wrapping. If in doubt, use quotes for people, and code tags for computers.

Thank you for changing your posts. While you may not appreciate the difference it makes, I and (I suspect) a large proportion of the other forum users do.

/off-topic

Ugh... Polite response full of useful information... Am I in the wrong place? smile /me Looks around...

Sorry couldn't help it wink.

Thanks for the info.

Andrzej

The worst thing about censorship is ██████ ██ ████ ████████████ and ██████ ███████ ███ ███████████.

Offline

#16 2015-06-23 19:08:14

AndrzejL
Member
Registered: 2012-12-07
Posts: 160

Re: [SOLVED] Odd messages at boot / in journal after systemd 221-1 upgrade

mauritiusdadd wrote:
AndrzejL wrote:
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/60-evdev.rules:17
RUN 'keyboard' /usr/lib/udev/rules.d/60-evdev.rules:17

This is the problem, it seems that with the new hwdb ABI, udev invokes /usr/lib/udev/rules.d/60-evdev.rules for /sys/class/input/event0 which wrongly applies the keyboard mapping rules defined in /lib/udev/hwdb.d/60-keyboard.hwdb.

# thinkpad_acpi driver
evdev:name:ThinkPad Extra Buttons:dmi:bvn*:bvr*:bd*:svnIBM*:pn*:pvr*
 KEYBOARD_KEY_01=battery                                # Fn+F2
 KEYBOARD_KEY_02=screenlock                             # Fn+F3
 KEYBOARD_KEY_03=sleep                                  # Fn+F4
 KEYBOARD_KEY_04=wlan                                   # Fn+F5
 KEYBOARD_KEY_06=switchvideomode                        # Fn+F7
 KEYBOARD_KEY_07=zoom                                   # Fn+F8 screen expand
 KEYBOARD_KEY_08=f24                                    # Fn+F9 undock
 KEYBOARD_KEY_0b=suspend                                # Fn+F12
 KEYBOARD_KEY_0f=brightnessup                           # Fn+Home
 KEYBOARD_KEY_10=brightnessdown                         # Fn+End
 KEYBOARD_KEY_11=kbdillumtoggle                         # Fn+PgUp - ThinkLight
 KEYBOARD_KEY_13=zoom                                   # Fn+Space
 KEYBOARD_KEY_14=volumeup
 KEYBOARD_KEY_15=volumedown
 KEYBOARD_KEY_16=mute
 KEYBOARD_KEY_17=prog1                                  # ThinkPad/ThinkVantage button (high keycode: "vendor")

but event0 is not a keyboard but it is your power switch. I think you should file a report for systemd.

Meanwhile you can try to see if it works if you edit the file /usr/lib/udev/rules.d/60-evdev.rules and replace these line

# device matching the input device name and the machine's DMI data
KERNELS=="input*", IMPORT{builtin}="hwdb 'evdev:name:$attr{name}:$attr{[dmi/id]modalias}'", \
  RUN{builtin}+="keyboard", GOTO="evdev_end"

with these ones

# device matching the input device name and the machine's DMI data
ENV{ID_INPUT_KEY}=="?*", KERNELS=="input*", IMPORT{builtin}="hwdb 'evdev:name:$attr{name}:$attr{[dmi/id]modalias}'", \
  RUN{builtin}+="keyboard", GOTO="evdev_end"

So that worked...

[root@wishthinkpad andrzejl]# cat /usr/lib/udev/rules.d/60-evdev.rules
# do not edit this file, it will be overwritten on update

ACTION=="remove", GOTO="evdev_end"
KERNEL!="event*", GOTO="evdev_end"

# skip later rules when we find something for this input device
IMPORT{builtin}="hwdb --subsystem=input --lookup-prefix=evdev:", \
  RUN{builtin}+="keyboard", GOTO="evdev_end"

# AT keyboard matching by the machine's DMI data
ENV{ID_INPUT_KEY}=="?*", DRIVERS=="atkbd", \
  IMPORT{builtin}="hwdb 'evdev:atkbd:$attr{[dmi/id]modalias}'", \
  RUN{builtin}+="keyboard", GOTO="evdev_end"

# device matching the input device name and the machine's DMI data
#KERNELS=="input*", IMPORT{builtin}="hwdb 'evdev:name:$attr{name}:$attr{[dmi/id]modalias}'", \
#  RUN{builtin}+="keyboard", GOTO="evdev_end"

# device matching the input device name and the machine's DMI data
ENV{ID_INPUT_KEY}=="?*", KERNELS=="input*", IMPORT{builtin}="hwdb 'evdev:name:$attr{name}:$attr{[dmi/id]modalias}'", \
  RUN{builtin}+="keyboard", GOTO="evdev_end"

LABEL="evdev_end"
[root@wishthinkpad andrzejl]# journalctl -b -l -x --no-pager -p 3
-- Logs begin at Sat 2014-12-20 09:00:02 GMT, end at Tue 2015-06-23 20:07:04 IST. --
Jun 23 20:04:36 wishthinkpad.loc kernel: serial 00:03: unable to assign resources
Jun 23 20:04:50 wishthinkpad.loc kernel: ACPI: Fatal opcode executed
Jun 23 20:04:50 wishthinkpad.loc kernel: piix4_smbus 0000:00:07.3: IBM system detected; this module may corrupt your serial eeprom! Refusing to load module!
[root@wishthinkpad andrzejl]#

I will try reporting it.

Thanks a lot!

Andrzej

The worst thing about censorship is ██████ ██ ████ ████████████ and ██████ ███████ ███ ███████████.

Offline

Pages: 1

Board footer

Powered by FluxBB