Hi Andy - any progress on this? Although the buildd's are running older
kernels, it seems that the DEP-8 Jenkins environment is running 3.19 and
is thus causing upstart tests to fail. For example:
https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt-
upstart/ARCH=amd64,label=adt/l
LKML thread: https://lkml.org/lkml/2015/3/16/474
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1429756
Title:
FTBFS: upstart test_job_process fails in majority of cases / Kernel
retur
Running with a 3.19.0-8-generic kernel I see:
- The Upstart test_job_process test fail within a few seconds when run in a
loop looking for the errror.
- My test program in #13 also finds the bug within ~30 seconds on my test
system.
Using the kernel in #11, I have run both tests simultaneously
I've written a basic program that surfaces this bug. To recreate:
$ cd /tmp
$ tar xvf bug-1429756.tgz
$ cd bug-1429756
$ make
$ ./bug-1429756.sh
loop 1
loop 2
ERROR: got failure scenario after 2 loops (got=16, count=17,
log=/tmp/tmp.uwZHkHh0mc)
$
** Attachment added: "bug-1429756.tgz"
https
@elfy - is plymouth is still crashing for you?
$ sudo grep SEGV /var/log/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphical interfac
@arges: can you try reproducing without "quiet splash" as that seems to
be the best lead we have so far.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot
205 boots and no problem with the 2 options removed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphical interface after installation
Status
After removing both 'quiet' and 'splash' options from
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, and running 'sudo
update-grub', I am no longer able to recreate the bug (over 100 boots on
a 64-bit kvm instance using utopic-desktop-amd64.iso (20140923)).
@elfy: can you provide details on how
It's looking like either "quiet" or more likely "splash" is the
triggering factor here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphical i
I have now recreated using utopic-desktop-amd64.iso (20140923) and
http://people.canonical.com/~jhunt/upstart/conf/rebooter.conf to force
continuous reboots.
It appears that the problem only occurs if "quiet splash" is specified
since I ran 25 boots without those options and was unable to recreate
Note also that I do have PRIMARY_DEVICE_FOR_DISPLAY=1 in /var/log/udev.
Recreation is under kvm.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into g
As discussed on irc, the problem seemed to be that the plymouth-ready
event was not being emitted since udev was not tagging a graphics device
with PRIMARY_DEVICE_FOR_DISPLAY, so it looked like the problem was
udev/kernel related.
According to jibel, if he enters the grub boot menu lightdm will
re
Public bug reported:
/var/log/kern.log shows:
Aug 28 17:32:20 faire kernel: [37077.847109] EXT4-fs (sde1): warning: maximal
mount count reached, running e2fsck is recommended
Aug 28 17:32:20 faire kernel: [37077.848127] EXT4-fs (sde1): recovery complete
Aug 28 17:32:20 faire kernel: [37077.8489
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1357252
Title:
Upstart jobs specifying cgroup fail to start occasionally
Status in Ubuntu Application
** Changed in: upstart
Status: New => In Progress
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1357252
@Chris - I'm not an expert at reading kernel stack traces, but I don't
think the oops stacktrace looks related to kvm. I just mentioned that I
was using kvm when the oops occurred (*). I've edited the title
accordingly.
(*) - I know this since I have a script which warns me as soon as an
oops is g
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1351353/+attachment/4167467/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1351353
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1351353/+attachment/4167466/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1351353
Public bug reported:
My system suddently became unresponsive so I tried to SysRq s/u/b and I
think that's what caused another problem.
Either way, my system hard-locked.
Aug 1 16:15:59 faire kernel: [31778.831601] [ cut here
]
Aug 1 16:15:59 faire kernel: [31778.83164
@jsalisbury - I am only using ubuntu-packaged kernels. When I get a
chance I'll try to identify the last working kernel. However, can you
tell from the stacktrace if this is a generic kernel issue? If so, can
the kernel team recreate?
@penalvch - my bios may not be at the latest version, but we ca
Public bug reported:
Writing a 3G image to an SD card led to an oops (on both occasions I
tried it):
$ cat foo.img | sudo dd bs=16M of=/dev/mmcblk0
[36467.181234] Call Trace:
[36467.181245] [] schedule_preempt_disabled+0x29/0x70
[36467.181251] [] __mutex_lock_slowpath+0xd5/0x1d0
[36467.181278]
** Changed in: upstart
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to
Public bug reported:
[0.70] BUG: Bad page state in process modprobe pfn:0
[0.70] page:81041000 count:0 mapcount:-127 mapping: (null) index:0x0
[0.70] page flags: 0x0()
[0.70] Modules linked in:
[0.70] [<80012bb8>] (unwind_backtrace+0x0/0x11c) from [<80
Public bug reported:
The kerneloops daemon ignores WARNING-type oops's. This seems to be due
to bug 346303 (2009).
Is this behaviour still in line with our processes? I'm guessing not
since the kernel team don't seem to be aware of this silent filtering
and it means that we would miss crash repor
Works fine with trusty using 3.13.0-24-generic and 3.13.0-27-generic
(different laptop - Lenovo T410).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1326300
Title:
Logitech QuickCam 40
Note that usb camera is still plugged when oops occurs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1326300
Title:
Logitech QuickCam 4000 Pro causes kernel oops when video switched of
Public bug reported:
To reproduce:
1) Plug in Logitech QuickCam 4000 Pro via USB
2) Run 'mplayer -tv device=/dev/video1 tv://'
3) Quit mplayer
4) Run, 'dmesg|grep -q 'Call Trace:' && echo found bug'
5) Observe that 'found bug' is displayed.
[ 9477.565079] usb 2-1: new full-speed USB device numbe
Public bug reported:
An unprivileged call to lxc-attach fails with kernel 3.15.0.1.2, but
works fine using 3.13.0-24-generic.
Under 3.15.0.1.2, attempting to connect to a running unprivileged
container:
$ lxc-attach --clear-env -n trusty -- /bin/true
lxc-attach: Permission denied - Could not ope
Problem no longer occurs running kernel 3.15.0-1-generic.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1319141
Title:
Hi Joseph - in the past few days created a script to show a pop up when
I get any kernel oopses and that is what caused me to raise the bug.
However, checking my logs the earliest occurrence I have is from April
21 with same kernel version (3.13.0-24-generic):
Apr 21 18:10:09 faire kernel: [ 5637
Public bug reported:
May 13 18:22:10 faire kernel: [35947.754796] PM: Syncing filesystems ... done.
May 13 18:22:10 faire kernel: [35947.782070] PM: Preparing system for mem sleep
May 13 19:17:45 faire kernel: [35947.782396] mmc0: card b368 removed
May 13 19:17:45 faire kernel: [35947.784816] Free
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: 2.14.
** Package changed: upstart (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300144
Title:
Requested shutdown results in Reboot
Status in “linux” package in Ub
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 m
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: 2.13.3
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https
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 som
$ 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
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
Still a problem on 3.13.0-17-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
Status in “linux” package in Ubuntu:
Confirmed
Status i
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 Kernel
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/12
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
Sta
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
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
ApportV
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
http
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 Kernel
Packages, which is sub
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 Kernel
Packages, which is subscribed to linu
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
** 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
Another thought - can you confirm that this system is being booted
without any external devices being plugged into it (ie no extermal
mouse, keyboard, monitor, printer, etc)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Other things to try...
When the system "freezes":
1) Can you still toggle the caps-lock light by pressing the caps-lock key?
2) Can you reboot by holding down *all* of the following keys combos (do all of
them):
alt + sysrq + s
alt + sysrq + u
alt + sysrq + b
Also, would it be poss
@meamy: Please can you try booting again with --debug - your attachment
in #14 looks like you booted with --verbose instead?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1256949
Title:
@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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/12637
At this point, I'd suggest temporarily disabling the network-manager
upstart job (which will of course disable networking):
echo manual | sudo tee /etc/init/network-manager.override
Does this give a reliable boot? To undo this change simply delete the
override file:
sudo rm /etc/init/network-ma
Still a problem on 3.13.0-5-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
Status in “linux” package in Ubuntu:
Confirmed
Status in
Still a problem with 3.13.0-5-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268880
Title:
unable to toggle microphone mute on T410 / unable to unload
thinkpad_acpi module
S
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 Kernel
Packages, which is subscri
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269717
Title:
shutdown
Still a problem with 3.13.0-4-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268880
Title:
unable to toggle microphone mute on T410 / unable to unload
thinkpad_acpi module
S
> I haven't been able to find where in upstart this is happening, but on the
> kernel side I can tell that it's due to an open() without
> O_NOCTTY.
Upstart does not open /dev/console without O_NOCTTY afaics. Are you sure
your kernel debug is showing pid 1 is doing this?
--
You received this b
Same problem with 3.13.0-4-generic. Any progress on this? kvm is
unusable due to this issue.
** Attachment added: "dmesg-3.13.0-4-generic.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3952909/+files/dmesg-3.13.0-4-generic.txt
--
You received this bug notificat
Same problem with 3.13.0-4-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
Status in “linux” package in Ubuntu:
Confirmed
Status in
Hi Colin - thanks, I'm now running thermald but cannot really stress my
system due to o/s bug 1268906 (kvm always makes it overheat unless fans
are disengaged. That is currently not possible on my T410 btw due to bug
1268880 - will that impact thermald's abilities?
--
You received this bug notifi
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268880
Title:
unable to toggle microphone mute on T410 / unable to un
Regression seems to have been introduced in 3.13. I've tested with a few
kernels and narrowed it to:
3.13.0-1-generic: BAD
3.11.0-2-generic : OK
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Alas, same issue using kernel 3.13.0-031300rc8-generic.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu
Problem still present with 3.13.0-031300rc8-generic kernel. Note that
with that kernel I get the following message at boot time:
tpm_tis 00:09: A TPM error (6) occurred attempting to read a pcr value
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
See CurrentDmesg.txt for lots of errors such as:
[ 1688.474887] Call Trace:
[ 1688.474914] [] kvm_vcpu_ioctl+0x433/0x4d0 [kvm]
[ 1688.474924] [] ? wake_up_state+0xf/0x20
[ 1688.474931] [] ? wake_futex+0x65/0x90
[ 1688.474937] [] ? futex_wake+0x13d/0x160
[ 1688.474942] [] ? do_futex+0xeb/0x660
Public bug reported:
Ran twice - first time running kvm killed my system. The second time, I
just got lots of kernel oops messages in dmesg.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-2-generic 3.13.0-2.17
ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
U
Public bug reported:
I recently pressed the physical microphone mute button on my Lenovo
T410. However, I am now unable to unmute it. The orange light next to
the mic mute button comes on when the kernel boots, but pressing it has
no effect.
Possibly related to this, I am now unable to unload the
Thanks for reporting this issue. It sounds like a kernel issue. Also, it
looks like you are running a custom kernel?
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@meamy - ok, I am starting to suspect this is either a kernel or
graphics card issue. Adding linux to bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Hi Joseph,
Due to the headaches introduced by bug 882147 (which effectively
guarantees that tests will fail erroneously), we are changing the
Upstart tests to detect a /tmp overlayfs filesystem and display a
warning. One approach is to make use of OVERLAYFS_SUPER_MAGIC to check
/tmp. See below for
Public bug reported:
Include file /usr/include/linux/magic.h is missing the following:
#define OVERLAYFS_SUPER_MAGIC 0x794c764f
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, w
@Rebecca: yes, but the man page is referring to bugs in the reboot
command. That commands calls the reboot system call and that is where
the problem lies (in the kernel).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Hi Rebecca,
Thanks for reporting this. The screenshot shows this to be a kernel
issue, not an Upstart one. Reassigning...
** Package changed: upstart (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
** Changed in: upstart (Ubuntu)
Status: Fix Released => Incomplete
** Changed in: upstart (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
We already have bug 1203595 for having the Session Init connect to the
D-Bus session bus.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client
FWICS D-Bus is behaving as designed: since the client has not called
dbus_connection_set_wakeup_main_function(), and since D-Bus messaging is
reliable, all libdbus is able to do when a signal is sent to a
connection is cache any messages the client has not yet processed in the
hope that at some fut
TBC, using the patch on #69 results in no memory bloat.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
Valgrind log from test_nih_dbus_server.c run using 'valgrind --num-
callers=100 ...'.
** Attachment added: "vg-test_nih_dbus_server.log.gz"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878682/+files/vg-test_nih_dbus_server.log.gz
--
You received this bug notifica
I can now recreate the memory bloat using a basic NIH D-Bus server
program and associated client program.
1) Run the server as:
$ ./test_nih_dbus_server unix:abstract=/com/hunt/james/foo
com.hunt.james.Foo /com/hunt/james/Foo
2) Run the client as:
$ ./test_nih_dbus_client unix:a
** Attachment added: "test_nih_dbus_client.c"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878664/+files/test_nih_dbus_client.c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
** Attachment added: "spam_dbus_server.sh"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878665/+files/spam_dbus_server.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Hi Steve,
The trace in #59 was produced by:
- Running Upstart via valgrind which upstart linked against debug builds of nih
and dbus.
- Running a single instance of the test program (#51).
- Running spam.sh (#52).
- Waiting until init was consuming ~200MB, then sending SIGTERM to the
init/valgr
Another valgrind log taken using the same precedure as above. However,
this time I waited until the init process was consuming over 2GB of RAM.
Top showed:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
15329 james 20 0 2463m 2,0g 12m R 100,0 26,1 6:51.59 memcheck-
Just got a much more interesting valgrind run. Juicy excerpt:
==9366== 147,560 bytes in 1,190 blocks are still reachable in loss record 187
of 188
==9366==at 0x402B965: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==9366==by 0x408E730: dbus_malloc0 (dbus-memory.c:572)
==
Neither does calling the following help:
dbus_connection_flush (connection);
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in
Note that the following call on the server side does not resolve the
issue:
while (dbus_connection_dispatch (connection) == DBUS_DISPATCH_DATA_REMAINS)
;
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Run as:
$ spam.sh
** Attachment added: "spam.sh"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3872619/+files/spam.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
Program attached in #51 demonstrates the incorrect calling behaviour. To
demonstrate the correct behaviour change the #if0/else/endif such that
rather than calling dbus_connection_open(), the program calls
nih_dbus_connect().
nih_dbus_connect(): No memory growth.
dbus_connection_open(): Memory gro
C program to trigger this bug. Run it in an environment with
UPSTART_SESSION set (such as a desktop/Touch environment), then run the
about-to-be attached spam.sh script.
** Attachment added: "trigger-bug-1235649.c"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/387261
Note that disabling libIndicatorsQml.so with #44 did not resolve the
problem. However, I am confident this is because there were other
connections to the Session Init (probably resulting from libupstart-app-
launch1).
This does need to be confirmed though.
--
You received this bug notification b
This problem can now be demonstrated with a single connection to upstart
that makes the following calls:
dbus_connection_open()
nih_dbus_proxy_new ()
The problem is not seen if the app instead calls:
- nih_dbus_connect (upstart_session, disconnect_handler)
- nih_dbus_proxy_
The problem is not observed when the only connections to upstart are the
standard upstart bridges (since they use nih_dbus_connect()).
For reference, here is nih_dbus_setup() which includes one or more calls
that unity seemingly should be calling itself:
http://bazaar.launchpad.net/~ubuntu-
branc
1 - 100 of 148 matches
Mail list logo
