From owner-freebsd-stable@FreeBSD.ORG Mon Jun 1 02:38:46 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D9F961AF for ; Mon, 1 Jun 2015 02:38:46 +0000 (UTC) (envelope-from financeiro4@urgentesim2015.com.br) Received: from smtp3.task.com.br (smtp3.task.com.br [67.228.2.213]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BE0EB1F03 for ; Mon, 1 Jun 2015 02:38:45 +0000 (UTC) (envelope-from financeiro4@urgentesim2015.com.br) Received: from windows-vultr ([::ffff:104.207.147.59]) (AUTH: LOGIN financeiro4@urgentesim2015.com.br) by smtp3.task.com.br with ESMTPA; Sun, 31 May 2015 23:29:05 -0300 id 00000000000258BC.00000000556BC371.00007577 From: "Ana Paula" Subject: Emissao de NF-e (Nota Fiscal Eletronica) 10:29:04 PM To: freebsd-stable@freebsd.org MIME-Version: 1.0 Date: Sun, 31 May 2015 22:29:04 -0400 Message-Id: <201505312229045469DA2C56$3EE467ACF5@WINDOWSVULTR> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 01 Jun 2015 02:38:46 -0000 Emissao de NF-e (Nota Fiscal Eletronica) Prezado(a) freebsd-stable@freebsd.org Foi emitida um NF-e (Nota Fiscal Eletronica) referente ao seu pedido N= -135789685. Escolha abaixo a melhor forma de consultar a sua NF-e NF-77951258753951258-10:29:04 PM-NF.XML http://dogophukhe.com/upload/f= urniture/media/Anexo_NFe_311502.zip NF-178967325753951258-10:29:04 PM-NF.PDF http://dogophukhe.com/upload/= furniture/media/Anexo_NFe_311502.zip Atenciosamente, Ana Paula. Setor Financeiro. Rj Net LTDA CNPJ:95.372.882/0001-22 From owner-freebsd-stable@FreeBSD.ORG Mon Jun 1 12:30:09 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 58E7AF23 for ; Mon, 1 Jun 2015 12:30:09 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 29FEB1622 for ; Mon, 1 Jun 2015 12:30:09 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by oihd6 with SMTP id d6so99852455oih.2 for ; Mon, 01 Jun 2015 05:30:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ulkrHh0dmGnKa/R9oslHSGWwV3SwVijM6Qun4Ovnh/o=; b=xi07lKzDYniAzNPChlNEB47VGqyn5UVpEhG5uvE1UULK2cHRAjbn0DmTLevtN7jehS yA8ua0GzTXs92xy0XPbNgwMZPNey8uFyuqQohhV0lavOZ8e7wIU5MvqugvbI4PtD/8t4 StBOh8k/SdW/aYhUhe+ejLV+VvTm1Z8CwmofYn5rn6kPkmAy8o7JVD0Wofg1xy5w7BbL 4/FnQiVv5fAVXGGmP/dFXgCHw6MTEw0R7vnVI8j5LGyN0eQEDt1pAppkbjS9MejUzhvX sfSSPbTI/1OMkSwKvOiQwi7sf5Tviwdq2qmHUeEySJNFn3zEHbYP1iwUJ52+4b71I281 KG7A== MIME-Version: 1.0 X-Received: by 10.202.209.137 with SMTP id i131mr16975482oig.57.1433161808066; Mon, 01 Jun 2015 05:30:08 -0700 (PDT) Received: by 10.60.117.230 with HTTP; Mon, 1 Jun 2015 05:30:08 -0700 (PDT) Date: Mon, 1 Jun 2015 08:30:08 -0400 Message-ID: Subject: any plans to MFC the new AMD64 linux fixes From: Aryeh Friedman To: FreeBSD Stable List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 01 Jun 2015 12:30:09 -0000 Last week in -head many fixes where made to the AMD64 support for Linux (r283424) that fix among other things www/linux-c6-flashplugin11 not working because the kernel is to old. Are there any plans to MFC this? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-stable@FreeBSD.ORG Mon Jun 1 13:10:24 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0B6E1DC for ; Mon, 1 Jun 2015 13:10:24 +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 BA22710BC for ; Mon, 1 Jun 2015 13:10:23 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1YzPTw-0002Kf-80 for freebsd-stable@freebsd.org; Mon, 01 Jun 2015 16:10:20 +0300 Date: Mon, 1 Jun 2015 16:10:20 +0300 From: Slawa Olhovchenkov To: freebsd-stable@freebsd.org Subject: How to track stable on multiple servers? Message-ID: <20150601131020.GC58397@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) 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.20 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, 01 Jun 2015 13:10:24 -0000 I have some set of FreeBSD servers in public internet and continue to find optimal way for track -stable branch. Handbook give next metods: 1. Tracking -security branch by freebsd-update. I want -stable, -security don't have wanted features. 2. svn & rebuilding world localy. To long and wery badly automated, bad version synchronisation between servers. 3. svn & rebuilding world on build server, install localy by NFS. Servers in public internet, I am to be afraid exposing NFS to public internet. Also, need to have localy /etc/{make,src}.conf in sync with build server. Also badly automated. 4. Build private freebsd-update-server and build (simularity to security btanch) updates for -stable. Need essentially dedicated server -- during build system time changed and this is may be raise side effects. freebsd-update work wery long time (hours) and accumulate a lot of garbage: # du -ms /var/db/freebsd-update/ 2010 /var/db/freebsd-update/ freebsd-update-server/freebsd-update too bugly and debuggint is not easy. config mergering working worse mergemaster. Don't allow to repair damaged files (freebsd-update IDS detect changes but don't repair this). 5. nanobsd. Don't automatic save /etc and etc. pkg updated throw system image update and reboot. Unaccpetable. Something else? From owner-freebsd-stable@FreeBSD.ORG Mon Jun 1 13:19:49 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 42A9F63B for ; Mon, 1 Jun 2015 13:19:49 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (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 BE1E1131A for ; Mon, 1 Jun 2015 13:19:48 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: by labpy14 with SMTP id py14so89465855lab.0 for ; Mon, 01 Jun 2015 06:19:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fuVeHkhhs2GBsu0ikK3EhsVNOorGT4nFuKS3vLum86U=; b=Cp/H+zH2REABu9cpqtS/1dZX+ctxdZL5704lV6l/tmWEB6/JENKymRPFKh+BbIH35l yQlJq70mOPgaDRKs0dv/Qv/tDA4WDQBQod9ZSmjvgjBJVgfWtoIQnCH4JaBzfyB/zRkv FMXNaDXCCgodxeL6ElLP54upvrSH8N2AJGOvVXc7NBBdio0QGrYSlH570JrdDVBGcQU3 6jmMuJjxURpG/o+mlXHxQP1Nxas6iKbDksL8wuyryuXBtqooExJQVhROIFLTnJZaOMWL T83Jr5513THUy+23w3v63vwDFLdzdHiMc9Nnivuu98jIyFppdahGnTUs8p7rnP/JuaSn ybgw== MIME-Version: 1.0 X-Received: by 10.152.203.162 with SMTP id kr2mr21049628lac.68.1433164786745; Mon, 01 Jun 2015 06:19:46 -0700 (PDT) Received: by 10.152.137.193 with HTTP; Mon, 1 Jun 2015 06:19:46 -0700 (PDT) In-Reply-To: <20150601131020.GC58397@zxy.spb.ru> References: <20150601131020.GC58397@zxy.spb.ru> Date: Mon, 1 Jun 2015 16:19:46 +0300 Message-ID: Subject: Re: How to track stable on multiple servers? From: Kimmo Paasiala To: Slawa Olhovchenkov Cc: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 01 Jun 2015 13:19:49 -0000 On Mon, Jun 1, 2015 at 4:10 PM, Slawa Olhovchenkov wrote: > I have some set of FreeBSD servers in public internet and continue to > find optimal way for track -stable branch. > > Handbook give next metods: > > 1. Tracking -security branch by freebsd-update. > I want -stable, -security don't have wanted features. > > 2. svn & rebuilding world localy. To long and wery badly automated, > bad version synchronisation between servers. > > 3. svn & rebuilding world on build server, install localy by NFS. > Servers in public internet, I am to be afraid exposing NFS to > public internet. Also, need to have localy /etc/{make,src}.conf in > sync with build server. Also badly automated. > > 4. Build private freebsd-update-server and build (simularity to > security btanch) updates for -stable. > Need essentially dedicated server -- during build system time > changed and this is may be raise side effects. > freebsd-update work wery long time (hours) and accumulate a lot of > garbage: > > # du -ms /var/db/freebsd-update/ > 2010 /var/db/freebsd-update/ > > freebsd-update-server/freebsd-update too bugly and debuggint is not > easy. > config mergering working worse mergemaster. > Don't allow to repair damaged files (freebsd-update IDS detect > changes but don't repair this). > > 5. nanobsd. > Don't automatic save /etc and etc. > pkg updated throw system image update and reboot. Unaccpetable. > > > Something else? When I had to something like this I went with option 3. It's not completely automated as you say because of /etc/(make|src).conf but there are no better options at the moment because /usr/obj is not "self contained" because its contents and interpretation depends on auxillary files, the /etc/make.conf and /etc/src.conf files. -Kimmo From owner-freebsd-stable@FreeBSD.ORG Mon Jun 1 14:39:26 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFE67D3C for ; Mon, 1 Jun 2015 14:39:26 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C55871706 for ; Mon, 1 Jun 2015 14:39:26 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t51EfAGQ019304 for ; Mon, 1 Jun 2015 07:41:16 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: <20150601131020.GC58397@zxy.spb.ru>, From: "Chris H" Subject: Re: How to track stable on multiple servers? Date: Mon, 01 Jun 2015 07:41:16 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <20417f512b516b053cab7ac4c3e17c81@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 01 Jun 2015 14:39:27 -0000 On Mon, 1 Jun 2015 16:19:46 +0300 Kimmo Paasiala wrote > On Mon, Jun 1, 2015 at 4:10 PM, Slawa Olhovchenkov wrote: > > I have some set of FreeBSD servers in public internet and continue to > > find optimal way for track -stable branch. > > > > Handbook give next metods: > > > > 1. Tracking -security branch by freebsd-update. > > I want -stable, -security don't have wanted features. > > > > 2. svn & rebuilding world localy. To long and wery badly automated, > > bad version synchronisation between servers. > > > > 3. svn & rebuilding world on build server, install localy by NFS. > > Servers in public internet, I am to be afraid exposing NFS to > > public internet. Also, need to have localy /etc/{make,src}.conf in > > sync with build server. Also badly automated. > > > > 4. Build private freebsd-update-server and build (simularity to > > security btanch) updates for -stable. > > Need essentially dedicated server -- during build system time > > changed and this is may be raise side effects. > > freebsd-update work wery long time (hours) and accumulate a lot of > > garbage: > > > > # du -ms /var/db/freebsd-update/ > > 2010 /var/db/freebsd-update/ > > > > freebsd-update-server/freebsd-update too bugly and debuggint is not > > easy. > > config mergering working worse mergemaster. > > Don't allow to repair damaged files (freebsd-update IDS detect > > changes but don't repair this). > > > > 5. nanobsd. > > Don't automatic save /etc and etc. > > pkg updated throw system image update and reboot. Unaccpetable. > > > > > > Something else? > > > When I had to something like this I went with option 3. It's not > completely automated as you say because of /etc/(make|src).conf but > there are no better options at the moment because /usr/obj is not > "self contained" because its contents and interpretation depends on > auxillary files, the /etc/make.conf and /etc/src.conf files. > > -Kimmo I go with a variation of option 3, using jails, and a combination of building packages, and using dump(8), and restore(8) (when needed). --Chris > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Jun 1 19:42:53 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A5D35BCD for ; Mon, 1 Jun 2015 19:42:53 +0000 (UTC) (envelope-from dchagin@dchagin.static.corbina.net) Received: from heemeyer.club (heemeyer.club [IPv6:2001:19f0:6400:80a1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "heemeyer.club", Issuer "heemeyer.club" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 79852155B for ; Mon, 1 Jun 2015 19:42:52 +0000 (UTC) (envelope-from dchagin@dchagin.static.corbina.net) Received: from dchagin.static.corbina.net (dchagin.static.corbina.ru [78.107.232.239]) by heemeyer.club (8.15.1/8.15.1) with ESMTPS id t51JggCK015167 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 1 Jun 2015 19:42:49 GMT (envelope-from dchagin@dchagin.static.corbina.net) X-Authentication-Warning: heemeyer.club: Host dchagin.static.corbina.ru [78.107.232.239] claimed to be dchagin.static.corbina.net Received: from dchagin.static.corbina.net (localhost [127.0.0.1]) by dchagin.static.corbina.net (8.15.1/8.15.1) with ESMTPS id t51Jgf6k066956 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 1 Jun 2015 22:42:41 +0300 (MSK) (envelope-from dchagin@dchagin.static.corbina.net) Received: (from dchagin@localhost) by dchagin.static.corbina.net (8.15.1/8.15.1/Submit) id t51Jgf66066955; Mon, 1 Jun 2015 22:42:41 +0300 (MSK) (envelope-from dchagin) Date: Mon, 1 Jun 2015 22:42:40 +0300 From: Chagin Dmitry To: Aryeh Friedman Cc: FreeBSD Stable List Subject: Re: any plans to MFC the new AMD64 linux fixes Message-ID: <20150601194240.GA66929@dchagin.static.corbina.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 01 Jun 2015 19:42:53 -0000 On Mon, Jun 01, 2015 at 08:30:08AM -0400, Aryeh Friedman wrote: > Last week in -head many fixes where made to the AMD64 support for Linux > (r283424) that fix among other things www/linux-c6-flashplugin11 not > working because the kernel is to old. Are there any plans to MFC this? > some people reports that flash is stop working after lemul merge, so it should be investigated carefully before merge to stable -- Have fun! chd From owner-freebsd-stable@FreeBSD.ORG Mon Jun 1 19:49:01 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 402BBFFE; Mon, 1 Jun 2015 19:49:01 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (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 05BFC15E8; Mon, 1 Jun 2015 19:49:01 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by obcnx10 with SMTP id nx10so106210010obc.2; Mon, 01 Jun 2015 12:49:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yAwx7zePwUSLXkDhlQVV7pOpRYAYamsw8Np3LLJ/ZF8=; b=uGY+88Z74NerLZ4/baBqZ7GWVVSWpYlla++Lv6bbVQM0N1W1fgE169nboTPdaw95oA Ms6PiLrViZOnTDfRJxqz271TpCIl/OXeGylw33Al+XlOQgzoTuHpA/7IN/K2Cq+5HCtt Y9EUW5rJLMPSgDqd0FCiNJfrvEvgfcvWU41vf+q5a4jnrtc5YThisd9zBaDgoQOjmtmQ RQ19tIa6BtHxboaH2QyXb8M8CBHgZyjHSiuMSVbN+TjjJhNFzQoUC8n5XqVfR5HIOGUG ppjpvrZuPPBxVMmsNFSP1LQQOEsy07FSoqOQTpSro4njeifks06WXM1Ey2YTFT082wHS JSaw== MIME-Version: 1.0 X-Received: by 10.60.96.35 with SMTP id dp3mr19816402oeb.47.1433188140233; Mon, 01 Jun 2015 12:49:00 -0700 (PDT) Received: by 10.60.117.230 with HTTP; Mon, 1 Jun 2015 12:49:00 -0700 (PDT) In-Reply-To: <20150601194240.GA66929@dchagin.static.corbina.net> References: <20150601194240.GA66929@dchagin.static.corbina.net> Date: Mon, 1 Jun 2015 15:49:00 -0400 Message-ID: Subject: Re: any plans to MFC the new AMD64 linux fixes From: Aryeh Friedman To: Chagin Dmitry Cc: FreeBSD Stable List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 01 Jun 2015 19:49:01 -0000 On Mon, Jun 1, 2015 at 3:42 PM, Chagin Dmitry wrote: > On Mon, Jun 01, 2015 at 08:30:08AM -0400, Aryeh Friedman wrote: > > Last week in -head many fixes where made to the AMD64 support for Linux > > (r283424) that fix among other things www/linux-c6-flashplugin11 not > > working because the kernel is to old. Are there any plans to MFC this? > > > some people reports that flash is stop working after lemul merge, > so it should be investigated carefully before merge to stable > If you need a tester I am game -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-stable@FreeBSD.ORG Tue Jun 2 23:10:16 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EBCCF358 for ; Tue, 2 Jun 2015 23:10:16 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 A70D61B4E for ; Tue, 2 Jun 2015 23:10:16 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: by qkhg32 with SMTP id g32so110232160qkh.0 for ; Tue, 02 Jun 2015 16:10:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lux/56UNt9Vf8U67b55I7fPtIGGxMzFhZtFkq5DHiIQ=; b=WpQyn4aWwla+PZAoCusq1nkKgjO93ZFuKLGzLFozusJAlhDS6G1oaRsTZqtaoHPIdk +vM6JOlm4BexEMrY1bN48m9p5aSN0yiMjoB+WkpZ6rnIMtN4sJHiUNbLqcBdgzNK1S+D WA/m8PFQDH1Ygh9ZI/pfPVjgk0Qve8K7ye4/1BqjjFf+zosbv6qzc9QkYHnGYNYTZPTb lthFiGvXUVgVems4Dp3PygWX4ouQlJvDzJmdIpNlP5kVPP3oCuKYCvUJk0K9PudLTTem 88T0I3PUpZOqEcnWGlKL3HwIt09dUCE51ZSpwgBe4PeCG+GSJzYB4so+C9GQJ4+yklre 0JJQ== MIME-Version: 1.0 X-Received: by 10.229.188.137 with SMTP id da9mr33664147qcb.27.1433286615520; Tue, 02 Jun 2015 16:10:15 -0700 (PDT) Received: by 10.229.191.4 with HTTP; Tue, 2 Jun 2015 16:10:15 -0700 (PDT) In-Reply-To: <90B2D392-01FD-415A-B3D9-3CEDFC8373C4@smkelly.org> References: <90B2D392-01FD-415A-B3D9-3CEDFC8373C4@smkelly.org> Date: Tue, 2 Jun 2015 16:10:15 -0700 Message-ID: Subject: Re: 10.1 NVMe kernel panic From: Jim Harris To: Sean Kelly 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.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 02 Jun 2015 23:10:17 -0000 On Thu, May 21, 2015 at 8:33 AM, Sean Kelly wrote: > Greetings. > > I have a Dell R630 server with four of Dell=E2=80=99s 800GB NVMe SSDs run= ning > FreeBSD 10.1-p10. According to the PCI vendor, they are some sort of > rebranded Samsung drive. If I boot the system and then load nvme.ko and > nvd.ko from a command line, the drives show up okay. If I put > nvme_load=3D=E2=80=9CYES=E2=80=9D > nvd_load=3D=E2=80=9CYES=E2=80=9D > in /boot/loader.conf, the box panics on boot: > panic: nexus_setup_intr: NULL irq resource! > > If I boot the system with =E2=80=9CSafe Mode: ON=E2=80=9D from the loader= menu, it also > boots successfully and the drives show up. > > You can see a full =E2=80=98boot -v=E2=80=99 here: > http://smkelly.org/stuff/nvme-panic.txt < > http://smkelly.org/stuff/nvme-panic.txt> > > Anyone have any insight into what the issue may be here? Ideally I need t= o > get this working in the next few days or return this thing to Dell. > Hi Sean, Can you try adding hw.nvme.force_intx=3D1 to /boot/loader.conf? I suspect you are able to load the drivers successfully after boot because interrupt assignments are not restricted to CPU0 at that point - see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199321 for a related issue. Your logs clearly show that vectors were allocated for the first 2 NVMe SSDs, but the third could not get its full allocation. There is a bug in the INTx fallback code that needs to be fixed - you do not hit this bug when loading after boot because bug #199321 only affects interrupt allocation during boot. If the force_intx test works, would you able to upgrade your nvme drivers to the latest on stable/10? There are several patches (one related to interrupt vector allocation) that have been pushed to stable/10 since 10.1 was released, and I will be pushing another patch for the issue you have reported shortly. Thanks, -Jim > > Thanks! > > -- > Sean Kelly > smkelly@smkelly.org > http://smkelly.org > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Wed Jun 3 03:06:57 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CA52CB87 for ; Wed, 3 Jun 2015 03:06:57 +0000 (UTC) (envelope-from smkelly@smkelly.org) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 9544D132C for ; Wed, 3 Jun 2015 03:06:57 +0000 (UTC) (envelope-from smkelly@smkelly.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 31B9F20B16 for ; Tue, 2 Jun 2015 23:06:50 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Tue, 02 Jun 2015 23:06:50 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=smkelly.org; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=DNi5d sRU2LV2j3lJRZDR9VMXENA=; b=rjldF7JnYpuXFvnMQd6GzqAiBw8vToCSqWPHV /HOEj/mqS4QluvaTzhZCdwwLrviy1OqJ4pPpLVXZjHK8zpd50JSGh0/pv7TI/dx1 88EDFEi5F5POy8nQ/RBNs/sMsD586nDN/sKAZRWhg1ZDTTPcUQlqGDgd+drmrxJJ zGR9aw= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=DNi5dsRU2LV2j3lJRZDR9VMXENA=; b=CB/tZ oK5ViECUKERLAkZZmVbhhy6M0Lrcn8ULodX6ldPSobK3VoCP6Z3/KD9A8ZvLU+xO oKA0LrgruU3ofTsny9dVf1Av9HFE12vTrvjBB15NCyCyPbME7jqvRCtoeNcVIi7A G+GpRjPjM1ce5y8VwkzGsMkgMLl1PMroRA2jOc= X-Sasl-enc: /viiZh7tbFMu4qkd9rUaZS3lSq7jxMnrb3gucSlo5+X6 1433300809 Received: from vpn-3.gwp.corp.flightaware.com (unknown [38.100.147.146]) by mail.messagingengine.com (Postfix) with ESMTPA id A64C5680141; Tue, 2 Jun 2015 23:06:49 -0400 (EDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2100\)) Subject: Re: 10.1 NVMe kernel panic From: Sean Kelly In-Reply-To: Date: Tue, 2 Jun 2015 22:06:48 -0500 Cc: FreeBSD-STABLE Mailing List Message-Id: References: <90B2D392-01FD-415A-B3D9-3CEDFC8373C4@smkelly.org> To: Jim Harris X-Mailer: Apple Mail (2.2100) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 03:06:57 -0000 Jim, Thanks for the reply. I set hw.nvme.force_intx=3D1 and get a new form of = kernel panic: http://smkelly.org/stuff/nvme_crash_force_intx.txt = It looks like the NVMes are just failing to initialize at all now. As = long as that tunable is in the kenv, I get this behavior. If I kldload = them after boot, the init fails as well. But if I kldunload, kenv -u, = kldload, it then works again. The only difference is kldload doesn=E2=80=99= t result in a panic, just timeouts initializing them all. I also compiled and tried stable/10 and it crashed in a similar way, but = i=E2=80=99ve not captured the panic yet. It crashes even without the = tunable in place. I=E2=80=99ll see if I can capture it. --=20 Sean Kelly smkelly@smkelly.org http://smkelly.org > On Jun 2, 2015, at 6:10 PM, Jim Harris wrote: >=20 >=20 >=20 > On Thu, May 21, 2015 at 8:33 AM, Sean Kelly > wrote: > Greetings. >=20 > I have a Dell R630 server with four of Dell=E2=80=99s 800GB NVMe SSDs = running FreeBSD 10.1-p10. According to the PCI vendor, they are some = sort of rebranded Samsung drive. If I boot the system and then load = nvme.ko and nvd.ko from a command line, the drives show up okay. If I = put > nvme_load=3D=E2=80=9CYES=E2=80=9D > nvd_load=3D=E2=80=9CYES=E2=80=9D > in /boot/loader.conf, the box panics on boot: > panic: nexus_setup_intr: NULL irq resource! >=20 > If I boot the system with =E2=80=9CSafe Mode: ON=E2=80=9D from the = loader menu, it also boots successfully and the drives show up. >=20 > You can see a full =E2=80=98boot -v=E2=80=99 here: > http://smkelly.org/stuff/nvme-panic.txt = = > >=20 > Anyone have any insight into what the issue may be here? Ideally I = need to get this working in the next few days or return this thing to = Dell. >=20 > Hi Sean, >=20 > Can you try adding hw.nvme.force_intx=3D1 to /boot/loader.conf? >=20 > I suspect you are able to load the drivers successfully after boot = because interrupt assignments are not restricted to CPU0 at that point - = see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199321 = for a = related issue. Your logs clearly show that vectors were allocated for = the first 2 NVMe SSDs, but the third could not get its full allocation. = There is a bug in the INTx fallback code that needs to be fixed - you do = not hit this bug when loading after boot because bug #199321 only = affects interrupt allocation during boot. >=20 > If the force_intx test works, would you able to upgrade your nvme = drivers to the latest on stable/10? There are several patches (one = related to interrupt vector allocation) that have been pushed to = stable/10 since 10.1 was released, and I will be pushing another patch = for the issue you have reported shortly. >=20 > Thanks, >=20 > -Jim >=20 >=20 > =20 >=20 > Thanks! >=20 > -- > Sean Kelly > smkelly@smkelly.org > http://smkelly.org >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing = list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable = > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org = " From owner-freebsd-stable@FreeBSD.ORG Wed Jun 3 11:34:06 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E4201668 for ; Wed, 3 Jun 2015 11:34:06 +0000 (UTC) (envelope-from ortadur@web.de) Received: from mout.web.de (mout.web.de [212.227.17.12]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.web.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 785C719B2 for ; Wed, 3 Jun 2015 11:34:06 +0000 (UTC) (envelope-from ortadur@web.de) Received: from [131.169.214.139] by 3capp-webde-bs60.server.lan (via HTTP); Wed, 3 Jun 2015 13:34:04 +0200 MIME-Version: 1.0 Message-ID: From: "Andre Meiser" To: freebsd-stable@freebsd.org Subject: Many core dumps in pthread_getspecific. Content-Type: text/plain; charset=UTF-8 Date: Wed, 3 Jun 2015 13:34:04 +0200 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K0:Zy+WSBjq7xjv1O/qkChLViXlecd1H2wiahJLiQhi1lF bTMO/6uFDTz41rZyBXKnysvXj9VgAiUK1islYdCVUIa9BFiHQP /72ATUbXXab0LftZWAPjH1JdLnGPbyANeLoMMzbVWNW4Mow3T1 //MwLeFnK114c9lrJwKu6O53s+Sip9PZSA30Lnyf9IiutVC72y p+VY15znL/y7f/FII+1KCt8riXT1bigDQka870ZMKw5qgrSwZM irYGmmAhqlv2TNEqD3cY+8+CoR6SL+Hefj7TOVQeYYO5clA65f DmtLLk= X-UI-Out-Filterresults: notjunk:1;V01:K0:icLovBhqe/w=:RMJ2s+RrBeGG4hRirXOswe Vy8D8+AVHd+I3USRjW4v7LWNjbCFargJ3XfAA9HfrPc+bJWzFx5tMKY3VwgOFkMDAyTFXUwlG CB4sQ6OEQWxpPiiCtb6pmqWzcYdOiqi08SsS8Yg9BGJ1L64HNBAaKvsd8SSeFldMXaBFZ4sKL K9zA7EEOIgtgJkWAG2Y1fthA491ld4yxN7injgkVehQcSVj0aFc4Z+tU+sRoRz8dpnIbKtYLo csvYFd1dPG1GhQBcM/QxL8C+LEmFPFDgiGUxtq2KMGgJXcHY9WmjFGbQIgJgoMZCgeH+JMorH u9760YhiipI4z4IVGBqQam+bfCMAodW3BczSXcIiLHSfonxMxDHZi00BwjkZgpu0kMeAhqnK6 O31sxBGMVERjGNFRY3mQjTYAZIZR1agZqBbunEmueJbmMOIOYmb7eKFE7XofT+LG/LWu3xcBB Nk7wyuJcbA== X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 11:34:07 -0000 Hi, I'm new to FreeBSD and I'm running into a lot of core dumps (mainly from Xorg, but also from vim, firefox, ...). That's why I asked on freebsd-questions: https://lists.freebsd.org/pipermail/freebsd-questions/2015-June/266138.html https://lists.freebsd.org/pipermail/freebsd-questions/2015-June/266141.html The last Xorg crash was less than 2h ago. :( It looks like that there is a missing check for NULL in lib/libkse/thread/thr_spec.c (line 211-214): pthread = _get_curthread(); /* Check if there is specific data: */ if (pthread->specific != NULL && (unsigned int)key < PTHREAD_KEYS_MAX) { If pthread is NULL it will core dump. So maybe something like this would help: if (pthread != NULL && pthread->specific != NULL && (unsigned int)key < PTHREAD_KEYS_MAX) { But as I'm said, I'm new to FreeBSD I can't evaluate it yet. I'm running the most recent stable: % uname -a FreeBSD andre 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Wed May 13 06:54:13 UTC 2015 I haven't compiled the base system so far. Maybe a more experienced FreeBSD guy can verify this and decide if it makes any sense or if I have to dig any deeper into it. Sincerely yours Andre. From owner-freebsd-stable@FreeBSD.ORG Wed Jun 3 12:07:35 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 92C5018B for ; Wed, 3 Jun 2015 12:07:35 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5849F1123 for ; Wed, 3 Jun 2015 12:07:34 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1Z07R8-0007ak-7t for freebsd-stable@freebsd.org; Wed, 03 Jun 2015 14:07:26 +0200 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Date: Wed, 03 Jun 2015 14:06:20 +0200 Subject: iwn & Intel Centrino Advanced-N 6235 support in 10-stable MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/1.0 (Win32) X-Authenticated-As-Hash: bdb49c4ff80bd276e321aade33e76e02752072e2 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50, URIBL_BLOCKED autolearn=disabled version=3.3.2 X-Scan-Signature: 7b320cd02cd98c580351ccd23ba1512a X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 12:07:35 -0000 Hello, I see support for the 6235 in iwn(4) is committed in Dec 2013 to CURRENT [1]. I would like to buy one of these for a reasonable price [2]. Will it be easy to use the driver from current in 10-stable? Or is there a reason support for this hardware is not MFC'ed? [1] http://svnweb.freebsd.org/base?view=revision&revision=259116 [2] http://www.routercenter.nl/product/294857/intel-centrino-advanced-n-6235.html A recommendation for a better supported card is also welcome. Regards, Ronald. From owner-freebsd-stable@FreeBSD.ORG Wed Jun 3 12:25:31 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9BB58730 for ; Wed, 3 Jun 2015 12:25:31 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) (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 3E59A16D3 for ; Wed, 3 Jun 2015 12:25:30 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by wgv5 with SMTP id 5so7734785wgv.1 for ; Wed, 03 Jun 2015 05:25:23 -0700 (PDT) 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:date :message-id:subject:from:to:cc:content-type; bh=bs82LR6VjDNMThKUAfPMTilFn8I4S5o5BKinkTqxDdk=; b=OR3FxTneMaSoW/wiX6L5BxalQjSx67rKLIyXSbySipityqR1fG0n7S8Vmy3C/0VndI RpUyYxTmgDzdX9aFZecxbAZV9W4SCBSFcD/mzG0rmQfsJ4FfEcqXwWmuJAKKPapslf2E pGxlqvi+p5+v/Hs8xvhtyA9t0I+jptmiDGohaGFzw/tdc3UjQ3x7u+4WRwJRjtpcTVvY KH+awtEa9ZVeAG3AU3mj2SS9zPrSWltmBdXyOzqMbG1vWRVwTI+Gl/M7wAM1JfyEa1+W aBYpA9aLMlmeOj96XesPvI+hZXeqocwJd3im2PBaqLaZsRpvF5cZhE/sn+2h/Pb3z/yA vDrw== X-Gm-Message-State: ALoCoQlMGp1epR9N5dNVoESV9R51jiGxwnEcWrffACHNfVzbKi3D1bDlxmmoxuByKuYMnxofDznN MIME-Version: 1.0 X-Received: by 10.180.99.2 with SMTP id em2mr41349034wib.59.1433334323416; Wed, 03 Jun 2015 05:25:23 -0700 (PDT) Received: by 10.194.162.225 with HTTP; Wed, 3 Jun 2015 05:25:23 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Jun 2015 14:25:23 +0200 Message-ID: Subject: Re: iwn & Intel Centrino Advanced-N 6235 support in 10-stable From: Oliver Pinter To: Ronald Klop Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 12:25:31 -0000 On 6/3/15, Ronald Klop wrote: > Hello, > > I see support for the 6235 in iwn(4) is committed in Dec 2013 to CURRENT > [1]. I would like to buy one of these for a reasonable price [2]. Will it > be easy to use the driver from current in 10-stable? Or is there a reason > support for this hardware is not MFC'ed? > > [1] http://svnweb.freebsd.org/base?view=revision&revision=259116 > [2] > http://www.routercenter.nl/product/294857/intel-centrino-advanced-n-6235.html > > A recommendation for a better supported card is also welcome. Hi Ronald! Try this branch: https://github.com/opntr/opBSD/tree/op/stable/10-stable-hbsd-iwn . I backported most of the net80211 and iwn related changes till 2014. August to 10-STABLE in this branch. > > Regards, > Ronald. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Wed Jun 3 13:30:58 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D5D2E49E for ; Wed, 3 Jun 2015 13:30:58 +0000 (UTC) (envelope-from will@sundivenetworks.com) Received: from mail.sundivenetworks.net (mail.sundivenetworks.net [212.13.212.5]) (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 A111D1681 for ; Wed, 3 Jun 2015 13:30:58 +0000 (UTC) (envelope-from will@sundivenetworks.com) Received: from static45-91.adsl.bogons.net ([85.158.45.91] helo=[192.168.1.53]) by mail.sundivenetworks.net with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Z088h-0006KO-Dl for freebsd-stable@freebsd.org; Wed, 03 Jun 2015 13:51:24 +0100 From: Will Green Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Xeon D-1540 Support Message-Id: Date: Wed, 3 Jun 2015 13:51:38 +0100 To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- X-Spam: No X-bounce-key: sundivenetworks.net-1; will@sundivenetworks.com; 1433338258; 5d1153c6; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 13:30:58 -0000 Hello, Has anyone had any success running FreeBSD 10.1 on the Xeon D-1540 [1]? = It=E2=80=99s a 8-core Broadwell-based Xeon SOC with integrated GigE or = 10GigE. The combination of low power and support for 128 GB of ram makes them = quite attractive. An example motherboard with this CPU is the Supermicro = X10SDV-F [2]. The Supermicro web site shows support for FreeBSD 10.1 = [3], but I haven=E2=80=99t seen any use in the wild. I will try to get = hold of a board to test, but any advance information on support would be = useful. Thanks, Will [1] = http://ark.intel.com/products/87039/Intel-Xeon-Processor-D-1540-12M-Cache-= 2_00-GHz [2] http://www.supermicro.co.uk/products/motherboard/Xeon/D/X10SDV-F.cfm [3] http://www.supermicro.co.uk/support/resources/OS/Broadwell-DE.cfm= From owner-freebsd-stable@FreeBSD.ORG Wed Jun 3 14:58:47 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B6761FD6 for ; Wed, 3 Jun 2015 14:58:47 +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 2C0591C2B for ; Wed, 3 Jun 2015 14:58:46 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t53EwcdX097627 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 3 Jun 2015 17:58:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t53EwcdX097627 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t53EwcHp097626; Wed, 3 Jun 2015 17:58:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 3 Jun 2015 17:58:38 +0300 From: Konstantin Belousov To: Andre Meiser Cc: freebsd-stable@freebsd.org Subject: Re: Many core dumps in pthread_getspecific. Message-ID: <20150603145838.GX2499@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 14:58:47 -0000 On Wed, Jun 03, 2015 at 01:34:04PM +0200, Andre Meiser wrote: > Hi, > > I'm new to FreeBSD and I'm running into a lot of core dumps (mainly from Xorg, but also from vim, firefox, ...). > That's why I asked on freebsd-questions: > > https://lists.freebsd.org/pipermail/freebsd-questions/2015-June/266138.html > https://lists.freebsd.org/pipermail/freebsd-questions/2015-June/266141.html > > The last Xorg crash was less than 2h ago. :( > > It looks like that there is a missing check for NULL in lib/libkse/thread/thr_spec.c (line 211-214): > > pthread = _get_curthread(); > > /* Check if there is specific data: */ > if (pthread->specific != NULL && (unsigned int)key < PTHREAD_KEYS_MAX) { > > If pthread is NULL it will core dump. So maybe something like this would help: > > if (pthread != NULL && pthread->specific != NULL && (unsigned int)key < PTHREAD_KEYS_MAX) { > > But as I'm said, I'm new to FreeBSD I can't evaluate it yet. > > I'm running the most recent stable: > > % uname -a > FreeBSD andre 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Wed May 13 06:54:13 UTC 2015 > > I haven't compiled the base system so far. Maybe a more experienced FreeBSD guy can verify this and decide if it makes any sense or if I have to dig any deeper into it. The backtraces you posted do not make any sense, e.g. pthread_mutex_unlock() does not call pthread_getspecific(), and pthread_getspecific() is not recursive. You should recompile both libc and libthr with debugging symbols, like cd /usr/src (cd lib/libc && make all install DEBUG_FLAGS=-g) (cd lib/libthr && make all install DEBUG_FLAGS=-g) then obtain the core dump and post backtraces. From owner-freebsd-stable@FreeBSD.ORG Wed Jun 3 15:48:08 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25EB1AE7 for ; Wed, 3 Jun 2015 15:48:08 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) (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 E5FB61956 for ; Wed, 3 Jun 2015 15:48:07 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: by ieclw1 with SMTP id lw1so16303580iec.3 for ; Wed, 03 Jun 2015 08:48:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=kBVzB02D2s2cuVu8yoq3U6SQ7JFioLwOH9ySxBu96Lc=; b=Ypnd03osAaqk4W1/7FtO569fyFce0hEk1gdhSgCJQrNURayT7fdYUzgT/z/54cMn3l 8r40lPwfRnFM1Crik2WOf8luum5eMNraGfxErvUb6u2/IKHXtvuJXZdeFrkqYkF/Mbpi YTQn2a+xQMX9vDbYF0nedT2s/5AG/AzX/GLvmGsESWA/kWK2CUMZsxSeJELAq4y2/vQ4 XLlxBCXOBaqMF3R15bpbSug3Qvst3vvRkMLS+sTAhxDZ+0k3PbXHr4k9Of/1XPKgtm9I aWN0ubzWp7q8EIzJnNG+H0fpNt4Fkm9I/dw6mSUD6VREqEQwoOkbvKJHqTSmp+p9UkyU Yq6g== X-Received: by 10.107.8.144 with SMTP id h16mr7514854ioi.49.1433346480997; Wed, 03 Jun 2015 08:48:00 -0700 (PDT) Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com. [209.85.223.171]) by mx.google.com with ESMTPSA id e10sm814771igy.11.2015.06.03.08.48.00 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jun 2015 08:48:00 -0700 (PDT) Received: by ieclw1 with SMTP id lw1so16303342iec.3 for ; Wed, 03 Jun 2015 08:48:00 -0700 (PDT) X-Received: by 10.107.39.209 with SMTP id n200mr2890941ion.59.1433346480560; Wed, 03 Jun 2015 08:48:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Eric Joyner Date: Wed, 03 Jun 2015 15:47:50 +0000 Message-ID: Subject: Re: Xeon D-1540 Support To: Will Green , freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 15:48:08 -0000 Yeah; you can run FreeBSD 10.1 and 11-CURRENT on an X10SDV-TLN4F. If you use stable/10 or CURRENT, you can also use the 10gig ethernet ports out of the box, too. On Wed, Jun 3, 2015 at 6:31 AM Will Green wrote: > Hello, > > Has anyone had any success running FreeBSD 10.1 on the Xeon D-1540 [1]? > It=E2=80=99s a 8-core Broadwell-based Xeon SOC with integrated GigE or 10= GigE. > > The combination of low power and support for 128 GB of ram makes them > quite attractive. An example motherboard with this CPU is the Supermicro > X10SDV-F [2]. The Supermicro web site shows support for FreeBSD 10.1 [3], > but I haven=E2=80=99t seen any use in the wild. I will try to get hold of= a board > to test, but any advance information on support would be useful. > > Thanks, > Will > > [1] > http://ark.intel.com/products/87039/Intel-Xeon-Processor-D-1540-12M-Cache= -2_00-GHz > [2] http://www.supermicro.co.uk/products/motherboard/Xeon/D/X10SDV-F.cfm > [3] http://www.supermicro.co.uk/support/resources/OS/Broadwell-DE.cfm > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Wed Jun 3 20:15:39 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D28D3CBF for ; Wed, 3 Jun 2015 20:15:39 +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 C062B1E56 for ; Wed, 3 Jun 2015 20:15:39 +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 C1FBD1193 for ; Wed, 3 Jun 2015 20:15:38 +0000 (UTC) Date: Wed, 3 Jun 2015 20:15:36 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-stable@freebsd.org Message-ID: <1958553005.13.1433362536304.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to normal : Build-UFS-image #1765 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: Build-UFS-image X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 20:15:39 -0000 See From owner-freebsd-stable@FreeBSD.ORG Thu Jun 4 20:02:58 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9DAC78CE for ; Thu, 4 Jun 2015 20:02:58 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 5C03E166C for ; Thu, 4 Jun 2015 20:02:57 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8F53328426; Thu, 4 Jun 2015 21:57:11 +0200 (CEST) Received: from illbsd.quip.test (ip-89-177-50-74.net.upcbroadband.cz [89.177.50.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 5E9A228423; Thu, 4 Jun 2015 21:57:10 +0200 (CEST) Message-ID: <5570AD96.5030802@quip.cz> Date: Thu, 04 Jun 2015 21:57:10 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Claus Andersen , freebsd-stable@freebsd.org Subject: Re: [SOLVED][BUG??] Re: Unattended install using bsdinstall and ZFS References: <555B141A.3000901@quip.cz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 04 Jun 2015 20:02:58 -0000 Claus Andersen wrote on 05/29/2015 19:17: > Hi! > > A quick re-cap: Want to do an unattended FreeBSD install using > bsdinstall and ZFS. I now have a workaround and consider crying > wol^H^H^Hbug. > > The following minimal install script works as expected for UFS: > > install-ufs.txt > DISTRIBUTIONS="kernel.txz base.txz" > RELEASE="10.1" > PARTITIONS="da0" > > #!/bin/sh > echo "Ready for post installation damage..." > > Invoke with: > bsdinstall script install-ufs.txt > > Now switching to ZFS I would expect the following to work: > > install-zfs1.txt > DISTRIBUTIONS="kernel.txz base.txz" > RELEASE="10.1" > ZFSBOOT_DISKS="da0 da1" > ZFSBOOT_VDEV_TYPE="mirror" > > #!/bin/sh > echo "Ready for post installation damage..." > > Invoke with: > bsdinstall script install-zfs1.txt > > Failure: > - ZFSBOOT_DISKS, ZFSBOOT_VDEV_TYPE not picked up > - Asks for ZFS configuration interactively > > Miroslav Lachman hinted that from looking at the source I should set > NONINTERACTIVE. This does not work. > > Hours later I have figure out the following which works(tm): > > install-zfs2.txt > DISTRIBUTIONS="kernel.txz base.txz" > RELEASE="10.1" > export ZFSBOOT_DISKS="da0 da1" > export ZFSBOOT_VDEV_TYPE="mirror" > export nonInteractive="YES" > > #!/bin/sh > echo "Ready for post installation damage..." > > Invoke with: > bsdinstall script install-zfs2.txt > > This works as expected but it does not sit nice with me. But I am no > guru so I would be very very happy if anyone can confirm if my findings > are bogus or not? There is a huge number of indirect variables which > really confuses me! It seems that either someone is putting in a lot of > indirections but is not done yet - or vice versa. So "proper" usage is > up in the air. > > Findings: > - CAPITAL letters are used for "input" variables > - CamelCase is used for "internal" variables. > - NONINTERACTIVE should be set by default when using "bsdinstall script" > - Setting NONINTERACTIVE manually is not picked up > - Setting nonInteractive works but is bad practice and not intended by > design > - Doing export as part of the bsdinstall script is not what was intended > by design > > Does these findings sound reasonable? If so - would it be fair to > consider the current functionality a bug? Or am I too stupid to get the > feature? > > I can file a PR and help out with test and documentation. But the > current incarnation of bsdinstall is too convoluted for my low level of > script-fu. I am out of free time so I cannot go deeper in this problem. But from what I see I can confirm your findings - it seems like a bug and it would be good if you can file a PR for it so it will not be lost. Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Sat Jun 6 07:50:32 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 413B2A93 for ; Sat, 6 Jun 2015 07:50:32 +0000 (UTC) (envelope-from ortadur@web.de) Received: from mout.web.de (mout.web.de [212.227.15.4]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.web.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF3A2131C for ; Sat, 6 Jun 2015 07:50:31 +0000 (UTC) (envelope-from ortadur@web.de) Received: from [31.16.117.145] by 3capp-webde-bs58.server.lan (via HTTP); Sat, 6 Jun 2015 09:50:22 +0200 MIME-Version: 1.0 Message-ID: From: "Andre Meiser" To: freebsd-stable@freebsd.org Subject: Re: Many core dumps in pthread_getspecific. Content-Type: text/plain; charset=UTF-8 Date: Sat, 6 Jun 2015 09:50:22 +0200 Importance: normal Sensitivity: Normal In-Reply-To: <20150603145838.GX2499@kib.kiev.ua> References: , <20150603145838.GX2499@kib.kiev.ua> X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K0:95seP68/0CdobYc/6uAbDQjOTblQFKpPMQ+gNzm2TEP kjY1WW+HRqMcnBqn9gD7q4fEkYgNlI/L9r4n9ks3Vc/xsuqWhc MtcPgLtFF8Mfm5eiPXORQkovZq1tI/t+1F6z8Ni4oGp/tLCncT ndmrVKsHK30y2pQ2pOza3KhaWxHx3fF0Pe0AhdcQEAofjqoW6C XPYmNvbKgnec9aYzAzy1s80NgRvVpHXbDeimAQh+tHeAPGHHc5 LYg+85Uy1ipoN+sJ2cj24QKMSYrLbp7MEvCUF/zWCt8P0MwxtL 9Yq7HM= X-UI-Out-Filterresults: notjunk:1;V01:K0:6bqqBpAkSbo=:vhTzlhinpALDM7kOHYxgTy Lw8XJ4LUyxhZMxtLyEChqmwO1i3IkFiPo8qCPuZBL1Bq3Xq67VMtbqA411NBWHcAbhLhM9T3O HMR39rxfsbfwk1nnZYsNaXvmCqra72Z6vF2LC1WcLmeHLDT1aiSwX7xTzuXN4kybsiC2l6B79 MGx03kAePdQMySP/nr0MIyWcaTGkM11mGpyHgWgmo6BdgCmy9byJ1CYZz7F3Dtyfpsl4K4g1i bbB9T20oSbvyey3nJD5spxIzV3wrq2t/7o4l823MrDRIw/UVq/kR+YVWht+Tsi6V9BbOm5GLI XMoa+zQ94hCIHKHHRxDIszNBXfJz8XIFIpapgD+GuHICS+0b9TH77IMl5/fn1w7P/4elPxw+M 9G9CBluvYpPSZoICWDdINDRDAz+xaQ36cuu9OJPGTayXb5NYTSGH2oS8KFOwbE83YWXWT2/UJ vF4Hp5qG9A== X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 06 Jun 2015 07:50:32 -0000 On Wed, Jun 03, 2015 at 16:58 +0200, Konstantin Belousov wrote: > You should recompile both libc and libthr with debugging symbols, like > cd /usr/src > (cd lib/libc && make all install DEBUG_FLAGS=-g) > (cd lib/libthr && make all install DEBUG_FLAGS=-g) > then obtain the core dump and post backtraces. Thank you, that was exactly what I was looking for. Now I like FreeBSD even more. ;) I made this short after and also rebooted the entire system to make all programmes use those debug libs. Since than I had not a single core dump. I experienced something similar in the past, that with activated debugging some errors can't be triggered any longer. At the moment I'm happy without crashes and I can work with this system. As soon as I'm getting a new core dump, I'll post the backtrace. If this won't happen for weeks, I may recompile the libs again, try to find a way to trigger the bug on purpose, enable the debug flag again and than provide the info. In the meantime, maybe a core developer may think about the lines of code I'd provided. Why is _get_curthread() compared to NULL at thr_kern.c (line 601) but not at thr_spec.c (line 224)? Either _get_curthread() never ever returns NULL, than it's pointless to test it or it's missing [not only] at thr_spec.c. I'm using activated hyperthreading: % sysctl hw.model hw.machine hw.ncpu hw.model: Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz hw.machine: amd64 hw.ncpu: 8 Sincerely yours Andre. From owner-freebsd-stable@FreeBSD.ORG Sat Jun 6 15:08:33 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0EE10A6D for ; Sat, 6 Jun 2015 15:08:33 +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 A65F613A4 for ; Sat, 6 Jun 2015 15:08:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t56F8LT4063718 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 6 Jun 2015 18:08:22 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t56F8LT4063718 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t56F8LqM063717; Sat, 6 Jun 2015 18:08:21 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 6 Jun 2015 18:08:21 +0300 From: Konstantin Belousov To: Andre Meiser Cc: freebsd-stable@freebsd.org Subject: Re: Many core dumps in pthread_getspecific. Message-ID: <20150606150821.GG2499@kib.kiev.ua> References: <20150603145838.GX2499@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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.20 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, 06 Jun 2015 15:08:33 -0000 On Sat, Jun 06, 2015 at 09:50:22AM +0200, Andre Meiser wrote: > On Wed, Jun 03, 2015 at 16:58 +0200, Konstantin Belousov wrote: > > You should recompile both libc and libthr with debugging symbols, like > > cd /usr/src > > (cd lib/libc && make all install DEBUG_FLAGS=-g) > > (cd lib/libthr && make all install DEBUG_FLAGS=-g) > > then obtain the core dump and post backtraces. > > Thank you, that was exactly what I was looking for. Now I like FreeBSD > even more. ;) > > I made this short after and also rebooted the entire system to make > all programmes use those debug libs. Since than I had not a single > core dump. Which means, most likely, that your installation was corrupted. > > I experienced something similar in the past, that with activated > debugging some errors can't be triggered any longer. > > At the moment I'm happy without crashes and I can work with this > system. As soon as I'm getting a new core dump, I'll post the > backtrace. If this won't happen for weeks, I may recompile the libs > again, try to find a way to trigger the bug on purpose, enable the > debug flag again and than provide the info. > > In the meantime, maybe a core developer may think about the lines > of code I'd provided. Why is _get_curthread() compared to NULL at > thr_kern.c (line 601) but not at thr_spec.c (line 224)? Either > _get_curthread() never ever returns NULL, than it's pointless to test > it or it's missing [not only] at thr_spec.c. Whole thr_kern.c file is 213 lines long in the HEAD. Might be, a core developer has a 601-lines long thr_kern.c. The only way for _get_curthread() to return NULL or, more likely, a garbage, is for the call to _get_curthread() to happens before the threading machinery was initialized. WRT the thr_spec.c, correct code must call pthread_key_create(3) at least once before calling any other pthread_key_*(3) functions. The implementation of pthread_key_create(3) interface, the function _pthread_key_create(), calls _thr_check_init() as the first action, and this helper initializes threading. So if _get_curthread() in any pthread_key_*() function returns NULL or garbage, this is an application' bug. > > I'm using activated hyperthreading: > > % sysctl hw.model hw.machine hw.ncpu hw.model: Intel(R) Xeon(R) CPU > E5-1620 v2 @ 3.70GHz hw.machine: amd64 hw.ncpu: 8 > > Sincerely yours Andre. _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable To > unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sat Jun 6 16:24:46 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5B78B994 for ; Sat, 6 Jun 2015 16:24:46 +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 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1CC3E15C1 for ; Sat, 6 Jun 2015 16:24:46 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1Z1Gtn-000OU6-Ld; Sat, 06 Jun 2015 17:24:43 +0100 Date: Sat, 6 Jun 2015 17:24:43 +0100 From: Gary Palmer To: Konstantin Belousov Cc: Andre Meiser , freebsd-stable@freebsd.org Subject: Re: Many core dumps in pthread_getspecific. Message-ID: <20150606162443.GA29089@in-addr.com> References: <20150603145838.GX2499@kib.kiev.ua> <20150606150821.GG2499@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150606150821.GG2499@kib.kiev.ua> 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.20 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, 06 Jun 2015 16:24:46 -0000 On Sat, Jun 06, 2015 at 06:08:21PM +0300, Konstantin Belousov wrote: > On Sat, Jun 06, 2015 at 09:50:22AM +0200, Andre Meiser wrote: > > On Wed, Jun 03, 2015 at 16:58 +0200, Konstantin Belousov wrote: > > > You should recompile both libc and libthr with debugging symbols, like > > > cd /usr/src > > > (cd lib/libc && make all install DEBUG_FLAGS=-g) > > > (cd lib/libthr && make all install DEBUG_FLAGS=-g) > > > then obtain the core dump and post backtraces. > > > > Thank you, that was exactly what I was looking for. Now I like FreeBSD > > even more. ;) > > > > I made this short after and also rebooted the entire system to make > > all programmes use those debug libs. Since than I had not a single > > core dump. > Which means, most likely, that your installation was corrupted. > > > > > I experienced something similar in the past, that with activated > > debugging some errors can't be triggered any longer. > > > > At the moment I'm happy without crashes and I can work with this > > system. As soon as I'm getting a new core dump, I'll post the > > backtrace. If this won't happen for weeks, I may recompile the libs > > again, try to find a way to trigger the bug on purpose, enable the > > debug flag again and than provide the info. > > > > In the meantime, maybe a core developer may think about the lines > > of code I'd provided. Why is _get_curthread() compared to NULL at > > thr_kern.c (line 601) but not at thr_spec.c (line 224)? Either > > _get_curthread() never ever returns NULL, than it's pointless to test > > it or it's missing [not only] at thr_spec.c. > Whole thr_kern.c file is 213 lines long in the HEAD. > Might be, a core developer has a 601-lines long thr_kern.c. lib/libkse/thread/thr_kern.c is longer and has a _get_curthread() call around line 601. Regards, Gary > The only way for _get_curthread() to return NULL or, more likely, a > garbage, is for the call to _get_curthread() to happens before the > threading machinery was initialized. WRT the thr_spec.c, correct code > must call pthread_key_create(3) at least once before calling any other > pthread_key_*(3) functions. The implementation of pthread_key_create(3) > interface, the function _pthread_key_create(), calls _thr_check_init() > as the first action, and this helper initializes threading. So if > _get_curthread() in any pthread_key_*() function returns NULL or > garbage, this is an application' bug.