All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: walt <w41ter@gmail.com>
Cc: linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: fix boot panic with SATAPI devices on non-SFF HBAs
Date: Sat, 19 Apr 2008 09:08:39 -0500	[thread overview]
Message-ID: <1208614119.3280.8.camel@localhost.localdomain> (raw)
In-Reply-To: <fucsch$ah0$1@ger.gmane.org>

On Sat, 2008-04-19 at 06:34 -0700, walt wrote:
> 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?

If it's a panic with a SATA drive, then no it wouldn't ... the problem I
fixed was in SATAPI only (That's CD/DVD/Tape devices).  If you actually
post the boot log and panic, linux-ide and Tejun might be able to help.
Your brief snippet indicates the controller isn't finding sda, I think.

James



      reply	other threads:[~2008-04-19 14:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 18:18 [PATCH] libata: fix boot panic with SATAPI devices on non-SFF HBAs James Bottomley
2008-04-19 13:34 ` walt
2008-04-19 14:08   ` James Bottomley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1208614119.3280.8.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=w41ter@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.