Date: Mon, 2 Jul 2001 10:44:20 -0700 From: John Reynolds~ <jreynold@sedona.ch.intel.com> To: stable@freebsd.org Cc: mhall@nms.fnc.fujitsu.com Subject: Re: Hard lockups since cvsup'ing Jul 1st. Help! Message-ID: <15168.45812.871475.349798@hip186.ch.intel.com> References: <Pine.GSO.4.10.10107021013040.3738-100000@firstbase.nms.fnc.fujitsu.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[ On Monday, July 2, Matthew Hall wrote: ] > > The kernel/world I built on Sunday night seem to lock my > system up hard after 3-5 minutes. > > My system > > Dual PIII 650's > AMI MegaRAID 1400 > 256mb ram > 2 linksys 10/100 (version 4.0's) > > I was tracking RELENG_4 ... the last known good kernel I > had was from about the 10th of June. Can anyone tell me > if anything went in from then till now that might effect > my raid controller, ethernet cards, linux emulation, my > u160 disks, etc? > > 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"! I was CVSup'ing and trying to sync all my machines to the latest -STABLE on Friday night. As I usually do, I installed just the kernel and rebooted to see if things were "ok". Well, they weren't. Hard lock, no keyboard activity could not telnet in, could not ping, couldn't do anything. Word to the wise--as long as you have physical access to the machine, ALWAYS test the new kernel before proceeding with installworld! There are these odd times when something will be wrong and it's MUCH easier to stop an "upgrade" cycle after installkernel versus backing out everything after installworld! I reverted back to "kernel.old" and the machine was solid again, so I kindly just "backed out" of that upgrade cycle restoring the kernel and /modules. I figured it was just a fluke or some wierd thing so I haven't reported it until now, but there certainly is something that has gone deathly south here. My machine is an Abit BP6 dual Celeron board with BX chipset and two fxp NICs. Been rock solid for years and still rock solid with "kernel.old" from the beginning part of June (sorry no exact date). After I make sure that my old kernel still worked, I tried booting into the new kernel to run some "tops" and "vmstat -i" and stuff, but the machine locked up too soon for me to type anything (just after logging into the console, BOOM). I've since CVS'uped from Sunday and just manually copied a new kernel to / but didn't have time to test it out. Does anybody have any clues as to how we go about tracking this down (aside from the binary search through all the commits from the "last known good kernel")? I'm going to try to CVSup again and also build a uni-processor kernel. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, (space for rent, cheap!) | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ------- end of forwarded message ------- -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, (space for rent, cheap!) | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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?15168.45812.871475.349798>