From mboxrd@z Thu Jan 1 00:00:00 1970 From: walt Subject: Re: [PATCH] libata: fix boot panic with SATAPI devices on non-SFF HBAs Date: Sat, 19 Apr 2008 06:34:30 -0700 Message-ID: References: <1208542728.3063.25.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from main.gmane.org ([80.91.229.2]:40017 "EHLO ciao.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755129AbYDSNe0 (ORCPT ); Sat, 19 Apr 2008 09:34:26 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JnDCt-0005xx-NG for linux-scsi@vger.kernel.org; Sat, 19 Apr 2008 13:34:19 +0000 Received: from adsl-69-234-190-202.dsl.irvnca.pacbell.net ([69.234.190.202]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 19 Apr 2008 13:34:19 +0000 Received: from w41ter by adsl-69-234-190-202.dsl.irvnca.pacbell.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 19 Apr 2008 13:34:19 +0000 In-Reply-To: <1208542728.3063.25.camel@localhost.localdomain> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: linux-scsi@vger.kernel.org Cc: linux-ide@vger.kernel.org James Bottomley wrote: > Current 2.6.25 git head now panics reliably on boot if you have a SATAPI > device connected. > > The problem was introduced by the libata merge trying to pull out all > the SFF code into a separate module... Hi James, When I saw your commit I thought it would fix the panic introduced by Tejun's commit <305d2a1a>, but no luck. I have a pata drive connected to a sata controller using a plugin adapter. After Tejun's commit the kernel panics with unknown-block (8,9) instead of mounting /dev/sda9. Is this the scenario your patch is intended to fix?