| 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: Tue, 20 Nov 2007 00:24:49 +0100 From: Francois Romieu <romieu@...zoreil.com> To: Denys <nuclearcat@...learcat.com> Cc: netdev@...r.kernel.org Subject: Re: r8169 crash Denys <nuclearcat@...learcat.com> : > Maybe it is good idea to print some registers/etc in watchdog message? > > I will try to reproduce problem with debug enabled, maybe it will be possible > to catch problem with more debug. Your customers will not necessarily like it but it could be useful to trace the Rx/Tx descriptor ring content and the irq status word. If your make it dependent on tp->msg_enable (settable via 'ethtool -s ethX msglvl 65535), you can enable it at will and catch some bit of normal traffic just before you experiment with the magic cable. > On Sun, 18 Nov 2007 22:00:38 +0100, Francois Romieu wrote > > Denys <nuclearcat@...learcat.com> : [...] > > I'll take care of it once I am done with the sis190 watchdog failure > > (nothing hard, simply ugly). Actually I lack a reliable indication that the Tx process is stuck. My hack seems able to recover but it can be quite slow to trigger. A contact at SiS would be welcome. -- Ueimor - 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