All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Patrick Ale <patrick.ale@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: Robert Hancock <hancockr@shaw.ca>
Subject: Re: libsata doesn't like bus without master
Date: Sun, 11 Feb 2007 12:34:05 -0600	[thread overview]
Message-ID: <45CF619D.6000704@shaw.ca> (raw)
In-Reply-To: <fa.3Ti1gtH2JY4DWsqr3J1loC7lcc0@ifi.uio.no>

Patrick Ale wrote:
> On 2/11/07, Robert Hancock <hancockr@shaw.ca> wrote:
>> Patrick Ale wrote:
>> > Something unrelated to the tests I am doing.
>> >
>> > I found out that the libsata driver doesn't really cope or likes the
>> > idea that you might have a controller without a master drive
>> > configured.
>> >
>> > In this case on ATA2 I have a CDROM drive, connected as slave.
>> > ATA: abnormal status 0x7F on port 0x177
>> > ATA: abnormal status 0x7F on port 0x177
>> > ata2.01: ATAPI, max UDMA/66
>> > ata2.01: configured for UDMA/66
>>
>> Having a single drive on the channel configured as slave is not really a
>> legal configuration. (I believe the ATA standards say that it's
>> something that a host controller/driver/OS is allowed to support, but it
>> is not required to.) A single drive should always be set to master (and
>> connected to the end of the cable and not the middle, by the way).
> 
> It is very legal when one of your harddisks blows out and you take it
> out temporarely and have no money for a replacement IMO. But then
> again, this is probably an abnormality.

Then in that case you should set the remaining drive as master. That's 
just the way PATA is. A lot of BIOSes won't even detect a drive that's 
set as slave with no master present.

> But still, it even complains when no drive is attached to a controller
> at all. Since when you buy an add-on PCI card you get 2 connectors
> even when you want to add one harddisk how does one deal with that?

Yeah, that's a better point. It's not really complaining, but we could 
probably have a better way of suppressing that message. I think it's 
largely there so that we can debug issues with drives not being detected 
when they should.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-02-11 18:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.OcrmlkSFqen95BGHXWJdR6KGswQ@ifi.uio.no>
     [not found] ` <fa.mIV6AQH7D5yiY39XNxbu0M2/1Kc@ifi.uio.no>
     [not found]   ` <fa.3Ti1gtH2JY4DWsqr3J1loC7lcc0@ifi.uio.no>
2007-02-11 18:34     ` Robert Hancock [this message]
2007-02-11 18:41       ` libsata doesn't like bus without master Patrick Ale
2007-02-11 19:58       ` Henrique de Moraes Holschuh
2007-02-11 20:09         ` Patrick Ale
2007-02-21 20:41 Vincent Legoll
2007-02-21 20:47 ` Vincent Legoll
2007-02-21 21:01   ` Patrick Ale
2007-02-21 21:04     ` Patrick Ale
2007-02-21 22:07     ` Vincent Legoll
2007-02-22  8:12     ` Paul Rolland
2007-02-22  8:38       ` Patrick Ale
     [not found] <fa.kM2jAt0lhoofVm0+pIia0W2vzoo@ifi.uio.no>
2007-02-11 17:39 ` Robert Hancock
2007-02-11 17:52   ` Patrick Ale
2007-02-13 16:05   ` Mark Lord
  -- strict thread matches above, loose matches on Subject: below --
2007-02-11 10:27 Patrick Ale
2007-02-13 20:17 ` Tejun Heo

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=45CF619D.6000704@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrick.ale@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.