I updated the description and corrected the Bug title to reflect the new
aspects of the bug I've found out:

sysfsutils  2.1.0-2 (hardy)

Sysfsutils manages to give a successful output only when sysfs.conf is set with 
only one scsi_host link tweak.
As far as I managed to understand the presence of other tweaks (for instance 
tweaks to cpu governor and sound card) did not affect this bug.
The only blocking tweak is the scsi_host link.
All tweaks that in sysfs.conf follow the first scsi_host link directive are 
ignored. However if they are put above to be executed first they are carried 
out fine.

Changing the first scsi_host link doesn't positively affect the bug
(host0, host1 and so on always cause the bug to appear).

 sudo sh -ex /etc/init.d/sysfsutils start
+ CONFFILE=/etc/sysfs.conf
+ [ -r /etc/sysfs.conf ]
+ echo -n Setting sysfs variables...
Setting sysfs variables...+ sed s/#.*$//; /^[[:space:]]*$/d; 
              
s/^[[:space:]]*\([^=[:space:]]*\)[[:space:]]*\([^=[:space:]]*\)[[:space:]]*=[[:space:]]*\(.*\)/\1
 \2 \3/ /etc/sysfs.conf
+ read f1 f2 f3
+ [ class/scsi_host/host0/link_power_management_policy = mode -a -n min_power 
-a -n  ]
+ [ class/scsi_host/host0/link_power_management_policy = owner -a -n min_power 
-a -n  ]
+ [ class/scsi_host/host0/link_power_management_policy -a -n min_power -a -z  ]
+ [ -f /sys/class/scsi_host/host0/link_power_management_policy ]
+ echo unknown attribute class/scsi_host/host0/link_power_management_policy
unknown attribute class/scsi_host/host0/link_power_management_policy
+ read f1 f2 f3
+ echo done.
done.
$


** Summary changed:

- sysfsutils install fails dpkg-configure with 2.6.24 kernel
+ sysfsutils fail to tweak all sysfs.conf directives

** Description changed:

  Binary package hint: sysfsutils
  
- Although libsysfs and sysfsutils work flawlessly on 2.6.22 kernel, 
- with the 2.6.24 one I cannot have /etc/init.d/sysfsutils running. 
+ if I set sysfs.conf as follows
+ # this enables lowest power state for SATA link host nr. 0,1,2
+ class/scsi_host/host0/link_power_management_policy = min_power
+ class/scsi_host/host1/link_power_management_policy = min_power
+ class/scsi_host/host2/link_power_management_policy = min_power
  
- Starting it via the init script simply does nothing, despite displaying
- "Setting sysfs variables..." (no "done" string however appears!)
+ and run sysfsutils only the first scsi_host link is set to min_power. 
+ Checking with 'cat' confirms the following output.
  
- Trying to re-install sysfsutils generates a dpkg-configure error saying
+ $ sudo sh -ex /etc/init.d/sysfsutils start
  
- /usr/sbin/dpkg-reconfigure: sysfsutils is broken or not fully installed
+ + CONFFILE=/etc/sysfs.conf
+ + [ -r /etc/sysfs.conf ]
+ + echo -n Setting sysfs variables...
+ Setting sysfs variables...+ sed s/#.*$//; /^[[:space:]]*$/d;
+               
s/^[[:space:]]*\([^=[:space:]]*\)[[:space:]]*\([^=[:space:]]*\)[[:space:]]*=[[:space:]]*\(.*\)/\1
 \2 \3/ /etc/sysfs.conf
+ + read f1 f2 f3
+ + [ class/scsi_host/host0/link_power_management_policy = mode -a -n min_power 
-a -n ]
+ + [ class/scsi_host/host0/link_power_management_policy = owner -a -n 
min_power -a -n ]
+ + [ class/scsi_host/host0/link_power_management_policy -a -n min_power -a -z ]
+ + [ -f /sys/class/scsi_host/host0/link_power_management_policy ]
+ + echo -n min_power
+ $
  
- however no way reinstalling it solves the problem (notice that rebooting
- with 2.6.22 kernel sysfsutils works again)
+ Sysfsutils manages to give a successful output only when sysfs.conf is set 
with only one scsi_host link tweak.
+ As far as I managed to understand the presence of other tweaks (for instance 
tweaks to cpu governor and sound card) did not affect this bug.
+ The only blocking tweak is the scsi_host link.
+ All tweaks that in sysfs.conf follow the first scsi_host link directive are 
ignored. However if they are put above to be executed first they are carried 
out fine.
+ 
+ Changing the first scsi_host link doesn't positively affect the bug
+ (host0, host1 and so on always cause the bug to appear).
+ 
+  sudo sh -ex /etc/init.d/sysfsutils start
+ + CONFFILE=/etc/sysfs.conf
+ + [ -r /etc/sysfs.conf ]
+ + echo -n Setting sysfs variables...
+ Setting sysfs variables...+ sed s/#.*$//; /^[[:space:]]*$/d; 
+               
s/^[[:space:]]*\([^=[:space:]]*\)[[:space:]]*\([^=[:space:]]*\)[[:space:]]*=[[:space:]]*\(.*\)/\1
 \2 \3/ /etc/sysfs.conf
+ + read f1 f2 f3
+ + [ class/scsi_host/host0/link_power_management_policy = mode -a -n min_power 
-a -n  ]
+ + [ class/scsi_host/host0/link_power_management_policy = owner -a -n 
min_power -a -n  ]
+ + [ class/scsi_host/host0/link_power_management_policy -a -n min_power -a -z  
]
+ + [ -f /sys/class/scsi_host/host0/link_power_management_policy ]
+ + echo unknown attribute class/scsi_host/host0/link_power_management_policy
+ unknown attribute class/scsi_host/host0/link_power_management_policy
+ + read f1 f2 f3
+ + echo done.
+ done.
+ $

** Description changed:

  Binary package hint: sysfsutils
  
  if I set sysfs.conf as follows
  # this enables lowest power state for SATA link host nr. 0,1,2
- class/scsi_host/host0/link_power_management_policy = min_power
- class/scsi_host/host1/link_power_management_policy = min_power
  class/scsi_host/host2/link_power_management_policy = min_power
+ class/scsi_host/host3/link_power_management_policy = min_power
+ class/scsi_host/host4/link_power_management_policy = min_power
  
- and run sysfsutils only the first scsi_host link is set to min_power. 
+ and run sysfsutils none of the scsi_host link are set to min_power. 
  Checking with 'cat' confirms the following output.
  
  $ sudo sh -ex /etc/init.d/sysfsutils start
  
  + CONFFILE=/etc/sysfs.conf
  + [ -r /etc/sysfs.conf ]
  + echo -n Setting sysfs variables...
  Setting sysfs variables...+ sed s/#.*$//; /^[[:space:]]*$/d;
                
s/^[[:space:]]*\([^=[:space:]]*\)[[:space:]]*\([^=[:space:]]*\)[[:space:]]*=[[:space:]]*\(.*\)/\1
 \2 \3/ /etc/sysfs.conf
  + read f1 f2 f3
- + [ class/scsi_host/host0/link_power_management_policy = mode -a -n min_power 
-a -n ]
- + [ class/scsi_host/host0/link_power_management_policy = owner -a -n 
min_power -a -n ]
- + [ class/scsi_host/host0/link_power_management_policy -a -n min_power -a -z ]
+ + [ class/scsi_host/host2/link_power_management_policy = mode -a -n min_power 
-a -n ]
+ + [ class/scsi_host/host2/link_power_management_policy = owner -a -n 
min_power -a -n ]
+ + [ class/scsi_host/host2/link_power_management_policy -a -n min_power -a -z ]
  + [ -f /sys/class/scsi_host/host0/link_power_management_policy ]
  + echo -n min_power
  $
  
- Sysfsutils manages to give a successful output only when sysfs.conf is set 
with only one scsi_host link tweak.
+ ls -l /sys/class/scsi_host/host3/link_power_management_policy 
+ -rw-r--r-- 1 root root 0 2008-02-21 17:43 
/sys/class/scsi_host/host3/link_power_management_policy
+ ls -l /sys/class/scsi_host/host2/link_power_management_policy 
+ -rw-r--r-- 1 root root 0 2008-02-21 17:45 
/sys/class/scsi_host/host2/link_power_management_policy
+ ls -l /sys/class/scsi_host/host4/link_power_management_policy 
+ -rw-r--r-- 1 root root 4096 2008-02-21 17:42 
/sys/class/scsi_host/host4/link_power_management_policy
+ 
+ cat /sys/class/scsi_host/host2/link_power_management_policy max_performance
+ and so on for the other two.
+ 
  As far as I managed to understand the presence of other tweaks (for instance 
tweaks to cpu governor and sound card) did not affect this bug.
  The only blocking tweak is the scsi_host link.
  All tweaks that in sysfs.conf follow the first scsi_host link directive are 
ignored. However if they are put above to be executed first they are carried 
out fine.
  
  Changing the first scsi_host link doesn't positively affect the bug
- (host0, host1 and so on always cause the bug to appear).
- 
-  sudo sh -ex /etc/init.d/sysfsutils start
- + CONFFILE=/etc/sysfs.conf
- + [ -r /etc/sysfs.conf ]
- + echo -n Setting sysfs variables...
- Setting sysfs variables...+ sed s/#.*$//; /^[[:space:]]*$/d; 
-               
s/^[[:space:]]*\([^=[:space:]]*\)[[:space:]]*\([^=[:space:]]*\)[[:space:]]*=[[:space:]]*\(.*\)/\1
 \2 \3/ /etc/sysfs.conf
- + read f1 f2 f3
- + [ class/scsi_host/host0/link_power_management_policy = mode -a -n min_power 
-a -n  ]
- + [ class/scsi_host/host0/link_power_management_policy = owner -a -n 
min_power -a -n  ]
- + [ class/scsi_host/host0/link_power_management_policy -a -n min_power -a -z  
]
- + [ -f /sys/class/scsi_host/host0/link_power_management_policy ]
- + echo unknown attribute class/scsi_host/host0/link_power_management_policy
- unknown attribute class/scsi_host/host0/link_power_management_policy
- + read f1 f2 f3
- + echo done.
- done.
- $
+ (host2, host3 and so on always cause the bug to appear).

-- 
sysfsutils fail to tweak all sysfs.conf directives
https://bugs.launchpad.net/bugs/184783
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to