From owner-freebsd-stable@FreeBSD.ORG Thu Oct 5 21:11:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 B098916A40F; Thu, 5 Oct 2006 21:11:32 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id D669E43D45; Thu, 5 Oct 2006 21:11:31 +0000 (GMT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id k95LBMBj095448; Fri, 6 Oct 2006 05:11:22 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id k95LBMf5095447; Fri, 6 Oct 2006 05:11:22 +0800 (KRAST) (envelope-from eugen) Date: Fri, 6 Oct 2006 05:11:22 +0800 From: Eugene Grosbein To: Dmitry Pryanishnikov Message-ID: <20061005211121.GA95111@svzserv.kemerovo.su> References: <451F6E8E.8020301@freebsd.org> <4523916C.1080905@crc.u-strasbg.fr> <20061004163622.GA35298@xor.obsecurity.org> <20061004173637.GA66349@svzserv.kemerovo.su> <20061005102923.N84384@fledge.watson.org> <20061005115140.GA47746@svzserv.kemerovo.su> <20061005130829.A46123@fledge.watson.org> <20061005144852.GA60575@svzserv.kemerovo.su> <20061005164821.GA71411@svzserv.kemerovo.su> <20061005235729.H36667@atlantis.atlantis.dp.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061005235729.H36667@atlantis.atlantis.dp.ua> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Stable , Robert Watson , bug-followup@freebsd.org Subject: Re: kern/103841: [fdc] fdc(4) does not work (regression) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2006 21:11:32 -0000 On Fri, Oct 06, 2006 at 12:00:15AM +0300, Dmitry Pryanishnikov wrote: > The problem is clearly an I/O port resource misdetection: > On Fri, 6 Oct 2006, Eugene Grosbein wrote: > >>4.11-STABLE: > >>fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > ---------------------------------------^^^^^^^^^^^^^^^^^ > OK. > >>6.2-PRERELEASE: > >>fdc0: port 0x3f0-0x3f5,0x3f0 irq 6 drq 2 on > >>acpi0 > ----------------------------------------^^^^^^^^^^^^^^^^^ > Bad (no 0x3f7, 0x3f0 gets listed twice). Recent revisions of fdc(4) do not use control register at port 0x3f7. CURRENT's version works fine and still probes controller this way, without 0x3f7. You can get background info from commint logs for fdc.c Eugene Grosbein