From: Michael Madore <mmadore@turbolinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Lockups on 2.4.1
Date: Fri, 23 Feb 2001 19:20:00 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005193@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005175@msgid-missing>
What is the recommendation for earlier B steppings?
On Fri, Feb 23, 2001 at 11:06:53AM -0800, Seth, Rohit wrote:
> Just want to add that if you are running on B3 then you should have
> CONFIG_ITANIUM_PTCG=y and CONFIG_DISABLE_VHPT not set.
>
> -----Original Message-----
> From: Jun Nakajima [mailto:jun@sco.com]
> Sent: Friday, February 23, 2001 7:20 AM
> To: Jack Steiner
> Cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] Re: Lockups on 2.4.1
>
>
> This might explain why I was _not_ able to reproduce such a hang after
> overnight stress tests on a 4-way Lion... My configuration has
> CONFIG_ITANIUM_PTCG=y, and flush_tlb_no_ptcg() is never called by
> flush_tlb_range() if it's defined.
>
>
--
Mike Madore
Software Engineer
TurboLinux, Inc.
next prev parent reply other threads:[~2001-02-23 19:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 16:05 [Linux-ia64] Re: Lockups on 2.4.1 Bill Nottingham
2001-02-21 17:16 ` Gerrit Huizenga
2001-02-21 17:57 ` David Mosberger
2001-02-21 18:58 ` Chris McDermott
2001-02-21 21:02 ` David Mosberger
2001-02-23 15:19 ` Jun Nakajima
2001-02-23 19:06 ` Seth, Rohit
2001-02-23 19:20 ` Michael Madore [this message]
2001-02-23 19:48 ` Seth, Rohit
2001-02-23 20:00 ` Jesse Barnes
2001-02-24 13:39 ` Francis Galiegue
2001-02-24 14:44 ` Francis Galiegue
2001-02-24 18:45 ` Michael Madore
2001-02-24 23:18 ` Joseph V Moss
2001-02-25 2:43 ` Francis Galiegue
2001-02-26 20:52 ` Jim Wilson
2001-03-07 3:51 ` [linux-ia64] " Tom King
2001-03-07 20:34 ` Jim Wilson
2001-03-08 3:45 ` Tom King
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=marc-linux-ia64-105590693005193@msgid-missing \
--to=mmadore@turbolinux.com \
--cc=linux-ia64@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