[SOLVED] Many systemd-udevd scheduler errors in log

Maniaxx · 2019-04-01 23:53:32

There's a massive count of red errors polluting my bootlog. How can i fix this?

$ journalctl -b
[...]
Apr 02 01:28:51 user systemd[1]: Started udev Kernel Device Manager.
Apr 02 01:28:51 user systemd-udevd[316]: acpi: Failed to open ATTR{/sys/bus/acpi/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[316]: button: Failed to open ATTR{/sys/bus/acpi/drivers/button/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[317]: cec: Failed to open ATTR{/sys/bus/cec/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[318]: ec: Failed to open ATTR{/sys/bus/acpi/drivers/ec/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[319]: hardware_error_device: Failed to open ATTR{/sys/bus/acpi/drivers/hardware_error_device/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[321]: processor_aggregator: Failed to open ATTR{/sys/bus/acpi/drivers/processor_aggregator/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[322]: thermal: Failed to open ATTR{/sys/bus/acpi/drivers/thermal/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[323]: video: Failed to open ATTR{/sys/bus/acpi/drivers/video/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[316]: container: Failed to open ATTR{/sys/bus/container/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[318]: cpu: Failed to open ATTR{/sys/bus/cpu/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[317]: event_source: Failed to open ATTR{/sys/bus/event_source/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[316]: gpio: Failed to open ATTR{/sys/bus/gpio/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[318]: processor: Failed to open ATTR{/sys/bus/cpu/drivers/processor/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[321]: edac: Failed to open ATTR{/sys/bus/edac/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[324]: clockevents: Failed to open ATTR{/sys/bus/clockevents/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[322]: firewire: Failed to open ATTR{/sys/bus/firewire/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[323]: genpd: Failed to open ATTR{/sys/bus/genpd/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[319]: clocksource: Failed to open ATTR{/sys/bus/clocksource/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[316]: i2c: Failed to open ATTR{/sys/bus/i2c/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[316]: WM8400: Failed to open ATTR{/sys/bus/i2c/drivers/WM8400/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[318]: aat2870: Failed to open ATTR{/sys/bus/i2c/drivers/aat2870/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[324]: 88PM860x: Failed to open ATTR{/sys/bus/i2c/drivers/88PM860x/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[320]: hpet: Failed to open ATTR{/sys/bus/acpi/drivers/hpet/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[322]: as3711: Failed to open ATTR{/sys/bus/i2c/drivers/as3711/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[317]: adp5520: Failed to open ATTR{/sys/bus/i2c/drivers/adp5520/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[316]: da903x: Failed to open ATTR{/sys/bus/i2c/drivers/da903x/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[318]: da9052: Failed to open ATTR{/sys/bus/i2c/drivers/da9052/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[319]: CHT Whiskey Cove PMIC: Failed to open ATTR{/sys/bus/i2c/drivers/CHT Whiskey Cove PMIC/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[321]: ab3100: Failed to open ATTR{/sys/bus/i2c/drivers/ab3100/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[323]: da9055-pmic: Failed to open ATTR{/sys/bus/i2c/drivers/da9055-pmic/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[325]: hid: Failed to open ATTR{/sys/bus/hid/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[316]: intel_soc_pmic_i2c: Failed to open ATTR{/sys/bus/i2c/drivers/intel_soc_pmic_i2c/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[321]: max77843: Failed to open ATTR{/sys/bus/i2c/drivers/max77843/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[317]: max8997: Failed to open ATTR{/sys/bus/i2c/drivers/max8997/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[318]: max8925: Failed to open ATTR{/sys/bus/i2c/drivers/max8925/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[326]: dummy: Failed to open ATTR{/sys/bus/i2c/drivers/dummy/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[325]: hid-generic: Failed to open ATTR{/sys/bus/hid/drivers/hid-generic/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[320]: lp8788: Failed to open ATTR{/sys/bus/i2c/drivers/lp8788/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[324]: htcpld-chip: Failed to open ATTR{/sys/bus/i2c/drivers/htcpld-chip/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[319]: max77620: Failed to open ATTR{/sys/bus/i2c/drivers/max77620/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[325]: max8998: Failed to open ATTR{/sys/bus/i2c/drivers/max8998/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[324]: palmas: Failed to open ATTR{/sys/bus/i2c/drivers/palmas/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[319]: rc5t583: Failed to open ATTR{/sys/bus/i2c/drivers/rc5t583/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[321]: sx150x-pinctrl: Failed to open ATTR{/sys/bus/i2c/drivers/sx150x-pinctrl/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[317]: tps65090: Failed to open ATTR{/sys/bus/i2c/drivers/tps65090/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[316]: sec_pmic: Failed to open ATTR{/sys/bus/i2c/drivers/sec_pmic/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[326]: smsc: Failed to open ATTR{/sys/bus/i2c/drivers/smsc/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[320]: stmpe-i2c: Failed to open ATTR{/sys/bus/i2c/drivers/stmpe-i2c/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[318]: tc3589x: Failed to open ATTR{/sys/bus/i2c/drivers/tc3589x/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[324]: tps6586x: Failed to open ATTR{/sys/bus/i2c/drivers/tps6586x/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[319]: tps65910: Failed to open ATTR{/sys/bus/i2c/drivers/tps65910/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[321]: wm831x: Failed to open ATTR{/sys/bus/i2c/drivers/wm831x/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[317]: isa: Failed to open ATTR{/sys/bus/isa/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[318]: wm8350: Failed to open ATTR{/sys/bus/i2c/drivers/wm8350/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[316]: tps80031: Failed to open ATTR{/sys/bus/i2c/drivers/tps80031/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[322]: machinecheck: Failed to open ATTR{/sys/bus/machinecheck/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[323]: memory: Failed to open ATTR{/sys/bus/memory/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[325]: tps68470: Failed to open ATTR{/sys/bus/i2c/drivers/tps68470/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[326]: twl: Failed to open ATTR{/sys/bus/i2c/drivers/twl/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[320]: twl6040: Failed to open ATTR{/sys/bus/i2c/drivers/twl6040/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[328]: nd: Failed to open ATTR{/sys/bus/nd/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[319]: node: Failed to open ATTR{/sys/bus/node/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[330]: pci: Failed to open ATTR{/sys/bus/pci/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[329]: nvmem: Failed to open ATTR{/sys/bus/nvmem/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[331]: pci-epf: Failed to open ATTR{/sys/bus/pci-epf/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[317]: serial: Failed to open ATTR{/sys/bus/serial/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[318]: platform: Failed to open ATTR{/sys/bus/platform/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[321]: pnp: Failed to open ATTR{/sys/bus/pnp/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[326]: pci_express: Failed to open ATTR{/sys/bus/pci_express/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[324]: scsi: Failed to open ATTR{/sys/bus/scsi/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[332]: serio: Failed to open ATTR{/sys/bus/serio/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[323]: usb-serial: Failed to open ATTR{/sys/bus/usb-serial/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[316]: usb: Failed to open ATTR{/sys/bus/usb/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[329]: basic-mmio-gpio: Failed to open ATTR{/sys/bus/platform/drivers/basic-mmio-gpio/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[325]: alarmtimer: Failed to open ATTR{/sys/bus/platform/drivers/alarmtimer/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[318]: acpi-fan: Failed to open ATTR{/sys/bus/platform/drivers/acpi-fan/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[322]: as3722-power-off: Failed to open ATTR{/sys/bus/platform/drivers/as3722-power-off/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[320]: axp288_pmic_acpi: Failed to open ATTR{/sys/bus/platform/drivers/axp288_pmic_acpi/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[333]: spi: Failed to open ATTR{/sys/bus/spi/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[319]: acpi-wmi: Failed to open ATTR{/sys/bus/platform/drivers/acpi-wmi/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[327]: mipi-dsi: Failed to open ATTR{/sys/bus/mipi-dsi/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[334]: broxton-pinctrl: Failed to open ATTR{/sys/bus/platform/drivers/broxton-pinctrl/queue/scheduler} for writing: No such file or directory
Apr 02 01:28:51 user systemd-udevd[338]: cdns-pcie-ep: Failed to open ATTR{/sys/bus/platform/drivers/cdns-pcie-ep/queue/scheduler} for writing: No such file or directory
[...]

Last edited by Maniaxx (2019-04-02 16:59:46)

V1del · 2019-04-02 06:48:29

Looks like you've set up an over eager udev rule to switch schedulers that matches on too much. If you didn't do anything like this yourself, is laptop-mode-tools or TLP or similar set up and how are they configured?

Maniaxx · 2019-04-02 16:19:31

Indeed. Its coming from improving_performance#Changing_I/O_scheduler.

# set scheduler for non-rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]|mmcblk[0-9]*|nvme[0-9]*", ATTR{queue/rotational}=="0", 
ATTR{queue/scheduler}="mq-deadline"
# set scheduler for rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1", ATTR{queue/scheduler}="bfq"

Any idea what's wrong here? I'm no expert in udev rules and don't know yet why this 'AND MATCHES' kick in everywhere.

Edit:
I'm wondering why 'queue/rotational' and 'queue/scheduler' are missing here. Looks like udevadm doesn't show up all ATTRS here:

$ udevadm info -a -p /sys/block/sda |grep queue
    ATTRS{queue_ramp_up_period}=="120000"
    ATTRS{queue_type}=="simple"
    ATTRS{queue_depth}=="32"

Edit2:
Solved, bad typo (line break). "ATTR{queue/scheduler}="mq-deadline" kicked in everywhere.
This one works properly (after 'udevadm control --reload-rules && udevadm trigger'):

# set scheduler for non-rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]|mmcblk[0-9]*|nvme[0-9]*", ATTR{queue/rotational}=="0", ATTR{queue/scheduler}="mq-deadline"
# set scheduler for rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1", ATTR{queue/scheduler}="bfq"

Thanks!

Last edited by Maniaxx (2019-04-02 17:04:57)

Arch Linux

#1 2019-04-01 23:53:32

[SOLVED] Many systemd-udevd scheduler errors in log

#2 2019-04-02 06:48:29

Re: [SOLVED] Many systemd-udevd scheduler errors in log

#3 2019-04-02 16:19:31

Re: [SOLVED] Many systemd-udevd scheduler errors in log

Board footer