From owner-freebsd-hackers Wed Jun 28 05:58:39 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA05409 for hackers-outgoing; Wed, 28 Jun 1995 05:58:39 -0700 Received: from husky.cslab.vt.edu (jaitken@cslab.cs.vt.edu [128.173.41.87]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA05403 for ; Wed, 28 Jun 1995 05:58:37 -0700 Received: (jaitken@localhost) by husky.cslab.vt.edu (8.6.10/8.6.4) id IAA17027; Wed, 28 Jun 1995 08:58:24 -0400 From: Jeff Aitken Message-Id: <199506281258.IAA17027@husky.cslab.vt.edu> Subject: Re: Random Lockups To: hm@altona.hamburg.com Date: Wed, 28 Jun 1995 08:58:24 -0400 (EDT) Cc: jaitken@cslab.cs.vt.edu, freebsd-hackers@freebsd.org In-Reply-To: from "Hellmuth Michaelis" at Jun 27, 95 10:17:59 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1486 Sender: hackers-owner@freebsd.org Precedence: bulk > Strange. Ispcvt is just straightforward and simple, the ioctls used do not > touch any sensible hardware, they just copy some bytes from here to there. > > hellmuth Perhaps it was just a coincidence? I did have a few other things running (an xterm or two, emacs, xconsole, maybe xlock). As I mentioned, the first lockup was during a disk-intensive operation (kernel recompile in the background, and a find in the foreground). It could have been the same thing. Perhaps there's some subtle bug in the NCR driver [*], or maybe I have some hardware that is ever so slightly out of whack that's causing these problems; I don't know. I tend to suspect the latter, or more people would have seen the same behaviour. Anyway, since these lockups don't seem to be repeatable (I tried running several 'find /' after the first one and couldn't make it happen again), and this machine is just for personal use, I'm not too terribly worried about it. Maybe they'll just go away when I install 2.1 ;) ;) [*] Stefan: I'm still working on the broken network connection at home, so I will send you that bug/problem report ASAP. On a completely unrelated note, I havvened to notice the following the last time I rebooted: (going from memory here, so it may not be 100% right) RTC basemem(635K) != BIOS basemem (640K) I didn't go digging through the boot/kernel code to find that error message; instead I was hoping someone could tell me what it means. ;) -- Jeff Aitken jaitken@vt.edu