From owner-freebsd-stable@FreeBSD.ORG Sun Sep 9 13:25:39 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 682CB106564A; Sun, 9 Sep 2012 13:25:39 +0000 (UTC) (envelope-from kirk.j.russell@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id C8CE18FC14; Sun, 9 Sep 2012 13:25:38 +0000 (UTC) Received: by wibhi8 with SMTP id hi8so868330wib.13 for ; Sun, 09 Sep 2012 06:25:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=XTm1IQOUVn/DbbV1bbWW6QbRFi8Te2PSEbBER5dX+ZY=; b=beD0/3cql53fPs9R83b0EjIkgbYBgz+ZzdkVJWy2l3F6nFQIlSsxT7vjXu24A8i0+Y izk3doyWV+h8lJ1XAd02l4HS7kP1N1NpUjoSQUh+3DCyst7Iagj13iCcJ3Cf2Ho55rgr vgykypKztQKHGueAzH/5iJ1u6sTDqmSe0seBKAtO8K7AocyQgM0ZdGE5iSco678WSthS G5X9h8yne6uhHjW4dUw6r5Uuasv/1St/hMcEODsrwUmS6aVWmG8VbBcggQGQKaUdCz8P P71MW6ngVggAoxcxAsbqXS4PvDWBlimnPrteQvlY3j1zgfYtpD8780eho56DTITZjIjA knVQ== MIME-Version: 1.0 Received: by 10.216.181.67 with SMTP id k45mr5825180wem.17.1347197137488; Sun, 09 Sep 2012 06:25:37 -0700 (PDT) Sender: kirk.j.russell@gmail.com Received: by 10.180.164.14 with HTTP; Sun, 9 Sep 2012 06:25:37 -0700 (PDT) In-Reply-To: <504B2C35.3030800@FreeBSD.org> References: <504B2C35.3030800@FreeBSD.org> Date: Sun, 9 Sep 2012 14:25:37 +0100 X-Google-Sender-Auth: U4fuIluMxbu8l5hDr4MTlKWnivc Message-ID: From: kirk russell To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.1 RC1 and CAM issues with old SCSI drive X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kirk@ba23.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Sep 2012 13:25:39 -0000 On Sat, Sep 8, 2012 at 12:29 PM, Alexander Motin wrote: > Hi. > > It seems like both of your problems have the same cause: device report wrong > size of INQUIRY data, that causes failure on attempt to fetch it. With > FreeBSD 9.0 it caused domain validation failures and so reduced transfer > rate, on 9.1 it also causes detection failure. I am not sure why detection > worked on 9.0, it needs some deeper code comparison, but I think it is > mostly device problem. > > Could you send me output of such commands from FreeBSD 9.0: > camcontrol cmd da0 -vEc "12 00 00 00 24 00" -i 36 - | hd > camcontrol cmd da0 -vEc "12 00 00 00 fe 00" -i 254 - | hd > camcontrol cmd da0 -vEc "12 00 00 01 00 00" -i 256 - | hd > > -- > Alexander Motin This is running 9.0-RELEASE. # camcontrol cmd da0 -vEc "12 00 00 00 24 00" -i 36 - | hd 00000000 00 00 02 02 fa 00 00 3e 43 4f 4d 50 41 51 50 43 |.......>COMPAQPC| 00000010 57 44 45 39 31 30 30 57 20 20 20 20 20 20 20 20 |WDE9100W | 00000020 31 2e 30 31 |1.01| 00000024 # camcontrol cmd da0 -vEc "12 00 00 00 fe 00" -i 254 - | hd 00000000 00 00 02 02 fa 00 00 3e 43 4f 4d 50 41 51 50 43 |.......>COMPAQPC| 00000010 57 44 45 39 31 30 30 57 20 20 20 20 20 20 20 20 |WDE9100W | 00000020 31 2e 30 31 32 33 30 31 57 53 37 30 32 30 33 37 |1.012301WS702037| 00000030 32 34 39 33 00 00 00 00 20 20 20 20 20 20 20 20 |2493.... | 00000040 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | * 00000060 57 44 45 39 31 30 30 2d 36 30 30 35 44 30 20 20 |WDE9100-6005D0 | 00000070 34 30 36 31 30 30 31 31 39 31 30 30 32 43 30 20 |4061001191002C0 | 00000080 32 34 30 38 00 00 00 00 00 00 00 00 00 00 00 00 |2408............| 00000090 00 00 00 00 4e 32 30 35 30 30 39 39 30 32 35 35 |....N20500990255| 000000a0 33 20 20 20 50 20 30 30 00 00 00 00 00 00 42 41 |3 P 00......BA| 000000b0 43 43 42 45 4b 43 31 39 39 38 30 38 32 38 57 53 |CCBEKC19980828WS| 000000c0 36 30 44 20 04 03 00 04 02 01 00 00 00 00 00 00 |60D ............| 000000d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000000f0 # camcontrol cmd da0 -vEc "12 00 00 01 00 00" -i 256 - | hd (pass1:ahc0:0:0:0): INQUIRY. CDB: 12 0 0 1 0 0 (pass1:ahc0:0:0:0): CAM status: SCSI Status Error (pass1:ahc0:0:0:0): SCSI status: Check Condition (pass1:ahc0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:24,0 (Invalid field in CDB) (pass1:ahc0:0:0:0): Command Specific Info: 0xffffffff (pass1:ahc0:0:0:0): Command byte 3 is invalid camcontrol: error sending command (pass1:ahc0:0:0:0): INQUIRY. CDB: 12 0 0 1 0 0 (pass1:ahc0:0:0:0): CAM status: SCSI Status Error (pass1:ahc0:0:0:0): SCSI status: Check Condition (pass1:ahc0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:24,0 (Invalid field in CDB) (pass1:ahc0:0:0:0): Command Specific Info: 0xffffffff (pass1:ahc0:0:0:0): Command byte 3 is invalid -- Kirk Russell http://www.ba23.org/ From owner-freebsd-stable@FreeBSD.ORG Sun Sep 9 15:54:30 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 88C94106566B for ; Sun, 9 Sep 2012 15:54:30 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 015828FC12 for ; Sun, 9 Sep 2012 15:54:29 +0000 (UTC) Received: by lage12 with SMTP id e12so991253lag.13 for ; Sun, 09 Sep 2012 08:54:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=u8GHfDR6+mKaKHbALtwj4CzmMuZS7NeYS0pE4Vv2Guo=; b=VBM5iaid3HAtbZERNtB+epQEzcB80b6ZzQ5jUs/STd/HaNVdLi3iy0N8zBqccpWNJK eDAuPEalciceAUno+27Hyq8hsZ4gj7luPUCYl94jnI8+7DWZ2LTempzBAJDN4TIiBvdj XHC7OdvRLIlWDjK3dw0CMm+HjT3zF8tap03Vn5fDH2eb5XCQWWJdeAV5X96S+TWh4vyt ornckgS8g+oWvyilk2sSb3DTs6iHo1p7aIMNqzcbN9LyLwogXWxg/cImiyvijbQTgHw3 bNk09Qyijj1yKwFOsI5NpEThvOwdfPDaZiUaFEMiANeS93gzbcW963FcSnC6rILcXfWf 88VQ== Received: by 10.152.129.104 with SMTP id nv8mr10175168lab.32.1347206068469; Sun, 09 Sep 2012 08:54:28 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id d1sm2864695lbk.16.2012.09.09.08.54.26 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 09 Sep 2012 08:54:27 -0700 (PDT) Sender: Alexander Motin Message-ID: <504CBBB1.20905@FreeBSD.org> Date: Sun, 09 Sep 2012 18:54:25 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120628 Thunderbird/13.0.1 MIME-Version: 1.0 To: kirk@ba23.org References: <504B2C35.3030800@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.1 RC1 and CAM issues with old SCSI drive X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Sep 2012 15:54:30 -0000 On 09.09.2012 16:25, kirk russell wrote: > On Sat, Sep 8, 2012 at 12:29 PM, Alexander Motin wrote: >> Hi. >> >> It seems like both of your problems have the same cause: device report wrong >> size of INQUIRY data, that causes failure on attempt to fetch it. With >> FreeBSD 9.0 it caused domain validation failures and so reduced transfer >> rate, on 9.1 it also causes detection failure. I am not sure why detection >> worked on 9.0, it needs some deeper code comparison, but I think it is >> mostly device problem. >> >> Could you send me output of such commands from FreeBSD 9.0: >> camcontrol cmd da0 -vEc "12 00 00 00 24 00" -i 36 - | hd >> camcontrol cmd da0 -vEc "12 00 00 00 fe 00" -i 254 - | hd >> camcontrol cmd da0 -vEc "12 00 00 01 00 00" -i 256 - | hd >> >> -- >> Alexander Motin > > This is running 9.0-RELEASE. > > # camcontrol cmd da0 -vEc "12 00 00 00 24 00" -i 36 - | hd > 00000000 00 00 02 02 fa 00 00 3e 43 4f 4d 50 41 51 50 43 |.......>COMPAQPC| > 00000010 57 44 45 39 31 30 30 57 20 20 20 20 20 20 20 20 |WDE9100W | > 00000020 31 2e 30 31 |1.01| > 00000024 > # camcontrol cmd da0 -vEc "12 00 00 00 fe 00" -i 254 - | hd > 00000000 00 00 02 02 fa 00 00 3e 43 4f 4d 50 41 51 50 43 |.......>COMPAQPC| > 00000010 57 44 45 39 31 30 30 57 20 20 20 20 20 20 20 20 |WDE9100W | > 00000020 31 2e 30 31 32 33 30 31 57 53 37 30 32 30 33 37 |1.012301WS702037| > 00000030 32 34 39 33 00 00 00 00 20 20 20 20 20 20 20 20 |2493.... | > 00000040 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | > * > 00000060 57 44 45 39 31 30 30 2d 36 30 30 35 44 30 20 20 |WDE9100-6005D0 | > 00000070 34 30 36 31 30 30 31 31 39 31 30 30 32 43 30 20 |4061001191002C0 | > 00000080 32 34 30 38 00 00 00 00 00 00 00 00 00 00 00 00 |2408............| > 00000090 00 00 00 00 4e 32 30 35 30 30 39 39 30 32 35 35 |....N20500990255| > 000000a0 33 20 20 20 50 20 30 30 00 00 00 00 00 00 42 41 |3 P 00......BA| > 000000b0 43 43 42 45 4b 43 31 39 39 38 30 38 32 38 57 53 |CCBEKC19980828WS| > 000000c0 36 30 44 20 04 03 00 04 02 01 00 00 00 00 00 00 |60D ............| > 000000d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| > * > 000000f0 > # camcontrol cmd da0 -vEc "12 00 00 01 00 00" -i 256 - | hd > (pass1:ahc0:0:0:0): INQUIRY. CDB: 12 0 0 1 0 0 > (pass1:ahc0:0:0:0): CAM status: SCSI Status Error > (pass1:ahc0:0:0:0): SCSI status: Check Condition > (pass1:ahc0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:24,0 (Invalid field in CDB) > (pass1:ahc0:0:0:0): Command Specific Info: 0xffffffff > (pass1:ahc0:0:0:0): Command byte 3 is invalid > camcontrol: error sending command > (pass1:ahc0:0:0:0): INQUIRY. CDB: 12 0 0 1 0 0 > (pass1:ahc0:0:0:0): CAM status: SCSI Status Error > (pass1:ahc0:0:0:0): SCSI status: Check Condition > (pass1:ahc0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:24,0 (Invalid field in CDB) > (pass1:ahc0:0:0:0): Command Specific Info: 0xffffffff > (pass1:ahc0:0:0:0): Command byte 3 is invalid It seems that problem can be in our SCSI code that rounds inquiry data size up to even. Please try to comment out line inquiry_len = roundup2(inquiry_len, 2); in sys/cam/scsi/scsi_xpt.c and rebuild the kernel. It should probably fix both device detection and transfer speed. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Sun Sep 9 17:11:25 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A019A106566B; Sun, 9 Sep 2012 17:11:25 +0000 (UTC) (envelope-from kirk.j.russell@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 04F508FC0C; Sun, 9 Sep 2012 17:11:24 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so1010600wgb.31 for ; Sun, 09 Sep 2012 10:11:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=49urNlBcDR1ZVjLc0FmTSSEtfD0GQmbbe9fnW5mLcoY=; b=c96ZwkYSPGrWIZCyj7uVqsLP3ygMTJnxa/roaXYzGFpHsC+yYyf6ppFmJ0mnNmj2uH ImtfcoMllp+ASOyc/cjDIsIwKUZKb6ujikb2nu3kI9IkOcH1T1jJzLLt2FBf9R/tUjDv ecU0uX37VGGpbWmToTUZBg1CyTZHV6yftaToKKWEAGmu6aHK5VIPx+fELZ2+foY3FFgX oSNb8snKsfwr1Ft09rwGH74eaiJ80b/TTip/NLkPMmTgypjRfJ0VtNXTVqKM+0DjTuy9 lqOLiHNpPLCjoUXoG2XEGn7Ia4twqyNlAu11Uc5KhAsXWILtZIOuO37q3jf6iHMHVzEY HtQg== MIME-Version: 1.0 Received: by 10.180.96.3 with SMTP id do3mr11543119wib.5.1347210683561; Sun, 09 Sep 2012 10:11:23 -0700 (PDT) Sender: kirk.j.russell@gmail.com Received: by 10.180.164.14 with HTTP; Sun, 9 Sep 2012 10:11:23 -0700 (PDT) In-Reply-To: <504CBBB1.20905@FreeBSD.org> References: <504B2C35.3030800@FreeBSD.org> <504CBBB1.20905@FreeBSD.org> Date: Sun, 9 Sep 2012 18:11:23 +0100 X-Google-Sender-Auth: os-XQaNF1AYf-scadmnm38X3Ons Message-ID: From: kirk russell To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.1 RC1 and CAM issues with old SCSI drive X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kirk@ba23.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Sep 2012 17:11:25 -0000 On Sun, Sep 9, 2012 at 4:54 PM, Alexander Motin wrote: > On 09.09.2012 16:25, kirk russell wrote: >> >> On Sat, Sep 8, 2012 at 12:29 PM, Alexander Motin wrote: >>> >>> Hi. >>> >>> It seems like both of your problems have the same cause: device report >>> wrong >>> size of INQUIRY data, that causes failure on attempt to fetch it. With >>> FreeBSD 9.0 it caused domain validation failures and so reduced transfer >>> rate, on 9.1 it also causes detection failure. I am not sure why >>> detection >>> worked on 9.0, it needs some deeper code comparison, but I think it is >>> mostly device problem. >>> >>> Could you send me output of such commands from FreeBSD 9.0: >>> camcontrol cmd da0 -vEc "12 00 00 00 24 00" -i 36 - | hd >>> camcontrol cmd da0 -vEc "12 00 00 00 fe 00" -i 254 - | hd >>> camcontrol cmd da0 -vEc "12 00 00 01 00 00" -i 256 - | hd >>> >>> -- >>> Alexander Motin >> >> [.....] > > It seems that problem can be in our SCSI code that rounds inquiry data size > up to even. Please try to comment out line > inquiry_len = roundup2(inquiry_len, 2); > in sys/cam/scsi/scsi_xpt.c and rebuild the kernel. It should probably fix > both device detection and transfer speed. > This is running 9.0-RELEASE, with your patch to scsi_xpt.c: da0 at ahc0 bus 0 scbus2 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: Command Queueing enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) This is running FreeBSD 9.1-RC1, with your patch to scsi_xpt.c: da0 at ahc0 bus 0 scbus2 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: Command Queueing enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) -- Kirk Russell http://www.ba23.org/ From owner-freebsd-stable@FreeBSD.ORG Sun Sep 9 18:49:46 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 691161065672 for ; Sun, 9 Sep 2012 18:49:46 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) by mx1.freebsd.org (Postfix) with ESMTP id 1C3918FC0A for ; Sun, 9 Sep 2012 18:49:46 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id E126625D3888; Sun, 9 Sep 2012 18:49:44 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id E5335BE84AE; Sun, 9 Sep 2012 18:49:43 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id Tj64NJrbYJ8Y; Sun, 9 Sep 2012 18:49:42 +0000 (UTC) Received: from nv.sbone.de (nv.sbone.de [IPv6:fde9:577b:c1a9:31::2013:138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 45A08BE84AD; Sun, 9 Sep 2012 18:49:42 +0000 (UTC) Date: Sun, 9 Sep 2012 18:49:41 +0000 (UTC) From: "Bjoern A. Zeeb" To: Norbert Aschendorff In-Reply-To: <503F8186.4070906@yahoo.de> Message-ID: References: <503CE60F.8040007@yahoo.de> <503E5C14.9090001@yahoo.de> <503F8186.4070906@yahoo.de> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: IPv4 vs. IPv6 Ethernet Performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Sep 2012 18:49:46 -0000 On Thu, 30 Aug 2012, Norbert Aschendorff wrote: Hi, > I tested it using tcpdump: http://nopaste.info/9394068f54_nl.html > The length field says for each packet 1408 bytes, so that should be OK. > > The Wireshark instance on the iperf server says something like "16732 > bytes on wire" for the most packets (not always with 16732 bytes, but > most packets over 10,000) - could that be reassembled somehow? only slowly catching up on email so... chiming in now. I'd assume in this case the iperf "server" is linux or did Jack add IPv6 LRO support to e1000? Sorry, I am not up-to-date. However, any modern peice of hardware should be able to fill the 1G link even with software doing csums or offloading really and all our routing table lookups. What's the well known FreeBSD machine of a machine? I can only imaging what's going on for you and some of the latest work was not yet merged to head or 9; I have 1 or 2 patches posted to net@ for review and testing though. Sorry not immediately helpful. /bz -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. From owner-freebsd-stable@FreeBSD.ORG Sun Sep 9 22:03:53 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42A1A106566B for ; Sun, 9 Sep 2012 22:03:53 +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 00AC98FC08 for ; Sun, 9 Sep 2012 22:03:51 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 3E84228427 for ; Sun, 9 Sep 2012 23:56:57 +0200 (CEST) Received: from [192.168.1.2] (static-84-242-120-26.net.upcbroadband.cz [84.242.120.26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 7C84A28423 for ; Sun, 9 Sep 2012 23:56:56 +0200 (CEST) Message-ID: <504D10A7.1070701@quip.cz> Date: Sun, 09 Sep 2012 23:56:55 +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: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: bsnmpd always died on HDD detach X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Sep 2012 22:03:53 -0000 I am running bsnmpd with basic snmpd.config (only community and location changed). When there is a problem with HDD and disk disapeared from ATA channel (eg.: disc physically removed) the bsnmpd always dumps core: kernel: pid 1188 (bsnmpd), uid 0: exited on signal 11 (core dumped) I see this for a long rime on all releases of 7.x and 8.x branches (i386 and amd64). I did not tested 9.x. Is it a known bug, or should I file PR? Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Mon Sep 10 05:45:08 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE8B2106566B for ; Mon, 10 Sep 2012 05:45:07 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 7D5AC8FC0A for ; Mon, 10 Sep 2012 05:45:07 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so1308864wgb.31 for ; Sun, 09 Sep 2012 22:45:06 -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=0WiWD95fHXv/fYuhfHhqM0W25YOVKZE0tqkn0Xyg+0A=; b=GkxfgVzC/nzH6AkoD4EIf2kffN97lRoLdLF92O8RZsfIHltSCDcdBYA/mQvvyjyF2d c+q3lsUWELWyQCH09hGGgAR5iA9kE/OEqRic0MXRwQYHccub1DKJA7vAFCAiTdvzCeS1 FHQIeVWx7ER5cDXMLmHbAo28HjPKUCt1akH3p4oVZXd2/RhwbgL7bnFzzE9m+LpKAP7W g5ccGIWePOKkE8Ru/QBqVTs0GSBzCTxa6N8sOCxzpNlFBcNGEglQicNTxA9gncp1NYvY 3amp0MbmxDKkZpJ5G4uWuBKqOAMCizg/DlRQ3u50cLNegAHjfitwNG+1V09tVClVjdR+ BHkw== Received: by 10.180.8.41 with SMTP id o9mr14569449wia.3.1347255904834; Sun, 09 Sep 2012 22:45:04 -0700 (PDT) Received: from localhost ([188.230.122.226]) by mx.google.com with ESMTPS id q4sm15468192wix.9.2012.09.09.22.45.02 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 09 Sep 2012 22:45:03 -0700 (PDT) Date: Mon, 10 Sep 2012 08:45:01 +0300 From: Mikolaj Golub To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20120910054459.GA57302@gmail.com> References: <504D10A7.1070701@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <504D10A7.1070701@quip.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: bsnmpd always died on HDD detach X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 05:45:08 -0000 On Sun, Sep 09, 2012 at 11:56:55PM +0200, Miroslav Lachman wrote: > I am running bsnmpd with basic snmpd.config (only community and location > changed). > > When there is a problem with HDD and disk disapeared from ATA channel > (eg.: disc physically removed) the bsnmpd always dumps core: > > kernel: pid 1188 (bsnmpd), uid 0: exited on signal 11 (core dumped) > > I see this for a long rime on all releases of 7.x and 8.x branches (i386 > and amd64). I did not tested 9.x. > > Is it a known bug, or should I file PR? Do you happen to run bsnmp-ucd too? If you do then what version is it? In bsnmp-ucd-0.3.5 I introduced a bug that lead to bsnmpd crash on a disk detach. It has been fixed (thanks to Brian Somers) in 0.3.6. -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Mon Sep 10 13:01:05 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 56F4C1065672; Mon, 10 Sep 2012 13:01:05 +0000 (UTC) (envelope-from jl.dupont@outlook.com) Received: from blu0-omc2-s34.blu0.hotmail.com (blu0-omc2-s34.blu0.hotmail.com [65.55.111.109]) by mx1.freebsd.org (Postfix) with ESMTP id 116E48FC14; Mon, 10 Sep 2012 13:01:04 +0000 (UTC) Received: from BLU002-W101 ([65.55.111.71]) by blu0-omc2-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 10 Sep 2012 06:00:57 -0700 Message-ID: X-Originating-IP: [194.145.144.230] From: Jean-Luc Dupont To: Gleb Smirnoff Date: Mon, 10 Sep 2012 13:00:57 +0000 Importance: Normal In-Reply-To: <20120907131441.GH44854@FreeBSD.org> References: , , <20120907131441.GH44854@FreeBSD.org> MIME-Version: 1.0 X-OriginalArrivalTime: 10 Sep 2012 13:00:57.0861 (UTC) FILETIME=[51F46B50:01CD8F54] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-stable@freebsd.org" Subject: RE: Kernel Panic on 9.0 and 9.1 with carp on BCE network interface X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 13:01:05 -0000 PiBEYXRlOiBGcmksIDcgU2VwIDIwMTIgMTc6MTQ6NDEgKzA0MDANCj4gRnJvbTogZ2xlYml1c0BG cmVlQlNELm9yZw0KPiBUbzogamwuZHVwb250QG91dGxvb2suY29tDQo+IENDOiBmcmVlYnNkLXN0 YWJsZUBGcmVlQlNELm9yZw0KPiBTdWJqZWN0OiBSZTogS2VybmVsIFBhbmljIG9uIDkuMCBhbmQg OS4xIHdpdGggY2FycCBvbiBCQ0UgbmV0d29yayBpbnRlcmZhY2UNCj4gDQo+IE9uIFRodSwgQXVn IDMwLCAyMDEyIGF0IDAyOjM5OjEwUE0gKzAwMDAsIEplYW4tTHVjIER1cG9udCB3cm90ZToNCj4g Sj4gU29ycnksIGl0IHNlZW1zIHRoYXQgSSBkaWRuJ3QgcHV0IHRoZSByaWdodCBiYWNrdHJhY2Ug Og0KPiBKPiANCj4gSj4gIzAgIGRvYWR1bXAgKHRleHRkdW1wPVZhcmlhYmxlICJ0ZXh0ZHVtcCIg aXMgbm90IGF2YWlsYWJsZS4NCj4gSj4gKSBhdCAvdXNyL3NyYy9zeXMva2Vybi9rZXJuX3NodXRk b3duLmM6MjcxDQo+IEo+IDI3MSAgICAgICAgICAgICAgICAgICAgIGR1bXBzeXMoJmR1bXBlcik7 DQo+IEo+IChrZ2RiKSAjMCAgZG9hZHVtcCAodGV4dGR1bXA9VmFyaWFibGUgInRleHRkdW1wIiBp cyBub3QgYXZhaWxhYmxlLg0KPiBKPiApIGF0IC91c3Ivc3JjL3N5cy9rZXJuL2tlcm5fc2h1dGRv d24uYzoyNzENCj4gSj4gIzEgIDB4ZmZmZmZmZmY4MDdmZGYwMiBpbiBrZXJuX3JlYm9vdCAoaG93 dG89MjYwKQ0KPiBKPiAgICAgYXQgL3Vzci9zcmMvc3lzL2tlcm4va2Vybl9zaHV0ZG93bi5jOjQ0 OA0KPiBKPiAjMiAgMHhmZmZmZmZmZjgwN2ZlM2UzIGluIHBhbmljIChmbXQ9MHgxMDQgPEFkZHJl c3MgMHgxMDQgb3V0IG9mIGJvdW5kcz4pDQo+IEo+ICAgICBhdCAvdXNyL3NyYy9zeXMva2Vybi9r ZXJuX3NodXRkb3duLmM6NjM2DQo+IEo+ICMzICAweGZmZmZmZmZmODBhZDI3MDAgaW4gdHJhcF9m YXRhbCAoZnJhbWU9MHhjLCBldmE9VmFyaWFibGUgImV2YSIgaXMgbm90IGF2YWlsYWJsZS4NCj4g Sj4gKQ0KPiBKPiAgICAgYXQgL3Vzci9zcmMvc3lzL2FtZDY0L2FtZDY0L3RyYXAuYzo4NTcNCj4g Sj4gIzQgIDB4ZmZmZmZmZmY4MGFkMmEzZCBpbiB0cmFwX3BmYXVsdCAoZnJhbWU9MHhmZmZmZmY4 MmU5N2EzNTAwLCB1c2VybW9kZT0wKQ0KPiBKPiAgICAgYXQgL3Vzci9zcmMvc3lzL2FtZDY0L2Ft ZDY0L3RyYXAuYzo3NzMNCj4gSj4gIzUgIDB4ZmZmZmZmZmY4MGFkMzA1ZSBpbiB0cmFwIChmcmFt ZT0weGZmZmZmZjgyZTk3YTM1MDApDQo+IEo+ICAgICBhdCAvdXNyL3NyYy9zeXMvYW1kNjQvYW1k NjQvdHJhcC5jOjQ1Ng0KPiBKPiAjNiAgMHhmZmZmZmZmZjgwYWJkNjdmIGluIGNhbGx0cmFwICgp DQo+IEo+ICAgICBhdCAvdXNyL3NyYy9zeXMvYW1kNjQvYW1kNjQvZXhjZXB0aW9uLlM6MjI4DQo+ IEo+ICM3ICAweGZmZmZmZmZmODA4NWY1OTcgaW4gbV9jb3B5bSAobT0weDAsIG9mZjA9MTUwMCwg bGVuPTE0ODAsIHdhaXQ9MSkNCj4gSj4gICAgIGF0IC91c3Ivc3JjL3N5cy9rZXJuL3VpcGNfbWJ1 Zi5jOjU0Mg0KPiBKPiAjOCAgMHhmZmZmZmZmZjgwOTJmMmM4IGluIGlwX2ZyYWdtZW50IChpcD0w eGZmZmZmZTAwOTcwZTA1ODAsIA0KPiBKPiAgICAgbV9mcmFnPTB4ZmZmZmZmODJlOTdhMzcyOCwg bXR1PVZhcmlhYmxlICJtdHUiIGlzIG5vdCBhdmFpbGFibGUuDQo+IEo+ICkgYXQgL3Vzci9zcmMv c3lzL25ldGluZXQvaXBfb3V0cHV0LmM6ODIyDQo+IEo+ICM5ICAweGZmZmZmZmZmODA5MmZjMTcg aW4gaXBfb3V0cHV0IChtPTB4ZmZmZmZlMDA5NzBlMDUwMCwgb3B0PVZhcmlhYmxlICJvcHQiIGlz IG5vdCBhdmFpbGFibGUuDQo+IEo+ICkNCj4gSj4gICAgIGF0IC91c3Ivc3JjL3N5cy9uZXRpbmV0 L2lwX291dHB1dC5jOjY1Mw0KPiBKPiAjMTAgMHhmZmZmZmZmZjgwOTI4NzEzIGluIGlwX2Zvcndh cmQgKG09MHhmZmZmZmUwMDk3MGUwNTAwLCBzcmNydD1WYXJpYWJsZSAic3JjcnQiIGlzIG5vdCBh dmFpbGFibGUuDQo+IEo+ICkNCj4gSj4gICAgIGF0IC91c3Ivc3JjL3N5cy9uZXRpbmV0L2lwX2lu cHV0LmM6MTQ5NA0KPiBKPiAjMTEgMHhmZmZmZmZmZjgwOTI5ZGM4IGluIGlwX2lucHV0IChtPTB4 ZmZmZmZlMDA5NzBlMDUwMCkNCj4gSj4gICAgIGF0IC91c3Ivc3JjL3N5cy9uZXRpbmV0L2lwX2lu cHV0LmM6NzAyDQo+IA0KPiBJIGRvbid0IHNlZSB0aGF0IHRoaXMgaXMgQ0FSUCByZWxhdGVkLiBE byB5b3UgdXNlIGFueSBmaXJld2FsbDogcGYgb3IgaXBmdz8NCj4gDQo+IENhbiB5b3UgcGxlYXNl IHNob3cgdGhlIGJlbG93IHNlc3Npb24gaW4gZ2RiIHdpdGggZGlzY3Vzc2VkIGNvcmUgZmlsZToN Cj4gDQo+IGdkYj4gZnIgOQ0KPiBnZGI+IHAgbXR1DQo+IGdkYj4gZnIgNw0KPiBnZGI+IHAgb2Zm DQo+IGdkYj4gZnIgOA0KPiBnZGI+IHAgbTANCj4gZ2RiPiBwICptMA0KPiANCj4gLS0gDQo+IFRv dHVzIHR1dXMsIEdsZWJpdXMuDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fDQo+IGZyZWVic2Qtc3RhYmxlQGZyZWVic2Qub3JnIG1haWxpbmcgbGlzdA0K PiBodHRwOi8vbGlzdHMuZnJlZWJzZC5vcmcvbWFpbG1hbi9saXN0aW5mby9mcmVlYnNkLXN0YWJs ZQ0KPiBUbyB1bnN1YnNjcmliZSwgc2VuZCBhbnkgbWFpbCB0byAiZnJlZWJzZC1zdGFibGUtdW5z dWJzY3JpYmVAZnJlZWJzZC5vcmciDQoNCkhpLCAgDQoNCiAgVGhhbmsgeW91IHZlcnkgbXVjaCBm b3IgeW91ciByZXBseSwgd2UgYXJlIHVzaW5nIElQRlcgd2l0aCBzZXZlcmFsIFZMQU4gYW5kIHNl dmVyYWwgQ0FSUCBvbiBpbnRlbCBpZ2IgYW5kIGJjZSBuZXR3b3JrIGNhcmRzIG9uIGEgZGVsbCBw b3dlcmVkZ2Ugc2VydmVycy4NCldoZW4gd2Ugc3RvcHBlZCB1c2luZyB0aGUgYmNlIGFuZCB1c2lu ZyBvbmx5IHRoZSBpZ2IgKHdpdGggbW9yZSB2bGFucyBwZXIgaW50ZXJmYWNlKSB3ZSBkb24ndCBo YXZlIGFueSBtb3JlIHBhbmljcy4NCg0KSGVyZSBpcyB0aGUgb3V0cHV0IG9mIHRoZSBkZWJ1Z2dl ciBhcyBhc2tlZCA6DQoNCihrZ2RiKSBmciA5DQojOSAgMHhmZmZmZmZmZjgwOTJmYzE3IGluIGlw X291dHB1dCAobT0weGZmZmZmZTAwOTQxYzgzMDAsIG9wdD1WYXJpYWJsZSAib3B0IiBpcyBub3Qg YXZhaWxhYmxlLg0KKSBhdCAvdXNyL3NyYy9zeXMvbmV0aW5ldC9pcF9vdXRwdXQuYzo2NTMNCjY1 MyAgICAgICAgICAgICBlcnJvciA9IGlwX2ZyYWdtZW50KGlwLCAmbSwgbXR1LCBpZnAtPmlmX2h3 YXNzaXN0LCBzd19jc3VtKTsNCihrZ2RiKSBwIG10dQ0KJDEgPSAxNTAwDQooa2dkYikgZnIgNw0K IzcgIDB4ZmZmZmZmZmY4MDg1ZjU5NyBpbiBtX2NvcHltIChtPTB4MCwgb2ZmMD0xNTAwLCBsZW49 MTMxNywgd2FpdD0xKSBhdCAvdXNyL3NyYy9zeXMva2Vybi91aXBjX21idWYuYzo1NDINCjU0MiAg ICAgICAgICAgICAgICAgICAgIGlmIChvZmYgPCBtLT5tX2xlbikNCihrZ2RiKSBwIG9mZg0KJDIg PSAxMjMzDQooa2dkYikgZnIgOA0KIzggIDB4ZmZmZmZmZmY4MDkyZjJjOCBpbiBpcF9mcmFnbWVu dCAoaXA9MHhmZmZmZmUwMDk0MWM4MzgwLCBtX2ZyYWc9MHhmZmZmZmY4MzQ4NjllN2Y4LCBtdHU9 VmFyaWFibGUgIm10dSIgaXMgbm90IGF2YWlsYWJsZS4NCikNCiAgICBhdCAvdXNyL3NyYy9zeXMv bmV0aW5ldC9pcF9vdXRwdXQuYzo4MjINCjgyMiAgICAgICAgICAgICAgICAgICAgIG0tPm1fbmV4 dCA9IG1fY29weW0obTAsIG9mZiwgbGVuLCBNX0RPTlRXQUlUKTsNCihrZ2RiKSBwIG0wDQokMyA9 IChzdHJ1Y3QgbWJ1ZiAqKSAweGZmZmZmZTAwOTQxYzgzMDANCihrZ2RiKSBwICptMA0KJDQgPSB7 bV9oZHIgPSB7bWhfbmV4dCA9IDB4ZmZmZmZlMDA4MWQ1MTgwMCwgbWhfbmV4dHBrdCA9IDB4MCwg bWhfZGF0YSA9IDB4ZmZmZmZlMDA5NDFjODM4MCAiRSIsIG1oX2xlbiA9IDQwLCANCiAgICBtaF9m bGFncyA9IDIsIG1oX3R5cGUgPSAxLCBwYWQgPSAiXDAwMFwwMDBcMDAwXDAwMFwwMDAifSwgTV9k YXQgPSB7TUggPSB7TUhfcGt0aGRyID0gew0KICAgICAgICByY3ZpZiA9IDB4ZmZmZmZlMDAwM2I1 MzgwMCwgaGVhZGVyID0gMHgwLCBsZW4gPSAyNjcsIGZsb3dpZCA9IDAsIGNzdW1fZmxhZ3MgPSAw LCBjc3VtX2RhdGEgPSA2NTUzNSwgDQogICAgICAgIHRzb19zZWdzeiA9IDAsIFBIX3Z0ID0ge3Z0 X3Z0YWcgPSAwLCB2dF9ucmVjcyA9IDB9LCB0YWdzID0ge3NsaF9maXJzdCA9IDB4MH19LCBNSF9k YXQgPSB7TUhfZXh0ID0gew0KICAgICAgICAgIGV4dF9idWYgPSAweDQwMDA5MmFlMDA0MDAwNDUg PEFkZHJlc3MgMHg0MDAwOTJhZTAwNDAwMDQ1IG91dCBvZiBib3VuZHM+LCBleHRfZnJlZSA9IDB4 MTYyMDcsIA0KICAgICAgICAgIGV4dF9hcmcxID0gMHg0MmZmZmYwMTFkMDAwMCwgZXh0X2FyZzIg PSAweDYwMTAwNWUwMDAwMDAwMCwgZXh0X3NpemUgPSAyNjYwMTQ3MjAwLCANCiAgICAgICAgICBy ZWZfY250ID0gMHg0MGY3ZTIwYjAxMDA0NSwgZXh0X3R5cGUgPSAtODQzOTcxMDIzfSwgDQogICAg ICAgIE1IX2RhdGFidWYgPSAiRVwwMDBAXDAwMO+/vVwyMjJcMDAwQFxhYlwwMDFcMDAwXDAwMFww MDBcMDAwXDAwMFwwMDBcMDAwXDAzNVwwMDHvv73vv71CXDAwMFwwMDBcMDAwXDAwMFwwMDBeXDAw MFwwMDFcMDA2XDAwMO+/vVwyMTZcMjM277+9XDIwMFxiXDAwMEVcMDAwXDAwMVx277+977+9QFww MDAxXDAwNu+/ve+/vUhcMDI1VO+/vVxuXG5cdktcMDAwXDAyNe+/ve+/vV5o77+977+977+9XDIy M1I+XDIwMFwwMzBcMDAwclwyMTPvv71cMDAwXDAwMFwwMDFcMDAxXGJcbu+/vSQqXDIwMDrvv73v v71cYSIsICdcMCcgPHJlcGVhdHMgNzUgdGltZXM+fX0sIA0KICAgIE1fZGF0YWJ1ZiA9ICJcMDAw OO+/vVwwMDNcMDAw77+977+977+9XDAwMFwwMDBcMDAwXDAwMFwwMDBcMDAwXDAwMFwwMDBcdlww MDFcMDAwXDAwMFwwMDBcMDAwXDAwMFwwMDBcMDAwXDAwMFwwMDBcMDAw77+977+9IiwgJ1wwJyA8 cmVwZWF0cyAxOCB0aW1lcz4sICJFXDAwMEBcMDAw77+9XDIyMlwwMDBAXGFiXDAwMVwwMDBcMDAw XDAwMFwwMDBcMDAwXDAwMFwwMDBcMDM1XDAwMe+/ve+/vUJcMDAwXDAwMFwwMDBcMDAwXDAwMF5c MDAwXDAwMVwwMDZcMDAw77+9XDIxNlwyMzbvv71cMjAwXGJcMDAwRVwwMDBcMDAxXHbvv73vv71A XDAwMDFcMDA277+977+9SFwwMjVU77+9XG5cblx2S1wwMDBcMDI177+977+9Xmjvv73vv73vv71c MjIzUj5cMjAwXDAzMFwwMDByXDIxM++/vVwwMDBcMDAwXDAwMVwwMDFcYlxu77+9JCpcMjAwOu+/ ve+/vVxhIiwgJ1wwJyA8cmVwZWF0cyA3NSB0aW1lcz59fQ0KKGtnZGIpIA0KDQogCQkgCSAgIAkJ ICA= From owner-freebsd-stable@FreeBSD.ORG Mon Sep 10 13:38:53 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06314106566B for ; Mon, 10 Sep 2012 13:38:53 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from mail.clearchain.com (leo.clearchain.com [199.73.29.74]) by mx1.freebsd.org (Postfix) with ESMTP id A69728FC08 for ; Mon, 10 Sep 2012 13:38:51 +0000 (UTC) Received: from pa106-71-128-107.pa.nsw.optusnet.com.au (pa106-71-128-107.pa.nsw.optusnet.com.au [106.71.128.107] (may be forged)) (authenticated bits=0) by mail.clearchain.com (8.14.5/8.14.5) with ESMTP id q8ADcZCM043899 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 10 Sep 2012 23:08:45 +0930 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <504DED78.2010203@clearchain.com> Date: Mon, 10 Sep 2012 23:09:04 +0930 From: Benjamin Close User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (mail.clearchain.com [199.73.29.74]); Mon, 10 Sep 2012 23:08:48 +0930 (CST) Subject: usb port issue in 9.1-Prerelease (Possibly Cam related) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 13:38:53 -0000 Hi Folks, I've facing an intermittent hang with a USB port which seems cam related: Event's that happen are: o USB modem (HUAWEI E220) plugged into PC ugen3.2: at usbus3 u3g0: <3G Modem> on usbus3 u3g0: Found 3 ports. umass0: on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:6:0:-1: Attached to scbus6 umass1: on usbus3 umass1: SCSI over Bulk-Only; quirks = 0x0000 umass1:7:1:-1: Attached to scbus7 cd1 at umass-sim0 bus 0 scbus6 target 0 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 1.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present da0 at umass-sim1 bus 1 scbus7 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present o Time Elapses....many packets passed, no da0 or cd1 used. o USB Modem drops off the bus (It does this occasionally as it resets itself) o Causes USB bus to lose devices ugen3.2: at usbus3 (disconnected) u3g0: at uhub3, port 1, addr 2 (disconnected) (cd1:umass-sim0:0:0:0): lost device, 1 refs (cd1:umass-sim0:0:0:0): removing device entry (pass4:umass-sim0:0:0:0): passdevgonecb: devfs entry is gone (da0:umass-sim1:1:0:0): lost device - 0 outstanding, 1 refs (da0:umass-sim1:1:0:0): removing device entry (pass5:umass-sim1:1:0:0): passdevgonecb: devfs entry is gone umass0: at uhub3, port 1, addr 2 (disconnected) At this point that particular USB port is effectively useless. Plugging anything into the ports shows no device showing up. Running usbconfig hangs with: PID TID COMM TDNAME KSTACK 48562 101874 usbconfig - mi_switch+0x186 sleepq_wait+0x42 _sx_xlock_hard+0x426 usbd_enum_lock+0xac usb_ref_device+0x21c usb_open+0xc7 devfs_open+0x197 vn_open_cred+0x2ff kern_openat+0x20a amd64_syscall+0x540 Xfast_syscall+0xf7 Controller is: uhci0@pci0:0:26:0: class=0x0c0300 card=0x02091028 chip=0x28348086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) USB UHCI Controller' class = serial bus subclass = USB uhci1@pci0:0:26:1: class=0x0c0300 card=0x02091028 chip=0x28358086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) USB UHCI Controller' class = serial bus subclass = USB ehci0@pci0:0:26:7: class=0x0c0320 card=0x02091028 chip=0x283a8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) USB2 EHCI Controller' class = serial bus subclass = USB It does however seem related to cam as looking at the various threads for the usb hub I find: (kgdb) bt #0 sched_switch (td=0xfffffe0002650000, newtd=0xfffffe000227f000, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1927 #1 0xffffffff808f34c6 in mi_switch (flags=260, newtd=0x0) at /usr/src/sys/kern/kern_synch.c:485 #2 0xffffffff8092bfd2 in sleepq_wait (wchan=0xfffffe001ec2a900, pri=92) at /usr/src/sys/kern/subr_sleepqueue.c:623 #3 0xffffffff808f3c69 in _sleep (ident=0xfffffe001ec2a900, lock=0xfffffe00371e9210, priority=Variable "priority" is not available. ) at /usr/src/sys/kern/kern_synch.c:250 #4 0xffffffff802bea02 in cam_sim_free (sim=0xfffffe001ec2a900, free_devq=1) at /usr/src/sys/cam/cam_sim.c:112 #5 0xffffffff8074f8ba in umass_detach (dev=Variable "dev" is not available. ) at /usr/src/sys/dev/usb/storage/umass.c:2183 #6 0xffffffff8091a054 in device_detach (dev=0xfffffe001ec2e900) at device_if.h:214 #7 0xffffffff8075c458 in usb_detach_device (udev=0xfffffe0007ce8800, iface_index=32 ' ', flag=Variable "flag" is not available. ) at /usr/src/sys/dev/usb/usb_device.c:1065 #8 0xffffffff8075c5f4 in usb_unconfigure (udev=0xfffffe0007ce8800, flag=Variable "flag" is not available. ) at /usr/src/sys/dev/usb/usb_device.c:455 #9 0xffffffff8075c88e in usb_free_device (udev=0xfffffe0007ce8800, flag=Variable "flag" is not available. ) at /usr/src/sys/dev/usb/usb_device.c:2093 #10 0xffffffff80764e5e in uhub_explore (udev=0xfffffe0007353800) at /usr/src/sys/dev/usb/usb_hub.c:358 #11 0xffffffff8074f536 in usb_bus_explore (pm=Variable "pm" is not available. ) at /usr/src/sys/dev/usb/controller/usb_controller.c:359 #12 0xffffffff80769173 in usb_process (arg=Variable "arg" is not available. ) at /usr/src/sys/dev/usb/usb_process.c:170 #13 0xffffffff808bc2df in fork_exit (callout=0xffffffff807690a0 , arg=0xffffff80007c0e88, frame=0xffffff804743cc40) at /usr/src/sys/kern/kern_fork.c:992 #14 0xffffffff80bc216e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:602 From: cam_sim_free(struct cam_sim *sim, int free_devq) (kgdb) l 107 { 108 int error; 109 110 sim->refcount--; 111 if (sim->refcount > 0) { 112 error = msleep(sim, sim->mtx, PRIBIO, "simfree", 0); 113 KASSERT(error == 0, ("invalid error value for msleep(9)")); 114 } 115 116 KASSERT(sim->refcount == 0, ("sim->refcount == 0")); It almost appears as if the cam layer is trying to finalise a write of some sort but the physical device has already gone. (kgdb) p sim->refcount $1 = 1 Not sure why refcount is still ==1. The same device in a box running 9.0-Stable (as of about 3 months ago) with a ICH9 controller works as expected. Any suggestions? Cheers, Benjamin From owner-freebsd-stable@FreeBSD.ORG Mon Sep 10 14:46:19 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4849A106564A for ; Mon, 10 Sep 2012 14:46:19 +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 027D98FC0C for ; Mon, 10 Sep 2012 14:46:18 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 444AB28423; Mon, 10 Sep 2012 16:46:17 +0200 (CEST) Received: from [192.168.1.2] (static-84-242-120-26.net.upcbroadband.cz [84.242.120.26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 8017128427; Mon, 10 Sep 2012 16:46:16 +0200 (CEST) Message-ID: <504DFD37.60105@quip.cz> Date: Mon, 10 Sep 2012 16:46:15 +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: Mikolaj Golub References: <504D10A7.1070701@quip.cz> <20120910054459.GA57302@gmail.com> In-Reply-To: <20120910054459.GA57302@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: bsnmpd always died on HDD detach X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 14:46:19 -0000 Mikolaj Golub wrote: > On Sun, Sep 09, 2012 at 11:56:55PM +0200, Miroslav Lachman wrote: >> I am running bsnmpd with basic snmpd.config (only community and location >> changed). >> >> When there is a problem with HDD and disk disapeared from ATA channel >> (eg.: disc physically removed) the bsnmpd always dumps core: >> >> kernel: pid 1188 (bsnmpd), uid 0: exited on signal 11 (core dumped) >> >> I see this for a long rime on all releases of 7.x and 8.x branches (i386 >> and amd64). I did not tested 9.x. >> >> Is it a known bug, or should I file PR? > > Do you happen to run bsnmp-ucd too? If you do then what version is it? > In bsnmp-ucd-0.3.5 I introduced a bug that lead to bsnmpd crash on a > disk detach. It has been fixed (thanks to Brian Somers) in 0.3.6. No, I never installed bsnmpd-ucd. We are using plain bsnmpd from base without any modules. It is used by MRTG only for network traffic. Nothing else. Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Mon Sep 10 20:35:17 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E6FB8106566B for ; Mon, 10 Sep 2012 20:35:17 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 720C98FC08 for ; Mon, 10 Sep 2012 20:35:17 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so1958432wgb.31 for ; Mon, 10 Sep 2012 13:35:16 -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=bgvclhEsPxruPrkknnTSqovtdy0KvW3WwSLnRf3SoRs=; b=p1v6g/5xDZZ3WA4suJnbiiEXpr9pMg82bn4kotZzv1oMxH8vKBg0G52sjuZzDCi8YE zjuwNXbn7LFNGxQkSHrbx86MyhBFnqSgw2Q4yrOdR/0dWJR7KteBeyxDzuAdO/xD8Dg+ 2ACWm5BcbAVzEBBjlZ8/Za5eCVbXUxzf/5n5JsNUFp8xmdtpaQ2BSzX4aWhZZ+Ad18H9 kekmvqshzIGOafgpM6Nk3zvzHVE76J6si9QmehzZ4AH5R+j4FJcxP8WD0VqfwYxnYXoz ped/VvR/HeUxLZDaJFIaer868jtlOJPMvqettz4Njst+8NHuTCJ7lul+Hcw/2uVgvISI Q/WA== Received: by 10.180.93.68 with SMTP id cs4mr19527278wib.14.1347309316056; Mon, 10 Sep 2012 13:35:16 -0700 (PDT) Received: from localhost ([95.69.174.83]) by mx.google.com with ESMTPS id j6sm212190wiy.4.2012.09.10.13.35.14 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 10 Sep 2012 13:35:15 -0700 (PDT) Sender: Mikolaj Golub Date: Mon, 10 Sep 2012 23:35:12 +0300 From: Mikolaj Golub To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20120910203511.GA27221@gmail.com> References: <504D10A7.1070701@quip.cz> <20120910054459.GA57302@gmail.com> <504DFD37.60105@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <504DFD37.60105@quip.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: bsnmpd always died on HDD detach X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 20:35:18 -0000 On Mon, Sep 10, 2012 at 04:46:15PM +0200, Miroslav Lachman wrote: > Mikolaj Golub wrote: > > On Sun, Sep 09, 2012 at 11:56:55PM +0200, Miroslav Lachman wrote: > >> I am running bsnmpd with basic snmpd.config (only community and location > >> changed). > >> > >> When there is a problem with HDD and disk disapeared from ATA channel > >> (eg.: disc physically removed) the bsnmpd always dumps core: > >> > >> kernel: pid 1188 (bsnmpd), uid 0: exited on signal 11 (core dumped) > >> > >> I see this for a long rime on all releases of 7.x and 8.x branches (i386 > >> and amd64). I did not tested 9.x. > >> > >> Is it a known bug, or should I file PR? > > > > Do you happen to run bsnmp-ucd too? If you do then what version is it? > > In bsnmp-ucd-0.3.5 I introduced a bug that lead to bsnmpd crash on a > > disk detach. It has been fixed (thanks to Brian Somers) in 0.3.6. > > No, I never installed bsnmpd-ucd. We are using plain bsnmpd from base > without any modules. > It is used by MRTG only for network traffic. Nothing else. Then the backtrace might be useful. gdb /usr/sbin/bsnmpd /path/to/bsnmpd.core bt -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 08:17:00 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A383F106566B for ; Tue, 11 Sep 2012 08:17:00 +0000 (UTC) (envelope-from prabhpal@digital-infotech.net) Received: from mail.digital-infotech.net (mail.digital-infotech.net [41.211.25.193]) by mx1.freebsd.org (Postfix) with ESMTP id 44ACC8FC0C for ; Tue, 11 Sep 2012 08:17:00 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.digital-infotech.net (Postfix) with ESMTP id 00D042E41B8 for ; Tue, 11 Sep 2012 08:15:55 +0000 (GMT) Received: from mail.digital-infotech.net ([127.0.0.1]) by localhost (mail.digital-infotech.net [127.0.0.1]) (maiad, port 10024) with ESMTP id 39851-10 for ; Tue, 11 Sep 2012 08:15:54 +0000 (GMT) Received: from Prabhpals-MacBook-Pro.local (Prabhpals-MacBook-Pro.local [41.211.27.79]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: prabhpal@digital-infotech.net) by mail.digital-infotech.net (Postfix) with ESMTPSA id DAE0D2E41B7 for ; Tue, 11 Sep 2012 08:15:54 +0000 (GMT) X-DKIM: OpenDKIM Filter v2.5.0 mail.digital-infotech.net DAE0D2E41B7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=digital-infotech.net; s=digital; t=1347351354; bh=6qnhjA5XaSuFpFafXsHINgfHuQMt2JjW3UCI81oRW2M=; h=Date:From:To:Subject; b=JPvJbAJNJKFmFZ9EYRnXCTPRnYWsaLOGoKEUijoDe8OGVM8SgqVXjY1kbX9to3rUE QySuvh9pvzqc374Vyxy99Ov7HDi+Uk6Jw+LjG112LGItYtLYvA24YdicNqGJB8pmcc ROdomQscoi38gssrgiHNydMVCDGP0FbwiCj7EJSE= Message-ID: <504EF33A.7080304@digital-infotech.net> Date: Tue, 11 Sep 2012 08:15:54 +0000 From: "Shiv. Nath" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: PF Configuration - FreeBSD Release 9.0 x64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 08:17:00 -0000 Dear FreeBSD Guys, It is FreeBSD Release 9.0 x64 and i see this log very frequent almost every second, And i want to block this IP from reaching my server. i configured the PF as following but still see the same logs, it is like it did not work. block in log quick from 41.211.2.239/32 to any Sep 11 07:49:56 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 4331 on interface 'em0.0' Sep 11 07:50:25 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 38627 on interface 'em0.0' Sep 11 07:51:29 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 38627 on interface 'em0.0' From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 08:26:59 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 846731065679 for ; Tue, 11 Sep 2012 08:26:59 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0A6948FC0A for ; Tue, 11 Sep 2012 08:26:58 +0000 (UTC) Received: by weyx56 with SMTP id x56so166204wey.13 for ; Tue, 11 Sep 2012 01:26:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to :x-gm-message-state; bh=EyP4kWgOtmI9cNPkwTgo45ThOzDIhbjM2zl6YBBRMhM=; b=kSeKjWnsa/QPiU0fIrEtOFM22tXQ8RQEfYvkC8VoNhQpA2vlnmAOIUNYGJyvxaX06k 9nBQySilNUCok7xBQV5km4TYTWcLZHnPvQJGj7k+5IDDvgQTf7s1M4G+lwCw13fBVXkS Xl0iyoyZT6GmcKknkZ76iTRhmd3wFkwDZbz2eVA4X9STbMq2vtylKN/3FPC8xDM0fxcC VJUNCQvX+XNxwWlz0yXApPrEI7PiT7loZvUn5h2ce8bEDF4ovttqjsFDPHd7NFcAQkB2 XO8qKEzygsKkToBtCASVnUVbJJ3716GLjMRetoHqu5FgsCFLhSZ3n21VtyvBBrQOhWXm 66kQ== Received: by 10.216.143.158 with SMTP id l30mr9750339wej.113.1347352016953; Tue, 11 Sep 2012 01:26:56 -0700 (PDT) Received: from [10.66.117.194] ([92.90.16.54]) by mx.google.com with ESMTPS id l5sm2315570wix.5.2012.09.11.01.26.55 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Sep 2012 01:26:55 -0700 (PDT) References: <504EF33A.7080304@digital-infotech.net> In-Reply-To: <504EF33A.7080304@digital-infotech.net> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: X-Mailer: iPhone Mail (9A405) From: Damien Fleuriot Date: Tue, 11 Sep 2012 10:26:42 +0200 To: "Shiv. Nath" X-Gm-Message-State: ALoCoQkbv4w5sttrAMQSkJKrXL/CLHkw5L8fhJ7R5yKtFZj5rLd4gLMu1jPZT6ktPh+WY8V48hHo Cc: "freebsd-stable@freebsd.org" Subject: Re: PF Configuration - FreeBSD Release 9.0 x64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 08:26:59 -0000 On 11 Sep 2012, at 10:15, "Shiv. Nath" wrote= : > Dear FreeBSD Guys, >=20 > It is FreeBSD Release 9.0 x64 and i see this log very frequent almost ever= y second, And i want to block this IP from reaching my server. i configured t= he PF as following but still see the same logs, it is like it did not work. >=20 > block in log quick from 41.211.2.239/32 to any >=20 >=20 > Sep 11 07:49:56 titan avahi-daemon[1567]: Received response from host 41.2= 11.2.239 with invalid source port 4331 on interface 'em0.0' > Sep 11 07:50:25 titan avahi-daemon[1567]: Received response from host 41.2= 11.2.239 with invalid source port 38627 on interface 'em0.0' > Sep 11 07:51:29 titan avahi-daemon[1567]: Received response from host 41.2= 11.2.239 with invalid source port 38627 on interface 'em0.0' > _______________________________________________ > 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" It says it received a *response* so my understanding is *you* are trying to c= onnect. Adjust your rule and see if it's any better.= From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 08:35:32 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD2821065673 for ; Tue, 11 Sep 2012 08:35:32 +0000 (UTC) (envelope-from christer.solskogen@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8C4498FC1E for ; Tue, 11 Sep 2012 08:35:32 +0000 (UTC) Received: by oagm1 with SMTP id m1so139261oag.13 for ; Tue, 11 Sep 2012 01:35:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=gyc9K6kl+JjbX5vpqQUl6Y6iM6vcxa2pucRkHVjQSfI=; b=kRjzocp3UVsiWiuxFwbSiF8FoLSZLc1N5Rp3X3MPovtLIOH47lfPJm7CVD6U2QqpnY WcrSEDNhLtOdN/m0Rhse7PVBvwQRSdubrpFHHbuX17zibInQB05BcrXpMq1KJ405R6im l2Zm6gn2PB6kSpmqGRTE1dpLrW09mKEuk6WXncrYsjRVi5xnL0I7FUmi4cGFvpUGRref 84j17VGeHcRvjhtBCK2IhrgQf84Qxs16bCfGx91R/+ZhgGwAB+J4lTezmq1g5RRuCTfG uC++RqPBI+dzItFUvXG3q8uIi2DH7c76LoJm8xzHmjTqjEKcVt9KUnbZzODXuhG5uFEQ EwnA== Received: by 10.182.75.9 with SMTP id y9mr17127475obv.86.1347352531698; Tue, 11 Sep 2012 01:35:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.32.141 with HTTP; Tue, 11 Sep 2012 01:35:11 -0700 (PDT) In-Reply-To: <504EF33A.7080304@digital-infotech.net> References: <504EF33A.7080304@digital-infotech.net> From: Christer Solskogen Date: Tue, 11 Sep 2012 10:35:11 +0200 Message-ID: To: "Shiv. Nath" Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org Subject: Re: PF Configuration - FreeBSD Release 9.0 x64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 08:35:32 -0000 On Tue, Sep 11, 2012 at 10:15 AM, Shiv. Nath wrote: > Dear FreeBSD Guys, > > It is FreeBSD Release 9.0 x64 and i see this log very frequent almost every > second, And i want to block this IP from reaching my server. i configured > the PF as following but still see the same logs, it is like it did not work. > > block in log quick from 41.211.2.239/32 to any > try block log quick ... instead. -- chs, From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 09:11:29 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 178521065672 for ; Tue, 11 Sep 2012 09:11:29 +0000 (UTC) (envelope-from prabhpal@digital-infotech.net) Received: from mail.digital-infotech.net (mail.digital-infotech.net [41.211.25.193]) by mx1.freebsd.org (Postfix) with ESMTP id AA3D98FC17 for ; Tue, 11 Sep 2012 09:11:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.digital-infotech.net (Postfix) with ESMTP id A8C732E41B8 for ; Tue, 11 Sep 2012 09:11:26 +0000 (GMT) Received: from mail.digital-infotech.net ([127.0.0.1]) by localhost (mail.digital-infotech.net [127.0.0.1]) (maiad, port 10024) with ESMTP id 50585-04 for ; Tue, 11 Sep 2012 09:11:26 +0000 (GMT) Received: from Prabhpals-MacBook-Pro.local (Prabhpals-MacBook-Pro.local [41.211.27.79]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: prabhpal@digital-infotech.net) by mail.digital-infotech.net (Postfix) with ESMTPSA id 8FD362E41B7 for ; Tue, 11 Sep 2012 09:11:26 +0000 (GMT) X-DKIM: OpenDKIM Filter v2.5.0 mail.digital-infotech.net 8FD362E41B7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=digital-infotech.net; s=digital; t=1347354686; bh=8wI6jOYT+5TAg1zc4x4YTnGV4wjfh6xk0mzOWJBbc00=; h=Date:From:To:Subject:References:In-Reply-To; b=aIuCxfvxva7ByUkMVys1DOFc2ZvjAR3Sb8qCfuTKPx0ZMlBy1/msU5hmsnsaW5ei6 DT2QG9MMq79RxXwSpKSnE2yOdSjX1vT99tytHVKHd8wnuYdV4smoYHCmexDQbGgtGd LdU8ly3OTZaFAELw+JOh88XnGvJyovd+RC2kPyvM= Message-ID: <504F003E.2000508@digital-infotech.net> Date: Tue, 11 Sep 2012 09:11:26 +0000 From: "Shiv. Nath" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <504EF33A.7080304@digital-infotech.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: PF Configuration - FreeBSD Release 9.0 x64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 09:11:29 -0000 Sep 11 07:49:56 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 4331 on interface 'em0.0' Sep 11 07:50:25 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 38627 on interface 'em0.0' Sep 11 07:51:29 titan avahi-daemon[1567]: Received response from host 41.211.2.239 with invalid source port 38627 on interface 'em0.0' _______________________________________________ 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" > > It says it received a *response* so my understanding is *you* are trying to connect. > > Adjust your rule and see if it's any better._______________________________________________ > 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" > Dear D. Fleuriot & Christer. S Thanks for your response and help, logically, you are correct (It says it received a *response* so my understanding is *you* are trying to connect) but frankly speaking, i don't know what is happening. i have 5,000 active public IP address configured in my network. The problematic IP belongs to one of my customer "41.211.2.239". i see the same log in many other server as well. i am bit confuse because how 10 servers from my data center has decided to send something to same particular IP whereas there are many thousand other ip available to send something. it is like that machine is sending broadcast and my servers receive it, but it confuse when reading logs. have you come across this kind of issue before? Thanks for your assistance, i will try to block using block log quick ... instead, or i will put this IP to VLAN to stop broadcasting. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 13:44:43 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 502ED1065674 for ; Tue, 11 Sep 2012 13:44:43 +0000 (UTC) (envelope-from niobos@dest-unreach.be) Received: from serv02.imset.org (hackerspace.be [IPv6:2001:41d0:2:1959:fedc:ba98:7654:3210]) by mx1.freebsd.org (Postfix) with ESMTP id E4C4D8FC0C for ; Tue, 11 Sep 2012 13:44:42 +0000 (UTC) Received: from raptor.rto.be (225.72-136-217.adsl-dyn.isp.belgacom.be [217.136.72.225]) by serv02.imset.org (Postfix) with ESMTPSA id 287DECA049 for ; Tue, 11 Sep 2012 15:44:42 +0200 (CEST) Message-ID: <504F4049.9080801@dest-unreach.be> Date: Tue, 11 Sep 2012 15:44:41 +0200 From: Niobos User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Kernel panic with geom_multipath + ZFS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 13:44:43 -0000 Hi, I'm under the illusion that I've found a bug in the FreeBSD kernel, but since I'm new to FreeBSD, a quiet voice tells me it's probably a case of "you're doing it wrong". Also, I'm not sure if this is the right place to complain. So feel free to redirect me. I'll start with some context: * FreeBSD storage.[...] 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 * There are 5 expansion units attached via SAS, daisy-chained. Each unit has 12 disks, totalling at 60 disks. To provide path redundancy, the units are connected HBA-1-2-3-4-5 and HBA-5-4-3-2-1. * I've configured a ZFS on top, with 6 RAID-Z2 arrays of 8+2 disks each. This setup should be able to survive a disk failure. However, manually ejecting one of the disks causes a kernel panic. I've manually OCR'd it below. The panic is not triggered by the ejection itself. I can see that fact in the kernel log a few seconds after the ejection. I think the panic is triggered by access to the (now ejected) disk. > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff807ced68 > stack pointer = 0x28:0xffffff80002ecb70 > frame pointer = 0x28:0xffffff80002ecbc0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 13 (g_down) > trap number = 12 > panic: page fault > cpuid = 0 > KDB: stack backtrace: > #0 0xffffffff808680fe at kdb_backtrace+0x5e > #1 0xffffffff80832cb7 at panic+0x184 > #2 0xffffffff80b18400 at trap_fatal+0x290 > #3 0xffffffff80b18749 at trap_pfault+0x1f9 > #4 0xffffffff80b18c0f at trap+0x3df > #5 0xffffffff80b0313f at calltrap+0x8 > #6 0xffffffff80g3f874 at g_io_schedule_down+0x1d4 > #7 0xffffffff807cfb7c at g_down_procbody+0x5c > #8 0xffffffff8080682f at fork_exit+0x11f > #9 0xffffffff80b0366e at fork_trampoline+0xe > Uptime: 7m16s > Automatic reboot in 15 seconds - press a key on the console to abort So the question is either "what am I doing wrong?" or "can anyone confirm this is a bug?" thanks in advance, Niels PS: I'm trying to post via email and read via nntp://gmane, I'm not sure how well this works. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 15:05:43 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9E7D106564A for ; Tue, 11 Sep 2012 15:05:43 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 71CB18FC0C for ; Tue, 11 Sep 2012 15:05:43 +0000 (UTC) Received: by qcsg15 with SMTP id g15so441339qcs.13 for ; Tue, 11 Sep 2012 08:05:42 -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=pd8aUbdkCtQ6e0gy1zLfxNSfkWcYzIyRjrf3xi7HYBM=; b=hYxemZ2hih22xpKmyqdrLk/jpFhTqX1k/QSp0vgBpzghkB3aYX+1BPXAhubLlwccVv ytBr6POLD/eYTK/FVGktJgSj0fhzFCVlON8g3qUiGxFfe1wMIk9TSAgBwD4oax/jCXN3 iWR//n7ChKapGny3pFAog4q1sSGa7CA1VAliyLfezto3V2KxjE+TdkMbV21ovess0Vjt 3z35ExLgBowkJkCmcT9niLjtE2WaVCBgh0ISUpBb1KCO33YuroPZaZGtxqchpJHFftul W3zwT8PYY//v0IYZsh3ixOo6LPSWoX3jl0totSuMKiC4OZ+aeFwtvcRDy906MwTOt0u0 IZeg== MIME-Version: 1.0 Received: by 10.224.176.132 with SMTP id be4mr10313696qab.45.1347375942698; Tue, 11 Sep 2012 08:05:42 -0700 (PDT) Received: by 10.49.95.230 with HTTP; Tue, 11 Sep 2012 08:05:42 -0700 (PDT) In-Reply-To: References: <504EF33A.7080304@digital-infotech.net> Date: Tue, 11 Sep 2012 11:05:42 -0400 Message-ID: From: Brandon Allbery To: Damien Fleuriot Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "Shiv. Nath" , "freebsd-stable@freebsd.org" Subject: Re: PF Configuration - FreeBSD Release 9.0 x64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 15:05:43 -0000 On Tue, Sep 11, 2012 at 4:26 AM, Damien Fleuriot wrote: > On 11 Sep 2012, at 10:15, "Shiv. Nath" > wrote: > > It is FreeBSD Release 9.0 x64 and i see this log very frequent almost > every second, And i want to block this IP from reaching my server. i > configured the PF as following but still see the same logs, it is like it > did not work. > > > > Sep 11 07:49:56 titan avahi-daemon[1567]: Received response from host > 41.211.2.239 with invalid source port 4331 on interface 'em0.0' > > It says it received a *response* so my understanding is *you* are trying > to connect. > But it's avahi (a zeroconf implementation) so the response is to a broadcast; the remote machine in question may also be broadcasting. I would actually question why avahi is even enabled on a server; perhaps the correct answer is simply to disable it in rc.conf. -- brandon s allbery allbery.b@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 15:12:58 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EC4C5106568A for ; Tue, 11 Sep 2012 15:12:58 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8EE968FC14 for ; Tue, 11 Sep 2012 15:12:58 +0000 (UTC) Received: by vcbfw7 with SMTP id fw7so1002371vcb.13 for ; Tue, 11 Sep 2012 08:12:57 -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=TC9X1QRJw5s6OkJO70x5LQwNpNrI2tn45QQjnRAld+o=; b=k5oq6AhBbBlD+LqC+MjC/gNFWM0GIQxfvTtzxgGLNKfr6depxxYUfKuAiVkaQb5THg dnWOfZjlFkKSMRp2FuKMBFcdwKvFVk+JCGLqO1MHVlp4dpnkvohM2v7Cu4PcVmNDi1ZI 1yA2k4urtyUhpBkY/6+J29lhOT/c2jQ+ZwZGlgNp0SzcJWWaHvRbUNPfPmUL4w6d8dQv 0UazfNJDpE7ZEDnEf/kjAMK8BGzJSgWNXRw6vjyT1mk3bsYyvh0ujN+n5R5KRYTu7XPH cp6sRlBI0z0Sl1aThZwPpTPwzi0mUNT8z5dstIFdO0Vw4tMszFdIc3PuuXN8uR1Qz+Ro c/aw== MIME-Version: 1.0 Received: by 10.58.13.33 with SMTP id e1mr27665461vec.51.1347376376841; Tue, 11 Sep 2012 08:12:56 -0700 (PDT) Received: by 10.58.230.134 with HTTP; Tue, 11 Sep 2012 08:12:56 -0700 (PDT) In-Reply-To: References: <504EF33A.7080304@digital-infotech.net> Date: Tue, 11 Sep 2012 18:12:56 +0300 Message-ID: From: Kimmo Paasiala To: Brandon Allbery Content-Type: text/plain; charset=UTF-8 Cc: "Shiv. Nath" , "freebsd-stable@freebsd.org" Subject: Re: PF Configuration - FreeBSD Release 9.0 x64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 15:12:59 -0000 On Tue, Sep 11, 2012 at 6:05 PM, Brandon Allbery wrote: > On Tue, Sep 11, 2012 at 4:26 AM, Damien Fleuriot wrote: > >> On 11 Sep 2012, at 10:15, "Shiv. Nath" >> wrote: >> > It is FreeBSD Release 9.0 x64 and i see this log very frequent almost >> every second, And i want to block this IP from reaching my server. i >> configured the PF as following but still see the same logs, it is like it >> did not work. >> > >> > Sep 11 07:49:56 titan avahi-daemon[1567]: Received response from host >> 41.211.2.239 with invalid source port 4331 on interface 'em0.0' >> >> It says it received a *response* so my understanding is *you* are trying >> to connect. >> > > But it's avahi (a zeroconf implementation) so the response is to a > broadcast; the remote machine in question may also be broadcasting. > > I would actually question why avahi is even enabled on a server; perhaps > the correct answer is simply to disable it in rc.conf. > You do know that avahi-daemon's main use is to advertise _services_ running on a host? From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 15:18:05 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77D3D1065715 for ; Tue, 11 Sep 2012 15:18:04 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id A9D9A8FC17 for ; Tue, 11 Sep 2012 15:18:03 +0000 (UTC) Received: by qatn12 with SMTP id n12so426920qat.13 for ; Tue, 11 Sep 2012 08:17:57 -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=EzKAtGJ75VzmMq2enLQ8eOLYnZINBAgS2Dkqe0oY9cg=; b=eCQFz4FX2H1L0QkRMhTfR1YzjBgKDCsUp2J7FOCs1Lt6RIUi/m/UqZOaVZSnp/t1A2 U7v45yX/ciuZhzA9615Yg4yVJRxKg+91ZCvXQbeLgWfnl3ZbkBufx8Ov3Sp0EHBVx6oz /kpggQhd28yI6iwvitl/qWp5ZBOGPMZlCK7O2MKGmwJTg22LmonIDbdD5xIWlb7zAymo 3EmEUVjGeUl8sO6DtKGhnn6yn/hChmSzlh3pxVgzKsU7GAkuPDlIBZVKObLszHDjVgL0 X6cpOUL2kHOdzcBOJ5pqu4JymFOLBX5oLFLgtgvhWX+0dnP244M9Yc3KvuK0EwLCdIvk Nhrw== MIME-Version: 1.0 Received: by 10.229.136.145 with SMTP id r17mr4783878qct.43.1347376677484; Tue, 11 Sep 2012 08:17:57 -0700 (PDT) Received: by 10.49.95.230 with HTTP; Tue, 11 Sep 2012 08:17:57 -0700 (PDT) In-Reply-To: References: <504EF33A.7080304@digital-infotech.net> Date: Tue, 11 Sep 2012 11:17:57 -0400 Message-ID: From: Brandon Allbery To: Kimmo Paasiala Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "Shiv. Nath" , "freebsd-stable@freebsd.org" Subject: Re: PF Configuration - FreeBSD Release 9.0 x64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 15:18:05 -0000 On Tue, Sep 11, 2012 at 11:12 AM, Kimmo Paasiala wrote: > On Tue, Sep 11, 2012 at 6:05 PM, Brandon Allbery > wrote: > > On Tue, Sep 11, 2012 at 4:26 AM, Damien Fleuriot wrote: > >> On 11 Sep 2012, at 10:15, "Shiv. Nath" > >> wrote: > >> It says it received a *response* so my understanding is *you* are trying > >> to connect. > > > > But it's avahi (a zeroconf implementation) so the response is to a > > broadcast; the remote machine in question may also be broadcasting. > > > > I would actually question why avahi is even enabled on a server; perhaps > > the correct answer is simply to disable it in rc.conf. > > You do know that avahi-daemon's main use is to advertise _services_ > running on a host? > Yes, but zeroconf-style services are often more of a peer-to-peer nature instead of fixed (which don't *need* zeroconf). It's also a larger attack surface. -- brandon s allbery allbery.b@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 15:57:11 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E286106566B for ; Tue, 11 Sep 2012 15:57:11 +0000 (UTC) (envelope-from prabhpal@digital-infotech.net) Received: from mail.digital-infotech.net (mail.digital-infotech.net [41.211.25.193]) by mx1.freebsd.org (Postfix) with ESMTP id 082478FC17 for ; Tue, 11 Sep 2012 15:57:10 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.digital-infotech.net (Postfix) with ESMTP id 2DF052E41B8 for ; Tue, 11 Sep 2012 15:57:07 +0000 (GMT) Received: from mail.digital-infotech.net ([127.0.0.1]) by localhost (mail.digital-infotech.net [127.0.0.1]) (maiad, port 10024) with ESMTP id 55541-03 for ; Tue, 11 Sep 2012 15:57:07 +0000 (GMT) Received: from Prabhpals-MacBook-Pro.local (Prabhpals-MacBook-Pro.local [41.211.27.79]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: prabhpal@digital-infotech.net) by mail.digital-infotech.net (Postfix) with ESMTPSA id 1A0082E41B7 for ; Tue, 11 Sep 2012 15:57:07 +0000 (GMT) X-DKIM: OpenDKIM Filter v2.5.0 mail.digital-infotech.net 1A0082E41B7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=digital-infotech.net; s=digital; t=1347379027; bh=T3ASo42mZIK9EpFs8vCJ+TVe4qXVWiKwVtjY+VM6JdE=; h=Date:From:To:Subject:References:In-Reply-To; b=mQZzmgC1VfEVfYYKOlhmHH8IU455yDVp+e1rqxIa2ilxrTIEu4cjDjoyWlcOTV1r1 OlWFaBA5MPOFIy6ynZy1dEzSexSYV1BIpheqhs64YjrSUUXXxAcVyDk9+9m0ElliZZ xK0/FzFFiNknT0K5XZOP7Cglgugo1ly/Qd/+E7Ys= Message-ID: <504F5F52.2030306@digital-infotech.net> Date: Tue, 11 Sep 2012 15:57:06 +0000 From: "Shiv. Nath" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <504EF33A.7080304@digital-infotech.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: PF Configuration - FreeBSD Release 9.0 x64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 15:57:11 -0000 I would actually question why avahi is even enabled on a server; perhaps the correct answer is simply to disable it in rc.conf. >> You do know that avahi-daemon's main use is to advertise _services_running on a host? >> > Yes, but zeroconf-style services are often more of a peer-to-peer nature > instead of fixed (which don't *need* zeroconf). It's also a larger attack > surface. > Dear Brandon A & Kimmo P. Thanks for the kind assistance and advices, in my case disabling "avahi" would not effect me much because it is only a mail server. thanks once again. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 20:17:08 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 098741065674; Tue, 11 Sep 2012 20:17:08 +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 839A28FC08; Tue, 11 Sep 2012 20:17:06 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 0914028423; Tue, 11 Sep 2012 22:17:00 +0200 (CEST) Received: from [192.168.1.2] (static-84-242-120-26.net.upcbroadband.cz [84.242.120.26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id C912328427; Tue, 11 Sep 2012 22:16:58 +0200 (CEST) Message-ID: <504F9C39.2070107@quip.cz> Date: Tue, 11 Sep 2012 22:16:57 +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: Mikolaj Golub References: <504D10A7.1070701@quip.cz> <20120910054459.GA57302@gmail.com> <504DFD37.60105@quip.cz> <20120910203511.GA27221@gmail.com> In-Reply-To: <20120910203511.GA27221@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: bsnmpd always died on HDD detach X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 20:17:08 -0000 Mikolaj Golub wrote: > On Mon, Sep 10, 2012 at 04:46:15PM +0200, Miroslav Lachman wrote: >> Mikolaj Golub wrote: >>> On Sun, Sep 09, 2012 at 11:56:55PM +0200, Miroslav Lachman wrote: >>>> I am running bsnmpd with basic snmpd.config (only community and location >>>> changed). >>>> >>>> When there is a problem with HDD and disk disapeared from ATA channel >>>> (eg.: disc physically removed) the bsnmpd always dumps core: >>>> >>>> kernel: pid 1188 (bsnmpd), uid 0: exited on signal 11 (core dumped) >>>> >>>> I see this for a long rime on all releases of 7.x and 8.x branches (i386 >>>> and amd64). I did not tested 9.x. >>>> >>>> Is it a known bug, or should I file PR? >>> >>> Do you happen to run bsnmp-ucd too? If you do then what version is it? >>> In bsnmp-ucd-0.3.5 I introduced a bug that lead to bsnmpd crash on a >>> disk detach. It has been fixed (thanks to Brian Somers) in 0.3.6. >> >> No, I never installed bsnmpd-ucd. We are using plain bsnmpd from base >> without any modules. >> It is used by MRTG only for network traffic. Nothing else. > > Then the backtrace might be useful. > > gdb /usr/sbin/bsnmpd /path/to/bsnmpd.core > bt # gdb /usr/sbin/bsnmpd /bsnmpd.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... Core was generated by `bsnmpd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libbegemot.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libbegemot.so.4 Reading symbols from /lib/libbsnmp.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libbsnmp.so.5 Reading symbols from /usr/lib/libwrap.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libwrap.so.6 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/lib/snmp_mibII.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/snmp_mibII.so Reading symbols from /usr/lib/snmp_pf.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/snmp_pf.so Reading symbols from /usr/lib/snmp_hostres.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/snmp_hostres.so Reading symbols from /lib/libkvm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libkvm.so.5 Reading symbols from /usr/lib/libdevinfo.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libdevinfo.so.5 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libgeom.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libgeom.so.5 Reading symbols from /usr/lib/libmemstat.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libmemstat.so.3 Reading symbols from /lib/libbsdxml.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libbsdxml.so.4 Reading symbols from /lib/libsbuf.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libsbuf.so.5 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x0000000801046cba in refresh_disk_storage_tbl () from /usr/lib/snmp_hostres.so (gdb) bt #0 0x0000000801046cba in refresh_disk_storage_tbl () from /usr/lib/snmp_hostres.so #1 0x00000008010478bd in refresh_device_tbl () from /usr/lib/snmp_hostres.so #2 0x0000000801047be6 in start_device_tbl () from /usr/lib/snmp_hostres.so #3 0x000000080065fad5 in poll_dispatch () from /lib/libbegemot.so.4 #4 0x000000000040616a in main () Is it all you need? (I don't know how to use gdb) It is on FreeBSD 8.3-RELEASE #0: Mon Apr 9 21:23:18 UTC 2012 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 21:11:06 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12AF21065670; Tue, 11 Sep 2012 21:11:06 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mx1.giulioferro.ch (mx1.giulioferro.ch [217.150.252.208]) by mx1.freebsd.org (Postfix) with ESMTP id 7AE8D8FC17; Tue, 11 Sep 2012 21:11:05 +0000 (UTC) Received: from mailscan.giulioferro.ch (unknown [192.168.115.2]) by mx1.giulioferro.ch (Postfix) with ESMTP id 794D0761BF; Tue, 11 Sep 2012 23:03:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at example.com Received: from mx1.giulioferro.ch ([192.168.114.4]) by mailscan.giulioferro.ch (mailscan.giulioferro.ch [192.168.115.2]) (amavisd-new, port 10024) with ESMTP id l83ILkMaGR0A; Tue, 11 Sep 2012 23:03:55 +0200 (CEST) Received: from mail.zirakzigil.org (net-93-70-48-129.cust.dsl.vodafone.it [93.70.48.129]) by mx1.giulioferro.ch (Postfix) with ESMTP id 00ED3761B1; Tue, 11 Sep 2012 23:03:54 +0200 (CEST) Received: from ext.zirakzigil.org (unknown [192.168.1.2]) by mail.zirakzigil.org (Postfix) with ESMTP id 3E98319C5A2; Tue, 11 Sep 2012 11:18:12 +0200 (CEST) X-Virus-Scanned: amavisd-new at zirakzigil.org Received: from mail.zirakzigil.org ([192.168.1.2]) by ext.zirakzigil.org (ext.zirakzigil.org [192.168.1.2]) (amavisd-new, port 10024) with ESMTP id 3i2Ys1yXIIKc; Tue, 11 Sep 2012 11:18:10 +0200 (CEST) Received: from [192.168.231.11] (ext [192.168.1.2]) (Authenticated sender: auryn@zirakzigil.org) by mail.zirakzigil.org (Postfix) with ESMTPA id 1AF0519C59E; Tue, 11 Sep 2012 11:18:07 +0200 (CEST) Message-ID: <504FA735.709@zirakzigil.org> Date: Tue, 11 Sep 2012 23:03:49 +0200 From: Giulio Ferro User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 21:11:06 -0000 Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --------------------------------------------------- ifconfig_igb0="inet ..." ifconfig_igb1="up" ifconfig_igb2="up" ifconfig_igb3="up" cloned_interfaces="lagg0" ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24" sshd_enable="YES" --------------------------------------------------- This doesn't even manage to start sshd, it just hangs there at boot. Disabling lagg configuration everything works correctly. This installation is a zfs root, but I don't think this has anything to do with this. Yes, I think that the maintainer of igb and/or lagg driver should absolutely look into this... On 09/07/2012 12:01 PM, Simon Dick wrote: > We've had similar problems with lagg at work, each lagg is made up of > one igb and one em port, sometimes for no apparent reason they seem to > stop passing through traffic. The easiest way we've found to get it > working again is ifconfig down and up on one of the physical > interfaces. This is on 8.1 > > On 3 September 2012 19:25, Giulio Ferro wrote: >> No idea anybody why this bug happens? Patches? >> >> >> >> On 08/29/2012 10:22 PM, Giulio Ferro wrote: >>> >>> On 08/28/2012 11:12 AM, Damien Fleuriot wrote: >>>> >>>> Hi Giulio, >>>> >>>> >>>> >>>> Just to clear things up: >>>> igb0: 192.168.9.60/24 >>>> lagg0: 192.168.12.21/24 >>>> >>> >>> Yes. >>> Actually I notice now that the lagg0 address is different from what >>> I wrote below in my rc.conf (192.168.12.7). I've just made many test >>> with different configuration, but no matter, it just doesn't work... >>> >>> >>>> >>>> What's the IP of the host you're trying ssh connections from ? >>> >>> >>> I'm just trying to connect to and from management interface igb0 >>> (192.168.9.60). >>> From external pc I do : ssh myuser@192.168.9.60 >>> From that server I do : ssh myuser@pcaddress >>> >>> Just to be more precise, the consequences are: >>> 1) daemon sshd on the server gets stuck and becomes unkillable >>> 2) the first connection may work, but then the program ssh on the >>> server becomes unresponsive and unkillable >>> >>> If I don't create a lagg0 interface and just connect (say) igb1 to >>> the data switch, I've no problem and everything works. >>> >>> Just to answer others' question, I connect igb1, igb2 and igb3 to the >>> same data switch in ports configured for aggregation. >>> I connect igb0 to another management switch (of course not configured >>> for aggregation) >>> >>> >>>> >>>> Also, just in case, did you enable any firewall ? (PF, ipfw) >>> >>> >>> As I already said, no. Nothing is working/active on this server, just >>> sshd. >>> >>> Thank you. >>> >>> >>>> >>>> >>>> >>>> On 27 August 2012 21:22, Giulio Ferro wrote: >>>>> >>>>> Hi, thanks for the answer >>>>> >>>>> Here is what you asked for: >>>>> >>>>> # ifconfig igb0 >>>>> igb0: flags=8843 metric 0 mtu >>>>> 1500 >>>>> >>>>> >>>>> options=4401bb >>>>> >>>>> ether ... >>>>> inet 192.168.9.60 netmask 0xffffff00 broadcast 192.168.9.255 >>>>> inet6 .... prefixlen 64 scopeid 0x1 >>>>> nd6 options=29 >>>>> media: Ethernet autoselect (1000baseT ) >>>>> status: active >>>>> >>>>> >>>>> >>>>> # netstat -rn >>>>> Routing tables >>>>> >>>>> Internet: >>>>> Destination Gateway Flags Refs Use Netif >>>>> Expire >>>>> default 192.168.9.1 UGS 0 0 igb0 >>>>> 127.0.0.1 link#12 UH 0 0 lo0 >>>>> 192.168.9.0/24 link#1 U 0 14 igb0 >>>>> 192.168.9.60 link#1 UHS 0 0 lo0 >>>>> 192.168.12.0/24 link#13 U 0 109 lagg0 >>>>> 192.168.12.21 link#13 UHS 0 0 lo0 >>>>> >>>>> Internet6: >>>>> Destination Gateway Flags >>>>> Netif Expire >>>>> ::/96 ::1 >>>>> UGRS lo0 >>>>> ::1 link#12 >>>>> UH lo0 >>>>> ::ffff:0.0.0.0/96 ::1 >>>>> UGRS lo0 >>>>> fe80::/10 ::1 >>>>> UGRS lo0 >>>>> fe80::%igb0/64 link#1 U >>>>> igb0 >>>>> fe80::ea39:35ff:feb6:a0d4%igb0 link#1 >>>>> UHS lo0 >>>>> fe80::%igb1/64 link#2 U >>>>> igb1 >>>>> fe80::ea39:35ff:feb6:a0d5%igb1 link#2 >>>>> UHS lo0 >>>>> fe80::%igb2/64 link#3 U >>>>> igb2 >>>>> fe80::ea39:35ff:feb6:a0d6%igb2 link#3 >>>>> UHS lo0 >>>>> fe80::%igb3/64 link#4 U >>>>> igb3 >>>>> fe80::ea39:35ff:feb6:a0d7%igb3 link#4 >>>>> UHS lo0 >>>>> fe80::%lo0/64 link#12 U >>>>> lo0 >>>>> fe80::1%lo0 link#12 >>>>> UHS lo0 >>>>> fe80::%lagg0/64 link#13 U >>>>> lagg0 >>>>> fe80::ea39:35ff:feb6:a0d5%lagg0 link#13 >>>>> UHS lo0 >>>>> ff01::%igb0/32 fe80::ea39:35ff:feb6:a0d4%igb0 >>>>> U igb0 >>>>> ff01::%igb1/32 fe80::ea39:35ff:feb6:a0d5%igb1 >>>>> U igb1 >>>>> ff01::%igb2/32 fe80::ea39:35ff:feb6:a0d6%igb2 >>>>> U igb2 >>>>> ff01::%igb3/32 fe80::ea39:35ff:feb6:a0d7%igb3 >>>>> U igb3 >>>>> ff01::%lo0/32 ::1 U >>>>> lo0 >>>>> ff01::%lagg0/32 fe80::ea39:35ff:feb6:a0d5%lagg0 U >>>>> lagg0 >>>>> ff02::/16 ::1 >>>>> UGRS lo0 >>>>> ff02::%igb0/32 fe80::ea39:35ff:feb6:a0d4%igb0 >>>>> U igb0 >>>>> ff02::%igb1/32 fe80::ea39:35ff:feb6:a0d5%igb1 >>>>> U igb1 >>>>> ff02::%igb2/32 fe80::ea39:35ff:feb6:a0d6%igb2 >>>>> U igb2 >>>>> ff02::%igb3/32 fe80::ea39:35ff:feb6:a0d7%igb3 >>>>> U igb3 >>>>> ff02::%lo0/32 ::1 U >>>>> lo0 >>>>> ff02::%lagg0/32 fe80::ea39:35ff:feb6:a0d5%lagg0 U >>>>> lagg0 >>>>> >>>>> >>>>> >>>>> # netstat -aln | grep 22 >>>>> tcp4 0 0 *.22 *.* LISTEN >>>>> tcp6 0 0 *.22 *.* LISTEN >>>>> >>>>> Note that I already tried to only listen on igb0 interface >>>>> (192.168.9.60) in >>>>> sshd_config, but the results are exactly >>>>> the same described below. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On 08/25/2012 01:22 PM, Damien Fleuriot wrote: >>>>>> >>>>>> >>>>>> In the meantime kindly post: >>>>>> >>>>>> >>>>>> Ifconfig for your igb0 >>>>>> Netstat -rn >>>>>> Netstat -aln | grep 22 >>>>>> >>>>>> >>>>>> >>>>>> On 25 Aug 2012, at 13:18, Damien Fleuriot wrote: >>>>>> >>>>>>> I'll get back to you regarding link aggregation when I'm done with >>>>>>> groceries. >>>>>>> >>>>>>> We use it here in production and it works flawlessly. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 25 Aug 2012, at 09:54, Giulio Ferro wrote: >>>>>>> >>>>>>>> No answer, so it seems that link aggregation doesn't really work in >>>>>>>> freebsd, >>>>>>>> this may help others with the same problem... >>>>>>>> >>>>>>>> I reverted back to one link for management and one for service, >>>>>>>> and ssh >>>>>>>> works as it should... >>>>>>>> >>>>>>>> >>>>>>>> On 08/21/2012 11:18 PM, Giulio Ferro wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> Scenario : freebsd 9 stable (yesterday) amd64 on HP server with 4 >>>>>>>>> nic >>>>>>>>> (igb) >>>>>>>>> >>>>>>>>> 1 nic is connected standalone to the management switch, the 3 other >>>>>>>>> nics >>>>>>>>> are connected to a switch configured for aggregation. >>>>>>>>> >>>>>>>>> If I configure the first nic (igb0) there is no problem, I can >>>>>>>>> operate >>>>>>>>> as I normally do and sshd functions normally. >>>>>>>>> >>>>>>>>> The problems start when I configure the 3 other nics for >>>>>>>>> aggregation: >>>>>>>>> >>>>>>>>> in /etc/rc.conf >>>>>>>>> ... >>>>>>>>> ifconfig_igb1="up" >>>>>>>>> ifconfig_igb2="up" >>>>>>>>> ifconfig_igb3="up" >>>>>>>>> >>>>>>>>> cloned_interfaces=lagg0 >>>>>>>>> ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport >>>>>>>>> igb3 192.168.12.7/24" >>>>>>>>> ... >>>>>>>>> >>>>>>>>> I restart the server and the aggregation seems to work correctly, in >>>>>>>>> fact ifconfig returns the correct lagg0 interface with the >>>>>>>>> aggregated >>>>>>>>> links, the correct protocol (lacp) and the correct ip address and >>>>>>>>> the >>>>>>>>> status is active. I can ping other IPs on the aggregated link. >>>>>>>>> >>>>>>>>> Also the other (standalone) link seems to work correctly. I can ping >>>>>>>>> that address from other machines, and I can ping other IPs from that >>>>>>>>> server. >>>>>>>>> >>>>>>>>> DNS lookups work ok too I can also use telnet to connect to pop3 >>>>>>>>> servers so there seems to be no problem on the network stack. >>>>>>>>> >>>>>>>>> But if I try to connect to the sshd service on that server, it hangs >>>>>>>>> indefinitely. On the server I find two sshd processes: >>>>>>>>> /usr/sbin/sshd >>>>>>>>> /usr/sbin/sshd -R >>>>>>>>> >>>>>>>>> There is no message in the logs. >>>>>>>>> >>>>>>>>> If I try to kill sshd (/etc/rc.d/sshd stop) I can't. it just stays >>>>>>>>> there >>>>>>>>> forever waiting for the pid to die (it never does) >>>>>>>>> >>>>>>>>> Even ssh client doesn't seem to work. In fact, if I try to >>>>>>>>> connect to >>>>>>>>> another server, the ssh client may start to work correctly, then >>>>>>>>> soon >>>>>>>>> or later it just hangs there forever, and I can't kill it with >>>>>>>>> ctrl-c. >>>>>>>>> >>>>>>>>> No firewall is configured, there is nothing else working on this >>>>>>>>> server. >>>>>>>>> >>>>>>>>> Thanks for any suggestions... >>>>>>>>> _______________________________________________ >>>>>>>>> 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" >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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" >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> freebsd-net@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>>>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >>> >>> >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> >> >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 21:35:06 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F9D31065687; Tue, 11 Sep 2012 21:35:04 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7492B8FC14; Tue, 11 Sep 2012 21:35:02 +0000 (UTC) Received: by lage12 with SMTP id e12so800495lag.13 for ; Tue, 11 Sep 2012 14:34:56 -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=SVzeH5cmM2D0ZPhsfhkp7Gv5uAsZy841C3JfYr/6dQw=; b=E/58jLEHRy+gw0fww1QzO5TjVAZwa8STbHtxuyP6wa4fwSKMQngG0dUYT8SWLiHXSz Ow899UsQCZZ3HE8PoJWmFEZaiW0HFSYJNTJrf6Y3DHc3Asc8fMrBY70w6/n8F/7H5fEC 5GsGdFYAly13n2NuNhoXWzZFVwCriz2+3RaZb3D5x1p64RsNFR09H3nkB71YNwcTv61V 8ebe7MglymIjeOtWoXWGpUhNZbnYBfjV8tVDu8DGQrOAeLo3Frn3pg6aLeRnnniE/B1L s+c63pt2Xd8vVXJR+GMqYuCcBKNE0MZjNbI2ExNJMSIlRGQ4g6nuAW0iit8frX/5mTf1 cq9g== MIME-Version: 1.0 Received: by 10.152.103.11 with SMTP id fs11mr16903975lab.23.1347399296233; Tue, 11 Sep 2012 14:34:56 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Tue, 11 Sep 2012 14:34:56 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Tue, 11 Sep 2012 14:34:56 -0700 (PDT) In-Reply-To: <504FA735.709@zirakzigil.org> References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> Date: Tue, 11 Sep 2012 14:34:56 -0700 Message-ID: From: Freddie Cash To: Giulio Ferro Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 21:35:06 -0000 On Sep 11, 2012 2:12 PM, "Giulio Ferro" wrote: > > Well, there definitely seems to be a problem with igb and lagg. > > igb alone works as it should, but doesn't seem to work properly in lagg. > > To be sure I started from scratch from a 9.0 release with nothing but: > > /etc/rc.conf > --------------------------------------------------- > ifconfig_igb0="inet ..." > > ifconfig_igb1="up" > ifconfig_igb2="up" > ifconfig_igb3="up" > > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24" > > sshd_enable="YES" > --------------------------------------------------- > > This doesn't even manage to start sshd, it just hangs there at boot. > > Disabling lagg configuration everything works correctly. > Just curious: does it work if you split the lagg configuration from the IP config: ifconfig_lagg0="laggproto ..." ifconfig_lagg0_alias0="inet 192..." I've had problems in the past with cloned interfaces not working right if you do everything in one ifconfig line. Never spent much time debugging it, though, as the split config always worked. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 21:55:12 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 458D7106566B for ; Tue, 11 Sep 2012 21:55:12 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id F19C38FC0A for ; Tue, 11 Sep 2012 21:55:11 +0000 (UTC) Received: by obbun3 with SMTP id un3so2004789obb.13 for ; Tue, 11 Sep 2012 14:55:11 -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=SGlnlBOzUJuRjaCfdN3hQh7Nicn510a6Gr5hjhvxdmg=; b=q1u9MoW4BFND3RJpfg1nuph0saqqzMhjVNCyQa1Uo9Vxl/bibGFEPnL2USTpLZOe3k rnHfskDUQAQ87OYAVHGi/WpOsHK9icn6mgAAvti1tyOT2mq4qz4J4bbpQC53WUEHm0Cg p45Benmwbt2iLTfzCreYOAxNoqLEdiMAu8wJNhrEAewKd9/K/Y2QT0XYunGo3bpgPSdw iV8zLmFC0tH/mA2ZrDyAAzK0H226O0n5dSguUGquLxU0s39ufI1XDlfGJEPuSJLiNgZh 05CDQQGtDBedVIgOQZ5YChwOdi+X/VE8Pdq1trdkYghxK+iD1sjB6j69yHFkUYkmeDXa iB6w== MIME-Version: 1.0 Received: by 10.182.72.8 with SMTP id z8mr12479784obu.87.1347400164920; Tue, 11 Sep 2012 14:49:24 -0700 (PDT) Received: by 10.60.46.165 with HTTP; Tue, 11 Sep 2012 14:49:24 -0700 (PDT) Date: Tue, 11 Sep 2012 23:49:24 +0200 Message-ID: From: Andreas Nilsson To: FreeBSD Stable Mailing List Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Clang as default compiler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 21:55:12 -0000 Today I decided to take the plunge and make clang the default compiler, ie I set WITH_CLANG=yes WITH_CLANG_IS_CC=yes WITH_CLANG_EXTRAS=yes in src.conf. No problem so far. However I wanted to avoid building base gcc ( the whole collection ). Is WITHOUT_GCC what I'm looking for? On another clang note: Is there a page specifying valid settings for -march, my google-foo is failing me. Ie, I'm looking for the equivalent of http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options After successful install I went on to upgrade some ports. Is there a specif PR to use for ports that fails with clang and does not specify to use gcc ( devel/cdecl and deskutils/calibre so were the culprits so far) Best regards Andreas From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 22:09:35 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2BB87106566B; Tue, 11 Sep 2012 22:09:35 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id D0C068FC08; Tue, 11 Sep 2012 22:09:34 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.5/8.14.5/NETPLEX) with ESMTP id q8BM9R3r038987; Tue, 11 Sep 2012 18:09:27 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.2.7 (mail.netplex.net [204.213.176.10]); Tue, 11 Sep 2012 18:09:28 -0400 (EDT) Date: Tue, 11 Sep 2012 18:09:27 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Giulio Ferro In-Reply-To: <504FA735.709@zirakzigil.org> Message-ID: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 22:09:35 -0000 On Tue, 11 Sep 2012, Giulio Ferro wrote: > Well, there definitely seems to be a problem with igb and lagg. > > igb alone works as it should, but doesn't seem to work properly in lagg. > > To be sure I started from scratch from a 9.0 release with nothing but: > > /etc/rc.conf > --------------------------------------------------- > ifconfig_igb0="inet ..." > > ifconfig_igb1="up" > ifconfig_igb2="up" > ifconfig_igb3="up" > > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 My rc.conf is something like this: # # For now, force ath0 to use the same MAC address as xl0. # This works around a bug where lagg is unable to set the # MAC address of the underlying wlan0 interface. # ifconfig_ath0="ether 01:02:03:04:05:06" wlans_ath0=wlan0 ifconfig_wlan0="ssid SSID_FOO_NAME WPA" ifconfig_xl0="up" closed_interfaces="lagg0" ifconfig_lagg0="laggproto failover laggport xl0 laggport wlan0" ifconfig_lagg0_alias0="inet 10.0.0.4 netmask 0xffffff00" I use aliasX to add the address and netmask. -- DE From owner-freebsd-stable@FreeBSD.ORG Tue Sep 11 22:12:16 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BD011065673; Tue, 11 Sep 2012 22:12:16 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 0A59A8FC0A; Tue, 11 Sep 2012 22:12:15 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.5/8.14.5/NETPLEX) with ESMTP id q8BMCFDq041313; Tue, 11 Sep 2012 18:12:15 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.2.7 (mail.netplex.net [204.213.176.10]); Tue, 11 Sep 2012 18:12:15 -0400 (EDT) Date: Tue, 11 Sep 2012 18:12:15 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Freddie Cash In-Reply-To: Message-ID: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, Giulio Ferro , "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 22:12:16 -0000 On Tue, 11 Sep 2012, Freddie Cash wrote: > On Sep 11, 2012 2:12 PM, "Giulio Ferro" wrote: >> >> cloned_interfaces="lagg0" >> ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 > 192.168.x.x/24" >> >> sshd_enable="YES" >> --------------------------------------------------- >> >> This doesn't even manage to start sshd, it just hangs there at boot. >> >> Disabling lagg configuration everything works correctly. >> > > Just curious: does it work if you split the lagg configuration from the IP > config: > > ifconfig_lagg0="laggproto ..." > ifconfig_lagg0_alias0="inet 192..." > > I've had problems in the past with cloned interfaces not working right if > you do everything in one ifconfig line. Never spent much time debugging it, > though, as the split config always worked. This was my experience too, though it's been quite a while since I tried it combined onto the same ifconfig line. -- DE From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 03:23:24 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40D311065672 for ; Wed, 12 Sep 2012 03:23:24 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2]) by mx1.freebsd.org (Postfix) with ESMTP id E9D0D8FC0C for ; Wed, 12 Sep 2012 03:23:23 +0000 (UTC) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.5/8.14.5) with ESMTP id q8C3NHc0002411; Tue, 11 Sep 2012 23:23:17 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.5/8.14.4/Submit) id q8C3NGs4002410; Tue, 11 Sep 2012 23:23:16 -0400 (EDT) (envelope-from wollman) Date: Tue, 11 Sep 2012 23:23:16 -0400 (EDT) From: Garrett Wollman Message-Id: <201209120323.q8C3NGs4002410@hergotha.csail.mit.edu> To: niobos@dest-unreach.be In-Reply-To: <504F4049.9080801@dest-unreach.be> Organization: none X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (hergotha.csail.mit.edu [127.0.0.1]); Tue, 11 Sep 2012 23:23:17 -0400 (EDT) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hergotha.csail.mit.edu Cc: stable@freebsd.org Subject: Re: Kernel panic with geom_multipath + ZFS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 03:23:24 -0000 In article <504F4049.9080801@dest-unreach.be>, niobos@dest-unreach.be writes: > >I'm under the illusion that I've found a bug in the FreeBSD kernel, but >since I'm new to FreeBSD, a quiet voice tells me it's probably a case of >"you're doing it wrong". Nope. It's a known bug in the version of geom_multipath that shipped with FreeBSD 9.0. It's fixed in 9.1. -GAWollman From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 04:31:32 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3255A106566B for ; Wed, 12 Sep 2012 04:31:32 +0000 (UTC) (envelope-from alonsoschaich@fastmail.fm) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id E7B588FC17 for ; Wed, 12 Sep 2012 04:31:31 +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 CA5CC21183 for ; Wed, 12 Sep 2012 00:31:25 -0400 (EDT) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 12 Sep 2012 00:31:25 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= from:to:subject:date:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; s=mesmtp; bh=FSOzHTPi4XJog1BYgAE4IJMbLcA=; b=bCTB9JwKzl8R+vFGVc/kMZPYoo3u lzqiK+yGG59if2Ra8UmWHEMw8c0oD3hKWrYY5sFNQGzfVSph38lYpbDDcr09rGQb x4f5DQvdfQFQpzODGv+8oqVkIyDsq5etm1slsdn1lEhA5DM5T4NUJ5g/1LKWNo9y UCy7SIXTxdwyGho= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=from:to:subject:date:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id; s=smtpout; bh=FSOzHTPi4XJog1BYgAE4IJMbLcA=; b=EIshS Sr7QeZdvd338cRCd4bOV3Q4fr4saVXKuMAt4Hej2hRkWMA+OIKDErOeGNxy7+Ich VsXbEQD09AuuQGDP5caJGj+FkPk3iSN7bQjBkStFAwkBVY9pHqhIZANbxMITKJIx hdN0X8jeO0hCa1djmf6R55sG/9392nUT1LqRw8= X-Sasl-enc: B3cysv970zkzqK9ujOeo0+mhJ6njwLGiUdHYdtEh8VxZ 1347424285 Received: from harmony.localnet.edu (unknown [217.84.49.43]) by mail.messagingengine.com (Postfix) with ESMTPA id 739AB4827A9 for ; Wed, 12 Sep 2012 00:31:25 -0400 (EDT) From: Schaich Alonso To: freebsd-stable@freebsd.org Date: Wed, 12 Sep 2012 06:30:33 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.8.4; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201209120630.33981.alonsoschaich@fastmail.fm> Subject: Re: Clang as default compiler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 04:31:32 -0000 On 2012-09-11 (Tuesday) 23:49:24 Andreas Nilsson wrote: > Today I decided to take the plunge and make clang the default compiler, ie > I set > > WITH_CLANG=yes > WITH_CLANG_IS_CC=yes > WITH_CLANG_EXTRAS=yes > > in src.conf. No problem so far. However I wanted to avoid building base gcc > ( the whole collection ). Is WITHOUT_GCC what I'm looking for? > It probably is. However, WITHOUT_GCC is not supported yet. > On another clang note: Is there a page specifying valid settings for > -march, my google-foo is failing me. Ie, I'm looking for the equivalent of > http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.htm > l#i386-and-x86_002d64-Options > Take a look at lines 120 and below of contrib/llvm/lib/Target/X86/X86.td in the FreeBSD source directory for supported march switches. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 05:58:39 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 36E2E1065674 for ; Wed, 12 Sep 2012 05:58:39 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id B9D2E8FC15 for ; Wed, 12 Sep 2012 05:58:38 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so1010863wgb.31 for ; Tue, 11 Sep 2012 22:58:37 -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=cFeggw+NzLWEJuO1HLiQX4Be7R/E2HEppcoPo9t+nCM=; b=OY+2lQtuUDevXnBzLYLr+eBh6SpRDkgB8nQ+Tdhs5jEZPU2yFnbxHDmv7JaLD98f17 WcvZv6+jV3ZBKjqBRTjROhZxg8tJWh49ovdKTKJl0khUeEkLoLt20bZjF4AxAY5+1BaM 8OH/MEL3YAG8rtudJffnxJIwRrUJFcCAQzHpEaMY3nD1/ezPgZtb4fWw8SsGup7GsjWR +6opal9cu92li8VAx45kmm1GkREiPUJEvEHNrx23DoPZYKzCUSiGaSUX34wgTG+nkT/z 1Rp9httwwnjXdKA3/Z3k6xfeRxIcsiVclbIlVLo4PNMhhT3hWqNDX3nBUN9Me16QGP3W e6gA== Received: by 10.180.90.104 with SMTP id bv8mr30128210wib.22.1347429517590; Tue, 11 Sep 2012 22:58:37 -0700 (PDT) Received: from localhost ([188.230.122.226]) by mx.google.com with ESMTPS id t8sm6439937wiy.3.2012.09.11.22.58.35 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Sep 2012 22:58:36 -0700 (PDT) Date: Wed, 12 Sep 2012 08:58:34 +0300 From: Mikolaj Golub To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20120912055831.GA48849@gmail.com> References: <504D10A7.1070701@quip.cz> <20120910054459.GA57302@gmail.com> <504DFD37.60105@quip.cz> <20120910203511.GA27221@gmail.com> <504F9C39.2070107@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <504F9C39.2070107@quip.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: bsnmpd always died on HDD detach X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 05:58:39 -0000 On Tue, Sep 11, 2012 at 10:16:57PM +0200, Miroslav Lachman wrote: > (gdb) bt > #0 0x0000000801046cba in refresh_disk_storage_tbl () from > /usr/lib/snmp_hostres.so > #1 0x00000008010478bd in refresh_device_tbl () from > /usr/lib/snmp_hostres.so > #2 0x0000000801047be6 in start_device_tbl () from /usr/lib/snmp_hostres.so > #3 0x000000080065fad5 in poll_dispatch () from /lib/libbegemot.so.4 > #4 0x000000000040616a in main () > > > Is it all you need? (I don't know how to use gdb) > > It is on FreeBSD 8.3-RELEASE #0: Mon Apr 9 21:23:18 UTC 2012 > root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Not sure we can get more than provided from this core as snmp_hostres is not built with debugging symbols. You can try rebuilding snmp_hostres with -g option, intalling and running gdb/bt again DEBUG_FLAGS=-g make -C /usr/src/usr.sbin/bsnmpd/modules/snmp_hostres clean all install AFAIK it might work or not. If it does not then wait for another crash :-) -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 06:04:55 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A44D106564A for ; Wed, 12 Sep 2012 06:04:55 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 73E7A8FC0C for ; Wed, 12 Sep 2012 06:04:55 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 3886F5625E; Wed, 12 Sep 2012 01:04:20 -0500 (CDT) Date: Wed, 12 Sep 2012 01:04:20 -0500 From: Mark Linimon To: Andreas Nilsson Message-ID: <20120912060420.GE31029@lonesome.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: FreeBSD Stable Mailing List Subject: Re: Clang as default compiler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 06:04:55 -0000 On Tue, Sep 11, 2012 at 11:49:24PM +0200, Andreas Nilsson wrote: > Is there a specif PR to use for ports that fails with clang and does > not specify to use gcc ( > devel/cdecl and deskutils/calibre so were > the culprits so far) There is no specific PR. We have not yet placed the requirement on our ports maintainers to deal with clang. For most of the failures, we are already aware of them, as a result of our periodic runs. So, just filing a PR to say "broken on clang" doesn't really help us all that much. mcl From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 06:16:33 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EA92106564A; Wed, 12 Sep 2012 06:16:33 +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 F2E818FC17; Wed, 12 Sep 2012 06:16:32 +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 q8C6GW8P033200; Wed, 12 Sep 2012 06:16:32 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id q8C6GWqw033162; Wed, 12 Sep 2012 06:16:32 GMT (envelope-from tinderbox@freebsd.org) Date: Wed, 12 Sep 2012 06:16:32 GMT Message-Id: <201209120616.q8C6GWqw033162@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 , , Precedence: bulk Cc: Subject: [releng_9_1 tinderbox] failure on arm/arm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 06:16:33 -0000 TB --- 2012-09-12 06:10:00 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-09-12 06:10:00 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-09-12 06:10:00 - starting RELENG_9_1 tinderbox run for arm/arm TB --- 2012-09-12 06:10:00 - cleaning the object tree TB --- 2012-09-12 06:10:00 - checking out /src from svn://svn.freebsd.org/base/releng/9.1 TB --- 2012-09-12 06:10:00 - cd /tinderbox/RELENG_9_1/arm/arm TB --- 2012-09-12 06:10:00 - /usr/local/bin/svn cleanup /src TB --- 2012-09-12 06:11:43 - /usr/local/bin/svn update /src TB --- 2012-09-12 06:16:32 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-09-12 06:16:32 - ERROR: unable to check out the source tree TB --- 2012-09-12 06:16:32 - 3.31 user 4.05 system 391.70 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9_1-arm-arm.full From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 06:16:50 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFAEF10656A8; Wed, 12 Sep 2012 06:16:50 +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 82F1C8FC08; Wed, 12 Sep 2012 06:16:50 +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 q8C6GoAK037388; Wed, 12 Sep 2012 06:16:50 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id q8C6GoiJ037387; Wed, 12 Sep 2012 06:16:50 GMT (envelope-from tinderbox@freebsd.org) Date: Wed, 12 Sep 2012 06:16:50 GMT Message-Id: <201209120616.q8C6GoiJ037387@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 , , Precedence: bulk Cc: Subject: [releng_9_1 tinderbox] failure on i386/pc98 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 06:16:50 -0000 TB --- 2012-09-12 06:10:00 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-09-12 06:10:00 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-09-12 06:10:00 - starting RELENG_9_1 tinderbox run for i386/pc98 TB --- 2012-09-12 06:10:00 - cleaning the object tree TB --- 2012-09-12 06:10:00 - checking out /src from svn://svn.freebsd.org/base/releng/9.1 TB --- 2012-09-12 06:10:00 - cd /tinderbox/RELENG_9_1/i386/pc98 TB --- 2012-09-12 06:10:00 - /usr/local/bin/svn cleanup /src TB --- 2012-09-12 06:11:43 - /usr/local/bin/svn update /src TB --- 2012-09-12 06:16:50 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-09-12 06:16:50 - ERROR: unable to check out the source tree TB --- 2012-09-12 06:16:50 - 3.41 user 3.98 system 409.67 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9_1-i386-pc98.full From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 06:18:36 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60FA01065693 for ; Wed, 12 Sep 2012 06:18:36 +0000 (UTC) (envelope-from christer.solskogen@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 276D58FC2F for ; Wed, 12 Sep 2012 06:18:35 +0000 (UTC) Received: by iebc12 with SMTP id c12so2941184ieb.13 for ; Tue, 11 Sep 2012 23:18:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=azAt8w4vw5MOpLPDEaOFvJgsxQNu5V/PWHMqajlmXnw=; b=GLEj/Tmbs442u8iK1en2pkSJaUCbYJmrEo3mCuRG4XwVmEfSoV83bEdWP7FQKiztEN ssyLls/dR6F0M3eyZCS7DEF+I1PkJeFrzE4ZRDbwq2EslrqtPUI/pB0pSI865/iHQQFy 83nc9mZzMiUuG0Jd/Ixu2W2MBl++D66qHTDDLw6hcjSmpUt4aeVHWEAS7R2l22sTFJgG baEiVA6+9ctQ2FeoLu1ci4RjzgClacoX4ngER5uH7Q+ybMgr3FxeoaEPuHdqbJaxBHuv z/8/BzgXmVBbkC4PWmAl1Ey9rI5EYCwq7a9kmuMexO1wfKq9X8cXTWdeXNiQ/kJoDKCB fpaQ== Received: by 10.42.114.16 with SMTP id e16mr23952922icq.57.1347430715230; Tue, 11 Sep 2012 23:18:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.103.103 with HTTP; Tue, 11 Sep 2012 23:18:15 -0700 (PDT) In-Reply-To: <20120912060420.GE31029@lonesome.com> References: <20120912060420.GE31029@lonesome.com> From: Christer Solskogen Date: Wed, 12 Sep 2012 08:18:15 +0200 Message-ID: To: Mark Linimon Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Stable Mailing List , Andreas Nilsson Subject: Re: Clang as default compiler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 06:18:36 -0000 On Wed, Sep 12, 2012 at 8:04 AM, Mark Linimon wrote: > For most of the failures, we are already aware of them, as a result of > our periodic runs. So, just filing a PR to say "broken on clang" doesn't > really help us all that much. > I disagree. Just a tiny bit ;-) If the PR says that USE_GCC=4.2 works as a workaround, it helps. -- chs, From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 07:00:48 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53B0B106564A for ; Wed, 12 Sep 2012 07:00:48 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id CE8418FC1C for ; Wed, 12 Sep 2012 07:00:47 +0000 (UTC) Received: by eeke52 with SMTP id e52so1038394eek.13 for ; Wed, 12 Sep 2012 00:00:46 -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=wDAUuBavzNQtMRvkLsJpHw1LElqMy6YYaWTudRHpybY=; b=wKd6H5zHOtqa0MDTHG6CUudtMlp00ft7bkU9Eg0HLTa7PmPr8tESgy4hZBA2Z8faON h53L7MLtTmdUqE4sZYQmd51ikB0hYXLClX8jiyUkUFWkS4WrnVilj4cV7AsGGXFb5j84 KAGwa7BZEaMrBQw+H1U60MEaNNq6Wnaxxyiucaba8bMN+y3tNP0B/qsoOdY2++50dasH 3T4plmwHLBsOp4FsOrS79ibHfSxNc8+UvY4kovlFgwYMgHxVqXEZh2bKPKFkNCqks+Nr XaJlIVhIYA240RB7aYJk2+uFJrv3Q7tbkIPS8whRZtrRH4Y2Yh9gCyGyWG4cHW6y4Lxw kheg== MIME-Version: 1.0 Received: by 10.204.157.18 with SMTP id z18mr5615622bkw.16.1347433246646; Wed, 12 Sep 2012 00:00:46 -0700 (PDT) Received: by 10.204.10.141 with HTTP; Wed, 12 Sep 2012 00:00:46 -0700 (PDT) Received: by 10.204.10.141 with HTTP; Wed, 12 Sep 2012 00:00:46 -0700 (PDT) In-Reply-To: References: <20120912060420.GE31029@lonesome.com> Date: Wed, 12 Sep 2012 08:00:46 +0100 Message-ID: From: Chris Rees To: Christer Solskogen Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Mark Linimon , FreeBSD , Andreas Nilsson Subject: Re: Clang as default compiler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 07:00:48 -0000 On 12 Sep 2012 07:19, "Christer Solskogen" wrote: > > On Wed, Sep 12, 2012 at 8:04 AM, Mark Linimon wrote: > > > For most of the failures, we are already aware of them, as a result of > > our periodic runs. So, just filing a PR to say "broken on clang" doesn't > > really help us all that much. > > > > I disagree. Just a tiny bit ;-) > If the PR says that USE_GCC=4.2 works as a workaround, it helps. We don't want thousands of PRs duplicating the information from a simple list of failures. Any can be fixed in this way. Chris From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 07:02:14 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A39E4106566B for ; Wed, 12 Sep 2012 07:02:14 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 78D738FC19 for ; Wed, 12 Sep 2012 07:02:13 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 978385623C; Wed, 12 Sep 2012 02:02:12 -0500 (CDT) Date: Wed, 12 Sep 2012 02:02:12 -0500 From: Mark Linimon To: Chris Rees Message-ID: <20120912070212.GA12778@lonesome.com> References: <20120912060420.GE31029@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Christer Solskogen , FreeBSD , Andreas Nilsson Subject: Re: Clang as default compiler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 07:02:14 -0000 On Wed, Sep 12, 2012 at 08:00:46AM +0100, Chris Rees wrote: > We don't want thousands of PRs duplicating the information from a simple > list of failures. Thanks, that was the point I was trying to make. mcl From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 08:39:17 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A96F3106566C for ; Wed, 12 Sep 2012 08:39:17 +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 253538FC18 for ; Wed, 12 Sep 2012 08:39:16 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 0481028427; Wed, 12 Sep 2012 10:39:15 +0200 (CEST) Received: from [192.168.1.2] (static-84-242-120-26.net.upcbroadband.cz [84.242.120.26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 9815628426; Wed, 12 Sep 2012 10:39:13 +0200 (CEST) Message-ID: <50504A30.10501@quip.cz> Date: Wed, 12 Sep 2012 10:39:12 +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: Mikolaj Golub References: <504D10A7.1070701@quip.cz> <20120910054459.GA57302@gmail.com> <504DFD37.60105@quip.cz> <20120910203511.GA27221@gmail.com> <504F9C39.2070107@quip.cz> <20120912055831.GA48849@gmail.com> In-Reply-To: <20120912055831.GA48849@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: bsnmpd always died on HDD detach X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 08:39:17 -0000 Mikolaj Golub wrote: > On Tue, Sep 11, 2012 at 10:16:57PM +0200, Miroslav Lachman wrote: > >> (gdb) bt >> #0 0x0000000801046cba in refresh_disk_storage_tbl () from >> /usr/lib/snmp_hostres.so >> #1 0x00000008010478bd in refresh_device_tbl () from >> /usr/lib/snmp_hostres.so >> #2 0x0000000801047be6 in start_device_tbl () from /usr/lib/snmp_hostres.so >> #3 0x000000080065fad5 in poll_dispatch () from /lib/libbegemot.so.4 >> #4 0x000000000040616a in main () >> >> >> Is it all you need? (I don't know how to use gdb) >> >> It is on FreeBSD 8.3-RELEASE #0: Mon Apr 9 21:23:18 UTC 2012 >> root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > Not sure we can get more than provided from this core as snmp_hostres > is not built with debugging symbols. You can try rebuilding > snmp_hostres with -g option, intalling and running gdb/bt again > > DEBUG_FLAGS=-g make -C /usr/src/usr.sbin/bsnmpd/modules/snmp_hostres clean all install > > AFAIK it might work or not. If it does not then wait for another crash :-) I don't know it is better or not. All I can say is: "it's different" ;) # gdb /usr/sbin/bsnmpd /bsnmpd.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... Core was generated by `bsnmpd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libbegemot.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libbegemot.so.4 Reading symbols from /lib/libbsnmp.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libbsnmp.so.5 Reading symbols from /usr/lib/libwrap.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libwrap.so.6 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/lib/snmp_mibII.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/snmp_mibII.so Reading symbols from /usr/lib/snmp_pf.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/snmp_pf.so Reading symbols from /usr/lib/snmp_hostres.so...done. Loaded symbols for /usr/lib/snmp_hostres.so Reading symbols from /lib/libkvm.so.5...done. Loaded symbols for /lib/libkvm.so.5 Reading symbols from /usr/lib/libdevinfo.so.5...done. Loaded symbols for /usr/lib/libdevinfo.so.5 Reading symbols from /lib/libm.so.5...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libgeom.so.5...done. Loaded symbols for /lib/libgeom.so.5 Reading symbols from /usr/lib/libmemstat.so.3...done. Loaded symbols for /usr/lib/libmemstat.so.3 Reading symbols from /lib/libbsdxml.so.4...done. Loaded symbols for /lib/libbsdxml.so.4 Reading symbols from /lib/libsbuf.so.5...done. Loaded symbols for /lib/libsbuf.so.5 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x0000000801046cba in disk_query_disk (entry=0x0) at hostres_diskstorage_tbl.c:241 241 partition_tbl_handle_disk(entry->index, entry->dev_name); (gdb) bt #0 0x0000000801046cba in disk_query_disk (entry=0x0) at hostres_diskstorage_tbl.c:241 #1 0x0000000801dd6a00 in ?? () #2 0x0000000801dd6600 in ?? () #3 0x0000000000000000 in ?? () #4 0x0000000801048230 in device_entry_create (name=0x0, location=0x800c14ee0 "0", descr=0x8010482a6 "") at hostres_device_tbl.c:217 #5 0x0000000801dd7800 in ?? () #6 0x0000000801dd7800 in ?? () #7 0x0000000801dd7400 in ?? () #8 0x0000000000000000 in ?? () #9 0x0000000801048230 in device_entry_create (name=0x801dd7c00 "", location=0x801048230 "˙˙I\213|$8čŕ\201˙˙L\211çčŘ\201˙˙é\035ţ˙˙H\215\025", descr=0x8010482a6 "") at hostres_device_tbl.c:217 #10 0x0000000801dd4a00 in ?? () #11 0x0000000801dd4a00 in ?? () #12 0x0000000801dd1a00 in ?? () #13 0x0000000000000000 in ?? () #14 0x0000000801048230 in device_entry_create (name=0x801dd8400 "", location=0x801048230 "˙˙I\213|$8čŕ\201˙˙L\211çčŘ\201˙˙é\035ţ˙˙H\215\025", descr=0x8010482a6 "") at hostres_device_tbl.c:217 #15 0x0000000801dd1800 in ?? () #16 0x0000000801dd1800 in ?? () #17 0x0000000800c00ea8 in ?? () #18 0x000000000051b1c8 in ?? () #19 0x0000000800c00938 in ?? () #20 0x000000000051b258 in ?? () #21 0x0000000801dc8a00 in ?? () #22 0x00000008009f7be9 in free () from /lib/libc.so.7 #23 0x0000000000000000 in ?? () #24 0x00007fffffffed98 in ?? () #25 0x00000008010478bd in device_entry_delete () at hostres_device_tbl.c:266 #26 0x00000000005187d0 in snmp_error () #27 0x0000000801047be6 in op_hrDeviceTable (ctx=Variable "ctx" is not available. ) at hostres_device_tbl.c:671 #28 0x000000000051b840 in ?? () #29 0x000000000051b830 in ?? () #30 0x0000000000000000 in ?? () #31 0x00007fffffffc360 in ?? () #32 0x000000000051b830 in ?? () #33 0x0000000000000000 in ?? () #34 0x00000008009efbd2 in _pthread_mutex_init_calloc_cb () from /lib/libc.so.7 #35 0x00000008009f2d32 in _malloc_prefork () from /lib/libc.so.7 #36 0x00000008009f6e1f in realloc () from /lib/libc.so.7 #37 0x0000000800e0b441 in mib_if_is_dyn () from /usr/lib/snmp_mibII.so #38 0x0000000000000000 in ?? () #39 0x00007fffffffc5cc in ?? () #40 0x0000000000000001 in ?? () #41 0x00007fffffffc5e0 in ?? () #42 0x31fa39e2fac72819 in ?? () #43 0x0000000000000001 in ?? () #44 0x000000080065fad5 in poll_dispatch () from /lib/libbegemot.so.4 #45 0x000000000040616a in main () I hope it helps you to debug this problem. Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 08:54:57 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5EF11065674 for ; Wed, 12 Sep 2012 08:54:57 +0000 (UTC) (envelope-from yerenkow@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 86E918FC08 for ; Wed, 12 Sep 2012 08:54:57 +0000 (UTC) Received: by iebc12 with SMTP id c12so3190867ieb.13 for ; Wed, 12 Sep 2012 01:54:51 -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=5j6UfrCc19Msjg6JJPafb28rn4fP49Z5LQekTnegSoI=; b=YYp3pK3lpNM40tG6t616DiR0s6vv6ZXMlGr38WSUXZcHD5PnE1uCg5cVDYMUB6wOM2 1m1VbV1tjR7QeSufqPRxQ9FrcVCT9KZbxdTHs0XJgfBD3NJiWrxeeRkNKAlQU1dW3UQ4 P8UDacrbTGnKrWiKBUDqfJHEgNuWerwIKVgPKJQRpFIXDGLdnw7okXPWADbBNLXahy93 VKDwmm4iKzbAoXCXvfi2PamyHTmozo0PBAJcR5Ik9qcGuJfEHM6oZKMbZbgFJJVgiVM6 ttgvGVcBanq9q3FnacZeLSO1j1N3waZdGiwhAEiYbjCO+9hOmciiTuc+1GiAetu/YaqW h2JQ== MIME-Version: 1.0 Received: by 10.50.190.197 with SMTP id gs5mr20292503igc.32.1347440091697; Wed, 12 Sep 2012 01:54:51 -0700 (PDT) Received: by 10.64.28.36 with HTTP; Wed, 12 Sep 2012 01:54:51 -0700 (PDT) In-Reply-To: <20120912070212.GA12778@lonesome.com> References: <20120912060420.GE31029@lonesome.com> <20120912070212.GA12778@lonesome.com> Date: Wed, 12 Sep 2012 11:54:51 +0300 Message-ID: From: Alexander Yerenkow To: Mark Linimon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Christer Solskogen , FreeBSD , Andreas Nilsson , Chris Rees Subject: Re: Clang as default compiler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 08:54:57 -0000 How about run automated test on two poudriere setups, one with CLANG set up, other with USE_GCC=4.2 applied to all ports which marked as broken, and find in pretty long but relatively easy way ports which should have USE_GCC=4.2 to survive clang-era, and ports which even with that require a bit more love? Is there somewhere list of these clang-failing ports? I think some mass testing could be organized by little efforts. -- Regards, Alexander Yerenkow From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 09:08:37 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6860F106564A for ; Wed, 12 Sep 2012 09:08:37 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 3B5E98FC14 for ; Wed, 12 Sep 2012 09:08:36 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 83D3E56258; Wed, 12 Sep 2012 04:08:35 -0500 (CDT) Date: Wed, 12 Sep 2012 04:08:35 -0500 From: Mark Linimon To: Alexander Yerenkow Message-ID: <20120912090835.GA22971@lonesome.com> References: <20120912060420.GE31029@lonesome.com> <20120912070212.GA12778@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Christer Solskogen , FreeBSD , Andreas Nilsson , Chris Rees Subject: Re: Clang as default compiler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 09:08:37 -0000 On Wed, Sep 12, 2012 at 11:54:51AM +0300, Alexander Yerenkow wrote: > How about run automated test on two poudriere setups, one with CLANG set > up, other with USE_GCC=4.2 applied to all ports which marked as broken, We have been running various tests for quite some time. > Is there somewhere list of these clang-failing ports? http://wiki.freebsd.org/PortsAndClang . I have been maintaing and updating this for over a year now. mcl From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 09:15:14 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 080411065680; Wed, 12 Sep 2012 09:15:14 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5F6D98FC19; Wed, 12 Sep 2012 09:15:13 +0000 (UTC) Received: from vhoffman.lon.namesco.net (lon.namesco.net [195.7.254.102]) (authenticated bits=0) by unsane.co.uk (8.14.5/8.14.5) with ESMTP id q8C9FBxu063402 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 12 Sep 2012 10:15:12 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <5050529F.20900@unsane.co.uk> Date: Wed, 12 Sep 2012 10:15:11 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: Giulio Ferro References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> In-Reply-To: <504FA735.709@zirakzigil.org> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 09:15:14 -0000 On 11/09/2012 22:03, Giulio Ferro wrote: > Well, there definitely seems to be a problem with igb and lagg. > > igb alone works as it should, but doesn't seem to work properly in lagg. > > To be sure I started from scratch from a 9.0 release with nothing but: > > /etc/rc.conf > --------------------------------------------------- > ifconfig_igb0="inet ..." > > ifconfig_igb1="up" > ifconfig_igb2="up" > ifconfig_igb3="up" > > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport > igb3 192.168.x.x/24" > > sshd_enable="YES" > --------------------------------------------------- > > This doesn't even manage to start sshd, it just hangs there at boot. > > Disabling lagg configuration everything works correctly. For what is worth its working fine for me on 8.3-RELEASE using failover. ifconfig_igb0="up" ifconfig_igb1="up" cloned_interfaces="lagg0 lagg0.53 lagg0.52 lagg0.66" ifconfig_lagg0="laggproto failover laggport igb0 laggport igb1 85.233.xxx.xxx/23" ifconfig_lagg0_53="inet 192.168.xxx.226/24" ifconfig_lagg0_52="inet 192.168.xxx.254/24" ifconfig_lagg0_66="inet 192.168.xxx.250/24" ipv4_addrs_lagg0_52="192.168.xxx.254/24 192.168.0.70/24" lagg0: flags=8843 metric 0 mtu 1500 options=401bb ether 00:25:90:39:64:76 inet 85.233.xx.xx netmask 0xfffffe00 broadcast 85.233.xx.255 media: Ethernet autoselect status: active laggproto failover laggport: igb1 flags=0<> laggport: igb0 flags=5 Vince From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 10:08:25 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1782E1065672 for ; Wed, 12 Sep 2012 10:08:25 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id C7F398FC0C for ; Wed, 12 Sep 2012 10:08:24 +0000 (UTC) Received: by obbun3 with SMTP id un3so2920169obb.13 for ; Wed, 12 Sep 2012 03:08:23 -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=n+sHydzfP9EiTCtW69yz7hcYSDnJ7zv2IcZ1aJoCpuc=; b=jIWS+m4z++ocQ9h32PDDiUZs/BapdzyRtCmOFxm7TnXQmPnXj/h3zAfz0Lj0wiyHBH /e169/RixpYjEPT+EhZE2BbzgLXFR4SZvhy/YFDJaeAkruuDq9/UYk7re4LaUE4r/pSd 2gvSsa04Zgk2VbIfo+JSWTdOzh1n2xqh8TEjECgsOSvY2URvVXZG8fcmOpkZd8q7zh60 Vv4fjhn4bKlilaEAvBiAWC+vO807fATqGbdn6jy77PlSPeYMPsLdnnKlwG7tDPlZtW1X +Twnp/KeXu4vJVoL8LRfmpVQ4S2Pg1VDT+gH8CRvyIO0JkawVmJUpEWFrlnAH5AD2/Ah FVqQ== MIME-Version: 1.0 Received: by 10.60.25.226 with SMTP id f2mr21073326oeg.53.1347444503745; Wed, 12 Sep 2012 03:08:23 -0700 (PDT) Received: by 10.60.46.165 with HTTP; Wed, 12 Sep 2012 03:08:23 -0700 (PDT) In-Reply-To: <201209120630.33981.alonsoschaich@fastmail.fm> References: <201209120630.33981.alonsoschaich@fastmail.fm> Date: Wed, 12 Sep 2012 12:08:23 +0200 Message-ID: From: Andreas Nilsson To: Schaich Alonso Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: Clang as default compiler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 10:08:25 -0000 > > > > in src.conf. No problem so far. However I wanted to avoid building base > gcc > > ( the whole collection ). Is WITHOUT_GCC what I'm looking for? > > > > It probably is. However, WITHOUT_GCC is not supported yet. > > > On another clang note: Is there a page specifying valid settings for > > -march, my google-foo is failing me. Ie, I'm looking for the equivalent > of > > > http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.htm > > l#i386-and-x86_002d64-Options > > > > Take a look at lines 120 and below of contrib/llvm/lib/Target/X86/X86.td in > the FreeBSD source directory for supported march switches. > >There is no specific PR. We have not yet placed the requirement on our >ports maintainers to deal with clang. Is there a time frame for this requirement? And for the know broken ports, how are the users supposed to deal with them until the ports is fixed? Modifying the port by hand in the local ports tree? Best regards Andreas From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 11:25:55 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 709F8106564A for ; Wed, 12 Sep 2012 11:25:55 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id EB9E08FC0C for ; Wed, 12 Sep 2012 11:25:53 +0000 (UTC) Received: by eeke52 with SMTP id e52so1269740eek.13 for ; Wed, 12 Sep 2012 04:25:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=5nFjshyF3IwEfANGZ3FLXC/bKPTqPeLks61n/jaPAtE=; b=MMDd+IvOjKuLpRx0kUrYPLT+edhhRSbKdEE4HKmc7oa67Dc/W5cis+sRX7Vli59GV6 Ocax4Ltfd2wGPWZWISGcHDmDkz4aDt9mouU/63/sqP5PhLlSXRddbr/6qYNGy/8jcSLp tfDnW2tI1Zv8EcDbRpcN4s8wcj3ScacRX2F/aiFWPyefN9JZTSTOnFWAHkHm7Nsxo0bG tBNSdl9Ex+/w3/1x5rPibDU4TAL4dlZCrO8VRKPrwjxwYgOisUKbS2Q/rIfxH6q6Faxi G27+8hkulPyu+5xR3GlSeq9Bh/KfQYBXwNaX4XHx4G73OUo3iVyrF1JaRfU+7Lst52xq QC+A== Received: by 10.204.145.90 with SMTP id c26mr5855889bkv.34.1347449152894; Wed, 12 Sep 2012 04:25:52 -0700 (PDT) Received: from green.local (186-102-132-95.pool.ukrtel.net. [95.132.102.186]) by mx.google.com with ESMTPS id gq2sm11607839bkc.13.2012.09.12.04.25.50 (version=SSLv3 cipher=OTHER); Wed, 12 Sep 2012 04:25:51 -0700 (PDT) Message-ID: <5050713D.4000400@gmail.com> Date: Wed, 12 Sep 2012 14:25:49 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 MIME-Version: 1.0 To: Andreas Nilsson References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Mailing List Subject: Re: Clang as default compiler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 11:25:55 -0000 12.09.2012 00:49, Andreas Nilsson wrote: > On another clang note: Is there a page specifying valid settings for > -march, my google-foo is failing me. Ie, I'm looking for the equivalent of > http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options I'm using the minimum of: : | gcc -E -v -march=native - : | clang -E -v -march=native - because there are number of ports that still doesn't compile with clang or GCC4.6. > After successful install I went on to upgrade some ports. Is there a specif > PR to use for ports that fails with clang and does not specify to use gcc ( > devel/cdecl and deskutils/calibre so were the culprits so far) It's up to you to fix this ports and submit patches. You can always rollback to using GCC. -- Sphinx of black quartz judge my vow. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 11:34:27 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB4D1106564A; Wed, 12 Sep 2012 11:34:27 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mx1.freebsd.org (Postfix) with ESMTP id 5CCE28FC14; Wed, 12 Sep 2012 11:34:26 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id BD7906A6001; Wed, 12 Sep 2012 13:34:25 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.5/8.14.5) with ESMTP id q8CBYPuS000577; Wed, 12 Sep 2012 13:34:25 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.5/8.14.5/Submit) id q8CBYPdh099455; Wed, 12 Sep 2012 13:34:25 +0200 (CEST) (envelope-from lars) Date: Wed, 12 Sep 2012 13:34:25 +0200 From: Lars Engels To: Thomas Steen Rasmussen Message-ID: <20120912113425.GK20762@e-new.0x20.net> References: <5007CFE6.6030808@intersonic.se> <500853DA.8050502@intersonic.se> <201207311632.30938.jhb@freebsd.org> <20120822093317.GW32916@e-new.0x20.net> <5034D4CD.4030301@gibfest.dk> <20120822165239.GX32916@e-new.0x20.net> <50351EA4.4040401@gibfest.dk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OPsOAWNf+lTlQ18+" Content-Disposition: inline In-Reply-To: <50351EA4.4040401@gibfest.dk> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.3-RELEASE-p2 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 11:34:27 -0000 --OPsOAWNf+lTlQ18+ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 22, 2012 at 08:02:12PM +0200, Thomas Steen Rasmussen wrote: >=20 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > =20 > On 22-08-2012 18:52, Lars Engels wrote: > > On Wed, Aug 22, 2012 at 02:47:09PM +0200, Thomas Steen Rasmussen wrote: > >> > >> On 22-08-2012 11:33, Lars Engels wrote: > >>> > >>> I have a T61 running 9.1-BETA1 (with PC-BSD). In most cases it is > >>> booting fine, but from time to time it hangs at boot time but the last > >>> lines are uhub0: ... to uhub4 > >>> Is that the same or a different issue? > >> Hello, > >> > >> I have that exact issue on an X301 after upgrading from 9.0 to > >> 9-STABLE a little while ago. It feels like it happens mostly when > >> rebooting from Windows to FreeBSD (dualboot machine), but I've > >> seen it from a cold boot as well. I've never seen it twice in > >> a row - turning the machine off and on again (by holding the > >> power button down) and it boots normally the next time. > >> > >> I am willing to test patches or enable extra debugging, or > >> help out any other way I can :) > > > > Have you ever seen that with verbose boot enabled? > Hello, >=20 > No, but I can boot verbosely the next times I boot and see if it comes up= ? Meanwhile I found out what's the cause of it. On 9.x it only hung from time to time, but I tried a few weeks old CURRENT and it hung at every boot at the same time. With enabled verbose boot it looked like this: http://bsd-geek.de/FreeBSD/IMAG0190.jpg Then I removed the AC cable and booted from battery and that worked. So it seems to me that some ACPI change in CURRENT made the situation even worse. --OPsOAWNf+lTlQ18+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlBQc0EACgkQKc512sD3afgWGQCgp/psKuu4ns7SOhfqK2h4Jy3/ HpUAnjzZQ+nzCRgcpt7nvZ8f0Pw3lyK0 =A13I -----END PGP SIGNATURE----- --OPsOAWNf+lTlQ18+-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 12:54:37 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 85776106564A; Wed, 12 Sep 2012 12:54:37 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 99F3F8FC12; Wed, 12 Sep 2012 12:54:35 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA04514; Wed, 12 Sep 2012 15:54:30 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <50508606.4040704@FreeBSD.org> Date: Wed, 12 Sep 2012 15:54:30 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120830 Thunderbird/15.0 MIME-Version: 1.0 To: Lars Engels References: <5007CFE6.6030808@intersonic.se> <500853DA.8050502@intersonic.se> <201207311632.30938.jhb@freebsd.org> <20120822093317.GW32916@e-new.0x20.net> <5034D4CD.4030301@gibfest.dk> <20120822165239.GX32916@e-new.0x20.net> <50351EA4.4040401@gibfest.dk> <20120912113425.GK20762@e-new.0x20.net> In-Reply-To: <20120912113425.GK20762@e-new.0x20.net> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Thomas Steen Rasmussen , freebsd-stable@FreeBSD.org Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 12:54:37 -0000 on 12/09/2012 14:34 Lars Engels said the following: > On Wed, Aug 22, 2012 at 08:02:12PM +0200, Thomas Steen Rasmussen wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 22-08-2012 18:52, Lars Engels wrote: >>> On Wed, Aug 22, 2012 at 02:47:09PM +0200, Thomas Steen Rasmussen wrote: >>>> >>>> On 22-08-2012 11:33, Lars Engels wrote: >>>>> >>>>> I have a T61 running 9.1-BETA1 (with PC-BSD). In most cases it is >>>>> booting fine, but from time to time it hangs at boot time but the last >>>>> lines are uhub0: ... to uhub4 >>>>> Is that the same or a different issue? >>>> Hello, >>>> >>>> I have that exact issue on an X301 after upgrading from 9.0 to >>>> 9-STABLE a little while ago. It feels like it happens mostly when >>>> rebooting from Windows to FreeBSD (dualboot machine), but I've >>>> seen it from a cold boot as well. I've never seen it twice in >>>> a row - turning the machine off and on again (by holding the >>>> power button down) and it boots normally the next time. >>>> >>>> I am willing to test patches or enable extra debugging, or >>>> help out any other way I can :) >>> >>> Have you ever seen that with verbose boot enabled? >> Hello, >> >> No, but I can boot verbosely the next times I boot and see if it comes up ? > > Meanwhile I found out what's the cause of it. On 9.x it only hung from > time to time, but I tried a few weeks old CURRENT and it hung at every > boot at the same time. > With enabled verbose boot it looked like this: > http://bsd-geek.de/FreeBSD/IMAG0190.jpg > > Then I removed the AC cable and booted from battery and that worked. So > it seems to me that some ACPI change in CURRENT made the situation even > worse. > Could you try to play with different eventtimer settings (preferably in current) ? You can use this thread / PR as a guide: http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus=14495 The place where boot stop looks suspiciously close to the place where timer interrupts should start driving the system. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 12:57:58 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C77191065678; Wed, 12 Sep 2012 12:57:58 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E55968FC1A; Wed, 12 Sep 2012 12:57:57 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA04544; Wed, 12 Sep 2012 15:57:53 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <505086D0.9080704@FreeBSD.org> Date: Wed, 12 Sep 2012 15:57:52 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120830 Thunderbird/15.0 MIME-Version: 1.0 To: Lars Engels References: <5007CFE6.6030808@intersonic.se> <500853DA.8050502@intersonic.se> <201207311632.30938.jhb@freebsd.org> <20120822093317.GW32916@e-new.0x20.net> <5034D4CD.4030301@gibfest.dk> <20120822165239.GX32916@e-new.0x20.net> <50351EA4.4040401@gibfest.dk> <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> In-Reply-To: <50508606.4040704@FreeBSD.org> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Thomas Steen Rasmussen , freebsd-stable@FreeBSD.org Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 12:57:58 -0000 on 12/09/2012 15:54 Andriy Gapon said the following: > on 12/09/2012 14:34 Lars Engels said the following: >> Meanwhile I found out what's the cause of it. On 9.x it only hung from >> time to time, but I tried a few weeks old CURRENT and it hung at every >> boot at the same time. >> With enabled verbose boot it looked like this: >> http://bsd-geek.de/FreeBSD/IMAG0190.jpg >> >> Then I removed the AC cable and booted from battery and that worked. So >> it seems to me that some ACPI change in CURRENT made the situation even >> worse. >> > > Could you try to play with different eventtimer settings (preferably in current) ? > You can use this thread / PR as a guide: > http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus=14495 > > The place where boot stop looks suspiciously close to the place where timer > interrupts should start driving the system. > Just in case. My point is that your system might using a timer that stops in certain (deeper) C-states. Generally FreeBSD disables deeper C-states in such a situation, but your system may require additional quirks. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 16:02:15 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91EAD106564A for ; Wed, 12 Sep 2012 16:02:15 +0000 (UTC) (envelope-from David.Boyd@insightbb.com) Received: from mail.insightbb.com (smtp2.insight.synacor.com [208.47.185.24]) by mx1.freebsd.org (Postfix) with ESMTP id 401F58FC08 for ; Wed, 12 Sep 2012 16:02:13 +0000 (UTC) X_CMAE_Category: 0,0 Undefined,Undefined X-CNFS-Analysis: v=1.1 cv=otbpgc9/MsxrXjQDYB5mdpLgueEeOusywo+Flwsf2UQ= c=1 sm=0 a=GrOWEK42gucA:10 a=jLN7EqiLvroA:10 a=8nJEP1OIZ-IA:10 a=RgBw9RmQAAAA:8 a=ycrxFw1kV7wmnZUCYJMA:9 a=wPNLvfGTeEIA:10 a=VWp6FqSG4Vb1RlmLnQz6YQ==:117 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Authentication-Results: smtp01.insight.synacor.com smtp.mail=David.Boyd@insightbb.com; spf=softfail; sender-id=softfail Authentication-Results: smtp01.insight.synacor.com header.from=David.Boyd@insightbb.com; sender-id=softfail Received-SPF: softfail (smtp01.insight.synacor.com: transitional domain insightbb.com does not designate 74.138.146.238 as permitted sender) Received: from [74.138.146.238] ([74.138.146.238:1556] helo=sneezy) by mail.insightbb.com (envelope-from ) (ecelerity 2.2.2.40 r(29895/29896)) with ESMTP id 57/24-13317-202B0505; Wed, 12 Sep 2012 12:02:12 -0400 From: "David Boyd" To: Date: Wed, 12 Sep 2012 12:02:10 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Importance: Normal Subject: systutils/arcconf errors on 9.x versions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 16:02:15 -0000 Back in July, this error was discussed briefly on the mailing list(s). It appears that a fix (r238182) was submitted for inclusion in 9.1 (early). This problem still appears in 9.1-RC1. Will the fix be included in 9.1-RELEASE (or better yet 9.1-RC2)? Thanks. David Boyd. ---------------------------------------------------------------------------- ------ 1st e-mail from pluknet responding to Sergey Kandaurov ---------------------------------------------------------------------------- ------ On 6 July 2012 14:49, Serg R wrote: > Hi! > > There is a problem with running the Adaptec Storage Manager in freebsd 9. > > # uname -a > FreeBSD sorgo 9.0-STABLE FreeBSD 9.0-STABLE #4: Thu May 31 13:39:39 SAMT 2012 root@sorgo:/usr/obj/usr/src/sys/SORGO amd64 > # portversion -v | grep arc > arcconf-v7.30.18837 = up-to-date with port > # arcconf > Undefined symbol "__collate_load_error" referenced from COPY relocation in /usr/local/sbin/arcconf This is probably because the private symbol __collate_load_error changed to macro (i.e. removed) in r235785 after 9.0. If so, it might brake those older binaries which rely on that symbol, though it's still defined in Symbol.map. Probably David Chisnall could further comment on this. -- wbr, pluknet ---------------------------------------------------------------------------- ------ 2nd e-mail from David Chisnall responding to Sergey Kandaurov ---------------------------------------------------------------------------- ------ On 6 Jul 2012, at 20:32, Sergey Kandaurov wrote: > This is probably because the private symbol __collate_load_error = changed > to macro (i.e. removed) in r235785 after 9.0. If so, it might brake = those > older binaries which rely on that symbol, though it's still defined in > Symbol.map. Probably David Chisnall could further comment on this. This was accidentally removed in the xlocale refactoring. I've restored = it in r238182 and CC'd re@ for permission to merge to the 9.1 release = branch. David= From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 17:25:27 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CE151065672; Wed, 12 Sep 2012 17:25:27 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id BE2BD8FC08; Wed, 12 Sep 2012 17:25:26 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id CB34C6A6001; Wed, 12 Sep 2012 19:25:25 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.5/8.14.5) with ESMTP id q8CHPPie057813; Wed, 12 Sep 2012 19:25:25 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.5/8.14.5/Submit) id q8CHPPNL056995; Wed, 12 Sep 2012 19:25:25 +0200 (CEST) (envelope-from lars) Date: Wed, 12 Sep 2012 19:25:25 +0200 From: Lars Engels To: Andriy Gapon Message-ID: <20120912172525.GU20762@e-new.0x20.net> References: <500853DA.8050502@intersonic.se> <201207311632.30938.jhb@freebsd.org> <20120822093317.GW32916@e-new.0x20.net> <5034D4CD.4030301@gibfest.dk> <20120822165239.GX32916@e-new.0x20.net> <50351EA4.4040401@gibfest.dk> <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="B2gdd0vZVCwxSorY" Content-Disposition: inline In-Reply-To: <50508606.4040704@FreeBSD.org> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.3-RELEASE-p2 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Thomas Steen Rasmussen , freebsd-stable@FreeBSD.org Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 17:25:27 -0000 --B2gdd0vZVCwxSorY Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote: > on 12/09/2012 14:34 Lars Engels said the following: > > On Wed, Aug 22, 2012 at 08:02:12PM +0200, Thomas Steen Rasmussen wrote: > >> > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> =20 > >> On 22-08-2012 18:52, Lars Engels wrote: > >>> On Wed, Aug 22, 2012 at 02:47:09PM +0200, Thomas Steen Rasmussen wrot= e: > >>>> > >>>> On 22-08-2012 11:33, Lars Engels wrote: > >>>>> > >>>>> I have a T61 running 9.1-BETA1 (with PC-BSD). In most cases it is > >>>>> booting fine, but from time to time it hangs at boot time but the l= ast > >>>>> lines are uhub0: ... to uhub4 > >>>>> Is that the same or a different issue? > >>>> Hello, > >>>> > >>>> I have that exact issue on an X301 after upgrading from 9.0 to > >>>> 9-STABLE a little while ago. It feels like it happens mostly when > >>>> rebooting from Windows to FreeBSD (dualboot machine), but I've > >>>> seen it from a cold boot as well. I've never seen it twice in > >>>> a row - turning the machine off and on again (by holding the > >>>> power button down) and it boots normally the next time. > >>>> > >>>> I am willing to test patches or enable extra debugging, or > >>>> help out any other way I can :) > >>> > >>> Have you ever seen that with verbose boot enabled? > >> Hello, > >> > >> No, but I can boot verbosely the next times I boot and see if it comes= up ? > >=20 > > Meanwhile I found out what's the cause of it. On 9.x it only hung from > > time to time, but I tried a few weeks old CURRENT and it hung at every > > boot at the same time. > > With enabled verbose boot it looked like this: > > http://bsd-geek.de/FreeBSD/IMAG0190.jpg > >=20 > > Then I removed the AC cable and booted from battery and that worked. So > > it seems to me that some ACPI change in CURRENT made the situation even > > worse. > >=20 >=20 > Could you try to play with different eventtimer settings (preferably in c= urrent) ? > You can use this thread / PR as a guide: > http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus=3D14495 >=20 > The place where boot stop looks suspiciously close to the place where tim= er > interrupts should start driving the system. Yes, that's it! Setting kern.eventtimer.timer=3D"i8254" let's the Thinkpad boot on CURRENT with the AC cable inserted. --B2gdd0vZVCwxSorY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlBQxYUACgkQKc512sD3afi5vACdHmZqfww6p+Y2UsFlzUZxqwKv 5a0AoJ8IVk1HFl5NOSlb5pGwUu/efOPF =Zg3/ -----END PGP SIGNATURE----- --B2gdd0vZVCwxSorY-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 17:30:46 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 416E9106564A; Wed, 12 Sep 2012 17:30:46 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 04DDE8FC0C; Wed, 12 Sep 2012 17:30:44 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA08176; Wed, 12 Sep 2012 20:30:37 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <5050C6BC.8000307@FreeBSD.org> Date: Wed, 12 Sep 2012 20:30:36 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120830 Thunderbird/15.0 MIME-Version: 1.0 To: Lars Engels References: <500853DA.8050502@intersonic.se> <201207311632.30938.jhb@freebsd.org> <20120822093317.GW32916@e-new.0x20.net> <5034D4CD.4030301@gibfest.dk> <20120822165239.GX32916@e-new.0x20.net> <50351EA4.4040401@gibfest.dk> <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> <20120912172525.GU20762@e-new.0x20.net> In-Reply-To: <20120912172525.GU20762@e-new.0x20.net> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Alexander Motin , freebsd-stable@FreeBSD.org Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 17:30:46 -0000 on 12/09/2012 20:25 Lars Engels said the following: > On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote: >> Could you try to play with different eventtimer settings (preferably in current) ? >> You can use this thread / PR as a guide: >> http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus=14495 >> >> The place where boot stop looks suspiciously close to the place where timer >> interrupts should start driving the system. > > Yes, that's it! > Setting kern.eventtimer.timer="i8254" let's the Thinkpad boot on > CURRENT with the AC cable inserted. > Please share your sysctl kern.eventtimer output with Alexander. He will probably ask for some additional information :-) Thanks for testing! -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 17:46:51 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0752A106564A; Wed, 12 Sep 2012 17:46:51 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mx1.freebsd.org (Postfix) with ESMTP id 86EF38FC15; Wed, 12 Sep 2012 17:46:50 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 83A886A6001; Wed, 12 Sep 2012 19:46:49 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.5/8.14.5) with ESMTP id q8CHknHP040326; Wed, 12 Sep 2012 19:46:49 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.5/8.14.5/Submit) id q8CHknMl039075; Wed, 12 Sep 2012 19:46:49 +0200 (CEST) (envelope-from lars) Date: Wed, 12 Sep 2012 19:46:49 +0200 From: Lars Engels To: Andriy Gapon Message-ID: <20120912174649.GV20762@e-new.0x20.net> References: <201207311632.30938.jhb@freebsd.org> <20120822093317.GW32916@e-new.0x20.net> <5034D4CD.4030301@gibfest.dk> <20120822165239.GX32916@e-new.0x20.net> <50351EA4.4040401@gibfest.dk> <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> <20120912172525.GU20762@e-new.0x20.net> <5050C6BC.8000307@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QbLupA6O8PZD6SZa" Content-Disposition: inline In-Reply-To: <5050C6BC.8000307@FreeBSD.org> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.3-RELEASE-p2 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Alexander Motin , freebsd-stable@FreeBSD.org Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 17:46:51 -0000 --QbLupA6O8PZD6SZa Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote: > on 12/09/2012 20:25 Lars Engels said the following: > > On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote: > >> Could you try to play with different eventtimer settings (preferably i= n current) ? > >> You can use this thread / PR as a guide: > >> http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus=3D144= 95 > >> > >> The place where boot stop looks suspiciously close to the place where = timer > >> interrupts should start driving the system. > >=20 > > Yes, that's it! > > Setting kern.eventtimer.timer=3D"i8254" let's the Thinkpad boot on > > CURRENT with the AC cable inserted. > >=20 >=20 > Please share your sysctl kern.eventtimer output with Alexander. > He will probably ask for some additional information :-) >=20 > Thanks for testing! lars@pts/12 > cat kern.eventtimer_10_r238992M.txt kern.eventtimer.choice: HPET(450) HPET1(440) HPET2(440) LAPIC(400) i8254(100) RTC(0) kern.eventtimer.et.LAPIC.flags: 15 kern.eventtimer.et.LAPIC.frequency: 0 kern.eventtimer.et.LAPIC.quality: 400 kern.eventtimer.et.i8254.flags: 1 kern.eventtimer.et.i8254.frequency: 1193182 kern.eventtimer.et.i8254.quality: 100 kern.eventtimer.et.HPET.flags: 3 kern.eventtimer.et.HPET.frequency: 14318180 kern.eventtimer.et.HPET.quality: 450 kern.eventtimer.et.HPET1.flags: 3 kern.eventtimer.et.HPET1.frequency: 14318180 kern.eventtimer.et.HPET1.quality: 440 kern.eventtimer.et.HPET2.flags: 3 kern.eventtimer.et.HPET2.frequency: 14318180 kern.eventtimer.et.HPET2.quality: 440 kern.eventtimer.et.RTC.flags: 17 kern.eventtimer.et.RTC.frequency: 32768 kern.eventtimer.et.RTC.quality: 0 kern.eventtimer.periodic: 1 kern.eventtimer.timer: i8254 kern.eventtimer.activetick: 1 kern.eventtimer.idletick: 0 kern.eventtimer.singlemul: 2 =20 lars@pts/12 > cat kern.eventtimer_9.1-RC1.txt kern.eventtimer.choice: HPET(450) HPET1(440) HPET2(440) LAPIC(400) i8254(100) RTC(0) kern.eventtimer.et.LAPIC.flags: 15 kern.eventtimer.et.LAPIC.frequency: 0 kern.eventtimer.et.LAPIC.quality: 400 kern.eventtimer.et.i8254.flags: 1 kern.eventtimer.et.i8254.frequency: 1193182 kern.eventtimer.et.i8254.quality: 100 kern.eventtimer.et.HPET.flags: 3 kern.eventtimer.et.HPET.frequency: 14318180 kern.eventtimer.et.HPET.quality: 450 kern.eventtimer.et.HPET1.flags: 3 kern.eventtimer.et.HPET1.frequency: 14318180 kern.eventtimer.et.HPET1.quality: 440 kern.eventtimer.et.HPET2.flags: 3 kern.eventtimer.et.HPET2.frequency: 14318180 kern.eventtimer.et.HPET2.quality: 440 kern.eventtimer.et.RTC.flags: 17 kern.eventtimer.et.RTC.frequency: 32768 kern.eventtimer.et.RTC.quality: 0 kern.eventtimer.periodic: 0 kern.eventtimer.timer: HPET kern.eventtimer.activetick: 1 kern.eventtimer.idletick: 0 kern.eventtimer.singlemul: 2 lars@pts/12 > diff -u kern.eventtimer_9.1-RC1.txt kern.eventtimer_10_r238992M.txt --- kern.eventtimer_9.1-RC1.txt 2012-09-12 19:43:58.000000000 +0200 +++ kern.eventtimer_10_r238992M.txt 2012-09-12 19:43:58.000000000 +0200 @@ -17,8 +17,8 @@ kern.eventtimer.et.RTC.flags: 17 kern.eventtimer.et.RTC.frequency: 32768 kern.eventtimer.et.RTC.quality: 0 -kern.eventtimer.periodic: 0 -kern.eventtimer.timer: HPET +kern.eventtimer.periodic: 1 +kern.eventtimer.timer: i8254 kern.eventtimer.activetick: 1 kern.eventtimer.idletick: 0 kern.eventtimer.singlemul: 2 --QbLupA6O8PZD6SZa Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlBQyokACgkQKc512sD3afiy1gCgnhtMShaCYkIwdNP47i8k6q3z azAAniK9kEkd7cxwlQLWqVvfZWbIyqAN =EYGp -----END PGP SIGNATURE----- --QbLupA6O8PZD6SZa-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 18:58:38 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3A301065670; Wed, 12 Sep 2012 18:58:38 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id E666E8FC16; Wed, 12 Sep 2012 18:58:37 +0000 (UTC) Received: by lage12 with SMTP id e12so1648651lag.13 for ; Wed, 12 Sep 2012 11:58:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=3XP3DXLUF1IDcnjoO0ZQXqLFNcfVgT3ZC1zJBRtZIcA=; b=Rq9sVvPUGsI+6Mng2WXUY0r0j0hutLB09LuNXvfUbUT006qBXhbnBfIPbWNZ06TrhW YD+dqBqfWA89eGs4l5Jag1vy6hhbgVWbyrTiogUyoUmxVP+Uf+hY492GnvoQT8Ptir50 SCaAeQDXbeb2VB15ThSNBSBIP6+9erTdPUe/m8nLM5Ipa4TYkulNWkmzrKelfm06iJnn ghZtHr9V13g5zNy6eJKwEBntPnfAZn9lTFrWpNEN1lFNF2szGQ1r8ZvkjNSemnO4NL5d M/yBwkIRYgVSyt9ABLfkzhLMDsoZG3Go+N5hXbLxj0wXjZZs5yUHvZYxt50c7D0uizl7 GUFw== Received: by 10.112.26.197 with SMTP id n5mr41990lbg.18.1347476315503; Wed, 12 Sep 2012 11:58:35 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id g6sm4127145lby.0.2012.09.12.11.58.33 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 12 Sep 2012 11:58:34 -0700 (PDT) Sender: Alexander Motin Message-ID: <5050DB57.90903@FreeBSD.org> Date: Wed, 12 Sep 2012 21:58:31 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120628 Thunderbird/13.0.1 MIME-Version: 1.0 To: Lars Engels References: <201207311632.30938.jhb@freebsd.org> <20120822093317.GW32916@e-new.0x20.net> <5034D4CD.4030301@gibfest.dk> <20120822165239.GX32916@e-new.0x20.net> <50351EA4.4040401@gibfest.dk> <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> <20120912172525.GU20762@e-new.0x20.net> <5050C6BC.8000307@FreeBSD.org> <20120912174649.GV20762@e-new.0x20.net> In-Reply-To: <20120912174649.GV20762@e-new.0x20.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, Andriy Gapon Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 18:58:38 -0000 On 12.09.2012 20:46, Lars Engels wrote: > On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote: >> on 12/09/2012 20:25 Lars Engels said the following: >>> On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote: >>>> Could you try to play with different eventtimer settings (preferably in current) ? >>>> You can use this thread / PR as a guide: >>>> http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus=14495 >>>> >>>> The place where boot stop looks suspiciously close to the place where timer >>>> interrupts should start driving the system. >>> >>> Yes, that's it! >>> Setting kern.eventtimer.timer="i8254" let's the Thinkpad boot on >>> CURRENT with the AC cable inserted. >>> >> >> Please share your sysctl kern.eventtimer output with Alexander. >> He will probably ask for some additional information :-) Sorry if I've missed, but it would be useful to see verbose dmesg in situation where system couldn't boot without switching eventtimer. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 19:22:54 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 67A54106564A; Wed, 12 Sep 2012 19:22:54 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mx1.giulioferro.ch (mx1.giulioferro.ch [217.150.252.208]) by mx1.freebsd.org (Postfix) with ESMTP id 0E0D68FC08; Wed, 12 Sep 2012 19:22:53 +0000 (UTC) Received: from mailscan.giulioferro.ch (unknown [192.168.115.2]) by mx1.giulioferro.ch (Postfix) with ESMTP id 9ACDC7770F; Wed, 12 Sep 2012 21:22:52 +0200 (CEST) X-Virus-Scanned: amavisd-new at example.com Received: from mx1.giulioferro.ch ([192.168.114.4]) by mailscan.giulioferro.ch (mailscan.giulioferro.ch [192.168.115.2]) (amavisd-new, port 10024) with ESMTP id w-DwA_sevC_M; Wed, 12 Sep 2012 21:22:49 +0200 (CEST) Received: from mail.zirakzigil.org (net-93-70-48-129.cust.dsl.vodafone.it [93.70.48.129]) by mx1.giulioferro.ch (Postfix) with ESMTP id 9767877701; Wed, 12 Sep 2012 21:22:49 +0200 (CEST) Received: from ext.zirakzigil.org (unknown [192.168.1.2]) by mail.zirakzigil.org (Postfix) with ESMTP id 4725B19CA3A; Wed, 12 Sep 2012 09:37:05 +0200 (CEST) X-Virus-Scanned: amavisd-new at zirakzigil.org Received: from mail.zirakzigil.org ([192.168.1.2]) by ext.zirakzigil.org (ext.zirakzigil.org [192.168.1.2]) (amavisd-new, port 10024) with ESMTP id gl2UONg6ebwH; Wed, 12 Sep 2012 09:37:04 +0200 (CEST) Received: from [192.168.231.11] (ext [192.168.1.2]) (Authenticated sender: auryn@zirakzigil.org) by mail.zirakzigil.org (Postfix) with ESMTPA id C29B919CA35; Wed, 12 Sep 2012 09:37:03 +0200 (CEST) Message-ID: <5050E107.6090403@zirakzigil.org> Date: Wed, 12 Sep 2012 21:22:47 +0200 From: Giulio Ferro User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Freddie Cash References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 19:22:54 -0000 On 09/11/2012 11:34 PM, Freddie Cash wrote: > > On Sep 11, 2012 2:12 PM, "Giulio Ferro" > wrote: > > > > Well, there definitely seems to be a problem with igb and lagg. > > > > igb alone works as it should, but doesn't seem to work properly in lagg. > > > > To be sure I started from scratch from a 9.0 release with nothing but: > > > > /etc/rc.conf > > --------------------------------------------------- > > ifconfig_igb0="inet ..." > > > > ifconfig_igb1="up" > > ifconfig_igb2="up" > > ifconfig_igb3="up" > > > > cloned_interfaces="lagg0" > > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport > igb3 192.168.x.x/24" > > > > sshd_enable="YES" > > --------------------------------------------------- > > > > This doesn't even manage to start sshd, it just hangs there at boot. > > > > Disabling lagg configuration everything works correctly. > > > > Just curious: does it work if you split the lagg configuration from the > IP config: > > ifconfig_lagg0="laggproto ..." > ifconfig_lagg0_alias0="inet 192..." > > I've had problems in the past with cloned interfaces not working right > if you do everything in one ifconfig line. Never spent much time > debugging it, though, as the split config always worked. > Nope, doesn't work. It always hangs at boot and cannot be killed (freebsd 9 RELEASE) I still think the problem is with lagg and / or igb. Someone should look into it. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 19:40:49 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EC7B1065670; Wed, 12 Sep 2012 19:40:49 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 703B28FC16; Wed, 12 Sep 2012 19:40:47 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so1743429lbb.13 for ; Wed, 12 Sep 2012 12:40:47 -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=MCU/TdbCD0k8aHp6hnjm73CrPAunzIOHeoIaeSbkBb0=; b=f9pf20OiPoJSPxTSjt8ilSVbZ+0ojA2KP6uVOYtX+CnydaXLUFru31Z/AtHeZaCA5B GBD/njej1NIhdvnCcbMwm39wt0OAgU4UGRS0//mIP/4XclFIIBKx/lOkC06SrUU7A0C+ RTbnijDlXxc4mdJaTQrE60LKuSUNMNfj7/WMBuPBbFD9MkDHecgOrm2H2N0UujuQn9GS 8f2ah1M2W/IqURMzoux+f5/B8O3i8o1+1RTFEBrjqDZadMxvYgnVuTYhN2PUt8GL7YmT xfAfVYYFR0UXuM+HVw1ejCFqOjGViwMgU8rEyixFL1mwydjW+X7zf7fdr0YSBvgFeAD9 ZFIg== MIME-Version: 1.0 Received: by 10.112.26.38 with SMTP id i6mr51135lbg.76.1347478846941; Wed, 12 Sep 2012 12:40:46 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Wed, 12 Sep 2012 12:40:46 -0700 (PDT) In-Reply-To: <5050E107.6090403@zirakzigil.org> References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> Date: Wed, 12 Sep 2012 12:40:46 -0700 Message-ID: From: Freddie Cash To: Giulio Ferro Content-Type: text/plain; charset=UTF-8 Cc: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 19:40:49 -0000 On Wed, Sep 12, 2012 at 12:22 PM, Giulio Ferro wrote: > On 09/11/2012 11:34 PM, Freddie Cash wrote: >> >> On Sep 11, 2012 2:12 PM, "Giulio Ferro" > > wrote: >> > >> > Well, there definitely seems to be a problem with igb and lagg. >> > >> > igb alone works as it should, but doesn't seem to work properly in >> lagg. >> > >> > To be sure I started from scratch from a 9.0 release with nothing but: >> > >> > /etc/rc.conf >> > --------------------------------------------------- >> > ifconfig_igb0="inet ..." >> > >> > ifconfig_igb1="up" >> > ifconfig_igb2="up" >> > ifconfig_igb3="up" >> > >> > cloned_interfaces="lagg0" >> > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport >> igb3 192.168.x.x/24" >> > >> > sshd_enable="YES" >> > --------------------------------------------------- >> > >> > This doesn't even manage to start sshd, it just hangs there at boot. >> > >> > Disabling lagg configuration everything works correctly. >> > >> >> Just curious: does it work if you split the lagg configuration from the >> IP config: >> >> ifconfig_lagg0="laggproto ..." >> ifconfig_lagg0_alias0="inet 192..." >> >> I've had problems in the past with cloned interfaces not working right >> if you do everything in one ifconfig line. Never spent much time >> debugging it, though, as the split config always worked. >> > > Nope, doesn't work. It always hangs at boot and cannot be killed (freebsd 9 > RELEASE) > > I still think the problem is with lagg and / or igb. > Someone should look into it. Thanks for checking. I've used lagg(4) with igb, just not on 9.x. You're right, it seems to be pointing to the igb(4) driver in 9.x compared to < 9.0. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 19:58:23 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5067E106566B; Wed, 12 Sep 2012 19:58:23 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id D21368FC0A; Wed, 12 Sep 2012 19:58:22 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 153536A6001; Wed, 12 Sep 2012 21:58:22 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.5/8.14.5) with ESMTP id q8CJwLVs061986; Wed, 12 Sep 2012 21:58:21 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.5/8.14.5/Submit) id q8CJwLRB061081; Wed, 12 Sep 2012 21:58:21 +0200 (CEST) (envelope-from lars) Date: Wed, 12 Sep 2012 21:58:21 +0200 From: Lars Engels To: Alexander Motin Message-ID: <20120912195821.GW20762@e-new.0x20.net> References: <20120822093317.GW32916@e-new.0x20.net> <5034D4CD.4030301@gibfest.dk> <20120822165239.GX32916@e-new.0x20.net> <50351EA4.4040401@gibfest.dk> <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> <20120912172525.GU20762@e-new.0x20.net> <5050C6BC.8000307@FreeBSD.org> <20120912174649.GV20762@e-new.0x20.net> <5050DB57.90903@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NN5Sl4cwfoGvUMzV" Content-Disposition: inline In-Reply-To: <5050DB57.90903@FreeBSD.org> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.3-RELEASE-p2 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@FreeBSD.org, Andriy Gapon Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 19:58:23 -0000 --NN5Sl4cwfoGvUMzV Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 12, 2012 at 09:58:31PM +0300, Alexander Motin wrote: > On 12.09.2012 20:46, Lars Engels wrote: > > On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote: > >> on 12/09/2012 20:25 Lars Engels said the following: > >>> On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote: > >>>> Could you try to play with different eventtimer settings (preferably= in current) ? > >>>> You can use this thread / PR as a guide: > >>>> http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus=3D1= 4495 > >>>> > >>>> The place where boot stop looks suspiciously close to the place wher= e timer > >>>> interrupts should start driving the system. > >>> > >>> Yes, that's it! > >>> Setting kern.eventtimer.timer=3D"i8254" let's the Thinkpad boot on > >>> CURRENT with the AC cable inserted. > >>> > >> > >> Please share your sysctl kern.eventtimer output with Alexander. > >> He will probably ask for some additional information :-) >=20 > Sorry if I've missed, but it would be useful to see verbose dmesg in=20 > situation where system couldn't boot without switching eventtimer. No problem. See: http://bsd-geek.de/FreeBSD/IMAG0190.jpg --NN5Sl4cwfoGvUMzV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlBQ6V0ACgkQKc512sD3afgGKACfWwqGNyhNlxCnlDNWX0q+dJJV ULcAoI6OWDt5HglF3Se5ix92yfuZ3A6o =CcIW -----END PGP SIGNATURE----- --NN5Sl4cwfoGvUMzV-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 20:08:31 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C5B9106564A; Wed, 12 Sep 2012 20:08:31 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6ABF08FC15; Wed, 12 Sep 2012 20:08:30 +0000 (UTC) Received: by lage12 with SMTP id e12so1710642lag.13 for ; Wed, 12 Sep 2012 13:08:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=5Dq0lrqZwWhGPEGjdfCzfUXkxJVFUnX+LhCX3bpoHAg=; b=rjMG2dn5CKr8oYbPcOLUfLDvo6d0bG8CUh7I6JPRpD5kMIHROj8X33hTTL6/LEeJ76 Vb5zBaVFuG7fVSKiogt6QR3DDA+hoJf8H4zg9WS21UiKaCfY6tQTUdlh7B3qEosav8BA nhgTPu/OA7uopcSK42YqJJSlqYAJ0dMXLrq2sKqwU08CNlZcwF9jR/26HjUZ6ZIa6Pon ExPvlfnhWFFE6n5T3BYq/VxjHceBqoDKmqSlyaZW9M0o4JAdoys/e7RdYA40Si6RFMt5 u7AnxiyQKI/0ihORrO5KK4DQnzkigwDMvgI8eWh4j2sfEUmgZg3dazinCSMSHqcF0pTs 0ikQ== Received: by 10.112.88.2 with SMTP id bc2mr82930lbb.61.1347480508898; Wed, 12 Sep 2012 13:08:28 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id u10sm5483178lbf.11.2012.09.12.13.08.27 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 12 Sep 2012 13:08:27 -0700 (PDT) Sender: Alexander Motin Message-ID: <5050EBB9.7040202@FreeBSD.org> Date: Wed, 12 Sep 2012 23:08:25 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120628 Thunderbird/13.0.1 MIME-Version: 1.0 To: Lars Engels References: <20120822093317.GW32916@e-new.0x20.net> <5034D4CD.4030301@gibfest.dk> <20120822165239.GX32916@e-new.0x20.net> <50351EA4.4040401@gibfest.dk> <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> <20120912172525.GU20762@e-new.0x20.net> <5050C6BC.8000307@FreeBSD.org> <20120912174649.GV20762@e-new.0x20.net> <5050DB57.90903@FreeBSD.org> <20120912195821.GW20762@e-new.0x20.net> In-Reply-To: <20120912195821.GW20762@e-new.0x20.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, Andriy Gapon Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 20:08:31 -0000 On 12.09.2012 22:58, Lars Engels wrote: > On Wed, Sep 12, 2012 at 09:58:31PM +0300, Alexander Motin wrote: >> On 12.09.2012 20:46, Lars Engels wrote: >>> On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote: >>>> on 12/09/2012 20:25 Lars Engels said the following: >>>>> On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote: >>>>>> Could you try to play with different eventtimer settings (preferably in current) ? >>>>>> You can use this thread / PR as a guide: >>>>>> http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus=14495 >>>>>> >>>>>> The place where boot stop looks suspiciously close to the place where timer >>>>>> interrupts should start driving the system. >>>>> >>>>> Yes, that's it! >>>>> Setting kern.eventtimer.timer="i8254" let's the Thinkpad boot on >>>>> CURRENT with the AC cable inserted. >>>>> >>>> >>>> Please share your sysctl kern.eventtimer output with Alexander. >>>> He will probably ask for some additional information :-) >> >> Sorry if I've missed, but it would be useful to see verbose dmesg in >> situation where system couldn't boot without switching eventtimer. > > No problem. See: http://bsd-geek.de/FreeBSD/IMAG0190.jpg No, I've seen that one and I don't mean it. I mean full verbose dmesg of successful boot in conditions where system was not booting before without setting kern.eventtimer.timer="i8254". -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 20:11:08 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 228241065670 for ; Wed, 12 Sep 2012 20:11:08 +0000 (UTC) (envelope-from jas@cse.yorku.ca) Received: from bronze.cs.yorku.ca (bronze.cs.yorku.ca [130.63.95.34]) by mx1.freebsd.org (Postfix) with ESMTP id E9B5C8FC0C for ; Wed, 12 Sep 2012 20:11:07 +0000 (UTC) Received: from [130.63.97.125] (ident=jas) by bronze.cs.yorku.ca with esmtp (Exim 4.76) (envelope-from ) id 1TBsyF-0003ES-FV for freebsd-stable@freebsd.org; Wed, 12 Sep 2012 15:51:35 -0400 Message-ID: <5050E7C7.5030607@cse.yorku.ca> Date: Wed, 12 Sep 2012 15:51:35 -0400 From: Jason Keltz User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.7) Gecko/20120824 Thunderbird/10.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.0 X-Spam-Level: - X-Spam-Report: Content preview: Hi. I'm running the 9.1-RC1 release. At the end of the boot sequence, I see: [...] Content analysis details: (-1.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SHORTCIRCUIT Not all rules were run, due to a shortcircuited rule -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP Subject: 9.1-rc1 cd/mps error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 20:11:08 -0000 Hi. I'm running the 9.1-RC1 release. At the end of the boot sequence, I see: mps0: mpssas_scsiio_timeout checking sc 0xffffff8000759000 cm 0xffffff8000784380 (probe19:mps0:0:19:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 length 0 SMID 240 command timeout cm 0xffffff8000784380 ccb 0xfffffe0006918000 mps0: mpssas_alloc_tm freezing simq mps0: timedout cm 0xffffff8000784380 allocated tm 0xffffff8000771148 (probe19:mps0:0:19:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 length 0 SMID 240 completed timedout cm 0xffffff8000784380 ccb 0xfffffe0006918000 during recovery ioc 8048 scsi 0 state c xfer 0 (noperiph:mps0:0:19:0): SMID 1 abort TaskMID 240 status 0x0 code 0x0 count 1 (noperiph:mps0:0:19:0): SMID 1 finished recovery after aborting TaskMID 240 mps0: mpssas_free_tm releasing simq (I had a similar error with a hang in 9.0 -- couldn't get out of it .. at least under 9.1 it doesn't hang). ... Can someone help me to figure out what this means? Should I be alarmed? The system has an Intel S3000AH server board with an LSI 9211-8i card with SAS2008 chipset, running IT firmware. It is connected to an older Chenbro CK12803 expander card which is connected to the 16 disk ports in the AIC RMC3E2-XPSS 3U chassis. The disks are all recognized -- da0 is a 1 TB, da1-11 are 2 TB disks. Any ideas? Thanks .. Jason Keltz From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 20:48:02 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 361081065688; Wed, 12 Sep 2012 20:48:02 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id BD0EA8FC0A; Wed, 12 Sep 2012 20:48:01 +0000 (UTC) Received: by vbmv11 with SMTP id v11so3390453vbm.13 for ; Wed, 12 Sep 2012 13:48:00 -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=QWfBuoN5GFFDS4W+f1pX1rw61Bd1ik/uM/Y1yeVdamA=; b=HbdchFnKGOlFptRx274d1YTtQCyaPEZMjIREqCBXqVbIEIkt2dkygFi+Leg4+H7rg6 zaFIWoFuDyEB7k5GFccfBOCZ9rhhQF8X6HJsVIrOqZMDENM27AQlmhtcNI+zXKIhVfjD B3lD971pv4elt33ezBfuFO93bs7SHWwHZ3qC1HawVruvhNC/GduuD+rss3N5Io708qys zVz9GcAuksaFDu0mp24dLm+u7zdJtRkwyuUjKHiD+qGveNOvIrqjsX0WbbOLjZmpAy2C C+JmmSm4buc4dYsB8vxQbRxcHrrVRezBjnAMvKENus3ldIppDRSJMLo17hnZq1C7Tw/T qyZA== MIME-Version: 1.0 Received: by 10.52.240.171 with SMTP id wb11mr23701811vdc.86.1347482880727; Wed, 12 Sep 2012 13:48:00 -0700 (PDT) Received: by 10.58.68.8 with HTTP; Wed, 12 Sep 2012 13:48:00 -0700 (PDT) In-Reply-To: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> Date: Wed, 12 Sep 2012 13:48:00 -0700 Message-ID: From: Jack Vogel To: Freddie Cash Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Giulio Ferro , "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 20:48:02 -0000 On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash wrote: > On Wed, Sep 12, 2012 at 12:22 PM, Giulio Ferro > wrote: > > On 09/11/2012 11:34 PM, Freddie Cash wrote: > >> > >> On Sep 11, 2012 2:12 PM, "Giulio Ferro" >> > wrote: > >> > > >> > Well, there definitely seems to be a problem with igb and lagg. > >> > > >> > igb alone works as it should, but doesn't seem to work properly in > >> lagg. > >> > > >> > To be sure I started from scratch from a 9.0 release with nothing > but: > >> > > >> > /etc/rc.conf > >> > --------------------------------------------------- > >> > ifconfig_igb0="inet ..." > >> > > >> > ifconfig_igb1="up" > >> > ifconfig_igb2="up" > >> > ifconfig_igb3="up" > >> > > >> > cloned_interfaces="lagg0" > >> > ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport > >> igb3 192.168.x.x/24" > >> > > >> > sshd_enable="YES" > >> > --------------------------------------------------- > >> > > >> > This doesn't even manage to start sshd, it just hangs there at boot. > >> > > >> > Disabling lagg configuration everything works correctly. > >> > > >> > >> Just curious: does it work if you split the lagg configuration from the > >> IP config: > >> > >> ifconfig_lagg0="laggproto ..." > >> ifconfig_lagg0_alias0="inet 192..." > >> > >> I've had problems in the past with cloned interfaces not working right > >> if you do everything in one ifconfig line. Never spent much time > >> debugging it, though, as the split config always worked. > >> > > > > Nope, doesn't work. It always hangs at boot and cannot be killed > (freebsd 9 > > RELEASE) > > > > I still think the problem is with lagg and / or igb. > > Someone should look into it. > > Thanks for checking. I've used lagg(4) with igb, just not on 9.x. > > You're right, it seems to be pointing to the igb(4) driver in 9.x > compared to < 9.0. > > How do you determine that since it doesn't happen without lagg? I've no reports of igb hanging otherwise and its being used extensively. Jack > -- > Freddie Cash > fjwcash@gmail.com > _______________________________________________ > 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 Sep 12 20:51:53 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 552B91065676; Wed, 12 Sep 2012 20:51:53 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 941958FC16; Wed, 12 Sep 2012 20:51:51 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so1803414lbb.13 for ; Wed, 12 Sep 2012 13:51:50 -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=wU0OcIooFPH78oJ1J2rmrS2zFfBH7vD1pI/uMxGf99E=; b=VRxrrkENfW1MLknD8Qxb1/aKCmhkikGKzGErVIjlu16A2fPd+/bAVROCncO6/EoeGX WdN2fzTnTqUpY4497Xer8/WA7ufbOO8mcFrf6x0LjLwf+QKw29JB9CsLofqJu8LNNaWD s4R4pOhMAT+oPNgO91GoslmGdygfH68JwNgl00TYrJCZ2IWl540s0e4bGGiNTYFY93Ma OygvdvOOj46y3kpzO9u2KJ34A5y2EChX2hmy/jFIySNmKw5EgOg+dyTjEy3SgelUaBF1 mMmJdOAt+Y+1TWXQye+BbVzA0WEEH8rBnj8vnZYszdLwp541uMyzQgQUSJTr+ahWWFe8 uUuA== MIME-Version: 1.0 Received: by 10.152.103.146 with SMTP id fw18mr20159796lab.30.1347483110583; Wed, 12 Sep 2012 13:51:50 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Wed, 12 Sep 2012 13:51:50 -0700 (PDT) In-Reply-To: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> Date: Wed, 12 Sep 2012 13:51:50 -0700 Message-ID: From: Freddie Cash To: Jack Vogel Content-Type: text/plain; charset=UTF-8 Cc: freebsd-net@freebsd.org, Giulio Ferro , "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 20:51:53 -0000 On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel wrote: > On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash wrote: >> Thanks for checking. I've used lagg(4) with igb, just not on 9.x. >> >> You're right, it seems to be pointing to the igb(4) driver in 9.x >> compared to < 9.0. >> > How do you determine that since it doesn't happen without lagg? I've no > reports of igb hanging otherwise and its being used extensively. Well, I did say "seems to". :) igb+lagg worked for us on 8.3. Haven't tried it since moving to 9.0 and 9-STABLE on those three boxes. igb+lagg doesn't work for him on 9.0. Although, I don't recall if non-LACP options were tried earlier in this thread, or if it's just the LACP mode that's failing. If one mode works (say failover) and LACP mode doesn't, that "seems to" point to lagg. I'll see if I can free up an igb port on my 9.0 and 9-STABLE boxes to test this with as well. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 20:56:09 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38509106570E; Wed, 12 Sep 2012 20:56:09 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id C1A298FC12; Wed, 12 Sep 2012 20:56:08 +0000 (UTC) Received: by vbmv11 with SMTP id v11so3401847vbm.13 for ; Wed, 12 Sep 2012 13:56:07 -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=4LOrDZJlXQPYd6JhyriS2t6Km3HNwBcZqqYlu+84agQ=; b=Do814Nz6fkDQKa6kmyS7oM8r6wltyW/fEbJgxOzBmsethLVb3nSp26/0dZv5utYeRu vYnQpbhl+PNJCZ4TLkckev9I73VJth0OEPDY9kaGjaUerCBnj/Lwe67LJmTsnKK2qZu3 UT607aA5ZotgNikgcZx8aWr62wYhFaZ4l5Amap//vcILtG5ZSkjdUavdlJg/yo0xss6K Lc4+xDqHutMqMt8+gtvfz/Ahxg3YuADApTFkZ0odv1+xBjZXnX0blIXeeqAkzR+deUtO 0rD+jpyp/pbOVsIiXZ8v1qAYevmUDRcfdr+M3WSv4wQHwaWqyfA1N5j5NGxLYStH8TUo REgQ== MIME-Version: 1.0 Received: by 10.220.225.194 with SMTP id it2mr29861852vcb.32.1347483367823; Wed, 12 Sep 2012 13:56:07 -0700 (PDT) Received: by 10.58.68.8 with HTTP; Wed, 12 Sep 2012 13:56:07 -0700 (PDT) In-Reply-To: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> Date: Wed, 12 Sep 2012 13:56:07 -0700 Message-ID: From: Jack Vogel To: Freddie Cash Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Giulio Ferro , "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 20:56:09 -0000 On Wed, Sep 12, 2012 at 1:51 PM, Freddie Cash wrote: > On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel wrote: > > On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash > wrote: > >> Thanks for checking. I've used lagg(4) with igb, just not on 9.x. > >> > >> You're right, it seems to be pointing to the igb(4) driver in 9.x > >> compared to < 9.0. > >> > > How do you determine that since it doesn't happen without lagg? I've no > > reports of igb hanging otherwise and its being used extensively. > > Well, I did say "seems to". :) > > igb+lagg worked for us on 8.3. Haven't tried it since moving to 9.0 > and 9-STABLE on those three boxes. > > igb+lagg doesn't work for him on 9.0. Although, I don't recall if > non-LACP options were tried earlier in this thread, or if it's just > the LACP mode that's failing. If one mode works (say failover) and > LACP mode doesn't, that "seems to" point to lagg. > > I'll see if I can free up an igb port on my 9.0 and 9-STABLE boxes to > test this with as well. > > I wouldn't use 9.0, go with 9.1 RC or whatever has the latest igb code, if you see the issue there I can see about getting some time to look into it here. Jack From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 21:06:15 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 46E491065686 for ; Wed, 12 Sep 2012 21:06:15 +0000 (UTC) (envelope-from jbeich@tormail.org) Received: from cpanel.centralhosts.net (cpanel.centralhosts.net [66.55.76.125]) by mx1.freebsd.org (Postfix) with ESMTP id 15F408FC1D for ; Wed, 12 Sep 2012 21:06:13 +0000 (UTC) Received: from ns4000818.ip-198-245-63.net ([198.245.63.147]:34145 helo=internal.tormail.org) by cpanel.centralhosts.net with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.77) (envelope-from ) id 1TAbiT-0000ma-Oo; Sun, 09 Sep 2012 03:14:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tormail.org; s=tm; h=Message-Id:X-TorMail-User:Content-Type:MIME-Version:References:Date:In-Reply-To:Subject:Cc:To:From; bh=TvgxCGKH83aN137W7k0W0XjRqB8hG/eiFjYxNNL7c9Y=; b=Ughga4ymrZ3VfRuVOGG2HIoZfc3JPNDr+xTeEDuaR3TwYtyYdveBLsNQLAPzxIyNZoLoPum+vobP0Rh4iB0GK4m7IdWGaLCbUUyzffESscdDEslV1q/zik8NOsJ5akZ7SB6RavNn187kvCI+BqDkAmB7mJ7MI8/ghm4bpy3ndnk=; Received: from jbeich by internal.tormail.org with local (Exim 4.63) (envelope-from ) id 1TAbjH-00087E-6x; Sun, 09 Sep 2012 07:14:57 +0000 From: Jan Beich To: Zhihao Yuan In-Reply-To: (Zhihao Yuan's message of "Sat, 8 Sep 2012 07:27:59 -0500") Date: Sun, 09 Sep 2012 00:14:24 -0700 References: <504B206E.7000409@gmx.us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-TorMail-User: jbeich Message-Id: <1TAbjH-00087E-6x@internal.tormail.org> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel.centralhosts.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tormail.org Cc: Gabor Kovesdan , Mike Manilone , freebsd-stable@freebsd.org Subject: Re: A BSD-licensed internationalization solution? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 21:06:15 -0000 --=-=-= Content-Type: text/plain Zhihao Yuan writes: >> >> Here are many applications using GNU gettext to provide an >> internationalized user interface. But I found that there isn't a >> BSD-licensed gettext. (so BSD apps do not have internationalization?) >> >> Is there one? Then I can just switch from gettext to that. > > libintl is LGPL, we don't have license issues against it. There is BSD licensed libintl, though. It seems to work fine with GPL gettext/msgfmt tools and no recompilation (libmap.conf trick). # grep for "citrus" http://www.netbsd.org/docs/software/3rdparty/ --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=libintl_freebsd.diff Content-Description: integrate libintl into base Index: lib/Makefile =================================================================== --- lib/Makefile (revision 240180) +++ lib/Makefile (working copy) @@ -37,6 +37,7 @@ SUBDIR_ORDERED= ${_csu} \ libcrypt \ libelf \ ${_libiconv_modules} \ + ${_libintl} \ libkvm \ msun \ libmd \ @@ -166,6 +167,7 @@ _librpcsec_gss= librpcsec_gss .if ${MK_ICONV} != "no" _libiconv_modules= libiconv_modules +_libintl= libintl .endif .if ${MK_IPX} != "no" Index: lib/libc/iconv/Symbol.map =================================================================== --- lib/libc/iconv/Symbol.map (revision 240180) +++ lib/libc/iconv/Symbol.map (working copy) @@ -39,6 +39,7 @@ FBSDprivate_1.0 { _citrus_bcs_strtoul; _citrus_bcs_tolower; _citrus_bcs_toupper; + _citrus_bcs_trunc_rws_len; _citrus_bcs_trunc_ws_len; _citrus_csmapper_open; _citrus_csmapper_close; Index: lib/libintl/Makefile =================================================================== RCS file: /cvsroot/src/lib/libintl/Makefile,v retrieving revision 1.6 diff -u -p -r1.6 Makefile --- lib/libintl/Makefile 14 May 2005 17:58:56 -0000 1.6 +++ lib/libintl/Makefile 9 Sep 2012 03:46:47 -0000 @@ -1,15 +1,13 @@ # $NetBSD: Makefile,v 1.6 2005/05/14 17:58:56 tshiozak Exp $ -.include - LIB= intl +SHLIB_MAJOR= 1 SRCS= gettext.c textdomain.c gettext_iconv.c gettext_dummy.c strhash.c \ sysdep.c plural_parser.c INCS= libintl.h -INCSDIR=/usr/include +CFLAGS+=-I${.CURDIR} -I${.CURDIR}/../libc -#CFLAGS+=-g -CPPFLAGS+=-I${.CURDIR} -I${.CURDIR}/../libc +NO_WCAST_ALIGN.clang= MAN= gettext.3 MLINKS= gettext.3 dgettext.3 gettext.3 dcgettext.3 \ Index: lib/libintl/gettext.c =================================================================== RCS file: /cvsroot/src/lib/libintl/gettext.c,v retrieving revision 1.28 diff -u -p -r1.28 gettext.c --- lib/libintl/gettext.c 30 Jul 2012 23:04:42 -0000 1.28 +++ lib/libintl/gettext.c 9 Sep 2012 03:46:47 -0000 @@ -290,7 +290,9 @@ validate(void *arg, struct mohandle *moh static __inline uint32_t calc_collision_step(uint32_t hashval, uint32_t hashsize) { - _DIAGASSERT(hashsize>2); +#ifdef DIAGNOSTIC + assert(hashsize > 2); +#endif return (hashval % (hashsize - 2)) + 1; } @@ -856,7 +856,7 @@ get_indexed_string(const char *str, size } #define _NGETTEXT_DEFAULT(msgid1, msgid2, n) \ - ((char *)__UNCONST((n) == 1 ? (msgid1) : (msgid2))) + __DECONST(char *, (n) == 1 ? (msgid1) : (msgid2)) char * dcngettext(const char *domainname, const char *msgid1, const char *msgid2, @@ -970,7 +970,7 @@ found: msgid = v; } - return (char *)__UNCONST(msgid); + return __DECONST(char *, msgid); fail: return _NGETTEXT_DEFAULT(msgid1, msgid2, n); Index: lib/libintl/gettext_iconv.c =================================================================== RCS file: /cvsroot/src/lib/libintl/gettext_iconv.c,v retrieving revision 1.8 diff -u -p -r1.8 gettext_iconv.c --- lib/libintl/gettext_iconv.c 18 Feb 2009 13:08:22 -0000 1.8 +++ lib/libintl/gettext_iconv.c 9 Sep 2012 05:57:56 -0000 @@ -55,7 +55,7 @@ static void *cacheroot; /* ARGSUSED1 */ static const struct cache * -cache_find(const char *msg, struct domainbinding *db) +cache_find(const char *msg, struct domainbinding *db __unused) { struct cache key; struct cache **c; Index: lib/libintl/libintl.h =================================================================== RCS file: /cvsroot/src/lib/libintl/libintl.h,v retrieving revision 1.4 diff -u -p -r1.4 libintl.h --- lib/libintl/libintl.h 14 Oct 2011 22:42:01 -0000 1.4 +++ lib/libintl/libintl.h 9 Sep 2012 03:46:47 -0000 @@ -31,6 +31,16 @@ #include +#define gettext libintl_gettext +#define dgettext libintl_dgettext +#define dcgettext libintl_dcgettext +#define ngettext libintl_ngettext +#define dngettext libintl_dngettext +#define dcngettext libintl_dcngettext +#define textdomain libintl_textdomain +#define bindtextdomain libintl_bindtextdomain +#define bind_textdomain_codeset libintl_bind_textdomain_codeset + __BEGIN_DECLS char *gettext(const char *) __format_arg(1); char *dgettext(const char *, const char *) __format_arg(2); Index: lib/libintl/plural_parser.c =================================================================== RCS file: /cvsroot/src/lib/libintl/plural_parser.c,v retrieving revision 1.2 diff -u -p -r1.2 plural_parser.c --- lib/libintl/plural_parser.c 17 Jan 2007 23:24:22 -0000 1.2 +++ lib/libintl/plural_parser.c 9 Sep 2012 03:46:48 -0000 @@ -34,10 +34,10 @@ __RCSID("$NetBSD: plural_parser.c,v 1.2 #include #include #include -#include -#include -#include -#include +#include +#include +#include +#include #include "plural_parser.h" #if defined(TEST_TOKENIZER) || defined(TEST_PARSER) @@ -893,7 +893,7 @@ region_skip_ws(struct _region *r) size_t len = _region_size(r); str = _bcs_skip_ws_len(str, &len); - _region_init(r, __UNCONST(str), len); + _region_init(r, __DECONST(void *, str), len); } static void @@ -903,7 +903,7 @@ region_trunc_rws(struct _region *r) size_t len = _region_size(r); _bcs_trunc_rws_len(str, &len); - _region_init(r, __UNCONST(str), len); + _region_init(r, __DECONST(void *, str), len); } static int @@ -1028,7 +1028,7 @@ parse_plural(struct parser_element **rpe { struct _region r; - _region_init(&r, __UNCONST(str), len); + _region_init(&r, __DECONST(void *, str), len); if (find_plural_forms(&r)) return T_NOTFOUND; @@ -1090,7 +1090,7 @@ _gettext_parse_plural(struct gettext_plu unsigned long _gettext_calculate_plural(const struct gettext_plural *pe, unsigned long n) { - return calculate_plural((void *)__UNCONST(pe), n); + return calculate_plural(__DECONST(void *, pe), n); } void Index: lib/libintl/strhash.c =================================================================== RCS file: /cvsroot/src/lib/libintl/strhash.c,v retrieving revision 1.3 diff -u -p -r1.3 strhash.c --- lib/libintl/strhash.c 25 Sep 2007 08:19:09 -0000 1.3 +++ lib/libintl/strhash.c 9 Sep 2012 03:46:48 -0000 @@ -38,7 +38,7 @@ __RCSID("$NetBSD: strhash.c,v 1.3 2007/0 /* * string hash function by P.J.Weinberger. - * this implementation is derived from src/lib/libc/citrus/citrus_db_hash.c. + * this implementation is derived from src/lib/libc/iconv/citrus_db_hash.c. */ uint32_t /*ARGSUSED*/ Index: lib/libintl/textdomain.c =================================================================== RCS file: /cvsroot/src/lib/libintl/textdomain.c,v retrieving revision 1.13 diff -u -p -r1.13 textdomain.c --- lib/libintl/textdomain.c 21 Mar 2012 10:10:36 -0000 1.13 +++ lib/libintl/textdomain.c 9 Sep 2012 03:46:48 -0000 @@ -96,7 +96,7 @@ bindtextdomain(const char *domainname, c if (p) return (p->path); else - return (char *)__UNCONST(_PATH_TEXTDOMAIN); + return __DECONST(char *, _PATH_TEXTDOMAIN); } strlcpy(p->path, dirname, sizeof(p->path)); --=-=-=-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 12 23:42:26 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C2DD3106566B; Wed, 12 Sep 2012 23:42:26 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by mx1.freebsd.org (Postfix) with ESMTP id 7E23A8FC12; Wed, 12 Sep 2012 23:42:26 +0000 (UTC) Received: from [IPv6:::1] (proxy6.corp.yahoo.com [216.145.48.19]) by mrout3.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q8CNg5vb021463; Wed, 12 Sep 2012 16:42:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1347493326; bh=jMQqoB2Eyx+2YVUG/ech8D7Hsi+V2/44j0XxJL9qNwQ=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=NGTmf+Q7e6ASgtHTKKXfsvpcyw1asNudf+z3axoqrox/uEUtsNsxRC49MgbMWmLrT EIqr+7tyMWiJcn6MizaTxRx1fvcPBIi4jrnwj0D1SDS9NP6Sp30km8CRK+W+ymnBnH cr/zbjfB4Pb80kunOIIqEww0usatlGnm86X9xe7U= From: Sean Bruno To: Jack Vogel In-Reply-To: References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> Content-Type: text/plain; charset="UTF-8" Date: Wed, 12 Sep 2012 16:42:05 -0700 Message-ID: <1347493325.4686.7.camel@powernoodle> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 493325003 Cc: "freebsd-net@freebsd.org" , Giulio Ferro , "freebsd-stable@freebsd.org" Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 23:42:26 -0000 > > igb+lagg worked for us on 8.3. Haven't tried it since moving to 9.0 > > and 9-STABLE on those three boxes. > > > > igb+lagg doesn't work for him on 9.0. Although, I don't recall if > > non-LACP options were tried earlier in this thread, or if it's just > > the LACP mode that's failing. If one mode works (say failover) and > > LACP mode doesn't, that "seems to" point to lagg. > > > > I'll see if I can free up an igb port on my 9.0 and 9-STABLE boxes to > > test this with as well. > > > > > > I wouldn't use 9.0, go with 9.1 RC or whatever has the latest igb code, > if you see the issue there I can see about getting some time to look into > it here. > > Jack We're running igb + lagg on two interfaces here at Yahoo without issues like this. We're using LACP exclusively with Cisco switches. If you're seeing failover issues, I wonder if its the switch you're using as opposed to the host and ethernet card? Just a shot in the dark here. Sean From owner-freebsd-stable@FreeBSD.ORG Thu Sep 13 05:31:05 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D747F106566B; Thu, 13 Sep 2012 05:31:05 +0000 (UTC) (envelope-from egrosbein@rdtc.ru) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5]) by mx1.freebsd.org (Postfix) with ESMTP id 2879D8FC08; Thu, 13 Sep 2012 05:31:04 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.5/8.14.5) with ESMTP id q8D5V2DW046391; Thu, 13 Sep 2012 12:31:02 +0700 (NOVT) (envelope-from egrosbein@rdtc.ru) Message-ID: <50516F96.1020905@rdtc.ru> Date: Thu, 13 Sep 2012 12:31:02 +0700 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7 MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Alexander Motin , re@freebsd.org Subject: GEOM_RAID in GENERIC is harmful X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 05:31:06 -0000 Hi! 9-STABLE has got options GEOM_RAID in GENERIC. In real world, this change is pretty harmful and there are lots of cases when 9.0-RELEASE systems upgraded to 9-STABLE fail to mount root UFS filesystem or attach ZFS. It seems, there are lots of HDDs supplied with pseudo-RAID labels at the end: pre-installed Windows machined having motherboards with pseudo-RAID like Intel RapidStore and alike. One can not even be aware of these labels. 9.0-RELEASE can be installed on such HDDs and use them with GMIRROR or ZFS without a problem. Upgraded to 9-STABLE, such system fails to build due to GRAID jumping out of box and grabbing HDDs for itself, so GMIRROR or ZFS got broken. That's makes users very angry when production server fails to boot with GENERIC kernel after correctly performed upgrade. GEOM_RAID compiled in GENERIC should be deactivated and require activation with some loader knob. Also, we need distinct RELEASE NOTES warning about the issue. Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Thu Sep 13 06:23:14 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 74D81106566B for ; Thu, 13 Sep 2012 06:23:14 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 024628FC1A for ; Thu, 13 Sep 2012 06:23:13 +0000 (UTC) Received: by wibhr14 with SMTP id hr14so2377756wib.13 for ; Wed, 12 Sep 2012 23:23:13 -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:content-transfer-encoding :in-reply-to:user-agent; bh=drRJjAzuTwL0rfRO+8v9VpxqYMmtv/wYguqaLL14hz0=; b=qrM5TA6mjKZWVi8uYl4zt2aFj0X2kFTu7iaQKdeZsDE8psrHfoLiT0wTNPwmdKxWbG 7GoS/Q5EF/wkHmLrHKylRHKDFlhM7EeyeUH73nELpp8r0+rXkwhUlxHpovcR8HyUR+XE XyUG+1QtliGBaPCTh5jgXDKDWlcJGUvU25u/gYMsoWpoGUbKne6tnfvLCKT+RYcVOwHq tCjHOAEiOC8JYvTb4idi+nLjbfTAvCDkaHWm3XmhQqSeCxmgW14WHdh0kW1IdIop/gIm jDxTneR/SmJqDstPa5nLhEcpNgU8D31yWzqfL6aCVu8N4iYnZzNFQwF/oaN/T0+GYhhU qxWQ== Received: by 10.216.138.73 with SMTP id z51mr596540wei.39.1347517392836; Wed, 12 Sep 2012 23:23:12 -0700 (PDT) Received: from localhost ([188.230.122.226]) by mx.google.com with ESMTPS id bc2sm18153322wib.0.2012.09.12.23.23.10 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 12 Sep 2012 23:23:11 -0700 (PDT) Date: Thu, 13 Sep 2012 09:23:09 +0300 From: Mikolaj Golub To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20120913062307.GA43842@gmail.com> References: <504D10A7.1070701@quip.cz> <20120910054459.GA57302@gmail.com> <504DFD37.60105@quip.cz> <20120910203511.GA27221@gmail.com> <504F9C39.2070107@quip.cz> <20120912055831.GA48849@gmail.com> <50504A30.10501@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <50504A30.10501@quip.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: bsnmpd always died on HDD detach X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 06:23:14 -0000 On Wed, Sep 12, 2012 at 10:39:12AM +0200, Miroslav Lachman wrote: > (gdb) bt > #0 0x0000000801046cba in disk_query_disk (entry=0x0) at > hostres_diskstorage_tbl.c:241 > #1 0x0000000801dd6a00 in ?? () > #2 0x0000000801dd6600 in ?? () > #3 0x0000000000000000 in ?? () > #4 0x0000000801048230 in device_entry_create (name=0x0, > location=0x800c14ee0 "0", descr=0x8010482a6 "") at hostres_device_tbl.c:217 > #5 0x0000000801dd7800 in ?? () > #6 0x0000000801dd7800 in ?? () > #7 0x0000000801dd7400 in ?? () > #8 0x0000000000000000 in ?? () > #9 0x0000000801048230 in device_entry_create (name=0x801dd7c00 "", > location=0x801048230 "˙˙I\213|$8čŕ\201˙˙L\211çčŘ\201˙˙é\035ţ˙˙H\215\025", > descr=0x8010482a6 "") at hostres_device_tbl.c:217 > #10 0x0000000801dd4a00 in ?? () > #11 0x0000000801dd4a00 in ?? () > #12 0x0000000801dd1a00 in ?? () > #13 0x0000000000000000 in ?? () > #14 0x0000000801048230 in device_entry_create (name=0x801dd8400 "", > location=0x801048230 "˙˙I\213|$8čŕ\201˙˙L\211çčŘ\201˙˙é\035ţ˙˙H\215\025", > descr=0x8010482a6 "") at hostres_device_tbl.c:217 > #15 0x0000000801dd1800 in ?? () > #16 0x0000000801dd1800 in ?? () > #17 0x0000000800c00ea8 in ?? () > #18 0x000000000051b1c8 in ?? () > #19 0x0000000800c00938 in ?? () > #20 0x000000000051b258 in ?? () > #21 0x0000000801dc8a00 in ?? () > #22 0x00000008009f7be9 in free () from /lib/libc.so.7 > #23 0x0000000000000000 in ?? () > #24 0x00007fffffffed98 in ?? () > #25 0x00000008010478bd in device_entry_delete () at hostres_device_tbl.c:266 > #26 0x00000000005187d0 in snmp_error () > #27 0x0000000801047be6 in op_hrDeviceTable (ctx=Variable "ctx" is not > available. > ) at hostres_device_tbl.c:671 > #28 0x000000000051b840 in ?? () > #29 0x000000000051b830 in ?? () > #30 0x0000000000000000 in ?? () > #31 0x00007fffffffc360 in ?? () > #32 0x000000000051b830 in ?? () > #33 0x0000000000000000 in ?? () > #34 0x00000008009efbd2 in _pthread_mutex_init_calloc_cb () from > /lib/libc.so.7 > #35 0x00000008009f2d32 in _malloc_prefork () from /lib/libc.so.7 > #36 0x00000008009f6e1f in realloc () from /lib/libc.so.7 > #37 0x0000000800e0b441 in mib_if_is_dyn () from /usr/lib/snmp_mibII.so > #38 0x0000000000000000 in ?? () > #39 0x00007fffffffc5cc in ?? () > #40 0x0000000000000001 in ?? () > #41 0x00007fffffffc5e0 in ?? () > #42 0x31fa39e2fac72819 in ?? () > #43 0x0000000000000001 in ?? () > #44 0x000000080065fad5 in poll_dispatch () from /lib/libbegemot.so.4 > #45 0x000000000040616a in main () > > > I hope it helps you to debug this problem. Looks like we can't trust to this output. -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Thu Sep 13 07:44:39 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12E73106566B; Thu, 13 Sep 2012 07:44:39 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 93AA98FC0A; Thu, 13 Sep 2012 07:44:38 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id C26376A6001; Thu, 13 Sep 2012 09:44:37 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.5/8.14.5) with ESMTP id q8D7ibDO043021; Thu, 13 Sep 2012 09:44:37 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.5/8.14.5/Submit) id q8D7ibwi042124; Thu, 13 Sep 2012 09:44:37 +0200 (CEST) (envelope-from lars) Date: Thu, 13 Sep 2012 09:44:37 +0200 From: Lars Engels To: Alexander Motin Message-ID: <20120913074437.GX20762@e-new.0x20.net> References: <20120822165239.GX32916@e-new.0x20.net> <50351EA4.4040401@gibfest.dk> <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> <20120912172525.GU20762@e-new.0x20.net> <5050C6BC.8000307@FreeBSD.org> <20120912174649.GV20762@e-new.0x20.net> <5050DB57.90903@FreeBSD.org> <20120912195821.GW20762@e-new.0x20.net> <5050EBB9.7040202@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8SUh+pnhVixfgwb7" Content-Disposition: inline In-Reply-To: <5050EBB9.7040202@FreeBSD.org> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.3-RELEASE-p2 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@FreeBSD.org, Andriy Gapon Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 07:44:39 -0000 --8SUh+pnhVixfgwb7 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 12, 2012 at 11:08:25PM +0300, Alexander Motin wrote: > On 12.09.2012 22:58, Lars Engels wrote: > > On Wed, Sep 12, 2012 at 09:58:31PM +0300, Alexander Motin wrote: > >> On 12.09.2012 20:46, Lars Engels wrote: > >>> On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote: > >>>> on 12/09/2012 20:25 Lars Engels said the following: > >>>>> On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote: > >>>>>> Could you try to play with different eventtimer settings (preferab= ly in current) ? > >>>>>> You can use this thread / PR as a guide: > >>>>>> http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus= =3D14495 > >>>>>> > >>>>>> The place where boot stop looks suspiciously close to the place wh= ere timer > >>>>>> interrupts should start driving the system. > >>>>> > >>>>> Yes, that's it! > >>>>> Setting kern.eventtimer.timer=3D"i8254" let's the Thinkpad boot on > >>>>> CURRENT with the AC cable inserted. > >>>>> > >>>> > >>>> Please share your sysctl kern.eventtimer output with Alexander. > >>>> He will probably ask for some additional information :-) > >> > >> Sorry if I've missed, but it would be useful to see verbose dmesg in > >> situation where system couldn't boot without switching eventtimer. > > > > No problem. See: http://bsd-geek.de/FreeBSD/IMAG0190.jpg >=20 > No, I've seen that one and I don't mean it. I mean full verbose dmesg of= =20 > successful boot in conditions where system was not booting before=20 > without setting kern.eventtimer.timer=3D"i8254". Ok, sorry. Here's a verbose dmesg booting CURRENT without AC power: http://bsd-geek.de/FreeBSD/T61_dmesg.boot.works --8SUh+pnhVixfgwb7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlBRjuUACgkQKc512sD3afjnSgCgrnLT3EZvHkU0/2HErDch2v3W H9UAnjcWO6OG1uNzPedR/JDYBQZ/fUaK =/PCj -----END PGP SIGNATURE----- --8SUh+pnhVixfgwb7-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 13 09:52:02 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CAD26106564A; Thu, 13 Sep 2012 09:52:02 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0E3EE8FC0A; Thu, 13 Sep 2012 09:52:01 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so2202738lbb.13 for ; Thu, 13 Sep 2012 02:52:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=otL+8QXPrWxrNup4BDkPE6sUyxnzlID6djQCRpwpVSM=; b=J0Tr3VqY5fA30CgGLmMiPPj3uPemc1zdZf/GwGyyXPN/BioMZZvK6jkeqWOk0g0GTu jvoeC/JHK8oxRk0/fGb8VbFFsNRL02Q1nHbOFJIcCUOgbLfnaTtfd1EK1MvwbleTAy3t MEShsxhs1tEBI6TIqbIvkY2i1A47NdT+BT3p5GpqVyxo59FgvJM3T9VhROPYRt8sMUHt dQPWc52HPrHvrkGoSXCmFBvEiEZKKGeUEc1JsBeDnB07RfOlUcrlW+kdfLi77nb1VLNs yrvm9Pe6ICq3DfdIwXGxEgqWpOgDJHLCFcHcPhJidig4grvFce4nZtUl8IRzwK7JKHwD +EIg== Received: by 10.152.105.210 with SMTP id go18mr1428899lab.13.1347529920765; Thu, 13 Sep 2012 02:52:00 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id lr17sm22827936lab.12.2012.09.13.02.51.58 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Sep 2012 02:51:59 -0700 (PDT) Sender: Alexander Motin Message-ID: <5051ACBD.1090207@FreeBSD.org> Date: Thu, 13 Sep 2012 12:51:57 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120628 Thunderbird/13.0.1 MIME-Version: 1.0 To: Eugene Grosbein References: <50516F96.1020905@rdtc.ru> In-Reply-To: <50516F96.1020905@rdtc.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, re@freebsd.org Subject: Re: GEOM_RAID in GENERIC is harmful X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 09:52:02 -0000 On 13.09.2012 08:31, Eugene Grosbein wrote: > 9-STABLE has got options GEOM_RAID in GENERIC. > In real world, this change is pretty harmful and there are lots of cases > when 9.0-RELEASE systems upgraded to 9-STABLE fail to mount root UFS filesystem > or attach ZFS. > > It seems, there are lots of HDDs supplied with pseudo-RAID labels at the end: > pre-installed Windows machined having motherboards with pseudo-RAID > like Intel RapidStore and alike. One can not even be aware of these labels. > > 9.0-RELEASE can be installed on such HDDs and use them with GMIRROR or ZFS > without a problem. Upgraded to 9-STABLE, such system fails to build due > to GRAID jumping out of box and grabbing HDDs for itself, > so GMIRROR or ZFS got broken. > > That's makes users very angry when production server fails to boot > with GENERIC kernel after correctly performed upgrade. > > GEOM_RAID compiled in GENERIC should be deactivated and require activation > with some loader knob. Also, we need distinct RELEASE NOTES warning about the issue. Problem of on-disk metadata garbage is not limited to GEOM_RAID. For example, I had case where remainders of old UFS file system were found by GEOM_LABEL and ZFS incorrectly attached to it instead of proper GPT partition, making other partitions inaccessible. Does it mean we should remove GEOM_LABEL also? I don't think so. All what GEOM_RAID is guilty in is that it was not in place for 9.0 release. If we remove it now, it will just postpone the problem for later time or will never be able to add it again because of the same reasons. Unlike GEOM_LABEL, metadata of GEOM_RAID is quite easy to delete without complete disk erase: `graid status -ag`, `graid delete ...`. Yes, it can be a problem if system can't boot, but now we at least have live mode on installation images, that should allow to do it. Adding some loader tunables indeed could simplify recovery in case of boot problem. I will probably add such ones now. It won't hurt. But I disagree they should be disabled by default, limiting users who really want to use BIOS RAID. Disabling them will also make metadata removal without full wipe more difficult because different RAIDs have different on-disk metadata layout, and you should know where exactly to apply dd. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Thu Sep 13 10:01:11 2012 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 55E8C1065672; Thu, 13 Sep 2012 10:01:11 +0000 (UTC) (envelope-from egrosbein@rdtc.ru) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5]) by mx1.freebsd.org (Postfix) with ESMTP id AFC758FC12; Thu, 13 Sep 2012 10:01:10 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.5/8.14.5) with ESMTP id q8DA17TR049361; Thu, 13 Sep 2012 17:01:07 +0700 (NOVT) (envelope-from egrosbein@rdtc.ru) Message-ID: <5051AEE3.7010907@rdtc.ru> Date: Thu, 13 Sep 2012 17:01:07 +0700 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7 MIME-Version: 1.0 To: Alexander Motin References: <50516F96.1020905@rdtc.ru> <5051ACBD.1090207@FreeBSD.org> In-Reply-To: <5051ACBD.1090207@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: stable@FreeBSD.org, re@FreeBSD.org Subject: Re: GEOM_RAID in GENERIC is harmful X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 10:01:11 -0000 13.09.2012 16:51, Alexander Motin wrote: >> That's makes users very angry when production server fails to boot >> with GENERIC kernel after correctly performed upgrade. >> >> GEOM_RAID compiled in GENERIC should be deactivated and require activation >> with some loader knob. Also, we need distinct RELEASE NOTES warning about the issue. > > Problem of on-disk metadata garbage is not limited to GEOM_RAID. For > example, I had case where remainders of old UFS file system were found > by GEOM_LABEL and ZFS incorrectly attached to it instead of proper GPT > partition, making other partitions inaccessible. Does it mean we should > remove GEOM_LABEL also? I don't think so. All what GEOM_RAID is guilty > in is that it was not in place for 9.0 release. If we remove it now, it > will just postpone the problem for later time or will never be able to > add it again because of the same reasons. We must be ready for lots of angry users of 9.1-RELEASE then and have BIG RED WARNING in RELEASE NOTES. Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Thu Sep 13 10:43:17 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18A031065672 for ; Thu, 13 Sep 2012 10:43:17 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [128.127.144.4]) by mx1.freebsd.org (Postfix) with ESMTP id B1D7D8FC12 for ; Thu, 13 Sep 2012 10:43:15 +0000 (UTC) Received: from bsdrookie.norma.com. ([IPv6:fd00::7f0]) by elf.hq.norma.perm.ru (8.14.5/8.14.5) with ESMTP id q8DADp0L041637 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 13 Sep 2012 16:13:51 +0600 (YEKT) (envelope-from emz@norma.perm.ru) Message-ID: <5051B1DF.9030300@norma.perm.ru> Date: Thu, 13 Sep 2012 16:13:51 +0600 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120806 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <50516F96.1020905@rdtc.ru> <5051ACBD.1090207@FreeBSD.org> In-Reply-To: <5051ACBD.1090207@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (elf.hq.norma.perm.ru [IPv6:fd00::30a]); Thu, 13 Sep 2012 16:13:51 +0600 (YEKT) X-Spam-Status: No hits=-97.8 bayes=0.5 testhits RDNS_NONE=1.274, SPF_SOFTFAIL=0.972, TO_NO_BRKTS_PCNT=0.001, USER_IN_WHITELIST=-100 autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru Subject: Re: GEOM_RAID in GENERIC is harmful X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 10:43:17 -0000 Hi. On 13.09.2012 15:51, Alexander Motin wrote: > > Problem of on-disk metadata garbage is not limited to GEOM_RAID. For > example, I had case where remainders of old UFS file system were found > by GEOM_LABEL and ZFS incorrectly attached to it instead of proper GPT > partition, making other partitions inaccessible. Does it mean we > should remove GEOM_LABEL also? I don't think so. All what GEOM_RAID is > guilty in is that it was not in place for 9.0 release. If we remove it > now, it will just postpone the problem for later time or will never be > able to add it again because of the same reasons. > > Unlike GEOM_LABEL, metadata of GEOM_RAID is quite easy to delete > without complete disk erase: `graid status -ag`, `graid delete ...`. > Yes, it can be a problem if system can't boot, but now we at least > have live mode on installation images, that should allow to do it. > > Adding some loader tunables indeed could simplify recovery in case of > boot problem. I will probably add such ones now. It won't hurt. But I > disagree they should be disabled by default, limiting users who really > want to use BIOS RAID. Disabling them will also make metadata removal > without full wipe more difficult because different RAIDs have > different on-disk metadata layout, and you should know where exactly > to apply dd. > From my point of view, the policy of new features should be like that: new features introduced to the system should by default try to mimic the old behavior. Right now we will have a situation when most of the users will just upgrade to the new kernel, and will get a non-bootable system or a system with one 100% busy disk (for example degraded raid0 gives this). On a system that manages to boot up 'graid delete -f' could lead to a livelock (got it today, on a degraded raid1). Furthermore, the situation when the engineer forgot about a disk with a glabel/gmirror data is less probable than a situation when you have a 'new' disk from another department which was extracted from some windows server or workstation. Should I test all of the disks against graid labels ? Yeah, may be. But for X last years I didn't do that, just because it worked for me and it didn't lead to a crash. The softraid labels were harmless all the way. I could use a zpool or a gmirror without even knowing that I have them. Now I suddenly need to care about the labels. Is GEOM_RAID great, as a feature ? Yep, it is. Is the way it is introduced into the system that great ? Not at all. From my point of view GEOM_RAID in GENERIC kernel is a bomb, and we will lose lots of FreeBSD beginners due to this. Eugene. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 13 15:06:17 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 001C2106566B; Thu, 13 Sep 2012 15:06:16 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3EDE48FC19; Thu, 13 Sep 2012 15:06:15 +0000 (UTC) Received: by lage12 with SMTP id e12so2420172lag.13 for ; Thu, 13 Sep 2012 08:06:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=WGFyq6Ua2/RlTNhMfiAazubWxy52wpQfBMBC06QE6RI=; b=koYBaSA4Z59W7Oek8/Bmg3/3x9ybfCWKG0mr4td6V9dB3WeQkRCPpwMLjnZhnceou0 h3YQMJT2w4vwMYiwMPR3vQc0QEHNiG7K08g31L5y6QcngCn03NIXC7+wV7z0HyTiVK7I 5yHJR5MBGJT/m+PWMjFAPIsdaLQeFbMYNSLI9Bah006IdHUMV+emEmK39QnxAVzrHMwD P59Vzxh/dCincA9v3IBBmoZRuS0wqvbhBWJiyp5od0zSN/wKeccPZ1LqqUbUOqE49gGe R8gmXOr4fDbBrGijKxcRX94f/Z6wrhLH+whhee+hd1ygg+COGwQo4caHElTSHDhG5UQs mP3Q== Received: by 10.112.31.233 with SMTP id d9mr1029206lbi.116.1347548774006; Thu, 13 Sep 2012 08:06:14 -0700 (PDT) Received: from pc.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id hz16sm23575100lab.6.2012.09.13.08.06.12 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Sep 2012 08:06:13 -0700 (PDT) Sender: Alexander Motin Message-ID: <5051F6A1.50900@FreeBSD.org> Date: Thu, 13 Sep 2012 18:07:13 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 MIME-Version: 1.0 To: Eugene Grosbein References: <50516F96.1020905@rdtc.ru> <5051ACBD.1090207@FreeBSD.org> <5051AEE3.7010907@rdtc.ru> In-Reply-To: <5051AEE3.7010907@rdtc.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@FreeBSD.org, re@FreeBSD.org Subject: Re: GEOM_RAID in GENERIC is harmful X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 15:06:17 -0000 On 13.09.2012 13:01, Eugene Grosbein wrote: > 13.09.2012 16:51, Alexander Motin wrote: > >>> That's makes users very angry when production server fails to boot >>> with GENERIC kernel after correctly performed upgrade. >>> >>> GEOM_RAID compiled in GENERIC should be deactivated and require activation >>> with some loader knob. Also, we need distinct RELEASE NOTES warning about the issue. >> >> Problem of on-disk metadata garbage is not limited to GEOM_RAID. For >> example, I had case where remainders of old UFS file system were found >> by GEOM_LABEL and ZFS incorrectly attached to it instead of proper GPT >> partition, making other partitions inaccessible. Does it mean we should >> remove GEOM_LABEL also? I don't think so. All what GEOM_RAID is guilty >> in is that it was not in place for 9.0 release. If we remove it now, it >> will just postpone the problem for later time or will never be able to >> add it again because of the same reasons. > > We must be ready for lots of angry users of 9.1-RELEASE then > and have BIG RED WARNING in RELEASE NOTES. Warning is good, but I don't think it will be "lots". It is enabled in 9-STABLE for some time now and I haven't seen many complains. If re@ permit to MFC r240465 in few days, solution for those who may need it will be simple: kern.geom.raid.enable=0. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Thu Sep 13 15:45:23 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1C812106566B for ; Thu, 13 Sep 2012 15:45:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id E6E9B8FC15 for ; Thu, 13 Sep 2012 15:45:22 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 44EAAB96F; Thu, 13 Sep 2012 11:45:22 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 13 Sep 2012 11:27:21 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <50516F96.1020905@rdtc.ru> <5051ACBD.1090207@FreeBSD.org> <5051B1DF.9030300@norma.perm.ru> In-Reply-To: <5051B1DF.9030300@norma.perm.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201209131127.21677.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 13 Sep 2012 11:45:22 -0400 (EDT) Cc: "Eugene M. Zheganin" Subject: Re: GEOM_RAID in GENERIC is harmful X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 15:45:23 -0000 On Thursday, September 13, 2012 6:13:51 am Eugene M. Zheganin wrote: > From my point of view GEOM_RAID in GENERIC kernel is a bomb, and we > will lose lots of FreeBSD beginners due to this. I had the completely opposite experience. I bought a new desktop and wanted to use the onboard SATA RAID. 9.0 didn't work out-of-the-box with a RAID-1 volume configured using the BIOS. I knew to kldload geom_raid.ko, but not all new users know to do that. I think the onboard SATA RAID on typical x86 motherboards is something we should be supporting out of the box. I don't disagree that there were some surprising side effects from enabling GEOM_RAID, but I think your viewpoint is very much one-sided. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Thu Sep 13 16:56:29 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 941A31065670; Thu, 13 Sep 2012 16:56:29 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id CF2C68FC08; Thu, 13 Sep 2012 16:56:27 +0000 (UTC) Received: by lage12 with SMTP id e12so2529542lag.13 for ; Thu, 13 Sep 2012 09:56:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=zt8HPAlkHvtvssNURkTgdyQYsp3mYxWjSayBjkefMBA=; b=UeEpGEBNmjhEVXxUU+KuPdhIVHLxtZ2kCLDpBoXL9c3EN/PICJkBQfbBK340l/s/nU avkSxKqPYsN3B1JzifQNUymMw9klv8QOq1kfmdKGBnHUKg4pvhU524/HyNik/5fwKSvr 1atrBLX4NUUC4+lsmFK5l7WzJpk6LOIglt89y+T9855nlT+8m5hcODZgQE2N2IHsPJmI WAy8rRz1yk32dXAIRc/dLlnfISPYJMSBFH1t0HzIPMvKhz7phWbgZWmx63sRV4GU98it 4CJZ6LC1vW0HYKA8F4leCFxPe2i3ePK7jCaOS6hHopTD6Jkc+M+LpDdnXnCeaMisY3eW 8PqQ== Received: by 10.112.8.228 with SMTP id u4mr138009lba.38.1347555386553; Thu, 13 Sep 2012 09:56:26 -0700 (PDT) Received: from pc.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id pi16sm23722108lab.7.2012.09.13.09.56.24 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Sep 2012 09:56:25 -0700 (PDT) Sender: Alexander Motin Message-ID: <505210A3.8000105@FreeBSD.org> Date: Thu, 13 Sep 2012 19:58:11 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 MIME-Version: 1.0 To: Lars Engels References: <20120822165239.GX32916@e-new.0x20.net> <50351EA4.4040401@gibfest.dk> <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> <20120912172525.GU20762@e-new.0x20.net> <5050C6BC.8000307@FreeBSD.org> <20120912174649.GV20762@e-new.0x20.net> <5050DB57.90903@FreeBSD.org> <20120912195821.GW20762@e-new.0x20.net> <5050EBB9.7040202@FreeBSD.org> <20120913074437.GX20762@e-new.0x20.net> In-Reply-To: <20120913074437.GX20762@e-new.0x20.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, Andriy Gapon Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 16:56:29 -0000 On 13.09.2012 10:44, Lars Engels wrote: > On Wed, Sep 12, 2012 at 11:08:25PM +0300, Alexander Motin wrote: >> On 12.09.2012 22:58, Lars Engels wrote: >>> On Wed, Sep 12, 2012 at 09:58:31PM +0300, Alexander Motin wrote: >>>> On 12.09.2012 20:46, Lars Engels wrote: >>>>> On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote: >>>>>> on 12/09/2012 20:25 Lars Engels said the following: >>>>>>> On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote: >>>>>>>> Could you try to play with different eventtimer settings (preferably in current) ? >>>>>>>> You can use this thread / PR as a guide: >>>>>>>> http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus=14495 >>>>>>>> >>>>>>>> The place where boot stop looks suspiciously close to the place where timer >>>>>>>> interrupts should start driving the system. >>>>>>> >>>>>>> Yes, that's it! >>>>>>> Setting kern.eventtimer.timer="i8254" let's the Thinkpad boot on >>>>>>> CURRENT with the AC cable inserted. >>>>>>> >>>>>> >>>>>> Please share your sysctl kern.eventtimer output with Alexander. >>>>>> He will probably ask for some additional information :-) >>>> >>>> Sorry if I've missed, but it would be useful to see verbose dmesg in >>>> situation where system couldn't boot without switching eventtimer. >>> >>> No problem. See: http://bsd-geek.de/FreeBSD/IMAG0190.jpg >> >> No, I've seen that one and I don't mean it. I mean full verbose dmesg of >> successful boot in conditions where system was not booting before >> without setting kern.eventtimer.timer="i8254". > > Ok, sorry. > Here's a verbose dmesg booting CURRENT without AC power: > http://bsd-geek.de/FreeBSD/T61_dmesg.boot.works Hmm. I see nothing suspicious. HPET driver output is typical for ICH8M chipset, many of which are working fine in different systems, including several mine. There was no significant changes in HPET after 9.0-RELASE except r231161. It changed device probe order that increased chance of interrupt sharing. It should not be a problem, but who knows. You can try to hint HPET driver specific IRQ 23 (that looks unused) to avoid sharing by setting hint.hpet.0.allowed_irqs="0x00800000". You've told that problem related to AC power state. Have you compared dmesg outputs with and without it? -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Thu Sep 13 17:04:53 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA776106566C for ; Thu, 13 Sep 2012 17:04:53 +0000 (UTC) (envelope-from apeiron@isuckatdomains.net) Received: from isuckatdomains.net (unknown [IPv6:2600:3c01:e000:4::1]) by mx1.freebsd.org (Postfix) with ESMTP id 91A728FC21 for ; Thu, 13 Sep 2012 17:04:53 +0000 (UTC) Received: from isuckatdomains.isuckatdomains.net (isuckatdomains.net [74.207.243.179]) by isuckatdomains.net (Postfix) with ESMTPSA id 784444581C for ; Thu, 13 Sep 2012 13:04:53 -0400 (EDT) Date: Thu, 13 Sep 2012 13:04:52 -0400 From: Chris Nehren To: freebsd-stable@freebsd.org Message-ID: <20120913170452.GF5302@isuckatdomains.isuckatdomains.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <503E129B.7070607@icritical.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PGNNI9BzQDUtgA2J" Content-Disposition: inline In-Reply-To: <503E129B.7070607@icritical.com> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: Userland dtrace broken? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 17:04:53 -0000 --PGNNI9BzQDUtgA2J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 29, 2012 at 14:01:15 +0100 , Matt Burke wrote: > Following http://wiki.freebsd.org/DTrace/userland on 9.1-RC1, the example > fails to work as demonstrated: >=20 > # dtrace -s pid.d -c test > dtrace: script 'pid.d' matched 2 probes > CPU ID FUNCTION:NAME > 1 59284 main:entry > dtrace: pid 25479 exited with status 1 >=20 > # >=20 >=20 > Also, I get hangs when trying to do pretty much anything with the pid:::e= ntry >=20 > # dtrace -n 'pid$target::malloc:entry' -c 'echo x' > dtrace: description 'pid$target::malloc:entry' matched 2 probes > xCPU ID FUNCTION:NAME > 1 59311 malloc:entry > load: 0.43 cmd: dtrace 63737 [running] 8.93r 1.60u 4.19s 35% 25072k > load: 0.88 cmd: echo 63738 [running] 45.10r 2.27u 18.75s 47% 1452k > load: 1.19 cmd: dtrace 63737 [running] 70.32r 12.14u 33.27s 64% 25072k >=20 > # procstat -k 63737 63738 > PID TID COMM TDNAME KSTACK > 63737 101505 dtrace - mi_switch > sleepq_catch_signals sleepq_timedwait_sig _sleep do_wait > __umtx_op_wait_uint_private amd64_syscall Xfast_syscall > 63737 111024 dtrace - > 63738 101657 echo - mi_switch > thread_suspend_switch ptracestop cursig ast doreti_ast >=20 >=20 > I have previously tried using dtrace on 9.0R, but it was insta-panic. Is > there anything I may have missed here? >=20 >=20 >=20 > make.conf: > STRIP=3D > CFLAGS+=3D-fno-omit-frame-pointer > WITH_CTF=3D1 >=20 > kernel config: > include GENERIC > ident DTRACE >=20 > makeoptions DEBUG=3D"-g" > makeoptions WITH_CTF=3D1 > options KDTRACE_FRAME > options KDTRACE_HOOKS > options DDB_CTF > options DDB >=20 Relevant to my interests, too. I've followed the instructions on the wiki / in the handbook (on 9.0/9.1-PRE) and only receive error messages. Is DTrace supposed to be working properly on 9.x, or is it still experimental? It's nice to say that FreeBSD nominally supports DTrace, but if it doesn't actually work then it needs to be labelled as such. I am fine with it being experimental if that's the case, but saying so would help manage expectations a lot better. --=20 Thanks and best regards, Chris Nehren --PGNNI9BzQDUtgA2J Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJQUhIzAAoJEB3ywRGrHAnQjpoP/3/ae5cR8wBOhsJRBHxZn9KX oceYxm7LQYg+wBPlln6IiJwaUU1hTd2naAMxZcEACHNFB5NlFaohl2MIKTYVqZh7 wmBc3FzVJB+woIW1CETM2gqgFdDAQF4cSwEVICst2u/f95M4H5SxT58ID/m3V5ks 3D1wl72TPRkqGeJyGgOHuasljq9NLqnZgyLMYerVzrSdBARCpXyGLZe7ukeonMK0 9co8BW17rs+xz1vAvZihkQnJTwiCE+3Fi3N+PVdhMKK3f9C8fHyHrgn5WFbpcRGE mw2D289dEQy1sc3yhneFsrkwZ7b9QktZ8cRw3VS1cD/cWbmTa5DeeCSWMd6+9t73 7gv5TkS43cxIhndMcjI9AMi9ZVYqUFGD9V94D0lqo1XEkTYDrVEU9+D8THL8Meqd rNyZ+VhYLzi8N+OdwiWiFXVI2A4dv5rgwdy5XL9NoesmrNYxHRCcPWiM5I+AF/q9 +QeyPMELwHpsFzBZXdjZ9xlGxmSK7nhmiyJWxmvt2xQBMPi3YSpShdnRM76DHQh6 g+0KNC8Vk+np7rdTZrQg0Tqs2L34uQip+c584qoEo5upd07tYmwuFvvr8l0xgjVz 2vTzHpA3SGV4r36msWmVDAvlgM+PCXbNuSOQ0zG9sk9DRdYYv8DEgTl/set54AvP oy+9wjVpi6O4Aa9fRg8a =HDF9 -----END PGP SIGNATURE----- --PGNNI9BzQDUtgA2J-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 13 19:47:27 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69151106566C; Thu, 13 Sep 2012 19:47:27 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mx1.giulioferro.ch (mx1.giulioferro.ch [217.150.252.208]) by mx1.freebsd.org (Postfix) with ESMTP id 0913D8FC08; Thu, 13 Sep 2012 19:47:26 +0000 (UTC) Received: from mailscan.giulioferro.ch (unknown [192.168.115.2]) by mx1.giulioferro.ch (Postfix) with ESMTP id 72A7578FC3; Thu, 13 Sep 2012 21:47:19 +0200 (CEST) X-Virus-Scanned: amavisd-new at example.com Received: from mx1.giulioferro.ch ([192.168.114.4]) by mailscan.giulioferro.ch (mailscan.giulioferro.ch [192.168.115.2]) (amavisd-new, port 10024) with ESMTP id 57UnpgRruTVU; Thu, 13 Sep 2012 21:47:17 +0200 (CEST) Received: from mail.zirakzigil.org (net-93-70-48-129.cust.dsl.vodafone.it [93.70.48.129]) by mx1.giulioferro.ch (Postfix) with ESMTP id A7F2578FB5; Thu, 13 Sep 2012 21:47:17 +0200 (CEST) Received: from ext.zirakzigil.org (unknown [192.168.1.2]) by mail.zirakzigil.org (Postfix) with ESMTP id 9911219C41A; Thu, 13 Sep 2012 10:01:31 +0200 (CEST) X-Virus-Scanned: amavisd-new at zirakzigil.org Received: from mail.zirakzigil.org ([192.168.1.2]) by ext.zirakzigil.org (ext.zirakzigil.org [192.168.1.2]) (amavisd-new, port 10024) with ESMTP id iyHe2vMaTfg5; Thu, 13 Sep 2012 10:01:31 +0200 (CEST) Received: from [192.168.231.11] (ext [192.168.1.2]) (Authenticated sender: auryn@zirakzigil.org) by mail.zirakzigil.org (Postfix) with ESMTPA id ADADF19C416; Thu, 13 Sep 2012 10:01:30 +0200 (CEST) Message-ID: <50523843.8040006@zirakzigil.org> Date: Thu, 13 Sep 2012 21:47:15 +0200 From: Giulio Ferro User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <503BC8F5.3040208@zirakzigil.org> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <504FA735.709@zirakzigil.org> <5050E107.6090403@zirakzigil.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 19:47:27 -0000 On 09/12/2012 10:51 PM, Freddie Cash wrote: > On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel wrote: >> On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash wrote: >>> Thanks for checking. I've used lagg(4) with igb, just not on 9.x. >>> >>> You're right, it seems to be pointing to the igb(4) driver in 9.x >>> compared to < 9.0. >>> >> How do you determine that since it doesn't happen without lagg? I've no >> reports of igb hanging otherwise and its being used extensively. > > Well, I did say "seems to". :) > > igb+lagg worked for us on 8.3. Haven't tried it since moving to 9.0 > and 9-STABLE on those three boxes. > > igb+lagg doesn't work for him on 9.0. Although, I don't recall if > non-LACP options were tried earlier in this thread, or if it's just > the LACP mode that's failing. If one mode works (say failover) and > LACP mode doesn't, that "seems to" point to lagg. Sorry, forgot to mention it. I tried both failover and lacp: neither worked. The switch is a Dell powerconnect 6248 with ports configured for aggragation. I first tried on a 9.1 prerelease, then on a 9.0 release to have everything clean. In both ssh, both as server and as client, become unresponsive and unkillable. The problem might also lie within ssh/d, but I somehow doubt it. I haven't tried other network services. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 14 08:17:53 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6891C106572B; Fri, 14 Sep 2012 08:17:53 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id DFC9D8FC1B; Fri, 14 Sep 2012 08:17:52 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 90FB46A6001; Fri, 14 Sep 2012 10:17:51 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.5/8.14.5) with ESMTP id q8E8HpH9029824; Fri, 14 Sep 2012 10:17:51 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.5/8.14.5/Submit) id q8E8Hp6A029688; Fri, 14 Sep 2012 10:17:51 +0200 (CEST) (envelope-from lars) Date: Fri, 14 Sep 2012 10:17:51 +0200 From: Lars Engels To: Alexander Motin Message-ID: <20120914081751.GA11773@e-new.0x20.net> References: <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> <20120912172525.GU20762@e-new.0x20.net> <5050C6BC.8000307@FreeBSD.org> <20120912174649.GV20762@e-new.0x20.net> <5050DB57.90903@FreeBSD.org> <20120912195821.GW20762@e-new.0x20.net> <5050EBB9.7040202@FreeBSD.org> <20120913074437.GX20762@e-new.0x20.net> <505210A3.8000105@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline In-Reply-To: <505210A3.8000105@FreeBSD.org> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.3-RELEASE-p2 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@FreeBSD.org, Andriy Gapon Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 08:17:53 -0000 --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 13, 2012 at 07:58:11PM +0300, Alexander Motin wrote: > On 13.09.2012 10:44, Lars Engels wrote: > > On Wed, Sep 12, 2012 at 11:08:25PM +0300, Alexander Motin wrote: > >> On 12.09.2012 22:58, Lars Engels wrote: > >>> On Wed, Sep 12, 2012 at 09:58:31PM +0300, Alexander Motin wrote: > >>>> On 12.09.2012 20:46, Lars Engels wrote: > >>>>> On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote: > >>>>>> on 12/09/2012 20:25 Lars Engels said the following: > >>>>>>> On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote: > >>>>>>>> Could you try to play with different eventtimer settings (prefer= ably in current) ? > >>>>>>>> You can use this thread / PR as a guide: > >>>>>>>> http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus= =3D14495 > >>>>>>>> > >>>>>>>> The place where boot stop looks suspiciously close to the place = where timer > >>>>>>>> interrupts should start driving the system. > >>>>>>> > >>>>>>> Yes, that's it! > >>>>>>> Setting kern.eventtimer.timer=3D"i8254" let's the Thinkpad boot = on > >>>>>>> CURRENT with the AC cable inserted. > >>>>>>> > >>>>>> > >>>>>> Please share your sysctl kern.eventtimer output with Alexander. > >>>>>> He will probably ask for some additional information :-) > >>>> > >>>> Sorry if I've missed, but it would be useful to see verbose dmesg in > >>>> situation where system couldn't boot without switching eventtimer. > >>> > >>> No problem. See: http://bsd-geek.de/FreeBSD/IMAG0190.jpg > >> > >> No, I've seen that one and I don't mean it. I mean full verbose dmesg = of > >> successful boot in conditions where system was not booting before > >> without setting kern.eventtimer.timer=3D"i8254". > > > > Ok, sorry. > > Here's a verbose dmesg booting CURRENT without AC power: > > http://bsd-geek.de/FreeBSD/T61_dmesg.boot.works >=20 > Hmm. I see nothing suspicious. HPET driver output is typical for ICH8M=20 > chipset, many of which are working fine in different systems, including= =20 > several mine. There was no significant changes in HPET after 9.0-RELASE= =20 > except r231161. It changed device probe order that increased chance of=20 > interrupt sharing. It should not be a problem, but who knows. You can=20 > try to hint HPET driver specific IRQ 23 (that looks unused) to avoid=20 > sharing by setting hint.hpet.0.allowed_irqs=3D"0x00800000". Setting that didn't change anything. > You've told that problem related to AC power state. Have you compared=20 > dmesg outputs with and without it? Here's are some more dmesgs: http://bsd-geek.de/FreeBSD/T61_dmesg.boot.9.works # PCBSD 9.1-RC1 success= uful boot on AC power http://bsd-geek.de/FreeBSD/T61_dmesg.boot.10.works # FreeBSD 10-CURRENT su= ccessful boot on battery http://bsd-geek.de/FreeBSD/T61_dmesg.boot.9_10.diff # Their diff --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlBS6C8ACgkQKc512sD3afgP4QCgqv3/XtmWgqoexydOkChSTHqy djgAn2+q92h/P4ePxGcErzeKXB1fqZti =0BCO -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 14 12:15:08 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 22549106566B; Fri, 14 Sep 2012 12:15:08 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 3CC108FC16; Fri, 14 Sep 2012 12:15:07 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA10707; Fri, 14 Sep 2012 15:15:04 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <50531FC8.4090307@FreeBSD.org> Date: Fri, 14 Sep 2012 15:15:04 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120830 Thunderbird/15.0 MIME-Version: 1.0 To: Lars Engels References: <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> <20120912172525.GU20762@e-new.0x20.net> <5050C6BC.8000307@FreeBSD.org> <20120912174649.GV20762@e-new.0x20.net> <5050DB57.90903@FreeBSD.org> <20120912195821.GW20762@e-new.0x20.net> <5050EBB9.7040202@FreeBSD.org> <20120913074437.GX20762@e-new.0x20.net> <505210A3.8000105@FreeBSD.org> <20120914081751.GA11773@e-new.0x20.net> In-Reply-To: <20120914081751.GA11773@e-new.0x20.net> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Alexander Motin , freebsd-stable@FreeBSD.org Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 12:15:08 -0000 on 14/09/2012 11:17 Lars Engels said the following: > Here's are some more dmesgs: > > http://bsd-geek.de/FreeBSD/T61_dmesg.boot.9.works # PCBSD 9.1-RC1 successuful boot on AC power > http://bsd-geek.de/FreeBSD/T61_dmesg.boot.10.works # FreeBSD 10-CURRENT successful boot on battery > http://bsd-geek.de/FreeBSD/T61_dmesg.boot.9_10.diff # Their diff > Is it possible to produce two verbose dmesgs for 10 - one on AC power and one on battery? I think that now you can complete booting in both cases. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Fri Sep 14 21:50:00 2012 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DDDEF1065672 for ; Fri, 14 Sep 2012 21:50:00 +0000 (UTC) (envelope-from ck-lists@cksoft.de) Received: from mx1.cksoft.de (mx1.cksoft.de [IPv6:2001:67c:24f8:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 656188FC0A for ; Fri, 14 Sep 2012 21:50:00 +0000 (UTC) Received: from m.cksoft.de (kieku.cksoft.de [62.157.130.195]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.cksoft.de (Postfix) with ESMTP id 2ABF92EB8D2 for ; Fri, 14 Sep 2012 23:49:59 +0200 (CEST) Received: from amavis.ahti.cksoft.de (amavis.ahti.cksoft.de [192.168.64.201]) by m.cksoft.de (Postfix) with ESMTP id D5B61ED011; Fri, 14 Sep 2012 23:49:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at cksoft.de Received: from m.cksoft.de ([192.168.64.204]) by amavis.ahti.cksoft.de (amavis.ahti.cksoft.de [192.168.64.201]) (amavisd-new, port 10024) with ESMTP id 2ynz1NtmtkFb; Fri, 14 Sep 2012 23:49:56 +0200 (CEST) Received: from pohjola.cksoft.de (pohjola.cksoft.de [192.168.64.31]) by m.cksoft.de (Postfix) with ESMTP id 7A277ECFE2; Fri, 14 Sep 2012 23:49:56 +0200 (CEST) Received: by pohjola.cksoft.de (Postfix, from userid 1000) id 70A3F681A6; Fri, 14 Sep 2012 23:49:56 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by pohjola.cksoft.de (Postfix) with ESMTP id 6CC176817A; Fri, 14 Sep 2012 23:49:56 +0200 (CEST) Date: Fri, 14 Sep 2012 23:49:56 +0200 (CEST) From: Christian Kratzer X-X-Sender: ck@pohjola.cksoft.de To: stable@FreeBSD.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-Spammer-Kill-Ratio: 75% MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Christian Kratzer Subject: RELENG_9 i386 cross build on amd64 broken ??? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Christian Kratzer List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 21:50:01 -0000 Hi, I have been trying to do an i386 cross build on RELENG_9 on an amd64 box for an embedded setup. A "make buildworld TARGET=i386" fails on the same source tree that a native amd64 build compiles. ===> usr.bin/kdump (depend) env CPP="cpp" sh /build/RELENG_9/src/usr.bin/kdump/mkioctls /usr/obj/i386.i386/build/RELENG_9/src/tmp/usr/include > ioctl.c *** [ioctl.c] Error code 1 Stop in /build/RELENG_9/src/usr.bin/kdump. *** [depend] Error code 1 Stop in /build/RELENG_9/src/usr.bin. *** [usr.bin.depend__D] Error code 1 Stop in /build/RELENG_9/src. *** [_depend] Error code 1 Stop in /build/RELENG_9/src. *** [buildworld] Error code 1 Stop in /build/RELENG_9/src. This works in RELENG_8 but has been failing on RELENG_9 for some time now. My last successfull crossbuild of i386 on amd64 was on May 15, 2012. Does above ring any bells with anyone ? Greetings Christian -- Christian Kratzer CK Software GmbH Email: ck@cksoft.de Wildberger Weg 24/2 Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart Web: http://www.cksoft.de/ Geschaeftsfuehrer: Christian Kratzer From owner-freebsd-stable@FreeBSD.ORG Sat Sep 15 04:41:20 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD424106566C for ; Sat, 15 Sep 2012 04:41:20 +0000 (UTC) (envelope-from crtmike@gmx.us) Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id 9BC358FC1C for ; Sat, 15 Sep 2012 04:41:20 +0000 (UTC) Received: (qmail invoked by alias); 15 Sep 2012 04:41:13 -0000 Received: from unknown (EHLO bsd.laptop.mike) [124.89.80.227] by mail.gmx.com (mp-us002) with SMTP; 15 Sep 2012 00:41:13 -0400 X-Authenticated: #137061016 X-Provags-ID: V01U2FsdGVkX19Ft49xnCZFB9VT+zVfSn/a0a3gimEs5R/ny1vXeO WvLeztT7qQ57Nt Message-ID: <505406DF.6080205@gmx.us> Date: Sat, 15 Sep 2012 12:41:03 +0800 From: Mike Manilone User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120910 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: how to update ports while using pkgng? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 04:41:21 -0000 Hi, I'm using ports with pkgng enabled. But I found that portmaster won't work. Is there any way to update ports? Thanks! Sincerely, Mike Manilone From owner-freebsd-stable@FreeBSD.ORG Sat Sep 15 04:54:31 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2E59A106564A for ; Sat, 15 Sep 2012 04:54:31 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9B1898FC12 for ; Sat, 15 Sep 2012 04:54:30 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so3890235lbb.13 for ; Fri, 14 Sep 2012 21:54:29 -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=s8xrkMxYNcw6MFHtvNqQt7MLaRR07QnGzhjvqhEF5to=; b=xnF/djRHwzbFpNRZscwgcz4MFBOF+oO/FzhcNB9R6PweQ1lGJuD8GzUPNCX3m5g7XX WlJ8BvfJX+xbiFfypmbgHbeNwJR3WANFexU0b5vRaVkvtM7ZlxeAhsRJu/vCYO0vNsfj JPAOYDcwYqI4PDC9EkSmtdAx344b/k9dR267n5aefHjCwotKtRNAlSfqjd5lsi0P6awq p08/Tq7Lyx+ZSHR+0b8phhcOVDPMRHBWVqxypLkK5ZpVr8T9sAOeQKu9yP9aZ/PmQrEW yV+c2DrJws+Hg0Lre9yKmieRrSZhyxpbndc6h9FKfI3qwv1sUyTMRZveVJqO+IKZK4O9 n9fQ== MIME-Version: 1.0 Received: by 10.112.103.167 with SMTP id fx7mr1794703lbb.44.1347684869243; Fri, 14 Sep 2012 21:54:29 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Fri, 14 Sep 2012 21:54:29 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Fri, 14 Sep 2012 21:54:29 -0700 (PDT) In-Reply-To: <505406DF.6080205@gmx.us> References: <505406DF.6080205@gmx.us> Date: Fri, 14 Sep 2012 21:54:29 -0700 Message-ID: From: Freddie Cash To: Mike Manilone Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: how to update ports while using pkgng? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 04:54:31 -0000 Read the pkgng faq online. There's a link to a patch for portmaster, and info on what to add to make.conf. On Sep 14, 2012 9:42 PM, "Mike Manilone" wrote: > Hi, > > I'm using ports with pkgng enabled. But I found that portmaster won't > work. Is there any way to update ports? Thanks! > > Sincerely, > Mike Manilone > ______________________________**_________________ > 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 Sat Sep 15 05:52:15 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C87BC106566C for ; Sat, 15 Sep 2012 05:52:15 +0000 (UTC) (envelope-from iveyeorgiv@yahoo.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 6E4AE8FC08 for ; Sat, 15 Sep 2012 05:52:15 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TClId-0002sh-2o for freebsd-stable@freebsd.org; Fri, 14 Sep 2012 22:52:15 -0700 Date: Fri, 14 Sep 2012 22:52:15 -0700 (PDT) From: iveyeorg To: freebsd-stable@freebsd.org Message-ID: <1347688335080-5743795.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Abercrombie jacket is very best in case you have the form of a greater program X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 05:52:15 -0000 There isn't any doubt that you will seem excellent Abercrombie shirts. http://www.abercrombieandfitchoutletschweiz.eu abercrombie clothing is extremely stylish and elegant, so you can make use of them confident and classy daily. On the other hand, you can still choose a leather shirt, you need to think about the form of your procedure. Made a decision the most effective shirt together with the form of your program, it is possible to make sure you do not seem excellent wearing luxurious informal Abercrombie clothes. So, right here are several of the primary recommendations on how to decide on a appropriate Abercrombie informal shirt, you can shape your process. Initial, http://www.abercrombieandfitchoutletschweiz.eu abercrombie and fitch garments, specifically its assortment of shirts, most are made for people using a thinner physique. Consequently, should you have a slim process, then you definitely is not going to find it tough to choose a suitable Abercrombie shirts. Nonetheless, if you'd like to hide their lanky form, you ought to not use leather shirt is accurate. Restricted the right T-shirt will hug your technique, the procedure will only emphasize your slender procedure. In an effort to receive the top result, you'll want to start using a slight reduction within the Abercrombie and Fitch shirts. Additionally it is advised to implement the deeper the shirt color to produce your program look larger. However, when you've got a plus tagging process, then it's ideal to buy Abercrombie T-shirts, a bigger dimension versus actual physique proportions. On this way, your Abercrombie and Fitch shirts fit flawlessly, so that you ought to appear fantastic wearing it. For women, greater breasts, it really is ideal if they buy Abercrombie button press V-neck or primary Abercrombie T-shirt, V-neck polo shirt. It is also most effective to avoid words or across your chest butterfly knot blouse. Lighting shadow Abercrombie jacket is very best in case you have the form of a greater program, so that you may seem slimmer. It is best to go get this influence with the black and shadows Abercrombie apparel. By way of example, you'll be able to use the deeper shadows jeans, it has a very light shadow Abercrombie shirt. In usual conditions, Abercrombie and Fitch T-shirt is designed for informal activities. But it is possible to use them as partial official fitted with the finest color and size decision. One example is, a khaki shirt will appear quite experienced, when you put it using the black shadow of casual pants. Guarantee you tuck the shirt, to enhance the appear of one's informal use of partial official. Which can be the most beneficial to avoid decreasing appropriate and lengthy T-shirt, so that you may prevent a sloppy appear. It is best to also not utilize the technique of tight-fitting shirt, mainly because it looks pretty formal. Only pick out the correct dimensions Abercrombie shirt for the system, so you can get a partial official look stylish informal tools. Abercrombie leading ideal informal apparel. You only ought to decide on the proper size, it will likely be the ideal shirt to your process form. It is best to also discover the way to utilize the design and color of one's http://www.abercrombieandfitchoutletschweiz.eu abercrombie and fitch schweiz in Brussels, so that it's going to seem excellent in your program. Correct design and style, and establish the best size Abercrombie and Fitch shirt wearing, you could use your informal use in some official occasions or to work with it together with your official jeans and shoes. About Abercrombie clothing, you want to extra http://www.abercrombieandfitchoutletschweiz.eu. ----- Have a good time in our abercrombie shop.We offer more fashion abercrombie outlet schweiz outlet styles and cheap abercrombie and fitch outlet for women,men and. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Abercrombie-jacket-is-very-best-in-case-you-have-the-form-of-a-greater-program-tp5743795.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@FreeBSD.ORG Sat Sep 15 06:10:15 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D690E106564A for ; Sat, 15 Sep 2012 06:10:15 +0000 (UTC) (envelope-from jeannettje@yahoo.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id B6C9D8FC0A for ; Sat, 15 Sep 2012 06:10:15 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TCla2-00040u-Ut for freebsd-stable@freebsd.org; Fri, 14 Sep 2012 23:10:15 -0700 Date: Fri, 14 Sep 2012 23:10:14 -0700 (PDT) From: jeannett To: freebsd-stable@freebsd.org Message-ID: <1347689414950-5743797.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Nike no cost run footwear will need to meet selected X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 06:10:15 -0000 To buy thinking of operating http://www.freerunshoesaustralia.org nike free run shoes adult, adult working footwear to generate a significant decision. This is a really private choice, and everybody who's a runner-up. They can purchase other's stuff. Long-distance runners on the exact same desires, and maintain it a thing you may speedily choose. Nike absolutely free run footwear specialization above time. Once there are numerous kinds of http://www.freerunshoesaustralia.org nike free run footwear and athletes have access to some sports shoes or tennis Nike no cost run shoes. A lot of movement, many people are going to be employing a similar form of shoes. This isn't the greatest coming, rubber soles, but at least this is a phase forward. Factors have undergone a tremendous alter. Now, virtually any sport has its very own Nike free of charge run footwear. Who run a growing number of Nike cost-free run footwear. Expanding the fashion number and type of running footwear. These footwear Nike free run to meet the certain wants of various sorts of gamers. Market the demand for these solutions and also to better comprehend how your body will work. Wearer Nike no cost run running footwear, Nike no cost run footwear will need to meet selected specifications. A Nike absolutely free run performance-enhancing demands. One more will need will be to be pleased could be the prevention of harm. Who run usually attempted to avoid the occurrence of chronic injury. The event highlighted the feet and legs. Just about every step-by-step foot for the ground. Nike free run shoes work to mitigate the affect of your results. All entrants, they run a special way. People today have various amounts arch in their feet. You'll find also variations, wherein the part of the foot hits the ground 1st. You can find even some distinctions which side to perform to begin with. Have to effectively take care of these differences. Suitable footwear by these distinctions. Companies to create solutions designed to meet the demands of the unique variations of operating. Nike no cost run footwear revenue to grownup athletes commitments, in an effort to meet their requirements. The interests of all of this, but the fact that many people are aware which they must acquire hindered. Many people who are not qualified or significant runner-up, and nobody knew the way that they run, and what they really need to buy. Really should be assessed in advance of pick Nike free of charge run shoe design runner-foot making. A spot to get retailers cater on the runner-up. Workers, encounter, observation and evaluation of purchaser needs. You can use a device, is often a treadmill. The high quality evaluation will give persons the feeling in the Nike free run footwear the way to get the job done about the street. Many prior to you may try out to generate a choice. This is certainly also conducive on the the prospective http://www.freerunshoesaustralia.org nike free australia operating shoes on the net adult. There are several assessment web sites. It is achievable to acquire all the data, can assist for making this vital purchase. This is not hurry the procedure. Appropriate footwear Nike free of charge run features a good deal to accomplish using the superior and expertise in the movement. Nike totally free run footwear, want additional http://www.freerunshoesaustralia.org. ----- NIKE FREE series can bring a perfect balance, nike free shoes australia awakened the people's feet, so that people like running barefoot on the ground, nike free run australia store and at the same time with the best protection to the feet. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Nike-no-cost-run-footwear-will-need-to-meet-selected-tp5743797.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@FreeBSD.ORG Sat Sep 15 11:48:04 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F730106564A; Sat, 15 Sep 2012 11:48:04 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mx1.freebsd.org (Postfix) with ESMTP id D5AAE8FC08; Sat, 15 Sep 2012 11:48:03 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 943B56A6001; Sat, 15 Sep 2012 13:48:02 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.5/8.14.5) with ESMTP id q8FBm2Ng000320; Sat, 15 Sep 2012 13:48:02 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.5/8.14.5/Submit) id q8FBm2X0099221; Sat, 15 Sep 2012 13:48:02 +0200 (CEST) (envelope-from lars) Date: Sat, 15 Sep 2012 13:48:02 +0200 From: Lars Engels To: Andriy Gapon Message-ID: <20120915114802.GL11773@e-new.0x20.net> References: <20120912172525.GU20762@e-new.0x20.net> <5050C6BC.8000307@FreeBSD.org> <20120912174649.GV20762@e-new.0x20.net> <5050DB57.90903@FreeBSD.org> <20120912195821.GW20762@e-new.0x20.net> <5050EBB9.7040202@FreeBSD.org> <20120913074437.GX20762@e-new.0x20.net> <505210A3.8000105@FreeBSD.org> <20120914081751.GA11773@e-new.0x20.net> <50531FC8.4090307@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OGLMwEELQbPC02lM" Content-Disposition: inline In-Reply-To: <50531FC8.4090307@FreeBSD.org> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.3-RELEASE-p2 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Alexander Motin , freebsd-stable@FreeBSD.org Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 11:48:04 -0000 --OGLMwEELQbPC02lM Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 14, 2012 at 03:15:04PM +0300, Andriy Gapon wrote: > on 14/09/2012 11:17 Lars Engels said the following: > > Here's are some more dmesgs: > >=20 > > http://bsd-geek.de/FreeBSD/T61_dmesg.boot.9.works # PCBSD 9.1-RC1 suc= cessuful boot on AC power > > http://bsd-geek.de/FreeBSD/T61_dmesg.boot.10.works # FreeBSD 10-CURREN= T successful boot on battery > > http://bsd-geek.de/FreeBSD/T61_dmesg.boot.9_10.diff # Their diff > >=20 >=20 > Is it possible to produce two verbose dmesgs for 10 - one on AC power and= one on > battery? > I think that now you can complete booting in both cases. Yes, they're here: http://bsd-geek.de/FreeBSD/T61_dmesg.boot.10.works http://bsd-geek.de/FreeBSD/T61_dmesg.boot.10_i8254.works http://bsd-geek.de/FreeBSD/T61_dmesg.boot.10_eventtimer.diff It shows also that with i8254 I'm having USB problems. --OGLMwEELQbPC02lM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlBUavIACgkQKc512sD3afig9ACffExGpXzuDEjYh5ZX4iqvrBg1 pxkAoJaIw67/0JUg1vIhmM/wz83qeh95 =kls6 -----END PGP SIGNATURE----- --OGLMwEELQbPC02lM-- From owner-freebsd-stable@FreeBSD.ORG Sat Sep 15 11:56:11 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 848B0106564A for ; Sat, 15 Sep 2012 11:56:11 +0000 (UTC) (envelope-from gondim@bsdinfo.com.br) Received: from zeus.linuxinfo.com.br (zeus.linuxinfo.com.br [186.193.48.13]) by mx1.freebsd.org (Postfix) with ESMTP id 3DC3F8FC1E for ; Sat, 15 Sep 2012 11:56:11 +0000 (UTC) Received: from zeus.linuxinfo.com.br (zeus.linuxinfo.com.br [127.0.0.1]) by zeus.linuxinfo.com.br (Postfix) with ESMTP id 8799E466A452 for ; Sat, 15 Sep 2012 08:47:42 -0300 (BRT) X-Virus-Scanned: amavisd-new at zeus.linuxinfo.com.br Received: from zeus.linuxinfo.com.br ([127.0.0.1]) by zeus.linuxinfo.com.br (zeus.linuxinfo.com.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sL89YdF_5Hbe for ; Sat, 15 Sep 2012 08:47:40 -0300 (BRT) Received: from [127.0.0.1] (unknown [186.193.48.8]) by zeus.linuxinfo.com.br (Postfix) with ESMTPSA id 4E694466A422 for ; Sat, 15 Sep 2012 08:47:39 -0300 (BRT) Message-ID: <50546AF9.4060505@bsdinfo.com.br> Date: Sat, 15 Sep 2012 08:48:09 -0300 From: Marcelo Gondim User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <505406DF.6080205@gmx.us> In-Reply-To: <505406DF.6080205@gmx.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: how to update ports while using pkgng? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 11:56:11 -0000 Em 15/09/2012 01:41, Mike Manilone escreveu: > Hi, > > I'm using ports with pkgng enabled. But I found that portmaster won't > work. Is there any way to update ports? Thanks! Hi, I use "portsnap fetch update" and "portmaster" to update my ports. Gondim From owner-freebsd-stable@FreeBSD.ORG Sat Sep 15 12:50:10 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAECA1065677; Sat, 15 Sep 2012 12:50:10 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2365D8FC08; Sat, 15 Sep 2012 12:50:09 +0000 (UTC) Received: by weyx56 with SMTP id x56so3468363wey.13 for ; Sat, 15 Sep 2012 05:50:08 -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=SsfJ72yD4jD8VnVpNXEdGeexSz9vNa4rC3fBkbd3iXc=; b=WoO/AsWH+CF88KafhbLCcYeNPGP7zkkVcB/m6WzXlirCbeNQrrShvi4LHsl54jvjMc 5ocdICuOoiH3vkDcygYCAYq34MusXFgoSklnqQP6C1BbePMg6DOKrDys4/VtyUZbzbBR V9By3/YLLwWM0Pr+NOK5wferajjLYDH5UPxueWaSCpkrWWR2U3IIc29Uemj2x0B8Rj9i zykAEEng0wvCLsmOZwAD5ImvMFjpAoiDGMtLAiNgfLYYZRAGThhVPX3/647yW9HeYDud l4/4uBNQmBwbIH4RW7vs0VbDgW35k1khDb3tc2t+22xKHY0gT0gqechX5pJaCXXfpbxq hLQQ== Received: by 10.217.1.206 with SMTP id n56mr3054949wes.151.1347713408854; Sat, 15 Sep 2012 05:50:08 -0700 (PDT) Received: from localhost ([95.69.174.83]) by mx.google.com with ESMTPS id hv8sm9172002wib.0.2012.09.15.05.50.06 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 15 Sep 2012 05:50:07 -0700 (PDT) Sender: Mikolaj Golub Date: Sat, 15 Sep 2012 15:50:05 +0300 From: Mikolaj Golub To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20120915125003.GA91163@gmail.com> References: <504D10A7.1070701@quip.cz> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <504D10A7.1070701@quip.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Hartmut Brandt , freebsd-stable@freebsd.org Subject: Re: bsnmpd always died on HDD detach X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 12:50:11 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Sep 09, 2012 at 11:56:55PM +0200, Miroslav Lachman wrote: > I am running bsnmpd with basic snmpd.config (only community and location > changed). > > When there is a problem with HDD and disk disapeared from ATA channel > (eg.: disc physically removed) the bsnmpd always dumps core: > > kernel: pid 1188 (bsnmpd), uid 0: exited on signal 11 (core dumped) > > I see this for a long rime on all releases of 7.x and 8.x branches (i386 > and amd64). I did not tested 9.x. Ok, I was able to to reproduce this under qemu doing atacontrol detach ata1 It crashes in snmp_hostres module, in refresh_device_tbl->refresh_disk_storage_tbl->disk_OS_get_ATA_disks when traversing device_map list and dereferencing map->entry_p, which is NULL here. device_map table is used for consistent device table indexing. refresh_device_tbl(), refresh routine for hrDeviceTable, checks the list of available devices and calls device_entry_delete() for devices that have gone. It does not remove the entry from device_map table, but just sets entry_p to NULL for it (to preserve index reuse by another device). Then refresh_disk_storage_tbl() is called, which in turn calls disk_OS_get_ATA_disks(); disk_OS_get_MD_disks(); disk_OS_get_disks(); and it crashes in disk_OS_get_ATA_disks() when the removed map entry is dereferenced. I am attaching the patch that fixes the issue for me. I was wandering why the issue was not observed after md device removal, as disk_OS_get_MD_disks() did the same things. It has turned out that hostres just does not see md devices, so this function is currently useless. hostres gets devices from devinfo(3), which does not return md devices. disk_OS_get_disks() calls kern.disks sysctl to get the list of disks, and uses device_map differently, so it is not affected. -- Mikolaj Golub --ZGiS0Q5IWpPtfppv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: inline; filename="hostres_diskstorage_tbl.c.skip.patch" Index: usr.sbin/bsnmpd/modules/snmp_hostres/hostres_diskstorage_tbl.c =================================================================== --- usr.sbin/bsnmpd/modules/snmp_hostres/hostres_diskstorage_tbl.c (revision 240529) +++ usr.sbin/bsnmpd/modules/snmp_hostres/hostres_diskstorage_tbl.c (working copy) @@ -287,6 +287,9 @@ disk_OS_get_ATA_disks(void) /* Walk over the device table looking for ata disks */ STAILQ_FOREACH(map, &device_map, link) { + /* Skip deleted entries. */ + if (map->entry_p == NULL) + continue; for (found = lookup; found->media != DSM_UNKNOWN; found++) { if (strncmp(map->name_key, found->dev_name, strlen(found->dev_name)) != 0) @@ -345,6 +348,9 @@ disk_OS_get_MD_disks(void) /* Look for md devices */ STAILQ_FOREACH(map, &device_map, link) { + /* Skip deleted entries. */ + if (map->entry_p == NULL) + continue; if (sscanf(map->name_key, "md%d", &unit) != 1) continue; --ZGiS0Q5IWpPtfppv-- From owner-freebsd-stable@FreeBSD.ORG Sat Sep 15 21:44:19 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CAA211065670 for ; Sat, 15 Sep 2012 21:44:19 +0000 (UTC) (envelope-from jamie@kode5.net) Received: from kontrol.kode5.net (kontrol.kode5.net [80.229.5.32]) by mx1.freebsd.org (Postfix) with ESMTP id 3D3DA8FC0A for ; Sat, 15 Sep 2012 21:44:18 +0000 (UTC) Received: from kontrol.kode5.net (localhost [127.0.0.1]) by kontrol.kode5.net (8.14.5/8.14.5) with ESMTP id q8FLiALE003013 for ; Sat, 15 Sep 2012 22:44:10 +0100 (BST) (envelope-from jamie@kode5.net) Received: (from jamie@localhost) by kontrol.kode5.net (8.14.5/8.14.5/Submit) id q8FLiANV003012 for freebsd-stable@freebsd.org; Sat, 15 Sep 2012 22:44:10 +0100 (BST) (envelope-from jamie@kode5.net) X-Authentication-Warning: kontrol.kode5.net: jamie set sender to jamie@kode5.net using -f Date: Sat, 15 Sep 2012 22:44:10 +0100 From: Jamie Paul Griffin To: freebsd-stable@freebsd.org Message-ID: <20120915214410.GA1710@kontrol.kode5.net> References: <505406DF.6080205@gmx.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: x-operating-system: FreeBSD 9.1-PRERELEASE amd64 x-pgp-fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38 x-pgp-key: 1D31DC38 User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.5 at kontrol.kode5.net X-Virus-Status: Clean Subject: Re: how to update ports while using pkgng? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 21:44:19 -0000 [ Freddie Cash wrote on Fri 14.Sep'12 at 21:54:29 -0700 ] > Read the pkgng faq online. There's a link to a patch for portmaster, and > info on what to add to make.conf. Can I ask: why is it still necessary for us to patch portmaster, can this not be implemented using an option during `make config` when installing portmaster or updating it, etc.? From owner-freebsd-stable@FreeBSD.ORG Sat Sep 15 21:47:17 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A408C106566C for ; Sat, 15 Sep 2012 21:47:17 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 706468FC16 for ; Sat, 15 Sep 2012 21:47:17 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so7884935pbb.13 for ; Sat, 15 Sep 2012 14:47:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=mQ1AgtmlF216IJQZIP4hAZ5adLvJuOO8y79NzC/3lnE=; b=tBonwFeymK7zrzV2DQm8E1dBJsJjqAaJpk4EK5aETXpGVb9BH36SPgp2mcqRnRGHJB LYEWB1/cxPQk4rxjR/oqYefEfum9NLH70f9jb4lUYVJJm/HSFgHJcLdjLH01vyIbX0LB puOM7lEjzuU0TQmaY8sSDXRYrzrSZ3rROYl9s= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=mQ1AgtmlF216IJQZIP4hAZ5adLvJuOO8y79NzC/3lnE=; b=IaRbsviWY1xFgXlRcatcMocJEezVVQTIaKk6JXsaF8mfekxtJcsdepRG5QAN6ecpfk oOWIQAucZ6F3YaKT8tDJevtAR2q3RQ7Mmy7FJMCyI/O+Nxio+AcaK1grbEK6Fwas2n4E 2KR3bAYW5vGG36iJUbRVfZ1XH2Xxu1th8rjuyBRL4bHt+Cb5pbRFigfas8SAe5ClTtBB ZMsaiPNMLPxSZK7+0c2U9ue8jbiqHFSsBgRBKzfkTvhQ7xdZ0iJQdI/6pO85XWgGcqZo lv2qzxhshz+C/w+EfZGE5Fm0UihcXMkDEDAQxiXhh753Zr1BWDXD3Wv0mMdcJvi/cTbH xP5w== Received: by 10.68.242.231 with SMTP id wt7mr12149178pbc.99.1347745636947; Sat, 15 Sep 2012 14:47:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.87.41 with HTTP; Sat, 15 Sep 2012 14:46:46 -0700 (PDT) In-Reply-To: <20120915214410.GA1710@kontrol.kode5.net> References: <505406DF.6080205@gmx.us> <20120915214410.GA1710@kontrol.kode5.net> From: Eitan Adler Date: Sat, 15 Sep 2012 17:46:46 -0400 Message-ID: To: Jamie Paul Griffin Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQlwDteukNPzOWBpF5Rm2GT9OTQCCo7XU4UyGLK7eSaAbHZ1e6p34GQOQ9lvAVK9qY/wPNlm Cc: freebsd-stable@freebsd.org Subject: Re: how to update ports while using pkgng? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 21:47:17 -0000 On 15 September 2012 17:44, Jamie Paul Griffin wrote: > [ Freddie Cash wrote on Fri 14.Sep'12 at 21:54:29 -0700 ] > >> Read the pkgng faq online. There's a link to a patch for portmaster, and >> info on what to add to make.conf. > > Can I ask: why is it still necessary for us to patch portmaster, can this not be implemented using an option during `make config` when installing portmaster or updating it, etc.? The maintainer of portmaster does not believe the patch to be of sufficient quality to make it into the mainstream release. It should be considered a "third party hack" for now. -- Eitan Adler