News Group Posts

Main Index

From: Bela Lubkin <b...@sco.com>
Subject: Re: Is 5.0.7 ready for production?
Date: Fri, 5 Sep 2003 22:06:50 GMT
Message-ID: <20030905220650.GP24551@sco.com> 
References: <bj8jb9$g2ph7$1@ID-105888.news.uni-berlin.de>
<HKq1n4.2sD@stevedunn.ca>
<3F58AA15.D55682A1@tkg.ca> 

Mike Brown wrote:

> Also if you are updating an 'older' Compaq ProLiant that requires the
> EFS548 version it generates the following error on 5.0.7:
> 
> i386ld: Symbol pci-debug in

"pci_debug", actually.  Which shows that you're typing this rather than
cut-and-paste or redirecting to a file, tsk.

> /var/opt/K/SCO/link/1.1.1Hw/etc/conf/pack.d/cpqw/Driver.o
> is multiply defined.
> 
> first defined in
> /var/opt/K/SCO/link/1.1.1Hw/etc/conf/pack.d/pci/Driver.o
> ERROR: Can not link-edit unix
> 
> 
> Obviously the EFS install fails and you don't get the required drivers.
> HP/Compaq is not showing any updated EFS although I did report this
> March 12th. Normally by now I would have updated a portion of my client
> base and would have something to report.  The problem now is that we
> do not want to be supporting two versions of O/S, so have left most
> people on 5.0.6.

You can fix the above problem by patching the variable name in
pci/Driver.o to remove the conflict.  The variable is internal to
pci/Driver.o, so its name can be changed without a matching change
elsewhere.  The variable in Compaq's driver is internal to it.  We just
have to resolve the name collision:

  # cd /etc/conf/pack.d/pci
  # cp -p Driver.o Driver.o.orig
  # strings -a -o Driver.o | grep -i debug
  18790 pci_debug
  # bs=1 count=9 oseek=18790 of=Driver.o
  9+0 records in
  9+0 records out
  # strings -a -o Driver.o | grep -i debug
(see below for later correction)
  18790 pci_Debug
  # cd /etc/conf/cf.d
  # ./link_unix

> I am testing Progress 9.1b on 5.0.7, with a ProLiant ML530G3.  So far
> the system has locked up about 6 times with the database running, no
> panic dumps as the system is completely locked.  The server runs fine
> for days without Progress running, locks up in a few hours after
> the database is started. No idea why yet.

Is this without database activity??  Doesn't the Compaq watchdog stuff
kick in and reboot the system?  (Not that that would be much better, but
it's odd to actually _hang_ a system with a watchdog in it...)

Newsgroups: comp.unix.sco.misc
From: Bela Lubkin 
Subject: "pci_debug" symbol conflict, Re: Is 5.0.7 ready for production?
Date: Sat, 6 Sep 2003 09:20:07 GMT
Message-ID: <20030906092007.GS24551@sco.com>
X-Nntp-Posting-Host: enigma.xenitec.on.ca
References: 

<3F58AA15.D55682A1@tkg.ca>
<20030905220650.GP24551@sco.com>
<20030905221854.GA5887@jpradley.jpr.com>

Jean-Pierre Radley wrote:

> Bela Lubkin typed (on Fri, Sep 05, 2003 at 10:06:50PM +0000):
> | 
> | You can fix the above problem by patching the variable name in
> | pci/Driver.o to remove the conflict.  The variable is internal to
> | pci/Driver.o, so its name can be changed without a matching change
> | elsewhere.  The variable in Compaq's driver is internal to it.  We just
> | have to resolve the name collision:
> | 
> |   # cd /etc/conf/pack.d/pci
> |   # cp -p Driver.o Driver.o.orig
> |   # strings -a -o Driver.o | grep -i debug
> |   18790 pci_debug
> |   # bs=1 count=9 oseek=18790 of=Driver.o
> 
> Hmm...   missing echo and dd here?

Yep.  Don't know what went wrong.  It's wrong in my outgoing log, so it
must have been some sort of typo/braino.

> 	# echo pci_debug | dd bs=1 count=9 oseek=18790 of=Driver.o

Almost:

        # echo pci_Debug | dd conv=notrunc bs=1 count=9 oseek=18790 of=Driver.o

-- the whole point was to _change_ the name; and "conv=notrunc" is
necessary or `dd` truncates the file.

I also meant to point out that the seek offset was from the `strings`
output, might be different on another system.  I must have been asleep.

> |   9+0 records in
> |   9+0 records out
> |   # strings -a -o Driver.o | grep -i debug
> |   18790 pci_Debug
> |   # cd /etc/conf/cf.d
> |   # ./link_unix

>Bela<

Comments?

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.