From owner-freebsd-stable Tue Apr 25 4:37: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from guardian-ext.merrion.nua.net (guardian-ext.merrion.nua.net [195.7.46.2]) by hub.freebsd.org (Postfix) with ESMTP id 73A2337BD1C for ; Tue, 25 Apr 2000 04:36:58 -0700 (PDT) (envelope-from tony@nua.ie) Received: (from uucp@localhost) by guardian-ext.merrion.nua.net (8.8.8/8.8.6) id MAA00728; Tue, 25 Apr 2000 12:36:24 +0100 (IST) Received: from globetrotter.merrion.nua.net(195.7.46.55) via SMTP by guardian-int.merrion.nua.net, id smtpdhjn722; Tue Apr 25 12:36:17 2000 From: Tony Byrne To: Tony Byrne Cc: Mike Tancsa , stable@FreeBSD.ORG Subject: Re: /usr/src/sys/modules/mlx Date: Tue, 25 Apr 2000 12:34:45 +0100 Organization: Nua Ltd. Message-ID: References: <4.2.2.20000424233913.039ecf08@mail.sentex.net> In-Reply-To: X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Apr 2000 12:05:02 +0100, you wrote: >Mike, > >Yup. I'm seeing similar problems, but during a GENERIC kernel compile. >Actually I'm in the early stages of doing a source upgrade of my >RELENG_3 workstation to RELENG_4. Maybe the problem is related to >this? I did a cvsup of the latest RELENG_4 sources this morning. I've checked the CVS repository and there's been a very recent commit of mlx_disk.c (about 16 hours ago) which *might* be the cause. Since I don't have a Mylex RAID controller and I only needed a 4.0 kernel in order to complete a source upgrade of 3.4 to 4.0, I commented out the mlx device line in my GENERIC kernel config file and the system happily compiled the kernel. Regards, Tony. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message