From owner-freebsd-questions@FreeBSD.ORG Sat May 1 19:52:33 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05AE416A4CE for ; Sat, 1 May 2004 19:52:33 -0700 (PDT) Received: from sdf.lonestar.org (ol.freeshell.org [192.94.73.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AB4943D1F for ; Sat, 1 May 2004 19:52:32 -0700 (PDT) (envelope-from lukas@sdf.lonestar.org) Received: from sdf.lonestar.org (IDENT:lukas@otaku.freeshell.org [192.94.73.2]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id i422qTvP011047 for ; Sun, 2 May 2004 02:52:29 GMT Received: (from lukas@localhost) by sdf.lonestar.org (8.12.10/8.12.8/Submit) id i422qTZU011450; Sat, 1 May 2004 19:52:29 -0700 (PDT) Date: Sat, 1 May 2004 19:52:29 -0700 (PDT) From: LukeD@pobox.com X-X-Sender: lukas@otaku.freeshell.org To: freebsd-questions@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: RAID card confusing mptable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: LukeD@pobox.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 May 2004 02:52:33 -0000 In reference to the situation I posted about on April 29, I've found a workaround to the problem. When I enabled a RAID array in my RAID controller's BIOS, I would get a "mptable_walk_table: Unknown MP Config Entry 18" panic while the kernel was loading. When I disabled the array, all was fine. mptable doesn't even show the problematic mptable entry. I've found a workaround that will let my RAID card work. Disabling APIC. After disabling APIC, the RAID card seems to work, but mptable shows the bad entry and closes with an MPTABLE HOSED message. I've read that there are still some open issues with apic, and getting RAID working is important to me, so I'll just turn off apic and bide my time. I have no proof that the apic on my motherboard is any good anyway, so it may very well be a hardware problem. I don't know how to tell.