Date: Mon, 5 May 2003 11:46:39 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: "Jacques A. Vidrine" <nectar@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: Today's -CURRENT, vinum damage Message-ID: <Pine.NEB.3.96L.1030505114500.24722W-100000@fledge.watson.org> In-Reply-To: <20030505153018.GA28343@hellblazer.celabo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 May 2003, Jacques A. Vidrine wrote: > I cvsup'd this morning, and built/installed a new -CURRENT. (I was > previously running circa morning April 29.) > > I was greeted by > WARNING: Expected rawoffset 63, found 0 > which seemed harmless enough (I only mention it in passing). > > When attempting to start Vinum, the `vinum' process became stuck & > unkillable in biord. Has anyone else seen this? It might be useful (and perhaps even instructive) to generate a stack trace for that kernel process. You can do this by breaking into DDB and using the trace command on the specific pid (i.e., trace 9). > I loaded my old kernel and I am trying to recover by rebuilding a > morning of 2003/05/04 world. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1030505114500.24722W-100000>