From owner-freebsd-i386@FreeBSD.ORG Tue Apr 5 08:30:10 2005 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47CB216A4CE for ; Tue, 5 Apr 2005 08:30:10 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D3A343D1D for ; Tue, 5 Apr 2005 08:30:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j358UAwV061571 for ; Tue, 5 Apr 2005 08:30:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j358U9X0061569; Tue, 5 Apr 2005 08:30:09 GMT (envelope-from gnats) Date: Tue, 5 Apr 2005 08:30:09 GMT Message-Id: <200504050830.j358U9X0061569@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Dmitry Pryanishnikov Subject: Re: i386/78929: atapicam prevents boot, system hangs X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dmitry Pryanishnikov List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2005 08:30:10 -0000 The following reply was made to PR i386/78929; it has been noted by GNATS. From: Dmitry Pryanishnikov To: freebsd-gnats-submit@FreeBSD.org, harrycoin@quietfountain.com Cc: Subject: Re: i386/78929: atapicam prevents boot, system hangs Date: Tue, 05 Apr 2005 11:24:52 +0300 Hello! I'm having similar troubles with ATAPICAM under 5.4-PRERELEASE CVSupped at the end of April (after small cosmetical changes came into RELENG_5). My CD-RW drive is AOpen CRW5232, it uses UDMA33 by default. The most interesting thing is that drive passes ATAPICAM initialization normally: 1) when it is connected to motherboard's ICH4 ATA controller; or 2) when I set hw.ata.atapi_dma=0 from the loader. It hanges only when it is connected to Promise Ultra 100 TX2 controller and uses UDMA mode during the boot. So I can set hw.ata.atapi_dma=0 in order to boot system and later set UDMA33 back using atacontrol - my drive then works correctly even on the Promise. Below are references in case some advanced in kernel programming person wants to fix this annoying bug: kernel configuration: ftp://external.atlantis.dp.ua/FreeBSD/PR/78929/lynx boot messages with hw.ata.atapi_dma set to 0: ftp://external.atlantis.dp.ua/FreeBSD/PR/78929/dmesg.boot some screenshots for the verbose boot with hw.ata.atapi_dma=1 and CD-RW attached to Promise controller: ftp://external.atlantis.dp.ua/FreeBSD/PR/78929/1.jpg ftp://external.atlantis.dp.ua/FreeBSD/PR/78929/2.jpg ftp://external.atlantis.dp.ua/FreeBSD/PR/78929/3.jpg ftp://external.atlantis.dp.ua/FreeBSD/PR/78929/4.jpg System doesn't proceed after 4.jpg. I just don't understand why it passes initialization at ICH4 - timing problems? Sincerely, Dmitry -- Atlantis ISP, System Administrator nic-hdl: LYNX-RIPE