I am noticing when I issue a reboot command to the X440 it will sit at shutting down the usrp-hwd service for a while, usually with a 90 second timeout. After that, it usually doesn't even reboot for quite some time. Is this a known issue? Is there anything I can do to debug why usrp-hwd is stuck shutting down? Any idea why, even after it shuts down, the RFSoC doesn't want to reboot itself appropriately? Thanks, Brian

The 90 second timeout is a known issue, and it was recently fixed. With the next release, the USRP Hardware Daemon (MPM) service should shutdown immediately. But I'm not aware of it taking a long time after the service shuts down. In my experience, it reboots very quickly after the service shuts down. Wade On Thu, May 8, 2025 at 4:04 PM Brian Padalino <bpadalino@gmail.com> wrote: > I am noticing when I issue a reboot command to the X440 it will sit at > shutting down the usrp-hwd service for a while, usually with a 90 second > timeout. > > After that, it usually doesn't even reboot for quite some time. > > Is this a known issue? Is there anything I can do to debug why usrp-hwd is > stuck shutting down? Any idea why, even after it shuts down, the RFSoC > doesn't want to reboot itself appropriately? > > Thanks, > Brian > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com >

On Sat, May 10, 2025 at 11:33 PM Wade Fife <wade.fife@ettus.com> wrote: > The 90 second timeout is a known issue, and it was recently fixed. With > the next release, the USRP Hardware Daemon (MPM) service should shutdown > immediately. > > But I'm not aware of it taking a long time after the service shuts down. > In my experience, it reboots very quickly after the service shuts down. > Good to know that the 90 second timeout thing was fixed recently. I just tried it again myself and when I get the 90 second timeout, systemd-shutdown complains about: systemd-shutdown[1]: Failed to set timeout to 10min: Invalid argument ... after which my system doesn't reboot at all. It's been sitting here for a few hours with nothing on the console moving it forward. Any tips on how I can debug this? Does your system that reboots normally still have that 10min invalid argument thing? Note I am running the released 4.8.0.0 image. Thanks, Brian