| 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: <483B0986.70606@krogh.cc> Date: Mon, 26 May 2008 21:03:34 +0200 From: Jesper Krogh <jesper@...gh.cc> To: David Miller <davem@...emloft.net> CC: yhlu.kernel@...il.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: NIU - Sun Neptune 10g - Transmit timed out reset (2.6.24) Jesper Krogh wrote: > David Miller wrote: >> From: Jesper Krogh <jesper@...gh.cc> >> Date: Sat, 10 May 2008 13:01:08 +0200 >> >>> Any good suggestions about the "Transmit timed out" messages. It >>> currently leads to a system that "doesnt die" but doesnt respond within >>> 15 minutes of load of the network adapter. >> >> It's likely some bug in the driver that hangs the card for whatever >> reason, which we'll need to work out. > > Ok. I have been testing a bit more. It generally works fine, It seems > the "transmit timed out" thing was provoked by dd in the tests, because > it was creating a lot of small requests. (default bs=512).(over NFS). > When the blocksize went up, the problem dissapered. (and the numer of > context-switches went down). Ok. Now I also hit it in production with the NFS-server, so this is definately a real bug somewhere in the driver. Should I register it at bugzilla? $ sudo grep -ci "Transmit timed out" /var/log/messages 1007 And only a hard reboot brought it back online. 2.6.25.2 -- Jesper -- 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