netdev - Re: Strange igb bug, out-of-tree driver seems to work fine.

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: <4DB0F965.4080605@candelatech.com>
Date:	Thu, 21 Apr 2011 20:43:33 -0700
From:	Ben Greear <greearb@...delatech.com>
To:	"Wyborny, Carolyn" <carolyn.wyborny@...el.com>
CC:	netdev <netdev@...r.kernel.org>
Subject: Re: Strange igb bug, out-of-tree driver seems to work fine.

On 04/21/2011 05:16 PM, Wyborny, Carolyn wrote:
>
>
>> -----Original Message-----
>> From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
>> On Behalf Of Ben Greear
>> Sent: Thursday, April 21, 2011 2:39 PM
>> To: netdev
>> Subject: Strange igb bug, out-of-tree driver seems to work fine.
>>
>> We have a 4-port NIC using the igb driver in a couple of systems,
>> and saw some strange issues (mostly rx CRC errors).  We tried 2.6.34,
>> 2.6.36, and 2.6.38 based kernels and all showed issues.  The NICs
>> are from two different vendors, though both use the igb driver.
>>
>> We then tried 2.6.36.3 with the out-of-tree igb-2.4.13.tar.gz
>> driver.  And everything seems to run clean.
>>
>> My kernels are somewhat hacked and tainted, and this testing
>> is using my tainting module, but since changing only the driver
>> seems to fix things, it's _probably_ not my fault this time!
>>
>> I am running a small hack to make igb work better with VLANs
>> in my 2.6.36 and .38 kernel, though not in the .34.  Here is the .36
>> diff:

>
> Hello,
>
> There have been recent patches for igb that I submitted that might contain the fix you found in the out-of-tree driver, although I'm not sure which one would affect rx CRC errors.  Were there other symptoms?  Any messages in the log?  I'll look through the patches and see if there is anything obvious and get you some commit numbers to try.

There was nothing else that I noticed.  If your patches are in 2.6.39-rc4+, I can try
them there perhaps?

Thanks,
Ben


-- 
Ben Greear <greearb@...delatech.com>
Candela Technologies Inc  http://www.candelatech.com
--
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