On Wed, 21.05.08 23:33, Lennart Poettering (mzerqung@xxxxxxxxxxx) wrote: > > > If you trigger one of those CPU overload issues, than this is most > > > likely due to the software entering some kind of busy loop. If you > > > want to fix this, you need to find out why we enter this busy > > > loop. Apparently the operation that should normally sleep for IO > > > doesn't sleep for IO in this case. Usually this means that an IO > > > condition that was signalled earlier was not handled as it should and > > > thus not reset. Unfortunately bugs like this don't leave any useful > > > coredumps, error messages or back traces and so can only be fixed by > > > spending some time in gdb to figure out what happens. > > > > This is hard to debug indeed. :-( So I take it you have no idea where to start > > with that? > > Hmm, install debuginfo packages. Run arts on top of PA through a > profile when this happens. If done properly it gives you an idea of > the hot spots, i.e. the loops that turned into busy loops. That should read "profiler", not "profile". Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
