Date: Mon, 19 Feb 2007 13:23:09 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: FreeBSD current mailing list <current@freebsd.org> Subject: [mfi] command timeouts Message-ID: <20070219130102.N47107@maildrop.int.zabbadoz.net>
next in thread | raw e-mail | index | archive | help
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 <hangs forever> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070219130102.N47107>