From owner-freebsd-stable Wed Oct 23 9:43:58 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FF1437B401 for ; Wed, 23 Oct 2002 09:43:55 -0700 (PDT) Received: from mailhub.webcraft99.com (prwire.bernama.com [202.188.124.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D93D43E65 for ; Wed, 23 Oct 2002 09:43:53 -0700 (PDT) (envelope-from afu-subscribed-list@aeefyu.net) Received: from localhost (beta.webcraft99.com [127.0.0.1]) by mailhub.webcraft99.com (Postfix) with ESMTP id C1F801932E; Thu, 24 Oct 2002 00:50:00 +0800 (MYT) Received: from krista.webcraft99.net (unknown [203.82.80.184]) by mailhub.webcraft99.com (Postfix) with ESMTP id 4A69519316; Thu, 24 Oct 2002 00:49:52 +0800 (MYT) Subject: Re: Random Crashes in 4.7 when transferring large files From: Al-Afu Reply-To: afu-subscribed-list@aeefyu.net To: afu-subscribed-list@aeefyu.net Cc: stable@FreeBSD.ORG In-Reply-To: <1035267709.580.16.camel@krista.webcraft99.net> References: <5.1.0.14.0.20021018075222.05f207b8@192.168.0.12> <1035267709.580.16.camel@krista.webcraft99.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 24 Oct 2002 00:35:30 +0800 Message-Id: <1035390935.747.9.camel@krista.webcraft99.net> Mime-Version: 1.0 X-Virus-Scanned: by AMaViS new-20020517 X-Razor-id: 67233881a3f08f3416c5789026c2b2ea0ecead23 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Am still looking for a fix for my 4.7-RELEASE no-coredumps crashes :( I've decided to revert to my 4.6.2-RELEASE kernel, to which everything seems to be back to normal for now (transferred 0.5GB files to and fro without any hiccups whatsoever). A study of /var/log/messages reveals the following: Oct 24 00:10:57 krista /kernel.STABLE: vmnet1: promiscuous mode enabled Oct 24 00:10:57 krista init: getting vmemoryuse resource limit: Invalid argument There are other similar messages on logins and crons /var/log/cron has the following: Oct 24 00:00:00 krista /usr/sbin/cron[638]: (root) CMD (newsyslog) Oct 24 00:00:00 krista /usr/sbin/cron[639]: (root) CMD (/usr/libexec/atrun) Oct 24 00:01:00 krista /usr/sbin/cron[645]: (root) CMD (adjkerntz -a) Oct 24 00:10:00 krista /usr/sbin/cron[371]: (root) CMD (/usr/libexec/atrun) Oct 24 00:10:00 krista /usr/sbin/cron[371]: getting vmemoryuse resource limit: Invalid argument Oct 24 00:15:00 krista /usr/sbin/cron[623]: (root) CMD (/usr/libexec/atrun) Oct 24 00:15:00 krista /usr/sbin/cron[623]: getting vmemoryuse resource limit: Invalid argument Does this shed a light on anything? I am pretty positive at this point to rule out hardware glitches. If someone points me to the right direction, I will gladly provide any sort of logs or information which is required to trace the root of the problem. On Tue, 2002-10-22 at 14:21, Al-Afu wrote: > Following my last week's post: > Host crashing when transferring large files (>100MB) over from my > 4.7-RELEASE vmware host to a remote SMB server: > > ------------- > > I have added the following to my kernel config: > makeoptions DEBUG=-g > options DDB > > Then did: > cd /usr/src && make clean && make cleandir && make buildkernel > kernconf=KERNEL && make installkernel kernconf=KERNEL > (however, there arent two copies of kernel built as described by the FAQ > (/kernel and /kernel.debug) > > I edited my /etc/rc.conf to the following: > dumpdev="/dev/ad2s1e" > dumpdir="/var/crash" > > HOWEVER, my /var/crash doesnt contain any core dumps, even after > multiple panics ( i simple copied over some large files to a remote host > to crash my 4.7-RELEASE) > > Even did a "dumpon /dev/ad2s1e" to no avail. > > I can confirm that /dev/ad2s1e exists and is of 1024MB partition, > whereas my system memory is 768MB. > > Did I leave anything out? > > Thanks again > > On Fri, 2002-10-18 at 19:55, Mike Tancsa wrote: > > > > Have a look in the handbook on how to build a debug kernel and how to > > capture a panic via a crash dump. If you find its crashing in the same > > place (ie. you load up the core dump file and it tells you its the same in > > the code) then its possibly a FreeBSD issue. If its crashing in random > > places each time, its more than likely a hardware issue. > > > > ---Mike > > > > At 03:11 PM 10/18/2002 +0800, Feisal Umar wrote: > > >I am frequently encountering crashes on my 4.7 workstation. The common > > > > -------------------------------------------------------------------- > > Mike Tancsa, tel +1 519 651 3400 > > Sentex Communications, mike@sentex.net > > Providing Internet since 1994 www.sentex.net > > Cambridge, Ontario Canada www.sentex.net/mike > > > > > > > -- > Al-Afu > Webcraft Sdn Bhd - http://www.webcraftsolutions.com > - http://www.webcraftworks.com > -------------------------------------- > "Beware of bugs in the above code; I have only proved it correct, not > tried it." > -- Donald Knuth -- Al-Afu Webcraft Sdn Bhd - http://www.webcraftsolutions.com - http://www.webcraftworks.com -------------------------------------- "I didn't know it was impossible when I did it." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message