From owner-freebsd-current@FreeBSD.ORG Wed Aug 13 03:43:25 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C514637B401 for ; Wed, 13 Aug 2003 03:43:25 -0700 (PDT) Received: from pump2.york.ac.uk (pump2.york.ac.uk [144.32.128.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id D516243FAF for ; Wed, 13 Aug 2003 03:43:24 -0700 (PDT) (envelope-from gavin@ury.york.ac.uk) Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81]) by pump2.york.ac.uk (8.12.9/8.12.9) with ESMTP id h7DAhNoN018677; Wed, 13 Aug 2003 11:43:23 +0100 (BST) Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.12.8p1/8.12.8) with ESMTP id h7DAhNJF042743; Wed, 13 Aug 2003 11:43:23 +0100 (BST) (envelope-from gavin@ury.york.ac.uk) Received: from localhost (gavin@localhost)h7DAhN4N042740; Wed, 13 Aug 2003 11:43:23 +0100 (BST) Date: Wed, 13 Aug 2003 11:43:23 +0100 (BST) From: Gavin Atkinson To: Soeren Schmidt In-Reply-To: <200308131008.h7DA88xX086193@spider.deepcore.dk> Message-ID: <20030813112706.U42447-100000@ury.york.ac.uk> References: <200308131008.h7DA88xX086193@spider.deepcore.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: TESTERS WANTED for ATAng preview 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2003 10:43:26 -0000 On Wed, 13 Aug 2003, Soeren Schmidt wrote: > It seems Gavin Atkinson wrote: > > ata1: spurious interrupt - status=0x7f error=0x7f reason=0x7f > > ad0: 19881MB [40395/16/63] at ata0-master UDMA100 > > acd0: CDROM at ata1-slave PIO4 > > OK, your CDROM doesn't like to be a sole master it appears... I hate it when people respond with this, but I'm going to join them and say "It works under Windows"... Also, under the new code, this problem prevents the booting of the machine, but under the old code the machine carries on booting after giving up on the drive. Is it possible for this failure mode to not prevent the booting of the machine at least? Gavin