From nobody@FreeBSD.org Thu Feb 15 08:48:53 2001 Return-Path: Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0972337B4EC for ; Thu, 15 Feb 2001 08:48:51 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f1FGmpH36522; Thu, 15 Feb 2001 08:48:51 -0800 (PST) (envelope-from nobody) Message-Id: <200102151648.f1FGmpH36522@freefall.freebsd.org> Date: Thu, 15 Feb 2001 08:48:51 -0800 (PST) From: rsimmons@spamcop.net To: freebsd-gnats-submit@FreeBSD.org Subject: vinum kernel module is compiled without debug support, even though -DVINUMDEBUG is in the Makefile X-Send-Pr-Version: www-1.0 >Number: 25114 >Category: kern >Synopsis: vinum kernel module is compiled without debug support, even though -DVINUMDEBUG is in the Makefile >Confidential: no >Severity: non-critical >Priority: low >Responsible: grog >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 15 08:50:00 PST 2001 >Closed-Date: Tue Mar 27 16:12:14 PST 2001 >Last-Modified: Tue Mar 27 16:19:15 PST 2001 >Originator: Rob Simmons >Release: 4.2-STABLE >Organization: >Environment: FreeBSD ned 4.2-STABLE FreeBSD 4.2-STABLE #0: Thu Feb 15 10:38:52 EST 2001 rsimmons@ned:/usr/obj/usr/src/sys/NED i386 >Description: After performing a cvsup/make world my vinum disk array would not come up and it was giving me the following message: "This program is compiled with debug support, but the kernel module does not have debug support. This program must be matched with the kernel module. Please alter /usr/src/sbin/vinum/Makefile and remove the option -DVINUMDEBUG from the CFLAGS definition, or alternatively edit /usr/src/sys/modules/vinum/Makefile and add the option -DVINUMDEBUG to the CFLAGS definition. Then rebuild the component of your choice with 'make clean all install'. If you rebuild the kernel module, you must stop vinum and restart it" I looked in both places and -DVINUMDEBUG was set in both Makefiles. I have the pseudo-device vinum set in the kernel config, so it is statically compiled into the kernel. To get rid of the problem, I went to the vinum userland program and recompiled it without the -DVINUMDEBUG option. The real problem is that the kernel module for vinum has the -DVINUMDEBUG option set but it is not actually being compiled with that option, it seems like that option is being ignored. >How-To-Repeat: cvsup a machine to the date in my uname above, then set the pseudo-device vinum option in the kernel config file. Then try to start vinum, it will give you the error that I listed above - and if you look in the two makefiles that it points you to, the -DVINUMDEBUG is set in both places, so it should work but it doesn't. >Fix: The workaround is to remove the -DVINUMDEBUG option from the userland vinum program. >Release-Note: >Audit-Trail: State-Changed-From-To: open->closed State-Changed-By: grog State-Changed-When: Tue Mar 27 16:12:14 PST 2001 State-Changed-Why: PR closed. Responsible-Changed-From-To: freebsd-bugs->grog Responsible-Changed-By: grog Responsible-Changed-When: Tue Mar 27 16:12:14 PST 2001 Responsible-Changed-Why: grog handles Vinum PRs. http://www.freebsd.org/cgi/query-pr.cgi?pr=25114 >Unformatted: Greg Lehey, 28 March 2001 Text tidied up. Please limit text lines to < 80 characters. From the vinum(4) man page: vinum is currently supplied as a kernel loadable module (kld), and does not require configuration. As with other klds, it is absolutely neces- sary to match the kld to the version of the operating system. Failure to do so will cause vinum to issue an error message and terminate. It is possible to configure vinum in the kernel, but this is not recom- mended. To do so, add this line to the kernel configuration file: pseudo-device vinum The real issue, though, is that the kernel module is not being used when you compile Vinum into the kernel. Remove the module from the kernel and things will work correctly. PR closed.