Linux IA64 platform development
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: "Deepak Kumar Gupta, Noida" <dkumar@hcltech.com>
Cc: "'lilbilchow@yahoo.com'" <lilbilchow@yahoo.com>,
	"'ananth@sgi.com'" <ananth@sgi.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'linux-ia64@vger.kernel.org'" <linux-ia64@vger.kernel.org>
Subject: Re: smp_call_function/flush_tlb_all hang on large memory system
Date: Mon, 22 Nov 2004 12:14:15 +0000	[thread overview]
Message-ID: <20041122121415.GA13845@lnx-holt.americas.sgi.com> (raw)
In-Reply-To: <267988DEACEC5A4D86D5FCD780313FBB2BFBB4@exch-03.noida.hcltech.com>

On Mon, Nov 22, 2004 at 03:15:00PM +0530, Deepak Kumar Gupta, Noida wrote:
> Hi William/Rajagopal
> 
> I saw your posting related to problem on internet. Just curious to ask you
> have you got any solution for that or not.. as i am facing same problem on
> SGI Propack 3 (based on kernel 2.4.18)on 2 CPU IA64 machine..
> 
> If you got any solution for this then pls let me know..
> 
> Any help in this regard is appreciated.
> 
> posting: http://www.cs.helsinki.fi/linux/linux-kernel/2003-11/1153.html
> 

Can you provide the output from an L2 "leds" command?  This will tell us
what the cpus are doing and whether they have interrupts enabled.  Have you
contacted your support people yet?  I did not see an open case for this,
but have no idea how your support person exactly filed it.

Thanks,
Robin Holt

  reply	other threads:[~2004-11-22 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22  9:57 smp_call_function/flush_tlb_all hang on large memory system Deepak Kumar Gupta, Noida
2004-11-22 12:14 ` Robin Holt [this message]
2004-11-23  2:23   ` Deepak Kumar Gupta, Noida
2004-11-23  2:26     ` Jack Steiner
2004-11-23 18:53     ` Zwane Mwaikambo
2004-11-23  2:36   ` Keith Owens

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=20041122121415.GA13845@lnx-holt.americas.sgi.com \
    --to=holt@sgi.com \
    --cc=ananth@sgi.com \
    --cc=dkumar@hcltech.com \
    --cc=lilbilchow@yahoo.com \
    --cc=linux-ia64@vger.kernel.org \
    --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