linux-kernel - Re: e1000 issue on DQ965GF board (was 24 lost ticks with 2.6.20.10 kernel)

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:	Fri, 4 May 2007 14:15:48 -0700
From:	Michel Lespinasse <walken@....org>
To:	"Kok, Auke" <auke-jan.h.kok@...el.com>
Cc:	Chuck Ebbert <cebbert@...hat.com>, linux-kernel@...r.kernel.org,
	Dave Jones <davej@...hat.com>, Jeb Cramer <cramerj@...el.com>,
	John Ronciak <john.ronciak@...el.com>,
	Jesse Brandeburg <jesse.brandeburg@...el.com>,
	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Subject: Re: e1000 issue on DQ965GF board (was 24 lost ticks with 2.6.20.10  kernel)

On Fri, May 04, 2007 at 11:25:43AM -0700, Kok, Auke wrote:
> can you try turning off the "management enable" function in the BIOS of the 
> DQ965GF? That fixes this issue for us in our labs. A fix for this is also 
> available in our standalone 7.5.5.1 driver (obtainable from e1000.sf.net), 
> but it hasn't made it upstream yet.

Done. Indeed, this fixed the issue. Thanks!

The interesting thing is that I *thought* I had it off, as I had never
touched this menu or set a password on it. The manual said that the board
would not be accessible from the network until I set a password, which I
had (incorrectly) assumed to mean the ME feature would be off. To turn off
the option (or even see I had it on) I had to google for the default
ME password, which turned out to be 'admin'.

Thanks for the help,

-- 
Michel "Walken" Lespinasse
"Bill Gates is a monocle and a Persian cat away from being the villain
in a James Bond movie." -- Dennis Miller
-
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/