From owner-freebsd-stable Fri Nov 24 8:13:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bumper.jellybaby.net (bumper.jellybaby.net [194.159.247.1]) by hub.freebsd.org (Postfix) with ESMTP id B434237B479 for ; Fri, 24 Nov 2000 08:13:56 -0800 (PST) Received: (from simond@localhost) by bumper.jellybaby.net (8.9.2/8.9.2) id QAA49191; Fri, 24 Nov 2000 16:12:40 GMT (envelope-from simond) Date: Fri, 24 Nov 2000 16:12:40 +0000 From: simond@irrelevant.org To: Drew Sanford Cc: stable@FreeBSD.ORG Subject: Re: Update - 4.2 install hangs while booting Message-ID: <20001124161240.D41148@irrelevant.org> References: <3A1E91B6.3040807@planetwe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A1E91B6.3040807@planetwe.com>; from drew@planetwe.com on Fri, Nov 24, 2000 at 10:05:10AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 24, 2000 at 10:05:10AM -0600, Drew Sanford wrote: > I have had a chance to play with 4.2 now, having gotten it installed, > and narrowed down some of the hardware problems that it could be. Here's > a system rundown: > > Asus A7V rev 1.02; Duron 800 > SBLive > NetGear FA 310Tx > 45 GB ATA100 IBM Deskstar as Master on Primary ATA100 > 32x ATAPI cd rom drive as Slave on Primary UDM33/66 > > When I boot the system with the Parallel port enabled in the bios, > regardless of the specified IRQ or IO port in bios, I get this: > > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > ppbus0: IEEE1284 device found /NIBBLE/ECP > Probing for PnP devices on ppbus0: > ppbus0: MLC, PCL, PML > lpt0: on ppbus0 > lpt0: Interupt-driven port > ppi0: on ppbus0 > > and here the system will hang, for at least 25 minutes. Beyond that I > figured it was usless to wait and see if anything would happen, and I > lost pateince besides. Here's the dmesg output for the same system, same > kernel, but with the parallel port disabled in the bios: I've had the same sort of thing happen to me sometimes on my A7V, that was with 4.1-STABLE, I've not had a chance to install 4.2 yet due to FreeBSD misdetecting my 20GB IBM drive as 2GB when using ATA66. Usually I found that just resetting the box after it hung there caused it to work on the next boot. > lauasanf@colossus(~)$ dmesg > ata1-slave: ata_command: timeout waiting for intr > ata1-slave: identify failed > ata1-master: ata_command: timeout waiting for intr > ata1-master: identify failed > ad4: 43979MB [89355/16/63] at ata2-master UDMA100 I get the same errors as these too (although sometimes they don't appear). I think that is just a "feature" of the Promise controller as it could be that which makes Windows pause ages while booting. Best of luck! -- Simon Dick simond@irrelevant.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message