Re: MLEN and crashes

Peter Wemm writes: >Gary Jennejohn wrote: >> Bruce Evans writes: >> >On Mon, 3 Apr 2000, Gary Jennejohn wrote: >> > >> >> Bruce Evans writes: >> >> >On Sun, 2 Apr 2000, Gary Jennejohn wrote: >> >> >> I think we should nuke csu_hdr since it's not used anywhere. Is that >> >> >> what you really mean

Re: MLEN and crashes

Gary Jennejohn wrote: > Peter Wemm writes: > >Gary Jennejohn wrote: > >> Bruce Evans writes: > >> >On Mon, 3 Apr 2000, Gary Jennejohn wrote: > >> > > >> >> Bruce Evans writes: > >> >> >On Sun, 2 Apr 2000, Gary Jennejohn wrote: > >> >> >> I think we should nuke csu_hdr since it's not used anywhere.

PPP segfaulting

Hi, The ppp built from the just cvsup'ed -current sources segfaulting. Following is backtrace. Please contact me of some additional debugging info will be necessary. -Maxim PPP ON vega> Program received signal SIGSEGV, Segmentation fault. 0x806e98e in sl_compress_tcp (m=0x809e000, ip=0x809e01c,

Sysctl

I don't know whether to hand this to -doc or here, so I'll take the risk of here, patch simply adds comments to sysctl variables. Started work on netinet, hopefully I'll have more later on in the day. (It's 4:40am right now). -- snip -- --- if_ether.c.orig Tue Apr 4 04:14:02 2000 +++ if_eth

world broken?

Hi! Is the world broken or I've missed something important? ===> gnu/usr.bin/groff/lkbib cc -O -pipe -I/usr/src/gnu/usr.bin/groff/lkbib/../include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1

UNIONFS

Here be dragons, I know :-). Got myself a nice juicy & reproducable crash here, so I thought I might as well try to track down this problem. But before I start,is anyone else working on this one? I'd hate to waste my not exactly ample time trying to duplicate somebody else's work. Regards, Timo

Re: PPP segfaulting

Maxim Sobolev writes: >Hi, > >The ppp built from the just cvsup'ed -current sources segfaulting. Following i >s >backtrace. Please contact me of some additional debugging info will be >necessary. > >-Maxim > >PPP ON vega> >Program received signal SIGSEGV, Segmentation fault. >0x806e98e in sl_compr

Re: UNIONFS

On Tue, 4 Apr 2000, Timo Geusch wrote: > Here be dragons, I know :-). Got myself a nice juicy & reproducable > crash here, so I thought I might as well try to track down this > problem. But before I start,is anyone else working on this one? I'd > hate to waste my not exactly ample time trying to

Re: Deadlock with vinum raid5

On Tue, Apr 04, 2000 at 08:59:59AM +0930, Greg Lehey <[EMAIL PROTECTED]> wrote: > Do you have dumps? No, for obvious reasons explained earlier. I'll spend some time today afternoon and set up suitable environment for getting dumps and debugging. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubsc

Re: Load average calculation?

On Mon, 3 Apr 2000, Richard Wackerbarth wrote: > On Mon, 03 Apr 2000, Donn Miller wrote: > > > I think we ought to re-examine the definition of load average. By > > load, we mean an actual load on the cpu, and waiting processes aren't > > really exerting a cpu load. So, by that reasoning I say

Re: ATA & 82C596 bug in 4.0-RELEASE?

> > > > > > I tried to install 4.0-RELEASE on a completely new PC system, but the > > > install failed with ATA write errors and resets. I moved the disk to another > > > PC and installed 4.0 via manual disklabels, newfs, bin + src extraction. > > > 4.0 booted fine on this system (a Dell Optiplex

Re: ATA & 82C596 bug in 4.0-RELEASE?

It seems John Hay wrote: > > > > Yup VIA has a new version of the 82C596 chip, in their usual visdom they > > change the interface, but not the chip ID (I'll nominate VIA for the > > way they do versioning). However I have worked out the solution with > > Chris Wiener <[EMAIL PROTECTED]>, that h

Re: ATA & 82C596 bug in 4.0-RELEASE?

On 4/04, John Hay wrote: | I have a machine that can be trashed. The trouble is that it cannot | install 4.x or -current because of the problem with the ata driver. | During installation it just go in a loop during newfs and keep on | spitting out errors. You are lucky, you go further than I do

Re: 2nd call for reviews and tests: buf->bio patch

At 8:14 AM +0200 2000/4/4, Jeroen Ruigrok/Asmodai wrote: > Besides, CURRENT does allow for the tree to be broken. I guess Bleeding > Edge lost its meaning within the FreeBSD ranks. Yes, but RELENG_4 is no longer -CURRENT. Therefore, different procedures need to be applied to it, now

Re: 2nd call for reviews and tests: buf->bio patch

At 8:23 AM +0200 2000/4/4, Jeroen Ruigrok/Asmodai wrote: > Like I said in another mail, this is CURRENT, things are > expected to break. You want stability of API's, go 3-STABLE. You want > a somewhat stable environment, go 4-STABLE. 5 is bleeding edge, have > your bandages ready.

Re: 2nd call for reviews and tests: buf->bio patch

It seems Brad Knowles wrote: > > Like I said in a previous message, Poul broke vinum (among other > things) under 4.0-STABLE, and this needs to be fixed ASAP. If Poul > had kept his changes unique to -CURRENT, then 4.0-STABLE wouldn't > have been affected. But he didn't, and it was. W

Re: 2nd call for reviews and tests: buf->bio patch

In message , Brad Knowles writes: >At 8:23 AM +0200 2000/4/4, Jeroen Ruigrok/Asmodai wrote: > >> Like I said in another mail, this is CURRENT, things are >> expected to break. You want stability of API's, go 3-STABLE. You want >> a somewhat stab

Re: UNIONFS

On Tue, Apr 04, 2000, Kris Kennaway wrote: > On Tue, 4 Apr 2000, Timo Geusch wrote: > > > Here be dragons, I know :-). Got myself a nice juicy & reproducable > > crash here, so I thought I might as well try to track down this > > problem. But before I start,is anyone else working on this one? I'd

Re: PPP segfaulting

Sorry, I should have done more than a few greps when reviewing this. The slcompress code is diving into the TCP header that comes after the IP header There's some nasty stuff going on here between vjcomp.c and slcompress.c - namely, the pointer passed into sl_uncompress_tcp is expected t

Re: 2nd call for reviews and tests: buf->bio patch

At 3:33 PM +0200 2000/4/4, Poul-Henning Kamp wrote: > I have not made one single commit to 4.0-STABLE which even comes > close to vinum. My apologies. I must have misread/misremembered what was being said with regards to the commits breaking vinum, and somehow gotten that crossed wi

current.freebsd.org

It seems that current.freebsd.org has been not working for a while now, and I was wondering if there is a better place to get the new snapshots, as well as install -current. I brief search of the mail archives tells me nothing ( i may have missed it, searching for current.freebsd.org on

Re: ATA & 82C596 bug in 4.0-RELEASE?

In message <[EMAIL PROTECTED]> John Hay writes: : > Woa! I havn't seen any reports of the '586 not working, please point : : I did report it to -current about the 9th of March and you did respond : to that message. I do seem to remember others complaining too, but when : I tried to look for them

Re: ATA & 82C596 bug in 4.0-RELEASE?

> > > > > > Yup VIA has a new version of the 82C596 chip, in their usual visdom they > > > change the interface, but not the chip ID (I'll nominate VIA for the > > > way they do versioning). However I have worked out the solution with > > > Chris Wiener <[EMAIL PROTECTED]>, that had this problem

Dangerously looking glitch (4.0-STABLE)

Hi, I've tried to track down why my own script which is cleaning non-matching distfiles from time to time produce incorrect results (just cvsup'ed 4.0). After some digging I've found that this bug could be easily reproduced by doing "find -exec md5" on large set of files several times consequient

Re: 2nd call for reviews and tests: buf->bio patch

On Tue, Apr 04, 2000 at 08:14:40AM +0200, Jeroen Ruigrok/Asmodai wrote: > Ehm. Not as if your VM stuff wasn't causing disruption. Needed, > granted, but disruptive as well. And ucd-snmp has been broken quite > some time (still is?) due to the work. > And I know of a lot of people who actively

Re: PPP segfaulting

Brian Somers writes: >Sorry, I should have done more than a few greps when reviewing this. While we're in self-castigation mode here ;), _I_ should have done more than a few greps before *committing* this. My first pointy hat in 5 years, not bad (of course, I don't do all that much committing).

Re: Load average calculation?

> Patrick Mau wrote: > > > On all Unix-like systems I know, the load average is the average mumber > > of processes running during a given time interval. I can't see what use > > it may have to count load for _waiting_ processes. > > > > I/O load is not process load, if a process waits for I/O c

sshd library problems

Hello all, I am running a 5.0-CURRENT system cvsup'd this afternoon, and sshd is not working for me. When I try to start it, I get the following: ** RSA_PKCS1: Unable to find an RSA implemenation shared library. ** Install either the USA (librsaINTL.so) or International (librsaUSA.so) ** RSA li

Re: UNIONFS

> I'm starting VFS hacking again :) Throw up a PR, I'll assign it to myself > and I'll look at it for you. Mind if I tag along for the ride? I just finished a "code walkthrough" class and vfs_ is somewhat fresh. Painfully fresh, I may add. I'll gladly sanity check patches. I was looking for a e

Re: 2nd call for reviews and tests: buf->bio patch

> Like I said in a previous message, Poul broke vinum (among other > things) under 4.0-STABLE, and this needs to be fixed ASAP. If Poul I'd actually consider it a really good idea if you could back this up since I have not seen anything to suggest that phk's changes have affected 4.0-STA

Re: FreeBSD random I/O performance issues

On Thu, 23 Mar 19100 (not like I'm slow or anything), Matthew Dillon wrote: [regarding random-access database files, such as are used for the INN history files, and FreeBSD 4.0...] > For INN there are several things you can tune in 4.0. First and > foremost you can try turning off the w

Re: sshd library problems

Hi Ben :) On Tue, Apr 04, 2000 at 05:41:05PM -0400, a little birdie told me that Ben Rosengart remarked > Hello all, > I am running a 5.0-CURRENT system cvsup'd this afternoon, and sshd is > not working for me. When I try to start it, I get the following: > > ** RSA_PKCS1: Unable to find an R

Re: sshd library problems

On Tue, Apr 04, 2000 at 05:28:52PM -0500, Matthew D. Fuller wrote: > Hi Ben :) Hello Matthew, always nice to "see" you. > On Tue, Apr 04, 2000 at 05:41:05PM -0400, a little birdie told me > that Ben Rosengart remarked > > Hello all, > > I am running a 5.0-CURRENT system cvsup'd this afternoon

USB/Orb/kue/iopener/filesystem corruption

On Mon, Apr 03, 2000 at 01:27:25PM -0400, Christopher Masto wrote: > Regarding USB drives, I have been using the Orb "2.2GB" USB-SCSI > version with some success. There do seem to be some serious > filesystem corruption problems, but I haven't had time to determine > where they're coming from. I

Re: USB/Orb/kue/iopener/filesystem corruption

Why does this sound like the warning that is written in the manual of the Iomega Zip drive: do not connect more than one Zip drive to the same USB host data might corrupted. Or something similar... Nick On Tue, 4 Apr 2000, Christopher Masto wrote: > On Mon, Apr 03, 2000 at 0

signal mask from jmp_buf

Hi all, What is the proper way for obtaining the signal mask from within the jmp_buf struct on 4.x or -current? Previously with the JDK port for < 3.x we did something like this: signalMask = jmpbuf[0]._sjb[6]; This no longer works now that we support >32 signals. Is there a better, m

Re: USB/Orb/kue/iopener/filesystem corruption

On Wed, Apr 05, 2000 at 12:07:55AM +0100, Nick Hibma wrote: > > Why does this sound like the warning that is written in the manual of > the Iomega Zip drive: > > do not connect more than one Zip drive to the same USB host data > might corrupted. > > Or something similar... But.. bu

Re: FreeBSD random I/O performance issues

On Sun, 2406 Sep 1993, Matthew Dillon wrote: > I've committed an 80% fix for the random seek / write > performance issue. The rest of the fix will come later > when Kirk commits his shared-lock-buffer-cache idea. > > I've committed it into -current and will MFC it into > -st

Re: Neat kernel development environment.

On Sat, Apr 01, 2000 at 04:32:36AM +1000, Matthew Dillon wrote: >I can just see all the coolness seeping out. Now guys, we have to >have as a goal something at least as comparable as what IBM did >with one of their mainframes. Oh, say, lets shoot for being able to >run 4000 copie

Re: FreeBSD random I/O performance issues

:Woo. Okay, so I took the bait and snarfed the k0deZ from midday GMT :02.April, and have built a suitable SMP kernel and world, and that's :what I've been running for one news peering swerver for a spell. : :... : :As I noted in the earlier message I just sent, disabling the write- :behind via t

Re: signal mask from jmp_buf

:Hi all, : :What is the proper way for obtaining the signal mask from :within the jmp_buf struct on 4.x or -current? Previously :with the JDK port for < 3.x we did something like this: : : signalMask = jmpbuf[0]._sjb[6]; : :This no longer works now that we support >32 signals. Is :there a

Is current.freebsd.org running Linux?

Why is this machine (current.freebsd.org) always rejecting guest privileges and why won't ANYBODY answer the question? Thanks in advance, Tom Veldhouse [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Is current.freebsd.org running Linux?

> Why is this machine (current.freebsd.org) always rejecting guest privileges > and why won't ANYBODY answer the question? Because it's been answered about a dozen times already; it's down with hardware problems, and the people responsible are trying to do something about it. -- \\ Give a man

Re: Is current.freebsd.org running Linux?

current.jp.freebsd.org is another stable/current build machine. /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: finger -l [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Please review newbus patch for amd and adv

In message <[EMAIL PROTECTED]> Takahashi Yoshihiro writes: : There is not ISA bus on PC-98. So, we can't use devices for ISA bus on : PC-98. But, PC-98 has `Cbus' which is like ISA bus in software place. : As most codes for ISA bus are useful for Cbus, the code for Cbus is : based on the code for

Re: sshd library problems

On Tue, 4 Apr 2000, Matthew D. Fuller wrote: > > ** RSA_PKCS1: Unable to find an RSA implemenation shared library. > (Aren't those filenames reversed? Just a hunch...) Thanks for catching these - I've just fixed the typos. Kris In God we Trust -- all others must submit an X.509 certifica

Upgrade 3.4 -> 5.0 -current Success

I just upgraded a 3.4 system from the Jan. 2000 CD to 5.0 -current. I used the 3.4 CD as an installation vehicle to get -current on a new disk, cleaning the tree in the process. I removed about 100MB that had accumulated over three years tracking -current. I had an existing -current system, and

Re: signal mask from jmp_buf

> Hi all, > > What is the proper way for obtaining the signal mask from > within the jmp_buf struct on 4.x or -current? Previously > with the JDK port for < 3.x we did something like this: > > signalMask = jmpbuf[0]._sjb[6]; > > This no longer works now that we support >32 signals. Is

Re: signal mask from jmp_buf

> > What is the proper way for obtaining the signal mask from > > within the jmp_buf struct on 4.x or -current? Previously > > with the JDK port for < 3.x we did something like this: > > > > signalMask = jmpbuf[0]._sjb[6]; > > > > This no longer works now that we support >32 signals. I

Re: FreeBSD random I/O performance issues

On Wed, 5 Apr 19100, Matthew Dillon wrote: > :performance -- innd was still unresponsive during the time that the > :random history database files needed updating for somewhere around > :10 to 15 seconds when handling a full feed. > > The innd problem is a different issue entirely, one relat

Vinum breakage (was: 2nd call for reviews and tests: buf->bio patch)

On Tuesday, 4 April 2000 at 15:31:00 +0200, Søren Schmidt wrote: > It seems Brad Knowles wrote: >> >> Like I said in a previous message, Poul broke vinum (among other >> things) under 4.0-STABLE, and this needs to be fixed ASAP. If Poul >> had kept his changes unique to -CURRENT, then 4.0-S

Vinum breakage (was: 2nd call for reviews and tests: buf->bio patch)

On Tuesday, 4 April 2000 at 15:33:43 +0200, Poul-Henning Kamp wrote: > In message , Brad Knowles writes: >> At 8:23 AM +0200 2000/4/4, Jeroen Ruigrok/Asmodai wrote: >> >>> Like I said in another mail, this is CURRENT, things are >>> expected to br

Re: Vinum breakage (was: 2nd call for reviews and tests: buf->bio patch)

In message <[EMAIL PROTECTED]>, Greg Lehey writes: >> >> The problem in vinum/releng4 is the problem greg has been blaming >> on CAM since at least FreeBSDcon and indications seems to be that >> it is actually a malloc/free gottcha in vinum. > >No, this is not correct. The problem you're talking