Christoph Hellwig wrote:
On Thu, May 17, 2007 at 09:58:03AM -0500, Wen Xiong wrote:
It really shouldn't be there at all because something in either the
intel
or pseries hardware is totally buggy and we should disable features in
the buggy one completely.
Hi,
Here there are not hardware issue
On Thu, May 17, 2007 at 09:58:03AM -0500, Wen Xiong wrote:
> >>It really shouldn't be there at all because something in either the
> intel
> >>or pseries hardware is totally buggy and we should disable features in
> >>the buggy one completely.
>
> Hi,
>
> Here there are not hardware issue on bot
Auke Kok wrote:
Our 82571 (first PCI-E hardware) causes P-Series hardware to throw
issues. Disabling PCI-E completion timeouts in our NIC resolves
the issue.
Signed-off-by: Auke Kok <[EMAIL PROTECTED]>
Cc: Wen Xiong <[EMAIL PROTECTED]>
---
drivers/net/e1000/e1000_main.c | 10 ++
1 fi
On Thu, 2007-05-17 at 17:04 -0400, Jeff Garzik wrote:
> Wen Xiong wrote:
> > Here there are not hardware issue on both Intel or PPC. The patch is to
> > work around a loop hold on early version of PCI SGI spec.
> > The later PCI Sgi have spec have corrected it. We can just implement it
> > fo
Wen Xiong wrote:
Here there are not hardware issue on both Intel or PPC. The patch is to
work around a loop hold on early version of PCI SGI spec.
The later PCI Sgi have spec have corrected it. We can just implement it
for PPC only. Other vendor may have the same issue.
If it is not a PP
On May 17, 2007, at 4:01 AM, Christoph Hellwig wrote:
On Wed, May 16, 2007 at 07:43:27PM -0500, Kumar Gala wrote:
index 49be393..830d851 100644
--- a/drivers/net/e1000/e1000_main.c
+++ b/drivers/net/e1000/e1000_main.c
@@ -819,6 +819,16 @@ e1000_reset(struct e1000_adapter *adapter)
On Wed, May 16, 2007 at 07:43:27PM -0500, Kumar Gala wrote:
> >index 49be393..830d851 100644
> >--- a/drivers/net/e1000/e1000_main.c
> >+++ b/drivers/net/e1000/e1000_main.c
> >@@ -819,6 +819,16 @@ e1000_reset(struct e1000_adapter *adapter)
> > E1000_WRITE_REG(&adapter->hw, CTRL, ctrl);
On May 16, 2007, at 3:53 AM, Auke Kok wrote:
Our 82571 (first PCI-E hardware) causes P-Series hardware to throw
issues. Disabling PCI-E completion timeouts in our NIC resolves
the issue.
Signed-off-by: Auke Kok <[EMAIL PROTECTED]>
Cc: Wen Xiong <[EMAIL PROTECTED]>
---
drivers/net/e1000/e1000
On Wed, 2007-05-16 at 17:11 -0500, Wen Xiong wrote:
> little history, on PCI-X adapters we did not time dma reads being
> returned to the adapter. On PCIe unfortunately the spec says that
> adapters need to time the dma reads the spec is not specific on the
> range but the timers can range from wo
Auke Kok wrote:
Our 82571 (first PCI-E hardware) causes P-Series hardware to throw
issues. Disabling PCI-E completion timeouts in our NIC resolves
the issue.
Signed-off-by: Auke Kok <[EMAIL PROTECTED]>
Cc: Wen Xiong <[EMAIL PROTECTED]>
---
drivers/net/e1000/e1000_main.c | 10 ++
1 fi
Our 82571 (first PCI-E hardware) causes P-Series hardware to throw
issues. Disabling PCI-E completion timeouts in our NIC resolves
the issue.
Signed-off-by: Auke Kok <[EMAIL PROTECTED]>
Cc: Wen Xiong <[EMAIL PROTECTED]>
---
drivers/net/e1000/e1000_main.c | 10 ++
1 files changed, 10 in
11 matches
Mail list logo
