RE: network got stuck during high nfs-load

I'm now getting a similar thing with the latest -STABLE build. NFS isn't involved, but this is on a heavily used webserver. NIC is a 3COM 3C905b. Ifconfig up and down works for about 5 packets, that's it. netstat was showing either errors inbound, or absolutely nothing. This happens about once

3c905B stops responding during ifconfig alias

This happens in -current and -stable. Machine: CPU: Pentium II (quarter-micron) (350.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 402653184 (393216K bytes) config> quit avail memory = 388808704 (379696K bytes ... xl0: <3Com 3c905B Fas

Tracking a Fatal Double Fault

Can someone please give me a short guide on how to track down a fatal double fault? System is 3.0-19990205-STABLE, and I've written down the fault info. Thanks, -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-curren

RE: Tracking a Fatal Double Fault

The machine is running a custom kernel, but nothing very unusual. My instinct is that it may be related to something with the 3c905B 3COM cards that I reported earlier, I'm trying with Intel EtherExpresses right now and getting no fault problems. The double-fault does not occur consistently, unf

RE: Tracking a Fatal Double Fault

So a double-fault is always a kernel stack problem? I find it suspicious that this same machine also had trouble with the 3c905B flaking out -- dropping packets during an ifconfig alias, and sometimes never reactivating the interface according to what tcpdump shows. The 3c905B problem repeates it

RE: 3c905B stops responding during ifconfig alias

Bill, Your patch worked perfectly. THANK YOU! By the way, I'd be happy to fedex a 3c905B to you for your use in testing these sorts of things if that would be helpful. We have a fairly large commitment to this card now (40+) and I'd do this happily to facilitate continuing performance enhanceme

panics & deciphering VMSTAT output

I've been trying to track down a regular, but not manually reproducible crash in 3.0-BETA (19990205). I can't get a crashdump due to a DSCHECK negative number bug. I think my swap space of 3+GB is too large for it. So, I've been having it send me the output of vmstat -m every 15 minutes to try t

RE: Problems in VM structure ?

I'm seeing different responses depending on hardware. On regular Pentium 166 machines, I almost NEVER get a panic. On brand-new Pentium II 350s, I get a panic every 6-9 hours. This happens when both kernels are configured the same for maxusers. It happens when both machines are under the same l

RE: RE: Problems in VM structure ?

> -Original Message- > From: Matthew Dillon [mailto:dil...@apollo.backplane.com] > :What's the chance that our kernel adaptations for PIIs > :is partly at fault? > : > :-Troy Cobb > : Circle Net, Inc. > : http://www.circle.net > > With what config? Have you tried

RE: Problems in VM structure ?

I've adjusted MAXUSERS to 128 on my heavily loaded PIIs and the crashes have not re-occurred for 24 hours now. (Had to adjust NMBCLUSTERS up, though) The panics were happening every 5-8 hours like clockwork prior to this. I believe that these crashes are caused by heavy network traffic, not heavy