All of lore.kernel.org
 help / color / mirror / Atom feed
From: Einar Saltnes <eisa@scali.no>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] clock stops on test9
Date: Tue, 17 Oct 2000 14:49:35 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205574@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205567@msgid-missing>

"Ahna, Christopher J" wrote:
> 
> Einar,
> 
> Are you building your test9 kernel with A1-specific fixes enabled?
> A1-specific fixes deal with interrupt handling and have historically caused
> problems like the one you're seeing on non-A1 stepping Itaniums.  Thanks,
> 
> Chris
> 
Hi,

on my Dual B1-stepping Itanium I have now only enabled the
BSTEP_SPECIFIC setting. But the clock will still stop after some time.

On my UP A2-stepping Itanium, however, I have enabled both the ASTEP_-
and the A1_SPECIFIC setting. On this machine it doesn't seem to be a
problem with the clock. Uptime today is four days.

As David M. pointed out, I will compile a new kernel enabling only the
ASTEP_SPECIFIC setting for the A2-stepping BigSur as this will be the
correct configuration for the actual processor.

I will also make some tests on a Dual A3-stepping BigSur with BIOS 60
which just came in my door...

Thanks!

Einar
-- 
| Einar Saltnes          |         Scali AS         |
| mailto:eisa@scali.no   |   http://www.scali.com   |
| Phone:+47 22 62 89 50  |  Scalable Linux Systems  |
| Fax  :+47 22 62 89 51  |      and Technology      |


  parent reply	other threads:[~2000-10-17 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-13  9:55 [Linux-ia64] clock stops on test9 Einar Saltnes
2000-10-13 16:26 ` David Mosberger
2000-10-17 14:25 ` Einar Saltnes
2000-10-17 14:49 ` Einar Saltnes [this message]
2000-10-18  2:05 ` Takayoshi Kouchi
2000-10-18  9:53 ` Einar Saltnes

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-105590678205574@msgid-missing \
    --to=eisa@scali.no \
    --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 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.