| 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: <4601AB37.7070302@redhat.com> Date: Wed, 21 Mar 2007 18:01:27 -0400 From: Chuck Ebbert <cebbert@...hat.com> To: Stephen Hemminger <shemminger@...ux-foundation.org> CC: linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: sky2 still broken in 2.6.20.3 Stephen Hemminger wrote: > On Wed, 21 Mar 2007 16:26:53 -0400 > Chuck Ebbert <cebbert@...hat.com> wrote: > >> Transmit timeouts and locked-up adapters still occur in kernel >> 2.6.20.3. > > There is more changes in 2.6.21-rc4 please try that. Yes, but I have to figure out how to get those to apply to 2.6.20.3. I was hoping you'd do that. :) > I am still getting reports of timeouts with that code but > it does recover better. It may be the case that with hardware > flow control transmits can take an indefinite period so increasing > the timeout value could help. > >> It looks like the patch that was applied to 2.6.20.2 >> is not enough. Unfortunately that one isn't the same as what >> went upstream. Looks like it needs to be reverted, then the two >> upstream patches applied? > > Until, unless the problem is reproducible with my hardware > there is not much that can be done. I'll add the better recovery > logic to for next stable cycle, but still not clear what causes > all the timeouts. I have a bug report and tester: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227420 - 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