From owner-freebsd-current@FreeBSD.ORG Sun May 16 16:21:47 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5350B106566C for ; Sun, 16 May 2010 16:21:47 +0000 (UTC) (envelope-from rrs@lakerest.net) Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by mx1.freebsd.org (Postfix) with ESMTP id D3B568FC13 for ; Sun, 16 May 2010 16:21:46 +0000 (UTC) Received: from [192.168.2.112] (pool-96-238-214-11.snfcca.dsl-w.verizon.net [96.238.214.11]) (authenticated bits=0) by lakerest.net (8.14.3/8.14.3) with ESMTP id o4GGLhbe066785 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Sun, 16 May 2010 12:21:45 -0400 (EDT) (envelope-from rrs@lakerest.net) Message-Id: <7D6DE8CE-1706-4532-8C2E-9693B8006902@lakerest.net> From: Randall Stewart To: FreeBSD Current Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Sun, 16 May 2010 03:38:50 -0700 X-Mailer: Apple Mail (2.936) Subject: an issue with head... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2010 16:21:47 -0000 Hi all: I have head running on a VM (amd64) and when in DDB (from a panic of my making).. I can't call doadump... well I can but it returns a lovely panic recursed on non-recursive mutex in cam... I will try to get a picture next time of the VM window so I can get more information ;-o R ------------------------------ Randall Stewart 803-317-4952 (cell) 803-345-0391(direct) From owner-freebsd-current@FreeBSD.ORG Sun May 16 18:36:47 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 569D1106566C for ; Sun, 16 May 2010 18:36:47 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 055598FC08 for ; Sun, 16 May 2010 18:36:46 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.3/8.14.3) id o4GIamF7005051; Sun, 16 May 2010 18:36:48 GMT (envelope-from kientzle@freebsd.org) Received: from horton.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id e88trz6tvwynimcespzufp6jc2; Sun, 16 May 2010 18:36:47 +0000 (UTC) (envelope-from kientzle@freebsd.org) Message-ID: <4BF03B2D.20402@freebsd.org> Date: Sun, 16 May 2010 11:36:29 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.23) Gecko/20100314 SeaMonkey/1.1.18 MIME-Version: 1.0 To: d@delphij.net References: <4BE9EA4F.9010803@delphij.net> In-Reply-To: <4BE9EA4F.9010803@delphij.net> Content-Type: multipart/mixed; boundary="------------040205040805000403040103" Cc: FreeBSD Current , Luigi Rizzo Subject: Re: [mini headsup] updating from 7.x to -CURRENT after lzma import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2010 18:36:47 -0000 This is a multi-part message in MIME format. --------------040205040805000403040103 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Xin LI wrote: > The recent lzma import has enabled libarchive's lzma support. However, > it have come to our attention that building -HEAD on earlier FreeBSD > versions (specifically, 7.x after 700044 through 8.x before 800022) have > been broken. > > The reason behind this is that 'make buildworld' will build a new ar(1) > binary which links to libarchive, causing build to break on these systems. The following patch partially fixes this problem by just disabling all compression support in ar. (There's definitely no gain in compressing static libraries unless ld can read them. ;-) I don't think this totally fixes the problem. I'd appreciate if someone could try this and let me know how far you get. Tim --------------040205040805000403040103 Content-Type: text/x-patch; name="ar_no_compression.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ar_no_compression.patch" Index: acpyacc.y =================================================================== --- acpyacc.y (revision 208162) +++ acpyacc.y (working copy) @@ -250,7 +250,7 @@ if ((a = archive_read_new()) == NULL) bsdar_errc(bsdar, EX_SOFTWARE, 0, "archive_read_new failed"); - archive_read_support_compression_all(a); + archive_read_support_compression_none(a); archive_read_support_format_ar(a); AC(archive_read_open_file(a, fname, DEF_BLKSZ)); if ((r = archive_read_next_header(a, &entry))) Index: write.c =================================================================== --- write.c (revision 208162) +++ write.c (working copy) @@ -247,7 +247,7 @@ if ((a = archive_read_new()) == NULL) bsdar_errc(bsdar, EX_SOFTWARE, 0, "archive_read_new failed"); - archive_read_support_compression_all(a); + archive_read_support_compression_none(a); archive_read_support_format_ar(a); AC(archive_read_open_filename(a, archive, DEF_BLKSZ)); for (;;) { Index: read.c =================================================================== --- read.c (revision 208162) +++ read.c (working copy) @@ -87,7 +87,7 @@ if ((a = archive_read_new()) == NULL) bsdar_errc(bsdar, EX_SOFTWARE, 0, "archive_read_new failed"); - archive_read_support_compression_all(a); + archive_read_support_compression_none(a); archive_read_support_format_ar(a); AC(archive_read_open_file(a, bsdar->filename, DEF_BLKSZ)); --------------040205040805000403040103-- From owner-freebsd-current@FreeBSD.ORG Sun May 16 19:26:50 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 116691065673; Sun, 16 May 2010 19:26:50 +0000 (UTC) (envelope-from alc@cs.rice.edu) Received: from mail.cs.rice.edu (mail.cs.rice.edu [128.42.1.31]) by mx1.freebsd.org (Postfix) with ESMTP id D0A958FC18; Sun, 16 May 2010 19:26:49 +0000 (UTC) Received: from mail.cs.rice.edu (localhost.localdomain [127.0.0.1]) by mail.cs.rice.edu (Postfix) with ESMTP id 3EA8E2C2A81; Sun, 16 May 2010 14:26:49 -0500 (CDT) X-Virus-Scanned: by amavis-2.4.0 at mail.cs.rice.edu Received: from mail.cs.rice.edu ([127.0.0.1]) by mail.cs.rice.edu (mail.cs.rice.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IJD8U1qADvuv; Sun, 16 May 2010 14:26:41 -0500 (CDT) Received: from adsl-216-63-78-18.dsl.hstntx.swbell.net (adsl-216-63-78-18.dsl.hstntx.swbell.net [216.63.78.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cs.rice.edu (Postfix) with ESMTP id 40C1A2C2AAC; Sun, 16 May 2010 14:26:41 -0500 (CDT) Message-ID: <4BF046F0.7070007@cs.rice.edu> Date: Sun, 16 May 2010 14:26:40 -0500 From: Alan Cox User-Agent: Thunderbird 2.0.0.24 (X11/20100501) MIME-Version: 1.0 To: Benjamin Kaduk References: <20100514053907.GL83316@deviant.kiev.zoral.com.ua> <4BED8ADE.1030100@cs.rice.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , alc@freebsd.org, freebsd-current@freebsd.org Subject: Re: kgdb unuseable with cores on current (for some people) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2010 19:26:50 -0000 Benjamin Kaduk wrote: > On Fri, 14 May 2010, Benjamin Kaduk wrote: > >> On Fri, 14 May 2010, Alan Cox wrote: >> >>> >>> I suspect the following is needed: >>> >>> Index: vm/vm_page.c >>> =================================================================== >>> --- vm/vm_page.c (revision 207823) >>> +++ vm/vm_page.c (working copy) >>> @@ -108,6 +108,7 @@ __FBSDID("$FreeBSD$"); >>> #include >>> #include >>> #include >>> +#include >>> #include >>> #include >>> #include >>> @@ -375,6 +376,14 @@ vm_page_startup(vm_offset_t vaddr) >>> new_end + vm_page_dump_size, VM_PROT_READ | VM_PROT_WRITE); >>> bzero((void *)vm_page_dump, vm_page_dump_size); >>> #endif >>> +#ifdef __amd64__ >>> + pa = DMAP_TO_PHYS((vm_offset_t)msgbufp); > > If I change this to be msgbufp->msg_ptr, then all works as expected. > > While tracking this down, I realized that passing the -q(uiet) > argument to kgdb would have been a valid workaround all along. > > > Alan, could you please commit the modified patch? Yes, it's done. Thanks, Alan From owner-freebsd-current@FreeBSD.ORG Sun May 16 20:18:57 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A9CF106566B; Sun, 16 May 2010 20:18:57 +0000 (UTC) (envelope-from kaiwang27@gmail.com) Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by mx1.freebsd.org (Postfix) with ESMTP id DB4F68FC20; Sun, 16 May 2010 20:18:56 +0000 (UTC) Received: by ewy24 with SMTP id 24so1095133ewy.13 for ; Sun, 16 May 2010 13:18:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received :x-authentication-warning:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=UeBF2IBtsTmFPs0sr1AGTnaMw2Y11URU3DW1gm3wyqo=; b=ftSJvWRZ9t5MxNlZIc/uR27CpL2XnVMtIEKzUVOMsO8dB8SETwH+Rdr3CxwMvL7Aq6 coL0QFTxm36piR7tLgcmE+eR4kAETRQQrdYfJulLzax+5twY+UXcFCJNP9KkfC93M0x8 H9VpZpqQF3HYak/LvILEhR07rK/D0wTWPsMS8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=x-authentication-warning:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; b=MrZ564Tfrfv6mWALI5Tx+0ZK39VfD4bYx+3hF8Gt+IMgfVrBhgQ/LpTUBVnDQEErNC Y3QKOtjxMQGy0DWKLN0iGkrufBpoTsYZp1X4zeyteXq7Hg5R8w9XDK6ipyD78xvPzBrO cSuk5BXDKserQFLCOzd63qaTqHUU9Cv3mcVc0= Received: by 10.213.54.74 with SMTP id p10mr2129026ebg.44.1274039606284; Sun, 16 May 2010 12:53:26 -0700 (PDT) Received: from localhost (81-233-38-26-no36.tbcn.telia.com [81.233.38.26]) by mx.google.com with ESMTPS id 14sm2460209ewy.6.2010.05.16.12.53.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 16 May 2010 12:53:24 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=localhost.my.domain) by localhost with esmtp (Exim 4.71 (FreeBSD)) (envelope-from ) id 1ODjtr-0002v9-GS; Sun, 16 May 2010 21:53:23 +0200 Received: (from kaiw@localhost) by localhost.my.domain (8.14.3/8.14.3/Submit) id o4GJrKpk011230; Sun, 16 May 2010 21:53:20 +0200 (CEST) (envelope-from kaiwang27@gmail.com) X-Authentication-Warning: localhost.my.domain: kaiw set sender to kaiwang27@gmail.com using -f Date: Sun, 16 May 2010 21:53:20 +0200 From: Kai Wang To: Tim Kientzle Message-ID: <20100516195320.GA3347@viskning> References: <4BE9EA4F.9010803@delphij.net> <4BF03B2D.20402@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4BF03B2D.20402@freebsd.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Luigi Rizzo , FreeBSD Current , d@delphij.net Subject: Re: [mini headsup] updating from 7.x to -CURRENT after lzma import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2010 20:18:57 -0000 On Sun, May 16, 2010 at 11:36:29AM -0700, Tim Kientzle wrote: > Xin LI wrote: > > The recent lzma import has enabled libarchive's lzma support. However, > > it have come to our attention that building -HEAD on earlier FreeBSD > > versions (specifically, 7.x after 700044 through 8.x before 800022) have > > been broken. > > > > The reason behind this is that 'make buildworld' will build a new ar(1) > > binary which links to libarchive, causing build to break on these systems. > > The following patch partially fixes this problem by just > disabling all compression support in ar. (There's definitely > no gain in compressing static libraries unless ld can > read them. ;-) I agree compressed ar(1) archive is not so useful without a ld(1) can read it. Also, the current ar(1) compression scheme is not well designed... Inside the elftoolchain project we are planning to rework the ar(1) compression part to make it only compress the member data while leave the member header intact. If the archive is compressed this way, ld(1) can still random access the archive members. In order to implement this compression scheme, we will probably need to use a separate compressor since libarchive always compress the whole archive/stream (if I undertand correctly). So if we are going down this road, removing ar(1) libarchive compression bits right now would not be a bad idea, in my opinion. > I don't think this totally fixes the problem. I'd > appreciate if someone could try this and let me > know how far you get. We also need to remove the compression stuff in the write part. I made a modified patch based on yours, it's available here: http://people.freebsd.org/~kaiw/ar.patch Thanks, Kai From owner-freebsd-current@FreeBSD.ORG Mon May 17 00:30:50 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4156B106564A; Mon, 17 May 2010 00:30:50 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id ADC9D8FC12; Mon, 17 May 2010 00:30:49 +0000 (UTC) X-Spam-Status: No X-Hellug-MailScanner-From: keramida@freebsd.org X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-0.2, required 5, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_50 0.80) X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-ID: o4H0B7Ei019440 Received: from kobe.laptop (ppp-94-64-236-75.home.otenet.gr [94.64.236.75]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-9.1) with ESMTP id o4H0B7Ei019440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 17 May 2010 03:11:14 +0300 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.4/8.14.4) with ESMTP id o4H0B701084785 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 May 2010 03:11:07 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.4/8.14.4/Submit) id o4H0B6O2084782; Mon, 17 May 2010 03:11:06 +0300 (EEST) (envelope-from keramida@freebsd.org) From: Giorgos Keramidas To: Maxim Sobolev References: <4BCF5BAF.7010501@FreeBSD.org> Date: Mon, 17 May 2010 03:11:06 +0300 In-Reply-To: <4BCF5BAF.7010501@FreeBSD.org> (Maxim Sobolev's message of "Wed, 21 Apr 2010 13:10:23 -0700") Message-ID: <877hn3tmjp.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: current@freebsd.org Subject: Re: SYSCTL_XXX(9) manual page deficiency X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2010 00:30:50 -0000 On Wed, 21 Apr 2010 13:10:23 -0700, Maxim Sobolev wrote: > Hi, > > According to the manual page for the SYSCTL_XXX(9) family of > functions, in order to use them one needs to include sys/types.h and > sys/sysctl.h. However, if you do just that the code doesn't compile > due to missing DATA_SET() macros, which is defined in > sys/linker_set.h. My question is whether or not sysctl.h should > include sys/linker_set.h or manual page to be extended to also > suggests that this include is required to use those functions? linker_set.h is a relatively small header that defines only a minimal amount of macros in the public namespace. Some of these symbols are a bit generic, e.g. SET_BEGIN, SET_END, SET_ENTRY, SET_FOREACH and SET_ITEM might conflict with symbol names from other code. On the other hand, the XXX_SET() code is only visible at the end of the SYSCTL_XXX() macros only for kernel code, and it has been there for a *very* long time: since phk committed revision 11863 in 1995. If there ever was a consumer of the kernel API of sysctl.h who had problems with the generic XXX_SET() macros in linker_set.h we'd probably know by now. IMO adding linker_set.h to sysctl.h is fine. From owner-freebsd-current@FreeBSD.ORG Mon May 17 08:00:56 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E4AC1065673; Mon, 17 May 2010 08:00:56 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [IPv6:2001:470:a803::1]) by mx1.freebsd.org (Postfix) with ESMTP id 81D708FC15; Mon, 17 May 2010 08:00:54 +0000 (UTC) Received: from mail.geekcn.org (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id B34CFA565F7; Mon, 17 May 2010 16:00:51 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by mail.geekcn.org (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with LMTP id WrXHZEQtPXTJ; Mon, 17 May 2010 16:00:45 +0800 (CST) Received: from delta.delphij.net (c-24-4-100-103.hsd1.ca.comcast.net [24.4.100.103]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 0D633A550B8; Mon, 17 May 2010 16:00:41 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=E0JINpaDsDneNhCMOKs7ESU/kB49fyRswnmp5xrrI3CYh8va0oq2C1yqq6FXGrxTo PkE6BCVh37TFaeosGP/xw== Message-ID: <4BF0F7A3.7010404@delphij.net> Date: Mon, 17 May 2010 01:00:35 -0700 From: Xin LI Organization: The Geek China Organization User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.9) Gecko/20100408 Thunderbird/3.0.4 ThunderBrowse/3.2.8.1 MIME-Version: 1.0 To: Kai Wang References: <4BE9EA4F.9010803@delphij.net> <4BF03B2D.20402@freebsd.org> <20100516195320.GA3347@viskning> In-Reply-To: <20100516195320.GA3347@viskning> X-Enigmail-Version: 1.0.1 OpenPGP: id=3FCA37C1; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Luigi Rizzo , Tim Kientzle , d@delphij.net, FreeBSD Current Subject: Re: [mini headsup] updating from 7.x to -CURRENT after lzma import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2010 08:00:56 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010/05/16 12:53, Kai Wang wrote: > On Sun, May 16, 2010 at 11:36:29AM -0700, Tim Kientzle wrote: >> Xin LI wrote: >>> The recent lzma import has enabled libarchive's lzma support. However, >>> it have come to our attention that building -HEAD on earlier FreeBSD >>> versions (specifically, 7.x after 700044 through 8.x before 800022) have >>> been broken. >>> >>> The reason behind this is that 'make buildworld' will build a new ar(1) >>> binary which links to libarchive, causing build to break on these systems. >> >> The following patch partially fixes this problem by just >> disabling all compression support in ar. (There's definitely >> no gain in compressing static libraries unless ld can >> read them. ;-) > > I agree compressed ar(1) archive is not so useful without a ld(1) can > read it. Also, the current ar(1) compression scheme is not well > designed... Inside the elftoolchain project we are planning to rework > the ar(1) compression part to make it only compress the member data > while leave the member header intact. If the archive is compressed > this way, ld(1) can still random access the archive members. In order > to implement this compression scheme, we will probably need to use a > separate compressor since libarchive always compress the whole > archive/stream (if I undertand correctly). So if we are going down > this road, removing ar(1) libarchive compression bits right now would > not be a bad idea, in my opinion. > >> I don't think this totally fixes the problem. I'd >> appreciate if someone could try this and let me >> know how far you get. > > We also need to remove the compression stuff in the write part. > I made a modified patch based on yours, it's available here: > > http://people.freebsd.org/~kaiw/ar.patch Yes I think this would fix the issue. (Maybe we should mention that these options would be ignored, in manual page?) Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJL8PeiAAoJEATO+BI/yjfB+vQH/A++3Tb6mxTG04e1/CszIn01 DN/73SeWXd7HT91KbbgaXdf3Or2QZJjiiOE5EHwSn1uxLaXQzAT3mrBvwN/sJC7N Ku/zTm4xwv3H1NYmcOqtC9X+ooHiusNz1PlQFMgHGXZPvziZyfYtaGsqWfUczAjU kr3H4u9OhrhqlMgoyQYWd6GxSe1WN7vFMVkuTcXByERyFlTdL2Xmfbv5np8s8wSF Iz+F+tSqUv/nGJZZJtu4Df/N5Msm0cPKiXhG+rFEINKmQzWjN09j1nwpWWfUDBq1 pmYRDqboQcooGgJUEJaTMRJFmS7RONJGmaUG+O8RVfuRCdQRxFBnrCH70AfguiM= =ZTRC -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Mon May 17 13:24:18 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30152106564A for ; Mon, 17 May 2010 13:24:18 +0000 (UTC) (envelope-from matt.thyer@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 02C658FC19 for ; Mon, 17 May 2010 13:24:17 +0000 (UTC) Received: by pwi9 with SMTP id 9so2910017pwi.13 for ; Mon, 17 May 2010 06:24:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=w48rKNJXIyz934sjvl9EXXLgeXn8NM5PmBGnKmBq2DU=; b=r/7VdUMTTWoJIHIHctD2FoWShq3FZW9q9nTRf97Bw7SJ9aaYlov7xhbf4Zcgx829X0 dGH3YxALLi5DxewoyKQ/c9K2HtwNXuHU+9c8Ywuh1js9etN1T1nwsstT2xqh/jHGJ8Vw 4s6erJx8CM7mYjNcKtDWs1TkhrgDtie86svcw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=p2SxN50IPstseiS5voQQVsTVdCvI9CFxfLkKDVqc8/Js+mNbRkrw/ZrFjtOj0fH9SO PLB4S7PlgZya9aBngvxRX5/0tmehIwXlxGhJvPIYbAb8gkL7ZdC2wE6sf+sDiLgyZzKa wRKegz8YvXI5/Pn7URVl70z3efRnkxWxNYjfA= MIME-Version: 1.0 Received: by 10.140.255.11 with SMTP id c11mr3679012rvi.137.1274102657410; Mon, 17 May 2010 06:24:17 -0700 (PDT) Received: by 10.141.41.14 with HTTP; Mon, 17 May 2010 06:24:17 -0700 (PDT) In-Reply-To: <20100512014651.GN73283@cicely7.cicely.de> References: <3a142e751003291708nc3e110bjca1789cc807f61a2@mail.gmail.com> <20100512014651.GN73283@cicely7.cicely.de> Date: Mon, 17 May 2010 22:54:17 +0930 Message-ID: From: Matt Thyer To: ticso@cicely.de Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: fsck unable to read disk sectors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2010 13:24:18 -0000 On 12 May 2010 11:16, Bernd Walter wrote: > > On Tue, May 11, 2010 at 10:15:13PM +0200, Alexander Best wrote: > > i've posted a log here which is pretty self explanatory: > > > > http://pastebin.com/tn3NiDDW > > [snip] > > One of the typical problems users have is that they forget that > adding a label takes one sector, so the labeled device is smaller. > This is no problem if you create the filesystem on the labeled > drive, but often enough people add the label after creating the > filesystem. FreeBSD's utilities should be able to detect this situation and either correct the filesystem size or refuse to apply the label. > Everything seems to work fine until the FS decides to use that special > sector. > I wouldn't add a label for ufs anyway, since UFS has labeling itself, > which is also handled by glabel module and doesn't require extra space. > Just setup the ufs label with tunefs -L and use the resulting /dev/ufs/... > device. > You only need extra label for swap, but this is not problem, since > it has no persistent ondisk structures. > [snip] > -- > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon May 17 14:02:14 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F21F1065678 for ; Mon, 17 May 2010 14:02:14 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id A972D8FC13 for ; Mon, 17 May 2010 14:02:12 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o4HE2A4o093875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 17 May 2010 16:02:11 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.3/8.14.3) with ESMTP id o4HE27B8033122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 May 2010 16:02:07 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o4HE273L014774; Mon, 17 May 2010 16:02:07 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o4HE27hs014773; Mon, 17 May 2010 16:02:07 +0200 (CEST) (envelope-from ticso) Date: Mon, 17 May 2010 16:02:07 +0200 From: Bernd Walter To: Matt Thyer Message-ID: <20100517140207.GZ92942@cicely7.cicely.de> References: <3a142e751003291708nc3e110bjca1789cc807f61a2@mail.gmail.com> <20100512014651.GN73283@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: freebsd-current@freebsd.org, ticso@cicely.de Subject: Re: fsck unable to read disk sectors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2010 14:02:14 -0000 On Mon, May 17, 2010 at 10:54:17PM +0930, Matt Thyer wrote: > On 12 May 2010 11:16, Bernd Walter wrote: > > > > On Tue, May 11, 2010 at 10:15:13PM +0200, Alexander Best wrote: > > > i've posted a log here which is pretty self explanatory: > > > > > > http://pastebin.com/tn3NiDDW > > > > > [snip] > > > > > One of the typical problems users have is that they forget that > > adding a label takes one sector, so the labeled device is smaller. > > This is no problem if you create the filesystem on the labeled > > drive, but often enough people add the label after creating the > > filesystem. > > FreeBSD's utilities should be able to detect this situation and either > correct the filesystem size or refuse to apply the label. How can this work? glabel doesn't know anything about volume contents - it just writes a label-sector and offers the remaning storage as a new volume. Result: Refusing is impossible. Changing UFS filesystem size isn't an easy task and the last sector is already lost when filesystem comes into game. Result: Too late. I think the only reasonable thing to be done is that fsck can speak up by checking the volume size with the filesystems size _after_ glabel has overwritten the last sector. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Mon May 17 16:01:59 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBC34106564A; Mon, 17 May 2010 16:01:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8A0F68FC12; Mon, 17 May 2010 16:01:59 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 38FF046B91; Mon, 17 May 2010 12:01:59 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 529C98A026; Mon, 17 May 2010 12:01:58 -0400 (EDT) From: John Baldwin To: "Matthew Fleming" Date: Mon, 17 May 2010 10:30:02 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <01NN32EOXMYC006UN1@tmk.com> <01NN3PQCOFHE006UN1@tmk.com> <06D5F9F6F655AD4C92E28B662F7F853E021D4D5E@seaxch09.desktop.isilon.com> In-Reply-To: <06D5F9F6F655AD4C92E28B662F7F853E021D4D5E@seaxch09.desktop.isilon.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201005171030.02740.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 17 May 2010 12:01:58 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, Terry Kennedy Subject: Re: Crash dump problem - sleeping thread owns a non-sleepable lock during crash dump write X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2010 16:01:59 -0000 On Friday 14 May 2010 11:42:44 am Matthew Fleming wrote: > > As an aside, this is a quad-core in one package CPU (an X3363). On both > > this box and a similar one with an X5470, console messages continue to > > print out after "the system has been halted - press any key to reboot" - > > in particular, the shutdown makes a bunch of the "behind the scenes" man- > > agement stuff like the virtual keyboard and monitor appear. Plugging or > > unplugging USB devices will go through the whole deal of detecting and > > making their service available. > > Oops, youre right that other CPUs are running. > > The stop_cpus() call is only made if kdb is entered. doadump() is called out of boot() which comes later. At Isilon weve been running with a patch that does stop_cpus() pretty close to the front of panic(9). > > As an design decision it seems reasonable to call stop_cpus() early in panic(9) simply because most causes for panic means something unexpected, and the sooner the other CPUs arent running the more likely it is that they dont do more damage, leaving the system in a more useful state for dump or {g,d}db analysis. This should be done before dump or entering kdb. > > Im ccing -current@ since I would like a small discussion of moving the stop_cpus() to earlier in panic. If this change is agreeable I can roll up a patch and test it on CURRENT. Im not sure yet how much of the other panic- related changes we have made at Isilon would be required. Right now what happens on x86 is that cpu_reset() actually ends up stopping the other CPUs. It's good that cpu_reset() does this so that 'reset' from DDB works. That said, it would probably be a good thing to stop CPUs earlier during a panic, and even during a normal shutdown. One issue with using stop_cpus() during shutdown is that it is too severe of a stop. That is, stop_cpus() doesn't release the threads currently running. This could be a problem during a normal shutdown if a non-boot CPU is running an interrupt thread needed during shutdown, etc. I think what we really want is a way to take CPUs offline (which Attilio is working on) and use that during a normal shutdown. A quick fix might be a way to force CPUs offline where you have a 'shutdown' or 'offline' mask of sorts and teach the scheduler to only return the idlethread in that case and then send an IPI_PREEMPT to all the CPUs. That will break any pinned or bound threads pinned to non-boot CPUs though. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue May 18 02:18:10 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90699106566B for ; Tue, 18 May 2010 02:18:10 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 62E818FC0A for ; Tue, 18 May 2010 02:18:10 +0000 (UTC) Received: by pvh11 with SMTP id 11so2804740pvh.13 for ; Mon, 17 May 2010 19:18:09 -0700 (PDT) Received: by 10.142.195.20 with SMTP id s20mr4277069wff.248.1274149089784; Mon, 17 May 2010 19:18:09 -0700 (PDT) Received: from [10.0.1.198] (udp022762uds.hawaiiantel.net [72.234.79.107]) by mx.google.com with ESMTPS id x35sm1865545wfh.18.2010.05.17.19.18.08 (version=SSLv3 cipher=RC4-MD5); Mon, 17 May 2010 19:18:09 -0700 (PDT) Date: Mon, 17 May 2010 16:18:06 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: current@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: SUJ Changes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 02:18:10 -0000 I fixed the sparse inode tunefs bug and changed the tunefs behavior based on discussions here on current@. Hopefully this works for everyone. I have one bad perf bug and one journal overflow bug left to resolve. Please keeps the reports coming and thank you for your help. Thanks, Jeff ---------- Forwarded message ---------- Date: Tue, 18 May 2010 01:45:28 +0000 (UTC) From: Jeff Roberson To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r208241 - head/sbin/tunefs Author: jeff Date: Tue May 18 01:45:28 2010 New Revision: 208241 URL: http://svn.freebsd.org/changeset/base/208241 Log: - Round up the journal size to the block size so we don't confuse fsck. Reported by: Mikolaj Golub - Only require 256k of blocks per-cg when trying to allocate contiguous journal blocks. The storage may not actually be contiguous but is at least within one cg. - When disabling SUJ leave SU enabled and report this to the user. It is expected that users will upgrade SU filesystems to SUJ and want a similar downgrade path. Modified: head/sbin/tunefs/tunefs.c Modified: head/sbin/tunefs/tunefs.c ============================================================================== --- head/sbin/tunefs/tunefs.c Tue May 18 00:46:15 2010 (r208240) +++ head/sbin/tunefs/tunefs.c Tue May 18 01:45:28 2010 (r208241) @@ -358,10 +358,12 @@ main(int argc, char *argv[]) warnx("%s remains unchanged as disabled", name); } else { journal_clear(); - sblock.fs_flags &= ~(FS_DOSOFTDEP | FS_SUJ); + sblock.fs_flags &= ~FS_SUJ; sblock.fs_sujfree = 0; - warnx("%s cleared, " - "remove .sujournal to reclaim space", name); + warnx("%s cleared but soft updates still set.", + name); + + warnx("remove .sujournal to reclaim space"); } } } @@ -546,7 +548,7 @@ journal_balloc(void) * Try to minimize fragmentation by requiring a minimum * number of blocks present. */ - if (cgp->cg_cs.cs_nbfree > 128 * 1024 * 1024) + if (cgp->cg_cs.cs_nbfree > 256 * 1024) break; if (contig == 0 && cgp->cg_cs.cs_nbfree) break; @@ -906,6 +908,8 @@ journal_alloc(int64_t size) if (size / sblock.fs_fsize > sblock.fs_fpg) size = sblock.fs_fpg * sblock.fs_fsize; size = MAX(SUJ_MIN, size); + /* fsck does not support fragments in journal files. */ + size = roundup(size, sblock.fs_bsize); } resid = blocks = size / sblock.fs_bsize; if (sblock.fs_cstotal.cs_nbfree < blocks) { From owner-freebsd-current@FreeBSD.ORG Tue May 18 05:35:37 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 302E51065674 for ; Tue, 18 May 2010 05:35:37 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id EFA768FC17 for ; Tue, 18 May 2010 05:35:36 +0000 (UTC) Received: by gyh20 with SMTP id 20so3128294gyh.13 for ; Mon, 17 May 2010 22:35:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.99.13 with SMTP id w13mr7609300ybb.139.1274160935439; Mon, 17 May 2010 22:35:35 -0700 (PDT) Received: by 10.150.137.17 with HTTP; Mon, 17 May 2010 22:35:35 -0700 (PDT) X-Originating-IP: [128.95.133.135] Date: Mon, 17 May 2010 22:35:35 -0700 Message-ID: From: Rob Farmer To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: make release broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 05:35:37 -0000 Hi, make release is broken on current. Seems to be related to the lzma import. This is on i386: cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo test.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo newfs.lo route.lo rtsol.lo tunefs.lo cpio.lo find.lo minigzip.lo sed.lo arp.lo ppp.lo sysinstall.lo usbconfig.lo -ll -ledit -lutil -lmd -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lcam -lsbuf -lufs -ldevinfo -lbsdxml -larchive -lbz2 -lusb -ljail /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x1e6): In function `archive_compressor_xz_init': : undefined reference to `lzma_lzma_preset' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x263): In function `archive_compressor_xz_init': : undefined reference to `lzma_alone_encoder' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x2c9): In function `archive_compressor_xz_init': : undefined reference to `lzma_stream_encoder' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x3ba): In function `drive_compressor': : undefined reference to `lzma_code' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x418): In function `drive_compressor': : undefined reference to `lzma_memusage' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x640): In function `archive_compressor_xz_finish': : undefined reference to `lzma_end' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x9e8): In function `archive_write_mtree_finish_entry': : undefined reference to `SHA1_Final' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xa2e): In function `archive_write_mtree_finish_entry': : undefined reference to `RIPEMD160_Final' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xa78): In function `archive_write_mtree_finish_entry': : undefined reference to `MD5_Final' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe43): In function `archive_write_mtree_data': : undefined reference to `SHA1_Update' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe63): In function `archive_write_mtree_data': : undefined reference to `MD5_Update' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe8b): In function `archive_write_mtree_data': : undefined reference to `RIPEMD160_Update' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x1297): In function `archive_write_mtree_header': : undefined reference to `SHA1_Init' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x12c7): In function `archive_write_mtree_header': : undefined reference to `RIPEMD160_Init' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x12f4): In function `archive_write_mtree_header': : undefined reference to `MD5_Init' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x152): In function `xz_lzma_bidder_init': : undefined reference to `lzma_alone_decoder' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x18c): In function `xz_lzma_bidder_init': : undefined reference to `lzma_stream_decoder' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x2b1): In function `xz_filter_close': : undefined reference to `lzma_end' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x567): In function `xz_filter_read': : undefined reference to `lzma_code' *** Error code 1 Stop in /usr/obj/usr/src/release/boot_crunch. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. -- Rob Farmer From owner-freebsd-current@FreeBSD.ORG Tue May 18 05:39:17 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A9EE1065673; Tue, 18 May 2010 05:39:17 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 08CC78FC12; Tue, 18 May 2010 05:39:16 +0000 (UTC) Received: by qyk11 with SMTP id 11so1886823qyk.13 for ; Mon, 17 May 2010 22:39:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Pr6fBRasrPOk6j+PjTdnvMDQXyyTuR4Ztp/dL+iM+sA=; b=I/Gp9Nuj/Qoped1RK/3yzY/QIoafLpJF5SOaUO6xTI0tjj+JYNS05i4HX19kAZnQbM KyNCm/+PNUY1/O+kqzOgVEx7cxTSDFeshuUB1jEfJvXgmKnyNbumyuyj50ydIt7ET/1z CSVMUGEKXPhq/O8aU3pfBmV5l2FomsbEkXxms= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=itW/12xJy0107V7X6jrl2HNTTGGg41kvkV+R7YI3rcfdkRVPUqY7H4e3nWx7VNHapt Byw3LY9t1CYVGvS63LnWNjWXnVV9ZSmf0zc1KzDI6Kt1W8zyiJvEsJDRDDhGQKgNC8Ll 6t+caWGYCus40Q4O3tVQvL+fehUAIL1+Kucks= MIME-Version: 1.0 Received: by 10.224.44.137 with SMTP id a9mr3447982qaf.218.1274161156074; Mon, 17 May 2010 22:39:16 -0700 (PDT) Received: by 10.229.193.14 with HTTP; Mon, 17 May 2010 22:39:16 -0700 (PDT) In-Reply-To: References: Date: Mon, 17 May 2010 22:39:16 -0700 Message-ID: From: Garrett Cooper To: Rob Farmer Content-Type: text/plain; charset=ISO-8859-1 Cc: Tim Kientzle , current@freebsd.org Subject: Re: make release broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 05:39:17 -0000 On Mon, May 17, 2010 at 10:35 PM, Rob Farmer wrote: > Hi, > > make release is broken on current. Seems to be related to the lzma > import. This is on i386: > > cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo > test.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo > newfs.lo route.lo rtsol.lo tunefs.lo cpio.lo find.lo minigzip.lo > sed.lo arp.lo ppp.lo sysinstall.lo usbconfig.lo -ll -ledit -lutil -lmd > -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lcam -lsbuf > -lufs -ldevinfo -lbsdxml -larchive -lbz2 -lusb -ljail > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x1e6): > In function `archive_compressor_xz_init': > : undefined reference to `lzma_lzma_preset' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x263): > In function `archive_compressor_xz_init': > : undefined reference to `lzma_alone_encoder' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x2c9): > In function `archive_compressor_xz_init': > : undefined reference to `lzma_stream_encoder' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x3ba): > In function `drive_compressor': > : undefined reference to `lzma_code' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x418): > In function `drive_compressor': > : undefined reference to `lzma_memusage' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x640): > In function `archive_compressor_xz_finish': > : undefined reference to `lzma_end' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x9e8): > In function `archive_write_mtree_finish_entry': > : undefined reference to `SHA1_Final' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xa2e): > In function `archive_write_mtree_finish_entry': > : undefined reference to `RIPEMD160_Final' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xa78): > In function `archive_write_mtree_finish_entry': > : undefined reference to `MD5_Final' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe43): > In function `archive_write_mtree_data': > : undefined reference to `SHA1_Update' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe63): > In function `archive_write_mtree_data': > : undefined reference to `MD5_Update' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe8b): > In function `archive_write_mtree_data': > : undefined reference to `RIPEMD160_Update' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x1297): > In function `archive_write_mtree_header': > : undefined reference to `SHA1_Init' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x12c7): > In function `archive_write_mtree_header': > : undefined reference to `RIPEMD160_Init' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x12f4): > In function `archive_write_mtree_header': > : undefined reference to `MD5_Init' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x152): > In function `xz_lzma_bidder_init': > : undefined reference to `lzma_alone_decoder' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x18c): > In function `xz_lzma_bidder_init': > : undefined reference to `lzma_stream_decoder' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x2b1): > In function `xz_filter_close': > : undefined reference to `lzma_end' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x567): > In function `xz_filter_read': > : undefined reference to `lzma_code' > *** Error code 1 > > Stop in /usr/obj/usr/src/release/boot_crunch. > *** Error code 1 > > Stop in /usr/src/release. > + umount /dev > *** Error code 1 > > Stop in /usr/src/release. libopenssl and libmd bits are missing too. Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Tue May 18 07:58:20 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DEFC106566B; Tue, 18 May 2010 07:58:20 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id A915C8FC12; Tue, 18 May 2010 07:58:19 +0000 (UTC) Received: by gyh20 with SMTP id 20so3170227gyh.13 for ; Tue, 18 May 2010 00:58:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=uiAWpvNdMpwIzqf7TfhvFKvG79EqTo9sWdqK5WssER0=; b=j90pX3wW+gKi2tAUZgvKSgkBGhRszuFnVYOeeZQDGOKcZ0BLAXJV4+LxauYOuUexoi V9b5or5n9G9IpKVMHBkq8WGYEtgLRFElBC77z+gO/iBaDnlfFOywCVaF2qIO+aNShf+Y CLwtDKDFfby8vur2SALk6n1Tnh6HH5johuPLk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=A3jjRHpbAbVGEkLZCj3xDB4astmmfbNjKwQzWi/zlMp86Ox/s6GZwGWiIQk3V1ERo7 ARV8buiodkLCAqmQTcaESXNiN+0HtrVCBlzXzkRtmmOPWsyQzS8CtqOcmj/nXniVxwnW pAP4d57DJcvlw5iZR7fOxs9Y1AcKN2LwG5ats= Received: by 10.150.100.14 with SMTP id x14mr7425671ybb.365.1274168090582; Tue, 18 May 2010 00:34:50 -0700 (PDT) Received: from [192.168.31.4] (adsl-99-35-14-184.dsl.klmzmi.sbcglobal.net [99.35.14.184]) by mx.google.com with ESMTPS id p5sm54507301ybe.12.2010.05.18.00.34.48 (version=SSLv3 cipher=RC4-MD5); Tue, 18 May 2010 00:34:49 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4BF24317.8070807@DataIX.net> Date: Tue, 18 May 2010 03:34:47 -0400 From: jhell User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Garrett Cooper References: In-Reply-To: X-Enigmail-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Tim Kientzle , Rob Farmer , current@freebsd.org Subject: Re: make release broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 07:58:20 -0000 On 5/18/2010 1:39 AM, Garrett Cooper wrote: > On Mon, May 17, 2010 at 10:35 PM, Rob Farmer wrote: >> Hi, >> >> make release is broken on current. Seems to be related to the lzma >> import. This is on i386: >> >> cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo >> test.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo >> newfs.lo route.lo rtsol.lo tunefs.lo cpio.lo find.lo minigzip.lo >> sed.lo arp.lo ppp.lo sysinstall.lo usbconfig.lo -ll -ledit -lutil -lmd >> -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lcam -lsbuf >> -lufs -ldevinfo -lbsdxml -larchive -lbz2 -lusb -ljail >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x1e6): >> In function `archive_compressor_xz_init': >> : undefined reference to `lzma_lzma_preset' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x263): >> In function `archive_compressor_xz_init': >> : undefined reference to `lzma_alone_encoder' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x2c9): >> In function `archive_compressor_xz_init': >> : undefined reference to `lzma_stream_encoder' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x3ba): >> In function `drive_compressor': >> : undefined reference to `lzma_code' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x418): >> In function `drive_compressor': >> : undefined reference to `lzma_memusage' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x640): >> In function `archive_compressor_xz_finish': >> : undefined reference to `lzma_end' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x9e8): >> In function `archive_write_mtree_finish_entry': >> : undefined reference to `SHA1_Final' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xa2e): >> In function `archive_write_mtree_finish_entry': >> : undefined reference to `RIPEMD160_Final' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xa78): >> In function `archive_write_mtree_finish_entry': >> : undefined reference to `MD5_Final' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe43): >> In function `archive_write_mtree_data': >> : undefined reference to `SHA1_Update' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe63): >> In function `archive_write_mtree_data': >> : undefined reference to `MD5_Update' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xe8b): >> In function `archive_write_mtree_data': >> : undefined reference to `RIPEMD160_Update' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x1297): >> In function `archive_write_mtree_header': >> : undefined reference to `SHA1_Init' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x12c7): >> In function `archive_write_mtree_header': >> : undefined reference to `RIPEMD160_Init' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x12f4): >> In function `archive_write_mtree_header': >> : undefined reference to `MD5_Init' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x152): >> In function `xz_lzma_bidder_init': >> : undefined reference to `lzma_alone_decoder' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x18c): >> In function `xz_lzma_bidder_init': >> : undefined reference to `lzma_stream_decoder' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x2b1): >> In function `xz_filter_close': >> : undefined reference to `lzma_end' >> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x567): >> In function `xz_filter_read': >> : undefined reference to `lzma_code' >> *** Error code 1 >> >> Stop in /usr/obj/usr/src/release/boot_crunch. >> *** Error code 1 >> >> Stop in /usr/src/release. >> + umount /dev >> *** Error code 1 >> >> Stop in /usr/src/release. > > libopenssl and libmd bits are missing too. > Thanks, > -Garrett This URL looks to be the problem you are seeing above. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=20426+0+current/freebsd-current -- jhell From owner-freebsd-current@FreeBSD.ORG Tue May 18 09:51:36 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66AF01065670 for ; Tue, 18 May 2010 09:51:36 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 0676A8FC1A for ; Tue, 18 May 2010 09:51:35 +0000 (UTC) Received: from park.js.berklix.net (p549A559F.dip.t-dialin.net [84.154.85.159]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id o4I9pUfg047567; Tue, 18 May 2010 09:51:33 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id o4I9pGaQ094062; Tue, 18 May 2010 11:51:25 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id o4I9oQr7041121; Tue, 18 May 2010 11:50:43 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201005180950.o4I9oQr7041121@fire.js.berklix.net> To: Rob Farmer From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Mon, 17 May 2010 22:35:35 PDT." Date: Tue, 18 May 2010 11:50:26 +0200 Sender: jhs@berklix.com Cc: current@freebsd.org Subject: Re: make release broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 09:51:36 -0000 Rob Farmer wrote: > Hi, > > make release is broken on current. Seems to be related to the lzma > import. This is on i386: .......... > : undefined reference to `lzma_end' > /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x567): > In function `xz_filter_read': > : undefined reference to `lzma_code' > *** Error code 1 > > Stop in /usr/obj/usr/src/release/boot_crunch. > *** Error code 1 I saw the same on my amd64 8.0-RELEASE, inside a chroot, building another 8.0-RELEASE. The end of my log below (all I kept, sorry, I'll give it another run now, at the time I assumed it was something wrong in my box). ext+0x392): In function `drive_compressor': : undefined reference to `lzma_code' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x3eb): In function `drive_compressor': : undefined reference to `lzma_memusage' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x5cf): In function `archive_compressor_xz_finish': : undefined reference to `lzma_end' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x96a): In function `archive_write_mtree_finish_entry': : undefined reference to `RIPEMD160_Final' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x9b0): In function `archive_write_mtree_finish_entry': : undefined reference to `SHA1_Final' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x9eb): In function `archive_write_mtree_finish_entry': : undefined reference to `MD5_Final' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xd36): In function `archive_write_mtree_data': : undefined reference to `SHA1_Update' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xd50): In function `archive_write_mtree_data': : undefined reference to `MD5_Update' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xd70): In function `archive_write_mtree_data': : undefined reference to `RIPEMD160_Update' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x1204): In function `archive_write_mtree_header': : undefined reference to `SHA1_Init' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x1238): In function `archive_write_mtree_header': : undefined reference to `RIPEMD160_Init' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x1268): In function `archive_write_mtree_header': : undefined reference to `MD5_Init' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x178): In function `xz_lzma_bidder_init': : undefined reference to `lzma_alone_decoder' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x1a5): In function `xz_lzma_bidder_init': : undefined reference to `lzma_stream_decoder' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x2a9): In function `xz_filter_close': : undefined reference to `lzma_end' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x560): In function `xz_filter_read': : undefined reference to `lzma_code' *** Error code 1 Stop in /usr/obj/usr/src/release/boot_crunch. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text, Not HTML quoted-printable Base64 http://www.asciiribbon.org From owner-freebsd-current@FreeBSD.ORG Tue May 18 15:30:40 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AF601065670 for ; Tue, 18 May 2010 15:30:40 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello089077043238.chello.pl [89.77.43.238]) by mx1.freebsd.org (Postfix) with ESMTP id 9E57D8FC18 for ; Tue, 18 May 2010 15:30:39 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 707E045CA6; Tue, 18 May 2010 17:30:37 +0200 (CEST) Received: from localhost (pdawidek.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 9FE7045C9B; Tue, 18 May 2010 17:30:29 +0200 (CEST) Date: Tue, 18 May 2010 17:30:19 +0200 From: Pawel Jakub Dawidek To: Kostik Belousov Message-ID: <20100518153019.GA1699@garage.freebsd.pl> References: <20100515100401.GT83316@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <20100515100401.GT83316@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=4.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: AESNI driver and fpu_kern KPI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 15:30:40 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 15, 2010 at 01:04:01PM +0300, Kostik Belousov wrote: > Hello, >=20 > please find at http://people.freebsd.org/~kib/misc/aesni.1.patch the > combined patch, containing the fpu_kern KPI and Intel AESNI crypto(9) > driver. I did development and some testing on the hardware generously > provided by Sentex Communications to Netperf cluster. Nice work. Few comments: - Could you modify this chunk in padlock.c: + td =3D curthread; + error =3D fpu_kern_enter(td, &ses->ses_fpu_ctx); + if (error !=3D 0) + goto out; error =3D padlock_hash_setup(ses, macini); + fpu_kern_leave(td, &ses->ses_fpu_ctx); + out: To something without goto, eg.: td =3D curthread; error =3D fpu_kern_enter(td, &ses->ses_fpu_ctx); if (error =3D=3D 0) { error =3D padlock_hash_setup(ses, macini); fpu_kern_leave(td, &ses->ses_fpu_ctx); } - I see that in sys/dev/random/nehemiah.c you don't check for return value of fpu_kern_enter(). That's the only place where you ignore it. Is that intended? - Unfortunately the driver in its current version can't be used with IPsec and with GELI where authentication is enabled. This is because the driver doesn't support sessions where both encryption and authentication is defined. Do you have plans to change it? I saw that you based crypto(9) bits on padlock, which does support sessions with authentication by calculating hashes in software. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkvysooACgkQForvXbEpPzRgIACgmBAAtggqwnb21MTpF1dI+cAB kawAn17T+DC1JxoO+ECEHnXXGEWnbfiI =iy9u -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G-- From owner-freebsd-current@FreeBSD.ORG Tue May 18 18:41:36 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8274F106566B; Tue, 18 May 2010 18:41:36 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 1B63A8FC16; Tue, 18 May 2010 18:41:35 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o4IIfjKf040278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 May 2010 21:41:45 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id o4IIfW49057853; Tue, 18 May 2010 21:41:32 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o4IIfWTU057852; Tue, 18 May 2010 21:41:32 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 18 May 2010 21:41:32 +0300 From: Kostik Belousov To: Pawel Jakub Dawidek Message-ID: <20100518184132.GA83316@deviant.kiev.zoral.com.ua> References: <20100515100401.GT83316@deviant.kiev.zoral.com.ua> <20100518153019.GA1699@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OqXX2KyyhehiiWxy" Content-Disposition: inline In-Reply-To: <20100518153019.GA1699@garage.freebsd.pl> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-current@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: AESNI driver and fpu_kern KPI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 18:41:36 -0000 --OqXX2KyyhehiiWxy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 18, 2010 at 05:30:19PM +0200, Pawel Jakub Dawidek wrote: > On Sat, May 15, 2010 at 01:04:01PM +0300, Kostik Belousov wrote: > > Hello, > >=20 > > please find at http://people.freebsd.org/~kib/misc/aesni.1.patch the > > combined patch, containing the fpu_kern KPI and Intel AESNI crypto(9) > > driver. I did development and some testing on the hardware generously > > provided by Sentex Communications to Netperf cluster. >=20 > Nice work. Few comments: >=20 > - Could you modify this chunk in padlock.c: >=20 > + td =3D curthread; > + error =3D fpu_kern_enter(td, &ses->ses_fpu_ctx); > + if (error !=3D 0) > + goto out; > error =3D padlock_hash_setup(ses, macini); > + fpu_kern_leave(td, &ses->ses_fpu_ctx); > + out: >=20 > To something without goto, eg.: >=20 > td =3D curthread; > error =3D fpu_kern_enter(td, &ses->ses_fpu_ctx); > if (error =3D=3D 0) { > error =3D padlock_hash_setup(ses, macini); > fpu_kern_leave(td, &ses->ses_fpu_ctx); > } Done. >=20 > - I see that in sys/dev/random/nehemiah.c you don't check for return > value of fpu_kern_enter(). That's the only place where you ignore it. > Is that intended? No, thank you, fixed. >=20 > - Unfortunately the driver in its current version can't be used with > IPsec and with GELI where authentication is enabled. This is because > the driver doesn't support sessions where both encryption and > authentication is defined. Do you have plans to change it? > I saw that you based crypto(9) bits on padlock, which does support > sessions with authentication by calculating hashes in software. My goal was to develop fpu_kern_enter() KPI. I used the AESNI as an opportunity to test the KPI in real application. I may consider adding software-implemented authentification sometime later. I would not object if anybody do this instead of me. Since you are there, I want to confirm that you do not have objections against your copyright left in aesni.c. The file was copied from padlock.c and I felt that removing the copyright is wrong. Updated patch, that also includes some other changes, mainly additions to fpu_kern() KPI, that were discussed/requested by Fabien Thomas, is at http://people.freebsd.org/~kib/misc/aesni.2.patch. Thank you for your comments. --OqXX2KyyhehiiWxy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkvy31sACgkQC3+MBN1Mb4jaMQCfQ1jDeLLMjEjS+0Be/3uJtFqA Jr8AoK+qxE2ou8m96ZvW/AXpc58hY932 =mX/Y -----END PGP SIGNATURE----- --OqXX2KyyhehiiWxy-- From owner-freebsd-current@FreeBSD.ORG Tue May 18 19:23:06 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4504C106564A for ; Tue, 18 May 2010 19:23:06 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id C722F8FC08 for ; Tue, 18 May 2010 19:23:05 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id l26so2743625fgb.13 for ; Tue, 18 May 2010 12:23:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:mime-version:content-type:content-disposition:user-agent; bh=XXOn9rRd+0OEdKT16oyx/QrDaEK4dH0CzHzouZiYJyw=; b=GldmIoLdsgo1b/bxNSF9m7S4rpOvx0/B3taixOjmZbv8vT72AqaQCWND+WKx08Vr1I Gw3Bfye1WxpQfi0wD1ea9uvYwyDhnIVvCIEsYnDIZfa57nRiLyIahhpcP+Nc6CcNsywA t6AgJjTPx9OyALiGS4ha7p9EGAtimV3avucSg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; b=XfMu30dNedWGt5JB/rAq2g6VvIh8BVpD5wXVz85PruxoUd2N5azYoUprSz4V213Tk4 nZ6GvgEGNcBQzhUVFVQRI8lMZ+XhC4UUP3XEKJuUyAIOVyUdO6HEwatliArI+8PH8mJV rpfW/HABAfuCDlBPgb3wUHL3u84CQCluQg3VI= Received: by 10.87.74.17 with SMTP id b17mr11502529fgl.59.1274208748317; Tue, 18 May 2010 11:52:28 -0700 (PDT) Received: from fsol ([79.126.67.173]) by mx.google.com with ESMTPS id l12sm9855095fgb.12.2010.05.18.11.52.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 18 May 2010 11:52:27 -0700 (PDT) Date: Tue, 18 May 2010 11:52:20 -0700 From: Roman Bogorodskiy To: current@freebsd.org Message-ID: <20100518185201.GA2745@fsol> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uXxzq0nDebZQVNAZ" Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: ffs_copyonwrite panics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 19:23:06 -0000 --uXxzq0nDebZQVNAZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I've been using -CURRENT last update in February for quite a long time and few weeks ago decided to finally update it. The update was quite unfortunate as system became very unstable: it just hangs few times a day and panics sometimes. Some things can be reproduced, some cannot. Reproducible ones: 1. background fsck always makes system hang 2. system crashes on operations with nullfs mounts (disabled that for now) The most annoying one is ffs_copyonwrite panic which I cannot reproduce. The thing is that if I will run 'startx' on it with some X apps it will panic just in few minutes. When I leave the box with nearly no stress (just use it as internet gateway for my laptop) it behaves a little better but will eventually crash in few hours anyway. The even more annoying thing is that when I cannot save the dump, because when the system boots and runs 'savecore' it leads to fss_copyonwrite panic as well. The panic happens when about 90% complete (as seem via ctrl-t). Any ideas how to debug and get rid of this issue? System arch is amd64. I don't know what other details could be useful. Roman Bogorodskiy --uXxzq0nDebZQVNAZ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iJwEAQECAAYFAkvy4eEACgkQgHRbOB2qykaZOgP/RKmfb6On+5pJz0YZsrZC9U88 ZnvZiX28/M9m+Srubl2b1IkQsFgS+DrulCapumLwMArNAr2WTDb3NaUEJ6fypfCG bNnfbOcQyY9FmYu+amSu9QIhMTAPHippOYcinMmQiATZ6et+CVCaPcbhiP0Rm9sH 7Euh27i7VNx+ovBuUL4= =OIDL -----END PGP SIGNATURE----- --uXxzq0nDebZQVNAZ-- From owner-freebsd-current@FreeBSD.ORG Tue May 18 20:12:02 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 293561065679; Tue, 18 May 2010 20:12:02 +0000 (UTC) (envelope-from fabien.thomas@netasq.com) Received: from work.netasq.com (mars.netasq.com [91.212.116.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6ABD28FC13; Tue, 18 May 2010 20:12:00 +0000 (UTC) Received: from [192.168.0.1] (unknown [172.16.0.46]) by work.netasq.com (Postfix) with ESMTPSA id C5A48740098; Tue, 18 May 2010 22:11:22 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Fabien Thomas In-Reply-To: <20100518184132.GA83316@deviant.kiev.zoral.com.ua> Date: Tue, 18 May 2010 22:11:54 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <56750197-F1C1-45AC-AA6B-72FBA02F24C5@netasq.com> References: <20100515100401.GT83316@deviant.kiev.zoral.com.ua> <20100518153019.GA1699@garage.freebsd.pl> <20100518184132.GA83316@deviant.kiev.zoral.com.ua> To: Kostik Belousov X-Mailer: Apple Mail (2.1078) Cc: freebsd-current@FreeBSD.org, Pawel Jakub Dawidek , freebsd-amd64@FreeBSD.org Subject: Re: AESNI driver and fpu_kern KPI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 20:12:02 -0000 >=20 >>=20 >> - Unfortunately the driver in its current version can't be used with >> IPsec and with GELI where authentication is enabled. This is because >> the driver doesn't support sessions where both encryption and >> authentication is defined. Do you have plans to change it? >> I saw that you based crypto(9) bits on padlock, which does support >> sessions with authentication by calculating hashes in software. > My goal was to develop fpu_kern_enter() KPI. I used the AESNI as an > opportunity to test the KPI in real application. I may consider adding > software-implemented authentification sometime later. I would not = object > if anybody do this instead of me. Today I've tested the patch with the same "issue" with IPsec, i've quickly re-included the same keyed hash function than padlock to = test, tomorrow I will test again and I will post a patch if it works well. A minor things: aesni only compile as a module. Another idea for Sha1 would be to integrate the new version from intel = http://software.intel.com/en-us/articles/improving-the-performance-of-the-= secure-hash-algorithm-1/ but it seems the 32bits version is not available at this time (and same licencing issue). Regards, Fabien From owner-freebsd-current@FreeBSD.ORG Tue May 18 20:59:13 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABB781065672 for ; Tue, 18 May 2010 20:59:13 +0000 (UTC) (envelope-from fk@fabiankeil.de) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.31.38]) by mx1.freebsd.org (Postfix) with ESMTP id 18BD48FC12 for ; Tue, 18 May 2010 20:59:12 +0000 (UTC) Received: from [78.34.140.135] (helo=r500.local) by smtprelay04.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1OETi0-00049E-8G; Tue, 18 May 2010 22:48:12 +0200 Date: Tue, 18 May 2010 22:48:19 +0200 From: Fabian Keil To: Roman Bogorodskiy Message-ID: <20100518224819.28d9624b@r500.local> In-Reply-To: <20100518185201.GA2745@fsol> References: <20100518185201.GA2745@fsol> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.20.1; amd64-portbld-freebsd9.0) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/fk-2008-08-18.asc Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/ULCw+2R6QiNFyA4SQLvZX9X"; protocol="application/pgp-signature" X-Df-Sender: 180909 X-Mailman-Approved-At: Tue, 18 May 2010 21:16:04 +0000 Cc: current@freebsd.org Subject: Re: ffs_copyonwrite panics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 20:59:13 -0000 --Sig_/ULCw+2R6QiNFyA4SQLvZX9X Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Roman Bogorodskiy wrote: > I've been using -CURRENT last update in February for quite a long time > and few weeks ago decided to finally update it. The update was quite > unfortunate as system became very unstable: it just hangs few times a > day and panics sometimes. >=20 > Some things can be reproduced, some cannot. Reproducible ones: >=20 > 1. background fsck always makes system hang > 2. system crashes on operations with nullfs mounts (disabled that for > now) >=20 > The most annoying one is ffs_copyonwrite panic which I cannot reproduce. > The thing is that if I will run 'startx' on it with some X apps it will > panic just in few minutes. When I leave the box with nearly no stress > (just use it as internet gateway for my laptop) it behaves a little > better but will eventually crash in few hours anyway. >=20 > The even more annoying thing is that when I cannot save the dump, > because when the system boots and runs 'savecore' it leads to > fss_copyonwrite panic as well. The panic happens when about 90% complete > (as seem via ctrl-t). >=20 > Any ideas how to debug and get rid of this issue? >=20 > System arch is amd64. I don't know what other details could be useful. I'm not familiar with the background fsck issue, but if the nullfs panic looks like this one, there's a fair chance it's already fixed: Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x10 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff82412f14 stack pointer =3D 0x28:0xffffff803e564620 frame pointer =3D 0x28:0xffffff803e564770 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 1825 (jail) panic: from debugger cpuid =3D 0 Uptime: 38s Dumping 1992 MB (5 chunks) chunk 0: 1MB (155 pages) ... ok chunk 1: 1990MB (509345 pages) 1974 [...] 6 ... ok chunk 2: 2MB (273 pages) ... ok chunk 3: 1MB (184 pages) #0 doadump () at pcpu.h:223 223 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:223 #1 0xffffffff803c506f in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:416 #2 0xffffffff803c546c in panic (fmt=3DVariable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:590 #3 0xffffffff801f6e77 in db_panic (addr=3DVariable "addr" is not available. ) at /usr/src/sys/ddb/db_command.c:478 #4 0xffffffff801f7281 in db_command (last_cmdp=3D0xffffffff808bfd80, cmd_t= able=3DVariable "cmd_table" is not available. ) at /usr/src/sys/ddb/db_command.c:445 #5 0xffffffff801f74d0 in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 #6 0xffffffff801f9429 in db_trap (type=3DVariable "type" is not available. ) at /usr/src/sys/ddb/db_main.c:229 #7 0xffffffff803f3c25 in kdb_trap (type=3D12, code=3D0, tf=3D0xffffff803e5= 64570) at /usr/src/sys/kern/subr_kdb.c:535 #8 0xffffffff8062ad9d in trap_fatal (frame=3D0xffffff803e564570, eva=3DVar= iable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:773 #9 0xffffffff8062b0fc in trap_pfault (frame=3D0xffffff803e564570, usermode= =3D0) at /usr/src/sys/amd64/amd64/trap.c:694 #10 0xffffffff8062b8ff in trap (frame=3D0xffffff803e564570) at /usr/src/sys/amd64/amd64/trap.c:451 #11 0xffffffff80611f33 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:223 #12 0xffffffff82412f14 in null_bypass (ap=3D0xffffff803e564780) at /usr/src/sys/modules/nullfs/../../fs/nullfs/null_vnops.c:269 #13 0xffffffff80448104 in vgonel (vp=3D0xffffff0005e05780) at vnode_if.h:10= 99 #14 0xffffffff8044835e in vrecycle (vp=3D0xffffff0005e05780, td=3DVariable = "td" is not available. ) at /usr/src/sys/kern/vfs_subr.c:2505 #15 0xffffffff82412e6f in null_inactive (ap=3DVariable "ap" is not availabl= e. ) at /usr/src/sys/modules/nullfs/../../fs/nullfs/null_vnops.c:665 #16 0xffffffff80444ff8 in vinactive (vp=3D0xffffff0005e05780,=20 td=3D0xffffff00054743e0) at vnode_if.h:807 #17 0xffffffff804495dd in vputx (vp=3D0xffffff0005e05780, func=3D2) at /usr/src/sys/kern/vfs_subr.c:2226 #18 0xffffffff8043e1ae in lookup (ndp=3D0xffffff803e564a50) at /usr/src/sys/kern/vfs_lookup.c:905 #19 0xffffffff8043eef7 in namei (ndp=3D0xffffff803e564a50) at /usr/src/sys/kern/vfs_lookup.c:269 #20 0xffffffff8044ec86 in kern_accessat (td=3D0xffffff00054743e0, fd=3D-100= ,=20 path=3D0x800537000
, pathseg=3DVaria= ble "pathseg" is not available. ) at /usr/src/sys/kern/vfs_syscalls.c:2140 #21 0xffffffff8062b21d in syscall (frame=3D0xffffff803e564c80) at /usr/src/sys/amd64/amd64/trap.c:946 #22 0xffffffff80612211 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:374 #23 0x000000080050e5ec in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb)=20 I got it reproducible with: FreeBSD 9.0-CURRENT #66 r+3fe665b: Fri May 14 17:45:10 CEST 2010 fk@r500.local:/usr/obj/usr/src/sys/ZOEY amd64 but it had already been fixed in Subversion/CVS on Saturday so I didn't investigate which commit caused it and which one fixed it. My previous kernel without the issue was: FreeBSD 9.0-CURRENT #65 r+6f48909: Sat May 8 19:28:58 CEST 2010 I'm currently using: FreeBSD 9.0-CURRENT #69 r+3a7afc7: Sun May 16 20:04:53 CEST 2010 without any issues either. I don't use background fsck, though. Fabian --Sig_/ULCw+2R6QiNFyA4SQLvZX9X Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkvy/RcACgkQSMVSH78upWORUgCePNh7EXdAVeybbfwOG0IOv+pJ 7HkAnRgunNyTSh5tJS7uJb5fDBOr4R8c =Qz9Q -----END PGP SIGNATURE----- --Sig_/ULCw+2R6QiNFyA4SQLvZX9X-- From owner-freebsd-current@FreeBSD.ORG Tue May 18 21:32:45 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B017106566B for ; Tue, 18 May 2010 21:32:45 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by mx1.freebsd.org (Postfix) with ESMTP id E64238FC15 for ; Tue, 18 May 2010 21:32:44 +0000 (UTC) Received: by ewy1 with SMTP id 1so193919ewy.13 for ; Tue, 18 May 2010 14:32:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=nZTRKIeUYErHgY/DJ9nggWYSLSUncMEA34y6jZ4CbfU=; b=MyjqNwz26zE3500ELwKUo/Vb1xp67UvXM9aXXRCwRVwjWdTHtB75AGFF46TX5QEpCj /EoJ10dUpYlEiinb4VoeOU9wgp9ZEvduTf5yUZymdP0VqTyTU3Ru4hV4Iyylgbv5nSoe cXKYt3CLVahLiL91trFiDAfRpRJk8XjlU9g1Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Is0Y8pPT385VMd1Ht4ajGaZVmD4zub0b0OZmhb0Hr+OpJAXlzxyeq8UmrJmb0Ndgs/ CZS/5b45C4bxqNWd6kyb+u11+WPhxDm1kiIpz+vJby0URdVi2IuS5JAxcsnxLVhDERVd ELgeYa2LI95cVY1WW9GoVjq51WANMVRjYYdpE= MIME-Version: 1.0 Received: by 10.213.3.9 with SMTP id 9mr3387378ebl.20.1274218363890; Tue, 18 May 2010 14:32:43 -0700 (PDT) Received: by 10.213.16.138 with HTTP; Tue, 18 May 2010 14:32:43 -0700 (PDT) Date: Tue, 18 May 2010 17:32:43 -0400 Message-ID: From: Ryan Stone To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Subject: HEAD can't bring up APs on Intel LC5528(Jasper Forest) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 21:32:45 -0000 I'm trying to bring up a new board based on Intel's Jasper Forest x86 processor. I can boot a kernel without SMP without any problems, but FreeBSD is not able to start up the Application Processors if I enable SMP. The error message that I get is: AP #2 (PHY# 2) failed! panic y/n? [y] This was a i386 kernel built from HEAD as May 2nd or so. It's not always PHY#2. Some number of APs manage to start up correctly, but one usually fails. I have observed one instance where all of the APs came up properly, so it seems as though there's some kind of race that I stand a very good chance of losing at least one time in seven tries. If I disable all but one AP through device.hints I stand a pretty good chance of successfully starting that AP and booting correctly. I've been banging my head against the wall for a while now and all indications are that the AP never starts at all. I enabled the CHECK_POINTS compile-time option and and nothing ever gets written to the CMOS for the AP that fails to start. Writing to the CMOS is the second thing that the AP does after doing a cli so it's a good bet that the AP never hits that code. Linux (version 2.6.28-11) is able to boot and start the APs just fine. My suspicion is that Linux is explicitly configuring something that FreeBSD is trusting the BIOS to do. We do have the reference board around, but we're having trouble getting the original Intel BIOS programmed into it. If we can get that working again I'll let you know whether FreeBSD can boot on it. If anybody can offer any hints or ideas for debugging this it'd be greatly appreciated, as right now I'm reduced to grasping at straws. From owner-freebsd-current@FreeBSD.ORG Tue May 18 23:24:50 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2485C1065670 for ; Tue, 18 May 2010 23:24:50 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id A289A8FC0C for ; Tue, 18 May 2010 23:24:49 +0000 (UTC) Received: by wye20 with SMTP id 20so82038wye.13 for ; Tue, 18 May 2010 16:24:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=EfRFOr8BuyLIE8ytvTMIhiONZB85rgMNSc575Fqoy7w=; b=d0kFV7EpmRGQKcRLEEV7z6bHX2L6sZ6uWrMb5hnH33hp1h6VKUqW0BpZmfI4B6BfZA Mc1hbW33DyBORBUZySVUT7nD+3o/9OnL9iCeTDSAmJ9MJheAXhkjS4luXgBH3s82GHtw nfUQRpsi34Li23saz38YbwENz3KimzwZj/Mgk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xTdChzYJFv2ylLt5EYi7UL2M18nAtkfwfagV9sf//ET90xP8y4Btt13Z0ie/Nc3ZzN 0hRovNCKCGbVQBWe7U59MuPDTbI0WMIEVCpwo0OUzTF3hIc0c2J72r5Cbo0KXsugKo28 ysM+DFE7SGX+wTa251Am59OB4P5rChsHSbwtY= MIME-Version: 1.0 Received: by 10.216.89.135 with SMTP id c7mr2813482wef.132.1274225086654; Tue, 18 May 2010 16:24:46 -0700 (PDT) Received: by 10.216.29.129 with HTTP; Tue, 18 May 2010 16:24:46 -0700 (PDT) In-Reply-To: References: Date: Tue, 18 May 2010 16:24:46 -0700 Message-ID: From: Jack Vogel To: Ryan Stone Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Current Subject: Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 23:24:50 -0000 What if you use amd64, have you tried that? Low level code is different. Interesting however, maybe I can get access to one around here, will see. Jack On Tue, May 18, 2010 at 2:32 PM, Ryan Stone wrote: > I'm trying to bring up a new board based on Intel's Jasper Forest x86 > processor. I can boot a kernel without SMP without any problems, but > FreeBSD is not able to start up the Application Processors if I enable > SMP. The error message that I get is: > > AP #2 (PHY# 2) failed! > panic y/n? [y] > > This was a i386 kernel built from HEAD as May 2nd or so. It's not > always PHY#2. Some number of APs manage to start up correctly, but > one usually fails. I have observed one instance where all of the APs > came up properly, so it seems as though there's some kind of race that > I stand a very good chance of losing at least one time in seven tries. > If I disable all but one AP through device.hints I stand a pretty > good chance of successfully starting that AP and booting correctly. > > I've been banging my head against the wall for a while now and all > indications are that the AP never starts at all. I enabled the > CHECK_POINTS compile-time option and and nothing ever gets written to > the CMOS for the AP that fails to start. Writing to the CMOS is the > second thing that the AP does after doing a cli so it's a good bet > that the AP never hits that code. > > Linux (version 2.6.28-11) is able to boot and start the APs just fine. > My suspicion is that Linux is explicitly configuring something that > FreeBSD is trusting the BIOS to do. > > We do have the reference board around, but we're having trouble > getting the original Intel BIOS programmed into it. If we can get > that working again I'll let you know whether FreeBSD can boot on it. > > If anybody can offer any hints or ideas for debugging this it'd be > greatly appreciated, as right now I'm reduced to grasping at straws. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue May 18 23:40:14 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAE52106564A for ; Tue, 18 May 2010 23:40:14 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by mx1.freebsd.org (Postfix) with ESMTP id 3F26A8FC15 for ; Tue, 18 May 2010 23:40:13 +0000 (UTC) Received: by ewy1 with SMTP id 1so217225ewy.13 for ; Tue, 18 May 2010 16:40:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=A2F86Hqnrwy1kf8B/5RCLGT4RJsUOOFtW+RahNIjlxU=; b=txahlfuqTndSkFr8I0YE2/4v0cvO9vah9doci5kUuKp0Y+SfILf+AIl4babaJUXR73 TMnOvnXgFYcqxCpU+XxXqt39T0jc99RMz6OqBnn48A2y1d8uKOrLAfUKqwDICgZVB1JW noIDOPwTj76Fx9DHGVAm5QvZP1EBhjYitQGBU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=uScibVhaYKsSWavlskm2P8qvF40zP7LEuovEErgnNVOf3n6r8WZYriWjSClordEd65 C3ykBXdX2gQg/5SHdQsvGqKLB4swi7vgoEclbBqS6YnhQJA6QxMn7od48mXaZR5zRXt+ Wd7A4AS2KErY2ey9JokW5OG4ewHW2omlaXyFg= MIME-Version: 1.0 Received: by 10.213.43.140 with SMTP id w12mr3038244ebe.42.1274226013097; Tue, 18 May 2010 16:40:13 -0700 (PDT) Received: by 10.213.16.138 with HTTP; Tue, 18 May 2010 16:40:13 -0700 (PDT) In-Reply-To: References: Date: Tue, 18 May 2010 19:40:13 -0400 Message-ID: From: Ryan Stone To: Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current Subject: Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2010 23:40:14 -0000 amd64 exhibits the same problem, except that it's not even polite and panics without even asking. From owner-freebsd-current@FreeBSD.ORG Wed May 19 00:08:35 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54BEB106566B for ; Wed, 19 May 2010 00:08:35 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id DD9108FC0C for ; Wed, 19 May 2010 00:08:34 +0000 (UTC) Received: by wye20 with SMTP id 20so104890wye.13 for ; Tue, 18 May 2010 17:08:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=MmHt4DK0RChwV5b7DdYWQGm8DBturBnl4gNSGfmQv0g=; b=F4ZAJO2Lwy1dLViAzuGih7JZvsfVXaZd9M0p/Ks0tBuqL+mklJfC8Jcl8Lxcov+9ky kRmZQmsVJtlPz7Twz9OQZP5Iym1dIkD+Qo+I+AT2XLhEnerS5PKcoDKA31a5pI0/oNpT aMQFgCmzB2Y1Uwf+lcNhR6pL0I3vFHCpyZLUE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=X8Vys8BRCtbBS5mIqwZ5vwN4zqsfN7cct2FqKQ+HaQ4H7wB4pM4elPX7rB3z/hrjsW iLtMYL6P6nRSIYjz+zKHj+TEKDntxgi9vwSjUCReH1+PvuBmrBnMfZZHpOKtNUzMpJ3G uDT3VCfCP5fcjFPAJ2GAppxzFmyG80gfiS3Og= MIME-Version: 1.0 Received: by 10.216.169.72 with SMTP id m50mr4609717wel.169.1274227713857; Tue, 18 May 2010 17:08:33 -0700 (PDT) Received: by 10.216.29.129 with HTTP; Tue, 18 May 2010 17:08:33 -0700 (PDT) In-Reply-To: References: Date: Tue, 18 May 2010 17:08:33 -0700 Message-ID: From: Jack Vogel To: Ryan Stone Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Current Subject: Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 May 2010 00:08:35 -0000 LOL, ok, I'm beating the bushes here Ryan, and I think I can get a system although it may be a day or two. Will let you know. Jack On Tue, May 18, 2010 at 4:40 PM, Ryan Stone wrote: > amd64 exhibits the same problem, except that it's not even polite and > panics without even asking. > From owner-freebsd-current@FreeBSD.ORG Wed May 19 01:42:40 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A74B9106566B for ; Wed, 19 May 2010 01:42:40 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-qy0-f188.google.com (mail-qy0-f188.google.com [209.85.221.188]) by mx1.freebsd.org (Postfix) with ESMTP id 55ABA8FC0A for ; Wed, 19 May 2010 01:42:40 +0000 (UTC) Received: by qyk26 with SMTP id 26so4468236qyk.28 for ; Tue, 18 May 2010 18:42:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type; bh=FAOkTaRKhqmWR2I0vwSPzjSGueNIcIGCny78xoC6LF0=; b=dOddtMTm5xDTsvp3iz2R/faUsOhrq+LyZoZw1dE7pb2HPJSuntP+pQAMf/PTqxcuR8 jXTUaXEgNkSWVO2PeFhKte2kAs7Yq0V409luHRqOYCYrGCfE471HJtchzf/ObBDXTFEd 2vQaSPkh7kv8UxfwUJjfhLQrNyeRTkJs5cfR8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; b=lMcpAE0lpFhsfmbCWByq4UZcUUz1bFkGnJmKSlYifep8ZqcbK9AcFNZcXt/9xeIhJg KsbOvNJJVu2HZPrS24VdRegYFRcvOKv3lPKl6iVfMkNL5wONFFw+/z3NcUr64ImTy3n7 PXI9V6eKtVhnsur2smutOyfB82ztqVm7giUM4= Received: by 10.224.25.203 with SMTP id a11mr4209254qac.104.1274233359333; Tue, 18 May 2010 18:42:39 -0700 (PDT) Received: from kan.dnsalias.net (c-24-63-226-98.hsd1.ma.comcast.net [24.63.226.98]) by mx.google.com with ESMTPS id 22sm4258860qyk.2.2010.05.18.18.42.37 (version=SSLv3 cipher=RC4-MD5); Tue, 18 May 2010 18:42:38 -0700 (PDT) Date: Tue, 18 May 2010 21:42:32 -0400 From: Alexander Kabaev To: Ryan Stone Message-ID: <20100518214232.35dfa23f@kan.dnsalias.net> In-Reply-To: References: X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/0J8N9RVnvolZC+P3ltfeKlG"; protocol="application/pgp-signature" Cc: FreeBSD Current , Jack Vogel Subject: Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 May 2010 01:42:40 -0000 --Sig_/0J8N9RVnvolZC+P3ltfeKlG Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 18 May 2010 19:40:13 -0400 Ryan Stone wrote: > amd64 exhibits the same problem, except that it's not even polite and > panics without even asking. Could you please try disabling legacy USB device support in BIOS if such an option is provided in your BIOS setup and see if that changes anything? --=20 Alexander Kabaev --Sig_/0J8N9RVnvolZC+P3ltfeKlG Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iD8DBQFL80INQ6z1jMm+XZYRAk8rAKCLgbetWfp3iIqRJt9KXQt0hrR76gCgmLwu 4izHnM+Y58Gfxm16BMknhsU= =/m1U -----END PGP SIGNATURE----- --Sig_/0J8N9RVnvolZC+P3ltfeKlG-- From owner-freebsd-current@FreeBSD.ORG Wed May 19 10:38:11 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F07D0106567E for ; Wed, 19 May 2010 10:38:10 +0000 (UTC) (envelope-from matt.thyer@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id C27C38FC21 for ; Wed, 19 May 2010 10:38:10 +0000 (UTC) Received: by pxi7 with SMTP id 7so2393441pxi.13 for ; Wed, 19 May 2010 03:38:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=sUrwkOkoCXN+XJkCVnHv44jm5kmfVxxdqB+AMHEkSLM=; b=rkE2n1mq2aNVFIaQhxhyLLHXQ7yeQE5i6GmrkPZQdlpip/Y0BAtf3OMrwPBCF0lJUe 5kXvA7sAGCg5kv0gdqjAenrjyEZYqLgG9Do2fwqBxZul4YpCZtfzErCn0H67E2RQcE/4 isZQsgc8WIJWkucaQ/GU9GnRsy0vMX3I7Oz+k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YcnbvlrVh9Pg8Rxa/Tcc54lIy+1sNb1HF//V4kJ+7V66OdawAevrVRHvgpw7yLsWqW r4WEe7NQv46pjfbP73Fwrd81MjwAVU7OOjNAS5ZnDmQuu/PoKwZpBcq3L3dR07TOIhzL oVJo1W6ueM2RfKzzRCN0ZVaTvBKcrqClfpWkw= MIME-Version: 1.0 Received: by 10.141.139.21 with SMTP id r21mr6270660rvn.2.1274265490242; Wed, 19 May 2010 03:38:10 -0700 (PDT) Received: by 10.141.41.14 with HTTP; Wed, 19 May 2010 03:38:10 -0700 (PDT) In-Reply-To: <20100517140207.GZ92942@cicely7.cicely.de> References: <3a142e751003291708nc3e110bjca1789cc807f61a2@mail.gmail.com> <20100512014651.GN73283@cicely7.cicely.de> <20100517140207.GZ92942@cicely7.cicely.de> Date: Wed, 19 May 2010 20:08:10 +0930 Message-ID: From: Matt Thyer To: ticso@cicely.de Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: fsck unable to read disk sectors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 May 2010 10:38:11 -0000 It wouldn't be the BSD way to try to stop the user shooting themselves in the foot. And I agree too as it wouldn't be right for glabel to try to keep track of all possible uses for a volume and know whether each is present. That would be a typical Linux type solution. However, would it be too much for glabel to just know about UFS and tell the user to use tunefs instead if there appears to be a UFS filesystem present ? On 17 May 2010 23:32, Bernd Walter wrote: > On Mon, May 17, 2010 at 10:54:17PM +0930, Matt Thyer wrote: >> On 12 May 2010 11:16, Bernd Walter wrote: >> > >> > On Tue, May 11, 2010 at 10:15:13PM +0200, Alexander Best wrote: >> > > i've posted a log here which is pretty self explanatory: >> > > >> > > http://pastebin.com/tn3NiDDW >> > > >> >> [snip] >> >> > >> > One of the typical problems users have is that they forget that >> > adding a label takes one sector, so the labeled device is smaller. >> > This is no problem if you create the filesystem on the labeled >> > drive, but often enough people add the label after creating the >> > filesystem. >> >> FreeBSD's utilities should be able to detect this situation and either >> correct the filesystem size or refuse to apply the label. > > How can this work? > glabel doesn't know anything about volume contents - it just writes a > label-sector and offers the remaning storage as a new volume. > Result: Refusing is impossible. > Changing UFS filesystem size isn't an easy task and the last sector is > already lost when filesystem comes into game. > Result: Too late. > I think the only reasonable thing to be done is that fsck can speak > up by checking the volume size with the filesystems size _after_ glabel > has overwritten the last sector. > > -- > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > From owner-freebsd-current@FreeBSD.ORG Wed May 19 11:15:00 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C9A41065678 for ; Wed, 19 May 2010 11:14:50 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id E95E58FC08 for ; Wed, 19 May 2010 11:14:49 +0000 (UTC) Received: by mail-pw0-f54.google.com with SMTP id 9so4095101pwi.13 for ; Wed, 19 May 2010 04:14:49 -0700 (PDT) Received: by 10.141.2.4 with SMTP id e4mr6179837rvi.60.1274267598522; Wed, 19 May 2010 04:13:18 -0700 (PDT) Received: from [10.0.1.198] (udp022762uds.hawaiiantel.net [72.234.79.107]) by mx.google.com with ESMTPS id b12sm6082803rvn.22.2010.05.19.04.13.16 (version=SSLv3 cipher=RC4-MD5); Wed, 19 May 2010 04:13:17 -0700 (PDT) Date: Wed, 19 May 2010 01:13:12 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: Roman Bogorodskiy In-Reply-To: <20100518185201.GA2745@fsol> Message-ID: References: <20100518185201.GA2745@fsol> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: ffs_copyonwrite panics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 May 2010 11:15:00 -0000 On Tue, 18 May 2010, Roman Bogorodskiy wrote: > Hi, > > I've been using -CURRENT last update in February for quite a long time > and few weeks ago decided to finally update it. The update was quite > unfortunate as system became very unstable: it just hangs few times a > day and panics sometimes. > > Some things can be reproduced, some cannot. Reproducible ones: > > 1. background fsck always makes system hang > 2. system crashes on operations with nullfs mounts (disabled that for > now) > > The most annoying one is ffs_copyonwrite panic which I cannot reproduce. > The thing is that if I will run 'startx' on it with some X apps it will > panic just in few minutes. When I leave the box with nearly no stress > (just use it as internet gateway for my laptop) it behaves a little > better but will eventually crash in few hours anyway. This may have been my fault. Can you please update and let me know if it is resolved? There was both a deadlock and a copyonwrite panic as a result of the softupdates journaling import. I just fixed the deadlock today. Thanks, Jeff > > The even more annoying thing is that when I cannot save the dump, > because when the system boots and runs 'savecore' it leads to > fss_copyonwrite panic as well. The panic happens when about 90% complete > (as seem via ctrl-t). > > Any ideas how to debug and get rid of this issue? > > System arch is amd64. I don't know what other details could be useful. > > Roman Bogorodskiy > From owner-freebsd-current@FreeBSD.ORG Wed May 19 16:12:39 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D028C106564A for ; Wed, 19 May 2010 16:12:39 +0000 (UTC) (envelope-from ambrosehua@gmail.com) Received: from mail-qy0-f188.google.com (mail-qy0-f188.google.com [209.85.221.188]) by mx1.freebsd.org (Postfix) with ESMTP id 87E908FC17 for ; Wed, 19 May 2010 16:12:39 +0000 (UTC) Received: by qyk26 with SMTP id 26so5689699qyk.28 for ; Wed, 19 May 2010 09:12:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=neVr592WYv1SaEYstYgmkJiUp1V0U9oK+ciEl/puWuo=; b=FOC6xrd8uKOTjpUf2ThbyJRgh3ppPi8QVtKWa/GCf8ORpbKEJ0+Vbug19pe3o00/Sx NoYqFgyFqlmJ7XA26zFL7JZstELvTirqoPIrlDPLx72BM+rU2wjdaneJcIkBWquF3MCo r8IH3ff94pbj/0C2GX1ZuhAs8IWlLNEyrlv6A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=HEkxibK8XEm042hphp3RfHNxK12adJaFaGKQkbuoR3DO+DfWFEBwKVrSX8hACoU8pK Tm3XdCwYS65bHIAYrdHNzYgXrbg7IK+hjVRxWN5sz2EObVyxG5fam0uYAr9s4B9GN1wH KqeT+t7NObwhrtiAIM8UuIVdZDoyYYCCT1gJ4= MIME-Version: 1.0 Received: by 10.224.27.18 with SMTP id g18mr4929501qac.28.1274283997889; Wed, 19 May 2010 08:46:37 -0700 (PDT) Received: by 10.229.98.205 with HTTP; Wed, 19 May 2010 08:46:37 -0700 (PDT) Date: Wed, 19 May 2010 23:46:37 +0800 Message-ID: From: ambrosehuang ambrose To: freebsd-current@freebsd.org X-Mailman-Approved-At: Wed, 19 May 2010 16:38:39 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: clangBSD build error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 May 2010 16:12:39 -0000 building clangBSD revision URL: http://svn.freebsd.org/base/projects/clangbsd Repository Root: http://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 208300 Node Kind: directory Schedule: normal Last Changed Author: rdivacky Last Changed Rev: 208260 Last Changed Date: 2010-05-18 18:21:49 +0800 (Tue, 18 May 2010) with llvm-devel(r103179) on freebsd 8 stable amd64 according to clangBSD wiki failed with following message: make -j4 buildworld ------------------------------------------------------------------------------------------------------------------------------------------------- ....................... /usr/src.svn/src/lib/libc/stdlib/malloc.c:1098:38: error: 'tls_model' attribute ignored static __thread arena_t *arenas_map TLS_MODEL; ^ /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated from: # define TLS_MODEL __attribute__((tls_model("initial-exec"))) ^ /usr/src.svn/src/lib/libc/stdlib/malloc.c:1103:38: error: 'tls_model' attribute ignored static __thread tcache_t *tcache_tls TLS_MODEL; ^ /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated from: # define TLS_MODEL __attribute__((tls_model("initial-exec"))) ^ /usr/src.svn/src/lib/libc/stdlib/malloc.c:1122:37: error: 'tls_model' attribute ignored static __thread bool mmap_unaligned TLS_MODEL; ^ /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated from: # define TLS_MODEL __attribute__((tls_model("initial-exec"))) -------------------------------------------------------------------------------------------------------------------------------------------------- it seems that clang does NOT support tls_model attribute, I'm not sure. Does anyone meet similar error ? From owner-freebsd-current@FreeBSD.ORG Wed May 19 17:21:26 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04BFC1065670 for ; Wed, 19 May 2010 17:21:26 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id 82D968FC08 for ; Wed, 19 May 2010 17:21:25 +0000 (UTC) Received: by wwb39 with SMTP id 39so840886wwb.13 for ; Wed, 19 May 2010 10:21:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=HICmVI6b+01FkqGda9tphdzE2sSqyaO9u2RkDQ62gnk=; b=KgUvgvmkNmf/AmjSA8QuoTxZbm52W9YS6ZS8dumnu21urFkfxy4NQQfHxTlW8An6vf btCp09ThmvaTJYumVYAGbdD0g4wzq4BIM+9JzCDxVZs51lw/krlVjjGEcRS0LWucvn6w GcyThh2IhDBVap4l5aXmwWRwGNNw/x+VeZkhA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=r4SXbbmgPAZdJkm07MXG78a8QA351KVKAf84b97FenkJJ1H1sra6zWQ4bCGaAzZZea 5e5gdIBiI3GZVs/wK+RR9T+/WkJ6v63hUpRRRmtupyXFj5m3Y3GZRRvmDkR6xKyJ5RzS bXDZahiCsJnlFEj2A0rPd0n7JzqhuXTPjcVSY= MIME-Version: 1.0 Received: by 10.216.155.17 with SMTP id i17mr3801078wek.91.1274289684073; Wed, 19 May 2010 10:21:24 -0700 (PDT) Received: by 10.216.29.129 with HTTP; Wed, 19 May 2010 10:21:23 -0700 (PDT) In-Reply-To: References: Date: Wed, 19 May 2010 10:21:23 -0700 Message-ID: From: Jack Vogel To: Ryan Stone Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Current Subject: Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 May 2010 17:21:26 -0000 I have gotten access to a system this morning, I booted and installed 8.0 RELEASE on it, it had no problems installing or afterwords booting the SMP kernel. So, is it possible there's a regression/issue in HEAD, or perhaps you have something in the PCIE expansion slots that cause it, the system I'm using has nothing. Otherwise its possible there is a hardware revision difference. Have you tried 8 REL ? I'm up and rebuilding a kernel on it right now. Jack On Tue, May 18, 2010 at 4:40 PM, Ryan Stone wrote: > amd64 exhibits the same problem, except that it's not even polite and > panics without even asking. > From owner-freebsd-current@FreeBSD.ORG Wed May 19 22:15:37 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0163106564A for ; Wed, 19 May 2010 22:15:37 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by mx1.freebsd.org (Postfix) with ESMTP id 6E4A28FC0A for ; Wed, 19 May 2010 22:15:37 +0000 (UTC) Received: by ewy1 with SMTP id 1so582124ewy.13 for ; Wed, 19 May 2010 15:15:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=5paj+jbp3sltOuXHZDoSK/lFmUkw59yNPqQygRMt1BI=; b=cR4CtHoWr6n532aU3lAMd4uO5Nm1z5YDq3orQ7p7S3awfqEbjXhDV//zuITdC7Yyeu SRBbrtfMoaPmrQhNr3MJZus6p2BmgUgmBAEfaa/c3hHi/8yC5pfJ/5CukjW5qwo1rFxC Xp13SN5JJ4fG+MGEpdv5T8chO52vTWMraOL28= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=DW9Z5NlMahK8Df6JDsmD9J2htwGnIRYyu1wEMVRjqBmfZ4Oxry+iZsCs40FfshZpIx TWdIsHL+N6ebbBbcNfDnQzlmvLhhs+Jydn8xb262fxE+U95QFKE4my3P9IE6qdKGpaZW /ay2DX+MX20EP0b6EPExC93AQ21YobY2ZsYpQ= MIME-Version: 1.0 Received: by 10.213.65.140 with SMTP id j12mr3684154ebi.74.1274305556426; Wed, 19 May 2010 14:45:56 -0700 (PDT) Received: by 10.213.16.138 with HTTP; Wed, 19 May 2010 14:45:56 -0700 (PDT) In-Reply-To: References: Date: Wed, 19 May 2010 17:45:56 -0400 Message-ID: From: Ryan Stone To: Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current Subject: Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 May 2010 22:15:38 -0000 I've also tried a 6.1-derived kernel. I doubt that it was fixed for 8.0-RELEASE and then broken again on HEAD, but I'll check and be sure. My guess is that the problem is with the BIOS. We loaned our reference board to our BIOS vendor for development purposes and the BIOS they left on it is also unable to start APs. I think that my best bet to track this down is to see how the original Intel BIOS and the bad BIOS is configuring the hardware differently. I'm not very familiar with this stuff so I'm not sure what I should be looking at. MTRRs, I guess. What else? From owner-freebsd-current@FreeBSD.ORG Thu May 20 00:05:54 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4892C106568A for ; Thu, 20 May 2010 00:05:54 +0000 (UTC) (envelope-from tom@uffner.com) Received: from eris.uffner.com (uffner.com [66.208.243.25]) by mx1.freebsd.org (Postfix) with ESMTP id 00E5F8FC15 for ; Thu, 20 May 2010 00:05:53 +0000 (UTC) Received: from kali.uffner.com (static-71-162-143-90.phlapa.fios.verizon.net [71.162.143.90]) (authenticated bits=0) by eris.uffner.com (8.14.3/8.14.3) with ESMTP id o4K087LO032030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 May 2010 20:08:14 -0400 (EDT) (envelope-from tom@uffner.com) Message-ID: <4BF46E78.6030909@uffner.com> Date: Wed, 19 May 2010 19:04:24 -0400 From: Tom Uffner User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.23) Gecko/20090916 SeaMonkey/1.1.18 MIME-Version: 1.0 To: Attilio Rao References: <20100226005115.GP14937@weongyo> <20100228095259.GB3536@weongyo> <20100301103240.3a4aac8a.ray@dlink.ua> <20100303082833.GB22865@weongyo> <20100303111014.6564ea1e.ray@dlink.ua> <20100312231333.GZ1295@weongyo> <4BD2201E.3090409@entel.upc.edu> <20100424231755.GI65380@weongyo> <4BD4A928.8020901@entel.upc.edu> <20100506190653.GA31100@weongyo> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 00:05:54 -0000 Attilio Rao wrote: > > I have another problem where the bwn is fully recognized and wlan0 is > created but the interface doesn't scan at all: > > # netstat -nil > Name Mtu Network Address Ipkts Ierrs Idrop > Opkts Oerrs Coll > bwn0 2290 00:26:5e:64:be:75 0 0 0 > 0 0 0 > > # ifconfig wlan0 > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:26:5e:64:be:75 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 1 (2412 MHz 11b) > country US authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60 > bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 1 wme > bintval 0 > > # kldstat > Id Refs Address Size Name > 1 4 0xffffffff80100000 90b9a8 kernel > 2 1 0xffffffff80c22000 28a9a bwn_v4_ucode.ko > > doing "ifconfig wlan0 list scan" ends up immediately without further output. > The dmesg is here: http://www.freebsd.org/~attilio/dmesg-bwn0.diff I had a similar problem w/ a 4309. If you haven't solved this already, please check that the radio is actually enabled. some laptops have a button. some have a key sequence. many also have a BIOS setting. mine looked pretty much the same as yours to FreeBSD but just endlessly scanned the channels for a signal until i noticed that the radio was disabled in BIOS. tom From owner-freebsd-current@FreeBSD.ORG Thu May 20 07:24:34 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76A86106566B for ; Thu, 20 May 2010 07:24:34 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (lev.vlakno.cz [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id 339008FC1D for ; Thu, 20 May 2010 07:24:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 8E9949CB099; Thu, 20 May 2010 09:21:22 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id leAsoJ8ypEoY; Thu, 20 May 2010 09:21:20 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 53C579CB151; Thu, 20 May 2010 09:21:20 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id o4K7LKCH037416; Thu, 20 May 2010 09:21:20 +0200 (CEST) (envelope-from rdivacky) Date: Thu, 20 May 2010 09:21:20 +0200 From: Roman Divacky To: ambrosehuang ambrose Message-ID: <20100520072120.GA36958@freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: clangBSD build error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 07:24:34 -0000 I tried building clangbsd yesterday with clang/llvm r104146 and it worked ok. and it still does: pes ~/clangbsd$ clang --version clang version 2.0 (trunk 104146) Target: x86_64-unknown-freebsd8.0 Thread model: posix pes ~/clangbsd$ clang -c lib/libc/stdlib/malloc.c -I lib/libc/include/ -DMAXPAGESIZES=1 && echo success lib/libc/stdlib/malloc.c:5408:12: warning: implicit declaration of function 'getpagesizes' is invalid in C99 [-Wimplicit-function-declaration] nsizes = getpagesizes(pagesizes, MAXPAGESIZES); ^ 1 warning generated. success can you retry with newer version? or show me how exactly to reproduce this? On Wed, May 19, 2010 at 11:46:37PM +0800, ambrosehuang ambrose wrote: > building clangBSD revision > URL: http://svn.freebsd.org/base/projects/clangbsd > Repository Root: http://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 208300 > Node Kind: directory > Schedule: normal > Last Changed Author: rdivacky > Last Changed Rev: 208260 > Last Changed Date: 2010-05-18 18:21:49 +0800 (Tue, 18 May 2010) > > with llvm-devel(r103179) on freebsd 8 stable amd64 according to clangBSD > wiki failed with following message: > > make -j4 buildworld > ------------------------------------------------------------------------------------------------------------------------------------------------- > ....................... > /usr/src.svn/src/lib/libc/stdlib/malloc.c:1098:38: error: 'tls_model' > attribute ignored > static __thread arena_t *arenas_map TLS_MODEL; > ^ > /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated from: > # define TLS_MODEL __attribute__((tls_model("initial-exec"))) > ^ > /usr/src.svn/src/lib/libc/stdlib/malloc.c:1103:38: error: 'tls_model' > attribute ignored > static __thread tcache_t *tcache_tls TLS_MODEL; > ^ > /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated from: > # define TLS_MODEL __attribute__((tls_model("initial-exec"))) > ^ > /usr/src.svn/src/lib/libc/stdlib/malloc.c:1122:37: error: 'tls_model' > attribute ignored > static __thread bool mmap_unaligned TLS_MODEL; > ^ > /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated from: > # define TLS_MODEL __attribute__((tls_model("initial-exec"))) > -------------------------------------------------------------------------------------------------------------------------------------------------- > > it seems that clang does NOT support tls_model attribute, I'm not sure. > > Does anyone meet similar error ? > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu May 20 10:08:07 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D29A1106566B; Thu, 20 May 2010 10:08:07 +0000 (UTC) (envelope-from vanilla@fatpipi.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 95DF98FC24; Thu, 20 May 2010 10:08:07 +0000 (UTC) Received: by iwn5 with SMTP id 5so1898697iwn.13 for ; Thu, 20 May 2010 03:08:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.186.161 with SMTP id cs33mr3533775ibb.65.1274348349875; Thu, 20 May 2010 02:39:09 -0700 (PDT) Received: by 10.231.167.202 with HTTP; Thu, 20 May 2010 02:39:09 -0700 (PDT) In-Reply-To: <20100520072120.GA36958@freebsd.org> References: <20100520072120.GA36958@freebsd.org> Date: Thu, 20 May 2010 17:39:09 +0800 Message-ID: From: Vanilla Hsu To: Roman Divacky X-Mailman-Approved-At: Thu, 20 May 2010 11:37:26 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org, ambrosehuang ambrose Subject: Re: clangBSD build error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: v@fatpipi.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 10:08:07 -0000 I got such message since 2 weeks ago. -- /home/clangbsd/lib/libc/sys/stack_protector.c:88:19: error: format string is not a string literal (potentially insecure) [-Wformat-security] syslog(LOG_CRIT, msg); ^~~ 1 error generated. *** Error code 1 Stop in /home/clangbsd/lib/libc. -- desktop [/root] -root- clang -v clang version 2.0 (trunk) Target: x86_64-portbld-freebsd9.0 Thread model: posix 2010/5/20 Roman Divacky > > I tried building clangbsd yesterday with clang/llvm r104146 and it worked > ok. > > and it still does: > > pes ~/clangbsd$ clang --version > clang version 2.0 (trunk 104146) > Target: x86_64-unknown-freebsd8.0 > Thread model: posix > > > pes ~/clangbsd$ clang -c lib/libc/stdlib/malloc.c -I lib/libc/include/ > -DMAXPAGESIZES=1 && echo success > lib/libc/stdlib/malloc.c:5408:12: warning: implicit declaration of function > 'getpagesizes' is invalid in C99 > [-Wimplicit-function-declaration] > nsizes = getpagesizes(pagesizes, MAXPAGESIZES); > ^ > 1 warning generated. > success > > can you retry with newer version? or show me how exactly to reproduce this? > > On Wed, May 19, 2010 at 11:46:37PM +0800, ambrosehuang ambrose wrote: > > building clangBSD revision > > URL: http://svn.freebsd.org/base/projects/clangbsd > > Repository Root: http://svn.freebsd.org/base > > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > > Revision: 208300 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: rdivacky > > Last Changed Rev: 208260 > > Last Changed Date: 2010-05-18 18:21:49 +0800 (Tue, 18 May 2010) > > > > with llvm-devel(r103179) on freebsd 8 stable amd64 according to clangBSD > > wiki failed with following message: > > > > make -j4 buildworld > > > ------------------------------------------------------------------------------------------------------------------------------------------------- > > ....................... > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:1098:38: error: 'tls_model' > > attribute ignored > > static __thread arena_t *arenas_map TLS_MODEL; > > ^ > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated > from: > > # define TLS_MODEL __attribute__((tls_model("initial-exec"))) > > ^ > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:1103:38: error: 'tls_model' > > attribute ignored > > static __thread tcache_t *tcache_tls TLS_MODEL; > > ^ > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated > from: > > # define TLS_MODEL __attribute__((tls_model("initial-exec"))) > > ^ > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:1122:37: error: 'tls_model' > > attribute ignored > > static __thread bool mmap_unaligned TLS_MODEL; > > ^ > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated > from: > > # define TLS_MODEL __attribute__((tls_model("initial-exec"))) > > > -------------------------------------------------------------------------------------------------------------------------------------------------- > > > > it seems that clang does NOT support tls_model attribute, I'm not sure. > > > > Does anyone meet similar error ? > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu May 20 12:06:38 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8249A106566C for ; Thu, 20 May 2010 12:06:38 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (lev.vlakno.cz [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id 3C40E8FC14 for ; Thu, 20 May 2010 12:06:36 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 0B4E79CB074; Thu, 20 May 2010 14:03:21 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzYV0EBkbxtB; Thu, 20 May 2010 14:03:18 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id CBBA19CB175; Thu, 20 May 2010 14:03:18 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id o4KC3I11012193; Thu, 20 May 2010 14:03:18 +0200 (CEST) (envelope-from rdivacky) Date: Thu, 20 May 2010 14:03:18 +0200 From: Roman Divacky To: v@fatpipi.com Message-ID: <20100520120318.GA12098@freebsd.org> References: <20100520072120.GA36958@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, ambrosehuang ambrose Subject: Re: clangBSD build error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 12:06:38 -0000 On Thu, May 20, 2010 at 05:39:09PM +0800, Vanilla Hsu wrote: > I got such message since 2 weeks ago. > > -- > /home/clangbsd/lib/libc/sys/stack_protector.c:88:19: error: format string is > not a string literal (potentially insecure) [-Wformat-security] > syslog(LOG_CRIT, msg); > ^~~ > 1 error generated. > *** Error code 1 you have to have NO_WERROR= WERROR= in /etc/make.conf or /etc/src.conf From owner-freebsd-current@FreeBSD.ORG Thu May 20 15:05:15 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F043F106566C; Thu, 20 May 2010 15:05:14 +0000 (UTC) (envelope-from gperez@entel.upc.edu) Received: from violet.upc.es (violet.upc.es [147.83.2.51]) by mx1.freebsd.org (Postfix) with ESMTP id 6CC608FC18; Thu, 20 May 2010 15:05:14 +0000 (UTC) Received: from ackerman2.upc.es (ackerman2.upc.es [147.83.2.244]) by violet.upc.es (8.14.1/8.13.1) with ESMTP id o4KF4uB5009210 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 20 May 2010 17:04:57 +0200 Received: from [192.168.100.187] (100.Red-79-144-109.dynamicIP.rima-tde.net [79.144.109.100]) (authenticated bits=0) by ackerman2.upc.es (8.13.8/8.13.8) with ESMTP id o4KF4q7s008340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 May 2010 17:04:55 +0200 Message-ID: <4BF54F93.9000409@entel.upc.edu> Date: Thu, 20 May 2010 17:04:51 +0200 From: =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= User-Agent: Thunderbird 2.0.0.24 (X11/20100509) MIME-Version: 1.0 To: current@freebsd.org References: <20100228095259.GB3536@weongyo> <20100301103240.3a4aac8a.ray@dlink.ua> <20100303082833.GB22865@weongyo> <20100303111014.6564ea1e.ray@dlink.ua> <20100312231333.GZ1295@weongyo> <4BD2201E.3090409@entel.upc.edu> <20100424231755.GI65380@weongyo> <4BD4A928.8020901@entel.upc.edu> <20100506190653.GA31100@weongyo> <58220.88.15.97.205.1273248485.squirrel@webmail.entel.upc.edu> <20100510195622.GA1295@weongyo> In-Reply-To: <20100510195622.GA1295@weongyo> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.63 on 147.83.2.244 X-Mail-Scanned: Criba 2.0 + Clamd X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (violet.upc.es [147.83.2.51]); Thu, 20 May 2010 17:04:57 +0200 (CEST) Cc: Ian FREISLICH , weongyo@freebsd.org Subject: Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 15:05:15 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 En/na Weongyo Jeong ha escrit: > On Fri, May 07, 2010 at 06:08:05PM +0200, Gustavo Perez Querol wrote: >>> Hello Gustau, I'm so sorry for belated response that I had no time to >>> read and work email and wireless stuffs. >>> >>> Could you please test this symptom with attached patch? It looks in >>> CURRENT it missed to initialize a ratectl when it associates with AP. >>> >> The patch made the machine to panic. I think it happened when launching >> the supplicant. In fact, right now it works by putting the RF switch to >> OFF. As soon as I change it to ON the machine panics. >> >> It get a trap 12, with two reasons : page fault and "bufwrite, buffer is >> not busy?" >> >> I'm running 9.0/AMD64 from 1 of May (don't know exact svn revision). >> >> Do you want me to test anything else ? > > OK. The patch is ready to test. Could you please test it with attached > patch? > > regards, > Weongyo Jeong > I've just updated to FreeBSD 8.1 PRERELEASE and I see the unsupported rate problem again. I applied the patch for CURRENT and it works. So I guess the patch was not MFC in the 8.1 branch. However it still works slow (betwenn 200 and 300 kbytes/s). I tried using a rum dongle with the same AP (which is a 8.0-STABLE system with an Atheros card) and works great when uploading (2Mb sustained). In my laptop I see now messages like these : bwn0: RX decryption attempted (old 0 keyidx 0x1) If you want me to try anything, let me know. Regards, Gus - -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJL9U+SAAoJEH+VVM1WSYnP2R8QAK2HZsdQ2vlqH37+N6MEmoBz AmWHVUYxqx9QINRGx64diuwgn9USU985nJyxj8VDJOYAiPpzSDnvwPt45djKCt51 MCscu9T74yuvNKlDUwIrsfXvTQsknS3UnynYBILmraXMNJRKwezlnqY5/TSDZEvW 8pNSDJrnt9kBvO4Uy1aLCb1aJ/8+LegsTPLjG2PxVEe+Q+3B1vdw7bKjPvQvJo6o EmNH0Ufx4jrVB8SIDKDRYsHFmOKabRyoMG3EYQr/Jz8ZtoPdVWPxMJbDxe4gwJFL N3FI/LvV51tMwAiT+k+k6rjxXXHV58roVw6r7Uu7LxeJKe0ctwyGImR/atP5t0Ak dVfnihGL3BJhY4sAQBUUem+ESWhdhgz/KYAWDjIbg+czo6cXQCYUTv5UDXoWObaS NrsqNsrBweqXui4QN5GdOa8OY2Bv5WjcZMU2v9C93h4uM5HE0P4Zm0ou3ruLgduS WpDBfoHP223qQvm0QQg/CreZUzbriZtDzeHCGwtBhf8pGlm0jlEMu/LGfWRsllGS uLgvg56yE4H6ybkaGkXy778ICqnztL5VhmMWf/UhMzsOM1I9g2xwuGUrTald+xgq YYY5gSu6Lx2ZwDaG1V2y8T/bHeo3d9Q201tKSJerO8K22JjjV8ySJQh+x9QcivwR CDGo0r6LzEHONgnYQA1q =QJQr -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Thu May 20 14:10:24 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDE00106566C for ; Thu, 20 May 2010 14:10:24 +0000 (UTC) (envelope-from ambrosehua@gmail.com) Received: from mail-qy0-f188.google.com (mail-qy0-f188.google.com [209.85.221.188]) by mx1.freebsd.org (Postfix) with ESMTP id 7F4C58FC18 for ; Thu, 20 May 2010 14:10:24 +0000 (UTC) Received: by qyk26 with SMTP id 26so7641250qyk.28 for ; Thu, 20 May 2010 07:10:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ziGr+8J7Ni2rnwZSNu1lb8i4AY92w7Ng0wjaZAdWnAo=; b=tAv3o/gNZSf+akDsiK615JV9rxpM9vhkp0IC0T77EjozSSxaXXW8oxP3VayEoXAZkj S0ncuLaMJ5F+F12U7wqdNr74pCElgg0OWwznQIaY1cOHF3FqfVKqchfR/ZP6PGlOEycE x2jtSdRVtr1BWaDE7j3cU9QC3shWPambp4ywM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=RRuEpyN2Zc9XyWcO9onn9mxmcRxFnWhUupNM5APhtTr4UoONPHpIzpsHadZlp3IAC/ uyH/28f6QefaClVzi2+KHDs5HIpTLw/2VJCip47u9RmOVXS7RwUoUPK9l4B9we52d3Xo v2hDIkyUxcvIEZwuJcjKL3OO9sPLw05aNAh+I= MIME-Version: 1.0 Received: by 10.224.68.1 with SMTP id t1mr83147qai.14.1274364623463; Thu, 20 May 2010 07:10:23 -0700 (PDT) Received: by 10.229.98.205 with HTTP; Thu, 20 May 2010 07:10:23 -0700 (PDT) In-Reply-To: <20100520072120.GA36958@freebsd.org> References: <20100520072120.GA36958@freebsd.org> Date: Thu, 20 May 2010 22:10:23 +0800 Message-ID: From: ambrosehuang ambrose To: Roman Divacky X-Mailman-Approved-At: Thu, 20 May 2010 15:07:28 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: clangBSD build error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 14:10:24 -0000 I found my clang version is : [root@lateaxfreebsd src]# clang --version clang version 2.0 (trunk) Target: *x86_64-portbld-freebsd8.0* Thread model: posix svn revision is r10379_1 in PORTS I think maybe you can use the llvm-devel in PORTS to reproduce this I try to update clang to the latest version with make BOOTSTRAP=1 _CKSUMFILES="", but it seems the patch file confilcts with latest code? Could you tell me how to bypass the patching step ? 2010/5/20 Roman Divacky > > I tried building clangbsd yesterday with clang/llvm r104146 and it worked > ok. > > and it still does: > > pes ~/clangbsd$ clang --version > clang version 2.0 (trunk 104146) > Target: x86_64-unknown-freebsd8.0 > Thread model: posix > > > pes ~/clangbsd$ clang -c lib/libc/stdlib/malloc.c -I lib/libc/include/ > -DMAXPAGESIZES=1 && echo success > lib/libc/stdlib/malloc.c:5408:12: warning: implicit declaration of function > 'getpagesizes' is invalid in C99 > [-Wimplicit-function-declaration] > nsizes = getpagesizes(pagesizes, MAXPAGESIZES); > ^ > 1 warning generated. > success > > can you retry with newer version? or show me how exactly to reproduce this? > > On Wed, May 19, 2010 at 11:46:37PM +0800, ambrosehuang ambrose wrote: > > building clangBSD revision > > URL: http://svn.freebsd.org/base/projects/clangbsd > > Repository Root: http://svn.freebsd.org/base > > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > > Revision: 208300 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: rdivacky > > Last Changed Rev: 208260 > > Last Changed Date: 2010-05-18 18:21:49 +0800 (Tue, 18 May 2010) > > > > with llvm-devel(r103179) on freebsd 8 stable amd64 according to clangBSD > > wiki failed with following message: > > > > make -j4 buildworld > > > ------------------------------------------------------------------------------------------------------------------------------------------------- > > ....................... > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:1098:38: error: 'tls_model' > > attribute ignored > > static __thread arena_t *arenas_map TLS_MODEL; > > ^ > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated > from: > > # define TLS_MODEL __attribute__((tls_model("initial-exec"))) > > ^ > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:1103:38: error: 'tls_model' > > attribute ignored > > static __thread tcache_t *tcache_tls TLS_MODEL; > > ^ > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated > from: > > # define TLS_MODEL __attribute__((tls_model("initial-exec"))) > > ^ > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:1122:37: error: 'tls_model' > > attribute ignored > > static __thread bool mmap_unaligned TLS_MODEL; > > ^ > > /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated > from: > > # define TLS_MODEL __attribute__((tls_model("initial-exec"))) > > > -------------------------------------------------------------------------------------------------------------------------------------------------- > > > > it seems that clang does NOT support tls_model attribute, I'm not sure. > > > > Does anyone meet similar error ? > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu May 20 17:59:28 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA5F31065674 for ; Thu, 20 May 2010 17:59:28 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id 9B0FB8FC13 for ; Thu, 20 May 2010 17:59:28 +0000 (UTC) Received: from [178.34.41.155] (helo=izar) by services.ipt.ru with esmtpa (Exim 4.54 (FreeBSD)) id 1OFA1m-000E5z-PF for freebsd-current@freebsd.org; Thu, 20 May 2010 21:59:26 +0400 From: Boris Samorodov To: freebsd-current@freebsd.org Date: Thu, 20 May 2010 21:59:25 +0400 Message-ID: <94820402@ipt.ru> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: MAKEOBJDIRPREFIX and installkernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 17:59:28 -0000 Hi List, here is something strange with current CURRENT: ----- [~]bsam@izar% LANG=C svn info FreeBSD/base/head/src Path: FreeBSD/base/head/src URL: svn+ssh://svn.freebsd.org/base/head Repository Root: svn+ssh://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 208354 Node Kind: directory Schedule: normal Last Changed Author: jkim Last Changed Rev: 208353 Last Changed Date: 2010-05-20 20:24:12 +0400 (Thu, 20 May 2010) [~]bsam@izar% echo $MAKEOBJDIRPREFIX /home/bsam/FreeBSD/base/head/obj [~]bsam@izar% sudo make -C FreeBSD/base/head/src installkernel -------------------------------------------------------------- >>> Installing kernel -------------------------------------------------------------- cd /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/tmac PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/games:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make KERNEL=kernel install cd: can't cd to /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR *** Error code 2 Stop in /usr/home/bsam/FreeBSD/base/head/src. *** Error code 1 Stop in /usr/home/bsam/FreeBSD/base/head/src. [~]bsam@izar% ----- That command used to work fine for years... -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-current@FreeBSD.ORG Thu May 20 18:58:05 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36A9C106566B for ; Thu, 20 May 2010 18:58:05 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id B14F78FC16 for ; Thu, 20 May 2010 18:58:04 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id l26so608565fgb.13 for ; Thu, 20 May 2010 11:58:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received :x-authentication-warning:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=n1uQyY+0L3VrVoNgdEeE6XeifHstOOD1idqx05mSIuU=; b=oUu1SE/MEfCXXwaL7W1zYrBZnHAoy+fGfE9ImPJUJgrQ6fbaO/jh7+iMADZVY4JvpJ jjzrOuTsfO7I/o2skuxg/00pM6qLaHhItb5+gBI2MWuqyBxbaZXiMZcB36PqKaK0IKvK bs4vTxsu+fac/rFK4UICW7yvDQWNQuwmSXMAM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=x-authentication-warning:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; b=K43O7jragW1vdVEr+LVohTZYSWd74AZnnl4SyHbIjkskuBZnXrwIcM1ksbPL/Agwxm sHbx8Qs62C/DQDqbdanTJWfWeotficLgBq00KhGYANNdZKUrtx/YDndmYEelsZZECCA+ 7k+WEkImrLFbPGzMuxUUNcTYE+UYwfV4A9kRM= Received: by 10.87.73.1 with SMTP id a1mr2318734fgl.17.1274381883372; Thu, 20 May 2010 11:58:03 -0700 (PDT) Received: from darklight.org.ru ([213.132.76.142]) by mx.google.com with ESMTPS id e3sm2048893fga.4.2010.05.20.11.58.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 20 May 2010 11:58:02 -0700 (PDT) Received: from darklight.org.ru (yuri@darklight.org.ru [127.0.0.1]) by darklight.org.ru (8.14.4/8.14.4) with ESMTP id o4KIw0cp016110; Thu, 20 May 2010 22:58:00 +0400 (MSD) (envelope-from yuri.pankov@gmail.com) Received: (from yuri@localhost) by darklight.org.ru (8.14.4/8.14.4/Submit) id o4KIw0MZ016109; Thu, 20 May 2010 22:58:00 +0400 (MSD) (envelope-from yuri.pankov@gmail.com) X-Authentication-Warning: darklight.org.ru: yuri set sender to yuri.pankov@gmail.com using -f Date: Thu, 20 May 2010 22:58:00 +0400 From: Yuri Pankov To: Boris Samorodov Message-ID: <20100520185759.GB2361@darklight.org.ru> References: <94820402@ipt.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <94820402@ipt.ru> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-current@freebsd.org Subject: Re: MAKEOBJDIRPREFIX and installkernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 18:58:05 -0000 On Thu, May 20, 2010 at 09:59:25PM +0400, Boris Samorodov wrote: > Hi List, > > here is something strange with current CURRENT: > ----- > [~]bsam@izar% LANG=C svn info FreeBSD/base/head/src > Path: FreeBSD/base/head/src > URL: svn+ssh://svn.freebsd.org/base/head > Repository Root: svn+ssh://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 208354 > Node Kind: directory > Schedule: normal > Last Changed Author: jkim > Last Changed Rev: 208353 > Last Changed Date: 2010-05-20 20:24:12 +0400 (Thu, 20 May 2010) > > [~]bsam@izar% echo $MAKEOBJDIRPREFIX > /home/bsam/FreeBSD/base/head/obj > > [~]bsam@izar% sudo make -C FreeBSD/base/head/src installkernel > -------------------------------------------------------------- > >>> Installing kernel > -------------------------------------------------------------- > cd /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/tmac PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/games:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make KERNEL=kernel install > cd: can't cd to /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR > *** Error code 2 > > Stop in /usr/home/bsam/FreeBSD/base/head/src. > *** Error code 1 > > Stop in /usr/home/bsam/FreeBSD/base/head/src. > [~]bsam@izar% > ----- > > That command used to work fine for years... Works here. May you've recently changed your sudoers to not keep env variables? > > -- > WBR, Boris Samorodov (bsam) > Research Engineer, http://www.ipt.ru Telephone & Internet SP > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve Yuri From owner-freebsd-current@FreeBSD.ORG Thu May 20 19:16:41 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87A82106566C for ; Thu, 20 May 2010 19:16:41 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id 44F808FC0C for ; Thu, 20 May 2010 19:16:41 +0000 (UTC) Received: from [178.34.41.155] (helo=izar) by services.ipt.ru with esmtpa (Exim 4.54 (FreeBSD)) id 1OFBEV-000Exb-N9; Thu, 20 May 2010 23:16:39 +0400 From: Boris Samorodov To: Yuri Pankov References: <94820402@ipt.ru> <20100520185759.GB2361@darklight.org.ru> Date: Thu, 20 May 2010 23:16:38 +0400 In-Reply-To: <20100520185759.GB2361@darklight.org.ru> (Yuri Pankov's message of "Thu, 20 May 2010 22:58:00 +0400") Message-ID: <28745769@ipt.ru> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-current@freebsd.org Subject: Re: MAKEOBJDIRPREFIX and installkernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 19:16:41 -0000 On Thu, 20 May 2010 22:58:00 +0400 Yuri Pankov wrote: > On Thu, May 20, 2010 at 09:59:25PM +0400, Boris Samorodov wrote: > > Hi List, > > > > here is something strange with current CURRENT: > > ----- > > [~]bsam@izar% LANG=C svn info FreeBSD/base/head/src > > Path: FreeBSD/base/head/src > > URL: svn+ssh://svn.freebsd.org/base/head > > Repository Root: svn+ssh://svn.freebsd.org/base > > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > > Revision: 208354 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: jkim > > Last Changed Rev: 208353 > > Last Changed Date: 2010-05-20 20:24:12 +0400 (Thu, 20 May 2010) > > > > [~]bsam@izar% echo $MAKEOBJDIRPREFIX > > /home/bsam/FreeBSD/base/head/obj > > > > [~]bsam@izar% sudo make -C FreeBSD/base/head/src installkernel > > -------------------------------------------------------------- > > >>> Installing kernel > > -------------------------------------------------------------- > > cd /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/tmac PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/games:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make KERNEL=kernel install > > cd: can't cd to /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR > > *** Error code 2 > > > > Stop in /usr/home/bsam/FreeBSD/base/head/src. > > *** Error code 1 > > > > Stop in /usr/home/bsam/FreeBSD/base/head/src. > > [~]bsam@izar% > > ----- > > > > That command used to work fine for years... > Works here. May you've recently changed your sudoers to not keep env > variables? Hm. I've upgraded ports recently. However sudoers is the same. Thanks for the tip. I'll try to find out what has changed at my system. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-current@FreeBSD.ORG Thu May 20 19:55:47 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 759F21065676 for ; Thu, 20 May 2010 19:55:47 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (lev.vlakno.cz [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id 30D1A8FC13 for ; Thu, 20 May 2010 19:55:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id F2A179CB08E; Thu, 20 May 2010 21:52:34 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K03YMJIBU03b; Thu, 20 May 2010 21:52:32 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id CB9129CB1AA; Thu, 20 May 2010 21:52:32 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id o4KJqW9N070947; Thu, 20 May 2010 21:52:32 +0200 (CEST) (envelope-from rdivacky) Date: Thu, 20 May 2010 21:52:32 +0200 From: Roman Divacky To: ambrosehuang ambrose Message-ID: <20100520195232.GA70802@freebsd.org> References: <20100520072120.GA36958@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: clangBSD build error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 19:55:47 -0000 On Thu, May 20, 2010 at 10:10:23PM +0800, ambrosehuang ambrose wrote: > I found my clang version is : > [root@lateaxfreebsd src]# clang --version > clang version 2.0 (trunk) > Target: *x86_64-portbld-freebsd8.0* > Thread model: posix > svn revision is r10379_1 in PORTS > > I think maybe you can use the llvm-devel in PORTS to reproduce this > > I try to update clang to the latest version with > make BOOTSTRAP=1 _CKSUMFILES="", but it seems the patch file confilcts with > latest code? > > Could you tell me how to bypass the patching step ? there's no point in upgrading to newer clang. there were no change in this.. are you sure you are compiling with llvm-devel the malloc.c in clangbsd? not some older/newer version? From owner-freebsd-current@FreeBSD.ORG Fri May 21 00:34:08 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7EDF1065678; Fri, 21 May 2010 00:34:07 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from csmtp3.one.com (csmtp3.one.com [91.198.169.23]) by mx1.freebsd.org (Postfix) with ESMTP id 7EAAF8FC12; Fri, 21 May 2010 00:34:07 +0000 (UTC) Received: from macfeast.lan (0x573b9942.cpe.ge-1-2-0-1101.ronqu1.customer.tele.dk [87.59.153.66]) by csmtp3.one.com (Postfix) with ESMTP id CE2D724061F2; Fri, 21 May 2010 00:34:05 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: multipart/signed; boundary=Apple-Mail-377--257897853; protocol="application/pkcs7-signature"; micalg=sha1 From: Erik Cederstrand In-Reply-To: Date: Fri, 21 May 2010 02:34:05 +0200 Message-Id: References: <20100508102005.GB1867@elmar.spoerlein.net> <20100510061057.GA93038@server.vk2pj.dyndns.org> <20100512141154.GF88504@acme.spoerlein.net> To: Jeff Roberson X-Mailer: Apple Mail (2.1078) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Attilio Rao , current@freebsd.org, Peter Jeremy Subject: Re: LOR: ufs vs bufwait X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 May 2010 00:34:08 -0000 --Apple-Mail-377--257897853 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Den 12/05/2010 kl. 22.44 skrev Jeff Roberson: >=20 > I think Peter Holm also saw this once while we were testing SUJ and = reproduced ~30 second hangs with stock sources. At this point we need = to brainstorm ideas for adding debugging instrumentation and come up = with the quickest possible repro. FWIW, I get this LOR on a ClangBSD virtual machine running the stess2 = test suite. I can reproduce the LOR reliably like this: # cd stress2 #./run.sh lockf.cfg - press ctrl-C - another LOR is triggered by the ctrl-C (a dirhash/bufwait LOR = described in kern/137852) # ./run.sh mkdir.cfg - LOR is triggered immediately Erik= --Apple-Mail-377--257897853-- From owner-freebsd-current@FreeBSD.ORG Fri May 21 09:24:26 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0108106564A; Fri, 21 May 2010 09:24:26 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9FE208FC1D; Fri, 21 May 2010 09:24:26 +0000 (UTC) Received: by pvg12 with SMTP id 12so406317pvg.13 for ; Fri, 21 May 2010 02:24:26 -0700 (PDT) Received: by 10.143.87.2 with SMTP id p2mr838150wfl.323.1274433865926; Fri, 21 May 2010 02:24:25 -0700 (PDT) Received: from [10.0.1.198] (udp022762uds.hawaiiantel.net [72.234.79.107]) by mx.google.com with ESMTPS id d14sm743541rva.18.2010.05.21.02.24.23 (version=SSLv3 cipher=RC4-MD5); Fri, 21 May 2010 02:24:24 -0700 (PDT) Date: Thu, 20 May 2010 23:24:21 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: Erik Cederstrand In-Reply-To: Message-ID: References: <20100508102005.GB1867@elmar.spoerlein.net> <20100510061057.GA93038@server.vk2pj.dyndns.org> <20100512141154.GF88504@acme.spoerlein.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Attilio Rao , current@freebsd.org, Peter Jeremy Subject: Re: LOR: ufs vs bufwait X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 May 2010 09:24:26 -0000 On Fri, 21 May 2010, Erik Cederstrand wrote: > > Den 12/05/2010 kl. 22.44 skrev Jeff Roberson: >> >> I think Peter Holm also saw this once while we were testing SUJ and reproduced ~30 second hangs with stock sources. At this point we need to brainstorm ideas for adding debugging instrumentation and come up with the quickest possible repro. > > FWIW, I get this LOR on a ClangBSD virtual machine running the stess2 test suite. > > I can reproduce the LOR reliably like this: > > # cd stress2 > #./run.sh lockf.cfg > - press ctrl-C > - another LOR is triggered by the ctrl-C (a dirhash/bufwait LOR described in kern/137852) > # ./run.sh mkdir.cfg > - LOR is triggered immediately > > Erik The LOR is actually safe. I need to bless the acquisition. We have always acquired the buffers in this order. The deadlocks people were seeing were actually livelocks due to softdepflush looping indefinitely. I have committed a fix for that. Thanks, Jeff From owner-freebsd-current@FreeBSD.ORG Fri May 21 17:43:32 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0780106564A for ; Fri, 21 May 2010 17:43:32 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 61ACF8FC1A for ; Fri, 21 May 2010 17:43:31 +0000 (UTC) Received: by wye20 with SMTP id 20so1094508wye.13 for ; Fri, 21 May 2010 10:43:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=J6+tUvrRTHXhiyqdkPHozw4O9QjbC5sjar1wbzyUxTY=; b=S3JPi8KB519Gz9vEs6ZjLbXc7Lqbi4Z9aAcFGZTyiT9/yL6YjktKJUd5EZyczCw6Vv icSmYxDSUn3ERDzvW2sj824VoRqSIWEcYvIZvPPPs5kF3ZixuQZhdj/2KCVC2+v2B80l opW53i58d2R8+Tn41mpjltBv3xjesnsmRobAQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=K5/1Zq8XI2uI0cHG479OyIjR0EfnP2zC1JsLKoqm5L9abIv52QZADBpsTlZDRe7W/C 8xnSmxCdAQ56XXJHBMVS71vrFn0hZvvETVjbwg19JlMZ9XdQIouaWeWCClfU0BbxT96p tkuDus381+IALSRU+OdJbEYwZMOZq1yGAuIXw= MIME-Version: 1.0 Received: by 10.216.86.140 with SMTP id w12mr1053585wee.95.1274463811138; Fri, 21 May 2010 10:43:31 -0700 (PDT) Received: by 10.216.36.135 with HTTP; Fri, 21 May 2010 10:43:31 -0700 (PDT) In-Reply-To: <20100518214232.35dfa23f@kan.dnsalias.net> References: <20100518214232.35dfa23f@kan.dnsalias.net> Date: Fri, 21 May 2010 13:43:31 -0400 Message-ID: From: Ryan Stone To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Cc: Jack Vogel Subject: Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 May 2010 17:43:32 -0000 Just wanted to give everybody some closure on this issue: Through the magic of a JTAG debugger, I was able to identify that the problem was an infinite loop in the BIOS's SMI handler. I'm not sure why this didn't effect Linux -- perhaps it brought up the APs before the SMI came in. In any case, this clearly isn't a FreeBSD problem and I've punted the problem back to the BIOS vendor. Thanks to everyone who offered help and advice. From owner-freebsd-current@FreeBSD.ORG Fri May 21 17:50:41 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DC23106564A for ; Fri, 21 May 2010 17:50:41 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id BACF58FC12 for ; Fri, 21 May 2010 17:50:40 +0000 (UTC) Received: by wwb18 with SMTP id 18so855004wwb.13 for ; Fri, 21 May 2010 10:50:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=/JqzXwAElrclyoCTmwdFElm6yO1Koz+4vt6nOTZYPac=; b=TLYyDwhNGUMHHJLgCNlnNuc58+OUpjzWValWxXoujle3pYLGQxE/pvRTnDhxhhU41W sEH4nJeg5/sLEjtiJGvM/EsbAXQvteJzXGEPme6GAaTr+GRpzJ9ta1g4C7d52YtFlPPT 1NeeOe3dZqAzhnWBABNhZUxmHbhzxTjolWSGs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=uwiJXJY+cAwlxwSYe64LWZZ9XcSm4gV4sLBysI9Xh9NUN5/Te+57OWPW8i41VGQ2OQ 5s9bDzDdIXF7FpMXL+MGmlNd50fSDQWGG+LSzIfWzEOEClluZIyqxu5wjtKF8sh+J/KI DdYsKYFLdVuTzHiiQL1SmpHpR5PWARfQK4Vzk= MIME-Version: 1.0 Received: by 10.227.69.71 with SMTP id y7mr1657209wbi.123.1274464239587; Fri, 21 May 2010 10:50:39 -0700 (PDT) Received: by 10.216.29.129 with HTTP; Fri, 21 May 2010 10:50:38 -0700 (PDT) In-Reply-To: References: <20100518214232.35dfa23f@kan.dnsalias.net> Date: Fri, 21 May 2010 10:50:38 -0700 Message-ID: From: Jack Vogel To: Ryan Stone Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Current Subject: Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 May 2010 17:50:41 -0000 Cool, glad its resolved. Jack On Fri, May 21, 2010 at 10:43 AM, Ryan Stone wrote: > Just wanted to give everybody some closure on this issue: Through the > magic of a JTAG debugger, I was able to identify that the problem was > an infinite loop in the BIOS's SMI handler. I'm not sure why this > didn't effect Linux -- perhaps it brought up the APs before the SMI > came in. In any case, this clearly isn't a FreeBSD problem and I've > punted the problem back to the BIOS vendor. Thanks to everyone who > offered help and advice. > From owner-freebsd-current@FreeBSD.ORG Sat May 22 02:34:24 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1208A106564A; Sat, 22 May 2010 02:34:24 +0000 (UTC) (envelope-from ambrosehua@gmail.com) Received: from mail-qy0-f188.google.com (mail-qy0-f188.google.com [209.85.221.188]) by mx1.freebsd.org (Postfix) with ESMTP id AA9D48FC0C; Sat, 22 May 2010 02:34:23 +0000 (UTC) Received: by qyk26 with SMTP id 26so2948457qyk.28 for ; Fri, 21 May 2010 19:34:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=vKGunNjsq89GktWVTNpUxyhoHDRFpp0LaOYpQM5uQx0=; b=K5NW+NRCaY5mNh4HqY3eWQ/goMiPGUdo6U71hYAhb7pqPXyLqoedG/aMdE/yGZNlRR E0sx6zX9INEP2Xmo03NxAEqu5RY1YUh2TZk+2DuhjyhxzwCac5FVqjAeiYOu5wJsfqC4 geqcDPHI797jXW94HfZ08tXvZAZvXF5fArgQ4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=WwOj8ra5BXpumz3dRIojxrTqlzNjJqJ9sNVd573OZ4Y69l+0Y81a8j5s3bv2q3DC1e 6O/QJ4D4gvoSGN49c3Kd7DvSL9wjrzGaxAeryxLGt15NeYsq6gEX1TUGXj+DFPMNwSw7 SPovBUV24WzINKK+yF2PFZCL/qXk2GA7rgFew= MIME-Version: 1.0 Received: by 10.229.250.201 with SMTP id mp9mr615274qcb.67.1274495662823; Fri, 21 May 2010 19:34:22 -0700 (PDT) Received: by 10.229.98.205 with HTTP; Fri, 21 May 2010 19:34:22 -0700 (PDT) In-Reply-To: <20100520195232.GA70802@freebsd.org> References: <20100520072120.GA36958@freebsd.org> <20100520195232.GA70802@freebsd.org> Date: Fri, 21 May 2010 19:34:22 -0700 Message-ID: From: ambrosehuang ambrose To: Roman Divacky X-Mailman-Approved-At: Sat, 22 May 2010 05:50:50 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: clangBSD build error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 May 2010 02:34:24 -0000 2010/5/21 Roman Divacky > On Thu, May 20, 2010 at 10:10:23PM +0800, ambrosehuang ambrose wrote: > > I found my clang version is : > > [root@lateaxfreebsd src]# clang --version > > clang version 2.0 (trunk) > > Target: *x86_64-portbld-freebsd8.0* > > Thread model: posix > > svn revision is r10379_1 in PORTS > > > > I think maybe you can use the llvm-devel in PORTS to reproduce this > > > > I try to update clang to the latest version with > > make BOOTSTRAP=1 _CKSUMFILES="", but it seems the patch file confilcts > with > > latest code? > > > > Could you tell me how to bypass the patching step ? > > there's no point in upgrading to newer clang. there were no change > in this.. are you sure you are compiling with llvm-devel the malloc.c > in clangbsd? not some older/newer version? > I'm sure the llvm-devel is version r10379 in freebsd-stable branch. I also found that the both clang from llvm-devel and clang built from clangBSD building /usr/src.svn/src/lib/libc/stdlib/malloc.c(/usr/src.svn/src is the clangBSD directory in my box) failed with same error. maybe the version of clang in llvm-devel is too low, but the clang in clangBSD itself should be OK From owner-freebsd-current@FreeBSD.ORG Sat May 22 08:30:14 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBD29106566B for ; Sat, 22 May 2010 08:30:14 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (lev.vlakno.cz [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id 74B3C8FC18 for ; Sat, 22 May 2010 08:30:13 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 7C0859CB0E6; Sat, 22 May 2010 10:26:59 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ECiX8R5bf7Sa; Sat, 22 May 2010 10:26:57 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 49EEE9CB1AA; Sat, 22 May 2010 10:26:57 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id o4M8Qv6h062393; Sat, 22 May 2010 10:26:57 +0200 (CEST) (envelope-from rdivacky) Date: Sat, 22 May 2010 10:26:57 +0200 From: Roman Divacky To: ambrosehuang ambrose Message-ID: <20100522082657.GA62078@freebsd.org> References: <20100520072120.GA36958@freebsd.org> <20100520195232.GA70802@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: clangBSD build error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 May 2010 08:30:14 -0000 On Fri, May 21, 2010 at 07:34:22PM -0700, ambrosehuang ambrose wrote: > 2010/5/21 Roman Divacky > > > On Thu, May 20, 2010 at 10:10:23PM +0800, ambrosehuang ambrose wrote: > > > I found my clang version is : > > > [root@lateaxfreebsd src]# clang --version > > > clang version 2.0 (trunk) > > > Target: *x86_64-portbld-freebsd8.0* > > > Thread model: posix > > > svn revision is r10379_1 in PORTS > > > > > > I think maybe you can use the llvm-devel in PORTS to reproduce this > > > > > > I try to update clang to the latest version with > > > make BOOTSTRAP=1 _CKSUMFILES="", but it seems the patch file confilcts > > with > > > latest code? > > > > > > Could you tell me how to bypass the patching step ? > > > > there's no point in upgrading to newer clang. there were no change > > in this.. are you sure you are compiling with llvm-devel the malloc.c > > in clangbsd? not some older/newer version? > > > > > I'm sure the llvm-devel is version r10379 in freebsd-stable branch. I also > found that the > both clang from llvm-devel and clang built from clangBSD building > /usr/src.svn/src/lib/libc/stdlib/malloc.c(/usr/src.svn/src > is the clangBSD directory in my box) failed > with same error. > > maybe the version of clang in llvm-devel is too low, but the clang in > clangBSD itself should be OK pes ~/clangbsd$ md5 lib/libc/stdlib/malloc.c MD5 (lib/libc/stdlib/malloc.c) = 312d85c5cf51aa3fa1ef46c0832f0056 can you compare to your malloc.c ? and if it differs can you send me your malloc.c ? From owner-freebsd-current@FreeBSD.ORG Sat May 22 10:28:56 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 245E0106566B for ; Sat, 22 May 2010 10:28:56 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (lev.vlakno.cz [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id D12198FC0C for ; Sat, 22 May 2010 10:28:55 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 066D69CB08B; Sat, 22 May 2010 12:25:41 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6PlAMorTfwQ8; Sat, 22 May 2010 12:25:38 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id CD2CA9CB1AA; Sat, 22 May 2010 12:25:38 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id o4MAPcja090442; Sat, 22 May 2010 12:25:38 +0200 (CEST) (envelope-from rdivacky) Date: Sat, 22 May 2010 12:25:38 +0200 From: Roman Divacky To: ambrosehuang ambrose Message-ID: <20100522102538.GA90330@freebsd.org> References: <20100520072120.GA36958@freebsd.org> <20100520195232.GA70802@freebsd.org> <20100522082657.GA62078@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100522082657.GA62078@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: clangBSD build error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 May 2010 10:28:56 -0000 On Sat, May 22, 2010 at 10:26:57AM +0200, Roman Divacky wrote: > On Fri, May 21, 2010 at 07:34:22PM -0700, ambrosehuang ambrose wrote: > > 2010/5/21 Roman Divacky > > > > > On Thu, May 20, 2010 at 10:10:23PM +0800, ambrosehuang ambrose wrote: > > > > I found my clang version is : > > > > [root@lateaxfreebsd src]# clang --version > > > > clang version 2.0 (trunk) > > > > Target: *x86_64-portbld-freebsd8.0* > > > > Thread model: posix > > > > svn revision is r10379_1 in PORTS > > > > > > > > I think maybe you can use the llvm-devel in PORTS to reproduce this > > > > > > > > I try to update clang to the latest version with > > > > make BOOTSTRAP=1 _CKSUMFILES="", but it seems the patch file confilcts > > > with > > > > latest code? > > > > > > > > Could you tell me how to bypass the patching step ? > > > > > > there's no point in upgrading to newer clang. there were no change > > > in this.. are you sure you are compiling with llvm-devel the malloc.c > > > in clangbsd? not some older/newer version? > > > > > > > > > I'm sure the llvm-devel is version r10379 in freebsd-stable branch. I also > > found that the > > both clang from llvm-devel and clang built from clangBSD building > > /usr/src.svn/src/lib/libc/stdlib/malloc.c(/usr/src.svn/src > > is the clangBSD directory in my box) failed > > with same error. > > > > maybe the version of clang in llvm-devel is too low, but the clang in > > clangBSD itself should be OK > > pes ~/clangbsd$ md5 lib/libc/stdlib/malloc.c > MD5 (lib/libc/stdlib/malloc.c) = 312d85c5cf51aa3fa1ef46c0832f0056 > > can you compare to your malloc.c ? and if it differs can you send me > your malloc.c ? I just tried with llvm-devel port and malloc.c from clangbsd and it works just ok. From owner-freebsd-current@FreeBSD.ORG Sat May 22 15:09:04 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0A02106567D for ; Sat, 22 May 2010 15:09:04 +0000 (UTC) (envelope-from james-freebsd-current@jrv.org) Received: from zimbra.jrv.org (adsl-70-243-84-11.dsl.austtx.swbell.net [70.243.84.11]) by mx1.freebsd.org (Postfix) with ESMTP id 9931F8FC20 for ; Sat, 22 May 2010 15:09:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zimbra.jrv.org (Postfix) with ESMTP id 3C1F016A09C; Sat, 22 May 2010 10:09:02 -0500 (CDT) X-Virus-Scanned: amavisd-new at zimbra.housenet.jrv Received: from zimbra.jrv.org ([127.0.0.1]) by localhost (zimbra.housenet.jrv [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ve5YS86bsAY7; Sat, 22 May 2010 10:09:01 -0500 (CDT) Received: from [10.0.2.15] (adsl-70-243-84-14.dsl.austtx.swbell.net [70.243.84.14]) by zimbra.jrv.org (Postfix) with ESMTPSA id 4E8C216A09B; Sat, 22 May 2010 10:09:01 -0500 (CDT) Message-ID: <4BF7F3A7.1060202@jrv.org> Date: Sat, 22 May 2010 10:09:27 -0500 From: "James R. Van Artsdalen" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: jhell References: <4BF24317.8070807@DataIX.net> In-Reply-To: <4BF24317.8070807@DataIX.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , Rob Farmer , current@freebsd.org Subject: Re: make release broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 May 2010 15:09:04 -0000 On 5/18/2010 2:34 AM, jhell wrote: > On Mon, May 17, 2010 at 10:35 PM, Rob Farmer > wrote: >>> make release is broken on current. Seems to be related to the lzma >>> import. This is on i386: >>> >>> cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo >>> test.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo >>> newfs.lo route.lo rtsol.lo tunefs.lo cpio.lo find.lo minigzip.lo >>> sed.lo arp.lo ppp.lo sysinstall.lo usbconfig.lo -ll -ledit -lutil -lmd >>> -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lcam -lsbuf >>> -lufs -ldevinfo -lbsdxml -larchive -lbz2 -lusb -ljail >>> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x1e6): >>> In function `archive_compressor_xz_init': >>> : undefined reference to `lzma_lzma_preset' >>> ... > > This URL looks to be the problem you are seeing above. > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=20426+0+current/freebsd-current > make release is still broken on amd64 as of svn 208373 (2010-05-21 04:52:49 -0500) That patch seems unrelated?