Date: Wed, 23 Aug 2000 11:45:14 +0200 From: Didier Derny <didier@omnix.net> To: John Indra <john@indocyber.com>, questions@freebsd.org Subject: Re: FreeBSD locks up frequently... Message-ID: <00082311504900.48705@idefix.omnix.net> In-Reply-To: <20000823114643.A43770@indocyber.com> References: <20000823114643.A43770@indocyber.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I've had nightmare with the 3com board using the xl0 driver I dont know if the problem comes from the driver or the board but our firewall crashed several a day under average load (average uptime around 6-8 hours) I finally replaced the 3com 3C905-TX board by the only one I had at that moment a PCI NE2000 clone and now it works like a charm last reboot July 2th 2000 (just after having removed the 3com boards) perhaps that you can try that if you have another board (not 3com) [check in you log for "xl0 timeout"] -- Didier Derny didier@omnix.net Le Mer, 23 aoû 2000, John Indra a écrit : > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Dear FreeBSD users... > > First of all, I feel obliged to explain my subject line. This mail isn't > about mocking (or anything similar to that) FreeBSD cause I really love > FreeBSD. This mail is purely a means for me to get help on how to remedy and > probably solve my problems. > > For some background info: I have a Compaq Deskpro EP system with Pentium III > 500 MHz, 256 SDRAM, 10 gigs Quantum harddrive, 3Com Boomerang NIC. This > system is quite new. When I first had this machine, I installed FreeBSD 3.4 > on it. It served as a web server, gateway, firewall, mail server and proxy. > The system is VERY stable. Days without any single unintentional reboots. > > After that, I formatted my harddrive (intentionally) to install FreeBSD > 4.0-20000714 directly from ftp://releng4.freebsd.org. Installation went > perfect, I have a new 4.0-STABLE system served as web server, gateway, > firewall, mail server, and proxy, the same job that I've given FreeBSD 3.4 > before. Then... the first weird occation happened. One day, when I arrived > at my office first thing in the morning, I found my system locked up! I > could switch to any virtual terminals (v0 to v7) but I couldn't login! When > I typed my username at login prompt, it didn't echo. I was sure that scroll > lock was off, and I make sure that Ctrl+S was not active. My harddrive LED > light on all the time and I heard my harddrive spinning. Ctrl+Alt+Del didn't > even respond thus all I could do was to power down the system. Sigh... I > compiled my kernel without any odd options, just to provide firewalling and > my hardware, that's it! I have a blank /etc/make.conf so I have a kernel > compiled without any compiler optimization settings. The system experienced > the same lock up every 3 days thus I couldn't have more than 3 days of > uptime. > > One day, I formatted my harddrive again (once again, intentionally), > installed FreeBSD 4.1-RELEASE which I got from burning the ISO, cvsup to > 4.1-STABLE. All went perfectly. Here's the output of uname: > [john@maverick john]$ uname -a > FreeBSD maverick.indocyber.com 4.1-STABLE FreeBSD 4.1-STABLE #0: Sun Aug 20 > 10:24:41 JAVT 2000 > root@maverick.indocyber.com:/usr/src/sys/compile/MAVERICK i386 > > I compiled my kernel with COPTFLAGS= -O -pipe. Then unexpectedly, when I > arrived ay the office this morning, I found it locked up like before. > Sigh... I tried to track what's happening from all the logs > (/var/log/messages, /var/log/httpd/error.log, /var/log/qmail/current, and > all relevant logs I have) but get nothing from all the log files. > > I hardly believe that this is a hardware problem. When I'm in the office, on > daily activities (Apache, Squid, MySQL, qmail, ipfw all running), I > frequently run gcc to compile a LOT of apps (most of them are compiling the > ports) concurrently. The machine never core dumps, never segfault, never get > any signal 6, 11, or 12, it just rocks solid, as solid as can be. FYI For > firewalling rules, I used /etc/rc.firewall simple configuration. But why > doesn't it have all days without unintentional reboots just like before, > when I have a FreeBSD 3.4? How can I really trace what has made my machine > to lock up? Is it some kind of DoS? Is my machine attacked from the > Internet? Cause after the lock up, it just won't even responds to pings. > After I rebooted the machine, fsck never gets a lot of home cleaning to do. > I even don't lose any files at all. This indicated that maybe the system > wasn't busy at all. > > Attached is my kernel config. I hope all of you guys on this mailing list > can enlighten me on this problem. Thanks a lot... > > Regards, > John Indra > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.2 (FreeBSD) > Comment: Be the best! > > iD8DBQE5o1cmxcp0HIxafmQRAoQXAJ9dCmF2wNSQFvFeTfdW9ZSNh2YhfgCeJ4Dy > x3mGc+sririydNM6Egqg+vE= > =3uwJ > -----END PGP SIGNATURE----- > ---------------------------------------- Content-Type: text/plain; name="unnamed" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- -- -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00082311504900.48705>