kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #138547
[Bug 1497966] [NEW] ISST-KVM:R3-0:Firestone:Ubuntu14043:beng2:Cannot reach network with Shiner T adapter
You have been subscribed to a public bug:
Problem Description:
===================
- Ping hangs or throws error message "Destination Host Unreachable" when IP is configured over pci-pt Shiner T adapter interface either dhcp entry or assigning IP statically assigning IP.
Steps to Reproduce:
==================
- beng2 has been installed with daily build 20150914
Logs:
====
root@beng2:~# uname -a
Linux beng2 3.19.0-28-generic #30~14.04.1-Ubuntu SMP Tue Sep 1 09:32:56 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
root@beng2:~#
- beng2 has pci-pt of Shiner T adapter and was netbooted via virtual ethernet interface(eth0)
- beng2 IP was configured at eth0 via dhcp and was fine working.
- When I tried to configure IP over shiner T adapter's interface, I can configure IP over eth3(link detected is yes)
Logs:
====
root@beng2:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 52:54:00:25:6c:f0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:21
eth3 Link encap:Ethernet HWaddr 40:f2:e9:31:15:e1
inet addr:10.33.33.1 Bcast:10.33.255.255 Mask:255.255.0.0
inet6 addr: fe80::42f2:e9ff:fe31:15e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1600 (1.6 KB)
Interrupt:17 Memory:10121800000-10121ffffff
eth4 Link encap:Ethernet HWaddr 40:f2:e9:31:15:e0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:17 Memory:10120000000-101207fffff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:49 errors:0 dropped:0 overruns:0 frame:0
TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4182 (4.1 KB) TX bytes:4182 (4.1 KB)
root@beng2:~# ethtool eth3
Settings for eth3:
Supported ports: [ TP ]
Supported link modes: 100baseT/Half 100baseT/Full
1000baseT/Full
10000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Advertised link modes: 100baseT/Half 100baseT/Full
1000baseT/Full
10000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 100baseT/Half 100baseT/Full
1000baseT/Full
10000baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 17
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000000 (0)
Link detected: yes
root@beng2:~#
- But it hangs when I try to ping network or ping fails with error message "destination host unreachable) though the gateway has been added.
root@beng2:~# ping -I eth3 kte
^C
root@beng2:~#
root@beng2:~# ping -I eth3 10.33.0.1
PING 10.33.0.1 (10.33.0.1) from 10.33.33.1 eth3: 56(84) bytes of data.
>From 10.33.33.1 icmp_seq=1 Destination Host Unreachable
>From 10.33.33.1 icmp_seq=2 Destination Host Unreachable
>From 10.33.33.1 icmp_seq=3 Destination Host Unreachable
^C
--- 10.33.0.1 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4024ms
pipe 3
root@beng2:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.33.0.1 0.0.0.0 UG 0 0 0 eth3
10.33.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth3
root@beng2:~# netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.33.0.1 0.0.0.0 UG 0 0 0 eth3
10.33.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth3
root@beng2:~#
- The same issue is seen when I configured IP via dhcp or statically
assigned IP over pci-pt shiner T adapter interface either.
Logs:
====
root@beng2:~# 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 eth3
iface eth3 inet static
address 10.33.33.1
gateway 10.33.0.1
netmask 255.255.0.0
# This is an autoconfigured IPv6 interface
iface eth3 inet6 auto
root@beng2:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-3.19.0-28-generic root=UUID=f8b193d1-546f-4025-b233-99f3d77a8a4a ro xmon=on splash quiet vt.handoff=7
root@beng2:~#
- Unable to generate sosreport since it got hanged in the following:
Logs:
====
[root@benkvm ~]# sosreport
sosreport (version 3.2)
This command will collect system configuration and diagnostic
information from this PowerKVM system. An archive containing the
collected information will be generated in /var/tmp.
For more information on IBM visit:
http://www-03.ibm.com/systems/power/software/linux/powerkvm
The generated archive may contain data considered sensitive and its
content should be reviewed by the originating organization before being
passed to any third party.
No changes will be made to system configuration.
Press ENTER to continue, or CTRL-C to quit.
Please enter your first initial and last name [benkvm.isst.aus.stglabs.ibm.com]:
Please enter the case id that you are generating this report for: beng2
Setting up archive ...
Setting up plugins ...
Running plugins. Please wait ...
Running 62/85: process...
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Taco Screen team (taco-screen-team)
Status: New
** Tags: architecture-ppc64 bot-comment bugnameltc-130843 severity-critical targetmilestone-inin1510
--
ISST-KVM:R3-0:Firestone:Ubuntu14043:beng2:Cannot reach network with Shiner T adapter
https://bugs.launchpad.net/bugs/1497966
You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
