public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Davis <tadavis@lbl.gov>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: endless APIC error messages..
Date: Mon, 01 Oct 2001 14:15:01 -0700	[thread overview]
Message-ID: <3BB8DCD5.A2CF293D@lbl.gov> (raw)

Yes, I know, I've got a busted ABIT-BP2 system board.

Running 2.4, I get thousands of the APIC error messages, which fill my
syslog.

Is there a reason for this constant spewing?  The short little patch,
that simply does stops the system from complaining any more - it's
busted - we know that.

--- linux/arch/i386/kernel/apic.c       Mon Oct  1 14:12:50 2001
+++ linux-2.4.9-ac16/arch/i386/kernel/apic.c    Mon Oct  1 14:10:19 2001
@@ -37,6 +37,8 @@
 int prof_old_multiplier[NR_CPUS] = { 1, };
 int prof_counter[NR_CPUS] = { 1, };
 
+static int apic_error_count = 50;
+
 int get_maxlvt(void)
 {
        unsigned int v, ver, maxlvt;
@@ -1061,8 +1063,11 @@
           6: Received illegal vector
           7: Illegal register address
        */
-       printk (KERN_ERR "APIC error on CPU%d: %02lx(%02lx)\n",
-               smp_processor_id(), v , v1);
+       if (apic_error_count != 0) {
+               apic_error_count--;
+               printk (KERN_ERR "APIC error on CPU%d: %02lx(%02lx)\n",
+                smp_processor_id(), v , v1);
+       }
 }
 
 /*

-- 
------------------------+--------------------------------------------------
Thomas Davis		| ASG Cluster guy
tadavis@lbl.gov		| 
(510) 486-4524		| "80 nodes and chugging Captain!"

             reply	other threads:[~2001-10-01 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01 21:15 Thomas Davis [this message]
2001-10-01 22:04 ` endless APIC error messages Mark Hahn
2001-10-01 22:19 ` Thomas Davis
2001-10-01 22:38   ` Alan Cox

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=3BB8DCD5.A2CF293D@lbl.gov \
    --to=tadavis@lbl.gov \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox