[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::axp-developer

Title:Alpha Developer Support
Notice:[email protected], 800-332-4786
Moderator:HYDRA::SYSTEM
Created:Mon Jun 06 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3722
Total number of notes:11359

3607.0. "Claritech" by HYDRA::BRYANT () Mon May 12 1997 13:08

    Company Name :  Claritech
    Contact Name :  Steven Jenson
    Phone        :  
    Fax          :  
    Email        :  [email protected]
    Date/Time in :  12-MAY-1997 12:07:37
    Entered by   :  Pat Bryant
    SPE center   :  MRO

    Category     :  UNIX
    OS Version   :  
    System H/W   :  4100


    Brief Description of Problem:
    -----------------------------
He can't run Ladebug without getting panic stops.  Not even a test
program which just prints out 'Hello World'.

T.RTitleUserPersonal
Name
DateLines
3607.1Is this V4.0B by any chance?...AMCUCS::SWIERKOWSKIQuot homines tot sententiaeMon May 12 1997 13:4916
Greetings!

  Check the version of Digital UNIX.  There is a known show-stopper (already 
QAR'ed) about 'dbx' (which may also affect 'ladebug'?).  See notes 3457
and 3600 in this conference for similar calls.  See notes 8562.*, 8540.*, 9275.*
and 9527.* in the DIGITAL_UNIX confererence for more details (especially note 
8562.1 for a description with a work-around), cheers...



						Tony Swierkowski
						Digital Equipment Corporation
						Software Partner Engineering
						Palo Alto, California
						(415) 617-3601
						"[email protected]"
3607.2Sent the following mail outHYDRA::BRYANTMon May 12 1997 14:2732
To:[email protected]
cc:
Subject:Known Problem?
--------
Steven,

I'm seeing evidence of the same problem occuring with other customers on 4.0b. 
It occurs when the kernel is build with KDEBUG setup in the kernel config file,
/sys/conf/XXXX where XXXX is the uppercase system name.  

The problem has to do with the kernel variable db_enable.  This is a relatively
new kernel variable, and gets set to 1 when KDEBUG is configured.  You can
resolve this by going into ladebug or dbx as superuser and doing the following:

dbx -k /vmunix        	/* or whatever you are running as the OS */
assign db_enable = 0

and then quit.  This will take care of the current session, but db_enable will
be reset if you have to reboot.  To take care of that:

dbx /vmunix          /* no -k this time, we want the disk version...
patch db_enable = 0

and you'll be set for the life of this particular kernel.  Note that you'll
have to do this all over again if you rebuild the kernel and leave KDEBUG
set.

Why don't you try this to see if you can get Ladebug functioning.  Let me know
and I'll find a proper patch that fixes this.

Thanks.
Pat Bryant
3607.3Need to find this guy a patchHYDRA::BRYANTFri May 16 1997 09:212
He sent back mail stating the workaround fixed his problem.  I now need to track
down a patch number for him.
3607.4Maybe # OSF410-046 (or possibly not)...AMCUCS::SWIERKOWSKIQuot homines tot sententiaeFri May 16 1997 14:03320
Greetings!

  Per the QAR (i.e. #50981), this is fixed by patch OSF410-046 (New id #26-00)
to V4.0B, *but* note 8562.9 in the DIGITAL_UNIX conference says this is *not*
fixed despite the QAR being "closed".  If another QAR has (re)opened this pro-
blem, I don't what it is.  Having said that a quick search through COMETS for
"OSF410-046" yielded the following that suggests the KDEBUG patch is in that
patch kit - a call directly to the CSC or UNIX engineering might be in order,
cheers...



						Tony Swierkowski
						Digital Equipment Corporation
						Software Partner Engineering
						Palo Alto, California
						(415) 617-3601
						"[email protected]"

P.S.	This looked like OSF410-046 is the fix (contrary to note 8562.9 in the
	DIGITAL_UNIX conference...

From:	DECPA::"[email protected]" "system PRIVILEGED account" 16-MAY-1997 10:00:05.86
To:	Tony Swierkowski <[email protected]>
CC:	
Subj:	PR2 KDEBUG problem DUv4

This is a multi-part message in MIME format.

--------------167E2781446B
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

http://encke.alf.dec.com/cgi/v4.2?query_string=osf410-046&form=f2&file=/usr/comet/data/champ0/OSD/C97/03/28/C970328004751&ttl=_PR2_KDEBUG_problem_DUv4_0b&db=UNIX_97&

--------------167E2781446B
Content-Type: text/plain; charset=us-ascii; name="C970328004751&ttl=_PR2_KDEBUG_problem_DUv4_0b&db=UNIX_97&"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="C970328004751&ttl=_PR2_KDEBUG_problem_DUv4_0b&db=UNIX_97&"


                          Display Condensed Output

S:SRC970328004751
B:327435
I:CEGELEC ESCA
U:BELLEVUE
R:WA
C:EMAIL SRQ
A:47773
T:(000)0000000
P:(PR2)  KDEBUG problem  DUv4.0b
N:0001

From:   (47773) PHOTON::SMTP%"[email protected]"  "(28-MAR-1997 19:09)"
To:     DSN%OSF-KERNEL
Subj:   (PR2)  KDEBUG problem  DUv4.0b

  System SPIKE is a VAXstation 4000-90 running VMS V6.2.
  (HW Ver=017800000000000013000202, SID=13000202, XSID=04010002, DSN=V1.2C)

Hello

I need to find the patch for DU v4.0b that fixes the KDEBUG problem.  I
think it might be OSF410-046.

Thanks

Tom

*****************************************
Tom Ozanich             Cegelec ESCA    *
11120 NE 33rd. Place    206.822.6800    *
Bellevue, WA  98004                     *
                                        *
Internet:               [email protected]    *
*****************************************

N:0002
\+-----------------------  Beginning of Screener's Text -----------------------+

\(PR2)  KDEBUG problem  DUv4.0b
\** This call was created by the customer using DSNlink.
\** The first work unit in the SRQ has more information.
\+--------------------------- End of Screener's Text --------------------------+

Hi Tom,

My name is Howard and I work with the Digital UNIX Kernel Team.  You are
correct - the kdebug patch is patch id OSF410-046.  However, the v40b patches
are now in a "setld" format.  With the setld patches, you should apply all the
patches to your system.  The setld format does not allow for individual patch
installation(s).

To retrieve the most current kit:
        ftp atlanta.service.digital.com
        login as anonymous or ftp
        <supply your email address for the password>
        ftp> cd pub/paches/osf1v40b
        ftp> get patches.tar
        ftp> get release-notes.ps
        ftp> quit

Please be sure to read the README prior to making any changes to your system.

============================================================================

Thank You

Howard Thomas,
Digital Support Center
N:0003

From:   (47773) PHOTON::SMTP%"[email protected]"  "(31-MAR-1997 19:35)"
To:     DSN%SRQ$C970328-4751
Subj:   RE: (PR2)  KDEBUG problem  DUv4.0b

  System SPIKE is a VAXstation 4000-90 running VMS V6.2.
  (HW Ver=017800000000000013000202, SID=13000202, XSID=04010002, DSN=V1.2C)

Hello,

For some reason I have not received your reply.  I wonder if the return
address (mail) is ok ?  Please reply to [email protected]

Thank you

Tom

On Fri, 28 Mar 1997, Digital Service Request Acknowledgment wrote:

> Your service request has been received by the Digital Customer Support
Center.
>
> It has been automatically entered into the CSC Administrative System for the
> product you specified.  Should you wish to send additional information,
please
> REPLY to this acknowledgement or send to the address listed on the FROM
line.
>
> If you wish to telephone the Customer Support Center regarding this
> service request, please refer to the service request number shown below.
>
> Thank you for using DSNlink to submit your service request.
>
> Digital Service Request Number:  C970328-4751
>                   Submitted To:  OSF-KERNEL
>             Subject of Request:  (PR2)  KDEBUG problem  DUv4.0b
>

*****************************************
Tom Ozanich             Cegelec ESCA    *
11120 NE 33rd. Place    206.822.6800    *
Bellevue, WA  98004                     *
                                        *
Internet:               [email protected]    *
*****************************************

N:0004

From:   (47773) PHOTON::SMTP%"[email protected]"  "(31-MAR-1997 20:56)"
To:     DSN%SRQ$C970328-4751
Subj:   RE: (PR2)  KDEBUG problem  DUv4.0b

  System SPIKE is a VAXstation 4000-90 running VMS V6.2.
  (HW Ver=017800000000000013000202, SID=13000202, XSID=04010002, DSN=V1.2C)

Greetings,

I found the patch information from the automated responce - thank-you

I am very happy to see the patches to be consolodated and set up with
setld.   The only question I have is   Where and when can I find out if a
new patch.tar file has been released?  Is there a central location for
patch update information?

This new system is a huge improvement over searching through hundreds of
patches for each minor release.

Thanks you

Tom

On Mon, 31 Mar 1997, Digital Service Request Acknowledgment wrote:

> The additional Service Request information you have submitted has been
received
> by the Digital Customer Support Center.
>
> It has been automatically appended to your original service request in the
CSC
> Administrative System.  Should you wish to send additional information,
please
> REPLY to this acknowledgement or send to the address listed on the FROM
line.
>
> Attached to this message is any additional information regarding this
> Service Request.
>
> If you wish to telephone the Customer Support Center regarding this
> Service Request, please refer to the service request number shown below.
>
> Thank you for using DSNlink.
>  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Work Unit Entered: 28-MAR-1997 20:14
> Status: DSN WORKING, RECEIVED BY CSC
>
>
> From:   (47773) PHOTON::SMTP%"[email protected]"  "(28-MAR-1997 19:09)"
> To:     DSN%OSF-KERNEL
> Subj:   (PR2)  KDEBUG problem  DUv4.0b
>
>   System SPIKE is a VAXstation 4000-90 running VMS V6.2.
>   (HW Ver=017800000000000013000202, SID=13000202, XSID=04010002, DSN=V1.2C)
>
> Hello
>
> I need to find the patch for DU v4.0b that fixes the KDEBUG problem.  I
> think it might be OSF410-046.
>
> Thanks
>
> Tom
>
>  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Work Unit Entered: 28-MAR-1997 22:35
> Status: (V) CLOSED
>
> Hi Tom,
>
> My name is Howard and I work with the Digital UNIX Kernel Team.  You are
> correct - the kdebug patch is patch id OSF410-046.  However, the v40b
patches
> are now in a "setld" format.  With the setld patches, you should apply all
the
> patches to your system.  The setld format does not allow for individual
patch
> installation(s).
>
> To retrieve the most current kit:
>       ftp atlanta.service.digital.com
>       login as anonymous or ftp
>       <supply your email address for the password>
>       ftp> cd pub/paches/osf1v40b
>       ftp> get patches.tar
>       ftp> get release-notes.ps
>       ftp> quit
>
> Please be sure to read the README prior to making any changes to your
system.
>
> ============================================================================
>
> Thank You
>
>
>
> Howard Thomas,
> Digital Support Center
>  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Work Unit Entered: 31-MAR-1997 20:40
> Status: DSN WORKING, RECEIVED BY CSC
>
>
> From:   (47773) PHOTON::SMTP%"[email protected]"  "(31-MAR-1997 19:35)"
> To:     DSN%SRQ$C970328-4751
> Subj:   RE: (PR2)  KDEBUG problem  DUv4.0b
>
>   System SPIKE is a VAXstation 4000-90 running VMS V6.2.
>   (HW Ver=017800000000000013000202, SID=13000202, XSID=04010002, DSN=V1.2C)
>

N:0005
\+-----------------------  Beginning of Screener's Text -----------------------+

\(PR2)  KDEBUG problem  DUv4.0b
\** This call was created by the customer using DSNlink.
\** This is additional information to the call owned by 327435
\+--------------------------- End of Screener's Text --------------------------+

Hi Tom,

My name is Chia-Jen Liu Chyan and I am with Digital Unix Support Kernel
Team. In reply to your last question for a center location for
patch update information. There is another public patch web page
http://www.service.digital.com/html/patch_service.html that will provide
you patch information. If you have DSNlink service, I think you will be able
to get new patch information from there.

Thank you.

Chia-Jen Liu Chyan.
Digital Unix Support

N:0006
** The previous work unit was queued by DSNlink to be sent to the customer
N:0007
Closing call... no other responses from customer...

Howard
x31511

--------------167E2781446B--


% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
% Received: from pobox1.pa.dec.com by mts-gw.pa.dec.com (5.65/09May94) id AA14445; Fri, 16 May 97 09:59:44 -0700
% Received: by pobox1.pa.dec.com; id AA24901; Fri, 16 May 97 09:59:44 -0700
% Received: from localhost by trapshooter.pa.dec.com (5.65v3.2/1.1.10.5/28Oct96-0253PM) id AA25776; Fri, 16 May 1997 10:01:44 -0700
% Sender: [email protected]
% Message-Id: <[email protected]>
% Date: Fri, 16 May 1997 10:01:43 -0700
% From: system PRIVILEGED account <[email protected]>
% Organization: Software Partner Engineering
% X-Mailer: Mozilla 3.0Gold (X11; I; OSF1 V4.0 alpha)
% Mime-Version: 1.0
% To: Tony Swierkowski <[email protected]>
% Subject: PR2 KDEBUG problem DUv4
% Content-Type: multipart/mixed; boundary="------------167E2781446B"

3607.5Sending patch informationHYDRA::BRYANTMon May 19 1997 15:0611
Steven,
The patch you require is OSF410-053.  It can be obtained from 

http://www.service.digital.com/html/patch_public.html

Use the search and download utility to locate the proper patch.  Your search
string will be "OSF410-053".

Thank you.
Pat Bryant
Alpha Developer Support