linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Art Haas" <ahaas@airmail.net>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: PATA ATAPI detection debug
Date: Tue, 23 Jan 2007 07:55:23 -0600	[thread overview]
Message-ID: <20070123135523.GA3961@artsapartment.org> (raw)
In-Reply-To: <45B5AB6B.5070903@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]

On Tue, Jan 23, 2007 at 03:30:03PM +0900, Tejun Heo wrote:
> Tejun Heo wrote:
> > Hello, all.
> > 
> > Many people have been reporting libata PATA ATAPI detection problem.  In
> > many but not all cases, the ATAPI device was occupying the slave slot
> > while a disk drive occupies the master slot.  Based on that and J.
> > Taimr's nullify freeze on via fix, I made a cocktail patch which
> > contained four different fixes and it seemed to have fixed the problem
> > for (at least) several people, but the reports are not all consistent.
> > 
> > The attached patches contain the same four fixes but has a selector
> > parameter to enable each fix separately.  Both are equivalent but using
> > 2.6.20-rc5 is recommended to rule out detection problems fixed by
> > polling IDENTIFY.
> > 
> > If your libata driver is compiled into the kernel, add
> > 'libata.debug_cocktail=N' to your kernel parameter.  If you compile
> > libata.ko as module, add 'debug_cocktail=N' module parameter to the
> > module parameter.  e.g. 'modprobe libata.ko debug_cocktail=1'.
> 
> Daniel Fraga and Sero's cases are different issue while I can't
> determine whether J. Taimr's case is limted on via chipset.  So, I need
> more input to proceed.
> 
> *Please* test and report the results.
> 
> Thanks.
> 
> -- 
> tejun

Hi.

I got a chance to test your patches yesterday. Enclosed is the 'dmesg'
output for tests of 'debug_cocktail' values of 1,2,4,8,5,9,6, and 10.
My machine booted successfully each time, but the CD-ROM drive was
never detected.

Sorry it took a while to get to testing. Hope the enclosed info provides
you with useful clues in solving the problem.

Art Haas
-- 
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.

-Thomas Jefferson to James Smith, 1822

[-- Attachment #2: debug_dmesg.tar.gz --]
[-- Type: application/octet-stream, Size: 5433 bytes --]

      reply	other threads:[~2007-01-23 13:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15  8:09 PATA ATAPI detection debug Tejun Heo
2007-01-23  6:30 ` Tejun Heo
2007-01-23 13:55   ` Art Haas [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=20070123135523.GA3961@artsapartment.org \
    --to=ahaas@airmail.net \
    --cc=htejun@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).