From: Zdenek Kabelac <kabi@fi.muni.cz>
To: Grzegorz Sojka <grzes@prioris.mini.pw.edu.pl>
Subject: Re: BUG
Date: Thu, 1 Feb 2001 11:49:30 GMT [thread overview]
Message-ID: <3A794D4A.CA113571@fi.muni.cz> (raw)
In-Reply-To: <Pine.BSF.4.21.0101312339170.38659-100000@prioris.mini.pw.edu.pl>
Grzegorz Sojka wrote:
>
> I am using kernel v2.4.0 on Abit BP6 with two Intel Pentium Celeron
> 366@517Mhz + video based on Riva TNT2 M64 32Mb + network card 3com 3c905b
> + Creative Sound Blaster 64 pnp isa and hercules video card. I'm geting
> all over the time messages like that:
> Jan 31 23:37:16 Zeus kernel: APIC error on CPU0: 02(02)
> Jan 31 23:37:17 Zeus kernel: APIC error on CPU1: 02(08)
Enjoy this wonderful patch :)
--- linux.orig/arch/i386/kernel/apic.c Tue Jan 23 21:41:23 2001
+++ linux/arch/i386/kernel/apic.c Tue Jan 23 21:40:41 2001
@@ -765,6 +765,7 @@
v1 = apic_read(APIC_ESR);
ack_APIC_irq();
irq_err_count++;
+ if (1) return;
/* Here is what the APIC error bits mean:
0: Send CS error
It's not fix - you just don't get this borring message....
--
There are three types of people in the world:
those who can count, and those who can't.
Zdenek Kabelac http://i.am/kabi/ kabi@i.am {debian.org; fi.muni.cz}
-
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/
next prev parent reply other threads:[~2001-02-01 11:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 22:50 BUG Grzegorz Sojka
2001-01-31 23:18 ` BUG James Sutherland
2001-02-01 11:04 ` BUG Maciej W. Rozycki
2001-02-01 11:49 ` Zdenek Kabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-07 18:42 BUG Attila A Odry
2002-03-19 21:20 bug Виталий
2006-01-12 15:23 bug Philippe Delodder
2006-01-14 1:01 ` bug Adrian Bunk
2011-12-19 18:02 Bug Володимир Остап
2016-11-02 15:04 Bug H-P.Teufel
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=3A794D4A.CA113571@fi.muni.cz \
--to=kabi@fi.muni.cz \
--cc=grzes@prioris.mini.pw.edu.pl \
/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