Date: Tue, 13 Mar 2001 10:47:11 -0500 From: Peter Radcliffe <pir@pir.net> To: freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Message-ID: <20010313104711.B6592@pir.net> In-Reply-To: <3AADBAB8.36039542@babbleon.org>; from bts@babbleon.org on Tue, Mar 13, 2001 at 01:14:16AM -0500 References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org>
next in thread | previous in thread | raw e-mail | index | archive | help
The Babbler <bts@babbleon.org> probably said: > Perhaps all PCMCIA support under FreeBSD should be considered > quasi-experimental or something, but I'm deliberately avoiding using > anything but stock 4.2-RELEASSE in order to (hopefully) get maximum > stability. PCMCIA under freebsd seems far more stable than Linux PCMCIA support when _correctly_ _configured_. I've helped dozens of people get wavelan support working at conferences and getting it as stable with Linux requires the exact correct versions (and the only way to find them is to test) of half a dozen things ... > For example, it froze both last night and tonight while I was trying to > get vmware networking set up properly. vmware messes with things at a pretty low level and isn't designed for FreeBSD. It's going to cause problems. Having said that, once I got it set up properly (you did read the FreeBSD readme, didn't you ?) it hasn't crashed the host OS on my machine in a long time. > But it's not just that; my gateway/firewall just locks up with the > PCMCIA light stuck on about every couple of weeks. I would assume you have a misconfiguration or a hardware problem. I've had freebsd boxes doing routing/filtering/pcmcia up for _months_ with no problems. > And making it all especially bad is that I've FreeBSD lose file contents > (revert to zero length) after rebooting, even on files that hadn't > actually been updated any time close to when the lockup occured. Never seen that in my last few years of freebsd use. > (In fairness, I should note that Linux PCMCIA support appears to be > superior to everybody else's. It's certainly superior to Windows as > well as FreeBSD.) Can't disagree strongly enough. > Anyway, any suggestions for determining the source of such crashes. For > the fully-configured system, since the lockups happen only every couple > of weeks, it's not really feasible to leave kernel tracing permanently > on or anything like that. And these "crashes" of which I speak are > system lockups, not kernel panics--there's no recovery possible becuase > it locks up tight as a drum and I have to power off. Nor is this just > an X display problem, for it also happens to my gateway/firewall, which > doesn't even have X installed. > > How would you deal with such problems? Double and triple check for any irq/memory problems and then start using DDB and DIAGNOSTIC. It's the only sane way to debug hard hangs. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010313104711.B6592>