From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] fix timer interrupts getting lost
Date: Tue, 06 May 2003 18:59:39 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705644@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705596@msgid-missing>
>>>>> On Wed, 23 Apr 2003 22:16:43 -0600, Alex Williamson <alex_williamson@attbi.com> said:
Alex> This patch fixes the issue of some CPUs not showing timer
Alex> interrupts going off. Seems during the process of sync'ing
Alex> the itc, we jumped over the next timer value. This patch is
Alex> against 2.5.67 + ia64. I haven't seen the problem on 2.4, but
Alex> a quick looks seems like it's potentially an issue there too.
Alex> Thanks,
Good catch. I applied this patch now.
The reason it started to show up on 2.5 now is mostly likely because I
had to move the ITC syncing to a point where interrupts are enabled.
--david
next prev parent reply other threads:[~2003-05-06 18:59 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
2003-05-06 18:59 ` David Mosberger [this message]
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-105590723705644@msgid-missing \
--to=davidm@napali.hpl.hp.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