From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 21 13:21:30 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8E5A106564A for ; Mon, 21 Apr 2008 13:21:30 +0000 (UTC) (envelope-from d_elbracht@ecngs.de) Received: from ecngs.de (mail.ecngs.de [217.73.144.50]) by mx1.freebsd.org (Postfix) with ESMTP id 31EA08FC27 for ; Mon, 21 Apr 2008 13:21:29 +0000 (UTC) (envelope-from d_elbracht@ecngs.de) Received: from EC1a (ec1.elbracht.net [217.73.144.99]) by ecngs.de (SurgeMail 3.8f2) with ESMTP id 2313333-1922481 for ; Mon, 21 Apr 2008 15:06:18 +0200 From: "d_elbracht" To: Date: Mon, 21 Apr 2008 15:06:06 +0200 Message-ID: <004901c8a3b0$785b7390$639049d9@EC1a> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcijsHV1NKvcjsLARPqcBwah7oMltw== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Subject: Errors on MPT (LSI3801E) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2008 13:21:30 -0000 We are seeing occasional errors like below System is a TYAN S3992, dual am64, 32GB RAM, cvsupd 7.0-STABLE FreeBSD 7.0-STABLE #4: Mon Mar 31 15:06:55 CEST 2008 An Infortrend S16S-G1030 + S16S-J1000-S is connected to an LSI3801-E. A Media-Scan on the Infortrend does NOT show any errors. The 3801 was swapped, still errors. besides the LSI 3801-E, there are 4 other controllers used with NO errors at all: twa0: <3ware 9000 series Storage Controller> port 0x5c00-0x5c3f mem 0xcc000000-0xcdffffff,0xfddff000-0xfddfffff irq 20 at device 5.0 on pci2 twa0: [ITHREAD] twa0: INFO: (0x15: 0x1300): Controller details:: Model 9550SX-12, 12 ports, Firmware FE9X 3.08.02.007, BIOS BE9X 3.08.00.002 atapci0: port 0x7c00-0x7c07,0x7880-0x7883,0x7800-0x7807,0x7480-0x7483,0x7400-0x741f mem 0xfdefe000-0xfdefffff irq 11 at device 14.0 on pci1 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] ata1: on atapci1 ata1: [ITHREAD] isp0: port 0x8800-0x88ff mem 0xfdfff000-0xfdffffff irq 22 at device 4.0 on pci3 isp0: [ITHREAD] isp0: Board Type 2312, Chip Revision 0x2, loaded F/W Revision 3.3.19 aac0: mem 0xfe400000-0xfe5fffff irq 28 at device 14.0 on pci7 aac0: Enabling 64-bit address support aac0: New comm. interface enabled aac0: [ITHREAD] aac0: ICP ICP5805BL, aac driver 2.0.0-1 aac0: Error 5 sending VMIoctl command mpt0: port 0xb000-0xb0ff mem 0xfeafc000-0xfeafffff,0xfeae0000-0xfeaeffff irq 30 at device 0.0 on pci9 mpt0: [ITHREAD] mpt0: MPI Version=1.5.17.0 mpt0: mpt_cam_event: 0x16 mpt0: mpt_cam_event: 0x16 Apr 21 13:01:21 spool1 kernel: bad block -289758967411216238, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block -1974150432459695593, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block 3924693657070553602, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block -1880893109408328697, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block 7443855300351118928, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block 8635841315344043953, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block -5554226653918778662, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block 3538396528377557312, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block 4440353572002830628, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: g_vfs_done():da53[READ(offset=709705054559076352, length=65536)]error = 5 Apr 21 13:01:21 spool1 kernel: bad block 5392362287553715125, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block -2588558218317828228, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block 4848756102075306261, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block -4433087689437922947, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block 4450693383788471588, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Apr 21 13:01:21 spool1 kernel: bad block 3047254019211875932, ino 3498114 Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114 on /news2/spool/news/28: bad block Any clue ? best regards Dieter