SEO

Hi,
I have written a DLKM module for hpux version 11i v2 (11.23). Now the
machine panics due to some wrong things in my module. Problem is when I
load the core through q4 or kwdb or kwdb -q4, I see the stack but I
dont see my routines in that.. it just says unknown procedure, although
I have compiled my module with debugging on. Following is a sample
stack trace I get -
#0 0xe0000000011f48e0:0 in panic_save_regs_switchstack+0x110
(0xe000000100635e80, 0x7, 0x713, 0xe0000000011e89c0, 0x2, 0x206c6100d3,
0xe00000010094b348, 0xe0000000002d9740)
#1 0xe0000000011e8a00:0 in panic
(0xe000000000256590, 0x896, 0xe000000000b02390, 0x2, 0x206c610011,
0xe000000100635f10, 0x2e8ae6852053, 0xe0000001005bb198) at
/ux/core/kern/em/svc/shutdown/panic.c:330
#2 0xe000000000b02390:0 in unaligned_hndlr
(0x9fffffff7f7e7200, 0xa, 0x0, 0x288, 0xe000000000b088c0, 0x206c61001d,
0x9fffffff7f7e71c0, 0x1) at /ux/core/kern/em/svc/misc/hl_ivt.c:1473
#3 0xe000000000b088c0:0 in bubbleup+0x740
(0x9fffffff7f7e7200, 0x9fffffff7f7e71f0, 0x9fffffff7f7e9518,
0x9fffffff7f7e8881, 0x206c61001d, 0x9fffffff7f7e7200, 0xa,
0x0)
#4 0xe000000146d369a0:0 in <unknown_procedure> +0x30
(0xe00000010e27e031, 0xe00000010e27e031, 0x29, 0x3f, 0xffffffff,
0xffffffffffffffff, 0xe00000010e27e031, 0xe00000010e27e039)
#5 0xe000000146d37390:0 in <unknown_procedure> +0x790
(0x0, 0xe000000146d266e0, 0xe000000146d266d0, 0x0, 0xe000000146d266e0,
0xe000000146d266d0, 0xb, 0xe00000010e27e000)
#6 0xe000000146d37520:0 in <unknown_procedure> +0x120
(0x0, 0xe000000146d266d0, 0xe000000146d266e0, 0x0, 0x17c0, 0x0,
0x0, 0xe000000146d266d0)
#7 0xe000000146d37790:0 in <unknown_procedure> +0x110
(0x17c0, 0x0, 0xe000000146d266e0, 0xe000000146d266d0, 0x0, 0x186,
0xe000000146d279b0, 0x0)
#8 0xe000000146d279b0:0 in <unknown_procedure> +0x270
(0x0, 0x206, 0xe000000146d273b0, 0x17c0, 0x0, 0xe000000146d266e0)
#9 0xe000000146d273b0:0 in <unknown_procedure> +0xf0
(0xe000000140378b00, 0xe000000140378b00, 0x10a9, 0xe000000000b17b90,
0x0, 0x206)
#10 0xe000000000b17b90:0 in mod_load_helper
(0xe000000141e6d100, 0x915, 0xe000000000b14b90, 0x2, 0x2099,
0x9fffffff7f7e7b40,
0x2e, 0x1) at /ux/core/kern/common/svc/dlkm/modctl.c:1347

I know it is a problem in my module, but I cant point out because of
this.
Please suggest me if I am need to add something to get these
information in the core dump. Following is the Makefile I am using to
compile the module -

--
MODULE=mymod
OBJS= ${MODULE}.o ${MODULE}.modmeta.o

CC=/opt/ansic/bin/cc
CCOPTS_common= -g +DD64

IDENTS_common= -DACLS -DAUDIT -DHPONCPLUS -DIDDS -DIPSEC
-DIVT_INTERCEPT \
-DLWSYSCALL -DPGPROF -DSTCP -D_CLEAN_BE -D_HPUX_SOURCE -D_KERNEL \
-D_LARGEFILE64_SOURCE -D_NO_USER_PROTOS -D_UNSUPPORTED \
-D__BIGMSGQUEUE_ENABLED -D__ROSE__ -U__hp9000s700 \
-D_XPG4_EXTENDED

# Definitions which apply to IPF only

CCOPTS_ipf= +DSitanium2 +kernel +objstatvars +Olit=all +Oshortdata=0
+W863
#CCOPTS_ipf= +DSitanium2 +kernel +objstatvars +W863

IDENTS_ipf= -DKERNEL_DEBUGGER -DVARIABLE_UAREA -D_SYSCALL_64
-D__NO_PA_HDRS

LDOPTS_ipf= +noobjdebug

# Merge the common and architecture-specific definitions

CCOPTS= ${CCOPTS_common} ${CCOPTS_ipf}
IDENTS= ${IDENTS_common} ${IDENTS_ipf}
#LDOPTS= ${LDOPTS_common} ${LDOPTS_ipf}

# Command locations

BUILDENV= /opt/ddk/11.23/BE/bin
BUILDENV_STUB= /opt/ddk/11.23/BE/macro_files
MODMETA= ${BUILDENV}/modmeta
MODLINK= ${BUILDENV}/modlink
STUB.m4= ${BUILDENV_STUB}/stub.m4

####################
# #
# Main build rules #
# #
####################

all: ${MODULE}

${MODULE}: ${OBJS}
@echo "Creating $@ ..."
rm -f $@
${MODLINK} -o ${MODULE} ${OBJS} ${LD_LIBS}

# Duplicate this rule as needed, updating dependencies appropriately

${MODULE}.o: ${MODULE}.c ${HEADERS}
@echo "Compiling ${MODULE}.c ..."
rm -f $@
${CC} ${CCOPTS} ${IDENTS} -c ${MODULE}.c

# This rule compiles the module metadata, which replaces master/space
files

${MODULE}.modmeta.o: ${MODULE}.modmeta
@echo "Compiling ${MODULE}.modmeta ..."
rm -f $@ ${MODULE}.modmeta.c
${MODMETA} ${IDENTS} ${MODULE}.modmeta > ${MODULE}.modmeta.c
${CC} ${CCOPTS} ${IDENTS} -c ${MODULE}.modmeta.c
rm -f ${MODULE}.modmeta.c

iam.techy@gmail.com wrote:
> Hi,
> I have written a DLKM module for hpux version 11i v2 (11.23). Now the
> machine panics due to some wrong things in my module. Problem is when I
> load the core through q4 or kwdb or kwdb -q4, I see the stack but I
> dont see my routines in that.. it just says unknown procedure, although
> I have compiled my module with debugging on. Following is a sample
> stack trace I get -

Use 'kcmodule' and change the module state to 'static'. Now try
your tests to reproduce the panic. You should be able to see
a proper stack trace in the resulting dump. I assume you already
know how to add debug information (for data structures/unions etc)
regarding your module, while using kwdb (see: adddebug).

HTH --vishwas

Oh, actually I got the answer for this. Sorry for not sharing that -
Starting kwdb or q4 with -m option includes my modues debug information
into the trace. Or otherwise I could even do add_module <mymod> at kwdb
prompt to add my module's information. This is provided the crash has
happened while module is loaded even if it is dynamic (static is not
really needed).

Thanks.

pai wrote:
> iam.techy@gmail.com wrote:
> > Hi,
> > I have written a DLKM module for hpux version 11i v2 (11.23). Now the
> > machine panics due to some wrong things in my module. Problem is when I
> > load the core through q4 or kwdb or kwdb -q4, I see the stack but I
> > dont see my routines in that.. it just says unknown procedure, although
> > I have compiled my module with debugging on. Following is a sample
> > stack trace I get -
>
> Use 'kcmodule' and change the module state to 'static'. Now try
> your tests to reproduce the panic. You should be able to see
> a proper stack trace in the resulting dump. I assume you already
> know how to add debug information (for data structures/unions etc)
> regarding your module, while using kwdb (see: adddebug).
>
> HTH --vishwas