>Number:         24262
>Category:       bin
>Synopsis:       LKM modload aborts module loading if debug and/or diagnostic are defined
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 27 23:05:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     Chris Tribo
>Release:        1.6ZH
>Organization:
>Environment:
NetBSD 1.6ZH (GENERIC_DIAGNOSTIC) #0: Sun Jan 18 16:09:07 EST 2004
root@Suck:/usr/obj/sys/arch/i386/compile/GENERIC_DIAGNOSTIC i386
>Description:
If I try to load the xf86 aperture driver with a debug/diagnostic kernel. modload emits this on boot:

/lkmtemp/: symbol '__bss_start' redeclared with different value (c03b31c4 != cbe876d4)
/lkmtemp/: symbol '_edata' redeclared with different value (c03b31c4 != cbe876d4)
/lkmtemp/: symbol '_end' redeclared with different value (c03eed44 != cbe87700)
LKM 'xf86': environment compile options mismatch - LKM '', kernel 'DEBUG,DIAGNOSTIC'

from the following line in /etc/lkm.conf:

/usr/pkg/lkm/xf86.o -vs - /usr/pkg/lkm/xf86_mod_install - AFTERMOUNT


then I have to use -f to defeat all version checks to get it to load. Is it reasonable to special case modload to ignore debug and diagnostic options, or only if the lkm was compiled with -g, -DDEBUG and/or -DDISAGNOSTIC; or is it not worth the trouble?
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: