From owner-freebsd-current Sun May 17 09:39:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08366 for freebsd-current-outgoing; Sun, 17 May 1998 09:39:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (tc-19.acadiau.ca [131.162.2.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08361 for ; Sun, 17 May 1998 09:39:37 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id NAA03745; Sun, 17 May 1998 13:39:39 -0300 (ADT) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 17 May 1998 13:39:39 -0300 (ADT) From: The Hermit Hacker To: "Justin T. Gibbs" cc: current@FreeBSD.ORG Subject: Re: Bad shutdown... In-Reply-To: <199805170713.BAA01671@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 May 1998, Justin T. Gibbs wrote: > In article you wrote: > > > > This is based on a 0515 kernel, with the CAM snapshot applied to it... > > > > hub# halt > > > > syncing disks... 3 3 done > > panic: lockmgr: pid 318, not exclusive lock holder 1 unlocking > > > > dumping to dev 20401, offset 262144 > > dump Aborting dump due to I/O error. status == 0x200, scsi status == 0x0 > > i/o error > > Automatic reboot in 15 seconds - press a key on the console to abort > > > I don't know about the SMP problem Well, that sheds some light on things... What SMP problem? This is a UP system :( Hell, its not even an SMP motherboard with only one CPU...:( Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message