From owner-freebsd-bugs Sun Jun 28 19:00:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16013 for freebsd-bugs-outgoing; Sun, 28 Jun 1998 19:00:55 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15998 for ; Sun, 28 Jun 1998 19:00:48 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id TAA16243; Sun, 28 Jun 1998 19:00:02 -0700 (PDT) Date: Sun, 28 Jun 1998 19:00:02 -0700 (PDT) Message-Id: <199806290200.TAA16243@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Kevin Day Subject: kern/6059: Close me Reply-To: Kevin Day Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/6059; it has been noted by GNATS. From: Kevin Day To: freebsd-gnats-submit@freebsd.org Cc: Subject: kern/6059: Close me Date: Sun, 28 Jun 1998 20:52:36 -0500 (CDT) This PR can be closed, if desired. I can't duplicate it here on 2.2.6, and the machine in question was a 2.2. It may have been entirely coincidental, as well. I have seen all sorts of weird 'cannot allocate llinfo' messages though, so perhaps there's a greater problem. I've seen it complain that it can't allocate llinfo for an IP that's bound to the machine itself, and i've seen it complain about garbage.. (i.e. cannot allocate llinfo for: 204.137.237.254rt@@@@@@@ is in my log right now...) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message