[Bug 1758273] [NEW] DD2.2 freezes/hangs after 20mins of uptime

[bugproxy]

Public bug reported:

== Comment: #0 - Application Cdeadmin  - 2018-03-19 09:30:53 ==
== Comment: #1 - Application Cdeadmin <> - 2018-03-19 09:30:55 ==
== Comment: #2 - Application Cdeadmin <> - 2018-03-19 09:30:57 ==
--- Comment From brihh 2018-03-19 09:10:30 EDT ---
Needless to say, machine is pretty unusable. Needed for Performance testing for 
release.

== Comment: #3 - Application Cdeadmin <> - 2018-03-19 10:10:59 ==
--- Comment From vaibhav92 2018-03-19 10:06:17 EDT ---
@pridhiviraj Any idea who can look into this ?
--- Comment From dougmill-ibm 2018-03-19 10:09:59 EDT ---
If machine is locked-up and console is unresponsive, try collecting eSEL data 
from the BMC.

== Comment: #4 - Application Cdeadmin  - 2018-03-19 10:40:59 ==
--- Comment From pridhiviraj 2018-03-19 10:38:47 EDT ---
@brihh Can you use latest 03/15 PNOR and re-create the issue. And also before 
it hangs please collect OPAL and kernel logs. @vaibhav92 If it is re-creatable 
OPAL/EM team need to look at it.

== Comment: #5 - Application Cdeadmin <> - 2018-03-19 11:01:58 ==
--- Comment From vaibhav92 2018-03-19 10:41:53 EDT ---
Saw this in the kernel-log of the system:

[ 1247.404962] PM: suspend entry (s2idle)
[ 1247.404970] PM: Syncing filesystems ... done.

Looks like its getting suspended after 20 mins of inactivity. Looking at the 
/etc/systemd/logind.conf see IdleAction by default is 'ignore':
#IdleAction=ignore
#IdleActionSec=30min

But clearly someone is issuing a suspend to the system. So this probably need 
to be looked by the distro/Power-Management/EM team
--- Comment From megcurry 2018-03-19 10:43:14 EDT ---
Please advise re. Assignments and Labels that would get the right team working 
on this.Mirror label gets a Bz opened, and that is necessary or at least 
useful for some of the LTC teams to look at things, right?
--- Comment From brihh 2018-03-19 10:47:45 EDT ---
odd about inactivity - i once had a test running for 20mins and it still froze:

`08:52:23 up 20 min,  4 users,  load average: 64.40, 98.94, 64.32`
--- Comment From brihh 2018-03-19 10:49:30 EDT ---
@pridhiviraj  where is the latest 3/15 PNOR that I can load?

```

== Comment: #8 - Application Cdeadmin <> - 2018-03-19 12:40:54 ==
--- Comment From pridhiviraj 2018-03-19 12:34:18 EDT ---
```
Mar 19 11:35:01 p215n15 rsyslogd-2007: action 'action 13' suspended, next retry 
is Mon Mar 19 11:35:31 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Mar 19 11:35:01 p215n15 CRON[6464]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
Mar 19 11:42:39 p215n15 systemd[1]: Starting Cleanup of Temporary Directories...
Mar 19 11:42:39 p215n15 rsyslogd-2007: action 'action 13' suspended, next retry 
is Mon Mar 19 11:43:39 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Mar 19 11:42:40 p215n15 systemd-tmpfiles[6504]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Mar 19 11:42:40 p215n15 systemd[1]: Started Cleanup of Temporary Directories.
Mar 19 11:45:01 p215n15 rsyslogd-2007: action 'action 13' suspended, next retry 
is Mon Mar 19 11:46:01 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Mar 19 11:45:01 p215n15 CRON[6524]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
Mar 19 11:47:39 p215n15 systemd[1]: Starting Message of the Day...
Mar 19 11:47:39 p215n15 rsyslogd-2007: action 'action 13' suspended, next retry 
is Mon Mar 19 11:48:39 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Mar 19 11:47:40 p215n15 50-motd-news[6528]:  * Meltdown, Spectre and Ubuntu: 
What are the attack vectors,
Mar 19 11:47:40 p215n15 50-motd-news[6528]:how the fixes work, and 
everything else you need to know
Mar 19 11:47:40 p215n15 50-motd-news[6528]:- https://ubu.one/u2Know
Mar 19 11:47:40 p215n15 systemd[1]: Started Message of the Day.
Mar 19 11:48:02 p215n15 NetworkManager[4662]:   [1521474482.7252] 
manager: sleep: sleep requested (sleeping: no  enabled: yes)
Mar 19 11:48:02 p215n15 NetworkManager[4662]:   [1521474482.7259] 
manager: NetworkManager state is now ASLEEP
Mar 19 11:48:02 p215n15 gnome-shell[5538]: Screen lock is locked down, not 
locking
Mar 19 11:48:02 p215n15 whoopsie[5264]: [11:48:02] offline
Mar 19 11:48:02 p215n15 systemd[1]: Reached target Sleep.
Mar 19 11:48:02 p215n15 systemd[1]: Starting Suspend...
Mar 19 11:48:02 p215n15 systemd-sleep[6576]: Suspending system...
Mar 19 11:48:02 p215n15 kernel: [ 1246.906320] PM: suspend entry (s2idle)
```
@vaibhav92 You are right, from the above messages looks like system is 
suspending by some cron job i guess.

== Comment: #9 - Application Cdeadmin <> - 2018-03-19 13:30:57 ==
--- Comment From brihh 2018-03-19 13:28:36 EDT ---
@pridhiviraj interesting. know offhand how i can shut that off? seems a bit 
annoying .. :-)

== Comment: #11 - Application Cdeadmin <> - 2018-03-19 17:10:51 ==
--- Comment From mzipse 2018-03-19 16:52:11 EDT ---
At our daily defect call, it 

[Bug 1719720] [NEW] [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127

[bugproxy]

Public bug reported:

---Problem Description---
Currently syslog is getting flooded with below log messages ..
Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
update' failed with exit code 127.

This is on UBuntu 17.10 latest build.. 
 
---uname output---
Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = ZZ-L 
  
---Steps to Reproduce---
 I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

As suggested in that bug, we did change udev script to create temporary
file under /run and that patch is available in ubuntu 17.10.

Looks like this is udev script issue. If I modify systemd-udevd like
below it works fine.

I've limited udev knowledge. I don't know if you have any other better
solution to this issue.

root@ltc-boston123:/lib/systemd/system# diff -Naurp  systemd-udevd.service.org 
systemd-udevd.service
--- systemd-udevd.service.org   2017-09-26 04:37:47.090057318 -0500
+++ systemd-udevd.service   2017-09-26 04:37:55.381739372 -0500
@@ -25,7 +25,7 @@ KillMode=mixed
 WatchdogSec=3min
 TasksMax=infinity
 MountFlags=slave
-MemoryDenyWriteExecute=yes
+#MemoryDenyWriteExecute=yes
 RestrictRealtime=yes
 RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
 SystemCallArchitectures=native


-Vasant

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-159280 severity-medium 
targetmilestone-inin1710

** Tags added: architecture-ppc64le bugnameltc-159280 severity-medium
targetmilestone-inin1710

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Package changed: ubuntu => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1719720

Title:
  [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with
  exit code 127

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1708409] sosreport

[bugproxy]

Default Comment by Bridge

** Attachment added: "sosreport"
   
https://bugs.launchpad.net/bugs/1708409/+attachment/4926428/+files/sosreport-ltc-test-ci2.kdump-20170803012543.tar.xz

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Package changed: ubuntu => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1708409

Title:
  kdump service does not start after configure/reboot

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1682774] [NEW] [systemd-udevd] Process '/bin/touch /var/lib/lsvpd/run.vpdupdate' failed with exit code 1

[bugproxy]

Public bug reported:

== Comment:  VASANT HEGDE  - 2017-04-13 11:14:43
==

Problem description :
  systemd-udevd daemon failed to execute udev rules.

Aug  9 01:28:43 abc systemd-udevd[19870]: Process '/bin/touch
/var/lib/lsvpd/run.vpdupdate' failed with exit code 1.


Rules file :
---
root@abc:/lib/udev/rules.d# cat 60-libvpd-2.2-2.rules 
KERNELS=="*", ACTION=="*", DEVPATH=="/devices/*", RUN+="/bin/touch 
/var/lib/lsvpd/run.vpdupdate"


If I restart the systemd-udevd daemon then it works fine.
- systemctl restart systemd-udevd


journalctl -u systemd-udevd 
-- Logs begin at Wed 2017-04-12 07:19:26 CDT, end at Thu 2017-04-13 11:11:16 
CDT. --
Apr 12 07:19:26 w37l systemd[1]: Starting udev Kernel Device Manager...
Apr 12 07:19:27 w37l systemd[1]: Started udev Kernel Device Manager.
Apr 12 07:19:27 w37l systemd-udevd[544]: Process '/bin/touch 
/var/lib/lsvpd/run.vpdupdate' failed with exit code 1

systemctl show systemd-udevd

Type=notify
Restart=always
NotifyAccess=main
RestartUSec=0
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
RuntimeMaxUSec=infinity
WatchdogUSec=3min
WatchdogTimestamp=Thu 2017-04-13 10:56:39 CDT
WatchdogTimestampMonotonic=57706791
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=489
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusText=Processing with 72 children at max
StatusErrno=0
Result=success
UID=4294967295
GID=4294967295
ExecMainStartTimestamp=Wed 2017-04-12 07:19:26 CDT
ExecMainStartTimestampMonotonic=4652319
ExecMainExitTimestampMonotonic=0
ExecMainPID=489
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/lib/systemd/systemd-udevd ; argv[]=/lib/systemd/systemd-udevd 
; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; 
status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/systemd-udevd.service
MemoryCurrent=18446744073709551615
CPUUsageNSec=18446744073709551615
TasksCurrent=1
Delegate=no
CPUAccounting=no
CPUWeight=18446744073709551615
StartupCPUWeight=18446744073709551615
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
IOAccounting=no
IOWeight=18446744073709551615
StartupIOWeight=18446744073709551615
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLow=0
MemoryHigh=18446744073709551615
MemoryMax=18446744073709551615
MemorySwapMax=18446744073709551615
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=yes
TasksMax=18446744073709551615
UMask=0022
LimitCPU=18446744073709551615
LimitCPUSoft=18446744073709551615
LimitFSIZE=18446744073709551615
LimitFSIZESoft=18446744073709551615
LimitDATA=18446744073709551615
LimitDATASoft=18446744073709551615
LimitSTACK=18446744073709551615
LimitSTACKSoft=8388608
LimitCORE=18446744073709551615
LimitCORESoft=0
LimitRSS=18446744073709551615
LimitRSSSoft=18446744073709551615
LimitNOFILE=4096
LimitNOFILESoft=1024
LimitAS=18446744073709551615
LimitASSoft=18446744073709551615
LimitNPROC=372260
LimitNPROCSoft=372260
LimitMEMLOCK=65536
LimitMEMLOCKSoft=65536
LimitLOCKS=18446744073709551615
LimitLOCKSSoft=18446744073709551615
LimitSIGPENDING=372260
LimitSIGPENDINGSoft=372260
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=18446744073709551615
LimitRTTIMESoft=18446744073709551615
OOMScoreAdjust=-1000
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=5
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
DynamicUser=no
RemoveIPC=no
MountFlags=524288
PrivateTmp=no
PrivateDevices=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectControlGroups=no
PrivateNetwork=no
PrivateUsers=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
MemoryDenyWriteExecute=yes
RestrictRealtime=yes
RestrictNamespace=2114060288
KillMode=mixed
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=systemd-udevd.service
Names=systemd-udevd.service
Requires=system.slice
Wants=systemd-udevd-kernel.socket systemd-udevd-control.socket
WantedBy=friendly-recovery.service systemd-udev-trigger.service sysinit.target
Before=friendly-recovery.service sysinit.target plymouth-start.service 
systemd-networkd.service
After=systemd-sysusers.service systemd-tmpfiles-setup-dev.service 
systemd-journald.socket system.slice systemd-udevd-kernel.socket 
systemd-udevd-control.socket
TriggeredBy=systemd-udevd-kernel.socket systemd-udevd-control.socket
Documentation=man:systemd-udevd.service(8) man:udev(7)
Description=udev Kernel Device Manager
LoadState=loaded

[Bug 1635423] [NEW] Every 24h we see [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. in the syslog

[bugproxy]

Public bug reported:

Summary
===
zEC12 System LPAR
Linux r35lp50 4.4.0-42-generic #62-Ubuntu SMP Fri Oct 7 23:12:40 UTC 2016 s390x 
s390x s390x GNU/Linux


Details
===
Every 24h systemd-tmpfiles is logging a message similar to this:
Oct 18 15:18:41 sysname systemd-tmpfiles[34404]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.

We have seen varying times on different Ubuntu system instances.


Additional information
===
Pasting the contents of the '/usr/lib/tmpfiles.d/var.conf' file below:

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

# See tmpfiles.d(5) for details

q /var 0755 - - -

L /var/run - - - - ../run

d /var/log 0755 - - -
f /var/log/wtmp 0664 root utmp -
f /var/log/btmp 0600 root utmp -

d /var/cache 0755 - - -

d /var/lib 0755 - - -

d /var/spool 0755 - - -

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-147749 severity-medium 
targetmilestone-inin1604

** Tags added: architecture-s39064 bugnameltc-147749 severity-medium
targetmilestone-inin1604

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1635423

Title:
  Every 24h we see [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for
  path "/var/log", ignoring.  in the syslog

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1615021] start-udev (modified on initrd)

[bugproxy]

Default Comment by Bridge

** Attachment added: "start-udev (modified on initrd)"
   https://bugs.launchpad.net/bugs/1615021/+attachment/4724078/+files/start-udev

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

** Package changed: ubuntu => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1615021

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1608469] xim_root

[bugproxy]

Default Comment by Bridge

** Attachment added: "xim_root"
   
https://bugs.launchpad.net/bugs/1608469/+attachment/4711480/+files/xim_root.zip

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

** Package changed: ubuntu => fcitx-configtool (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fcitx-configtool in Ubuntu.
https://bugs.launchpad.net/bugs/1608469

Title:
  fcitx does not handle  XmbReetIC() properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fcitx-configtool/+bug/1608469/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1602737] SOS report for systemd PCI Roce Interface renaming

[bugproxy]

Default Comment by Bridge

** Attachment added: "SOS report for systemd PCI Roce Interface renaming"
   
https://bugs.launchpad.net/bugs/1602737/+attachment/4700239/+files/sosreport-HGrauer-20160713144947.tar.xz

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1602737

Title:
  PCI RoCE Interface could not be renamed from default name with link
  file

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1589526] sosreport

[bugproxy]

Default Comment by Bridge

** Attachment added: "sosreport"
   
https://bugs.launchpad.net/bugs/1589526/+attachment/4678212/+files/sosreport-O.Baruch-20160606035758.tar.bz2

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1589526

Title:
  fcp multipath devices does not exist after reboot

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs