'devctl clear driver' shall not fail if no driver has been found

[saper_saper.info]

Summary

Detaching bhyve(4) ppt driver from the unsupported PCI device shall
not cause "Device not configured" error. We do not expect
that a new driver must take the device over in this case.

[saper_saper.info]

I was really confused by the wifibox messages like this

2025-08-04T11:35:14+0200 WARN  PPT device pci2:0:0 could not be destroyed
2025-08-04T11:35:20+0200 WARN  PPT device pci2:0:0 could not be destroyed
2025-08-04T11:35:27+0200 WARN  PPT device pci2:0:0 could not be destroyed
2025-08-04T11:35:34+0200 WARN  PPT device pci2:0:0 could not be destroyed
2025-08-04T11:35:40+0200 WARN  PPT device pci2:0:0 could not be destroyed
2025-08-04T11:35:47+0200 WARN  PPT device pci2:0:0 could not be destroyed
2025-08-04T11:35:54+0200 WARN  PPT device pci2:0:0 could not be destroyed
2025-08-04T11:36:00+0200 WARN  PPT device pci2:0:0 could not be destroyed

https://lists.freebsd.org/archives/freebsd-current/2025-August/008456.html

[imp]

sys/kern/subr_bus.c

5964–5975

yea, device_probe() is weird. It returns -1 in two cases, only one of which is relevant here (the DS_ALIVE one). I guess neither could happen getting here though, assuming that device_detach does the right thing.

[saper_saper.info]

Silence ENXIO from device_probe()

device_probe() will return ENXIO when no driver could be found.

[saper_saper.info]

As it turns out, we get ENXIO from device_probe() when no driver has been found.

With this change wifibox does not report any error anymore and it can be stopped and started multiple times.

I wonder how to test this with some other device, or whether devmatch works/does not work with this

[jhb]

lib/libdevctl/devctl.3

381

This I think already covers the behavior you are fixing as it says the error is only if attach fails, not if probe doesn't find a driver, so I would probably leave off the manpage update.

sys/kern/subr_bus.c

5964–5975

I think this needs a comment, something like:

devclass_delete_device(...);

/*
  * Don't use device_probe_and_attach so that failing to find a new driver
  * isn't reported as an error.
  */
error = device_probe(dev);

[saper_saper.info]

Added the comment code, updated the function description in the manpage
instead of an error code.

[saper_saper.info]

lib/libdevctl/devctl.3

381

you are right, I have moved it to the function description instead. The reason I'd like to update it is that I was trying to deduct if that behaviour is correct from the manpage, but I wasn't sure.

[saper_saper.info]

Whitespace fix

[jhb]

This looks good to me modulo one style nit I can fix while merging. Is "Marcin Cieslak <[e-mail]>" the right way to credit you as the author of the commit?