Date: Mon, 09 Oct 2006 15:33:35 -0500 From: Eric Anderson <anderson@centtech.com> To: Fredrik Widlund <fredrik.widlund@qbrick.com> Cc: freebsd-current@freebsd.org Subject: Re: 6.2-BETA2 Dell PE1950 Message-ID: <452AB21F.20700@centtech.com> In-Reply-To: <45266948.3070407@qbrick.com> References: <4522E54C.7060406@qbrick.com> <4523AA3C.2000107@qbrick.com> <45266948.3070407@qbrick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <LSILogic SAS/SATA Adapter> 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.
------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?452AB21F.20700>