I've run the following test:
while true > do > cat link_power_management_policy > echo max_performance | sudo tee link_power_management_policy > sleep 3 > echo min_power | sudo tee link_power_management_policy > sleep 3 > done
While this loop is running, I've created some artificial fs activity:
while true > do > cat /boot/vmlinuz-2.6.38-020638rc5-generic > /dev/null > sleep 1 > done
And also:
for n in $(seq 0 9) > do > sudo find /usr -type f -iname \*$n\* -exec cat {} > /dev/null \; > done
I have found no signs of excepetion Emask in kern.log, the test was run for more than 2 hours.
For completeness, uname -a: Linux spitfire 2.6.38-020638rc5-generic #201102160907 SMP Wed Feb 16 10:18:56 UTC 2011 i686 GNU/Linux
I've run the following test:
while true management_ policy management_ policy management_ policy
> do
> cat link_power_
> echo max_performance | sudo tee link_power_
> sleep 3
> echo min_power | sudo tee link_power_
> sleep 3
> done
While this loop is running, I've created some artificial fs activity:
while true 2.6.38- 020638rc5- generic > /dev/null
> do
> cat /boot/vmlinuz-
> sleep 1
> done
And also:
for n in $(seq 0 9)
> do
> sudo find /usr -type f -iname \*$n\* -exec cat {} > /dev/null \;
> done
I have found no signs of excepetion Emask in kern.log, the test was run
for more than 2 hours.
For completeness, uname -a: 020638rc5- generic #201102160907 SMP Wed Feb 16
Linux spitfire 2.6.38-
10:18:56 UTC 2011 i686 GNU/Linux