David Lawless wrote:
> Hi Alex,
>
> I'm back from the mines, and can now spend some time on the
> 'igb' driver and the 82575.
>
> Since your message was written I did build and install the
> 1.3.8.6 version with DCA enabled. As with 1.2.44.9 only one
> interrupt is allocated instead of four as s
David,
I would recommend downloading the latest ixgbe and igb drivers from our
sourceforge website, e1000.sf.net. Both of the drivers you are testing may not
be fully compatible with the 2.6.27 kernel since there were a number of TX
multiqueue changes made. This might be why you are seeing th
Yikes! Not my day.
Accidently ran
# ethtool -G eth3 rx 4096 tx 4096
on a DOWN state 'ixgbe' port (Intel 10-GBASE-CX4)
and got yet another oops. Same command worked ok
on UP state 'eth2' just before the 'eth3' oops.Initializing cgroup subsys cpuset
Linux version 2.6.27.1 ([EMAIL PROTECTED]) (g
I'm a sucker for punishment, so I tried again.
First time the ports were open--probably a useful detail.
Worked better with the ports closed, but
did get this kernel warning with traceback.
# ethtool -A eth4 autoneg off rx off tx off
# ethtool -A eth5 autoneg off rx off tx off
# ethtool -A eth6
Alex,
Still fiddling with the 'igb' eval server a just a little bit on
background.
See some data loss compared with another server with 'e1000e'
dual-port PTs attached to the same Cisco 6909-E. Might be
better under 2.6.27.1 than RHEL 2.6.18-92.1.13.el5. Realized I
forgot to apply 'ethtool'
Alex,
Thank you for the patch. I've just hit an serious
work crunch, so I have to set this project aside
for about a month. Sorry about that.
I will check out the patch once the other critical
deadline is met.
David
At 09:40 10/20/2008 -0700, Duyck, Alexander H wrote:
>David,
>
>The attach
David,
The attached patch does two things. One it adds a bit more to the dmesg output
for the driver when the interface is brought up via ifconfig. You should seem
some messages about MSIXBM(x) in there. Also there is a workaround included to
bring the link up without need for the link statu
David,
Based on the information you provided it would appear that the link interrupt
for the ports isn't getting through. If you have ethtool 6 installed I would
appreciate it if you could send me a copy of an "ethtool -d" dump for one of
the non-functional ports so I can check to verify that
onciak, John
>Subject: Re: [E1000-devel] IGB driver 1.2.44.9 problem
>
>David Lawless wrote:
>> It only works with the pure Fedora kernel, which we did not
>> compile. Note that it fails to work with the RHEL 5 kernel,
>> which we also did not compile. A noticeable difference
Alex,
Thank you for your response. I will try out the recommendations
over the next couple of days and report back.
Unfortunately it's not practical to swap the CX4 and VT-quad
cards because the server is in a remote managed data center. I
can say that the CX4 is in the half-height half-lengt
David Lawless wrote:
> It does work under Fedora 9 (2.6.26.5-45.fc9.x86_64), but in
> that case MSI interrupts are completely disabled and it falls
> back to PCI-APIC interrupts. MSI-X interrupts are indicated for
> RHEL 5.2 and the Kernel.org kernel, though as I said it does not
> actually w
David Lawless wrote:
> It only works with the pure Fedora kernel, which we did not
> compile. Note that it fails to work with the RHEL 5 kernel,
> which we also did not compile. A noticeable difference is that
> the RHEL 5 kernel configures the 82575's with MSI-X interrupts.
If the only differen
Yes, of course. The same IP as works perfectly when pure Fedora
9 is up. The problem with that is DCA is not enabled an
interrupts are set to PCI rather than MSI-X. These are the
precise reason why we're evaluating the 82575. Otherwise
82571EB would be sufficient and a whole lot less troubl
At 08:31 10/13/2008 -0700, Ronciak, John wrote:
>David,
>
>First thanks for the report. It looks like you have a number of
>different things going on.
>
>First is that the only interface reporting that it has link up
>is eth6 which is one of the igb ports. All of the rest show "no
>link" inclu
David,
First thanks for the report. It looks like you have a number of
different things going on.
First is that the only interface reporting that it has link up is eth6
which is one of the igb ports. All of the rest show "no link" including
the Tigon3 NIC. Not getting link is most likely somet
15 matches
Mail list logo
