linux-kernel - Re: Checking module parameters

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090119093814.BC18014CA88@irishsea.home.craig-wood.com>
Date:	Mon, 19 Jan 2009 09:38:07 +0000
From:	nick@...ig-wood.com (Nick Craig-Wood)
To:	David Wagner <daw@...berkeley.edu>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Checking module parameters

David Wagner <daw@...berkeley.edu> wrote:
>  Is there a way to tell what options have been applied to a currently
>  loaded kernel module?
> 
>  I'm trying to force libata to use 1.5Gbps rather than 3Gbps, so I created
>  a file /etc/modprobe.d/local containing:
>    options libata force=1.5Gbps
>  However my SATA drive gets loaded at 3Gbps.  I'm trying to figure out how
>  to debug this so that I can tell whether the option got correctly applied
>  to the libata module, and if not, how to force the SATA link to 1.5Gbps.
>  Any suggestions or ideas?
> 
>  (I can't set libata.force=1.5Gbps as a kernel argument because on my
>  Fedora kernel, libata is loaded as a module rather than built into the
>  kernel.  I can't run "modprobe libata force=1.5Gbps" by hand because
>  I've got SATA drives, so the libata module is automatically loaded before
>  I get shell access.)

I had to do this recently (under debian I ended up putting
"libata force=1.5Gbps" into /etc/modules)

You can check it is working by looking for something like this in the log

[    2.345058] ata1: FORCE: PHY spd limit set to 1.5Gbps
[    2.345058] ata1: SATA max UDMA/133 abar m2048@...b106000 port 0xfb106100 irq 218
[    2.345058] ata2: FORCE: PHY spd limit set to 1.5Gbps
[    2.345058] ata2: SATA max UDMA/133 abar m2048@...b106000 port 0xfb106180 irq 218
[    2.345058] ata3: FORCE: PHY spd limit set to 1.5Gbps
[    2.345058] ata3: SATA max UDMA/133 abar m2048@...b106000 port 0xfb106200 irq 218
[    2.345058] ata4: FORCE: PHY spd limit set to 1.5Gbps
[    2.345058] ata4: SATA max UDMA/133 abar m2048@...b106000 port 0xfb106280 irq 218
[    2.345058] ata5: FORCE: PHY spd limit set to 1.5Gbps
[    2.345058] ata5: SATA max UDMA/133 abar m2048@...b106000 port 0xfb106300 irq 218
[    2.345058] ata6: FORCE: PHY spd limit set to 1.5Gbps
[    2.345058] ata6: SATA max UDMA/133 abar m2048@...b106000 port 0xfb106380 irq 218

-- 
Nick Craig-Wood <nick@...ig-wood.com> -- http://www.craig-wood.com/nick
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/