Re: amd(8) cores dump when load high
> Yes, we found that it crashes when swap is used. on an amd64 architecture, amd could not plock it's pages in memory, and would, under memory preasure be swapped out, and break. I just run some tests under 7.1-PRERELEASE, and - it seems that plock is working. - amd is not being swapped out. are you running with amd -S ? danny > > > On Fri, Dec 26, 2008 at 6:02 PM, Rong-en Fan wrote: > > On Tue, Dec 23, 2008 at 12:44 AM, Lin Jui-Nan Eric > > wrote: > >> Dear listers, > >> > >> We currently found that amd frequently cores dump while loading is > >> high (about 4~5) after we upgrade world & kernel from 7.0-RELEASE to > >> 7.1-PRERELEASE. > >> > >> I have read -stable and svn log of 7-STABLE, but can not found a > >> report or a solution. Did anyone have the same issue? Thank you very > >> much. > >> > > > > According to my previous experience, amd 6.1.5 crashes > > under low memory situations. Not necessary high load. > > > > Regards, > > Rong-En Fan > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: amd(8) cores dump when load high
No, we do not running amd with -S. # ps auxww | grep amd root 706 0.0 0.1 7660 5416 ?? Ss Wed05PM 4:48.12 /usr/sbin/amd -p -k amd64 -x all /net amd.map On Sat, Dec 27, 2008 at 4:51 PM, Danny Braniss wrote: >> Yes, we found that it crashes when swap is used. > > on an amd64 architecture, amd could not plock it's pages in memory, and would, > under memory preasure be swapped out, and break. > I just run some tests under 7.1-PRERELEASE, and > - it seems that plock is working. > - amd is not being swapped out. > are you running with amd -S ? >danny > >> >> >> On Fri, Dec 26, 2008 at 6:02 PM, Rong-en Fan wrote: >> > On Tue, Dec 23, 2008 at 12:44 AM, Lin Jui-Nan Eric >> > wrote: >> >> Dear listers, >> >> >> >> We currently found that amd frequently cores dump while loading is >> >> high (about 4~5) after we upgrade world & kernel from 7.0-RELEASE to >> >> 7.1-PRERELEASE. >> >> >> >> I have read -stable and svn log of 7-STABLE, but can not found a >> >> report or a solution. Did anyone have the same issue? Thank you very >> >> much. >> >> >> > >> > According to my previous experience, amd 6.1.5 crashes >> > under low memory situations. Not necessary high load. >> > >> > Regards, >> > Rong-En Fan >> > >> ___ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" >> > > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: process stuck in vmopar
2008/12/27 Mike Tancsa : > At 03:31 PM 12/26/2008, pluknet wrote: > >> Also seen on 6.3, 6.4 releases. >> >> Prepared as PR kern/129956. > > I wonder if this is the same or similar issue in where the poster is also > seeing processes stuck in UFS state > > http://lists.freebsd.org/pipermail/freebsd-stable/2008-December/047118.html > I doubt. Stucking in ufs state in my case is only triggered by earlier stucking of another process in vmopar state. Also no high load there seen in gstat, as in that mail. -- wbr, pluknet ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: amd(8) cores dump when load high
> No, we do not running amd with -S. > > # ps auxww | grep amd > root 706 0.0 0.1 7660 5416 ?? Ss Wed05PM 4:48.12 > /usr/sbin/amd -p -k amd64 -x all /net amd.map > well, I'm running 7.1-PRERELEASE, what does the amd logs show? Dec 27 10:37:01 sf-02 amd[856]: AM-UTILS VERSION INFORMATION: Dec 27 10:37:01 sf-02 amd[856]: Copyright (c) 1997-2006 Erez Zadok Dec 27 10:37:01 sf-02 amd[856]: Copyright (c) 1990 Jan-Simon Pendry Dec 27 10:37:01 sf-02 amd[856]: Copyright (c) 1990 Imperial College of Science, Technology & Medicine Dec 27 10:37:01 sf-02 amd[856]: Copyright (c) 1990 The Regents of the University of California. Dec 27 10:37:01 sf-02 amd[856]: am-utils version 6.1.5 (build 1). Dec 27 10:37:01 sf-02 amd[856]: Report bugs to https://bugzilla.am-utils.org/ or am-ut...@am-utils.org. Dec 27 10:37:01 sf-02 amd[856]: Configured by da...@sunfire on date Sun Jun 29 16:59:06 IDT 2008. Dec 27 10:37:01 sf-02 amd[856]: Built by da...@sunfire on date Sun Jun 29 17:02:07 IDT 2008. Dec 27 10:37:01 sf-02 amd[856]: cpu=x86_64 (little-endian), arch=amd64, karch=amd64. Dec 27 10:37:01 sf-02 amd[856]: full_os=freebsd7.0, os=freebsd7, osver=7.0, vendor=unknown, distro=none. Dec 27 10:37:01 sf-02 amd[856]: domain=unknown.domain, host=sf-02, hostd=sf-02.unknown.domain. Dec 27 10:37:01 sf-02 amd[856]: Map support for: root, passwd, hesiod, union, nis, ndbm, file, exec, error. Dec 27 10:37:01 sf-02 amd[856]: AMFS: nfs, link, nfsx, nfsl, host, linkx, program, union, ufs, cdfs, Dec 27 10:37:01 sf-02 amd[856]: pcfs, auto, direct, toplvl, error, inherit. Dec 27 10:37:01 sf-02 amd[856]: FS: cd9660, nfs, nfs3, nullfs, msdosfs, ufs, unionfs. Dec 27 10:37:01 sf-02 amd[856]: Network: wire="132.65.16.0" (netnumber=132.65.16). Dec 27 10:37:01 sf-02 amd[856]: My ip addr is 127.0.0.1 Dec 27 10:37:01 sf-02 amd[857]: released controlling tty using setsid() Dec 27 10:37:01 sf-02 amd[857]: Locked process pages in memory ** > > On Sat, Dec 27, 2008 at 4:51 PM, Danny Braniss wrote: > >> Yes, we found that it crashes when swap is used. > > > > on an amd64 architecture, amd could not plock it's pages in memory, and > > would, > > under memory preasure be swapped out, and break. > > I just run some tests under 7.1-PRERELEASE, and > > - it seems that plock is working. > > - amd is not being swapped out. > > are you running with amd -S ? > >danny > > > >> > >> > >> On Fri, Dec 26, 2008 at 6:02 PM, Rong-en Fan wrote: > >> > On Tue, Dec 23, 2008 at 12:44 AM, Lin Jui-Nan Eric > >> > wrote: > >> >> Dear listers, > >> >> > >> >> We currently found that amd frequently cores dump while loading is > >> >> high (about 4~5) after we upgrade world & kernel from 7.0-RELEASE to > >> >> 7.1-PRERELEASE. > >> >> > >> >> I have read -stable and svn log of 7-STABLE, but can not found a > >> >> report or a solution. Did anyone have the same issue? Thank you very > >> >> much. > >> >> > >> > > >> > According to my previous experience, amd 6.1.5 crashes > >> > under low memory situations. Not necessary high load. > >> > > >> > Regards, > >> > Rong-En Fan > >> > > >> ___ > >> freebsd-stable@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > >> > > > > > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: amd(8) cores dump when load high
On Sat, Dec 27, 2008 at 7:03 PM, Danny Braniss wrote: >> No, we do not running amd with -S. >> >> # ps auxww | grep amd >> root 706 0.0 0.1 7660 5416 ?? Ss Wed05PM 4:48.12 >> /usr/sbin/amd -p -k amd64 -x all /net amd.map >> > well, I'm running 7.1-PRERELEASE, what does the amd logs show? > [...] > Dec 27 10:37:01 sf-02 amd[857]: Locked process pages in memory >** Hmm.. interesting, I got this Dec 26 15:32:11 bsd2 amd[39723]: Couldn't lock process pages in memory using mlo ckall(): Resource temporarily unavailable w/ 7-STABLE around Sep 4. I don't put plock = no in amd.conf, so by default it's plock'ed. Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: amd.core on 7.1-BETA2 amd64
"Julian Stacey" wrote: > Hi stable@, > I have been seeing some amd core dumps in / running 7.1-BETA2 amd64 PS I see with cd / ; /bin/ls -l | grep host lrwxrwxrwx 1 root wheel 5 Dec 27 12:36 carp -> /host lrwxrwxrwx 1 root wheel 5 Dec 27 13:41 host -> /host (carp is nothing I deliberately set up) host -> /host is obviously wrong, should be a directory, something keeps removing the directory & creating this recursive symbolic link. Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
amd.core on 7.1-BETA2 amd64
Hi stable@, I have been seeing some amd core dumps in / running 7.1-BETA2 amd64 with rc.confamd_flags="-l syslog -n -r -t 3 /host /etc/amd.map" I recall someone else mentioned amd cores recently too. I have reinstalled with /etc/make.conf CFLAGS += -g -static # for gdb debugger For /usr/src/usr.sbin/amd & installed without -s so: file `which amd` /usr/sbin/amd: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), for FreeBSD 7.0 (700112), statically linked, FreeBSD-style, not stripped If I can get it to core again I will provide a backtrace In hope of producing something perhaps interesting for re@ I will cvs -R export -r RELENG_7_1 src # make world Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: amd(8) cores dump when load high
Lin Jui-Nan Eric wrote: > Dear listers, > > We currently found that amd frequently cores dump while loading is > high (about 4~5) after we upgrade world & kernel from 7.0-RELEASE to > 7.1-PRERELEASE. > > I have read -stable and svn log of 7-STABLE, but can not found a > report or a solution. Did anyone have the same issue? Thank you very > much. When I work on large pictures in Gimp (i.e. 8000x6000), not lying on an amd mounted file system amd dies on my systems. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: amd(8) cores dump when load high
I got "Couldn't lock process pages in memory using mlockall()" too: Dec 27 23:20:38 worker1 amd[90422]: switched to logfile "syslog" Dec 27 23:20:38 worker1 amd[90422]: AM-UTILS VERSION INFORMATION: Dec 27 23:20:38 worker1 amd[90422]: Copyright (c) 1997-2006 Erez Zadok Dec 27 23:20:38 worker1 amd[90422]: Copyright (c) 1990 Jan-Simon Pendry Dec 27 23:20:38 worker1 amd[90422]: Copyright (c) 1990 Imperial College of Science, Technology & Medicine Dec 27 23:20:38 worker1 amd[90422]: Copyright (c) 1990 The Regents of the University of California. Dec 27 23:20:38 worker1 amd[90422]: am-utils version 6.1.5 (build 701100). Dec 27 23:20:38 worker1 amd[90422]: Report bugs to https://bugzilla.am-utils.org/ or am-ut...@am-utils.org. Dec 27 23:20:38 worker1 amd[90422]: Configured by David O'Brien on date 4-December-2007 PST. Dec 27 23:20:38 worker1 amd[90422]: Built by r...@worker1 on date Sun Nov 30 00:20:03 CST 2008. Dec 27 23:20:38 worker1 amd[90422]: cpu=amd64 (little-endian), arch=amd64, karch=amd64. Dec 27 23:20:38 worker1 amd[90422]: full_os=freebsd7.1, os=freebsd7, osver=7.1, vendor=undermydesk, distro=The FreeBSD Project. Dec 27 23:20:38 worker1 amd[90422]: domain=unknown.domain, host=worker1, hostd=worker1.unknown.domain. Dec 27 23:20:38 worker1 amd[90422]: Map support for: root, passwd, union, nis, ndbm, file, exec, error. Dec 27 23:20:38 worker1 amd[90422]: AMFS: nfs, link, nfsx, nfsl, host, linkx, program, union, ufs, cdfs, Dec 27 23:20:38 worker1 amd[90422]: pcfs, auto, direct, toplvl, error, inherit. Dec 27 23:20:38 worker1 amd[90422]: FS: cd9660, nfs, nfs3, nullfs, msdosfs, ufs, unionfs. Dec 27 23:20:38 worker1 amd[90422]: Network: wire="10.1.1.0" (netnumber=10.1.1). Dec 27 23:20:38 worker1 amd[90422]: My ip addr is 127.0.0.1 Dec 27 23:20:38 worker1 amd[90423]: released controlling tty using setsid() Dec 27 23:20:38 worker1 amd[90423]: Couldn't lock process pages in memory using mlockall(): Resource temporarily unavailable Dec 27 23:20:38 worker1 amd[90423]: file server localhost, type local, state starts up Dec 27 23:20:38 worker1 amd[90423]: Trying mount of amd.map on /net fstype toplvl mount_type non-autofs Dec 27 23:20:38 worker1 amd[90423]: creating mountpoint directory '/net' Dec 27 23:20:38 worker1 amd[90424]: /net: disabling nfs congestion window Dec 27 23:20:38 worker1 amd[90423]: first time load of map amd.map succeeded Dec 27 23:20:38 worker1 amd[90423]: amd.map mounted fstype toplvl on /net Dec 27 23:20:38 worker1 amd[90423]: /net set to never timeout I don't have a amd.conf: worker1 [/] -jnlin- ls -al /etc/amd.conf ls: /etc/amd.conf: No such file or directory On Sat, Dec 27, 2008 at 9:07 PM, Rong-en Fan wrote: > On Sat, Dec 27, 2008 at 7:03 PM, Danny Braniss wrote: >>> No, we do not running amd with -S. >>> >>> # ps auxww | grep amd >>> root 706 0.0 0.1 7660 5416 ?? Ss Wed05PM 4:48.12 >>> /usr/sbin/amd -p -k amd64 -x all /net amd.map >>> >> well, I'm running 7.1-PRERELEASE, what does the amd logs show? >> > [...] >> Dec 27 10:37:01 sf-02 amd[857]: Locked process pages in memory >>** > > Hmm.. interesting, I got this > > Dec 26 15:32:11 bsd2 amd[39723]: Couldn't lock process pages in memory using > mlo > ckall(): Resource temporarily unavailable > > w/ 7-STABLE around Sep 4. I don't put plock = no in amd.conf, so > by default it's plock'ed. > > Regards, > Rong-En Fan > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: amd(8) cores dump when load high
> I got "Couldn't lock process pages in memory using mlockall()" too: [...] > On Sat, Dec 27, 2008 at 9:07 PM, Rong-en Fan wrote: > > On Sat, Dec 27, 2008 at 7:03 PM, Danny Braniss wrote: > >>> No, we do not running amd with -S. > >>> > >>> # ps auxww | grep amd > >>> root 706 0.0 0.1 7660 5416 ?? Ss Wed05PM 4:48.12 > >>> /usr/sbin/amd -p -k amd64 -x all /net amd.map > >>> > >> well, I'm running 7.1-PRERELEASE, what does the amd logs show? > >> > > [...] > >> Dec 27 10:37:01 sf-02 amd[857]: Locked process pages in memory > >>** > > > > Hmm.. interesting, I got this > > > > Dec 26 15:32:11 bsd2 amd[39723]: Couldn't lock process pages in memory > > using mlo > > ckall(): Resource temporarily unavailable > > > > w/ 7-STABLE around Sep 4. I don't put plock = no in amd.conf, so > > by default it's plock'ed. > > > > Regards, > > Rong-En Fan > > some more ingrediants: when running vanilla amd it also failes to lock pages: Couldn't lock process pages in memory using mlockall(): Resource temporarily unavailable while the amd I'm running, which includes the latest - non official - patches works fine. but, the main diff I see is: opteron> ldd /usr/sbin/amd /usr/sbin/amd: libc.so.7 => /lib/libc.so.7 (0x80065a000) while opteron> ldd /SBIN/amd /SBIN/amd: librt.so.1 => /usr/lib/librt.so.1 (0x800658000) librpcsvc.so.4 => /usr/lib/librpcsvc.so.4 (0x80075d000) libwrap.so.5 => /usr/lib/libwrap.so.5 (0x800866000) libc.so.7 => /lib/libc.so.7 (0x80096f000) danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
