- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- File: /sys/BINARY/isp.mod
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
Discussions
Discussions
Forums
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
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
тАО11-07-2007 04:51 AM
тАО11-07-2007 04:51 AM
we have a problem with Qlogic (SCSI Adapter).
the server in question is:
Tru64 Unix 4.0D version
Hp support asked to do the following:
There is a patch that needs to be put on this system to take care of similar Qlogic (SCSI Adapter) performance issues:
kzpba_v40d_bl13.tar
they asked to know the following:
server_unix[11]# dupatch -track -type kit
* Previous session logs saved in session.log.[1-25]
- This dupatch session is logged in //var/adm/patch/log/session.log
Patches installed on the system came from following patch kits:
--------------------------------------------------------------
- DUV40DAS00003-19990208 OSF425
- DUV40DAS0005-19991007 OSF425
NOTE
When a patch kit is listed, it does not necessarily mean
all patches on that kit are installed on your system.
the tar file contains:
system 286120 Dec 6 1999 isp.mod
system 260 Feb 16 2000 Readme.0d
also they ask to do (Readme.0d):
As superuser:
cp /sys/BINARY/isp.mod /sys/BINARY/isp.mod_orig
cp ./isp.mod /sys/BINARY/isp.mod
chmod 0644 /sys/BINARY/isp.mod
chown bin:bin /sys/BINARY/isp.mod
A kernal rebuild (doconfig тАУc HOSTNAME) and reboot is required. (HOSTNAME is name of your host; can be found in /sys/conf/ directory )
QUESTIONS:
1.- What isp.mod file means?
2.- why they are asking to replace this file isp.mod?
3.- what the file isp.mod contains?
4.- what this command "doconfig тАУc HOSTNAME" means?
4.- why is necessary to rebuild the kernel?
5.- what do i have to do before rebuild the kernel?, we never have rebuild a kernel.
please let us know.
thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2007 05:20 AM
тАО11-07-2007 05:20 AM
SolutionIs the kernel "module" (driver) for the HBA.
2.- why they are asking to replace this file isp.mod?
Should be a "patched" version that contains the code to solve/optimize performance.
3.- what the file isp.mod contains?
All info needed to handle the HBA. Some information could be get if you run:
strings isp.mod
4.- what this command "doconfig c HOSTNAME" means?
Will "recompile" the kernel with the new driver.
4.- why is necessary to rebuild the kernel?
To add the new driver support into the kernel.
5.- what do i have to do before rebuild the kernel?, we never have rebuild a kernel.
Save your old kernel:
cp /vmunix /vmunix.bak
After the doconfig finish, you will get a message:
Your new kernel is at "/path/location"
You have to copy the resulting kernel file to the /.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2007 05:27 AM
тАО11-07-2007 05:27 AM
Re: File: /sys/BINARY/isp.mod
1.- What isp.mod file means?
This file is one of the module (.mod) files that makes up the kernel.
2.- why they are asking to replace this file isp.mod?
Presumably because there is a bug in that module that is causing your problem.
3.- what the file isp.mod contains?
Part of the kernel.
4.- what this command "doconfig c HOSTNAME" means?
Rebuilds the kernel configured for your system. See "man doconfig" for more information.
4.- why is necessary to rebuild the kernel?
The patch is to the kernel, how else are you going to get the patch into the kernel?
5.- what do i have to do before rebuild the kernel?, we never have rebuild a kernel
See "man doconfig" for more information.
Ann
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2007 05:46 AM
тАО11-07-2007 05:46 AM
Re: File: /sys/BINARY/isp.mod
is there a risk after rebuild the kernel?
what could happen?
please let us know.
thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2007 06:37 AM
тАО11-07-2007 06:37 AM
Re: File: /sys/BINARY/isp.mod
# cp /vmunix /vmunix.old
Before you copy in the new kernel:
# cp /usr/sys/YOUR_HOSTNAME/vmunix /vmunix
So, you can always go back to the old kernel if something goes wrong.
Replace HOSTNAME or YOUR_HOSTNAME in the examples with the name of your system in upper case. For example if the name of your system is fred, replace HOSTNAME or YOUR_HOSTNAME with FRED.
Ann
Ann
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2007 07:31 AM
тАО11-07-2007 07:31 AM
Re: File: /sys/BINARY/isp.mod
>>> boot -fi vmunix.old
Then you can copy back your kernel file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2007 07:32 AM
тАО11-07-2007 07:32 AM
Re: File: /sys/BINARY/isp.mod
Then, the activities to be done are:
Save your old kernel:
cp /vmunix /vmunix.bak
cp /usr/sys/MY_HOSTNAME/vmunix /vmunix
As superuser:
cp /sys/BINARY/isp.mod /sys/BINARY/isp.mod_orig
cp ./isp.mod /sys/BINARY/isp.mod
chmod 0644 /sys/BINARY/isp.mod
chown bin: bin /sys/BINARY/isp.mod
A kernel rebuild (doconfig ├в c HOSTNAME)
And reboot is required. (HOSTNAME is name of your host; can be found in /sys/conf/ directory)
After the doconfig finish, you will get a message:
Your new kernel is at "/path/location"
You have to copy the resulting kernel file to the /.
a) what will happen when it has run the command doconfing -c HOSTNAME?
in that moment is going to be down the system? or do i have to down it by myself?
b) what is the best command and option to shut down the server?
c) how can i know if the system could start correctly? is the system going to be up? or will the system be blocked?
d) how can i know if i have to return back the old version of the file vmunix?
e) if the system failed, do i have to rebuild the kernel with the old isp.mod file?
please let us know.
thanks. :0)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2007 08:14 AM
тАО11-07-2007 08:14 AM
Re: File: /sys/BINARY/isp.mod
in that moment is going to be down the system? or do i have to down it by myself?
The system will not go down, you have to reboot it yourself after you copy the new vmunix file to the / directory.
b) what is the best command and option to shut down the server?
It depends on the version you're running. since you're running V4.0D (a VERY old version!)
# shutdown -r
would probably be the best option. See
"man shutdown" for any additional options you may want/need to add to the shutdown command.
c) how can i know if the system could start correctly? is the system going to be up? or will the system be blocked?
It is highly unlikely that there will be any problems caused by booting the newly built kernel. But, if the system crashes or hangs, you can reboot using the old kernel using the commands that Ivan listed in his previous response "To boot your old kernel..."
d) how can i know if i have to return back the old version of the file vmunix?
It is highly unlikely that this will happen, but if the system crashes, hangs, or gets many error messages (not informational messages, those are normal) on booting.
e) if the system failed, do i have to rebuild the kernel with the old isp.mod file?
No, just copy your old vmunix back into place, i.e.:
# cp /vmunix /vmunix.bad
# cp /vmunix.old /vmunix
If you followed Ivan's instructions in his previous update "To boot your old kernel..." you will already be running the old version of the kernel (before the patch). These instructions make sure that you will continue to run the old kernel after any reboots.
Ann
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2007 08:29 AM
тАО11-07-2007 08:29 AM
Re: File: /sys/BINARY/isp.mod
we will follow your suggests ...
THANKS ALL FOR YOUR HELP ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2007 07:26 AM
тАО11-09-2007 07:26 AM
Re: File: /sys/BINARY/isp.mod
Hi ..
the kernel was rebuild sucessfully, i have a question, i answered "n",
1.- if i have answered "y", what would have been showed?
2.- what the system means when it says "to edit the configuration" ?
3.- does the system mean to run: strings vmunix?
server_unix[34]# doconfig -c SERVERPATITO
*** KERNEL CONFIGURATION AND BUILD PROCEDURE ***
Saving /sys/conf/SERVERPATITO as /sys/conf/SERVERPATITO.bck
Do you want to edit the configuration file? (y/n) [n]: n
*** PERFORMING KERNEL BUILD ***
Working....Wed Nov 7 18:20:25 CST 2007
The new kernel is /sys/SERVERPATITO/vmunix
server_unix[35]#
==========================================
On the other hand:
when i saw the vmunix through strings command i could see the following:
server_unix[9]# diff new_vmunix old_vmunix
817,818c817
< @(#)$RCSfile: isp1020.c,v $ $Revision: 1.1.303.1 $ (DEC) $Date: 1999/12/02 15:47:45 $
< @(#)$RCSfile: isp1020.c,v $ $Revision: 1.1.303.1 $ SS_PERFORM_TMO, untimeout test patch
---
> @(#)$RCSfile: isp1020.c,v $ $Revision: 1.1.213.6 $ (DEC) $Date: 1999/06/21 17:07:08 $
2200c2199
< Digital UNIX V4.0D (Rev. 878); Wed Nov 7 18:20:51 CST 2007
---
> Digital UNIX V4.0D (Rev. 878); Thu Sep 20 15:31:16 CDT 2007
server_unix[10]#
QUESTIONS:
4.- What is the meaning of the sentence "untimeout test patch"?
5.- what is the meaning of the fields of the lines that were changed?
< @(#)$RCSfile: isp1020.c,v $ $Revision: 1.1.303.1 $ (DEC) $Date: 1999/12/02 15:47:45 $
< @(#)$RCSfile: isp1020.c,v $ $Revision: 1.1.303.1 $ SS_PERFORM_TMO, untimeout test patch
thanks in advance.
Regards.