From owner-freebsd-current  Sun Dec 31  1: 2:25 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 01:02:21 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5569837B400; Sun, 31 Dec 2000 01:02:20 -0800 (PST)
Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92])
	by tasogare.imasy.or.jp (8.11.1+3.4W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id eBV92Hk18135;
	Sun, 31 Dec 2000 18:02:17 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
To: current@freebsd.org
Cc: hackers@freebsd.org
Subject: CFR: Generalized power-management interface
X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20001231180216L.iwasaki@jp.FreeBSD.org>
Date: Sun, 31 Dec 2000 18:02:16 +0900
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 41
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I've created new common framework on generalized power-management
interface for userland utilities.

http://people.freebsd.org/~iwasaki/acpi/power-20001229.tar.gz

This provides some PM APIs to APM applications, such as wmapm, so that
these applications can be ported smoothly to use ACPI (power
management portion).  Currently following APIs are implemented;

int	 power_get_syspm_info(struct power_syspm_info *);
int	 power_get_batt_info(u_int, struct power_batt_info *);
int	 power_standby(void);
int	 power_suspend(void);
int	 power_hibernate(void);

And PM event notification mechanism is suggested to be implemented so far.

Sample application is included in usr.sbin/power/ which is very similar
to apm(8) but supports ACPI as well.

usr.sbin/acpi/acpibatt/ is for displaying acpi_cmbat (ACPI Control
Method Battery), can be used to verify that generalized
power-management interface is working correctly.
Note that many ACPI BIOS give us unknown battery remaining time when
ac-line is plugged in.  MIB 'hw.battery.full_charge_time' can be used to
specify the full charged remaining time of batteries in minutes, like
	sysctl -w hw.battery.full_charge_time=60,60
for multiple number of batteries, or
	sysctl -w hw.battery.full_charge_time=120
for a battery installed.

To test them, /dev/power is required as a device control file.

% ls -l /dev/power
crw-r--r--  1 root  wheel  210,   0  12/19 04:51 /dev/power

I'll commit them at sometime early in coming century.

Any comments would be appreciated.  Thanks!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31  1:37:47 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 01:37:45 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ns.internet.dk (ns.internet.dk [194.19.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id 7C1E437B400
	for <freebsd-current@FreeBSD.ORG>; Sun, 31 Dec 2000 01:37:44 -0800 (PST)
Received: (from uucp@localhost)
	by ns.internet.dk (8.11.1/8.11.1) with UUCP id eBV9bgI06716;
	Sun, 31 Dec 2000 10:37:42 +0100 (CET)
	(envelope-from leifn@neland.dk)
Received: from gina (gina.neland.dk [192.168.0.14])
	by arnold.neland.dk (8.11.0/8.11.0) with SMTP id eBV9bVs07809;
	Sun, 31 Dec 2000 10:37:36 +0100 (CET)
	(envelope-from leifn@neland.dk)
Message-ID: <001901c0730d$5204f6c0$0e00a8c0@neland.dk>
Reply-To: "Leif Neland" <leif@neland.dk>
From: "Leif Neland" <leifn@neland.dk>
To: "Gerhard Sittig" <Gerhard.Sittig@gmx.net>,
	<freebsd-current@FreeBSD.ORG>
References: <001f01c07286$9a055a00$0e00a8c0@neland.dk> <20001230215241.M253@speedy.gsinet>
Subject: Re: IGMP queries
Date: Sun, 31 Dec 2000 10:37:00 +0100
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

From: "Gerhard Sittig" <Gerhard.Sittig@gmx.net>
To: <freebsd-current@FreeBSD.ORG>
Sent: Saturday, December 30, 2000 9:52 PM

> On Sat, Dec 30, 2000 at 18:32 +0100, Leif Neland wrote:
> >
> > My isp's router is sending me IGMP queries.
> >
> > 18:25:07.850008 212.242.151.2 > 224.0.0.1: 212.242.151.2 >
> > 224.0.0.1: igmp v2 query [intvl 10]igmp query [ttl 1]
>
> Ask your provider to not do it. :)  Do you run any multicast
> enabled applications, anyhow?  If not, all of the 224.0.0.0/4
> stuff is not needed ...
>
> > I think it keeps my user-ppp connection open, even if I have
> > this rule in my firewall:
> > $fwcmd add 65432 deny ip from 212.242.151.2 to any
> >
> > If it is true, how can I filter it to stop resetting the
> > idle-timeout?
>
> If you use ppp(8) -- you don't state what your uplink looks like,
> whether it's an analog modem / ISDN / DSL / plain ethernet /
> whatever -- there are four filter lists:  those packets allowed
> to pass in, those to pass out, those to trigger dialing and those
> to keep the session alive.  All the lists can be positive or
> negativ, but are somewhat limited in their length and
> flexibility.  Maybe this feature will help you, although all of
> the above is what I got from reading "man 8 ppp" and not from
> personal experience. :(
>

I use isdn4bsd.

rtfm:
I'll try if "set filter alive 0 deny igmp" does not help.

Tnx





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31  8:55:34 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 08:55:32 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail.eqpankkiiriliike.fi (fw.eQpankkiiriliike.fi [212.226.216.93])
	by hub.freebsd.org (Postfix) with ESMTP id 9C2D137B400
	for <freebsd-current@freebsd.org>; Sun, 31 Dec 2000 08:55:31 -0800 (PST)
Received: from eqonline.fi ([10.11.0.244]) by
          mail.eqpankkiiriliike.fi (Netscape Messaging Server 4.15) with
          ESMTP id G6FYZ200.612 for <freebsd-current@freebsd.org>; Sun, 31
          Dec 2000 18:54:38 +0200 
Sender: sja@FreeBSD.ORG
Message-ID: <3A4F650D.3212A5C5@eqonline.fi>
Date: Sun, 31 Dec 2000 18:55:41 +0200
From: User Sja <sakari.jalovaara@eqonline.fi>
Organization: eQ Online
X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Subject: PROCTREE_LOCK() vs. gdb hang
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I don't really know my way around the kernel so I'm just guessing here:

Is there a proctree lock release operation missing in kern_sig.c,
function issignal()?  There seems to be one lock operation more
than there are release operations.  I tried putting one in and
now gdb doesn't hang the whole machine (at least as easily as
before.)


#kern (sja@tilli) 112> cvs diff -u kern_sig.c
Index: kern_sig.c
===================================================================
RCS file: /usr/cvs/src/sys/kern/kern_sig.c,v
retrieving revision 1.98
diff -u -r1.98 kern_sig.c
--- kern_sig.c  2000/12/23 19:43:09     1.98
+++ kern_sig.c  2000/12/31 16:01:45
@@ -1311,6 +1311,7 @@
                                PROCTREE_LOCK(PT_SHARED);
                        } while (!trace_req(p)
                                 && p->p_flag & P_TRACED);
+                       PROCTREE_LOCK(PT_RELEASE);
 
                        /*
                         * If the traced bit got turned off, go back up


++sja


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31  9:12: 9 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 09:12:04 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 8899937B400; Sun, 31 Dec 2000 09:12:04 -0800 (PST)
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id C9FB76E26FD; Sun, 31 Dec 2000 09:12:03 -0800 (PST)
Received: from neserve0.corp.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: neserve0.corp.us.uu.net [153.39.92.148])
	id QQjvyy03730;
	Sun, 31 Dec 2000 17:11:47 GMT
Received: from localhost by neserve0.corp.us.uu.net with ESMTP 
	(peer crosschecked as: rayhicks@localhost)
	id QQjvyy09895;
	Sun, 31 Dec 2000 12:11:46 -0500 (EST)
Date: Sun, 31 Dec 2000 12:11:46 -0500 (EST)
From: Raymond Hicks <rayhicks@UU.NET>
X-Sender: rayhicks@neserve0.corp.us.uu.net
To: questions@freebsd.org
Cc: current@freebsd.org
Subject: make buildworld fails after cvsup
Message-ID: <Pine.GSO.4.20.0012311210150.6955-100000@neserve0.corp.us.uu.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I am cvsup to current last night and this morning the make buildworld
giving following errors..  anyone have similar or know what this is?

uudecode < /usr/src/share/tabset/xerox1720.uu
uudecode < /usr/src/share/tabset/xerox1730.uu
uudecode < /usr/src/share/tabset/xerox1730-lm.uu
uudecode < /usr/src/share/tabset/zenith29.uu
===> share/termcap
ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder >
/dev/null
Segmentation fault - core dumped
*** Error code 139

Stop in /usr/src/share/termcap.
*** Error code 1

Stop in /usr/src/share.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Thanks
raymond hicks



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31  9:47:19 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 09:47:16 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
	by hub.freebsd.org (Postfix) with ESMTP id 79C3C37B400
	for <freebsd-current@FreeBSD.ORG>; Sun, 31 Dec 2000 09:47:15 -0800 (PST)
Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1])
	by whizzo.transsys.com (8.11.1/8.11.0) with ESMTP id eBVAnBr23486;
	Sun, 31 Dec 2000 05:49:12 -0500 (EST)
	(envelope-from louie@whizzo.transsys.com)
Message-Id: <200012311049.eBVAnBr23486@whizzo.transsys.com>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: Gerhard Sittig <Gerhard.Sittig@gmx.net>
Cc: freebsd-current@FreeBSD.ORG
X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: IGMP queries 
References: <001f01c07286$9a055a00$0e00a8c0@neland.dk> <20001230215241.M253@speedy.gsinet> 
In-reply-to: Your message of "Sat, 30 Dec 2000 21:52:41 +0100."
             <20001230215241.M253@speedy.gsinet> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 31 Dec 2000 05:49:11 -0500
Sender: louie@TransSys.COM
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> 
> > Btw, can I use IGMP to something useful/interesting/funny?
> 
> AFAIK it's some kind of dynamic route establishment (learning
> about topology by listening to what your neighbour knows about
> the network).  Home users and small LANs won't need it IMHO,
> maybe WAN links will benefit?  But I'm definitely not keen on
> having "the world" tell me where to send my packets to.  I just
> hand the traffic to my provider's dialin port. :>

IGMP is the protocol used between a multicast router, and end-hosts on
a subnetwork; much like ICMP is used between a router and an end-host
to help manage unicast traffic.

So, when your hosts joins a multicast group, it sends (to a multicast group)
an IGMP message announcing this.  This is supposed to cause a multicast
router on the subnetwork to begin forwarding the traffic onto the
subnet.  The multicast router will also periodically send IGMP
group membership queries onto the subnetwork to see if there are
any hosts still interested/subscribed to a group.  If it gets no replies
after a while, it will stop forwarding unsubscribed groups onto
that subnetwork.

So that's why you're seeing IGMP queries; the multicast router is
trying to see if you've joined any multicast groups so it can
try to send you traffic.  It's got nothing to do with "having the
world tell you where to send your packets to."

louie


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31  9:56:14 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 09:56:12 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail.eqpankkiiriliike.fi (fw.eQpankkiiriliike.fi [212.226.216.93])
	by hub.freebsd.org (Postfix) with ESMTP id 69D8837B400
	for <current@freebsd.org>; Sun, 31 Dec 2000 09:56:11 -0800 (PST)
Received: from eqonline.fi ([10.11.0.244]) by
          mail.eqpankkiiriliike.fi (Netscape Messaging Server 4.15) with
          ESMTP id G6G1S800.E15 for <current@freebsd.org>; Sun, 31 Dec
          2000 19:55:20 +0200 
Sender: sja@FreeBSD.ORG
Message-ID: <3A4F7346.97C47D59@eqonline.fi>
Date: Sun, 31 Dec 2000 19:56:22 +0200
From: User Sja <sakari.jalovaara@eqonline.fi>
Organization: eQ Online
X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: current@freebsd.org
Subject: Re: make buildworld fails after cvsup
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I am cvsup to current last night and this morning the make buildworld
> giving following errors..  anyone have similar or know what this is?
>
> uudecode < /usr/src/share/tabset/xerox1720.uu
> uudecode < /usr/src/share/tabset/xerox1730.uu
> uudecode < /usr/src/share/tabset/xerox1730-lm.uu
> uudecode < /usr/src/share/tabset/zenith29.uu
> ===> share/termcap
> ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > /dev/null
> Segmentation fault - core dumped

Hmm, ex is crashing...  Does "vi" also core dump on you?

There may be a bit of fallout from the recent removal
of "CIRCLEQ"s (see /usr/include/sys/queue.h).

How does this patch look to everyone:

RCS file: /usr/cvs/src/lib/libc/db/mpool/mpool.c,v
retrieving revision 1.6
diff -u -r1.6 mpool.c
--- src/lib/libc/db/mpool/mpool.c       2000/12/29 20:24:58     1.6
+++ src/lib/libc/db/mpool/mpool.c       2000/12/31 17:46:35
@@ -271,7 +271,7 @@
        BKT *bp;
 
        /* Free up any space allocated to the lru pages. */
-       while ((bp = TAILQ_FIRST(&mp->lqh)) != (void *)&mp->lqh) {
+       while ((bp = TAILQ_FIRST(&mp->lqh)) != NULL) {
                TAILQ_REMOVE(&mp->lqh, bp, q);
                free(bp);
        }


++sja


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 10: 2:44 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 10:02:40 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by hub.freebsd.org (Postfix) with ESMTP id 9F71F37B698
	for <current@freebsd.org>; Sun, 31 Dec 2000 10:02:37 -0800 (PST)
Received: from neserve0.corp.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: neserve0.corp.us.uu.net [153.39.92.148])
	id QQjvzc19504;
	Sun, 31 Dec 2000 18:02:36 GMT
Received: from localhost by neserve0.corp.us.uu.net with ESMTP 
	(peer crosschecked as: rayhicks@localhost)
	id QQjvzc16115;
	Sun, 31 Dec 2000 13:02:35 -0500 (EST)
Date: Sun, 31 Dec 2000 13:02:35 -0500 (EST)
From: Raymond Hicks <rayhicks@UU.NET>
X-Sender: rayhicks@neserve0.corp.us.uu.net
To: User Sja <sakari.jalovaara@eqonline.fi>
Cc: current@freebsd.org
Subject: Re: make buildworld fails after cvsup
In-Reply-To: <3A4F7346.97C47D59@eqonline.fi>
Message-ID: <Pine.GSO.4.20.0012311259570.15800-100000@neserve0.corp.us.uu.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

nothing else happens...  I mean after running buildworld or I should say
during i get this error and if I run it again it does the same
thing..  back at command line i can still do whatever ..  everything else
seems unharmed although uname -a still say 4.2 becaue could not complete
cvsup to current..  any ideas how to get around this?  what will queue.h
do for me?

lates
raymond hicks

On Sun, 31 Dec 2000, User Sja wrote:

> > I am cvsup to current last night and this morning the make buildworld
> > giving following errors..  anyone have similar or know what this is?
> >
> > uudecode < /usr/src/share/tabset/xerox1720.uu
> > uudecode < /usr/src/share/tabset/xerox1730.uu
> > uudecode < /usr/src/share/tabset/xerox1730-lm.uu
> > uudecode < /usr/src/share/tabset/zenith29.uu
> > ===> share/termcap
> > ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > /dev/null
> > Segmentation fault - core dumped
> 
> Hmm, ex is crashing...  Does "vi" also core dump on you?
> 
> There may be a bit of fallout from the recent removal
> of "CIRCLEQ"s (see /usr/include/sys/queue.h).
> 
> How does this patch look to everyone:
> 
> RCS file: /usr/cvs/src/lib/libc/db/mpool/mpool.c,v
> retrieving revision 1.6
> diff -u -r1.6 mpool.c
> --- src/lib/libc/db/mpool/mpool.c       2000/12/29 20:24:58     1.6
> +++ src/lib/libc/db/mpool/mpool.c       2000/12/31 17:46:35
> @@ -271,7 +271,7 @@
>         BKT *bp;
>  
>         /* Free up any space allocated to the lru pages. */
> -       while ((bp = TAILQ_FIRST(&mp->lqh)) != (void *)&mp->lqh) {
> +       while ((bp = TAILQ_FIRST(&mp->lqh)) != NULL) {
>                 TAILQ_REMOVE(&mp->lqh, bp, q);
>                 free(bp);
>         }
> 
> 
> ++sja
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 10: 3:54 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 10:03:53 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40])
	by hub.freebsd.org (Postfix) with ESMTP id C441837B402
	for <current@freebsd.org>; Sun, 31 Dec 2000 10:03:50 -0800 (PST)
Received: by peitho.fxp.org (Postfix, from userid 1501)
	id 814FA13614; Sun, 31 Dec 2000 13:03:12 -0500 (EST)
Date: Sun, 31 Dec 2000 13:03:12 -0500
From: Chris Faulhaber <jedgar@fxp.org>
To: User Sja <sakari.jalovaara@eqonline.fi>
Cc: current@freebsd.org
Subject: Re: make buildworld fails after cvsup
Message-ID: <20001231130312.A21898@peitho.fxp.org>
References: <3A4F7346.97C47D59@eqonline.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3A4F7346.97C47D59@eqonline.fi>; from sakari.jalovaara@eqonline.fi on Sun, Dec 31, 2000 at 07:56:22PM +0200
Sender: cdf.lists@fxp.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Dec 31, 2000 at 07:56:22PM +0200, User Sja wrote:
> > I am cvsup to current last night and this morning the make buildworld
> > giving following errors..  anyone have similar or know what this is?
> >
> > uudecode < /usr/src/share/tabset/xerox1720.uu
> > uudecode < /usr/src/share/tabset/xerox1730.uu
> > uudecode < /usr/src/share/tabset/xerox1730-lm.uu
> > uudecode < /usr/src/share/tabset/zenith29.uu
> > ===> share/termcap
> > ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > /dev/null
> > Segmentation fault - core dumped
> 
> Hmm, ex is crashing...  Does "vi" also core dump on you?
> 
> There may be a bit of fallout from the recent removal
> of "CIRCLEQ"s (see /usr/include/sys/queue.h).
> 
> How does this patch look to everyone:
> 
> RCS file: /usr/cvs/src/lib/libc/db/mpool/mpool.c,v
> retrieving revision 1.6
> diff -u -r1.6 mpool.c

green already committed that fix yesterday.  Does this still happen when
building with rev. 1.7 ?

-- 
Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org
--------------------------------------------------------
FreeBSD: The Power To Serve   -   http://www.FreeBSD.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 10: 9:51 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 10:09:49 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail.eqpankkiiriliike.fi (fw.eQpankkiiriliike.fi [212.226.216.93])
	by hub.freebsd.org (Postfix) with ESMTP id 69AB937B400
	for <current@freebsd.org>; Sun, 31 Dec 2000 10:09:48 -0800 (PST)
Received: from eqonline.fi ([10.11.0.244]) by
          mail.eqpankkiiriliike.fi (Netscape Messaging Server 4.15) with
          ESMTP id G6G2EX00.G0Y for <current@freebsd.org>; Sun, 31 Dec
          2000 20:08:57 +0200 
Sender: sja@FreeBSD.ORG
Message-ID: <3A4F7674.7EF61BCE@eqonline.fi>
Date: Sun, 31 Dec 2000 20:09:56 +0200
From: Sakari Jalovaara <sakari.jalovaara@eqonline.fi>
Organization: eQ Online
X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: current@freebsd.org
Subject: Re: make buildworld fails after cvsup
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I wrote:
> [CIRCLEQs and ex / vi crashing]

Scratch that, Brian Feldman already fixed it.

Re-sup and compile.

++sja


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 11:42: 7 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 11:42:05 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from volatile.chemikals.org (ci391991-a.grnvle1.sc.home.com [24.9.31.75])
	by hub.freebsd.org (Postfix) with ESMTP id ED7E337B400
	for <freebsd-current@FreeBSD.ORG>; Sun, 31 Dec 2000 11:42:04 -0800 (PST)
Received: (from morganw@localhost)
	by volatile.chemikals.org (8.11.1/8.11.1) id eBVJfww90138;
	Sun, 31 Dec 2000 14:41:58 -0500 (EST)
	(envelope-from morganw)
Date: Sun, 31 Dec 2000 14:41:58 -0500 (EST)
From: Wesley Morgan <morganw@chemikals.org>
To: User Sja <sakari.jalovaara@eqonline.fi>
Cc: <freebsd-current@FreeBSD.ORG>
Subject: Re: PROCTREE_LOCK() vs. gdb hang
In-Reply-To: <3A4F650D.3212A5C5@eqonline.fi>
Message-ID: <Pine.BSF.4.31.0012311440570.90127-100000@volatile.chemikals.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, 31 Dec 2000, User Sja wrote:

> I don't really know my way around the kernel so I'm just guessing here:
>
> Is there a proctree lock release operation missing in kern_sig.c,
> function issignal()?  There seems to be one lock operation more
> than there are release operations.  I tried putting one in and
> now gdb doesn't hang the whole machine (at least as easily as
> before.)

I don't know anything about the kernel either, but I locked up in gdb the
other day and every process eventually became stuck in proctree... Just my
$0.02US

-- 
                                           _ __ ___ ____  ___ ___ ___
          Wesley N Morgan                       _ __ ___ | _ ) __|   \
          morganw@chemikals.org                     _ __ | _ \._ \ |) |
          FreeBSD: The Power To Serve                  _ |___/___/___/
          6bone: 3ffe:1ce3:7::b4ff:fe53:c297
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 12:24:34 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 12:24:32 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from green.dyndns.org (localhost [127.0.0.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 746C237B400; Sun, 31 Dec 2000 12:24:30 -0800 (PST)
Received: from localhost (7jkmw6@localhost [127.0.0.1])
	by green.dyndns.org (8.11.1/8.11.1) with ESMTP id eBVKOOu12964;
	Sun, 31 Dec 2000 15:24:27 -0500 (EST)
	(envelope-from green@FreeBSD.org)
Message-Id: <200012312024.eBVKOOu12964@green.dyndns.org>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: User Sja <sakari.jalovaara@eqonline.fi>
Cc: freebsd-current@FreeBSD.org, ps@FreeBSD.org
Subject: Re: PROCTREE_LOCK() vs. gdb hang 
In-Reply-To: Message from User Sja <sakari.jalovaara@eqonline.fi> 
   of "Sun, 31 Dec 2000 18:55:41 +0200." <3A4F650D.3212A5C5@eqonline.fi> 
From: "Brian F. Feldman" <green@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 31 Dec 2000 15:24:24 -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

User Sja <sakari.jalovaara@eqonline.fi> wrote:
> I don't really know my way around the kernel so I'm just guessing here:
> 
> Is there a proctree lock release operation missing in kern_sig.c,
> function issignal()?  There seems to be one lock operation more
> than there are release operations.  I tried putting one in and
> now gdb doesn't hang the whole machine (at least as easily as
> before.)

I think you've really found the problem!  Your analysis and fix seems to be 
correct, and it wouldn't affect "normal" operations, only those when a 
process is being traced.  I'll test it out right now to make sure it works, 
and Paul can commit it if he also thinks it is correct.

> #kern (sja@tilli) 112> cvs diff -u kern_sig.c
> Index: kern_sig.c
> ===================================================================
> RCS file: /usr/cvs/src/sys/kern/kern_sig.c,v
> retrieving revision 1.98
> diff -u -r1.98 kern_sig.c
> --- kern_sig.c  2000/12/23 19:43:09     1.98
> +++ kern_sig.c  2000/12/31 16:01:45
> @@ -1311,6 +1311,7 @@
>                                 PROCTREE_LOCK(PT_SHARED);
>                         } while (!trace_req(p)
>                                  && p->p_flag & P_TRACED);
> +                       PROCTREE_LOCK(PT_RELEASE);
>  
>                         /*
>                          * If the traced bit got turned off, go back up
> 
> 
> ++sja



-- 
 Brian Fundakowski Feldman           \  FreeBSD: The Power to Serve!  /
 green@FreeBSD.org                    `------------------------------'




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 12:53:52 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 12:53:50 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from jbloom.jbloom.org (reyim.ne.mediaone.net [24.218.251.241])
	by hub.freebsd.org (Postfix) with ESMTP id EEB9937B400
	for <current@freebsd.org>; Sun, 31 Dec 2000 12:53:49 -0800 (PST)
Received: from acm.org (localhost [127.0.0.1])
	by jbloom.jbloom.org (8.11.1/8.11.1) with ESMTP id eBVKmr914798;
	Sun, 31 Dec 2000 15:48:53 -0500 (EST)
	(envelope-from bloom@acm.org)
Sender: bloom@jbloom.jbloom.org
Message-ID: <3A4F9BB5.F699D66B@acm.org>
Date: Sun, 31 Dec 2000 15:48:53 -0500
From: Jim Bloom <bloom@acm.org>
Reply-To: bloom@acm.org
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Poul-Henning Kamp <phk@critter.freebsd.dk>, current@freebsd.org
Subject: Problem building md module
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

While trying to build a new kernel today, I received errors relating to
vnode_if.h not existing.  I have put the patch below which fixed the
problem for me.  (Sorry if the patch does not apply because of cut and
paste errors, but it may easily be hand editted.)

Jim Bloom
bloom@acm.org


Index: Makefile
===================================================================
RCS file: /users/ncvs/src/sys/modules/md/Makefile,v
retrieving revision 1.7
diff -u -r1.7 Makefile
--- Makefile    2000/09/02 19:17:10     1.7
+++ Makefile    2000/12/31 18:35:36
@@ -2,7 +2,7 @@
 
 .PATH: ${.CURDIR}/../../dev/md
 KMOD=  md
-SRCS=  md.c opt_mfs.h opt_md.h
+SRCS=  md.c opt_mfs.h opt_md.h vnode_if.h
 NOMAN=
 
 .include <bsd.kmod.mk>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 14:53: 9 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 14:53:08 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by hub.freebsd.org (Postfix) with ESMTP id E43FF37B404
	for <current@freebsd.org>; Sun, 31 Dec 2000 14:53:07 -0800 (PST)
Received: from neserve0.corp.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: neserve0.corp.us.uu.net [153.39.92.148])
	id QQjvzv12553
	for <current@freebsd.org>; Sun, 31 Dec 2000 22:53:07 GMT
Received: from localhost by neserve0.corp.us.uu.net with ESMTP 
	(peer crosschecked as: rayhicks@localhost)
	id QQjvzv03709
	for <current@freebsd.org>; Sun, 31 Dec 2000 17:53:05 -0500 (EST)
Date: Sun, 31 Dec 2000 17:53:05 -0500 (EST)
From: Raymond Hicks <rayhicks@UU.NET>
X-Sender: rayhicks@neserve0.corp.us.uu.net
To: current@freebsd.org
Subject: continued problems with cvsup and buildworld to current
Message-ID: <Pine.GSO.4.20.0012311749290.3555-100000@neserve0.corp.us.uu.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Here is the deal,  I am cvsup remotely and my connection got killed so I
firstly do not know the status of the buildworld and when I type ps -aux i
get ps: kinfo_proc size mismatch (expected 640, got 0)
from there i try killall -9 buildworld and i get proc size mismatch (51744
total, 640 chunks)
userland out of sync with kernel, recompile libkvm etc...  should i just
start over again?  dmesg gives this but I got core dump from cvsup
builworld yesterday so could be from that...  
id 12668 (ex), uid 0: exited on signal 11 (core dumped)
pid 60670 (ex), uid 0: exited on signal 11 (core dumped)
pid 8937 (ex), uid 0: exited on signal 11 (core dumped)
...
 any help is appreciated here..
lates
raymond hicks



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 17: 2:47 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 17:02:45 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222])
	by hub.freebsd.org (Postfix) with ESMTP id 2EF7937B402
	for <freebsd-current@FreeBSD.ORG>; Sun, 31 Dec 2000 17:02:45 -0800 (PST)
Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137])
	by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0112Oh39355;
	Sun, 31 Dec 2000 17:02:24 -0800 (PST)
	(envelope-from jhb@foo.osd.bsdi.com)
Received: (from jhb@localhost)
	by foo.osd.bsdi.com (8.11.1/8.11.0) id f0112ik22008;
	Sun, 31 Dec 2000 17:02:44 -0800 (PST)
	(envelope-from jhb)
Message-ID: <XFMail.001231170244.jhb@FreeBSD.org>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20001230165252.A28872@elvis.mu.org>
Date: Sun, 31 Dec 2000 17:02:44 -0800 (PST)
Organization: BSD, Inc.
From: John Baldwin <jhb@FreeBSD.ORG>
To: Paul Saab <paul@mu.org>
Subject: Re: cvs commit: src/sys/kern sys_process.c
Cc: Szilveszter Adam <sziszi@petra.hos.u-szeged.hu>,
	freebsd-current@FreeBSD.ORG
Sender: jhb@foo.osd.bsdi.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 31-Dec-00 Paul Saab wrote:
> I already have and that fixed it.

Well, try http://www.FreeBSD.org/~jhb/patches/kern_sig.patch and see if that
helps.  I fubar'd some of the sched_lock handling in the signal code.  If that
works, try putting the proctree lock back in and see if it still hangs.
 
> John Baldwin (jhb@FreeBSD.ORG) wrote:
>> 
>> On 30-Dec-00 Paul Saab wrote:
>> > This will not fix the problem.  I even removed rev 1.57-1.58 and it
>> > still causes gdb to lockup the system.
>> 
>> Try backing out the proctree lock.
>> 
>> -- 
>> 
>> John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
>> PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
>> "Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
> 
> -- 
> Paul Saab
> Technical Yahoo
> paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org
> Do You .. uhh .. Yahoo!?

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 17:24:25 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 17:24:23 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by hub.freebsd.org (Postfix) with ESMTP id 3B3CB37B400
	for <current@freebsd.org>; Sun, 31 Dec 2000 17:24:23 -0800 (PST)
Received: from neserve0.corp.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: neserve0.corp.us.uu.net [153.39.92.148])
	id QQjwaf00133
	for <current@freebsd.org>; Mon, 1 Jan 2001 01:24:22 GMT
Received: from localhost by neserve0.corp.us.uu.net with ESMTP 
	(peer crosschecked as: rayhicks@localhost)
	id QQjwaf15174
	for <current@freebsd.org>; Sun, 31 Dec 2000 20:24:21 -0500 (EST)
Date: Sun, 31 Dec 2000 20:24:21 -0500 (EST)
From: Raymond Hicks <rayhicks@UU.NET>
X-Sender: rayhicks@neserve0.corp.us.uu.net
To: current@freebsd.org
Subject: buildworld still failing when going current
Message-ID: <Pine.GSO.4.20.0012312021550.3555-100000@neserve0.corp.us.uu.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have had this problem since yesterday...  I cvsup using the supfile on
handbook for going current...  i remove all from /usr/obj...  I cd
/usr/src and make buildworld and I get the following errors..  I am
running 4.2 STABLE.. please lend a hand...

uudecode < /usr/src/share/tabset/xerox1720.uu
uudecode < /usr/src/share/tabset/xerox1730.uu
uudecode < /usr/src/share/tabset/xerox1730-lm.uu
uudecode < /usr/src/share/tabset/zenith29.uu
===> share/termcap
ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder >
/dev/null
Segmentation fault - core dumped
*** Error code 139

Stop in /usr/src/share/termcap.
*** Error code 1

Stop in /usr/src/share.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
thanks 
raymond hicks



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 17:53:43 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 17:53:41 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222])
	by hub.freebsd.org (Postfix) with ESMTP id 1DBB237B400
	for <current@FreeBSD.ORG>; Sun, 31 Dec 2000 17:53:41 -0800 (PST)
Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137])
	by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f011rKh40034;
	Sun, 31 Dec 2000 17:53:20 -0800 (PST)
	(envelope-from jhb@foo.osd.bsdi.com)
Received: (from jhb@localhost)
	by foo.osd.bsdi.com (8.11.1/8.11.0) id f011reT22357;
	Sun, 31 Dec 2000 17:53:40 -0800 (PST)
	(envelope-from jhb)
Message-ID: <XFMail.001231175340.jhb@FreeBSD.org>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <200012302342.eBUNgW142476@earth.backplane.com>
Date: Sun, 31 Dec 2000 17:53:40 -0800 (PST)
Organization: BSD, Inc.
From: John Baldwin <jhb@FreeBSD.ORG>
To: Matt Dillon <dillon@earth.backplane.com>
Subject: Re: Current hangs...
Cc: current@FreeBSD.ORG
Sender: jhb@foo.osd.bsdi.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 30-Dec-00 Matt Dillon wrote:
>  #include <sys/param.h>
> @@ -352,12 +352,25 @@
>               return (0);
>  
>       /*
> +      * MARK/SCAN initialization to avoid infinite loops
> +      */
> +     s = splbio();
> +        for (bp = TAILQ_FIRST(&vp->v_dirtyblkhd); bp;
> +             bp = TAILQ_NEXT(bp, b_vnbufs)) {
> +                bp->b_flags &= ~B_SCANNED;
> +     }
> +     splx(s);

Why not this:

s = splbio();
TAILQ_FOREACH(bp, &vp->v_dirtyblkhd, b_vnbufs) {
        bp->b_flags &= ~B_SCANNED;
}

We do have foreach queue(3) macros. :)

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 17:56: 3 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 17:56:02 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222])
	by hub.freebsd.org (Postfix) with ESMTP id 2C0E337B400
	for <freebsd-current@FreeBSD.ORG>; Sun, 31 Dec 2000 17:56:02 -0800 (PST)
Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137])
	by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f011tfh40074;
	Sun, 31 Dec 2000 17:55:41 -0800 (PST)
	(envelope-from jhb@foo.osd.bsdi.com)
Received: (from jhb@localhost)
	by foo.osd.bsdi.com (8.11.1/8.11.0) id f011u0s22402;
	Sun, 31 Dec 2000 17:56:00 -0800 (PST)
	(envelope-from jhb)
Message-ID: <XFMail.001231175600.jhb@FreeBSD.org>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <3A4F650D.3212A5C5@eqonline.fi>
Date: Sun, 31 Dec 2000 17:56:00 -0800 (PST)
Organization: BSD, Inc.
From: John Baldwin <jhb@FreeBSD.ORG>
To: User Sja <sakari.jalovaara@eqonline.fi>
Subject: RE: PROCTREE_LOCK() vs. gdb hang
Cc: freebsd-current@FreeBSD.ORG
Sender: jhb@foo.osd.bsdi.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 31-Dec-00 User Sja wrote:
> I don't really know my way around the kernel so I'm just guessing here:
> 
> Is there a proctree lock release operation missing in kern_sig.c,
> function issignal()?  There seems to be one lock operation more
> than there are release operations.  I tried putting one in and
> now gdb doesn't hang the whole machine (at least as easily as
> before.)

This looks correct.  If Paul can test it and commit it that would be most
helpful.

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 18: 4:52 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 18:04:51 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135])
	by hub.freebsd.org (Postfix) with ESMTP
	id E9E0637B400; Sun, 31 Dec 2000 18:04:50 -0800 (PST)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.1/8.9.3) id f0124oW47215;
	Sun, 31 Dec 2000 18:04:50 -0800 (PST)
	(envelope-from dillon)
Date: Sun, 31 Dec 2000 18:04:50 -0800 (PST)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200101010204.f0124oW47215@earth.backplane.com>
To: John Baldwin <jhb@FreeBSD.ORG>
Cc: current@FreeBSD.ORG
Subject: Re: Current hangs...
References:  <XFMail.001231175340.jhb@FreeBSD.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:
:Why not this:
:
:s = splbio();
:TAILQ_FOREACH(bp, &vp->v_dirtyblkhd, b_vnbufs) {

    First rule when making simple bug fixes by copying working code from one
    source file to another is:  Dont try to optimize the code on the
    fly.

    Personally speaking, I don't find the FOREACH macros any more readable
    vs an explicit for loop.  They hide too much... like for example the
    fact that you are dependant on the current pointer remaining valid to
    get the next pointer in the loop.

					-Matt



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 18:18:56 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 18:18:53 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222])
	by hub.freebsd.org (Postfix) with ESMTP id 99ECB37B400
	for <current@FreeBSD.ORG>; Sun, 31 Dec 2000 18:18:53 -0800 (PST)
Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137])
	by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f012IWh40279;
	Sun, 31 Dec 2000 18:18:32 -0800 (PST)
	(envelope-from jhb@foo.osd.bsdi.com)
Received: (from jhb@localhost)
	by foo.osd.bsdi.com (8.11.1/8.11.0) id f012Irl22548;
	Sun, 31 Dec 2000 18:18:53 -0800 (PST)
	(envelope-from jhb)
Message-ID: <XFMail.001231181852.jhb@FreeBSD.org>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <200101010204.f0124oW47215@earth.backplane.com>
Date: Sun, 31 Dec 2000 18:18:52 -0800 (PST)
Organization: BSD, Inc.
From: John Baldwin <jhb@FreeBSD.ORG>
To: Matt Dillon <dillon@earth.backplane.com>
Subject: Re: Current hangs...
Cc: current@FreeBSD.ORG
Sender: jhb@foo.osd.bsdi.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 01-Jan-01 Matt Dillon wrote:
>:
>:Why not this:
>:
>:s = splbio();
>:TAILQ_FOREACH(bp, &vp->v_dirtyblkhd, b_vnbufs) {
> 
>     First rule when making simple bug fixes by copying working code from one
>     source file to another is:  Dont try to optimize the code on the
>     fly.

That works.

>     Personally speaking, I don't find the FOREACH macros any more readable
>     vs an explicit for loop.  They hide too much... like for example the
>     fact that you are dependant on the current pointer remaining valid to
>     get the next pointer in the loop.

Erm, I find one succint line easier to read than something sprawled across 2-3
lines of code.  Also, I was never under the assumption that you could do a
*_FOREACH() loop while the list changed out from under you.  I doubt anyone
else is either. :)

>                                       -Matt

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 19:16:34 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 19:16:32 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail.gmx.net (pop.gmx.net [194.221.183.20])
	by hub.freebsd.org (Postfix) with SMTP id D504437B400
	for <freebsd-current@FreeBSD.ORG>; Sun, 31 Dec 2000 19:16:31 -0800 (PST)
Received: (qmail 807 invoked by uid 0); 1 Jan 2001 03:16:30 -0000
Received: from pd9508837.dip.t-dialin.net (HELO speedy.gsinet) (217.80.136.55)
  by mail.gmx.net (mail03) with SMTP; 1 Jan 2001 03:16:30 -0000
Received: (from sittig@localhost)
	by speedy.gsinet (8.8.8/8.8.8) id VAA10283
	for freebsd-current@FreeBSD.ORG; Sun, 31 Dec 2000 21:55:15 +0100
Date: Sun, 31 Dec 2000 21:55:15 +0100
From: Gerhard Sittig <Gerhard.Sittig@gmx.net>
To: freebsd-current@FreeBSD.ORG
Subject: Re: IGMP queries
Message-ID: <20001231215515.Q253@speedy.gsinet>
Mail-Followup-To: freebsd-current@FreeBSD.ORG
References: <001f01c07286$9a055a00$0e00a8c0@neland.dk> <20001230215241.M253@speedy.gsinet> <200012311049.eBVAnBr23486@whizzo.transsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <200012311049.eBVAnBr23486@whizzo.transsys.com>; from louie@TransSys.COM on Sun, Dec 31, 2000 at 05:49:11AM -0500
Organization: System Defenestrators Inc.
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Dec 31, 2000 at 05:49 -0500, Louis A. Mamakos wrote:
> 
> IGMP is the protocol used between a multicast router, and
> end-hosts on a subnetwork; much like ICMP is used between a
> router and an end-host to help manage unicast traffic.

I realize now that I have confused IGMP with EGP & friends.
Looking at /etc/protocols could have saved me from this. :)

igmp  2   IGMP   # internet group management protocol
egp   8   EGP    # exterior gateway protocol

> So that's why you're seeing IGMP queries; the multicast router
> is trying to see if you've joined any multicast groups so it
> can try to send you traffic.  It's got nothing to do with
> "having the world tell you where to send your packets to."

The bad feelings I have with these is when reading Linux mailing
lists (far behind in the past:) where people always wondered "why
does my ISP connection always go up / keep up?" when they thought
running routed(8) would be a Bright Idea (TM).  Thinking about
routing in a LAN with four machines and doing it manually must be
very demanding. :>  And again see my above confusion with EGP.


OK, there's sooo much yet to learn for me ...  Keep buzzing when
I do something wrong, I'm very *happy* with getting corrected. :)


virtually yours   82D1 9B9C 01DC 4FB4 D7B4  61BE 3F49 4F77 72DE DA76
Gerhard Sittig   true | mail -s "get gpg key" Gerhard.Sittig@gmx.net
-- 
     If you don't understand or are scared by any of the above
             ask your parents or an adult to help you.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


From owner-freebsd-current  Sun Dec 31 21:46:13 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 31 21:46:11 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
	by hub.freebsd.org (Postfix) with ESMTP id E375F37B400
	for <freebsd-current@FreeBSD.ORG>; Sun, 31 Dec 2000 21:46:10 -0800 (PST)
Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1])
	by whizzo.transsys.com (8.11.1/8.11.0) with ESMTP id f015k9r27506;
	Mon, 1 Jan 2001 00:46:09 -0500 (EST)
	(envelope-from louie@whizzo.transsys.com)
Message-Id: <200101010546.f015k9r27506@whizzo.transsys.com>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: Gerhard Sittig <Gerhard.Sittig@gmx.net>
Cc: freebsd-current@FreeBSD.ORG
X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: IGMP queries 
References: <001f01c07286$9a055a00$0e00a8c0@neland.dk> <20001230215241.M253@speedy.gsinet> <200012311049.eBVAnBr23486@whizzo.transsys.com> <20001231215515.Q253@speedy.gsinet> 
In-reply-to: Your message of "Sun, 31 Dec 2000 21:55:15 +0100."
             <20001231215515.Q253@speedy.gsinet> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 01 Jan 2001 00:46:09 -0500
Sender: louie@TransSys.COM
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


EGP hasn't been in wide use for probably 7 or 8 years now.

I think the real problem with this dynamic link issue and keeping the
connection up is that the default policy is wrong.  You ought to 
specify what sort of traffic is "important" and should cause a
dynamic link to be established (and kept up), rather than trying
to exclude things.

For example, you'd probably not want to have NTP establish or keep
your link up; perhaps not DNS, either.  Probabably you'd want
TCP/SSH or TCP/HTTPD though.

louie



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message


