| 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: <4C10EFB6.3020500@canonical.com> Date: Thu, 10 Jun 2010 07:59:18 -0600 From: Tim Gardner <tim.gardner@...onical.com> To: Jesse Brandeburg <jesse.brandeburg@...il.com> CC: e1000-devel@...ts.sourceforge.net, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: e1000e probe failure on 2.6.34 and higher, Intel MB Hi, http://bugs.launchpad.net/bugs/591707 I've a bug where e1000e works with Lucid (2.6.32), but fails to probe with 2.6.35-rc2. The output is mighty terse. [ 28.193628] e1000e 0000:00:19.0: PCI INT A disabled [ 28.193740] e1000e: probe of 0000:00:19.0 failed with error -3 The full dmesg logs are at https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/591707/comments/23 and https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/591707/comments/24 The reporter says that it also fails with 2.6.34. The report has logs showing that it works with 2.6.32 and fails with 2.6.35-rc1. I've requested the reporter install a vanilla -rc2 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc2-maverick/linux-image-2.6.35-020635rc2-generic_2.6.35-020635rc2_amd64.deb, but I do not expect different results given that the only change from rc1 to rc2 is 'e1000e: change logical negate to bitwise' (which is not germane to probing). This appears to be an Intel OEM MB as far as I can tell from the DMI. It was new in April so is unlikely to have flash corruption issues such as those observed with 2.6.24. Any suggestions on why the probe silently fails? None of the module params look like they'll make a difference. rtg -- Tim Gardner tim.gardner@...onical.com -- 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