<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/ethernet/intel/igb, branch linux-3.6.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.6.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.6.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2012-08-09T09:36:05Z</updated>
<entry>
<title>igb: Fix register defines for all non-82575 hardware</title>
<updated>2012-08-09T09:36:05Z</updated>
<author>
<name>Alexander Duyck</name>
</author>
<published>2012-08-08T05:18:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a2d6a1d5a435b051d3660961d5dee5b33b15f754'/>
<id>urn:sha1:a2d6a1d5a435b051d3660961d5dee5b33b15f754</id>
<content type='text'>
It looks like the register defines for DCA were never updated after going from
82575 to 82576.  This change addresses that by updating the defines.

Signed-off-by: Alexander Duyck &lt;alexander.h.duyck@intel.com&gt;
Tested-by: Jeff Pieper &lt;jeffrey.e.pieper@intel.com&gt;
Signed-off-by: Peter P Waskiewicz Jr &lt;peter.p.waskiewicz.jr@intel.com&gt;
</content>
</entry>
<entry>
<title>igb: fix panic while dumping packets on Tx hang with IOMMU</title>
<updated>2012-08-09T09:36:05Z</updated>
<author>
<name>Emil Tantilov</name>
</author>
<published>2012-07-28T05:07:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b669588abaceb5c6d70699b6c009e5cedc42449b'/>
<id>urn:sha1:b669588abaceb5c6d70699b6c009e5cedc42449b</id>
<content type='text'>
This patch resolves a "BUG: unable to handle kernel paging request at ..."
oops while dumping packet data. The issue occurs with IOMMU enabled due to
the address provided by phys_to_virt().

This patch avoids phys_to_virt() by making using skb-&gt;data and the address
of the pages allocated for Rx.

Signed-off-by: Emil Tantilov &lt;emil.s.tantilov@intel.com&gt;
Tested-by: Jeff Pieper &lt;jeffrey.e.pieper@intel.com&gt;
Signed-off-by: Peter P Waskiewicz Jr &lt;peter.p.waskiewicz.jr@intel.com&gt;
</content>
</entry>
<entry>
<title>igb: add delay to allow igb loopback test to succeed on 8086:10c9</title>
<updated>2012-08-07T07:47:51Z</updated>
<author>
<name>Stefan Assmann</name>
</author>
<published>2012-08-07T07:45:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=119b0e0351bcdb7833f368781e6241ff283b49e5'/>
<id>urn:sha1:119b0e0351bcdb7833f368781e6241ff283b49e5</id>
<content type='text'>
Some 8086:10c9 NICs have a problem completing the ethtool loopback test.
The result looks like this:

ethtool -t eth1
The test result is FAIL
The test extra info:
Register test  (offline)         0
Eeprom test    (offline)         0
Interrupt test (offline)         0
Loopback test  (offline)         13
Link test   (on/offline)         0

A bisect clearly points to commit a95a07445ee97a2fef65befafbadcc30ca1bd145.
However that seems to only trigger the bug. While adding some printk the
problem disappeared, so this might be a timing issue. After some trial and
error I discovered that adding a small delay just before igb_write_phy_reg()
in igb_integrated_phy_loopback() allows the loopback test to succeed.
I was unable to figure out the root cause so far but I expect it to be
somewhere in the following executing path
igb_integrated_phy_loopback
-&gt;igb_write_phy_reg_igp
  -&gt;igb_write_phy_reg_mdic
    -&gt;igb_acquire_phy_82575
      -&gt;igb_acquire_swfw_sync_82575

The problem could only be observed on 8086:10c9 NICs so far and not all
of them show the behaviour. I did not restrict the workaround to this
type of NIC as it should do no harm to other igb NICs.

With the patch below the loopback test succeeded 500 times in a row
using a NIC that would otherwise fail.

Signed-off-by: Stefan Assmann &lt;sassmann@kpanic.de&gt;
Tested-by: Aaron Brown &lt;aaron.f.brown@intel.com&gt;
Signed-off-by: Peter P Waskiewicz Jr &lt;peter.p.waskiewicz.jr@intel.com&gt;
</content>
</entry>
<entry>
<title>igb: don't break user visible strings over multiple lines in igb_ethtool.c</title>
<updated>2012-08-04T09:45:07Z</updated>
<author>
<name>Jesper Juhl</name>
</author>
<published>2012-08-01T05:41:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d836200a1c239a488cd2ed9867f4792f25f721d5'/>
<id>urn:sha1:d836200a1c239a488cd2ed9867f4792f25f721d5</id>
<content type='text'>
Even when they go beyond 80 characters, user visible strings should be
on one line to make them easy to grep for.

Signed-off-by: Jesper Juhl &lt;jj@chaosbits.net&gt;
Tested-by: Jeff Pieper &lt;jeffrey.e.pieper@intel.com&gt;
Signed-off-by: Peter P Waskiewicz Jr &lt;peter.p.waskiewicz.jr@intel.com&gt;
</content>
</entry>
<entry>
<title>igb: correct hardware type (i210/i211) check in igb_loopback_test()</title>
<updated>2012-08-04T09:44:29Z</updated>
<author>
<name>Jesper Juhl</name>
</author>
<published>2012-08-01T05:41:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=89d351c046c287f293b4b2fda1d76c4df44b95ce'/>
<id>urn:sha1:89d351c046c287f293b4b2fda1d76c4df44b95ce</id>
<content type='text'>
In the original code
...
 	if ((adapter-&gt;hw.mac.type == e1000_i210)
		|| (adapter-&gt;hw.mac.type == e1000_i210)) {
...
the second check of 'adapter-&gt;hw.mac.type' is pointless since it tests
for the exact same value as the first.

Signed-off-by: Jesper Juhl &lt;jj@chaosbits.net&gt;
Acked-by: Carolyn Wyborny &lt;carolyn.wyborny@intel.com&gt;
Tested-by: Jeff Pieper &lt;jeffrey.e.pieper@intel.com&gt;
Signed-off-by: Peter P Waskiewicz Jr &lt;peter.p.waskiewicz.jr@intel.com&gt;
</content>
</entry>
<entry>
<title>igb: Fix for failure to init on some 82576 devices.</title>
<updated>2012-08-04T09:43:47Z</updated>
<author>
<name>Carolyn Wyborny</name>
</author>
<published>2012-07-31T01:01:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=925b11f706642732ce2ae53b0f0d3fd54adc5075'/>
<id>urn:sha1:925b11f706642732ce2ae53b0f0d3fd54adc5075</id>
<content type='text'>
Move nvm invalid size check to before size assigned by mac_type for
82575 and later parts in get_invariants function.  This fixes a problem
found on some 82576 devices where the part will not initialize because
the nvm_read function pointer ends up getting assigned to the incorrect
function.

Reported By: Stefan Assmann &lt;sassmann@redhat.com&gt;
Signed-off-by: Carolyn Wyborny &lt;carolyn.wyborny@intel.com&gt;
Tested-by: Jeff Pieper &lt;jeffrey.e.pieper@intel.com&gt;
Signed-off-by: Peter P Waskiewicz Jr &lt;peter.p.waskiewicz.jr@intel.com&gt;
</content>
</entry>
<entry>
<title>netvm: propagate page-&gt;pfmemalloc from skb_alloc_page to skb</title>
<updated>2012-08-01T01:42:46Z</updated>
<author>
<name>Mel Gorman</name>
</author>
<published>2012-07-31T23:44:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0614002bb5f7411e61ffa0dfe5be1f2c84df3da3'/>
<id>urn:sha1:0614002bb5f7411e61ffa0dfe5be1f2c84df3da3</id>
<content type='text'>
The skb-&gt;pfmemalloc flag gets set to true iff during the slab allocation
of data in __alloc_skb that the the PFMEMALLOC reserves were used.  If
page splitting is used, it is possible that pages will be allocated from
the PFMEMALLOC reserve without propagating this information to the skb.
This patch propagates page-&gt;pfmemalloc from pages allocated for fragments
to the skb.

It works by reintroducing and expanding the skb_alloc_page() API to take
an skb.  If the page was allocated from pfmemalloc reserves, it is
automatically copied.  If the driver allocates the page before the skb, it
should call skb_propagate_pfmemalloc() after the skb is allocated to
ensure the flag is copied properly.

Failure to do so is not critical.  The resulting driver may perform slower
if it is used for swap-over-NBD or swap-over-NFS but it should not result
in failure.

[davem@davemloft.net: API rename and consistency]
Signed-off-by: Mel Gorman &lt;mgorman@suse.de&gt;
Acked-by: David S. Miller &lt;davem@davemloft.net&gt;
Cc: Neil Brown &lt;neilb@suse.de&gt;
Cc: Peter Zijlstra &lt;a.p.zijlstra@chello.nl&gt;
Cc: Mike Christie &lt;michaelc@cs.wisc.edu&gt;
Cc: Eric B Munson &lt;emunson@mgebm.net&gt;
Cc: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Cc: Sebastian Andrzej Siewior &lt;sebastian@breakpoint.cc&gt;
Cc: Mel Gorman &lt;mgorman@suse.de&gt;
Cc: Christoph Lameter &lt;cl@linux.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>igb: reset PHY in the link_up process to recover PHY setting after power down.</title>
<updated>2012-07-21T23:07:37Z</updated>
<author>
<name>Akeem G. Abodunrin</name>
</author>
<published>2012-07-17T04:51:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=76886596921dd0e058f7f0a16de6151629390d15'/>
<id>urn:sha1:76886596921dd0e058f7f0a16de6151629390d15</id>
<content type='text'>
There was a previous patch to resolve issue with 82576 losing PHY setting
after PHY power down. However that previous implementation triggered speed
mismatch and occasional link lost. Now, this patch resolves both initial
PHY setting and speed mismatch issues.

Signed-off-by: Akeem G. Abodunrin &lt;akeem.g.abodunrin@intel.com&gt;
Tested-by: Jeff Pieper &lt;jeffrey.e.pieper@intel.com&gt;
Signed-off-by: Jeff Kirsher &lt;jeffrey.t.kirsher@intel.com&gt;
</content>
</entry>
<entry>
<title>ethernet: Use eth_random_addr</title>
<updated>2012-07-17T05:38:27Z</updated>
<author>
<name>Joe Perches</name>
</author>
<published>2012-07-12T19:33:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7efd26d0db5917b9e53d72e76e52338b2600ae20'/>
<id>urn:sha1:7efd26d0db5917b9e53d72e76e52338b2600ae20</id>
<content type='text'>
Convert the existing uses of random_ether_addr to
the new eth_random_addr.

Signed-off-by: Joe Perches &lt;joe@perches.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>drivers/net/ethernet: Fix (nearly-)kernel-doc comments for various functions</title>
<updated>2012-07-11T06:13:46Z</updated>
<author>
<name>Ben Hutchings</name>
</author>
<published>2012-07-10T10:56:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=49ce9c2cda18f62b13055dc715e7b514157c2da8'/>
<id>urn:sha1:49ce9c2cda18f62b13055dc715e7b514157c2da8</id>
<content type='text'>
Fix incorrect start markers, wrapped summary lines, missing section
breaks, incorrect separators, and some name mismatches.  Delete
a few that are content-free.

Signed-off-by: Ben Hutchings &lt;bhutchings@solarflare.com&gt;
Acked-by: Jeff Kirsher &lt;jeffrey.t.kirsher@intel.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
