Hi Joseph tank btw so far for ur help uname -a Linux production01 3.13.0-031300rc1-generic #201311291222 SMP Fri Nov 29 17:25:01 UTC 2013 x86_64 GNU/Linux WORKING :-D
Thomas p.s. little problem with your Kernel: dpkg -i linux-image-3.13.0-031300rc1-generic_3.13.0-031300rc1.201311291222_amd64.deb (Reading database ... 149718 files and directories currently installed.) Preparing to replace linux-image-3.13.0-031300rc1-generic 3.13.0-031300rc1.201311291222 (using linux-image-3.13.0-031300rc1-generic_3.13.0-031300rc1.201311291222_amd64.deb) ... Done. Unpacking replacement linux-image-3.13.0-031300rc1-generic ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-031300rc1-generic /boot/vmlinuz-3.13.0-031300rc1-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-031300rc1-generic /boot/vmlinuz-3.13.0-031300rc1-generic Setting up linux-image-3.13.0-031300rc1-generic (3.13.0-031300rc1.201311291222) ... Running depmod. update-initramfs: deferring update (hook will be called later) Not updating initrd symbolic links since we are being updated/reinstalled (3.13.0-031300rc1.201311291222 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (3.13.0-031300rc1.201311291222 was configured last, according to dpkg) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-031300rc1-generic /boot/vmlinuz-3.13.0-031300rc1-generic run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-031300rc1-generic /boot/vmlinuz-3.13.0-031300rc1-generic Error! Bad return status for module build on kernel: 3.13.0-031300rc1-generic (x86_64) Consult /var/lib/dkms/openvswitch/1.9.3+git20131029/build/make.log for more information. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-031300rc1-generic /boot/vmlinuz-3.13.0-031300rc1-generic update-initramfs: Generating /boot/initrd.img-3.13.0-031300rc1-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-031300rc1-generic /boot/vmlinuz-3.13.0-031300rc1-generic Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.13.0-031300rc1-generic Found initrd image: /boot/initrd.img-3.13.0-031300rc1-generic Found linux image: /boot/vmlinuz-3.11-2-amd64 Found initrd image: /boot/initrd.img-3.11-2-amd64 Found linux image: /boot/vmlinuz-3.10-3-amd64 Found initrd image: /boot/initrd.img-3.10-3-amd64 Found linux image: /boot/vmlinuz-3.9-1-amd64 Found initrd image: /boot/initrd.img-3.9-1-amd64 Found linux image: /boot/vmlinuz-3.5.0-44-generic Found initrd image: /boot/initrd.img-3.5.0-44-generic Found linux image: /boot/vmlinuz-3.4.0-3-generic Found initrd image: /boot/initrd.img-3.4.0-3-generic Found linux image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd image: /boot/initrd.img-3.2.0-4-amd64 done Ill attach lspci -vv and dmesg in next two posts Thank you much! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1245938 Title: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Quantal: Confirmed Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have a server (Dell R715) with two Intel x520 NIC's. If we run Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel driver or with Intel compiled one), but if we upgrade release to 12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel drivers fails with error: [ 226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7 [ 226.395770] Copyright (c) 1999-2013 Intel Corporation. [ 226.395980] ixgbe: probe of 0000:22:00.0 failed with error -5 [ 226.396092] ixgbe: probe of 0000:22:00.1 failed with error -5 [ 226.396203] ixgbe: probe of 0000:23:00.0 failed with error -5 [ 226.396311] ixgbe: probe of 0000:23:00.1 failed with error -5 I contacted Intel developers and they responded: "Hey Fernando, We (ixgbe) only returns EIO (error 5) for a couple of reasons. 1) When we fail to io map (ioremap) 2) If the eeprom checksum is incorrect. 3) If the MAC address from the checksum is invalid Reasons 2 and 3 are related to the NIC's eeprom so if they worked with another system they should still be fine now. If you really wanted to verify you could try out the NIC's on a known good system again to see if the eeprom somehow got corrupted. That pretty much leaves us with ioremap returning an error. I'm not at all sure why your Ubuntu release would not like the way we are calling ioremap, but it might give you a place to start looking in Ubuntu changes. Thanks, -Don" If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's works fine. Please let me know how can I help! Regards Fernando To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp