From: "Alan Jenkins" <alan-jenkins@tuffmail.co.uk>
To: "Grant Grundler" <grundler@google.com>
Cc: "Justin Piszcz" <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: 2.6.28: Is there a way to disable sata probing for certain ports?
Date: Tue, 30 Dec 2008 19:08:28 +0000 [thread overview]
Message-ID: <9b2b86520812301108k525ca193gac0307b630bdbbd1@mail.gmail.com> (raw)
In-Reply-To: <da824cf30812300908x3ff6061cn569203d5163664ea@mail.gmail.com>
On Tue, Dec 30, 2008 at 5:08 PM, Grant Grundler <grundler@google.com> wrote:
> On Tue, Dec 30, 2008 at 4:24 AM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>> When I boot from an Intel X25-E SSD, it takes roughly a few seconds;
>> however, items such as:
>>
>> $ dmesg|grep link\ down
>> [ 2.447030] ata4: SATA link down (SStatus 0 SControl 300)
>> [ 4.481288] ata5: SATA link down (SStatus 0 SControl 0)
>> [ 6.501288] ata6: SATA link down (SStatus 0 SControl 0)
>> [ 8.522038] ata7: SATA link down (SStatus 0 SControl 0)
>> [ 10.552288] ata8: SATA link down (SStatus 0 SControl 0)
>>
>> Scanning for devices on channels that have nothing connected adds to the
>> boot time, is there anyway to turn off/disable scanning for certain ports to
>> help speed the boot process?
>
> Some BIOSs allow one to enable/disable each port individually.
> Have you checked the BIOS config menus for such an option?
>
> drivers/ata/libata-core.c declares "ata_force_param_buf" but I don't
> see any documentation for it despite the reference to
> Documentation/kernel-parameters.txt .
There is. Search the file for "libata.force". But it doesn't support
disabling the scan for specific ports; that has yet to be implemented.
<https://kerneltrap.org/mailarchive/linux-kernel/2008/8/11/2900064/thread>
Alan
next prev parent reply other threads:[~2008-12-30 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 12:24 Justin Piszcz
2008-12-30 17:08 ` Grant Grundler
2008-12-30 19:08 ` Alan Jenkins [this message]
2008-12-31 21:01 ` Justin Piszcz
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=9b2b86520812301108k525ca193gac0307b630bdbbd1@mail.gmail.com \
--to=alan-jenkins@tuffmail.co.uk \
--cc=grundler@google.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--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®