From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <ak@suse.de>
Cc: torvalds@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Readd BUG for SMP TLB IPI
Date: 10 Jul 2003 00:38:56 +0100 [thread overview]
Message-ID: <1057793934.7138.9.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030709193246.059ee57d.ak@suse.de>
On Mer, 2003-07-09 at 18:32, Andi Kleen wrote:
> > > How do you know it an happen on them? Do you have backtraces?
> >
> > I sat down with a BP6 owner and did lots of debugging.
>
> I meant on the not known-to-be-nearly-unusable boards. Or are you saying that
> on the other boards the APIC bus could be lossy too, but it's very unlikely?
> [my personal feeling would be to consider the lossy APIC bus to be a hardware
> problem, like an MCE that cannot be really handled]
APIC errors can occur on any box. The checksum ensures they get
retransmitted but does mean you can ger replay of events
> I suspect when you have a lossy APIC bug you will run into problems with other IPIs too,
> it's really an uphill fight which you are likely to lose.
If you follow intels recommendations it ought to just work. Its basically about
checking if the message is one you processed and not repeating the execution
next prev parent reply other threads:[~2003-07-09 23:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 10:49 Andi Kleen
2003-07-09 11:27 ` Alan Cox
2003-07-09 11:41 ` Andi Kleen
2003-07-09 16:53 ` Alan Cox
2003-07-09 16:58 ` Andi Kleen
2003-07-09 17:04 ` Alan Cox
2003-07-09 17:32 ` Andi Kleen
2003-07-09 23:38 ` Alan Cox [this message]
2003-07-09 17:37 ` Compile failure 2.4.22-pre3-ac1 Midian
2003-07-09 18:10 ` Steven Cole
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=1057793934.7138.9.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®