[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9929d2390911031337p6115fef0wc1b94e5141ead341@mail.gmail.com>
Date: Tue, 3 Nov 2009 13:37:47 -0800
From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To: Naohiro Ooiwa <nooiwa@...aclelinux.com>
Cc: jesse.brandeburg@...el.com, peter.p.waskiewicz.jr@...el.com,
john.ronciak@...el.com, davem@...emloft.net,
Andrew Morton <akpm@...ux-foundation.org>,
netdev@...r.kernel.org, svaidy@...ux.vnet.ibm.com,
e1000-devel@...ts.sourceforge.net
Subject: Re: [PATCH] e1000: the power down when running ifdown command
2009/11/3 Naohiro Ooiwa <nooiwa@...aclelinux.com>:
> Jeff Kirsher wrote:
>> 2009/10/31 Naohiro Ooiwa <nooiwa@...aclelinux.com>:
>>
>> I have added this patch to my tree for testing. This patch requires a
>> fair amount of regression testing, so once its passed testing I will
>> push the patch to David/netdev.
>
> I appreciate the marge your tree.
> If there is anything I can do, please let me know.
>
> And I know this patch is good for e100 driver too.
> I would really like to create patch for it.
> How do you think about e100 driver.
>
>
> Thanks,
> Naohiro Ooiwa
>
Patches are always welcome (referring to a e100 patch).
As far as the e1000 patch goes, it has a number of issues which were
found in testing. Here are just a few problems we saw:
1. ethtool -t - crashes the system
2. ethtool eth0 - always shows link/speed as 1000/Full even when there
is no cable
3. ethtool -s eth0 autoneg on/off - system hang. Sometimes a copper
interface will show up as fiber after this.
4. ethtool -d/-S/-g etc - will corrupt the stats of the interface
while doing ifup/down
So it appears that more needs to be done to the driver to get this to
work as expected.
NAK
--
Cheers,
Jeff
--
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