From owner-freebsd-stable Fri Jun 8 14:38:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from guardian.hermes.si (guardian.hermes.si [193.77.5.150]) by hub.freebsd.org (Postfix) with ESMTP id 9EFBA37B411 for ; Fri, 8 Jun 2001 14:38:29 -0700 (PDT) (envelope-from mitja@lamu.hermes.si) Received: from hermes.si (primus.hermes.si [193.77.5.98]) by guardian.hermes.si (8.9.3/8.9.3) with ESMTP id XAA02057 for ; Fri, 8 Jun 2001 23:38:26 +0200 (METDST) Received: (from root@localhost) by hermes.si (8.9.3/8.9.3) id XAA25616 for ; Fri, 8 Jun 2001 23:38:25 +0200 Received: from lamu.hermes.si (lamu.hermes.si [10.17.1.230]) by hermes.si (8.9.3/8.9.3) with ESMTP id XAA25530; Fri, 8 Jun 2001 23:38:24 +0200 Received: by lamu.hermes.si (8.11.3/8.9.3) id f58LdwA00746; Fri, 8 Jun 2001 23:39:58 +0200 (CEST) Message-Id: <200106082139.f58LdwA00746@lamu.hermes.si> Content-Type: text/plain; charset="iso-8859-1" From: Mitja Horvat Organization: Hermes SoftLab To: David Malone Subject: Re: 3Com 3c905B related kernel panic Date: Fri, 8 Jun 2001 23:39:57 +0200 X-Mailer: KMail [version 1.2.2] Cc: freebsd-stable@FreeBSD.ORG References: <200106061550.f56FomJ00618@lamu.hermes.si> <20010606172405.A57743@walton.maths.tcd.ie> In-Reply-To: <20010606172405.A57743@walton.maths.tcd.ie> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, > The commit was allowing oversized frames so that VLAN tagged frames > could get through. From the commit message it sounds like something > on your network may be sending big frames. Bill Paul would be the > best person to talk to about this - make sure you include all the > info you have about the problem if you send him a message. I contacted Bill and sent him additional information. Strangely, I cannot reproduce the problem since I cvsupped today, so I guess it was related to some other part of the kernel code or some kind of hardware conflict. Anyway, thank you for your help. Best regards, Mitja. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message