[lkml]   [2010]   [Sep]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: sudo rmmod ahci @ succeeds: filesystem access errors follow
On Wednesday 08 September 2010 19:28:57 Stefan Richter wrote:
> Pedro Francisco wrote:
> > That makes no sense. That's what the force option "-f" is for. It's my
> > opinion the usage count for ahci on `lsmod' should be 1 and not 0.
> > Whoever still wants to remove it can use the `rmmod -f ahci'
> The usage count of a module is only there to ensure that function calls
> into the module succeed. As long as some other part of the kernel has a
> pointer of a function in the module, removal of the module needs to be
> prevented.
> "rmmod ahci" on the other hand is something like pulling the SATA cable.
> Or ejection of the controller from an ExpressCard slot. The driver
> shutdown causes the controller device and thus its child devices (disk
> devices behind the controller) to go away, and that's it. You can do also
> # echo $DEVICE_ID > /sys/module/ahci/drivers/pci\:ahci/unbind
> which tells the driver to let go of the controller.

Hum ok... Still I find it weird since on 2.6.32 I've, after `lsmod | grep -i
ahci 32200 4
and on
ahci 32200 0

Why the change of behaviour? Is it because of the split of libahci from ahci ?


 \ /
  Last update: 2010-09-08 21:53    [W:0.043 / U:33.968 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site