From: David Howells <dhowells@cambridge.redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Dual PPro timer stopping problem
Date: Thu, 03 Oct 2002 15:36:23 +0100 [thread overview]
Message-ID: <14734.1033655783@warthog.cambridge.redhat.com> (raw)
In-Reply-To: Your message of "03 Oct 2002 15:24:36 BST." <1033655076.28007.22.camel@irongate.swansea.linux.org.uk>
> Does this happen with "noapic" ?
Interesting:
[root@host164 root]# cat /proc/interrupts
CPU0 CPU1
0: 150710 0 XT-PIC timer
1: 15 0 XT-PIC i8042
2: 0 0 XT-PIC cascade
11: 457 0 XT-PIC eth0
14: 74220 0 XT-PIC ide0
NMI: 35480 150619
LOC: 150451 150454
ERR: 0
MIS: 0
Lots of zeros in the CPU1 column.
It's still going though.
David
next prev parent reply other threads:[~2002-10-03 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 14:03 Dual PPro timer stopping problem David Howells
2002-10-03 14:24 ` Alan Cox
2002-10-03 14:36 ` David Howells [this message]
2002-10-03 17:29 ` george anzinger
2002-10-03 20:46 ` Benjamin LaHaise
2002-10-03 21:19 ` george anzinger
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=14734.1033655783@warthog.cambridge.redhat.com \
--to=dhowells@cambridge.redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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