Date: Wed, 13 Aug 2003 09:30:01 +0100 (BST) From: Gavin Atkinson <gavin@ury.york.ac.uk> To: Soeren Schmidt <sos@spider.deepcore.dk> Cc: current@freebsd.org Subject: Re: TESTERS WANTED for ATAng preview 1 Message-ID: <20030813091223.I40092-100000@ury.york.ac.uk> In-Reply-To: <200308081955.h78JtCB9065960@spider.deepcore.dk> References: <200308081955.h78JtCB9065960@spider.deepcore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 8 Aug 2003, Soeren Schmidt wrote: > ftp://ftp.deepcore.dk/pub/ATAng > Before these rather radical changes to the ATA driver hits the > tree, here is the opportunity to test them out, give usefull > feedback and for the depending subsytems to adjust to the new > ways of things (burncd & atapicam are good examples). Hi, I'm using ATAng-20030809-1.tgz on top-of-tree current on hardware detected with the old ATA code as: atapci0: <Intel ICH5 UDMA100 controller> port 0xffa0-0xffaf,0-0x3,0-0x7,0-0x3,0-0x7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 atapci1: <Intel ICH5 SATA150 controller> port 0xdc00-0xdc0f,0xe000-0xe003,0xe400-0xe407,0xe800-0xe803,0xec00-0xec07 irq 10 at device 31.2 on pci0 ata2: at 0xec00 on atapci1 ata3: at 0xe400 on atapci1 ata1-master: timeout waiting for interrupt ata1-master: ATAPI identify failed ad0: 19881MB <Maxtor 6E020L0> [40395/16/63] at ata0-master UDMA100 (ata1-master is a CD-ROM drive, and freebsd has been unable to detect it since I installed FreeBSD onto this machine about two weeks ago). With the new ATA code, the boot now hangs. I now get on a verbose bootup: ata1-master: FAILURE - ATAPI_IDENTIFY timeout ata1: resetting devices .. ata1: pre reset mask=03 ostat0=58 ostat2=00 ata1-master: ATAPI 14 EB ata1-slave: ATAPI 7F 7F ata1: after reset mask=03 stat0=10 stat1=00 ata1: devices=04 ata1-master: FAILURE - ATAPI_IDENTIFY status=1<ERROR> error=0 <hang here> db> tr 0 mi_switch(...) msleep(...) ata_queue_request(...) ata_getparam(...) ata_identify_devices(...) ata_boot_attach(...) Unplugging the CD-ROM drive allows the machine to boot normally. Once booted, I keep seeing these messages relating to the S-ATA controller (which has no devices plugged into it): ata2: spurious interrupt - status=0x7f error=0xff reason=0xff ata3: spurious interrupt - status=0x7f error=0xff reason=0xff These are also new with the new ATA code. Hope that all helps, I can test any patches necessary. Gavin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030813091223.I40092-100000>