| 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: Wed, 14 Sep 2011 09:48:21 -0400 From: Chris Ball <cjb@...top.org> To: Jeremy Fitzhardinge <jeremy@...p.org> Cc: Philip Rakity <prakity@...vell.com>, "linux-mmc\@vger.kernel.org" <linux-mmc@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Manoj Iyer <manoj.iyer@...onical.com> Subject: Re: SDHCI regression since 2.6.39 Hi Jeremy, On Tue, Sep 13 2011, Jeremy Fitzhardinge wrote: > Very strange. I reinstalled the original 2.6.38-based F15 kernel > (kernel-2.6.38.6-26.rc1.fc15.x86_64) which I'm sure did work, and it is > failing in the same way. So I guess some BIOS setting changed, or the > hardware itself has died? But it's still there; it does appear on the > PCI bus, and it does respond to the driver to some extent (register > dumps aren't all 0xff, etc). Long shot, but did you try removing power completely between the reboots? I wonder if the PCI config space write patch could be (a) bogus for your device, and (b) preserved across warm reboot by your PCI hardware. So, you could just try removing the battery and PSU, hitting the power button a few times with them unplugged to discharge caps, and then boot into the old kernel again. Thanks, - Chris. -- Chris Ball <cjb@...top.org> <http://printf.net/> One Laptop Per Child -- 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