From owner-freebsd-current@FreeBSD.ORG Mon Oct 9 20:33:43 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D0BF16A415 for ; Mon, 9 Oct 2006 20:33:43 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A81A43D67 for ; Mon, 9 Oct 2006 20:33:35 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k99KXYDK020215; Mon, 9 Oct 2006 15:33:35 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <452AB21F.20700@centtech.com> Date: Mon, 09 Oct 2006 15:33:35 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20060923) MIME-Version: 1.0 To: Fredrik Widlund References: <4522E54C.7060406@qbrick.com> <4523AA3C.2000107@qbrick.com> <45266948.3070407@qbrick.com> In-Reply-To: <45266948.3070407@qbrick.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/2016/Mon Oct 9 11:58:54 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: 6.2-BETA2 Dell PE1950 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2006 20:33:43 -0000 On 10/06/06 09:33, Fredrik Widlund wrote: > Hi, > > I can't reproduce the problem. Everything is exactly the same, but I get > no timeouts and the nic seems to work without any problems. > > Kind regards, > Fredrik Widlund > > > Fredrik Widlund wrote: >> Hi, >> >> An update, right now the BCE nic seems to work, I'm not sure exactly why >> yet. I'm attaching the dmesg however. >> >> SAS adapter is the PERC 5I, which is handled by the MPT driver in >> 6.2-Beta2. I'll continue to look at this. There are some unhandled >> events (0x12, 0x16), but these might not be needed. >> >> [mpi_ioc.h] >> #define MPI_EVENT_SAS_PHY_LINK_STATUS (0x00000012) >> ... >> #define MPI_EVENT_SAS_DISCOVERY (0x00000016) >> >> [dmesg mpt part] >> mpt0: port 0xec00-0xecff mem >> 0xfc7fc000-0xfc7fffff,0xfc7e0000-0xfc7effff irq 64 at device 8.0 on pci2 >> mpt0: [GIANT-LOCKED] >> mpt0: MPI Version=1.5.12.0 >> mpt0: mpt_cam_event: 0x16 >> mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). >> mpt0: mpt_cam_event: 0x12 >> mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). >> mpt0: mpt_cam_event: 0x16 >> mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). Just a followup: 6.2-BETA2 works on this system, however I just got a panic in the mfi driver. I didn't have a dumpdev set when it broke to ddb (can I set it once in ddb?), but it's still in the debugger if anyone wants any info from it. I think something like this is happening (somewhat guessing here, as I don't have the trace in front of me): In sys/dev/mfi/mfi.c around line 349, mfi_intr gets called, which executes the mfi_complete command and returns, but the device_printf ("Cannot set up interrupt") gets called anyhow and ends up causing a panic down in sccnputc. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------