Re: kernel panic on boot with 4G RAM

Steve Shorter wrote: You really need to change the allocation of swap page descriptors in /sys/i386/machdep.c (among other things). Is this a trivial change? I don't know much about FreeBSD kernel internals but can edit source with some guidance OR can these changes be effected

Re: huge MFREE() macro?

On Tue, Jan 01, 2002 at 10:16:25PM -0800, Matthew Dillon wrote: I noticed a bunch of routines use MFREE() instead of m_free() (which just calls MFREE()). MFREE() is a huge macro. textdata bss dec hex filename 1986399 252380 145840 2384619 2462eb kernel text

Re: kernel panic on boot with 4G RAM

hi, happy 2002 to all!, As I said before, look at the handbook, though it is somewhat incomplete. Don't you think this should be documented properly in the handbook, in the 'kernel config' chapter? Cause if thats so, I can advice 'darklogik' who is currently rewriting the 'kernel config'

Magic number 100 in /sys/kern/kern_fork.c

I've review /sys/kern/kern_fork.c file and have a question why the room of 100 process numbers is hardcoded in the source? I think that if such room is needed, it must be defined somewhere in headers, isn't it. Can someone explain me more the idea about that room? -- Dimitar Peikov Programmer

Re: Running out of bufferspace

I think that fact that you still see the problem hours later indicates that some internal device doesnt have a process to revisit the queue once you've filled it. You can do the same thing fairly easily with a trafic generator that uses raw socketscheck the ifp-if_snd.ifq_len for the device

Re: Running out of bufferspace

Rogier R. Mulhuijzen wrote: Well turns out my problem was two-fold. I'm indeed running out of ifp-if_snd on my xl0 interface, but I was also running out of space on my vmnet1 interface, but since I don't always run vmware it wasn't being emptied. Guess mount_smbfs needs a little patch.. I'll

Re: Re: userland program panics freebsd 4.3

FYI: just finished up a scan of a network with 1200 hosts and now panic's I did not install the second set of patches (or third) but only that first set ti utils.c that prevented the /procpid% scanning. Not only doesn't it crash, but it seems to be faster. It is a LOT faster than nessus 1.09

Re: The Hurd

On Tuesday, January 1, 2002, at 12:31 PM, Miguel Mendez wrote: On Tuesday 01 January 2002 20:14, Rafter Man wrote: So my question is: Will FreeBSD take a good look at the Hurd? I tried the Hurd in 1999 and wasn't very impressed, just downloaded the H2 ISO but haven't tried it yet. The

Interview Published

Kerneltrap did a good interview of me a week or so ago (one of several interviews they are doing) and just published it: http://kerneltrap.com/article.php?sid=459 -Matt Matthew Dillon

Re: Magic number 100 in /sys/kern/kern_fork.c

Dimitar Peikov wrote: I've review /sys/kern/kern_fork.c file and have a question why the room of 100 process numbers is hardcoded in the source? I think that if such room is needed, it must be defined somewhere in headers, isn't it. Can someone explain me more the idea about that room?

Patch for SIS630ET embedded NIC

I would appreciate if people that have SIS Ethernet controllers to test out this patch. I added support for the 630ET based on the changes in the Linux driver. It seems to work fine. I'd like to get some yes it doesn't break anything or heh, now my SIS Ethernet controller works now comments

Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers

Hey Søren, Do you have any idea what to do with the problems I am experiencing with the Intel-series chipset? Regards Kristian - Original Message - From: SXren Schmidt [EMAIL PROTECTED] To: Nils Holland [EMAIL PROTECTED] Cc: Matthew Dillon [EMAIL PROTECTED]; Mike Silbersack [EMAIL

Interrupt Latency / FreeBSD Realtime ?

Hi Everybody, I'm looking for information about what you can expect in regarding to hardware interrupt latency in FreeBSD Assuming that you run without swap, and turn off whatever services that would otherwise complicate things, do anybody have any idea how long you can expect the worst

more observations on nullfs filesystem

[replies sent directly to me may timeout and bounce, since I'm not online as often as I should be, but I'll check the list archives] Guten Morgen This was tried under -current (and probably -stable too) Should a nullfs mount handle options the way that one would expect from a normal

Junior FS hacker task (more observations on nullfs filesystem)

BOUWSMA Beery wrote: This was tried under -current (and probably -stable too) Should a nullfs mount handle options the way that one would expect from a normal filesystem mount? In particular, I have a read-only nullfs mount, but accesses to that read-only filesystem result in the atime

Solaris /usr/proc/bin/pstack functionality?

See the post below. Is there a way to get at this information in FreeBSD? Thanks, Jos - Forwarded message from Justin Erenkrantz [EMAIL PROTECTED] - Date: Wed, 2 Jan 2002 14:02:24 -0800 From: Justin Erenkrantz [EMAIL PROTECTED] To: Aaron Bannert [EMAIL PROTECTED], [EMAIL PROTECTED]

Re: Solaris /usr/proc/bin/pstack functionality?

: :See the post below. Is there a way to get at this information in FreeBSD? : :Thanks, :Jos Well, ktrace -i will certainly follow children. In fact, ktrace can attach to all current children (-d) of a process as well as attach to new children. Yahoo found a few bugs in ktrace by

Re: Solaris /usr/proc/bin/pstack functionality?

On Wed, Jan 02, 2002 at 11:34:59PM -0800, Matthew Dillon wrote: Well, ktrace -i will certainly follow children. In fact, ktrace can attach to all current children (-d) of a process as well as attach to new children. Yahoo found a few bugs in ktrace by running 'ktrace -i -d