From: Steve Snyder <ssnyder@sierradesign.com>
To: linux-kernel@vger.kernel.org
Subject: APIC errors seen on v2.4.21
Date: Tue, 5 Aug 2003 09:51:26 -0700 [thread overview]
Message-ID: <200308050951.26186.ssnyder@sierradesign.com> (raw)
Today I found 2 APIC errors in my system log:
Aug 5 10:45:27 helios kernel: APIC error on CPU0: 00(02)
Aug 5 10:45:27 helios kernel: APIC error on CPU1: 00(02)
Perhaps this is just coincidence but I had just closed an application that
uses the serial port. The serial driver is integral to the kernel, not
built as a module.
A snippet of log file, showing the context of the errors, is shown below.
It documents my shutting down HylaFAX, the errors occurring, and
restarting HylaFAX. The APIC errors occurred 38 seconds after closing the
serial port.
My environment:
Red Hat Linux v7.3 + all RH updates + plain-vanilla kernel v2.4.21
Dual Pentium3/850MHz on a Giga-Byte GA-6BXDU motherboard
The Linux Kernel FAQ (at http://www.tux.org/lkml/#s13-4) says not to worry
about only a few such errors. OK, I won't. I am noting this behavior in
case anyone is interested.
Thanks.
------------------------
Aug 5 10:44:49 helios FaxQueuer[1072]: QUIT
Aug 5 10:44:49 helios hylafax: Shutting down HylaFAX queue manager (faxq): succeeded
Aug 5 10:44:49 helios hylafax: hfaxd shutdown succeeded
Aug 5 10:44:49 helios FaxGetty[1082]: CAUGHT SIGNAL 15
Aug 5 10:44:49 helios hylafax: faxgetty shutdown succeeded
Aug 5 10:45:27 helios kernel: APIC error on CPU0: 00(02)
Aug 5 10:45:27 helios kernel: APIC error on CPU1: 00(02)
Aug 5 11:07:51 helios FaxQueuer[25301]: HylaFAX (tm) Version 4.1.7
Aug 5 11:07:51 helios FaxQueuer[25301]: Copyright (c) 1990-1996 Sam Leffler
Aug 5 11:07:51 helios FaxQueuer[25301]: Copyright (c) 1991-1996 Silicon Graphics, Inc.
Aug 5 11:07:51 helios hylafax: faxq startup succeeded
Aug 5 11:07:51 helios HylaFAX[25306]: HylaFAX INET Protocol Server: restarted.
Aug 5 11:07:51 helios hylafax: hfaxd startup succeeded
Aug 5 11:07:51 helios hylafax: faxgetty startup succeeded
------------------------
reply other threads:[~2003-08-05 16:55 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=200308050951.26186.ssnyder@sierradesign.com \
--to=ssnyder@sierradesign.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
all inboxes | Powered by JetHome®