mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hermann Himmelbauer <dusty@violin.dyndns.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Karsten Keil <kkeil@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: APIC-Errors+Crashes on GA 586DX, 2.2.17/2.4.3
Date: Sun, 22 Apr 2001 14:56:07 +0200	[thread overview]
Message-ID: <3AE2D4E7.4D7E58BD@violin.dyndns.org> (raw)
In-Reply-To: <E14r6ZO-0004Xf-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > here. These errors itself are not a problem since the APIC bus detect
> > it and recover, but if here are double errors in a way that the checksum
> > is OK, the APIC may run in trouble.
> 
> Also nothing but recent -ac kernels in the 2.4 range handle the replay of
> IPI's sometimes caused by this. That patch is a post 2.4.4 thing to sort out.

Hmmm, that's a little too technical for me ;-)
Does that mean that this patch would perhaps increase the stability of
my board as this code tries to prevent those double errors? 
If yes, where could I get this patch to try it out?

What do you think of the following suggestion:
-Implement two runtime kernel variables like

/proc/sys/kernel/print_apic_errors
This would simply disable those "APIC error" kernel logs, so that the
logfile is not flooded. (45000 log entries in 1 hour are quite a lot).
Anyway once you know that your board has this problem, IMHO there is no
further use in those messages.

/proc/sys/kernel/enable_apic
The second one would enable/disable the APIC code for testing purposes -
like the "noapic" parameter during boottime. But as I have no knowledge
about those kernel internals, perhaps this wish is impossible to
implement...

Once again, thank you for your help!

		Best Regards,
		Hermann

-- 
 ,_,
(O,O)     "There is more to life than increasing its speed."
(   )     -- Gandhi
-"-"--------------------------------------------------------------

  reply	other threads:[~2001-04-22 12:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-21 13:07 Hermann Himmelbauer
2001-04-21 16:04 ` Karsten Keil
2001-04-21 23:13   ` Alan Cox
2001-04-22 12:56     ` Hermann Himmelbauer [this message]
2001-04-22 13:02       ` Alan Cox
2001-04-22  9:22   ` Hermann Himmelbauer
2001-04-22 12:23     ` Alan Cox
2001-04-22 20:02     ` Ingo Oeser

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=3AE2D4E7.4D7E58BD@violin.dyndns.org \
    --to=dusty@violin.dyndns.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dusty@strike.wu-wien.ac.at \
    --cc=kkeil@suse.de \
    --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®