Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263173AbUD2XoO (ORCPT ); Thu, 29 Apr 2004 19:44:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264913AbUD2XoO (ORCPT ); Thu, 29 Apr 2004 19:44:14 -0400 Received: from sol.linkinnovations.com ([203.94.173.142]:45440 "EHLO theirongiant.lochness.weebeastie.net") by vger.kernel.org with ESMTP id S263173AbUD2XoL (ORCPT ); Thu, 29 Apr 2004 19:44:11 -0400 Date: Fri, 30 Apr 2004 09:42:59 +1000 From: CaT To: linux-kernel@vger.kernel.org Cc: Jeff Garzik Subject: libata + siI3112 + 2.6.5-rc3 hang Message-ID: <20040429234258.GA6145@zip.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organisation: Furball Inc. User-Agent: Mutt/1.5.5.1+cvs20040105i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4071 Lines: 101 Just acquired a Seagate 200GB SATA HD (yeah, baby, yeah ;) and hooked it up to my onboard Silicon Image iI 3112 SATA Raid controller of my Gigabyte nforce2 MB. Things work fine for the most part except when heavy IO is done on the drive. Then the system hangs totally with no console error msgs displayed. This also happens under Debian sarge's 2.4.25 aswell and has occured when I did a mke2fs -c on a partition and (twice) with hdparm -tT. The first time hdparm works fine and infact clocks the HD at 62MB/s (wowsers!), but the second time the system hangs. I'm not 100% sure what info to provide here so I took a stab at a few things: 0000:01:0d.0 Unknown mass storage controller: CMD Technology Inc Silicon Image SiI 3112 SATARaid Controller (rev 02) Subsystem: CMD Technology Inc Silicon Image SiI 3112 SATARaid Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 --- 8< --- scsi0? I thought it detected it at scsi1? This reminds me. The MB has the connector labeled as SATA1 but on bootup it's detected as the primary SATA drive. --- 8< --- CONFIG_SCSI_SATA=y # CONFIG_SCSI_SATA_SVW is not set # CONFIG_SCSI_SATA_PROMISE is not set CONFIG_SCSI_SATA_SIL=y # CONFIG_SCSI_SATA_SIS is not set # CONFIG_SCSI_SATA_VIA is not set # CONFIG_SCSI_SATA_VITESSE is not set --- 8< --- lexx:/proc# more interrupts CPU0 0: 5107953 IO-APIC-edge timer 1: 9 IO-APIC-edge i8042 2: 0 XT-PIC cascade 8: 1 IO-APIC-edge rtc 9: 0 XT-PIC NVidia nForce2 11: 1872 IO-APIC-edge eth0 12: 58 IO-APIC-edge i8042 15: 3200 IO-APIC-edge libata NMI: 0 LOC: 5107919 ERR: 0 MIS: 0 If you need more info, any debugging done, etc please yell. This is going to be the primary and only linux drive in the system (I'm relegating windows to 'PATA') and so it'd be nice to have it stable. :) Thanks. -- Red herrings strewn hither and yon. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/