| 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: <53721E7C.3090406@gmail.com> Date: Tue, 13 May 2014 15:30:36 +0200 From: Daniel Mack <zonque@...il.com> To: George Cherian <george.cherian@...com>, linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org, linux-omap@...r.kernel.org CC: balbi@...com, gregkh@...uxfoundation.org Subject: Re: [PATCH v3 0/5] Add support for SW babble Control On 05/13/2014 03:24 PM, George Cherian wrote: > Basically, there are 2 types of babble conditions. > 1) Transient babble condition - which could be recovered from without an > IP reset . > 2) Babble condition - which could be recovered from only by doing an IP > reset. Ok, thanks for the explanation. > Looks like you are always hitting case 2 (Most times am also hitting the > same). Seems like, yes. > There is no 100% reliable method to force it to happen. Following is > my setup , > I have a HUB with 4 devices connected , which gives me a Babble interrupt > on both connects and disconnects ( Not always though). I also get them at disconnects, but only with one specific USB device. But as I don't ever see case 1) above, I can't say if your approach works. What I can say, though, is that your patches don't break the recovery from babble conditions that I experienced :) Daniel -- 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