diff options
| author | Robin H. Johnson <robbat2@gentoo.org> | 2013-12-16 09:31:19 -0800 |
|---|---|---|
| committer | Ben Hutchings <ben@decadent.org.uk> | 2014-02-15 19:20:13 +0000 |
| commit | 536b1f2107eddfd94b7ab11a787b460b1ac4941a (patch) | |
| tree | 9a731e6c40de07a225371a039314ffeed1e1908a /Documentation | |
| parent | fac003d581af1a7b2922d723c2cd078e533a2fb6 (diff) | |
| download | kernel_samsung_smdk4412-536b1f2107eddfd94b7ab11a787b460b1ac4941a.zip kernel_samsung_smdk4412-536b1f2107eddfd94b7ab11a787b460b1ac4941a.tar.gz kernel_samsung_smdk4412-536b1f2107eddfd94b7ab11a787b460b1ac4941a.tar.bz2 | |
libata: disable a disk via libata.force params
commit b8bd6dc36186fe99afa7b73e9e2d9a98ad5c4865 upstream.
A user on StackExchange had a failing SSD that's soldered directly
onto the motherboard of his system. The BIOS does not give any option
to disable it at all, so he can't just hide it from the OS via the
BIOS.
The old IDE layer had hdX=noprobe override for situations like this,
but that was never ported to the libata layer.
This patch implements a disable flag for libata.force.
Example use:
libata.force=2.0:disable
[v2 of the patch, removed the nodisable flag per Tejun Heo]
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
Signed-off-by: Tejun Heo <tj@kernel.org>
Link: http://unix.stackexchange.com/questions/102648/how-to-tell-linux-kernel-3-0-to-completely-ignore-a-failing-disk
Link: http://askubuntu.com/questions/352836/how-can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not-even-co
Link: http://superuser.com/questions/599333/how-to-disable-kernel-probing-for-drive
[bwh: Backported to 3.2: adjust context]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/kernel-parameters.txt | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 2ba8272..1b196ea 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -1305,6 +1305,8 @@ bytes respectively. Such letter suffixes can also be entirely omitted. * dump_id: dump IDENTIFY data. + * disable: Disable this device. + If there are multiple matching configurations changing the same attribute, the last one is used. |