All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Walberg <tewalberg@mediaone.net>
To: "Jorge Boncompte (DTI2)" <jorge@dti2.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ERR in /proc/interrupts
Date: Thu, 18 Jan 2001 16:10:00 -0600	[thread overview]
Message-ID: <20010118161000.A3487@mediaone.net> (raw)
In-Reply-To: <001c01c08199$387205f0$067039c3@cintasverdes>
In-Reply-To: <001c01c08199$387205f0$067039c3@cintasverdes> from Jorge Boncompte (DTI2) on 01/18/2001 15:54

[-- Attachment #1: Type: text/plain, Size: 2232 bytes --]

A quick perusal of the 2.2.18 source code (I don't have
a copy of 2.4.x handy) shows that it's directly
related to the number of IPIs (inter-processor
interrupts) the system has taken. I'm not real
sure under what conditions this occurs, but it's
someplace to start...


			tw


On 01/18/2001 22:54 +0100, Jorge Boncompte (DTI2) wrote:
>>	    What does ERR mean in /proc/interrupts? I have a computer running
>>	2.4.0test12 that has a lot of this ERR's?
>>	
>>	           CPU0
>>	  0:  116445752          XT-PIC  timer
>>	  1:     389614          XT-PIC  keyboard
>>	  2:          0          XT-PIC  cascade
>>	  5:   34298837          XT-PIC  eth1
>>	  8:          1          XT-PIC  rtc
>>	 10:  400182075          XT-PIC  eth0
>>	 11:   23181909          XT-PIC  ide0, ide1
>>	 14:          4          XT-PIC  ide2
>>	 15:     692215          XT-PIC  ide3
>>	 64:          0            none  acpi
>>	NMI:          0
>>	ERR:    1586756
>>	
>>	This is an AMD 800 + Tyan K7 mobo.
>>	
>>	    -Jorge
>>	
>>	==============================================================
>>	Jorge Boncompte - Técnico de sistemas
>>	DTI2 - Desarrollo de la Tecnología de las Comunicaciones
>>	--------------------------------------------------------------
>>	C/ Abogado Enriquez Barrios, 5   14004 CORDOBA (SPAIN)
>>	Tlf: +34 957 761395 / FAX: +34 957 450380
>>	--------------------------------------------------------------
>>	jorge@dti2.net _-_-_-_-_-_-_-_-_-_-_-_-_-_ http://www.dti2.net
>>	==============================================================
>>	Without wicker a basket cannot be done.
>>	==============================================================
>>	
>>	
>>	-
>>	To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>	the body of a message to majordomo@vger.kernel.org
>>	Please read the FAQ at http://www.tux.org/lkml/
End of included message



-- 
+--------------------------+------------------------------+
| Tim Walberg              | tewalberg@mediaone.net       |
| 828 Marshall Ct.         | www.concentric.net/~twalberg |
| Palatine, IL 60074       |                              |
+--------------------------+------------------------------+

[-- Attachment #2: Type: application/pgp-signature, Size: 175 bytes --]

  reply	other threads:[~2001-01-18 22:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-18 21:54 ERR in /proc/interrupts Jorge Boncompte (DTI2)
2001-01-18 22:10 ` Tim Walberg [this message]
2001-01-18 22:31   ` Jorge Boncompte (DTI2)
2001-01-18 22:41   ` Timur Tabi
2001-01-18 22:58     ` Jorge Boncompte (DTI2)
2001-01-18 22:21 ` Timur Tabi
  -- strict thread matches above, loose matches on Subject: below --
2003-09-30  9:39 Andreas Schwarz
2003-09-30 10:16 ` Christian
2003-09-30 10:34   ` Andreas Schwarz
2003-09-30 17:54     ` Andreas Schwarz
2003-09-30 10:45   ` Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010118161000.A3487@mediaone.net \
    --to=tewalberg@mediaone.net \
    --cc=jorge@dti2.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.