From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 00:17:35 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1233916A4B3 for ; Sun, 21 Sep 2003 00:17:35 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78B3243FFB for ; Sun, 21 Sep 2003 00:17:33 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id h8L7HSgG019259; Sun, 21 Sep 2003 03:17:28 -0400 (EDT) Date: Sun, 21 Sep 2003 03:17:28 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Kris Kennaway In-Reply-To: <20030921063540.GA41190@rot13.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org cc: "M. Warner Losh" cc: h@schmalzbauer.de Subject: Re: Fixing -pthreads (Re: ports and -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 07:17:35 -0000 On Sat, 20 Sep 2003, Kris Kennaway wrote: > On Sun, Sep 21, 2003 at 02:12:55AM -0400, Daniel Eischen wrote: > > On Sat, 20 Sep 2003, Kris Kennaway wrote: > > > > > On Sun, Sep 21, 2003 at 01:44:35AM -0400, Daniel Eischen wrote: > > > > > What, precisely, do you object to in the above proposal? > > > > > > > > 1, 2, and 3. I don't think backing out -pthread change helps > > > > much in fixing ports... > > > > > > Again, why? Please explain instead of asserting, because that's > > > getting us nowhere towards resolving this. > > > > Because when things break, people fix them. There is no > > motivation (as seen in the last 2+ years) to fix something > > that isn't broken. > > What's the real issue here? It seems like you're suggesting that it's > not your responsibility to help fix the broken ports, and that other > people should do the work instead. Well, sorta yes. I don't have the time to fix broken ports but I can help guide others. I have other things on my plate. I do have one of my own ports to fix though. > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=321307+0+archive/2003/freebsd-ports/20030601.freebsd-ports > > > > my posting to ports@ in May of this year. > > That change doesn't seem to have happened, or to be the same thing > we're discussing here. Anyway, if you'd been interested in > pre-empting problems with the -pthread change you could have asked me > to do a package build with the change in place to test the waters, and > then worked with me and others to minimize the impact at the time when > the commit went in. I routinely do this with other committers > (including the gcc imports), and I'm happy to continue doing so. Well, actually it is directly related. Part of the plan to transition to libpthread is making ports PTHREAD_LIBS compliant. As stated in that thread, if a libpthread exists on the system, autoconf/configure will pick it up and the port will also end up using -pthread and/or PTHREAD_LIBS. If PTHREAD_LIBS is set to libthr or libc_r (something other than libpthread), then the port ends up linking to both libraries. This doesn't work but you don't know it until your run the application and very weird things happen. Causing a clean breakage is better because you know at compile-time that something is wrong. So ports need to first be PTHREAD_LIBS compliant before we make the switch. Soon after ports are fixed, we can rename it. I think doing a build of all the ports is a good idea. I guess you've already done that if I recall an earlier email correctly. I also think most of the problems are already known, and if you give it a few days after the freeze things should look a lot better. Actually, to look ahead a bit... After ports are fixed, it still might be a good idea to do another package build, but this time with libkse installed as libpthread and PTHREAD_LIBS set to libc_r (or something that is not libpthread). Is there an easy way to do an 'ldd' of the resulting binaries to make sure libpthread isn't referenced? Feel free to take this offline if you want... > However, the strategy of just dumping a change into the tree and then > leaving it to others to clean up the mess is not a good one - it's > disruptive to the development cycle, it causes developers to get > bogged down in arguments like we find ourselves having now, and the > bottom line is that it's just not very polite to the people that your > change affects. As Will mentioned, I think the changes are mostly done. I don't think I just 'dumped' the changes into the tree. It has been over 2 years since, yada yada yada, and the ports system should have been using PTHREAD_LIBS since then. I don't want to argue with you; I respect you and everyone else here and God knows you guys contribute an awful lot. > > When the GCC-3.3 import broke a lot of ports, did you ask for it to > > be backed out so that ports could first be fixed? > > No, kan and I worked together before the change went in to evaluate > the impact on packages, then I coordinated a group of volunteers to > help fix the resulting fallout. I'm trying to do the same thing now. > Are you willing to be part of the solution to this problem? >From what I've recently read, the freeze should be lifting this week. Can we hold off till then? Is a few more days going to matter? If the freeze continues longer than expected, I'll back the change out until it's over. -- Dan Eischen From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 00:34:09 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E25A016A4B3 for ; Sun, 21 Sep 2003 00:34:09 -0700 (PDT) Received: from procyon.firepipe.net (procyon.firepipe.net [198.78.66.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68F8F43FE3 for ; Sun, 21 Sep 2003 00:34:09 -0700 (PDT) (envelope-from will@csociety.org) Received: by procyon.firepipe.net (Postfix, from userid 1000) id D718031EB1; Sun, 21 Sep 2003 00:34:08 -0700 (PDT) Date: Sun, 21 Sep 2003 00:34:08 -0700 From: Will Andrews To: current@freebsd.org Message-ID: <20030921073408.GS47671@procyon.firepipe.net> Mail-Followup-To: current@freebsd.org References: <20030921063540.GA41190@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Subject: Re: Fixing -pthreads (Re: ports and -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 07:34:10 -0000 On Sun, Sep 21, 2003 at 03:17:28AM -0400, Daniel Eischen wrote: > From what I've recently read, the freeze should be lifting > this week. Can we hold off till then? Is a few more days > going to matter? If the freeze continues longer than expected, > I'll back the change out until it's over. I think we are going to extend it to allow more fixes for 4.9 since it's going to be delayed. But I'm not positive. Regards, -- wca From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 00:38:03 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 036E616A4B3 for ; Sun, 21 Sep 2003 00:38:03 -0700 (PDT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DDDA43FCB for ; Sun, 21 Sep 2003 00:38:02 -0700 (PDT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id A942914655; Sun, 21 Sep 2003 02:38:01 -0500 (CDT) Date: Sun, 21 Sep 2003 02:38:01 -0500 (CDT) From: Mark Linimon X-X-Sender: linimon@pancho To: Daniel Eischen In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: h@schmalzbauer.de cc: current@freebsd.org cc: "M. Warner Losh" cc: Kris Kennaway Subject: Re: Fixing -pthreads (Re: ports and -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 07:38:03 -0000 IMHO if the ports tree is unfrozen for the -pthreads fixes, the 4.9 release schedule will drift days if not weeks. While it's not as apparent as the kernel build issues, there are significant QA issues that go into the ports system. That's why the freeze is in place, to allow the QA process to run its course. Executive summary: POLA was violated for all the ports maintainers who do not keep up with kernel intricacies. Dismissing their distress at this doesn't really help the project move along. mcl From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 00:43:31 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6016C16A4B3; Sun, 21 Sep 2003 00:43:31 -0700 (PDT) Received: from purge.bash.sh (purge.bash.sh [193.178.223.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD51343FF3; Sun, 21 Sep 2003 00:43:29 -0700 (PDT) (envelope-from stu@ipng.org.uk) Received: from public1-blac3-3-cust241.manc.broadband.ntl.com ([213.106.20.241] helo=icecold.stu) by purge.bash.sh with asmtp (Exim 4.22 #3 ) id 1A0ysR-0004fF-Re; Sun, 21 Sep 2003 08:43:27 +0100 Date: Sun, 21 Sep 2003 08:43:25 +0100 From: Stuart Walsh To: Pawel Worach Message-Id: <20030921084325.6634c5b1.stu@ipng.org.uk> In-Reply-To: <3F6C60BE.5060207@telia.com> References: <3F6C60BE.5060207@telia.com> X-Mailer: Sylpheed version 0.9.3claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 X-SA-Exim-Mail-From: stu@ipng.org.uk Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60-rc5 (1.205-2003-09-16-exp) on purge.bash.sh X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.60-rc5 X-SA-Exim-Version: 3.1 (built Fri Sep 19 20:51:20 BST 2003) X-SA-Exim-Scanned: Yes cc: current@freebsd.org cc: wilko@freebsd.org Subject: Re: if_sk build fails X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 07:43:31 -0000 On Sat, 20 Sep 2003 16:14:22 +0200 Pawel Worach wrote: > Hi! > > Last if_sk update broke buildkernel > > ===> sk > rm -f .depend > mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ > -I@/../include /usr/src/sys/modules/sk/../../pci/if_sk.c > /usr/src/sys/pci/if_sk.c:129:26: pci/yukonreg.h: No such file or directory > mkdep: compile failed > > missed to cvs add yukonreg.h? > > - Pawel > This was fixed sometime yesterday with a commit of yukonreg.h. Regards, Stuart From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 00:44:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DCD116A4C0 for ; Sun, 21 Sep 2003 00:44:32 -0700 (PDT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F2DD43FE1 for ; Sun, 21 Sep 2003 00:44:31 -0700 (PDT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id C84B8140AB; Sun, 21 Sep 2003 02:44:30 -0500 (CDT) Date: Sun, 21 Sep 2003 02:44:30 -0500 (CDT) From: Mark Linimon X-X-Sender: linimon@pancho To: Daniel Eischen In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: h@schmalzbauer.de cc: current@freebsd.org cc: "M. Warner Losh" cc: Kris Kennaway Subject: Re: Fixing -pthreads (Re: ports and -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 07:44:32 -0000 > I don't think committing fixes for -current breakages should cause > problems for 4.9-RELEASE (especially with the caveat that they be > compile tested on -stable). It takes several days to do the compile QA. That's assuming that no actual users are allowed to have time to test the changes before the release is cut. IMHO, what you think just doesn't reflect the actual reality involved. We are just going to have to disagree on this. You should really look at the bento logs and get an understanding of the continual QA that is done on the _over_ 9000 ports (many of which have _no_ maintainer signed up) before you make assumptions that there shouldn't be significant problems with what you propose. mcl From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 01:02:09 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5606316A4B3 for ; Sun, 21 Sep 2003 01:02:09 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA8D543FDF for ; Sun, 21 Sep 2003 01:02:06 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id h8L825gG025292; Sun, 21 Sep 2003 04:02:05 -0400 (EDT) Date: Sun, 21 Sep 2003 04:02:05 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Will Andrews In-Reply-To: <20030921073408.GS47671@procyon.firepipe.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Fixing -pthreads (Re: ports and -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 08:02:09 -0000 On Sun, 21 Sep 2003, Will Andrews wrote: > On Sun, Sep 21, 2003 at 03:17:28AM -0400, Daniel Eischen wrote: > > From what I've recently read, the freeze should be lifting > > this week. Can we hold off till then? Is a few more days > > going to matter? If the freeze continues longer than expected, > > I'll back the change out until it's over. > > I think we are going to extend it to allow more fixes for 4.9 > since it's going to be delayed. But I'm not positive. OK, instead of waiting for it to be delayed, I backed out the -pthread removal until it's over. -- Dan Eischen From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 01:25:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9E3E16A4C1; Sun, 21 Sep 2003 01:25:10 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C83843FCB; Sun, 21 Sep 2003 01:25:10 -0700 (PDT) (envelope-from DougB@freebsd.org) Received: from master.dougb.net (12-234-17-181.client.attbi.com[12.234.17.181]) by comcast.net (rwcrmhc13) with SMTP id <2003092108250901500gh7hfe>; Sun, 21 Sep 2003 08:25:09 +0000 Date: Sun, 21 Sep 2003 01:25:09 -0700 (PDT) From: Doug Barton To: deischen@freebsd.org In-Reply-To: Message-ID: <20030921011930.K9576@znfgre.qbhto.arg> References: Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Fixing -pthreads (Re: ports and -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 08:25:10 -0000 On Sun, 21 Sep 2003, Daniel Eischen wrote: > Well, actually it is directly related. Part of the plan to > transition to libpthread is making ports PTHREAD_LIBS compliant. > As stated in that thread, if a libpthread exists on the system, > autoconf/configure will pick it up and the port will also end up > using -pthread and/or PTHREAD_LIBS. If PTHREAD_LIBS is set > to libthr or libc_r (something other than libpthread), then > the port ends up linking to both libraries. This doesn't work > but you don't know it until your run the application and very > weird things happen. Causing a clean breakage is better because > you know at compile-time that something is wrong. So ports need to > first be PTHREAD_LIBS compliant before we make the switch. Soon > after ports are fixed, we can rename it. Where the ports are concerned, I think this is a reasonable course of action, and I'd like to thank you for backing out the -pthread change on HEAD. I am a little confused about one thing though. What is going to happen to third party apps that use -pthread that aren't compiled through the ports? Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 01:35:37 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DA7116A4B3; Sun, 21 Sep 2003 01:35:37 -0700 (PDT) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E5844400B; Sun, 21 Sep 2003 01:35:35 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: from freebsd1.cimlogic.com.au (localhost [127.0.0.1]) by cimlogic.com.au (8.12.9/8.12.9) with ESMTP id h8L8c1vl032241; Sun, 21 Sep 2003 18:38:01 +1000 (EST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.12.9/8.12.9/Submit) id h8L8c04Q032240; Sun, 21 Sep 2003 18:38:00 +1000 (EST) Date: Sun, 21 Sep 2003 18:38:00 +1000 From: John Birrell To: Doug Barton Message-ID: <20030921083800.GB31793@freebsd1.cimlogic.com.au> References: <20030921011930.K9576@znfgre.qbhto.arg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030921011930.K9576@znfgre.qbhto.arg> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: Fixing -pthreads (Re: ports and -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 08:35:37 -0000 On Sun, Sep 21, 2003 at 01:25:09AM -0700, Doug Barton wrote: > I am a little confused about one thing though. What is going to > happen to third party apps that use -pthread that aren't compiled > through the ports? They need to replace -pthread with their thread library of choice (e.g. -lc_r or -lpthread). -- John Birrell From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 01:38:30 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1636716A4B3; Sun, 21 Sep 2003 01:38:30 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5027643FBF; Sun, 21 Sep 2003 01:38:29 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id h8L8cSgG000024; Sun, 21 Sep 2003 04:38:28 -0400 (EDT) Date: Sun, 21 Sep 2003 04:38:28 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Doug Barton In-Reply-To: <20030921011930.K9576@znfgre.qbhto.arg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Fixing -pthreads (Re: ports and -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 08:38:30 -0000 On Sun, 21 Sep 2003, Doug Barton wrote: > On Sun, 21 Sep 2003, Daniel Eischen wrote: > > > Well, actually it is directly related. Part of the plan to > > transition to libpthread is making ports PTHREAD_LIBS compliant. > > As stated in that thread, if a libpthread exists on the system, > > autoconf/configure will pick it up and the port will also end up > > using -pthread and/or PTHREAD_LIBS. If PTHREAD_LIBS is set > > to libthr or libc_r (something other than libpthread), then > > the port ends up linking to both libraries. This doesn't work > > but you don't know it until your run the application and very > > weird things happen. Causing a clean breakage is better because > > you know at compile-time that something is wrong. So ports need to > > first be PTHREAD_LIBS compliant before we make the switch. Soon > > after ports are fixed, we can rename it. > > Where the ports are concerned, I think this is a reasonable course of > action, and I'd like to thank you for backing out the -pthread change on > HEAD. I am a little confused about one thing though. What is going to > happen to third party apps that use -pthread that aren't compiled > through the ports? They'll have to choose one of our threading libraries. -pthread will be a NOOP for them, so their application will fail to link. If the third party application is a library, it won't be as obvious because it won't cause a compile or link error. This holds true for ports also. It might not be that much of a problem though, because applications that link to the third party library can always link to whatever threads library they want. Then the third party library would end up using the threads library chosen by the application. This might be the way to go for OpenGL or other similar libraries. It allows you to have applications linked with different thread libraries and not be broken by OpenGL (or whatever) being explicitly linked to a different threads library than the application. -- Dan Eischen From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 01:40:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B46BB16A4B3 for ; Sun, 21 Sep 2003 01:40:47 -0700 (PDT) Received: from r-kk.iij4u.or.jp (r-kk.iij4u.or.jp [210.130.0.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50F7143F75 for ; Sun, 21 Sep 2003 01:40:46 -0700 (PDT) (envelope-from niioka@kk.iij4u.or.jp) Received: from localhost (h157.p020.iij4u.or.jp [210.130.20.157]) by r-kk.iij4u.or.jp (8.11.6+IIJ/8.11.6) with SMTP id h8L8eiS15089 for ; Sun, 21 Sep 2003 17:40:44 +0900 (JST) Received: (qmail 73323 invoked from network); 21 Sep 2003 16:50:08 +0900 X-Authentication: niioka was authenticated by localhost at 21 Sep 2003 16:50:08 +0900 Received: from localhost (127.0.0.1) by localhost with SMTP; 21 Sep 2003 16:50:08 +0900 Date: Sun, 21 Sep 2003 16:49:31 +0900 (JST) Message-Id: <20030921.164931.193706567.niioka@kk.iij4u.or.jp> To: freebsd-current@freebsd.org From: Kenichi Niioka X-Mailer: Mew version 4.0.58 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: CIS is too long X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 08:40:47 -0000 FreeBSD 5.1-CURRENT #0: Sat Sep 20 11:38:46 JST 2003 Sep 20 12:47:38 daemon kernel: root@daemon.icm.unisys.co.jp:/home/niioka/src/obj/usr/src/sys/DAEMON I'm getting the following errors when I insert my pccard. CIS is too long -- truncating pccard0: Card has no functions! cbb0: PC Card card activation failed I tried to make buildkernel and installkernel with OLDCARD, and I'm getting the following messages wheh I insert my pccard. So, I can use the "Panasonic KX-PH402D" card. pccard: card inserted, slot 0 Sep 21 16:30:40 daemon pccardd[188]: Card "Panasonic"("KX-PH402D") [] [[none]] matched "Panasonic" ("KX-PH402D") [(null)] [(null)] sio0 at port 0x2f8-0x2ff irq 9 slot 0 on pccard0 sio0: type 16550A sio0: unable to activate interrupt in fast mode - using normal mode Sep 21 16:30:45 daemon pccardd[188]: sio0: Panasonic (KX-PH402D) inserted. I want to know how can I use my pccard with GENERIC kernel. Regards. -- Kenichi Niioka From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 02:39:19 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C00816A4B3 for ; Sun, 21 Sep 2003 02:39:19 -0700 (PDT) Received: from brattain.numericable.net (brattain.numericable.net [80.236.0.151]) by mx1.FreeBSD.org (Postfix) with SMTP id 60A1443F75 for ; Sun, 21 Sep 2003 02:39:17 -0700 (PDT) (envelope-from vitalis@numericable.fr) Received: (qmail 19127 invoked from network); 21 Sep 2003 09:39:16 -0000 Received: from unknown (HELO ?81.220.34.71?) ([81.220.34.71]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 21 Sep 2003 09:39:16 -0000 From: Vitalis To: freebsd-ports-bugs@freebsd.org, current Content-Type: text/plain Message-Id: <1064137155.578.17.camel@sankukai.ice-age.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Sun, 21 Sep 2003 09:39:15 +0000 Content-Transfer-Encoding: 7bit Subject: ncurses-5.3 buggy under 5.1-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 09:39:19 -0000 Hi! The installation of the ncurses-5.3 port leaves the system unusable for apps needing libncurses e.g. vi, sysinstall... The characters on output are severely scrambled. Its desinstallation solves the problem (the ncurses-5.2 from src/contrib works fine with 5.1-current). But some good ports require ncurses-5.3! From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 02:51:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81ED916A4B3 for ; Sun, 21 Sep 2003 02:51:04 -0700 (PDT) Received: from pfepc.post.tele.dk (pfepc.post.tele.dk [193.162.153.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A5C043FF7 for ; Sun, 21 Sep 2003 02:51:03 -0700 (PDT) (envelope-from nicolai@catpipe.net) Received: from 0x50a4509b.boanxx9.adsl-dhcp.tele.dk (0x50a4509b.boanxx9.adsl-dhcp.tele.dk [80.164.80.155]) by pfepc.post.tele.dk (Postfix) with ESMTP id 58921262AA6 for ; Sun, 21 Sep 2003 11:51:01 +0200 (CEST) From: Nicolai Petri Organization: catpipe Systems ApS To: current@freebsd.org Date: Sun, 21 Sep 2003 11:50:41 +0200 User-Agent: KMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309211150.41961.nicolai@catpipe.net> Subject: Unable to newfs/fsck partition on -current because of write failed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 09:51:04 -0000 I'm running -current from september, 14 on my notebook. After an unclean shutdown (out of batteri) my /var filesystem died horrible. Now when i'm trying to do a fsck I always get "write failed" for a lot of blocks. I saw this error some months ago where I just wiped the fs with newfs. But now even newfs gives me "Write failed". This seems a bit odd because i can easily do a "dd if=/dev/zero of=/dev/ad0s2d" and clear out the label. Any hints ? I'm thinking geom and/or blocksize problems. But that's just a guess. -- Cheers, Nicolai Petri From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 03:26:45 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D86BF16A4B3 for ; Sun, 21 Sep 2003 03:26:45 -0700 (PDT) Received: from smtp.web.de (smtp02.web.de [217.72.192.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 810D243FE1 for ; Sun, 21 Sep 2003 03:26:44 -0700 (PDT) (envelope-from thorsten.greiner@web.de) Received: from [80.141.13.44] (helo=tybalt) by smtp.web.de with asmtp (WEB.DE 4.99 #448) id 1A11QP-0001oL-00; Sun, 21 Sep 2003 12:26:42 +0200 Date: Sun, 21 Sep 2003 12:26:40 +0200 From: Thorsten Greiner To: Nicolai Petri Message-ID: <20030921102639.GA1357@tybalt> References: <200309211150.41961.nicolai@catpipe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200309211150.41961.nicolai@catpipe.net> User-Agent: Mutt/1.4.1i Sender: thorsten.greiner@web.de cc: current@freebsd.org Subject: Re: Unable to newfs/fsck partition on -current because of write failed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 10:26:46 -0000 * Nicolai Petri [2003-09-21 12:23]: > But now even newfs gives me "Write failed". This seems a bit odd > because i can easily do a "dd if=/dev/zero of=/dev/ad0s2d" and > clear out the label. Any hints ? I'm thinking geom and/or > blocksize problems. But that's just a guess. There was a small window in which the -CURRENT kernel was broken. This happened just around September 14th, so I suggest you either upgrade your kernel or use a kernel built before September 14th. Regards -Thorsten -- Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away. From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 04:15:14 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E37716A4BF for ; Sun, 21 Sep 2003 04:15:14 -0700 (PDT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BBFC43FFB for ; Sun, 21 Sep 2003 04:15:11 -0700 (PDT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) h8LBF8Fs093760 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 21 Sep 2003 13:15:09 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost)h8LBF8wa093759 for freebsd-current@freebsd.org; Sun, 21 Sep 2003 13:15:08 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.12.9/8.12.9) with ESMTP id h8LBANEb013383 for ; Sun, 21 Sep 2003 13:10:23 +0200 (CEST) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost)h8LBAN8r013382 for freebsd-current@freebsd.org; Sun, 21 Sep 2003 13:10:23 +0200 (CEST) Date: Sun, 21 Sep 2003 13:10:22 +0200 From: Andreas Klemm To: freebsd-current@freebsd.org Message-ID: <20030921111022.GA7415@titan.klemm.apsfilter.org> References: <20030909180947.GA23478@titan.klemm.apsfilter.org> <20030913071847.GA10778@titan.klemm.apsfilter.org> <20030913.092402.62370625.imp@bsdimp.com> <20030913141119.A27896@sasami.jurai.net> <20030913165818.I27896@sasami.jurai.net> <20030914002507.GA5239@titan.klemm.apsfilter.org> <20030913203403.E27896@sasami.jurai.net> <20030914194647.GA18839@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030914194647.GA18839@titan.klemm.apsfilter.org> X-Operating-System: FreeBSD 5.1-CURRENT X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.4i Subject: -current on laptop: panic: m_free detected a mbuf double free X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 11:15:14 -0000 Update the status now on -current. I downloaded the last recent snapshot of 2003-09-20 from current.freebsd.org. Made a test ftp session using the live CDROM. Same like a week before. Panic if I download something big from my FreeBSD ftp server. 5.1 on my normal PIII PC works fine. This seems to be PCMCIA related. db> trace Debugger(... panic(... m_free(... m_freem(... ip_input(... swi_net(... ithread_loop(... fork_exit(... fork_trampoline(... On Sun, Sep 14, 2003 at 09:46:47PM +0200, Andreas Klemm wrote: > On Sat, Sep 13, 2003 at 08:35:06PM -0400, Matthew N. Dodd wrote: > > On Sun, 14 Sep 2003, Andreas Klemm wrote: > > > It works for me, xl0 card is recognized. > > > > Great! > > > > > But during heavy ftp network traffic the LAPTOP panics. > > machine paniced 2 times > A) one time after transferring ~90 MB of a ~300 MB large ISO image > B) 2nd time after transferring ~ 8 MB of same large file > C) 3rd time after transferring ~ 6 MB of same large file > > In DDB I see using where, that the machine always crashes within > the same functions. DDB tells me: > > to B) panic: m_free detected a mbuf double-free > Debugger("panic") > Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 > db> where > Debugger > panic > m_free > m_freem > ip_input <---------- happens at different functions > ... > db> panic > ... > > to C) panic: m_free detected a mbuf double-free > Debugger("panic") > Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 > db> where > Debugger > panic > m_free > m_freem > xl_txeof <----------- happens at different functions > xl_intr > cbb_intr > ithread_loop > fork_exit > fork_trampoline > --- trap 0x1, eip = 0, esp = 0xcb042d7c, ebp = 0 --- > db> panic > panic: from debugger > Uptime: 2m55s > Dumping 191M > Dump complete > > > Let's see what gdb tells me, from panic "B)" > Sorry for case "C)" I didn't have enough space :-( > > (kgdb) where > > #0 doadump > #1 0x... in boot (howto=260) at ../../../kern/kern_shutdown.c: 372 > #2 0x... in panic () at ../../../kern/kern_shutdown.c: 550 > #3 0x... in db_panic () at ../../../ddb/db_command.c: 450 > #4 0x... in db_command (...) at ../../../ddb/db_command.c: 346 > #5 0x... in db_command_loop () at ../../../ddb/db_command.c: 472 > #6 0x... in db_trap (type=3, code=0) at ../../../ddb/db_trap.c: 73 > #7 0x... in kdb_trap (type=3, code=0, regs=0xcb027bc6) > at ../../../i386/i386/db_interface.c: 171 > #8 0x... in trap (frame= > {tf_fs = 24, tf_es = -1039597552, tf_ds = 16, tf_edi = 1, tf_esi ) -1070431840, tf_ebp = -889029704, tf_isp = -889029736, tf_ebx = 0, tf_edx = 0, tf_ecx = 32, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1070703196, tf_cs = 8, tf_eflags = 642, tf_esp = -1070363254, tf_ss = -1070440292}) > at ../../../i386/i386/trap.c: 577 > #9 0x... in calltrap () at {standard input}: 102 > #10 0x... in panic (fmt=0xc03281a0 "m_free detected a mbuf double-freeze") > at ../../../kern/kern_shutdown.c: 534 > #11 0x... in m_free (mb=0xc0d4fe00) at ../../../kern/subr_mbuf.c: 1368 > #12 0x... in m_freem (mb=0x0) at ../../../kern/subr_mbuf.c: 1403 > #13 0x... in ip_input (mb=0xc0d4fe00) at ../../../netinet/ip_input.c: 963 > #14 0x... in swi_net (dummy=0x0) at ../../../net/net_isr.c: 236 > #15 0x... in ithread_loop (arg=0xc0d33200) > at ../../../kern/kern_intr.c: 534 > #16 0x... in fork_exit (callout=0xc01b3900 , arg=0x0, > frame=0x0) at ../../../kern/kern_fork.c: 796 > > (kgdb) up 8 > #8 0x... in trap (frame= > {tf_fs = 24, tf_es = -1039597552, tf_ds = 16, tf_edi = 1, tf_esi ) -1070431840, tf_ebp = -889029704, tf_isp = -889029736, tf_ebx = 0, tf_edx = 0, tf_ecx = 32, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1070703196, tf_cs = 8, tf_eflags = 642, tf_esp = -1070363254, tf_ss = -1070440292}) > 577 if (kbd_trap (type, 0, &frame) > > (kgdb) frame frame->tf_ebp frame->tf_eip > > Too many args in frame specification ... > hmmmm "/&%"(/&%(" does the developer handbook need and update ? ;-) > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-GDB > > Here it ends , have no clue how to select correct frames ... :-) > > > Andreas /// > > -- > Andreas Klemm - Powered by FreeBSD 5.1-CURRENT > Need a magic printfilter today ? -> http://www.apsfilter.org/ > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" Andreas /// -- Andreas Klemm - Powered by FreeBSD 5.1-CURRENT Need a magic printfilter today ? -> http://www.apsfilter.org/ From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 05:01:55 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1334616A4B3 for ; Sun, 21 Sep 2003 05:01:55 -0700 (PDT) Received: from hueymiccailhuitl.mtu.ru (hueytecuilhuitl.mtu.ru [195.34.32.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B12643FBF for ; Sun, 21 Sep 2003 05:01:54 -0700 (PDT) (envelope-from sem@ciam.ru) Received: from ciam.ru (ppp131-47.dialup.mtu-net.ru [62.118.131.47]) by hueymiccailhuitl.mtu.ru (Postfix) with ESMTP id E44BB1544B3 for ; Sun, 21 Sep 2003 16:00:43 +0400 (MSD) (envelope-from sem@ciam.ru) Message-ID: <3F6D92EB.1020102@ciam.ru> Date: Sun, 21 Sep 2003 16:00:43 +0400 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: -current brake ufs for -stable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 12:01:55 -0000 Hello! I've installed both -current and -stable on my box. One of partition I plan to share betwen them (place ports/distfiles there). I newfs'ed it from -stable and wrote on it from -current. When I booted with -stable I've found the partition FS was broken. I think it's because of extended atributes -current wrote on it. I don't like to turn off extended attributes on -current at all. I'd like to have some option for mount to disable it (I've not found it on manpage). How can I use the partition this way now? ---- Sem. From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 05:42:26 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1854916A4B3 for ; Sun, 21 Sep 2003 05:42:26 -0700 (PDT) Received: from shaft.techsupport.co.uk (shaft.techsupport.co.uk [212.250.77.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id A390F43FDF for ; Sun, 21 Sep 2003 05:42:20 -0700 (PDT) (envelope-from setantae@submonkey.net) Received: from pc3-cdif2-5-cust222.cdif.cable.ntl.com ([81.101.152.222] helo=shrike.submonkey.net ident=mailnull) by shaft.techsupport.co.uk with esmtp (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.22) id 1A13Xb-0007rJ-Kx; Sun, 21 Sep 2003 13:42:15 +0100 Received: from setantae by shrike.submonkey.net with local (Exim 4.22) id 1A13XW-0003By-L6; Sun, 21 Sep 2003 13:42:10 +0100 Date: Sun, 21 Sep 2003 13:42:10 +0100 From: Ceri Davies To: "M. Warner Losh" Message-ID: <20030921124210.GD342@submonkey.net> Mail-Followup-To: Ceri Davies , "M. Warner Losh" , current@freebsd.org References: <20030920.204425.25098720.imp@bsdimp.com> <200309210257.h8L2vuIe062108@realtime.exit.com> <20030920.211440.27154168.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AsxXAMtlQ5JHofzM" Content-Disposition: inline In-Reply-To: <20030920.211440.27154168.imp@bsdimp.com> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.4i Sender: Ceri Davies cc: current@freebsd.org Subject: Re: really 4.9 stability X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 12:42:26 -0000 --AsxXAMtlQ5JHofzM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 20, 2003 at 09:14:40PM -0600, M. Warner Losh wrote: > In message: <200309210257.h8L2vuIe062108@realtime.exit.com> > Frank Mayhar writes: > : Everything has been rock-solid, no problems at all. Were it not for > : PAE, I would say to go ahead and release it. >=20 > That's good to hear. The re@ folks at devsummit had said that even > w/o PAE enabled, bad things were happening to people. However, I've > seen a number of reports since then that contradict this, or that the > instability isn't that common. I'm confused; how does one disable PAE? I don't see a kernel option for it. Ceri --=20 User: DO YOU ACCEPT JESUS CHRIST AS YOUR PERSONAL LORD AND SAVIOR? Iniaes: Sure, I can accept all forms of payment. -- www.chatterboxchallenge.com --AsxXAMtlQ5JHofzM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/bZyiocfcwTS3JF8RArAUAJ9FpQbNANqWR4QoI66VKpdCg/4oUwCdEyYM cGFo+TFOnV5bIrzK+1aXt4Q= =qizN -----END PGP SIGNATURE----- --AsxXAMtlQ5JHofzM-- From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 06:00:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9084216A4B3 for ; Sun, 21 Sep 2003 06:00:15 -0700 (PDT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99DBE43FDF for ; Sun, 21 Sep 2003 06:00:14 -0700 (PDT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 8A1DC1FFAD9 for ; Sun, 21 Sep 2003 15:00:12 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 2B14D1FF973; Sun, 21 Sep 2003 15:00:11 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id B74C1155A6; Sun, 21 Sep 2003 12:59:47 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id AD16815384 for ; Sun, 21 Sep 2003 12:59:48 +0000 (UTC) Date: Sun, 21 Sep 2003 12:59:48 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20020300 Subject: make release and md(4) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 13:00:15 -0000 Hi, when doing my first make release I noticed it stopped somewhere and hung :( 74830 p2 D+ 0:01.12 cpio -dump /mnt The host is i386 and TARGET ist sparc64 just to confuse. The base system runs a HEAD world/kernel from mid july. The above cpio must be from src/release/sparc64/mkisoimages.sh unlucky me tried to see what's going on and did a ls /u3/mnt which also hung. more unlucky me also typed in sync in another screen. kill -9 on the processes did not help. After another sync I am no longer able to remotely do anything with the machine apart from successfully pinging it. Somewhere in between I tried to ktrace the processes but didn't get any output. This is what strace said: abcde# strace -p 74883 # ls getdirentries(3, ^C abcde# strace -p 74830 # cpio write(4, ".............................."..., 512^C abcde# strace -p 74920 # sync sync(0^C I found an older PR http://www.freebsd.org/cgi/query-pr.cgi?pr=47538 that might be related. How are snapshots and release builds done by others ? Or are things already fixed and I should update base system to latest head (thinking about atang) ? and btw: are /dev/mdXc supposed to be existent as given in the release Makefiles/scripts ? Thanks for any comments. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 06:13:26 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC9A216A4B3 for ; Sun, 21 Sep 2003 06:13:26 -0700 (PDT) Received: from MAILSERVER.ofw.fi (ns.ofw.fi [194.111.144.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6259E44001 for ; Sun, 21 Sep 2003 06:13:25 -0700 (PDT) (envelope-from dan.naumov@ofw.fi) Received: from [172.16.161.81] by MAILSERVER.ofw.fi (NTMail 7.00.0022/NT1439.00.90501b21) with ESMTP id uvbamaaa for current@FreeBSD.ORG; Sun, 21 Sep 2003 16:11:57 +0300 From: Dan Naumov To: Thomas Quinot In-Reply-To: <20030920195311.GA97748@melusine.cuivre.fr.eu.org> References: <200309200755.h8K7t4fA049614@spider.deepcore.dk> <20030920195311.GA97748@melusine.cuivre.fr.eu.org> Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1064150012.838.3.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Sun, 21 Sep 2003 16:13:32 +0300 Content-Transfer-Encoding: 8bit cc: current@FreeBSD.ORG Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 21 Sep 2003 13:13:26 -0000 On Sat, 2003-09-20 at 22:53, Thomas Quinot wrote: > Le 2003-09-20, Daniel Eischen écrivait : > > > No, using latest sources, with or without atapicam, does > > not solve the problem. It still hangs. > > Please try the patch below, it should at least work around the problem. I have rebuilt world after you have committed the patch and now the system boots properly with ATAPICAM enabled in the kernel. It no longer hangs at boot. I tried mounting /dev/cd0 and suceeded. However, not everything seems to be perfect, take a look at the bottom of the included dmesg output: =================================================================== Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Sun Sep 21 15:44:22 EEST 2003 root@localhost.localdomain:/usr/obj/usr/src/sys/JAGO Preloaded elf kernel "/boot/kernel/kernel" at 0xc04b6000. Preloaded elf module "/boot/kernel/linux.ko" at 0xc04b61f4. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04b62a0. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) processor (1400.06-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x644 Stepping = 4 Features=0x183f9ff AMD Features=0xc0440000 real memory = 536805376 (511 MB) avail memory = 516239360 (492 MB) Pentium Pro MTRR support enabled VESA: v3.0, 65536k memory, flags:0x1, mode table:0xc03c82c2 (1000022) VESA: NVidia npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 10 entries at 0xc00fddb0 acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_cpu0: port 0x530-0x537 on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 7 INTD is routed to irq 5 pcib0: slot 7 INTD is routed to irq 5 pcib0: slot 10 INTA is routed to irq 11 pcib0: slot 14 INTA is routed to irq 11 agp0: port 0xc000-0xc003 mem 0xe4000000-0xe4000fff,0xe0000000-0xe1ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci_cfgintr: 1:5 INTA BIOS irq 10 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xc400-0xc40f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] uhci0: port 0xc800-0xc81f irq 5 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xcc00-0xcc1f irq 5 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 7.4 (no driver attached) rl0: port 0xe000-0xe0ff mem 0xe4001000-0xe40010ff irq 11 at device 10.0 on pci0 rl0: Ethernet address: 00:e0:7d:9f:be:31 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0xe400-0xe43f irq 11 at device 14.0 on pci0 pcm0: atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 orm0: