If both swap partitions are enabled then "make -k buildworld" crashes the system with ABSOLUTE CONSISTENCY. Since this behavior has been around for about a year (???) I assume my system configuration must be unusual ... or surely this would have been discovered and fixed earlier. Several months ago a bug was found with dual swap partitions. It involved some cross-partition alignment problem. When that bug was fixed most of my crashes disappeared. Except for this problem. But "make -k buildworld" continued to crash the system. Fix: The workaround is to comment out the second swap partition in fstab. How-To-Repeat: 1) Edit fstab to use 2 separate swap partitions on 2 separate drives. 2) Run with softupdates. 3) Run "make -k buildworld" Note 1: I don't know if the second partition *must* be on a different drive to cause the crash, only that my system is set up that way. Note 2: I don't know if softupdates has anything to do with this problem.
State Changed From-To: open->feedback Do you still experience this problem? Providing a stack traceback (see the handbook section on kernel debugging) would go a long way towards identifying the possible problem in FreeBSD
State Changed From-To: feedback->closed Feedback timeout
Adding to audit trail ----- Forwarded message from Daniel Ortmann <ortmann@sparc.isl.net> ----- Delivered-To: kkenn@localhost.obsecurity.org Date: Thu, 02 Aug 2001 00:20:28 -0500 From: Daniel Ortmann <ortmann@sparc.isl.net> Subject: Re: kern/17067: consistent "make -k buildworld" crash with 2 swap partitions In-reply-to: kris@FreeBSD.org's message of "Thu, 24 May 2001 12:39:22 -0700 (PDT)" To: kris@FreeBSD.org X-Mailer: Gnus v5.7/Emacs 20.7 Delivered-to: kris@freebsd.org My problem was solved by taking the side off of my computer and aiming a LARGE fan into it. It was evidentally a heat problem that had NOTHING to do with FreeBSD. kris@FreeBSD.org writes: > Synopsis: consistent "make -k buildworld" crash with 2 swap partitions > > State-Changed-From-To: open->feedback > State-Changed-By: kris > State-Changed-When: Thu May 24 12:38:21 PDT 2001 > State-Changed-Why: > Do you still experience this problem? Providing a stack traceback > (see the handbook section on kernel debugging) would go a long way > towards identifying the possible problem in FreeBSD > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17067 > > -- Daniel Ortmann IBM Circuit Technology 2414 30 av NW, #D E315, bldg 040-2 Rochester, MN 55901 3605 Hwy 52 N 507.288.7732 (h) 507.253.6795 (w) ortmann@isl.net ortmann@us.ibm.com "The answers are so simple and we all know where to look, but it's easier just to avoid the question." -- Kansas ----- End forwarded message -----