From owner-freebsd-hackers Sat Aug 24 0:16:57 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1AF637B400; Sat, 24 Aug 2002 00:16:54 -0700 (PDT) Received: from perimeter.co.za (obelix.perimeter.co.za [209.212.102.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75F9243E6A; Sat, 24 Aug 2002 00:16:51 -0700 (PDT) (envelope-from bsd@perimeter.co.za) Received: from asterix (ndf-dial-196-30-125-95.mweb.co.za [196.30.125.95]) (AUTH: LOGIN bsd@perimeter.co.za) by perimeter.co.za with esmtp; Sat, 24 Aug 2002 09:16:45 +0200 Message-ID: <029901c24b3e$3e8d5320$0200000a@perimeter.co.za> From: "Patrick O'Reilly" To: "Greg 'groggy' Lehey" Cc: "Andrew Gallatin" , "Julian Elischer" , ivan_alb@agava.com, freebsd-hackers@freebsd.org References: <15718.14981.573727.965999@grasshopper.cs.duke.edu> <054301c24aae$6b99ed50$b50d030a@PATRICK> <3D6642A2.3040102@agava.com> <15718.17268.289160.923598@grasshopper.cs.duke.edu> <3D664415.3040908@agava.com> <15718.17582.370143.817484@grasshopper.cs.duke.edu> <20020824044646.GA87563@wantadilla.lemis.com> <024d01c24b3b$b7f90860$0200000a@perimeter.co.za> <20020824070321.GG87563@wantadilla.lemis.com> Subject: Re: Kernel Panic = System crash 8 times in 4 days Date: Sat, 24 Aug 2002 09:16:58 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Greg 'groggy' Lehey" > Hmm, I haven't heard much about that. I've got the manual - but that's about as much as I know. :) > Correct. I don't recommend putting the Vinum module into the kernel. > The mods to vinumrequest.c relate to every request. I'm not sure that > they're relevant to the Vinum crashes, but it's exactly where the > crash occurs, and I haven't been able to reproduce the problem > elsewhere. > > I still think we have a basic IDE problem. I've spent the last few > hours installing 4-STABLE on a Duron box, and I'm running into a lot > of trouble with the IDE drives. SCSI seems to work fine, and so do > Linux, NetBSD and OpenBSD. Well, at least I haven't seen this kind of > problem yet. OK - I'll try that patch. But now for the dumb question: How do I do this? I am a religious user of cvsup, portupgrade and make. Applying a specific patch is foreign territory to me. Here are the version numbers I have for these bits of source under /usr/src/sys/dev/vinum: # grep FreeBSD vinumstate.c * $FreeBSD: src/sys/dev/vinum/vinumstate.c,v 1.28.2.2 2000/06/08 02:00:23 grog Exp $ # grep FreeBSD vinumrequest.c * $FreeBSD: src/sys/dev/vinum/vinumrequest.c,v 1.44.2.4 2002/02/03 07:10:26 grog Exp $ # Next step? --- Regards, Patrick O'Reilly. ___ _ __ / _ )__ __ (_)_ __ ___ _/ /____ __ / __/ -_) _) / ~ ) -_), ,-/ -_) _) /_/ \__/_//_/_/~/_/\__/ \__/\__/_/ http://www.perimeter.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message