← Back to team overview

kernel-packages team mailing list archive

[Bug 1312230] Missing required logs.

 

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1312230

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: trusty

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

Title:
  powerpc: virsh shutdown & reboot won't work with Ubuntu LE guest OS

Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  virsh shutdown & reboot won't work with Ubuntu Alpha-2 LE guest OS

  This issue seen for PPC64LE Guest OS.

  virsh shutdown & reboot command does not work with LE Guets OS

  Even I have not seen any kernel messages in syslog / dmesg .

  Ubuntu Alpha-2 LE Guest OS :
  ------------------------------------

  root@destiny:~# uname -a
  Linux destiny 3.13.0-5-generic #20-Ubuntu SMP Mon Jan 20 20:03:57 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
  root@destiny:~#
  root@destiny:~#
  root@destiny:~# cat /etc/issue
  Ubuntu Trusty Tahr (development branch) \n \l

  root@destiny:~#

  root@localhost a2]# virsh list --all
   Id Name State
  ----------------------------------------------------
   35 shri_alpha2 running
   47 jagan_ubuntu_alpha2 running
   54 kal_uFeb5_alpha2 running
   - shri_a2 shut off

  [root@localhost a2]#

  [root@localhost ~]# virsh reboot shri_alpha2
  Domain shri_alpha2 is being rebooted

  [root@localhost ~]# virsh list --all
   Id Name State
  ----------------------------------------------------
   2 jagan_ubuntu_alpha2 running
   3 harini running
   4 shri_alpha2 running
   - kal_uFeb5_alpha2 shut off

  [root@localhost ~]#

  [root@localhost ~]# virsh shutdown shri_alpha2
  Domain shri_alpha2 is being shutdown

  [root@localhost ~]#
  [root@localhost ~]# virsh list --all
   Id Name State
  ----------------------------------------------------
   2 jagan_ubuntu_alpha2 running
   3 harini running
   4 shri_alpha2 running
   - kal_uFeb5_alpha2 shut off

  [root@localhost ~]#

  only RTAS: event message will get added in syslog, no other kernel messages related to reboot/shutdown :
  ===========================================================================================

  root@destiny:~# dmesg | tail
  [ 6.841851] type=1400 audit(1391590975.820:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=405 comm="apparmor_parser"
  [ 6.864017] type=1400 audit(1391590975.840:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=407 comm="apparmor_parser"
  [ 8.508839] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
  [ 8.509752] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [ 9.268663] IPv6: eth0: IPv6 duplicate address fe80::5054:ff:feb3:2df8 detected!
  [ 9.340129] init: failsafe main process (495) killed by TERM signal
  [ 9.996017] init: plymouth-stop pre-start process (728) terminated with status 1
  [ 105.190734] random: nonblocking pool is initialized
  [ 115.952677] RTAS: event: 1, Type: EPOW, Severity: 4
  [ 178.118201] RTAS: event: 2, Type: EPOW, Severity: 4
  root@destiny:~#

  root@destiny:~# cat /var/log/syslog | tail
  Feb 5 03:02:58 destiny dhclient: bound to 192.168.122.73 -- renewal in 1453 seconds.
  Feb 5 03:02:58 destiny kernel: [ 9.268663] IPv6: eth0: IPv6 duplicate address fe80::5054:ff:feb3:2df8 detected!
  Feb 5 03:02:58 destiny cron[652]: (CRON) INFO (pidfile fd = 3)
  Feb 5 03:02:58 destiny cron[674]: (CRON) STARTUP (fork ok)
  Feb 5 03:02:58 destiny cron[674]: (CRON) INFO (Running @reboot jobs)
  Feb 5 03:02:58 destiny /usr/sbin/irqbalance: Balancing is ineffective on systems with a single cache domain. Shutting down
  Feb 5 05:04:04 destiny ntpdate[566]: step time server 91.189.94.4 offset 7259.802352 sec
  Feb 5 05:05:33 destiny kernel: [ 105.190734] random: nonblocking pool is initialized
  Feb 5 05:05:44 destiny kernel: [ 115.952677] RTAS: event: 1, Type: EPOW, Severity: 4 <---------------
  Feb 5 05:06:46 destiny kernel: [ 178.118201] RTAS: event: 2, Type: EPOW, Severity: 4 <---------------
  root@destiny:~#

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


References