re: port-arm/56842

[Jim Spath <jspath55%gmail.com@localhost>]

The following reply was made to PR port-arm/56842; it has been noted by GNATS.

From: Jim Spath <jspath55%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: re: port-arm/56842
Date: Thu, 9 Jun 2022 09:42:42 -0400

 My original install sd card is now corrupt/suspect after a power cycle
 required fsck which then failed to recover some files.
 
 Looking back, I found errors related to the USB/ethernet adapter:
 
 May  3 10:50:38 n0b /netbsd: [ 58744.3697748] ure0: autoconfiguration
 error: watchdog timeout
 May  3 10:50:48 n0b /netbsd: [ 58754.3704177] ure0: autoconfiguration
 error: usb error on tx: TIMEOUT
 ...
 May  5 15:15:10 n0b dhcpcd[153]: ure0: dhcp_sendudp: Host is down
 May  5 15:15:10 n0b dhcpcd[153]: ure0: bpf_send: No buffer space available
 ...
 May 27 00:58:39 n0b dhcpcd[153]: ure0: bpf_send: No buffer space available
 ...
 Jun  4 21:25:03 n0b dhcpcd[260]: ure0: bpf_send: No buffer space available
 
 The first adapter:
 Jun  4 21:27:21 n0b /netbsd: [   7.0539144] ure0: Realtek (0xbda) USB
 10/100/1000 LAN (0x8153), rev 2.10/31.00, addr 4
 
 The second adapter:
 Jun  4 23:16:43 n0b /netbsd: [ 6554.5805440] ure0: Realtek (0xbda) USB
 10/100 LAN (0x8152), rev 2.10/20.00, addr 4
 
 I installed the same 9.2 stable image on a second Pi, with the same
 10/100 LAN adapter model. So far, no cron hangs on either. I will let
 the new system run for a few more days, then switch to the suspect
 adapter and see if the problem recurs. It seems feasible that network
 driver errors could be a root cause.
 
 Strangely, both adapter models say "Gigabit LAN" on the case, but the
 one that connected at 1000BT had errors, while the 100BT connection
 does not. And, the model that only connected at 100 works at 1000 on a
 PC.
 
 (apologies for missending this to gnats-admin first)