Ignite-UX

SIGSEGV received during ignite process

 
Nivesh Patnaik
Frequent Advisor

SIGSEGV received during ignite process

I have an HP-UX 11.00 system with Ignite B.5.3.35. The kernel parameters are attached. I believe maxdsiz and maxssiz are adequate.

4GB of swap is allocated on the system. I created a customized image for tape media.

During Ignite, right during (or after) the execution of /opt/ignite/data/scripts/os_arch_post_l, I get:

Pid 146 received a SIGSEGV for stack growth failure,
Possible causes: insufficient memory or swap space, or stack size exceeded maxssiz.

Any suggestions?
I gave him his drink as usual. Some men can't hold their arsenic.
7 REPLIES 7
RAC_1
Honored Contributor

Re: SIGSEGV received during ignite process

What is the setting for massiz_64bit and maxdsiz_64bit?

Anil
There is no substitute to HARDWORK
Nivesh Patnaik
Frequent Advisor

Re: SIGSEGV received during ignite process

maxssiz 256MB
maxssiz_64bit 256MB

maxdsiz 390MB
maxdsiz_64bit 1GB

maxtsiz 128MB
maxtsiz_64bit 1GB
I gave him his drink as usual. Some men can't hold their arsenic.
Don Morris_1
Honored Contributor

Re: SIGSEGV received during ignite process

Is your setting for maxssiz _really_ 65536 as reported in your attachment, or did this whatever tool you used do some processing?

The reason being -- the maxssiz tunable is in *bytes*, not pages. If you're really set to 65536, you're running with 64k -- which is not likely to be enough.
Nivesh Patnaik
Frequent Advisor

Re: SIGSEGV received during ignite process

The maxssiz is really 256 MB.

The attachment is the output from /usr/sbin/sysdef which I think shows the values in pages...each page being 4 KBytes.

65536 (Pages) * 4 KB = 262144 KB = 256 MB

Yup, I think that is correct.
I gave him his drink as usual. Some men can't hold their arsenic.
RAC_1
Honored Contributor

Re: SIGSEGV received during ignite process

Does it create some core after it receives SIGSEGV? IF yes do as follows.

adb /file_core
on adb prompt
$c
$C

What that reports??

Anil
There is no substitute to HARDWORK
Nivesh Patnaik
Frequent Advisor

Re: SIGSEGV received during ignite process

Searched the entire system for a core file. None found.

The SIGSEGV error message appears right after the os_arch_post_l (default version) script runs.

After the error message, I see the message:
Running the ioinit command ("/sbin/ioinit -c") and the ignite process continues to completion.

Right now I am creating new media with a modified post load script to see if the script itself is causing the error, or if the error message is being generated independent of the script running.

Will post the results as soon as I get to it.
I gave him his drink as usual. Some men can't hold their arsenic.
Nivesh Patnaik
Frequent Advisor

Re: SIGSEGV received during ignite process

Okay, after modifying HP's default post archive load script, I think the problem is
occuring towards the very end of the script.

Commenting out this section of code eliminates the problem.

# Add fiber channel drivers when needed. /dev/config is needed for
# the ioscan below to work. However it produces output complaining
# about the lack of /etc/ioconfig (so /dev/null it)
insf -e -d dev_config > /dev/null 2>&1

if ioscan -fk |grep -q "^fcp " ; then
grep -q "^fcT1_fcp$" /stand/system
if [[ $? -ne 0 ]] then
echo "fcT1_fcp" >> /stand/system
fi
fi



The same code is used in other previous Ignite versions, so I cannot figure out what is causing the issue. Has anyone else run into this?
I gave him his drink as usual. Some men can't hold their arsenic.