From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mel Gorman <mel@csn.ul.ie>
Cc: petkovbb@gmail.com, sshtylyov@ru.mvista.com,
linux-kernel@vger.kernel.org
Subject: Re: Is the change to IDE probing really necessary?
Date: Tue, 25 Nov 2008 00:03:06 +0000 [thread overview]
Message-ID: <20081125000306.014f7771@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20081124230948.GB8293@csn.ul.ie>
> Then can the message outputted printed out say something along those
> lines? On this particular machine, probing 0x3F resulted in a misconfigured
That is exactly what it says at the moment.
> machine. It's not obvious to me at all that 0x3F means probe everything,
> possibly with adverse results and 0x03 means peer at primary/secondary.
> Which in this case resulted in no disk because the mask defaults to 0
> now instead of 0x3 or anything else.
The mask is set to 0 and then the master/slave are detected based upon
the presence of PCI IDE devices on the master/slave ports.
> What you suggest for the numbers in each case is right, but it's not
> obvious. The machine might be so old that no will encounter this problem
> in practice.
That is why pata_legacy does it automatically. Users shouldn't need to.
> > If you want it to just work automatically use pata_legacy instead as that
> > automatically flips between probing ISA tertiary devices and leaving
> > things well alone according to the presence of PCI bus.
> >
>
> It doesn't find the disk.
If pata_legacy fails to find the disk then please send me an lspci
-vvxxx, chances are you shouldn't be using pata_legacy or ide_generic in
the first place but have a PCI device and don't have the right driver
loaded (or we don't have a right driver in which case it needs the
heuristics fixing up)
next prev parent reply other threads:[~2008-11-25 0:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 15:56 Mel Gorman
2008-11-24 18:43 ` Mel Gorman
2008-11-24 18:54 ` Alan Cox
2008-11-24 23:09 ` Mel Gorman
2008-11-25 0:03 ` Alan Cox [this message]
2008-11-25 0:16 ` Mel Gorman
2008-11-25 0:30 ` Alan Cox
2008-11-25 0:36 ` Mel Gorman
2008-11-24 22:51 ` Borislav Petkov
2008-11-25 0:01 ` Mel Gorman
2008-11-25 7:21 ` Borislav Petkov
2008-11-25 10:45 ` Mel Gorman
[not found] <bBM1f-6TS-19@gated-at.bofh.it>
[not found] ` <bBOFD-1WX-21@gated-at.bofh.it>
[not found] ` <bBOYV-2w9-7@gated-at.bofh.it>
[not found] ` <bBSST-7ut-11@gated-at.bofh.it>
[not found] ` <bBTFg-8vL-15@gated-at.bofh.it>
[not found] ` <bBTOS-dn-3@gated-at.bofh.it>
[not found] ` <bBU8c-w0-1@gated-at.bofh.it>
2008-11-26 21:48 ` Bodo Eggert
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=20081125000306.014f7771@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=petkovbb@gmail.com \
--cc=sshtylyov@ru.mvista.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 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®