------- Comment From mu...@br.ibm.com 2015-12-21 17:07 EDT------- Externalizing comment and closing the issue on our side, since the fix is released and tested. Thank you for the help.
(In reply to comment #29) > thanks Guilherme for the system and getting the system firmware upgraded to > latest SP2. > > Issue seems to fixed with Ubuntu 14.04.04. > > root@ltc-fire2:~# uname -a > Linux ltc-fire2 4.2.0-22-generic #27~14.04.1-Ubuntu SMP Fri Dec 18 10:56:52 > UTC 2015 ppc64le ppc64le ppc64le GNU/Linux > > > root@ltc-fire2:~# cat /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > auto eth4 > iface eth4 inet static > address 9.40.195.137 > netmask 255.255.255.0 > network 9.40.195.0 > broadcast 9.40.195.255 > gateway 9.40.195.1 > # dns-* options are implemented by the resolvconf package, if installed > dns-nameservers 9.3.1.200 > dns-search aus.stglabs.ibm.com > > > > root@ltc-fire2:~# ll /sys/class/net > total 0 > drwxr-xr-x 2 root root 0 Dec 21 09:34 ./ > drwxr-xr-x 58 root root 0 Dec 21 08:59 ../ > lrwxrwxrwx 1 root root 0 Dec 21 08:59 eth0 -> > ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/net/eth0/ > lrwxrwxrwx 1 root root 0 Dec 21 08:59 eth1 -> > ../../devices/pci0004:00/0004:00:00.0/0004:01:00.1/net/eth1/ > lrwxrwxrwx 1 root root 0 Dec 21 08:59 eth2 -> > ../../devices/pci0004:00/0004:00:00.0/0004:01:00.2/net/eth2/ > lrwxrwxrwx 1 root root 0 Dec 21 08:59 eth3 -> > ../../devices/pci0004:00/0004:00:00.0/0004:01:00.3/net/eth3/ > lrwxrwxrwx 1 root root 0 Dec 21 08:59 eth4 -> > ../../devices/pci0001:00/0001:00:00.0/0001:01:00.0/net/eth4/ > lrwxrwxrwx 1 root root 0 Dec 21 08:59 eth5 -> > ../../devices/pci0001:00/0001:00:00.0/0001:01:00.1/net/eth5/ > lrwxrwxrwx 1 root root 0 Dec 21 08:59 lo -> ../../devices/virtual/net/lo/ > root@ltc-fire2:~# route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 0.0.0.0 9.40.195.1 0.0.0.0 UG 0 0 0 eth4 > 9.40.195.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4 > > > > root@ltc-fire2:~# lspci -nn > ... > 0001:00:00.0 PCI bridge [0604]: IBM Device [1014:03dc] > 0001:01:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme II > BCM57810 10 Gigabit Ethernet [14e4:168e] (rev 10) > 0001:01:00.1 Ethernet controller [0200]: Broadcom Corporation NetXtreme II > BCM57810 10 Gigabit Ethernet [14e4:168e] (rev 10) > > > root@ltc-fire2:~# echo 1:1:0:0:0 > > /sys/kernel/debug/powerpc/PCI0001/err_injct > root@ltc-fire2:~# [ 2444.814857] EEH: Frozen PE#1 on PHB#1 detected > [ 2444.815000] EEH: PE location: N/A, PHB location: N/A > [ 2444.816227] bnx2x: [bnx2x_io_error_detected:13743(eth4)]IO error detected > [ 2444.831916] bnx2x: [bnx2x_timer:5761(eth4)]MFW seems hanged: drv_pulse > (0x726) != mcp_pulse (0x7fff) > [ 2444.832477] bnx2x: [bnx2x_io_error_detected:13743(eth5)]IO error detected > [ 2448.850852] bnx2x: [bnx2x_io_slot_reset:13778(eth4)]IO slot reset > initializing... > [ 2448.851245] bnx2x: [bnx2x_io_slot_reset:13794(eth4)]IO slot reset --> > driver unload > [ 2448.932353] bnx2x: [bnx2x_io_slot_reset:13778(eth5)]IO slot reset > initializing... > > > > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.814857] EEH: Frozen PE#1 on PHB#1 > detecc > ted > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.815000] EEH: PE location: N/A, PHB > locaa > tion: N/A > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.816220] EEH: This PCI device has > failedd > 1 times in the last hour > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.816222] EEH: Notify device drivers > to ss > hutdown > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.816227] bnx2x: > [bnx2x_io_error_detectedd > :13743(eth4)]IO error detected > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.831916] bnx2x: > [bnx2x_timer:5761(eth4)]] > MFW seems hanged: drv_pulse (0x726) != mcp_pulse (0x7fff) > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832477] bnx2x: > [bnx2x_io_error_detectedd > :13743(eth5)]IO error detected > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832702] EEH: Collect temporary log > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832705] PHB3 PHB#1 Diag-data > (Version: > 1) > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832707] brdgCtl: 00000002 > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832709] RootSts: 00000040 > 00400000 > f0820048 00100147 00002000 > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832712] PhbSts: > 0000001c00000000 00 > 000001c00000000 > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832712] PhbSts: > 0000001c00000000 00 > 000001c00000000 > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832714] Lem: > 0000001000000004 44 > 2498e327f502eae 0000000000000000 > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832717] OutErr: > 0000000800000000 00 > 000000800000000 0204006000003b10 103c731800000000 > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832719] InBErr: > 0000000000000020 00 > 000000000000020 4001010000000000 0000000000000000 > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832721] PE[ 1] A/B: > 8400001b00000000 88 > 0003b10103c7318 > Dec 21 09:39:47 ltc-fire2 kernel: [ 2444.832724] EEH: Reset without hotplug > actii > vity > Dec 21 09:39:51 ltc-fire2 kernel: [ 2448.850848] EEH: Notify device drivers > the > completion of reset > Dec 21 09:39:51 ltc-fire2 kernel: [ 2448.850852] bnx2x: > [bnx2x_io_slot_reset:1377 > 78(eth4)]IO slot reset initializing... > Dec 21 09:39:51 ltc-fire2 kernel: [ 2448.851097] bnx2x 0001:01:00.0: > enabling dee > vice (0140 -> 0142) > Dec 21 09:39:51 ltc-fire2 kernel: [ 2448.851245] bnx2x: > [bnx2x_io_slot_reset:1377 > 94(eth4)]IO slot reset --> driver unload > Dec 21 09:39:51 ltc-fire2 kernel: [ 2448.932353] bnx2x: > [bnx2x_io_slot_reset:1377 > 78(eth5)]IO slot reset initializing... > Dec 21 09:39:51 ltc-fire2 kernel: [ 2448.932609] bnx2x 0001:01:00.1: > enabling dee > vice (0140 -> 0142) > Dec 21 09:39:51 ltc-fire2 kernel: [ 2448.932747] EEH: Notify device driver > to ree > sume > Dec 21 09:39:51 ltc-fire2 kernel: [ 2449.435871] bnx2x 0001:01:00.0 eth4: > using > MSI-X IRQs: sp 498 fp[0] 502 ... fp[7] 495 > Dec 21 09:39:54 ltc-fire2 kernel: [ 2452.598799] bnx2x 0001:01:00.0 eth4: > NIC Lii > nk is Up, 1000 Mbps full duplex, Flow control: ON - receive & transmit > > > after the EEH , interface is accessible upto 5 EEH per design ** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin14044 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522071 Title: EEH recovery fails for shinner T on firestone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
