- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- HELP es40 simple_lock: time limit exceed.
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
04-13-2006 07:18 PM
04-13-2006 07:18 PM
HELP es40 simple_lock: time limit exceed.
I got messages from /var/adm/messages as follows:
Apr 12 21:46:09 com1 vmunix: simple_lock: time limit exceeded
Apr 12 21:46:09 com1 vmunix:
Apr 12 21:46:09 com1 vmunix: pc of caller: 0xfffffc0000283b6c
Apr 12 21:46:09 com1 vmunix: lock address: 0xfffffc000ef68338
Apr 12 21:46:09 com1 vmunix: lock info addr: 0xfffffc0000bfabc0
Apr 12 21:46:09 com1 vmunix: lock class name: proc.p_lock
Apr 12 21:46:09 com1 vmunix: current lock state: 0xd00000ba0028cead (cpu=?,pc=0xfffffc000028ceac,busy)
Apr 12 21:46:09 com1 vmunix:
Apr 12 21:46:09 com1 vmunix: panic (cpu 1): simple_lock: time limit exceeded
Apr 12 21:46:09 com1 vmunix: syncing disks... device string for dump = SCSI 1 4 0 2 200 0 0.
Apr 12 21:46:09 com1 vmunix: DUMP.prom: dev SCSI 1 4 0 2 200 0 0, block 4181188
Apr 12 21:46:09 com1 vmunix: device string for dump = SCSI 1 4 0 2 200 0 0.
Apr 12 21:46:09 com1 vmunix: DUMP.prom: dev SCSI 1 4 0 2 200 0 0, block 4181188
Apr 12 21:46:09 com1 vmunix: Alpha boot: available memory from 0x211e000 to 0x3fd52000
Apr 12 21:46:09 com1 vmunix: Compaq Tru64 UNIX V5.1 (Rev. 732); Wed Mar 6 19:36:54 CST 2002
The OS Version is Tru64 UNIX V5.1, I upgraded the Firmware to 7.0-2 and Patch kit PK6
- T64V51B20AS0006-20030210 OSF510
Can anyone help me?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2006 08:22 PM
04-13-2006 08:22 PM
Re: HELP es40 simple_lock: time limit exceed.
Can you see if it's always the same CPU and/or always the same lock? That knowledge might point you in the right direction. For instance if it's a hardware problem, then one possibility is that the CPU holding the lock is hung. Note that the CPU crashing the system, is not the one that would be hung.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2006 09:58 PM
04-13-2006 09:58 PM
Re: HELP es40 simple_lock: time limit exceed.
Upgrade to 5.1B would be nice, but it would help only if the problem was software related.
As Han said, can you give more informations about what CPU crashed the system?
Did you upgrade the firmware after instalation of new CPUs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2006 02:55 AM
04-19-2006 02:55 AM
Re: HELP es40 simple_lock: time limit exceed.
I checked the session logs in /var/adm/patch/log, the patch 1163.00 in PK6 was not patched, because the sys_check have some problem. the sys_check version is 1.34. I'd like to delete the sys_check134, and reinstall the PK6 then install sys_check 1.4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2006 10:07 PM
05-09-2006 10:07 PM