> -Original Message-
> From: Andy Lutomirski [mailto:l...@amacapital.net]
> Sent: Thursday, March 14, 2013 3:43 PM
> To: Allan, Bruce W
> Cc: Network Development; e1000-devel@lists.sourceforge.net
> Subject: Re: em1 is visible to iproute2 but not ethtool or tcpdump
>
> On Thu, Mar 14, 2013
I believe these error messages are already logged
on allocation failure by warn_alloc_failed and so
get a dump_stack on OOM.
Remove the unnecessary additional error logging.
Around these deletions:
o Alignment neatening.
o Remove unnecessary casts of dma_alloc_coherent.
o Hoist assigns from ifs.
On Thu, Mar 14, 2013 at 1:45 PM, Allan, Bruce W wrote:
>> -Original Message-
>> From: netdev-ow...@vger.kernel.org [mailto:netdev-
>> ow...@vger.kernel.org] On Behalf Of Andy Lutomirski
>> Sent: Thursday, March 14, 2013 9:54 AM
>> To: Network Development
>> Cc: e1000-devel@lists.sourceforg
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of Andy Lutomirski
> Sent: Thursday, March 14, 2013 9:54 AM
> To: Network Development
> Cc: e1000-devel@lists.sourceforge.net
> Subject: em1 is visible to iproute2 but not ethtool or
My e1000e device is em1. It has this rather strange behavior on
Fedora's 3.8.1 (although 3.7.something did the same thing, I believe):
$ ip link show dev em1
6: em1: mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
link/ether f0:de:f1:59:f6:c9 brd ff:ff:ff:ff:ff:ff
$ strace -e socket,ioctl eth
