*** This bug is a duplicate of bug 901038 ***
https://bugs.launchpad.net/bugs/901038
Hi Serge,
The problem I believe is that Upstart is in the process of restarting so
initctl cannot (yet) reconnect to Upstart until it has finished the re-
exec. See comment #7 on bug 901038.
** This bug has
*** This bug is a duplicate of bug 901038 ***
https://bugs.launchpad.net/bugs/901038
Hi Serge,
The problem I believe is that Upstart is in the process of restarting so
initctl cannot (yet) reconnect to Upstart until it has finished the re-
exec. See comment #7 on bug 901038.
** This bug has
Hi Huubb,
Thanks for this information. This is still very curious since according
to your /var/crash/, Upstart did seemingly crash, but on a different day
to chrome (chromium) crashing. Also, the upstart crash file seems to
have been uploaded before the crash occurred. That might be because
Hi Huubb,
Thanks again. However, please can you attach
/var/crash/_sbin_init.0.crash as it doesn't appear in 'out'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300235
Title:
init crashed with
Hi Serge,
I'm running on pure amd64 too so the problem is not arch-specific.
The simplest way to recreate:
$ kvm -cdrom /usr/lib/memtest86+/memtest86+.iso -m 512
Just hold down control+alt and frantically toggle the monitor using the
'2' and '1'. Within a couple of seconds it hangs.
--
You
This is rather odd - the attachments relate to Upstart, and yet the
corefiles on this bug and all the duplicates come from Chrome.
Examples:
/tmp/CoreDump: ELF 64-bit LSB core file x86-64, version 1 (SYSV),
SVR4-style, from '/opt/google/chrome-unstable/chrome --type=zygote
--log-level=0
Please can those affected attach a list of files in their /var/crash/
directory.
Also, can anyone reproduce this issue or was it purely a one off?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Serge,
I'm running on pure amd64 too so the problem is not arch-specific.
The simplest way to recreate:
$ kvm -cdrom /usr/lib/memtest86+/memtest86+.iso -m 512
Just hold down control+alt and frantically toggle the monitor using the
'2' and '1'. Within a couple of seconds it hangs.
--
You
Sorry - ignore that. However, problem persists on a separate fully-
updated amd64 trusty system running kvm version 2.0.0~rc1+dfsg-0ubuntu3.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: upstart
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238078
Title:
global environment table is not serialised
To manage notifications
*** This bug is a duplicate of bug 1300235 ***
https://bugs.launchpad.net/bugs/1300235
** This bug has been marked a duplicate of bug 1300235
init crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry - ignore that. However, problem persists on a separate fully-
updated amd64 trusty system running kvm version 2.0.0~rc1+dfsg-0ubuntu3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1257352
Public bug reported:
Oops caused when trying to start an lxc unprivileged container.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion:
Patch forwarded to Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306412
Title:
patch -pq throws segfault
To manage notifications about this bug go to:
Right. So to be completely clear, by calling nih_dbus_setup(), nih was
registering a libdbus handler that runs on the client side such that
whenever libdbus deemed necessary, it would attempt to wake up the
clients main loop by calling nih_main_loop_interrupt(). However, since
the client didn't
Confused as to why this bug has been raised? I have already fixed this
issue to rotate logs hourly in 1.12.1-0ubuntu2 ?? Also why 17 minutes
past the hour exactly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A fix for this issue is attached - the cleanup() function calls
forget_output_files(), even if the list that stores those files is never
created.
** Patch added: patch-bug-1306412.diff
The problem here is that applications linked to the cgmanager client
library are not calling nih_main_loop(). That's a problem because the
nih-dbus code calls nih_main_loop_interrupt() which adds a byte to the
main loop interrupt pipe. After 65536 bytes have been added to that
pipe, the next call
Right. So to be completely clear, by calling nih_dbus_setup(), nih was
registering a libdbus handler that runs on the client side such that
whenever libdbus deemed necessary, it would attempt to wake up the
clients main loop by calling nih_main_loop_interrupt(). However, since
the client didn't
@John - do you have a crash file or a state file
(/var/crash/_sbin_init.*.crash or /var/log/upstart/upstart.state)? If
so, please can you attach them to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Nick,
Thanks for reporting this issue. Yes, Upstart uses inotify so the error
shown is coming directly from the kernel. However, the error relates to
the lack of inotify watches, not the lack of disk space. What the error
you are seeing means is that Upstart will not recognise any changes to
I saw cgmanager spinning at 100% cpu earlier and just managed to strace
before my system overheated and powered off. Didn't catch the
problematic call, but the errno was EMFILE. Interesting since bug
1300663 shows the same value from upstart. I wonder if this might be a
kernel issue?
--
You
** Package changed: upstart (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300144
Title:
Requested shutdown results in Reboot
To manage notifications about this bug go
HI Serge - yes, problem is still there with the ppa versions:
$ dpkg -l|egrep kvm|qemu
ii ipxe-qemu
1.0.0+git-2013.c3d1e78-2ubuntu1 all PXE boot
firmware - ROM images for qemu
ii kvm-ipxe
HI Serge - yes, problem is still there with the ppa versions:
$ dpkg -l|egrep kvm|qemu
ii ipxe-qemu
1.0.0+git-2013.c3d1e78-2ubuntu1 all PXE boot
firmware - ROM images for qemu
ii kvm-ipxe
Public bug reported:
Occasionally seen in Virtualbox VM.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-19-generic 3.13.0-19.39
ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
Uname: Linux 3.13.0-19-generic i686
NonfreeKernelModules: nvidia
ApportVersion:
** Attachment added: virtualbox-kernel-oops.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296659/+attachment/4040675/+files/virtualbox-kernel-oops.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Simply booting a VM without 'quiet' and 'splash' shows the oops - I've
only noticed it a couple of times. Just tried 10 boots and didn't hit it
again though.
(Note that I cannot compare virtualbox's behaviour with kvm due to bug
1268906).
--
You received this bug notification because you are a
Public bug reported:
Moving a window to another workspace using the context menu options
Move to Workspace right or Move to Another Workspace causes unity to
lose track of the window entirely - it disappears never to return.
Note: the processes associated with the windows *are* still running as
** Package changed: upstart (Ubuntu) = dbus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250668
Title:
upstart session for dbus has hard coded .cache directory
To manage notifications
Actually that file lives in the dbus package:
$ dpkg -L upstart|grep dbus.conf
$ dpkg -L dbus|grep dbus.conf
/usr/share/upstart/sessions/dbus.conf
/etc/init/dbus.conf
$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
$ arch
i686
$ dpkg -l linux-generic
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
$ sudo apt-get install linux-generic:amd64 linux-headers-generic:amd64
linux-headers-3.13.0-18-generic:amd64 linux-headers-3.13.0-18
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-3.13.0-18 is already the newest version.
Some packages
Yes:
$ sudo apt-get install linux-generic:amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that
Public bug reported:
When plymouthd is running, it's /proc/$pid/cmdline shows argv[0] as
'@sbin/plymouthd'.
Running plymouthd without specifying the path sets cmdline to
'@lymouthd' so it is over-writing the first character of its argv[0].
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package:
Hi Serge,
Looking at nih's configure.ac, you actually want to use '--enable-
threading' I think. I've never used this option and tbh wasn't even
aware it was there.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Hi Serge,
Looking at nih's configure.ac, you actually want to use '--enable-
threading' I think. I've never used this option and tbh wasn't even
aware it was there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Michał,
This is how Upstart is supposed to work and it documented as such in
initctl(8) under 'restart'.
** Changed in: upstart (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: debian/tests/control: build-depend on libcap-dev since procenv
0.33 now uses that.
https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/1293674/+attachment/4028699/+files/sbuild-builddep-on-libcap-dev.patch
--
You received this bug notification because you are a member of
Public bug reported:
sbuild's dep8 control file needs to add a dependency on libcap-dev now
that procenv (build by the sbuild dep8 test) requires it.
** Affects: sbuild (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Still a problem on 3.13.0-17-generic.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
To manage notifications about this bug go to:
Still a problem on 3.13.0-17-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
To manage notifications about this bug go to:
Hi Colin - thanks, yes running thermald has improved the situation
immensely! I do still very occasionally see overheats, although they are
extremely rare now and I suspect may be more related to my fans needing
a clean :-)
--
You received this bug notification because you are a member of Ubuntu
** Changed in: upstart
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222705
Title:
init assert failure: alloc.c:633: Assertion failed in nih_unref: ref
To be clear, I am suggesting we have a notification appear when the user
manually disconnects the VPN at the point the connection is brought
down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1288667
Public bug reported:
When a VPN connection has been created, a notification appears stating:
VPN Login Message
VPN connection has been successfully established.
However, the converse is not true; disconnecting from the VPN does not
result in a message like this:
VPN Logout Message
*** This bug is a duplicate of bug 1286698 ***
https://bugs.launchpad.net/bugs/1286698
** This bug has been marked a duplicate of bug 1286698
Logout, Restart Shutdown does not work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1286698 ***
https://bugs.launchpad.net/bugs/1286698
** This bug has been marked a duplicate of bug 1286698
Logout, Restart Shutdown does not work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for reporting this bug. However, please do not report the same
bug three times :-)
** Package changed: upstart (Ubuntu) = gnome-session (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
(Long) Pressing the super (aka windows) key displays the Keyboard
Shortcuts overlay. However, this summary does not show that Super+L is
now a shortcut for locking the screen.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140303-0ubuntu1
Do you still have the status file somewhere so we can see what binary
data it contained?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284164
Title:
~/.cache/upstart grows enormous
To manage
The logrotate job is simply invoking logrotate program so it could be a
bug in logrotate? Nobody else appears to have reported this issue.
Do you have a ~/.cache/upstart/logrotate.log containing any errors? We
could simply make the job delete the status file if it exists prior to
running
Thanks for reporting this issue. A few questions:
1) Is this behaviour repeatable?
2) Are there other users logged in when you attempt to shutdown the system?
3) Can you still switch accounts from the menu?
The fact that using the shutdown/reboot commands is the only way to
shutdown your system
I suspect issue this could be rather critical for Ubuntu Studio.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261654
Title:
missing LADSPA support
To manage notifications about this bug go to:
Please can those affected attach the requested logs in comment #3 ?
** Changed in: upstart (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263140
Title:
I don't know if the padlock is actually being overlayed onto the
existing connection-type image, but I'd prefer to see an icon like the
attached. In other words, invert the 2 arrows for a wired connection and
make the right-hand arrow stem shorter, allowing space for a padlock
bottom-right.
**
Public bug reported:
The current nm-applet icon that is shown for a wired VPN connection is
very unclear - overlaying a padlock onto the existing connection-type
icon works fine for the usual wifi icon, but with a wired connection the
padlock merges into the down arrow and looks like screen
This isn't really a bug with Upstart since it appears the problem is
that bamfdaemon is spamming dbus somehow. Upstart is simply logging the
output.
That said, there is an outstanding merge proposal to have the session
logrotate job run periodically which would have avoided so much disk
space
** Package changed: bamf (Ubuntu) = dbus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284164
Title:
~/.cache/upstart grows enormous
To manage notifications about this bug go to:
Scott - agreed. However, the root cause has nothing to do with Upstart.
Yes, we can make Upstart perform more frequent rotations, but I think we
need to understand why your log is growing so fast: yours seems to be
growing at ~32MB / day, mine grows at ~100k.
Taking a slighly longer peek, it
Just noticed the tagging on this bug - please can you raise a new
upstart bug attaching upstart.state (fro /var/log/ or
~/.cache/upstart/). Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It looks like the main culprit is the web browser and/or the Google
plugins - every Google connection apears to result in a multi-line burst
of json being logged. Are you running the browser/plugins with any debug
enabled?
--
You received this bug notification because you are a member of Ubuntu
** Changed in: upstart (Ubuntu)
Assignee: James Hunt (jamesodhunt) = (unassigned)
** Changed in: upstart
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Hi Alan,
Is this reproducable? If so, a 'ps -efwww' would be useful so we can see
what is actually running initctl and what it is trying to do. Also, if
you can 'strace -o /tmp/initctl.strace -s 1024 -fFv -p pid-of-initctl'
and attach /tmp/initctl.strace to the bug that would be very useful.
**
** Changed in: upstart (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234653
Title:
upstart-dbus-bridge --system is not started on boot
To manage
Public bug reported:
$ lxc-start -n trusty
lxc_container: Permission denied - failed to get real path for
'/home/james/.local/share/lxc/trusty/rootfs'
lxc_container: failed to mount rootfs
lxc_container: failed to setup rootfs for 'trusty'
lxc_container: failed to setup the container
The problem does seem to be an LXC bug. However, I can work around it by
changing the perms on my home directory from 0750 to 0755.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1277466
Public bug reported:
$ lxc-start -n trusty
lxc_container: Permission denied - failed to get real path for
'/home/james/.local/share/lxc/trusty/rootfs'
lxc_container: failed to mount rootfs
lxc_container: failed to setup rootfs for 'trusty'
lxc_container: failed to setup the container
The problem does seem to be an LXC bug. However, I can work around it by
changing the perms on my home directory from 0750 to 0755.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1277466
Title:
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1277594
Title:
Please make --no-sessions the default, and add
I think the switch to 3.13 may have borked kvm for me. I'll try to
confirm that tomorrow...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running
Public bug reported:
.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: udisks2 2.1.2-1
ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
Uname: Linux 3.13.0-6-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
CustomUdevRuleFiles:
I think the switch to 3.13 may have borked kvm for me. I'll try to
confirm that tomorrow...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
To manage
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Importance: Undecided = Low
** Changed in: upstart
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: upstart
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275308
Title:
Correction for man page for socket-event(7)
To manage notifications about
Hi Joseph - see dmesg.txt.gz for the stack traces. I cannot recreate
this issue on demand I'm afraid and have not see it since raising this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274143
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
** Also affects: upstart
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
** Changed in: upstart
Status: New = In Progress
** Changed in: upstart
Assignee: (unassigned) = James Hunt (jamesodhunt)
** Changed in: upstart
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Can you attach ~/.xsession-errors? Is there a /var/crash/*init*.crash?
If you can recreate this running upstart with '--debug' that could also
give us something.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Issue occurred when using a WiPi USB adapter (wlan1).
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-5-generic 3.13.0-5.20
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic i686
NonfreeKernelModules: nvidia
** Attachment added: sudo lshw -c network
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274143/+attachment/3961769/+files/lsusb_-c_network.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Jérôme - thank you for reporting this issue. However, this is not a
bug in Upstart - Upstart simply records all output from the programs it
starts, so that output is entirely up to the programs being run, not
Upstart. The 2 examples you give do indeed prefix every line with their
program name,
Serge has just identified that the trigger for this bug is running kvm
with '-net user': without this option, no issues.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Latest series of oopses running on a fully updated trusty system.
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3958887/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Same problem running with -vnc :7
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/395/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
To be clear, my host system is a 64-bit capable first-gen i7, but is
actually running fully 32-bit.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup
Latest trusty desktop image (dated 24 Jan) results in the oops when
running with kvm as:
$ kvm --enable-kvm -cdrom ubuntu_trusty-desktop-i386.iso -boot d -m 1024
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Serge has just identified that the trigger for this bug is running kvm
with '-net user': without this option, no issues.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Latest series of oopses running on a fully updated trusty system.
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3958887/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
To be clear, my host system is a 64-bit capable first-gen i7, but is
actually running fully 32-bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
To
Same problem running with -vnc :7
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/395/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Latest trusty desktop image (dated 24 Jan) results in the oops when
running with kvm as:
$ kvm --enable-kvm -cdrom ubuntu_trusty-desktop-i386.iso -boot d -m 1024
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sounds like the original driver had caused the kernel to become totally
unresponsive. Glad the problem has been resolved for you.
Please could you attach the output of sudo lshw -c network to this bug
so we can see the details of your broadcom wireless card?
Thanks!
--
You received this bug
Still a problem on 3.13.0-5-generic.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
To manage notifications about this bug go to:
dmesg from 3.13.0-5-generic kernel.
** Attachment added: dmesg.3.13.0-5-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3954151/+files/dmesg.3.13.0-5-generic
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
@Serge - perfectly happy to change that, in fact...
@Stéphane - could you review and test lp:~jamesodhunt/upstart/kmsg-
noctty? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: upstart
Assignee: (unassigned) = James Hunt (jamesodhunt)
** Changed in: upstart
Status: New = Fix Committed
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu Trusty)
Status: New = Confirmed
--
You
This sounds like a kernel issue relating to your hardware.
** Package changed: upstart (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269717
Title:
shutdown now does not
Still a problem with 3.13.0-5-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268880
Title:
unable to toggle microphone mute on T410 / unable to unload
thinkpad_acpi module
To manage
Still a problem on 3.13.0-5-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
To manage notifications about this bug go to:
401 - 500 of 2008 matches
Mail list logo
