mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve Snyder <swsnyder@insightbb.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: increasing APIC errors & spontaneous reboots
Date: Sun, 9 Nov 2003 08:17:08 -0800	[thread overview]
Message-ID: <200311090817.08570.swsnyder@insightbb.com> (raw)

Hello.

I'm seeing an increasing number of APIC errors (variable irq_mis_count, 
displayed as the "MIS:"  value in /proc/interrupts) and I'm also seeing 
spontaneous reboots.  Could these be related?

Before I go into details, a little background.  I've been using this same 
motherboard/CPUs/RAM with the 2.4.x kernels for several years with no 
problems.  Oh, the MIS: count would climb to 2, maybe as high as 4 but as 
no problems were experienced I never much cared.  The hardware being used 
is a Giga-Byte GA-6BXDU motherboard, dual P3/850Mhz processors and 3 
256MB sticks of ECC PC100 RAM.

For the last 6 - 8 months I've been seeing the MIS count increasing.  The 
largest I've seen is a value of 20.  During the same period I've been 
seeing spontaneous reboots.  The system will reboot itself every 3 to 4 
weeks.  There's no great uptime here; those APIC errors accumulate in 
less than a month.

No problems are seen in the system logs for this machine.  Things are 
apparently going along fine, then the next log entry is the starting line 
of a kernel loading.  The system has rebooted.  (I'm administering this 
machine remotely, so I can't report any text shown on the screen.)

I initially suspected the problems were heat-related (no, I do not 
overclock anything) but lm_sensors consistently shows the CPU fan 
rotations and temperatures to be of reasonable values.

Although this generally is a Red Hat v7.3 system, I run the latest stable 
plain-vanilla Linux kernel, not RH's patched versions.  I am currently 
running v2.4.22, with v2.4.21 before that.

Can anyone explain to me what would cause the increasing APIC MIS counts?  
Also, could this cause the system to reboot?

Thanks.


                 reply	other threads:[~2003-11-09 16:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200311090817.08570.swsnyder@insightbb.com \
    --to=swsnyder@insightbb.com \
    --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

Powered by JetHome