| 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
| ||
|
Date: Mon, 29 Sep 2008 18:56:17 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Jiri Kosina <jkosina@...e.cz> cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, jesse.brandeburg@...el.com Subject: Re: Linux 2.6.27-rc8 On Tue, 30 Sep 2008, Jiri Kosina wrote: > > Intel is working with us on tracking down and resolving the issue, but > this is not going as well as one would like to see (one attempt, one card > with completely hosed EEPROM contents ... and restoring the contents is > not *that* trivial). What's the magic to trigger it? I've got a laptop with that e1000e chip in it, and am obviously running a recent kernel on it. Do people have a handle on it? Is it actually verified to be kernel-related, and not related to the X server etc? Linus -- 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