Mine: openat(AT_FDCWD, "/dev/ipmi0", O_RDWR) = 3 <0.000052 Yours: openat(AT_FDCWD, "/dev/ipmi0", O_RDWR) = -1 EINVAL (Invalid argument) <0.000053>
So we are back at the kernel backend of this - on your particular hardware/firmware - not behaving correctly. This isn't one of the later ioctls, just the basic open fails. I re-checked my system and even a "cat /dev/ipmi0" while failing as expected eventually can open the device just fine (only fails later when reading) # strace -e openat cat /dev/ipmi0 2>&1|grep ipmi0 openat(AT_FDCWD, "/dev/ipmi0", O_RDONLY) = 3 So why isn't it "openable" in his case? @Kernel people, what would you want Ventsislav to look out for ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836701 Title: ubuntu18.04: ipmitool failed: Could not open device at /dev/ipmi0 : No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1836701/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
