| 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: Sun, 21 Sep 2008 23:45:06 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: Marcel Holtmann <holtmann@...ux.intel.com> Cc: Evgeniy Polyakov <johnpol@....mipt.ru>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, ipw2100-devel@...ts.sourceforge.net, linux-wireless@...r.kernel.org, yi.zhu@...el.com, reinette.chatre@...el.com, jgarzik@...ox.com, linville@...driver.com, davem@...emloft.net Subject: Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware restart. On Sun, Sep 21, 2008 at 09:35:31PM +0200, Marcel Holtmann wrote: > I don't know if it is for this bug or a different one, but Matthew > Garrett seem to have some pending patches. At least that is what he told > me at PlumbersConf. Lets see if these patches do help. And please follow > up with Arjan's suggestion and put a WARN_ON in the upstream code > instead of waving CONFIG_BROKEN around. The fix I had for this was actually for ipw2200, but it ought to be applicable for 2100 as well. The ideal fix is probably to ensure that ipw*_down D3s the card and *_up D0s it, which brings enhanced runtime power saving and also has the nice side effect of actually resetting the damned POS in error cases. -- Matthew Garrett | mjg59@...f.ucam.org -- 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