linux-kernel - RE: [E1000-devel] Intel dg45fc motherboard still bricks with e1000e driver

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]

Date:	Mon, 1 Dec 2008 13:08:35 -0700
From:	"Tantilov, Emil S" <emil.s.tantilov@...el.com>
To:	Steve Moring <smoring@...oo.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>
Subject: RE: [E1000-devel] Intel dg45fc motherboard still bricks with e1000e
	driver

Steve Moring wrote:
> I don't know if I should enter a bug on this or not as I thought this
> one was fixed already, but I have an Intel dg45fc that comes with a
> gig enet card built in. If I force the connection to 100mb by
> connecting a switch that is only capable of 100mb, all is good, as soon > as I connect it to a gig capable switch, it bricks the machine on the > > next reboot forcing me to reload the bios.

Please file a bug so we can track this issue.

By "reload" do you mean reflash the BIOS? Can you be more specific about the symptoms?

> I have tried the following combinations: x86_64 with and without XEN,
> i586 with and without XEN, all behave identically with the above
> observations.

The NVM corruption issue that was resolved (I presume this is what you meant) was root caused to CONFIG_FTRACE being enabled in the kernel and only on ia32 arch. If you're seeing this problem on x86_64 then it is most likely unrelated.

I also presume that you are using e1000e that ships with OpenSUSE 11.1. Have you tried using the latest e1000e from sourceforge?

Thanks,
Emil
--
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/