Date: Fri, 22 Dec 2000 00:00:49 -0800 From: "Brian O'Shea" <boshea@ricochet.net> To: Bernhard Valenti <bernhard.valenti@gmx.net> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: weird problem with athlon on -stable Message-ID: <20001222000049.Q24087@beastie.localdomain> In-Reply-To: <000501c06bff$c2d279a0$0200000a@cipher>; from Bernhard Valenti on Fri, Dec 22, 2000 at 02:12:59AM -0800 References: <000501c06bff$c2d279a0$0200000a@cipher>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 22, 2000 at 02:12:59AM -0800, Bernhard Valenti wrote: > hi, > > i'm experiencing some weird problem... > > when 4.2 was in beta i setup a athlon 500(asus board), and copied the > freebsd installation from my primary machine ( dual celeron ) to the athlons > disk. i had to build a single CPU kernel on the athlon cause the smp kernel > did abort during boot. so i went into single user(with kernel.GENERIC), > built a new kernel, and booted it. 2-3 seconds after printing the login > prompt, the box crashed *every*( i tried ~10 times) time i booted > normally(no unusual message during boot,no panic, but it stoped responding > to the keyboard/network). but it worked perfectly fine in single user mode.. > i spent ~2 hours in single user mode with manually started services and > network. i think i even ran a make world.. anyway.. i couldnt find the > problem so i went and installed 4.1.1-release from cd. everything worked > fine after that, even after updating to 4.2 > > today, i bought a athlon 1Ghz+abit board(different chipset then the asus), > replaced the dual celeron with it, and have exactly the same problem. is a > world built on a smp incompatible with single cpu systems !?(i doubt that) > maybe its that i choose i686 as cpu type, but why does "single user" work > fine then? > > is there something i'm missing ? i'd be glad to hear any ideas.. In addition to starting services manually in single user mode, did you set any sysctl's that might also get set in the rc scripts? For example, if you have gateway_enable="YES" in rc.conf, then the command "sysctl -w net.inet.ip.forwarding=1" is run in rc.network. You might grep for "sysctl" in /etc/rc* to see if there are any sysctl's that need checking. Also, are there any kernel modules that get loaded as a result of your rc.conf settings? Good luck, -brian > > bernhard > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Brian O'Shea boshea@ricochet.net 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?20001222000049.Q24087>