lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 6 Jan 2007 14:04:59 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Ken Moffat <zarniwhoop@...world.com>
Cc:	Len Brown <lenb@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: x86 instability with 2.6.1{8,9}

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ