From owner-freebsd-questions Fri Apr 28 23:43:51 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mostgraveconcern.com (mostgraveconcern.com [216.82.145.240]) by hub.freebsd.org (Postfix) with ESMTP id 7AC6137B87F for ; Fri, 28 Apr 2000 23:43:47 -0700 (PDT) (envelope-from dan@mostgraveconcern.com) Received: from danco (danco.mostgraveconcern.com [10.0.0.2]) by mostgraveconcern.com (8.9.3/8.9.3) with SMTP id XAA00441 for ; Fri, 28 Apr 2000 23:43:47 -0700 (PDT) (envelope-from dan@mostgraveconcern.com) Message-ID: <060901bfb1a6$43d0ad20$0200000a@danco> Reply-To: "Dan O'Connor" From: "Dan O'Connor" To: "freebsd-questions" Subject: atapci0 error with 4.0! Date: Fri, 28 Apr 2000 23:43:44 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh, no! FBSD 4.0 doesn't like my Dell Dimension XPS 90MHz (Intel P166MHz O/D CPU) motherboard... I'm in the process of upgrading 3.4-STABLE to 4.0-STABLE and after the 'make buildworld' and kernel compile steps, I reboot the machine into single-user mode, and poof--kenel panic: atapci0: port 0x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 atapci0: Busmastering DMA not supported panic: resource_list_alloc: resource entry is busy This error occurs not only with my custom kernel, but with GENERIC as well. This machine runs flawlessly with 3.4-STABLE (and 3.3, 3.2, 3.1, 2.2.8, and 2.2.7 before that), so I really doubt if the ATA controller chip is *that* buggy. Just to check to see if it was just this machine, I tried booting the 4.0 installation floppies on a similar machine (w/ 90MHZ CPU) and, presto, same thing... I get the impression the new ATAPI driver isn't really ready for prime time yet.... Is there anything I can do about this? It seems a shame to be stuck with 3.4 for the rest of my life... The complete boot message is below... --Dan --- BOOT MESSAGES --- FreeBSD/i386 bootstrap loader, Revision 0.7 639/65472kB (root@pandora.mostgraveconcern.com, Tue Apr 18 22:14:53 PDT 2000) Loading /boot/defaults/loader.conf /kernel text=0x12f645 data=0x1c060+0x19f98 syms=[0x4+0x234a0+0x4+0x25fad] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... Type '?' for a list of commands, 'help' for more detailed help. disk1s1a:> unload disk1s1a:> load /GENERIC /GENERIC text=0x21b5a2 data=0x27bcc+0x1ed2c syms=[0x4+0x30ec0+0x4+0x32da5] disk1s1a:> boot -s Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #0: Fri Apr 28 22:23:18 PDT 2000 root@pandora.mostgraveconcern.com:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Overdrive Pentium/P55C (139.60-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x1544 Stepping = 4 Features=0x8001bf real memory = 83886080 (81920K bytes) avail memory = 77647872 (75828K bytes) Preloaded elf kernel "GENERIC" at 0xc03c8000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 atapci0: port 0x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 atapci0: Busmastering DMA not supported panic: resource_list_alloc: resource entry is busy Uptime: 0s Automatic reboot in 15 seconds - press a key on the console to abort -- Dan O'Connor On Matters of Most Grave Concern http://www.mostgraveconcern.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message