All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@osdl.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Readd BUG for SMP TLB IPI
Date: Wed, 9 Jul 2003 19:32:46 +0200	[thread overview]
Message-ID: <20030709193246.059ee57d.ak@suse.de> (raw)
In-Reply-To: <1057770255.6255.70.camel@dhcp22.swansea.linux.org.uk>

On 09 Jul 2003 18:04:15 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Mer, 2003-07-09 at 17:58, Andi Kleen wrote:
> > > It can happen to any PII/PIII box, its just very very rare on others, so
> > > rare I guess such crashes are in the noise.
> > 
> > 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] 

> > If the BUG was there they wouldn't be in the noise.  With the incomplete/broken
> > handling it's just a silent hang.
> 
> I'm not arguing BUG is better than hang, but working right is better than BUG 8)

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.

Anyways, having a clear BUG will make it easier to evaluate if there is really
a problem.

-Andi

  reply	other threads:[~2003-07-09 17:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 10:49 [PATCH] Readd BUG for SMP TLB IPI 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 [this message]
2003-07-09 23:38             ` Alan Cox
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=20030709193246.059ee57d.ak@suse.de \
    --to=ak@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.