[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Launchpad has imported 129 comments from the remote bug at https://bugzilla.novell.com/show_bug.cgi?id=425480. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-09-11T13:05:40+00:00 Stbinner wrote: Updated today my work station after two or three weeks to current Factory kernel and since then the onboard network card doesn't show up anymore: e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k2 e1000e: Copyright (c) 1999-2008 Intel Corporation. e1000e :00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 e1000e :00:19.0: setting latency timer to 64 input: PC Speaker as /devices/platform/pcspkr/input/input3 :00:19.0: :00:19.0: The NVM Checksum Is Not Valid e1000e :00:19.0: PCI INT A disabled e1000e: probe of :00:19.0 failed with error -5 Booted an openSUSE 11.0 installation and same issue there now too. Some BIOS/checksum got broken? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/10 On 2008-09-11T13:06:33+00:00 Stbinner wrote: Created attachment 239061 dmesg of Factory installation Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/11 On 2008-09-11T13:07:04+00:00 Stbinner wrote: Created attachment 239062 dmesg of 11.0 installation Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/12 On 2008-09-21T15:25:56+00:00 Stbinner wrote: *** Bug 428180 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/20 On 2008-09-21T16:29:54+00:00 Karsten-keil wrote: Intel did cleanup e1000 and e1000e to have no duplicate PCI IDs in both drivers. Maybe they removed this on the wrong driver. Can you please try to unload e1000e and load e1000 manually if the card is not detected, then please add the ids to the driver on runtime: echo "vendor device subvendor subdevice class class_mask driver_data" > \ /sys/bus/pci/drivers/e1000/new_id All fields are passed in as hexadecimal values (no leading 0x). The vendor and device fields are mandatory, the others are optional. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/21 On 2008-09-21T17:26:30+00:00 Andreas Jaeger wrote: See bug 428180 - I can load the e1000 just fine but it does not work at all. after: echo "8086 104b" > /sys/bus/pci/drivers/e1000/new_id I see the following in dmesg: e1000 :00:19.0: setting latency timer to 64 e1000: :00:19.0: e1000_probe: The EEPROM Checksum Is Not Valid /*/ Current EEPROM Checksum : 0x Calculated : 0xbaf9 OffsetValues == : ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0010: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0020: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0030: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0040: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0050: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0060: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0070: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Include this output when contacting your support provider. This is not a software error! Something bad happened to your hardware or EEPROM image. Ignoring this problem could result in further problems, possibly loss of data, corruption or system hangs! The MAC Address will be reset to 00:00:00:00:00:00, which is invalid and requires you to set the proper MAC address manually before continuing to enable this network device. Please inspect the EEPROM dump and report the issue to your hardware vendor or Intel Customer Support. /*/ e1000: :00:19.0: e1000_probe: Invalid MAC Address e1000: :00:19.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) 00:00:00:00:00:00 e1000: :00:19.0: e1000_probe: This device (id 8086:104b) will no longer be supported by this driver i n the future. e1000: :00:19.0: e1000_probe: please use the "e1000e" driver instead. e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/22 On 2008-09-21T18:31:10+00:00 Karsten-keil wrote: I fear that the EEPROM was deleted. This may be the reason, the fix is e1000 related, but it seems that e1000e has
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Launchpad has imported 37 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=459202. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-08-14T22:17:43+00:00 Michal wrote: Description of problem: I am unable to use my Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 03). System does not see it. Pleae find dmesg output. e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0 e1000e: Copyright (c) 1999-2007 Intel Corporation. ACPI: PCI Interrupt :00:19.0[A] -> GSI 22 (level, low) -> IRQ 22 PCI: Setting latency timer of device :00:19.0 to 64 iTCO_vendor_support: vendor-support=0 :00:19.0: The NVM Checksum Is Not Valid ACPI: PCI interrupt for device :00:19.0 disabled e1000e: probe of :00:19.0 failed with error -5 Version-Release number of selected component (if applicable): Driver version 0.2.0 How reproducible: Happens everytime Steps to Reproduce: 1.Boot computer Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/0 On 2008-08-15T00:44:06+00:00 Yanko wrote: What kernel version is this? Has this adapter ever worked under Fedora. If yes when did it stop? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/1 On 2008-08-15T23:36:51+00:00 Michal wrote: I am sorry, i totally forgot about these details. Kernels which i have: 2.6.25.11-97.fc9.x86_64 2.6.25.14-108.fc9.x86_64 I guess it stopped shortly after i upgraded to F9. It must have been one of first kernel updates. I am not sure if that ever worked in F9. Strange thing, on ubuntu i can not use it too. I do not have dmesg output yet. I will try and see if this matches. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/2 On 2008-08-22T01:42:03+00:00 Chuck wrote: Can you post the output of 'lspci -nn -s :00:19.0'? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/3 On 2008-08-22T06:41:39+00:00 Michal wrote: Output you have requested: 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC Gigabit Network Connection [8086:104b] (rev 03) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/4 On 2008-09-11T17:27:22+00:00 Jesse wrote: The driver you have supports your hardware, but is erroring out on load. The "NVM checksum is not valid" means that something corrupted your system BIOS flash. Can you please give us details about the hardware in your system, attach the output of # lspci -vvv > lspci.txt # dmidecode > dmiout.txt we have some reports that Lenovo systems (a lot of them) are starting to have this issue. Please DO NOT run ibautil as some sites on the web suggest to try to fix this issue. It will likely cause you to have to replace your motherboard to get LAN functionality back. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/10 On 2008-09-11T22:31:41+00:00 Michal wrote: Created attachment 316491 dmiout.txt Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/11 On 2008-09-11T22:32:07+00:00 Michal wrote: Created attachment 316492 lspci.txt Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/12 On 2008-09-12T06:28:13+00:00 Michal wrote: I have messed around a little with my card. Just wanted to check some suggestions point out here http://www.thinkwiki.org/wiki/Problem_with_e1000:_EEPROM_Checksum_Is_Not_Valid#Solutions Little orange led on my ethernet is constantly flashing, when i tried with unloading e1000e module it did not changed anything. When i plugged in cable it stopped and green led showed up, meaning that connection is ok though driver still failed to load. If you need any other info i will gladly help. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/13 On 2008-09-12T16:28:34+00:00 Jesse wrote: okay, so you have an HP machine with an ICH8 chipset. I don't know what the little orange LED flashing means, I will have to check on that. can you get into the iAMT setup just after BIOS
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
this bug is not a catchall for all e1000e issues, the original issue this bug was filed against is fixed and will be highly unlikely to reoccur. If you're having e1000e issues please file a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263555 Title: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
I have ThinkPad X60 with 82573L, and after upgrading to 11.04 beta with latest kernel it stop working almost at all. Tested e1000e 1.2.20-k2 (in stock kernel) and 1.3.10a driver with no luck, booting with option pcie_aspm=force doesn't help, I've tried e1000e_recover.iso but it does not boot on my 32bit processor, and the last what strange I cannot read eeprom: @tpx60:~# ifconfig eth0 up @tpx60:~# ethtool -e eth0 Cannot get driver information: No such device @tpx60:~# ifconfig eth0 down @tpx60:~# ethtool -e eth0 Offset Values -- -- 0x ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0030 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0050 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0060 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff @tpx60:~# dmesg | grep e1000e [1.231354] e1000e: Intel(R) PRO/1000 Network Driver - 1.2.20-k2 [1.231358] e1000e: Copyright(c) 1999 - 2011 Intel Corporation. [1.231392] e1000e :02:00.0: Disabling ASPM L1 [1.231410] e1000e :02:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.231435] e1000e :02:00.0: setting latency timer to 64 [1.231639] e1000e :02:00.0: irq 44 for MSI/MSI-X [1.232563] e1000e :02:00.0: Disabling ASPM L0s [1.392249] e1000e :02:00.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:16:d3:3a:47:ae [1.392253] e1000e :02:00.0: eth0: Intel(R) PRO/1000 Network Connection [1.392332] e1000e :02:00.0: eth0: MAC: 2, PHY: 2, PBA No: 005302-003 [ 27.120351] e1000e :02:00.0: irq 44 for MSI/MSI-X [ 27.176320] e1000e :02:00.0: irq 44 for MSI/MSI-X [ 28.762602] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 28.762610] e1000e :02:00.0: eth0: 10/100 speed: disabling TSO [ 32.855747] e1000e :02:00.0: PCI INT A disabled [ 32.855761] e1000e :02:00.0: PME# enabled [ 89.756091] e1000e :02:00.0: BAR 0: set to [mem 0xee00-0xee01] (PCI address [0xee00-0xee01]) [ 89.756109] e1000e :02:00.0: BAR 2: set to [io 0x2000-0x201f] (PCI address [0x2000-0x201f]) [ 89.756154] e1000e :02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) [ 89.756208] e1000e :02:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100107) [ 89.756278] e1000e :02:00.0: PME# disabled [ 89.756372] e1000e :02:00.0: Disabling ASPM L1 [ 89.756474] e1000e :02:00.0: irq 44 for MSI/MSI-X [ 89.758786] e1000e :02:00.0: eth0: MAC Wakeup cause - Link Status Change [ 89.828165] e1000e :02:00.0: PME# enabled [ 89.976110] e1000e :02:00.0: BAR 0: set to [mem 0xee00-0xee01] (PCI address [0xee00-0xee01]) [ 89.976128] e1000e :02:00.0: BAR 2: set to [io 0x2000-0x201f] (PCI address [0x2000-0x201f]) [ 89.976184] e1000e :02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) [ 89.976234] e1000e :02:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100107) [ 89.976329] e1000e :02:00.0: PME# disabled [ 90.052487] e1000e :02:00.0: irq 44 for MSI/MSI-X [ 90.108195] e1000e :02:00.0: irq 44 for MSI/MSI-X [ 91.183858] e1000e :02:00.0: PME# enabled [ 108.668103] e1000e :02:00.0: BAR 0: set to [mem 0xee00-0xee01] (PCI address [0xee00-0xee01]) [ 108.668121] e1000e :02:00.0: BAR 2: set to [io 0x2000-0x201f] (PCI address [0x2000-0x201f]) [ 108.668167] e1000e :02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) [ 108.668222] e1000e :02:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100107) [ 108.668294] e1000e :02:00.0: PME# disabled [ 108.668388] e1000e :02:00.0: Disabling ASPM L1 [ 108.668491] e1000e :02:00.0: irq 44 for MSI/MSI-X [ 108.670799] e1000e :02:00.0: eth0: MAC Wakeup cause - Link Status Change [ 108.740171] e1000e :02:00.0: PME# enabled [ 108.900079] e1000e :02:00.0: BAR 0: set to [mem 0xee00-0xee01] (PCI address [0xee00-0xee01]) [ 108.900096] e1000e :02:00.0: BAR 2: set to [io 0x2000-0x201f] (PCI address [0x2000-0x201f]) [ 108.900142] e1000e :02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) [ 108.900197] e1000e :02:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100107) [ 108.900304] e1000e :02:00.0: PME# disabled [ 108.976495] e1000e :02:00.0: irq 44 for MSI/MSI-X [ 109.032199] e1000e :02:00.0: irq 44 for MSI/MSI-X [ 110.107879] e1000e :02:00.0: PME# enabled NIC works fine in Windows 7 and OpenBSD, contact me for more info if needed -- You received
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Mandriva) Importance: Unknown = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263555 Title: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263555 Title: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Gentoo Linux) Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263555 Title: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Ubuntu) Status: Fix Released = Confirmed -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Please don't change bug statuses without explanation ** Changed in: linux (Ubuntu) Status: Confirmed = Fix Released -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Burned the iso, followed your instructions, but: eth0 EEprom len 4096 checksum ed0e wrong should be 830e So I can't send you my ethtool.dmp My notebook is a Fujitsu Siemens Lifebook E8410 Thank you Dave!!! -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
This is unusual, as the e1000e_nvm -r –d eth0 -o ethtool.dmp command normally dumps out the 1Gb portion of the system flash even if it _does_ have a bad checksum, and then I've been fixing the checksum content. Are you sure that there isn't an ethtool.dmp file created in the local directory from which you ran e1000e_nvm ? If there really is no ethtool.dmp, please send me 1) lspci -tv 2) lspci -xxx 3) dmesg (that includes the failure of the e1000e driver to load) and I'll send you an instrumented driver that will dump out the 1Gb flash content, and we may be able to fix it from there. At least I hope so. As I say, I've fixed a lot of these corruptions, but do not recall seeing this particular failure mode before. Dave -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of bonsiware Sent: Wednesday, October 07, 2009 3:26 AM To: Graham, David Subject: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk Burned the iso, followed your instructions, but: eth0 EEprom len 4096 checksum ed0e wrong should be 830e So I can't send you my ethtool.dmp My notebook is a Fujitsu Siemens Lifebook E8410 Thank you Dave!!! -- [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” package in Ubuntu: Fix Released Status in “linux-lpia” package in Ubuntu: Fix Released Status in linux in Ubuntu Intrepid: Fix Released Status in linux-lpia in Ubuntu Intrepid: Fix Released Status in “linux” package in Fedora: Fix Released Status in “linux” package in Gentoo Linux: Fix Released Status in “linux” package in Mandriva: Fix Released Status in “linux” package in Suse: Fix Released 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 (search for em0) http://www.mail-archive.com/e1000-de...@lists.sourceforge.net/msg00360.html http://www.mail-archive.com/e1000-de...@lists.sourceforge.net/msg00398.html -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
lspci -tv: +-19.0 Intel Corporation 82566DC Gigabit Network Connection lspci -xxx: 00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 03) 00: 86 80 4b 10 03 01 10 00 03 00 00 02 00 00 00 00 10: 00 00 40 fe 00 40 42 fe 21 18 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 00 00 30: 00 00 00 00 c8 00 00 00 00 00 00 00 0b 01 00 00 dmesg: [1.652371] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2 [1.652374] e1000e: Copyright (c) 1999-2008 Intel Corporation. [1.652440] e1000e :00:19.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.652447] e1000e :00:19.0: pci_enable_pcie_error_reporting failed 0xfffb [1.652456] e1000e :00:19.0: setting latency timer to 64 [1.652628] alloc irq_desc for 28 on node -1 [1.652630] alloc kstat_irqs on node -1 [1.652647] e1000e :00:19.0: irq 28 for MSI/MSI-X [1.739443] ohci1394 :1c:03.4: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.757784] :00:19.0: :00:19.0: The NVM Checksum Is Not Valid [1.787486] e1000e :00:19.0: PCI INT A disabled [1.787495] e1000e: probe of :00:19.0 failed with error -5 -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Thanks, I still don't understand how it is that e1000e_recover didn't work for you, but I admit that I have been using it as a tool, and don't understand its inner workings. Let's try another approach to get the invalid NVM content listed, this time by the driver when it reads the data. I attach a patch e1000e-1.0.15.shownvm.patch which can be applied our latest e1000e sourceforge release. To install the driver, and collect that result , please proceeed as follows 1) Copy this patch to a local directory 2) Download e1000e-1.0.15.tar.gz from http://sourceforge.net/projects/e1000/files/ 3) Untar the tarball to a local directory, tar xvzf e1000e-1.0.15.tar.gz 4) cd e1000e-1.0.15/src 5) Apply the patch patch -p2 ../../e1000e-1.0.15.shownvm.patch 6) Remove the old driver, build install the new one rmmod e1000e make insmod e1000e.ko 7) The system message log should have the NVM content that was read. The driver should also load even in the presence of the errored NVM. Please let me know whether it does load and work, and .send me the dmesg log that includes the NVM dump, and I will see if I can fix it up and return it to you with instructions on how to apply the fixed-up version, Thanks Dave From: boun...@canonical.com [boun...@canonical.com] On Behalf Of bonsiware [bonsiw...@gmail.com] Sent: Wednesday, October 07, 2009 10:28 AM To: Graham, David Subject: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk lspci -tv: +-19.0 Intel Corporation 82566DC Gigabit Network Connection lspci -xxx: 00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 03) 00: 86 80 4b 10 03 01 10 00 03 00 00 02 00 00 00 00 10: 00 00 40 fe 00 40 42 fe 21 18 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 00 00 30: 00 00 00 00 c8 00 00 00 00 00 00 00 0b 01 00 00 dmesg: [1.652371] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2 [1.652374] e1000e: Copyright (c) 1999-2008 Intel Corporation. [1.652440] e1000e :00:19.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.652447] e1000e :00:19.0: pci_enable_pcie_error_reporting failed 0xfffb [1.652456] e1000e :00:19.0: setting latency timer to 64 [1.652628] alloc irq_desc for 28 on node -1 [1.652630] alloc kstat_irqs on node -1 [1.652647] e1000e :00:19.0: irq 28 for MSI/MSI-X [1.739443] ohci1394 :1c:03.4: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.757784] :00:19.0: :00:19.0: The NVM Checksum Is Not Valid [1.787486] e1000e :00:19.0: PCI INT A disabled [1.787495] e1000e: probe of :00:19.0 failed with error -5 -- [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” package in Ubuntu: Fix Released Status in “linux-lpia” package in Ubuntu: Fix Released Status in linux in Ubuntu Intrepid: Fix Released Status in linux-lpia in Ubuntu Intrepid: Fix Released Status in “linux” package in Fedora: Fix Released Status in “linux” package in Gentoo Linux: Fix Released Status in “linux” package in Mandriva: Fix Released Status in “linux” package in Suse: Fix Released 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 (search for em0) http://www.mail-archive.com/e1000-de...@lists.sourceforge.net/msg00360.html http://www.mail-archive.com/e1000-de...@lists.sourceforge.net/msg00398.html ** Attachment added: e1000e-1.0.15.shownvm.patch http://launchpadlibrarian.net/33264068/e1000e-1.0.15.shownvm.patch -- [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
I am still contacted about once per month for instructions on how to recover ethernet functionality on systems that have had their 1Gb flash content corrupted, possibly by this defect. If you believe that you are affected by this isssue, you can safely perform steps 1 through 5 from the bullet list below, then contact me with the result, from which I will prepare a fully repaired image, and post it back to you. You can then continue with steps 6,7 8. 1) Download a CD image of the recovery program (originally created by Karsten Keil formerly of SuSE) from http://e1000.sourceforge.net/e1000e_recover.iso. Please type the address in your browser window and choose save to fle- you cannot search for this file. 2) Burn the iso to CD, boot the CD. When prompted, select “Rescue System” Linux will load, you’ll see an openSUSE splashscreen, and eventually a login prompt. 3) Log on as root. There's no password, so just hit return. 4) Read the current eeprom and save it to file. Be patient ! e1000e_nvm -r –d eth0 -o ethtool.dmp 5) mount a USB disk to save the file, and send the file to me david_dot_graham_at_intel_dot_com I will then fix up the image, and mail it back to you as ethtoola.dmp. When you receive the updated file: 6) Write the new eeprom content back to your system NVM e1000e_nvm –d eth0 -P 108C8086 ethtoola.dmp 7) You will see some warnings, select YES when prompted. 8) You should then be able to remove the recovery CD, and successfully boot back to a working ethernet using Linux, Windows, OpenSolaris, or anything else. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Prior to upgrading to kernel 2.6.27-9 No kernel panics were experienced. However kernel panics seem random they seem to occur during high network activity when using the Ethernet device (Intel Corporation 82573L Gigabit Ethernet Controller) which uses the e1000e driver. No reports of hardware dieing yet and hopefully this bug will be limited to kernel panics! -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Is there a link as to how to recover ? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
While we should expect no further reports of flash corruptions due to this bug, I would like to know of any systems which did fall foul of the bug, and have not yet had their flash restored. Pleae let me know if you have system that had proper (e1000e) LAN functionality proor to installing a 2.6.27-rc kernel, and lost it while running the rc kernel. So as not to confuse this bug report, please contact me offline and I will try to help you restore your LAN. david.graham_at_intel_dot_com -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Ubuntu) Assignee: Tim Gardner (timg-tpi) = (unassigned) ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Basilisk (bluebal-1) -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Ubuntu) Assignee: Basilisk (bluebal-1) = Tim Gardner (timg-tpi) -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Also affects: linux-lpia (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-lpia (Ubuntu Intrepid) Importance: Undecided = Critical Assignee: (unassigned) = Amit Kucheria (amitk) Status: New = Fix Committed Target: None = ubuntu-8.10 -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
This bug was fixed in the package linux-lpia - 2.6.27-4.9 --- linux-lpia (2.6.27-4.9) intrepid; urgency=low [ Amit Kucheria ] * SAUCE: Start new release Ignore: yes * SAUCE: Add LPIA keyword in front of all our tags * SAUCE: Disable DYANMIC_FTRACE - LP: #263555 * SAUCE: Disable ath5k from configs - LP: #288148 * SAUCE: Fix rebase script some more * SAUCE: Change default TCP congestion algorithm to cubic - LP: #278801 * SAUCE: Enable vesafb module -- Amit Kucheria [EMAIL PROTECTED] Thu, 23 Oct 2008 20:07:26 + ** Changed in: linux-lpia (Ubuntu Intrepid) Status: Fix Committed = Fix Released -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Gentoo Linux) Status: Confirmed = Fix Released -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
So in the interests of adding some closure to this bug. The issue turns out to have never been the e1000e driver's fault. Just to clarify. there were two bugs here. Yes the ftrace code should have been more careful in using cmpxchg, and tried harder to not write into code that might have swapped out (note, 2.6.28 has this fixed). But the e1000e driver absolutely did have a bug. The driver should never had left open that a random write into it could brick the board. I'm actually glad that ftrace was the culprit. Because it allowed for a consistent reproducer. Just imagine if ftrace did not cause this. Any little bug in the kernel could have brick you card. And guess what? You would be out of luck, because it would be extremely hard to ever reproduce it again. I'm not denying that ftrace did not have a bug. I just want the record to state, that ftrace was not the only one at fault here. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Gentoo Linux) Status: Fix Released = Confirmed -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Is this Problem resolved now? I think I read somewhere that there already is a patch that you guys from Ubuntu just need to integrate. Is that true? If yes why is it taking so long? (no offense, just curious) -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
jagdfalke: Please see the top of the page, it's marked as Fix Released -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
I have downloaded LiveCD for AMD 64 and for x86 64 yesterday and when I tried AMD 64 version as a LiveSession I was not able to use network on a computer that I use now to write this message :)) (now I an writing in Hardy) so it is not yet released AFAIAC. On 10/17/08, Chris Jones [EMAIL PROTECTED] wrote: jagdfalke: Please see the top of the page, it's marked as Fix Released -- [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: Fix Released Status in linux source package in Gentoo Linux: Fix Released Status in linux source package in Mandriva: Fix Released Status in linux source package in Suse: Fix Released 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 (search for em0) http://www.mail-archive.com/[EMAIL PROTECTED]/msg00360.html http://www.mail-archive.com/[EMAIL PROTECTED]/msg00398.html -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
For your Information: Launchpad is NOT a support forum, in future situations please refer to the forums. As for your Problem: The driver is fixed in the current kernel-release, but as the live-cd still ships with the old kernel, networking is of course disabled with this card. I recommend waiting for the final release or downloading the new kernel- packages onto a usb-stick or similar and installing them by hand. As of HOW to do that, please refer to the forums. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
I am very sorry that I have missused this place. I hope that You will be able to forgive and forget. I am just an old guy ... ;) I will wait for official release. Thank You very much. Once again sorry for the noise. On 10/17/08, hefeweiz3n [EMAIL PROTECTED] wrote: For your Information: Launchpad is NOT a support forum, in future situations please refer to the forums. As for your Problem: The driver is fixed in the current kernel-release, but as the live-cd still ships with the old kernel, networking is of course disabled with this card. I recommend waiting for the final release or downloading the new kernel- packages onto a usb-stick or similar and installing them by hand. As of HOW to do that, please refer to the forums. -- [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: Fix Released Status in linux source package in Gentoo Linux: Fix Released Status in linux source package in Mandriva: Fix Released Status in linux source package in Suse: Fix Released 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 (search for em0) http://www.mail-archive.com/[EMAIL PROTECTED]/msg00360.html http://www.mail-archive.com/[EMAIL PROTECTED]/msg00398.html -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
So in the interests of adding some closure to this bug. The issue turns out to have never been the e1000e driver's fault. The fault lies with the CONFIG_DYNAMIC_FTRACE option. So specifically when the FTRACE code was enabled, it was doing a locked cmpxchg instruction on memory that had been previously used as __INIT code from some other module. a) some other module loads b) that module's init code calls into ftrace which stores the EIP c) that module discards its init code d) e1000e loads e) e1000e asks the kernel for memory to ioremap onto, and gets the memory location of the code at b) and maps the flash/NVM control registers there. f) ftraced runs and rewrites onto bytes 4-8 of the memory location from b/e g) since the lock/cmpxchg instruction is undefined for memory mapped registers, random junk is written to the b/e location h) depending on the contents of the junk in g) the NVM is either byte corrupted or block erased, which is detected the next time the e1000e driver is loaded. a short term workaround is in 2.6.27.1 (disable CONFIG_DYNAMIC_FTRACE) and the longer term fix is rewrites of the cmpxchg code (which is already done and will be in 2.6.28-rc1) I strongly recommend that 2.6.27.1 be picked up in ubuntu immediately -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Try to get a Vista DVD from somebody. You can actually boot them in a sort of Live System, perhaps you can install the drivers in it (the installation does not need a restart). -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
hello, a week ago I have upgraded my Hardy to Intrepid beta on 3 machines. the oldest one is still with Intrepid but two new had to be downgraded to Hardy since network did not work. is it safe now to upgrade them to Intrepid beta or should I wait for official release? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Michael as im having the same issue; i might try and do the same. Quite disappointing that we have to rely on Windows to bail us out. Ive even tried compiling the Intel drivers under Linux with the same error. Perhaps a live Windows Distro like Barts PE? I dont want to have to put the V1sta disks in and blow away my Ubuntu install. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Suse) Status: In Progress = Fix Released -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
This is the patch which has passed Intel's testing and with this patch that issue can't be reproduced again now. It looks to be a work-around and with the .28 a fix for the root cause of the problem. Date: Wed, 15 Oct 2008 18:21:44 -0400 (EDT) From: Steven Rostedt [EMAIL PROTECTED] To: LKML [EMAIL PROTECTED], [EMAIL PROTECTED] cc: Linus Torvalds [EMAIL PROTECTED], Andrew Morton [EMAIL PROTECTED], Arjan van de Ven [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], Thomas Gleixner [EMAIL PROTECTED], Ingo Molnar [EMAIL PROTECTED] Subject: [PATCH -stable] disable CONFIG_DYNAMIC_FTRACE due to possible memory corruption on module unload While debugging the e1000e corruption bug with Intel, we discovered today that the dynamic ftrace code in mainline is the likely source of this bug. For the stable kernel we are providing the only viable fix patch: labeling CONFIG_DYNAMIC_FTRACE as broken. (see the patch below) We will follow up with a backport patch that contains the fixes. But since the fixes are not a one liner, the safest approach for now is to disable the code in question. The cause of the bug is due to the way the current code in mainline handles dynamic ftrace. When dynamic ftrace is turned on, it also turns on CONFIG_FTRACE which enables the -pg config in gcc that places a call to mcount at every function call. With just CONFIG_FTRACE this causes a noticeable overhead. CONFIG_DYNAMIC_FTRACE works to ease this overhead by dynamically updating the mcount call sites into nops. The problem arises when we trace functions and modules are unloaded. The first time a function is called, it will call mcount and the mcount call will call ftrace_record_ip. This records the calling site and stores it in a preallocated hash table. Later on a daemon will wake up and call kstop_machine and convert any mcount callers into nops. The evolution of this code first tried to do this without the kstop_machine and used cmpxchg to update the callers as they were called. But I was informed that this is dangerous to do on SMP machines if another CPU is running that same code. The solution was to do this with kstop_machine. We still used cmpxchg to test if the code that we are modifying is indeed code that we expect to be before updating it - as a final line of defense. But on 32bit machines, ioremapped memory and modules share the same address space. When a module would load its code into memory and execute some code, that would register the function. On module unload, ftrace incorrectly did not zap these functions from its hash (this was the bug). The cmpxchg could have saved us in most cases (via luck) - but with ioremap-ed memory that was exactly the wrong thing to do - the results of cmpxchg on device memory are undefined. (and will likely result in a write) The pending .28 ftrace tree does not have this bug anymore, as a general push towards more robustness of code patching, this is done differently: we do not use cmpxchg and we do a WARN_ON and turn the tracer off if anything deviates from its expected state. Furthermore, patch sites are statically identified during build time so there's no runtime discovery of dynamic code areas anymore, and no room for code unmaps to cause the hash to become out of date. We believe the fragility of dynamic patching has been sufficiently addressed in the development code via the static patching method, but further suggestions to make it more robust are welcome. Signed-off-by: Steven Rostedt [EMAIL PROTECTED] Acked-by: Ingo Molnar [EMAIL PROTECTED] Acked-by: Thomas Gleixner [EMAIL PROTECTED] --- kernel/trace/Kconfig |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) Index: linux-compile.git/kernel/trace/Kconfig === --- linux-compile.git.orig/kernel/trace/Kconfig 2008-10-02 10:18:49.0 -0400 +++ linux-compile.git/kernel/trace/Kconfig 2008-10-15 17:29:34.0 -0400 @@ -103,7 +103,8 @@ config CONTEXT_SWITCH_TRACER all switching of tasks. config DYNAMIC_FTRACE - bool enable/disable ftrace tracepoints dynamically + bool enable/disable ftrace tracepoints dynamically (BROKEN) + depends on BROKEN depends on FTRACE depends on HAVE_DYNAMIC_FTRACE default y -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
I fixed my network card in my x61t with the Vista drivers from intel.com ( http://downloadcenter.intel.com/Filter_Results.aspx?strOSs=AllstrTypes=AllProductID=2775lang=engOSFullName=All%20Operating%20Systems ). Yust installed them and played with their diagnostic tools in the driver. Both PXE and normal networking under Linux are working again :-) I BIOS-upgrade alone did not help (actually, it was a downgrade^^) Please write something about this solution in the error message about the wrong crc, it would help many people. Thanks, Michael Fritscher -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Gentoo Linux) Status: Confirmed = Fix Released -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
If it helps i am also having this problem aswell; i have included output of lshw aswell // Linux penfold 2.6.27-6-generic #1 SMP Tue Oct 7 04:15:04 UTC 2008 i686 GNU/Linux [2.319073] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6 [2.319076] e1000e: Copyright (c) 1999-2008 Intel Corporation. [2.319116] e1000e :00:19.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [2.319126] e1000e :00:19.0: setting latency timer to 64 [2.377161] e1000e :00:19.0: PCI INT A disabled [2.377199] e1000e: probe of :00:19.0 failed with error -5 *-network UNCLAIMED product: 82566DC-2 Gigabit Network Connection *-network *-network DISABLED \\ -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Fedora) Status: In Progress = Fix Released -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Fedora) Status: Confirmed = In Progress -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
same for me: under Linux, the e1000e driver refuses to load: 388.961230] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6 [ 388.961249] e1000e: Copyright (c) 1999-2008 Intel Corporation. [ 388.961346] e1000e :00:19.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [ 388.961374] e1000e :00:19.0: setting latency timer to 64 [ 389.013108] :00:19.0: :00:19.0: The NVM Checksum Is Not Valid [ 389.023427] e1000e :00:19.0: PCI INT A disabled [ 389.023567] e1000e: probe of :00:19.0 failed with error -5 (Khairul, you missed the most imported line becuase of the grep!) But it works fine under Windows. uname -a: Linux michis-ibm 2.6.27-6-generic #1 SMP Tue Oct 7 04:15:04 UTC 2008 i686 GNU/Linux -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
sorry .. i miss to read previous comment, i done it manually now i get from dmesg [ 25.596061] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 [ 25.596065] e1000e: Copyright (c) 1999-2008 Intel Corporation. [ 25.596142] e1000e :00:19.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [ 25.596159] e1000e :00:19.0: setting latency timer to 64 [ 25.658013] e1000e :00:19.0: PCI INT A disabled [ 25.673108] e1000e: probe of :00:19.0 failed with error -5 -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
For those who got this working on the 2.6.27-5.4 kernel. Does the newer 2.6.27-5.5 kernel that is in the repositories now also work for you? On Mon, Oct 6, 2008 at 7:10 AM, mrbean71 [EMAIL PROTECTED] 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. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
I confirm that the new binaries are working for me. uname -r 2.6.27-5-generic Thanks a lot for the great job! -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
The fix will be included in the subsequent daily images Is the fix avalible now in the daily builds?: http://cdimage.ubuntu.com/daily-live/current/ if not when will it be? Or is there another link? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Driver seems to be ok, eth0 come up automagically. Now I think there are problems with knetwork manager: i wrote manually resolv.conf and i have to restar network from a shell to make dns work. But probably this is another story. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
The fix was not in 20081004 but it should be in 20081005 and is definitely in 20081006. Therefore any of the ISO would have the correct kernel. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
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 PROTECTED] 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.htmlhttp://www.blahonga.org/%7Eart/rant.html(search for em0) http://www.mail-archive.com/[EMAIL PROTECTED]/msg00360.html http://www.mail-archive.com/[EMAIL PROTECTED]/msg00398.html -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
The fix was not in 20081004 but it should be in 20081005 and is definitely in 20081006. Therefore any of the ISO would have the correct kernel. No, 20081007 will be the first daily image that includes this module again. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
the updated kernel is in the 20081006 manifest: linux-generic 2.6.27.5.5 linux-headers-2.6.27-5 2.6.27-5.8 linux-headers-2.6.27-5-generic 2.6.27-5.8 linux-headers-generic 2.6.27.5.5 linux-image-2.6.27-5-generic 2.6.27-5.8 linux-image-generic 2.6.27.5.5 linux-libc-dev 2.6.27-5.8 linux-restricted-modules-2.6.27-5-generic 2.6.27-5.7 linux-restricted-modules-common 2.6.27-5.7 linux-restricted-modules-generic 2.6.27.5.5 That worked fine for me. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
any ways to fix/patches/ways for eeprom/NVM problem? after upgrade to 2.6.27-5.8, the Ethernet still wont work ? $ dmesg | grep e1000e [5.604448] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 [5.604456] e1000e: Copyright (c) 1999-2008 Intel Corporation. [5.604557] e1000e :00:19.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [5.604586] e1000e :00:19.0: setting latency timer to 64 [5.683292] e1000e :00:19.0: PCI INT A disabled [5.683335] e1000e: probe of :00:19.0 failed with error -5 the ethernet works well if booting to windows XP .. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux Status: In Progress = Fix Released -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
@Anil: While that re-enables the driver for the session, it's not the permanent solution. I just upgraded from 2.6.27.4 to 2.6.27.5, but /etc/modprobe.d /blacklist-e1000e still remains on disk, and you'd need to either comment out the line blacklisting the driver, or move/delete the file to get this fixed. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
i've finally received the -5 drivers and i still don't have an internet connection available to me. the only kernel im having any luck with is -3. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Hi all, mi NIC won't work with any 2.6.27 kernel, now i'm writing from: Linux marcoPC 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux This is lspci result: 00:19.0 Ethernet controller: Intel Corporation 82562V-2 10/100 Network Connection (rev 02) It seems card is recognized from 2.6.27.5 but don't work, I can make up and down with ifconfig with no result. It prefectly work rebooting 2.6.24-21. If you need I wan't help to understand. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Hi all, my NIC won't work with any 2.6.27 kernel, now i'm writing from: Linux marcoPC 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux This is lspci result: 00:19.0 Ethernet controller: Intel Corporation 82562V-2 10/100 Network Connection (rev 02) It seems card is recognized from 2.6.27.5 but don't work, I can make up and down with ifconfig with no result. It prefectly work rebooting 2.6.24-21. If you need I wan't help to understand. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Arve's fix was good, I have blacklisted the driver e1000e as the workaround and never removed the blacklist. With the removed from /etc/modprobe.d/blacklist it works fine -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
2.6.27-5 fixed my problems, just to confirm that this works for some people. On Sun, Oct 5, 2008 at 4:09 PM, mrbean71 [EMAIL PROTECTED] wrote: Hi all, my NIC won't work with any 2.6.27 kernel, now i'm writing from: Linux marcoPC 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux This is lspci result: 00:19.0 Ethernet controller: Intel Corporation 82562V-2 10/100 Network Connection (rev 02) It seems card is recognized from 2.6.27.5 but don't work, I can make up and down with ifconfig with no result. It prefectly work rebooting 2.6.24-21. If you need I wan't help to understand. -- [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. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Just confirming that it works fine with my T61p 6457-7WU. $ uname -r 2.6.27-5-generic $ lsmod | grep 100 e1000e128040 0 lshw also shows the device properly setup, and no longer unclaimed. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Mine was T61 6464 - AP3 If upgrading the 2.6.27-5 this morning [EMAIL PROTECTED]:~$ uname -r 2.6.27-5-generic [EMAIL PROTECTED]:~$ lsmod | grep 1000 it doesnt give me any result, should i remove the blacklist manually or it will be done automatically after upgrading it ? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
i've tried manually remove the blacklist-e1000e but it doesnt work for me at all .. any suggestion what should i do next ? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
No package here, when it will arrive? It's really amazing when you have no network ... -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
If you have no network whatsoever, you'll need to grab the package using another machine or OS, use a daily build CD image, or downgrade to a version where the driver was not disabled and then upgrade to the current one. http://packages.ubuntu.com/intrepid/linux-image-2.6.27-5-generic http://packages.ubuntu.com/intrepid/linux-image-2.6.27-5-server (As Colin mentioned, it will take a while for linux-* packages to be updated to automatically bring in the new package.) -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Kernel Bugzilla #11382 is already fixed http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4a7703582836f55a1cbad0e2c1c6ebbee3f9b3a7 Best regards, Renato S. Yamane -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Since the Kernel upgrade i still appear to be having some troubles with the network card; im using an X200 laptop that ships with a 82566DC-2 network card; [EMAIL PROTECTED]:~$ uname -a Linux penfold 2.6.27-5-generic #1 SMP Fri Oct 3 00:38:23 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ sudo lshw *-network UNCLAIMED description: Ethernet controller product: 82566DC-2 Gigabit Network Connection vendor: Intel Corporation physical id: 19 bus info: [EMAIL PROTECTED]:00:19.0 version: 03 width: 32 bits clock: 33MHz capabilities: pm msi cap_list configuration: latency=0 *-usb:0 [EMAIL PROTECTED]:~$ sudo cat /var/log/dmesg | grep e1000 [2.567349] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 [2.567352] e1000e: Copyright (c) 1999-2008 Intel Corporation. [2.567394] e1000e :00:19.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [2.567405] e1000e :00:19.0: setting latency timer to 64 [2.636692] e1000e :00:19.0: PCI INT A disabled [2.636708] e1000e: probe of :00:19.0 failed with error -5 I went straight from 2.6.27.4 -- .5 could that be it? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
once you have the kernel running do modprobe e1000e On Saturday 04 October 2008 4:07:43 pm Simon Sigre wrote: Since the Kernel upgrade i still appear to be having some troubles with the network card; im using an X200 laptop that ships with a 82566DC-2 network card; [EMAIL PROTECTED]:~$ uname -a Linux penfold 2.6.27-5-generic #1 SMP Fri Oct 3 00:38:23 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ sudo lshw *-network UNCLAIMED description: Ethernet controller product: 82566DC-2 Gigabit Network Connection vendor: Intel Corporation physical id: 19 bus info: [EMAIL PROTECTED]:00:19.0 version: 03 width: 32 bits clock: 33MHz capabilities: pm msi cap_list configuration: latency=0 *-usb:0 [EMAIL PROTECTED]:~$ sudo cat /var/log/dmesg | grep e1000 [2.567349] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 [2.567352] e1000e: Copyright (c) 1999-2008 Intel Corporation. [2.567394] e1000e :00:19.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [2.567405] e1000e :00:19.0: setting latency timer to 64 [2.636692] e1000e :00:19.0: PCI INT A disabled [2.636708] e1000e: probe of :00:19.0 failed with error -5 I went straight from 2.6.27.4 -- .5 could that be it? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
How could I install this fix manually (not over the internet). At the time I've got no other connection as a wired. Is there a possibility to update the system via usb stick? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Please ask in the forum not here On Fri, Oct 3, 2008 at 9:29 AM, Daniel Kutik [EMAIL PROTECTED] wrote: How could I install this fix manually (not over the internet). At the time I've got no other connection as a wired. Is there a possibility to update the system via usb stick? -- [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: In Progress 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: Confirmed 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 (search for em0) http://www.mail-archive.com/[EMAIL PROTECTED]/msg00360.html http://www.mail-archive.com/[EMAIL PROTECTED]/msg00398.html -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
This is very creepy that Linux can permanently damage hardware! How can this be? Why? How can it be prevented? Does it really need to do these risky operations? Similar things must never happen in the future! Completely unacceptable! If Linux permanently damages peoples hardware, then nobody will dare to try Linux, and how can I recommend it to friends? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Fred, please comment only if you can provide relevant informations about this bug, and use forums if you just want to complain. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
The bug is not fixed yet except to disable the driver. I just upgraded from 8.04 to 8.10 beta using update manager and the the card on a HP dc7800 was disabled. One problem with this is that once upgraded, you have no connection to the internet to get fixes. Had to do a fresh reinstall 8.04. I understand this is a beta version, but it seems a beta release should be further along. ** Changed in: linux (Ubuntu Intrepid) Status: Fix Released = In Progress -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Mandriva) Status: Confirmed = Fix Released -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Michael, I don't believe the new package has been made available to download in repositories yet, (i just checked). Once the new package is there, I would test the upgrade again, for now you can use an older kernel and it should work. I am not going to change back to Fix Released in case i am mistaken, but I don't think the fix has been made available yet. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Is there a way for me to unblacklist this until the update? The card worked fine until I updated to the kernel with the blacklist. - Or is this really a danger even if it works? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Everyone here needs one answer. If we run 'apt' when are we going to get the 'fix' ? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://launchpad.net/ubuntu/+source/linux/2.6.27-4.7/+build/728333 Status: Failed to upload (...) 2008-10-03 02:46:59 INFORejection during accept. Aborting partial accept. 2008-10-03 02:46:59 WARNING Upload was rejected: 2008-10-03 02:46:59 WARNING Unable to find source package linux/2.6.27-4.7 in intrepid (...) -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
2.6.27-4.7 was rejected because 2.6.27-5.8 had already been uploaded. I just accepted the binaries for 2.6.27-5.8 into the archive, and they should be available within the hour; it will take a little bit longer for the 'linux' etc. metapackages to catch up with this. ** Changed in: linux (Ubuntu Intrepid) Status: In Progress = Fix Released -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Thanks Colin. 2.6.27-5-8 works for me: 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit Network Connection [8086:10f5] (rev 03) -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Will You update/rebuild beta cd/dvd images once fix is released? Sorry for negative opinion but it's ridiculous that many people who have such ethernet cards can't use this beta because of not functional network card and even can't get fixed packages by update without other Internet connection. It should be at least mentioned as warning in release anouncement. In my opinion any release should have been delayed because of such bugs. I really like Kubuntu and Ubuntu distributions but it's release cycles should be more flexible to make the best product as it can be. For example I can't even boot Ubuntu Hardy Heron (LTS) shipped CDs on about 80% PCs around on which Gutsy Gibbon worked without problems and I still can't use my DVD+/-RW drive at home with latest Hardy kernel updates - I need to use Gutsy kernel. And once more sorry for a little OT. Keep up good 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Will You update/rebuild beta cd/dvd images once fix is released? No. The fix will be included in the subsequent daily images, in the release candidate image, and in the final release. It should be at least mentioned as warning in release anouncement. It was. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
You could also probably just put the kernel packages on a flash drive, and install them manually. On Fri, Oct 3, 2008 at 2:32 PM, Steve Langasek [EMAIL PROTECTED] wrote: Will You update/rebuild beta cd/dvd images once fix is released? No. The fix will be included in the subsequent daily images, in the release candidate image, and in the final release. It should be at least mentioned as warning in release anouncement. It was. -- [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. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
This seems to give some hope, even on de-bricking hardware... http://lkml.org/lkml/2008/10/1/368 Is it? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
On Wed, Oct 1, 2008 at 7:46 PM, vjohn [EMAIL PROTECTED] wrote: So, the Intel haven't opened the code of your hardware? So, how it's happen? It's happen because it isn't a stable kernel release, and because linux is developed by humans, and they might make mistakes. And I think the linux testing team was to small to reveal this bug. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
And because, after they learned about the problem, they failed to communicate effectively and never removed the cd-image. This has never happened before, and obviously there was no policy for this situation. Which automatically means that some developpers turn into 'its your fault'-mode and be less supportive of the community members who have bricked their hardware. It turned into a blame game. There were more it's an alpha .. you knew what you were getting it to expressions than any compassion. Worse, appearantly its easier to type it's an alpha .. off course it's going to break your hardware .. and you test on your own risk .. 10 times .. than to put a warning up. At least: it was said at least 10 times before the warning was up. That speaks volumes about priority. And the image is still available and linked to from many places that do not contain the warning. The mistake was just an oopsie .. the aftermath, how it was being dealt with, (and still is) .. a PR horror. 2008/10/2 Lorenzo Zolfanelli [EMAIL PROTECTED] On Wed, Oct 1, 2008 at 7:46 PM, vjohn [EMAIL PROTECTED] wrote: So, the Intel haven't opened the code of your hardware? So, how it's happen? It's happen because it isn't a stable kernel release, and because linux is developed by humans, and they might make mistakes. And I think the linux testing team was to small to reveal this bug. Apologetic. -- [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. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Indeed the alpha release should have been replaced in a hurry by a new release with the module blacklisted. What I see from outside is that the burocratic need to release images only at established dates is preventing a well known practice - release a fixed iso in a hurry - to happen. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
http://ubuntuforums.org/showthread.php?p=5889487#post5889487 -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Some people might have been around long enough to remember the Xorg breaking dapper update in 2006. There are quite a few similarities in what happened and peoples responses. After the incident there was a report, and changes were made to make sure it did not happen again [0,1]. Once this has settled down I am sure there will be a report with recommendations. More angry messages here are not needed. Take discussions to the forum or the devel-discuss mailing list. [0] http://www.markshuttleworth.com/archives/54 [1] http://err.no/personal/blog/tech/Ubuntu/2006-08-24-11-36_broken_X_in_Ubuntu.html -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Hi people, sorry by angry message, but I'm realy needing my onboard network working in gnu/linux... Yesterday I have installed m$ windows in my machine to test the onboard network card (for something it's work! hehe) and it work fine in windows... only in linux box have the The NVM Checksum Is Not Valid... So the network card remain working... Of course the gnu/linux is develloped by humans, but the kernel team need do more testing in new releases, because have a great responsability in thousands machines runing this great operating system! Thanks a lot and I will wait the solution, when it appear... Vinicius -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
** Changed in: linux (Suse) Status: Incomplete = In Progress -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
This bug is in an alpha release which is using a release candidate version of the kernel so I think your comments are too tough. Why don't you use hardy as suggested in many places in Ubuntu documentation? My only concern about the present bug is that it discourages testers of alpha software who may not wish to see their hardware compromised. This is not good for the eventual stability of the final release. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Hi, Quoting vjohn [EMAIL PROTECTED]: Hi people, sorry by angry message, but I'm realy needing my onboard network working in gnu/linux... Yesterday I have installed m$ windows in my machine to test the onboard network card (for something it's work! hehe) You definatly should *NOT* be running Alpha or Beta software on a work-critical machine, the workarround is to install an older kernel, see the big warning topic on the forums. (http://ubuntuforums.org/showpost.php?p=5882185postcount=38) and it work fine in windows... only in linux box have the The NVM Checksum Is Not Valid... So the network card remain working... Of course the gnu/linux is develloped by humans, but the kernel team need do more testing in new releases, What do you think the point is of Beta Alpha releases? To test the code on a larger ecosystem containing alot more diverse hardware, the whole discussion is pointless anyway, people clearly don't read warnings or even solutions when they're staring them in the face. because have a great responsability in thousands machines runing this great operating system! Thanks a lot and I will wait the solution, when it appear... Vinicius If my reply sounds abit bitter, it's probably because i am, there's been alot of whining wailing about how they were supposed to do this that pull iso's etc etc etc etc ad infinitum, blah -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
What make's an alpha or beta tester's hardware less valuable than the hardware the final release is installed on? In many cases it is the same hardware. While I agree many install alpha or beta releases when they shouldn't, a large number of people are actually working to do testing, and their complaints are valid. If I or anybody sounds like they are whining wailing it is because their hardware is valuable, and they are doing a service to you and everybody else. On Thu, Oct 2, 2008 at 9:06 AM, Amon_Re [EMAIL PROTECTED] wrote: Hi, Quoting vjohn [EMAIL PROTECTED]: Hi people, sorry by angry message, but I'm realy needing my onboard network working in gnu/linux... Yesterday I have installed m$ windows in my machine to test the onboard network card (for something it's work! hehe) You definatly should *NOT* be running Alpha or Beta software on a work-critical machine, the workarround is to install an older kernel, see the big warning topic on the forums. (http://ubuntuforums.org/showpost.php?p=5882185postcount=38) and it work fine in windows... only in linux box have the The NVM Checksum Is Not Valid... So the network card remain working... Of course the gnu/linux is develloped by humans, but the kernel team need do more testing in new releases, What do you think the point is of Beta Alpha releases? To test the code on a larger ecosystem containing alot more diverse hardware, the whole discussion is pointless anyway, people clearly don't read warnings or even solutions when they're staring them in the face. because have a great responsability in thousands machines runing this great operating system! Thanks a lot and I will wait the solution, when it appear... Vinicius If my reply sounds abit bitter, it's probably because i am, there's been alot of whining wailing about how they were supposed to do this that pull iso's etc etc etc etc ad infinitum, blah -- [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. -- Tom McKay -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Hey guys, Let's use this bug tracker to get the problem fixed. Can we please keep the discussion of whether or not to pull the CD image to the forums or mailing lists? This is a place to talk about the bug *itself* and how to get the bug *itself* fixed, not to discuss the implications of this bug. I bet we can get this dilemma fixed MUCH faster if we stop pointing fingers, stop bickering about what to do with the CD image, and start hacking. Why do I say this? Nicorac posted a link to the Linux Kernel Mailing list. I'll repost it here so you don't have to scroll up: http://lkml.org/lkml/2008/10/1/368 From the page: Currently we (Intel Ethernet) are reproducing the issue on multiple machines in house, we are working on the issue with the other core Linux teams here at Intel and within the community. No resolution yet but we are much closer now. Later we will post patches to help users who have had this problem restore their eeprom from either a saved image from ethtool -e or from another identical system. This means that your hardware is NOT permanently bricked. When someone writes the Lazarus program to resurrect your NIC from the dead, everything will be OK and your computer will return to normal. So, because your hardware is not permanently in danger, let's focus on getting the bug fixed now before 8.10 ships and clean up the aftermath later. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
A small Button with the phrase Don't Panic on it ... http://lkml.org/lkml/2008/10/1/368 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4a7703582836f55a1cbad0e2c1c6ebbee3f9b3a7 This patch is meant to prevent all future corruptions of the e1000e NVM (non volatile memory) after the driver is loaded. The registers stay locked until the machine is power cycled. Does this impose any user-visible behavior change? (such as not being able to set up wake-on-lan, change MAC address, whatever). no, because none of that is stored permanently in the eeprom unless you do writes with ethtool -E. Our policy for the driver is generally don't ever write to the eeprom. So all the normal paths (except for initial start on preproduction hardware and ethtool -E writes) do not write to the eeprom. Currently the driver will let you try to commit a change but with this patch it will never get written to NVM unless you reboot, load driver (the first time!) with WriteProtectNVM=0 and *then* do ethtool -E. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
So can we expect an Ubuntu Alpha 7 with this Intel provide eeprom protection patch and the removal of the e1000 blacklisting? This will allow me to continue testing Intrepid on a machine with e1000 (and it needs at least Alpha 6 anyway because it has GMA 45000 graphics). Or is the hope that beta will wait for this critical problem to be fixed. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
I'm using intel based HP dc5800 Desktop with Ethernet card that is using the bad drivers. I've migrated to Intrepid after alpha 2 was released and unti the e1000e driver was blacklisted (i've noticed no eth0 :) ) I had no problems. Now I'm using external LAN and my dualboot Vista is working great with the internal card. No corruption with me. If someone wants safe, use Hardy, Gutsy, Feisty or Debian.. Here be dragons, isn't right? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
Well, those patches were released in the last two or three days -- basically, we have to wait for upstream kernel devs who are capable/willing to reproduce the issue to test the patches, and then consider how to get that code into the Ubuntu kernel. (Directly applying patches? Go through Debian first? etc. etc.) Another issue is that the kernel freeze is on October 16th[1]. I don't think it would be nice to ship with e1000e blacklisted, so if the resolution isn't tested/approved by then, a release manager will need to grant an exemption to push the release date back into November. [1] https://wiki.ubuntu.com/IntrepidReleaseSchedule -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
The patch is already committed to ubuntu git branch of the kernel. All ubuntu packages have been frozen for a few days for the beta release. I dont think there is any chance of putting a new kernel in the beta at this stage. After the beta is out there will most likely be a kernel update with the fix/workaround. I would expect that this will be in the next few days, assuming nobody finds any problems with it. There should also be a restore tool quite soon, for anyone who has had their card corrupted. I am not sure if any ubuntu tester were actually effected. -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
So will the nic drivers be blacklisted in the beta? And hopefully updated later with a patch? -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
