Dear All
Thank you very much for answering. I do not found
any error message using uerf -R | more . The
problem is related with a bad ground (I BELIEVE), because
the console cable (4 m long) worked fine before power loss.
Really, only the printer and the console are connected to
the "regular" ground, being the cpu and crt connected to a
reliable ground (we were lucky they are not connected to the
same circuit).
Also the "Stray interrupt" message dissapears if console is
directed to the graphic CRT instead to the VT320.
Our maintenance support will change the console and cable
(and clean the connections with alcohol).
Thank you spetially to
From: Magali.Bernard_at_univ-st-etienne.fr (Magali BERNARD)
From: glidden <glidden_at_harvard.edu> (Mark E. Glidden)
From: Javier Aida <jaida_at_gmd.com.pe> (Javier Aida)
From: wander <wander_at_cptec.inpe.br> (Wanderley O. Mendes)
From: Hellebo Knut <Knut.Hellebo_at_nho.hydro.com> (Hellebo Knut)
My original message:
From: depaz_at_tendilla.qfa.uam.es
To: alpha-osf-managers_at_ornl.gov
Subject: After power loss: Stray interrupt
Date: Thu, 13 Jun 96 10:24:01 -0100
Dear All
I have a DEC alpha 3000-600 with OSF/1 Ver 3.2.
After a complete and terrible power loss, I switch off the
machine, switch on, and after booting OSF/1 I get the following messages
in the console (about 18 times each minute) :
Stray Interrupt - IR:0 (intmask:c8)
Stray Interrupt - IR:80 (intmask:c8) ; SIR:0
Can anybody give me any hints?. Thank you
Jose
_____________
Dr. Jose Luis Garcia de Paz |_ /
Departamento de Quimica Fisica | |
Facultad de Ciencias, C-XIV-602 | 0 /
Universidad Autonoma de Madrid < | Telephon: +34-1-397.4957 or 4263
Ctra de Colmenar Km. 15 |_ ___/ Fax: +34-1-397.4512
E-28049 Madrid (SPAIN) \/ E-mail: <depaz_at_vm1.sdi.uam.ES>
alt E-mail: <depaz_at_tendilla.qfa.uam.ES>
http://www.uam.es/qfa/depaz.html
http://www.adi.uam.es/~depaz
From: Magali.Bernard_at_univ-st-etienne.fr (Magali BERNARD)
To: depaz_at_tendilla.qfa.uam.es
Subject: Re: After power loss: Stray interrupt
Date: Thu, 13 Jun 96 14:17:04 +0200
> After a complete and terrible power loss, I switch off the
> machine, switch on, and after booting OSF/1 I get the following messages
> in the console (about 18 times each minute) :
>
> Stray Interrupt - IR:0 (intmask:c8)
> Stray Interrupt - IR:80 (intmask:c8) ; SIR:0
>
I posted an identical message (07 Jun 96):
> What means next message ? (in kern.log) We got it from time to time
> under DUnix 3.2C
>
> > Jun 6 18:57:31 onzon vmunix: Stray interrupt - IR:0 (intmask:c0)
Still waiting for real answer - and the problem here appears not very often.
Here are the answers I received, if you can find some information :
------- Forwarded Messages
To: Magali.Bernard_at_univ-st-etienne.fr (Magali BERNARD)
Subject: Re: Kernel message
In-Reply-To: Your message of "Fri, 07 Jun 96 16:36:39 +0200."
<199606071436.QAA30749_at_onzon.univ-st-etienne.fr>
Date: Fri, 07 Jun 96 10:54:27 -0400
From: "Dr. Tom Blinn, 603-881-0646" <tpb_at_zk3.dec.com>
X-Mts: smtp
It means you got a stray interrupt -- the hardware interrupted the CPU at a
point when no interrupt was expected by the system software. For instance,
if your system has an ISA bus and one of the ISA adapters isn't working as
it should, it might post a hardware interrupt at a point where none of the
device drivers expects the interrupt.
Either it's flaky hardware or a defect in the software. Since you didn't
say what machine you're seeing this on, it's difficult to say exactly what
might be causing it.
Tom
------- Message 2
From: "E. Niederacher" <niederacher_at_fh-vorarlberg.ac.at>
Reply-To: niederacher_at_fh-vorarlberg.ac.at
Organization: Fachhochschul.Studiengdnge.Vorarlberg
X-Mailer: Mozilla 3.0b3 (Win95; I)
MIME-Version: 1.0
To: Magali BERNARD <Magali.Bernard_at_univ-st-etienne.fr>
Subject: Re: Kernel message
References: <199606071436.QAA30749_at_onzon.univ-st-etienne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I asked the same question a few month ago in this mailing list - with no
response. But Digitial hotline said, this is related to esmog on my long
console cable. And I think that's a possible answer.
- --
// Egon Niederacher Information Services niederacher_at_fh-vorarlberg.ac.at
// Fachhochschul.Studiengaenge.Vorarlberg
http://www.fh-vorarlberg.ac.at/
------- Message 3
From: "Schuhl, Robert" <robert.schuhl_at_ald-vt.de>
Subject: Re: Kernel message
To: "Magali BERNARD" <Magali.Bernard_at_univ-st-etienne.fr>
X-Mailer: Mail*Link SMTP-PS 3.0.2
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; Name="Message Body"
Content-Transfer-Encoding: quoted-printable
Hi!
We had this error, when the memory-contacts corroded. Cleaning the with =
alcohol helped.
Robert
------- Message 4
From: Hellebo Knut <Knut.Hellebo_at_nho.hydro.com>
Message-ID: <9606111645.ZM15551_at_bgptu1.nho.hydro.com>
In-Reply-To: Magali.Bernard_at_univ-st-etienne.fr (Magali BERNARD) "Kernel
message" (Jun 7, 4:36pm)
References: <199606071436.QAA30749_at_onzon.univ-st-etienne.fr>
Reply-To: Knut.Hellebo_at_nho.hydro.com
X-Mailer: Z-Mail (3.2.2 10apr95 MediaMail)
To: Magali.Bernard_at_univ-st-etienne.fr (Magali BERNARD)
Subject: Re: Kernel message
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Regards,
Here is what I got awhile ago regarding "stray interrupts", Good Luck :-)
[DEC OSF/1] "stray interrupt - ir:nnn [intmask:0xnn]" Message On Console
COPYRIGHT (c) 1988, 1993 by Digital Equipment Corporation.
ALL RIGHTS RESERVED. No distribution except as provided under contract.
OP/SYS: DEC OSF/1 AXP All Versions
SOURCE: Digital Equipment Corporation
QUESTION:
The following message keeps appearing on the console:
stray interrupt - ir:nnn [intmask:0xnn]
What does it mean?
ANSWER:
The message is coming from the generic interrupt handler on the OSF/1
system.
If an interrupt is received that cannot be identified as one being
expected,
you receive the above message.
To help determine what caused the interrupt, you can use the following
formula:
SIR = Serial Port Interrupt Register (shows what serial port
interrupted)
IR = Interrupt Register
IntMask = interrupt enable mask
Masked_IR = Interrupts that will be dealt with (not masked out, e.g.
IT & IntMask)
The Masked_IR can then be ANDed with some values to determine what the
interrupt came from. For example,
Masked_IR & 0x80 = interrupt caused by a device handled by the SCC chip,
e.g.
network interface, isdn, serial port.
Masked_IR & 0x40 = a specific turbochannel slot interrupted
Masked_IR & 0x3F = multiple turbochannel slot interrupts where detected.
Each one will be dealt with individually.
If the interrupt was not one of the above it is considered a "stray." The
best
way to determine what caused the interrupt is if there is an SIR present
that
means it came from one of the serial ports, which may indicate a noisy
line.
Otherwise, it most likely came from the turbochannel and can indicate a bad
SCSI cable or the like.
Of course, it is always possible that a bad motherboard may misidentify a
given interrupt and give the appearance of a bus problem.
This is a STARS article extract - Marts 94 \by Jeff Finkelstein (310695)
- --
******************************************************************
* Knut Helleboe | DAMN GOOD COFFEE !! *
* Norsk Hydro a.s | (and hot too) *
* Phone: +47 55 996870, Fax: +47 55 996342 | *
* Pager: +47 96 500718 | *
* E-mail: Knut.Hellebo_at_nho.hydro.com | Dale Cooper, FBI *
******************************************************************
------- End of Forwarded Messages
_________________________________________
Magali BERNARD (magali_at_univ-st-etienne.fr)
CRITeR - 23 rue du Dr Paul Michelon
42023 St-Etienne Cedex 2 - FRANCE
Tel: 77.48.50.62
Subject: Re: After power loss: Stray interrupt
Date: Thu, 13 Jun 96 08:50:52 -0500
From: glidden <glidden_at_harvard.edu>
To: <depaz_at_tendilla.qfa.uam.es>
Assuming you can get into the system ..., look in the binary error log
for more information on the problem
uerf -R |more
Mark E. Glidden
Harvard University
Office of Information Technology
10 Ware Street Cambridge MA
(617) 496-9266
From: Javier Aida <jaida_at_gmd.com.pe>
To: "'depaz_at_tendilla.qfa.uam.es'" <depaz_at_tendilla.qfa.uam.es>
Subject: RE: After power loss: Stray interrupt
Date: Thu, 13 Jun 1996 10:21:00 -0500
Hola, Jos=E9
No tengo muchas pistas, lo =FAnico que recuerdo es que algo similar me
ocurri=F3 con un DECsystem 5100, corriendo ULTRIX, tuvimos un problema =
con
la alimentaci=F3n de energ=EDa, y sufrimos un repentino corte. El =
mensaje es
pr=E1cticamente igual, y en esa ocasi=F3n se trat=F3 de un problema con =
el
m=F3dulo del CPU (hardware problem).
Espero resuelvas tu problema pronto.
Saludos desde Lima
Date: Thu, 13 Jun 1996 13:27:12 -0300
From: wander <wander_at_cptec.inpe.br>
To: depaz_at_tendilla.qfa.uam.es
Subject: Re: After power loss: Stray interrupt
--
Hi,
The Stray Interrupt could be caused by a poor power ground. Check if
your console is plugged on the same circuit as your system. Check if
your console data cable is not too much longer.
I hope this help...
Regards
Wander
--------------------=======--------------------
Wanderley O. Mendes wander_at_cptec.inpe.br
Software Specialist Digital Equipment do Brasil
Phone: 55-012-561-2820 Ext.9432 Fax: 55-012-561-2835
INPE/CPTEC - Cachoeira Paulista - Sao Paulo - Brazil
Date: Mon, 17 Jun 1996 16:29:57 +0200
From: Hellebo Knut <Knut.Hellebo_at_nho.hydro.com>
To: depaz_at_tendilla.qfa.uam.es
Subject: Re: After power loss: Stray interrupt
Regards,
Here's what I got from DEC regarding 'Stray interrupts':
--
******************************************************************
* Knut Helleboe | DAMN GOOD COFFEE !! *
* Norsk Hydro a.s | (and hot too) *
* Phone: +47 55 996870, Fax: +47 55 996342 | *
* Pager: +47 96 500718 | *
* E-mail: Knut.Hellebo_at_nho.hydro.com | Dale Cooper, FBI *
******************************************************************
From: sveinn_at_nwo.dec.com
To: knut.hellebo_at_nho.hydro.com
Subject: Stray Interrupt
Date: Mon, 17 Jul 95 10:34:04 +0200
[DEC OSF/1] "stray interrupt - ir:nnn [intmask:0xnn]" Message On Console
COPYRIGHT (c) 1988, 1993 by Digital Equipment Corporation.
ALL RIGHTS RESERVED. No distribution except as provided under contract.
OP/SYS: DEC OSF/1 AXP All Versions
SOURCE: Digital Equipment Corporation
QUESTION:
The following message keeps appearing on the console:
stray interrupt - ir:nnn [intmask:0xnn]
What does it mean?
ANSWER:
The message is coming from the generic interrupt handler on the OSF/1 system.
If an interrupt is received that cannot be identified as one being expected,
you receive the above message.
To help determine what caused the interrupt, you can use the following
formula:
SIR = Serial Port Interrupt Register (shows what serial port interrupted)
IR = Interrupt Register
IntMask = interrupt enable mask
Masked_IR = Interrupts that will be dealt with (not masked out, e.g.
IT & IntMask)
The Masked_IR can then be ANDed with some values to determine what the
interrupt came from. For example,
Masked_IR & 0x80 = interrupt caused by a device handled by the SCC chip, e.g.
network interface, isdn, serial port.
Masked_IR & 0x40 = a specific turbochannel slot interrupted
Masked_IR & 0x3F = multiple turbochannel slot interrupts where detected.
Each one will be dealt with individually.
If the interrupt was not one of the above it is considered a "stray." The best
way to determine what caused the interrupt is if there is an SIR present that
means it came from one of the serial ports, which may indicate a noisy line.
Otherwise, it most likely came from the turbochannel and can indicate a bad
SCSI cable or the like.
Of course, it is always possible that a bad motherboard may misidentify a
given interrupt and give the appearance of a bus problem.
This is a STARS article extract - Marts 94 \by Jeff Finkelstein (310695)
Received on Wed Jun 19 1996 - 16:43:49 NZST