From owner-freebsd-current Fri Dec 15 15:08:56 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA24949 for current-outgoing; Fri, 15 Dec 1995 15:08:56 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA24944 Fri, 15 Dec 1995 15:08:52 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id QAA18167; Fri, 15 Dec 1995 16:11:14 -0700 Date: Fri, 15 Dec 1995 16:11:14 -0700 From: Nate Williams Message-Id: <199512152311.QAA18167@rocky.sri.MT.net> To: Ollivier Robert Cc: sos@FreeBSD.ORG, nate@rocky.sri.MT.net, current@FreeBSD.ORG Subject: Re: -current kernel is *very* unusable In-Reply-To: <199512152302.AAA00878@keltia.freenix.fr> References: <199512151928.UAA03732@ra.dkuug.dk> <199512152302.AAA00878@keltia.freenix.fr> Sender: owner-current@FreeBSD.ORG Precedence: bulk > > I get core dunps all over the place if I stress the system a little, > > ie a cvs update will produce multiple coredumps if I start a Xsession > > on another vty. It seems we have some really bad stuff in there > > somewhere. I've checked on my old system from about 28 september, and > > it doesn't have the above problems, even the atapi driver works there ;( > > I reported a problem at probe time for the EISA stuff (Buslogic) a few days > ago. It appears to have been fixed but with my current kernel, sources from > today, everything works... except that when I launch X11, the mouse doesn't > move at all !! Interrupts seem to get in (as reported by systat -netstat) > but the pointer is frozen. My box is an IBM laptop. Specs are: 20MB of memory 810 MB IDE disk 2.88MB floppy psm0 device (disabled/enabled it doesn't seem to make any difference) sio 0 - 16450's zp0 - 3C589C lpt0 - Parallel printer Pretty basic stuff here. If I add 'DDB', the machine hangs forever. However, the kernel without DDB simply reboots. Nate