HI On 6.5-current:
As I wrote @ 1:46 AM, it seems OK! But, I experiment some troubles on my connexion: - unwanted SSH disconnections - on X, with Firefox, tabs crashed always in same time. Perhaps, for Firefox, it's a problem with pledge? I see thoses messages in /var/log/messages - egual on 'dmesg': Jun 22 11:21:21 ptb-z /bsd: firefox[19999]: pledge "flock", syscall 92 Jun 22 11:21:21 ptb-z /bsd: firefox[17962]: pledge "flock", syscall 92 Jun 22 11:21:22 ptb-z /bsd: firefox[47501]: pledge "flock", syscall 92 (...) firefox[68021]: pledge "flock", syscall 92 firefox[22469]: pledge "flock", syscall 92 firefox[41244]: pledge "flock", syscall 92 ??? On 6/22/19 6:27 AM, Kevin Lo wrote: > On Fri, Jun 21, 2019 at 09:44:12PM +0200, Stephane HUC "PengouinBSD" wrote: >> HI, > Hi, > >> To communicate on Internet, with my laptop - a Dell Alienware 13 - I >> use an external LAN Adapter USB to RJ. This run correcty! >> >> I did not notice / understood that the physical network card was managed >> . >> >> $ grep alc0 dmesg.txt >> >> alc0 at pci2 dev 0 function 0 "Attansic Technology E2200" rev 0x10: >> msi, address 34:e6:d7:1b:7f:14 >> atphy0 at alc0 phy 0: AR8035 10/100/1000 PHY, rev. 9 >> >> But, if I configure inet and inet6 on hostname.alc0 file, either dhcp >> or static informations, dmesg filled with "alc0: watchdog timeout" and >> /var/log/messages grow up! >> >> Into /var/log/messages, as: >> Jun 21 16:13:26 ptb-aw13zou /bsd: alc0: watchdog timeout >> Jun 21 16:14:00 ptb-aw13zou /bsd: alc0: watchdog timeout >> Jun 21 16:15:56 ptb-aw13zou last message repeated 5 times >> Jun 21 16:25:39 ptb-aw13zou last message repeated 20 times >> Jun 21 16:35:34 ptb-aw13zou last message repeated 21 times >> Jun 21 16:45:57 ptb-aw13zou last message repeated 22 times >> Jun 21 16:55:56 ptb-aw13zou last message repeated 19 times >> Jun 21 17:05:46 ptb-aw13zou last message repeated 22 times >> Jun 21 17:15:37 ptb-aw13zou last message repeated 22 times >> Jun 21 17:25:30 ptb-aw13zou last message repeated 22 times >> Jun 21 17:27:54 ptb-aw13zou last message repeated 4 times >> >> With 'dhcp', the system reply: "no lease". >> >> Someone can explain-me the reason (simply), please?! >> (and, perhaps, found a solution…) > I think this bug has been fixed in r1.48. Please try -current, thanks. >
