linux-kernel - RE: [E1000-devel] e1000e probe failure on 2.6.34 and higher, Intel MB

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] [day] [month] [year] [list]

Message-ID: <DDC57477F5D6F845A0DDCB99D3C4812D0CA6A93F56@orsmsx510.amr.corp.intel.com>
Date:	Thu, 10 Jun 2010 08:44:42 -0700
From:	"Ronciak, John" <john.ronciak@...el.com>
To:	"tim.gardner@...onical.com" <tim.gardner@...onical.com>,
	Jesse Brandeburg <jesse.brandeburg@...il.com>
CC:	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [E1000-devel] e1000e probe failure on 2.6.34 and higher, Intel
 MB

Tim,

> [   28.193628] e1000e 0000:00:19.0: PCI INT A disabled
> [   28.193740] e1000e: probe of 0000:00:19.0 failed with error -3
This looks like a BIOS problem.  It looks the interrupts aren't being setup correctly in the system and the driver can't request them.  Why it's working on some kernels and not others may be do to some BIOS setup with the interrupts that happens in one and not in the other.  Does the MB have the latest BIOS on it?  Please make sure and test it again if not.


Cheers,
John


--
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/