kernel-packages team mailing list archive

[bugproxy <bugproxy@xxxxxxxxxx>]

------- Comment From PSCHMIDT@xxxxxxxxxx 2016-03-07 01:33 EDT-------
Problem persists with kernel 4.4.0-9-generic

Did run some thousand reboots over the weekend....no enccw0.0.f5f0
network available on Monday morning.

uname -a
Linux s8330025 4.4.0-9-generic #24-Ubuntu SMP Mon Feb 29 19:30:59 UTC 2016 s390x
s390x s390x GNU/Linux

root@s8330025:/etc# ip a s
ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enccw0.0.f5f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 02:a2:1e:00:01:43 brd ff:ff:ff:ff:ff:ff
inet 9.152.162.175/22 brd 9.152.163.255 scope global enccw0.0.f5f0
valid_lft forever preferred_lft forever
3: lxcbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether 96:3d:1a:6d:9a:2e brd ff:ff:ff:ff:ff:ff
inet 10.0.3.1/24 scope global lxcbr0
valid_lft forever preferred_lft forever
inet6 fe80::943d:1aff:fe6d:9a2e/64 scope link
valid_lft forever preferred_lft forever

root@s8330025:/etc# ifconfig
ifconfig
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
lxcbr0    Link encap:Ethernet  HWaddr 96:3d:1a:6d:9a:2e
inet addr:10.0.3.1  Bcast:0.0.0.0  Mask:255.255.255.0
inet6 addr: fe80::943d:1aff:fe6d:9a2e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B)  TX bytes:570 (570.0 B)

root@s8330025:/etc# ifup enccw0.0.f5f0
ifup enccw0.0.f5f0
RTNETLINK answers: File exists
Failed to bring up enccw0.0.f5f0.

root@s8330025:/etc# ifdown enccw0.0.f5f0
ifdown enccw0.0.f5f0
ifdown: interface enccw0.0.f5f0 not configured

-- 
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/1552788

Title:
  network lost after large number of reboots

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  network lost after large number of reboots (>500)
   
  Contact Information = pschmidt@xxxxxxxxxx 
   
  ---uname output---
  Linux s8330025 4.4.0-2-generic #16-Ubuntu SMP Thu Jan 28 15:44:18 UTC 2016 s390x s390x s390x GNU/Linux
   
  Machine Type = s390 z/VM Guest 
   
  ---Steps to Reproduce---
   reboot z/VM guest several times >500. After a large number of reboots the network interfaces doesn't come up any more. The z/VM guest boots fine, unless the missing network. Impossible to bring up network again manually.

  ==

  Further debug shows that it is the "ip link set enccw0.0.f5f0 up" that
  is failing with "RTNETLINK answers: Operation not permitted".  Looking
  for further debug assistance in determining why the CAP_NET_ADMIN
  check for the root user running ip might be failing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552788/+subscriptions