Date: Fri, 29 Dec 95 14:45:18 EDT From: M C Wong <mcw@hpato.aus.hp.com> To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: mcw@hpato.aus.hp.com, freebsd-questions@freefall.freebsd.org Subject: Re: [2.1R] what happens when swap is full ? Message-ID: <199512290345.AA073118721@hp.com> In-Reply-To: <199512290247.NAA04952@genesis.atrad.adelaide.edu.au>; from "Michael Smith" at Dec 29, 95 1:17 pm
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- > M C Wong stands accused of saying: > > I just have a lock up of the system in X session after loading > > the swap space with as high as 96% and I think it's growing. In fact > > the whole system just hangs again. Note, this is also a follow-up with > > some paging errors which posted before and now I disabled the sd0s1b > > leaving only wd0s2b (which is smaller) to see if the previous paging > > errors will go away. > Sorry, I don't recall your paging errors message; could you repost the > bare details? lespoir:/local/home/wongm 124 > Dec 26 13:56:50 lespoir last message repeated 126 times Dec 26 13:56:52 lespoir /kernel: aha0: Invalid bus phase/sequence Dec 26 13:56:50 lespoir last message repeated 126 times Dec 26 13:56:52 lespoir /kernel: aha0: Invalid bus phase/sequence Dec 26 13:56:52 lespoir /kernel: vnode_pager_input: I/O read error Dec 26 13:56:52 lespoir /kernel: vnode_pager_input: I/O read error Dec 26 13:56:52 lespoir /kernel: vm_fault: pager input (probably hardware) error, PID 1553 failure Dec 26 13:56:52 lespoir /kernel: vm_fault: pager input (probably hardware) error, PID 1553 failure Dec 26 13:56:53 lespoir /kernel: Linux-emul(1204): syslog() not supported (BSD sigreturn) Dec 26 13:56:53 lespoir /kernel: Linux-emul(1204): syslog() not supported (BSD sigreturn) As pointed in my earlier postings, sometimes some processes get killed, this is most obvious when you switch between virtual screen in the same vt session using fvwm, and when you try to access, say, an xterm after leaving it alone for long time, you can hear that the disk is paging by the noise, and as soon as when you try to type something in the xterm shell, it disappears and I can see on the console the above errors plus others saying things like process id gets killed. In the most unfortunate instances, I have processes like init gets killed which subsequently results in a system hang soon after it gets killed, or instance when you are puzzled why the mail you sent out is sitting in the queue with message saying server timeout, which in fact the local sendmail has been killed ... > That's unusual, unless you have something running overnight with a > memory leak. You're not running xperfmon by any chance are you? Yes, I have 2 BSDI of Netscape 2.0b3 running, and 1 Linux version of Netscape running plus other stuff like xearth, cxterm, top, vmstat, istat, nfsstat, xterm, tin etc. Oddly enough not xperfmon. > -- > ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ > ]] Genesis Software genesis@atrad.adelaide.edu.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ > ]] "Who does BSD?" "We do Chucky, we do." [[ - -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ M.C Wong Email: mcw@hpato.aus.hp.com Australian Telecom Operation Voice: +61 3 9210 5568 Hewlett-Packard Australia Ltd Fax: +61 3 9210 5550 P.O. Box 221, Blackburn 3130, Australia OS: FreeBSD-1.1.5.1 http://www-ato.aus.hp.com/~mcw -----BEGIN PGP SIGNATURE----- Version: 2.6.2i iQCVAwUBMONkQEmThh0X7Um5AQG/IwP/Yg67PAb111umENPHgyDZNLbJM2sgebO9 ESpXIRvECMpUzgj/T7bAEUuTo6zQnleI/h2SmboirVY+p1pSVOImriHjTFIEWOb2 wFLuDtjixMnZlS0/seIyY7zfGm8L6WA/mVgEYFlcr1k4/CR36NJrK7VFIotM3pof cf9E5b2BnC4= =K3g3 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512290345.AA073118721>