*BSD News Article 26928


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!foxhound.dsto.gov.au!fang.dsto.gov.au!yoyo.aarnet.edu.au!news.adelaide.edu.au!basser.cs.su.oz.au!news.cs.su.oz.au!metro!dmssyd.syd.dms.CSIRO.AU!dmsperth.per.dms.CSIRO.AU!uniwa!harbinger.cc.monash.edu.au!msuinfo!uwm.edu!cs.utexas.edu!howland.reston.ans.net!sol.ctr.columbia.edu!usenet.ucs.indiana.edu!pegasus2.astro.indiana.edu!sdslavin
From: sdslavin@pegasus2.astro.indiana.edu (Shawn Slavin)
Subject: Info regarding kernal compiles
Message-ID: <CKnMDu.7sy@usenet.ucs.indiana.edu>
Sender: news@usenet.ucs.indiana.edu (USENET News System)
Nntp-Posting-Host: pegasus2.astro.indiana.edu
Organization: Indiana University Astronomy Department
Date: Thu, 3 Feb 1994 15:15:30 GMT
Lines: 22


Hi there!  I posted a while back about trouble with panic trap messages on soft
reboots of my FreeBSD-1.0 system (i486/50 DX2).  I had another problem with my
keyboard, and both seemed to be fixed by switching to the SYSCONS
configuration, rather than GENERICAH.

Well, I tried to compile it again the other day, and back came the panic trap
messages on soft reboots.  I then realized that I had used the -m486 -O2
options with gcc, and not the default -O.  So, I recompiled it with the -m486
-O2, and it works great.

So, I don't see why the -O2 option has anything to do with this.  BUT, is there
something in the kernal code that will be significantly affected by the -m486
option?  When I was getting the problem on reboots, that was the only problem.
Other than that the system worked fine.  So, the question is:  does the 486
switch change the way my system is reset on reboots?  BTW, hard reboots have
never been a problem, except for fsck being upset when my system didn't close
out the filesystems on the soft reboot.

Hmmm.  Very curious.

Shawn