ΠΡΟΣΟΧΗ ΟΣΟΙ ΧΡΗΣΙΜΟΠΟΙΕΙΤΕ intel e1000e ethernet driver με πυρήνες 2.6.27-rc

[hasodikis]

είπα να παίξω με ubuntu 8.10 aplha 6 (πριν το απορρίψω και αυτό) και υπέπεσε στην αντίληψή μου...

http://www.ubuntu.com/testing/intrepid/alpha6

 

WARNING

 

Due to an unresolved bug in the Linux kernel included in Alpha 6, it should not be used on Intel ethernet hardware handled by the e1000e driver (Intel GigE). Doing so may render your network hardware permanently inoperable.

 

Older Intel ethernet hardware which uses the e1000 driver is not affected by this; however, some hardware which used the e1000 driver in previous Ubuntu releases, such as hardware that uses a PCI Express bus, has been moved from e1000 to e1000e in the latest kernel releases. If in doubt, do not use Alpha 6, and subscribe to https://bugs.launchpad.net/bugs/263555 to be notified when the bug is fixed in the daily images.

 

Το έχουν μεν στην σελίδα τους αλλά επειδή πολλοί κατεβάζουν το .iso χωρίς να την επισκευθούν (πχ από λινκ στο distrowatch) είπα να το βάλω και εδώ...

Είναι πολύ σημαντικό πιθανόν να κάνει μόνιμη ζημιά στην ethernet κανοντας την 'άχρηστη,,,,

 

Από Lunchpad

 

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)

 

http://www.blahonga.org/~art/rant.html (search for "em0")

http://<email'>http://<email address hidden>/msg00360.html

http://<email address hidden>/msg00398.html

 

χαρείτε κουφούς διαλόγους.... έχουμε επιβεβαιβωμένο bug που προκαλεί ζημιά σε hardware

 

Jeffrey Baker wrote on 2008-09-22: (permalink)

 

This is just my humble opinion, but the Alpha CD downloads should be pulled from the archive. This kernel can partially ruin your hardware, and unsuspecting users shouldn't be able to merrily download it.

 

 

Colin Watson wrote on 2008-09-22: (permalink)

Jeffrey, we can't afford to do that; we need to be able to test with the Alpha CDs on the wide variety of hardware not affected by this bug, or our development schedules for 8.10 will be seriously compromised. However, I'd be happy to add a warning to the cdimage web pages. Can anyone suggest some text?

 

 

Alacrityathome wrote on 2008-09-23: (permalink)

 

Colin,

 

Seems that a warning may be insufficient. I would think most of the folks testing a pre-release may not know they have an e1000e driver or affected NIC.

 

Maybe blacklist e1000e asap and then re-instate e1000e after a fix is found.

 

Perhaps have the "warning" state something about the e1000e being temporarily withheld from the pre-release with certain Intel NICs affected.

 

John

ArbitraryConstant wrote on 2008-09-23: (permalink)

 

Is Ubuntu willing to risk the liability of distributing software known to destroy hardware?

Scruffynerf wrote on 2008-09-23: (permalink)

 

Unless Canonical wants liability for

a) Individual user's destroyed hardware

Crippling reputation damages, especially against the 'new to linux' groups

I'd echo the suggestion to pull the liveCD's until this is fixed.

 

When new linux users discovered permanently corrupted hardware after trying Ubuntu, and this gets out in the wider webs, all of Ubuntu's efforts at promoting Ubuntu will also be destroyed.

 

Breaking known good hardware is a problem greater than keeping to a self-imposed delivery schedule.

 

Arnd wrote on 2008-09-23: (permalink)

 

> It's alpha software, people should be considered as being aware that using it might break stuff.

 

That's absolutely ridiculous. I'm being aware that ubuntu alpha or beta can break some stuff (like eating my filesystem or deleting my partitions etc). In fact it already did. However, this is a whole different thing as BREAKING HARDWARE.

To make this clear, we are talking about RMAing laptops and mainboards because of this bug. And we are also talking about reasonable popular hardware. With the statement standing in the room that I should espect my hardware to die when I try ubuntu I will certainly don't try any alpha or beta ubuntu software ever again.

 

In my opinion the Alpha should be pulled NOW. Then you can discuss what steps have to be make to address this problem. (e.g. one easy sollution: disable e1000 and republish) This won't you cost more than a few days.

 

Just my 2 cents

 

Jeffrey Baker wrote on 2008-09-23: (permalink)

 

There's no reason to be hysterical, but a re-spin of Alpha 6 CDs without the e1000e module may be called for. This is a separate bug, but the recommended workaround of adding "blacklist e1000e" in /etc/modprobe.d/blacklist doesn't work. Somehow, udev or some other thing manages to load it anyway. I had to unlink it.

abingham wrote on 2008-09-23: (permalink)

 

Intel has ~80% CPU market share and >=70% of the chipset market for their own CPU.

 

So at least 56% of machines sold are Intel CPUs with Intel chipsets that are susceptible to this bug.

 

1 in 2 of Ubuntu testers could be vulnerable to this.

 

kai

 

Chris Jones wrote 21 hours ago: (permalink)

 

Please listen to what Jesse said in comment #24. This is a bug report, not a discussion forum.

 

Calls for ISOs to be pulled, legal claims, accusations and use of capslock should be on the ubuntu-devel or ubuntu-devel-discuss mailing list. For one thing, by posting to those lists your opinion will be seen by a much wider audience.

 

The people subscribed to this bug have either been affected by this bug (such as myself, I filed this bug), or are trying to fix it.

 

Yelling at those people (which is what a number of you are doing) will solve nothing. Stop it please. The only relevant discussion here is that which is gathering information about the bug, or attempting to fix it.

 

I appreciate this is a contentious issue (since my laptop was affected by this), but I want to read about progress, I don't want to read lots of ranting. I also don't want this post to be perceived as negative, or whining, or whatever. I fully sympathise with people who are trying to protect their fellow users from harm, and in that respect I apologise for not shouting more about this bug when it was first uncovered. All I did was make sure as many of the people as possible who could fix it, knew about it.

If you would like to argue with me about this, please do not do it here, email me personally (see my Launchpad overview page for my addresses) or via <email address hidden>.

 

telos

 

Launchpad Janitor wrote 17 hours ago: (permalink)

 

This bug was fixed in the package linux - 2.6.27-4.6

 

---------------

linux (2.6.27-4.6) intrepid; urgency=low

 

[ Tim Gardner ]

 

* Disable e1000e until the NVRAM corruption problem is found.

- LP: #263555

 

[ Upstream Kernel Changes ]

 

* Revert "[bluetooth] Eliminate checks for impossible conditions in IRQ

handler"

 

-- Ben Collins <email address hidden> Tue, 23 Sep 2008 09:53:57 -0400

 

Αν είναι δυνατόν.......................................

Hasodikis

-----Προστέθηκε 24/9/2008 στις 10 : 02 : 13-----

Λίστα συγκευών που επηρεάζονται

 

 

 

Ravindran, it looks like you are affected. Here's a list of affected devices taken from http://episteme.arstechnica.com/eve/forums/a/tpc/f/96509133/m/302000834931?r=202000364931#202000364931 .

 

8086:1049 82566MM Gigabit Network Connection (Centrino Pro notebooks made since 2007)

8086:104a 82566DM Gigabit Network Connection (vPro desktops made since 2006)

8086:104b 82566DC Gigabit Network Connection (some desktops made since 2006)

8086:104c 82562V 10/100 Network Connection (some desktops made since 2006)

8086:104d 82566MC Gigabit Network Connection (notebooks made since 2007)

8086:105e PRO/1000 PT Dual Port Network Connection

8086:105f PRO/1000 PF Dual Port Server Adapter

8086:1060 PRO/1000 PB Dual Port Server Connection

8086:107d PRO/1000 PT Server Adapter

8086:107e PRO/1000 PF Server Adapter

8086:107f PRO/1000 PB Server Connection

8086:108b PRO/1000 PM Network Connection (82573V integrated)

8086:108c PRO/1000 PM Network Connection (82573E integrated)

8086:1096 PRO/1000 EB Network Connection with I/O Acceleration (servers since 2006)

8086:1098 PRO/1000 EB Backplane Connection with I/O Acceleration (servers since 2006)

8086:109a PRO/1000 PL Network Connection

8086:10a4 PRO/1000 PT Quad Port Server Adapter

8086:10a5 PRO/1000 PF Quad Port Server Adapter

8086:10b9 PRO/1000 PT Desktop Adapter

8086:10ba PRO/1000 EB1 Network Connection with I/O Acceleration (servers since 2007)

8086:10bb PRO/1000 EB1 Backplane Connection with I/O Acceleration (servers since 2007)

8086:10bc PRO/1000 PT Quad Port LP Server Adapter

8086:10bd 82566DM-2 Gigabit Network Connection (vPro desktops since 2007)

8086:10bf 82567LF Gigabit Network Connection (desktops since 2008)

8086:10c0 82562V-2 10/100 Network Connection

8086:10c2 82562G-2 10/100 Network Connection

8086:10c3 82562GT-2 10/100 Network Connection

8086:10c4 82562GT 10/100 Network Connection

8086:10c5 82562G 10/100 Network Connection

8086:10cb 82567V Gigabit Network Connection (desktops since 2008)

8086:10cc 82567LM-2 Gigabit Network Connection

8086:10cd 82567LF-2 Gigabit Network Connection

8086:10ce 82567V-2 Gigabit Network Connection

8086:10d5 Gigabit PT Quad Port Server ExpressModule

8086:10d9 82571EB Dual Port Gigabit Mezzanine Adapter

8086:10da 82571EB Quad Port Gigabit Mezzanine Adapter

8086:10f5 82567LM Gigabit Network Connection

8086:294c 82566DC-2 Gigabit Network Connection (desktops since 2007)

[DIMITRISG]

γμτ θα χαιρομουν πολυ να το ειχε μονο το ubuntu αλλα το εχει και το mandriva

URGENT NOTIFICATION: major bug in all Mandriva Linux 2009 pre-releases

 

Published by awilliamson on Τρίτη, Σεπτέμβριος 23 2008 @ 09:33:16 CEST

 

 

 

A major kernel bug was recently discovered (see also Mandriva bug 44147). This is not a Mandriva-specific issue, the cause lies in the official kernel code, and the issue will affect any system or distribution that uses the affected kernels. It can cause the EEPROM data on network interfaces supported by the e1000e module to become corrupted, rendering the interface unusable. The issue is believed mainly to affect systems based on the Intel ICH8 and ICH9 chipsets.

 

This bug is known to be present in all current 2.6.27 pre-release kernels, and may possibly affect 2.6.25 and 2.6.26 kernels.

 

The issue potentially affects all current Mandriva Linux 2009 pre-releases (earlier pre-releases came with a 2.6.26 kernel, but if you installed one and updated regularly, you would be automatically updated to a 2.6.27 kernel). It will not affect Mandriva Linux 2009 RC2, which will be released soon with a kernel that works around the issue. The issue will not be present in the final release of Mandriva Linux 2009. It does not affect any Mandriva Linux stable release (including 2008 Spring) unless you are using a non-official kernel. If you are using any current Mandriva Linux 2009 pre-release, we highly recommend you check whether this issue may affect you.

 

To check if your network adapter uses this module, run the following command as root:

 

/sbin/lsmod | grep e1000e

 

If it returns any output, then the e1000e module is loaded on your system, and you may be affected by this issue. If it does not return any output but just returns immediately to a prompt, you are not affected by the issue.

 

If you do have the affected hardware, we (and Intel) recommend you immediately back up your EEPROM data, using the following command as root:

 

ethtool -e ethX > savemyeep.txt

 

Where ethX is the affected interface. Usually it will be eth0. This will save the EEPROM data to the savemyeep.txt file. Keep this file safe. If you were subsequently to have the problem occur, we can then assist you in restoring the data from this backup file.

 

We recommend you then immediately switch to an unaffected kernel. Cooker kernels from version 2.6.27-0.rc7.1.1mnb work around the problem by disabling the driver; this will prevent your network interface from working, but will also ensure it is not affected by this issue. Kernel 2.6.27-0.rc7.1.1mnb will be available in the Cooker repositories on September 24th. You can also attempt to 'downgrade' to the latest official kernel available for Mandriva Linux 2008 Spring, by downloading the relevant packages directly from a 2008 Spring repository. As this will be a 2.6.24 kernel, it is unaffected by this problem. However, you may have difficulty booting and using a 2009 pre-release correctly with a 2.6.24 kernel.

 

If you cannot switch to an unaffected kernel, we recommend you immediately stop the network service, and then run the following commands as root:

 

modprobe -r e1000e

rm -f /lib/modules/2.6.26*/kernel/drivers/net/e1000e/e1000e.ko.gz

rm -f /lib/modules/2.6.27*/kernel/drivers/net/e1000e/e1000e.ko.gz

depmod -a

 

Then restart the network service. This will remove the affected module from all potentially affected kernels on your system entirely, making it impossible for it to load in future and thus cause you to suffer the bug. It will, of course, prevent the network interface in question from working with these kernels.

 

If you believe you have already been affected by the issue, which usually manifests itself as the network interface suddenly failing to work after a kernel panic caused by a graphics driver and seems to mainly affect systems which use the Intel ICH8 / ICH9 chipset, you may be able to resolve the problem by 'updating' (or simply reflashing the same version of) the motherboard's BIOS (see your motherboard or laptop vendor's support site for BIOS downloads and flashing instructions). If this does not work, the only safe course of action is to return the system or motherboard to your vendor for repair or replacement. Some sources may recommend the use of a tool named ibautil.exe, but please do not do this. It is in fact more likely to cause more irreparable damage to the EEPROM than it is to fix it.

 

If you have any trouble understanding or following these instructions, or you have any questions about this issue and your potential exposure to it, please post to the official Mandriva Cooker forum, the Cooker mailing list, or the kernel-discuss mailing list. Mandriva staff monitor all of these locations closely and will be able to assist you immediately with any questions, concerns or problems.

Main - URGENT NOTIFICATION: major bug in all Mandriva Linux 2009 pre-releases

Version 1.6 last modified by TeaAge on 24/09/2008 at 18:45

 

http://club.mandriva.com/xwiki/bin/view/Main/e1000eBugNotification

[hasodikis]

Αχα....... παρακαλείται ένας mod να αλλάξει τον τίτλο ώστε να μην είναι μονο Ubuntu specific.....

Hasodikis

[gdp77]

Δεν θα το είχε μόνο το Ubuntu, αλλά οποιαδήποτε διανομή χρησιμοποίησε το συγκεκριμένο kernel. Απ' ό,τι κατάλαβα το bug ήταν στον kernel. Πάντως πρώτη φορά ακούω για software bug που μπορεί να καταστρέψει hardware. Δηλαδή θα μπορούσε να βγει και κάποιος ιός που να καταστρέφει hardware; Μήπως πρέπει να ερευνήσουμε και για bug στο προαναφερθέν hardware;

 

hasodiki μετά την "επεξεργασία", επέλεξε "επεξεργαστής κειμένου". Νομίζω ότι μπορείς να αλλάξεις τίτλο σε κάτι πιο γενικό + ότι το bug διορθώθηκε.

[SnapShot]

θα μπορούσε να αλλάξει ο τίτλος του θέματος σε

«ορίστε ένας λόγος που δεν πρέπει να παίζετε με alpha/beta/release candidate software, ιδιαίτερα όταν είναι kernel aka η καρδιά του συστήματος σας»

[parsifal]

Πάντως πρώτη φορά ακούω για software bug που μπορεί να καταστρέψει hardware. Δηλαδή θα μπορούσε να βγει και κάποιος ιός που να καταστρέφει hardware;

 

Πολύ σπάνια, αλλά συμβαίνει. Το τελευταίο που θυμάμαι προσωπικά ήταν σε Windows, με το πρόγραμμα DScaler που παρομοίως έγραφε σε non volatile RAM ορισμένων PCI TV tuners (ή Asus ή MSI ήταν).

[hasodikis]

θα μπορούσε να αλλάξει ο τίτλος του θέματος σε

«ορίστε ένας λόγος που δεν πρέπει να παίζετε με alpha/beta/release candidate software, ιδιαίτερα όταν είναι kernel aka η καρδιά του συστήματος σας»

 

Αυτό που λες ... δεν ισχύει..... Ακυρώνει τον λόγο ύπαρξης των beta κτλ releases, ο οποίος είναι κυρίως το testing...., το bug reporting και to debugging. Γι αυτό υπάρχουν και για αυτό διανέμονται και μάλιστα ο ρόλος που επιτελούν στο λίνουξ είναι πολύ πιο σημαντικός από σχεδόν οποιοδήποτε άλλο κομμάτι λογισμικού.

Τούτου λεχθέντος... θεωρώ απαράδεκτο...... να είναι γνωστή η ύπαρξη του bug (ειδικά του συγκεκριμένου που επηρεάζει παρα μα πάρα πολύ κόσμο) και να πρέπει να περάσει τοσο πολύς χρόνος ώστε να αναρτηθούν ανεπαρκείς προειδοποιήσεις και περισσότερος για να γίνει τροποποίησηη στο .iso.

 

ΠΟΤΕ δεν κάνω εγκατασταση Alpha ή Beta ως σύστημα εργασίας μου . Διατηρώ ένα partition 10 gb στο σκληρό μου ακριβω για το λόγο αυτό.Για να δοκιμάζω διανομές (στην περίπτωση των beta για να συμβάλλω έστω με το reporting στην επιδιόρθωση tvn bugs). Θέλω να μπορώ να το κάνω αυτό χωρις να κινδυνέυει το hardware μου , όχι από bugs άγνωστα ... εγκαθιστώντας αναλαμβάνω την ευθύνη για αυτά, ΑΛΛΑ ΑΠΟ ΤΑ ΓΝΩΣΤΑ.

 

Hasodikis

[firewalker]

ΔΔηλαδή θα μπορούσε να βγει και κάποιος ιός που να καταστρέφει hardware;

 

Υπάρχουν πάρα πολλοί. Ιδιαίτερα στα πρώτα χρόνια γινόταν χαμός.

[gdp77]

Έχεις κάποιο link; Εγώ πρώτη φορά το ακούω ότι υπάρχει δυνατότητα μέσω software να καταστρέψεις hardware.

[soturin]

http://en.wikipedia.org/wiki/CIH_virus αυτό είναι τέτοια περίπτωση? γιατί μόνον αυτό είχα ξανακούσει

[firewalker]

Γιατί τα bios να έχουν virus protection; :-)

 

Δεν θυμάμαι τα ονόματα των ιών. Θυμάμαι όμως ότι υπήρχε κάποιος που σου κατέστρεφε τον σκληρό δίσκο (συγκεκριμένο μοντέλο). Τον έβαζε σε test mode (ή κάτι τέτοιο) και του άλλαζε τα φώτα. Έχω ένα cd που έχει κάποια τμήματα του κώδικα από κάτι τέτοιους ιούς. Θα κοιτάξω να το βρω.

 

Φαντάσου έναν ιό που ξεκινά να κάνει flash τον dvd-rw για παράδειγμα και του πετάει μέσα ότι θέλει.

 

Ήταν ποιο αθώα τα πράγματα τότε και οι χρήστες έτρεχαν ότι εκτελέσιμο υπήρχε μέσα σε μια δισκέτα...

[pegasos]

Και στο παρελθον υπήρχαν προβλήματα με το Mandrake που μπορούσαν να σου χαλάσουν το hardware.

 

http://www.theinquirer.net/en/inquirer/news/2003/10/26/lg-fails-to-support-linux-with-its-cd-rom-firmware

[parsifal]

To incident που ανέφερα πιο πάνω:

 

http://www.dscaler.org/phpBB/viewtopic.php?t=2985

http://www.dscaler.org/phpBB/viewtopic.php?t=3083

 

Δε θυμόμουν σωστά, το πρόγραμμα έκανε corrupt δεδομένα σε κάποιο EEPROM chip της κάρτας, όχι σε NVRAM...

[apoikos]

Ήταν ποιο αθώα τα πράγματα τότε και οι χρήστες έτρεχαν ότι εκτελέσιμο υπήρχε μέσα σε μια δισκέτα...

 

Γιατί, τώρα τι κάνουν δηλαδή;

[NullScan]

Τώρα τρέχουν οτι εκτελέσιμο τους έρθει στο e-mail