From owner-freebsd-questions@FreeBSD.ORG Mon Jan 5 21:26:54 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B017010656FB for ; Mon, 5 Jan 2009 21:26:54 +0000 (UTC) (envelope-from freebsd@southportcomputers.co.uk) Received: from ted.southportcomputers.co.uk (ted.southportcomputers.co.uk [92.48.124.28]) by mx1.freebsd.org (Postfix) with ESMTP id 6EBC78FC1B for ; Mon, 5 Jan 2009 21:26:54 +0000 (UTC) (envelope-from freebsd@southportcomputers.co.uk) Received: from office.southportcomputers.co.uk ([217.155.248.110] helo=[127.0.0.1]) by ted.southportcomputers.co.uk with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LJwyJ-000AGB-MZ for freebsd-questions@freebsd.org; Mon, 05 Jan 2009 21:26:51 +0000 Message-ID: <49627B1B.5060801@southportcomputers.co.uk> Date: Mon, 05 Jan 2009 21:26:51 +0000 From: Colin User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 090105-0, 05/01/2009), Outbound message X-Antivirus-Status: Clean X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ted.southportcomputers.co.uk X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [26 6] / [26 6] X-AntiAbuse: Sender Address Domain - southportcomputers.co.uk X-Source: X-Source-Args: X-Source-Dir: Subject: Re: 7.0-RELEASE and megaraid (mpt0) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2009 21:26:56 -0000 *Tim Kellers wrote:* >Colin wrote: >>/ Hi folks, />/> I'm running a new server with FreeBSD 7.0-RELEASE and am seeing />>/ timeouts and other messages with mpt0 />> //>>/ These include: />>/ mpt_cam_event: 0x16, 0x12 & 0x60 />>/ />/> More importantly these: />/> Dec 28 16:33:30 ted kernel: mpt0: request 0xc68db554:44729 timed out />/> for ccb 0xc691f000 (req->ccb 0xc691f000) />/> Dec 28 16:33:30 ted kernel: mpt0: request 0xc68d8bc4:44730 timed out />/> for ccb 0xc6ac1c00 (req->ccb 0xc6ac1c00) />/> Dec 28 16:33:30 ted kernel: mpt0: attempting to abort req />/> 0xc68db554:44729 function 0 />/> Dec 28 16:33:30 ted kernel: mpt0: request 0xc68d8328:44731 timed out />/> for ccb 0xc68df800 (req->ccb 0xc68df800) />/> Dec 28 16:33:30 ted kernel: mpt0: mpt_recover_commands: IOC Status />/> 0x4a. Resetting controller. />/> Dec 28 16:33:30 ted kernel: mpt0: completing timedout/aborted req />/> 0xc68db554:44729 />/> Dec 28 16:33:30 ted kernel: mpt0: completing timedout/aborted req />/> 0xc68d8bc4:44730 />/> Dec 28 16:33:30 ted kernel: mpt0: completing timedout/aborted req />/> 0xc68d8328:44731 />/> Dec 28 16:33:30 ted kernel: mpt0: request 0xc68d5ac8:0 timed out for />/> ccb 0xc6af4000 (req->ccb 0) />>/ />/> I have raised this with my provider and they have said "it is working />/> fine without any problem you can simply ignore this message". />>/ />/> Now I'm no expert on the megaraid controller but I'm fairly certain />/> that frequent timeouts are not something that I want to be seeing. I />/> looked around and saw other people asking the same but no answers />/> posted publicly. I was also wondering as to whether linux emulation />/> could be used to run the LSI Megaraid storage manager or whether />/> attempting to do so is a very bad idea.. />>/ />/> Thanks, />/> Colin />>/ Southport Computers. />/> _______________________________________________ />/> freebsd-questions at freebsd.org mailing list />/> http://lists.freebsd.org/mailman/listinfo/freebsd-questions />/> To unsubscribe, send any mail to />/> "freebsd-questions-unsubscribe at freebsd.org " />>/ />>/ />I'm running 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Sat Dec 27 >03:44:52 EST 2008 AMD on a Dell 2850 Poweredge with the defaut LSI/PERC >4 and AMR kernel devices and I'm not seeing any timeouts at all. Maybe >someone knows if something significant in those device files changed >from 7.0 to 7.1? I don't think the Linux drivers are a viable option. >But using 7.1 PRE seems to work just fine, here. > > >mpt0: port 0xec00-0xecff mem >0xdfdf0000-0xdfdfffff,0xdfde0000-0xdfdeffff irq 34 at device 5.0 on pci2 >mpt0: [ITHREAD] >mpt0: MPI Version=1.2.12.0 > > >amr0: mem 0xd90f0000-0xd90fffff irq 106 at >device 4.0 on pci9 >amr0: Using 64-bit DMA >amr0: [ITHREAD] >amr0: delete logical drives supported by controller >amr0: Firmware 351S, BIOS 1.10, 128MB RAM Looks like we're on different hardware. Mine is SAS and yours is SCSI mpt0: port 0xec00-0xecff mem 0xdffec000-0xdffeffff,0xdfff0000-0xdfffffff irq 16 at device 0.0 on pci2 mpt0: [ITHREAD] mpt0: MPI Version=1.5.16.0 da0 at mpt0 bus 0 target 8 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 300.000MB/s transfers da0: Command Queueing Enabled da0: 476837MB (976562176 512 byte sectors: 255H 63S/T 60788C) I have however noticed that the events only occur at specific times. So far I have noticed them only at boot time just after dmesg identifies the adapter and also whenever I try to install/upgrade a port. It doesn't matter what port it is but here is an example (seen as I'm having trouble with the mysql port not compiling but that's for a different thread) # make ===> Extracting for mysql-client-5.0.75 => MD5 Checksum OK for mysql-5.0.75.tar.gz. => SHA256 Checksum OK for mysql-5.0.75.tar.gz. #######Long pause here of >30 seconds with the mpt0 errors being logged ===> Patching for mysql-client-5.0.75