Date: Fri, 23 Aug 2002 21:13:00 +0200 From: "Patrick O'Reilly" <bsd@perimeter.co.za> To: "Julian Elischer" <julian@elischer.org> Cc: "Andrew Gallatin" <gallatin@cs.duke.edu>, freebsd-hackers@freebsd.org Subject: Re: Kernel Panic = System crash 8 times in 4 days Message-ID: <007201c24ad9$1abc4560$0200000a@perimeter.co.za> References: <Pine.BSF.4.21.0208231146250.68522-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Julian Elischer" <julian@elischer.org> > > OK - It looks to me like I need to build with: > > options VINUMDEBUG > > > compile vinum in so that it's not a module for starters.. Grrr.. I was hoping we would not have to go this route! :) Julian, will this produce better information than I was able to get, as shown at http://docs.perimeter.co.za/crash/20020823_1623_d ? Assuming it would be best for me to go ahead, could I just ask for a little guidance please. I was not able, with my limited experience, to figure out what must be changed if I will compile vinum into the kernel. 1) I gather I need the following in my KERNCONF: pseudo-device vinum #Vinum concat/mirror/raid driver options VINUMDEBUG #enable Vinum debugging hooks 2) Do I need to change anything else? Does the vinum module need to be changed and rebuilt at the same time that I do a build kernel? Does the rc.conf start_vinum="YES" remain the same? Once again, thanks to all for your support... --- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007201c24ad9$1abc4560$0200000a>