| 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: <1203549449.13495.140.camel@dell> Date: Wed, 20 Feb 2008 15:17:29 -0800 From: "Michael Chan" <mchan@...adcom.com> To: "David Miller" <davem@...emloft.net> cc: tonyb@...ernetics.com, mcarlson@...adcom.com, herbert@...dor.apana.org.au, netdev <netdev@...r.kernel.org>, gregkh@...e.de, linux-kernel@...r.kernel.org Subject: Re: TG3 network data corruption regression 2.6.24/2.6.23.4 On Wed, 2008-02-20 at 15:08 -0800, David Miller wrote: > From: Tony Battersby <tonyb@...ernetics.com> > Date: Wed, 20 Feb 2008 18:04:09 -0500 > > > The following patch fixes the problem for me. Do we want to accept this > > patch and call it a day or continue investigating the source of the problem? > > > > Patch applies to 2.6.24.2, but doesn't apply to 2.6.25-rc. If everyone > > agrees that this is the right solution, I will resubmit with a proper > > subject line and description. > > A chipset bug, if it even exists, should be worked around in the > driver for that hardware. We shouldn't make every other piece > of hardware in the world suffer too. > > Yes, we should workaround this in the TG3 driver once we understand what the problem is and how to workaround it. We are still looking through the errata list to sort this out. It looks like it is the starting DMA address of the TX buffer that is causing the problem. -- 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