Date: Mon, 05 Mar 2001 18:11:03 -0500 From: Gary Jackson <bargle@umiacs.umd.edu> To: hackers@freebsd.org Subject: Strange, possibly network-related, crashes Message-ID: <200103052311.SAA25244@leviathan.umiacs.umd.edu>
next in thread | raw e-mail | index | archive | help
I'm having some problems with a 4.2-Release NAT box. If I leave it up and connected to the outside world for a couple of days, it starts crashing with a page not found type of error (I'm sorry I don't have the full text of the error - it finishes crashing and reboots before I can read the error from the screen). It will continue to come up, then crash, repeatedly, until I turn it off or disconnect it from the outside world. This has happened twice since I set the box up, and it takes two to three days for the fun to begin. I had 4.0 installed on the same machine, and I never had any problems with it: it would stay up for months at a time, with little intervention on my part. The problems started when I made the following changes to the machine: 1. I upgraded the OS to 4.2 2. I installed an 802.11 PCI card The machine is currently configured with two intel FE network cards (using the fxp device), and a Cisco AiroNet 340 802.11 card (using the an device). If someone has any idea as to what this might be, that would be cool if you could tell me. However, I don't expect that kind of luck. I'm interested in information on how to get the kernel to drop to the debugger when it wrecks like that, so I can fix the problem myself, or write a more useful query to this list. -- Gary Jackson bargle@umiacs.umd.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103052311.SAA25244>