Comment 167 for bug 263555

Hi,

I confirm that it works for me. I just update the kernel to 2.6.27-5. In a
first moment it seemed to do nothing, but I just did:

sudo ifconfig eth0 down
sudo ifconfig eth0 up

And that was all, my network started to be ok.

Bye,

Juan David Cuevas Guarnizo
Investigador - Grupo GASURE
Tel: +57 4 219 8548
Bloque 19 - Facultad de Ingeniería
Universidad de Antioquia
Medellín - Colombia

"La actividad social de la gente de la universidad debe ser total y
radicalmente ajena a toda actitud de conformismos con la injusticia social,
la desigualdad económica y la opresión intelectual". - Eduardo Umaña Luna.

On Mon, Oct 6, 2008 at 07:10, mrbean71 <email address hidden> wrote:

> I don't know if open a new bug. I think e1000e have some problem here
> result of furter investigation.
> Same behaviour from 27.3 and 27.5 (in the last driver is not blacklisted).
> Sometime network work out of the box, sometime network work out of the box
> sometimes I need to:
>
> sudo modprobe -r e1000e
> sudo modprobe e1000e
>
> now I'm writing with 27.5 kernel and removed added driver two times to
> make it work.
>
> --
> [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at
> risk
> https://bugs.launchpad.net/bugs/263555
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Linux Kernel: Fix Released
> Status in "linux" source package in Ubuntu: Fix Released
> Status in linux in Ubuntu Intrepid: Fix Released
> Status in "linux" source package in Fedora: Confirmed
> Status in "linux" source package in Gentoo Linux: Confirmed
> Status in "linux" source package in Mandriva: Fix Released
> Status in "linux" source package in Suse: In Progress
>
> Bug description:
> In some circumstances it appears possible for the 2.6.27-rc kernels to
> corrupt the NVRAM used by some Intel network parts to store data such as MAC
> addresses.
> This is limited to the new e1000e driver, and reports have only appeared
> from users of "82566 and 82567 based LAN parts (ich8 and ich9)" (to quote
> Intel). The reports seem to be isolated to laptops, but it is not clear if
> this is because desktop/server parts are not vulnerable, or if use cases
> simply increase the chances of laptop users being hit.
>
> Once this corruption has occurred, recovery may be possible via a BIOS
> update, but may well require replacement of the hardware. Use of Intel's
> IABUTIL.EXE is strongly discouraged, as it will worsen the problem to the
> point where the network part will no longer appear on the PCI bus.
>
> (this is a new description, the original one was based on too much
> guesswork. Below are the URLs originally referenced)
> (the driver i blacklisted in Ubuntu for 2.6.27-rc in the latest releases,
> so if your network is not working, it doesn't have to be damaged, but just
> disabled in order to prevent any accidents until this bug is solved, don't
> wary!)
> http://www.blahonga.org/~art/rant.html<http://www.blahonga.org/%7Eart/rant.html>(search for "em0")
> http://<email address hidden>/msg00360.html
> http://<email address hidden>/msg00398.html
>