Date: Wed, 30 Apr 2003 15:31:30 -0700 From: Kent Stewart <kstewart@owt.com> To: Glenn Johnson <gjohnson@srrc.ars.usda.gov>, Jens Schweikhardt <schweikh@schweikhardt.net> Cc: current@freebsd.org Subject: Re: kernel crashes and portupgrade Message-ID: <200304301531.30642.kstewart@owt.com> In-Reply-To: <20030430220804.GA35025@node1.cluster.srrc.usda.gov> References: <20030430174441.GA22732@node1.cluster.srrc.usda.gov> <20030430194742.GA20357@schweikhardt.net> <20030430220804.GA35025@node1.cluster.srrc.usda.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 30 April 2003 03:08 pm, Glenn Johnson wrote: > On Wed, Apr 30, 2003 at 09:47:42PM +0200, Jens Schweikhardt wrote: > > On Wed, Apr 30, 2003 at 12:44:41PM -0500, Glenn Johnson wrote: # > > Does any one know if portupgrade has a problem or is it something > > in # -current that it is interacting with? > > > > I get the "panic: freeing free block" (that other people reported) > > during "make install" in a number of ports under /usr/ports on a > > freshly installed system. I'm not using portupgrade at all, so it > > is not portupgrade specific. It's rather something that portupgrade > > runs doing its job. Could be heavy disk I/O, lots of context > > switches or whatever. > > Hmm, I know at least two of the panics I had were during the install > stage of ports. One was perl, the other was XFree86-4-Server. > > I have not had a problem with an intallworld though. I just had one running /usr/libexec/locate.updatedb from kde as root. I cvsuped, updated the system, and tried it from the command line and had no problem. I am just letting it sit with kde running and setiathome. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200304301531.30642.kstewart>