| 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: <36D9DB17C6DE9E40B059440DB8D95F52064B1CE4@orsmsx418.amr.corp.intel.com> Date: Mon, 29 Sep 2008 19:30:05 -0700 From: "Brandeburg, Jesse" <jesse.brandeburg@...el.com> To: "Linus Torvalds" <torvalds@...ux-foundation.org>, "Jiri Kosina" <jkosina@...e.cz> Cc: "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org> Subject: RE: Linux 2.6.27-rc8 Linus Torvalds wrote: > 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? my current status mail was posted earlier today to lkml from this address, since then we've had a local reproduction and are going for number two. The reproduction seems racy, i.e. it doesn't happen every time, so we put it in a loop doing detect, check eeprom, detect, etc, and we'll see if it fails. Reproduction seems to consistently be around X probing time, no firm leads yet. As for Intel we have keithp and jbarnes as well as arjan, auke, myself and a few others involved. We have some patches to lock the nvm down, we'll be posting those tonight and tomorrow, I also have some debug logic (and fixes) to help prove that we don't think it's a race in e1000e. -- Jesse -- 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