From owner-freebsd-current Wed Mar 22 14: 1:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4990037C2A1 for ; Wed, 22 Mar 2000 14:01:49 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA29964; Wed, 22 Mar 2000 15:01:47 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA33948; Wed, 22 Mar 2000 15:01:46 -0700 (MST) Message-Id: <200003222201.PAA33948@harmony.village.org> To: "Ilmar S. Habibulin" Subject: Re: -current sudden panics :( Cc: Nikolai Saoukh , Yoshinobu Inoue , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Mar 2000 08:15:39 +0300." References: Date: Wed, 22 Mar 2000 15:01:46 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Ilmar S. Habibulin" writes: : This is driver for ed(ne2000) cards. I have realtek(rl driver). I took a : look at his source and didn't find such strings. There is comment there : about cutting off mbuf header before passing it to ether_input - what's : this? I applied a similar patch to the end of the rl packet handling routine. It didn't solve my arp crashes, however. It is almost as if sometimes the rl driver passes a packet to ether_input and then does bad things to it behind the scenes... I've not had a lot of time to try to track down why this does what it does. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message