From owner-freebsd-current@FreeBSD.ORG Mon Feb 19 13:25:13 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12A0316A406 for ; Mon, 19 Feb 2007 13:25:13 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 94E4113C494 for ; Mon, 19 Feb 2007 13:25:12 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id E60471FFDE6 for ; Mon, 19 Feb 2007 14:25:10 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 9F68F1FFDD7; Mon, 19 Feb 2007 14:25:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id A0A4C444889 for ; Mon, 19 Feb 2007 13:23:09 +0000 (UTC) Date: Mon, 19 Feb 2007 13:23:09 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: FreeBSD current mailing list Message-ID: <20070219130102.N47107@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: Subject: [mfi] command timeouts 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, 19 Feb 2007 13:25:13 -0000 Hi, I am testing mfi on a Dell 2950 with 6 PD, 2LD (1st LD=RAID1, 2nd LD=RAID5, 1HTSP). (The somewhat sucky) megacli "works". While most commands to gather information work fine, as do pulling out disks hard, setting a disk offline or running some other commands hangs 'something', which might be the controller? For example: foo# megacli -PDOffline -PhysDrv'[1:3]' -a0 EnclId-1 SlotId-3 state changed to OffLine. foo# foo# ls -l It's not only this process but all disk IO related processes. On the serial console I get: ... mfi0: COMMAND 0xffffffff80c3c040 TIMEOUT AFTER 732 SECONDS mfi0: COMMAND 0xffffffff80c3b8d0 TIMEOUT AFTER 732 SECONDS mfi0: COMMAND 0xffffffff80c3cb68 TIMEOUT AFTER 732 SECONDS mfi0: COMMAND 0xffffffff80c3bd98 TIMEOUT AFTER 732 SECONDS mfi0: COMMAND 0xffffffff80c3bc88 TIMEOUT AFTER 732 SECONDS mfi0: COMMAND 0xffffffff80c3cbf0 TIMEOUT AFTER 732 SECONDS mfi0: COMMAND 0xffffffff80c3cc78 TIMEOUT AFTER 732 SECONDS mfi0: COMMAND 0xffffffff80c3cf20 TIMEOUT AFTER 732 SECONDS mfi0: COMMAND 0xffffffff80c3cd88 TIMEOUT AFTER 732 SECONDS mfi0: COMMAND 0xffffffff80c3cfa8 TIMEOUT AFTER 732 SECONDS mfi0: COMMAND 0xffffffff80c3d828 TIMEOUT AFTER 684 SECONDS mfi0: COMMAND 0xffffffff80c3db58 TIMEOUT AFTER 679 SECONDS mfi0: COMMAND 0xffffffff80c3de88 TIMEOUT AFTER 44 SECONDS mfi0: COMMAND 0xffffffff80c3c728 TIMEOUT AFTER 763 SECONDS mfi0: COMMAND 0xffffffff80c3c040 TIMEOUT AFTER 763 SECONDS mfi0: COMMAND 0xffffffff80c3b8d0 TIMEOUT AFTER 763 SECONDS mfi0: COMMAND 0xffffffff80c3cb68 TIMEOUT AFTER 763 SECONDS mfi0: COMMAND 0xffffffff80c3bd98 TIMEOUT AFTER 763 SECONDS mfi0: COMMAND 0xffffffff80c3bc88 TIMEOUT AFTER 763 SECONDS mfi0: COMMAND 0xffffffff80c3cbf0 TIMEOUT AFTER 763 SECONDS mfi0: COMMAND 0xffffffff80c3cc78 TIMEOUT AFTER 763 SECONDS mfi0: COMMAND 0xffffffff80c3cf20 TIMEOUT AFTER 763 SECONDS mfi0: COMMAND 0xffffffff80c3cd88 TIMEOUT AFTER 763 SECONDS mfi0: COMMAND 0xffffffff80c3cfa8 TIMEOUT AFTER 763 SECONDS mfi0: COMMAND 0xffffffff80c3d828 TIMEOUT AFTER 715 SECONDS mfi0: COMMAND 0xffffffff80c3db58 TIMEOUT AFTER 710 SECONDS mfi0: COMMAND 0xffffffff80c3de88 TIMEOUT AFTER 75 SECONDS mfi0: COMMAND 0xffffffff80c3c728 TIMEOUT AFTER 793 SECONDS mfi0: COMMAND 0xffffffff80c3c040 TIMEOUT AFTER 794 SECONDS mfi0: COMMAND 0xffffffff80c3b8d0 TIMEOUT AFTER 794 SECONDS mfi0: COMMAND 0xffffffff80c3cb68 TIMEOUT AFTER 794 SECONDS mfi0: COMMAND 0xffffffff80c3bd98 TIMEOUT AFTER 794 SECONDS mfi0: COMMAND 0xffffffff80c3bc88 TIMEOUT AFTER 794 SECONDS mfi0: COMMAND 0xffffffff80c3cbf0 TIMEOUT AFTER 794 SECONDS mfi0: COMMAND 0xffffffff80c3cc78 TIMEOUT AFTER 794 SECONDS mfi0: COMMAND 0xffffffff80c3cf20 TIMEOUT AFTER 794 SECONDS mfi0: COMMAND 0xffffffff80c3cd88 TIMEOUT AFTER 794 SECONDS mfi0: COMMAND 0xffffffff80c3cfa8 TIMEOUT AFTER 794 SECONDS mfi0: COMMAND 0xffffffff80c3d828 TIMEOUT AFTER 746 SECONDS mfi0: COMMAND 0xffffffff80c3db58 TIMEOUT AFTER 741 SECONDS mfi0: COMMAND 0xffffffff80c3de88 TIMEOUT AFTER 106 SECONDS mfi0: COMMAND 0xffffffff80c3c728 TIMEOUT AFTER 824 SECONDS ... I can still break to ddb. Without disk I/O, the only possible thing I can really do is type reset. I'll build a debugging kernel so I can do show alllocks, etc but if someone with more experience with this driver/hw could contact me I can run further tests. I also found that doing a single "sync" could hang the system under some circumstances for 1-4 seconds. /bz -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT