Bug 16471

Summary: e1000 doesn't work on machines with more than 4GB of RAM - Detected Tx Unit Hang
Product: Drivers Reporter: Patrick (ps_mail)
Component: NetworkAssignee: Jesse Brandeburg (jesse.brandeburg)
Status: CLOSED CODE_FIX    
Severity: normal CC: frederic, jesse.brandeburg
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2.6.32 Subsystem:
Regression: No Bisected commit-id:

Description Patrick 2010-07-27 17:17:46 UTC
Like described on this mailing list:

http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg01135.html

the e1000 driver doesn't work on systems with 4 (or more) GB of RAM.

The following patch fixes this Problem for me, since ~1 year, by disabling allocation of ram beyound adresses of 4GB. As this wasn't fixed already in the kernel, I'm reporting this bug, in the hope that this patch or any better code modification would fix this bug in the stable kernel.

--- a/drivers/net/e1000/e1000_main.c    2010-07-26 21:39:42.448000000 +0200
+++ b/drivers/net/e1000/e1000_main.c    2010-07-26 21:41:01.268000000 +0200
@@ -826,10 +826,10 @@
        if (err)
                return err;
-       if (!pci_set_dma_mask(pdev, DMA_BIT_MASK(64)) &&
+/*     if (!pci_set_dma_mask(pdev, DMA_BIT_MASK(64)) &&
            !pci_set_consistent_dma_mask(pdev, DMA_BIT_MASK(64))) {
                pci_using_dac = 1;
-       } else {
+       } else*/ {
                err = pci_set_dma_mask(pdev, DMA_BIT_MASK(32));
                if (err) {
                        err = pci_set_consistent_dma_mask(pdev, DMA_BIT_MASK(32));
Comment 1 Patrick 2010-07-27 17:24:59 UTC
OK this is a duplicate of Bug 14048 and 15339. I've just used the wrong search pattern *sorry*.

But in the other posts there is no fix or patch available, so I let this bugreport open....
Comment 2 Jesse Brandeburg 2010-10-06 18:41:47 UTC
patch was pushed upstream 8/9 into net-next

http://git.kernel.org/?p=linux/kernel/git/davem/net-next-2.6.git;a=commitdiff;h=e508be174ad36b0cf9b324cd04978c2b13c21502
Comment 3 Jesse Brandeburg 2012-10-30 15:57:43 UTC
*** Bug 15339 has been marked as a duplicate of this bug. ***