Vallo Kallaste wrote: > On Sat, Feb 22, 2003 at 11:43:01AM -0500, "Paul A. Howes" > <[EMAIL PROTECTED]> wrote: > > I am receiving some strange errors during a buildworld of 5.0-RELEASE-p2 > > from 5.0-RELEASE-p1. The location of where the failure varies, but the > > program that causes the failure is the same every time: "as". > > > > The errors are a variety of signal 10 and signal 4. I do find an > > "as.core" file under /usr/obj, but as is stripped, so there are no > > debugging symbols or listing that I can provide. > > > > The strange thing is that I have been able to successfully build > > XFree86, KDE, and many other ports on this system. I followed the > > 4.x-to-5.0 upgrade directions to the letter about a month ago, and have > > had no major problems before this. > > > > Any help would be greatly appreciated! > > As John Hay suggested, add DISABLE_PSE and DISABLE_PG_G to your > kernel configuration and rebuild/install kernel. I was having > _exactly_ same behaviour; at the beginning of test runs to narrow > the problem a bit I did _large_ ports builds, which ran for 1,5 > days.. flawlessly, as you had seen. Then changed test method to > parallel (make -j4) buildworld and the problem occasionally appeared > from nowhere again. The flags mentioned before will work, as I > haven't had any problems after enabling them (months of time now).
I thought this was the default in 5.x GENERIC; has someone turned these options off in the default config?!? I certainly haven't seen changes to locore.s, pmap.c, and machdep.c that would fix the problem by working around the CPU bug. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
