From owner-freebsd-bugs@FreeBSD.ORG Thu Oct 5 21:20:28 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38E0516A416 for ; Thu, 5 Oct 2006 21:20:28 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4193D43D6A for ; Thu, 5 Oct 2006 21:20:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k95LKOOx006756 for ; Thu, 5 Oct 2006 21:20:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k95LKOvx006755; Thu, 5 Oct 2006 21:20:24 GMT (envelope-from gnats) Date: Thu, 5 Oct 2006 21:20:24 GMT Message-Id: <200610052120.k95LKOvx006755@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Eugene Grosbein Cc: Subject: Re: kern/103841: [fdc] fdc(4) does not work (regression) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eugene Grosbein List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2006 21:20:28 -0000 The following reply was made to PR kern/103841; it has been noted by GNATS. From: Eugene Grosbein To: Dmitry Pryanishnikov Cc: Robert Watson , FreeBSD Stable , bug-followup@freebsd.org Subject: Re: kern/103841: [fdc] fdc(4) does not work (regression) Date: Fri, 6 Oct 2006 05:11:22 +0800 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