public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Takayoshi Kochi <kochi@hpc.bs1.fc.nec.co.jp>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] fix timer interrupts getting lost
Date: Thu, 24 Apr 2003 11:56:46 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705598@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705596@msgid-missing>

Thanks Alex!

This patch fixed the problem I reported before.
And I could observe some "oops jumped a timer." messages
(with debug flag enabled).

>     This patch fixes the issue of some CPUs not showing timer interrupts
> going off.  Seems during the process of sync'ing the itc, we jumped over
> the next timer value.  This patch is against 2.5.67 + ia64.  I haven't
> seen the problem on 2.4, but a quick looks seems like it's potentially
> an issue there too.  Thanks,

>> Hi,
>> 
>> Thanks to Alex's fixes for PCI segment support, we could
>> boot 2.5.67 kernel on Tiger.  But a strange thing is happening.
>> Only cpu0 & 1 are getting timer interrupts and cpu 2 & 3 aren't.
>> This problem is reproducible and we see this phenomenon after every
>> boot.  It seems that these cpus stop receiving timer
>> interrupts after a very short while.
>> Has anyone seen this?

Thanks,
---
Takayoshi Kochi <kochi@hpc.bs1.fc.nec.co.jp>



  reply	other threads:[~2003-04-24 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24  4:16 [Linux-ia64] [PATCH] fix timer interrupts getting lost Alex Williamson
2003-04-24 11:56 ` Takayoshi Kochi [this message]
2003-05-06 18:59 ` David Mosberger
2003-05-09 20:44 ` Bjorn Helgaas

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-105590723705598@msgid-missing \
    --to=kochi@hpc.bs1.fc.nec.co.jp \
    --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