From mboxrd@z Thu Jan 1 00:00:00 1970 From: Doug McLain Subject: [Fwd: Re: sata_sil problems (lockup at boottime)] Date: Mon, 10 Jan 2005 16:04:53 -0500 Message-ID: <41E2EDF5.5000706@comcast.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------070203010604020004010201" Return-path: Received: from rwcrmhc12.comcast.net ([216.148.227.85]:33252 "EHLO rwcrmhc12.comcast.net") by vger.kernel.org with ESMTP id S262725AbVAJWEn (ORCPT ); Mon, 10 Jan 2005 17:04:43 -0500 Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: linux-ide@vger.kernel.org, jgarzik@pobox.com This is a multi-part message in MIME format. --------------070203010604020004010201 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit -- http://nostar.net/ --------------070203010604020004010201 Content-Type: message/rfc822; name="Re: sata_sil problems (lockup at boottime)" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Re: sata_sil problems (lockup at boottime)" Received: from vger.kernel.org ([12.107.209.244]) by sccrmxc14.comcast.net (sccrmxc14) with ESMTP id <20050110163626s140065qrfe>; Mon, 10 Jan 2005 16:36:26 +0000 X-Originating-IP: [12.107.209.244] Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262317AbVAJQer (ORCPT ); Mon, 10 Jan 2005 11:34:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262318AbVAJQer (ORCPT ); Mon, 10 Jan 2005 11:34:47 -0500 Received: from rwcrmhc12.comcast.net ([216.148.227.85]:32952 "EHLO rwcrmhc12.comcast.net") by vger.kernel.org with ESMTP id S262317AbVAJQeW (ORCPT ); Mon, 10 Jan 2005 11:34:22 -0500 Received: from [192.168.0.5] (bgp01091238bgs.waren401.mi.comcast.net[68.43.184.152]) by comcast.net (rwcrmhc12) with ESMTP id <2005011016342001400ge0jee>; Mon, 10 Jan 2005 16:34:21 +0000 Message-ID: <41E2A088.8090802@comcast.net> Date: Mon, 10 Jan 2005 10:34:32 -0500 From: Doug McLain User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040618 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gerald Hopf , linux-kernel@vger.kernel.org Subject: Re: sata_sil problems (lockup at boottime) References: <41B243A5.2010506@nv-systems.net> In-Reply-To: <41B243A5.2010506@nv-systems.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org Gerald Hopf wrote: > Hello everyone, > > i'm having some really strange problems with the sata_sil driver. > > My hardware: > Asus A7N8X Deluxe Rev 1.x with onboard Sil3112 Controller > - Samsung SP1614C SATA Harddrive > - for further testing : PATA to SATA Adapter that came with an ABIT > Mainboard > > What i'm trying to accomplish: i'm trying to use this Samsung SATA > harddrive in my Linux Fileserver: > > When the Silicon Image Controller is enabled (it can be disabled by a > jumper) and no harddrive is connected, everything boots fine. > If i connect a harddrive, i get the following message (exact messages > change slightly) while booting: > > - - - - - START - - - - - > ====================== > [] common_interrupt+0x1a/0x20 > [] __do_softirq+0x30/0x90 > [] do_softirq+0x41/0x50 > ====================== > [] irq_exit+0x34/0x40 > [] do_IRQ+9x45/0x60 > [] common_interrupt+0x1a/0x20 > [] delay_tsc+0x14/0x20 > [] __delay+0x12/0x20 > [] ata_pio_complet+0xe0/0x1f0 > [] ata_pio_test+0x95/0xb0 > [] worker_thread+0x1cc/0x290 > [] ata_pio_task+0x0/0xb0 > [] default_wake_function+0x0/0x20 > [] default_wake_function+0x0/0x20 > [] worker_thread+0x0/0x290 > [] kthread+0xa5/0xb0 > [] kthread+0x0/0xb0 > [] kernel_thread_helper+0x5/0x14 > handlers: > [] (ata_interrupt+0x0/0x1c0) > Disabling IRQ #11 > ata: dev 0 ATA, max UDMA/100, 361882080 sectors: lba 48 > _ > - - - - - END - - - - - > > This happens with both the Samsung SP1614C "native" SATA drive, as well > as with an IBM 180GB PATA drive, using a PATA-to-SATA Adapter. > So i'm not sure whether this is harddrive dependent, but at least it > doesn't look like it... > > This problem has been there in all of the latest 2.6.X kernel revisions. > I'm currently using 2.6.10-rc3 (which came out today), but i've allready > had this problem in 2.6.9 and 2.6.8 and probably even 2.6.7 if i > remember correctly. > > I tried quite a lot to get rid of those problems, including: > - Flashing a new/different Bios (even with different versions of the > Silicon Image SATA Bios part: 4.2.47 and 4.2.50) > - Disabling APIC in the Bios, compiling Kernel with or without APIC > - Changing the IRQ of the Controller by reserving IRQ#11 in the Bios > - Disabling allmost every other onboard device i could, including > serial/parallel/usb/firewire/3com lan (and there are no PCI/Addon cards > besides an nvidia geforce2mx agp card installed in this pc anyway!) > - Connecting drives to both ports > > I found the following discussions which might be related to what i'm > experiencing, but noone seems to have a solution. Some seem to suggest > it worked fine till 2.6.5: > (The first two seem to be most related, i'm not so sure of the third one) > http://www.fedoraforum.org/forum/archive/index.php/t-26543.html > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128180 > http://www.fedoraforum.org/forum/archive/index.php/t-23028.html > > Screenshots of the error messages can be found here: > http://www.nv-systems.net/pics/lkml/sata_sil1.jpg <-- the one from above > http://www.nv-systems.net/pics/lkml/sata_sil2.jpg <-- with samsung > instead of ibm > http://www.nv-systems.net/pics/lkml/sata_sil3.jpg <-- the screen just > before the problem > > Is there ANYTHING i can do (except buying a promise controller) ? > > Yours sincerely, > Gerald I am having exactly the same problem, the only difference being the model of drive. Mine is a WD2000. The sata_sil module loads ok though, if the drive is not connected. If it is connected, hard lock. Tested on 2.4.25, 2.6.9, 2.6.10. Doug -- http://nostar.net/ - 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/ --------------070203010604020004010201--