linux-kernel - Re: 2.6.27.19 + 28.7: network timeouts for r8169 and 8139too

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200905101209.15634.lkml@morethan.org>
Date:	Sun, 10 May 2009 12:09:12 -0500
From:	"Michael S. Zick" <lkml@...ethan.org>
To:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.27.19 + 28.7: network timeouts for r8169 and 8139too

On Sun May 10 2009, Michael Riepe wrote:
> 
> Michael Buesch wrote:
> 
> >>It seems to me that this particular chip really doesn't like MSI.
> > 
> > 
> > I can confirm this. I tried with msi enabled and it starts breaking
> > after a few seconds of heavy transfers. Disabling MSI results in a reliable connection.
> > 
> > Maybe we should disable MSI as temporary workaround for affected chips?
> 
> Yep. It may not solve the problem, but it's a lot better than turning
> MSI off for everything, including apparently working NICs that use the
> same driver(s).
> 

Lucky people, at least you have a device specific driver.  ;)
No device specific driver for the Via PCI-to-PCIe bridge (1106:324B)
used in the CX700 chip set.
(and the 8139too driver is not acting up on this machine.)

Not a problem in my case, building without MSI support gives up very little.

Mike
--
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/