maxdsize and aCC

[Nitin kashyap]

was not able to reply to the earlier thread, so posted a new one.
In continuation with that maxdsize and aCC problem, the log of mk_kernel is:

Compiling /stand/build/conf.c...
Loading the kernel...
Pid 28004 killed due to text modification or page I/O error
/sbin/sh: 28004 Bus error(coredump)
*** Error exit code 138

Stop.
config: make did an exit(1)

[Ravi_8]

Hi,

Error exit code 138 :

stack overflow:
A floating-point expression caused a stack overflow on the 8087/287/387 coprocessor or the emulator. Stack-overflow floating-point exceptions are trapped up to a limit of seven levels in addition to the eight levels usually supported by the 8087/287/387 coprocessor. This error terminates the program with exit code 138.


Better log a call with HP.

[Elmar P. Kolkman]

It seems Ravi posted in the wrong thread ;-)

Sending this to HP seems a good idea. Or try to generate your kernel with your previous version (vmunix.prev), since you were able to generate a kernel in that version.

Also: did you change kernel parameters using an editor or did you use SAM? It might be a parameter is outside the boudaries now, which means it cannot be compiled... But that is not possible if the parameter is changed with SAM.

[Nitin kashyap]

ok shall try that...
I made teh config changes through SAM, aswell as gave the command to make the kernel through the same.

Only later did i try to give the mk_kernel command from the command line too.

[Jakes Louw]

Hi

What are the values for maxssiz, maxtsiz, and maxdsiz?

[Ravi_8]

Hi, Nitin

is your machine running 32 bit or 64 bit

#getconf KERNEL_BITS

post the o/p

[Nitin kashyap]

its running 32 bit.. and the values are:

maxdsize: 0x4000000
maxswapchunks: 256
memswap_on: 1
swchunk: 2048
maxssize: 0x800000
maxtsize: 0x4000000

Do i have to close all the processes running on teh machine before attempting to build it??

[Jakes Louw]

Firstly:

Take maxdsiz back to default = 256 MB (x10000000)
Take maxssiz up to double default = 16 MB (x1000000)
and take maxtsiz back to default = 256 MB (x10000000)

HOWEVER: only make these changes if you have sufficient free swap (you shouldn't be using more than 50% swap now on average), or else if you are able to add swap, as these changes force an increase in swap usage due to swap space reservation based on the stack segment setting.

[Elmar P. Kolkman]

Have you checked memory usage around a compile? Failing memory allocations that are not checked might cause errors like this.

[Jakes Louw]

Failing malloc calls are usually due to 3 things:

1) Insufficient memory
2) Incorrect stack segment settings
3) Insufficient swap

All the indications here are that this is a process stack problem.

What is the history of this server? Is this a new install? Was it rebuilt? What was the last change prior to the problem? Did the server boot with all its main memory?

[Ravi_8]

Hi Nitin

problem looks interesting,

can you do this

#kmtune|grep maxdsiz

#kmtune -s maxdsiz=
#mk_kernel

post the o/p

[Nitin kashyap]

Ravi,
here is teh output

Value of TERM has been set to "ansi".
WARNING: YOU ARE SUPERUSER !!\n
-bash-2.05b#
-bash-2.05b#
-bash-2.05b#
-bash-2.05b#
-bash-2.05b#
-bash-2.05b# kmtune|grep maxdsiz
maxdsiz 0x04000000
maxdsiz_64bit 0x0000000040000000
-bash-2.05b# kmtune -s maxdsiz=0x10000000
-bash-2.05b# mk_kernel
Compiling /stand/build/conf.c...
Loading the kernel...
Pid 7069 killed due to text modification or page I/O error
/sbin/sh: 7069 Bus error(coredump)
*** Error exit code 138

Stop.
config: make did an exit(1)

[Ravi_8]

Hi,

could u copy /stand/system.prev to /stand/system and
#mk_kernel

[Nitin kashyap]

I would not like to do that lats step, because system.prev is dated 19th september, and after that we have made amny critical updates, including upgrade from aCC3.33 to acc 3.52

Further after the unsuccesful modification of the parameters through SAM, aswell as command line modifications through
kmtune -s