From owner-freebsd-current Sun Aug 5 12:18: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gnf.org (firewall.gnf.org [208.44.31.34]) by hub.freebsd.org (Postfix) with ESMTP id 8A82437B403 for ; Sun, 5 Aug 2001 12:17:59 -0700 (PDT) (envelope-from gordont@gnf.org) Received: by mail.gnf.org (Postfix, from userid 888) id 989C611E503; Sun, 5 Aug 2001 12:17:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 8903E11A56A for ; Sun, 5 Aug 2001 12:17:59 -0700 (PDT) Date: Sun, 5 Aug 2001 12:17:59 -0700 (PDT) From: Gordon Tetlow To: Subject: ahc fails to attach in -current (was: snapshot installation woes) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 4 Aug 2001, Gordon Tetlow wrote: > Sure enough, that fixed the kernel panic, but here's the next odd piece, > my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 > dmesg reports that ahc0 is there. The lines from the dmesg are (hand > typed): > > ahc0: port 0x5000-0x50ff mem 0x50000000-0x50000fff irq 15 at device 15.0 on pci0 > device_probe_and_attach: ahc0 attach returned 12 > > errno.h says ENOMEM is 12, so it seems that something in the ahc driver is > unable to allocate memory. Dunno where or why, but something is fouling > it up. By contrast 4.3-RELEASE doesn't have any issues (I'll try a recent > snapshot if that would help). Sorry I can't help out any more, but the > debugging tools in the installation disks seem to lacking > (understandably). Okay, I tried with a 4.4-PRERELEASE bootdisk that was available on current.jp.freebsd.org and dmesg came up with the following: ahc0: port 0x5000-0x50ff mem 0x50000000-0x50000fff irq 15 at device 15.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs Since -stable and -current are using the exact same driver, there is something more subtle (and sinister?) going on that I can't figure out. At this point, I'm throwing my hands up in the air unless someone can give me a better idea as to what the possible problem could be. I'd really like to try -current on this box as it's a dual proc PPro 200. Thanks, -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message