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]
Message-ID: <20090907013328.GA19670@khazad-dum.debian.net>
Date:	Sun, 6 Sep 2009 22:33:28 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Stefan Assmann <sassmann@...hat.com>
Cc:	linux-kernel@...r.kernel.org, jcm@...hat.com, sdietrich@...ell.com,
	linux-acpi@...r.kernel.org, andi@...stfloor.org, hpa@...or.com,
	mingo@...e.hu, Olaf.Dabrunz@....net, ktokunag@...hat.com,
	tglx@...utronix.de, lenb@...nel.org
Subject: Re: [RFC][PATCH 0/2] boot interrupts on Intel X58 and 55x0

On Fri, 04 Sep 2009, Stefan Assmann wrote:
> is more serious namely the onboard NIC (8086:10c9) is malfunctioning on some
> of our test system if the second patch is applied. It fails to acquire an IP
> from DHCP and we're pretty clueless on this issue right now.
> Help is greatly appreciated!

Did you read Intel documet 320839-009, August/2009, already?  It is at:
http://www.intel.com/Assets/PDF/specupdate/320839.pdf

I see some stuff there that might be a problem, many of the "issues" are
related to interrupt handling.  Errata 40 (EOI to IOAPIC can be blocked)
even states that one should avoid the X58 IOH IOAPIC on stepping B2
completely, and use the IOAPIC in the ICH10R instead.

And the B2 stepping is the one in most motherboards (B3 is quite new).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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