Bad fix for -current breakage

Note, a real fix would be applied to all the config.* files, and would depend on the BOOTSTRAP symbol that we define during the early stages of the build. This is my wimpy fix for people that want a quick fix to the problem of building -current on -stable. Now, to the next breakage in the tree :

World on -stable is busted

cc -O -pipe -I/usr/obj/home/imp/FreeBSD/src/gnu/usr.bin/perl/miniperl -I/home/imp/FreeBSD/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -DPERL_EXTERNAL_GLOB -DPERL_CORE -DAPPLLIB_EXP=\"/usr/libdata/perl/BSDPAN\" -L/usr/obj/home/imp/FreeBSD/src/gnu/usr.bin/perl/miniperl/../libperl

Re: panic: bwrite: buffer is not busy???

* Dag-Erling Smorgrav <[EMAIL PROTECTED]> [020317 22:55] wrote: > Alfred Perlstein <[EMAIL PROTECTED]> writes: > > Please let me know if this works for you. > > [...] > > + PROC_LOCK(td); > > *cough* *cough* > > :) It was untested. :) I'm sure you can fix it, I've got to get some sleep, let

Re: panic: bwrite: buffer is not busy???

Alfred Perlstein <[EMAIL PROTECTED]> writes: > Please let me know if this works for you. > [...] > + PROC_LOCK(td); *cough* *cough* :) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the messag

utmp and current

Hi, I updated to current 5.0 several weeks back and just noticed that the utmp logging for people users logged in is missing. The wtmp is populated very strangely too. None of the ttyv* are logged logging of ttyp* is selective ( on what ? I havent been able to figure it out). All the li

Re: panic: bwrite: buffer is not busy???

On Sun, Mar 17, 2002 at 10:17:39PM -0800, Alfred Perlstein wrote: > * Dag-Erling Smorgrav <[EMAIL PROTECTED]> [020317 19:27] wrote: > > > > ...the process has no open files at all, because... > > > > (kgdb) p p->p_pid > > $4 = 10099 > > (kgdb) p p->p_comm > > $5 = "wc\000oot", '\000' > > (kgdb)

Re: panic: bwrite: buffer is not busy???

* Dag-Erling Smorgrav <[EMAIL PROTECTED]> [020317 19:27] wrote: > > ...the process has no open files at all, because... > > (kgdb) p p->p_pid > $4 = 10099 > (kgdb) p p->p_comm > $5 = "wc\000oot", '\000' > (kgdb) p p->p_stat > $6 = 3 > (kgdb) p/x p->p_flag > $7 = 0x6000 > > ...it's exiting, and

Re: panic: bwrite: buffer is not busy???

Kris Kennaway <[EMAIL PROTECTED]> writes: > #14 0xc0204b92 in _mtx_lock_sleep (m=0xc2f91f34, opts=0, file=0x0, line=0) > at ../../../kern/kern_mutex.c:370 (kgdb) up 14 #14 0xc0204b92 in _mtx_lock_sleep (m=0xc2f91f34, opts=0, file=0x0, line=0) at ../../../kern/kern_mutex.c:370 370

zlib breakage(was cvs commit: src/share/man/man4 ng_pptpgre.4)

This bug affects everything that uses libz of course. It also breaks zgrep. Try "cd /home/ncvs/C*/*logs; zgrep foo *". On Sun, 17 Mar 2002, Bruce Evans wrote: > On Sun, 17 Mar 2002, I wrote: > > > That may be, but ispell is not man's best friend: > > > > $ man ispell > > Segmentation f

Re: Patch to fix the build of the smbfs.ko kernel module

Hi, > On Sun, 17 Mar 2002 15:38:48 -0800 > Maxime Henrion <[EMAIL PROTECTED]> said: mux> Actually, this patch is wrong because it won't ever compile des_enc.S. mux> Whatever I do, des_enc.c gets compiled and I can't figure out how to mux> compile a .S file with bsd.kmod.mk. If someone w

Re: panic: bwrite: buffer is not busy???

Kris Kennaway <[EMAIL PROTECTED]> writes: > [...] "up 14" followed by "p *m" would be nice; making the dump and the debugging kernel available on freefall would be even nicer. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebs

Re: cvs commit: src/sys/kern kern_mtxpool.c src/sys/sys kernel.h src/sys/vm vm_fault.c vm_glue.c vm_map.c vm_map.h vm_pageout.c vm_zone.c

:Hmm. Ok, so right now the code that has been branched for DP1 makes use :of Brian's recent locking commits. My original thought was we'd simply :back it out of that branch to make sure that the DP is reliable. How hard :would it be for us to switch to what you propose (just convert all slocks

Re: cvs commit: src/sys/kern kern_mtxpool.c src/sys/sys kernel.h src/sys/vm vm_fault.c vm_glue.c vm_map.c vm_map.h vm_pageout.c vm_zone.c

On Sun, 17 Mar 2002, Matthew Dillon wrote: > It fixed some things, it broke some things. Pretty much standard > fare for anyone who has ever done work on the vm_map lock, including > yours truely. John Dyson couldn't get it right, David Greenman couldn't > get it right, I could

Re: HEADS UP: -CURRENT Feature Slush is OVER

On Sun, 17 Mar 2002, Terry Lambert wrote: > Garance A Drosihn wrote: > > At 1:15 AM -0800 3/17/02, Murray Stokely wrote: > > >On Sun, Mar 17, 2002 at 01:08:43AM -0800, Terry Lambert wrote: > > >> Minimally, pick a date, and then do a CVS diff against that > > >> date, and include it on the CDR

Re: HEADS UP: -CURRENT Feature Slush is OVER

Garance A Drosihn wrote: > At 1:15 AM -0800 3/17/02, Murray Stokely wrote: > >On Sun, Mar 17, 2002 at 01:08:43AM -0800, Terry Lambert wrote: > >> Minimally, pick a date, and then do a CVS diff against that > >> date, and include it on the CDROM. > > > > I would be happy to do this. I checked

Re: cvs commit: src/sys/kern kern_mtxpool.c src/sys/sys kernel.h src/sys/vm vm_fault.c vm_glue.c vm_map.c vm_map.h vm_pageout.c vm_zone.c

: :Hi, : :Sorry to unwantedly butt in, but the patch supplied by Seigo actually :solved the vm_map.c locking problems which used to come up on my system. :Just some info. :) : :Regards, : : -- Hiten Pandya : -- <[EMAIL PROTECTED]> It fixed some things, it broke some things. Pretty much st

Re: Patch to fix the build of the smbfs.ko kernel module

Hajimu UMEMOTO wrote: > Hi, > > > On Sat, 16 Mar 2002 01:32:04 -0800 > > Maxime Henrion <[EMAIL PROTECTED]> said: > > mux> Since the addition of optimized 3DES encryption for x86, the build of the > mux> smbfs kernel module has been broken (on all platforms). This is because > mux> new

Re: panic: bwrite: buffer is not busy???

On Sun, Mar 17, 2002 at 12:49:58PM -0800, Kris Kennaway wrote: > I tried upgrading the bento cluster to 5.x so I can actually get 5.0 > packages built (eaccess problems), and 5 of them blew up in about 10 > minutes with this (I think this is going to be an .. uh .. interesting > test of the stabil

Re: HEADS UP: -CURRENT Feature Slush is OVER

In message , Garance A Drosihn writes: >At 8:35 AM -0800 3/17/02, David O'Brien wrote: >>My earlier concerns about the use of Perforce were when a developers >>expected other developers to use Perforce for _shared_ development. >>Or that tried to claim that t

Re: -current lock warning...

Apparently, On Sun, Mar 17, 2002 at 09:17:22AM -0800, Alfred Perlstein said words to the effect of; > * Robert Watson <[EMAIL PROTECTED]> [020317 09:08] wrote: > > > > On Sun, 17 Mar 2002, Alfred Perlstein wrote: > > > > > * Munehiro Matsuda <[EMAIL PROTECTED]> [020317 06:36] wrote: > >

Re: HEADS UP: -CURRENT Feature Slush is OVER

At 8:35 AM -0800 3/17/02, David O'Brien wrote: >My earlier concerns about the use of Perforce were when a developers >expected other developers to use Perforce for _shared_ development. >Or that tried to claim that their code was "published" if it was >in the Perforce depot on Freefall. Exactly m

Re: panic: bwrite: buffer is not busy???

On Sun, Mar 17, 2002 at 12:49:58PM -0800, Kris Kennaway wrote: > I tried upgrading the bento cluster to 5.x so I can actually get 5.0 > packages built (eaccess problems), and 5 of them blew up in about 10 > minutes with this (I think this is going to be an .. uh .. interesting > test of the stabil

Re: HEADS UP: -CURRENT Feature Slush is OVER

At 1:15 AM -0800 3/17/02, Murray Stokely wrote: >On Sun, Mar 17, 2002 at 01:08:43AM -0800, Terry Lambert wrote: >> Minimally, pick a date, and then do a CVS diff against that >> date, and include it on the CDROM. > > I would be happy to do this. I checked out a copy of the CVS tree >right bef

panic: bwrite: buffer is not busy???

I tried upgrading the bento cluster to 5.x so I can actually get 5.0 packages built (eaccess problems), and 5 of them blew up in about 10 minutes with this (I think this is going to be an .. uh .. interesting test of the stability of 5.0-CURRENT): IdlePTD at phsyical address 0x004a6000 initial pc

5.0-C KERNEL (Was: Re: problems with perl)

> cc1: warnings being treated as errors # make NO_WERROR=yes ... M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: problems with perl

>> The perl upgrade seems to be having problems. I got this twice >> towday making buildworld from 4.5: > Please test the enclosed patch. That patch allows perl to compile. Unfortunatly, I'm still unable to make a 5.0 kernel from 4.5, so I cant test it. cc -c -O -pipe -Wall -Wredundant-dec

Re: cvs commit: src/sys/kern kern_mtxpool.c src/sys/sys kernel.h src/sys/vm vm_fault.c vm_glue.c vm_map.c vm_map.h vm_pageout.c vm_zone.c

Hi, Sorry to unwantedly butt in, but the patch supplied by Seigo actually solved the vm_map.c locking problems which used to come up on my system. Just some info. :) Regards, -- Hiten Pandya -- <[EMAIL PROTECTED]> --- Matthew Dillon <[EMAIL PROTECTED]> wrote: > I have no idea what the

Re: cvs commit: src/sys/kern kern_mtxpool.c src/sys/sys kernel.hsrc/sys/vm vm_fault.c vm_glue.c vm_map.c vm_map.h vm_pageout.c vm_zone.c

I have no idea what the frig you guys are doing in vm_map.c. I would recommend that all the changes be backed out. Then I would recommend that the following be done: * change the lockmgr vm_map lock to be exclusive-only * test & commit * change the lockmgr vm

subscribe

subscribe _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: -current lock warning...

* Robert Watson <[EMAIL PROTECTED]> [020317 09:08] wrote: > > On Sun, 17 Mar 2002, Alfred Perlstein wrote: > > > * Munehiro Matsuda <[EMAIL PROTECTED]> [020317 06:36] wrote: > > > > > > PS. I got another message that happend when I ^C'ed a buildworld earlier, > > > with same kernel. May be it

Re: -current lock warning...

On Sun, 17 Mar 2002, Alfred Perlstein wrote: > * Munehiro Matsuda <[EMAIL PROTECTED]> [020317 06:36] wrote: > > > > PS. I got another message that happend when I ^C'ed a buildworld earlier, > > with same kernel. May be it should go to Alfred Perlstein? > > > > lock order reversal > > 1st 0xc

kernel build failure in amr

Hi, Without -DNO_WERROR, i sometimes get a build failure on CURRENT sources, as shown below. However, this does not always occur, maybe 30% of the compiles succeed. Why would it sometimes compile fine? I've deleted my /usr/obj and /usr/src, and even my cvs repositry, without success.# Gavin cc

Re: HEADS UP: -CURRENT Feature Slush is OVER

On Sun, Mar 17, 2002 at 12:56:42AM -0800, Terry Lambert wrote: > It seems to me that, at worst, this is being done to "prove > to the heathens" that use of Perforce is a bad idea. It > certainly is, if history is going to be lost, but that's not > a result of the tool, here, it's a result of inte

Re: HEADS UP: -CURRENT Feature Slush is OVER

On Sun, Mar 17, 2002 at 01:08:43AM -0800, Terry Lambert wrote: > Imagine that you have the developer's prerelease, and you > have a bug (because you're a developer who's using the > pre-release). > > Now say you have become involved in the process, because the > pre-release has done it's job. Yo

Re: -current lock warning...

* Munehiro Matsuda <[EMAIL PROTECTED]> [020317 06:36] wrote: > > PS. I got another message that happend when I ^C'ed a buildworld earlier, > with same kernel. May be it should go to Alfred Perlstein? > > lock order reversal > 1st 0xc198eec0 pipe mutex @ ../../../kern/sys_pipe.c:779 > 2nd 0xc0

Re: HEADS UP: -CURRENT Feature Slush is OVER

On Sun, Mar 17, 2002 at 02:13:16AM -0800, Annelise Anderson wrote: > > If a tag was laid down can't it be retrieved indefinitely? A non-branching > tag? What am I missing? The tag will create a point in time in the CVS repository that cannot be ever changed. This is a restriction that we've al

Re: HEADS UP: -CURRENT Feature Slush is OVER

On Sun, Mar 17, 2002 at 10:48:53AM +0100, Hellmuth Michaelis wrote: > Not taking into account (good) technical reasons, i am quite a bit > concerned about the increasing tendency to a) use "private" repositories > instead of the one and only repository every committer is able to see and > use and

Re: -current lock warning...

From: Seigo Tanimura <[EMAIL PROTECTED]> Date: Sun, 17 Mar 2002 01:17:21 +0900 ::Seigo> On Sat, 16 Mar 2002 10:22:22 +0100, ::Seigo> Poul-Henning Kamp <[EMAIL PROTECTED]> said: :: ::Seigo> Poul-Henning> acquiring duplicate lock of same type: "thrd_sleep" ::Seigo> Poul-Henning> 1st @ ../../../vm

Re: web Browsers (Re: gcc -O broken in CURRENT)

* Greg Black ([EMAIL PROTECTED]) wrote: > Joerg Wunsch wrote: > > > Galeon. > > Yeah right. Galeon wouldn't even build on the last FreeBSD box I > tried it on when somebody told me to try it. Tried Skipstone? Gecko based GTK browser. -- Thomas 'Freaky' Hurst - [EMAIL PROTECTED] - http://

Re: strange apm/acpi message on CPQ Armada E700

On Fri, Mar 15, 2002 at 11:11:45PM +0100, Wilko Bulte wrote: Never mind.. this was due to the fact that device.hints had APM disabled. Looks a lot better now: APM version: 1.2 APM Managment: Enabled AC Line status: on-line Battery status: charging Remaining battery life: 62% Remaining battery t

Re: HEADS UP: -CURRENT Feature Slush is OVER

On Sun, Mar 17, 2002 at 02:13:16AM -0800, Annelise Anderson wrote: > > The source will be on the CDROM. Nor is there any major importance to > > DP1. Are you also upset that you cannot reproduce the July 17th, 1998 > > -CURRENT snapshot CD from WC? > > > If a tag was laid down can't it be retri

Re: HEADS UP: -CURRENT Feature Slush is OVER

On Sun, 17 Mar 2002, David O'Brien wrote: > On Sat, Mar 16, 2002 at 02:08:51PM -0800, Terry Lambert wrote: > > I hate this whole direction. > > > > I think it's an incredibly bad idea that we are not going > > to be able to reproduce what went onto any given CDROM in > > ten years. > > The sour

Re: problems with perl

> The perl upgrade seems to be having problems. I got this twice > towday making buildworld from 4.5: Please test the enclosed patch. M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn Index: config.SH-elf.alpha =

Re: HEADS UP: -CURRENT Feature Slush is OVER

>From the keyboard of Murray Stokely: > tree for previous snapshots. We are actually moving more in the > direction you advocate by at least moving the snapshot production into > Perforce so that more developers can participate. Not taking into account (good) technical reasons, i am quite a bit

Re: HEADS UP: -CURRENT Feature Slush is OVER

On Sun, Mar 17, 2002 at 01:08:43AM -0800, Terry Lambert wrote: > Minimally, pick a date, and then do a CVS diff against that > date, and include it on the CDROM. I would be happy to do this. I checked out a copy of the CVS tree right before we made the Perforce branch so that we could tag it l

Re: HEADS UP: -CURRENT Feature Slush is OVER

Murray Stokely wrote: > On Sat, Mar 16, 2002 at 02:08:51PM -0800, Terry Lambert wrote: > > I think it's an incredibly bad idea that we are not going > > to be able to reproduce what went onto any given CDROM in > > ten years. > >I agree that it is very important to be able to reproduce offici

Re: web Browsers (Re: gcc -O broken in CURRENT)

Maxim Sobolev wrote: | On Sun, 2002-03-17 at 09:56, Greg Black wrote: | > Yeah right. Galeon wouldn't even build on the last FreeBSD box | > I tried it on when somebody told me to try it. | | It compiles/works here like a charm, however, if you do have problems | with it please send a problem re

Re: HEADS UP: -CURRENT Feature Slush is OVER

David O'Brien wrote: > On Sat, Mar 16, 2002 at 02:08:51PM -0800, Terry Lambert wrote: > > I hate this whole direction. > > > > I think it's an incredibly bad idea that we are not going > > to be able to reproduce what went onto any given CDROM in > > ten years. > > The source will be on the CDROM

Re: web Browsers (Re: gcc -O broken in CURRENT)

On Sun, 2002-03-17 at 09:56, Greg Black wrote: > Joerg Wunsch wrote: > > | "David O'Brien" <[EMAIL PROTECTED]> wrote: > | > | >> Slow. Eats memory. Crashes all the time. Does not save state > | >> between sessions. Does not render HTML 4 properly. Does not support > | >> CSS properly. Does

Re: web Browsers (Re: gcc -O broken in CURRENT)

"David O'Brien" wrote: | On Sat, Mar 16, 2002 at 06:05:13AM +0100, Dag-Erling Smorgrav wrote: | > Garrett Wollman <[EMAIL PROTECTED]> writes: | > > What problems do you have with it? | > | > Slow. Eats memory. Crashes all the time. Does not save state | > between sessions. Does not render HTM

Re: ACPI autoload failed -- unable to install

Folks, the "autoload failed" message is just telling you that you have ACPI, but there is no ACPI KLD on the floppy. It has absolutely nothing whatsoever to do with your problem. By the sound of it, you've got a corrupted floppy image. -- To announce that there must be no criticism of the p

Re: HEADS UP: -CURRENT Feature Slush is OVER

On Sat, Mar 16, 2002 at 02:08:51PM -0800, Terry Lambert wrote: > I think it's an incredibly bad idea that we are not going > to be able to reproduce what went onto any given CDROM in > ten years. I agree that it is very important to be able to reproduce official releases of FreeBSD N years dow

problems with perl

The perl upgrade seems to be having problems. I got this twice towday making buildworld from 4.5: thanx, brad [...] cc -O -pipe -I/usr/obj/5.0/usr/src/gnu/usr.bin/perl/miniperl -I/5.0/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -DPERL_EXTERNAL_GLOB -DPERL_CORE -DAPPLLIB_EXP

Re: HEADS UP: -CURRENT Feature Slush is OVER

On Sat, 2002-03-16 at 21:53, David O'Brien wrote: > On Sat, Mar 16, 2002 at 04:43:47PM +0200, Maxim Sobolev wrote: > > > primary goals in all of this are (1) to provide a usable preview of > > > the 5.0-CURRENT code, and (2) to minimize the impact on -CURRENT > > > developers. After evaluating se

Re: HEADS UP: -CURRENT Feature Slush is OVER

On Sat, Mar 16, 2002 at 02:08:51PM -0800, Terry Lambert wrote: > I hate this whole direction. > > I think it's an incredibly bad idea that we are not going > to be able to reproduce what went onto any given CDROM in > ten years. The source will be on the CDROM. Nor is there any major importance