mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Patrick Ale" <patrick.ale@gmail.com>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: libsata doesn't like bus without master
Date: Sun, 11 Feb 2007 19:41:44 +0100	[thread overview]
Message-ID: <8d158e1f0702111041m24a631dawf415a26d327a4d37@mail.gmail.com> (raw)
In-Reply-To: <45CF619D.6000704@shaw.ca>

On 2/11/07, Robert Hancock <hancockr@shaw.ca> wrote:
> Patrick Ale wrote:
> > On 2/11/07, Robert Hancock <hancockr@shaw.ca> wrote:
> >> Patrick Ale wrote:
> 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.

Yea, I guess you're right. For me it isnt a problem, This error
message will disappear for me anyway, since I am going to re-add the
drive now, like I said yesterday, I am re-adding stuff one by one, to
isolate problems.

I can just imagine that switching a jumper might not be as easy for
everybody, especialy when they bought special front-loading harddisk
bays for their disks and all, for the very reason of not having to
open the case.

> 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.

It's not like it is causing any problems, nothing hangs or slows down
at boot time, its just something I came across when checking my dmesg
and wanted to inform the list so I could see if this was normal
behaviour or not :)


Patrick

  reply	other threads:[~2007-02-11 18:41 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
2007-02-11 18:41       ` Patrick Ale [this message]
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=8d158e1f0702111041m24a631dawf415a26d327a4d37@mail.gmail.com \
    --to=patrick.ale@gmail.com \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®