On Saturday 04 December 2004 04:28, Anthony Brock wrote: > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Jonas Meurer > Sent: Friday, December 03, 2004 5:05 PM > To: [EMAIL PROTECTED] > Subject: Re: [uml-user] bind9 utils seg fault
> On 02/12/2004 Tad Kollar wrote: > > I'm running a 2.4.27 host + host-skas3-2.4.25.patch and have tried guest > > kernels 2.6.8.1 (patched), vanilla 2.6.9, and 2.6.10-rc2-mm4. On each of > > these guests, everything works fine except for tools that come with > > bind9 (host, dig, nslookup, named, rndc, etc) from Debian sid. They all > > seg fault immediately... strace and ltrace indicate the problem > > happening at a slightly different point each time. Strace shows it's > > most often after a munmap(), and ltrace seems to point to libisc as the > > culprit. The same tools work fine on a real host. There's plenty of > > memory available, only about 20M used out of 128M available to each > > guest. > I've been experiencing erratic problems with bind 9.2.3 (bind-9.2.3-76) on > my SuSE 9.1 UML images. The host is running a stock SuSE 2.6.5 kernel > (2.6.5-7.111-smp) while the guest is running 2.6.7-1um. The software will > run for hours or even days between crashes. Unfortunately, I've never been > able to "witness" a crash. The only apparently linked event is a spike in > the CPU for 2-5 minutes prior to the crash. > Unfortunately, I have no idea if this is related to UML or SuSE. > Fortunately, I've minimized the impact through multiple servers and a > script that automates the restart of the daemon when it dies. I don't know > if this might help, but here is the list of linked libraries: > # ldd `which named` > liblwres.so.1 => /usr/lib/liblwres.so.1 (0x4001c000) > libdns.so.11 => /usr/lib/libdns.so.11 (0x4002c000) > libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0x4012d000) > libisccfg.so.0 => /usr/lib/libisccfg.so.0 (0x4021d000) > libisccc.so.0 => /usr/lib/libisccc.so.0 (0x4022d000) > libisc.so.7 => /usr/lib/libisc.so.7 (0x40235000) > libnsl.so.1 => /lib/libnsl.so.1 (0x4026e000) > libpthread.so.0 => /lib/libpthread.so.0 (0x40284000) It uses pthread, i.e LinuxThreads or NPTL. Might someone investigate about what the hell is that "--disable-threads" configure option? If anyone goes to take it and post here, I guess it could be evident what's going on. It might well be using his own NPTL version, or the kernel facilities for it with custom libraries... > libc.so.6 => /lib/libc.so.6 (0x402d7000) > libdl.so.2 => /lib/libdl.so.2 (0x403ec000) > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) -- Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 http://www.user-mode-linux.org/~blaisorblade ------------------------------------------------------- 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://productguide.itmanagersjournal.com/ _______________________________________________ User-mode-linux-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
