[Bug 850935] Re: upstart-udev-bridge at 100% CPU

*** This bug is a duplicate of bug 829980 *** https://bugs.launchpad.net/bugs/829980 Hi Steve - please could you attach your /var/log/udev to bug 829980 so I can check my fix will work in all cases. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

*** This bug is a duplicate of bug 829980 *** https://bugs.launchpad.net/bugs/829980 Since I can't reply to the private bug of which this is a duplicate... I tried the test in comment 14, there is no tmp file: steve@steve-laptop:~$ ls /etc/init/bug-850935.conf /etc/init/bug-850935.conf stev

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

*** This bug is a duplicate of bug 829980 *** https://bugs.launchpad.net/bugs/829980 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upstart (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

*** This bug is a duplicate of bug 829980 *** https://bugs.launchpad.net/bugs/829980 ** This bug has been marked a duplicate of private bug 829980 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

I'm not now convinced the kernel isn't spamming us. Can you do the following: 1) sudo stop upstart-udev-bridge 2) Plonk the attached bug-850935.conf into /etc/init/. 3) Reboot with the battery attached. bug-850935.conf will create a file /tmp/bug-850935.log with 1 line for every "power_supply-dev

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

I booted the system w/ no battery and AC power. upstart-udev-bridge was not using any CPU according to 'top'. CPU usage shot to 100% after inserting the battery. I see this in dmesg when I add the battery. I assume it's not related based on comment #10: [ 126.010934] ACPI: EC: GPE storm detected

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

I love proportional fonts. Don't you? :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850935 Title: upstart-udev-bridge at 100% CPU To manage notifications about this bug go to: https://bugs.launc

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

I wonder if the event name itself is the problem. I've never seen a udev event which contained underscores: power_supply-device-added ^ | is this normal? If this system is a laptop and you can boot it with the battery removed on ac power, that would be an int

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

I don't think it's spamming us. The code that is causing the cpu to max out I think is in upstart-udev-bridge.c: 276 pending_call = NIH_SHOULD (upstart_emit_event (upstart, 277name, env, FALSE, 278

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

Additional backtrace with more detail. Each bt I take (I've done about 10) shows that we're emitting a power_supply-device-added, is the kernel spamming us with events? (gdb) attach 318 Attaching to process 318 Reading symbols from /sbin/upstart-udev-bridge...Reading symbols from /usr/lib/debug/s

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

I don't see ddebs for libnih, but I did install upstart-dbgsym and nih- dbus-tool-dbgsym. Here's the resulting stack: Thread 1 (Thread 0x7f9d72f09720 (LWP 318)): #0 0x7f9d72172be2 in _IO_do_write () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f9d72171d95 in _IO_file_xsputn () from /lib/x

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

With -s 1024: 318 write(2, "process 318: ", 13) = 13 318 write(2, "arguments to dbus_message_iter_append_basic() were incorrect, assertion \"_dbus_check_is_valid_utf8 (*string_p)\" failed in file ../../dbus/dbus-message.c line 2534.\nThis is normally a bug in some application using the

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

Could you install the ddebs for upstart + libnih so we can get a proper stack trace? dbus_message_iter_append_basic() is called in a lot of places. I suspect that either upstart-udev-bridge (or more likely libnih-dbus*) is calling NIH_MUST() or NIH_SHOULD() which will spin forever until they get th

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

Could you add "-s 1024" to an strace as the strings are truncated in the attached log. I think we'll find the log will then show lines like this: arguments to dbus_message_iter_append_basic() were incorrect, assertion "%s" failed in file %s line %d. This is normally a bug in some applicat

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

After rebooting the system, upstart-udev-bridge is at 100% CPU on one of my cores - so this is reproducible, and not necessarily related to compiz. Let me know if there's anything I can do to help debug. The backtrace implies dbus is involved, so I tried shutting down all applications and watching

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

** Attachment added: "upstart-udev-bridge.strace" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/850935/+attachment/2407727/+files/upstart-udev-bridge.strace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.laun

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

Backtrace via GDB: steve@steve-laptop:~$ sudo gdb GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. Ther

[Bug 850935] Re: upstart-udev-bridge at 100% CPU

-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850935 Title: upstart-udev-bridge at 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/85093