I would boot with init=3D/bin/sh, then run `exec strace -D -o /var/log/systemd.trace /lib/systemd/systemd` to get a trace, and see if the EINVAL actually comes from calling close_range() or from something else. --=20 Mantas Mikul=C4=97nas --000000000000f0fa8805d95543d5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">On Thu, Mar 3, 2022 at 9:09 PM Christophe= r Obbard <<a href=3D"mailto:chris.obbard@xxxxxxxxxxxxx">chris.obbard@col= labora.com</a>> wrote:<br></div><div class=3D"gmail_quote"><blockquote c= lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli= d rgb(204,204,204);padding-left:1ex">Hi systemd experts!<br> <br> I am using systemd-247 and systemd-250 on debian system, which is <br> running a minimal downstream 5.4 kernel for a Qualcomm board.<br> <br> systemd 241 in debian buster works fine, but systemd 247 (debian <br> bullseye) and systemd 250 (debian unstable) seem to get upset about file <b= r> descriptors on services. These errors are consistant and the board boots <b= r> just fine with init=3D/bin/sh<br> <br> I've got the required kernel config from README in my kernel, I am usin= g <br> a heavily patched downstream kernel, but from the following log can you <br= > suggest anything I can do to debug this (other than throwing the board <br> out of the window) ?<br></blockquote><div><br></div><div>From the message, = it looks like the error is returned by close_all_fds() in src/basic/fd-util= .c, where the only major change is that it has been ported to call close_ra= nge() if that's available...</div><div><br></div><div>I would boot with= init=3D/bin/sh, then run `exec strace -D -o /var/log/systemd.trace /lib/sy= stemd/systemd` to get a trace, and see if the EINVAL actually comes from ca= lling=C2=A0close_range() or from something else.</div></div><div><br></div>= -- <br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Mantas M= ikul=C4=97nas</div></div></div> --000000000000f0fa8805d95543d5--