From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: Craig Bradney <cbradney@zip.com.au>
Cc: ross@datscreative.com.au, recbo@nishanet.com,
linux-kernel@vger.kernel.org
Subject: Re: Fwd: Re: Working nforce2, was Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered
Date: Mon, 15 Dec 2003 16:56:01 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.55.0312151652260.22939@jurand.ds.pg.gda.pl> (raw)
In-Reply-To: <1071500545.6680.15.camel@athlonxp.bradney.info>
On Mon, 15 Dec 2003, Craig Bradney wrote:
> CPU0
> 0: 245382420 IO-APIC-edge timer
> 1: 139577 IO-APIC-edge i8042
> 2: 0 XT-PIC cascade
> 8: 3 IO-APIC-edge rtc
> 9: 0 IO-APIC-level acpi
> 12: 1478615 IO-APIC-edge i8042
> 14: 1055548 IO-APIC-edge ide0
> 15: 737664 IO-APIC-edge ide1
> 19: 18405692 IO-APIC-level radeon@PCI:3:0:0
> 21: 5257090 IO-APIC-level ehci_hcd, NVidia nForce2, eth0
> 22: 3 IO-APIC-level ohci1394
> NMI: 14944
> LOC: 245087891
> ERR: 0
> MIS: 6
>
> As for NMI.. I actually forget which I booted from... I think =1, but NMI is a small number now.. would it have wrapped?
That's "=2" -- otherwise the NMI count would be rougly the same as the
sum of counts for IRQ 0 for all processors. And you can actually get your
kernel's command line from /proc/cmdline.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
next prev parent reply other threads:[~2003-12-15 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 14:30 Fwd: Re: Working nforce2, was Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered Ross Dickson
2003-12-15 15:02 ` Craig Bradney
2003-12-15 15:56 ` Maciej W. Rozycki [this message]
2003-12-15 16:54 ` Ross Dickson
2003-12-16 6:07 ` Bob
[not found] <200312132040.00875.ross@datscreative.com.au>
2003-12-13 12:00 ` Fwd: " Bob
2003-12-15 13:11 ` Maciej W. Rozycki
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=Pine.LNX.4.55.0312151652260.22939@jurand.ds.pg.gda.pl \
--to=macro@ds2.pg.gda.pl \
--cc=cbradney@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=recbo@nishanet.com \
--cc=ross@datscreative.com.au \
/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;
as well as URLs for NNTP newsgroup(s).