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
po
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 terminate
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_i
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
** 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 receiv
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)
(...
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.
http
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.
h
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 t
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++
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 cras
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
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 Cen
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:
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
** Summary changed:
- udlfd video driver hangs in iscsi booted initrd : (trusty)
+ udlfd video driver hangs " BUG: scheduling while atomic " iscsi booted
initrd : (trusty)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
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 installi
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:
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 sea
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
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 fa
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 Ubun
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 iss
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: Bu
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
e
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: Bu
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 man
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
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:
/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
I am thinking since the VM hasn't terminated due to defect 1317603 ,
qemu-system-ppc has to be terminated with killwhich 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
** 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
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: Li
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.launch
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:
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/132
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
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:
Enabli
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
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
Titl
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
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:
Enab
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:
En
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 s
[ 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: Seri
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
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
Does Ubuntu test virsh with ppc ?
Specifically hvm
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 "
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:
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 a
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 im
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 mana
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
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 ; miss
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 e5
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
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
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 n
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 /v
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 ini
** 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
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
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 init
** 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.
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: powe
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:
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
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
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 bin
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
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-0
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 recom
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 [sunr
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.
h
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 Resea
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. --
Digita
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/13
I know it's not a "bug" per say .
On Sat, Mar 8, 2014 at 8:21 AM, Ben Collins 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 comm
Public bug reported:
Multiple Oops in NFS unmount during shutdown (saucy rel )
3.11.0-5-powerpc-e500mc #8-Ubuntu
(saucy)root@(none):/work/svy/tools# * Stopping MD monitoring service mdadm
--monitor[
OK ]
* Asking all rem
Public bug reported:
I was experimenting with an iscsi boot device as root device , and
one of the preliminary steps is getting a network connection established via
the default initrd.
It appears that starting the network from init hangs the
system.
I installed Ubuntu directly to an iSCSI t
NFS Server:
Linux ab763 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64
x86_64 x86_64 GNU/Linux
--
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_remov
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
ht
Originally reportedas defect 1276298.
--
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:
h
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
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:
http
85 matches
Mail list logo
