Fedora Account System
Red Hat Associate
Red Hat Customer
i've been using fedora12 for quite some time now, and did multiple kernel upgrades since first install. last kernel upgrade i did was 2 days ago for : kernel-2.6.32.11-99.fc12.x86_64 after a reboot 2 days later, i found the system an ultra-24 network-less. After various reboots and digging in system logs what i saw later in dmesg is the following : e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2 e1000e: Copyright (c) 1999-2008 Intel Corporation. alloc irq_desc for 20 on node -1 alloc kstat_irqs on node -1 e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 e1000e 0000:00:19.0: setting latency timer to 64 alloc irq_desc for 26 on node -1 alloc kstat_irqs on node -1 e1000e 0000:00:19.0: irq 26 for MSI/MSI-X 0000:00:19.0: 0000:00:19.0: The NVM Checksum Is Not Valid e1000e 0000:00:19.0: PCI INT A disabled e1000e: probe of 0000:00:19.0 failed with error -5 upon which i googled for 'NVM Checsum Is not Valid' : http://www.google.co.uk/search?q=The+NVM+Checksum+Is+Not+Valid&ie=utf-8&oe=utf-8&aq=t and got reference to 2 already closed bugs : https://bugzilla.redhat.com/show_bug.cgi?id=459202 https://bugzilla.redhat.com/show_bug.cgi?id=459203 I'm not versed enough in kernel matters to decypher all these, but it seems that if fix there was, now regression there is. Could anyone proficient on the matter please comment. Also, I'd appreciate if i could get 'plain' english explanation about the fact that this bug may be destructiv at hardware level. Does this mean that the onboard e1000e controller is busted, hence the whole mother board to change? I read about some Intel tool to fixup the hardware issue, but frankely didn't figure out all ins/outs discussed here. So the basic question is : Is my hardware really busted? If possibly not, then how can i check it up and confirm? If it's fixable given the current kernel, what are the next steps to get it all back and running. Looking forward your feedback Thanks
after upgrading the machine with the latest bios http://www.sun.com/desktop/workstation/ultra24/downloads.jsp The network adapter is again visible at bios level. I had to deconfigure the PCI ethernet adapteur, prior to re-enable the on-board adapter (iva ifconfig down/up) and now all seems good. Yet, i would like to understant the cause that lead to this situation. It's very penalizing (parallizing i should say) to loose onboard network adapater upon a linux upgrade. I'll remain available to provide you with data that you might need to figure things out. thanks
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.