From owner-freebsd-stable@FreeBSD.ORG Sun May 19 02:11:01 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C8CBE1ED for ; Sun, 19 May 2013 02:11:01 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:32]) by mx1.freebsd.org (Postfix) with ESMTP id 9711CEEC for ; Sun, 19 May 2013 02:11:01 +0000 (UTC) Received: from omta09.emeryville.ca.mail.comcast.net ([76.96.30.20]) by qmta03.emeryville.ca.mail.comcast.net with comcast id ddqX1l0090S2fkCA3eB1jl; Sun, 19 May 2013 02:11:01 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta09.emeryville.ca.mail.comcast.net with comcast id deB01l0091t3BNj8VeB03K; Sun, 19 May 2013 02:11:00 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 270B573A33; Sat, 18 May 2013 19:11:00 -0700 (PDT) Date: Sat, 18 May 2013 19:11:00 -0700 From: Jeremy Chadwick To: kpneal@pobox.com Subject: Re: Unexpected reboot/crash on 8.2-RELEASE. Message-ID: <20130519021100.GA19058@icarus.home.lan> References: <20130519014521.GA3841@neutralgood.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130519014521.GA3841@neutralgood.org> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1368929461; bh=kDHIWAraN/B1PhW9DZQz7QyH/UuWsQcMLRR1IX8o+9A=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=Hrngy/HUZd+byX3J3Rb+viPg7eD4r9EJhdmWg/WfHnP3ExesFBRTIZp2ImgE6cbkU EOY4Rl1RSvc5FSpRPTLI7hSp5DzURwwHRbImRtDZqruOfWkYbomcV6Hkv/pBcFBnXI OiXChVBJ+PsplGKjBeCxFRMKD7JfjPAGxNYk+/bXe/NXxmLfWbJOEcu9RjtBaTMo1B QrskSJCj5T/DGpXDhMFEVcOeXgfUkxIHVXKP4Qhv/AlIdFKjTjkTNbmu7P1z9fzcPh gdE4p0EwoUwrWJCjT7rd3yhjXoB2kXmo8+6HhqQKnuJCiG0S0WWrIRMIfFwzSLUBwf eyormUGFfNTYg== Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 May 2013 02:11:01 -0000 On Sat, May 18, 2013 at 09:45:21PM -0400, kpneal@pobox.com wrote: > I had an unexpected reboot of my Dell R610 today around 2:05-06pm today. > I do not know if it crashed or if it was power cycled. > > This machine is running: > FreeBSD gunsight1.neutralgood.org 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Thu Dec 8 21:58:59 UTC 2011 root@:/usr/obj/usr/src/sys/GENERIC amd64 > > It's a stock 8.2-RELEASE kernel except I had to tweak it near the top of > vfs_mountroot() to delay before attempting to mount the root filesystem. > (Without my tweak it attempts to mount root before the USB drive is finished > getting attached.) > > The dmesg shows this at the reboot: > mfi0: 24272 (422106527s/0x0020/info) - Patrol Read complete > mfi0: 24273 (422172000s/0x0020/info) - Patrol Read started > mfi0: 24318 (422192750s/0x0020/info) - Patrol Read complete > mfi0: 24319 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028) > mfi0: 24320 (boot + 3s/0x0020/info) - Firmware version 1.22.12-0952 > mfi0: 24321 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028) > mfi0: 24322 (boot + 3s/0x0020/info) - Firmware version 1.22.12-0952 > > Does this mean the machine did not lose power? I ask because my datacenter > had some sort of power incident and I'm not sure if the server lost power > or not. But if the kernel message buffer from before the incident is still > present then the machine never lost power, correct? The datacenter's power > incident I'm told happened somewhere around the time of the reboot so I > have to ask. > > It looks like I didn't have dumps enabled. That's ... not helpful. > > The machine has been stable for: > 2:05PM up 472 days, 21 mins, 7 users, load averages: 0.01, 0.02, 0.00 > > http://www.neutralgood.org/~kpn/dmesg.boot > > Here's various stats I usually keep displayed. This is the last from > before the reboot: > http://www.neutralgood.org/~kpn/status.txt Your system did not reboot nor did it crash. If it did, your uptime would not be showing 472 days.. Really, it's that simple. > I've got all the power savings features turned off in the BIOS and, like > I said, the machine has been stable for all this time. However, one thing > to note from a couple of days ago: > > May 14 00:49:13 gunsight1 -- MARK -- > May 14 01:00:45 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 35 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 65 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 95 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 125 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 155 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 185 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 215 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 245 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 275 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 305 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 335 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 365 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 395 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 425 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 455 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 485 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 515 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 545 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 575 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 605 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 635 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 665 SECONDS > May 14 01:19:36 gunsight1 -- MARK -- > May 14 01:39:36 gunsight1 -- MARK -- > May 14 01:59:37 gunsight1 -- MARK -- > May 14 02:10:55 gunsight1 kernel: mfi0: 24089 (421826400s/0x0020/info) - Patrol Read started Your mfi device timeouts are unrelated. If you want to talk about them, please discuss them in a new/separate thread. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sun May 19 03:02:47 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 71358511 for ; Sun, 19 May 2013 03:02:47 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ia0-x236.google.com (mail-ia0-x236.google.com [IPv6:2607:f8b0:4001:c02::236]) by mx1.freebsd.org (Postfix) with ESMTP id 472EA386 for ; Sun, 19 May 2013 03:02:47 +0000 (UTC) Received: by mail-ia0-f182.google.com with SMTP id z3so6426394iad.27 for ; Sat, 18 May 2013 20:02:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=XN23hE5/LoM5C2OcFA/8RWshaCHA0p4i8ZzwRYYXN5A=; b=eCMbqVrbM0Ih6HLelsxGk+IoznTIwS7Q53h44IiWIUp9JmhedMXunCVrbyvNd9uCll FzkgxAEnsmbDBRijN29jWye8cCIJYq/PP49S3wbh8XlzIFsQqFYq6Qaj0mw/N7TrnCcm eXf+iy2wvkDHxWxH/kXRuFoP8Oy49GAsldal+J6AcIYNykEW8B+8rqPkrRyjDkDjY+Ft NuafSIN4uo64VhH3+puaOO0g127krRd+a9lLUdlGc1+vrdq26it5Y2SRgz1maxfDJYp2 Q7O01UqrBoe/cVzt11ClKbADHUZEv9rYV0efXVlEj/PQkLy2+mnjHNdBVos4EfbNNzCz 8Mvw== X-Received: by 10.50.20.38 with SMTP id k6mr2280725ige.50.1368931003639; Sat, 18 May 2013 19:36:43 -0700 (PDT) Received: from gloom ([137.122.64.57]) by mx.google.com with ESMTPSA id qn10sm5140368igc.6.2013.05.18.19.36.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 May 2013 19:36:42 -0700 (PDT) Sender: Mark Johnston Date: Sat, 18 May 2013 22:36:37 -0400 From: Mark Johnston To: kpneal@pobox.com Subject: Re: Unexpected reboot/crash on 8.2-RELEASE. Message-ID: <20130519023637.GA1781@gloom> References: <20130519014521.GA3841@neutralgood.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130519014521.GA3841@neutralgood.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 May 2013 03:02:47 -0000 On Sat, May 18, 2013 at 09:45:21PM -0400, kpneal@pobox.com wrote: > I had an unexpected reboot of my Dell R610 today around 2:05-06pm today. > I do not know if it crashed or if it was power cycled. > > This machine is running: > FreeBSD gunsight1.neutralgood.org 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Thu Dec 8 21:58:59 UTC 2011 root@:/usr/obj/usr/src/sys/GENERIC amd64 > > It's a stock 8.2-RELEASE kernel except I had to tweak it near the top of > vfs_mountroot() to delay before attempting to mount the root filesystem. > (Without my tweak it attempts to mount root before the USB drive is finished > getting attached.) > > The dmesg shows this at the reboot: > mfi0: 24272 (422106527s/0x0020/info) - Patrol Read complete > mfi0: 24273 (422172000s/0x0020/info) - Patrol Read started > mfi0: 24318 (422192750s/0x0020/info) - Patrol Read complete > mfi0: 24319 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028) > mfi0: 24320 (boot + 3s/0x0020/info) - Firmware version 1.22.12-0952 > mfi0: 24321 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028) > mfi0: 24322 (boot + 3s/0x0020/info) - Firmware version 1.22.12-0952 > > Does this mean the machine did not lose power? I ask because my datacenter > had some sort of power incident and I'm not sure if the server lost power > or not. But if the kernel message buffer from before the incident is still > present then the machine never lost power, correct? The datacenter's power > incident I'm told happened somewhere around the time of the reboot so I > have to ask. The LSI controllers I've used will keep internal event logs which are persistent across power cycles (so long as the BBU isn't dead, presumably). It looks like mfi(4) has been set up to dump the entire event log during boot. Log entries created after the last reboot are displayed with a timestamp of "boot + Ns". > > It looks like I didn't have dumps enabled. That's ... not helpful. > > The machine has been stable for: > 2:05PM up 472 days, 21 mins, 7 users, load averages: 0.01, 0.02, 0.00 That's a bit confusing... did you mean "had been"? This is the exact uptime that's in status.txt below. > > http://www.neutralgood.org/~kpn/dmesg.boot > > Here's various stats I usually keep displayed. This is the last from > before the reboot: > http://www.neutralgood.org/~kpn/status.txt > > I've got all the power savings features turned off in the BIOS and, like > I said, the machine has been stable for all this time. However, one thing > to note from a couple of days ago: > This is probably unrelated? As an aside, it'd be nice if mfi(4) dumped info about the dcmd/io cmd at least once if it times out. At the moment, it only does that if MFI_DEBUG is enabled... does anyone have an objection to changing this from a compile-time option to a sysctl? Thanks, -Mark > May 14 00:49:13 gunsight1 -- MARK -- > May 14 01:00:45 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 35 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 65 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 95 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 125 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 155 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 185 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 215 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 245 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 275 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 305 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 335 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 365 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 395 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 425 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 455 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 485 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 515 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 545 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 575 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 605 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 635 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 665 SECONDS > May 14 01:19:36 gunsight1 -- MARK -- > May 14 01:39:36 gunsight1 -- MARK -- > May 14 01:59:37 gunsight1 -- MARK -- > May 14 02:10:55 gunsight1 kernel: mfi0: 24089 (421826400s/0x0020/info) - Patrol Read started > > -- > Kevin P. Neal http://www.pobox.com/~kpn/ > "Not even the dumbest terrorist would choose an encryption program that > allowed the U.S. government to hold the key." -- (Fortune magazine > is smarter than the US government, Oct 29 2001, page 196.) > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sun May 19 06:07:00 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2CF77991 for ; Sun, 19 May 2013 06:07:00 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) by mx1.freebsd.org (Postfix) with ESMTP id 14202AC9 for ; Sun, 19 May 2013 06:07:00 +0000 (UTC) Received: from delphij-macbook.local (unknown [IPv6:2001:470:83bf:0:2066:5e0e:2de1:cd7b]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id 3425A97B6; Sat, 18 May 2013 23:06:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1368943619; bh=ECNS7ZdzQz5hHsCUJlfvP20V5hOvpgFSmmKmBtEl4Bc=; h=Date:From:Reply-To:To:CC:Subject:References:In-Reply-To; b=3z0oC5g0t3J9tJ2uvfByyVuWUj7pIukSi8ElgPr0ikr0srS8d+wCN0paxfGg/XWyl isdjUsRudusd/bK0teV9NIpIQOtDw4ElW8XkkD6ySFrlY5J1c9s/4Af/IVnqnQNPtL DZCUDMaUIdCEesteFb9/yPXrK5iOlzcAt9S8ca2c= Message-ID: <51986C02.1080303@delphij.net> Date: Sat, 18 May 2013 23:06:58 -0700 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: Michael Gass Subject: Re: Is there a library issue between 9.0 and 9.1 -ThreadRuneLocale ? References: <20130518184909.GA23083@csbsju.edu> In-Reply-To: <20130518184909.GA23083@csbsju.edu> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 May 2013 06:07:00 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 5/18/13 11:49 AM, Michael Gass wrote: > Cannot update my ports. Run portsnap followed by portmaster -a and > various ports will not update. Keep getting error msg of Undefined > symbol: "_ThreadRuneLocale" This happens for instance in updating > to png-1.5.15 or to freetype2. > > Are there library issues between 9.0 and 9.1? I am running > 9.0-stable on an i386 > > Last time I updated was in March and that went well. > > Do I need to uninstall all my ports and start over? Do I need to > move up to 9.1? You will have to move up to 9.1, running binaries compiled for newer FreeBSD versions is not supported. You don't have to start over though, running binaries compiled for older FreeBSD versions is supported. Cheers, -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJRmGwCAAoJEG80Jeu8UPuzO+cH/R4ru4Br7zq0kMvIs7G3IJEZ uKYUG1gmDrEFcHD67huPTGcS9YX56U5eb3EXuMiT/913WGgVVrcjxU/ui96Y3hEs zJy5BIha9MEYzqv52fqWQtyCusJFcW+0aMHQrd9gDaCJuTmfpQ0ArcZ0yWoPu3UV cubW0vHODkGBUx2MGPURqMLxow8FAFnUvCinymWhHTfPwnh7WwocqA5cR6/H40hg RbOJoCDxvw2f/s9eeAKW1ebjpxQ1JfvEPNvq9Ss+pZvZk23aCUxEPfT6Mdlm27EY VZJFNY2yTXCT+ZTMO00ytOjjd51hKo7C2/FJ41dtHICN4VQFbZD1pTnoDR1kCYs= =uUhB -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sun May 19 10:52:04 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DD4EA8EC for ; Sun, 19 May 2013 10:52:04 +0000 (UTC) (envelope-from prvs=18517728d5=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 82C481B1 for ; Sun, 19 May 2013 10:52:03 +0000 (UTC) Received: from r2d2 ([46.65.172.4]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50003883429.msg for ; Sun, 19 May 2013 11:51:57 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 19 May 2013 11:51:57 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 46.65.172.4 X-Return-Path: prvs=18517728d5=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org Message-ID: From: "Steven Hartland" To: , References: <20130519014521.GA3841@neutralgood.org> Subject: Re: Unexpected reboot/crash on 8.2-RELEASE. Date: Sun, 19 May 2013 11:51:57 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 May 2013 10:52:04 -0000 Under 8.2 once MFI sees a timeout it will timeout forever. I committed major updates to MFI in r247367 & r247369 which deal with many error condition problems that cause panics. So if your seeing issues with MFI I'd suggest you upgrade to stable/8. Regards Steve ----- Original Message ----- From: To: Sent: Sunday, May 19, 2013 2:45 AM Subject: Unexpected reboot/crash on 8.2-RELEASE. >I had an unexpected reboot of my Dell R610 today around 2:05-06pm today. > I do not know if it crashed or if it was power cycled. > > This machine is running: > FreeBSD gunsight1.neutralgood.org 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Thu Dec 8 21:58:59 UTC 2011 > root@:/usr/obj/usr/src/sys/GENERIC amd64 > > It's a stock 8.2-RELEASE kernel except I had to tweak it near the top of > vfs_mountroot() to delay before attempting to mount the root filesystem. > (Without my tweak it attempts to mount root before the USB drive is finished > getting attached.) > > The dmesg shows this at the reboot: > mfi0: 24272 (422106527s/0x0020/info) - Patrol Read complete > mfi0: 24273 (422172000s/0x0020/info) - Patrol Read started > mfi0: 24318 (422192750s/0x0020/info) - Patrol Read complete > mfi0: 24319 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028) > mfi0: 24320 (boot + 3s/0x0020/info) - Firmware version 1.22.12-0952 > mfi0: 24321 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028) > mfi0: 24322 (boot + 3s/0x0020/info) - Firmware version 1.22.12-0952 > > Does this mean the machine did not lose power? I ask because my datacenter > had some sort of power incident and I'm not sure if the server lost power > or not. But if the kernel message buffer from before the incident is still > present then the machine never lost power, correct? The datacenter's power > incident I'm told happened somewhere around the time of the reboot so I > have to ask. > > It looks like I didn't have dumps enabled. That's ... not helpful. > > The machine has been stable for: > 2:05PM up 472 days, 21 mins, 7 users, load averages: 0.01, 0.02, 0.00 > > http://www.neutralgood.org/~kpn/dmesg.boot > > Here's various stats I usually keep displayed. This is the last from > before the reboot: > http://www.neutralgood.org/~kpn/status.txt > > I've got all the power savings features turned off in the BIOS and, like > I said, the machine has been stable for all this time. However, one thing > to note from a couple of days ago: > > May 14 00:49:13 gunsight1 -- MARK -- > May 14 01:00:45 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 35 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 65 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 95 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 125 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 155 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 185 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 215 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 245 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 275 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 305 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 335 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 365 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 395 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 425 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 455 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 485 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 515 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 545 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 575 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 605 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 635 SECONDS > May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 665 SECONDS > May 14 01:19:36 gunsight1 -- MARK -- > May 14 01:39:36 gunsight1 -- MARK -- > May 14 01:59:37 gunsight1 -- MARK -- > May 14 02:10:55 gunsight1 kernel: mfi0: 24089 (421826400s/0x0020/info) - Patrol Read started > > -- > Kevin P. Neal http://www.pobox.com/~kpn/ > "Not even the dumbest terrorist would choose an encryption program that > allowed the U.S. government to hold the key." -- (Fortune magazine > is smarter than the US government, Oct 29 2001, page 196.) > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Tue May 21 12:40:47 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AD9235F8 for ; Tue, 21 May 2013 12:40:47 +0000 (UTC) (envelope-from db@bsdsystems.de) Received: from fop.bsdsystems.de (mx.bsdsystems.de [88.198.57.43]) by mx1.freebsd.org (Postfix) with ESMTP id A1EEBE36 for ; Tue, 21 May 2013 12:40:46 +0000 (UTC) Received: from wuerschtl.global.intra.guj.com (unknown [194.12.218.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by fop.bsdsystems.de (Postfix) with ESMTP id BF7D754691; Tue, 21 May 2013 14:40:38 +0200 (CEST) Subject: Re: still mbuf leak in 9.0 / 9.1? Mime-Version: 1.0 (Apple Message framework v1085) From: dennis berger In-Reply-To: <20130518153538.GA9228@icarus.home.lan> Date: Tue, 21 May 2013 14:40:38 +0200 Message-Id: <387AEDDC-114C-40D6-B7C4-3AF1708F7CDF@bsdsystems.de> References: <004BC6EA-D8E6-473E-851C-9CDA7578510A@nipsi.de> <20130515211436.GA42790@icarus.home.lan> <696B5622-A95D-4187-A027-07ECC9B5AD1F@nipsi.de> <4F319A22-E611-4EE6-A970-98315B15C12F@nipsi.de> <1186B7CE-EC84-42F6-8904-EDD0C4A5FFBD@bsdsystems.de> <20130517173101.GB87223@icarus.home.lan> <20130518153538.GA9228@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1085) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Steven Hartland , FreeBSD stable , Ronald Klop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 May 2013 12:40:47 -0000 Hi Jeremy, thanks for your detailed explanation. -dennis Am 18.05.2013 um 17:35 schrieb Jeremy Chadwick: > On Sat, May 18, 2013 at 12:14:28PM +0200, Ronald Klop wrote: >> On Fri, 17 May 2013 19:31:01 +0200, Jeremy Chadwick = wrote: >>=20 >>> On Fri, May 17, 2013 at 11:37:23AM +0200, dennis berger wrote: >>>> Hi List, >>>> I can confirm that it is the bug you mentioned steven. >>>> Here is how I found it. >>>>=20 >>>> I recorded hourly zfskern and nfsd stats. like this. >>>>=20 >>>> echo "PROCSTAT" >> $reportname >>>> pgrep -S "(zfskern|nfsd)" | xargs procstat -kk >> $reportname >>>>=20 >>>> luckily it crashed this night and logged this. >>>>=20 >>>> 1910 101508 nfsd nfsd: service mi_switch+0x186 >>>> sleepq_wait+0x42 _sleep+0x376 arc_lowmem+0x77 kmem_malloc+0xc1 >>>> uma_large_malloc+0x4a malloc+0xd9 arc_get_data_buf+0xb5 >>>> arc_read_nolock+0x1ec arc_read+0x93 dbuf_prefetch+0x12c >>>> dmu_zfetch_dofetch+0x10b dmu_zfetch+0xaf8 dbuf_read+0x4a7 >>>> dmu_buf_hold_array_by_dnode+0x16b dmu_buf_hold_array+0x67 >>>> dmu_read_uio+0x3f zfs_freebsd_read+0x3e3 >>>>=20 >>>> Maybe it would be good to merge this fix into RELENG_9_1 and >>>> distribute a fix via freebsd-update what do you think? >>>>=20 >>>> best, >>>> -dennis >>>>=20 >>>>=20 >>>> Am 16.05.2013 um 11:42 schrieb dennis berger: >>>>=20 >>>>> This is indeed a ZFS+NFS system and I can see that istgt and >>>> nfs are stuck in some ZIO state. Maybe it's this. >>>>> Thank's for pointing out. >>>>>=20 >>>>> Is it this ZFS+NFS deadlock? >>>>>=20 >>>>> --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c >>>>> +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c >>>>> @@ -3720,8 +3720,16 @@ arc_lowmem(void *arg __unused, int >>>> howto __unused) >>>>> mutex_enter(&arc_reclaim_thr_lock); >>>>> needfree =3D 1; >>>>> cv_signal(&arc_reclaim_thr_cv); >>>>> - while (needfree) >>>>> - msleep(&needfree, &arc_reclaim_thr_lock, 0, "zfs:lowmem", 0); >>>>> + >>>>> + /* >>>>> + * It is unsafe to block here in arbitrary threads, because >>>> we can come >>>>> + * here from ARC itself and may hold ARC locks and thus risk >>>> a deadlock >>>>> + * with ARC reclaim thread. >>>>> + */ >>>>> + if (curproc =3D=3D pageproc) { >>>>> + while (needfree) >>>>> + msleep(&needfree, &arc_reclaim_thr_lock, 0, "zfs:lowmem", 0); >>>>> + } >>>>> mutex_exit(&arc_reclaim_thr_lock); >>>>> mutex_exit(&arc_lowmem_lock); >>>>> } >>>>>=20 >>>>> I'll try to crash our testsystem. I'll assume that stressing >>>> NFS backed with ZFS a lot might trigger this bug? >>>>>=20 >>>>> -dennis >>>>>=20 >>>>>=20 >>>>> Am 16.05.2013 um 00:03 schrieb Steven Hartland: >>>>>=20 >>>>>> ----- Original Message ----- From: "dennis berger" >>>>>>> FreeBSD 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec >>>> 4 09:23:10 UTC 2012 >>>>>>>=20 >>>>>>>> 3. Regarding this: >>>>>>>>>> A clean shutdown isn't possible though. It hangs after vnode >>>>>>>>>> cleaning, normally you would see detaching of usb devices >>>> here, or >>>>>>>>>> other devices maybe? >>>>>>>> Please don't conflate this with your above issue. This is = almost >>>>>>>> certainly unrelated. Please start a new thread about that >>>> if desired. >>>>>>>=20 >>>>>>> Maybe this is a misunderstanding normally this system will >>>> shutdown cleanly, of course. >>>>>>> This hang only appears after the network problem above. >>>>>>=20 >>>>>> If this is a ZFS system, its a known issue which is fixed in = current, >>>>>> stable-9, stable-8 and the upcoming 8.4 release. >>>>>>=20 >>>>>> If not and you have USB devices see if the following sysctl = helps: >>>>>> hw.usb.no_shutdown_wait=3D1 >>>=20 >>> I'm sorry to say it won't happen. The only updates that the = -RELEASE >>> branches get are for security. If you want fixes for other things, = you >>> need to follow/run stables branches (i.e. stable/9), otherwise you = will >>> need to wait until 9.2-RELEASE comes out. >>>=20 >>=20 >> And errata notices? Are they for security? >=20 > Example case: >=20 > http://www.freebsd.org/releases/9.1R/errata.html >=20 > Only the items in section "Security Advisories" would get actual = updates > pushed out to the 9.1-RELEASE branch (e.g. RELENG_9_1); the items in > sections "Open Issues" and "Late-breaking News" are purely FYIs. = There > are always hundreds of bugs that never show up in either of those > sections but are mentioned in the next official versions' Release = Notes. > I can speculate all day and night as to why this is, but it's easier = for > me to just say "that's just the way it is". >=20 > For example, compare the "Open Issues" in the 9.0-RELEASE errata to = all > the bugfixes in the 9.1-RELEASE Release Notes (you'll have to go = through > each item by hand and read it): >=20 > http://www.freebsd.org/releases/9.0R/errata.html > http://www.freebsd.org/releases/9.1R/relnotes-detailed.html >=20 > ...and you'll see what I mean. >=20 > So to recap: when you run a -RELEASE branch, you should only expect > fixes related to security. For any other problems, you are expected = to > run stable/X (e.g. stable/9) or get to backport the fix yourself. >=20 > And because I am certain someone will bring it up: no, the fixes done = in > stable/X cannot necessarily be turned into a patch file for a -RELEASE > branch. The reason is that there are often other commits to stable/X > branches which are for things other than bugfixes (i.e. > re-engineering/refactoring of code, semantics changes, or entire > portions nuked altogether). Sometimes "backported" patches can be = made, > but it isn't always the case -- it is not always as simple as "the = patch > applied cleanly". ZFS and NFS are two (of many) things which have = been > undergoing constant change. >=20 > --=20 > | Jeremy Chadwick jdc@koitsu.org | > | UNIX Systems Administrator http://jdc.koitsu.org/ | > | Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" Dipl.-Inform. (FH) Dennis Berger email: db@bsdsystems.de mobile: +491791231509 fon: +494054001817 From owner-freebsd-stable@FreeBSD.ORG Tue May 21 15:24:36 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 88FD03AD for ; Tue, 21 May 2013 15:24:36 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 347B59A6 for ; Tue, 21 May 2013 15:24:36 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r4LFOYVg080289; Tue, 21 May 2013 09:24:34 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r4LFOYNq080286; Tue, 21 May 2013 09:24:34 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 21 May 2013 09:24:34 -0600 (MDT) From: Warren Block To: Michael Gass Subject: Re: Command line not responding In-Reply-To: <20130518024920.GA32753@csbsju.edu> Message-ID: References: <20130517175653.GA15498@csbsju.edu> <20130517185513.GA88287@icarus.home.lan> <20130518024920.GA32753@csbsju.edu> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 21 May 2013 09:24:34 -0600 (MDT) Cc: Jeremy Chadwick , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 May 2013 15:24:36 -0000 On Fri, 17 May 2013, Michael Gass wrote: > On Fri, May 17, 2013 at 11:55:13AM -0700, Jeremy Chadwick wrote: >> On Fri, May 17, 2013 at 12:56:53PM -0500, Michael Gass wrote: >>> Running 9.0-Stable on an i386. >>> >>> Whenever I type a command at the prompt I get >>> the output >>> >>> /usr/local/lib/libintl.so.9: Undefined symbol "_ThreadRuneLocale" >>> >>> and nothing else - the command will not run. Just the >>> above output. Commands like "ls" and "exit" work, but not much >>> else. This happends whether I am logged in a user or as root. >>> Cannot even halt the system from the command line. >>> >>> Started to happen after trying to update the freetype2 port. >>> Got an error msg while updating libXft-2.1.14. From that point >>> on I cannot use the command line. >>> >>> I have no idea what to try. Any suggestions. >> > > >> First provide the contents of /etc/make.conf and /etc/src.conf. >> > > Thanks for getting back to me. Here are the contents of the two > files. I rebuilt the kernel last fall and have updated ports > fairly regularly since. Things have worked fine until today when > I tried to update ports. > > # File: make.conf > # The ? in the below is for buildworld > CPUTYPE?=pentium2 > # Uncomment the below for general builds. > CFLAGS= -O -pipe > # Uncomment the below for kernel builds. > # COPTFLAGS= -O -pipe It is almost always a mistake to set CFLAGS in make.conf. Not only does it not improve performance, it frequently causes problems. It will sometimes decrease performance for ports that can safely use custom CFLAGS themselves, because it prevents them from using those custom flags. In other words, custom CFLAGS provide few or zero improvements, and have a significant risk of causing problems. From owner-freebsd-stable@FreeBSD.ORG Wed May 22 02:12:57 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D896B7B6 for ; Wed, 22 May 2013 02:12:57 +0000 (UTC) (envelope-from usaopp@hushmail.com) Received: from smtp5.hushmail.com (smtp5a.hushmail.com [65.39.178.235]) by mx1.freebsd.org (Postfix) with ESMTP id C3F4EE25 for ; Wed, 22 May 2013 02:12:57 +0000 (UTC) Received: from smtp5.hushmail.com (smtp5a.hushmail.com [65.39.178.235]) by smtp5.hushmail.com (Postfix) with SMTP id 8E8BC5809A for ; Wed, 22 May 2013 01:42:41 +0000 (UTC) Received: from smtp.hushmail.com (w6.hushmail.com [65.39.178.92]) by smtp5.hushmail.com (Postfix) with ESMTP; Wed, 22 May 2013 01:42:40 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id 275A5A6E38; Wed, 22 May 2013 01:42:40 +0000 (UTC) MIME-Version: 1.0 Date: Tue, 21 May 2013 21:42:39 -0400 To: freebsd-stable@freebsd.org Subject: OpenSSH in -STABLE From: usaopp@hushmail.com Message-Id: <20130522014240.275A5A6E38@smtp.hushmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: des@des.no X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 22 May 2013 02:12:57 -0000 Hi. Are there any plans to get OpenSSH 6.2 in 9-STABLE? I'd like to check out the new AES-GCM stuff without going to -CURRENT on this system. If there are no plans, is there a possibility? Thanks From owner-freebsd-stable@FreeBSD.ORG Wed May 22 02:19:59 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 50108A64 for ; Wed, 22 May 2013 02:19:59 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id 30CBCE5A for ; Wed, 22 May 2013 02:19:58 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.7/8.14.7) with ESMTP id r4M2JwIR026663; Tue, 21 May 2013 19:19:58 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.7/8.14.7/Submit) id r4M2JwYk026662; Tue, 21 May 2013 19:19:58 -0700 (PDT) (envelope-from david) Date: Tue, 21 May 2013 19:19:58 -0700 From: David Wolfskill To: usaopp@hushmail.com Subject: Re: OpenSSH in -STABLE Message-ID: <20130522021958.GA1291@albert.catwhisker.org> References: <20130522014240.275A5A6E38@smtp.hushmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6Jy4/gb9ZgnsEOX8" Content-Disposition: inline In-Reply-To: <20130522014240.275A5A6E38@smtp.hushmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 22 May 2013 02:19:59 -0000 --6Jy4/gb9ZgnsEOX8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 21, 2013 at 09:42:39PM -0400, usaopp@hushmail.com wrote: > Hi. Are there any plans to get OpenSSH 6.2 in 9-STABLE? I'd like to > check out the new AES-GCM stuff without going to -CURRENT on this > system. If there are no plans, is there a possibility? Thanks > .... Please refer to ports/security/openssh-portable; its Makefile says it's 6.2p2,1, last updated about 5 days ago. Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --6Jy4/gb9ZgnsEOX8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iEYEARECAAYFAlGcK00ACgkQmprOCmdXAD1LBgCfSKwLlA6Bvw5uHt+3GHvmp7OA beoAni5wt8MkZOggWrCTJKglxlZgENka =/AJP -----END PGP SIGNATURE----- --6Jy4/gb9ZgnsEOX8-- From owner-freebsd-stable@FreeBSD.ORG Wed May 22 03:01:40 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id ADECD265 for ; Wed, 22 May 2013 03:01:40 +0000 (UTC) (envelope-from giorgiolago@gmail.com) Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id C706F142 for ; Wed, 22 May 2013 03:01:39 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id q57so470529wes.41 for ; Tue, 21 May 2013 20:01:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=cGpR8Kbobsx110d2z+rHL7s2UnuXbITeJ98t0Vnrnsk=; b=t+gFF7/0/cf3PFjPBXBhiNJz9zdJEQu9IFPlWi6/Ol5C9xKlCloIYAPBLJGDDTysR6 ebDX8EK0MOlgfc+Nu7KDDTYtDPEXBd8QTwA6BnY8xDBQC3Dq4bmcx8VVfsNVlxAAOy3q R6bueBhYmfR6AVElgU4p+SERyp5KdQb5+i/ZCp3Aj5JRdqh8D5GoUg43aNmOAJsdvcmQ 15pNRTmuXzQ4saYPaDKEwm2cQV3I7oK6RoJ6p7Wt7qnSvZ7UHq0adxsCiyQbq+z1E5Ns kS7FxQg/nm8T6aznQ+QC9NP2awpbp+70KiezyKW+FP+VjrlwXcRKFfBOdeYJs6aPGlF1 R8Qg== MIME-Version: 1.0 X-Received: by 10.180.39.233 with SMTP id s9mr10166674wik.25.1369191698918; Tue, 21 May 2013 20:01:38 -0700 (PDT) Received: by 10.194.174.231 with HTTP; Tue, 21 May 2013 20:01:38 -0700 (PDT) Date: Wed, 22 May 2013 00:01:38 -0300 Message-ID: Subject: em2: watchdog timeout -- resetting From: Giorgio Emanuel To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 22 May 2013 03:01:40 -0000 Hello, I have a server pfsense in bridge mode to function as transparent FW, the problem is that once I connect the pfsense between my router core and my core switch catalyst a few seconds begin to appear several messages like these: em2: watchdog timeout - resetting em2: watchdog timeout - resetting em2: watchdog timeout - resetting em2: watchdog timeout - resetting And the connection falls back repeatedly and indefinitely. Searching on google did some tweaks: hw.em.rxd =3D "4096" hw.em.txd =3D "4096" hw.em.tx_int_delay =3D "250" hw.em.rx_int_delay =3D "250" hw.em.tx_abs_int_delay =3D "250" hw.em.rx_abs_int_delay =3D "250" hw.em.enable_msix =3D "0" hw.em.msix_queues =3D "2" hw.em.rx_process_limit =3D "-1" hw.em.fc_setting =3D "0" hw.em.num_queues =3D 1 I tried several variations, but also without success. My infrastructure: (7301 cisco router) ------ em1 (pfsense bridge0) em2 ------ sw core cisco catalyst I tried also a fresh installation of pfsense 2.0.3 without success. My network card is an Intel =AE PRO/1000 MT Dual Port Server Adapter PCI-X = on a 32-bit PCI slot, operating bridge in 1 <-> em2. Motherboard ASUS P8H61-V and CPU corei5, I tried disabling all onboard devices, also without success. I have 4 nics identical, tested one per one all without success also. I am using the latest bios from ASUS site, I tried various combinations of bios, also without success. I tried to activate the device polling unsuccessfully to solve the problem. I tried disable acpi on boot menu but the ser without acpi wont boot. I tried disable TOE, FLOW CONTROL, no sucess. This is a link to a troughput 60 Mbits with multiple VLANs (more than 200) Wisp provider. I tested the same server same hardware but using linux (debian 6) did the bridges, and everything worked properly!, so it is clear that this is a problem software (in intel em driver?) Tested on another server (P5VD2MX + Core2Duo) but with the same NIC, and the problem occurs in the same way. I realized that it generates a huge number of interruptions em2 over 200 thousand. #vmstat -i interrupt total rate irq16: em1 12891 40 irq17: em2 546630 1713 irq19: atapci0 5181 16 irq23: ehci0 ehci1 1049 3 cpu0: timer 637069 1997 irq256: em0 1557 4 cpu3: timer 636939 1996 cpu2: timer 636939 1996 cpu1: timer 636938 1996 Total 3115193 9765 Data for debug: [2.0.3-RELEASE] [root@pfsense.localdomain] / root (1): sysctl hw.em hw.em.eee_setting: 0 hw.em.rx_process_limit: 100 hw.em.enable_msix: 0 hw.em.sbp: 0 hw.em.smart_pwr_down: 0 hw.em.txd: 4096 hw.em.rxd: 4096 hw.em.rx_abs_int_delay: 66 hw.em.tx_abs_int_delay: 66 hw.em.rx_int_delay: 0 hw.em.tx_int_delay: 0 [2.0.3-RELEASE] [root@pfsense.localdomain] / root (3): sysctl dev.em.2 dev.em.2.% desc: Intel (R) PRO/1000 Legacy Network Connection 1.0.4 dev.em.2.% driver: in dev.em.2.% location: slot =3D 0 function =3D 1 dev.em.2.% pnpinfo: vendor =3D 0x8086 device =3D 0x1079 subvendor =3D 0x808= 6 subdevice =3D 0x1179 class =3D 0x020000 dev.em.2.% parent: PCI4 dev.em.2.nvm: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 0 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 dev.em.2.flow_control: 0 dev.em.2.mbuf_alloc_fail: 0 dev.em.2.cluster_alloc_fail: 0 dev.em.2.dropped: 0 dev.em.2.tx_dma_fail: 0 dev.em.2.tx_desc_fail1: 0 dev.em.2.tx_desc_fail2: 0 dev.em.2.rx_overruns: 0 dev.em.2.watchdog_timeouts: 0 dev.em.2.device_control: 1076888137 dev.em.2.rx_control: 32794 dev.em.2.fc_high_water: 47104 dev.em.2.fc_low_water: 45604 dev.em.2.fifo_workaround: 0 dev.em.2.fifo_reset: 0 dev.em.2.txd_head: 243 dev.em.2.txd_tail: 243 dev.em.2.rxd_head: 1374 dev.em.2.rxd_tail: 1373 dev.em.2.mac_stats.excess_coll: 0 dev.em.2.mac_stats.single_coll: 0 dev.em.2.mac_stats.multiple_coll: 0 dev.em.2.mac_stats.late_coll: 0 dev.em.2.mac_stats.collision_count: 0 dev.em.2.mac_stats.symbol_errors: 0 dev.em.2.mac_stats.sequence_errors: 0 dev.em.2.mac_stats.defer_count: 0 dev.em.2.mac_stats.missed_packets: 0 dev.em.2.mac_stats.recv_no_buff: 0 dev.em.2.mac_stats.recv_undersize: 0 dev.em.2.mac_stats.recv_fragmented: 0 dev.em.2.mac_stats.recv_oversize: 0 dev.em.2.mac_stats.recv_jabber: 0 dev.em.2.mac_stats.recv_errs: 0 dev.em.2.mac_stats.crc_errs: 0 dev.em.2.mac_stats.alignment_errs: 0 dev.em.2.mac_stats.coll_ext_errs: 0 dev.em.2.mac_stats.xon_recvd: 0 dev.em.2.mac_stats.xon_txd: 0 dev.em.2.mac_stats.xoff_recvd: 0 dev.em.2.mac_stats.xoff_txd: 0 dev.em.2.mac_stats.total_pkts_recvd: 6681156 dev.em.2.mac_stats.good_pkts_recvd: 6681156 dev.em.2.mac_stats.bcast_pkts_recvd: 17313 dev.em.2.mac_stats.mcast_pkts_recvd: 156511 dev.em.2.mac_stats.rx_frames_64: 1199707 dev.em.2.mac_stats.rx_frames_65_127: 2110104 dev.em.2.mac_stats.rx_frames_128_255: 396 862 dev.em.2.mac_stats.rx_frames_256_511: 196001 dev.em.2.mac_stats.rx_frames_512_1023: 138581 dev.em.2.mac_stats.rx_frames_1024_1522: 2639901 dev.em.2.mac_stats.good_octets_recvd: 4439337234 dev.em.2.mac_stats.good_octets_txd: 15529 dev.em.2.mac_stats.total_pkts_txd: 143 dev.em.2.mac_stats.good_pkts_txd: 143 dev.em.2.mac_stats.bcast_pkts_txd: 104 dev.em.2.mac_stats.mcast_pkts_txd: 39 dev.em.2.mac_stats.tx_frames_64: 48 dev.em.2.mac_stats.tx_frames_65_127: 69 dev.em.2.mac_stats.tx_frames_128_255: 20 dev.em.2.mac_stats.tx_frames_256_511: 6 dev.em.2.mac_stats.tx_frames_512_1023: 0 dev.em.2.mac_stats.tx_frames_1024_1522: 0 dev.em.2.mac_stats.tso_txd: 0 dev.em.2.mac_stats.tso_ctx_fail: 0 #uname -a FreeBSD pfsense.localdomain 8.1-RELEASE-p13 FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:58:43 EDT 2013 root@snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSenses= rc/src/sys/pfSense_SMP.8 amd64 # Pciconf-lvc: em1 @ pci0: 4:0:0: class =3D 0x020000 card =3D 0x11798086 chip =3D 0x107980= 86 rev =3D 0x03 hdr =3D 0x00 class =3D network subclass =3D ethernet cap 01 [dc] =3D powerspec 2 supports D0 D3 current D0 cap 07 [e4] =3D PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction em2 @ pci0: 4:0:1: class =3D 0x020000 card =3D 0x11798086 chip =3D 0x107980= 86 rev =3D 0x03 hdr =3D 0x00 class =3D network subclass =3D ethernet cap 01 [dc] =3D powerspec 2 supports D0 D3 current D0 cap 07 [e4] =3D PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction dmesg Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:58:43 EDT 2013 root@snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSe= nsesrc/src/sys/pfSense_SMP.8 amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM) i5-2310 CPU @ 2.90GHz (2892.73-MHz K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x206a7 Family =3D 6 Model =3D 2a St= epping =3D 7 Features=3D0xbfebfbff Features2=3D0x179ae3bf,SSE4.1,SSE4.2,POPCNT,,AESNI,XSAVE,> AMD Features=3D0x28100800 AMD Features2=3D0x1 TSC: P-state invariant real memory =3D 8589934592 (8192 MB) avail memory =3D 7952838656 (7584 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard wlan: mac acl policy registered kbd1 at kbdmux0 cryptosoft0: on motherboard padlock0: No ACE support. acpi0: on motherboard acpi0: [ITHREAD] ACPI Error (psargs-0464): [RAMB] Namespace lookup failure, AE_NOT_FOUND ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20100331/nsinit-442) acpi0: Power Button (fixed) acpi0: reservation of 67, 1 (4) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xf000-0xf03f mem 0xf7800000-0xf7bfffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0 pci0: at device 22.0 (no driver attached) ehci0: mem 0xf7f04000-0xf7f043ff irq 23 at device 26.0 on pci0 ehci0: [ITHREAD] usbus0: EHCI version 1.0 usbus0: on ehci0 pcib2: irq 16 at device 28.0 on pci0 pci2: on pcib2 em0: port 0xe000-0xe01f mem 0xf7e20000-0xf7e3ffff,0xf7e00000-0xf7e1ffff irq 16 at device 0.0 on pci2 em0: Using an MSI interrupt em0: [FILTER] pcib3: irq 16 at device 28.4 on pci0 pci3: on pcib3 pcib4: irq 16 at device 0.0 on pci3 pci4: on pcib4 em1: port 0xd040-0xd07f mem 0xf7d20000-0xf7d3ffff,0xf7cc0000-0xf7cfffff irq 16 at device 0.0 on pci= 4 em1: [FILTER] em2: port 0xd000-0xd03f mem 0xf7d00000-0xf7d1ffff,0xf7c40000-0xf7c7ffff irq 17 at device 0.1 on pci= 4 em2: [FILTER] ehci1: mem 0xf7f03000-0xf7f033ff irq 23 at device 29.0 on pci0 ehci1: [ITHREAD] usbus1: EHCI version 1.0 usbus1: on ehci1 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xf7f02000-0xf7f027ff irq 19 at device 31.2 on pci0 atapci0: [ITHREAD] atapci0: AHCI v1.30 controller with 4 3Gbps ports, PM not supported ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 acpi_tz0: on acpi0 acpi_tz1: on acpi0 atrtc0: port 0x70-0x77 irq 8 on acpi0 atrtc0: Warning: Couldn't map I/O. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: cannot reserve I/O port range coretemp0: on cpu0 est0: on cpu0 p4tcc0: on cpu0 coretemp1: on cpu1 est1: on cpu1 p4tcc1: on cpu1 coretemp2: on cpu2 est2: on cpu2 p4tcc2: on cpu2 coretemp3: on cpu3 est3: on cpu3 p4tcc3: on cpu3 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 ad4: 476940MB at ata2-master UDMA100 SATA 3Gb/s ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 acd0: DVDR at ata3-master UDMA100 SATA 1.5Gb/s SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! Root mount waiting for: usbus1 usbus0 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered Root mount waiting for: usbus1 usbus0 ugen0.2: at usbus0 uhub2: on usbus0 ugen1.2: at usbus1 uhub3: on usbus1 Root mount waiting for: usbus1 usbus0 uhub2: 4 ports with 4 removable, self powered uhub3: 6 ports with 6 removable, self powered ugen0.3: at usbus0 ukbd0: on usbus0 kbd2 at ukbd0 uhid0: on usbus0 Trying to mount root from ufs:/dev/ad4s1a pflog0: promiscuous mode enabled em2: link state changed to UP bridge0: promiscuous mode enabled pflog0: promiscuous mode disabled Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...0 0 0 done All buffers synced. Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:58:43 EDT 2013 root@snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSe= nsesrc/src/sys/pfSense_SMP.8 amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM) i5-2310 CPU @ 2.90GHz (2892.72-MHz K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x206a7 Family =3D 6 Model =3D 2a St= epping =3D 7 Features=3D0xbfebfbff Features2=3D0x179ae3bf,SSE4.1,SSE4.2,POPCNT,,AESNI,XSAVE,> AMD Features=3D0x28100800 AMD Features2=3D0x1 TSC: P-state invariant real memory =3D 8589934592 (8192 MB) avail memory =3D 7952838656 (7584 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard wlan: mac acl policy registered kbd1 at kbdmux0 cryptosoft0: on motherboard padlock0: No ACE support. acpi0: on motherboard acpi0: [ITHREAD] ACPI Error (psargs-0464): [RAMB] Namespace lookup failure, AE_NOT_FOUND ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20100331/nsinit-442) acpi0: Power Button (fixed) acpi0: reservation of 67, 1 (4) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xf000-0xf03f mem 0xf7800000-0xf7bfffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0 pci0: at device 22.0 (no driver attached) ehci0: mem 0xf7f04000-0xf7f043ff irq 23 at device 26.0 on pci0 ehci0: [ITHREAD] usbus0: EHCI version 1.0 usbus0: on ehci0 pcib2: irq 16 at device 28.0 on pci0 pci2: on pcib2 em0: port 0xe000-0xe01f mem 0xf7e20000-0xf7e3ffff,0xf7e00000-0xf7e1ffff irq 16 at device 0.0 on pci2 em0: Using an MSI interrupt em0: [FILTER] pcib3: irq 16 at device 28.4 on pci0 pci3: on pcib3 pcib4: irq 16 at device 0.0 on pci3 pci4: on pcib4 em1: port 0xd040-0xd07f mem 0xf7d20000-0xf7d3ffff,0xf7cc0000-0xf7cfffff irq 16 at device 0.0 on pci= 4 em1: [FILTER] em2: port 0xd000-0xd03f mem 0xf7d00000-0xf7d1ffff,0xf7c40000-0xf7c7ffff irq 17 at device 0.1 on pci= 4 em2: [FILTER] ehci1: mem 0xf7f03000-0xf7f033ff irq 23 at device 29.0 on pci0 ehci1: [ITHREAD] usbus1: EHCI version 1.0 usbus1: on ehci1 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xf7f02000-0xf7f027ff irq 19 at device 31.2 on pci0 atapci0: [ITHREAD] atapci0: AHCI v1.30 controller with 4 3Gbps ports, PM not supported ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 acpi_tz0: on acpi0 acpi_tz1: on acpi0 atrtc0: port 0x70-0x77 irq 8 on acpi0 atrtc0: Warning: Couldn't map I/O. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: cannot reserve I/O port range coretemp0: on cpu0 est0: on cpu0 p4tcc0: on cpu0 coretemp1: on cpu1 est1: on cpu1 p4tcc1: on cpu1 coretemp2: on cpu2 est2: on cpu2 p4tcc2: on cpu2 coretemp3: on cpu3 est3: on cpu3 p4tcc3: on cpu3 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 ad4: 476940MB at ata2-master UDMA100 SATA 3Gb/s ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 acd0: DVDR at ata3-master UDMA100 SATA 1.5Gb/s SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! Root mount waiting for: usbus1 usbus0 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered Root mount waiting for: usbus1 usbus0 ugen0.2: at usbus0 uhub2: on usbus0 ugen1.2: at usbus1 uhub3: on usbus1 uhub2: 4 ports with 4 removable, self powered uhub3: 6 ports with 6 removable, self powered Root mount waiting for: usbus0 ugen0.3: at usbus0 ukbd0: on usbus0 kbd2 at ukbd0 uhid0: on usbus0 Trying to mount root from ufs:/dev/ad4s1a pflog0: promiscuous mode enabled em2: link state changed to UP bridge0: promiscuous mode enabled From owner-freebsd-stable@FreeBSD.ORG Wed May 22 03:03:44 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4C2C63BA for ; Wed, 22 May 2013 03:03:44 +0000 (UTC) (envelope-from usaopp@hushmail.com) Received: from smtp2.hushmail.com (smtp2a.hushmail.com [65.39.178.237]) by mx1.freebsd.org (Postfix) with ESMTP id 393A21A6 for ; Wed, 22 May 2013 03:03:44 +0000 (UTC) Received: from smtp2.hushmail.com (smtp2a.hushmail.com [65.39.178.237]) by smtp2.hushmail.com (Postfix) with SMTP id 69F80E7D5F for ; Wed, 22 May 2013 03:02:28 +0000 (UTC) Received: from smtp.hushmail.com (w6.hushmail.com [65.39.178.92]) by smtp2.hushmail.com (Postfix) with ESMTP; Wed, 22 May 2013 03:02:27 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id 58AF2A6E34; Wed, 22 May 2013 03:02:27 +0000 (UTC) MIME-Version: 1.0 Date: Tue, 21 May 2013 23:02:27 -0400 To: david@catwhisker.org Subject: Re: OpenSSH in -STABLE From: usaopp@hushmail.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" Message-Id: <20130522030227.58AF2A6E34@smtp.hushmail.com> Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 22 May 2013 03:03:44 -0000 On Tue, 21 May 2013 22:20:08 -0400 "David Wolfskill" wrote: >On Tue, May 21, 2013 at 09:42:39PM -0400, usaopp@hushmail.com >wrote: >> Hi. Are there any plans to get OpenSSH 6.2 in 9-STABLE? I'd like >to >> check out the new AES-GCM stuff without going to -CURRENT on >this >> system. If there are no plans, is there a possibility? Thanks >> .... > >Please refer to ports/security/openssh-portable; its Makefile says >it's >6.2p2,1, last updated about 5 days ago. > Thanks, but that wasn't what I asked about. I'm aware of the version in ports. From owner-freebsd-stable@FreeBSD.ORG Wed May 22 03:11:13 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 057C6770 for ; Wed, 22 May 2013 03:11:13 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:80]) by mx1.freebsd.org (Postfix) with ESMTP id C7B5923A for ; Wed, 22 May 2013 03:11:12 +0000 (UTC) Received: from omta07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by qmta08.emeryville.ca.mail.comcast.net with comcast id erAl1l0041GXsucA8rBBi4; Wed, 22 May 2013 03:11:11 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta07.emeryville.ca.mail.comcast.net with comcast id erB91l00q1t3BNj8UrBAHw; Wed, 22 May 2013 03:11:11 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E44FE73A1B; Tue, 21 May 2013 20:11:09 -0700 (PDT) Date: Tue, 21 May 2013 20:11:09 -0700 From: Jeremy Chadwick To: usaopp@hushmail.com Subject: Re: OpenSSH in -STABLE Message-ID: <20130522031109.GA91722@icarus.home.lan> References: <20130522021958.GA1291@albert.catwhisker.org> <20130522030227.58AF2A6E34@smtp.hushmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130522030227.58AF2A6E34@smtp.hushmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369192271; bh=F1BT8nrzrg/7kUEWYbuEyEB6AAXlM0jlCbQvT9mK2+U=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=Ruu/eBsDx0ybrnM2NQCIvhGFgiO1YCzs0rFhoGue22NXb3apRKPD809j3DqGWbnVS dKuLzqexGvDHfbE3FIWif8kJUhMsJDythT95r/JRSgoLtDlOyjys5fDM5KCKoxf5AB nS7awoILwjzRG4ShnvQFjEhs6vf76tZFBmd5AVoi1XATOn9hw7YV04U7iwpbapRfmA cz+NieIDJsJHMhwjEnn+xgdIy8XFQAHNm+EL8tZUL+GyaANPYNlfHww5F0vlf0sej4 ZLTzV6fMj8inshoyqw6DuGHfpAvaLHjp1IL3EmIvlnTmu0wJrzWyveUHVCrv4U7p0S xzotrRE1euTrQ== Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 22 May 2013 03:11:13 -0000 On Tue, May 21, 2013 at 11:02:27PM -0400, usaopp@hushmail.com wrote: > On Tue, 21 May 2013 22:20:08 -0400 "David Wolfskill" > wrote: > >On Tue, May 21, 2013 at 09:42:39PM -0400, usaopp@hushmail.com > >wrote: > >> Hi. Are there any plans to get OpenSSH 6.2 in 9-STABLE? I'd like > >to > >> check out the new AES-GCM stuff without going to -CURRENT on > >this > >> system. If there are no plans, is there a possibility? Thanks > >> .... > > > >Please refer to ports/security/openssh-portable; its Makefile says > >it's > >6.2p2,1, last updated about 5 days ago. > > > > Thanks, but that wasn't what I asked about. I'm aware of the > version in ports. Try freebsd-security@freebsd.org, I am certain you will get an answer there. Fact: OpenSSH 6.2p1 was imported to head/CURRENT on March 22nd, and 6.2p2 was imported to head/CURRENT on May 22nd: http://svnweb.freebsd.org/base/head/crypto/openssh/ChangeLog OpenSSH is such an important/key piece of software that, much like OpenSSL, it is one that does not warrant haste when it comes to getting MFC'd. If you want something more recent on non-CURRENT, you will usually be told to run the version from ports. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed May 22 03:12:18 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5270887B for ; Wed, 22 May 2013 03:12:18 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:24]) by mx1.freebsd.org (Postfix) with ESMTP id 216CE255 for ; Wed, 22 May 2013 03:12:18 +0000 (UTC) Received: from omta12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by qmta02.emeryville.ca.mail.comcast.net with comcast id eqkT1l0090x6nqcA2rCHmb; Wed, 22 May 2013 03:12:17 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta12.emeryville.ca.mail.comcast.net with comcast id erCB1l00d1t3BNj8YrCBLe; Wed, 22 May 2013 03:12:17 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8D51573A1D; Tue, 21 May 2013 20:12:11 -0700 (PDT) Date: Tue, 21 May 2013 20:12:11 -0700 From: Jeremy Chadwick To: usaopp@hushmail.com Subject: Re: OpenSSH in -STABLE Message-ID: <20130522031211.GA91852@icarus.home.lan> References: <20130522021958.GA1291@albert.catwhisker.org> <20130522030227.58AF2A6E34@smtp.hushmail.com> <20130522031109.GA91722@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130522031109.GA91722@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369192337; bh=ls0yWI2BQ/bUSigYlEB/zm+cUalluuanHv6zDMARyj8=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=aL0Hg65epDH5uxGbusn7yC4jYDxK2RaInIJ1YjIK2DapDlalxVOmj1vtieqNsrlYS 143vtw8P2SKSU1apaI9a9OOFI3kkWZoB1YZDn2ON2vKWzSO5hwhZOyYINNnW3s0xsL mmPeeC359GeqFuHL1IgrXzxdaC90p/TGE9EB6IopaF1BhFozzX+YQOyg2RnZLX/oyS QxQs4aaSUTDP153eLCZCP+TSYGMQz0Ei4SeiNeHW5BlUe8Y2gBz2Cb5CsKDCfr9dvP Pb0jALli6pZ19K40SsZJpQDDDsIiBvGke6sqSPOHtTZh/chSD8ylhTqK55qr05PJLO bf8jazR+gyNLA== Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 22 May 2013 03:12:18 -0000 On Tue, May 21, 2013 at 08:11:09PM -0700, Jeremy Chadwick wrote: > ... 6.2p2 was imported to head/CURRENT on May 22nd ... Typo on my part: this should have read May 17th, as is obvious from svnweb. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed May 22 03:29:00 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C3B02B07 for ; Wed, 22 May 2013 03:29:00 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qe0-f45.google.com (mail-qe0-f45.google.com [209.85.128.45]) by mx1.freebsd.org (Postfix) with ESMTP id 8A3E6316 for ; Wed, 22 May 2013 03:29:00 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id q19so867962qeb.4 for ; Tue, 21 May 2013 20:28:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=f/4A/sDu9dSqh5MsPqkzkY+/71dxGQp0wIjsLxJxQpc=; b=M/nSSnqAAgLN9/9tVQVDMG/bQZ5BWqsW0uRnDNxX5bqXFJQiaoSTppvI6rHsNhc0JU 9vCFRYiikbVSialZulmKIN6OXFkCAmvcFL2zIYWoEPMs20aRGR9ilCJkdWqcMXI0pAhO Ue/u2HmcKiGcBwImb4H9NrYx09vMNSTb1+miJRdtcAV6nRdKqb9wTVB3N+UDRFjhC8EP PNnV1RWbaVVjrXczfQw/ul603PZMGUADeAI/d+mShNIG/HIs8fPfbFZ40v9icRqDP3tR qXortpTG3wZMnRtPo+lmJO5sS2l1u35+VNQYZCicxvttgsgAXp3xo6px08Q5FZrT/HQy 7j0g== MIME-Version: 1.0 X-Received: by 10.224.171.194 with SMTP id i2mr5244563qaz.80.1369193334705; Tue, 21 May 2013 20:28:54 -0700 (PDT) Received: by 10.49.0.66 with HTTP; Tue, 21 May 2013 20:28:54 -0700 (PDT) Received: by 10.49.0.66 with HTTP; Tue, 21 May 2013 20:28:54 -0700 (PDT) In-Reply-To: <20130522030227.58AF2A6E34@smtp.hushmail.com> References: <20130522030227.58AF2A6E34@smtp.hushmail.com> Date: Tue, 21 May 2013 20:28:54 -0700 Message-ID: Subject: Re: OpenSSH in -STABLE From: Freddie Cash To: usaopp@hushmail.com Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 22 May 2013 03:29:00 -0000 Well, you showed an interest in testing a specific feature of 6.2, so a recommendation to use the version in ports is perfectly valid. :) On 2013-05-21 8:03 PM, wrote: > On Tue, 21 May 2013 22:20:08 -0400 "David Wolfskill" > wrote: > >On Tue, May 21, 2013 at 09:42:39PM -0400, usaopp@hushmail.com > >wrote: > >> Hi. Are there any plans to get OpenSSH 6.2 in 9-STABLE? I'd like > >to > >> check out the new AES-GCM stuff without going to -CURRENT on > >this > >> system. If there are no plans, is there a possibility? Thanks > >> .... > > > >Please refer to ports/security/openssh-portable; its Makefile says > >it's > >6.2p2,1, last updated about 5 days ago. > > > > Thanks, but that wasn't what I asked about. I'm aware of the > version in ports. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Wed May 22 08:22:29 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6478A50E for ; Wed, 22 May 2013 08:22:29 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 29E571D8 for ; Wed, 22 May 2013 08:22:28 +0000 (UTC) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp-int.des.no (Postfix) with ESMTP id E34CA71D2; Wed, 22 May 2013 08:14:07 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id 453D24A850; Wed, 22 May 2013 10:14:00 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: usaopp@hushmail.com Subject: Re: OpenSSH in -STABLE References: <20130522014240.275A5A6E38@smtp.hushmail.com> Date: Wed, 22 May 2013 10:13:59 +0200 In-Reply-To: <20130522014240.275A5A6E38@smtp.hushmail.com> (usaopp@hushmail.com's message of "Tue, 21 May 2013 21:42:39 -0400") Message-ID: <868v37zb20.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 22 May 2013 08:22:29 -0000 usaopp@hushmail.com writes: > Hi. Are there any plans to get OpenSSH 6.2 in 9-STABLE? I'd like to > check out the new AES-GCM stuff without going to -CURRENT on this > system. If there are no plans, is there a possibility? Thanks Use the port. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Thu May 23 12:55:28 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 965D8832 for ; Thu, 23 May 2013 12:55:28 +0000 (UTC) (envelope-from MGASS@csbsju.edu) Received: from smtp1.computing.csbsju.edu (smtp1.computing.csbsju.edu [152.65.184.22]) by mx1.freebsd.org (Postfix) with ESMTP id 5240BE82 for ; Thu, 23 May 2013 12:55:27 +0000 (UTC) X-AuditID: ac10425b-b7f706d0000032df-c6-519e11b8c32a Received: from Mail-HTCAS1.ad.csbsju.edu (Unknown_Domain [172.16.66.43]) by smtp1.computing.csbsju.edu (Symantec Messaging Gateway) with SMTP id AA.57.13023.8B11E915; Thu, 23 May 2013 07:55:21 -0500 (CDT) Received: from nx.csbsju.edu (172.16.66.48) by MAIL-HTCAS1.ad.csbsju.edu (172.16.66.43) with Microsoft SMTP Server id 14.3.123.3; Thu, 23 May 2013 07:55:20 -0500 Received: by nx.csbsju.edu (Postfix, from userid 1401) id AB2F818022C; Thu, 23 May 2013 07:55:20 -0500 (CDT) Date: Thu, 23 May 2013 07:55:20 -0500 From: Michael Gass To: Subject: Swap Warning Message? Message-ID: <20130523125520.GA14671@csbsju.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA11TfUwbdRjury3dFfuT65WPd7eB7KJGp2OyTLM44pYtkrmYhW7J4scfWOit lH6u185hoqJ04MhiWgW2dlDqcI6hWbXAwj4CCJHxseBMZ1SGJJotKiIT6swap3jXK3Dsv+ee 533f5/34HaGgbqlpwmx3sy67wcqo0pWfkTue2HBBG9I/1Vur3jJYQ21Hu07MtypL0CvpRUbW aj7EujY+91p6xb/jl+TONuXh2lv18moUVtQjNQHkZjg19CcScTZcm4qo6lE6QZHjCK6PRpTi x2kEfn9QLkRRpB3OeRfSBKwkH4HLw/2rBKzicd1X7ysFnEnmwzt1J1QC1pF50HQ8kcSY3Aj1 gd+UItbCSOBmEivIJyF8aZ6PIXi8Bs78Rwh0FvkwNIycV4m2udDkm1T4UEZQkh2UZAeXs8NI 0YFozuZ2FhaUO2xOj9tsNxWUc2VcpaeANXqiSFzcqz0oFC8cQCSBGA3WykJ6Ks1wiKuyDSAL IWdo3DhyUk/pyhzGqgoDV1HKecpsZo4zO+xMFl6P+fAHlzSXx8pyTCa2kDyNl+gyj9XC5GF6 JKCnciSFOKe53OzwcKUel3UAAaHgUzuPtfCpRkPVG6zLIRYcQGsIJZODv/POlFCkyeBmLSzr ZF2L6usEweRiJJPJqGwXa2IPHzBb+bch7RRwr9CSViqLzebgTXHekZQqyX7X4b5cfnB6ZcWV LcsJ9QAyERpmtWhPcU6DjTObpNaZuDu5jUVJtNXhDQKrWWSTlrniirKXq0jtRtFBei1+ppHv NkuIqPDYV05J5+CzQlFSoibd6Gy8T0jLkAiCIZ2PSwR+9YpyUs9p5JPz7wJwg/AItPw/d990 OjyYnCOliMNROKThyQdSZHK2tXhVsvOlElKbTR2IQGREAd8HQnKIzv2YDpG2BIZhX0sGjN0d p2Bs5rYO7rw3BDB1zv84TH39wVaY/DS2DVqn/Tugc+bY8/BhYqYYAn9d2A2T/tYXIXYztAcW Pvp4L3jHZvZC6/A3++DofPvLMNl5uRSmfOFy8P5y2wje32Ms3OmvOwATRxtM0PflCAfxM93V CBI3xt5FsBBsrkEw2ZI4giA8cbIeTfMXly9f3G24fyeZ+PRos3DxlLR48bnhgHDxFJu6+Kh4 8aUq0rXQ1cjx6w+D96Ltu4orH82roR+brX4rrt65LdSlie9U744U5ckcvZTj2y7jnP7e1uYj 7bUH4513+//ZXxO7VjnRfbF/9qWrjcqHet7su3r92ZweIqpTz/6h+8Tydunf60D99JaLm68M 7Sls0p/qiLleCHyR36BOi3YVXbkhL/b/fP6nz9u2BxglV2EoXK9wcYb/AahynVJ4BQAA X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 12:55:28 -0000 Updated 9.1 to 9 stable on an old PII with 256 MB of memory. (FreeBSD runs fine on this machine). After updating have been getting the following warning on startup: warning: total configured swap (524288 pages) exceeds maximum recommended amount (497056 pages). warning: increase kern.maxswzone or reduce amount of swap space. I allocated 2.0 GB of swap when I installed. This was not a problem in the past. Should I ignore this warning or do I need to do something? -- Michael Gass mgass@csbsju.edu From owner-freebsd-stable@FreeBSD.ORG Thu May 23 13:27:30 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5A38C838 for ; Thu, 23 May 2013 13:27:30 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.78]) by mx1.freebsd.org (Postfix) with ESMTP id 2024CF9 for ; Thu, 23 May 2013 13:27:29 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1UfVYF-0000gv-9c; Thu, 23 May 2013 15:27:27 +0200 Received: from [81.21.138.17] (helo=ronaldradial.versatec.local) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1UfVYC-0007no-UM; Thu, 23 May 2013 15:27:24 +0200 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-stable@freebsd.org, "Michael Gass" Subject: Re: Swap Warning Message? References: <20130523125520.GA14671@csbsju.edu> Date: Thu, 23 May 2013 15:27:24 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: <20130523125520.GA14671@csbsju.edu> User-Agent: Opera Mail/12.15 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: - X-Spam-Score: -1.9 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=disabled version=3.3.1 X-Scan-Signature: 4052b6d1c9976086d5ab5ce040fcf5b8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 13:27:30 -0000 On Thu, 23 May 2013 14:55:20 +0200, Michael Gass wrote: > Updated 9.1 to 9 stable on an old PII with 256 MB of memory. > (FreeBSD runs fine on this machine). After updating have > been getting the following warning on startup: > > warning: total configured swap (524288 pages) exceeds maximum recommended > amount (497056 pages). > warning: increase kern.maxswzone or reduce amount of swap space. > > I allocated 2.0 GB of swap when I installed. This was not a problem > in the past. > > Should I ignore this warning or do I need to do something? Do you ever use that amount of swap? Swap needs some memory for administration of which page goes where so it has a cost to increase swap too much. If you are swapping 2 GB on 256 MB I don't think you have a very usable machine, but I don't know the details of what you are doing. Maybe your swap is on very fast SSD. My advice would be to monitor your swap usage and reduce the amount of swap to a little more than you really use. Probably 1 or 2 times the amount of RAM. Ronald. From owner-freebsd-stable@FreeBSD.ORG Thu May 23 19:49:02 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 75FA9BC8 for ; Thu, 23 May 2013 19:49:02 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:48]) by mx1.freebsd.org (Postfix) with ESMTP id 46FFAD50 for ; Thu, 23 May 2013 19:49:02 +0000 (UTC) Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta05.emeryville.ca.mail.comcast.net with comcast id fRz51l0031wfjNsA5XozKX; Thu, 23 May 2013 19:48:59 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta23.emeryville.ca.mail.comcast.net with comcast id fXoy1l00N1t3BNj8jXoyys; Thu, 23 May 2013 19:48:59 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 5F17A73A33; Thu, 23 May 2013 12:48:58 -0700 (PDT) Date: Thu, 23 May 2013 12:48:58 -0700 From: Jeremy Chadwick To: Michael Gass Subject: Re: Swap Warning Message? Message-ID: <20130523194858.GA31234@icarus.home.lan> References: <20130523125520.GA14671@csbsju.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130523125520.GA14671@csbsju.edu> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369338539; bh=vE/hMbQsa6gX648XvIzVAoD0zfb8krbxMjxF6cCE0Js=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=G/0yamj2/sFTE+MIOUJ7hHP/kHZ+ds4IjDOWPKE3Ty1PVWs4xiKe01Rv3kwKa4SKV iQGluNS9Ewd7Oj3Nl5j4sj68EghQuVrHNVdZFkQghHGbLyUuqfbcVy8HfW1YJPFpQS TyXyhgicOyjlPoEUXxIayByV/3JcN6kX5CmLo1ZHfqfCYMHEA4E1LwJgMK6eFHuZbl DvF2Pg6z9x0/3OCDa0jTJaspmcKoj4SwOqS9qkIMscBMh3ZuCJrZZW7yFLKvNbCMQ0 pV0+WOSxv14xl7qwtIN4x5gv1sonHKARLOQ21kE6cm317h9Evon6Vixu04fqnoqMq4 5SU9eS8YaJENA== Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 19:49:02 -0000 On Thu, May 23, 2013 at 07:55:20AM -0500, Michael Gass wrote: > Updated 9.1 to 9 stable on an old PII with 256 MB of memory. > (FreeBSD runs fine on this machine). After updating have > been getting the following warning on startup: > > warning: total configured swap (524288 pages) exceeds maximum recommended > amount (497056 pages). > warning: increase kern.maxswzone or reduce amount of swap space. > > I allocated 2.0 GB of swap when I installed. This was not a problem > in the past. > > Should I ignore this warning or do I need to do something? Taken from my /boot/loader.conf: # Set kern.maxswzone to 0 to squelch "total configured swap exceeds # maximum recommended amount" warning, even with maxpages/2 fix. # http://lists.freebsd.org/pipermail/freebsd-stable/2012-August/thread.html#69301 # kern.maxswzone="0" Give the small amount of memory on your system, I would suggest using the above /boot/loader.conf setting, since your system is significantly likely to make use of lots of swap; decreasing swap space in your case seems downright silly. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu May 23 20:54:57 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C468F342 for ; Thu, 23 May 2013 20:54:57 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 58607FE8 for ; Thu, 23 May 2013 20:54:56 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id r4NKsuU1033826 for ; Fri, 24 May 2013 00:54:56 +0400 (MSK) (envelope-from marck@rinet.ru) Date: Fri, 24 May 2013 00:54:56 +0400 (MSK) From: Dmitry Morozovsky To: freebsd-stable@FreeBSD.org Subject: Proposed MFC to hastctl: compact 'status' and introduce 'list' command Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Fri, 24 May 2013 00:54:56 +0400 (MSK) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 20:54:57 -0000 Dear colleagues, is there any objection for MFCing the change introduced in http://svnweb.freebsd.org/changeset/base/248291 (the most major change: compacting output of `hastctl status' to one-liner per provider; old output is retained as `list' command) to at least stable/9 ? The reason I'm asking is that it could lead to changes in hast-related scripts which one use in production. If no objections are received I'm (with the generous support from trociny, thank you Mikolaj!) tend to merge it after, say, 2 weeks. Thanks! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Fri May 24 00:38:59 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5035D297; Fri, 24 May 2013 00:38:59 +0000 (UTC) (envelope-from mikes@siralan.org) Received: from mail.suso.org (mail.suso.org [66.244.94.5]) by mx1.freebsd.org (Postfix) with ESMTP id 2DB69AFF; Fri, 24 May 2013 00:38:59 +0000 (UTC) Received: from c-98-223-197-163.hsd1.in.comcast.net (c-98-223-197-163.hsd1.in.comcast.net [98.223.197.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.suso.org (Postfix) with ESMTP id D527F1381FB; Fri, 24 May 2013 00:19:54 +0000 (GMT) Date: Thu, 23 May 2013 20:18:33 -0400 (EDT) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: Craig Rodrigues Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 In-Reply-To: Message-ID: References: <20130508174721.GD1651@glenbarber.us> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Glen Barber , freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 00:38:59 -0000 I've just tested 8.4-RC3 using a different Supermicro 1U box with a fresh installation of 8.4-RC3. I had problems with the installation, wouldn't boot until I used a Windows 98 FDISK to write a master boot record (no idea why; this system uses an Adaptec SATA 1.5 6-channel PCI-X board with two drives in RAID 1). Using the em0 interface there are no problems with DHCP; when I switch to the fxp0 interface the interface starts going up/down in the same manner as reported. The problem appears associated with "world", not with the kernel (running the 8.4 kernel with the 8.3 world does not have this problem). This motherboard is an X5DPL-iGM with 2 Xeon 2.8GHz CPUs and 4 GB of RAM. The other unit (an earlier board) has a Serverworks chipset with a single Xeon CPU but also with a 100Mbit Intel Pro100 Ethernet port and a 1000Mbit Intel Pro1000 Ethernet port. This unit isn't doing anything useful, so testing isn't a problem. Mike Squires mikes@siralan.org From owner-freebsd-stable@FreeBSD.ORG Fri May 24 01:09:45 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CD71D97E for ; Fri, 24 May 2013 01:09:45 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:227]) by mx1.freebsd.org (Postfix) with ESMTP id 98ADCCE1 for ; Fri, 24 May 2013 01:09:45 +0000 (UTC) Received: from omta04.emeryville.ca.mail.comcast.net ([76.96.30.35]) by qmta12.emeryville.ca.mail.comcast.net with comcast id fRzU1l0020lTkoC01d9kXe; Fri, 24 May 2013 01:09:44 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta04.emeryville.ca.mail.comcast.net with comcast id fd9j1l00V1t3BNj8Qd9kQ0; Fri, 24 May 2013 01:09:44 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id ADE6773A33; Thu, 23 May 2013 18:09:43 -0700 (PDT) Date: Thu, 23 May 2013 18:09:43 -0700 From: Jeremy Chadwick To: "Michael L. Squires" Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524010943.GA37252@icarus.home.lan> References: <20130508174721.GD1651@glenbarber.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369357784; bh=d2kocGgHetrHa2tHC/GC6MNkXN4PWYwTlPc+FQHIAAc=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=hr7+LO9zd+lc8AvTVAPziukJIZnjGv47OmNaAfJmU1hmBBGIszDZ3jFzycUENTqJ9 MR0sxgYIntbhHy1ncMu8V6bJvtWQuBmBfJdTzoJWIRFvK3ouZOEWcvZ/e2ZM/n85KV WfStBi7j8DFEQlE805VwPEcIHOuxZUyUdym2YpD2/xN+F7aQBOJ6hsTh0Op1P3Nade 0qZm656afqVfSZ3y7OwVnMXN+L/UwfklHDMGVJrrZi0qrm+c6qrRlcDLKTxHk0siUq 0zKjtHtTO7S/laHHJ7kRZJQyWLz/PB0lldLGMrUBEOl0+IyRWcD65djlJxAd5SyABY LPtA0fjJ61mow== Cc: YongHyeon PYUN , Craig Rodrigues , freebsd-stable@freebsd.org, FreeBSD Release Engineering Team , Glen Barber X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 01:09:45 -0000 On Thu, May 23, 2013 at 08:18:33PM -0400, Michael L. Squires wrote: > I've just tested 8.4-RC3 using a different Supermicro 1U box with a fresh > installation of 8.4-RC3. I had problems with the installation, wouldn't > boot until I used a Windows 98 FDISK to write a master boot record > (no idea why; this system uses an Adaptec SATA 1.5 6-channel PCI-X > board with two > drives in RAID 1). > > Using the em0 interface there are no problems with DHCP; when I > switch to the fxp0 interface the interface starts going up/down in > the same manner as reported. > > The problem appears associated with "world", not with the kernel (running > the 8.4 kernel with the 8.3 world does not have this problem). > > This motherboard is an X5DPL-iGM with 2 Xeon 2.8GHz CPUs and 4 GB of RAM. > The other unit (an earlier board) has a Serverworks chipset with a single > Xeon CPU but also with a 100Mbit Intel Pro100 Ethernet port and a 1000Mbit > Intel Pro1000 Ethernet port. > > This unit isn't doing anything useful, so testing isn't a problem. Mike, Yong-Hyeon asked you a very important question which you didn't answer: http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073458.html If you assign a static IP address, does fxp0 behave properly? I'm also re-adding Yong-Hyeon to the CC list here. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 24 01:21:22 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 204AFB4B; Fri, 24 May 2013 01:21:22 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 799DED55; Fri, 24 May 2013 01:21:21 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 8502923F804; Thu, 23 May 2013 21:21:19 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.3 onyx.glenbarber.us 8502923F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Thu, 23 May 2013 21:21:17 -0400 From: Glen Barber To: Jeremy Chadwick Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524012117.GE1672@glenbarber.us> References: <20130508174721.GD1651@glenbarber.us> <20130524010943.GA37252@icarus.home.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="h56sxpGKRmy85csR" Content-Disposition: inline In-Reply-To: <20130524010943.GA37252@icarus.home.lan> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: YongHyeon PYUN , Craig Rodrigues , FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 01:21:22 -0000 --h56sxpGKRmy85csR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 23, 2013 at 06:09:43PM -0700, Jeremy Chadwick wrote: > On Thu, May 23, 2013 at 08:18:33PM -0400, Michael L. Squires wrote: > > I've just tested 8.4-RC3 using a different Supermicro 1U box with a fre= sh > > installation of 8.4-RC3. I had problems with the installation, wouldn't > > boot until I used a Windows 98 FDISK to write a master boot record > > (no idea why; this system uses an Adaptec SATA 1.5 6-channel PCI-X > > board with two > > drives in RAID 1). > >=20 > > Using the em0 interface there are no problems with DHCP; when I > > switch to the fxp0 interface the interface starts going up/down in > > the same manner as reported. > >=20 > > The problem appears associated with "world", not with the kernel (runni= ng > > the 8.4 kernel with the 8.3 world does not have this problem). > >=20 > > This motherboard is an X5DPL-iGM with 2 Xeon 2.8GHz CPUs and 4 GB of RA= M. > > The other unit (an earlier board) has a Serverworks chipset with a sing= le > > Xeon CPU but also with a 100Mbit Intel Pro100 Ethernet port and a 1000M= bit > > Intel Pro1000 Ethernet port. > >=20 > > This unit isn't doing anything useful, so testing isn't a problem. >=20 > Mike, Yong-Hyeon asked you a very important question which you didn't > answer: >=20 > http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073458.html >=20 > If you assign a static IP address, does fxp0 behave properly? >=20 > I'm also re-adding Yong-Hyeon to the CC list here. >=20 At this point, I am not convinced we have a problem with what will turn out to be 8.4-RELEASE. There have been several attempts to ensure the upgraded version is actually 8.4-RC3 (and again, 'uname -a' is not provided in this email...). I find it very hard to believe that we have exactly one fxp(4) user upgrading to 8.4-*. I'd really like to make sure that this is not an issue that will affect an uncountable number of users, but truthfully, at this point have to consider it a local configuration problem. Glen --h56sxpGKRmy85csR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJRnsCNAAoJEFJPDDeguUajWFcIALN9mlbBmPauwlUKeIWuHi+o psVM8V+ByqOkgWuB/E1Y2YFlju3ibOJljXEsvkL9NmLGuXN9PfUu/9jjs/8ETeGM 7CMu7SiMB9v+THOFMt7ddspfWgawc4DlqEiEJ/kbEKk3zhBRDVe87QwLutQ7qXOk ck7GIgnIqi+xso0PLBkzxCEC3e8AYjM3CS/ioG13bIdnr91DKAtiJAJHnkPGLBK1 H6aM5wHQZNczYhN4DTbkYHn40eGaLg56nliqXBUPMz1FqTEVeBwjsOVxckIbIOPO ODc48tU90f+7pND6GbLIUTgB5tOJPNwEywjGCtEY5kg0TyyR73s2SF/w6GguSwQ= =0E8A -----END PGP SIGNATURE----- --h56sxpGKRmy85csR-- From owner-freebsd-stable@FreeBSD.ORG Fri May 24 03:03:56 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 61BF03B9 for ; Fri, 24 May 2013 03:03:56 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:227]) by mx1.freebsd.org (Postfix) with ESMTP id 2CB0C235 for ; Fri, 24 May 2013 03:03:56 +0000 (UTC) Received: from omta07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by qmta12.emeryville.ca.mail.comcast.net with comcast id felJ1l0031GXsuc01f3sqL; Fri, 24 May 2013 03:03:52 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta07.emeryville.ca.mail.comcast.net with comcast id ff3r1l00g1t3BNj8Uf3sWE; Fri, 24 May 2013 03:03:52 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id C45DF73A33; Thu, 23 May 2013 20:03:51 -0700 (PDT) Date: Thu, 23 May 2013 20:03:51 -0700 From: Jeremy Chadwick To: Glen Barber Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524030351.GA39091@icarus.home.lan> References: <20130508174721.GD1651@glenbarber.us> <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524012117.GE1672@glenbarber.us> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369364633; bh=TFKt/3PPF9OHSX3nE1QogbgK4OvFiXTOGqiWQE/1hjI=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=iFwPXFeq2IwA/TxJ0V1z4OOwGZMQJfeoagwRUvx9ezH7L/NySYxErLtAnZo1LznRu nfcVsX6wtzbYaXpOzztIKajJYGpbgK6PbgZ6QSaeohn6eYnQ8BxGR3ANGMgHYpk3E6 CWTLM2z9SOreskSSmTd2WQQkYGymrX3qCONRdNcAh+ZJqauPwsdimqzQ4eC+pb8whT SMdpve4fuGTHfhrnehbDjfUNZDzIfwDVqgC791ZIWr3+5WaLbyoPrOBz+8RpLdKiw3 nyTOGPLfzvxSLXRcYnqav1WI2U3gjqb6y9oPGuJRxeEENG+VE0KTI3kDSTZUPmhdnw Ok7L8PWKXmHYw== Cc: YongHyeon PYUN , Craig Rodrigues , FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 03:03:56 -0000 On Thu, May 23, 2013 at 09:21:17PM -0400, Glen Barber wrote: > On Thu, May 23, 2013 at 06:09:43PM -0700, Jeremy Chadwick wrote: > > On Thu, May 23, 2013 at 08:18:33PM -0400, Michael L. Squires wrote: > > > I've just tested 8.4-RC3 using a different Supermicro 1U box with a fresh > > > installation of 8.4-RC3. I had problems with the installation, wouldn't > > > boot until I used a Windows 98 FDISK to write a master boot record > > > (no idea why; this system uses an Adaptec SATA 1.5 6-channel PCI-X > > > board with two > > > drives in RAID 1). > > > > > > Using the em0 interface there are no problems with DHCP; when I > > > switch to the fxp0 interface the interface starts going up/down in > > > the same manner as reported. > > > > > > The problem appears associated with "world", not with the kernel (running > > > the 8.4 kernel with the 8.3 world does not have this problem). > > > > > > This motherboard is an X5DPL-iGM with 2 Xeon 2.8GHz CPUs and 4 GB of RAM. > > > The other unit (an earlier board) has a Serverworks chipset with a single > > > Xeon CPU but also with a 100Mbit Intel Pro100 Ethernet port and a 1000Mbit > > > Intel Pro1000 Ethernet port. > > > > > > This unit isn't doing anything useful, so testing isn't a problem. > > > > Mike, Yong-Hyeon asked you a very important question which you didn't > > answer: > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073458.html > > > > If you assign a static IP address, does fxp0 behave properly? > > > > I'm also re-adding Yong-Hyeon to the CC list here. > > > > At this point, I am not convinced we have a problem with what will turn > out to be 8.4-RELEASE. > > There have been several attempts to ensure the upgraded version is > actually 8.4-RC3 (and again, 'uname -a' is not provided in this > email...). > > I find it very hard to believe that we have exactly one fxp(4) user > upgrading to 8.4-*. > > I'd really like to make sure that this is not an issue that will affect > an uncountable number of users, but truthfully, at this point have to > consider it a local configuration problem. I have numerous Supermicro 1U boxes sitting in my garage from closing down my hosting organisation back in August 2012. I am certain one or two of them have Intel NICs that use fxp(4) -- the problem is that I don't know what exact NIC and PHY model they use. >From what I can tell, there are at least two systems Mike has which experience this anomaly. One of those systems' dmesg: http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073440.html The relevant lines start at "fxp0: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 39EC3609; Fri, 24 May 2013 03:13:08 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [199.48.134.227]) by mx1.freebsd.org (Postfix) with ESMTP id 109552B7; Fri, 24 May 2013 03:13:07 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id D8BEB23F804; Thu, 23 May 2013 23:13:05 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.3 onyx.glenbarber.us D8BEB23F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Thu, 23 May 2013 23:13:03 -0400 From: Glen Barber To: Jeremy Chadwick Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524031303.GC28865@glenbarber.us> References: <20130508174721.GD1651@glenbarber.us> <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="p2kqVDKq5asng8Dg" Content-Disposition: inline In-Reply-To: <20130524030351.GA39091@icarus.home.lan> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: YongHyeon PYUN , freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 03:13:08 -0000 --p2kqVDKq5asng8Dg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 23, 2013 at 08:03:51PM -0700, Jeremy Chadwick wrote: > On Thu, May 23, 2013 at 09:21:17PM -0400, Glen Barber wrote: > > On Thu, May 23, 2013 at 06:09:43PM -0700, Jeremy Chadwick wrote: > > > On Thu, May 23, 2013 at 08:18:33PM -0400, Michael L. Squires wrote: > > > > I've just tested 8.4-RC3 using a different Supermicro 1U box with a= fresh > > > > installation of 8.4-RC3. I had problems with the installation, wou= ldn't > > > > boot until I used a Windows 98 FDISK to write a master boot record > > > > (no idea why; this system uses an Adaptec SATA 1.5 6-channel PCI-X > > > > board with two > > > > drives in RAID 1). > > > >=20 > > > > Using the em0 interface there are no problems with DHCP; when I > > > > switch to the fxp0 interface the interface starts going up/down in > > > > the same manner as reported. > > > >=20 > > > > The problem appears associated with "world", not with the kernel (r= unning > > > > the 8.4 kernel with the 8.3 world does not have this problem). > > > >=20 > > > > This motherboard is an X5DPL-iGM with 2 Xeon 2.8GHz CPUs and 4 GB o= f RAM. > > > > The other unit (an earlier board) has a Serverworks chipset with a = single > > > > Xeon CPU but also with a 100Mbit Intel Pro100 Ethernet port and a 1= 000Mbit > > > > Intel Pro1000 Ethernet port. > > > >=20 > > > > This unit isn't doing anything useful, so testing isn't a problem. > > >=20 > > > Mike, Yong-Hyeon asked you a very important question which you didn't > > > answer: > > >=20 > > > http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073458.html > > >=20 > > > If you assign a static IP address, does fxp0 behave properly? > > >=20 > > > I'm also re-adding Yong-Hyeon to the CC list here. > > >=20 > >=20 > > At this point, I am not convinced we have a problem with what will turn > > out to be 8.4-RELEASE. > >=20 > > There have been several attempts to ensure the upgraded version is > > actually 8.4-RC3 (and again, 'uname -a' is not provided in this > > email...). > >=20 > > I find it very hard to believe that we have exactly one fxp(4) user > > upgrading to 8.4-*. > >=20 > > I'd really like to make sure that this is not an issue that will affect > > an uncountable number of users, but truthfully, at this point have to > > consider it a local configuration problem. >=20 > I have numerous Supermicro 1U boxes sitting in my garage from closing > down my hosting organisation back in August 2012. I am certain one or > two of them have Intel NICs that use fxp(4) -- the problem is that I > don't know what exact NIC and PHY model they use. >=20 > >From what I can tell, there are at least two systems Mike has which > experience this anomaly. One of those systems' dmesg: >=20 > http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073440.html >=20 > The relevant lines start at "fxp0: the way down to "pci0:0:8:0: bad VPD cksum, remain 14". I'm not sure if > the bad VPD checksum message is relevant to the fxp0 device or not. >=20 > The 2nd system is mentioned above/in this post: >=20 > http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073530.html >=20 > But there's no verbose dmesg etc. for the 2nd system so I don't know if > it has the same NIC/PHY. >=20 My understanding from the start of this thread is that "both" machines are actually the same machine, but with different combinations of userland/kernel. (No, not arguing anything - only one person can answer if my understanding is correct or not.) > The model of NIC and PHY matters greatly; most users don't seem to > realise how important this is, they think in terms of "Intel vs. > Broadcom vs. Realtek". >=20 > Output from "pciconf -lvbc", specifically the lines relevant to the fxp0 > device, from both systems, would be highly beneficial. >=20 > In the meantime, I'll head down to my garage to see if I can find those > fxp(4) boxes and see if they're 85551s (I sure hope I haven't pulled the > CPUs/RAM from them). If I find a match, I can try to reproduce this. >=20 It has been quite costly now (time) waiting for information on this particular issue at this point, unfortunately. Glen --p2kqVDKq5asng8Dg Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJRntq/AAoJEFJPDDeguUajYAMH/RlsVfEQPoevSEoY6t7qTWDN 0uDAuTtxjwYzaevF/nItLTDsDWLsW7ZYsJ/ELEu6ckZolMG1g3yDi63t4lZ7FWTu 4778n8FLQzFivfssjE3GgLQ5pSrHXE3+J2RB4uMT7ztA50Exg5/soSPi4ooI6NV8 xMVJqPdGox4WgvILQmckvfaspfcj2nYO5V7vSZs9/d2Usv4L/Z80JP9+BczXBP92 FJDchLbZGHv+LshT0Sj98OcmZVqHTahWnf2OgVtXKP9DFP0TF7e9NQ7o9+fxd0Ou gWXmzQTdzgX4cwQFhHNKmhpmtUO5EcPrVfzHzhQp3HCZ09Umccvmchg1DKt+kZA= =hCSz -----END PGP SIGNATURE----- --p2kqVDKq5asng8Dg-- From owner-freebsd-stable@FreeBSD.ORG Fri May 24 03:38:08 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F39A0EDA for ; Fri, 24 May 2013 03:38:07 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:17]) by mx1.freebsd.org (Postfix) with ESMTP id BE6E13D8 for ; Fri, 24 May 2013 03:38:07 +0000 (UTC) Received: from omta10.emeryville.ca.mail.comcast.net ([76.96.30.28]) by qmta10.emeryville.ca.mail.comcast.net with comcast id ffYi1l0050cQ2SLAAfe70U; Fri, 24 May 2013 03:38:07 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta10.emeryville.ca.mail.comcast.net with comcast id ffe61l00K1t3BNj8Wfe6aB; Fri, 24 May 2013 03:38:07 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 7F80373A33; Thu, 23 May 2013 20:38:06 -0700 (PDT) Date: Thu, 23 May 2013 20:38:06 -0700 From: Jeremy Chadwick To: Glen Barber Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524033806.GA39720@icarus.home.lan> References: <20130508174721.GD1651@glenbarber.us> <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524031303.GC28865@glenbarber.us> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369366687; bh=+ZVjgXzrC8HKP6XYjHpIVp1ks117JofWSnitgqvUV+Q=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=jacwPhGFvpNBBpjKORAD6TGvDewOga9lvwD4ZumgmRqpGz3L42LIz6xP45kSomGVQ V4omP1pm9bQVmE8Ae/thRjj+UKPA6Wv1bC1+BEDocqQw9zMO6/AJ7LsLIh5/Nlp+U/ kLrDu9y/nwQuy+Zgkj3gF2wcVnNUFpjDVmJRXtRIf6RcGmngexBMvV9TI5Y5D1s7Ly YXMKUit3JxMsrrENsUMPcama4+cBwAsSoVuV+H9JiH8TcSV5/abcVWUbnHLuj5l6JU 5aWbxs9EtaUz4kVPALlJaDFliQyOzc7IBYTEkNTjTgCFALHc5JYX4yeXR3eX7fxyup ySxHrPktlITKw== Cc: YongHyeon PYUN , FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 03:38:08 -0000 On Thu, May 23, 2013 at 11:13:03PM -0400, Glen Barber wrote: > On Thu, May 23, 2013 at 08:03:51PM -0700, Jeremy Chadwick wrote: > > On Thu, May 23, 2013 at 09:21:17PM -0400, Glen Barber wrote: > > > On Thu, May 23, 2013 at 06:09:43PM -0700, Jeremy Chadwick wrote: > > > > On Thu, May 23, 2013 at 08:18:33PM -0400, Michael L. Squires wrote: > > > > > I've just tested 8.4-RC3 using a different Supermicro 1U box with a fresh > > > > > installation of 8.4-RC3. I had problems with the installation, wouldn't > > > > > boot until I used a Windows 98 FDISK to write a master boot record > > > > > (no idea why; this system uses an Adaptec SATA 1.5 6-channel PCI-X > > > > > board with two > > > > > drives in RAID 1). > > > > > > > > > > Using the em0 interface there are no problems with DHCP; when I > > > > > switch to the fxp0 interface the interface starts going up/down in > > > > > the same manner as reported. > > > > > > > > > > The problem appears associated with "world", not with the kernel (running > > > > > the 8.4 kernel with the 8.3 world does not have this problem). > > > > > > > > > > This motherboard is an X5DPL-iGM with 2 Xeon 2.8GHz CPUs and 4 GB of RAM. > > > > > The other unit (an earlier board) has a Serverworks chipset with a single > > > > > Xeon CPU but also with a 100Mbit Intel Pro100 Ethernet port and a 1000Mbit > > > > > Intel Pro1000 Ethernet port. > > > > > > > > > > This unit isn't doing anything useful, so testing isn't a problem. > > > > > > > > Mike, Yong-Hyeon asked you a very important question which you didn't > > > > answer: > > > > > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073458.html > > > > > > > > If you assign a static IP address, does fxp0 behave properly? > > > > > > > > I'm also re-adding Yong-Hyeon to the CC list here. > > > > > > > > > > At this point, I am not convinced we have a problem with what will turn > > > out to be 8.4-RELEASE. > > > > > > There have been several attempts to ensure the upgraded version is > > > actually 8.4-RC3 (and again, 'uname -a' is not provided in this > > > email...). > > > > > > I find it very hard to believe that we have exactly one fxp(4) user > > > upgrading to 8.4-*. > > > > > > I'd really like to make sure that this is not an issue that will affect > > > an uncountable number of users, but truthfully, at this point have to > > > consider it a local configuration problem. > > > > I have numerous Supermicro 1U boxes sitting in my garage from closing > > down my hosting organisation back in August 2012. I am certain one or > > two of them have Intel NICs that use fxp(4) -- the problem is that I > > don't know what exact NIC and PHY model they use. > > > > >From what I can tell, there are at least two systems Mike has which > > experience this anomaly. One of those systems' dmesg: > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073440.html > > > > The relevant lines start at "fxp0: > the way down to "pci0:0:8:0: bad VPD cksum, remain 14". I'm not sure if > > the bad VPD checksum message is relevant to the fxp0 device or not. > > > > The 2nd system is mentioned above/in this post: > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073530.html > > > > But there's no verbose dmesg etc. for the 2nd system so I don't know if > > it has the same NIC/PHY. > > > > My understanding from the start of this thread is that "both" machines > are actually the same machine, but with different combinations of > userland/kernel. (No, not arguing anything - only one person can answer > if my understanding is correct or not.) > > The model of NIC and PHY matters greatly; most users don't seem to > > realise how important this is, they think in terms of "Intel vs. > > Broadcom vs. Realtek". > > > > Output from "pciconf -lvbc", specifically the lines relevant to the fxp0 > > device, from both systems, would be highly beneficial. > > > > In the meantime, I'll head down to my garage to see if I can find those > > fxp(4) boxes and see if they're 85551s (I sure hope I haven't pulled the > > CPUs/RAM from them). If I find a match, I can try to reproduce this. > > > > It has been quite costly now (time) waiting for information on this > particular issue at this point, unfortunately. I made a typo above -- I meant to say "82551" not "85551". Anyways... Hearing you on FM. :-) Inventory of old systems of mine didn't take long. I had 3 systems; one used dual Broadcom NICs (so that's out), the other used dual Intel 82541EI NICs (which is driven by em(4) so that's out). The remaining system: - Supermicro 5010E -- Have CPU + RAM -- NIC: Intel DA82562EM -- NIC: Intel GD82559 -- Supermicro site states (1) Intel 82559 and (1) Intel VE CNR -- http://www.supermicro.com/products/system/1U/5010/SYS-5010E.cfm -- fxp(4) driver claims to support 82562EM and 82559 -- http://svnweb.freebsd.org/base/stable/8/sys/dev/fxp/if_fxp.c?revision=242909&view=markup However neither of these are 82551. Summary: I do have a system I can use to test fxp(4), however it does not use the Intel 82551 (in case this turns out to be a chip-specific driver bug). If someone wants me to test DHCP via fxp(4) on the above system (I can do so with both NICs), just let me know; it should only take me half an hour or so. I'll politely wait for someone to say "please do so" else won't bother. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 24 03:42:48 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 614D4102; Fri, 24 May 2013 03:42:48 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 3543560E; Fri, 24 May 2013 03:42:48 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id DEC5F23F804; Thu, 23 May 2013 23:42:46 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.3 onyx.glenbarber.us DEC5F23F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Thu, 23 May 2013 23:42:44 -0400 From: Glen Barber To: Jeremy Chadwick Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524034244.GD28865@glenbarber.us> References: <20130508174721.GD1651@glenbarber.us> <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="J5MfuwkIyy7RmF4Q" Content-Disposition: inline In-Reply-To: <20130524033806.GA39720@icarus.home.lan> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: YongHyeon PYUN , FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 03:42:48 -0000 --J5MfuwkIyy7RmF4Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: > If someone wants me to test DHCP via fxp(4) on the above system (I can > do so with both NICs), just let me know; it should only take me half an > hour or so. >=20 > I'll politely wait for someone to say "please do so" else won't bother. >=20 For the sake of completeness... "Please do so." :) Glen --J5MfuwkIyy7RmF4Q Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJRnuG0AAoJEFJPDDeguUajrbMH/jdvVtlbo0YP5IQeoit5Ejf4 atze9Tf4NxhAcCMQd++N4Aa+p+j2x+DbWBuoFfu+YbhUmLRhHJscyrLgYUmeowKV gYDWX1LItS/AhA60UBxtNn0MptIgSOumdb8tR7CeJwR7GG1YxNuqFw6bdN/QzmPr bd4hEcgVURhe8KQRETQoRxxBLZYsdbgPaKeYzWUWeQFhq67TNPTK36Y+1fxOmxgH Gm4uSLm6y6nCMvwlbrg3p/JafO/Jd5cCtFUa2Q8tYu64VHAeffEW8jSPNUUePz4G s8mLI9Ljp9O1sJ9fh4xjoQbl+R91flTaE9KUAUAwMYRBFZz0QTNliKgFIHgJiyY= =Bc66 -----END PGP SIGNATURE----- --J5MfuwkIyy7RmF4Q-- From owner-freebsd-stable@FreeBSD.ORG Fri May 24 04:40:38 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2442CCF for ; Fri, 24 May 2013 04:40:38 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:96]) by mx1.freebsd.org (Postfix) with ESMTP id E5EB08EA for ; Fri, 24 May 2013 04:40:37 +0000 (UTC) Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta09.emeryville.ca.mail.comcast.net with comcast id fgdw1l0041smiN4A9ggcMa; Fri, 24 May 2013 04:40:36 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta20.emeryville.ca.mail.comcast.net with comcast id fggc1l0011t3BNj8gggc22; Fri, 24 May 2013 04:40:36 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E6EB873A33; Thu, 23 May 2013 21:40:35 -0700 (PDT) Date: Thu, 23 May 2013 21:40:35 -0700 From: Jeremy Chadwick To: Glen Barber Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524044035.GA40957@icarus.home.lan> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524034244.GD28865@glenbarber.us> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369370436; bh=6rMlN1JsOecUCbxfxR8BMpNw0y7NDEJ/PHDDsNvVzHs=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=jEuGD7hOVIVUpyhG9327j4sxAF+e5uBNpFimPCkuNq7GjQMBywFq+Vl8JpBxB2IlH U5AEb4P0Tk34VLLtkc9ADfGw7zx2XorLLY59PMI8RWsLp7dB0lzCpnjKkzU6t86Hw/ UBACmwDBvIeSqvEjadA3QwsbChprU63sdv9VoRvLv2yQMjNZoFar3i5zbj0W0HhyIj TbE7QTiliXLPwJoKQri4exF5CQ9fL0hHy0zKlYXH99/asob6WvbteCD8rwRiFhgl7j Q5DEJLQy5v7Lcj3tbPo3t3wuIC+h2lnzZoswwIa+0+huzjluvTcKSjE/L8UVlz8Qd5 LKMaKT4lhSlaw== Cc: YongHyeon PYUN , freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 04:40:38 -0000 On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote: > On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: > > If someone wants me to test DHCP via fxp(4) on the above system (I can > > do so with both NICs), just let me know; it should only take me half an > > hour or so. > > > > I'll politely wait for someone to say "please do so" else won't bother. > > > > For the sake of completeness... > > "Please do so." :) Issue reproduced 100% reliably, even within sysinstall. ISO image used: ftp://ftp4.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/8.4/FreeBSD-8.4-RC3-i386-disc1.iso I just chose to Configure the system, selected Networking, chose NO to the IPv6 configuration choice, and YES to the DHCP configuration choice, then hit Alt-F2 to watch relevant output. This was the result: http://imgbin.org/index.php?page=image&id=13718 ...with the fxp0 physif up/down messages continuing indefinitely. fxp0 on the system is the Intel 82559. Shot of console's dmesg: http://imgbin.org/index.php?page=image&id=13720 Nothing is connected to fxp1. Key points for those asking me to help debug: - I only have VGA console on this box - I do not have an IDE hard disk of any sort for temporary OS installation, setup, kernel testing, etc.. - The system cannot boot USB media of any sort, so memsticks are out - The ATAPI drive is CD-only; there is no DVD support, so there's no easy way to get a "real" shell with full utilities (i.e. "Fixit") So if someone wants to take a stab at this, they'll need to do so and make me an ISO. Sorry that I can't make things easier. :-( This definitely needs to get fixed before 8.4-RELEASE. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 24 04:49:20 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8C028279 for ; Fri, 24 May 2013 04:49:20 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:227]) by mx1.freebsd.org (Postfix) with ESMTP id 56DDF942 for ; Fri, 24 May 2013 04:49:20 +0000 (UTC) Received: from omta05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by qmta12.emeryville.ca.mail.comcast.net with comcast id fc2b1l0040vp7WL01gpLKc; Fri, 24 May 2013 04:49:20 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta05.emeryville.ca.mail.comcast.net with comcast id fgpK1l00B1t3BNj8RgpKNL; Fri, 24 May 2013 04:49:19 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 1529573A33; Thu, 23 May 2013 21:49:19 -0700 (PDT) Date: Thu, 23 May 2013 21:49:19 -0700 From: Jeremy Chadwick To: Glen Barber Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524044919.GA41292@icarus.home.lan> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524044035.GA40957@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369370960; bh=1CZMWFVBlduLIuOViIzCxyBQNMJsJr6+qU638vCYvUk=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=iqreBg5o3YulPMG2ulK3QyrIiewWNqMW/Y7aH0Opy5S9lAni1rjUbySPLpeXnwPdJ lMCg0+OGzjr//kNyYVGA2jmo0AarLN7vnkYqknGbIFJE3YFl5GulVu8YmnXFUpTSce jTFqsb/cPu4MOao6F/60VSYr6At8TApkgFxbZmLV0MNYk+dQNcwlXNDUNGPv26iHui 45DeLPMh+1sXEVzNzF8VbaW7ItqLVk7040Fg6W0mtkSqs1O//cGXG89mQE7kErquZA IIkR1bNtPWEBQQ5YkFtgtxJ8DyfvjPDg0PpeTO6hfr53gkkMteNTepYV1In36WL615 RiGXgYR9Pv5ZA== Cc: YongHyeon PYUN , FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 04:49:20 -0000 On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: > On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote: > > On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: > > > If someone wants me to test DHCP via fxp(4) on the above system (I can > > > do so with both NICs), just let me know; it should only take me half an > > > hour or so. > > > > > > I'll politely wait for someone to say "please do so" else won't bother. > > > > > > > For the sake of completeness... > > > > "Please do so." :) > > Issue reproduced 100% reliably, even within sysinstall. > > {snip} Forgot to add: This issue ONLY happens when using DHCP. Statically assigning the IP address works fine; fxp0 goes down once, up once, then stays up indefinitely. I also tested network I/O in the statically-assigned scenario. Pinging the box from another machine on the LAN: $ ping 192.168.1.192 PING 192.168.1.192 (192.168.1.192): 56 data bytes 64 bytes from 192.168.1.192: icmp_seq=0 ttl=64 time=0.180 ms 64 bytes from 192.168.1.192: icmp_seq=1 ttl=64 time=0.138 ms 64 bytes from 192.168.1.192: icmp_seq=2 ttl=64 time=0.214 ms 64 bytes from 192.168.1.192: icmp_seq=3 ttl=64 time=0.165 ms 64 bytes from 192.168.1.192: icmp_seq=4 ttl=64 time=0.114 ms ^C --- 192.168.1.192 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.114/0.162/0.214/0.034 ms -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 24 04:56:26 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2C476409; Fri, 24 May 2013 04:56:26 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id F3977983; Fri, 24 May 2013 04:56:25 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 306B223F804; Fri, 24 May 2013 00:56:22 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.3 onyx.glenbarber.us 306B223F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Fri, 24 May 2013 00:56:20 -0400 From: Glen Barber To: Jeremy Chadwick Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524045620.GE28865@glenbarber.us> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4Epv4kl9IRBfg3rk" Content-Disposition: inline In-Reply-To: <20130524044035.GA40957@icarus.home.lan> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: YongHyeon PYUN , freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 04:56:26 -0000 --4Epv4kl9IRBfg3rk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: > [...] > So if someone wants to take a stab at this, they'll need to do so and > make me an ISO. Sorry that I can't make things easier. :-( >=20 > This definitely needs to get fixed before 8.4-RELEASE. >=20 *sigh*.... At this point, it is highly unlikely this will be fixed before 8.4-RELEASE. We are _far_ too deep into the release cycle. In fact, we are effectively done with the release, and waiting on release notes to be completed. I think this will likely be included in errata notes for the release. It is very unfortunate that this waited so long to be reported, as much time has passed since 8.4-BETA1... Glen --4Epv4kl9IRBfg3rk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJRnvL0AAoJEFJPDDeguUaj0k4H/1eB/nfjObIak8c+BvdSllLI 51+akpDVKR/qBfuRl2pfSHztLZutJlkvWL+LanoJlqLD2Wg4s8L4/g3YLQki3sgd Yde6o7AAWdgcNzMA602sAmow4Alulxn4K6cvBmZEz3mCHlA2B3EEa+Z1j5kouwPm 9MX8his3KJhHX6nyKbdsFumPTP5+ML/hblZ7bkIZWyCZyLCQNdNfF8qXz69XuSzg nO8wHR92UaERRBzjNodsWOKvprQFZoUTNF/8+2e6/5aupHI5AyyFWcbAmkw3jeyD lQpQfTqlyTTDNRSnPi0Vgvgv4JRMAEGNTev6YYU+Blry6oiGKCsWQYT21ywQJ5w= =27UM -----END PGP SIGNATURE----- --4Epv4kl9IRBfg3rk-- From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:03:59 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 508C05E1; Fri, 24 May 2013 05:03:59 +0000 (UTC) (envelope-from spork@bway.net) Received: from smtp1.bway.net (smtp1.v6.bway.net [IPv6:2607:d300:1::27]) by mx1.freebsd.org (Postfix) with ESMTP id 11A679CE; Fri, 24 May 2013 05:03:59 +0000 (UTC) Received: from toasty.sporklab.com (foon.sporktines.com [96.57.144.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: spork@bway.net) by smtp1.bway.net (Postfix) with ESMTPSA id BD94395854; Fri, 24 May 2013 01:03:50 -0400 (EDT) References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> In-Reply-To: <20130524044035.GA40957@icarus.home.lan> Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=windows-1252 Message-Id: Content-Transfer-Encoding: quoted-printable From: Charles Sprickman Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Date: Fri, 24 May 2013 01:03:49 -0400 To: Jeremy Chadwick X-Mailer: Apple Mail (2.1085) Cc: YongHyeon PYUN , Glen Barber , freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 05:03:59 -0000 On May 24, 2013, at 12:40 AM, Jeremy Chadwick wrote: > On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote: >> On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: >>> If someone wants me to test DHCP via fxp(4) on the above system (I = can >>> do so with both NICs), just let me know; it should only take me half = an >>> hour or so. >>>=20 >>> I'll politely wait for someone to say "please do so" else won't = bother. >>>=20 >>=20 >> For the sake of completeness... >>=20 >> "Please do so." :) >=20 > Issue reproduced 100% reliably, even within sysinstall. >=20 > ISO image used: >=20 > = ftp://ftp4.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/8.4/FreeBSD-8.4-RC3= -i386-disc1.iso >=20 > I just chose to Configure the system, selected Networking, chose NO to > the IPv6 configuration choice, and YES to the DHCP configuration = choice, > then hit Alt-F2 to watch relevant output. >=20 > This was the result: >=20 > http://imgbin.org/index.php?page=3Dimage&id=3D13718 >=20 > ...with the fxp0 physif up/down messages continuing indefinitely. >=20 > fxp0 on the system is the Intel 82559. Shot of console's dmesg: >=20 > http://imgbin.org/index.php?page=3Dimage&id=3D13720 >=20 > Nothing is connected to fxp1. >=20 > Key points for those asking me to help debug: >=20 > - I only have VGA console on this box > - I do not have an IDE hard disk of any sort for temporary OS There are machines in my garage that are supposed to go to the recycling = dump. I have old boot messages from one P-III box that indicates there's an = Intel 82559 chip onboard. I do have drives, and I do have a CD drive, although I'm uncertain as to = its condition. I can make a serial console available. USB booting is out of the question. I am currently out of blank CD-R's, but might be able to find my meager = stash of CD-RWs that I couldn't find last week=85 Failing that, can I = dd a memstick image onto a drive? Mr. Barber loves these machines, they are his favorites. :) C > installation, setup, kernel testing, etc.. > - The system cannot boot USB media of any sort, so memsticks are out > - The ATAPI drive is CD-only; there is no DVD support, so there's no > easy way to get a "real" shell with full utilities (i.e. "Fixit") >=20 > So if someone wants to take a stab at this, they'll need to do so and > make me an ISO. Sorry that I can't make things easier. :-( >=20 > This definitely needs to get fixed before 8.4-RELEASE. >=20 > --=20 > | Jeremy Chadwick jdc@koitsu.org | > | UNIX Systems Administrator http://jdc.koitsu.org/ | > | Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:11:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9E4C6821 for ; Fri, 24 May 2013 05:11:41 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:32]) by mx1.freebsd.org (Postfix) with ESMTP id 25528A23 for ; Fri, 24 May 2013 05:11:41 +0000 (UTC) Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta03.emeryville.ca.mail.comcast.net with comcast id fh0w1l0041smiN4A3hBgss; Fri, 24 May 2013 05:11:40 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta20.emeryville.ca.mail.comcast.net with comcast id fhBf1l00h1t3BNj8ghBghF; Fri, 24 May 2013 05:11:40 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id D905D73A33; Thu, 23 May 2013 22:11:39 -0700 (PDT) Date: Thu, 23 May 2013 22:11:39 -0700 From: Jeremy Chadwick To: Glen Barber Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524051139.GA41712@icarus.home.lan> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> <20130524045620.GE28865@glenbarber.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524045620.GE28865@glenbarber.us> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369372300; bh=t2XZyOpkGYvLvvECZcpT7h3jS36rBNc7sFcVtoMurNQ=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=fk9i42kVcO8FpXevyrccdOCQVpbp6JXqhudEB3gXhWjW9irGDCcX9vA0eC+HnnKgC 4SY8PpE8KXsP+QanjAj50PLvk7rJmdnVJYVX0WAXEr8CV3ZWPi6zHQbJoKNneZ1juT 5uZDc4xfdShzoAWJ7JzKw3yOZx/80DjxazVJ1Cmt2ElG2Y6KWMFZKfAD5+hTKdbtGM WSbtsFFVLcmpo4IW+fjb14LKPRQz4ciVHbaV+hbv0nSkzAdU3D1kqaeUSal3TGDbhp mJ2ekrYFPpdJF2XotFJphGcxMyd4GKN9ArqATLXHivngXJDceyrWIVUAnlxrl+LKcG fzODWN2GMZn8w== Cc: YongHyeon PYUN , FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 05:11:41 -0000 On Fri, May 24, 2013 at 12:56:20AM -0400, Glen Barber wrote: > On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: > > [...] > > So if someone wants to take a stab at this, they'll need to do so and > > make me an ISO. Sorry that I can't make things easier. :-( > > > > This definitely needs to get fixed before 8.4-RELEASE. > > > > *sigh*.... > > At this point, it is highly unlikely this will be fixed before > 8.4-RELEASE. We are _far_ too deep into the release cycle. In fact, we > are effectively done with the release, and waiting on release notes to > be completed. > > I think this will likely be included in errata notes for the release. I urge you to meet with others in Release Engineering and discuss this fully. This is major enough that, once fixed, it warrants an immediate binary update (to the kernel + if_fxp.ko) pushed out via freebsd-update. fxp(4) is a commonly-used driver; it isn't something rare/uncommon. Also remember at this stage we don't know if it's a specific PHY model or specific NIC model (or series) which triggers it. For all we know it could affect everything that fxp(4) drives. Please don't forget that FreeBSD has a very well-established history of having rock-solid Intel NIC support. Sure, mistakes happen, we're human, bugs get introduced, but this does not bode well -- meaning I would expect Slashdot et al to pick up on this. > It is very unfortunate that this waited so long to be reported, as much > time has passed since 8.4-BETA1... This is what happens when people socially proliferate the belief that "RELEASE is rock solid/stable, don't run stable/X" -- the number of people who test what changes between RELEASE builds is vastly smaller comparatively. I've only been saying this for the past 15 years, so it's even more unfortunate that people keep believing it. :/ -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:18:29 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C2F81BDF; Fri, 24 May 2013 05:18:29 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 8C68CA8B; Fri, 24 May 2013 05:18:29 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r4O5ISEF046101; Fri, 24 May 2013 05:18:28 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r4O5IS9S046100; Fri, 24 May 2013 05:18:28 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 24 May 2013 05:18:28 GMT Message-Id: <201305240518.r4O5IS9S046100@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on arm/arm Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 05:18:29 -0000 TB --- 2013-05-24 03:55:19 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-05-24 03:55:19 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-05-24 03:55:19 - starting RELENG_9 tinderbox run for arm/arm TB --- 2013-05-24 03:55:19 - cleaning the object tree TB --- 2013-05-24 03:55:19 - /usr/local/bin/svn stat /src TB --- 2013-05-24 03:55:24 - At svn revision 250954 TB --- 2013-05-24 03:55:25 - building world TB --- 2013-05-24 03:55:25 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 03:55:25 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 03:55:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 03:55:25 - SRCCONF=/dev/null TB --- 2013-05-24 03:55:25 - TARGET=arm TB --- 2013-05-24 03:55:25 - TARGET_ARCH=arm TB --- 2013-05-24 03:55:25 - TZ=UTC TB --- 2013-05-24 03:55:25 - __MAKE_CONF=/dev/null TB --- 2013-05-24 03:55:25 - cd /src TB --- 2013-05-24 03:55:25 - /usr/bin/make -B buildworld >>> World build started on Fri May 24 03:55:26 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri May 24 05:17:46 UTC 2013 TB --- 2013-05-24 05:17:46 - cd /src/sys/arm/conf TB --- 2013-05-24 05:17:46 - /usr/sbin/config -m AVILA TB --- 2013-05-24 05:17:46 - building AVILA kernel TB --- 2013-05-24 05:17:46 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 05:17:46 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 05:17:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 05:17:46 - SRCCONF=/dev/null TB --- 2013-05-24 05:17:46 - TARGET=arm TB --- 2013-05-24 05:17:46 - TARGET_ARCH=arm TB --- 2013-05-24 05:17:46 - TZ=UTC TB --- 2013-05-24 05:17:46 - __MAKE_CONF=/dev/null TB --- 2013-05-24 05:17:46 - cd /src TB --- 2013-05-24 05:17:46 - /usr/bin/make -B buildkernel KERNCONF=AVILA >>> Kernel build for AVILA started on Fri May 24 05:17:46 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -mbig-endian -c -x assembler-with-cpp -DLOCORE -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/arm/arm/locore.S cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/cam/cam.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/cam/cam_periph.c /src/sys/cam/cam_periph.c: In function 'cam_periph_mapmem': /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_MASK' undeclared (first use in this function) /src/sys/cam/cam_periph.c:736: error: (Each undeclared identifier is reported only once /src/sys/cam/cam_periph.c:736: error: for each function it appears in.) /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_VADDR' undeclared (first use in this function) *** Error code 1 Stop in /obj/arm.arm/src/sys/AVILA. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-05-24 05:18:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-24 05:18:28 - ERROR: failed to build AVILA kernel TB --- 2013-05-24 05:18:28 - 3043.30 user 582.96 system 4988.62 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-arm-arm.full From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:24:28 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D0390D96; Fri, 24 May 2013 05:24:28 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [199.48.134.227]) by mx1.freebsd.org (Postfix) with ESMTP id AC040ACE; Fri, 24 May 2013 05:24:28 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id E3B1F23F804; Fri, 24 May 2013 01:24:26 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.3 onyx.glenbarber.us E3B1F23F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Fri, 24 May 2013 01:24:24 -0400 From: Glen Barber To: Jeremy Chadwick Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524052424.GF28865@glenbarber.us> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> <20130524045620.GE28865@glenbarber.us> <20130524051139.GA41712@icarus.home.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7cm2iqirTL37Ot+N" Content-Disposition: inline In-Reply-To: <20130524051139.GA41712@icarus.home.lan> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: YongHyeon PYUN , FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 05:24:28 -0000 --7cm2iqirTL37Ot+N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Speaking entirely on behalf of myself now... On Thu, May 23, 2013 at 10:11:39PM -0700, Jeremy Chadwick wrote: > > I think this will likely be included in errata notes for the release. >=20 > I urge you to meet with others in Release Engineering and discuss this > fully. This is major enough that, once fixed, it warrants an immediate > binary update (to the kernel + if_fxp.ko) pushed out via freebsd-update. >=20 It can be solved with a -pN update after 8.4-RELEASE is out. > fxp(4) is a commonly-used driver; it isn't something rare/uncommon. >=20 Right. So why do we have exactly 1 (now 2) reports of this? We are already behind the release schedule. There have been 4 "Hey, the next release is available for testing, so please do so" announcements. At this stage, holding up this release for last-minute (not last-minute code changes, either) reports will do nothing for the FreeBSD Project as a whole but hold up the remaining releases scheduled for the remainder of the year. > Also remember at this stage we don't know if it's a specific PHY model > or specific NIC model (or series) which triggers it. For all we know it > could affect everything that fxp(4) drives. >=20 Right. Without this information, we simply cannot hold off the release indefinitely. I've asked the OP to do some very specific things, all without yielding results, as well as replies from others. > Please don't forget that FreeBSD has a very well-established history of > having rock-solid Intel NIC support. Sure, mistakes happen, we're > human, bugs get introduced, but this does not bode well -- meaning I > would expect Slashdot et al to pick up on this. >=20 This is not a last minute bug. This is a last minute report, sadly. Glen --7cm2iqirTL37Ot+N Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJRnvmIAAoJEFJPDDeguUaj7bUH/RV6ysx/1ZzZexqBq6QVJ60U yrr7gkABtzM2vpwgc3hAy/A8b3bturjyzW375ORav25CkbvInmmVdgVe5lKb4BmK KZlgVFbscN1mYygLX4YvgdkHsJozH21mqLrXPDoe2dgdifg+d8xwLPBoycRGhReR FKGsqbwFJ843bHcqoLHJXSesYrRKYQEl0302B0ajd5SfVMDMtAk4muk3HmS0rd8y J3b2G63WJAewKWSshlecYzrGHfIej2f7VhciTfvmsJrYl6+e1YqVMozepSR1aerE eVKIymZmKJ73VGgfKi+W849TA39tkZ1VgVhqOCtV2xoS/jNno35B9bjBj27TC5Q= =ssXG -----END PGP SIGNATURE----- --7cm2iqirTL37Ot+N-- From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:27:56 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B8AEDD2; Fri, 24 May 2013 05:27:56 +0000 (UTC) (envelope-from jpaetzel@FreeBSD.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 74C22B01; Fri, 24 May 2013 05:27:56 +0000 (UTC) Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 9B90620AF0; Fri, 24 May 2013 01:27:55 -0400 (EDT) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 24 May 2013 01:27:55 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=references:mime-version:in-reply-to :content-type:content-transfer-encoding:message-id:cc:from :subject:date:to; s=smtpout; bh=1iGdiF8BmWT/1Z3TNd+wmQFYknE=; b= cYou4r6z5QpTJ0C9D+wuDEwzCWRCQSM8PpS4g0Duj+WIl3e0eMbNnY45/foME87R d5V+tU/HgLlBM47TfsDbPGWSvip/aaJVI5pXLFypasEJY9gWrq+mEo8D0K54FqJO rGG2GBR/7Im1rIGc5c7NCqTkc0MxzkmViSqc5H5YC9E= X-Sasl-enc: KBl+or/AjwAslrBJU5eldKt2vrH4Au2tkzKPtxRrCmhl 1369373275 Received: from [10.59.35.195] (unknown [166.137.184.74]) by mail.messagingengine.com (Postfix) with ESMTPA id 2941B200064; Fri, 24 May 2013 01:27:55 -0400 (EDT) References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> <20130524045620.GE28865@glenbarber.us> <20130524051139.GA41712@icarus.home.lan> Mime-Version: 1.0 (1.0) In-Reply-To: <20130524051139.GA41712@icarus.home.lan> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <2690F8C5-62DF-4F0F-9F40-759CA870CF88@FreeBSD.org> X-Mailer: iPhone Mail (10B350) From: Josh Paetzel Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Date: Thu, 23 May 2013 22:26:31 -0700 To: Jeremy Chadwick Cc: YongHyeon PYUN , Glen Barber , "freebsd-stable@freebsd.org" , FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 05:27:56 -0000 At this point fxp hardware is over a decade old. I'm loath to introduce dela= ys at the end of the runway for this issue.=20 Keep in mind that delays to 8.4 are pushed directly on to delays for 9.2, wh= ich won't be started until 8.4 is completed, and is desperately needed. (9.1= doesn't have drivers for common shipping hardware for example). Factors lik= e these as well as the age of fxp hardware drive my decision to complete 8.4= and push this fix in to EN territory.=20 Thanks, Josh Paetzel FreeBSD - The Power to Serve On May 23, 2013, at 10:11 PM, Jeremy Chadwick wrote: > On Fri, May 24, 2013 at 12:56:20AM -0400, Glen Barber wrote: >> On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: >>> [...] >>> So if someone wants to take a stab at this, they'll need to do so and >>> make me an ISO. Sorry that I can't make things easier. :-( >>>=20 >>> This definitely needs to get fixed before 8.4-RELEASE. >>=20 >> *sigh*.... >>=20 >> At this point, it is highly unlikely this will be fixed before >> 8.4-RELEASE. We are _far_ too deep into the release cycle. In fact, we >> are effectively done with the release, and waiting on release notes to >> be completed. >>=20 >> I think this will likely be included in errata notes for the release. >=20 > I urge you to meet with others in Release Engineering and discuss this > fully. This is major enough that, once fixed, it warrants an immediate > binary update (to the kernel + if_fxp.ko) pushed out via freebsd-update. >=20 > fxp(4) is a commonly-used driver; it isn't something rare/uncommon. >=20 > Also remember at this stage we don't know if it's a specific PHY model > or specific NIC model (or series) which triggers it. For all we know it > could affect everything that fxp(4) drives. >=20 > Please don't forget that FreeBSD has a very well-established history of > having rock-solid Intel NIC support. Sure, mistakes happen, we're > human, bugs get introduced, but this does not bode well -- meaning I > would expect Slashdot et al to pick up on this. >=20 >> It is very unfortunate that this waited so long to be reported, as much >> time has passed since 8.4-BETA1... >=20 > This is what happens when people socially proliferate the belief that > "RELEASE is rock solid/stable, don't run stable/X" -- the number of > people who test what changes between RELEASE builds is vastly smaller > comparatively. I've only been saying this for the past 15 years, so > it's even more unfortunate that people keep believing it. :/ >=20 > --=20 > | Jeremy Chadwick jdc@koitsu.org | > | UNIX Systems Administrator http://jdc.koitsu.org/ | > | Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:32:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 40DBD240; Fri, 24 May 2013 05:32:23 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com [209.85.217.170]) by mx1.freebsd.org (Postfix) with ESMTP id 90896B46; Fri, 24 May 2013 05:32:22 +0000 (UTC) Received: by mail-lb0-f170.google.com with SMTP id t13so4256733lbd.29 for ; Thu, 23 May 2013 22:32:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=pJzJo7uyESPGRG6Op9LXCGl+m4jS9e02UbpB4E7t7HM=; b=1ICYu4Oa5XBrClHsEtmdiWMsTRYhawg40IsUp4O6vy4W9qhgLM9UhJu6xCklNTw/jZ 6dQZPuPdJtKiiVUhFrI504yB3iOgKkB/K+wY8FaiV8dJbrodkZhLbfZbEtWD+p/VmXLd MGof1WBWHrKn2XyKOjUA7ppcXvU41gKO58s3pcdDjqvMfz/vN2W2d9Sx0MIS2pxPTn/G Lqa3DfV8raSXVZdN7AQAUwNGyFUMufld3DIYiP5SLB464ZSEoWWS2CujPxk2cs/7EaIT gCjMbReNOSY7eLP/RuB36JT60CAnQ6Qt6pUc1R15s9G059wj9cpYXW7DoxfcMBZTof/E lLaQ== X-Received: by 10.112.129.67 with SMTP id nu3mr1409127lbb.38.1369373541028; Thu, 23 May 2013 22:32:21 -0700 (PDT) Received: from localhost ([188.230.122.226]) by mx.google.com with ESMTPSA id n7sm5861240lbd.12.2013.05.23.22.32.18 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 23 May 2013 22:32:19 -0700 (PDT) Date: Fri, 24 May 2013 08:32:16 +0300 From: Mikolaj Golub To: Dmitry Morozovsky Subject: Re: Proposed MFC to hastctl: compact 'status' and introduce 'list' command Message-ID: <20130524053215.GA12310@gmail.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 05:32:23 -0000 On Fri, May 24, 2013 at 12:54:56AM +0400, Dmitry Morozovsky wrote: > Dear colleagues, > > is there any objection for MFCing the change introduced in > > http://svnweb.freebsd.org/changeset/base/248291 > > (the most major change: compacting output of `hastctl status' to one-liner per > provider; old output is retained as `list' command) > > to at least stable/9 ? If we agreed to merge, I would prefer to both stable/9 and 8 to have divergence between branches as minimal as possible. > The reason I'm asking is that it could lead to changes in hast-related scripts > which one use in production. > > If no objections are received I'm (with the generous support from trociny, > thank you Mikolaj!) tend to merge it after, say, 2 weeks. > > Thanks! > > -- > Sincerely, > D.Marck [DM5020, MCK-RIPE, DM3-RIPN] > [ FreeBSD committer: marck@FreeBSD.org ] > ------------------------------------------------------------------------ > *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** > ------------------------------------------------------------------------ > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:35:44 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 94708385; Fri, 24 May 2013 05:35:44 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 10F48B7C; Fri, 24 May 2013 05:35:43 +0000 (UTC) Received: from alph.d.allbsd.org (p2175-ipbf701funabasi.chiba.ocn.ne.jp [122.25.209.175]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r4O5ZQB7038992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 May 2013 14:35:37 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.5/8.14.5) with ESMTP id r4O5ZOe2091371; Fri, 24 May 2013 14:35:26 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Fri, 24 May 2013 14:34:35 +0900 (JST) Message-Id: <20130524.143435.828617708137294793.hrs@allbsd.org> To: jdc@koitsu.org Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 From: Hiroki Sato In-Reply-To: <20130524044035.GA40957@icarus.home.lan> References: <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Fri_May_24_14_34_35_2013_232)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Fri, 24 May 2013 14:35:37 +0900 (JST) X-Spam-Status: No, score=-94.2 required=13.0 tests=CONTENT_TYPE_PRESENT, ONLY1HOPDIRECT,QENCPTR1,RCVD_IN_PBL,SAMEHELOBY2HOP,TO_NO_BRKTS_PCNT, USER_IN_WHITELIST,X_CHINESE_RELAY autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: pyunyh@gmail.com, gjb@FreeBSD.org, re@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 05:35:44 -0000 ----Security_Multipart(Fri_May_24_14_34_35_2013_232)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jeremy Chadwick wrote in <20130524044035.GA40957@icarus.home.lan>: jd> On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote: jd> > On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: jd> > > If someone wants me to test DHCP via fxp(4) on the above system (I can jd> > > do so with both NICs), just let me know; it should only take me half an jd> > > hour or so. jd> > > jd> > > I'll politely wait for someone to say "please do so" else won't bother. jd> > > jd> > jd> > For the sake of completeness... jd> > jd> > "Please do so." :) jd> jd> Issue reproduced 100% reliably, even within sysinstall. jd> jd> ISO image used: jd> jd> ftp://ftp4.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/8.4/FreeBSD-8.4-RC3-i386-disc1.iso jd> jd> I just chose to Configure the system, selected Networking, chose NO to jd> the IPv6 configuration choice, and YES to the DHCP configuration choice, jd> then hit Alt-F2 to watch relevant output. jd> jd> This was the result: jd> jd> http://imgbin.org/index.php?page=image&id=13718 jd> jd> ...with the fxp0 physif up/down messages continuing indefinitely. jd> jd> fxp0 on the system is the Intel 82559. Shot of console's dmesg: jd> jd> http://imgbin.org/index.php?page=image&id=13720 Hmm, I tried RC3 on one of my test machines which has fxp0: ---- FreeBSD 8.4-RC3 #0 r250307: Tue May 7 04:40:16 UTC 2013 root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 ... fxp0: port 0x2800-0x283f mem 0xc4ffe000-0xc4ffefff,0xc4e00000-0xc4efffff irq 10 at device 3.0 on pci0 miibus0: on fxp0 inphy0: PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow fxp0: Ethernet address: 00:02:a5:eb:14:93 fxp0: [ITHREAD] fxp0@pci0:0:3:0: class=0x020000 card=0xb1340e11 chip=0x12298086 rev=0x08 hdr=0x00 vendor = 'Intel Corporation' device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class = network subclass = ethernet dev.inphy.0.%desc: i82555 10/100 media interface dev.inphy.0.%driver: inphy dev.inphy.0.%location: phyno=1 dev.inphy.0.%pnpinfo: oui=0xaa00 model=0x15 rev=0x4 dev.inphy.0.%parent: miibus0 ---- It worked well for a PXE boot at least. I will give dhclient a try later. -- Hiroki ----Security_Multipart(Fri_May_24_14_34_35_2013_232)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlGe++sACgkQTyzT2CeTzy3CUACglRQbzzGzCAlii2b5aY6qjahb 8mcAoK+UVrWKF8OblaHFnvCpU7xvadYq =VQx6 -----END PGP SIGNATURE----- ----Security_Multipart(Fri_May_24_14_34_35_2013_232)---- From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:45:24 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CE70E5D2 for ; Fri, 24 May 2013 05:45:24 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:211]) by mx1.freebsd.org (Postfix) with ESMTP id 99E43CE9 for ; Fri, 24 May 2013 05:45:24 +0000 (UTC) Received: from omta10.emeryville.ca.mail.comcast.net ([76.96.30.28]) by qmta11.emeryville.ca.mail.comcast.net with comcast id fhlF1l0010cQ2SLABhlQRE; Fri, 24 May 2013 05:45:24 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta10.emeryville.ca.mail.comcast.net with comcast id fhlP1l00P1t3BNj8WhlPpf; Fri, 24 May 2013 05:45:24 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 55A1E73A33; Thu, 23 May 2013 22:45:23 -0700 (PDT) Date: Thu, 23 May 2013 22:45:23 -0700 From: Jeremy Chadwick To: Glen Barber Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524054523.GA42525@icarus.home.lan> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> <20130524045620.GE28865@glenbarber.us> <20130524051139.GA41712@icarus.home.lan> <20130524052424.GF28865@glenbarber.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524052424.GF28865@glenbarber.us> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369374324; bh=9zWAf4NPVXcCRi8uSfejs1lHlucqtBv09gmaGr8aX/A=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=oUBKuGd/Mk6sY70NT69k30m56hCCl+yvqK8xg/fT2dHzoJwUfsTkh6HUARxBfBbzv hKyhfVAJFBpdmjo1Z2a5HoCsJ7TQctdcMF3TVREQl+wz87yDX5njdRakv6gCBxbtnk xrbWyUf8FMWpzMzzvNVkzTBW3noS7OG8w9Y3KbOBM2JJ9DW/Fb3LB9MP40a7bWpgJb eXLac8w7a3JkR5oOR+rG94ESmQEw1yQP2C69hAAmsq65H+IIWc/6BsNpje/go203Ir 7uvN4wvnYphTXiixDUHKY38J6/ONTBaNwej3f0XlKfKgBfA68Tej95pHSELSniApmw 0q8hI1B3yOQwQ== Cc: YongHyeon PYUN , FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 05:45:24 -0000 On Fri, May 24, 2013 at 01:24:24AM -0400, Glen Barber wrote: > Speaking entirely on behalf of myself now... > > On Thu, May 23, 2013 at 10:11:39PM -0700, Jeremy Chadwick wrote: > > > I think this will likely be included in errata notes for the release. > > > > I urge you to meet with others in Release Engineering and discuss this > > fully. This is major enough that, once fixed, it warrants an immediate > > binary update (to the kernel + if_fxp.ko) pushed out via freebsd-update. > > > > It can be solved with a -pN update after 8.4-RELEASE is out. Not that I'm calling the shots or anything, but: Let's go with that, combined with an included mention in the Errata section of the Release Notes as you initially mentioned. Sorry I can't be of more help; Charles' environment sounds like it would be better-suited for testing, and I'm sure Michael can test out a patch if/when someone gets around to poking at things. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:47:36 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 542A27E4; Fri, 24 May 2013 05:47:36 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by mx1.freebsd.org (Postfix) with ESMTP id 2365ED15; Fri, 24 May 2013 05:47:36 +0000 (UTC) Received: by mail-pd0-f175.google.com with SMTP id 6so3404852pdd.20 for ; Thu, 23 May 2013 22:47:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=GUSypoip906UDecrQ7QTvxBqk+Hz2SIM02+RcVFWiis=; b=PsAMrcQ7JreUzvkj/+QAmwVuhahaEr2jsy17q5k/zcCs8HZ3ZwGhebg3oRzavkkvit k2RBF22KFUOBy++wcRcga7VHK4SI8vV/aH8bIWAduoSoHfJCytW6g1NFB8SkX8408Jcm 3gtpK48laaWWqGPsNeHHCHux+Z396oOjdFnM6fheoAKtZCn81fbdOJHHW6wfP5WuiMAA odjBqpItEnzBw1l+7/T6yl0+LafgiUmsjHYk5krdeOLRhSojJeq5gCo+9N1EHCMyv6G2 GuzQBkiVpQehwT8ZoC/e9Pw+SxTvKEMvfbWqTGeBVlViySNSDOLKY99whuLqF0etSPRr DdSw== X-Received: by 10.68.13.228 with SMTP id k4mr15806483pbc.215.1369374450642; Thu, 23 May 2013 22:47:30 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id bs2sm15948330pad.17.2013.05.23.22.47.27 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 23 May 2013 22:47:29 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 24 May 2013 14:47:20 +0900 From: YongHyeon PYUN Date: Fri, 24 May 2013 14:47:20 +0900 To: Jeremy Chadwick Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524054720.GA1496@michelle.cdnetworks.com> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> <20130524044919.GA41292@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524044919.GA41292@icarus.home.lan> User-Agent: Mutt/1.4.2.3i Cc: Glen Barber , freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 05:47:36 -0000 On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote: > On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: > > On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote: > > > On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: > > > > If someone wants me to test DHCP via fxp(4) on the above system (I can > > > > do so with both NICs), just let me know; it should only take me half an > > > > hour or so. > > > > > > > > I'll politely wait for someone to say "please do so" else won't bother. > > > > > > > > > > For the sake of completeness... > > > > > > "Please do so." :) > > > > Issue reproduced 100% reliably, even within sysinstall. > > > > {snip} > > Forgot to add: > > This issue ONLY happens when using DHCP. > > Statically assigning the IP address works fine; fxp0 goes down once, > up once, then stays up indefinitely. I asked Mike to try backing out dhclient(8) change(r247336) but it seems he missed that. Jeremy, could you try that? I guess dhclient(8) does not like flow-control negotiation of fxp(4) after link establishment. > > I also tested network I/O in the statically-assigned scenario. Pinging > the box from another machine on the LAN: > > $ ping 192.168.1.192 > PING 192.168.1.192 (192.168.1.192): 56 data bytes > 64 bytes from 192.168.1.192: icmp_seq=0 ttl=64 time=0.180 ms > 64 bytes from 192.168.1.192: icmp_seq=1 ttl=64 time=0.138 ms > 64 bytes from 192.168.1.192: icmp_seq=2 ttl=64 time=0.214 ms > 64 bytes from 192.168.1.192: icmp_seq=3 ttl=64 time=0.165 ms > 64 bytes from 192.168.1.192: icmp_seq=4 ttl=64 time=0.114 ms > ^C > --- 192.168.1.192 ping statistics --- > 5 packets transmitted, 5 packets received, 0.0% packet loss > round-trip min/avg/max/stddev = 0.114/0.162/0.214/0.034 ms From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:58:34 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0C1BCC26 for ; Fri, 24 May 2013 05:58:34 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:211]) by mx1.freebsd.org (Postfix) with ESMTP id 885ABDD6 for ; Fri, 24 May 2013 05:58:33 +0000 (UTC) Received: from omta19.emeryville.ca.mail.comcast.net ([76.96.30.76]) by qmta11.emeryville.ca.mail.comcast.net with comcast id fhvp1l0031eYJf8ABhyZ0L; Fri, 24 May 2013 05:58:33 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta19.emeryville.ca.mail.comcast.net with comcast id fhyY1l00R1t3BNj01hyY7f; Fri, 24 May 2013 05:58:33 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 7763773A33; Thu, 23 May 2013 22:58:32 -0700 (PDT) Date: Thu, 23 May 2013 22:58:32 -0700 From: Jeremy Chadwick To: YongHyeon PYUN Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524055832.GA42673@icarus.home.lan> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524054720.GA1496@michelle.cdnetworks.com> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369375113; bh=w+iL3L+LK2+aPkNnfeXppJYHjevC6RPhnzwSYW4fmHM=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=iOg/CG8ncfR88nyD/4p05n8D5nWt4ILSgns/3IG1bzGs0Q3IHGT/17StTJTWRCEcv etKMt6bSrLbhGB8TfRn2xvbpZIkFwqCHcD+0zFque0fREoFtCJHdAnSxWQwG6vi3VX gwYV5oVgqrfh90MotB+EaPEL+nBPfFBEM7E12gczts5iWSLn+y3KdaiPRqfqjNAQV9 zQs61ZQpH5MAhv48dAO1ZXkPGFaTwCHGVq80jMGkKgc6h9hxgbNNZo9Tfpohwe1ySJ c3BXDiFXHRYtMY4RC7V2auqF+Ffz7oqmMj55JVeVtDG8XAAxCK+TdPAcm5n3Di42vA w2U/JRMXra9tw== Cc: Glen Barber , freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 05:58:34 -0000 On Fri, May 24, 2013 at 02:47:20PM +0900, YongHyeon PYUN wrote: > On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote: > > On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: > > > On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote: > > > > On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: > > > > > If someone wants me to test DHCP via fxp(4) on the above system (I can > > > > > do so with both NICs), just let me know; it should only take me half an > > > > > hour or so. > > > > > > > > > > I'll politely wait for someone to say "please do so" else won't bother. > > > > > > > > > > > > > For the sake of completeness... > > > > > > > > "Please do so." :) > > > > > > Issue reproduced 100% reliably, even within sysinstall. > > > > > > {snip} > > > > Forgot to add: > > > > This issue ONLY happens when using DHCP. > > > > Statically assigning the IP address works fine; fxp0 goes down once, > > up once, then stays up indefinitely. > > I asked Mike to try backing out dhclient(8) change(r247336) but it > seems he missed that. Jeremy, could you try that? > > I guess dhclient(8) does not like flow-control negotiation of > fxp(4) after link establishment. I can't test anything without an ISO -- the system in question is truly "bare-bones" (no hard disk, can't boot USB memsticks, etc.). I'm not a good test subject for changes on this one, I'm sorry to say. :-( If there's some way to disable flow-control negotiation in fxp(4) or miibus(4) via loader, I can try that, but I don't know what the MIB name would be. If r247336 turns out to be the cause: ironic, as r247336 references PR 166656, which was tested against -- wait for it -- xl(4). People in *this* thread are saying "screw legacy hardware" yet the PR is for something as old as the 3C905B? Maybe I should bow out of this thread before I have an aneurysm. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 24 06:55:46 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BA024E34; Fri, 24 May 2013 06:55:46 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 81268A3; Fri, 24 May 2013 06:55:46 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r4O6tkCt060360; Fri, 24 May 2013 06:55:46 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r4O6tjxA060345; Fri, 24 May 2013 06:55:45 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 24 May 2013 06:55:45 GMT Message-Id: <201305240655.r4O6tjxA060345@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on i386/pc98 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 06:55:46 -0000 TB --- 2013-05-24 03:55:19 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-05-24 03:55:19 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-05-24 03:55:19 - starting RELENG_9 tinderbox run for i386/pc98 TB --- 2013-05-24 03:55:19 - cleaning the object tree TB --- 2013-05-24 03:55:19 - /usr/local/bin/svn stat /src TB --- 2013-05-24 03:55:24 - At svn revision 250954 TB --- 2013-05-24 03:55:25 - building world TB --- 2013-05-24 03:55:25 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 03:55:25 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 03:55:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 03:55:25 - SRCCONF=/dev/null TB --- 2013-05-24 03:55:25 - TARGET=pc98 TB --- 2013-05-24 03:55:25 - TARGET_ARCH=i386 TB --- 2013-05-24 03:55:25 - TZ=UTC TB --- 2013-05-24 03:55:25 - __MAKE_CONF=/dev/null TB --- 2013-05-24 03:55:25 - cd /src TB --- 2013-05-24 03:55:25 - /usr/bin/make -B buildworld >>> World build started on Fri May 24 03:55:26 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri May 24 06:50:23 UTC 2013 TB --- 2013-05-24 06:50:23 - generating LINT kernel config TB --- 2013-05-24 06:50:23 - cd /src/sys/pc98/conf TB --- 2013-05-24 06:50:23 - /usr/bin/make -B LINT TB --- 2013-05-24 06:50:23 - cd /src/sys/pc98/conf TB --- 2013-05-24 06:50:23 - /usr/sbin/config -m LINT TB --- 2013-05-24 06:50:23 - building LINT kernel TB --- 2013-05-24 06:50:23 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 06:50:23 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 06:50:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 06:50:23 - SRCCONF=/dev/null TB --- 2013-05-24 06:50:23 - TARGET=pc98 TB --- 2013-05-24 06:50:23 - TARGET_ARCH=i386 TB --- 2013-05-24 06:50:23 - TZ=UTC TB --- 2013-05-24 06:50:23 - __MAKE_CONF=/dev/null TB --- 2013-05-24 06:50:23 - cd /src TB --- 2013-05-24 06:50:23 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri May 24 06:50:23 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue aic7xxx_reg_print.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/cam/cam.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/cam/cam_periph.c /src/sys/cam/cam_periph.c: In function 'cam_periph_mapmem': /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_MASK' undeclared (first use in this function) /src/sys/cam/cam_periph.c:736: error: (Each undeclared identifier is reported only once /src/sys/cam/cam_periph.c:736: error: for each function it appears in.) /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_VADDR' undeclared (first use in this function) *** Error code 1 Stop in /obj/pc98.i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-05-24 06:55:45 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-24 06:55:45 - ERROR: failed to build LINT kernel TB --- 2013-05-24 06:55:45 - 8200.66 user 914.80 system 10825.99 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-i386-pc98.full From owner-freebsd-stable@FreeBSD.ORG Fri May 24 06:55:55 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 35D00F25; Fri, 24 May 2013 06:55:55 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id F34F0A6; Fri, 24 May 2013 06:55:54 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r4O6tsar061123; Fri, 24 May 2013 06:55:54 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r4O6tsNu061114; Fri, 24 May 2013 06:55:54 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 24 May 2013 06:55:54 GMT Message-Id: <201305240655.r4O6tsNu061114@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on i386/i386 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 06:55:55 -0000 TB --- 2013-05-24 03:55:19 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-05-24 03:55:19 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-05-24 03:55:19 - starting RELENG_9 tinderbox run for i386/i386 TB --- 2013-05-24 03:55:19 - cleaning the object tree TB --- 2013-05-24 03:55:19 - /usr/local/bin/svn stat /src TB --- 2013-05-24 03:55:24 - At svn revision 250954 TB --- 2013-05-24 03:55:25 - building world TB --- 2013-05-24 03:55:25 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 03:55:25 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 03:55:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 03:55:25 - SRCCONF=/dev/null TB --- 2013-05-24 03:55:25 - TARGET=i386 TB --- 2013-05-24 03:55:25 - TARGET_ARCH=i386 TB --- 2013-05-24 03:55:25 - TZ=UTC TB --- 2013-05-24 03:55:25 - __MAKE_CONF=/dev/null TB --- 2013-05-24 03:55:25 - cd /src TB --- 2013-05-24 03:55:25 - /usr/bin/make -B buildworld >>> World build started on Fri May 24 03:55:26 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri May 24 06:50:30 UTC 2013 TB --- 2013-05-24 06:50:30 - generating LINT kernel config TB --- 2013-05-24 06:50:30 - cd /src/sys/i386/conf TB --- 2013-05-24 06:50:30 - /usr/bin/make -B LINT TB --- 2013-05-24 06:50:30 - cd /src/sys/i386/conf TB --- 2013-05-24 06:50:30 - /usr/sbin/config -m LINT TB --- 2013-05-24 06:50:30 - building LINT kernel TB --- 2013-05-24 06:50:30 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 06:50:30 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 06:50:30 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 06:50:30 - SRCCONF=/dev/null TB --- 2013-05-24 06:50:30 - TARGET=i386 TB --- 2013-05-24 06:50:30 - TARGET_ARCH=i386 TB --- 2013-05-24 06:50:30 - TZ=UTC TB --- 2013-05-24 06:50:30 - __MAKE_CONF=/dev/null TB --- 2013-05-24 06:50:30 - cd /src TB --- 2013-05-24 06:50:30 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri May 24 06:50:30 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue aic79xx_reg_print.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/cam/cam.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/cam/cam_periph.c /src/sys/cam/cam_periph.c: In function 'cam_periph_mapmem': /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_MASK' undeclared (first use in this function) /src/sys/cam/cam_periph.c:736: error: (Each undeclared identifier is reported only once /src/sys/cam/cam_periph.c:736: error: for each function it appears in.) /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_VADDR' undeclared (first use in this function) *** Error code 1 Stop in /obj/i386.i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-05-24 06:55:54 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-24 06:55:54 - ERROR: failed to build LINT kernel TB --- 2013-05-24 06:55:54 - 8258.61 user 912.08 system 10834.66 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-i386-i386.full From owner-freebsd-stable@FreeBSD.ORG Fri May 24 07:16:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3D9AD62C; Fri, 24 May 2013 07:16:41 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-lb0-f171.google.com (mail-lb0-f171.google.com [209.85.217.171]) by mx1.freebsd.org (Postfix) with ESMTP id 57CC41A4; Fri, 24 May 2013 07:16:39 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id v20so4326859lbc.30 for ; Fri, 24 May 2013 00:16:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=XlB7j2HbGLLO8mt9pno8AUTjvwGgj8lzAMoBQ+DTp+0=; b=qVvSMJLoL4oNvXTW407gIVO2bGi+h96f07y1Ou7sCCK/EUFt3gzPdsLsc2jvDxLD1K 6wpX69BlUehiBOltULIA9f+v0PBBTNOSmV9fx0ZFKvmMFrm3CUO76sjsCYY4QYNhdf+L DhMfaU9NowbheOs1z35xQFMvfRLBpRVOyplVykfBC5S5tVYYqO3shIlJJlioRhq/0yAg QqRGqSJZT90PhzLc/BqguDJZ0iqPy5oTztmrSOvuni10VVlgYuwBGfCpY0FCljRvTT7U CaKfB1HvHX2CH6E/F9qVaYa1tFC+UmsM49GKTYnVCkOu8n2bwyeNJPEVnaTFPJIWrKrj D3Kg== MIME-Version: 1.0 X-Received: by 10.152.4.7 with SMTP id g7mr8112637lag.44.1369379793294; Fri, 24 May 2013 00:16:33 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.3.102 with HTTP; Fri, 24 May 2013 00:16:33 -0700 (PDT) Received: by 10.112.3.102 with HTTP; Fri, 24 May 2013 00:16:33 -0700 (PDT) In-Reply-To: <20130524055832.GA42673@icarus.home.lan> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com> <20130524055832.GA42673@icarus.home.lan> Date: Fri, 24 May 2013 00:16:33 -0700 X-Google-Sender-Auth: iAkaWNa6E5sWAkwbh6HWkPseIfA Message-ID: Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 From: Craig Rodrigues To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: YongHyeon PYUN , FreeBSD Release Engineering Team , freebsd-stable@freebsd.org, Glen Barber X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 07:16:41 -0000 On May 24, 2013 1:58 AM, "Jeremy Chadwick" wrote: > > I can't test anything without an ISO -- the system in question is truly > "bare-bones" (no hard disk, can't boot USB memsticks, etc.). I'm not a > good test subject for changes on this one, I'm afraid. On another system, if you can set up an NFS root file system of 8.4 and PXE boot it, then you can help test individual changes to binaries such as dhclient. See: http://www.freebsd.org/doc/en/books/handbook/network-pxe-nfs.html PXE booting environment may or may not repro the problem, but it would be very helpful if you could try it since you have the right hardware. As Glen and Josh have mentioned, unfortunately this is probably too late in the 8.4 release cycle to fix and will have to be release noted. -- Craig From owner-freebsd-stable@FreeBSD.ORG Fri May 24 07:18:16 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0714E738; Fri, 24 May 2013 07:18:16 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id C47741BB; Fri, 24 May 2013 07:18:15 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r4O7IFQ1023438; Fri, 24 May 2013 07:18:15 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r4O7IFPV023434; Fri, 24 May 2013 07:18:15 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 24 May 2013 07:18:15 GMT Message-Id: <201305240718.r4O7IFPV023434@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on ia64/ia64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 07:18:16 -0000 TB --- 2013-05-24 05:18:28 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-05-24 05:18:28 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-05-24 05:18:28 - starting RELENG_9 tinderbox run for ia64/ia64 TB --- 2013-05-24 05:18:28 - cleaning the object tree TB --- 2013-05-24 05:18:28 - /usr/local/bin/svn stat /src TB --- 2013-05-24 05:18:55 - At svn revision 250954 TB --- 2013-05-24 05:18:56 - building world TB --- 2013-05-24 05:18:56 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 05:18:56 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 05:18:56 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 05:18:56 - SRCCONF=/dev/null TB --- 2013-05-24 05:18:56 - TARGET=ia64 TB --- 2013-05-24 05:18:56 - TARGET_ARCH=ia64 TB --- 2013-05-24 05:18:56 - TZ=UTC TB --- 2013-05-24 05:18:56 - __MAKE_CONF=/dev/null TB --- 2013-05-24 05:18:56 - cd /src TB --- 2013-05-24 05:18:56 - /usr/bin/make -B buildworld >>> World build started on Fri May 24 05:18:57 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri May 24 07:14:38 UTC 2013 TB --- 2013-05-24 07:14:38 - generating LINT kernel config TB --- 2013-05-24 07:14:38 - cd /src/sys/ia64/conf TB --- 2013-05-24 07:14:38 - /usr/bin/make -B LINT TB --- 2013-05-24 07:14:38 - cd /src/sys/ia64/conf TB --- 2013-05-24 07:14:38 - /usr/sbin/config -m LINT TB --- 2013-05-24 07:14:38 - building LINT kernel TB --- 2013-05-24 07:14:38 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 07:14:38 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 07:14:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 07:14:38 - SRCCONF=/dev/null TB --- 2013-05-24 07:14:38 - TARGET=ia64 TB --- 2013-05-24 07:14:38 - TARGET_ARCH=ia64 TB --- 2013-05-24 07:14:38 - TZ=UTC TB --- 2013-05-24 07:14:38 - __MAKE_CONF=/dev/null TB --- 2013-05-24 07:14:38 - cd /src TB --- 2013-05-24 07:14:38 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri May 24 07:14:38 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror aic79xx_reg_print.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/cam/cam.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/cam/cam_periph.c /src/sys/cam/cam_periph.c: In function 'cam_periph_mapmem': /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_MASK' undeclared (first use in this function) /src/sys/cam/cam_periph.c:736: error: (Each undeclared identifier is reported only once /src/sys/cam/cam_periph.c:736: error: for each function it appears in.) /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_VADDR' undeclared (first use in this function) *** Error code 1 Stop in /obj/ia64.ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-05-24 07:18:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-24 07:18:15 - ERROR: failed to build LINT kernel TB --- 2013-05-24 07:18:15 - 4979.01 user 669.09 system 7186.53 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-ia64-ia64.full From owner-freebsd-stable@FreeBSD.ORG Fri May 24 07:30:58 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 52053C21; Fri, 24 May 2013 07:30:58 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 39B2024E; Fri, 24 May 2013 07:30:57 +0000 (UTC) Received: from alph.d.allbsd.org (p2175-ipbf701funabasi.chiba.ocn.ne.jp [122.25.209.175]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r4O7UeTZ052993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 May 2013 16:30:50 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.5/8.14.5) with ESMTP id r4O7UclS092450; Fri, 24 May 2013 16:30:39 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Fri, 24 May 2013 16:29:26 +0900 (JST) Message-Id: <20130524.162926.395058052118975996.hrs@allbsd.org> To: pyunyh@gmail.com Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 From: Hiroki Sato In-Reply-To: <20130524054720.GA1496@michelle.cdnetworks.com> References: <20130524044035.GA40957@icarus.home.lan> <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Fri_May_24_16_29_26_2013_592)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Fri, 24 May 2013 16:30:50 +0900 (JST) X-Spam-Status: No, score=-94.5 required=13.0 tests=CONTENT_TYPE_PRESENT, ONLY1HOPDIRECT,RCVD_IN_PBL,SAMEHELOBY2HOP,TO_NO_BRKTS_PCNT,USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: jdc@koitsu.org, gjb@FreeBSD.org, freebsd-stable@FreeBSD.org, re@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 07:30:58 -0000 ----Security_Multipart(Fri_May_24_16_29_26_2013_592)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit YongHyeon PYUN wrote in <20130524054720.GA1496@michelle.cdnetworks.com>: py> On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote: py> > On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: py> > > On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote: py> > > > On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: py> > > > > If someone wants me to test DHCP via fxp(4) on the above system (I can py> > > > > do so with both NICs), just let me know; it should only take me half an py> > > > > hour or so. py> > > > > py> > > > > I'll politely wait for someone to say "please do so" else won't bother. py> > > > > py> > > > py> > > > For the sake of completeness... py> > > > py> > > > "Please do so." :) py> > > py> > > Issue reproduced 100% reliably, even within sysinstall. py> > > py> > > {snip} py> > py> > Forgot to add: py> > py> > This issue ONLY happens when using DHCP. py> > py> > Statically assigning the IP address works fine; fxp0 goes down once, py> > up once, then stays up indefinitely. py> py> I asked Mike to try backing out dhclient(8) change(r247336) but it py> seems he missed that. Jeremy, could you try that? py> py> I guess dhclient(8) does not like flow-control negotiation of py> fxp(4) after link establishment. Okay, I could reproduce this issue on my box. After invocation of dhclient(8), a link is up and then state_reboot() drops the link establishment. Removing the changes around RTM_IFINFO in r247336 makes it work with no problem. A workaround is specifying the following line in rc.conf: ifconfig_fxp0="DHCP media 100baseTX mediaopt full-duplex" -- Hiroki ----Security_Multipart(Fri_May_24_16_29_26_2013_592)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlGfFtYACgkQTyzT2CeTzy2L9ACfaXPluTP5rFEX9DHxU2N29fa6 PYoAn1jFexNVUJ4xrHtgL8KylJZ2Bn2Q =POsy -----END PGP SIGNATURE----- ----Security_Multipart(Fri_May_24_16_29_26_2013_592)---- From owner-freebsd-stable@FreeBSD.ORG Fri May 24 07:32:32 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 22BA4D4E; Fri, 24 May 2013 07:32:32 +0000 (UTC) (envelope-from spork@bway.net) Received: from smtp1.bway.net (smtp1.bway.net [216.220.96.27]) by mx1.freebsd.org (Postfix) with ESMTP id F0766271; Fri, 24 May 2013 07:32:31 +0000 (UTC) Received: from frankentosh.sporklab.com (foon.sporktines.com [96.57.144.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: spork@bway.net) by smtp1.bway.net (Postfix) with ESMTPSA id B80B495854; Fri, 24 May 2013 03:32:29 -0400 (EDT) Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Charles Sprickman In-Reply-To: <20130524054720.GA1496@michelle.cdnetworks.com> Date: Fri, 24 May 2013 03:32:29 -0400 Content-Transfer-Encoding: 7bit Message-Id: <91E1EEEC-CD78-4E9B-B71A-A8B4F5417D81@bway.net> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com> To: pyunyh@gmail.com X-Mailer: Apple Mail (2.1085) Cc: Jeremy Chadwick , Glen Barber , freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 07:32:32 -0000 On May 24, 2013, at 1:47 AM, YongHyeon PYUN wrote: > On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote: >> On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: >>> On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote: >>>> On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: >>>>> If someone wants me to test DHCP via fxp(4) on the above system (I can >>>>> do so with both NICs), just let me know; it should only take me half an >>>>> hour or so. >>>>> >>>>> I'll politely wait for someone to say "please do so" else won't bother. >>>>> >>>> >>>> For the sake of completeness... >>>> >>>> "Please do so." :) >>> >>> Issue reproduced 100% reliably, even within sysinstall. >>> >>> {snip} >> >> Forgot to add: >> >> This issue ONLY happens when using DHCP. >> >> Statically assigning the IP address works fine; fxp0 goes down once, >> up once, then stays up indefinitely. > > I asked Mike to try backing out dhclient(8) change(r247336) but it > seems he missed that. Jeremy, could you try that? I have a system up and running and showing the problem (that was non-trival, just for the record - one machine blew the PSU after POST, the other refused to boot off an IDE drive, and then required two CD-ROM drives before I found a functional one, and it took a good half-hour to find what's apparently the last piece of writable CD-R media I own). I am not awesome with svn, but I'll see if I can manually undo r247336 and give it a spin. Charles > > I guess dhclient(8) does not like flow-control negotiation of > fxp(4) after link establishment. > >> >> I also tested network I/O in the statically-assigned scenario. Pinging >> the box from another machine on the LAN: >> >> $ ping 192.168.1.192 >> PING 192.168.1.192 (192.168.1.192): 56 data bytes >> 64 bytes from 192.168.1.192: icmp_seq=0 ttl=64 time=0.180 ms >> 64 bytes from 192.168.1.192: icmp_seq=1 ttl=64 time=0.138 ms >> 64 bytes from 192.168.1.192: icmp_seq=2 ttl=64 time=0.214 ms >> 64 bytes from 192.168.1.192: icmp_seq=3 ttl=64 time=0.165 ms >> 64 bytes from 192.168.1.192: icmp_seq=4 ttl=64 time=0.114 ms >> ^C >> --- 192.168.1.192 ping statistics --- >> 5 packets transmitted, 5 packets received, 0.0% packet loss >> round-trip min/avg/max/stddev = 0.114/0.162/0.214/0.034 ms > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Fri May 24 07:33:30 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6B5ADE6B; Fri, 24 May 2013 07:33:30 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 3071928E; Fri, 24 May 2013 07:33:30 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r4O7XTNk047959; Fri, 24 May 2013 07:33:29 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r4O7XTQa047954; Fri, 24 May 2013 07:33:29 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 24 May 2013 07:33:29 GMT Message-Id: <201305240733.r4O7XTQa047954@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on amd64/amd64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 07:33:30 -0000 TB --- 2013-05-24 03:55:19 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-05-24 03:55:19 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-05-24 03:55:19 - starting RELENG_9 tinderbox run for amd64/amd64 TB --- 2013-05-24 03:55:19 - cleaning the object tree TB --- 2013-05-24 03:55:19 - /usr/local/bin/svn stat /src TB --- 2013-05-24 03:55:24 - At svn revision 250954 TB --- 2013-05-24 03:55:25 - building world TB --- 2013-05-24 03:55:25 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 03:55:25 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 03:55:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 03:55:25 - SRCCONF=/dev/null TB --- 2013-05-24 03:55:25 - TARGET=amd64 TB --- 2013-05-24 03:55:25 - TARGET_ARCH=amd64 TB --- 2013-05-24 03:55:25 - TZ=UTC TB --- 2013-05-24 03:55:25 - __MAKE_CONF=/dev/null TB --- 2013-05-24 03:55:25 - cd /src TB --- 2013-05-24 03:55:25 - /usr/bin/make -B buildworld >>> World build started on Fri May 24 03:55:26 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Fri May 24 07:27:48 UTC 2013 TB --- 2013-05-24 07:27:48 - generating LINT kernel config TB --- 2013-05-24 07:27:48 - cd /src/sys/amd64/conf TB --- 2013-05-24 07:27:48 - /usr/bin/make -B LINT TB --- 2013-05-24 07:27:48 - cd /src/sys/amd64/conf TB --- 2013-05-24 07:27:48 - /usr/sbin/config -m LINT TB --- 2013-05-24 07:27:48 - building LINT kernel TB --- 2013-05-24 07:27:48 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 07:27:48 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 07:27:48 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 07:27:48 - SRCCONF=/dev/null TB --- 2013-05-24 07:27:48 - TARGET=amd64 TB --- 2013-05-24 07:27:48 - TARGET_ARCH=amd64 TB --- 2013-05-24 07:27:48 - TZ=UTC TB --- 2013-05-24 07:27:48 - __MAKE_CONF=/dev/null TB --- 2013-05-24 07:27:48 - cd /src TB --- 2013-05-24 07:27:48 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri May 24 07:27:48 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue aic79xx_reg_print.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/cam/cam.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/cam/cam_periph.c /src/sys/cam/cam_periph.c: In function 'cam_periph_mapmem': /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_MASK' undeclared (first use in this function) /src/sys/cam/cam_periph.c:736: error: (Each undeclared identifier is reported only once /src/sys/cam/cam_periph.c:736: error: for each function it appears in.) /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_VADDR' undeclared (first use in this function) *** Error code 1 Stop in /obj/amd64.amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-05-24 07:33:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-24 07:33:29 - ERROR: failed to build LINT kernel TB --- 2013-05-24 07:33:29 - 9782.77 user 1201.08 system 13089.84 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-amd64-amd64.full From owner-freebsd-stable@FreeBSD.ORG Fri May 24 07:37:17 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E9DCE178; Fri, 24 May 2013 07:37:17 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 158FF2CF; Fri, 24 May 2013 07:37:16 +0000 (UTC) Received: from alph.d.allbsd.org (p2175-ipbf701funabasi.chiba.ocn.ne.jp [122.25.209.175]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r4O7b1CA053638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 May 2013 16:37:11 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.5/8.14.5) with ESMTP id r4O7b1En092540; Fri, 24 May 2013 16:37:01 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Fri, 24 May 2013 16:36:46 +0900 (JST) Message-Id: <20130524.163646.628115045676432731.hrs@allbsd.org> To: pyunyh@gmail.com Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 From: Hiroki Sato In-Reply-To: <20130524.162926.395058052118975996.hrs@allbsd.org> References: <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com> <20130524.162926.395058052118975996.hrs@allbsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Fri_May_24_16_36_46_2013_210)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Fri, 24 May 2013 16:37:11 +0900 (JST) X-Spam-Status: No, score=-94.5 required=13.0 tests=CONTENT_TYPE_PRESENT, ONLY1HOPDIRECT,RCVD_IN_PBL,SAMEHELOBY2HOP,USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: jdc@koitsu.org, gjb@FreeBSD.org, freebsd-stable@FreeBSD.org, re@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 07:37:18 -0000 ----Security_Multipart(Fri_May_24_16_36_46_2013_210)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hiroki Sato wrote in <20130524.162926.395058052118975996.hrs@allbsd.org>: hr> YongHyeon PYUN wrote hr> in <20130524054720.GA1496@michelle.cdnetworks.com>: hr> hr> A workaround is specifying the following line in rc.conf: hr> hr> ifconfig_fxp0="DHCP media 100baseTX mediaopt full-duplex" Hmm, I guess this can happen on other NICs when the link negotiation causes a link-state flap. Is it true? -- Hiroki ----Security_Multipart(Fri_May_24_16_36_46_2013_210)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlGfGI4ACgkQTyzT2CeTzy2XTgCdFWHi5xwbeoiytgb6LIhDhJIq 8RYAoJdz4reCIKhjHN5yFP+lbRV5ZPTz =tOPc -----END PGP SIGNATURE----- ----Security_Multipart(Fri_May_24_16_36_46_2013_210)---- From owner-freebsd-stable@FreeBSD.ORG Fri May 24 07:52:39 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 865CD975; Fri, 24 May 2013 07:52:39 +0000 (UTC) (envelope-from john@theusgroup.com) Received: from theusgroup.com (theusgroup.com [64.122.243.222]) by mx1.freebsd.org (Postfix) with ESMTP id 68EC3405; Fri, 24 May 2013 07:52:39 +0000 (UTC) From: John To: Hiroki Sato Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 In-reply-to: <20130524.162926.395058052118975996.hrs@allbsd.org> References: <20130524044035.GA40957@icarus.home.lan> <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com> <20130524.162926.395058052118975996.hrs@allbsd.org> Comments: In-reply-to Hiroki Sato message dated "Fri, 24 May 2013 16:29:26 +0900." Date: Fri, 24 May 2013 00:46:45 -0700 Message-Id: <20130524074645.22C52A30@server.theusgroup.com> Cc: pyunyh@gmail.com, jdc@koitsu.org, freebsd-stable@FreeBSD.org, re@FreeBSD.org, gjb@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 07:52:39 -0000 >YongHyeon PYUN wrote > in <20130524054720.GA1496@michelle.cdnetworks.com>: > >py> On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote: >py> > On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: >py> > > On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote: >py> > > > On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: >py> > > > > If someone wants me to test DHCP via fxp(4) on the above system (I can >py> > > > > do so with both NICs), just let me know; it should only take me half an >py> > > > > hour or so. >py> > > > > >py> > > > > I'll politely wait for someone to say "please do so" else won't bother. >py> > > > > >py> > > > >py> > > > For the sake of completeness... >py> > > > >py> > > > "Please do so." :) >py> > > >py> > > Issue reproduced 100% reliably, even within sysinstall. >py> > > >py> > > {snip} >py> > >py> > Forgot to add: >py> > >py> > This issue ONLY happens when using DHCP. >py> > >py> > Statically assigning the IP address works fine; fxp0 goes down once, >py> > up once, then stays up indefinitely. >py> >py> I asked Mike to try backing out dhclient(8) change(r247336) but it >py> seems he missed that. Jeremy, could you try that? >py> >py> I guess dhclient(8) does not like flow-control negotiation of >py> fxp(4) after link establishment. > > Okay, I could reproduce this issue on my box. After invocation of > dhclient(8), a link is up and then state_reboot() drops the link > establishment. Removing the changes around RTM_IFINFO in r247336 > makes it work with no problem. > > A workaround is specifying the following line in rc.conf: > > ifconfig_fxp0="DHCP media 100baseTX mediaopt full-duplex" > >-- Hiroki I can confirm that backing out r247336 on a box running 9.1-stable.r250229 fixes the problem. I hadn't seen the problem before because the box normally has a static ip address. John Theus TheUsGroup.com From owner-freebsd-stable@FreeBSD.ORG Fri May 24 08:21:34 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C1FC1A8F; Fri, 24 May 2013 08:21:34 +0000 (UTC) (envelope-from spork@bway.net) Received: from smtp1.bway.net (smtp1.bway.net [216.220.96.27]) by mx1.freebsd.org (Postfix) with ESMTP id 8076E83D; Fri, 24 May 2013 08:21:34 +0000 (UTC) Received: from frankentosh.sporklab.com (foon.sporktines.com [96.57.144.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: spork@bway.net) by smtp1.bway.net (Postfix) with ESMTPSA id 62D0395854; Fri, 24 May 2013 04:21:33 -0400 (EDT) Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=windows-1252 From: Charles Sprickman In-Reply-To: <20130524054720.GA1496@michelle.cdnetworks.com> Date: Fri, 24 May 2013 04:21:32 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <1C316A6C-7285-4178-B325-8A905E277342@bway.net> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com> To: pyunyh@gmail.com X-Mailer: Apple Mail (2.1085) Cc: Jeremy Chadwick , Glen Barber , freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 08:21:34 -0000 On May 24, 2013, at 1:47 AM, YongHyeon PYUN wrote: > On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote: >> On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: >>> On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote: >>>> On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: >>>>> If someone wants me to test DHCP via fxp(4) on the above system (I = can >>>>> do so with both NICs), just let me know; it should only take me = half an >>>>> hour or so. >>>>>=20 >>>>> I'll politely wait for someone to say "please do so" else won't = bother. >>>>>=20 >>>>=20 >>>> For the sake of completeness... >>>>=20 >>>> "Please do so." :) >>>=20 >>> Issue reproduced 100% reliably, even within sysinstall. >>>=20 >>> {snip}=20 >>=20 >> Forgot to add: >>=20 >> This issue ONLY happens when using DHCP. >>=20 >> Statically assigning the IP address works fine; fxp0 goes down once, >> up once, then stays up indefinitely. >=20 > I asked Mike to try backing out dhclient(8) change(r247336) but it > seems he missed that. Jeremy, could you try that? >=20 > I guess dhclient(8) does not like flow-control negotiation of > fxp(4) after link establishment. Confirmed here that removing the linkstate stuff from r247336 fixes it. Before: May 24 08:00:17 fxptest dhclient: New Subnet Mask (fxp0): 255.255.255.0 May 24 08:00:17 fxptest dhclient: New Broadcast Address (fxp0): = 10.3.2.255 May 24 08:00:17 fxptest dhclient: New Routers (fxp0): 10.3.2.1 May 24 08:00:19 fxptest kernel: fxp0: link state changed to UP May 24 08:00:19 fxptest kernel: fxp0: link state changed to DOWN May 24 08:00:19 fxptest dhclient: New IP Address (fxp0): 10.3.2.109 May 24 08:00:19 fxptest dhclient: New Subnet Mask (fxp0): 255.255.255.0 May 24 08:00:19 fxptest dhclient: New Broadcast Address (fxp0): = 10.3.2.255 May 24 08:00:19 fxptest dhclient: New Routers (fxp0): 10.3.2.1 May 24 08:00:21 fxptest kernel: fxp0: link state changed to UP May 24 08:00:21 fxptest dhclient: New IP Address (fxp0): 10.3.2.109 May 24 08:00:21 fxptest kernel: fxp0: link state changed to DOWN May 24 08:00:21 fxptest dhclient: New Subnet Mask (fxp0): 255.255.255.0 May 24 08:00:21 fxptest dhclient: New Broadcast Address (fxp0): = 10.3.2.255 May 24 08:00:21 fxptest dhclient: New Routers (fxp0): 10.3.2.1 May 24 08:00:23 fxptest kernel: fxp0: link state changed to UP May 24 08:00:23 fxptest dhclient: New IP Address (fxp0): 10.3.2.109 May 24 08:00:23 fxptest kernel: fxp0: link state changed to DOWN After: May 24 08:07:05 fxptest kernel: fxp0: link state changed to DOWN May 24 08:07:07 fxptest kernel: fxp0: link state changed to UP May 24 08:07:12 fxptest dhclient: New IP Address (fxp0): 10.3.2.109 May 24 08:07:12 fxptest kernel: fxp0: link state changed to DOWN May 24 08:07:12 fxptest dhclient: New Subnet Mask (fxp0): 255.255.255.0 May 24 08:07:12 fxptest dhclient: New Broadcast Address (fxp0): = 10.3.2.255 May 24 08:07:12 fxptest dhclient: New Routers (fxp0): 10.3.2.1 May 24 08:07:14 fxptest kernel: fxp0: link state changed to UP root@fxptest:/usr/home/spork # date Fri May 24 08:10:32 UTC 2013 Note there is still a down/up/down/up transition on starting dhclient=85 Am I correct that the linkstate changes are meant to allow for an = automatic retry for a lease when the ethernet connection is dropped? = That doesn't seem wrong, it just seems like somewhere we should be = waiting a few seconds. It appears that each time dhclient gets a lease, = even without the linkstate code, the connection briefly drops=85' Charles= From owner-freebsd-stable@FreeBSD.ORG Fri May 24 08:48:38 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DFEBED64; Fri, 24 May 2013 08:48:38 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id A8C499F1; Fri, 24 May 2013 08:48:38 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r4O8mcMR045293; Fri, 24 May 2013 08:48:38 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r4O8mc13045292; Fri, 24 May 2013 08:48:38 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 24 May 2013 08:48:38 GMT Message-Id: <201305240848.r4O8mc13045292@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on sparc64/sparc64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 08:48:39 -0000 TB --- 2013-05-24 07:33:29 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-05-24 07:33:29 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-05-24 07:33:29 - starting RELENG_9 tinderbox run for sparc64/sparc64 TB --- 2013-05-24 07:33:30 - cleaning the object tree TB --- 2013-05-24 07:33:30 - /usr/local/bin/svn stat /src TB --- 2013-05-24 07:33:37 - At svn revision 250954 TB --- 2013-05-24 07:33:38 - building world TB --- 2013-05-24 07:33:38 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 07:33:38 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 07:33:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 07:33:38 - SRCCONF=/dev/null TB --- 2013-05-24 07:33:38 - TARGET=sparc64 TB --- 2013-05-24 07:33:38 - TARGET_ARCH=sparc64 TB --- 2013-05-24 07:33:38 - TZ=UTC TB --- 2013-05-24 07:33:38 - __MAKE_CONF=/dev/null TB --- 2013-05-24 07:33:38 - cd /src TB --- 2013-05-24 07:33:38 - /usr/bin/make -B buildworld >>> World build started on Fri May 24 07:33:38 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri May 24 08:45:28 UTC 2013 TB --- 2013-05-24 08:45:28 - generating LINT kernel config TB --- 2013-05-24 08:45:28 - cd /src/sys/sparc64/conf TB --- 2013-05-24 08:45:28 - /usr/bin/make -B LINT TB --- 2013-05-24 08:45:28 - cd /src/sys/sparc64/conf TB --- 2013-05-24 08:45:28 - /usr/sbin/config -m LINT TB --- 2013-05-24 08:45:28 - building LINT kernel TB --- 2013-05-24 08:45:28 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 08:45:28 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 08:45:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 08:45:28 - SRCCONF=/dev/null TB --- 2013-05-24 08:45:28 - TARGET=sparc64 TB --- 2013-05-24 08:45:28 - TARGET_ARCH=sparc64 TB --- 2013-05-24 08:45:28 - TZ=UTC TB --- 2013-05-24 08:45:28 - __MAKE_CONF=/dev/null TB --- 2013-05-24 08:45:28 - cd /src TB --- 2013-05-24 08:45:28 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri May 24 08:45:28 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror aic79xx_reg_print.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/cam/cam.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/cam/cam_periph.c /src/sys/cam/cam_periph.c: In function 'cam_periph_mapmem': /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_MASK' undeclared (first use in this function) /src/sys/cam/cam_periph.c:736: error: (Each undeclared identifier is reported only once /src/sys/cam/cam_periph.c:736: error: for each function it appears in.) /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_VADDR' undeclared (first use in this function) *** Error code 1 Stop in /obj/sparc64.sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-05-24 08:48:38 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-24 08:48:38 - ERROR: failed to build LINT kernel TB --- 2013-05-24 08:48:38 - 3430.39 user 540.41 system 4508.14 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-sparc64-sparc64.full From owner-freebsd-stable@FreeBSD.ORG Fri May 24 09:28:05 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 86FAB3DB; Fri, 24 May 2013 09:28:05 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 44DB8DA7; Fri, 24 May 2013 09:28:05 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id r4O9S49I074756; Fri, 24 May 2013 09:28:04 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id r4O9S4aV074742; Fri, 24 May 2013 09:28:04 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 24 May 2013 09:28:04 GMT Message-Id: <201305240928.r4O9S4aV074742@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on powerpc/powerpc Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 09:28:05 -0000 TB --- 2013-05-24 06:55:54 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-05-24 06:55:54 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-05-24 06:55:54 - starting RELENG_9 tinderbox run for powerpc/powerpc TB --- 2013-05-24 06:55:54 - cleaning the object tree TB --- 2013-05-24 06:55:54 - /usr/local/bin/svn stat /src TB --- 2013-05-24 06:56:07 - At svn revision 250954 TB --- 2013-05-24 06:56:08 - building world TB --- 2013-05-24 06:56:08 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 06:56:08 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 06:56:08 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 06:56:08 - SRCCONF=/dev/null TB --- 2013-05-24 06:56:08 - TARGET=powerpc TB --- 2013-05-24 06:56:08 - TARGET_ARCH=powerpc TB --- 2013-05-24 06:56:08 - TZ=UTC TB --- 2013-05-24 06:56:08 - __MAKE_CONF=/dev/null TB --- 2013-05-24 06:56:08 - cd /src TB --- 2013-05-24 06:56:08 - /usr/bin/make -B buildworld >>> World build started on Fri May 24 06:56:08 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri May 24 09:26:03 UTC 2013 TB --- 2013-05-24 09:26:03 - generating LINT kernel config TB --- 2013-05-24 09:26:03 - cd /src/sys/powerpc/conf TB --- 2013-05-24 09:26:03 - /usr/bin/make -B LINT TB --- 2013-05-24 09:26:03 - cd /src/sys/powerpc/conf TB --- 2013-05-24 09:26:03 - /usr/sbin/config -m LINT TB --- 2013-05-24 09:26:03 - building LINT kernel TB --- 2013-05-24 09:26:03 - CROSS_BUILD_TESTING=YES TB --- 2013-05-24 09:26:03 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-24 09:26:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-24 09:26:03 - SRCCONF=/dev/null TB --- 2013-05-24 09:26:03 - TARGET=powerpc TB --- 2013-05-24 09:26:03 - TARGET_ARCH=powerpc TB --- 2013-05-24 09:26:03 - TZ=UTC TB --- 2013-05-24 09:26:03 - __MAKE_CONF=/dev/null TB --- 2013-05-24 09:26:03 - cd /src TB --- 2013-05-24 09:26:03 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri May 24 09:26:03 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror aic79xx_reg_print.c cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/cam/cam.c cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/cam/cam_periph.c /src/sys/cam/cam_periph.c: In function 'cam_periph_mapmem': /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_MASK' undeclared (first use in this function) /src/sys/cam/cam_periph.c:736: error: (Each undeclared identifier is reported only once /src/sys/cam/cam_periph.c:736: error: for each function it appears in.) /src/sys/cam/cam_periph.c:736: error: 'CAM_DATA_VADDR' undeclared (first use in this function) *** Error code 1 Stop in /obj/powerpc.powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-05-24 09:28:04 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-24 09:28:04 - ERROR: failed to build LINT kernel TB --- 2013-05-24 09:28:04 - 7580.59 user 805.73 system 9129.79 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-powerpc-powerpc.full From owner-freebsd-stable@FreeBSD.ORG Fri May 24 10:02:27 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1FA7DD8D for ; Fri, 24 May 2013 10:02:27 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [IPv6:2a02:b90:3002:e550::3]) by mx1.freebsd.org (Postfix) with ESMTP id DBC461000 for ; Fri, 24 May 2013 10:02:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ingresso.co.uk; s=x; h=Date:From:Message-Id:In-Reply-To:Subject:To; bh=TF2Mylcbpu+wgA/npobGZ2Qea5GhTnG+YAhv4Oxb1fA=; b=3bVuE10asA9DTd+AND1wVPtuhPBmzqgpbgv5iDP7E4ZyQetZlhLY9RI4wEmIta5y7KU8fI/iSWJIliDULB+Kgx7xyQVCexdIyOmjqpr1I5cr4z57MT/kn3DHILKcs+T0QEvT7HTGPxdFufLO8snK3KHGnj6erXXBGNdEKlPeZ1U=; Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UfopN-000DUq-2c; Fri, 24 May 2013 11:02:25 +0100 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UfopM-0002S8-V2; Fri, 24 May 2013 11:02:24 +0100 To: freebsd-stable@FreeBSD.org, marck@rinet.ru Subject: Re: Proposed MFC to hastctl: compact 'status' and introduce 'list' command In-Reply-To: Message-Id: From: Pete French Date: Fri, 24 May 2013 11:02:24 +0100 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 10:02:27 -0000 > http://svnweb.freebsd.org/changeset/base/248291 ... > The reason I'm asking is that it could lead to changes in hast-related scripts > which one use in production. Any chance we could do this is 2 stages - first being to add 'list' to give us a chnace ti change scripts over, then make the chnages to 'status'. I have scripts which try and parse the outut from 'status' which will need changing, and I sspect I am not the only one... cheers, -pete. From owner-freebsd-stable@FreeBSD.ORG Fri May 24 10:08:30 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 402E531D; Fri, 24 May 2013 10:08:30 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 990B7D4; Fri, 24 May 2013 10:08:29 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id r4OA8SYh086391; Fri, 24 May 2013 14:08:28 +0400 (MSK) (envelope-from marck@rinet.ru) Date: Fri, 24 May 2013 14:08:28 +0400 (MSK) From: Dmitry Morozovsky To: Pete French Subject: Re: Proposed MFC to hastctl: compact 'status' and introduce 'list' command In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Fri, 24 May 2013 14:08:28 +0400 (MSK) Cc: trociny@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 10:08:30 -0000 Pete, On Fri, 24 May 2013, Pete French wrote: > > http://svnweb.freebsd.org/changeset/base/248291 > ... > > The reason I'm asking is that it could lead to changes in hast-related scripts > > which one use in production. > > > Any chance we could do this is 2 stages - first being to add 'list' to give us a chnace > ti change scripts over, then make the chnages to 'status'. I have scripts > which try and parse the outut from 'status' which will need changing, > and I sspect I am not the only one... I see no problem with this, as it is one-lite patch (modulo usage/manual page changes); it would be direct commit to -stable, but as it is temporary, I see no problem there too. Mikolaj, your opinion? -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Fri May 24 11:19:52 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D338D22F; Fri, 24 May 2013 11:19:52 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 2D9E5759; Fri, 24 May 2013 11:19:51 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id fg20so4341483lab.29 for ; Fri, 24 May 2013 04:19:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=/zk5CS9bk9UqWgaj5bvW3TT+JyB308WD8hwzSfVhdqU=; b=1CS+agEZaPTOxhErdqhHphl0o973iWShYZjMrmDzv4DqMOJ+4tXLgU0i3kvgwkN4w5 THheBgI+s13L8mlbA3lN0mnN7TBrfCB26+LmZ4c5H5jHgkW1yfTixcSdGJAdgxc4m2ux pSR8pARPlbKXSX49uC1cW4yxELZ0pJrFJmZdtgGjElh3P4wvdIOv87YYKqIBbZYAkxbi /gO+zSKp3de2pdnMugi1dLol9jBSNV45eMXMD08SRf/+oDI4orWmKBWg1EOeiIKcQ7gP 9YkAyqpFR1OvKIEdhZtJqdshSmE6oKuVzAZjFw5+kpNZ4nP4xDig5C4seoPSajnpxvOL svIA== X-Received: by 10.152.1.104 with SMTP id 8mr8741232lal.33.1369394390444; Fri, 24 May 2013 04:19:50 -0700 (PDT) Received: from localhost ([188.230.122.226]) by mx.google.com with ESMTPSA id a5sm6554296laa.2.2013.05.24.04.19.48 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 24 May 2013 04:19:49 -0700 (PDT) Date: Fri, 24 May 2013 14:19:46 +0300 From: Mikolaj Golub To: Dmitry Morozovsky Subject: Re: Proposed MFC to hastctl: compact 'status' and introduce 'list' command Message-ID: <20130524111945.GB12310@gmail.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: trociny@freebsd.org, freebsd-stable@freebsd.org, Pete French X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 11:19:52 -0000 On Fri, May 24, 2013 at 02:08:28PM +0400, Dmitry Morozovsky wrote: > Pete, > > On Fri, 24 May 2013, Pete French wrote: > > > > http://svnweb.freebsd.org/changeset/base/248291 > > ... > > > The reason I'm asking is that it could lead to changes in hast-related scripts > > > which one use in production. > > > > > > Any chance we could do this is 2 stages - first being to add 'list' to give us a chnace > > ti change scripts over, then make the chnages to 'status'. I have scripts > > which try and parse the outut from 'status' which will need changing, > > and I sspect I am not the only one... > > I see no problem with this, as it is one-lite patch (modulo usage/manual page > changes); it would be direct commit to -stable, but as it is temporary, I see > no problem there too. > > Mikolaj, your opinion? It looks like a very good idea. -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Fri May 24 12:52:26 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7CCFA9AD; Fri, 24 May 2013 12:52:26 +0000 (UTC) (envelope-from mikes@siralan.org) Received: from mail.suso.org (mail.suso.org [66.244.94.5]) by mx1.freebsd.org (Postfix) with ESMTP id 58B78B83; Fri, 24 May 2013 12:52:25 +0000 (UTC) Received: from c-98-223-197-163.hsd1.in.comcast.net (c-98-223-197-163.hsd1.in.comcast.net [98.223.197.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.suso.org (Postfix) with ESMTP id CA41C13814A; Fri, 24 May 2013 12:52:22 +0000 (GMT) Date: Fri, 24 May 2013 08:51:00 -0400 (EDT) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: Glen Barber Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 In-Reply-To: <20130524012117.GE1672@glenbarber.us> Message-ID: References: <20130508174721.GD1651@glenbarber.us> <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Jeremy Chadwick , Craig Rodrigues , YongHyeon PYUN , freebsd-stable@FreeBSD.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 12:52:26 -0000 I'll have access to the test box on Tuesday, will test a fixed IP number then. I'm unable to test that here since reinstalling 8.4 on the NAT box will require eventually reinstalling 8.3-RELEASE and I'm not the only one using the NAT box for Internet access. The test box had 8.3-RC3 installed from a downloaded 8.3-RC3 CD using installation from the CD and with all binaries taken off the CD. No changes were made after installation and reboot. I agree that this seems to be a problem only experienced by those still using the fxp interface and DHCP on a certain subset of Supermicro systems, which has to be a very small group. I did find one other reference to a similar problem at http://forum.pfsense.org/index.php?topic=61102.0) However, one of the posters was using 8.3p7 which predates my 8.3p8. The posters also report that this issue affects only a small subset of similar machines and can be solved by either changing the boot order of the connected systems (not possible for me) or by forcing fxp to 100Mbit full duplex, which I haven't tried. I definitely don't want this issue to hold up 8.4-RELEASE; if it is a problem it can be fixed for those affected with a patch after release. Mike Squires mikes@siralan.org msquires@iga.in.gov (where the test box lives) From owner-freebsd-stable@FreeBSD.ORG Fri May 24 14:40:22 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4B3EB287 for ; Fri, 24 May 2013 14:40:22 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 00ED2662 for ; Fri, 24 May 2013 14:40:21 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1Uft1V-000C0B-An for freebsd-stable@FreeBSD.org; Fri, 24 May 2013 17:31:13 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: freebsd-stable@FreeBSD.org Subject: SunFire X2200 ilo's bge1 DOWN/UP Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 May 2013 17:31:13 +0300 From: Daniel Braniss Message-ID: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 14:40:22 -0000 hi, after upgrading to 9.1-stable, this particular hardware - SunFire X2200, is toggeling bge1 DOWN/UP every few hours, this port is being used by the ILO. To check, I upgraded another identical host, and the same problem appears. There is not correlation with time, since they happend at totaly different times. I rebooted both hosts at almost the same time. one host : uptime: 5:24PM up 6:15, 0 users, load averages: 0.00, 0.00, 0.00 May 24 12:53:52 sf-04 kernel: bge1: link state changed to DOWN May 24 12:53:55 sf-04 kernel: bge1: link state changed to UP May 24 15:34:25 sf-04 kernel: bge1: link state changed to DOWN May 24 15:34:28 sf-04 kernel: bge1: link state changed to UP and uptime: 5:24PM up 6:14, 0 users, load averages: 0.00, 0.00, 0.00 May 24 16:30:44 sf-10 kernel: bge1: link state changed to DOWN May 24 16:30:44 sf-10 kernel: bge1: link state changed to UP this is not serious, the ilo (ssh) connection is ok, but it's anoying, we have more than 10 of this hosts, and if I upgrade all of them, the logs will fill up with this :-) any ideas? cheers, danny From owner-freebsd-stable@FreeBSD.ORG Fri May 24 15:06:28 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AC15CADC for ; Fri, 24 May 2013 15:06:28 +0000 (UTC) (envelope-from feld@feld.me) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 7F147800 for ; Fri, 24 May 2013 15:06:27 +0000 (UTC) Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 1D73B20B3D for ; Fri, 24 May 2013 11:06:21 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 24 May 2013 11:06:22 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=feld.me; h= content-type:references:subject:to:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to; s= mesmtp; bh=FKmwrE/cGUJzDyBdY4/CARoNlVM=; b=ngInhLGkmGPby1d8ORKDO l2+TU1ShTiQ5cc+CPjWYi67d6YhH5ZXKIsr0JeWKUsUJ+LbWUY0j0e72pSvrbNZn efUJ3KeC8RASvC01yYbXqyq3OtJAN0fttnQfBzNwwDpbCAhteqwhu2I/ZMEXXKmW yO+4du0lD1+2jEHocIBr2s= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:references:subject:to:date :mime-version:content-transfer-encoding:from:message-id :in-reply-to; s=smtpout; bh=FKmwrE/cGUJzDyBdY4/CARoNlVM=; b=KxSa dgjlAlDIQZq1Gxwc2XzPhdFeB23RxsUCtAlgksmu6Pl3KfKVgQyhWmK4KRgtcQKp q11Qjl7sIbgGURB4CoVAKzUSACfWfXhNNERvA9Nya9p4/QWQtQprQow8W58ADY6y PY8Ag0YASBxX/I+PxO/CSsjp/wcJUcP/V2ATXAI= X-Sasl-enc: UHX4Oy+MKmYGENqX80hVwDKQE5uF7Vske2QU9ev/hwsg 1369407981 Received: from markf.office.supranet.net (unknown [66.170.8.18]) by mail.messagingengine.com (Postfix) with ESMTPA id 67D38C8000C for ; Fri, 24 May 2013 11:06:21 -0400 (EDT) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes References: Subject: Re: SunFire X2200 ilo's bge1 DOWN/UP To: freebsd-stable@freebsd.org Date: Fri, 24 May 2013 10:06:21 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Mark Felder" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.15 (FreeBSD) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 15:06:28 -0000 Is this your bug? http://www.freebsd.org/cgi/query-pr.cgi?pr=171121 From owner-freebsd-stable@FreeBSD.ORG Fri May 24 15:23:27 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 11B2F1D5; Fri, 24 May 2013 15:23:27 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) by mx1.freebsd.org (Postfix) with ESMTP id C28238C7; Fri, 24 May 2013 15:23:26 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r4OFNK5P091181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 May 2013 08:23:20 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r4OFNKBQ091180; Fri, 24 May 2013 08:23:20 -0700 (PDT) (envelope-from jmg) Date: Fri, 24 May 2013 08:23:20 -0700 From: John-Mark Gurney To: Hiroki Sato Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524152319.GA90852@funkthat.com> Mail-Followup-To: Hiroki Sato , pyunyh@gmail.com, jdc@koitsu.org, gjb@freebsd.org, freebsd-stable@freebsd.org, re@freebsd.org References: <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com> <20130524.162926.395058052118975996.hrs@allbsd.org> <20130524.163646.628115045676432731.hrs@allbsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524.163646.628115045676432731.hrs@allbsd.org> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Fri, 24 May 2013 08:23:20 -0700 (PDT) Cc: pyunyh@gmail.com, jdc@koitsu.org, freebsd-stable@freebsd.org, re@freebsd.org, gjb@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 15:23:27 -0000 Hiroki Sato wrote this message on Fri, May 24, 2013 at 16:36 +0900: > Hiroki Sato wrote > in <20130524.162926.395058052118975996.hrs@allbsd.org>: > > hr> YongHyeon PYUN wrote > hr> in <20130524054720.GA1496@michelle.cdnetworks.com>: > hr> > hr> A workaround is specifying the following line in rc.conf: > hr> > hr> ifconfig_fxp0="DHCP media 100baseTX mediaopt full-duplex" > > Hmm, I guess this can happen on other NICs when the link negotiation > causes a link-state flap. Is it true? Just as a bit of history of this change (since I think I may have introduced part of this issue in 163061 of if_fxp.c)... fxp used to previously not drop link when you would switch from autoneg to a fixed media... The problem with this was that if you booted it always defaults to autoneg and if your switch was autoneg, then the switch would negotiate 100/full. If you then manually switched fxp to 100/full, things would be fine till either the switch was reset and/or the cable pulled. Then when the switch came back and was not be able to autoneg, it then would make the link 100/half, which of course would cause problems.... I made this change because it was better to flap the link on media switch, and force and earlier detection that there was this mismatch between the switch, then possibly months or years later... I actually believe all 100Mbps cards should do this on media change in order to prevent the above issue... Unless of course the card can do both autoneg and fixed media at the same time, which is probably the problem with this fxp chip/phy... Hope this helps with some history behind this issue.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-stable@FreeBSD.ORG Fri May 24 15:35:20 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A4F3A555 for ; Fri, 24 May 2013 15:35:20 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 68774979 for ; Fri, 24 May 2013 15:35:20 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id AA6A12842E; Fri, 24 May 2013 17:35:12 +0200 (CEST) Received: from [192.168.1.2] (ip-89-177-49-222.net.upcbroadband.cz [89.177.49.222]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 9405528427; Fri, 24 May 2013 17:35:11 +0200 (CEST) Message-ID: <519F88AE.4020203@quip.cz> Date: Fri, 24 May 2013 17:35:10 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: Daniel Braniss Subject: Re: SunFire X2200 ilo's bge1 DOWN/UP References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 15:35:20 -0000 Daniel Braniss wrote: > hi, after upgrading to 9.1-stable, this particular hardware - SunFire X2200, > is toggeling bge1 DOWN/UP every few hours, this port is being used by the ILO. > To check, I upgraded another identical host, and the same problem appears. > There > is not correlation with time, since they happend at totaly different times. > I rebooted both hosts at almost the same time. > one host : > uptime: 5:24PM up 6:15, 0 users, load averages: 0.00, 0.00, 0.00 > May 24 12:53:52 sf-04 kernel: bge1: link state changed to DOWN > May 24 12:53:55 sf-04 kernel: bge1: link state changed to UP > May 24 15:34:25 sf-04 kernel: bge1: link state changed to DOWN > May 24 15:34:28 sf-04 kernel: bge1: link state changed to UP > > and > uptime: 5:24PM up 6:14, 0 users, load averages: 0.00, 0.00, 0.00 > > May 24 16:30:44 sf-10 kernel: bge1: link state changed to DOWN > May 24 16:30:44 sf-10 kernel: bge1: link state changed to UP > > this is not serious, the ilo (ssh) connection is ok, but it's anoying, we have > more > than 10 of this hosts, and if I upgrade all of them, the logs will fill up > with this :-) What revision are you running? There was problem report at February http://lists.freebsd.org/pipermail/freebsd-net/2013-February/034715.html http://lists.freebsd.org/pipermail/freebsd-net/2013-March/034778.html I provided access to Yongari to our Sun Fire X2100 M2 (bge 5715C) and he fixed the problem. (in revision r248226, I don't know if it was MFCed) http://lists.freebsd.org/pipermail/freebsd-net/2013-March/034922.html Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Fri May 24 18:04:10 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 269EA569; Fri, 24 May 2013 18:04:10 +0000 (UTC) (envelope-from john@theusgroup.com) Received: from theusgroup.com (theusgroup.com [64.122.243.222]) by mx1.freebsd.org (Postfix) with ESMTP id 09A4C689; Fri, 24 May 2013 18:04:10 +0000 (UTC) From: John To: "Michael L. Squires" Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 In-reply-to: References: <20130508174721.GD1651@glenbarber.us> <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> Comments: In-reply-to "Michael L. Squires" message dated "Fri, 24 May 2013 08:51:00 -0400." Date: Fri, 24 May 2013 11:04:07 -0700 Message-Id: <20130524180408.0A297A86@server.theusgroup.com> Cc: Jeremy Chadwick , YongHyeon PYUN , freebsd-stable@FreeBSD.org, Craig Rodrigues , Glen Barber , FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 18:04:10 -0000 > >I agree that this seems to be a problem only experienced by those still >using the fxp interface and DHCP on a certain subset of Supermicro >systems, which has to be a very small group. > This isn't entirely correct. The test box I used has an Intel Pro 100 pci card plugged into an Intel motherboard. fxp0: port 0xe000-0xe03f mem 0xfe600000-0xfe600fff,0xfe500000-0xfe5fffff irq 22 at device 1.0 on pci3 miibus0: on fxp0 inphy0: PHY 1 on miibus0 John Theus TheUsGroup.com From owner-freebsd-stable@FreeBSD.ORG Sat May 25 16:26:44 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 00D4B805 for ; Sat, 25 May 2013 16:26:43 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id AAE998C5 for ; Sat, 25 May 2013 16:26:42 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1UgHIc-0001xB-Fc; Sat, 25 May 2013 19:26:31 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: SunFire X2200 ilo's bge1 DOWN/UP In-reply-to: <519F88AE.4020203@quip.cz> References: <519F88AE.4020203@quip.cz> Comments: In-reply-to Miroslav Lachman <000.fbsd@quip.cz> message dated "Fri, 24 May 2013 17:35:10 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 May 2013 19:26:30 +0300 From: Daniel Braniss Message-ID: Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 May 2013 16:26:44 -0000 > Daniel Braniss wrote: > > hi, after upgrading to 9.1-stable, this particular hardware - SunFire X2200, > > is toggeling bge1 DOWN/UP every few hours, this port is being used by the ILO. > > To check, I upgraded another identical host, and the same problem appears. > > There > > is not correlation with time, since they happend at totaly different times. > > I rebooted both hosts at almost the same time. > > one host : > > uptime: 5:24PM up 6:15, 0 users, load averages: 0.00, 0.00, 0.00 > > May 24 12:53:52 sf-04 kernel: bge1: link state changed to DOWN > > May 24 12:53:55 sf-04 kernel: bge1: link state changed to UP > > May 24 15:34:25 sf-04 kernel: bge1: link state changed to DOWN > > May 24 15:34:28 sf-04 kernel: bge1: link state changed to UP > > > > and > > uptime: 5:24PM up 6:14, 0 users, load averages: 0.00, 0.00, 0.00 > > > > May 24 16:30:44 sf-10 kernel: bge1: link state changed to DOWN > > May 24 16:30:44 sf-10 kernel: bge1: link state changed to UP > > > > this is not serious, the ilo (ssh) connection is ok, but it's anoying, we have > > more > > than 10 of this hosts, and if I upgrade all of them, the logs will fill up > > with this :-) > > What revision are you running? > Friday morning's, probably r250960 (I run svnsync then convert to hg :-) > There was problem report at February > http://lists.freebsd.org/pipermail/freebsd-net/2013-February/034715.html > http://lists.freebsd.org/pipermail/freebsd-net/2013-March/034778.html > > I provided access to Yongari to our Sun Fire X2100 M2 (bge 5715C) and he > fixed the problem. (in revision r248226, I don't know if it was MFCed) > > http://lists.freebsd.org/pipermail/freebsd-net/2013-March/034922.html > > Miroslav Lachman well, it seems different, it just goes down, then few secs later goes up. thanks, danny From owner-freebsd-stable@FreeBSD.ORG Sat May 25 16:35:21 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E3A4BACB for ; Sat, 25 May 2013 16:35:21 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 9CA3C92E for ; Sat, 25 May 2013 16:35:21 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1UgHR7-00021c-AE; Sat, 25 May 2013 19:35:17 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: "Mark Felder" Subject: Re: SunFire X2200 ilo's bge1 DOWN/UP In-reply-to: References: Comments: In-reply-to "Mark Felder" message dated "Fri, 24 May 2013 10:06:21 -0500." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 May 2013 19:35:17 +0300 From: Daniel Braniss Message-ID: Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 May 2013 16:35:21 -0000 > Is this your bug? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=171121 no, this bge is only used for the ilo, it happens even if it's idling, ie no active connection. it is also very erratic, it happens at random intervals, from 3 hs to 10hs, and the down/up 'hickup' lasts between less than a sec to about 3sec. thanks, danny