Re: aarch64 (Windows Dev Kit 2023): "ure0: spurious link down (PHY link up), overriding" and umass WRITE(10)/READ(10) errors

On 4/23/26 10:13, Mark Millard wrote:
> On 4/23/26 08:27, bob prohaska wrote:
>> On Wed, Apr 22, 2026 at 11:11:10PM -0700, Mark Millard wrote:
>>> In recent times I've been seeing the following sort of sequence
>> retries remaining notices, I've only seen "3", never more or less.
>>>
>>
>> Very similar messages have been common on my Pi2 armv7 systems.
>> The "3 retries remaining" match is exact, memory isn't good
>> enough to confirm the rest. Generally, no other obvious trouble
>> has accompanied the messages (no repeatable crashes or panics).
> 
> The obvious trouble in my context is making some operations take much
> longer from the sum of all the activity-paused times. Other than the
> time consequences, things seem to have operated okay.
> 
>>
>> Thanks for writing!
>>
>> bob prohaska
>>
>>>
>>
>>
> 
> 

Based on the da*:umass-sim* messages . . .

I've looked up the /var/log/messages history and the first example was from:

FreeBSD 16.0-CURRENT main-n285028-2b954770ddd7 GENERIC-NODEBUG arm64
(Apr 13 Pacific Time)

previously, the kind of activities that are getting the messages did not
happen for:

FreeBSD 16.0-CURRENT main-n284677-769a6f803d1b GENERIC-NODEBUG arm64
(Mar 24 Pacific Time)

So 351 commits earlier. Between there was not much relevant activity: so
effectively untested.


As for having the message:

  ure0: spurious link down (PHY link up), overriding

being associated with the da*:umass-sim* messages, that was first
recorded under:

FreeBSD 16.0-CURRENT main-n285067-2d13620c6e1b GENERIC-NODEBUG arm64
(Apr 15 Pacific Time)


-- 
===
Mark Millard
marklmi at yahoo.com