From owner-freebsd-bugs  Mon May 21  7:20:14 2001
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 65D1237B422
	for <freebsd-bugs@hub.freebsd.org>; Mon, 21 May 2001 07:20:10 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f4LEKAY32117;
	Mon, 21 May 2001 07:20:10 -0700 (PDT)
	(envelope-from gnats)
Date: Mon, 21 May 2001 07:20:10 -0700 (PDT)
Message-Id: <200105211420.f4LEKAY32117@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: "Lazaro D. Salem" <salem@statoil.com>
Subject: Re: misc/18201: Freeze at boot time when trying to upgrade a running 
 i386 from 3.3- RELEASE to 4.0 RELEASE
Reply-To: "Lazaro D. Salem" <salem@statoil.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR misc/18201; it has been noted by GNATS.

From: "Lazaro D. Salem" <salem@statoil.com>
To: freebsd-gnats-submit@FreeBSD.org, salem@statoil.com,
	lazaro@online.no
Cc:  
Subject: Re: misc/18201: Freeze at boot time when trying to upgrade a running 
 i386 from 3.3- RELEASE to 4.0 RELEASE
Date: Mon, 21 May 2001 16:20:09 +0200

 A followup to a related PR has been submitted with a work around this
 problem
 See:
 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=26686
 
 Also related is the PR:
 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=26736
 
 The IRQ peculiarity mentioned here has nothing to do with the freeze.
 It has been suggested the culprit is the ex driver probing an installed
 the NE2000 NIC. Disabling the NE2000 did not not help.
 Physically removing the NE2000 did help and the boot completed
 without problems. If the ex driver is the culprit, why cannot we
 disabled
 at the kernel configuration stage? This was possible to do in the
 3.x releases,  but is not possible to do with the 4.x releases.
 
 Cheers
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message