From owner-freebsd-questions Sun May 19 0:59:24 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mail.halplant.com (66-61-52-186.wo4.cox.rr.com [66.61.52.186]) by hub.freebsd.org (Postfix) with ESMTP id 17A7437B40C for ; Sun, 19 May 2002 00:59:19 -0700 (PDT) Received: by mail.halplant.com (Postfix, from userid 1001) id 0598118D; Sun, 19 May 2002 03:59:17 -0400 (EDT) Date: Sun, 19 May 2002 03:59:17 -0400 From: Andrew J Caines To: FreeBSD Questions Subject: Kernel bombs on Promise TX2 Ultra ATA/100 with disk Message-ID: <20020519075917.GA330@hal9000.halplant.com> Reply-To: Andrew J Caines Mail-Followup-To: FreeBSD Questions Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.99i Organization: H.A.L. Plant X-PGP-Fingerprint: C59A 2F74 1139 9432 B457 0B61 DDF2 AA61 67C3 18A1 X-Powered-by: FreeBSD 4.6-RC X-URL: http://halplant.com:88/ Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Summary: Kernel boots with Promise ATA/100 controler and no disks, boots with disk on ATA/33 controler, crashes with disk on ATA/100 controler. Details: The onboard ATA/33 controler handles the boot disk (Quantum Fireball 6.4GB), CD-ROM and an ATA/100 disk (Maxtor 20GB). To get more out of the Maxtor, I added the Promise controler and attached the Maxtor to it. During boot, the BIOS picks up the Promise controler and shows it probe and find the Maxtor and correctly determine it to be UDMA/100 capable. The boot loader loads as normal, but as soon as the kernel (both 4.5-STABLE and recent 4.6-RC) load starts, it bombs with a console message which look vaguely like.. epi: 0001xb4 abc: 0053dt ... [five more lines like that] BTX Halted. ..at which point it hangs hard. With the Maxtor attached to the onboard ATA/33 controler, the kernel boots fine and recognises the Promise controler. # dmesg | egrep '^(ata|ad)' atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 atapci1: port 0xfc70-0xfc7f,0xfc8c-0xfc8f,0xfc68-0xfc6f,0xfc88-0xfc8b,0xfc60-0xfc67 mem 0xfedf8000-0xfedfbfff irq 9 at device 16.0 on pci0 ata2: at 0xfc60 on atapci1 ata3: at 0xfc68 on atapci1 ata0-slave: ATA identify retries exceeded ad0: 6149MB [13328/15/63] at ata0-master UDMA33 ad1: 19541MB [39703/16/63] at ata1-master UDMA33 When I connected an ATA/33 Zip disk to the Promise controler, it bombs in exactly the same fashion. Any assistance in determining why I can't have my disk on the Promise controler would be much appreciated. The only suspicion I have is that this may be irq related. I seem to have quite a few devices (all working) on irq 9: # dmesg | awk '/irq 9/{print $1,$2,$3,$4}' pci1: port atapci1: