From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Kien Pham <kienca@lycos.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: LibATA ATAPI-Found lockup spot.
Date: Tue, 18 Jan 2005 21:35:50 +0100 [thread overview]
Message-ID: <58cb370e05011812354b35494e@mail.gmail.com> (raw)
In-Reply-To: <41ED66D8.2040808@pobox.com>
On Tue, 18 Jan 2005 14:43:20 -0500, Jeff Garzik <jgarzik@pobox.com> wrote:
> Kien Pham wrote:
> > Hi Jeff,
> >
> > It blocks forever on line 2450 of libata-core.c. This is on vanilla
> > 2.6.10 kernel source. Relevent snippet follows so you don't have to dig.
> > Basically, the middle SCSI layer successfully sends 3 INQUIRY commands.
> > Then it sends a REPORT LUNs command that fails with a status 0x50. The
> > error register reads 0x60 at this point. Then the ATAPI layer sends a
> > REQUEST SENSE which never completes because an interrupt never occurs
> > and we're stuck at line 2450 waiting for completion. O.K. I know the how
> > it happens, any ideas on the why? Or am I on my own? :)
>
> I think Bart mentioned something about problems with REPORT LUNS... I
> bet things would work if we didn't send that command...
There were problems before we supported REQUEST SENSE.
AFAIR ide-scsi sends REPORT LUNS so it should be also OK for libata...
next prev parent reply other threads:[~2005-01-18 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050118191122.4DC7ACA0AF@ws7-4.us4.outblaze.com>
2005-01-18 19:43 ` LibATA ATAPI-Found lockup spot Jeff Garzik
2005-01-18 20:35 ` Bartlomiej Zolnierkiewicz [this message]
2005-01-18 21:22 Kien Pham
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=58cb370e05011812354b35494e@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=jgarzik@pobox.com \
--cc=kienca@lycos.com \
--cc=linux-ide@vger.kernel.org \
/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.