Re: kern/59253 (amdzentemp fails to register with sysmon)

[pgoyette%NetBSD.org@localhost]

Synopsis: amdzentemp fails to register with sysmon

Responsible-Changed-From-To: kern-bug-people->pgoyette
Responsible-Changed-By: pgoyette%NetBSD.org@localhost
Responsible-Changed-When: Thu, 10 Apr 2025 23:20:10 +0000
Responsible-Changed-Why:
it's mine


State-Changed-From-To: open->closed
State-Changed-By: pgoyette%NetBSD.org@localhost
State-Changed-When: Thu, 10 Apr 2025 23:20:10 +0000
State-Changed-Why:
Immediate problem resolved using existing /etc/rc.d mechanisms.  Long
term, we need a way for bus that is being rescanned to check if any of
it already-attached children have been "superseded" by a higher
priority match (which can happen with a newly-loading driver module).
If s higher-priority device driver is now available it may need to
evict the current driver (assuming the current driver allows itself to
be unloaded).