[Kernel-packages] [Bug 1552788] Re: network lost after large number of reboots

2016-04-14 Thread Dimitri John Ledkov
Ok cool, thanks a lot for informing us! Closing this bug on launchpad
then.

** Changed in: ubuntu-z-systems
   Status: New => Invalid

-- 
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 Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  network lost after large number of reboots (>500)
   
  Contact Information = pschm...@de.ibm.com 
   
  ---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-z-systems/+bug/1552788/+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


[Kernel-packages] [Bug 1552788] Re: network lost after large number of reboots

2016-04-14 Thread bugproxy
** Tags removed: targetmilestone-inin1604
** Tags added: targetmilestone-inin---

-- 
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 Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  network lost after large number of reboots (>500)
   
  Contact Information = pschm...@de.ibm.com 
   
  ---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-z-systems/+bug/1552788/+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


[Kernel-packages] [Bug 1552788] Re: network lost after large number of reboots

2016-04-14 Thread Dimitri John Ledkov
insufficient information provided by the bug reporter; using a two month
old installation; please upgrade. Closing as invalid until then.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
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 Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  network lost after large number of reboots (>500)
   
  Contact Information = pschm...@de.ibm.com 
   
  ---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-z-systems/+bug/1552788/+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


[Kernel-packages] [Bug 1552788] Re: network lost after large number of reboots

2016-04-14 Thread Dimitri John Ledkov
Looking at interfaces definition - it is still using acient interface
names which are no longer in use. Has this installation been upgraded at
all? The interface name today should be encf5f0 today.

Also:
4   
./sosreport-s8330025-20160224080320/etc/sysconfig/hardware/config-ccw-0.0.f5f0
0   
./sosreport-s8330025-20160224080320/etc/sysconfig/hardware/config-ccw-0.0.eb4a

Are present, which means that this system is not upgraded to have latest
sysconfig-hardware package.

Your installation is really old, and thus is no longer supported, as
common with development series only up to date systems are supported.

Please upgrade your instance to latest packages, and try to reproduce
the problem. With new udev rules managed by chzdev interface bring up
should be more reliable.

-- 
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 Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  network lost after large number of reboots (>500)
   
  Contact Information = pschm...@de.ibm.com 
   
  ---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-z-systems/+bug/1552788/+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


[Kernel-packages] [Bug 1552788] Re: network lost after large number of reboots

2016-04-08 Thread dann frazier
** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

-- 
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 Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  network lost after large number of reboots (>500)
   
  Contact Information = pschm...@de.ibm.com 
   
  ---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-z-systems/+bug/1552788/+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


[Kernel-packages] [Bug 1552788] Re: network lost after large number of reboots

2016-03-11 Thread dann frazier
OK, thanks for the update. Will set to Incomplete for now. Once your
investigation is complete, please change the status back to NEW if you
believe there is an OS issue, or Invalid if the issue needs to be
resolved in the VM layer.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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:
  Incomplete

Bug description:
  ---Problem Description---
  network lost after large number of reboots (>500)
   
  Contact Information = pschm...@de.ibm.com 
   
  ---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

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


[Kernel-packages] [Bug 1552788] Re: network lost after large number of reboots

2016-03-07 Thread Dimitri John Ledkov
** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
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:
  Confirmed

Bug description:
  ---Problem Description---
  network lost after large number of reboots (>500)
   
  Contact Information = pschm...@de.ibm.com 
   
  ---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

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


[Kernel-packages] [Bug 1552788] Re: network lost after large number of reboots

2016-03-07 Thread Dimitri John Ledkov
Hi,

Is the system fully updated since installing, or only selectively? I ask
this, because i would expect the interface name to have been renamed and
migrated to encf5f0 -> shorter prefix, and leading zeros stripped as of
systemd 228-4ubuntu2. Installation was done with  systemd just before
that one. Just a curious note, not assuming it will actually fix this.

The fact that link state is down, and there is no ipv6 address
configured is disturbing.

Three units did fail:
  UNIT LOAD   ACTIVE SUBDESCRIPTION
* console-setup.serviceloaded failed failed Set console keymap
* multipath-tools-boot.service loaded failed failed LSB: early multipath boot 
script
* networking.service   loaded failed failed Raise network interfaces

Fist one is mostly harmless, and should be fixed in latest console-setup.
Last one is disturbing.

And second one:
Is multipath expected to be setup on the system? There are errors from parsing 
the config files:
"Feb 24 08:03:28 | error parsing config file"

Regards,

Dimitri.

-- 
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 = pschm...@de.ibm.com 
   
  ---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

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


[Kernel-packages] [Bug 1552788] Re: network lost after large number of reboots

2016-03-03 Thread Tim Gardner
Can this be reproduced with a recent kernel ? For example,
4.4.0-9-generic.

-- 
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 = pschm...@de.ibm.com 
   
  ---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

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


[Kernel-packages] [Bug 1552788] Re: network lost after large number of reboots

2016-03-03 Thread Kevin W. Rudd
** Package changed: ubuntu => linux (Ubuntu)

-- 
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 = pschm...@de.ibm.com 
   
  ---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

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