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: Fri, 28 Nov 2008 11:18:27 -0600 From: Jay Cliburn <jcliburn@...il.com> To: Arjan van de Ven <arjan@...ux.intel.com> Cc: NetDev <netdev@...r.kernel.org> Subject: Re: oops/warning report for the week of November 26, 2008 [trimmed the cc list down to netdev only] On Wed, 26 Nov 2008 15:11:14 -0800 Arjan van de Ven <arjan@...ux.intel.com> wrote: > Rank 12: dev_watchdog(atl1) (oops) > Reported 56 times (109 total reports) > This oops was last seen in version 2.6.27.5, and first seen > in 2.6.26.6. More info: > http://www.kerneloops.org/searchweek.php?search=dev_watchdog(atl1) I can't reproduce this, so I've launched a request at fedoraforum.org hoping I can snag a Fedora user who's encountering the bug and willing to test. The tx timeout reports at kerneloops.org appear to be happening on a startling variety of network drivers (startling to me, anyway): r8169, atl1, atl2, sis900, cdc_ether, orinoco_cs, tg3, ne2k-pci, via-rhine, 8139too, ath_pci, e1000, gl620a, sky2, hso, fealnx, forcedeth; probably others, but I quit looking. Is it correct to assume all these drivers are showing symptoms of the poor timeout handling you mentioned in your r8169 comment, or is the occasional tx timeout to be expected, and the leaders in this category (r8169, sis900, atl1) are the only ones suffering from deficient timeout handling? Jay -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists