From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 07:09:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 785DC1065672; Wed, 3 Dec 2008 07:09:08 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from mail.consult-scs.com (MAIL.CONSULT-SCS.COM [208.81.60.67]) by mx1.freebsd.org (Postfix) with ESMTP id 5EEC18FC0A; Wed, 3 Dec 2008 07:09:08 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from [127.0.0.1] (host77.netvulture.com [208.201.244.77]) (Authenticated sender: vulture@netvulture.com) by mail.consult-scs.com (Postfix) with ESMTPA id 4F2DE1642485; Tue, 2 Dec 2008 23:09:46 -0800 (PST) Message-ID: <49363099.5040701@netvulture.com> Date: Tue, 02 Dec 2008 23:09:13 -0800 From: Jonathan Feally User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-stable@freebsd.org References: <4933A00E.7080201@netvulture.com> <4934C733.4020506@netvulture.com> <49357329.9000107@netvulture.com> <493587D4.5000400@netvulture.com> <4935FA57.6080106@netvulture.com> In-Reply-To: <4935FA57.6080106@netvulture.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SCS-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 4F2DE1642485.30571 X-SCS-MailScanner: Found to be clean X-SCS-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-204.399, required 4, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, INIT_RECVD_OUR_AUTH -200.00) X-SCS-MailScanner-From: vulture@netvulture.com Cc: Subject: Re: dhclient doing DISCOVER with bad IP checksum - compile optimization issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2008 07:09:08 -0000 Ok, I managed to cause it again. dhclient was the problem. My source tree was fine. Turns out that it is my make.conf CFLAGS=-O3 setting. When compiled with -O3 it will generate packets with bad checksums. Simply recompiling it with -O2 did not cause this issue and dhclient works fine. So the question becomes, what is happening with -O3 that is breaking it? So far I am not having any other issues with -O3 on the rest of the system. -Jon -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.