- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: SIGSEGV and kernel parameters
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2001 02:30 AM
12-27-2001 02:30 AM
SIGSEGV and kernel parameters
I have a problem where we are receiving a Segmentation Violation. I believe this is a problem due to our kernel parameters. We are running HPUX V11.11 on a N4000x4way with 8192MB RAM. Our current parameters are :
maxdsiz_64bit 0xc0000000
maxtsiz_64bit 0x100000000
maxssiz_64bit 0x10000000
maxdsiz 0xc0000000
maxssiz 0x04fb3000
maxtsiz 0x40000000
What would you recomend we up these too?
regards
Phil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2001 03:46 AM
12-27-2001 03:46 AM
Re: SIGSEGV and kernel parameters
first in is impotentd that you will know how was your system install 32 bit or 64 bit .
you can see it with the command :
getconf KERNEL_BITS
i think that you are working with 64 bit .
my advise it to change this param to there max. size .
see this link for details on the params and what is the max size of this params ,
http://docs.hp.com//hpux/onlinedocs/os/KCparams.OverviewAll.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2001 06:15 AM
12-27-2001 06:15 AM
Re: SIGSEGV and kernel parameters
The N-class computer only runs a 64 bit kernel so there are no practical limits on RAM, but you need to look at the memory and process management papers in /usr/share/doc.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2001 06:27 AM
12-27-2001 06:27 AM
Re: SIGSEGV and kernel parameters
Thanks
Phil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2001 08:42 AM
12-27-2001 08:42 AM
Re: SIGSEGV and kernel parameters
[extprocPLSEx][7662] Received signal 11, SIGSEGV, in user mode, [SIG_DFL], partial siginfo
[extprocPLSEx][7662] Siginfo: si_code: I_NONEXIST, faulting address: 0x3c2b4fd8, si_errno: 0
[extprocPLSEx][7662] PC: 0xc019c5b7, instruction: 0x4b570030
Scratching head now :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2001 08:54 AM
12-27-2001 08:54 AM
Re: SIGSEGV and kernel parameters
As Bill stated, it depends on what applications you are running. I personally always set the maxdsiz parameter to the maximum on production systems because I have scripts that monitor the memory usage of processes and alert me when a certain threshold is reached. I can then make a decision on whether it is normal or there is a memory leak and I need to shutdown the application.
If you're getting a SIGSEGV it may or may not be related to these parameters, it could simply be a bug the program. A couple of questions:
- how big is the resulting corefile? If the size of the core is equal to maxdsiz then thats likely to be your problem. If its less than maxdsiz then your problem is elsewhere.
- what are the lines immediately before the SIGSEGV line in your tusc trace? Do any system calls return errno's? I would expect an ENOMEM if you hit maxdsiz. No errors in the tusc trace indicates that the program has simply tried to access memory illegally, and you won't get any more info from tusc on this.
- do you have access to the source code? If so, run the core file through a debugger like wdb or gdb and you can get a stack trace. If not, send the core back to the vendor or application developers, along with any other relevant information.
Regards,
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2001 09:10 AM
12-27-2001 09:10 AM
Re: SIGSEGV and kernel parameters
[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] recv(6, "0 ", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] recv(6, "1 ", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] recv(6, "9 ", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] recv(6, "; ", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] recv(6, ". ", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] recv(6, "\n", 1, 0) ..................................................................... = 1
[extprocPLSEx][7662] Received signal 11, SIGSEGV, in user mode, [SIG_DFL], partial siginfo
[extprocPLSEx][7662] Siginfo: si_code: I_NONEXIST, faulting address: 0x3c2b4fd8, si_errno: 0
[extprocPLSEx][7662] PC: 0xc019c5b7, instruction: 0x4b570030
[extprocPLSEx][7662] exit(11) [implicit] ..................................................................... WIFSIGNALED(SIGSEGV)|
WCOREDUMP
[/orarpc/bin/][6940] select(2048, 0x7b0445c8, NULL, NULL, NULL) .............................................. = 1
[/orarpc/bin/][6940] gettimeofday(0x7b0444f0, NULL) .......................................................... = 0
[/orarpc/bin/][6940] gettimeofday(0x7b04a7f0, NULL) .......................................................... = 0
[/orarpc/bin/][6940] getsockname(7, 0x7b04ab2c, 0x7b04ab20) .................................................. = 0
[/orarpc/bin/][6940] accept(7, 0x7b04ab00, 0x7b04aafc) ....................................................... = 12
[/orarpc/bin/][6940] fcntl(12, F_SETFD, 1) ................................................................... = 0
[/orarpc/bin/][6940] ioctl(12, FIONBIO, 0x7b04a5f8) .......................................................... = 0
[/orarpc/bin/][6940] sigaction(SIGPIPE, 0x7b04a5f0, 0x7b04a618) .............................................. = 0
[/orarpc/bin/][6940] select(2048, 0x7b0445c8, 0x7b0446c8, NULL, NULL) ........................................ = 1
[/orarpc/bin/][6940] gettimeofday(0x7b0444f0, NULL) .......................................................... = 0