Re: [E1000-devel] 2.6.27 e1000e EEPROM corruption
Hi Brandeburg, Jesse wrote: yeah, running ibautil appears to pretty well kill many part's NVM. Ah, damn. I've been working a similar thread on the e1000-devel mailing list. The good news is that the LAN parts eeprom is part of the NVM/Flash on the motherboard, so it is at least possible for the bios to fix it. Right now my BIOS says my MAC address is Not applicable. I am relatively sure that this isn't a driver bug, do you have iAMT enabled/system management (aka the ME) on your x300? I'm pretty sure the AMT stuff is disabled in the BIOS. which model x300? 6478-14G if you're comfortable, I would appreciate you resending this to e1000-devel@lists.sourceforge.net cc'd (and so apologies for the lack of decent quoting, I'm leaving all of our mails so the list archive has it. With you, this is basically three users that have this problem and are reporting to us. A lenovo R61, an HP laptop, and your X300. Three completely different designs. I can't speak to the hardware, but it's been my experience that my X300 has very similar intel chips in it to an X61, so it's entirely possible that the R61 has similar parts too. You can try a bios update to reinstall your current version, or downgrade then upgrade again. I was running lenovo's 1.04 bios. I downloaded 1.05b and it's not changed anything. Perhaps the updates don't necessarily rewrite the entire BIOS and include the NVM? Cheers, Chris -Original Message- From: Chris Jones [mailto:[EMAIL PROTECTED] Sent: Friday, August 29, 2008 2:20 PM To: Brandeburg, Jesse Subject: 2.6.27 e1000e EEPROM corruption Hi wrt http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg00333.h tml I have a Thinkpad X300 which I tried out an alpha build of Ubuntu Intrepid (8.10). It uses Intel's 0.4.1.7 e1000e rather than the vanilla kernel.org one, as I understand it. I think the ethernet port worked for a brief while, but then the driver claimed the eeprom checksum was invalid. After some poking around I tried Intel's PROBOOT tool from a freedos disk and ran IBAUTIL -DEFCFG. This claimed the mac address was all ff, and from that point, the device has failed to appear on the PCI bus, so I can't do any further diagnostic or attempted repair work on it. I'm wondering if you would be able to advise me what my options are at this point? My general expectation is that unless Lenovo have a BIOS update which programs a new EEPROM version (I don't think they do, and I'm on the latest BIOS anyway), my only option is to return the unit for repair. Any information you can provide would be hugely appreciated. This is the relevant lspci output for the chip before this happened. 00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM Gigabit Network Connection [8086:1049] (rev 03) Subsystem: Lenovo Device [17aa:20b9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 219 Region 0: Memory at fa20 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at fa225000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 1840 [size=32] Capabilities: [c8] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Address: fee0300c Data: 4152 Kernel driver in use: e1000e Kernel modules: e1000e Cheers, -- Chris Jones [EMAIL PROTECTED] www.canonical.com - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
Re: [E1000-devel] 2.6.27 e1000e EEPROM corruption
Chris Jones wrote: Hi Brandeburg, Jesse wrote: yeah, running ibautil appears to pretty well kill many part's NVM. Ah, damn. upon some follow up questions it appears that ibautil should only ever be run on Intel branded PCI/PCI-X/PCIe adapters that plug into a slot. It may have a bug which allows you to run it where you should not. I've been working a similar thread on the e1000-devel mailing list. The good news is that the LAN parts eeprom is part of the NVM/Flash on the motherboard, so it is at least possible for the bios to fix it. Right now my BIOS says my MAC address is Not applicable. the nvm section that either points to your LAN init area or the NVM section pointed to by that pointer is invalid now. I am relatively sure that this isn't a driver bug, do you have iAMT enabled/system management (aka the ME) on your x300? I'm pretty sure the AMT stuff is disabled in the BIOS. which model x300? 6478-14G if you're comfortable, I would appreciate you resending this to e1000-devel@lists.sourceforge.net cc'd (and so apologies for the lack of decent quoting, I'm leaving all of our mails so the list archive has it. With you, this is basically three users that have this problem and are reporting to us. A lenovo R61, an HP laptop, and your X300. Three completely different designs. I can't speak to the hardware, but it's been my experience that my X300 has very similar intel chips in it to an X61, so it's entirely possible that the R61 has similar parts too. Right, even looks like bioses are the same. X61 (I have one) has an 82573 part on it, which is a LAN part that is not integrated into the chipset, but I think the NVM for that part can be integrated into the system. You can try a bios update to reinstall your current version, or downgrade then upgrade again. I was running lenovo's 1.04 bios. I downloaded 1.05b and it's not changed anything. Perhaps the updates don't necessarily rewrite the entire BIOS and include the NVM? Yes, not all bioses will upgrade the NVM for the lan. Chances are good that if the file size is larger it will upgrade more of the NVM, hopefully upgrading the LAN NVM as well (check the release notes) I've also procured a thinkpad R61 pre-production for some testing next week. Telling us anything that you might have done which could help us reproduce this would be appreciated. Jesse - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
Re: [E1000-devel] 2.6.27 e1000e EEPROM corruption
Hi Brandeburg, Jesse wrote: Yes, not all bioses will upgrade the NVM for the lan. Chances are good that if the file size is larger it will upgrade more of the NVM, hopefully upgrading the LAN NVM as well (check the release notes) None of the release notes for it mention the network chip specifically. The changelog is at: http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovolndocid=MIGR-69539 Telling us anything that you might have done which could help us reproduce this would be appreciated. The timeline is something like this: * Some months ago - I buy the laptop, format it without booting Windows and install Ubuntu Hardy on it (2.6.24). LAN part works perfectly every day. * Last night - I upgraded the machine to Ubuntu Intrepid (2.6.27) at home, but I only use wireless at home, so the LAN part was not used immediately. * Today - I went to work and used the LAN part successfully all morning. * Lunchtime - I reboot the laptop quite a few times to try and figure out a bug with the Intel Xorg driver with Intrepid's X/Mesa. I notice that I am getting an OOPS from the kernel on boot. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/262600 * Between lunch and 15:45 - I reboot a couple of times more to try different things with the graphics driver. * 15:47 - I boot the system and the e1000e driver reports a checksum failure. The LAN part doesn't work again from this point. Tried booting 2.6.24, still errors on the checksum. * This evening - I upgrade the BIOS to 1.05b, no change. * Slightly later this evening - I use qemu to make a bootable freedos USB stick and copy IABUTIL.EXE and EEUPDATE.EXE to it. Boot the image (available on request) and run IABUTIL.EXE -DEFCFG. It claims to have updated and shows a MAC address of ff:ff:ff:ff:ff:ff. I then ran EEUPDATE.EXE and it said it could find no adapters. From this point on, the LAN part is not listed in lspci and the BIOS claims there is no applicable MAC address (where before IABUTIL, but while it was showing invalid checksums, the MAC address would change after each powercycle). I think that's about it. I guess the thing to do is to install Ubuntu Intrepid on there (I think tomorrow's daily cdimage should include the 2.6.27 kernel, but if not you'll get 2.6.26 and .27 will be available from apt), then use the LAN interface and reboot a few times. Hit the network a bunch and see what happens. I don't think I did any particularly large network transfers before it went wrong. I guess it'd be interesting to know if the other folks seeing this have the same OOPS from drm, but I have no idea how likely that is to be related. Cheers, -- Chris Jones [EMAIL PROTECTED] www.canonical.com - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
Re: [E1000-devel] 2.6.27 e1000e EEPROM corruption
Chris Jones wrote: Hi Brandeburg, Jesse wrote: Yes, not all bioses will upgrade the NVM for the lan. Chances are good that if the file size is larger it will upgrade more of the NVM, hopefully upgrading the LAN NVM as well (check the release notes) None of the release notes for it mention the network chip specifically. The changelog is at: http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo; lndocid=MIGR-69539 Telling us anything that you might have done which could help us reproduce this would be appreciated. The timeline is something like this: Thanks for the detailed timeline, I will try to be looking into this or coordinating my team looking into this next Tuesday. As of this point working with Lenovo to get your machine repaired or getting them to give you an app to restore the LAN eeprom is the only way forward. Even if we figure out what is going wrong and reproduce it I don't think I can directly help you get your LAN part to show back up. Somehow you have to get your system NVM (aka flash bios) to get a correct setup, and the only people that have that is Lenovo, since their design is specific. Did you try running IBM's diagnostics programs? They have PC-Doctor bootable CDs but I don't know what they get up to. I sure hope this isn't something new to 2.6.27 (kernel feature, ick) We may need to start talking to LKML soon to make sure this is tracked at that level in case it is a kernel problem of some kind. Jesse - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
