From: Randy Dunlap <randy.dunlap@oracle.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: Len Brown <lenb@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: x86 instability with 2.6.1{8,9}
Date: Sat, 6 Jan 2007 14:04:59 -0800 [thread overview]
Message-ID: <20070106140459.a6b72039.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070102193459.GA19894@deepthought>
On Tue, 2 Jan 2007 19:34:59 +0000 Ken Moffat wrote:
> On Tue, Jan 02, 2007 at 01:42:32PM -0500, Len Brown wrote:
> >
> > You might remove and re-insert the DIMMS.
> > Sometimes there are poor contacts if the DIMMS are not fully seated and clicked in.
> >
> > The real mystery is the 32 vs 64-bit thing.
> > Are the devices configured the same way -- ie are they both in IOAPIC mode
> > and /proc/interrupts looks the same for both modes?
> >
> > -Len
>
> Too late, I've started memtest-86+. If it seems ok after an
> overnight run, I'll take a look at /proc/interrupts. How can I tell
> it is in IOAPIC mode, please ? Google was not helpful for this, but
> if it's an override, the only things on my command lines are root=
> and video= settings.
(did anyone ever answer this?)
In IO-APIC mode, /proc/interrupts contains entries like these:
CPU0 CPU1
0: 121218123 0 IO-APIC-edge timer
1: 715259 0 IO-APIC-edge i8042
6: 5 0 IO-APIC-edge floppy
7: 0 0 IO-APIC-edge parport0
9: 0 0 IO-APIC-level acpi
12: 10011272 0 IO-APIC-edge i8042
14: 11561548 0 IO-APIC-edge ide0
66: 4525183 0 PCI-MSI libata
74: 1711 0 IO-APIC-level ehci_hcd:usb1, uhci_hcd:usb6
82: 4 0 IO-APIC-level ohci_hcd:usb2, ohci_hcd:usb3, ohci_hcd:usb4, ohci_hcd:usb5
98: 101326 0 PCI-MSI HDA Intel
106: 17747181 0 PCI-MSI eth0
169: 0 0 IO-APIC-level uhci_hcd:usb9
177: 3 0 IO-APIC-level ohci1394
185: 15 0 IO-APIC-level uhci_hcd:usb8, aic79xx
193: 427962 0 IO-APIC-level uhci_hcd:usb7, aic79xx
If not in IO-APIC mode, lots of those will say "XT-PIC" instead
of IO-APIC.
> Certainly, it seems likely that the configs could be fairly
> different in their detail.
---
~Randy
next prev parent reply other threads:[~2007-01-06 22:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-01 16:01 x86 instability with 2.6.1{8,9} Ken Moffat
2007-01-01 16:48 ` Alistair John Strachan
2007-01-01 17:07 ` Ken Moffat
2007-01-01 19:13 ` Ken Moffat
2007-01-01 19:45 ` Alistair John Strachan
2007-01-02 17:25 ` Len Brown
2007-01-02 18:04 ` Ken Moffat
2007-01-02 18:42 ` Len Brown
2007-01-02 19:34 ` Ken Moffat
2007-01-06 22:04 ` Randy Dunlap [this message]
2007-01-07 14:26 ` Ken Moffat
2007-01-15 16:29 ` Ken Moffat
2007-01-25 23:56 ` Ken Moffat
2007-01-31 21:36 ` Chuck Ebbert
2007-01-31 23:26 ` Ken Moffat
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=20070106140459.a6b72039.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zarniwhoop@ntlworld.com \
/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.