From owner-freebsd-stable@freebsd.org Sun Sep 11 21:54:02 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF74EBD60EE for ; Sun, 11 Sep 2016 21:54:02 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (mail.farley.org [IPv6:2001:470:1f07:14d3:2::11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B23AAEC5 for ; Sun, 11 Sep 2016 21:54:02 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (thor.farley.org [IPv6:2001:470:1f07:14d3:1:0:0:5]) by mail.farley.org (8.15.2/8.15.2) with ESMTP id u8BLs00W016393 for ; Sun, 11 Sep 2016 17:54:00 -0400 (EDT) (envelope-from scf@FreeBSD.org) Date: Sun, 11 Sep 2016 17:54:00 -0400 (EDT) From: "Sean C. Farley" To: freebsd-stable@FreeBSD.org Subject: Slow CD access until primed by readcd (cdrtools) Message-ID: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.farley.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Sep 2016 21:54:03 -0000 I ran into an issue with at least a few CD's where the access to them mounted as cd9660 was very slow. dd of /dev/cd0 was also slow. However, if I run readcd (from cdrtools-devel-3.02a06,1) at least once, which would run at full speed, then any access to the disc whether mounted or not is at full speed. I do not recall this happening in the past, but this is with a newer computer (i.e., newer drive). It appears to be that something is determining the full speed correctly when readcd is run and is keeping that state until the disc is removed while mounting or running dd against the drive does not. OS: 10.3-STABLE (r304921) amd64. pass0: Removable CD-ROM SCSI device pass0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO 8192bytes) Any ideas? Sean -- scf@FreeBSD.org From owner-freebsd-stable@freebsd.org Mon Sep 12 09:39:14 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7CC1BD6114 for ; Mon, 12 Sep 2016 09:39:14 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D2E7FC87 for ; Mon, 12 Sep 2016 09:39:14 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id CE98DBD6112; Mon, 12 Sep 2016 09:39:14 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE44DBD6111 for ; Mon, 12 Sep 2016 09:39:14 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8FCAEC85; Mon, 12 Sep 2016 09:39:14 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bjNhh-000Ahz-AU; Mon, 12 Sep 2016 12:39:05 +0300 Date: Mon, 12 Sep 2016 12:39:05 +0300 From: Slawa Olhovchenkov To: Andriy Gapon Cc: Konstantin Belousov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160912093905.GP34394@zxy.spb.ru> References: <20151212130615.GE70867@zxy.spb.ru> <20151212133513.GL82577@kib.kiev.ua> <20160901112724.GX88122@zxy.spb.ru> <20160901114500.GJ83214@kib.kiev.ua> <20160901121300.GZ88122@zxy.spb.ru> <4ba05c00-f737-f562-553d-a7fa59145768@FreeBSD.org> <20160904151415.GE83214@kib.kiev.ua> <20160904162926.GF83214@kib.kiev.ua> <358ed414-9da6-ac29-55fc-6d7be680c2ce@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <358ed414-9da6-ac29-55fc-6d7be680c2ce@FreeBSD.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2016 09:39:15 -0000 On Sun, Sep 04, 2016 at 08:14:07PM +0300, Andriy Gapon wrote: > On 04/09/2016 19:29, Konstantin Belousov wrote: > > This is possible, of course. But it would not affect "SMP: Added CPU ..." > > lines. > > Well, looking at the code it seems that only if mptable is used, then those > lines are expected to correctly identify a BSP. With MADT there is no > information to identify the BSP and that is supposed to happen in cpu_mp_start(). > > > static void > madt_add_cpu(u_int acpi_id, u_int apic_id, u_int flags) > { > struct lapic_info *la; > > /* > * The MADT does not include a BSP flag, so we have to let the > * MP code figure out which CPU is the BSP on its own. > */ > ... > > In other words, those "SMP: Added CPU ..." are truly a cosmetic issue. > And it's my guess (just a guess) that BSP LAPIC ID is incorrect in the > problematic configuration. For next day or two I am have new server with same hardware before put in prodution. Can I do some test for you? From owner-freebsd-stable@freebsd.org Mon Sep 12 13:45:39 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9EB15BD7DEE for ; Mon, 12 Sep 2016 13:45:39 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 88D6DCF8 for ; Mon, 12 Sep 2016 13:45:39 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 849E7BD7DED; Mon, 12 Sep 2016 13:45:39 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84448BD7DEC for ; Mon, 12 Sep 2016 13:45:39 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id DA5A2CF7 for ; Mon, 12 Sep 2016 13:45:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA17770; Mon, 12 Sep 2016 16:45:30 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bjRYA-0003Iy-Ia; Mon, 12 Sep 2016 16:45:30 +0300 Subject: Re: X2APIC support To: Slawa Olhovchenkov References: <20151212130615.GE70867@zxy.spb.ru> <20151212133513.GL82577@kib.kiev.ua> <20160901112724.GX88122@zxy.spb.ru> <20160901114500.GJ83214@kib.kiev.ua> <20160901121300.GZ88122@zxy.spb.ru> <4ba05c00-f737-f562-553d-a7fa59145768@FreeBSD.org> <20160904151415.GE83214@kib.kiev.ua> <20160904162926.GF83214@kib.kiev.ua> <358ed414-9da6-ac29-55fc-6d7be680c2ce@FreeBSD.org> <20160912093905.GP34394@zxy.spb.ru> Cc: Konstantin Belousov , stable@FreeBSD.org From: Andriy Gapon Message-ID: Date: Mon, 12 Sep 2016 16:44:09 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160912093905.GP34394@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2016 13:45:39 -0000 On 12/09/2016 12:39, Slawa Olhovchenkov wrote: > On Sun, Sep 04, 2016 at 08:14:07PM +0300, Andriy Gapon wrote: > >> On 04/09/2016 19:29, Konstantin Belousov wrote: >>> This is possible, of course. But it would not affect "SMP: Added CPU ..." >>> lines. >> >> Well, looking at the code it seems that only if mptable is used, then those >> lines are expected to correctly identify a BSP. With MADT there is no >> information to identify the BSP and that is supposed to happen in cpu_mp_start(). >> >> >> static void >> madt_add_cpu(u_int acpi_id, u_int apic_id, u_int flags) >> { >> struct lapic_info *la; >> >> /* >> * The MADT does not include a BSP flag, so we have to let the >> * MP code figure out which CPU is the BSP on its own. >> */ >> ... >> >> In other words, those "SMP: Added CPU ..." are truly a cosmetic issue. >> And it's my guess (just a guess) that BSP LAPIC ID is incorrect in the >> problematic configuration. > > For next day or two I am have new server with same hardware before put > in prodution. > Can I do some test for you? > >From my earlier email: "my guess can be checked by adding a printf to cpu_mp_start() right after boot_cpu_id assignment". -- Andriy Gapon From owner-freebsd-stable@freebsd.org Mon Sep 12 15:23:41 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E471BBD837B for ; Mon, 12 Sep 2016 15:23:41 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 98B6D6AA for ; Mon, 12 Sep 2016 15:23:41 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: by mail-vk0-x229.google.com with SMTP id 16so120024980vko.2 for ; Mon, 12 Sep 2016 08:23:41 -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; bh=N4ZhJQg2EQt0fisKJnxd6ErWKff4sFhdRtKRXqAhZAg=; b=xtOCDMp3dOBmGb1rz3xtySJrEmEvRlQMUj6RRN0hvv7FguK4ycD9WlNu5J3GDp+nFB /ND/W2UOLLfRO0+AYpAaPJpJ9WM5koVaqwyUC/w7ir0r8SskKTh27ZnmQUp/WuCachz3 7HGUisjt1e9L/90otvML+lFk9xz8QMZrTuLmA5j5J5QsBYiBP411wsdX+iyqOufO49ZH oBrxLJZoZMhqWSWy+INd5ivxwrs+I/xCJ81AYYzLYzWenIL+F4u08/SqcpS+V1Gg7uw8 C0WYgIJxy4HpkVysWMb39DXLJIRW5f/rIfIZelWKJmFpKC3TOUWMgOGU8DvGE7U2c4Xw +R9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=N4ZhJQg2EQt0fisKJnxd6ErWKff4sFhdRtKRXqAhZAg=; b=MPWfSnr6Ux2ganghrFARTlA3Lw7HMvBnvf/U4SwvaBqlc+93J5Id/Vd0FXXEvOSH6P FNMD7XXuvRaiR2Mv2EZ2hi0/OxpnJ0Z2pw/mlHmTqO53h6clwrqDTfD3T1hcWaqjGx5z YtCLagGlGPFB3n95enVgEzjihyPq5r/xzD85stiYCSjwUrubL/BVO+ZvuKFR+Op6DLdV tmTjR47HvS1I+fD9I9xLrdUMtgESEGy+mrFXpyeo6fllctaAEjYyhqYqr+vpysvDRft/ RWaDFeocdMb6FZc+nAjTfhsC2TccDlKZxoLPL08bPELPxTV8y4Y3BxI6gmlk4a2SnGoD UqFA== X-Gm-Message-State: AE9vXwMBPaNJO1ZgJiV2qXX1or7jBEydScZmdnGv5PRD41kiCCVNflYBzlDwh3h1s4mDunYKG48v7l/OQfkB5Q== X-Received: by 10.31.136.70 with SMTP id k67mr13139213vkd.13.1473693819965; Mon, 12 Sep 2016 08:23:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.83.106 with HTTP; Mon, 12 Sep 2016 08:23:39 -0700 (PDT) In-Reply-To: References: <4996AF96-76BA-47F1-B328-D4FE7AC777EE@sarenet.es> From: Jim Harris Date: Mon, 12 Sep 2016 08:23:39 -0700 Message-ID: Subject: Re: Intel NVMe troubles? To: Borja Marcos Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2016 15:23:42 -0000 On Mon, Aug 1, 2016 at 11:49 AM, Jim Harris wrote: > > > On Mon, Aug 1, 2016 at 7:38 AM, Borja Marcos wrote: > >> >> > >> > It looks like all of the TRIM commands are formatted properly. The >> failures do not happen until about 10 seconds after the last TRIM to eac= h >> drive was submitted, and immediately before TRIMs start to the next driv= e, >> so I'm assuming the failures are for the the last few TRIM commands but >> cannot say for sure. Could you apply patch v2 (attached) which will dum= p >> the TRIM payload contents inline with the failure messages? >> >> Sure, this is the complete /var/log/messages starting with the system >> boot. Before booting I destroyed the pool >> so that you could capture what happens when booting, zpool create, etc. >> >> Remember that the drives are in LBA format #3 (4 KB blocks). As far as I >> know that=E2=80=99s preferred to the old 512 byte blocks. >> >> Thank you very much and sorry about the belated response. > > > Hi Borja, > > Thanks for the additional testing. This has all of the detail that I nee= d > for now. > > -Jim > > > There is an updated DCT 3.0.2 at: https://downloadcenter.intel. com/download/26221/Intel-SSD-Data-Center-Tool which has a fix for this issue. Borja has already downloaded this update and confirmed it looks good so far. Posting the update and results here so it is archived on the STABLE mailing list. Thanks, -Jim From owner-freebsd-stable@freebsd.org Mon Sep 12 16:44:16 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93474BD802C for ; Mon, 12 Sep 2016 16:44:16 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7DFBF858 for ; Mon, 12 Sep 2016 16:44:16 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 7D5A4BD802B; Mon, 12 Sep 2016 16:44:16 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D043BD8029 for ; Mon, 12 Sep 2016 16:44:16 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3F5A0857; Mon, 12 Sep 2016 16:44:16 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bjUL6-000Khb-UX; Mon, 12 Sep 2016 19:44:12 +0300 Date: Mon, 12 Sep 2016 19:44:12 +0300 From: Slawa Olhovchenkov To: Andriy Gapon Cc: Konstantin Belousov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160912164412.GS34394@zxy.spb.ru> References: <20160901112724.GX88122@zxy.spb.ru> <20160901114500.GJ83214@kib.kiev.ua> <20160901121300.GZ88122@zxy.spb.ru> <4ba05c00-f737-f562-553d-a7fa59145768@FreeBSD.org> <20160904151415.GE83214@kib.kiev.ua> <20160904162926.GF83214@kib.kiev.ua> <358ed414-9da6-ac29-55fc-6d7be680c2ce@FreeBSD.org> <20160912093905.GP34394@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2016 16:44:16 -0000 On Mon, Sep 12, 2016 at 04:44:09PM +0300, Andriy Gapon wrote: > On 12/09/2016 12:39, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 08:14:07PM +0300, Andriy Gapon wrote: > > > >> On 04/09/2016 19:29, Konstantin Belousov wrote: > >>> This is possible, of course. But it would not affect "SMP: Added CPU ..." > >>> lines. > >> > >> Well, looking at the code it seems that only if mptable is used, then those > >> lines are expected to correctly identify a BSP. With MADT there is no > >> information to identify the BSP and that is supposed to happen in cpu_mp_start(). > >> > >> > >> static void > >> madt_add_cpu(u_int acpi_id, u_int apic_id, u_int flags) > >> { > >> struct lapic_info *la; > >> > >> /* > >> * The MADT does not include a BSP flag, so we have to let the > >> * MP code figure out which CPU is the BSP on its own. > >> */ > >> ... > >> > >> In other words, those "SMP: Added CPU ..." are truly a cosmetic issue. > >> And it's my guess (just a guess) that BSP LAPIC ID is incorrect in the > >> problematic configuration. > > > > For next day or two I am have new server with same hardware before put > > in prodution. > > Can I do some test for you? > > > > >From my earlier email: > "my guess can be checked by adding a printf to cpu_mp_start() right after > boot_cpu_id assignment". I am not kernel developer: please point what I am need insert and file for edit. From owner-freebsd-stable@freebsd.org Mon Sep 12 17:06:32 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8B16BD883C for ; Mon, 12 Sep 2016 17:06:32 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B2B13E64 for ; Mon, 12 Sep 2016 17:06:32 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id AE8C0BD883B; Mon, 12 Sep 2016 17:06:32 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE2E1BD883A for ; Mon, 12 Sep 2016 17:06:32 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0FE06E63 for ; Mon, 12 Sep 2016 17:06:31 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA18173; Mon, 12 Sep 2016 20:06:29 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bjUgf-0003T4-FD; Mon, 12 Sep 2016 20:06:29 +0300 Subject: Re: X2APIC support To: Slawa Olhovchenkov References: <20160901112724.GX88122@zxy.spb.ru> <20160901114500.GJ83214@kib.kiev.ua> <20160901121300.GZ88122@zxy.spb.ru> <4ba05c00-f737-f562-553d-a7fa59145768@FreeBSD.org> <20160904151415.GE83214@kib.kiev.ua> <20160904162926.GF83214@kib.kiev.ua> <358ed414-9da6-ac29-55fc-6d7be680c2ce@FreeBSD.org> <20160912093905.GP34394@zxy.spb.ru> <20160912164412.GS34394@zxy.spb.ru> Cc: Konstantin Belousov , stable@FreeBSD.org From: Andriy Gapon Message-ID: <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> Date: Mon, 12 Sep 2016 20:05:33 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160912164412.GS34394@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2016 17:06:32 -0000 On 12/09/2016 19:44, Slawa Olhovchenkov wrote: > I am not kernel developer: please point what I am need insert and file > for edit. In sys/amd64/amd64/mp_machdep.c (assuming you use amd64), in function cpu_mp_start, in this place /* Set boot_cpu_id if needed. */ if (boot_cpu_id == -1) { boot_cpu_id = PCPU_GET(apic_id); cpu_info[boot_cpu_id].cpu_bsp = 1; } else right after boot_cpu_id = PCPU_GET(apic_id) line please insert printf("boot_cpu_id = %d\n", boot_cpu_id); -- Andriy Gapon From owner-freebsd-stable@freebsd.org Mon Sep 12 17:53:52 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BDBBBD8732 for ; Mon, 12 Sep 2016 17:53:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 36418786 for ; Mon, 12 Sep 2016 17:53:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 3203BBD8731; Mon, 12 Sep 2016 17:53:52 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31BB6BD8730 for ; Mon, 12 Sep 2016 17:53:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E8E3A785; Mon, 12 Sep 2016 17:53:51 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bjVQS-000MKq-CQ; Mon, 12 Sep 2016 20:53:48 +0300 Date: Mon, 12 Sep 2016 20:53:48 +0300 From: Slawa Olhovchenkov To: Andriy Gapon Cc: Konstantin Belousov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160912175348.GV34394@zxy.spb.ru> References: <20160901121300.GZ88122@zxy.spb.ru> <4ba05c00-f737-f562-553d-a7fa59145768@FreeBSD.org> <20160904151415.GE83214@kib.kiev.ua> <20160904162926.GF83214@kib.kiev.ua> <358ed414-9da6-ac29-55fc-6d7be680c2ce@FreeBSD.org> <20160912093905.GP34394@zxy.spb.ru> <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2016 17:53:52 -0000 On Mon, Sep 12, 2016 at 08:05:33PM +0300, Andriy Gapon wrote: > On 12/09/2016 19:44, Slawa Olhovchenkov wrote: > > I am not kernel developer: please point what I am need insert and file > > for edit. > > In sys/amd64/amd64/mp_machdep.c (assuming you use amd64), in function > cpu_mp_start, in this place > /* Set boot_cpu_id if needed. */ > if (boot_cpu_id == -1) { > boot_cpu_id = PCPU_GET(apic_id); > cpu_info[boot_cpu_id].cpu_bsp = 1; > } else > > right after boot_cpu_id = PCPU_GET(apic_id) line please insert > printf("boot_cpu_id = %d\n", boot_cpu_id); VT(vga): text 80x25 CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2200.05-MHz K8-class CPU) Origin="GenuineIntel" Id=0x406f1 Family=0x6 Model=0x4f Stepping=1 Features=0xbfebfbff Features2=0x7ffefbff AMD Features=0x2c100800 AMD Features2=0x121 Structured Extended Features=0x21cbfbb XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 137438953472 (131072 MB) avail memory = 133407973376 (127227 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: boot_cpu_id = 255 kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = ff fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80537e74 stack pointer = 0x28:0xffffffff814b3a60 frame pointer = 0x28:0xffffffff814b3a70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xffffffff805272e7 at kdb_backtrace+0x67 #1 0xffffffff804dd662 at vpanic+0x182 #2 0xffffffff804dd4d3 at panic+0x43 #3 0xffffffff807a37a1 at trap_fatal+0x351 #4 0xffffffff807a3993 at trap_pfault+0x1e3 #5 0xffffffff807a2f1c at trap+0x26c #6 0xffffffff80787ca1 at calltrap+0x8 #7 0xffffffff8083b53a at topo_probe+0x61a #8 0xffffffff8078fe93 at cpu_mp_start+0x1c3 #9 0xffffffff805382ca at mp_start+0x3a #10 0xffffffff80465cd8 at mi_startup+0x118 #11 0xffffffff8028dfac at btext+0x2c Uptime: 1s From owner-freebsd-stable@freebsd.org Mon Sep 12 20:26:59 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9B79BD8391 for ; Mon, 12 Sep 2016 20:26:59 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id BA04DEE2; Mon, 12 Sep 2016 20:26:59 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 230EA16FB; Mon, 12 Sep 2016 20:26:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Mon, 12 Sep 2016 20:26:57 +0000 From: Glen Barber To: Shawn Webb Cc: freebsd-stable@freebsd.org Subject: Re: How's 11.0-RELEASE coming? Message-ID: <20160912202657.GN56455@FreeBSD.org> References: <201609080059.SAA22410@mail.lariat.net> <20160908134434.I91459@sola.nimnet.asn.au> <201609090104.TAA05066@mail.lariat.net> <20160909012420.GC56455@FreeBSD.org> <20160909140850.GA34751@mutt-hardenedbsd> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mI5TpPl/qDRoXxBg" Content-Disposition: inline In-Reply-To: <20160909140850.GA34751@mutt-hardenedbsd> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2016 20:26:59 -0000 --mI5TpPl/qDRoXxBg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 09, 2016 at 10:08:50AM -0400, Shawn Webb wrote: > Hey Glen, >=20 > I'm just checking in to see if you saw this bug report I filed: >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212418 >=20 > It affects 11.0-RC2. >=20 Sorry for the delayed reply. No, I did not. Superficially, it looks like an EN candidate, I believe. Glen --mI5TpPl/qDRoXxBg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJX1w+MAAoJEAMUWKVHj+KTc/8P/39K88WFCFjhn1cHywzn3gTE ll78lK5jsyouQi4lckgmhvBecqY4gvLWp+sMA1OQcK4lThsrNnN4qinEvtU4h2hq q4UfGseRQ+xcspfzknSu9ErNuE89jXw5swHSmpXtNwd8H7Mwvgc9kxaeRe58FBxL t3oaRuSMDnElBRUkYVnv42PBdwX0+6Uo+WPtwNJcxAH/eET7bQYJ1VrdEih59tXc qvUoZdWZPeKB0BvKbDo9Bc+XO3jyCZ/Bk2posHqA2Pmuzp1q06SQ8+5UbnAfcicD FzEZ+JZ1/Ot2orwH549z+LBR3egz2dyv/ugXXhVyiwdyhRrnYf86Qu3KTSGTDgj+ KYkbQZaHbYVMzbYha8TaGDynNgcl+fLYwisRplQgZIlHFnXtC3K5U3eEDRmfJc9N SP7tm7F/FFfNaPqwiJy1NSC1icsmyT8pUazvcq7CALb+c2CWBfPa98HW01p11J8n B11GQJ8X+6oAPM54M/oJLW6zYgf24eu2wkJpClySxjs1UvvVgVv7F9g2T01ldfY+ UlnF8hspuemMsw3LZ7zQOLEEI0eHu5Oxoj9yRlpN1LPTwkoqw5aaT0VOPcrLzlLQ uyPuYLXQxyumnCS3N5ZkRTD0SoJSuOgIeuKqeoeYC4ztrN5daRgRTMRUbWN6AjkY CwcqrpmSwGeMMRpVgoSL =0aPn -----END PGP SIGNATURE----- --mI5TpPl/qDRoXxBg-- From owner-freebsd-stable@freebsd.org Tue Sep 13 06:27:41 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44D23BD7237 for ; Tue, 13 Sep 2016 06:27:41 +0000 (UTC) (envelope-from dciin@cloudwebx5.newtekwebhosting.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 26302D42 for ; Tue, 13 Sep 2016 06:27:41 +0000 (UTC) (envelope-from dciin@cloudwebx5.newtekwebhosting.com) Received: by mailman.ysv.freebsd.org (Postfix) id 21E67BD7234; Tue, 13 Sep 2016 06:27:41 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F4C8BD7233 for ; Tue, 13 Sep 2016 06:27:41 +0000 (UTC) (envelope-from dciin@cloudwebx5.newtekwebhosting.com) Received: from gwa1.webcontrolcenter.com (gwa1.webcontrolcenter.com [63.134.207.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 960F5D41 for ; Tue, 13 Sep 2016 06:27:39 +0000 (UTC) (envelope-from dciin@cloudwebx5.newtekwebhosting.com) Received: from GWAX.webcontrolcenter.com (gwax.crystaltech.com [63.134.207.78]) by gwa1.webcontrolcenter.com with SMTP (version=TLS\Tls12 cipher=Aes256 bits=256); Mon, 12 Sep 2016 23:12:23 -0700 Received: from cloudwebx5.newtekwebhosting.com (cloudwebx5.newtekwebhosting.com [75.103.66.7]) by GWAX.webcontrolcenter.com with SMTP (version=TLS\Tls12 cipher=Aes256 bits=256); Mon, 12 Sep 2016 23:12:14 -0700 Received: from dciin by cloudwebx5.newtekwebhosting.com with local (Exim 4.87) (envelope-from ) id 1bjgx4-000Uow-CY for stable@freebsd.org; Mon, 12 Sep 2016 23:12:14 -0700 To: stable@freebsd.org Subject: Problems with item delivery, n.00846960 X-PHP-Script: blog.mahindraworldcity.com/post.php for 95.128.94.230 Date: Tue, 13 Sep 2016 00:12:14 -0600 From: "FedEx International MailService" Reply-To: "FedEx International MailService" Message-ID: <9eddd5f46162063eddefb0cba3d65387@blog.mahindraworldcity.com> X-Priority: 3 MIME-Version: 1.0 Sender: X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cloudwebx5.newtekwebhosting.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [978 32007] / [47 12] X-AntiAbuse: Sender Address Domain - cloudwebx5.newtekwebhosting.com X-Get-Message-Sender-Via: cloudwebx5.newtekwebhosting.com: authenticated_id: dciin/from_h X-Authenticated-Sender: cloudwebx5.newtekwebhosting.com: perry.michael@blog.mahindraworldcity.com X-Source: X-Source-Args: /usr/sbin/proxyexec -q -d -s /var/lib/proxyexec/cagefs.sock/socket /bin/cagefs.server X-Source-Dir: dci.in:/public_html/blog.mahindraworldcity.com Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 06:27:41 -0000 Dear Customer, Your parcel has arrived at September 10. Courier was unable to deliver the parcel to you. You can review complete details of your order in the find attached. Sincerely, Perry Michael, Sr. Station Manager. From owner-freebsd-stable@freebsd.org Tue Sep 13 07:06:04 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BA93CBD7E99 for ; Tue, 13 Sep 2016 07:06:04 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu01176a.smtpx.saremail.com (cu01176a.smtpx.saremail.com [195.16.150.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7C310D2 for ; Tue, 13 Sep 2016 07:06:03 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.8.36] (izaro.sarenet.es [192.148.167.11]) by proxypop03.sare.net (Postfix) with ESMTPSA id EE77E9DDF74; Tue, 13 Sep 2016 08:58:56 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Intel NVMe troubles? From: Borja Marcos In-Reply-To: Date: Tue, 13 Sep 2016 08:58:56 +0200 Cc: FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: References: <4996AF96-76BA-47F1-B328-D4FE7AC777EE@sarenet.es> To: Jim Harris X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 07:06:04 -0000 > On 12 Sep 2016, at 17:23, Jim Harris wrote: >=20 > There is an updated DCT 3.0.2 at: https://downloadcenter.intel. > com/download/26221/Intel-SSD-Data-Center-Tool which has a fix for this > issue. >=20 > Borja has already downloaded this update and confirmed it looks good = so > far. Posting the update and results here so it is archived on the = STABLE > mailing list. Is it just my imagination or has trim performance improved dramatically? = I=E2=80=99m being unable to replicate the I/O stalls that I observed after running some simultaneous Bonnie++ = benchmarks with large files. Thanks, Borja. From owner-freebsd-stable@freebsd.org Tue Sep 13 07:06:44 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84C92BD7F26 for ; Tue, 13 Sep 2016 07:06:44 +0000 (UTC) (envelope-from Matthias_Wolf@eumx.net) Received: from owm.eumx.net (eumx.net [91.82.101.43]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4480B1F1 for ; Tue, 13 Sep 2016 07:06:43 +0000 (UTC) (envelope-from Matthias_Wolf@eumx.net) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=eumx.net; h=date:from:to :cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=default; bh=o/BBLhUab Vd6/FBCQZ7+XPjHQWc=; b=tBeXRAtNG78YTe56M1SJVPLG7/ZjHtC2peYaCuaP2 20CR3oEInzMJuyk7GgoWid0bp2IKoScbLlHoKO42sgC09i7u0YBX0suNqbpubWlg 0svyXcQjxzGyR4QkvEVlNZOc7lW8hCgCyP6n+qPYZelFo44tzmBf5zhz4JGAMo28 0w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=eumx.net; h=date:from:to:cc :subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=default; b=ZM3 LndZ3rxTpePm7KuY6f2bRrHAGx/7psfHvmp5cRMo7x83MQfIXgrgDGxP9Jrd6YSg rRi0XOnr/fGcrRxfUQ8ctwz6IUvuDdPDmZqbpFxh64vZbmzcG3vD8CXiBwKfR1gF V6/K9LuPv9YO1grML0lhlNcOO7BXzvvJ30kRceRE= Date: Tue, 13 Sep 2016 08:34:06 +0200 From: Matthias Wolf To: freebsd-stable@freebsd.org Cc: FedEx International MailService Subject: Re: Problems with item delivery, n.00846960 Message-ID: <20160913083406.3fdbd7ff@eumx.net> In-Reply-To: <9eddd5f46162063eddefb0cba3d65387@blog.mahindraworldcity.com> References: <9eddd5f46162063eddefb0cba3d65387@blog.mahindraworldcity.com> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 07:06:44 -0000 How about you go fuck youself spammer-scum. On Tue, 13 Sep 2016 00:12:14 -0600 "FedEx International MailService" wrote: > Dear Customer, > > Your parcel has arrived at September 10. Courier was unable to > deliver the parcel to you. You can review complete details of your > order in the find attached. > > Sincerely, > Perry Michael, > Sr. Station Manager. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Tue Sep 13 12:04:52 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5481BD731F for ; Tue, 13 Sep 2016 12:04:52 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BEEC2EBC for ; Tue, 13 Sep 2016 12:04:52 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id BE3C8BD731D; Tue, 13 Sep 2016 12:04:52 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDE58BD731C for ; Tue, 13 Sep 2016 12:04:52 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1A73EEBA for ; Tue, 13 Sep 2016 12:04:51 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA22008; Tue, 13 Sep 2016 15:04:49 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bjmSH-0004UT-AD; Tue, 13 Sep 2016 15:04:49 +0300 Subject: Re: X2APIC support To: Slawa Olhovchenkov References: <20160901121300.GZ88122@zxy.spb.ru> <4ba05c00-f737-f562-553d-a7fa59145768@FreeBSD.org> <20160904151415.GE83214@kib.kiev.ua> <20160904162926.GF83214@kib.kiev.ua> <358ed414-9da6-ac29-55fc-6d7be680c2ce@FreeBSD.org> <20160912093905.GP34394@zxy.spb.ru> <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> <20160912175348.GV34394@zxy.spb.ru> Cc: Konstantin Belousov , stable@FreeBSD.org From: Andriy Gapon Message-ID: Date: Tue, 13 Sep 2016 15:04:13 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160912175348.GV34394@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 12:04:52 -0000 On 12/09/2016 20:53, Slawa Olhovchenkov wrote: > boot_cpu_id = 255 I think that this points towards the BIOS not configuring the BSP LAPIC correctly when you select that combination of BIOS options. That's weird, but I fail to find any other explanation. If wonder what would happen if you disable X2APIC_OPT_OUT and set hw.x2apic_enable=0 in loader.conf or at the loader prompt. -- Andriy Gapon From owner-freebsd-stable@freebsd.org Tue Sep 13 12:11:41 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8C56BD75EF for ; Tue, 13 Sep 2016 12:11:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D3A41223 for ; Tue, 13 Sep 2016 12:11:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id CF507BD75ED; Tue, 13 Sep 2016 12:11:41 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CED78BD75EC for ; Tue, 13 Sep 2016 12:11:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 91903221; Tue, 13 Sep 2016 12:11:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bjmYn-000Mac-8V; Tue, 13 Sep 2016 15:11:33 +0300 Date: Tue, 13 Sep 2016 15:11:33 +0300 From: Slawa Olhovchenkov To: Andriy Gapon Cc: Konstantin Belousov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160913121133.GX34394@zxy.spb.ru> References: <20160904151415.GE83214@kib.kiev.ua> <20160904162926.GF83214@kib.kiev.ua> <358ed414-9da6-ac29-55fc-6d7be680c2ce@FreeBSD.org> <20160912093905.GP34394@zxy.spb.ru> <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> <20160912175348.GV34394@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 12:11:42 -0000 On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote: > On 12/09/2016 20:53, Slawa Olhovchenkov wrote: > > boot_cpu_id = 255 > > I think that this points towards the BIOS not configuring the BSP LAPIC > correctly when you select that combination of BIOS options. > That's weird, but I fail to find any other explanation. > > If wonder what would happen if you disable X2APIC_OPT_OUT and set > hw.x2apic_enable=0 in loader.conf or at the loader prompt. Boot OK w/o hw.x2apic_enable=0, only with disable X2APIC_OPT_OUT. From owner-freebsd-stable@freebsd.org Tue Sep 13 12:39:15 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4106BD9270 for ; Tue, 13 Sep 2016 12:39:15 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id CDD9F65F for ; Tue, 13 Sep 2016 12:39:15 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id CD36EBD926F; Tue, 13 Sep 2016 12:39:15 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCD88BD926E for ; Tue, 13 Sep 2016 12:39:15 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 246E265E for ; Tue, 13 Sep 2016 12:39:14 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA22099; Tue, 13 Sep 2016 15:39:13 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bjmzZ-0004Vv-6N; Tue, 13 Sep 2016 15:39:13 +0300 Subject: Re: X2APIC support To: Slawa Olhovchenkov References: <20160904151415.GE83214@kib.kiev.ua> <20160904162926.GF83214@kib.kiev.ua> <358ed414-9da6-ac29-55fc-6d7be680c2ce@FreeBSD.org> <20160912093905.GP34394@zxy.spb.ru> <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> <20160912175348.GV34394@zxy.spb.ru> <20160913121133.GX34394@zxy.spb.ru> Cc: Konstantin Belousov , stable@FreeBSD.org From: Andriy Gapon Message-ID: <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> Date: Tue, 13 Sep 2016 15:38:17 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160913121133.GX34394@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 12:39:16 -0000 On 13/09/2016 15:11, Slawa Olhovchenkov wrote: > On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote: > >> On 12/09/2016 20:53, Slawa Olhovchenkov wrote: >>> boot_cpu_id = 255 >> >> I think that this points towards the BIOS not configuring the BSP LAPIC >> correctly when you select that combination of BIOS options. >> That's weird, but I fail to find any other explanation. >> >> If wonder what would happen if you disable X2APIC_OPT_OUT and set >> hw.x2apic_enable=0 in loader.conf or at the loader prompt. > > Boot OK w/o hw.x2apic_enable=0, only with disable X2APIC_OPT_OUT. > This doesn't answer my question and doesn't add any new information, correct? -- Andriy Gapon From owner-freebsd-stable@freebsd.org Tue Sep 13 12:42:43 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D071DBD9455 for ; Tue, 13 Sep 2016 12:42:43 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BADA8A43 for ; Tue, 13 Sep 2016 12:42:43 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id BA35EBD9454; Tue, 13 Sep 2016 12:42:43 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9E9EBD9453 for ; Tue, 13 Sep 2016 12:42:43 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6DA24A42; Tue, 13 Sep 2016 12:42:42 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bjn2t-000NJv-Ms; Tue, 13 Sep 2016 15:42:39 +0300 Date: Tue, 13 Sep 2016 15:42:39 +0300 From: Slawa Olhovchenkov To: Andriy Gapon Cc: Konstantin Belousov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160913124239.GZ34394@zxy.spb.ru> References: <20160904162926.GF83214@kib.kiev.ua> <358ed414-9da6-ac29-55fc-6d7be680c2ce@FreeBSD.org> <20160912093905.GP34394@zxy.spb.ru> <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> <20160912175348.GV34394@zxy.spb.ru> <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 12:42:43 -0000 On Tue, Sep 13, 2016 at 03:38:17PM +0300, Andriy Gapon wrote: > On 13/09/2016 15:11, Slawa Olhovchenkov wrote: > > On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote: > > > >> On 12/09/2016 20:53, Slawa Olhovchenkov wrote: > >>> boot_cpu_id = 255 > >> > >> I think that this points towards the BIOS not configuring the BSP LAPIC > >> correctly when you select that combination of BIOS options. > >> That's weird, but I fail to find any other explanation. > >> > >> If wonder what would happen if you disable X2APIC_OPT_OUT and set > >> hw.x2apic_enable=0 in loader.conf or at the loader prompt. > > > > Boot OK w/o hw.x2apic_enable=0, only with disable X2APIC_OPT_OUT. > > > > This doesn't answer my question and doesn't add any new information, correct? I am don't see any question. I am see only suggestion of workaround. Sorry if missunderstund. You need some additional debug print? From owner-freebsd-stable@freebsd.org Tue Sep 13 12:58:38 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C68E6BD996A for ; Tue, 13 Sep 2016 12:58:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B0277299 for ; Tue, 13 Sep 2016 12:58:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id AC18CBD9969; Tue, 13 Sep 2016 12:58:38 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABC3DBD9968 for ; Tue, 13 Sep 2016 12:58:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 08C8B28C for ; Tue, 13 Sep 2016 12:58:36 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA22148; Tue, 13 Sep 2016 15:58:35 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bjnIJ-0004X1-H4; Tue, 13 Sep 2016 15:58:35 +0300 Subject: Re: X2APIC support To: Slawa Olhovchenkov References: <20160904162926.GF83214@kib.kiev.ua> <358ed414-9da6-ac29-55fc-6d7be680c2ce@FreeBSD.org> <20160912093905.GP34394@zxy.spb.ru> <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> <20160912175348.GV34394@zxy.spb.ru> <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> Cc: Konstantin Belousov , stable@FreeBSD.org From: Andriy Gapon Message-ID: Date: Tue, 13 Sep 2016 15:57:39 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160913124239.GZ34394@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 12:58:38 -0000 On 13/09/2016 15:42, Slawa Olhovchenkov wrote: > On Tue, Sep 13, 2016 at 03:38:17PM +0300, Andriy Gapon wrote: > >> On 13/09/2016 15:11, Slawa Olhovchenkov wrote: >>> On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote: >>> >>>> On 12/09/2016 20:53, Slawa Olhovchenkov wrote: >>>>> boot_cpu_id = 255 >>>> >>>> I think that this points towards the BIOS not configuring the BSP LAPIC >>>> correctly when you select that combination of BIOS options. >>>> That's weird, but I fail to find any other explanation. >>>> >>>> If wonder what would happen if you disable X2APIC_OPT_OUT and set >>>> hw.x2apic_enable=0 in loader.conf or at the loader prompt. >>> >>> Boot OK w/o hw.x2apic_enable=0, only with disable X2APIC_OPT_OUT. >>> >> >> This doesn't answer my question and doesn't add any new information, correct? > > I am don't see any question. I am see only suggestion of workaround. > Sorry if missunderstund. > You need some additional debug print? > I already knew from you that not enabling X2APIC_OPT_OUT fixed the problem. "If wonder what would happen if you disable X2APIC_OPT_OUT and set hw.x2apic_enable=0 in loader.conf or at the loader prompt." This was a question even though there is no question mark. -- Andriy Gapon From owner-freebsd-stable@freebsd.org Tue Sep 13 13:08:22 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12BE3BD9BCF; Tue, 13 Sep 2016 13:08:22 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 0599CB0C; Tue, 13 Sep 2016 13:08:22 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 0C24E1D65; Tue, 13 Sep 2016 13:08:20 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Tue, 13 Sep 2016 13:08:19 +0000 From: Glen Barber To: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Cc: FreeBSD Release Engineering Team Subject: 11.0-RELEASE status update Message-ID: <20160913130819.GQ56455@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="kERJ49nCKmnv470N" Content-Disposition: inline X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 13:08:22 -0000 --kERJ49nCKmnv470N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline There is one issue that was brought to our attention, which we are waiting for feedback before classifying as an EN candidate. Once we receive feedback, the 11.0-RELEASE schedule should be updated to reflect reality. At present, I am hopeful 11.0-RC3 builds should start 9/14/2016 at 00:00 UTC (about 11 hours from now). Thank you for your patience, and apologies for the delay. Glen On behalf of: re@ --kERJ49nCKmnv470N Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJX1/pDAAoJEAMUWKVHj+KT8F8P/j6qkRqUcdxoMsXl+cl2a28E okaPr2fanzd8Zf72HNWpo4J0r5hk1bWln9Qs4KaU6zZS7bv0DH1sBwQTDzcQnbDe 5+lKY3iYSZyugXn53bDGfMJ7XOBQt+xvYjIV0ZcjfsqNAk7KOYzBsUmG6HYgHDJt dZYXHRSzg2Q3nIEXx9G9/5l/z6d0M+vKbfJaSqZcNcRMwXMRsDXcweEHId7OOTk0 Q2N4RGvdVPBEYR0j7DMRGNzP94S/RNMZF557oMMgwcEMOEcu6m+B3hmqqU0IPl2U /aEv4A1arKgejLcAZSRB7pAw8jwoV61gODkA0/Z7b4bNVJIFiRazjpRuGDlyhrEn NkHdcjn6Hsb72/+fFPA/za9Jr7I8KFHG8W9nlWAkDrncVSqLtUK/eUttUokDiEff ppICLWR4m3jYUwV8QjANafbudW+Nenl3xrdgd8mqHtfHt2I3qdlVBhDjFMLxU5yV 2cRHAKucG4KXSLBCJZVZ4nVBqFoEzxeM2kGG4KYj2cHx5G9j6ZiZ08MXwgJQ2ltp Tuz1AFSSMQ6sJ+d3WLF/9bUrkEVtCqfZBh3FikaMVxynktCIupMm2IH2TwqF4b5e JEV4fX++RaDobWCVu0SZT3PshRzp3NMLV8sEIhtI8D//V7CzOwEWh9Fs4uqwCA4l kGX/QNRbCSYeXMPmF+lO =Dvy3 -----END PGP SIGNATURE----- --kERJ49nCKmnv470N-- From owner-freebsd-stable@freebsd.org Tue Sep 13 14:12:44 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B808BD9E00 for ; Tue, 13 Sep 2016 14:12:44 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 5F3F5E9E; Tue, 13 Sep 2016 14:12:44 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 6C488147; Tue, 13 Sep 2016 14:12:43 +0000 (UTC) Date: Tue, 13 Sep 2016 14:12:40 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org Message-ID: <605729374.14.1473775960094.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build became unstable: FreeBSD_stable_10 #397 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkKKb2VAfYQKfu1t7qk4nR5qzUBEI+UqT4BPec4qHVhqUy0FFdq50sMH+3y9bCDNOufctov6VqTNffZ3YXArnZK95YF0OX97fh+E9txYOUX1adc+TikcKjuYpHmL5dE62eaZTI+4A5jnRonskQ1PaoIFz0Kbu4mWzkFsmdiXTraGzomXq4cHUCATA2+K4eDYgjXEQI30z3GOMmmZ4t/+6QGk1cMb/BqMWHbn80AsRCb4tU7Hpd72XLDpsuO7YRP1Q0CjmNAuBOTj+sFiiOe6U9HpqOlQN+iFUvBdZo/ybuy5Kh71cAaYQNL68cYdZJ6binH/DkG3KY/fS7DFYAeuwjwIDAQAB X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: UNSTABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 14:12:44 -0000 See From owner-freebsd-stable@freebsd.org Tue Sep 13 14:21:22 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F2D2BD9115 for ; Tue, 13 Sep 2016 14:21:22 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 59C8A77A for ; Tue, 13 Sep 2016 14:21:22 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 59270BD9114; Tue, 13 Sep 2016 14:21:22 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58CE8BD9113 for ; Tue, 13 Sep 2016 14:21:22 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1653E776; Tue, 13 Sep 2016 14:21:22 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bjoaM-000Pg8-NW; Tue, 13 Sep 2016 17:21:18 +0300 Date: Tue, 13 Sep 2016 17:21:18 +0300 From: Slawa Olhovchenkov To: Andriy Gapon Cc: Konstantin Belousov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160913142118.GA34394@zxy.spb.ru> References: <20160912093905.GP34394@zxy.spb.ru> <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> <20160912175348.GV34394@zxy.spb.ru> <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 14:21:22 -0000 On Tue, Sep 13, 2016 at 03:57:39PM +0300, Andriy Gapon wrote: > On 13/09/2016 15:42, Slawa Olhovchenkov wrote: > > On Tue, Sep 13, 2016 at 03:38:17PM +0300, Andriy Gapon wrote: > > > >> On 13/09/2016 15:11, Slawa Olhovchenkov wrote: > >>> On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote: > >>> > >>>> On 12/09/2016 20:53, Slawa Olhovchenkov wrote: > >>>>> boot_cpu_id = 255 > >>>> > >>>> I think that this points towards the BIOS not configuring the BSP LAPIC > >>>> correctly when you select that combination of BIOS options. > >>>> That's weird, but I fail to find any other explanation. > >>>> > >>>> If wonder what would happen if you disable X2APIC_OPT_OUT and set > >>>> hw.x2apic_enable=0 in loader.conf or at the loader prompt. > >>> > >>> Boot OK w/o hw.x2apic_enable=0, only with disable X2APIC_OPT_OUT. > >>> > >> > >> This doesn't answer my question and doesn't add any new information, correct? > > > > I am don't see any question. I am see only suggestion of workaround. > > Sorry if missunderstund. > > You need some additional debug print? > > > > I already knew from you that not enabling X2APIC_OPT_OUT fixed the problem. > "If wonder what would happen if you disable X2APIC_OPT_OUT and set > hw.x2apic_enable=0 in loader.conf or at the loader prompt." > This was a question even though there is no question mark. boot failed: set hw.x2apic_enable=0 loading required module 'krpc' /boot/kernel.VSTREAM/krpc.ko size 0x2a210 at 0x134e000 loading required module 'opensolaris' ^@/boot/kernel.VSTREAM/opensolaris.ko size 0xadb8 at 0x1379000 /boot/kernel.VSTREAM/if_igb.ko size 0x69f10 at 0x1384000 can't find 'if_ixgbe' /boot/kernel.VSTREAM/if_lagg.ko size 0x150c0 at 0x13ee000^M ^@ +/boot/kernel.VSTREAM/ukbd.ko size 0xe128 at 0x1404000 loading required module 'usb' /boot/kernel.VSTREAM/usb.ko size 0x458b0 at 0x1413000^M| /boot/kernel.VSTREAM/umass.ko size 0xaa10 at 0x1459000 /boot/kernel.VSTREAM/accf_http.ko size 0x2710 at 0x1464000 /boot/kernel.VSTREAM/uhci.ko size 0xd508 at 0x1467000 /boot/kernel.VSTREAM/ohci.ko size 0xc9d0 at 0x1475000^M /boot/kernel.VSTREAM/ehci.ko size 0xfc40 at 0x1482000 /boot/kernel.VSTREAM/xhci.ko size 0x11068 at 0x1492000 /boot/kernel.VSTREAM/cc_htcp.ko size 0x3a70 at 0x14a4000 Booting... Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-RELEASE-p305117 #0: Mon Sep 12 20:38:53 MSK 2016 slw@edge21.int.integros.com:/usr/obj/usr/src/sys/VSTREAM amd64 FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) VT(vga): text 80x25 CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2200.04-MHz K8-class CPU) Origin="GenuineIntel" Id=0x406f1 Family=0x6 Model=0x4f Stepping=1 Features=0xbfebfbff Features2=0x7ffefbff AMD Features=0x2c100800 AMD Features2=0x121 Structured Extended Features=0x21cbfbb XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 137438953472 (131072 MB) avail memory = 133407973376 (127227 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: boot_cpu_id = 255 kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = ff fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80537e74 stack pointer = 0x28:0xffffffff814b3a60 frame pointer = 0x28:0xffffffff814b3a70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xffffffff805272e7 at kdb_backtrace+0x67 #1 0xffffffff804dd662 at vpanic+0x182 #2 0xffffffff804dd4d3 at panic+0x43 #3 0xffffffff807a37a1 at trap_fatal+0x351 #4 0xffffffff807a3993 at trap_pfault+0x1e3 #5 0xffffffff807a2f1c at trap+0x26c #6 0xffffffff80787ca1 at calltrap+0x8 #7 0xffffffff8083b53a at topo_probe+0x61a #8 0xffffffff8078fe93 at cpu_mp_start+0x1c3 #9 0xffffffff805382ca at mp_start+0x3a #10 0xffffffff80465cd8 at mi_startup+0x118 #11 0xffffffff8028dfac at btext+0x2c Uptime: 1s From owner-freebsd-stable@freebsd.org Tue Sep 13 14:55:10 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D10EBD9A0C for ; Tue, 13 Sep 2016 14:55:10 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 76A98B3A for ; Tue, 13 Sep 2016 14:55:10 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7288BBD9A0B; Tue, 13 Sep 2016 14:55:10 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7224BBD9A0A for ; Tue, 13 Sep 2016 14:55:10 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D6283B39 for ; Tue, 13 Sep 2016 14:55:09 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA22376; Tue, 13 Sep 2016 17:55:02 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bjp70-0004cM-1b; Tue, 13 Sep 2016 17:55:02 +0300 Subject: Re: X2APIC support To: Slawa Olhovchenkov References: <20160912093905.GP34394@zxy.spb.ru> <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> <20160912175348.GV34394@zxy.spb.ru> <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> Cc: Konstantin Belousov , stable@FreeBSD.org From: Andriy Gapon Message-ID: <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> Date: Tue, 13 Sep 2016 17:54:26 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160913142118.GA34394@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 14:55:10 -0000 On 13/09/2016 17:21, Slawa Olhovchenkov wrote: > boot failed: > > set hw.x2apic_enable=0 > loading required module 'krpc' > /boot/kernel.VSTREAM/krpc.ko size 0x2a210 at 0x134e000 > loading required module 'opensolaris' > ^@/boot/kernel.VSTREAM/opensolaris.ko size 0xadb8 at 0x1379000 > /boot/kernel.VSTREAM/if_igb.ko size 0x69f10 at 0x1384000 > can't find 'if_ixgbe' > /boot/kernel.VSTREAM/if_lagg.ko size 0x150c0 at 0x13ee000^M ^@ > +/boot/kernel.VSTREAM/ukbd.ko size 0xe128 at 0x1404000 > loading required module 'usb' > /boot/kernel.VSTREAM/usb.ko size 0x458b0 at 0x1413000^M| > /boot/kernel.VSTREAM/umass.ko size 0xaa10 at 0x1459000 > /boot/kernel.VSTREAM/accf_http.ko size 0x2710 at 0x1464000 > /boot/kernel.VSTREAM/uhci.ko size 0xd508 at 0x1467000 > /boot/kernel.VSTREAM/ohci.ko size 0xc9d0 at 0x1475000^M > /boot/kernel.VSTREAM/ehci.ko size 0xfc40 at 0x1482000 > /boot/kernel.VSTREAM/xhci.ko size 0x11068 at 0x1492000 > /boot/kernel.VSTREAM/cc_htcp.ko size 0x3a70 at 0x14a4000 > Booting... > Copyright (c) 1992-2016 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.0-RELEASE-p305117 #0: Mon Sep 12 20:38:53 MSK 2016 > slw@edge21.int.integros.com:/usr/obj/usr/src/sys/VSTREAM amd64 > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) > VT(vga): text 80x25 > CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2200.04-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x406f1 Family=0x6 Model=0x4f Stepping=1 > Features=0xbfebfbff > Features2=0x7ffefbff > AMD Features=0x2c100800 > AMD Features2=0x121 > Structured Extended Features=0x21cbfbb > XSAVE Features=0x1 > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr > TSC: P-state invariant, performance statistics > real memory = 137438953472 (131072 MB) > avail memory = 133407973376 (127227 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: > boot_cpu_id = 255 > kernel trap 12 with interrupts disabled > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = ff > fault virtual address = 0x0 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80537e74 > stack pointer = 0x28:0xffffffff814b3a60 > frame pointer = 0x28:0xffffffff814b3a70 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = resume, IOPL = 0 > current process = 0 () > trap number = 12 > panic: page fault > cpuid = 0 > KDB: stack backtrace: > #0 0xffffffff805272e7 at kdb_backtrace+0x67 > #1 0xffffffff804dd662 at vpanic+0x182 > #2 0xffffffff804dd4d3 at panic+0x43 > #3 0xffffffff807a37a1 at trap_fatal+0x351 > #4 0xffffffff807a3993 at trap_pfault+0x1e3 > #5 0xffffffff807a2f1c at trap+0x26c > #6 0xffffffff80787ca1 at calltrap+0x8 > #7 0xffffffff8083b53a at topo_probe+0x61a > #8 0xffffffff8078fe93 at cpu_mp_start+0x1c3 > #9 0xffffffff805382ca at mp_start+0x3a > #10 0xffffffff80465cd8 at mi_startup+0x118 > #11 0xffffffff8028dfac at btext+0x2c > Uptime: 1s Thank you! It seems like exactly the same behavior that happens when you toggle that BIOS option. My theory is that in both cases, hw.x2apic_enable=0 and X2APIC_OPT_OUT is on, the BIOS turns on x2APIC mode and transitions to OS in that mode. In the case when X2APIC_OPT_OUT is on it's clearly a BIOS bug. But maybe we could do a little bit better in both cases. At the very least we could detect the situation and panic with a helpful message (e.g. "x2APIC mode is disabled but turn on by BIOS"). Perhaps we could even try to downgrade to xAPIC mode. -- Andriy Gapon From owner-freebsd-stable@freebsd.org Tue Sep 13 14:59:59 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60991BD9B74 for ; Tue, 13 Sep 2016 14:59:59 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4B5A0E79 for ; Tue, 13 Sep 2016 14:59:59 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 472D1BD9B73; Tue, 13 Sep 2016 14:59:59 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46D47BD9B72 for ; Tue, 13 Sep 2016 14:59:59 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 08A4DE76; Tue, 13 Sep 2016 14:59:59 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bjpBl-0000g5-3A; Tue, 13 Sep 2016 17:59:57 +0300 Date: Tue, 13 Sep 2016 17:59:57 +0300 From: Slawa Olhovchenkov To: Andriy Gapon Cc: Konstantin Belousov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160913145957.GC34394@zxy.spb.ru> References: <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> <20160912175348.GV34394@zxy.spb.ru> <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 14:59:59 -0000 On Tue, Sep 13, 2016 at 05:54:26PM +0300, Andriy Gapon wrote: > On 13/09/2016 17:21, Slawa Olhovchenkov wrote: > > boot failed: > > > > set hw.x2apic_enable=0 > > loading required module 'krpc' > > /boot/kernel.VSTREAM/krpc.ko size 0x2a210 at 0x134e000 > > loading required module 'opensolaris' > > ^@/boot/kernel.VSTREAM/opensolaris.ko size 0xadb8 at 0x1379000 > > /boot/kernel.VSTREAM/if_igb.ko size 0x69f10 at 0x1384000 > > can't find 'if_ixgbe' > > /boot/kernel.VSTREAM/if_lagg.ko size 0x150c0 at 0x13ee000^M ^@ > > +/boot/kernel.VSTREAM/ukbd.ko size 0xe128 at 0x1404000 > > loading required module 'usb' > > /boot/kernel.VSTREAM/usb.ko size 0x458b0 at 0x1413000^M| > > /boot/kernel.VSTREAM/umass.ko size 0xaa10 at 0x1459000 > > /boot/kernel.VSTREAM/accf_http.ko size 0x2710 at 0x1464000 > > /boot/kernel.VSTREAM/uhci.ko size 0xd508 at 0x1467000 > > /boot/kernel.VSTREAM/ohci.ko size 0xc9d0 at 0x1475000^M > > /boot/kernel.VSTREAM/ehci.ko size 0xfc40 at 0x1482000 > > /boot/kernel.VSTREAM/xhci.ko size 0x11068 at 0x1492000 > > /boot/kernel.VSTREAM/cc_htcp.ko size 0x3a70 at 0x14a4000 > > Booting... > > Copyright (c) 1992-2016 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights reserved. > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > FreeBSD 11.0-RELEASE-p305117 #0: Mon Sep 12 20:38:53 MSK 2016 > > slw@edge21.int.integros.com:/usr/obj/usr/src/sys/VSTREAM amd64 > > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) > > VT(vga): text 80x25 > > CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2200.04-MHz K8-class CPU) > > Origin="GenuineIntel" Id=0x406f1 Family=0x6 Model=0x4f Stepping=1 > > Features=0xbfebfbff > > Features2=0x7ffefbff > > AMD Features=0x2c100800 > > AMD Features2=0x121 > > Structured Extended Features=0x21cbfbb > > XSAVE Features=0x1 > > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr > > TSC: P-state invariant, performance statistics > > real memory = 137438953472 (131072 MB) > > avail memory = 133407973376 (127227 MB) > > Event timer "LAPIC" quality 600 > > ACPI APIC Table: > > boot_cpu_id = 255 > > kernel trap 12 with interrupts disabled > > > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = ff > > fault virtual address = 0x0 > > fault code = supervisor read data, page not present > > instruction pointer = 0x20:0xffffffff80537e74 > > stack pointer = 0x28:0xffffffff814b3a60 > > frame pointer = 0x28:0xffffffff814b3a70 > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, long 1, def32 0, gran 1 > > processor eflags = resume, IOPL = 0 > > current process = 0 () > > trap number = 12 > > panic: page fault > > cpuid = 0 > > KDB: stack backtrace: > > #0 0xffffffff805272e7 at kdb_backtrace+0x67 > > #1 0xffffffff804dd662 at vpanic+0x182 > > #2 0xffffffff804dd4d3 at panic+0x43 > > #3 0xffffffff807a37a1 at trap_fatal+0x351 > > #4 0xffffffff807a3993 at trap_pfault+0x1e3 > > #5 0xffffffff807a2f1c at trap+0x26c > > #6 0xffffffff80787ca1 at calltrap+0x8 > > #7 0xffffffff8083b53a at topo_probe+0x61a > > #8 0xffffffff8078fe93 at cpu_mp_start+0x1c3 > > #9 0xffffffff805382ca at mp_start+0x3a > > #10 0xffffffff80465cd8 at mi_startup+0x118 > > #11 0xffffffff8028dfac at btext+0x2c > > Uptime: 1s > > Thank you! > It seems like exactly the same behavior that happens when you toggle that BIOS > option. > > My theory is that in both cases, hw.x2apic_enable=0 and X2APIC_OPT_OUT is on, > the BIOS turns on x2APIC mode and transitions to OS in that mode. > In the case when X2APIC_OPT_OUT is on it's clearly a BIOS bug. > But maybe we could do a little bit better in both cases. At the very least we > could detect the situation and panic with a helpful message (e.g. "x2APIC mode > is disabled but turn on by BIOS"). Perhaps we could even try to downgrade to > xAPIC mode. Goggling on X2APIC_OPT_OUT take same result: other OS in this case downgrade to xAPIC mode. From owner-freebsd-stable@freebsd.org Tue Sep 13 15:22:50 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B045EBD9387 for ; Tue, 13 Sep 2016 15:22:50 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9581DC4 for ; Tue, 13 Sep 2016 15:22:50 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 94DE2BD9384; Tue, 13 Sep 2016 15:22:50 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 948C2BD9383 for ; Tue, 13 Sep 2016 15:22:50 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 38AD6C2; Tue, 13 Sep 2016 15:22:50 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u8DFMeCl014051 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 13 Sep 2016 18:22:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u8DFMeCl014051 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u8DFMeLc014050; Tue, 13 Sep 2016 18:22:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 13 Sep 2016 18:22:40 +0300 From: Konstantin Belousov To: Andriy Gapon Cc: Slawa Olhovchenkov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160913152240.GE38409@kib.kiev.ua> References: <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> <20160912175348.GV34394@zxy.spb.ru> <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 15:22:50 -0000 On Tue, Sep 13, 2016 at 05:54:26PM +0300, Andriy Gapon wrote: > On 13/09/2016 17:21, Slawa Olhovchenkov wrote: > > boot failed: > > > > set hw.x2apic_enable=0 > > loading required module 'krpc' > > /boot/kernel.VSTREAM/krpc.ko size 0x2a210 at 0x134e000 > > loading required module 'opensolaris' > > ^@/boot/kernel.VSTREAM/opensolaris.ko size 0xadb8 at 0x1379000 > > /boot/kernel.VSTREAM/if_igb.ko size 0x69f10 at 0x1384000 > > can't find 'if_ixgbe' > > /boot/kernel.VSTREAM/if_lagg.ko size 0x150c0 at 0x13ee000^M ^@ > > +/boot/kernel.VSTREAM/ukbd.ko size 0xe128 at 0x1404000 > > loading required module 'usb' > > /boot/kernel.VSTREAM/usb.ko size 0x458b0 at 0x1413000^M| > > /boot/kernel.VSTREAM/umass.ko size 0xaa10 at 0x1459000 > > /boot/kernel.VSTREAM/accf_http.ko size 0x2710 at 0x1464000 > > /boot/kernel.VSTREAM/uhci.ko size 0xd508 at 0x1467000 > > /boot/kernel.VSTREAM/ohci.ko size 0xc9d0 at 0x1475000^M > > /boot/kernel.VSTREAM/ehci.ko size 0xfc40 at 0x1482000 > > /boot/kernel.VSTREAM/xhci.ko size 0x11068 at 0x1492000 > > /boot/kernel.VSTREAM/cc_htcp.ko size 0x3a70 at 0x14a4000 > > Booting... > > Copyright (c) 1992-2016 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights reserved. > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > FreeBSD 11.0-RELEASE-p305117 #0: Mon Sep 12 20:38:53 MSK 2016 > > slw@edge21.int.integros.com:/usr/obj/usr/src/sys/VSTREAM amd64 > > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) > > VT(vga): text 80x25 > > CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2200.04-MHz K8-class CPU) > > Origin="GenuineIntel" Id=0x406f1 Family=0x6 Model=0x4f Stepping=1 > > Features=0xbfebfbff > > Features2=0x7ffefbff > > AMD Features=0x2c100800 > > AMD Features2=0x121 > > Structured Extended Features=0x21cbfbb > > XSAVE Features=0x1 > > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr > > TSC: P-state invariant, performance statistics > > real memory = 137438953472 (131072 MB) > > avail memory = 133407973376 (127227 MB) > > Event timer "LAPIC" quality 600 > > ACPI APIC Table: > > boot_cpu_id = 255 > > kernel trap 12 with interrupts disabled > > > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = ff > > fault virtual address = 0x0 > > fault code = supervisor read data, page not present > > instruction pointer = 0x20:0xffffffff80537e74 > > stack pointer = 0x28:0xffffffff814b3a60 > > frame pointer = 0x28:0xffffffff814b3a70 > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, long 1, def32 0, gran 1 > > processor eflags = resume, IOPL = 0 > > current process = 0 () > > trap number = 12 > > panic: page fault > > cpuid = 0 > > KDB: stack backtrace: > > #0 0xffffffff805272e7 at kdb_backtrace+0x67 > > #1 0xffffffff804dd662 at vpanic+0x182 > > #2 0xffffffff804dd4d3 at panic+0x43 > > #3 0xffffffff807a37a1 at trap_fatal+0x351 > > #4 0xffffffff807a3993 at trap_pfault+0x1e3 > > #5 0xffffffff807a2f1c at trap+0x26c > > #6 0xffffffff80787ca1 at calltrap+0x8 > > #7 0xffffffff8083b53a at topo_probe+0x61a > > #8 0xffffffff8078fe93 at cpu_mp_start+0x1c3 > > #9 0xffffffff805382ca at mp_start+0x3a > > #10 0xffffffff80465cd8 at mi_startup+0x118 > > #11 0xffffffff8028dfac at btext+0x2c > > Uptime: 1s > > Thank you! > It seems like exactly the same behavior that happens when you toggle that BIOS > option. > > My theory is that in both cases, hw.x2apic_enable=0 and X2APIC_OPT_OUT is on, > the BIOS turns on x2APIC mode and transitions to OS in that mode. > In the case when X2APIC_OPT_OUT is on it's clearly a BIOS bug. > But maybe we could do a little bit better in both cases. At the very least we > could detect the situation and panic with a helpful message (e.g. "x2APIC mode > is disabled but turn on by BIOS"). Perhaps we could even try to downgrade to > xAPIC mode. If hw.x2apic_enable=0 and machine booted to the stage of topo probe, BIOS definitely did not made hand-off with x2APIC enabled. Any access to the LAPIC registers page in x2APIC mode faults. And X2APIC_OPT_OUT also does not result in x2APIC mode hand-off, for the same reason. System would panic much earlier, while dmesg indicates that LAPIC ICR calibration was succesful. It is invalid LAPIC Id or a bug in topo code or combination of issues. From owner-freebsd-stable@freebsd.org Tue Sep 13 15:53:18 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77D5ABD9FA1 for ; Tue, 13 Sep 2016 15:53:18 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6191F6B6 for ; Tue, 13 Sep 2016 15:53:18 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 60F9FBD9FA0; Tue, 13 Sep 2016 15:53:18 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 609ACBD9F9F for ; Tue, 13 Sep 2016 15:53:18 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B5F3A6B5 for ; Tue, 13 Sep 2016 15:53:17 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA22486; Tue, 13 Sep 2016 18:53:14 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bjq1K-0004fW-P8; Tue, 13 Sep 2016 18:53:14 +0300 Subject: Re: X2APIC support To: Konstantin Belousov References: <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> <20160912175348.GV34394@zxy.spb.ru> <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913152240.GE38409@kib.kiev.ua> Cc: Slawa Olhovchenkov , stable@FreeBSD.org From: Andriy Gapon Message-ID: Date: Tue, 13 Sep 2016 18:52:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160913152240.GE38409@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 15:53:18 -0000 On 13/09/2016 18:22, Konstantin Belousov wrote: > Any access > to the LAPIC registers page in x2APIC mode faults. Is this a fact? I read the following in the specification: In x2APIC mode, the memory mapped interface is not available and any access to the MMIO interface will behave similar to that of a legacy xAPIC in globally disabled state. But I couldn't find what actually happens for the legacy xAPIC in globally disabled state. For AMD processors it is documented that if xAPIC is disabled then accessing the APIC memory range works the same as accessing the regular memory. That can be different for Intel processors, of course. -- Andriy Gapon From owner-freebsd-stable@freebsd.org Tue Sep 13 19:26:02 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5611BD8C95 for ; Tue, 13 Sep 2016 19:26:02 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A039ED62 for ; Tue, 13 Sep 2016 19:26:02 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: by mail-yw0-x22a.google.com with SMTP id g192so112562866ywh.1 for ; Tue, 13 Sep 2016 12:26:02 -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; bh=Sf5amHKoMLFigyLaf3vrIBDudSYYnbCoN+t0luMGSD4=; b=yGMvlvpqtVV7XX3xJ1vYapiNeNugEnqKmJx9E2vNUt1Kr+6bLDowaAlmKjAcJTzkUv FJIuZ+zhaSx+1wvWLWJg9ZY7UCjyozYu0pAd2la3EkDVRlf/hGjUhI+6r7yWPrdHoMPj uR6VjCq/FfoqKOPMJht3qLPHQe+CMzucAti6r3EGC/4F9Mbhbhd55nIILqzyCJ/J/+5X ssapBVk6B4M5WwLJmoCBVnXMcbCWU30sF9D74j5lSjf8MHLY0GoANXxzyjuloYuiGcYV mxORO89z5DGlikqCL+DBadi94dRQyHxObVI4J3YGG9fO46yysBOYuh+NV7GxmfoXx2Ce eKyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Sf5amHKoMLFigyLaf3vrIBDudSYYnbCoN+t0luMGSD4=; b=Qj8vln5gZJo7yDeKLZc3oVi4vOOTt1GlBAVnWjXDq1U7lyfc6E5x+foPG36+C/Dprr GFyE9fqD29iDWS1AxH4WH5G+0l+RuG/jOstoIZ3ppaaJZNeTe7YoDqd03LW9Eir1CWRe w83hr87y6+YmA6kaIBTFAmssomZDL3IJ3l/k8gPZa9bwN/xn+T/ov9UXWtq+n2iapdGT IC+vAZlntBkEgIQ6ayWOFTlAfrJLQEqAudz3EeDEfIpg08gkuUHOYKATuiQnuccaTzQ8 KhTiOy6MnHDL2JTxucOkhRRDXAFTNB0hwDIDRECZjC0NKrJXc0GMe9gZTmmCdXiRzcoL FJwA== X-Gm-Message-State: AE9vXwP8iQmQiLJzCwB7nCNcHrN6rnNEcjaAbGWIqiQ0RPaOTLk0LGgP5QJ17jLXizp4/+bz/VvmLXmdIqiGRA== X-Received: by 10.13.228.135 with SMTP id n129mr2517277ywe.196.1473794761955; Tue, 13 Sep 2016 12:26:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.83.106 with HTTP; Tue, 13 Sep 2016 12:26:01 -0700 (PDT) In-Reply-To: References: <4996AF96-76BA-47F1-B328-D4FE7AC777EE@sarenet.es> From: Jim Harris Date: Tue, 13 Sep 2016 12:26:01 -0700 Message-ID: Subject: Re: Intel NVMe troubles? To: Borja Marcos Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2016 19:26:03 -0000 On Monday, September 12, 2016, Borja Marcos wrote: > > > On 12 Sep 2016, at 17:23, Jim Harris > wrote: > > > > There is an updated DCT 3.0.2 at: https://downloadcenter.intel. > > com/download/26221/Intel-SSD-Data-Center-Tool which has a fix for this > > issue. > > > > Borja has already downloaded this update and confirmed it looks good so > > far. Posting the update and results here so it is archived on the STAB= LE > > mailing list. > > Is it just my imagination or has trim performance improved dramatically? > I=E2=80=99m being unable to replicate > the I/O stalls that I observed after running some simultaneous Bonnie++ > benchmarks with large files. Yes - Trim performance should be significantly faster with the FW included in the 3.0.2 DCT release. Jim > > Thanks, > > > > Borja. > > > From owner-freebsd-stable@freebsd.org Wed Sep 14 11:36:41 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADCB3AC4B06 for ; Wed, 14 Sep 2016 11:36:41 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 939B51A67 for ; Wed, 14 Sep 2016 11:36:41 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 8F439AC4B04; Wed, 14 Sep 2016 11:36:41 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8EE76AC4B02 for ; Wed, 14 Sep 2016 11:36:41 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0712E1A65; Wed, 14 Sep 2016 11:36:40 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u8EBaZRZ067574 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 14 Sep 2016 14:36:35 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u8EBaZRZ067574 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u8EBaYuN067573; Wed, 14 Sep 2016 14:36:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 14 Sep 2016 14:36:34 +0300 From: Konstantin Belousov To: Andriy Gapon Cc: Slawa Olhovchenkov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160914113634.GF38409@kib.kiev.ua> References: <20160912175348.GV34394@zxy.spb.ru> <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913152240.GE38409@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 11:36:41 -0000 On Tue, Sep 13, 2016 at 06:52:19PM +0300, Andriy Gapon wrote: > On 13/09/2016 18:22, Konstantin Belousov wrote: > > Any access > > to the LAPIC registers page in x2APIC mode faults. > > Is this a fact? > I read the following in the specification: > > In x2APIC mode, the memory mapped interface is not available and any > access to the MMIO interface will behave similar to that of a legacy xAPIC > in globally disabled state. > > But I couldn't find what actually happens for the legacy xAPIC in globally > disabled state. For AMD processors it is documented that if xAPIC is disabled > then accessing the APIC memory range works the same as accessing the regular > memory. That can be different for Intel processors, of course. Look at the native_lapic_init(), very beginning of the function. If x2apic_mode is non-zero, lapic_map is cleared after DMAP page cache attributes are changed. Right now, if BIOS pass control to OS in x2APIC mode, thinks just work because no LAPIC accesses are done until native_lapic_enable_x2apic() is called. This just happens, I thought about more organized receipt of the current LAPIC mode. Issue is that decision for LAPIC mode is performed by madt enumerator which pref. should not read LAPIC config (too early). And it is not clear at all, what to do if there is reason to use xAPIC, as checked by madt_setup_local(), but we are in x2APIC mode already. Anyway, returning to the original issue, I do not believe that the hand-off on that machine occured in the x2APIC mode when X2APIC_OPT_OUT is specified. Kernel would fault in that case. From owner-freebsd-stable@freebsd.org Wed Sep 14 12:19:32 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DCF83BDAFC6 for ; Wed, 14 Sep 2016 12:19:32 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id C7DF91170 for ; Wed, 14 Sep 2016 12:19:32 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id C4146BDAFC5; Wed, 14 Sep 2016 12:19:32 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1A27BDAFC4 for ; Wed, 14 Sep 2016 12:19:32 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76A3A116E; Wed, 14 Sep 2016 12:19:32 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bk99w-00002I-8y; Wed, 14 Sep 2016 15:19:24 +0300 Date: Wed, 14 Sep 2016 15:19:24 +0300 From: Slawa Olhovchenkov To: Konstantin Belousov Cc: Andriy Gapon , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160914121924.GA2840@zxy.spb.ru> References: <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913152240.GE38409@kib.kiev.ua> <20160914113634.GF38409@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160914113634.GF38409@kib.kiev.ua> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 12:19:33 -0000 On Wed, Sep 14, 2016 at 02:36:34PM +0300, Konstantin Belousov wrote: > On Tue, Sep 13, 2016 at 06:52:19PM +0300, Andriy Gapon wrote: > > On 13/09/2016 18:22, Konstantin Belousov wrote: > > > Any access > > > to the LAPIC registers page in x2APIC mode faults. > > > > Is this a fact? > > I read the following in the specification: > > > > In x2APIC mode, the memory mapped interface is not available and any > > access to the MMIO interface will behave similar to that of a legacy xAPIC > > in globally disabled state. > > > > But I couldn't find what actually happens for the legacy xAPIC in globally > > disabled state. For AMD processors it is documented that if xAPIC is disabled > > then accessing the APIC memory range works the same as accessing the regular > > memory. That can be different for Intel processors, of course. > > Look at the native_lapic_init(), very beginning of the function. If > x2apic_mode is non-zero, lapic_map is cleared after DMAP page cache > attributes are changed. > > Right now, if BIOS pass control to OS in x2APIC mode, thinks just work > because no LAPIC accesses are done until native_lapic_enable_x2apic() is > called. This just happens, I thought about more organized receipt of the > current LAPIC mode. Issue is that decision for LAPIC mode is performed > by madt enumerator which pref. should not read LAPIC config (too early). > And it is not clear at all, what to do if there is reason to use xAPIC, > as checked by madt_setup_local(), but we are in x2APIC mode already. > > Anyway, returning to the original issue, I do not believe that the > hand-off on that machine occured in the x2APIC mode when X2APIC_OPT_OUT > is specified. Kernel would fault in that case. As I assume, other OS don't fault in this case. From owner-freebsd-stable@freebsd.org Wed Sep 14 12:23:17 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C41CBD9217 for ; Wed, 14 Sep 2016 12:23:17 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 55ACC1618 for ; Wed, 14 Sep 2016 12:23:17 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 51077BD9214; Wed, 14 Sep 2016 12:23:17 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50AE0BD9211 for ; Wed, 14 Sep 2016 12:23:17 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 83EAE1616 for ; Wed, 14 Sep 2016 12:23:15 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA25631; Wed, 14 Sep 2016 15:23:14 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bk9Dd-0005hq-Uy; Wed, 14 Sep 2016 15:23:13 +0300 Subject: Re: X2APIC support To: Konstantin Belousov References: <20160912175348.GV34394@zxy.spb.ru> <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913152240.GE38409@kib.kiev.ua> <20160914113634.GF38409@kib.kiev.ua> Cc: Slawa Olhovchenkov , stable@FreeBSD.org From: Andriy Gapon Message-ID: <763df55a-4b69-9f7a-1042-0f631a729881@FreeBSD.org> Date: Wed, 14 Sep 2016 15:22:17 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160914113634.GF38409@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 12:23:17 -0000 On 14/09/2016 14:36, Konstantin Belousov wrote: > On Tue, Sep 13, 2016 at 06:52:19PM +0300, Andriy Gapon wrote: >> On 13/09/2016 18:22, Konstantin Belousov wrote: >>> Any access >>> to the LAPIC registers page in x2APIC mode faults. >> >> Is this a fact? >> I read the following in the specification: >> >> In x2APIC mode, the memory mapped interface is not available and any >> access to the MMIO interface will behave similar to that of a legacy xAPIC >> in globally disabled state. >> >> But I couldn't find what actually happens for the legacy xAPIC in globally >> disabled state. For AMD processors it is documented that if xAPIC is disabled >> then accessing the APIC memory range works the same as accessing the regular >> memory. That can be different for Intel processors, of course. > > Look at the native_lapic_init(), very beginning of the function. If > x2apic_mode is non-zero, lapic_map is cleared after DMAP page cache > attributes are changed. Right, but we are talking about the case where x2apic_mode *is zero* while the hardware in x2APIC mode. > Right now, if BIOS pass control to OS in x2APIC mode, thinks just work > because no LAPIC accesses are done until native_lapic_enable_x2apic() is > called. This just happens, I thought about more organized receipt of the > current LAPIC mode. Issue is that decision for LAPIC mode is performed > by madt enumerator which pref. should not read LAPIC config (too early). > And it is not clear at all, what to do if there is reason to use xAPIC, > as checked by madt_setup_local(), but we are in x2APIC mode already. Yes. As I mentioned earlier we should at least panic with an informative message. Maybe we could add some code to so something smarter later. > Anyway, returning to the original issue, I do not believe that the > hand-off on that machine occured in the x2APIC mode when X2APIC_OPT_OUT > is specified. Kernel would fault in that case. I think that it should be easy to check that if Slawa is still willing to try another diagnostic patch. diff --git a/sys/x86/x86/local_apic.c b/sys/x86/x86/local_apic.c index 203e9d00e8acc..37ac03fb9d811 100644 --- a/sys/x86/x86/local_apic.c +++ b/sys/x86/x86/local_apic.c @@ -429,6 +429,12 @@ native_lapic_init(vm_paddr_t addr) if (x2apic_mode) { native_lapic_enable_x2apic(); lapic_map = NULL; + } else if ((cpu_feature2 & CPUID2_X2APIC) != 0) { + r = rdmsr(MSR_APICBASE); + printf("MSR_APICBASE = 0x%16jx\n", (uintmax_t)r); + if ((r & (APICBASE_X2APIC | APICBASE_ENABLED)) == + (APICBASE_X2APIC | APICBASE_ENABLED)) + printf("x2APIC is prohibited but turned on by BIOS\n"); } /* Setup the spurious interrupt handler. */ -- Andriy Gapon From owner-freebsd-stable@freebsd.org Wed Sep 14 12:26:50 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8628EBD93AD for ; Wed, 14 Sep 2016 12:26:50 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7010A1860 for ; Wed, 14 Sep 2016 12:26:50 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6C03DBD93AC; Wed, 14 Sep 2016 12:26:50 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B9FCBD93AA for ; Wed, 14 Sep 2016 12:26:50 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C1B1F185F for ; Wed, 14 Sep 2016 12:26:48 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA25643; Wed, 14 Sep 2016 15:26:48 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bk9H5-0005i3-R4; Wed, 14 Sep 2016 15:26:47 +0300 Subject: Re: X2APIC support To: Slawa Olhovchenkov References: <20160912164412.GS34394@zxy.spb.ru> <5662c700-f139-4754-8693-7adc0f2657be@FreeBSD.org> <20160912175348.GV34394@zxy.spb.ru> <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913145957.GC34394@zxy.spb.ru> Cc: Konstantin Belousov , stable@FreeBSD.org From: Andriy Gapon Message-ID: <8cfc77d4-fc70-34e3-8a10-4fd6b5d32bc0@FreeBSD.org> Date: Wed, 14 Sep 2016 15:25:52 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160913145957.GC34394@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 12:26:50 -0000 On 13/09/2016 17:59, Slawa Olhovchenkov wrote: > Goggling on X2APIC_OPT_OUT take same result: other OS in this case > downgrade to xAPIC mode. It still does not make any sense for BIOS to turn on x2APIC and then instruct the OS that x2APIC must not be used. -- Andriy Gapon From owner-freebsd-stable@freebsd.org Wed Sep 14 12:33:16 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50FE1BD973C for ; Wed, 14 Sep 2016 12:33:16 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3B4CC1E9A for ; Wed, 14 Sep 2016 12:33:16 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 3A697BD973B; Wed, 14 Sep 2016 12:33:16 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A139BD9739 for ; Wed, 14 Sep 2016 12:33:16 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EE9571E99; Wed, 14 Sep 2016 12:33:15 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bk9NJ-0000OG-VX; Wed, 14 Sep 2016 15:33:13 +0300 Date: Wed, 14 Sep 2016 15:33:13 +0300 From: Slawa Olhovchenkov To: Andriy Gapon Cc: Konstantin Belousov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160914123313.GC2840@zxy.spb.ru> References: <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913152240.GE38409@kib.kiev.ua> <20160914113634.GF38409@kib.kiev.ua> <763df55a-4b69-9f7a-1042-0f631a729881@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <763df55a-4b69-9f7a-1042-0f631a729881@FreeBSD.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 12:33:16 -0000 On Wed, Sep 14, 2016 at 03:22:17PM +0300, Andriy Gapon wrote: > On 14/09/2016 14:36, Konstantin Belousov wrote: > > On Tue, Sep 13, 2016 at 06:52:19PM +0300, Andriy Gapon wrote: > >> On 13/09/2016 18:22, Konstantin Belousov wrote: > >>> Any access > >>> to the LAPIC registers page in x2APIC mode faults. > >> > >> Is this a fact? > >> I read the following in the specification: > >> > >> In x2APIC mode, the memory mapped interface is not available and any > >> access to the MMIO interface will behave similar to that of a legacy xAPIC > >> in globally disabled state. > >> > >> But I couldn't find what actually happens for the legacy xAPIC in globally > >> disabled state. For AMD processors it is documented that if xAPIC is disabled > >> then accessing the APIC memory range works the same as accessing the regular > >> memory. That can be different for Intel processors, of course. > > > > Look at the native_lapic_init(), very beginning of the function. If > > x2apic_mode is non-zero, lapic_map is cleared after DMAP page cache > > attributes are changed. > > Right, but we are talking about the case where x2apic_mode *is zero* while the > hardware in x2APIC mode. > > > Right now, if BIOS pass control to OS in x2APIC mode, thinks just work > > because no LAPIC accesses are done until native_lapic_enable_x2apic() is > > called. This just happens, I thought about more organized receipt of the > > current LAPIC mode. Issue is that decision for LAPIC mode is performed > > by madt enumerator which pref. should not read LAPIC config (too early). > > And it is not clear at all, what to do if there is reason to use xAPIC, > > as checked by madt_setup_local(), but we are in x2APIC mode already. > > Yes. As I mentioned earlier we should at least panic with an informative > message. Maybe we could add some code to so something smarter later. > > > Anyway, returning to the original issue, I do not believe that the > > hand-off on that machine occured in the x2APIC mode when X2APIC_OPT_OUT > > is specified. Kernel would fault in that case. > > I think that it should be easy to check that if Slawa is still willing to try > another diagnostic patch. What combination of BIOS setting need? > diff --git a/sys/x86/x86/local_apic.c b/sys/x86/x86/local_apic.c > index 203e9d00e8acc..37ac03fb9d811 100644 > --- a/sys/x86/x86/local_apic.c > +++ b/sys/x86/x86/local_apic.c > @@ -429,6 +429,12 @@ native_lapic_init(vm_paddr_t addr) > if (x2apic_mode) { > native_lapic_enable_x2apic(); > lapic_map = NULL; > + } else if ((cpu_feature2 & CPUID2_X2APIC) != 0) { > + r = rdmsr(MSR_APICBASE); > + printf("MSR_APICBASE = 0x%16jx\n", (uintmax_t)r); > + if ((r & (APICBASE_X2APIC | APICBASE_ENABLED)) == > + (APICBASE_X2APIC | APICBASE_ENABLED)) > + printf("x2APIC is prohibited but turned on by BIOS\n"); > } > > /* Setup the spurious interrupt handler. */ > > > > -- > Andriy Gapon From owner-freebsd-stable@freebsd.org Wed Sep 14 12:36:38 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70F6CBD98AA for ; Wed, 14 Sep 2016 12:36:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5A6A31102 for ; Wed, 14 Sep 2016 12:36:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 59C38BD98A9; Wed, 14 Sep 2016 12:36:38 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 596CABD98A8 for ; Wed, 14 Sep 2016 12:36:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 95E4C1101 for ; Wed, 14 Sep 2016 12:36:36 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA25670; Wed, 14 Sep 2016 15:36:35 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bk9QZ-0005ia-AZ; Wed, 14 Sep 2016 15:36:35 +0300 Subject: Re: X2APIC support To: Slawa Olhovchenkov References: <20160913121133.GX34394@zxy.spb.ru> <71a1f864-66de-0010-5024-e8e985f422f4@FreeBSD.org> <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913152240.GE38409@kib.kiev.ua> <20160914113634.GF38409@kib.kiev.ua> <763df55a-4b69-9f7a-1042-0f631a729881@FreeBSD.org> <20160914123313.GC2840@zxy.spb.ru> Cc: Konstantin Belousov , stable@FreeBSD.org From: Andriy Gapon Message-ID: <966c58d6-db64-2879-6709-0aa596bec24b@FreeBSD.org> Date: Wed, 14 Sep 2016 15:35:39 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160914123313.GC2840@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 12:36:38 -0000 On 14/09/2016 15:33, Slawa Olhovchenkov wrote: > On Wed, Sep 14, 2016 at 03:22:17PM +0300, Andriy Gapon wrote: > >> On 14/09/2016 14:36, Konstantin Belousov wrote: >>> On Tue, Sep 13, 2016 at 06:52:19PM +0300, Andriy Gapon wrote: >>>> On 13/09/2016 18:22, Konstantin Belousov wrote: >>>>> Any access >>>>> to the LAPIC registers page in x2APIC mode faults. >>>> >>>> Is this a fact? >>>> I read the following in the specification: >>>> >>>> In x2APIC mode, the memory mapped interface is not available and any >>>> access to the MMIO interface will behave similar to that of a legacy xAPIC >>>> in globally disabled state. >>>> >>>> But I couldn't find what actually happens for the legacy xAPIC in globally >>>> disabled state. For AMD processors it is documented that if xAPIC is disabled >>>> then accessing the APIC memory range works the same as accessing the regular >>>> memory. That can be different for Intel processors, of course. >>> >>> Look at the native_lapic_init(), very beginning of the function. If >>> x2apic_mode is non-zero, lapic_map is cleared after DMAP page cache >>> attributes are changed. >> >> Right, but we are talking about the case where x2apic_mode *is zero* while the >> hardware in x2APIC mode. >> >>> Right now, if BIOS pass control to OS in x2APIC mode, thinks just work >>> because no LAPIC accesses are done until native_lapic_enable_x2apic() is >>> called. This just happens, I thought about more organized receipt of the >>> current LAPIC mode. Issue is that decision for LAPIC mode is performed >>> by madt enumerator which pref. should not read LAPIC config (too early). >>> And it is not clear at all, what to do if there is reason to use xAPIC, >>> as checked by madt_setup_local(), but we are in x2APIC mode already. >> >> Yes. As I mentioned earlier we should at least panic with an informative >> message. Maybe we could add some code to so something smarter later. >> >>> Anyway, returning to the original issue, I do not believe that the >>> hand-off on that machine occured in the x2APIC mode when X2APIC_OPT_OUT >>> is specified. Kernel would fault in that case. >> >> I think that it should be easy to check that if Slawa is still willing to try >> another diagnostic patch. > > What combination of BIOS setting need? The one that causes the crash. >> diff --git a/sys/x86/x86/local_apic.c b/sys/x86/x86/local_apic.c >> index 203e9d00e8acc..37ac03fb9d811 100644 >> --- a/sys/x86/x86/local_apic.c >> +++ b/sys/x86/x86/local_apic.c >> @@ -429,6 +429,12 @@ native_lapic_init(vm_paddr_t addr) >> if (x2apic_mode) { >> native_lapic_enable_x2apic(); >> lapic_map = NULL; >> + } else if ((cpu_feature2 & CPUID2_X2APIC) != 0) { >> + r = rdmsr(MSR_APICBASE); >> + printf("MSR_APICBASE = 0x%16jx\n", (uintmax_t)r); >> + if ((r & (APICBASE_X2APIC | APICBASE_ENABLED)) == >> + (APICBASE_X2APIC | APICBASE_ENABLED)) >> + printf("x2APIC is prohibited but turned on by BIOS\n"); >> } >> >> /* Setup the spurious interrupt handler. */ >> >> >> >> -- >> Andriy Gapon -- Andriy Gapon From owner-freebsd-stable@freebsd.org Wed Sep 14 12:49:53 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5DA44BDA011 for ; Wed, 14 Sep 2016 12:49:53 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 485A819C9 for ; Wed, 14 Sep 2016 12:49:53 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 4442BBDA010; Wed, 14 Sep 2016 12:49:53 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43D88BDA00F for ; Wed, 14 Sep 2016 12:49:53 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0545B19C7; Wed, 14 Sep 2016 12:49:53 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bk9dP-0000lW-1j; Wed, 14 Sep 2016 15:49:51 +0300 Date: Wed, 14 Sep 2016 15:49:51 +0300 From: Slawa Olhovchenkov To: Andriy Gapon Cc: Konstantin Belousov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160914124950.GE2840@zxy.spb.ru> References: <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913152240.GE38409@kib.kiev.ua> <20160914113634.GF38409@kib.kiev.ua> <763df55a-4b69-9f7a-1042-0f631a729881@FreeBSD.org> <20160914123313.GC2840@zxy.spb.ru> <966c58d6-db64-2879-6709-0aa596bec24b@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <966c58d6-db64-2879-6709-0aa596bec24b@FreeBSD.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 12:49:53 -0000 On Wed, Sep 14, 2016 at 03:35:39PM +0300, Andriy Gapon wrote: > On 14/09/2016 15:33, Slawa Olhovchenkov wrote: > > On Wed, Sep 14, 2016 at 03:22:17PM +0300, Andriy Gapon wrote: > > > >> On 14/09/2016 14:36, Konstantin Belousov wrote: > >>> On Tue, Sep 13, 2016 at 06:52:19PM +0300, Andriy Gapon wrote: > >>>> On 13/09/2016 18:22, Konstantin Belousov wrote: > >>>>> Any access > >>>>> to the LAPIC registers page in x2APIC mode faults. > >>>> > >>>> Is this a fact? > >>>> I read the following in the specification: > >>>> > >>>> In x2APIC mode, the memory mapped interface is not available and any > >>>> access to the MMIO interface will behave similar to that of a legacy xAPIC > >>>> in globally disabled state. > >>>> > >>>> But I couldn't find what actually happens for the legacy xAPIC in globally > >>>> disabled state. For AMD processors it is documented that if xAPIC is disabled > >>>> then accessing the APIC memory range works the same as accessing the regular > >>>> memory. That can be different for Intel processors, of course. > >>> > >>> Look at the native_lapic_init(), very beginning of the function. If > >>> x2apic_mode is non-zero, lapic_map is cleared after DMAP page cache > >>> attributes are changed. > >> > >> Right, but we are talking about the case where x2apic_mode *is zero* while the > >> hardware in x2APIC mode. > >> > >>> Right now, if BIOS pass control to OS in x2APIC mode, thinks just work > >>> because no LAPIC accesses are done until native_lapic_enable_x2apic() is > >>> called. This just happens, I thought about more organized receipt of the > >>> current LAPIC mode. Issue is that decision for LAPIC mode is performed > >>> by madt enumerator which pref. should not read LAPIC config (too early). > >>> And it is not clear at all, what to do if there is reason to use xAPIC, > >>> as checked by madt_setup_local(), but we are in x2APIC mode already. > >> > >> Yes. As I mentioned earlier we should at least panic with an informative > >> message. Maybe we could add some code to so something smarter later. > >> > >>> Anyway, returning to the original issue, I do not believe that the > >>> hand-off on that machine occured in the x2APIC mode when X2APIC_OPT_OUT > >>> is specified. Kernel would fault in that case. > >> > >> I think that it should be easy to check that if Slawa is still willing to try > >> another diagnostic patch. > > > > What combination of BIOS setting need? > > The one that causes the crash. VT(vga): text 80x25 CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2200.05-MHz K8-class CPU) Origin="GenuineIntel" Id=0x406f1 Family=0x6 Model=0x4f Stepping=1 Features=0xbfebfbff Features2=0x7ffefbff AMD Features=0x2c100800 AMD Features2=0x121 Structured Extended Features=0x21cbfbb XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 137438953472 (131072 MB) avail memory = 133407973376 (127227 MB) MSR_APICBASE = 0x fee00d00 x2APIC is prohibited but turned on by BIOS Event timer "LAPIC" quality 600 ACPI APIC Table: boot_cpu_id = 255 kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = ff fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80537e74 stack pointer = 0x28:0xffffffff814b3a60 frame pointer = 0x28:0xffffffff814b3a70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xffffffff805272e7 at kdb_backtrace+0x67 #1 0xffffffff804dd662 at vpanic+0x182 #2 0xffffffff804dd4d3 at panic+0x43 #3 0xffffffff807a37a1 at trap_fatal+0x351 #4 0xffffffff807a3993 at trap_pfault+0x1e3 #5 0xffffffff807a2f1c at trap+0x26c #6 0xffffffff80787ca1 at calltrap+0x8 #7 0xffffffff8083b57a at topo_probe+0x61a #8 0xffffffff8078fe93 at cpu_mp_start+0x1c3 #9 0xffffffff805382ca at mp_start+0x3a #10 0xffffffff80465cd8 at mi_startup+0x118 #11 0xffffffff8028dfac at btext+0x2c Uptime: 1s > >> diff --git a/sys/x86/x86/local_apic.c b/sys/x86/x86/local_apic.c > >> index 203e9d00e8acc..37ac03fb9d811 100644 > >> --- a/sys/x86/x86/local_apic.c > >> +++ b/sys/x86/x86/local_apic.c > >> @@ -429,6 +429,12 @@ native_lapic_init(vm_paddr_t addr) > >> if (x2apic_mode) { > >> native_lapic_enable_x2apic(); > >> lapic_map = NULL; > >> + } else if ((cpu_feature2 & CPUID2_X2APIC) != 0) { > >> + r = rdmsr(MSR_APICBASE); > >> + printf("MSR_APICBASE = 0x%16jx\n", (uintmax_t)r); > >> + if ((r & (APICBASE_X2APIC | APICBASE_ENABLED)) == > >> + (APICBASE_X2APIC | APICBASE_ENABLED)) > >> + printf("x2APIC is prohibited but turned on by BIOS\n"); > >> } > >> > >> /* Setup the spurious interrupt handler. */ > >> > >> > >> > >> -- > >> Andriy Gapon > > > -- > Andriy Gapon From owner-freebsd-stable@freebsd.org Wed Sep 14 13:59:25 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0BBFBBD9E1D for ; Wed, 14 Sep 2016 13:59:25 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id F21D8186B; Wed, 14 Sep 2016 13:59:24 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id D212E1D8; Wed, 14 Sep 2016 13:59:24 +0000 (UTC) Date: Wed, 14 Sep 2016 13:59:22 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org Message-ID: <1681923444.21.1473861563065.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <605729374.14.1473775960094.JavaMail.jenkins@jenkins-9.freebsd.org> References: <605729374.14.1473775960094.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to stable : FreeBSD_stable_10 #398 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkKKb2VAfYQKfu1t7qk4nR5qzUBEI+UqT4BPec4qHVhqUy0FFdq50sMH+3y9bCDNOufctov6VqTNffZ3YXArnZK95YF0OX97fh+E9txYOUX1adc+TikcKjuYpHmL5dE62eaZTI+4A5jnRonskQ1PaoIFz0Kbu4mWzkFsmdiXTraGzomXq4cHUCATA2+K4eDYgjXEQI30z3GOMmmZ4t/+6QGk1cMb/BqMWHbn80AsRCb4tU7Hpd72XLDpsuO7YRP1Q0CjmNAuBOTj+sFiiOe6U9HpqOlQN+iFUvBdZo/ybuy5Kh71cAaYQNL68cYdZJ6binH/DkG3KY/fS7DFYAeuwjwIDAQAB X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 13:59:25 -0000 See From owner-freebsd-stable@freebsd.org Wed Sep 14 14:03:21 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B491FBDA225 for ; Wed, 14 Sep 2016 14:03:21 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9DFCC1005 for ; Wed, 14 Sep 2016 14:03:21 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9D529BDA224; Wed, 14 Sep 2016 14:03:21 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D021BDA223 for ; Wed, 14 Sep 2016 14:03:21 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id EA0A51002 for ; Wed, 14 Sep 2016 14:03:20 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA25848; Wed, 14 Sep 2016 17:03:18 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bkAmT-0005nA-Qq; Wed, 14 Sep 2016 17:03:18 +0300 Subject: Re: X2APIC support To: Slawa Olhovchenkov , Konstantin Belousov References: <20160913124239.GZ34394@zxy.spb.ru> <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913152240.GE38409@kib.kiev.ua> <20160914113634.GF38409@kib.kiev.ua> <763df55a-4b69-9f7a-1042-0f631a729881@FreeBSD.org> <20160914123313.GC2840@zxy.spb.ru> <966c58d6-db64-2879-6709-0aa596bec24b@FreeBSD.org> <20160914124950.GE2840@zxy.spb.ru> Cc: stable@FreeBSD.org From: Andriy Gapon Message-ID: <50cf91d9-072d-76fe-768c-8a6a9515bd93@FreeBSD.org> Date: Wed, 14 Sep 2016 17:02:21 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160914124950.GE2840@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 14:03:21 -0000 On 14/09/2016 15:49, Slawa Olhovchenkov wrote: > MSR_APICBASE = 0x fee00d00 > x2APIC is prohibited but turned on by BIOS Kostik, ^^^^^ P.S. the format string for the value should have been 0x%016jx. -- Andriy Gapon From owner-freebsd-stable@freebsd.org Wed Sep 14 16:08:08 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 682E5BDAE27 for ; Wed, 14 Sep 2016 16:08:08 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4D9C61AAE for ; Wed, 14 Sep 2016 16:08:08 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4CFFFBDAE26; Wed, 14 Sep 2016 16:08:08 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CABABDAE25 for ; Wed, 14 Sep 2016 16:08:08 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EAF941AAD; Wed, 14 Sep 2016 16:08:07 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u8EG82pC031915 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 14 Sep 2016 19:08:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u8EG82pC031915 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u8EG829F031914; Wed, 14 Sep 2016 19:08:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 14 Sep 2016 19:08:02 +0300 From: Konstantin Belousov To: Andriy Gapon Cc: Slawa Olhovchenkov , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160914160802.GH38409@kib.kiev.ua> References: <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913152240.GE38409@kib.kiev.ua> <20160914113634.GF38409@kib.kiev.ua> <763df55a-4b69-9f7a-1042-0f631a729881@FreeBSD.org> <20160914123313.GC2840@zxy.spb.ru> <966c58d6-db64-2879-6709-0aa596bec24b@FreeBSD.org> <20160914124950.GE2840@zxy.spb.ru> <50cf91d9-072d-76fe-768c-8a6a9515bd93@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50cf91d9-072d-76fe-768c-8a6a9515bd93@FreeBSD.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 16:08:08 -0000 On Wed, Sep 14, 2016 at 05:02:21PM +0300, Andriy Gapon wrote: > On 14/09/2016 15:49, Slawa Olhovchenkov wrote: > > MSR_APICBASE = 0x fee00d00 > > x2APIC is prohibited but turned on by BIOS > > Kostik, ^^^^^ Well, the following might work, but I have no good idea what to do when BIOS does handoff with x2APIC enabled and directs us to not enable it. Switching to xAPIC mode is not an option, I suspect. diff --git a/sys/x86/acpica/madt.c b/sys/x86/acpica/madt.c index 241a769..3a93fd6 100644 --- a/sys/x86/acpica/madt.c +++ b/sys/x86/acpica/madt.c @@ -138,7 +138,6 @@ madt_setup_local(void) madt = pmap_mapbios(madt_physaddr, madt_length); if ((cpu_feature2 & CPUID2_X2APIC) != 0) { - x2apic_mode = 1; reason = NULL; /* @@ -150,21 +149,17 @@ madt_setup_local(void) if (dmartbl_physaddr != 0) { dmartbl = acpi_map_table(dmartbl_physaddr, ACPI_SIG_DMAR); - if ((dmartbl->Flags & ACPI_DMAR_X2APIC_OPT_OUT) != 0) { - x2apic_mode = 0; + if ((dmartbl->Flags & ACPI_DMAR_X2APIC_OPT_OUT) != 0) reason = "by DMAR table"; - } acpi_unmap_table(dmartbl); } if (vm_guest == VM_GUEST_VMWARE) { vmware_hvcall(VMW_HVCMD_GETVCPU_INFO, p); if ((p[0] & VMW_VCPUINFO_VCPU_RESERVED) != 0 || - (p[0] & VMW_VCPUINFO_LEGACY_X2APIC) == 0) { - x2apic_mode = 0; - reason = "inside VMWare without intr redirection"; - } + (p[0] & VMW_VCPUINFO_LEGACY_X2APIC) == 0) + reason = + "inside VMWare without intr redirection"; } else if (vm_guest == VM_GUEST_XEN) { - x2apic_mode = 0; reason = "due to running under XEN"; } else if (vm_guest == VM_GUEST_NO && CPUID_TO_FAMILY(cpu_id) == 0x6 && @@ -184,13 +179,21 @@ madt_setup_local(void) if (!strcmp(hw_vendor, "LENOVO") || !strcmp(hw_vendor, "ASUSTeK Computer Inc.")) { - x2apic_mode = 0; reason = "for a suspected SandyBridge BIOS bug"; } freeenv(hw_vendor); } } + if (reason != NULL && lapic_is_x2apic()) { + if (bootverbose) + printf("x2APIC should be disabled %s but " + "already enabled by BIOS; enabling.\n", + reason); + reason = NULL; + } + if (reason == NULL) + x2apic_mode = 1; TUNABLE_INT_FETCH("hw.x2apic_enable", &x2apic_mode); if (!x2apic_mode && reason != NULL && bootverbose) printf("x2APIC available but disabled %s\n", reason); diff --git a/sys/x86/include/apicvar.h b/sys/x86/include/apicvar.h index 1ddb69e..09c3a63 100644 --- a/sys/x86/include/apicvar.h +++ b/sys/x86/include/apicvar.h @@ -206,6 +206,7 @@ struct apic_ops { void (*create)(u_int, int); void (*init)(vm_paddr_t); void (*xapic_mode)(void); + bool (*is_x2apic)(void); void (*setup)(int); void (*dump)(const char *); void (*disable)(void); @@ -268,6 +269,13 @@ lapic_xapic_mode(void) apic_ops.xapic_mode(); } +static inline bool +lapic_is_x2apic(void) +{ + + return (apic_ops.is_x2apic()); +} + static inline void lapic_setup(int boot) { diff --git a/sys/x86/x86/local_apic.c b/sys/x86/x86/local_apic.c index cd774df..d9a3453 100644 --- a/sys/x86/x86/local_apic.c +++ b/sys/x86/x86/local_apic.c @@ -269,6 +269,16 @@ native_lapic_enable_x2apic(void) wrmsr(MSR_APICBASE, apic_base); } +static bool +native_lapic_is_x2apic(void) +{ + uint64_t apic_base; + + apic_base = rdmsr(MSR_APICBASE); + return ((apic_base & (APICBASE_X2APIC | APICBASE_ENABLED)) == + (APICBASE_X2APIC | APICBASE_ENABLED)); +} + static void lapic_enable(void); static void lapic_resume(struct pic *pic, bool suspend_cancelled); static void lapic_timer_oneshot(struct lapic *); @@ -329,6 +339,7 @@ struct apic_ops apic_ops = { .create = native_lapic_create, .init = native_lapic_init, .xapic_mode = native_lapic_xapic_mode, + .is_x2apic = native_lapic_is_x2apic, .setup = native_lapic_setup, .dump = native_lapic_dump, .disable = native_lapic_disable, diff --git a/sys/x86/xen/xen_apic.c b/sys/x86/xen/xen_apic.c index 4d7a39b..45c3c18 100644 --- a/sys/x86/xen/xen_apic.c +++ b/sys/x86/xen/xen_apic.c @@ -139,6 +139,13 @@ xen_pv_lapic_disable(void) } +static bool +xen_pv_lapic_is_x2apic(void) +{ + + return (false); +} + static void xen_pv_lapic_eoi(void) { @@ -351,6 +358,7 @@ struct apic_ops xen_apic_ops = { .create = xen_pv_lapic_create, .init = xen_pv_lapic_init, .xapic_mode = xen_pv_lapic_disable, + .is_x2apic = xen_pv_lapic_is_x2apic, .setup = xen_pv_lapic_setup, .dump = xen_pv_lapic_dump, .disable = xen_pv_lapic_disable, From owner-freebsd-stable@freebsd.org Wed Sep 14 19:26:42 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDF63BDA2F8 for ; Wed, 14 Sep 2016 19:26:42 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id C79DB1FD1 for ; Wed, 14 Sep 2016 19:26:42 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id C3734BDA2F6; Wed, 14 Sep 2016 19:26:42 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C31E2BDA2F5 for ; Wed, 14 Sep 2016 19:26:42 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id EA53A1FCE for ; Wed, 14 Sep 2016 19:26:41 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id WAA26413; Wed, 14 Sep 2016 22:26:33 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bkFpJ-00061u-8w; Wed, 14 Sep 2016 22:26:33 +0300 Subject: Re: X2APIC support To: Konstantin Belousov , Slawa Olhovchenkov References: <20160913142118.GA34394@zxy.spb.ru> <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913152240.GE38409@kib.kiev.ua> <20160914113634.GF38409@kib.kiev.ua> <763df55a-4b69-9f7a-1042-0f631a729881@FreeBSD.org> <20160914123313.GC2840@zxy.spb.ru> <966c58d6-db64-2879-6709-0aa596bec24b@FreeBSD.org> <20160914124950.GE2840@zxy.spb.ru> <50cf91d9-072d-76fe-768c-8a6a9515bd93@FreeBSD.org> <20160914160802.GH38409@kib.kiev.ua> Cc: stable@FreeBSD.org From: Andriy Gapon Message-ID: <791a83d5-3303-038f-7912-9a2671eba485@FreeBSD.org> Date: Wed, 14 Sep 2016 22:25:36 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160914160802.GH38409@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 19:26:43 -0000 On 14/09/2016 19:08, Konstantin Belousov wrote: > Well, the following might work, but I have no good idea what to do > when BIOS does handoff with x2APIC enabled and directs us to not > enable it. Switching to xAPIC mode is not an option, I suspect. The specification describes a way to transition from x2APIC to xAPIC mode, but it's not trivial, because it requires checking all CPU IDs and disabling CPUs with too high ones. Personally, I am not comfortable with your patch. First, it seems that the patch does not cover hw.x2apic_enable=0. And I don't like that we leave x2APIC mode enabled even when we otherwise would not enable it just because BIOS. All in all, if we can't go x2APIC -> xAPIC, then I would prefer a meaningful panic over a "compromise". Just my opinion. The topic probably warrants a wider discussion and a proper review. Slawa, thank you for your persistence and testing. -- Andriy Gapon From owner-freebsd-stable@freebsd.org Wed Sep 14 21:24:31 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C8BCB96667 for ; Wed, 14 Sep 2016 21:24:31 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 66E55179D for ; Wed, 14 Sep 2016 21:24:31 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 62C5DB96665; Wed, 14 Sep 2016 21:24:31 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62673B96664 for ; Wed, 14 Sep 2016 21:24:31 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 232DF179B; Wed, 14 Sep 2016 21:24:31 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkHfO-000DIH-S6; Thu, 15 Sep 2016 00:24:26 +0300 Date: Thu, 15 Sep 2016 00:24:26 +0300 From: Slawa Olhovchenkov To: Konstantin Belousov Cc: Andriy Gapon , stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160914212426.GI2840@zxy.spb.ru> References: <37f5cebc-3fa1-9e95-5123-f3d8daa3130a@FreeBSD.org> <20160913152240.GE38409@kib.kiev.ua> <20160914113634.GF38409@kib.kiev.ua> <763df55a-4b69-9f7a-1042-0f631a729881@FreeBSD.org> <20160914123313.GC2840@zxy.spb.ru> <966c58d6-db64-2879-6709-0aa596bec24b@FreeBSD.org> <20160914124950.GE2840@zxy.spb.ru> <50cf91d9-072d-76fe-768c-8a6a9515bd93@FreeBSD.org> <20160914160802.GH38409@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160914160802.GH38409@kib.kiev.ua> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 21:24:31 -0000 On Wed, Sep 14, 2016 at 07:08:02PM +0300, Konstantin Belousov wrote: > On Wed, Sep 14, 2016 at 05:02:21PM +0300, Andriy Gapon wrote: > > On 14/09/2016 15:49, Slawa Olhovchenkov wrote: > > > MSR_APICBASE = 0x fee00d00 > > > x2APIC is prohibited but turned on by BIOS > > > > Kostik, ^^^^^ > > Well, the following might work, but I have no good idea what to do > when BIOS does handoff with x2APIC enabled and directs us to not > enable it. Switching to xAPIC mode is not an option, I suspect. CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2200.05-MHz K8-class CPU) Origin="GenuineIntel" Id=0x406f1 Family=0x6 Model=0x4f Stepping=1 Features=0xbfebfbff Features2=0x7ffefbff AMD Features=0x2c100800 AMD Features2=0x121 Structured Extended Features=0x21cbfbb XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 137438953472 (131072 MB) avail memory = 133407973376 (127227 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: boot_cpu_id = 0 FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs FreeBSD/SMP: 2 package(s) x 12 core(s) random: unblocking device. ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard random: entropy device external interface module_register_init: MOD_LOAD (vesa, 0xffffffff807bf2f0, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" kbd1 at kbdmux0 netmap: loaded module vtvga0: on motherboard cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) [...] boot OK, w/o any APIC-related messages > diff --git a/sys/x86/acpica/madt.c b/sys/x86/acpica/madt.c > index 241a769..3a93fd6 100644 > --- a/sys/x86/acpica/madt.c > +++ b/sys/x86/acpica/madt.c > @@ -138,7 +138,6 @@ madt_setup_local(void) > > madt = pmap_mapbios(madt_physaddr, madt_length); > if ((cpu_feature2 & CPUID2_X2APIC) != 0) { > - x2apic_mode = 1; > reason = NULL; > > /* > @@ -150,21 +149,17 @@ madt_setup_local(void) > if (dmartbl_physaddr != 0) { > dmartbl = acpi_map_table(dmartbl_physaddr, > ACPI_SIG_DMAR); > - if ((dmartbl->Flags & ACPI_DMAR_X2APIC_OPT_OUT) != 0) { > - x2apic_mode = 0; > + if ((dmartbl->Flags & ACPI_DMAR_X2APIC_OPT_OUT) != 0) > reason = "by DMAR table"; > - } > acpi_unmap_table(dmartbl); > } > if (vm_guest == VM_GUEST_VMWARE) { > vmware_hvcall(VMW_HVCMD_GETVCPU_INFO, p); > if ((p[0] & VMW_VCPUINFO_VCPU_RESERVED) != 0 || > - (p[0] & VMW_VCPUINFO_LEGACY_X2APIC) == 0) { > - x2apic_mode = 0; > - reason = "inside VMWare without intr redirection"; > - } > + (p[0] & VMW_VCPUINFO_LEGACY_X2APIC) == 0) > + reason = > + "inside VMWare without intr redirection"; > } else if (vm_guest == VM_GUEST_XEN) { > - x2apic_mode = 0; > reason = "due to running under XEN"; > } else if (vm_guest == VM_GUEST_NO && > CPUID_TO_FAMILY(cpu_id) == 0x6 && > @@ -184,13 +179,21 @@ madt_setup_local(void) > if (!strcmp(hw_vendor, "LENOVO") || > !strcmp(hw_vendor, > "ASUSTeK Computer Inc.")) { > - x2apic_mode = 0; > reason = > "for a suspected SandyBridge BIOS bug"; > } > freeenv(hw_vendor); > } > } > + if (reason != NULL && lapic_is_x2apic()) { > + if (bootverbose) > + printf("x2APIC should be disabled %s but " > + "already enabled by BIOS; enabling.\n", > + reason); > + reason = NULL; > + } > + if (reason == NULL) > + x2apic_mode = 1; > TUNABLE_INT_FETCH("hw.x2apic_enable", &x2apic_mode); > if (!x2apic_mode && reason != NULL && bootverbose) > printf("x2APIC available but disabled %s\n", reason); > diff --git a/sys/x86/include/apicvar.h b/sys/x86/include/apicvar.h > index 1ddb69e..09c3a63 100644 > --- a/sys/x86/include/apicvar.h > +++ b/sys/x86/include/apicvar.h > @@ -206,6 +206,7 @@ struct apic_ops { > void (*create)(u_int, int); > void (*init)(vm_paddr_t); > void (*xapic_mode)(void); > + bool (*is_x2apic)(void); > void (*setup)(int); > void (*dump)(const char *); > void (*disable)(void); > @@ -268,6 +269,13 @@ lapic_xapic_mode(void) > apic_ops.xapic_mode(); > } > > +static inline bool > +lapic_is_x2apic(void) > +{ > + > + return (apic_ops.is_x2apic()); > +} > + > static inline void > lapic_setup(int boot) > { > diff --git a/sys/x86/x86/local_apic.c b/sys/x86/x86/local_apic.c > index cd774df..d9a3453 100644 > --- a/sys/x86/x86/local_apic.c > +++ b/sys/x86/x86/local_apic.c > @@ -269,6 +269,16 @@ native_lapic_enable_x2apic(void) > wrmsr(MSR_APICBASE, apic_base); > } > > +static bool > +native_lapic_is_x2apic(void) > +{ > + uint64_t apic_base; > + > + apic_base = rdmsr(MSR_APICBASE); > + return ((apic_base & (APICBASE_X2APIC | APICBASE_ENABLED)) == > + (APICBASE_X2APIC | APICBASE_ENABLED)); > +} > + > static void lapic_enable(void); > static void lapic_resume(struct pic *pic, bool suspend_cancelled); > static void lapic_timer_oneshot(struct lapic *); > @@ -329,6 +339,7 @@ struct apic_ops apic_ops = { > .create = native_lapic_create, > .init = native_lapic_init, > .xapic_mode = native_lapic_xapic_mode, > + .is_x2apic = native_lapic_is_x2apic, > .setup = native_lapic_setup, > .dump = native_lapic_dump, > .disable = native_lapic_disable, > diff --git a/sys/x86/xen/xen_apic.c b/sys/x86/xen/xen_apic.c > index 4d7a39b..45c3c18 100644 > --- a/sys/x86/xen/xen_apic.c > +++ b/sys/x86/xen/xen_apic.c > @@ -139,6 +139,13 @@ xen_pv_lapic_disable(void) > > } > > +static bool > +xen_pv_lapic_is_x2apic(void) > +{ > + > + return (false); > +} > + > static void > xen_pv_lapic_eoi(void) > { > @@ -351,6 +358,7 @@ struct apic_ops xen_apic_ops = { > .create = xen_pv_lapic_create, > .init = xen_pv_lapic_init, > .xapic_mode = xen_pv_lapic_disable, > + .is_x2apic = xen_pv_lapic_is_x2apic, > .setup = xen_pv_lapic_setup, > .dump = xen_pv_lapic_dump, > .disable = xen_pv_lapic_disable, From owner-freebsd-stable@freebsd.org Wed Sep 14 21:35:06 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 730D7B968FF for ; Wed, 14 Sep 2016 21:35:06 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 36EDA1CB5 for ; Wed, 14 Sep 2016 21:35:06 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkHpg-000DZ1-1F; Thu, 15 Sep 2016 00:35:04 +0300 Date: Thu, 15 Sep 2016 00:35:04 +0300 From: Slawa Olhovchenkov To: hiren panchasara Cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914213503.GJ2840@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160905014612.GA42393@strugglingcoder.info> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 21:35:06 -0000 On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > Under high network load and may be addtional conditional system go to > > unresponsible state -- no reaction to network and console (USB IPMI > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > debug this? > > Can you panic it from console to get to db> to get backtrace and other > info when it goes unresponsive? ipmi console don't respond (chassis power diag don't react) login on sol console stuck on *tcp. From owner-freebsd-stable@freebsd.org Wed Sep 14 21:43:07 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E97F8B96C0A for ; Wed, 14 Sep 2016 21:43:07 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id D6A5A107A for ; Wed, 14 Sep 2016 21:43:07 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 7D26A1734C; Wed, 14 Sep 2016 14:43:06 -0700 (PDT) Date: Wed, 14 Sep 2016 14:43:06 -0700 From: hiren panchasara To: Slawa Olhovchenkov Cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914214306.GU9397@strugglingcoder.info> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="xi8lRpXYeGgNnUjs" Content-Disposition: inline In-Reply-To: <20160914213503.GJ2840@zxy.spb.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 21:43:08 -0000 --xi8lRpXYeGgNnUjs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: >=20 > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > Under high network load and may be addtional conditional system go to > > > unresponsible state -- no reaction to network and console (USB IPMI > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > debug this? > >=20 > > Can you panic it from console to get to db> to get backtrace and other > > info when it goes unresponsive? >=20 > ipmi console don't respond (chassis power diag don't react) > login on sol console stuck on *tcp. I assume you tried ~^b (tilda followed by ctrl+b) without success? That usually drops into db> I am also fighting an issue where upon said keystrokes, I see=20 "KDB: enter: Break to debugger" but it doesn't drop to db> At that point I have to 'ipmitool blah power reset' the box. Cheers, Hiren --xi8lRpXYeGgNnUjs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJX2cRmXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lF3QH/RDnMatewC1kNve/TT5NQJEJ /prEfbRYB3yQv9d9D3SxDuxELecbosoIaPNohW1VmNq8vC+ctuBgy3NupgcfAhw5 CJcRhn3MgpZT+i04dBBkCTA0BpCUCfZ2jmme/HCzp5AGaNZy/aHCkBlDqC7PbC/i sFmrN/L5jFVAKS9SRuRCRcTma14iMuD8ZzxdiwobEc4Lpa/geuF49n70DiiGA1mm 9z7ouEMZvAqTlj/fyMSEO9GlAcJy6WGVBvOCyiOIm0Rb9t2Bw+pycq0YA3Wjuy6X yoo4FRHU3ItR72/cNGZhosHTKvKEKoO8f5+sFvsKpta0eF3J84UMN6W9+IA88+w= =PUtd -----END PGP SIGNATURE----- --xi8lRpXYeGgNnUjs-- From owner-freebsd-stable@freebsd.org Wed Sep 14 21:56:58 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECD97B96FCF for ; Wed, 14 Sep 2016 21:56:58 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id DF2C31761 for ; Wed, 14 Sep 2016 21:56:58 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 7C18017358; Wed, 14 Sep 2016 14:56:57 -0700 (PDT) Date: Wed, 14 Sep 2016 14:56:57 -0700 From: hiren panchasara To: Slawa Olhovchenkov Cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914215657.GV9397@strugglingcoder.info> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="McQJJYUzjTUqtsGv" Content-Disposition: inline In-Reply-To: <20160914213503.GJ2840@zxy.spb.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 21:56:59 -0000 --McQJJYUzjTUqtsGv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: >=20 > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > Under high network load and may be addtional conditional system go to > > > unresponsible state -- no reaction to network and console (USB IPMI > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > debug this? > >=20 > > Can you panic it from console to get to db> to get backtrace and other > > info when it goes unresponsive? >=20 > ipmi console don't respond (chassis power diag don't react) > login on sol console stuck on *tcp. Also *tcp means its stuck on lock tcp? if so, that'd be lock on V_tcbinfo. I think? tcp_subr.c has tcp_init() which calls in_pcbinfo_init(&V_tcbinfo, "tcp", &V_tcb, hashsize, hashsize, "tcp_inpcb", tcp_inpcb_init, NULL, 0, IPI_HASHFIELDS_4TUPLE); and "tcp" is the name used to initialise the lock inside in_pcbinfo_init() with INP_INFO_LOCK_INIT(pcbinfo, name);=20 What exact svn rev are you on? Also do you have any local changes? Cheers, Hiren --McQJJYUzjTUqtsGv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJX2cemXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/llfsIAJRtMAP8XgYD+8UEtAWZb8he rIGOf5ELS1mCki3DJE+5c24+oj6k5W2tRlgfJk2e/Rx2AY3kZlW63A8ypceT1ieQ Um67B9ntrL7Ad+MMzow9r92JGpijU5Sq0GxBK8V/GP1OZ0fqd+geqc+BcF1p952v pAdS8ehw/KMbtQAnL9PuNFNQb01pIG3mU3SJ7Jie+g8LZRno242gH/yXYXTwlI8d 2BdAkyUeanfj6LxDJBgITx7uiff8RlDcbw9s3IQeNvIV/snkGt/BSPj59kYBdwe2 RnYAUlSf2unJXG10SDQ5YSAPabrjU0WtD250yB/oNU2oO3+xxAI910OBHrZFi8s= =6prP -----END PGP SIGNATURE----- --McQJJYUzjTUqtsGv-- From owner-freebsd-stable@freebsd.org Wed Sep 14 21:57:16 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBAEDBDA019 for ; Wed, 14 Sep 2016 21:57:16 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AEDB61867 for ; Wed, 14 Sep 2016 21:57:16 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkIB8-000E6W-Dv; Thu, 15 Sep 2016 00:57:14 +0300 Date: Thu, 15 Sep 2016 00:57:14 +0300 From: Slawa Olhovchenkov To: hiren panchasara Cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914215714.GK2840@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160914214306.GU9397@strugglingcoder.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160914214306.GU9397@strugglingcoder.info> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 21:57:17 -0000 On Wed, Sep 14, 2016 at 02:43:06PM -0700, hiren panchasara wrote: > On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > Under high network load and may be addtional conditional system go to > > > > unresponsible state -- no reaction to network and console (USB IPMI > > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > > debug this? > > > > > > Can you panic it from console to get to db> to get backtrace and other > > > info when it goes unresponsive? > > > > ipmi console don't respond (chassis power diag don't react) > > login on sol console stuck on *tcp. > > I assume you tried ~^b (tilda followed by ctrl+b) without success? ~B, as in man ipmitool > That usually drops into db> May be now need some sysctl for enable this? > I am also fighting an issue where upon said keystrokes, I see > "KDB: enter: Break to debugger" but it doesn't drop to db> > At that point I have to 'ipmitool blah power reset' the box. > > Cheers, > Hiren From owner-freebsd-stable@freebsd.org Wed Sep 14 22:00:10 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48583BDA19E for ; Wed, 14 Sep 2016 22:00:10 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0A3D21A32 for ; Wed, 14 Sep 2016 22:00:10 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkIDw-000EBJ-3A; Thu, 15 Sep 2016 01:00:08 +0300 Date: Thu, 15 Sep 2016 01:00:08 +0300 From: Slawa Olhovchenkov To: hiren panchasara Cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914220008.GL2840@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160914215657.GV9397@strugglingcoder.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160914215657.GV9397@strugglingcoder.info> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 22:00:10 -0000 On Wed, Sep 14, 2016 at 02:56:57PM -0700, hiren panchasara wrote: > On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > Under high network load and may be addtional conditional system go to > > > > unresponsible state -- no reaction to network and console (USB IPMI > > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > > debug this? > > > > > > Can you panic it from console to get to db> to get backtrace and other > > > info when it goes unresponsive? > > > > ipmi console don't respond (chassis power diag don't react) > > login on sol console stuck on *tcp. > > Also *tcp means its stuck on lock tcp? if so, that'd be lock on > V_tcbinfo. I think? > > tcp_subr.c has tcp_init() which calls > in_pcbinfo_init(&V_tcbinfo, "tcp", &V_tcb, hashsize, hashsize, > "tcp_inpcb", tcp_inpcb_init, NULL, 0, IPI_HASHFIELDS_4TUPLE); > > and "tcp" is the name used to initialise the lock inside > in_pcbinfo_init() with > INP_INFO_LOCK_INIT(pcbinfo, name); > > What exact svn rev are you on? r305117 > Also do you have any local changes? only kerberos related. I am using kerberos and NIS. From owner-freebsd-stable@freebsd.org Wed Sep 14 22:04:21 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D882BDA409 for ; Wed, 14 Sep 2016 22:04:21 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id 6F4171F83 for ; Wed, 14 Sep 2016 22:04:20 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 5EC8717380; Wed, 14 Sep 2016 15:04:20 -0700 (PDT) Date: Wed, 14 Sep 2016 15:04:20 -0700 From: hiren panchasara To: Slawa Olhovchenkov Cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914220420.GW9397@strugglingcoder.info> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160914214306.GU9397@strugglingcoder.info> <20160914215714.GK2840@zxy.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="35rzUHtxHARXKmYf" Content-Disposition: inline In-Reply-To: <20160914215714.GK2840@zxy.spb.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 22:04:21 -0000 --35rzUHtxHARXKmYf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 09/15/16 at 12:57P, Slawa Olhovchenkov wrote: > On Wed, Sep 14, 2016 at 02:43:06PM -0700, hiren panchasara wrote: >=20 > > On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > >=20 > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > > Under high network load and may be addtional conditional system g= o to > > > > > unresponsible state -- no reaction to network and console (USB IP= MI > > > > > emulation). INVARIANTS give to high overhad. Is this exist some w= ay to > > > > > debug this? > > > >=20 > > > > Can you panic it from console to get to db> to get backtrace and ot= her > > > > info when it goes unresponsive? > > >=20 > > > ipmi console don't respond (chassis power diag don't react) > > > login on sol console stuck on *tcp. > >=20 > > I assume you tried ~^b (tilda followed by ctrl+b) without success? >=20 > ~B, as in man ipmitool No, not shift-b but ctrl-b. I am not aware of ipmitool reference. On unresponsive console, try ~^b (tilda followed by ctrl+b) >=20 > > That usually drops into db> >=20 > May be now need some sysctl for enable this? There is a sysctl for this too but on console, the keystrokes I said should work, imo. Cheers, Hiren --35rzUHtxHARXKmYf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJX2clkXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lQjoH/0QMS4+dHSN2H3Ean0aJ4noz BnarS4LzatJfuJlGqXVvCRLUCTIwcw4BSoTQpW2LqgMcFvmcnCpUXu6DoSQuq++J MVbPZ9gqB5zGv6sh9uoa974meGKxBz60UaZstfSfzsvnqcQf8mnp1/JtrL90G1ed JKLy0prGjUge9Im4pMx7M3rsnCQakoNWgrfnVbRjOWIA+uqllNd5iBXi7Q7zAsRn D4RWATZOJkUH3xrgchTZUXspLUZYQ8HYGzRcIqdCOsk5ChpS+R3EOfdzeGYoRHEn 0qF1TTvt3Y0KrnMMtKU2V2VZlVgo2wi5mCU8uo6w2h2LlrQyV89ld7oRBk6dIxY= =N9WX -----END PGP SIGNATURE----- --35rzUHtxHARXKmYf-- From owner-freebsd-stable@freebsd.org Wed Sep 14 22:13:38 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09FBABDA8BC for ; Wed, 14 Sep 2016 22:13:38 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C08B417D1 for ; Wed, 14 Sep 2016 22:13:37 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkIQx-000EW1-Ka; Thu, 15 Sep 2016 01:13:35 +0300 Date: Thu, 15 Sep 2016 01:13:35 +0300 From: Slawa Olhovchenkov To: hiren panchasara Cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914221335.GM2840@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160914214306.GU9397@strugglingcoder.info> <20160914215714.GK2840@zxy.spb.ru> <20160914220420.GW9397@strugglingcoder.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160914220420.GW9397@strugglingcoder.info> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 22:13:38 -0000 On Wed, Sep 14, 2016 at 03:04:20PM -0700, hiren panchasara wrote: > On 09/15/16 at 12:57P, Slawa Olhovchenkov wrote: > > On Wed, Sep 14, 2016 at 02:43:06PM -0700, hiren panchasara wrote: > > > > > On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > > > Under high network load and may be addtional conditional system go to > > > > > > unresponsible state -- no reaction to network and console (USB IPMI > > > > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > > > > debug this? > > > > > > > > > > Can you panic it from console to get to db> to get backtrace and other > > > > > info when it goes unresponsive? > > > > > > > > ipmi console don't respond (chassis power diag don't react) > > > > login on sol console stuck on *tcp. > > > > > > I assume you tried ~^b (tilda followed by ctrl+b) without success? > > > > ~B, as in man ipmitool > > No, not shift-b but ctrl-b. > > I am not aware of ipmitool reference. On unresponsive console, try > ~^b (tilda followed by ctrl+b) ipmitool ~B send break, do you talk about break or about special serial console keystroke to enter debuger, distinct from break? > > > > > That usually drops into db> > > > > May be now need some sysctl for enable this? > > There is a sysctl for this too but on console, the keystrokes I said > should work, imo. > > Cheers, > Hiren From owner-freebsd-stable@freebsd.org Wed Sep 14 22:17:18 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8497BBDAB07 for ; Wed, 14 Sep 2016 22:17:18 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 117F41A97 for ; Wed, 14 Sep 2016 22:17:18 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-wm0-x233.google.com with SMTP id l68so167395wml.1 for ; Wed, 14 Sep 2016 15:17:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=P/pkt4vS3mTjgFBz5qEIIiUTCyAilSUJHcHDeJRdV5U=; b=ce+Jka2Hd/CnQO6AB5/eX4UIHWByQr12vbjOyNab1RHy1kja1Fh7c4W0ieUJyHfGW5 WIFAIW3bmIMhCTQu+N+1NA27PyplASy60iSEy6gzpJ8cEnoBZywDgiUQ0JtOXp6ai8Ro lIEUnItpb+A7ySZMeO/VHFQrc+3dpZ/QkFa23YRxhpWybh9tEb3BwWcJhDfHEF4Eynty OvJUTsxC12Tbr78jJezcoXH8PhyQvhzHNt8vC3cteSEud8W6ZZxB5G6nx1yv1+C9dHZX E+7PYBncyDifULwTBe47Va+c1t6XoTqUONK8QyVX7X2agQ05KOYXgVKZuvza5PK02Elc fYcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=P/pkt4vS3mTjgFBz5qEIIiUTCyAilSUJHcHDeJRdV5U=; b=J7XVbieF5CQG8ZMbnSBygorQDZ0p10mIQalNf/zXz71wMbvV+2onoX3KaqJXUYkQU+ TeCNEmhURa8Ye3EtUQ30tK0k8TYoKfMSJeowhwi42+4CiSso4m/C7wjlJA2iHRUtefQm kypRu5thcAbcqTHn19SJdVUWM44EfqPs+dcjU32wNwNmgNT3iYIxq2dTMDKYLi8Pfuak ckSdVibL9nyUkrfOjSImIqGEDnoaBfMov6cbsg55TStVOwswRgnPSo16KSGyBOk8Ysi/ QDGeEVPtefMDdrgj8EnImf0G2MnfLx7wJvHMeVQsSomr3Ydi0YRsuoOCij5o9Fd8HH4q Hd2Q== X-Gm-Message-State: AE9vXwOlKp0f5HlKqu14WsAQeUqDYHahocwFS7W9ITcbYWVg1oIIFYoNMzl+zxvmHR7soslqMs838tWJ8sCyyHyg X-Received: by 10.194.9.228 with SMTP id d4mr4716146wjb.135.1473891436623; Wed, 14 Sep 2016 15:17:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.139.208 with HTTP; Wed, 14 Sep 2016 15:17:16 -0700 (PDT) In-Reply-To: References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160905074348.GE34394@zxy.spb.ru> From: Oliver Pinter Date: Thu, 15 Sep 2016 00:17:16 +0200 Message-ID: Subject: 11.0 stuck on high network load To: Warner Losh Cc: Slawa Olhovchenkov , FreeBSD-STABLE Mailing List , hiren panchasara Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 22:17:18 -0000 On Monday, September 5, 2016, Warner Losh > wrote: > On Mon, Sep 5, 2016 at 1:43 AM, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > >> On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > >> > I am try using 11.0 on Dual E5-2620 (no X2APIC). > >> > Under high network load and may be addtional conditional system go to > >> > unresponsible state -- no reaction to network and console (USB IPMI > >> > emulation). INVARIANTS give to high overhad. Is this exist some way to > >> > debug this? > >> > >> Can you panic it from console to get to db> to get backtrace and other > >> info when it goes unresponsive? > > > > no > > no reaction > > So the canonical 'ipmitool chassis power diag' doesn't send an NMI to > get you to the debugger? > > I've seen this at Netflix on one variant of our flash offload box with > a Intel e5-2697v2 running with the Chelsio driver. We're working > around it by having fewer receive threads than CPUs in the system. The > only way the boxes would come back was with watchdog. The load was > streaming video > ~36Gbps out 4 lagged 10G ports. Console is totally > unresponsive as well. > Try to set kern.sched.preempt_thresh sysctl to 224 to get back your > console.. > This is on our FreeBSD-10 stable based fork. > From my debugging, we go from totally fine as far as I can tell from > ps, etc in the moments leading to the hang to being totally wedged. It > seems a very sudden-onset condition. Sound at all familiar? > > Warner > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://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 14 22:23:22 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CBBACBDADFD for ; Wed, 14 Sep 2016 22:23:22 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 955801E97 for ; Wed, 14 Sep 2016 22:23:22 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bkIaO-0007MA-22; Wed, 14 Sep 2016 23:23:20 +0100 Date: Wed, 14 Sep 2016 23:23:20 +0100 From: Gary Palmer To: Slawa Olhovchenkov Cc: hiren panchasara , freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914222319.GD42278@in-addr.com> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160914214306.GU9397@strugglingcoder.info> <20160914215714.GK2840@zxy.spb.ru> <20160914220420.GW9397@strugglingcoder.info> <20160914221335.GM2840@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160914221335.GM2840@zxy.spb.ru> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 22:23:22 -0000 On Thu, Sep 15, 2016 at 01:13:35AM +0300, Slawa Olhovchenkov wrote: > On Wed, Sep 14, 2016 at 03:04:20PM -0700, hiren panchasara wrote: > > > On 09/15/16 at 12:57P, Slawa Olhovchenkov wrote: > > > On Wed, Sep 14, 2016 at 02:43:06PM -0700, hiren panchasara wrote: > > > > > > > On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > > > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > > > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > > > > Under high network load and may be addtional conditional system go to > > > > > > > unresponsible state -- no reaction to network and console (USB IPMI > > > > > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > > > > > debug this? > > > > > > > > > > > > Can you panic it from console to get to db> to get backtrace and other > > > > > > info when it goes unresponsive? > > > > > > > > > > ipmi console don't respond (chassis power diag don't react) > > > > > login on sol console stuck on *tcp. > > > > > > > > I assume you tried ~^b (tilda followed by ctrl+b) without success? > > > > > > ~B, as in man ipmitool > > > > No, not shift-b but ctrl-b. > > > > I am not aware of ipmitool reference. On unresponsive console, try > > ~^b (tilda followed by ctrl+b) > > ipmitool ~B send break, do you talk about break or about special > serial console keystroke to enter debuger, distinct from break? A lot of old console servers used to send break when they reset or on boot, so the FreeBSD console does not break to debugger when a break command is received. That's why the tidla CTRL-b is required as it's sufficiently unlikely to be accidentally sent by equipment connected to the serial console. Regards, Gary From owner-freebsd-stable@freebsd.org Wed Sep 14 22:25:35 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4EDBBDAF16 for ; Wed, 14 Sep 2016 22:25:35 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A252310CB; Wed, 14 Sep 2016 22:25:35 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkIcV-000Eoy-UR; Thu, 15 Sep 2016 01:25:31 +0300 Date: Thu, 15 Sep 2016 01:25:31 +0300 From: Slawa Olhovchenkov To: Gary Palmer Cc: hiren panchasara , freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914222531.GN2840@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160914214306.GU9397@strugglingcoder.info> <20160914215714.GK2840@zxy.spb.ru> <20160914220420.GW9397@strugglingcoder.info> <20160914221335.GM2840@zxy.spb.ru> <20160914222319.GD42278@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160914222319.GD42278@in-addr.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 22:25:36 -0000 On Wed, Sep 14, 2016 at 11:23:20PM +0100, Gary Palmer wrote: > On Thu, Sep 15, 2016 at 01:13:35AM +0300, Slawa Olhovchenkov wrote: > > On Wed, Sep 14, 2016 at 03:04:20PM -0700, hiren panchasara wrote: > > > > > On 09/15/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > On Wed, Sep 14, 2016 at 02:43:06PM -0700, hiren panchasara wrote: > > > > > > > > > On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > > > > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > > > > > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > > > > > Under high network load and may be addtional conditional system go to > > > > > > > > unresponsible state -- no reaction to network and console (USB IPMI > > > > > > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > > > > > > debug this? > > > > > > > > > > > > > > Can you panic it from console to get to db> to get backtrace and other > > > > > > > info when it goes unresponsive? > > > > > > > > > > > > ipmi console don't respond (chassis power diag don't react) > > > > > > login on sol console stuck on *tcp. > > > > > > > > > > I assume you tried ~^b (tilda followed by ctrl+b) without success? > > > > > > > > ~B, as in man ipmitool > > > > > > No, not shift-b but ctrl-b. > > > > > > I am not aware of ipmitool reference. On unresponsive console, try > > > ~^b (tilda followed by ctrl+b) > > > > ipmitool ~B send break, do you talk about break or about special > > serial console keystroke to enter debuger, distinct from break? > > A lot of old console servers used to send break when they reset or > on boot, so the FreeBSD console does not break to debugger when > a break command is received. That's why the tidla CTRL-b is > required as it's sufficiently unlikely to be accidentally sent by > equipment connected to the serial console. OK, thanks to clarification, I am try ~^B on next attempt. From owner-freebsd-stable@freebsd.org Wed Sep 14 23:33:16 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A970BDA452 for ; Wed, 14 Sep 2016 23:33:16 +0000 (UTC) (envelope-from astral@wangsamp.km.ua) Received: from h.sputnikmedia.net (h.sputnikmedia.net [193.239.68.13]) by mx1.freebsd.org (Postfix) with ESMTP id CC5771DD3 for ; Wed, 14 Sep 2016 23:33:15 +0000 (UTC) (envelope-from astral@wangsamp.km.ua) Received: from h.sputnikmedia.net (h.sputnikmedia.net [193.239.68.13]) by h.sputnikmedia.net (Postfix) with ESMTP id 461F41708D; Thu, 15 Sep 2016 02:33:07 +0300 (EEST) Date: Thu, 15 Sep 2016 02:33:07 +0300 (EEST) From: "Oleksandr V. Typlyns'kyi" To: Slawa Olhovchenkov cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load In-Reply-To: <20160904215739.GC22212@zxy.spb.ru> Message-ID: References: <20160904215739.GC22212@zxy.spb.ru> X-Mailer: MTA++ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 23:33:16 -0000 Sep 5 Sep 5, 2016 at 00:57 Slawa Olhovchenkov wrote: > I am try using 11.0 on Dual E5-2620 (no X2APIC). > Under high network load and may be addtional conditional system go to > unresponsible state -- no reaction to network and console (USB IPMI > emulation). INVARIANTS give to high overhad. Is this exist some way to > debug this? Do you have any routing table changes? In my case system totally hangs after route change command invocation. Sequence of commands route del + route add works fine. Maybe it is FIB related, but with -fib option system hangs too. -- WNGS-RIPE From owner-freebsd-stable@freebsd.org Wed Sep 14 23:51:10 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C22A3BDA9E0 for ; Wed, 14 Sep 2016 23:51:10 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 82E7A15EF for ; Wed, 14 Sep 2016 23:51:10 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkJxK-000GsK-Df; Thu, 15 Sep 2016 02:51:06 +0300 Date: Thu, 15 Sep 2016 02:51:06 +0300 From: Slawa Olhovchenkov To: "Oleksandr V. Typlyns'kyi" Cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160914235106.GO2840@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2016 23:51:10 -0000 On Thu, Sep 15, 2016 at 02:33:07AM +0300, Oleksandr V. Typlyns'kyi wrote: > Sep 5 Sep 5, 2016 at 00:57 Slawa Olhovchenkov wrote: > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > Under high network load and may be addtional conditional system go to > > unresponsible state -- no reaction to network and console (USB IPMI > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > debug this? > > Do you have any routing table changes? > In my case system totally hangs after route change command invocation. > Sequence of commands route del + route add works fine. > Maybe it is FIB related, but with -fib option system hangs too. No, only default exist and don't changed From owner-freebsd-stable@freebsd.org Thu Sep 15 08:59:43 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D57DBBDCB0B for ; Thu, 15 Sep 2016 08:59:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 549FE1BC8 for ; Thu, 15 Sep 2016 08:59:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u8F8xcSu046655 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 15 Sep 2016 11:59:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u8F8xcSu046655 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u8F8xcq4046654; Thu, 15 Sep 2016 11:59:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 15 Sep 2016 11:59:38 +0300 From: Konstantin Belousov To: Slawa Olhovchenkov Cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160915085938.GN38409@kib.kiev.ua> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160914213503.GJ2840@zxy.spb.ru> User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 08:59:43 -0000 On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrote: > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > Under high network load and may be addtional conditional system go to > > > unresponsible state -- no reaction to network and console (USB IPMI > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > debug this? > > > > Can you panic it from console to get to db> to get backtrace and other > > info when it goes unresponsive? > > ipmi console don't respond (chassis power diag don't react) > login on sol console stuck on *tcp. Is 'login' you reference is the ipmi client state, or you mean login(1) on the wedged host ? If BMC stops responding simultaneously with the host, I would suspect the hardware platform issues instead of a software problem. Do you have dedicated LAN port for BMC ? From owner-freebsd-stable@freebsd.org Thu Sep 15 09:06:35 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A32F8BDCEF8 for ; Thu, 15 Sep 2016 09:06:35 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 67C4010BB for ; Thu, 15 Sep 2016 09:06:35 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkScr-0004Qj-Em; Thu, 15 Sep 2016 12:06:33 +0300 Date: Thu, 15 Sep 2016 12:06:33 +0300 From: Slawa Olhovchenkov To: Konstantin Belousov Cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160915090633.GS2840@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160915085938.GN38409@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160915085938.GN38409@kib.kiev.ua> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 09:06:35 -0000 On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > Under high network load and may be addtional conditional system go to > > > > unresponsible state -- no reaction to network and console (USB IPMI > > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > > debug this? > > > > > > Can you panic it from console to get to db> to get backtrace and other > > > info when it goes unresponsive? > > > > ipmi console don't respond (chassis power diag don't react) > > login on sol console stuck on *tcp. > > Is 'login' you reference is the ipmi client state, or you mean login(1) > on the wedged host ? on the wedged host > If BMC stops responding simultaneously with the host, I would suspect > the hardware platform issues instead of a software problem. Do you have > dedicated LAN port for BMC ? Yes. But BMC emulate USB keyboard and this is may be lock inside USB system. "ipmi console don't respond" must be read as "ipmi console runnnig and attached but system don't react to keypress on this console". at the sime moment system respon to `enter` on ipmi sol console, but after enter `root` stuck in login in the '*tcp' state (I think this is NIS related). From owner-freebsd-stable@freebsd.org Thu Sep 15 14:41:07 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1CB8BDB014 for ; Thu, 15 Sep 2016 14:41:07 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5A90795B; Thu, 15 Sep 2016 14:41:07 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkXqZ-000CD5-AT; Thu, 15 Sep 2016 17:41:03 +0300 Date: Thu, 15 Sep 2016 17:41:03 +0300 From: Slawa Olhovchenkov To: freebsd-stable@freebsd.org Cc: John Baldwin Subject: Re: nginx and FreeBSD11 Message-ID: <20160915144103.GB2960@zxy.spb.ru> References: <20160907191348.GD22212@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160907191348.GD22212@zxy.spb.ru> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 14:41:07 -0000 On Wed, Sep 07, 2016 at 10:13:48PM +0300, Slawa Olhovchenkov wrote: > I am have strange issuse with nginx on FreeBSD11. > I am have FreeBSD11 instaled over STABLE-10. > nginx build for FreeBSD10 and run w/o recompile work fine. > nginx build for FreeBSD11 crushed inside rbtree lookups: next node > totaly craped. > > I am see next potential cause: > > 1) clang 3.8 code generation issuse > 2) system library issuse > > may be i am miss something? > > How to find real cause? I find real cause and this like show-stopper for RELEASE. I am use nginx with AIO and AIO from one nginx process corrupt memory from other nginx process. Yes, this is cross-process memory corruption. Last case, core dumped proccess with pid 1060 at 15:45:14. Corruped memory at 0x860697000. I am know about good memory at 0x86067f800. Dumping (form core) this region to file and analyze by hexdump I am found start of corrupt region -- offset 0000c8c0 from 0x86067f800. 0x86067f800+0xc8c0 = 0x86068c0c0 I am preliminary enabled debuggin of AIO started operation to nginx error log (memory address, file name, offset and size of transfer). grep -i 86068c0c0 error.log near 15:45:14 give target file. grep ce949665cbcd.hls error.log near 15:45:14 give next result: 2016/09/15 15:45:13 [notice] 1055#0: *11659936 AIO_RD 000000082065DB60 start 000000086068C0C0 561b0 2646736 ce949665cbcd.hls 2016/09/15 15:45:14 [notice] 1060#0: *10998125 AIO_RD 000000081F1FFB60 start 000000086FF2C0C0 6cdf0 140016832 ce949665cbcd.hls 2016/09/15 15:45:14 [notice] 1055#0: *11659936 AIO_RD 00000008216B6B60 start 000000086472B7C0 7ff70 2999424 ce949665cbcd.hls 0x860697000-0x86068c0c0 = 0xaf40 from memory dump: 0000af00 5c 81 4d 7c 0b b6 81 f2 c8 a5 df 94 08 43 c1 08 |\.M|.........C..| 0000af10 74 00 57 55 5f 15 11 b1 00 d5 29 6a 4e d2 fd fb |t.WU_.....)jN...| 0000af20 49 d1 fd 98 49 58 b7 66 c2 c9 64 67 30 05 06 c0 |I...IX.f..dg0...| 0000af30 0e b2 64 fa b7 9f 69 69 fc cd 91 82 83 ba c3 f2 |..d...ii........| 0000af40 b7 34 eb 8e 0e 88 40 60 1b a8 71 7a 12 15 26 d3 |.4....@`..qz..&.| 0000af50 7f 3e 80 e9 74 96 30 24 cb 82 88 8a ea e0 45 10 |.>..t.0$......E.| 0000af60 e5 75 b2 f7 5b 7c 83 fa 95 a9 09 80 0a 8c fd a9 |.u..[|..........| 0000af70 ef 30 f6 68 9c b2 3f ae 2e e5 21 79 78 8b 34 36 |.0.h..?...!yx.46| 0000af80 c6 55 16 a2 47 00 ca 13 9c 8e 2c 6b eb c7 4f 51 |.U..G.....,k..OQ| 0000af90 81 80 71 f3 a5 9a 5f 40 54 9c f1 f9 ba 81 b2 82 |..q..._@T.......| from disk file (offset from 2646736): 0000af00 5c 81 4d 7c 0b b6 81 f2 c8 a5 df 94 08 43 c1 08 |\.M|.........C..| 0000af10 74 00 57 55 5f 15 11 b1 00 d5 29 6a 4e d2 fd fb |t.WU_.....)jN...| 0000af20 49 d1 fd 98 49 58 b7 66 c2 c9 64 67 30 05 06 c0 |I...IX.f..dg0...| 0000af30 0e b2 64 fa b7 9f 69 69 fc cd 91 82 83 ba c3 f2 |..d...ii........| 0000af40 b7 34 eb 8e 0e 88 40 60 1b a8 71 7a 12 15 26 d3 |.4....@`..qz..&.| 0000af50 7f 3e 80 e9 74 96 30 24 cb 82 88 8a ea e0 45 10 |.>..t.0$......E.| 0000af60 e5 75 b2 f7 5b 7c 83 fa 95 a9 09 80 0a 8c fd a9 |.u..[|..........| 0000af70 ef 30 f6 68 9c b2 3f ae 2e e5 21 79 78 8b 34 36 |.0.h..?...!yx.46| 0000af80 c6 55 16 a2 47 00 ca 13 9c 8e 2c 6b eb c7 4f 51 |.U..G.....,k..OQ| 0000af90 81 80 71 f3 a5 9a 5f 40 54 9c f1 f9 ba 81 b2 82 |..q..._@T.......| Bingo! aio read file by process 1055 placed to same memory address as requested but in memory space of process 1060! This is kernel bug and this bug must be stoped release. From owner-freebsd-stable@freebsd.org Thu Sep 15 16:52:32 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48653BDA2C2 for ; Thu, 15 Sep 2016 16:52:32 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 156D73B9; Thu, 15 Sep 2016 16:52:31 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: by mail-it0-x229.google.com with SMTP id 186so84506760itf.0; Thu, 15 Sep 2016 09:52: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; bh=wCXL8aLDY4LgPd9YoHVTS7BTog1SkbNBGUjNWGvmOoU=; b=UbjIlnJt6JCmBKUC1Mjrip4p39kT/kZqXfcKDilKwZB+qd8J7e5S11wReTTl+r6XqA 2/g72tpaNv3dNfrpRBIWaQyqDD/tQ7jdHRn6MDGqXKYS7LgtdG2ny1f3Y6Tt6+Av7niH UW7/GettBXTKkhqdRDb35mCvE8GVIbYr3CVTyk5izXDKOYGgAxkQhH1A+d/WFtUlr29P WoRQBg3DJv2duDmIFvZ38v/g6zfXO+bwzLZmd8rIN5BP5X2rAKezoUQ2Q4otDK9UAUgE wPh74PUZPAmiM8PpI+CHM2jVnSAywJDpX1d28pUBRJK2E+sJN2H2D/Y/Caww4hJLmaEj /BYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wCXL8aLDY4LgPd9YoHVTS7BTog1SkbNBGUjNWGvmOoU=; b=RepUiKLPFUvMBZtoaGRWaSm+I54zMcKwLfXSr1gE3y1OE5K1yih6EHGDLS8IrfmV6L C/eBdC2ovaGQBltjuRoubnOVl6lxD3PxluCWjmY9t+uQehF6iXqMN/7VwKOEssN8o710 1QV5AeQxKl/vJ6IeJEQHlwnsl7SY0ZyJLrobY8ao0IljJeQtnG1xU2YT59a6FZjnp6IO aMxluZ+Y7wo1Tx8JFUNb42Ev6YYD+HulgtE2vq2HT5EJzfLsA0T/fDgi/vO40Rs28pBn insLv4jVApcZs+rNLglNlUzNUNHWjifm7FwwVRsw/IugdGpCIiBKXVqripHUGmmP/Bwj QGjA== X-Gm-Message-State: AE9vXwPEDjnMup3s7CAupORWnDbiPbhau5ADus+3ii6loJ3Np+GUoV4g5Bk5ewSzTJLxaUGjL8f6wiif9kyz/Q== X-Received: by 10.36.117.79 with SMTP id y76mr598200itc.35.1473958350919; Thu, 15 Sep 2016 09:52:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.164.82 with HTTP; Thu, 15 Sep 2016 09:52:30 -0700 (PDT) In-Reply-To: <20160915144103.GB2960@zxy.spb.ru> References: <20160907191348.GD22212@zxy.spb.ru> <20160915144103.GB2960@zxy.spb.ru> From: jungle Boogie Date: Thu, 15 Sep 2016 09:52:30 -0700 Message-ID: Subject: Re: nginx and FreeBSD11 To: Slawa Olhovchenkov Cc: freebsd-stable , John Baldwin Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 16:52:32 -0000 On 15 September 2016 at 07:41, Slawa Olhovchenkov wrote: > Bingo! > aio read file by process 1055 placed to same memory address as requested but in memory space of process 1060! > > This is kernel bug and this bug must be stoped release. When was it introduced? -- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info From owner-freebsd-stable@freebsd.org Thu Sep 15 16:55:22 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 543EEBDA3DE for ; Thu, 15 Sep 2016 16:55:22 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1A4B3781; Thu, 15 Sep 2016 16:55:22 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkZwU-000FEP-Kx; Thu, 15 Sep 2016 19:55:18 +0300 Date: Thu, 15 Sep 2016 19:55:18 +0300 From: Slawa Olhovchenkov To: jungle Boogie Cc: freebsd-stable , John Baldwin Subject: Re: nginx and FreeBSD11 Message-ID: <20160915165518.GV2840@zxy.spb.ru> References: <20160907191348.GD22212@zxy.spb.ru> <20160915144103.GB2960@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 16:55:22 -0000 On Thu, Sep 15, 2016 at 09:52:30AM -0700, jungle Boogie wrote: > On 15 September 2016 at 07:41, Slawa Olhovchenkov wrote: > > Bingo! > > aio read file by process 1055 placed to same memory address as requested but in memory space of process 1060! > > > > This is kernel bug and this bug must be stoped release. > > When was it introduced? I am try 11.x as r305117 and don't try other releases. Don't see in 10.x line. aio in 11.x was refactored. From owner-freebsd-stable@freebsd.org Thu Sep 15 17:34:17 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2F5ABDB4E2 for ; Thu, 15 Sep 2016 17:34:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 93C84CEA for ; Thu, 15 Sep 2016 17:34:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id 202CB10AF7D; Thu, 15 Sep 2016 13:34:16 -0400 (EDT) From: John Baldwin To: Slawa Olhovchenkov Cc: freebsd-stable@freebsd.org Subject: Re: nginx and FreeBSD11 Date: Thu, 15 Sep 2016 10:28:11 -0700 Message-ID: <1823460.vTm8IvUQsF@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-PRERELEASE; KDE/4.14.10; amd64; ; ) In-Reply-To: <20160915144103.GB2960@zxy.spb.ru> References: <20160907191348.GD22212@zxy.spb.ru> <20160915144103.GB2960@zxy.spb.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Thu, 15 Sep 2016 13:34:16 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 17:34:17 -0000 On Thursday, September 15, 2016 05:41:03 PM Slawa Olhovchenkov wrote: > On Wed, Sep 07, 2016 at 10:13:48PM +0300, Slawa Olhovchenkov wrote: > > > I am have strange issuse with nginx on FreeBSD11. > > I am have FreeBSD11 instaled over STABLE-10. > > nginx build for FreeBSD10 and run w/o recompile work fine. > > nginx build for FreeBSD11 crushed inside rbtree lookups: next node > > totaly craped. > > > > I am see next potential cause: > > > > 1) clang 3.8 code generation issuse > > 2) system library issuse > > > > may be i am miss something? > > > > How to find real cause? > > I find real cause and this like show-stopper for RELEASE. > I am use nginx with AIO and AIO from one nginx process corrupt memory > from other nginx process. Yes, this is cross-process memory > corruption. > > Last case, core dumped proccess with pid 1060 at 15:45:14. > Corruped memory at 0x860697000. > I am know about good memory at 0x86067f800. > Dumping (form core) this region to file and analyze by hexdump I am > found start of corrupt region -- offset 0000c8c0 from 0x86067f800. > 0x86067f800+0xc8c0 = 0x86068c0c0 > > I am preliminary enabled debuggin of AIO started operation to nginx > error log (memory address, file name, offset and size of transfer). > > grep -i 86068c0c0 error.log near 15:45:14 give target file. > grep ce949665cbcd.hls error.log near 15:45:14 give next result: > > 2016/09/15 15:45:13 [notice] 1055#0: *11659936 AIO_RD 000000082065DB60 start 000000086068C0C0 561b0 2646736 ce949665cbcd.hls > 2016/09/15 15:45:14 [notice] 1060#0: *10998125 AIO_RD 000000081F1FFB60 start 000000086FF2C0C0 6cdf0 140016832 ce949665cbcd.hls > 2016/09/15 15:45:14 [notice] 1055#0: *11659936 AIO_RD 00000008216B6B60 start 000000086472B7C0 7ff70 2999424 ce949665cbcd.hls Does nginx only use AIO for regular files or does it also use it with sockets? You can try using this patch as a diagnostic (you will need to run with INVARIANTS enabled, or at least enabled for vfs_aio.c): Index: vfs_aio.c =================================================================== --- vfs_aio.c (revision 305811) +++ vfs_aio.c (working copy) @@ -787,6 +787,8 @@ aio_process_rw(struct kaiocb *job) * aio_aqueue() acquires a reference to the file that is * released in aio_free_entry(). */ + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, + ("%s: vmspace mismatch", __func__)); if (cb->aio_lio_opcode == LIO_READ) { auio.uio_rw = UIO_READ; if (auio.uio_resid == 0) @@ -1054,6 +1056,8 @@ aio_switch_vmspace(struct kaiocb *job) { vmspace_switch_aio(job->userproc->p_vmspace); + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, + ("%s: vmspace mismatch", __func__)); } If this panics, then vmspace_switch_aio() is not working for some reason. -- John Baldwin From owner-freebsd-stable@freebsd.org Thu Sep 15 17:49:51 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C771BDB985 for ; Thu, 15 Sep 2016 17:49:51 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 33FB5BFC; Thu, 15 Sep 2016 17:49:51 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkanE-000GOM-Bm; Thu, 15 Sep 2016 20:49:48 +0300 Date: Thu, 15 Sep 2016 20:49:48 +0300 From: Slawa Olhovchenkov To: John Baldwin Cc: freebsd-stable@freebsd.org Subject: Re: nginx and FreeBSD11 Message-ID: <20160915174948.GW2840@zxy.spb.ru> References: <20160907191348.GD22212@zxy.spb.ru> <20160915144103.GB2960@zxy.spb.ru> <1823460.vTm8IvUQsF@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1823460.vTm8IvUQsF@ralph.baldwin.cx> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 17:49:51 -0000 On Thu, Sep 15, 2016 at 10:28:11AM -0700, John Baldwin wrote: > On Thursday, September 15, 2016 05:41:03 PM Slawa Olhovchenkov wrote: > > On Wed, Sep 07, 2016 at 10:13:48PM +0300, Slawa Olhovchenkov wrote: > > > > > I am have strange issuse with nginx on FreeBSD11. > > > I am have FreeBSD11 instaled over STABLE-10. > > > nginx build for FreeBSD10 and run w/o recompile work fine. > > > nginx build for FreeBSD11 crushed inside rbtree lookups: next node > > > totaly craped. > > > > > > I am see next potential cause: > > > > > > 1) clang 3.8 code generation issuse > > > 2) system library issuse > > > > > > may be i am miss something? > > > > > > How to find real cause? > > > > I find real cause and this like show-stopper for RELEASE. > > I am use nginx with AIO and AIO from one nginx process corrupt memory > > from other nginx process. Yes, this is cross-process memory > > corruption. > > > > Last case, core dumped proccess with pid 1060 at 15:45:14. > > Corruped memory at 0x860697000. > > I am know about good memory at 0x86067f800. > > Dumping (form core) this region to file and analyze by hexdump I am > > found start of corrupt region -- offset 0000c8c0 from 0x86067f800. > > 0x86067f800+0xc8c0 = 0x86068c0c0 > > > > I am preliminary enabled debuggin of AIO started operation to nginx > > error log (memory address, file name, offset and size of transfer). > > > > grep -i 86068c0c0 error.log near 15:45:14 give target file. > > grep ce949665cbcd.hls error.log near 15:45:14 give next result: > > > > 2016/09/15 15:45:13 [notice] 1055#0: *11659936 AIO_RD 000000082065DB60 start 000000086068C0C0 561b0 2646736 ce949665cbcd.hls > > 2016/09/15 15:45:14 [notice] 1060#0: *10998125 AIO_RD 000000081F1FFB60 start 000000086FF2C0C0 6cdf0 140016832 ce949665cbcd.hls > > 2016/09/15 15:45:14 [notice] 1055#0: *11659936 AIO_RD 00000008216B6B60 start 000000086472B7C0 7ff70 2999424 ce949665cbcd.hls > > Does nginx only use AIO for regular files or does it also use it with sockets? Only for regular files. > You can try using this patch as a diagnostic (you will need to > run with INVARIANTS enabled, How much debugs produced? I am have about 5-10K aio's per second. > or at least enabled for vfs_aio.c): How I can do this (enable INVARIANTS for vfs_aio.c)? > Index: vfs_aio.c > =================================================================== > --- vfs_aio.c (revision 305811) > +++ vfs_aio.c (working copy) > @@ -787,6 +787,8 @@ aio_process_rw(struct kaiocb *job) > * aio_aqueue() acquires a reference to the file that is > * released in aio_free_entry(). > */ > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, > + ("%s: vmspace mismatch", __func__)); > if (cb->aio_lio_opcode == LIO_READ) { > auio.uio_rw = UIO_READ; > if (auio.uio_resid == 0) > @@ -1054,6 +1056,8 @@ aio_switch_vmspace(struct kaiocb *job) > { > > vmspace_switch_aio(job->userproc->p_vmspace); > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, > + ("%s: vmspace mismatch", __func__)); > } > > If this panics, then vmspace_switch_aio() is not working for > some reason. This issuse caused rare, this panic produced with issuse or on any aio request? (this is production server) From owner-freebsd-stable@freebsd.org Thu Sep 15 18:10:50 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9243BDBFFD; Thu, 15 Sep 2016 18:10:50 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 9E1C3A08; Thu, 15 Sep 2016 18:10:50 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id D43C61FE; Thu, 15 Sep 2016 18:10:49 +0000 (UTC) Date: Thu, 15 Sep 2016 18:10:41 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: emaste@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <297891549.23.1473963049906.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_11-i386 - Build #143 - Failure MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_11-i386 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2016 18:10:51 -0000 FreeBSD_STABLE_11-i386 - Build #143 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-i386/1= 43/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-i386/143= /changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-i386/143/= console Change summaries: 305837 by emaste: MFC r303674: readelf: report ARM program and section header types The end of the build log: [...truncated 140550 lines...] cc -O2 -pipe -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include = -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/include -I/us= r/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/include -I/usr= /src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/include -I/= usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/sntp/libopts -I/usr/src/u= sr.sbin/ntp/libntp/../../../lib/libc/i386 -I/usr/src/usr.sbin/ntp/libntp/.= ./../../lib/libedit/edit -I/usr/src/usr.sbin/ntp/libntp/../ -I/usr/src/us= r.sbin/ntp/libntp/ -DHAVE_BSD_NICE -DHAVE_STDINT_H -DSYS_FREEBSD -DPARSE = -DHAVE_CONFIG_H -DOPENSSL -DUSE_OPENSSL_CRYPTO_RAND -DAUTOKEY -MD -MF.dep= end.result.o -MTresult.o -std=3Dgnu99 -fstack-protector-strong -Wno-pointer= -sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-= tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unuse= d-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -Wno-= switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-argument= s -c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/result.c -o= result.o --- all_subdir_usr.bin --- --- all_subdir_usr.bin/lex --- =3D=3D=3D> usr.bin/lex (all) --- all_subdir_usr.sbin --- --- all_subdir_usr.sbin/pmcstat --- --- pmcpl_gprof.o --- --- all_subdir_usr.sbin/ntp --- --- task.o --- --- all_subdir_usr.sbin/pmcstat --- cc -O2 -pipe -g -MD -MF.depend.pmcpl_gprof.o -MTpmcpl_gprof.o -std=3Dgn= u99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k= -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointe= r-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunuse= d-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredu= ndant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-dec= larations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-= const-variable -Qunused-arguments -c /usr/src/usr.sbin/pmcstat/pmcpl_gpro= f.c -o pmcpl_gprof.o --- all_subdir_usr.sbin/ntp --- cc -O2 -pipe -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include = -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/include -I/us= r/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/include -I/usr= /src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/include -I/= usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/sntp/libopts -I/usr/src/u= sr.sbin/ntp/libntp/../../../lib/libc/i386 -I/usr/src/usr.sbin/ntp/libntp/.= ./../../lib/libedit/edit -I/usr/src/usr.sbin/ntp/libntp/../ -I/usr/src/us= r.sbin/ntp/libntp/ -DHAVE_BSD_NICE -DHAVE_STDINT_H -DSYS_FREEBSD -DPARSE = -DHAVE_CONFIG_H -DOPENSSL -DUSE_OPENSSL_CRYPTO_RAND -DAUTOKEY -MD -MF.dep= end.task.o -MTtask.o -std=3Dgnu99 -fstack-protector-strong -Wno-pointer-sig= n -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-taut= ological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-fu= nction -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -Wno-swit= ch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -= c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/task.c -o task.= o --- all_subdir_usr.bin --- --- parse.c --- yacc -d -o parse.c /usr/src/usr.bin/lex/../../contrib/flex/parse.y --- scan.c --- lex -t -is /usr/src/usr.bin/lex/../../contrib/flex/scan.l > scan.c --- skel.c --- sed 's/m4_/m4postproc_/g; s/m4preproc_/m4_/g' /usr/src/usr.bin/lex/../../c= ontrib/flex/flex.skl | m4 -I/usr/src/usr.bin/lex/../../contrib/flex -P `aw= k -f /usr/src/usr.bin/lex/version.awk /usr/src/usr.bin/lex/config.h` | sed= 's/m4postproc_/m4_/g' | sh /usr/src/usr.bin/lex/../../contrib/flex/mkskel= .sh > skel.c --- all_subdir_usr.bin/indent --- --- lexi.o --- cc -O2 -pipe -g -MD -MF.depend.lexi.o -MTlexi.o -std=3Dgnu99 -fstack-pr= otector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unuse= d-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wretu= rn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -W= cast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -W= old-style-definition -Wno-pointer-sign -Wthread-safety -Wno-empty-body -Wno= -string-plus-int -Wno-unused-const-variable -Qunused-arguments -c /usr/sr= c/usr.bin/indent/lexi.c -o lexi.o --- all_subdir_usr.bin/lex --- --- .depend --- echo lex.full: /usr/obj/usr/src/tmp/usr/lib/libc.a >> .depend --- buf.o --- cc -O2 -pipe -I. -I/usr/src/usr.bin/lex -I/usr/src/usr.bin/lex/../../contr= ib/flex -DHAVE_CONFIG_H -g -MD -MF.depend.buf.o -MTbuf.o -std=3Dgnu99 -f= stack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -W= no-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arit= h -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int= -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wn= o-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unuse= d-local-typedef -Qunused-arguments -c /usr/src/usr.bin/lex/../../contrib/= flex/buf.c -o buf.o --- all_subdir_usr.sbin --- --- all_subdir_usr.sbin/pmcstat --- --- pmcpl_annotate.o --- cc -O2 -pipe -g -MD -MF.depend.pmcpl_annotate.o -MTpmcpl_annotate.o -st= d=3Dgnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-form= at-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -W= pointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -= Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs = -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-variab= le-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-u= nused-const-variable -Qunused-arguments -c /usr/src/usr.sbin/pmcstat/pmcp= l_annotate.c -o pmcpl_annotate.o --- all_subdir_usr.bin --- --- ccl.o --- cc -O2 -pipe -I. -I/usr/src/usr.bin/lex -I/usr/src/usr.bin/lex/../../contr= ib/flex -DHAVE_CONFIG_H -g -MD -MF.depend.ccl.o -MTccl.o -std=3Dgnu99 -f= stack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -W= no-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arit= h -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int= -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wn= o-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unuse= d-local-typedef -Qunused-arguments -c /usr/src/usr.bin/lex/../../contrib/= flex/ccl.c -o ccl.o --- all_subdir_usr.sbin --- --- pmcpl_annotate_cg.o --- cc -O2 -pipe -g -MD -MF.depend.pmcpl_annotate_cg.o -MTpmcpl_annotate_cg= .o -std=3Dgnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wn= o-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototy= pes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wsh= adow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-ex= terns -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-= variable-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int = -Wno-unused-const-variable -Qunused-arguments -c /usr/src/usr.sbin/pmcsta= t/pmcpl_annotate_cg.c -o pmcpl_annotate_cg.o --- all_subdir_usr.bin --- --- all_subdir_usr.bin/indent --- --- parse.o --- cc -O2 -pipe -g -MD -MF.depend.parse.o -MTparse.o -std=3Dgnu99 -fstack-= protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unu= sed-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wre= turn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter = -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls = -Wold-style-definition -Wno-pointer-sign -Wthread-safety -Wno-empty-body -W= no-string-plus-int -Wno-unused-const-variable -Qunused-arguments -c /usr/= src/usr.bin/indent/parse.c -o parse.o --- all_subdir_usr.sbin --- --- all_subdir_usr.sbin/ntp --- --- sha1.o --- cc -O2 -pipe -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include = -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/include -I/us= r/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/include -I/usr= /src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/include -I/= usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/sntp/libopts -I/usr/src/u= sr.sbin/ntp/libntp/../../../lib/libc/i386 -I/usr/src/usr.sbin/ntp/libntp/.= ./../../lib/libedit/edit -I/usr/src/usr.sbin/ntp/libntp/../ -I/usr/src/us= r.sbin/ntp/libntp/ -DHAVE_BSD_NICE -DHAVE_STDINT_H -DSYS_FREEBSD -DPARSE = -DHAVE_CONFIG_H -DOPENSSL -DUSE_OPENSSL_CRYPTO_RAND -DAUTOKEY -MD -MF.dep= end.sha1.o -MTsha1.o -std=3Dgnu99 -fstack-protector-strong -Wno-pointer-sig= n -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-taut= ological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-fu= nction -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -Wno-swit= ch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -= c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/sha1.c -o sha1.= o --- all_subdir_usr.bin --- --- pr_comment.o --- cc -O2 -pipe -g -MD -MF.depend.pr_comment.o -MTpr_comment.o -std=3Dgnu9= 9 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -= W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-= arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-= parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredund= ant-decls -Wold-style-definition -Wno-pointer-sign -Wthread-safety -Wno-emp= ty-body -Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments= -c /usr/src/usr.bin/indent/pr_comment.c -o pr_comment.o --- all_subdir_usr.bin/lex --- --- dfa.o --- cc -O2 -pipe -I. -I/usr/src/usr.bin/lex -I/usr/src/usr.bin/lex/../../contr= ib/flex -DHAVE_CONFIG_H -g -MD -MF.depend.dfa.o -MTdfa.o -std=3Dgnu99 -f= stack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -W= no-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arit= h -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int= -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wn= o-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unuse= d-local-typedef -Qunused-arguments -c /usr/src/usr.bin/lex/../../contrib/= flex/dfa.c -o dfa.o --- all_subdir_usr.sbin --- --- all_subdir_usr.sbin/pmcstat --- --- pmcpl_calltree.o --- cc -O2 -pipe -g -MD -MF.depend.pmcpl_calltree.o -MTpmcpl_calltree.o -st= d=3Dgnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-form= at-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -W= pointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -= Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs = -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-variab= le-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-u= nused-const-variable -Qunused-arguments -c /usr/src/usr.sbin/pmcstat/pmcp= l_calltree.c -o pmcpl_calltree.o --- all_subdir_usr.bin --- --- all_subdir_usr.bin/indent --- --- args.o --- cc -O2 -pipe -g -MD -MF.depend.args.o -MTargs.o -std=3Dgnu99 -fstack-pr= otector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unuse= d-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wretu= rn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -W= cast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -W= old-style-definition -Wno-pointer-sign -Wthread-safety -Wno-empty-body -Wno= -string-plus-int -Wno-unused-const-variable -Qunused-arguments -c /usr/sr= c/usr.bin/indent/args.c -o args.o --- indent.full --- cc -O2 -pipe -g -std=3Dgnu99 -fstack-protector-strong -Wsystem-headers -Wer= ror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmi= ssing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings = -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winlin= e -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-si= gn -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-v= ariable -Qunused-arguments -o indent.full indent.o io.o lexi.o parse.o pr_= comment.o args.o =20 --- indent.1.gz --- gzip -cn /usr/src/usr.bin/indent/indent.1 > indent.1.gz --- indent.debug --- objcopy --only-keep-debug indent.full indent.debug --- indent --- objcopy --strip-debug --add-gnu-debuglink=3Dindent.debug indent.full inden= t --- all_subdir_usr.sbin --- --- all_subdir_usr.sbin/ntp --- --- sockaddr.o --- cc -O2 -pipe -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include = -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/include -I/us= r/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/include -I/usr= /src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/include -I/= usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/sntp/libopts -I/usr/src/u= sr.sbin/ntp/libntp/../../../lib/libc/i386 -I/usr/src/usr.sbin/ntp/libntp/.= ./../../lib/libedit/edit -I/usr/src/usr.sbin/ntp/libntp/../ -I/usr/src/us= r.sbin/ntp/libntp/ -DHAVE_BSD_NICE -DHAVE_STDINT_H -DSYS_FREEBSD -DPARSE = -DHAVE_CONFIG_H -DOPENSSL -DUSE_OPENSSL_CRYPTO_RAND -DAUTOKEY -MD -MF.dep= end.sockaddr.o -MTsockaddr.o -std=3Dgnu99 -fstack-protector-strong -Wno-poi= nter-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -= Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-u= nused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -= Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-argu= ments -c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/sockadd= r.c -o sockaddr.o --- all_subdir_usr.bin --- --- all_subdir_usr.bin/lex --- --- ecs.o --- cc -O2 -pipe -I. -I/usr/src/usr.bin/lex -I/usr/src/usr.bin/lex/../../contr= ib/flex -DHAVE_CONFIG_H -g -MD -MF.depend.ecs.o -MTecs.o -std=3Dgnu99 -f= stack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -W= no-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arit= h -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int= -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wn= o-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unuse= d-local-typedef -Qunused-arguments -c /usr/src/usr.bin/lex/../../contrib/= flex/ecs.c -o ecs.o --- all_subdir_usr.bin/mkstr --- =3D=3D=3D> usr.bin/mkstr (all) --- .depend --- echo mkstr.full: /usr/obj/usr/src/tmp/usr/lib/libc.a >> .depend --- mkstr.o --- cc -O2 -pipe -g -MD -MF.depend.mkstr.o -MTmkstr.o -std=3Dgnu99 -fstack-= protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninit= ialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-= const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses= -equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typed= ef -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Qunused-argum= ents -c /usr/src/usr.bin/mkstr/mkstr.c -o mkstr.o --- all_subdir_usr.bin/lex --- --- filter.o --- cc -O2 -pipe -I. -I/usr/src/usr.bin/lex -I/usr/src/usr.bin/lex/../../contr= ib/flex -DHAVE_CONFIG_H -g -MD -MF.depend.filter.o -MTfilter.o -std=3Dgn= u99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k= -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointe= r-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-pl= us-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-val= ue -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno= -unused-local-typedef -Qunused-arguments -c /usr/src/usr.bin/lex/../../co= ntrib/flex/filter.c -o filter.o --- all_subdir_usr.sbin --- --- msgcat.o --- cc -O2 -pipe -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include = -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/include -I/us= r/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/include -I/usr= /src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/include -I/= usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/sntp/libopts -I/usr/src/u= sr.sbin/ntp/libntp/../../../lib/libc/i386 -I/usr/src/usr.sbin/ntp/libntp/.= ./../../lib/libedit/edit -I/usr/src/usr.sbin/ntp/libntp/../ -I/usr/src/us= r.sbin/ntp/libntp/ -DHAVE_BSD_NICE -DHAVE_STDINT_H -DSYS_FREEBSD -DPARSE = -DHAVE_CONFIG_H -DOPENSSL -DUSE_OPENSSL_CRYPTO_RAND -DAUTOKEY -MD -MF.dep= end.msgcat.o -MTmsgcat.o -std=3Dgnu99 -fstack-protector-strong -Wno-pointer= -sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-= tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unuse= d-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -Wno-= switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-argument= s -c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/nls/msgcat.= c -o msgcat.o --- condition.o --- cc -O2 -pipe -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include = -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/include -I/us= r/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/include -I/usr= /src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/include -I/= usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/sntp/libopts -I/usr/src/u= sr.sbin/ntp/libntp/../../../lib/libc/i386 -I/usr/src/usr.sbin/ntp/libntp/.= ./../../lib/libedit/edit -I/usr/src/usr.sbin/ntp/libntp/../ -I/usr/src/us= r.sbin/ntp/libntp/ -DHAVE_BSD_NICE -DHAVE_STDINT_H -DSYS_FREEBSD -DPARSE = -DHAVE_CONFIG_H -DOPENSSL -DUSE_OPENSSL_CRYPTO_RAND -DAUTOKEY -MD -MF.dep= end.condition.o -MTcondition.o -std=3Dgnu99 -fstack-protector-strong -Wno-p= ointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable= -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno= -unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch= -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-ar= guments -c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthre= ads/condition.c -o condition.o --- all_subdir_usr.bin --- --- all_subdir_usr.bin/mkstr --- --- mkstr.full --- cc -O2 -pipe -g -std=3Dgnu99 -fstack-protector-strong -Wsystem-headers -Wer= ror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wno-empty-b= ody -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compa= re -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-en= um-conversion -Wno-unused-local-typedef -Wno-switch -Wno-switch-enum -Wno-k= nr-promoted-parameter -Qunused-arguments -o mkstr.full mkstr.o =20 --- all_subdir_usr.sbin --- --- all_subdir_usr.sbin/pmcstat --- --- pmcstat.8.gz --- gzip -cn /usr/src/usr.sbin/pmcstat/pmcstat.8 > pmcstat.8.gz --- all_subdir_usr.bin --- --- mkstr.1.gz --- gzip -cn /usr/src/usr.bin/mkstr/mkstr.1 > mkstr.1.gz --- mkstr.debug --- objcopy --only-keep-debug mkstr.full mkstr.debug --- mkstr --- objcopy --strip-debug --add-gnu-debuglink=3Dmkstr.debug mkstr.full mkstr --- all_subdir_usr.sbin --- --- pmcstat.full --- cc -O2 -pipe -g -std=3Dgnu99 -fstack-protector-strong -Wsystem-headers -Wer= ror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmi= ssing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings = -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winlin= e -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-si= gn -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-str= ing-plus-int -Wno-unused-const-variable -Qunused-arguments -o pmcstat.full= pmcstat.o pmcstat_log.o pmcpl_callgraph.o pmcpl_gprof.o pmcpl_annotate.o p= mcpl_annotate_cg.o pmcpl_calltree.o -lelf -lkvm -lpmc -lm -lncursesw --- all_subdir_usr.sbin/ntp --- --- thread.o --- cc -O2 -pipe -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include = -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/include -I/us= r/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/include -I/usr= /src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/include -I/= usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/sntp/libopts -I/usr/src/u= sr.sbin/ntp/libntp/../../../lib/libc/i386 -I/usr/src/usr.sbin/ntp/libntp/.= ./../../lib/libedit/edit -I/usr/src/usr.sbin/ntp/libntp/../ -I/usr/src/us= r.sbin/ntp/libntp/ -DHAVE_BSD_NICE -DHAVE_STDINT_H -DSYS_FREEBSD -DPARSE = -DHAVE_CONFIG_H -DOPENSSL -DUSE_OPENSSL_CRYPTO_RAND -DAUTOKEY -MD -MF.dep= end.thread.o -MTthread.o -std=3Dgnu99 -fstack-protector-strong -Wno-pointer= -sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-= tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unuse= d-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -Wno-= switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-argument= s -c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/th= read.c -o thread.o --- all_subdir_usr.bin --- --- all_subdir_usr.bin/lex --- --- gen.o --- cc -O2 -pipe -I. -I/usr/src/usr.bin/lex -I/usr/src/usr.bin/lex/../../contr= ib/flex -DHAVE_CONFIG_H -g -MD -MF.depend.gen.o -MTgen.o -std=3Dgnu99 -f= stack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -W= no-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arit= h -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int= -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wn= o-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unuse= d-local-typedef -Qunused-arguments -c /usr/src/usr.bin/lex/../../contrib/= flex/gen.c -o gen.o --- all_subdir_usr.bin/nm --- =3D=3D=3D> usr.bin/nm (all) --- all_subdir_usr.sbin --- --- all_subdir_usr.sbin/pmcstat --- --- pmcstat.debug --- objcopy --only-keep-debug pmcstat.full pmcstat.debug --- pmcstat --- objcopy --strip-debug --add-gnu-debuglink=3Dpmcstat.debug pmcstat.full pmc= stat --- all_subdir_usr.bin --- --- all_subdir_usr.bin/readelf --- =3D=3D=3D> usr.bin/readelf (all) --- all_subdir_usr.sbin --- --- all_subdir_usr.sbin/ntp --- --- mutex.o --- cc -O2 -pipe -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include = -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/include -I/us= r/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/include -I/usr= /src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/include -I/= usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/sntp/libopts -I/usr/src/u= sr.sbin/ntp/libntp/../../../lib/libc/i386 -I/usr/src/usr.sbin/ntp/libntp/.= ./../../lib/libedit/edit -I/usr/src/usr.sbin/ntp/libntp/../ -I/usr/src/us= r.sbin/ntp/libntp/ -DHAVE_BSD_NICE -DHAVE_STDINT_H -DSYS_FREEBSD -DPARSE = -DHAVE_CONFIG_H -DOPENSSL -DUSE_OPENSSL_CRYPTO_RAND -DAUTOKEY -MD -MF.dep= end.mutex.o -MTmutex.o -std=3Dgnu99 -fstack-protector-strong -Wno-pointer-s= ign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-ta= utological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-= function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -Wno-sw= itch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments = -c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/mute= x.c -o mutex.o --- all_subdir_usr.bin --- --- all_subdir_usr.bin/nm --- --- .depend --- echo nm.full: /usr/obj/usr/src/tmp/usr/lib/libc.a /usr/obj/usr/src/tmp/usr/= lib/libdwarf.a /usr/obj/usr/src/lib/libelftc/libelftc.a /usr/obj/usr/src/tm= p/usr/lib/libelf.a >> .depend --- nm.o --- cc -O2 -pipe -I/usr/src/contrib/elftoolchain/libelftc -I/usr/src/contrib= /elftoolchain/common -g -MD -MF.depend.nm.o -MTnm.o -std=3Dgnu99 -fstack-p= rotector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unus= ed-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wret= urn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -= Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -= Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations -Wt= hread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variabl= e -Qunused-arguments -c /usr/src/contrib/elftoolchain/nm/nm.c -o nm.o --- all_subdir_usr.bin/readelf --- --- sys/elf32.h --- mkdir -p /usr/obj/usr/src/usr.bin/readelf/sys ln -sf /usr/src/sys/sys/elf32.h sys/elf32.h --- sys/elf64.h --- mkdir -p /usr/obj/usr/src/usr.bin/readelf/sys ln -sf /usr/src/sys/sys/elf64.h sys/elf64.h --- sys/elf_common.h --- mkdir -p /usr/obj/usr/src/usr.bin/readelf/sys ln -sf /usr/src/sys/sys/elf_common.h sys/elf_common.h --- .depend --- echo readelf.full: /usr/obj/usr/src/tmp/usr/lib/libc.a /usr/obj/usr/src/tmp= /usr/lib/libdwarf.a /usr/obj/usr/src/lib/libelftc/libelftc.a /usr/obj/usr/s= rc/tmp/usr/lib/libelf.a >> .depend --- readelf.o --- cc -O2 -pipe -I/usr/src/contrib/elftoolchain/libelftc -I/usr/src/contrib/e= lftoolchain/common -I. -g -MD -MF.depend.readelf.o -MTreadelf.o -std=3Dg= nu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2= k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpoint= er-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunus= ed-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wred= undant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-de= clarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused= -const-variable -Qunused-arguments -c /usr/src/contrib/elftoolchain/reade= lf/readelf.c -o readelf.o --- all_subdir_usr.sbin --- --- dir.o --- cc -O2 -pipe -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include = -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/include -I/us= r/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/include -I/usr= /src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/include -I/= usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/sntp/libopts -I/usr/src/u= sr.sbin/ntp/libntp/../../../lib/libc/i386 -I/usr/src/usr.sbin/ntp/libntp/.= ./../../lib/libedit/edit -I/usr/src/usr.sbin/ntp/libntp/../ -I/usr/src/us= r.sbin/ntp/libntp/ -DHAVE_BSD_NICE -DHAVE_STDINT_H -DSYS_FREEBSD -DPARSE = -DHAVE_CONFIG_H -DOPENSSL -DUSE_OPENSSL_CRYPTO_RAND -DAUTOKEY -MD -MF.dep= end.dir.o -MTdir.o -std=3Dgnu99 -fstack-protector-strong -Wno-pointer-sign = -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautol= ogical-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-func= tion -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -Wno-switch= -enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c = /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/dir.c -o dir= .o --- all_subdir_usr.bin --- /usr/src/contrib/elftoolchain/readelf/readelf.c:633:9: error: use of undecl= ared identifier 'PT_ARM_ARCHEXT' case PT_ARM_ARCHEXT: return "ARM_ARCHEXT"; ^ /usr/src/contrib/elftoolchain/readelf/readelf.c:634:9: error: use of undecl= ared identifier 'PT_ARM_EXIDX' case PT_ARM_EXIDX: return "ARM_EXIDX"; ^ --- all_subdir_usr.sbin --- --- errno2result.o --- cc -O2 -pipe -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include = -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/include -I/us= r/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/include -I/usr= /src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/include -I/= usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/sntp/libopts -I/usr/src/u= sr.sbin/ntp/libntp/../../../lib/libc/i386 -I/usr/src/usr.sbin/ntp/libntp/.= ./../../lib/libedit/edit -I/usr/src/usr.sbin/ntp/libntp/../ -I/usr/src/us= r.sbin/ntp/libntp/ -DHAVE_BSD_NICE -DHAVE_STDINT_H -DSYS_FREEBSD -DPARSE = -DHAVE_CONFIG_H -DOPENSSL -DUSE_OPENSSL_CRYPTO_RAND -DAUTOKEY -MD -MF.dep= end.errno2result.o -MTerrno2result.o -std=3Dgnu99 -fstack-protector-strong = -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-va= riable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equalit= y -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-= switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunu= sed-arguments -c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc= /unix/errno2result.c -o errno2result.o --- file.o --- cc -O2 -pipe -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/include = -I/usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/include -I/us= r/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/include -I/usr= /src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/pthreads/include -I/= usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/sntp/libopts -I/usr/src/u= sr.sbin/ntp/libntp/../../../lib/libc/i386 -I/usr/src/usr.sbin/ntp/libntp/.= ./../../lib/libedit/edit -I/usr/src/usr.sbin/ntp/libntp/../ -I/usr/src/us= r.sbin/ntp/libntp/ -DHAVE_BSD_NICE -DHAVE_STDINT_H -DSYS_FREEBSD -DPARSE = -DHAVE_CONFIG_H -DOPENSSL -DUSE_OPENSSL_CRYPTO_RAND -DAUTOKEY -MD -MF.dep= end.file.o -MTfile.o -std=3Dgnu99 -fstack-protector-strong -Wno-pointer-sig= n -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-taut= ological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-fu= nction -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -Wno-swit= ch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -= c /usr/src/usr.sbin/ntp/libntp/../../../contrib/ntp/lib/isc/unix/file.c -o = file.o --- all_subdir_usr.bin --- 2 errors generated. *** [readelf.o] Error code 1 bmake[4]: stopped in /usr/src/usr.bin/readelf 1 error bmake[4]: stopped in /usr/src/usr.bin/readelf *** [all_subdir_usr.bin/readelf] Error code 2 bmake[3]: stopped in /usr/src/usr.bin --- all_subdir_usr.sbin --- A failure has been detected in another branch of the parallel make bmake[5]: stopped in /usr/src/usr.sbin/ntp/libntp *** [all_subdir_usr.sbin/ntp/libntp] Error code 2 bmake[4]: stopped in /usr/src/usr.sbin/ntp 1 error bmake[4]: stopped in /usr/src/usr.sbin/ntp *** [all_subdir_usr.sbin/ntp] Error code 2 bmake[3]: stopped in /usr/src/usr.sbin 1 error bmake[3]: stopped in /usr/src/usr.sbin *** [all_subdir_usr.sbin] Error code 2 bmake[2]: stopped in /usr/src --- all_subdir_usr.bin --- --- all_subdir_usr.bin/nm --- A failure has been detected in another branch of the parallel make bmake[4]: stopped in /usr/src/usr.bin/nm *** [all_subdir_usr.bin/nm] Error code 2 bmake[3]: stopped in /usr/src/usr.bin --- all_subdir_usr.bin/lex --- A failure has been detected in another branch of the parallel make bmake[4]: stopped in /usr/src/usr.bin/lex *** [all_subdir_usr.bin/lex] Error code 2 bmake[3]: stopped in /usr/src/usr.bin 3 errors bmake[3]: stopped in /usr/src/usr.bin *** [all_subdir_usr.bin] Error code 2 bmake[2]: stopped in /usr/src 2 errors bmake[2]: stopped in /usr/src *** [everything] Error code 2 bmake[1]: stopped in /usr/src 1 error bmake[1]: stopped in /usr/src *** [buildworld] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src Build step 'Execute shell' marked build as failure [WARNINGS] Skipping publisher since build result is FAILURE [PostBuildScript] - Execution post build scripts. [FreeBSD_STABLE_11-i386] $ /bin/sh -xe /tmp/hudson4308728789212837591.sh + export 'PATH=3D/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/b= in' + export 'jname=3DFreeBSD_STABLE_11-i386' + echo 'clean up jail FreeBSD_STABLE_11-i386' clean up jail FreeBSD_STABLE_11-i386 + sudo jail -r FreeBSD_STABLE_11-i386 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::102:1 -alias + sudo umount FreeBSD_STABLE_11-i386/usr/src + sudo umount FreeBSD_STABLE_11-i386/dev + sudo rm -fr FreeBSD_STABLE_11-i386 + true + sudo chflags -R noschg FreeBSD_STABLE_11-i386 + sudo rm -fr FreeBSD_STABLE_11-i386 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-stable@freebsd.org Thu Sep 15 18:12:52 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 33427BDC2FB for ; Thu, 15 Sep 2016 18:12:52 +0000 (UTC) (envelope-from andoriyu@gmail.com) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7D07E88 for ; Thu, 15 Sep 2016 18:12:51 +0000 (UTC) (envelope-from andoriyu@gmail.com) Received: by mail-pa0-x229.google.com with SMTP id cm16so18145767pac.0 for ; Thu, 15 Sep 2016 11:12:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:subject:mime-version; bh=as3wXk9v7wcWFPCITKf4kD3IIN3R3XTutpJBUoP2hW0=; b=eFeTl0kZB6suWQUbzsQO0P57O8ysBp1meNBeNty7SIgEZCNIvqttwmWUu6nGZ36eVD h3dMkvwaByJBgmCBtW9OpsOR625SmahXF7Lhy+Fv/Qrn26O+eXkyVFiqXz7pR0++i3ux aWUnUjh4pqQY0blbxDgwMmKLs0WLpoZfTnANqOkNPL/CveaWrD4WadfsrxQVCadeqaqh /faaBa7Sdo6I/bcXGtiA2LjmAOfJX4MFgamQrpxULvCO0aPzNyeXsslPB2mwiR5bantj RloY+boUJCrkJmbbcKGenOuSVfgryXj27UfNteLY+whknKWBhuI36iDeFsXV+vizRHRs eApw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:message-id:subject:mime-version; bh=as3wXk9v7wcWFPCITKf4kD3IIN3R3XTutpJBUoP2hW0=; b=RAx3SmlMtW527HKtH9fxEjDuwOxvGxRfOYBNzsuJ+mHxr46zj84OW/5MeZ6iLfGRW8 Af+vdxt0tYFAgunOpZn7ICKLhpu6Asw/KhnVcOvXOr30wgsXG5YuD8jsJ1lt4hKDqp25 ZsVuo3t9we/emiij9krNaPyMs+e1/H5xldhNZ44OGlBDcCgxQSBvSG7TTOvUnRoDwcZ5 0rtLS3vVVVuIpXJ3qvNaE5kwqouFvLkAF9OmQZIF7b5CQe6FfIdVfrfLN7cwGaAZeKm0 IQQCdEvqI1eYulPdpz4ABa2qFKRLoDeKI1S3L7pA3UojCBeNzmgP8yaWitmhE3CiQ2w3 5hnQ== X-Gm-Message-State: AE9vXwMz0mpy4tc3wospTVPd8J2tjx3tm/o3+i9mRlm22goB41QiWKMatsg7de3vAEPBPw== X-Received: by 10.66.101.99 with SMTP id ff3mr2895909pab.170.1473963171137; Thu, 15 Sep 2016 11:12:51 -0700 (PDT) Received: from ac-book.local.mail (rrcs-74-87-203-130.west.biz.rr.com. [74.87.203.130]) by smtp.gmail.com with ESMTPSA id y184sm46690218pfg.94.2016.09.15.11.12.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Sep 2016 11:12:50 -0700 (PDT) Date: Thu, 15 Sep 2016 11:12:47 -0700 From: Andrey Cherkashin To: freebsd-stable@freebsd.org Message-ID: Subject: NVMe as boot device. X-Mailer: Airmail Beta (384) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="4D3A8B8B-3F9F-4ABB-AAD2-B56D6103B448"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 18:12:52 -0000 --4D3A8B8B-3F9F-4ABB-AAD2-B56D6103B448 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I know =46reeBSD supports NVMe as root device, but does it support it as = boot=3F Can=E2=80=99t find any confirmation. --4D3A8B8B-3F9F-4ABB-AAD2-B56D6103B448 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using AMPGpg -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJX2uSgAAoJEKSpiMgkaMpQJ9UQAJ5At8HlBDBUGEad2BAEbcV3 VU3X/NogQDM1z6vHHHL0I3h1eKF8AwJ6Gue0ySV/I44KmWR4CxdTjsftycjx7xNj HX3AwkiIWr0lPBN78Yn3ety5Fhg5xvAXhzvLC1NZfeS9YGzTHGxn/GiQmFjCRU5Y DEQGouqnPZ4eJLVp3uiFO3pDGr7zciOiT1EoCG6viFAAgQH5uK9qqYsRmLO5RvLN v4m/PEUlTH6sfifYHI88qWMa4FS0SzEMC3o9upbZEzpDbI3HMLkTbZE44rMzMbDo J0Xc8laeV9RtFEWcCW2zriebae9GFPsTzR58fFsA7SFnTKt2WHrG3txTE4MFpEZ/ DaSBf2lfY763qzzuY/sBigZs8V2FEnvvFJBjCYN4j0rjxTfCAjq8XRApdKn37nEz 3WjtBQi4mwLJW9Zmda3selOv1eelsFi8pmlHbUFBy1mqfPrRGlkYPr0Qb2sigi7z R4OFH5cbIbwxsr3kTDqxxjpJWFSg5BTph0aQvdyDrkkk4PPJ6TYkVfpRn/TrHkMN SXGPy4u0fCCC3GJzZBFHVpfEzNOey1AHTgckswKQ7TQXQXOEiq8Ak52s4TxgxrJ8 daBVbboFICqe2PL3H4QmXWy6J1G4cjiTP7OoGNoseTYP1YNoeQGKoVT/V3eVSmIh vhgd4gRaCTjmM8w84YmN -----END PGP SIGNATURE----- --4D3A8B8B-3F9F-4ABB-AAD2-B56D6103B448-- From owner-freebsd-stable@freebsd.org Thu Sep 15 18:54:43 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24899BDCAC3 for ; Thu, 15 Sep 2016 18:54:43 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D8E656E5 for ; Thu, 15 Sep 2016 18:54:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id 5B89E10AF7D; Thu, 15 Sep 2016 14:54:34 -0400 (EDT) From: John Baldwin To: Slawa Olhovchenkov Cc: freebsd-stable@freebsd.org Subject: Re: nginx and FreeBSD11 Date: Thu, 15 Sep 2016 11:54:12 -0700 Message-ID: <15357564.UUkYdbUZHc@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-PRERELEASE; KDE/4.14.10; amd64; ; ) In-Reply-To: <20160915174948.GW2840@zxy.spb.ru> References: <20160907191348.GD22212@zxy.spb.ru> <1823460.vTm8IvUQsF@ralph.baldwin.cx> <20160915174948.GW2840@zxy.spb.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Thu, 15 Sep 2016 14:54:34 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 18:54:43 -0000 On Thursday, September 15, 2016 08:49:48 PM Slawa Olhovchenkov wrote: > On Thu, Sep 15, 2016 at 10:28:11AM -0700, John Baldwin wrote: > > > On Thursday, September 15, 2016 05:41:03 PM Slawa Olhovchenkov wrote: > > > On Wed, Sep 07, 2016 at 10:13:48PM +0300, Slawa Olhovchenkov wrote: > > > > > > > I am have strange issuse with nginx on FreeBSD11. > > > > I am have FreeBSD11 instaled over STABLE-10. > > > > nginx build for FreeBSD10 and run w/o recompile work fine. > > > > nginx build for FreeBSD11 crushed inside rbtree lookups: next node > > > > totaly craped. > > > > > > > > I am see next potential cause: > > > > > > > > 1) clang 3.8 code generation issuse > > > > 2) system library issuse > > > > > > > > may be i am miss something? > > > > > > > > How to find real cause? > > > > > > I find real cause and this like show-stopper for RELEASE. > > > I am use nginx with AIO and AIO from one nginx process corrupt memory > > > from other nginx process. Yes, this is cross-process memory > > > corruption. > > > > > > Last case, core dumped proccess with pid 1060 at 15:45:14. > > > Corruped memory at 0x860697000. > > > I am know about good memory at 0x86067f800. > > > Dumping (form core) this region to file and analyze by hexdump I am > > > found start of corrupt region -- offset 0000c8c0 from 0x86067f800. > > > 0x86067f800+0xc8c0 = 0x86068c0c0 > > > > > > I am preliminary enabled debuggin of AIO started operation to nginx > > > error log (memory address, file name, offset and size of transfer). > > > > > > grep -i 86068c0c0 error.log near 15:45:14 give target file. > > > grep ce949665cbcd.hls error.log near 15:45:14 give next result: > > > > > > 2016/09/15 15:45:13 [notice] 1055#0: *11659936 AIO_RD 000000082065DB60 start 000000086068C0C0 561b0 2646736 ce949665cbcd.hls > > > 2016/09/15 15:45:14 [notice] 1060#0: *10998125 AIO_RD 000000081F1FFB60 start 000000086FF2C0C0 6cdf0 140016832 ce949665cbcd.hls > > > 2016/09/15 15:45:14 [notice] 1055#0: *11659936 AIO_RD 00000008216B6B60 start 000000086472B7C0 7ff70 2999424 ce949665cbcd.hls > > > > Does nginx only use AIO for regular files or does it also use it with sockets? > > Only for regular files. > > > You can try using this patch as a diagnostic (you will need to > > run with INVARIANTS enabled, > > How much debugs produced? > I am have about 5-10K aio's per second. > > > or at least enabled for vfs_aio.c): > > How I can do this (enable INVARIANTS for vfs_aio.c)? Include INVARIANT_SUPPORT in your kernel and add a line with: #define INVARIANTS at the top of sys/kern/vfs_aio.c. > > > Index: vfs_aio.c > > =================================================================== > > --- vfs_aio.c (revision 305811) > > +++ vfs_aio.c (working copy) > > @@ -787,6 +787,8 @@ aio_process_rw(struct kaiocb *job) > > * aio_aqueue() acquires a reference to the file that is > > * released in aio_free_entry(). > > */ > > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, > > + ("%s: vmspace mismatch", __func__)); > > if (cb->aio_lio_opcode == LIO_READ) { > > auio.uio_rw = UIO_READ; > > if (auio.uio_resid == 0) > > @@ -1054,6 +1056,8 @@ aio_switch_vmspace(struct kaiocb *job) > > { > > > > vmspace_switch_aio(job->userproc->p_vmspace); > > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, > > + ("%s: vmspace mismatch", __func__)); > > } > > > > If this panics, then vmspace_switch_aio() is not working for > > some reason. > > This issuse caused rare, this panic produced with issuse or on any aio > request? (this is production server) It would panic in the case that we are going to write into the wrong process (so about as rare as your issue). -- John Baldwin From owner-freebsd-stable@freebsd.org Thu Sep 15 19:09:52 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31E15BDCF1D for ; Thu, 15 Sep 2016 19:09:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EBDD01AD; Thu, 15 Sep 2016 19:09:51 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkc2e-000IGW-Nt; Thu, 15 Sep 2016 22:09:48 +0300 Date: Thu, 15 Sep 2016 22:09:48 +0300 From: Slawa Olhovchenkov To: John Baldwin Cc: freebsd-stable@freebsd.org Subject: Re: nginx and FreeBSD11 Message-ID: <20160915190948.GY2840@zxy.spb.ru> References: <20160907191348.GD22212@zxy.spb.ru> <1823460.vTm8IvUQsF@ralph.baldwin.cx> <20160915174948.GW2840@zxy.spb.ru> <15357564.UUkYdbUZHc@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15357564.UUkYdbUZHc@ralph.baldwin.cx> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 19:09:52 -0000 On Thu, Sep 15, 2016 at 11:54:12AM -0700, John Baldwin wrote: > > > Index: vfs_aio.c > > > =================================================================== > > > --- vfs_aio.c (revision 305811) > > > +++ vfs_aio.c (working copy) > > > @@ -787,6 +787,8 @@ aio_process_rw(struct kaiocb *job) > > > * aio_aqueue() acquires a reference to the file that is > > > * released in aio_free_entry(). > > > */ > > > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, > > > + ("%s: vmspace mismatch", __func__)); > > > if (cb->aio_lio_opcode == LIO_READ) { > > > auio.uio_rw = UIO_READ; > > > if (auio.uio_resid == 0) > > > @@ -1054,6 +1056,8 @@ aio_switch_vmspace(struct kaiocb *job) > > > { > > > > > > vmspace_switch_aio(job->userproc->p_vmspace); > > > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, > > > + ("%s: vmspace mismatch", __func__)); > > > } > > > > > > If this panics, then vmspace_switch_aio() is not working for > > > some reason. > > > > This issuse caused rare, this panic produced with issuse or on any aio > > request? (this is production server) > > It would panic in the case that we are going to write into the wrong > process (so about as rare as your issue). Can I configure automatic reboot (not halted) in this case? From owner-freebsd-stable@freebsd.org Thu Sep 15 19:41:32 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C8D3BDB92F for ; Thu, 15 Sep 2016 19:41:32 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E54A791F for ; Thu, 15 Sep 2016 19:41:31 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u8FJfQcF069211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 15 Sep 2016 21:41:27 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: slw@zxy.spb.ru Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id u8FJfIZk024491 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 16 Sep 2016 02:41:18 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: nginx and FreeBSD11 To: Slawa Olhovchenkov References: <20160907191348.GD22212@zxy.spb.ru> <1823460.vTm8IvUQsF@ralph.baldwin.cx> <20160915174948.GW2840@zxy.spb.ru> <15357564.UUkYdbUZHc@ralph.baldwin.cx> <20160915190948.GY2840@zxy.spb.ru> Cc: freebsd-stable@freebsd.org From: Eugene Grosbein Message-ID: <57DAF958.4030603@grosbein.net> Date: Fri, 16 Sep 2016 02:41:12 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20160915190948.GY2840@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 19:41:32 -0000 >> It would panic in the case that we are going to write into the wrong >> process (so about as rare as your issue). > > Can I configure automatic reboot (not halted) in this case? options KDB_UNATTENDED configures kernel for automatic reboot after panic. From owner-freebsd-stable@freebsd.org Thu Sep 15 20:17:54 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C953FBDC1B5 for ; Thu, 15 Sep 2016 20:17:54 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AA02BC30 for ; Thu, 15 Sep 2016 20:17:54 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id BA3CC10AF7E; Thu, 15 Sep 2016 16:17:53 -0400 (EDT) From: John Baldwin To: Slawa Olhovchenkov Cc: freebsd-stable@freebsd.org Subject: Re: nginx and FreeBSD11 Date: Thu, 15 Sep 2016 13:17:50 -0700 Message-ID: <10607861.GgoaaofMji@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-PRERELEASE; KDE/4.14.10; amd64; ; ) In-Reply-To: <20160915190948.GY2840@zxy.spb.ru> References: <20160907191348.GD22212@zxy.spb.ru> <15357564.UUkYdbUZHc@ralph.baldwin.cx> <20160915190948.GY2840@zxy.spb.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Thu, 15 Sep 2016 16:17:53 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 20:17:54 -0000 On Thursday, September 15, 2016 10:09:48 PM Slawa Olhovchenkov wrote: > On Thu, Sep 15, 2016 at 11:54:12AM -0700, John Baldwin wrote: > > > > > Index: vfs_aio.c > > > > =================================================================== > > > > --- vfs_aio.c (revision 305811) > > > > +++ vfs_aio.c (working copy) > > > > @@ -787,6 +787,8 @@ aio_process_rw(struct kaiocb *job) > > > > * aio_aqueue() acquires a reference to the file that is > > > > * released in aio_free_entry(). > > > > */ > > > > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, > > > > + ("%s: vmspace mismatch", __func__)); > > > > if (cb->aio_lio_opcode == LIO_READ) { > > > > auio.uio_rw = UIO_READ; > > > > if (auio.uio_resid == 0) > > > > @@ -1054,6 +1056,8 @@ aio_switch_vmspace(struct kaiocb *job) > > > > { > > > > > > > > vmspace_switch_aio(job->userproc->p_vmspace); > > > > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, > > > > + ("%s: vmspace mismatch", __func__)); > > > > } > > > > > > > > If this panics, then vmspace_switch_aio() is not working for > > > > some reason. > > > > > > This issuse caused rare, this panic produced with issuse or on any aio > > > request? (this is production server) > > > > It would panic in the case that we are going to write into the wrong > > process (so about as rare as your issue). > > Can I configure automatic reboot (not halted) in this case? FreeBSD in a stable branch should already reboot (after writing out a dump) by default unless you have configured it otherwise. -- John Baldwin From owner-freebsd-stable@freebsd.org Thu Sep 15 20:21:43 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D8D9BDC3C4; Thu, 15 Sep 2016 20:21:43 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 01314F51; Thu, 15 Sep 2016 20:21:43 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id F069D201; Thu, 15 Sep 2016 20:21:42 +0000 (UTC) Date: Thu, 15 Sep 2016 20:21:40 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: emaste@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <1673563282.25.1473970902993.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <297891549.23.1473963049906.JavaMail.jenkins@jenkins-9.freebsd.org> References: <297891549.23.1473963049906.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_11-i386 - Build #144 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_11-i386 X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2016 20:21:43 -0000 FreeBSD_STABLE_11-i386 - Build #144 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-i386/144/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-i386/144/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_11-i386/144/console Change summaries: 305848 by emaste: MFC r303677: Move/add ARM ELF PHDR types to elf_common.h 305847 by emaste: MFC r303670: Add ELFOSABI_ARM_AEABI ELF OSABI constant 305846 by emaste: MFC r303335: apply some style(9) to kbd: make function name start in column 1 305845 by emaste: MFC r305160: Set UEFI boot loader PE/COFF timestamps to known value for reproducible builds Sponsored by: The FreeBSD Foundation 305844 by emaste: MFC r305130: Update to ELF Tool Chain r3490 Improvements include: * readelf: report all relocation types in rel/rela for MIPS N64 * readelf: add ELFOSABI_ARM_AEABI * elfdump: add ELFOSABI_ARM_AEABI and ELFOSABI_ARM * Add recent RISC-V relocations * elfcopy: use elftc_timestamp, to support SOURCE_DATE_EPOCH MFC r305155: readelf: silence GCC 4.2.1 uninitialized variable warning Sponsored by: The FreeBSD Foundation 305842 by emaste: MFC r304191: elfcopy: correct comment typo (Missed in r305838) 305839 by emaste: MFC r304160: elfcopy: add elf64-littleaarch64 output target support 305838 by emaste: MFC r304151: elfcopy: silence GCC 5.3 unitialized variable warning Although it's a false positive there is little cost to initializing it always. From owner-freebsd-stable@freebsd.org Thu Sep 15 20:44:20 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A2C7BDCADF for ; Thu, 15 Sep 2016 20:44:20 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5D0BAF97; Thu, 15 Sep 2016 20:44:20 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkdW4-000KOI-JG; Thu, 15 Sep 2016 23:44:16 +0300 Date: Thu, 15 Sep 2016 23:44:16 +0300 From: Slawa Olhovchenkov To: John Baldwin Cc: freebsd-stable@freebsd.org Subject: Re: nginx and FreeBSD11 Message-ID: <20160915204416.GZ2840@zxy.spb.ru> References: <20160907191348.GD22212@zxy.spb.ru> <1823460.vTm8IvUQsF@ralph.baldwin.cx> <20160915174948.GW2840@zxy.spb.ru> <15357564.UUkYdbUZHc@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15357564.UUkYdbUZHc@ralph.baldwin.cx> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 20:44:20 -0000 On Thu, Sep 15, 2016 at 11:54:12AM -0700, John Baldwin wrote: > On Thursday, September 15, 2016 08:49:48 PM Slawa Olhovchenkov wrote: > > On Thu, Sep 15, 2016 at 10:28:11AM -0700, John Baldwin wrote: > > > > > On Thursday, September 15, 2016 05:41:03 PM Slawa Olhovchenkov wrote: > > > > On Wed, Sep 07, 2016 at 10:13:48PM +0300, Slawa Olhovchenkov wrote: > > > > > > > > > I am have strange issuse with nginx on FreeBSD11. > > > > > I am have FreeBSD11 instaled over STABLE-10. > > > > > nginx build for FreeBSD10 and run w/o recompile work fine. > > > > > nginx build for FreeBSD11 crushed inside rbtree lookups: next node > > > > > totaly craped. > > > > > > > > > > I am see next potential cause: > > > > > > > > > > 1) clang 3.8 code generation issuse > > > > > 2) system library issuse > > > > > > > > > > may be i am miss something? > > > > > > > > > > How to find real cause? > > > > > > > > I find real cause and this like show-stopper for RELEASE. > > > > I am use nginx with AIO and AIO from one nginx process corrupt memory > > > > from other nginx process. Yes, this is cross-process memory > > > > corruption. > > > > > > > > Last case, core dumped proccess with pid 1060 at 15:45:14. > > > > Corruped memory at 0x860697000. > > > > I am know about good memory at 0x86067f800. > > > > Dumping (form core) this region to file and analyze by hexdump I am > > > > found start of corrupt region -- offset 0000c8c0 from 0x86067f800. > > > > 0x86067f800+0xc8c0 = 0x86068c0c0 > > > > > > > > I am preliminary enabled debuggin of AIO started operation to nginx > > > > error log (memory address, file name, offset and size of transfer). > > > > > > > > grep -i 86068c0c0 error.log near 15:45:14 give target file. > > > > grep ce949665cbcd.hls error.log near 15:45:14 give next result: > > > > > > > > 2016/09/15 15:45:13 [notice] 1055#0: *11659936 AIO_RD 000000082065DB60 start 000000086068C0C0 561b0 2646736 ce949665cbcd.hls > > > > 2016/09/15 15:45:14 [notice] 1060#0: *10998125 AIO_RD 000000081F1FFB60 start 000000086FF2C0C0 6cdf0 140016832 ce949665cbcd.hls > > > > 2016/09/15 15:45:14 [notice] 1055#0: *11659936 AIO_RD 00000008216B6B60 start 000000086472B7C0 7ff70 2999424 ce949665cbcd.hls > > > > > > Does nginx only use AIO for regular files or does it also use it with sockets? > > > > Only for regular files. > > > > > You can try using this patch as a diagnostic (you will need to > > > run with INVARIANTS enabled, > > > > How much debugs produced? > > I am have about 5-10K aio's per second. > > > > > or at least enabled for vfs_aio.c): > > > > How I can do this (enable INVARIANTS for vfs_aio.c)? > > Include INVARIANT_SUPPORT in your kernel and add a line with: > > #define INVARIANTS > > at the top of sys/kern/vfs_aio.c. # sysctl -a | grep -i inva kern.timecounter.invariant_tsc: 1 kern.features.invariant_support: 1 options INVARIANT_SUPPORT but no string `vmspace mismatch` in kernel. May be I am miss some? #define INVARIANTS #include __FBSDID("$FreeBSD: stable/11/sys/kern/vfs_aio.c 304738 2016-08-24 09:18:38Z kib $"); #include "opt_compat.h" #include #include #include #include #include From owner-freebsd-stable@freebsd.org Thu Sep 15 22:06:45 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CAC1FBDC9B4 for ; Thu, 15 Sep 2016 22:06:45 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 61E73960 for ; Thu, 15 Sep 2016 22:06:45 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: by mail-wm0-x234.google.com with SMTP id 1so8516340wmz.1 for ; Thu, 15 Sep 2016 15:06:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lAg/CyrtwGGh6AyL39c9Dgu6jxk7fIvq5Qkzn/tS9bM=; b=oPgeB5x8GhewzVsjOLKknvCKy4qZCwk5w4p1tT79pJ/RW9Ujtb4Z58nPt7734YJHit gH8dORSuaWVRHDJjVOVaaD9+79b75F7yk4GSZbObNio4OHa4YJcgbJqreUdDwiCx33Y2 nmjUK0eBUORL6/RLREElu1Gjgsh4zQnbLKlIaC0+T8JcqK76Zd/Hw8Rqp/ruscarWpV4 zRQUZTpxFpyyTRrWN9OMT/xHEyBN3oYGXL+qleVF4Ca3+XctB3HmOtunlSMM1ADQaZ63 CAw5rf82lM9UGBemXmENxNzN3lxjS5zeWiYJ236gSmYt5eHqZUDZFnMFIFsybqKzqt+m ltaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lAg/CyrtwGGh6AyL39c9Dgu6jxk7fIvq5Qkzn/tS9bM=; b=D1/pm6GPOIBiCk/TymYS9dSULgDS3TYBqG00vvHkzvNyJOP5nIjAdzOmiMStZpPU3B eZNwSC8OGo1J9wFqbprfu1I+PDjI19wD4VQQc0vitCjIddJm+ZbavvT/Qey1MwLs+PU3 Wnb7FNtD9IR4l/n5j9nwjMbimYhqr1KLD7dIWn+hGuobrsxzUkjSuHke273/pyUuVJ8Z LPNYlp/j4ye1TANvyvBv49fgqNFtRs6VW2MwMAnudoU8soyL/pE62G0ITQTJ1XNbqyXX nBVW43hkATO9pBMf1iu73ksTxKsQciANPprQrRSGFCqnvo4S68LO35qbtu4v5uCHBbSC TkPw== X-Gm-Message-State: AE9vXwOVQ4SbdRKWb+mWgaOdhQD4xCmTn7TVpTfXAV1RI/YUl/hr3B+VBqA48B4L6xpcLyHApoc35PxxWWlXEhka X-Received: by 10.194.84.134 with SMTP id z6mr2189105wjy.204.1473977203863; Thu, 15 Sep 2016 15:06:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.157.23 with HTTP; Thu, 15 Sep 2016 15:06:42 -0700 (PDT) In-Reply-To: References: From: Steven Hartland Date: Thu, 15 Sep 2016 23:06:42 +0100 Message-ID: Subject: Re: NVMe as boot device. To: Andrey Cherkashin Cc: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2016 22:06:45 -0000 Yes but you need to boot with efi as that's the old thing mode that supports nvme boot. We have an nvme only ZFS box and it works fine On Thursday, 15 September 2016, Andrey Cherkashin wrote: > Hi, > > I know FreeBSD supports NVMe as root device, but does it support it as > boot? Can=E2=80=99t find any confirmation. From owner-freebsd-stable@freebsd.org Fri Sep 16 04:13:30 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9957BDC03D for ; Fri, 16 Sep 2016 04:13:30 +0000 (UTC) (envelope-from andoriyu@gmail.com) Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A4DC28A8 for ; Fri, 16 Sep 2016 04:13:30 +0000 (UTC) (envelope-from andoriyu@gmail.com) Received: by mail-pf0-x229.google.com with SMTP id q2so3228696pfj.3 for ; Thu, 15 Sep 2016 21:13:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=PHTLdH4SLtpJAuIRvgI/7HAyp7EUZc+2vlk9RUqE4vA=; b=rGq0ljrnvHTmqxqY/Wo9lqsv8WWw8SC3bTLDZEuHJFkzj0wRefMCIxwII4i4KT7YT/ lu88AAfArWt6EGP6BNvcdR0Z1aRNC+TTN7IPAktxKMxYBUj5N1AwJ7m/nLAXaFJ00sqW xCHp/HKpSOpGEQLhiZ1fQwXzRrUsbM1MCQegYrbDqkCKiA+jgo94VYBq/s07CBpoiSZQ DVstNAKOGFXSiCZz2UhuOwTwB7hgBGeAj+AEda6Wc5ts+ptEm/N+qBFr62WE/aAuTwK1 rj5sCySVy9VX7n57Al5XY/Y65kFbmd+V3/HzmcxGZlmcEWK7IjEVYoHhVnFTKPgq0Dri o9dA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=PHTLdH4SLtpJAuIRvgI/7HAyp7EUZc+2vlk9RUqE4vA=; b=eO9+lzK3PaHxK1qhplk76KDzOIX4HwF9Zj4R81TBT3L5KTc5NjIjvdqWAh9kyLOC55 YhJZ2d4kYpHhMtSxiSiXZ+06t2XvW/lHbwnbm0/nxQtl9LMyvNeqqsws8QTx5F1TWiKx dSzVPWf+yecoWic7FexnHQPVZx/tHDoMU2RC7l4t42YSpJAZUCPv88jVW3b+z8HRyVC9 6cqAYCY3Hp0rSB2NjqshQN0BPGv7qjQpXgaGu+j7BmrHZ0D8Ge88McpSDFBwlE12stYI r+pUOMIrx4m8V8+Y/W2UjKq3jRFC+dSks2hMaBExRcBc+JT80LudCHUNs0hZy3AyiEku BlxA== X-Gm-Message-State: AE9vXwMn7jUsixyJle6BvG/nuE6G91i09wb0kcBQMMv66ywFKV81jkRH1eN4lNmzfvEv0g== X-Received: by 10.98.107.198 with SMTP id g189mr19976727pfc.14.1473999210297; Thu, 15 Sep 2016 21:13:30 -0700 (PDT) Received: from ac-book.local.mail (cpe-76-170-61-115.socal.res.rr.com. [76.170.61.115]) by smtp.gmail.com with ESMTPSA id l81sm10084144pfi.14.2016.09.15.21.13.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Sep 2016 21:13:28 -0700 (PDT) Date: Thu, 15 Sep 2016 21:13:26 -0700 From: Andrey Cherkashin To: Warner Losh Cc: "=?utf-8?Q?freebsd-stable=40freebsd.org?=" Message-ID: In-Reply-To: References: Subject: Re: NVMe as boot device. X-Mailer: Airmail Beta (384) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="FE68F1D7-F723-44E7-88C0-5C377899952E"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 04:13:30 -0000 --FE68F1D7-F723-44E7-88C0-5C377899952E Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Glad to hear that. Thank you. On Thursday, 15 September 2016, Andrey Cherkashin = wrote: Hi, I know =46reeBSD supports NVMe as root device, but does it support it as = boot=3F Can=E2=80=99t find any confirmation. --FE68F1D7-F723-44E7-88C0-5C377899952E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using AMPGpg -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJX23FnAAoJEKSpiMgkaMpQNAYQAJVa58p7UIm77x6OUyUCMmRL BSwcVm2uEN6TfhhJE1R2DuqkjaRpKWHZXFdqsl+IRmxUAPoC+CEpaOu4yI1E7x6x B89zgwV8+NBf14SbHcpwKCE6r1fe+J2IMHxIguHPu1ZYwOk/F5vZdkxCXbAv0/VT 1pr8qvlASxPmLXzEnRCI2BvsiVkGRMRArkGpk/xe8VEWK2DGepC4XLmYGTE95lq6 ZHRsF0YD3966YJVCJDiTNo/KjNAMM6vCT6SRLvbbCc85mkf1+Tn6vXQq2wbLZz3F UsTTcPs0+sU+THRw3Vh8dRPoLvnl5qO/J1CzpvJGNRsGtSMCiywKZpNpvnw57Mix s3kAzv9ZcKfLv3+osh1KxDVHDdekMEKDyp6cRE/Z6GS8kN8Gg3Rrl67zizrDNtnq 6wtdWX003Sbkj1J+tcimnh/aB7nzPFI8DZN/cKvh0KigkUrXmuOH0n5xe4dg8NaD AA39OIzwps10xbUtekt6iDj8QMaoujdd+XzM5huYfkdWTfY4NiHCntiCRnVSQMvO HcBuEb7EBBAxKr+wSlS5d/afysBBfK8uPE0x+0wco9rkqWP1VMthr27TZh4pMu6h vGVctej0dYUVaINI8VwlORvminPqKqm/tGQ4GBwb0kDgbJlm7gvBpjgkwMjVeigE sfxQyMEddJPHvEhQZlhy -----END PGP SIGNATURE----- --FE68F1D7-F723-44E7-88C0-5C377899952E-- From owner-freebsd-stable@freebsd.org Fri Sep 16 07:44:03 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63BB4BDCF49 for ; Fri, 16 Sep 2016 07:44:03 +0000 (UTC) (envelope-from sa.inbox@gmail.com) Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C09316E6 for ; Fri, 16 Sep 2016 07:44:03 +0000 (UTC) (envelope-from sa.inbox@gmail.com) Received: by mail-oi0-x229.google.com with SMTP id q188so102259357oia.3 for ; Fri, 16 Sep 2016 00:44:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=tPQFsg8eqcZn9vqig3Ath8zevICUMO7/tqe0Mbc5EWY=; b=NDqWGni1P6Y1NmtKEXvC0AMTpcpdp30CEj1HbM4hWSUXr4ehWdDGEWLsB+t2zrJnXn QVOk+V//9tY95yGRsnhsn237oQURS9mK1uZtf760NH80XBALmCgVC72OjYpouXP6Ofpz zQNrz90KiPGJs3UZfdQ3fgQmm4IRuGoKYuLnSTXDNRf5bVWHZIUUhkDje/AutCxzT2ed EWq3h0EiFu5nv79PenJBNUuhz85C2WOTXpBODl5VEbSukNKTT0I0PB3pVq0KEgVL8y41 I6Pk8KAM7Nsyd7sQl8+uyAwdDZ6brBxj7wvD+uBWsyVcr+yzX0S31JYgcfxplNVxL5jj QF1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=tPQFsg8eqcZn9vqig3Ath8zevICUMO7/tqe0Mbc5EWY=; b=NnB4No68/7/+1LciJI82kLx6OFJj6Y6F6ncYw+ZJfgAOpsW6z6UMWOw7ZbK5kYBHtx 2ojsr2xUn2VLrm69zJVpsqYFL0aJNUAHOK+fQ841n/0k2vIC6tAFCbIq1NjgvlzDvL8y S/KZzbO8FZWpwxW+4+qUP2UAoGY7V/sqqcFzSv+fIFRhmKFkH+Lew5P4IQzKOywQVNdi WsYCwyznAyVGFalb/83Oul+MLp58aKdCxLG+WtYg4d52fdOEtOhoCH3uW9gEW33KC7pq wAu+QmLp3BdcOIn684Mv6tVxtPV8sgbkC/aiPGaW/88LqyCeP20DH0Av3Ovr3NwxxUqd foOw== X-Gm-Message-State: AE9vXwMov2y6sYiK5oTtB3IynH5j6BZQMnKxW6PDYLM8RDxAfXE7EMRTqCUfRGmmuA3bEDfngisd3wfuITSkQA== X-Received: by 10.157.29.186 with SMTP id y55mr4074655otd.228.1474011842013; Fri, 16 Sep 2016 00:44:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.37.180 with HTTP; Fri, 16 Sep 2016 00:43:41 -0700 (PDT) From: Alexander Shitov Date: Fri, 16 Sep 2016 10:43:41 +0300 Message-ID: Subject: FreeBSD 11.0-RC3 failed on hyper-v 2012r2 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 07:44:03 -0000 I've found that FreeBSD 11.0-RC3 failed to install on hyperv 2012r2 on disk partitioning step ------------------------Abort----------------- |Partitioning error | | | |An installation step has been aborted. Would| |you like to restart the installation or exit| |the installer? | | --------------------------------------------- Any thoughts? Relevant bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212721 From owner-freebsd-stable@freebsd.org Fri Sep 16 09:16:31 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9F80BDC078 for ; Fri, 16 Sep 2016 09:16:31 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 540362EA; Fri, 16 Sep 2016 09:16:31 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u8G9GI0V092376 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 16 Sep 2016 12:16:18 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u8G9GI0V092376 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u8G9GHBO092375; Fri, 16 Sep 2016 12:16:17 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 16 Sep 2016 12:16:17 +0300 From: Konstantin Belousov To: John Baldwin Cc: Slawa Olhovchenkov , freebsd-stable@freebsd.org Subject: Re: nginx and FreeBSD11 Message-ID: <20160916091617.GT38409@kib.kiev.ua> References: <20160907191348.GD22212@zxy.spb.ru> <1823460.vTm8IvUQsF@ralph.baldwin.cx> <20160915174948.GW2840@zxy.spb.ru> <15357564.UUkYdbUZHc@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15357564.UUkYdbUZHc@ralph.baldwin.cx> User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 09:16:31 -0000 On Thu, Sep 15, 2016 at 11:54:12AM -0700, John Baldwin wrote: > On Thursday, September 15, 2016 08:49:48 PM Slawa Olhovchenkov wrote: > > On Thu, Sep 15, 2016 at 10:28:11AM -0700, John Baldwin wrote: > > > > > On Thursday, September 15, 2016 05:41:03 PM Slawa Olhovchenkov wrote: > > > > On Wed, Sep 07, 2016 at 10:13:48PM +0300, Slawa Olhovchenkov wrote: > > > > > > > > > I am have strange issuse with nginx on FreeBSD11. > > > > > I am have FreeBSD11 instaled over STABLE-10. > > > > > nginx build for FreeBSD10 and run w/o recompile work fine. > > > > > nginx build for FreeBSD11 crushed inside rbtree lookups: next node > > > > > totaly craped. > > > > > > > > > > I am see next potential cause: > > > > > > > > > > 1) clang 3.8 code generation issuse > > > > > 2) system library issuse > > > > > > > > > > may be i am miss something? > > > > > > > > > > How to find real cause? > > > > > > > > I find real cause and this like show-stopper for RELEASE. > > > > I am use nginx with AIO and AIO from one nginx process corrupt memory > > > > from other nginx process. Yes, this is cross-process memory > > > > corruption. > > > > > > > > Last case, core dumped proccess with pid 1060 at 15:45:14. > > > > Corruped memory at 0x860697000. > > > > I am know about good memory at 0x86067f800. > > > > Dumping (form core) this region to file and analyze by hexdump I am > > > > found start of corrupt region -- offset 0000c8c0 from 0x86067f800. > > > > 0x86067f800+0xc8c0 = 0x86068c0c0 > > > > > > > > I am preliminary enabled debuggin of AIO started operation to nginx > > > > error log (memory address, file name, offset and size of transfer). > > > > > > > > grep -i 86068c0c0 error.log near 15:45:14 give target file. > > > > grep ce949665cbcd.hls error.log near 15:45:14 give next result: > > > > > > > > 2016/09/15 15:45:13 [notice] 1055#0: *11659936 AIO_RD 000000082065DB60 start 000000086068C0C0 561b0 2646736 ce949665cbcd.hls > > > > 2016/09/15 15:45:14 [notice] 1060#0: *10998125 AIO_RD 000000081F1FFB60 start 000000086FF2C0C0 6cdf0 140016832 ce949665cbcd.hls > > > > 2016/09/15 15:45:14 [notice] 1055#0: *11659936 AIO_RD 00000008216B6B60 start 000000086472B7C0 7ff70 2999424 ce949665cbcd.hls > > > > > > Does nginx only use AIO for regular files or does it also use it with sockets? > > > > Only for regular files. > > > > > You can try using this patch as a diagnostic (you will need to > > > run with INVARIANTS enabled, > > > > How much debugs produced? > > I am have about 5-10K aio's per second. > > > > > or at least enabled for vfs_aio.c): > > > > How I can do this (enable INVARIANTS for vfs_aio.c)? > > Include INVARIANT_SUPPORT in your kernel and add a line with: > > #define INVARIANTS > > at the top of sys/kern/vfs_aio.c. > > > > > > Index: vfs_aio.c > > > =================================================================== > > > --- vfs_aio.c (revision 305811) > > > +++ vfs_aio.c (working copy) > > > @@ -787,6 +787,8 @@ aio_process_rw(struct kaiocb *job) > > > * aio_aqueue() acquires a reference to the file that is > > > * released in aio_free_entry(). > > > */ > > > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, > > > + ("%s: vmspace mismatch", __func__)); > > > if (cb->aio_lio_opcode == LIO_READ) { > > > auio.uio_rw = UIO_READ; > > > if (auio.uio_resid == 0) > > > @@ -1054,6 +1056,8 @@ aio_switch_vmspace(struct kaiocb *job) > > > { > > > > > > vmspace_switch_aio(job->userproc->p_vmspace); > > > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace, > > > + ("%s: vmspace mismatch", __func__)); > > > } > > > > > > If this panics, then vmspace_switch_aio() is not working for > > > some reason. > > > > This issuse caused rare, this panic produced with issuse or on any aio > > request? (this is production server) > > It would panic in the case that we are going to write into the wrong > process (so about as rare as your issue). > vmspace_switch_aio() allows context switching with old curpmap and new proc->p_vmspace. This is a weird condition, where curproc->p_vmspace->vm_pmap is not equal to curcpu->pc_curpmap. I do not see an obvious place which would immediately break, e.g. even for context switch between assignment of newvm to p_vmspace and pmap_activate(), the context-switch call to pmap_activate_sw() seems to do right thing. Still, just in case, try this diff --git a/sys/vm/vm_map.c b/sys/vm/vm_map.c index a23468e..fbaa6c1 100644 --- a/sys/vm/vm_map.c +++ b/sys/vm/vm_map.c @@ -481,6 +481,7 @@ vmspace_switch_aio(struct vmspace *newvm) if (oldvm == newvm) return; + critical_enter(); /* * Point to the new address space and refer to it. */ @@ -489,6 +490,7 @@ vmspace_switch_aio(struct vmspace *newvm) /* Activate the new mapping. */ pmap_activate(curthread); + critical_exit(); /* Remove the daemon's reference to the old address space. */ KASSERT(oldvm->vm_refcnt > 1, From owner-freebsd-stable@freebsd.org Fri Sep 16 10:17:18 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C18D8BDC491 for ; Fri, 16 Sep 2016 10:17:18 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 73A50AC8; Fri, 16 Sep 2016 10:17:18 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkqCo-000DxV-4X; Fri, 16 Sep 2016 13:17:14 +0300 Date: Fri, 16 Sep 2016 13:17:14 +0300 From: Slawa Olhovchenkov To: Konstantin Belousov Cc: John Baldwin , freebsd-stable@freebsd.org Subject: Re: nginx and FreeBSD11 Message-ID: <20160916101713.GA2840@zxy.spb.ru> References: <20160907191348.GD22212@zxy.spb.ru> <1823460.vTm8IvUQsF@ralph.baldwin.cx> <20160915174948.GW2840@zxy.spb.ru> <15357564.UUkYdbUZHc@ralph.baldwin.cx> <20160916091617.GT38409@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160916091617.GT38409@kib.kiev.ua> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 10:17:18 -0000 On Fri, Sep 16, 2016 at 12:16:17PM +0300, Konstantin Belousov wrote: > > vmspace_switch_aio() allows context switching with old curpmap > and new proc->p_vmspace. This is a weird condition, where > curproc->p_vmspace->vm_pmap is not equal to curcpu->pc_curpmap. I do > not see an obvious place which would immediately break, e.g. even > for context switch between assignment of newvm to p_vmspace and > pmap_activate(), the context-switch call to pmap_activate_sw() seems to > do right thing. > > Still, just in case, try this > > diff --git a/sys/vm/vm_map.c b/sys/vm/vm_map.c > index a23468e..fbaa6c1 100644 > --- a/sys/vm/vm_map.c > +++ b/sys/vm/vm_map.c > @@ -481,6 +481,7 @@ vmspace_switch_aio(struct vmspace *newvm) > if (oldvm == newvm) > return; > > + critical_enter(); > /* > * Point to the new address space and refer to it. > */ > @@ -489,6 +490,7 @@ vmspace_switch_aio(struct vmspace *newvm) > > /* Activate the new mapping. */ > pmap_activate(curthread); > + critical_exit(); > > /* Remove the daemon's reference to the old address space. */ > KASSERT(oldvm->vm_refcnt > 1, OK, nginx core dumped, kernel don't crushed. Now I am try this patch (critical_enter) and reboot. PS: vi regresion: can't exit from vi when no space on /tmp From owner-freebsd-stable@freebsd.org Fri Sep 16 10:37:41 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7B3BBDC8B0 for ; Fri, 16 Sep 2016 10:37:41 +0000 (UTC) (envelope-from sa.inbox@gmail.com) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B8214699 for ; Fri, 16 Sep 2016 10:37:41 +0000 (UTC) (envelope-from sa.inbox@gmail.com) Received: by mail-oi0-x22d.google.com with SMTP id m11so106646097oif.1 for ; Fri, 16 Sep 2016 03:37:41 -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; bh=nrrV4cJuvwqA+XTVJZwRDZbUnVYE4X+4XLc8uyh3duw=; b=0EkmLWz/iYJIiUdXjetyBSco8U5DCMpckjbkXyGOtj9y7ab5MV+JeZ4bNSome8xaCr IsSHhgMLaBB6h2if5UCNBuhAuZQYi86mtikv5NvjbnuZbqCQrNnBkNGq0XMTIadM6j2E ijsrnIAJbAVy8mVk2yOl0GG59sFeiAznCnHUM78HBwcjeytzg4sFHG8Eo6uJ9DomzGoO w0oITBlZa3wIghpuEbq2MFpM1YtKA+wIOPV9vEjesW9SWXwLQhCjIAaQLVloqnjbsVez O3Rgddp/Og4z4e9Nyc68NfdYnF6hihV3Zwgz4138WJDMX0f0pE2ubIMsxEcQu2lOWOWC lpnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=nrrV4cJuvwqA+XTVJZwRDZbUnVYE4X+4XLc8uyh3duw=; b=Mhe6LAnp87Va+Q+HQvYeb3X/90Kmlh3jJDE+0PnzVFvJrGHOohTtvEsTwPoHugPaDC q73mq+M/yv0dhSfceWQAtmsryUN8ZMrdJ7TAKBEkF+4JMPiEFJdcdI7kaJAFiYJaUeTz Nqg2MxvuVKvTQOhXChJhObipXuB4rVtODl6r/AQBWe4CsyKmxdkm0JbDqY84A/6DlO+D sR2U0ROL87bmg/TULTZ9S6vXGKKQ99GLM80FznnFzabNvCCb/JC1THKRsIK/mqhwkezc qxsVCN5D9llAdHo+vdegzLjae4y4f5UvpFsNFuXpTOL0Ul3O0CGLv9TtDXVL90dgE0+6 7IqQ== X-Gm-Message-State: AE9vXwO115jClkNpb6MGichezOXAa8XDFisn8Ju7AD9M2F41yhk8WRcBjjOuJJkl6zMvD/zgO+B3dTyB+uOyow== X-Received: by 10.157.45.23 with SMTP id v23mr11550635ota.167.1474022260791; Fri, 16 Sep 2016 03:37:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.37.180 with HTTP; Fri, 16 Sep 2016 03:37:20 -0700 (PDT) In-Reply-To: References: From: Alexander Shitov Date: Fri, 16 Sep 2016 13:37:20 +0300 Message-ID: Subject: Re: FreeBSD 11.0-RC3 failed on hyper-v 2012r2 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 10:37:42 -0000 Installation fails with fixed sized and dynamically sized disks. Issue is important because it affects possibility to upgrade existing FreeBSD 10.3 production VMs to FreeBSD 11.0 On Fri, Sep 16, 2016 at 10:43 AM, Alexander Shitov wrote: > I've found that FreeBSD 11.0-RC3 failed to install on hyperv 2012r2 on > disk partitioning step > > ------------------------Abort----------------- > |Partitioning error | > | | > |An installation step has been aborted. Would| > |you like to restart the installation or exit| > |the installer? | > | > --------------------------------------------- > Any thoughts? > > Relevant bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212721 From owner-freebsd-stable@freebsd.org Fri Sep 16 13:57:21 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 818FEBDC88C for ; Fri, 16 Sep 2016 13:57:21 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46218FCC; Fri, 16 Sep 2016 13:57:21 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bktdg-000JyE-8E; Fri, 16 Sep 2016 16:57:12 +0300 Date: Fri, 16 Sep 2016 16:57:12 +0300 From: Slawa Olhovchenkov To: Konstantin Belousov Cc: John Baldwin , freebsd-stable@freebsd.org Subject: Re: nginx and FreeBSD11 Message-ID: <20160916135712.GB2840@zxy.spb.ru> References: <20160907191348.GD22212@zxy.spb.ru> <1823460.vTm8IvUQsF@ralph.baldwin.cx> <20160915174948.GW2840@zxy.spb.ru> <15357564.UUkYdbUZHc@ralph.baldwin.cx> <20160916091617.GT38409@kib.kiev.ua> <20160916101713.GA2840@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160916101713.GA2840@zxy.spb.ru> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 13:57:21 -0000 On Fri, Sep 16, 2016 at 01:17:14PM +0300, Slawa Olhovchenkov wrote: > On Fri, Sep 16, 2016 at 12:16:17PM +0300, Konstantin Belousov wrote: > > > > > vmspace_switch_aio() allows context switching with old curpmap > > and new proc->p_vmspace. This is a weird condition, where > > curproc->p_vmspace->vm_pmap is not equal to curcpu->pc_curpmap. I do > > not see an obvious place which would immediately break, e.g. even > > for context switch between assignment of newvm to p_vmspace and > > pmap_activate(), the context-switch call to pmap_activate_sw() seems to > > do right thing. > > > > Still, just in case, try this > > > > diff --git a/sys/vm/vm_map.c b/sys/vm/vm_map.c > > index a23468e..fbaa6c1 100644 > > --- a/sys/vm/vm_map.c > > +++ b/sys/vm/vm_map.c > > @@ -481,6 +481,7 @@ vmspace_switch_aio(struct vmspace *newvm) > > if (oldvm == newvm) > > return; > > > > + critical_enter(); > > /* > > * Point to the new address space and refer to it. > > */ > > @@ -489,6 +490,7 @@ vmspace_switch_aio(struct vmspace *newvm) > > > > /* Activate the new mapping. */ > > pmap_activate(curthread); > > + critical_exit(); > > > > /* Remove the daemon's reference to the old address space. */ > > KASSERT(oldvm->vm_refcnt > 1, > > OK, nginx core dumped, kernel don't crushed. > Now I am try this patch (critical_enter) and reboot. nginx still core dumped. From owner-freebsd-stable@freebsd.org Fri Sep 16 18:18:44 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5F40BDDCD1 for ; Fri, 16 Sep 2016 18:18:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 770FEE63 for ; Fri, 16 Sep 2016 18:18:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkxih-0000IO-Lh; Fri, 16 Sep 2016 21:18:39 +0300 Date: Fri, 16 Sep 2016 21:18:39 +0300 From: Slawa Olhovchenkov To: Konstantin Belousov Cc: freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160916181839.GC2960@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160915085938.GN38409@kib.kiev.ua> <20160915090633.GS2840@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160915090633.GS2840@zxy.spb.ru> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 18:18:44 -0000 On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > > > On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrote: > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > > Under high network load and may be addtional conditional system go to > > > > > unresponsible state -- no reaction to network and console (USB IPMI > > > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > > > debug this? > > > > > > > > Can you panic it from console to get to db> to get backtrace and other > > > > info when it goes unresponsive? > > > > > > ipmi console don't respond (chassis power diag don't react) > > > login on sol console stuck on *tcp. > > > > Is 'login' you reference is the ipmi client state, or you mean login(1) > > on the wedged host ? > > on the wedged host > > > If BMC stops responding simultaneously with the host, I would suspect > > the hardware platform issues instead of a software problem. Do you have > > dedicated LAN port for BMC ? > > Yes. > But BMC emulate USB keyboard and this is may be lock inside USB > system. > "ipmi console don't respond" must be read as "ipmi console runnnig and > attached but system don't react to keypress on this console". > at the sime moment system respon to `enter` on ipmi sol console, but > after enter `root` stuck in login in the '*tcp' state (I think this is > NIS related). ~^B don't break to debuger. But I can login to sol console. All system work tooooo slooooow. Some cores displayed by top as 100% idle. Some cores displayed by top as 100% interrupt. last pid: 16631; load averages: 9.00, 9.08, 9.35 up 0+06:26:34 19:53:13 832 processes: 22 running, 765 sleeping, 42 waiting, 3 lock CPU 0: 0.0% user, 0.0% nice, 0.0% system, 100% interrupt, 0.0% idle CPU 1: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 3: 0.0% user, 0.0% nice, 0.4% system, 0.0% interrupt, 99.6% idle CPU 4: 0.0% user, 0.0% nice, 0.0% system, 100% interrupt, 0.0% idle CPU 5: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 6: 0.0% user, 0.0% nice, 0.0% system, 100% interrupt, 0.0% idle CPU 7: 0.0% user, 0.0% nice, 0.0% system, 100% interrupt, 0.0% idle CPU 8: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 9: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 10: 0.0% user, 0.0% nice, 0.0% system, 100% interrupt, 0.0% idle CPU 11: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 1564M Active, 5169M Inact, 114G Wired, 4548M Free ARC: 107G Total, 98G MFU, 9476M MRU, 160K Anon, 150M Header, 254M Other Swap: 32G Total, 32G Free Now I am trying to # pmcstat -c 0 -S CPU_CLK_UNHALTED_CORE -l 10 -O sample0.out load: 10.32 cmd: pmcstat 16878 [runnable] 4632.42r 0.00u 0.00s 0% 2940k I am still waiting From owner-freebsd-stable@freebsd.org Fri Sep 16 18:23:17 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 137D6BDDEF3 for ; Fri, 16 Sep 2016 18:23:17 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E2AE62D for ; Fri, 16 Sep 2016 18:23:16 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u8GIN6Ew073708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 16 Sep 2016 20:23:07 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: slw@zxy.spb.ru Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id u8GIN1Ev024215 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 17 Sep 2016 01:23:01 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: 11.0 stuck on high network load To: Slawa Olhovchenkov References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160915085938.GN38409@kib.kiev.ua> <20160915090633.GS2840@zxy.spb.ru> <20160916181839.GC2960@zxy.spb.ru> Cc: freebsd-stable@FreeBSD.org From: Eugene Grosbein Message-ID: <57DC3880.7090405@grosbein.net> Date: Sat, 17 Sep 2016 01:22:56 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20160916181839.GC2960@zxy.spb.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 18:23:17 -0000 17.09.2016 1:18, Slawa Olhovchenkov пишет: > ~^B don't break to debuger. Make sure your kernel config has: # Solaris implements a new BREAK which is initiated by a character # sequence CR ~ ^b which is similar to a familiar pattern used on # Sun servers by the Remote Console. There are FreeBSD extensions: # CR ~ ^p requests force panic and CR ~ ^r requests a clean reboot. options ALT_BREAK_TO_DEBUGGER And don't forget that tilde (~) should follow CR (Enter). From owner-freebsd-stable@freebsd.org Fri Sep 16 18:26:19 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3E31BDD003 for ; Fri, 16 Sep 2016 18:26:19 +0000 (UTC) (envelope-from cejkar@fit.vutbr.cz) Received: from kazi.fit.vutbr.cz (kazi6.fit.vutbr.cz [IPv6:2001:67c:1220:808::93e5:80c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "kazi.fit.vutbr.cz", Issuer "Brno University of Technology CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FC2F81F for ; Fri, 16 Sep 2016 18:26:19 +0000 (UTC) (envelope-from cejkar@fit.vutbr.cz) Received: from kazi.fit.vutbr.cz (localhost [127.0.0.1]) by kazi.fit.vutbr.cz (8.15.2/8.15.2) with ESMTPS id u8GIQGPU083822 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 16 Sep 2016 20:26:16 +0200 (CEST) Received: (from cejkar@localhost) by kazi.fit.vutbr.cz (8.15.2/8.15.1/Submit) id u8GIQG5M083821 for freebsd-stable@freebsd.org; Fri, 16 Sep 2016 20:26:16 +0200 (CEST) (envelope-from cejkar@fit.vutbr.cz) X-Authentication-Warning: kazi.fit.vutbr.cz: cejkar set sender to cejkar@fit.vutbr.cz using -f Date: Fri, 16 Sep 2016 20:26:16 +0200 From: Cejka Rudolf To: freebsd-stable@freebsd.org Subject: Bug 209491 (Broadcast storm with ipfw+natd+gateway) from -CURRENT is now in 11-STABLE Message-ID: <20160916182616.GA81570@fit.vutbr.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.6.1 (2016-04-27) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fit.vutbr.cz; h=date:from:to:subject:message-id:mime-version:content-type; s=mx1; bh=a7bkcP7/IBGFVLE0e3MMtyz/LEbzi4BtKRibXl9O7l8=; b=57Nw467WYLGNBxM5VhZqikw18HzEIOs4AFIUm7dZNzGSO6S8UyFIqKmwrXUvFVNzQB4S2+XeSaRrb/Yj9W/Mlkzy9e0XBFW3iSg2Jb1uSGeQfQSnZzfRng7W1AhhKaWBZbpSPHK1i8MOOrH6tjQ8Tis/vVtkUcY5aNEUpNj/CWE= X-Scanned-By: MIMEDefang 2.78 on 147.229.8.12 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 18:26:19 -0000 Hello, I have reported bug 209491 (Broadcast storm with ipfw+natd+gateway) for -CURRENT, but now it is also in 11-STABLE. It is still here, as I have tested it today with src r305790 (11.0-PRERELEASE). So please be warned. If you are using similar configuration as me with ipfw+natd+gateway, you can see unusual traffic on your outer network. In our case, three servers with outer interface on the same local network (broadcast domain) plus some workstations with netbios queries means seriously overloaded network. Best regards. -- Rudolf Cejka http://www.fit.vutbr.cz/~cejkar Brno University of Technology, Faculty of Information Technology Bozetechova 2, 612 66 Brno, Czech Republic From owner-freebsd-stable@freebsd.org Fri Sep 16 18:31:00 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2FAFCBDD0F1 for ; Fri, 16 Sep 2016 18:31:00 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id 203AB9E7 for ; Fri, 16 Sep 2016 18:30:59 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 7F6C417E32; Fri, 16 Sep 2016 11:30:53 -0700 (PDT) Date: Fri, 16 Sep 2016 11:30:53 -0700 From: hiren panchasara To: Slawa Olhovchenkov Cc: Konstantin Belousov , freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160916183053.GL9397@strugglingcoder.info> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160915085938.GN38409@kib.kiev.ua> <20160915090633.GS2840@zxy.spb.ru> <20160916181839.GC2960@zxy.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="lFd1dPlLw0MeZdw2" Content-Disposition: inline In-Reply-To: <20160916181839.GC2960@zxy.spb.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 18:31:00 -0000 --lFd1dPlLw0MeZdw2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: >=20 > > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > >=20 > > > On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrote: > > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > >=20 > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > > > Under high network load and may be addtional conditional system= go to > > > > > > unresponsible state -- no reaction to network and console (USB = IPMI > > > > > > emulation). INVARIANTS give to high overhad. Is this exist some= way to > > > > > > debug this? > > > > >=20 > > > > > Can you panic it from console to get to db> to get backtrace and = other > > > > > info when it goes unresponsive? > > > >=20 > > > > ipmi console don't respond (chassis power diag don't react) > > > > login on sol console stuck on *tcp. > > >=20 > > > Is 'login' you reference is the ipmi client state, or you mean login(= 1) > > > on the wedged host ? > >=20 > > on the wedged host > >=20 > > > If BMC stops responding simultaneously with the host, I would suspect > > > the hardware platform issues instead of a software problem. Do you h= ave > > > dedicated LAN port for BMC ? > >=20 > > Yes. > > But BMC emulate USB keyboard and this is may be lock inside USB > > system. > > "ipmi console don't respond" must be read as "ipmi console runnnig and > > attached but system don't react to keypress on this console". > > at the sime moment system respon to `enter` on ipmi sol console, but > > after enter `root` stuck in login in the '*tcp' state (I think this is > > NIS related). >=20 > ~^B don't break to debuger. > But I can login to sol console. You can probably: debug.kdb.enter: set to enter the debugger or force a panic and get vmcore: debug.kdb.panic: set to panic the kernel Cheers, Hiren --lFd1dPlLw0MeZdw2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJX3DpUXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lcFMH/2xGmwkl+aCnFgAx6j0kvQ4W kaUcihnWA2osBCErqSVgW6GtBMV+bD0iqNLGaiolLP146i89YHoI0gfNpjTpF/XF lWBln7Fi/NJrnAJyBnixmYgwiDd5A+P2S7WGFuf6FYf6IM9fCh6tI7eXXLcefvv2 2KauMT3hqQTHb/etRPt9Hfd0KJPY8A/ApoZWOzhlwIniASi1nlzs565yRcQZUkk6 0S4+JqXVHPjWsGWRbbI6y1+6085m81v+cHo4C5JSz3tihTSIvXLh1FBlINQ9+Hl2 g1e5UtQik/U9aopI8N21WhgopXwqAzAMlk5jbRwItEe/ZDSbiD9UEu5hx+3vB/k= =I/3D -----END PGP SIGNATURE----- --lFd1dPlLw0MeZdw2-- From owner-freebsd-stable@freebsd.org Fri Sep 16 18:42:32 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C3E2BDD460 for ; Fri, 16 Sep 2016 18:42:32 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DA7812C for ; Fri, 16 Sep 2016 18:42:32 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bky5l-0000ra-VY; Fri, 16 Sep 2016 21:42:30 +0300 Date: Fri, 16 Sep 2016 21:42:29 +0300 From: Slawa Olhovchenkov To: hiren panchasara Cc: Konstantin Belousov , freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160916184229.GF2840@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160915085938.GN38409@kib.kiev.ua> <20160915090633.GS2840@zxy.spb.ru> <20160916181839.GC2960@zxy.spb.ru> <20160916183053.GL9397@strugglingcoder.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160916183053.GL9397@strugglingcoder.info> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 18:42:32 -0000 On Fri, Sep 16, 2016 at 11:30:53AM -0700, hiren panchasara wrote: > On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > > On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > > > > > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > > > > > > > On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrote: > > > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > > > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > > > > Under high network load and may be addtional conditional system go to > > > > > > > unresponsible state -- no reaction to network and console (USB IPMI > > > > > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > > > > > debug this? > > > > > > > > > > > > Can you panic it from console to get to db> to get backtrace and other > > > > > > info when it goes unresponsive? > > > > > > > > > > ipmi console don't respond (chassis power diag don't react) > > > > > login on sol console stuck on *tcp. > > > > > > > > Is 'login' you reference is the ipmi client state, or you mean login(1) > > > > on the wedged host ? > > > > > > on the wedged host > > > > > > > If BMC stops responding simultaneously with the host, I would suspect > > > > the hardware platform issues instead of a software problem. Do you have > > > > dedicated LAN port for BMC ? > > > > > > Yes. > > > But BMC emulate USB keyboard and this is may be lock inside USB > > > system. > > > "ipmi console don't respond" must be read as "ipmi console runnnig and > > > attached but system don't react to keypress on this console". > > > at the sime moment system respon to `enter` on ipmi sol console, but > > > after enter `root` stuck in login in the '*tcp' state (I think this is > > > NIS related). > > > > ~^B don't break to debuger. > > But I can login to sol console. > > You can probably: > debug.kdb.enter: set to enter the debugger > > or force a panic and get vmcore: > debug.kdb.panic: set to panic the kernel > I am still waiting to exit pmcstat. Oh, for NMI need not `ipmitool chassis power diag`! need `ipmitool power diag`! But debugger not entered: ^C^C^C^C^C^C^C^CNMI ... going to debugger NMI ... going to debugger NMI ... going to debugger NMI ... going to debugger NMI ... going to debugger NMI ... going to debugger NMI ... going to debugger NMI ... going to debugger NMI ... going to debugger NMI ... going to debugger NMI ... going to debugger NMI ... going to debugger load: 9.91 cmd: pmcstat 16878 [runnable] 5930.57r 0.00u 0.00s 0% 2940k From owner-freebsd-stable@freebsd.org Fri Sep 16 19:03:33 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1825ABDD8D2 for ; Fri, 16 Sep 2016 19:03:33 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C93DEC6E for ; Fri, 16 Sep 2016 19:03:32 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkyQ6-0001L7-5c; Fri, 16 Sep 2016 22:03:30 +0300 Date: Fri, 16 Sep 2016 22:03:30 +0300 From: Slawa Olhovchenkov To: hiren panchasara Cc: Konstantin Belousov , freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160916190330.GG2840@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160915085938.GN38409@kib.kiev.ua> <20160915090633.GS2840@zxy.spb.ru> <20160916181839.GC2960@zxy.spb.ru> <20160916183053.GL9397@strugglingcoder.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160916183053.GL9397@strugglingcoder.info> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 19:03:33 -0000 On Fri, Sep 16, 2016 at 11:30:53AM -0700, hiren panchasara wrote: > On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > > On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > > > > > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > > > > > > > On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrote: > > > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > > > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > > > > Under high network load and may be addtional conditional system go to > > > > > > > unresponsible state -- no reaction to network and console (USB IPMI > > > > > > > emulation). INVARIANTS give to high overhad. Is this exist some way to > > > > > > > debug this? > > > > > > > > > > > > Can you panic it from console to get to db> to get backtrace and other > > > > > > info when it goes unresponsive? > > > > > > > > > > ipmi console don't respond (chassis power diag don't react) > > > > > login on sol console stuck on *tcp. > > > > > > > > Is 'login' you reference is the ipmi client state, or you mean login(1) > > > > on the wedged host ? > > > > > > on the wedged host > > > > > > > If BMC stops responding simultaneously with the host, I would suspect > > > > the hardware platform issues instead of a software problem. Do you have > > > > dedicated LAN port for BMC ? > > > > > > Yes. > > > But BMC emulate USB keyboard and this is may be lock inside USB > > > system. > > > "ipmi console don't respond" must be read as "ipmi console runnnig and > > > attached but system don't react to keypress on this console". > > > at the sime moment system respon to `enter` on ipmi sol console, but > > > after enter `root` stuck in login in the '*tcp' state (I think this is > > > NIS related). > > > > ~^B don't break to debuger. > > But I can login to sol console. > > You can probably: > debug.kdb.enter: set to enter the debugger > > or force a panic and get vmcore: > debug.kdb.panic: set to panic the kernel I am reset this host. PMC samples collected and decoded: @ CPU_CLK_UNHALTED_CORE [4653445 samples] 51.86% [2413083] lock_delay @ /boot/kernel.VSTREAM/kernel 100.0% [2413083] __rw_wlock_hard 100.0% [2413083] tcp_tw_2msl_scan 99.99% [2412958] pfslowtimo 100.0% [2412958] softclock_call_cc 100.0% [2412958] softclock 100.0% [2412958] intr_event_execute_handlers 100.0% [2412958] ithread_loop 100.0% [2412958] fork_exit 00.01% [125] tcp_twstart 100.0% [125] tcp_do_segment 100.0% [125] tcp_input 100.0% [125] ip_input 100.0% [125] swi_net 100.0% [125] intr_event_execute_handlers 100.0% [125] ithread_loop 100.0% [125] fork_exit 09.43% [438774] _rw_runlock_cookie @ /boot/kernel.VSTREAM/kernel 100.0% [438774] tcp_tw_2msl_scan 99.99% [438735] pfslowtimo 100.0% [438735] softclock_call_cc 100.0% [438735] softclock 100.0% [438735] intr_event_execute_handlers 100.0% [438735] ithread_loop 100.0% [438735] fork_exit 00.01% [39] tcp_twstart 100.0% [39] tcp_do_segment 100.0% [39] tcp_input 100.0% [39] ip_input 100.0% [39] swi_net 100.0% [39] intr_event_execute_handlers 100.0% [39] ithread_loop 100.0% [39] fork_exit 08.57% [398970] __rw_wlock_hard @ /boot/kernel.VSTREAM/kernel 100.0% [398970] tcp_tw_2msl_scan 99.99% [398940] pfslowtimo 100.0% [398940] softclock_call_cc 100.0% [398940] softclock 100.0% [398940] intr_event_execute_handlers 100.0% [398940] ithread_loop 100.0% [398940] fork_exit 00.01% [30] tcp_twstart 100.0% [30] tcp_do_segment 100.0% [30] tcp_input 100.0% [30] ip_input 100.0% [30] swi_net 100.0% [30] intr_event_execute_handlers 100.0% [30] ithread_loop 100.0% [30] fork_exit 05.79% [269224] __rw_try_rlock @ /boot/kernel.VSTREAM/kernel 100.0% [269224] tcp_tw_2msl_scan 99.99% [269203] pfslowtimo 100.0% [269203] softclock_call_cc 100.0% [269203] softclock 100.0% [269203] intr_event_execute_handlers 100.0% [269203] ithread_loop 100.0% [269203] fork_exit 00.01% [21] tcp_twstart 100.0% [21] tcp_do_segment 100.0% [21] tcp_input 100.0% [21] ip_input 100.0% [21] swi_net 100.0% [21] intr_event_execute_handlers 100.0% [21] ithread_loop 100.0% [21] fork_exit 05.35% [249141] _rw_wlock_cookie @ /boot/kernel.VSTREAM/kernel 99.76% [248543] tcp_tw_2msl_scan 99.99% [248528] pfslowtimo 100.0% [248528] softclock_call_cc 100.0% [248528] softclock 100.0% [248528] intr_event_execute_handlers 100.0% [248528] ithread_loop 100.0% [248528] fork_exit 00.01% [15] tcp_twstart 100.0% [15] tcp_do_segment 100.0% [15] tcp_input 100.0% [15] ip_input 100.0% [15] swi_net 100.0% [15] intr_event_execute_handlers 100.0% [15] ithread_loop 100.0% [15] fork_exit 00.24% [598] pfslowtimo 100.0% [598] softclock_call_cc 100.0% [598] softclock 100.0% [598] intr_event_execute_handlers 100.0% [598] ithread_loop 100.0% [598] fork_exit From owner-freebsd-stable@freebsd.org Fri Sep 16 19:11:56 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A25B8BDDB41 for ; Fri, 16 Sep 2016 19:11:56 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id 8B0EF1E8; Fri, 16 Sep 2016 19:11:56 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id ACC8A17E72; Fri, 16 Sep 2016 12:11:55 -0700 (PDT) Date: Fri, 16 Sep 2016 12:11:55 -0700 From: hiren panchasara To: Slawa Olhovchenkov , jch@FreeBSD.org Cc: Konstantin Belousov , freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160916191155.GM9397@strugglingcoder.info> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160915085938.GN38409@kib.kiev.ua> <20160915090633.GS2840@zxy.spb.ru> <20160916181839.GC2960@zxy.spb.ru> <20160916183053.GL9397@strugglingcoder.info> <20160916190330.GG2840@zxy.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Rl6QTk5rIKeAVhSO" Content-Disposition: inline In-Reply-To: <20160916190330.GG2840@zxy.spb.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 19:11:56 -0000 --Rl6QTk5rIKeAVhSO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable + jch@=20 On 09/16/16 at 10:03P, Slawa Olhovchenkov wrote: > On Fri, Sep 16, 2016 at 11:30:53AM -0700, hiren panchasara wrote: >=20 > > On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > > > On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > > >=20 > > > > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > > > >=20 > > > > > On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrot= e: > > > > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrot= e: > > > > > >=20 > > > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > > > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > > > > > > > Under high network load and may be addtional conditional sy= stem go to > > > > > > > > unresponsible state -- no reaction to network and console (= USB IPMI > > > > > > > > emulation). INVARIANTS give to high overhad. Is this exist = some way to > > > > > > > > debug this? > > > > > > >=20 > > > > > > > Can you panic it from console to get to db> to get backtrace = and other > > > > > > > info when it goes unresponsive? > > > > > >=20 > > > > > > ipmi console don't respond (chassis power diag don't react) > > > > > > login on sol console stuck on *tcp. > > > > >=20 > > > > > Is 'login' you reference is the ipmi client state, or you mean lo= gin(1) > > > > > on the wedged host ? > > > >=20 > > > > on the wedged host > > > >=20 > > > > > If BMC stops responding simultaneously with the host, I would sus= pect > > > > > the hardware platform issues instead of a software problem. Do y= ou have > > > > > dedicated LAN port for BMC ? > > > >=20 > > > > Yes. > > > > But BMC emulate USB keyboard and this is may be lock inside USB > > > > system. > > > > "ipmi console don't respond" must be read as "ipmi console runnnig = and > > > > attached but system don't react to keypress on this console". > > > > at the sime moment system respon to `enter` on ipmi sol console, but > > > > after enter `root` stuck in login in the '*tcp' state (I think this= is > > > > NIS related). > > >=20 > > > ~^B don't break to debuger. > > > But I can login to sol console. > >=20 > > You can probably: > > debug.kdb.enter: set to enter the debugger > >=20 > > or force a panic and get vmcore: > > debug.kdb.panic: set to panic the kernel >=20 > I am reset this host. > PMC samples collected and decoded: >=20 > @ CPU_CLK_UNHALTED_CORE [4653445 samples] >=20 > 51.86% [2413083] lock_delay @ /boot/kernel.VSTREAM/kernel > 100.0% [2413083] __rw_wlock_hard > 100.0% [2413083] tcp_tw_2msl_scan > 99.99% [2412958] pfslowtimo > 100.0% [2412958] softclock_call_cc > 100.0% [2412958] softclock > 100.0% [2412958] intr_event_execute_handlers > 100.0% [2412958] ithread_loop > 100.0% [2412958] fork_exit > 00.01% [125] tcp_twstart > 100.0% [125] tcp_do_segment > 100.0% [125] tcp_input > 100.0% [125] ip_input > 100.0% [125] swi_net > 100.0% [125] intr_event_execute_handlers > 100.0% [125] ithread_loop > 100.0% [125] fork_exit >=20 > 09.43% [438774] _rw_runlock_cookie @ /boot/kernel.VSTREAM/kernel > 100.0% [438774] tcp_tw_2msl_scan > 99.99% [438735] pfslowtimo > 100.0% [438735] softclock_call_cc > 100.0% [438735] softclock > 100.0% [438735] intr_event_execute_handlers > 100.0% [438735] ithread_loop > 100.0% [438735] fork_exit > 00.01% [39] tcp_twstart > 100.0% [39] tcp_do_segment > 100.0% [39] tcp_input > 100.0% [39] ip_input > 100.0% [39] swi_net > 100.0% [39] intr_event_execute_handlers > 100.0% [39] ithread_loop > 100.0% [39] fork_exit >=20 > 08.57% [398970] __rw_wlock_hard @ /boot/kernel.VSTREAM/kernel > 100.0% [398970] tcp_tw_2msl_scan > 99.99% [398940] pfslowtimo > 100.0% [398940] softclock_call_cc > 100.0% [398940] softclock > 100.0% [398940] intr_event_execute_handlers > 100.0% [398940] ithread_loop > 100.0% [398940] fork_exit > 00.01% [30] tcp_twstart > 100.0% [30] tcp_do_segment > 100.0% [30] tcp_input > 100.0% [30] ip_input > 100.0% [30] swi_net > 100.0% [30] intr_event_execute_handlers > 100.0% [30] ithread_loop > 100.0% [30] fork_exit >=20 > 05.79% [269224] __rw_try_rlock @ /boot/kernel.VSTREAM/kernel > 100.0% [269224] tcp_tw_2msl_scan > 99.99% [269203] pfslowtimo > 100.0% [269203] softclock_call_cc > 100.0% [269203] softclock > 100.0% [269203] intr_event_execute_handlers > 100.0% [269203] ithread_loop > 100.0% [269203] fork_exit > 00.01% [21] tcp_twstart > 100.0% [21] tcp_do_segment > 100.0% [21] tcp_input > 100.0% [21] ip_input > 100.0% [21] swi_net > 100.0% [21] intr_event_execute_handlers > 100.0% [21] ithread_loop > 100.0% [21] fork_exit >=20 > 05.35% [249141] _rw_wlock_cookie @ /boot/kernel.VSTREAM/kernel > 99.76% [248543] tcp_tw_2msl_scan > 99.99% [248528] pfslowtimo > 100.0% [248528] softclock_call_cc > 100.0% [248528] softclock > 100.0% [248528] intr_event_execute_handlers > 100.0% [248528] ithread_loop > 100.0% [248528] fork_exit > 00.01% [15] tcp_twstart > 100.0% [15] tcp_do_segment > 100.0% [15] tcp_input > 100.0% [15] ip_input > 100.0% [15] swi_net > 100.0% [15] intr_event_execute_handlers > 100.0% [15] ithread_loop > 100.0% [15] fork_exit > 00.24% [598] pfslowtimo > 100.0% [598] softclock_call_cc > 100.0% [598] softclock > 100.0% [598] intr_event_execute_handlers > 100.0% [598] ithread_loop > 100.0% [598] fork_exit > As I suspected, this looks like a hang trying to lock V_tcbinfo. I'm ccing Julien here who worked on WLOCK -> RLOCK transition to improve performance for short-lived connections. I am not too sure if thats the problem but looks in similar area so he may be able to provide some insights. Cheers, Hiren --Rl6QTk5rIKeAVhSO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJX3EP4XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lHn8H/1xhU1sBwwDrER+AdJdWwrGp SiM06yPhh/7tKt1ouP0omUF4/OoBQonbnyKkNr59UE4N+xVpacTGuQxysb6OE/+c 6GxaDbgoajv2NPHrJ5VZvXV22bcc7nHz4NfArWGQ0HfJZDFum3cDiwm99qj9svUW R5Iy76a2RnW2wB8wKxuQ08lCZ+0eGZzyXV+DJYEvl7LwApPmFgvxmOTWCeenhcAw QFcu3XnAYtpP/FoYP8zFq6hiib/UlyyhZFNWHxuApYvLbLYa9Cwbfn+R77P8K4ns nn42f1ecPyvDDGkq99qyHVCrA2q8b6DWiiZaFIOdRVX5NdWx8pP3tZeMuAA68aw= =eNR2 -----END PGP SIGNATURE----- --Rl6QTk5rIKeAVhSO-- From owner-freebsd-stable@freebsd.org Fri Sep 16 19:35:42 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A2C4BDD49A for ; Fri, 16 Sep 2016 19:35:42 +0000 (UTC) (envelope-from lacey.leanne@gmail.com) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EFFB26D0 for ; Fri, 16 Sep 2016 19:35:41 +0000 (UTC) (envelope-from lacey.leanne@gmail.com) Received: by mail-pa0-x230.google.com with SMTP id wk8so28672048pab.1 for ; Fri, 16 Sep 2016 12:35:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:to:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=jj/sqzXk6pKE5l/J53PNBE8JD3vQ2PRJidTYIrAy3VI=; b=AsZTOcXRVYkiLLYyXvbk9vqIpd8UlZ2Lapr904AGcsSUxa70ygFS6voNFKV3DyQV9K bz7MZVhT7+i/AUY0/WtNSkJcfg+MTKLlCU5g7UMV6B+eKSStkd8HVWqrSnUTOL/5eAAz 599iqDkPtFn5BgqFSVYvcfoZFPROFVuxZdpq/QbFs3YBmgP/jb+kr7cMt8Hs3l5L39QL eq2cOtHP6av0RtuugBFbRdcCqicKrpnYQQ9foEiXeqGtLDEsA3MLtqHfGDR8BFa1TWko R56XaTyLLNXd6Soswu3kpZ2U7yemGlp5DeuWp2iXhhN1azx9BN6/TlC7cmndOGNJ2SwM isqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=jj/sqzXk6pKE5l/J53PNBE8JD3vQ2PRJidTYIrAy3VI=; b=c8I7KONh4vX9i+Wrsq/YExpwzkP/BF2Q8HMca/7WZDSUBEBfykCIBchSev9mVe8aIP RqKsxHpGTHaGl51rQCR7kPum3LZ+RYgglCWt/xiYMjY07qEaF/ghaomCwaOfTCtGvNT9 lrroQ9PYyPA4mpgRsGTB9WpHSPFnAQUtrItUJp79w7XzVxggfaFB/ELVmMpa0z2Mfmd7 PsA/gsbtPcbCzEvXk4Y7IZhuyMUjfSSJ3AuUEFXXyLMWJZe6nRbyYXvOLfKc1VAfwEZO h2FvWt7dlN5K0QU13MlHx18mcZJLHwyDX/sH6BjMoxR+N/kT4FK5XIG3PjiCxVMyaVtr 6TOw== X-Gm-Message-State: AE9vXwM5J+cBfFqj7DFwhRDxMsIneBcfeGHH4B/OYgJ0UJ3d9TTpaKh3MINTUCjHApPWwQ== X-Received: by 10.66.26.232 with SMTP id o8mr25592221pag.103.1474054541357; Fri, 16 Sep 2016 12:35:41 -0700 (PDT) Received: from [192.168.0.197] ([162.247.40.130]) by smtp.gmail.com with ESMTPSA id b64sm54035142pfa.82.2016.09.16.12.35.40 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Sep 2016 12:35:40 -0700 (PDT) From: Lacey Powers Subject: FreeBSD 11.0-RC2 to 11.0-RC3 fetching metadata signature failed To: freebsd-stable@freebsd.org Message-ID: <7f36c233-a7ec-21da-2c14-466993d3568e@gmail.com> Date: Fri, 16 Sep 2016 12:35:40 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 19:35:42 -0000 Hello Everyone, Whenever I try to run freebsd-update to go from 11.0-RC2 to 11.0-RC3, I get the following error: # freebsd-update upgrade -r 11.0-RC3 Looking up update.FreeBSD.org mirrors... 4 mirrors found. Fetching metadata signature for 11.0-RC2 from update5.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/src world/base world/doc world/lib32 The following components of FreeBSD do not seem to be installed: kernel/generic-dbg world/base-dbg world/lib32-dbg Does this look reasonable (y/n)? y Fetching metadata signature for 11.0-RC3 from update5.freebsd.org... failed. Fetching metadata signature for 11.0-RC3 from update4.freebsd.org... failed. Fetching metadata signature for 11.0-RC3 from update6.freebsd.org... failed. Fetching metadata signature for 11.0-RC3 from update3.freebsd.org... failed. No mirrors remaining, giving up. Does this mean that 11.0-RC3 isn't actually out, or is something going on with my machine that I should be looking into? Best, Lacey From owner-freebsd-stable@freebsd.org Fri Sep 16 19:40:02 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51F7FBDD5AC for ; Fri, 16 Sep 2016 19:40:02 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 42D9C8B0; Fri, 16 Sep 2016 19:40:02 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id E0A0C1F49; Fri, 16 Sep 2016 19:40:01 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 16 Sep 2016 19:40:00 +0000 From: Glen Barber To: Lacey Powers Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 11.0-RC2 to 11.0-RC3 fetching metadata signature failed Message-ID: <20160916194000.GL35413@FreeBSD.org> References: <7f36c233-a7ec-21da-2c14-466993d3568e@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PpocKf6TCvdC9BKE" Content-Disposition: inline In-Reply-To: <7f36c233-a7ec-21da-2c14-466993d3568e@gmail.com> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 19:40:02 -0000 --PpocKf6TCvdC9BKE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 16, 2016 at 12:35:40PM -0700, Lacey Powers wrote: > Hello Everyone, >=20 > Whenever I try to run freebsd-update to go from 11.0-RC2 to 11.0-RC3, I > get the following error: >=20 > # freebsd-update upgrade -r 11.0-RC3 >=20 > Looking up update.FreeBSD.org mirrors... 4 mirrors found. > Fetching metadata signature for 11.0-RC2 from update5.freebsd.org... done. > Fetching metadata index... done. > Inspecting system... done. >=20 > The following components of FreeBSD seem to be installed: > kernel/generic src/src world/base world/doc world/lib32 >=20 > The following components of FreeBSD do not seem to be installed: > kernel/generic-dbg world/base-dbg world/lib32-dbg >=20 > Does this look reasonable (y/n)? y >=20 > Fetching metadata signature for 11.0-RC3 from update5.freebsd.org... fail= ed. > Fetching metadata signature for 11.0-RC3 from update4.freebsd.org... fail= ed. > Fetching metadata signature for 11.0-RC3 from update6.freebsd.org... fail= ed. > Fetching metadata signature for 11.0-RC3 from update3.freebsd.org... fail= ed. > No mirrors remaining, giving up. >=20 > Does this mean that 11.0-RC3 isn't actually out, or is something going > on with my machine that I should be looking into? >=20 The freebsd-update(8) builds have not yet completed. Glen --PpocKf6TCvdC9BKE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJX3EqKAAoJEAMUWKVHj+KTCoEQAJLUl5/fdfOHCUuQTKb8UvVN XS86kD6oityXthS+IVfMPDTGLWoKn3MivhoLile4LTs4/xw6S7yntf9IO9pqpKlj WCktuOCRQeY6sNvNPamVZb+/bhysmJ7wGCLPGVomNuGbEOL9UULb56SJ39a57Yer paDVAmYXoNQSMSZO+LXLIfiT5p/1e0Vu/CukTLe8EhfVJaonKccAjhlB0m1c5NYX g8G3RMUqOrRM3HLnT5AgMNPWPMqbtCrESs426aGfz/p4xsW2aBFb2YZb5TwmCX10 UaiEf3S8uX46VzlNU7KZJeGw4QHvNwTcOL024D4xFz8C0dc2wfBibIcrBoVlAMdq rgSaPqQf6OQ6u7m+P9Tt9tloZO9TsIXuDoaS0Thkmirv0sPvbQl2NKS+UAKhMohG 5c+Tx4BE6QT/Nwe1kKc74VuMHJgtiarM00UsdRPz1Ncc3rThg8Xr/coFX68DHQzO muu/Rti2Y+cuLzqiS3Lu30iQNMa16fU5EOe9T9VmkGQKyHr+4xVfhhmuhf07iOtK yzK9cUYalwTAvU61kJ+agRTL5dt4XXBLCKOq3my+htYuTy6xUf1MiweFBZeQoQdg EgGrKcOGVw12FXZxC1XbsPyVc3OpGR16dHpMeKec5FcIM0Gzs9ND1+Lxhh3ma7uf AjjuKruJInx1DxQCGcFr =UNCp -----END PGP SIGNATURE----- --PpocKf6TCvdC9BKE-- From owner-freebsd-stable@freebsd.org Fri Sep 16 20:31:01 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4542BDD1B4 for ; Fri, 16 Sep 2016 20:31:01 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F6A6319; Fri, 16 Sep 2016 20:31:01 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bkzmj-0003U4-7l; Fri, 16 Sep 2016 23:30:57 +0300 Date: Fri, 16 Sep 2016 23:30:57 +0300 From: Slawa Olhovchenkov To: hiren panchasara Cc: jch@FreeBSD.org, Konstantin Belousov , freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160916203057.GH2840@zxy.spb.ru> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160915085938.GN38409@kib.kiev.ua> <20160915090633.GS2840@zxy.spb.ru> <20160916181839.GC2960@zxy.spb.ru> <20160916183053.GL9397@strugglingcoder.info> <20160916190330.GG2840@zxy.spb.ru> <20160916191155.GM9397@strugglingcoder.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160916191155.GM9397@strugglingcoder.info> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 20:31:01 -0000 On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote: > > As I suspected, this looks like a hang trying to lock V_tcbinfo. > > I'm ccing Julien here who worked on WLOCK -> RLOCK transition to improve > performance for short-lived connections. I am not too sure if thats the > problem but looks in similar area so he may be able to provide some > insights. No, this is other case. In may case at this time no network traffic more then hour. This is some sore of deadlock or like. From owner-freebsd-stable@freebsd.org Fri Sep 16 21:46:48 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 593E4BDD250 for ; Fri, 16 Sep 2016 21:46:48 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id 48916DD3; Fri, 16 Sep 2016 21:46:47 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 76CD717F65; Fri, 16 Sep 2016 14:46:46 -0700 (PDT) Date: Fri, 16 Sep 2016 14:46:46 -0700 From: hiren panchasara To: Slawa Olhovchenkov Cc: Konstantin Belousov , jch@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160916214646.GR9397@strugglingcoder.info> References: <20160904215739.GC22212@zxy.spb.ru> <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160915085938.GN38409@kib.kiev.ua> <20160915090633.GS2840@zxy.spb.ru> <20160916181839.GC2960@zxy.spb.ru> <20160916183053.GL9397@strugglingcoder.info> <20160916190330.GG2840@zxy.spb.ru> <20160916191155.GM9397@strugglingcoder.info> <20160916203057.GH2840@zxy.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="F74xYepWx8quU230" Content-Disposition: inline In-Reply-To: <20160916203057.GH2840@zxy.spb.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 21:46:48 -0000 --F74xYepWx8quU230 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 09/16/16 at 11:30P, Slawa Olhovchenkov wrote: > On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote: >=20 > >=20 > > As I suspected, this looks like a hang trying to lock V_tcbinfo. > >=20 > > I'm ccing Julien here who worked on WLOCK -> RLOCK transition to improve > > performance for short-lived connections. I am not too sure if thats the > > problem but looks in similar area so he may be able to provide some > > insights. >=20 > No, this is other case. In may case at this time no network traffic > more then hour. This is some sore of deadlock or like. In my limited understanding, such deadlock like situation can occur without traffic too. Cheers, Hiren --F74xYepWx8quU230 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJX3GhCXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lbWoH/i9AjDz8VZy4LyfaQnA59BS8 SYBBVa0dBb/Oru+ltLUdSnG1YUgUfVDapCBBkAoZj4DBDDjFevzxcKBv3Dz4vDIS Bpj6rOtwyqjzrDE/LG3FmT2Nt68PvKzO/Uk3TpluSvdI70q3yr9pzQAmGrAwsIz3 E706nb2fEecETnYP11kwrc9HPyPKJqIA2vOpvg7u5Ixa2PhdtfKrEUycD9Na8pMN qug3UxlhR01w9VMUk7PGyIKc1VvI/RP0hFCIsR8hYdh37vDrPUYDwWOrOjzT+VMR o8S0AItFzScO4Iw4igUQ6WnopGXvAx+ubR1Qpaomr3Lwd1cumLYvTlRWn3GyWCs= =JFDK -----END PGP SIGNATURE----- --F74xYepWx8quU230-- From owner-freebsd-stable@freebsd.org Fri Sep 16 21:48:50 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1319EBDD30B for ; Fri, 16 Sep 2016 21:48:50 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id 02B3CF06; Fri, 16 Sep 2016 21:48:49 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 2129B17F6E; Fri, 16 Sep 2016 14:48:49 -0700 (PDT) Date: Fri, 16 Sep 2016 14:48:49 -0700 From: hiren panchasara To: Slawa Olhovchenkov Cc: Konstantin Belousov , jch@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160916214849.GS9397@strugglingcoder.info> References: <20160905014612.GA42393@strugglingcoder.info> <20160914213503.GJ2840@zxy.spb.ru> <20160915085938.GN38409@kib.kiev.ua> <20160915090633.GS2840@zxy.spb.ru> <20160916181839.GC2960@zxy.spb.ru> <20160916183053.GL9397@strugglingcoder.info> <20160916190330.GG2840@zxy.spb.ru> <20160916191155.GM9397@strugglingcoder.info> <20160916203057.GH2840@zxy.spb.ru> <20160916214646.GR9397@strugglingcoder.info> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="uWKIjLx9zRJNHvcs" Content-Disposition: inline In-Reply-To: <20160916214646.GR9397@strugglingcoder.info> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2016 21:48:50 -0000 --uWKIjLx9zRJNHvcs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 09/16/16 at 02:46P, hiren panchasara wrote: > On 09/16/16 at 11:30P, Slawa Olhovchenkov wrote: > > On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote: > >=20 > > >=20 > > > As I suspected, this looks like a hang trying to lock V_tcbinfo. > > >=20 > > > I'm ccing Julien here who worked on WLOCK -> RLOCK transition to impr= ove > > > performance for short-lived connections. I am not too sure if thats t= he > > > problem but looks in similar area so he may be able to provide some > > > insights. > >=20 > > No, this is other case. In may case at this time no network traffic > > more then hour. This is some sore of deadlock or like. >=20 > In my limited understanding, such deadlock like situation can occur > without traffic too. Err, I meant to say light traffic. Cheers, Hiren --uWKIjLx9zRJNHvcs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJX3GjBXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lp6EH/0n++W/+uIF17UNuzUwgKZ6E z6WnGI61fXbA7sEhIGcUt7O7atyrd6XDSsr/Tdh1VIdDEHIVD35q5ko3KvxP/RNW hAskDn/pBTBmhHS04WJYp9ThOz9kwnYBSbFti3Gsq9iI0qwVK6Jj79KhYChoAQbR GjRfmWna/2xwIJkILtO8+pDEJkgVZQF4xq+Tuj8MLGL4tG+MfBx5cuTe4S1etBTU yRaIRmkJW6sWRPvnlkgEJybZTzdW2jlVt9EqpGVGq6odT7Zh82vgLaXLbtLko4HH 6n6M38Tve45tYWe1a2ZY+uDlQUhPEunMKB6lColNstkBBBc0p5e6BO8uBjDF/5A= =IL0t -----END PGP SIGNATURE----- --uWKIjLx9zRJNHvcs-- From owner-freebsd-stable@freebsd.org Sat Sep 17 14:27:47 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F8F2BDE965; Sat, 17 Sep 2016 14:27:47 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 93662C51; Sat, 17 Sep 2016 14:27:47 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 4847B17C1; Sat, 17 Sep 2016 14:27:46 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Sat, 17 Sep 2016 14:27:46 +0000 From: Glen Barber To: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Cc: FreeBSD Release Engineering Team Subject: FreeBSD 11.0-RC3 Now Available Message-ID: <20160917142746.GA26765@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 17 Sep 2016 14:27:47 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The third RC build of the 11.0-RELEASE release cycle is now available. Installation images are available for: o 11.0-RC3 amd64 GENERIC o 11.0-RC3 i386 GENERIC o 11.0-RC3 powerpc GENERIC o 11.0-RC3 powerpc64 GENERIC64 o 11.0-RC3 sparc64 GENERIC o 11.0-RC3 armv6 BANANAPI o 11.0-RC3 armv6 BEAGLEBONE o 11.0-RC3 armv6 CUBIEBOARD o 11.0-RC3 armv6 CUBIEBOARD2 o 11.0-RC3 armv6 CUBOX-HUMMINGBOARD o 11.0-RC3 armv6 GUMSTIX o 11.0-RC3 armv6 RPI-B o 11.0-RC3 armv6 RPI2 o 11.0-RC3 armv6 PANDABOARD o 11.0-RC3 armv6 WANDBOARD o 11.0-RC3 aarch64 GENERIC Note regarding arm/armv6 images: For convenience for those without console access to the system, a freebsd user with a password of freebsd is available by default for ssh(1) access. Additionally, the root user password is set to root, which it is strongly recommended to change the password for both users after gaining access to the system. Installer images and memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/11.0/ The image checksums follow at the end of this e-mail. If you notice problems you can report them through the Bugzilla PR system or on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the "releng/11.0" branch. A summary of changes since 11.0-RC2 includes: o A boot issue affecting booting from large volumes has been fixed. o A boot issue affecting powerpc/powerpc has been fixed. o Debugging options have been turned off for arm64/aarch64. o The libarchive(3) library has been updated. o The cron(8) utility has been updated to include a bug fix. o An ipfw(4) 'set enable/disable' bug has been fixed. o The arm64/aarch64 kernel has been updated to print a warning when running on pass 1.1 hardware. A list of changes since 10.0-RELEASE are available on the releng/11.0 release notes: https://www.freebsd.org/releases/11.0R/relnotes.html Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 11.0-RELEASE cycle progresses. === Virtual Machine Disk Images === VM disk images are available for the amd64 and i386 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD FTP mirrors): ftp://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/11.0-RC3/ The partition layout is: ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VHD, VMDK, and raw disk image formats. The image download size is approximately 135 MB and 165 MB respectively (amd64/i386), decompressing to a 21 GB sparse image. Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI loader file is needed for qemu-system-aarch64 to be able to boot the virtual machine images. See this page for more information: https://wiki.freebsd.org/arm64/QEMU To boot the VM image, run: % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \ -bios QEMU_EFI.fd -serial telnet::4444,server -nographic \ -drive if=none,file=VMDISK,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -device virtio-net-device,netdev=net0 \ -netdev user,id=net0 Be sure to replace "VMDISK" with the path to the virtual machine image. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: us-east-1 region: ami-6e6f1d79 us-west-1 region: ami-b03679d0 us-west-2 region: ami-64f02204 sa-east-1 region: ami-5637a73a eu-west-1 region: ami-e47c0597 eu-central-1 region: ami-af7082c0 ap-northeast-1 region: ami-57469036 ap-northeast-2 region: ami-e43bee8a ap-southeast-1 region: ami-023fe561 ap-southeast-2 region: ami-75a39216 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-11.0-RC3 % vagrant up === Upgrading === The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 11.0-RC3 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 9.x. Alternatively, the user can install misc/compat9x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == o 11.0-RC3 amd64 GENERIC: SHA512 (FreeBSD-11.0-RC3-amd64-bootonly.iso) = b427221da0649adb6dbffd121d3a65dd1c0f32998a9e56b63f51329a44b7d31260b7a7d5fc27ca9e9cc34340062981adfb1771f3ab6cc03b02032b573b0042ab SHA512 (FreeBSD-11.0-RC3-amd64-bootonly.iso.xz) = 3f4786d4058a66506d1f5248b222498ed214eac5d71267f5b2e6da60b15cb770da67c0342574a2b2e181d37a9ecd41b83da9c735d48ff51747e170dd8be8b04e SHA512 (FreeBSD-11.0-RC3-amd64-disc1.iso) = a51de951faf0a866abb3fe7d03c07bd4a894f078eeb2b13a4997ac4b940fd6c0f65f75a77076649d8c8fc1421f7d226e40bcf6dc8058a5ca6b0ec8597cbb4fac SHA512 (FreeBSD-11.0-RC3-amd64-disc1.iso.xz) = 5e02f37f0a8110898a767d077d4a6384e236f51cd3f407d91a78dac8178ab7b10e80b04e44ef59a228b0b533f9e103c6f40b922edccbf276e05ad20f5d8faffd SHA512 (FreeBSD-11.0-RC3-amd64-dvd1.iso) = 6838a3763d74e1485a6653195877926d1e9cd2933503cc36aaf8ae093f64831f91de3f0370dfa5c92ce27062a8836c1a5f3b9d0d9a2945c5cf49578599b00b51 SHA512 (FreeBSD-11.0-RC3-amd64-dvd1.iso.xz) = 2312ab6a693c82025883012add0a20cf6ad091b594bd25a4e21a3885248869aa82bd713b40851929002c406d0eb92eb7f7a9263d7530b9c412d7d81932ee4a36 SHA512 (FreeBSD-11.0-RC3-amd64-memstick.img) = 09201c3d47a03fe76adb436ee72ff27952ecfe212201d412221bc3745d31056c7fd8ec87936b93a1af72b31fe1fddf7071332242b587a4f8989e08b1c29fd96b SHA512 (FreeBSD-11.0-RC3-amd64-memstick.img.xz) = f4b6eb7a911db5ea918fe6dc6e486fb626169d00167245554d1b74065e30faa11039cab9f4944c68d406c19f2551fbe537aa906feb0e09daef4018d1d6600292 SHA512 (FreeBSD-11.0-RC3-amd64-mini-memstick.img) = a3e29d3c36d907add6703dc547125e9981508290d041f1939c64dff16d5e9c840c9f8c3c2890ca9a339ba7be42a9cd33fc22550d5929ecaa739172b41f4f2bfc SHA512 (FreeBSD-11.0-RC3-amd64-mini-memstick.img.xz) = 7ad35857243a44da7ecf43be307cb56164a69f07655eb9d3c372ac9ce355ffa6c049c39270347126050eeab10aac038626688d8f98194dc9f579e6db3fcf9adc SHA256 (FreeBSD-11.0-RC3-amd64-bootonly.iso) = ee9e5cebbd351b0e63a2cbe3dacb7667ee16a01feaf18fa78e8e3c45061c7934 SHA256 (FreeBSD-11.0-RC3-amd64-bootonly.iso.xz) = 025234eb3083d0c9b58fd41eb7adcaaa7df6b68a8a628e3c31e817ef4065378b SHA256 (FreeBSD-11.0-RC3-amd64-disc1.iso) = e3181c26038c2e7ff3065389e26e617bc0e120c496c458b2a351ffa76fdcafc8 SHA256 (FreeBSD-11.0-RC3-amd64-disc1.iso.xz) = f6ade521d7eb18ea66de77ded7873d25eb88bb81b581c9cd5a17d7ba9a93b8e9 SHA256 (FreeBSD-11.0-RC3-amd64-dvd1.iso) = 2cba19d56b45ca952fe2291115b898c45652ec87b2fb3d0b1178d30d2fc01ac6 SHA256 (FreeBSD-11.0-RC3-amd64-dvd1.iso.xz) = 06b5f46dcf7247c0267b9da66678658ed0415c85beb4cf3af79a1771f7a214ed SHA256 (FreeBSD-11.0-RC3-amd64-memstick.img) = 9413b302ba505271adc09a6ac4979d5e5db47ec9a1f75c35e8a58f97c85057f7 SHA256 (FreeBSD-11.0-RC3-amd64-memstick.img.xz) = f0900c95d985240f3d99e04abe1683af3dc093f6b5ecaf0511fabb81b8860b33 SHA256 (FreeBSD-11.0-RC3-amd64-mini-memstick.img) = d342ef430ceb925b0d5c30c6ddd25d8e57627957cf4d0e201a7933341369c534 SHA256 (FreeBSD-11.0-RC3-amd64-mini-memstick.img.xz) = 576e434158d21823046796146c64b664d894f71ebbe472ad59321de18aa358e4 o 11.0-RC3 i386 GENERIC: SHA512 (FreeBSD-11.0-RC3-i386-bootonly.iso) = 338acf5fff44b865cf02ea528d50fa3bce5ad1ad5f2e586ab8f0c4877e0762c65dcb48f29e3b9013b7e3511238b3f61dbeab941f8821e4a2e749b9821d1e8104 SHA512 (FreeBSD-11.0-RC3-i386-bootonly.iso.xz) = 1c1e5fd2b65b388cebb66d88e51cb506173f72400440a3c7103f602bb8f269248cd6685e56367ed47077b094affb6d864515476a59696a3404764b1b4385b69e SHA512 (FreeBSD-11.0-RC3-i386-disc1.iso) = 67576f127fc0c436cde9cfd0cd5c7c2f922702c890b88663bb10293bcf6ae0d77cd8e09addc837a1d065d074325b85f8107be483ec05995c6044055865f3e3c8 SHA512 (FreeBSD-11.0-RC3-i386-disc1.iso.xz) = 4707c1028113d28ba15d9eb4332bc7df9e24eb55303b5914eb1e82dd53c846ce8d53ee4cbc38ecf7cd1d4eb728518e8ce815aa7ac545e4abda6fd1341d18600c SHA512 (FreeBSD-11.0-RC3-i386-dvd1.iso) = 2bd76433ff692443e76a68d5c587c107d920f23d9c8fa5e959dc314707c41cad82b1765e15a2db986ed53f12f3d7638078c43b053f35fd8ac0a8118f93173f55 SHA512 (FreeBSD-11.0-RC3-i386-dvd1.iso.xz) = 6c5ea4fa3e13f28a453ecb22a1ca33c5bacf4b5c7f1b348224bff528396675558304793b79ca18fdbc2c1e1faef42076bb09669705129f9f84349724556d8713 SHA512 (FreeBSD-11.0-RC3-i386-memstick.img) = 20ec56cb6da70f3c22efedbbb5c6ffcfccb9f6d6e8389012b7b2587509e1bbd97358b3a182f4ed752683714ee2f393c8ea43a64b6620338bdd862f0379e9c7d8 SHA512 (FreeBSD-11.0-RC3-i386-memstick.img.xz) = 045e76b136c08e5fb421752b439da7c99a8df91af51dc68b31d748c35032275afde2744ad18b3c61d86240cba4065011d38492c3f8bc8c6691805185eac999b0 SHA512 (FreeBSD-11.0-RC3-i386-mini-memstick.img) = cd5c37754269951e2d4630a3883c85cff2bc4afec5c9f7affafddd719c30ec6655098a3eb905f9967b22a6371b18777eac134ed6895473251b24b08032bb63d3 SHA512 (FreeBSD-11.0-RC3-i386-mini-memstick.img.xz) = b576ff7fa8c84d5e075b6a7165d8600f677b615c10d7d34e998d4a4b61de75f01251aa5a90474325381ab08eacc1626bc60582d35e9110626fca1000515618c6 SHA256 (FreeBSD-11.0-RC3-i386-bootonly.iso) = c4087f8422bd92ef210b021f9e994a425cccf7dda396a87aa072f501424e0a67 SHA256 (FreeBSD-11.0-RC3-i386-bootonly.iso.xz) = 0adbe5c296a35d4ab9b20454cfa54c4a26701e78c2748f6c619b627589eb4b30 SHA256 (FreeBSD-11.0-RC3-i386-disc1.iso) = 4ee5cf168b8f7b37cc97813866a207f634c3a838b2f1b1cac2e18aa307bc012a SHA256 (FreeBSD-11.0-RC3-i386-disc1.iso.xz) = ab9d6d9365de644a592dd803580e1d98fc1ba9a02cf6adb92a0642be2a57b37e SHA256 (FreeBSD-11.0-RC3-i386-dvd1.iso) = 19076848dd8003c86928e9cb7f13c60e82db39dcc63d3f2b545676da68fd2650 SHA256 (FreeBSD-11.0-RC3-i386-dvd1.iso.xz) = 063ce49668c351ecd51713ffe1c7f6fb32f82f1097140d591bb555c5e1330b5a SHA256 (FreeBSD-11.0-RC3-i386-memstick.img) = 9fd11955f9a3096ac1ad5cbb271125fa73ed0694feec01222768a009a6ccef9c SHA256 (FreeBSD-11.0-RC3-i386-memstick.img.xz) = e877690dda328731ec2ba8f87bba44be0b68d19fc4b7a9737b40e4c896d3cd2c SHA256 (FreeBSD-11.0-RC3-i386-mini-memstick.img) = 49da228e725fa321518b34135f663e38b34b268c8399fe08acd8acee741de900 SHA256 (FreeBSD-11.0-RC3-i386-mini-memstick.img.xz) = 1a8328355dc37b61f00faa152dfc632e0fa4c729bf2abb5f3302605924217087 o 11.0-RC3 powerpc GENERIC: SHA512 (FreeBSD-11.0-RC3-powerpc-bootonly.iso) = 9aef67ef9215d29f4310c6843d008331a3dd4ad6bb6341c15554383f5013545de051e692a1bb5c65455d16e1e24e10a4afc1c24e549ea189247018c867a26e4f SHA512 (FreeBSD-11.0-RC3-powerpc-bootonly.iso.xz) = 28dea0238163281bd7bde6bd879fd497a9b317625d57eef5b35c293078035f2a5ec79d9d8aa3e910e512a98576517ce7d906aed7511b56c5e421abfd13a2331f SHA512 (FreeBSD-11.0-RC3-powerpc-disc1.iso) = 84d6a83e0b52237c952cf76e2580a56428ddd2ca4bd284868e784829465bc197d0a4709fc5709a96115c30f9dc40360b1363592fcf377cd9c9d64bf809dc7ef7 SHA512 (FreeBSD-11.0-RC3-powerpc-disc1.iso.xz) = 77a1f7e611a69d29de35eccc1353811ab00f293f03ca575ec6a42e49b0ad9fa16dc34b9bc271714442aa3e7cd9dc58409d9192e43e2d1c16555ea98f78f91077 SHA512 (FreeBSD-11.0-RC3-powerpc-memstick.img) = 4403d543666ba645a73b626512c1221bfe4f4aa9756991e852e58708edcc7c281576bd5edfa5eedb5e266e88a4473a98cca16af9861f1256c51192db6b6a1003 SHA512 (FreeBSD-11.0-RC3-powerpc-memstick.img.xz) = 39d3e8e140afcc8782f74ee844bd4cb1185a51724a136dbabf33173620668bd6b8b828c1d1809c52f5e93bf0a6df040a82f6148923214bf0983e6e90ce7f83b3 SHA512 (FreeBSD-11.0-RC3-powerpc-mini-memstick.img) = e122e16902a1d48e441d56717e02926c758af84c46814bfaa71b3ab46a4e2e4385216addbf1e49e86ee849fe02a2579b956bc3c2d0b0bb796fb4ddfa04b66db1 SHA512 (FreeBSD-11.0-RC3-powerpc-mini-memstick.img.xz) = 29eb0171b0f05216be0a24f75250309c62558ce57909300ae9d3deb91ba8c960a98885b993737679ece59673df0a4aee18fe417211be4e91939899152cf0edc0 SHA256 (FreeBSD-11.0-RC3-powerpc-bootonly.iso) = 29b7792b17a81b83b743cf22683083974e36c87bb8a0b9b5cb6179de56b004e5 SHA256 (FreeBSD-11.0-RC3-powerpc-bootonly.iso.xz) = 00dcd2f7fd6a2851210444b8332dc4f880307675e824aed85966aae568464d2b SHA256 (FreeBSD-11.0-RC3-powerpc-disc1.iso) = dd116295d309bc70752783201cfb57b27d3b89ba91b9a29f32fc406e03c9ca5c SHA256 (FreeBSD-11.0-RC3-powerpc-disc1.iso.xz) = f3f3dcd5112967646ef1c1aac24724fb0916feea54b15d516b5367cc202417f9 SHA256 (FreeBSD-11.0-RC3-powerpc-memstick.img) = fab751ada809b80fe1d38250ddd3a1d2f1897a5b9562fd1c3ae613545b807526 SHA256 (FreeBSD-11.0-RC3-powerpc-memstick.img.xz) = 151e31e836e76d5273c5b4618c03b55b628450df61ad8942e2a2aaa84a78c45d SHA256 (FreeBSD-11.0-RC3-powerpc-mini-memstick.img) = 558fbcd2d9ca7e142b1dc4f2ba9a5a510895c8fb78d79f5cf9422cab4738f388 SHA256 (FreeBSD-11.0-RC3-powerpc-mini-memstick.img.xz) = b8c2e02d91c777f0a6f26aaf5ce2c88adf978a4798fbf1891e7487de0c445294 o 11.0-RC3 powerpc64 GENERIC64: SHA512 (FreeBSD-11.0-RC3-powerpc-powerpc64-bootonly.iso) = 7a586a47368ee0ff452b8f0ef6df0c467cd9ae362d77f8c5ced0d74d62010e6c9b0fc2f6717614ad55ed8aa8c43ecd0f4eb67c83fd2004111b6443d403d936a9 SHA512 (FreeBSD-11.0-RC3-powerpc-powerpc64-bootonly.iso.xz) = dbefdbbaba2a4adbc490dc48e7dc609f572a344c5d9ff8950388c02546398d26a30b511ce5e582d30d4001a0e688437bbb843e489199a1021845fa1214595e9d SHA512 (FreeBSD-11.0-RC3-powerpc-powerpc64-disc1.iso) = 21bb0498493f8e66f4ffbe24db76185e3c3c455be0f08acdbc9b961b222671f01582015f995565b043f56d98f1b1bc48c56404343eedaccbed8e53bea3355a7e SHA512 (FreeBSD-11.0-RC3-powerpc-powerpc64-disc1.iso.xz) = a42dbbb455dd46cf19611dc8fba1ac9663b3951f80a98d7518f588fda96a942e8d149eb958ebb4256c68635909fb7c1f682bb398926ec4f8b877d66d5151f9e1 SHA512 (FreeBSD-11.0-RC3-powerpc-powerpc64-memstick.img) = 710dac83df3031b97e7d68a818a264a17dbc7e376f2ebb7ed0109508f11e22577711b4b94dcbac363bcaf369f7ff05da293f09600c4795f53ac51c015df6b8b8 SHA512 (FreeBSD-11.0-RC3-powerpc-powerpc64-memstick.img.xz) = 95b407424223af360e096de9746ace10cde21d17c910167723f4c6069770537cd65c6f682000d8559826d4529573fbcb2d84ca26ea244c41ccc17d327fca158e SHA512 (FreeBSD-11.0-RC3-powerpc-powerpc64-mini-memstick.img) = 84e3b1ed6fe8534f42f1c228d4d05be6da07c0c19204df0978102cf86d461f85ba8ce7bc3a4fb8e512e862185b1829ee7b6168e27b34f1bb0702a560ec042816 SHA512 (FreeBSD-11.0-RC3-powerpc-powerpc64-mini-memstick.img.xz) = 136169c04b6aee368920e4b36d67704660cdaf1c6eda5e6b2fd3f92b17eed59205b1cfeed13280fc8fa1351c4ef606445d239daf9925a08ef1717bcc2dc9143c SHA256 (FreeBSD-11.0-RC3-powerpc-powerpc64-bootonly.iso) = 5bf1cfcab2fa5498daadd2ec5982cd205f9522e8d362f3db2fa3f460cf4ec280 SHA256 (FreeBSD-11.0-RC3-powerpc-powerpc64-bootonly.iso.xz) = 49d675f444d30869440ed56ae17b12a1174a02056b37b944e94d4ed6d35833bc SHA256 (FreeBSD-11.0-RC3-powerpc-powerpc64-disc1.iso) = c0290bd32feaaa3999827545ae5cb747a2c81da6aab17012970eeee518d55228 SHA256 (FreeBSD-11.0-RC3-powerpc-powerpc64-disc1.iso.xz) = b5347d5e09b588e22a3c3719750e3272937f029bc89270daee7af971bc5ba624 SHA256 (FreeBSD-11.0-RC3-powerpc-powerpc64-memstick.img) = b5d7814a364d60771acd56ce14a66ec5f83d8e0005eb95fc444675b383d68f37 SHA256 (FreeBSD-11.0-RC3-powerpc-powerpc64-memstick.img.xz) = c32bb2aa4c14ba551d732492a728e25a90a768794790b358c0a9260926a7d046 SHA256 (FreeBSD-11.0-RC3-powerpc-powerpc64-mini-memstick.img) = f34fb0b73d82efae31df0dff5cf686b47c0fba53e704e6efbc8d3a2239301989 SHA256 (FreeBSD-11.0-RC3-powerpc-powerpc64-mini-memstick.img.xz) = feca4df46cc2d1da322225638b3391a13a5f0d97423d63f47047773351f238df o 11.0-RC3 sparc64 GENERIC: SHA512 (FreeBSD-11.0-RC3-sparc64-bootonly.iso) = 2a6dba661b62a52b1f55d8bd81bc40c038eebc9a7334017e7e6239cb89d327dd77c371dca5209da772b77bf289b858c8d2ecbf86a44365fed5d713b9bd542c2e SHA512 (FreeBSD-11.0-RC3-sparc64-bootonly.iso.xz) = 64de2c617216c42d778d0c2da583722f92d26c05b336bcd4d6716985de38fe0e52f3a42d52b78f0271617f671dac412eaf93c9aa919123e627cb863bb3576b7c SHA512 (FreeBSD-11.0-RC3-sparc64-disc1.iso) = ecfb9a2492eed77a8a2f4f31eb18e00cd85425a6a4edef493ab4e90621b8fe8d24aa85f0d3613099b70cb81b33dddf1492d2440fce7af97481088504420d3f59 SHA512 (FreeBSD-11.0-RC3-sparc64-disc1.iso.xz) = 649d9d2c95b29b17b12c320cb6c9ca73667dfb295818521eb9fcdf579d659616533ea09de5f8ec804565ff47882461085bbc2980b25aa071d8405cc781b90601 SHA256 (FreeBSD-11.0-RC3-sparc64-bootonly.iso) = b5182e26bd574ff0d7d8fcd847eaa90ad27d37029440f585b3bd4ef6bfb6370e SHA256 (FreeBSD-11.0-RC3-sparc64-bootonly.iso.xz) = 8c02c8dfaecebb1c84b9ab2fe6e341c248d017976253106cd37d3525ef850ef2 SHA256 (FreeBSD-11.0-RC3-sparc64-disc1.iso) = 5ae9fc75687933dd8c3b07506e290a1ef75a655512a427b66b0d11f308638122 SHA256 (FreeBSD-11.0-RC3-sparc64-disc1.iso.xz) = 0826e5c9e231a10f47c70b7664f3ac72340af39cc9eaa2c43472836aa3de7dca o 11.0-RC3 armv6 BANANAPI: SHA512 (FreeBSD-11.0-RC3-arm-armv6-BANANAPI.img.xz) = 8c5be2a8cb041b3923092cfacf9d272de7d569ac2019f9064985eb33cd228d691807a3e70ed48f3190debee4eec7f41dd7be5a78cd00ff674683d4460d23fa3e SHA256 (FreeBSD-11.0-RC3-arm-armv6-BANANAPI.img.xz) = 9d2467fdb1c5969a0f6593d2af4c9fb265e0745c27031642a2bd252d5b4c5c61 o 11.0-RC3 armv6 BEAGLEBONE: SHA512 (FreeBSD-11.0-RC3-arm-armv6-BEAGLEBONE.img.xz) = bd0bdd044fa77a508dbb0634577e558d04d25429b24517fc994adbaddf65e075d82ba5eb50bc5fe8bc244a7555635b3896fe824b7cd0cfba8293c7050278575a SHA256 (FreeBSD-11.0-RC3-arm-armv6-BEAGLEBONE.img.xz) = 08f00d5cc99395c324ddacf10a0ecd6f8996fa56e2a3d36640a616ed4e6e9830 o 11.0-RC3 armv6 CUBIEBOARD: SHA512 (FreeBSD-11.0-RC3-arm-armv6-CUBIEBOARD.img.xz) = ffe43d069d0263fdf2c1831a5d799c8edece2afc9a86d255cb0acdcb3e75c2a4625e0f5f27fffd09d7cabeb45699ade4a5e85269d19f15d96fbd59efa5dcd032 SHA256 (FreeBSD-11.0-RC3-arm-armv6-CUBIEBOARD.img.xz) = 9350034b1a6d3ef27a83a17c0ff7e811856ab06e15754c299537d58eb89e2704 o 11.0-RC3 armv6 CUBIEBOARD2: SHA512 (FreeBSD-11.0-RC3-arm-armv6-CUBIEBOARD2.img.xz) = 222d4689af43a51545f194b9e0d83fd58308c4a5a77372989a0f9d4a3d5c0df1aa16435c77cbc26aa34646719746db67340a9cdd66b4979bb91f830ad0560c18 SHA256 (FreeBSD-11.0-RC3-arm-armv6-CUBIEBOARD2.img.xz) = a6e513f1baec454ecb0ed9d41df6a7c2374b00da17f6d3ad4cb30cd1ed3280e5 o 11.0-RC3 armv6 CUBOX-HUMMINGBOARD: SHA512 (FreeBSD-11.0-RC3-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) = bb90b6c836294b5e3ff51333e0f834605637d980fe1f96afbb3e1822f95416d4933b94f83f865b625461c5bc403369efb6aaf19e90ea70a689dfefd2b61c9169 SHA256 (FreeBSD-11.0-RC3-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) = 504e1f88169f15b240cacf3ec4000d027fb7ab55ba11dd1387e505ea298e46cf o 11.0-RC3 armv6 GUMSTIX: SHA512 (FreeBSD-11.0-RC3-arm-armv6-GUMSTIX.img.xz) = d09379fe9e6492177b30e9fdc3ebaf62f17e237fcdc0cc9b7d7a9fe60d174fe36db10ccc2d6741bb5042d657c0978ab80e839084fb5b7430722db05e27e0b98b SHA256 (FreeBSD-11.0-RC3-arm-armv6-GUMSTIX.img.xz) = 4a61003ecaa7faad1800877e1f67ef1c2fb04a0f74571e0de99710ee665bc1f2 o 11.0-RC3 armv6 RPI-B: SHA512 (FreeBSD-11.0-RC3-arm-armv6-RPI-B.img.xz) = a23fa704b628ccdc356588b131ec6bff1aee00b2cd818c0cbef075afa778f52774079e655d2dde3b3a58d5ab161b5e77000b76bd3a5326f678bec4e6b464785d SHA256 (FreeBSD-11.0-RC3-arm-armv6-RPI-B.img.xz) = 770b0353de5ea12bded518a03c7e6d012ade02a9e21ff0a30b536468497d4922 o 11.0-RC3 armv6 RPI2: SHA512 (FreeBSD-11.0-RC3-arm-armv6-RPI2.img.xz) = 2cafafdeeda59f8e48e231d83a988fb533e3e11e206859c8ad86c68219b802d4f5091f05fbdd5637a544ded34faf068598ddef637b4eb39adddc78008b016c6a SHA256 (FreeBSD-11.0-RC3-arm-armv6-RPI2.img.xz) = 3b7f1a8ce9e89e929e95af1717846e0da9ed78be4e5aad96c0dc8072098de896 o 11.0-RC3 armv6 PANDABOARD: SHA512 (FreeBSD-11.0-RC3-arm-armv6-PANDABOARD.img.xz) = a614f26389fa6c39a8c0ba1410f50437f797c606a7a62e4ba0b51b6c3fdb7bc28a36d343b6b952f7ea551593f36ddcd99699337dcbfb83ebbd33c2d429eeac62 SHA256 (FreeBSD-11.0-RC3-arm-armv6-PANDABOARD.img.xz) = 52cd067981685023aa54e52b9df0eb98bdce3b058e6e9ac8026e0f0b782f0d03 o 11.0-RC3 armv6 WANDBOARD: SHA512 (FreeBSD-11.0-RC3-arm-armv6-WANDBOARD.img.xz) = d2bcf6575e287f35c32b7a4a03fd345622568771311dd1fe28faeee19d39fa2213fa7c620b46cc56495db403fc0722f3121eabce829aada28cea4765f7cd0cfd SHA256 (FreeBSD-11.0-RC3-arm-armv6-WANDBOARD.img.xz) = 2f443310adfd9d1ac94dd27aeea9dc4a75cadf460ffa99ff24df805567e6357f o 11.0-RC3 aarch64 GENERIC: SHA512 (FreeBSD-11.0-RC3-arm64-aarch64-memstick.img) = 5a2c4d608510edd8d4eacbd4b4ab1ec309ef1e3ac157d1a9fffd85c5f781df29ce81e6f95206c5f9ce7dc1a75f55f61dfe981790c2a7c7e0326e5a4ed0fcb4f7 SHA512 (FreeBSD-11.0-RC3-arm64-aarch64-memstick.img.xz) = b7c4ec6f444a9152109804651407b4fcdb20916fd7aca2a16165c4071312dc0823c82b29a1ec3a771d4f0bf7c0eb97f4317a3334c73bcd846c76c6e65271a044 SHA512 (FreeBSD-11.0-RC3-arm64-aarch64-mini-memstick.img) = a0969b45ac7a50d538fa351d8e3b6582031963fc94e8d85e657320136759c95cf633ac38ffb771de26cb1c7cd52469e92bb2d16192508a18beca4755aad7d84f SHA512 (FreeBSD-11.0-RC3-arm64-aarch64-mini-memstick.img.xz) = 54ced0316658dd4d36febaa8addb52b08001219a231ba0fe994f0664b677bf7260c81118ada8bd3e7c1da579a284ea842bd3afb280bf7943669a07868d60c4b6 SHA256 (FreeBSD-11.0-RC3-arm64-aarch64-memstick.img) = 74342b7b7b6f583c50b432d8ce0ed95f7a654ffc2bd0c3af2a3577b238600900 SHA256 (FreeBSD-11.0-RC3-arm64-aarch64-memstick.img.xz) = df4dac8287ade9a0a41741a999948722ddd9016f8574841241e4f07aa483aaf7 SHA256 (FreeBSD-11.0-RC3-arm64-aarch64-mini-memstick.img) = 5c056cfee4a1b6f012e4ad3ff3f97dd1c53fa15e7de4f9003a2ca2174d3e7a54 SHA256 (FreeBSD-11.0-RC3-arm64-aarch64-mini-memstick.img.xz) = 1a0ebe9059b98ee7c4044198c0df94a0232fadfe1d6e8d5674d88ac60ec12746 == VM IMAGE CHECKSUMS == o 11.0-RC3 amd64: SHA512 (FreeBSD-11.0-RC3-amd64.qcow2.xz) = 43720fd63a32687e29a09081bd341ec7d63bd5723b2a17d465b2ff5b560d68b47deb64c530327bee594f14dd91eb8cd9db72ec0bb8c831496d54af4feb99d67b SHA512 (FreeBSD-11.0-RC3-amd64.raw.xz) = 272bc124b41b2a79288a263dd6865899d91d89472c5511db2659a5104c83ca97d370077148bfda99114b1fdea09dc0371def49a6db259902107e2f2a335a6dbb SHA512 (FreeBSD-11.0-RC3-amd64.vhd.xz) = 340bb16001e47f8d0df8209e2d7dce7c1fe77dc5b01953bb8cc9d0a1d1b41fe9cdedf9503d44b66788329715b8c8a71bc8ff85eedceae7eab426a04c927260cb SHA512 (FreeBSD-11.0-RC3-amd64.vmdk.xz) = 8406a309bc022b8e32bb87e2e7a931e6ad1bfc9d4b4ce5ceb6ed7f5237a8fca15b3b3dff42d1b85c8aeef50853fc13b87c59182739a2e4464d1752772591784a SHA256 (FreeBSD-11.0-RC3-amd64.qcow2.xz) = 63b97db4e6337348463af1f62bf60fe40377cf62f31e9751309c47259ade9af8 SHA256 (FreeBSD-11.0-RC3-amd64.raw.xz) = 8904d877c5266f695c2dddea812777537651431a7fe43444a6d5bdbdf026facb SHA256 (FreeBSD-11.0-RC3-amd64.vhd.xz) = b5c9967d78e871463b025f23e7459ec94d59bab941b3774ef1960db5c83b3481 SHA256 (FreeBSD-11.0-RC3-amd64.vmdk.xz) = b0697644500cf5d060bab0a31671ac83ef8106af8b988396eec94090a8b95f99 o 11.0-RC3 i386: SHA512 (FreeBSD-11.0-RC3-i386.qcow2.xz) = 857a43ab0f83b6b589445746a2e802703be65443c396ea4e7a986b7a2d3f9e6d5b2f9f82dbdaec8319cd573d396d22ea128d8188c7d6ad437fcd517ddf72664a SHA512 (FreeBSD-11.0-RC3-i386.raw.xz) = 99555a50dfb283395e7aab18e2988d55d8503fdfdc276debb7334cea9f9d6169385aca2e4afe6ea0040a5391c2b0d7c6676393106812028f691814f50fc6c87d SHA512 (FreeBSD-11.0-RC3-i386.vhd.xz) = 087e36033fb9883c11a4367c836dfb87576ddc880ee9b33d90881a7cc2b783fa9f3602e29047b58622ef603645937d44d11797f7cfd24c605ab1dd79bd4891a8 SHA512 (FreeBSD-11.0-RC3-i386.vmdk.xz) = b5dd0341bef26e61a1b68bbf92cf5f57c04bc47a96bf1923423b9809841476246ee9d9b92f14c11aacee662d36c86345337489662052daf0efbfb94980beb535 SHA256 (FreeBSD-11.0-RC3-i386.qcow2.xz) = 17193e1ccc732f82aa332f2e24fcf256a2282bd695795312c628d94ebf8dce4e SHA256 (FreeBSD-11.0-RC3-i386.raw.xz) = 5d7d35dfb1a25c1e39caf02e3f3db8241c493e73421a41108ac580f2378b70f1 SHA256 (FreeBSD-11.0-RC3-i386.vhd.xz) = f323c199d3490795bc0bbbc833d731a28ee47b473d3978678b2f4f1b0479f879 SHA256 (FreeBSD-11.0-RC3-i386.vmdk.xz) = e63d096e2038c91945ab7be965432fcd4793f3f2696f08f7e380c9880e07f9c2 o 11.0-RC3 aarch64: SHA512 (FreeBSD-11.0-RC3-arm64-aarch64.qcow2.xz) = 36b6451f2476b3c58efad064da68ba3bc11aebfab723131f1e0e5d14bd6bb5f223710cc909e20afc1b3b90f5c098d8556945213da8f9724cc5ede121472601bc SHA512 (FreeBSD-11.0-RC3-arm64-aarch64.raw.xz) = d88a1eafb23049e66a78b48ce1b0af8017d810428bc71c70e3ad6bf6ac0eca1489047a06223243da03eb98f6f79efb6a5dca69088366dc7d13a2a39bf0a70732 SHA512 (FreeBSD-11.0-RC3-arm64-aarch64.vhd.xz) = e6394d676e0499f46e72ea60e0d65e7663f9f207bdb552a586ed719a791ce6ca55d92d9e6e495fe5bfd6a3af2388fd5ccc69ab8396c9204f3b702fd23f89f0b0 SHA512 (FreeBSD-11.0-RC3-arm64-aarch64.vmdk.xz) = f082d48e6c6cd82e192006c6cbdd2c811262f453d8a9bcdae59d84c6623c33fb074892dd03d59bea79f32dc90bcfd267a933f84883034d557308daa085f18e2e SHA256 (FreeBSD-11.0-RC3-arm64-aarch64.qcow2.xz) = 81f38f6bcb9a59af82e7a001a62b870d2fe3dcaf609d0e1ec8113a25db00e07f SHA256 (FreeBSD-11.0-RC3-arm64-aarch64.raw.xz) = 275c458cfa29eea0ec9188b9ceea15eafbfd6193b47ca51dfa65a95f126668f0 SHA256 (FreeBSD-11.0-RC3-arm64-aarch64.vhd.xz) = 4c9e2c8d81ae78d1e1ebb6895b06fe833206892ae2358c906364f274c81e71c4 SHA256 (FreeBSD-11.0-RC3-arm64-aarch64.vmdk.xz) = 17657549cb0116b3f54aaeeb2d8ab6b452c50d0035d62b8105ec41f5c7fdf28e Regards, Glen Love FreeBSD? Support this and future releases with a donation to the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJX3VLiAAoJEAMUWKVHj+KToUMP/iIJxGKE6748dmd+o/yhhL7t smewUXvesWw1q7JIg6CglGXWn43O2sp/Ynn6r0DHS4CxgToy1ndwNmWGoLCeIrZs x5OiM4bzBVyOGk6aW8B1cpO5OcwsOtb46vUCcIeBXC1NGYnslL/rZFma7oiurH/I hR3dmCE5q8jUvqFCjoNlA2bTE//j5uiXgYoNbXPi6R8UGbVj9m0x9e7/uVVvSXmS fbiyFtlMtD6CldhOHko/2GR6UxwnnsTcKJrqRy5iSsqxapTb3DpQCNe4+hyee7Hj 9hf2YbmEhVAbhejSDQazXZZFNTTtpEcHvOehYIBNKLS+LFOaTukQNsJ/GSb5TvJY 19hjXLWxPPo8LvmzoVTAsCpQ7sks66spEtJSfz5IuS622hH+YRKjT1A48tyB06TI ZbSQpRQ5vTkDkLJCKL1bjixlUXciRieOdZb/l1PgvBB5CdS3kMEVLmJFCnxLE9Vu R0I+NAbWImJEvR27Fp8VkgOPn+vaJVvLSrOoLpT5ExywZX0KOjlftXyXAglr9N73 oIqp03CV9EU13/feeFbUzJSGvfmLY/Ule+dO/65Mu5PZRpzRC3OiIUuK+4RNbQpv yYc13pnbyUHApO1ZysdV7IZB84xAyMyWpu4Comzyzcrp0PY6m8FMpQ0WB64hHv5r KzhgOqMPAUk851Q6duXC =10h3 -----END PGP SIGNATURE----- From owner-freebsd-stable@freebsd.org Sat Sep 17 16:32:48 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40F3BBDE5CF for ; Sat, 17 Sep 2016 16:32:48 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F127BCD1; Sat, 17 Sep 2016 16:32:47 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1blIXd-0004Qp-I3; Sat, 17 Sep 2016 19:32:37 +0300 Date: Sat, 17 Sep 2016 19:32:37 +0300 From: Slawa Olhovchenkov To: hiren panchasara Cc: Konstantin Belousov , jch@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20160917163237.GD2960@zxy.spb.ru> References: <20160914213503.GJ2840@zxy.spb.ru> <20160915085938.GN38409@kib.kiev.ua> <20160915090633.GS2840@zxy.spb.ru> <20160916181839.GC2960@zxy.spb.ru> <20160916183053.GL9397@strugglingcoder.info> <20160916190330.GG2840@zxy.spb.ru> <20160916191155.GM9397@strugglingcoder.info> <20160916203057.GH2840@zxy.spb.ru> <20160916214646.GR9397@strugglingcoder.info> <20160916214849.GS9397@strugglingcoder.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160916214849.GS9397@strugglingcoder.info> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 17 Sep 2016 16:32:48 -0000 On Fri, Sep 16, 2016 at 02:48:49PM -0700, hiren panchasara wrote: > On 09/16/16 at 02:46P, hiren panchasara wrote: > > On 09/16/16 at 11:30P, Slawa Olhovchenkov wrote: > > > On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote: > > > > > > > > > > > As I suspected, this looks like a hang trying to lock V_tcbinfo. > > > > > > > > I'm ccing Julien here who worked on WLOCK -> RLOCK transition to improve > > > > performance for short-lived connections. I am not too sure if thats the > > > > problem but looks in similar area so he may be able to provide some > > > > insights. > > > > > > No, this is other case. In may case at this time no network traffic > > > more then hour. This is some sore of deadlock or like. > > > > In my limited understanding, such deadlock like situation can occur > > without traffic too. > > Err, I meant to say light traffic. I am point again -- I am dont have traffic totaly. Absolytly no traffic From owner-freebsd-stable@freebsd.org Sat Sep 17 21:31:45 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A86FBDE5CD for ; Sat, 17 Sep 2016 21:31:45 +0000 (UTC) (envelope-from www@untersteiner.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 00B65330 for ; Sat, 17 Sep 2016 21:31:45 +0000 (UTC) (envelope-from www@untersteiner.com) Received: by mailman.ysv.freebsd.org (Postfix) id F3DCCBDE5CC; Sat, 17 Sep 2016 21:31:44 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1387BDE5CB for ; Sat, 17 Sep 2016 21:31:44 +0000 (UTC) (envelope-from www@untersteiner.com) Received: from smtp.outgoing.loopia.se (smtp.outgoing.loopia.se [194.9.95.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 63F7E32D for ; Sat, 17 Sep 2016 21:31:44 +0000 (UTC) (envelope-from www@untersteiner.com) Received: from s554.loopia.se (localhost [127.0.0.1]) by s554.loopia.se (Postfix) with ESMTP id 4228C19C613E for ; Sat, 17 Sep 2016 23:23:21 +0200 (CEST) Received: from s554.loopia.se (localhost [127.0.0.1]) by s554.loopia.se (Postfix) with ESMTP id 21FCE9CD59F; Sat, 17 Sep 2016 23:23:21 +0200 (CEST) X-Virus-Scanned: amavisd-new at outgoing-smtp.loopia.se X-Spam-Flag: NO X-Spam-Score: 3.987 X-Spam-Level: *** X-Spam-Status: No, score=3.987 tagged_above=-999 required=15 tests=[BAYES_50=2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_FONT_LOW_CONTRAST=0.786, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.199] autolearn=no autolearn_force=no Received: from s554.loopia.se ([127.0.0.1]) by s554.loopia.se (s554.loopia.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ZKFxj8PeS64j; Sat, 17 Sep 2016 23:23:18 +0200 (CEST) Received: from s529.loopia.se (s529.loopia.se [194.9.94.137]) by s554.loopia.se (Postfix) with ESMTP id 222442920EEA; Sat, 17 Sep 2016 23:23:09 +0200 (CEST) Received: by s529.loopia.se (Postfix, from userid 80) id 25F9D582C1B; Sat, 17 Sep 2016 23:23:09 +0200 (CEST) X-Loopia-Auth: domain X-Loopia-Domain: untersteiner.com To: stable@freebsd.org Subject: Important message about your paypal account ! X-PHP-Originating-Script: 80:mailer.php From: PayPal Cc: support@loopia.se Message-Id: <20160917212309.25F9D582C1B@s529.loopia.se> Date: Sat, 17 Sep 2016 23:23:09 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 17 Sep 2016 21:31:45 -0000