Date: Sat, 8 Jun 1996 13:09:32 +1000 From: Bruce Evans <bde@zeta.org.au> To: davo@katy.apana.org.au, freebsd-bugs@freebsd.org, freebsd-hackers@freebsd.org Cc: sa-tech@tierzero.apana.org.au Subject: Re: Interface problem Message-ID: <199606080309.NAA15037@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>Hmmm, I've just noticed some errors showing in the system message >buffer that are not turning up in /var/log/messages at least >not in full. dmesg shows: >arpresolve: can't allocate llinfo >and 110 more lines the same :( >I only found two similar lines in /var/log/messages* >messages.1:May 30 00:50:19 pasa /kernel: ocate llinfo >messages.1:May 30 00:50:19 pasa /kernel: ocate llinfo It looks like the message buffer filled up. >Note, the machine has only been up 12 hours at the moment so the >current stuff shown in dmesg is not getting logged. Is there any >way of simulating tail -f `dmesg` :) It should get logged. >> > User ppp caused a problem at first with "device not configured" >> > sometimes and "can't find ifindex" at others. We got past that >> > one with some mods to the ppp code but yesterday, a cslip >> > connection failed rather strangely. Sliplogin worked ok and >> > configured the interface (sl8) but I could not get it to come >> > up. The SLIOCSUNIT ioctl is poorly implemented in 2.1R and -stable. It always allocates the specified unit even if this unit is in use or doesn't exist. Perhaps this causes some of your other problems. >Can anyone tell me why open(/dev/tun0) would return ENOXIO when >the device is in use? ENXIO. It just returned ENXIO when it should have returned EBUSY. This was recently fixed in -current. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606080309.NAA15037>