Date: Mon, 2 Jul 2001 16:06:24 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: John Reynolds <jreynold@sedona.ch.intel.com>, stable@FreeBSD.ORG Cc: mhall@nms.fnc.fujitsu.com, ohartman@klima.physik.uni-mainz.de Subject: Re: Hard lockups since cvsup'ing Jul 1st. Help! Message-ID: <p05101009b766836061da@[128.113.24.47]> In-Reply-To: <15168.45812.871475.349798@hip186.ch.intel.com> References: <Pine.GSO.4.10.10107021013040.3738-100000@firstbase.nms.fnc.fujitsu.com> <15168.45812.871475.349798@hip186.ch.intel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:44 AM -0700 7/2/01, John Reynolds~ wrote: >[ On Monday, July 2, Matthew Hall wrote: ] > > I don't know why my system is locking up so completely - >> I've never had FreeBSD do this to me. :-) >> >> If there's any more information I can provide, please let >> me know. Right now I'm cvsup'ing back to June 1st (to be > >I don't have any information except to say "me too"! Perhaps it would be helpful for both of you to include the output of 'dmesg' (or just take the contents of /var/run/dmesg.boot) when you get a chance. It would also be interesting to know if you'd have better luck with a kernel that did not include multi-processor support. From what little I can guess, it seems that everyone having this kind of freeze-up problem is running a multi-processor machine. That is just a wild-assed guess on my part, though. I personally won't be able to help much, but I'll be interested in the outcome as I also have dual-processor machine. I just sync'ed with stable on June 26th, and I expected to do that again this week, but maybe I'll hold off for a few days... -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu 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?p05101009b766836061da>