Date: Thu, 11 Nov 1999 10:52:10 -0600 (CST) From: Wayne M Barnes <stabilizer@klentaq.com> To: mi@kot.ne.mediaone.net (Mikhail Teterin) Cc: freebsd-stable@freebsd.org (FreeBSD Stable) Subject: Re: ethernet hard or soft failure Message-ID: <199911111652.KAA02871@klentaq.com> In-Reply-To: <199911110616.BAA63189@rtfm.newton> from Mikhail Teterin at "Nov 11, 1999 1:16:33 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Dear M I, When your cron job runs, everyone will be knocked off their jobs, no? Or is it harmless, and they just get a 1 sec. blip, without their xterms or sessions dying? How could I run your line of commands only when the link is down? By the way, I should have pointed out that my cron job captured a crash (see log at http://barnes1.wustl.edu/wayne/NMB): > 303/320 mbufs in use: > 244 mbufs allocated to data > 59 mbufs allocated to packet headers > 14/62/4096 mbuf clusters in use (current/peak/max) > 164 Kbytes allocated to network (40% in use) Tue Nov 9 12:45:00 CST 1999 LOCKUP OF INTERNET CONNECTON OCCURS -- REBOOT AT 12:47 I was hoping the many mbufs in use was a clue, although the available mbuf clusters do not seem to be near saturated. 15 minute time points are not very illuminating. Wayne M Barnes stabilizer@klentaq.com > I continue having my ISA ep-card lock up every so often (under heavy > traffic in both directions). My workaround is a cron-job: > > ifconfig ep0 down; sleep 1; ifconfig ep0 up > > -mi > > Wayne M Barnes once stated: > > =Dear Bill > = > = :( > = > = Our network guru has looked for rogue cards or laptops on our > =dept. network and found none. > = > = I have increased maxusers to 256, and have tried NMBCLUSTERS at 1024, > =4096, (and currently 16K; too recent for results, yet.) > = > = I have increased my bpf units to 24. > = > = I have set up a cron job to run every 15 minutes and log the > =DIFF against the last time, then DATE, to > =http://barnes1.wustl.edu/wayne/NMB > =[Here is testNMB* which crontab runs every 15 minutes: > =netstat -m | diff NMB.boring - | grep ">" >> ~wayne/NMB.log > =date >> ~wayne/NMB.log > =netstat -m > ~wayne/NMB.boring > =] > = > = No luck so far. Every weekday between 1 and 4 or so, my NIC card stops > =transmitting across the network. The console is stays up, but no pings > =can get out, nor can anyone log in from anywhere else. > = > = Our network guy JJ found a recommendation on "Deja News" (I don't know > =where that is) to increase kern.vm.kmem.size as the next resort. I > =don't know what a the current value is, or what a reasonable next level > =is. I can't tell by inspecting source mbuf.h, either. It's well > =concealed, if it's there. > = > =Wayne M Barnes stabilizer@klentaq.com > = > => Wayne, I'm curious to see if you ever got your ethernet issues resolved. > => I'm currently having VERY similar issues with a -CURRENT box. My NIC's > => have been 3com 3c905 and generic DEC 2104x chipset cards, FYI. So far for > => me the only thing that's helped (hasn't fixed it, but helped) has been to > => disable my screensaver in X. > => > => --Bill > => > => > = > = > = > =To Unsubscribe: send mail to majordomo@FreeBSD.org > =with "unsubscribe freebsd-stable" in the body of the message > = > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911111652.KAA02871>