From: J S <g1p...@ya...> - 2005-03-19 16:30:55
|
Hi All, After some discussion on the #openmosix channel on irc, I found out that the behavior with the openmosix tools I described below is more likely due to a bug in the kernel patch than with a configuration issue, which I had thought previously. I was able to get a backtrace of openmosixview for more debugging information: Program received signal SIGBUS, Bus error. [Switching to Thread 16384 (LWP 2199)] 0x409c2c2f in strlen () from /lib/libc.so.6 (gdb) bt #0 0x409c2c2f in strlen () from /lib/libc.so.6 #1 0x4026dd3c in qt_write_dib () from /usr/lib/libqt-mt.so.3 #2 0x4026e5ef in qt_write_dib () from /usr/lib/libqt-mt.so.3 #3 0x402610f9 in QImage::QImage () from /usr/lib/libqt-mt.so.3 #4 0x402a6807 in QPixmap::QPixmap () from /usr/lib/libqt-mt.so.3 #5 0x080663df in QString::~QString () #6 0x40962dc6 in __libc_start_main () from /lib/libc.so.6 #7 0x0804f0e1 in ?? () More output at: http://www.clusterix.net/bt.txt This test was also with the 2.4.27 migshm patch. If you need any more information about this bug, just let me know. Thanks, J Silverman --- J S <g1p...@ya...> wrote: > Hi All, > > I'm currently working on the next release of > Clusterix; however, I'm having some major problems > with OpenMosix that I just can't seem to fix. > > The default install of the userland tools added some > "mosrun -h" entries in inittab, but with all of > them, > all but one process was then subsequently locked > from > migration, including any new processes. If I remove > one mosrun entry from one line (which also starts > the > main script that loads the rest of Clusterix), all > but > one process is able to migrate from there. I know > neither is correct, from working on my installed > system, which shows some locked processes (mostly > daemons) and the rest unlocked. > > Now, when I try it without the one mosrun command in > inittab, everything seems to work correctly except > for > the openmosixview tools. If I try to load one tool > on > a low powered machine within a cluster, it seems to > try to migrate it before it fully loads and then > causing it to segfault (sometimes the whole kernel > oops's). I have no idea why its behaving this way, > but any help would be appreciated so I can release > the > next Clusterix :-) > > Btw, here is some key info: > > Kernel 2.4.27 (patch-2.4.27-om-20041102) > Most current userland tools > Most current openmosixview thats in Debian unstable > > Thanks, > J Silverman > > > > __________________________________ > Do you Yahoo!? > Yahoo! Small Business - Try our new resources site! > http://smallbusiness.yahoo.com/resources/ > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT > Products from real users. > Discover which products truly live up to the hype. > Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > openMosix-general mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/openmosix-general > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |