Hi Carsten, any update?
Carsten Aulbert wrote:
> Hi Jesse,
>
> sorry for the late reply, too much other work to rank this question
> high enough.
>
> I was able to work around the problem by adding netconsole module
> loading to a dhclient hook.
>
> Brandeburg, Jesse schrieb:
>>>
>>> 0d:00.0 0
Hi Jesse,
sorry for the late reply, too much other work to rank this question high
enough.
I was able to work around the problem by adding netconsole module
loading to a dhclient hook.
Brandeburg, Jesse schrieb:
>>
>> 0d:00.0 0200: 8086:108c (rev 03)
>> 0e:00.0 0200: 8086:109a
>
> ah, our good
Hi again,
Carsten Aulbert wrote:
>> you're welcome to try the attached patch (against 2.6.29-rc1 but should
>> apply)
>> but it is more a shot in the dark than an actual fix for your issue.
>
> Well, let's see. I will try it remotely now, if it fails and IPMI stops
> as well, I'll be lost.
>
It
Hi Jesse,
Brandeburg, Jesse wrote:
> Carsten Aulbert wrote:
>> And another hi from me
>>
>> I think I've found the problem.
>>
>> We are using netconsole for remote logging and this one is loaded via
>> /etc/modules (obviously *before* DHCP is running. netconsole tries to
>> force its way through
And another hi from me
I think I've found the problem.
We are using netconsole for remote logging and this one is loaded via
/etc/modules (obviously *before* DHCP is running. netconsole tries to
force its way through and in 2.6.25.9 that does not seem to be an issue,
however with the 2.6.27.10 ke
Hi again,
Carsten Aulbert wrote:
> Next thing I do is I could
> o set the MTU to 1500
> o power the system down
> o reboot into the new kernel with e1000e
> o see what happens
>
> Anything else I should/could try?
OK, did that, i.e. switched MTU manually to 1500, shutdown -h now, power
cord off,
Hi John,
Ronciak, John wrote:
> For the 2.6.27 kernel you should be only using the e1000e driver. This is
> the driver needed going forward that will support the 82573 devices.
Tried (as written before) and it failed in the same manner.
>
> Have you been using jumbo frames in your previous ins
0-devel] Kernel 2.6.27.10: e1000e hangs during
>boot at MTU change
>
>Hi all,
>
>I hope e1000e questions are on topic here as well:
>
>We are currently in transition from 2.6.25.9 to 2.6.27.10 (vanilla) and
>hit quite a few problems with our NICs.
>
>0d:00.0 Etherne
Hi all,
I hope e1000e questions are on topic here as well:
We are currently in transition from 2.6.25.9 to 2.6.27.10 (vanilla) and
hit quite a few problems with our NICs.
0d:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet
Controller (Copper) (rev 03)
0e:00.0 Ethernet controll
