From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 01:25:28 2004 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 678A116A4CF for ; Sun, 28 Mar 2004 01:25:28 -0800 (PST) Received: from darkness.comp.waw.pl (unknown [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id A09AA43D3F for ; Sun, 28 Mar 2004 01:25:27 -0800 (PST) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 50876ACAE3; Sun, 28 Mar 2004 11:25:26 +0200 (CEST) Date: Sun, 28 Mar 2004 11:25:26 +0200 From: Pawel Jakub Dawidek To: freebsd-current@freebsd.org Message-ID: <20040328092526.GX8930@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W0fIhK6DANimrc4b" Content-Disposition: inline User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 Subject: [jmc@netbsd.org: CVS commit: [netbsd-1-6] src/sys/kern] 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, 28 Mar 2004 09:25:28 -0000 --W0fIhK6DANimrc4b Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. I think this fix is also related to us, isn't it? ----- Forwarded message from James Chacon ----- X-Original-To: nick@garage.freebsd.pl Delivered-To: pjd@darkness.comp.waw.pl Delivered-To: source-changes@netbsd.org From: James Chacon Subject: CVS commit: [netbsd-1-6] src/sys/kern To: source-changes@NetBSD.org Reply-To: jmc@netbsd.org Date: Sun, 28 Mar 2004 08:02:36 +0000 (UTC) Precedence: list Commiter: James Chacon Branch: netbsd-1-6 Files: 1.93.6.3 src/sys/kern/kern_exit.c =20 Log Message: Pullup rev 1.104-1.106 (requested by junyoung in ticket #1615) Make sure that, if orphaned child is being traced, it's reparented back to the original parent before it's killed. Diffs: COMMAND: cvs -d:pserver:anoncvs@anoncvs.netbsd.org:/cvsroot rdiff -u -r1.93= .6.2 -r1.93.6.3 src/sys/kern/kern_exit.c Index: src/sys/kern/kern_exit.c diff -u src/sys/kern/kern_exit.c:1.93.6.2 src/sys/kern/kern_exit.c:1.93.6.3 --- src/sys/kern/kern_exit.c:1.93.6.2 Wed Oct 22 06:15:50 2003 +++ src/sys/kern/kern_exit.c Sun Mar 28 08:02:36 2004 @@ -1,4 +1,4 @@ -/* $NetBSD: kern_exit.c,v 1.93.6.2 2003/10/22 06:15:50 jmc Exp $ */ +/* $NetBSD: kern_exit.c,v 1.93.6.3 2004/03/28 08:02:36 jmc Exp $ */ =20 /*- * Copyright (c) 1998, 1999 The NetBSD Foundation, Inc. @@ -78,7 +78,7 @@ */ =20 #include -__KERNEL_RCSID(0, "$NetBSD: kern_exit.c,v 1.93.6.2 2003/10/22 06:15:50 jmc= Exp $"); +__KERNEL_RCSID(0, "$NetBSD: kern_exit.c,v 1.93.6.3 2004/03/28 08:02:36 jmc= Exp $"); =20 #include "opt_ktrace.h" #include "opt_sysv.h" @@ -240,14 +240,25 @@ wakeup((caddr_t)initproc); for (; q !=3D 0; q =3D nq) { nq =3D q->p_sibling.le_next; - proc_reparent(q, initproc); + /* - * Traced processes are killed - * since their existence means someone is screwing up. + * Traced processes are killed since their existence + * means someone is screwing up. Since we reset the + * trace flags, the logic in sys_wait4() would not be + * triggered to reparent the process to its + * original parent, so we must do this here. */ if (q->p_flag & P_TRACED) { + if (q->p_opptr !=3D q->p_pptr) { + struct proc *t =3D q->p_opptr; + proc_reparent(q, t ? t : initproc); + q->p_opptr =3D NULL; + } else + proc_reparent(q, initproc); q->p_flag &=3D ~(P_TRACED|P_WAITED|P_FSTRACE); psignal(q, SIGKILL); + } else { + proc_reparent(q, initproc); } } =20 ----- End forwarded message ----- --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --W0fIhK6DANimrc4b Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAZpoGForvXbEpPzQRAsJ5AJ90FCc2hY9mRDwmee1HhLiLA5sk1ACeMxzI 3xtXc7GTqaGRaELBlsrn0ro= =Uhh7 -----END PGP SIGNATURE----- --W0fIhK6DANimrc4b-- From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 02:39:06 2004 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 0BA9516A4CE for ; Sun, 28 Mar 2004 02:39:06 -0800 (PST) Received: from pfepb.post.tele.dk (pfepb.post.tele.dk [195.41.46.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98EA743D3F for ; Sun, 28 Mar 2004 02:39:05 -0800 (PST) (envelope-from esbjerg@xbsd.net) Received: from xbsd.net (0x50a16596.boanxx13.adsl-dhcp.tele.dk [80.161.101.150]) by pfepb.post.tele.dk (Postfix) with ESMTP id 02BDB5EE058 for ; Sun, 28 Mar 2004 12:39:03 +0200 (CEST) Received: by xbsd.net (Postfix, from userid 1000) id AAB443DF13; Sun, 28 Mar 2004 12:39:00 +0200 (CEST) Date: Sun, 28 Mar 2004 12:39:00 +0200 From: Sven Esbjerg To: freebsd-current@freebsd.org Message-ID: <20040328103900.GA4143@gosling.home.xbsd.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: unable to boot 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, 28 Mar 2004 10:39:06 -0000 I have been trying to update to latest current without luck. It seems something changed in init and fsck_ffs. When I boot a newer kernel than March 16. I get problems at fsck. What I see is: Mounting root from: ufs:/dev/ad0s2a start_init: trying /sbin/init pid 105 (fsck_ufs), uid 0: exited on signal 8 pid 106 (fsck_ufs), uid 0: exited on signal 8 and then it hangs. I installed the latest fsck_ffs (matching the new kernel) which seems to have removed the fsck problems since it doesn't exit with signal 8 any more. However it still hangs after trying /sbin/init. I read /usr/src/UPDATING which doesn't say anything about fsck_ffs og init. I have no problems booting with the kernel build on March 16. Any suggestions. Sven Esbjerg From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 04:18:37 2004 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 21B6B16A4CF for ; Sun, 28 Mar 2004 04:18:37 -0800 (PST) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE69943D39 for ; Sun, 28 Mar 2004 04:18:35 -0800 (PST) (envelope-from Holger.Kipp@alogis.com) Received: from intserv.int1.b.intern (localhost [127.0.0.1]) by alogis.com (8.11.1/8.9.3) with SMTP id i2SCIVb41656; Sun, 28 Mar 2004 14:18:31 +0200 (CEST) (envelope-from hk@alogis.com) Message-Id: <200403281218.i2SCIVb41656@alogis.com> Date: Sun, 28 Mar 2004 12:18:26 +0000 From: Holger Kipp To: martin@mullet.se X-Mailer: phpGroupWare (http://www.phpgroupware.org) MIME-version: 1.0 Content-type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-description: Mail message body cc: freebsd-current@freebsd.org Subject: [SOLVED] mod_usertrack: apache "exited on signal 11" on FreeBSD 5.2 CURRENT (now) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Holger.Kipp@alogis.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Mar 2004 12:18:38 -0000 Martin Nilsson (martin@mullet.se) wrote: > > >Holger Kipp wrote: >> Just checked if this is the same with the latest FreeBSD 5.2-CURRENT >> from now (cvsupped an hour ago), also rebuilding apache13-modssl >> with portupgrade. >> >> Same behaviour: Everything works fine with CookieTracking off, but >> with CookieTracking on, I get clean 'signal 11'. This is with >> CookieStyle Netscape and CookieStyle Cookie. CookieStyle Cookie2 >> seems to work, but then I receive a different Cookie per request :-( > >Hi, I had the same problem but solved it with adding the following to my >httpd.conf: > >CookieName Apache > [...] >This problem is also present in 4.9, I heven't had time to debug it further. That bug was introduced with the 'latest' version of mod_usertrack. See http://issues.apache.org/bugzilla/show_bug.cgi?id=24483 for details. It is only necessary to set CookieName explicitly. As soon as the latest version of Apache (affects both 1.3 and 2.0) is in the ports, the problem should go away. Fix for 2.0.49 went only in 25.03.2004, though. Sorry for the noise. Regards, Holger Kipp From owner-freebsd-current@FreeBSD.ORG Sat Mar 27 11:38:44 2004 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 B1A3216A4D0 for ; Sat, 27 Mar 2004 11:38:44 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id DC8FE43D2D for ; Sat, 27 Mar 2004 11:38:43 -0800 (PST) (envelope-from mayday@gmx.net) Received: (qmail 23368 invoked by uid 65534); 27 Mar 2004 19:38:42 -0000 Received: from p508A8B7C.dip0.t-ipconnect.de (EHLO 192.168.0.4) (80.138.139.124) by mail.gmx.net (mp005) with SMTP; 27 Mar 2004 20:38:42 +0100 X-Authenticated: #431110 From: Benjamin Sobotta To: W.K.Offermans@TUe.nl Date: Sat, 27 Mar 2004 20:39:28 +0000 User-Agent: KMail/1.6 References: <20040327110135.GA92431@tom.chem.tue.nl> In-Reply-To: <20040327110135.GA92431@tom.chem.tue.nl> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200403272039.28489.mayday@gmx.net> X-Mailman-Approved-At: Sun, 28 Mar 2004 05:03:59 -0800 cc: current@freebsd.org Subject: Re: FreeBSD 5.2.1 on ASUS PC-DL Deluxe 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: Sat, 27 Mar 2004 19:38:44 -0000 Hi Works perfectly fine here except the onboard NIC. Sound and Promise RAID work fine. Great board! Regards, Ben On Saturday 27 March 2004 11:01, Willy Offermans wrote: > Dear FreeBSD friends, > > My boss has asked me to replace the old computer by a new one. We want > to invest our money in an ASUS PC-DL deluxe with two Intel Xeon 2.4 GHz. > Does anybody have experiences with this board and FreeBSD 5.2.1? From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 00:57:57 2004 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 C2B5916A4CE for ; Sun, 28 Mar 2004 00:57:57 -0800 (PST) Received: from as6-1-5.kr.m.bonet.se (as6-1-5.kr.m.bonet.se [217.215.84.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2B4543D3F for ; Sun, 28 Mar 2004 00:57:56 -0800 (PST) (envelope-from martin@mullet.se) Received: from mullet.se (euklides.gneto.com [192.168.10.11]) by as6-1-5.kr.m.bonet.se (Postfix) with ESMTP id 1344B743C7; Sun, 28 Mar 2004 10:57:55 +0200 (CEST) Message-ID: <40669393.30807@mullet.se> Date: Sun, 28 Mar 2004 10:57:55 +0200 From: Martin Nilsson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040311 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Holger.Kipp@alogis.com References: <200403272317.i2RNHGb14933@alogis.com> In-Reply-To: <200403272317.i2RNHGb14933@alogis.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Sun, 28 Mar 2004 05:03:59 -0800 cc: freebsd-current@freebsd.org Subject: Re: mod_usertrack: apache "exited on signal 11" on FreeBSD 5.2CURRENT (now) 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, 28 Mar 2004 08:57:57 -0000 Holger Kipp wrote: > Just checked if this is the same with the latest FreeBSD 5.2-CURRENT > from now (cvsupped an hour ago), also rebuilding apache13-modssl > with portupgrade. > > Same behaviour: Everything works fine with CookieTracking off, but > with CookieTracking on, I get clean 'signal 11'. This is with > CookieStyle Netscape and CookieStyle Cookie. CookieStyle Cookie2 > seems to work, but then I receive a different Cookie per request :-( Hi, I had the same problem but solved it with adding the following to my httpd.conf: CookieTracking On CookieExpires "2 years" CookieFormat Compact CookieName Apache CookieStyle RFC2965 I know that all options have sensible defaults but without the above apache segfaults in some regexp function in libc. This problem is also present in 4.9, I heven't had time to debug it further. /Martin -- Martin Nilsson, CTO & Founder, Mullet Scandinavia AB, Malmö, SWEDEN E-mail: martin@mullet.se, Phone: +46-(0)708-606170, Web: www.mullet.se Our business is well engineered servers optimised for FreeBSD & Linux From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 06:22:23 2004 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 AB80516A4CE; Sun, 28 Mar 2004 06:22:23 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAD2843D1F; Sun, 28 Mar 2004 06:22:22 -0800 (PST) (envelope-from freebsd-current-local@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (sccrmhc12) with ESMTP id <2004032814221801200n75fbe>; Sun, 28 Mar 2004 14:22:22 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id 314FAF; Sun, 28 Mar 2004 09:22:18 -0500 (EST) Sender: lowell@be-well.ilk.org To: John Baldwin References: <20040318132321.F9436@root.org> <44r7vg5r2j.fsf@be-well.ilk.org> <44lllo5quz.fsf@be-well.ilk.org> <200403261407.22278.jhb@FreeBSD.org> From: Lowell Gilbert Date: 28 Mar 2004 09:22:18 -0500 In-Reply-To: <200403261407.22278.jhb@FreeBSD.org> Message-ID: <44n061rqzp.fsf@be-well.ilk.org> Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: current@freebsd.org Subject: Re: agp0 hang in 5.2.1-RELEASE 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, 28 Mar 2004 14:22:23 -0000 John Baldwin writes: > Can you try moving those hunks into the attach method rather than the probe > method by the way? Certainly. I don't expect that to work though, because in my case the lockup was happening in the probe itself. [Yes, that means that the hardware is exhibiting fairly broken behaviour; but I still wanted to run FreeBSD on it...] It will probably take me a few days; the buildworld (which I need for unrelated reasons) takes many hours for this system. > For what it's worth, Warner and I are talking off-line > about a more general approach in the new-bus code itself. I did see a message where he said he was also planning on including a mechanism for avoiding the probe. From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 07:57:52 2004 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 6319F16A4CE for ; Sun, 28 Mar 2004 07:57:52 -0800 (PST) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0705743D49 for ; Sun, 28 Mar 2004 07:57:52 -0800 (PST) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1B7ceq-0000Ym-00; Sun, 28 Mar 2004 17:57:08 +0200 Date: Sun, 28 Mar 2004 17:57:08 +0200 To: "Moore, Robert" Message-ID: <20040328155708.GC19001@poupinou.org> References: <37F890616C995246BE76B3E6B2DBE055201C6C@orsmsx403.jf.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <37F890616C995246BE76B3E6B2DBE055201C6C@orsmsx403.jf.intel.com> User-Agent: Mutt/1.5.4i From: Bruno Ducrot cc: acpi-jp@jp.FreeBSD.org cc: current@freebsd.org cc: Nate Lawson Subject: Re: [acpi-jp 3117] RE: ACPI-CA 20040311 imported 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, 28 Mar 2004 15:57:52 -0000 On Fri, Mar 26, 2004 at 01:52:21PM -0800, Moore, Robert wrote: > Here's an example of ASL recursion: > > Method(PWUP,0,NotSerialized) > { > If(LAnd(\_SB.PCI0.CBS0.PWRS,\_SB.PCI0.CBS1.PWRS)) > { > If(LNot(And(_ADR /* \_SB.PCI0.CBS0._ADR */,0xFFFF))) > { > And(MCTL /* \_SB.PCI0.CBS0.MCTL */,0x7C,Local0) > Or(Local0,BMCL /* \_SB.PCI0.CBS0.BMCL */,MCTL /* > \_SB.PCI0.CBS0.MCTL */) > } > Else > { > \_SB.PCI0.CBS0.PWUP() > } > } > } I assume that PWRS are some hardware io (pci conf probably), able to detect if the cardbus is powered or not. I assume _ADR can not be made dynamic. So far, this function look like: Method(PWUP, 0, NotSerialized) { While (Not((LAnd(\_SB.PCI0.CBS0.PWRS,\_SB.PCI0.CBS1.PWRS))) { Noop } } and is probably called from _WAK, or more likely from _PS0 so far I guess it is ok to busy loop (in both form). Why not writting the busy loop instead? In the original form, there is the possibility to crash the system by overflowing the kernel stack if the bus is not powered quickly. -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 08:52:58 2004 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 B29FA16A4CE for ; Sun, 28 Mar 2004 08:52:58 -0800 (PST) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 463FB43D2D for ; Sun, 28 Mar 2004 08:52:58 -0800 (PST) (envelope-from kirk@strauser.com) Received: from pooh.strauser.com (pooh.honeypot.net [10.0.5.128]) by kanga.honeypot.net (8.12.10/8.12.10) with ESMTP id i2SGqud4030893 for ; Sun, 28 Mar 2004 10:52:57 -0600 (CST) (envelope-from kirk@strauser.com) To: freebsd-current@freebsd.org References: <20040326225740.GA3567@rocco.epita.fr> From: Kirk Strauser Date: Sun, 28 Mar 2004 10:52:53 -0600 In-Reply-To: <20040326225740.GA3567@rocco.epita.fr> (jeremie le-hen's message of "Fri, 26 Mar 2004 23:57:40 +0100") Message-ID: <87ptawewwq.fsf@strauser.com> Lines: 25 X-Mailer: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65', clamav-milter version '0.60p' Subject: Re: New jail related rc.conf variable 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, 28 Mar 2004 16:52:58 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable At 2004-03-26T22:57:40Z, jeremie le-hen writes: > Therefore, I though that the jail rc script was laking of flexibility in > sense that there is no simple way to do some unusual configuration before > starting the jail and I decided to add a `jail_example_pre_exec' variable > in rc.conf which is simply a command to execute before jailing. Alternatively, I'm still developing and using my JailAdmin scripts (available at http://subwiki.honeypot.net/cgi-bin/view/Freebsd/JailAdmin) . They provide functionality similar to /etc/rc.jail, but additionally provide the ability to mount filesystems before starting a jail and unmount them after stopping it, to manage an arbitrary number of named jails, and to get some statistics from running jails via SNMP. It's been a little while since the last update, but it still works correctly on -CURRENT systems. I'm anticipating a few changes in the near future, possibly including packing the system as a port. =2D-=20 Kirk Strauser "94 outdated ports on the box, 94 outdated ports. Portupgrade one, an hour 'til done, 82 outdated ports on the box." --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAZwLo5sRg+Y0CpvERAnEkAJ9fmyeDaTrEw93YG55ksgJqYtfq2wCfSbjy TvKJCzGLb4rBYh0J7pB155w= =KYY/ -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 10:23:19 2004 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 06DC016A4CE; Sun, 28 Mar 2004 10:23:19 -0800 (PST) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3655843D3F; Sun, 28 Mar 2004 10:23:18 -0800 (PST) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.11/8.12.11) with ESMTP id i2SINGut000185; Sun, 28 Mar 2004 22:23:16 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.11/8.12.11/Submit) id i2SINFqH000184; Sun, 28 Mar 2004 22:23:16 +0400 (MSD) (envelope-from ache) Date: Sun, 28 Mar 2004 22:23:14 +0400 From: Andrey Chernov To: des@freebsd.org, current@freebsd.org Message-ID: <20040328182314.GA99956@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , des@freebsd.org, current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.24.0.7; VDF 6.24.0.73 (host: pobrecita.freebsd.ru) Subject: mtree -L is broken due to unneded type=link additions to BSD.*.dist 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, 28 Mar 2004 18:23:19 -0000 I found commit which broke 'mtree -L', it is BSD.usr.dist v1.293 (des) and BSD.local.dist v1.108 (des) Symptoms are: mtree -eU -L -f /usr/src/etc/mtree/BSD.usr.dist -p /usr share/nls/en_US.US-ASCII changed type expected link found dir share/nls/POSIX changed type expected link found dir This commit is not only broke 'make hierarchy', it is completelly unneded, because those symlinks are already created by /usr/src/etc/nls.alias processing. Please back it out. -- Andrey Chernov | http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 10:44:48 2004 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 55FF816A4CE for ; Sun, 28 Mar 2004 10:44:48 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ECF743D31 for ; Sun, 28 Mar 2004 10:44:47 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i2SIijjr006508 for ; Sun, 28 Mar 2004 20:44:45 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: current@freebsd.org From: Poul-Henning Kamp Date: Sun, 28 Mar 2004 20:44:45 +0200 Message-ID: <6507.1080499485@critter.freebsd.dk> Subject: =?iso-8859-1?q?diskless_booting_is_b=F8rked=2E=2E=2E?= 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, 28 Mar 2004 18:44:48 -0000 Root mounting fails. Please fix soon. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 11:48:07 2004 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 942F716A4CE for ; Sun, 28 Mar 2004 11:48:07 -0800 (PST) Received: from darkness.comp.waw.pl (unknown [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFB3843D1F for ; Sun, 28 Mar 2004 11:48:06 -0800 (PST) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id D3477ACAE3; Sun, 28 Mar 2004 21:48:04 +0200 (CEST) Date: Sun, 28 Mar 2004 21:48:04 +0200 From: Pawel Jakub Dawidek To: Poul-Henning Kamp Message-ID: <20040328194804.GD8930@darkness.comp.waw.pl> References: <6507.1080499485@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u7HsstwThBMwNUgg" Content-Disposition: inline In-Reply-To: <6507.1080499485@critter.freebsd.dk> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: current@freebsd.org Subject: Re: diskless booting is b?rked... 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, 28 Mar 2004 19:48:07 -0000 --u7HsstwThBMwNUgg Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 28, 2004 at 08:44:45PM +0200, Poul-Henning Kamp wrote: +>=20 +> Root mounting fails. +>=20 +> Please fix soon. Wasn't this fixed here: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D2902139+0+archive/2004/cvs-a= ll/20040328.cvs-all --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --u7HsstwThBMwNUgg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAZyv0ForvXbEpPzQRAuU2AKCMTZ8FTOlhQ0g6i0+LCrqiCmfHkQCfV5PF xYtd7GcGfzLBbcZHab8EN9Q= =gdTe -----END PGP SIGNATURE----- --u7HsstwThBMwNUgg-- From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 11:58:14 2004 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 80AA116A4CF for ; Sun, 28 Mar 2004 11:58:14 -0800 (PST) Received: from express.cec.wustl.edu (express.cec.wustl.edu [128.252.21.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FF8C43D1F for ; Sun, 28 Mar 2004 11:58:14 -0800 (PST) (envelope-from jam6@cec.wustl.edu) Received: from scales (adsl-65-69-84-199.dsl.stlsmo.swbell.net [65.69.84.199]) (authenticated bits=0) by express.cec.wustl.edu (8.12.5/8.12.5) with ESMTP id i2SJwDNx004376 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sun, 28 Mar 2004 13:58:13 -0600 (CST) Message-ID: <007d01c414ff$005bf8e0$0300a8c0@scales> From: "Jeff Mitchell" To: Date: Sun, 28 Mar 2004 13:58:11 -0600 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Pthread Issues 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, 28 Mar 2004 19:58:14 -0000 Current folks-- I'm having some major issues with pthreads. I have a base 5.2 = cvsupgraded to 5.2.1. To save a lot of copying and pasting and keep = this message from being too long, please check: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-March/006393.html= and http://lists.freebsd.org/pipermail/freebsd-ports/2004-March/010982.html for more information that might give clues to some of the issues. At someone's request tried the following (in = /usr/ports/net/openldap21-client) shocker1# make -VOSVERSION -VPTHREAD_CFLAGS -VPTHREAD_LIBS 502010 -D_THREAD_SAFE -lc_r Someone else suggested creating a /etc/libmap.conf with the following: libpthread.so.1 libc_r.so.5 libpthread.so libc_r.so None of this has worked, however. It was mentioned to me that "checking = for pthread_create in default libraries" is supposed to be successful, = so maybe something went wrong with my base system upgrade. I have no idea, personally. Anyone that could help me out, it'd be much = appreciated, as I'm pretty much barred from upgrading a significant = number of my ports beause of dependencies on the ones that are failing. If there's any other information that would be helpful, please let me = know. Thanks, Jeff From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 12:12:51 2004 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 3C3BC16A4CE for ; Sun, 28 Mar 2004 12:12:51 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C696D43D1F for ; Sun, 28 Mar 2004 12:12:50 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i2SKAUxC032535; Sun, 28 Mar 2004 15:10:30 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i2SKAUlD032532; Sun, 28 Mar 2004 15:10:30 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 28 Mar 2004 15:10:30 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp In-Reply-To: <6507.1080499485@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: =?iso-8859-1?q?diskless_booting_is_b=F8rked=2E=2E=2E?= 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, 28 Mar 2004 20:12:51 -0000 On Sun, 28 Mar 2004, Poul-Henning Kamp wrote: > Root mounting fails. > > Please fix soon. I can boot a kernel from about an hour ago with pxeboot without problems; there were some pertinent NFS changes recently. I haven't tried the new userland diskless booting pieces as yet, however--I'm using an older world since the work I'm doing now is primarily kernel work. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 13:10:19 2004 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 839D316A4CE for ; Sun, 28 Mar 2004 13:10:19 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D62F43D39 for ; Sun, 28 Mar 2004 13:10:19 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i2SLAI43078271 for freebsd-current@freebsd.org; Sun, 28 Mar 2004 15:10:18 -0600 (CST) (envelope-from dan) Date: Sun, 28 Mar 2004 15:10:18 -0600 From: Dan Nelson To: freebsd-current@freebsd.org Message-ID: <20040328211018.GN3446@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i Subject: panic: mutex Giant owned at ../../../kern/kern_thread.c:1341 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, 28 Mar 2004 21:10:19 -0000 Got this running an ibcs2_coff binary on today's kernel: (kgdb) where #0 doadump () at ../../../kern/kern_shutdown.c:240 #1 0xc0660fc3 in boot (howto=256) at ../../../kern/kern_shutdown.c:374 #2 0xc06613f9 in __panic () at ../../../kern/kern_shutdown.c:552 #3 0xc065775c in _mtx_assert (m=0xc093a2e0, what=0, file=0xc087d3cf "../../../kern/kern_thread.c", line=1341) at ../../../kern/kern_mutex.c:731 #4 0xc066ee6e in thread_wait (p=0xc093a2e0) at ../../../kern/kern_thread.c:1341 #5 0xc0649ad7 in kern_wait (td=0xc7ef5540, pid=-1064840241, status=0xedca5cd8, options=0, rusage=0x0) at ../../../kern/kern_exit.c:696 #6 0xc7c1dd5b in ibcs2_wait (td=0xc7ef5540, uap=0x0) at /usr/src/sys/i386/ibcs2/ibcs2_misc.c:164 #7 0xc080c360 in syscall (frame= {tf_fs = 6160431, tf_es = 589871, tf_ds = -1078001617, tf_edi = 6167724, tf_esi = 639332, tf_ebp = -1077950500, tf_isp = -305504908, tf_ebx = 0, tf_edx = 609623, tf_ecx = 1, tf_eax = 7, tf_trapno = 12, tf_err = 7, tf_eip = 975377, tf_cs = 31, tf_eflags = 2774, tf_esp = -1077950528, tf_ss = 47}) at ../../../i386/i386/trap.c:1004 #8 0xc07f73b2 in Xlcall_syscall () at {standard input}:118 ---Can't read userspace from dump, or kernel process--- -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 13:13:18 2004 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 0C3FF16A4CE for ; Sun, 28 Mar 2004 13:13:18 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBCC243D1F for ; Sun, 28 Mar 2004 13:13:17 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i2SLDHNm079546 for freebsd-current@freebsd.org; Sun, 28 Mar 2004 15:13:17 -0600 (CST) (envelope-from dan) Date: Sun, 28 Mar 2004 15:13:17 -0600 From: Dan Nelson To: freebsd-current@freebsd.org Message-ID: <20040328211316.GO3446@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i Subject: Acquiring lockmgr lock "ufs" with the following non-sleepable locks held: 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, 28 Mar 2004 21:13:18 -0000 Got this warning running an ibcs2_coff binary on today's -current: Acquiring lockmgr lock "ufs" with the following non-sleepable locks held: exclusive sleep mutex system map r = 0 (0xc103b060) locked @ vm/vm_map.c:2869 Stack backtrace: backtrace(c096ad7c,edca5748,115,1,c0947ff8) at backtrace+0x17 witness_warn(5,c093aae8,c087ab88,c0887eb9,c0946320) at witness_warn+0x1c5 lockmgr(c7ed85c0,1030041,c7ed8514,c7ef5540,1030041) at lockmgr+0xd9 ufs_lock(edca57ac,edca57c8,c06ce702,edca57ac,c7ed8514) at ufs_lock+0x4d ufs_vnoperate(edca57ac,c7ed8514,edca57c0,c068c4d7,c096ad68) at ufs_vnoperate+0x18 vn_lock(c7ed8514,1030041,c7ef5540,c06c206c,c7ef3084) at vn_lock+0xf2 vget(c7ed8514,1030041,c7ef5540,45c,0) at vget+0x116 vnode_pager_lock(c7ef3084,0,c0890f91,125,edca58a8) at vnode_pager_lock+0x141 vm_fault(c103b000,edcc8000,1,0,c7ef5540) at vm_fault+0x281 trap_pfault(edca5990,0,edcc8000,0,edcc8000) at trap_pfault+0x172 trap(c1030018,c7ef0010,120010,434000,edcc8000) at trap+0x353 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc0809bdc, esp = 0xedca59d0, ebp = 0xedca5a20 --- slow_copyout(c7c51674,c7ed8514,ee3b4,4003b4,5d074) at slow_copyout+0x4 exec_coff_imgact(edca5b8c,0,c0879fb3,148,c0946320) at exec_coff_imgact+0x3f5 kern_execve(c7ef5540,8107204,8107230,810b004,0) at kern_execve+0x3cc execve(c7ef5540,edca5d14,c,7,3) at execve+0x30 syscall(2f,2f,2f,8107204,8107230) at syscall+0x2a0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (59), eip = 0x807c22f, esp = 0xbfbfc91c, ebp = 0xbfbfc938 --- -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 13:15:21 2004 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 697C616A4CE for ; Sun, 28 Mar 2004 13:15:21 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28EA943D46 for ; Sun, 28 Mar 2004 13:15:21 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i2SLFKhe089036 for freebsd-current@freebsd.org; Sun, 28 Mar 2004 15:15:20 -0600 (CST) (envelope-from dan) Date: Sun, 28 Mar 2004 15:15:20 -0600 From: Dan Nelson To: freebsd-current@freebsd.org Message-ID: <20040328211519.GP3446@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i Subject: Sleeping on "biord" with the following non-sleepable locks held: 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, 28 Mar 2004 21:15:21 -0000 Got this warning running an ibcs2_coff binary on today's -current: Sleeping on "biord" with the following non-sleepable locks held: exclusive sleep mutex system map r = 0 (0xc103b060) locked @ vm/vm_map.c:2869 Stack backtrace: backtrace(c096ad7c,edca55d0,c0882f4b,1,c096b340) at backtrace+0x17 witness_warn(5,c096b340,c087ce7a,c088355f,edca5600) at witness_warn+0x1c5 msleep(d3c2d3e8,c096b340,4c,c088355f,0) at msleep+0x62 bwait(d3c2d3e8,4c,c088355f,20000000,edca56fc) at bwait+0x70 bufwait(d3c2d3e8,0,ffffffff,4000,0) at bufwait+0x38 ufs_bmaparray(c7ed8514,48,0,edca5720,0) at ufs_bmaparray+0x638 ufs_bmap(edca578c,edca57b8,c07c252f,edca578c,0) at ufs_bmap+0x69 ufs_vnoperate(edca578c,0,c089332d,f4,edca5774) at ufs_vnoperate+0x18 vnode_pager_haspage(c7ef3084,122,0,edca5800,edca57fc) at vnode_pager_haspage+0x1cf vm_fault_additional_pages(c2aa77f0,0,0,edca58c4,edca5888) at vm_fault_additional_pages+0xa3 vm_fault(c103b000,edcc8000,1,0,c7ef5540) at vm_fault+0x850 trap_pfault(edca5990,0,edcc8000,0,edcc8000) at trap_pfault+0x172 trap(c1030018,c7ef0010,120010,434000,edcc8000) at trap+0x353 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc0809bdc, esp = 0xedca59d0, ebp = 0xedca5a20 --- slow_copyout(c7c51674,c7ed8514,ee3b4,4003b4,5d074) at slow_copyout+0x4 exec_coff_imgact(edca5b8c,0,c0879fb3,148,c0946320) at exec_coff_imgact+0x3f5 kern_execve(c7ef5540,8107204,8107230,810b004,0) at kern_execve+0x3cc execve(c7ef5540,edca5d14,c,7,3) at execve+0x30 syscall(2f,2f,2f,8107204,8107230) at syscall+0x2a0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (59), eip = 0x807c22f, esp = 0xbfbfc91c, ebp = 0xbfbfc938 --- -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 13:26:01 2004 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 B4BBA16A4CE for ; Sun, 28 Mar 2004 13:26:01 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45A5643D41 for ; Sun, 28 Mar 2004 13:26:01 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i2SLQ0hu009257 for freebsd-current@freebsd.org; Sun, 28 Mar 2004 15:26:00 -0600 (CST) (envelope-from dan) Date: Sun, 28 Mar 2004 15:26:00 -0600 From: Dan Nelson To: freebsd-current@freebsd.org Message-ID: <20040328212600.GQ3446@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i Subject: LOR: "system map @ vm/vm_map.c:2869" vs "Giant @ kern/kern_synch.c:268" 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, 28 Mar 2004 21:26:01 -0000 Got this warning running an ibcs2_coff binary against today's -current. Haven't seen it posted before. Would it be a good idea to change the first line of the LOR warning to list both locks (as in my subject), to make it easier to search the archives (and avoid all of these "vm object" vs "swap_pager swhash" posts)? lock order reversal 1st 0xc103b060 system map (system map) @ vm/vm_map.c:2869 2nd 0xc093a2e0 Giant (Giant) @ kern/kern_synch.c:268 Stack backtrace: backtrace(c087ff6f,c093a2e0,c087bd47,c087bd47,c087cebc) at backtrace+0x17 witness_checkorder(c093a2e0,9,c087cebc,10c,c0687b75) at witness_checkorder+0x6f8 _mtx_lock_flags(c093a2e0,0,c087ceb3,10c,0) at _mtx_lock_flags+0x9d msleep(d3c2d3e8,c096b340,4c,c088355f,0) at msleep+0x594 bwait(d3c2d3e8,4c,c088355f,20000000,edca56fc) at bwait+0x70 bufwait(d3c2d3e8,0,ffffffff,4000,0) at bufwait+0x38 ufs_bmaparray(c7ed8514,48,0,edca5720,0) at ufs_bmaparray+0x638 ufs_bmap(edca578c,edca57b8,c07c252f,edca578c,0) at ufs_bmap+0x69 ufs_vnoperate(edca578c,0,c089332d,f4,edca5774) at ufs_vnoperate+0x18 vnode_pager_haspage(c7ef3084,122,0,edca5800,edca57fc) at vnode_pager_haspage+0x1cf vm_fault_additional_pages(c2aa77f0,0,0,edca58c4,edca5888) at vm_fault_additional_pages+0xa3 vm_fault(c103b000,edcc8000,1,0,c7ef5540) at vm_fault+0x850 trap_pfault(edca5990,0,edcc8000,0,edcc8000) at trap_pfault+0x172 trap(c1030018,c7ef0010,120010,434000,edcc8000) at trap+0x353 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc0809bdc, esp = 0xedca59d0, ebp = 0xedca5a20 --- slow_copyout(c7c51674,c7ed8514,ee3b4,4003b4,5d074) at slow_copyout+0x4 exec_coff_imgact(edca5b8c,0,c0879fb3,148,c0946320) at exec_coff_imgact+0x3f5 kern_execve(c7ef5540,8107204,8107230,810b004,0) at kern_execve+0x3cc execve(c7ef5540,edca5d14,c,7,3) at execve+0x30 syscall(2f,2f,2f,8107204,8107230) at syscall+0x2a0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (59), eip = 0x807c22f, esp = 0xbfbfc91c, ebp = 0xbfbfc938 --- -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 14:20:33 2004 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 768E516A4CE for ; Sun, 28 Mar 2004 14:20:33 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FF9143D2F for ; Sun, 28 Mar 2004 14:20:33 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i2SMKW78092525 for freebsd-current@freebsd.org; Sun, 28 Mar 2004 16:20:32 -0600 (CST) (envelope-from dan) Date: Sun, 28 Mar 2004 16:20:31 -0600 From: Dan Nelson To: freebsd-current@freebsd.org Message-ID: <20040328222031.GA19463@dan.emsphone.com> References: <20040328211018.GN3446@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040328211018.GN3446@dan.emsphone.com> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i Subject: Re: panic: mutex Giant owned at ../../../kern/kern_thread.c:1341 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, 28 Mar 2004 22:20:33 -0000 In the last episode (Mar 28), Dan Nelson said: > Got this running an ibcs2_coff binary on today's kernel: > > (kgdb) where > #6 0xc7c1dd5b in ibcs2_wait (td=0xc7ef5540, uap=0x0) > at /usr/src/sys/i386/ibcs2/ibcs2_misc.c:164 I think this is due to ibcs2_wait being left out when wait4() was converted to giant-free (giant-allergic actually). The following seems to fix it: Index: syscalls.master =================================================================== RCS file: /mnt/emssrv5/home/ncvs/src/sys/i386/ibcs2/syscalls.master,v retrieving revision 1.17 diff -u -r1.17 syscalls.master --- syscalls.master 6 Feb 2004 20:20:07 -0000 1.17 +++ syscalls.master 28 Mar 2004 22:00:40 -0000 @@ -37,7 +37,7 @@ 4 MNOPROTO { int write(int fd, char *buf, u_int nbytes); } 5 STD { int ibcs2_open(char *path, int flags, int mode); } 6 MNOPROTO { int close(int fd); } -7 STD { int ibcs2_wait(int a1, int a2, int a3); } +7 MSTD { int ibcs2_wait(int a1, int a2, int a3); } 8 STD { int ibcs2_creat(char *path, int mode); } 9 NOPROTO { int link(char *path, char *link); } 10 STD { int ibcs2_unlink(char *path); } -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 14:54:08 2004 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 7C25116A4CF; Sun, 28 Mar 2004 14:54:08 -0800 (PST) Received: from pooker.samsco.home (65-101-231-193.dnvr.qwest.net [65.101.231.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B38543D39; Sun, 28 Mar 2004 14:54:08 -0800 (PST) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.home (8.12.10/8.12.10) with ESMTP id i2SMt60v013165; Sun, 28 Mar 2004 15:55:07 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <40675694.3080609@freebsd.org> Date: Sun, 28 Mar 2004 15:49:56 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <20040328211018.GN3446@dan.emsphone.com> <20040328222031.GA19463@dan.emsphone.com> In-Reply-To: <20040328222031.GA19463@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.home cc: freebsd-current@freebsd.org Subject: Re: panic: mutex Giant owned at ../../../kern/kern_thread.c:1341 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, 28 Mar 2004 22:54:08 -0000 Dan Nelson wrote: > In the last episode (Mar 28), Dan Nelson said: > >>Got this running an ibcs2_coff binary on today's kernel: >> >>(kgdb) where >>#6 0xc7c1dd5b in ibcs2_wait (td=0xc7ef5540, uap=0x0) >> at /usr/src/sys/i386/ibcs2/ibcs2_misc.c:164 > > > I think this is due to ibcs2_wait being left out when wait4() was > converted to giant-free (giant-allergic actually). The following seems > to fix it: > > Index: syscalls.master > =================================================================== > RCS file: /mnt/emssrv5/home/ncvs/src/sys/i386/ibcs2/syscalls.master,v > retrieving revision 1.17 > diff -u -r1.17 syscalls.master > --- syscalls.master 6 Feb 2004 20:20:07 -0000 1.17 > +++ syscalls.master 28 Mar 2004 22:00:40 -0000 > @@ -37,7 +37,7 @@ > 4 MNOPROTO { int write(int fd, char *buf, u_int nbytes); } > 5 STD { int ibcs2_open(char *path, int flags, int mode); } > 6 MNOPROTO { int close(int fd); } > -7 STD { int ibcs2_wait(int a1, int a2, int a3); } > +7 MSTD { int ibcs2_wait(int a1, int a2, int a3); } > 8 STD { int ibcs2_creat(char *path, int mode); } > 9 NOPROTO { int link(char *path, char *link); } > 10 STD { int ibcs2_unlink(char *path); } > > I agree that this is appropriate. However, ibcs2_wait() might need to have some proc locks sprinkled into it. It would be good to have someone like John Baldwin comment on it. Scott From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 15:47:14 2004 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 3666F16A4CE for ; Sun, 28 Mar 2004 15:47:14 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5A2243D1D for ; Sun, 28 Mar 2004 15:47:13 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i2SNirxC035686 for ; Sun, 28 Mar 2004 18:44:53 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i2SNiqSB035683 for ; Sun, 28 Mar 2004 18:44:52 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 28 Mar 2004 18:44:52 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: HEADS UP: debug.mpsafenet behavior changing! (turn it off) 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, 28 Mar 2004 23:47:14 -0000 On Mon, 22 Mar 2004, Robert Watson wrote: > This is an advance HEADS UP. This is a reminder e-mail! If you have debug.mpsafenet turned on, please turn of off for the next few weeks. I'll send out e-mails as things move along. I just merged the semantic change to debug.mpsafenet to cover the entire stack, and will now start pushing Giant into socket-related system calls. However, I won't be adding most of the new locking until we've done a review pass on arch@ next week. Thanks! (remainder of my original post below). > Over the next two weeks, I'm going to start merging more significant > parts of the network locking patches. The first change is that the > definition of debug.mpsafenet is going to chang. Up until now, this > tunable has meant: > > If set, don't hold Giant over the lower levels of the network stack and > IP forwarding path. If unset, Giant is held over the lower level parts > of the stack. > > This provided substantial performance benefits on SMP and UP for > forwarding and filtering, but not for locally sourced or sinked network > traffic (as it didn't release Giant higher in the stack). As we push > Giant off the higher levels of the stack, we will be changing how > debug.mpsafenet works. Here's the new definition: > > If set, don't hold Giant over any of the network stack, including the > sockets layer. If unset, Giant is held over all parts of the network > stack. > > It's likely few people are running with debug.mpsafenet; however, if you > are, this is your warning that you'll probably want to stop running with > it shortly. With this change, we will be migrating to a dual-mode stack, > in which you can either run the whole thing with Giant, or none of it. > This approach is substantially easier to implement than a mixed mode > stack, in which some pieces are covered with Giant running side by side > with other pieces that are not. During the migration period to > fine-grained locking (as patches are merged, etc), it will likely be a > very bad idea to run with this tunable set, so turn it off now! > debug.mpsafenet will continue to exist for the forseeable future in some > form, as it will allow non-MPSAFE network stack components to continue to > function, at the cost of performance. > > In the next few days, I will be posting pretty large patchsets to arch@ > and requesting review and testing. I'll commit a note to UPDATING with > similar but abbreviated content. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Senior Research Scientist, McAfee Research > > _______________________________________________ > 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 Sun Mar 28 18:01:35 2004 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 2116716A4CE; Sun, 28 Mar 2004 18:01:35 -0800 (PST) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7122A43D2D; Sun, 28 Mar 2004 18:01:33 -0800 (PST) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with asmtp (Exim 4.30; FreeBSD) id 1B7mwR-000KFV-H2; Mon, 29 Mar 2004 10:55:59 +0800 Message-Id: <6.0.3.0.2.20040329102508.029f5670@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Mon, 29 Mar 2004 11:05:55 +0900 To: freebsd-current@freebsd.org From: Ganbold Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-hackers@freebsd.org Subject: Re: Question regarding shell user creation at login time 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: Mon, 29 Mar 2004 02:01:35 -0000 Hi, I traced sshd using ktrace and it says: ...... 10198 new CALL setuid(0) 10198 new RET setuid -1 errno 1 Operation not permitted 10198 new CALL execve(0x80485d0,0xbfbfed8c,0xbfbfed94) 10198 new NAMI "/home/new/new.pl" 10198 new RET execve -1 errno 13 Permission denied 10198 new CALL exit(0xffffffff) ..... My C program is: #include main(ac, av) char **av; { setuid(0); execv("/home/new/new.pl",av); } Directory: public# ls -la ~new total 46 drwxr-xr-x 2 root wheel 512 Mar 29 09:10 . drwxr-xr-x 8 root wheel 512 Mar 25 15:28 .. -r--r----- 1 root new 767 Mar 24 17:43 .cshrc -r--r----- 1 root new 248 Mar 26 12:32 .login -r--r----- 1 root new 158 Mar 24 17:43 .login_conf -r--r----- 1 root new 373 Mar 24 17:43 .mail_aliases -r--r----- 1 root new 331 Mar 24 17:43 .mailrc -r--r----- 1 root new 797 Mar 24 17:43 .profile -r--r----- 1 root new 276 Mar 24 17:43 .rhosts -r--r----- 1 root new 975 Mar 24 17:43 .shrc -rwsr-x--- 1 root new 4651 Mar 26 08:47 new ---------- 1 root wheel 94 Mar 26 08:47 new.c -r-x------ 1 root wheel 15430 Mar 25 15:16 new.pl -rw-r--r-- 1 root wheel 52 Mar 25 16:52 new.sh Can somebody tell me the reason why it is failed? Thanks in advance, Ganbold From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 18:41:04 2004 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 1559E16A4CE; Sun, 28 Mar 2004 18:41:03 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C56F43D2D; Sun, 28 Mar 2004 18:41:03 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i2T2cexC037172; Sun, 28 Mar 2004 21:38:41 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i2T2ceRl037169; Sun, 28 Mar 2004 21:38:40 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 28 Mar 2004 21:38:40 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ganbold In-Reply-To: <6.0.3.0.2.20040329102508.029f5670@202.179.0.80> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Question regarding shell user creation at login time 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: Mon, 29 Mar 2004 02:41:04 -0000 On Mon, 29 Mar 2004, Ganbold wrote: > Hi, > > I traced sshd using ktrace and it says: > ...... > 10198 new CALL setuid(0) > 10198 new RET setuid -1 errno 1 Operation not permitted > 10198 new CALL execve(0x80485d0,0xbfbfed8c,0xbfbfed94) > 10198 new NAMI "/home/new/new.pl" > 10198 new RET execve -1 errno 13 Permission denied > 10198 new CALL exit(0xffffffff) > ..... Don't you mean to be running /home/new/new instead? new.pl isn't world readable/executable. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research > > My C program is: > > #include > > main(ac, av) > char **av; > { > setuid(0); > execv("/home/new/new.pl",av); > } > > Directory: > > public# ls -la ~new > total 46 > drwxr-xr-x 2 root wheel 512 Mar 29 09:10 . > drwxr-xr-x 8 root wheel 512 Mar 25 15:28 .. > -r--r----- 1 root new 767 Mar 24 17:43 .cshrc > -r--r----- 1 root new 248 Mar 26 12:32 .login > -r--r----- 1 root new 158 Mar 24 17:43 .login_conf > -r--r----- 1 root new 373 Mar 24 17:43 .mail_aliases > -r--r----- 1 root new 331 Mar 24 17:43 .mailrc > -r--r----- 1 root new 797 Mar 24 17:43 .profile > -r--r----- 1 root new 276 Mar 24 17:43 .rhosts > -r--r----- 1 root new 975 Mar 24 17:43 .shrc > -rwsr-x--- 1 root new 4651 Mar 26 08:47 new > ---------- 1 root wheel 94 Mar 26 08:47 new.c > -r-x------ 1 root wheel 15430 Mar 25 15:16 new.pl > -rw-r--r-- 1 root wheel 52 Mar 25 16:52 new.sh > > > Can somebody tell me the reason why it is failed? > > Thanks in advance, > > Ganbold > > _______________________________________________ > 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 Sun Mar 28 19:52:52 2004 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 2077016A4CE; Sun, 28 Mar 2004 19:52:52 -0800 (PST) Received: from mail.itep.ru (thor.itep.ru [194.85.69.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1948143D2F; Sun, 28 Mar 2004 19:52:51 -0800 (PST) (envelope-from gubarev@itep.ru) Received: by mail.itep.ru (Postfix, from userid 44) id 07F2E15AB2C; Mon, 29 Mar 2004 07:52:49 +0400 (MSD) Received: from lattice.itep.ru (lattice.itep.ru [193.124.225.175]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.itep.ru (Postfix) with ESMTP id 7774E15AB4D; Mon, 29 Mar 2004 07:52:48 +0400 (MSD) Received: from lattice.itep.ru (localhost [127.0.0.1]) by lattice.itep.ru (8.12.11/8.12.4) with ESMTP id i2T3ql0Z017584; Mon, 29 Mar 2004 07:52:47 +0400 Received: from localhost (gubarev@localhost) by lattice.itep.ru (8.12.11/8.12.4) with ESMTP id i2T3qlGp017581; Mon, 29 Mar 2004 07:52:47 +0400 Date: Mon, 29 Mar 2004 07:52:47 +0400 (MSD) From: gubarev@itep.ru To: John Baldwin Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on thor.itep.ru X-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,NO_REAL_NAME autolearn=no version=2.63 X-Spam-Level: cc: freebsd-current@FreeBSD.org cc: gubarev@itep.ru Subject: Re: hang/panic of 5.2.1-RELEASE installation. 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: Mon, 29 Mar 2004 03:52:52 -0000 On Fri, 26 Mar 2004, John Baldwin wrote: > On Friday 26 March 2004 04:54 am, gubarev@itep.ru wrote: > > Dear all, > > > > fresh installation of 5.2.1-RELEASE fails here with > > funny symptoms which apparently was never discussed before > > (at least I failed to find anything similar). Machine basically > > is P4 with 1Gb RAM, ATI Radeon 9000 (laptop - see below for details). > > > > 1. With HTT enabled and almost all devices disabled (via BIOS) > > I have a strictly reproducible kernel panic right after interrupts > > assignment. The relevant kernel message is > > > > "panic: interrupt from missing bus" > > > > which seems to be from sys/i386/i386/mptable.c. The verbose boot > > and panic messages are given below. > > > > 2. Without HTT and with other devices enabled machine completely hangs > > just at "Mounting root from ...". Perhaps this is usual hardware > > conflict although I'm not sure. > > > > Any help will be greatly appreciated. Any additional details could > > be provided immediately..... > > Can you post the output of mptable? Sorry, I see no way to do that - kernel is not loading at all, this was an installation attempt. From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 20:09:36 2004 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 BB33B16A4CE for ; Sun, 28 Mar 2004 20:09:36 -0800 (PST) Received: from mail.itep.ru (thor.itep.ru [194.85.69.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76D3B43D39 for ; Sun, 28 Mar 2004 20:09:36 -0800 (PST) (envelope-from gubarev@itep.ru) Received: by mail.itep.ru (Postfix, from userid 44) id 6905E15AC4B; Mon, 29 Mar 2004 08:09:35 +0400 (MSD) Received: from lattice.itep.ru (lattice.itep.ru [193.124.225.175]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.itep.ru (Postfix) with ESMTP id E9C6715AB2C; Mon, 29 Mar 2004 08:09:34 +0400 (MSD) Received: from lattice.itep.ru (localhost [127.0.0.1]) by lattice.itep.ru (8.12.11/8.12.4) with ESMTP id i2T49YsH017625; Mon, 29 Mar 2004 08:09:34 +0400 Received: from localhost (gubarev@localhost) by lattice.itep.ru (8.12.11/8.12.4) with ESMTP id i2T49Wn2017622; Mon, 29 Mar 2004 08:09:34 +0400 Date: Mon, 29 Mar 2004 08:09:32 +0400 (MSD) From: gubarev@itep.ru To: Doug White Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on thor.itep.ru X-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,NO_REAL_NAME autolearn=no version=2.63 X-Spam-Level: cc: freebsd-current@freebsd.org cc: Gubarev Fedor Subject: Re: hang/panic of 5.2.1-RELEASE installation. 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: Mon, 29 Mar 2004 04:09:36 -0000 On Fri, 26 Mar 2004, Doug White wrote: > On Fri, 26 Mar 2004 gubarev@itep.ru wrote: > > > > > fresh installation of 5.2.1-RELEASE fails here with > > funny symptoms which apparently was never discussed before > > (at least I failed to find anything similar). Machine basically > > is P4 with 1Gb RAM, ATI Radeon 9000 (laptop - see below for details). > > > > 1. With HTT enabled and almost all devices disabled (via BIOS) > > I have a strictly reproducible kernel panic right after interrupts > > assignment. The relevant kernel message is > > > > "panic: interrupt from missing bus" > > You have ACPI disabled it appears .. have you tried enabling it? Sure, I tried, the only difference on boot is "ACPI autoload failed - no such file or directory" before kernel loading. Seems ACPI module is missing on installation media? > It sounds like your mptable is corrrupted... check for a BIOS update. Will try that although not sure whether it'll help.... From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 22:16:31 2004 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 28D4A16A4CE for ; Sun, 28 Mar 2004 22:16:31 -0800 (PST) Received: from leticia.terra.com.br (leticia.terra.com.br [200.154.55.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDF8643D55 for ; Sun, 28 Mar 2004 22:16:30 -0800 (PST) (envelope-from m0f0x@sdf.lonestar.org) Received: from talara.terra.com.br (talara.terra.com.br [200.154.55.136]) by leticia.terra.com.br (Postfix) with ESMTP id 132AD3C17A for ; Mon, 29 Mar 2004 03:16:28 -0300 (BRT) Received: from m0f0x.localdomain (unknown [200.228.78.17]) (authenticated user m0f0x) by talara.terra.com.br (Postfix) with ESMTP id B05603C00D for ; Mon, 29 Mar 2004 03:16:26 -0300 (BRT) To: freebsd-current@freebsd.org References: <007d01c414ff$005bf8e0$0300a8c0@scales> Message-ID: From: m0f0x Content-Type: text/plain; format=flowed; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Mon, 29 Mar 2004 03:17:02 -0300 In-Reply-To: <007d01c414ff$005bf8e0$0300a8c0@scales> User-Agent: Opera7.23/FreeBSD M2 build 518 Subject: Re: Pthread Issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: m0f0x@sdf.lonestar.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2004 06:16:31 -0000 I've got the same problems, when using CURRENT (cvsupped on 25/03). May apps (like xmms, mplayer, and others that I've forgot) where generating core dumps, even when they're rebuilded. Anybody got solutions? My temporary solution was: move back do 5.2.1-RELEASE (p3). Thanks in advance, m0f0x On Sun, 28 Mar 2004 13:58:11 -0600, Jeff Mitchell wrote: > Current folks-- > > I'm having some major issues with pthreads. I have a base 5.2 > cvsupgraded to 5.2.1. To save a lot of copying and pasting and keep > this message from being too long, please check: > > http://lists.freebsd.org/pipermail/freebsd-hackers/2004-March/006393.html > and > http://lists.freebsd.org/pipermail/freebsd-ports/2004-March/010982.html > > for more information that might give clues to some of the issues. > > At someone's request tried the following (in > /usr/ports/net/openldap21-client) > > shocker1# make -VOSVERSION -VPTHREAD_CFLAGS -VPTHREAD_LIBS > 502010 > -D_THREAD_SAFE > -lc_r > > Someone else suggested creating a /etc/libmap.conf with the following: > > libpthread.so.1 libc_r.so.5 > libpthread.so libc_r.so > > None of this has worked, however. It was mentioned to me that "checking > for pthread_create in default libraries" is supposed to be successful, > so maybe something went wrong with my base system upgrade. > > I have no idea, personally. Anyone that could help me out, it'd be much > appreciated, as I'm pretty much barred from upgrading a significant > number of my ports beause of dependencies on the ones that are failing. > > If there's any other information that would be helpful, please let me > know. > > Thanks, > Jeff From owner-freebsd-current@FreeBSD.ORG Mon Mar 29 02:59:36 2004 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 2663816A4CE for ; Mon, 29 Mar 2004 02:59:36 -0800 (PST) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BA1F43D45 for ; Mon, 29 Mar 2004 02:59:35 -0800 (PST) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with asmtp (Exim 4.30; FreeBSD) id 1B7vLJ-000Nnt-H8 for freebsd-current@freebsd.org; Mon, 29 Mar 2004 19:54:13 +0800 Message-Id: <6.0.3.0.2.20040329195802.02a17ae0@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Mon, 29 Mar 2004 20:04:33 +0900 To: freebsd-current@freebsd.org From: Ganbold Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: Question regarding shell user creation at login time - SOLVED 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: Mon, 29 Mar 2004 10:59:36 -0000 Hi, I solved my problem. The problem was totally due to my fault. The problem was I mounted /home partition with nosuid option. Sorry for creating big threads in mailing list for this issue. I apologize if I made any inconvenience for all. Thanks for all, Ganbold From owner-freebsd-current@FreeBSD.ORG Mon Mar 29 03:53:48 2004 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 07E5616A4CE for ; Mon, 29 Mar 2004 03:53:48 -0800 (PST) Received: from e-post02.e-se.ru (smtp.mail.km.ru [217.174.99.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB03543D55 for ; Mon, 29 Mar 2004 03:53:46 -0800 (PST) (envelope-from el2000@km.ru) Received: from www3.comptech.local ( [81.26.156.34]) by e-post02.e-se.ru with ESMTP id 120DFC8C3084898039616; Mon, 29 Mar 2004 15:53:56 +0400 Date: Mon, 29 Mar 2004 15:53:32 +0400 From: Eugene Lisitsky X-Priority: 3 (Normal) Message-ID: <982645672.20040329155332@km.ru> To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Mouse bugs and devfs. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eugene Lisitsky List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2004 11:53:48 -0000 Hello All! Recently I worked in Kivio (from KDE 3.2.1; program was compiled from ports) with mouse and keyboard. During the moving object with pressed Ctrl key the bug occured. Mouse cursor stalled on the screen and didn't answer on mouse moving or pressing it's keys. I switched to a console, but mouse didn't work there even the cursor was not visible. I restated moused, cursor appeared, but didn't move with mouse and disappered on keyboard pressing. So this bug isn't in moused but in mouse ports. Is there way to reset mouse port or reinitialize device in devfs? I deleted /dev/psm0, after that moused didn't start with message "Device /dev/psm0 not found". Is it possible to recreate device "on the fly"? Such as /dev/da0 can appear and disapper on attaching and detaching flash bar drive. I guess there must be a system call to rescan devices. I found only one - reboot :( System: i386 CPU - Celeron 1.7GHz FreeBSD 5.2.1-RELEASE, installed 5.2 and then recompiled with 5.2.1 sources. Mouse PS/2. Thank you. -- Best regards, Eugene mailto:el2000@km.ru From owner-freebsd-current@FreeBSD.ORG Mon Mar 29 04:36:28 2004 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 816D316A4CE for ; Mon, 29 Mar 2004 04:36:28 -0800 (PST) Received: from vimes.aminor.no (vimes.aminor.no [213.187.177.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0050143D41 for ; Mon, 29 Mar 2004 04:36:28 -0800 (PST) (envelope-from eivind@aminor.no) Received: from localhost (localhost.eivind [127.0.0.1]) by vimes.aminor.no (Postfix) with ESMTP id 171F717889 for ; Mon, 29 Mar 2004 14:36:26 +0200 (CEST) Received: from vimes.aminor.no ([127.0.0.1]) by localhost (vimes.eivind [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85300-09 for ; Mon, 29 Mar 2004 14:36:19 +0200 (CEST) Received: from [10.122.7.143] (nextra-3-244.nextra.no [148.122.3.244]) by vimes.aminor.no (Postfix) with ESMTP id 9453717887 for ; Mon, 29 Mar 2004 14:36:19 +0200 (CEST) Date: Mon, 29 Mar 2004 14:39:06 +0200 From: Eivind Olsen To: freebsd-current@freebsd.org Message-ID: <80149338.1080571146@[10.122.7.143]> X-Mailer: Mulberry/3.1.2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at aminor.no Subject: Problems with "Unable to read from thread kernel pipe" 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: Mon, 29 Mar 2004 12:36:28 -0000 Hello. I'm currently running FreeBSD 5.2.1-RELEASE-p3 and I'm having problems with Apache2 / PHP4. For some reason Apache has started to cause some problems. The symptoms are that all the httpd-processes start to consume all the CPU-time and things slow down. If I then stop Apache I am left with some zombie httpd-processes. In my httpd-error.log file I see the following: [Mon Mar 29 13:33:04 2004] [notice] suEXEC mechanism enabled (wrapper: /usr/local/sbin/suexec) [Mon Mar 29 13:33:07 2004] [notice] Apache/2.0.49 (Unix) PHP/4.3.5 mod_ssl/2.0.49 OpenSSL/0.9.7c-p1 configured -- resuming normal operations Fatal error 'Unable to read from thread kernel pipe' at line 1100 in file /usr/src/lib/libc_r/uthread/uthread_kern.c (errno = 0) [Mon Mar 29 13:36:41 2004] [notice] child pid 85040 exit signal Abort trap (6) Fatal error 'Unable to read from thread kernel pipe' at line 1100 in file /usr/src/lib/libc_r/uthread/uthread_kern.c (errno = 0) [Mon Mar 29 13:37:18 2004] [notice] child pid 85042 exit signal Abort trap (6) This seems to point back to something in the base system, right? I've searched for the text "Unable to read from thread kernel pipe" and haven't found any solutions, but I've found the PR 63670 which has been reported regarding Gtk2-Perl + Perl 5.8.2 (Yes, I have Perl 5.8.2 installed here, I'll try to reinstall 5.6.x and see if this helps). Here's some information regarding my system: vimes# uname -a FreeBSD vimes.eivind 5.2.1-RELEASE-p3 FreeBSD 5.2.1-RELEASE-p3 #0: Wed Mar 17 23:55:35 CET 2004 root@vimes.eivind:/usr/obj/usr/src/sys/VIMES i386 vimes# (the VIMES-kernel here is GENERIC + ipfilter compiled into the kernel) Here are the libraries /usr/local/sbin/httpd are linking against: vimes# ldd httpd httpd: libz.so.2 => /lib/libz.so.2 (0x280c0000) libssl.so.3 => /usr/lib/libssl.so.3 (0x280ce000) libcrypto.so.3 => /lib/libcrypto.so.3 (0x28100000) libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9 (0x28210000) libexpat.so.5 => /usr/local/lib/libexpat.so.5 (0x28223000) libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x28243000) libm.so.2 => /lib/libm.so.2 (0x28260000) libcrypt.so.2 => /lib/libcrypt.so.2 (0x28279000) libc.so.5 => /lib/libc.so.5 (0x28292000) vimes# Does anyone have any suggestions? -- Regards / Hilsen Eivind Olsen From owner-freebsd-current@FreeBSD.ORG Sun Mar 28 22:01:01 2004 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 A2F7816A4CE for ; Sun, 28 Mar 2004 22:01:01 -0800 (PST) Received: from skyweb.ca (smtp-1.vancouver.ipapp.com [216.152.192.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32D5B43D31 for ; Sun, 28 Mar 2004 22:01:01 -0800 (PST) (envelope-from mjohnston@skyweb.ca) Received: from [192.168.0.3] ([64.42.246.20]) by smtp-1.vancouver.ipapp.com ; Sun, 28 Mar 2004 22:00:58 -0800 From: Mark Johnston To: current@freebsd.org Content-Type: text/plain Message-Id: <1080540061.3799.2.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 29 Mar 2004 00:01:02 -0600 Content-Transfer-Encoding: 7bit X-Rcpt-To: X-Country: CA X-Mailman-Approved-At: Mon, 29 Mar 2004 05:11:37 -0800 Subject: cvs-src summary for 03/28/2004 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: Mon, 29 Mar 2004 06:01:01 -0000 FreeBSD cvs-src summary for 21/03/04 to 28/03/04 ++++++++++++++++++++++++++++++++++++++++++++++++ This is a regular weekly summary of FreeBSD's cutting-edge development. It is intended to help the FreeBSD community keep up with the fast-paced work going on in FreeBSD-CURRENT by distilling the deluge of data from the CVS mailing list into a (hopefully) easy-to-read newsletter. This newsletter is marked up in reStructuredText_, so any odd punctuation that you see is likely intended for the reST parser. .. _reStructuredText: http://docutils.sourceforge.net/rst.html You can get old summaries, and an HTML version of this one, at http://www.xl0.org/FreeBSD/. Please send any comments to Mark Johnston (mark at xl0.org). For Lukasz Dudek and Szymon Roczniak's Polish translations of these summaries, which may lag the English ones slightly, please see http://mocart.pinco.pl/FreeBSD/. .. contents:: ============ New features ============ truss enhanced to decode more structures ---------------------------------------- David Malone (dwmalone) committed code to truss, which traces the system calls a program is executing, that allows it to decode many structures passed to and from system calls, producing more useful output. The code was initially contributed by Dan Nelson in `PR 52190`_, and has been modified somewhat by David. .. _`PR 52190`: http://www.freebsd.org/cgi/query-pr.cgi?pr=52190 http://docs.freebsd.org/cgi/mid.cgi?200403231237.i2NCb3vw085027 Build target added to build the toolchain only ---------------------------------------------- Ruslan Ermilov (ru) added a target to the system Makefile called "toolchain", which does the same thing as buildworld, but stops before actually building the world; i.e., it rebuilds only the tools and libraries. With these changes, individual parts of world can be built alone, or the kernel can be built without the world. To find out how to do this, see a `follow-up from Ruslan`. The toolchain target should be used only if you're sure you know what you're doing; the only supported upgrade path is still as `documented in the Handbook`. .. _`follow-up from Ruslan`: http://docs.freebsd.org/cgi/mid.cgi?20040324151245.GD42844 .. _`documented in the Handbook`: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html http://docs.freebsd.org/cgi/mid.cgi?200403240826.i2O8QMoF087714 Multicast group support added to netstat ---------------------------------------- Bruce M. Simpson (bms) added support to netstat to print the multicast groups that the system belongs to. This function is called automatically when netstat is used, so no new command-line flags are necessary. http://docs.freebsd.org/cgi/mid.cgi?200403250843.i2P8hx6g047670 pkill and pgrep commands added ------------------------------ Garance A. Drosehn added the pkill and pgrep commands from NetBSD, applying a number of patches written by Mario Sergio Fujikawa Ferreira (lioux) for the sysutils/pkill port. pgrep is used to search the process table on the system, like ps | grep, and pkill is used to kill processes matching a given pattern, like killall. http://docs.freebsd.org/cgi/mid.cgi?200403251908.i2PJ8m91006049 =============== Notable changes =============== debug.mpsafenet temporarily out of order ---------------------------------------- Robert Watson (rwatson) added the following note to UPDATING: The debug.mpsafenet tunable controls whether the kernel Giant lock is held across the lower levels of the network stack, and by default is turned off. In the few days following 20040322, the behavior of debug.mpsafenet will change such that this tunable controls Giant over all levels of the network stack. If you are currently setting debug.mpsafenet to 1, you should set it back to 0 (the default) again during the change-over. An additional note will be added to UPDATING when sufficient locking is merged to permit this to take place. http://docs.freebsd.org/cgi/mid.cgi?200403221637.i2MGbXxb090535 UTF-8 versions added for all supported locales ---------------------------------------------- Tim J. Robbins (tjr) committed Unicode UTF-8 versions of all of the supported system locales. The UTF-8 locales were previously available in Hye-Shik Chang (perky)'s misc/utf8locale port. Most of the work for this commit was done by Hye-Shik in that port. For a precise list of the exact locales affected, please see the commit message below. http://docs.freebsd.org/cgi/mid.cgi?200403270814.i2R8EGiO061708 Diskless boot system split up ----------------------------- Brooks Davis (brooks) split the diskless rc script, which sets up filesystems for a diskless system, into hostname, resolve, tmp, and var pieces. He has also improved the scripts to create /tmp and /var automatically if they aren't writable, rather than triggering when / is NFS mounted. http://docs.freebsd.org/cgi/mid.cgi?200403232322.i2NNMZLe056410 Major Firewire enhancements; also MFC'ed ---------------------------------------- Hidetoshi Shimokawa (simokawa) committed many enhancements to the Firewire code, improving compatibility with 4.x and DragonFly BSD, improving device probing, and fixing other bugs in both the Firewire and the SBP-2 (serial Bus Protocol) support required for Firewire-based storage devices. This work was also merged to 4.x. http://docs.freebsd.org/cgi/mid.cgi?200403262317.i2QNHBgY030234 i386 pipe performance significantly improved -------------------------------------------- Alan Cox (alc) removed some unnecessary code from the pipe system, adjusting the optimized case. This eliminates the sysctls kern.ipc.maxpipekvawired and kern.ipc.amountpipekvawired, and speeds up pipes on i386 significantly. For instance, on a 2.4GHz Xeon, Alan saw the pipe bandwidth increase from 1050 MB/s to 1850 MB/s. http://docs.freebsd.org/cgi/mid.cgi?200403271950.i2RJoN9P033780 Most PicoBSD floppy image scripts removed ----------------------------------------- Luigi Rizoz (luigi) removed the net, router, isp, and dial floppy types for PicoBSD, a compact build of FreeBSD. In -CURRENT, only a single base floppy type will be supported, with users building on that to suit their needs. http://docs.freebsd.org/cgi/mid.cgi?200403240751.i2O7peAO079157 http://docs.freebsd.org/cgi/mid.cgi?200403240753.i2O7rCg0079966 http://docs.freebsd.org/cgi/mid.cgi?200403240754.i2O7s0mH080045 http://docs.freebsd.org/cgi/mid.cgi?200403240755.i2O7t9Nq080220 ================= Discussion topics ================= doscmd moved from base system to ports tree ------------------------------------------- Dag-Erling Smorgrav removed doscmd, a basic DOS emulator, from the base system, since it has been moved to ports. This sparked a few threads of confusion. David O'Brien (obrien) asked whether there was really consensus for the change; Dag-Erling said that there had been. Garance A. Drosihn (gad) disagreed, saying that he had thought it was going to stay until 6.0. Julian Elischer agreed with Garance. Doug Barton (dougb) gave his impression of the conversation, ending with Tim J. Robbins (tjr)'s suggestion that waiting until 6.0 could work, but if that wasn't the plan, doscmd should be removed before 5.3. Julian, John Baldwin (jhb), and Tim followed up, saying that each had different impressions of the original discussion, but that they all agreed that doscmd should stay gone. Garance and Dag-Erling also posted their impressions of the initial discussion, differing again on the details, but again not arguing that doscmd should return. Alexey Dokuchaev (danfe) expressed his disappointment at the removal, since he had planned to improve doscmd. Dag-Erling clarified that doscmd is still available in the projects repository; Alexey answered that he had missed that. http://docs.freebsd.org/cgi/mid.cgi?200403232227.i2NMRQn5042762 ================= Committer changes ================= Wilko Bulte (wilko), acting as the core secretary, moved Hiten Pandya (hmp) from being a doc-only committer to a src committer. Dag-Erling Smorgrav (des) will be his mentor. http://docs.freebsd.org/cgi/mid.cgi?200403231935.i2NJZ4BU098762 =================== Important bug fixes =================== Local denial-of-service bug in VM system fixed ---------------------------------------------- Tim J. Robbins (tjr) fixed a bug in the VM code that allowed a user to force the kernel to allocate an unlimited amount of memory, causing a panic or system hang. Tim has also seen the bug occur without any malicious user input. I'm not sure whether other FreeBSD versions are affected by the bug. http://docs.freebsd.org/cgi/mid.cgi?200403230837.i2N8bZe4025918 Crash when using setsockopt on IPv6 sockets eliminated ------------------------------------------------------ Hajimu Umemoto committed a fix to the IPv6 code that prevents a crash when setsockopt() is given invalid parameters. Before the fix, regular users could crash the system using setsockopt() on v6 sockets. This problem was reported by Katsuhisa ABE in `PR 61513`_. .. _`PR 61513`: http://www.freebsd.org/cgi/query-pr.cgi?pr=61513 http://docs.freebsd.org/cgi/mid.cgi?200403261952.i2QJqIrp078521 Information leak in process separation fix MFC'ed ------------------------------------------------- Pawel Jakub Dawidek (pjd) MFC'ed the fix to the information leak problem `mentioned last week`_. Again, this fix prevents processes from circumventing restrictions on seeing one another. .. _`mentioned last week`: http://excel.xl0.org/FreeBSD/21-03-04.html#information-leak-in-process-separation-fixed http://docs.freebsd.org/cgi/mid.cgi?200403262207.i2QM7SPX014969 =============== Other bug fixes =============== Bill Paul (wpaul) committed a fix to the VM subsystem that allows threads to be created with extra stack pages. This bug was preventing his fixing the `problem with the Intel Centrino 2200BG`_ wireless networking chip mentioned last week. With the VM problem fixed, the Centrino problem has been eliminated. .. _`problem with the Intel Centrino 2200BG`: http://excel.xl0.org/FreeBSD/21-03-04.html#other-bug-fixes http://docs.freebsd.org/cgi/mid.cgi?200403220028.i2M0ScPc047763 Thomas Moestl (tmm) fixed the isp driver, supporting Qlogic-based SCSI and fibre channel cards, to work properly on Sparc-64-based systems. The problem was reported, and the fix tested, by Marius Strobl. http://docs.freebsd.org/cgi/mid.cgi?200403232341.i2NNfdlU060190 Bruce M. Simpson (bms) fixed the madvise() system call to work under Linux binary emulation; it was previously unimplemented. The fix was submitted by Matthias Schuendehuette, who reports that it makes the Linux binaries of StarOffice 7.0 work. http://docs.freebsd.org/cgi/mid.cgi?200403282143.i2SLhRK6021263 Max Laier (mlaier) imported fixes to the PF packet filter from OpenBSD's stable branch. The first fix makes binat work for incoming connections when a netblock is used as the source in the rule, and the second corrects a kernel panic when an anchor ruleset is empty. The first bug was reported to OpenBSD by Karl O. Pinc. http://docs.freebsd.org/cgi/mid.cgi?200403281931.i2SJVnQc086555 From owner-freebsd-current@FreeBSD.ORG Mon Mar 29 01:33:04 2004 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 53FEB16A4CE for ; Mon, 29 Mar 2004 01:33:04 -0800 (PST) Received: from boggle.pobox.com (boggle.pobox.com [208.58.1.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1510C43D45 for ; Mon, 29 Mar 2004 01:33:04 -0800 (PST) (envelope-from b.candler@pobox.com) Received: from colander (localhost [127.0.0.1]) by boggle.pobox.com (Postfix) with ESMTP id 783477F9BA for ; Mon, 29 Mar 2004 04:33:03 -0500 (EST) Received: from jester.pobox.com (jester.pobox.com [64.71.166.114]) by boggle.pobox.com (Postfix) with ESMTP for ; Mon, 29 Mar 2004 04:33:03 -0500 (EST) Received: from vaio.linnet.org (unknown [80.44.130.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jester.pobox.com (Postfix) with ESMTP id 7797E88 for ; Mon, 29 Mar 2004 04:33:02 -0500 (EST) Received: from brian by vaio.linnet.org with local (Exim 4.30) id 1B7t8d-000AcT-OX for freebsd-current@freebsd.org; Mon, 29 Mar 2004 10:32:59 +0100 Date: Mon, 29 Mar 2004 10:32:59 +0100 From: Brian Candler To: freebsd-current@freebsd.org Message-ID: <20040329093259.GB40784@uk.tiscali.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Mon, 29 Mar 2004 05:11:37 -0800 Subject: Filesystem panic in 5.2.1-RELEASE 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: Mon, 29 Mar 2004 09:33:04 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Oops, posted this to the wrong list. Summary: I built a new 5.2.1 system yesterday, and it was fine while building a new kernel. This morning I've had it panic twice while doing relatively innocuous things, details attached. I've had it suggested to me that I should disable ACPI, so I have now added hints.acpi.0.disabled="1" to /boot/device.hints I'll see if that makes anything more stable, but otherwise I'd be interested in other people's comments about the crashes I've seen. I would have stuck with 4.x, except the nVidia ethernet driver wasn't supported, so I thought that would be a good reason to try 5.2.1 (answer: that doesn't support the network driver either! But there's a separate module available) Regards, Brian. --YZ5djTAD1cGYuMQK Content-Type: message/rfc822 Content-Disposition: inline Date: Mon, 29 Mar 2004 09:31:32 +0100 From: Brian Candler To: freebsd-stable@freebsd.org Subject: Filesystem panic in 5.2.1-RELEASE Message-ID: <20040329083132.GA40513@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Oh dear, my first experience with FreeBSD-5.2.1-RELEASE is not good: --------------------------------------------------------------------------- ... playdog# mv downloads /v/downloads/nvidia playdog# ln -s ../v/downloads . mode = 040700, inum = 82, fs = /u panic: ffs_valloc: dup alloc syncing disks, buffers remaining... 131 131 129 129 129 129 129 129 129 129 12 9 129 129 129 129 129 129 129 129 129 129 129 giving up on 90 buffers Uptime: 18m55s Shutting down ACPI Automatic reboot in 15 seconds - press a key on the console to abort --------------------------------------------------------------------------- This is a freshly-installed machine [*]: Soltek EQ3702A Athlon 2500+ processor (166MHz FSB), 512MB RAM (166MHz) nVidia chipset /u and /v are two slices on the same Western Digital 80GB IDE drive. [*] Actually it previously had a 4.8 install on it. I did an install over and newfs'd all the slices except data slices /u, /v, /w; I noticed that sysinstall did an fsck_ffs on those slices. I had compiled and was running my own kernel, which was just GENERIC with some stuff taken out (removed I486/I586, INET6, most of the SCSI stuff). I was getting ready to compile an nvidia network driver - I had attached a USB floppy, copied some files off it, and unmounted the floppy, before doing the lines shown above. The system was running for several hours yesterday, including a complete kernel rebuild, without any crashing - so I'm fairly sure the hardware is OK. The only odd thing I have noticed about this system is that when running the GENERIC kernel (from the install CD or after installation), it locks up just after mounting the root filesystem, requiring a hard reboot. The only way to get round this is to choose "safe mode" at boot time. However when running my own compiled kernel I don't have this problem. A diff of my kernel against GENERIC is attached. Sorry I don't have anything else like a crash dump. I was rather hoping not to see this sort of problem with 5.2.1; maybe I should just install 4.9 instead :-( Regards, Brian. --YZ5djTAD1cGYuMQK Content-Type: message/rfc822 Content-Disposition: inline Date: Mon, 29 Mar 2004 09:49:06 +0100 From: Brian Candler To: freebsd-stable@freebsd.org Subject: Re: Filesystem panic in 5.2.1-RELEASE Message-ID: <20040329084906.GA40570@uk.tiscali.com> References: <20040329083132.GA40513@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040329083132.GA40513@uk.tiscali.com> User-Agent: Mutt/1.4.1i Whoa, another crash, this time when plugging in the USB floppy: playdog# umass0: Y-E DATA FlashBuster-U, rev 1.00/1.14, addr 2 umass0: at uhub1 port 3 (addr 2) disconnected umass0: detached Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code = supervisor read, page not present instruction pointer = 0x8:0xc04a17f0 stack pointer = 0x10:0xd62b2c90 frame pointer = 0x10:0xd62b2cb0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processr eflags = interrupt enabled, resume, IPOL = 0 current process = 28 (swi8: tty:sio clock) trap number = 12 panic: page fault syncing disks, buffers remaining... 265 265 265 265 265 265 265 265 265 265 265 265 265 265 265 265 265 265 265 265 giving up on 191 buffers Uptime: 17m13s Shutting down ACPI Automatic reboot in 15 seconds - press a key on the console to abort Given the amazingly good track record of 4.x, I guess I really should be suspecting a hardware problem now. But to be sure I need to downgrade to 4.x - which I hope doesn't mean losing my ufs2 filesystems :-( At least my filesystems are being checked in the background now... Regards, Brian. --YZ5djTAD1cGYuMQK-- From owner-freebsd-current@FreeBSD.ORG Mon Mar 29 05:15:28 2004 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 55E6716A4CE for ; Mon, 29 Mar 2004 05:15:28 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0D2843D53 for ; Mon, 29 Mar 2004 05:15:27 -0800 (PST) (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 i2TDFRtf018657; Mon, 29 Mar 2004 08:15:27 -0500 (EST) Date: Mon, 29 Mar 2004 08:15:27 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: m0f0x In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Pthread Issues 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: Mon, 29 Mar 2004 13:15:28 -0000 On Mon, 29 Mar 2004, m0f0x wrote: > I've got the same problems, when using CURRENT (cvsupped on 25/03). May > apps (like xmms, mplayer, and others that I've forgot) where generating > core dumps, even when they're rebuilded. > > Anybody got solutions? My temporary solution was: move back do > 5.2.1-RELEASE (p3). You guys don't have libc_r installed. None of the autoconf scripts showed that libc_r was found. Come on guys -- look at the messages from the scripts. You've hosed your system somehow. -- Dan Eischen From owner-freebsd-current@FreeBSD.ORG Mon Mar 29 07:39:26 2004 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 075B516A4CE for ; Mon, 29 Mar 2004 07:39:26 -0800 (PST) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7822043D54 for ; Mon, 29 Mar 2004 07:39:25 -0800 (PST) (envelope-from kirk@strauser.com) Received: from pooh.strauser.com (pooh.honeypot.net [10.0.5.128]) by kanga.honeypot.net (8.12.11/8.12.11) with ESMTP id i2TFdNEW041812 for ; Mon, 29 Mar 2004 09:39:24 -0600 (CST) (envelope-from kirk@strauser.com) To: freebsd-current@freebsd.org From: Kirk Strauser Date: Mon, 29 Mar 2004 09:39:20 -0600 Message-ID: <87k713ek7r.fsf@strauser.com> Lines: 61 X-Mailer: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65', clamav-milter version '0.60p' Subject: My vinum scare 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: Mon, 29 Mar 2004 15:39:26 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable Yesterday, I updated my system from a 5.1-CURRENT build on 2004-01-29 to recent source. All of my filesystems, except for root and swap, are on vinum volumes for flexibility in management. After the 'installkernel' step, I rebooted into single-user to make installworld and run mergemaster, and this completed successfully. Then, I rebooted to bring the system back online. That's when I discovered that vinum had totally lost all of its configuration information, except for the name of the single drive ("wd120") that I use. Following the instructions at http://www.vinumvm.org/vinum/how-to-debug.html, I got: # < log tr -d '\000-\011\200-\377' IN VINOkanga.honeypot.netwd120a>P.pMg@[obme>MBR da0 2 r0w0e0 r0w0e0 da0s4 'vinum dumpconfig' reported nothing but the definition of the "wd120" drive: no volumes, plexes, or subdisks. Nothing. At this point, I had a minor heart attack. Once I stepped back, I remembered that I *always* use 'printconfig' to write a copy of my configuration to /etc/vinum.conf. A quick 'vinum create' command had me back up and running with no ill effects. I have no idea what happened, but I ask that you trust me when I say that I hadn't touched vinum at all during the system update. Two lessons: 1) Realizing that you have a backup of such critical data as your vinum configuration is one of the best feelings in the world. 2) Realizing that in the event of failure of lesson #1, that you still have a full backup to tape from a few hours earlier, and that no matter *what* happens, you're only an hour away from having your system back... It doesn't get much better than that. =2D-=20 Kirk Strauser "94 outdated ports on the box, 94 outdated ports. Portupgrade one, an hour 'til done, 82 outdated ports on the box." --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAaEMr5sRg+Y0CpvERAm2KAJwI3DTr6cwiO1+q1ouWkjHZxYKL9ACeK9U6 lOaL/KgbRfq3CnZepGXBfnY= =crDY -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-current@FreeBSD.ORG Mon Mar 29 07:40:00 2004 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 E00DF16A4CE for ; Mon, 29 Mar 2004 07:40:00 -0800 (PST) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CD4B43D46 for ; Mon, 29 Mar 2004 07:39:59 -0800 (PST) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1B7yrm-0007VP-00 for ; Mon, 29 Mar 2004 17:39:58 +0200 Received: from mulder.f5.com ([205.229.151.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Mar 2004 17:39:58 +0200 Received: from atkin901 by mulder.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Mar 2004 17:39:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: othermark Date: Mon, 29 Mar 2004 07:39:52 -0800 Lines: 753 Message-ID: References: <20040323135932.L13222@carver.gumbysoft.com> <200403241430.29558.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="nextPart6004112.iZj3FCEBGW" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: mulder.f5.com User-Agent: KNode/0.7.6 Sender: news Subject: Re: puc(4) device not attaching issue in -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: Mon, 29 Mar 2004 15:40:01 -0000 --nextPart6004112.iZj3FCEBGW Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8Bit John Baldwin wrote: > On Tuesday 23 March 2004 05:58 pm, othermark wrote: >> Doug White wrote: >> > On Tue, 23 Mar 2004, othermark wrote: >> >> none0@pci0:6:1: class=0x070002 card=0x00000000 chip=0x01811407 >> >> rev=0x00 hdr=0x00 >> >> vendor = 'Lava Computer Manufacturing Inc' >> >> device = 'Lava Octopus PCI Ports 5-8' >> >> class = simple comms >> >> subclass = UART >> >> >> >> device 6.1 has chip 0x018111407=and pucdata.c has only has an entry >> >> for 0x0180, so I'm not sure how it was picking up 0x0181 in earlier >> >> releases, or that it still does and something else is blocking it >> >> from happening... >> > >> > What happens if you add that PCI ID to the driver? >> >> If I add a duplicate the entry in pucdata.c so it looks like this: >> >> >> /* Lava Computers Octopus-550 serial ports */ >> { "Lava Computers Octopus-550 8-port serial part B", >> NULL, >> { 0x1407, 0x0181, 0, 0 }, >> { 0xffff, 0xfffc, 0, 0 }, > > The 0xfffc is a mask meaning that this matches 0x0180, 0x0181, 0x0182, and > 0x0183 by the way, so you don't need an extra entry. Can you do a boot > -v? I'm curious if the second device has its BAR's setup. I've attached a verbose boot to this message. How do you tell if the BAR is setup or not? -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); --nextPart6004112.iZj3FCEBGW Content-Type: text/plain; name="puc.txt" Content-Transfer-Encoding: 8Bit Content-Disposition: attachment; filename="puc.txt" Copyright (c) 1992-2004 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.2-CURRENT #14: Tue Mar 23 14:17:06 PST 2004 root@adkinson245.f5net.com:/usr/obj/usr/src/sys/NEMO5 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a91000. Calibrating clock(s) ... i8254 clock: 1193090 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 930163681 Hz CPU: Intel Pentium III (930.16-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 1073741824 (1024 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c26000 - 0x000000003edcffff, 1041932288 bytes (254378 pages) avail memory = 1041215488 (992 MB) bios32: Found BIOS32 Service Directory header at 0xc00f73f0 bios32: Entry = 0xfd830 (c00fd830) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd830+0x18f pnpbios: Found PnP BIOS data at 0xc00f7420 pnpbios: Entry = f0000:a206 Rev = 1.0 Other BIOS signatures found: wlan: <802.11 Link Layer> null: random: mem: Pentium Pro MTRR support enabled cpu0 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x80007904 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00071166) pcibios: BIOS version 2.10 Found $PIR table, 12 entries at 0xc00fdf00 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs slot 15 1 0 A 0x12 3 4 5 6 7 10 11 12 slot 15 1 0 B 0x14 3 4 5 6 7 10 11 12 embedded 0 15 A 0x02 3 4 5 6 7 10 11 12 embedded 0 1 A 0x1e 3 4 5 6 7 10 11 12 embedded 0 1 B 0x1d 3 4 5 6 7 10 11 12 embedded 0 2 A 0x1f 3 4 5 6 7 10 11 12 embedded 0 7 A 0x18 3 4 5 6 7 10 11 12 slot 1 0 3 A 0x11 3 4 5 6 7 10 11 12 slot 1 0 3 B 0x12 3 4 5 6 7 10 11 12 slot 1 0 3 C 0x13 3 4 5 6 7 10 11 12 slot 1 0 3 D 0x14 3 4 5 6 7 10 11 12 slot 2 0 4 A 0x13 3 4 5 6 7 10 11 12 slot 2 0 4 B 0x14 3 4 5 6 7 10 11 12 slot 2 0 4 C 0x11 3 4 5 6 7 10 11 12 slot 2 0 4 D 0x12 3 4 5 6 7 10 11 12 slot 3 0 5 A 0x15 3 4 5 6 7 10 11 12 slot 3 0 5 B 0x16 3 4 5 6 7 10 11 12 slot 3 0 5 C 0x1d 3 4 5 6 7 10 11 12 slot 3 0 5 D 0x1e 3 4 5 6 7 10 11 12 slot 4 2 1 A 0x19 3 4 5 6 7 10 11 12 slot 4 2 1 B 0x1a 3 4 5 6 7 10 11 12 slot 4 2 1 C 0x1b 3 4 5 6 7 10 11 12 slot 4 2 1 D 0x1c 3 4 5 6 7 10 11 12 slot 5 2 2 A 0x1b 3 4 5 6 7 10 11 12 slot 5 2 2 B 0x1c 3 4 5 6 7 10 11 12 slot 5 2 2 C 0x19 3 4 5 6 7 10 11 12 slot 5 2 2 D 0x1a 3 4 5 6 7 10 11 12 slot 6 0 6 A 0x17 3 4 5 6 7 10 11 12 slot 6 0 6 B 0x18 3 4 5 6 7 10 11 12 slot 6 0 6 C 0x15 3 4 5 6 7 10 11 12 slot 6 0 6 D 0x16 3 4 5 6 7 10 11 12 pcib0: at pcibus 0 on motherboard $PIR: Links after initial probe: Link IRQ Ref IRQs 0x12 255 3 3 4 5 6 7 10 11 12 0x14 255 3 3 4 5 6 7 10 11 12 0x2 255 1 3 4 5 6 7 10 11 12 0x1e 255 2 3 4 5 6 7 10 11 12 0x1d 255 2 3 4 5 6 7 10 11 12 0x1f 255 1 3 4 5 6 7 10 11 12 0x18 255 2 3 4 5 6 7 10 11 12 0x11 255 2 3 4 5 6 7 10 11 12 0x13 255 2 3 4 5 6 7 10 11 12 0x15 255 2 3 4 5 6 7 10 11 12 0x16 255 2 3 4 5 6 7 10 11 12 0x19 255 2 3 4 5 6 7 10 11 12 0x1a 255 2 3 4 5 6 7 10 11 12 0x1b 255 2 3 4 5 6 7 10 11 12 0x1c 255 2 3 4 5 6 7 10 11 12 0x17 255 1 3 4 5 6 7 10 11 12 $PIR: Found matching pin for 1.0.INTA at func 0: 11 $PIR: Found matching pin for 0.15.INTA at func 2: 11 $PIR: Found matching pin for 0.2.INTA at func 0: 7 $PIR: Found matching pin for 0.7.INTA at func 0: 11 $PIR: Found matching pin for 0.3.INTA at func 0: 11 $PIR: Found matching pin for 0.4.INTA at func 0: 10 $PIR: Found matching pin for 0.5.INTA at func 0: 5 $PIR: Found matching pin for 0.6.INTA at func 0: 12 $PIR: Links after initial IRQ discovery: Link IRQ Ref IRQs 0x12 11 3 3 4 5 6 7 10 11 12 0x14 255 3 3 4 5 6 7 10 11 12 0x2 11 1 3 4 5 6 7 10 11 12 0x1e 255 2 3 4 5 6 7 10 11 12 0x1d 255 2 3 4 5 6 7 10 11 12 0x1f 7 1 3 4 5 6 7 10 11 12 0x18 11 2 3 4 5 6 7 10 11 12 0x11 11 2 3 4 5 6 7 10 11 12 0x13 10 2 3 4 5 6 7 10 11 12 0x15 5 2 3 4 5 6 7 10 11 12 0x16 255 2 3 4 5 6 7 10 11 12 0x19 255 2 3 4 5 6 7 10 11 12 0x1a 255 2 3 4 5 6 7 10 11 12 0x1b 255 2 3 4 5 6 7 10 11 12 0x1c 255 2 3 4 5 6 7 10 11 12 0x17 12 1 3 4 5 6 7 10 11 12 $PIR: IRQs used by BIOS: 5 7 10 11 12 $PIR: Interrupt Weights: [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ] [ 0 0 0 0 0 2 0 1 0 0 2 8 1 0 0 0 ] pci0: on pcib0 pci0: physical bus=0 map[10]: type 3, range 32, base fc000000, size 25, memory disabled map[14]: type 1, range 32, base feafb000, size 12, memory disabled found-> vendor=0x1166, dev=0x0007, revid=0x22 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0005, revid=0x01 bus=0, slot=0, func=1 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0007, statreg=0x22b0, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0006, revid=0x00 bus=0, slot=0, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0002, statreg=0xa200, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0006, revid=0x00 bus=0, slot=0, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0002, statreg=0x2200, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 4, range 32, base 0000f8c0, size 6, enabled $PIR: 0:2 INTA routed to irq 7 found-> vendor=0x1274, dev=0x1371, revid=0x08 bus=0, slot=2, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0410, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x0c (3000 ns), maxlat=0x80 (32000 ns) intpin=a, irq=7 powerspec 1 supports D0 D2 D3 current D0 map[10]: type 3, range 32, base fe3ff000, size 12, enabled map[14]: type 4, range 32, base 0000fca0, size 5, enabled map[18]: type 1, range 32, base fe600000, size 20, enabled $PIR: 0:3 INTA routed to irq 11 found-> vendor=0x8086, dev=0x1229, revid=0x04 bus=0, slot=3, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=11 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base feaf8000, size 12, enabled map[14]: type 4, range 32, base 0000fc00, size 6, enabled map[18]: type 1, range 32, base fe800000, size 20, enabled $PIR: 0:4 INTA routed to irq 10 found-> vendor=0x8086, dev=0x1229, revid=0x08 bus=0, slot=4, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000f8a8, size 3, enabled map[14]: type 4, range 32, base 0000f8b0, size 3, enabled map[18]: type 4, range 32, base 0000f8b8, size 3, enabled map[1c]: type 4, range 32, base 0000fc88, size 3, enabled $PIR: 0:5 INTA routed to irq 5 found-> vendor=0x1407, dev=0x0180, revid=0x00 bus=0, slot=5, func=0 class=07-00-02, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x0480, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[10]: type 4, range 32, base 0000f888, size 3, enabled map[14]: type 4, range 32, base 0000f890, size 3, enabled map[18]: type 4, range 32, base 0000f898, size 3, enabled map[1c]: type 4, range 32, base 0000f8a0, size 3, enabled $PIR: 0:5 INTA routed to irq 5 found-> vendor=0x1407, dev=0x0181, revid=0x00 bus=0, slot=5, func=1 class=07-00-02, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x0480, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[10]: type 1, range 32, base feaff000, size 12, enabled map[14]: type 4, range 32, base 0000fc40, size 6, enabled map[18]: type 1, range 32, base fe700000, size 20, enabled $PIR: 0:6 INTA routed to irq 12 found-> vendor=0x8086, dev=0x1229, revid=0x08 bus=0, slot=6, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=12 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base feaf9000, size 12, enabled map[14]: type 4, range 32, base 0000fcc0, size 6, enabled map[18]: type 1, range 32, base fe900000, size 20, enabled $PIR: 0:7 INTA routed to irq 11 found-> vendor=0x8086, dev=0x1229, revid=0x08 bus=0, slot=7, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[90]: type 4, range 32, base 00000500, size 4, enabled found-> vendor=0x1166, dev=0x0200, revid=0x4f bus=0, slot=15, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 0000fc90, size 4, enabled found-> vendor=0x1166, dev=0x0211, revid=0x00 bus=0, slot=15, func=1 class=01-01-8a, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 32, base feafe000, size 12, enabled $PIR: 0:15 INTA routed to irq 11 found-> vendor=0x1166, dev=0x0220, revid=0x04 bus=0, slot=15, func=2 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0017, statreg=0x0280, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x50 (20000 ns) intpin=a, irq=11 pcib1: at device 0.1 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xe000-0xefff pcib1: memory decode 0xfe500000-0xfe5fffff pcib1: prefetched decode 0xf0000000-0xf7ffffff pci1: on pcib1 pci1: physical bus=1 map[10]: type 3, range 32, base f0000000, size 27, enabled map[14]: type 4, range 32, base 0000e800, size 8, enabled map[18]: type 1, range 32, base fe5f0000, size 16, enabled $PIR: 1:0 INTA routed to irq 11 found-> vendor=0x1002, dev=0x5157, revid=0x00 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0287, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 pci1: at device 0.0 (no driver attached) pcm0: port 0xf8c0-0xf8ff irq 7 at device 2.0 on pci0 pcm0: pcm0: Codec features 18 bit DAC, 18 bit ADC, 5 bit master volume, SigmaTel 3D Enhancement pcm0: Primary codec extended features AMAP pcm0: sndbuf_setmap 2a3000, 1000; 0xc620f000 -> 2a3000 pcm0: sndbuf_setmap 285000, 1000; 0xc6211000 -> 285000 fxp0: port 0xfca0-0xfcbf mem 0xfe600000-0xfe6fffff,0xfe3ff000-0xfe3fffff irq 11 at device 3.0 on pci0 fxp0: using memory space register mapping fxp0: PCI IDs: 8086 1229 8086 0009 0004 fxp0: Dynamic Standby mode is disabled miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: bpf attached fxp0: Ethernet address: 00:a0:c9:8d:e9:51 fxp1: port 0xfc00-0xfc3f mem 0xfe800000-0xfe8fffff,0xfeaf8000-0xfeaf8fff irq 10 at device 4.0 on pci0 fxp1: using memory space register mapping fxp1: PCI IDs: 8086 1229 8086 000e 0008 fxp1: Dynamic Standby mode is disabled miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: bpf attached fxp1: Ethernet address: 00:d0:b7:6b:f5:92 puc0: port 0xfc88-0xfc8f,0xf8b8-0xf8bf,0xf8b0-0xf8b7,0xf8a8-0xf8af irq 5 at device 5.0 on pci0 sio4: on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode sio5: on puc0 sio5: type 16550A sio5: unable to activate interrupt in fast mode - using normal mode sio6: on puc0 sio6: type 16550A sio6: unable to activate interrupt in fast mode - using normal mode sio7: on puc0 sio7: type 16550A sio7: unable to activate interrupt in fast mode - using normal mode pci0: at device 5.1 (no driver attached) fxp2: port 0xfc40-0xfc7f mem 0xfe700000-0xfe7fffff,0xfeaff000-0xfeafffff irq 12 at device 6.0 on pci0 fxp2: using memory space register mapping fxp2: PCI IDs: 8086 1229 8086 000c 0008 fxp2: Dynamic Standby mode is disabled miibus2: on fxp2 inphy2: on miibus2 inphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp2: bpf attached fxp2: Ethernet address: 00:d0:b7:4c:b3:01 fxp3: port 0xfcc0-0xfcff mem 0xfe900000-0xfe9fffff,0xfeaf9000-0xfeaf9fff irq 11 at device 7.0 on pci0 fxp3: using memory space register mapping fxp3: PCI IDs: 8086 1229 8086 000c 0008 fxp3: Dynamic Standby mode is disabled miibus3: on fxp3 inphy3: on miibus3 inphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp3: bpf attached fxp3: Ethernet address: 00:e0:81:00:f6:bf isab0: port 0x500-0x50f at device 15.0 on pci0 isa0: on isab0 atapci0: port 0xfc90-0xfc9f at device 15.1 on pci0 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata0-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 mask=03 stat0=50 stat1=00 devices=0x1 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1-master: stat=0x00 err=0x01 lsb=0x14 msb=0xeb ata1-slave: stat=0x00 err=0x04 lsb=0x7f msb=0x7f ata1: reset tp2 mask=03 stat0=00 stat1=00 devices=0x4 ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ohci0: mem 0xfeafe000-0xfeafefff irq 11 at device 15.2 on pci0 ohci0: (New OHCI DeviceId=0x02201166) usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered uhub0: device problem, disabling port 2 pcib2: at pcibus 2 on motherboard pci2: on pcib2 pci2: physical bus=2 ex_isa_identify() ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff pnpbios: 18 devices, largest 178 bytes PNP0c02: adding io range 0x80-0x80, size=0x1, align=0x1 PNP0c02: adding io range 0xe0-0xe1, size=0x2, align=0x1 PNP0c02: adding fixed memory32 range 0xfff80000-0xffffffff, size=0x80000 pnpbios: handle 0 device ID PNP0c02 (020cd041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0xe8000-0xfffff, size=0x18000 PNP0c01: adding fixed memory32 range 0x100000-0x3fffffff, size=0x3ff00000 pnpbios: handle 1 device ID PNP0c01 (010cd041) PNP0200: adding io range 0-0xf, size=0x10, align=0x1 PNP0200: adding io range 0x81-0x8f, size=0xf, align=0x1 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 PNP0200: adding dma mask 0x10 pnpbios: handle 2 device ID PNP0200 (0002d041) PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 PNP0100: adding irq mask 0x1 pnpbios: handle 4 device ID PNP0100 (0001d041) PNP0b00: adding io range 0x70-0x71, size=0x2, align=0x1 PNP0b00: adding irq mask 0x100 pnpbios: handle 5 device ID PNP0b00 (000bd041) PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 PNP0303: adding irq mask 0x2 pnpbios: handle 6 device ID PNP0303 (0303d041) PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: adding irq mask 0x2000 pnpbios: handle 7 device ID PNP0c04 (040cd041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 pnpbios: handle 8 device ID PNP0800 (0008d041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 pnpbios: handle 9 device ID PNP0a03 (030ad041) PNP0c02: adding io range 0x510-0x513, size=0x4, align=0x1 PNP0c02: adding io range 0x514-0x515, size=0x2, align=0x1 PNP0c02: adding io range 0x518-0x51b, size=0x4, align=0x1 PNP0c02: adding io range 0x520-0x521, size=0x2, align=0x1 PNP0c02: adding io range 0x524-0x529, size=0x6, align=0x1 PNP0c02: adding io range 0x538-0x53f, size=0x8, align=0x1 PNP0c02: adding io range 0x530-0x530, size=0x1, align=0x1 PNP0c02: adding io range 0x500-0x50d, size=0xe, align=0x1 PNP0c02: adding io range 0x40b-0x40b, size=0x1, align=0x1 PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0c02: adding io range 0x4d6-0x4d6, size=0x1, align=0x1 PNP0c02: adding io range 0xc00-0xc01, size=0x2, align=0x1 PNP0c02: adding io range 0xc06-0xc08, size=0x3, align=0x1 PNP0c02: adding io range 0xc14-0xc14, size=0x1, align=0x1 PNP0c02: adding io range 0xc49-0xc4a, size=0x2, align=0x1 PNP0c02: adding io range 0xc50-0xc52, size=0x3, align=0x1 PNP0c02: adding io range 0xc6c-0xc6c, size=0x1, align=0x1 PNP0c02: adding io range 0xc6f-0xc6f, size=0x1, align=0x1 PNP0c02: adding io range 0xcd6-0xcd7, size=0x2, align=0x1 PNP0c02: adding io range 0xf50-0xf58, size=0x9, align=0x1 pnpbios: handle 10 device ID PNP0c02 (020cd041) PNP0c02: adding fixed memory32 range 0xfec00000-0xfec0ffff, size=0x10000 PNP0c02: adding fixed memory32 range 0xfee00000-0xfee00fff, size=0x1000 pnpbios: handle 11 device ID PNP0c02 (020cd041) PNP0c02: adding io range 0x540-0x55f, size=0x20, align=0x1 pnpbios: handle 12 device ID PNP0c02 (020cd041) PNP0c02: adding fixed memory32 range 0xce800-0xcffff, size=0x1800 pnpbios: handle 13 device ID PNP0c02 (020cd041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 PNP0501: adding irq mask 0x10 pnpbios: handle 15 device ID PNP0501 (0105d041) PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0x8 PNP0501: adding irq mask 0x8 pnpbios: handle 16 device ID PNP0501 (0105d041) PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x8 PNP0700: adding io range 0x3f7-0x3f7, size=0x1, align=0x1 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 pnpbios: handle 17 device ID PNP0700 (0007d041) pnpbios: handle 19 device ID PNP0400 (0004d041) sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: