[Bug 1317651] Re: ppc: VM hangs on first boot after network install
Servergy went out of business in 2015 after SEC stock fraud scandal. This bug is no longer relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317651 Title: ppc: VM hangs on first boot after network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1317651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317664] Re: qtemu crashes creating ppc image
Servergy went out of business in 2015 after SEC stock fraud scandal. This bug is no longer relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317664 Title: qtemu crashes creating ppc image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtemu/+bug/1317664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304045] Re: rpciod: page alloc error no
Servergy went out of business in 2015 after SEC stock fraud scandal. This bug is no longer relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304045 Title: rpciod: page alloc error no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1304045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276290] Re: Oops in rpc_remove_client_dir (NFS mount)
Servergy went out of business in 2015 after SEC stock fraud scandal. This bug is no longer relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276290 Title: Oops in rpc_remove_client_dir (NFS mount) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1276290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313896] Re: edac start-up fails for ppc ; missing p4080 config info
Servergy went out of business in 2015 after SEC stock fraud scandal. This bug is no longer relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313896 Title: edac start-up fails for ppc ; missing p4080 config info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edac-utils/+bug/1313896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317960] Re: ppc: qemu launcher fails to start e500mc netinstaller VM
Servergy went out of business in 2015 after SEC stock fraud scandal. This bug is no longer relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317960 Title: ppc: qemu launcher fails to start e500mc netinstaller VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-launcher/+bug/1317960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] Re: Enabling lock checking in ppc-e500mc produces bug checks
Servergy went out of business in 2015 after SEC stock fraud scandal. This bug is no longer relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1324640] Re: vm-builder fails on creating ppc images
Servergy went out of business in 2015 after SEC stock fraud scandal. This bug is no longer relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1324640 Title: vm-builder fails on creating ppc images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1324640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279403] Re: udlfd video driver hangs " BUG: scheduling while atomic " iscsi booted initrd : (trusty)
Servergy closed in 2015 after SEC stock fraud scandal. This bug is no longer relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279403 Title: udlfd video driver hangs " BUG: scheduling while atomic " iscsi booted initrd : (trusty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1279403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317603] Re: qemu-system-ppc does not terminate on VM exit
I am no longer working on this project, -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1317603] Re: qemu-system-ppc does not terminate on VM exit
I am no longer working on this project, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1324640] [NEW] vm-builder fails on creating ppc images
Public bug reported:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS
(trusty)root@jade-rev4:/etc# uname -a
Linux jade-rev4 3.13.0-24-powerpc-e500mc #46-Ubuntu SMP Thu Apr 10 19:52:34 UTC
2014 ppc ppc ppc GNU/Linux
(trusty)root@jade-
(trusty)root@jade-rev4:~# vmbuilder kvm ubuntu --suite trusty --flavour virtual
--arch ppce500 -o --libvirt qemu:///system
2014-05-29 12:26:42,551 INFO: logging to file: /tmp/tmp4PWYvg
Traceback (most recent call last):
File /usr/bin/vmbuilder, line 24, in module
cli.main()
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 142,
in main
hypervisor, distro = self.handle_args(optparser, args)
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 297,
in handle_args
distro = VMBuilder.get_distro(args[1])()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 75, in
__init__
super(Distro, self).__init__()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 31, in
__init__
self.plugins = [plugin_class(self) for plugin_class in self.plugin_classes]
File /usr/lib/python2.7/dist-packages/VMBuilder/plugins/__init__.py, line
46, in __init__
self.register_options()
File
/usr/lib/python2.7/dist-packages/VMBuilder/plugins/network/__init__.py, line
70, in register_options
domainname =
'.'.join(socket.gethostbyname_ex(socket.gethostname())[0].split('.')[1:]) or
defaultdomain
socket.gaierror: [Errno -5] No address associated with hostname
(trusty)root@jade-rev4:~# vmbuilder kvm ubuntu --suite trusty --flavour virtual
--arch ppce500 -o --libvirt qemu:///system
2014-05-29 12:27:21,211 INFO: logging to file: /tmp/tmpUKkpet
Traceback (most recent call last):
File /usr/bin/vmbuilder, line 24, in module
cli.main()
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 142,
in main
hypervisor, distro = self.handle_args(optparser, args)
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 297,
in handle_args
distro = VMBuilder.get_distro(args[1])()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 75, in
__init__
super(Distro, self).__init__()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 31, in
__init__
self.plugins = [plugin_class(self) for plugin_class in self.plugin_classes]
File /usr/lib/python2.7/dist-packages/VMBuilder/plugins/__init__.py, line
46, in __init__
self.register_options()
File
/usr/lib/python2.7/dist-packages/VMBuilder/plugins/network/__init__.py, line
70, in register_options
domainname =
'.'.join(socket.gethostbyname_ex(socket.gethostname())[0].split('.')[1:]) or
defaultdomain
socket.gaierror: [Errno -5] No address associated with hostname
(trusty)root@jade-rev4:~# cat /tmp/tmpUKkpet
2014-05-29 12:27 INFO: logging to file: /tmp/tmpUKkpet
2014-05-29 12:27 DEBUG : Loading plugins
2014-05-29 12:27 DEBUG : ['dpkg', '--print-architecture']
2014-05-29 12:27 DEBUG : powerpc
(trusty)root@jade-rev4:~# dpkg --print-architecture
powerpc
(trusty)root@jade-rev4:~# vmbuilder kvm ubuntu --suite trusty --flavour virtual
--arch ppce500 -o --libvirt qemu:///system
2014-05-29 12:28:39,097 INFO: logging to file: /tmp/tmp6Npv0z
Traceback (most recent call last):
File /usr/bin/vmbuilder, line 24, in module
cli.main()
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 142,
in main
hypervisor, distro = self.handle_args(optparser, args)
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 297,
in handle_args
distro = VMBuilder.get_distro(args[1])()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 75, in
__init__
super(Distro, self).__init__()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 31, in
__init__
self.plugins = [plugin_class(self) for plugin_class in self.plugin_classes]
File /usr/lib/python2.7/dist-packages/VMBuilder/plugins/__init__.py, line
46, in __init__
self.register_options()
File
/usr/lib/python2.7/dist-packages/VMBuilder/plugins/network/__init__.py, line
70, in register_options
domainname =
'.'.join(socket.gethostbyname_ex(socket.gethostname())[0].split('.')[1:]) or
defaultdomain
socket.gaierror: [Errno -5] No address associated with hostname
(trusty)root@jade-rev4:~# vmbuilder kvm ubuntu --suite trusty --flavour virtual
--arch ppce500
2014-05-29 12:28:56,995 INFO: logging to file: /tmp/tmpG6Puxi
Traceback (most recent call last):
File /usr/bin/vmbuilder, line 24, in module
cli.main()
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 142,
in main
hypervisor, distro = self.handle_args(optparser, args)
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 297,
in handle_args
distro = VMBuilder.get_distro(args[1])()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 75, in
__init__
super(Distro,
[Bug 1317664] Re: qtemu crashes creating ppc image
I made sure all the dependencies were installed: apt-get install -y cmake quilt libqt4-dev libqtwebkit-dev libvncserver- dev -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317664 Title: qtemu crashes creating ppc image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtemu/+bug/1317664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318629] Re: book3e bootloader recommendation should point to grub-ieee1275
This fix needs applied to a ISO image ; Where can I find that image at ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318629 Title: book3e bootloader recommendation should point to grub-ieee1275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1318629] Re: book3e bootloader recommendation should point to grub-ieee1275
Hi, This change needs applied to a ISO image for installation; Where can I locate that image ? Regards, John. -- o Energy-efficiency is #1 reason data centers look to expand. -- Digital Realty Trust o Green Data Centers spending to increase 300% worldwide by 2016. -- Pike Research o Data Centers have become as vital to the functioning of society as power stations. -- The Economist On Thu, May 29, 2014 at 7:55 AM, Luis Henriques luis.henriq...@canonical.com wrote: This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are subscribed to a duplicate bug report (1317925). https://bugs.launchpad.net/bugs/1318629 Title: book3e bootloader recommendation should point to grub-ieee1275 Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: The original idea of a grub-kexec never happened. These platforms need at least grub-ieee1275 to generate grub.cfg, so recommended that instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318629/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318629 Title: book3e bootloader recommendation should point to grub-ieee1275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318629] Re: book3e bootloader recommendation should point to grub-ieee1275
The ISO procedure for https://wiki.ubuntu.com/Testing/QATracker is based on Intel x86 using virtbox. It does not address ppc test cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318629 Title: book3e bootloader recommendation should point to grub-ieee1275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1324640] [NEW] vm-builder fails on creating ppc images
Public bug reported:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS
(trusty)root@jade-rev4:/etc# uname -a
Linux jade-rev4 3.13.0-24-powerpc-e500mc #46-Ubuntu SMP Thu Apr 10 19:52:34 UTC
2014 ppc ppc ppc GNU/Linux
(trusty)root@jade-
(trusty)root@jade-rev4:~# vmbuilder kvm ubuntu --suite trusty --flavour virtual
--arch ppce500 -o --libvirt qemu:///system
2014-05-29 12:26:42,551 INFO: logging to file: /tmp/tmp4PWYvg
Traceback (most recent call last):
File /usr/bin/vmbuilder, line 24, in module
cli.main()
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 142,
in main
hypervisor, distro = self.handle_args(optparser, args)
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 297,
in handle_args
distro = VMBuilder.get_distro(args[1])()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 75, in
__init__
super(Distro, self).__init__()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 31, in
__init__
self.plugins = [plugin_class(self) for plugin_class in self.plugin_classes]
File /usr/lib/python2.7/dist-packages/VMBuilder/plugins/__init__.py, line
46, in __init__
self.register_options()
File
/usr/lib/python2.7/dist-packages/VMBuilder/plugins/network/__init__.py, line
70, in register_options
domainname =
'.'.join(socket.gethostbyname_ex(socket.gethostname())[0].split('.')[1:]) or
defaultdomain
socket.gaierror: [Errno -5] No address associated with hostname
(trusty)root@jade-rev4:~# vmbuilder kvm ubuntu --suite trusty --flavour virtual
--arch ppce500 -o --libvirt qemu:///system
2014-05-29 12:27:21,211 INFO: logging to file: /tmp/tmpUKkpet
Traceback (most recent call last):
File /usr/bin/vmbuilder, line 24, in module
cli.main()
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 142,
in main
hypervisor, distro = self.handle_args(optparser, args)
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 297,
in handle_args
distro = VMBuilder.get_distro(args[1])()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 75, in
__init__
super(Distro, self).__init__()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 31, in
__init__
self.plugins = [plugin_class(self) for plugin_class in self.plugin_classes]
File /usr/lib/python2.7/dist-packages/VMBuilder/plugins/__init__.py, line
46, in __init__
self.register_options()
File
/usr/lib/python2.7/dist-packages/VMBuilder/plugins/network/__init__.py, line
70, in register_options
domainname =
'.'.join(socket.gethostbyname_ex(socket.gethostname())[0].split('.')[1:]) or
defaultdomain
socket.gaierror: [Errno -5] No address associated with hostname
(trusty)root@jade-rev4:~# cat /tmp/tmpUKkpet
2014-05-29 12:27 INFO: logging to file: /tmp/tmpUKkpet
2014-05-29 12:27 DEBUG : Loading plugins
2014-05-29 12:27 DEBUG : ['dpkg', '--print-architecture']
2014-05-29 12:27 DEBUG : powerpc
(trusty)root@jade-rev4:~# dpkg --print-architecture
powerpc
(trusty)root@jade-rev4:~# vmbuilder kvm ubuntu --suite trusty --flavour virtual
--arch ppce500 -o --libvirt qemu:///system
2014-05-29 12:28:39,097 INFO: logging to file: /tmp/tmp6Npv0z
Traceback (most recent call last):
File /usr/bin/vmbuilder, line 24, in module
cli.main()
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 142,
in main
hypervisor, distro = self.handle_args(optparser, args)
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 297,
in handle_args
distro = VMBuilder.get_distro(args[1])()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 75, in
__init__
super(Distro, self).__init__()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 31, in
__init__
self.plugins = [plugin_class(self) for plugin_class in self.plugin_classes]
File /usr/lib/python2.7/dist-packages/VMBuilder/plugins/__init__.py, line
46, in __init__
self.register_options()
File
/usr/lib/python2.7/dist-packages/VMBuilder/plugins/network/__init__.py, line
70, in register_options
domainname =
'.'.join(socket.gethostbyname_ex(socket.gethostname())[0].split('.')[1:]) or
defaultdomain
socket.gaierror: [Errno -5] No address associated with hostname
(trusty)root@jade-rev4:~# vmbuilder kvm ubuntu --suite trusty --flavour virtual
--arch ppce500
2014-05-29 12:28:56,995 INFO: logging to file: /tmp/tmpG6Puxi
Traceback (most recent call last):
File /usr/bin/vmbuilder, line 24, in module
cli.main()
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 142,
in main
hypervisor, distro = self.handle_args(optparser, args)
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 297,
in handle_args
distro = VMBuilder.get_distro(args[1])()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 75, in
__init__
super(Distro,
[Bug 1279403] Re: udlfd video driver hangs BUG: scheduling while atomic iscsi booted initrd : (trusty)
** Summary changed: - udlfd video driver hangs in iscsi booted initrd : (trusty) + udlfd video driver hangs BUG: scheduling while atomiciscsi booted initrd : (trusty) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279403 Title: udlfd video driver hangs BUG: scheduling while atomiciscsi booted initrd : (trusty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1279403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317651] Re: ppc: VM hangs on first boot after network install
The root of this is the image is missing /etc/init/ttyS0.conf This file needs added to the distro ; ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1317651 Title: ppc: VM hangs on first boot after network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1317651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1317651] Re: ppc: VM hangs on first boot after network install
It appears /etc/init/ttyS0.conf needs added to the package upstart (trusty)root@jade-rev4:/etc/init# dpkg -S tty1.conf upstart: /etc/init/tty1.conf There is no tty0.conf either. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1317651 Title: ppc: VM hangs on first boot after network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1317651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1317651] Re: ppc: VM hangs on first boot after network install
Looking more at this, it appears the device should be automatically configured: [root@ab763 init]# cat serial.conf # Automatically start a configured serial console # # How this works: # # On boot, a udev helper examines /dev/console. If a serial console is the # primary console (last console on the commandline in grub), the event # 'fedora.serial-console-available port name speed' is emitted, which # triggers this script. It waits for the runlevel to finish, ensures # the proper port is in /etc/securetty, and starts the getty. # -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1317651 Title: ppc: VM hangs on first boot after network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1317651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1279403] Re: tg3 driver hangs in iscsi booted initrd : (trusty)
** Patch added: Patch for system hang https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+attachment/4121466/+files/video.patch ** Summary changed: - tg3 driver hangs in iscsi booted initrd : (trusty) + udlfd video driver hangs in iscsi booted initrd : (trusty) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279403 Title: udlfd video driver hangs in iscsi booted initrd : (trusty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279403] Re: tg3 driver hangs in iscsi booted initrd : (trusty)
i back ported a fix from Alexander Holler: The console functions are using spinlocks while calling fb-driver ops but udlfb waits for a semaphore in many ops. This results in the BUG scheduling while atomic. One of those call flows is e.g. vt_console_print() (spinlock printing_lock) (...) dlfb_ops_imageblit() dlfb_handle_damage() dlfb_get_urb() down_timeout(semaphore) BUG: scheduling while atomic (...) vt_console_print() (release spinlock printing_lock) Fix this through a workqueue for dlfb_handle_damage(). Cc: stable at vger.kernel.org Signed-off-by: Alexander Holler holler at ahsoftware.de And it cured the hang. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279403 Title: udlfd video driver hangs in iscsi booted initrd : (trusty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317651] Re: ppc: VM hangs on first boot after network install
The root of this is the image is missing /etc/init/ttyS0.conf This file needs added to the distro ; ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317651 Title: ppc: VM hangs on first boot after network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1317651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317651] Re: ppc: VM hangs on first boot after network install
It appears /etc/init/ttyS0.conf needs added to the package upstart (trusty)root@jade-rev4:/etc/init# dpkg -S tty1.conf upstart: /etc/init/tty1.conf There is no tty0.conf either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317651 Title: ppc: VM hangs on first boot after network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1317651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317651] Re: ppc: VM hangs on first boot after network install
Looking more at this, it appears the device should be automatically configured: [root@ab763 init]# cat serial.conf # Automatically start a configured serial console # # How this works: # # On boot, a udev helper examines /dev/console. If a serial console is the # primary console (last console on the commandline in grub), the event # 'fedora.serial-console-available port name speed' is emitted, which # triggers this script. It waits for the runlevel to finish, ensures # the proper port is in /etc/securetty, and starts the getty. # -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317651 Title: ppc: VM hangs on first boot after network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1317651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317664] Re: qtemu crashes creating ppc image
I pulled the source down : wget http://archive.ubuntu.com/ubuntu/pool/universe/q/qtemu/qtemu_2.0~alpha1.orig.tar.gz Added the Qt4 core build components, ran cmake ; and the produce doesn't build: /usr/bin/cmake -E cmake_link_script CMakeFiles/qtemu.dir/link.txt --verbose=1 /usr/bin/c++ CMakeFiles/qtemu.dir/main.o CMakeFiles/qtemu.dir/mainwindow.o CMakeFiles/qtemu.dir/helpwindow.o CMakeFiles/qtemu.dir/configwindow.o CMakeFiles/qtemu.dir/machineprocess.o CMakeFiles/qtemu.dir/wizard.o CMakeFiles/qtemu.dir/machinewizard.o CMakeFiles/qtemu.dir/machinetab.o CMakeFiles/qtemu.dir/vnc/remoteview.o CMakeFiles/qtemu.dir/vnc/vncclientthread.o CMakeFiles/qtemu.dir/vnc/vncview.o CMakeFiles/qtemu.dir/machineview.o CMakeFiles/qtemu.dir/machinesplash.o CMakeFiles/qtemu.dir/machinescrollarea.o CMakeFiles/qtemu.dir/machineconfig.o CMakeFiles/qtemu.dir/machineconfigobject.o CMakeFiles/qtemu.dir/netconfig.o CMakeFiles/qtemu.dir/usbconfig.o CMakeFiles/qtemu.dir/settingstab.o CMakeFiles/qtemu.dir/qtemuenvironment.o CMakeFiles/qtemu.dir/harddiskmanager.o CMakeFiles/qtemu.dir/controlpanel.o CMakeFiles/qtemu.dir/networkpage.o CMakeFiles/qtemu.dir/usbpage.o CMakeFiles/qtemu.dir/usbmodel.o CMakeFiles/qtemu.dir/interfacemodel.o CMakeFiles/qtemu.dir/floatingtoolbar.o CMakeFil es/qtemu.dir/halobject.o CMakeFiles/qtemu.dir/guesttoolslistener.o CMakeFiles/qtemu.dir/GuestTools/modules/guestmodule.o CMakeFiles/qtemu.dir/GuestTools/modules/clipboard/clipboardsync.o CMakeFiles/qtemu.dir/moc_config.o CMakeFiles/qtemu.dir/moc_machineprocess.o CMakeFiles/qtemu.dir/moc_machinetab.o CMakeFiles/qtemu.dir/moc_wizard.o CMakeFiles/qtemu.dir/moc_machinewizard.o CMakeFiles/qtemu.dir/moc_helpwindow.o CMakeFiles/qtemu.dir/moc_configwindow.o CMakeFiles/qtemu.dir/moc_mainwindow.o CMakeFiles/qtemu.dir/vnc/moc_vncview.o CMakeFiles/qtemu.dir/vnc/moc_remoteview.o CMakeFiles/qtemu.dir/vnc/moc_vncclientthread.o CMakeFiles/qtemu.dir/moc_machineview.o CMakeFiles/qtemu.dir/moc_machinesplash.o CMakeFiles/qtemu.dir/moc_machinescrollarea.o CMakeFiles/qtemu.dir/moc_machineconfig.o CMakeFiles/qtemu.dir/moc_machineconfigobject.o CMakeFiles/qtemu.dir/moc_netconfig.o CMakeFiles/qtemu.dir/moc_usbconfig.o CMakeFiles/qtemu.dir/moc_settingstab.o CMakeFiles/qtemu.dir/moc_qtemuenvironment.o CMakeFi les/qtemu.dir/moc_harddiskmanager.o CMakeFiles/qtemu.dir/moc_controlpanel.o CMakeFiles/qtemu.dir/moc_networkpage.o CMakeFiles/qtemu.dir/moc_usbpage.o CMakeFiles/qtemu.dir/moc_usbmodel.o CMakeFiles/qtemu.dir/moc_interfacemodel.o CMakeFiles/qtemu.dir/moc_floatingtoolbar.o CMakeFiles/qtemu.dir/moc_halobject.o CMakeFiles/qtemu.dir/moc_guesttoolslistener.o CMakeFiles/qtemu.dir/GuestTools/modules/moc_guestmodule.o CMakeFiles/qtemu.dir/GuestTools/modules/clipboard/moc_clipboardsync.o CMakeFiles/qtemu.dir/qrc_qtemu.o -o qtemu -rdynamic -lQtCore -lQtGui -lQtXml -lQtSvg -lQtDBus -lQtWebKit -lQtDBus /home2/qtemu/libvncserver/libvncclient/.libs/libvncclient.so.0.0.0 -lQtWebKit /home2/qtemu/libvncserver/libvncclient/.libs/libvncclient.so.0.0.0 /usr/bin/ld: CMakeFiles/qtemu.dir/machineprocess.o: undefined reference to symbol '_ZN12QLocalSocket15connectToServerERK7QString6QFlagsIN9QIODevice12OpenModeFlagEE' //usr/lib/powerpc-linux-gnu/libQtNetwork.so.4: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[2]: *** [qtemu] Error 1 make[2]: Leaving directory `/home2/qtemu/qtemu-2.0~alpha1' make[1]: *** [CMakeFiles/qtemu.dir/all] Error 2 make[1]: Leaving directory `/home2/qtemu/qtemu-2.0~alpha1' make: *** [all] Error 2 (trusty)root@jade-rev4:/home2/qtemu/qtemu-2.0~alpha1# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317664 Title: qtemu crashes creating ppc image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtemu/+bug/1317664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279403] Re: tg3 driver hangs in iscsi booted initrd : (trusty)
Seems the video driver calling timeout in the wrong context is the root cause: [ 45.638269] Call Trace: 4[ 45.638273] [e69a38a0] [c00080bc] show_stack+0xfc/0x1c0 (unreliable) 4[ 45.638277] [e69a38f0] [c07fd050] dump_stack+0x78/0xa0 4[ 45.638285] [e69a3900] [c008eb50] dequeue_task_idle+0x40/0x60 4[ 45.638288] [e69a3910] [c07ebc7c] __schedule+0x4dc/0x780 4[ 45.638292] [e69a3a20] [c07eaf64] schedule_timeout+0x144/0x260 4[ 45.638295] [e69a3a80] [c07ee368] __down_timeout+0x78/0xc0 4[ 45.638299] [e69a3ab0] [c00a1834] down_timeout+0x74/0x80 4[ 45.638303] [e69a3ad0] [c0439f0c] dlfb_get_urb+0x2c/0xc0 4[ 45.638306] [e69a3af0] [c043b5e4] dlfb_handle_damage.isra.3+0xa4/0x1f0 4[ 45.638309] [e69a3b30] [c0419934] soft_cursor+0x1b4/0x2a0 4[ 45.638313] [e69a3b60] [c041935c] bit_cursor+0x52c/0x550 4[ 45.638316] [e69a3bf0] [c0415400] fbcon_cursor+0x130/0x1b0 4[ 45.638319] [e69a3c20] [c046f098] vt_console_print+0x248/0x4a0 4[ 45.638322] [e69a3c70] [c00a6ab0] call_console_drivers.constprop.18+0xf0/0x170 4[ 45.638325] [e69a3c90] [c00a73a4] console_unlock+0x474/0x4a0 4[ 45.638329] [e69a3cc0] [c00a76c4] vprintk_emit+0x2f4/0x500 4[ 45.638332] [e69a3d10] [c0499018] dev_vprintk_emit+0x58/0x70 4[ 45.638336] [e69a3db0] [c0499084] dev_printk_emit+0x54/0x70 4[ 45.638339] [e69a3de0] [c06db0a4] netdev_info+0x74/0x90 4[ 45.638346] [e69a3e20] [f1c6ead8] tg3_link_report+0xb8/0x170 [tg3] 4[ 45.638351] [e69a3e30] [f1c6f888] tg3_test_and_report_link_chg+0x58/0xa0 [tg3] 4[ 45.638358] [e69a3e40] [f1c79ef4] tg3_setup_phy+0xf74/0x2450 [tg3] 4[ 45.638364] [e69a3ee0] [f1c7f6b8] tg3_poll+0x398/0x430 [tg3] 4[ 45.638367] [e69a3f30] [c06d9954] net_rx_action+0x144/0x250 4[ 45.638370] [e69a3f80] [c0055758] __do_softirq+0x118/0x2b0 4[ 45.638374] [e69a3fe0] [c0055d04] irq_exit+0xb4/0xf0 4[ 45.638377] [e69a3ff0] [c000e8d0] call_do_irq+0x24/0x3c 4[ 45.638380] [c0b75e90] [c00054c8] do_IRQ+0x98/0x110 4[ 45.638383] [c0b75eb0] [c0010bfc] ret_from_except+0x0/0x18 4[ 45.638388] --- Exception: 501 at arch_cpu_idle+0x30/0x80 4[ 45.638388] LR = arch_cpu_idle+0x30/0x80 4[ 45.638392] [c0b75f70] [c00b5bd8] rcu_idle_enter+0xb8/0x100 (unreliable) 4[ 45.638395] [c0b75f80] [c00a93a0] cpu_startup_entry+0x160/0x260 4[ 45.638398] [c0b75fc0] [c0a887ec] start_kernel+0x33c/0x350 4[ 45.638401] [c0b75ff0] [c3fc] skpinv+0x2e8/0x324 1[ 45.638412] Unable to handle kernel paging request for instruction fetch 1[ 45.638413] Faulting instruction address: 0x [dumpcommon]kdb -bt Stack traceback for pid 74 0xe62b8000 742 11 R 0xe62b8340 *kworker/1:1 Call Trace: [e63978e0] [c00080bc] show_stack+0xfc/0x1c0 (unreliable) [e6397930] [c00fcb28] kdb_show_stack+0x88/0xb0 [e6397950] [c00fcc04] kdb_bt1.isra.0+0xb4/0x140 [e6397980] [c00fd010] kdb_bt+0x380/0x450 [e6397a10] [c00f9c50] kdb_parse+0x270/0x720 [e6397a60] [c00fa1d4] kdb_exec_defcmd+0xd4/0x140 [e6397a80] [c00f9c50] kdb_parse+0x270/0x720 [e6397ad0] [c00fa7b8] kdb_main_loop+0x348/0x7c0 [e6397b30] [c00fdee8] kdb_stub+0x248/0x4c0 [e6397b70] [c00f2a10] kgdb_cpu_enter+0x3c0/0x6a0 [e6397bd0] [c00f30a0] kgdb_handle_exception+0x1c0/0x220 [e6397c20] [c0011a04] kgdb_debugger+0x94/0xb0 [e6397c30] [c000bd3c] die+0x2ec/0x310 [e6397c60] [c0010a68] handle_page_fault+0x7c/0x80 --- Exception: 400 at (null) LR = ttwu_activate+0x28/0x70 [e6397d30] [c0088e70] ttwu_do_activate+0x50/0x70 [e6397d50] [c0088ff4] sched_ttwu_pending+0x84/0xb0 [e6397d70] [c0089f10] scheduler_ipi+0x60/0x190 [e6397d90] [c00126d0] smp_ipi_demux+0xa0/0xf0 [e6397db0] [c0010250] doorbell_exception+0x70/0xa0 [e6397dd0] [c0010bb0] ret_from_except_full+0x0/0x4c --- Exception: 2070 at linkwatch_event+0x0/0x50 LR = process_one_work+0x14c/0x3e0 [e6397e90] [c006fef8] process_one_work+0x128/0x3e0 (unreliable) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279403 Title: tg3 driver hangs in iscsi booted initrd : (trusty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321365] Re: virsh (ppc) fails with missing /proc/device-tree/cpu
I work with Ben; The kernel is now supported by the Ubuntu kernel group ; I am not sure how these procedures work but I would like to be able to test virsh related patches as they are made available to trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321365 Title: virsh (ppc) fails with missing /proc/device-tree/cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1321365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1317603] Re: qemu-system-ppc does not terminate on VM exit
qemu-system-ppc never terminates. Regards, John. -- o Energy-efficiency is #1 reason data centers look to expand. -- Digital Realty Trust o Green Data Centers spending to increase 300% worldwide by 2016. -- Pike Research o Data Centers have become as vital to the functioning of society as power stations. -- The Economist On Sat, May 24, 2014 at 5:35 PM, Serge Hallyn 1317...@bugs.launchpad.net wrote: What do you mean by cannot be rebooted? When you log into the guest and type reboot, nothing happens? Does init call reboot(2) and the kernel ignores it? All of userspace is properly terminated, and kernel hangs at the actual reboot? ** Also affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit Status in QEMU: New Status in “qemu” package in Ubuntu: New Bug description: When a VM is created for a p4080-e500mc ; the VM can not be rebooted or terminated. The qemu-system-ppc process must be killed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.9+ ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Thu May 8 12:20:57 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1317603] Re: qemu-system-ppc does not terminate on VM exit
It does not change the the behaviour. With or without those options the VM qemu-system-ppc session never exits. Regards, John. -- o Energy-efficiency is #1 reason data centers look to expand. -- Digital Realty Trust o Green Data Centers spending to increase 300% worldwide by 2016. -- Pike Research o Data Centers have become as vital to the functioning of society as power stations. -- The Economist On Sat, May 24, 2014 at 7:12 PM, Serge Hallyn 1317...@bugs.launchpad.net wrote: Quoting joh...@servergy.com (joh...@servergy.com): qemu-system-ppc never terminates. Assuming you are using the same scripts as in the other bugs, you are passing -no-shutdown to qemu, asking it to not exit when the guest exits. If you want qemu to exit when the guest is done, then please remove that flag, and see if that fixes it. If you are then manually killing qemu before the guest is done running, that would also explain why the guest fs is corrupted. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit Status in QEMU: New Status in “qemu” package in Ubuntu: New Bug description: When a VM is created for a p4080-e500mc ; the VM can not be rebooted or terminated. The qemu-system-ppc process must be killed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.9+ ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Thu May 8 12:20:57 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1317603] Re: qemu-system-ppc does not terminate on VM exit
qemu-system-ppc never terminates. Regards, John. -- o Energy-efficiency is #1 reason data centers look to expand. -- Digital Realty Trust o Green Data Centers spending to increase 300% worldwide by 2016. -- Pike Research o Data Centers have become as vital to the functioning of society as power stations. -- The Economist On Sat, May 24, 2014 at 5:35 PM, Serge Hallyn 1317...@bugs.launchpad.net wrote: What do you mean by cannot be rebooted? When you log into the guest and type reboot, nothing happens? Does init call reboot(2) and the kernel ignores it? All of userspace is properly terminated, and kernel hangs at the actual reboot? ** Also affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit Status in QEMU: New Status in “qemu” package in Ubuntu: New Bug description: When a VM is created for a p4080-e500mc ; the VM can not be rebooted or terminated. The qemu-system-ppc process must be killed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.9+ ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Thu May 8 12:20:57 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1317603] Re: qemu-system-ppc does not terminate on VM exit
It does not change the the behaviour. With or without those options the VM qemu-system-ppc session never exits. Regards, John. -- o Energy-efficiency is #1 reason data centers look to expand. -- Digital Realty Trust o Green Data Centers spending to increase 300% worldwide by 2016. -- Pike Research o Data Centers have become as vital to the functioning of society as power stations. -- The Economist On Sat, May 24, 2014 at 7:12 PM, Serge Hallyn 1317...@bugs.launchpad.net wrote: Quoting joh...@servergy.com (joh...@servergy.com): qemu-system-ppc never terminates. Assuming you are using the same scripts as in the other bugs, you are passing -no-shutdown to qemu, asking it to not exit when the guest exits. If you want qemu to exit when the guest is done, then please remove that flag, and see if that fixes it. If you are then manually killing qemu before the guest is done running, that would also explain why the guest fs is corrupted. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit Status in QEMU: New Status in “qemu” package in Ubuntu: New Bug description: When a VM is created for a p4080-e500mc ; the VM can not be rebooted or terminated. The qemu-system-ppc process must be killed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.9+ ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Thu May 8 12:20:57 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321365] Re: virsh (ppc) fails with missing /proc/device-tree/cpu
Does Ubuntu test virsh with ppc ? Specifically type arch='ppc' machine='ppce500'hvm/type On e500mc kernels ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321365 Title: virsh (ppc) fails with missing /proc/device-tree/cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1321365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279403] Re: tg3 driver hangs in iscsi booted initrd : (trusty)
Looking at EPC - of 0x885ac - could *p be null ?
R31 = c0b0b340 ; no
static void ttwu_activate(struct rq *rq, struct task_struct *p, int en_flags)
{
activate_task(rq, p, en_flags);
c008859c: 7f c3 f3 78 mr r3,r30
c00885a0: 7f e4 fb 78 mr r4,r31
c00885a4: 38 a0 00 05 li r5,5
c00885a8: 4b ff fb 39 bl c00880e0 activate_task
p-on_rq = 1;
/* if a worker is waking up, notify workqueue */
if (p-flags PF_WQ_WORKER)
c00885ac: 81 3f 00 0c lwz r9,12(r31)
}
[1]kdb md c0b0b340
0xc0b0b340 0100 c0b74000 0002 0020 ..@.. ..
0xc0b0b350 e62b9d00 .+..
0xc0b0b360 fffeee67 0001 ...g
0xc0b0b370 0078 0078 0078 ...x...x...x
0xc0b0b380 c0817520 0400 0040
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279403
Title:
tg3 driver hangs in iscsi booted initrd : (trusty)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] [NEW] Enabling lock checking in ppc-e500mc produces bug checks
Public bug reported: Building a 3.13.24. kernel with lock checking enabled produces Oops ; See console log for example ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu May 22 11:54:41 2014 Lsusb: Bus 002 Device 002: ID 17e9:047b DisplayLink Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 udlfb ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 nomdmonddf nomdmonisw sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago) WifiSyslog: ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] HookError_source_linux.txt
apport information ** Attachment added: HookError_source_linux.txt https://bugs.launchpad.net/bugs/1322270/+attachment/4117726/+files/HookError_source_linux.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1322270/+attachment/4117727/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1322270/+attachment/4117730/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1322270/+attachment/4117731/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1322270/+attachment/4117725/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] Re: Enabling lock checking in ppc-e500mc produces bug checks
apport information ** Tags added: apport-collected ** Description changed: Building a 3.13.0.24. kernel with lock checking enabled produces Oops ; See console log for example ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu May 22 11:54:41 2014 Lsusb: Bus 002 Device 002: ID 17e9:047b DisplayLink Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 udlfb ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 nomdmonddf nomdmonisw sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago) WifiSyslog: + --- + ApportVersion: 2.14.1-0ubuntu3 + Architecture: powerpc + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CurrentDesktop: XFCE + CurrentDmesg: + Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied + dmesg: write failed: Broken pipe + DistroRelease: Ubuntu 14.04 + Lsusb: + Bus 002 Device 002: ID 17e9:047b DisplayLink + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 udlfb + ProcKernelCmdLine: /boot/vmlinux-3.13.0-24-powerpc-e500mc root=UUID=2ac7a0ae-6bc0--82a4-2a20d352a877 ro console=ttyS0,115200 nomdmonddf nomdmonisw sgyboot=break kgdboc=ttyS0,115200 console=ttyS0,115200 fsl_fm_max_frm=9022 fsl_fman_phy_max_frm=9022 + ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 + RfKill: + + Tags: trusty + Uname: Linux 3.13.0-24-powerpc-e500mc ppc + UpgradeStatus: Upgraded to trusty on 2014-04-29 (23 days ago) + UserGroups: wireshark + WifiSyslog: + + _MarkForUpload: True ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1322270/+attachment/4117724/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1322270/+attachment/4117732/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1322270/+attachment/4117729/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1322270/+attachment/4117728/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1322270/+attachment/4117733/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1322270/+attachment/4117734/+files/UdevLog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322270] Re: Enabling lock checking in ppc-e500mc produces bug checks
[ 11.158704] usb usb2: Product: Freescale On-Chip EHCI Host Controller [ 11.158704] usb usb2: Product: Freescale On-Chip EHCI Host Controller [ 11.171577] usb usb2: Manufacturer: Linux 3.13.9+ ehci_hcd [ 11.171577] usb usb2: Manufacturer: Linux 3.13.9+ ehci_hcd [ 11.182539] usb usb2: SerialNumber: fsl-ehci.1 [ 11.182539] usb usb2: SerialNumber: fsl-ehci.1 [ 11.191762] hub 2-0:1.0: in hub_probe [ 11.191762] hub 2-0:1.0: in hub_probe [ 11.199264] hub 2-0:1.0: USB hub found [ 11.199264] hub 2-0:1.0: USB hub found [ 11.206778] hub 2-0:1.0: 1 port detected [ 11.206778] hub 2-0:1.0: 1 port detected [ 11.215272] mousedev: PS/2 mouse device common for all mice [ 11.215272] mousedev: PS/2 mouse device common for all mice [ 11.227120] device-mapper: uevent: version 1.0.3 [ 11.227120] device-mapper: uevent: version 1.0.3 [ 11.236595] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-de...@redhat.com [ 11.236595] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-de...@redhat.com [ 11.253536] ledtrig-cpu: registered to indicate activity on CPUs [ 11.253536] ledtrig-cpu: registered to indicate activity on CPUs [ 11.265788] BUG: key deadbeef not in .data! [ 11.265788] BUG: key deadbeef not in .data! [ 11.274148] DEBUG_LOCKS_WARN_ON(1)[ 11.274148] DEBUG_LOCKS_WARN_ON(1) Entering kdb (current=0xe60a8000, pid 1) Entering kdb (current=0xe60a8000, pid 1) on processor 1 on processor 1 Oops: (null) Oops: (null) due to oops @ 0xc00a650c due to oops @ 0xc00a650c dCPU: 1 PID: 1 Comm: swapper/1 Not tainted 3.13.9+ #4 dCPU: 1 PID: 1 Comm: swapper/1 Not tainted 3.13.9+ #4 dtask: e60a8000 ti: e609e000 task.ti: e609e000 dtask: e60a8000 ti: e609e000 task.ti: e609e000 NIP: c00a650c LR: c00a650c CTR: c04281e0 NIP: c00a650c LR: c00a650c CTR: c04281e0 REGS: e609fc40 TRAP: 0700 Not tainted (3.13.9+) REGS: e609fc40 TRAP: 0700 Not tainted (3.13.9+) MSR: 00029002 MSR: 00029002 CECE,EE,EE,ME,ME CR: 22ad2e82 XER: CR: 22ad2e82 XER: GPR00: GPR00: c00a650c c00a650c e609fcf0 e609fcf0 e60a8000 e60a8000 0016 0016 0001 0001 c00af694 c00af694 0001 0001 GPR08: GPR08: 22ad2e84 22ad2e84 c0002cc0 c0002cc0 GPR16: GPR16: 0100 0100 c06b1cf0 c06b1cf0 c09fc134 c09fc134 c0bd45b4 c0bd45b4 c08a6564 c08a6564 GPR24: GPR24: e6293400 e6293400 c08a6554 c08a6554 e1c77aa0 e1c77aa0 c0bd c0bd e1c77af8 e1c77af8 deadbeef deadbeef NIP [c00a650c] lockdep_init_map+0x31c/0x4a0 NIP [c00a650c] lockdep_init_map+0x31c/0x4a0 LR [c00a650c] lockdep_init_map+0x31c/0x4a0 LR [c00a650c] lockdep_init_map+0x31c/0x4a0 Call Trace: Call Trace: [e609fcf0] [c00a650c] lockdep_init_map+0x31c/0x4a0[e609fcf0] [c00a650c] lockdep_init_map+0x31c/0x4a0 (unreliable) (unreliable) [e609fd30] [c0245500] sysfs_add_file_mode_ns+0x70/0x110[e609fd30] [c0245500] sysfs_add_file_mode_ns+0x70/0x110 [e609fd60] [c02489c0] internal_create_group+0x110/0x2f0[e609fd60] [c02489c0] internal_create_group+0x110/0x2f0 [e609fda0] [c06b20e4] of_fsl_bman_probe+0x2b4/0x340[e609fda0] [c06b20e4] of_fsl_bman_probe+0x2b4/0x340 [e609fde0] [c04bb0b4] platform_drv_probe+0x34/0x80[e609fde0] [c04bb0b4] platform_drv_probe+0x34/0x80 [e609fdf0] [c04b8c8c] driver_probe_device+0xbc/0x3d0[e609fdf0] [c04b8c8c] driver_probe_device+0xbc/0x3d0 [e609fe10] [c04b90fc] __driver_attach+0xdc/0xe0[e609fe10] [c04b90fc] __driver_attach+0xdc/0xe0 more more [e609fe30] [c04b647c] bus_for_each_dev+0x7c/0xd0[e609fe30] [c04b647c] bus_for_each_dev+0x7c/0xd0 more more Only 'q' or 'Q' are processed at more prompt, input ignored Only 'q' or 'Q' are processed at more prompt, input ignored [e609fe60] [c04b7f88] bus_add_driver+0x198/0x290[e609fe60] [c04b7f88] bus_add_driver+0x198/0x290 [e609fe80] [c04b96f4] driver_register+0x94/0x150[e609fe80] [c04b96f4] driver_register+0x94/0x150 [e609fe90] [c0002528] do_one_initcall+0x128/0x1f0[e609fe90] [c0002528] do_one_initcall+0x128/0x1f0 [e609ff00] [c0acc9cc] kernel_init_freeable+0x1c4/0x260[e609ff00] [c0acc9cc] kernel_init_freeable+0x1c4/0x260 [e609ff30] [c0002ce0] kernel_init+0x20/0x140[e609ff30] [c0002ce0] kernel_init+0x20/0x140 [e609ff40] [c00106d0] ret_from_kernel_thread+0x5c/0x64[e609ff40] [c00106d0] ret_from_kernel_thread+0x5c/0x64 Instruction dump:Instruction dump: 48313515 48313515 2f83 2f83 41defd8c 41defd8c 3d20c0bd 3d20c0bd 812944a0 812944a0 2f89 2f89 40fefd7c 40fefd7c 3c60c09e 3c60c09e 3c80c0a5 3c80c0a5 38849a44 38849a44 3863b8c4 3863b8c4 48785395 48785395 0fe0 0fe0 4bfffd60 4bfffd60 93de 93de 7fc3f378 7fc3f378 [1]kdb [1]kdb tt ** Attachment added: entire console log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+attachment/4117723/+files/console-1322270.txt **
[Bug 1322270] Re: Enabling lock checking in ppc-e500mc produces bug checks
set CONFIG_DEBUG_LOCK_ALLOC =y in .config -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322270 Title: Enabling lock checking in ppc-e500mc produces bug checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279403] Re: tg3 driver hangs in iscsi booted initrd : (trusty)
I enabled kgdboc=ttyS0,115200 and caught this : [ 71.145241] input: Barcode Reader as /devices/ffe00.soc/ffe21.usb/fsl-ehci.0/usb1/1-1/1-1.3/1-1.3:1.1/input/input1 [ 71.145493] hid-generic 0003:13BA:0018.0002: input,hidraw1: USB HID v1.10 Mouse [Barcode Reader ] on usb-fsl-ehci.0-1.3/input1 [ 71.206233] md: raid6 personality registered for level 6 [ 71.206235] md: raid5 personality registered for level 5 [ 71.206236] md: raid4 personality registered for level 4 [ 71.260531] md: raid10 personality registered for level 10 [ 71.664609] udlfb: DisplayLink USB device /dev/fb0 attached. 1440x900 resolution. Using 5064K framebuffer memory [ 71.934176] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready [ 72.083988] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready [ 73.549288] tg3 :01:00.0 eth2: Link is up at 100 Mbps, full duplex Entering kdb (current=0xe62b8000, pid 74) on processor 1 Oops: (null) due to oops @ 0x0 dCPU: 1 PID: 74 Comm: kworker/1:1 Tainted: GW3.13.9+ #3 dWorkqueue: events linkwatch_event dtask: e62b8000 ti: e6396000 task.ti: e6396000 NIP: LR: c00885ac CTR: REGS: e6397ca0 TRAP: 0400 Tainted: GW (3.13.9+) MSR: 00021002 CE,ME CR: 22ad2e28 XER: GPR00: c00885ac e6397d50 e62b8000 d1826900 c0b0b340 0005 448130bc 0011 GPR08: 0011 204c2f00 c0078250 e62c7920 GPR16: d1826680 GPR24: c0b6 10d2 c0b06900 c0b06900 c0b80e18 e6396000 d1826900 c0b0b340 NIP [] (null) LR [c00885ac] ttwu_do_activate.constprop.70+0x4c/0x90 Call Trace: [e6397d50] [c00885ac] ttwu_do_activate.constprop.70+0x4c/0x90 (unreliable) [e6397d60] [c0089d80] scheduler_ipi+0xb0/0x1e0 [e6397d90] [c00126d0] smp_ipi_demux+0xa0/0xf0 [e6397db0] [c0010250] doorbell_exception+0x70/0xa0 [e6397dd0] [c0010bb0] ret_from_except_full+0x0/0x4c --- Exception: 2070 at linkwatch_event+0x0/0x50 LR = process_one_work+0x14c/0x3e0 [e6397e90] [c006fef8] process_one_work+0x128/0x3e0 (unreliable) [e6397ec0] [c00708d4] worker_thread+0x134/0x3e0 [e6397ef0] [c0078324] kthread+0xd4/0xf0 [e6397f40] [c001068c] ret_from_kernel_thread+0x5c/0x64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279403 Title: tg3 driver hangs in iscsi booted initrd : (trusty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321028] Re: qemu-system-ppc : file systems are not shutting down clean
1. ssgyboot-break has no effect in the VM kernel; It is only used by jade-initrd-2.0.bin ; kernel cmdline: [0.00] pcpu-alloc: s28800 r8192 d16256 u53248 alloc=13*4096 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pag es: 260608 [0.00] Kernel command line: (host)/boot/vmlinux-3.13.0-24-powerpc-e500mc root=/dev/vda1 ro quiet splash vt.handoff=7 2: see attached file . 3. VM's do not exit from qemu-system-ppc ; see defect : 1317603 . ** Attachment added: initrd,kern, syslog.txt https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321028/+attachment/4116985/+files/bug1321028.tgz -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1321028 Title: qemu-system-ppc : file systems are not shutting down clean To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1321028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321028] Re: qemu-system-ppc : file systems are not shutting down clean
/var/log/syslog attached as syslog.onboot when file system is dirty ; Since the VM terminated ; the device should have been umounted ; ** Attachment added: syslog.onboot https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321028/+attachment/4116987/+files/syslog.onboot -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1321028 Title: qemu-system-ppc : file systems are not shutting down clean To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1321028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321028] Re: qemu-system-ppc : file systems are not shutting down clean
I am thinking since the VM hasn't terminated due to defect 1317603 , qemu-system-ppc has to be terminated with kill pid which is not kill -9 ; I could see some inconsistencies with virtio device file not being sync'ed ; but the VM did unmount it; -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1321028 Title: qemu-system-ppc : file systems are not shutting down clean To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1321028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321028] Re: qemu-system-ppc : file systems are not shutting down clean
1. ssgyboot-break has no effect in the VM kernel; It is only used by jade-initrd-2.0.bin ; kernel cmdline: [0.00] pcpu-alloc: s28800 r8192 d16256 u53248 alloc=13*4096 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pag es: 260608 [0.00] Kernel command line: (host)/boot/vmlinux-3.13.0-24-powerpc-e500mc root=/dev/vda1 ro quiet splash vt.handoff=7 2: see attached file . 3. VM's do not exit from qemu-system-ppc ; see defect : 1317603 . ** Attachment added: initrd,kern, syslog.txt https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321028/+attachment/4116985/+files/bug1321028.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321028 Title: qemu-system-ppc : file systems are not shutting down clean To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1321028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321028] Re: qemu-system-ppc : file systems are not shutting down clean
/var/log/syslog attached as syslog.onboot when file system is dirty ; Since the VM terminated ; the device should have been umounted ; ** Attachment added: syslog.onboot https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321028/+attachment/4116987/+files/syslog.onboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321028 Title: qemu-system-ppc : file systems are not shutting down clean To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1321028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321028] Re: qemu-system-ppc : file systems are not shutting down clean
I am thinking since the VM hasn't terminated due to defect 1317603 , qemu-system-ppc has to be terminated with kill pid which is not kill -9 ; I could see some inconsistencies with virtio device file not being sync'ed ; but the VM did unmount it; -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321028 Title: qemu-system-ppc : file systems are not shutting down clean To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1321028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317987] Re: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory
** Changed in: libvirt (Ubuntu) Status: Incomplete = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317987 Title: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1317987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321362] [NEW] virsh fails to launch : missing /proc/device-tree/cpu
Public bug reported: virsh # define vm01.xml virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found With or without the controller_type pcistatement fails: (trusty)root@jade-rev4:/home2/qemu# cat *xml domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' nameUbuntu-VM01/name uuid38bbffe5-47e9-4a3b-84b1-1af5ff3f7194/uuid memory unit='KiB'1048576/memory currentMemory unit='KiB'1048576/currentMemory vcpu placement='static'1/vcpu os type arch='ppc' machine='ppce500'hvm/type kernel/home2/qemu/jade-kernel-2.0.bin/kernel initrd/home2/qemu/jade-initrd-2.0.bin/initrd cmdlineconsole=ttyS0/cmdline /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootdestroy/on_reboot on_crashdestroy/on_crash devices emulator/usr/bin/qemu-system-ppc/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/home2/qemu/jade-ubuntu-14.04.qcow2.netinstall'/ target dev='vda' bus='virtio'/ /disk controller type='usb' index='0'/ !--controller type='pci' index='0' model='pci-root'/ -- memballoon model='virtio'/ /devices qemu:commandline qemu:arg value='-no-shutdown'/ /qemu:commandline /domain virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Tue May 20 11:30:04 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (21 days ago) ** Affects: qemu (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1321362 Title: virsh fails to launch : missing /proc/device-tree/cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321362/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321362] Re: virsh fails to launch : missing /proc/device-tree/cpu
refiled under: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1321365 ** Changed in: qemu (Ubuntu) Status: New = Invalid ** Description changed: - - - virsh # define vm01.xml + virsh # define vm01.xml virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found - With or without the controller_type pcistatement fails: (trusty)root@jade-rev4:/home2/qemu# cat *xml domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' - nameUbuntu-VM01/name - uuid38bbffe5-47e9-4a3b-84b1-1af5ff3f7194/uuid - memory unit='KiB'1048576/memory - currentMemory unit='KiB'1048576/currentMemory - vcpu placement='static'1/vcpu - os - type arch='ppc' machine='ppce500'hvm/type - kernel/home2/qemu/jade-kernel-2.0.bin/kernel - initrd/home2/qemu/jade-initrd-2.0.bin/initrd - cmdlineconsole=ttyS0/cmdline - /os - clock offset='utc'/ - on_poweroffdestroy/on_poweroff - on_rebootdestroy/on_reboot - on_crashdestroy/on_crash - devices - emulator/usr/bin/qemu-system-ppc/emulator - disk type='file' device='disk' - driver name='qemu' type='raw'/ - source file='/home2/qemu/jade-ubuntu-14.04.qcow2.netinstall'/ - target dev='vda' bus='virtio'/ - /disk - controller type='usb' index='0'/ + nameUbuntu-VM01/name + uuid38bbffe5-47e9-4a3b-84b1-1af5ff3f7194/uuid + memory unit='KiB'1048576/memory + currentMemory unit='KiB'1048576/currentMemory + vcpu placement='static'1/vcpu + os + type arch='ppc' machine='ppce500'hvm/type + kernel/home2/qemu/jade-kernel-2.0.bin/kernel + initrd/home2/qemu/jade-initrd-2.0.bin/initrd + cmdlineconsole=ttyS0/cmdline + /os + clock offset='utc'/ + on_poweroffdestroy/on_poweroff + on_rebootdestroy/on_reboot + on_crashdestroy/on_crash + devices + emulator/usr/bin/qemu-system-ppc/emulator + disk type='file' device='disk' + driver name='qemu' type='raw'/ + source file='/home2/qemu/jade-ubuntu-14.04.qcow2.netinstall'/ + target dev='vda' bus='virtio'/ + /disk + controller type='usb' index='0'/ !--controller type='pci' index='0' model='pci-root'/ -- - memballoon model='virtio'/ - /devices - qemu:commandline - qemu:arg value='-no-shutdown'/ - /qemu:commandline + memballoon model='virtio'/ + /devices + qemu:commandline + qemu:arg value='-no-shutdown'/ + /qemu:commandline /domain - virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Tue May 20 11:30:04 2014 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (21 days ago) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1321362 Title: virsh fails to launch : missing /proc/device-tree/cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321362/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321365] [NEW] virsh (ppc) fails with missing /proc/device-tree/cpu
Public bug reported: virsh # define vm01.xml virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found With or without the controller_type pci statement fails: (trusty)root@jade-rev4:/home2/qemu# cat *xml domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' nameUbuntu-VM01/name uuid38bbffe5-47e9-4a3b-84b1-1af5ff3f7194/uuid memory unit='KiB'1048576/memory currentMemory unit='KiB'1048576/currentMemory vcpu placement='static'1/vcpu os type arch='ppc' machine='ppce500'hvm/type kernel/home2/qemu/jade-kernel-2.0.bin/kernel initrd/home2/qemu/jade-initrd-2.0.bin/initrd cmdlineconsole=ttyS0/cmdline /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootdestroy/on_reboot on_crashdestroy/on_crash devices emulator/usr/bin/qemu-system-ppc/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/home2/qemu/jade-ubuntu-14.04.qcow2.netinstall'/ target dev='vda' bus='virtio'/ /disk controller type='usb' index='0'/ !-- controller type='pci' index='0' model='pci-root'/ -- memballoon model='virtio'/ /devices qemu:commandline qemu:arg value='-no-shutdown'/ /qemu:commandline /domain virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvirt-bin 1.2.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Tue May 20 11:39:39 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libvirt UpgradeStatus: Upgraded to trusty on 2014-04-29 (21 days ago) modified.conffile..etc.libvirt.libvirt.conf: [modified] mtime.conffile..etc.libvirt.libvirt.conf: 2014-05-15T15:07:48.854124 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1321365 Title: virsh (ppc) fails with missing /proc/device-tree/cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1321365/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321362] [NEW] virsh fails to launch : missing /proc/device-tree/cpu
Public bug reported: virsh # define vm01.xml virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found With or without the controller_type pcistatement fails: (trusty)root@jade-rev4:/home2/qemu# cat *xml domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' nameUbuntu-VM01/name uuid38bbffe5-47e9-4a3b-84b1-1af5ff3f7194/uuid memory unit='KiB'1048576/memory currentMemory unit='KiB'1048576/currentMemory vcpu placement='static'1/vcpu os type arch='ppc' machine='ppce500'hvm/type kernel/home2/qemu/jade-kernel-2.0.bin/kernel initrd/home2/qemu/jade-initrd-2.0.bin/initrd cmdlineconsole=ttyS0/cmdline /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootdestroy/on_reboot on_crashdestroy/on_crash devices emulator/usr/bin/qemu-system-ppc/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/home2/qemu/jade-ubuntu-14.04.qcow2.netinstall'/ target dev='vda' bus='virtio'/ /disk controller type='usb' index='0'/ !--controller type='pci' index='0' model='pci-root'/ -- memballoon model='virtio'/ /devices qemu:commandline qemu:arg value='-no-shutdown'/ /qemu:commandline /domain virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Tue May 20 11:30:04 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (21 days ago) ** Affects: qemu (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321362 Title: virsh fails to launch : missing /proc/device-tree/cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321362] Re: virsh fails to launch : missing /proc/device-tree/cpu
refiled under: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1321365 ** Changed in: qemu (Ubuntu) Status: New = Invalid ** Description changed: - - - virsh # define vm01.xml + virsh # define vm01.xml virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found - With or without the controller_type pcistatement fails: (trusty)root@jade-rev4:/home2/qemu# cat *xml domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' - nameUbuntu-VM01/name - uuid38bbffe5-47e9-4a3b-84b1-1af5ff3f7194/uuid - memory unit='KiB'1048576/memory - currentMemory unit='KiB'1048576/currentMemory - vcpu placement='static'1/vcpu - os - type arch='ppc' machine='ppce500'hvm/type - kernel/home2/qemu/jade-kernel-2.0.bin/kernel - initrd/home2/qemu/jade-initrd-2.0.bin/initrd - cmdlineconsole=ttyS0/cmdline - /os - clock offset='utc'/ - on_poweroffdestroy/on_poweroff - on_rebootdestroy/on_reboot - on_crashdestroy/on_crash - devices - emulator/usr/bin/qemu-system-ppc/emulator - disk type='file' device='disk' - driver name='qemu' type='raw'/ - source file='/home2/qemu/jade-ubuntu-14.04.qcow2.netinstall'/ - target dev='vda' bus='virtio'/ - /disk - controller type='usb' index='0'/ + nameUbuntu-VM01/name + uuid38bbffe5-47e9-4a3b-84b1-1af5ff3f7194/uuid + memory unit='KiB'1048576/memory + currentMemory unit='KiB'1048576/currentMemory + vcpu placement='static'1/vcpu + os + type arch='ppc' machine='ppce500'hvm/type + kernel/home2/qemu/jade-kernel-2.0.bin/kernel + initrd/home2/qemu/jade-initrd-2.0.bin/initrd + cmdlineconsole=ttyS0/cmdline + /os + clock offset='utc'/ + on_poweroffdestroy/on_poweroff + on_rebootdestroy/on_reboot + on_crashdestroy/on_crash + devices + emulator/usr/bin/qemu-system-ppc/emulator + disk type='file' device='disk' + driver name='qemu' type='raw'/ + source file='/home2/qemu/jade-ubuntu-14.04.qcow2.netinstall'/ + target dev='vda' bus='virtio'/ + /disk + controller type='usb' index='0'/ !--controller type='pci' index='0' model='pci-root'/ -- - memballoon model='virtio'/ - /devices - qemu:commandline - qemu:arg value='-no-shutdown'/ - /qemu:commandline + memballoon model='virtio'/ + /devices + qemu:commandline + qemu:arg value='-no-shutdown'/ + /qemu:commandline /domain - virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Tue May 20 11:30:04 2014 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (21 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321362 Title: virsh fails to launch : missing /proc/device-tree/cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321365] [NEW] virsh (ppc) fails with missing /proc/device-tree/cpu
Public bug reported: virsh # define vm01.xml virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found With or without the controller_type pci statement fails: (trusty)root@jade-rev4:/home2/qemu# cat *xml domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' nameUbuntu-VM01/name uuid38bbffe5-47e9-4a3b-84b1-1af5ff3f7194/uuid memory unit='KiB'1048576/memory currentMemory unit='KiB'1048576/currentMemory vcpu placement='static'1/vcpu os type arch='ppc' machine='ppce500'hvm/type kernel/home2/qemu/jade-kernel-2.0.bin/kernel initrd/home2/qemu/jade-initrd-2.0.bin/initrd cmdlineconsole=ttyS0/cmdline /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootdestroy/on_reboot on_crashdestroy/on_crash devices emulator/usr/bin/qemu-system-ppc/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/home2/qemu/jade-ubuntu-14.04.qcow2.netinstall'/ target dev='vda' bus='virtio'/ /disk controller type='usb' index='0'/ !-- controller type='pci' index='0' model='pci-root'/ -- memballoon model='virtio'/ /devices qemu:commandline qemu:arg value='-no-shutdown'/ /qemu:commandline /domain virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvirt-bin 1.2.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Tue May 20 11:39:39 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libvirt UpgradeStatus: Upgraded to trusty on 2014-04-29 (21 days ago) modified.conffile..etc.libvirt.libvirt.conf: [modified] mtime.conffile..etc.libvirt.libvirt.conf: 2014-05-15T15:07:48.854124 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321365 Title: virsh (ppc) fails with missing /proc/device-tree/cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1321365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321365] Re: virsh (ppc) fails with missing /proc/device-tree/cpu
Related : https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1317987 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321365 Title: virsh (ppc) fails with missing /proc/device-tree/cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1321365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317987] Re: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory
Hi; I'll try your other images listed - if they are e500pc kernels (FreeScale P4080 SOC ) ; Our boot kernel is unique so far and is only used for boot IPL ; Isn't this product suppose to work as well as Intel qemu + kvm ? I appreciate your help ; but these issues are related to out of box behavior ; The PowerPC qemu ; qtemu related tools are no where near as full feature and functional as x86 ; -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317987 Title: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1317987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321028] [NEW] qemu-system-ppc : file systems are not shutting down clean
Public bug reported: Launching a VM that has been shutdown gracefully ( via init 0) typically requires fsck to run when it is started ; This indications data integrity issues; The symptom can be seen by observing the fsck running when the VM restarted. Install 14-04-LTS to a VM and the issue can be seen ; (trusty)vnc@jade-rev4:/home2/qemu$ cat vm1/go.sh mymac=52:54:00:12:34:10 T=` echo $mymac | cut -d: -f5,6 | sed s/\://` mytap=tap$T tunctl -d $mytap tunctl -t $mytap /usr/bin/qemu-system-ppc -M ppce500 -nographic -kernel jade-kernel.bin \ -initrd jade-initrd-2.0.bin -m 1G -enable-kvm \ -drive file=jade-ubuntu-14.04.raw,if=virtio \ -net nic,vlan=0,macaddr=$mymac \ -net tap,vlan=0,ifname=$mytap,script=/usr/local/bin/qemu-ifup \ -append console=ttyS0 ssgyboot=break \ -no-shutdown -no-reboot -name `basename $fp` ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Mon May 19 17:01:14 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (20 days ago) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1321028 Title: qemu-system-ppc : file systems are not shutting down clean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321028] [NEW] qemu-system-ppc : file systems are not shutting down clean
Public bug reported: Launching a VM that has been shutdown gracefully ( via init 0) typically requires fsck to run when it is started ; This indications data integrity issues; The symptom can be seen by observing the fsck running when the VM restarted. Install 14-04-LTS to a VM and the issue can be seen ; (trusty)vnc@jade-rev4:/home2/qemu$ cat vm1/go.sh mymac=52:54:00:12:34:10 T=` echo $mymac | cut -d: -f5,6 | sed s/\://` mytap=tap$T tunctl -d $mytap tunctl -t $mytap /usr/bin/qemu-system-ppc -M ppce500 -nographic -kernel jade-kernel.bin \ -initrd jade-initrd-2.0.bin -m 1G -enable-kvm \ -drive file=jade-ubuntu-14.04.raw,if=virtio \ -net nic,vlan=0,macaddr=$mymac \ -net tap,vlan=0,ifname=$mytap,script=/usr/local/bin/qemu-ifup \ -append console=ttyS0 ssgyboot=break \ -no-shutdown -no-reboot -name `basename $fp` ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Mon May 19 17:01:14 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (20 days ago) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321028 Title: qemu-system-ppc : file systems are not shutting down clean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319923] Re: Console stdin ignored using -nographic mode
It appears that running qemu in the background causes this. ** Changed in: qemu (Ubuntu) Status: New = Incomplete ** Changed in: qemu (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1319923 Title: Console stdin ignored using -nographic mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1319923/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1319923] Re: Console stdin ignored using -nographic mode
It appears that running qemu in the background causes this. ** Changed in: qemu (Ubuntu) Status: New = Incomplete ** Changed in: qemu (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319923 Title: Console stdin ignored using -nographic mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1319923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319923] [NEW] Console stdin ignored using -nographic mode
Public bug reported: (trusty)root@jade-rev4:/home2/qemu/vm2# lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 dpkg -l | grep qemu | grep ppc qemu-system-ppc 2.0.0~rc1+dfsg- 0ubuntu3.1 Launching VM's from qemu-system-ppc frequently fail to read stdin - VM is HUNG ? /usr/bin/qemu-system-ppc -M ppce500 -nographic -kernel jade-kernel.bin-new \ -initrd svy-initrd-raw.bin -m 1G -enable-kvm \ -append console=ttyS0 sgyboot=break \ -name Ubuntu-$$ When the launch sequence works , there is an interactive shell that busybox commands can be executed: -- Screen: Servergy Boot Loader. == You are now in a standard shell. svy-boot# ls bin dev init mnt root sbin tmp var boot etc lib proc run sys usr svy-boot# cat /proc/partitions major minor #blocks name 2530 41943040 vda 25318387584 vda1 2532 33553408 vda2 svy-boot# --- EOT However , other launch sequences hang , stdout messages appear , but stdin is ignored. I SUSPECT THE ISSUE IS IN QEMU and NOT THE VM because when TERMINTR key is caught (^c ) and QEMU quits: --- Screen Servergy Boot Loader. == You are now in a standard shell. svy-boot# ls -- stdin IGNORED ; ^C(trusty)root@jade-rev4:/home2/qemu/vm2# qemu: terminating on signal 2 NOTE ^^Cntr C is caught by QEMU and terminates ; ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Thu May 15 11:06:05 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (16 days ago) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1319923 Title: Console stdin ignored using -nographic mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1319923/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1317987] Re: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory
Hi I do get further with full pathnames for the kernel,initrd, and disk image; However there are issues with the xml file that was generated from the args file: (trusty)root@jade-rev4:/home2/qemu# cat go14.04.args qemu-system-ppc -M ppce500 -nographic -kernel /home2/qemu/jade-kernel-2.0.bin -initrd /home2/qemu/jade-initrd-2.0.bin -m 1024 -enable-kvm -drive file=/home2/qemu/jade-ubuntu-14.04.qcow2.netinstall,if=virtio -append console=ttyS0 -no-shutdown -no-reboot -name Ubuntu-VM01 (trusty)root@jade-rev4:/home2/qemu# virsh domxml-from-native qemu-argv go14.04.args vm01.xml (trusty)root@jade-rev4:/home2/qemu# virsh -c qemu:///system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # define vm01.xml Domain Ubuntu-VM01 defined from vm01.xml virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found virsh # exit (trusty)root@jade-rev4:/home2/qemu# ls /proc/device-tree/ #address-cells dcsr@f name aliases fsl,dpaapcie@ffe20 bman-portals@ff400 interrupt-parentpcie@ffe201000 chosen localbus@ffe124000 qman-portals@ff420 compatible memory #size-cells cpusmodel soc@ffe00 (trusty)root@jade-rev4:/home2/qemu# ls /proc/device-tree/cpus #address-cellsPowerPC,e500mc@1 PowerPC,e500mc@4 PowerPC,e500mc@7 name PowerPC,e500mc@2 PowerPC,e500mc@5 #size-cells PowerPC,e500mc@0 PowerPC,e500mc@3 PowerPC,e500mc@6 What is the root cause of the PCI config error ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317987 Title: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1317987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319923] [NEW] Console stdin ignored using -nographic mode
Public bug reported: (trusty)root@jade-rev4:/home2/qemu/vm2# lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 dpkg -l | grep qemu | grep ppc qemu-system-ppc 2.0.0~rc1+dfsg- 0ubuntu3.1 Launching VM's from qemu-system-ppc frequently fail to read stdin - VM is HUNG ? /usr/bin/qemu-system-ppc -M ppce500 -nographic -kernel jade-kernel.bin-new \ -initrd svy-initrd-raw.bin -m 1G -enable-kvm \ -append console=ttyS0 sgyboot=break \ -name Ubuntu-$$ When the launch sequence works , there is an interactive shell that busybox commands can be executed: -- Screen: Servergy Boot Loader. == You are now in a standard shell. svy-boot# ls bin dev init mnt root sbin tmp var boot etc lib proc run sys usr svy-boot# cat /proc/partitions major minor #blocks name 2530 41943040 vda 25318387584 vda1 2532 33553408 vda2 svy-boot# --- EOT However , other launch sequences hang , stdout messages appear , but stdin is ignored. I SUSPECT THE ISSUE IS IN QEMU and NOT THE VM because when TERMINTR key is caught (^c ) and QEMU quits: --- Screen Servergy Boot Loader. == You are now in a standard shell. svy-boot# ls -- stdin IGNORED ; ^C(trusty)root@jade-rev4:/home2/qemu/vm2# qemu: terminating on signal 2 NOTE ^^Cntr C is caught by QEMU and terminates ; ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Thu May 15 11:06:05 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (16 days ago) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319923 Title: Console stdin ignored using -nographic mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1319923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318629] Re: book3e bootloader recommendation should point to grub-ieee1275
Hi; How and when will this be implemented ? Will future 3.13.0-24-powerpc-e500mc installs configure grub.cfg ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318629 Title: book3e bootloader recommendation should point to grub-ieee1275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317987] Re: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory
Hi, (trusty)root@jade-rev4:/home2/qemu# dpkg -l | egrep qemu-system-pcc|openb ii netcat-openbsd 1.105-7ubuntu1 powerpc TCP/IP swiss army knife ii openbios-ppc1.1-1ubuntu1 all PowerPC Open Firmware ii openbsd-inetd 0.20091229-2ubuntu3 powerpc OpenBSD Internet Superserver (trusty)root@jade-rev4:/home2/qemu# I can run a vm manually : (trusty)root@jade-rev4:/home2/qemu# cat go3.sh exec qemu-system-ppc -M ppce500 -nographic -kernel jade-kernel.bin \ -initrd jade-initrd-2.0.bin -m 1G -enable-kvm -drive \ file=jade-ubuntu-14.04.qcow2,if=virtio -append console=ttyS0 syboot=break \ -no-shutdown -no-reboot -name Ubuntu-$$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317987 Title: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1317987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317987] Re: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory
Here you go (trusty)root@jade-rev4:/home2/qemu# dpkg -l | egrep qemu-system-ppc|openbio ii openbios-ppc1.1-1ubuntu1 all PowerPC Open Firmware ii qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 powerpc QEMU full system emulation binaries (ppc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317987 Title: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1317987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317987] [NEW] error: Cannot check QEMU binary qemu-system-ppc: No such file or directory
Public bug reported: trusty)root@jade-rev4:/home2/qemu# virsh -c qemu:///system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # define vm01.xml error: Failed to define domain from vm01.xml error: Cannot check QEMU binary qemu-system-ppc: No such file or directory (trusty)root@jade-rev4:/home2/qemu# (trusty)root@jade-rev4:/home2/qemu# (trusty)root@jade-rev4:/home2/qemu# cat vm01.xml domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' nameUbuntu-VM01/name uuid38bbffe5-47e9-4a3b-84b1-1af5ff3f7194/uuid memory unit='KiB'1048576/memory currentMemory unit='KiB'1048576/currentMemory vcpu placement='static'1/vcpu os type arch='ppc' machine='ppce500'hvm/type kerneljade-kernel-2.0.bin/kernel initrdjade-initrd-2.0.bin/initrd cmdlineconsole=ttyS0/cmdline /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootdestroy/on_reboot on_crashdestroy/on_crash devices emulatorqemu-system-ppc/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='jade-ubuntu-14.04.qcow2.netinstall'/ target dev='vda' bus='virtio'/ /disk controller type='usb' index='0'/ controller type='pci' index='0' model='pci-root'/ memballoon model='virtio'/ /devices qemu:commandline qemu:arg value='-no-shutdown'/ /qemu:commandline /domain ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvirt-bin 1.2.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc CurrentDesktop: XFCE Date: Fri May 9 12:06:14 2014 KernLog: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libvirt UpgradeStatus: Upgraded to trusty on 2014-04-29 (10 days ago) modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1317987 Title: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1317987/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1317925] [NEW] ppc-trusty base install missing grub2-common package
Public bug reported: trusty missing grub2-common package; The install process need to run update-grub ;, but the package is missing; ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc CrashDB: ubuntu CurrentDesktop: XFCE Date: Fri May 9 09:05:50 2014 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) VarLogDistupgradeApttermlog: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-term.log' VarLogDistupgradeLspcitxt: :00:00.0 PCI bridge [0604]: Freescale Semiconductor Inc P4080E [1957:0400] (rev 30) :01:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f] :01:00.1 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f] 0001:02:00.0 PCI bridge [0604]: Freescale Semiconductor Inc P4080E [1957:0400] (rev 30) 0001:03:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator] [1000:0079] (rev 05) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug dist-upgrade powerpc trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317925 Title: ppc-trusty base install missing grub2-common package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1317925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317960] [NEW] ppc: qemu launcher fails to start e500mc netinstaller VM
Public bug reported: Attempt to launch these images: http://ports.ubuntu.com/ubuntu-ports/dists/trusty/main/installer- powerpc/current/images/e500mc/netboot/ Nothing happens; ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-launcher 1.7.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc CurrentDesktop: XFCE Date: Fri May 9 10:43:44 2014 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu-launcher UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) ** Affects: qemu-launcher (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317960 Title: ppc: qemu launcher fails to start e500mc netinstaller VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-launcher/+bug/1317960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317969] [NEW] ppc - no log messages produced after selecting log feature
Public bug reported: Selecting the log feature in the GUI menu produces no logs in /tmp Try launching : http://ports.ubuntu.com/ubuntu-ports/dists/trusty/main/installer- powerpc/current/images/e500mc/netboot/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-launcher 1.7.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc CurrentDesktop: XFCE Date: Fri May 9 10:57:11 2014 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu-launcher UpgradeStatus: Upgraded to trusty on 2014-04-29 (10 days ago) ** Affects: qemu-launcher (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317969 Title: ppc - no log messages produced after selecting log feature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-launcher/+bug/1317969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317987] [NEW] error: Cannot check QEMU binary qemu-system-ppc: No such file or directory
Public bug reported: trusty)root@jade-rev4:/home2/qemu# virsh -c qemu:///system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # define vm01.xml error: Failed to define domain from vm01.xml error: Cannot check QEMU binary qemu-system-ppc: No such file or directory (trusty)root@jade-rev4:/home2/qemu# (trusty)root@jade-rev4:/home2/qemu# (trusty)root@jade-rev4:/home2/qemu# cat vm01.xml domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' nameUbuntu-VM01/name uuid38bbffe5-47e9-4a3b-84b1-1af5ff3f7194/uuid memory unit='KiB'1048576/memory currentMemory unit='KiB'1048576/currentMemory vcpu placement='static'1/vcpu os type arch='ppc' machine='ppce500'hvm/type kerneljade-kernel-2.0.bin/kernel initrdjade-initrd-2.0.bin/initrd cmdlineconsole=ttyS0/cmdline /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootdestroy/on_reboot on_crashdestroy/on_crash devices emulatorqemu-system-ppc/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='jade-ubuntu-14.04.qcow2.netinstall'/ target dev='vda' bus='virtio'/ /disk controller type='usb' index='0'/ controller type='pci' index='0' model='pci-root'/ memballoon model='virtio'/ /devices qemu:commandline qemu:arg value='-no-shutdown'/ /qemu:commandline /domain ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvirt-bin 1.2.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.0-24-powerpc-e500mc ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc CurrentDesktop: XFCE Date: Fri May 9 12:06:14 2014 KernLog: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libvirt UpgradeStatus: Upgraded to trusty on 2014-04-29 (10 days ago) modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317987 Title: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1317987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317603] [NEW] qemu-system-ppc does not terminate on VM exit
Public bug reported: When a VM is created for a p4080-e500mc ; the VM can not be rebooted or terminated. The qemu-system-ppc process must be killed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.9+ ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Thu May 8 12:20:57 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1317603/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1317651] [NEW] ppc: VM hangs on first boot after network install
Public bug reported: 1. perform a direct install to a new file by obtaining the network install components from http://ports.ubuntu.com/ubuntu-ports/dists/trusty/main/installer-powerpc/current/images/e500mc/netboot/ qemu-system-ppc -M ppce500 -nographic -kernel vmlinux \ -initrd initrd.gz -m 1G -enable-kvm -drive \ file=jade-ubuntu-14.04.qcow2.netinstall ,if=virtio -append console=ttyS0 \ -no-shutdown -no-reboot -name Ubuntu-$$ Install only the BASE and OPENSSL packages 2. boot new image : qemu-system-ppc -M ppce500 -nographic -kernel jade-kernel-2.0.bin \ -initrd jade-initrd-2.0.bin -m 1G -enable-kvm -drive \ file=jade-ubuntu-14.04.qcow2.netinstall,if=virtio -append console=ttyS0 \ -no-shutdown -no-reboot -name Ubuntu-$$ VM hangs on boot: * Starting OpenSSH server [ OK ] * Starting ACPI daemon [ OK ] * Starting regular background program processing daemon [ OK ] * Starting deferred execution scheduler [ OK ] * Stopping save kernel messages [ OK ] * Restoring resolver state... [ OK ] * Stopping CPU interrupts balancing daemon [ OK ] * Stopping System V runlevel compatibility [ OK ] dead ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.9+ ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Thu May 8 15:10:10 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1317651 Title: ppc: VM hangs on first boot after network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1317651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1317603] [NEW] qemu-system-ppc does not terminate on VM exit
Public bug reported: When a VM is created for a p4080-e500mc ; the VM can not be rebooted or terminated. The qemu-system-ppc process must be killed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.9+ ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Thu May 8 12:20:57 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317603 Title: qemu-system-ppc does not terminate on VM exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1317603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317651] [NEW] ppc: VM hangs on first boot after network install
Public bug reported: 1. perform a direct install to a new file by obtaining the network install components from http://ports.ubuntu.com/ubuntu-ports/dists/trusty/main/installer-powerpc/current/images/e500mc/netboot/ qemu-system-ppc -M ppce500 -nographic -kernel vmlinux \ -initrd initrd.gz -m 1G -enable-kvm -drive \ file=jade-ubuntu-14.04.qcow2.netinstall ,if=virtio -append console=ttyS0 \ -no-shutdown -no-reboot -name Ubuntu-$$ Install only the BASE and OPENSSL packages 2. boot new image : qemu-system-ppc -M ppce500 -nographic -kernel jade-kernel-2.0.bin \ -initrd jade-initrd-2.0.bin -m 1G -enable-kvm -drive \ file=jade-ubuntu-14.04.qcow2.netinstall,if=virtio -append console=ttyS0 \ -no-shutdown -no-reboot -name Ubuntu-$$ VM hangs on boot: * Starting OpenSSH server [ OK ] * Starting ACPI daemon [ OK ] * Starting regular background program processing daemon [ OK ] * Starting deferred execution scheduler [ OK ] * Stopping save kernel messages [ OK ] * Restoring resolver state... [ OK ] * Stopping CPU interrupts balancing daemon [ OK ] * Stopping System V runlevel compatibility [ OK ] dead ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.9+ ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Thu May 8 15:10:10 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317651 Title: ppc: VM hangs on first boot after network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1317651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317664] Re: qtemu crashes creating ppc image
** Attachment added: shot 2 https://bugs.launchpad.net/ubuntu/+source/qtemu/+bug/1317664/+attachment/4108311/+files/Screenshot%20-%2005082014%20-%2004%EF%80%BA01%EF%80%BA55%20PM.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317664 Title: qtemu crashes creating ppc image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtemu/+bug/1317664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317664] [NEW] qtemu crashes creating ppc image
Public bug reported: qtemu tried to send a report; I don;t know if it worked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qtemu 2.0~alpha1-1ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9 Uname: Linux 3.13.9+ ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Thu May 8 15:55:04 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qtemu UpgradeStatus: Upgraded to trusty on 2014-04-29 (9 days ago) ** Affects: qtemu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc trusty ** Attachment added: screen shots https://bugs.launchpad.net/bugs/1317664/+attachment/4108309/+files/Screenshot%20-%2005082014%20-%2003%EF%80%BA59%EF%80%BA31%20PM.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317664 Title: qtemu crashes creating ppc image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtemu/+bug/1317664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279403] Re: tg3 driver hangs in iscsi booted initrd : (saucy)
retested with Trusty kernel 3-13-0-24 by doing a direct install to a iSCSI target; Stiil hangs ; -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279403 Title: tg3 driver hangs in iscsi booted initrd : (saucy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279403] Re: tg3 driver hangs in iscsi booted initrd : (trusty)
** Summary changed: - tg3 driver hangs in iscsi booted initrd : (saucy) + tg3 driver hangs in iscsi booted initrd : (trusty) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279403 Title: tg3 driver hangs in iscsi booted initrd : (trusty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1313911] Re: Please add debconf option to disable os_prober
Why propose these complicate solutions to a simple request ?
fix grub-mkconfig to discover images only on mounted file systems
without making any system modification using chmod or editting files.
Regards,
John.
--
o Energy-efficiency is #1 reason data centers look to expand. --
Digital Realty Trust
o Green Data Centers spending to increase 300% worldwide by 2016. --
Pike Research
o Data Centers have become as vital to the functioni
ng of society as power stations. -- The Economist
On Tue, Apr 29, 2014 at 4:53 AM, Colin Watson cjwat...@canonical.com wrote:
grub2's debconf setup is already excessively cumbersome, and I'd rather
not add to it; but you can put GRUB_DISABLE_OS_PROBER=true in
/etc/default/grub, as documented in info grub.
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1313911
Title:
Please add debconf option to disable os_prober
Status in “grub2” package in Ubuntu:
Triaged
Bug description:
grub-mkconfig looks at all disks in the system and generates a huge
grub.cfg file;
It searches unmounted disks and adds everything with a /grub directory
to grub.cfg ;
By default - it should only search the current /boot partition, or
alternately add an option
that searches all mounted FS ;
IT SHOULD NOT BROWSE ALL RAW DISKS - EVEN THOSE THAT ARE NOT MOUNTED.
dpkg -l | grep grub-comm
ii grub-common2.02~beta2-9
powerpc GRand Unified Bootloader (common file)
grub file with contents of umounted disks:
( only /dev/sda was mounted )
-
(trusty)root@(none):~# cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ ${next_entry} ] ; then
set default=${next_entry}
set next_entry=
save_env next_entry
set boot_once=true
else
set default=5
fi
if [ x${feature_menuentry_id} = xy ]; then
menuentry_id_option=--id
else
menuentry_id_option=
fi
export menuentry_id_option
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env
recordfail; fi; fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd3,msdos3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint-ieee1275='ieee1275//sas/disk@20300,msdos3' --hint-bios=hd3,msdos3
--hint-efi=hd3,msdos3 --hint-baremetal=ahci3,msdos3
95af99e7-e863-4417-b594-e5debfabb9ee
else
search --no-floppy --fs-uuid --set=root
95af99e7-e863-4417-b594-e5debfabb9ee
fi
font=/usr/share/grub/unicode.pf2
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ ${recordfail} = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload=${1}
if [ ${1} = keep ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
}
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set
[Bug 1313888] Re: ppc : Trusty ISO install fails booted from CD
It appears the root cause is the CD is not being detected in Linux - /dev/sr0 - that is attached to a USB , is missing when the Install process starts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313888 Title: ppc : Trusty ISO install fails booted from CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1313888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313911] [NEW] grub-mkconfig finds all /grub directories on umounted disks
Public bug reported:
grub-mkconfig looks at all disks in the system and generates a huge grub.cfg
file;
It searches unmounted disks and adds everything with a /grub directory
to grub.cfg ;
By default - it should only search the current /boot partition, or alternately
add an option
that searches all mounted FS ;
IT SHOULD NOT BROWSE ALL RAW DISKS - EVEN THOSE THAT ARE NOT MOUNTED.
dpkg -l | grep grub-comm
ii grub-common2.02~beta2-9
powerpc GRand Unified Bootloader (common file)
grub file with contents of umounted disks:
( only /dev/sda was mounted )
-
(trusty)root@(none):~# cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ ${next_entry} ] ; then
set default=${next_entry}
set next_entry=
save_env next_entry
set boot_once=true
else
set default=5
fi
if [ x${feature_menuentry_id} = xy ]; then
menuentry_id_option=--id
else
menuentry_id_option=
fi
export menuentry_id_option
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env
recordfail; fi; fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd3,msdos3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint-ieee1275='ieee1275//sas/disk@20300,msdos3' --hint-bios=hd3,msdos3
--hint-efi=hd3,msdos3 --hint-baremetal=ahci3,msdos3
95af99e7-e863-4417-b594-e5debfabb9ee
else
search --no-floppy --fs-uuid --set=root 95af99e7-e863-4417-b594-e5debfabb9ee
fi
font=/usr/share/grub/unicode.pf2
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ ${recordfail} = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload=${1}
if [ ${1} = keep ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
}
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-95af99e7-e863-4417-b594-e5debfabb9ee' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd3,msdos3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint-ieee1275='ieee1275//sas/disk@20300,msdos3' --hint-bios=hd3,msdos3
--hint-efi=hd3,msdos3 --hint-baremetal=ahci3,msdos3
95af99e7-e863-4417-b594-e5debfabb9ee
else
search --no-floppy --fs-uuid --set=root
95af99e7-e863-4417-b594-e5debfabb9ee
fi
linux /boot/vmlinux-3.13.9+
root=UUID=95af99e7-e863-4417-b594-e5debfabb9ee ro console=ttyS0,115200
nomdmonddf nomdmonisw
initrd /boot/initrd.img-3.13.9+
}
submenu 'Advanced options for Ubuntu' $menuentry_id_option
'gnulinux-advanced-95af99e7-e863-4417-b594-e5debfabb9ee' {
menuentry 'Ubuntu, with Linux 3.13.9+' --class ubuntu --class gnu-linux
--class gnu --class os $menuentry_id_option
'gnulinux-3.13.9+-advanced-95af99e7-e863-4417-b594-e5debfabb9ee' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
[Bug 1313911] Re: grub-mkconfig finds all /grub directories on umounted disks
Hi ; I shouldn't have to modify a file to stop unwanted behavior ; I am requesting an option be added to the cli; ** Changed in: grub-installer (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313911 Title: grub-mkconfig finds all /grub directories on umounted disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1313911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1313911] Re: grub-mkconfig finds all /grub directories on umounted disks
chmod +ax may be a handy debug tool; not acceptable for deployments ;
there needs to be a runtime cli option.
Regards,
John.
--
o Energy-efficiency is #1 reason data centers look to expand. --
Digital Realty Trust
o Green Data Centers spending to increase 300% worldwide by 2016. --
Pike Research
o Data Centers have become as vital to the functioni
ng of society as power stations. -- The Economist
On Mon, Apr 28, 2014 at 6:02 PM, Phillip Susi ps...@ubuntu.com wrote:
That is exactly what os_prober is supposed to do since usually the other
OS(es) is(are) not mounted. If you don't want os_prober to detect other
operating systems, then you can disable it with chmod a-x /etc/grub.d
/30_os-prober.
** Changed in: grub-installer (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1313911
Title:
grub-mkconfig finds all /grub directories on umounted disks
Status in grub-installer package in Ubuntu:
Invalid
Bug description:
grub-mkconfig looks at all disks in the system and generates a huge
grub.cfg file;
It searches unmounted disks and adds everything with a /grub directory
to grub.cfg ;
By default - it should only search the current /boot partition, or
alternately add an option
that searches all mounted FS ;
IT SHOULD NOT BROWSE ALL RAW DISKS - EVEN THOSE THAT ARE NOT MOUNTED.
dpkg -l | grep grub-comm
ii grub-common2.02~beta2-9
powerpc GRand Unified Bootloader (common file)
grub file with contents of umounted disks:
( only /dev/sda was mounted )
-
(trusty)root@(none):~# cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ ${next_entry} ] ; then
set default=${next_entry}
set next_entry=
save_env next_entry
set boot_once=true
else
set default=5
fi
if [ x${feature_menuentry_id} = xy ]; then
menuentry_id_option=--id
else
menuentry_id_option=
fi
export menuentry_id_option
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env
recordfail; fi; fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd3,msdos3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint-ieee1275='ieee1275//sas/disk@20300,msdos3' --hint-bios=hd3,msdos3
--hint-efi=hd3,msdos3 --hint-baremetal=ahci3,msdos3
95af99e7-e863-4417-b594-e5debfabb9ee
else
search --no-floppy --fs-uuid --set=root
95af99e7-e863-4417-b594-e5debfabb9ee
fi
font=/usr/share/grub/unicode.pf2
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ ${recordfail} = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload=${1}
if [ ${1} = keep ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
}
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set
[Bug 1313888] [NEW] ppc : Trusty ISO install fails booted from CD
Public bug reported: The ppc 14.04 CD boots ok and the install process starts ; but it eventually fails during setup phase complaining it's can't find the CD; Saucy ppc ISO boots and installs a p4080 cts-1000 base system ok , but requires additional post install steps ( adding grub and installing e500mc kernel deb package) ; Description:Ubuntu 14.04 LTS Release:14.04 (saucy)root@jade-jpd://media/cdrom# more README.diskdefines #define DISKNAME Ubuntu-Server 14.04 LTS Trusty Tahr - Release powerpc #define TYPE binary #define TYPEbinary 1 #define ARCH powerpc #define ARCHpowerpc 1 #define DISKNUM 1 #define DISKNUM1 1 #define TOTALNUM 0 #define TOTALNUM0 1 ** Affects: linux-ppc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313888 Title: ppc : Trusty ISO install fails booted from CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1313888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313896] [NEW] edac start-up fails for ppc ; missing p4080 config info
Public bug reported: Missing command in piped open at /usr/sbin/edac-ctl line 173. failed to run : Broken pipe * failure with exit code 32 * Loading DIMM labels for Memory Error Detection and Correction edac[fail] poking around: (trusty)root@(none):~# /usr/sbin/edac-ctl --status edac-ctl: drivers are loaded. (trusty)root@(none):~# /usr/sbin/edac-ctl --print-labels Missing command in piped open at /usr/sbin/edac-ctl line 173. failed to run : Broken pipe (trusty)root@(none):~# see man edac-ctl and man edac-util ; missing from cts-1000 config : /etc/edac/mainboard /sys/class/dmi/id/board_vendor /sys/class/dmi/id/board_name We likely need to add some product specific configuration or setup instructions if we want to use this tool ; (trusty)root@jade-rev4:~# lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 ' (trusty)root@jade-rev4:~# dpkg -l | grep e500 iU linux-headers-3.13.0-24-powerpc-e500mc 3.13.0-24.46 powerpc Linux kernel headers for version 3.13.0 on 32-bit Freescale Power e500mc ii linux-image-3.13.0-24-powerpc-e500mc 3.13.0-24.46 powerpc Linux kernel image for version 3.13.0 on 32-bit Freescale Power e500mc ii linux-image-powerpc-e500mc 3.13.0.24.28 powerpc Linux kernel image on Freescale Power e500mc. iU linux-tools-3.13.0-24-powerpc-e500mc 3.13.0-24.46 powerpc Linux kernel version specific tools for version 3.13.0-24 ** Affects: edac-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313896 Title: edac start-up fails for ppc ; missing p4080 config info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edac-utils/+bug/1313896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304045] [NEW] rpciod: page alloc error no
Public bug reported: (saucy)root@jade-rev4:/home2/usbkey# [21841.439960] kworker/4:1: page allocation failure: order:0, mode:0x204000 [21841.446658] CPU: 4 PID: 77 Comm: kworker/4:1 Tainted: GF 3.11.0-5-powerpc-e500mc #8-Ubuntu [21841.455917] Workqueue: rpciod rpc_async_schedule [sunrpc] [21841.461307] Call Trace: [21841.463749] [ea427bb0] [c00080fc] show_stack+0xfc/0x1c0 (unreliable) [21841.470100] [ea427c00] [c080ae6c] dump_stack+0x78/0xa0 [21841.475233] [ea427c10] [c01651cc] warn_alloc_failed+0xfc/0x160 [21841.481059] [ea427c70] [c01686c8] __alloc_pages_nodemask+0x678/0x880 [21841.487407] [ea427d50] [c01af2b0] new_slab+0x290/0x2a0 [21841.492538] [ea427d70] [c01b1070] __slab_alloc.constprop.64+0x3f0/0x500 [21841.499143] [ea427df0] [c01b135c] __kmalloc+0x1dc/0x230 [21841.504371] [ea427e10] [fa514cd8] rpc_malloc+0x48/0xa0 [sunrpc] [21841.510290] [ea427e20] [fa50b278] call_allocate+0xe8/0x160 [sunrpc] [21841.516556] [ea427e30] [fa5156c4] __rpc_execute+0x94/0x3b0 [sunrpc] [21841.522823] [ea427e80] [fa515a0c] rpc_async_schedule+0x2c/0x50 [sunrpc] [21841.529431] [ea427e90] [c007f8e0] process_one_work+0x150/0x3f0 [21841.535255] [ea427ec0] [c00802b4] worker_thread+0x134/0x3e0 [21841.540821] [ea427ef0] [c0088084] kthread+0xb4/0xc0 [21841.545692] [ea427f40] [c001073c] ret_from_kernel_thread+0x5c/0x64 [21841.551861] Mem-Info: [21841.554123] DMA per-cpu: [21841.556646] CPU0: hi: 90, btch: 15 usd: 78 [21841.561426] CPU1: hi: 90, btch: 15 usd: 2 [21841.566205] CPU2: hi: 90, btch: 15 usd: 79 [21841.570985] CPU3: hi: 90, btch: 15 usd: 67 [21841.575764] CPU4: hi: 90, btch: 15 usd: 14 [21841.580543] CPU5: hi: 90, btch: 15 usd: 0 [21841.585323] CPU6: hi: 90, btch: 15 usd: 55 [21841.590102] CPU7: hi: 90, btch: 15 usd: 75 [21841.594881] HighMem per-cpu: [21841.597751] CPU0: hi: 186, btch: 31 usd: 0 [21841.602530] CPU1: hi: 186, btch: 31 usd: 180 [21841.607309] CPU2: hi: 186, btch: 31 usd: 0 [21841.612089] CPU3: hi: 186, btch: 31 usd: 0 [21841.616868] CPU4: hi: 186, btch: 31 usd: 0 [21841.621648] CPU5: hi: 186, btch: 31 usd: 0 [21841.626427] CPU6: hi: 186, btch: 31 usd: 0 [21841.631206] CPU7: hi: 186, btch: 31 usd: 169 [21841.635991] active_anon:20771 inactive_anon:21077 isolated_anon:0 [21841.635991] active_file:452533 inactive_file:476704 isolated_file:6 [21841.635991] unevictable:0 dirty:0 writeback:0 unstable:0 [21841.635991] free:7239714 slab_reclaimable:38857 slab_unreclaimable:9994 [21841.635991] mapped:16084 shmem:336 pagetables:1476 bounce:0 [21841.635991] free_cma:0 [21841.668561] DMA free:27984kB min:2252kB low:2812kB high:3376kB active_anon:0kB inactive_anon:0kB active_file:33552kB inactive_file:33484kB unevictable:0kB isolated(anon):0kB isolated(file):24kB present:786432kB managed:317684kB mlocked:0kB dirty:0kB writeback:0kB mapped:8kB shmem:0kB slab_reclaimable:155428kB slab_unreclaimable:36288kB kernel_stack:2384kB pagetables:5904kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [21841.709623] lowmem_reserve[]: 0 0 32000 32000 [21841.713988] HighMem free:28934512kB min:512kB low:58676kB high:116840kB active_anon:83084kB inactive_anon:84308kB active_file:1776580kB inactive_file:1873332kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768000kB managed:32768000kB mlocked:0kB dirty:0kB writeback:0kB mapped:64328kB shmem:1344kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [21841.756438] lowmem_reserve[]: 0 0 0 0 [21841.760099] DMA: 1338*4kB (UEM) 448*8kB (UEM) 213*16kB (UEM) 160*32kB (UEM) 61*64kB (UEM) 14*128kB (UEM) 9*256kB (UEM) 0*512kB 0*1024kB 0*2048kB 1*4096kB (R) = 29560kB [21841.775088] HighMem: 515*4kB (UM) 1221*8kB (UM) 95*16kB (UM) 61*32kB (UM) 43*64kB (UM) 18*128kB (UM) 12*256kB (UM) 7*512kB (M) 5*1024kB (M) 5*2048kB (UM) 7054*4096kB (UMR) = 28935556kB [21841.791561] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=4096kB [21841.799986] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=16384kB [21841.808499] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=65536kB [21841.817011] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=262144kB [21841.825610] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB [21841.834295] 929384 total pagecache pages [21841.838207] 0 pages in swap cache [21841.841510] Swap cache stats: add 0, delete 0, find 0/0 [21841.846722] Free swap = 33553404kB [21841.850199] Total swap = 33553404kB [21841.853677] __slab_alloc: 144 callbacks suppressed [21841.858456] SLUB: Unable to allocate memory on node -1 (gfp=0x0) [21841.864452] cache: kmalloc-4096, object size: 4096, buffer size: 4096, default order: 3,
[Bug 1297452] [NEW] dirty root FS should be forced clean if they are dirty
Public bug reported: It is poor practice not to force clean a dirty root FS (ext4 type) on boot if the system has gone down hard; The root FS comes up mounted read only and one has to manually reboot to recovery mode and force fsck through a command line. For Server class machines the user invention increases down time. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=13.10 DISTRIB_CODENAME=saucy DISTRIB_DESCRIPTION=Ubuntu 13.10 NAME=Ubuntu VERSION=13.10, Saucy Salamander ID=ubuntu ID_LIKE=debian PRETTY_NAME=Ubuntu 13.10 VERSION_ID=13.10 HOME_URL=http://www.ubuntu.com/; SUPPORT_URL=http://help.ubuntu.com/; BUG_REPORT_URL=http://bugs.launchpad.net/ubuntu/; # uname -a Linux -jpd 3.11.0-6-powerpc-e500mc #9-Ubuntu SMP Fri Feb 28 04:08:05 UTC 2014 ppc ppc ppc GNU/Linux ** Affects: linux-ppc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297452 Title: dirty root FS should be forced clean if they are dirty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1297452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1282201] Re: SysRQ over serial console redirects to syslog
I know it's not a bug per say . On Sat, Mar 8, 2014 at 8:21 AM, Ben Collins benmcollin...@gmail.com wrote: John, This isn't a bug. You are normally booted in Linux with the quiet flag passed to the kernel command line. You won't see output like this unless you either boot without that flag, or run a command such as dmesg --console-on or twiddle some bits in /proc/sys/kernel/printk. This is normal behavior. ** Changed in: linux-ppc (Ubuntu) Status: New = Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1282201 Title: SysRQ over serial console redirects to syslog Status in linux-ppc package in Ubuntu: Invalid Bug description: VERSION=13.10, Saucy Salamander ID=ubuntu ID_LIKE=debian PRETTY_NAME=Ubuntu 13.10 VERSION_ID=13.10 vmlinux-3.11.0-5-powerpc-e500mc When SysRQ is enabled through /proc : echo 1 /proc/sys/kernel/sysrq All responses from SysRQ sequences are redirected to /var/log/syslog , not the serial console. For instance: SySRQ ( break ) l Is suppose to report CPU stack traces . The summary is sent to v/var/log/syslog , not the serial port, which defeats the entire purpose of SysRQ feature which is intended for diagnostics of server issues. The logging behavior can redirected to the console by using : dmesg --console-on This should be the default behavior for ppc ; It is also how x86 has worked in the past. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1282201/+subscriptions -- *Regards,* * John.* *--* *o* Energy-efficiency is #1 reason data centers look to expand. -- Digital Realty Trust *o* Green Data Centers spending to increase 300% worldwide by 2016. -- Pike Research *o *Data Centers have become as vital to the functioni ng of society as power stations. -- The Economist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282201 Title: SysRQ over serial console redirects to syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1282201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282201] [NEW] SysRQ over serial console redirects to syslog
Public bug reported: VERSION=13.10, Saucy Salamander ID=ubuntu ID_LIKE=debian PRETTY_NAME=Ubuntu 13.10 VERSION_ID=13.10 vmlinux-3.11.0-5-powerpc-e500mc When SysRQ is enabled through /proc : echo 1 /proc/sys/kernel/sysrq All responses from SysRQ sequences are redirected to /var/log/syslog , not the serial console. For instance: SySRQ ( break ) l Is suppose to report CPU stack traces . The summary is sent to v/var/log/syslog , not the serial port, which defeats the entire purpose of SysRQ feature which is intended for diagnostics of server issues. The logging behavior can redirected to the console by using : dmesg --console-on This should be the default behavior for ppc ; It is also how x86 has worked in the past. ** Affects: linux-ppc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282201 Title: SysRQ over serial console redirects to syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1282201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279403] [NEW] tg3 driver hangs in iscsi booted initrd : (saucy)
Public bug reported: Testing saucy iscsi target booted on e500mc default initrd hangs when tg3 driver started. saucy was installed to an iSCSI target using the interactive setup from: http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/vmlinux http://ports.ubuntu.com/dists/saucy/main/installer-powerpc/current/images/e500mc/netboot/initrd.gz Linux version 3.11.0-5-powerpc-e500mc initrd.img-3.11.0-5-powerpc-e500mc Booted from flash USB to simulate a pxe boot. svy-boot# svy-boot# mount /dev/sda1 /mnt svy-boot# cd /mnt/iscsi2 svy-boot# ./go.sh /sbin/kexec --command='root=/dev/ram ro UUID=1cfe9f29-e188-4e00-ac47-3bf2245b117f ro break debug interface=eth4 console=tty0 console=ttyS0,115200 dhcp ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0 ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 ' --initrd=/mnt/iscsi2/initrd.img-3.11.0-5-powerpc-e500mc -l /mnt/iscsi2/vmlinux-3.11.0-5-powerpc-e500mc with break enabled I can enter cli in the initramfs - This is embedded fsl eth1 ( 1Gbe ) with a cable : (initramfs) ipconfig -t 10 -c dhcp -d eth1 (initramfs) IP-Config: eth1 hardware address 02:30:b0:00:10:01 mtu 1500 DHCP IP-Config: no response after 10 secs - giving up - System is alive ( I have a prompt ) - The above SHOULD HAVE WORKED since it is an active port. This is embedded fsl eth1 - (10Gbe) - No cable (initramfs) ipconfig -t 10 -c dhcp -d eth0 (initramfs) (initramfs) IP-Config: eth0 hardware address 02:30:b0:00:10:00 mtu 1500 DHCP IP-Config: no response after 10 secs - giving up - System is alive ( I have a prompt) tg3 stand up card in pci-e slot: (initramfs) ipconfig -t 10 -c dhcp -d eth4 (initramfs) (initramfs) [ 218.394187] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready (initramfs) (initramfs) [ 221.268533] tg3 :01:00.1 eth4: Link is up at 1000 Mbps, full duplex hung iSCSI target information: Server: CentOS 6.4 .x64 . #passwd setup # # tgtadm --lld iscsi --op new --mode account --user ronnie --password password # tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie # # dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10 tgtadm --lld iscsi --op delete --mode target --tid 1 tgtadm --lld iscsi --op new --mode target --tid 1 -T iqn.2001-04.com.jade:storage.disk0 tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b `pwd`/iscsi.disk0 tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL tgtadm --lld iscsi --op show --mode target ** Affects: linux-ppc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279403 Title: tg3 driver hangs in iscsi booted initrd : (saucy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1279403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
