| 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
| ||
|
Message-Id: <20080923.140519.268233735.davem@davemloft.net> Date: Tue, 23 Sep 2008 14:05:19 -0700 (PDT) From: David Miller <davem@...emloft.net> To: jkosina@...e.cz Cc: david.vrabel@....com, airlied@...il.com, rjw@...k.pl, linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org, chrisl@...are.com Subject: Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM From: Jiri Kosina <jkosina@...e.cz> Date: Tue, 23 Sep 2008 16:29:16 +0200 (CEST) > On Mon, 22 Sep 2008, David Miller wrote: > > > So I went through the changes from 2.6.27-rc5 until the SHA1 > > ID ec0c15afb41fd9ad45b53468b60db50170e22346 and there were > > definitely no E1000 or E1000E changes during that time. > > Some recent comments on [1] seem to indicate that this is somehow coupled > into prior problems/panics with Intel graphics. My current suspicion in all of this is either the GEM kernel patches or recent X server. However, the eeprom/nvram programming sequence seems non-trivial on the e1000e. You have to execute a set of precise register writes and register polls to successfully write things out to the nvram. This makes something like a random scribble out to MMIO space less likely to cause this problem. Is there some linear mapping of the nvram that could be written to on these cards? -- 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